diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index bc8ca23..5217da1 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -6,13 +6,13 @@ }, "metadata": { "description": "AI-powered strategic advisor for entrepreneurs. 158 skills, 24 diagnostics, 21 playbooks, 9 industry packs.", - "version": "1.0.0" + "version": "1.1.0-rc.1" }, "plugins": [ { "name": "foreman", "description": "AI-powered strategic advisor for entrepreneurs. 158 business framework skills, 24 diagnostic triage systems, 21 multi-step playbooks, 48 output templates, 9 industry packs, board simulation, implementation tracking, research guides, and organizational politics navigation. Supports solo mode, Stoic philosophical mode, and multilingual output.", - "version": "1.0.0", + "version": "1.1.0-rc.1", "author": { "name": "Fatih Guner" }, diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 24043f4..8376567 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -1,8 +1,10 @@ { "name": "foreman", - "version": "1.0.0", + "version": "1.1.0-rc.1", "description": "AI-powered strategic advisor for entrepreneurs", - "author": "Fatih Guner", - "skills": "./.claude/skills/", - "commands": "./.claude/commands/" + "author": { + "name": "Fatih Guner" + }, + "skills": "./plugins/foreman/skills/", + "commands": "./.claude/plugin-commands/" } diff --git a/.claude/RUNTIME.md b/.claude/RUNTIME.md new file mode 100644 index 0000000..97acbf1 --- /dev/null +++ b/.claude/RUNTIME.md @@ -0,0 +1,33 @@ +# Foreman runtime contract + +This document defines current runtime behavior. Use it when older examples in command, mode or memory documents describe a different storage shape. + +Resolve paths relative to this content directory (the directory containing this file). In a cloned or initialized Claude project this is `.claude/`. In a plugin it is the bundled `content/` directory. In Codex the `foreman` skill links here. Read `policies/advisory.md` and `catalog.json` before routing. + +For a specific request, search `catalog.json` for the requested kind and identifier and read only the matching entry and aliases. Load the entire catalog only when browsing or comparing many entries. This avoids carrying the full catalog through every advisory turn. + +Use exact catalog identifiers first, then `aliases`, then a unique normalized name. Ask the user to choose if several identifiers match. Reject empty names and paths. A diagnostic or template is not a skill: use the catalog's `kind` to load the correct layer. Semantic content links are relative to each source file, while instruction paths beginning `.claude/` are relative to this content root after removing that prefix. + +## Persistence + +All hosts use schema version 1 at `/.foreman//state.json`. Keep this file private and outside version control. The default founder ID for the local CLI is `default`. For multiple founders, pass an explicit ID on every call; never infer another founder's records. OpenClaw scopes data by its trusted agent and sender context. To share an existing agent-only store with the CLI, pass that agent ID as `--founder`. + +Run `node "/runtime/run.mjs" --workspace "" --founder default ...`. Substitute real absolute paths and shell-quote each argument. User text is data; never interpolate it as executable shell syntax. This runtime needs Node 22.19 or later, and no package install or network connection. Check its exit status and returned JSON. Do not edit `state.json` directly. + +Read profile: `profile`. Set `/solo`: `profile --mode solo`; `/solo off`: `profile --mode standard`. Set `/stoic`: `profile --stoic on`; off uses `off`. Set `/language tr`: `profile --language tr`; default uses `en`; status only reads. `/sector saas` uses `profile --sector saas`. Always read persisted settings at the start of a new session. + +Read tasks: `track --filter all` (also `active`, `overdue`, `stalled`, or any of the six statuses). Add a confirmed task: `task --id impl-001 --description "Interview five customers" --deadline 2026-10-01`. Update `/progress impl-001 40 note`: `task --id impl-001 --progress 40 --note "note"`. Status changes use `--status not-started|in-progress|blocked|completed|abandoned|deferred`. A completed task has progress 100. Use `--revision N` when editing a previously read revision; a conflict requires rereading, not overwriting. + +After a confirmed playbook step, save the next step: `resume --playbook pivot-playbook --step 2`. Read `resume` to continue from that checkpoint; verify the playbook and step against the catalog before writing. The exposed Claude command is `/foreman-resume`, because `/resume` is a host command. Never mark a step complete based merely on a generated recommendation. + +If the runtime or workspace is unavailable, explain that persistence is unavailable and keep the session usable. Do not fabricate saved tasks. Do not run a package installer automatically to enable persistence. + +## Schema and legacy migration + +Canonical preferences are `identity.mode` (`standard|solo`), `identity.stoic_mode` (boolean), `identity.language` (language code or name), and `company.sector`. Tasks are `implementation_items`; the checkpoint is `active.playbook: {id, next_step}` or null. Every record has `schema_version: 1`, `founder_id`, `revision` and `history`. + +Legacy YAML memory remains readable source material. To migrate, read the user's existing identity/company/active/history files, assemble their parsed contents into one JSON object in a temporary file, and run `migrate --input ""`. Migrate into an unused founder destination only. The runtime normalizes `mode_solo`, `mode_stoic`, and `preferences` and preserves the original object under `legacy`. A validation error leaves the destination unchanged. Keep original files until the user has verified the result. Never silently reset a malformed or newer state file. + +## Host commands + +Claude project commands are the files in `commands/`; names that conflict with built-ins use the `foreman-` prefix. Use `/foreman-run` for playbooks and `/foreman-skill` for skill previews. The latter also avoids a `skill.md` / `SKILL.md` filesystem collision that hides sibling commands. Plugin commands use `/foreman:NAME`. Consult `catalog.json` for the exact map. In Codex, invoke `$foreman` with the requested operation or use an individual framework skill. Do not advertise Claude slash commands as Codex commands. diff --git a/.claude/agents/_schema/agent-template.md b/.claude/_schema/agents/agent-template.md similarity index 100% rename from .claude/agents/_schema/agent-template.md rename to .claude/_schema/agents/agent-template.md diff --git a/.claude/commands/_schema/command-template.md b/.claude/_schema/commands/command-template.md similarity index 100% rename from .claude/commands/_schema/command-template.md rename to .claude/_schema/commands/command-template.md diff --git a/.claude/catalog-aliases.json b/.claude/catalog-aliases.json new file mode 100644 index 0000000..0d52f6a --- /dev/null +++ b/.claude/catalog-aliases.json @@ -0,0 +1,30 @@ +{ + "skill": { + "swot-analysis": "swot-pest-analysis", + "swot": "swot-pest-analysis", + "kaizen": "kaizen-bpr", + "tuckman-stages": "tuckman-team-stages", + "nps": "net-promoter-score" + }, + "diagnostic": { + "team": "team-dysfunction-diagnosis", + "product": "product-market-fit-diagnosis", + "culture": "culture-erosion-diagnosis", + "competition": "competitive-threat-diagnosis", + "churn": "customer-churn-diagnosis", + "cofounder": "cofounder-conflict-diagnosis", + "communication": "communication-breakdown-diagnosis", + "decisions": "decision-paralysis-diagnosis", + "operations": "operational-chaos-diagnosis", + "strategy": "strategic-drift-diagnosis" + }, + "research": { + "customer-interviews": "customer-interview-guide", + "market-sizing": "market-sizing-worksheet", + "competitor-analysis": "competitor-research-template", + "financial-modeling": "financial-modeling-guide", + "funding-landscape": "funding-landscape-research", + "technology-stack": "technology-stack-research", + "regulatory-landscape": "regulatory-landscape-research" + } +} diff --git a/.claude/catalog.json b/.claude/catalog.json new file mode 100644 index 0000000..ec875f5 --- /dev/null +++ b/.claude/catalog.json @@ -0,0 +1,1872 @@ +{ + "entries": [ + { + "id": "diagnostic-agent", + "kind": "agent", + "path": "agents/diagnostic-agent.md" + }, + { + "id": "memory-agent", + "kind": "agent", + "path": "agents/memory-agent.md" + }, + { + "id": "orchestrator-agent", + "kind": "agent", + "path": "agents/orchestrator-agent.md" + }, + { + "id": "output-agent", + "kind": "agent", + "path": "agents/output-agent.md" + }, + { + "id": "playbook-runner-agent", + "kind": "agent", + "path": "agents/playbook-runner-agent.md" + }, + { + "id": "skill-executor-agent", + "kind": "agent", + "path": "agents/skill-executor-agent.md" + }, + { + "id": "execution-commands", + "kind": "command", + "path": "commands/execution-commands.md", + "category": "execution" + }, + { + "id": "implementation-commands", + "kind": "command", + "path": "commands/implementation-commands.md", + "category": "implementation" + }, + { + "id": "language-mode-commands", + "kind": "command", + "path": "commands/language-command.md", + "category": "meta" + }, + { + "id": "memory-commands", + "kind": "command", + "path": "commands/memory-commands.md", + "category": "memory" + }, + { + "id": "navigation-commands", + "kind": "command", + "path": "commands/navigation-commands.md", + "category": "navigation" + }, + { + "id": "org-politics-commands", + "kind": "command", + "path": "commands/org-politics-commands.md", + "category": "org-politics" + }, + { + "id": "research-commands", + "kind": "command", + "path": "commands/research-commands.md", + "category": "research" + }, + { + "id": "simulation-commands", + "kind": "command", + "path": "commands/simulation-commands.md", + "category": "simulation" + }, + { + "id": "stoic-mode-commands", + "kind": "command", + "path": "commands/stoic-command.md", + "category": "meta" + }, + { + "id": "cofounder-conflict-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/cofounder-conflict-diagnosis.md" + }, + { + "id": "communication-breakdown-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/communication-breakdown-diagnosis.md" + }, + { + "id": "competitive-threat-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/competitive-threat-diagnosis.md" + }, + { + "id": "culture-erosion-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/culture-erosion-diagnosis.md" + }, + { + "id": "customer-churn-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/customer-churn-diagnosis.md" + }, + { + "id": "decision-paralysis-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/decision-paralysis-diagnosis.md" + }, + { + "id": "fundraising-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/fundraising-diagnosis.md" + }, + { + "id": "growth-stall-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/growth-stall-diagnosis.md" + }, + { + "id": "hiring-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/hiring-diagnosis.md" + }, + { + "id": "innovation-drought-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/innovation-drought-diagnosis.md" + }, + { + "id": "leadership-crisis-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/leadership-crisis-diagnosis.md" + }, + { + "id": "market-entry-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/market-entry-diagnosis.md" + }, + { + "id": "negotiation-stuck-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/negotiation-stuck-diagnosis.md" + }, + { + "id": "operational-chaos-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/operational-chaos-diagnosis.md" + }, + { + "id": "partnership-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/partnership-diagnosis.md" + }, + { + "id": "pricing-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/pricing-diagnosis.md" + }, + { + "id": "product-market-fit-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/product-market-fit-diagnosis.md" + }, + { + "id": "revenue-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/revenue-diagnosis.md" + }, + { + "id": "strategic-drift-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/strategic-drift-diagnosis.md" + }, + { + "id": "team-dysfunction-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/team-dysfunction-diagnosis.md" + }, + { + "id": "communication-hook", + "kind": "hook", + "path": "hooks/communication-hook.md" + }, + { + "id": "competition-hook", + "kind": "hook", + "path": "hooks/competition-hook.md" + }, + { + "id": "culture-hook", + "kind": "hook", + "path": "hooks/culture-hook.md" + }, + { + "id": "decision-hook", + "kind": "hook", + "path": "hooks/decision-hook.md" + }, + { + "id": "fundraising-hook", + "kind": "hook", + "path": "hooks/fundraising-hook.md" + }, + { + "id": "growth-hook", + "kind": "hook", + "path": "hooks/growth-hook.md" + }, + { + "id": "innovation-hook", + "kind": "hook", + "path": "hooks/innovation-hook.md" + }, + { + "id": "launch-hook", + "kind": "hook", + "path": "hooks/launch-hook.md" + }, + { + "id": "leadership-hook", + "kind": "hook", + "path": "hooks/leadership-hook.md" + }, + { + "id": "negotiation-hook", + "kind": "hook", + "path": "hooks/negotiation-hook.md" + }, + { + "id": "partnership-hook", + "kind": "hook", + "path": "hooks/partnership-hook.md" + }, + { + "id": "personal-growth-hook", + "kind": "hook", + "path": "hooks/personal-growth-hook.md" + }, + { + "id": "product-hook", + "kind": "hook", + "path": "hooks/product-hook.md" + }, + { + "id": "research-hook", + "kind": "hook", + "path": "hooks/research-hook.md" + }, + { + "id": "revenue-and-sales-hook", + "kind": "hook", + "path": "hooks/revenue-and-sales-hook.md" + }, + { + "id": "strategy-hook", + "kind": "hook", + "path": "hooks/strategy-hook.md" + }, + { + "id": "team-hook", + "kind": "hook", + "path": "hooks/team-hook.md" + }, + { + "id": "implementation-tracking", + "kind": "implementation", + "path": "implementation/IMPLEMENTATION.md" + }, + { + "id": "blocker-diagnosis", + "kind": "diagnostic", + "path": "implementation/support/blocker-diagnosis.md" + }, + { + "id": "implementation-retrospective", + "kind": "template", + "path": "implementation/support/implementation-retrospective.md" + }, + { + "id": "blocker-analysis", + "kind": "template", + "path": "implementation/templates/blocker-analysis.md" + }, + { + "id": "implementation-dashboard", + "kind": "template", + "path": "implementation/templates/implementation-dashboard.md" + }, + { + "id": "weekly-progress-report", + "kind": "template", + "path": "implementation/templates/weekly-progress-report.md" + }, + { + "id": "organizational-alignment-playbook", + "kind": "playbook", + "path": "org-politics/organizational-alignment-playbook.md", + "category": "playbooks" + }, + { + "id": "power-dynamics-diagnosis", + "kind": "diagnostic", + "path": "org-politics/power-dynamics-diagnosis.md" + }, + { + "id": "stakeholder-resistance-diagnosis", + "kind": "diagnostic", + "path": "org-politics/stakeholder-resistance-diagnosis.md" + }, + { + "id": "coalition-building-plan", + "kind": "template", + "path": "org-politics/templates/coalition-building-plan.md" + }, + { + "id": "communication-strategy-map", + "kind": "template", + "path": "org-politics/templates/communication-strategy-map.md" + }, + { + "id": "negotiation-position-map", + "kind": "template", + "path": "org-politics/templates/negotiation-position-map.md" + }, + { + "id": "political-risk-assessment", + "kind": "template", + "path": "org-politics/templates/political-risk-assessment.md" + }, + { + "id": "resistance-management-plan", + "kind": "template", + "path": "org-politics/templates/resistance-management-plan.md" + }, + { + "id": "stakeholder-influence-map", + "kind": "template", + "path": "org-politics/templates/stakeholder-influence-map.md" + }, + { + "id": "board-meeting-agenda", + "kind": "template", + "path": "output-templates/board/board-meeting-agenda.md" + }, + { + "id": "ceo-succession-brief", + "kind": "template", + "path": "output-templates/board/ceo-succession-brief.md" + }, + { + "id": "change-initiative-proposal", + "kind": "template", + "path": "output-templates/board/change-initiative-proposal.md" + }, + { + "id": "compensation-review-brief", + "kind": "template", + "path": "output-templates/board/compensation-review-brief.md" + }, + { + "id": "quarterly-strategic-review", + "kind": "template", + "path": "output-templates/board/quarterly-strategic-review.md" + }, + { + "id": "regulatory-compliance-update", + "kind": "template", + "path": "output-templates/board/regulatory-compliance-update.md" + }, + { + "id": "risk-assessment-brief", + "kind": "template", + "path": "output-templates/board/risk-assessment-brief.md" + }, + { + "id": "analysis-report", + "kind": "template", + "path": "output-templates/client/analysis-report.md" + }, + { + "id": "case-study-template", + "kind": "template", + "path": "output-templates/client/case-study-template.md" + }, + { + "id": "onboarding-welcome-packet", + "kind": "template", + "path": "output-templates/client/onboarding-welcome-packet.md" + }, + { + "id": "partnership-memo", + "kind": "template", + "path": "output-templates/client/partnership-memo.md" + }, + { + "id": "project-status-update", + "kind": "template", + "path": "output-templates/client/project-status-update.md" + }, + { + "id": "proposal-outline", + "kind": "template", + "path": "output-templates/client/proposal-outline.md" + }, + { + "id": "quarterly-business-review", + "kind": "template", + "path": "output-templates/client/quarterly-business-review.md" + }, + { + "id": "service-level-agreement", + "kind": "template", + "path": "output-templates/client/service-level-agreement.md" + }, + { + "id": "cap-table-summary", + "kind": "template", + "path": "output-templates/investor/cap-table-summary.md" + }, + { + "id": "competitive-landscape-brief", + "kind": "template", + "path": "output-templates/investor/competitive-landscape-brief.md" + }, + { + "id": "decision-rationale-memo", + "kind": "template", + "path": "output-templates/investor/decision-rationale-memo.md" + }, + { + "id": "due-diligence-checklist", + "kind": "template", + "path": "output-templates/investor/due-diligence-checklist.md" + }, + { + "id": "exit-scenario-analysis", + "kind": "template", + "path": "output-templates/investor/exit-scenario-analysis.md" + }, + { + "id": "fundraising-deck-outline", + "kind": "template", + "path": "output-templates/investor/fundraising-deck-outline.md" + }, + { + "id": "investor-update-email", + "kind": "template", + "path": "output-templates/investor/investor-update-email.md" + }, + { + "id": "market-opportunity-summary", + "kind": "template", + "path": "output-templates/investor/market-opportunity-summary.md" + }, + { + "id": "strategic-analysis-one-pager", + "kind": "template", + "path": "output-templates/investor/strategic-analysis-one-pager.md" + }, + { + "id": "unit-economics-snapshot", + "kind": "template", + "path": "output-templates/investor/unit-economics-snapshot.md" + }, + { + "id": "annual-review-and-planning", + "kind": "template", + "path": "output-templates/self/annual-review-and-planning.md" + }, + { + "id": "career-strategy-canvas", + "kind": "template", + "path": "output-templates/self/career-strategy-canvas.md" + }, + { + "id": "decision-journal", + "kind": "template", + "path": "output-templates/self/decision-journal.md" + }, + { + "id": "founder-mental-health-check", + "kind": "template", + "path": "output-templates/self/founder-mental-health-check.md" + }, + { + "id": "leadership-reflection", + "kind": "template", + "path": "output-templates/self/leadership-reflection.md" + }, + { + "id": "learning-plan", + "kind": "template", + "path": "output-templates/self/learning-plan.md" + }, + { + "id": "negotiation-prep-sheet", + "kind": "template", + "path": "output-templates/self/negotiation-prep-sheet.md" + }, + { + "id": "personal-board-tracker", + "kind": "template", + "path": "output-templates/self/personal-board-tracker.md" + }, + { + "id": "stakeholder-map", + "kind": "template", + "path": "output-templates/self/stakeholder-map.md" + }, + { + "id": "weekly-ceo-review", + "kind": "template", + "path": "output-templates/self/weekly-ceo-review.md" + }, + { + "id": "action-plan", + "kind": "template", + "path": "output-templates/team/action-plan.md" + }, + { + "id": "culture-values-document", + "kind": "template", + "path": "output-templates/team/culture-values-document.md" + }, + { + "id": "feedback-360-template", + "kind": "template", + "path": "output-templates/team/feedback-360-template.md" + }, + { + "id": "hiring-scorecard", + "kind": "template", + "path": "output-templates/team/hiring-scorecard.md" + }, + { + "id": "incident-postmortem", + "kind": "template", + "path": "output-templates/team/incident-postmortem.md" + }, + { + "id": "meeting-notes-template", + "kind": "template", + "path": "output-templates/team/meeting-notes-template.md" + }, + { + "id": "new-initiative-brief", + "kind": "template", + "path": "output-templates/team/new-initiative-brief.md" + }, + { + "id": "offsite-planning-guide", + "kind": "template", + "path": "output-templates/team/offsite-planning-guide.md" + }, + { + "id": "one-on-one-template", + "kind": "template", + "path": "output-templates/team/one-on-one-template.md" + }, + { + "id": "project-kickoff-document", + "kind": "template", + "path": "output-templates/team/project-kickoff-document.md" + }, + { + "id": "retrospective-template", + "kind": "template", + "path": "output-templates/team/retrospective-template.md" + }, + { + "id": "role-description-template", + "kind": "template", + "path": "output-templates/team/role-description-template.md" + }, + { + "id": "team-health-check", + "kind": "template", + "path": "output-templates/team/team-health-check.md" + }, + { + "id": "acquisition-evaluation-playbook", + "kind": "playbook", + "path": "playbooks/acquisition-evaluation-playbook.md" + }, + { + "id": "board-formation-playbook", + "kind": "playbook", + "path": "playbooks/board-formation-playbook.md" + }, + { + "id": "competitive-response-playbook", + "kind": "playbook", + "path": "playbooks/competitive-response-playbook.md", + "category": "playbooks" + }, + { + "id": "crisis-playbook", + "kind": "playbook", + "path": "playbooks/crisis-playbook.md" + }, + { + "id": "first-100-customers-playbook", + "kind": "playbook", + "path": "playbooks/first-100-customers-playbook.md" + }, + { + "id": "founder-transition-playbook", + "kind": "playbook", + "path": "playbooks/founder-transition-playbook.md", + "category": "playbooks" + }, + { + "id": "fundraising-playbook", + "kind": "playbook", + "path": "playbooks/fundraising-playbook.md" + }, + { + "id": "innovation-sprint-playbook", + "kind": "playbook", + "path": "playbooks/innovation-sprint-playbook.md", + "category": "playbooks" + }, + { + "id": "international-expansion-playbook", + "kind": "playbook", + "path": "playbooks/international-expansion-playbook.md", + "category": "playbooks" + }, + { + "id": "launch-playbook", + "kind": "playbook", + "path": "playbooks/launch-playbook.md" + }, + { + "id": "negotiation-playbook", + "kind": "playbook", + "path": "playbooks/negotiation-playbook.md", + "category": "playbooks" + }, + { + "id": "partnership-playbook", + "kind": "playbook", + "path": "playbooks/partnership-playbook.md", + "category": "playbooks" + }, + { + "id": "personal-brand-playbook", + "kind": "playbook", + "path": "playbooks/personal-brand-playbook.md", + "category": "playbooks" + }, + { + "id": "pivot-playbook", + "kind": "playbook", + "path": "playbooks/pivot-playbook.md" + }, + { + "id": "pricing-strategy-playbook", + "kind": "playbook", + "path": "playbooks/pricing-strategy-playbook.md" + }, + { + "id": "product-market-fit-playbook", + "kind": "playbook", + "path": "playbooks/product-market-fit-playbook.md", + "category": "playbooks" + }, + { + "id": "remote-team-playbook", + "kind": "playbook", + "path": "playbooks/remote-team-playbook.md", + "category": "playbooks" + }, + { + "id": "scaling-playbook", + "kind": "playbook", + "path": "playbooks/scaling-playbook.md", + "category": "playbooks" + }, + { + "id": "strategy-reset-playbook", + "kind": "playbook", + "path": "playbooks/strategy-reset-playbook.md", + "category": "playbooks" + }, + { + "id": "team-rebuild-playbook", + "kind": "playbook", + "path": "playbooks/team-rebuild-playbook.md", + "category": "playbooks" + }, + { + "id": "brand-perception-research", + "kind": "research", + "path": "research/brand-perception-research.md" + }, + { + "id": "churn-analysis-guide", + "kind": "research", + "path": "research/churn-analysis-guide.md" + }, + { + "id": "competitor-research-template", + "kind": "research", + "path": "research/competitor-research-template.md" + }, + { + "id": "content-strategy-research", + "kind": "research", + "path": "research/content-strategy-research.md" + }, + { + "id": "customer-interview-guide", + "kind": "research", + "path": "research/customer-interview-guide.md" + }, + { + "id": "data-collection-plan", + "kind": "research", + "path": "research/data-collection-plan.md" + }, + { + "id": "due-diligence-research", + "kind": "research", + "path": "research/due-diligence-research.md" + }, + { + "id": "financial-modeling-guide", + "kind": "research", + "path": "research/financial-modeling-guide.md" + }, + { + "id": "funding-landscape-research", + "kind": "research", + "path": "research/funding-landscape-research.md" + }, + { + "id": "industry-mapping-guide", + "kind": "research", + "path": "research/industry-mapping-guide.md" + }, + { + "id": "market-sizing-worksheet", + "kind": "research", + "path": "research/market-sizing-worksheet.md" + }, + { + "id": "partnership-research-guide", + "kind": "research", + "path": "research/partnership-research-guide.md" + }, + { + "id": "pricing-research-guide", + "kind": "research", + "path": "research/pricing-research-guide.md" + }, + { + "id": "regulatory-landscape-research", + "kind": "research", + "path": "research/regulatory-landscape-research.md" + }, + { + "id": "survey-design-guide", + "kind": "research", + "path": "research/survey-design-guide.md" + }, + { + "id": "talent-market-research", + "kind": "research", + "path": "research/talent-market-research.md" + }, + { + "id": "technology-stack-research", + "kind": "research", + "path": "research/technology-stack-research.md" + }, + { + "id": "user-testing-protocol", + "kind": "research", + "path": "research/user-testing-protocol.md" + }, + { + "id": "culture-guardian", + "kind": "persona", + "path": "simulation/board-personas/culture-guardian.md" + }, + { + "id": "customer-advocate", + "kind": "persona", + "path": "simulation/board-personas/customer-advocate.md" + }, + { + "id": "financial-hawk", + "kind": "persona", + "path": "simulation/board-personas/financial-hawk.md" + }, + { + "id": "friendly-challenger", + "kind": "persona", + "path": "simulation/board-personas/friendly-challenger.md" + }, + { + "id": "growth-strategist", + "kind": "persona", + "path": "simulation/board-personas/growth-strategist.md" + }, + { + "id": "industry-veteran", + "kind": "persona", + "path": "simulation/board-personas/industry-veteran.md" + }, + { + "id": "legal-counsel", + "kind": "persona", + "path": "simulation/board-personas/legal-counsel.md" + }, + { + "id": "operational-expert", + "kind": "persona", + "path": "simulation/board-personas/operational-expert.md" + }, + { + "id": "skeptic-investor", + "kind": "persona", + "path": "simulation/board-personas/skeptic-investor.md" + }, + { + "id": "technical-advisor", + "kind": "persona", + "path": "simulation/board-personas/technical-advisor.md" + }, + { + "id": "post-simulation-diagnostic", + "kind": "diagnostic", + "path": "simulation/post-simulation-diagnostic.md" + }, + { + "id": "ai-augmentation-not-automation", + "kind": "skill", + "path": "skills/ai-leadership/ai-augmentation-not-automation.md", + "category": "ai-leadership" + }, + { + "id": "ai-communication-culture", + "kind": "skill", + "path": "skills/ai-leadership/ai-communication-culture.md", + "category": "ai-leadership" + }, + { + "id": "ai-emotional-intelligence", + "kind": "skill", + "path": "skills/ai-leadership/ai-emotional-intelligence.md", + "category": "ai-leadership" + }, + { + "id": "ai-human-centered-approach", + "kind": "skill", + "path": "skills/ai-leadership/ai-human-centered-approach.md", + "category": "ai-leadership" + }, + { + "id": "ai-inclusive-collaboration", + "kind": "skill", + "path": "skills/ai-leadership/ai-inclusive-collaboration.md", + "category": "ai-leadership" + }, + { + "id": "ai-learning-for-leaders", + "kind": "skill", + "path": "skills/ai-leadership/ai-learning-for-leaders.md", + "category": "ai-leadership" + }, + { + "id": "ai-purpose-driven-questions", + "kind": "skill", + "path": "skills/ai-leadership/ai-purpose-driven-questions.md", + "category": "ai-leadership" + }, + { + "id": "ai-stakeholder-balance", + "kind": "skill", + "path": "skills/ai-leadership/ai-stakeholder-balance.md", + "category": "ai-leadership" + }, + { + "id": "ai-vision-and-strategy", + "kind": "skill", + "path": "skills/ai-leadership/ai-vision-and-strategy.md", + "category": "ai-leadership" + }, + { + "id": "creative-collaboration-and-context", + "kind": "skill", + "path": "skills/creative/creative-collaboration-and-context.md", + "category": "creative" + }, + { + "id": "creative-completion-and-renewal", + "kind": "skill", + "path": "skills/creative/creative-completion-and-renewal.md", + "category": "creative" + }, + { + "id": "creative-flow-and-inspiration", + "kind": "skill", + "path": "skills/creative/creative-flow-and-inspiration.md", + "category": "creative" + }, + { + "id": "creative-identity-and-purpose", + "kind": "skill", + "path": "skills/creative/creative-identity-and-purpose.md", + "category": "creative" + }, + { + "id": "creative-obstacles", + "kind": "skill", + "path": "skills/creative/creative-obstacles.md", + "category": "creative" + }, + { + "id": "creative-perception-and-awareness", + "kind": "skill", + "path": "skills/creative/creative-perception-and-awareness.md", + "category": "creative" + }, + { + "id": "creative-practice-and-habit", + "kind": "skill", + "path": "skills/creative/creative-practice-and-habit.md", + "category": "creative" + }, + { + "id": "creative-shaping-and-craft", + "kind": "skill", + "path": "skills/creative/creative-shaping-and-craft.md", + "category": "creative" + }, + { + "id": "choosing-and-executing", + "kind": "skill", + "path": "skills/decisions/choosing-and-executing.md", + "category": "decisions" + }, + { + "id": "decision-traps-and-roles", + "kind": "skill", + "path": "skills/decisions/decision-traps-and-roles.md", + "category": "decisions" + }, + { + "id": "evaluating-options", + "kind": "skill", + "path": "skills/decisions/evaluating-options.md", + "category": "decisions" + }, + { + "id": "generating-solutions", + "kind": "skill", + "path": "skills/decisions/generating-solutions.md", + "category": "decisions" + }, + { + "id": "tough-decision-situations", + "kind": "skill", + "path": "skills/decisions/tough-decision-situations.md", + "category": "decisions" + }, + { + "id": "ambidexterity", + "kind": "skill", + "path": "skills/frameworks/ambidexterity.md", + "category": "frameworks" + }, + { + "id": "appreciative-inquiry", + "kind": "skill", + "path": "skills/frameworks/appreciative-inquiry.md", + "category": "frameworks" + }, + { + "id": "art-of-war", + "kind": "skill", + "path": "skills/frameworks/art-of-war.md", + "category": "frameworks" + }, + { + "id": "balanced-scorecard", + "kind": "skill", + "path": "skills/frameworks/balanced-scorecard.md", + "category": "frameworks" + }, + { + "id": "belbin-team-roles", + "kind": "skill", + "path": "skills/frameworks/belbin-team-roles.md", + "category": "frameworks" + }, + { + "id": "black-swans", + "kind": "skill", + "path": "skills/frameworks/black-swans.md", + "category": "frameworks" + }, + { + "id": "blue-ocean-strategy", + "kind": "skill", + "path": "skills/frameworks/blue-ocean-strategy.md", + "category": "frameworks" + }, + { + "id": "business-model-canvas", + "kind": "skill", + "path": "skills/frameworks/business-model-canvas.md", + "category": "frameworks" + }, + { + "id": "carnegie-win-friends", + "kind": "skill", + "path": "skills/frameworks/carnegie-win-friends.md", + "category": "frameworks" + }, + { + "id": "cialdini-influence", + "kind": "skill", + "path": "skills/frameworks/cialdini-influence.md", + "category": "frameworks" + }, + { + "id": "covey-seven-habits", + "kind": "skill", + "path": "skills/frameworks/covey-seven-habits.md", + "category": "frameworks" + }, + { + "id": "disruptive-innovation", + "kind": "skill", + "path": "skills/frameworks/disruptive-innovation.md", + "category": "frameworks" + }, + { + "id": "doblin-ten-types", + "kind": "skill", + "path": "skills/frameworks/doblin-ten-types.md", + "category": "frameworks" + }, + { + "id": "eisenhower-matrix", + "kind": "skill", + "path": "skills/frameworks/eisenhower-matrix.md", + "category": "frameworks" + }, + { + "id": "emotional-intelligence", + "kind": "skill", + "path": "skills/frameworks/emotional-intelligence.md", + "category": "frameworks" + }, + { + "id": "flow-state", + "kind": "skill", + "path": "skills/frameworks/flow-state.md", + "category": "frameworks" + }, + { + "id": "four-ps-marketing", + "kind": "skill", + "path": "skills/frameworks/four-ps-marketing.md", + "category": "frameworks" + }, + { + "id": "giving-feedback", + "kind": "skill", + "path": "skills/frameworks/giving-feedback.md", + "category": "frameworks" + }, + { + "id": "grow-model", + "kind": "skill", + "path": "skills/frameworks/grow-model.md", + "category": "frameworks" + }, + { + "id": "growth-mindset", + "kind": "skill", + "path": "skills/frameworks/growth-mindset.md", + "category": "frameworks" + }, + { + "id": "growth-share-matrix", + "kind": "skill", + "path": "skills/frameworks/growth-share-matrix.md", + "category": "frameworks" + }, + { + "id": "hackman-enabling-conditions", + "kind": "skill", + "path": "skills/frameworks/hackman-enabling-conditions.md", + "category": "frameworks" + }, + { + "id": "johari-window", + "kind": "skill", + "path": "skills/frameworks/johari-window.md", + "category": "frameworks" + }, + { + "id": "kaizen-bpr", + "kind": "skill", + "path": "skills/frameworks/kaizen-bpr.md", + "category": "frameworks" + }, + { + "id": "kotter-change-model", + "kind": "skill", + "path": "skills/frameworks/kotter-change-model.md", + "category": "frameworks" + }, + { + "id": "leadership-pipeline", + "kind": "skill", + "path": "skills/frameworks/leadership-pipeline.md", + "category": "frameworks" + }, + { + "id": "lean-in", + "kind": "skill", + "path": "skills/frameworks/lean-in.md", + "category": "frameworks" + }, + { + "id": "lewin-leadership-styles", + "kind": "skill", + "path": "skills/frameworks/lewin-leadership-styles.md", + "category": "frameworks" + }, + { + "id": "maslow-hierarchy", + "kind": "skill", + "path": "skills/frameworks/maslow-hierarchy.md", + "category": "frameworks" + }, + { + "id": "myers-briggs-type-indicator", + "kind": "skill", + "path": "skills/frameworks/myers-briggs-type-indicator.md", + "category": "frameworks" + }, + { + "id": "net-promoter-score", + "kind": "skill", + "path": "skills/frameworks/net-promoter-score.md", + "category": "frameworks" + }, + { + "id": "neuro-linguistic-programming", + "kind": "skill", + "path": "skills/frameworks/neuro-linguistic-programming.md", + "category": "frameworks" + }, + { + "id": "organisational-culture", + "kind": "skill", + "path": "skills/frameworks/organisational-culture.md", + "category": "frameworks" + }, + { + "id": "porters-five-forces", + "kind": "skill", + "path": "skills/frameworks/porters-five-forces.md", + "category": "frameworks" + }, + { + "id": "product-life-cycle", + "kind": "skill", + "path": "skills/frameworks/product-life-cycle.md", + "category": "frameworks" + }, + { + "id": "psychological-safety", + "kind": "skill", + "path": "skills/frameworks/psychological-safety.md", + "category": "frameworks" + }, + { + "id": "radical-candor", + "kind": "skill", + "path": "skills/frameworks/radical-candor.md", + "category": "frameworks" + }, + { + "id": "scenario-planning", + "kind": "skill", + "path": "skills/frameworks/scenario-planning.md", + "category": "frameworks" + }, + { + "id": "shamrock-organisation", + "kind": "skill", + "path": "skills/frameworks/shamrock-organisation.md", + "category": "frameworks" + }, + { + "id": "situational-leadership", + "kind": "skill", + "path": "skills/frameworks/situational-leadership.md", + "category": "frameworks" + }, + { + "id": "smart-goals", + "kind": "skill", + "path": "skills/frameworks/smart-goals.md", + "category": "frameworks" + }, + { + "id": "swot-pest-analysis", + "kind": "skill", + "path": "skills/frameworks/swot-pest-analysis.md", + "category": "frameworks" + }, + { + "id": "systems-thinking", + "kind": "skill", + "path": "skills/frameworks/systems-thinking.md", + "category": "frameworks" + }, + { + "id": "thinking-fast-and-slow", + "kind": "skill", + "path": "skills/frameworks/thinking-fast-and-slow.md", + "category": "frameworks" + }, + { + "id": "thomas-kilmann-conflict", + "kind": "skill", + "path": "skills/frameworks/thomas-kilmann-conflict.md", + "category": "frameworks" + }, + { + "id": "tipping-point", + "kind": "skill", + "path": "skills/frameworks/tipping-point.md", + "category": "frameworks" + }, + { + "id": "trust-equation", + "kind": "skill", + "path": "skills/frameworks/trust-equation.md", + "category": "frameworks" + }, + { + "id": "tuckman-team-stages", + "kind": "skill", + "path": "skills/frameworks/tuckman-team-stages.md", + "category": "frameworks" + }, + { + "id": "vuca-framework", + "kind": "skill", + "path": "skills/frameworks/vuca-framework.md", + "category": "frameworks" + }, + { + "id": "win-win-negotiation", + "kind": "skill", + "path": "skills/frameworks/win-win-negotiation.md", + "category": "frameworks" + }, + { + "id": "coalition-and-partnership-games", + "kind": "skill", + "path": "skills/game-theory/coalition-and-partnership-games.md", + "category": "game-theory" + }, + { + "id": "evolutionary-strategy", + "kind": "skill", + "path": "skills/game-theory/evolutionary-strategy.md", + "category": "game-theory" + }, + { + "id": "first-mover-strategy", + "kind": "skill", + "path": "skills/game-theory/first-mover-strategy.md", + "category": "game-theory" + }, + { + "id": "game-theory-fundamentals", + "kind": "skill", + "path": "skills/game-theory/game-theory-fundamentals.md", + "category": "game-theory" + }, + { + "id": "information-asymmetry", + "kind": "skill", + "path": "skills/game-theory/information-asymmetry.md", + "category": "game-theory" + }, + { + "id": "negotiation-game-theory", + "kind": "skill", + "path": "skills/game-theory/negotiation-game-theory.md", + "category": "game-theory" + }, + { + "id": "prisoners-dilemma-and-cooperation", + "kind": "skill", + "path": "skills/game-theory/prisoners-dilemma-and-cooperation.md", + "category": "game-theory" + }, + { + "id": "ai-era-leadership", + "kind": "skill", + "path": "skills/leadership/ai-era-leadership.md", + "category": "leadership" + }, + { + "id": "business-writing-for-leaders", + "kind": "skill", + "path": "skills/leadership/business-writing-for-leaders.md", + "category": "leadership" + }, + { + "id": "career-strategy-for-leaders", + "kind": "skill", + "path": "skills/leadership/career-strategy-for-leaders.md", + "category": "leadership" + }, + { + "id": "decision-making-under-pressure", + "kind": "skill", + "path": "skills/leadership/decision-making-under-pressure.md", + "category": "leadership" + }, + { + "id": "delegation-and-empowerment", + "kind": "skill", + "path": "skills/leadership/delegation-and-empowerment.md", + "category": "leadership" + }, + { + "id": "emotional-courage", + "kind": "skill", + "path": "skills/leadership/emotional-courage.md", + "category": "leadership" + }, + { + "id": "employee-engagement-retention", + "kind": "skill", + "path": "skills/leadership/employee-engagement-retention.md", + "category": "leadership" + }, + { + "id": "focus-and-priority-management", + "kind": "skill", + "path": "skills/leadership/focus-and-priority-management.md", + "category": "leadership" + }, + { + "id": "humility-and-power", + "kind": "skill", + "path": "skills/leadership/humility-and-power.md", + "category": "leadership" + }, + { + "id": "inclusive-leadership", + "kind": "skill", + "path": "skills/leadership/inclusive-leadership.md", + "category": "leadership" + }, + { + "id": "introvert-leadership", + "kind": "skill", + "path": "skills/leadership/introvert-leadership.md", + "category": "leadership" + }, + { + "id": "leader-resilience-and-wellbeing", + "kind": "skill", + "path": "skills/leadership/leader-resilience-and-wellbeing.md", + "category": "leadership" + }, + { + "id": "leader-self-reflection", + "kind": "skill", + "path": "skills/leadership/leader-self-reflection.md", + "category": "leadership" + }, + { + "id": "leadership-style-adaptation", + "kind": "skill", + "path": "skills/leadership/leadership-style-adaptation.md", + "category": "leadership" + }, + { + "id": "leadership-voice-and-presence", + "kind": "skill", + "path": "skills/leadership/leadership-voice-and-presence.md", + "category": "leadership" + }, + { + "id": "leading-through-change", + "kind": "skill", + "path": "skills/leadership/leading-through-change.md", + "category": "leadership" + }, + { + "id": "learning-agility", + "kind": "skill", + "path": "skills/leadership/learning-agility.md", + "category": "leadership" + }, + { + "id": "learning-from-failure", + "kind": "skill", + "path": "skills/leadership/learning-from-failure.md", + "category": "leadership" + }, + { + "id": "managing-up", + "kind": "skill", + "path": "skills/leadership/managing-up.md", + "category": "leadership" + }, + { + "id": "mentoring-and-coaching", + "kind": "skill", + "path": "skills/leadership/mentoring-and-coaching.md", + "category": "leadership" + }, + { + "id": "persuasion-and-influence", + "kind": "skill", + "path": "skills/leadership/persuasion-and-influence.md", + "category": "leadership" + }, + { + "id": "psychological-safety-practice", + "kind": "skill", + "path": "skills/leadership/psychological-safety-practice.md", + "category": "leadership" + }, + { + "id": "purpose-driven-leadership", + "kind": "skill", + "path": "skills/leadership/purpose-driven-leadership.md", + "category": "leadership" + }, + { + "id": "senior-leadership-transition", + "kind": "skill", + "path": "skills/leadership/senior-leadership-transition.md", + "category": "leadership" + }, + { + "id": "storytelling-for-leaders", + "kind": "skill", + "path": "skills/leadership/storytelling-for-leaders.md", + "category": "leadership" + }, + { + "id": "strategic-questioning", + "kind": "skill", + "path": "skills/leadership/strategic-questioning.md", + "category": "leadership" + }, + { + "id": "strategic-thinking-and-alignment", + "kind": "skill", + "path": "skills/leadership/strategic-thinking-and-alignment.md", + "category": "leadership" + }, + { + "id": "team-culture-and-dynamics", + "kind": "skill", + "path": "skills/leadership/team-culture-and-dynamics.md", + "category": "leadership" + }, + { + "id": "competitive-negotiation", + "kind": "skill", + "path": "skills/negotiation/competitive-negotiation.md", + "category": "negotiation" + }, + { + "id": "cooperative-negotiation", + "kind": "skill", + "path": "skills/negotiation/cooperative-negotiation.md", + "category": "negotiation" + }, + { + "id": "delivering-the-deal", + "kind": "skill", + "path": "skills/negotiation/delivering-the-deal.md", + "category": "negotiation" + }, + { + "id": "negotiation-mindset-and-self", + "kind": "skill", + "path": "skills/negotiation/negotiation-mindset-and-self.md", + "category": "negotiation" + }, + { + "id": "connecting-with-people", + "kind": "skill", + "path": "skills/people/connecting-with-people.md", + "category": "people" + }, + { + "id": "influencing-and-persuading", + "kind": "skill", + "path": "skills/people/influencing-and-persuading.md", + "category": "people" + }, + { + "id": "inspiring-and-retaining", + "kind": "skill", + "path": "skills/people/inspiring-and-retaining.md", + "category": "people" + }, + { + "id": "meeting-the-right-people", + "kind": "skill", + "path": "skills/people/meeting-the-right-people.md", + "category": "people" + }, + { + "id": "reading-people", + "kind": "skill", + "path": "skills/people/reading-people.md", + "category": "people" + }, + { + "id": "resolving-people-conflict", + "kind": "skill", + "path": "skills/people/resolving-people-conflict.md", + "category": "people" + }, + { + "id": "teaching-and-leading", + "kind": "skill", + "path": "skills/people/teaching-and-leading.md", + "category": "people" + }, + { + "id": "understanding-people", + "kind": "skill", + "path": "skills/people/understanding-people.md", + "category": "people" + }, + { + "id": "stoic-acceptance-amor-fati", + "kind": "skill", + "path": "skills/stoic/stoic-acceptance-amor-fati.md", + "category": "stoic" + }, + { + "id": "stoic-control-and-clarity", + "kind": "skill", + "path": "skills/stoic/stoic-control-and-clarity.md", + "category": "stoic" + }, + { + "id": "stoic-duty-and-service", + "kind": "skill", + "path": "skills/stoic/stoic-duty-and-service.md", + "category": "stoic" + }, + { + "id": "stoic-emotional-mastery", + "kind": "skill", + "path": "skills/stoic/stoic-emotional-mastery.md", + "category": "stoic" + }, + { + "id": "stoic-fortitude-and-resilience", + "kind": "skill", + "path": "skills/stoic/stoic-fortitude-and-resilience.md", + "category": "stoic" + }, + { + "id": "stoic-mortality-and-perspective", + "kind": "skill", + "path": "skills/stoic/stoic-mortality-and-perspective.md", + "category": "stoic" + }, + { + "id": "stoic-pragmatism", + "kind": "skill", + "path": "skills/stoic/stoic-pragmatism.md", + "category": "stoic" + }, + { + "id": "stoic-problem-solving", + "kind": "skill", + "path": "skills/stoic/stoic-problem-solving.md", + "category": "stoic" + }, + { + "id": "stoic-right-action", + "kind": "skill", + "path": "skills/stoic/stoic-right-action.md", + "category": "stoic" + }, + { + "id": "stoic-self-awareness", + "kind": "skill", + "path": "skills/stoic/stoic-self-awareness.md", + "category": "stoic" + }, + { + "id": "stoic-unbiased-thought", + "kind": "skill", + "path": "skills/stoic/stoic-unbiased-thought.md", + "category": "stoic" + }, + { + "id": "stoic-virtue-and-kindness", + "kind": "skill", + "path": "skills/stoic/stoic-virtue-and-kindness.md", + "category": "stoic" + }, + { + "id": "building-story-stakes", + "kind": "skill", + "path": "skills/storytelling/building-story-stakes.md", + "category": "storytelling" + }, + { + "id": "emotional-impact-in-stories", + "kind": "skill", + "path": "skills/storytelling/emotional-impact-in-stories.md", + "category": "storytelling" + }, + { + "id": "finding-your-stories", + "kind": "skill", + "path": "skills/storytelling/finding-your-stories.md", + "category": "storytelling" + }, + { + "id": "story-beginnings-and-endings", + "kind": "skill", + "path": "skills/storytelling/story-beginnings-and-endings.md", + "category": "storytelling" + }, + { + "id": "story-performance-and-delivery", + "kind": "skill", + "path": "skills/storytelling/story-performance-and-delivery.md", + "category": "storytelling" + }, + { + "id": "story-structure-and-arc", + "kind": "skill", + "path": "skills/storytelling/story-structure-and-arc.md", + "category": "storytelling" + }, + { + "id": "storytelling-truth-and-vividness", + "kind": "skill", + "path": "skills/storytelling/storytelling-truth-and-vividness.md", + "category": "storytelling" + }, + { + "id": "what-is-a-story", + "kind": "skill", + "path": "skills/storytelling/what-is-a-story.md", + "category": "storytelling" + }, + { + "id": "building-thinking-strength", + "kind": "skill", + "path": "skills/thinking/building-thinking-strength.md", + "category": "thinking" + }, + { + "id": "defining-and-exploring-problems", + "kind": "skill", + "path": "skills/thinking/defining-and-exploring-problems.md", + "category": "thinking" + }, + { + "id": "enemies-of-clear-thinking", + "kind": "skill", + "path": "skills/thinking/enemies-of-clear-thinking.md", + "category": "thinking" + }, + { + "id": "evaluating-and-deciding", + "kind": "skill", + "path": "skills/thinking/evaluating-and-deciding.md", + "category": "thinking" + }, + { + "id": "managing-weakness-and-mistakes", + "kind": "skill", + "path": "skills/thinking/managing-weakness-and-mistakes.md", + "category": "thinking" + }, + { + "id": "wanting-what-matters", + "kind": "skill", + "path": "skills/thinking/wanting-what-matters.md", + "category": "thinking" + }, + { + "id": "clarity-and-concision", + "kind": "skill", + "path": "skills/writing/clarity-and-concision.md", + "category": "writing" + }, + { + "id": "grammar-and-mechanics", + "kind": "skill", + "path": "skills/writing/grammar-and-mechanics.md", + "category": "writing" + }, + { + "id": "plain-language-and-flow", + "kind": "skill", + "path": "skills/writing/plain-language-and-flow.md", + "category": "writing" + }, + { + "id": "reader-psychology", + "kind": "skill", + "path": "skills/writing/reader-psychology.md", + "category": "writing" + }, + { + "id": "revising-and-editing", + "kind": "skill", + "path": "skills/writing/revising-and-editing.md", + "category": "writing" + }, + { + "id": "tone-and-engagement", + "kind": "skill", + "path": "skills/writing/tone-and-engagement.md", + "category": "writing" + }, + { + "id": "writing-effective-emails", + "kind": "skill", + "path": "skills/writing/writing-effective-emails.md", + "category": "writing" + }, + { + "id": "writing-for-navigation", + "kind": "skill", + "path": "skills/writing/writing-for-navigation.md", + "category": "writing" + }, + { + "id": "writing-for-response", + "kind": "skill", + "path": "skills/writing/writing-for-response.md", + "category": "writing" + }, + { + "id": "writing-memos-and-reports", + "kind": "skill", + "path": "skills/writing/writing-memos-and-reports.md", + "category": "writing" + }, + { + "id": "writing-performance-reviews", + "kind": "skill", + "path": "skills/writing/writing-performance-reviews.md", + "category": "writing" + }, + { + "id": "writing-process", + "kind": "skill", + "path": "skills/writing/writing-process.md", + "category": "writing" + }, + { + "id": "writing-with-purpose", + "kind": "skill", + "path": "skills/writing/writing-with-purpose.md", + "category": "writing" + } + ], + "aliases": { + "skill": { + "swot-analysis": "swot-pest-analysis", + "swot": "swot-pest-analysis", + "kaizen": "kaizen-bpr", + "tuckman-stages": "tuckman-team-stages", + "nps": "net-promoter-score" + }, + "diagnostic": { + "team": "team-dysfunction-diagnosis", + "product": "product-market-fit-diagnosis", + "culture": "culture-erosion-diagnosis", + "competition": "competitive-threat-diagnosis", + "churn": "customer-churn-diagnosis", + "cofounder": "cofounder-conflict-diagnosis", + "communication": "communication-breakdown-diagnosis", + "decisions": "decision-paralysis-diagnosis", + "operations": "operational-chaos-diagnosis", + "strategy": "strategic-drift-diagnosis" + }, + "research": { + "customer-interviews": "customer-interview-guide", + "market-sizing": "market-sizing-worksheet", + "competitor-analysis": "competitor-research-template", + "financial-modeling": "financial-modeling-guide", + "funding-landscape": "funding-landscape-research", + "technology-stack": "technology-stack-research", + "regulatory-landscape": "regulatory-landscape-research" + } + }, + "commands": { + "apply": "apply", + "diagnose": "diagnose", + "run": "foreman-run", + "resume": "foreman-resume", + "output": "output", + "track": "track", + "progress": "progress", + "blockers": "blockers", + "check-in": "check-in", + "language": "language", + "context": "foreman-context", + "update": "update", + "history": "history", + "decisions": "decisions", + "follow-ups": "follow-ups", + "forget": "forget", + "reset": "foreman-reset", + "help": "foreman-help", + "about": "about", + "version": "version", + "feedback": "feedback", + "sector": "sector", + "stage": "stage", + "skills": "skills", + "skill": "foreman-skill", + "templates": "templates", + "playbooks": "playbooks", + "diagnostics": "diagnostics", + "hooks": "hooks", + "search": "search", + "stakeholders": "stakeholders", + "power-map": "power-map", + "resistance": "resistance", + "coalition": "coalition", + "format": "format", + "export": "export", + "compare": "compare", + "status": "foreman-status", + "skip": "skip", + "back": "back", + "pause": "pause", + "abort": "abort", + "research": "research", + "simulate": "simulate", + "solo": "solo", + "stoic": "stoic" + } +} diff --git a/.claude/commands/abort.md b/.claude/commands/abort.md new file mode 100644 index 0000000..f60f13a --- /dev/null +++ b/.claude/commands/abort.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /abort command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /abort + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/about.md b/.claude/commands/about.md new file mode 100644 index 0000000..2e1778d --- /dev/null +++ b/.claude/commands/about.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /about command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /about + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /about with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/apply.md b/.claude/commands/apply.md new file mode 100644 index 0000000..2172e4d --- /dev/null +++ b/.claude/commands/apply.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /apply command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /apply + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /apply with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/back.md b/.claude/commands/back.md new file mode 100644 index 0000000..0856a3e --- /dev/null +++ b/.claude/commands/back.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /back command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /back + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /back with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/blockers.md b/.claude/commands/blockers.md new file mode 100644 index 0000000..692dab2 --- /dev/null +++ b/.claude/commands/blockers.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /blockers command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /blockers + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /blockers with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/check-in.md b/.claude/commands/check-in.md new file mode 100644 index 0000000..79e6e1b --- /dev/null +++ b/.claude/commands/check-in.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /check-in command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /check-in + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /check-in with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/coalition.md b/.claude/commands/coalition.md new file mode 100644 index 0000000..089b2b8 --- /dev/null +++ b/.claude/commands/coalition.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /coalition command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /coalition + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /coalition with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/compare.md b/.claude/commands/compare.md new file mode 100644 index 0000000..6d8eb0d --- /dev/null +++ b/.claude/commands/compare.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /compare command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /compare + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /compare with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/decisions.md b/.claude/commands/decisions.md new file mode 100644 index 0000000..de9ac6e --- /dev/null +++ b/.claude/commands/decisions.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /decisions command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /decisions + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /decisions with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/diagnose.md b/.claude/commands/diagnose.md new file mode 100644 index 0000000..351e24f --- /dev/null +++ b/.claude/commands/diagnose.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /diagnose command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnose + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /diagnose with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +Before answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact. diff --git a/.claude/commands/diagnostics.md b/.claude/commands/diagnostics.md new file mode 100644 index 0000000..8228831 --- /dev/null +++ b/.claude/commands/diagnostics.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /diagnostics command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnostics + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /diagnostics with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/export.md b/.claude/commands/export.md new file mode 100644 index 0000000..4ee1dae --- /dev/null +++ b/.claude/commands/export.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /export command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /export + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /export with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/feedback.md b/.claude/commands/feedback.md new file mode 100644 index 0000000..940eb4b --- /dev/null +++ b/.claude/commands/feedback.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /feedback command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /feedback + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /feedback with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/follow-ups.md b/.claude/commands/follow-ups.md new file mode 100644 index 0000000..446fa06 --- /dev/null +++ b/.claude/commands/follow-ups.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /follow-ups command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /follow-ups + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /follow-ups with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-context.md b/.claude/commands/foreman-context.md new file mode 100644 index 0000000..a07d220 --- /dev/null +++ b/.claude/commands/foreman-context.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /context command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /context + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /context with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-help.md b/.claude/commands/foreman-help.md new file mode 100644 index 0000000..fcf6a21 --- /dev/null +++ b/.claude/commands/foreman-help.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /help command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /help + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /help with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-reset.md b/.claude/commands/foreman-reset.md new file mode 100644 index 0000000..76b547b --- /dev/null +++ b/.claude/commands/foreman-reset.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /reset command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /reset + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /reset with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-resume.md b/.claude/commands/foreman-resume.md new file mode 100644 index 0000000..5d9cde8 --- /dev/null +++ b/.claude/commands/foreman-resume.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resume command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resume + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /resume with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-run.md b/.claude/commands/foreman-run.md new file mode 100644 index 0000000..fee87b3 --- /dev/null +++ b/.claude/commands/foreman-run.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /run command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /run + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /run with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-skill.md b/.claude/commands/foreman-skill.md new file mode 100644 index 0000000..1260b36 --- /dev/null +++ b/.claude/commands/foreman-skill.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skill command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skill + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /skill with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/foreman-status.md b/.claude/commands/foreman-status.md new file mode 100644 index 0000000..509e630 --- /dev/null +++ b/.claude/commands/foreman-status.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /status command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /status + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /status with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/forget.md b/.claude/commands/forget.md new file mode 100644 index 0000000..7c5869c --- /dev/null +++ b/.claude/commands/forget.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /forget command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /forget + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /forget with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/format.md b/.claude/commands/format.md new file mode 100644 index 0000000..9bbeee3 --- /dev/null +++ b/.claude/commands/format.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /format command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /format + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /format with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/history.md b/.claude/commands/history.md new file mode 100644 index 0000000..e094fe9 --- /dev/null +++ b/.claude/commands/history.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /history command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /history + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /history with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/hooks.md b/.claude/commands/hooks.md new file mode 100644 index 0000000..0af0a59 --- /dev/null +++ b/.claude/commands/hooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /hooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /hooks + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /hooks with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/language.md b/.claude/commands/language.md new file mode 100644 index 0000000..955b4fa --- /dev/null +++ b/.claude/commands/language.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /language command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /language + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/language-command.md and execute only /language with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/commands/memory-commands.md b/.claude/commands/memory-commands.md index bab6647..32add1c 100644 --- a/.claude/commands/memory-commands.md +++ b/.claude/commands/memory-commands.md @@ -30,6 +30,8 @@ commands: author: "Fatih Guner" --- +> Runtime note: These layers describe conceptual and legacy memory. Current writes use the versioned state and migration protocol in `.claude/RUNTIME.md`. Do not create a second active store. + # Memory Commands ## `/context` diff --git a/.claude/commands/output.md b/.claude/commands/output.md new file mode 100644 index 0000000..fbee56e --- /dev/null +++ b/.claude/commands/output.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /output command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /output + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /output with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/pause.md b/.claude/commands/pause.md new file mode 100644 index 0000000..e0f983d --- /dev/null +++ b/.claude/commands/pause.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /pause command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /pause + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /pause with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/playbooks.md b/.claude/commands/playbooks.md new file mode 100644 index 0000000..b781af6 --- /dev/null +++ b/.claude/commands/playbooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /playbooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /playbooks + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /playbooks with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/power-map.md b/.claude/commands/power-map.md new file mode 100644 index 0000000..059e664 --- /dev/null +++ b/.claude/commands/power-map.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /power-map command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /power-map + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /power-map with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/progress.md b/.claude/commands/progress.md new file mode 100644 index 0000000..d68cb28 --- /dev/null +++ b/.claude/commands/progress.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /progress command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /progress + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /progress with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/research.md b/.claude/commands/research.md new file mode 100644 index 0000000..9bb7d13 --- /dev/null +++ b/.claude/commands/research.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /research command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /research + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/research-commands.md and execute only /research with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/resistance.md b/.claude/commands/resistance.md new file mode 100644 index 0000000..0d61733 --- /dev/null +++ b/.claude/commands/resistance.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resistance command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resistance + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /resistance with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/search.md b/.claude/commands/search.md new file mode 100644 index 0000000..8ed7b1b --- /dev/null +++ b/.claude/commands/search.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /search command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /search + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /search with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/sector.md b/.claude/commands/sector.md new file mode 100644 index 0000000..51611ca --- /dev/null +++ b/.claude/commands/sector.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /sector command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /sector + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /sector with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/simulate.md b/.claude/commands/simulate.md new file mode 100644 index 0000000..d081e55 --- /dev/null +++ b/.claude/commands/simulate.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /simulate command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /simulate + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/simulation-commands.md and execute only /simulate with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/skills.md b/.claude/commands/skills.md new file mode 100644 index 0000000..7308c02 --- /dev/null +++ b/.claude/commands/skills.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skills command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skills + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /skills with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/skip.md b/.claude/commands/skip.md new file mode 100644 index 0000000..076c065 --- /dev/null +++ b/.claude/commands/skip.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skip command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skip + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /skip with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/solo.md b/.claude/commands/solo.md new file mode 100644 index 0000000..a6232f2 --- /dev/null +++ b/.claude/commands/solo.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /solo command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /solo + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/solo-command.md and execute only /solo with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/commands/stage.md b/.claude/commands/stage.md new file mode 100644 index 0000000..f129326 --- /dev/null +++ b/.claude/commands/stage.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stage command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stage + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/stakeholders.md b/.claude/commands/stakeholders.md new file mode 100644 index 0000000..874982b --- /dev/null +++ b/.claude/commands/stakeholders.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stakeholders command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stakeholders + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /stakeholders with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/stoic.md b/.claude/commands/stoic.md new file mode 100644 index 0000000..fc24021 --- /dev/null +++ b/.claude/commands/stoic.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /stoic command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stoic + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/stoic-command.md and execute only /stoic with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/commands/templates.md b/.claude/commands/templates.md new file mode 100644 index 0000000..6c57ea0 --- /dev/null +++ b/.claude/commands/templates.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /templates command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /templates + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /templates with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/track.md b/.claude/commands/track.md new file mode 100644 index 0000000..aa56402 --- /dev/null +++ b/.claude/commands/track.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /track command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /track + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /track with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/update.md b/.claude/commands/update.md new file mode 100644 index 0000000..23cc52a --- /dev/null +++ b/.claude/commands/update.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /update command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /update + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /update with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/commands/version.md b/.claude/commands/version.md new file mode 100644 index 0000000..8eac0c5 --- /dev/null +++ b/.claude/commands/version.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /version command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /version + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /version with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/diagnostics/decision-paralysis-diagnosis.md b/.claude/diagnostics/decision-paralysis-diagnosis.md index c201aed..4f2f87d 100644 --- a/.claude/diagnostics/decision-paralysis-diagnosis.md +++ b/.claude/diagnostics/decision-paralysis-diagnosis.md @@ -27,6 +27,8 @@ author: "Fatih Guner" # Decision Paralysis Diagnosis +Do not dismiss a stated irreversible risk before identifying the actual commitments. Treat the cause of hesitation as a hypothesis. Bound any experiment to the founder's runway, time and resources instead of inventing a universal duration. + Jeff Bezos distinguishes between Type 1 decisions (irreversible, consequential -- walk through a one-way door) and Type 2 decisions (reversible, low-cost -- walk through a two-way door and come back if it does not work). Most founders treat every decision as Type 1. The result is not prudence but paralysis -- weeks of deliberation over choices that could be tested in days, board meetings to resolve questions that a single phone call would answer. Worse, genuine Type 1 decisions receive the same agonized treatment, diluted by decision fatigue from all the false alarms. This diagnostic determines what is actually preventing the decision and whether the blockage is rational, emotional, structural, or self-imposed. --- diff --git a/.claude/diagnostics/fundraising-diagnosis.md b/.claude/diagnostics/fundraising-diagnosis.md index d8f284d..f11993a 100644 --- a/.claude/diagnostics/fundraising-diagnosis.md +++ b/.claude/diagnostics/fundraising-diagnosis.md @@ -28,6 +28,8 @@ author: "Fatih Guner" # Fundraising Diagnosis +First establish the funding stage, purpose and constraints. Required evidence varies by investor and stage; do not tell every pre-seed founder that existing revenue or mature unit economics are prerequisites. + Ninety percent of fundraising failures are misdiagnosed. The founder assumes the pitch deck needs better graphics. The advisor suggests more networking. The accelerator recommends "getting your story right." Meanwhile, the actual problem -- no product-market fit, no defensible unit economics, or a valuation that insults the intelligence of anyone who can operate a spreadsheet -- goes unaddressed. A polished pitch for a fundamentally unfundable business is still unfundable. This diagnostic separates the signal from the noise. --- diff --git a/.claude/diagnostics/revenue-diagnosis.md b/.claude/diagnostics/revenue-diagnosis.md index a738254..b4ee00f 100644 --- a/.claude/diagnostics/revenue-diagnosis.md +++ b/.claude/diagnostics/revenue-diagnosis.md @@ -30,17 +30,28 @@ author: "Fatih Guner" # Revenue Diagnosis +## First-response contract + +Until comparable revenue components are available, the result is **cause not established**. If the only acquisition evidence is that new customers still arrive, explicitly tell the founder that this does not establish whether acquisition revenue is improving or deteriorating. Customer counts, customer quality, conversion and realized price can move differently. + +Build the opening answer around the revenue bridge, with unknown components marked unknown: opening revenue + new revenue + expansion - contraction - churn = closing revenue. Ask for the previous and current period's new revenue and lost/contracted existing revenue. Keep acquisition, retention and pricing hypotheses open until those measurements distinguish them. Do not label the cause "existing customers" merely because acquisition is nonzero. Do not invent a universal churn target, NPS threshold, or ideal rate. + +Recommend collecting or reconciling these measurements as the first action. A channel shutdown, pricing reversal, or product change requires additional evidence. Once the measurements exist, use the triage below and explain which observation supports the selected branch. + ## Entry Symptoms The entrepreneur says some version of: "Sales are dropping," "We can't close deals anymore," "Revenue has flatlined," or "Our pipeline dried up." The complaint centres on money not coming in — but the underlying cause could be anything from a broken pricing model to a dying market. ## Triage Questions +Treat the branches below as hypotheses to investigate. Start with a revenue bridge over one consistent period: opening revenue + new customer revenue + expansion - contraction - churn = closing revenue. Ask for the missing components before excluding a cause. New customers can still arrive while acquisition volume, conversion, customer quality, or average deal size deteriorates. + ### Q1: Is the revenue problem coming from new customers or existing customers? -- **New customers (acquisition is failing)** — proceed to Q2 -- **Existing customers (retention is failing)** — proceed to Q4 +- **New customer revenue is below the comparable baseline** — investigate acquisition and conversion in Q2 +- **Existing customer revenue is below the comparable baseline** — investigate churn, contraction and expansion in Q4 - **Both** — proceed to Q2, then Q4; the diagnosis will compound +- **Unknown, or only customer counts are available** — request new and existing revenue, customer counts and average revenue for the same periods. Keep both acquisition and retention hypotheses open. ### Q2: What does your sales pipeline look like right now? @@ -50,14 +61,14 @@ The entrepreneur says some version of: "Sales are dropping," "We can't close dea ### Q3: Has your pricing, packaging, or discounting changed in the last 6 months? -- **Yes, we changed pricing** — likely diagnosis: **pricing-misalignment**. The market is rejecting the new value equation. +- **Yes, we changed pricing** — investigate **pricing-misalignment**. Compare conversion, realized prices and churn before and after the change; timing alone does not establish causation. - **No, pricing is unchanged but competitors undercut us** — likely diagnosis: **market-contraction** or competitive pressure. Proceed to Q6. - **No, and we're discounting more just to close** — the product's perceived value is eroding. Likely diagnosis: **weak-product-market-fit**. Proceed to Q5. ### Q4: What does your churn data show? -- **Churn is rising — customers leave within 3-6 months** — likely diagnosis: **high-churn**. The product fails to deliver sustained value. -- **Churn is stable but expansion revenue is flat** — customers stay but don't grow. The problem is monetisation, not retention. Likely diagnosis: **pricing-misalignment**. +- **Churn is rising — customers leave within 3-6 months** — investigate **high-churn**. Check cohort mix, expectations, onboarding, customer fit and value delivery before selecting an intervention. +- **Churn is stable but expansion revenue is flat** — examine monetisation and expansion opportunities while checking whether the stable churn level itself is sustainable. Pricing is one hypothesis; adoption and customer budget constraints are alternatives. - **Churn is rising and NPS is falling simultaneously** — likely diagnosis: **weak-product-market-fit**. The original problem the product solved may no longer exist or matter. ### Q5: Is the product still solving the problem it was built to solve? @@ -69,8 +80,8 @@ The entrepreneur says some version of: "Sales are dropping," "We can't close dea ### Q6: Has the competitive landscape changed meaningfully in the past year? - **New entrants appeared with lower prices or better features** — likely diagnosis: **market-contraction** (if industry-wide) or **broken-go-to-market** (if positioning failed to adapt). -- **No significant competitive change** — the problem is internal. Return to Q2 and Q5 for internal root causes. -- **A major competitor exited, yet our sales still dropped** — likely diagnosis: **sales-team-capability-gap**. Market opportunity exists but the team cannot capture it. +- **No significant competitive change** — return to Q2 and Q5, and check demand, regulation and macroeconomic conditions. Absence of a new competitor does not prove an internal cause. +- **A major competitor exited, yet our sales still dropped** — investigate both shrinking market demand and ability to capture suitable buyers. A competitor exit alone does not establish a sales-team capability gap. ## Diagnosis Map diff --git a/.claude/diagnostics/team-dysfunction-diagnosis.md b/.claude/diagnostics/team-dysfunction-diagnosis.md index 1c1ac04..a890a1a 100644 --- a/.claude/diagnostics/team-dysfunction-diagnosis.md +++ b/.claude/diagnostics/team-dysfunction-diagnosis.md @@ -31,6 +31,8 @@ author: "Fatih Guner" # Team Dysfunction Diagnosis +Role ambiguity can explain a pattern but does not prove why particular colleagues blame each other. Ask about one concrete delayed decision or handoff before attributing motives or declaring a root cause. + ## Entry Symptoms The entrepreneur describes breakdown in human terms: "The team isn't working," "Morale is terrible," "People keep leaving," or "Nobody takes ownership." These complaints are almost always symptoms, not causes. A team that "isn't working" could be suffering from a dozen different ailments — and the wrong treatment makes most of them worse. diff --git a/.claude/hooks/communication-hook.md b/.claude/hooks/communication-hook.md index 32eafac..cd29a4a 100644 --- a/.claude/hooks/communication-hook.md +++ b/.claude/hooks/communication-hook.md @@ -3,6 +3,33 @@ name: "communication-hook" description: "Hook for communication-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Nobody reads my emails + - Team misunderstands everything + - Investors don't get it + - Meetings are useless + - Can't explain what we do + - My writing sucks + - Presentation went badly + - Internal comms are chaos + - Board doesn't understand our strategy + - I dread public speaking + - Our messaging is all over the place + - People tune out when I talk +routes_to: + diagnostics: + - communication-breakdown-diagnosis + templates: + - meeting-notes-template + skills: + - business-model-canvas + - organisational-culture + - storytelling-for-leaders + - stoic-emotional-mastery + - story-performance-and-delivery + - reader-psychology + - writing-effective-emails + - writing-for-navigation --- # Communication Hook @@ -46,29 +73,29 @@ IF intent == writing-deficit: IF intent == meeting-dysfunction: → diagnostics/communication-breakdown-diagnosis - → skills/leadership/effective-meetings + → output-templates/team/meeting-notes-template.md → skills/writing/writing-for-navigation IF intent == stakeholder-communication: → diagnostics/communication-breakdown-diagnosis - → skills/storytelling/storytelling-for-leaders + → skills/leadership/storytelling-for-leaders.md → output-templates/investor/ → output-templates/board/ IF intent == messaging-clarity: → diagnostics/communication-breakdown-diagnosis - → skills/storytelling/storytelling-for-leaders - → skills/frameworks/value-proposition-canvas + → skills/leadership/storytelling-for-leaders.md + → skills/frameworks/business-model-canvas.md IF intent == presentation-anxiety: - → skills/storytelling/stage-presence - → skills/storytelling/storytelling-for-leaders - → skills/stoic/managing-emotions + → skills/storytelling/story-performance-and-delivery.md + → skills/leadership/storytelling-for-leaders.md + → skills/stoic/stoic-emotional-mastery.md IF intent == internal-alignment: → diagnostics/communication-breakdown-diagnosis → skills/writing/writing-for-navigation - → skills/leadership/organisational-culture + → skills/frameworks/organisational-culture.md → output-templates/team/ ``` diff --git a/.claude/hooks/culture-hook.md b/.claude/hooks/culture-hook.md index 904f372..f4e9490 100644 --- a/.claude/hooks/culture-hook.md +++ b/.claude/hooks/culture-hook.md @@ -3,6 +3,31 @@ name: "culture-hook" description: "Hook for culture-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Culture is breaking down + - Values mean nothing here + - New hires don't fit + - We've lost our identity + - Remote killed our culture + - People don't care anymore + - It used to feel different + - We're just a job now + - Nobody lives our values + - The vibe has completely changed + - Culture doesn't scale + - We hired too fast and lost something +routes_to: + diagnostics: + - culture-erosion-diagnosis + templates: + - culture-values-document + - hiring-scorecard + playbooks: + - scaling-playbook + skills: + - organisational-culture + - purpose-driven-leadership + - team-culture-and-dynamics --- # Culture Hook @@ -40,28 +65,28 @@ Every organisation has a culture. Few have the one they think they do. When the ``` IF intent == culture-erosion OR values-integrity-gap: → diagnostics/culture-erosion-diagnosis - → skills/leadership/organisational-culture + → skills/frameworks/organisational-culture.md → output-templates/team/culture-values-document IF intent == culture-fit-mismatch: → diagnostics/culture-erosion-diagnosis → skills/leadership/team-culture-and-dynamics - → skills/people/hiring-cultural-alignment + → output-templates/team/hiring-scorecard.md IF intent == remote-culture-strain: → diagnostics/culture-erosion-diagnosis - → skills/leadership/organisational-culture + → skills/frameworks/organisational-culture.md → skills/leadership/team-culture-and-dynamics IF intent == meaning-deficit: → diagnostics/culture-erosion-diagnosis - → skills/leadership/organisational-culture - → skills/ai-leadership/purpose-driven-leadership + → skills/frameworks/organisational-culture.md + → skills/leadership/purpose-driven-leadership.md IF intent == scaling-culture-dilution: → diagnostics/culture-erosion-diagnosis - → skills/leadership/organisational-culture - → playbooks/scaling-culture-playbook + → skills/frameworks/organisational-culture.md + → playbooks/scaling-playbook.md ``` **Priority:** Medium diff --git a/.claude/hooks/decision-hook.md b/.claude/hooks/decision-hook.md index b2b0089..a4fc600 100644 --- a/.claude/hooks/decision-hook.md +++ b/.claude/hooks/decision-hook.md @@ -3,6 +3,34 @@ name: "decision-hook" description: "Hook for decision-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Can't decide + - Analysis paralysis + - Every option seems risky + - Going back and forth + - What should I do? + - Too many options + - Afraid of making the wrong call + - Team can't agree on direction + - Need a framework for this decision + - Been debating this for weeks + - Don't have enough information to decide + - Every advisor says something different + - Flip-flopping on this constantly +routes_to: + diagnostics: + - decision-paralysis-diagnosis + templates: + - decision-journal + skills: + - choosing-and-executing + - evaluating-options + - generating-solutions + - tough-decision-situations + - decision-making-under-pressure + - leader-self-reflection + - enemies-of-clear-thinking + - evaluating-and-deciding --- # Decision Hook @@ -42,31 +70,31 @@ The cost of a wrong decision is almost always lower than the cost of no decision IF intent == decision-paralysis OR fear-driven-indecision: → diagnostics/decision-paralysis-diagnosis → skills/thinking/enemies-of-clear-thinking - → skills/decisions/evaluating-and-deciding - → output-templates/team/decision-journal + → skills/thinking/evaluating-and-deciding.md + → output-templates/self/decision-journal.md IF intent == collective-indecision: → diagnostics/decision-paralysis-diagnosis → skills/decisions/tough-decision-situations - → skills/decisions/consensus-and-commitment + → skills/decisions/choosing-and-executing.md → skills/thinking/enemies-of-clear-thinking IF intent == decision-framework-need: - → skills/decisions/evaluating-and-deciding + → skills/thinking/evaluating-and-deciding.md → skills/decisions/generating-solutions - → skills/decisions/even-swaps - → output-templates/team/decision-journal + → skills/decisions/evaluating-options.md + → output-templates/self/decision-journal.md IF intent == information-gap-excuse: → diagnostics/decision-paralysis-diagnosis → skills/thinking/enemies-of-clear-thinking - → skills/decisions/evaluating-and-deciding - → skills/decisions/seventy-percent-rule + → skills/thinking/evaluating-and-deciding.md + → skills/leadership/decision-making-under-pressure.md IF intent == advisor-confusion: → diagnostics/decision-paralysis-diagnosis - → skills/thinking/self-accountability - → skills/decisions/evaluating-and-deciding + → skills/leadership/leader-self-reflection.md + → skills/thinking/evaluating-and-deciding.md → skills/decisions/tough-decision-situations ``` diff --git a/.claude/hooks/innovation-hook.md b/.claude/hooks/innovation-hook.md index e1887ae..ddce3c9 100644 --- a/.claude/hooks/innovation-hook.md +++ b/.claude/hooks/innovation-hook.md @@ -3,6 +3,36 @@ name: "innovation-hook" description: "Hook for innovation-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - No new ideas + - Everything feels stale + - Team plays it safe + - We're stuck in a rut + - Innovation dried up + - Same old approaches + - Need fresh thinking + - How do I get creative again? + - We're not experimenting enough + - Nobody takes risks anymore + - Our product hasn't evolved in months + - Competitors are out-innovating us + - Brainstorming sessions produce nothing useful +routes_to: + diagnostics: + - innovation-drought-diagnosis + playbooks: + - innovation-sprint-playbook + skills: + - creative-collaboration-and-context + - creative-identity-and-purpose + - creative-obstacles + - creative-practice-and-habit + - generating-solutions + - blue-ocean-strategy + - business-model-canvas + - disruptive-innovation + - doblin-ten-types + - enemies-of-clear-thinking --- # Innovation Hook @@ -41,14 +71,14 @@ Creativity is not a personality trait that some teams possess and others lack. I ``` IF intent == creativity-drought OR founder-creative-block: → diagnostics/innovation-drought-diagnosis - → skills/creative/creative-identity-and-permission - → skills/creative/obstacles-and-blocks + → skills/creative/creative-identity-and-purpose.md + → skills/creative/creative-obstacles.md → skills/decisions/generating-solutions IF intent == risk-aversion: → diagnostics/innovation-drought-diagnosis → skills/thinking/enemies-of-clear-thinking - → skills/creative/practice-and-habit + → skills/creative/creative-practice-and-habit.md → playbooks/innovation-sprint-playbook IF intent == experimentation-gap: @@ -66,8 +96,8 @@ IF intent == competitive-innovation-lag: IF intent == ideation-process-failure: → diagnostics/innovation-drought-diagnosis → skills/decisions/generating-solutions - → skills/decisions/brainswarming - → skills/creative/collaboration-and-context + → skills/decisions/generating-solutions.md + → skills/creative/creative-collaboration-and-context.md ``` **Priority:** Medium diff --git a/.claude/hooks/launch-hook.md b/.claude/hooks/launch-hook.md index 89f984c..2e81526 100644 --- a/.claude/hooks/launch-hook.md +++ b/.claude/hooks/launch-hook.md @@ -3,6 +3,36 @@ name: "launch-hook" description: "Hook for launch-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Launching next month + - Entering a new market + - How do I launch? + - Going international + - New product launch + - Market entry strategy + - First launch ever + - Expanding to Europe/Asia + - GTM plan needed + - Go-to-market strategy + - Beta to general availability + - Launch timeline is slipping + - Don't know where to start with launch +routes_to: + diagnostics: + - market-entry-diagnosis + playbooks: + - first-100-customers-playbook + - international-expansion-playbook + - launch-playbook + skills: + - choosing-and-executing + - blue-ocean-strategy + - business-model-canvas + - growth-share-matrix + - net-promoter-score + - porters-five-forces + - first-mover-strategy + - stoic-right-action --- # Launch Hook @@ -55,23 +85,23 @@ IF intent == gtm-strategy: → diagnostics/market-entry-diagnosis → playbooks/launch-playbook → skills/frameworks/business-model-canvas - → skills/frameworks/value-proposition-canvas + → skills/frameworks/business-model-canvas.md IF intent == launch-execution: → playbooks/launch-playbook - → skills/leadership/effective-execution - → skills/thinking/self-control + → skills/decisions/choosing-and-executing.md + → skills/stoic/stoic-right-action.md IF intent == beta-transition: → diagnostics/market-entry-diagnosis → playbooks/first-100-customers-playbook - → skills/frameworks/crossing-the-chasm - → skills/frameworks/nps + → playbooks/first-100-customers-playbook.md + → skills/frameworks/net-promoter-score.md IF intent == product-line-launch: → diagnostics/market-entry-diagnosis → playbooks/launch-playbook - → skills/frameworks/ansoff-matrix + → skills/frameworks/growth-share-matrix.md → skills/frameworks/blue-ocean-strategy ``` diff --git a/.claude/hooks/negotiation-hook.md b/.claude/hooks/negotiation-hook.md index 7e8ba81..9228457 100644 --- a/.claude/hooks/negotiation-hook.md +++ b/.claude/hooks/negotiation-hook.md @@ -3,6 +3,32 @@ name: "negotiation-hook" description: "Hook for negotiation-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Deal is stuck + - Can't agree on terms + - They won't budge + - Getting a bad deal + - How do I negotiate this? + - Term sheet makes no sense + - Partner wants too much + - Contract negotiation + - They're playing hardball + - I keep giving in + - Vendor is squeezing us + - Salary negotiation with a key hire + - Licensing terms are unfair +routes_to: + diagnostics: + - negotiation-stuck-diagnosis + templates: + - negotiation-prep-sheet + playbooks: + - negotiation-playbook + skills: + - prisoners-dilemma-and-cooperation + - competitive-negotiation + - cooperative-negotiation + - delivering-the-deal --- # Negotiation Hook @@ -42,15 +68,15 @@ Negotiations fail for predictable reasons, yet founders persist in treating each IF intent == negotiation-deadlock: → diagnostics/negotiation-stuck-diagnosis → skills/negotiation/cooperative-negotiation - → skills/negotiation/resolution-roadmap + → skills/negotiation/delivering-the-deal.md IF intent == weak-position-negotiation OR power-asymmetry: → diagnostics/negotiation-stuck-diagnosis → skills/negotiation/competitive-negotiation - → skills/game-theory/credible-commitment + → skills/game-theory/prisoners-dilemma-and-cooperation.md IF intent == term-comprehension: - → skills/negotiation/negotiation-preparation + → output-templates/self/negotiation-prep-sheet.md → playbooks/negotiation-playbook IF intent == negotiation-skill-gap: @@ -61,7 +87,7 @@ IF intent == negotiation-skill-gap: IF intent == concession-pattern: → diagnostics/negotiation-stuck-diagnosis - → skills/negotiation/purposeful-concessions + → skills/negotiation/cooperative-negotiation.md → skills/negotiation/competitive-negotiation ``` diff --git a/.claude/hooks/partnership-hook.md b/.claude/hooks/partnership-hook.md index 450f0b6..e121c4e 100644 --- a/.claude/hooks/partnership-hook.md +++ b/.claude/hooks/partnership-hook.md @@ -3,6 +3,37 @@ name: "partnership-hook" description: "Hook for partnership-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Got a partnership offer + - Cofounder problems + - Should we merge? + - Strategic alliance opportunity + - Partner isn't delivering + - Equity split fight + - Joint venture? + - Acquisition offer came in + - My cofounder wants out + - Thinking about bringing on a cofounder + - Our partner is competing with us + - How do I structure this deal? + - Vesting schedule dispute +routes_to: + diagnostics: + - cofounder-conflict-diagnosis + - partnership-diagnosis + templates: + - unit-economics-snapshot + - personal-board-tracker + playbooks: + - acquisition-evaluation-playbook + - partnership-playbook + skills: + - swot-pest-analysis + - coalition-and-partnership-games + - information-asymmetry + - cooperative-negotiation + - delivering-the-deal + - resolving-people-conflict --- # Partnership Hook @@ -42,32 +73,32 @@ Partnerships are the business equivalent of marriage — entered with optimism, IF intent == cofounder-conflict: → diagnostics/cofounder-conflict-diagnosis → skills/negotiation/cooperative-negotiation - → skills/people/conflict-resolution + → skills/people/resolving-people-conflict.md → skills/game-theory/coalition-and-partnership-games IF intent == partnership-evaluation OR jv-structuring: → diagnostics/partnership-diagnosis → playbooks/partnership-playbook → skills/game-theory/coalition-and-partnership-games - → skills/frameworks/swot-analysis + → skills/frameworks/swot-pest-analysis.md IF intent == ma-evaluation: → diagnostics/partnership-diagnosis → playbooks/acquisition-evaluation-playbook - → skills/frameworks/unit-economics + → output-templates/investor/unit-economics-snapshot.md → skills/game-theory/information-asymmetry IF intent == partnership-breakdown: → diagnostics/partnership-diagnosis - → skills/negotiation/resolution-roadmap - → skills/people/conflict-resolution + → skills/negotiation/delivering-the-deal.md + → skills/people/resolving-people-conflict.md → skills/game-theory/coalition-and-partnership-games IF intent == partner-addition: → diagnostics/partnership-diagnosis → playbooks/partnership-playbook - → skills/game-theory/shapley-value - → skills/people/advisory-board + → skills/game-theory/coalition-and-partnership-games.md + → output-templates/self/personal-board-tracker.md ``` **Priority:** Medium diff --git a/.claude/hooks/personal-growth-hook.md b/.claude/hooks/personal-growth-hook.md index 81e7d98..fe51b91 100644 --- a/.claude/hooks/personal-growth-hook.md +++ b/.claude/hooks/personal-growth-hook.md @@ -3,6 +3,40 @@ name: "personal-growth-hook" description: "Hook for personal-growth-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - Want to be a better leader + - Need a mentor + - How do I grow? + - Skill gaps + - Career feels stuck + - Building my personal brand + - Want to learn more + - Investing in myself + - Need to develop my team + - Executive coaching + - Outgrowing my own abilities + - Not sure I'm the right CEO anymore + - How do other founders handle this? + - Want to build my network +routes_to: + templates: + - personal-board-tracker + playbooks: + - founder-transition-playbook + - personal-brand-playbook + skills: + - tuckman-team-stages + - career-strategy-for-leaders + - leader-self-reflection + - learning-agility + - mentoring-and-coaching + - storytelling-for-leaders + - meeting-the-right-people + - teaching-and-leading + - stoic-emotional-mastery + - stoic-right-action + - stoic-self-awareness + - reader-psychology --- # Personal Growth Hook @@ -43,40 +77,40 @@ The founder who asks "how do I become a better leader" has already crossed the m ``` IF intent == leadership-development: → skills/leadership/leader-self-reflection - → skills/ai-leadership/learning-agility + → skills/leadership/learning-agility.md → skills/leadership/career-strategy-for-leaders - → skills/stoic/self-discipline + → skills/stoic/stoic-right-action.md IF intent == mentorship-seeking: → skills/leadership/mentoring-and-coaching - → skills/people/advisory-board - → skills/people/networking + → output-templates/self/personal-board-tracker.md + → skills/people/meeting-the-right-people.md IF intent == skill-gap-remediation: → skills/leadership/leader-self-reflection - → skills/ai-leadership/learning-agility - → skills/thinking/self-knowledge + → skills/leadership/learning-agility.md + → skills/stoic/stoic-self-awareness.md IF intent == career-plateau: → skills/leadership/career-strategy-for-leaders - → skills/thinking/self-accountability + → skills/leadership/leader-self-reflection.md → playbooks/founder-transition-playbook IF intent == personal-brand: → playbooks/personal-brand-playbook - → skills/storytelling/storytelling-for-leaders + → skills/leadership/storytelling-for-leaders.md → skills/writing/reader-psychology IF intent == team-development: → skills/leadership/mentoring-and-coaching → skills/people/teaching-and-leading - → skills/frameworks/tuckman-stages + → skills/frameworks/tuckman-team-stages.md IF intent == role-fitness-doubt: → skills/leadership/leader-self-reflection - → skills/stoic/managing-emotions + → skills/stoic/stoic-emotional-mastery.md → playbooks/founder-transition-playbook - → skills/thinking/self-knowledge + → skills/stoic/stoic-self-awareness.md ``` **Priority:** Low diff --git a/.claude/hooks/research-hook.md b/.claude/hooks/research-hook.md index b66de0b..d24e9b0 100644 --- a/.claude/hooks/research-hook.md +++ b/.claude/hooks/research-hook.md @@ -3,6 +3,42 @@ name: "research-hook" description: "Hook for research-hook intent classification and routing" priority: "medium" author: "Fatih Guner" +trigger_patterns: + - I need data + - Where do I find information about my market? + - How do I research my competitors? + - I don't have the numbers + - Need to validate my assumptions + - How do I size my market? + - Need competitive intelligence + - How to interview customers + - I need to do due diligence + - Don't know where to start with research + - How much should I charge -- I need pricing data + - Need to understand the regulatory landscape + - How do I find out what customers actually want? + - I'm guessing at these numbers + - Where do I get benchmarks for my industry? +routes_to: + research: + - brand-perception-research + - churn-analysis-guide + - competitor-research-template + - content-strategy-research + - customer-interview-guide + - data-collection-plan + - due-diligence-research + - financial-modeling-guide + - funding-landscape-research + - industry-mapping-guide + - market-sizing-worksheet + - partnership-research-guide + - pricing-research-guide + - regulatory-landscape-research + - survey-design-guide + - talent-market-research + - technology-stack-research + - user-testing-protocol --- # Research Hook diff --git a/.claude/implementation/IMPLEMENTATION.md b/.claude/implementation/IMPLEMENTATION.md index 4ba8716..18638c6 100644 --- a/.claude/implementation/IMPLEMENTATION.md +++ b/.claude/implementation/IMPLEMENTATION.md @@ -1,3 +1,9 @@ +--- +name: implementation-tracking +description: "Runtime-backed task status, progress, blockers and accountability." +author: "Fatih Guner" +--- + # Implementation Tracking -- The Accountability Layer diff --git a/.claude/implementation/templates/blocker-analysis.md b/.claude/implementation/templates/blocker-analysis.md index 8020dd8..4a44359 100644 --- a/.claude/implementation/templates/blocker-analysis.md +++ b/.claude/implementation/templates/blocker-analysis.md @@ -1,16 +1,23 @@ --- name: "blocker-analysis" -description: "Produces a structured root-cause analysis of one or more blockers preventing implementation progress. Goes beyond surface identification to apply the five-whys technique, assess downstream impact, recommend specific resolution paths through the Foreman system, and define escalation triggers. Use when a blocker persists beyond one check-in cycle or when multiple blockers share a common root cause that warrants deeper investigation." +description: "Produces a structured root-cause analysis of one or more blockers + preventing implementation progress. Goes beyond surface identification to + apply the five-whys technique, assess downstream impact, recommend specific + resolution paths through the Foreman system, and define escalation triggers. + Use when a blocker persists beyond one check-in cycle or when multiple + blockers share a common root cause that warrants deeper investigation." audience: "self" applicable_skills: - evaluating-and-deciding - scenario-planning - - stakeholder-map - - resource-allocation + - eisenhower-matrix - stoic-emotional-mastery - stoic-control-and-clarity format: "analysis" author: "Fatih Guner" +related_content: + - kind: template + ref: stakeholder-map --- # Blocker Analysis diff --git a/.claude/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml b/.claude/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml index e336516..9bfc9d4 100644 --- a/.claude/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml +++ b/.claude/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml @@ -30,7 +30,10 @@ pack_metadata: sector: "agency-consulting" display_name: "Agency / Consulting" version: "1.0.0" - description: "Benchmark data for service businesses — consulting firms, digital agencies, creative studios, development shops, marketing agencies, PR firms, staffing firms, and professional services — where people, utilization, and rates are the fundamental economic drivers." + description: "Benchmark data for service businesses — consulting firms, digital + agencies, creative studios, development shops, marketing agencies, PR firms, + staffing firms, and professional services — where people, utilization, and + rates are the fundamental economic drivers." applicable_stages: - idea - validation @@ -58,110 +61,159 @@ benchmarks: - name: "Revenue" id: "revenue" category: "growth" - definition: "Total annual revenue from all sources — project fees, retainers, hourly billing, and productized services — before any cost deductions." + definition: "Total annual revenue from all sources — project fees, retainers, + hourly billing, and productized services — before any cost deductions." formula: "Sum of all client payments recognized in the fiscal year" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $250K annual revenue" - signal: "Solo practitioner or very early agency. Revenue depends entirely on the founder's personal billing capacity, leaving no margin for growth investment." + signal: "Solo practitioner or very early agency. Revenue depends entirely on the + founder's personal billing capacity, leaving no margin for growth + investment." below_average: value: "$250K-$750K" - signal: "Small agency with 2-5 people. Enough to cover salaries but insufficient to invest in sales, marketing, or operational infrastructure." + signal: "Small agency with 2-5 people. Enough to cover salaries but insufficient + to invest in sales, marketing, or operational infrastructure." average: value: "$750K-$3M" - signal: "Established small agency. Can support a dedicated leadership layer and begin investing in business development beyond founder-led sales." + signal: "Established small agency. Can support a dedicated leadership layer and + begin investing in business development beyond founder-led sales." good: value: "$3M-$10M" - signal: "Mid-size agency with departmental structure, multiple service lines, and a client portfolio diversified enough to weather individual client losses." + signal: "Mid-size agency with departmental structure, multiple service lines, + and a client portfolio diversified enough to weather individual client + losses." excellent: value: "> $10M" - signal: "Large agency with institutional client relationships, strong brand recognition, and the capacity to invest in proprietary methodologies or productized offerings." + signal: "Large agency with institutional client relationships, strong brand + recognition, and the capacity to invest in proprietary methodologies + or productized offerings." stage_notes: - seed: "Most agencies start as solo consultancies or partnerships. Revenue below $250K is typical for year one. Focus on landing 2-3 anchor clients rather than chasing scale." - series_a: "Agencies rarely raise venture capital. At the $1M-$3M stage, the equivalent milestone is hiring the first non-billable role (ops manager, business developer) and proving the firm can generate revenue beyond the founder." - series_b_plus: "At $5M+, the agency faces the 'scaling wall' — the founder can no longer personally oversee every engagement. Systems, processes, and a management layer become essential." + seed: "Most agencies start as solo consultancies or partnerships. Revenue below + $250K is typical for year one. Focus on landing 2-3 anchor clients + rather than chasing scale." + series_a: "Agencies rarely raise venture capital. At the $1M-$3M stage, the + equivalent milestone is hiring the first non-billable role (ops manager, + business developer) and proving the firm can generate revenue beyond the + founder." + series_b_plus: "At $5M+, the agency faces the 'scaling wall' — the founder can + no longer personally oversee every engagement. Systems, processes, and a + management layer become essential." data_sources: - source: "Agency Management Institute Financial Benchmarks" year: "2023" - source: "Promethean Research Agency Revenue Study" year: "2024" - related_metrics: ["revenue-per-employee", "revenue-per-client"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "Revenue in agencies can be reported as gross revenue (total billings) or net revenue (after subcontractor and pass-through costs). Always clarify which basis is used. Net revenue is the more meaningful figure for benchmarking." + related_metrics: [ "revenue-per-employee", "revenue-per-client" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Revenue in agencies can be reported as gross revenue (total billings) + or net revenue (after subcontractor and pass-through costs). Always + clarify which basis is used. Net revenue is the more meaningful figure for + benchmarking." - name: "Revenue per Employee" id: "revenue-per-employee" category: "efficiency" - definition: "Total annual revenue divided by average full-time-equivalent headcount, measuring the revenue-generating efficiency of the team." + definition: "Total annual revenue divided by average full-time-equivalent + headcount, measuring the revenue-generating efficiency of the team." formula: "Annual revenue / Average FTE headcount" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $100K per employee" - signal: "Severe underpricing, chronic low utilization, or excessive overhead. The firm cannot sustain competitive salaries at this level." + signal: "Severe underpricing, chronic low utilization, or excessive overhead. + The firm cannot sustain competitive salaries at this level." below_average: value: "$100K-$150K" - signal: "Below the sustainability threshold for most markets. Either rates are too low, utilization is poor, or non-billable headcount is excessive." + signal: "Below the sustainability threshold for most markets. Either rates are + too low, utilization is poor, or non-billable headcount is excessive." average: value: "$150K-$200K" - signal: "Solid baseline for a healthy agency. Supports market-rate salaries, reasonable overhead, and modest profit margins." + signal: "Solid baseline for a healthy agency. Supports market-rate salaries, + reasonable overhead, and modest profit margins." good: value: "$200K-$300K" - signal: "Strong revenue productivity. Indicates premium pricing, high utilization, or an efficient leverage model with lower-cost junior staff." + signal: "Strong revenue productivity. Indicates premium pricing, high + utilization, or an efficient leverage model with lower-cost junior + staff." excellent: value: "> $300K per employee" - signal: "Elite efficiency. Typical of strategy consultancies, specialized technical firms, or agencies with a strong productized service component." + signal: "Elite efficiency. Typical of strategy consultancies, specialized + technical firms, or agencies with a strong productized service + component." stage_notes: - seed: "Sole consultants often exceed $200K because there is no overhead. The metric becomes meaningful only after the first few hires, when the denominator includes non-billable staff." - series_a: "At 10-25 employees, this metric reveals whether the firm can maintain economic efficiency as it adds management and operational layers." - series_b_plus: "At 50+ employees, revenue per employee typically compresses as the firm adds middle management, HR, finance, and operations. Maintaining $200K+ at scale signals a well-run operation." + seed: "Sole consultants often exceed $200K because there is no overhead. The + metric becomes meaningful only after the first few hires, when the + denominator includes non-billable staff." + series_a: "At 10-25 employees, this metric reveals whether the firm can maintain + economic efficiency as it adds management and operational layers." + series_b_plus: "At 50+ employees, revenue per employee typically compresses as + the firm adds middle management, HR, finance, and operations. + Maintaining $200K+ at scale signals a well-run operation." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["revenue", "utilization-rate", "average-billable-rate"] - related_skills: ["balanced-scorecard", "shamrock-organisation"] - caveats: "Revenue per employee varies dramatically by geography, service type, and seniority mix. A strategy consultancy and a staffing firm are not comparable on this metric. Benchmark within the firm's specific discipline." + related_metrics: [ "revenue", "utilization-rate", "average-billable-rate" ] + related_skills: [ "balanced-scorecard", "shamrock-organisation" ] + caveats: "Revenue per employee varies dramatically by geography, service type, + and seniority mix. A strategy consultancy and a staffing firm are not + comparable on this metric. Benchmark within the firm's specific + discipline." - name: "Revenue per Client" id: "revenue-per-client" category: "growth" - definition: "Average annual revenue generated from each active client, indicating account depth and the ability to expand relationships." + definition: "Average annual revenue generated from each active client, + indicating account depth and the ability to expand relationships." formula: "Annual revenue / Number of active clients" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $10K per client annually" - signal: "Transactional client relationships. The firm is doing small, one-off projects with little relationship depth or expansion potential." + signal: "Transactional client relationships. The firm is doing small, one-off + projects with little relationship depth or expansion potential." below_average: value: "$10K-$30K" - signal: "Some repeat business but accounts are not deep enough to justify dedicated account management." + signal: "Some repeat business but accounts are not deep enough to justify + dedicated account management." average: value: "$30K-$75K" - signal: "Meaningful client relationships. Large enough to warrant strategic account planning and regular relationship maintenance." + signal: "Meaningful client relationships. Large enough to warrant strategic + account planning and regular relationship maintenance." good: value: "$75K-$200K" - signal: "Strong account depth. Clients are engaging the firm across multiple services or on sustained retainers." + signal: "Strong account depth. Clients are engaging the firm across multiple + services or on sustained retainers." excellent: value: "> $200K per client annually" - signal: "Deep strategic partnerships. The firm is embedded in the client's operations. High switching costs for the client." + signal: "Deep strategic partnerships. The firm is embedded in the client's + operations. High switching costs for the client." stage_notes: - seed: "Early agencies should aim for fewer, deeper client relationships rather than many small ones. One $100K client is more valuable than ten $10K clients at this stage." - series_a: "As the agency grows, balancing account depth with diversification becomes critical. Target a minimum of $50K per client with no single client exceeding 25% of revenue." - series_b_plus: "At scale, revenue per client becomes a segmentation tool. Identify which client tier generates the best margin and concentrate growth there." + seed: "Early agencies should aim for fewer, deeper client relationships rather + than many small ones. One $100K client is more valuable than ten $10K + clients at this stage." + series_a: "As the agency grows, balancing account depth with diversification + becomes critical. Target a minimum of $50K per client with no single + client exceeding 25% of revenue." + series_b_plus: "At scale, revenue per client becomes a segmentation tool. + Identify which client tier generates the best margin and concentrate + growth there." data_sources: - source: "Promethean Research Agency Benchmarks" year: "2024" - source: "Agency Management Institute Financial Benchmarks" year: "2023" - related_metrics: ["client-concentration", "client-retention-rate"] - related_skills: ["business-model-canvas", "net-promoter-score"] - caveats: "This metric must be interpreted alongside client count. A $3M agency with 3 clients ($1M each) has dangerous concentration. A $3M agency with 30 clients ($100K each) may have insufficient account depth." + related_metrics: [ "client-concentration", "client-retention-rate" ] + related_skills: [ "business-model-canvas", "net-promoter-score" ] + caveats: "This metric must be interpreted alongside client count. A $3M agency + with 3 clients ($1M each) has dangerous concentration. A $3M agency with + 30 clients ($100K each) may have insufficient account depth." # ───────────────────────────────────────────── # UTILIZATION METRICS @@ -170,110 +222,158 @@ benchmarks: - name: "Utilization Rate" id: "utilization-rate" category: "efficiency" - definition: "The percentage of total available working hours that are spent on client-billable or client-related productive work, including both billed and unbilled client work." + definition: "The percentage of total available working hours that are spent on + client-billable or client-related productive work, including both billed + and unbilled client work." formula: "(Total hours on client work / Total available working hours) x 100" unit: "percentage" direction: "target-range" benchmarks: poor: value: "< 55%" - signal: "Chronic underutilization. Staff are idle or consumed by internal work. Revenue cannot cover costs at this level unless rates are extraordinarily high." + signal: "Chronic underutilization. Staff are idle or consumed by internal work. + Revenue cannot cover costs at this level unless rates are + extraordinarily high." below_average: value: "55%-62%" - signal: "Below optimal. Either bench time is excessive, too much time is consumed by non-billable overhead, or the firm has hired ahead of demand." + signal: "Below optimal. Either bench time is excessive, too much time is + consumed by non-billable overhead, or the firm has hired ahead of + demand." average: value: "62%-68%" - signal: "Healthy utilization for most agencies and consultancies. Leaves room for professional development, sales, and administrative work." + signal: "Healthy utilization for most agencies and consultancies. Leaves room + for professional development, sales, and administrative work." good: value: "68%-75%" - signal: "Strong utilization. The firm is running efficiently without burning out staff. Typical of well-managed mid-size agencies." + signal: "Strong utilization. The firm is running efficiently without burning out + staff. Typical of well-managed mid-size agencies." excellent: value: "75%-80%" - signal: "Near-optimal utilization. Beyond 80%, quality degrades, burnout accelerates, and no capacity exists for new business development." + signal: "Near-optimal utilization. Beyond 80%, quality degrades, burnout + accelerates, and no capacity exists for new business development." stage_notes: - seed: "Solo consultants can achieve 70-80% utilization because they have minimal overhead. Once the first non-billable hire is made, overall utilization drops mechanically." - series_a: "At 10-25 people, target 65% firm-wide utilization. Leadership and operations staff should not be expected to bill significant hours." - series_b_plus: "Larger firms target 65-70% for billable staff, with firm-wide utilization (including leadership and ops) averaging 55-65%." + seed: "Solo consultants can achieve 70-80% utilization because they have minimal + overhead. Once the first non-billable hire is made, overall utilization + drops mechanically." + series_a: "At 10-25 people, target 65% firm-wide utilization. Leadership and + operations staff should not be expected to bill significant hours." + series_b_plus: "Larger firms target 65-70% for billable staff, with firm-wide + utilization (including leadership and ops) averaging 55-65%." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["billable-utilization-rate", "bench-time", "revenue-per-employee"] - related_skills: ["balanced-scorecard", "eisenhower-matrix"] - caveats: "Utilization above 80% is not a goal — it is a warning sign. Sustained high utilization leaves no capacity for professional development, innovation, or new business pursuit. It also correlates strongly with employee attrition." + related_metrics: [ "billable-utilization-rate", "bench-time", "revenue-per-employee" ] + related_skills: [ "balanced-scorecard", "eisenhower-matrix" ] + caveats: "Utilization above 80% is not a goal — it is a warning sign. Sustained + high utilization leaves no capacity for professional development, + innovation, or new business pursuit. It also correlates strongly with + employee attrition." - name: "Billable Utilization Rate" id: "billable-utilization-rate" category: "efficiency" - definition: "The percentage of total available working hours that are actually billed to and paid by clients, excluding unbilled client work, write-offs, and internal time." + definition: "The percentage of total available working hours that are actually + billed to and paid by clients, excluding unbilled client work, write-offs, + and internal time." formula: "(Hours billed to clients / Total available working hours) x 100" unit: "percentage" direction: "target-range" benchmarks: poor: value: "< 50%" - signal: "Fewer than half of available hours generate revenue. The gap between utilization and billable utilization suggests significant write-offs, scope creep, or unbilled work." + signal: "Fewer than half of available hours generate revenue. The gap between + utilization and billable utilization suggests significant write-offs, + scope creep, or unbilled work." below_average: value: "50%-58%" - signal: "Moderate leakage between worked hours and billed hours. Common causes: scope creep, poor time tracking, and reluctance to bill for all work performed." + signal: "Moderate leakage between worked hours and billed hours. Common causes: + scope creep, poor time tracking, and reluctance to bill for all work + performed." average: value: "58%-65%" - signal: "Acceptable billable efficiency. The gap between utilization rate and billable rate should be under 7 percentage points." + signal: "Acceptable billable efficiency. The gap between utilization rate and + billable rate should be under 7 percentage points." good: value: "65%-72%" - signal: "Strong billing discipline. The firm captures most productive time as revenue and maintains tight scope management." + signal: "Strong billing discipline. The firm captures most productive time as + revenue and maintains tight scope management." excellent: value: "72%-78%" - signal: "Exceptional billing efficiency. Characteristic of firms with rigorous time tracking, clear scoping, and value-based pricing that minimizes the billable-hours problem." + signal: "Exceptional billing efficiency. Characteristic of firms with rigorous + time tracking, clear scoping, and value-based pricing that minimizes + the billable-hours problem." stage_notes: - seed: "Solo consultants should track the gap between time worked and time billed. A gap above 10 percentage points indicates systemic scope creep or undercharging." - series_a: "As the firm grows, the billable utilization rate for delivery staff should be tracked separately from firm-wide utilization." - series_b_plus: "Mature agencies use the gap between utilization and billable utilization as a management metric — it reveals operational efficiency." + seed: "Solo consultants should track the gap between time worked and time + billed. A gap above 10 percentage points indicates systemic scope creep + or undercharging." + series_a: "As the firm grows, the billable utilization rate for delivery staff + should be tracked separately from firm-wide utilization." + series_b_plus: "Mature agencies use the gap between utilization and billable + utilization as a management metric — it reveals operational efficiency." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["utilization-rate", "effective-billable-rate", "scope-creep-rate"] - related_skills: ["balanced-scorecard", "smart-goals"] - caveats: "Firms using fixed-price or retainer models may find billable utilization difficult to measure precisely. In these cases, track 'productive utilization' against contracted deliverables rather than hourly billing." + related_metrics: [ "utilization-rate", "effective-billable-rate", "scope-creep-rate" ] + related_skills: [ "balanced-scorecard", "smart-goals" ] + caveats: "Firms using fixed-price or retainer models may find billable + utilization difficult to measure precisely. In these cases, track + 'productive utilization' against contracted deliverables rather than + hourly billing." - name: "Bench Time" id: "bench-time" category: "efficiency" - definition: "The percentage of billable staff who are currently unassigned to any client project, representing idle capacity and a direct cost to the business." + definition: "The percentage of billable staff who are currently unassigned to + any client project, representing idle capacity and a direct cost to the + business." formula: "(FTEs without client assignments / Total billable FTEs) x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 20%" - signal: "One in five billable staff is idle. This drains cash and indicates either a sales pipeline failure or overhiring relative to demand." + signal: "One in five billable staff is idle. This drains cash and indicates + either a sales pipeline failure or overhiring relative to demand." below_average: value: "15%-20%" - signal: "Elevated bench. Acceptable for brief periods between major projects but unsustainable beyond one quarter." + signal: "Elevated bench. Acceptable for brief periods between major projects but + unsustainable beyond one quarter." average: value: "10%-15%" - signal: "Manageable bench level. Some bench time is healthy — it enables rapid response to new opportunities and allows for professional development." + signal: "Manageable bench level. Some bench time is healthy — it enables rapid + response to new opportunities and allows for professional + development." good: value: "5%-10%" - signal: "Lean operation with modest buffer capacity. The firm can respond to new work without significant hiring lag." + signal: "Lean operation with modest buffer capacity. The firm can respond to new + work without significant hiring lag." excellent: value: "< 5%" - signal: "Near-full deployment. Efficient but potentially fragile — no surge capacity for unexpected opportunities or client emergencies." + signal: "Near-full deployment. Efficient but potentially fragile — no surge + capacity for unexpected opportunities or client emergencies." stage_notes: - seed: "Bench is rarely relevant for agencies under 5 people — everyone works on everything. The concept becomes meaningful at 10+ billable staff." - series_a: "At 10-25 people, bench management becomes a critical skill. Track bench weekly, not monthly. A two-week bench period per person per year is a reasonable target." - series_b_plus: "Larger agencies use bench strategically — assigning benched staff to R&D, internal tools, thought leadership, or pre-sales activities." + seed: "Bench is rarely relevant for agencies under 5 people — everyone works on + everything. The concept becomes meaningful at 10+ billable staff." + series_a: "At 10-25 people, bench management becomes a critical skill. Track + bench weekly, not monthly. A two-week bench period per person per year + is a reasonable target." + series_b_plus: "Larger agencies use bench strategically — assigning benched + staff to R&D, internal tools, thought leadership, or pre-sales + activities." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["utilization-rate", "revenue-per-employee"] - related_skills: ["scenario-planning", "eisenhower-matrix"] - caveats: "Zero bench time is not a goal. Firms with zero bench cannot respond to new opportunities, leading to turned-away revenue. Optimal bench is 5-10%, deployed productively." + related_metrics: [ "utilization-rate", "revenue-per-employee" ] + related_skills: [ "scenario-planning", "eisenhower-matrix" ] + caveats: "Zero bench time is not a goal. Firms with zero bench cannot respond to + new opportunities, leading to turned-away revenue. Optimal bench is 5-10%, + deployed productively." # ───────────────────────────────────────────── # PRICING & RATE METRICS @@ -282,74 +382,117 @@ benchmarks: - name: "Average Billable Rate" id: "average-billable-rate" category: "unit-economics" - definition: "The mean hourly rate charged across all billable staff and engagement types, before any discounts, write-offs, or scope adjustments." + definition: "The mean hourly rate charged across all billable staff and + engagement types, before any discounts, write-offs, or scope adjustments." formula: "Total standard billings / Total hours billed" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $100/hour" - signal: "Commodity pricing territory. At this rate, the firm competes with freelancers and offshore teams. Margins are thin and talent retention is difficult." + signal: "Commodity pricing territory. At this rate, the firm competes with + freelancers and offshore teams. Margins are thin and talent retention + is difficult." below_average: value: "$100-$150/hour" - signal: "Mid-market rate. Viable for execution-focused agencies but insufficient for strategic advisory or premium creative work." + signal: "Mid-market rate. Viable for execution-focused agencies but insufficient + for strategic advisory or premium creative work." average: value: "$150-$225/hour" - signal: "Professional-grade rate. Supports experienced staff, decent margins, and investment in the business. Typical for competent mid-market agencies." + signal: "Professional-grade rate. Supports experienced staff, decent margins, + and investment in the business. Typical for competent mid-market + agencies." good: value: "$225-$350/hour" - signal: "Premium rate. Commands respect and supports higher-caliber talent. Typical for specialized consultancies and top-tier creative agencies." + signal: "Premium rate. Commands respect and supports higher-caliber talent. + Typical for specialized consultancies and top-tier creative agencies." excellent: value: "> $350/hour" - signal: "Elite rate. Reserved for management consultancies, highly specialized technical firms, and agencies with exceptional brand and track record." + signal: "Elite rate. Reserved for management consultancies, highly specialized + technical firms, and agencies with exceptional brand and track + record." stage_notes: - seed: "New consultants often underprice to win work. Calculate a minimum viable rate: (target salary + overhead + profit margin) / (available billable hours). Most solos should charge more than they think." - series_a: "Blended rate matters more than individual rates. The firm should have a rate card by seniority level and manage the staff mix to achieve target blended rate." - series_b_plus: "At scale, rate management becomes strategic. Senior staff should command rates 3-5x junior staff. The blended rate should rise as the firm's reputation grows." + seed: "New consultants often underprice to win work. Calculate a minimum viable + rate: (target salary + overhead + profit margin) / (available billable + hours). Most solos should charge more than they think." + series_a: "Blended rate matters more than individual rates. The firm should have + a rate card by seniority level and manage the staff mix to achieve + target blended rate." + series_b_plus: "At scale, rate management becomes strategic. Senior staff should + command rates 3-5x junior staff. The blended rate should rise as the + firm's reputation grows." data_sources: - source: "HubSpot Agency Pricing Report" year: "2024" - source: "Promethean Research Agency Benchmarks" year: "2024" - related_metrics: ["effective-billable-rate", "revenue-per-employee"] - related_skills: ["pricing-diagnosis", "four-ps-marketing"] - caveats: "Rates vary enormously by geography, discipline, and client segment. A $150/hour rate in a low-cost market may represent premium pricing. Always benchmark within the firm's specific context." + related_metrics: [ "effective-billable-rate", "revenue-per-employee" ] + related_skills: + - four-ps-marketing + caveats: "Rates vary enormously by geography, discipline, and client segment. A + $150/hour rate in a low-cost market may represent premium pricing. Always + benchmark within the firm's specific context." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Effective Billable Rate" id: "effective-billable-rate" category: "unit-economics" - definition: "The actual revenue earned per hour of work performed on client engagements, accounting for discounts, write-offs, scope creep, and fixed-price overruns." - formula: "Actual revenue collected / Total hours worked on client projects (billed and unbilled)" + definition: "The actual revenue earned per hour of work performed on client + engagements, accounting for discounts, write-offs, scope creep, and + fixed-price overruns." + formula: "Actual revenue collected / Total hours worked on client projects + (billed and unbilled)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< 60% of standard rate" - signal: "Massive value leakage. For every dollar the firm should earn, it collects less than 60 cents. Discounting, write-offs, and scope creep are eroding the business." + signal: "Massive value leakage. For every dollar the firm should earn, it + collects less than 60 cents. Discounting, write-offs, and scope creep + are eroding the business." below_average: value: "60%-75% of standard rate" - signal: "Significant rate erosion. Common causes: aggressive discounting to win work, poor scope management, and failure to bill for change orders." + signal: "Significant rate erosion. Common causes: aggressive discounting to win + work, poor scope management, and failure to bill for change orders." average: value: "75%-85% of standard rate" - signal: "Moderate erosion. The gap between standard and effective rate is manageable but indicates room for improvement in scope and billing discipline." + signal: "Moderate erosion. The gap between standard and effective rate is + manageable but indicates room for improvement in scope and billing + discipline." good: value: "85%-92% of standard rate" - signal: "Strong rate realization. The firm maintains discipline on scope, billing, and discounts while remaining competitive." + signal: "Strong rate realization. The firm maintains discipline on scope, + billing, and discounts while remaining competitive." excellent: value: "> 92% of standard rate" - signal: "Exceptional rate realization. Nearly all work performed is captured as revenue. Characteristic of firms with strong positioning and negotiation discipline." + signal: "Exceptional rate realization. Nearly all work performed is captured as + revenue. Characteristic of firms with strong positioning and + negotiation discipline." stage_notes: - seed: "Solo consultants should track effective rate obsessively. The gap between what they charge and what they actually earn per hour often reveals shocking underpricing." - series_a: "At 10-25 people, effective rate realization becomes a management discipline. Train project managers to track hours against estimates and flag overruns early." - series_b_plus: "Mature agencies target 85%+ effective rate realization and include it in project manager KPIs." + seed: "Solo consultants should track effective rate obsessively. The gap between + what they charge and what they actually earn per hour often reveals + shocking underpricing." + series_a: "At 10-25 people, effective rate realization becomes a management + discipline. Train project managers to track hours against estimates and + flag overruns early." + series_b_plus: "Mature agencies target 85%+ effective rate realization and + include it in project manager KPIs." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Agency Management Institute Financial Benchmarks" year: "2023" - related_metrics: ["average-billable-rate", "scope-creep-rate", "gross-margin"] - related_skills: ["pricing-diagnosis", "competitive-negotiation"] - caveats: "Effective rate is the single most revealing metric for agency profitability. A firm with a high standard rate but low effective rate has a discipline problem, not a pricing problem." + related_metrics: [ "average-billable-rate", "scope-creep-rate", "gross-margin" ] + related_skills: + - competitive-negotiation + caveats: "Effective rate is the single most revealing metric for agency + profitability. A firm with a high standard rate but low effective rate has + a discipline problem, not a pricing problem." + related_content: + - kind: diagnostic + ref: pricing-diagnosis # ───────────────────────────────────────────── # PROFITABILITY METRICS @@ -358,74 +501,108 @@ benchmarks: - name: "Gross Margin" id: "gross-margin" category: "financial" - definition: "Revenue minus direct costs of service delivery (staff salaries, freelancer costs, subcontractor fees, and direct project expenses), expressed as a percentage of revenue." + definition: "Revenue minus direct costs of service delivery (staff salaries, + freelancer costs, subcontractor fees, and direct project expenses), + expressed as a percentage of revenue." formula: "(Revenue - Direct costs of delivery) / Revenue x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 40%" - signal: "Dangerously thin margins. After overhead, the firm is likely unprofitable. Either rates are too low, utilization is poor, or the cost of delivery is excessive." + signal: "Dangerously thin margins. After overhead, the firm is likely + unprofitable. Either rates are too low, utilization is poor, or the + cost of delivery is excessive." below_average: value: "40%-50%" - signal: "Thin margins that leave little room for overhead, business development, and profit. Common in agencies competing on price." + signal: "Thin margins that leave little room for overhead, business development, + and profit. Common in agencies competing on price." average: value: "50%-55%" - signal: "Acceptable gross margin for most agency types. Enough to cover overhead and generate a modest profit." + signal: "Acceptable gross margin for most agency types. Enough to cover overhead + and generate a modest profit." good: value: "55%-65%" - signal: "Healthy margins indicating strong pricing, efficient delivery, and good leverage (appropriate mix of senior and junior staff)." + signal: "Healthy margins indicating strong pricing, efficient delivery, and good + leverage (appropriate mix of senior and junior staff)." excellent: value: "> 65%" - signal: "Premium margins. Typical of strategy consultancies, highly specialized firms, or agencies with significant productized revenue." + signal: "Premium margins. Typical of strategy consultancies, highly specialized + firms, or agencies with significant productized revenue." stage_notes: - seed: "Solo consultants without subcontractors may see gross margins of 90%+ because there are no direct labor costs beyond their own time. This compresses dramatically with the first hires." - series_a: "At 10-25 people, gross margin is the critical metric. If gross margin is below 50%, the firm cannot sustain the overhead structure needed to grow." - series_b_plus: "Mature agencies should maintain gross margin above 50% while investing in senior talent and specialized capabilities." + seed: "Solo consultants without subcontractors may see gross margins of 90%+ + because there are no direct labor costs beyond their own time. This + compresses dramatically with the first hires." + series_a: "At 10-25 people, gross margin is the critical metric. If gross margin + is below 50%, the firm cannot sustain the overhead structure needed to + grow." + series_b_plus: "Mature agencies should maintain gross margin above 50% while + investing in senior talent and specialized capabilities." data_sources: - source: "Deltek Clarity Industry Study" year: "2023" - source: "Agency Management Institute Financial Benchmarks" year: "2023" - related_metrics: ["ebitda-margin", "effective-billable-rate", "leverage-ratio"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "Gross margin in agencies depends heavily on how 'direct costs' are classified. Some firms include all staff salaries in COGS; others include only billable staff. Ensure consistent classification when benchmarking." + related_metrics: [ "ebitda-margin", "effective-billable-rate", "leverage-ratio" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Gross margin in agencies depends heavily on how 'direct costs' are + classified. Some firms include all staff salaries in COGS; others include + only billable staff. Ensure consistent classification when benchmarking." - name: "EBITDA Margin" id: "ebitda-margin" category: "financial" - definition: "Earnings before interest, taxes, depreciation, and amortization as a percentage of revenue, representing the operating profitability of the firm." - formula: "(Revenue - All operating expenses) / Revenue x 100 (before interest, taxes, depreciation, amortization)" + definition: "Earnings before interest, taxes, depreciation, and amortization as + a percentage of revenue, representing the operating profitability of the + firm." + formula: "(Revenue - All operating expenses) / Revenue x 100 (before interest, + taxes, depreciation, amortization)" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 5%" - signal: "Near breakeven. The firm has no margin of safety. A single lost client or late payment could create a cash crisis." + signal: "Near breakeven. The firm has no margin of safety. A single lost client + or late payment could create a cash crisis." below_average: value: "5%-10%" - signal: "Thin profitability. Sufficient to survive but not to invest in growth, build reserves, or reward partners generously." + signal: "Thin profitability. Sufficient to survive but not to invest in growth, + build reserves, or reward partners generously." average: value: "10%-15%" - signal: "Respectable profitability for a well-run agency. Enough to build cash reserves, invest modestly in growth, and provide competitive partner compensation." + signal: "Respectable profitability for a well-run agency. Enough to build cash + reserves, invest modestly in growth, and provide competitive partner + compensation." good: value: "15%-20%" - signal: "Strong profitability. The firm can invest in growth, weather downturns, and attract partner-level talent with meaningful equity or profit participation." + signal: "Strong profitability. The firm can invest in growth, weather downturns, + and attract partner-level talent with meaningful equity or profit + participation." excellent: value: "> 20%" - signal: "Exceptional profitability. Typical of specialized consultancies, firms with productized offerings, or agencies with dominant market positions." + signal: "Exceptional profitability. Typical of specialized consultancies, firms + with productized offerings, or agencies with dominant market + positions." stage_notes: - seed: "Profitability in year one is a luxury but not a requirement. However, agencies should target breakeven within 12-18 months — unlike product companies, agencies should not burn cash for years." - series_a: "At 10-25 employees, target 10%+ EBITDA margin. If margins are thinner, examine overhead ratio and utilization before cutting salaries." - series_b_plus: "Mature agencies operating below 10% EBITDA are likely either overinvesting in growth or suffering from structural margin problems." + seed: "Profitability in year one is a luxury but not a requirement. However, + agencies should target breakeven within 12-18 months — unlike product + companies, agencies should not burn cash for years." + series_a: "At 10-25 employees, target 10%+ EBITDA margin. If margins are + thinner, examine overhead ratio and utilization before cutting + salaries." + series_b_plus: "Mature agencies operating below 10% EBITDA are likely either + overinvesting in growth or suffering from structural margin problems." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["gross-margin", "overhead-ratio", "revenue-per-employee"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "In owner-operated agencies, EBITDA may be understated because the owner takes a below-market salary, or overstated because the owner pays themselves above-market. Normalize owner compensation to market rate before benchmarking." + related_metrics: [ "gross-margin", "overhead-ratio", "revenue-per-employee" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "In owner-operated agencies, EBITDA may be understated because the + owner takes a below-market salary, or overstated because the owner pays + themselves above-market. Normalize owner compensation to market rate + before benchmarking." # ───────────────────────────────────────────── # CLIENT METRICS @@ -434,74 +611,103 @@ benchmarks: - name: "Client Concentration" id: "client-concentration" category: "financial" - definition: "The revenue share attributable to the single largest client, measuring dependency risk." + definition: "The revenue share attributable to the single largest client, + measuring dependency risk." formula: "Revenue from largest client / Total revenue x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 40%" - signal: "Existential dependency. Losing this client would threaten the firm's survival. The client also holds excessive negotiating power over rates and terms." + signal: "Existential dependency. Losing this client would threaten the firm's + survival. The client also holds excessive negotiating power over rates + and terms." below_average: value: "30%-40%" - signal: "Dangerously concentrated. The firm's strategic decisions are constrained by the need to retain this account." + signal: "Dangerously concentrated. The firm's strategic decisions are + constrained by the need to retain this account." average: value: "20%-30%" - signal: "Moderate concentration. Manageable if the relationship is strong, but diversification should be an active priority." + signal: "Moderate concentration. Manageable if the relationship is strong, but + diversification should be an active priority." good: value: "10%-20%" - signal: "Healthy balance between account depth and diversification. No single client loss would fundamentally threaten the business." + signal: "Healthy balance between account depth and diversification. No single + client loss would fundamentally threaten the business." excellent: value: "< 10%" - signal: "Well-diversified. The firm can walk away from any single client without existential risk, which paradoxically strengthens negotiating power." + signal: "Well-diversified. The firm can walk away from any single client without + existential risk, which paradoxically strengthens negotiating power." stage_notes: - seed: "High concentration is inevitable in the first 1-2 years. Accept it, but actively pursue diversification. Every new client reduces existential risk." - series_a: "At $1M-$3M revenue, no client should exceed 25%. This is the stage where concentration risk transitions from 'understood and managed' to 'structural vulnerability.'" - series_b_plus: "At $5M+, target sub-15% for the largest client and ensure the top 5 clients combined represent no more than 50% of revenue." + seed: "High concentration is inevitable in the first 1-2 years. Accept it, but + actively pursue diversification. Every new client reduces existential + risk." + series_a: "At $1M-$3M revenue, no client should exceed 25%. This is the stage + where concentration risk transitions from 'understood and managed' to + 'structural vulnerability.'" + series_b_plus: "At $5M+, target sub-15% for the largest client and ensure the + top 5 clients combined represent no more than 50% of revenue." data_sources: - source: "Agency Management Institute Financial Benchmarks" year: "2023" - source: "David C. Baker / ReCourses — agency economics" year: "2024" - related_metrics: ["revenue-per-client", "client-retention-rate"] - related_skills: ["scenario-planning", "porters-five-forces"] - caveats: "Concentration is acceptable when the client is contractually committed (multi-year retainer) and strategically aligned. It is dangerous when the relationship is month-to-month and dependent on a single champion." + related_metrics: [ "revenue-per-client", "client-retention-rate" ] + related_skills: [ "scenario-planning", "porters-five-forces" ] + caveats: "Concentration is acceptable when the client is contractually committed + (multi-year retainer) and strategically aligned. It is dangerous when the + relationship is month-to-month and dependent on a single champion." - name: "Client Retention Rate" id: "client-retention-rate" category: "retention" - definition: "The percentage of clients from the prior year who continue to engage the firm in the current year, measuring relationship durability." + definition: "The percentage of clients from the prior year who continue to + engage the firm in the current year, measuring relationship durability." formula: "(Clients retained from prior year / Total clients in prior year) x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 60%" - signal: "The firm loses nearly half its clients annually. This forces constant new business development and prevents account deepening. Often a quality or relationship problem." + signal: "The firm loses nearly half its clients annually. This forces constant + new business development and prevents account deepening. Often a + quality or relationship problem." below_average: value: "60%-70%" - signal: "Below average retention. The firm is on a treadmill — acquiring new clients to replace departing ones rather than growing existing relationships." + signal: "Below average retention. The firm is on a treadmill — acquiring new + clients to replace departing ones rather than growing existing + relationships." average: value: "70%-80%" - signal: "Reasonable retention for most agency types. Some churn is natural as client needs evolve, budgets shift, or projects conclude." + signal: "Reasonable retention for most agency types. Some churn is natural as + client needs evolve, budgets shift, or projects conclude." good: value: "80%-90%" - signal: "Strong retention indicating the firm is embedded in client operations and delivering consistent value." + signal: "Strong retention indicating the firm is embedded in client operations + and delivering consistent value." excellent: value: "> 90%" - signal: "Exceptional client loyalty. The firm has become a trusted extension of the client's team. Typical of deep retainer relationships." + signal: "Exceptional client loyalty. The firm has become a trusted extension of + the client's team. Typical of deep retainer relationships." stage_notes: - seed: "Early-stage retention is volatile because the client base is small — losing one of three clients is 33% churn. Track retention carefully but interpret it within the context of a small sample." - series_a: "At 15-30 clients, retention rate becomes statistically meaningful and a leading indicator of firm health." - series_b_plus: "Mature firms should segment retention by client tier. Retaining top-tier clients (top 20% by revenue) matters far more than retaining small project clients." + seed: "Early-stage retention is volatile because the client base is small — + losing one of three clients is 33% churn. Track retention carefully but + interpret it within the context of a small sample." + series_a: "At 15-30 clients, retention rate becomes statistically meaningful and + a leading indicator of firm health." + series_b_plus: "Mature firms should segment retention by client tier. Retaining + top-tier clients (top 20% by revenue) matters far more than retaining + small project clients." data_sources: - source: "Hinge Research Institute High Growth Study" year: "2023" - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - related_metrics: ["client-concentration", "revenue-per-client", "nps-client"] - related_skills: ["net-promoter-score", "trust-equation"] - caveats: "Retention does not measure revenue retention. A firm can retain 90% of clients while revenue from those clients declines. Track both logo and revenue retention." + related_metrics: [ "client-concentration", "revenue-per-client", "nps-client" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "Retention does not measure revenue retention. A firm can retain 90% of + clients while revenue from those clients declines. Track both logo and + revenue retention." # ───────────────────────────────────────────── # SALES & PIPELINE METRICS @@ -510,182 +716,262 @@ benchmarks: - name: "Average Project Value" id: "average-project-value" category: "sales" - definition: "The mean revenue from a single client engagement, whether a discrete project, a retainer period, or a phase of work." + definition: "The mean revenue from a single client engagement, whether a + discrete project, a retainer period, or a phase of work." formula: "Total project revenue / Number of projects closed" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $5K" - signal: "Micro-projects with high overhead relative to revenue. The firm spends as much time selling and onboarding as delivering." + signal: "Micro-projects with high overhead relative to revenue. The firm spends + as much time selling and onboarding as delivering." below_average: value: "$5K-$15K" - signal: "Small projects. Viable for freelancers but challenging for agencies with overhead. Requires high volume to generate meaningful revenue." + signal: "Small projects. Viable for freelancers but challenging for agencies + with overhead. Requires high volume to generate meaningful revenue." average: value: "$15K-$50K" - signal: "Standard agency project size. Large enough to justify structured delivery and account management." + signal: "Standard agency project size. Large enough to justify structured + delivery and account management." good: value: "$50K-$150K" - signal: "Meaningful engagements that warrant strategic planning, phased delivery, and senior oversight. Typical of mid-market consulting." + signal: "Meaningful engagements that warrant strategic planning, phased + delivery, and senior oversight. Typical of mid-market consulting." excellent: value: "> $150K" - signal: "Large, complex engagements. These projects define the firm's reputation and require sophisticated project management and executive attention." + signal: "Large, complex engagements. These projects define the firm's reputation + and require sophisticated project management and executive attention." stage_notes: - seed: "Small agencies should raise average project value steadily. Moving from $10K to $25K average project size transforms the economics of the business." - series_a: "At $1M-$3M revenue, the firm should have a clear minimum project size and decline work below it. Minimum thresholds reduce operational complexity." - series_b_plus: "Larger agencies use project tiering — small projects ($10K-$50K), medium ($50K-$200K), large ($200K+) — with different delivery models for each." + seed: "Small agencies should raise average project value steadily. Moving from + $10K to $25K average project size transforms the economics of the + business." + series_a: "At $1M-$3M revenue, the firm should have a clear minimum project size + and decline work below it. Minimum thresholds reduce operational + complexity." + series_b_plus: "Larger agencies use project tiering — small projects + ($10K-$50K), medium ($50K-$200K), large ($200K+) — with different + delivery models for each." data_sources: - source: "HubSpot Agency Pricing Report" year: "2024" - source: "Promethean Research Agency Benchmarks" year: "2024" - related_metrics: ["revenue-per-client", "win-rate", "sales-cycle-length"] - related_skills: ["pricing-diagnosis", "competitive-negotiation"] - caveats: "Average project value can be misleading if the firm has a bimodal distribution — many small projects and a few large ones. Examine the distribution, not just the mean." + related_metrics: [ "revenue-per-client", "win-rate", "sales-cycle-length" ] + related_skills: + - competitive-negotiation + caveats: "Average project value can be misleading if the firm has a bimodal + distribution — many small projects and a few large ones. Examine the + distribution, not just the mean." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Pipeline Coverage Ratio" id: "pipeline-coverage-ratio" category: "sales" - definition: "The ratio of total pipeline value to the revenue target for the period, indicating whether the firm has sufficient opportunities to meet its goals." + definition: "The ratio of total pipeline value to the revenue target for the + period, indicating whether the firm has sufficient opportunities to meet + its goals." formula: "Total weighted pipeline value / Revenue target for the period" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 2x" - signal: "Insufficient pipeline. The firm will almost certainly miss its revenue target. Immediate new business development investment is needed." + signal: "Insufficient pipeline. The firm will almost certainly miss its revenue + target. Immediate new business development investment is needed." below_average: value: "2x-3x" - signal: "Thin coverage. Achievable only if win rates are above average. No margin for slippage or delayed decisions." + signal: "Thin coverage. Achievable only if win rates are above average. No + margin for slippage or delayed decisions." average: value: "3x-4x" - signal: "Adequate coverage for most agencies. Provides a reasonable buffer against lost opportunities and delayed client decisions." + signal: "Adequate coverage for most agencies. Provides a reasonable buffer + against lost opportunities and delayed client decisions." good: value: "4x-5x" - signal: "Strong pipeline. The firm can be selective about which opportunities to pursue and negotiate from a position of strength." + signal: "Strong pipeline. The firm can be selective about which opportunities to + pursue and negotiate from a position of strength." excellent: value: "> 5x" - signal: "Robust pipeline. Enables strategic client selection and premium pricing. The firm can decline work that does not align with its positioning." + signal: "Robust pipeline. Enables strategic client selection and premium + pricing. The firm can decline work that does not align with its + positioning." stage_notes: - seed: "Pipeline discipline is rare in small agencies. Even a simple spreadsheet tracking opportunities, probability, and timeline is transformative." - series_a: "At $1M-$3M, formalize the pipeline with stages and probability weights. Weekly pipeline reviews should become a non-negotiable management ritual." - series_b_plus: "Mature agencies track pipeline velocity (how fast deals progress), pipeline quality (weighted by ideal client criteria), and pipeline source (referral vs. outbound vs. inbound)." + seed: "Pipeline discipline is rare in small agencies. Even a simple spreadsheet + tracking opportunities, probability, and timeline is transformative." + series_a: "At $1M-$3M, formalize the pipeline with stages and probability + weights. Weekly pipeline reviews should become a non-negotiable + management ritual." + series_b_plus: "Mature agencies track pipeline velocity (how fast deals + progress), pipeline quality (weighted by ideal client criteria), and + pipeline source (referral vs. outbound vs. inbound)." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Hinge Research Institute High Growth Study" year: "2023" - related_metrics: ["win-rate", "sales-cycle-length", "revenue"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "Pipeline coverage is only meaningful with honest probability weighting. A 5x pipeline filled with unqualified, low-probability opportunities provides false comfort." + related_metrics: [ "win-rate", "sales-cycle-length", "revenue" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "Pipeline coverage is only meaningful with honest probability + weighting. A 5x pipeline filled with unqualified, low-probability + opportunities provides false comfort." - name: "Win Rate" id: "win-rate" category: "sales" - definition: "The percentage of formal proposals or pitches that result in a signed engagement, measuring the firm's competitive effectiveness." + definition: "The percentage of formal proposals or pitches that result in a + signed engagement, measuring the firm's competitive effectiveness." formula: "(Proposals won / Total proposals submitted) x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 20%" - signal: "Four out of five proposals fail. Either the firm is pursuing the wrong opportunities, the proposals are weak, or pricing is misaligned." + signal: "Four out of five proposals fail. Either the firm is pursuing the wrong + opportunities, the proposals are weak, or pricing is misaligned." below_average: value: "20%-30%" - signal: "Below average but not uncommon, especially for agencies that respond to open RFPs. Qualification discipline would improve this metric." + signal: "Below average but not uncommon, especially for agencies that respond to + open RFPs. Qualification discipline would improve this metric." average: value: "30%-40%" - signal: "Standard win rate for agencies with a mix of referral and competitive pitches." + signal: "Standard win rate for agencies with a mix of referral and competitive + pitches." good: value: "40%-55%" - signal: "Strong conversion. The firm is qualifying well, positioning effectively, and pricing competitively." + signal: "Strong conversion. The firm is qualifying well, positioning + effectively, and pricing competitively." excellent: value: "> 55%" - signal: "Exceptional win rate. Indicates strong referral pipeline, expert positioning, or excellent pre-qualification. The firm may not be pitching enough." + signal: "Exceptional win rate. Indicates strong referral pipeline, expert + positioning, or excellent pre-qualification. The firm may not be + pitching enough." stage_notes: - seed: "Early agencies should track win rate from day one. A pattern of losing helps identify positioning weaknesses faster than a pattern of not pitching at all." - series_a: "At $1M-$3M, analyze win rate by source: referral wins should exceed 50%, competitive pitch wins will be lower. If overall rate is below 25%, the firm has a positioning or pricing problem." - series_b_plus: "Mature agencies use win/loss analysis to improve positioning. Interview lost prospects to understand why they chose a competitor." + seed: "Early agencies should track win rate from day one. A pattern of losing + helps identify positioning weaknesses faster than a pattern of not + pitching at all." + series_a: "At $1M-$3M, analyze win rate by source: referral wins should exceed + 50%, competitive pitch wins will be lower. If overall rate is below 25%, + the firm has a positioning or pricing problem." + series_b_plus: "Mature agencies use win/loss analysis to improve positioning. + Interview lost prospects to understand why they chose a competitor." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Hinge Research Institute High Growth Study" year: "2023" - related_metrics: ["pipeline-coverage-ratio", "sales-cycle-length", "average-project-value"] - related_skills: ["competitive-negotiation", "delivering-the-deal"] - caveats: "A very high win rate (>60%) may indicate the firm is only pursuing 'safe' opportunities and not stretching into larger or more prestigious engagements." + related_metrics: [ "pipeline-coverage-ratio", "sales-cycle-length", "average-project-value" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "A very high win rate (>60%) may indicate the firm is only pursuing + 'safe' opportunities and not stretching into larger or more prestigious + engagements." - name: "Sales Cycle Length" id: "sales-cycle-length" category: "sales" - definition: "The average elapsed time from initial qualified contact with a prospect to a signed contract, measuring the speed of the sales process." + definition: "The average elapsed time from initial qualified contact with a + prospect to a signed contract, measuring the speed of the sales process." formula: "Average days from first qualified meeting to contract signature" unit: "days" direction: "lower-is-better" benchmarks: poor: value: "> 120 days" - signal: "Excessively long sales cycle. Either the firm is pursuing enterprise clients without the infrastructure to support long cycles, or decisions are stalling without resolution." + signal: "Excessively long sales cycle. Either the firm is pursuing enterprise + clients without the infrastructure to support long cycles, or + decisions are stalling without resolution." below_average: value: "90-120 days" - signal: "Lengthy for most agency engagements. Acceptable for large, complex projects but a drag on cash flow for standard work." + signal: "Lengthy for most agency engagements. Acceptable for large, complex + projects but a drag on cash flow for standard work." average: value: "45-90 days" - signal: "Typical for mid-market agency work. Allows for proper scoping, proposal development, and client decision-making." + signal: "Typical for mid-market agency work. Allows for proper scoping, proposal + development, and client decision-making." good: value: "21-45 days" - signal: "Efficient sales process. The firm qualifies quickly, proposes clearly, and drives decisions. Typical of firms with strong referral pipelines." + signal: "Efficient sales process. The firm qualifies quickly, proposes clearly, + and drives decisions. Typical of firms with strong referral + pipelines." excellent: value: "< 21 days" - signal: "Rapid conversion. Characteristic of firms selling productized services, working from strong referrals, or engaging repeat clients on new projects." + signal: "Rapid conversion. Characteristic of firms selling productized services, + working from strong referrals, or engaging repeat clients on new + projects." stage_notes: - seed: "Early agencies should aim for short cycles. Long sales cycles consume founder time that should be spent on delivery and relationship building." - series_a: "At $1M-$3M, segment sales cycle by engagement type. Retainer renewals should close in 1-2 weeks; new client projects in 30-60 days." - series_b_plus: "Mature agencies track sales cycle by client tier. Enterprise engagements with procurement involvement will naturally take longer." + seed: "Early agencies should aim for short cycles. Long sales cycles consume + founder time that should be spent on delivery and relationship + building." + series_a: "At $1M-$3M, segment sales cycle by engagement type. Retainer renewals + should close in 1-2 weeks; new client projects in 30-60 days." + series_b_plus: "Mature agencies track sales cycle by client tier. Enterprise + engagements with procurement involvement will naturally take longer." data_sources: - source: "HubSpot Agency Pricing Report" year: "2024" - source: "Promethean Research Agency Benchmarks" year: "2024" - related_metrics: ["win-rate", "pipeline-coverage-ratio"] - related_skills: ["delivering-the-deal", "competitive-negotiation"] - caveats: "Sales cycle length should be measured from the first qualified interaction, not from initial contact. Including unqualified leads inflates the metric and obscures the real conversion timeline." + related_metrics: [ "win-rate", "pipeline-coverage-ratio" ] + related_skills: [ "delivering-the-deal", "competitive-negotiation" ] + caveats: "Sales cycle length should be measured from the first qualified + interaction, not from initial contact. Including unqualified leads + inflates the metric and obscures the real conversion timeline." - name: "Cost per Lead" id: "cost-per-lead" category: "sales" - definition: "The total cost of generating a qualified new business lead, including marketing, business development, events, and content creation costs." - formula: "Total business development and marketing spend / Number of qualified leads generated" + definition: "The total cost of generating a qualified new business lead, + including marketing, business development, events, and content creation + costs." + formula: "Total business development and marketing spend / Number of qualified + leads generated" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $2,000 per lead" - signal: "Extremely expensive lead generation. At this cost, the firm needs very high average project values and win rates to achieve positive ROI on business development." + signal: "Extremely expensive lead generation. At this cost, the firm needs very + high average project values and win rates to achieve positive ROI on + business development." below_average: value: "$1,000-$2,000" - signal: "Elevated cost. Acceptable for agencies targeting enterprise clients with $100K+ engagements, but expensive for mid-market firms." + signal: "Elevated cost. Acceptable for agencies targeting enterprise clients + with $100K+ engagements, but expensive for mid-market firms." average: value: "$500-$1,000" - signal: "Reasonable lead cost for most professional services firms. Achievable through a mix of content marketing, networking, and selective paid channels." + signal: "Reasonable lead cost for most professional services firms. Achievable + through a mix of content marketing, networking, and selective paid + channels." good: value: "$200-$500" - signal: "Efficient lead generation. Typically driven by strong referral networks, thought leadership content, and organic reputation." + signal: "Efficient lead generation. Typically driven by strong referral + networks, thought leadership content, and organic reputation." excellent: value: "< $200 per lead" - signal: "Highly efficient. Usually indicates a strong referral engine or dominant thought leadership position that generates inbound interest at low cost." + signal: "Highly efficient. Usually indicates a strong referral engine or + dominant thought leadership position that generates inbound interest + at low cost." stage_notes: - seed: "Most early agencies spend $0 on formal lead generation — leads come from the founder's network. Track the implicit cost of the founder's time on business development." - series_a: "At $1M-$3M, begin tracking lead source and cost by channel. Referrals are typically the cheapest and highest-converting source." - series_b_plus: "Mature agencies diversify lead sources while monitoring cost per lead by channel. Content marketing and speaking engagements often deliver the best long-term CPL." + seed: "Most early agencies spend $0 on formal lead generation — leads come from + the founder's network. Track the implicit cost of the founder's time on + business development." + series_a: "At $1M-$3M, begin tracking lead source and cost by channel. Referrals + are typically the cheapest and highest-converting source." + series_b_plus: "Mature agencies diversify lead sources while monitoring cost per + lead by channel. Content marketing and speaking engagements often + deliver the best long-term CPL." data_sources: - source: "HubSpot Agency Pricing Report" year: "2024" - source: "Hinge Research Institute High Growth Study" year: "2023" - related_metrics: ["win-rate", "pipeline-coverage-ratio", "average-project-value"] - related_skills: ["four-ps-marketing", "business-model-canvas"] - caveats: "Many agencies undercount lead cost by ignoring the opportunity cost of senior staff time spent on business development. A partner spending 30% of their time on BD has a real cost even if no cash is spent on marketing." + related_metrics: [ "win-rate", "pipeline-coverage-ratio", "average-project-value" ] + related_skills: [ "four-ps-marketing", "business-model-canvas" ] + caveats: "Many agencies undercount lead cost by ignoring the opportunity cost of + senior staff time spent on business development. A partner spending 30% of + their time on BD has a real cost even if no cash is spent on marketing." # ───────────────────────────────────────────── # PEOPLE & TALENT METRICS @@ -694,146 +980,212 @@ benchmarks: - name: "Employee Retention Rate" id: "employee-retention-rate" category: "retention" - definition: "The percentage of employees who remain with the firm over a twelve-month period, measuring talent stability and organizational health." - formula: "(Employees at end of period - New hires during period) / Employees at start of period x 100" + definition: "The percentage of employees who remain with the firm over a + twelve-month period, measuring talent stability and organizational + health." + formula: "(Employees at end of period - New hires during period) / Employees at + start of period x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 70%" - signal: "Crisis-level attrition. Nearly a third of the team leaves annually. Client relationships, institutional knowledge, and delivery quality all suffer." + signal: "Crisis-level attrition. Nearly a third of the team leaves annually. + Client relationships, institutional knowledge, and delivery quality + all suffer." below_average: value: "70%-80%" - signal: "Elevated turnover. The firm is spending excessive time and money on recruiting and onboarding replacements. Key client relationships may be at risk." + signal: "Elevated turnover. The firm is spending excessive time and money on + recruiting and onboarding replacements. Key client relationships may + be at risk." average: value: "80%-85%" - signal: "Industry-standard retention for agencies. Some turnover is natural as junior staff advance their careers." + signal: "Industry-standard retention for agencies. Some turnover is natural as + junior staff advance their careers." good: value: "85%-92%" - signal: "Strong retention indicating healthy culture, competitive compensation, and meaningful work." + signal: "Strong retention indicating healthy culture, competitive compensation, + and meaningful work." excellent: value: "> 92%" - signal: "Exceptional loyalty. The firm is a destination employer in its market. Key staff departures are rare and managed proactively." + signal: "Exceptional loyalty. The firm is a destination employer in its market. + Key staff departures are rare and managed proactively." stage_notes: - seed: "At under 10 people, every departure is destabilizing. Retention is existential — losing one of five people is a 20% attrition event." - series_a: "At 10-25 people, institute stay interviews, not just exit interviews. Understand why people stay and reinforce those factors." - series_b_plus: "Track retention by seniority tier. Losing junior staff at 15% annually is manageable. Losing senior staff at 15% is a crisis." + seed: "At under 10 people, every departure is destabilizing. Retention is + existential — losing one of five people is a 20% attrition event." + series_a: "At 10-25 people, institute stay interviews, not just exit interviews. + Understand why people stay and reinforce those factors." + series_b_plus: "Track retention by seniority tier. Losing junior staff at 15% + annually is manageable. Losing senior staff at 15% is a crisis." data_sources: - source: "Bureau of Labor Statistics — Professional Services" year: "2024" - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - related_metrics: ["enps", "revenue-per-employee", "leverage-ratio"] - related_skills: ["inspiring-and-retaining", "organisational-culture"] - caveats: "Aggregate retention masks 'regrettable' versus 'non-regrettable' attrition. Track whether departures are top performers (regrettable) or underperformers (often healthy). The quality of retention matters as much as the rate." + related_metrics: [ "enps", "revenue-per-employee", "leverage-ratio" ] + related_skills: [ "inspiring-and-retaining", "organisational-culture" ] + caveats: "Aggregate retention masks 'regrettable' versus 'non-regrettable' + attrition. Track whether departures are top performers (regrettable) or + underperformers (often healthy). The quality of retention matters as much + as the rate." - name: "Revenue per Partner/Principal" id: "revenue-per-partner" category: "efficiency" - definition: "Total firm revenue divided by the number of partners, principals, or senior leaders, measuring the revenue-generation capacity of the leadership team." + definition: "Total firm revenue divided by the number of partners, principals, + or senior leaders, measuring the revenue-generation capacity of the + leadership team." formula: "Annual revenue / Number of partners or principals" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $500K per partner" - signal: "Partners are not generating sufficient revenue to justify their compensation and the overhead they represent." + signal: "Partners are not generating sufficient revenue to justify their + compensation and the overhead they represent." below_average: value: "$500K-$750K" - signal: "Below the threshold for competitive partner compensation in most markets. The firm may have too many partners relative to its revenue base." + signal: "Below the threshold for competitive partner compensation in most + markets. The firm may have too many partners relative to its revenue + base." average: value: "$750K-$1.2M" - signal: "Sustainable revenue per partner. Supports competitive compensation and modest reinvestment in the firm." + signal: "Sustainable revenue per partner. Supports competitive compensation and + modest reinvestment in the firm." good: value: "$1.2M-$2M" - signal: "Strong partner productivity. Partners are effectively leveraging teams and winning significant work." + signal: "Strong partner productivity. Partners are effectively leveraging teams + and winning significant work." excellent: value: "> $2M per partner" - signal: "Exceptional leverage. Partners are managing large teams and major accounts. Typical of management consultancies and large agencies with strong brands." + signal: "Exceptional leverage. Partners are managing large teams and major + accounts. Typical of management consultancies and large agencies with + strong brands." stage_notes: - seed: "For solo consultants, this metric equals total revenue. It becomes meaningful when the firm adds a second partner or principal." - series_a: "At the point of adding partners, this metric determines whether the firm can afford them. A partner should generate at least $750K within their first full year." - series_b_plus: "Mature firms use revenue per partner as a promotion criterion. Partners who consistently fall below the threshold are a drag on firm economics." + seed: "For solo consultants, this metric equals total revenue. It becomes + meaningful when the firm adds a second partner or principal." + series_a: "At the point of adding partners, this metric determines whether the + firm can afford them. A partner should generate at least $750K within + their first full year." + series_b_plus: "Mature firms use revenue per partner as a promotion criterion. + Partners who consistently fall below the threshold are a drag on firm + economics." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "David C. Baker / ReCourses — agency economics" year: "2024" - related_metrics: ["revenue-per-employee", "leverage-ratio"] - related_skills: ["leadership-pipeline", "delegation-and-empowerment"] - caveats: "Revenue per partner varies enormously by firm type. A solo-practice consultant at $400K is healthy; a partner at a 50-person agency at $400K is underperforming. Always benchmark within the firm's context." + related_metrics: [ "revenue-per-employee", "leverage-ratio" ] + related_skills: [ "leadership-pipeline", "delegation-and-empowerment" ] + caveats: "Revenue per partner varies enormously by firm type. A solo-practice + consultant at $400K is healthy; a partner at a 50-person agency at $400K + is underperforming. Always benchmark within the firm's context." - name: "Leverage Ratio" id: "leverage-ratio" category: "efficiency" - definition: "The ratio of junior billable staff to senior billable staff (partners, principals, directors), measuring the firm's ability to scale expertise through staffing structure." - formula: "Number of junior/mid-level billable staff / Number of senior staff (partners, principals, directors)" + definition: "The ratio of junior billable staff to senior billable staff + (partners, principals, directors), measuring the firm's ability to scale + expertise through staffing structure." + formula: "Number of junior/mid-level billable staff / Number of senior staff + (partners, principals, directors)" unit: "ratio" direction: "target-range" benchmarks: poor: value: "< 2:1" - signal: "Top-heavy firm. Too many senior staff relative to junior. Margins are compressed because high-cost talent does work that lower-cost staff could handle." + signal: "Top-heavy firm. Too many senior staff relative to junior. Margins are + compressed because high-cost talent does work that lower-cost staff + could handle." below_average: value: "2:1 to 3:1" - signal: "Low leverage. The firm is not fully utilizing the capacity of senior staff to supervise and develop junior talent." + signal: "Low leverage. The firm is not fully utilizing the capacity of senior + staff to supervise and develop junior talent." average: value: "3:1 to 5:1" - signal: "Balanced leverage for most consulting and agency models. Senior staff can oversee work quality while junior staff handle execution." + signal: "Balanced leverage for most consulting and agency models. Senior staff + can oversee work quality while junior staff handle execution." good: value: "5:1 to 8:1" - signal: "Strong leverage. Seniors focus on client relationships, quality, and sales while junior staff execute. Margins benefit from the cost differential." + signal: "Strong leverage. Seniors focus on client relationships, quality, and + sales while junior staff execute. Margins benefit from the cost + differential." excellent: value: "> 8:1" - signal: "High leverage. Typical of staffing firms or agencies with highly standardized delivery models. Requires robust training and quality control systems." + signal: "High leverage. Typical of staffing firms or agencies with highly + standardized delivery models. Requires robust training and quality + control systems." stage_notes: - seed: "Leverage is irrelevant for solo consultants and becomes meaningful only after the first few junior hires." - series_a: "At 10-25 people, deliberately design the leverage model. Each senior person should manage 3-5 junior staff. Hiring a senior person without a team to leverage is economically inefficient." - series_b_plus: "Mature firms explicitly manage leverage as a profit driver. Every percentage point shift from senior to junior delivery (at maintained quality) flows directly to margin." + seed: "Leverage is irrelevant for solo consultants and becomes meaningful only + after the first few junior hires." + series_a: "At 10-25 people, deliberately design the leverage model. Each senior + person should manage 3-5 junior staff. Hiring a senior person without a + team to leverage is economically inefficient." + series_b_plus: "Mature firms explicitly manage leverage as a profit driver. + Every percentage point shift from senior to junior delivery (at + maintained quality) flows directly to margin." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "David C. Baker / ReCourses — agency economics" year: "2024" - related_metrics: ["revenue-per-partner", "gross-margin", "revenue-per-employee"] - related_skills: ["shamrock-organisation", "leadership-pipeline"] - caveats: "High leverage only works if the firm invests in training, methodology, and quality control. Without these, leverage becomes a euphemism for letting inexperienced staff do senior work poorly." + related_metrics: [ "revenue-per-partner", "gross-margin", "revenue-per-employee" ] + related_skills: [ "shamrock-organisation", "leadership-pipeline" ] + caveats: "High leverage only works if the firm invests in training, methodology, + and quality control. Without these, leverage becomes a euphemism for + letting inexperienced staff do senior work poorly." - name: "Overhead Ratio" id: "overhead-ratio" category: "financial" - definition: "Total non-delivery overhead costs (rent, administration, non-billable salaries, technology, insurance, marketing) as a percentage of revenue." + definition: "Total non-delivery overhead costs (rent, administration, + non-billable salaries, technology, insurance, marketing) as a percentage + of revenue." formula: "Total overhead costs / Revenue x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 45%" - signal: "Overhead consuming nearly half of revenue. Even with healthy gross margins, profitability is crushed by excessive non-delivery costs." + signal: "Overhead consuming nearly half of revenue. Even with healthy gross + margins, profitability is crushed by excessive non-delivery costs." below_average: value: "35%-45%" - signal: "Elevated overhead. Common in firms with expensive office space, large non-billable staff, or excessive technology spend." + signal: "Elevated overhead. Common in firms with expensive office space, large + non-billable staff, or excessive technology spend." average: value: "25%-35%" - signal: "Typical overhead range for professional services firms. Manageable if gross margin is healthy." + signal: "Typical overhead range for professional services firms. Manageable if + gross margin is healthy." good: value: "18%-25%" - signal: "Lean overhead. The firm runs efficiently with minimal non-delivery costs. Often achieved by remote-first firms or those with minimal office space." + signal: "Lean overhead. The firm runs efficiently with minimal non-delivery + costs. Often achieved by remote-first firms or those with minimal + office space." excellent: value: "< 18%" - signal: "Ultra-lean overhead. Typical of virtual agencies, solo consultancies with minimal infrastructure, or firms that have ruthlessly eliminated non-productive costs." + signal: "Ultra-lean overhead. Typical of virtual agencies, solo consultancies + with minimal infrastructure, or firms that have ruthlessly eliminated + non-productive costs." stage_notes: - seed: "Solo consultants naturally have low overhead. Track overhead percentage from the start to establish a baseline before it creeps up." - series_a: "The first office lease, the first full-time operations hire, and the first CRM subscription represent overhead step-changes. Ensure each addition is justified by revenue capacity." - series_b_plus: "At scale, overhead ratio is the primary controllable lever for EBITDA improvement. Conduct an annual overhead audit to identify costs that no longer deliver value." + seed: "Solo consultants naturally have low overhead. Track overhead percentage + from the start to establish a baseline before it creeps up." + series_a: "The first office lease, the first full-time operations hire, and the + first CRM subscription represent overhead step-changes. Ensure each + addition is justified by revenue capacity." + series_b_plus: "At scale, overhead ratio is the primary controllable lever for + EBITDA improvement. Conduct an annual overhead audit to identify costs + that no longer deliver value." data_sources: - source: "Deltek Clarity Industry Study" year: "2023" - source: "Agency Management Institute Financial Benchmarks" year: "2023" - related_metrics: ["ebitda-margin", "gross-margin", "revenue-per-employee"] - related_skills: ["eisenhower-matrix", "balanced-scorecard"] - caveats: "Some overhead is investment (marketing, training, R&D). Cutting all overhead to minimize the ratio can starve the firm of growth capability. Distinguish between productive overhead and waste." + related_metrics: [ "ebitda-margin", "gross-margin", "revenue-per-employee" ] + related_skills: [ "eisenhower-matrix", "balanced-scorecard" ] + caveats: "Some overhead is investment (marketing, training, R&D). Cutting all + overhead to minimize the ratio can starve the firm of growth capability. + Distinguish between productive overhead and waste." # ───────────────────────────────────────────── # PROJECT & DELIVERY METRICS @@ -842,74 +1194,110 @@ benchmarks: - name: "Scope Creep Rate" id: "scope-creep-rate" category: "efficiency" - definition: "The percentage of projects that exceed their original scope, budget, or timeline by more than 10%, measuring the firm's scoping and project management discipline." - formula: "(Projects exceeding original scope by >10% / Total projects completed) x 100" + definition: "The percentage of projects that exceed their original scope, + budget, or timeline by more than 10%, measuring the firm's scoping and + project management discipline." + formula: "(Projects exceeding original scope by >10% / Total projects completed) + x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 50%" - signal: "More than half of projects overrun. This is a systemic scoping, negotiation, or project management failure that directly erodes margins." + signal: "More than half of projects overrun. This is a systemic scoping, + negotiation, or project management failure that directly erodes + margins." below_average: value: "35%-50%" - signal: "Frequent scope creep. The firm is likely absorbing significant unbilled work. Effective rate realization is depressed." + signal: "Frequent scope creep. The firm is likely absorbing significant unbilled + work. Effective rate realization is depressed." average: value: "20%-35%" - signal: "Moderate scope creep. Some overruns are inevitable, but at this level the firm should have change-order processes that capture additional scope as additional revenue." + signal: "Moderate scope creep. Some overruns are inevitable, but at this level + the firm should have change-order processes that capture additional + scope as additional revenue." good: value: "10%-20%" - signal: "Well-managed scope. The firm scopes accurately, communicates boundaries clearly, and uses change orders effectively." + signal: "Well-managed scope. The firm scopes accurately, communicates boundaries + clearly, and uses change orders effectively." excellent: value: "< 10%" - signal: "Exceptional scope discipline. Nearly all projects deliver within the original parameters. Characteristic of firms with mature methodologies and experienced project managers." + signal: "Exceptional scope discipline. Nearly all projects deliver within the + original parameters. Characteristic of firms with mature methodologies + and experienced project managers." stage_notes: - seed: "Early agencies frequently underscope because they want to impress clients and lack experience with estimation. Track actuals versus estimates from the first project." - series_a: "At $1M-$3M, implement formal change-order processes. Every scope expansion should be documented and either billed or explicitly absorbed as an investment." - series_b_plus: "Mature agencies use scope creep data to improve estimation accuracy, identify which project types and client types are most prone to overruns, and adjust pricing accordingly." + seed: "Early agencies frequently underscope because they want to impress clients + and lack experience with estimation. Track actuals versus estimates from + the first project." + series_a: "At $1M-$3M, implement formal change-order processes. Every scope + expansion should be documented and either billed or explicitly absorbed + as an investment." + series_b_plus: "Mature agencies use scope creep data to improve estimation + accuracy, identify which project types and client types are most prone + to overruns, and adjust pricing accordingly." data_sources: - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - source: "Deltek Clarity Industry Study" year: "2023" - related_metrics: ["effective-billable-rate", "gross-margin"] - related_skills: ["competitive-negotiation", "delivering-the-deal"] - caveats: "Not all scope expansion is negative. Strategic scope extension on a key account can deepen the relationship and lead to expansion. The issue is unmanaged scope creep — work that is neither billed nor strategically justified." + related_metrics: [ "effective-billable-rate", "gross-margin" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "Not all scope expansion is negative. Strategic scope extension on a + key account can deepen the relationship and lead to expansion. The issue + is unmanaged scope creep — work that is neither billed nor strategically + justified." - name: "Accounts Receivable Days" id: "ar-days" category: "financial" - definition: "The average number of days between invoicing and payment collection, measuring cash collection efficiency." + definition: "The average number of days between invoicing and payment + collection, measuring cash collection efficiency." formula: "(Accounts Receivable / Annual Revenue) x 365" unit: "days" direction: "lower-is-better" benchmarks: poor: value: "> 75 days" - signal: "Dangerously slow collections. The firm is financing client operations with its own cash. Cash flow crises are likely." + signal: "Dangerously slow collections. The firm is financing client operations + with its own cash. Cash flow crises are likely." below_average: value: "60-75 days" - signal: "Elevated AR. The firm is extending significant implicit credit to clients. Cash flow is strained, especially during growth periods." + signal: "Elevated AR. The firm is extending significant implicit credit to + clients. Cash flow is strained, especially during growth periods." average: value: "45-60 days" - signal: "Typical for agencies billing on net-30 terms with some payment delays. Manageable but room for improvement." + signal: "Typical for agencies billing on net-30 terms with some payment delays. + Manageable but room for improvement." good: value: "30-45 days" - signal: "Healthy cash collection. Clients pay within terms. The firm has adequate cash flow to meet payroll and operating expenses." + signal: "Healthy cash collection. Clients pay within terms. The firm has + adequate cash flow to meet payroll and operating expenses." excellent: value: "< 30 days" - signal: "Excellent cash discipline. Achieved through upfront deposits, milestone-based billing, retainer pre-payment, or credit card billing." + signal: "Excellent cash discipline. Achieved through upfront deposits, + milestone-based billing, retainer pre-payment, or credit card + billing." stage_notes: - seed: "Cash flow kills more agencies than lack of revenue. Require deposits (25-50% upfront) on all new projects from day one. Never start work without a signed contract and deposit." - series_a: "At $1M-$3M, AR management becomes a dedicated function. Late-paying clients should be flagged, followed up, and — for chronic offenders — moved to pre-payment or retainer terms." - series_b_plus: "Mature agencies negotiate payment terms as actively as they negotiate rates. Net-15 or retainer pre-payment structures dramatically improve cash position." + seed: "Cash flow kills more agencies than lack of revenue. Require deposits + (25-50% upfront) on all new projects from day one. Never start work + without a signed contract and deposit." + series_a: "At $1M-$3M, AR management becomes a dedicated function. Late-paying + clients should be flagged, followed up, and — for chronic offenders — + moved to pre-payment or retainer terms." + series_b_plus: "Mature agencies negotiate payment terms as actively as they + negotiate rates. Net-15 or retainer pre-payment structures dramatically + improve cash position." data_sources: - source: "Deltek Clarity Industry Study" year: "2023" - source: "Agency Management Institute Financial Benchmarks" year: "2023" - related_metrics: ["ebitda-margin", "revenue"] - related_skills: ["competitive-negotiation", "delivering-the-deal"] - caveats: "AR days can be artificially improved by front-loading billing (billing before work is complete) or worsened by client-imposed payment terms (net-60 or net-90 at large enterprises). Understand the underlying payment dynamics, not just the number." + related_metrics: [ "ebitda-margin", "revenue" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "AR days can be artificially improved by front-loading billing (billing + before work is complete) or worsened by client-imposed payment terms + (net-60 or net-90 at large enterprises). Understand the underlying payment + dynamics, not just the number." # ───────────────────────────────────────────── # SATISFACTION & LOYALTY METRICS @@ -918,71 +1306,99 @@ benchmarks: - name: "Client NPS" id: "nps-client" category: "retention" - definition: "Net Promoter Score measured among the firm's client contacts, indicating client satisfaction and likelihood to refer." + definition: "Net Promoter Score measured among the firm's client contacts, + indicating client satisfaction and likelihood to refer." formula: "% Promoters (9-10) - % Detractors (0-6) on a 0-10 recommendation scale" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 20" - signal: "Clients are dissatisfied or indifferent. Referrals will be rare and churn is likely. The firm has a service quality or relationship problem." + signal: "Clients are dissatisfied or indifferent. Referrals will be rare and + churn is likely. The firm has a service quality or relationship + problem." below_average: value: "20-35" - signal: "Below average satisfaction. Some clients are happy, but a meaningful portion would not recommend the firm." + signal: "Below average satisfaction. Some clients are happy, but a meaningful + portion would not recommend the firm." average: value: "35-50" - signal: "Acceptable satisfaction. Clients are generally content but the firm is not generating the enthusiasm that drives organic referrals." + signal: "Acceptable satisfaction. Clients are generally content but the firm is + not generating the enthusiasm that drives organic referrals." good: value: "50-70" - signal: "Strong client advocacy. Clients actively recommend the firm to peers. Referral pipeline should be healthy." + signal: "Strong client advocacy. Clients actively recommend the firm to peers. + Referral pipeline should be healthy." excellent: value: "> 70" - signal: "Exceptional client loyalty. The firm is a trusted partner whose clients enthusiastically advocate for it. This is the strongest growth engine in professional services." + signal: "Exceptional client loyalty. The firm is a trusted partner whose clients + enthusiastically advocate for it. This is the strongest growth engine + in professional services." stage_notes: - seed: "Even with 3-5 clients, measuring NPS establishes a feedback discipline. Use the qualitative follow-up question to understand what drives satisfaction." - series_a: "At 15-30 clients, NPS becomes predictive. Segment by engagement type (project vs. retainer) and client tier. Retainer client NPS should be higher." - series_b_plus: "Mature agencies tie NPS to account manager performance and use detractor feedback to drive operational improvements." + seed: "Even with 3-5 clients, measuring NPS establishes a feedback discipline. + Use the qualitative follow-up question to understand what drives + satisfaction." + series_a: "At 15-30 clients, NPS becomes predictive. Segment by engagement type + (project vs. retainer) and client tier. Retainer client NPS should be + higher." + series_b_plus: "Mature agencies tie NPS to account manager performance and use + detractor feedback to drive operational improvements." data_sources: - source: "Hinge Research Institute High Growth Study" year: "2023" - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - related_metrics: ["client-retention-rate", "revenue-per-client"] - related_skills: ["net-promoter-score", "trust-equation"] - caveats: "NPS in agencies is relationship-dependent — the score often reflects the quality of the account manager or lead consultant rather than the firm as a whole. Survey multiple contacts per client for a balanced view." + related_metrics: [ "client-retention-rate", "revenue-per-client" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "NPS in agencies is relationship-dependent — the score often reflects + the quality of the account manager or lead consultant rather than the firm + as a whole. Survey multiple contacts per client for a balanced view." - name: "Employee NPS (eNPS)" id: "enps" category: "retention" - definition: "Net Promoter Score measured among the firm's employees, indicating satisfaction, engagement, and likelihood to recommend the firm as an employer." + definition: "Net Promoter Score measured among the firm's employees, indicating + satisfaction, engagement, and likelihood to recommend the firm as an + employer." formula: "% Employee Promoters (9-10) - % Employee Detractors (0-6)" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 0" - signal: "More detractors than promoters. The firm has a serious culture, compensation, or management problem. Attrition will accelerate." + signal: "More detractors than promoters. The firm has a serious culture, + compensation, or management problem. Attrition will accelerate." below_average: value: "0-15" - signal: "Net positive but weak. Employees are not enthusiastic advocates. Vulnerability to external offers is high." + signal: "Net positive but weak. Employees are not enthusiastic advocates. + Vulnerability to external offers is high." average: value: "15-30" - signal: "Decent employee satisfaction. The firm is a reasonable place to work but not a destination employer." + signal: "Decent employee satisfaction. The firm is a reasonable place to work + but not a destination employer." good: value: "30-50" - signal: "Strong employee advocacy. Staff recommend the firm to talented friends — a powerful recruiting advantage." + signal: "Strong employee advocacy. Staff recommend the firm to talented friends + — a powerful recruiting advantage." excellent: value: "> 50" - signal: "Exceptional employer brand. Recruiting is easier, retention is strong, and employee engagement drives client satisfaction." + signal: "Exceptional employer brand. Recruiting is easier, retention is strong, + and employee engagement drives client satisfaction." stage_notes: - seed: "At under 10 people, formal eNPS is less relevant than direct, honest conversations. Institute monthly check-ins with every team member." - series_a: "At 10-25 people, quarterly eNPS surveys provide a scalable feedback mechanism. Pair quantitative scores with open-ended qualitative input." - series_b_plus: "At 50+, eNPS becomes a leading indicator of attrition, client satisfaction, and firm performance. Track and act on it with the same rigor as financial metrics." + seed: "At under 10 people, formal eNPS is less relevant than direct, honest + conversations. Institute monthly check-ins with every team member." + series_a: "At 10-25 people, quarterly eNPS surveys provide a scalable feedback + mechanism. Pair quantitative scores with open-ended qualitative input." + series_b_plus: "At 50+, eNPS becomes a leading indicator of attrition, client + satisfaction, and firm performance. Track and act on it with the same + rigor as financial metrics." data_sources: - source: "Bureau of Labor Statistics — Professional Services" year: "2024" - source: "SPI Research Professional Services Maturity Benchmark" year: "2024" - related_metrics: ["employee-retention-rate", "nps-client"] - related_skills: ["organisational-culture", "psychological-safety-practice"] - caveats: "eNPS is a lagging indicator — by the time it drops, the damage is done. Pair eNPS with leading indicators: Glassdoor reviews, offer acceptance rate, and informal sentiment from managers." + related_metrics: [ "employee-retention-rate", "nps-client" ] + related_skills: [ "organisational-culture", "psychological-safety-practice" ] + caveats: "eNPS is a lagging indicator — by the time it drops, the damage is + done. Pair eNPS with leading indicators: Glassdoor reviews, offer + acceptance rate, and informal sentiment from managers." diff --git a/.claude/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml b/.claude/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml index 775223a..2c9e63e 100644 --- a/.claude/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml +++ b/.claude/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml @@ -39,49 +39,95 @@ diagnostic_rules: - diagnostic: "customer-churn-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Client churn in agencies is fundamentally different from subscription churn. Clients do not 'cancel' — they finish a project and do not return, reduce retainer scope, bring work in-house, or quietly move to a competitor. Churn in agencies is often invisible until the revenue impact materializes months later. The triage must address agency-specific churn drivers: relationship quality, deliverable satisfaction, internal champion departure, budget cuts, and the ever-present threat of in-house teams." + adaptation_rationale: "Client churn in agencies is fundamentally different from + subscription churn. Clients do not 'cancel' — they finish a project and do + not return, reduce retainer scope, bring work in-house, or quietly move to + a competitor. Churn in agencies is often invisible until the revenue + impact materializes months later. The triage must address agency-specific + churn drivers: relationship quality, deliverable satisfaction, internal + champion departure, budget cuts, and the ever-present threat of in-house + teams." additional_triage_questions: - - question: "When clients leave, do they explicitly terminate (tell you they are leaving) or silently attrit (stop calling, reduce scope, let the retainer lapse without renewal)?" - purpose: "Silent attrition is far more common in agencies than explicit termination. Clients avoid confrontation by gradually reducing engagement. Detecting silent attrition requires proactive relationship health monitoring." - routing_impact: "Silent attrition routes to trust-equation and net-promoter-score for relationship health assessment. Explicit termination routes to competitive-threat-diagnosis and root cause analysis." - - question: "Has the departing client's internal champion (your primary contact) changed roles, left the company, or been reorganized?" - purpose: "Agency relationships are person-to-person. When the champion leaves, the relationship often dies — the replacement may have their own agency preferences or may not value the existing engagement." - routing_impact: "Champion departure routes to stakeholder-map and relationship diversification strategy. Ensure multiple relationships within each client organization." - - question: "Are clients leaving because they are bringing the capability in-house?" - purpose: "In-housing is the structural threat to agency models. If multiple clients are building internal teams to replace agency services, the agency's core offering may be commoditizing." - routing_impact: "In-housing trend routes to disruptive-innovation and blue-ocean-strategy for repositioning above the in-house capability level." + - question: "When clients leave, do they explicitly terminate (tell you they are + leaving) or silently attrit (stop calling, reduce scope, let the + retainer lapse without renewal)?" + purpose: "Silent attrition is far more common in agencies than explicit + termination. Clients avoid confrontation by gradually reducing + engagement. Detecting silent attrition requires proactive relationship + health monitoring." + routing_impact: "Silent attrition routes to trust-equation and + net-promoter-score for relationship health assessment. Explicit + termination routes to competitive-threat-diagnosis and root cause + analysis." + - question: "Has the departing client's internal champion (your primary contact) + changed roles, left the company, or been reorganized?" + purpose: "Agency relationships are person-to-person. When the champion leaves, + the relationship often dies — the replacement may have their own + agency preferences or may not value the existing engagement." + routing_impact: "Champion departure routes to stakeholder-map and relationship + diversification strategy. Ensure multiple relationships within each + client organization." + - question: "Are clients leaving because they are bringing the capability + in-house?" + purpose: "In-housing is the structural threat to agency models. If multiple + clients are building internal teams to replace agency services, the + agency's core offering may be commoditizing." + routing_impact: "In-housing trend routes to disruptive-innovation and + blue-ocean-strategy for repositioning above the in-house capability + level." diagnosis_weight_shifts: more_likely: - diagnosis: "Relationship-driven churn" - reason: "In agencies, most churn is relationship-driven rather than quality-driven. The work may be excellent, but if the client does not feel personally valued, connected, and heard, they will move to a firm that provides that feeling." + reason: "In agencies, most churn is relationship-driven rather than + quality-driven. The work may be excellent, but if the client does + not feel personally valued, connected, and heard, they will move to + a firm that provides that feeling." - diagnosis: "Value perception gap" - reason: "Agencies frequently fail to communicate the value they deliver. When clients do not see the connection between agency fees and business outcomes, they question the expenditure — especially during budget reviews." + reason: "Agencies frequently fail to communicate the value they deliver. When + clients do not see the connection between agency fees and business + outcomes, they question the expenditure — especially during budget + reviews." less_likely: - diagnosis: "Product quality failure" - reason: "Agencies can adjust quality in real time through feedback loops. Chronic quality failure is less common than relationship neglect or value communication failure." + reason: "Agencies can adjust quality in real time through feedback loops. + Chronic quality failure is less common than relationship neglect or + value communication failure." agency_specific_diagnoses: - name: "Silent attrition — the invisible churn" - description: "Clients are not formally leaving but are gradually disengaging: reducing retainer scope, declining project extensions, responding slowly to outreach, and shifting work to other providers without explicit notification." + description: "Clients are not formally leaving but are gradually disengaging: + reducing retainer scope, declining project extensions, responding + slowly to outreach, and shifting work to other providers without + explicit notification." symptoms: - "Retainer scope reductions without clear explanation" - "Longer gaps between engagements with previously active clients" - "Client contacts becoming unresponsive to proactive outreach" - - "Revenue per client declining across the portfolio without explicit client departures" - routes_to_skills: ["trust-equation", "net-promoter-score", "connecting-with-people"] - routes_to_templates: ["quarterly-business-review", "project-status-update"] + - "Revenue per client declining across the portfolio without explicit + client departures" + routes_to_skills: [ "trust-equation", "net-promoter-score", "connecting-with-people" ] + routes_to_templates: [ "quarterly-business-review", "project-status-update" ] - name: "In-housing displacement" - description: "Clients are building internal teams to replace agency services. This is a structural shift, not a temporary budget reallocation. The agency's core service is being commoditized to the point where clients prefer to hire permanent staff rather than pay agency rates." + description: "Clients are building internal teams to replace agency services. + This is a structural shift, not a temporary budget reallocation. The + agency's core service is being commoditized to the point where clients + prefer to hire permanent staff rather than pay agency rates." symptoms: - - "Multiple clients hiring for roles that mirror the agency's core service" + - "Multiple clients hiring for roles that mirror the agency's core + service" - "Clients requesting knowledge transfer or documentation of processes" - - "Budget objections citing 'we could hire someone full-time for what we pay you annually'" - - "Decline concentrated in one service line rather than across the board" - routes_to_skills: ["disruptive-innovation", "blue-ocean-strategy", "product-life-cycle"] - routes_to_templates: ["strategic-analysis-one-pager", "proposal-outline"] + - "Budget objections citing 'we could hire someone full-time for what + we pay you annually'" + - "Decline concentrated in one service line rather than across the + board" + routes_to_skills: [ "disruptive-innovation", "blue-ocean-strategy", "product-life-cycle" ] + routes_to_templates: [ "strategic-analysis-one-pager", "proposal-outline" ] sector_red_flags: - - "Client retention below 70% annually — the firm is on a treadmill, replacing clients faster than it can deepen relationships." - - "Three or more clients reducing retainer scope in the same quarter — early signal of a systemic value perception problem." - - "Key client champion departures without a relationship-transfer plan — each departure is a churn risk that compounds if unaddressed." + - "Client retention below 70% annually — the firm is on a treadmill, + replacing clients faster than it can deepen relationships." + - "Three or more clients reducing retainer scope in the same quarter — + early signal of a systemic value perception problem." + - "Key client champion departures without a relationship-transfer plan — + each departure is a churn risk that compounds if unaddressed." # ───────────────────────────────────────────── # 2. GROWTH STALL DIAGNOSIS @@ -89,58 +135,119 @@ diagnostic_rules: - diagnostic: "growth-stall-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Agency growth stalls have characteristic causes that differ fundamentally from product business stalls. Agency growth is constrained by three ceilings: the founder's personal capacity (cannot sell and deliver simultaneously), talent availability (cannot hire fast enough to meet demand), and client acquisition (pipeline dries up when delivery consumes all attention). The most common stall pattern is the feast-or-famine cycle — the agency is too busy delivering to develop new business, then too desperate to be selective about incoming work." + adaptation_rationale: "Agency growth stalls have characteristic causes that + differ fundamentally from product business stalls. Agency growth is + constrained by three ceilings: the founder's personal capacity (cannot + sell and deliver simultaneously), talent availability (cannot hire fast + enough to meet demand), and client acquisition (pipeline dries up when + delivery consumes all attention). The most common stall pattern is the + feast-or-famine cycle — the agency is too busy delivering to develop new + business, then too desperate to be selective about incoming work." additional_triage_questions: - - question: "Is the growth stall caused by insufficient demand (not enough clients or projects) or insufficient capacity (demand exists but you cannot deliver it)?" - purpose: "Demand-side stalls require sales and marketing investment. Capacity-side stalls require hiring, subcontracting, or process efficiency. These are opposite problems with opposite solutions." - routing_impact: "Demand stall routes to four-ps-marketing and business development strategy. Capacity stall routes to shamrock-organisation and delegation-and-empowerment for scaling delivery." - - question: "How many hours per week does the founder spend on non-billable business development — and has this changed in the past 6 months?" - purpose: "The most common agency growth stall occurs when the founder becomes consumed by delivery and stops developing new business. Revenue lags 3-6 months later." - routing_impact: "Founder-consumed-by-delivery routes to eisenhower-matrix and delegation-and-empowerment for immediate rebalancing." - - question: "Have you hit a revenue plateau where the firm has been stuck at approximately the same level for 12+ months?" - purpose: "Revenue plateaus in agencies typically occur at predictable thresholds: $500K (founder capacity ceiling), $1.5M-$2M (first management layer needed), $5M (institutional processes required). Each requires a structural change to break through." - routing_impact: "Plateau at $500K routes to delegation skills and first hires. Plateau at $1.5M-$2M routes to leadership-pipeline and management structure. Plateau at $5M routes to systems-thinking and organizational design." + - question: "Is the growth stall caused by insufficient demand (not enough clients + or projects) or insufficient capacity (demand exists but you cannot + deliver it)?" + purpose: "Demand-side stalls require sales and marketing investment. + Capacity-side stalls require hiring, subcontracting, or process + efficiency. These are opposite problems with opposite solutions." + routing_impact: "Demand stall routes to four-ps-marketing and business + development strategy. Capacity stall routes to shamrock-organisation + and delegation-and-empowerment for scaling delivery." + - question: "How many hours per week does the founder spend on non-billable + business development — and has this changed in the past 6 months?" + purpose: "The most common agency growth stall occurs when the founder becomes + consumed by delivery and stops developing new business. Revenue lags + 3-6 months later." + routing_impact: "Founder-consumed-by-delivery routes to eisenhower-matrix and + delegation-and-empowerment for immediate rebalancing." + - question: "Have you hit a revenue plateau where the firm has been stuck at + approximately the same level for 12+ months?" + purpose: "Revenue plateaus in agencies typically occur at predictable + thresholds: $500K (founder capacity ceiling), $1.5M-$2M (first + management layer needed), $5M (institutional processes required). Each + requires a structural change to break through." + routing_impact: "Plateau at $500K routes to delegation skills and first hires. + Plateau at $1.5M-$2M routes to leadership-pipeline and management + structure. Plateau at $5M routes to systems-thinking and + organizational design." diagnosis_weight_shifts: more_likely: - diagnosis: "Founder-as-bottleneck" - reason: "The single most common agency growth stall. The founder cannot simultaneously deliver outstanding work, manage the team, develop new business, and run operations. Growth stops at the founder's personal capacity." + reason: "The single most common agency growth stall. The founder cannot + simultaneously deliver outstanding work, manage the team, develop + new business, and run operations. Growth stops at the founder's + personal capacity." - diagnosis: "Feast-or-famine revenue cycle" - reason: "Agencies without dedicated business development alternate between overwhelming demand (no time to sell) and desperate pipeline gaps (no work coming in). This cycle prevents steady growth." + reason: "Agencies without dedicated business development alternate between + overwhelming demand (no time to sell) and desperate pipeline gaps + (no work coming in). This cycle prevents steady growth." less_likely: - diagnosis: "Market saturation" - reason: "Professional services markets are enormous and fragmented. True market saturation is rare — growth stalls in agencies are almost always internal, not market-driven." + reason: "Professional services markets are enormous and fragmented. True market + saturation is rare — growth stalls in agencies are almost always + internal, not market-driven." agency_specific_diagnoses: - name: "Founder capacity ceiling" - description: "The agency has reached the maximum revenue the founder can personally generate, oversee, and sell. Growth requires the founder to delegate delivery, client relationships, or business development — but the founder has not made this transition, either because they cannot find people to delegate to or because they are unwilling to relinquish control." + description: "The agency has reached the maximum revenue the founder can + personally generate, oversee, and sell. Growth requires the founder to + delegate delivery, client relationships, or business development — but + the founder has not made this transition, either because they cannot + find people to delegate to or because they are unwilling to relinquish + control." symptoms: - "Revenue flat for 12+ months despite market demand" - - "Founder working 55+ hours per week with no capacity for additional work" + - "Founder working 55+ hours per week with no capacity for additional + work" - "New clients turned away or delayed because of founder availability" - - "No employee authorized to make client-facing decisions without founder approval" - routes_to_skills: ["delegation-and-empowerment", "leadership-pipeline", "shamrock-organisation"] - routes_to_templates: ["weekly-ceo-review", "role-description-template"] + - "No employee authorized to make client-facing decisions without + founder approval" + routes_to_skills: + [ + "delegation-and-empowerment", + "leadership-pipeline", + "shamrock-organisation" + ] + routes_to_templates: [ "weekly-ceo-review", "role-description-template" ] - name: "Feast-or-famine revenue cycle" - description: "Revenue oscillates wildly between periods of overwhelming demand and periods of painful underutilization. The cycle perpetuates because the agency invests zero time in business development during busy periods and panic-sells during quiet periods, producing low-quality pipeline." + description: "Revenue oscillates wildly between periods of overwhelming demand + and periods of painful underutilization. The cycle perpetuates because + the agency invests zero time in business development during busy + periods and panic-sells during quiet periods, producing low-quality + pipeline." symptoms: - "Revenue variance of 30%+ between best and worst quarters" - - "Business development activity inversely correlated with delivery load" - - "Bench time spikes followed by capacity crunches requiring overtime and rushed hiring" + - "Business development activity inversely correlated with delivery + load" + - "Bench time spikes followed by capacity crunches requiring overtime + and rushed hiring" - "Pipeline coverage ratio swinging between 1x and 5x across the year" - routes_to_skills: ["balanced-scorecard", "scenario-planning", "eisenhower-matrix"] - routes_to_templates: ["action-plan", "weekly-ceo-review"] + routes_to_skills: [ "balanced-scorecard", "scenario-planning", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "weekly-ceo-review" ] - name: "Productization paralysis" - description: "The agency recognizes that productizing services (fixed-scope, fixed-price, repeatable offerings) would improve margins and scalability, but cannot stop accepting custom work long enough to build the productized offering. Every time resources are allocated to productization, a client project takes priority." + description: "The agency recognizes that productizing services (fixed-scope, + fixed-price, repeatable offerings) would improve margins and + scalability, but cannot stop accepting custom work long enough to + build the productized offering. Every time resources are allocated to + productization, a client project takes priority." symptoms: - - "Productization initiative started but never completed (multiple times)" - - "Custom work consistently prioritized over productization because it generates immediate revenue" - - "Founder intellectually convinced of productization value but operationally unable to execute" - - "No distinct pricing or packaging for the intended productized service" - routes_to_skills: ["business-model-canvas", "eisenhower-matrix", "disruptive-innovation"] - routes_to_templates: ["new-initiative-brief", "decision-rationale-memo"] + - "Productization initiative started but never completed (multiple + times)" + - "Custom work consistently prioritized over productization because it + generates immediate revenue" + - "Founder intellectually convinced of productization value but + operationally unable to execute" + - "No distinct pricing or packaging for the intended productized + service" + routes_to_skills: [ "business-model-canvas", "eisenhower-matrix", "disruptive-innovation" ] + routes_to_templates: [ "new-initiative-brief", "decision-rationale-memo" ] sector_red_flags: - - "Founder billing more than 60% of available hours — growth is structurally impossible at this utilization level because no time remains for sales and management." - - "Zero dedicated business development time in the past 30 days — the pipeline will empty within 3-6 months." - - "Revenue flat for 12+ months in a growing market — the stall is internal, not market-driven." + - "Founder billing more than 60% of available hours — growth is + structurally impossible at this utilization level because no time + remains for sales and management." + - "Zero dedicated business development time in the past 30 days — the + pipeline will empty within 3-6 months." + - "Revenue flat for 12+ months in a growing market — the stall is + internal, not market-driven." # ───────────────────────────────────────────── # 3. PRODUCT-MARKET FIT DIAGNOSIS @@ -148,35 +255,74 @@ diagnostic_rules: - diagnostic: "product-market-fit-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Product-market fit in agencies translates to 'service-market fit' — the alignment between the firm's expertise, delivery model, and pricing with a specific client segment's needs and willingness to pay. Unlike product PMF, which is measured through retention curves and organic growth, service-market fit is measured through client retention, referral volume, pricing power, and the ease of winning new business within the target segment." + adaptation_rationale: "Product-market fit in agencies translates to + 'service-market fit' — the alignment between the firm's expertise, + delivery model, and pricing with a specific client segment's needs and + willingness to pay. Unlike product PMF, which is measured through + retention curves and organic growth, service-market fit is measured + through client retention, referral volume, pricing power, and the ease of + winning new business within the target segment." additional_triage_questions: - - question: "Is your referral pipeline healthy — do existing clients actively recommend you to their peers, and do those referrals convert at a high rate?" - purpose: "Referral volume and conversion are the strongest PMF signals in professional services. Clients who refer are satisfied, and referred prospects convert at high rates because trust transfers through the referral." - routing_impact: "Low referral volume routes to net-promoter-score and trust-equation for relationship assessment. High referral volume with low conversion routes to four-ps-marketing for positioning and messaging." - - question: "Can you charge premium rates (top 25% in your market) and still win consistently?" - purpose: "Pricing power is the definitive PMF signal in agencies. If clients pay premium rates without extensive negotiation, the firm has service-market fit." - routing_impact: "Low pricing power despite good work routes to positioning and specialization analysis. Premium pricing power routes to growth and scaling strategy." + - question: "Is your referral pipeline healthy — do existing clients actively + recommend you to their peers, and do those referrals convert at a high + rate?" + purpose: "Referral volume and conversion are the strongest PMF signals in + professional services. Clients who refer are satisfied, and referred + prospects convert at high rates because trust transfers through the + referral." + routing_impact: "Low referral volume routes to net-promoter-score and + trust-equation for relationship assessment. High referral volume with + low conversion routes to four-ps-marketing for positioning and + messaging." + - question: "Can you charge premium rates (top 25% in your market) and still win + consistently?" + purpose: "Pricing power is the definitive PMF signal in agencies. If clients pay + premium rates without extensive negotiation, the firm has + service-market fit." + routing_impact: "Low pricing power despite good work routes to positioning and + specialization analysis. Premium pricing power routes to growth and + scaling strategy." diagnosis_weight_shifts: more_likely: - - diagnosis: "Service-market fit exists for a niche but the firm is not focused on it" - reason: "Most agencies have accidental PMF in a subsegment they have not identified. Their best clients share characteristics (industry, size, problem type) that the agency has not deliberately targeted." + - diagnosis: "Service-market fit exists for a niche but the firm is not focused on + it" + reason: "Most agencies have accidental PMF in a subsegment they have not + identified. Their best clients share characteristics (industry, + size, problem type) that the agency has not deliberately targeted." less_likely: - diagnosis: "The service has no market" - reason: "Professional services always have a market — someone always needs expertise. The question is not whether a market exists but whether the firm's specific combination of expertise, positioning, and pricing matches a specific buyer's needs." + reason: "Professional services always have a market — someone always needs + expertise. The question is not whether a market exists but whether + the firm's specific combination of expertise, positioning, and + pricing matches a specific buyer's needs." agency_specific_diagnoses: - name: "Accidental niche PMF" - description: "The agency has strong service-market fit in a specific niche (industry vertical, company size, problem type) but has not recognized or deliberately pursued it. The best clients, highest retention, and strongest referrals all cluster in one segment that the firm treats as just another part of its undifferentiated client base." + description: "The agency has strong service-market fit in a specific niche + (industry vertical, company size, problem type) but has not recognized + or deliberately pursued it. The best clients, highest retention, and + strongest referrals all cluster in one segment that the firm treats as + just another part of its undifferentiated client base." symptoms: - - "Highest-NPS clients share common characteristics (industry, size, problem type)" + - "Highest-NPS clients share common characteristics (industry, size, + problem type)" - "Best referrals come from a specific client cluster" - "Win rate dramatically higher in one segment than others" - - "The firm describes itself as a generalist but 40%+ of revenue comes from one recognizable segment" - routes_to_skills: ["blue-ocean-strategy", "business-model-canvas", "strategic-thinking-and-alignment"] - routes_to_templates: ["strategic-analysis-one-pager", "market-opportunity-summary"] + - "The firm describes itself as a generalist but 40%+ of revenue comes + from one recognizable segment" + routes_to_skills: + [ + "blue-ocean-strategy", + "business-model-canvas", + "strategic-thinking-and-alignment" + ] + routes_to_templates: [ "strategic-analysis-one-pager", "market-opportunity-summary" ] sector_red_flags: - - "No referrals in the past quarter despite having active clients — a strong signal that service-market fit is weak." - - "Win rate below 20% — the firm's positioning, pricing, or targeting is misaligned with the prospects it pursues." - - "Unable to articulate what makes the firm different from competitors in one sentence — a clarity problem that undermines every pitch." + - "No referrals in the past quarter despite having active clients — a + strong signal that service-market fit is weak." + - "Win rate below 20% — the firm's positioning, pricing, or targeting is + misaligned with the prospects it pursues." + - "Unable to articulate what makes the firm different from competitors in + one sentence — a clarity problem that undermines every pitch." # ───────────────────────────────────────────── # 4. PRICING DIAGNOSIS @@ -184,41 +330,91 @@ diagnostic_rules: - diagnostic: "pricing-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Pricing is the most consequential strategic decision in agencies and the one most systematically mismanaged. The agency pricing spectrum — from hourly billing to value-based pricing — fundamentally determines revenue per employee, margin structure, client relationships, and scalability. Most agencies are severely underpriced because founders set rates based on their previous salary plus a margin, rather than on the value they deliver. The diagnosis must evaluate not just the price level but the pricing model itself." + adaptation_rationale: "Pricing is the most consequential strategic decision in + agencies and the one most systematically mismanaged. The agency pricing + spectrum — from hourly billing to value-based pricing — fundamentally + determines revenue per employee, margin structure, client relationships, + and scalability. Most agencies are severely underpriced because founders + set rates based on their previous salary plus a margin, rather than on the + value they deliver. The diagnosis must evaluate not just the price level + but the pricing model itself." additional_triage_questions: - - question: "What is your current pricing model — hourly, project-based, retainer, value-based, or a mix — and why did you choose it?" - purpose: "Most agencies default to hourly or project pricing without evaluating alternatives. Each model has distinct economic characteristics that affect utilization pressure, scope management, and revenue predictability." - routing_impact: "Hourly pricing routes to evaluation of value-based or project-based alternatives. Fixed-price with frequent overruns routes to scoping and change-order process improvement. Retainer with low utilization routes to retainer restructuring." - - question: "When was the last time you raised rates, and what was the client response?" - purpose: "Many agencies have not raised rates in years. The clients' response to price increases is almost always less negative than the agency fears — and reveals pricing power (or lack thereof)." - routing_impact: "Never raised rates routes to immediate pricing analysis. Raised rates with no pushback routes to further increases. Raised rates and lost clients routes to value communication and positioning improvement." - - question: "What is your effective billable rate — the actual revenue per hour worked on client projects after discounts, write-offs, and scope overruns?" - purpose: "The gap between standard rate and effective rate reveals the true pricing problem. A firm with a $200/hour rate and a $130/hour effective rate does not have a pricing problem — it has a scope management and discounting problem." - routing_impact: "Gap exceeding 25% routes to scope-creep and discounting diagnosis. Gap under 10% with still-low margins routes to rate increase strategy." + - question: "What is your current pricing model — hourly, project-based, retainer, + value-based, or a mix — and why did you choose it?" + purpose: "Most agencies default to hourly or project pricing without evaluating + alternatives. Each model has distinct economic characteristics that + affect utilization pressure, scope management, and revenue + predictability." + routing_impact: "Hourly pricing routes to evaluation of value-based or + project-based alternatives. Fixed-price with frequent overruns routes + to scoping and change-order process improvement. Retainer with low + utilization routes to retainer restructuring." + - question: "When was the last time you raised rates, and what was the client + response?" + purpose: "Many agencies have not raised rates in years. The clients' response to + price increases is almost always less negative than the agency fears — + and reveals pricing power (or lack thereof)." + routing_impact: "Never raised rates routes to immediate pricing analysis. Raised + rates with no pushback routes to further increases. Raised rates and + lost clients routes to value communication and positioning + improvement." + - question: "What is your effective billable rate — the actual revenue per hour + worked on client projects after discounts, write-offs, and scope + overruns?" + purpose: "The gap between standard rate and effective rate reveals the true + pricing problem. A firm with a $200/hour rate and a $130/hour + effective rate does not have a pricing problem — it has a scope + management and discounting problem." + routing_impact: "Gap exceeding 25% routes to scope-creep and discounting + diagnosis. Gap under 10% with still-low margins routes to rate + increase strategy." diagnosis_weight_shifts: more_likely: - diagnosis: "Chronic underpricing" - reason: "The default error in agencies is underpricing. Founders anchor on their previous salary, competitor rates, or what 'feels fair' rather than on the value delivered. Most agencies capture 15-30% of the value they create for clients." + reason: "The default error in agencies is underpricing. Founders anchor on their + previous salary, competitor rates, or what 'feels fair' rather than + on the value delivered. Most agencies capture 15-30% of the value + they create for clients." - diagnosis: "Pricing model mismatch" - reason: "Many agencies use hourly billing for strategic work (which penalizes speed and expertise) or project pricing for unpredictable work (which guarantees overruns). The model must match the work type." + reason: "Many agencies use hourly billing for strategic work (which penalizes + speed and expertise) or project pricing for unpredictable work + (which guarantees overruns). The model must match the work type." less_likely: - diagnosis: "Overpricing relative to value" - reason: "Genuine overpricing in agencies is rare. What appears as a 'too expensive' objection is almost always a value communication failure — the prospect does not understand the value, not that the value does not exist." + reason: "Genuine overpricing in agencies is rare. What appears as a 'too + expensive' objection is almost always a value communication failure + — the prospect does not understand the value, not that the value + does not exist." agency_specific_diagnoses: - name: "Pricing floor trap" - description: "The agency has positioned itself at the low end of the market — competing on price against freelancers and offshore teams. Low rates attract cost-sensitive clients who demand more for less, negotiate aggressively, and churn at the first sign of a cheaper alternative. The firm cannot invest in talent, quality, or business development because margins are too thin." + description: "The agency has positioned itself at the low end of the market — + competing on price against freelancers and offshore teams. Low rates + attract cost-sensitive clients who demand more for less, negotiate + aggressively, and churn at the first sign of a cheaper alternative. + The firm cannot invest in talent, quality, or business development + because margins are too thin." symptoms: - "Rates in the bottom quartile for the firm's market and discipline" - - "Win rate high but margins thin — winning through price, not through value" + - "Win rate high but margins thin — winning through price, not through + value" - "Client objections focus on cost rather than outcomes" - - "Unable to attract or retain senior talent because compensation is not competitive" + - "Unable to attract or retain senior talent because compensation is + not competitive" - "Competing regularly against freelancers and offshore teams" - routes_to_skills: ["pricing-diagnosis", "blue-ocean-strategy", "porters-five-forces"] - routes_to_templates: ["unit-economics-snapshot", "strategic-analysis-one-pager"] + routes_to_skills: + - blue-ocean-strategy + - porters-five-forces + routes_to_templates: [ "unit-economics-snapshot", "strategic-analysis-one-pager" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - - "Effective billable rate below 65% of standard rate — scope creep and discounting are destroying the pricing strategy." - - "Rates unchanged for 24+ months — the firm is almost certainly leaving money on the table." - - "Revenue per employee below $120K — a mathematical indicator that rates, utilization, or both are critically low." + - "Effective billable rate below 65% of standard rate — scope creep and + discounting are destroying the pricing strategy." + - "Rates unchanged for 24+ months — the firm is almost certainly leaving + money on the table." + - "Revenue per employee below $120K — a mathematical indicator that rates, + utilization, or both are critically low." # ───────────────────────────────────────────── # 5. FUNDRAISING DIAGNOSIS @@ -226,37 +422,73 @@ diagnostic_rules: - diagnostic: "fundraising-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Most agencies do not raise venture capital — and should not. Agency economics (linear scaling, people-dependent) do not fit the VC model (exponential scaling, technology-dependent). However, agencies do seek capital through bank loans, lines of credit, revenue-based financing, SBA loans, partnership buyins/buyouts, and occasionally strategic investors. The fundraising diagnostic must be reframed entirely for these capital sources, which have different requirements, metrics, and expectations than venture capital." + adaptation_rationale: "Most agencies do not raise venture capital — and should + not. Agency economics (linear scaling, people-dependent) do not fit the VC + model (exponential scaling, technology-dependent). However, agencies do + seek capital through bank loans, lines of credit, revenue-based financing, + SBA loans, partnership buyins/buyouts, and occasionally strategic + investors. The fundraising diagnostic must be reframed entirely for these + capital sources, which have different requirements, metrics, and + expectations than venture capital." additional_triage_questions: - - question: "What is the capital for — bridging a cash flow gap (AR financing), funding growth (hiring ahead of demand), acquiring another firm, or buying out a partner?" - purpose: "Each capital need has a different optimal source. AR financing requires a line of credit. Growth hiring requires revenue-based financing or retained earnings. Acquisitions require a term loan or investor. Partner buyouts require structured financing." - routing_impact: "Cash flow gap routes to AR management and line-of-credit options. Growth hiring routes to revenue-based financing and scenario-planning. Acquisition routes to M&A analysis. Partner buyout routes to negotiation skills and structured deal design." + - question: "What is the capital for — bridging a cash flow gap (AR financing), + funding growth (hiring ahead of demand), acquiring another firm, or + buying out a partner?" + purpose: "Each capital need has a different optimal source. AR financing + requires a line of credit. Growth hiring requires revenue-based + financing or retained earnings. Acquisitions require a term loan or + investor. Partner buyouts require structured financing." + routing_impact: "Cash flow gap routes to AR management and line-of-credit + options. Growth hiring routes to revenue-based financing and + scenario-planning. Acquisition routes to M&A analysis. Partner buyout + routes to negotiation skills and structured deal design." - question: "What is the firm's current EBITDA margin and debt capacity?" - purpose: "Lenders evaluate agencies primarily on profitability and cash flow stability — not growth rate. An agency with 15% EBITDA margin and stable revenue can access more favorable lending terms than a faster-growing but unprofitable one." - routing_impact: "Healthy EBITDA routes to bank financing options. Low EBITDA routes to profitability improvement before seeking capital." + purpose: "Lenders evaluate agencies primarily on profitability and cash flow + stability — not growth rate. An agency with 15% EBITDA margin and + stable revenue can access more favorable lending terms than a + faster-growing but unprofitable one." + routing_impact: "Healthy EBITDA routes to bank financing options. Low EBITDA + routes to profitability improvement before seeking capital." diagnosis_weight_shifts: more_likely: - diagnosis: "Cash flow timing mismatch" - reason: "The most common 'capital need' in agencies is not growth financing but cash flow management — the gap between when payroll is due and when clients pay. A line of credit or improved AR processes often solves this without external capital." + reason: "The most common 'capital need' in agencies is not growth financing but + cash flow management — the gap between when payroll is due and when + clients pay. A line of credit or improved AR processes often solves + this without external capital." - diagnosis: "Over-capitalization temptation" - reason: "Agencies seeking external capital often want to hire ahead of demand. This is dangerous in services because idle talent burns cash immediately, unlike product inventory which retains some value." + reason: "Agencies seeking external capital often want to hire ahead of demand. + This is dangerous in services because idle talent burns cash + immediately, unlike product inventory which retains some value." less_likely: - diagnosis: "Need for venture capital" - reason: "Traditional agency models are incompatible with VC expectations. VC-compatible agency models require a productized or technology component that enables non-linear scaling." + reason: "Traditional agency models are incompatible with VC expectations. + VC-compatible agency models require a productized or technology + component that enables non-linear scaling." agency_specific_diagnoses: - name: "Utilization death spiral" - description: "The agency raised capital or used retained earnings to hire ahead of demand, but the expected demand did not materialize. Bench time consumes cash, pressure to fill capacity leads to accepting low-margin or off-strategy work, which diverts senior attention from business development, which further reduces high-quality pipeline." + description: "The agency raised capital or used retained earnings to hire ahead + of demand, but the expected demand did not materialize. Bench time + consumes cash, pressure to fill capacity leads to accepting low-margin + or off-strategy work, which diverts senior attention from business + development, which further reduces high-quality pipeline." symptoms: - "Bench time above 20% for more than one quarter" - - "Accepting work below minimum rate or outside the firm's positioning to fill capacity" + - "Accepting work below minimum rate or outside the firm's positioning + to fill capacity" - "Cash burn rate accelerating despite stable or growing revenue" - - "New hires underutilized while existing staff are overloaded (indicating a skills or client mismatch)" - routes_to_skills: ["scenario-planning", "shamrock-organisation", "eisenhower-matrix"] - routes_to_templates: ["action-plan", "decision-rationale-memo"] + - "New hires underutilized while existing staff are overloaded + (indicating a skills or client mismatch)" + routes_to_skills: [ "scenario-planning", "shamrock-organisation", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "decision-rationale-memo" ] sector_red_flags: - - "Seeking VC funding for a traditional agency model — the economics do not support venture returns and the resulting pressure will distort the business." - - "Hiring more than 3 people simultaneously without confirmed pipeline to support them — high risk of utilization death spiral." - - "AR exceeding 60 days while also seeking external capital — fix the collection problem before adding new capital." + - "Seeking VC funding for a traditional agency model — the economics do + not support venture returns and the resulting pressure will distort the + business." + - "Hiring more than 3 people simultaneously without confirmed pipeline to + support them — high risk of utilization death spiral." + - "AR exceeding 60 days while also seeking external capital — fix the + collection problem before adding new capital." # ───────────────────────────────────────────── # 6. REVENUE DIAGNOSIS @@ -264,37 +496,74 @@ diagnostic_rules: - diagnostic: "revenue-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Agency revenue decomposes differently from product revenue. The components are: project revenue (discrete engagements with defined scope), retainer revenue (recurring monthly fees for ongoing work), hourly overflow (ad hoc billing beyond scope), and productized revenue (fixed-price packaged services). Healthy agencies diversify across these streams, with retainer revenue providing stability and project revenue providing growth. The diagnosis must evaluate both the total revenue and the quality of the revenue mix." + adaptation_rationale: "Agency revenue decomposes differently from product + revenue. The components are: project revenue (discrete engagements with + defined scope), retainer revenue (recurring monthly fees for ongoing + work), hourly overflow (ad hoc billing beyond scope), and productized + revenue (fixed-price packaged services). Healthy agencies diversify across + these streams, with retainer revenue providing stability and project + revenue providing growth. The diagnosis must evaluate both the total + revenue and the quality of the revenue mix." additional_triage_questions: - - question: "What percentage of your revenue is recurring (retainers and ongoing contracts) versus project-based (discrete engagements)?" - purpose: "Revenue predictability determines the firm's ability to plan, hire, and invest. A firm with 60%+ recurring revenue can plan confidently. A firm with 80%+ project revenue lives in perpetual uncertainty." - routing_impact: "Low recurring revenue routes to retainer development strategy and client-relationship deepening. High recurring revenue with stagnant growth routes to new client acquisition and pipeline development." - - question: "What is your revenue concentration — what percentage comes from your top 3 clients?" - purpose: "Client concentration is the primary revenue risk in agencies. If the top 3 clients represent more than 50% of revenue, any single departure creates a crisis." - routing_impact: "Concentration above 50% routes to immediate diversification strategy and client-acquisition investment." + - question: "What percentage of your revenue is recurring (retainers and ongoing + contracts) versus project-based (discrete engagements)?" + purpose: "Revenue predictability determines the firm's ability to plan, hire, + and invest. A firm with 60%+ recurring revenue can plan confidently. A + firm with 80%+ project revenue lives in perpetual uncertainty." + routing_impact: "Low recurring revenue routes to retainer development strategy + and client-relationship deepening. High recurring revenue with + stagnant growth routes to new client acquisition and pipeline + development." + - question: "What is your revenue concentration — what percentage comes from your + top 3 clients?" + purpose: "Client concentration is the primary revenue risk in agencies. If the + top 3 clients represent more than 50% of revenue, any single departure + creates a crisis." + routing_impact: "Concentration above 50% routes to immediate diversification + strategy and client-acquisition investment." diagnosis_weight_shifts: more_likely: - diagnosis: "Revenue quality deterioration" - reason: "Agency revenue can grow in total while deteriorating in quality — more project work (unpredictable), smaller average project sizes (higher overhead), and lower rates (price competition). Total revenue masks these trends." + reason: "Agency revenue can grow in total while deteriorating in quality — more + project work (unpredictable), smaller average project sizes (higher + overhead), and lower rates (price competition). Total revenue masks + these trends." - diagnosis: "Client concentration creating fragility" - reason: "Many agencies grow revenue by deepening a few client relationships rather than broadening the client base. This concentrates risk dangerously." + reason: "Many agencies grow revenue by deepening a few client relationships + rather than broadening the client base. This concentrates risk + dangerously." less_likely: - diagnosis: "Market-wide demand decline" - reason: "Professional services demand is remarkably resilient. Even in recessions, organizations need external expertise. Revenue problems in agencies are almost always firm-specific, not market-wide." + reason: "Professional services demand is remarkably resilient. Even in + recessions, organizations need external expertise. Revenue problems + in agencies are almost always firm-specific, not market-wide." agency_specific_diagnoses: - name: "Retainer erosion" - description: "Retainer revenue — the foundation of agency stability — is declining as clients reduce scope, pause engagements, or shift to project-based relationships. The firm's revenue is becoming increasingly unpredictable and project-dependent." + description: "Retainer revenue — the foundation of agency stability — is + declining as clients reduce scope, pause engagements, or shift to + project-based relationships. The firm's revenue is becoming + increasingly unpredictable and project-dependent." symptoms: - "Retainer revenue declining as a percentage of total revenue" - "Average retainer duration shortening" - - "Clients requesting 'project-based' pricing for work previously on retainer" - - "Revenue forecasting accuracy declining (more misses, wider variance)" - routes_to_skills: ["net-promoter-score", "trust-equation", "pricing-diagnosis"] - routes_to_templates: ["quarterly-business-review", "service-level-agreement"] + - "Clients requesting 'project-based' pricing for work previously on + retainer" + - "Revenue forecasting accuracy declining (more misses, wider + variance)" + routes_to_skills: + - net-promoter-score + - trust-equation + routes_to_templates: [ "quarterly-business-review", "service-level-agreement" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - - "Top 3 clients representing more than 50% of revenue — one departure creates a survival crisis." - - "Recurring revenue below 30% of total — the firm has no revenue floor and will suffer in any demand downturn." - - "Average project value declining quarter over quarter — the firm is accepting smaller, less profitable work." + - "Top 3 clients representing more than 50% of revenue — one departure + creates a survival crisis." + - "Recurring revenue below 30% of total — the firm has no revenue floor + and will suffer in any demand downturn." + - "Average project value declining quarter over quarter — the firm is + accepting smaller, less profitable work." # ───────────────────────────────────────────── # 7. COMPETITIVE THREAT DIAGNOSIS @@ -302,34 +571,67 @@ diagnostic_rules: - diagnostic: "competitive-threat-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency competitive threats come from four distinct directions: other agencies (traditional competitors), freelancers and contractor collectives (lower cost), in-house teams (client self-sufficiency), and AI tools (automation of agency deliverables). Each threat requires a different response, and agencies often focus exclusively on agency-to-agency competition while ignoring the more dangerous structural threats." + adaptation_rationale: "Agency competitive threats come from four distinct + directions: other agencies (traditional competitors), freelancers and + contractor collectives (lower cost), in-house teams (client + self-sufficiency), and AI tools (automation of agency deliverables). Each + threat requires a different response, and agencies often focus exclusively + on agency-to-agency competition while ignoring the more dangerous + structural threats." additional_triage_questions: - - question: "Which competitive threat is most active: another agency winning your clients, freelancers undercutting your rates, clients building in-house teams, or AI tools replacing your services?" - purpose: "Each threat type requires a different strategic response. Agency competition requires differentiation. Freelancer competition requires value demonstration. In-housing requires elevation to strategic advisory. AI competition requires integration and repositioning." - routing_impact: "Agency competition routes to blue-ocean-strategy and positioning refinement. Freelancer/AI competition routes to disruptive-innovation and value-stacking above automation. In-housing routes to strategic advisory repositioning." + - question: "Which competitive threat is most active: another agency winning your + clients, freelancers undercutting your rates, clients building + in-house teams, or AI tools replacing your services?" + purpose: "Each threat type requires a different strategic response. Agency + competition requires differentiation. Freelancer competition requires + value demonstration. In-housing requires elevation to strategic + advisory. AI competition requires integration and repositioning." + routing_impact: "Agency competition routes to blue-ocean-strategy and + positioning refinement. Freelancer/AI competition routes to + disruptive-innovation and value-stacking above automation. In-housing + routes to strategic advisory repositioning." diagnosis_weight_shifts: more_likely: - diagnosis: "In-house team displacement" - reason: "The greatest long-term threat to agencies is not other agencies but clients deciding they can do the work themselves. When multiple clients build internal teams, it signals that the agency's service has commoditized." + reason: "The greatest long-term threat to agencies is not other agencies but + clients deciding they can do the work themselves. When multiple + clients build internal teams, it signals that the agency's service + has commoditized." - diagnosis: "AI disruption of commodity services" - reason: "AI tools are rapidly replacing tasks that agencies bill for: copywriting, basic design, data analysis, media planning, and code generation. Agencies that bill for execution rather than strategy face existential AI risk." + reason: "AI tools are rapidly replacing tasks that agencies bill for: + copywriting, basic design, data analysis, media planning, and code + generation. Agencies that bill for execution rather than strategy + face existential AI risk." less_likely: - diagnosis: "Price-based competitive displacement by another agency" - reason: "Losing clients purely on price to another agency is rare if the relationship is strong. Agencies lose on price when they have failed to build relationship depth or demonstrate differentiated value." + reason: "Losing clients purely on price to another agency is rare if the + relationship is strong. Agencies lose on price when they have failed + to build relationship depth or demonstrate differentiated value." agency_specific_diagnoses: - name: "AI commoditization threat" - description: "AI tools are performing tasks that constitute a significant portion of the agency's billable work. Clients are beginning to question why they pay agency rates for work that AI can approximate. The threat is not that AI replaces the agency entirely, but that it compresses the scope and value of what clients are willing to outsource." + description: "AI tools are performing tasks that constitute a significant + portion of the agency's billable work. Clients are beginning to + question why they pay agency rates for work that AI can approximate. + The threat is not that AI replaces the agency entirely, but that it + compresses the scope and value of what clients are willing to + outsource." symptoms: - "Clients mentioning AI tools as alternatives during negotiations" - - "Reduction in demand for specific deliverable types (e.g., basic content, simple designs)" - - "Prospects asking whether the agency uses AI and why they should pay human rates" - - "Junior staff work increasingly automatable, threatening the leverage model" - routes_to_skills: ["disruptive-innovation", "ai-vision-and-strategy", "blue-ocean-strategy"] - routes_to_templates: ["strategic-analysis-one-pager", "competitive-landscape-brief"] + - "Reduction in demand for specific deliverable types (e.g., basic + content, simple designs)" + - "Prospects asking whether the agency uses AI and why they should pay + human rates" + - "Junior staff work increasingly automatable, threatening the + leverage model" + routes_to_skills: [ "disruptive-innovation", "ai-vision-and-strategy", "blue-ocean-strategy" ] + routes_to_templates: [ "strategic-analysis-one-pager", "competitive-landscape-brief" ] sector_red_flags: - - "Three or more clients building in-house versions of the agency's core service in the same year — structural displacement is underway." - - "Win rate declining against freelancers or small firms — the agency's overhead is not justified by sufficient value differentiation." - - "AI-generated deliverables achieving 'good enough' quality for tasks that constitute more than 30% of the agency's billable hours." + - "Three or more clients building in-house versions of the agency's core + service in the same year — structural displacement is underway." + - "Win rate declining against freelancers or small firms — the agency's + overhead is not justified by sufficient value differentiation." + - "AI-generated deliverables achieving 'good enough' quality for tasks + that constitute more than 30% of the agency's billable hours." # ───────────────────────────────────────────── # 8. STRATEGIC DRIFT DIAGNOSIS @@ -337,32 +639,60 @@ diagnostic_rules: - diagnostic: "strategic-drift-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Strategic drift in agencies manifests as 'everything for everyone' syndrome — the firm accepts any work from any client, gradually losing its positioning and becoming an undifferentiated generalist. The temptation is structural: declining a $50K project because it is 'off-strategy' feels irresponsible when payroll is due. Strategic drift in agencies is the accumulated result of hundreds of small, individually rational decisions to take the work that is available rather than the work that builds the firm's positioning." + adaptation_rationale: "Strategic drift in agencies manifests as 'everything for + everyone' syndrome — the firm accepts any work from any client, gradually + losing its positioning and becoming an undifferentiated generalist. The + temptation is structural: declining a $50K project because it is + 'off-strategy' feels irresponsible when payroll is due. Strategic drift in + agencies is the accumulated result of hundreds of small, individually + rational decisions to take the work that is available rather than the work + that builds the firm's positioning." additional_triage_questions: - - question: "Can you describe your ideal client and ideal project in one sentence each — and does more than 50% of your current revenue come from that profile?" - purpose: "The ability to articulate a clear ideal client is a positioning litmus test. If less than 50% of revenue fits the ideal profile, the firm has drifted." - routing_impact: "Unable to articulate routes to blue-ocean-strategy and strategic-thinking-and-alignment for positioning development. Can articulate but low alignment routes to disciplined client selection and off-strategy work reduction." + - question: "Can you describe your ideal client and ideal project in one sentence + each — and does more than 50% of your current revenue come from that + profile?" + purpose: "The ability to articulate a clear ideal client is a positioning litmus + test. If less than 50% of revenue fits the ideal profile, the firm has + drifted." + routing_impact: "Unable to articulate routes to blue-ocean-strategy and + strategic-thinking-and-alignment for positioning development. Can + articulate but low alignment routes to disciplined client selection + and off-strategy work reduction." diagnosis_weight_shifts: more_likely: - diagnosis: "Revenue-driven drift — accepting anything that pays" - reason: "The most common drift mechanism in agencies. Each off-strategy project seems harmless individually but collectively erodes the firm's positioning, stretches capabilities, and prevents specialization." + reason: "The most common drift mechanism in agencies. Each off-strategy project + seems harmless individually but collectively erodes the firm's + positioning, stretches capabilities, and prevents specialization." less_likely: - diagnosis: "Market disruption causing strategic irrelevance" - reason: "Agency strategic drift is almost always self-inflicted through lack of discipline rather than externally caused. The market did not change — the firm's discipline did." + reason: "Agency strategic drift is almost always self-inflicted through lack of + discipline rather than externally caused. The market did not change + — the firm's discipline did." agency_specific_diagnoses: - name: "Scope-of-service sprawl" - description: "The agency has gradually expanded its service offerings in response to client requests until it offers everything from strategy to execution across multiple disciplines. Each service line is staffed by one or two people, none of whom are world-class. The firm competes as a generalist against specialists in every discipline and loses on quality while maintaining the overhead of multiple capabilities." + description: "The agency has gradually expanded its service offerings in + response to client requests until it offers everything from strategy + to execution across multiple disciplines. Each service line is staffed + by one or two people, none of whom are world-class. The firm competes + as a generalist against specialists in every discipline and loses on + quality while maintaining the overhead of multiple capabilities." symptoms: - - "More than 6 distinct service offerings with no shared methodology or positioning" + - "More than 6 distinct service offerings with no shared methodology + or positioning" - "Each service line staffed by fewer than 3 people" - "Difficulty describing what the firm 'does' in a single sentence" - - "Winning work primarily through existing relationships rather than expertise-based positioning" - routes_to_skills: ["blue-ocean-strategy", "porters-five-forces", "eisenhower-matrix"] - routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + - "Winning work primarily through existing relationships rather than + expertise-based positioning" + routes_to_skills: [ "blue-ocean-strategy", "porters-five-forces", "eisenhower-matrix" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] sector_red_flags: - - "Unable to decline any project regardless of fit — a sign that financial pressure has overridden strategic discipline." - - "The firm's website lists more than 8 service categories — typically an indicator of everything-for-everyone positioning." - - "Revenue spread evenly across unrelated industries and service types with no identifiable specialization." + - "Unable to decline any project regardless of fit — a sign that financial + pressure has overridden strategic discipline." + - "The firm's website lists more than 8 service categories — typically an + indicator of everything-for-everyone positioning." + - "Revenue spread evenly across unrelated industries and service types + with no identifiable specialization." # ───────────────────────────────────────────── # 9. TEAM DYSFUNCTION DIAGNOSIS @@ -370,34 +700,62 @@ diagnostic_rules: - diagnostic: "team-dysfunction-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency team dysfunction has characteristic patterns driven by the client-service nature of the business. The most common dysfunctions: account managers over-promise while delivery teams under-deliver, senior staff hoard client relationships while junior staff feel excluded, creative/strategy teams and execution teams operate in silos, and the pressure to be billable suppresses the collaborative, unbillable time that builds team cohesion." + adaptation_rationale: "Agency team dysfunction has characteristic patterns + driven by the client-service nature of the business. The most common + dysfunctions: account managers over-promise while delivery teams + under-deliver, senior staff hoard client relationships while junior staff + feel excluded, creative/strategy teams and execution teams operate in + silos, and the pressure to be billable suppresses the collaborative, + unbillable time that builds team cohesion." additional_triage_questions: - - question: "Is there tension between the people who sell work (partners, account managers) and the people who deliver it (creatives, developers, consultants) — specifically, are commitments made during the sales process that delivery cannot fulfill?" - purpose: "The sell-deliver gap is the most common and most damaging agency dysfunction. It creates impossible expectations, frustrated delivery teams, disappointed clients, and mutual blame between functions." - routing_impact: "Sell-deliver misalignment routes to cooperative-negotiation for internal process redesign and trust-equation for rebuilding internal trust between functions." + - question: "Is there tension between the people who sell work (partners, account + managers) and the people who deliver it (creatives, developers, + consultants) — specifically, are commitments made during the sales + process that delivery cannot fulfill?" + purpose: "The sell-deliver gap is the most common and most damaging agency + dysfunction. It creates impossible expectations, frustrated delivery + teams, disappointed clients, and mutual blame between functions." + routing_impact: "Sell-deliver misalignment routes to cooperative-negotiation for + internal process redesign and trust-equation for rebuilding internal + trust between functions." diagnosis_weight_shifts: more_likely: - diagnosis: "Sell-deliver gap" - reason: "Agency sales incentives (winning the pitch) and delivery incentives (quality within scope) are structurally misaligned. Without deliberate processes to reconcile these, tension is inevitable." + reason: "Agency sales incentives (winning the pitch) and delivery incentives + (quality within scope) are structurally misaligned. Without + deliberate processes to reconcile these, tension is inevitable." - diagnosis: "Burnout-driven dysfunction" - reason: "Agency work involves high emotional labor (demanding clients, tight deadlines, personal investment in creative output). Teams that are consistently overutilized degrade in collaboration, quality, and morale." + reason: "Agency work involves high emotional labor (demanding clients, tight + deadlines, personal investment in creative output). Teams that are + consistently overutilized degrade in collaboration, quality, and + morale." less_likely: - diagnosis: "Insufficient talent" - reason: "What appears as talent insufficiency in agencies is often a systems problem: talented people performing poorly because of unclear priorities, impossible workloads, or dysfunctional processes." + reason: "What appears as talent insufficiency in agencies is often a systems + problem: talented people performing poorly because of unclear + priorities, impossible workloads, or dysfunctional processes." agency_specific_diagnoses: - name: "Talent retention crisis — key people leaving and taking clients" - description: "Senior staff with deep client relationships are departing — and taking clients with them. The firm's client base is hollowing out as the people who are the firm's product walk out the door." + description: "Senior staff with deep client relationships are departing — and + taking clients with them. The firm's client base is hollowing out as + the people who are the firm's product walk out the door." symptoms: - - "Senior employee departures followed by client departures within 3-6 months" - - "Clients requesting specific individuals rather than engaging the firm as an institution" + - "Senior employee departures followed by client departures within 3-6 + months" + - "Clients requesting specific individuals rather than engaging the + firm as an institution" - "No non-compete or non-solicit agreements in employment contracts" - - "Client relationships concentrated in individual employees rather than distributed across the firm" - routes_to_skills: ["inspiring-and-retaining", "organisational-culture", "trust-equation"] - routes_to_templates: ["hiring-scorecard", "team-health-check"] + - "Client relationships concentrated in individual employees rather + than distributed across the firm" + routes_to_skills: [ "inspiring-and-retaining", "organisational-culture", "trust-equation" ] + routes_to_templates: [ "hiring-scorecard", "team-health-check" ] sector_red_flags: - - "Delivery team attrition above 25% — the firm cannot maintain quality or client relationships with this level of turnover." - - "Account manager making commitments to clients without delivery team input — a structural sell-deliver gap." - - "Key person dependency — any individual whose departure would directly cause client loss." + - "Delivery team attrition above 25% — the firm cannot maintain quality or + client relationships with this level of turnover." + - "Account manager making commitments to clients without delivery team + input — a structural sell-deliver gap." + - "Key person dependency — any individual whose departure would directly + cause client loss." # ───────────────────────────────────────────── # 10. COFOUNDER CONFLICT DIAGNOSIS @@ -405,32 +763,57 @@ diagnostic_rules: - diagnostic: "cofounder-conflict-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency co-founder (and co-partner) conflicts cluster around four issues: client ownership (who 'owns' which relationships), revenue contribution (who brings in more business), role boundaries (who decides what), and strategic direction (generalist vs. specialist, growth vs. lifestyle). The personal nature of agency work makes these conflicts particularly intense — each partner's contribution is directly measurable through billings and client retention." + adaptation_rationale: "Agency co-founder (and co-partner) conflicts cluster + around four issues: client ownership (who 'owns' which relationships), + revenue contribution (who brings in more business), role boundaries (who + decides what), and strategic direction (generalist vs. specialist, growth + vs. lifestyle). The personal nature of agency work makes these conflicts + particularly intense — each partner's contribution is directly measurable + through billings and client retention." additional_triage_questions: - - question: "Is the conflict about strategic direction (what the firm should become), revenue contribution (who generates more business), or operational authority (who decides how work is done)?" - purpose: "Each conflict type requires different intervention. Strategic conflicts need facilitated alignment sessions. Revenue contribution disputes need transparent metrics and equitable compensation structures. Authority conflicts need explicit role definitions." - routing_impact: "Strategic direction routes to strategic-thinking-and-alignment and scenario-planning. Revenue contribution routes to balanced-scorecard with transparent partner metrics. Authority routes to delegation-and-empowerment and explicit role documentation." + - question: "Is the conflict about strategic direction (what the firm should + become), revenue contribution (who generates more business), or + operational authority (who decides how work is done)?" + purpose: "Each conflict type requires different intervention. Strategic + conflicts need facilitated alignment sessions. Revenue contribution + disputes need transparent metrics and equitable compensation + structures. Authority conflicts need explicit role definitions." + routing_impact: "Strategic direction routes to strategic-thinking-and-alignment + and scenario-planning. Revenue contribution routes to + balanced-scorecard with transparent partner metrics. Authority routes + to delegation-and-empowerment and explicit role documentation." diagnosis_weight_shifts: more_likely: - diagnosis: "Unequal contribution resentment" - reason: "In agencies, each partner's contribution is visible — billings, clients brought in, people managed. When one partner perceives an imbalance, resentment builds rapidly." + reason: "In agencies, each partner's contribution is visible — billings, clients + brought in, people managed. When one partner perceives an imbalance, + resentment builds rapidly." less_likely: - diagnosis: "Vision misalignment" - reason: "Most agency partnership conflicts are operational, not visionary. Partners usually agree on what a good agency looks like — they disagree on roles, compensation, and authority." + reason: "Most agency partnership conflicts are operational, not visionary. + Partners usually agree on what a good agency looks like — they + disagree on roles, compensation, and authority." agency_specific_diagnoses: - name: "Partner lifestyle mismatch" - description: "One partner wants to grow aggressively (hire, take on debt, pursue large clients) while the other wants to maintain a lifestyle practice (stable income, manageable hours, select clients). Neither goal is wrong, but they are incompatible in a single firm." + description: "One partner wants to grow aggressively (hire, take on debt, pursue + large clients) while the other wants to maintain a lifestyle practice + (stable income, manageable hours, select clients). Neither goal is + wrong, but they are incompatible in a single firm." symptoms: - "Recurring arguments about hiring decisions, debt, and investment" - "One partner working significantly more hours than the other" - "Disagreement about whether to take on large, risky opportunities" - - "One partner subtly sabotaging growth initiatives or cost-cutting measures" - routes_to_skills: ["cooperative-negotiation", "evaluating-and-deciding", "covey-seven-habits"] - routes_to_templates: ["decision-rationale-memo", "quarterly-strategic-review"] + - "One partner subtly sabotaging growth initiatives or cost-cutting + measures" + routes_to_skills: [ "cooperative-negotiation", "evaluating-and-deciding", "covey-seven-habits" ] + routes_to_templates: [ "decision-rationale-memo", "quarterly-strategic-review" ] sector_red_flags: - - "Partners communicating through staff rather than directly — a sign the conflict has become personal." - - "Key staff choosing sides — the conflict is contaminating the entire organization." - - "One partner quietly meeting with clients to establish independent relationships — possible prelude to a split." + - "Partners communicating through staff rather than directly — a sign the + conflict has become personal." + - "Key staff choosing sides — the conflict is contaminating the entire + organization." + - "One partner quietly meeting with clients to establish independent + relationships — possible prelude to a split." # ───────────────────────────────────────────── # 11. MARKET ENTRY DIAGNOSIS @@ -438,22 +821,41 @@ diagnostic_rules: - diagnostic: "market-entry-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Market entry for agencies means entering a new vertical, a new service line, or a new geographic market. Unlike product companies, agencies can 'enter' a new market by winning a single client — but sustaining that entry requires building credible expertise and a reference-worthy track record. The key question is always: can the firm build sufficient credibility in the new market to win competitively, or will it always be an outsider competing against firms with deeper domain expertise?" + adaptation_rationale: "Market entry for agencies means entering a new vertical, + a new service line, or a new geographic market. Unlike product companies, + agencies can 'enter' a new market by winning a single client — but + sustaining that entry requires building credible expertise and a + reference-worthy track record. The key question is always: can the firm + build sufficient credibility in the new market to win competitively, or + will it always be an outsider competing against firms with deeper domain + expertise?" additional_triage_questions: - - question: "Do you have at least one reference client in the target market — someone who can vouch for your work in this specific context?" - purpose: "Agency market entry without a reference client is nearly impossible. Prospects in any market want to see proof of domain experience. The first reference client is the gateway." - routing_impact: "No reference client routes to a landing strategy: discounted or pro-bono first engagement to build the reference. Existing reference routes to targeted outreach using the case study." + - question: "Do you have at least one reference client in the target market — + someone who can vouch for your work in this specific context?" + purpose: "Agency market entry without a reference client is nearly impossible. + Prospects in any market want to see proof of domain experience. The + first reference client is the gateway." + routing_impact: "No reference client routes to a landing strategy: discounted or + pro-bono first engagement to build the reference. Existing reference + routes to targeted outreach using the case study." diagnosis_weight_shifts: more_likely: - diagnosis: "Credibility gap in the target market" - reason: "Agencies entering new verticals face the 'but have you done this in our industry?' objection. Overcoming the credibility gap is the primary market-entry challenge." + reason: "Agencies entering new verticals face the 'but have you done this in our + industry?' objection. Overcoming the credibility gap is the primary + market-entry challenge." less_likely: - diagnosis: "Inadequate market size" - reason: "Most professional services verticals are large enough to support multiple agencies. Market size is rarely the barrier — credibility and relationships are." + reason: "Most professional services verticals are large enough to support + multiple agencies. Market size is rarely the barrier — credibility + and relationships are." agency_specific_diagnoses: [] sector_red_flags: - - "Entering a new market without a single reference client or case study — nearly impossible to win competitive pitches without proof of domain expertise." - - "Adding a new service line without hiring someone who has delivered it before — quality risk is high." + - "Entering a new market without a single reference client or case study — + nearly impossible to win competitive pitches without proof of domain + expertise." + - "Adding a new service line without hiring someone who has delivered it + before — quality risk is high." # ───────────────────────────────────────────── # 12. HIRING DIAGNOSIS @@ -461,28 +863,55 @@ diagnostic_rules: - diagnostic: "hiring-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency hiring is uniquely consequential because every hire directly affects delivery capacity, client relationships, and revenue. Hiring too slow means turning away work; hiring too fast means paying for bench time. The critical agency hiring decisions: when to add the first non-billable role (operations, office management), when to hire senior versus junior (the leverage decision), and when to hire full-time versus freelance (the Shamrock decision)." + adaptation_rationale: "Agency hiring is uniquely consequential because every + hire directly affects delivery capacity, client relationships, and + revenue. Hiring too slow means turning away work; hiring too fast means + paying for bench time. The critical agency hiring decisions: when to add + the first non-billable role (operations, office management), when to hire + senior versus junior (the leverage decision), and when to hire full-time + versus freelance (the Shamrock decision)." additional_triage_questions: - - question: "Is this hire intended to fill existing billable demand (you have work waiting) or to build capacity for expected future demand (you hope work will come)?" - purpose: "Hiring against existing demand is low-risk. Hiring against expected demand is speculative — and the most common cause of utilization death spirals in agencies." - routing_impact: "Hiring against existing demand routes to rapid hiring execution. Hiring speculatively routes to scenario-planning and the decision to use freelancers instead of full-time hires until demand is confirmed." - - question: "Are you hiring a 'doer' (someone to produce work) or a 'grower' (someone to bring in and manage client relationships)?" - purpose: "Agencies need both but often hire doers when they need growers. A firm at capacity that hires another developer when it needs a business developer will not solve its growth problem." - routing_impact: "Doer hire routes to utilization and leverage optimization. Grower hire routes to business development strategy and role-description-template." + - question: "Is this hire intended to fill existing billable demand (you have work + waiting) or to build capacity for expected future demand (you hope + work will come)?" + purpose: "Hiring against existing demand is low-risk. Hiring against expected + demand is speculative — and the most common cause of utilization death + spirals in agencies." + routing_impact: "Hiring against existing demand routes to rapid hiring + execution. Hiring speculatively routes to scenario-planning and the + decision to use freelancers instead of full-time hires until demand is + confirmed." + - question: "Are you hiring a 'doer' (someone to produce work) or a 'grower' + (someone to bring in and manage client relationships)?" + purpose: "Agencies need both but often hire doers when they need growers. A firm + at capacity that hires another developer when it needs a business + developer will not solve its growth problem." + routing_impact: "Doer hire routes to utilization and leverage optimization. + Grower hire routes to business development strategy and + role-description-template." diagnosis_weight_shifts: more_likely: - diagnosis: "Hiring doers when the firm needs growers" - reason: "Agencies default to hiring the type of person the founder is — usually a practitioner. But growth requires people who can sell, manage relationships, and develop business." + reason: "Agencies default to hiring the type of person the founder is — usually + a practitioner. But growth requires people who can sell, manage + relationships, and develop business." - diagnosis: "Hiring full-time when freelancers would suffice" - reason: "Many agency hiring 'needs' are actually surge-capacity needs that the Shamrock model (freelancers) handles more efficiently than permanent headcount." + reason: "Many agency hiring 'needs' are actually surge-capacity needs that the + Shamrock model (freelancers) handles more efficiently than permanent + headcount." less_likely: - diagnosis: "Compensation insufficient to attract talent" - reason: "While agency salaries are often lower than tech company salaries, talented people choose agencies for variety, autonomy, and interesting work. Compensation is rarely the binding constraint." + reason: "While agency salaries are often lower than tech company salaries, + talented people choose agencies for variety, autonomy, and + interesting work. Compensation is rarely the binding constraint." agency_specific_diagnoses: [] sector_red_flags: - - "Hiring three or more people simultaneously without confirmed project pipeline — high risk of bench-time crisis." - - "First senior hire (VP, Director level) without a clear mandate and success criteria — expensive failure is likely." - - "Every new hire being a practitioner with zero hires in business development or operations — the firm will hit a growth ceiling." + - "Hiring three or more people simultaneously without confirmed project + pipeline — high risk of bench-time crisis." + - "First senior hire (VP, Director level) without a clear mandate and + success criteria — expensive failure is likely." + - "Every new hire being a practitioner with zero hires in business + development or operations — the firm will hit a growth ceiling." # ───────────────────────────────────────────── # 13. OPERATIONAL CHAOS DIAGNOSIS @@ -490,35 +919,60 @@ diagnostic_rules: - diagnostic: "operational-chaos-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency operational chaos manifests as missed deadlines, inaccurate time tracking, billing disputes, resource conflicts (multiple projects competing for the same person), and communication breakdowns between account management and delivery. Unlike product companies where operations center on technology infrastructure, agency operations center on people management — scheduling, utilization tracking, project profitability monitoring, and capacity planning." + adaptation_rationale: "Agency operational chaos manifests as missed deadlines, + inaccurate time tracking, billing disputes, resource conflicts (multiple + projects competing for the same person), and communication breakdowns + between account management and delivery. Unlike product companies where + operations center on technology infrastructure, agency operations center + on people management — scheduling, utilization tracking, project + profitability monitoring, and capacity planning." additional_triage_questions: - - question: "Do you have a resource management system — a way to see who is assigned to what, who is available, and what capacity exists for new work?" - purpose: "Most agencies under 20 people have no formal resource management. Work assignments happen through hallway conversations, Slack messages, and the founder's mental model. This breaks at scale." - routing_impact: "No resource management routes to immediate process implementation. Existing system with poor adoption routes to process enforcement and training." + - question: "Do you have a resource management system — a way to see who is + assigned to what, who is available, and what capacity exists for new + work?" + purpose: "Most agencies under 20 people have no formal resource management. Work + assignments happen through hallway conversations, Slack messages, and + the founder's mental model. This breaks at scale." + routing_impact: "No resource management routes to immediate process + implementation. Existing system with poor adoption routes to process + enforcement and training." - question: "What percentage of projects deliver on time, on scope, and on budget?" - purpose: "On-time, on-scope, on-budget delivery is the operational health metric for agencies. Below 60% indicates systemic operational problems." - routing_impact: "Below 60% routes to systems-thinking for root cause analysis and action-plan for structured improvement." + purpose: "On-time, on-scope, on-budget delivery is the operational health metric + for agencies. Below 60% indicates systemic operational problems." + routing_impact: "Below 60% routes to systems-thinking for root cause analysis + and action-plan for structured improvement." diagnosis_weight_shifts: more_likely: - diagnosis: "Scope creep epidemic" - reason: "The most common operational chaos in agencies is unmanaged scope expansion — work grows beyond the original agreement without corresponding billing, eating into margins project by project." + reason: "The most common operational chaos in agencies is unmanaged scope + expansion — work grows beyond the original agreement without + corresponding billing, eating into margins project by project." less_likely: - diagnosis: "Technology failure" - reason: "Agencies rarely fail because of technology. They fail because of people management, scoping, and process problems." + reason: "Agencies rarely fail because of technology. They fail because of people + management, scoping, and process problems." agency_specific_diagnoses: - name: "Scope creep epidemic" - description: "The majority of projects systematically exceed their original scope, budget, and timeline. The firm absorbs the overruns without billing, effectively subsidizing client work with agency profits. Root causes include: optimistic scoping, unclear contracts, inability to say no to client requests, and lack of change-order processes." + description: "The majority of projects systematically exceed their original + scope, budget, and timeline. The firm absorbs the overruns without + billing, effectively subsidizing client work with agency profits. Root + causes include: optimistic scoping, unclear contracts, inability to + say no to client requests, and lack of change-order processes." symptoms: - "More than 40% of projects exceeding scope by more than 15%" - - "No formal change-order process or the process exists but is rarely invoked" + - "No formal change-order process or the process exists but is rarely + invoked" - "Effective billable rate more than 20% below standard rate" - - "Project managers reporting they feel unable to push back on client scope additions" + - "Project managers reporting they feel unable to push back on client + scope additions" - "Client expectations consistently exceed what was agreed in the SOW" - routes_to_skills: ["competitive-negotiation", "delivering-the-deal", "systems-thinking"] - routes_to_templates: ["service-level-agreement", "project-kickoff-document"] + routes_to_skills: [ "competitive-negotiation", "delivering-the-deal", "systems-thinking" ] + routes_to_templates: [ "service-level-agreement", "project-kickoff-document" ] sector_red_flags: - - "No time tracking system or time tracked but not reviewed — the firm is flying blind on utilization and project profitability." - - "More than 40% of projects exceeding scope — systemic scoping or boundary-setting failure." + - "No time tracking system or time tracked but not reviewed — the firm is + flying blind on utilization and project profitability." + - "More than 40% of projects exceeding scope — systemic scoping or + boundary-setting failure." - "AR exceeding 60 days — operational cash flow crisis building." # ───────────────────────────────────────────── @@ -527,23 +981,45 @@ diagnostic_rules: - diagnostic: "leadership-crisis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Leadership crises in agencies are amplified by the founder-as-product dynamic. When the founder burns out, the firm's primary sales channel, quality assurance mechanism, and client relationship manager all degrade simultaneously. Agency leadership crises also occur during partnership disputes, when key clients threaten to leave, or when the founder must transition from practitioner to manager — a transition many founders resist or fail." + adaptation_rationale: "Leadership crises in agencies are amplified by the + founder-as-product dynamic. When the founder burns out, the firm's primary + sales channel, quality assurance mechanism, and client relationship + manager all degrade simultaneously. Agency leadership crises also occur + during partnership disputes, when key clients threaten to leave, or when + the founder must transition from practitioner to manager — a transition + many founders resist or fail." additional_triage_questions: - - question: "Is the leadership crisis driven by founder burnout (overwork and exhaustion), a partnership conflict, or a failure to transition from practitioner to manager?" - purpose: "Each crisis type requires different intervention. Burnout requires immediate workload reduction. Partnership conflict requires mediation or structured separation. Transition failure requires coaching and delegation support." - routing_impact: "Burnout routes to founder-mental-health-check and immediate delegation. Partnership conflict routes to cofounder-conflict-diagnosis. Transition failure routes to delegation-and-empowerment and leadership-pipeline." + - question: "Is the leadership crisis driven by founder burnout (overwork and + exhaustion), a partnership conflict, or a failure to transition from + practitioner to manager?" + purpose: "Each crisis type requires different intervention. Burnout requires + immediate workload reduction. Partnership conflict requires mediation + or structured separation. Transition failure requires coaching and + delegation support." + routing_impact: "Burnout routes to founder-mental-health-check and immediate + delegation. Partnership conflict routes to + cofounder-conflict-diagnosis. Transition failure routes to + delegation-and-empowerment and leadership-pipeline." diagnosis_weight_shifts: more_likely: - diagnosis: "Founder burnout" - reason: "Agency founders work extremely long hours, carry emotional weight of client relationships, and often feel they cannot step back without the business collapsing. Burnout is endemic." + reason: "Agency founders work extremely long hours, carry emotional weight of + client relationships, and often feel they cannot step back without + the business collapsing. Burnout is endemic." less_likely: - diagnosis: "External leadership crisis (board pressure, investor conflict)" - reason: "Most agencies do not have boards or external investors. Leadership crises are internal — between founders, between partners, or within the founder's own capacity." + reason: "Most agencies do not have boards or external investors. Leadership + crises are internal — between founders, between partners, or within + the founder's own capacity." agency_specific_diagnoses: [] sector_red_flags: - - "Founder working 60+ hours per week for more than 6 consecutive months — burnout is imminent." - - "Founder avoiding difficult decisions (pricing, hiring, firing, client conversations) — decision fatigue indicating deeper leadership exhaustion." - - "Key leadership departure without a succession plan — the departure may cascade to additional losses." + - "Founder working 60+ hours per week for more than 6 consecutive months — + burnout is imminent." + - "Founder avoiding difficult decisions (pricing, hiring, firing, client + conversations) — decision fatigue indicating deeper leadership + exhaustion." + - "Key leadership departure without a succession plan — the departure may + cascade to additional losses." # ───────────────────────────────────────────── # 15. DECISION PARALYSIS DIAGNOSIS @@ -551,23 +1027,38 @@ diagnostic_rules: - diagnostic: "decision-paralysis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Decision paralysis in agencies often centers on the growth-versus-lifestyle choice, pricing decisions (afraid to raise rates), specialization decisions (afraid to narrow the offering), and hiring decisions (afraid to commit to permanent overhead). These decisions feel high-stakes because they are highly personal — they directly affect the founder's income, workload, and identity." + adaptation_rationale: "Decision paralysis in agencies often centers on the + growth-versus-lifestyle choice, pricing decisions (afraid to raise rates), + specialization decisions (afraid to narrow the offering), and hiring + decisions (afraid to commit to permanent overhead). These decisions feel + high-stakes because they are highly personal — they directly affect the + founder's income, workload, and identity." additional_triage_questions: - - question: "Which decision has been deferred longest — and what is the cost of continued delay?" - purpose: "Naming the deferred decision and quantifying its cost often provides the urgency needed to act." - routing_impact: "Pricing decision deferred routes to pricing-diagnosis with urgency framing. Growth/lifestyle decision deferred routes to covey-seven-habits for 'Begin with the End in Mind' exercise." + - question: "Which decision has been deferred longest — and what is the cost of + continued delay?" + purpose: "Naming the deferred decision and quantifying its cost often provides + the urgency needed to act." + routing_impact: "Pricing decision deferred routes to pricing-diagnosis with + urgency framing. Growth/lifestyle decision deferred routes to + covey-seven-habits for 'Begin with the End in Mind' exercise." diagnosis_weight_shifts: more_likely: - diagnosis: "Fear of irreversibility" - reason: "Agency founders often treat reversible decisions as irreversible. Raising rates, narrowing the offering, or hiring a new role feel permanent but are almost always adjustable." + reason: "Agency founders often treat reversible decisions as irreversible. + Raising rates, narrowing the offering, or hiring a new role feel + permanent but are almost always adjustable." less_likely: - diagnosis: "Insufficient information" - reason: "Agency decisions rarely require more data. The founder usually knows what to do — the barrier is emotional, not informational." + reason: "Agency decisions rarely require more data. The founder usually knows + what to do — the barrier is emotional, not informational." agency_specific_diagnoses: [] sector_red_flags: - - "Pricing unchanged for 24+ months while costs have risen — the decision to raise rates has been paralyzed by fear." - - "Specialization discussed for years but never implemented — the firm remains a generalist because the decision to narrow feels risky." - - "Key hire identified but not made for 6+ months — paralysis is constraining growth." + - "Pricing unchanged for 24+ months while costs have risen — the decision + to raise rates has been paralyzed by fear." + - "Specialization discussed for years but never implemented — the firm + remains a generalist because the decision to narrow feels risky." + - "Key hire identified but not made for 6+ months — paralysis is + constraining growth." # ───────────────────────────────────────────── # 16. INNOVATION DROUGHT DIAGNOSIS @@ -575,23 +1066,40 @@ diagnostic_rules: - diagnostic: "innovation-drought-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency innovation drought manifests as stale service offerings, outdated methodologies, and failure to adopt new tools and approaches. Client work consumes all capacity, leaving nothing for R&D, experimentation, or new service development. The result: the firm delivers the same services it offered five years ago while the market evolves around it." + adaptation_rationale: "Agency innovation drought manifests as stale service + offerings, outdated methodologies, and failure to adopt new tools and + approaches. Client work consumes all capacity, leaving nothing for R&D, + experimentation, or new service development. The result: the firm delivers + the same services it offered five years ago while the market evolves + around it." additional_triage_questions: - - question: "What new service, methodology, or capability has the firm developed in the past 12 months — not for a client, but as a proactive investment?" - purpose: "If the answer is 'nothing,' the firm is coasting on past innovation. Every year without proactive investment in new capabilities increases the risk of commoditization." - routing_impact: "No recent innovation routes to eisenhower-matrix for capacity creation and doblin-ten-types for innovation opportunity identification." + - question: "What new service, methodology, or capability has the firm developed + in the past 12 months — not for a client, but as a proactive + investment?" + purpose: "If the answer is 'nothing,' the firm is coasting on past innovation. + Every year without proactive investment in new capabilities increases + the risk of commoditization." + routing_impact: "No recent innovation routes to eisenhower-matrix for capacity + creation and doblin-ten-types for innovation opportunity + identification." diagnosis_weight_shifts: more_likely: - diagnosis: "Client delivery consuming all innovation capacity" - reason: "The classic agency trap: 100% of capacity is consumed by client work, leaving zero for R&D, new service development, or methodology refinement." + reason: "The classic agency trap: 100% of capacity is consumed by client work, + leaving zero for R&D, new service development, or methodology + refinement." less_likely: - diagnosis: "Lack of creative talent" - reason: "Agency teams are typically creative and capable. Innovation drought is a capacity and prioritization problem, not a talent problem." + reason: "Agency teams are typically creative and capable. Innovation drought is + a capacity and prioritization problem, not a talent problem." agency_specific_diagnoses: [] sector_red_flags: - - "No internal R&D or innovation time allocated in the past year — the firm is running entirely on legacy capabilities." - - "Competitors adopting AI, new methodologies, or new service models while the firm's offering remains static." - - "Clients asking about capabilities the firm does not have — the market is signaling unmet needs." + - "No internal R&D or innovation time allocated in the past year — the + firm is running entirely on legacy capabilities." + - "Competitors adopting AI, new methodologies, or new service models while + the firm's offering remains static." + - "Clients asking about capabilities the firm does not have — the market + is signaling unmet needs." # ───────────────────────────────────────────── # 17. PARTNERSHIP DIAGNOSIS @@ -599,23 +1107,44 @@ diagnostic_rules: - diagnostic: "partnership-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency partnerships operate differently from product partnerships. Agency partnerships include: referral partnerships (firms that send clients to each other), subcontracting relationships (firms that extend each other's capacity), technology partnerships (platforms and tools that the agency implements), and strategic alliances (firms that collaborate on large opportunities neither could win alone). The most valuable agency partnerships are reciprocal referral relationships with complementary firms — they generate the highest-quality leads at the lowest cost." + adaptation_rationale: "Agency partnerships operate differently from product + partnerships. Agency partnerships include: referral partnerships (firms + that send clients to each other), subcontracting relationships (firms that + extend each other's capacity), technology partnerships (platforms and + tools that the agency implements), and strategic alliances (firms that + collaborate on large opportunities neither could win alone). The most + valuable agency partnerships are reciprocal referral relationships with + complementary firms — they generate the highest-quality leads at the + lowest cost." additional_triage_questions: - - question: "Is this a referral partnership (you send each other clients), a delivery partnership (you subcontract to each other), or a technology partnership (you implement their platform)?" - purpose: "Each partnership type has different value dynamics and risks. Referral partnerships are low-risk, high-value. Delivery partnerships require quality alignment. Technology partnerships create dependency." - routing_impact: "Referral partnerships route to cooperative-negotiation for mutual benefit structuring. Delivery partnerships route to shamrock-organisation for quality management. Technology partnerships route to information-asymmetry for dependency risk assessment." + - question: "Is this a referral partnership (you send each other clients), a + delivery partnership (you subcontract to each other), or a technology + partnership (you implement their platform)?" + purpose: "Each partnership type has different value dynamics and risks. Referral + partnerships are low-risk, high-value. Delivery partnerships require + quality alignment. Technology partnerships create dependency." + routing_impact: "Referral partnerships route to cooperative-negotiation for + mutual benefit structuring. Delivery partnerships route to + shamrock-organisation for quality management. Technology partnerships + route to information-asymmetry for dependency risk assessment." diagnosis_weight_shifts: more_likely: - diagnosis: "Informal partnerships that lack structure" - reason: "Most agency partnerships are handshake arrangements without clear expectations, referral tracking, or reciprocity metrics. They atrophy because neither party manages them actively." + reason: "Most agency partnerships are handshake arrangements without clear + expectations, referral tracking, or reciprocity metrics. They + atrophy because neither party manages them actively." less_likely: - diagnosis: "Fundamentally incompatible partners" - reason: "Agency partnership failures are usually about neglect and misaligned expectations, not fundamental incompatibility." + reason: "Agency partnership failures are usually about neglect and misaligned + expectations, not fundamental incompatibility." agency_specific_diagnoses: [] sector_red_flags: - - "Technology partnership creating revenue dependency — more than 40% of revenue comes from implementing a single platform." - - "One-sided referral relationship — the agency sends referrals but never receives them." - - "Partnership agreements without defined terms, referral fees, or accountability mechanisms." + - "Technology partnership creating revenue dependency — more than 40% of + revenue comes from implementing a single platform." + - "One-sided referral relationship — the agency sends referrals but never + receives them." + - "Partnership agreements without defined terms, referral fees, or + accountability mechanisms." # ───────────────────────────────────────────── # 18. COMMUNICATION BREAKDOWN DIAGNOSIS @@ -623,23 +1152,41 @@ diagnostic_rules: - diagnostic: "communication-breakdown-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Communication in agencies operates on two axes simultaneously: internal communication (between partners, account managers, and delivery teams) and external communication (with clients). Breakdowns on either axis damage the business, but the interaction between the two is where the most damaging failures occur — for example, when internal miscommunication about project scope leads to incorrect client expectations." + adaptation_rationale: "Communication in agencies operates on two axes + simultaneously: internal communication (between partners, account + managers, and delivery teams) and external communication (with clients). + Breakdowns on either axis damage the business, but the interaction between + the two is where the most damaging failures occur — for example, when + internal miscommunication about project scope leads to incorrect client + expectations." additional_triage_questions: - - question: "Is the communication breakdown primarily internal (team members not aligned on scope, priorities, or timelines) or external (client expectations not matching what is being delivered)?" - purpose: "Internal breakdowns require process and tool fixes. External breakdowns require client communication protocol redesign." - routing_impact: "Internal breakdown routes to team process improvement. External breakdown routes to client communication cadence and expectation management." + - question: "Is the communication breakdown primarily internal (team members not + aligned on scope, priorities, or timelines) or external (client + expectations not matching what is being delivered)?" + purpose: "Internal breakdowns require process and tool fixes. External + breakdowns require client communication protocol redesign." + routing_impact: "Internal breakdown routes to team process improvement. External + breakdown routes to client communication cadence and expectation + management." diagnosis_weight_shifts: more_likely: - diagnosis: "Internal-external communication disconnect" - reason: "The most damaging communication breakdown in agencies occurs when the account team and the delivery team have different understandings of what was agreed with the client." + reason: "The most damaging communication breakdown in agencies occurs when the + account team and the delivery team have different understandings of + what was agreed with the client." less_likely: - diagnosis: "Technology-driven communication failure" - reason: "Agency communication failures are almost never about tools. They are about processes, habits, and the cultural norms around transparency." + reason: "Agency communication failures are almost never about tools. They are + about processes, habits, and the cultural norms around + transparency." agency_specific_diagnoses: [] sector_red_flags: - - "Client complaints about 'not knowing what is happening' on their projects — a project communication cadence failure." - - "Delivery team and account team disagreeing about project scope in front of the client — internal alignment failure." - - "Critical information communicated verbally but never documented — leading to 'I thought you said' disputes." + - "Client complaints about 'not knowing what is happening' on their + projects — a project communication cadence failure." + - "Delivery team and account team disagreeing about project scope in front + of the client — internal alignment failure." + - "Critical information communicated verbally but never documented — + leading to 'I thought you said' disputes." # ───────────────────────────────────────────── # 19. NEGOTIATION STUCK DIAGNOSIS @@ -647,23 +1194,45 @@ diagnostic_rules: - diagnostic: "negotiation-stuck-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency negotiations get stuck in predictable ways: scope negotiations where the client wants more work for the same price, rate negotiations where procurement demands discounts the agency cannot absorb, contract negotiations where legal terms (liability, IP ownership, indemnification) create impasses, and internal negotiations where partners disagree on strategic direction or resource allocation." + adaptation_rationale: "Agency negotiations get stuck in predictable ways: scope + negotiations where the client wants more work for the same price, rate + negotiations where procurement demands discounts the agency cannot absorb, + contract negotiations where legal terms (liability, IP ownership, + indemnification) create impasses, and internal negotiations where partners + disagree on strategic direction or resource allocation." additional_triage_questions: - - question: "Is the negotiation stuck on scope (what you will deliver), price (what they will pay), terms (contractual conditions), or timing (when work starts or payment is due)?" - purpose: "Each stall type has different resolution tactics. Scope stalls resolve through phased delivery. Price stalls resolve through value reframing. Terms stalls require creative legal solutions. Timing stalls require urgency creation." - routing_impact: "Scope stalls route to phased-proposal design. Price stalls route to value-based reframing and competitive-negotiation. Terms stalls route to delivering-the-deal with emphasis on flexible contract templates." + - question: "Is the negotiation stuck on scope (what you will deliver), price + (what they will pay), terms (contractual conditions), or timing (when + work starts or payment is due)?" + purpose: "Each stall type has different resolution tactics. Scope stalls resolve + through phased delivery. Price stalls resolve through value reframing. + Terms stalls require creative legal solutions. Timing stalls require + urgency creation." + routing_impact: "Scope stalls route to phased-proposal design. Price stalls + route to value-based reframing and competitive-negotiation. Terms + stalls route to delivering-the-deal with emphasis on flexible contract + templates." diagnosis_weight_shifts: more_likely: - diagnosis: "Scope-price deadlock" - reason: "The most common agency negotiation stall: the client wants more than the budget allows. The resolution is usually scope reduction, phased delivery, or value-based justification for the higher investment." + reason: "The most common agency negotiation stall: the client wants more than + the budget allows. The resolution is usually scope reduction, phased + delivery, or value-based justification for the higher investment." less_likely: - diagnosis: "Fundamental value disagreement" - reason: "If the client is negotiating, they have already decided the agency provides value. The stall is about terms, not about whether to engage." + reason: "If the client is negotiating, they have already decided the agency + provides value. The stall is about terms, not about whether to + engage." agency_specific_diagnoses: [] sector_red_flags: - - "Proposals stalling for 60+ days without resolution — the client may be using the proposal to justify an internal budget or benchmark another vendor." - - "Procurement demanding rate reductions below the firm's cost floor — this is not a negotiation, it is a signal that the client values cost over quality." - - "Internal partner negotiation about firm direction stalled for 6+ months — the firm is paralyzed." + - "Proposals stalling for 60+ days without resolution — the client may be + using the proposal to justify an internal budget or benchmark another + vendor." + - "Procurement demanding rate reductions below the firm's cost floor — + this is not a negotiation, it is a signal that the client values cost + over quality." + - "Internal partner negotiation about firm direction stalled for 6+ months + — the firm is paralyzed." # ───────────────────────────────────────────── # 20. CULTURE EROSION DIAGNOSIS @@ -671,34 +1240,65 @@ diagnostic_rules: - diagnostic: "culture-erosion-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Agency culture is uniquely vulnerable because the work is intensely personal, client demands create constant external pressure, and the creative/strategic professionals who drive agency value are highly sensitive to cultural degradation. Culture erosion in agencies often begins when the firm prioritizes client satisfaction over employee experience — accepting unreasonable client demands, tolerating abusive client behavior, and burning teams on impossible deadlines to maintain client relationships." + adaptation_rationale: "Agency culture is uniquely vulnerable because the work is + intensely personal, client demands create constant external pressure, and + the creative/strategic professionals who drive agency value are highly + sensitive to cultural degradation. Culture erosion in agencies often + begins when the firm prioritizes client satisfaction over employee + experience — accepting unreasonable client demands, tolerating abusive + client behavior, and burning teams on impossible deadlines to maintain + client relationships." additional_triage_questions: - - question: "Has the firm accepted client behavior (yelling, unreasonable deadlines, scope abuse, disrespect) that undermines team morale — and if so, why?" - purpose: "Agencies often tolerate client behavior they would never accept from an employee because the client represents revenue. This tolerance sends a message to the team: the client matters more than you do." - routing_impact: "Client behavior tolerance routes to trust-equation and boundary-setting frameworks. The agency must be willing to fire toxic clients to protect culture." - - question: "Has the firm's growth outpaced its ability to maintain the culture that attracted early employees?" - purpose: "The culture that works at 5 people (founder-led, informal, family-like) does not work at 25 people. Culture must be deliberately evolved, not left to erode." - routing_impact: "Growth-driven erosion routes to organisational-culture and team-culture-and-dynamics for deliberate culture scaling." + - question: "Has the firm accepted client behavior (yelling, unreasonable + deadlines, scope abuse, disrespect) that undermines team morale — and + if so, why?" + purpose: "Agencies often tolerate client behavior they would never accept from + an employee because the client represents revenue. This tolerance + sends a message to the team: the client matters more than you do." + routing_impact: "Client behavior tolerance routes to trust-equation and + boundary-setting frameworks. The agency must be willing to fire toxic + clients to protect culture." + - question: "Has the firm's growth outpaced its ability to maintain the culture + that attracted early employees?" + purpose: "The culture that works at 5 people (founder-led, informal, + family-like) does not work at 25 people. Culture must be deliberately + evolved, not left to erode." + routing_impact: "Growth-driven erosion routes to organisational-culture and + team-culture-and-dynamics for deliberate culture scaling." diagnosis_weight_shifts: more_likely: - diagnosis: "Client-above-team culture" - reason: "The most common culture erosion pattern in agencies: prioritizing client satisfaction at the expense of employee wellbeing until the best people leave." + reason: "The most common culture erosion pattern in agencies: prioritizing + client satisfaction at the expense of employee wellbeing until the + best people leave." - diagnosis: "Growth outpacing culture infrastructure" - reason: "Agencies that double headcount without investing in onboarding, communication norms, and cultural rituals lose the culture that made them attractive." + reason: "Agencies that double headcount without investing in onboarding, + communication norms, and cultural rituals lose the culture that made + them attractive." less_likely: - diagnosis: "Toxic leadership" - reason: "Most agency culture erosion is caused by neglect — no one is responsible for culture — rather than malicious leadership." + reason: "Most agency culture erosion is caused by neglect — no one is + responsible for culture — rather than malicious leadership." agency_specific_diagnoses: - name: "Client-abuse tolerance" - description: "The agency tolerates abusive client behavior — aggressive communication, unreasonable demands, last-minute changes without additional compensation, disrespect toward team members — because the revenue is needed. This tolerance erodes team morale, drives attrition among the best people, and ultimately damages the agency's capacity to serve any client well." + description: "The agency tolerates abusive client behavior — aggressive + communication, unreasonable demands, last-minute changes without + additional compensation, disrespect toward team members — because the + revenue is needed. This tolerance erodes team morale, drives attrition + among the best people, and ultimately damages the agency's capacity to + serve any client well." symptoms: - "Team members requesting to be reassigned from specific clients" - "Higher attrition among staff assigned to demanding accounts" - - "Senior leadership rationalizing poor client behavior ('they are just passionate')" - - "eNPS declining while client NPS remains stable — the team absorbs the cost of client satisfaction" - routes_to_skills: ["trust-equation", "radical-candor", "psychological-safety-practice"] - routes_to_templates: ["culture-values-document", "team-health-check"] + - "Senior leadership rationalizing poor client behavior ('they are + just passionate')" + - "eNPS declining while client NPS remains stable — the team absorbs + the cost of client satisfaction" + routes_to_skills: [ "trust-equation", "radical-candor", "psychological-safety-practice" ] + routes_to_templates: [ "culture-values-document", "team-health-check" ] sector_red_flags: - "eNPS below 10 — the team is not just disengaged but actively unhappy." - - "Employee attrition above 25% — culture problems are driving out talent faster than the firm can replace them." - - "The firm has never fired a client for behavioral reasons — a sign that revenue is prioritized over people in every case." + - "Employee attrition above 25% — culture problems are driving out talent + faster than the firm can replace them." + - "The firm has never fired a client for behavioral reasons — a sign that + revenue is prioritized over people in every case." diff --git a/.claude/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml b/.claude/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml index d6e9c5b..12f0958 100644 --- a/.claude/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml +++ b/.claude/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml @@ -46,221 +46,786 @@ skill_overlays: - skill: "porters-five-forces" category: "frameworks" agency_relevance: "critical" - agency_context: "Porter's Five Forces reveals the structurally brutal economics of professional services. Buyer power is HIGH — clients can always find another agency, switch costs are low (especially for project-based work), and procurement departments actively commoditize services through competitive pitching. Threat of substitutes is expanding relentlessly: in-house teams, freelancer platforms (Upwork, Toptal), AI tools that automate creative and analytical tasks, and offshore delivery. Barriers to entry are NEAR ZERO — anyone with a laptop and a LinkedIn profile can start a consultancy. Supplier power is concentrated in scarce talent — specialized developers, strategists, and creatives are the 'supply' that agencies compete for. Rivalry is intense, fragmented, and often irrational (agencies undercutting to win work they cannot profitably deliver)." + agency_context: "Porter's Five Forces reveals the structurally brutal economics + of professional services. Buyer power is HIGH — clients can always find + another agency, switch costs are low (especially for project-based work), + and procurement departments actively commoditize services through + competitive pitching. Threat of substitutes is expanding relentlessly: + in-house teams, freelancer platforms (Upwork, Toptal), AI tools that + automate creative and analytical tasks, and offshore delivery. Barriers to + entry are NEAR ZERO — anyone with a laptop and a LinkedIn profile can + start a consultancy. Supplier power is concentrated in scarce talent — + specialized developers, strategists, and creatives are the 'supply' that + agencies compete for. Rivalry is intense, fragmented, and often irrational + (agencies undercutting to win work they cannot profitably deliver)." agency_anti_patterns: - - "Ignoring the threat of in-house teams. The most dangerous substitute is not another agency — it is the client deciding to hire the capability internally. Agencies must deliver value that in-house teams cannot: breadth of experience, objectivity, surge capacity, and specialized expertise." - - "Treating low barriers to entry as irrelevant because the firm has relationships. Relationships are necessary but eroding — procurement-led selection processes increasingly neutralize relationship advantages." - - "Overlooking AI as a substitute force. AI tools are rapidly replacing tasks that agencies bill for: copywriting, basic design, data analysis, code generation, and media planning. Agencies that do not adapt will see their addressable work shrink." - agency_example: "A digital marketing agency uses Five Forces to understand why margins are compressing. The analysis reveals that buyer power has increased (clients now use agency-comparison platforms and demand competitive pitches for every project), substitutes have multiplied (AI content tools, in-house content teams, freelancer collectives), and new entrants are undercutting prices (former employees starting solo practices). The firm responds by deepening specialization in a vertical (healthcare marketing), building proprietary data assets, and offering outcome-based pricing that shifts competition from cost to results." - benchmark_references: ["client-retention-rate", "win-rate", "average-billable-rate"] + - "Ignoring the threat of in-house teams. The most dangerous substitute is + not another agency — it is the client deciding to hire the capability + internally. Agencies must deliver value that in-house teams cannot: + breadth of experience, objectivity, surge capacity, and specialized + expertise." + - "Treating low barriers to entry as irrelevant because the firm has + relationships. Relationships are necessary but eroding — procurement-led + selection processes increasingly neutralize relationship advantages." + - "Overlooking AI as a substitute force. AI tools are rapidly replacing + tasks that agencies bill for: copywriting, basic design, data analysis, + code generation, and media planning. Agencies that do not adapt will see + their addressable work shrink." + agency_example: "A digital marketing agency uses Five Forces to understand why + margins are compressing. The analysis reveals that buyer power has + increased (clients now use agency-comparison platforms and demand + competitive pitches for every project), substitutes have multiplied (AI + content tools, in-house content teams, freelancer collectives), and new + entrants are undercutting prices (former employees starting solo + practices). The firm responds by deepening specialization in a vertical + (healthcare marketing), building proprietary data assets, and offering + outcome-based pricing that shifts competition from cost to results." + benchmark_references: [ "client-retention-rate", "win-rate", "average-billable-rate" ] - skill: "blue-ocean-strategy" category: "frameworks" agency_relevance: "critical" - agency_context: "Most agencies compete in blood-red oceans — undifferentiated services, price-based competition, and a race to the bottom on rates. Blue ocean strategy is structurally essential because agency differentiation cannot come from product features (there is no product). It must come from positioning: the intersection of a specific expertise, a specific client type, and a specific delivery model that competitors cannot or will not replicate. The strategy canvas exercise maps the agency's offerings against competitors and reveals where the market over-serves (elaborate pitch processes, bloated account teams, over-designed deliverables) and under-serves (speed, transparency, outcome guarantees, embedded models)." + agency_context: "Most agencies compete in blood-red oceans — undifferentiated + services, price-based competition, and a race to the bottom on rates. Blue + ocean strategy is structurally essential because agency differentiation + cannot come from product features (there is no product). It must come from + positioning: the intersection of a specific expertise, a specific client + type, and a specific delivery model that competitors cannot or will not + replicate. The strategy canvas exercise maps the agency's offerings + against competitors and reveals where the market over-serves (elaborate + pitch processes, bloated account teams, over-designed deliverables) and + under-serves (speed, transparency, outcome guarantees, embedded models)." agency_anti_patterns: - - "Defining the blue ocean too broadly. 'Full-service agency for mid-market companies' is not a blue ocean — it is the exact red ocean every agency swims in. The blue ocean must be specific enough that a competitor would hesitate to follow." - - "Creating a blue ocean that eliminates the relationship advantage. Agencies that automate away the human relationship in pursuit of differentiation lose the one asset clients value most." - - "Abandoning the blue ocean at the first sign of success. When a niche strategy works, agencies are tempted to expand back into general services, re-entering the red ocean they escaped." - agency_example: "A web development agency, competing against hundreds of generalist firms on price, applies blue ocean strategy and identifies an uncontested space: fractional CTO services for non-technical founders. They eliminate traditional agency deliverables (proposals, wireframes, design comps) and instead embed a senior technologist directly in the founder's decision-making process. The pricing shifts from project-based to monthly retainer. Competitors cannot follow because they are structured around project delivery teams, not individual advisory relationships." - benchmark_references: ["average-billable-rate", "client-retention-rate", "revenue-per-client"] + - "Defining the blue ocean too broadly. 'Full-service agency for + mid-market companies' is not a blue ocean — it is the exact red ocean + every agency swims in. The blue ocean must be specific enough that a + competitor would hesitate to follow." + - "Creating a blue ocean that eliminates the relationship advantage. + Agencies that automate away the human relationship in pursuit of + differentiation lose the one asset clients value most." + - "Abandoning the blue ocean at the first sign of success. When a niche + strategy works, agencies are tempted to expand back into general + services, re-entering the red ocean they escaped." + agency_example: "A web development agency, competing against hundreds of + generalist firms on price, applies blue ocean strategy and identifies an + uncontested space: fractional CTO services for non-technical founders. + They eliminate traditional agency deliverables (proposals, wireframes, + design comps) and instead embed a senior technologist directly in the + founder's decision-making process. The pricing shifts from project-based + to monthly retainer. Competitors cannot follow because they are structured + around project delivery teams, not individual advisory relationships." + benchmark_references: [ "average-billable-rate", "client-retention-rate", "revenue-per-client" ] - skill: "business-model-canvas" category: "frameworks" agency_relevance: "critical" - agency_context: "The Business Model Canvas for agencies requires fundamental reinterpretation of nearly every block. Key Resources: the firm's people, their expertise, and their relationships — there are no physical assets, patents, or technology platforms that constitute a moat. Revenue Streams: must decompose into the pricing spectrum — hourly, project-based, retainer, value-based, and productized — each with radically different economics and risk profiles. Cost Structure: dominated by salaries (typically 55-70% of revenue) with relatively thin variable costs. Customer Relationships: the relationship IS the value proposition; clients buy the person, not the firm. Channels: referrals, thought leadership, speaking, and networking — not advertising or digital marketing in most cases. The canvas is most powerful for agencies when used to map the transition from a time-selling model to a value-selling or productized model." + agency_context: "The Business Model Canvas for agencies requires fundamental + reinterpretation of nearly every block. Key Resources: the firm's people, + their expertise, and their relationships — there are no physical assets, + patents, or technology platforms that constitute a moat. Revenue Streams: + must decompose into the pricing spectrum — hourly, project-based, + retainer, value-based, and productized — each with radically different + economics and risk profiles. Cost Structure: dominated by salaries + (typically 55-70% of revenue) with relatively thin variable costs. + Customer Relationships: the relationship IS the value proposition; clients + buy the person, not the firm. Channels: referrals, thought leadership, + speaking, and networking — not advertising or digital marketing in most + cases. The canvas is most powerful for agencies when used to map the + transition from a time-selling model to a value-selling or productized + model." agency_anti_patterns: - - "Listing 'expertise' or 'talent' as the Value Proposition without specifying what outcome that expertise delivers. Clients do not buy expertise — they buy results. The value proposition must be framed as a measurable client outcome." - - "Omitting freelancers and subcontractors from Key Partnerships. For most agencies, the ability to scale through the Shamrock model (core staff + contractors) is a critical strategic asset." - - "Treating the canvas as static. Agency business models must evolve as the firm grows — from founder-does-everything to leveraged delivery to productized services." - agency_example: "A two-person branding consultancy uses the canvas to identify a strategic vulnerability: their Key Resource is the founder's personal reputation, their Channel is the founder's network, and their Revenue Stream is 100% project-based billing. The canvas redesign introduces a second channel (content marketing to build the firm's brand beyond the founder), a second revenue stream (a productized brand audit at a fixed price), and a Key Partnership with a stable of freelance designers who extend capacity without increasing fixed costs." - benchmark_references: ["revenue-per-employee", "revenue-per-client", "gross-margin", "leverage-ratio"] + - "Listing 'expertise' or 'talent' as the Value Proposition without + specifying what outcome that expertise delivers. Clients do not buy + expertise — they buy results. The value proposition must be framed as a + measurable client outcome." + - "Omitting freelancers and subcontractors from Key Partnerships. For most + agencies, the ability to scale through the Shamrock model (core staff + + contractors) is a critical strategic asset." + - "Treating the canvas as static. Agency business models must evolve as + the firm grows — from founder-does-everything to leveraged delivery to + productized services." + agency_example: "A two-person branding consultancy uses the canvas to identify a + strategic vulnerability: their Key Resource is the founder's personal + reputation, their Channel is the founder's network, and their Revenue + Stream is 100% project-based billing. The canvas redesign introduces a + second channel (content marketing to build the firm's brand beyond the + founder), a second revenue stream (a productized brand audit at a fixed + price), and a Key Partnership with a stable of freelance designers who + extend capacity without increasing fixed costs." + benchmark_references: + [ + "revenue-per-employee", + "revenue-per-client", + "gross-margin", + "leverage-ratio" + ] - skill: "four-ps-marketing" category: "frameworks" agency_relevance: "critical" - agency_context: "The Four Ps require radical adaptation for professional services because the 'product' is intangible, produced and consumed simultaneously, and varies with every engagement. Product in agencies is the service itself — defined by methodology, expertise, and the quality of the team assigned. The agency's challenge is to make an intangible, variable service feel tangible and consistent through packaging, case studies, and proprietary frameworks. Price is the single hardest decision — hourly, project, retainer, value-based, or hybrid. Most agencies default to hourly or project pricing and leave enormous value on the table. Place means distribution: where clients find the agency — referral networks, conferences, content, directories, or partnerships. Promotion for professional services is fundamentally different from product promotion: thought leadership, speaking, publishing, and case studies replace advertising." + agency_context: "The Four Ps require radical adaptation for professional + services because the 'product' is intangible, produced and consumed + simultaneously, and varies with every engagement. Product in agencies is + the service itself — defined by methodology, expertise, and the quality of + the team assigned. The agency's challenge is to make an intangible, + variable service feel tangible and consistent through packaging, case + studies, and proprietary frameworks. Price is the single hardest decision + — hourly, project, retainer, value-based, or hybrid. Most agencies default + to hourly or project pricing and leave enormous value on the table. Place + means distribution: where clients find the agency — referral networks, + conferences, content, directories, or partnerships. Promotion for + professional services is fundamentally different from product promotion: + thought leadership, speaking, publishing, and case studies replace + advertising." agency_anti_patterns: - - "Pricing based on cost-plus (hours x rate + margin) rather than value delivered. Cost-plus pricing caps revenue at the number of available hours. Value-based pricing decouples revenue from time." - - "Promoting capabilities instead of outcomes. Clients do not care that the agency 'does brand strategy.' They care that the agency 'helps companies increase market share through repositioning.'" - - "Treating 'Place' as a website. The most effective distribution channels for agencies are referral networks, partner relationships, and speaking platforms — not websites." - agency_example: "A management consulting firm uses the Four Ps to restructure its go-to-market. Product: they package their strategy offering into three tiers — diagnostic (2-week engagement), strategy development (6-week engagement), and implementation support (ongoing retainer). Price: they shift from day-rate billing to fixed-price engagements with value-based premiums for outcome achievement. Place: they invest in industry conference speaking and a quarterly research report that generates inbound leads. Promotion: they replace generic capability decks with vertical-specific case studies that demonstrate measurable client outcomes." - benchmark_references: ["average-billable-rate", "win-rate", "cost-per-lead", "average-project-value"] + - "Pricing based on cost-plus (hours x rate + margin) rather than value + delivered. Cost-plus pricing caps revenue at the number of available + hours. Value-based pricing decouples revenue from time." + - "Promoting capabilities instead of outcomes. Clients do not care that + the agency 'does brand strategy.' They care that the agency 'helps + companies increase market share through repositioning.'" + - "Treating 'Place' as a website. The most effective distribution channels + for agencies are referral networks, partner relationships, and speaking + platforms — not websites." + agency_example: "A management consulting firm uses the Four Ps to restructure + its go-to-market. Product: they package their strategy offering into three + tiers — diagnostic (2-week engagement), strategy development (6-week + engagement), and implementation support (ongoing retainer). Price: they + shift from day-rate billing to fixed-price engagements with value-based + premiums for outcome achievement. Place: they invest in industry + conference speaking and a quarterly research report that generates inbound + leads. Promotion: they replace generic capability decks with + vertical-specific case studies that demonstrate measurable client + outcomes." + benchmark_references: + [ + "average-billable-rate", + "win-rate", + "cost-per-lead", + "average-project-value" + ] - skill: "net-promoter-score" category: "frameworks" agency_relevance: "critical" - agency_context: "NPS is the single most predictive metric for agency growth because agencies grow primarily through referrals. A high NPS means clients actively recommend the firm to peers — the most efficient and highest-converting sales channel in professional services. In agencies, NPS should be measured at two critical moments: mid-engagement (to catch problems before they damage the relationship) and post-engagement (to capture the final impression). The qualitative follow-up question ('why did you give that score?') is more valuable than the score itself — it reveals whether satisfaction is driven by the quality of work, the quality of the relationship, or both. Segmenting NPS by engagement type (project vs. retainer), client size, and account manager reveals which parts of the firm drive advocacy." + agency_context: "NPS is the single most predictive metric for agency growth + because agencies grow primarily through referrals. A high NPS means + clients actively recommend the firm to peers — the most efficient and + highest-converting sales channel in professional services. In agencies, + NPS should be measured at two critical moments: mid-engagement (to catch + problems before they damage the relationship) and post-engagement (to + capture the final impression). The qualitative follow-up question ('why + did you give that score?') is more valuable than the score itself — it + reveals whether satisfaction is driven by the quality of work, the quality + of the relationship, or both. Segmenting NPS by engagement type (project + vs. retainer), client size, and account manager reveals which parts of the + firm drive advocacy." agency_anti_patterns: - - "Surveying clients only after project completion. By then, a dissatisfied client has already formed opinions that may have spread through their network. Mid-project check-ins catch problems early." - - "Accepting high NPS without building a formal referral program. Promoters recommend when asked and given a mechanism — not spontaneously. Build the ask into the post-project process." - - "Treating NPS as a firm-wide number when it is really an individual-level metric. In agencies, NPS reflects the account lead, not the firm. Track by account manager to identify who drives advocacy." - agency_example: "A PR agency discovers that its overall NPS of 45 masks a bimodal distribution: retainer clients score 65+ while project clients score 25. Investigation reveals that retainer relationships build the trust and familiarity that drive satisfaction, while project engagements feel transactional. The agency responds by converting its best project clients to retainer relationships and redesigning the project experience to include relationship-building touchpoints (monthly calls, proactive recommendations) even during discrete engagements." - benchmark_references: ["nps-client", "client-retention-rate", "revenue-per-client"] + - "Surveying clients only after project completion. By then, a + dissatisfied client has already formed opinions that may have spread + through their network. Mid-project check-ins catch problems early." + - "Accepting high NPS without building a formal referral program. + Promoters recommend when asked and given a mechanism — not + spontaneously. Build the ask into the post-project process." + - "Treating NPS as a firm-wide number when it is really an + individual-level metric. In agencies, NPS reflects the account lead, not + the firm. Track by account manager to identify who drives advocacy." + agency_example: "A PR agency discovers that its overall NPS of 45 masks a + bimodal distribution: retainer clients score 65+ while project clients + score 25. Investigation reveals that retainer relationships build the + trust and familiarity that drive satisfaction, while project engagements + feel transactional. The agency responds by converting its best project + clients to retainer relationships and redesigning the project experience + to include relationship-building touchpoints (monthly calls, proactive + recommendations) even during discrete engagements." + benchmark_references: [ "nps-client", "client-retention-rate", "revenue-per-client" ] - skill: "shamrock-organisation" category: "frameworks" agency_relevance: "critical" - agency_context: "The Shamrock Organisation is perhaps the most directly applicable framework to agency economics. Its three leaves map precisely to how modern agencies operate. The first leaf (core professional staff) represents the full-time team whose expertise, client relationships, and institutional knowledge define the firm. The second leaf (the flexible labor force) includes freelancers, subcontractors, and specialist contractors who extend capacity without increasing fixed costs — this is the primary mechanism by which agencies manage the feast-or-famine revenue cycle. The third leaf (outsourced functions) covers bookkeeping, IT support, legal, and increasingly, production tasks that AI and offshore teams handle. The strategic question for every agency is: what belongs in each leaf? The answer determines the firm's cost structure, flexibility, quality consistency, and scalability." + agency_context: "The Shamrock Organisation is perhaps the most directly + applicable framework to agency economics. Its three leaves map precisely + to how modern agencies operate. The first leaf (core professional staff) + represents the full-time team whose expertise, client relationships, and + institutional knowledge define the firm. The second leaf (the flexible + labor force) includes freelancers, subcontractors, and specialist + contractors who extend capacity without increasing fixed costs — this is + the primary mechanism by which agencies manage the feast-or-famine revenue + cycle. The third leaf (outsourced functions) covers bookkeeping, IT + support, legal, and increasingly, production tasks that AI and offshore + teams handle. The strategic question for every agency is: what belongs in + each leaf? The answer determines the firm's cost structure, flexibility, + quality consistency, and scalability." agency_anti_patterns: - - "Over-relying on the flexible leaf (freelancers) to the point where the firm has no core identity or consistent quality. When most delivery is outsourced, the agency becomes a broker, not a firm." - - "Refusing to use the flexible leaf out of a belief that all work must be done by full-time staff. This creates utilization crises during slow periods and capacity crises during busy periods." - - "Placing client-facing roles in the flexible leaf. Client relationship management should be core — freelancers who interact directly with clients without oversight erode trust and brand consistency." - agency_example: "A 15-person digital agency uses the Shamrock model to redesign its staffing structure. Core (first leaf): 10 people including strategy, account management, creative direction, and project management — roles where consistency and client relationships are paramount. Flexible (second leaf): a vetted pool of 25 freelance designers, developers, and writers who scale delivery capacity from 10 to 30 people as demand fluctuates. Outsourced (third leaf): bookkeeping, payroll, QA testing, and basic production tasks handled by a virtual assistant service and an offshore QA team. This structure reduces fixed costs by 30% while maintaining quality on client-facing work." - benchmark_references: ["utilization-rate", "bench-time", "gross-margin", "overhead-ratio"] + - "Over-relying on the flexible leaf (freelancers) to the point where the + firm has no core identity or consistent quality. When most delivery is + outsourced, the agency becomes a broker, not a firm." + - "Refusing to use the flexible leaf out of a belief that all work must be + done by full-time staff. This creates utilization crises during slow + periods and capacity crises during busy periods." + - "Placing client-facing roles in the flexible leaf. Client relationship + management should be core — freelancers who interact directly with + clients without oversight erode trust and brand consistency." + agency_example: "A 15-person digital agency uses the Shamrock model to redesign + its staffing structure. Core (first leaf): 10 people including strategy, + account management, creative direction, and project management — roles + where consistency and client relationships are paramount. Flexible (second + leaf): a vetted pool of 25 freelance designers, developers, and writers + who scale delivery capacity from 10 to 30 people as demand fluctuates. + Outsourced (third leaf): bookkeeping, payroll, QA testing, and basic + production tasks handled by a virtual assistant service and an offshore QA + team. This structure reduces fixed costs by 30% while maintaining quality + on client-facing work." + benchmark_references: [ "utilization-rate", "bench-time", "gross-margin", "overhead-ratio" ] - skill: "trust-equation" category: "frameworks" agency_relevance: "critical" - agency_context: "Trust is EVERYTHING in professional services. Clients buy the person before they buy the firm. The Trust Equation (Credibility + Reliability + Intimacy / Self-Orientation) is the master framework for agency business development and client retention. Credibility in agencies is built through case studies, thought leadership, credentials, and the team's experience — it is what gets the agency into the room. Reliability is demonstrated through consistent delivery, meeting deadlines, and keeping promises — it is what keeps the client. Intimacy is the willingness to have honest, sometimes uncomfortable conversations about the client's business, not just the project scope — it is what deepens the relationship. Self-Orientation is the agency's tendency to prioritize its own interests (pushing unnecessary scope, recommending more work rather than less, obscuring results to justify continued engagement). Low self-orientation — the willingness to tell a client they do not need the agency's services — paradoxically generates the most trust and the most referrals." + agency_context: "Trust is EVERYTHING in professional services. Clients buy the + person before they buy the firm. The Trust Equation (Credibility + + Reliability + Intimacy / Self-Orientation) is the master framework for + agency business development and client retention. Credibility in agencies + is built through case studies, thought leadership, credentials, and the + team's experience — it is what gets the agency into the room. Reliability + is demonstrated through consistent delivery, meeting deadlines, and + keeping promises — it is what keeps the client. Intimacy is the + willingness to have honest, sometimes uncomfortable conversations about + the client's business, not just the project scope — it is what deepens the + relationship. Self-Orientation is the agency's tendency to prioritize its + own interests (pushing unnecessary scope, recommending more work rather + than less, obscuring results to justify continued engagement). Low + self-orientation — the willingness to tell a client they do not need the + agency's services — paradoxically generates the most trust and the most + referrals." agency_anti_patterns: - - "Building credibility through credentials alone while neglecting reliability. A firm with impressive case studies that misses deadlines and delivers inconsistently will lose to a less credentialed firm that delivers on time, every time." - - "Avoiding intimacy by keeping the relationship 'professional.' Agencies that never push back on a client's bad ideas, never share uncomfortable truths, and never challenge assumptions are valued less than those with the courage to have honest conversations." - - "Recommending more work when less is needed. The short-term revenue gain from expanding scope is dwarfed by the long-term trust earned by telling a client when they do not need additional help." - agency_example: "A strategy consultancy loses a competitive pitch despite having the strongest credentials and the most impressive case studies. Post-mortem analysis through the trust equation reveals the gap: the winning firm demonstrated intimacy during the pitch process — they challenged the client's assumptions, asked probing questions about root causes rather than symptoms, and told the client that one of their three stated priorities was misguided. The losing firm presented polished credentials (credibility) but never demonstrated the willingness to engage honestly (intimacy). The lesson: clients hire agencies that tell them what they need to hear, not what they want to hear." - benchmark_references: ["nps-client", "client-retention-rate", "win-rate"] + - "Building credibility through credentials alone while neglecting + reliability. A firm with impressive case studies that misses deadlines + and delivers inconsistently will lose to a less credentialed firm that + delivers on time, every time." + - "Avoiding intimacy by keeping the relationship 'professional.' Agencies + that never push back on a client's bad ideas, never share uncomfortable + truths, and never challenge assumptions are valued less than those with + the courage to have honest conversations." + - "Recommending more work when less is needed. The short-term revenue gain + from expanding scope is dwarfed by the long-term trust earned by telling + a client when they do not need additional help." + agency_example: "A strategy consultancy loses a competitive pitch despite having + the strongest credentials and the most impressive case studies. + Post-mortem analysis through the trust equation reveals the gap: the + winning firm demonstrated intimacy during the pitch process — they + challenged the client's assumptions, asked probing questions about root + causes rather than symptoms, and told the client that one of their three + stated priorities was misguided. The losing firm presented polished + credentials (credibility) but never demonstrated the willingness to engage + honestly (intimacy). The lesson: clients hire agencies that tell them what + they need to hear, not what they want to hear." + benchmark_references: [ "nps-client", "client-retention-rate", "win-rate" ] - - skill: "pricing-diagnosis" - category: "frameworks" + - category: "frameworks" agency_relevance: "critical" - agency_context: "Pricing is the single most consequential strategic decision in professional services — and the one most agencies get wrong. The agency pricing spectrum runs from hourly billing (lowest value capture, easiest to sell, punishes efficiency) through project-based (moderate value capture, requires accurate scoping) through retainer (stable revenue, rewards relationship depth) to value-based (highest value capture, hardest to implement, decouples revenue from time). Most agencies default to hourly or project pricing because it is familiar and 'safe,' but this ceiling caps revenue at available hours multiplied by acceptable rates. The pricing diagnosis for agencies must evaluate: current pricing model and its limitations, the gap between value delivered and price charged (most agencies capture 15-30% of the value they create), client willingness to pay for outcomes versus inputs, and the firm's ability to estimate and manage scope (the prerequisite for fixed-price and value-based models)." + agency_context: "Pricing is the single most consequential strategic decision in + professional services — and the one most agencies get wrong. The agency + pricing spectrum runs from hourly billing (lowest value capture, easiest + to sell, punishes efficiency) through project-based (moderate value + capture, requires accurate scoping) through retainer (stable revenue, + rewards relationship depth) to value-based (highest value capture, hardest + to implement, decouples revenue from time). Most agencies default to + hourly or project pricing because it is familiar and 'safe,' but this + ceiling caps revenue at available hours multiplied by acceptable rates. + The pricing diagnosis for agencies must evaluate: current pricing model + and its limitations, the gap between value delivered and price charged + (most agencies capture 15-30% of the value they create), client + willingness to pay for outcomes versus inputs, and the firm's ability to + estimate and manage scope (the prerequisite for fixed-price and + value-based models)." agency_anti_patterns: - - "Competing on price. Agencies that win work by being the cheapest attract the worst clients — those who value cost over quality, negotiate relentlessly, and leave when a cheaper option appears." - - "Discounting to fill capacity. When bench time rises, the temptation to discount rates to win any available work is strong. But discounted work sets a new price anchor, trains clients to expect lower rates, and attracts the wrong client profile." - - "Charging hourly for strategic work. Hourly billing for strategy engagements punishes the agency for being fast and experienced — a senior strategist who solves a problem in 2 hours earns less than a junior who takes 20 hours. Value-based pricing is the appropriate model for advisory work." - agency_example: "A design agency charging $150/hour for all work discovers through pricing diagnosis that their effective rate is $105/hour after scope creep, write-offs, and discounting. The diagnosis reveals three pricing failures: (1) hourly billing punishes their efficiency — a logo redesign takes the senior designer 15 hours but would take a competitor 40, yet the client pays less for the superior result; (2) project scoping is inaccurate, leading to systematic undercharging on complex projects; (3) retainer clients are billed hourly against a monthly budget that consistently goes unused, creating guilt on the client side. The fix: shift to value-based project pricing for strategic work, fixed-fee productized packages for recurring work, and outcome-linked retainers for ongoing relationships." - benchmark_references: ["average-billable-rate", "effective-billable-rate", "gross-margin", "revenue-per-employee"] + - "Competing on price. Agencies that win work by being the cheapest + attract the worst clients — those who value cost over quality, negotiate + relentlessly, and leave when a cheaper option appears." + - "Discounting to fill capacity. When bench time rises, the temptation to + discount rates to win any available work is strong. But discounted work + sets a new price anchor, trains clients to expect lower rates, and + attracts the wrong client profile." + - "Charging hourly for strategic work. Hourly billing for strategy + engagements punishes the agency for being fast and experienced — a + senior strategist who solves a problem in 2 hours earns less than a + junior who takes 20 hours. Value-based pricing is the appropriate model + for advisory work." + agency_example: "A design agency charging $150/hour for all work discovers + through pricing diagnosis that their effective rate is $105/hour after + scope creep, write-offs, and discounting. The diagnosis reveals three + pricing failures: (1) hourly billing punishes their efficiency — a logo + redesign takes the senior designer 15 hours but would take a competitor + 40, yet the client pays less for the superior result; (2) project scoping + is inaccurate, leading to systematic undercharging on complex projects; + (3) retainer clients are billed hourly against a monthly budget that + consistently goes unused, creating guilt on the client side. The fix: + shift to value-based project pricing for strategic work, fixed-fee + productized packages for recurring work, and outcome-linked retainers for + ongoing relationships." + benchmark_references: + [ + "average-billable-rate", + "effective-billable-rate", + "gross-margin", + "revenue-per-employee" + ] + kind: diagnostic + ref: pricing-diagnosis - skill: "balanced-scorecard" category: "frameworks" agency_relevance: "critical" - agency_context: "The Balanced Scorecard translates directly into agency operating metrics across its four perspectives, with one critical modification: people are the central asset, not technology or products. Financial perspective: revenue per employee, gross margin, EBITDA margin, utilization rate, effective billable rate. Client perspective: NPS, client retention rate, revenue per client, scope creep rate. Internal process perspective: proposal win rate, project delivery on time and on budget, bench time, AR days. Learning & Growth perspective: employee NPS, employee retention, training hours per person, senior-to-junior development pipeline. The scorecard is particularly powerful in agencies because it forces balance between financial extraction (utilization, rates) and organizational health (employee satisfaction, training) — the tension that defines agency management." + agency_context: "The Balanced Scorecard translates directly into agency + operating metrics across its four perspectives, with one critical + modification: people are the central asset, not technology or products. + Financial perspective: revenue per employee, gross margin, EBITDA margin, + utilization rate, effective billable rate. Client perspective: NPS, client + retention rate, revenue per client, scope creep rate. Internal process + perspective: proposal win rate, project delivery on time and on budget, + bench time, AR days. Learning & Growth perspective: employee NPS, employee + retention, training hours per person, senior-to-junior development + pipeline. The scorecard is particularly powerful in agencies because it + forces balance between financial extraction (utilization, rates) and + organizational health (employee satisfaction, training) — the tension that + defines agency management." agency_anti_patterns: - - "Overweighting the financial perspective at the expense of Learning & Growth. Agencies that maximize utilization and minimize training investment earn higher short-term margins but lose talent and degrade quality over time." - - "Ignoring the internal process perspective. Most agencies do not track proposal efficiency, project profitability, or bench management with the same rigor they apply to revenue." - - "Treating the scorecard as a reporting tool rather than a management tool. The scorecard should drive weekly leadership discussions about trade-offs — is the push for higher utilization damaging employee satisfaction?" - agency_example: "A 30-person consulting firm implements a balanced scorecard and discovers a dangerous imbalance: financial metrics are strong (utilization at 78%, margins at 18%) but Learning & Growth metrics are deteriorating (eNPS at 12, retention at 72%, training hours at zero). The scorecard reveals that the firm has been maximizing short-term profits by running people hard with no investment in development. The corrective action: reduce utilization target to 70%, institute 'innovation Fridays' for professional development, and implement a mentoring program. Within two quarters, eNPS rises to 35 and retention improves to 88% — the financial metrics stabilize at slightly lower but sustainable levels." - benchmark_references: ["revenue-per-employee", "utilization-rate", "nps-client", "enps", "employee-retention-rate"] + - "Overweighting the financial perspective at the expense of Learning & + Growth. Agencies that maximize utilization and minimize training + investment earn higher short-term margins but lose talent and degrade + quality over time." + - "Ignoring the internal process perspective. Most agencies do not track + proposal efficiency, project profitability, or bench management with the + same rigor they apply to revenue." + - "Treating the scorecard as a reporting tool rather than a management + tool. The scorecard should drive weekly leadership discussions about + trade-offs — is the push for higher utilization damaging employee + satisfaction?" + agency_example: "A 30-person consulting firm implements a balanced scorecard and + discovers a dangerous imbalance: financial metrics are strong (utilization + at 78%, margins at 18%) but Learning & Growth metrics are deteriorating + (eNPS at 12, retention at 72%, training hours at zero). The scorecard + reveals that the firm has been maximizing short-term profits by running + people hard with no investment in development. The corrective action: + reduce utilization target to 70%, institute 'innovation Fridays' for + professional development, and implement a mentoring program. Within two + quarters, eNPS rises to 35 and retention improves to 88% — the financial + metrics stabilize at slightly lower but sustainable levels." + benchmark_references: + [ + "revenue-per-employee", + "utilization-rate", + "nps-client", + "enps", + "employee-retention-rate" + ] - skill: "product-life-cycle" category: "frameworks" agency_relevance: "high" - agency_context: "Professional services do not have traditional product lifecycles, but the concept applies powerfully to service offerings. Every agency service line passes through introduction (the firm develops a new capability), growth (demand exceeds capacity and the service is profitable), maturity (the service becomes commoditized, competition drives down pricing), and decline (clients no longer need the service or cheaper alternatives emerge). The critical agency insight: service lines must be actively managed as a portfolio. Social media management was a growth service in 2015 and is commoditized in 2026. AI strategy consulting is in the introduction phase now and will eventually mature. Agencies that ride a single service line through its full lifecycle without developing successors face existential risk." + agency_context: "Professional services do not have traditional product + lifecycles, but the concept applies powerfully to service offerings. Every + agency service line passes through introduction (the firm develops a new + capability), growth (demand exceeds capacity and the service is + profitable), maturity (the service becomes commoditized, competition + drives down pricing), and decline (clients no longer need the service or + cheaper alternatives emerge). The critical agency insight: service lines + must be actively managed as a portfolio. Social media management was a + growth service in 2015 and is commoditized in 2026. AI strategy consulting + is in the introduction phase now and will eventually mature. Agencies that + ride a single service line through its full lifecycle without developing + successors face existential risk." agency_anti_patterns: - - "Clinging to a mature service line because 'it is what we are known for.' Reputation built on a commoditized service is a trap — the firm will compete on price in a declining market." - - "Investing equally across all service lines regardless of lifecycle position. Services in growth deserve disproportionate investment; services in decline should be harvested for margin, not invested in for growth." - - "Failing to sunset declining services. Agencies often maintain services nobody wants because existing staff are skilled in them. This misallocates talent." - agency_example: "A digital agency's SEO service line, once its primary revenue driver, has entered maturity — clients demand it but treat it as a commodity, competition from freelancers and tools drives down rates, and margins have compressed from 60% to 35%. Rather than fighting for share in a commoditizing market, the agency uses lifecycle analysis to launch two growth-phase offerings: AI-powered content strategy (leveraging their SEO data assets) and conversion rate optimization. The mature SEO practice becomes a client-acquisition funnel for higher-margin growth services." - benchmark_references: ["gross-margin", "average-billable-rate", "revenue"] + - "Clinging to a mature service line because 'it is what we are known + for.' Reputation built on a commoditized service is a trap — the firm + will compete on price in a declining market." + - "Investing equally across all service lines regardless of lifecycle + position. Services in growth deserve disproportionate investment; + services in decline should be harvested for margin, not invested in for + growth." + - "Failing to sunset declining services. Agencies often maintain services + nobody wants because existing staff are skilled in them. This + misallocates talent." + agency_example: "A digital agency's SEO service line, once its primary revenue + driver, has entered maturity — clients demand it but treat it as a + commodity, competition from freelancers and tools drives down rates, and + margins have compressed from 60% to 35%. Rather than fighting for share in + a commoditizing market, the agency uses lifecycle analysis to launch two + growth-phase offerings: AI-powered content strategy (leveraging their SEO + data assets) and conversion rate optimization. The mature SEO practice + becomes a client-acquisition funnel for higher-margin growth services." + benchmark_references: [ "gross-margin", "average-billable-rate", "revenue" ] - skill: "disruptive-innovation" category: "frameworks" agency_relevance: "high" - agency_context: "Professional services are being disrupted from multiple directions simultaneously. AI tools are the most visible disruptor — they perform tasks (writing, design, analysis, coding) that agencies bill for. Freelancer platforms disrupt from below with lower overhead and more flexible engagement models. Productized service firms (like Design Pickle for design or LAIRE for marketing) disrupt with standardized, subscription-based delivery that replaces custom agency work. Offshore teams disrupt on cost. The disruption framework helps agencies identify which of their services are vulnerable, which are defensible, and how to position the firm where automation and commoditization cannot follow — typically in strategy, relationship management, creative direction, and complex problem-solving." + agency_context: "Professional services are being disrupted from multiple + directions simultaneously. AI tools are the most visible disruptor — they + perform tasks (writing, design, analysis, coding) that agencies bill for. + Freelancer platforms disrupt from below with lower overhead and more + flexible engagement models. Productized service firms (like Design Pickle + for design or LAIRE for marketing) disrupt with standardized, + subscription-based delivery that replaces custom agency work. Offshore + teams disrupt on cost. The disruption framework helps agencies identify + which of their services are vulnerable, which are defensible, and how to + position the firm where automation and commoditization cannot follow — + typically in strategy, relationship management, creative direction, and + complex problem-solving." agency_anti_patterns: - - "Dismissing AI as 'not good enough' for client work. AI tools will improve faster than most agencies expect. The correct response is to integrate AI into delivery to increase efficiency, not to ignore it." - - "Trying to compete with disruptors on their terms. An agency cannot out-price a freelancer collective or out-automate an AI tool. The response must be differentiation, not cost reduction." - - "Waiting for disruption to arrive rather than proactively repositioning. By the time a service is visibly commoditized, margins have already eroded." - agency_example: "A copywriting agency recognizes that AI writing tools are a disruptive threat to its core service. Rather than competing with AI on content production, the agency repositions upmarket: it becomes a content strategy consultancy that uses AI tools internally to produce more content faster, while selling strategic thinking, brand voice development, and editorial oversight that AI cannot replicate. The firm's revenue per employee increases 40% as production costs drop while strategic fees rise." - benchmark_references: ["average-billable-rate", "revenue-per-employee", "gross-margin"] + - "Dismissing AI as 'not good enough' for client work. AI tools will + improve faster than most agencies expect. The correct response is to + integrate AI into delivery to increase efficiency, not to ignore it." + - "Trying to compete with disruptors on their terms. An agency cannot + out-price a freelancer collective or out-automate an AI tool. The + response must be differentiation, not cost reduction." + - "Waiting for disruption to arrive rather than proactively repositioning. + By the time a service is visibly commoditized, margins have already + eroded." + agency_example: "A copywriting agency recognizes that AI writing tools are a + disruptive threat to its core service. Rather than competing with AI on + content production, the agency repositions upmarket: it becomes a content + strategy consultancy that uses AI tools internally to produce more content + faster, while selling strategic thinking, brand voice development, and + editorial oversight that AI cannot replicate. The firm's revenue per + employee increases 40% as production costs drop while strategic fees + rise." + benchmark_references: [ "average-billable-rate", "revenue-per-employee", "gross-margin" ] - skill: "growth-share-matrix" category: "frameworks" agency_relevance: "high" - agency_context: "The BCG Growth-Share Matrix maps to agency service lines and client segments. Stars: high-growth, high-share service lines (e.g., AI consulting for an early-mover agency) that justify aggressive hiring and investment. Cash Cows: mature, dominant service lines (e.g., established web development practice) that generate reliable revenue and fund investment in Stars. Question Marks: new service lines with potential but unproven demand (e.g., a new industry vertical). Dogs: underperforming service lines with low growth and low share (e.g., print design in a digital world). The matrix is equally useful when applied to client segments — which client types generate the best margins with the least effort, and which consume disproportionate resources?" + agency_context: "The BCG Growth-Share Matrix maps to agency service lines and + client segments. Stars: high-growth, high-share service lines (e.g., AI + consulting for an early-mover agency) that justify aggressive hiring and + investment. Cash Cows: mature, dominant service lines (e.g., established + web development practice) that generate reliable revenue and fund + investment in Stars. Question Marks: new service lines with potential but + unproven demand (e.g., a new industry vertical). Dogs: underperforming + service lines with low growth and low share (e.g., print design in a + digital world). The matrix is equally useful when applied to client + segments — which client types generate the best margins with the least + effort, and which consume disproportionate resources?" agency_anti_patterns: - - "Killing 'Dog' service lines that serve as entry points for larger engagements. A low-margin service that consistently leads to high-margin follow-on work is strategically valuable despite its standalone economics." - - "Over-investing in Stars without building delivery capacity. Winning more AI strategy work than the firm can deliver damages reputation and quality." - - "Failing to apply the matrix to client segments. Some client types are 'Dogs' — low growth, high maintenance, poor margins — and should be actively managed out of the portfolio." - agency_example: "A marketing agency applies the matrix to its client portfolio and discovers that its largest client category (startups) is a Question Mark — high growth but low share (many competitors) and poor margins (startups negotiate hard and churn fast). Its mid-market B2B clients are Cash Cows — stable relationships, good margins, steady work. The agency redirects growth investment from startup acquisition to mid-market B2B deepening, using Cash Cow profits to fund a Star initiative: a productized marketing audit specifically designed for mid-market B2B companies." - benchmark_references: ["revenue-per-client", "gross-margin", "client-retention-rate"] + - "Killing 'Dog' service lines that serve as entry points for larger + engagements. A low-margin service that consistently leads to high-margin + follow-on work is strategically valuable despite its standalone + economics." + - "Over-investing in Stars without building delivery capacity. Winning + more AI strategy work than the firm can deliver damages reputation and + quality." + - "Failing to apply the matrix to client segments. Some client types are + 'Dogs' — low growth, high maintenance, poor margins — and should be + actively managed out of the portfolio." + agency_example: "A marketing agency applies the matrix to its client portfolio + and discovers that its largest client category (startups) is a Question + Mark — high growth but low share (many competitors) and poor margins + (startups negotiate hard and churn fast). Its mid-market B2B clients are + Cash Cows — stable relationships, good margins, steady work. The agency + redirects growth investment from startup acquisition to mid-market B2B + deepening, using Cash Cow profits to fund a Star initiative: a productized + marketing audit specifically designed for mid-market B2B companies." + benchmark_references: [ "revenue-per-client", "gross-margin", "client-retention-rate" ] - skill: "swot-pest-analysis" category: "frameworks" agency_relevance: "high" - agency_context: "SWOT and PEST analysis for agencies must account for the unique environmental forces shaping professional services. Political: government procurement regulations, data privacy laws that affect agency work, immigration policies that impact talent availability. Economic: corporate marketing and consulting budget cycles, recession sensitivity (agencies are often first to be cut), interest rates affecting client investment. Social: remote work enabling agencies to hire globally (and clients to hire globally too), the rise of the creator economy as a substitute for agency services, generational expectations of work-life balance. Technological: AI tools transforming every agency discipline, project management and collaboration tools reducing overhead, the collapse of barriers between agency services (design, development, marketing converging)." + agency_context: "SWOT and PEST analysis for agencies must account for the unique + environmental forces shaping professional services. Political: government + procurement regulations, data privacy laws that affect agency work, + immigration policies that impact talent availability. Economic: corporate + marketing and consulting budget cycles, recession sensitivity (agencies + are often first to be cut), interest rates affecting client investment. + Social: remote work enabling agencies to hire globally (and clients to + hire globally too), the rise of the creator economy as a substitute for + agency services, generational expectations of work-life balance. + Technological: AI tools transforming every agency discipline, project + management and collaboration tools reducing overhead, the collapse of + barriers between agency services (design, development, marketing + converging)." agency_anti_patterns: - - "Listing 'talented team' as a Strength without acknowledging that talent is also the primary constraint. The team that is a strength today becomes a weakness when key people leave." - - "Ignoring the Technology PEST factor. Agencies that do not understand how AI is reshaping their disciplines will be blindsided by disruption." - - "Conducting SWOT as a feel-good exercise that lists more Strengths than Weaknesses. Honest SWOT requires more courage in agencies because weaknesses are often personal — the founder's limitations, key person dependency, or lack of systems." - agency_example: "A PR agency conducts a PEST analysis and identifies that AI-generated media monitoring and sentiment analysis (Technology) will commoditize a service that generates 30% of revenue, that a generational shift toward authenticity and transparency (Social) creates an opportunity for their crisis communications practice, and that tightening data privacy regulations (Political) will increase demand for compliance-aware communications. The SWOT reveals that their Weakness — lack of data analytics capability — prevents them from capitalizing on the Technology threat. The strategic response: partner with a data analytics firm rather than building the capability internally." - benchmark_references: ["revenue", "gross-margin", "average-billable-rate"] + - "Listing 'talented team' as a Strength without acknowledging that talent + is also the primary constraint. The team that is a strength today + becomes a weakness when key people leave." + - "Ignoring the Technology PEST factor. Agencies that do not understand + how AI is reshaping their disciplines will be blindsided by disruption." + - "Conducting SWOT as a feel-good exercise that lists more Strengths than + Weaknesses. Honest SWOT requires more courage in agencies because + weaknesses are often personal — the founder's limitations, key person + dependency, or lack of systems." + agency_example: "A PR agency conducts a PEST analysis and identifies that + AI-generated media monitoring and sentiment analysis (Technology) will + commoditize a service that generates 30% of revenue, that a generational + shift toward authenticity and transparency (Social) creates an opportunity + for their crisis communications practice, and that tightening data privacy + regulations (Political) will increase demand for compliance-aware + communications. The SWOT reveals that their Weakness — lack of data + analytics capability — prevents them from capitalizing on the Technology + threat. The strategic response: partner with a data analytics firm rather + than building the capability internally." + benchmark_references: [ "revenue", "gross-margin", "average-billable-rate" ] - skill: "scenario-planning" category: "frameworks" agency_relevance: "high" - agency_context: "Agency revenue is inherently volatile — the feast-or-famine cycle is structural, not accidental. Scenario planning must address three critical scenarios for every agency: (1) Client loss scenario — what happens if the top client (or top two) leave? (2) Talent loss scenario — what happens if a key producer departs and takes client relationships? (3) Market shift scenario — what happens if a core service line is commoditized faster than expected? Financial scenarios should model at least three cases: base (current trajectory), growth (win a major account or enter a new vertical), and contraction (lose a major client or face a recession). Each scenario needs explicit triggers and pre-committed responses." + agency_context: "Agency revenue is inherently volatile — the feast-or-famine + cycle is structural, not accidental. Scenario planning must address three + critical scenarios for every agency: (1) Client loss scenario — what + happens if the top client (or top two) leave? (2) Talent loss scenario — + what happens if a key producer departs and takes client relationships? (3) + Market shift scenario — what happens if a core service line is + commoditized faster than expected? Financial scenarios should model at + least three cases: base (current trajectory), growth (win a major account + or enter a new vertical), and contraction (lose a major client or face a + recession). Each scenario needs explicit triggers and pre-committed + responses." agency_anti_patterns: - - "Planning only for growth scenarios. Agencies are optimistic by nature but vulnerable to downturns. A contraction scenario with a pre-committed cost-reduction plan preserves the firm when the inevitable downturn arrives." - - "Building scenarios that assume the same team is available. People are the production capacity in agencies — scenarios must account for attrition, hiring difficulty, and key-person risk." - - "Failing to scenario-plan cash flow separately from revenue. A $3M agency with $200K in receivables and a $100K monthly payroll can face a cash crisis even while 'growing.'" - agency_example: "A 20-person consultancy builds three scenarios for the next 12 months. Base: current trajectory, 10% revenue growth from existing clients plus modest new business. Growth: win a major government contract that would double headcount requirements, requiring rapid hiring and subcontractor engagement. Contraction: top client (28% of revenue) announces an in-house build, requiring immediate cost reduction and aggressive new business development. Each scenario has financial projections, talent implications, and a decision trigger that signals which scenario is materializing." - benchmark_references: ["client-concentration", "revenue", "bench-time", "overhead-ratio"] + - "Planning only for growth scenarios. Agencies are optimistic by nature + but vulnerable to downturns. A contraction scenario with a pre-committed + cost-reduction plan preserves the firm when the inevitable downturn + arrives." + - "Building scenarios that assume the same team is available. People are + the production capacity in agencies — scenarios must account for + attrition, hiring difficulty, and key-person risk." + - "Failing to scenario-plan cash flow separately from revenue. A $3M + agency with $200K in receivables and a $100K monthly payroll can face a + cash crisis even while 'growing.'" + agency_example: "A 20-person consultancy builds three scenarios for the next 12 + months. Base: current trajectory, 10% revenue growth from existing clients + plus modest new business. Growth: win a major government contract that + would double headcount requirements, requiring rapid hiring and + subcontractor engagement. Contraction: top client (28% of revenue) + announces an in-house build, requiring immediate cost reduction and + aggressive new business development. Each scenario has financial + projections, talent implications, and a decision trigger that signals + which scenario is materializing." + benchmark_references: [ "client-concentration", "revenue", "bench-time", "overhead-ratio" ] - skill: "eisenhower-matrix" category: "frameworks" agency_relevance: "high" - agency_context: "Agency founders and leaders face a relentless stream of competing demands — client emergencies, proposal deadlines, employee issues, billing disputes, and new business opportunities all compete for attention. The Eisenhower Matrix in agencies must specifically address the tension between billable work (Urgent and revenue-generating) and business-building work (Important but not Urgent — sales, thought leadership, process improvement, training). The most damaging agency pattern is the founder who is personally billable at high utilization, leaving zero time for business development, hiring, and strategic planning. This creates a ceiling on growth that is precisely equal to the founder's personal capacity." + agency_context: "Agency founders and leaders face a relentless stream of + competing demands — client emergencies, proposal deadlines, employee + issues, billing disputes, and new business opportunities all compete for + attention. The Eisenhower Matrix in agencies must specifically address the + tension between billable work (Urgent and revenue-generating) and + business-building work (Important but not Urgent — sales, thought + leadership, process improvement, training). The most damaging agency + pattern is the founder who is personally billable at high utilization, + leaving zero time for business development, hiring, and strategic + planning. This creates a ceiling on growth that is precisely equal to the + founder's personal capacity." agency_anti_patterns: - - "Treating every client request as Urgent/Important. Client requests feel urgent because the client is pressing, but most can be scheduled without damaging the relationship. Learning to say 'I can address this by Thursday' rather than 'I will drop everything now' is a survival skill." - - "Spending all time in billable delivery (Urgent/Important) and neglecting business development and systems-building (Not Urgent/Important). This guarantees the feast-or-famine cycle — when the current project ends, there is nothing in the pipeline." - - "Delegating business development because it is 'Not Urgent.' In agencies, the founder's personal involvement in business development and client relationships is often irreplaceable, at least until the firm is large enough to hire a dedicated BD lead." - agency_example: "An agency founder tracks time for two weeks and discovers that 75% is spent on billable client work (Urgent/Important), 15% on email and administrative tasks (Urgent/Not Important), and 10% on ad hoc emergencies. Zero time is spent on strategic work: no pipeline development, no process documentation, no staff development. The Eisenhower Matrix reveals that the founder must reduce billable utilization from 75% to 50%, delegate administrative tasks, and protect 15-20 hours per week for business development and firm-building — the Not Urgent/Important quadrant that determines whether the agency grows or stalls." - benchmark_references: ["utilization-rate", "pipeline-coverage-ratio", "revenue"] + - "Treating every client request as Urgent/Important. Client requests feel + urgent because the client is pressing, but most can be scheduled without + damaging the relationship. Learning to say 'I can address this by + Thursday' rather than 'I will drop everything now' is a survival skill." + - "Spending all time in billable delivery (Urgent/Important) and + neglecting business development and systems-building (Not + Urgent/Important). This guarantees the feast-or-famine cycle — when the + current project ends, there is nothing in the pipeline." + - "Delegating business development because it is 'Not Urgent.' In + agencies, the founder's personal involvement in business development and + client relationships is often irreplaceable, at least until the firm is + large enough to hire a dedicated BD lead." + agency_example: "An agency founder tracks time for two weeks and discovers that + 75% is spent on billable client work (Urgent/Important), 15% on email and + administrative tasks (Urgent/Not Important), and 10% on ad hoc + emergencies. Zero time is spent on strategic work: no pipeline + development, no process documentation, no staff development. The + Eisenhower Matrix reveals that the founder must reduce billable + utilization from 75% to 50%, delegate administrative tasks, and protect + 15-20 hours per week for business development and firm-building — the Not + Urgent/Important quadrant that determines whether the agency grows or + stalls." + benchmark_references: [ "utilization-rate", "pipeline-coverage-ratio", "revenue" ] - skill: "systems-thinking" category: "frameworks" agency_relevance: "high" - agency_context: "Agency businesses contain reinforcing feedback loops that create non-obvious outcomes. The talent-quality loop: better work attracts better clients, better clients provide better case studies, better case studies attract better talent, better talent produces better work. The utilization-burnout loop: high utilization generates revenue, but sustained high utilization causes burnout, burnout causes attrition, attrition requires emergency hiring and knowledge transfer, which reduces quality and increases costs. The feast-or-famine loop: busy periods consume all capacity for business development, no business development creates pipeline gaps, pipeline gaps create bench time, bench time pressures the team to take any available work, undifferentiated work leads to price competition, price competition thins margins, thin margins prevent hiring sales capacity. Systems thinking helps agency leaders identify which loop to intervene in and where." + agency_context: "Agency businesses contain reinforcing feedback loops that + create non-obvious outcomes. The talent-quality loop: better work attracts + better clients, better clients provide better case studies, better case + studies attract better talent, better talent produces better work. The + utilization-burnout loop: high utilization generates revenue, but + sustained high utilization causes burnout, burnout causes attrition, + attrition requires emergency hiring and knowledge transfer, which reduces + quality and increases costs. The feast-or-famine loop: busy periods + consume all capacity for business development, no business development + creates pipeline gaps, pipeline gaps create bench time, bench time + pressures the team to take any available work, undifferentiated work leads + to price competition, price competition thins margins, thin margins + prevent hiring sales capacity. Systems thinking helps agency leaders + identify which loop to intervene in and where." agency_anti_patterns: - - "Treating symptoms instead of systems. Hiring more people to address missed deadlines when the root cause is poor scoping. Running overtime to absorb scope creep when the root cause is weak contracts." - - "Ignoring the time delay in feedback loops. Cutting training and development today does not decrease quality tomorrow — it decreases quality in 6-12 months, making the cause invisible." - - "Optimizing utilization without modeling second-order effects. Pushing utilization from 68% to 78% generates short-term revenue but increases attrition, which costs far more to replace." - agency_example: "A growing agency notices that quality complaints are rising despite hiring experienced people. Systems analysis reveals a reinforcing loop: rapid growth requires fast hiring, fast hiring dilutes culture and methodology consistency, inconsistent methodology produces variable quality, variable quality generates client complaints, complaints consume senior staff time for firefighting, senior time spent firefighting reduces their availability for mentoring new hires, less mentoring perpetuates inconsistency. The intervention point is not quality control (a downstream symptom) but onboarding and mentoring (an upstream cause) — slowing hiring to match the firm's capacity to integrate new people." - benchmark_references: ["employee-retention-rate", "utilization-rate", "nps-client", "scope-creep-rate"] + - "Treating symptoms instead of systems. Hiring more people to address + missed deadlines when the root cause is poor scoping. Running overtime + to absorb scope creep when the root cause is weak contracts." + - "Ignoring the time delay in feedback loops. Cutting training and + development today does not decrease quality tomorrow — it decreases + quality in 6-12 months, making the cause invisible." + - "Optimizing utilization without modeling second-order effects. Pushing + utilization from 68% to 78% generates short-term revenue but increases + attrition, which costs far more to replace." + agency_example: "A growing agency notices that quality complaints are rising + despite hiring experienced people. Systems analysis reveals a reinforcing + loop: rapid growth requires fast hiring, fast hiring dilutes culture and + methodology consistency, inconsistent methodology produces variable + quality, variable quality generates client complaints, complaints consume + senior staff time for firefighting, senior time spent firefighting reduces + their availability for mentoring new hires, less mentoring perpetuates + inconsistency. The intervention point is not quality control (a downstream + symptom) but onboarding and mentoring (an upstream cause) — slowing hiring + to match the firm's capacity to integrate new people." + benchmark_references: + [ + "employee-retention-rate", + "utilization-rate", + "nps-client", + "scope-creep-rate" + ] - skill: "smart-goals" category: "frameworks" agency_relevance: "high" - agency_context: "SMART goals in agencies must account for the dual nature of the business: client delivery and firm building. Agency leaders need goals in both domains — a set of delivery goals (utilization, on-time delivery, client satisfaction) and a set of business-building goals (pipeline, win rate, thought leadership, talent development). The most common failure in agencies is setting revenue goals without corresponding capacity and operational goals. Hitting a $5M revenue target requires specific utilization rates, staffing levels, average project sizes, and win rates — each of which should be an explicit SMART goal." + agency_context: "SMART goals in agencies must account for the dual nature of the + business: client delivery and firm building. Agency leaders need goals in + both domains — a set of delivery goals (utilization, on-time delivery, + client satisfaction) and a set of business-building goals (pipeline, win + rate, thought leadership, talent development). The most common failure in + agencies is setting revenue goals without corresponding capacity and + operational goals. Hitting a $5M revenue target requires specific + utilization rates, staffing levels, average project sizes, and win rates — + each of which should be an explicit SMART goal." agency_anti_patterns: - - "Setting revenue goals without operational sub-goals. '$5M revenue this year' is incomplete without 'win 15 new projects at $100K average, maintain 90% client retention, and achieve 67% utilization.'" - - "Setting goals only at the firm level without cascading to individuals. Each partner, account manager, and project lead should have goals that connect to the firm-level objectives." - - "Ignoring the tension between utilization goals and business development goals. A 75% utilization target for a partner leaves only 25% for sales and management — often insufficient." - agency_example: "Instead of 'grow revenue 20%,' a consultancy sets Q2 SMART goals: (1) Win 5 new retainer clients at $8K+/month through focused outreach to the healthcare vertical (Specific, Measurable, Achievable given pipeline, Relevant to vertical strategy, Q2 Time-bound). (2) Increase billable utilization from 63% to 67% by reducing bench time through better resource planning (Specific, Measurable, achievable in 90 days, directly impacts margin). (3) Reduce average AR days from 52 to 40 by implementing automated invoicing and payment follow-up (Specific, Measurable, directly impacts cash flow, Time-bound to Q2). Each goal has a named owner and weekly measurement." - benchmark_references: ["revenue", "utilization-rate", "ar-days", "win-rate"] + - "Setting revenue goals without operational sub-goals. '$5M revenue this + year' is incomplete without 'win 15 new projects at $100K average, + maintain 90% client retention, and achieve 67% utilization.'" + - "Setting goals only at the firm level without cascading to individuals. + Each partner, account manager, and project lead should have goals that + connect to the firm-level objectives." + - "Ignoring the tension between utilization goals and business development + goals. A 75% utilization target for a partner leaves only 25% for sales + and management — often insufficient." + agency_example: "Instead of 'grow revenue 20%,' a consultancy sets Q2 SMART + goals: (1) Win 5 new retainer clients at $8K+/month through focused + outreach to the healthcare vertical (Specific, Measurable, Achievable + given pipeline, Relevant to vertical strategy, Q2 Time-bound). (2) + Increase billable utilization from 63% to 67% by reducing bench time + through better resource planning (Specific, Measurable, achievable in 90 + days, directly impacts margin). (3) Reduce average AR days from 52 to 40 + by implementing automated invoicing and payment follow-up (Specific, + Measurable, directly impacts cash flow, Time-bound to Q2). Each goal has a + named owner and weekly measurement." + benchmark_references: [ "revenue", "utilization-rate", "ar-days", "win-rate" ] - skill: "doblin-ten-types" category: "frameworks" agency_relevance: "high" - agency_context: "The Ten Types of Innovation framework is revealing for agencies because most agency innovation happens in a single type — Service (improving client deliverables) — while nine other innovation types are ignored. The most powerful agency innovations often come from Profit Model (shifting from hourly to value-based or productized pricing), Network (building freelancer ecosystems and strategic partnerships), Process (developing proprietary methodologies that standardize delivery), Channel (creating content platforms or communities that generate inbound leads), and Customer Engagement (building client advisory boards, communities of practice, or educational programs). Innovation in Service alone leads to an arms race of better deliverables at similar prices." + agency_context: "The Ten Types of Innovation framework is revealing for agencies + because most agency innovation happens in a single type — Service + (improving client deliverables) — while nine other innovation types are + ignored. The most powerful agency innovations often come from Profit Model + (shifting from hourly to value-based or productized pricing), Network + (building freelancer ecosystems and strategic partnerships), Process + (developing proprietary methodologies that standardize delivery), Channel + (creating content platforms or communities that generate inbound leads), + and Customer Engagement (building client advisory boards, communities of + practice, or educational programs). Innovation in Service alone leads to + an arms race of better deliverables at similar prices." agency_anti_patterns: - - "Defining innovation as 'better creative work' or 'more advanced technology.' These are Service innovations that every competitor also pursues. The most defensible innovations are in business model, process, and channel." - - "Ignoring Profit Model innovation. The shift from hourly to value-based or productized pricing is a Profit Model innovation that transforms agency economics more than any service improvement." - - "Dismissing Network innovation. An agency with a curated ecosystem of freelancers, technology partners, and complementary service providers can deliver more value than a larger firm with only internal resources." - agency_example: "A web development shop applies Doblin's framework and identifies that all of its innovation investment goes to Service (learning new technologies, improving code quality) and none to other types. Applying the framework, the agency pursues Profit Model innovation (a monthly subscription for ongoing website maintenance and optimization at a fixed fee), Channel innovation (a free website audit tool that generates qualified leads), and Process innovation (a proprietary discovery methodology that reduces project scoping from 2 weeks to 2 days). The combined innovations increase revenue per employee by 35% despite no change in the quality of the underlying development work." - benchmark_references: ["revenue-per-employee", "average-billable-rate", "win-rate"] + - "Defining innovation as 'better creative work' or 'more advanced + technology.' These are Service innovations that every competitor also + pursues. The most defensible innovations are in business model, process, + and channel." + - "Ignoring Profit Model innovation. The shift from hourly to value-based + or productized pricing is a Profit Model innovation that transforms + agency economics more than any service improvement." + - "Dismissing Network innovation. An agency with a curated ecosystem of + freelancers, technology partners, and complementary service providers + can deliver more value than a larger firm with only internal resources." + agency_example: "A web development shop applies Doblin's framework and + identifies that all of its innovation investment goes to Service (learning + new technologies, improving code quality) and none to other types. + Applying the framework, the agency pursues Profit Model innovation (a + monthly subscription for ongoing website maintenance and optimization at a + fixed fee), Channel innovation (a free website audit tool that generates + qualified leads), and Process innovation (a proprietary discovery + methodology that reduces project scoping from 2 weeks to 2 days). The + combined innovations increase revenue per employee by 35% despite no + change in the quality of the underlying development work." + benchmark_references: [ "revenue-per-employee", "average-billable-rate", "win-rate" ] - skill: "emotional-intelligence" category: "frameworks" agency_relevance: "high" - agency_context: "Emotional intelligence is a core professional competency in agencies — not a 'nice to have.' Agency professionals navigate three emotionally charged domains daily: client relationships (reading buyer sentiment, managing expectations, delivering bad news about budgets or timelines), team management (motivating creative professionals who are intrinsically driven, handling the stress of tight deadlines and demanding clients, retaining talent that has abundant alternatives), and business development (reading the room in pitches, building personal connections that differentiate the firm, handling rejection when proposals are declined). The emotional demands of agency work are higher than in most industries because the work is personal — a rejected design or a criticized strategy can feel like a personal attack." + agency_context: "Emotional intelligence is a core professional competency in + agencies — not a 'nice to have.' Agency professionals navigate three + emotionally charged domains daily: client relationships (reading buyer + sentiment, managing expectations, delivering bad news about budgets or + timelines), team management (motivating creative professionals who are + intrinsically driven, handling the stress of tight deadlines and demanding + clients, retaining talent that has abundant alternatives), and business + development (reading the room in pitches, building personal connections + that differentiate the firm, handling rejection when proposals are + declined). The emotional demands of agency work are higher than in most + industries because the work is personal — a rejected design or a + criticized strategy can feel like a personal attack." agency_anti_patterns: - - "Treating client feedback on creative work as objective critique. Creative professionals often internalize criticism of their work as criticism of themselves. Leaders must translate client feedback into actionable direction without transmitting the emotional charge." - - "Ignoring the emotional toll of client service. Agency burnout is not primarily about hours — it is about the emotional labor of managing demanding clients, absorbing scope creep, and maintaining enthusiasm under pressure." - - "Promoting the best individual contributors to management roles without assessing emotional intelligence. The best designer or developer is not necessarily the best people manager." - agency_example: "A creative director notices that a senior designer is delivering increasingly mediocre work after a difficult client engagement where three rounds of feedback essentially reversed the original creative direction. Rather than addressing the output (a symptom), the CD applies emotional intelligence: she acknowledges the designer's frustration, validates that the client process was demoralizing, discusses how to set creative boundaries in future engagements, and temporarily assigns the designer to an internal branding project where creative freedom restores motivation. The designer's output quality recovers within two weeks." - benchmark_references: ["enps", "employee-retention-rate", "nps-client"] + - "Treating client feedback on creative work as objective critique. + Creative professionals often internalize criticism of their work as + criticism of themselves. Leaders must translate client feedback into + actionable direction without transmitting the emotional charge." + - "Ignoring the emotional toll of client service. Agency burnout is not + primarily about hours — it is about the emotional labor of managing + demanding clients, absorbing scope creep, and maintaining enthusiasm + under pressure." + - "Promoting the best individual contributors to management roles without + assessing emotional intelligence. The best designer or developer is not + necessarily the best people manager." + agency_example: "A creative director notices that a senior designer is + delivering increasingly mediocre work after a difficult client engagement + where three rounds of feedback essentially reversed the original creative + direction. Rather than addressing the output (a symptom), the CD applies + emotional intelligence: she acknowledges the designer's frustration, + validates that the client process was demoralizing, discusses how to set + creative boundaries in future engagements, and temporarily assigns the + designer to an internal branding project where creative freedom restores + motivation. The designer's output quality recovers within two weeks." + benchmark_references: [ "enps", "employee-retention-rate", "nps-client" ] - skill: "covey-seven-habits" category: "frameworks" agency_relevance: "moderate" - agency_context: "The Seven Habits apply with particular force to agency founders navigating the transition from practitioner to business leader. 'Begin with the End in Mind' forces the question: is the goal a lifestyle business ($500K-$2M, high personal income, minimal staff), a scale agency ($5M-$20M, institutional clients, exit potential), or something else? Every operational decision flows from this choice. 'Put First Things First' maps directly to the Not Urgent/Important quadrant where business development and strategic planning live — the work most agency leaders neglect. 'Think Win-Win' is essential for long-term client relationships and talent retention. 'Sharpen the Saw' addresses the burnout epidemic in agency leadership, where 60-hour weeks and always-on client service erode judgment." + agency_context: "The Seven Habits apply with particular force to agency founders + navigating the transition from practitioner to business leader. 'Begin + with the End in Mind' forces the question: is the goal a lifestyle + business ($500K-$2M, high personal income, minimal staff), a scale agency + ($5M-$20M, institutional clients, exit potential), or something else? + Every operational decision flows from this choice. 'Put First Things + First' maps directly to the Not Urgent/Important quadrant where business + development and strategic planning live — the work most agency leaders + neglect. 'Think Win-Win' is essential for long-term client relationships + and talent retention. 'Sharpen the Saw' addresses the burnout epidemic in + agency leadership, where 60-hour weeks and always-on client service erode + judgment." agency_anti_patterns: - - "Running the agency without clarity on the end goal. An agency designed for lifestyle and an agency designed for scale require completely different staffing, pricing, and client strategies. Ambiguity between these goals creates strategic drift." - - "Neglecting 'Sharpen the Saw' because every hour not billed is seen as lost revenue. Agency leaders who never invest in their own development become the ceiling on their firm's capability." - agency_example: "An agency founder applies 'Begin with the End in Mind' and realizes he has been building a scale agency (hiring, pursuing large accounts, taking on debt) when his actual goal is a lifestyle consultancy (high personal income, flexibility, interesting work, no management headaches). This clarity triggers a strategic reversal: he reduces the team from 12 to 5, lets go of demanding enterprise clients, raises rates by 40%, and restructures as a boutique practice. Revenue drops from $2.5M to $1.5M, but personal income increases and work-life balance improves dramatically." - benchmark_references: ["ebitda-margin", "revenue-per-employee", "enps"] + - "Running the agency without clarity on the end goal. An agency designed + for lifestyle and an agency designed for scale require completely + different staffing, pricing, and client strategies. Ambiguity between + these goals creates strategic drift." + - "Neglecting 'Sharpen the Saw' because every hour not billed is seen as + lost revenue. Agency leaders who never invest in their own development + become the ceiling on their firm's capability." + agency_example: "An agency founder applies 'Begin with the End in Mind' and + realizes he has been building a scale agency (hiring, pursuing large + accounts, taking on debt) when his actual goal is a lifestyle consultancy + (high personal income, flexibility, interesting work, no management + headaches). This clarity triggers a strategic reversal: he reduces the + team from 12 to 5, lets go of demanding enterprise clients, raises rates + by 40%, and restructures as a boutique practice. Revenue drops from $2.5M + to $1.5M, but personal income increases and work-life balance improves + dramatically." + benchmark_references: [ "ebitda-margin", "revenue-per-employee", "enps" ] # ───────────────────────────────────────────── # NEGOTIATION (4 skills) @@ -269,46 +834,161 @@ skill_overlays: - skill: "competitive-negotiation" category: "negotiation" agency_relevance: "critical" - agency_context: "Competitive negotiation in agencies occurs in three high-stakes contexts: scope negotiation (the most frequent — clients requesting additional work within existing budgets), rate negotiation (clients pushing for lower rates or requesting discounts to retain the relationship), and contract negotiation (payment terms, liability caps, IP ownership, and exclusivity clauses). Scope negotiation is the most consequential because it directly determines project profitability — the agency that cannot hold scope boundaries watches margins evaporate project by project. Rate negotiation is complicated by the personal nature of agency services — reducing the rate feels like devaluing the people doing the work. Contract terms like IP ownership and non-competes can have long-term strategic implications that exceed the financial value of the individual deal." + agency_context: "Competitive negotiation in agencies occurs in three high-stakes + contexts: scope negotiation (the most frequent — clients requesting + additional work within existing budgets), rate negotiation (clients + pushing for lower rates or requesting discounts to retain the + relationship), and contract negotiation (payment terms, liability caps, IP + ownership, and exclusivity clauses). Scope negotiation is the most + consequential because it directly determines project profitability — the + agency that cannot hold scope boundaries watches margins evaporate project + by project. Rate negotiation is complicated by the personal nature of + agency services — reducing the rate feels like devaluing the people doing + the work. Contract terms like IP ownership and non-competes can have + long-term strategic implications that exceed the financial value of the + individual deal." agency_anti_patterns: - - "Discounting rates to retain a client without obtaining anything in return. Every discount should be exchanged for something: a longer commitment, a case study, a referral, or expanded scope." - - "Absorbing scope expansion without documentation. Informal scope expansion ('can you also just quickly do X?') is the primary margin killer in agencies. Every addition should be documented and either billed or explicitly traded for something." - - "Negotiating from the assumption that the client has all the power. Agencies often underestimate their leverage — switching costs for clients include knowledge transfer, relationship rebuilding, learning curves, and project disruption." - agency_example: "A client requests a 15% rate reduction at contract renewal, citing competitive alternatives. The agency prepares by quantifying the value delivered (three campaigns generating $4.2M in attributable revenue against $450K in fees), documenting the switching costs (estimated 3-month productivity loss during transition), and preparing a counter-proposal: maintaining rates but adding a performance bonus tied to campaign outcomes. The client accepts the counter-proposal because it demonstrates confidence in results and aligns incentives — the negotiation shifts from cost to value." - benchmark_references: ["average-billable-rate", "effective-billable-rate", "client-retention-rate"] + - "Discounting rates to retain a client without obtaining anything in + return. Every discount should be exchanged for something: a longer + commitment, a case study, a referral, or expanded scope." + - "Absorbing scope expansion without documentation. Informal scope + expansion ('can you also just quickly do X?') is the primary margin + killer in agencies. Every addition should be documented and either + billed or explicitly traded for something." + - "Negotiating from the assumption that the client has all the power. + Agencies often underestimate their leverage — switching costs for + clients include knowledge transfer, relationship rebuilding, learning + curves, and project disruption." + agency_example: "A client requests a 15% rate reduction at contract renewal, + citing competitive alternatives. The agency prepares by quantifying the + value delivered (three campaigns generating $4.2M in attributable revenue + against $450K in fees), documenting the switching costs (estimated 3-month + productivity loss during transition), and preparing a counter-proposal: + maintaining rates but adding a performance bonus tied to campaign + outcomes. The client accepts the counter-proposal because it demonstrates + confidence in results and aligns incentives — the negotiation shifts from + cost to value." + benchmark_references: + [ + "average-billable-rate", + "effective-billable-rate", + "client-retention-rate" + ] - skill: "cooperative-negotiation" category: "negotiation" agency_relevance: "critical" - agency_context: "Cooperative negotiation is the foundation of long-term agency-client relationships. Unlike transactional sales where the negotiation ends at signature, agency engagements involve continuous negotiation — about priorities, timelines, scope, and resources — throughout the relationship. The most successful agencies frame the engagement as a partnership where both parties invest in mutual success, rather than a vendor-client transaction where the agency delivers what is ordered. Cooperative negotiation also governs the most important internal negotiation in agencies: resource allocation across competing client demands. When three clients all need the senior designer this week, the allocation decision is a negotiation — and how it is handled determines which clients receive excellent service and which feel neglected." + agency_context: "Cooperative negotiation is the foundation of long-term + agency-client relationships. Unlike transactional sales where the + negotiation ends at signature, agency engagements involve continuous + negotiation — about priorities, timelines, scope, and resources — + throughout the relationship. The most successful agencies frame the + engagement as a partnership where both parties invest in mutual success, + rather than a vendor-client transaction where the agency delivers what is + ordered. Cooperative negotiation also governs the most important internal + negotiation in agencies: resource allocation across competing client + demands. When three clients all need the senior designer this week, the + allocation decision is a negotiation — and how it is handled determines + which clients receive excellent service and which feel neglected." agency_anti_patterns: - - "Agreeing to everything the client requests to preserve the relationship. Accommodation is not cooperation. True cooperative negotiation involves honest trade-offs: 'We can add this feature, but it will push the launch by two weeks. Is that trade-off acceptable?'" - - "Treating retainer renewals as rubber-stamp exercises. Renewal is an opportunity to renegotiate scope, rates, and terms based on demonstrated value. Agencies that passively renew at the same terms leave value on the table." - - "Failing to negotiate internally with the same rigor applied to client negotiations. Resource allocation, project sequencing, and priority-setting across the firm require explicit cooperative negotiation among partners and account leads." - agency_example: "An agency managing a $180K annual retainer uses cooperative negotiation at the annual review. Rather than simply renewing at the same terms, they present: value delivered (documented outcomes), scope evolution (how the work has grown beyond the original brief), and a restructured proposal — the retainer increases to $220K but includes a new service (quarterly competitive analysis) and an outcome-linked bonus. The client agrees because the agency has framed the increase as expanded value, not a price increase. Both parties gain: the agency increases revenue per client and the client receives additional strategic support." - benchmark_references: ["revenue-per-client", "client-retention-rate", "nps-client"] + - "Agreeing to everything the client requests to preserve the + relationship. Accommodation is not cooperation. True cooperative + negotiation involves honest trade-offs: 'We can add this feature, but it + will push the launch by two weeks. Is that trade-off acceptable?'" + - "Treating retainer renewals as rubber-stamp exercises. Renewal is an + opportunity to renegotiate scope, rates, and terms based on demonstrated + value. Agencies that passively renew at the same terms leave value on + the table." + - "Failing to negotiate internally with the same rigor applied to client + negotiations. Resource allocation, project sequencing, and + priority-setting across the firm require explicit cooperative + negotiation among partners and account leads." + agency_example: "An agency managing a $180K annual retainer uses cooperative + negotiation at the annual review. Rather than simply renewing at the same + terms, they present: value delivered (documented outcomes), scope + evolution (how the work has grown beyond the original brief), and a + restructured proposal — the retainer increases to $220K but includes a new + service (quarterly competitive analysis) and an outcome-linked bonus. The + client agrees because the agency has framed the increase as expanded + value, not a price increase. Both parties gain: the agency increases + revenue per client and the client receives additional strategic support." + benchmark_references: [ "revenue-per-client", "client-retention-rate", "nps-client" ] - skill: "delivering-the-deal" category: "negotiation" agency_relevance: "high" - agency_context: "Deal execution in agencies has unique characteristics: proposals compete against 2-5 other firms in a structured evaluation process; procurement departments at large clients apply standardized vendor management frameworks that strip out the personal relationship; SOW terms (liability, IP, indemnification) can stall deals for weeks; and the gap between verbal agreement and signed contract is where deals die — the client's enthusiasm cools, internal priorities shift, or a competitor makes a counter-offer. The skill of delivering the deal means: submitting proposals that are easy to approve (not elaborate documents that require committee review), having flexible SOW templates ready for rapid negotiation, maintaining momentum between verbal yes and signature, and building internal champions within the client organization who drive urgency." + agency_context: "Deal execution in agencies has unique characteristics: + proposals compete against 2-5 other firms in a structured evaluation + process; procurement departments at large clients apply standardized + vendor management frameworks that strip out the personal relationship; SOW + terms (liability, IP, indemnification) can stall deals for weeks; and the + gap between verbal agreement and signed contract is where deals die — the + client's enthusiasm cools, internal priorities shift, or a competitor + makes a counter-offer. The skill of delivering the deal means: submitting + proposals that are easy to approve (not elaborate documents that require + committee review), having flexible SOW templates ready for rapid + negotiation, maintaining momentum between verbal yes and signature, and + building internal champions within the client organization who drive + urgency." agency_anti_patterns: - - "Investing weeks in elaborate proposal documents that clients do not read. The proposal should be as short as the decision process allows. A 3-page proposal closed in 2 weeks beats a 30-page proposal that takes 3 months." - - "Losing momentum between verbal agreement and contract signature. Follow up within 24 hours of verbal acceptance with the SOW. Every day of delay increases the probability of deal collapse." - - "Treating the signed contract as the finish line. In agencies, the real deal begins at kickoff — the first 30 days of delivery either confirm the client's decision or plant the seeds of regret." - agency_example: "An agency creates a 'deal acceleration kit' containing: a modular SOW template (core terms pre-approved by legal, with fill-in sections for scope, timeline, and pricing), a one-page proposal format for engagements under $50K, three reference clients pre-briefed and ready for calls, and a standard project kickoff plan sent with the SOW to demonstrate readiness. The kit reduces average proposal-to-signature time from 35 days to 14 days, and the kickoff plan attached to the SOW increases close rate by 18% because it makes the agency feel prepared and easy to work with." - benchmark_references: ["win-rate", "sales-cycle-length", "average-project-value"] + - "Investing weeks in elaborate proposal documents that clients do not + read. The proposal should be as short as the decision process allows. A + 3-page proposal closed in 2 weeks beats a 30-page proposal that takes 3 + months." + - "Losing momentum between verbal agreement and contract signature. Follow + up within 24 hours of verbal acceptance with the SOW. Every day of delay + increases the probability of deal collapse." + - "Treating the signed contract as the finish line. In agencies, the real + deal begins at kickoff — the first 30 days of delivery either confirm + the client's decision or plant the seeds of regret." + agency_example: "An agency creates a 'deal acceleration kit' containing: a + modular SOW template (core terms pre-approved by legal, with fill-in + sections for scope, timeline, and pricing), a one-page proposal format for + engagements under $50K, three reference clients pre-briefed and ready for + calls, and a standard project kickoff plan sent with the SOW to + demonstrate readiness. The kit reduces average proposal-to-signature time + from 35 days to 14 days, and the kickoff plan attached to the SOW + increases close rate by 18% because it makes the agency feel prepared and + easy to work with." + benchmark_references: [ "win-rate", "sales-cycle-length", "average-project-value" ] - skill: "negotiation-mindset-and-self" category: "negotiation" agency_relevance: "high" - agency_context: "Agency founders and senior consultants negotiate constantly — with clients, prospects, subcontractors, employees, and partners — often from a position of perceived weakness. The perceived weakness is structural: the client has budget authority, the talent has other job offers, and the subcontractor has other clients. The negotiation mindset skill helps agency leaders recognize that their leverage is greater than they perceive: they possess specialized expertise, deep knowledge of the client's business, existing relationships and trust, and the capacity to solve problems the other party cannot solve alone. The most common mindset failure in agencies is believing that saying 'no' to a client will end the relationship, when in practice, the ability to set boundaries increases respect and trust." + agency_context: "Agency founders and senior consultants negotiate constantly — + with clients, prospects, subcontractors, employees, and partners — often + from a position of perceived weakness. The perceived weakness is + structural: the client has budget authority, the talent has other job + offers, and the subcontractor has other clients. The negotiation mindset + skill helps agency leaders recognize that their leverage is greater than + they perceive: they possess specialized expertise, deep knowledge of the + client's business, existing relationships and trust, and the capacity to + solve problems the other party cannot solve alone. The most common mindset + failure in agencies is believing that saying 'no' to a client will end the + relationship, when in practice, the ability to set boundaries increases + respect and trust." agency_anti_patterns: - - "Entering negotiations from a scarcity mindset. Agencies that believe every prospect is critical and every client is irreplaceable negotiate from desperation, which produces bad terms." - - "Confusing accommodation with service. Excellent client service does not mean accepting every demand. It means delivering outstanding results within clearly defined boundaries." - - "Avoiding negotiation by absorbing costs. Many agency founders would rather silently eat scope creep than have an uncomfortable conversation about additional fees. This is a mindset problem, not a negotiation technique problem." - agency_example: "A consultant has been absorbing an average of 20% additional scope on every project because she fears that raising the issue will damage client relationships. Mindset work reveals the core belief: 'If I push back on scope, the client will think I am not dedicated and will find someone else.' Reframing: 'Clients who value me will respect clear boundaries. Clients who expect unlimited free work are not clients I want.' After implementing boundary conversations on the next three projects, two clients respond positively (one even apologizes for past overreach), and one client terminates — which frees capacity for more profitable work." - benchmark_references: ["effective-billable-rate", "scope-creep-rate", "nps-client"] + - "Entering negotiations from a scarcity mindset. Agencies that believe + every prospect is critical and every client is irreplaceable negotiate + from desperation, which produces bad terms." + - "Confusing accommodation with service. Excellent client service does not + mean accepting every demand. It means delivering outstanding results + within clearly defined boundaries." + - "Avoiding negotiation by absorbing costs. Many agency founders would + rather silently eat scope creep than have an uncomfortable conversation + about additional fees. This is a mindset problem, not a negotiation + technique problem." + agency_example: "A consultant has been absorbing an average of 20% additional + scope on every project because she fears that raising the issue will + damage client relationships. Mindset work reveals the core belief: 'If I + push back on scope, the client will think I am not dedicated and will find + someone else.' Reframing: 'Clients who value me will respect clear + boundaries. Clients who expect unlimited free work are not clients I + want.' After implementing boundary conversations on the next three + projects, two clients respond positively (one even apologizes for past + overreach), and one client terminates — which frees capacity for more + profitable work." + benchmark_references: [ "effective-billable-rate", "scope-creep-rate", "nps-client" ] # ───────────────────────────────────────────── # LEADERSHIP (5 skills) @@ -317,68 +997,225 @@ skill_overlays: - skill: "delegation-and-empowerment" category: "leadership" agency_relevance: "critical" - agency_context: "Delegation is the defining leadership challenge in professional services because the founder IS the product initially. Clients hired the founder's expertise, judgment, and personal attention. Transitioning from doing the work to managing others who do the work requires delegating without diminishing quality — and convincing clients that the junior consultant or designer is a suitable replacement for the founder's personal involvement. The delegation journey in agencies has three phases: Phase 1, the founder does everything (solo consultant). Phase 2, the founder delegates execution but retains client relationships and quality control (small agency). Phase 3, the founder delegates client relationships to account managers and quality control to creative directors (scaled agency). Most agency founders get stuck between Phase 1 and Phase 2, creating a permanent ceiling on firm size." + agency_context: "Delegation is the defining leadership challenge in professional + services because the founder IS the product initially. Clients hired the + founder's expertise, judgment, and personal attention. Transitioning from + doing the work to managing others who do the work requires delegating + without diminishing quality — and convincing clients that the junior + consultant or designer is a suitable replacement for the founder's + personal involvement. The delegation journey in agencies has three phases: + Phase 1, the founder does everything (solo consultant). Phase 2, the + founder delegates execution but retains client relationships and quality + control (small agency). Phase 3, the founder delegates client + relationships to account managers and quality control to creative + directors (scaled agency). Most agency founders get stuck between Phase 1 + and Phase 2, creating a permanent ceiling on firm size." agency_anti_patterns: - - "Delegating tasks but not authority. Assigning junior staff to create the deliverable but then rewriting it entirely defeats the purpose and demoralizes the team." - - "Delegating client relationships too early. Clients hired the founder. Transitioning the relationship to an account manager requires a deliberate, gradual handoff — not an abrupt switch." - - "Refusing to delegate because 'no one can do it as well as I can.' This is often true in the short term but guarantees the firm cannot grow. The founder's job is to build the team's capability, not to protect their own indispensability." - agency_example: "A strategy consultant earning $500K annually from personal billings hits a growth ceiling — she cannot bill more than 1,800 hours per year. She begins delegating by hiring a senior associate who shadows her on three engagements, then runs a portion of the fourth engagement independently with the founder reviewing key deliverables. Within 12 months, the associate handles 60% of delivery independently. The founder's time shifts to business development and executive-level client advisory — higher-value work that generates $350K in personal billings plus $300K from the associate's work, growing firm revenue from $500K to $650K with a clear path to $1M." - benchmark_references: ["revenue-per-partner", "leverage-ratio", "revenue"] + - "Delegating tasks but not authority. Assigning junior staff to create + the deliverable but then rewriting it entirely defeats the purpose and + demoralizes the team." + - "Delegating client relationships too early. Clients hired the founder. + Transitioning the relationship to an account manager requires a + deliberate, gradual handoff — not an abrupt switch." + - "Refusing to delegate because 'no one can do it as well as I can.' This + is often true in the short term but guarantees the firm cannot grow. The + founder's job is to build the team's capability, not to protect their + own indispensability." + agency_example: "A strategy consultant earning $500K annually from personal + billings hits a growth ceiling — she cannot bill more than 1,800 hours per + year. She begins delegating by hiring a senior associate who shadows her + on three engagements, then runs a portion of the fourth engagement + independently with the founder reviewing key deliverables. Within 12 + months, the associate handles 60% of delivery independently. The founder's + time shifts to business development and executive-level client advisory — + higher-value work that generates $350K in personal billings plus $300K + from the associate's work, growing firm revenue from $500K to $650K with a + clear path to $1M." + benchmark_references: [ "revenue-per-partner", "leverage-ratio", "revenue" ] - skill: "leadership-pipeline" category: "frameworks" agency_relevance: "high" - agency_context: "The Leadership Pipeline is essential for agencies because the growth trajectory follows a predictable path: from individual contributor (billable consultant) to managing others (project/account manager) to managing managers (department/practice lead) to running the business (partner/principal). Each transition requires fundamentally different skills and a different relationship with billable work. The most common pipeline failure in agencies is promoting the best consultant to a management role without any transition support — they continue doing the consulting work themselves (because they are good at it and it generates revenue) while neglecting the management work (because it is new and uncomfortable). The result: an overburdened manager who does both jobs poorly." + agency_context: "The Leadership Pipeline is essential for agencies because the + growth trajectory follows a predictable path: from individual contributor + (billable consultant) to managing others (project/account manager) to + managing managers (department/practice lead) to running the business + (partner/principal). Each transition requires fundamentally different + skills and a different relationship with billable work. The most common + pipeline failure in agencies is promoting the best consultant to a + management role without any transition support — they continue doing the + consulting work themselves (because they are good at it and it generates + revenue) while neglecting the management work (because it is new and + uncomfortable). The result: an overburdened manager who does both jobs + poorly." agency_anti_patterns: - - "Promoting based on billing performance rather than leadership potential. The highest-billing consultant may be the worst manager — they succeed through individual excellence, not through developing others." - - "Expecting new managers to maintain their previous utilization rate. A new project manager or account lead needs at least 25-30% of their time for management activities. Reducing their billing target is a necessary investment." - - "Skipping the 'managing managers' level. Going directly from individual contributors to a single firm leader creates a bottleneck where all management flows through one person." - agency_example: "A 25-person agency promotes three senior consultants to practice leads without adjusting their utilization targets. Within six months, all three are working 55+ hour weeks — billing 40+ hours on client work and spending evenings on management tasks. Two burn out and one leaves. The agency redesigns the leadership pipeline: practice leads bill at 50% utilization (not 70%), receive management training, and are evaluated on team performance (utilization, quality, retention) rather than personal billing. The firm's delivery capacity and quality improve because the leaders are actually leading." - benchmark_references: ["employee-retention-rate", "leverage-ratio", "revenue-per-partner"] + - "Promoting based on billing performance rather than leadership + potential. The highest-billing consultant may be the worst manager — + they succeed through individual excellence, not through developing + others." + - "Expecting new managers to maintain their previous utilization rate. A + new project manager or account lead needs at least 25-30% of their time + for management activities. Reducing their billing target is a necessary + investment." + - "Skipping the 'managing managers' level. Going directly from individual + contributors to a single firm leader creates a bottleneck where all + management flows through one person." + agency_example: "A 25-person agency promotes three senior consultants to + practice leads without adjusting their utilization targets. Within six + months, all three are working 55+ hour weeks — billing 40+ hours on client + work and spending evenings on management tasks. Two burn out and one + leaves. The agency redesigns the leadership pipeline: practice leads bill + at 50% utilization (not 70%), receive management training, and are + evaluated on team performance (utilization, quality, retention) rather + than personal billing. The firm's delivery capacity and quality improve + because the leaders are actually leading." + benchmark_references: [ "employee-retention-rate", "leverage-ratio", "revenue-per-partner" ] - skill: "strategic-thinking-and-alignment" category: "leadership" agency_relevance: "high" - agency_context: "Strategic alignment in agencies is challenged by a structural tension: the short-term revenue imperative (take any work that pays) versus the long-term positioning imperative (specialize, differentiate, and decline work that does not fit). Most agencies default to the short-term imperative, accepting every client and every project type, which prevents the specialization that drives premium pricing. Strategic alignment requires the agency to define what it does, for whom, and — critically — what it will NOT do. This is harder in agencies than in product companies because declining a $50K project that is 'not our thing' feels like throwing money away, when in fact it frees capacity for higher-margin work that builds the firm's reputation in its chosen specialty." + agency_context: "Strategic alignment in agencies is challenged by a structural + tension: the short-term revenue imperative (take any work that pays) + versus the long-term positioning imperative (specialize, differentiate, + and decline work that does not fit). Most agencies default to the + short-term imperative, accepting every client and every project type, + which prevents the specialization that drives premium pricing. Strategic + alignment requires the agency to define what it does, for whom, and — + critically — what it will NOT do. This is harder in agencies than in + product companies because declining a $50K project that is 'not our thing' + feels like throwing money away, when in fact it frees capacity for + higher-margin work that builds the firm's reputation in its chosen + specialty." agency_anti_patterns: - - "Defining strategy as 'we do everything for everyone.' This is the absence of strategy, not a strategy. It guarantees competition on price." - - "Allowing individual partners to pursue their own client strategies without firm-level alignment. Autonomous partners build fiefdoms rather than a coherent firm." - - "Setting a strategic direction and then accepting every piece of off-strategy work because 'we need the revenue.' Strategy requires the discipline to say no — especially when saying no is financially painful." - agency_example: "A generalist digital agency adopts a vertical specialization strategy: healthcare marketing for mid-size hospital systems. The first year is painful — they decline $400K in non-healthcare work while healthcare revenue grows slowly to $250K. By year two, healthcare clients refer other healthcare organizations, the agency develops proprietary benchmarking data for the sector, and they can charge 30% more than generalist competitors because they understand the regulatory landscape and speak the client's language. Revenue exceeds the generalist baseline within 30 months, at significantly higher margins." - benchmark_references: ["average-billable-rate", "client-retention-rate", "win-rate", "revenue-per-client"] + - "Defining strategy as 'we do everything for everyone.' This is the + absence of strategy, not a strategy. It guarantees competition on + price." + - "Allowing individual partners to pursue their own client strategies + without firm-level alignment. Autonomous partners build fiefdoms rather + than a coherent firm." + - "Setting a strategic direction and then accepting every piece of + off-strategy work because 'we need the revenue.' Strategy requires the + discipline to say no — especially when saying no is financially + painful." + agency_example: "A generalist digital agency adopts a vertical specialization + strategy: healthcare marketing for mid-size hospital systems. The first + year is painful — they decline $400K in non-healthcare work while + healthcare revenue grows slowly to $250K. By year two, healthcare clients + refer other healthcare organizations, the agency develops proprietary + benchmarking data for the sector, and they can charge 30% more than + generalist competitors because they understand the regulatory landscape + and speak the client's language. Revenue exceeds the generalist baseline + within 30 months, at significantly higher margins." + benchmark_references: + [ + "average-billable-rate", + "client-retention-rate", + "win-rate", + "revenue-per-client" + ] - skill: "employee-engagement-retention" category: "leadership" agency_relevance: "high" - agency_context: "Retention in agencies is existential — when people leave, they take client relationships, institutional knowledge, and billable capacity with them. The worst outcome is when a departing employee takes clients to a new firm or starts a competing practice. Agency retention is driven by three factors that differ from product companies: (1) Quality of work — creative and strategic professionals leave when the work becomes repetitive or unchallenging. (2) Client relationships — staff who manage client relationships directly have more leverage and more reason to leave. (3) Growth trajectory — talented people leave when they see no path to partnership, ownership, or expanded responsibility." + agency_context: "Retention in agencies is existential — when people leave, they + take client relationships, institutional knowledge, and billable capacity + with them. The worst outcome is when a departing employee takes clients to + a new firm or starts a competing practice. Agency retention is driven by + three factors that differ from product companies: (1) Quality of work — + creative and strategic professionals leave when the work becomes + repetitive or unchallenging. (2) Client relationships — staff who manage + client relationships directly have more leverage and more reason to leave. + (3) Growth trajectory — talented people leave when they see no path to + partnership, ownership, or expanded responsibility." agency_anti_patterns: - - "Treating retention as a compensation problem when it is usually a work-quality problem. Talented agency professionals will accept modest compensation for exceptional work — they will not accept exceptional compensation for mediocre work." - - "Waiting until someone resigns to address retention. By then, the decision is made. Proactive retention requires quarterly career conversations with every key person." - - "Ignoring the client-relationship risk of attrition. When a senior account manager leaves, assess which clients are at risk and proactively strengthen those relationships through leadership engagement." - agency_example: "A consulting firm discovers through exit interviews that the top reason for departure is 'lack of growth opportunities.' The firm responds by creating three career tracks: a client track (account management to partner), a craft track (specialist to practice expert), and a management track (team lead to operations director). Each track has defined milestones, compensation bands, and development plans. A profit-sharing program at the senior level creates financial incentives to stay. Retention improves from 78% to 91% over 18 months." - benchmark_references: ["employee-retention-rate", "enps", "revenue-per-employee"] + - "Treating retention as a compensation problem when it is usually a + work-quality problem. Talented agency professionals will accept modest + compensation for exceptional work — they will not accept exceptional + compensation for mediocre work." + - "Waiting until someone resigns to address retention. By then, the + decision is made. Proactive retention requires quarterly career + conversations with every key person." + - "Ignoring the client-relationship risk of attrition. When a senior + account manager leaves, assess which clients are at risk and proactively + strengthen those relationships through leadership engagement." + agency_example: "A consulting firm discovers through exit interviews that the + top reason for departure is 'lack of growth opportunities.' The firm + responds by creating three career tracks: a client track (account + management to partner), a craft track (specialist to practice expert), and + a management track (team lead to operations director). Each track has + defined milestones, compensation bands, and development plans. A + profit-sharing program at the senior level creates financial incentives to + stay. Retention improves from 78% to 91% over 18 months." + benchmark_references: [ "employee-retention-rate", "enps", "revenue-per-employee" ] - skill: "focus-and-priority-management" category: "leadership" agency_relevance: "high" - agency_context: "Agency leaders are pulled in more directions simultaneously than leaders in most other business types. On any given day, a founder may need to: deliver on a client project, prepare a proposal for a new prospect, resolve a staffing conflict, chase an overdue invoice, conduct a performance review, and attend a networking event. The result is chronic context-switching that degrades the quality of all activities. Priority management in agencies requires explicit time blocking: designated days or half-days for client delivery, business development, management, and strategic thinking. The most impactful priority decision for agency leaders is how to split time between billable work and non-billable firm-building." + agency_context: "Agency leaders are pulled in more directions simultaneously + than leaders in most other business types. On any given day, a founder may + need to: deliver on a client project, prepare a proposal for a new + prospect, resolve a staffing conflict, chase an overdue invoice, conduct a + performance review, and attend a networking event. The result is chronic + context-switching that degrades the quality of all activities. Priority + management in agencies requires explicit time blocking: designated days or + half-days for client delivery, business development, management, and + strategic thinking. The most impactful priority decision for agency + leaders is how to split time between billable work and non-billable + firm-building." agency_anti_patterns: - - "Allowing the day to be driven by whoever is most urgent. Without explicit priorities, the loudest client and the most pressing emergency consume all available time." - - "Treating 'being busy' as evidence of productivity. High activity in agencies can mask low impact — billing 50 hours while the pipeline dries up is busy but not productive." - - "Failing to protect time for deep work. Agency deliverables — strategy documents, creative concepts, proposals — require uninterrupted focus. Constant interruptions produce mediocre output." - agency_example: "An agency founder implements a time-blocking system: Mondays for internal management (team meetings, pipeline review, financial review), Tuesday-Thursday for client delivery and client meetings, Fridays for business development (proposals, networking, thought leadership). The founder also establishes a 'minimum viable personal billability' target of 40% — enough to stay connected to client work without being consumed by it. Within three months, pipeline coverage improves from 1.5x to 3.5x because business development finally receives consistent attention." - benchmark_references: ["pipeline-coverage-ratio", "utilization-rate", "revenue"] + - "Allowing the day to be driven by whoever is most urgent. Without + explicit priorities, the loudest client and the most pressing emergency + consume all available time." + - "Treating 'being busy' as evidence of productivity. High activity in + agencies can mask low impact — billing 50 hours while the pipeline dries + up is busy but not productive." + - "Failing to protect time for deep work. Agency deliverables — strategy + documents, creative concepts, proposals — require uninterrupted focus. + Constant interruptions produce mediocre output." + agency_example: "An agency founder implements a time-blocking system: Mondays + for internal management (team meetings, pipeline review, financial + review), Tuesday-Thursday for client delivery and client meetings, Fridays + for business development (proposals, networking, thought leadership). The + founder also establishes a 'minimum viable personal billability' target of + 40% — enough to stay connected to client work without being consumed by + it. Within three months, pipeline coverage improves from 1.5x to 3.5x + because business development finally receives consistent attention." + benchmark_references: [ "pipeline-coverage-ratio", "utilization-rate", "revenue" ] - skill: "mentoring-and-coaching" category: "leadership" agency_relevance: "high" - agency_context: "Mentoring and coaching are the primary mechanisms by which agencies scale expertise. The founder's knowledge must transfer to the team — not through documentation alone but through structured mentoring relationships where junior staff observe, practice, receive feedback, and gradually assume more complex responsibilities. In agencies, mentoring also serves a business purpose: mentored employees are more engaged (reducing attrition), develop client-ready capabilities faster (reducing time to full billability), and become the next generation of account leads (enabling the founder to step back from delivery). The agency mentoring challenge is time — every hour spent mentoring is an hour not billed." + agency_context: "Mentoring and coaching are the primary mechanisms by which + agencies scale expertise. The founder's knowledge must transfer to the + team — not through documentation alone but through structured mentoring + relationships where junior staff observe, practice, receive feedback, and + gradually assume more complex responsibilities. In agencies, mentoring + also serves a business purpose: mentored employees are more engaged + (reducing attrition), develop client-ready capabilities faster (reducing + time to full billability), and become the next generation of account leads + (enabling the founder to step back from delivery). The agency mentoring + challenge is time — every hour spent mentoring is an hour not billed." agency_anti_patterns: - - "Treating mentoring as 'nice to have' rather than a core business activity. In agencies, mentoring IS the mechanism by which the firm scales. Without it, the firm is perpetually dependent on the founder's personal capacity." - - "Mentoring only on technical skills while ignoring client management skills. The most valuable agency skill — managing client relationships — is the hardest to teach and the most neglected in mentoring programs." - - "Expecting mentoring to happen organically. It does not. Structured mentoring requires explicit pairing, regular cadence, and accountability." - agency_example: "A design agency implements a structured mentoring program where each senior designer mentors two junior designers. The program includes: weekly 1:1 sessions (30 minutes), joint client presentations where the junior observes then gradually presents, and 'graduated responsibility' where the junior designer leads increasingly complex deliverables with decreasing oversight. After 12 months, three junior designers are independently managing client deliverables, freeing senior designers to focus on business development and creative direction. The firm's delivery capacity effectively doubles without proportional hiring." - benchmark_references: ["leverage-ratio", "employee-retention-rate", "revenue-per-employee"] + - "Treating mentoring as 'nice to have' rather than a core business + activity. In agencies, mentoring IS the mechanism by which the firm + scales. Without it, the firm is perpetually dependent on the founder's + personal capacity." + - "Mentoring only on technical skills while ignoring client management + skills. The most valuable agency skill — managing client relationships — + is the hardest to teach and the most neglected in mentoring programs." + - "Expecting mentoring to happen organically. It does not. Structured + mentoring requires explicit pairing, regular cadence, and + accountability." + agency_example: "A design agency implements a structured mentoring program where + each senior designer mentors two junior designers. The program includes: + weekly 1:1 sessions (30 minutes), joint client presentations where the + junior observes then gradually presents, and 'graduated responsibility' + where the junior designer leads increasingly complex deliverables with + decreasing oversight. After 12 months, three junior designers are + independently managing client deliverables, freeing senior designers to + focus on business development and creative direction. The firm's delivery + capacity effectively doubles without proportional hiring." + benchmark_references: [ "leverage-ratio", "employee-retention-rate", "revenue-per-employee" ] # ───────────────────────────────────────────── # GAME THEORY (2 skills) @@ -387,22 +1224,67 @@ skill_overlays: - skill: "prisoners-dilemma-and-cooperation" category: "game-theory" agency_relevance: "moderate" - agency_context: "The Prisoner's Dilemma manifests in agency economics through pricing dynamics and competitive pitching. When multiple agencies compete for a project and each must submit pricing independently, the temptation to undercut creates a race-to-the-bottom that destroys industry margins. The cooperative solution — agencies maintaining rate integrity even when competing — is unstable because the incentive to defect (discount to win) always exists. The same dynamic appears in the freelancer-agency relationship: agencies tempted to underpay freelancers to protect margins, while freelancers are tempted to go directly to clients and cut out the agency. Repeated-game theory suggests that agencies with long-term relationships (clients, freelancers, competitors) benefit from cooperation, while one-shot interactions invite defection." + agency_context: "The Prisoner's Dilemma manifests in agency economics through + pricing dynamics and competitive pitching. When multiple agencies compete + for a project and each must submit pricing independently, the temptation + to undercut creates a race-to-the-bottom that destroys industry margins. + The cooperative solution — agencies maintaining rate integrity even when + competing — is unstable because the incentive to defect (discount to win) + always exists. The same dynamic appears in the freelancer-agency + relationship: agencies tempted to underpay freelancers to protect margins, + while freelancers are tempted to go directly to clients and cut out the + agency. Repeated-game theory suggests that agencies with long-term + relationships (clients, freelancers, competitors) benefit from + cooperation, while one-shot interactions invite defection." agency_anti_patterns: - - "Always defecting (discounting) in competitive pitches. This trains the market to expect low prices and erodes margins industry-wide." - - "Treating competing agencies as pure adversaries. In mature markets, agencies frequently collaborate — subcontracting to each other, referring work that does not fit, and maintaining relationships that benefit everyone." - agency_example: "Two competing PR agencies in the same city initially undercut each other's pricing on every pitch. After years of this, both realize their margins have eroded to 8%. They reach an informal understanding: neither will quote below their published rate card. Instead, they compete on quality, relationships, and specialization. Both firms' margins recover to 15%+ within two years, and they occasionally refer work to each other when a client needs capabilities outside their specialty." - benchmark_references: ["average-billable-rate", "gross-margin", "win-rate"] + - "Always defecting (discounting) in competitive pitches. This trains the + market to expect low prices and erodes margins industry-wide." + - "Treating competing agencies as pure adversaries. In mature markets, + agencies frequently collaborate — subcontracting to each other, + referring work that does not fit, and maintaining relationships that + benefit everyone." + agency_example: "Two competing PR agencies in the same city initially undercut + each other's pricing on every pitch. After years of this, both realize + their margins have eroded to 8%. They reach an informal understanding: + neither will quote below their published rate card. Instead, they compete + on quality, relationships, and specialization. Both firms' margins recover + to 15%+ within two years, and they occasionally refer work to each other + when a client needs capabilities outside their specialty." + benchmark_references: [ "average-billable-rate", "gross-margin", "win-rate" ] - skill: "information-asymmetry" category: "game-theory" agency_relevance: "high" - agency_context: "Information asymmetry shapes every agency-client interaction. The agency typically knows more about the complexity of the work, the real cost of delivery, and the range of possible outcomes. The client typically knows more about their internal budget, their urgency, their alternatives, and their satisfaction with the agency's work. Agencies that exploit information asymmetry (overscoping work, padding timelines, obscuring costs) gain short-term margin at the cost of long-term trust. Agencies that proactively reduce information asymmetry (transparent time tracking, open-book pricing, honest complexity assessments) build the trust that sustains relationships and justifies premium pricing. The most powerful application: helping clients understand the true value of the agency's work by sharing relevant benchmarks and market data." + agency_context: "Information asymmetry shapes every agency-client interaction. + The agency typically knows more about the complexity of the work, the real + cost of delivery, and the range of possible outcomes. The client typically + knows more about their internal budget, their urgency, their alternatives, + and their satisfaction with the agency's work. Agencies that exploit + information asymmetry (overscoping work, padding timelines, obscuring + costs) gain short-term margin at the cost of long-term trust. Agencies + that proactively reduce information asymmetry (transparent time tracking, + open-book pricing, honest complexity assessments) build the trust that + sustains relationships and justifies premium pricing. The most powerful + application: helping clients understand the true value of the agency's + work by sharing relevant benchmarks and market data." agency_anti_patterns: - - "Exploiting asymmetry by obscuring what work actually costs or how long it actually takes. Clients who discover they have been overcharged never return." - - "Failing to leverage legitimate asymmetry. Agencies possess genuine expertise that clients lack — sharing this knowledge (through education, frameworks, and benchmarks) positions the agency as a trusted advisor rather than a vendor." - agency_example: "A web development agency adopts transparent project management — the client can see the time tracker, the project budget consumption, and the remaining scope in real time. Initially, the team fears this will lead to micromanagement and scope disputes. In practice, the transparency builds trust: clients see the real complexity of the work, understand why changes have cost implications, and feel confident they are getting fair value. Client retention increases from 72% to 89%, and the agency can charge higher rates because trust reduces the 'risk premium' clients apply to opaque vendors." - benchmark_references: ["effective-billable-rate", "nps-client", "client-retention-rate"] + - "Exploiting asymmetry by obscuring what work actually costs or how long + it actually takes. Clients who discover they have been overcharged never + return." + - "Failing to leverage legitimate asymmetry. Agencies possess genuine + expertise that clients lack — sharing this knowledge (through education, + frameworks, and benchmarks) positions the agency as a trusted advisor + rather than a vendor." + agency_example: "A web development agency adopts transparent project management + — the client can see the time tracker, the project budget consumption, and + the remaining scope in real time. Initially, the team fears this will lead + to micromanagement and scope disputes. In practice, the transparency + builds trust: clients see the real complexity of the work, understand why + changes have cost implications, and feel confident they are getting fair + value. Client retention increases from 72% to 89%, and the agency can + charge higher rates because trust reduces the 'risk premium' clients apply + to opaque vendors." + benchmark_references: [ "effective-billable-rate", "nps-client", "client-retention-rate" ] # ───────────────────────────────────────────── # PEOPLE (2 skills) @@ -411,23 +1293,66 @@ skill_overlays: - skill: "connecting-with-people" category: "people" agency_relevance: "high" - agency_context: "Connection is the primary sales channel for professional services. Agencies grow through relationships — referrals from satisfied clients, connections made at industry events, relationships with former colleagues who move to potential client organizations, and bonds formed through shared experiences and mutual interests. The depth and breadth of the founder's (and the team's) professional network directly determines the firm's growth ceiling. Unlike product companies where marketing can generate demand at scale, agencies rely on one-to-one relationships that require genuine connection — not transactional networking." + agency_context: "Connection is the primary sales channel for professional + services. Agencies grow through relationships — referrals from satisfied + clients, connections made at industry events, relationships with former + colleagues who move to potential client organizations, and bonds formed + through shared experiences and mutual interests. The depth and breadth of + the founder's (and the team's) professional network directly determines + the firm's growth ceiling. Unlike product companies where marketing can + generate demand at scale, agencies rely on one-to-one relationships that + require genuine connection — not transactional networking." agency_anti_patterns: - - "Networking with the sole intent of selling. People sense transactional intent and withdraw. The most productive agency networking is genuinely helpful — offering introductions, sharing insights, solving problems without expectation of return." - - "Limiting relationship-building to the founder. Every senior team member should be building relationships in their domain. The agency's network should be broader than any individual's." - agency_example: "An agency founder shifts from attending networking events (transactional, low conversion) to hosting a monthly dinner for 8-10 marketing leaders in her city. No pitch, no agenda — just honest conversation about challenges in the industry. Within a year, five dinner attendees have become clients, three have made referrals, and the founder has become a known connector in the local marketing community. The cost: $500/month in dinner expenses. The return: $400K in new business attributable to dinner connections." - benchmark_references: ["cost-per-lead", "pipeline-coverage-ratio", "win-rate"] + - "Networking with the sole intent of selling. People sense transactional + intent and withdraw. The most productive agency networking is genuinely + helpful — offering introductions, sharing insights, solving problems + without expectation of return." + - "Limiting relationship-building to the founder. Every senior team member + should be building relationships in their domain. The agency's network + should be broader than any individual's." + agency_example: "An agency founder shifts from attending networking events + (transactional, low conversion) to hosting a monthly dinner for 8-10 + marketing leaders in her city. No pitch, no agenda — just honest + conversation about challenges in the industry. Within a year, five dinner + attendees have become clients, three have made referrals, and the founder + has become a known connector in the local marketing community. The cost: + $500/month in dinner expenses. The return: $400K in new business + attributable to dinner connections." + benchmark_references: [ "cost-per-lead", "pipeline-coverage-ratio", "win-rate" ] - skill: "inspiring-and-retaining" category: "people" agency_relevance: "high" - agency_context: "Inspiring and retaining talent in agencies requires understanding what motivates agency professionals — and it is not primarily compensation. Agency professionals are typically driven by: the quality and variety of client work, the opportunity to develop expertise, autonomy in how they approach problems, recognition for creative and strategic contributions, and a sense of belonging to a team they respect. The retention equation in agencies is further complicated by the fact that every senior departure is a potential competitive threat — departing staff can take clients, start competing practices, or join clients directly, reducing the agency's relationship base." + agency_context: "Inspiring and retaining talent in agencies requires + understanding what motivates agency professionals — and it is not + primarily compensation. Agency professionals are typically driven by: the + quality and variety of client work, the opportunity to develop expertise, + autonomy in how they approach problems, recognition for creative and + strategic contributions, and a sense of belonging to a team they respect. + The retention equation in agencies is further complicated by the fact that + every senior departure is a potential competitive threat — departing staff + can take clients, start competing practices, or join clients directly, + reducing the agency's relationship base." agency_anti_patterns: - - "Attempting to retain through compensation alone when the underlying work is unsatisfying. A 20% raise does not compensate for repetitive work, difficult clients, and lack of growth." - - "Failing to give meaningful credit for contributions. In agencies where senior leaders present work that junior staff created, the junior staff feel invisible — and leave." - - "Not having honest conversations about career trajectories. Agencies without clear paths to partnership, ownership, or expanded responsibility lose ambitious people to firms that offer these paths." - agency_example: "A development agency losing senior developers to tech companies at higher salaries reframes its retention strategy. Instead of trying to match tech salaries (financially impossible), the agency emphasizes unique advantages: variety of projects (tech companies offer one product; the agency offers dozens), autonomy (developers choose their tech stack and approach for each project), impact visibility (developers see their work launched and used by real clients), and profit-sharing (a percentage of project margins distributed quarterly). Attrition among senior developers drops from 35% to 12% annually." - benchmark_references: ["employee-retention-rate", "enps", "revenue-per-employee"] + - "Attempting to retain through compensation alone when the underlying + work is unsatisfying. A 20% raise does not compensate for repetitive + work, difficult clients, and lack of growth." + - "Failing to give meaningful credit for contributions. In agencies where + senior leaders present work that junior staff created, the junior staff + feel invisible — and leave." + - "Not having honest conversations about career trajectories. Agencies + without clear paths to partnership, ownership, or expanded + responsibility lose ambitious people to firms that offer these paths." + agency_example: "A development agency losing senior developers to tech companies + at higher salaries reframes its retention strategy. Instead of trying to + match tech salaries (financially impossible), the agency emphasizes unique + advantages: variety of projects (tech companies offer one product; the + agency offers dozens), autonomy (developers choose their tech stack and + approach for each project), impact visibility (developers see their work + launched and used by real clients), and profit-sharing (a percentage of + project margins distributed quarterly). Attrition among senior developers + drops from 35% to 12% annually." + benchmark_references: [ "employee-retention-rate", "enps", "revenue-per-employee" ] # ───────────────────────────────────────────── # STORYTELLING (1 skill) @@ -436,12 +1361,34 @@ skill_overlays: - skill: "story-structure-and-arc" category: "storytelling" agency_relevance: "high" - agency_context: "Storytelling is the primary sales mechanism in professional services. Agencies sell through stories: case studies that demonstrate results, origin stories that establish credibility, client transformation narratives that make intangible expertise tangible, and vision stories that help prospects imagine a better future. The pitch process itself is a story arc — situation (the client's current challenge), complication (why the challenge is harder than it appears), resolution (the agency's approach), and proof (evidence from similar situations). Agencies that master storytelling convert at significantly higher rates than those that present capabilities, methodologies, and credentials without narrative structure." + agency_context: "Storytelling is the primary sales mechanism in professional + services. Agencies sell through stories: case studies that demonstrate + results, origin stories that establish credibility, client transformation + narratives that make intangible expertise tangible, and vision stories + that help prospects imagine a better future. The pitch process itself is a + story arc — situation (the client's current challenge), complication (why + the challenge is harder than it appears), resolution (the agency's + approach), and proof (evidence from similar situations). Agencies that + master storytelling convert at significantly higher rates than those that + present capabilities, methodologies, and credentials without narrative + structure." agency_anti_patterns: - - "Presenting case studies as fact sheets rather than stories. 'We redesigned the website and traffic increased 200%' is a fact. 'The client was losing market share to a digitally native competitor, and the outdated website was the most visible symptom of a deeper brand identity crisis' is the beginning of a story." - - "Telling only success stories. The most powerful agency narratives include honest moments of challenge, unexpected obstacles, and how the team adapted — this builds trust through vulnerability." - agency_example: "A consulting firm restructures its pitch process around story arc. Instead of opening with firm credentials (boring, self-oriented), they open with a story about a similar client facing the same challenge — the situation, the hidden complexity, the approach, and the measurable outcome. The credentials slide moves to the appendix. Win rate increases from 28% to 42% because prospects see themselves in the story and feel confident the agency understands their world." - benchmark_references: ["win-rate", "average-project-value"] + - "Presenting case studies as fact sheets rather than stories. 'We + redesigned the website and traffic increased 200%' is a fact. 'The + client was losing market share to a digitally native competitor, and the + outdated website was the most visible symptom of a deeper brand identity + crisis' is the beginning of a story." + - "Telling only success stories. The most powerful agency narratives + include honest moments of challenge, unexpected obstacles, and how the + team adapted — this builds trust through vulnerability." + agency_example: "A consulting firm restructures its pitch process around story + arc. Instead of opening with firm credentials (boring, self-oriented), + they open with a story about a similar client facing the same challenge — + the situation, the hidden complexity, the approach, and the measurable + outcome. The credentials slide moves to the appendix. Win rate increases + from 28% to 42% because prospects see themselves in the story and feel + confident the agency understands their world." + benchmark_references: [ "win-rate", "average-project-value" ] # ───────────────────────────────────────────── # THINKING & DECISIONS (2 skills) @@ -450,19 +1397,67 @@ skill_overlays: - skill: "defining-and-exploring-problems" category: "thinking" agency_relevance: "high" - agency_context: "The most valuable skill an agency can offer is problem definition — helping clients understand what their real problem is before jumping to solutions. Clients come to agencies with symptoms ('our website is outdated,' 'our brand feels tired,' 'we need a new CRM'). The agency's job is to diagnose the underlying problem, which is often different from the stated symptom. An outdated website may reflect a deeper positioning problem. A tired brand may reflect a product-market fit issue. A CRM request may reflect a sales process failure that no technology will solve. Agencies that excel at problem definition become trusted advisors; agencies that simply execute the client's stated brief become order-takers." + agency_context: "The most valuable skill an agency can offer is problem + definition — helping clients understand what their real problem is before + jumping to solutions. Clients come to agencies with symptoms ('our website + is outdated,' 'our brand feels tired,' 'we need a new CRM'). The agency's + job is to diagnose the underlying problem, which is often different from + the stated symptom. An outdated website may reflect a deeper positioning + problem. A tired brand may reflect a product-market fit issue. A CRM + request may reflect a sales process failure that no technology will solve. + Agencies that excel at problem definition become trusted advisors; + agencies that simply execute the client's stated brief become + order-takers." agency_anti_patterns: - - "Jumping to solutions because the client is impatient. Clients often want to skip diagnosis and go straight to 'fix it.' The agency must advocate for proper problem definition even when the client resists." - - "Defining the problem in terms of the agency's capabilities. A branding agency sees every problem as a branding problem. A web agency sees every problem as a website problem. The agency must diagnose honestly, even if the solution lies outside its services." - agency_example: "A client approaches a digital agency requesting a complete website redesign — a $120K project. During the discovery phase, the agency applies problem-definition rigor and discovers that the website's traffic is strong but conversion is abysmal. The real problem is not the design — it is the unclear value proposition and confusing pricing page. The agency recommends a $30K conversion optimization project instead of the $120K redesign. The client is initially surprised but grateful. The optimization project delivers a 3x conversion improvement, and the client becomes the agency's most vocal advocate — generating $350K in referral revenue over the next two years." - benchmark_references: ["nps-client", "client-retention-rate", "revenue-per-client"] + - "Jumping to solutions because the client is impatient. Clients often + want to skip diagnosis and go straight to 'fix it.' The agency must + advocate for proper problem definition even when the client resists." + - "Defining the problem in terms of the agency's capabilities. A branding + agency sees every problem as a branding problem. A web agency sees every + problem as a website problem. The agency must diagnose honestly, even if + the solution lies outside its services." + agency_example: "A client approaches a digital agency requesting a complete + website redesign — a $120K project. During the discovery phase, the agency + applies problem-definition rigor and discovers that the website's traffic + is strong but conversion is abysmal. The real problem is not the design — + it is the unclear value proposition and confusing pricing page. The agency + recommends a $30K conversion optimization project instead of the $120K + redesign. The client is initially surprised but grateful. The optimization + project delivers a 3x conversion improvement, and the client becomes the + agency's most vocal advocate — generating $350K in referral revenue over + the next two years." + benchmark_references: [ "nps-client", "client-retention-rate", "revenue-per-client" ] - skill: "evaluating-and-deciding" category: "thinking" agency_relevance: "moderate" - agency_context: "Agency leaders face a distinct class of decisions shaped by the people-as-product reality. The most consequential recurring decisions: which clients to pursue (the portfolio decision), which people to hire (the capability decision), which services to offer (the positioning decision), how to price (the value-capture decision), and when to grow versus when to consolidate (the timing decision). The decision-making challenge in agencies is that most decisions have both financial and relationship dimensions — declining a project may damage a client relationship, firing a low performer may affect team morale, raising prices may lose a client. Effective agency decision-making requires weighing these dimensions simultaneously." + agency_context: "Agency leaders face a distinct class of decisions shaped by the + people-as-product reality. The most consequential recurring decisions: + which clients to pursue (the portfolio decision), which people to hire + (the capability decision), which services to offer (the positioning + decision), how to price (the value-capture decision), and when to grow + versus when to consolidate (the timing decision). The decision-making + challenge in agencies is that most decisions have both financial and + relationship dimensions — declining a project may damage a client + relationship, firing a low performer may affect team morale, raising + prices may lose a client. Effective agency decision-making requires + weighing these dimensions simultaneously." agency_anti_patterns: - - "Making decisions based solely on financial analysis without considering relationship impact. The most profitable decision is not always the best decision if it damages a strategically important relationship." - - "Delaying personnel decisions because of the personal difficulty. Keeping a low-performing employee because the conversation is uncomfortable harms the team, the clients, and ultimately the individual." - agency_example: "An agency must decide whether to take on a large project from a demanding client with a reputation for scope creep and late payment. Financial analysis says yes — the project would fill bench capacity and generate $200K in revenue. Relationship analysis says caution — the team that would be assigned has already expressed frustration with difficult clients, and assigning them to another one risks attrition. The agency decides to accept the project but with structural protections: a detailed SOW with explicit change-order processes, milestone-based billing, and a project manager experienced with demanding clients. The decision weighs both dimensions." - benchmark_references: ["utilization-rate", "employee-retention-rate", "scope-creep-rate"] + - "Making decisions based solely on financial analysis without considering + relationship impact. The most profitable decision is not always the best + decision if it damages a strategically important relationship." + - "Delaying personnel decisions because of the personal difficulty. + Keeping a low-performing employee because the conversation is + uncomfortable harms the team, the clients, and ultimately the + individual." + agency_example: "An agency must decide whether to take on a large project from a + demanding client with a reputation for scope creep and late payment. + Financial analysis says yes — the project would fill bench capacity and + generate $200K in revenue. Relationship analysis says caution — the team + that would be assigned has already expressed frustration with difficult + clients, and assigning them to another one risks attrition. The agency + decides to accept the project but with structural protections: a detailed + SOW with explicit change-order processes, milestone-based billing, and a + project manager experienced with demanding clients. The decision weighs + both dimensions." + benchmark_references: [ "utilization-rate", "employee-retention-rate", "scope-creep-rate" ] diff --git a/.claude/industry-packs/fintech/fintech-benchmarks.yaml b/.claude/industry-packs/fintech/fintech-benchmarks.yaml index 5c9028d..d8a04c1 100644 --- a/.claude/industry-packs/fintech/fintech-benchmarks.yaml +++ b/.claude/industry-packs/fintech/fintech-benchmarks.yaml @@ -31,7 +31,9 @@ pack_metadata: sector: "fintech" display_name: "Fintech" version: "1.0.0" - description: "Benchmark data for fintech companies spanning payments, lending, neobanking, insurtech, wealthtech, crypto, embedded finance, and regtech — with regulatory compliance as a first-class dimension." + description: "Benchmark data for fintech companies spanning payments, lending, + neobanking, insurtech, wealthtech, crypto, embedded finance, and regtech — + with regulatory compliance as a first-class dimension." applicable_stages: - idea - validation @@ -59,67 +61,101 @@ benchmarks: - name: "Total Payment Volume (TPV)" id: "tpv" category: "growth" - definition: "The aggregate dollar value of all transactions processed through the platform in a given period. TPV is the top-line measure of scale for payments businesses — it represents the economic activity intermediated, not the revenue retained." + definition: "The aggregate dollar value of all transactions processed through + the platform in a given period. TPV is the top-line measure of scale for + payments businesses — it represents the economic activity intermediated, + not the revenue retained." formula: "SUM(transaction_value) over period" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $1M monthly TPV at 12 months post-launch" - signal: "Insufficient transaction velocity to sustain the business. Processing costs eat margins at low volume." + signal: "Insufficient transaction velocity to sustain the business. Processing + costs eat margins at low volume." below_average: value: "$1M-$10M monthly TPV at 12 months" - signal: "Early traction but not yet at the scale where unit economics improve. Interchange and processing cost negotiations remain unfavorable." + signal: "Early traction but not yet at the scale where unit economics improve. + Interchange and processing cost negotiations remain unfavorable." average: value: "$10M-$100M monthly TPV at 12 months" - signal: "Meaningful scale. Enough volume to negotiate improved interchange rates and demonstrate product-market fit to investors." + signal: "Meaningful scale. Enough volume to negotiate improved interchange rates + and demonstrate product-market fit to investors." good: value: "$100M-$1B monthly TPV at 12 months" - signal: "Strong volume. Unit economics improve materially at this scale through volume-based pricing tiers with card networks and processors." + signal: "Strong volume. Unit economics improve materially at this scale through + volume-based pricing tiers with card networks and processors." excellent: value: "> $1B monthly TPV at 12 months" - signal: "Exceptional scale. Rare at this stage — indicates viral adoption in a high-volume vertical or a major enterprise client onboarded." + signal: "Exceptional scale. Rare at this stage — indicates viral adoption in a + high-volume vertical or a major enterprise client onboarded." stage_notes: - seed: "TPV trajectory matters more than absolute level. Investors look for consistent week-over-week growth in transaction volume, not static snapshots." - series_a: "Series A payments companies typically process $50M-$500M annual TPV. The conversion from TPV to net revenue (take rate) is scrutinized heavily." - series_b_plus: "At Series B+, TPV growth rate must exceed 50% YoY. Investors shift focus from TPV to net revenue growth and margin expansion." + seed: "TPV trajectory matters more than absolute level. Investors look for + consistent week-over-week growth in transaction volume, not static + snapshots." + series_a: "Series A payments companies typically process $50M-$500M annual TPV. + The conversion from TPV to net revenue (take rate) is scrutinized + heavily." + series_b_plus: "At Series B+, TPV growth rate must exceed 50% YoY. Investors + shift focus from TPV to net revenue growth and margin expansion." data_sources: - source: "McKinsey Global Payments Report" - url: "https://www.mckinsey.com/industries/financial-services/our-insights/the-2023-mckinsey-global-payments-report" + url: "https://www.mckinsey.com/industries/financial-services/our-insights/the-2\ + 023-mckinsey-global-payments-report" year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["take-rate", "transaction-volume", "revenue-per-transaction"] - related_skills: ["balanced-scorecard", "business-model-canvas"] - caveats: "TPV can be inflated by pass-through transactions that generate minimal revenue. Always pair TPV with take rate to understand actual economics. High-TPV businesses with sub-10bps take rates face margin compression risk." + related_metrics: [ "take-rate", "transaction-volume", "revenue-per-transaction" ] + related_skills: [ "balanced-scorecard", "business-model-canvas" ] + caveats: "TPV can be inflated by pass-through transactions that generate minimal + revenue. Always pair TPV with take rate to understand actual economics. + High-TPV businesses with sub-10bps take rates face margin compression + risk." - name: "Take Rate / Interchange Revenue" id: "take-rate" category: "unit-economics" - definition: "The percentage of total payment volume retained as net revenue after interchange, assessments, and processor costs. This is the fintech equivalent of gross margin on transactions — it measures the platform's pricing power and value-add per dollar processed." + definition: "The percentage of total payment volume retained as net revenue + after interchange, assessments, and processor costs. This is the fintech + equivalent of gross margin on transactions — it measures the platform's + pricing power and value-add per dollar processed." formula: "Net Revenue / TPV x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 0.1% (10 bps)" - signal: "Commodity processing with no value-add. The business is a payment pass-through — vulnerable to disintermediation by Stripe, Adyen, or direct bank connections." + signal: "Commodity processing with no value-add. The business is a payment + pass-through — vulnerable to disintermediation by Stripe, Adyen, or + direct bank connections." below_average: value: "0.1-0.3% (10-30 bps)" - signal: "Low-margin payment facilitation. Sustainable only at extreme volume. Durbin Amendment caps debit interchange at ~22 cents + 5bps for large issuers." + signal: "Low-margin payment facilitation. Sustainable only at extreme volume. + Durbin Amendment caps debit interchange at ~22 cents + 5bps for large + issuers." average: value: "0.3-1.0% (30-100 bps)" - signal: "Standard payment facilitation with some value-add services (fraud prevention, underwriting, analytics). Stripe retains approximately 50-70bps after interchange." + signal: "Standard payment facilitation with some value-add services (fraud + prevention, underwriting, analytics). Stripe retains approximately + 50-70bps after interchange." good: value: "1.0-2.5% (100-250 bps)" - signal: "Significant value-add justifying premium pricing. Includes embedded services (lending, insurance, identity) bundled with payments." + signal: "Significant value-add justifying premium pricing. Includes embedded + services (lending, insurance, identity) bundled with payments." excellent: value: "> 2.5% (250+ bps)" - signal: "Platform economics with deep vertical integration. Possible through managed services, lending-on-volume, or regulated services where compliance creates pricing power." + signal: "Platform economics with deep vertical integration. Possible through + managed services, lending-on-volume, or regulated services where + compliance creates pricing power." stage_notes: - seed: "Take rate is a hypothesis at seed. Regulatory constraints (interchange caps under Durbin Amendment in US, IFR in EU) set hard ceilings on certain revenue lines." - series_a: "Take rate compression is the primary risk. Demonstrate the path to increasing take rate through value-add services, not just volume growth." - series_b_plus: "At scale, even 5bps of take rate improvement is material. Investors model take rate trajectory alongside TPV growth." + seed: "Take rate is a hypothesis at seed. Regulatory constraints (interchange + caps under Durbin Amendment in US, IFR in EU) set hard ceilings on + certain revenue lines." + series_a: "Take rate compression is the primary risk. Demonstrate the path to + increasing take rate through value-add services, not just volume + growth." + series_b_plus: "At scale, even 5bps of take rate improvement is material. + Investors model take rate trajectory alongside TPV growth." data_sources: - source: "Stripe Financial Reports" year: "2024" @@ -127,117 +163,183 @@ benchmarks: year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["tpv", "revenue-per-transaction", "gross-margin"] - related_skills: ["pricing-diagnosis", "porters-five-forces"] - caveats: "Take rate varies dramatically by vertical and payment method. Card-present transactions yield different interchange than card-not-present. Cross-border transactions carry higher interchange but also higher fraud risk. Regulatory caps (PSD2 IFR in Europe, Durbin in US) constrain take rates on regulated interchange." + related_metrics: [ "tpv", "revenue-per-transaction", "gross-margin" ] + related_skills: + - porters-five-forces + caveats: "Take rate varies dramatically by vertical and payment method. + Card-present transactions yield different interchange than + card-not-present. Cross-border transactions carry higher interchange but + also higher fraud risk. Regulatory caps (PSD2 IFR in Europe, Durbin in US) + constrain take rates on regulated interchange." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Transaction Volume" id: "transaction-volume" category: "growth" - definition: "The total number of discrete transactions processed in a given period, independent of dollar value. Transaction volume measures platform utilization and is the primary driver of variable costs (processing fees per transaction)." + definition: "The total number of discrete transactions processed in a given + period, independent of dollar value. Transaction volume measures platform + utilization and is the primary driver of variable costs (processing fees + per transaction)." formula: "COUNT(transactions) over period" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 10K monthly transactions at 12 months" - signal: "Insufficient scale for meaningful unit economics. Fixed infrastructure costs dominate variable transaction costs." + signal: "Insufficient scale for meaningful unit economics. Fixed infrastructure + costs dominate variable transaction costs." below_average: value: "10K-100K monthly transactions" - signal: "Early traction. Enough transactions to detect fraud patterns and optimize processing routes." + signal: "Early traction. Enough transactions to detect fraud patterns and + optimize processing routes." average: value: "100K-1M monthly transactions" - signal: "Operational scale. Justifies investment in proprietary fraud detection, transaction monitoring, and compliance automation." + signal: "Operational scale. Justifies investment in proprietary fraud detection, + transaction monitoring, and compliance automation." good: value: "1M-10M monthly transactions" - signal: "Strong scale. Volume-based pricing from networks and processors materially improves unit economics." + signal: "Strong scale. Volume-based pricing from networks and processors + materially improves unit economics." excellent: value: "> 10M monthly transactions" - signal: "Massive scale. Enables sophisticated data-driven products (credit scoring, personalization, predictive analytics) built on transaction data." + signal: "Massive scale. Enables sophisticated data-driven products (credit + scoring, personalization, predictive analytics) built on transaction + data." stage_notes: - seed: "Transaction count matters for demonstrating usage patterns. Quality of transactions (repeat users, consistent amounts) signals more than volume alone." - series_a: "Transaction growth rate and transactions per user are more meaningful than raw count. BSA/AML transaction monitoring requirements scale with volume." - series_b_plus: "At scale, transaction cost per unit should decline through volume discounts and processing optimization. Regulatory reporting obligations (CTR, SAR) increase with volume." + seed: "Transaction count matters for demonstrating usage patterns. Quality of + transactions (repeat users, consistent amounts) signals more than volume + alone." + series_a: "Transaction growth rate and transactions per user are more meaningful + than raw count. BSA/AML transaction monitoring requirements scale with + volume." + series_b_plus: "At scale, transaction cost per unit should decline through + volume discounts and processing optimization. Regulatory reporting + obligations (CTR, SAR) increase with volume." data_sources: - source: "Stripe Financial Reports" year: "2024" - source: "Plaid Developer Reports" year: "2024" - related_metrics: ["tpv", "revenue-per-transaction", "cost-per-transaction", "transactions-per-user"] - related_skills: ["balanced-scorecard", "systems-thinking"] - caveats: "Transaction volume without revenue context is a vanity metric. A million transactions at zero margin is worse than 100K transactions at healthy margin. Always pair with revenue per transaction and cost per transaction." + related_metrics: + [ + "tpv", + "revenue-per-transaction", + "cost-per-transaction", + "transactions-per-user" + ] + related_skills: [ "balanced-scorecard", "systems-thinking" ] + caveats: "Transaction volume without revenue context is a vanity metric. A + million transactions at zero margin is worse than 100K transactions at + healthy margin. Always pair with revenue per transaction and cost per + transaction." - name: "Revenue per Transaction" id: "revenue-per-transaction" category: "unit-economics" - definition: "The average net revenue captured per individual transaction after interchange, assessments, and direct processing costs. This metric measures the economic value of each transaction to the platform." + definition: "The average net revenue captured per individual transaction after + interchange, assessments, and direct processing costs. This metric + measures the economic value of each transaction to the platform." formula: "Net Revenue / Transaction Count" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $0.05 per transaction" - signal: "Micro-transaction economics that require extreme volume to sustain the business. Common in peer-to-peer payments and low-value card transactions." + signal: "Micro-transaction economics that require extreme volume to sustain the + business. Common in peer-to-peer payments and low-value card + transactions." below_average: value: "$0.05-$0.25 per transaction" - signal: "Low per-unit economics. Business viability depends on high frequency and volume. Cross-sell opportunities needed to increase lifetime value." + signal: "Low per-unit economics. Business viability depends on high frequency + and volume. Cross-sell opportunities needed to increase lifetime + value." average: value: "$0.25-$1.00 per transaction" - signal: "Sustainable per-transaction economics for payment facilitators. Enough margin per transaction to fund fraud prevention and customer support." + signal: "Sustainable per-transaction economics for payment facilitators. Enough + margin per transaction to fund fraud prevention and customer support." good: value: "$1.00-$5.00 per transaction" - signal: "Strong unit economics per transaction. Indicates value-add services or higher-value transaction types (B2B payments, cross-border, lending)." + signal: "Strong unit economics per transaction. Indicates value-add services or + higher-value transaction types (B2B payments, cross-border, lending)." excellent: value: "> $5.00 per transaction" - signal: "Premium transaction economics. Typical of embedded lending, cross-border B2B payments, or regulated financial services where compliance creates pricing power." + signal: "Premium transaction economics. Typical of embedded lending, + cross-border B2B payments, or regulated financial services where + compliance creates pricing power." stage_notes: - seed: "Revenue per transaction is a function of average transaction size and take rate. Model both variables independently." - series_a: "Demonstrate revenue per transaction stability or improvement over time. Declining revenue per transaction signals take rate compression or mix shift." - series_b_plus: "Revenue per transaction should increase as value-add services (fraud tools, analytics, lending) are layered on top of core payment processing." + seed: "Revenue per transaction is a function of average transaction size and + take rate. Model both variables independently." + series_a: "Demonstrate revenue per transaction stability or improvement over + time. Declining revenue per transaction signals take rate compression or + mix shift." + series_b_plus: "Revenue per transaction should increase as value-add services + (fraud tools, analytics, lending) are layered on top of core payment + processing." data_sources: - source: "Stripe Financial Reports" year: "2024" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["take-rate", "cost-per-transaction", "transaction-volume"] - related_skills: ["pricing-diagnosis", "four-ps-marketing"] - caveats: "Average revenue per transaction can be misleading when the transaction mix is bimodal — a platform processing both $5 consumer payments and $50K B2B invoices will show a meaningless average." + related_metrics: [ "take-rate", "cost-per-transaction", "transaction-volume" ] + related_skills: + - four-ps-marketing + caveats: "Average revenue per transaction can be misleading when the transaction + mix is bimodal — a platform processing both $5 consumer payments and $50K + B2B invoices will show a meaningless average." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Cost per Transaction" id: "cost-per-transaction" category: "unit-economics" - definition: "The total variable cost incurred to process a single transaction, including interchange fees, processor costs, fraud prevention, compliance screening (KYC/AML), and customer support allocation." - formula: "(Interchange + Assessment Fees + Processor Fees + Fraud Costs + Compliance Costs + Support Allocation) / Transaction Count" + definition: "The total variable cost incurred to process a single transaction, + including interchange fees, processor costs, fraud prevention, compliance + screening (KYC/AML), and customer support allocation." + formula: "(Interchange + Assessment Fees + Processor Fees + Fraud Costs + + Compliance Costs + Support Allocation) / Transaction Count" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $1.50 per transaction" - signal: "High per-transaction cost indicating inefficient processing, excessive manual compliance review, or high fraud losses." + signal: "High per-transaction cost indicating inefficient processing, excessive + manual compliance review, or high fraud losses." below_average: value: "$0.75-$1.50 per transaction" - signal: "Above-average costs, often driven by manual compliance processes or premium fraud prevention services." + signal: "Above-average costs, often driven by manual compliance processes or + premium fraud prevention services." average: value: "$0.25-$0.75 per transaction" - signal: "Standard processing costs for card-based payment facilitation. Interchange is the dominant component." + signal: "Standard processing costs for card-based payment facilitation. + Interchange is the dominant component." good: value: "$0.10-$0.25 per transaction" - signal: "Efficient processing with automated compliance and fraud systems. Volume-based interchange discounts contributing." + signal: "Efficient processing with automated compliance and fraud systems. + Volume-based interchange discounts contributing." excellent: value: "< $0.10 per transaction" - signal: "Highly efficient processing — typically ACH-based or direct bank transfer models that bypass card interchange entirely." + signal: "Highly efficient processing — typically ACH-based or direct bank + transfer models that bypass card interchange entirely." stage_notes: - seed: "Cost per transaction is high at low volume because fixed compliance and infrastructure costs are spread across few transactions." - series_a: "Demonstrate clear path to cost per transaction reduction through volume, automation, and processing route optimization." - series_b_plus: "Cost per transaction optimization is a primary margin lever. Every cent saved per transaction at high volume is material to EBITDA." + seed: "Cost per transaction is high at low volume because fixed compliance and + infrastructure costs are spread across few transactions." + series_a: "Demonstrate clear path to cost per transaction reduction through + volume, automation, and processing route optimization." + series_b_plus: "Cost per transaction optimization is a primary margin lever. + Every cent saved per transaction at high volume is material to EBITDA." data_sources: - source: "McKinsey Global Payments Report" year: "2023" - source: "Nilson Report" year: "2024" - related_metrics: ["revenue-per-transaction", "gross-margin", "fraud-loss-rate"] - related_skills: ["balanced-scorecard", "systems-thinking"] - caveats: "Cost per transaction must include compliance costs — many fintechs exclude KYC/AML screening costs from transaction COGS, understating true unit costs. Regulators expect full cost transparency." + related_metrics: [ "revenue-per-transaction", "gross-margin", "fraud-loss-rate" ] + related_skills: [ "balanced-scorecard", "systems-thinking" ] + caveats: "Cost per transaction must include compliance costs — many fintechs + exclude KYC/AML screening costs from transaction COGS, understating true + unit costs. Regulators expect full cost transparency." # ───────────────────────────────────────────── # CUSTOMER ACQUISITION & LIFECYCLE @@ -246,30 +348,49 @@ benchmarks: - name: "Customer Acquisition Cost" id: "cac" category: "unit-economics" - definition: "The fully loaded cost to acquire one new active customer, including marketing, sales, referral incentives, sign-up bonuses, and the cost of KYC/identity verification during onboarding. In fintech, CAC must include compliance-driven onboarding costs that do not exist in non-regulated businesses." - formula: "(Total Sales & Marketing Spend + KYC/Onboarding Costs + Sign-Up Incentives) / New Active Customers" + definition: "The fully loaded cost to acquire one new active customer, including + marketing, sales, referral incentives, sign-up bonuses, and the cost of + KYC/identity verification during onboarding. In fintech, CAC must include + compliance-driven onboarding costs that do not exist in non-regulated + businesses." + formula: "(Total Sales & Marketing Spend + KYC/Onboarding Costs + Sign-Up + Incentives) / New Active Customers" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $200 (consumer) / > $2,000 (SMB) / > $25,000 (enterprise)" - signal: "Acquisition cost exceeds first-year revenue for many customers. Growth is uneconomic without significant cross-sell or long customer lifetimes." + signal: "Acquisition cost exceeds first-year revenue for many customers. Growth + is uneconomic without significant cross-sell or long customer + lifetimes." below_average: - value: "$100-$200 (consumer) / $1,000-$2,000 (SMB) / $10,000-$25,000 (enterprise)" - signal: "High CAC driven by competitive acquisition environment, expensive KYC processes, or low organic adoption." + value: "$100-$200 (consumer) / $1,000-$2,000 (SMB) / $10,000-$25,000 + (enterprise)" + signal: "High CAC driven by competitive acquisition environment, expensive KYC + processes, or low organic adoption." average: value: "$30-$100 (consumer) / $500-$1,000 (SMB) / $5,000-$10,000 (enterprise)" - signal: "Standard acquisition costs for regulated financial services. KYC typically accounts for $5-$15 of consumer CAC." + signal: "Standard acquisition costs for regulated financial services. KYC + typically accounts for $5-$15 of consumer CAC." good: value: "$10-$30 (consumer) / $200-$500 (SMB) / $2,000-$5,000 (enterprise)" - signal: "Efficient acquisition through product-led growth, referrals, or embedded distribution. KYC automation reducing onboarding friction." + signal: "Efficient acquisition through product-led growth, referrals, or + embedded distribution. KYC automation reducing onboarding friction." excellent: value: "< $10 (consumer) / < $200 (SMB) / < $2,000 (enterprise)" - signal: "Viral or embedded acquisition. Common in neobanks with referral programs (Nubank achieved <$5 CAC in Brazil) or embedded finance with distribution partnerships." + signal: "Viral or embedded acquisition. Common in neobanks with referral + programs (Nubank achieved <$5 CAC in Brazil) or embedded finance with + distribution partnerships." stage_notes: - seed: "CAC is high and unstable at seed. Manual KYC processes inflate early costs. Focus on learning which channels yield compliant, active customers." - series_a: "CAC should be declining as KYC automation scales and channel efficiency improves. Segment CAC by channel and by customer quality (active vs. dormant)." - series_b_plus: "CAC efficiency is a primary value driver. Nubank's sub-$5 CAC was central to its IPO narrative. Demonstrate the relationship between CAC and LTV by cohort." + seed: "CAC is high and unstable at seed. Manual KYC processes inflate early + costs. Focus on learning which channels yield compliant, active + customers." + series_a: "CAC should be declining as KYC automation scales and channel + efficiency improves. Segment CAC by channel and by customer quality + (active vs. dormant)." + series_b_plus: "CAC efficiency is a primary value driver. Nubank's sub-$5 CAC + was central to its IPO narrative. Demonstrate the relationship between + CAC and LTV by cohort." data_sources: - source: "Nubank S-1 Filing" year: "2021" @@ -277,37 +398,56 @@ benchmarks: year: "2024" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["ltv", "kyc-conversion-rate", "kyc-cost-per-customer"] - related_skills: ["four-ps-marketing", "blue-ocean-strategy"] - caveats: "Fintech CAC must include KYC/identity verification costs — these are non-optional regulatory requirements that do not exist in unregulated businesses. Excluding them understates true acquisition cost and misleads unit economics calculations." + related_metrics: [ "ltv", "kyc-conversion-rate", "kyc-cost-per-customer" ] + related_skills: [ "four-ps-marketing", "blue-ocean-strategy" ] + caveats: "Fintech CAC must include KYC/identity verification costs — these are + non-optional regulatory requirements that do not exist in unregulated + businesses. Excluding them understates true acquisition cost and misleads + unit economics calculations." - name: "Customer Lifetime Value" id: "ltv" category: "unit-economics" - definition: "The total net revenue expected from a customer over the entire duration of their relationship with the platform, adjusted for gross margin and the cost of regulatory compliance associated with maintaining the account." - formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross Margin % x Average Customer Lifetime in months)" + definition: "The total net revenue expected from a customer over the entire + duration of their relationship with the platform, adjusted for gross + margin and the cost of regulatory compliance associated with maintaining + the account." + formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross + Margin % x Average Customer Lifetime in months)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "LTV:CAC ratio < 1.5x" - signal: "Customer economics are underwater. The business is destroying value with each new customer. Common when regulatory compliance costs are underestimated in the LTV calculation." + signal: "Customer economics are underwater. The business is destroying value + with each new customer. Common when regulatory compliance costs are + underestimated in the LTV calculation." below_average: value: "LTV:CAC ratio 1.5-3x" - signal: "Marginal economics. Insufficient margin of safety against regulatory cost increases, credit losses, or competitive fee compression." + signal: "Marginal economics. Insufficient margin of safety against regulatory + cost increases, credit losses, or competitive fee compression." average: value: "LTV:CAC ratio 3-5x" - signal: "Healthy unit economics. Standard range for venture-backed fintechs with established product-market fit." + signal: "Healthy unit economics. Standard range for venture-backed fintechs with + established product-market fit." good: value: "LTV:CAC ratio 5-8x" - signal: "Strong economics driven by high retention, effective cross-sell, and efficient acquisition. Nubank reported LTV:CAC above 5x at IPO." + signal: "Strong economics driven by high retention, effective cross-sell, and + efficient acquisition. Nubank reported LTV:CAC above 5x at IPO." excellent: value: "LTV:CAC ratio > 8x" - signal: "Exceptional economics. May indicate under-investment in growth — verify that the company is deploying capital aggressively enough." + signal: "Exceptional economics. May indicate under-investment in growth — verify + that the company is deploying capital aggressively enough." stage_notes: - seed: "LTV is largely theoretical at seed. Base it on comparable fintech cohort data and conservative assumptions about retention and cross-sell." - series_a: "LTV should be derived from at least 12 months of cohort data. Separate LTV by customer segment — consumer, SMB, and enterprise have radically different lifetimes." - series_b_plus: "Mature LTV models incorporate multiple revenue streams (payments, lending, deposits, insurance) and regulatory cost assumptions. SoFi's cross-sell from lending to banking demonstrated LTV uplift through product expansion." + seed: "LTV is largely theoretical at seed. Base it on comparable fintech cohort + data and conservative assumptions about retention and cross-sell." + series_a: "LTV should be derived from at least 12 months of cohort data. + Separate LTV by customer segment — consumer, SMB, and enterprise have + radically different lifetimes." + series_b_plus: "Mature LTV models incorporate multiple revenue streams + (payments, lending, deposits, insurance) and regulatory cost + assumptions. SoFi's cross-sell from lending to banking demonstrated LTV + uplift through product expansion." data_sources: - source: "Nubank S-1 Filing" year: "2021" @@ -315,9 +455,12 @@ benchmarks: year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["cac", "net-revenue-retention", "monthly-active-users"] - related_skills: ["balanced-scorecard", "net-promoter-score"] - caveats: "Fintech LTV calculations must account for regulatory compliance costs that compound over the customer lifetime — ongoing KYC refresh, transaction monitoring, and SAR filing costs. Omitting these overstates LTV by 10-20% in lending and payments." + related_metrics: [ "cac", "net-revenue-retention", "monthly-active-users" ] + related_skills: [ "balanced-scorecard", "net-promoter-score" ] + caveats: "Fintech LTV calculations must account for regulatory compliance costs + that compound over the customer lifetime — ongoing KYC refresh, + transaction monitoring, and SAR filing costs. Omitting these overstates + LTV by 10-20% in lending and payments." # ───────────────────────────────────────────── # CREDIT & RISK METRICS (Lending-Specific) @@ -326,30 +469,51 @@ benchmarks: - name: "Net Interest Margin" id: "net-interest-margin" category: "financial" - definition: "The difference between interest income earned on loans and the interest paid on deposits or borrowed funds, expressed as a percentage of average earning assets. NIM is the core profitability metric for lending and neobanking fintechs — it measures the spread the institution captures between its cost of funds and its lending yield." + definition: "The difference between interest income earned on loans and the + interest paid on deposits or borrowed funds, expressed as a percentage of + average earning assets. NIM is the core profitability metric for lending + and neobanking fintechs — it measures the spread the institution captures + between its cost of funds and its lending yield." formula: "(Interest Income - Interest Expense) / Average Earning Assets x 100" unit: "percentage" direction: "target-range" benchmarks: poor: value: "< 2.0%" - signal: "Margin too thin to cover operating costs and credit losses. The institution is pricing loans too competitively or paying too much for deposits/funding." + signal: "Margin too thin to cover operating costs and credit losses. The + institution is pricing loans too competitively or paying too much for + deposits/funding." below_average: value: "2.0-3.0%" - signal: "Narrow margin that leaves little room for credit losses or operating expenses. Typical of fintechs relying on warehouse lending facilities with high cost of capital." + signal: "Narrow margin that leaves little room for credit losses or operating + expenses. Typical of fintechs relying on warehouse lending facilities + with high cost of capital." average: value: "3.0-5.0%" - signal: "Standard range for digital lenders. FDIC-insured average NIM was approximately 3.3% in 2023. Fintech lenders without bank charters typically operate at higher NIM due to higher-risk lending." + signal: "Standard range for digital lenders. FDIC-insured average NIM was + approximately 3.3% in 2023. Fintech lenders without bank charters + typically operate at higher NIM due to higher-risk lending." good: value: "5.0-8.0%" - signal: "Strong NIM indicating either low cost of funds (bank charter, deposit funding) or higher-yield lending (subprime, small-dollar, BNPL). Must be evaluated against credit losses." + signal: "Strong NIM indicating either low cost of funds (bank charter, deposit + funding) or higher-yield lending (subprime, small-dollar, BNPL). Must + be evaluated against credit losses." excellent: value: "> 8.0%" - signal: "Very high NIM — typically indicative of high-risk lending (personal loans, payday alternative) where credit losses may consume the margin advantage. Requires careful risk-adjusted analysis." + signal: "Very high NIM — typically indicative of high-risk lending (personal + loans, payday alternative) where credit losses may consume the margin + advantage. Requires careful risk-adjusted analysis." stage_notes: - seed: "NIM is largely theoretical pre-launch. Model it based on target lending products, expected cost of capital, and regulatory capital requirements." - series_a: "Early NIM data from initial loan portfolio. Watch for NIM compression as the portfolio diversifies from early, hand-picked borrowers to broader origination." - series_b_plus: "Stable NIM demonstrates funding advantage and pricing discipline. A bank charter can transform NIM by replacing warehouse lending with deposit funding (Varo, SoFi). Capital adequacy requirements constrain leveraged NIM expansion." + seed: "NIM is largely theoretical pre-launch. Model it based on target lending + products, expected cost of capital, and regulatory capital + requirements." + series_a: "Early NIM data from initial loan portfolio. Watch for NIM compression + as the portfolio diversifies from early, hand-picked borrowers to + broader origination." + series_b_plus: "Stable NIM demonstrates funding advantage and pricing + discipline. A bank charter can transform NIM by replacing warehouse + lending with deposit funding (Varo, SoFi). Capital adequacy requirements + constrain leveraged NIM expansion." data_sources: - source: "FDIC Quarterly Banking Profile" year: "2023" @@ -357,81 +521,125 @@ benchmarks: year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["default-rate", "loan-origination-volume", "capital-adequacy-ratio"] - related_skills: ["scenario-planning", "balanced-scorecard"] - caveats: "NIM in isolation is dangerous. A high NIM paired with high default rates produces negative risk-adjusted returns. Always evaluate NIM net of expected credit losses. Regulatory scrutiny increases when NIM significantly exceeds industry averages — regulators may view it as a signal of predatory pricing." + related_metrics: [ "default-rate", "loan-origination-volume", "capital-adequacy-ratio" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "NIM in isolation is dangerous. A high NIM paired with high default + rates produces negative risk-adjusted returns. Always evaluate NIM net of + expected credit losses. Regulatory scrutiny increases when NIM + significantly exceeds industry averages — regulators may view it as a + signal of predatory pricing." - name: "Default Rate / Non-Performing Loans" id: "default-rate" category: "financial" - definition: "The percentage of the loan portfolio that has defaulted or is classified as non-performing (typically 90+ days past due). This is the primary credit risk metric for lending fintechs and directly determines whether net interest margin translates to actual profit." + definition: "The percentage of the loan portfolio that has defaulted or is + classified as non-performing (typically 90+ days past due). This is the + primary credit risk metric for lending fintechs and directly determines + whether net interest margin translates to actual profit." formula: "Non-Performing Loans / Total Outstanding Loan Portfolio x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 10%" - signal: "Credit underwriting is failing. At this default rate, most lending models are unprofitable regardless of NIM. Regulators will scrutinize underwriting standards." + signal: "Credit underwriting is failing. At this default rate, most lending + models are unprofitable regardless of NIM. Regulators will scrutinize + underwriting standards." below_average: value: "5-10%" - signal: "Elevated credit losses consuming most of the interest margin. Common in subprime or thin-file lending. Requires exceptional NIM to remain viable." + signal: "Elevated credit losses consuming most of the interest margin. Common in + subprime or thin-file lending. Requires exceptional NIM to remain + viable." average: value: "2-5%" - signal: "Standard range for fintech lenders. FDIC average non-performing loan ratio was approximately 0.7% for banks in 2023 — fintech lenders serving underbanked populations typically run higher." + signal: "Standard range for fintech lenders. FDIC average non-performing loan + ratio was approximately 0.7% for banks in 2023 — fintech lenders + serving underbanked populations typically run higher." good: value: "1-2%" - signal: "Strong credit quality. Indicates effective underwriting models, appropriate risk pricing, and disciplined portfolio management." + signal: "Strong credit quality. Indicates effective underwriting models, + appropriate risk pricing, and disciplined portfolio management." excellent: value: "< 1%" - signal: "Exceptional credit quality. Typical of prime lending, secured lending, or highly selective origination. Verify that the portfolio is not too conservative — under-lending limits growth." + signal: "Exceptional credit quality. Typical of prime lending, secured lending, + or highly selective origination. Verify that the portfolio is not too + conservative — under-lending limits growth." stage_notes: - seed: "Default rate is unknown pre-origination. Model based on FICO score distribution, loan type, and comparable fintech portfolios. Regulators require capital reserves against expected losses." - series_a: "Early vintage data emerges. Beware of vintage bias — default rates are artificially low in young portfolios because defaults take 6-18 months to materialize." - series_b_plus: "Mature vintage analysis across multiple economic conditions. Stress-test the portfolio against recession scenarios. Rating agencies and investors scrutinize default trends when evaluating securitization or warehouse facility renewal." + seed: "Default rate is unknown pre-origination. Model based on FICO score + distribution, loan type, and comparable fintech portfolios. Regulators + require capital reserves against expected losses." + series_a: "Early vintage data emerges. Beware of vintage bias — default rates + are artificially low in young portfolios because defaults take 6-18 + months to materialize." + series_b_plus: "Mature vintage analysis across multiple economic conditions. + Stress-test the portfolio against recession scenarios. Rating agencies + and investors scrutinize default trends when evaluating securitization + or warehouse facility renewal." data_sources: - source: "FDIC Quarterly Banking Profile" year: "2023" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["net-interest-margin", "loan-origination-volume", "capital-adequacy-ratio"] - related_skills: ["scenario-planning", "black-swans"] - caveats: "Default rates are lagging indicators — they reflect underwriting decisions made 6-18 months ago. Rising default rates in the current portfolio reflect past decisions that cannot be corrected. Early detection through delinquency tracking (30-day, 60-day) is essential. Regulatory agencies examine default rates as part of fair lending and UDAP/UDAAP enforcement." + related_metrics: [ "net-interest-margin", "loan-origination-volume", "capital-adequacy-ratio" ] + related_skills: [ "scenario-planning", "black-swans" ] + caveats: "Default rates are lagging indicators — they reflect underwriting + decisions made 6-18 months ago. Rising default rates in the current + portfolio reflect past decisions that cannot be corrected. Early detection + through delinquency tracking (30-day, 60-day) is essential. Regulatory + agencies examine default rates as part of fair lending and UDAP/UDAAP + enforcement." - name: "Loan Origination Volume" id: "loan-origination-volume" category: "growth" - definition: "The total dollar value of new loans originated in a given period. Measures the lending engine's throughput and growth velocity." + definition: "The total dollar value of new loans originated in a given period. + Measures the lending engine's throughput and growth velocity." formula: "SUM(new_loan_principal) over period" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $1M monthly originations at 12 months" - signal: "Insufficient volume to build statistically meaningful credit models or achieve economies of scale in servicing." + signal: "Insufficient volume to build statistically meaningful credit models or + achieve economies of scale in servicing." below_average: value: "$1M-$10M monthly originations" - signal: "Early-stage lending volume. Credit models are still learning. Warehouse facility utilization is low, increasing cost of capital." + signal: "Early-stage lending volume. Credit models are still learning. Warehouse + facility utilization is low, increasing cost of capital." average: value: "$10M-$50M monthly originations" - signal: "Meaningful scale. Portfolio data supports credit model refinement. Warehouse facility economics improve." + signal: "Meaningful scale. Portfolio data supports credit model refinement. + Warehouse facility economics improve." good: value: "$50M-$250M monthly originations" - signal: "Strong origination velocity. Sufficient volume for securitization. Multiple lending products may contribute." + signal: "Strong origination velocity. Sufficient volume for securitization. + Multiple lending products may contribute." excellent: value: "> $250M monthly originations" - signal: "Institutional scale. SoFi originated $4.4B in personal loans in Q4 2023 alone. At this scale, capital markets access and cost of funds become the primary competitive advantages." + signal: "Institutional scale. SoFi originated $4.4B in personal loans in Q4 2023 + alone. At this scale, capital markets access and cost of funds become + the primary competitive advantages." stage_notes: - seed: "Origination volume is minimal and manual. Regulatory licensing (state lending licenses, NMLS registration) must be in place before origination begins." - series_a: "Origination growth should exceed 100% YoY. Watch origination quality alongside quantity — loosening underwriting to grow volume is a path to credit losses." - series_b_plus: "Capital markets strategy (securitization, forward flow agreements, bank partnerships) becomes central to scaling origination. Regulatory capital requirements constrain balance-sheet lending." + seed: "Origination volume is minimal and manual. Regulatory licensing (state + lending licenses, NMLS registration) must be in place before origination + begins." + series_a: "Origination growth should exceed 100% YoY. Watch origination quality + alongside quantity — loosening underwriting to grow volume is a path to + credit losses." + series_b_plus: "Capital markets strategy (securitization, forward flow + agreements, bank partnerships) becomes central to scaling origination. + Regulatory capital requirements constrain balance-sheet lending." data_sources: - source: "SoFi Annual Reports" year: "2023" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["net-interest-margin", "default-rate", "capital-adequacy-ratio"] - related_skills: ["growth-share-matrix", "scenario-planning"] - caveats: "Origination volume can be vanity if credit quality is deteriorating. Rapid origination growth paired with loosening underwriting standards is the classic pattern preceding credit crises. Regulators scrutinize rapid portfolio growth as a leading indicator of risk." + related_metrics: [ "net-interest-margin", "default-rate", "capital-adequacy-ratio" ] + related_skills: [ "growth-share-matrix", "scenario-planning" ] + caveats: "Origination volume can be vanity if credit quality is deteriorating. + Rapid origination growth paired with loosening underwriting standards is + the classic pattern preceding credit crises. Regulators scrutinize rapid + portfolio growth as a leading indicator of risk." # ───────────────────────────────────────────── # FRAUD & SECURITY @@ -440,74 +648,112 @@ benchmarks: - name: "Fraud Rate" id: "fraud-rate" category: "efficiency" - definition: "The percentage of total transactions identified as fraudulent, whether caught before processing (attempted fraud) or resulting in actual losses (realized fraud). The combined metric measures the overall fraud exposure of the platform." + definition: "The percentage of total transactions identified as fraudulent, + whether caught before processing (attempted fraud) or resulting in actual + losses (realized fraud). The combined metric measures the overall fraud + exposure of the platform." formula: "(Fraudulent Transactions / Total Transactions) x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 1.0% of transactions" - signal: "Fraud exposure is dangerously high. Card network thresholds (Visa, Mastercard) for excessive fraud typically trigger fines or program termination at rates above 1%." + signal: "Fraud exposure is dangerously high. Card network thresholds (Visa, + Mastercard) for excessive fraud typically trigger fines or program + termination at rates above 1%." below_average: value: "0.5-1.0%" - signal: "Elevated fraud requiring immediate investment in detection and prevention. Approaching card network monitoring thresholds." + signal: "Elevated fraud requiring immediate investment in detection and + prevention. Approaching card network monitoring thresholds." average: value: "0.1-0.5%" - signal: "Standard fraud exposure for card-not-present transactions. Industry average for e-commerce is approximately 0.1% of transactions (Nilson Report 2023)." + signal: "Standard fraud exposure for card-not-present transactions. Industry + average for e-commerce is approximately 0.1% of transactions (Nilson + Report 2023)." good: value: "0.05-0.1%" - signal: "Below-average fraud rate indicating effective detection systems and robust identity verification." + signal: "Below-average fraud rate indicating effective detection systems and + robust identity verification." excellent: value: "< 0.05%" - signal: "Best-in-class fraud prevention. Typically requires ML-based real-time detection, multi-factor authentication, and sophisticated device fingerprinting." + signal: "Best-in-class fraud prevention. Typically requires ML-based real-time + detection, multi-factor authentication, and sophisticated device + fingerprinting." stage_notes: - seed: "Fraud rate data is limited. Implement basic fraud rules and 3D Secure. Budget for fraud losses as a cost of learning." - series_a: "Fraud detection must be semi-automated. Manual review at scale is uneconomic. Card networks impose monitoring programs above specific thresholds." - series_b_plus: "Proprietary fraud models trained on transaction data become a competitive moat. Low fraud rate enables lower interchange and better network relationships. PCI-DSS compliance is mandatory." + seed: "Fraud rate data is limited. Implement basic fraud rules and 3D Secure. + Budget for fraud losses as a cost of learning." + series_a: "Fraud detection must be semi-automated. Manual review at scale is + uneconomic. Card networks impose monitoring programs above specific + thresholds." + series_b_plus: "Proprietary fraud models trained on transaction data become a + competitive moat. Low fraud rate enables lower interchange and better + network relationships. PCI-DSS compliance is mandatory." data_sources: - source: "Nilson Report — Card Fraud Worldwide" year: "2023" - source: "Stripe Radar benchmarks" year: "2024" - related_metrics: ["fraud-loss-rate", "cost-per-transaction"] - related_skills: ["systems-thinking", "scenario-planning"] - caveats: "Fraud rate can be artificially lowered by rejecting legitimate transactions (false positives). An aggressive fraud filter that blocks 5% of legitimate transactions to achieve a low fraud rate destroys more revenue than the fraud it prevents. Track false positive rate alongside fraud rate." + related_metrics: [ "fraud-loss-rate", "cost-per-transaction" ] + related_skills: [ "systems-thinking", "scenario-planning" ] + caveats: "Fraud rate can be artificially lowered by rejecting legitimate + transactions (false positives). An aggressive fraud filter that blocks 5% + of legitimate transactions to achieve a low fraud rate destroys more + revenue than the fraud it prevents. Track false positive rate alongside + fraud rate." - name: "Fraud Loss Rate" id: "fraud-loss-rate" category: "financial" - definition: "The actual dollar losses from fraud as a percentage of total payment volume. Unlike fraud rate (which counts incidents), fraud loss rate measures the financial impact — the money that could not be recovered after fraudulent transactions were processed." + definition: "The actual dollar losses from fraud as a percentage of total + payment volume. Unlike fraud rate (which counts incidents), fraud loss + rate measures the financial impact — the money that could not be recovered + after fraudulent transactions were processed." formula: "(Gross Fraud Losses - Recoveries) / TPV x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 0.5% of TPV" - signal: "Fraud losses are consuming a significant portion of gross revenue. At a 1% take rate, 0.5% fraud losses represent half of all revenue." + signal: "Fraud losses are consuming a significant portion of gross revenue. At a + 1% take rate, 0.5% fraud losses represent half of all revenue." below_average: value: "0.1-0.5% of TPV" - signal: "Elevated losses that materially impact profitability. Common in high-risk verticals (gambling, crypto, cross-border) without sophisticated detection." + signal: "Elevated losses that materially impact profitability. Common in + high-risk verticals (gambling, crypto, cross-border) without + sophisticated detection." average: value: "0.05-0.1% of TPV" - signal: "Standard fraud losses for card-not-present payment processors. Global card fraud losses averaged approximately 6.8 cents per $100 (6.8bps) in 2022." + signal: "Standard fraud losses for card-not-present payment processors. Global + card fraud losses averaged approximately 6.8 cents per $100 (6.8bps) + in 2022." good: value: "0.02-0.05% of TPV" - signal: "Below-average fraud losses indicating effective prevention, rapid detection, and strong recovery processes." + signal: "Below-average fraud losses indicating effective prevention, rapid + detection, and strong recovery processes." excellent: value: "< 0.02% of TPV" - signal: "Minimal fraud losses. Requires sophisticated ML-based detection, strong identity verification, and effective chargeback management." + signal: "Minimal fraud losses. Requires sophisticated ML-based detection, strong + identity verification, and effective chargeback management." stage_notes: - seed: "Budget 20-50bps of TPV for fraud losses in early operations. Fraud patterns are unpredictable before the platform has enough data to train models." - series_a: "Fraud loss trajectory matters more than current level. Demonstrate declining fraud losses per dollar processed as detection improves." - series_b_plus: "Fraud loss rate is a key due diligence item for investors and banking partners. Card networks and regulators impose program requirements when losses exceed thresholds." + seed: "Budget 20-50bps of TPV for fraud losses in early operations. Fraud + patterns are unpredictable before the platform has enough data to train + models." + series_a: "Fraud loss trajectory matters more than current level. Demonstrate + declining fraud losses per dollar processed as detection improves." + series_b_plus: "Fraud loss rate is a key due diligence item for investors and + banking partners. Card networks and regulators impose program + requirements when losses exceed thresholds." data_sources: - source: "Nilson Report — Card Fraud Worldwide" year: "2023" - source: "McKinsey Global Payments Report" year: "2023" - related_metrics: ["fraud-rate", "take-rate", "gross-margin"] - related_skills: ["balanced-scorecard", "black-swans"] - caveats: "Fraud losses are often under-reported because they are netted against reserves or absorbed into general COGS. Transparent fraud loss reporting is a regulatory requirement under BSA/AML and is increasingly expected by banking partners and card networks." + related_metrics: [ "fraud-rate", "take-rate", "gross-margin" ] + related_skills: [ "balanced-scorecard", "black-swans" ] + caveats: "Fraud losses are often under-reported because they are netted against + reserves or absorbed into general COGS. Transparent fraud loss reporting + is a regulatory requirement under BSA/AML and is increasingly expected by + banking partners and card networks." # ───────────────────────────────────────────── # KYC & COMPLIANCE @@ -516,146 +762,239 @@ benchmarks: - name: "KYC/Onboarding Conversion Rate" id: "kyc-conversion-rate" category: "efficiency" - definition: "The percentage of customers who begin the onboarding/identity verification process and successfully complete it to become active users. This metric measures the friction that regulatory-mandated KYC imposes on customer acquisition — a cost unique to regulated financial services." + definition: "The percentage of customers who begin the onboarding/identity + verification process and successfully complete it to become active users. + This metric measures the friction that regulatory-mandated KYC imposes on + customer acquisition — a cost unique to regulated financial services." formula: "(Customers who completed KYC / Customers who initiated KYC) x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 50%" - signal: "Half of prospective customers abandon onboarding. The KYC process is too lengthy, too confusing, or rejects too many legitimate applicants. Each abandoned application represents wasted CAC." + signal: "Half of prospective customers abandon onboarding. The KYC process is + too lengthy, too confusing, or rejects too many legitimate applicants. + Each abandoned application represents wasted CAC." below_average: value: "50-65%" - signal: "Significant drop-off driven by excessive documentation requirements, slow verification, or poor mobile UX during identity capture." + signal: "Significant drop-off driven by excessive documentation requirements, + slow verification, or poor mobile UX during identity capture." average: value: "65-80%" - signal: "Standard conversion for regulated fintech onboarding. Industry average for digital-first onboarding with identity verification is approximately 70% (Plaid, 2023)." + signal: "Standard conversion for regulated fintech onboarding. Industry average + for digital-first onboarding with identity verification is + approximately 70% (Plaid, 2023)." good: value: "80-90%" - signal: "Strong onboarding conversion. Indicates streamlined KYC with real-time verification, OCR document capture, and progressive disclosure of requirements." + signal: "Strong onboarding conversion. Indicates streamlined KYC with real-time + verification, OCR document capture, and progressive disclosure of + requirements." excellent: value: "> 90%" - signal: "Exceptional conversion. Possible with instant verification (Plaid Identity, Jumio), simplified CDD for low-risk products, or embedded onboarding within an existing trusted platform." + signal: "Exceptional conversion. Possible with instant verification (Plaid + Identity, Jumio), simplified CDD for low-risk products, or embedded + onboarding within an existing trusted platform." stage_notes: - seed: "KYC conversion is often manually managed and low. Every point of conversion improvement directly reduces effective CAC." - series_a: "Automated KYC (OCR, database verification, liveness detection) should bring conversion above 70%. Track drop-off by step to identify specific friction points." - series_b_plus: "KYC conversion optimization is a continuous process. Regulatory requirements evolve — CDD requirements under BSA/AML and EU AMLD6 may add new verification steps that re-introduce friction." + seed: "KYC conversion is often manually managed and low. Every point of + conversion improvement directly reduces effective CAC." + series_a: "Automated KYC (OCR, database verification, liveness detection) should + bring conversion above 70%. Track drop-off by step to identify specific + friction points." + series_b_plus: "KYC conversion optimization is a continuous process. Regulatory + requirements evolve — CDD requirements under BSA/AML and EU AMLD6 may + add new verification steps that re-introduce friction." data_sources: - source: "Plaid Developer Reports" year: "2023" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["cac", "kyc-cost-per-customer", "monthly-active-users"] - related_skills: ["systems-thinking", "product-life-cycle"] - caveats: "KYC conversion cannot be optimized at the expense of compliance. Regulators expect risk-based customer due diligence — simplifying KYC for high-risk customer segments violates BSA/AML requirements. The optimization challenge is to maintain compliance while minimizing friction for legitimate customers." + related_metrics: [ "cac", "kyc-cost-per-customer", "monthly-active-users" ] + related_skills: [ "systems-thinking", "product-life-cycle" ] + caveats: "KYC conversion cannot be optimized at the expense of compliance. + Regulators expect risk-based customer due diligence — simplifying KYC for + high-risk customer segments violates BSA/AML requirements. The + optimization challenge is to maintain compliance while minimizing friction + for legitimate customers." - name: "KYC Cost per Customer" id: "kyc-cost-per-customer" category: "unit-economics" - definition: "The average cost to complete identity verification and customer due diligence for one new customer, including identity provider APIs, document verification services, sanctions screening, PEP checks, and manual review time for flagged applications." - formula: "(Identity Verification Costs + Sanctions/PEP Screening + Manual Review Labor + CDD Technology Costs) / Customers Verified" + definition: "The average cost to complete identity verification and customer due + diligence for one new customer, including identity provider APIs, document + verification services, sanctions screening, PEP checks, and manual review + time for flagged applications." + formula: "(Identity Verification Costs + Sanctions/PEP Screening + Manual Review + Labor + CDD Technology Costs) / Customers Verified" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $15 per customer (consumer) / > $150 (business)" - signal: "KYC costs are a material drag on unit economics. Manual review rates are likely above 20%, indicating poor automation or high-risk customer mix." + signal: "KYC costs are a material drag on unit economics. Manual review rates + are likely above 20%, indicating poor automation or high-risk customer + mix." below_average: value: "$8-$15 (consumer) / $75-$150 (business)" - signal: "Above-average KYC costs. Common when using premium identity providers without volume discounts, or when regulatory requirements mandate enhanced due diligence for most customers." + signal: "Above-average KYC costs. Common when using premium identity providers + without volume discounts, or when regulatory requirements mandate + enhanced due diligence for most customers." average: value: "$3-$8 (consumer) / $30-$75 (business)" - signal: "Standard KYC costs for digital fintech onboarding. Reflects automated identity verification with database matching and selective manual review." + signal: "Standard KYC costs for digital fintech onboarding. Reflects automated + identity verification with database matching and selective manual + review." good: value: "$1-$3 (consumer) / $15-$30 (business)" - signal: "Efficient KYC powered by automated verification, low manual review rates (<5%), and volume-based pricing with identity providers." + signal: "Efficient KYC powered by automated verification, low manual review + rates (<5%), and volume-based pricing with identity providers." excellent: value: "< $1 (consumer) / < $15 (business)" - signal: "Highly efficient KYC. Possible with proprietary verification systems, pre-verified customer pools (embedded finance), or tiered KYC that applies minimal verification for low-risk activities." + signal: "Highly efficient KYC. Possible with proprietary verification systems, + pre-verified customer pools (embedded finance), or tiered KYC that + applies minimal verification for low-risk activities." stage_notes: - seed: "KYC costs are high per customer at low volume. No volume discounts from identity providers. Manual review rates are high as processes are established." - series_a: "Negotiate volume-based pricing with identity providers (Jumio, Onfido, Plaid Identity). Target <10% manual review rate." - series_b_plus: "KYC cost optimization through proprietary models, consortium data sharing, and risk-based tiering. Regulatory requirements for periodic KYC refresh (CDD updates) add ongoing per-customer costs." + seed: "KYC costs are high per customer at low volume. No volume discounts from + identity providers. Manual review rates are high as processes are + established." + series_a: "Negotiate volume-based pricing with identity providers (Jumio, + Onfido, Plaid Identity). Target <10% manual review rate." + series_b_plus: "KYC cost optimization through proprietary models, consortium + data sharing, and risk-based tiering. Regulatory requirements for + periodic KYC refresh (CDD updates) add ongoing per-customer costs." data_sources: - source: "CB Insights State of Fintech" year: "2024" - source: "Plaid Developer Reports" year: "2023" - related_metrics: ["cac", "kyc-conversion-rate", "regulatory-compliance-cost"] - related_skills: ["systems-thinking", "kaizen-bpr"] - caveats: "KYC costs are not a one-time expense. Regulatory requirements mandate periodic customer refresh (enhanced CDD for higher-risk customers, sanctions list rescreening, address verification updates). The ongoing KYC cost per customer per year may exceed the initial verification cost." + related_metrics: [ "cac", "kyc-conversion-rate", "regulatory-compliance-cost" ] + related_skills: [ "systems-thinking", "kaizen-bpr" ] + caveats: "KYC costs are not a one-time expense. Regulatory requirements mandate + periodic customer refresh (enhanced CDD for higher-risk customers, + sanctions list rescreening, address verification updates). The ongoing KYC + cost per customer per year may exceed the initial verification cost." - name: "Regulatory Compliance Cost (% of Revenue)" id: "regulatory-compliance-cost" category: "efficiency" - definition: "Total regulatory compliance expenditure as a percentage of net revenue, encompassing KYC/AML operations, regulatory technology, compliance staff, legal counsel, audit costs, license maintenance, and regulatory reporting. This metric is unique to regulated industries and represents the 'tax' that regulation imposes on the business model." - formula: "(Compliance Staff Costs + RegTech Spend + Legal & Audit + License Fees + Regulatory Reporting Costs) / Net Revenue x 100" + definition: "Total regulatory compliance expenditure as a percentage of net + revenue, encompassing KYC/AML operations, regulatory technology, + compliance staff, legal counsel, audit costs, license maintenance, and + regulatory reporting. This metric is unique to regulated industries and + represents the 'tax' that regulation imposes on the business model." + formula: "(Compliance Staff Costs + RegTech Spend + Legal & Audit + License Fees + + Regulatory Reporting Costs) / Net Revenue x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 25% of revenue" - signal: "Compliance costs are consuming a quarter of revenue. Typical of early-stage fintechs building compliance infrastructure from scratch, or companies facing regulatory enforcement actions." + signal: "Compliance costs are consuming a quarter of revenue. Typical of + early-stage fintechs building compliance infrastructure from scratch, + or companies facing regulatory enforcement actions." below_average: value: "15-25%" - signal: "High compliance cost burden. Common during initial license acquisition, SOX compliance buildout, or in jurisdictions with complex multi-regulator environments." + signal: "High compliance cost burden. Common during initial license acquisition, + SOX compliance buildout, or in jurisdictions with complex + multi-regulator environments." average: value: "8-15%" - signal: "Standard compliance cost for established fintech companies. Banks average approximately 10-15% of operating costs on compliance (McKinsey 2023). Fintechs typically run at the higher end due to scale disadvantages." + signal: "Standard compliance cost for established fintech companies. Banks + average approximately 10-15% of operating costs on compliance + (McKinsey 2023). Fintechs typically run at the higher end due to scale + disadvantages." good: value: "4-8%" - signal: "Efficient compliance through automation, regtech tools, and mature compliance processes. Scale advantages reduce per-customer compliance cost." + signal: "Efficient compliance through automation, regtech tools, and mature + compliance processes. Scale advantages reduce per-customer compliance + cost." excellent: value: "< 4%" - signal: "Highly efficient compliance — typically achieved by large-scale fintechs with proprietary regtech, automated regulatory reporting, and mature compliance programs. Stripe and Plaid operate in this range at scale." + signal: "Highly efficient compliance — typically achieved by large-scale + fintechs with proprietary regtech, automated regulatory reporting, and + mature compliance programs. Stripe and Plaid operate in this range at + scale." stage_notes: - seed: "Compliance costs as a percentage of revenue will be extremely high (30-50%+) because the infrastructure must be built before revenue scales. This is expected and investors should be educated accordingly." - series_a: "Compliance cost percentage should decline as revenue scales faster than compliance infrastructure costs. Target 15-20% and demonstrate the trajectory toward 10%." - series_b_plus: "At scale, compliance costs should approach 5-10% of revenue. Investment in regtech automation is the primary lever. Regulatory changes (new reporting requirements, expanded licensing) can cause step-function cost increases." + seed: "Compliance costs as a percentage of revenue will be extremely high + (30-50%+) because the infrastructure must be built before revenue + scales. This is expected and investors should be educated accordingly." + series_a: "Compliance cost percentage should decline as revenue scales faster + than compliance infrastructure costs. Target 15-20% and demonstrate the + trajectory toward 10%." + series_b_plus: "At scale, compliance costs should approach 5-10% of revenue. + Investment in regtech automation is the primary lever. Regulatory + changes (new reporting requirements, expanded licensing) can cause + step-function cost increases." data_sources: - source: "McKinsey Global Payments Report" year: "2023" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["kyc-cost-per-customer", "gross-margin", "cost-to-income-ratio"] - related_skills: ["balanced-scorecard", "kaizen-bpr"] - caveats: "Under-spending on compliance is more dangerous than over-spending. A fintech with compliance costs at 2% of revenue may be under-investing — the savings today become enforcement actions, fines, and license revocations tomorrow. The 2023 consent orders against neobanks (Chime, Dave) demonstrate the cost of compliance under-investment." + related_metrics: [ "kyc-cost-per-customer", "gross-margin", "cost-to-income-ratio" ] + related_skills: [ "balanced-scorecard", "kaizen-bpr" ] + caveats: "Under-spending on compliance is more dangerous than over-spending. A + fintech with compliance costs at 2% of revenue may be under-investing — + the savings today become enforcement actions, fines, and license + revocations tomorrow. The 2023 consent orders against neobanks (Chime, + Dave) demonstrate the cost of compliance under-investment." - name: "Capital Adequacy Ratio" id: "capital-adequacy-ratio" category: "financial" - definition: "The ratio of regulatory capital to risk-weighted assets, measuring the institution's capacity to absorb losses while protecting depositors and the financial system. Applicable to fintechs with bank charters, lending operations, or custody of customer funds." + definition: "The ratio of regulatory capital to risk-weighted assets, measuring + the institution's capacity to absorb losses while protecting depositors + and the financial system. Applicable to fintechs with bank charters, + lending operations, or custody of customer funds." formula: "(Tier 1 Capital + Tier 2 Capital) / Risk-Weighted Assets x 100" unit: "percentage" direction: "target-range" benchmarks: poor: value: "< 8% (below Basel III minimum)" - signal: "Below regulatory minimum. The institution faces immediate supervisory action, restrictions on lending, and potential license revocation." + signal: "Below regulatory minimum. The institution faces immediate supervisory + action, restrictions on lending, and potential license revocation." below_average: value: "8-10%" - signal: "At or near minimum requirements. No buffer for unexpected losses. Regulators will impose heightened surveillance and may restrict growth." + signal: "At or near minimum requirements. No buffer for unexpected losses. + Regulators will impose heightened surveillance and may restrict + growth." average: value: "10-13%" - signal: "Standard capitalization. Meets requirements with moderate buffer. Most U.S. banks maintain ratios in this range." + signal: "Standard capitalization. Meets requirements with moderate buffer. Most + U.S. banks maintain ratios in this range." good: value: "13-18%" - signal: "Well-capitalized with significant buffer. Provides flexibility for portfolio growth, acquisitions, or absorption of credit cycle downturns." + signal: "Well-capitalized with significant buffer. Provides flexibility for + portfolio growth, acquisitions, or absorption of credit cycle + downturns." excellent: value: "> 18%" - signal: "Very well-capitalized. Common in fintech banks pre-growth phase when capital has been raised but not yet deployed into earning assets. Over-capitalization at mature scale may indicate under-deployment of capital." + signal: "Very well-capitalized. Common in fintech banks pre-growth phase when + capital has been raised but not yet deployed into earning assets. + Over-capitalization at mature scale may indicate under-deployment of + capital." stage_notes: - seed: "Capital adequacy is relevant only for charter holders. For non-bank fintechs, the equivalent is cash reserves relative to customer funds held and contingent liabilities." - series_a: "If pursuing a bank charter, demonstrate a clear capital plan. Regulators evaluate the institution's ability to maintain capital adequacy under stress scenarios." - series_b_plus: "Capital planning becomes a board-level topic. Basel III requirements, CECL accounting standards, and stress testing (DFAST for larger institutions) govern capital management." + seed: "Capital adequacy is relevant only for charter holders. For non-bank + fintechs, the equivalent is cash reserves relative to customer funds + held and contingent liabilities." + series_a: "If pursuing a bank charter, demonstrate a clear capital plan. + Regulators evaluate the institution's ability to maintain capital + adequacy under stress scenarios." + series_b_plus: "Capital planning becomes a board-level topic. Basel III + requirements, CECL accounting standards, and stress testing (DFAST for + larger institutions) govern capital management." data_sources: - source: "Basel Committee on Banking Supervision" year: "2023" - source: "FDIC Quarterly Banking Profile" year: "2023" - related_metrics: ["net-interest-margin", "default-rate", "loan-origination-volume"] - related_skills: ["scenario-planning", "balanced-scorecard"] - caveats: "Capital adequacy requirements differ by charter type and jurisdiction. De novo bank charters typically face higher capital requirements for the first 3-7 years. ILC charters, fintech charters, and international charters each carry different capital standards. Non-bank fintechs with bank partnerships must understand their partner bank's capital constraints." + related_metrics: [ "net-interest-margin", "default-rate", "loan-origination-volume" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "Capital adequacy requirements differ by charter type and jurisdiction. + De novo bank charters typically face higher capital requirements for the + first 3-7 years. ILC charters, fintech charters, and international + charters each carry different capital standards. Non-bank fintechs with + bank partnerships must understand their partner bank's capital + constraints." # ───────────────────────────────────────────── # FINANCIAL PERFORMANCE @@ -664,30 +1003,48 @@ benchmarks: - name: "Gross Margin" id: "gross-margin" category: "financial" - definition: "Net revenue minus cost of revenue (interchange, processing fees, fraud losses, hosting, compliance-driven transaction costs) as a percentage of net revenue. Gross margin in fintech varies dramatically by business model — payments businesses operate at lower gross margins than software-like revenue streams." + definition: "Net revenue minus cost of revenue (interchange, processing fees, + fraud losses, hosting, compliance-driven transaction costs) as a + percentage of net revenue. Gross margin in fintech varies dramatically by + business model — payments businesses operate at lower gross margins than + software-like revenue streams." formula: "(Net Revenue - Cost of Revenue) / Net Revenue x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 30%" - signal: "Thin margins indicating the business is primarily a payment pass-through with minimal value-add. Vulnerable to interchange changes and processor price increases." + signal: "Thin margins indicating the business is primarily a payment + pass-through with minimal value-add. Vulnerable to interchange changes + and processor price increases." below_average: value: "30-45%" - signal: "Low-margin financial services. Common in pure-play payment processing where interchange is the dominant COGS component." + signal: "Low-margin financial services. Common in pure-play payment processing + where interchange is the dominant COGS component." average: value: "45-60%" - signal: "Standard range for diversified fintech companies with a mix of transaction-based and subscription/fee-based revenue. Nubank's gross margin approached 50% at IPO." + signal: "Standard range for diversified fintech companies with a mix of + transaction-based and subscription/fee-based revenue. Nubank's gross + margin approached 50% at IPO." good: value: "60-75%" - signal: "Strong margins driven by SaaS-like revenue components (subscription fees, platform fees, data products) layered on top of transaction processing." + signal: "Strong margins driven by SaaS-like revenue components (subscription + fees, platform fees, data products) layered on top of transaction + processing." excellent: value: "> 75%" - signal: "Software-like margins. Typical of regtech, B2B fintech infrastructure, or platforms where the payment processing is a distribution channel for higher-margin products." + signal: "Software-like margins. Typical of regtech, B2B fintech infrastructure, + or platforms where the payment processing is a distribution channel + for higher-margin products." stage_notes: - seed: "Gross margin is often negative at seed due to fixed compliance and infrastructure costs spread over minimal revenue." - series_a: "Gross margin trajectory matters more than current level. Demonstrate the path to 50%+ through scale and product mix evolution." - series_b_plus: "Investors evaluate gross margin by revenue line. Separate transaction-based revenue (lower margin) from platform/subscription revenue (higher margin). The ratio determines valuation multiples — SaaS-like margins command SaaS-like multiples." + seed: "Gross margin is often negative at seed due to fixed compliance and + infrastructure costs spread over minimal revenue." + series_a: "Gross margin trajectory matters more than current level. Demonstrate + the path to 50%+ through scale and product mix evolution." + series_b_plus: "Investors evaluate gross margin by revenue line. Separate + transaction-based revenue (lower margin) from platform/subscription + revenue (higher margin). The ratio determines valuation multiples — + SaaS-like margins command SaaS-like multiples." data_sources: - source: "Nubank S-1 Filing" year: "2021" @@ -695,45 +1052,73 @@ benchmarks: year: "2024" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["take-rate", "cost-per-transaction", "regulatory-compliance-cost"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "Gross margin definitions vary across fintech sub-sectors. Lending fintechs may classify credit losses as COGS or below the gross margin line. Payment processors differ on whether fraud losses are COGS or operating expenses. Normalize definitions when benchmarking against peers." + related_metrics: [ "take-rate", "cost-per-transaction", "regulatory-compliance-cost" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Gross margin definitions vary across fintech sub-sectors. Lending + fintechs may classify credit losses as COGS or below the gross margin + line. Payment processors differ on whether fraud losses are COGS or + operating expenses. Normalize definitions when benchmarking against + peers." - name: "Net Revenue Retention" id: "net-revenue-retention" category: "retention" - definition: "The percentage of revenue retained from existing customers after accounting for expansion (new products, increased usage), contraction (downgrade, reduced volume), and churn. In fintech, NRR measures the platform's ability to deepen customer relationships through cross-sell and increased transaction volume." - formula: "(Starting Revenue + Expansion - Contraction - Churn) / Starting Revenue x 100" + definition: "The percentage of revenue retained from existing customers after + accounting for expansion (new products, increased usage), contraction + (downgrade, reduced volume), and churn. In fintech, NRR measures the + platform's ability to deepen customer relationships through cross-sell and + increased transaction volume." + formula: "(Starting Revenue + Expansion - Contraction - Churn) / Starting + Revenue x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 90%" - signal: "Significant revenue erosion from existing customers. In payments, this may reflect merchant attrition or transaction volume decline. In lending, it may indicate borrowers refinancing elsewhere." + signal: "Significant revenue erosion from existing customers. In payments, this + may reflect merchant attrition or transaction volume decline. In + lending, it may indicate borrowers refinancing elsewhere." below_average: value: "90-100%" - signal: "Flat to slightly declining revenue from existing customers. The platform is not successfully cross-selling or the core product faces competitive displacement." + signal: "Flat to slightly declining revenue from existing customers. The + platform is not successfully cross-selling or the core product faces + competitive displacement." average: value: "100-115%" - signal: "Modest net expansion from existing customers. Standard for fintech platforms where transaction volume grows naturally with customer business growth." + signal: "Modest net expansion from existing customers. Standard for fintech + platforms where transaction volume grows naturally with customer + business growth." good: value: "115-130%" - signal: "Strong expansion driven by effective cross-sell (adding lending to payments, insurance to banking) or organic transaction volume growth. Nubank achieved 120%+ NRR through product expansion." + signal: "Strong expansion driven by effective cross-sell (adding lending to + payments, insurance to banking) or organic transaction volume growth. + Nubank achieved 120%+ NRR through product expansion." excellent: value: "> 130%" - signal: "Exceptional expansion. Indicates a platform where customers adopt multiple products over time — the fintech superapp model (SoFi, Nubank, Revolut)." + signal: "Exceptional expansion. Indicates a platform where customers adopt + multiple products over time — the fintech superapp model (SoFi, + Nubank, Revolut)." stage_notes: - seed: "NRR is unmeasurable with few customers. Track qualitative signals: are existing customers requesting additional products or processing more volume?" - series_a: "NRR above 100% is a strong signal. In fintech, cross-sell into adjacent products (payments -> lending -> deposits) is the primary NRR driver." - series_b_plus: "NRR above 120% signals platform economics. Investors value fintech platforms with strong NRR at higher multiples because cross-sell reduces blended CAC." + seed: "NRR is unmeasurable with few customers. Track qualitative signals: are + existing customers requesting additional products or processing more + volume?" + series_a: "NRR above 100% is a strong signal. In fintech, cross-sell into + adjacent products (payments -> lending -> deposits) is the primary NRR + driver." + series_b_plus: "NRR above 120% signals platform economics. Investors value + fintech platforms with strong NRR at higher multiples because cross-sell + reduces blended CAC." data_sources: - source: "Nubank S-1 Filing" year: "2021" - source: "SoFi Annual Reports" year: "2023" - related_metrics: ["ltv", "monthly-active-users", "transactions-per-user"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "Fintech NRR can be inflated by macroeconomic tailwinds — rising transaction volumes in a growing economy lift NRR without any action by the platform. Stress-test NRR against recession scenarios where transaction volumes decline." + related_metrics: [ "ltv", "monthly-active-users", "transactions-per-user" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Fintech NRR can be inflated by macroeconomic tailwinds — rising + transaction volumes in a growing economy lift NRR without any action by + the platform. Stress-test NRR against recession scenarios where + transaction volumes decline." # ───────────────────────────────────────────── # ENGAGEMENT & GROWTH @@ -742,110 +1127,167 @@ benchmarks: - name: "Monthly Active Users" id: "monthly-active-users" category: "product" - definition: "The number of unique users who perform at least one qualifying financial activity (transaction, login with balance check, transfer, loan payment) within a calendar month. In fintech, MAU should exclude passive account holders who have not engaged — the definition must reflect genuine financial activity." + definition: "The number of unique users who perform at least one qualifying + financial activity (transaction, login with balance check, transfer, loan + payment) within a calendar month. In fintech, MAU should exclude passive + account holders who have not engaged — the definition must reflect genuine + financial activity." formula: "COUNT(DISTINCT users with qualifying_activity) over calendar month" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 20% of registered users are monthly active" - signal: "The product is not embedded in customers' financial lives. High dormancy indicates the product is used occasionally rather than habitually." + signal: "The product is not embedded in customers' financial lives. High + dormancy indicates the product is used occasionally rather than + habitually." below_average: value: "20-40% of registered users active" - signal: "Moderate engagement. Common for single-product fintechs where usage is periodic (lending, insurance) rather than daily." + signal: "Moderate engagement. Common for single-product fintechs where usage is + periodic (lending, insurance) rather than daily." average: value: "40-60% of registered users active" - signal: "Solid engagement. Standard for neobanks and payment apps where regular transactions drive recurring usage." + signal: "Solid engagement. Standard for neobanks and payment apps where regular + transactions drive recurring usage." good: value: "60-80% of registered users active" - signal: "Strong engagement indicating the product is a primary financial tool. Nubank reported 80%+ MAU/total customer ratio." + signal: "Strong engagement indicating the product is a primary financial tool. + Nubank reported 80%+ MAU/total customer ratio." excellent: value: "> 80% of registered users active" - signal: "Exceptional engagement. The product is the customer's primary financial account. High MAU/registered ratio correlates with strong NRR and low churn." + signal: "Exceptional engagement. The product is the customer's primary financial + account. High MAU/registered ratio correlates with strong NRR and low + churn." stage_notes: - seed: "MAU is small in absolute terms. Focus on engagement depth (transactions per active user) rather than breadth." - series_a: "MAU growth rate and MAU/registered ratio are the key metrics. Declining ratio as acquisition scales suggests the new cohorts are less engaged than early adopters." - series_b_plus: "DAU/MAU ratio becomes important — daily engagement indicates the product is a financial utility. Nubank and Revolut target DAU/MAU above 30%." + seed: "MAU is small in absolute terms. Focus on engagement depth (transactions + per active user) rather than breadth." + series_a: "MAU growth rate and MAU/registered ratio are the key metrics. + Declining ratio as acquisition scales suggests the new cohorts are less + engaged than early adopters." + series_b_plus: "DAU/MAU ratio becomes important — daily engagement indicates the + product is a financial utility. Nubank and Revolut target DAU/MAU above + 30%." data_sources: - source: "Nubank Annual Reports" year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["transactions-per-user", "net-revenue-retention", "cac"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "MAU definitions vary across fintechs and can be gamed. A 'login' should not count as an active user event if no financial activity occurred. Define MAU consistently and disclose the definition to investors. Regulators may also require active account reporting for dormant account regulations." + related_metrics: [ "transactions-per-user", "net-revenue-retention", "cac" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "MAU definitions vary across fintechs and can be gamed. A 'login' + should not count as an active user event if no financial activity + occurred. Define MAU consistently and disclose the definition to + investors. Regulators may also require active account reporting for + dormant account regulations." - name: "Transactions per User per Month" id: "transactions-per-user" category: "product" - definition: "The average number of transactions each active user conducts per month. Measures engagement depth and the degree to which the product is embedded in the customer's daily financial life." + definition: "The average number of transactions each active user conducts per + month. Measures engagement depth and the degree to which the product is + embedded in the customer's daily financial life." formula: "Total Monthly Transactions / Monthly Active Users" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 2 transactions/user/month" - signal: "Low engagement. The product is not habitual — customers use it for occasional, specific needs rather than as a daily financial tool." + signal: "Low engagement. The product is not habitual — customers use it for + occasional, specific needs rather than as a daily financial tool." below_average: value: "2-5 transactions/user/month" - signal: "Moderate engagement. Typical of single-use-case products (bill pay, remittance, specific investment activity)." + signal: "Moderate engagement. Typical of single-use-case products (bill pay, + remittance, specific investment activity)." average: value: "5-10 transactions/user/month" - signal: "Solid engagement. Standard for neobanks where a debit card and direct deposit drive regular transaction activity." + signal: "Solid engagement. Standard for neobanks where a debit card and direct + deposit drive regular transaction activity." good: value: "10-20 transactions/user/month" - signal: "Strong engagement indicating the product serves multiple financial needs. Cross-sell into payments, savings, and investments drives transaction frequency." + signal: "Strong engagement indicating the product serves multiple financial + needs. Cross-sell into payments, savings, and investments drives + transaction frequency." excellent: value: "> 20 transactions/user/month" - signal: "Exceptional engagement. The product is the customer's primary financial account. High transaction frequency drives data advantage and cross-sell opportunity." + signal: "Exceptional engagement. The product is the customer's primary financial + account. High transaction frequency drives data advantage and + cross-sell opportunity." stage_notes: - seed: "Transaction frequency data is limited. Track whether early users increase their transaction frequency over time — a strong product-market fit signal." - series_a: "Transactions per user should increase as the product adds use cases. A declining trend despite product additions signals a product problem." - series_b_plus: "High transactions per user drives revenue per user and creates data moats for credit underwriting, personalization, and fraud detection." + seed: "Transaction frequency data is limited. Track whether early users increase + their transaction frequency over time — a strong product-market fit + signal." + series_a: "Transactions per user should increase as the product adds use cases. + A declining trend despite product additions signals a product problem." + series_b_plus: "High transactions per user drives revenue per user and creates + data moats for credit underwriting, personalization, and fraud + detection." data_sources: - source: "Nubank Annual Reports" year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["monthly-active-users", "revenue-per-transaction", "net-revenue-retention"] - related_skills: ["net-promoter-score", "systems-thinking"] - caveats: "Average transactions per user masks bimodal distribution. Power users may transact 50+ times per month while dormant users transact once. Segment this metric by cohort and user type to expose the actual engagement distribution." + related_metrics: [ "monthly-active-users", "revenue-per-transaction", "net-revenue-retention" ] + related_skills: [ "net-promoter-score", "systems-thinking" ] + caveats: "Average transactions per user masks bimodal distribution. Power users + may transact 50+ times per month while dormant users transact once. + Segment this metric by cohort and user type to expose the actual + engagement distribution." - name: "Deposit Growth Rate" id: "deposit-growth-rate" category: "growth" - definition: "The month-over-month or year-over-year growth rate of customer deposits held on the platform. For neobanks and deposit-taking fintechs, deposit growth is both a customer engagement metric and a funding cost metric — deposits are the cheapest source of lending capital." + definition: "The month-over-month or year-over-year growth rate of customer + deposits held on the platform. For neobanks and deposit-taking fintechs, + deposit growth is both a customer engagement metric and a funding cost + metric — deposits are the cheapest source of lending capital." formula: "(Deposits_current - Deposits_prior) / Deposits_prior x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 5% QoQ deposit growth" - signal: "Deposit growth stalling. Customers are not deepening their relationship with the platform or are moving deposits to competitors offering higher yields." + signal: "Deposit growth stalling. Customers are not deepening their relationship + with the platform or are moving deposits to competitors offering + higher yields." below_average: value: "5-15% QoQ" - signal: "Moderate growth. Deposits are accumulating but not at the rate needed to fund significant lending operations." + signal: "Moderate growth. Deposits are accumulating but not at the rate needed + to fund significant lending operations." average: value: "15-30% QoQ" - signal: "Healthy deposit growth. Sufficient to fund lending expansion and demonstrate to regulators that the deposit base is stable." + signal: "Healthy deposit growth. Sufficient to fund lending expansion and + demonstrate to regulators that the deposit base is stable." good: value: "30-50% QoQ" - signal: "Strong growth. Chime, Varo, and SoFi achieved 40%+ QoQ deposit growth during high-growth phases. Indicates direct deposit adoption." + signal: "Strong growth. Chime, Varo, and SoFi achieved 40%+ QoQ deposit growth + during high-growth phases. Indicates direct deposit adoption." excellent: value: "> 50% QoQ" - signal: "Exceptional growth. Typically accompanied by a catalytic event — product launch, rate promotion, or viral moment. Verify that deposits are 'sticky' (direct deposit) not 'hot money' (rate-chasing)." + signal: "Exceptional growth. Typically accompanied by a catalytic event — + product launch, rate promotion, or viral moment. Verify that deposits + are 'sticky' (direct deposit) not 'hot money' (rate-chasing)." stage_notes: - seed: "Deposits are minimal if the product is pre-launch. For neobanks, the first milestone is direct deposit adoption — this signals primary banking relationship." - series_a: "Deposit growth rate and average deposit balance per customer are the key metrics. Regulators monitor deposit stability for charter applications." - series_b_plus: "Deposit growth enables the lending engine. The cost of deposit funding (interest paid) versus wholesale funding (warehouse lines) is the primary margin differentiator for neobanks." + seed: "Deposits are minimal if the product is pre-launch. For neobanks, the + first milestone is direct deposit adoption — this signals primary + banking relationship." + series_a: "Deposit growth rate and average deposit balance per customer are the + key metrics. Regulators monitor deposit stability for charter + applications." + series_b_plus: "Deposit growth enables the lending engine. The cost of deposit + funding (interest paid) versus wholesale funding (warehouse lines) is + the primary margin differentiator for neobanks." data_sources: - source: "SoFi Annual Reports" year: "2023" - source: "FDIC Quarterly Banking Profile" year: "2023" - related_metrics: ["net-interest-margin", "monthly-active-users", "net-revenue-retention"] - related_skills: ["growth-share-matrix", "product-life-cycle"] - caveats: "Deposit growth driven by high interest rate promotions produces 'hot money' — deposits that leave when rates normalize. Measure the percentage of deposits that arrive via direct deposit (sticky) versus manual transfer (potentially rate-sensitive). Regulators evaluate deposit stability as part of safety and soundness examinations." + related_metrics: [ "net-interest-margin", "monthly-active-users", "net-revenue-retention" ] + related_skills: [ "growth-share-matrix", "product-life-cycle" ] + caveats: "Deposit growth driven by high interest rate promotions produces 'hot + money' — deposits that leave when rates normalize. Measure the percentage + of deposits that arrive via direct deposit (sticky) versus manual transfer + (potentially rate-sensitive). Regulators evaluate deposit stability as + part of safety and soundness examinations." # ───────────────────────────────────────────── # WEALTHTECH METRICS @@ -854,38 +1296,57 @@ benchmarks: - name: "Assets Under Management" id: "aum" category: "growth" - definition: "The total market value of financial assets managed on behalf of customers. AUM is the top-line scale metric for wealthtech, robo-advisors, and investment platforms. Revenue is typically a percentage of AUM (management fee), making AUM growth the primary revenue driver." + definition: "The total market value of financial assets managed on behalf of + customers. AUM is the top-line scale metric for wealthtech, robo-advisors, + and investment platforms. Revenue is typically a percentage of AUM + (management fee), making AUM growth the primary revenue driver." formula: "SUM(customer_portfolio_market_value)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $10M AUM at 12 months" - signal: "Insufficient scale to cover operating costs. At a 25bps management fee, $10M AUM generates only $25K annual revenue." + signal: "Insufficient scale to cover operating costs. At a 25bps management fee, + $10M AUM generates only $25K annual revenue." below_average: value: "$10M-$100M AUM" - signal: "Early traction but economics are challenging. A 50bps fee on $50M AUM generates $250K annual revenue." + signal: "Early traction but economics are challenging. A 50bps fee on $50M AUM + generates $250K annual revenue." average: value: "$100M-$1B AUM" - signal: "Meaningful scale. Betterment and Wealthfront surpassed $1B AUM within 3 years. Sufficient to attract institutional partnerships." + signal: "Meaningful scale. Betterment and Wealthfront surpassed $1B AUM within 3 + years. Sufficient to attract institutional partnerships." good: value: "$1B-$10B AUM" - signal: "Strong scale with improving unit economics. Management fee revenue supports meaningful team and technology investment." + signal: "Strong scale with improving unit economics. Management fee revenue + supports meaningful team and technology investment." excellent: value: "> $10B AUM" - signal: "Institutional scale. Betterment manages approximately $35B; Wealthfront approximately $50B. At this scale, even 1bps of fee optimization is material." + signal: "Institutional scale. Betterment manages approximately $35B; Wealthfront + approximately $50B. At this scale, even 1bps of fee optimization is + material." stage_notes: - seed: "AUM is minimal. Focus on demonstrating investment methodology and regulatory compliance (RIA registration with SEC or state regulators)." - series_a: "AUM growth rate and average account balance are the key metrics. SEC registration required at $100M+ AUM. Compliance costs step up with registration." - series_b_plus: "AUM growth must be decomposed into net flows (customer deposits minus withdrawals) and market appreciation. Investors scrutinize net flows because market appreciation is not attributable to the platform's efforts." + seed: "AUM is minimal. Focus on demonstrating investment methodology and + regulatory compliance (RIA registration with SEC or state regulators)." + series_a: "AUM growth rate and average account balance are the key metrics. SEC + registration required at $100M+ AUM. Compliance costs step up with + registration." + series_b_plus: "AUM growth must be decomposed into net flows (customer deposits + minus withdrawals) and market appreciation. Investors scrutinize net + flows because market appreciation is not attributable to the platform's + efforts." data_sources: - source: "a16z Fintech Reports" year: "2024" - source: "CB Insights State of Fintech" year: "2024" - related_metrics: ["monthly-active-users", "net-revenue-retention", "cac"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "AUM is heavily influenced by market movements. A wealthtech platform can report 30% AUM growth with zero net customer deposits if the market rises 30%. Always decompose AUM changes into net flows and market appreciation. SEC and FINRA regulations govern AUM calculation and disclosure methodology." + related_metrics: [ "monthly-active-users", "net-revenue-retention", "cac" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "AUM is heavily influenced by market movements. A wealthtech platform + can report 30% AUM growth with zero net customer deposits if the market + rises 30%. Always decompose AUM changes into net flows and market + appreciation. SEC and FINRA regulations govern AUM calculation and + disclosure methodology." # ───────────────────────────────────────────── # OPERATIONAL EFFICIENCY @@ -894,30 +1355,48 @@ benchmarks: - name: "Cost to Income Ratio" id: "cost-to-income-ratio" category: "efficiency" - definition: "Total operating expenses divided by total operating income, measuring the operational efficiency of the financial institution. This is the banking industry's core efficiency metric, and fintech companies targeting bank economics must track it. Lower ratios indicate more efficient operations." + definition: "Total operating expenses divided by total operating income, + measuring the operational efficiency of the financial institution. This is + the banking industry's core efficiency metric, and fintech companies + targeting bank economics must track it. Lower ratios indicate more + efficient operations." formula: "Operating Expenses / Operating Income x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 100% (operating at a loss)" - signal: "Expenses exceed income. Expected at early stage but unsustainable. Investor capital is funding operations, not just growth." + signal: "Expenses exceed income. Expected at early stage but unsustainable. + Investor capital is funding operations, not just growth." below_average: value: "80-100%" - signal: "Near break-even operations. The institution is not yet generating meaningful operating profit." + signal: "Near break-even operations. The institution is not yet generating + meaningful operating profit." average: value: "50-80%" - signal: "Standard range for fintech companies approaching maturity. Traditional banks average 55-65%. Digital-first fintechs should target the lower end." + signal: "Standard range for fintech companies approaching maturity. Traditional + banks average 55-65%. Digital-first fintechs should target the lower + end." good: value: "35-50%" - signal: "Efficient operations. Nubank achieved a cost-to-income ratio below 40% — demonstrating the structural efficiency advantage of digital-first financial services." + signal: "Efficient operations. Nubank achieved a cost-to-income ratio below 40% + — demonstrating the structural efficiency advantage of digital-first + financial services." excellent: value: "< 35%" - signal: "Exceptional efficiency. Significantly better than traditional banking. Achieved through digital-only operations, automated processes, and minimal branch infrastructure." + signal: "Exceptional efficiency. Significantly better than traditional banking. + Achieved through digital-only operations, automated processes, and + minimal branch infrastructure." stage_notes: - seed: "Cost-to-income ratio is extremely high (200%+) and irrelevant at seed. Focus on building the infrastructure that will drive efficiency at scale." - series_a: "Ratio should improve quarterly. Demonstrate operating leverage — revenue growing faster than operating costs." - series_b_plus: "Target sub-50% and declining. Nubank's path from >100% to <40% was central to its equity story. Regulators evaluate this ratio for safety and soundness — excessively low ratios may indicate under-investment in compliance or risk management." + seed: "Cost-to-income ratio is extremely high (200%+) and irrelevant at seed. + Focus on building the infrastructure that will drive efficiency at + scale." + series_a: "Ratio should improve quarterly. Demonstrate operating leverage — + revenue growing faster than operating costs." + series_b_plus: "Target sub-50% and declining. Nubank's path from >100% to <40% + was central to its equity story. Regulators evaluate this ratio for + safety and soundness — excessively low ratios may indicate + under-investment in compliance or risk management." data_sources: - source: "Nubank Annual Reports" year: "2023" @@ -925,37 +1404,57 @@ benchmarks: year: "2023" - source: "McKinsey Global Payments Report" year: "2023" - related_metrics: ["gross-margin", "regulatory-compliance-cost", "net-interest-margin"] - related_skills: ["kaizen-bpr", "balanced-scorecard"] - caveats: "Cost-to-income ratio comparisons between fintechs and traditional banks are misleading without adjusting for business mix. A bank with branches, lending operations, and wealth management has fundamentally different cost structure than a digital-only payment processor. Compare within peer group." + related_metrics: [ "gross-margin", "regulatory-compliance-cost", "net-interest-margin" ] + related_skills: [ "kaizen-bpr", "balanced-scorecard" ] + caveats: "Cost-to-income ratio comparisons between fintechs and traditional + banks are misleading without adjusting for business mix. A bank with + branches, lending operations, and wealth management has fundamentally + different cost structure than a digital-only payment processor. Compare + within peer group." - name: "ARPU — Average Revenue per User" id: "arpu" category: "unit-economics" - definition: "The average monthly or annual net revenue generated per active user across all revenue streams (transaction fees, interchange, interest income, subscription fees, premium services). ARPU measures the monetization intensity of the user base." + definition: "The average monthly or annual net revenue generated per active user + across all revenue streams (transaction fees, interchange, interest + income, subscription fees, premium services). ARPU measures the + monetization intensity of the user base." formula: "Total Net Revenue / Average Monthly Active Users" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $2/month per user (consumer)" - signal: "Low monetization. The product has not found a revenue model that matches engagement. Common in free neobanks relying solely on interchange from debit transactions." + signal: "Low monetization. The product has not found a revenue model that + matches engagement. Common in free neobanks relying solely on + interchange from debit transactions." below_average: value: "$2-$5/month (consumer)" - signal: "Below-average monetization. Typical of single-revenue-line fintech products (interchange only, or low-frequency lending only)." + signal: "Below-average monetization. Typical of single-revenue-line fintech + products (interchange only, or low-frequency lending only)." average: value: "$5-$15/month (consumer)" - signal: "Standard monetization. Nubank reported approximately $8 monthly ARPU at IPO. Sufficient to fund operations if retention is strong." + signal: "Standard monetization. Nubank reported approximately $8 monthly ARPU at + IPO. Sufficient to fund operations if retention is strong." good: value: "$15-$40/month (consumer)" - signal: "Strong monetization through multiple revenue streams. Cross-sell into lending, insurance, and premium services lifts ARPU above single-product levels." + signal: "Strong monetization through multiple revenue streams. Cross-sell into + lending, insurance, and premium services lifts ARPU above + single-product levels." excellent: value: "> $40/month (consumer)" - signal: "Exceptional ARPU. SoFi achieved $50+ monthly ARPU through multi-product adoption (lending + investing + banking). Indicates deep platform engagement." + signal: "Exceptional ARPU. SoFi achieved $50+ monthly ARPU through multi-product + adoption (lending + investing + banking). Indicates deep platform + engagement." stage_notes: - seed: "ARPU is low and unstable. Focus on identifying which revenue streams will drive future ARPU growth." - series_a: "ARPU growth trajectory matters. Demonstrate the ARPU uplift as customers adopt additional products — the multi-product ARPU story is central to fintech platform narratives." - series_b_plus: "ARPU by product vintage and product adoption tier should be the reporting standard. Show that customers who adopt 3+ products generate 5-8x the ARPU of single-product customers." + seed: "ARPU is low and unstable. Focus on identifying which revenue streams will + drive future ARPU growth." + series_a: "ARPU growth trajectory matters. Demonstrate the ARPU uplift as + customers adopt additional products — the multi-product ARPU story is + central to fintech platform narratives." + series_b_plus: "ARPU by product vintage and product adoption tier should be the + reporting standard. Show that customers who adopt 3+ products generate + 5-8x the ARPU of single-product customers." data_sources: - source: "Nubank S-1 Filing" year: "2021" @@ -963,6 +1462,14 @@ benchmarks: year: "2023" - source: "a16z Fintech Reports" year: "2024" - related_metrics: ["monthly-active-users", "net-revenue-retention", "ltv"] - related_skills: ["pricing-diagnosis", "business-model-canvas"] - caveats: "ARPU that relies heavily on interchange is vulnerable to regulatory caps (Durbin, PSD2 IFR). Separate ARPU by revenue type to understand regulatory exposure. Lending-driven ARPU is subject to credit cycle risk — high ARPU from interest income in benign credit conditions may vanish in a downturn." + related_metrics: [ "monthly-active-users", "net-revenue-retention", "ltv" ] + related_skills: + - business-model-canvas + caveats: "ARPU that relies heavily on interchange is vulnerable to regulatory + caps (Durbin, PSD2 IFR). Separate ARPU by revenue type to understand + regulatory exposure. Lending-driven ARPU is subject to credit cycle risk — + high ARPU from interest income in benign credit conditions may vanish in a + downturn." + related_content: + - kind: diagnostic + ref: pricing-diagnosis diff --git a/.claude/industry-packs/fintech/fintech-diagnostic-rules.yaml b/.claude/industry-packs/fintech/fintech-diagnostic-rules.yaml index 11b017d..452d240 100644 --- a/.claude/industry-packs/fintech/fintech-diagnostic-rules.yaml +++ b/.claude/industry-packs/fintech/fintech-diagnostic-rules.yaml @@ -35,49 +35,103 @@ diagnostic_rules: - diagnostic: "customer-churn-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Fintech churn has a dimension absent from other industries: compliance-driven involuntary churn. Account closures triggered by KYC failures, AML risk reviews, and fraud suspicion create churn that is not product-driven and cannot be solved by product improvements. Separating compliance-driven churn from product/market churn is essential for accurate diagnosis." + adaptation_rationale: "Fintech churn has a dimension absent from other + industries: compliance-driven involuntary churn. Account closures + triggered by KYC failures, AML risk reviews, and fraud suspicion create + churn that is not product-driven and cannot be solved by product + improvements. Separating compliance-driven churn from product/market churn + is essential for accurate diagnosis." additional_triage_questions: - - question: "What percentage of customer departures are compliance-driven (account closures from KYC failures, risk reviews, fraud flags) versus voluntary (customer chose to leave)?" - purpose: "Compliance-driven churn is a regulatory cost, not a product problem. High compliance-driven churn may indicate overly aggressive risk models or poor KYC UX, but the solution lies in compliance process optimization, not product features." - routing_impact: "High compliance-driven churn (>15% of total) routes to KYC/AML process optimization and false positive rate analysis. Voluntary churn routes to standard product-market-fit and competitive analysis." - - question: "Is churn concentrated among customers who never completed full onboarding (abandoned KYC), customers in the first 90 days (activation failure), or established customers (value decay or competitive switch)?" - purpose: "Fintech onboarding has unique friction from KYC/identity verification. Early churn driven by KYC abandonment is a different problem than churn among established users." - routing_impact: "KYC abandonment churn routes to onboarding conversion optimization. Post-activation churn routes to product value and engagement analysis. Established customer churn routes to competitive and pricing analysis." - - question: "Has a banking partner policy change, regulatory update, or compliance process change coincided with the churn increase?" - purpose: "Fintech churn can spike after regulatory changes — new KYC requirements, tighter fraud rules, or banking partner risk appetite changes that restrict product availability." - routing_impact: "Regulatory-coincident churn routes to compliance impact assessment and process adaptation. Non-regulatory churn routes to standard churn diagnosis." + - question: "What percentage of customer departures are compliance-driven (account + closures from KYC failures, risk reviews, fraud flags) versus + voluntary (customer chose to leave)?" + purpose: "Compliance-driven churn is a regulatory cost, not a product problem. + High compliance-driven churn may indicate overly aggressive risk + models or poor KYC UX, but the solution lies in compliance process + optimization, not product features." + routing_impact: "High compliance-driven churn (>15% of total) routes to KYC/AML + process optimization and false positive rate analysis. Voluntary churn + routes to standard product-market-fit and competitive analysis." + - question: "Is churn concentrated among customers who never completed full + onboarding (abandoned KYC), customers in the first 90 days (activation + failure), or established customers (value decay or competitive + switch)?" + purpose: "Fintech onboarding has unique friction from KYC/identity verification. + Early churn driven by KYC abandonment is a different problem than + churn among established users." + routing_impact: "KYC abandonment churn routes to onboarding conversion + optimization. Post-activation churn routes to product value and + engagement analysis. Established customer churn routes to competitive + and pricing analysis." + - question: "Has a banking partner policy change, regulatory update, or compliance + process change coincided with the churn increase?" + purpose: "Fintech churn can spike after regulatory changes — new KYC + requirements, tighter fraud rules, or banking partner risk appetite + changes that restrict product availability." + routing_impact: "Regulatory-coincident churn routes to compliance impact + assessment and process adaptation. Non-regulatory churn routes to + standard churn diagnosis." diagnosis_weight_shifts: more_likely: - diagnosis: "Compliance friction driving early-lifecycle churn" - reason: "KYC requirements, identity verification failures, and compliance-mandated account restrictions create friction that does not exist in unregulated products. This is the most common and most under-diagnosed fintech churn driver." + reason: "KYC requirements, identity verification failures, and + compliance-mandated account restrictions create friction that does + not exist in unregulated products. This is the most common and most + under-diagnosed fintech churn driver." - diagnosis: "Trust breach accelerating departure" - reason: "Financial services are trust-dependent. A single incident — unauthorized charge, account freeze, data concern — drives churn faster in fintech than in other industries because money is involved." + reason: "Financial services are trust-dependent. A single incident — + unauthorized charge, account freeze, data concern — drives churn + faster in fintech than in other industries because money is + involved." less_likely: - diagnosis: "Feature gap driving churn" - reason: "Fintech customers rarely leave because of missing features — they leave because of broken trust, better rates, regulatory friction, or competitive switching incentives. Feature gaps are over-diagnosed as churn drivers." + reason: "Fintech customers rarely leave because of missing features — they leave + because of broken trust, better rates, regulatory friction, or + competitive switching incentives. Feature gaps are over-diagnosed as + churn drivers." fintech_specific_diagnoses: - name: "Compliance-driven involuntary churn" - description: "Customer accounts are being closed or restricted at rates that exceed industry norms due to overly aggressive fraud detection, unnecessarily broad risk review criteria, or banking partner risk appetite restrictions. The company is losing legitimate customers to compliance processes designed to catch bad actors." + description: "Customer accounts are being closed or restricted at rates that + exceed industry norms due to overly aggressive fraud detection, + unnecessarily broad risk review criteria, or banking partner risk + appetite restrictions. The company is losing legitimate customers to + compliance processes designed to catch bad actors." symptoms: - - "Account closure rate exceeds 3% monthly, with majority classified as compliance-driven" - - "False positive rate on fraud detection exceeds 90% (legitimate transactions flagged as suspicious)" - - "Customer complaints about account freezes, transaction declines, or identity verification failures are the #1 support category" - - "Banking partner has recently tightened risk criteria or expanded restricted categories" - routes_to_skills: ["systems-thinking", "kaizen-bpr", "trust-equation"] - routes_to_templates: ["action-plan", "incident-postmortem"] + - "Account closure rate exceeds 3% monthly, with majority classified + as compliance-driven" + - "False positive rate on fraud detection exceeds 90% (legitimate + transactions flagged as suspicious)" + - "Customer complaints about account freezes, transaction declines, or + identity verification failures are the #1 support category" + - "Banking partner has recently tightened risk criteria or expanded + restricted categories" + routes_to_skills: [ "systems-thinking", "kaizen-bpr", "trust-equation" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] - name: "Trust-driven voluntary churn cascade" - description: "A trust-damaging event (security incident, publicized regulatory action, data breach, widespread account freezes) has triggered an accelerating wave of voluntary departures. In fintech, trust erosion spreads virally — customers see others leaving and conclude they should leave too." + description: "A trust-damaging event (security incident, publicized regulatory + action, data breach, widespread account freezes) has triggered an + accelerating wave of voluntary departures. In fintech, trust erosion + spreads virally — customers see others leaving and conclude they + should leave too." symptoms: - "Churn rate doubles or triples within 30 days of a specific event" - - "Social media and app store reviews reference a specific trust-breaking incident" - - "Direct deposit migrations away from the platform accelerating (the strongest signal of primary banking relationship abandonment)" - - "New customer acquisition simultaneously declining as negative word-of-mouth spreads" - routes_to_skills: ["trust-equation", "black-swans", "emotional-intelligence"] - routes_to_templates: ["incident-postmortem", "risk-assessment-brief"] + - "Social media and app store reviews reference a specific + trust-breaking incident" + - "Direct deposit migrations away from the platform accelerating (the + strongest signal of primary banking relationship abandonment)" + - "New customer acquisition simultaneously declining as negative + word-of-mouth spreads" + routes_to_skills: [ "trust-equation", "black-swans", "emotional-intelligence" ] + routes_to_templates: [ "incident-postmortem", "risk-assessment-brief" ] sector_red_flags: - - "Account closures exceeding new account openings for any sustained period — the business is shrinking at the customer level." - - "Direct deposit migration rate increasing — customers moving their primary banking relationship is the most consequential churn signal in neobanking." - - "Churn coinciding with a regulatory examination or enforcement action — indicates the event has become public knowledge and is affecting customer confidence." + - "Account closures exceeding new account openings for any sustained + period — the business is shrinking at the customer level." + - "Direct deposit migration rate increasing — customers moving their + primary banking relationship is the most consequential churn signal in + neobanking." + - "Churn coinciding with a regulatory examination or enforcement action — + indicates the event has become public knowledge and is affecting + customer confidence." # ───────────────────────────────────────────── # 2. GROWTH STALL DIAGNOSIS @@ -85,49 +139,105 @@ diagnostic_rules: - diagnostic: "growth-stall-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Fintech growth stalls have regulatory dimensions that other industries do not. Growth can stall because of licensing constraints (cannot enter new states without new licenses), banking partner capacity limits (partner bank's own regulatory capital constrains volume), or regulatory enforcement (consent order restricting new customer acquisition). The growth stall diagnostic must separate market-driven stalls from regulation-driven stalls." + adaptation_rationale: "Fintech growth stalls have regulatory dimensions that + other industries do not. Growth can stall because of licensing constraints + (cannot enter new states without new licenses), banking partner capacity + limits (partner bank's own regulatory capital constrains volume), or + regulatory enforcement (consent order restricting new customer + acquisition). The growth stall diagnostic must separate market-driven + stalls from regulation-driven stalls." additional_triage_questions: - - question: "Is the growth stall geographically constrained — are you growing in states where you hold licenses but stalling in states where you lack them?" - purpose: "State-by-state licensing requirements create geographic growth ceilings that are regulatory, not market-driven. This is the most common fintech growth constraint that is misdiagnosed as a marketing problem." - routing_impact: "Geographic constraint routes to licensing strategy and regulatory expansion planning. Uniform stall across licensed states routes to product/market analysis." - - question: "Has your banking partner imposed new volume limits, customer type restrictions, or compliance requirements that constrain onboarding capacity?" - purpose: "Banking partner constraints are a unique fintech growth ceiling. Partners facing their own regulatory pressure may restrict the fintech's ability to onboard new customers." - routing_impact: "Partner-constrained growth routes to partnership diversification and charter strategy. Non-partner-constrained growth routes to standard growth diagnosis." - - question: "Are you approaching a regulatory threshold (number of customers, transaction volume, assets) that triggers enhanced regulatory requirements?" - purpose: "Certain regulatory thresholds trigger step-function compliance cost increases — e.g., BSA/AML requirements intensify at specific transaction volume thresholds; SEC RIA registration is required above $100M AUM." - routing_impact: "Threshold proximity routes to compliance infrastructure planning and scenario-planning for cost step-ups. Non-threshold-related stall routes to standard market analysis." + - question: "Is the growth stall geographically constrained — are you growing in + states where you hold licenses but stalling in states where you lack + them?" + purpose: "State-by-state licensing requirements create geographic growth + ceilings that are regulatory, not market-driven. This is the most + common fintech growth constraint that is misdiagnosed as a marketing + problem." + routing_impact: "Geographic constraint routes to licensing strategy and + regulatory expansion planning. Uniform stall across licensed states + routes to product/market analysis." + - question: "Has your banking partner imposed new volume limits, customer type + restrictions, or compliance requirements that constrain onboarding + capacity?" + purpose: "Banking partner constraints are a unique fintech growth ceiling. + Partners facing their own regulatory pressure may restrict the + fintech's ability to onboard new customers." + routing_impact: "Partner-constrained growth routes to partnership + diversification and charter strategy. Non-partner-constrained growth + routes to standard growth diagnosis." + - question: "Are you approaching a regulatory threshold (number of customers, + transaction volume, assets) that triggers enhanced regulatory + requirements?" + purpose: "Certain regulatory thresholds trigger step-function compliance cost + increases — e.g., BSA/AML requirements intensify at specific + transaction volume thresholds; SEC RIA registration is required above + $100M AUM." + routing_impact: "Threshold proximity routes to compliance infrastructure + planning and scenario-planning for cost step-ups. + Non-threshold-related stall routes to standard market analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory ceiling constraining growth" - reason: "Fintech growth stalls frequently have regulatory root causes — licensing limitations, banking partner capacity, compliance infrastructure bottlenecks, or impending regulatory thresholds." + reason: "Fintech growth stalls frequently have regulatory root causes — + licensing limitations, banking partner capacity, compliance + infrastructure bottlenecks, or impending regulatory thresholds." - diagnosis: "Banking partner dependency bottleneck" - reason: "Fintechs that depend on a single banking partner are constrained by that partner's risk appetite, regulatory capital, and compliance capacity. The partner becomes the growth bottleneck." + reason: "Fintechs that depend on a single banking partner are constrained by + that partner's risk appetite, regulatory capital, and compliance + capacity. The partner becomes the growth bottleneck." less_likely: - diagnosis: "Macro-economic demand decline" - reason: "Fintech demand is generally robust — the shift from traditional to digital financial services is a multi-decade secular trend. Growth stalls attributed to 'the market' are usually regulatory, competitive, or execution problems." + reason: "Fintech demand is generally robust — the shift from traditional to + digital financial services is a multi-decade secular trend. Growth + stalls attributed to 'the market' are usually regulatory, + competitive, or execution problems." fintech_specific_diagnoses: - name: "Banking partner dependency bottleneck" - description: "Growth is constrained by the banking partner's capacity, risk appetite, or regulatory standing. The fintech has market demand and product-market fit but cannot onboard customers or process volume because the banking partner has imposed restrictions." + description: "Growth is constrained by the banking partner's capacity, risk + appetite, or regulatory standing. The fintech has market demand and + product-market fit but cannot onboard customers or process volume + because the banking partner has imposed restrictions." symptoms: - - "Marketing generates qualified leads that cannot be converted because onboarding is paused or throttled" - - "Banking partner has communicated volume caps, customer type restrictions, or enhanced compliance requirements" - - "Banking partner has received a regulatory order, consent agreement, or MRA that affects its fintech programs" - - "Competitor fintechs using different banking partners are growing while you are stalling" - routes_to_skills: ["scenario-planning", "prisoners-dilemma-and-cooperation", "coalition-and-partnership-games"] - routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + - "Marketing generates qualified leads that cannot be converted + because onboarding is paused or throttled" + - "Banking partner has communicated volume caps, customer type + restrictions, or enhanced compliance requirements" + - "Banking partner has received a regulatory order, consent agreement, + or MRA that affects its fintech programs" + - "Competitor fintechs using different banking partners are growing + while you are stalling" + routes_to_skills: + [ + "scenario-planning", + "prisoners-dilemma-and-cooperation", + "coalition-and-partnership-games" + ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] - name: "License gap constraining addressable market" - description: "The company has product-market fit in licensed states but cannot expand because it lacks licenses in target states. The growth ceiling is regulatory, not commercial — demand exists in unlicensed states but cannot be served." + description: "The company has product-market fit in licensed states but cannot + expand because it lacks licenses in target states. The growth ceiling + is regulatory, not commercial — demand exists in unlicensed states but + cannot be served." symptoms: - - "Strong growth metrics in existing markets with no sign of saturation" - - "Inbound customer interest from states where the company is not licensed" - - "Competitors with broader licensing are gaining market share in the unlicensed states" - - "License applications are pending but regulatory approval timelines extend 6-18 months" - routes_to_skills: ["first-mover-strategy", "scenario-planning"] - routes_to_templates: ["market-opportunity-summary", "action-plan"] + - "Strong growth metrics in existing markets with no sign of + saturation" + - "Inbound customer interest from states where the company is not + licensed" + - "Competitors with broader licensing are gaining market share in the + unlicensed states" + - "License applications are pending but regulatory approval timelines + extend 6-18 months" + routes_to_skills: [ "first-mover-strategy", "scenario-planning" ] + routes_to_templates: [ "market-opportunity-summary", "action-plan" ] sector_red_flags: - - "Banking partner requesting 60-day review of the fintech relationship — often a precursor to termination or significant restriction." - - "Multiple state regulators simultaneously requesting information about the company's operations — signals coordinated regulatory scrutiny." - - "Growth rate declining despite increasing marketing spend — suggests a structural constraint (regulatory, partner, or infrastructure) rather than a demand problem." + - "Banking partner requesting 60-day review of the fintech relationship — + often a precursor to termination or significant restriction." + - "Multiple state regulators simultaneously requesting information about + the company's operations — signals coordinated regulatory scrutiny." + - "Growth rate declining despite increasing marketing spend — suggests a + structural constraint (regulatory, partner, or infrastructure) rather + than a demand problem." # ───────────────────────────────────────────── # 3. PRODUCT-MARKET FIT DIAGNOSIS @@ -135,37 +245,80 @@ diagnostic_rules: - diagnostic: "product-market-fit-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Product-market fit in fintech must be evaluated separately from regulatory fit. A product can have strong market demand but fail because the regulatory framework is hostile (as many crypto products discovered in 2022-2024). Conversely, a product with modest market demand can succeed because regulatory barriers protect it from competition. PMF diagnosis must assess both market demand and regulatory viability." + adaptation_rationale: "Product-market fit in fintech must be evaluated + separately from regulatory fit. A product can have strong market demand + but fail because the regulatory framework is hostile (as many crypto + products discovered in 2022-2024). Conversely, a product with modest + market demand can succeed because regulatory barriers protect it from + competition. PMF diagnosis must assess both market demand and regulatory + viability." additional_triage_questions: - - question: "Does the product's regulatory status allow it to operate in its current form long-term, or is there regulatory risk that the product structure may be challenged or prohibited?" - purpose: "Some fintech products achieve apparent PMF while operating in regulatory gray zones. If the regulatory framework is likely to change, apparent PMF is illusory — the market signal is from a product that may not legally exist in its current form." - routing_impact: "Regulatory-uncertain PMF routes to regulatory risk assessment and product restructuring analysis. Regulatory-secure PMF routes to standard scaling playbooks." - - question: "Is customer retention driven by genuine product value or by switching costs created by regulatory friction (KYC requirements at new provider, data portability barriers)?" - purpose: "Fintech retention can be artificially inflated by the KYC burden of switching. If customers stay because switching requires another identity verification process rather than because the product is superior, PMF is weaker than retention metrics suggest." - routing_impact: "Switching-cost-driven retention routes to competitive vulnerability analysis — open banking mandates will eliminate this retention mechanism. Value-driven retention routes to growth investment." + - question: "Does the product's regulatory status allow it to operate in its + current form long-term, or is there regulatory risk that the product + structure may be challenged or prohibited?" + purpose: "Some fintech products achieve apparent PMF while operating in + regulatory gray zones. If the regulatory framework is likely to + change, apparent PMF is illusory — the market signal is from a product + that may not legally exist in its current form." + routing_impact: "Regulatory-uncertain PMF routes to regulatory risk assessment + and product restructuring analysis. Regulatory-secure PMF routes to + standard scaling playbooks." + - question: "Is customer retention driven by genuine product value or by switching + costs created by regulatory friction (KYC requirements at new + provider, data portability barriers)?" + purpose: "Fintech retention can be artificially inflated by the KYC burden of + switching. If customers stay because switching requires another + identity verification process rather than because the product is + superior, PMF is weaker than retention metrics suggest." + routing_impact: "Switching-cost-driven retention routes to competitive + vulnerability analysis — open banking mandates will eliminate this + retention mechanism. Value-driven retention routes to growth + investment." diagnosis_weight_shifts: more_likely: - diagnosis: "PMF exists but regulatory environment is uncertain" - reason: "Many fintech products demonstrate market demand in regulatory gray zones. BNPL, certain crypto products, and earned wage access all showed strong PMF signals while facing evolving regulatory scrutiny." - - diagnosis: "PMF exists for a niche but compliance costs prevent profitable scaling" - reason: "The per-customer compliance cost (KYC, ongoing monitoring) creates a minimum viable customer value that excludes low-value segments. PMF may be real but the unit economics are broken by compliance costs." + reason: "Many fintech products demonstrate market demand in regulatory gray + zones. BNPL, certain crypto products, and earned wage access all + showed strong PMF signals while facing evolving regulatory + scrutiny." + - diagnosis: "PMF exists for a niche but compliance costs prevent profitable + scaling" + reason: "The per-customer compliance cost (KYC, ongoing monitoring) creates a + minimum viable customer value that excludes low-value segments. PMF + may be real but the unit economics are broken by compliance costs." less_likely: - diagnosis: "Product quality failure" - reason: "In fintech, product quality failures (bugs, crashes) are dangerous but rarely the primary PMF issue. The question is usually whether the financial product design is correct, not whether the software works." + reason: "In fintech, product quality failures (bugs, crashes) are dangerous but + rarely the primary PMF issue. The question is usually whether the + financial product design is correct, not whether the software + works." fintech_specific_diagnoses: - name: "Regulatory-dependent PMF" - description: "The product has achieved strong market traction but its regulatory status is uncertain or evolving. If the regulatory framework changes unfavorably, the product may need fundamental restructuring or may become illegal." + description: "The product has achieved strong market traction but its regulatory + status is uncertain or evolving. If the regulatory framework changes + unfavorably, the product may need fundamental restructuring or may + become illegal." symptoms: - - "Strong user growth and engagement metrics in the context of ambiguous or evolving regulation" - - "Regulatory bodies have issued guidance, proposed rules, or enforcement actions affecting similar products" - - "Legal counsel advises that the product's regulatory classification is uncertain" - - "Investors raise regulatory risk as a primary concern despite strong commercial metrics" - routes_to_skills: ["scenario-planning", "swot-pest-analysis", "game-theory-fundamentals"] - routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + - "Strong user growth and engagement metrics in the context of + ambiguous or evolving regulation" + - "Regulatory bodies have issued guidance, proposed rules, or + enforcement actions affecting similar products" + - "Legal counsel advises that the product's regulatory classification + is uncertain" + - "Investors raise regulatory risk as a primary concern despite strong + commercial metrics" + routes_to_skills: [ "scenario-planning", "swot-pest-analysis", "game-theory-fundamentals" ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] sector_red_flags: - - "Product achieves PMF in jurisdictions with light regulation but fails in jurisdictions with strict regulation — suggests the product works only in the absence of regulatory constraints." - - "Customer acquisition is strong but direct deposit adoption (primary banking relationship indicator) is weak — suggests the product is a secondary tool, not a primary financial relationship." - - "NPS is high but only among customers who have not yet experienced a compliance friction event (fraud flag, account review, transaction decline)." + - "Product achieves PMF in jurisdictions with light regulation but fails + in jurisdictions with strict regulation — suggests the product works + only in the absence of regulatory constraints." + - "Customer acquisition is strong but direct deposit adoption (primary + banking relationship indicator) is weak — suggests the product is a + secondary tool, not a primary financial relationship." + - "NPS is high but only among customers who have not yet experienced a + compliance friction event (fraud flag, account review, transaction + decline)." # ───────────────────────────────────────────── # 4. PRICING DIAGNOSIS @@ -173,40 +326,90 @@ diagnostic_rules: - diagnostic: "pricing-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Pricing in fintech is fundamentally different from other industries because regulators set maximum prices for many revenue lines. Interchange is capped, interest rates face usury limits, and fees must comply with UDAP/UDAAP. Pricing diagnosis must begin with regulatory ceiling analysis, then assess competitive positioning within those constraints. The diagnosis must also evaluate whether the current pricing structure is sustainable under anticipated regulatory changes." + adaptation_rationale: "Pricing in fintech is fundamentally different from other + industries because regulators set maximum prices for many revenue lines. + Interchange is capped, interest rates face usury limits, and fees must + comply with UDAP/UDAAP. Pricing diagnosis must begin with regulatory + ceiling analysis, then assess competitive positioning within those + constraints. The diagnosis must also evaluate whether the current pricing + structure is sustainable under anticipated regulatory changes." additional_triage_questions: - - question: "What percentage of your revenue comes from regulated revenue lines (interchange, interest income subject to rate caps, fees subject to UDAP scrutiny) versus unregulated lines (subscription fees, data products, analytics)?" - purpose: "Revenue concentration in regulated lines creates pricing risk — regulatory changes can compress revenue without any commercial recourse. The diagnosis must assess pricing power in the context of regulatory constraints." - routing_impact: "High regulated-revenue concentration (>70%) routes to revenue diversification strategy and regulatory risk assessment. Diversified revenue routes to standard pricing optimization." - - question: "Have any of your fees been identified as potential 'junk fees' under current CFPB guidance, or has any regulatory body questioned the transparency or fairness of your pricing?" - purpose: "CFPB junk fee enforcement is targeting late fees, overdraft fees, and non-sufficient fund fees across the industry. Pricing structures that rely on these revenue lines face regulatory compression." - routing_impact: "Regulatory fee risk routes to immediate pricing restructure with compliance review. No regulatory concern routes to standard pricing optimization." - - question: "How does your pricing compare to the regulatory maximum in each jurisdiction? Are you priced near the ceiling, at midpoint, or well below?" - purpose: "Pricing near regulatory ceilings leaves no room for competitive response and may attract regulatory attention. Pricing well below ceilings may indicate under-pricing or may reflect the appropriate competitive positioning." - routing_impact: "Near-ceiling pricing routes to competitive analysis and regulatory risk review. Below-ceiling pricing routes to standard willingness-to-pay and value-capture analysis." + - question: "What percentage of your revenue comes from regulated revenue lines + (interchange, interest income subject to rate caps, fees subject to + UDAP scrutiny) versus unregulated lines (subscription fees, data + products, analytics)?" + purpose: "Revenue concentration in regulated lines creates pricing risk — + regulatory changes can compress revenue without any commercial + recourse. The diagnosis must assess pricing power in the context of + regulatory constraints." + routing_impact: "High regulated-revenue concentration (>70%) routes to revenue + diversification strategy and regulatory risk assessment. Diversified + revenue routes to standard pricing optimization." + - question: "Have any of your fees been identified as potential 'junk fees' under + current CFPB guidance, or has any regulatory body questioned the + transparency or fairness of your pricing?" + purpose: "CFPB junk fee enforcement is targeting late fees, overdraft fees, and + non-sufficient fund fees across the industry. Pricing structures that + rely on these revenue lines face regulatory compression." + routing_impact: "Regulatory fee risk routes to immediate pricing restructure + with compliance review. No regulatory concern routes to standard + pricing optimization." + - question: "How does your pricing compare to the regulatory maximum in each + jurisdiction? Are you priced near the ceiling, at midpoint, or well + below?" + purpose: "Pricing near regulatory ceilings leaves no room for competitive + response and may attract regulatory attention. Pricing well below + ceilings may indicate under-pricing or may reflect the appropriate + competitive positioning." + routing_impact: "Near-ceiling pricing routes to competitive analysis and + regulatory risk review. Below-ceiling pricing routes to standard + willingness-to-pay and value-capture analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Interchange compression from regulatory or network changes" - reason: "Interchange revenue faces structural compression from Durbin Amendment expansion, PSD2 IFR tightening, and card network rate adjustments. This is the most common pricing pressure in payments fintech." + reason: "Interchange revenue faces structural compression from Durbin Amendment + expansion, PSD2 IFR tightening, and card network rate adjustments. + This is the most common pricing pressure in payments fintech." - diagnosis: "Fee structure under regulatory scrutiny" - reason: "CFPB junk fee initiative, state attorney general enforcement, and class-action litigation are actively targeting fee structures across fintech. Pricing that was standard three years ago may be non-compliant today." + reason: "CFPB junk fee initiative, state attorney general enforcement, and + class-action litigation are actively targeting fee structures across + fintech. Pricing that was standard three years ago may be + non-compliant today." less_likely: - diagnosis: "Over-pricing relative to competition" - reason: "Fintech markets are generally competitive on price. Under-pricing (leaving money on the table through flat-rate models or excessive discounting) is more common than over-pricing." + reason: "Fintech markets are generally competitive on price. Under-pricing + (leaving money on the table through flat-rate models or excessive + discounting) is more common than over-pricing." fintech_specific_diagnoses: - name: "Regulated revenue concentration risk" - description: "The majority of revenue comes from revenue lines subject to regulatory caps or requirements. A regulatory change — interchange cap reduction, interest rate ceiling, fee prohibition — could eliminate a significant portion of revenue without any market-driven alternative." + description: "The majority of revenue comes from revenue lines subject to + regulatory caps or requirements. A regulatory change — interchange cap + reduction, interest rate ceiling, fee prohibition — could eliminate a + significant portion of revenue without any market-driven alternative." symptoms: - - "More than 70% of revenue from interchange, net interest income, or regulated fees" - - "Pending or proposed regulation that would affect the primary revenue line" - - "Revenue per customer declining despite stable or growing customer engagement (regulatory compression, not market compression)" - - "Inability to raise prices because the current price is at or near regulatory maximums" - routes_to_skills: ["pricing-diagnosis", "scenario-planning", "business-model-canvas"] - routes_to_templates: ["unit-economics-snapshot", "risk-assessment-brief"] + - "More than 70% of revenue from interchange, net interest income, or + regulated fees" + - "Pending or proposed regulation that would affect the primary + revenue line" + - "Revenue per customer declining despite stable or growing customer + engagement (regulatory compression, not market compression)" + - "Inability to raise prices because the current price is at or near + regulatory maximums" + routes_to_skills: + - scenario-planning + - business-model-canvas + routes_to_templates: [ "unit-economics-snapshot", "risk-assessment-brief" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - - "Revenue per transaction declining without a corresponding increase in transaction volume — signals take rate compression from regulatory or competitive forces." - - "CFPB, state AG, or card network inquiry specifically about fee structures — the revenue line is under active regulatory review." - - "Banking partner renegotiating revenue share terms — may indicate the partner is absorbing regulatory costs and passing them through." + - "Revenue per transaction declining without a corresponding increase in + transaction volume — signals take rate compression from regulatory or + competitive forces." + - "CFPB, state AG, or card network inquiry specifically about fee + structures — the revenue line is under active regulatory review." + - "Banking partner renegotiating revenue share terms — may indicate the + partner is absorbing regulatory costs and passing them through." # ───────────────────────────────────────────── # 5. FUNDRAISING DIAGNOSIS @@ -214,37 +417,77 @@ diagnostic_rules: - diagnostic: "fundraising-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Fintech fundraising is uniquely affected by regulatory status. Investors evaluate regulatory risk as a primary investment criterion — the company's license status, compliance infrastructure, banking partner stability, and regulatory history directly affect valuation and investability. A fintech with strong metrics but weak regulatory standing will struggle to raise; a fintech with moderate metrics but a bank charter will command a premium." + adaptation_rationale: "Fintech fundraising is uniquely affected by regulatory + status. Investors evaluate regulatory risk as a primary investment + criterion — the company's license status, compliance infrastructure, + banking partner stability, and regulatory history directly affect + valuation and investability. A fintech with strong metrics but weak + regulatory standing will struggle to raise; a fintech with moderate + metrics but a bank charter will command a premium." additional_triage_questions: - - question: "What is your current regulatory status — what licenses do you hold, what applications are pending, and have you received any regulatory orders, MRAs, or enforcement actions?" - purpose: "Regulatory status is a gating criterion for fintech investment. Most institutional investors will not invest in a fintech with unresolved enforcement actions or pending license revocations." - routing_impact: "Clean regulatory status routes to standard fundraising preparation. Regulatory issues route to remediation planning before fundraising — raising with regulatory problems on the record depresses valuation and limits investor pool." - - question: "Can you articulate your regulatory moat — how does your compliance infrastructure, licensing, or charter create durable competitive advantage?" - purpose: "Sophisticated fintech investors view regulatory compliance as a competitive advantage, not just a cost. The ability to articulate regulatory moat demonstrates strategic maturity." - routing_impact: "Strong regulatory narrative routes to fundraising execution. Weak regulatory narrative routes to regulatory strategy development before fundraising." + - question: "What is your current regulatory status — what licenses do you hold, + what applications are pending, and have you received any regulatory + orders, MRAs, or enforcement actions?" + purpose: "Regulatory status is a gating criterion for fintech investment. Most + institutional investors will not invest in a fintech with unresolved + enforcement actions or pending license revocations." + routing_impact: "Clean regulatory status routes to standard fundraising + preparation. Regulatory issues route to remediation planning before + fundraising — raising with regulatory problems on the record depresses + valuation and limits investor pool." + - question: "Can you articulate your regulatory moat — how does your compliance + infrastructure, licensing, or charter create durable competitive + advantage?" + purpose: "Sophisticated fintech investors view regulatory compliance as a + competitive advantage, not just a cost. The ability to articulate + regulatory moat demonstrates strategic maturity." + routing_impact: "Strong regulatory narrative routes to fundraising execution. + Weak regulatory narrative routes to regulatory strategy development + before fundraising." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory risk deterring investors" - reason: "Post-2022, fintech investors are heavily weighting regulatory risk. The wave of consent orders and the Synapse BaaS collapse made regulatory due diligence the primary filter for many fintech-focused VCs." + reason: "Post-2022, fintech investors are heavily weighting regulatory risk. The + wave of consent orders and the Synapse BaaS collapse made regulatory + due diligence the primary filter for many fintech-focused VCs." - diagnosis: "Banking partner instability creating investability concerns" - reason: "Investors now evaluate banking partner risk as company risk. A fintech dependent on a single BaaS provider that is facing its own regulatory issues will struggle to raise regardless of its commercial metrics." + reason: "Investors now evaluate banking partner risk as company risk. A fintech + dependent on a single BaaS provider that is facing its own + regulatory issues will struggle to raise regardless of its + commercial metrics." less_likely: - diagnosis: "Market too small" - reason: "Financial services markets are enormous. The 'market too small' objection in fintech usually means the investor does not believe the company can achieve sufficient market share, not that the market is too small." + reason: "Financial services markets are enormous. The 'market too small' + objection in fintech usually means the investor does not believe the + company can achieve sufficient market share, not that the market is + too small." fintech_specific_diagnoses: - name: "Regulatory risk premium depressing valuation" - description: "The company's commercial metrics warrant a higher valuation, but investors are applying a regulatory risk discount due to uncertain licensing, pending regulatory changes, or banking partner instability." + description: "The company's commercial metrics warrant a higher valuation, but + investors are applying a regulatory risk discount due to uncertain + licensing, pending regulatory changes, or banking partner + instability." symptoms: - - "Investor feedback consistently cites 'regulatory risk' as a primary concern despite strong commercial metrics" - - "Valuation offers are 30-50% below comparable non-regulated technology companies with similar metrics" - - "Investors request extensive regulatory due diligence that extends the fundraising timeline" - - "Term sheets include regulatory-triggered provisions (accelerated repayment, valuation adjustments, additional board seats if enforcement actions occur)" - routes_to_skills: ["scenario-planning", "competitive-negotiation", "trust-equation"] - routes_to_templates: ["fundraising-deck-outline", "due-diligence-checklist"] + - "Investor feedback consistently cites 'regulatory risk' as a primary + concern despite strong commercial metrics" + - "Valuation offers are 30-50% below comparable non-regulated + technology companies with similar metrics" + - "Investors request extensive regulatory due diligence that extends + the fundraising timeline" + - "Term sheets include regulatory-triggered provisions (accelerated + repayment, valuation adjustments, additional board seats if + enforcement actions occur)" + routes_to_skills: [ "scenario-planning", "competitive-negotiation", "trust-equation" ] + routes_to_templates: [ "fundraising-deck-outline", "due-diligence-checklist" ] sector_red_flags: - - "Unable to provide a clean regulatory history to investors — any past enforcement actions or consent orders must be disclosed and remediated before fundraising." - - "Banking partner relationship is on a 90-day or shorter contract — investors view this as existential risk." - - "Fundraising during a period of active regulatory examination — examiners' findings could materially change the company's risk profile mid-raise." + - "Unable to provide a clean regulatory history to investors — any past + enforcement actions or consent orders must be disclosed and remediated + before fundraising." + - "Banking partner relationship is on a 90-day or shorter contract — + investors view this as existential risk." + - "Fundraising during a period of active regulatory examination — + examiners' findings could materially change the company's risk profile + mid-raise." # ───────────────────────────────────────────── # 6. REVENUE DIAGNOSIS @@ -252,37 +495,71 @@ diagnostic_rules: - diagnostic: "revenue-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Revenue in fintech decomposes into regulated and unregulated streams with fundamentally different risk profiles and growth dynamics. Interchange revenue is subject to regulatory caps and network rate changes. Interest income is subject to credit cycle risk and rate caps. Fee revenue is subject to UDAP/UDAAP enforcement. Subscription/SaaS-like revenue is largely unregulated. The revenue diagnostic must separately evaluate each stream's health, regulatory risk, and growth potential." + adaptation_rationale: "Revenue in fintech decomposes into regulated and + unregulated streams with fundamentally different risk profiles and growth + dynamics. Interchange revenue is subject to regulatory caps and network + rate changes. Interest income is subject to credit cycle risk and rate + caps. Fee revenue is subject to UDAP/UDAAP enforcement. + Subscription/SaaS-like revenue is largely unregulated. The revenue + diagnostic must separately evaluate each stream's health, regulatory risk, + and growth potential." additional_triage_questions: - - question: "Decompose your revenue by type: interchange/processing fees, net interest income, transaction fees, subscription/platform fees, and other. Which types are growing and which are compressing?" - purpose: "Each fintech revenue type has different regulatory exposure, competitive dynamics, and growth characteristics. A single 'revenue' metric masks critical composition changes." - routing_impact: "Interchange compression routes to diversification strategy. NII decline routes to credit and funding cost analysis. Fee compression routes to UDAP/UDAAP risk review. Subscription growth routes to product expansion strategy." - - question: "Have any recent regulatory changes, card network rate adjustments, or banking partner term changes affected your revenue per transaction?" - purpose: "Fintech revenue can decline due to external regulatory or partner actions rather than market dynamics. Distinguishing externally-imposed revenue compression from market-driven compression changes the response strategy." - routing_impact: "Externally-imposed compression routes to regulatory adaptation and revenue diversification. Market-driven compression routes to competitive analysis and pricing optimization." + - question: "Decompose your revenue by type: interchange/processing fees, net + interest income, transaction fees, subscription/platform fees, and + other. Which types are growing and which are compressing?" + purpose: "Each fintech revenue type has different regulatory exposure, + competitive dynamics, and growth characteristics. A single 'revenue' + metric masks critical composition changes." + routing_impact: "Interchange compression routes to diversification strategy. NII + decline routes to credit and funding cost analysis. Fee compression + routes to UDAP/UDAAP risk review. Subscription growth routes to + product expansion strategy." + - question: "Have any recent regulatory changes, card network rate adjustments, or + banking partner term changes affected your revenue per transaction?" + purpose: "Fintech revenue can decline due to external regulatory or partner + actions rather than market dynamics. Distinguishing externally-imposed + revenue compression from market-driven compression changes the + response strategy." + routing_impact: "Externally-imposed compression routes to regulatory adaptation + and revenue diversification. Market-driven compression routes to + competitive analysis and pricing optimization." diagnosis_weight_shifts: more_likely: - diagnosis: "Interchange/regulatory compression eroding transaction revenue" - reason: "Structural interchange compression from Durbin Amendment expansion proposals, PSD2 IFR, and card network rate adjustments is the most common revenue challenge in payments fintech." + reason: "Structural interchange compression from Durbin Amendment expansion + proposals, PSD2 IFR, and card network rate adjustments is the most + common revenue challenge in payments fintech." - diagnosis: "Credit cycle deterioration compressing net interest income" - reason: "Rising default rates consume NIM. Lending fintechs that originate during benign credit conditions face revenue compression when the cycle turns." + reason: "Rising default rates consume NIM. Lending fintechs that originate + during benign credit conditions face revenue compression when the + cycle turns." less_likely: - diagnosis: "Pricing too low" - reason: "Fintech pricing is often at or near regulatory ceilings. Under-pricing is less common than in SaaS because regulatory frameworks often define the pricing landscape." + reason: "Fintech pricing is often at or near regulatory ceilings. Under-pricing + is less common than in SaaS because regulatory frameworks often + define the pricing landscape." fintech_specific_diagnoses: - name: "Credit cycle revenue compression" - description: "Rising default rates are consuming the net interest margin, compressing lending revenue even as origination volume grows. The revenue problem is a credit quality problem, not a pricing or volume problem." + description: "Rising default rates are consuming the net interest margin, + compressing lending revenue even as origination volume grows. The + revenue problem is a credit quality problem, not a pricing or volume + problem." symptoms: - - "Loan origination volume growing but net lending revenue declining or flat" + - "Loan origination volume growing but net lending revenue declining + or flat" - "Default rate increasing across recent vintages" - "Provision for credit losses increasing as percentage of revenue" - - "Warehouse lender or securitization counterparty requesting enhanced credit data or tightening advance rates" - routes_to_skills: ["scenario-planning", "black-swans", "balanced-scorecard"] - routes_to_templates: ["unit-economics-snapshot", "risk-assessment-brief"] + - "Warehouse lender or securitization counterparty requesting enhanced + credit data or tightening advance rates" + routes_to_skills: [ "scenario-planning", "black-swans", "balanced-scorecard" ] + routes_to_templates: [ "unit-economics-snapshot", "risk-assessment-brief" ] sector_red_flags: - - "Revenue per transaction declining for three consecutive quarters — signals structural take rate compression." - - "Net interest margin declining while origination volume grows — classic credit deterioration pattern." - - "Revenue concentration in a single stream above 80% — existential risk from regulatory change affecting that stream." + - "Revenue per transaction declining for three consecutive quarters — + signals structural take rate compression." + - "Net interest margin declining while origination volume grows — classic + credit deterioration pattern." + - "Revenue concentration in a single stream above 80% — existential risk + from regulatory change affecting that stream." # ───────────────────────────────────────────── # 7. COMPETITIVE THREAT DIAGNOSIS @@ -290,46 +567,95 @@ diagnostic_rules: - diagnostic: "competitive-threat-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Competitive threats in fintech include a category absent from other industries: regulatory-enabled competition. Open banking mandates (PSD2, Section 1033) allow competitors to access customer data, demolishing data moats. New charter types (fintech charter proposals, ILC charters) allow competitors to access banking capabilities. Big tech companies (Apple, Google, Amazon) can enter financial services by leveraging existing trust, distribution, and regulatory relationships. Regulatory changes do not just affect the company — they reshape the competitive landscape." + adaptation_rationale: "Competitive threats in fintech include a category absent + from other industries: regulatory-enabled competition. Open banking + mandates (PSD2, Section 1033) allow competitors to access customer data, + demolishing data moats. New charter types (fintech charter proposals, ILC + charters) allow competitors to access banking capabilities. Big tech + companies (Apple, Google, Amazon) can enter financial services by + leveraging existing trust, distribution, and regulatory relationships. + Regulatory changes do not just affect the company — they reshape the + competitive landscape." additional_triage_questions: - - question: "Is the competitive threat from a peer fintech, a traditional bank launching digital products, big tech entering your space (Apple Pay, Google Wallet, Amazon Lending), or a regulatory change enabling new types of competitors?" - purpose: "Each threat type requires a different response and has different dynamics. Peer fintech competition is familiar; big tech entry is existential; regulatory-enabled competition is structural." - routing_impact: "Peer fintech routes to differentiation strategy. Traditional bank digital entry routes to speed-and-UX advantage analysis. Big tech entry routes to niche defensibility and regulatory advantage analysis. Regulatory-enabled competition routes to strategic repositioning." - - question: "Has a regulatory change (open banking mandate, new license type, fee cap change) directly enabled or empowered a competitor?" - purpose: "Regulatory changes can overnight transform the competitive landscape. PSD2 open banking enabled a wave of new payment initiation services in Europe. Similar dynamics are emerging in the US." - routing_impact: "Regulatory-enabled threat routes to regulatory strategy and differentiation beyond data access. Non-regulatory threat routes to standard competitive analysis." + - question: "Is the competitive threat from a peer fintech, a traditional bank + launching digital products, big tech entering your space (Apple Pay, + Google Wallet, Amazon Lending), or a regulatory change enabling new + types of competitors?" + purpose: "Each threat type requires a different response and has different + dynamics. Peer fintech competition is familiar; big tech entry is + existential; regulatory-enabled competition is structural." + routing_impact: "Peer fintech routes to differentiation strategy. Traditional + bank digital entry routes to speed-and-UX advantage analysis. Big tech + entry routes to niche defensibility and regulatory advantage analysis. + Regulatory-enabled competition routes to strategic repositioning." + - question: "Has a regulatory change (open banking mandate, new license type, fee + cap change) directly enabled or empowered a competitor?" + purpose: "Regulatory changes can overnight transform the competitive landscape. + PSD2 open banking enabled a wave of new payment initiation services in + Europe. Similar dynamics are emerging in the US." + routing_impact: "Regulatory-enabled threat routes to regulatory strategy and + differentiation beyond data access. Non-regulatory threat routes to + standard competitive analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Big tech entry into financial services" - reason: "Apple (Apple Card, Apple Savings, Apple Pay Later), Google (Google Wallet, Plex banking), and Amazon (Amazon Lending, Amazon Pay) are actively expanding in fintech. Their distribution and trust advantages are existential threats to standalone fintechs." + reason: "Apple (Apple Card, Apple Savings, Apple Pay Later), Google (Google + Wallet, Plex banking), and Amazon (Amazon Lending, Amazon Pay) are + actively expanding in fintech. Their distribution and trust + advantages are existential threats to standalone fintechs." - diagnosis: "Regulatory change enabling new competition" - reason: "Open banking mandates (PSD2, Section 1033) are structurally increasing competition by requiring data portability. Fintechs that relied on data lock-in for retention face new competitive dynamics." + reason: "Open banking mandates (PSD2, Section 1033) are structurally increasing + competition by requiring data portability. Fintechs that relied on + data lock-in for retention face new competitive dynamics." less_likely: - diagnosis: "Price-based competitive displacement" - reason: "In fintech, competition rarely occurs on price alone because regulatory costs create a floor. The competitive threat is typically about distribution, trust, UX, and product breadth rather than price." + reason: "In fintech, competition rarely occurs on price alone because regulatory + costs create a floor. The competitive threat is typically about + distribution, trust, UX, and product breadth rather than price." fintech_specific_diagnoses: - name: "Big tech financial services entry" - description: "A major technology platform (Apple, Google, Amazon, Meta) has launched or announced a financial product that directly competes with the company's core offering. The platform's existing user base, brand trust, and distribution advantages create a competitive threat that cannot be addressed through product features alone." + description: "A major technology platform (Apple, Google, Amazon, Meta) has + launched or announced a financial product that directly competes with + the company's core offering. The platform's existing user base, brand + trust, and distribution advantages create a competitive threat that + cannot be addressed through product features alone." symptoms: - - "Major tech platform launches a competing financial product (Apple Savings, Google Wallet expansion, Amazon Pay expansion)" - - "Customer acquisition costs increasing as the platform's free or subsidized offering attracts price-sensitive customers" - - "Win rate declining in customer segments that overlap with the platform's user base" - - "Media coverage shifting from 'fintech vs. banks' to 'fintech vs. big tech'" - routes_to_skills: ["porters-five-forces", "blue-ocean-strategy", "disruptive-innovation"] - routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + - "Major tech platform launches a competing financial product (Apple + Savings, Google Wallet expansion, Amazon Pay expansion)" + - "Customer acquisition costs increasing as the platform's free or + subsidized offering attracts price-sensitive customers" + - "Win rate declining in customer segments that overlap with the + platform's user base" + - "Media coverage shifting from 'fintech vs. banks' to 'fintech vs. + big tech'" + routes_to_skills: [ "porters-five-forces", "blue-ocean-strategy", "disruptive-innovation" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] - name: "Open banking regulatory disruption" - description: "Open banking mandates (PSD2 in EU, Section 1033 in US) are enabling competitors to access customer financial data that was previously proprietary. Data-based moats are being demolished by regulation, requiring new sources of competitive advantage." + description: "Open banking mandates (PSD2 in EU, Section 1033 in US) are + enabling competitors to access customer financial data that was + previously proprietary. Data-based moats are being demolished by + regulation, requiring new sources of competitive advantage." symptoms: - - "New competitors emerging that leverage open banking APIs to offer aggregation, comparison, or switching services" - - "Customer data portability reducing switching costs that previously protected retention" - - "API compliance costs increasing as open banking mandates require the company to share data with authorized third parties" - - "Competitive analysis reveals competitors using the company's own data feeds as inputs to competing products" - routes_to_skills: ["porters-five-forces", "first-mover-strategy", "scenario-planning"] - routes_to_templates: ["competitive-landscape-brief", "risk-assessment-brief"] + - "New competitors emerging that leverage open banking APIs to offer + aggregation, comparison, or switching services" + - "Customer data portability reducing switching costs that previously + protected retention" + - "API compliance costs increasing as open banking mandates require + the company to share data with authorized third parties" + - "Competitive analysis reveals competitors using the company's own + data feeds as inputs to competing products" + routes_to_skills: [ "porters-five-forces", "first-mover-strategy", "scenario-planning" ] + routes_to_templates: [ "competitive-landscape-brief", "risk-assessment-brief" ] sector_red_flags: - - "Apple, Google, or Amazon announces a product that directly overlaps with the company's core offering — this is the highest-severity competitive event in fintech." - - "Regulatory body announces open banking implementation timeline — the company has a limited window to transition from data-lock-in to value-based retention." - - "Traditional bank launches a digital-only subsidiary targeting the same customer segment with lower fees and FDIC insurance — combining digital UX with banking trust." + - "Apple, Google, or Amazon announces a product that directly overlaps + with the company's core offering — this is the highest-severity + competitive event in fintech." + - "Regulatory body announces open banking implementation timeline — the + company has a limited window to transition from data-lock-in to + value-based retention." + - "Traditional bank launches a digital-only subsidiary targeting the same + customer segment with lower fees and FDIC insurance — combining digital + UX with banking trust." # ───────────────────────────────────────────── # 8. STRATEGIC DRIFT DIAGNOSIS @@ -337,31 +663,66 @@ diagnostic_rules: - diagnostic: "strategic-drift-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Strategic drift in fintech often manifests as mission-compliance divergence — the company's strategic direction pulls away from its compliance infrastructure. Chasing new product lines without obtaining required licenses, entering new markets without regulatory preparation, or pivoting the business model without assessing regulatory implications are fintech-specific forms of strategic drift." + adaptation_rationale: "Strategic drift in fintech often manifests as + mission-compliance divergence — the company's strategic direction pulls + away from its compliance infrastructure. Chasing new product lines without + obtaining required licenses, entering new markets without regulatory + preparation, or pivoting the business model without assessing regulatory + implications are fintech-specific forms of strategic drift." additional_triage_questions: - - question: "Is the company's product strategy outpacing its compliance infrastructure — are you launching or planning products that require regulatory capabilities you have not yet built?" - purpose: "The most dangerous form of strategic drift in fintech is when product ambition exceeds compliance capacity. Launching a lending product without proper licensing or a custody product without adequate security infrastructure is not strategic ambition — it is regulatory drift." - routing_impact: "Compliance gap routes to compliance infrastructure assessment and licensing strategy before further product expansion. Aligned infrastructure routes to standard strategic analysis." + - question: "Is the company's product strategy outpacing its compliance + infrastructure — are you launching or planning products that require + regulatory capabilities you have not yet built?" + purpose: "The most dangerous form of strategic drift in fintech is when product + ambition exceeds compliance capacity. Launching a lending product + without proper licensing or a custody product without adequate + security infrastructure is not strategic ambition — it is regulatory + drift." + routing_impact: "Compliance gap routes to compliance infrastructure assessment + and licensing strategy before further product expansion. Aligned + infrastructure routes to standard strategic analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Strategy outpacing compliance infrastructure" - reason: "Growth-stage fintechs frequently build products faster than they build compliance capabilities. The 'move fast' instinct that serves well in technology companies creates regulatory risk in financial services." + reason: "Growth-stage fintechs frequently build products faster than they build + compliance capabilities. The 'move fast' instinct that serves well + in technology companies creates regulatory risk in financial + services." less_likely: - diagnosis: "Industry disruption causing drift" - reason: "Fintech strategic drift is usually self-inflicted — chasing multiple revenue lines, entering new geographies prematurely, or following competitor moves without strategic rationale." + reason: "Fintech strategic drift is usually self-inflicted — chasing multiple + revenue lines, entering new geographies prematurely, or following + competitor moves without strategic rationale." fintech_specific_diagnoses: - name: "Mission-compliance divergence" - description: "The company's strategy is evolving in directions that strain or exceed its regulatory licenses, compliance infrastructure, or banking partner agreements. Product development is outpacing regulatory preparation, creating growing risk that a product will be launched or scaled without adequate compliance foundation." + description: "The company's strategy is evolving in directions that strain or + exceed its regulatory licenses, compliance infrastructure, or banking + partner agreements. Product development is outpacing regulatory + preparation, creating growing risk that a product will be launched or + scaled without adequate compliance foundation." symptoms: - - "Product roadmap includes features or products that require licenses the company does not hold" - - "Compliance team flagging concerns about planned launches that are being overridden by commercial leadership" - - "Banking partner pushing back on new product proposals as outside the scope of the partnership agreement" - - "Legal counsel identifying gaps between current regulatory permissions and planned activities" - routes_to_skills: ["strategic-thinking-and-alignment", "balanced-scorecard", "scenario-planning"] - routes_to_templates: ["quarterly-strategic-review", "risk-assessment-brief"] + - "Product roadmap includes features or products that require licenses + the company does not hold" + - "Compliance team flagging concerns about planned launches that are + being overridden by commercial leadership" + - "Banking partner pushing back on new product proposals as outside + the scope of the partnership agreement" + - "Legal counsel identifying gaps between current regulatory + permissions and planned activities" + routes_to_skills: + [ + "strategic-thinking-and-alignment", + "balanced-scorecard", + "scenario-planning" + ] + routes_to_templates: [ "quarterly-strategic-review", "risk-assessment-brief" ] sector_red_flags: - - "Compliance team reporting to commercial leadership rather than directly to CEO/board — creates structural pressure to subordinate compliance to commercial goals." - - "Product launches occurring without formal compliance sign-off — indicates compliance has been marginalized in the product development process." + - "Compliance team reporting to commercial leadership rather than directly + to CEO/board — creates structural pressure to subordinate compliance to + commercial goals." + - "Product launches occurring without formal compliance sign-off — + indicates compliance has been marginalized in the product development + process." # ───────────────────────────────────────────── # 9. TEAM DYSFUNCTION DIAGNOSIS @@ -369,32 +730,66 @@ diagnostic_rules: - diagnostic: "team-dysfunction-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "The most common and consequential team dysfunction in fintech is the growth-compliance tension. Product and growth teams view compliance as an obstacle; compliance teams view growth teams as reckless. This tension is productive when managed (compliance constraints force creative solutions) and destructive when unmanaged (compliance is bypassed or growth is paralyzed). Second-order dysfunction arises from the emotional burden of handling customer financial distress — compliance and support teams experience burnout at higher rates." + adaptation_rationale: "The most common and consequential team dysfunction in + fintech is the growth-compliance tension. Product and growth teams view + compliance as an obstacle; compliance teams view growth teams as reckless. + This tension is productive when managed (compliance constraints force + creative solutions) and destructive when unmanaged (compliance is bypassed + or growth is paralyzed). Second-order dysfunction arises from the + emotional burden of handling customer financial distress — compliance and + support teams experience burnout at higher rates." additional_triage_questions: - - question: "Is there active tension between the growth/product team and the compliance/legal team? How are disagreements about regulatory risk resolved?" - purpose: "Growth-compliance tension is the defining team dynamic in fintech. The resolution mechanism — who wins when growth wants to launch a product that compliance flags as risky — reveals the company's true risk culture." - routing_impact: "Unresolved growth-compliance tension routes to organizational design and decision rights framework. Healthy tension with clear resolution mechanism routes to standard team optimization." + - question: "Is there active tension between the growth/product team and the + compliance/legal team? How are disagreements about regulatory risk + resolved?" + purpose: "Growth-compliance tension is the defining team dynamic in fintech. The + resolution mechanism — who wins when growth wants to launch a product + that compliance flags as risky — reveals the company's true risk + culture." + routing_impact: "Unresolved growth-compliance tension routes to organizational + design and decision rights framework. Healthy tension with clear + resolution mechanism routes to standard team optimization." diagnosis_weight_shifts: more_likely: - diagnosis: "Growth-compliance cultural divide" - reason: "Fintech companies that hire separately from tech (for growth roles) and banking (for compliance roles) create cultural divides. The two groups operate with different risk tolerances, vocabularies, and success metrics." + reason: "Fintech companies that hire separately from tech (for growth roles) and + banking (for compliance roles) create cultural divides. The two + groups operate with different risk tolerances, vocabularies, and + success metrics." less_likely: - diagnosis: "Individual performance issues" - reason: "Apparent individual underperformance in fintech compliance or operations roles is often a system-level problem — inadequate tooling, unclear authority, or conflicting priorities." + reason: "Apparent individual underperformance in fintech compliance or + operations roles is often a system-level problem — inadequate + tooling, unclear authority, or conflicting priorities." fintech_specific_diagnoses: - name: "Compliance team burnout and attrition" - description: "The compliance, risk, and BSA/AML team is experiencing high turnover due to workload, inadequate tooling, organizational marginalization, or the emotional toll of financial crimes investigation. Compliance team instability creates regulatory risk that cascades through the organization." + description: "The compliance, risk, and BSA/AML team is experiencing high + turnover due to workload, inadequate tooling, organizational + marginalization, or the emotional toll of financial crimes + investigation. Compliance team instability creates regulatory risk + that cascades through the organization." symptoms: - "Compliance team turnover exceeding 25% annually" - - "BSA officer or CCO departure — the most consequential single-person risk in fintech" - - "Regulatory reporting delays or quality degradation as experienced staff depart" - - "Compliance team members expressing frustration that their concerns are not heard by leadership" - routes_to_skills: ["trust-equation", "emotional-intelligence", "strategic-thinking-and-alignment"] - routes_to_templates: ["team-health-check", "action-plan"] + - "BSA officer or CCO departure — the most consequential single-person + risk in fintech" + - "Regulatory reporting delays or quality degradation as experienced + staff depart" + - "Compliance team members expressing frustration that their concerns + are not heard by leadership" + routes_to_skills: + [ + "trust-equation", + "emotional-intelligence", + "strategic-thinking-and-alignment" + ] + routes_to_templates: [ "team-health-check", "action-plan" ] sector_red_flags: - - "BSA officer or Chief Compliance Officer resignation — regulators view this as a red flag that triggers enhanced examination." - - "Compliance team being asked to 'find a way to approve' products or customers that fail standard risk criteria." - - "Growth team referring to compliance as 'the Department of No' — indicates a cultural divide that creates regulatory risk." + - "BSA officer or Chief Compliance Officer resignation — regulators view + this as a red flag that triggers enhanced examination." + - "Compliance team being asked to 'find a way to approve' products or + customers that fail standard risk criteria." + - "Growth team referring to compliance as 'the Department of No' — + indicates a cultural divide that creates regulatory risk." # ───────────────────────────────────────────── # 10. COFOUNDER CONFLICT DIAGNOSIS @@ -402,21 +797,41 @@ diagnostic_rules: - diagnostic: "cofounder-conflict-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Co-founder conflict in fintech often centers on risk appetite — one founder wants aggressive growth while the other prioritizes compliance conservatism. This is a structurally different conflict than technical-vs-commercial disagreements because the downside of getting it wrong includes personal legal liability (BSA officers and compliance officers can face individual criminal charges for willful compliance failures)." + adaptation_rationale: "Co-founder conflict in fintech often centers on risk + appetite — one founder wants aggressive growth while the other prioritizes + compliance conservatism. This is a structurally different conflict than + technical-vs-commercial disagreements because the downside of getting it + wrong includes personal legal liability (BSA officers and compliance + officers can face individual criminal charges for willful compliance + failures)." additional_triage_questions: - - question: "Does the conflict center on risk tolerance — specifically, does one founder want to move faster than the other believes is safe from a regulatory perspective?" - purpose: "Risk appetite disagreements in fintech carry legal weight. The co-founder advocating caution may be protecting the company from enforcement actions; the co-founder advocating speed may be protecting the company from running out of runway." - routing_impact: "Risk appetite conflict routes to regulatory risk framework development and explicit risk tolerance documentation. Non-regulatory conflict routes to standard co-founder mediation." + - question: "Does the conflict center on risk tolerance — specifically, does one + founder want to move faster than the other believes is safe from a + regulatory perspective?" + purpose: "Risk appetite disagreements in fintech carry legal weight. The + co-founder advocating caution may be protecting the company from + enforcement actions; the co-founder advocating speed may be protecting + the company from running out of runway." + routing_impact: "Risk appetite conflict routes to regulatory risk framework + development and explicit risk tolerance documentation. Non-regulatory + conflict routes to standard co-founder mediation." diagnosis_weight_shifts: more_likely: - diagnosis: "Risk appetite divergence amplified by personal legal exposure" - reason: "In fintech, the co-founder who holds compliance responsibilities (BSA officer, CCO role) faces personal legal liability for compliance failures. This asymmetric risk exposure amplifies normal disagreements into existential conflicts." + reason: "In fintech, the co-founder who holds compliance responsibilities (BSA + officer, CCO role) faces personal legal liability for compliance + failures. This asymmetric risk exposure amplifies normal + disagreements into existential conflicts." less_likely: - diagnosis: "Equity/compensation dispute" - reason: "Co-founder conflicts in fintech more commonly stem from strategic disagreements about regulatory approach than from compensation disputes." + reason: "Co-founder conflicts in fintech more commonly stem from strategic + disagreements about regulatory approach than from compensation + disputes." fintech_specific_diagnoses: [] sector_red_flags: - - "Co-founder who serves as BSA officer or CCO expressing concern about personal liability exposure — this person has a legal obligation to escalate compliance concerns and may resign to protect themselves." + - "Co-founder who serves as BSA officer or CCO expressing concern about + personal liability exposure — this person has a legal obligation to + escalate compliance concerns and may resign to protect themselves." # ───────────────────────────────────────────── # 11. MARKET ENTRY DIAGNOSIS @@ -424,34 +839,68 @@ diagnostic_rules: - diagnostic: "market-entry-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Market entry in fintech is fundamentally a regulatory question before it is a commercial question. Every new market (geographic, product, customer segment) requires regulatory analysis: what licenses are needed, what compliance infrastructure must be built, what is the regulatory approval timeline, and what are the ongoing compliance costs? A fintech that evaluates market entry on commercial attractiveness alone will fail — the regulatory pathway determines feasibility, timeline, and economics." + adaptation_rationale: "Market entry in fintech is fundamentally a regulatory + question before it is a commercial question. Every new market (geographic, + product, customer segment) requires regulatory analysis: what licenses are + needed, what compliance infrastructure must be built, what is the + regulatory approval timeline, and what are the ongoing compliance costs? A + fintech that evaluates market entry on commercial attractiveness alone + will fail — the regulatory pathway determines feasibility, timeline, and + economics." additional_triage_questions: - - question: "What regulatory licenses, approvals, or registrations are required to enter this market, and what is the realistic timeline and cost to obtain them?" - purpose: "Regulatory licensing timelines range from 30 days (some state money transmitter licenses) to 3+ years (bank charter). This is the single most important input to market entry planning in fintech." - routing_impact: "Short licensing timeline (<6 months) routes to standard market entry planning. Long licensing timeline (>12 months) routes to regulatory-first market entry strategy with interim alternatives (partnerships with licensed entities)." - - question: "Are there existing licensed entities (banks, BaaS providers, broker-dealers) through which you could enter the market via partnership rather than obtaining your own license?" - purpose: "Partnership-based market entry is faster but creates dependency. Direct licensing is slower but creates a moat. The choice between these approaches is the fundamental market entry decision in fintech." - routing_impact: "Partnership entry routes to coalition-and-partnership-games and banking partner evaluation. Direct licensing routes to regulatory strategy and capital planning." + - question: "What regulatory licenses, approvals, or registrations are required to + enter this market, and what is the realistic timeline and cost to + obtain them?" + purpose: "Regulatory licensing timelines range from 30 days (some state money + transmitter licenses) to 3+ years (bank charter). This is the single + most important input to market entry planning in fintech." + routing_impact: "Short licensing timeline (<6 months) routes to standard market + entry planning. Long licensing timeline (>12 months) routes to + regulatory-first market entry strategy with interim alternatives + (partnerships with licensed entities)." + - question: "Are there existing licensed entities (banks, BaaS providers, + broker-dealers) through which you could enter the market via + partnership rather than obtaining your own license?" + purpose: "Partnership-based market entry is faster but creates dependency. + Direct licensing is slower but creates a moat. The choice between + these approaches is the fundamental market entry decision in fintech." + routing_impact: "Partnership entry routes to coalition-and-partnership-games and + banking partner evaluation. Direct licensing routes to regulatory + strategy and capital planning." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory barrier as primary entry challenge" - reason: "In fintech, the regulatory barrier IS the market entry challenge. Product-market fit, competitive dynamics, and go-to-market strategy are secondary to the fundamental question: can we legally operate in this market?" + reason: "In fintech, the regulatory barrier IS the market entry challenge. + Product-market fit, competitive dynamics, and go-to-market strategy + are secondary to the fundamental question: can we legally operate in + this market?" less_likely: - diagnosis: "Product readiness as primary barrier" - reason: "Product readiness matters but is solvable with engineering. Regulatory readiness is harder, slower, and more uncertain." + reason: "Product readiness matters but is solvable with engineering. Regulatory + readiness is harder, slower, and more uncertain." fintech_specific_diagnoses: - name: "Regulatory pathway as market entry gating factor" - description: "The target market is commercially attractive but the regulatory pathway is unclear, lengthy, or expensive. The market entry decision depends primarily on regulatory feasibility rather than commercial attractiveness." + description: "The target market is commercially attractive but the regulatory + pathway is unclear, lengthy, or expensive. The market entry decision + depends primarily on regulatory feasibility rather than commercial + attractiveness." symptoms: - - "Market opportunity analysis is compelling but regulatory counsel cannot confirm a clear licensing pathway" - - "Required licenses involve multi-year application processes and multi-million-dollar capital requirements" - - "Competitors have entered the market through regulatory approaches that may not be replicable (grandfathered licenses, special purpose charters)" - - "Regulatory environment in the target market is actively changing, creating uncertainty about which requirements will apply" - routes_to_skills: ["scenario-planning", "first-mover-strategy", "game-theory-fundamentals"] - routes_to_templates: ["market-opportunity-summary", "decision-rationale-memo"] + - "Market opportunity analysis is compelling but regulatory counsel + cannot confirm a clear licensing pathway" + - "Required licenses involve multi-year application processes and + multi-million-dollar capital requirements" + - "Competitors have entered the market through regulatory approaches + that may not be replicable (grandfathered licenses, special purpose + charters)" + - "Regulatory environment in the target market is actively changing, + creating uncertainty about which requirements will apply" + routes_to_skills: [ "scenario-planning", "first-mover-strategy", "game-theory-fundamentals" ] + routes_to_templates: [ "market-opportunity-summary", "decision-rationale-memo" ] sector_red_flags: - - "Planning market entry without regulatory counsel assessment — the most common and most dangerous mistake in fintech expansion." - - "Entering a market based on a regulatory interpretation that has not been tested or confirmed with the relevant regulator." + - "Planning market entry without regulatory counsel assessment — the most + common and most dangerous mistake in fintech expansion." + - "Entering a market based on a regulatory interpretation that has not + been tested or confirmed with the relevant regulator." # ───────────────────────────────────────────── # 12. PARTNERSHIP DIAGNOSIS @@ -459,35 +908,79 @@ diagnostic_rules: - diagnostic: "partnership-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Partnerships in fintech are regulated relationships. Banking partnerships are subject to OCC, FDIC, and Federal Reserve third-party risk management guidance. Card network partnerships are governed by network rules and PCI-DSS requirements. Technology partnerships that handle financial data are subject to GLBA service provider requirements. Partnership diagnosis in fintech must evaluate regulatory compliance of the partnership structure, regulatory risk shared between partners, and the impact of partner regulatory actions on the company." + adaptation_rationale: "Partnerships in fintech are regulated relationships. + Banking partnerships are subject to OCC, FDIC, and Federal Reserve + third-party risk management guidance. Card network partnerships are + governed by network rules and PCI-DSS requirements. Technology + partnerships that handle financial data are subject to GLBA service + provider requirements. Partnership diagnosis in fintech must evaluate + regulatory compliance of the partnership structure, regulatory risk shared + between partners, and the impact of partner regulatory actions on the + company." additional_triage_questions: - - question: "Is your banking partner currently under any regulatory order, MRA, consent agreement, or enhanced supervision that could affect your operations?" - purpose: "A banking partner's regulatory standing directly determines the fintech's operational stability. Partner regulatory issues become the fintech's issues." - routing_impact: "Partner under regulatory action routes to immediate contingency planning and secondary partner evaluation. Clean partner regulatory status routes to standard partnership optimization." - - question: "Is the regulatory responsibility allocation between you and your partner clearly documented, and has it been reviewed by both parties' regulatory counsel?" - purpose: "Ambiguous compliance responsibility in fintech partnerships is the source of most partnership breakdowns. When a regulatory issue arises, both parties must know who is responsible." - routing_impact: "Ambiguous allocation routes to immediate partnership agreement review and compliance responsibility matrix development. Clear allocation routes to standard partnership health assessment." + - question: "Is your banking partner currently under any regulatory order, MRA, + consent agreement, or enhanced supervision that could affect your + operations?" + purpose: "A banking partner's regulatory standing directly determines the + fintech's operational stability. Partner regulatory issues become the + fintech's issues." + routing_impact: "Partner under regulatory action routes to immediate contingency + planning and secondary partner evaluation. Clean partner regulatory + status routes to standard partnership optimization." + - question: "Is the regulatory responsibility allocation between you and your + partner clearly documented, and has it been reviewed by both parties' + regulatory counsel?" + purpose: "Ambiguous compliance responsibility in fintech partnerships is the + source of most partnership breakdowns. When a regulatory issue arises, + both parties must know who is responsible." + routing_impact: "Ambiguous allocation routes to immediate partnership agreement + review and compliance responsibility matrix development. Clear + allocation routes to standard partnership health assessment." diagnosis_weight_shifts: more_likely: - diagnosis: "Banking partner regulatory stress creating operational risk" - reason: "The 2023-2024 wave of regulatory actions against BaaS providers and partner banks demonstrated that partner regulatory risk is the most consequential partnership risk in fintech." + reason: "The 2023-2024 wave of regulatory actions against BaaS providers and + partner banks demonstrated that partner regulatory risk is the most + consequential partnership risk in fintech." less_likely: - diagnosis: "Partnership value misalignment" - reason: "Fintech partnerships are typically structured around regulatory enablement — the value proposition (licensed entity enables unlicensed activities) is usually clear, even when commercial terms are suboptimal." + reason: "Fintech partnerships are typically structured around regulatory + enablement — the value proposition (licensed entity enables + unlicensed activities) is usually clear, even when commercial terms + are suboptimal." fintech_specific_diagnoses: - name: "Banking partner regulatory contagion" - description: "The banking partner is experiencing regulatory pressure that is flowing through to the fintech — operational restrictions, enhanced compliance requirements, volume limitations, or potential relationship termination driven by the bank's regulatory situation rather than the fintech's performance." + description: "The banking partner is experiencing regulatory pressure that is + flowing through to the fintech — operational restrictions, enhanced + compliance requirements, volume limitations, or potential relationship + termination driven by the bank's regulatory situation rather than the + fintech's performance." symptoms: - - "Banking partner imposing new compliance requirements not present in the original partnership agreement" - - "Account opening or transaction processing delays attributable to partner-side compliance reviews" - - "Industry news reporting regulatory actions against the partner bank's fintech programs" - - "Partner bank requesting audit access or compliance data beyond previous requirements" - routes_to_skills: ["prisoners-dilemma-and-cooperation", "scenario-planning", "coalition-and-partnership-games"] - routes_to_templates: ["risk-assessment-brief", "partnership-memo"] + - "Banking partner imposing new compliance requirements not present in + the original partnership agreement" + - "Account opening or transaction processing delays attributable to + partner-side compliance reviews" + - "Industry news reporting regulatory actions against the partner + bank's fintech programs" + - "Partner bank requesting audit access or compliance data beyond + previous requirements" + routes_to_skills: + [ + "prisoners-dilemma-and-cooperation", + "scenario-planning", + "coalition-and-partnership-games" + ] + routes_to_templates: [ "risk-assessment-brief", "partnership-memo" ] sector_red_flags: - - "Banking partner's OCC or FDIC examination results in MRA (Matter Requiring Attention) or MRIA (Matter Requiring Immediate Attention) related to fintech oversight." - - "Banking partner communicating through legal counsel rather than business contacts — indicates the relationship is being managed as a risk rather than a partnership." - - "Multiple fintechs simultaneously receiving restrictive communications from the same banking partner — indicates a systemic regulatory response affecting the partner's entire fintech program." + - "Banking partner's OCC or FDIC examination results in MRA (Matter + Requiring Attention) or MRIA (Matter Requiring Immediate Attention) + related to fintech oversight." + - "Banking partner communicating through legal counsel rather than + business contacts — indicates the relationship is being managed as a + risk rather than a partnership." + - "Multiple fintechs simultaneously receiving restrictive communications + from the same banking partner — indicates a systemic regulatory response + affecting the partner's entire fintech program." # ───────────────────────────────────────────── # 13. LEADERSHIP CRISIS DIAGNOSIS @@ -495,22 +988,41 @@ diagnostic_rules: - diagnostic: "leadership-crisis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Leadership crises in fintech carry regulatory consequences. The departure of a BSA officer, CCO, or any individual with regulatory obligations triggers reporting requirements and regulatory scrutiny. A leadership crisis during a regulatory examination compounds the stress. Leaders who hold personal regulatory designations cannot be replaced as casually as other roles — regulators must approve certain leadership changes." + adaptation_rationale: "Leadership crises in fintech carry regulatory + consequences. The departure of a BSA officer, CCO, or any individual with + regulatory obligations triggers reporting requirements and regulatory + scrutiny. A leadership crisis during a regulatory examination compounds + the stress. Leaders who hold personal regulatory designations cannot be + replaced as casually as other roles — regulators must approve certain + leadership changes." additional_triage_questions: - - question: "Does the leadership crisis involve individuals who hold regulatory designations (BSA officer, CCO, CISO, designated compliance personnel) whose departure triggers regulatory notification requirements?" - purpose: "Regulatory-designated leadership changes require notification to regulators and may trigger enhanced supervision. These are not ordinary personnel changes." - routing_impact: "Regulatory-designated leader departure routes to immediate regulatory notification planning and interim designation of qualified personnel. Non-regulatory leadership routes to standard succession planning." + - question: "Does the leadership crisis involve individuals who hold regulatory + designations (BSA officer, CCO, CISO, designated compliance personnel) + whose departure triggers regulatory notification requirements?" + purpose: "Regulatory-designated leadership changes require notification to + regulators and may trigger enhanced supervision. These are not + ordinary personnel changes." + routing_impact: "Regulatory-designated leader departure routes to immediate + regulatory notification planning and interim designation of qualified + personnel. Non-regulatory leadership routes to standard succession + planning." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory-designated leader departure creating compliance vacuum" - reason: "The loss of a BSA officer, CCO, or other regulatory-designated individual creates immediate compliance risk and requires regulatory notification." + reason: "The loss of a BSA officer, CCO, or other regulatory-designated + individual creates immediate compliance risk and requires regulatory + notification." less_likely: - diagnosis: "General leadership style mismatch" - reason: "Leadership crises in fintech are more often about regulatory stress, compliance disagreements, or personal liability concerns than about leadership style." + reason: "Leadership crises in fintech are more often about regulatory stress, + compliance disagreements, or personal liability concerns than about + leadership style." fintech_specific_diagnoses: [] sector_red_flags: - - "BSA officer or CCO departure without a pre-identified successor — creates a compliance gap that regulators view as a critical deficiency." - - "Multiple compliance-designated personnel departing within a short period — signals systemic cultural or risk issues." + - "BSA officer or CCO departure without a pre-identified successor — + creates a compliance gap that regulators view as a critical deficiency." + - "Multiple compliance-designated personnel departing within a short + period — signals systemic cultural or risk issues." # ───────────────────────────────────────────── # 14. OPERATIONAL CHAOS DIAGNOSIS @@ -518,31 +1030,54 @@ diagnostic_rules: - diagnostic: "operational-chaos-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Operational chaos in fintech carries regulatory consequences that do not exist in other industries. Missed regulatory reporting deadlines, SAR filing backlogs, KYC refresh failures, and transaction monitoring outages are not just operational problems — they are compliance violations that can trigger enforcement actions. The operational chaos diagnostic must prioritize regulatory-deadline operations over discretionary operations." + adaptation_rationale: "Operational chaos in fintech carries regulatory + consequences that do not exist in other industries. Missed regulatory + reporting deadlines, SAR filing backlogs, KYC refresh failures, and + transaction monitoring outages are not just operational problems — they + are compliance violations that can trigger enforcement actions. The + operational chaos diagnostic must prioritize regulatory-deadline + operations over discretionary operations." additional_triage_questions: - - question: "Are any regulatory-deadline operations (SAR filing, CTR filing, state regulatory reporting, audit submissions) currently behind schedule or at risk of missing deadlines?" - purpose: "Regulatory deadlines are non-negotiable. A SAR must be filed within 30 days of detection. CTRs must be filed within 15 days. Missing these deadlines is a compliance violation, not an operational inconvenience." - routing_impact: "Regulatory deadline risk routes to immediate triage and resource reallocation to compliance operations. No deadline risk routes to standard operational improvement." + - question: "Are any regulatory-deadline operations (SAR filing, CTR filing, state + regulatory reporting, audit submissions) currently behind schedule or + at risk of missing deadlines?" + purpose: "Regulatory deadlines are non-negotiable. A SAR must be filed within 30 + days of detection. CTRs must be filed within 15 days. Missing these + deadlines is a compliance violation, not an operational + inconvenience." + routing_impact: "Regulatory deadline risk routes to immediate triage and + resource reallocation to compliance operations. No deadline risk + routes to standard operational improvement." diagnosis_weight_shifts: more_likely: - diagnosis: "Compliance operations drowning growth operations" - reason: "Rapid growth in fintech generates proportional growth in compliance workload (more transactions to monitor, more SARs to file, more KYC to process). When compliance operations cannot scale with growth, both compliance and growth suffer." + reason: "Rapid growth in fintech generates proportional growth in compliance + workload (more transactions to monitor, more SARs to file, more KYC + to process). When compliance operations cannot scale with growth, + both compliance and growth suffer." less_likely: - diagnosis: "Technology infrastructure failure" - reason: "Pure technology failures are usually addressable. Operational chaos in fintech more often stems from the collision of fast-growing transaction volumes and linear-scaling compliance processes." + reason: "Pure technology failures are usually addressable. Operational chaos in + fintech more often stems from the collision of fast-growing + transaction volumes and linear-scaling compliance processes." fintech_specific_diagnoses: - name: "Compliance operations overwhelm" - description: "Transaction volume growth has outpaced the compliance team's capacity to process AML alerts, file SARs, complete KYC reviews, and generate regulatory reports. The compliance backlog creates regulatory risk that threatens the business." + description: "Transaction volume growth has outpaced the compliance team's + capacity to process AML alerts, file SARs, complete KYC reviews, and + generate regulatory reports. The compliance backlog creates regulatory + risk that threatens the business." symptoms: - "SAR filing backlog exceeding 30 days from alert disposition" - "AML alert queue growing faster than the team can review" - "KYC refresh reviews past due for more than 10% of customer base" - "Regulatory reporting submitted late or with known errors" - routes_to_skills: ["kaizen-bpr", "systems-thinking", "eisenhower-matrix"] - routes_to_templates: ["action-plan", "incident-postmortem"] + routes_to_skills: [ "kaizen-bpr", "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] sector_red_flags: - - "SAR filing deadline missed — this is a BSA violation that must be remediated immediately and may require self-reporting to FinCEN." - - "Transaction monitoring system outage lasting more than 24 hours — creates a compliance gap that regulators will examine." + - "SAR filing deadline missed — this is a BSA violation that must be + remediated immediately and may require self-reporting to FinCEN." + - "Transaction monitoring system outage lasting more than 24 hours — + creates a compliance gap that regulators will examine." # ───────────────────────────────────────────── # 15. DECISION PARALYSIS DIAGNOSIS @@ -550,22 +1085,43 @@ diagnostic_rules: - diagnostic: "decision-paralysis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Decision paralysis in fintech is amplified by the irreversibility of regulatory decisions and the personal liability that attaches to financial services decisions. Leaders who face personal legal exposure for compliance failures may become paralyzed by risk aversion. The diagnosis must distinguish between healthy caution (warranted by regulatory risk) and excessive paralysis (preventing necessary business decisions)." + adaptation_rationale: "Decision paralysis in fintech is amplified by the + irreversibility of regulatory decisions and the personal liability that + attaches to financial services decisions. Leaders who face personal legal + exposure for compliance failures may become paralyzed by risk aversion. + The diagnosis must distinguish between healthy caution (warranted by + regulatory risk) and excessive paralysis (preventing necessary business + decisions)." additional_triage_questions: - - question: "Is the paralysis driven by uncertainty about regulatory requirements — specifically, the team cannot decide because they do not know what the rules are?" - purpose: "Regulatory ambiguity is a common source of fintech decision paralysis. When the rules are unclear, conservative leaders wait for clarity while aggressive leaders proceed at risk. Neither is optimal without explicit risk framework." - routing_impact: "Regulatory uncertainty routes to regulatory engagement strategy (proactive outreach to regulators, no-action letter requests, sandbox applications). Non-regulatory paralysis routes to standard decision framework." + - question: "Is the paralysis driven by uncertainty about regulatory requirements + — specifically, the team cannot decide because they do not know what + the rules are?" + purpose: "Regulatory ambiguity is a common source of fintech decision paralysis. + When the rules are unclear, conservative leaders wait for clarity + while aggressive leaders proceed at risk. Neither is optimal without + explicit risk framework." + routing_impact: "Regulatory uncertainty routes to regulatory engagement strategy + (proactive outreach to regulators, no-action letter requests, sandbox + applications). Non-regulatory paralysis routes to standard decision + framework." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory uncertainty freezing strategic decisions" - reason: "Fintech operates in a regulatory environment that changes frequently. Pending regulations, ambiguous guidance, and enforcement pattern shifts create uncertainty that paralyzes strategic planning." + reason: "Fintech operates in a regulatory environment that changes frequently. + Pending regulations, ambiguous guidance, and enforcement pattern + shifts create uncertainty that paralyzes strategic planning." less_likely: - diagnosis: "Insufficient data for decision" - reason: "Fintech companies typically have abundant data (transaction data, customer behavior, financial metrics). Paralysis is rarely about missing data — it is about regulatory uncertainty or risk aversion." + reason: "Fintech companies typically have abundant data (transaction data, + customer behavior, financial metrics). Paralysis is rarely about + missing data — it is about regulatory uncertainty or risk aversion." fintech_specific_diagnoses: [] sector_red_flags: - - "Major strategic decisions delayed more than 6 months citing 'regulatory uncertainty' — may indicate leadership using regulation as an excuse for inaction." - - "No new products launched in 12+ months because compliance review is perpetually incomplete." + - "Major strategic decisions delayed more than 6 months citing 'regulatory + uncertainty' — may indicate leadership using regulation as an excuse for + inaction." + - "No new products launched in 12+ months because compliance review is + perpetually incomplete." # ───────────────────────────────────────────── # 16. HIRING DIAGNOSIS @@ -573,22 +1129,41 @@ diagnostic_rules: - diagnostic: "hiring-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Fintech hiring must address a talent pool that spans two traditionally separate industries — technology and financial services/compliance. The compliance talent market is constrained: experienced BSA officers, CCOs, and regulatory counsel are scarce and expensive. Hiring the wrong compliance leadership has regulatory consequences — regulators evaluate the qualifications of designated compliance personnel." + adaptation_rationale: "Fintech hiring must address a talent pool that spans two + traditionally separate industries — technology and financial + services/compliance. The compliance talent market is constrained: + experienced BSA officers, CCOs, and regulatory counsel are scarce and + expensive. Hiring the wrong compliance leadership has regulatory + consequences — regulators evaluate the qualifications of designated + compliance personnel." additional_triage_questions: - - question: "Are you struggling to hire for compliance, risk, and regulatory roles specifically — BSA officer, CCO, CISO, regulatory counsel?" - purpose: "Compliance talent scarcity is the most common and most consequential hiring challenge in fintech. The talent pool is small, compensation expectations are high, and regulators evaluate the qualifications of designated personnel." - routing_impact: "Compliance hiring difficulty routes to compensation benchmarking against banking (not tech) standards and recruitment strategy for regulated industry talent." + - question: "Are you struggling to hire for compliance, risk, and regulatory roles + specifically — BSA officer, CCO, CISO, regulatory counsel?" + purpose: "Compliance talent scarcity is the most common and most consequential + hiring challenge in fintech. The talent pool is small, compensation + expectations are high, and regulators evaluate the qualifications of + designated personnel." + routing_impact: "Compliance hiring difficulty routes to compensation + benchmarking against banking (not tech) standards and recruitment + strategy for regulated industry talent." diagnosis_weight_shifts: more_likely: - diagnosis: "Compliance talent scarcity constraining growth" - reason: "Experienced BSA officers, CCOs, and financial services regulatory counsel are in high demand across both traditional banking and fintech. Competition for this talent is intense." + reason: "Experienced BSA officers, CCOs, and financial services regulatory + counsel are in high demand across both traditional banking and + fintech. Competition for this talent is intense." less_likely: - diagnosis: "Employer brand weakness" - reason: "Fintech companies generally attract strong talent from both tech and financial services. Hiring challenges are more often about specific skill sets (compliance, regulatory) than general attractiveness." + reason: "Fintech companies generally attract strong talent from both tech and + financial services. Hiring challenges are more often about specific + skill sets (compliance, regulatory) than general attractiveness." fintech_specific_diagnoses: [] sector_red_flags: - - "BSA officer or CCO position vacant for more than 30 days — regulators view this as a critical gap." - - "Compliance staff being hired at below-market compensation (banking market, not tech market) — creates retention risk in the highest-consequence function." + - "BSA officer or CCO position vacant for more than 30 days — regulators + view this as a critical gap." + - "Compliance staff being hired at below-market compensation (banking + market, not tech market) — creates retention risk in the + highest-consequence function." # ───────────────────────────────────────────── # 17. INNOVATION DROUGHT DIAGNOSIS @@ -596,22 +1171,38 @@ diagnostic_rules: - diagnostic: "innovation-drought-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Innovation in fintech is constrained by compliance review processes that can slow product development. The diagnostic must distinguish between genuine innovation drought (no creative ideas) and compliance-bottlenecked innovation (ideas exist but cannot clear regulatory review). The former requires creativity; the latter requires process improvement." + adaptation_rationale: "Innovation in fintech is constrained by compliance review + processes that can slow product development. The diagnostic must + distinguish between genuine innovation drought (no creative ideas) and + compliance-bottlenecked innovation (ideas exist but cannot clear + regulatory review). The former requires creativity; the latter requires + process improvement." additional_triage_questions: - - question: "Is the innovation drought caused by a lack of ideas, or by a compliance review process that prevents ideas from reaching market?" - purpose: "Many fintech companies have innovative ideas that die in compliance review — not because they are non-compliant, but because the review process is slow, under-resourced, or excessively conservative." - routing_impact: "Compliance bottleneck routes to compliance process redesign and 'compliance-in-the-room' product development practice. Genuine idea drought routes to standard innovation frameworks." + - question: "Is the innovation drought caused by a lack of ideas, or by a + compliance review process that prevents ideas from reaching market?" + purpose: "Many fintech companies have innovative ideas that die in compliance + review — not because they are non-compliant, but because the review + process is slow, under-resourced, or excessively conservative." + routing_impact: "Compliance bottleneck routes to compliance process redesign and + 'compliance-in-the-room' product development practice. Genuine idea + drought routes to standard innovation frameworks." diagnosis_weight_shifts: more_likely: - diagnosis: "Compliance review bottleneck suppressing innovation velocity" - reason: "The most common innovation barrier in fintech is not a lack of creativity but a slow, under-resourced, or overly conservative compliance review process that prevents ideas from reaching market." + reason: "The most common innovation barrier in fintech is not a lack of + creativity but a slow, under-resourced, or overly conservative + compliance review process that prevents ideas from reaching market." less_likely: - diagnosis: "Organizational complacency" - reason: "Fintech companies rarely suffer from complacency — the pace of regulatory and competitive change prevents it. Innovation drought is more often structural (compliance bottleneck) than cultural." + reason: "Fintech companies rarely suffer from complacency — the pace of + regulatory and competitive change prevents it. Innovation drought is + more often structural (compliance bottleneck) than cultural." fintech_specific_diagnoses: [] sector_red_flags: - - "Average time from product concept to compliance approval exceeding 6 months — indicates compliance is a bottleneck, not a partner." - - "Compliance team rejecting ideas without suggesting compliant alternatives — indicates a 'Department of No' culture." + - "Average time from product concept to compliance approval exceeding 6 + months — indicates compliance is a bottleneck, not a partner." + - "Compliance team rejecting ideas without suggesting compliant + alternatives — indicates a 'Department of No' culture." # ───────────────────────────────────────────── # 18. CULTURE EROSION DIAGNOSIS @@ -619,31 +1210,65 @@ diagnostic_rules: - diagnostic: "culture-erosion-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Culture erosion in fintech manifests as a divergence between stated values (customer-first, transparency, financial inclusion) and actual behavior (hidden fees, aggressive collections, predatory lending terms). This is not just a culture problem — it is a regulatory risk. UDAP/UDAAP enforcement targets practices that are unfair, deceptive, or abusive, which are often the downstream manifestation of culture erosion." + adaptation_rationale: "Culture erosion in fintech manifests as a divergence + between stated values (customer-first, transparency, financial inclusion) + and actual behavior (hidden fees, aggressive collections, predatory + lending terms). This is not just a culture problem — it is a regulatory + risk. UDAP/UDAAP enforcement targets practices that are unfair, deceptive, + or abusive, which are often the downstream manifestation of culture + erosion." additional_triage_questions: - - question: "Are there practices in the company that leadership would not be comfortable disclosing to a regulator during an examination?" - purpose: "This question cuts directly to culture-compliance alignment. If the answer is yes, the company has a culture problem that is also a regulatory risk." - routing_impact: "Affirmative answer routes to immediate compliance assessment and ethical review. Negative answer routes to standard culture diagnosis." + - question: "Are there practices in the company that leadership would not be + comfortable disclosing to a regulator during an examination?" + purpose: "This question cuts directly to culture-compliance alignment. If the + answer is yes, the company has a culture problem that is also a + regulatory risk." + routing_impact: "Affirmative answer routes to immediate compliance assessment + and ethical review. Negative answer routes to standard culture + diagnosis." diagnosis_weight_shifts: more_likely: - diagnosis: "Revenue pressure eroding ethical standards" - reason: "Fintech companies under growth pressure may adopt practices that extract revenue from customers at the expense of transparency — hidden fees, aggressive upselling, misleading marketing. These are simultaneously culture failures and regulatory violations." + reason: "Fintech companies under growth pressure may adopt practices that + extract revenue from customers at the expense of transparency — + hidden fees, aggressive upselling, misleading marketing. These are + simultaneously culture failures and regulatory violations." less_likely: - diagnosis: "Remote work eroding culture" - reason: "Remote work culture challenges exist in fintech but are not the primary culture erosion driver. Revenue pressure and growth-compliance tension are more consequential." + reason: "Remote work culture challenges exist in fintech but are not the primary + culture erosion driver. Revenue pressure and growth-compliance + tension are more consequential." fintech_specific_diagnoses: - name: "Financial inclusion rhetoric vs. predatory practice" - description: "The company publicly positions itself as promoting financial inclusion but its actual product terms, fee structures, or lending practices disproportionately burden the underbanked populations it claims to serve. The gap between narrative and reality creates both ethical liability and regulatory risk under UDAP/UDAAP and fair lending laws." + description: "The company publicly positions itself as promoting financial + inclusion but its actual product terms, fee structures, or lending + practices disproportionately burden the underbanked populations it + claims to serve. The gap between narrative and reality creates both + ethical liability and regulatory risk under UDAP/UDAAP and fair + lending laws." symptoms: - - "APRs or effective fee rates exceeding 36% for products marketed to underbanked consumers" - - "Internal metrics tracking revenue extraction per customer rather than financial wellbeing outcomes" - - "Marketing emphasizes 'financial inclusion' while product design maximizes fee revenue from financially vulnerable customers" - - "Fair lending analysis identifies disparate impact across protected demographic groups" - routes_to_skills: ["trust-equation", "tough-decision-situations", "defining-and-exploring-problems"] - routes_to_templates: ["risk-assessment-brief", "culture-values-document"] + - "APRs or effective fee rates exceeding 36% for products marketed to + underbanked consumers" + - "Internal metrics tracking revenue extraction per customer rather + than financial wellbeing outcomes" + - "Marketing emphasizes 'financial inclusion' while product design + maximizes fee revenue from financially vulnerable customers" + - "Fair lending analysis identifies disparate impact across protected + demographic groups" + routes_to_skills: + [ + "trust-equation", + "tough-decision-situations", + "defining-and-exploring-problems" + ] + routes_to_templates: [ "risk-assessment-brief", "culture-values-document" ] sector_red_flags: - - "Customer complaint rate to CFPB or state regulators increasing — regulatory complaints are both a culture signal and a regulatory risk indicator." - - "Internal compliance concerns being documented in writing and escalated through formal channels — indicates the compliance team believes informal escalation is insufficient, a serious warning sign." + - "Customer complaint rate to CFPB or state regulators increasing — + regulatory complaints are both a culture signal and a regulatory risk + indicator." + - "Internal compliance concerns being documented in writing and escalated + through formal channels — indicates the compliance team believes + informal escalation is insufficient, a serious warning sign." # ───────────────────────────────────────────── # 19. COMMUNICATION BREAKDOWN DIAGNOSIS @@ -651,22 +1276,43 @@ diagnostic_rules: - diagnostic: "communication-breakdown-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Communication breakdowns in fintech carry regulatory weight because certain communications are legally required. Adverse action notices for credit denials, fee disclosures, privacy notices under GLBA, and breach notification under state laws have specific content, timing, and delivery requirements. Internal communication breakdowns between the compliance team and other functions can lead to regulatory violations." + adaptation_rationale: "Communication breakdowns in fintech carry regulatory + weight because certain communications are legally required. Adverse action + notices for credit denials, fee disclosures, privacy notices under GLBA, + and breach notification under state laws have specific content, timing, + and delivery requirements. Internal communication breakdowns between the + compliance team and other functions can lead to regulatory violations." additional_triage_questions: - - question: "Is the communication breakdown affecting customer-facing regulatory disclosures (fee disclosures, adverse action notices, privacy notices) or internal compliance escalation channels?" - purpose: "Customer-facing disclosure failures are regulatory violations. Internal escalation failures lead to regulatory issues going unaddressed until they become enforcement actions." - routing_impact: "Customer disclosure failures route to immediate compliance remediation and disclosure process redesign. Internal escalation failures route to compliance governance and reporting line restructuring." + - question: "Is the communication breakdown affecting customer-facing regulatory + disclosures (fee disclosures, adverse action notices, privacy notices) + or internal compliance escalation channels?" + purpose: "Customer-facing disclosure failures are regulatory violations. + Internal escalation failures lead to regulatory issues going + unaddressed until they become enforcement actions." + routing_impact: "Customer disclosure failures route to immediate compliance + remediation and disclosure process redesign. Internal escalation + failures route to compliance governance and reporting line + restructuring." diagnosis_weight_shifts: more_likely: - diagnosis: "Compliance-operations communication gap" - reason: "The most consequential communication breakdown in fintech occurs between the compliance function and operational teams. When compliance concerns do not reach the right decision-makers, regulatory violations result." + reason: "The most consequential communication breakdown in fintech occurs + between the compliance function and operational teams. When + compliance concerns do not reach the right decision-makers, + regulatory violations result." less_likely: - diagnosis: "Meeting culture problems" - reason: "Meeting format issues exist but are not the primary communication concern in fintech. The critical communication challenge is ensuring regulatory information flows to decision-makers." + reason: "Meeting format issues exist but are not the primary communication + concern in fintech. The critical communication challenge is ensuring + regulatory information flows to decision-makers." fintech_specific_diagnoses: [] sector_red_flags: - - "Compliance team unable to reach C-suite leadership with urgent regulatory concerns — creates personal liability risk for compliance personnel who have legal obligations to escalate." - - "Customer-facing communications going live without compliance review — any customer-facing communication about a financial product should be reviewed for regulatory compliance." + - "Compliance team unable to reach C-suite leadership with urgent + regulatory concerns — creates personal liability risk for compliance + personnel who have legal obligations to escalate." + - "Customer-facing communications going live without compliance review — + any customer-facing communication about a financial product should be + reviewed for regulatory compliance." # ───────────────────────────────────────────── # 20. NEGOTIATION STUCK DIAGNOSIS @@ -674,19 +1320,41 @@ diagnostic_rules: - diagnostic: "negotiation-stuck-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Stuck negotiations in fintech most commonly involve banking partner terms, regulatory consent orders, and enterprise client compliance requirements. These negotiations are fundamentally different from commercial negotiations because they involve regulatory constraints that limit the negotiation space — neither party can agree to terms that violate regulatory requirements." + adaptation_rationale: "Stuck negotiations in fintech most commonly involve + banking partner terms, regulatory consent orders, and enterprise client + compliance requirements. These negotiations are fundamentally different + from commercial negotiations because they involve regulatory constraints + that limit the negotiation space — neither party can agree to terms that + violate regulatory requirements." additional_triage_questions: - - question: "Is the negotiation stuck because of a regulatory constraint that limits what either party can agree to — e.g., the banking partner cannot agree to terms that violate third-party risk management guidance?" - purpose: "Regulatory constraints narrow the zone of possible agreement in fintech negotiations. Understanding which constraints are binding helps identify whether the negotiation is stuck because of interests or because of regulations." - routing_impact: "Regulatory-constrained negotiation routes to regulatory-informed alternative generation — finding terms that satisfy both commercial interests and regulatory requirements. Interest-based stall routes to standard negotiation frameworks." + - question: "Is the negotiation stuck because of a regulatory constraint that + limits what either party can agree to — e.g., the banking partner + cannot agree to terms that violate third-party risk management + guidance?" + purpose: "Regulatory constraints narrow the zone of possible agreement in + fintech negotiations. Understanding which constraints are binding + helps identify whether the negotiation is stuck because of interests + or because of regulations." + routing_impact: "Regulatory-constrained negotiation routes to + regulatory-informed alternative generation — finding terms that + satisfy both commercial interests and regulatory requirements. + Interest-based stall routes to standard negotiation frameworks." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory constraint as hidden negotiation barrier" - reason: "In fintech, negotiations often stall because one party cannot explain that a regulatory requirement prevents agreement. Banking partners, in particular, may resist terms without disclosing the specific regulatory guidance driving their position." + reason: "In fintech, negotiations often stall because one party cannot explain + that a regulatory requirement prevents agreement. Banking partners, + in particular, may resist terms without disclosing the specific + regulatory guidance driving their position." less_likely: - diagnosis: "Personality-driven stalemate" - reason: "Fintech negotiations are typically between sophisticated parties who understand the regulatory landscape. Stalemates are more often structural (regulatory constraints) than personal." + reason: "Fintech negotiations are typically between sophisticated parties who + understand the regulatory landscape. Stalemates are more often + structural (regulatory constraints) than personal." fintech_specific_diagnoses: [] sector_red_flags: - - "Banking partner negotiation stalled for more than 90 days — may indicate the partner is conducting an internal regulatory review of the entire fintech program." - - "Regulatory settlement negotiation — requires specialized counsel and should not be handled by the general business team." + - "Banking partner negotiation stalled for more than 90 days — may + indicate the partner is conducting an internal regulatory review of the + entire fintech program." + - "Regulatory settlement negotiation — requires specialized counsel and + should not be handled by the general business team." diff --git a/.claude/industry-packs/fintech/fintech-skill-overlays.yaml b/.claude/industry-packs/fintech/fintech-skill-overlays.yaml index 554981e..fa8fc20 100644 --- a/.claude/industry-packs/fintech/fintech-skill-overlays.yaml +++ b/.claude/industry-packs/fintech/fintech-skill-overlays.yaml @@ -46,211 +46,763 @@ skill_overlays: - skill: "porters-five-forces" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Regulation rewrites Porter's Five Forces in fintech. Barriers to entry are overwhelmingly regulatory — licensing requirements (state money transmitter licenses, bank charters, SEC/FINRA registration), capital requirements (Basel III, state net worth minimums), and compliance infrastructure create moats that cost $1M-$50M+ to cross. Threat of new entrants must include both startups AND big tech (Apple Pay, Google Wallet, Amazon Lending) who can amortize compliance costs across massive user bases. Buyer power is amplified by regulatory mandates — PSD2 Open Banking in Europe and Section 1033 in the US force data portability, structurally increasing buyer switching power. Supplier power concentrates in banking-as-a-service providers (Synapse, Column, Cross River) and card network duopoly (Visa/Mastercard)." + fintech_context: "Regulation rewrites Porter's Five Forces in fintech. Barriers + to entry are overwhelmingly regulatory — licensing requirements (state + money transmitter licenses, bank charters, SEC/FINRA registration), + capital requirements (Basel III, state net worth minimums), and compliance + infrastructure create moats that cost $1M-$50M+ to cross. Threat of new + entrants must include both startups AND big tech (Apple Pay, Google + Wallet, Amazon Lending) who can amortize compliance costs across massive + user bases. Buyer power is amplified by regulatory mandates — PSD2 Open + Banking in Europe and Section 1033 in the US force data portability, + structurally increasing buyer switching power. Supplier power concentrates + in banking-as-a-service providers (Synapse, Column, Cross River) and card + network duopoly (Visa/Mastercard)." fintech_anti_patterns: - - "Assuming regulatory barriers protect you permanently. Regulatory frameworks evolve — PSD2 demolished barriers in European payments; Section 1033 will do the same in the US. Incumbents who rely on licensing moats without building product moats face disruption when regulations change." - - "Ignoring the big tech threat vector. Apple, Google, and Amazon can enter any fintech vertical with enormous distribution advantages, pre-existing customer trust, and the ability to operate regulated services as loss leaders within their ecosystem." - - "Treating the card networks (Visa, Mastercard) as neutral infrastructure. They are powerful suppliers who set interchange rates, impose compliance requirements, and can revoke processing privileges. Their expansion into fintech infrastructure (Visa Direct, Mastercard Send) makes them potential competitors." - fintech_example: "A payments fintech applies Porter's Five Forces and discovers that its apparent competitive moat — money transmitter licenses in 48 states — is actually shared with 15 competitors. The real competitive force is supplier power: their single banking partner (BaaS provider) processes all transactions, and a regulatory enforcement action against that partner would halt their business overnight. This analysis shifts strategy from product differentiation to banking partner diversification and eventually a direct bank charter application." - benchmark_references: ["take-rate", "regulatory-compliance-cost", "tpv"] + - "Assuming regulatory barriers protect you permanently. Regulatory + frameworks evolve — PSD2 demolished barriers in European payments; + Section 1033 will do the same in the US. Incumbents who rely on + licensing moats without building product moats face disruption when + regulations change." + - "Ignoring the big tech threat vector. Apple, Google, and Amazon can + enter any fintech vertical with enormous distribution advantages, + pre-existing customer trust, and the ability to operate regulated + services as loss leaders within their ecosystem." + - "Treating the card networks (Visa, Mastercard) as neutral + infrastructure. They are powerful suppliers who set interchange rates, + impose compliance requirements, and can revoke processing privileges. + Their expansion into fintech infrastructure (Visa Direct, Mastercard + Send) makes them potential competitors." + fintech_example: "A payments fintech applies Porter's Five Forces and discovers + that its apparent competitive moat — money transmitter licenses in 48 + states — is actually shared with 15 competitors. The real competitive + force is supplier power: their single banking partner (BaaS provider) + processes all transactions, and a regulatory enforcement action against + that partner would halt their business overnight. This analysis shifts + strategy from product differentiation to banking partner diversification + and eventually a direct bank charter application." + benchmark_references: [ "take-rate", "regulatory-compliance-cost", "tpv" ] - skill: "blue-ocean-strategy" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Blue ocean creation in fintech is uniquely constrained — you cannot create an uncontested market space by ignoring regulations. The most successful fintech blue oceans are created by serving populations that incumbent banks find unprofitable to serve (Nubank in Brazil, M-Pesa in Kenya), by making compliance itself a product (Alloy, Chainalysis), or by embedding financial services where they were previously absent (Shopify Capital, Toast payments). The strategy canvas must include a regulatory axis — the compliance burden of existing solutions versus the compliance innovation of the new offering." + fintech_context: "Blue ocean creation in fintech is uniquely constrained — you + cannot create an uncontested market space by ignoring regulations. The + most successful fintech blue oceans are created by serving populations + that incumbent banks find unprofitable to serve (Nubank in Brazil, M-Pesa + in Kenya), by making compliance itself a product (Alloy, Chainalysis), or + by embedding financial services where they were previously absent (Shopify + Capital, Toast payments). The strategy canvas must include a regulatory + axis — the compliance burden of existing solutions versus the compliance + innovation of the new offering." fintech_anti_patterns: - - "Pursuing a blue ocean that exists because it is illegal. Many apparent market gaps in financial services exist because regulatory constraints prohibit the activity. 'Move fast and break things' in fintech means fines, enforcement actions, and prison." - - "Ignoring that regulatory arbitrage creates temporary blue oceans. Operating without a required license is not a strategy — it is a ticking clock. The regulatory gap will close, and enforcement will follow." - - "Assuming financial inclusion is automatically a blue ocean. Serving underbanked populations requires understanding why banks exited those markets — credit risk, fraud risk, and compliance costs are real, not arbitrary barriers." - fintech_example: "Nubank created a blue ocean in Brazilian financial services by eliminating what incumbents considered essential — branches, relationship managers, paper statements, and complex fee schedules. The strategy canvas revealed that Brazilian banks over-served high-net-worth customers with premium services while punishing mass-market customers with opaque fees. Nubank's blue ocean was 'transparent, digital-only, zero-fee banking for the mass market' — a space incumbents could not enter without cannibalizing their fee-dependent business models. Critically, Nubank obtained a full banking license, ensuring the blue ocean was regulatory-compliant." - benchmark_references: ["cac", "monthly-active-users", "cost-to-income-ratio"] + - "Pursuing a blue ocean that exists because it is illegal. Many apparent + market gaps in financial services exist because regulatory constraints + prohibit the activity. 'Move fast and break things' in fintech means + fines, enforcement actions, and prison." + - "Ignoring that regulatory arbitrage creates temporary blue oceans. + Operating without a required license is not a strategy — it is a ticking + clock. The regulatory gap will close, and enforcement will follow." + - "Assuming financial inclusion is automatically a blue ocean. Serving + underbanked populations requires understanding why banks exited those + markets — credit risk, fraud risk, and compliance costs are real, not + arbitrary barriers." + fintech_example: "Nubank created a blue ocean in Brazilian financial services by + eliminating what incumbents considered essential — branches, relationship + managers, paper statements, and complex fee schedules. The strategy canvas + revealed that Brazilian banks over-served high-net-worth customers with + premium services while punishing mass-market customers with opaque fees. + Nubank's blue ocean was 'transparent, digital-only, zero-fee banking for + the mass market' — a space incumbents could not enter without + cannibalizing their fee-dependent business models. Critically, Nubank + obtained a full banking license, ensuring the blue ocean was + regulatory-compliant." + benchmark_references: [ "cac", "monthly-active-users", "cost-to-income-ratio" ] - skill: "business-model-canvas" category: "frameworks" fintech_relevance: "critical" - fintech_context: "The Business Model Canvas for fintech requires a regulatory layer across nearly every block. Key Partners must include banking partners, card networks, identity verification providers, and regulators themselves — the regulatory relationship is a partnership that enables the business. Key Activities must include compliance operations (KYC, AML, transaction monitoring, regulatory reporting) as a core activity, not an overhead function. Revenue Streams must distinguish between regulated revenue (interchange, interest income, advisory fees subject to regulatory caps) and unregulated revenue (SaaS fees, data products). Cost Structure must separate compliance costs because they are non-discretionary — you cannot cut compliance spending to extend runway." + fintech_context: "The Business Model Canvas for fintech requires a regulatory + layer across nearly every block. Key Partners must include banking + partners, card networks, identity verification providers, and regulators + themselves — the regulatory relationship is a partnership that enables the + business. Key Activities must include compliance operations (KYC, AML, + transaction monitoring, regulatory reporting) as a core activity, not an + overhead function. Revenue Streams must distinguish between regulated + revenue (interchange, interest income, advisory fees subject to regulatory + caps) and unregulated revenue (SaaS fees, data products). Cost Structure + must separate compliance costs because they are non-discretionary — you + cannot cut compliance spending to extend runway." fintech_anti_patterns: - - "Omitting the regulatory infrastructure from Key Resources. Licenses, compliance systems, banking relationships, and regulatory goodwill are among the most valuable and hardest-to-replicate resources in fintech." - - "Treating compliance as a Cost Structure line item rather than a Key Activity. In fintech, compliance is not overhead — it is the activity that enables every other activity on the canvas." - - "Designing the Customer Relationship block without considering regulatory constraints on customer communication. Financial services advertising, account disclosures, and marketing are regulated by UDAP/UDAAP, TILA, Reg Z, and state-specific rules." - fintech_example: "A BNPL fintech maps its Business Model Canvas and discovers that its Key Partners block reveals existential concentration risk: one BaaS provider, one card network processor, and one identity verification vendor. A failure at any partner halts the business. The Key Activities analysis reveals that 40% of engineering time is spent on compliance-related features (regulatory reporting, transaction monitoring alerts, customer disclosure requirements) — far more than anticipated. This canvas analysis triggers a strategic shift: diversify banking partners, build redundant identity verification, and restructure engineering to treat compliance features as first-class product features rather than afterthoughts." - benchmark_references: ["regulatory-compliance-cost", "gross-margin", "cac", "kyc-cost-per-customer"] + - "Omitting the regulatory infrastructure from Key Resources. Licenses, + compliance systems, banking relationships, and regulatory goodwill are + among the most valuable and hardest-to-replicate resources in fintech." + - "Treating compliance as a Cost Structure line item rather than a Key + Activity. In fintech, compliance is not overhead — it is the activity + that enables every other activity on the canvas." + - "Designing the Customer Relationship block without considering + regulatory constraints on customer communication. Financial services + advertising, account disclosures, and marketing are regulated by + UDAP/UDAAP, TILA, Reg Z, and state-specific rules." + fintech_example: "A BNPL fintech maps its Business Model Canvas and discovers + that its Key Partners block reveals existential concentration risk: one + BaaS provider, one card network processor, and one identity verification + vendor. A failure at any partner halts the business. The Key Activities + analysis reveals that 40% of engineering time is spent on + compliance-related features (regulatory reporting, transaction monitoring + alerts, customer disclosure requirements) — far more than anticipated. + This canvas analysis triggers a strategic shift: diversify banking + partners, build redundant identity verification, and restructure + engineering to treat compliance features as first-class product features + rather than afterthoughts." + benchmark_references: + [ + "regulatory-compliance-cost", + "gross-margin", + "cac", + "kyc-cost-per-customer" + ] - skill: "four-ps-marketing" category: "frameworks" fintech_relevance: "critical" - fintech_context: "The Four Ps require regulatory awareness at every level in fintech. Product is subject to regulatory approval — new financial products may require regulatory filing, disclosure documents, or license amendments. Price in fintech faces regulatory caps: interchange caps under Durbin Amendment and PSD2 IFR, interest rate caps under state usury laws, fee restrictions under UDAP/UDAAP. Place (distribution) is constrained by licensing — you can only distribute financial products in jurisdictions where you hold appropriate licenses. Promotion is heavily regulated by UDAP/UDAAP, TILA advertising requirements, SEC advertising rules for investment products, and state-specific marketing restrictions. A marketing claim that would be merely aggressive in SaaS could be a regulatory violation in fintech." + fintech_context: "The Four Ps require regulatory awareness at every level in + fintech. Product is subject to regulatory approval — new financial + products may require regulatory filing, disclosure documents, or license + amendments. Price in fintech faces regulatory caps: interchange caps under + Durbin Amendment and PSD2 IFR, interest rate caps under state usury laws, + fee restrictions under UDAP/UDAAP. Place (distribution) is constrained by + licensing — you can only distribute financial products in jurisdictions + where you hold appropriate licenses. Promotion is heavily regulated by + UDAP/UDAAP, TILA advertising requirements, SEC advertising rules for + investment products, and state-specific marketing restrictions. A + marketing claim that would be merely aggressive in SaaS could be a + regulatory violation in fintech." fintech_anti_patterns: - - "Setting prices without understanding regulatory caps. Durbin Amendment caps debit interchange for large issuers. State usury laws cap interest rates. UDAP/UDAAP prohibits unfair fees. Price is not a free variable in fintech." - - "Running 'growth hack' marketing without regulatory review. APR disclosures, fee transparency, and truthful advertising are legal requirements, not suggestions. Misleading financial advertising triggers CFPB enforcement." - - "Distributing financial products across state lines without appropriate licensing. Each state has its own licensing requirements for lending, money transmission, and insurance. Unlicensed activity is a criminal offense in many jurisdictions." - fintech_example: "A neobank applies the Four Ps and discovers that its planned 'no-fee overdraft' marketing campaign violates UDAP/UDAAP because the overdraft product has conditions that effectively charge customers through a different mechanism. The Promotion analysis reveals that 30% of planned marketing messages require regulatory rewording. The Place analysis identifies 12 states where the company lacks lending licenses, constraining geographic expansion. The Four Ps exercise transforms from a marketing planning tool into a regulatory compliance mapping exercise — the correct application for financial services." - benchmark_references: ["cac", "arpu", "kyc-conversion-rate"] + - "Setting prices without understanding regulatory caps. Durbin Amendment + caps debit interchange for large issuers. State usury laws cap interest + rates. UDAP/UDAAP prohibits unfair fees. Price is not a free variable in + fintech." + - "Running 'growth hack' marketing without regulatory review. APR + disclosures, fee transparency, and truthful advertising are legal + requirements, not suggestions. Misleading financial advertising triggers + CFPB enforcement." + - "Distributing financial products across state lines without appropriate + licensing. Each state has its own licensing requirements for lending, + money transmission, and insurance. Unlicensed activity is a criminal + offense in many jurisdictions." + fintech_example: "A neobank applies the Four Ps and discovers that its planned + 'no-fee overdraft' marketing campaign violates UDAP/UDAAP because the + overdraft product has conditions that effectively charge customers through + a different mechanism. The Promotion analysis reveals that 30% of planned + marketing messages require regulatory rewording. The Place analysis + identifies 12 states where the company lacks lending licenses, + constraining geographic expansion. The Four Ps exercise transforms from a + marketing planning tool into a regulatory compliance mapping exercise — + the correct application for financial services." + benchmark_references: [ "cac", "arpu", "kyc-conversion-rate" ] - skill: "net-promoter-score" category: "frameworks" fintech_relevance: "critical" - fintech_context: "NPS in fintech carries existential weight because financial services are trust-dependent. A security breach, a wrongful account freeze, or a compliance-driven account closure can transform a promoter into a vocal detractor who warns others away from the platform — and in fintech, those warnings spread faster and hit harder than in other industries because money is involved. NPS surveys in fintech must be triggered by financial milestones (first direct deposit, first loan approval, first claim resolution), not arbitrary time intervals. The qualitative feedback is especially valuable for identifying compliance friction points — KYC frustrations, false-positive fraud blocks, and unexplained transaction declines that damage trust." + fintech_context: "NPS in fintech carries existential weight because financial + services are trust-dependent. A security breach, a wrongful account + freeze, or a compliance-driven account closure can transform a promoter + into a vocal detractor who warns others away from the platform — and in + fintech, those warnings spread faster and hit harder than in other + industries because money is involved. NPS surveys in fintech must be + triggered by financial milestones (first direct deposit, first loan + approval, first claim resolution), not arbitrary time intervals. The + qualitative feedback is especially valuable for identifying compliance + friction points — KYC frustrations, false-positive fraud blocks, and + unexplained transaction declines that damage trust." fintech_anti_patterns: - - "Surveying NPS after account opening but not after the first regulatory friction event (KYC delay, fraud block, transaction decline). The true NPS is measured after the customer has experienced the compliance-driven friction that defines fintech UX." - - "Ignoring the detractor signal from account closures. In fintech, forced account closures (due to compliance triggers, risk reviews, or fraud suspicion) generate extreme detractors who can cause reputational damage disproportionate to their numbers." - - "Optimizing NPS by reducing compliance friction in ways that create regulatory risk. The goal is to minimize unnecessary friction while maintaining full compliance — not to eliminate compliance steps that customers find annoying." - fintech_example: "A neobank segments NPS by customer journey stage and discovers that NPS is 72 after account opening but drops to 18 after the first account freeze triggered by their automated fraud detection system. Investigation reveals that 85% of fraud-flagged accounts are false positives, and the resolution process requires 48 hours — during which customers cannot access their money. The NPS data drives a product investment in real-time fraud review and instant account unfreezing for confirmed false positives, restoring NPS to 55 after fraud events while maintaining BSA/AML compliance." - benchmark_references: ["kyc-conversion-rate", "monthly-active-users", "net-revenue-retention"] + - "Surveying NPS after account opening but not after the first regulatory + friction event (KYC delay, fraud block, transaction decline). The true + NPS is measured after the customer has experienced the compliance-driven + friction that defines fintech UX." + - "Ignoring the detractor signal from account closures. In fintech, forced + account closures (due to compliance triggers, risk reviews, or fraud + suspicion) generate extreme detractors who can cause reputational damage + disproportionate to their numbers." + - "Optimizing NPS by reducing compliance friction in ways that create + regulatory risk. The goal is to minimize unnecessary friction while + maintaining full compliance — not to eliminate compliance steps that + customers find annoying." + fintech_example: "A neobank segments NPS by customer journey stage and discovers + that NPS is 72 after account opening but drops to 18 after the first + account freeze triggered by their automated fraud detection system. + Investigation reveals that 85% of fraud-flagged accounts are false + positives, and the resolution process requires 48 hours — during which + customers cannot access their money. The NPS data drives a product + investment in real-time fraud review and instant account unfreezing for + confirmed false positives, restoring NPS to 55 after fraud events while + maintaining BSA/AML compliance." + benchmark_references: [ "kyc-conversion-rate", "monthly-active-users", "net-revenue-retention" ] - skill: "product-life-cycle" category: "frameworks" fintech_relevance: "high" - fintech_context: "Product lifecycle in fintech is uniquely shaped by regulatory evolution. Introduction phase includes regulatory approval — a lending product cannot launch until state licenses are obtained, disclosures are approved, and compliance infrastructure is operational. Growth phase may be accelerated or constrained by regulatory decisions: PSD2 opened European payments markets; conversely, crypto regulation in 2022-2024 constrained growth for entire sub-sectors. Maturity arrives when the regulatory framework stabilizes and compliance becomes a commodity rather than a differentiator. Decline can be triggered by regulatory change — a new regulation can obsolete an entire business model overnight (as happened with payday lending regulations in multiple states)." + fintech_context: "Product lifecycle in fintech is uniquely shaped by regulatory + evolution. Introduction phase includes regulatory approval — a lending + product cannot launch until state licenses are obtained, disclosures are + approved, and compliance infrastructure is operational. Growth phase may + be accelerated or constrained by regulatory decisions: PSD2 opened + European payments markets; conversely, crypto regulation in 2022-2024 + constrained growth for entire sub-sectors. Maturity arrives when the + regulatory framework stabilizes and compliance becomes a commodity rather + than a differentiator. Decline can be triggered by regulatory change — a + new regulation can obsolete an entire business model overnight (as + happened with payday lending regulations in multiple states)." fintech_anti_patterns: - - "Assuming product lifecycle is determined solely by market dynamics. In fintech, a regulation can move a product from Growth to Decline in a single legislative session. Monitor regulatory pipelines as closely as competitive dynamics." - - "Investing in Growth-phase tactics for a product whose regulatory environment is entering Maturity. When compliance becomes commoditized (as happened with basic KYC), the competitive advantage shifts from 'we are compliant' to 'we are compliant AND differentiated.'" - - "Sunsetting a product without understanding regulatory obligations for data retention, customer notification, and account closure. Financial product wind-down has regulatory requirements that non-financial products do not." - fintech_example: "BNPL products followed a textbook product lifecycle compressed by regulatory intervention. Introduction (2018-2020): novel product, light regulation, rapid adoption. Growth (2020-2022): mainstream adoption, high-profile IPOs. Regulatory trigger (2022-2024): CFPB classifies BNPL as credit subject to TILA, multiple states introduce BNPL-specific regulation. The product is now transitioning from Growth to Maturity faster than market dynamics alone would dictate — regulatory intervention accelerated the lifecycle by 3-5 years." - benchmark_references: ["monthly-active-users", "regulatory-compliance-cost", "gross-margin"] + - "Assuming product lifecycle is determined solely by market dynamics. In + fintech, a regulation can move a product from Growth to Decline in a + single legislative session. Monitor regulatory pipelines as closely as + competitive dynamics." + - "Investing in Growth-phase tactics for a product whose regulatory + environment is entering Maturity. When compliance becomes commoditized + (as happened with basic KYC), the competitive advantage shifts from 'we + are compliant' to 'we are compliant AND differentiated.'" + - "Sunsetting a product without understanding regulatory obligations for + data retention, customer notification, and account closure. Financial + product wind-down has regulatory requirements that non-financial + products do not." + fintech_example: "BNPL products followed a textbook product lifecycle compressed + by regulatory intervention. Introduction (2018-2020): novel product, light + regulation, rapid adoption. Growth (2020-2022): mainstream adoption, + high-profile IPOs. Regulatory trigger (2022-2024): CFPB classifies BNPL as + credit subject to TILA, multiple states introduce BNPL-specific + regulation. The product is now transitioning from Growth to Maturity + faster than market dynamics alone would dictate — regulatory intervention + accelerated the lifecycle by 3-5 years." + benchmark_references: [ "monthly-active-users", "regulatory-compliance-cost", "gross-margin" ] - skill: "disruptive-innovation" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Disruptive innovation in fintech follows the classic pattern with a regulatory twist: the incumbent is protected not just by product complexity but by regulatory moats. Disruption occurs when a fintech finds a regulatory pathway that incumbents overlooked or dismissed. Stripe disrupted payment processing by acting as a payment facilitator (payfac) rather than requiring each merchant to obtain its own merchant account — a regulatory interpretation that incumbents had not exploited. Nubank disrupted Brazilian banking by obtaining a digital banking license rather than building branches. The disruption framework must account for regulatory pathways as a strategic variable — the choice of charter, license, or regulatory framework IS the innovation." + fintech_context: "Disruptive innovation in fintech follows the classic pattern + with a regulatory twist: the incumbent is protected not just by product + complexity but by regulatory moats. Disruption occurs when a fintech finds + a regulatory pathway that incumbents overlooked or dismissed. Stripe + disrupted payment processing by acting as a payment facilitator (payfac) + rather than requiring each merchant to obtain its own merchant account — a + regulatory interpretation that incumbents had not exploited. Nubank + disrupted Brazilian banking by obtaining a digital banking license rather + than building branches. The disruption framework must account for + regulatory pathways as a strategic variable — the choice of charter, + license, or regulatory framework IS the innovation." fintech_anti_patterns: - - "Trying to disrupt from outside the regulatory perimeter. Unlike tech disruption where you can 'beg forgiveness,' operating without required financial licenses is a federal crime. The regulatory pathway must be established before or concurrent with the disruption." - - "Assuming incumbents are permanently constrained by legacy regulation. Banks are actively lobbying for regulatory relief and building digital subsidiaries. The window for regulatory-arbitrage disruption closes." - - "Confusing regulatory non-compliance with innovation. Uber's 'ignore existing regulations' playbook does not transfer to financial services — financial regulators have enforcement power that transportation regulators lacked." - fintech_example: "Square disrupted the merchant acquiring industry by using the payment facilitator (payfac) model, which allowed it to aggregate small merchants under its own master merchant account rather than requiring each business to undergo individual underwriting. The incumbent acquirers dismissed this approach as impractical and risky. Square's innovation was not primarily technological (the card reader was simple) but regulatory and operational — it found a compliant pathway that incumbents had not exploited, then built technology to manage the fraud and compliance risk at scale." - benchmark_references: ["tpv", "cac", "cost-per-transaction"] + - "Trying to disrupt from outside the regulatory perimeter. Unlike tech + disruption where you can 'beg forgiveness,' operating without required + financial licenses is a federal crime. The regulatory pathway must be + established before or concurrent with the disruption." + - "Assuming incumbents are permanently constrained by legacy regulation. + Banks are actively lobbying for regulatory relief and building digital + subsidiaries. The window for regulatory-arbitrage disruption closes." + - "Confusing regulatory non-compliance with innovation. Uber's 'ignore + existing regulations' playbook does not transfer to financial services — + financial regulators have enforcement power that transportation + regulators lacked." + fintech_example: "Square disrupted the merchant acquiring industry by using the + payment facilitator (payfac) model, which allowed it to aggregate small + merchants under its own master merchant account rather than requiring each + business to undergo individual underwriting. The incumbent acquirers + dismissed this approach as impractical and risky. Square's innovation was + not primarily technological (the card reader was simple) but regulatory + and operational — it found a compliant pathway that incumbents had not + exploited, then built technology to manage the fraud and compliance risk + at scale." + benchmark_references: [ "tpv", "cac", "cost-per-transaction" ] - skill: "balanced-scorecard" category: "frameworks" fintech_relevance: "critical" - fintech_context: "The Balanced Scorecard in fintech requires a fifth perspective beyond the traditional four: Regulatory Compliance. Financial Perspective: net revenue, NIM, gross margin, cost-to-income ratio — but constrained by regulatory capital requirements and fee caps. Customer Perspective: NPS, MAU, transactions per user, KYC conversion rate — the regulatory friction in customer experience is a measurable variable. Internal Process Perspective: fraud detection accuracy, false positive rate, AML alert disposition time, regulatory reporting accuracy. Learning & Growth Perspective: compliance training completion, audit finding remediation velocity, regulatory change management speed. Regulatory Perspective (added): license status, examination findings, enforcement action risk, regulatory capital surplus/deficit." + fintech_context: "The Balanced Scorecard in fintech requires a fifth perspective + beyond the traditional four: Regulatory Compliance. Financial Perspective: + net revenue, NIM, gross margin, cost-to-income ratio — but constrained by + regulatory capital requirements and fee caps. Customer Perspective: NPS, + MAU, transactions per user, KYC conversion rate — the regulatory friction + in customer experience is a measurable variable. Internal Process + Perspective: fraud detection accuracy, false positive rate, AML alert + disposition time, regulatory reporting accuracy. Learning & Growth + Perspective: compliance training completion, audit finding remediation + velocity, regulatory change management speed. Regulatory Perspective + (added): license status, examination findings, enforcement action risk, + regulatory capital surplus/deficit." fintech_anti_patterns: - - "Tracking financial metrics without a regulatory compliance perspective. A fintech with excellent growth metrics and deteriorating compliance standing is heading toward an enforcement action that will erase the financial performance." - - "Measuring Internal Process efficiency without including compliance process metrics. AML alert disposition time, SAR filing timeliness, and regulatory reporting accuracy are operational metrics with legal consequences." - - "Ignoring the Learning & Growth investment in compliance talent. Compliance officers, BSA officers, and legal counsel are not overhead — they are the human infrastructure that enables the business." - fintech_example: "A lending fintech implements a balanced scorecard with five perspectives: Financial (loan origination volume, NIM, default rate, gross margin), Customer (application completion rate, NPS, repeat borrower rate), Internal Process (underwriting decision time, SAR filing timeliness, fair lending audit results), Learning & Growth (compliance training completion rate, new regulation integration speed, audit finding closure rate), Regulatory (state license renewal status, examination finding severity, regulatory capital adequacy). The scorecard reveals that accelerating origination volume (Financial) is creating SAR filing backlogs (Internal Process) and triggering fair lending pattern concerns (Regulatory) — the scorecard prevents a growth strategy from causing a compliance crisis." - benchmark_references: ["regulatory-compliance-cost", "default-rate", "kyc-conversion-rate", "gross-margin", "net-interest-margin"] + - "Tracking financial metrics without a regulatory compliance perspective. + A fintech with excellent growth metrics and deteriorating compliance + standing is heading toward an enforcement action that will erase the + financial performance." + - "Measuring Internal Process efficiency without including compliance + process metrics. AML alert disposition time, SAR filing timeliness, and + regulatory reporting accuracy are operational metrics with legal + consequences." + - "Ignoring the Learning & Growth investment in compliance talent. + Compliance officers, BSA officers, and legal counsel are not overhead — + they are the human infrastructure that enables the business." + fintech_example: "A lending fintech implements a balanced scorecard with five + perspectives: Financial (loan origination volume, NIM, default rate, gross + margin), Customer (application completion rate, NPS, repeat borrower + rate), Internal Process (underwriting decision time, SAR filing + timeliness, fair lending audit results), Learning & Growth (compliance + training completion rate, new regulation integration speed, audit finding + closure rate), Regulatory (state license renewal status, examination + finding severity, regulatory capital adequacy). The scorecard reveals that + accelerating origination volume (Financial) is creating SAR filing + backlogs (Internal Process) and triggering fair lending pattern concerns + (Regulatory) — the scorecard prevents a growth strategy from causing a + compliance crisis." + benchmark_references: + [ + "regulatory-compliance-cost", + "default-rate", + "kyc-conversion-rate", + "gross-margin", + "net-interest-margin" + ] - skill: "trust-equation" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Trust is EXISTENTIAL in fintech — one security breach, one data leak, or one regulatory enforcement action can be fatal. The Trust Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to fintech as follows: Credibility = regulatory licenses, SOC 2 Type II certification, PCI-DSS compliance, FDIC insurance, published security practices. Reliability = 99.99% uptime, consistent transaction processing, predictable fee schedules, accurate account balances. Intimacy = understanding the customer's financial situation, personalized financial guidance, empathetic handling of financial distress. Self-Orientation = the denominator that destroys trust — hidden fees, opaque pricing, dark patterns that prevent account closure, selling customer data to third parties, and any behavior that prioritizes revenue extraction over customer financial wellbeing. UDAP/UDAAP enforcement is essentially a legal codification of the Self-Orientation problem." + fintech_context: "Trust is EXISTENTIAL in fintech — one security breach, one + data leak, or one regulatory enforcement action can be fatal. The Trust + Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to + fintech as follows: Credibility = regulatory licenses, SOC 2 Type II + certification, PCI-DSS compliance, FDIC insurance, published security + practices. Reliability = 99.99% uptime, consistent transaction processing, + predictable fee schedules, accurate account balances. Intimacy = + understanding the customer's financial situation, personalized financial + guidance, empathetic handling of financial distress. Self-Orientation = + the denominator that destroys trust — hidden fees, opaque pricing, dark + patterns that prevent account closure, selling customer data to third + parties, and any behavior that prioritizes revenue extraction over + customer financial wellbeing. UDAP/UDAAP enforcement is essentially a + legal codification of the Self-Orientation problem." fintech_anti_patterns: - - "Building credibility through marketing while neglecting reliability. A fintech that advertises '100% secure' but has never undergone a penetration test is building trust on a foundation that will collapse catastrophically." - - "Using dark patterns to increase retention. Hiding account closure options, requiring phone calls to cancel, or imposing unexpected fees are high-Self-Orientation behaviors that regulators are increasingly targeting through UDAP/UDAAP enforcement." - - "Treating data privacy as a legal checkbox rather than a trust signal. GDPR, CCPA, and GLBA compliance are regulatory minimums — customers expect their financial data to be treated with extraordinary care. Any data breach is a trust-extinction event." - fintech_example: "Chime built trust through radical simplification of the Self-Orientation denominator: no overdraft fees, no minimum balance fees, no monthly fees, and early direct deposit access. Each of these reduced perceived Self-Orientation (the company is not trying to extract fees) while increasing Credibility (FDIC-insured through partner banks) and Reliability (consistent experience). The trust equation explains Chime's growth to 15M+ accounts — in a market where consumers distrust banks, eliminating the behaviors that generate distrust is the most powerful growth lever." - benchmark_references: ["monthly-active-users", "net-revenue-retention", "fraud-rate"] + - "Building credibility through marketing while neglecting reliability. A + fintech that advertises '100% secure' but has never undergone a + penetration test is building trust on a foundation that will collapse + catastrophically." + - "Using dark patterns to increase retention. Hiding account closure + options, requiring phone calls to cancel, or imposing unexpected fees + are high-Self-Orientation behaviors that regulators are increasingly + targeting through UDAP/UDAAP enforcement." + - "Treating data privacy as a legal checkbox rather than a trust signal. + GDPR, CCPA, and GLBA compliance are regulatory minimums — customers + expect their financial data to be treated with extraordinary care. Any + data breach is a trust-extinction event." + fintech_example: "Chime built trust through radical simplification of the + Self-Orientation denominator: no overdraft fees, no minimum balance fees, + no monthly fees, and early direct deposit access. Each of these reduced + perceived Self-Orientation (the company is not trying to extract fees) + while increasing Credibility (FDIC-insured through partner banks) and + Reliability (consistent experience). The trust equation explains Chime's + growth to 15M+ accounts — in a market where consumers distrust banks, + eliminating the behaviors that generate distrust is the most powerful + growth lever." + benchmark_references: [ "monthly-active-users", "net-revenue-retention", "fraud-rate" ] - skill: "swot-pest-analysis" category: "frameworks" fintech_relevance: "critical" - fintech_context: "PEST analysis in fintech is dominated by the Political and Legal dimensions to an extent not seen in other industries. Political: regulatory regime changes (new administration = new enforcement priorities), international regulatory coordination (Basel standards, FATF recommendations), state-level regulatory fragmentation (50 different money transmitter license requirements). Economic: interest rate environment (directly impacts lending NIM and deposit competition), credit cycle position (determines default rates), funding market conditions (warehouse line availability, securitization market health). Social: financial inclusion expectations, consumer privacy concerns, trust in digital-only institutions, generational banking preferences. Technological: real-time payments infrastructure (FedNow, RTP), open banking APIs (Plaid, MX), blockchain/DLT applications, AI in credit underwriting (model risk management requirements)." + fintech_context: "PEST analysis in fintech is dominated by the Political and + Legal dimensions to an extent not seen in other industries. Political: + regulatory regime changes (new administration = new enforcement + priorities), international regulatory coordination (Basel standards, FATF + recommendations), state-level regulatory fragmentation (50 different money + transmitter license requirements). Economic: interest rate environment + (directly impacts lending NIM and deposit competition), credit cycle + position (determines default rates), funding market conditions (warehouse + line availability, securitization market health). Social: financial + inclusion expectations, consumer privacy concerns, trust in digital-only + institutions, generational banking preferences. Technological: real-time + payments infrastructure (FedNow, RTP), open banking APIs (Plaid, MX), + blockchain/DLT applications, AI in credit underwriting (model risk + management requirements)." fintech_anti_patterns: - - "Under-weighting the Political dimension. A change in CFPB leadership can shift enforcement priorities overnight. A new state attorney general can launch investigations into practices previously tolerated. Regulatory risk is the dominant PEST factor in fintech." - - "Treating SWOT Strengths as permanent. A regulatory license is a strength today but can be revoked tomorrow. A banking partnership is a strength until the partner bank faces its own regulatory issues. Fintech strengths are more fragile than they appear." - - "Conducting PEST analysis without monitoring regulatory pipelines. Proposed regulations (CFPB rulemaking, state legislative sessions, Basel Committee consultations) signal future changes that should be incorporated into the analysis." - fintech_example: "A crypto exchange conducts PEST analysis in early 2024 and identifies that the Political dimension is about to shift dramatically: the EU's MiCA regulation takes effect, creating a comprehensive regulatory framework that will require significant compliance investment but also legitimize the industry. The Economic dimension shows institutional interest increasing. The SWOT reveals that the company's lack of EU entity is a critical Weakness that must be addressed before MiCA enforcement, while its strong compliance infrastructure (built for US regulations) is a Strength that transfers to the EU framework. The analysis drives a six-month plan to establish an EU entity and obtain MiCA authorization before competitors." - benchmark_references: ["regulatory-compliance-cost", "gross-margin", "monthly-active-users"] + - "Under-weighting the Political dimension. A change in CFPB leadership + can shift enforcement priorities overnight. A new state attorney general + can launch investigations into practices previously tolerated. + Regulatory risk is the dominant PEST factor in fintech." + - "Treating SWOT Strengths as permanent. A regulatory license is a + strength today but can be revoked tomorrow. A banking partnership is a + strength until the partner bank faces its own regulatory issues. Fintech + strengths are more fragile than they appear." + - "Conducting PEST analysis without monitoring regulatory pipelines. + Proposed regulations (CFPB rulemaking, state legislative sessions, Basel + Committee consultations) signal future changes that should be + incorporated into the analysis." + fintech_example: "A crypto exchange conducts PEST analysis in early 2024 and + identifies that the Political dimension is about to shift dramatically: + the EU's MiCA regulation takes effect, creating a comprehensive regulatory + framework that will require significant compliance investment but also + legitimize the industry. The Economic dimension shows institutional + interest increasing. The SWOT reveals that the company's lack of EU entity + is a critical Weakness that must be addressed before MiCA enforcement, + while its strong compliance infrastructure (built for US regulations) is a + Strength that transfers to the EU framework. The analysis drives a + six-month plan to establish an EU entity and obtain MiCA authorization + before competitors." + benchmark_references: [ "regulatory-compliance-cost", "gross-margin", "monthly-active-users" ] - skill: "scenario-planning" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Scenario planning in fintech must include regulatory scenarios as a primary dimension — not an afterthought. The three critical scenario dimensions are: regulatory environment (favorable vs. restrictive vs. transformative), credit/economic cycle (expansion vs. contraction vs. crisis), and competitive dynamics (stable vs. big-tech entry vs. regulatory-enabled new competition). Regulatory scenarios have outsized impact: an unfavorable CFPB ruling can eliminate an entire revenue line; a favorable charter decision can unlock deposit funding that transforms unit economics; an open banking mandate can demolish switching-cost moats overnight. Every fintech should maintain scenarios for: (1) a major regulatory change affecting their core product, (2) a banking partner failure or exit, (3) a credit cycle downturn that doubles default rates." + fintech_context: "Scenario planning in fintech must include regulatory scenarios + as a primary dimension — not an afterthought. The three critical scenario + dimensions are: regulatory environment (favorable vs. restrictive vs. + transformative), credit/economic cycle (expansion vs. contraction vs. + crisis), and competitive dynamics (stable vs. big-tech entry vs. + regulatory-enabled new competition). Regulatory scenarios have outsized + impact: an unfavorable CFPB ruling can eliminate an entire revenue line; a + favorable charter decision can unlock deposit funding that transforms unit + economics; an open banking mandate can demolish switching-cost moats + overnight. Every fintech should maintain scenarios for: (1) a major + regulatory change affecting their core product, (2) a banking partner + failure or exit, (3) a credit cycle downturn that doubles default rates." fintech_anti_patterns: - - "Building only financial scenarios without regulatory scenarios. A fintech that models three growth rates but does not model the impact of a regulatory enforcement action is scenario planning incorrectly." - - "Treating the banking partner relationship as a constant across scenarios. Banking partners can exit fintech relationships, face their own regulatory actions, or change terms. Scenario planning must include partner risk." - - "Ignoring credit cycle scenarios in lending. Every lending fintech must model performance through a recession — default rates that are 2-3x baseline levels. If the business model does not survive a downturn, it is not sustainable." - fintech_example: "A BNPL company builds four scenarios: (1) Base: current growth trajectory, CFPB regulation increases compliance costs by 20% but does not require fundamental model changes. (2) Regulatory upside: BNPL receives a favorable regulatory classification that legitimizes the product and drives mainstream adoption. (3) Regulatory downside: BNPL classified as credit under TILA, requiring full credit reporting, adverse action notices, and ability-to-repay assessments — fundamentally changing the cost structure. (4) Credit downturn: recession doubles default rates while transaction volume declines 30%. Each scenario has pre-committed strategic responses and trigger indicators." - benchmark_references: ["default-rate", "regulatory-compliance-cost", "gross-margin"] + - "Building only financial scenarios without regulatory scenarios. A + fintech that models three growth rates but does not model the impact of + a regulatory enforcement action is scenario planning incorrectly." + - "Treating the banking partner relationship as a constant across + scenarios. Banking partners can exit fintech relationships, face their + own regulatory actions, or change terms. Scenario planning must include + partner risk." + - "Ignoring credit cycle scenarios in lending. Every lending fintech must + model performance through a recession — default rates that are 2-3x + baseline levels. If the business model does not survive a downturn, it + is not sustainable." + fintech_example: "A BNPL company builds four scenarios: (1) Base: current growth + trajectory, CFPB regulation increases compliance costs by 20% but does not + require fundamental model changes. (2) Regulatory upside: BNPL receives a + favorable regulatory classification that legitimizes the product and + drives mainstream adoption. (3) Regulatory downside: BNPL classified as + credit under TILA, requiring full credit reporting, adverse action + notices, and ability-to-repay assessments — fundamentally changing the + cost structure. (4) Credit downturn: recession doubles default rates while + transaction volume declines 30%. Each scenario has pre-committed strategic + responses and trigger indicators." + benchmark_references: [ "default-rate", "regulatory-compliance-cost", "gross-margin" ] - - skill: "pricing-diagnosis" - category: "frameworks" + - category: "frameworks" fintech_relevance: "critical" - fintech_context: "Pricing in fintech is constrained by regulation in ways that no other industry experiences. Interchange is capped by Durbin Amendment (debit) and PSD2 IFR (EU credit/debit). Interest rates face state usury law ceilings and federal Military Lending Act caps. Fees must comply with UDAP/UDAAP — fees that are 'unfair, deceptive, or abusive' are illegal regardless of their commercial rationale. Pricing diagnosis must begin with a regulatory ceiling analysis: what are the maximum permissible prices for each revenue line? Then assess competitive positioning within those regulatory constraints. The diagnosis should also evaluate cross-subsidy strategies — free checking funded by interchange, zero-interest BNPL funded by merchant fees — and assess their regulatory sustainability." + fintech_context: "Pricing in fintech is constrained by regulation in ways that + no other industry experiences. Interchange is capped by Durbin Amendment + (debit) and PSD2 IFR (EU credit/debit). Interest rates face state usury + law ceilings and federal Military Lending Act caps. Fees must comply with + UDAP/UDAAP — fees that are 'unfair, deceptive, or abusive' are illegal + regardless of their commercial rationale. Pricing diagnosis must begin + with a regulatory ceiling analysis: what are the maximum permissible + prices for each revenue line? Then assess competitive positioning within + those regulatory constraints. The diagnosis should also evaluate + cross-subsidy strategies — free checking funded by interchange, + zero-interest BNPL funded by merchant fees — and assess their regulatory + sustainability." fintech_anti_patterns: - - "Setting prices based on willingness-to-pay without checking regulatory caps. A lending product priced at market-clearing rates may violate usury laws in specific states." - - "Assuming current regulatory pricing constraints are permanent. Interchange caps can tighten (as PSD2 demonstrated in Europe). Interest rate caps can change. Fee prohibitions can expand. Price within current regulations but plan for tighter constraints." - - "Hiding fees that regulators consider material. CFPB 'junk fee' enforcement is targeting practices like surprise overdraft fees, late payment penalties, and account maintenance fees that are not prominently disclosed. Opacity is a regulatory risk, not a pricing strategy." - fintech_example: "A payments company conducts pricing diagnosis and discovers that 60% of its revenue comes from interchange on debit transactions — revenue that is capped by the Durbin Amendment and could be further compressed by proposed legislation. The diagnosis reveals that the company's premium services (fraud analytics, financial reporting, lending integration) are under-priced relative to the value delivered because they were originally bundled 'free' with payment processing. The prescription: unbundle value-add services into separately priced products that are not subject to interchange regulation, shifting the revenue mix from regulated (interchange) to unregulated (SaaS-like fees) over 18 months." - benchmark_references: ["take-rate", "arpu", "gross-margin", "regulatory-compliance-cost"] + - "Setting prices based on willingness-to-pay without checking regulatory + caps. A lending product priced at market-clearing rates may violate + usury laws in specific states." + - "Assuming current regulatory pricing constraints are permanent. + Interchange caps can tighten (as PSD2 demonstrated in Europe). Interest + rate caps can change. Fee prohibitions can expand. Price within current + regulations but plan for tighter constraints." + - "Hiding fees that regulators consider material. CFPB 'junk fee' + enforcement is targeting practices like surprise overdraft fees, late + payment penalties, and account maintenance fees that are not prominently + disclosed. Opacity is a regulatory risk, not a pricing strategy." + fintech_example: "A payments company conducts pricing diagnosis and discovers + that 60% of its revenue comes from interchange on debit transactions — + revenue that is capped by the Durbin Amendment and could be further + compressed by proposed legislation. The diagnosis reveals that the + company's premium services (fraud analytics, financial reporting, lending + integration) are under-priced relative to the value delivered because they + were originally bundled 'free' with payment processing. The prescription: + unbundle value-add services into separately priced products that are not + subject to interchange regulation, shifting the revenue mix from regulated + (interchange) to unregulated (SaaS-like fees) over 18 months." + benchmark_references: [ "take-rate", "arpu", "gross-margin", "regulatory-compliance-cost" ] + kind: diagnostic + ref: pricing-diagnosis - skill: "systems-thinking" category: "frameworks" fintech_relevance: "high" - fintech_context: "Fintech businesses are complex adaptive systems with regulatory feedback loops that create non-obvious outcomes. The most important loops: (1) The compliance investment loop: investing in compliance enables licenses, which enable products, which generate revenue, which funds more compliance — or underinvesting triggers enforcement, which restricts products, which reduces revenue, which further reduces compliance investment. (2) The trust-growth loop: trust enables customer acquisition, usage generates data, data improves products and risk models, improved products deepen trust. (3) The credit spiral: loan origination generates interest income, income funds new origination, but loosening underwriting to grow origination increases defaults, which consume the interest income, requiring tighter underwriting, which reduces origination. (4) The banking partner dependency loop: growth requires a banking partner, partner enables growth, growth increases partner's regulatory exposure, partner imposes restrictions, restrictions constrain growth." + fintech_context: "Fintech businesses are complex adaptive systems with + regulatory feedback loops that create non-obvious outcomes. The most + important loops: (1) The compliance investment loop: investing in + compliance enables licenses, which enable products, which generate + revenue, which funds more compliance — or underinvesting triggers + enforcement, which restricts products, which reduces revenue, which + further reduces compliance investment. (2) The trust-growth loop: trust + enables customer acquisition, usage generates data, data improves products + and risk models, improved products deepen trust. (3) The credit spiral: + loan origination generates interest income, income funds new origination, + but loosening underwriting to grow origination increases defaults, which + consume the interest income, requiring tighter underwriting, which reduces + origination. (4) The banking partner dependency loop: growth requires a + banking partner, partner enables growth, growth increases partner's + regulatory exposure, partner imposes restrictions, restrictions constrain + growth." fintech_anti_patterns: - - "Treating compliance as a one-time cost rather than a feedback loop. Under-investment in compliance creates a negative spiral: enforcement action, operational restrictions, customer loss, revenue decline, further compliance under-investment." - - "Ignoring the time delays in credit risk feedback loops. Loose underwriting today generates revenue today but creates losses 6-18 months later. The delay makes the causal connection invisible to decision-makers focused on quarterly metrics." - - "Optimizing one metric without modeling regulatory second-order effects. Growing transaction volume rapidly may trigger enhanced BSA/AML monitoring requirements that overwhelm the compliance team, leading to suspicious activity reporting failures." - fintech_example: "A neobank discovers through systems analysis that its rapid customer growth is creating a negative feedback loop: more customers generate more transaction monitoring alerts, the compliance team cannot process alerts fast enough, alert backlogs trigger regulatory scrutiny, regulators impose growth restrictions until the backlog is cleared, restrictions slow customer acquisition. The system solution is not to hire more compliance analysts (linear scaling) but to invest in automated alert triage (exponential scaling) — a systems-level intervention that breaks the constraint on growth." - benchmark_references: ["regulatory-compliance-cost", "monthly-active-users", "fraud-rate"] + - "Treating compliance as a one-time cost rather than a feedback loop. + Under-investment in compliance creates a negative spiral: enforcement + action, operational restrictions, customer loss, revenue decline, + further compliance under-investment." + - "Ignoring the time delays in credit risk feedback loops. Loose + underwriting today generates revenue today but creates losses 6-18 + months later. The delay makes the causal connection invisible to + decision-makers focused on quarterly metrics." + - "Optimizing one metric without modeling regulatory second-order effects. + Growing transaction volume rapidly may trigger enhanced BSA/AML + monitoring requirements that overwhelm the compliance team, leading to + suspicious activity reporting failures." + fintech_example: "A neobank discovers through systems analysis that its rapid + customer growth is creating a negative feedback loop: more customers + generate more transaction monitoring alerts, the compliance team cannot + process alerts fast enough, alert backlogs trigger regulatory scrutiny, + regulators impose growth restrictions until the backlog is cleared, + restrictions slow customer acquisition. The system solution is not to hire + more compliance analysts (linear scaling) but to invest in automated alert + triage (exponential scaling) — a systems-level intervention that breaks + the constraint on growth." + benchmark_references: [ "regulatory-compliance-cost", "monthly-active-users", "fraud-rate" ] - skill: "cialdini-influence" category: "frameworks" fintech_relevance: "high" - fintech_context: "Cialdini's influence principles apply powerfully to fintech — but several operate under regulatory constraints. Scarcity is regulated: creating artificial urgency around financial products ('limited-time rate, apply now!') is scrutinized under UDAP/UDAAP if the scarcity is manufactured. Social Proof must be truthful: testimonials and performance claims for investment products are regulated by SEC and FINRA. Reciprocity works differently: free financial products (free checking, free trades) create obligation but must deliver genuine value — 'free' products that generate hidden revenue (payment for order flow, data selling) face regulatory backlash. Authority in fintech comes from regulatory credentials: FDIC insurance, state licenses, SOC 2 certification, and regulatory examination results carry more authority than celebrity endorsements. Commitment & Consistency drives financial product adoption: customers who set up direct deposit are dramatically more likely to use the product long-term." + fintech_context: "Cialdini's influence principles apply powerfully to fintech — + but several operate under regulatory constraints. Scarcity is regulated: + creating artificial urgency around financial products ('limited-time rate, + apply now!') is scrutinized under UDAP/UDAAP if the scarcity is + manufactured. Social Proof must be truthful: testimonials and performance + claims for investment products are regulated by SEC and FINRA. Reciprocity + works differently: free financial products (free checking, free trades) + create obligation but must deliver genuine value — 'free' products that + generate hidden revenue (payment for order flow, data selling) face + regulatory backlash. Authority in fintech comes from regulatory + credentials: FDIC insurance, state licenses, SOC 2 certification, and + regulatory examination results carry more authority than celebrity + endorsements. Commitment & Consistency drives financial product adoption: + customers who set up direct deposit are dramatically more likely to use + the product long-term." fintech_anti_patterns: - - "Using Scarcity tactics that violate financial advertising regulations. 'Only 48 hours to lock in this rate' is permissible if true; 'limited spots available' for a digital banking product with infinite capacity is deceptive." - - "Deploying Social Proof that constitutes a financial guarantee. 'Join 10M customers who trust us' is acceptable; 'our customers earn 12% returns' without proper disclaimers violates SEC advertising rules." - - "Relying on Authority signals that customers do not understand. Displaying a state banking license number is legally required but provides no authority to consumers. FDIC insurance badges, on the other hand, are immediately recognized and powerfully trust-building." - fintech_example: "Robinhood leveraged Commitment & Consistency (fractional shares lowered the commitment threshold, making everyone an 'investor'), Social Proof (referral waitlists created visible demand), and Authority (SEC-registered, SIPC-insured) to acquire 22M+ accounts. However, the company's use of gamification elements (confetti after trades) and the opacity of payment for order flow revenue created Self-Orientation concerns that eventually attracted FINRA fines and SEC scrutiny — demonstrating that Cialdini's principles must be applied within regulatory boundaries." - benchmark_references: ["cac", "monthly-active-users", "kyc-conversion-rate"] + - "Using Scarcity tactics that violate financial advertising regulations. + 'Only 48 hours to lock in this rate' is permissible if true; 'limited + spots available' for a digital banking product with infinite capacity is + deceptive." + - "Deploying Social Proof that constitutes a financial guarantee. 'Join + 10M customers who trust us' is acceptable; 'our customers earn 12% + returns' without proper disclaimers violates SEC advertising rules." + - "Relying on Authority signals that customers do not understand. + Displaying a state banking license number is legally required but + provides no authority to consumers. FDIC insurance badges, on the other + hand, are immediately recognized and powerfully trust-building." + fintech_example: "Robinhood leveraged Commitment & Consistency (fractional + shares lowered the commitment threshold, making everyone an 'investor'), + Social Proof (referral waitlists created visible demand), and Authority + (SEC-registered, SIPC-insured) to acquire 22M+ accounts. However, the + company's use of gamification elements (confetti after trades) and the + opacity of payment for order flow revenue created Self-Orientation + concerns that eventually attracted FINRA fines and SEC scrutiny — + demonstrating that Cialdini's principles must be applied within regulatory + boundaries." + benchmark_references: [ "cac", "monthly-active-users", "kyc-conversion-rate" ] - skill: "growth-share-matrix" category: "frameworks" fintech_relevance: "high" - fintech_context: "The BCG Growth-Share Matrix in fintech must account for regulatory capital allocation alongside financial capital. Stars (high growth, high share) may require disproportionate regulatory capital — a fast-growing lending product consumes capital reserves. Cash Cows (low growth, high share) in fintech are often legacy products with stable regulatory relationships and proven compliance — they fund the compliance build-out for new products. Question Marks must include the regulatory licensing timeline — a promising new product that requires a 2-year license acquisition is a very different Question Mark than one that operates under existing licenses. Dogs in fintech cannot always be killed — regulatory obligations may require maintaining products or services for existing customers even when they are uneconomic." + fintech_context: "The BCG Growth-Share Matrix in fintech must account for + regulatory capital allocation alongside financial capital. Stars (high + growth, high share) may require disproportionate regulatory capital — a + fast-growing lending product consumes capital reserves. Cash Cows (low + growth, high share) in fintech are often legacy products with stable + regulatory relationships and proven compliance — they fund the compliance + build-out for new products. Question Marks must include the regulatory + licensing timeline — a promising new product that requires a 2-year + license acquisition is a very different Question Mark than one that + operates under existing licenses. Dogs in fintech cannot always be killed + — regulatory obligations may require maintaining products or services for + existing customers even when they are uneconomic." fintech_anti_patterns: - - "Allocating resources solely based on market attractiveness without considering regulatory capital constraints. A Star product that requires 50% of available regulatory capital limits the entire portfolio." - - "Sunsetting Dog products without accounting for regulatory wind-down obligations. Customer notification requirements, data retention mandates, and account migration timelines constrain how quickly uneconomic products can be discontinued." - - "Ignoring the regulatory timeline for Question Marks. A product that requires a new license, charter amendment, or regulatory approval operates on regulatory time, not market time." - fintech_example: "A multi-product fintech maps its portfolio: Payments (Cash Cow — mature, high share, stable regulatory relationship), Lending (Star — growing rapidly but consuming capital reserves), Crypto custody (Question Mark — high growth market but regulatory framework uncertain), and Check cashing (Dog — declining, low margin, but regulatory obligations require continued service for existing customers). The matrix reveals that the Lending Star is consuming the capital that should fund the Crypto Question Mark's regulatory preparation — triggering a capital planning discussion with the board." - benchmark_references: ["gross-margin", "loan-origination-volume", "regulatory-compliance-cost"] + - "Allocating resources solely based on market attractiveness without + considering regulatory capital constraints. A Star product that requires + 50% of available regulatory capital limits the entire portfolio." + - "Sunsetting Dog products without accounting for regulatory wind-down + obligations. Customer notification requirements, data retention + mandates, and account migration timelines constrain how quickly + uneconomic products can be discontinued." + - "Ignoring the regulatory timeline for Question Marks. A product that + requires a new license, charter amendment, or regulatory approval + operates on regulatory time, not market time." + fintech_example: "A multi-product fintech maps its portfolio: Payments (Cash Cow + — mature, high share, stable regulatory relationship), Lending (Star — + growing rapidly but consuming capital reserves), Crypto custody (Question + Mark — high growth market but regulatory framework uncertain), and Check + cashing (Dog — declining, low margin, but regulatory obligations require + continued service for existing customers). The matrix reveals that the + Lending Star is consuming the capital that should fund the Crypto Question + Mark's regulatory preparation — triggering a capital planning discussion + with the board." + benchmark_references: [ "gross-margin", "loan-origination-volume", "regulatory-compliance-cost" ] - skill: "doblin-ten-types" category: "frameworks" fintech_relevance: "high" - fintech_context: "The Ten Types of Innovation framework reveals that the most successful fintech innovations occur outside the Product Performance dimension. Profit Model innovation is central: subscription-based financial services, zero-commission trading, BNPL — each is a Profit Model innovation applied to financial services. Network innovation through open banking APIs, banking-as-a-service, and embedded finance creates ecosystem value. Process innovation through automated compliance, AI-driven underwriting, and real-time payments transforms operational economics. Channel innovation through embedded finance (Shopify Capital, Uber driver lending) places financial services at the point of need. Customer Engagement innovation through financial literacy tools, spend categorization, and savings gamification builds emotional connection." + fintech_context: "The Ten Types of Innovation framework reveals that the most + successful fintech innovations occur outside the Product Performance + dimension. Profit Model innovation is central: subscription-based + financial services, zero-commission trading, BNPL — each is a Profit Model + innovation applied to financial services. Network innovation through open + banking APIs, banking-as-a-service, and embedded finance creates ecosystem + value. Process innovation through automated compliance, AI-driven + underwriting, and real-time payments transforms operational economics. + Channel innovation through embedded finance (Shopify Capital, Uber driver + lending) places financial services at the point of need. Customer + Engagement innovation through financial literacy tools, spend + categorization, and savings gamification builds emotional connection." fintech_anti_patterns: - - "Innovating on Product Performance (features) while ignoring Profit Model constraints. A more feature-rich lending product is useless if the interest rate is capped by regulation and the cost to serve exceeds the margin." - - "Neglecting Process innovation in compliance. The fintech with the most efficient compliance process (lowest cost per SAR, fastest KYC, most accurate transaction monitoring) has a structural cost advantage that compounds at scale." - - "Ignoring Service innovation. Financial products are confusing and stressful for customers. Service innovations (real-time support, transparent status tracking, proactive financial guidance) build trust and reduce churn." - fintech_example: "Stripe's success maps across multiple innovation types: Process (one-line API integration vs. months of payment gateway setup), Network (developer ecosystem creating distribution), Profit Model (pay-per-transaction vs. monthly minimums and setup fees), Channel (embedded directly in developers' code), and Structure (remote-first global team accessing talent globally). Product Performance (payment processing itself) was deliberately NOT the primary innovation — Stripe processes payments through existing infrastructure. The multi-type innovation created compound defensibility that commodity processors could not replicate." - benchmark_references: ["cac", "cost-per-transaction", "kyc-cost-per-customer"] + - "Innovating on Product Performance (features) while ignoring Profit + Model constraints. A more feature-rich lending product is useless if the + interest rate is capped by regulation and the cost to serve exceeds the + margin." + - "Neglecting Process innovation in compliance. The fintech with the most + efficient compliance process (lowest cost per SAR, fastest KYC, most + accurate transaction monitoring) has a structural cost advantage that + compounds at scale." + - "Ignoring Service innovation. Financial products are confusing and + stressful for customers. Service innovations (real-time support, + transparent status tracking, proactive financial guidance) build trust + and reduce churn." + fintech_example: "Stripe's success maps across multiple innovation types: + Process (one-line API integration vs. months of payment gateway setup), + Network (developer ecosystem creating distribution), Profit Model + (pay-per-transaction vs. monthly minimums and setup fees), Channel + (embedded directly in developers' code), and Structure (remote-first + global team accessing talent globally). Product Performance (payment + processing itself) was deliberately NOT the primary innovation — Stripe + processes payments through existing infrastructure. The multi-type + innovation created compound defensibility that commodity processors could + not replicate." + benchmark_references: [ "cac", "cost-per-transaction", "kyc-cost-per-customer" ] - skill: "eisenhower-matrix" category: "frameworks" fintech_relevance: "high" - fintech_context: "The Eisenhower Matrix in fintech is complicated by the fact that regulatory deadlines create non-negotiable urgency. Regulatory examination responses, license renewal deadlines, SAR filing requirements, and consent order compliance timelines are all Urgent AND Important — they cannot be deprioritized. This compresses the available bandwidth for Not Urgent/Important strategic work (product vision, market expansion, partnership development). The fintech-specific challenge is distinguishing between genuinely urgent compliance requirements and compliance theater (activities that feel urgent because they involve regulators but are not actually time-critical). BSA/AML transaction monitoring is Urgent/Important. Updating an internal compliance policy that is already effective is Not Urgent/Important." + fintech_context: "The Eisenhower Matrix in fintech is complicated by the fact + that regulatory deadlines create non-negotiable urgency. Regulatory + examination responses, license renewal deadlines, SAR filing requirements, + and consent order compliance timelines are all Urgent AND Important — they + cannot be deprioritized. This compresses the available bandwidth for Not + Urgent/Important strategic work (product vision, market expansion, + partnership development). The fintech-specific challenge is distinguishing + between genuinely urgent compliance requirements and compliance theater + (activities that feel urgent because they involve regulators but are not + actually time-critical). BSA/AML transaction monitoring is + Urgent/Important. Updating an internal compliance policy that is already + effective is Not Urgent/Important." fintech_anti_patterns: - - "Treating all regulatory activities as Urgent/Important. Compliance work ranges from genuinely urgent (SAR filing within 30 days of detection) to strategically important but not urgent (building a compliance training program) to busywork (reformatting existing policies for aesthetic reasons)." - - "Deprioritizing compliance infrastructure as Not Urgent because no regulator has asked about it yet. The absence of regulatory inquiry is not evidence that compliance is adequate — it is evidence that you have not been examined." - - "Delegating regulatory relationship management. The CEO's relationship with regulators is Urgent/Important and cannot be delegated — regulatory goodwill is a strategic asset." - fintech_example: "A fintech CEO uses the Eisenhower Matrix to discover that 50% of leadership time is consumed by Urgent/Not Important activities: responding to banking partner operational requests, reviewing routine compliance reports that the CCO should own, and attending standing meetings with external counsel that could be async. The critical finding: Not Urgent/Important activities — building a second banking partner relationship, preparing for future regulatory examinations, developing the compliance technology roadmap — receive zero time. The matrix restructuring frees 10 hours per week for strategic compliance and growth work." - benchmark_references: ["regulatory-compliance-cost"] + - "Treating all regulatory activities as Urgent/Important. Compliance work + ranges from genuinely urgent (SAR filing within 30 days of detection) to + strategically important but not urgent (building a compliance training + program) to busywork (reformatting existing policies for aesthetic + reasons)." + - "Deprioritizing compliance infrastructure as Not Urgent because no + regulator has asked about it yet. The absence of regulatory inquiry is + not evidence that compliance is adequate — it is evidence that you have + not been examined." + - "Delegating regulatory relationship management. The CEO's relationship + with regulators is Urgent/Important and cannot be delegated — regulatory + goodwill is a strategic asset." + fintech_example: "A fintech CEO uses the Eisenhower Matrix to discover that 50% + of leadership time is consumed by Urgent/Not Important activities: + responding to banking partner operational requests, reviewing routine + compliance reports that the CCO should own, and attending standing + meetings with external counsel that could be async. The critical finding: + Not Urgent/Important activities — building a second banking partner + relationship, preparing for future regulatory examinations, developing the + compliance technology roadmap — receive zero time. The matrix + restructuring frees 10 hours per week for strategic compliance and growth + work." + benchmark_references: [ "regulatory-compliance-cost" ] - skill: "emotional-intelligence" category: "frameworks" fintech_relevance: "high" - fintech_context: "Emotional intelligence in fintech extends beyond interpersonal dynamics to a specific domain: managing the emotional weight of handling other people's money. Customers who experience financial distress (account freezes, loan denials, fraud on their accounts) are in heightened emotional states that require specific EI competencies. Regulators who examine the company are human beings whose concerns must be understood and addressed with emotional sophistication — adversarial regulatory relationships lead to enforcement actions. Banking partners experience anxiety about regulatory risk that manifests as restrictive behavior — understanding and addressing their emotional concerns (not just their contractual requirements) maintains critical partnerships." + fintech_context: "Emotional intelligence in fintech extends beyond interpersonal + dynamics to a specific domain: managing the emotional weight of handling + other people's money. Customers who experience financial distress (account + freezes, loan denials, fraud on their accounts) are in heightened + emotional states that require specific EI competencies. Regulators who + examine the company are human beings whose concerns must be understood and + addressed with emotional sophistication — adversarial regulatory + relationships lead to enforcement actions. Banking partners experience + anxiety about regulatory risk that manifests as restrictive behavior — + understanding and addressing their emotional concerns (not just their + contractual requirements) maintains critical partnerships." fintech_anti_patterns: - - "Treating customer financial distress as a purely operational issue. A customer whose account is frozen due to a false-positive fraud alert is not a 'ticket to resolve' — they are a person who cannot access their money. The emotional dimension of financial services failures is categorically different from a software bug." - - "Approaching regulatory examinations as adversarial. Regulators are executing a mandate; meeting them with defensiveness rather than transparency and collaboration escalates the examination and increases enforcement risk." - - "Ignoring the emotional toll on compliance and risk teams. People who spend their days reviewing fraud cases, suspicious activity, and financial crimes experience secondary trauma. EI for fintech leaders includes caring for these teams." - fintech_example: "A neobank's VP of Customer Success applies emotional intelligence during a regulatory-mandated mass account review that requires freezing 2,000 accounts for enhanced due diligence. Rather than sending form letters, the team implements personalized outreach explaining the review, providing a timeline, and offering alternative access to funds where possible. The EI-informed approach transforms a potential PR crisis into a trust-building moment — customers who felt respected during the process became more loyal than customers who never experienced the freeze." - benchmark_references: ["monthly-active-users", "net-revenue-retention"] + - "Treating customer financial distress as a purely operational issue. A + customer whose account is frozen due to a false-positive fraud alert is + not a 'ticket to resolve' — they are a person who cannot access their + money. The emotional dimension of financial services failures is + categorically different from a software bug." + - "Approaching regulatory examinations as adversarial. Regulators are + executing a mandate; meeting them with defensiveness rather than + transparency and collaboration escalates the examination and increases + enforcement risk." + - "Ignoring the emotional toll on compliance and risk teams. People who + spend their days reviewing fraud cases, suspicious activity, and + financial crimes experience secondary trauma. EI for fintech leaders + includes caring for these teams." + fintech_example: "A neobank's VP of Customer Success applies emotional + intelligence during a regulatory-mandated mass account review that + requires freezing 2,000 accounts for enhanced due diligence. Rather than + sending form letters, the team implements personalized outreach explaining + the review, providing a timeline, and offering alternative access to funds + where possible. The EI-informed approach transforms a potential PR crisis + into a trust-building moment — customers who felt respected during the + process became more loyal than customers who never experienced the + freeze." + benchmark_references: [ "monthly-active-users", "net-revenue-retention" ] - skill: "black-swans" category: "frameworks" fintech_relevance: "critical" - fintech_context: "Fintech is uniquely exposed to black swan events because financial systems are interconnected, leveraged, and trust-dependent. A black swan in fintech can propagate through the system: a BaaS provider failure can freeze customer funds for dozens of fintech companies (as the Synapse collapse demonstrated in 2024). A sovereign debt crisis can freeze cross-border payment corridors overnight. A zero-day vulnerability in a widely-used identity verification API can expose millions of KYC records. A regulatory enforcement action against one prominent fintech can trigger enhanced scrutiny of the entire sector. The black swan framework must be applied not just to the company's own operations but to its banking partners, technology providers, regulatory environment, and the broader financial system." + fintech_context: "Fintech is uniquely exposed to black swan events because + financial systems are interconnected, leveraged, and trust-dependent. A + black swan in fintech can propagate through the system: a BaaS provider + failure can freeze customer funds for dozens of fintech companies (as the + Synapse collapse demonstrated in 2024). A sovereign debt crisis can freeze + cross-border payment corridors overnight. A zero-day vulnerability in a + widely-used identity verification API can expose millions of KYC records. + A regulatory enforcement action against one prominent fintech can trigger + enhanced scrutiny of the entire sector. The black swan framework must be + applied not just to the company's own operations but to its banking + partners, technology providers, regulatory environment, and the broader + financial system." fintech_anti_patterns: - - "Assuming partner stability. The Synapse BaaS failure in 2024 demonstrated that a banking-as-a-service provider collapse can freeze customer funds across dozens of fintech companies. Partner risk IS company risk." - - "Ignoring correlated risks. A credit cycle downturn simultaneously increases default rates, reduces transaction volume, tightens funding markets, and intensifies regulatory scrutiny — these are not independent events." - - "Treating cybersecurity as an IT concern rather than an existential risk. A data breach at a fintech is not a PR problem — it is a regulatory enforcement trigger, a customer trust destroyer, and potentially a company-ending event." - fintech_example: "The Synapse BaaS collapse in 2024 was a black swan for the fintech companies that relied on it. Customer funds were frozen for months, regulatory investigations were launched, and several fintech companies faced existential crises. The lesson for black swan planning: fintech companies must stress-test their banking partner dependencies, maintain contingency plans for partner failure, ensure customer funds are properly segregated and reconciled, and — most critically — understand the regulatory framework governing their banking relationships deeply enough to protect customers when the unexpected occurs." - benchmark_references: ["capital-adequacy-ratio", "fraud-rate", "regulatory-compliance-cost"] + - "Assuming partner stability. The Synapse BaaS failure in 2024 + demonstrated that a banking-as-a-service provider collapse can freeze + customer funds across dozens of fintech companies. Partner risk IS + company risk." + - "Ignoring correlated risks. A credit cycle downturn simultaneously + increases default rates, reduces transaction volume, tightens funding + markets, and intensifies regulatory scrutiny — these are not independent + events." + - "Treating cybersecurity as an IT concern rather than an existential + risk. A data breach at a fintech is not a PR problem — it is a + regulatory enforcement trigger, a customer trust destroyer, and + potentially a company-ending event." + fintech_example: "The Synapse BaaS collapse in 2024 was a black swan for the + fintech companies that relied on it. Customer funds were frozen for + months, regulatory investigations were launched, and several fintech + companies faced existential crises. The lesson for black swan planning: + fintech companies must stress-test their banking partner dependencies, + maintain contingency plans for partner failure, ensure customer funds are + properly segregated and reconciled, and — most critically — understand the + regulatory framework governing their banking relationships deeply enough + to protect customers when the unexpected occurs." + benchmark_references: [ "capital-adequacy-ratio", "fraud-rate", "regulatory-compliance-cost" ] # ───────────────────────────────────────────── # GAME THEORY (5 skills) @@ -259,57 +811,210 @@ skill_overlays: - skill: "game-theory-fundamentals" category: "game-theory" fintech_relevance: "critical" - fintech_context: "Fintech operates within a multi-player game that includes a uniquely powerful player: the regulator. Unlike traditional competitive games where all players follow the same rules, the regulator writes the rules, enforces them asymmetrically, and can change them mid-game. Game theory in fintech must model: (1) The regulatory game — compliance as a cooperative game with regulators where good-faith collaboration yields better outcomes than adversarial minimum compliance. (2) The competitive game — where regulatory barriers create oligopolistic dynamics and compliance capability is a competitive weapon. (3) The partnership game — where banking partners, card networks, and identity providers are simultaneously cooperators and potential competitors. (4) The trust game — where customer trust is a repeated game and a single defection (breach, fraud, hidden fee) can terminate the relationship permanently." + fintech_context: "Fintech operates within a multi-player game that includes a + uniquely powerful player: the regulator. Unlike traditional competitive + games where all players follow the same rules, the regulator writes the + rules, enforces them asymmetrically, and can change them mid-game. Game + theory in fintech must model: (1) The regulatory game — compliance as a + cooperative game with regulators where good-faith collaboration yields + better outcomes than adversarial minimum compliance. (2) The competitive + game — where regulatory barriers create oligopolistic dynamics and + compliance capability is a competitive weapon. (3) The partnership game — + where banking partners, card networks, and identity providers are + simultaneously cooperators and potential competitors. (4) The trust game — + where customer trust is a repeated game and a single defection (breach, + fraud, hidden fee) can terminate the relationship permanently." fintech_anti_patterns: - - "Modeling the competitive game without the regulatory player. Fintech strategy that ignores how regulators will react to competitive moves is fatally incomplete. Aggressive pricing, rapid expansion, or innovative product launches all have regulatory implications." - - "Treating regulatory compliance as a one-shot game. It is a repeated game with memory — regulators remember past behavior. A fintech with a history of good-faith compliance receives more favorable treatment than one with a history of resistance." - - "Applying zero-sum thinking to the regulatory relationship. The regulator's goal (consumer protection, financial stability) is not opposed to the fintech's goal (growth, profitability) — regulatory compliance and commercial success can be aligned." - fintech_example: "A payments company analyzes its competitive dynamics as a three-player game: the company, a direct competitor, and the state regulator considering new licensing requirements. If both companies lobby against the regulation, it may be blocked but at reputational cost. If the company embraces the regulation while the competitor opposes it, the company gains regulatory goodwill and the competitor faces enforcement risk. The Nash equilibrium analysis reveals that proactive regulatory engagement (cooperate with the regulator) is the dominant strategy — the company that embraces regulation earliest converts a constraint into a competitive advantage." - benchmark_references: ["regulatory-compliance-cost", "take-rate"] + - "Modeling the competitive game without the regulatory player. Fintech + strategy that ignores how regulators will react to competitive moves is + fatally incomplete. Aggressive pricing, rapid expansion, or innovative + product launches all have regulatory implications." + - "Treating regulatory compliance as a one-shot game. It is a repeated + game with memory — regulators remember past behavior. A fintech with a + history of good-faith compliance receives more favorable treatment than + one with a history of resistance." + - "Applying zero-sum thinking to the regulatory relationship. The + regulator's goal (consumer protection, financial stability) is not + opposed to the fintech's goal (growth, profitability) — regulatory + compliance and commercial success can be aligned." + fintech_example: "A payments company analyzes its competitive dynamics as a + three-player game: the company, a direct competitor, and the state + regulator considering new licensing requirements. If both companies lobby + against the regulation, it may be blocked but at reputational cost. If the + company embraces the regulation while the competitor opposes it, the + company gains regulatory goodwill and the competitor faces enforcement + risk. The Nash equilibrium analysis reveals that proactive regulatory + engagement (cooperate with the regulator) is the dominant strategy — the + company that embraces regulation earliest converts a constraint into a + competitive advantage." + benchmark_references: [ "regulatory-compliance-cost", "take-rate" ] - skill: "prisoners-dilemma-and-cooperation" category: "game-theory" fintech_relevance: "critical" - fintech_context: "The Prisoner's Dilemma appears repeatedly in fintech: in industry-wide compliance standards (if all companies invest in AML, the ecosystem is safer; if one defects by under-investing, they gain a cost advantage until caught), in data sharing for fraud prevention (sharing fraud data helps everyone but revealing patterns might help competitors), and in banking partnerships (both parties benefit from cooperation but each has incentives to extract more value). The most consequential dilemma is the compliance investment dilemma: every fintech that under-invests in compliance gains a short-term cost advantage but creates systemic risk that triggers regulatory crackdowns affecting the entire industry. The 2023-2024 wave of consent orders against neobanks demonstrated the collective punishment that follows when individual players defect on compliance." + fintech_context: "The Prisoner's Dilemma appears repeatedly in fintech: in + industry-wide compliance standards (if all companies invest in AML, the + ecosystem is safer; if one defects by under-investing, they gain a cost + advantage until caught), in data sharing for fraud prevention (sharing + fraud data helps everyone but revealing patterns might help competitors), + and in banking partnerships (both parties benefit from cooperation but + each has incentives to extract more value). The most consequential dilemma + is the compliance investment dilemma: every fintech that under-invests in + compliance gains a short-term cost advantage but creates systemic risk + that triggers regulatory crackdowns affecting the entire industry. The + 2023-2024 wave of consent orders against neobanks demonstrated the + collective punishment that follows when individual players defect on + compliance." fintech_anti_patterns: - - "Defecting on compliance investment because competitors appear to be under-investing. The short-term cost advantage of compliance under-investment is dwarfed by the expected cost of enforcement actions — the game is iterated, and the regulator always detects defection eventually." - - "Refusing to participate in industry fraud data sharing networks because of competitive concerns. The collective benefit of fraud network disruption outweighs the marginal competitive information shared." - - "Treating the banking partner relationship as exploitative rather than cooperative. Fintechs that extract maximum value from banking partners while contributing minimum compliance effort face relationship termination — the partner will defect when the regulatory risk exceeds the revenue benefit." - fintech_example: "The fintech industry's response to the Synapse BaaS collapse illustrates the Prisoner's Dilemma in action. Before the collapse, individual fintechs had incentives to minimize banking partner due diligence (cost savings). After the collapse, every fintech in the BaaS ecosystem faced enhanced scrutiny because the industry had collectively under-invested in partner oversight. The Nash equilibrium shifted: regulatory attention made compliance cooperation the dominant strategy. Industry groups formed to establish BaaS oversight standards — a cooperative equilibrium enforced by the regulatory threat." - benchmark_references: ["regulatory-compliance-cost", "fraud-rate"] + - "Defecting on compliance investment because competitors appear to be + under-investing. The short-term cost advantage of compliance + under-investment is dwarfed by the expected cost of enforcement actions + — the game is iterated, and the regulator always detects defection + eventually." + - "Refusing to participate in industry fraud data sharing networks because + of competitive concerns. The collective benefit of fraud network + disruption outweighs the marginal competitive information shared." + - "Treating the banking partner relationship as exploitative rather than + cooperative. Fintechs that extract maximum value from banking partners + while contributing minimum compliance effort face relationship + termination — the partner will defect when the regulatory risk exceeds + the revenue benefit." + fintech_example: "The fintech industry's response to the Synapse BaaS collapse + illustrates the Prisoner's Dilemma in action. Before the collapse, + individual fintechs had incentives to minimize banking partner due + diligence (cost savings). After the collapse, every fintech in the BaaS + ecosystem faced enhanced scrutiny because the industry had collectively + under-invested in partner oversight. The Nash equilibrium shifted: + regulatory attention made compliance cooperation the dominant strategy. + Industry groups formed to establish BaaS oversight standards — a + cooperative equilibrium enforced by the regulatory threat." + benchmark_references: [ "regulatory-compliance-cost", "fraud-rate" ] - skill: "first-mover-strategy" category: "game-theory" fintech_relevance: "high" - fintech_context: "First-mover advantage in fintech is complicated by the regulatory approval timeline. A fintech can be first-to-market with a product concept but blocked from launch by licensing delays — creating a window for competitors who find faster regulatory pathways. Conversely, being the first company to obtain a specific license or charter creates a durable advantage because the regulatory process acts as a years-long barrier to entry. The most powerful first-mover advantages in fintech are regulatory: being the first to obtain a bank charter (Varo), the first to gain a BitLicense (Circle), or the first to secure approval for a novel product structure creates moats that market-based first-mover advantages cannot match." + fintech_context: "First-mover advantage in fintech is complicated by the + regulatory approval timeline. A fintech can be first-to-market with a + product concept but blocked from launch by licensing delays — creating a + window for competitors who find faster regulatory pathways. Conversely, + being the first company to obtain a specific license or charter creates a + durable advantage because the regulatory process acts as a years-long + barrier to entry. The most powerful first-mover advantages in fintech are + regulatory: being the first to obtain a bank charter (Varo), the first to + gain a BitLicense (Circle), or the first to secure approval for a novel + product structure creates moats that market-based first-mover advantages + cannot match." fintech_anti_patterns: - - "Racing to launch before regulatory approval is complete. First-to-market with an unlicensed product is not a first-mover advantage — it is a violation. The penalty for operating without required licenses far exceeds any revenue gained." - - "Assuming first-mover advantage is permanent in regulated markets. Regulators can mandate interoperability (open banking), eliminate proprietary advantages (data portability), or create new competitive pathways (new charter types) that erode first-mover moats." - - "Ignoring the second-mover advantage in fintech compliance. Second movers can learn from the first mover's regulatory mistakes and compliance costs, often launching with better compliance at lower cost." - fintech_example: "Varo Bank became the first consumer fintech to receive a national bank charter from the OCC in 2020. This first-mover advantage was regulatory in nature: the charter application process took over three years and cost tens of millions in legal and compliance preparation. Competing fintechs who started the charter process later (Revolut, SoFi) faced similar timelines. Varo's first-mover advantage was not in product innovation but in regulatory positioning — the charter enabled deposit-funded lending with dramatically better unit economics than the BaaS-dependent model competitors were forced to use." - benchmark_references: ["net-interest-margin", "regulatory-compliance-cost", "capital-adequacy-ratio"] + - "Racing to launch before regulatory approval is complete. + First-to-market with an unlicensed product is not a first-mover + advantage — it is a violation. The penalty for operating without + required licenses far exceeds any revenue gained." + - "Assuming first-mover advantage is permanent in regulated markets. + Regulators can mandate interoperability (open banking), eliminate + proprietary advantages (data portability), or create new competitive + pathways (new charter types) that erode first-mover moats." + - "Ignoring the second-mover advantage in fintech compliance. Second + movers can learn from the first mover's regulatory mistakes and + compliance costs, often launching with better compliance at lower cost." + fintech_example: "Varo Bank became the first consumer fintech to receive a + national bank charter from the OCC in 2020. This first-mover advantage was + regulatory in nature: the charter application process took over three + years and cost tens of millions in legal and compliance preparation. + Competing fintechs who started the charter process later (Revolut, SoFi) + faced similar timelines. Varo's first-mover advantage was not in product + innovation but in regulatory positioning — the charter enabled + deposit-funded lending with dramatically better unit economics than the + BaaS-dependent model competitors were forced to use." + benchmark_references: + [ + "net-interest-margin", + "regulatory-compliance-cost", + "capital-adequacy-ratio" + ] - skill: "information-asymmetry" category: "game-theory" fintech_relevance: "critical" - fintech_context: "Information asymmetry is the foundational problem that financial regulation exists to address. Lenders know less about borrowers than borrowers know about themselves (adverse selection). Borrowers may take on more risk after obtaining a loan (moral hazard). Customers do not understand complex financial product terms (information asymmetry in pricing). Fintech innovation either reduces or exploits these asymmetries — and the regulatory response depends on which. Fintechs that use alternative data to reduce information asymmetry in credit underwriting (reducing adverse selection) are generally embraced by regulators. Fintechs that exploit information asymmetry to sell opaque products to unsophisticated consumers (increasing asymmetry) face enforcement. The regulatory lens is: does this innovation make information more symmetric or less?" + fintech_context: "Information asymmetry is the foundational problem that + financial regulation exists to address. Lenders know less about borrowers + than borrowers know about themselves (adverse selection). Borrowers may + take on more risk after obtaining a loan (moral hazard). Customers do not + understand complex financial product terms (information asymmetry in + pricing). Fintech innovation either reduces or exploits these asymmetries + — and the regulatory response depends on which. Fintechs that use + alternative data to reduce information asymmetry in credit underwriting + (reducing adverse selection) are generally embraced by regulators. + Fintechs that exploit information asymmetry to sell opaque products to + unsophisticated consumers (increasing asymmetry) face enforcement. The + regulatory lens is: does this innovation make information more symmetric + or less?" fintech_anti_patterns: - - "Exploiting information asymmetry in product design. Complex fee structures, opaque pricing, and deliberately confusing terms may increase short-term revenue but trigger UDAP/UDAAP enforcement and destroy trust." - - "Ignoring adverse selection in lending. Without robust underwriting, lending platforms attract the borrowers that traditional lenders have already rejected — the information asymmetry problem that has driven lending regulation for centuries." - - "Failing to recognize that regulators exist to address information asymmetry. Financial regulation is fundamentally about leveling the information playing field. Innovations that align with this goal receive regulatory support; innovations that oppose it receive enforcement." - fintech_example: "Upstart's approach to information asymmetry in lending demonstrates the regulatory-innovation alignment. Traditional credit scoring uses limited variables (FICO, income, debt ratio), creating information asymmetry where the lender cannot distinguish between borrowers with similar scores but different true risk profiles. Upstart's AI model incorporates additional variables (education, employment history, cost of living) to reduce this asymmetry. Critically, Upstart obtained a CFPB no-action letter by demonstrating that its model expanded credit access without increasing risk — the innovation reduced information asymmetry, aligning with regulatory goals. The company openly publishes fair lending analysis, further reducing the asymmetry between regulator and lender." - benchmark_references: ["default-rate", "loan-origination-volume"] + - "Exploiting information asymmetry in product design. Complex fee + structures, opaque pricing, and deliberately confusing terms may + increase short-term revenue but trigger UDAP/UDAAP enforcement and + destroy trust." + - "Ignoring adverse selection in lending. Without robust underwriting, + lending platforms attract the borrowers that traditional lenders have + already rejected — the information asymmetry problem that has driven + lending regulation for centuries." + - "Failing to recognize that regulators exist to address information + asymmetry. Financial regulation is fundamentally about leveling the + information playing field. Innovations that align with this goal receive + regulatory support; innovations that oppose it receive enforcement." + fintech_example: "Upstart's approach to information asymmetry in lending + demonstrates the regulatory-innovation alignment. Traditional credit + scoring uses limited variables (FICO, income, debt ratio), creating + information asymmetry where the lender cannot distinguish between + borrowers with similar scores but different true risk profiles. Upstart's + AI model incorporates additional variables (education, employment history, + cost of living) to reduce this asymmetry. Critically, Upstart obtained a + CFPB no-action letter by demonstrating that its model expanded credit + access without increasing risk — the innovation reduced information + asymmetry, aligning with regulatory goals. The company openly publishes + fair lending analysis, further reducing the asymmetry between regulator + and lender." + benchmark_references: [ "default-rate", "loan-origination-volume" ] - skill: "coalition-and-partnership-games" category: "game-theory" fintech_relevance: "high" - fintech_context: "Coalition formation in fintech is shaped by the regulatory requirement for licensed intermediaries. Every fintech coalition must include at least one regulated entity — a bank, a broker-dealer, an insurance carrier — whose license enables the coalition's activities. This creates asymmetric coalition dynamics: the regulated entity has outsized power because their license is the enabling asset. Coalition games in fintech include: BaaS partnerships (fintech + bank), payment processing alliances (fintech + card network + issuing bank), lending marketplaces (fintech platform + multiple lending partners), and embedded finance (non-financial platform + fintech infrastructure provider). Each coalition must solve the regulatory allocation problem: who bears the compliance responsibility, and who bears the regulatory risk?" + fintech_context: "Coalition formation in fintech is shaped by the regulatory + requirement for licensed intermediaries. Every fintech coalition must + include at least one regulated entity — a bank, a broker-dealer, an + insurance carrier — whose license enables the coalition's activities. This + creates asymmetric coalition dynamics: the regulated entity has outsized + power because their license is the enabling asset. Coalition games in + fintech include: BaaS partnerships (fintech + bank), payment processing + alliances (fintech + card network + issuing bank), lending marketplaces + (fintech platform + multiple lending partners), and embedded finance + (non-financial platform + fintech infrastructure provider). Each coalition + must solve the regulatory allocation problem: who bears the compliance + responsibility, and who bears the regulatory risk?" fintech_anti_patterns: - - "Entering a coalition without understanding regulatory responsibility allocation. When a fintech uses a banking partner, the bank bears primary regulatory responsibility — but the fintech's actions create the bank's regulatory risk. This asymmetry must be explicitly addressed." - - "Forming coalitions based solely on commercial terms without assessing regulatory risk sharing. A bank partnership with attractive revenue terms but ambiguous compliance responsibility allocation is a liability, not an asset." - - "Ignoring the regulatory pressure on banking partners. OCC, FDIC, and Federal Reserve guidance on bank-fintech partnerships is tightening. Banking partners face increasing pressure to oversee fintech activities, which translates into operational restrictions on the fintech." - fintech_example: "The embedded finance coalition between Shopify and Stripe demonstrates effective coalition game theory. Shopify provides the merchant distribution (millions of merchants), Stripe provides the payment infrastructure and regulatory compliance layer, and Celtic Bank (Stripe's lending partner) provides the lending license. The coalition works because each player contributes a resource the others cannot efficiently build (distribution, infrastructure, license), and the regulatory responsibility is clearly allocated — Stripe handles PCI-DSS and payment compliance, Celtic Bank handles lending regulation, and Shopify handles the merchant relationship. The coalition creates value that no individual player could create alone." - benchmark_references: ["tpv", "cac", "regulatory-compliance-cost"] + - "Entering a coalition without understanding regulatory responsibility + allocation. When a fintech uses a banking partner, the bank bears + primary regulatory responsibility — but the fintech's actions create the + bank's regulatory risk. This asymmetry must be explicitly addressed." + - "Forming coalitions based solely on commercial terms without assessing + regulatory risk sharing. A bank partnership with attractive revenue + terms but ambiguous compliance responsibility allocation is a liability, + not an asset." + - "Ignoring the regulatory pressure on banking partners. OCC, FDIC, and + Federal Reserve guidance on bank-fintech partnerships is tightening. + Banking partners face increasing pressure to oversee fintech activities, + which translates into operational restrictions on the fintech." + fintech_example: "The embedded finance coalition between Shopify and Stripe + demonstrates effective coalition game theory. Shopify provides the + merchant distribution (millions of merchants), Stripe provides the payment + infrastructure and regulatory compliance layer, and Celtic Bank (Stripe's + lending partner) provides the lending license. The coalition works because + each player contributes a resource the others cannot efficiently build + (distribution, infrastructure, license), and the regulatory responsibility + is clearly allocated — Stripe handles PCI-DSS and payment compliance, + Celtic Bank handles lending regulation, and Shopify handles the merchant + relationship. The coalition creates value that no individual player could + create alone." + benchmark_references: [ "tpv", "cac", "regulatory-compliance-cost" ] # ───────────────────────────────────────────── # NEGOTIATION (3 skills) @@ -318,35 +1023,122 @@ skill_overlays: - skill: "competitive-negotiation" category: "negotiation" fintech_relevance: "high" - fintech_context: "Competitive negotiation in fintech occurs across three primary contexts: banking partner negotiations (the most critical — terms, compliance responsibility allocation, revenue sharing), regulatory negotiations (responding to examination findings, negotiating consent order terms, advocating for favorable regulatory interpretations), and enterprise client negotiations (compliance requirements embedded in contracts, data security addenda, regulatory representation clauses). Banking partner negotiations are uniquely high-stakes: the partner bank holds asymmetric power because their license enables the fintech's operations. Regulatory negotiations require a specific tone — adversarial negotiation tactics that work in commercial settings can backfire catastrophically with regulators." + fintech_context: "Competitive negotiation in fintech occurs across three primary + contexts: banking partner negotiations (the most critical — terms, + compliance responsibility allocation, revenue sharing), regulatory + negotiations (responding to examination findings, negotiating consent + order terms, advocating for favorable regulatory interpretations), and + enterprise client negotiations (compliance requirements embedded in + contracts, data security addenda, regulatory representation clauses). + Banking partner negotiations are uniquely high-stakes: the partner bank + holds asymmetric power because their license enables the fintech's + operations. Regulatory negotiations require a specific tone — adversarial + negotiation tactics that work in commercial settings can backfire + catastrophically with regulators." fintech_anti_patterns: - - "Applying aggressive negotiation tactics to regulatory interactions. Regulators have enforcement power that commercial counterparties do not. 'Hardball' with a regulator escalates to enforcement actions." - - "Negotiating banking partnership terms without independent regulatory counsel. Commercial terms that seem favorable may embed compliance obligations that are operationally impractical or financially ruinous." - - "Using competitive leverage (threatening to switch banks) with a banking partner during a regulatory examination period. The partner bank will prioritize its regulatory standing over the commercial relationship — every time." - fintech_example: "A fintech negotiates its banking partnership renewal after the partner bank receives regulatory guidance to strengthen fintech oversight. The bank proposes tripling compliance reporting requirements and imposing a 60-day termination clause. Rather than countering aggressively, the fintech prepares a detailed compliance portfolio demonstrating its existing controls, proposes a joint compliance committee with shared cost, and offers to undergo a voluntary third-party compliance audit. This cooperative approach preserves the relationship while addressing the bank's regulatory concern — competitive negotiation in fintech requires understanding that the real counterparty is often the regulator, not the negotiating partner." - benchmark_references: ["regulatory-compliance-cost", "take-rate"] + - "Applying aggressive negotiation tactics to regulatory interactions. + Regulators have enforcement power that commercial counterparties do not. + 'Hardball' with a regulator escalates to enforcement actions." + - "Negotiating banking partnership terms without independent regulatory + counsel. Commercial terms that seem favorable may embed compliance + obligations that are operationally impractical or financially ruinous." + - "Using competitive leverage (threatening to switch banks) with a banking + partner during a regulatory examination period. The partner bank will + prioritize its regulatory standing over the commercial relationship — + every time." + fintech_example: "A fintech negotiates its banking partnership renewal after the + partner bank receives regulatory guidance to strengthen fintech oversight. + The bank proposes tripling compliance reporting requirements and imposing + a 60-day termination clause. Rather than countering aggressively, the + fintech prepares a detailed compliance portfolio demonstrating its + existing controls, proposes a joint compliance committee with shared cost, + and offers to undergo a voluntary third-party compliance audit. This + cooperative approach preserves the relationship while addressing the + bank's regulatory concern — competitive negotiation in fintech requires + understanding that the real counterparty is often the regulator, not the + negotiating partner." + benchmark_references: [ "regulatory-compliance-cost", "take-rate" ] - skill: "cooperative-negotiation" category: "negotiation" fintech_relevance: "critical" - fintech_context: "Cooperative negotiation is the dominant strategy for fintech regulatory relationships. The regulatory examination process is fundamentally a negotiation — the regulator identifies concerns, the company proposes remediation, and both parties work toward an outcome that satisfies regulatory requirements while allowing business continuity. This negotiation is cooperative, not competitive — both parties benefit from a well-regulated, sustainable fintech. Cooperative negotiation also governs industry consortium formation (shared KYC utilities, fraud data networks, regulatory advocacy groups) where competitors must collaborate on non-competitive infrastructure. The embedded finance ecosystem depends on cooperative negotiation between platforms, infrastructure providers, and banks." + fintech_context: "Cooperative negotiation is the dominant strategy for fintech + regulatory relationships. The regulatory examination process is + fundamentally a negotiation — the regulator identifies concerns, the + company proposes remediation, and both parties work toward an outcome that + satisfies regulatory requirements while allowing business continuity. This + negotiation is cooperative, not competitive — both parties benefit from a + well-regulated, sustainable fintech. Cooperative negotiation also governs + industry consortium formation (shared KYC utilities, fraud data networks, + regulatory advocacy groups) where competitors must collaborate on + non-competitive infrastructure. The embedded finance ecosystem depends on + cooperative negotiation between platforms, infrastructure providers, and + banks." fintech_anti_patterns: - - "Treating regulatory examinations as adversarial. Examiners who feel the company is being obstructive escalate findings. Transparent, cooperative engagement results in better outcomes — examiners who feel the company is genuinely committed to compliance give the benefit of the doubt on ambiguous issues." - - "Negotiating data sharing agreements with competitive restrictions that prevent fraud prevention cooperation. In fintech, shared fraud intelligence is a collective good — restrictions that protect competitive advantage at the expense of fraud detection harm the ecosystem." - - "Entering multi-party partnerships (embedded finance) without cooperative framework agreements. Without explicit cooperation norms, partnership coalitions devolve into competitive extraction — each party trying to capture more of the value at others' expense." - fintech_example: "A group of competing neobanks forms a cooperative consortium to share anonymized fraud pattern data. Each participant feared sharing would help competitors. Cooperative negotiation produced a framework: data is anonymized and aggregated (no individual transaction data shared), contributions are measured and reciprocity enforced (free-riders are excluded), and a neutral third party manages the data (no participant gains competitive intelligence beyond fraud patterns). The result: all participants saw 30% improvement in fraud detection rates. The cooperative equilibrium proved more valuable than the competitive information each party feared sharing." - benchmark_references: ["fraud-rate", "fraud-loss-rate", "regulatory-compliance-cost"] + - "Treating regulatory examinations as adversarial. Examiners who feel the + company is being obstructive escalate findings. Transparent, cooperative + engagement results in better outcomes — examiners who feel the company + is genuinely committed to compliance give the benefit of the doubt on + ambiguous issues." + - "Negotiating data sharing agreements with competitive restrictions that + prevent fraud prevention cooperation. In fintech, shared fraud + intelligence is a collective good — restrictions that protect + competitive advantage at the expense of fraud detection harm the + ecosystem." + - "Entering multi-party partnerships (embedded finance) without + cooperative framework agreements. Without explicit cooperation norms, + partnership coalitions devolve into competitive extraction — each party + trying to capture more of the value at others' expense." + fintech_example: "A group of competing neobanks forms a cooperative consortium + to share anonymized fraud pattern data. Each participant feared sharing + would help competitors. Cooperative negotiation produced a framework: data + is anonymized and aggregated (no individual transaction data shared), + contributions are measured and reciprocity enforced (free-riders are + excluded), and a neutral third party manages the data (no participant + gains competitive intelligence beyond fraud patterns). The result: all + participants saw 30% improvement in fraud detection rates. The cooperative + equilibrium proved more valuable than the competitive information each + party feared sharing." + benchmark_references: [ "fraud-rate", "fraud-loss-rate", "regulatory-compliance-cost" ] - skill: "delivering-the-deal" category: "negotiation" fintech_relevance: "high" - fintech_context: "Deal execution in fintech is complicated by regulatory requirements embedded in every contract. Enterprise fintech deals require: regulatory compliance representations (the product complies with applicable laws), data security addenda (PCI-DSS, SOC 2, GDPR compliance), business continuity provisions (what happens if the fintech loses its license or banking partner), and regulatory change clauses (who bears the cost when regulations change). Banking partnership agreements require: compliance responsibility matrices (who does KYC, who files SARs), audit rights (the bank must be able to examine the fintech's compliance program), and termination triggers (regulatory events that allow immediate termination). These deal elements add 30-60 days to typical sales cycles." + fintech_context: "Deal execution in fintech is complicated by regulatory + requirements embedded in every contract. Enterprise fintech deals require: + regulatory compliance representations (the product complies with + applicable laws), data security addenda (PCI-DSS, SOC 2, GDPR compliance), + business continuity provisions (what happens if the fintech loses its + license or banking partner), and regulatory change clauses (who bears the + cost when regulations change). Banking partnership agreements require: + compliance responsibility matrices (who does KYC, who files SARs), audit + rights (the bank must be able to examine the fintech's compliance + program), and termination triggers (regulatory events that allow immediate + termination). These deal elements add 30-60 days to typical sales cycles." fintech_anti_patterns: - - "Attempting to close deals without pre-prepared compliance documentation. Enterprise buyers and banking partners request SOC 2 reports, PCI-DSS attestations, penetration test results, and regulatory licenses before closing. Not having these ready extends the sales cycle by months." - - "Ignoring regulatory change clauses in long-term contracts. A three-year contract without a mechanism to address regulatory changes (new compliance requirements, new fee caps) creates unpredictable risk for both parties." - - "Treating regulatory representations as boilerplate. Representing that your product 'complies with all applicable laws' creates legal liability. Each representation should be reviewed by regulatory counsel and scoped to specific regulations." - fintech_example: "A B2B fintech creates a 'regulatory deal kit' for enterprise sales: pre-completed SOC 2 Type II report, PCI-DSS Attestation of Compliance, state-by-state license registry, data processing agreement (GDPR-compliant), BSA/AML program summary, and penetration test results (redacted). The kit also includes a compliance responsibility matrix template that clearly allocates regulatory obligations between the fintech and the client. This kit reduces enterprise deal cycles from 120 days to 65 days by preempting the three most common stall points: security review, regulatory verification, and compliance responsibility negotiation." - benchmark_references: ["cac", "regulatory-compliance-cost"] + - "Attempting to close deals without pre-prepared compliance + documentation. Enterprise buyers and banking partners request SOC 2 + reports, PCI-DSS attestations, penetration test results, and regulatory + licenses before closing. Not having these ready extends the sales cycle + by months." + - "Ignoring regulatory change clauses in long-term contracts. A three-year + contract without a mechanism to address regulatory changes (new + compliance requirements, new fee caps) creates unpredictable risk for + both parties." + - "Treating regulatory representations as boilerplate. Representing that + your product 'complies with all applicable laws' creates legal + liability. Each representation should be reviewed by regulatory counsel + and scoped to specific regulations." + fintech_example: "A B2B fintech creates a 'regulatory deal kit' for enterprise + sales: pre-completed SOC 2 Type II report, PCI-DSS Attestation of + Compliance, state-by-state license registry, data processing agreement + (GDPR-compliant), BSA/AML program summary, and penetration test results + (redacted). The kit also includes a compliance responsibility matrix + template that clearly allocates regulatory obligations between the fintech + and the client. This kit reduces enterprise deal cycles from 120 days to + 65 days by preempting the three most common stall points: security review, + regulatory verification, and compliance responsibility negotiation." + benchmark_references: [ "cac", "regulatory-compliance-cost" ] # ───────────────────────────────────────────── # THINKING & DECISIONS (4 skills) @@ -355,46 +1147,173 @@ skill_overlays: - skill: "enemies-of-clear-thinking" category: "thinking" fintech_relevance: "critical" - fintech_context: "Fintech operators face cognitive biases amplified by the high-stakes, regulation-heavy nature of financial services. Survivorship bias: benchmarking against successful neobanks while ignoring the majority that failed or received enforcement actions. Sunk cost fallacy: continuing to invest in a banking partner relationship that is deteriorating because switching costs seem prohibitive. Confirmation bias: interpreting ambiguous compliance signals as 'no news is good news' rather than investigating potential violations. Anchoring: fixating on the initial take rate or NIM assumption when market conditions and regulations have shifted. Normalcy bias: assuming the current regulatory environment is permanent when legislative change is imminent. Optimism bias: under-estimating default rates and over-estimating credit model accuracy because the model has not yet been tested through a credit cycle." + fintech_context: "Fintech operators face cognitive biases amplified by the + high-stakes, regulation-heavy nature of financial services. Survivorship + bias: benchmarking against successful neobanks while ignoring the majority + that failed or received enforcement actions. Sunk cost fallacy: continuing + to invest in a banking partner relationship that is deteriorating because + switching costs seem prohibitive. Confirmation bias: interpreting + ambiguous compliance signals as 'no news is good news' rather than + investigating potential violations. Anchoring: fixating on the initial + take rate or NIM assumption when market conditions and regulations have + shifted. Normalcy bias: assuming the current regulatory environment is + permanent when legislative change is imminent. Optimism bias: + under-estimating default rates and over-estimating credit model accuracy + because the model has not yet been tested through a credit cycle." fintech_anti_patterns: - - "Using benign credit period data to validate credit models. A model that performs well during economic expansion has not been tested. Optimism bias makes founders believe their underwriting is superior when it may simply be untested." - - "Interpreting regulatory silence as regulatory approval. The absence of an enforcement action does not mean the company is compliant — it means the company has not yet been examined. Normalcy bias creates false security." - - "Anchoring on early vintage loan performance when projecting portfolio quality. Early borrowers are systematically different from later borrowers — they are typically lower risk because they self-select. Extrapolating early performance to the full portfolio is a textbook anchoring error." - fintech_example: "A lending fintech reports a 1% default rate and celebrates its underwriting model. An advisor trained in clear thinking identifies three biases: (1) Vintage bias — the portfolio is only 8 months old, and most defaults occur between months 12-24. (2) Survivorship bias — comparing to the 1% default rate of successful lending fintechs while ignoring the 5-10% default rates that caused several competitors to fail. (3) Confirmation bias — the team cites the 1% rate as evidence the model works while ignoring early delinquency signals that suggest default rates will rise. The clear-thinking intervention triggers a stress test that projects 3-4% default rates at portfolio maturity — fundamentally changing the capital planning." - benchmark_references: ["default-rate", "net-interest-margin", "loan-origination-volume"] + - "Using benign credit period data to validate credit models. A model that + performs well during economic expansion has not been tested. Optimism + bias makes founders believe their underwriting is superior when it may + simply be untested." + - "Interpreting regulatory silence as regulatory approval. The absence of + an enforcement action does not mean the company is compliant — it means + the company has not yet been examined. Normalcy bias creates false + security." + - "Anchoring on early vintage loan performance when projecting portfolio + quality. Early borrowers are systematically different from later + borrowers — they are typically lower risk because they self-select. + Extrapolating early performance to the full portfolio is a textbook + anchoring error." + fintech_example: "A lending fintech reports a 1% default rate and celebrates its + underwriting model. An advisor trained in clear thinking identifies three + biases: (1) Vintage bias — the portfolio is only 8 months old, and most + defaults occur between months 12-24. (2) Survivorship bias — comparing to + the 1% default rate of successful lending fintechs while ignoring the + 5-10% default rates that caused several competitors to fail. (3) + Confirmation bias — the team cites the 1% rate as evidence the model works + while ignoring early delinquency signals that suggest default rates will + rise. The clear-thinking intervention triggers a stress test that projects + 3-4% default rates at portfolio maturity — fundamentally changing the + capital planning." + benchmark_references: [ "default-rate", "net-interest-margin", "loan-origination-volume" ] - skill: "evaluating-and-deciding" category: "thinking" fintech_relevance: "high" - fintech_context: "Decision-making in fintech must account for a dimension absent in most industries: regulatory irreversibility. Some fintech decisions are irreversible not because of market dynamics but because of regulatory consequences. Launching a product without proper licensing cannot be 'undone' — the regulatory record of unlicensed activity persists. A compliance failure that triggers an enforcement action permanently alters the company's regulatory profile. The one-way-door / two-way-door framework must be expanded in fintech to include a third category: regulatory one-way doors — decisions that create permanent regulatory records regardless of whether they can be commercially reversed." + fintech_context: "Decision-making in fintech must account for a dimension absent + in most industries: regulatory irreversibility. Some fintech decisions are + irreversible not because of market dynamics but because of regulatory + consequences. Launching a product without proper licensing cannot be + 'undone' — the regulatory record of unlicensed activity persists. A + compliance failure that triggers an enforcement action permanently alters + the company's regulatory profile. The one-way-door / two-way-door + framework must be expanded in fintech to include a third category: + regulatory one-way doors — decisions that create permanent regulatory + records regardless of whether they can be commercially reversed." fintech_anti_patterns: - - "Treating regulatory decisions as two-way doors. Applying for a bank charter, launching a lending product, or entering a new regulated market creates regulatory obligations and records that cannot be reversed by simply stopping the activity." - - "Deciding by speed when the decision has regulatory implications. The 'move fast' ethos must be tempered by regulatory awareness — fast decisions that create compliance violations are expensive regardless of how quickly they were made." - - "Over-relying on data for credit decisions without understanding model risk management requirements. Regulators require that credit models be explainable, fair, and validated — a purely data-driven decision process that cannot explain its logic violates regulatory requirements (ECOA, FCRA, SR 11-7)." - fintech_example: "A fintech must decide whether to apply for a bank charter or continue operating through a banking partner. Applying the expanded one-way-door framework: Charter application is a regulatory one-way door — once filed, the company is under OCC supervision, must submit to examinations, and the application outcome becomes part of the permanent regulatory record. The partnership is a two-way door commercially but creates regulatory dependencies. The team analyzes both options through the regulatory irreversibility lens and decides to pursue the charter — accepting the regulatory one-way door because the long-term unit economics (deposit funding vs. warehouse lending) justify the permanent commitment." - benchmark_references: ["net-interest-margin", "regulatory-compliance-cost", "capital-adequacy-ratio"] + - "Treating regulatory decisions as two-way doors. Applying for a bank + charter, launching a lending product, or entering a new regulated market + creates regulatory obligations and records that cannot be reversed by + simply stopping the activity." + - "Deciding by speed when the decision has regulatory implications. The + 'move fast' ethos must be tempered by regulatory awareness — fast + decisions that create compliance violations are expensive regardless of + how quickly they were made." + - "Over-relying on data for credit decisions without understanding model + risk management requirements. Regulators require that credit models be + explainable, fair, and validated — a purely data-driven decision process + that cannot explain its logic violates regulatory requirements (ECOA, + FCRA, SR 11-7)." + fintech_example: "A fintech must decide whether to apply for a bank charter or + continue operating through a banking partner. Applying the expanded + one-way-door framework: Charter application is a regulatory one-way door — + once filed, the company is under OCC supervision, must submit to + examinations, and the application outcome becomes part of the permanent + regulatory record. The partnership is a two-way door commercially but + creates regulatory dependencies. The team analyzes both options through + the regulatory irreversibility lens and decides to pursue the charter — + accepting the regulatory one-way door because the long-term unit economics + (deposit funding vs. warehouse lending) justify the permanent commitment." + benchmark_references: + [ + "net-interest-margin", + "regulatory-compliance-cost", + "capital-adequacy-ratio" + ] - skill: "defining-and-exploring-problems" category: "thinking" fintech_relevance: "high" - fintech_context: "Problem definition in fintech must always ask: is this a market problem, a product problem, or a regulatory problem? These three root cause categories require fundamentally different solutions, and misdiagnosis is common. Declining transaction volume could be a market problem (competition, economic downturn), a product problem (UX friction, feature gaps), or a regulatory problem (compliance-driven account closures, new KYC requirements deterring customers). Rising default rates could be a credit model problem, an economic cycle problem, or a regulatory problem (adverse selection caused by new fair lending requirements). The discipline of separating market, product, and regulatory root causes prevents fintech teams from applying product solutions to regulatory problems." + fintech_context: "Problem definition in fintech must always ask: is this a + market problem, a product problem, or a regulatory problem? These three + root cause categories require fundamentally different solutions, and + misdiagnosis is common. Declining transaction volume could be a market + problem (competition, economic downturn), a product problem (UX friction, + feature gaps), or a regulatory problem (compliance-driven account + closures, new KYC requirements deterring customers). Rising default rates + could be a credit model problem, an economic cycle problem, or a + regulatory problem (adverse selection caused by new fair lending + requirements). The discipline of separating market, product, and + regulatory root causes prevents fintech teams from applying product + solutions to regulatory problems." fintech_anti_patterns: - - "Defining the problem as 'we need feature X' when the real problem is regulatory friction. Building a better payment screen does not solve the problem if customers are abandoning during KYC verification." - - "Framing regulatory requirements as problems to be solved rather than constraints to be optimized within. 'The problem is we need to do KYC' is wrong framing. 'The problem is our KYC process takes 4 minutes when it should take 30 seconds' is correct framing." - - "Conflating symptoms across different root cause categories. 'Customers are churning' is a symptom. If some churn is product-driven (bad UX), some is market-driven (competitor offering better rates), and some is compliance-driven (account closures from risk reviews), treating it as a single problem leads to solutions that address none of the causes." - fintech_example: "A neobank diagnoses 'declining growth' and the product team proposes building five new features. Rigorous problem exploration reveals three distinct problems: (1) KYC conversion dropped 15% after adding a new identity verification step required by updated BSA/AML guidance — a regulatory problem requiring UX optimization of the compliance flow. (2) New customer activation declined because the onboarding flow does not guide users to set up direct deposit — a product problem. (3) Marketing CAC increased 40% because a competitor launched a high-yield savings promotion — a market problem requiring competitive response. The product team's feature proposal would have addressed none of these actual problems." - benchmark_references: ["kyc-conversion-rate", "cac", "monthly-active-users"] + - "Defining the problem as 'we need feature X' when the real problem is + regulatory friction. Building a better payment screen does not solve the + problem if customers are abandoning during KYC verification." + - "Framing regulatory requirements as problems to be solved rather than + constraints to be optimized within. 'The problem is we need to do KYC' + is wrong framing. 'The problem is our KYC process takes 4 minutes when + it should take 30 seconds' is correct framing." + - "Conflating symptoms across different root cause categories. 'Customers + are churning' is a symptom. If some churn is product-driven (bad UX), + some is market-driven (competitor offering better rates), and some is + compliance-driven (account closures from risk reviews), treating it as a + single problem leads to solutions that address none of the causes." + fintech_example: "A neobank diagnoses 'declining growth' and the product team + proposes building five new features. Rigorous problem exploration reveals + three distinct problems: (1) KYC conversion dropped 15% after adding a new + identity verification step required by updated BSA/AML guidance — a + regulatory problem requiring UX optimization of the compliance flow. (2) + New customer activation declined because the onboarding flow does not + guide users to set up direct deposit — a product problem. (3) Marketing + CAC increased 40% because a competitor launched a high-yield savings + promotion — a market problem requiring competitive response. The product + team's feature proposal would have addressed none of these actual + problems." + benchmark_references: [ "kyc-conversion-rate", "cac", "monthly-active-users" ] - skill: "tough-decision-situations" category: "decisions" fintech_relevance: "critical" - fintech_context: "Fintech founders face uniquely difficult decisions that carry regulatory and legal consequences beyond commercial impact. Whether to self-report a compliance failure to regulators (legally required in many cases, strategically important in all). Whether to exit a banking partner relationship when the partner faces regulatory issues (staying risks contagion, leaving disrupts operations). Whether to restrict a profitable product when internal compliance review identifies potential fair lending issues (short-term revenue vs. long-term enforcement risk). Whether to pursue a bank charter (years of regulatory effort and supervision vs. permanent unit economics advantage). Whether to shut down a product that has customer obligations (data retention, account migration, regulatory wind-down requirements). These decisions cannot be made on commercial grounds alone — they require regulatory judgment." + fintech_context: "Fintech founders face uniquely difficult decisions that carry + regulatory and legal consequences beyond commercial impact. Whether to + self-report a compliance failure to regulators (legally required in many + cases, strategically important in all). Whether to exit a banking partner + relationship when the partner faces regulatory issues (staying risks + contagion, leaving disrupts operations). Whether to restrict a profitable + product when internal compliance review identifies potential fair lending + issues (short-term revenue vs. long-term enforcement risk). Whether to + pursue a bank charter (years of regulatory effort and supervision vs. + permanent unit economics advantage). Whether to shut down a product that + has customer obligations (data retention, account migration, regulatory + wind-down requirements). These decisions cannot be made on commercial + grounds alone — they require regulatory judgment." fintech_anti_patterns: - - "Delaying self-reporting of compliance failures in hopes they will be resolved before discovery. Regulators penalize concealment far more severely than the underlying violation. The cover-up is always worse than the crime in regulatory enforcement." - - "Making tough decisions about regulated products without regulatory counsel present. Commercial instincts that serve well in unregulated businesses can lead to disastrous outcomes when applied to regulated financial products." - - "Treating ethical concerns about financial products (predatory lending terms, exploitative fee structures, algorithmic bias in credit scoring) as merely PR risks rather than regulatory and moral obligations. UDAP/UDAAP and fair lending laws exist because these are not just bad PR — they are illegal." - fintech_example: "A lending fintech's internal audit discovers that its AI credit model is inadvertently producing disparate impact in loan approvals across protected demographic groups. The tough decision: continue operating the model (which is profitable and passes traditional statistical tests) while investigating, or immediately suspend it (disrupting operations and loan volume) until the fair lending analysis is complete. The company chooses suspension, self-reports to the CFPB, and engages an independent fair lending auditor. The decision costs $2M in lost origination but avoids a potential $50M+ enforcement action — and demonstrates to regulators that the company takes fair lending seriously, building regulatory goodwill that proves valuable in future interactions." - benchmark_references: ["regulatory-compliance-cost", "default-rate", "loan-origination-volume"] + - "Delaying self-reporting of compliance failures in hopes they will be + resolved before discovery. Regulators penalize concealment far more + severely than the underlying violation. The cover-up is always worse + than the crime in regulatory enforcement." + - "Making tough decisions about regulated products without regulatory + counsel present. Commercial instincts that serve well in unregulated + businesses can lead to disastrous outcomes when applied to regulated + financial products." + - "Treating ethical concerns about financial products (predatory lending + terms, exploitative fee structures, algorithmic bias in credit scoring) + as merely PR risks rather than regulatory and moral obligations. + UDAP/UDAAP and fair lending laws exist because these are not just bad PR + — they are illegal." + fintech_example: "A lending fintech's internal audit discovers that its AI + credit model is inadvertently producing disparate impact in loan approvals + across protected demographic groups. The tough decision: continue + operating the model (which is profitable and passes traditional + statistical tests) while investigating, or immediately suspend it + (disrupting operations and loan volume) until the fair lending analysis is + complete. The company chooses suspension, self-reports to the CFPB, and + engages an independent fair lending auditor. The decision costs $2M in + lost origination but avoids a potential $50M+ enforcement action — and + demonstrates to regulators that the company takes fair lending seriously, + building regulatory goodwill that proves valuable in future interactions." + benchmark_references: [ "regulatory-compliance-cost", "default-rate", "loan-origination-volume" ] # ───────────────────────────────────────────── # AI & LEADERSHIP (3 skills) @@ -403,43 +1322,161 @@ skill_overlays: - skill: "ai-vision-and-strategy" category: "ai-leadership" fintech_relevance: "critical" - fintech_context: "AI in fintech operates under regulatory requirements that do not exist in other industries. Credit underwriting models using AI/ML must comply with fair lending laws (ECOA, FCRA) that require explainability — a model that cannot explain why it denied a loan application violates adverse action notice requirements. AI-driven fraud detection must balance effectiveness with false-positive rates that affect customer access to funds. AI-based customer communication must comply with financial services disclosure requirements. The SR 11-7 guidance on model risk management requires that all models used in financial decision-making (credit, pricing, risk) be validated, documented, and subject to independent review. EU AI Act classifies financial services AI as 'high-risk,' imposing additional requirements. AI strategy in fintech must be compliance-first: what is the regulatory framework for AI in our specific financial activity, and how does our AI approach satisfy it?" + fintech_context: "AI in fintech operates under regulatory requirements that do + not exist in other industries. Credit underwriting models using AI/ML must + comply with fair lending laws (ECOA, FCRA) that require explainability — a + model that cannot explain why it denied a loan application violates + adverse action notice requirements. AI-driven fraud detection must balance + effectiveness with false-positive rates that affect customer access to + funds. AI-based customer communication must comply with financial services + disclosure requirements. The SR 11-7 guidance on model risk management + requires that all models used in financial decision-making (credit, + pricing, risk) be validated, documented, and subject to independent + review. EU AI Act classifies financial services AI as 'high-risk,' + imposing additional requirements. AI strategy in fintech must be + compliance-first: what is the regulatory framework for AI in our specific + financial activity, and how does our AI approach satisfy it?" fintech_anti_patterns: - - "Deploying black-box ML models for credit decisions. Regulators require that credit decisions be explainable. A model that accurately predicts default but cannot explain its reasoning violates adverse action notice requirements under ECOA and FCRA." - - "Using AI to optimize revenue extraction without fair lending analysis. An AI that optimizes pricing may inadvertently create disparate impact across protected demographic groups — a violation regardless of intent." - - "Treating AI model validation as a one-time event. SR 11-7 requires ongoing monitoring, periodic revalidation, and challenger model comparison. A model validated at launch but never revalidated is a compliance risk." - fintech_example: "Upstart developed an AI credit underwriting model that expands beyond traditional FICO scores. Critically, the company obtained a CFPB no-action letter before scaling, demonstrated fair lending compliance through published disparate impact analysis, and maintained explainability features that generate specific adverse action reasons for every denied application. The AI strategy was regulatory-first: prove to regulators that the model expands credit access (reducing information asymmetry) rather than exploiting it, and do so transparently. This regulatory alignment enabled Upstart to scale to $12B+ in loan originations while facing less regulatory friction than competitors who deployed AI without regulatory engagement." - benchmark_references: ["default-rate", "loan-origination-volume", "regulatory-compliance-cost"] + - "Deploying black-box ML models for credit decisions. Regulators require + that credit decisions be explainable. A model that accurately predicts + default but cannot explain its reasoning violates adverse action notice + requirements under ECOA and FCRA." + - "Using AI to optimize revenue extraction without fair lending analysis. + An AI that optimizes pricing may inadvertently create disparate impact + across protected demographic groups — a violation regardless of intent." + - "Treating AI model validation as a one-time event. SR 11-7 requires + ongoing monitoring, periodic revalidation, and challenger model + comparison. A model validated at launch but never revalidated is a + compliance risk." + fintech_example: "Upstart developed an AI credit underwriting model that expands + beyond traditional FICO scores. Critically, the company obtained a CFPB + no-action letter before scaling, demonstrated fair lending compliance + through published disparate impact analysis, and maintained explainability + features that generate specific adverse action reasons for every denied + application. The AI strategy was regulatory-first: prove to regulators + that the model expands credit access (reducing information asymmetry) + rather than exploiting it, and do so transparently. This regulatory + alignment enabled Upstart to scale to $12B+ in loan originations while + facing less regulatory friction than competitors who deployed AI without + regulatory engagement." + benchmark_references: [ "default-rate", "loan-origination-volume", "regulatory-compliance-cost" ] - skill: "ai-human-centered-approach" category: "ai-leadership" fintech_relevance: "high" - fintech_context: "Human-centered AI in fintech is not just a design philosophy — it is a regulatory requirement. The CFPB has issued guidance that automated financial decision-making must include meaningful human oversight. Fair lending laws require that AI-driven credit decisions be reviewable by humans who can explain the reasoning. Customer-facing AI (chatbots, robo-advisors) must include escalation to human agents for complex financial questions. The human-centered approach in fintech means: humans design the models, humans validate the outputs, humans oversee the decisions, and humans are available when AI fails. This is not optional — it is a regulatory mandate under SR 11-7, ECOA, and emerging AI regulations." + fintech_context: "Human-centered AI in fintech is not just a design philosophy — + it is a regulatory requirement. The CFPB has issued guidance that + automated financial decision-making must include meaningful human + oversight. Fair lending laws require that AI-driven credit decisions be + reviewable by humans who can explain the reasoning. Customer-facing AI + (chatbots, robo-advisors) must include escalation to human agents for + complex financial questions. The human-centered approach in fintech means: + humans design the models, humans validate the outputs, humans oversee the + decisions, and humans are available when AI fails. This is not optional — + it is a regulatory mandate under SR 11-7, ECOA, and emerging AI + regulations." fintech_anti_patterns: - - "Removing human oversight from financial decision-making to reduce costs. Regulators expect human review of AI-driven credit decisions, fraud alerts, and compliance determinations. Full automation without human oversight is a regulatory violation." - - "Deploying customer-facing AI without human escalation paths. A chatbot that handles financial complaints without the ability to escalate to a human violates consumer protection expectations and potentially UDAP/UDAAP." - - "Treating AI explainability as a feature rather than a requirement. In financial services, explainability is not a nice-to-have — it is legally required for credit decisions, insurance underwriting, and investment recommendations." - fintech_example: "A robo-advisor implements AI-driven portfolio management but applies human-centered design principles required by SEC/FINRA guidance: algorithmic recommendations are explained in plain language, customers can override AI suggestions, a registered investment advisor reviews flagged recommendations before execution, and quarterly human-reviewed performance reports are generated. The human-centered approach costs 15% more than full automation but satisfies regulatory requirements, reduces liability exposure, and produces higher customer trust scores — trust that translates directly to higher AUM retention." - benchmark_references: ["aum", "monthly-active-users", "regulatory-compliance-cost"] + - "Removing human oversight from financial decision-making to reduce + costs. Regulators expect human review of AI-driven credit decisions, + fraud alerts, and compliance determinations. Full automation without + human oversight is a regulatory violation." + - "Deploying customer-facing AI without human escalation paths. A chatbot + that handles financial complaints without the ability to escalate to a + human violates consumer protection expectations and potentially + UDAP/UDAAP." + - "Treating AI explainability as a feature rather than a requirement. In + financial services, explainability is not a nice-to-have — it is legally + required for credit decisions, insurance underwriting, and investment + recommendations." + fintech_example: "A robo-advisor implements AI-driven portfolio management but + applies human-centered design principles required by SEC/FINRA guidance: + algorithmic recommendations are explained in plain language, customers can + override AI suggestions, a registered investment advisor reviews flagged + recommendations before execution, and quarterly human-reviewed performance + reports are generated. The human-centered approach costs 15% more than + full automation but satisfies regulatory requirements, reduces liability + exposure, and produces higher customer trust scores — trust that + translates directly to higher AUM retention." + benchmark_references: [ "aum", "monthly-active-users", "regulatory-compliance-cost" ] - skill: "strategic-thinking-and-alignment" category: "leadership" fintech_relevance: "high" - fintech_context: "Strategic alignment in fintech must incorporate the compliance function as a strategic partner, not a cost center. The most common misalignment in fintech organizations is between the growth team (which wants speed and scale) and the compliance team (which wants control and risk mitigation). This tension is productive when managed — compliance constraints force creative solutions and build sustainable competitive advantages. It is destructive when one side dominates — uncontrolled growth leads to enforcement actions; excessive compliance conservatism prevents market entry. Strategic alignment means ensuring that growth targets include compliance readiness, that product roadmaps include regulatory features, and that the compliance team understands commercial objectives well enough to find compliant paths to growth." + fintech_context: "Strategic alignment in fintech must incorporate the compliance + function as a strategic partner, not a cost center. The most common + misalignment in fintech organizations is between the growth team (which + wants speed and scale) and the compliance team (which wants control and + risk mitigation). This tension is productive when managed — compliance + constraints force creative solutions and build sustainable competitive + advantages. It is destructive when one side dominates — uncontrolled + growth leads to enforcement actions; excessive compliance conservatism + prevents market entry. Strategic alignment means ensuring that growth + targets include compliance readiness, that product roadmaps include + regulatory features, and that the compliance team understands commercial + objectives well enough to find compliant paths to growth." fintech_anti_patterns: - - "Treating compliance as a veto function rather than an enabling function. A compliance team that only says 'no' is not aligned with the business. Aligned compliance says 'not that way, but here is a compliant way to achieve the same goal.'" - - "Excluding the Chief Compliance Officer from strategic planning. The CCO should be present at strategy offsites, product planning sessions, and board meetings — not consulted after decisions are made." - - "Setting growth targets without modeling the compliance infrastructure required to support them. Doubling customer count requires proportional investment in transaction monitoring, KYC operations, and regulatory reporting capacity." - fintech_example: "A neobank's CEO institutes 'compliance-in-the-room' policy: the CCO or a compliance delegate attends every product planning meeting and every go-to-market strategy session. Initially resisted by the product team as slowing decisions, the policy produces unexpected benefits: compliance identifies regulatory risks early (preventing costly late-stage redesigns), suggests compliant alternatives to blocked product ideas, and provides regulatory intelligence that opens new market opportunities. Strategic alignment transforms compliance from a cost center into a strategic advantage — the company launches products faster than competitors because compliance is built in, not bolted on." - benchmark_references: ["regulatory-compliance-cost", "monthly-active-users"] + - "Treating compliance as a veto function rather than an enabling + function. A compliance team that only says 'no' is not aligned with the + business. Aligned compliance says 'not that way, but here is a compliant + way to achieve the same goal.'" + - "Excluding the Chief Compliance Officer from strategic planning. The CCO + should be present at strategy offsites, product planning sessions, and + board meetings — not consulted after decisions are made." + - "Setting growth targets without modeling the compliance infrastructure + required to support them. Doubling customer count requires proportional + investment in transaction monitoring, KYC operations, and regulatory + reporting capacity." + fintech_example: "A neobank's CEO institutes 'compliance-in-the-room' policy: + the CCO or a compliance delegate attends every product planning meeting + and every go-to-market strategy session. Initially resisted by the product + team as slowing decisions, the policy produces unexpected benefits: + compliance identifies regulatory risks early (preventing costly late-stage + redesigns), suggests compliant alternatives to blocked product ideas, and + provides regulatory intelligence that opens new market opportunities. + Strategic alignment transforms compliance from a cost center into a + strategic advantage — the company launches products faster than + competitors because compliance is built in, not bolted on." + benchmark_references: [ "regulatory-compliance-cost", "monthly-active-users" ] - skill: "kaizen-bpr" category: "frameworks" fintech_relevance: "high" - fintech_context: "Kaizen and Business Process Reengineering in fintech must focus on compliance processes as the primary efficiency opportunity. KYC onboarding, transaction monitoring, SAR filing, regulatory reporting, and audit preparation are process-heavy activities that consume 10-25% of fintech operating costs. Small, continuous improvements (Kaizen) apply to reducing false positive rates in fraud detection, shortening KYC verification time, and accelerating regulatory report generation. Business Process Reengineering applies to fundamental restructuring — replacing manual transaction monitoring with automated systems, transitioning from batch to real-time regulatory reporting, or consolidating multi-state compliance into a unified framework." + fintech_context: "Kaizen and Business Process Reengineering in fintech must + focus on compliance processes as the primary efficiency opportunity. KYC + onboarding, transaction monitoring, SAR filing, regulatory reporting, and + audit preparation are process-heavy activities that consume 10-25% of + fintech operating costs. Small, continuous improvements (Kaizen) apply to + reducing false positive rates in fraud detection, shortening KYC + verification time, and accelerating regulatory report generation. Business + Process Reengineering applies to fundamental restructuring — replacing + manual transaction monitoring with automated systems, transitioning from + batch to real-time regulatory reporting, or consolidating multi-state + compliance into a unified framework." fintech_anti_patterns: - - "Applying BPR to compliance processes without regulatory counsel. Redesigning the AML process to be 'more efficient' may inadvertently eliminate controls that regulators require. Process redesign in compliance must be validated against regulatory requirements." - - "Ignoring the compliance process improvement opportunity. Many fintechs invest heavily in product and engineering process improvement while running compliance on manual spreadsheets and email chains." - - "Treating compliance process improvements as one-time projects. Regulatory requirements change continuously — a process optimized for today's regulations may be non-compliant tomorrow. Kaizen (continuous improvement) is the correct approach." - fintech_example: "A payments fintech applies Kaizen to its SAR filing process and discovers that the average time from alert to filing is 22 days — against a regulatory expectation of 30 days but with no buffer for complex cases. Small improvements over six months: automated pre-population of SAR forms from transaction data (saves 2 days), standardized narrative templates for common typologies (saves 1 day), and a triage system that routes simple cases to junior analysts and complex cases to senior investigators (improves quality while reducing cycle time to 14 days). The Kaizen approach produces compliant, efficient processes without the risk of a full BPR that might inadvertently remove required controls." - benchmark_references: ["regulatory-compliance-cost", "kyc-cost-per-customer", "cost-to-income-ratio"] + - "Applying BPR to compliance processes without regulatory counsel. + Redesigning the AML process to be 'more efficient' may inadvertently + eliminate controls that regulators require. Process redesign in + compliance must be validated against regulatory requirements." + - "Ignoring the compliance process improvement opportunity. Many fintechs + invest heavily in product and engineering process improvement while + running compliance on manual spreadsheets and email chains." + - "Treating compliance process improvements as one-time projects. + Regulatory requirements change continuously — a process optimized for + today's regulations may be non-compliant tomorrow. Kaizen (continuous + improvement) is the correct approach." + fintech_example: "A payments fintech applies Kaizen to its SAR filing process + and discovers that the average time from alert to filing is 22 days — + against a regulatory expectation of 30 days but with no buffer for complex + cases. Small improvements over six months: automated pre-population of SAR + forms from transaction data (saves 2 days), standardized narrative + templates for common typologies (saves 1 day), and a triage system that + routes simple cases to junior analysts and complex cases to senior + investigators (improves quality while reducing cycle time to 14 days). The + Kaizen approach produces compliant, efficient processes without the risk + of a full BPR that might inadvertently remove required controls." + benchmark_references: + [ + "regulatory-compliance-cost", + "kyc-cost-per-customer", + "cost-to-income-ratio" + ] diff --git a/.claude/industry-packs/healthtech/healthtech-benchmarks.yaml b/.claude/industry-packs/healthtech/healthtech-benchmarks.yaml index 11ec4b6..b629368 100644 --- a/.claude/industry-packs/healthtech/healthtech-benchmarks.yaml +++ b/.claude/industry-packs/healthtech/healthtech-benchmarks.yaml @@ -34,7 +34,11 @@ pack_metadata: sector: "healthtech" display_name: "Healthtech" version: "1.0.0" - description: "Benchmark data for healthtech companies spanning digital health, telemedicine, health SaaS, clinical decision support, digital therapeutics, remote patient monitoring, health data analytics, genomics, mental health tech, and AI-powered diagnostics — with patient safety, clinical validation, and regulatory compliance as first-class dimensions." + description: "Benchmark data for healthtech companies spanning digital health, + telemedicine, health SaaS, clinical decision support, digital therapeutics, + remote patient monitoring, health data analytics, genomics, mental health + tech, and AI-powered diagnostics — with patient safety, clinical validation, + and regulatory compliance as first-class dimensions." applicable_stages: - idea - validation @@ -62,218 +66,377 @@ benchmarks: - name: "Clinical Validation Stage" id: "clinical-validation-stage" category: "product" - definition: "The highest level of clinical evidence the product has achieved, ranging from internal pilot data to peer-reviewed randomized controlled trial results and regulatory clearance. This metric defines the company's credibility with providers, payers, and regulators." - formula: "Categorical: Pilot (internal data) → Observational Study → RCT → Peer-Reviewed Publication → Regulatory Clearance/Approval" + definition: "The highest level of clinical evidence the product has achieved, + ranging from internal pilot data to peer-reviewed randomized controlled + trial results and regulatory clearance. This metric defines the company's + credibility with providers, payers, and regulators." + formula: "Categorical: Pilot (internal data) → Observational Study → RCT → + Peer-Reviewed Publication → Regulatory Clearance/Approval" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "Pilot data only, no external validation" - signal: "Insufficient evidence to convince health systems, payers, or regulators. The product is a hypothesis, not a validated intervention. Sales conversations stall at the clinical evidence question." + signal: "Insufficient evidence to convince health systems, payers, or + regulators. The product is a hypothesis, not a validated intervention. + Sales conversations stall at the clinical evidence question." below_average: value: "Single-arm observational study, < 100 patients" - signal: "Early signal but not sufficient for most health system procurement committees or payer coverage decisions. Useful for generating interest, not for closing contracts." + signal: "Early signal but not sufficient for most health system procurement + committees or payer coverage decisions. Useful for generating + interest, not for closing contracts." average: - value: "Multi-site observational study or single-site RCT, 100-500 patients, abstract presented at clinical conference" - signal: "Meaningful evidence that supports pilot agreements with health systems. Payers may consider coverage with conditions. Sufficient for seed/Series A fundraising from health-focused investors." + value: "Multi-site observational study or single-site RCT, 100-500 patients, + abstract presented at clinical conference" + signal: "Meaningful evidence that supports pilot agreements with health systems. + Payers may consider coverage with conditions. Sufficient for + seed/Series A fundraising from health-focused investors." good: - value: "Multi-site RCT, 500+ patients, peer-reviewed publication in indexed journal" - signal: "Strong evidence base that satisfies most health system clinical review committees. Payer coverage discussions become substantive. Regulatory submission supported by this level of evidence." + value: "Multi-site RCT, 500+ patients, peer-reviewed publication in indexed + journal" + signal: "Strong evidence base that satisfies most health system clinical review + committees. Payer coverage discussions become substantive. Regulatory + submission supported by this level of evidence." excellent: - value: "Multiple RCTs, published in high-impact journals (NEJM, JAMA, Lancet), regulatory clearance/approval obtained" - signal: "Gold-standard evidence. Health systems adopt based on evidence alone. Payers offer reimbursement. The company has a durable competitive moat built on clinical proof." + value: "Multiple RCTs, published in high-impact journals (NEJM, JAMA, Lancet), + regulatory clearance/approval obtained" + signal: "Gold-standard evidence. Health systems adopt based on evidence alone. + Payers offer reimbursement. The company has a durable competitive moat + built on clinical proof." stage_notes: - seed: "Pilot data is expected at seed. Investors assess the clinical study design and the team's ability to execute it, not the results themselves. A credible study protocol with IRB approval is a meaningful signal." - series_a: "At least one published or conference-presented study is expected. Series A health investors will evaluate whether the study design is rigorous enough to support future regulatory and reimbursement claims." - series_b_plus: "Peer-reviewed publications and regulatory milestones are expected. Without them, the product remains a science project. Clinical validation is the single strongest moat in healthtech." + seed: "Pilot data is expected at seed. Investors assess the clinical study + design and the team's ability to execute it, not the results themselves. + A credible study protocol with IRB approval is a meaningful signal." + series_a: "At least one published or conference-presented study is expected. + Series A health investors will evaluate whether the study design is + rigorous enough to support future regulatory and reimbursement claims." + series_b_plus: "Peer-reviewed publications and regulatory milestones are + expected. Without them, the product remains a science project. Clinical + validation is the single strongest moat in healthtech." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "FDA Digital Health Center of Excellence" year: "2024" - related_metrics: ["clinical-evidence-strength", "patient-outcomes-improvement", "regulatory-approval-status"] - related_skills: ["trust-equation", "balanced-scorecard"] - caveats: "Clinical validation stage is not binary — a strong observational study in the right patient population may outweigh a weak RCT. The relevance of each evidence level varies by therapeutic area, regulatory pathway, and payer requirements." + related_metrics: + [ + "clinical-evidence-strength", + "patient-outcomes-improvement", + "regulatory-approval-status" + ] + related_skills: [ "trust-equation", "balanced-scorecard" ] + caveats: "Clinical validation stage is not binary — a strong observational study + in the right patient population may outweigh a weak RCT. The relevance of + each evidence level varies by therapeutic area, regulatory pathway, and + payer requirements." - name: "Regulatory Approval Status" id: "regulatory-approval-status" category: "product" - definition: "The current status of the product on its regulatory pathway — pre-submission, submitted, cleared/approved, or exempt. For FDA-regulated products, this encompasses 510(k) clearance, De Novo classification, PMA approval, or Breakthrough Device designation. For non-FDA products, this covers state licensing, CLIA certification, or CE marking." - formula: "Categorical: Not Applicable (wellness) → Pre-Submission → Submitted → Cleared/Approved" + definition: "The current status of the product on its regulatory pathway — + pre-submission, submitted, cleared/approved, or exempt. For FDA-regulated + products, this encompasses 510(k) clearance, De Novo classification, PMA + approval, or Breakthrough Device designation. For non-FDA products, this + covers state licensing, CLIA certification, or CE marking." + formula: "Categorical: Not Applicable (wellness) → Pre-Submission → Submitted → + Cleared/Approved" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "Product requires regulatory clearance but no submission timeline exists" - signal: "Existential risk. The company is building a product it cannot legally sell. Every month of development without a regulatory strategy is potentially wasted." + signal: "Existential risk. The company is building a product it cannot legally + sell. Every month of development without a regulatory strategy is + potentially wasted." below_average: - value: "Pre-submission meeting requested or completed; submission 6-12 months away" - signal: "Regulatory strategy exists but execution has not begun. Investors will discount the company for regulatory risk. Health systems will not pilot without a clear pathway." + value: "Pre-submission meeting requested or completed; submission 6-12 months + away" + signal: "Regulatory strategy exists but execution has not begun. Investors will + discount the company for regulatory risk. Health systems will not + pilot without a clear pathway." average: - value: "Submission filed or Breakthrough Device designation obtained; clearance expected within 6 months" - signal: "Active regulatory engagement. Breakthrough Device designation provides FDA interaction advantages and accelerated review. Health systems may begin pilot agreements contingent on clearance." + value: "Submission filed or Breakthrough Device designation obtained; clearance + expected within 6 months" + signal: "Active regulatory engagement. Breakthrough Device designation provides + FDA interaction advantages and accelerated review. Health systems may + begin pilot agreements contingent on clearance." good: value: "510(k) cleared or De Novo classified; CE mark obtained for EU market" - signal: "Regulatory barrier crossed. The product can be legally marketed and sold. This is a major de-risking event that unlocks health system procurement and payer coverage conversations." + signal: "Regulatory barrier crossed. The product can be legally marketed and + sold. This is a major de-risking event that unlocks health system + procurement and payer coverage conversations." excellent: - value: "PMA approved or multiple regulatory clearances across geographies (FDA + CE + additional markets)" - signal: "Strongest regulatory position. PMA creates a higher barrier for competitors. Multi-geography clearance enables global commercialization." + value: "PMA approved or multiple regulatory clearances across geographies (FDA + + CE + additional markets)" + signal: "Strongest regulatory position. PMA creates a higher barrier for + competitors. Multi-geography clearance enables global + commercialization." stage_notes: - seed: "A clear regulatory pathway and classification strategy is expected at seed. Founders should have completed an FDA pre-submission meeting or equivalent. Investors assess regulatory literacy as a proxy for execution capability." - series_a: "Submission filed or clearance obtained is ideal at Series A. The 2024-2026 funding environment penalizes healthtech companies that have not de-risked regulatory pathway." - series_b_plus: "Clearance is a prerequisite for Series B in regulated healthtech. Companies raising at this stage without clearance face significant valuation compression." + seed: "A clear regulatory pathway and classification strategy is expected at + seed. Founders should have completed an FDA pre-submission meeting or + equivalent. Investors assess regulatory literacy as a proxy for + execution capability." + series_a: "Submission filed or clearance obtained is ideal at Series A. The + 2024-2026 funding environment penalizes healthtech companies that have + not de-risked regulatory pathway." + series_b_plus: "Clearance is a prerequisite for Series B in regulated + healthtech. Companies raising at this stage without clearance face + significant valuation compression." data_sources: - source: "FDA Digital Health Center of Excellence" year: "2024" - source: "IQVIA Digital Health Trends" year: "2024" - related_metrics: ["clinical-validation-stage", "time-to-regulatory-clearance", "regulatory-pathway-cost"] - related_skills: ["scenario-planning", "vuca-framework"] - caveats: "Not all healthtech products require FDA clearance. Wellness apps, provider workflow tools, and certain clinical decision support tools may be exempt under FDA guidance. Misclassifying a regulated product as exempt is a serious legal and business risk." + related_metrics: + [ + "clinical-validation-stage", + "time-to-regulatory-clearance", + "regulatory-pathway-cost" + ] + related_skills: [ "scenario-planning", "vuca-framework" ] + caveats: "Not all healthtech products require FDA clearance. Wellness apps, + provider workflow tools, and certain clinical decision support tools may + be exempt under FDA guidance. Misclassifying a regulated product as exempt + is a serious legal and business risk." - name: "Patient Outcomes Improvement (%)" id: "patient-outcomes-improvement" category: "product" - definition: "The measurable improvement in patient health outcomes attributable to the product, expressed as a percentage improvement over standard of care or control group. This is the ultimate measure of whether the product fulfills its clinical promise." - formula: "(Outcome_intervention - Outcome_control) / Outcome_control x 100, where outcome is the primary clinical endpoint" + definition: "The measurable improvement in patient health outcomes attributable + to the product, expressed as a percentage improvement over standard of + care or control group. This is the ultimate measure of whether the product + fulfills its clinical promise." + formula: "(Outcome_intervention - Outcome_control) / Outcome_control x 100, + where outcome is the primary clinical endpoint" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 5% improvement or not statistically significant" - signal: "The product does not demonstrably improve outcomes. Without measurable improvement, the value proposition rests on operational efficiency alone — a weaker position for reimbursement and adoption." + signal: "The product does not demonstrably improve outcomes. Without measurable + improvement, the value proposition rests on operational efficiency + alone — a weaker position for reimbursement and adoption." below_average: value: "5-10% improvement, p < 0.05 in pilot study" - signal: "Modest improvement that may not meet clinical significance thresholds. Sufficient for internal use cases but unlikely to secure dedicated reimbursement or change clinical guidelines." + signal: "Modest improvement that may not meet clinical significance thresholds. + Sufficient for internal use cases but unlikely to secure dedicated + reimbursement or change clinical guidelines." average: value: "10-20% improvement, p < 0.05 in adequately powered study" - signal: "Clinically meaningful improvement. Sufficient to support health economic arguments and to interest health system clinical review committees." + signal: "Clinically meaningful improvement. Sufficient to support health + economic arguments and to interest health system clinical review + committees." good: value: "20-35% improvement, replicated across multiple sites" - signal: "Strong clinical impact. Sufficient for guideline inclusion, payer coverage with dedicated reimbursement codes, and differentiated positioning against competitors." + signal: "Strong clinical impact. Sufficient for guideline inclusion, payer + coverage with dedicated reimbursement codes, and differentiated + positioning against competitors." excellent: - value: "> 35% improvement, published in high-impact journal with health economic analysis" - signal: "Transformative clinical impact. The product becomes a standard-of-care candidate. Payers actively seek to cover it because better outcomes reduce downstream costs." + value: "> 35% improvement, published in high-impact journal with health economic + analysis" + signal: "Transformative clinical impact. The product becomes a standard-of-care + candidate. Payers actively seek to cover it because better outcomes + reduce downstream costs." stage_notes: - seed: "Outcome data is aspirational at seed. The metric should be defined (what primary endpoint will be measured) even if results are not yet available." - series_a: "Preliminary outcome data from pilot studies should be available. Even directional improvement with a credible study design is valuable." - series_b_plus: "Robust outcome data is required. Health-focused investors at this stage perform clinical due diligence as rigorous as financial due diligence." + seed: "Outcome data is aspirational at seed. The metric should be defined (what + primary endpoint will be measured) even if results are not yet + available." + series_a: "Preliminary outcome data from pilot studies should be available. Even + directional improvement with a credible study design is valuable." + series_b_plus: "Robust outcome data is required. Health-focused investors at + this stage perform clinical due diligence as rigorous as financial due + diligence." data_sources: - source: "Journal of Medical Internet Research — Digital Health Outcomes" year: "2024" - source: "IQVIA Digital Health Trends" year: "2024" - related_metrics: ["clinical-validation-stage", "clinical-evidence-strength", "patient-satisfaction-score"] - related_skills: ["balanced-scorecard", "net-promoter-score"] - caveats: "Outcome improvement varies dramatically by condition, intervention type, and comparator. A 10% improvement in cancer survival is transformative; a 10% improvement in appointment scheduling convenience is trivial. Context is everything." + related_metrics: + [ + "clinical-validation-stage", + "clinical-evidence-strength", + "patient-satisfaction-score" + ] + related_skills: [ "balanced-scorecard", "net-promoter-score" ] + caveats: "Outcome improvement varies dramatically by condition, intervention + type, and comparator. A 10% improvement in cancer survival is + transformative; a 10% improvement in appointment scheduling convenience is + trivial. Context is everything." - name: "Clinical Evidence Strength (Levels 1-5)" id: "clinical-evidence-strength" category: "product" - definition: "A composite rating of the strength and quality of clinical evidence supporting the product, based on the Oxford Centre for Evidence-Based Medicine levels. Level 1: systematic reviews of RCTs. Level 2: individual RCTs. Level 3: controlled cohort studies. Level 4: case series or poor-quality cohort. Level 5: expert opinion or mechanism-based reasoning." - formula: "Oxford CEBM Level assignment based on highest-quality study supporting the product's primary clinical claim" + definition: "A composite rating of the strength and quality of clinical evidence + supporting the product, based on the Oxford Centre for Evidence-Based + Medicine levels. Level 1: systematic reviews of RCTs. Level 2: individual + RCTs. Level 3: controlled cohort studies. Level 4: case series or + poor-quality cohort. Level 5: expert opinion or mechanism-based + reasoning." + formula: "Oxford CEBM Level assignment based on highest-quality study supporting + the product's primary clinical claim" unit: "ratio" direction: "lower-is-better" benchmarks: poor: value: "Level 5 — Expert opinion or mechanism-based reasoning only" - signal: "No clinical data. The product's claims rest on theoretical arguments. Providers and payers will not adopt based on theory alone." + signal: "No clinical data. The product's claims rest on theoretical arguments. + Providers and payers will not adopt based on theory alone." below_average: value: "Level 4 — Case series or poor-quality cohort study" - signal: "Anecdotal evidence that may support early-stage fundraising but cannot support reimbursement or guideline inclusion." + signal: "Anecdotal evidence that may support early-stage fundraising but cannot + support reimbursement or guideline inclusion." average: value: "Level 3 — Non-randomized controlled cohort study" - signal: "Meaningful evidence that supports pilot deployment and early payer conversations. Most digital health companies at Series A operate at this level." + signal: "Meaningful evidence that supports pilot deployment and early payer + conversations. Most digital health companies at Series A operate at + this level." good: value: "Level 2 — Well-designed RCT" - signal: "Strong evidence. Supports regulatory submission, payer coverage decisions, and health system adoption. A competitive advantage over companies with lower evidence levels." + signal: "Strong evidence. Supports regulatory submission, payer coverage + decisions, and health system adoption. A competitive advantage over + companies with lower evidence levels." excellent: value: "Level 1 — Systematic review of RCTs or multiple high-quality RCTs" - signal: "Highest evidence quality. The product is supported by the same evidence standard as pharmaceutical interventions. This is rare in digital health and represents a formidable competitive moat." + signal: "Highest evidence quality. The product is supported by the same evidence + standard as pharmaceutical interventions. This is rare in digital + health and represents a formidable competitive moat." stage_notes: - seed: "Level 4-5 is acceptable at seed. The study design and protocol for achieving Level 2-3 evidence should be articulated." - series_a: "Level 3 evidence is expected. Companies with Level 2 evidence at Series A command premium valuations." - series_b_plus: "Level 2 evidence is the target. Companies at Level 3 or below face questions about whether the product will ever achieve the evidence threshold needed for scale." + seed: "Level 4-5 is acceptable at seed. The study design and protocol for + achieving Level 2-3 evidence should be articulated." + series_a: "Level 3 evidence is expected. Companies with Level 2 evidence at + Series A command premium valuations." + series_b_plus: "Level 2 evidence is the target. Companies at Level 3 or below + face questions about whether the product will ever achieve the evidence + threshold needed for scale." data_sources: - source: "Oxford Centre for Evidence-Based Medicine" year: "2024" - source: "IQVIA Digital Health Trends" year: "2024" - related_metrics: ["clinical-validation-stage", "patient-outcomes-improvement"] - related_skills: ["trust-equation", "systems-thinking"] - caveats: "Evidence level alone does not determine clinical utility. A well-designed Level 3 study in the right population may be more persuasive than a poorly executed Level 2 study. Quality within each level matters as much as the level itself." + related_metrics: [ "clinical-validation-stage", "patient-outcomes-improvement" ] + related_skills: [ "trust-equation", "systems-thinking" ] + caveats: "Evidence level alone does not determine clinical utility. A + well-designed Level 3 study in the right population may be more persuasive + than a poorly executed Level 2 study. Quality within each level matters as + much as the level itself." - name: "Time to Regulatory Clearance" id: "time-to-regulatory-clearance" category: "product" - definition: "The elapsed time from the decision to pursue regulatory clearance to the date of clearance/approval, including pre-submission meetings, study execution, submission preparation, and FDA review." + definition: "The elapsed time from the decision to pursue regulatory clearance + to the date of clearance/approval, including pre-submission meetings, + study execution, submission preparation, and FDA review." formula: "Date of clearance — Date of regulatory strategy initiation" unit: "months" direction: "lower-is-better" benchmarks: poor: value: "> 36 months" - signal: "Regulatory process has stalled or the company underestimated complexity. Runway consumption during extended regulatory timelines is the leading cause of healthtech company failure." + signal: "Regulatory process has stalled or the company underestimated + complexity. Runway consumption during extended regulatory timelines is + the leading cause of healthtech company failure." below_average: value: "24-36 months" - signal: "Within range for complex submissions (De Novo, PMA) but long for 510(k). May indicate regulatory strategy missteps or insufficient pre-submission engagement." + signal: "Within range for complex submissions (De Novo, PMA) but long for + 510(k). May indicate regulatory strategy missteps or insufficient + pre-submission engagement." average: value: "12-24 months" - signal: "Typical for a well-managed 510(k) process including clinical study execution. De Novo classifications also fall in this range with Breakthrough Device designation." + signal: "Typical for a well-managed 510(k) process including clinical study + execution. De Novo classifications also fall in this range with + Breakthrough Device designation." good: value: "6-12 months" - signal: "Efficient regulatory process. Common for 510(k) submissions with strong predicate device arguments and existing clinical data. Indicates regulatory sophistication." + signal: "Efficient regulatory process. Common for 510(k) submissions with strong + predicate device arguments and existing clinical data. Indicates + regulatory sophistication." excellent: value: "< 6 months" - signal: "Exceptional speed, typically achieved through Breakthrough Device program pre-review alignment, strong predicate arguments, or prior regulatory experience. Rare for first-time submissions." + signal: "Exceptional speed, typically achieved through Breakthrough Device + program pre-review alignment, strong predicate arguments, or prior + regulatory experience. Rare for first-time submissions." stage_notes: - seed: "Time to clearance is estimated at seed. Investors assess the realism of the timeline based on pathway complexity and team regulatory experience." - series_a: "Active regulatory engagement should be underway. The timeline should be supported by pre-submission meeting feedback and a concrete study protocol." - series_b_plus: "Clearance should be obtained or imminent. Companies raising Series B with 18+ months of remaining regulatory timeline face severe valuation compression." + seed: "Time to clearance is estimated at seed. Investors assess the realism of + the timeline based on pathway complexity and team regulatory + experience." + series_a: "Active regulatory engagement should be underway. The timeline should + be supported by pre-submission meeting feedback and a concrete study + protocol." + series_b_plus: "Clearance should be obtained or imminent. Companies raising + Series B with 18+ months of remaining regulatory timeline face severe + valuation compression." data_sources: - source: "FDA Digital Health Center of Excellence" year: "2024" - source: "Deloitte Life Sciences Outlook" year: "2025" - related_metrics: ["regulatory-approval-status", "regulatory-pathway-cost"] - related_skills: ["scenario-planning", "smart-goals"] - caveats: "Timelines vary dramatically by pathway. A 510(k) with a strong predicate can clear in 3-6 months of FDA review. A PMA requiring clinical trials may take 3-5 years. De Novo falls between. Always specify the pathway when citing this metric." + related_metrics: [ "regulatory-approval-status", "regulatory-pathway-cost" ] + related_skills: [ "scenario-planning", "smart-goals" ] + caveats: "Timelines vary dramatically by pathway. A 510(k) with a strong + predicate can clear in 3-6 months of FDA review. A PMA requiring clinical + trials may take 3-5 years. De Novo falls between. Always specify the + pathway when citing this metric." - name: "Regulatory Pathway Cost" id: "regulatory-pathway-cost" category: "financial" - definition: "The total cost incurred to achieve regulatory clearance or approval, including regulatory consulting, clinical study costs, submission fees, legal expenses, and internal staff time allocated to regulatory affairs." - formula: "SUM(regulatory consulting fees + clinical study costs + FDA user fees + legal costs + internal regulatory staff allocation)" + definition: "The total cost incurred to achieve regulatory clearance or + approval, including regulatory consulting, clinical study costs, + submission fees, legal expenses, and internal staff time allocated to + regulatory affairs." + formula: "SUM(regulatory consulting fees + clinical study costs + FDA user fees + + legal costs + internal regulatory staff allocation)" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $5M for 510(k); > $20M for De Novo/PMA" - signal: "Regulatory costs consuming a disproportionate share of capital. May indicate scope creep in clinical studies, regulatory strategy pivots, or insufficient internal regulatory expertise leading to over-reliance on consultants." + signal: "Regulatory costs consuming a disproportionate share of capital. May + indicate scope creep in clinical studies, regulatory strategy pivots, + or insufficient internal regulatory expertise leading to over-reliance + on consultants." below_average: value: "$2M-$5M for 510(k); $10M-$20M for De Novo/PMA" - signal: "High end of normal. Acceptable if the regulatory pathway is complex or involves a novel technology, but warrants cost optimization review." + signal: "High end of normal. Acceptable if the regulatory pathway is complex or + involves a novel technology, but warrants cost optimization review." average: value: "$500K-$2M for 510(k); $3M-$10M for De Novo/PMA" - signal: "Typical range for well-managed regulatory processes. Clinical study costs are usually the largest component." + signal: "Typical range for well-managed regulatory processes. Clinical study + costs are usually the largest component." good: value: "$200K-$500K for 510(k); $1M-$3M for De Novo" - signal: "Capital-efficient regulatory process. Indicates strong predicate strategy, efficient study design, or leveraged real-world evidence." + signal: "Capital-efficient regulatory process. Indicates strong predicate + strategy, efficient study design, or leveraged real-world evidence." excellent: value: "< $200K for 510(k); < $1M for De Novo" - signal: "Exceptional efficiency. Often achieved by companies with experienced regulatory leadership, strong predicate arguments, or innovative use of real-world data in lieu of prospective studies." + signal: "Exceptional efficiency. Often achieved by companies with experienced + regulatory leadership, strong predicate arguments, or innovative use + of real-world data in lieu of prospective studies." stage_notes: - seed: "Regulatory cost estimates should be included in financial projections. Under-budgeting regulatory costs is the most common financial planning error in healthtech." - series_a: "Actual regulatory spend should be tracked against projections. Investors evaluate cost discipline alongside regulatory progress." - series_b_plus: "Regulatory costs should be substantially amortized by this stage. Ongoing regulatory costs (post-market surveillance, periodic reporting) are typically modest." + seed: "Regulatory cost estimates should be included in financial projections. + Under-budgeting regulatory costs is the most common financial planning + error in healthtech." + series_a: "Actual regulatory spend should be tracked against projections. + Investors evaluate cost discipline alongside regulatory progress." + series_b_plus: "Regulatory costs should be substantially amortized by this + stage. Ongoing regulatory costs (post-market surveillance, periodic + reporting) are typically modest." data_sources: - source: "Deloitte Life Sciences Outlook" year: "2025" - source: "Rock Health Digital Health Funding Report" year: "2024" - related_metrics: ["time-to-regulatory-clearance", "regulatory-approval-status", "r-and-d-pct-of-revenue"] - related_skills: ["scenario-planning", "business-model-canvas"] - caveats: "Regulatory pathway cost varies by 10-50x depending on the pathway, therapeutic area, and whether prospective clinical studies are required. Comparing 510(k) costs to PMA costs is meaningless without pathway context." + related_metrics: + [ + "time-to-regulatory-clearance", + "regulatory-approval-status", + "r-and-d-pct-of-revenue" + ] + related_skills: [ "scenario-planning", "business-model-canvas" ] + caveats: "Regulatory pathway cost varies by 10-50x depending on the pathway, + therapeutic area, and whether prospective clinical studies are required. + Comparing 510(k) costs to PMA costs is meaningless without pathway + context." # ───────────────────────────────────────────── # ADOPTION & ENGAGEMENT METRICS @@ -282,146 +445,252 @@ benchmarks: - name: "Provider Adoption Rate" id: "provider-adoption-rate" category: "product" - definition: "The percentage of targeted providers (physicians, nurses, therapists) who actively use the product in their clinical workflow after it has been made available to them. Active use means the provider has used the product for clinical purposes at least once in the trailing 30 days." - formula: "Active providers (used in last 30 days) / Total providers with access x 100" + definition: "The percentage of targeted providers (physicians, nurses, + therapists) who actively use the product in their clinical workflow after + it has been made available to them. Active use means the provider has used + the product for clinical purposes at least once in the trailing 30 days." + formula: "Active providers (used in last 30 days) / Total providers with access + x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 20%" - signal: "Critical adoption failure. The majority of providers with access are not using the product. This typically signals workflow disruption, insufficient training, or a product that adds burden without commensurate clinical value." + signal: "Critical adoption failure. The majority of providers with access are + not using the product. This typically signals workflow disruption, + insufficient training, or a product that adds burden without + commensurate clinical value." below_average: value: "20-40%" - signal: "Partial adoption. Some providers find value but the product has not crossed the threshold where it becomes embedded in standard workflow. Risk of contract non-renewal at health system level." + signal: "Partial adoption. Some providers find value but the product has not + crossed the threshold where it becomes embedded in standard workflow. + Risk of contract non-renewal at health system level." average: value: "40-60%" - signal: "Moderate adoption. Sufficient for contract renewal but unlikely to drive organic expansion. Provider feedback likely reveals workflow integration gaps." + signal: "Moderate adoption. Sufficient for contract renewal but unlikely to + drive organic expansion. Provider feedback likely reveals workflow + integration gaps." good: value: "60-80%" - signal: "Strong adoption. The product has become part of standard workflow for the majority of targeted providers. This level supports health system expansion and peer referral." + signal: "Strong adoption. The product has become part of standard workflow for + the majority of targeted providers. This level supports health system + expansion and peer referral." excellent: value: "> 80%" - signal: "Exceptional adoption. The product is embedded in clinical workflow. Providers resist its removal. This creates a powerful retention moat and supports organic expansion." + signal: "Exceptional adoption. The product is embedded in clinical workflow. + Providers resist its removal. This creates a powerful retention moat + and supports organic expansion." stage_notes: - seed: "Adoption rate is measured in pilot settings. Even 5-10 engaged providers who provide deep feedback are more valuable than 50 providers with superficial adoption." - series_a: "Pilot adoption rates above 60% are a strong signal. Demonstrating that providers voluntarily continue using the product after the pilot period is critical." - series_b_plus: "System-wide adoption rates should be tracked across all deployed health system customers. Variation between customers reveals implementation quality differences." + seed: "Adoption rate is measured in pilot settings. Even 5-10 engaged providers + who provide deep feedback are more valuable than 50 providers with + superficial adoption." + series_a: "Pilot adoption rates above 60% are a strong signal. Demonstrating + that providers voluntarily continue using the product after the pilot + period is critical." + series_b_plus: "System-wide adoption rates should be tracked across all deployed + health system customers. Variation between customers reveals + implementation quality differences." data_sources: - source: "AMA Digital Health Research" year: "2024" - source: "KLAS Research — Provider Adoption Studies" year: "2024" - related_metrics: ["clinical-workflow-integration-score", "provider-nps", "time-to-value-implementation"] - related_skills: ["kotter-change-model", "net-promoter-score"] - caveats: "Provider adoption in healthtech is fundamentally different from user adoption in consumer software. Providers are time-constrained, change-resistant, and motivated by patient outcomes — not features. A product that saves 2 minutes per patient encounter will be adopted; one that adds 30 seconds will be rejected regardless of its other benefits." + related_metrics: + [ + "clinical-workflow-integration-score", + "provider-nps", + "time-to-value-implementation" + ] + related_skills: [ "kotter-change-model", "net-promoter-score" ] + caveats: "Provider adoption in healthtech is fundamentally different from user + adoption in consumer software. Providers are time-constrained, + change-resistant, and motivated by patient outcomes — not features. A + product that saves 2 minutes per patient encounter will be adopted; one + that adds 30 seconds will be rejected regardless of its other benefits." - name: "Patient Engagement Rate" id: "patient-engagement-rate" category: "product" - definition: "The percentage of enrolled patients who actively engage with the product within a defined period. For patient-facing products (apps, DTx, remote monitoring), this measures whether patients use the product as intended by the clinical protocol." - formula: "Active patients (completed ≥ 1 engagement action in trailing 7 days) / Enrolled patients x 100" + definition: "The percentage of enrolled patients who actively engage with the + product within a defined period. For patient-facing products (apps, DTx, + remote monitoring), this measures whether patients use the product as + intended by the clinical protocol." + formula: "Active patients (completed ≥ 1 engagement action in trailing 7 days) / + Enrolled patients x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 20% weekly engagement" - signal: "Patients are not using the product. For DTx and remote monitoring, this means the clinical intervention is not being delivered. Low engagement invalidates clinical outcomes data and undermines the value proposition to providers and payers." + signal: "Patients are not using the product. For DTx and remote monitoring, this + means the clinical intervention is not being delivered. Low engagement + invalidates clinical outcomes data and undermines the value + proposition to providers and payers." below_average: value: "20-35% weekly engagement" - signal: "Partial engagement. Some patients are using the product but the majority are not. Engagement decay from enrollment is likely steep." + signal: "Partial engagement. Some patients are using the product but the + majority are not. Engagement decay from enrollment is likely steep." average: value: "35-50% weekly engagement" - signal: "Moderate engagement. Sufficient for clinical effect in some therapeutic areas but below the threshold that DTx companies must demonstrate for reimbursement." + signal: "Moderate engagement. Sufficient for clinical effect in some therapeutic + areas but below the threshold that DTx companies must demonstrate for + reimbursement." good: value: "50-70% weekly engagement" - signal: "Strong engagement. Sufficient for most clinical protocols and reimbursement requirements. Demonstrates that the product maintains patient attention in a competitive attention environment." + signal: "Strong engagement. Sufficient for most clinical protocols and + reimbursement requirements. Demonstrates that the product maintains + patient attention in a competitive attention environment." excellent: value: "> 70% weekly engagement" - signal: "Exceptional for digital health. Rare outside acute-phase interventions and products with strong provider reinforcement loops. This level supports premium reimbursement and clinical outcome claims." + signal: "Exceptional for digital health. Rare outside acute-phase interventions + and products with strong provider reinforcement loops. This level + supports premium reimbursement and clinical outcome claims." stage_notes: - seed: "Engagement is measured in small cohorts. Qualitative understanding of why patients engage or disengage is more valuable than the rate itself." - series_a: "Engagement data from pilot studies should show the shape of the engagement curve — does it flatten (sustainable) or continue declining (unsustainable)?" - series_b_plus: "Engagement at scale is the key question. Products that maintain engagement beyond 90 days demonstrate durability that payers and providers require." + seed: "Engagement is measured in small cohorts. Qualitative understanding of why + patients engage or disengage is more valuable than the rate itself." + series_a: "Engagement data from pilot studies should show the shape of the + engagement curve — does it flatten (sustainable) or continue declining + (unsustainable)?" + series_b_plus: "Engagement at scale is the key question. Products that maintain + engagement beyond 90 days demonstrate durability that payers and + providers require." data_sources: - source: "IQVIA Digital Health Trends" year: "2024" - source: "Rock Health Digital Health Funding Report" year: "2024" - related_metrics: ["monthly-active-patients", "patient-satisfaction-score", "patient-outcomes-improvement"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "Engagement must be measured against the clinical protocol's dosage requirement, not arbitrary usage metrics. A DTx requiring daily use has different engagement thresholds than a remote monitoring system requiring weekly check-ins. Over-engagement (patient anxiety from constant monitoring) is also a risk." + related_metrics: + [ + "monthly-active-patients", + "patient-satisfaction-score", + "patient-outcomes-improvement" + ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Engagement must be measured against the clinical protocol's dosage + requirement, not arbitrary usage metrics. A DTx requiring daily use has + different engagement thresholds than a remote monitoring system requiring + weekly check-ins. Over-engagement (patient anxiety from constant + monitoring) is also a risk." - name: "Monthly Active Patients" id: "monthly-active-patients" category: "growth" - definition: "The total number of unique patients who completed at least one clinically meaningful action on the platform in the trailing 30 days. For provider-facing products, this is the number of patients whose care was supported by the product." + definition: "The total number of unique patients who completed at least one + clinically meaningful action on the platform in the trailing 30 days. For + provider-facing products, this is the number of patients whose care was + supported by the product." formula: "COUNT(DISTINCT patients with ≥ 1 clinical action in trailing 30 days)" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 1,000 MAP at 12 months post-launch" - signal: "Insufficient scale to generate meaningful clinical data, attract payer interest, or sustain the business. Distribution channels are not working." + signal: "Insufficient scale to generate meaningful clinical data, attract payer + interest, or sustain the business. Distribution channels are not + working." below_average: value: "1,000-5,000 MAP at 12 months" - signal: "Early traction but limited to pilot deployments. Insufficient scale for robust outcomes analysis." + signal: "Early traction but limited to pilot deployments. Insufficient scale for + robust outcomes analysis." average: value: "5,000-25,000 MAP at 12 months" - signal: "Meaningful scale. Sufficient patient volume for credible outcomes analysis and to demonstrate health system adoption. Attractive for Series A health-focused investors." + signal: "Meaningful scale. Sufficient patient volume for credible outcomes + analysis and to demonstrate health system adoption. Attractive for + Series A health-focused investors." good: value: "25,000-100,000 MAP at 12 months" - signal: "Strong scale across multiple health system customers. Clinical data at this volume supports peer-reviewed publication and payer coverage submissions." + signal: "Strong scale across multiple health system customers. Clinical data at + this volume supports peer-reviewed publication and payer coverage + submissions." excellent: value: "> 100,000 MAP at 12 months" - signal: "Exceptional scale. Sufficient for population health analyses, real-world evidence generation, and health plan partnerships. Data at this scale becomes a strategic asset." + signal: "Exceptional scale. Sufficient for population health analyses, + real-world evidence generation, and health plan partnerships. Data at + this scale becomes a strategic asset." stage_notes: - seed: "MAP is measured in hundreds during pilots. The metric matters less than the depth of engagement and quality of outcomes data generated." - series_a: "5,000-25,000 MAP across multiple sites demonstrates repeatable deployment. Growth rate matters more than absolute level." - series_b_plus: "MAP growth should compound as health system deployments expand. The ratio of MAP to contracted lives indicates penetration within deployed customers." + seed: "MAP is measured in hundreds during pilots. The metric matters less than + the depth of engagement and quality of outcomes data generated." + series_a: "5,000-25,000 MAP across multiple sites demonstrates repeatable + deployment. Growth rate matters more than absolute level." + series_b_plus: "MAP growth should compound as health system deployments expand. + The ratio of MAP to contracted lives indicates penetration within + deployed customers." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "CB Insights State of Digital Health" year: "2024" - related_metrics: ["patient-engagement-rate", "revenue-per-patient-per-month"] - related_skills: ["balanced-scorecard", "growth-share-matrix"] - caveats: "MAP is not equivalent to MAU in consumer apps. In healthtech, each 'active patient' represents a clinical relationship with associated safety obligations. Rapid MAP growth without proportional clinical support infrastructure is a patient safety risk." + related_metrics: [ "patient-engagement-rate", "revenue-per-patient-per-month" ] + related_skills: [ "balanced-scorecard", "growth-share-matrix" ] + caveats: "MAP is not equivalent to MAU in consumer apps. In healthtech, each + 'active patient' represents a clinical relationship with associated safety + obligations. Rapid MAP growth without proportional clinical support + infrastructure is a patient safety risk." - name: "Clinical Workflow Integration Score" id: "clinical-workflow-integration-score" category: "product" - definition: "A composite metric measuring the depth of integration between the product and existing clinical workflows — EHR integration level, single sign-on availability, data interchange standards support (HL7 FHIR, SMART on FHIR), and the number of additional clicks or steps required in the provider's workflow." - formula: "Weighted composite: EHR integration (40%) + standards compliance (25%) + additional workflow steps (20%) + data bidirectionality (15%)" + definition: "A composite metric measuring the depth of integration between the + product and existing clinical workflows — EHR integration level, single + sign-on availability, data interchange standards support (HL7 FHIR, SMART + on FHIR), and the number of additional clicks or steps required in the + provider's workflow." + formula: "Weighted composite: EHR integration (40%) + standards compliance (25%) + + additional workflow steps (20%) + data bidirectionality (15%)" unit: "ratio" direction: "higher-is-better" benchmarks: poor: - value: "Score < 30 — Standalone product with no EHR integration, requires separate login and manual data entry" - signal: "Dead on arrival in most health system sales processes. Providers will not adopt a product that requires them to leave their EHR workflow. Manual data entry creates clinical risk through transcription errors." + value: "Score < 30 — Standalone product with no EHR integration, requires + separate login and manual data entry" + signal: "Dead on arrival in most health system sales processes. Providers will + not adopt a product that requires them to leave their EHR workflow. + Manual data entry creates clinical risk through transcription errors." below_average: - value: "Score 30-50 — Basic EHR integration (read-only), single sign-on, limited data standards support" - signal: "Minimum viable integration. Providers can access the product from the EHR but must re-enter clinical data. Acceptable for pilot phase but insufficient for scaled deployment." + value: "Score 30-50 — Basic EHR integration (read-only), single sign-on, limited + data standards support" + signal: "Minimum viable integration. Providers can access the product from the + EHR but must re-enter clinical data. Acceptable for pilot phase but + insufficient for scaled deployment." average: - value: "Score 50-70 — Bidirectional EHR integration via HL7 FHIR, data flows both directions, integrated alerting" - signal: "Solid integration level. The product participates in the clinical workflow without creating significant additional burden. Most health system IT teams will approve deployment." + value: "Score 50-70 — Bidirectional EHR integration via HL7 FHIR, data flows + both directions, integrated alerting" + signal: "Solid integration level. The product participates in the clinical + workflow without creating significant additional burden. Most health + system IT teams will approve deployment." good: - value: "Score 70-85 — Deep EHR embedding via SMART on FHIR, appears as a native EHR module, zero additional clicks for core workflow" - signal: "Strong integration. The product is nearly invisible in the workflow — it adds value without adding steps. This is the threshold for enterprise-wide deployment approval." + value: "Score 70-85 — Deep EHR embedding via SMART on FHIR, appears as a native + EHR module, zero additional clicks for core workflow" + signal: "Strong integration. The product is nearly invisible in the workflow — + it adds value without adding steps. This is the threshold for + enterprise-wide deployment approval." excellent: - value: "Score > 85 — Fully embedded, ambient operation (requires no provider action for core function), works across multiple EHR vendors" - signal: "Exceptional integration. The product operates within the EHR environment as if native, across Epic, Cerner/Oracle Health, and other systems. Multi-vendor support is a significant competitive advantage." + value: "Score > 85 — Fully embedded, ambient operation (requires no provider + action for core function), works across multiple EHR vendors" + signal: "Exceptional integration. The product operates within the EHR + environment as if native, across Epic, Cerner/Oracle Health, and other + systems. Multi-vendor support is a significant competitive advantage." stage_notes: - seed: "Integration strategy should be defined at seed. The target EHR platform and integration approach must be identified. SMART on FHIR capabilities are increasingly expected by health systems." - series_a: "Working integration with at least one major EHR (Epic or Cerner/Oracle Health) should be demonstrated. Health system customers will verify integration depth during evaluation." - series_b_plus: "Multi-EHR support and deep integration are expected. Health system CIOs increasingly require SMART on FHIR compliance and participation in EHR app marketplaces (Epic App Orchard, Cerner Code)." + seed: "Integration strategy should be defined at seed. The target EHR platform + and integration approach must be identified. SMART on FHIR capabilities + are increasingly expected by health systems." + series_a: "Working integration with at least one major EHR (Epic or + Cerner/Oracle Health) should be demonstrated. Health system customers + will verify integration depth during evaluation." + series_b_plus: "Multi-EHR support and deep integration are expected. Health + system CIOs increasingly require SMART on FHIR compliance and + participation in EHR app marketplaces (Epic App Orchard, Cerner Code)." data_sources: - source: "KLAS Research — Provider Adoption Studies" year: "2024" - source: "CHIME CIO Surveys" year: "2024" - related_metrics: ["provider-adoption-rate", "time-to-value-implementation"] - related_skills: ["systems-thinking", "doblin-ten-types"] - caveats: "Integration depth must be balanced against vendor dependency. Building exclusively on Epic's proprietary APIs creates lock-in. FHIR-first architecture with EHR-specific adapters provides the best balance of integration depth and vendor flexibility." + related_metrics: [ "provider-adoption-rate", "time-to-value-implementation" ] + related_skills: [ "systems-thinking", "doblin-ten-types" ] + caveats: "Integration depth must be balanced against vendor dependency. Building + exclusively on Epic's proprietary APIs creates lock-in. FHIR-first + architecture with EHR-specific adapters provides the best balance of + integration depth and vendor flexibility." # ───────────────────────────────────────────── # REIMBURSEMENT & REVENUE METRICS @@ -430,182 +699,311 @@ benchmarks: - name: "Payer Reimbursement Rate" id: "payer-reimbursement-rate" category: "financial" - definition: "The percentage of product usage that is covered by health insurance payers (commercial, Medicare, Medicaid), as opposed to self-pay or employer direct-contract arrangements. For healthtech, payer reimbursement is the gatekeeper to scalable revenue." - formula: "Revenue from payer-reimbursed encounters / Total revenue from clinical encounters x 100" + definition: "The percentage of product usage that is covered by health insurance + payers (commercial, Medicare, Medicaid), as opposed to self-pay or + employer direct-contract arrangements. For healthtech, payer reimbursement + is the gatekeeper to scalable revenue." + formula: "Revenue from payer-reimbursed encounters / Total revenue from clinical + encounters x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 10% payer-covered" - signal: "The product operates almost entirely outside the reimbursement system. Revenue depends on out-of-pocket patient spend or direct employer contracts — both limited and fragile channels." + signal: "The product operates almost entirely outside the reimbursement system. + Revenue depends on out-of-pocket patient spend or direct employer + contracts — both limited and fragile channels." below_average: value: "10-30% payer-covered" - signal: "Some payer coverage secured but not the norm. Revenue model likely depends on a mix of reimbursement and alternative payment mechanisms. Scalability constrained." + signal: "Some payer coverage secured but not the norm. Revenue model likely + depends on a mix of reimbursement and alternative payment mechanisms. + Scalability constrained." average: value: "30-60% payer-covered" - signal: "Material payer coverage. Reimbursement pathway exists and is growing. The company can demonstrate to health systems that the product generates reimbursable revenue." + signal: "Material payer coverage. Reimbursement pathway exists and is growing. + The company can demonstrate to health systems that the product + generates reimbursable revenue." good: value: "60-80% payer-covered" - signal: "Strong reimbursement position. Majority of usage is payer-covered, reducing patient and health system financial burden. Scalable revenue model validated." + signal: "Strong reimbursement position. Majority of usage is payer-covered, + reducing patient and health system financial burden. Scalable revenue + model validated." excellent: value: "> 80% payer-covered with dedicated CPT or HCPCS codes" - signal: "Best-in-class reimbursement. Dedicated billing codes provide pricing transparency and predictability. The product is integrated into the healthcare payment infrastructure." + signal: "Best-in-class reimbursement. Dedicated billing codes provide pricing + transparency and predictability. The product is integrated into the + healthcare payment infrastructure." stage_notes: - seed: "Reimbursement strategy should be defined, including target CPT codes and payer engagement plan. Reimbursement-naivety at seed is the most common indicator of healthtech failure at later stages." - series_a: "Some form of reimbursement should be demonstrated — even if through existing codes or pilot payer agreements. A clear pathway to broader coverage must be articulated." - series_b_plus: "Broad payer coverage is expected for revenue-stage companies. The transition from pilot payer agreements to at-scale reimbursement is a critical Series B milestone." + seed: "Reimbursement strategy should be defined, including target CPT codes and + payer engagement plan. Reimbursement-naivety at seed is the most common + indicator of healthtech failure at later stages." + series_a: "Some form of reimbursement should be demonstrated — even if through + existing codes or pilot payer agreements. A clear pathway to broader + coverage must be articulated." + series_b_plus: "Broad payer coverage is expected for revenue-stage companies. + The transition from pilot payer agreements to at-scale reimbursement is + a critical Series B milestone." data_sources: - source: "CMS Innovation Center Evaluation Reports" year: "2024" - source: "McKinsey Healthcare Practice Reports" year: "2024" - related_metrics: ["revenue-per-patient-per-month", "clinical-validation-stage"] - related_skills: ["business-model-canvas", "pricing-diagnosis"] - caveats: "Reimbursement rates vary dramatically by payer, geography, and product type. Medicare coverage decisions set precedents that commercial payers follow, but not immediately — there is typically a 12-24 month lag. State Medicaid programs have independent coverage decisions." + related_metrics: [ "revenue-per-patient-per-month", "clinical-validation-stage" ] + related_skills: + - business-model-canvas + caveats: "Reimbursement rates vary dramatically by payer, geography, and product + type. Medicare coverage decisions set precedents that commercial payers + follow, but not immediately — there is typically a 12-24 month lag. State + Medicaid programs have independent coverage decisions." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Revenue per Patient per Month" id: "revenue-per-patient-per-month" category: "unit-economics" - definition: "The average monthly revenue generated per active patient on the platform, including all revenue streams: payer reimbursement, patient co-pays, health system SaaS fees allocated per patient, and employer direct-pay allocated per covered life." + definition: "The average monthly revenue generated per active patient on the + platform, including all revenue streams: payer reimbursement, patient + co-pays, health system SaaS fees allocated per patient, and employer + direct-pay allocated per covered life." formula: "Total monthly revenue / Monthly active patients" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $5 per patient per month" - signal: "Revenue per patient too low to cover clinical support costs. The unit economics cannot support the clinical oversight and safety monitoring required for patient-facing health products." + signal: "Revenue per patient too low to cover clinical support costs. The unit + economics cannot support the clinical oversight and safety monitoring + required for patient-facing health products." below_average: value: "$5-$20 per patient per month" - signal: "Low margin per patient. Sustainable only at very high volume with minimal clinical support requirements. Typical of wellness-adjacent products without dedicated reimbursement." + signal: "Low margin per patient. Sustainable only at very high volume with + minimal clinical support requirements. Typical of wellness-adjacent + products without dedicated reimbursement." average: value: "$20-$75 per patient per month" - signal: "Moderate per-patient revenue. Common for remote patient monitoring and chronic disease management platforms with CPT-code-based reimbursement." + signal: "Moderate per-patient revenue. Common for remote patient monitoring and + chronic disease management platforms with CPT-code-based + reimbursement." good: value: "$75-$200 per patient per month" - signal: "Strong per-patient revenue. Typical of digital therapeutics with dedicated reimbursement, specialty-focused platforms, and clinical decision support tools with demonstrated outcome improvement." + signal: "Strong per-patient revenue. Typical of digital therapeutics with + dedicated reimbursement, specialty-focused platforms, and clinical + decision support tools with demonstrated outcome improvement." excellent: value: "> $200 per patient per month" - signal: "Premium per-patient revenue. Achieved by products serving high-acuity conditions, products with pharma co-pay assistance, or products that replace significantly more expensive alternatives." + signal: "Premium per-patient revenue. Achieved by products serving high-acuity + conditions, products with pharma co-pay assistance, or products that + replace significantly more expensive alternatives." stage_notes: - seed: "Revenue per patient is estimated from the reimbursement strategy. Seed-stage companies should model both reimbursed and non-reimbursed scenarios." - series_a: "Actual revenue per patient from pilot deployments should be available. The gap between contracted revenue and realized revenue (patient dropout, engagement decay) must be understood." - series_b_plus: "Revenue per patient should be stable or growing. Expansion through additional services per patient is a key growth lever." + seed: "Revenue per patient is estimated from the reimbursement strategy. + Seed-stage companies should model both reimbursed and non-reimbursed + scenarios." + series_a: "Actual revenue per patient from pilot deployments should be + available. The gap between contracted revenue and realized revenue + (patient dropout, engagement decay) must be understood." + series_b_plus: "Revenue per patient should be stable or growing. Expansion + through additional services per patient is a key growth lever." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "CMS Innovation Center Evaluation Reports" year: "2024" - related_metrics: ["payer-reimbursement-rate", "monthly-active-patients", "patient-engagement-rate"] - related_skills: ["pricing-diagnosis", "business-model-canvas"] - caveats: "Revenue per patient must be interpreted in the context of clinical support costs per patient. A $100/patient/month product that requires $80/patient/month in clinical staffing has fundamentally different economics than one requiring $10/patient/month." + related_metrics: + [ + "payer-reimbursement-rate", + "monthly-active-patients", + "patient-engagement-rate" + ] + related_skills: + - business-model-canvas + caveats: "Revenue per patient must be interpreted in the context of clinical + support costs per patient. A $100/patient/month product that requires + $80/patient/month in clinical staffing has fundamentally different + economics than one requiring $10/patient/month." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Customer Acquisition Cost (per Provider/Health System)" id: "cac-health-system" category: "sales" - definition: "The fully loaded cost to acquire a new health system or provider group customer, including sales team costs, marketing, clinical pilot costs, integration implementation, and regulatory/compliance review costs incurred during the sales process." - formula: "Total sales & marketing cost (including pilot costs) / Number of new health system customers acquired" + definition: "The fully loaded cost to acquire a new health system or provider + group customer, including sales team costs, marketing, clinical pilot + costs, integration implementation, and regulatory/compliance review costs + incurred during the sales process." + formula: "Total sales & marketing cost (including pilot costs) / Number of new + health system customers acquired" unit: "currency" direction: "lower-is-better" benchmarks: poor: value: "> $500K per health system customer" - signal: "Acquisition cost is unsustainably high. The sales process likely includes extensive free pilot periods, custom integration work, and long clinical evaluation cycles that the company is funding entirely." + signal: "Acquisition cost is unsustainably high. The sales process likely + includes extensive free pilot periods, custom integration work, and + long clinical evaluation cycles that the company is funding entirely." below_average: value: "$200K-$500K per health system customer" - signal: "High but not unusual for enterprise health system sales. Acceptable only if contract values and retention rates justify the investment." + signal: "High but not unusual for enterprise health system sales. Acceptable + only if contract values and retention rates justify the investment." average: value: "$75K-$200K per health system customer" - signal: "Moderate CAC for health system sales. Typical for companies with established clinical evidence and streamlined implementation processes." + signal: "Moderate CAC for health system sales. Typical for companies with + established clinical evidence and streamlined implementation + processes." good: value: "$25K-$75K per health system customer" - signal: "Efficient customer acquisition. Indicates strong inbound demand driven by clinical evidence, peer referral, or health system innovation network effects." + signal: "Efficient customer acquisition. Indicates strong inbound demand driven + by clinical evidence, peer referral, or health system innovation + network effects." excellent: value: "< $25K per health system customer" - signal: "Exceptional efficiency. Often achieved through health system innovation programs, EHR marketplace distribution, or products with such strong clinical evidence that they sell themselves." + signal: "Exceptional efficiency. Often achieved through health system innovation + programs, EHR marketplace distribution, or products with such strong + clinical evidence that they sell themselves." stage_notes: - seed: "CAC is difficult to measure at seed — early customers are often acquired through founder relationships. Track the full cost of pilot deployments as a proxy." - series_a: "CAC should be measured for non-founder-sourced customers. The ratio of CAC to first-year contract value indicates commercial viability." - series_b_plus: "CAC should be declining as brand recognition, clinical evidence, and referenceable customers reduce the sales effort required." + seed: "CAC is difficult to measure at seed — early customers are often acquired + through founder relationships. Track the full cost of pilot deployments + as a proxy." + series_a: "CAC should be measured for non-founder-sourced customers. The ratio + of CAC to first-year contract value indicates commercial viability." + series_b_plus: "CAC should be declining as brand recognition, clinical evidence, + and referenceable customers reduce the sales effort required." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "CB Insights State of Digital Health" year: "2024" - related_metrics: ["sales-cycle-length", "contract-value-health-system", "provider-adoption-rate"] - related_skills: ["four-ps-marketing", "blue-ocean-strategy"] - caveats: "Health system CAC must include the cost of clinical pilots, which are often provided free or at reduced cost. Excluding pilot costs from CAC understates the true acquisition cost by 30-60%." + related_metrics: + [ + "sales-cycle-length", + "contract-value-health-system", + "provider-adoption-rate" + ] + related_skills: [ "four-ps-marketing", "blue-ocean-strategy" ] + caveats: "Health system CAC must include the cost of clinical pilots, which are + often provided free or at reduced cost. Excluding pilot costs from CAC + understates the true acquisition cost by 30-60%." - name: "Sales Cycle Length" id: "sales-cycle-length" category: "sales" - definition: "The elapsed time from initial qualified engagement with a health system or provider group buyer to signed contract. In healthtech, this cycle includes clinical evaluation, IT security review, legal review, and often a pilot period." + definition: "The elapsed time from initial qualified engagement with a health + system or provider group buyer to signed contract. In healthtech, this + cycle includes clinical evaluation, IT security review, legal review, and + often a pilot period." formula: "Median days from first qualified meeting to signed contract" unit: "months" direction: "lower-is-better" benchmarks: poor: value: "> 18 months" - signal: "Sales cycle is dangerously long. At this duration, the company must maintain 18+ months of pipeline to sustain growth, and customer requirements may change during the process." + signal: "Sales cycle is dangerously long. At this duration, the company must + maintain 18+ months of pipeline to sustain growth, and customer + requirements may change during the process." below_average: value: "12-18 months" - signal: "Long but within range for complex health system enterprise sales. Common for novel products requiring clinical evaluation committees and pilot deployment." + signal: "Long but within range for complex health system enterprise sales. + Common for novel products requiring clinical evaluation committees and + pilot deployment." average: value: "6-12 months" - signal: "Typical for health system SaaS sales with established clinical evidence. The cycle includes IT review, clinical evaluation, and contract negotiation." + signal: "Typical for health system SaaS sales with established clinical + evidence. The cycle includes IT review, clinical evaluation, and + contract negotiation." good: value: "3-6 months" - signal: "Efficient for healthtech. Achieved by products with strong clinical evidence, streamlined implementation, and established procurement pathways." + signal: "Efficient for healthtech. Achieved by products with strong clinical + evidence, streamlined implementation, and established procurement + pathways." excellent: value: "< 3 months" - signal: "Exceptional speed. Rare for health system enterprise sales. Typically achieved through EHR marketplace distribution, self-serve models for individual providers, or products sold to non-clinical buyers." + signal: "Exceptional speed. Rare for health system enterprise sales. Typically + achieved through EHR marketplace distribution, self-serve models for + individual providers, or products sold to non-clinical buyers." stage_notes: - seed: "Sales cycle length is discovered, not planned, at seed. Early customers teach the company what the real buying process looks like." - series_a: "Sales cycle data from 5-10 deals should inform forecasting and pipeline management. Investors will evaluate whether the sales cycle is compatible with the company's runway." - series_b_plus: "Sales cycle optimization becomes a key efficiency lever. Reducing cycle length by 30% has the same revenue impact as increasing pipeline by 30%." + seed: "Sales cycle length is discovered, not planned, at seed. Early customers + teach the company what the real buying process looks like." + series_a: "Sales cycle data from 5-10 deals should inform forecasting and + pipeline management. Investors will evaluate whether the sales cycle is + compatible with the company's runway." + series_b_plus: "Sales cycle optimization becomes a key efficiency lever. + Reducing cycle length by 30% has the same revenue impact as increasing + pipeline by 30%." data_sources: - source: "CHIME CIO Surveys" year: "2024" - source: "Rock Health Digital Health Funding Report" year: "2024" - related_metrics: ["cac-health-system", "contract-value-health-system"] - related_skills: ["first-mover-strategy", "negotiation-game-theory"] - caveats: "Health system sales cycles are structural, not sales-execution problems. Clinical evaluation, IT security review, and legal review have minimum durations that cannot be compressed through sales technique. The answer is not faster selling but better pipeline management." + related_metrics: [ "cac-health-system", "contract-value-health-system" ] + related_skills: [ "first-mover-strategy", "negotiation-game-theory" ] + caveats: "Health system sales cycles are structural, not sales-execution + problems. Clinical evaluation, IT security review, and legal review have + minimum durations that cannot be compressed through sales technique. The + answer is not faster selling but better pipeline management." - name: "Contract Value (Health System Deals)" id: "contract-value-health-system" category: "sales" - definition: "The total annual contract value of health system enterprise deals, including SaaS fees, implementation fees, and any per-patient or per-encounter fees based on contracted volume." - formula: "Annual SaaS fees + (per-patient/encounter fee x contracted volume) + implementation fees (amortized over contract term)" + definition: "The total annual contract value of health system enterprise deals, + including SaaS fees, implementation fees, and any per-patient or + per-encounter fees based on contracted volume." + formula: "Annual SaaS fees + (per-patient/encounter fee x contracted volume) + + implementation fees (amortized over contract term)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $50K ACV" - signal: "Contract value too low to justify health system enterprise sales motion. The economics do not support the long sales cycle and implementation effort required." + signal: "Contract value too low to justify health system enterprise sales + motion. The economics do not support the long sales cycle and + implementation effort required." below_average: value: "$50K-$150K ACV" - signal: "Low-end enterprise deal. Sustainable if sales cycle is under 6 months and implementation is lightweight. Typical for departmental (not enterprise-wide) deployments." + signal: "Low-end enterprise deal. Sustainable if sales cycle is under 6 months + and implementation is lightweight. Typical for departmental (not + enterprise-wide) deployments." average: value: "$150K-$500K ACV" - signal: "Mid-market health system deal. Justifies dedicated sales effort and implementation support. Common for clinical decision support, analytics, and remote monitoring platforms." + signal: "Mid-market health system deal. Justifies dedicated sales effort and + implementation support. Common for clinical decision support, + analytics, and remote monitoring platforms." good: value: "$500K-$2M ACV" - signal: "Strong enterprise deal. Indicates broad deployment across the health system. The contract likely includes multi-department or system-wide licensing." + signal: "Strong enterprise deal. Indicates broad deployment across the health + system. The contract likely includes multi-department or system-wide + licensing." excellent: value: "> $2M ACV" - signal: "Large enterprise deal. Typically system-wide deployment at a large IDN (Integrated Delivery Network). These deals often include multi-year commitments and strategic partnership elements." + signal: "Large enterprise deal. Typically system-wide deployment at a large IDN + (Integrated Delivery Network). These deals often include multi-year + commitments and strategic partnership elements." stage_notes: - seed: "Contract value is negotiated in early pilots. Founders should resist the temptation to give the product away — even pilot pricing establishes a reference point for future negotiations." - series_a: "Multiple contracts at consistent ACV levels demonstrate repeatable commercial traction. ACV growth from initial to subsequent deals is a positive signal." - series_b_plus: "ACV expansion within existing customers (land-and-expand) is as important as new customer ACV. Multi-year contracts with annual escalators provide revenue predictability." + seed: "Contract value is negotiated in early pilots. Founders should resist the + temptation to give the product away — even pilot pricing establishes a + reference point for future negotiations." + series_a: "Multiple contracts at consistent ACV levels demonstrate repeatable + commercial traction. ACV growth from initial to subsequent deals is a + positive signal." + series_b_plus: "ACV expansion within existing customers (land-and-expand) is as + important as new customer ACV. Multi-year contracts with annual + escalators provide revenue predictability." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "KLAS Research — Emerging Technology Studies" year: "2024" - related_metrics: ["sales-cycle-length", "cac-health-system", "revenue-per-patient-per-month"] - related_skills: ["pricing-diagnosis", "competitive-negotiation"] - caveats: "Contract value must be distinguished from realized revenue. Health system contracts often include ramp periods, volume-contingent pricing, and outcome-based components. A $1M ACV contract that is 50% outcome-contingent has very different economics than a $500K fully committed contract." + related_metrics: [ "sales-cycle-length", "cac-health-system", "revenue-per-patient-per-month" ] + related_skills: + - competitive-negotiation + caveats: "Contract value must be distinguished from realized revenue. Health + system contracts often include ramp periods, volume-contingent pricing, + and outcome-based components. A $1M ACV contract that is 50% + outcome-contingent has very different economics than a $500K fully + committed contract." + related_content: + - kind: diagnostic + ref: pricing-diagnosis # ───────────────────────────────────────────── # SATISFACTION & TRUST METRICS @@ -614,146 +1012,241 @@ benchmarks: - name: "Patient Satisfaction Score" id: "patient-satisfaction-score" category: "product" - definition: "A composite patient experience metric derived from validated survey instruments (CAHPS, SUS adapted for health, proprietary NPS), measuring patient satisfaction with the digital health experience — distinct from clinical outcome satisfaction." - formula: "Mean score on validated patient satisfaction instrument, normalized to 0-100 scale" + definition: "A composite patient experience metric derived from validated survey + instruments (CAHPS, SUS adapted for health, proprietary NPS), measuring + patient satisfaction with the digital health experience — distinct from + clinical outcome satisfaction." + formula: "Mean score on validated patient satisfaction instrument, normalized to + 0-100 scale" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 50" - signal: "Patients actively dislike the experience. High abandonment risk. In healthtech, dissatisfied patients stop using the product — which means the clinical intervention stops, outcomes deteriorate, and the value proposition collapses." + signal: "Patients actively dislike the experience. High abandonment risk. In + healthtech, dissatisfied patients stop using the product — which means + the clinical intervention stops, outcomes deteriorate, and the value + proposition collapses." below_average: value: "50-65" - signal: "Below average patient experience. The product may deliver clinical value but the experience creates friction that limits engagement and retention." + signal: "Below average patient experience. The product may deliver clinical + value but the experience creates friction that limits engagement and + retention." average: value: "65-75" - signal: "Adequate patient experience. Patients tolerate the product for its clinical benefits. Room for improvement, especially in UX design for diverse health literacy levels." + signal: "Adequate patient experience. Patients tolerate the product for its + clinical benefits. Room for improvement, especially in UX design for + diverse health literacy levels." good: value: "75-85" - signal: "Strong patient experience. Patients recommend the product to peers. This level supports word-of-mouth growth and payer satisfaction metrics." + signal: "Strong patient experience. Patients recommend the product to peers. + This level supports word-of-mouth growth and payer satisfaction + metrics." excellent: value: "> 85" - signal: "Exceptional patient experience. Rare in healthcare technology. The product has achieved the difficult balance of clinical rigor and consumer-grade UX." + signal: "Exceptional patient experience. Rare in healthcare technology. The + product has achieved the difficult balance of clinical rigor and + consumer-grade UX." stage_notes: - seed: "Patient satisfaction is measured qualitatively through pilot participant interviews. Net Promoter Score is a reasonable proxy at this stage." - series_a: "Quantitative satisfaction data from pilot studies should be available. Comparison to benchmark scores in the therapeutic area provides context." - series_b_plus: "Patient satisfaction should be tracked continuously and reported to health system customers as part of QBR materials." + seed: "Patient satisfaction is measured qualitatively through pilot participant + interviews. Net Promoter Score is a reasonable proxy at this stage." + series_a: "Quantitative satisfaction data from pilot studies should be + available. Comparison to benchmark scores in the therapeutic area + provides context." + series_b_plus: "Patient satisfaction should be tracked continuously and reported + to health system customers as part of QBR materials." data_sources: - source: "IQVIA Digital Health Trends" year: "2024" - source: "AMA Digital Health Research" year: "2024" - related_metrics: ["patient-engagement-rate", "provider-nps"] - related_skills: ["net-promoter-score", "emotional-intelligence"] - caveats: "Patient satisfaction and clinical outcomes are not always correlated. Patients may be satisfied with a product that does not improve outcomes (pleasant but ineffective) or dissatisfied with one that does (effective but unpleasant). Both dimensions must be tracked independently." + related_metrics: [ "patient-engagement-rate", "provider-nps" ] + related_skills: [ "net-promoter-score", "emotional-intelligence" ] + caveats: "Patient satisfaction and clinical outcomes are not always correlated. + Patients may be satisfied with a product that does not improve outcomes + (pleasant but ineffective) or dissatisfied with one that does (effective + but unpleasant). Both dimensions must be tracked independently." - name: "Provider NPS" id: "provider-nps" category: "product" - definition: "Net Promoter Score measured among providers (physicians, nurses, clinical staff) who use the product. Reflects whether clinicians would recommend the product to colleagues — the single most powerful distribution mechanism in healthcare." + definition: "Net Promoter Score measured among providers (physicians, nurses, + clinical staff) who use the product. Reflects whether clinicians would + recommend the product to colleagues — the single most powerful + distribution mechanism in healthcare." formula: "% Promoters (9-10) - % Detractors (0-6) among surveyed providers" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 0" - signal: "More detractors than promoters among providers. The product is generating negative word-of-mouth in clinical networks — an existential threat given how heavily providers rely on peer recommendations." + signal: "More detractors than promoters among providers. The product is + generating negative word-of-mouth in clinical networks — an + existential threat given how heavily providers rely on peer + recommendations." below_average: value: "0-20" - signal: "Tepid provider sentiment. The product is tolerated but not championed. Organic expansion through provider referral will not occur at this level." + signal: "Tepid provider sentiment. The product is tolerated but not championed. + Organic expansion through provider referral will not occur at this + level." average: value: "20-40" - signal: "Positive but not enthusiastic. Providers see value but also experience friction. Most health IT products cluster in this range." + signal: "Positive but not enthusiastic. Providers see value but also experience + friction. Most health IT products cluster in this range." good: value: "40-60" - signal: "Strong provider advocacy. Providers actively recommend the product to colleagues. This is the threshold where organic adoption within and across health systems accelerates." + signal: "Strong provider advocacy. Providers actively recommend the product to + colleagues. This is the threshold where organic adoption within and + across health systems accelerates." excellent: value: "> 60" - signal: "Exceptional provider advocacy. Rare in health IT where clinician satisfaction with technology is chronically low. A provider NPS above 60 is a formidable competitive moat." + signal: "Exceptional provider advocacy. Rare in health IT where clinician + satisfaction with technology is chronically low. A provider NPS above + 60 is a formidable competitive moat." stage_notes: - seed: "Provider NPS from pilot clinicians should be collected. Even a small sample (n=10-20) reveals whether clinicians find the product genuinely valuable." - series_a: "Provider NPS should be tracked across all deployment sites. Variation between sites reveals implementation quality and workflow fit differences." - series_b_plus: "Provider NPS should be published in sales materials and QBR reports. High provider NPS is a differentiated asset in health system procurement processes." + seed: "Provider NPS from pilot clinicians should be collected. Even a small + sample (n=10-20) reveals whether clinicians find the product genuinely + valuable." + series_a: "Provider NPS should be tracked across all deployment sites. Variation + between sites reveals implementation quality and workflow fit + differences." + series_b_plus: "Provider NPS should be published in sales materials and QBR + reports. High provider NPS is a differentiated asset in health system + procurement processes." data_sources: - source: "KLAS Research — Provider Satisfaction" year: "2024" - source: "AMA Digital Health Research" year: "2024" - related_metrics: ["provider-adoption-rate", "patient-satisfaction-score"] - related_skills: ["net-promoter-score", "trust-equation"] - caveats: "Provider NPS is influenced by implementation quality as much as product quality. A good product poorly implemented will receive low NPS. Always segment NPS by deployment maturity to separate product quality from implementation quality." + related_metrics: [ "provider-adoption-rate", "patient-satisfaction-score" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "Provider NPS is influenced by implementation quality as much as + product quality. A good product poorly implemented will receive low NPS. + Always segment NPS by deployment maturity to separate product quality from + implementation quality." - name: "HIPAA Compliance Score" id: "hipaa-compliance-score" category: "efficiency" - definition: "A composite metric measuring the completeness and maturity of the company's HIPAA compliance program, including technical safeguards, administrative safeguards, physical safeguards, breach notification procedures, and business associate agreement coverage." - formula: "Weighted composite across HIPAA Security Rule requirements: Technical (35%) + Administrative (35%) + Physical (15%) + BAA coverage (15%), scored 0-100" + definition: "A composite metric measuring the completeness and maturity of the + company's HIPAA compliance program, including technical safeguards, + administrative safeguards, physical safeguards, breach notification + procedures, and business associate agreement coverage." + formula: "Weighted composite across HIPAA Security Rule requirements: Technical + (35%) + Administrative (35%) + Physical (15%) + BAA coverage (15%), scored + 0-100" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "Score < 50 — Material gaps in HIPAA compliance" - signal: "The company is operating with significant legal and operational risk. A breach or OCR audit at this compliance level could result in civil monetary penalties ($100-$50K per violation, up to $1.5M per violation category per year), corrective action plans, and reputational damage that destroys customer relationships." + signal: "The company is operating with significant legal and operational risk. A + breach or OCR audit at this compliance level could result in civil + monetary penalties ($100-$50K per violation, up to $1.5M per violation + category per year), corrective action plans, and reputational damage + that destroys customer relationships." below_average: - value: "Score 50-70 — Basic safeguards in place but gaps in documentation, training, or BAA coverage" - signal: "Minimum compliance posture. Sufficient to pass a cursory review but vulnerable to OCR investigation. Health system customers' security teams will identify gaps during vendor assessment." + value: "Score 50-70 — Basic safeguards in place but gaps in documentation, + training, or BAA coverage" + signal: "Minimum compliance posture. Sufficient to pass a cursory review but + vulnerable to OCR investigation. Health system customers' security + teams will identify gaps during vendor assessment." average: - value: "Score 70-85 — Comprehensive compliance program with regular risk assessments, documented policies, and staff training" - signal: "Solid compliance posture. Sufficient for most health system procurement processes. Annual risk assessment conducted and documented." + value: "Score 70-85 — Comprehensive compliance program with regular risk + assessments, documented policies, and staff training" + signal: "Solid compliance posture. Sufficient for most health system procurement + processes. Annual risk assessment conducted and documented." good: - value: "Score 85-95 — Mature compliance program with independent audit, incident response testing, and continuous monitoring" - signal: "Strong compliance. Third-party HIPAA audit completed (e.g., HITRUST CSF certification). Health system customers can rely on independent validation rather than conducting their own assessment." + value: "Score 85-95 — Mature compliance program with independent audit, incident + response testing, and continuous monitoring" + signal: "Strong compliance. Third-party HIPAA audit completed (e.g., HITRUST CSF + certification). Health system customers can rely on independent + validation rather than conducting their own assessment." excellent: - value: "Score > 95 — HITRUST CSF certified, SOC 2 Type II, ongoing penetration testing, zero findings on most recent audit" - signal: "Best-in-class compliance. HITRUST certification with SOC 2 Type II provides the highest assurance level. Accelerates health system sales by eliminating security review as a sales cycle bottleneck." + value: "Score > 95 — HITRUST CSF certified, SOC 2 Type II, ongoing penetration + testing, zero findings on most recent audit" + signal: "Best-in-class compliance. HITRUST certification with SOC 2 Type II + provides the highest assurance level. Accelerates health system sales + by eliminating security review as a sales cycle bottleneck." stage_notes: - seed: "Foundational HIPAA compliance (encryption, access controls, BAAs with all vendors) must be in place from day one. Cutting corners on HIPAA at seed creates technical and legal debt that compounds." - series_a: "A formal risk assessment and documented compliance program should be completed. Third-party audit (HITRUST or SOC 2) should be on the near-term roadmap." - series_b_plus: "HITRUST CSF certification or SOC 2 Type II should be obtained. Large health system customers will require one or both." + seed: "Foundational HIPAA compliance (encryption, access controls, BAAs with all + vendors) must be in place from day one. Cutting corners on HIPAA at seed + creates technical and legal debt that compounds." + series_a: "A formal risk assessment and documented compliance program should be + completed. Third-party audit (HITRUST or SOC 2) should be on the + near-term roadmap." + series_b_plus: "HITRUST CSF certification or SOC 2 Type II should be obtained. + Large health system customers will require one or both." data_sources: - source: "HHS OCR Enforcement Data" year: "2024" - source: "CHIME CIO Surveys" year: "2024" - related_metrics: ["data-security-incident-rate"] - related_skills: ["balanced-scorecard", "vuca-framework"] - caveats: "HIPAA compliance is a floor, not a ceiling. Passing a HIPAA audit does not mean the company has strong security — it means the company meets minimum federal requirements. State health data privacy laws (e.g., California CMIA, New York SHIELD Act) may impose additional requirements." + related_metrics: [ "data-security-incident-rate" ] + related_skills: [ "balanced-scorecard", "vuca-framework" ] + caveats: "HIPAA compliance is a floor, not a ceiling. Passing a HIPAA audit does + not mean the company has strong security — it means the company meets + minimum federal requirements. State health data privacy laws (e.g., + California CMIA, New York SHIELD Act) may impose additional requirements." - name: "Data Security Incident Rate" id: "data-security-incident-rate" category: "efficiency" - definition: "The number of data security incidents involving protected health information (PHI) per quarter, including breaches, unauthorized access events, and near-misses. A breach affecting 500+ individuals triggers HHS notification and public disclosure." + definition: "The number of data security incidents involving protected health + information (PHI) per quarter, including breaches, unauthorized access + events, and near-misses. A breach affecting 500+ individuals triggers HHS + notification and public disclosure." formula: "COUNT(security incidents involving PHI) per quarter" unit: "ratio" direction: "lower-is-better" benchmarks: poor: value: "> 3 incidents per quarter or any breach affecting 500+ individuals" - signal: "Critical security problem. A breach affecting 500+ individuals triggers HHS notification, public disclosure on the HHS 'Wall of Shame,' mandatory OCR investigation, and potential civil monetary penalties. The business may not survive the reputational damage." + signal: "Critical security problem. A breach affecting 500+ individuals triggers + HHS notification, public disclosure on the HHS 'Wall of Shame,' + mandatory OCR investigation, and potential civil monetary penalties. + The business may not survive the reputational damage." below_average: value: "2-3 incidents per quarter (sub-500 individuals)" - signal: "Concerning incident rate. Each incident requires breach risk assessment under HIPAA, notification to affected individuals, and internal investigation. Cumulative incidents suggest systemic security weaknesses." + signal: "Concerning incident rate. Each incident requires breach risk assessment + under HIPAA, notification to affected individuals, and internal + investigation. Cumulative incidents suggest systemic security + weaknesses." average: value: "1 incident per quarter (sub-500 individuals)" - signal: "Occasional incidents within range for growing healthtech companies. Each incident should trigger root cause analysis and security improvement." + signal: "Occasional incidents within range for growing healthtech companies. + Each incident should trigger root cause analysis and security + improvement." good: value: "0-1 incidents per year" - signal: "Strong security posture. Incident rate consistent with mature security programs. Proactive threat monitoring and security testing are keeping pace with threat evolution." + signal: "Strong security posture. Incident rate consistent with mature security + programs. Proactive threat monitoring and security testing are keeping + pace with threat evolution." excellent: - value: "Zero incidents for 12+ months with active penetration testing and threat monitoring" - signal: "Exceptional security. Not merely the absence of detected incidents but the presence of active security testing that validates the security posture continuously." + value: "Zero incidents for 12+ months with active penetration testing and threat + monitoring" + signal: "Exceptional security. Not merely the absence of detected incidents but + the presence of active security testing that validates the security + posture continuously." stage_notes: - seed: "Zero incidents is the only acceptable target from day one. A PHI breach at seed stage can destroy the company before it begins." - series_a: "Incident response procedures should be documented and tested. Penetration testing should be conducted at least annually." - series_b_plus: "Continuous security monitoring and regular penetration testing (quarterly) are expected. Health system customers will audit incident history during procurement." + seed: "Zero incidents is the only acceptable target from day one. A PHI breach + at seed stage can destroy the company before it begins." + series_a: "Incident response procedures should be documented and tested. + Penetration testing should be conducted at least annually." + series_b_plus: "Continuous security monitoring and regular penetration testing + (quarterly) are expected. Health system customers will audit incident + history during procurement." data_sources: - source: "HHS OCR Breach Portal" year: "2024" - source: "HITRUST Cyber Threat Intelligence Reports" year: "2024" - related_metrics: ["hipaa-compliance-score"] - related_skills: ["black-swans", "systems-thinking"] - caveats: "Zero incidents may reflect a lack of detection capability rather than a lack of incidents. Security incident metrics must be paired with proactive security testing (penetration testing, red teaming) to distinguish between 'no incidents' and 'no detected incidents.'" + related_metrics: [ "hipaa-compliance-score" ] + related_skills: [ "black-swans", "systems-thinking" ] + caveats: "Zero incidents may reflect a lack of detection capability rather than + a lack of incidents. Security incident metrics must be paired with + proactive security testing (penetration testing, red teaming) to + distinguish between 'no incidents' and 'no detected incidents.'" # ───────────────────────────────────────────── # RETENTION & CHURN METRICS @@ -762,74 +1255,125 @@ benchmarks: - name: "Churn Rate (Provider/Health System)" id: "churn-rate-provider" category: "retention" - definition: "The percentage of provider or health system customers who terminate their contract or fail to renew in a given period. In healthtech, provider churn has both business and clinical implications — when a health system leaves, patients lose access to the intervention." + definition: "The percentage of provider or health system customers who terminate + their contract or fail to renew in a given period. In healthtech, provider + churn has both business and clinical implications — when a health system + leaves, patients lose access to the intervention." formula: "Customers lost in period / Customers at start of period x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 20% annual churn" - signal: "Severe retention failure. Losing one in five health system customers annually means the company must replace its entire customer base every five years just to maintain revenue. This rate also suggests the product is not delivering sustained clinical or operational value." + signal: "Severe retention failure. Losing one in five health system customers + annually means the company must replace its entire customer base every + five years just to maintain revenue. This rate also suggests the + product is not delivering sustained clinical or operational value." below_average: value: "15-20% annual churn" - signal: "High churn that undermines growth economics. Each churned health system represents lost patients, lost clinical data continuity, and lost reference potential." + signal: "High churn that undermines growth economics. Each churned health system + represents lost patients, lost clinical data continuity, and lost + reference potential." average: value: "10-15% annual churn" - signal: "Moderate churn. Typical for healthtech companies in early scaling phase where implementation quality varies across customers." + signal: "Moderate churn. Typical for healthtech companies in early scaling phase + where implementation quality varies across customers." good: value: "5-10% annual churn" - signal: "Strong retention. Most health system customers are renewing and expanding. Churn is concentrated among poor-fit customers or those with organizational changes (M&A, leadership turnover)." + signal: "Strong retention. Most health system customers are renewing and + expanding. Churn is concentrated among poor-fit customers or those + with organizational changes (M&A, leadership turnover)." excellent: value: "< 5% annual churn" - signal: "Exceptional retention. The product is embedded in clinical workflow and delivering sustained value. Health systems consider it a critical part of their technology infrastructure." + signal: "Exceptional retention. The product is embedded in clinical workflow and + delivering sustained value. Health systems consider it a critical part + of their technology infrastructure." stage_notes: - seed: "Churn is unmeasurable with a few pilot customers. Focus on qualitative renewal intent signals — would this customer renew at full price?" - series_a: "First renewal data should be available. The transition from free/reduced pilot to paid contract is the moment of truth for retention." - series_b_plus: "Churn should be disaggregated by customer cohort, deployment size, and therapeutic area. Identifying patterns in churn enables targeted retention interventions." + seed: "Churn is unmeasurable with a few pilot customers. Focus on qualitative + renewal intent signals — would this customer renew at full price?" + series_a: "First renewal data should be available. The transition from + free/reduced pilot to paid contract is the moment of truth for + retention." + series_b_plus: "Churn should be disaggregated by customer cohort, deployment + size, and therapeutic area. Identifying patterns in churn enables + targeted retention interventions." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "KLAS Research — Emerging Technology Studies" year: "2024" - related_metrics: ["churn-rate-patient", "provider-nps", "provider-adoption-rate"] - related_skills: ["net-promoter-score", "systems-thinking"] - caveats: "Health system churn often follows personnel changes — when the clinical champion who adopted the product leaves, the contract is at risk. Reducing key-person dependency requires embedding the product in workflow rather than relying on individual advocacy." + related_metrics: [ "churn-rate-patient", "provider-nps", "provider-adoption-rate" ] + related_skills: [ "net-promoter-score", "systems-thinking" ] + caveats: "Health system churn often follows personnel changes — when the + clinical champion who adopted the product leaves, the contract is at risk. + Reducing key-person dependency requires embedding the product in workflow + rather than relying on individual advocacy." - name: "Churn Rate (Patient)" id: "churn-rate-patient" category: "retention" - definition: "The percentage of enrolled patients who disengage from the product in a given period, measured as patients who have not completed a clinical engagement action in 30+ days. Patient churn in healthtech is not merely a business metric — it means a patient is no longer receiving the intended clinical intervention." - formula: "Patients inactive for 30+ days in period / Patients active at start of period x 100" + definition: "The percentage of enrolled patients who disengage from the product + in a given period, measured as patients who have not completed a clinical + engagement action in 30+ days. Patient churn in healthtech is not merely a + business metric — it means a patient is no longer receiving the intended + clinical intervention." + formula: "Patients inactive for 30+ days in period / Patients active at start of + period x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 40% monthly churn" - signal: "Catastrophic engagement failure. Most patients abandon the product within weeks of enrollment. The clinical intervention is not being delivered to the majority of patients. Clinical outcome claims are undermined." + signal: "Catastrophic engagement failure. Most patients abandon the product + within weeks of enrollment. The clinical intervention is not being + delivered to the majority of patients. Clinical outcome claims are + undermined." below_average: value: "25-40% monthly churn" - signal: "High attrition that limits clinical effectiveness. Typical of products with poor onboarding, low perceived value, or excessive burden on patients." + signal: "High attrition that limits clinical effectiveness. Typical of products + with poor onboarding, low perceived value, or excessive burden on + patients." average: value: "15-25% monthly churn" - signal: "Moderate attrition. Common in digital health, where patient engagement naturally decays over time. The challenge is to flatten the engagement curve." + signal: "Moderate attrition. Common in digital health, where patient engagement + naturally decays over time. The challenge is to flatten the engagement + curve." good: value: "8-15% monthly churn" - signal: "Strong patient retention. The product maintains engagement beyond the initial novelty period. Clinical outcome data at this retention level is credible." + signal: "Strong patient retention. The product maintains engagement beyond the + initial novelty period. Clinical outcome data at this retention level + is credible." excellent: value: "< 8% monthly churn" - signal: "Exceptional patient retention. Rare in digital health. Typically achieved by products with strong provider reinforcement loops, tangible daily value, and personalized engagement." + signal: "Exceptional patient retention. Rare in digital health. Typically + achieved by products with strong provider reinforcement loops, + tangible daily value, and personalized engagement." stage_notes: - seed: "Patient churn patterns are being discovered. The shape of the engagement decay curve (steep initial drop vs. gradual decline vs. flattening) is more informative than the rate itself." - series_a: "Patient retention data across multiple cohorts should show improving trends as the product evolves. Cohort-over-cohort improvement is a key investor signal." - series_b_plus: "Patient retention at scale must support clinical outcome claims. If the product's clinical study assumed 70% engagement but real-world engagement is 30%, outcome expectations must be adjusted." + seed: "Patient churn patterns are being discovered. The shape of the engagement + decay curve (steep initial drop vs. gradual decline vs. flattening) is + more informative than the rate itself." + series_a: "Patient retention data across multiple cohorts should show improving + trends as the product evolves. Cohort-over-cohort improvement is a key + investor signal." + series_b_plus: "Patient retention at scale must support clinical outcome claims. + If the product's clinical study assumed 70% engagement but real-world + engagement is 30%, outcome expectations must be adjusted." data_sources: - source: "IQVIA Digital Health Trends" year: "2024" - source: "Journal of Medical Internet Research — Engagement Studies" year: "2024" - related_metrics: ["patient-engagement-rate", "monthly-active-patients", "patient-satisfaction-score"] - related_skills: ["product-life-cycle", "systems-thinking"] - caveats: "Not all patient churn is negative. Patients who complete a therapeutic protocol and graduate from the product are 'positive churn' — they have received the intended intervention. Separate therapeutic completion from disengagement in churn analysis." + related_metrics: + [ + "patient-engagement-rate", + "monthly-active-patients", + "patient-satisfaction-score" + ] + related_skills: [ "product-life-cycle", "systems-thinking" ] + caveats: "Not all patient churn is negative. Patients who complete a therapeutic + protocol and graduate from the product are 'positive churn' — they have + received the intended intervention. Separate therapeutic completion from + disengagement in churn analysis." # ───────────────────────────────────────────── # FINANCIAL METRICS @@ -838,107 +1382,181 @@ benchmarks: - name: "Gross Margin" id: "gross-margin" category: "financial" - definition: "Revenue minus cost of goods sold as a percentage of revenue. In healthtech, COGS includes not only hosting and infrastructure but also clinical staff costs (if the product requires clinician involvement for delivery), regulatory compliance costs allocated to service delivery, and clinical content maintenance." + definition: "Revenue minus cost of goods sold as a percentage of revenue. In + healthtech, COGS includes not only hosting and infrastructure but also + clinical staff costs (if the product requires clinician involvement for + delivery), regulatory compliance costs allocated to service delivery, and + clinical content maintenance." formula: "(Revenue - COGS) / Revenue x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 40%" - signal: "Margin too low for a technology company. The product likely requires significant human clinical intervention per patient, making it a services business with a technology wrapper." + signal: "Margin too low for a technology company. The product likely requires + significant human clinical intervention per patient, making it a + services business with a technology wrapper." below_average: value: "40-55%" - signal: "Below software margins. Common for healthtech products with embedded clinical services (telehealth with employed clinicians, RPM with nurse monitoring). Investors will question scalability." + signal: "Below software margins. Common for healthtech products with embedded + clinical services (telehealth with employed clinicians, RPM with nurse + monitoring). Investors will question scalability." average: value: "55-70%" - signal: "Moderate margins. Typical for healthtech products with some clinical service component. Improving margins through automation and AI-assisted clinical workflows is a common growth strategy." + signal: "Moderate margins. Typical for healthtech products with some clinical + service component. Improving margins through automation and + AI-assisted clinical workflows is a common growth strategy." good: value: "70-80%" - signal: "Software-like margins. Achieved by products that deliver value through technology with minimal per-patient clinical staff cost. This is the target range for scalable healthtech." + signal: "Software-like margins. Achieved by products that deliver value through + technology with minimal per-patient clinical staff cost. This is the + target range for scalable healthtech." excellent: value: "> 80%" - signal: "Pure software margins. Typical for health data analytics, clinical decision support tools, and administrative workflow products that do not require clinical staff per encounter." + signal: "Pure software margins. Typical for health data analytics, clinical + decision support tools, and administrative workflow products that do + not require clinical staff per encounter." stage_notes: - seed: "Gross margin is estimated at seed. The key question is whether the product's clinical model requires human clinicians per patient interaction (services) or whether technology delivers the intervention (software)." - series_a: "Actual gross margin from revenue-generating operations should be calculated. If below 50%, a clear path to margin expansion must be articulated." - series_b_plus: "Gross margin should be trending toward 60%+. Companies with clinical services components should show a path to automating clinical workflows." + seed: "Gross margin is estimated at seed. The key question is whether the + product's clinical model requires human clinicians per patient + interaction (services) or whether technology delivers the intervention + (software)." + series_a: "Actual gross margin from revenue-generating operations should be + calculated. If below 50%, a clear path to margin expansion must be + articulated." + series_b_plus: "Gross margin should be trending toward 60%+. Companies with + clinical services components should show a path to automating clinical + workflows." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "CB Insights State of Digital Health" year: "2024" - related_metrics: ["revenue-per-patient-per-month", "r-and-d-pct-of-revenue"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "Healthtech gross margin classification is contested. Whether clinical staff costs belong in COGS or OpEx depends on whether clinicians are essential to product delivery (COGS) or provide supplementary support (OpEx). Be consistent and transparent about classification methodology." + related_metrics: [ "revenue-per-patient-per-month", "r-and-d-pct-of-revenue" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Healthtech gross margin classification is contested. Whether clinical + staff costs belong in COGS or OpEx depends on whether clinicians are + essential to product delivery (COGS) or provide supplementary support + (OpEx). Be consistent and transparent about classification methodology." - name: "R&D as % of Revenue (Clinical + Technical)" id: "r-and-d-pct-of-revenue" category: "efficiency" - definition: "The percentage of revenue invested in research and development, including both technical R&D (software engineering, infrastructure, AI/ML development) and clinical R&D (clinical study design and execution, regulatory affairs, medical writing, clinical evidence generation)." + definition: "The percentage of revenue invested in research and development, + including both technical R&D (software engineering, infrastructure, AI/ML + development) and clinical R&D (clinical study design and execution, + regulatory affairs, medical writing, clinical evidence generation)." formula: "(Technical R&D spend + Clinical R&D spend) / Total revenue x 100" unit: "percentage" direction: "target-range" benchmarks: poor: value: "> 80% of revenue (at growth stage) or < 15% (at any stage)" - signal: "Either unsustainably high R&D spend that depletes capital without corresponding clinical or commercial progress, or dangerously low investment that starves the clinical evidence pipeline and product development." + signal: "Either unsustainably high R&D spend that depletes capital without + corresponding clinical or commercial progress, or dangerously low + investment that starves the clinical evidence pipeline and product + development." below_average: value: "50-80% of revenue (growth stage)" - signal: "High R&D intensity. Acceptable during clinical validation phase but must be declining as a percentage of revenue as the company transitions to commercial scaling." + signal: "High R&D intensity. Acceptable during clinical validation phase but + must be declining as a percentage of revenue as the company + transitions to commercial scaling." average: value: "30-50% of revenue" - signal: "Typical for healthtech companies balancing ongoing clinical evidence generation with product development. The split between clinical and technical R&D reveals strategic priorities." + signal: "Typical for healthtech companies balancing ongoing clinical evidence + generation with product development. The split between clinical and + technical R&D reveals strategic priorities." good: value: "20-30% of revenue" - signal: "Efficient R&D investment. Indicates the company has passed the heaviest clinical validation investment phase and is optimizing returns on existing evidence assets." + signal: "Efficient R&D investment. Indicates the company has passed the heaviest + clinical validation investment phase and is optimizing returns on + existing evidence assets." excellent: value: "15-20% of revenue with continued clinical evidence publication" - signal: "Optimal balance. Sufficient investment to maintain clinical evidence leadership and product innovation while preserving capital for commercial scaling." + signal: "Optimal balance. Sufficient investment to maintain clinical evidence + leadership and product innovation while preserving capital for + commercial scaling." stage_notes: - seed: "R&D is effectively 100% of spend at seed. The relevant question is the split between clinical and technical R&D — both must be funded." - series_a: "R&D split (clinical vs. technical) should be explicit. Investors assess whether the company is allocating sufficient resources to clinical evidence generation alongside product development." - series_b_plus: "R&D as percentage of revenue should be declining as revenue scales. However, cutting clinical R&D too aggressively leaves the company vulnerable to competitors who build stronger evidence." + seed: "R&D is effectively 100% of spend at seed. The relevant question is the + split between clinical and technical R&D — both must be funded." + series_a: "R&D split (clinical vs. technical) should be explicit. Investors + assess whether the company is allocating sufficient resources to + clinical evidence generation alongside product development." + series_b_plus: "R&D as percentage of revenue should be declining as revenue + scales. However, cutting clinical R&D too aggressively leaves the + company vulnerable to competitors who build stronger evidence." data_sources: - source: "Rock Health Digital Health Funding Report" year: "2024" - source: "Deloitte Life Sciences Outlook" year: "2025" - related_metrics: ["gross-margin", "clinical-validation-stage"] - related_skills: ["balanced-scorecard", "eisenhower-matrix"] - caveats: "Clinical R&D in healthtech is not optional — it is the equivalent of product R&D in software. Companies that cut clinical evidence investment to improve short-term financials risk losing the evidence advantage that sustains their market position." + related_metrics: [ "gross-margin", "clinical-validation-stage" ] + related_skills: [ "balanced-scorecard", "eisenhower-matrix" ] + caveats: "Clinical R&D in healthtech is not optional — it is the equivalent of + product R&D in software. Companies that cut clinical evidence investment + to improve short-term financials risk losing the evidence advantage that + sustains their market position." - name: "Time to Value (Implementation at Health System)" id: "time-to-value-implementation" category: "sales" - definition: "The elapsed time from contract signing to the health system customer realizing measurable value from the product — defined as the point at which the system is live, providers are trained, and clinical workflow integration is complete." + definition: "The elapsed time from contract signing to the health system + customer realizing measurable value from the product — defined as the + point at which the system is live, providers are trained, and clinical + workflow integration is complete." formula: "Date of measurable value realization — Date of contract signing" unit: "months" direction: "lower-is-better" benchmarks: poor: value: "> 12 months" - signal: "Implementation is a major bottleneck. Health system customers become frustrated, internal champions lose political capital, and the risk of pre-go-live cancellation increases." + signal: "Implementation is a major bottleneck. Health system customers become + frustrated, internal champions lose political capital, and the risk of + pre-go-live cancellation increases." below_average: value: "6-12 months" - signal: "Long implementation. Common for complex EHR integrations and enterprise-wide deployments but creates significant risk of customer disengagement." + signal: "Long implementation. Common for complex EHR integrations and + enterprise-wide deployments but creates significant risk of customer + disengagement." average: value: "3-6 months" - signal: "Typical for healthtech products requiring EHR integration, provider training, and clinical workflow adaptation. Manageable if expectations are set clearly during the sales process." + signal: "Typical for healthtech products requiring EHR integration, provider + training, and clinical workflow adaptation. Manageable if expectations + are set clearly during the sales process." good: value: "1-3 months" - signal: "Efficient implementation. Achieved through standardized deployment playbooks, pre-built EHR integrations, and scalable provider training programs." + signal: "Efficient implementation. Achieved through standardized deployment + playbooks, pre-built EHR integrations, and scalable provider training + programs." excellent: value: "< 1 month" - signal: "Rapid time to value. Exceptional for health system enterprise products. Typically achieved by cloud-native products with self-service EHR integration (SMART on FHIR) and on-demand training." + signal: "Rapid time to value. Exceptional for health system enterprise products. + Typically achieved by cloud-native products with self-service EHR + integration (SMART on FHIR) and on-demand training." stage_notes: - seed: "Time to value is being optimized during early deployments. Each pilot reveals integration and training bottlenecks that inform the implementation playbook." - series_a: "Implementation time should be trending downward as the company standardizes deployment. A repeatable implementation playbook is a key scaling prerequisite." - series_b_plus: "Time to value should be a competitive advantage. Companies that deploy faster earn revenue faster, generate outcomes data faster, and create stronger customer relationships." + seed: "Time to value is being optimized during early deployments. Each pilot + reveals integration and training bottlenecks that inform the + implementation playbook." + series_a: "Implementation time should be trending downward as the company + standardizes deployment. A repeatable implementation playbook is a key + scaling prerequisite." + series_b_plus: "Time to value should be a competitive advantage. Companies that + deploy faster earn revenue faster, generate outcomes data faster, and + create stronger customer relationships." data_sources: - source: "KLAS Research — Implementation Studies" year: "2024" - source: "CHIME CIO Surveys" year: "2024" - related_metrics: ["provider-adoption-rate", "clinical-workflow-integration-score", "cac-health-system"] - related_skills: ["kotter-change-model", "smart-goals"] - caveats: "Time to value must be measured from the customer's perspective, not the company's. Going live is not value realization — value realization occurs when providers are actively using the product and clinical or operational outcomes are measurable. Many healthtech companies declare 'go-live' before the customer experiences value." + related_metrics: + [ + "provider-adoption-rate", + "clinical-workflow-integration-score", + "cac-health-system" + ] + related_skills: [ "kotter-change-model", "smart-goals" ] + caveats: "Time to value must be measured from the customer's perspective, not + the company's. Going live is not value realization — value realization + occurs when providers are actively using the product and clinical or + operational outcomes are measurable. Many healthtech companies declare + 'go-live' before the customer experiences value." diff --git a/.claude/industry-packs/healthtech/healthtech-diagnostic-rules.yaml b/.claude/industry-packs/healthtech/healthtech-diagnostic-rules.yaml index e87e868..fac8ca9 100644 --- a/.claude/industry-packs/healthtech/healthtech-diagnostic-rules.yaml +++ b/.claude/industry-packs/healthtech/healthtech-diagnostic-rules.yaml @@ -42,58 +42,133 @@ diagnostic_rules: - diagnostic: "customer-churn-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Churn in healthtech has three distinct dimensions absent from other industries. Provider churn (health systems terminating contracts) is driven by adoption failure, clinical evidence gaps, or reimbursement changes — not product satisfaction in the SaaS sense. Patient churn (patients disengaging) has clinical consequences — a patient who stops using a DTx is not merely a lost user but a patient not receiving their prescribed intervention. Payer churn (payers discontinuing coverage) eliminates the revenue foundation for an entire patient population. Separating these three churn vectors is essential for accurate diagnosis." + adaptation_rationale: "Churn in healthtech has three distinct dimensions absent + from other industries. Provider churn (health systems terminating + contracts) is driven by adoption failure, clinical evidence gaps, or + reimbursement changes — not product satisfaction in the SaaS sense. + Patient churn (patients disengaging) has clinical consequences — a patient + who stops using a DTx is not merely a lost user but a patient not + receiving their prescribed intervention. Payer churn (payers discontinuing + coverage) eliminates the revenue foundation for an entire patient + population. Separating these three churn vectors is essential for accurate + diagnosis." additional_triage_questions: - - question: "Which stakeholder is churning — health system customers (contract non-renewal), patients (disengagement from the clinical intervention), or payers (coverage termination)?" - purpose: "Each churn type has fundamentally different root causes and solutions. Health system churn signals adoption or evidence failure. Patient churn signals engagement or clinical relevance failure. Payer churn signals reimbursement or evidence failure." - routing_impact: "Health system churn routes to provider-adoption-rate analysis and clinical-workflow-integration assessment. Patient churn routes to patient-engagement-rate analysis and clinical protocol review. Payer churn routes to clinical-evidence-strength assessment and reimbursement strategy review." - - question: "Is provider adoption within the health system customer above 50%, or are contracted providers not using the product?" - purpose: "Health systems may terminate contracts not because the product is inadequate but because their providers did not adopt it — an implementation failure, not a product failure. Low adoption within contracted systems is the most common and most fixable healthtech churn driver." - routing_impact: "Low adoption (<50%) routes to implementation process review, provider training assessment, and clinical workflow integration analysis. High adoption with churn routes to clinical evidence review and competitive analysis." - - question: "Did the churn coincide with a change in reimbursement policy, clinical guidelines, or the departure of the clinical champion at the health system?" - purpose: "Healthtech churn is frequently triggered by external events — a payer discontinuing coverage eliminates the revenue justification, updated clinical guidelines that favor a different approach reduce the evidence argument, and the departure of the physician champion removes the internal advocate." - routing_impact: "Reimbursement-driven churn routes to payer strategy review and alternative revenue model exploration. Guideline-driven churn routes to clinical evidence strategy reassessment. Champion-departure churn routes to relationship diversification and implementation depth analysis." + - question: "Which stakeholder is churning — health system customers (contract + non-renewal), patients (disengagement from the clinical intervention), + or payers (coverage termination)?" + purpose: "Each churn type has fundamentally different root causes and solutions. + Health system churn signals adoption or evidence failure. Patient + churn signals engagement or clinical relevance failure. Payer churn + signals reimbursement or evidence failure." + routing_impact: "Health system churn routes to provider-adoption-rate analysis + and clinical-workflow-integration assessment. Patient churn routes to + patient-engagement-rate analysis and clinical protocol review. Payer + churn routes to clinical-evidence-strength assessment and + reimbursement strategy review." + - question: "Is provider adoption within the health system customer above 50%, or + are contracted providers not using the product?" + purpose: "Health systems may terminate contracts not because the product is + inadequate but because their providers did not adopt it — an + implementation failure, not a product failure. Low adoption within + contracted systems is the most common and most fixable healthtech + churn driver." + routing_impact: "Low adoption (<50%) routes to implementation process review, + provider training assessment, and clinical workflow integration + analysis. High adoption with churn routes to clinical evidence review + and competitive analysis." + - question: "Did the churn coincide with a change in reimbursement policy, + clinical guidelines, or the departure of the clinical champion at the + health system?" + purpose: "Healthtech churn is frequently triggered by external events — a payer + discontinuing coverage eliminates the revenue justification, updated + clinical guidelines that favor a different approach reduce the + evidence argument, and the departure of the physician champion removes + the internal advocate." + routing_impact: "Reimbursement-driven churn routes to payer strategy review and + alternative revenue model exploration. Guideline-driven churn routes + to clinical evidence strategy reassessment. Champion-departure churn + routes to relationship diversification and implementation depth + analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Provider adoption failure driving health system churn" - reason: "The most common healthtech churn pattern: the health system buys the product, but providers do not use it. Low adoption leads to low outcomes, which leads to non-renewal. The product may be excellent — but if providers do not adopt it, the clinical value is never delivered." + reason: "The most common healthtech churn pattern: the health system buys the + product, but providers do not use it. Low adoption leads to low + outcomes, which leads to non-renewal. The product may be excellent — + but if providers do not adopt it, the clinical value is never + delivered." - diagnosis: "Reimbursement loss undermining the business case for continued use" - reason: "When payers reduce or eliminate coverage for the product's clinical use case, health systems lose the financial justification for the contract. The product's clinical value is unchanged, but the economic model collapses." + reason: "When payers reduce or eliminate coverage for the product's clinical use + case, health systems lose the financial justification for the + contract. The product's clinical value is unchanged, but the + economic model collapses." less_likely: - diagnosis: "Product feature inadequacy" - reason: "Healthtech churn is rarely driven by missing features. It is driven by workflow disruption, insufficient evidence, reimbursement failure, or adoption barriers. Feature gap is the most over-diagnosed and least accurate churn driver in healthtech." + reason: "Healthtech churn is rarely driven by missing features. It is driven by + workflow disruption, insufficient evidence, reimbursement failure, + or adoption barriers. Feature gap is the most over-diagnosed and + least accurate churn driver in healthtech." healthtech_specific_diagnoses: - name: "Clinical validation gap driving payer and provider rejection" - description: "The product lacks sufficient clinical evidence to satisfy health system clinical review committees and payer coverage criteria. Sales stall at the evidence question, and existing customers do not renew because they cannot demonstrate clinical value to their internal stakeholders. The product may be effective, but without published evidence, effectiveness cannot be verified." + description: "The product lacks sufficient clinical evidence to satisfy health + system clinical review committees and payer coverage criteria. Sales + stall at the evidence question, and existing customers do not renew + because they cannot demonstrate clinical value to their internal + stakeholders. The product may be effective, but without published + evidence, effectiveness cannot be verified." symptoms: - - "Health system clinical review committees requesting evidence that does not exist" + - "Health system clinical review committees requesting evidence that + does not exist" - "Payers declining coverage citing insufficient evidence" - - "Existing customers unable to justify renewal to their clinical and administrative leadership" - - "Competitors with published studies winning head-to-head evaluations despite inferior product" - routes_to_skills: ["trust-equation", "balanced-scorecard", "scenario-planning"] - routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + - "Existing customers unable to justify renewal to their clinical and + administrative leadership" + - "Competitors with published studies winning head-to-head evaluations + despite inferior product" + routes_to_skills: [ "trust-equation", "balanced-scorecard", "scenario-planning" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] - name: "Provider adoption resistance causing implementation failure" - description: "The product has been deployed at health systems, but providers are not using it. The product adds steps to clinical workflow, generates excessive alerts, requires a separate login, or simply does not fit the way clinicians work. The health system sees low utilization data and declines to renew." + description: "The product has been deployed at health systems, but providers are + not using it. The product adds steps to clinical workflow, generates + excessive alerts, requires a separate login, or simply does not fit + the way clinicians work. The health system sees low utilization data + and declines to renew." symptoms: - "Provider adoption rate below 30% at deployed health systems" - - "Health system CIO or CMIO citing 'low utilization' as reason for non-renewal" - - "Provider feedback referencing 'extra clicks,' 'alert fatigue,' or 'workflow disruption'" - - "Support tickets dominated by workflow and integration issues rather than product defects" - routes_to_skills: ["kotter-change-model", "systems-thinking", "net-promoter-score"] - routes_to_templates: ["action-plan", "incident-postmortem"] + - "Health system CIO or CMIO citing 'low utilization' as reason for + non-renewal" + - "Provider feedback referencing 'extra clicks,' 'alert fatigue,' or + 'workflow disruption'" + - "Support tickets dominated by workflow and integration issues rather + than product defects" + routes_to_skills: [ "kotter-change-model", "systems-thinking", "net-promoter-score" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] - name: "Patient engagement collapse undermining clinical outcomes" - description: "Patients enroll in the product but disengage within weeks. For patient-facing healthtech (DTx, RPM, chronic disease management), patient disengagement means the clinical intervention is not being delivered. Without sustained engagement, outcomes cannot improve, and the clinical value proposition collapses." + description: "Patients enroll in the product but disengage within weeks. For + patient-facing healthtech (DTx, RPM, chronic disease management), + patient disengagement means the clinical intervention is not being + delivered. Without sustained engagement, outcomes cannot improve, and + the clinical value proposition collapses." symptoms: - - "Patient engagement rate declining below 25% by week 4 post-enrollment" - - "Clinical outcome metrics showing no improvement because patients are not receiving the intervention" - - "Provider and payer questioning the product's clinical effectiveness based on real-world engagement data" - - "Published clinical trial engagement rates significantly higher than real-world deployment engagement" - routes_to_skills: ["product-life-cycle", "net-promoter-score", "emotional-intelligence"] - routes_to_templates: ["action-plan", "quarterly-business-review"] + - "Patient engagement rate declining below 25% by week 4 + post-enrollment" + - "Clinical outcome metrics showing no improvement because patients + are not receiving the intervention" + - "Provider and payer questioning the product's clinical effectiveness + based on real-world engagement data" + - "Published clinical trial engagement rates significantly higher than + real-world deployment engagement" + routes_to_skills: [ "product-life-cycle", "net-promoter-score", "emotional-intelligence" ] + routes_to_templates: [ "action-plan", "quarterly-business-review" ] sector_red_flags: - - "Health system contract non-renewal when provider adoption was below 40% — signals an implementation problem, not a product problem, but the commercial outcome is identical." - - "Payer coverage termination affecting multiple health system customers simultaneously — a systemic reimbursement risk that can collapse revenue rapidly." - - "Patient disengagement rate exceeding the rate observed in clinical trials — signals that real-world conditions do not replicate trial conditions, undermining the evidence base." + - "Health system contract non-renewal when provider adoption was below 40% + — signals an implementation problem, not a product problem, but the + commercial outcome is identical." + - "Payer coverage termination affecting multiple health system customers + simultaneously — a systemic reimbursement risk that can collapse revenue + rapidly." + - "Patient disengagement rate exceeding the rate observed in clinical + trials — signals that real-world conditions do not replicate trial + conditions, undermining the evidence base." # ───────────────────────────────────────────── # 2. GROWTH STALL DIAGNOSIS @@ -101,60 +176,135 @@ diagnostic_rules: - diagnostic: "growth-stall-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Healthtech growth stalls have structural causes absent from other industries. Growth can stall because of regulatory bottlenecks (waiting for FDA clearance to market the product), clinical validation delays (study takes longer than projected), health system sales cycle length (12-18 month cycles create lumpy, unpredictable growth), provider change resistance (clinicians adopt slowly regardless of product quality), or reimbursement gaps (product cleared but not covered). The growth stall diagnostic must separate market-driven stalls from regulation-driven stalls, evidence-driven stalls, and reimbursement-driven stalls." + adaptation_rationale: "Healthtech growth stalls have structural causes absent + from other industries. Growth can stall because of regulatory bottlenecks + (waiting for FDA clearance to market the product), clinical validation + delays (study takes longer than projected), health system sales cycle + length (12-18 month cycles create lumpy, unpredictable growth), provider + change resistance (clinicians adopt slowly regardless of product quality), + or reimbursement gaps (product cleared but not covered). The growth stall + diagnostic must separate market-driven stalls from regulation-driven + stalls, evidence-driven stalls, and reimbursement-driven stalls." additional_triage_questions: - - question: "Is the growth stall occurring pre-regulatory clearance (cannot market the product), post-clearance but pre-reimbursement (can market but health systems cannot bill for it), or post-reimbursement (can market and bill but customers are not buying)?" - purpose: "Each phase has a fundamentally different growth constraint. Pre-clearance stalls are regulatory problems. Pre-reimbursement stalls are payer strategy problems. Post-reimbursement stalls are commercial execution problems." - routing_impact: "Pre-clearance routes to regulatory pathway assessment and scenario-planning for timeline extension. Pre-reimbursement routes to payer strategy and alternative revenue model development. Post-reimbursement routes to standard commercial growth diagnosis." - - question: "How many health system customers are in active sales pipeline, and what is the median time-in-stage for each pipeline phase?" - purpose: "Healthtech pipeline is notoriously long. A growth stall may reflect pipeline maturation (deals progressing slowly through clinical evaluation, IT review, and legal) rather than pipeline weakness (insufficient inbound demand). The distinction determines the response." - routing_impact: "Long time-in-stage routes to sales process optimization and health system procurement cycle alignment. Weak pipeline routes to clinical evidence marketing and demand generation strategy." - - question: "Is the growth stall concentrated in health systems that have not seen your clinical evidence, or in health systems that have evaluated and declined?" - purpose: "Awareness-driven stalls (health systems do not know about the product) are marketing problems. Evaluation-driven stalls (health systems evaluated and said no) are evidence, pricing, or workflow problems." - routing_impact: "Awareness-driven routes to clinical conference strategy, KOL engagement, and medical affairs investment. Evaluation-driven routes to root cause analysis of declines — evidence gap, pricing gap, or workflow integration gap." + - question: "Is the growth stall occurring pre-regulatory clearance (cannot market + the product), post-clearance but pre-reimbursement (can market but + health systems cannot bill for it), or post-reimbursement (can market + and bill but customers are not buying)?" + purpose: "Each phase has a fundamentally different growth constraint. + Pre-clearance stalls are regulatory problems. Pre-reimbursement stalls + are payer strategy problems. Post-reimbursement stalls are commercial + execution problems." + routing_impact: "Pre-clearance routes to regulatory pathway assessment and + scenario-planning for timeline extension. Pre-reimbursement routes to + payer strategy and alternative revenue model development. + Post-reimbursement routes to standard commercial growth diagnosis." + - question: "How many health system customers are in active sales pipeline, and + what is the median time-in-stage for each pipeline phase?" + purpose: "Healthtech pipeline is notoriously long. A growth stall may reflect + pipeline maturation (deals progressing slowly through clinical + evaluation, IT review, and legal) rather than pipeline weakness + (insufficient inbound demand). The distinction determines the + response." + routing_impact: "Long time-in-stage routes to sales process optimization and + health system procurement cycle alignment. Weak pipeline routes to + clinical evidence marketing and demand generation strategy." + - question: "Is the growth stall concentrated in health systems that have not seen + your clinical evidence, or in health systems that have evaluated and + declined?" + purpose: "Awareness-driven stalls (health systems do not know about the product) + are marketing problems. Evaluation-driven stalls (health systems + evaluated and said no) are evidence, pricing, or workflow problems." + routing_impact: "Awareness-driven routes to clinical conference strategy, KOL + engagement, and medical affairs investment. Evaluation-driven routes + to root cause analysis of declines — evidence gap, pricing gap, or + workflow integration gap." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory bottleneck delaying market access" - reason: "FDA clearance delays are the most common healthtech growth stall cause. Companies that under-budgeted regulatory timeline find themselves unable to sell while burning cash." + reason: "FDA clearance delays are the most common healthtech growth stall cause. + Companies that under-budgeted regulatory timeline find themselves + unable to sell while burning cash." - diagnosis: "Clinical evidence insufficient for health system procurement" - reason: "Health system clinical review committees increasingly require published evidence before approving new technology. Companies without peer-reviewed publications face a wall in the sales process." + reason: "Health system clinical review committees increasingly require published + evidence before approving new technology. Companies without + peer-reviewed publications face a wall in the sales process." - diagnosis: "Sales cycle length creating cash flow gap" - reason: "12-18 month health system sales cycles mean that a company must fund 12-18 months of sales effort before the first dollar of revenue. Growth stalls often reflect pipeline maturation time, not market rejection." + reason: "12-18 month health system sales cycles mean that a company must fund + 12-18 months of sales effort before the first dollar of revenue. + Growth stalls often reflect pipeline maturation time, not market + rejection." less_likely: - diagnosis: "Product-market fit failure" - reason: "If clinical evidence shows outcome improvement and health systems are interested but the process is slow, the problem is structural (sales cycle, reimbursement) not fundamental (product-market fit)." + reason: "If clinical evidence shows outcome improvement and health systems are + interested but the process is slow, the problem is structural (sales + cycle, reimbursement) not fundamental (product-market fit)." healthtech_specific_diagnoses: - name: "Regulatory pathway failure stalling commercialization" - description: "The product requires FDA clearance but the regulatory process has stalled — either because FDA has requested additional data, the pre-submission meeting revealed a more complex pathway than expected, or the company's regulatory strategy was based on incorrect classification assumptions. Until clearance is obtained, the product cannot be marketed for clinical use." + description: "The product requires FDA clearance but the regulatory process has + stalled — either because FDA has requested additional data, the + pre-submission meeting revealed a more complex pathway than expected, + or the company's regulatory strategy was based on incorrect + classification assumptions. Until clearance is obtained, the product + cannot be marketed for clinical use." symptoms: - - "FDA requesting additional clinical data beyond what was planned and budgeted" - - "Regulatory pathway reclassification (e.g., from 510(k) to De Novo) extending timeline by 12+ months" + - "FDA requesting additional clinical data beyond what was planned and + budgeted" + - "Regulatory pathway reclassification (e.g., from 510(k) to De Novo) + extending timeline by 12+ months" - "Pre-submission meeting feedback more negative than expected" - "Regulatory timeline extending beyond the company's cash runway" - routes_to_skills: ["scenario-planning", "vuca-framework", "systems-thinking"] - routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + routes_to_skills: [ "scenario-planning", "vuca-framework", "systems-thinking" ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] - name: "Reimbursement denial blocking revenue scalability" - description: "The product has FDA clearance and health system interest, but payers are not covering the product's clinical use case. Without reimbursement, health systems must fund the product from operational budgets — a much smaller and more competitive funding source than payer reimbursement. Revenue growth is capped at what health systems will pay out-of-pocket." + description: "The product has FDA clearance and health system interest, but + payers are not covering the product's clinical use case. Without + reimbursement, health systems must fund the product from operational + budgets — a much smaller and more competitive funding source than + payer reimbursement. Revenue growth is capped at what health systems + will pay out-of-pocket." symptoms: - "Medicare coverage determination pending or denied" - - "Commercial payers declining coverage citing insufficient evidence or non-essential classification" - - "Health system customers requesting that the product generate reimbursable events through existing CPT codes" - - "Revenue growth plateauing at a level consistent with health system IT budget allocation rather than clinical service reimbursement" - routes_to_skills: ["pricing-diagnosis", "business-model-canvas", "competitive-negotiation"] - routes_to_templates: ["market-opportunity-summary", "decision-rationale-memo"] + - "Commercial payers declining coverage citing insufficient evidence + or non-essential classification" + - "Health system customers requesting that the product generate + reimbursable events through existing CPT codes" + - "Revenue growth plateauing at a level consistent with health system + IT budget allocation rather than clinical service reimbursement" + routes_to_skills: + - business-model-canvas + - competitive-negotiation + routes_to_templates: [ "market-opportunity-summary", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Provider change resistance limiting deployment expansion" - description: "The product is cleared, reimbursed, and contracted, but provider adoption within deployed health systems is low. Clinicians are resistant to changing established workflows, skeptical of the product's clinical value, or overwhelmed by the current technology burden. Growth stalls because land-and-expand within health systems fails." + description: "The product is cleared, reimbursed, and contracted, but provider + adoption within deployed health systems is low. Clinicians are + resistant to changing established workflows, skeptical of the + product's clinical value, or overwhelmed by the current technology + burden. Growth stalls because land-and-expand within health systems + fails." symptoms: - - "Provider adoption rate below 40% at deployed health systems despite available training" - - "Health system expansion from pilot to enterprise blocked by low pilot adoption metrics" - - "Provider feedback citing workflow disruption, alert fatigue, or insufficient clinical value" + - "Provider adoption rate below 40% at deployed health systems despite + available training" + - "Health system expansion from pilot to enterprise blocked by low + pilot adoption metrics" + - "Provider feedback citing workflow disruption, alert fatigue, or + insufficient clinical value" - "Clinical champions frustrated by peers' refusal to adopt" - routes_to_skills: ["kotter-change-model", "trust-equation", "leading-through-change"] - routes_to_templates: ["action-plan", "new-initiative-brief"] + routes_to_skills: [ "kotter-change-model", "trust-equation", "leading-through-change" ] + routes_to_templates: [ "action-plan", "new-initiative-brief" ] sector_red_flags: - - "Regulatory clearance delayed 6+ months beyond projected timeline — triggers cascade: delayed revenue, extended burn, potential need for bridge financing." - - "Pipeline consisting of fewer than 10 qualified health system opportunities — healthtech requires a larger pipeline than the close rate suggests because health system evaluations are long and unpredictable." - - "Zero payer coverage obtained 12+ months after FDA clearance — signals that the clinical evidence does not meet payer standards or that the reimbursement strategy is flawed." + - "Regulatory clearance delayed 6+ months beyond projected timeline — + triggers cascade: delayed revenue, extended burn, potential need for + bridge financing." + - "Pipeline consisting of fewer than 10 qualified health system + opportunities — healthtech requires a larger pipeline than the close + rate suggests because health system evaluations are long and + unpredictable." + - "Zero payer coverage obtained 12+ months after FDA clearance — signals + that the clinical evidence does not meet payer standards or that the + reimbursement strategy is flawed." # ───────────────────────────────────────────── # 3. PRODUCT-MARKET FIT DIAGNOSIS @@ -162,37 +312,77 @@ diagnostic_rules: - diagnostic: "product-market-fit-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Product-market fit in healthtech requires satisfying three markets simultaneously: patients (who benefit), providers (who use), and payers (who fund). A product can have patient-market fit (patients love it) without provider-market fit (providers will not prescribe it) or payer-market fit (payers will not cover it). True healthtech PMF exists when all three stakeholders validate the product — patients engage, providers adopt, and payers reimburse. Partial PMF is the most dangerous state: strong signal from one stakeholder masks the absence from another." + adaptation_rationale: "Product-market fit in healthtech requires satisfying + three markets simultaneously: patients (who benefit), providers (who use), + and payers (who fund). A product can have patient-market fit (patients + love it) without provider-market fit (providers will not prescribe it) or + payer-market fit (payers will not cover it). True healthtech PMF exists + when all three stakeholders validate the product — patients engage, + providers adopt, and payers reimburse. Partial PMF is the most dangerous + state: strong signal from one stakeholder masks the absence from another." additional_triage_questions: - - question: "Which stakeholder is validating the product and which is not — are patients engaged but providers not prescribing, or are providers interested but payers not covering?" - purpose: "Identifies which leg of the triple aim is failing. Patient-only validation (engagement without provider prescription) suggests a consumer product mislabeled as clinical. Provider-only validation (interest without patient engagement) suggests a workflow tool that patients do not use. Payer-only validation is impossible without evidence." - routing_impact: "Patient without provider routes to clinical evidence strengthening and provider engagement strategy. Provider without payer routes to reimbursement pathway analysis. Provider without patient routes to patient experience redesign." - - question: "Does the product's retention curve flatten — do patients and providers who stay past an initial period continue long-term — or does it continuously decline?" - purpose: "A flattening retention curve for both patients and providers is the strongest healthtech PMF signal. Continuous decline in either population indicates PMF has not been achieved." - routing_impact: "Flattening curves with low initial retention routes to onboarding optimization. Continuously declining curves route to fundamental value proposition reassessment." + - question: "Which stakeholder is validating the product and which is not — are + patients engaged but providers not prescribing, or are providers + interested but payers not covering?" + purpose: "Identifies which leg of the triple aim is failing. Patient-only + validation (engagement without provider prescription) suggests a + consumer product mislabeled as clinical. Provider-only validation + (interest without patient engagement) suggests a workflow tool that + patients do not use. Payer-only validation is impossible without + evidence." + routing_impact: "Patient without provider routes to clinical evidence + strengthening and provider engagement strategy. Provider without payer + routes to reimbursement pathway analysis. Provider without patient + routes to patient experience redesign." + - question: "Does the product's retention curve flatten — do patients and + providers who stay past an initial period continue long-term — or does + it continuously decline?" + purpose: "A flattening retention curve for both patients and providers is the + strongest healthtech PMF signal. Continuous decline in either + population indicates PMF has not been achieved." + routing_impact: "Flattening curves with low initial retention routes to + onboarding optimization. Continuously declining curves route to + fundamental value proposition reassessment." diagnosis_weight_shifts: more_likely: - diagnosis: "PMF for one stakeholder but not the triple aim" - reason: "Healthtech companies frequently achieve PMF with one stakeholder (usually patients or providers) while failing with another (usually payers). This partial PMF creates a business that generates enthusiasm but not sustainable revenue." + reason: "Healthtech companies frequently achieve PMF with one stakeholder + (usually patients or providers) while failing with another (usually + payers). This partial PMF creates a business that generates + enthusiasm but not sustainable revenue." - diagnosis: "Clinical evidence insufficient to validate PMF" - reason: "Unlike SaaS where retention data validates PMF, healthtech PMF requires clinical outcome data. A product that retains users but does not improve outcomes has consumer PMF but not clinical PMF." + reason: "Unlike SaaS where retention data validates PMF, healthtech PMF requires + clinical outcome data. A product that retains users but does not + improve outcomes has consumer PMF but not clinical PMF." less_likely: - diagnosis: "Product is fundamentally flawed" - reason: "If any clinical stakeholder validates the product, the technology likely works for someone. The question is usually not product quality but clinical-commercial alignment." + reason: "If any clinical stakeholder validates the product, the technology + likely works for someone. The question is usually not product + quality but clinical-commercial alignment." healthtech_specific_diagnoses: - name: "Triple-aim misalignment" - description: "The product satisfies one or two of the triple aim (better outcomes, better experience, lower cost) but fails on the third. Payers require all three. A product that improves outcomes but increases cost will not receive broad reimbursement. A product that reduces cost but worsens experience will not be adopted by patients or providers." + description: "The product satisfies one or two of the triple aim (better + outcomes, better experience, lower cost) but fails on the third. + Payers require all three. A product that improves outcomes but + increases cost will not receive broad reimbursement. A product that + reduces cost but worsens experience will not be adopted by patients or + providers." symptoms: - - "Strong clinical outcome data but payer rejection citing cost-effectiveness" + - "Strong clinical outcome data but payer rejection citing + cost-effectiveness" - "Strong patient engagement but providers reporting workflow burden" - "Strong provider adoption but patient outcome metrics not improving" - - "Health economic analysis showing that the product's cost exceeds the cost of the alternative it replaces" - routes_to_skills: ["business-model-canvas", "systems-thinking", "balanced-scorecard"] - routes_to_templates: ["strategic-analysis-one-pager", "unit-economics-snapshot"] + - "Health economic analysis showing that the product's cost exceeds + the cost of the alternative it replaces" + routes_to_skills: [ "business-model-canvas", "systems-thinking", "balanced-scorecard" ] + routes_to_templates: [ "strategic-analysis-one-pager", "unit-economics-snapshot" ] sector_red_flags: - - "Provider NPS above 40 but payer coverage denied — the product has clinical validation but not economic validation." - - "Patient engagement above 50% but clinical outcomes not improving — the product is engaging but not clinically effective." - - "Clinical outcomes improving but gross margin below 40% — the clinical model is too labor-intensive for scalable delivery." + - "Provider NPS above 40 but payer coverage denied — the product has + clinical validation but not economic validation." + - "Patient engagement above 50% but clinical outcomes not improving — the + product is engaging but not clinically effective." + - "Clinical outcomes improving but gross margin below 40% — the clinical + model is too labor-intensive for scalable delivery." # ───────────────────────────────────────────── # 4. PRICING DIAGNOSIS @@ -200,37 +390,91 @@ diagnostic_rules: - diagnostic: "pricing-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Pricing in healthtech is fundamentally reimbursement-constrained. The diagnostic must determine whether the pricing problem is: (1) reimbursement misalignment (product priced above what payers will cover), (2) billing code mismatch (product's clinical service does not map to existing CPT/HCPCS codes), (3) health system budget constraint (product requires operational budget because no reimbursement pathway exists), or (4) value-capture failure (product delivers value but captures too little of it through pricing). The standard pricing diagnosis framework (value-based pricing, competitive pricing, cost-plus) must be adapted because the 'price' in healthtech is often determined by CMS, not by the company." + adaptation_rationale: "Pricing in healthtech is fundamentally + reimbursement-constrained. The diagnostic must determine whether the + pricing problem is: (1) reimbursement misalignment (product priced above + what payers will cover), (2) billing code mismatch (product's clinical + service does not map to existing CPT/HCPCS codes), (3) health system + budget constraint (product requires operational budget because no + reimbursement pathway exists), or (4) value-capture failure (product + delivers value but captures too little of it through pricing). The + standard pricing diagnosis framework (value-based pricing, competitive + pricing, cost-plus) must be adapted because the 'price' in healthtech is + often determined by CMS, not by the company." additional_triage_questions: - - question: "Is the product's revenue dependent on payer reimbursement (billing CPT/HCPCS codes), health system SaaS subscription, employer direct contract, or patient self-pay?" - purpose: "Each revenue model has different pricing constraints. Reimbursement-dependent revenue is price-capped by CMS and commercial payer schedules. SaaS subscription is negotiated with health system IT budgets. Employer direct pay is negotiated with benefits purchasers. Self-pay is constrained by patient willingness to pay." - routing_impact: "Reimbursement-dependent routes to CPT code analysis and payer rate optimization. SaaS subscription routes to health system IT budget analysis and value demonstration. Employer direct routes to benefits ROI analysis. Self-pay routes to consumer pricing and willingness-to-pay research." - - question: "Have you identified the specific CPT or HCPCS codes that apply to your product's clinical service, and have you verified the reimbursement rates with the target payer population?" - purpose: "Many healthtech pricing problems originate in a fundamental disconnect between the product's clinical service and the billing code system. If no applicable code exists, or if the applicable code's reimbursement rate is below the product's cost to deliver, the pricing problem is structural." - routing_impact: "No applicable code routes to new code application strategy (CPT Category III or HCPCS application) and alternative revenue model development. Applicable code with low reimbursement routes to margin optimization and service delivery cost reduction." + - question: "Is the product's revenue dependent on payer reimbursement (billing + CPT/HCPCS codes), health system SaaS subscription, employer direct + contract, or patient self-pay?" + purpose: "Each revenue model has different pricing constraints. + Reimbursement-dependent revenue is price-capped by CMS and commercial + payer schedules. SaaS subscription is negotiated with health system IT + budgets. Employer direct pay is negotiated with benefits purchasers. + Self-pay is constrained by patient willingness to pay." + routing_impact: "Reimbursement-dependent routes to CPT code analysis and payer + rate optimization. SaaS subscription routes to health system IT budget + analysis and value demonstration. Employer direct routes to benefits + ROI analysis. Self-pay routes to consumer pricing and + willingness-to-pay research." + - question: "Have you identified the specific CPT or HCPCS codes that apply to + your product's clinical service, and have you verified the + reimbursement rates with the target payer population?" + purpose: "Many healthtech pricing problems originate in a fundamental disconnect + between the product's clinical service and the billing code system. If + no applicable code exists, or if the applicable code's reimbursement + rate is below the product's cost to deliver, the pricing problem is + structural." + routing_impact: "No applicable code routes to new code application strategy (CPT + Category III or HCPCS application) and alternative revenue model + development. Applicable code with low reimbursement routes to margin + optimization and service delivery cost reduction." diagnosis_weight_shifts: more_likely: - diagnosis: "Reimbursement rate below product cost to deliver" - reason: "The most common healthtech pricing problem: the product's clinical service maps to a CPT code that reimburses at a rate below the cost of delivery, including clinical support staff, technology, and overhead." + reason: "The most common healthtech pricing problem: the product's clinical + service maps to a CPT code that reimburses at a rate below the cost + of delivery, including clinical support staff, technology, and + overhead." - diagnosis: "No applicable billing code exists" - reason: "Many novel healthtech products deliver clinical services that do not map neatly to existing billing codes. Without a code, the product must rely on health system operational budgets — a much smaller and more competitive funding source." + reason: "Many novel healthtech products deliver clinical services that do not + map neatly to existing billing codes. Without a code, the product + must rely on health system operational budgets — a much smaller and + more competitive funding source." less_likely: - diagnosis: "Over-pricing relative to competition" - reason: "Healthtech pricing is typically constrained below market-clearing levels by reimbursement rates. Over-pricing relative to competition is less common than under-reimbursement relative to cost." + reason: "Healthtech pricing is typically constrained below market-clearing + levels by reimbursement rates. Over-pricing relative to competition + is less common than under-reimbursement relative to cost." healthtech_specific_diagnoses: - name: "Reimbursement code mismatch" - description: "The product's clinical service does not map to existing CPT or HCPCS codes, or maps to codes that reimburse at rates far below the product's cost of delivery. The company must either adapt its service model to match existing codes, pursue new code creation (a 2-4 year process), or find non-reimbursement revenue models." + description: "The product's clinical service does not map to existing CPT or + HCPCS codes, or maps to codes that reimburse at rates far below the + product's cost of delivery. The company must either adapt its service + model to match existing codes, pursue new code creation (a 2-4 year + process), or find non-reimbursement revenue models." symptoms: - - "Health system billing departments unable to identify applicable codes" - - "Reimbursement revenue per patient significantly below contracted SaaS price per patient" - - "Health systems requesting that the product be structured to generate billable events under existing codes" + - "Health system billing departments unable to identify applicable + codes" + - "Reimbursement revenue per patient significantly below contracted + SaaS price per patient" + - "Health systems requesting that the product be structured to + generate billable events under existing codes" - "CPT application submitted but timeline extends 2+ years" - routes_to_skills: ["business-model-canvas", "pricing-diagnosis", "scenario-planning"] - routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + routes_to_skills: + - business-model-canvas + - scenario-planning + routes_to_templates: [ "unit-economics-snapshot", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - - "Product priced above Medicare reimbursement rate for the applicable CPT code — health systems absorb the gap, creating adoption resistance." - - "Revenue model dependent entirely on patient self-pay for a clinical product — this limits addressable market to patients with disposable income and willingness to pay for healthcare out-of-pocket." - - "No reimbursement strategy articulated despite clinical product positioning — a signal that the company has not confronted the fundamental revenue question." + - "Product priced above Medicare reimbursement rate for the applicable CPT + code — health systems absorb the gap, creating adoption resistance." + - "Revenue model dependent entirely on patient self-pay for a clinical + product — this limits addressable market to patients with disposable + income and willingness to pay for healthcare out-of-pocket." + - "No reimbursement strategy articulated despite clinical product + positioning — a signal that the company has not confronted the + fundamental revenue question." # ───────────────────────────────────────────── # 5. FUNDRAISING DIAGNOSIS @@ -238,37 +482,72 @@ diagnostic_rules: - diagnostic: "fundraising-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech fundraising requires demonstrating clinical validation milestones alongside commercial traction. Health-focused investors (Rock Health portfolio companies, a16z Bio+Health, GV Health) apply clinical due diligence as rigorously as financial due diligence. The diagnostic must evaluate whether the company's regulatory pathway, clinical evidence, and reimbursement strategy are investor-ready." + adaptation_rationale: "Healthtech fundraising requires demonstrating clinical + validation milestones alongside commercial traction. Health-focused + investors (Rock Health portfolio companies, a16z Bio+Health, GV Health) + apply clinical due diligence as rigorously as financial due diligence. The + diagnostic must evaluate whether the company's regulatory pathway, + clinical evidence, and reimbursement strategy are investor-ready." additional_triage_questions: - - question: "What is your clinical validation stage — pilot data, observational study, RCT, peer-reviewed publication, or regulatory clearance?" - purpose: "Clinical validation stage is the single most important variable in healthtech fundraising readiness. Seed investors accept pilot data. Series A investors expect at least observational study results. Series B investors expect peer-reviewed publications or regulatory clearance." - routing_impact: "Below-threshold clinical evidence routes to clinical study design and execution planning before fundraising. At-threshold evidence routes to investor narrative development." - - question: "Can you articulate the regulatory pathway, timeline, and cost for your product?" - purpose: "Regulatory literacy is a gating criterion for healthtech fundraising. Investors evaluate whether the founder understands the FDA pathway, has budgeted appropriately, and has a realistic timeline." - routing_impact: "Unclear regulatory pathway routes to regulatory strategy development before fundraising. Clear pathway routes to regulatory milestone integration into pitch narrative." + - question: "What is your clinical validation stage — pilot data, observational + study, RCT, peer-reviewed publication, or regulatory clearance?" + purpose: "Clinical validation stage is the single most important variable in + healthtech fundraising readiness. Seed investors accept pilot data. + Series A investors expect at least observational study results. Series + B investors expect peer-reviewed publications or regulatory + clearance." + routing_impact: "Below-threshold clinical evidence routes to clinical study + design and execution planning before fundraising. At-threshold + evidence routes to investor narrative development." + - question: "Can you articulate the regulatory pathway, timeline, and cost for + your product?" + purpose: "Regulatory literacy is a gating criterion for healthtech fundraising. + Investors evaluate whether the founder understands the FDA pathway, + has budgeted appropriately, and has a realistic timeline." + routing_impact: "Unclear regulatory pathway routes to regulatory strategy + development before fundraising. Clear pathway routes to regulatory + milestone integration into pitch narrative." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical evidence gap reducing investor confidence" - reason: "The most common healthtech fundraising failure: the product shows promising metrics but lacks the clinical evidence that health-focused investors require. General tech investors may not notice this gap, but they cannot help with health system commercialization." + reason: "The most common healthtech fundraising failure: the product shows + promising metrics but lacks the clinical evidence that + health-focused investors require. General tech investors may not + notice this gap, but they cannot help with health system + commercialization." - diagnosis: "Regulatory risk perceived as too high" - reason: "Investors discount healthtech companies with uncertain regulatory pathways. A company that might need a De Novo versus a 510(k) carries significantly more risk than one with a clear predicate-based 510(k) strategy." + reason: "Investors discount healthtech companies with uncertain regulatory + pathways. A company that might need a De Novo versus a 510(k) + carries significantly more risk than one with a clear + predicate-based 510(k) strategy." less_likely: - diagnosis: "Market too small" - reason: "Healthcare markets are enormous. 'Market too small' in healthtech usually means the company has not articulated the reimbursement pathway that unlocks the addressable market." + reason: "Healthcare markets are enormous. 'Market too small' in healthtech + usually means the company has not articulated the reimbursement + pathway that unlocks the addressable market." healthtech_specific_diagnoses: - name: "Investor-clinical evidence mismatch" - description: "The company's clinical evidence stage does not match the expectations of the target investor tier. Presenting pilot data to Series B investors, or approaching general tech investors with a regulatory-heavy pitch, creates a fundamental mismatch." + description: "The company's clinical evidence stage does not match the + expectations of the target investor tier. Presenting pilot data to + Series B investors, or approaching general tech investors with a + regulatory-heavy pitch, creates a fundamental mismatch." symptoms: - - "Health-focused investors requesting clinical data that does not exist" - - "General tech investors unable to evaluate the clinical value proposition" - - "Investor feedback consistently referencing 'evidence' or 'regulatory risk' as concerns" + - "Health-focused investors requesting clinical data that does not + exist" + - "General tech investors unable to evaluate the clinical value + proposition" + - "Investor feedback consistently referencing 'evidence' or + 'regulatory risk' as concerns" - "Fundraising process extending beyond 6 months without term sheet" - routes_to_skills: ["story-structure-and-arc", "trust-equation", "scenario-planning"] - routes_to_templates: ["fundraising-deck-outline", "market-opportunity-summary"] + routes_to_skills: [ "story-structure-and-arc", "trust-equation", "scenario-planning" ] + routes_to_templates: [ "fundraising-deck-outline", "market-opportunity-summary" ] sector_red_flags: - - "Raising Series A without any published clinical study — health-focused investors will pass." - - "Raising with regulatory clearance timeline extending beyond 18 months — investors see 18+ months of pre-revenue burn." - - "No clinical advisory board — signals that the founder has not engaged the clinical community." + - "Raising Series A without any published clinical study — health-focused + investors will pass." + - "Raising with regulatory clearance timeline extending beyond 18 months — + investors see 18+ months of pre-revenue burn." + - "No clinical advisory board — signals that the founder has not engaged + the clinical community." # ───────────────────────────────────────────── # 6. REVENUE DIAGNOSIS @@ -276,37 +555,73 @@ diagnostic_rules: - diagnostic: "revenue-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Revenue in healthtech decomposes along three dimensions: revenue source (payer reimbursement, health system SaaS, employer direct, patient self-pay), revenue driver (number of patients x revenue per patient, or number of health systems x contract value), and revenue quality (reimbursement-backed revenue is more durable than operational budget allocations). The diagnostic must identify which dimension is underperforming." + adaptation_rationale: "Revenue in healthtech decomposes along three dimensions: + revenue source (payer reimbursement, health system SaaS, employer direct, + patient self-pay), revenue driver (number of patients x revenue per + patient, or number of health systems x contract value), and revenue + quality (reimbursement-backed revenue is more durable than operational + budget allocations). The diagnostic must identify which dimension is + underperforming." additional_triage_questions: - - question: "What percentage of revenue comes from payer reimbursement versus health system operational budgets versus other sources?" - purpose: "Revenue mix determines durability and scalability. Reimbursement-backed revenue scales with patient volume. Operational budget revenue is capped by IT spending limits. The mix determines the company's ceiling." - routing_impact: "Low reimbursement share routes to payer strategy and clinical evidence development. High reimbursement share with low revenue routes to patient volume and provider adoption analysis." - - question: "Is the revenue problem driven by too few customers (health systems), too few patients per customer, or too little revenue per patient?" - purpose: "Healthtech revenue is a three-variable equation. Identifying which variable is underperforming focuses the diagnostic." - routing_impact: "Too few customers routes to sales process and demand generation analysis. Too few patients per customer routes to provider adoption and implementation quality. Too little revenue per patient routes to reimbursement and pricing analysis." + - question: "What percentage of revenue comes from payer reimbursement versus + health system operational budgets versus other sources?" + purpose: "Revenue mix determines durability and scalability. + Reimbursement-backed revenue scales with patient volume. Operational + budget revenue is capped by IT spending limits. The mix determines the + company's ceiling." + routing_impact: "Low reimbursement share routes to payer strategy and clinical + evidence development. High reimbursement share with low revenue routes + to patient volume and provider adoption analysis." + - question: "Is the revenue problem driven by too few customers (health systems), + too few patients per customer, or too little revenue per patient?" + purpose: "Healthtech revenue is a three-variable equation. Identifying which + variable is underperforming focuses the diagnostic." + routing_impact: "Too few customers routes to sales process and demand generation + analysis. Too few patients per customer routes to provider adoption + and implementation quality. Too little revenue per patient routes to + reimbursement and pricing analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Reimbursement underperformance" - reason: "The most common healthtech revenue problem: the product generates clinical value but the reimbursement rate is too low, the coverage is too narrow, or the billing process is too complex for health system billing departments." + reason: "The most common healthtech revenue problem: the product generates + clinical value but the reimbursement rate is too low, the coverage + is too narrow, or the billing process is too complex for health + system billing departments." - diagnosis: "Low patient volume per health system customer" - reason: "Health system contracts often project patient volumes that are not realized because provider adoption is low, patient enrollment is slow, or the clinical use case is narrower than contracted." + reason: "Health system contracts often project patient volumes that are not + realized because provider adoption is low, patient enrollment is + slow, or the clinical use case is narrower than contracted." less_likely: - diagnosis: "Pricing too low" - reason: "Healthtech pricing is typically constrained by reimbursement rates. The revenue problem is usually not pricing but volume — either patient volume or health system customer volume." + reason: "Healthtech pricing is typically constrained by reimbursement rates. The + revenue problem is usually not pricing but volume — either patient + volume or health system customer volume." healthtech_specific_diagnoses: - name: "Revenue model-clinical model mismatch" - description: "The revenue model assumes one clinical delivery model, but the actual clinical delivery requires a different model. For example: the revenue model assumes per-patient SaaS pricing, but clinical effectiveness requires clinician-monitored RPM — the clinician cost is not captured in the revenue model, creating a structural margin problem." + description: "The revenue model assumes one clinical delivery model, but the + actual clinical delivery requires a different model. For example: the + revenue model assumes per-patient SaaS pricing, but clinical + effectiveness requires clinician-monitored RPM — the clinician cost is + not captured in the revenue model, creating a structural margin + problem." symptoms: - - "Gross margin declining as patient volume increases (clinical support costs scaling linearly while revenue scales sub-linearly)" + - "Gross margin declining as patient volume increases (clinical + support costs scaling linearly while revenue scales sub-linearly)" - "Clinical team headcount growing faster than patient enrollment" - - "Health system customers requesting clinical support that exceeds the contracted service level" - - "Clinical outcome metrics requiring higher-touch intervention than the technology alone provides" - routes_to_skills: ["business-model-canvas", "systems-thinking", "balanced-scorecard"] - routes_to_templates: ["unit-economics-snapshot", "quarterly-strategic-review"] + - "Health system customers requesting clinical support that exceeds + the contracted service level" + - "Clinical outcome metrics requiring higher-touch intervention than + the technology alone provides" + routes_to_skills: [ "business-model-canvas", "systems-thinking", "balanced-scorecard" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] sector_red_flags: - - "Revenue per patient declining as the company scales — signals that higher-acuity (higher-revenue) patients were served first and the marginal patient generates less revenue." - - "Health system contract renewals at lower ACV than initial contracts — signals value delivery concerns or competitive pressure on pricing." - - "More than 40% of contracted patient volume not realized — signals provider adoption or patient enrollment failure." + - "Revenue per patient declining as the company scales — signals that + higher-acuity (higher-revenue) patients were served first and the + marginal patient generates less revenue." + - "Health system contract renewals at lower ACV than initial contracts — + signals value delivery concerns or competitive pressure on pricing." + - "More than 40% of contracted patient volume not realized — signals + provider adoption or patient enrollment failure." # ───────────────────────────────────────────── # 7. COMPETITIVE THREAT DIAGNOSIS @@ -314,34 +629,73 @@ diagnostic_rules: - diagnostic: "competitive-threat-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech competitive threats come from four sources beyond traditional competitors: EHR vendors building native functionality (Epic and Oracle Health adding clinical decision support, remote monitoring, and AI features directly into their platforms), pharmaceutical companies funding digital companions (Pharma-sponsored DTx and patient engagement tools), academic medical centers developing and commercializing clinical tools, and large technology companies entering healthcare (Google Health, Amazon Health, Apple Health). Each threat type requires a different response." + adaptation_rationale: "Healthtech competitive threats come from four sources + beyond traditional competitors: EHR vendors building native functionality + (Epic and Oracle Health adding clinical decision support, remote + monitoring, and AI features directly into their platforms), pharmaceutical + companies funding digital companions (Pharma-sponsored DTx and patient + engagement tools), academic medical centers developing and commercializing + clinical tools, and large technology companies entering healthcare (Google + Health, Amazon Health, Apple Health). Each threat type requires a + different response." additional_triage_questions: - - question: "Is the competitive threat from a peer healthtech startup, an EHR vendor building native functionality, a pharma company sponsoring a competing digital intervention, or a big tech company entering healthcare?" - purpose: "Each threat source has different capabilities, motivations, and vulnerabilities. Peer startups compete on evidence and execution. EHR vendors compete on integration. Pharma competes on clinical reach and funding. Big tech competes on data and distribution." - routing_impact: "Peer startup routes to clinical evidence differentiation and first-mover advantage. EHR vendor routes to integration depth analysis and partnership strategy. Pharma routes to clinical evidence superiority and independence positioning. Big tech routes to clinical specialization and regulatory expertise as differentiators." + - question: "Is the competitive threat from a peer healthtech startup, an EHR + vendor building native functionality, a pharma company sponsoring a + competing digital intervention, or a big tech company entering + healthcare?" + purpose: "Each threat source has different capabilities, motivations, and + vulnerabilities. Peer startups compete on evidence and execution. EHR + vendors compete on integration. Pharma competes on clinical reach and + funding. Big tech competes on data and distribution." + routing_impact: "Peer startup routes to clinical evidence differentiation and + first-mover advantage. EHR vendor routes to integration depth analysis + and partnership strategy. Pharma routes to clinical evidence + superiority and independence positioning. Big tech routes to clinical + specialization and regulatory expertise as differentiators." diagnosis_weight_shifts: more_likely: - diagnosis: "EHR vendor platform encroachment" - reason: "Epic and Oracle Health are expanding clinical functionality within their platforms. A healthtech product that operates outside the EHR is vulnerable to a native equivalent that requires no additional integration, procurement, or training." + reason: "Epic and Oracle Health are expanding clinical functionality within + their platforms. A healthtech product that operates outside the EHR + is vulnerable to a native equivalent that requires no additional + integration, procurement, or training." - diagnosis: "Clinical evidence leapfrog" - reason: "A competitor publishing superior clinical evidence (larger study, higher-impact journal, better outcomes) can rapidly shift health system and payer preferences. Clinical evidence is the primary competitive weapon in healthtech." + reason: "A competitor publishing superior clinical evidence (larger study, + higher-impact journal, better outcomes) can rapidly shift health + system and payer preferences. Clinical evidence is the primary + competitive weapon in healthtech." less_likely: - diagnosis: "Price-based competitive displacement" - reason: "Health systems rarely switch clinical tools based on price alone. Clinical evidence, workflow integration, and provider satisfaction drive switching decisions." + reason: "Health systems rarely switch clinical tools based on price alone. + Clinical evidence, workflow integration, and provider satisfaction + drive switching decisions." healthtech_specific_diagnoses: - name: "Clinical workflow disruption from EHR-native alternative" - description: "The primary EHR vendor (Epic or Oracle Health) has released or announced native functionality that replicates the healthtech product's core capability. Because the native functionality is embedded in the clinical workflow, requires no additional integration, and is included in the existing EHR license, health systems default to the EHR-native option — even if it is clinically inferior." + description: "The primary EHR vendor (Epic or Oracle Health) has released or + announced native functionality that replicates the healthtech + product's core capability. Because the native functionality is + embedded in the clinical workflow, requires no additional integration, + and is included in the existing EHR license, health systems default to + the EHR-native option — even if it is clinically inferior." symptoms: - - "Health system prospects citing 'we will wait for Epic/Cerner to build it' in sales conversations" - - "Existing customers asking about migration to EHR-native alternatives" - - "EHR vendor announcing roadmap features that overlap with the product's core functionality" + - "Health system prospects citing 'we will wait for Epic/Cerner to + build it' in sales conversations" + - "Existing customers asking about migration to EHR-native + alternatives" + - "EHR vendor announcing roadmap features that overlap with the + product's core functionality" - "Pipeline deals pausing pending EHR vendor product evaluation" - routes_to_skills: ["porters-five-forces", "disruptive-innovation", "blue-ocean-strategy"] - routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + routes_to_skills: [ "porters-five-forces", "disruptive-innovation", "blue-ocean-strategy" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] sector_red_flags: - - "Epic or Oracle Health announcing a feature set that replicates the product's core capability — the most consequential competitive threat in healthtech." - - "A competitor publishing an RCT in NEJM or JAMA that demonstrates superior outcomes." - - "A pharmaceutical company launching a competing digital therapeutic with pharma-scale clinical trial funding and physician detailing distribution." + - "Epic or Oracle Health announcing a feature set that replicates the + product's core capability — the most consequential competitive threat in + healthtech." + - "A competitor publishing an RCT in NEJM or JAMA that demonstrates + superior outcomes." + - "A pharmaceutical company launching a competing digital therapeutic with + pharma-scale clinical trial funding and physician detailing + distribution." # ───────────────────────────────────────────── # 8. STRATEGIC DRIFT DIAGNOSIS @@ -349,34 +703,63 @@ diagnostic_rules: - diagnostic: "strategic-drift-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech strategic drift often manifests as expanding the clinical scope beyond the evidence base — pursuing additional indications, therapeutic areas, or clinical use cases before validating the first one. The long feedback loops in healthtech (12-24 months for clinical studies, 6-18 months for health system sales) make drift harder to detect and more damaging when discovered." + adaptation_rationale: "Healthtech strategic drift often manifests as expanding + the clinical scope beyond the evidence base — pursuing additional + indications, therapeutic areas, or clinical use cases before validating + the first one. The long feedback loops in healthtech (12-24 months for + clinical studies, 6-18 months for health system sales) make drift harder + to detect and more damaging when discovered." additional_triage_questions: - - question: "Is the product pursuing additional clinical indications or therapeutic areas beyond the one where clinical evidence has been established?" - purpose: "Healthtech companies are tempted to expand clinical scope before validating the first indication. Each new indication requires independent clinical evidence, potentially a new regulatory submission, and new payer coverage — each representing 12-36 months of additional investment." - routing_impact: "Premature clinical expansion routes to focus assessment and evidence-first strategy. Evidence-validated expansion routes to portfolio planning using growth-share-matrix." + - question: "Is the product pursuing additional clinical indications or + therapeutic areas beyond the one where clinical evidence has been + established?" + purpose: "Healthtech companies are tempted to expand clinical scope before + validating the first indication. Each new indication requires + independent clinical evidence, potentially a new regulatory + submission, and new payer coverage — each representing 12-36 months of + additional investment." + routing_impact: "Premature clinical expansion routes to focus assessment and + evidence-first strategy. Evidence-validated expansion routes to + portfolio planning using growth-share-matrix." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical scope creep ahead of evidence" - reason: "Health system customers request the product for additional clinical use cases. The company expands to satisfy customers but without the evidence base to support the expanded claims." + reason: "Health system customers request the product for additional clinical use + cases. The company expands to satisfy customers but without the + evidence base to support the expanded claims." - diagnosis: "Regulatory classification confusion" - reason: "As the product expands features and clinical scope, its regulatory classification may shift — a wellness product that adds diagnostic features may suddenly require FDA clearance." + reason: "As the product expands features and clinical scope, its regulatory + classification may shift — a wellness product that adds diagnostic + features may suddenly require FDA clearance." less_likely: - diagnosis: "Market-driven strategic shift" - reason: "Healthcare markets are large and stable. True market-driven strategic shifts are rare — most healthtech strategic drift is internal, driven by opportunity chasing rather than market forces." + reason: "Healthcare markets are large and stable. True market-driven strategic + shifts are rare — most healthtech strategic drift is internal, + driven by opportunity chasing rather than market forces." healthtech_specific_diagnoses: - name: "HIPAA breach response consuming strategic capacity" - description: "A data security incident involving protected health information has consumed executive attention, engineering resources, and legal budget. The company is in crisis response mode — regulatory notification, patient notification, OCR investigation preparation — and strategic initiatives have stalled." + description: "A data security incident involving protected health information + has consumed executive attention, engineering resources, and legal + budget. The company is in crisis response mode — regulatory + notification, patient notification, OCR investigation preparation — + and strategic initiatives have stalled." symptoms: - "PHI breach reported to HHS OCR" - - "Executive team spending >50% of time on breach response and investigation" + - "Executive team spending >50% of time on breach response and + investigation" - "Product development halted for security remediation" - - "Health system customers requesting security audit and considering contract termination" - routes_to_skills: ["black-swans", "vuca-framework", "systems-thinking"] - routes_to_templates: ["incident-postmortem", "risk-assessment-brief"] + - "Health system customers requesting security audit and considering + contract termination" + routes_to_skills: [ "black-swans", "vuca-framework", "systems-thinking" ] + routes_to_templates: [ "incident-postmortem", "risk-assessment-brief" ] sector_red_flags: - - "Product marketed for clinical use cases not supported by the clinical evidence base — creates regulatory and liability risk." - - "Three or more therapeutic areas being pursued simultaneously with clinical evidence in none." - - "Regulatory classification shifting due to feature additions — signals that product decisions are being made without regulatory impact assessment." + - "Product marketed for clinical use cases not supported by the clinical + evidence base — creates regulatory and liability risk." + - "Three or more therapeutic areas being pursued simultaneously with + clinical evidence in none." + - "Regulatory classification shifting due to feature additions — signals + that product decisions are being made without regulatory impact + assessment." # ───────────────────────────────────────────── # 9. TEAM DYSFUNCTION DIAGNOSIS @@ -384,32 +767,59 @@ diagnostic_rules: - diagnostic: "team-dysfunction-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech team dysfunction has a unique dimension: the tension between clinical and commercial teams. Clinical team members (CMO, clinical operations, medical affairs) prioritize patient safety, evidence rigor, and clinical protocol adherence. Commercial team members (CEO, sales, marketing) prioritize growth, revenue, and market expansion. When these priorities conflict — and they inevitably do — the resolution determines both the company's culture and its clinical integrity." + adaptation_rationale: "Healthtech team dysfunction has a unique dimension: the + tension between clinical and commercial teams. Clinical team members (CMO, + clinical operations, medical affairs) prioritize patient safety, evidence + rigor, and clinical protocol adherence. Commercial team members (CEO, + sales, marketing) prioritize growth, revenue, and market expansion. When + these priorities conflict — and they inevitably do — the resolution + determines both the company's culture and its clinical integrity." additional_triage_questions: - - question: "Is there a structural tension between the clinical team (CMO, medical affairs) and the commercial team (CEO, sales) regarding product direction, evidence requirements, or marketing claims?" - purpose: "Clinical-commercial tension is the healthtech-specific variant of the SaaS product-sales tension, but with higher stakes. When commercial pressure overrides clinical judgment, the consequences include regulatory risk, patient safety risk, and reputational damage." - routing_impact: "Clinical-commercial misalignment routes to governance structure assessment and clinical-commercial decision framework development." + - question: "Is there a structural tension between the clinical team (CMO, medical + affairs) and the commercial team (CEO, sales) regarding product + direction, evidence requirements, or marketing claims?" + purpose: "Clinical-commercial tension is the healthtech-specific variant of the + SaaS product-sales tension, but with higher stakes. When commercial + pressure overrides clinical judgment, the consequences include + regulatory risk, patient safety risk, and reputational damage." + routing_impact: "Clinical-commercial misalignment routes to governance structure + assessment and clinical-commercial decision framework development." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical-commercial team misalignment" - reason: "The most common and most consequential healthtech team dysfunction. When the CMO and CEO disagree on whether the clinical evidence is sufficient to support a marketing claim, the resolution — and the process for reaching it — defines the company." + reason: "The most common and most consequential healthtech team dysfunction. + When the CMO and CEO disagree on whether the clinical evidence is + sufficient to support a marketing claim, the resolution — and the + process for reaching it — defines the company." less_likely: - diagnosis: "Individual performance issues" - reason: "Healthtech team members tend to be highly motivated by the mission. Performance issues are more often structural (unclear decision authority between clinical and commercial) than individual." + reason: "Healthtech team members tend to be highly motivated by the mission. + Performance issues are more often structural (unclear decision + authority between clinical and commercial) than individual." healthtech_specific_diagnoses: - name: "Clinical leadership void" - description: "The company lacks a credible clinical leader (CMO, VP Clinical) with the authority to make clinical decisions. Product, regulatory, and evidence decisions are made by non-clinical executives, leading to clinical missteps, provider distrust, and regulatory risk." + description: "The company lacks a credible clinical leader (CMO, VP Clinical) + with the authority to make clinical decisions. Product, regulatory, + and evidence decisions are made by non-clinical executives, leading to + clinical missteps, provider distrust, and regulatory risk." symptoms: - - "Clinical decisions made by product managers or engineers without clinical input" - - "No clinical advisory board or a board that meets fewer than twice per year" - - "Provider customers expressing concern about the company's clinical credibility" - - "Marketing materials making clinical claims not reviewed by a clinical professional" - routes_to_skills: ["hackman-enabling-conditions", "leadership-pipeline", "trust-equation"] - routes_to_templates: ["role-description-template", "hiring-scorecard"] + - "Clinical decisions made by product managers or engineers without + clinical input" + - "No clinical advisory board or a board that meets fewer than twice + per year" + - "Provider customers expressing concern about the company's clinical + credibility" + - "Marketing materials making clinical claims not reviewed by a + clinical professional" + routes_to_skills: [ "hackman-enabling-conditions", "leadership-pipeline", "trust-equation" ] + routes_to_templates: [ "role-description-template", "hiring-scorecard" ] sector_red_flags: - - "CMO resignation — signals irreconcilable conflict between clinical and commercial priorities." - - "Clinical advisory board members disengaging — signals that clinical advice is being ignored." - - "Marketing claims exceeding the clinical evidence base — signals that commercial pressure has overridden clinical governance." + - "CMO resignation — signals irreconcilable conflict between clinical and + commercial priorities." + - "Clinical advisory board members disengaging — signals that clinical + advice is being ignored." + - "Marketing claims exceeding the clinical evidence base — signals that + commercial pressure has overridden clinical governance." # ───────────────────────────────────────────── # 10. COFOUNDER CONFLICT DIAGNOSIS @@ -417,31 +827,61 @@ diagnostic_rules: - diagnostic: "cofounder-conflict-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech co-founder conflicts often center on the clinical-commercial divide — the physician co-founder prioritizes clinical rigor and patient safety while the technology co-founder prioritizes product development speed and market scaling. This tension is productive when managed well (it ensures both clinical quality and commercial viability) and destructive when it degenerates into mutual veto power." + adaptation_rationale: "Healthtech co-founder conflicts often center on the + clinical-commercial divide — the physician co-founder prioritizes clinical + rigor and patient safety while the technology co-founder prioritizes + product development speed and market scaling. This tension is productive + when managed well (it ensures both clinical quality and commercial + viability) and destructive when it degenerates into mutual veto power." additional_triage_questions: - - question: "Is the conflict centered on clinical evidence standards (how much evidence is enough before scaling), product direction (clinical depth vs. market breadth), or resource allocation (clinical R&D vs. commercial investment)?" - purpose: "Each conflict type has a different resolution path. Evidence disagreements require external benchmarking against health system and payer requirements. Product direction conflicts require customer input. Resource allocation requires financial modeling." - routing_impact: "Evidence standard conflicts route to health system and payer requirements analysis. Product direction routes to customer discovery and clinical advisory board input. Resource allocation routes to financial scenario planning." + - question: "Is the conflict centered on clinical evidence standards (how much + evidence is enough before scaling), product direction (clinical depth + vs. market breadth), or resource allocation (clinical R&D vs. + commercial investment)?" + purpose: "Each conflict type has a different resolution path. Evidence + disagreements require external benchmarking against health system and + payer requirements. Product direction conflicts require customer + input. Resource allocation requires financial modeling." + routing_impact: "Evidence standard conflicts route to health system and payer + requirements analysis. Product direction routes to customer discovery + and clinical advisory board input. Resource allocation routes to + financial scenario planning." diagnosis_weight_shifts: more_likely: - - diagnosis: "Clinical-commercial priority tension between physician and technology co-founders" - reason: "The most common healthtech co-founder conflict pattern. The physician founder sees every corner cut as a patient safety risk. The technology founder sees every clinical requirement as a commercial impediment." + - diagnosis: "Clinical-commercial priority tension between physician and + technology co-founders" + reason: "The most common healthtech co-founder conflict pattern. The physician + founder sees every corner cut as a patient safety risk. The + technology founder sees every clinical requirement as a commercial + impediment." less_likely: - diagnosis: "Equity and compensation disputes" - reason: "Healthtech co-founders are often mission-driven. Equity conflicts are less common than priority conflicts about how to pursue the mission." + reason: "Healthtech co-founders are often mission-driven. Equity conflicts are + less common than priority conflicts about how to pursue the + mission." healthtech_specific_diagnoses: - name: "Evidence-standard deadlock" - description: "The physician co-founder refuses to support commercialization until clinical evidence meets academic standards (multi-site RCT, peer-reviewed publication). The technology co-founder argues that waiting for this level of evidence consumes runway and allows competitors to establish market position. Both are partially right — and the deadlock prevents either path from being pursued." + description: "The physician co-founder refuses to support commercialization + until clinical evidence meets academic standards (multi-site RCT, + peer-reviewed publication). The technology co-founder argues that + waiting for this level of evidence consumes runway and allows + competitors to establish market position. Both are partially right — + and the deadlock prevents either path from being pursued." symptoms: - - "Product commercially available but CMO/physician co-founder declines to endorse marketing claims" + - "Product commercially available but CMO/physician co-founder + declines to endorse marketing claims" - "Commercial launch repeatedly delayed pending 'one more study'" - - "Technology co-founder pursuing sales conversations without clinical co-founder involvement" - - "Board unable to resolve the disagreement because both positions are defensible" - routes_to_skills: ["cooperative-negotiation", "evaluating-and-deciding", "scenario-planning"] - routes_to_templates: ["decision-journal", "quarterly-strategic-review"] + - "Technology co-founder pursuing sales conversations without clinical + co-founder involvement" + - "Board unable to resolve the disagreement because both positions are + defensible" + routes_to_skills: [ "cooperative-negotiation", "evaluating-and-deciding", "scenario-planning" ] + routes_to_templates: [ "decision-journal", "quarterly-strategic-review" ] sector_red_flags: - - "Physician co-founder publicly expressing concerns about the product's clinical readiness — damages credibility with health system customers." - - "Technology co-founder making clinical claims without physician co-founder endorsement — creates regulatory and liability exposure." + - "Physician co-founder publicly expressing concerns about the product's + clinical readiness — damages credibility with health system customers." + - "Technology co-founder making clinical claims without physician + co-founder endorsement — creates regulatory and liability exposure." # ───────────────────────────────────────────── # 11. MARKET ENTRY DIAGNOSIS @@ -449,30 +889,56 @@ diagnostic_rules: - diagnostic: "market-entry-diagnosis" sector_adaptation: "reframed" - adaptation_rationale: "Market entry in healthtech is not about digital distribution — it is about clinical validation, regulatory clearance, and reimbursement. The question is not 'can we enter this market?' but 'do we have the evidence, the regulatory status, and the reimbursement pathway to enter this market sustainably?' Healthtech market entry without these three foundations creates a business that can sell but cannot scale." + adaptation_rationale: "Market entry in healthtech is not about digital + distribution — it is about clinical validation, regulatory clearance, and + reimbursement. The question is not 'can we enter this market?' but 'do we + have the evidence, the regulatory status, and the reimbursement pathway to + enter this market sustainably?' Healthtech market entry without these + three foundations creates a business that can sell but cannot scale." additional_triage_questions: - - question: "Does the target clinical market have established reimbursement codes, or would entry require creating new reimbursement pathways?" - purpose: "Entering a market with established reimbursement is fundamentally different from entering one that requires new code creation. Established codes mean revenue is available upon launch. New codes require 2-4 years of CMS/AMA application process." - routing_impact: "Established reimbursement routes to competitive positioning and sales strategy. No reimbursement routes to alternative revenue model development and reimbursement pathway timeline planning." + - question: "Does the target clinical market have established reimbursement codes, + or would entry require creating new reimbursement pathways?" + purpose: "Entering a market with established reimbursement is fundamentally + different from entering one that requires new code creation. + Established codes mean revenue is available upon launch. New codes + require 2-4 years of CMS/AMA application process." + routing_impact: "Established reimbursement routes to competitive positioning and + sales strategy. No reimbursement routes to alternative revenue model + development and reimbursement pathway timeline planning." diagnosis_weight_shifts: more_likely: - diagnosis: "Market entry without reimbursement foundation" - reason: "The most common healthtech market entry failure: building and clearing a product for a clinical market where no reimbursement pathway exists. Revenue remains limited to health system operational budgets." + reason: "The most common healthtech market entry failure: building and clearing + a product for a clinical market where no reimbursement pathway + exists. Revenue remains limited to health system operational + budgets." less_likely: - diagnosis: "Market too small" - reason: "Clinical markets are large. 'Too small' usually means the company has not identified the patient population or reimbursement pathway that unlocks the addressable market." + reason: "Clinical markets are large. 'Too small' usually means the company has + not identified the patient population or reimbursement pathway that + unlocks the addressable market." healthtech_specific_diagnoses: - name: "Regulatory pathway mismatch for target market" - description: "The company's regulatory strategy is misaligned with the target clinical market's requirements. A product positioned for clinical diagnosis may require PMA (not 510(k)), a product marketed to patients directly may need different clearance than one marketed to providers, or the regulatory classification chosen limits the clinical claims that drive market entry." + description: "The company's regulatory strategy is misaligned with the target + clinical market's requirements. A product positioned for clinical + diagnosis may require PMA (not 510(k)), a product marketed to patients + directly may need different clearance than one marketed to providers, + or the regulatory classification chosen limits the clinical claims + that drive market entry." symptoms: - - "FDA pre-submission feedback indicating a more complex pathway than planned" - - "Clinical claims constrained by regulatory classification, limiting the addressable market" - - "Competitors with different regulatory classifications making broader clinical claims" - routes_to_skills: ["scenario-planning", "first-mover-strategy", "systems-thinking"] - routes_to_templates: ["market-opportunity-summary", "risk-assessment-brief"] + - "FDA pre-submission feedback indicating a more complex pathway than + planned" + - "Clinical claims constrained by regulatory classification, limiting + the addressable market" + - "Competitors with different regulatory classifications making + broader clinical claims" + routes_to_skills: [ "scenario-planning", "first-mover-strategy", "systems-thinking" ] + routes_to_templates: [ "market-opportunity-summary", "risk-assessment-brief" ] sector_red_flags: - - "Entering a clinical market without engaging a regulatory consultant or performing a regulatory pathway assessment." - - "Market entry plan that does not include a reimbursement strategy — will produce revenue ceiling surprises." + - "Entering a clinical market without engaging a regulatory consultant or + performing a regulatory pathway assessment." + - "Market entry plan that does not include a reimbursement strategy — will + produce revenue ceiling surprises." # ───────────────────────────────────────────── # 12. HIRING DIAGNOSIS @@ -480,31 +946,69 @@ diagnostic_rules: - diagnostic: "hiring-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech hiring requires specialized talent that spans the clinical-commercial divide: clinical informaticists, regulatory affairs specialists, health economics and outcomes researchers (HEOR), and clinical operations professionals. These roles do not exist in standard technology company hiring playbooks. The most critical and most commonly failed healthtech hire is the Chief Medical Officer — finding a physician who combines clinical credibility, strategic thinking, and startup operational capacity is rare and expensive." + adaptation_rationale: "Healthtech hiring requires specialized talent that spans + the clinical-commercial divide: clinical informaticists, regulatory + affairs specialists, health economics and outcomes researchers (HEOR), and + clinical operations professionals. These roles do not exist in standard + technology company hiring playbooks. The most critical and most commonly + failed healthtech hire is the Chief Medical Officer — finding a physician + who combines clinical credibility, strategic thinking, and startup + operational capacity is rare and expensive." additional_triage_questions: - - question: "Are you hiring clinical talent (CMO, clinical operations, medical affairs, HEOR) or commercial/technical talent, and do you have the domain expertise to evaluate clinical candidates?" - purpose: "Clinical hiring failures are the most expensive in healthtech. A CMO without startup operational capacity, a clinical operations hire without health system experience, or a HEOR professional without payer engagement experience can set the company back 12-18 months." - routing_impact: "Clinical hiring routes to clinical advisory board-led hiring process and specialized healthtech recruiting. Commercial/technical hiring routes to standard hiring processes with healthtech domain requirements." + - question: "Are you hiring clinical talent (CMO, clinical operations, medical + affairs, HEOR) or commercial/technical talent, and do you have the + domain expertise to evaluate clinical candidates?" + purpose: "Clinical hiring failures are the most expensive in healthtech. A CMO + without startup operational capacity, a clinical operations hire + without health system experience, or a HEOR professional without payer + engagement experience can set the company back 12-18 months." + routing_impact: "Clinical hiring routes to clinical advisory board-led hiring + process and specialized healthtech recruiting. Commercial/technical + hiring routes to standard hiring processes with healthtech domain + requirements." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical leadership hiring failure" - reason: "The most common and most consequential healthtech hiring mistake: hiring a CMO from academia who lacks commercial instincts, or a CMO from industry who lacks clinical credibility with the provider audience." + reason: "The most common and most consequential healthtech hiring mistake: + hiring a CMO from academia who lacks commercial instincts, or a CMO + from industry who lacks clinical credibility with the provider + audience." less_likely: - diagnosis: "Compensation competitiveness" - reason: "Clinical talent in healthtech is motivated by mission and clinical impact. Compensation matters but is rarely the primary barrier for CMO or clinical operations hires." + reason: "Clinical talent in healthtech is motivated by mission and clinical + impact. Compensation matters but is rarely the primary barrier for + CMO or clinical operations hires." healthtech_specific_diagnoses: - name: "Clinical-technical culture clash" - description: "Clinical hires (physicians, nurses, pharmacists) and technical hires (engineers, product managers) operate with fundamentally different work cultures. Clinical culture values thoroughness, evidence, protocol adherence, and patient safety. Technology culture values speed, iteration, experimentation, and shipping. Without deliberate cultural integration, the two groups develop mutual frustration that manifests as slow decisions, unresolved tensions, and talent attrition." + description: "Clinical hires (physicians, nurses, pharmacists) and technical + hires (engineers, product managers) operate with fundamentally + different work cultures. Clinical culture values thoroughness, + evidence, protocol adherence, and patient safety. Technology culture + values speed, iteration, experimentation, and shipping. Without + deliberate cultural integration, the two groups develop mutual + frustration that manifests as slow decisions, unresolved tensions, and + talent attrition." symptoms: - - "Clinical team describing engineering team as 'reckless' or 'careless with patient safety'" - - "Engineering team describing clinical team as 'blockers' or 'too slow'" - - "Product decisions oscillating between clinical and technical priorities without resolution framework" - - "Clinical or engineering talent leaving within first year, citing cultural misfit" - routes_to_skills: ["organisational-culture", "psychological-safety", "thomas-kilmann-conflict"] - routes_to_templates: ["culture-values-document", "team-health-check"] + - "Clinical team describing engineering team as 'reckless' or + 'careless with patient safety'" + - "Engineering team describing clinical team as 'blockers' or 'too + slow'" + - "Product decisions oscillating between clinical and technical + priorities without resolution framework" + - "Clinical or engineering talent leaving within first year, citing + cultural misfit" + routes_to_skills: + [ + "organisational-culture", + "psychological-safety", + "thomas-kilmann-conflict" + ] + routes_to_templates: [ "culture-values-document", "team-health-check" ] sector_red_flags: - - "No clinical leadership (CMO or equivalent) hired by Series A — signals that clinical governance is absent." - - "CMO or clinical leader attrition within 12 months — signals clinical-commercial cultural incompatibility." + - "No clinical leadership (CMO or equivalent) hired by Series A — signals + that clinical governance is absent." + - "CMO or clinical leader attrition within 12 months — signals + clinical-commercial cultural incompatibility." # ───────────────────────────────────────────── # 13. OPERATIONAL CHAOS DIAGNOSIS @@ -512,31 +1016,60 @@ diagnostic_rules: - diagnostic: "operational-chaos-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Operational chaos in healthtech has clinical safety implications absent from other industries. A deployment failure, data error, or system outage in a clinical product can affect patient care. HIPAA compliance adds operational requirements (security monitoring, access controls, audit logging, breach notification procedures) that do not exist in non-health industries. The operational chaos diagnostic must evaluate whether operational failures are creating patient safety risk." + adaptation_rationale: "Operational chaos in healthtech has clinical safety + implications absent from other industries. A deployment failure, data + error, or system outage in a clinical product can affect patient care. + HIPAA compliance adds operational requirements (security monitoring, + access controls, audit logging, breach notification procedures) that do + not exist in non-health industries. The operational chaos diagnostic must + evaluate whether operational failures are creating patient safety risk." additional_triage_questions: - - question: "Has any operational failure (system outage, data error, deployment issue) affected clinical operations or patient care at a health system customer?" - purpose: "Clinical operational failures are categorically different from standard SaaS outages. A clinical decision support tool that is unavailable during a clinical shift forces providers to fall back to pre-technology workflows — which may not be available or may be unfamiliar to newer staff." - routing_impact: "Clinical operational failures route to patient safety incident review and clinical risk assessment. Non-clinical operational failures route to standard DevOps improvement." + - question: "Has any operational failure (system outage, data error, deployment + issue) affected clinical operations or patient care at a health system + customer?" + purpose: "Clinical operational failures are categorically different from + standard SaaS outages. A clinical decision support tool that is + unavailable during a clinical shift forces providers to fall back to + pre-technology workflows — which may not be available or may be + unfamiliar to newer staff." + routing_impact: "Clinical operational failures route to patient safety incident + review and clinical risk assessment. Non-clinical operational failures + route to standard DevOps improvement." diagnosis_weight_shifts: more_likely: - diagnosis: "HIPAA compliance gaps creating operational burden" - reason: "Companies that did not build HIPAA compliance into their operational foundation from day one face escalating remediation costs as they scale — each new health system customer adds compliance requirements." + reason: "Companies that did not build HIPAA compliance into their operational + foundation from day one face escalating remediation costs as they + scale — each new health system customer adds compliance + requirements." less_likely: - diagnosis: "Over-process" - reason: "Healthtech companies rarely have too much process. Given the regulatory and safety requirements, the typical failure is under-process — insufficient quality assurance, incomplete documentation, and inadequate incident response procedures." + reason: "Healthtech companies rarely have too much process. Given the regulatory + and safety requirements, the typical failure is under-process — + insufficient quality assurance, incomplete documentation, and + inadequate incident response procedures." healthtech_specific_diagnoses: - name: "Clinical system availability failure" - description: "The product's uptime and reliability do not meet clinical availability standards. Health systems require near-100% availability for clinical tools because unavailability during clinical care creates patient safety risk. Standard SaaS uptime (99.5%) may be insufficient for clinical applications." + description: "The product's uptime and reliability do not meet clinical + availability standards. Health systems require near-100% availability + for clinical tools because unavailability during clinical care creates + patient safety risk. Standard SaaS uptime (99.5%) may be insufficient + for clinical applications." symptoms: - - "System outages during clinical hours generating patient safety concern reports" - - "Health system customers requiring SLA amendments with higher availability guarantees and financial penalties" - - "Clinical staff creating paper-based workarounds for system unavailability — indicating distrust of system reliability" + - "System outages during clinical hours generating patient safety + concern reports" + - "Health system customers requiring SLA amendments with higher + availability guarantees and financial penalties" + - "Clinical staff creating paper-based workarounds for system + unavailability — indicating distrust of system reliability" - "Incident rate exceeding health system vendor management thresholds" - routes_to_skills: ["systems-thinking", "kaizen-bpr", "balanced-scorecard"] - routes_to_templates: ["incident-postmortem", "action-plan"] + routes_to_skills: [ "systems-thinking", "kaizen-bpr", "balanced-scorecard" ] + routes_to_templates: [ "incident-postmortem", "action-plan" ] sector_red_flags: - - "Any system outage that affected active patient care — requires patient safety incident review and root cause analysis." - - "HIPAA security assessment identifying critical gaps — requires immediate remediation before additional health system deployments." + - "Any system outage that affected active patient care — requires patient + safety incident review and root cause analysis." + - "HIPAA security assessment identifying critical gaps — requires + immediate remediation before additional health system deployments." # ───────────────────────────────────────────── # 14. LEADERSHIP CRISIS DIAGNOSIS @@ -544,20 +1077,35 @@ diagnostic_rules: - diagnostic: "leadership-crisis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Leadership crises in healthtech carry additional dimensions: a CEO who loses the trust of the clinical advisory board, a CMO who resigns citing ethical concerns, or a leadership team that is perceived as prioritizing commercial interests over patient welfare can trigger cascading damage — health system customers re-evaluate contracts, clinical talent departs, and the company's clinical reputation suffers." + adaptation_rationale: "Leadership crises in healthtech carry additional + dimensions: a CEO who loses the trust of the clinical advisory board, a + CMO who resigns citing ethical concerns, or a leadership team that is + perceived as prioritizing commercial interests over patient welfare can + trigger cascading damage — health system customers re-evaluate contracts, + clinical talent departs, and the company's clinical reputation suffers." additional_triage_questions: - - question: "Has the leadership crisis affected the clinical advisory board's engagement, the CMO's confidence in the product's safety, or health system customers' trust in the company's clinical commitment?" - purpose: "Leadership crises in healthtech can cascade into clinical credibility crises. If the clinical advisory board disengages, the company loses its clinical governance infrastructure." - routing_impact: "Clinical credibility impact routes to clinical governance restoration and advisory board re-engagement. No clinical credibility impact routes to standard leadership crisis resolution." + - question: "Has the leadership crisis affected the clinical advisory board's + engagement, the CMO's confidence in the product's safety, or health + system customers' trust in the company's clinical commitment?" + purpose: "Leadership crises in healthtech can cascade into clinical credibility + crises. If the clinical advisory board disengages, the company loses + its clinical governance infrastructure." + routing_impact: "Clinical credibility impact routes to clinical governance + restoration and advisory board re-engagement. No clinical credibility + impact routes to standard leadership crisis resolution." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical leadership crisis" - reason: "The departure or disengagement of the CMO or clinical advisory board creates a credibility vacuum that is uniquely damaging in healthtech." + reason: "The departure or disengagement of the CMO or clinical advisory board + creates a credibility vacuum that is uniquely damaging in + healthtech." less_likely: [] healthtech_specific_diagnoses: [] sector_red_flags: - - "Clinical advisory board members resigning — signals that clinical governance has failed." - - "CMO expressing public concerns about patient safety — existential reputational risk." + - "Clinical advisory board members resigning — signals that clinical + governance has failed." + - "CMO expressing public concerns about patient safety — existential + reputational risk." # ───────────────────────────────────────────── # 15. DECISION PARALYSIS DIAGNOSIS @@ -565,22 +1113,41 @@ diagnostic_rules: - diagnostic: "decision-paralysis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech faces a legitimate tension between decision speed and clinical caution. Some decisions that would be 'just ship it' in SaaS require deliberation in healthtech because they affect patient care. The diagnostic must distinguish between appropriate clinical caution (deliberation that protects patients) and decision paralysis (inaction that delays value without protecting anyone)." + adaptation_rationale: "Healthtech faces a legitimate tension between decision + speed and clinical caution. Some decisions that would be 'just ship it' in + SaaS require deliberation in healthtech because they affect patient care. + The diagnostic must distinguish between appropriate clinical caution + (deliberation that protects patients) and decision paralysis (inaction + that delays value without protecting anyone)." additional_triage_questions: - - question: "Is the delayed decision one that could affect patient safety if made incorrectly, or is it a commercial or operational decision with no clinical implications?" - purpose: "Clinical decisions merit deliberation proportional to their patient safety impact. Commercial decisions should not be held to the same standard — the opportunity cost of delay is real." - routing_impact: "Clinical decisions route to risk-benefit analysis with clinical advisory input. Commercial decisions route to bias-toward-action with reversibility assessment." + - question: "Is the delayed decision one that could affect patient safety if made + incorrectly, or is it a commercial or operational decision with no + clinical implications?" + purpose: "Clinical decisions merit deliberation proportional to their patient + safety impact. Commercial decisions should not be held to the same + standard — the opportunity cost of delay is real." + routing_impact: "Clinical decisions route to risk-benefit analysis with clinical + advisory input. Commercial decisions route to bias-toward-action with + reversibility assessment." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical caution masquerading as decision paralysis" - reason: "In healthtech, some apparent paralysis is actually appropriate caution — the CMO delaying a product release pending additional safety review is exercising clinical judgment, not avoiding decisions." + reason: "In healthtech, some apparent paralysis is actually appropriate caution + — the CMO delaying a product release pending additional safety + review is exercising clinical judgment, not avoiding decisions." less_likely: - diagnosis: "Insufficient information" - reason: "Healthtech companies typically have more information than they can process — clinical data, regulatory guidance, payer feedback. The problem is usually synthesis, not data availability." + reason: "Healthtech companies typically have more information than they can + process — clinical data, regulatory guidance, payer feedback. The + problem is usually synthesis, not data availability." healthtech_specific_diagnoses: [] sector_red_flags: - - "Regulatory submission delayed more than 6 months beyond readiness due to internal disagreement — the opportunity cost of delay in regulatory timeline is severe." - - "Product decisions requiring consensus from clinical, regulatory, commercial, and technical teams simultaneously — a sign of unclear decision authority." + - "Regulatory submission delayed more than 6 months beyond readiness due + to internal disagreement — the opportunity cost of delay in regulatory + timeline is severe." + - "Product decisions requiring consensus from clinical, regulatory, + commercial, and technical teams simultaneously — a sign of unclear + decision authority." # ───────────────────────────────────────────── # 16. INNOVATION DROUGHT DIAGNOSIS @@ -588,31 +1155,59 @@ diagnostic_rules: - diagnostic: "innovation-drought-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Innovation in healthtech faces a unique constraint: regulatory requirements can slow the pace of product evolution. Changes to FDA-cleared products may require supplemental submissions. Clinical evidence requirements mean that new features with clinical claims must be validated before marketing. The diagnostic must distinguish between regulatory-constrained innovation (slow but appropriate) and organizational innovation failure (slow due to internal dysfunction)." + adaptation_rationale: "Innovation in healthtech faces a unique constraint: + regulatory requirements can slow the pace of product evolution. Changes to + FDA-cleared products may require supplemental submissions. Clinical + evidence requirements mean that new features with clinical claims must be + validated before marketing. The diagnostic must distinguish between + regulatory-constrained innovation (slow but appropriate) and + organizational innovation failure (slow due to internal dysfunction)." additional_triage_questions: - - question: "Is the innovation constraint regulatory (changes require FDA submissions or clinical validation) or organizational (the team is not generating or prioritizing innovative ideas)?" - purpose: "Regulatory innovation constraints are structural and cannot be 'solved' — they must be designed around. Organizational innovation constraints are addressable through process and culture changes." - routing_impact: "Regulatory constraint routes to predetermined change control planning and innovation within cleared indications. Organizational constraint routes to standard innovation cultivation approaches." + - question: "Is the innovation constraint regulatory (changes require FDA + submissions or clinical validation) or organizational (the team is not + generating or prioritizing innovative ideas)?" + purpose: "Regulatory innovation constraints are structural and cannot be + 'solved' — they must be designed around. Organizational innovation + constraints are addressable through process and culture changes." + routing_impact: "Regulatory constraint routes to predetermined change control + planning and innovation within cleared indications. Organizational + constraint routes to standard innovation cultivation approaches." diagnosis_weight_shifts: more_likely: - diagnosis: "Regulatory burden consuming innovation capacity" - reason: "Post-market surveillance, adverse event reporting, and regulatory submission preparation consume engineering and clinical resources that would otherwise fund innovation." + reason: "Post-market surveillance, adverse event reporting, and regulatory + submission preparation consume engineering and clinical resources + that would otherwise fund innovation." less_likely: - diagnosis: "Lack of creative talent" - reason: "Healthtech teams are typically highly qualified and intrinsically motivated by the mission. Innovation failure is more often structural than talent-driven." + reason: "Healthtech teams are typically highly qualified and intrinsically + motivated by the mission. Innovation failure is more often + structural than talent-driven." healthtech_specific_diagnoses: - name: "Clinical evidence treadmill" - description: "The company must continuously generate new clinical evidence to maintain and expand market position — but the evidence generation process consumes the R&D resources that would fund product innovation. The company is trapped in a cycle of proving what it has rather than building what comes next." + description: "The company must continuously generate new clinical evidence to + maintain and expand market position — but the evidence generation + process consumes the R&D resources that would fund product innovation. + The company is trapped in a cycle of proving what it has rather than + building what comes next." symptoms: - - "More than 50% of clinical R&D budget allocated to studies validating existing features rather than developing new capabilities" - - "Competitor product innovation outpacing the company despite inferior current evidence" - - "Clinical team overwhelmed by study management, data collection, and publication preparation" - - "No product roadmap items beyond evidence generation for current capabilities" - routes_to_skills: ["eisenhower-matrix", "balanced-scorecard", "growth-share-matrix"] - routes_to_templates: ["quarterly-strategic-review", "new-initiative-brief"] + - "More than 50% of clinical R&D budget allocated to studies + validating existing features rather than developing new + capabilities" + - "Competitor product innovation outpacing the company despite + inferior current evidence" + - "Clinical team overwhelmed by study management, data collection, and + publication preparation" + - "No product roadmap items beyond evidence generation for current + capabilities" + routes_to_skills: [ "eisenhower-matrix", "balanced-scorecard", "growth-share-matrix" ] + routes_to_templates: [ "quarterly-strategic-review", "new-initiative-brief" ] sector_red_flags: - - "No product capability additions in 12+ months despite active engineering team — resources consumed by maintenance, compliance, and evidence generation." - - "Competitors launching features that health system customers request — signals innovation gap." + - "No product capability additions in 12+ months despite active + engineering team — resources consumed by maintenance, compliance, and + evidence generation." + - "Competitors launching features that health system customers request — + signals innovation gap." # ───────────────────────────────────────────── # 17. PARTNERSHIP DIAGNOSIS @@ -620,32 +1215,70 @@ diagnostic_rules: - diagnostic: "partnership-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech partnerships are ecosystem-critical: EHR vendor partnerships determine market access, pharmaceutical company partnerships fund clinical studies and provide distribution, health system partnerships provide clinical validation sites, and payer partnerships enable reimbursement. Each partnership type has different power dynamics and risk profiles." + adaptation_rationale: "Healthtech partnerships are ecosystem-critical: EHR + vendor partnerships determine market access, pharmaceutical company + partnerships fund clinical studies and provide distribution, health system + partnerships provide clinical validation sites, and payer partnerships + enable reimbursement. Each partnership type has different power dynamics + and risk profiles." additional_triage_questions: - - question: "Is this a technology partnership (EHR integration), a clinical validation partnership (health system study site), a distribution partnership (pharma or health plan), or a data partnership (clinical data access)?" - purpose: "Each healthtech partnership type has unique dynamics. EHR partnerships are gatekeeper relationships. Health system partnerships are clinical credibility relationships. Pharma partnerships provide funding but may create independence concerns. Data partnerships raise HIPAA compliance requirements." - routing_impact: "EHR partnership routes to integration strategy and vendor relationship management. Health system partnership routes to clinical study design and mutual publication agreements. Pharma partnership routes to independence governance and conflict-of-interest management. Data partnership routes to HIPAA compliance and data use agreement structuring." + - question: "Is this a technology partnership (EHR integration), a clinical + validation partnership (health system study site), a distribution + partnership (pharma or health plan), or a data partnership (clinical + data access)?" + purpose: "Each healthtech partnership type has unique dynamics. EHR partnerships + are gatekeeper relationships. Health system partnerships are clinical + credibility relationships. Pharma partnerships provide funding but may + create independence concerns. Data partnerships raise HIPAA compliance + requirements." + routing_impact: "EHR partnership routes to integration strategy and vendor + relationship management. Health system partnership routes to clinical + study design and mutual publication agreements. Pharma partnership + routes to independence governance and conflict-of-interest management. + Data partnership routes to HIPAA compliance and data use agreement + structuring." diagnosis_weight_shifts: more_likely: - diagnosis: "EHR vendor dependency creating existential risk" - reason: "A healthtech company that depends on Epic or Oracle Health integration for market access is in a structurally dependent relationship. The EHR vendor can change integration policies, launch competing functionality, or deprioritize the integration partnership." + reason: "A healthtech company that depends on Epic or Oracle Health integration + for market access is in a structurally dependent relationship. The + EHR vendor can change integration policies, launch competing + functionality, or deprioritize the integration partnership." less_likely: - diagnosis: "Partnership value misalignment" - reason: "Healthcare partnerships tend to be well-aligned on patient outcomes, even when commercial interests diverge. The shared mission provides a foundation for partnership that other industries lack." + reason: "Healthcare partnerships tend to be well-aligned on patient outcomes, + even when commercial interests diverge. The shared mission provides + a foundation for partnership that other industries lack." healthtech_specific_diagnoses: - name: "Pharma partnership independence erosion" - description: "A pharmaceutical company partnership provides valuable funding, distribution, or clinical study support, but the partnership creates perceived or actual conflicts of interest. Health systems and providers may question whether the healthtech product serves patient interests or pharma commercial interests. The partnership that enables growth simultaneously undermines clinical credibility." + description: "A pharmaceutical company partnership provides valuable funding, + distribution, or clinical study support, but the partnership creates + perceived or actual conflicts of interest. Health systems and + providers may question whether the healthtech product serves patient + interests or pharma commercial interests. The partnership that enables + growth simultaneously undermines clinical credibility." symptoms: - - "Health system customers expressing concern about pharma influence on clinical recommendations" - - "Clinical advisory board members questioning independence from pharma partner" - - "Product roadmap influenced by pharma partner's commercial priorities rather than clinical evidence" + - "Health system customers expressing concern about pharma influence + on clinical recommendations" + - "Clinical advisory board members questioning independence from + pharma partner" + - "Product roadmap influenced by pharma partner's commercial + priorities rather than clinical evidence" - "Provider adoption declining after pharma partnership announcement" - routes_to_skills: ["trust-equation", "prisoners-dilemma-and-cooperation", "information-asymmetry"] - routes_to_templates: ["partnership-memo", "risk-assessment-brief"] + routes_to_skills: + [ + "trust-equation", + "prisoners-dilemma-and-cooperation", + "information-asymmetry" + ] + routes_to_templates: [ "partnership-memo", "risk-assessment-brief" ] sector_red_flags: - - "EHR vendor partnership agreement with exclusivity clauses that limit future strategic options." - - "Pharma partnership that influences clinical content or recommendations — destroys provider trust." - - "Health system research partnership with publication veto rights — undermines evidence credibility." + - "EHR vendor partnership agreement with exclusivity clauses that limit + future strategic options." + - "Pharma partnership that influences clinical content or recommendations + — destroys provider trust." + - "Health system research partnership with publication veto rights — + undermines evidence credibility." # ───────────────────────────────────────────── # 18. COMMUNICATION BREAKDOWN DIAGNOSIS @@ -653,20 +1286,38 @@ diagnostic_rules: - diagnostic: "communication-breakdown-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Communication breakdowns in healthtech have clinical safety implications. Miscommunication between clinical and engineering teams about product behavior can result in clinical tools that function differently from what clinicians expect. Miscommunication between the company and health system customers about product capabilities can lead to clinical decisions based on incorrect assumptions about the product's scope or accuracy." + adaptation_rationale: "Communication breakdowns in healthtech have clinical + safety implications. Miscommunication between clinical and engineering + teams about product behavior can result in clinical tools that function + differently from what clinicians expect. Miscommunication between the + company and health system customers about product capabilities can lead to + clinical decisions based on incorrect assumptions about the product's + scope or accuracy." additional_triage_questions: - - question: "Has a communication breakdown between the clinical team and the engineering team resulted in a product that behaves differently from what clinicians expect or what clinical documentation describes?" - purpose: "Clinical-engineering communication failures can create patient safety risk if the product's clinical behavior diverges from what providers have been trained to expect." - routing_impact: "Clinical-engineering communication gaps route to clinical requirements documentation improvement and cross-functional review processes. Non-clinical communication issues route to standard communication improvement." + - question: "Has a communication breakdown between the clinical team and the + engineering team resulted in a product that behaves differently from + what clinicians expect or what clinical documentation describes?" + purpose: "Clinical-engineering communication failures can create patient safety + risk if the product's clinical behavior diverges from what providers + have been trained to expect." + routing_impact: "Clinical-engineering communication gaps route to clinical + requirements documentation improvement and cross-functional review + processes. Non-clinical communication issues route to standard + communication improvement." diagnosis_weight_shifts: more_likely: - diagnosis: "Clinical-technical translation failure" - reason: "Clinical requirements expressed in medical terminology may be misinterpreted by engineering teams. Engineering constraints expressed in technical terminology may not convey clinical implications to the clinical team." + reason: "Clinical requirements expressed in medical terminology may be + misinterpreted by engineering teams. Engineering constraints + expressed in technical terminology may not convey clinical + implications to the clinical team." less_likely: [] healthtech_specific_diagnoses: [] sector_red_flags: - - "Product clinical documentation inconsistent with actual product behavior — a patient safety and regulatory risk." - - "Health system customers reporting product behavior that surprises clinical staff — indicates training or documentation failure." + - "Product clinical documentation inconsistent with actual product + behavior — a patient safety and regulatory risk." + - "Health system customers reporting product behavior that surprises + clinical staff — indicates training or documentation failure." # ───────────────────────────────────────────── # 19. NEGOTIATION STUCK DIAGNOSIS @@ -674,24 +1325,48 @@ diagnostic_rules: - diagnostic: "negotiation-stuck-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech negotiations get stuck in characteristic ways: health system procurement processes that require clinical evaluation committee approval (adding 3-6 months), IT security reviews that demand HITRUST or SOC 2 certification (adding 2-4 months if not already obtained), legal reviews requiring HIPAA-compliant BAA terms, and payer contract negotiations that require clinical evidence dossier review." + adaptation_rationale: "Healthtech negotiations get stuck in characteristic ways: + health system procurement processes that require clinical evaluation + committee approval (adding 3-6 months), IT security reviews that demand + HITRUST or SOC 2 certification (adding 2-4 months if not already + obtained), legal reviews requiring HIPAA-compliant BAA terms, and payer + contract negotiations that require clinical evidence dossier review." additional_triage_questions: - - question: "Is the negotiation stuck at clinical evaluation (clinical review committee), IT/security review (HIPAA, SOC 2, HITRUST assessment), legal review (BAA, data use agreement), or commercial terms (pricing, contract structure)?" - purpose: "Each health system procurement gate has different resolution strategies. Clinical committee stalls require evidence. IT stalls require certifications. Legal stalls require standardized agreements. Commercial stalls require pricing creativity." - routing_impact: "Clinical committee stall routes to evidence strengthening and clinical champion engagement. IT security stall routes to certification acceleration and pre-prepared security documentation. Legal stall routes to BAA template preparation. Commercial stall routes to pricing restructuring." + - question: "Is the negotiation stuck at clinical evaluation (clinical review + committee), IT/security review (HIPAA, SOC 2, HITRUST assessment), + legal review (BAA, data use agreement), or commercial terms (pricing, + contract structure)?" + purpose: "Each health system procurement gate has different resolution + strategies. Clinical committee stalls require evidence. IT stalls + require certifications. Legal stalls require standardized agreements. + Commercial stalls require pricing creativity." + routing_impact: "Clinical committee stall routes to evidence strengthening and + clinical champion engagement. IT security stall routes to + certification acceleration and pre-prepared security documentation. + Legal stall routes to BAA template preparation. Commercial stall + routes to pricing restructuring." diagnosis_weight_shifts: more_likely: - diagnosis: "IT security review blocking the deal" - reason: "Health system IT security reviews are increasingly rigorous. HITRUST CSF certification or SOC 2 Type II is becoming a prerequisite, not a nice-to-have. Companies without these certifications face 2-6 month deal delays." + reason: "Health system IT security reviews are increasingly rigorous. HITRUST + CSF certification or SOC 2 Type II is becoming a prerequisite, not a + nice-to-have. Companies without these certifications face 2-6 month + deal delays." - diagnosis: "Clinical evaluation committee requiring additional evidence" - reason: "Health system clinical review committees evaluate new technology with the same rigor they apply to clinical protocol changes. Insufficient evidence stalls the evaluation, sometimes indefinitely." + reason: "Health system clinical review committees evaluate new technology with + the same rigor they apply to clinical protocol changes. Insufficient + evidence stalls the evaluation, sometimes indefinitely." less_likely: - diagnosis: "Price disagreement" - reason: "Healthtech negotiations rarely stall on price alone — they stall on clinical evidence, security certification, or contractual terms. Price is usually the last and easiest issue to resolve." + reason: "Healthtech negotiations rarely stall on price alone — they stall on + clinical evidence, security certification, or contractual terms. + Price is usually the last and easiest issue to resolve." healthtech_specific_diagnoses: [] sector_red_flags: - - "Deals stalling 60+ days in IT security review — indicates the company needs HITRUST or SOC 2 certification to unblock the pipeline." - - "Clinical evaluation committee requesting a pilot study before contracting — adds 3-12 months to the sales cycle." + - "Deals stalling 60+ days in IT security review — indicates the company + needs HITRUST or SOC 2 certification to unblock the pipeline." + - "Clinical evaluation committee requesting a pilot study before + contracting — adds 3-12 months to the sales cycle." # ───────────────────────────────────────────── # 20. CULTURE EROSION DIAGNOSIS @@ -699,30 +1374,70 @@ diagnostic_rules: - diagnostic: "culture-erosion-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Healthtech culture erosion carries patient safety consequences. A culture that deprioritizes clinical rigor, tolerates shortcuts in evidence generation, or allows commercial pressure to override clinical judgment creates conditions where patient harm becomes more likely. The most dangerous form of healthtech culture erosion is the normalization of clinical corners being cut — each small compromise establishes a precedent for the next, until the cumulative effect creates serious clinical risk." + adaptation_rationale: "Healthtech culture erosion carries patient safety + consequences. A culture that deprioritizes clinical rigor, tolerates + shortcuts in evidence generation, or allows commercial pressure to + override clinical judgment creates conditions where patient harm becomes + more likely. The most dangerous form of healthtech culture erosion is the + normalization of clinical corners being cut — each small compromise + establishes a precedent for the next, until the cumulative effect creates + serious clinical risk." additional_triage_questions: - - question: "Has the company's culture shifted from 'patient outcomes first' to 'growth first' — and do clinical team members feel empowered to challenge decisions that they believe compromise patient safety?" - purpose: "The health of the patient-safety culture is the most consequential cultural metric in healthtech. When clinical team members feel unable to raise safety concerns, the company has lost its most important cultural asset." - routing_impact: "Patient-safety culture erosion routes to psychological-safety assessment and clinical governance restructuring. Non-safety culture issues route to standard culture improvement." + - question: "Has the company's culture shifted from 'patient outcomes first' to + 'growth first' — and do clinical team members feel empowered to + challenge decisions that they believe compromise patient safety?" + purpose: "The health of the patient-safety culture is the most consequential + cultural metric in healthtech. When clinical team members feel unable + to raise safety concerns, the company has lost its most important + cultural asset." + routing_impact: "Patient-safety culture erosion routes to psychological-safety + assessment and clinical governance restructuring. Non-safety culture + issues route to standard culture improvement." diagnosis_weight_shifts: more_likely: - diagnosis: "Commercial pressure eroding clinical culture" - reason: "As healthtech companies face growth pressure from investors and board members, the temptation to deprioritize clinical rigor in favor of commercial velocity increases. This erosion is gradual and often unrecognized until a clinical incident reveals the accumulated risk." + reason: "As healthtech companies face growth pressure from investors and board + members, the temptation to deprioritize clinical rigor in favor of + commercial velocity increases. This erosion is gradual and often + unrecognized until a clinical incident reveals the accumulated + risk." less_likely: - diagnosis: "Growth outpacing culture infrastructure" - reason: "Healthtech companies grow more slowly than consumer tech, providing more time to develop culture. When culture erodes, the cause is usually pressure, not pace." + reason: "Healthtech companies grow more slowly than consumer tech, providing + more time to develop culture. When culture erodes, the cause is + usually pressure, not pace." healthtech_specific_diagnoses: - name: "Clinical integrity erosion" - description: "The company's commitment to clinical rigor has eroded under commercial pressure. Evidence standards have been relaxed, marketing claims have crept beyond the evidence base, clinical advisory board input is being ignored, and the CMO or clinical leadership feels unable to enforce clinical standards. The company has not yet experienced a patient safety incident, but the conditions for one are developing." + description: "The company's commitment to clinical rigor has eroded under + commercial pressure. Evidence standards have been relaxed, marketing + claims have crept beyond the evidence base, clinical advisory board + input is being ignored, and the CMO or clinical leadership feels + unable to enforce clinical standards. The company has not yet + experienced a patient safety incident, but the conditions for one are + developing." symptoms: - - "Clinical team members expressing private concern about evidence standards but not raising them formally" - - "Marketing materials making claims that the clinical team would not endorse if asked directly" - - "Clinical advisory board meetings becoming shorter, less substantive, or less frequent" - - "Commercial milestones being celebrated while clinical milestones are treated as obstacles" - - "New hires describing the culture as 'a tech company that happens to be in health' rather than 'a health company that uses technology'" - routes_to_skills: ["psychological-safety", "purpose-driven-leadership", "organisational-culture"] - routes_to_templates: ["culture-values-document", "risk-assessment-brief"] + - "Clinical team members expressing private concern about evidence + standards but not raising them formally" + - "Marketing materials making claims that the clinical team would not + endorse if asked directly" + - "Clinical advisory board meetings becoming shorter, less + substantive, or less frequent" + - "Commercial milestones being celebrated while clinical milestones + are treated as obstacles" + - "New hires describing the culture as 'a tech company that happens to + be in health' rather than 'a health company that uses technology'" + routes_to_skills: + [ + "psychological-safety", + "purpose-driven-leadership", + "organisational-culture" + ] + routes_to_templates: [ "culture-values-document", "risk-assessment-brief" ] sector_red_flags: - - "Clinical team attrition above 20% annually — the most sensitive indicator of clinical culture erosion." - - "Clinical advisory board members declining to participate in marketing or sales activities — signals concern about clinical integrity." - - "Any instance of a clinical safety concern being overridden by commercial pressure without documented clinical review — this is the sentinel event that predicts future patient harm." + - "Clinical team attrition above 20% annually — the most sensitive + indicator of clinical culture erosion." + - "Clinical advisory board members declining to participate in marketing + or sales activities — signals concern about clinical integrity." + - "Any instance of a clinical safety concern being overridden by + commercial pressure without documented clinical review — this is the + sentinel event that predicts future patient harm." diff --git a/.claude/industry-packs/healthtech/healthtech-skill-overlays.yaml b/.claude/industry-packs/healthtech/healthtech-skill-overlays.yaml index 76aa620..5ed8341 100644 --- a/.claude/industry-packs/healthtech/healthtech-skill-overlays.yaml +++ b/.claude/industry-packs/healthtech/healthtech-skill-overlays.yaml @@ -50,199 +50,829 @@ skill_overlays: - skill: "porters-five-forces" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Porter's Five Forces in healthtech are dominated by a force the original model does not explicitly name: regulatory power. Buyer power is concentrated not in patients but in health system procurement committees and payer organizations — both operate with institutional purchasing processes that take 6-18 months. Threat of new entrants is suppressed by regulatory barriers (FDA clearance, HIPAA compliance, clinical evidence requirements) that cost $500K-$20M to cross. Supplier power concentrates in EHR vendors (Epic and Oracle Health control 60%+ of the hospital market), clinical data partners, and specialized clinical talent. Substitutes include not just competing digital products but the status quo of manual clinical processes — the most powerful 'competitor' in healthtech is 'do nothing differently.' Rivalry intensity is shaped by clinical evidence: the company with the strongest published outcomes data wins, regardless of product polish." + healthtech_context: "Porter's Five Forces in healthtech are dominated by a force + the original model does not explicitly name: regulatory power. Buyer power + is concentrated not in patients but in health system procurement + committees and payer organizations — both operate with institutional + purchasing processes that take 6-18 months. Threat of new entrants is + suppressed by regulatory barriers (FDA clearance, HIPAA compliance, + clinical evidence requirements) that cost $500K-$20M to cross. Supplier + power concentrates in EHR vendors (Epic and Oracle Health control 60%+ of + the hospital market), clinical data partners, and specialized clinical + talent. Substitutes include not just competing digital products but the + status quo of manual clinical processes — the most powerful 'competitor' + in healthtech is 'do nothing differently.' Rivalry intensity is shaped by + clinical evidence: the company with the strongest published outcomes data + wins, regardless of product polish." healthtech_anti_patterns: - - "Treating the patient as the buyer. In most healthtech business models, the buyer is the health system (who procures the technology), the payer (who reimburses for its use), or the employer (who contracts for employee health benefits). The patient is the beneficiary, not the purchaser. Misidentifying the buyer distorts every strategic decision." - - "Underestimating the power of EHR vendors as suppliers. Epic and Oracle Health (Cerner) are not neutral platforms — they are gatekeepers who control clinical workflow access. Their app marketplaces, integration policies, and strategic priorities determine which healthtech products can reach providers." - - "Ignoring 'do nothing' as the strongest substitute. Health systems adopt new technology slowly because the cost of change (workflow disruption, training, clinical risk) often exceeds the perceived benefit of adoption. The five forces analysis must quantify the switching cost from current workflows, not just from competing products." - healthtech_example: "A clinical decision support startup applies Porter's Five Forces and discovers that its apparent competitive advantage — superior AI accuracy — is irrelevant to the buying decision. Buyer power analysis reveals that health system procurement committees prioritize EHR integration depth and clinical evidence level over algorithmic performance. Supplier power analysis shows that Epic's integration policies effectively determine market access. The threat of substitutes reveals that 70% of target clinicians use a combination of UpToDate, peer consultation, and clinical experience as their 'decision support tool' — and they are satisfied with it. This analysis pivots the strategy from AI performance marketing to deep Epic integration, published clinical evidence, and workflow time-savings messaging." - benchmark_references: ["clinical-workflow-integration-score", "provider-adoption-rate", "sales-cycle-length"] + - "Treating the patient as the buyer. In most healthtech business models, + the buyer is the health system (who procures the technology), the payer + (who reimburses for its use), or the employer (who contracts for + employee health benefits). The patient is the beneficiary, not the + purchaser. Misidentifying the buyer distorts every strategic decision." + - "Underestimating the power of EHR vendors as suppliers. Epic and Oracle + Health (Cerner) are not neutral platforms — they are gatekeepers who + control clinical workflow access. Their app marketplaces, integration + policies, and strategic priorities determine which healthtech products + can reach providers." + - "Ignoring 'do nothing' as the strongest substitute. Health systems adopt + new technology slowly because the cost of change (workflow disruption, + training, clinical risk) often exceeds the perceived benefit of + adoption. The five forces analysis must quantify the switching cost from + current workflows, not just from competing products." + healthtech_example: "A clinical decision support startup applies Porter's Five + Forces and discovers that its apparent competitive advantage — superior AI + accuracy — is irrelevant to the buying decision. Buyer power analysis + reveals that health system procurement committees prioritize EHR + integration depth and clinical evidence level over algorithmic + performance. Supplier power analysis shows that Epic's integration + policies effectively determine market access. The threat of substitutes + reveals that 70% of target clinicians use a combination of UpToDate, peer + consultation, and clinical experience as their 'decision support tool' — + and they are satisfied with it. This analysis pivots the strategy from AI + performance marketing to deep Epic integration, published clinical + evidence, and workflow time-savings messaging." + benchmark_references: + [ + "clinical-workflow-integration-score", + "provider-adoption-rate", + "sales-cycle-length" + ] - skill: "blue-ocean-strategy" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Blue ocean strategy in healthtech must navigate a unique constraint: you cannot create an uncontested market space by bypassing clinical evidence, regulatory requirements, or reimbursement pathways. The most successful healthtech blue oceans are found in therapeutic areas that incumbent health IT ignores (behavioral health, musculoskeletal care, chronic pain), in care settings that existing technology does not serve (home-based care, rural health, community health centers), or in reimagining the care delivery model itself (asynchronous care, AI-augmented diagnosis, prescription digital therapeutics). The strategy canvas must include a clinical evidence axis — products that create blue oceans through evidence-based clinical differentiation build durable moats that marketing-led differentiation cannot replicate." + healthtech_context: "Blue ocean strategy in healthtech must navigate a unique + constraint: you cannot create an uncontested market space by bypassing + clinical evidence, regulatory requirements, or reimbursement pathways. The + most successful healthtech blue oceans are found in therapeutic areas that + incumbent health IT ignores (behavioral health, musculoskeletal care, + chronic pain), in care settings that existing technology does not serve + (home-based care, rural health, community health centers), or in + reimagining the care delivery model itself (asynchronous care, + AI-augmented diagnosis, prescription digital therapeutics). The strategy + canvas must include a clinical evidence axis — products that create blue + oceans through evidence-based clinical differentiation build durable moats + that marketing-led differentiation cannot replicate." healthtech_anti_patterns: - - "Pursuing a blue ocean that exists because the therapeutic area lacks reimbursement. Some clinical areas are uncontested not because competitors overlooked them but because payers do not cover interventions in that space. A blue ocean without a reimbursement pathway is a desert." - - "Creating uncontested space by avoiding FDA regulation. Products marketed as 'wellness' to sidestep regulatory requirements sacrifice the clinical credibility that health systems and payers require. The regulatory exemption that enabled the blue ocean also limits the addressable market." - - "Confusing consumer health engagement with clinical blue ocean. Consumer-facing health apps operate in a different market than clinical healthtech. A beautifully designed wellness app is not competing in the same ocean as a clinically validated diagnostic tool." - healthtech_example: "Pear Therapeutics created a blue ocean in behavioral health by pursuing FDA clearance for prescription digital therapeutics — a category that did not exist. Instead of competing with the hundreds of unregulated mental health apps, Pear obtained De Novo FDA authorization for reSET (substance use disorder) and reSET-O (opioid use disorder), creating a new category: software that is prescribed like a drug, covered by insurance, and supported by RCT evidence. The blue ocean was not 'digital mental health' (crowded) but 'FDA-cleared, reimbursable, prescription software for substance use disorders' (uncontested). The regulatory pathway that competitors avoided became the moat." - benchmark_references: ["clinical-validation-stage", "regulatory-approval-status", "payer-reimbursement-rate"] + - "Pursuing a blue ocean that exists because the therapeutic area lacks + reimbursement. Some clinical areas are uncontested not because + competitors overlooked them but because payers do not cover + interventions in that space. A blue ocean without a reimbursement + pathway is a desert." + - "Creating uncontested space by avoiding FDA regulation. Products + marketed as 'wellness' to sidestep regulatory requirements sacrifice the + clinical credibility that health systems and payers require. The + regulatory exemption that enabled the blue ocean also limits the + addressable market." + - "Confusing consumer health engagement with clinical blue ocean. + Consumer-facing health apps operate in a different market than clinical + healthtech. A beautifully designed wellness app is not competing in the + same ocean as a clinically validated diagnostic tool." + healthtech_example: "Pear Therapeutics created a blue ocean in behavioral health + by pursuing FDA clearance for prescription digital therapeutics — a + category that did not exist. Instead of competing with the hundreds of + unregulated mental health apps, Pear obtained De Novo FDA authorization + for reSET (substance use disorder) and reSET-O (opioid use disorder), + creating a new category: software that is prescribed like a drug, covered + by insurance, and supported by RCT evidence. The blue ocean was not + 'digital mental health' (crowded) but 'FDA-cleared, reimbursable, + prescription software for substance use disorders' (uncontested). The + regulatory pathway that competitors avoided became the moat." + benchmark_references: + [ + "clinical-validation-stage", + "regulatory-approval-status", + "payer-reimbursement-rate" + ] - skill: "business-model-canvas" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "The Business Model Canvas for healthtech demands a triple-stakeholder lens across every block. Value Proposition must articulate separate value for patients (better outcomes, better experience), providers (clinical workflow improvement, reduced burden), and payers (cost reduction, quality improvement). Customer Segments must identify the buyer (health system, payer, employer, patient) and distinguish them from the user (provider, patient) and the beneficiary (patient). Channels must account for health system procurement processes, EHR marketplace distribution, payer contracting, and clinical society endorsement. Revenue Streams must distinguish between payer reimbursement (CPT/HCPCS coded), health system SaaS fees, employer direct contracts, and patient self-pay. Key Activities must include clinical validation (evidence generation is a core business activity, not R&D overhead), regulatory affairs, and HIPAA compliance. Key Resources include clinical evidence, regulatory clearances, clinical advisory board relationships, and payer contracts — all of which are non-replicable assets." + healthtech_context: "The Business Model Canvas for healthtech demands a + triple-stakeholder lens across every block. Value Proposition must + articulate separate value for patients (better outcomes, better + experience), providers (clinical workflow improvement, reduced burden), + and payers (cost reduction, quality improvement). Customer Segments must + identify the buyer (health system, payer, employer, patient) and + distinguish them from the user (provider, patient) and the beneficiary + (patient). Channels must account for health system procurement processes, + EHR marketplace distribution, payer contracting, and clinical society + endorsement. Revenue Streams must distinguish between payer reimbursement + (CPT/HCPCS coded), health system SaaS fees, employer direct contracts, and + patient self-pay. Key Activities must include clinical validation + (evidence generation is a core business activity, not R&D overhead), + regulatory affairs, and HIPAA compliance. Key Resources include clinical + evidence, regulatory clearances, clinical advisory board relationships, + and payer contracts — all of which are non-replicable assets." healthtech_anti_patterns: - - "Designing the canvas with the patient as the only customer. The patient is the ultimate beneficiary, but the customer (who pays) is typically the health system, the payer, or the employer. A canvas that ignores the buyer's needs will produce a product that patients love but no one procures." - - "Omitting clinical evidence generation from Key Activities. In healthtech, generating and publishing clinical evidence is as critical as building the product itself. Companies that treat evidence as an afterthought discover that sales stall when clinical review committees ask for data." - - "Treating regulatory compliance as a Cost Structure line item rather than a Key Activity and Key Resource. Regulatory clearance is an asset that enables the business — a competitive moat, not an expense to minimize." - healthtech_example: "A remote patient monitoring startup maps its Business Model Canvas and discovers a critical misalignment: the Value Proposition emphasizes patient engagement features, but the Customer (health system) evaluates based on clinical outcome improvement and EHR integration, while the Payer evaluates based on cost avoidance (reduced ED visits, avoided hospitalizations). The canvas redesign creates three aligned value propositions: patient-facing (convenient monitoring with personalized insights), provider-facing (ambient data collection that reduces documentation burden), and payer-facing (demonstrated 25% reduction in preventable hospitalizations with published evidence). Revenue Streams shift from patient subscription to payer reimbursement via RPM CPT codes (99453, 99454, 99457, 99458), tripling the per-patient revenue and removing the patient willingness-to-pay constraint." - benchmark_references: ["payer-reimbursement-rate", "revenue-per-patient-per-month", "clinical-validation-stage"] + - "Designing the canvas with the patient as the only customer. The patient + is the ultimate beneficiary, but the customer (who pays) is typically + the health system, the payer, or the employer. A canvas that ignores the + buyer's needs will produce a product that patients love but no one + procures." + - "Omitting clinical evidence generation from Key Activities. In + healthtech, generating and publishing clinical evidence is as critical + as building the product itself. Companies that treat evidence as an + afterthought discover that sales stall when clinical review committees + ask for data." + - "Treating regulatory compliance as a Cost Structure line item rather + than a Key Activity and Key Resource. Regulatory clearance is an asset + that enables the business — a competitive moat, not an expense to + minimize." + healthtech_example: "A remote patient monitoring startup maps its Business Model + Canvas and discovers a critical misalignment: the Value Proposition + emphasizes patient engagement features, but the Customer (health system) + evaluates based on clinical outcome improvement and EHR integration, while + the Payer evaluates based on cost avoidance (reduced ED visits, avoided + hospitalizations). The canvas redesign creates three aligned value + propositions: patient-facing (convenient monitoring with personalized + insights), provider-facing (ambient data collection that reduces + documentation burden), and payer-facing (demonstrated 25% reduction in + preventable hospitalizations with published evidence). Revenue Streams + shift from patient subscription to payer reimbursement via RPM CPT codes + (99453, 99454, 99457, 99458), tripling the per-patient revenue and + removing the patient willingness-to-pay constraint." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "clinical-validation-stage" + ] - skill: "four-ps-marketing" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "The Four Ps in healthtech operate under constraints that fundamentally differ from consumer or enterprise software. Product is subject to FDA regulation — changes to a cleared device require regulatory impact assessment, and marketing claims must be consistent with the cleared indication for use. Price in healthtech is often not market-determined but reimbursement-determined: CPT codes, DRG payments, and payer fee schedules set the effective price ceiling regardless of the product's value. Place (distribution) runs through health system procurement, EHR marketplaces, clinical society endorsements, and payer formularies — not app stores, content marketing, or outbound sales. Promotion faces strict constraints: FDA labeling requirements limit what can be claimed, FTC health advertising rules prohibit unsubstantiated claims, and clinical audiences respond to peer-reviewed evidence and key opinion leader endorsement, not marketing copy." + healthtech_context: "The Four Ps in healthtech operate under constraints that + fundamentally differ from consumer or enterprise software. Product is + subject to FDA regulation — changes to a cleared device require regulatory + impact assessment, and marketing claims must be consistent with the + cleared indication for use. Price in healthtech is often not + market-determined but reimbursement-determined: CPT codes, DRG payments, + and payer fee schedules set the effective price ceiling regardless of the + product's value. Place (distribution) runs through health system + procurement, EHR marketplaces, clinical society endorsements, and payer + formularies — not app stores, content marketing, or outbound sales. + Promotion faces strict constraints: FDA labeling requirements limit what + can be claimed, FTC health advertising rules prohibit unsubstantiated + claims, and clinical audiences respond to peer-reviewed evidence and key + opinion leader endorsement, not marketing copy." healthtech_anti_patterns: - - "Setting price based on willingness-to-pay surveys or competitor matching. In healthtech, the price ceiling is often the reimbursement rate for the relevant CPT or HCPCS code. Pricing above reimbursement means the health system absorbs the gap — a losing proposition for adoption." - - "Treating consumer digital marketing as the distribution strategy. Health system buyers do not discover clinical tools through Google ads or content marketing. They discover them through clinical conferences, peer publications, EHR marketplace listings, and clinical advisory network recommendations." - - "Making clinical claims in marketing materials that exceed the evidence base or the FDA-cleared indications. This triggers FDA enforcement risk, FTC action, and — most damaging — loss of credibility with the clinical audience that evaluates claims with scientific rigor." - healthtech_example: "A digital therapeutics company applies the Four Ps and restructures its entire go-to-market. Product: they scope the product to match the FDA-cleared indication exactly, resisting feature creep that would trigger a new regulatory submission. Price: they align pricing to the CPT code reimbursement rate for remote therapeutic monitoring (99457, 99458), ensuring health systems can bill payers for the product's use without margin loss. Place: they abandon direct-to-consumer advertising and instead pursue Epic App Orchard listing, clinical conference presentations, and health plan formulary inclusion. Promotion: they replace feature-focused marketing with an evidence brief summarizing their published RCT results, distributed through medical affairs channels rather than marketing channels." - benchmark_references: ["payer-reimbursement-rate", "revenue-per-patient-per-month", "provider-adoption-rate"] + - "Setting price based on willingness-to-pay surveys or competitor + matching. In healthtech, the price ceiling is often the reimbursement + rate for the relevant CPT or HCPCS code. Pricing above reimbursement + means the health system absorbs the gap — a losing proposition for + adoption." + - "Treating consumer digital marketing as the distribution strategy. + Health system buyers do not discover clinical tools through Google ads + or content marketing. They discover them through clinical conferences, + peer publications, EHR marketplace listings, and clinical advisory + network recommendations." + - "Making clinical claims in marketing materials that exceed the evidence + base or the FDA-cleared indications. This triggers FDA enforcement risk, + FTC action, and — most damaging — loss of credibility with the clinical + audience that evaluates claims with scientific rigor." + healthtech_example: "A digital therapeutics company applies the Four Ps and + restructures its entire go-to-market. Product: they scope the product to + match the FDA-cleared indication exactly, resisting feature creep that + would trigger a new regulatory submission. Price: they align pricing to + the CPT code reimbursement rate for remote therapeutic monitoring (99457, + 99458), ensuring health systems can bill payers for the product's use + without margin loss. Place: they abandon direct-to-consumer advertising + and instead pursue Epic App Orchard listing, clinical conference + presentations, and health plan formulary inclusion. Promotion: they + replace feature-focused marketing with an evidence brief summarizing their + published RCT results, distributed through medical affairs channels rather + than marketing channels." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "provider-adoption-rate" + ] - skill: "net-promoter-score" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "NPS in healthtech must be measured separately for each stakeholder: patients, providers, and payer partners. Provider NPS is the most commercially consequential because provider word-of-mouth drives adoption across health systems — a physician champion at one hospital who recommends the product to colleagues at the next health system is the most powerful sales channel in healthcare. Patient NPS is clinically consequential because dissatisfied patients disengage, and disengagement means the clinical intervention stops. Payer NPS matters for contract renewal but is rarely measured. NPS surveys in healthtech must be triggered by clinical milestones (first clinical encounter with the product, 30-day check-in, treatment completion) rather than arbitrary time intervals, and must be designed for diverse health literacy levels." + healthtech_context: "NPS in healthtech must be measured separately for each + stakeholder: patients, providers, and payer partners. Provider NPS is the + most commercially consequential because provider word-of-mouth drives + adoption across health systems — a physician champion at one hospital who + recommends the product to colleagues at the next health system is the most + powerful sales channel in healthcare. Patient NPS is clinically + consequential because dissatisfied patients disengage, and disengagement + means the clinical intervention stops. Payer NPS matters for contract + renewal but is rarely measured. NPS surveys in healthtech must be + triggered by clinical milestones (first clinical encounter with the + product, 30-day check-in, treatment completion) rather than arbitrary time + intervals, and must be designed for diverse health literacy levels." healthtech_anti_patterns: - - "Measuring a single NPS score that blends patients and providers. These populations have fundamentally different relationships with the product, different satisfaction drivers, and different impact on the business. Blended NPS obscures both signals." - - "Optimizing patient NPS by removing clinical friction. Some clinical friction is necessary — adherence reminders, symptom tracking requirements, and escalation protocols serve patient safety even when they reduce satisfaction. NPS optimization that compromises clinical protocols is dangerous." - - "Using NPS testimonials as clinical evidence. Anecdotal patient satisfaction is not the same as clinical validation. Investors, payers, and regulators evaluate evidence, not testimonials. Conflating the two undermines credibility with clinical audiences." - healthtech_example: "A chronic disease management platform segments NPS and discovers a dangerous gap: patient NPS is 65 (strong) but provider NPS is -12 (deeply negative). Investigation reveals that patients love the app's engagement features, but providers are frustrated by alert fatigue — the system generates too many low-priority clinical alerts that interrupt workflow. The provider NPS insight triggers a clinical alert redesign that reduces alert volume by 70% while maintaining safety-critical escalations. Provider NPS rises to 35 within one quarter, and the health system expands from a pilot deployment to enterprise-wide licensing." - benchmark_references: ["provider-nps", "patient-satisfaction-score", "provider-adoption-rate"] + - "Measuring a single NPS score that blends patients and providers. These + populations have fundamentally different relationships with the product, + different satisfaction drivers, and different impact on the business. + Blended NPS obscures both signals." + - "Optimizing patient NPS by removing clinical friction. Some clinical + friction is necessary — adherence reminders, symptom tracking + requirements, and escalation protocols serve patient safety even when + they reduce satisfaction. NPS optimization that compromises clinical + protocols is dangerous." + - "Using NPS testimonials as clinical evidence. Anecdotal patient + satisfaction is not the same as clinical validation. Investors, payers, + and regulators evaluate evidence, not testimonials. Conflating the two + undermines credibility with clinical audiences." + healthtech_example: "A chronic disease management platform segments NPS and + discovers a dangerous gap: patient NPS is 65 (strong) but provider NPS is + -12 (deeply negative). Investigation reveals that patients love the app's + engagement features, but providers are frustrated by alert fatigue — the + system generates too many low-priority clinical alerts that interrupt + workflow. The provider NPS insight triggers a clinical alert redesign that + reduces alert volume by 70% while maintaining safety-critical escalations. + Provider NPS rises to 35 within one quarter, and the health system expands + from a pilot deployment to enterprise-wide licensing." + benchmark_references: [ "provider-nps", "patient-satisfaction-score", "provider-adoption-rate" ] - skill: "product-life-cycle" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "The product lifecycle in healthtech is fundamentally slower than in software because regulatory requirements create stage gates between lifecycle phases. Introduction requires not just product launch but regulatory clearance, clinical evidence generation, and payer reimbursement — each adding 6-24 months. Growth is constrained by health system sales cycles (6-18 months per customer) and implementation timelines (1-12 months per deployment). Maturity arrives when the clinical evidence base is well-established, reimbursement is broadly available, and the technology is integrated into clinical guidelines. Decline in healthtech is often triggered not by technology obsolescence but by new clinical evidence that a competing intervention is superior, or by regulatory changes that alter the competitive landscape. The critical insight for healthtech is that clinical evidence generates compounding returns — the lifecycle can be extended almost indefinitely if the company continues to publish outcomes data." + healthtech_context: "The product lifecycle in healthtech is fundamentally slower + than in software because regulatory requirements create stage gates + between lifecycle phases. Introduction requires not just product launch + but regulatory clearance, clinical evidence generation, and payer + reimbursement — each adding 6-24 months. Growth is constrained by health + system sales cycles (6-18 months per customer) and implementation + timelines (1-12 months per deployment). Maturity arrives when the clinical + evidence base is well-established, reimbursement is broadly available, and + the technology is integrated into clinical guidelines. Decline in + healthtech is often triggered not by technology obsolescence but by new + clinical evidence that a competing intervention is superior, or by + regulatory changes that alter the competitive landscape. The critical + insight for healthtech is that clinical evidence generates compounding + returns — the lifecycle can be extended almost indefinitely if the company + continues to publish outcomes data." healthtech_anti_patterns: - - "Applying consumer technology lifecycle expectations to healthtech. Products that achieve mass adoption in 12 months in consumer software may take 5-7 years to reach the same adoption level in healthcare. This is not failure — it is the structural reality of clinical adoption." - - "Treating regulatory clearance as the product launch. Clearance is the beginning of commercialization, not the end of development. Post-market surveillance, real-world evidence generation, and ongoing clinical validation continue throughout the lifecycle." - - "Assuming that a clinically validated product is immune to lifecycle decline. New clinical evidence — even evidence about competing approaches — can rapidly shift clinical guidelines and render a previously dominant product obsolete." - healthtech_example: "A telemedicine platform applies product lifecycle analysis and recognizes that its core video visit product has reached maturity — adoption plateaued during COVID and is now declining as health systems rebalance toward in-person care. Rather than defending the mature product, the company identifies that asynchronous care (store-and-forward clinical consultations) is in the Introduction phase with growing clinical evidence and emerging reimbursement. They allocate 60% of R&D to asynchronous care capabilities while maintaining the video visit product as a cash cow that funds the transition." - benchmark_references: ["provider-adoption-rate", "clinical-validation-stage", "monthly-active-patients"] + - "Applying consumer technology lifecycle expectations to healthtech. + Products that achieve mass adoption in 12 months in consumer software + may take 5-7 years to reach the same adoption level in healthcare. This + is not failure — it is the structural reality of clinical adoption." + - "Treating regulatory clearance as the product launch. Clearance is the + beginning of commercialization, not the end of development. Post-market + surveillance, real-world evidence generation, and ongoing clinical + validation continue throughout the lifecycle." + - "Assuming that a clinically validated product is immune to lifecycle + decline. New clinical evidence — even evidence about competing + approaches — can rapidly shift clinical guidelines and render a + previously dominant product obsolete." + healthtech_example: "A telemedicine platform applies product lifecycle analysis + and recognizes that its core video visit product has reached maturity — + adoption plateaued during COVID and is now declining as health systems + rebalance toward in-person care. Rather than defending the mature product, + the company identifies that asynchronous care (store-and-forward clinical + consultations) is in the Introduction phase with growing clinical evidence + and emerging reimbursement. They allocate 60% of R&D to asynchronous care + capabilities while maintaining the video visit product as a cash cow that + funds the transition." + benchmark_references: + [ + "provider-adoption-rate", + "clinical-validation-stage", + "monthly-active-patients" + ] - skill: "growth-share-matrix" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "The BCG Growth-Share Matrix maps to healthtech product portfolios with an essential modification: market share in healthtech is measured not by revenue share but by clinical evidence share and formulary/guideline inclusion. A Star is a product line with strong clinical evidence in a growing therapeutic area. A Cash Cow is a product with established reimbursement and embedded health system integration in a mature clinical area. Question Marks are products in emerging therapeutic areas with promising but unproven evidence. Dogs are products in declining therapeutic areas or those that failed to achieve clinical validation. The matrix is particularly useful for multi-product healthtech companies deciding where to invest clinical R&D resources." + healthtech_context: "The BCG Growth-Share Matrix maps to healthtech product + portfolios with an essential modification: market share in healthtech is + measured not by revenue share but by clinical evidence share and + formulary/guideline inclusion. A Star is a product line with strong + clinical evidence in a growing therapeutic area. A Cash Cow is a product + with established reimbursement and embedded health system integration in a + mature clinical area. Question Marks are products in emerging therapeutic + areas with promising but unproven evidence. Dogs are products in declining + therapeutic areas or those that failed to achieve clinical validation. The + matrix is particularly useful for multi-product healthtech companies + deciding where to invest clinical R&D resources." healthtech_anti_patterns: - - "Measuring market share by revenue alone. In healthtech, clinical evidence share (number and quality of publications, guideline mentions, key opinion leader endorsement) is a leading indicator that predicts revenue share 12-24 months in advance." - - "Killing 'Dog' product lines that serve a patient safety function. Some low-growth, low-share products in healthtech serve critical but small patient populations. Discontinuing them has ethical implications that do not arise in other industries." - - "Investing in Stars without ensuring clinical evidence keeps pace with growth. Rapid commercial scaling ahead of clinical evidence creates vulnerability — a competitor who publishes superior outcomes data can displace a market leader regardless of installed base." - healthtech_example: "A digital health company with products across diabetes management (Star — growing market, strong RCT evidence), hypertension monitoring (Cash Cow — mature market, established reimbursement), mental health screening (Question Mark — growing market, pilot data only), and weight management (Dog — crowded market, weak evidence) uses the matrix to allocate clinical R&D. They fund a multi-site RCT for mental health screening (to determine if it becomes a Star or is divested) while maintaining the diabetes product's evidence advantage and harvesting hypertension monitoring revenue to fund the portfolio." - benchmark_references: ["clinical-validation-stage", "monthly-active-patients", "revenue-per-patient-per-month"] + - "Measuring market share by revenue alone. In healthtech, clinical + evidence share (number and quality of publications, guideline mentions, + key opinion leader endorsement) is a leading indicator that predicts + revenue share 12-24 months in advance." + - "Killing 'Dog' product lines that serve a patient safety function. Some + low-growth, low-share products in healthtech serve critical but small + patient populations. Discontinuing them has ethical implications that do + not arise in other industries." + - "Investing in Stars without ensuring clinical evidence keeps pace with + growth. Rapid commercial scaling ahead of clinical evidence creates + vulnerability — a competitor who publishes superior outcomes data can + displace a market leader regardless of installed base." + healthtech_example: "A digital health company with products across diabetes + management (Star — growing market, strong RCT evidence), hypertension + monitoring (Cash Cow — mature market, established reimbursement), mental + health screening (Question Mark — growing market, pilot data only), and + weight management (Dog — crowded market, weak evidence) uses the matrix to + allocate clinical R&D. They fund a multi-site RCT for mental health + screening (to determine if it becomes a Star or is divested) while + maintaining the diabetes product's evidence advantage and harvesting + hypertension monitoring revenue to fund the portfolio." + benchmark_references: + [ + "clinical-validation-stage", + "monthly-active-patients", + "revenue-per-patient-per-month" + ] - skill: "disruptive-innovation" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Healthtech is the canonical domain for disruptive innovation with a safety constraint. Disruption in healthcare follows a specific pattern: moving clinical capabilities from higher-cost settings to lower-cost settings (hospital to clinic, clinic to home, home to self-care) and from specialist-dependent to technology-enabled (radiologist interpretation to AI-assisted screening, physician diagnosis to nurse-led with decision support). The disruption trajectory is limited by clinical safety — you cannot disrupt a care setting if the lower-cost alternative compromises patient outcomes. The most successful healthtech disruptors achieve equivalent or superior clinical outcomes at lower cost and greater convenience, validated through rigorous clinical studies. This evidence-validated disruption is the only sustainable path." + healthtech_context: "Healthtech is the canonical domain for disruptive + innovation with a safety constraint. Disruption in healthcare follows a + specific pattern: moving clinical capabilities from higher-cost settings + to lower-cost settings (hospital to clinic, clinic to home, home to + self-care) and from specialist-dependent to technology-enabled + (radiologist interpretation to AI-assisted screening, physician diagnosis + to nurse-led with decision support). The disruption trajectory is limited + by clinical safety — you cannot disrupt a care setting if the lower-cost + alternative compromises patient outcomes. The most successful healthtech + disruptors achieve equivalent or superior clinical outcomes at lower cost + and greater convenience, validated through rigorous clinical studies. This + evidence-validated disruption is the only sustainable path." healthtech_anti_patterns: - - "Attempting to disrupt clinical processes without clinical evidence that the disruption is safe. 'Move fast and break things' in healthcare means patients get hurt. Every disruption of a clinical process requires evidence that patient outcomes are maintained or improved." - - "Disrupting the provider's role without provider involvement in the design. Healthtech products that attempt to disintermediate physicians face fierce resistance and often fail clinically because they lack the clinical nuance that providers contribute." - - "Assuming that consumer adoption is sufficient validation. Patients adopting a health app does not validate clinical effectiveness. Consumer popularity and clinical efficacy are independent dimensions." - healthtech_example: "Livongo disrupted chronic disease management by moving continuous glucose monitoring and behavioral intervention from the endocrinologist's office to the patient's home. The disruption was validated through clinical studies showing equivalent or improved A1C outcomes at 30% lower cost. Critically, Livongo did not disintermediate endocrinologists — it complemented their care by providing continuous data between visits. The disruption's safety was evidence-validated, and its economic model was reimbursement-ready. This combination — clinically validated, provider-complementary, payer-attractive — is the healthtech disruption template." - benchmark_references: ["patient-outcomes-improvement", "revenue-per-patient-per-month", "payer-reimbursement-rate"] + - "Attempting to disrupt clinical processes without clinical evidence that + the disruption is safe. 'Move fast and break things' in healthcare means + patients get hurt. Every disruption of a clinical process requires + evidence that patient outcomes are maintained or improved." + - "Disrupting the provider's role without provider involvement in the + design. Healthtech products that attempt to disintermediate physicians + face fierce resistance and often fail clinically because they lack the + clinical nuance that providers contribute." + - "Assuming that consumer adoption is sufficient validation. Patients + adopting a health app does not validate clinical effectiveness. Consumer + popularity and clinical efficacy are independent dimensions." + healthtech_example: "Livongo disrupted chronic disease management by moving + continuous glucose monitoring and behavioral intervention from the + endocrinologist's office to the patient's home. The disruption was + validated through clinical studies showing equivalent or improved A1C + outcomes at 30% lower cost. Critically, Livongo did not disintermediate + endocrinologists — it complemented their care by providing continuous data + between visits. The disruption's safety was evidence-validated, and its + economic model was reimbursement-ready. This combination — clinically + validated, provider-complementary, payer-attractive — is the healthtech + disruption template." + benchmark_references: + [ + "patient-outcomes-improvement", + "revenue-per-patient-per-month", + "payer-reimbursement-rate" + ] - skill: "balanced-scorecard" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "The Balanced Scorecard for healthtech requires a fifth perspective beyond the original four: Clinical Outcomes. Financial: revenue, gross margin, reimbursement rate, burn rate. Customer: must be split into provider satisfaction and patient satisfaction, tracked independently. Internal Process: clinical workflow integration, regulatory milestone progress, implementation velocity, HIPAA compliance posture. Learning & Growth: clinical evidence pipeline, regulatory capability development, clinical advisory board strength. Clinical Outcomes: patient outcomes improvement, clinical evidence strength, adverse event rate, patient safety incident rate. This fifth perspective is non-negotiable — it is the ethical and commercial foundation of the business." + healthtech_context: "The Balanced Scorecard for healthtech requires a fifth + perspective beyond the original four: Clinical Outcomes. Financial: + revenue, gross margin, reimbursement rate, burn rate. Customer: must be + split into provider satisfaction and patient satisfaction, tracked + independently. Internal Process: clinical workflow integration, regulatory + milestone progress, implementation velocity, HIPAA compliance posture. + Learning & Growth: clinical evidence pipeline, regulatory capability + development, clinical advisory board strength. Clinical Outcomes: patient + outcomes improvement, clinical evidence strength, adverse event rate, + patient safety incident rate. This fifth perspective is non-negotiable — + it is the ethical and commercial foundation of the business." healthtech_anti_patterns: - - "Omitting the Clinical Outcomes perspective. A healthtech balanced scorecard that does not track patient outcomes is equivalent to a manufacturing scorecard that does not track product quality — the omission eventually manifests as catastrophic failure." - - "Subordinating clinical metrics to financial metrics. In healthtech, clinical outcomes lead financial outcomes by 12-24 months. Declining outcome metrics predict declining revenue, not the reverse. The scorecard must reflect this causal hierarchy." - - "Tracking only lagging indicators. Healthtech scorecards must include leading indicators for clinical risk: adverse event near-misses, patient safety concern reports, and clinical protocol deviation rates. By the time a lagging indicator reveals a clinical problem, patients may already have been harmed." - healthtech_example: "A remote patient monitoring company implements a five-perspective balanced scorecard: Financial (RPM reimbursement revenue, gross margin, CAC payback), Provider (provider NPS, provider adoption rate, clinical workflow integration score), Patient (patient engagement rate, patient satisfaction, monthly active patients), Internal Process (implementation time to value, HIPAA compliance score, EHR integration coverage), Clinical Outcomes (30-day readmission reduction, A1C improvement, patient safety incident rate). The scorecard reveals that financial metrics are strong but clinical outcome improvement has plateaued — the product is generating revenue from RPM billing codes but not delivering the outcome improvement that sustains long-term payer support. This triggers an R&D reallocation toward clinical effectiveness." - benchmark_references: ["patient-outcomes-improvement", "provider-nps", "patient-engagement-rate", "hipaa-compliance-score", "gross-margin"] + - "Omitting the Clinical Outcomes perspective. A healthtech balanced + scorecard that does not track patient outcomes is equivalent to a + manufacturing scorecard that does not track product quality — the + omission eventually manifests as catastrophic failure." + - "Subordinating clinical metrics to financial metrics. In healthtech, + clinical outcomes lead financial outcomes by 12-24 months. Declining + outcome metrics predict declining revenue, not the reverse. The + scorecard must reflect this causal hierarchy." + - "Tracking only lagging indicators. Healthtech scorecards must include + leading indicators for clinical risk: adverse event near-misses, patient + safety concern reports, and clinical protocol deviation rates. By the + time a lagging indicator reveals a clinical problem, patients may + already have been harmed." + healthtech_example: "A remote patient monitoring company implements a + five-perspective balanced scorecard: Financial (RPM reimbursement revenue, + gross margin, CAC payback), Provider (provider NPS, provider adoption + rate, clinical workflow integration score), Patient (patient engagement + rate, patient satisfaction, monthly active patients), Internal Process + (implementation time to value, HIPAA compliance score, EHR integration + coverage), Clinical Outcomes (30-day readmission reduction, A1C + improvement, patient safety incident rate). The scorecard reveals that + financial metrics are strong but clinical outcome improvement has + plateaued — the product is generating revenue from RPM billing codes but + not delivering the outcome improvement that sustains long-term payer + support. This triggers an R&D reallocation toward clinical effectiveness." + benchmark_references: + [ + "patient-outcomes-improvement", + "provider-nps", + "patient-engagement-rate", + "hipaa-compliance-score", + "gross-margin" + ] - skill: "swot-pest-analysis" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "SWOT and PEST for healthtech must account for the regulatory and clinical forces that dominate the external environment. Political: FDA policy shifts (AI/ML guidance evolution, digital health pre-certification program), CMS reimbursement policy changes, state telehealth parity laws, and congressional healthcare reform legislation. Economic: health system IT budget cycles, payer reimbursement rate adjustments, employer health benefit spending trends, and venture capital appetite for healthtech. Social: patient digital health literacy gaps, provider technology adoption resistance, health equity disparities in digital access, and post-COVID telehealth utilization normalization. Technological: AI/ML model validation standards for clinical use, interoperability standards (FHIR, USCDI), cloud security evolution, and genomics/precision medicine technology maturation." + healthtech_context: "SWOT and PEST for healthtech must account for the + regulatory and clinical forces that dominate the external environment. + Political: FDA policy shifts (AI/ML guidance evolution, digital health + pre-certification program), CMS reimbursement policy changes, state + telehealth parity laws, and congressional healthcare reform legislation. + Economic: health system IT budget cycles, payer reimbursement rate + adjustments, employer health benefit spending trends, and venture capital + appetite for healthtech. Social: patient digital health literacy gaps, + provider technology adoption resistance, health equity disparities in + digital access, and post-COVID telehealth utilization normalization. + Technological: AI/ML model validation standards for clinical use, + interoperability standards (FHIR, USCDI), cloud security evolution, and + genomics/precision medicine technology maturation." healthtech_anti_patterns: - - "Listing 'HIPAA compliance' as a strength. Every healthtech company must be HIPAA compliant — it is a legal requirement, not a differentiator. Strengths must be genuinely distinctive." - - "Ignoring the political dimension of reimbursement. CMS reimbursement decisions are as much political as clinical — congressional mandates, budget constraints, and policy priorities shape which digital health services receive coverage." - - "Conducting SWOT against direct competitors only. The most dangerous competitor in healthtech is often not another startup but a new clinical guideline that recommends an alternative approach, a payer coverage decision that excludes digital interventions, or an EHR vendor building native functionality." - healthtech_example: "A mental health tech company applies PEST and identifies a convergence of Political tailwinds (Mental Health Parity Act enforcement increasing, state telehealth parity laws expanding), Economic support (employer mental health benefit spending growing 25% annually), and Social momentum (post-pandemic destigmatization of digital mental health services). However, Technological analysis reveals that GPT-4 class models are enabling conversational AI therapy tools that could commoditize the company's chatbot-based intervention. The SWOT synthesis positions the company to leverage the political/economic/social tailwinds by pivoting from chatbot delivery to provider-augmented digital therapy with published clinical evidence — a moat that general-purpose AI cannot replicate." - benchmark_references: ["payer-reimbursement-rate", "regulatory-approval-status", "monthly-active-patients"] + - "Listing 'HIPAA compliance' as a strength. Every healthtech company must + be HIPAA compliant — it is a legal requirement, not a differentiator. + Strengths must be genuinely distinctive." + - "Ignoring the political dimension of reimbursement. CMS reimbursement + decisions are as much political as clinical — congressional mandates, + budget constraints, and policy priorities shape which digital health + services receive coverage." + - "Conducting SWOT against direct competitors only. The most dangerous + competitor in healthtech is often not another startup but a new clinical + guideline that recommends an alternative approach, a payer coverage + decision that excludes digital interventions, or an EHR vendor building + native functionality." + healthtech_example: "A mental health tech company applies PEST and identifies a + convergence of Political tailwinds (Mental Health Parity Act enforcement + increasing, state telehealth parity laws expanding), Economic support + (employer mental health benefit spending growing 25% annually), and Social + momentum (post-pandemic destigmatization of digital mental health + services). However, Technological analysis reveals that GPT-4 class models + are enabling conversational AI therapy tools that could commoditize the + company's chatbot-based intervention. The SWOT synthesis positions the + company to leverage the political/economic/social tailwinds by pivoting + from chatbot delivery to provider-augmented digital therapy with published + clinical evidence — a moat that general-purpose AI cannot replicate." + benchmark_references: + [ + "payer-reimbursement-rate", + "regulatory-approval-status", + "monthly-active-patients" + ] - skill: "scenario-planning" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "Scenario planning in healthtech must address the high-variance regulatory and reimbursement environment. The three most critical scenario dimensions are: regulatory pathway outcome (cleared/approved vs. delayed vs. rejected), reimbursement decision (payer covers vs. payer declines vs. payer covers with conditions), and clinical evidence results (positive outcomes vs. null results vs. adverse findings). Each dimension has downstream effects on revenue, fundraising, and competitive position that cascade through the business model. Healthtech scenario planning must also include a clinical safety scenario — what happens if the product causes patient harm, and what contingencies are in place." + healthtech_context: "Scenario planning in healthtech must address the + high-variance regulatory and reimbursement environment. The three most + critical scenario dimensions are: regulatory pathway outcome + (cleared/approved vs. delayed vs. rejected), reimbursement decision (payer + covers vs. payer declines vs. payer covers with conditions), and clinical + evidence results (positive outcomes vs. null results vs. adverse + findings). Each dimension has downstream effects on revenue, fundraising, + and competitive position that cascade through the business model. + Healthtech scenario planning must also include a clinical safety scenario + — what happens if the product causes patient harm, and what contingencies + are in place." healthtech_anti_patterns: - - "Building all scenarios on the assumption that regulatory clearance is obtained. A scenario plan that does not include a 'clearance delayed 12 months' or 'clearance denied' scenario is not a scenario plan — it is a single plan with different revenue assumptions." - - "Ignoring the reimbursement scenario. A product with FDA clearance but no payer coverage has limited commercial viability. The reimbursement dimension is as important as the regulatory dimension." - - "Excluding the adverse clinical event scenario. Products that interact with patient care carry a non-zero probability of causing harm. A scenario plan must include this possibility and the company's clinical, legal, and communication response." - healthtech_example: "A clinical AI company builds four scenarios for the next 24 months: (1) Base: FDA clearance in 12 months, Medicare coverage decision in 18 months, positive RCT results. (2) Upside: Breakthrough Device designation accelerates clearance to 6 months, commercial payers follow Medicare coverage. (3) Regulatory Delay: FDA requests additional data, clearance delayed 12 months, requiring runway extension through cost reduction. (4) Adverse Event: Post-market surveillance reveals a safety signal requiring product modification and supplemental submission. Each scenario has pre-committed strategic responses: runway management, communication plans, regulatory response protocols, and clinical advisory board engagement." - benchmark_references: ["time-to-regulatory-clearance", "regulatory-pathway-cost", "payer-reimbursement-rate"] + - "Building all scenarios on the assumption that regulatory clearance is + obtained. A scenario plan that does not include a 'clearance delayed 12 + months' or 'clearance denied' scenario is not a scenario plan — it is a + single plan with different revenue assumptions." + - "Ignoring the reimbursement scenario. A product with FDA clearance but + no payer coverage has limited commercial viability. The reimbursement + dimension is as important as the regulatory dimension." + - "Excluding the adverse clinical event scenario. Products that interact + with patient care carry a non-zero probability of causing harm. A + scenario plan must include this possibility and the company's clinical, + legal, and communication response." + healthtech_example: "A clinical AI company builds four scenarios for the next 24 + months: (1) Base: FDA clearance in 12 months, Medicare coverage decision + in 18 months, positive RCT results. (2) Upside: Breakthrough Device + designation accelerates clearance to 6 months, commercial payers follow + Medicare coverage. (3) Regulatory Delay: FDA requests additional data, + clearance delayed 12 months, requiring runway extension through cost + reduction. (4) Adverse Event: Post-market surveillance reveals a safety + signal requiring product modification and supplemental submission. Each + scenario has pre-committed strategic responses: runway management, + communication plans, regulatory response protocols, and clinical advisory + board engagement." + benchmark_references: + [ + "time-to-regulatory-clearance", + "regulatory-pathway-cost", + "payer-reimbursement-rate" + ] - - skill: "pricing-diagnosis" - category: "frameworks" + - category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Pricing in healthtech is fundamentally reimbursement-constrained. Unlike SaaS where pricing is a free strategic variable, healthtech pricing must align with the CPT, HCPCS, or DRG codes through which the product generates revenue. The pricing diagnosis must evaluate: reimbursement pathway (which codes apply, what rates they pay, which payers cover them), pricing model (per-patient-per-month, per-encounter, site license, hybrid), the gap between product cost and reimbursement rate (margin analysis), and whether the product generates new reimbursable events or substitutes for existing ones. The diagnosis must also address the three-payer problem: Medicare sets a national rate, commercial payers negotiate independently, and Medicaid varies by state — creating three distinct pricing realities." + healthtech_context: "Pricing in healthtech is fundamentally + reimbursement-constrained. Unlike SaaS where pricing is a free strategic + variable, healthtech pricing must align with the CPT, HCPCS, or DRG codes + through which the product generates revenue. The pricing diagnosis must + evaluate: reimbursement pathway (which codes apply, what rates they pay, + which payers cover them), pricing model (per-patient-per-month, + per-encounter, site license, hybrid), the gap between product cost and + reimbursement rate (margin analysis), and whether the product generates + new reimbursable events or substitutes for existing ones. The diagnosis + must also address the three-payer problem: Medicare sets a national rate, + commercial payers negotiate independently, and Medicaid varies by state — + creating three distinct pricing realities." healthtech_anti_patterns: - - "Setting price based on value-based pricing methodology without verifying that a reimbursement pathway exists at that price. A product worth $500/patient/month to the health system is worthless commercially if the applicable CPT code reimburses at $50." - - "Ignoring the distinction between facility and professional reimbursement. Some CPT codes have different rates depending on whether the service is provided in a hospital or a physician office — this affects the product's economic attractiveness in each setting." - - "Treating price increases as a growth lever. Healthtech price increases are constrained by reimbursement rates, health system budget cycles, and contractual terms that often include rate locks. The expansion lever in healthtech is more patients or more services per patient, not higher prices." - healthtech_example: "A remote patient monitoring company conducts a pricing diagnosis and discovers that its $150/patient/month price exceeds the combined reimbursement from RPM CPT codes (99453 + 99454 + 99457 + 99458 = approximately $120/patient/month at Medicare rates). Health system customers are absorbing a $30/patient/month loss on every enrolled patient. The pricing diagnosis triggers a restructuring: base platform fee aligned to reimbursement rates, with premium analytics and population health features sold as a separate SaaS license that is not reimbursement-dependent. This separates the reimbursement-constrained clinical product from the market-priced analytics product." - benchmark_references: ["payer-reimbursement-rate", "revenue-per-patient-per-month", "gross-margin"] + - "Setting price based on value-based pricing methodology without + verifying that a reimbursement pathway exists at that price. A product + worth $500/patient/month to the health system is worthless commercially + if the applicable CPT code reimburses at $50." + - "Ignoring the distinction between facility and professional + reimbursement. Some CPT codes have different rates depending on whether + the service is provided in a hospital or a physician office — this + affects the product's economic attractiveness in each setting." + - "Treating price increases as a growth lever. Healthtech price increases + are constrained by reimbursement rates, health system budget cycles, and + contractual terms that often include rate locks. The expansion lever in + healthtech is more patients or more services per patient, not higher + prices." + healthtech_example: "A remote patient monitoring company conducts a pricing + diagnosis and discovers that its $150/patient/month price exceeds the + combined reimbursement from RPM CPT codes (99453 + 99454 + 99457 + 99458 = + approximately $120/patient/month at Medicare rates). Health system + customers are absorbing a $30/patient/month loss on every enrolled + patient. The pricing diagnosis triggers a restructuring: base platform fee + aligned to reimbursement rates, with premium analytics and population + health features sold as a separate SaaS license that is not + reimbursement-dependent. This separates the reimbursement-constrained + clinical product from the market-priced analytics product." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "gross-margin" + ] + kind: diagnostic + ref: pricing-diagnosis - skill: "trust-equation" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Trust in healthtech operates at a higher standard than in any other technology sector because the stakes are human health and life. The trust equation (Credibility + Reliability + Intimacy / Self-Orientation) must be interpreted through a clinical lens. Credibility in healthtech requires published clinical evidence, not marketing claims — providers evaluate trust through peer-reviewed publications, clinical conference presentations, and key opinion leader endorsement. Reliability means clinical uptime and consistent performance on clinical metrics, not merely system availability — a clinical decision support tool that provides inconsistent recommendations destroys trust faster than system downtime. Intimacy means respecting the clinician-patient relationship and the provider's clinical judgment — products that override or undermine provider autonomy are rejected. Self-Orientation in healthtech is measured by whether the company prioritizes patient outcomes over revenue growth — clinical audiences have finely tuned sensors for commercial motives disguised as clinical concern." + healthtech_context: "Trust in healthtech operates at a higher standard than in + any other technology sector because the stakes are human health and life. + The trust equation (Credibility + Reliability + Intimacy / + Self-Orientation) must be interpreted through a clinical lens. Credibility + in healthtech requires published clinical evidence, not marketing claims — + providers evaluate trust through peer-reviewed publications, clinical + conference presentations, and key opinion leader endorsement. Reliability + means clinical uptime and consistent performance on clinical metrics, not + merely system availability — a clinical decision support tool that + provides inconsistent recommendations destroys trust faster than system + downtime. Intimacy means respecting the clinician-patient relationship and + the provider's clinical judgment — products that override or undermine + provider autonomy are rejected. Self-Orientation in healthtech is measured + by whether the company prioritizes patient outcomes over revenue growth — + clinical audiences have finely tuned sensors for commercial motives + disguised as clinical concern." healthtech_anti_patterns: - - "Building trust through marketing testimonials rather than clinical evidence. Providers trust peer-reviewed studies, not patient testimonials. A single well-designed RCT builds more trust than a thousand marketing case studies." - - "Treating HIPAA compliance as a trust-building credential. HIPAA compliance is the minimum legal requirement, not a trust differentiator. Trust is built through evidence, clinical expertise, and demonstrated commitment to patient outcomes." - - "Moving fast at the expense of clinical reliability. In SaaS, a bug costs customer satisfaction. In healthtech, a clinical recommendation error can cost a patient's life. The trust equation's Reliability numerator must be weighted for clinical consequence." - healthtech_example: "A clinical AI startup struggles to gain traction despite superior diagnostic accuracy. Applying the trust equation reveals the problem: Credibility is low because results are published only on arXiv preprints, not in clinical journals — providers do not trust unreviewed claims. Reliability is undermined by inconsistent model performance across patient demographics, which providers have noticed. Intimacy is damaged because the product presents AI recommendations as directives rather than decision support, threatening provider autonomy. Self-Orientation is perceived as high because the company's marketing emphasizes 'replacing radiologists' rather than 'supporting clinical decisions.' The trust analysis triggers a strategic reset: publish in JAMA Radiology, conduct bias audits across demographics, redesign the UX to position AI as advisory, and reframe messaging around clinical augmentation." - benchmark_references: ["clinical-evidence-strength", "provider-nps", "provider-adoption-rate"] + - "Building trust through marketing testimonials rather than clinical + evidence. Providers trust peer-reviewed studies, not patient + testimonials. A single well-designed RCT builds more trust than a + thousand marketing case studies." + - "Treating HIPAA compliance as a trust-building credential. HIPAA + compliance is the minimum legal requirement, not a trust differentiator. + Trust is built through evidence, clinical expertise, and demonstrated + commitment to patient outcomes." + - "Moving fast at the expense of clinical reliability. In SaaS, a bug + costs customer satisfaction. In healthtech, a clinical recommendation + error can cost a patient's life. The trust equation's Reliability + numerator must be weighted for clinical consequence." + healthtech_example: "A clinical AI startup struggles to gain traction despite + superior diagnostic accuracy. Applying the trust equation reveals the + problem: Credibility is low because results are published only on arXiv + preprints, not in clinical journals — providers do not trust unreviewed + claims. Reliability is undermined by inconsistent model performance across + patient demographics, which providers have noticed. Intimacy is damaged + because the product presents AI recommendations as directives rather than + decision support, threatening provider autonomy. Self-Orientation is + perceived as high because the company's marketing emphasizes 'replacing + radiologists' rather than 'supporting clinical decisions.' The trust + analysis triggers a strategic reset: publish in JAMA Radiology, conduct + bias audits across demographics, redesign the UX to position AI as + advisory, and reframe messaging around clinical augmentation." + benchmark_references: [ "clinical-evidence-strength", "provider-nps", "provider-adoption-rate" ] - skill: "doblin-ten-types" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "The Ten Types of Innovation framework reveals that healthtech companies over-invest in Product Performance innovation (clinical accuracy, feature richness) while underinvesting in the innovation types that drive adoption and sustainability. The most impactful healthtech innovations often come from Profit Model (reimbursement-aligned pricing, risk-sharing with payers), Network (EHR integration ecosystem, clinical data partnerships), Process (clinical workflow optimization, regulatory pathway efficiency), Channel (EHR marketplace distribution, clinical society endorsement), Customer Engagement (patient engagement design, provider champion programs), and Service (implementation support, clinical training programs). Channel and Service innovations are particularly underinvested in healthtech — companies build clinically excellent products and then struggle with distribution because they ignore the innovation types that connect the product to its clinical audience." + healthtech_context: "The Ten Types of Innovation framework reveals that + healthtech companies over-invest in Product Performance innovation + (clinical accuracy, feature richness) while underinvesting in the + innovation types that drive adoption and sustainability. The most + impactful healthtech innovations often come from Profit Model + (reimbursement-aligned pricing, risk-sharing with payers), Network (EHR + integration ecosystem, clinical data partnerships), Process (clinical + workflow optimization, regulatory pathway efficiency), Channel (EHR + marketplace distribution, clinical society endorsement), Customer + Engagement (patient engagement design, provider champion programs), and + Service (implementation support, clinical training programs). Channel and + Service innovations are particularly underinvested in healthtech — + companies build clinically excellent products and then struggle with + distribution because they ignore the innovation types that connect the + product to its clinical audience." healthtech_anti_patterns: - - "Treating clinical accuracy as the only innovation vector. A diagnostic AI with 99% accuracy that cannot be integrated into clinical workflow is less innovative than one with 95% accuracy that operates natively within the EHR." - - "Ignoring Service innovation. Health system customers evaluate the total experience — implementation support, clinical training, ongoing support, and QBR reporting — not just the product. Service innovation is the most underrated competitive lever in healthtech." - - "Skipping Profit Model innovation. The shift from fee-for-service to value-based care creates opportunities for healthtech companies to innovate on pricing — risk-sharing arrangements, outcome-based pricing, and shared savings models that align company revenue with patient outcomes." - healthtech_example: "A population health analytics company maps its innovation portfolio across the ten types and discovers that 85% of R&D investment is in Product Performance (better algorithms, more data sources, faster processing). Channel innovation (how health systems discover and adopt the product), Service innovation (implementation and training), and Customer Engagement innovation (provider champion development, clinical community building) receive less than 5% combined. Rebalancing investment toward Channel (Epic App Orchard listing, HIMSS presence), Service (standardized implementation playbook, provider certification program), and Engagement (clinical advisory board expansion, outcomes publication program) accelerates adoption more than the next algorithmic improvement would." - benchmark_references: ["provider-adoption-rate", "clinical-workflow-integration-score", "time-to-value-implementation"] + - "Treating clinical accuracy as the only innovation vector. A diagnostic + AI with 99% accuracy that cannot be integrated into clinical workflow is + less innovative than one with 95% accuracy that operates natively within + the EHR." + - "Ignoring Service innovation. Health system customers evaluate the total + experience — implementation support, clinical training, ongoing support, + and QBR reporting — not just the product. Service innovation is the most + underrated competitive lever in healthtech." + - "Skipping Profit Model innovation. The shift from fee-for-service to + value-based care creates opportunities for healthtech companies to + innovate on pricing — risk-sharing arrangements, outcome-based pricing, + and shared savings models that align company revenue with patient + outcomes." + healthtech_example: "A population health analytics company maps its innovation + portfolio across the ten types and discovers that 85% of R&D investment is + in Product Performance (better algorithms, more data sources, faster + processing). Channel innovation (how health systems discover and adopt the + product), Service innovation (implementation and training), and Customer + Engagement innovation (provider champion development, clinical community + building) receive less than 5% combined. Rebalancing investment toward + Channel (Epic App Orchard listing, HIMSS presence), Service (standardized + implementation playbook, provider certification program), and Engagement + (clinical advisory board expansion, outcomes publication program) + accelerates adoption more than the next algorithmic improvement would." + benchmark_references: + [ + "provider-adoption-rate", + "clinical-workflow-integration-score", + "time-to-value-implementation" + ] - skill: "eisenhower-matrix" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "Healthtech founders face an additional prioritization dimension that the Eisenhower Matrix must accommodate: clinical urgency. A patient safety concern is always Urgent and Important — it cannot be delegated or scheduled for later. A regulatory submission deadline is Urgent and Important. A clinical study protocol revision may be Not Urgent but is Important for long-term reimbursement viability. Health system sales cycles create artificial urgency ('we need this feature by go-live next month') that often falls in Urgent/Not Important. The key healthtech adaptation is to separate clinical urgency (patient safety, regulatory compliance) from commercial urgency (customer requests, sales pressure) — clinical urgency always takes precedence." + healthtech_context: "Healthtech founders face an additional prioritization + dimension that the Eisenhower Matrix must accommodate: clinical urgency. A + patient safety concern is always Urgent and Important — it cannot be + delegated or scheduled for later. A regulatory submission deadline is + Urgent and Important. A clinical study protocol revision may be Not Urgent + but is Important for long-term reimbursement viability. Health system + sales cycles create artificial urgency ('we need this feature by go-live + next month') that often falls in Urgent/Not Important. The key healthtech + adaptation is to separate clinical urgency (patient safety, regulatory + compliance) from commercial urgency (customer requests, sales pressure) — + clinical urgency always takes precedence." healthtech_anti_patterns: - - "Treating health system feature requests with the same urgency as patient safety concerns. A health system asking for a report format change is commercially urgent but not clinically important. A clinical alert system failure is both." - - "Delegating regulatory affairs tasks to the Not Urgent/Important quadrant. Regulatory deadlines are unforgiving — a missed submission window can delay clearance by 6-12 months." - - "Spending all capacity on Urgent/Important clinical and regulatory tasks, leaving no capacity for the Not Urgent/Important work (clinical evidence strategy, payer relationship development, product vision) that determines long-term success." - healthtech_example: "A healthtech CEO uses the Eisenhower Matrix to regain strategic capacity. Urgent/Important: a clinical safety alert that requires immediate investigation and response protocol activation. Urgent/Not Important: a health system customer requesting a custom EHR integration variant — delegated to the implementation team with standard integration templates. Not Urgent/Important: designing the clinical study that will generate the evidence needed for Medicare coverage in 18 months — the CEO allocates weekly protected time for this strategic work. Not Urgent/Not Important: attending a general tech conference with no healthtech-specific content — declined." + - "Treating health system feature requests with the same urgency as + patient safety concerns. A health system asking for a report format + change is commercially urgent but not clinically important. A clinical + alert system failure is both." + - "Delegating regulatory affairs tasks to the Not Urgent/Important + quadrant. Regulatory deadlines are unforgiving — a missed submission + window can delay clearance by 6-12 months." + - "Spending all capacity on Urgent/Important clinical and regulatory + tasks, leaving no capacity for the Not Urgent/Important work (clinical + evidence strategy, payer relationship development, product vision) that + determines long-term success." + healthtech_example: "A healthtech CEO uses the Eisenhower Matrix to regain + strategic capacity. Urgent/Important: a clinical safety alert that + requires immediate investigation and response protocol activation. + Urgent/Not Important: a health system customer requesting a custom EHR + integration variant — delegated to the implementation team with standard + integration templates. Not Urgent/Important: designing the clinical study + that will generate the evidence needed for Medicare coverage in 18 months + — the CEO allocates weekly protected time for this strategic work. Not + Urgent/Not Important: attending a general tech conference with no + healthtech-specific content — declined." benchmark_references: [] - skill: "kotter-change-model" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "Kotter's change model is essential for healthtech because every product deployment at a health system is a change management project. Providers resist new technology not because they are technophobic but because clinical workflow changes carry patient safety risk and add to already-excessive workloads. Step 1 (Create Urgency) must be grounded in clinical evidence — 'your readmission rate is 22% when the national benchmark is 15%' is more compelling than 'our product improves efficiency.' Step 3 (Form a Coalition) requires a clinical champion (respected physician who endorses the product), an IT sponsor (who approves integration), and an administrative sponsor (who approves the budget). Step 5 (Remove Obstacles) means addressing EHR integration barriers, training gaps, and clinical workflow disruptions. Step 6 (Quick Wins) must be clinical — a measurable improvement in a clinical metric within the first 30 days of deployment." + healthtech_context: "Kotter's change model is essential for healthtech because + every product deployment at a health system is a change management + project. Providers resist new technology not because they are technophobic + but because clinical workflow changes carry patient safety risk and add to + already-excessive workloads. Step 1 (Create Urgency) must be grounded in + clinical evidence — 'your readmission rate is 22% when the national + benchmark is 15%' is more compelling than 'our product improves + efficiency.' Step 3 (Form a Coalition) requires a clinical champion + (respected physician who endorses the product), an IT sponsor (who + approves integration), and an administrative sponsor (who approves the + budget). Step 5 (Remove Obstacles) means addressing EHR integration + barriers, training gaps, and clinical workflow disruptions. Step 6 (Quick + Wins) must be clinical — a measurable improvement in a clinical metric + within the first 30 days of deployment." healthtech_anti_patterns: - - "Attempting change without a clinical champion. Technology-led change initiatives that lack a respected physician advocate are rejected by clinical staff. The champion must be a peer, not an administrator." - - "Equating training with change management. Training teaches how to use the product. Change management addresses why the product matters, how it fits into clinical workflow, and what will change in daily practice. Training alone is insufficient." - - "Measuring change success by adoption metrics (logins, usage) rather than clinical outcome metrics (patient outcomes, workflow efficiency). Providers respect evidence of impact, not evidence of activity." - healthtech_example: "A clinical decision support company deploys at a 500-bed hospital using Kotter's model. Step 1: Present data showing that the hospital's sepsis mortality rate exceeds the CMS benchmark, creating clinical urgency. Step 3: Recruit the Chief Medical Officer as executive sponsor, a hospitalist physician champion, and the CMIO as IT sponsor. Step 5: Integrate the sepsis alert directly into the Epic workflow so it requires zero additional clicks. Step 6: After 30 days, publish internal data showing a 15% improvement in time-to-antibiotic for sepsis patients — a quick win that converts skeptical clinicians into advocates." - benchmark_references: ["provider-adoption-rate", "time-to-value-implementation", "patient-outcomes-improvement"] + - "Attempting change without a clinical champion. Technology-led change + initiatives that lack a respected physician advocate are rejected by + clinical staff. The champion must be a peer, not an administrator." + - "Equating training with change management. Training teaches how to use + the product. Change management addresses why the product matters, how it + fits into clinical workflow, and what will change in daily practice. + Training alone is insufficient." + - "Measuring change success by adoption metrics (logins, usage) rather + than clinical outcome metrics (patient outcomes, workflow efficiency). + Providers respect evidence of impact, not evidence of activity." + healthtech_example: "A clinical decision support company deploys at a 500-bed + hospital using Kotter's model. Step 1: Present data showing that the + hospital's sepsis mortality rate exceeds the CMS benchmark, creating + clinical urgency. Step 3: Recruit the Chief Medical Officer as executive + sponsor, a hospitalist physician champion, and the CMIO as IT sponsor. + Step 5: Integrate the sepsis alert directly into the Epic workflow so it + requires zero additional clicks. Step 6: After 30 days, publish internal + data showing a 15% improvement in time-to-antibiotic for sepsis patients — + a quick win that converts skeptical clinicians into advocates." + benchmark_references: + [ + "provider-adoption-rate", + "time-to-value-implementation", + "patient-outcomes-improvement" + ] - skill: "systems-thinking" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Healthcare is the most complex adaptive system that any entrepreneur will encounter. Systems thinking is not optional in healthtech — it is a survival skill. The healthcare system comprises interconnected subsystems (clinical delivery, payment, regulation, public health, research) where interventions in one area produce unpredictable effects in others. A digital health product that improves patient outcomes may increase health system costs (more survivors requiring continued care), reduce provider revenue (fewer procedures), or trigger regulatory scrutiny (new safety monitoring requirements). Healthtech entrepreneurs must map the causal loops, feedback mechanisms, and unintended consequences of their products within the healthcare system — and design for the systemic effects, not just the primary clinical effect." + healthtech_context: "Healthcare is the most complex adaptive system that any + entrepreneur will encounter. Systems thinking is not optional in + healthtech — it is a survival skill. The healthcare system comprises + interconnected subsystems (clinical delivery, payment, regulation, public + health, research) where interventions in one area produce unpredictable + effects in others. A digital health product that improves patient outcomes + may increase health system costs (more survivors requiring continued + care), reduce provider revenue (fewer procedures), or trigger regulatory + scrutiny (new safety monitoring requirements). Healthtech entrepreneurs + must map the causal loops, feedback mechanisms, and unintended + consequences of their products within the healthcare system — and design + for the systemic effects, not just the primary clinical effect." healthtech_anti_patterns: - - "Optimizing for a single metric without understanding system-level effects. Reducing hospital readmissions (a common healthtech value proposition) may reduce hospital revenue under fee-for-service payment — creating perverse incentives that block adoption." - - "Assuming that better clinical outcomes automatically lead to business success. The healthcare system's misaligned incentives mean that products improving patient outcomes may not generate revenue, while products that generate revenue may not improve outcomes." - - "Ignoring the provider workforce system. Products that increase clinical workload — even marginally — in an already-burned-out healthcare workforce face adoption resistance regardless of their clinical merit." - healthtech_example: "A hospital-at-home technology company applies systems thinking and maps the full causal loop of their intervention: Product reduces hospital stays (primary effect) → Reduces hospital bed utilization (secondary effect) → Reduces hospital revenue under fee-for-service (negative business effect for the customer) → BUT reduces 30-day readmissions (positive quality effect) → Improves CMS quality scores → Increases hospital reimbursement through value-based incentive programs (positive business effect). The systems map reveals that the product's value proposition depends entirely on the hospital's payment model mix. Hospitals with >30% value-based contracts benefit financially; hospitals with <10% value-based contracts lose revenue. This insight transforms the sales strategy: target hospitals with high value-based contract exposure." - benchmark_references: ["patient-outcomes-improvement", "payer-reimbursement-rate", "provider-adoption-rate"] + - "Optimizing for a single metric without understanding system-level + effects. Reducing hospital readmissions (a common healthtech value + proposition) may reduce hospital revenue under fee-for-service payment — + creating perverse incentives that block adoption." + - "Assuming that better clinical outcomes automatically lead to business + success. The healthcare system's misaligned incentives mean that + products improving patient outcomes may not generate revenue, while + products that generate revenue may not improve outcomes." + - "Ignoring the provider workforce system. Products that increase clinical + workload — even marginally — in an already-burned-out healthcare + workforce face adoption resistance regardless of their clinical merit." + healthtech_example: "A hospital-at-home technology company applies systems + thinking and maps the full causal loop of their intervention: Product + reduces hospital stays (primary effect) → Reduces hospital bed utilization + (secondary effect) → Reduces hospital revenue under fee-for-service + (negative business effect for the customer) → BUT reduces 30-day + readmissions (positive quality effect) → Improves CMS quality scores → + Increases hospital reimbursement through value-based incentive programs + (positive business effect). The systems map reveals that the product's + value proposition depends entirely on the hospital's payment model mix. + Hospitals with >30% value-based contracts benefit financially; hospitals + with <10% value-based contracts lose revenue. This insight transforms the + sales strategy: target hospitals with high value-based contract exposure." + benchmark_references: + [ + "patient-outcomes-improvement", + "payer-reimbursement-rate", + "provider-adoption-rate" + ] - skill: "smart-goals" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "SMART goals in healthtech must be clinically specific, not just commercially specific. A goal like 'increase revenue 30%' is incomplete — it must be decomposed into clinical components: 'enroll 500 new patients in RPM program (clinical), achieve >60% 90-day engagement rate (clinical), secure billing code coverage from 3 additional commercial payers (reimbursement), reduce 30-day readmission rate by 15% in enrolled population (outcomes).' Every commercial goal should be traceable to a clinical goal, because in healthtech, clinical outcomes drive commercial outcomes, not the reverse." + healthtech_context: "SMART goals in healthtech must be clinically specific, not + just commercially specific. A goal like 'increase revenue 30%' is + incomplete — it must be decomposed into clinical components: 'enroll 500 + new patients in RPM program (clinical), achieve >60% 90-day engagement + rate (clinical), secure billing code coverage from 3 additional commercial + payers (reimbursement), reduce 30-day readmission rate by 15% in enrolled + population (outcomes).' Every commercial goal should be traceable to a + clinical goal, because in healthtech, clinical outcomes drive commercial + outcomes, not the reverse." healthtech_anti_patterns: - - "Setting commercial goals without clinical outcome targets. Revenue targets that lack corresponding patient outcome targets signal a business-first culture that undermines clinical credibility." - - "Setting clinical goals without reimbursement pathway analysis. A goal to 'demonstrate 20% outcome improvement' is incomplete if the improvement does not align with a reimbursable service or measurable quality metric." - healthtech_example: "A digital therapeutics company sets SMART goals that integrate clinical and commercial dimensions: Specific — Achieve FDA clearance for insomnia DTx and secure coverage from 3 of the top 10 commercial payers. Measurable — Published RCT demonstrating >40% improvement in ISI (Insomnia Severity Index), coverage covering >30M insured lives. Achievable — RCT enrollment complete, regulatory pre-submission meeting positive. Relevant — Insomnia affects 30% of adults, represents $100B+ in economic impact, and has inadequate pharmacological treatment. Time-bound — Clearance within 8 months, payer coverage within 14 months." - benchmark_references: ["regulatory-approval-status", "payer-reimbursement-rate", "patient-outcomes-improvement"] + - "Setting commercial goals without clinical outcome targets. Revenue + targets that lack corresponding patient outcome targets signal a + business-first culture that undermines clinical credibility." + - "Setting clinical goals without reimbursement pathway analysis. A goal + to 'demonstrate 20% outcome improvement' is incomplete if the + improvement does not align with a reimbursable service or measurable + quality metric." + healthtech_example: "A digital therapeutics company sets SMART goals that + integrate clinical and commercial dimensions: Specific — Achieve FDA + clearance for insomnia DTx and secure coverage from 3 of the top 10 + commercial payers. Measurable — Published RCT demonstrating >40% + improvement in ISI (Insomnia Severity Index), coverage covering >30M + insured lives. Achievable — RCT enrollment complete, regulatory + pre-submission meeting positive. Relevant — Insomnia affects 30% of + adults, represents $100B+ in economic impact, and has inadequate + pharmacological treatment. Time-bound — Clearance within 8 months, payer + coverage within 14 months." + benchmark_references: + [ + "regulatory-approval-status", + "payer-reimbursement-rate", + "patient-outcomes-improvement" + ] # ───────────────────────────────────────────── # GAME THEORY (4 skills) @@ -251,42 +881,147 @@ skill_overlays: - skill: "game-theory-fundamentals" category: "game-theory" healthtech_relevance: "high" - healthtech_context: "Game theory in healthtech must account for multi-player games with asymmetric information and non-financial payoffs. The key players are the healthtech company, health systems, payers, regulators, providers, patients, and competing healthtech companies. Unlike most industries, the 'game' is not purely competitive — healthcare norms emphasize cooperation and patient welfare, creating mixed-motive games where pure self-interest strategies backfire. The regulator (FDA) is a player whose moves are partially predictable through public guidance and pre-submission feedback. Payers play a sequential game — Medicare moves first, and commercial payers follow with a lag. Health systems play a signaling game — early adopters send signals to later adopters through conference presentations and publications." + healthtech_context: "Game theory in healthtech must account for multi-player + games with asymmetric information and non-financial payoffs. The key + players are the healthtech company, health systems, payers, regulators, + providers, patients, and competing healthtech companies. Unlike most + industries, the 'game' is not purely competitive — healthcare norms + emphasize cooperation and patient welfare, creating mixed-motive games + where pure self-interest strategies backfire. The regulator (FDA) is a + player whose moves are partially predictable through public guidance and + pre-submission feedback. Payers play a sequential game — Medicare moves + first, and commercial payers follow with a lag. Health systems play a + signaling game — early adopters send signals to later adopters through + conference presentations and publications." healthtech_anti_patterns: - - "Applying zero-sum competitive logic. Healthcare is fundamentally cooperative — providers, payers, and healthtech companies share a common interest in patient outcomes. Pure competitive strategies that harm other players damage the company's reputation in a trust-dependent ecosystem." - - "Ignoring the regulator as a player. FDA is not a passive rule-setter but an active participant whose guidance documents, enforcement actions, and pre-submission feedback shape the competitive landscape." - healthtech_example: "A clinical AI company analyzes the competitive game among three AI diagnostic startups competing for FDA clearance in the same indication. Game theory reveals that the first company to publish a peer-reviewed clinical study sets the evidence benchmark — subsequent entrants must meet or exceed it. This first-mover advantage in evidence generation is more valuable than first-mover advantage in product features. The company accelerates its clinical study timeline, accepting a slightly smaller sample size (adequate for 510(k) but not for the comprehensive study it originally planned) to establish the evidence benchmark before competitors." - benchmark_references: ["clinical-validation-stage", "regulatory-approval-status"] + - "Applying zero-sum competitive logic. Healthcare is fundamentally + cooperative — providers, payers, and healthtech companies share a common + interest in patient outcomes. Pure competitive strategies that harm + other players damage the company's reputation in a trust-dependent + ecosystem." + - "Ignoring the regulator as a player. FDA is not a passive rule-setter + but an active participant whose guidance documents, enforcement actions, + and pre-submission feedback shape the competitive landscape." + healthtech_example: "A clinical AI company analyzes the competitive game among + three AI diagnostic startups competing for FDA clearance in the same + indication. Game theory reveals that the first company to publish a + peer-reviewed clinical study sets the evidence benchmark — subsequent + entrants must meet or exceed it. This first-mover advantage in evidence + generation is more valuable than first-mover advantage in product + features. The company accelerates its clinical study timeline, accepting a + slightly smaller sample size (adequate for 510(k) but not for the + comprehensive study it originally planned) to establish the evidence + benchmark before competitors." + benchmark_references: [ "clinical-validation-stage", "regulatory-approval-status" ] - skill: "first-mover-strategy" category: "game-theory" healthtech_relevance: "high" - healthtech_context: "First-mover advantage in healthtech manifests differently than in consumer technology. Being first to market with a product is less valuable than being first to publish clinical evidence, first to obtain regulatory clearance, or first to secure payer reimbursement. These 'regulatory firsts' create durable advantages because: (1) the first cleared product establishes the predicate device that subsequent entrants must reference, (2) the first published RCT sets the evidence standard, (3) the first company to negotiate payer coverage establishes the reimbursement code and rate that defines the market. The risk of being first is also higher in healthtech — first movers bear the full cost of clinical validation and may discover that the market is not reimbursement-ready." + healthtech_context: "First-mover advantage in healthtech manifests differently + than in consumer technology. Being first to market with a product is less + valuable than being first to publish clinical evidence, first to obtain + regulatory clearance, or first to secure payer reimbursement. These + 'regulatory firsts' create durable advantages because: (1) the first + cleared product establishes the predicate device that subsequent entrants + must reference, (2) the first published RCT sets the evidence standard, + (3) the first company to negotiate payer coverage establishes the + reimbursement code and rate that defines the market. The risk of being + first is also higher in healthtech — first movers bear the full cost of + clinical validation and may discover that the market is not + reimbursement-ready." healthtech_anti_patterns: - - "Prioritizing product launch speed over clinical evidence. In healthtech, launching first without evidence is worse than launching second with evidence. The first-mover advantage accrues to the evidence leader, not the product leader." - - "Assuming first-mover regulatory clearance creates a permanent moat. FDA clearance for a competitor is typically achievable within 12-24 months using the first mover's device as a predicate. The durable moat is clinical evidence and health system relationships, not the clearance itself." - healthtech_example: "In the continuous glucose monitoring market, Dexcom's first-mover advantage was built not on product features but on three regulatory firsts: first to achieve FDA clearance for a non-adjunctive CGM (patients could dose insulin based on CGM readings alone), first to publish the evidence that supported this clearance, and first to establish Medicare coverage. Abbott's FreeStyle Libre followed with a competitive product — but Dexcom's regulatory and reimbursement head start created a durable clinical workflow and payer relationship advantage that took Abbott years to close." - benchmark_references: ["regulatory-approval-status", "time-to-regulatory-clearance", "payer-reimbursement-rate"] + - "Prioritizing product launch speed over clinical evidence. In + healthtech, launching first without evidence is worse than launching + second with evidence. The first-mover advantage accrues to the evidence + leader, not the product leader." + - "Assuming first-mover regulatory clearance creates a permanent moat. FDA + clearance for a competitor is typically achievable within 12-24 months + using the first mover's device as a predicate. The durable moat is + clinical evidence and health system relationships, not the clearance + itself." + healthtech_example: "In the continuous glucose monitoring market, Dexcom's + first-mover advantage was built not on product features but on three + regulatory firsts: first to achieve FDA clearance for a non-adjunctive CGM + (patients could dose insulin based on CGM readings alone), first to + publish the evidence that supported this clearance, and first to establish + Medicare coverage. Abbott's FreeStyle Libre followed with a competitive + product — but Dexcom's regulatory and reimbursement head start created a + durable clinical workflow and payer relationship advantage that took + Abbott years to close." + benchmark_references: + [ + "regulatory-approval-status", + "time-to-regulatory-clearance", + "payer-reimbursement-rate" + ] - skill: "prisoners-dilemma-and-cooperation" category: "game-theory" healthtech_relevance: "high" - healthtech_context: "The prisoner's dilemma appears repeatedly in healthtech: between healthtech companies and health systems (share clinical data vs. hoard it), between competing healthtech companies (collaborate on standards vs. pursue proprietary lock-in), and between healthtech and payers (invest in long-term outcomes vs. optimize short-term costs). The cooperative equilibrium is both more ethical and more profitable in healthtech because the ecosystem is small, reputation-dependent, and long-memory. Defecting (e.g., over-claiming clinical results, locking in health systems with proprietary data formats) yields short-term advantage but destroys the trust that health system and payer relationships require." + healthtech_context: "The prisoner's dilemma appears repeatedly in healthtech: + between healthtech companies and health systems (share clinical data vs. + hoard it), between competing healthtech companies (collaborate on + standards vs. pursue proprietary lock-in), and between healthtech and + payers (invest in long-term outcomes vs. optimize short-term costs). The + cooperative equilibrium is both more ethical and more profitable in + healthtech because the ecosystem is small, reputation-dependent, and + long-memory. Defecting (e.g., over-claiming clinical results, locking in + health systems with proprietary data formats) yields short-term advantage + but destroys the trust that health system and payer relationships + require." healthtech_anti_patterns: - - "Defecting on data interoperability. Building proprietary data formats to lock in health system customers creates short-term switching costs but generates long-term resentment and regulatory risk (FHIR interoperability mandates)." - - "Defecting on clinical evidence integrity. Overstating clinical results to win a deal may succeed once, but the health system will discover the discrepancy — and will communicate the betrayal to every other system in its network." - healthtech_example: "Two competing remote patient monitoring companies face a prisoner's dilemma on industry data standards. Company A adopts open FHIR-based data standards, making it easy for health systems to switch providers. Company B builds proprietary data formats. In the short run, Company B retains customers through lock-in. In the long run, health system CIOs refuse to adopt Company B's closed system, and CMS interoperability mandates force Company B to adopt open standards anyway — having spent resources on a proprietary system that must be rebuilt. Company A's cooperative strategy wins because the regulatory environment and buyer preferences penalize defection." - benchmark_references: ["clinical-workflow-integration-score", "churn-rate-provider"] + - "Defecting on data interoperability. Building proprietary data formats + to lock in health system customers creates short-term switching costs + but generates long-term resentment and regulatory risk (FHIR + interoperability mandates)." + - "Defecting on clinical evidence integrity. Overstating clinical results + to win a deal may succeed once, but the health system will discover the + discrepancy — and will communicate the betrayal to every other system in + its network." + healthtech_example: "Two competing remote patient monitoring companies face a + prisoner's dilemma on industry data standards. Company A adopts open + FHIR-based data standards, making it easy for health systems to switch + providers. Company B builds proprietary data formats. In the short run, + Company B retains customers through lock-in. In the long run, health + system CIOs refuse to adopt Company B's closed system, and CMS + interoperability mandates force Company B to adopt open standards anyway — + having spent resources on a proprietary system that must be rebuilt. + Company A's cooperative strategy wins because the regulatory environment + and buyer preferences penalize defection." + benchmark_references: [ "clinical-workflow-integration-score", "churn-rate-provider" ] - skill: "information-asymmetry" category: "game-theory" healthtech_relevance: "high" - healthtech_context: "Information asymmetry in healthtech takes a unique form: the healthtech company knows its product's clinical data intimately, while health system buyers, payers, and patients must rely on the company's disclosures. This creates a moral hazard — the company is incentivized to emphasize positive results and downplay limitations. Healthcare's response to this asymmetry is institutional: clinical peer review, IRB oversight, FDA review, and clinical advisory board scrutiny all serve as information asymmetry reduction mechanisms. Healthtech companies that proactively reduce information asymmetry (by publishing all clinical data, including unfavorable results) build trust faster than those that manage information strategically." + healthtech_context: "Information asymmetry in healthtech takes a unique form: + the healthtech company knows its product's clinical data intimately, while + health system buyers, payers, and patients must rely on the company's + disclosures. This creates a moral hazard — the company is incentivized to + emphasize positive results and downplay limitations. Healthcare's response + to this asymmetry is institutional: clinical peer review, IRB oversight, + FDA review, and clinical advisory board scrutiny all serve as information + asymmetry reduction mechanisms. Healthtech companies that proactively + reduce information asymmetry (by publishing all clinical data, including + unfavorable results) build trust faster than those that manage information + strategically." healthtech_anti_patterns: - - "Selectively disclosing clinical data. Publishing favorable results while suppressing unfavorable ones is a form of information manipulation that, when discovered, destroys clinical credibility permanently." - - "Exploiting patient information asymmetry. Patients cannot evaluate clinical claims with the same rigor as providers. Products that make unsupported claims to patients are ethically problematic and legally vulnerable." - healthtech_example: "A clinical AI company voluntarily publishes its model's performance across demographic subgroups, revealing that accuracy is lower for certain populations. This transparency initially concerns potential health system customers. However, the disclosure — and the company's plan to address the disparity — builds trust with clinical advisory boards and positions the company as an ethical leader. A competitor that conceals similar disparities faces a devastating public disclosure when an academic researcher identifies the bias, destroying that company's clinical credibility." - benchmark_references: ["clinical-evidence-strength", "provider-nps"] + - "Selectively disclosing clinical data. Publishing favorable results + while suppressing unfavorable ones is a form of information manipulation + that, when discovered, destroys clinical credibility permanently." + - "Exploiting patient information asymmetry. Patients cannot evaluate + clinical claims with the same rigor as providers. Products that make + unsupported claims to patients are ethically problematic and legally + vulnerable." + healthtech_example: "A clinical AI company voluntarily publishes its model's + performance across demographic subgroups, revealing that accuracy is lower + for certain populations. This transparency initially concerns potential + health system customers. However, the disclosure — and the company's plan + to address the disparity — builds trust with clinical advisory boards and + positions the company as an ethical leader. A competitor that conceals + similar disparities faces a devastating public disclosure when an academic + researcher identifies the bias, destroying that company's clinical + credibility." + benchmark_references: [ "clinical-evidence-strength", "provider-nps" ] # ───────────────────────────────────────────── # NEGOTIATION (3 skills) @@ -295,32 +1030,110 @@ skill_overlays: - skill: "cooperative-negotiation" category: "negotiation" healthtech_relevance: "critical" - healthtech_context: "Health system and payer negotiations in healthtech are inherently cooperative because the relationship extends over years and the shared interest is patient outcomes. Adversarial negotiation tactics destroy the trust required for clinical partnerships. Cooperative negotiation in healthtech means: structuring pilot agreements as mutual learning exercises (not win/lose evaluations), designing contracts with shared outcome metrics (not just SaaS seat licenses), and treating the health system's clinical champion as a co-developer (not a customer). The negotiation framework must also address the multi-stakeholder nature of health system deals: the clinical champion, the CIO/CMIO, procurement, legal, and the clinical review committee each have different interests that must be satisfied cooperatively." + healthtech_context: "Health system and payer negotiations in healthtech are + inherently cooperative because the relationship extends over years and the + shared interest is patient outcomes. Adversarial negotiation tactics + destroy the trust required for clinical partnerships. Cooperative + negotiation in healthtech means: structuring pilot agreements as mutual + learning exercises (not win/lose evaluations), designing contracts with + shared outcome metrics (not just SaaS seat licenses), and treating the + health system's clinical champion as a co-developer (not a customer). The + negotiation framework must also address the multi-stakeholder nature of + health system deals: the clinical champion, the CIO/CMIO, procurement, + legal, and the clinical review committee each have different interests + that must be satisfied cooperatively." healthtech_anti_patterns: - - "Negotiating against the clinical champion. The clinical champion is the company's strongest advocate inside the health system. An adversarial negotiation stance with this person damages the most valuable relationship in the deal." - - "Using artificial urgency or competitive pressure tactics. Health system procurement moves at its own pace — creating false urgency undermines trust and signals commercial desperation." - healthtech_example: "A healthtech company negotiating a $500K enterprise deployment at a major health system structures the deal cooperatively: a 90-day pilot with jointly defined clinical outcome metrics, pricing that starts at cost during the pilot and escalates to full rate upon outcome achievement, shared publication rights for clinical results, and a dedicated implementation liaison who reports to both the company and the health system CMIO. This structure converts a vendor-buyer negotiation into a clinical partnership — and the health system becomes a referenceable advocate." - benchmark_references: ["contract-value-health-system", "sales-cycle-length", "time-to-value-implementation"] + - "Negotiating against the clinical champion. The clinical champion is the + company's strongest advocate inside the health system. An adversarial + negotiation stance with this person damages the most valuable + relationship in the deal." + - "Using artificial urgency or competitive pressure tactics. Health system + procurement moves at its own pace — creating false urgency undermines + trust and signals commercial desperation." + healthtech_example: "A healthtech company negotiating a $500K enterprise + deployment at a major health system structures the deal cooperatively: a + 90-day pilot with jointly defined clinical outcome metrics, pricing that + starts at cost during the pilot and escalates to full rate upon outcome + achievement, shared publication rights for clinical results, and a + dedicated implementation liaison who reports to both the company and the + health system CMIO. This structure converts a vendor-buyer negotiation + into a clinical partnership — and the health system becomes a + referenceable advocate." + benchmark_references: + [ + "contract-value-health-system", + "sales-cycle-length", + "time-to-value-implementation" + ] - skill: "competitive-negotiation" category: "negotiation" healthtech_relevance: "moderate" - healthtech_context: "Competitive negotiation in healthtech applies primarily in three contexts: payer rate negotiations (where the healthtech company negotiates reimbursement rates with commercial payers), exclusive distribution agreements (where health systems demand exclusive territory rights), and M&A discussions. In payer negotiations, the company's clinical evidence is its primary leverage — published outcomes data that demonstrates cost avoidance is the strongest argument for higher reimbursement rates. In exclusive territory negotiations, the company must balance the value of exclusivity (guaranteed volume) against the cost (limited market access)." + healthtech_context: "Competitive negotiation in healthtech applies primarily in + three contexts: payer rate negotiations (where the healthtech company + negotiates reimbursement rates with commercial payers), exclusive + distribution agreements (where health systems demand exclusive territory + rights), and M&A discussions. In payer negotiations, the company's + clinical evidence is its primary leverage — published outcomes data that + demonstrates cost avoidance is the strongest argument for higher + reimbursement rates. In exclusive territory negotiations, the company must + balance the value of exclusivity (guaranteed volume) against the cost + (limited market access)." healthtech_anti_patterns: - - "Using competitive negotiation tactics in health system relationships. Health systems are long-term clinical partners, not adversarial counterparties. Competitive tactics that win a deal but damage the relationship cost more in the long run." - - "Negotiating payer rates without published health economic data. Payers evaluate reimbursement based on cost-effectiveness evidence. Without it, the negotiation lacks a credible anchor." - healthtech_example: "A digital therapeutics company negotiates with a large commercial payer for formulary inclusion. The company's competitive advantage is a published RCT showing 35% improvement in outcomes and a health economic analysis demonstrating $4,200 in avoided medical costs per patient per year. The negotiation anchors on value: the company requests a reimbursement rate of $200/patient/month ($2,400/year) — significantly less than the $4,200 in demonstrated savings. The payer accepts because the cost-savings ratio is compelling, and the clinical evidence provides the internal justification for the coverage decision." - benchmark_references: ["payer-reimbursement-rate", "patient-outcomes-improvement", "clinical-evidence-strength"] + - "Using competitive negotiation tactics in health system relationships. + Health systems are long-term clinical partners, not adversarial + counterparties. Competitive tactics that win a deal but damage the + relationship cost more in the long run." + - "Negotiating payer rates without published health economic data. Payers + evaluate reimbursement based on cost-effectiveness evidence. Without it, + the negotiation lacks a credible anchor." + healthtech_example: "A digital therapeutics company negotiates with a large + commercial payer for formulary inclusion. The company's competitive + advantage is a published RCT showing 35% improvement in outcomes and a + health economic analysis demonstrating $4,200 in avoided medical costs per + patient per year. The negotiation anchors on value: the company requests a + reimbursement rate of $200/patient/month ($2,400/year) — significantly + less than the $4,200 in demonstrated savings. The payer accepts because + the cost-savings ratio is compelling, and the clinical evidence provides + the internal justification for the coverage decision." + benchmark_references: + [ + "payer-reimbursement-rate", + "patient-outcomes-improvement", + "clinical-evidence-strength" + ] - skill: "negotiation-game-theory" category: "game-theory" healthtech_relevance: "high" - healthtech_context: "Negotiation game theory in healthtech must account for the sequential nature of health system and payer negotiations. Health systems negotiate with full awareness that Medicare rates set a reference price, that competing health systems have likely received similar proposals, and that the healthtech company's clinical evidence is either strong or weak (not something that can be bluffed). The repeated-game nature of healthcare negotiations (annual renewals, multi-year contracts, expanding relationships) means that cooperative strategies dominate competitive ones. Healthtech negotiations are also information-rich: both parties can observe clinical outcomes, usage data, and patient engagement metrics in real time." + healthtech_context: "Negotiation game theory in healthtech must account for the + sequential nature of health system and payer negotiations. Health systems + negotiate with full awareness that Medicare rates set a reference price, + that competing health systems have likely received similar proposals, and + that the healthtech company's clinical evidence is either strong or weak + (not something that can be bluffed). The repeated-game nature of + healthcare negotiations (annual renewals, multi-year contracts, expanding + relationships) means that cooperative strategies dominate competitive + ones. Healthtech negotiations are also information-rich: both parties can + observe clinical outcomes, usage data, and patient engagement metrics in + real time." healthtech_anti_patterns: - - "Bluffing about clinical evidence or product capabilities. Healthcare negotiations are conducted by clinically sophisticated buyers who verify claims independently. Being caught in a bluff destroys not just the deal but the company's reputation across the health system network." - - "Treating each negotiation as independent. Health system purchasing networks share information. A concession made to one system becomes the expected baseline for the next." - healthtech_example: "A healthtech company analyzes the negotiation game across its health system pipeline and recognizes that its first major health system deal will set the reference price for all subsequent negotiations. Game theory analysis suggests a strategy of accepting slightly lower pricing on the first deal in exchange for contractual permission to publish clinical outcomes data — the published results from a prestigious health system become leverage for higher pricing in subsequent negotiations." - benchmark_references: ["contract-value-health-system", "sales-cycle-length"] + - "Bluffing about clinical evidence or product capabilities. Healthcare + negotiations are conducted by clinically sophisticated buyers who verify + claims independently. Being caught in a bluff destroys not just the deal + but the company's reputation across the health system network." + - "Treating each negotiation as independent. Health system purchasing + networks share information. A concession made to one system becomes the + expected baseline for the next." + healthtech_example: "A healthtech company analyzes the negotiation game across + its health system pipeline and recognizes that its first major health + system deal will set the reference price for all subsequent negotiations. + Game theory analysis suggests a strategy of accepting slightly lower + pricing on the first deal in exchange for contractual permission to + publish clinical outcomes data — the published results from a prestigious + health system become leverage for higher pricing in subsequent + negotiations." + benchmark_references: [ "contract-value-health-system", "sales-cycle-length" ] # ───────────────────────────────────────────── # LEADERSHIP & PEOPLE (5 skills) @@ -329,52 +1142,171 @@ skill_overlays: - skill: "decision-making-under-pressure" category: "leadership" healthtech_relevance: "critical" - healthtech_context: "Decision-making under pressure in healthtech carries a dimension absent from other technology sectors: clinical consequence. A decision to ship a product update may affect patient care. A decision to delay a feature may leave patients without a beneficial intervention. A decision to cut costs may reduce clinical support staffing below safe levels. Healthtech leaders must develop a decision framework that explicitly weighs patient safety alongside commercial considerations — and when the two conflict, patient safety must prevail without exception. This is not merely an ethical stance but a practical one: a single patient safety incident can destroy the company through regulatory action, litigation, and reputational damage." + healthtech_context: "Decision-making under pressure in healthtech carries a + dimension absent from other technology sectors: clinical consequence. A + decision to ship a product update may affect patient care. A decision to + delay a feature may leave patients without a beneficial intervention. A + decision to cut costs may reduce clinical support staffing below safe + levels. Healthtech leaders must develop a decision framework that + explicitly weighs patient safety alongside commercial considerations — and + when the two conflict, patient safety must prevail without exception. This + is not merely an ethical stance but a practical one: a single patient + safety incident can destroy the company through regulatory action, + litigation, and reputational damage." healthtech_anti_patterns: - - "Applying the 'bias toward action' startup philosophy to clinical decisions. Speed is valuable for commercial decisions but dangerous for clinical ones. Clinical decisions require deliberation proportional to the potential for patient harm." - - "Delegating clinical safety decisions to non-clinical team members. Patient safety decisions must involve clinical expertise — a product manager or engineer without clinical background should not make decisions that affect patient care pathways." - healthtech_example: "A healthtech CEO faces a pressure decision: a health system customer demands a product feature change that would bypass a clinical safety alert to reduce provider alert fatigue. The commercial pressure is significant — the customer threatens contract non-renewal. The CEO consults the clinical advisory board, which determines that the safety alert prevents a rare but potentially fatal drug interaction. The decision: the alert remains mandatory, but the product team redesigns the alert UX to reduce fatigue without compromising safety. The customer renews after seeing the redesigned experience." - benchmark_references: ["data-security-incident-rate", "provider-nps"] + - "Applying the 'bias toward action' startup philosophy to clinical + decisions. Speed is valuable for commercial decisions but dangerous for + clinical ones. Clinical decisions require deliberation proportional to + the potential for patient harm." + - "Delegating clinical safety decisions to non-clinical team members. + Patient safety decisions must involve clinical expertise — a product + manager or engineer without clinical background should not make + decisions that affect patient care pathways." + healthtech_example: "A healthtech CEO faces a pressure decision: a health system + customer demands a product feature change that would bypass a clinical + safety alert to reduce provider alert fatigue. The commercial pressure is + significant — the customer threatens contract non-renewal. The CEO + consults the clinical advisory board, which determines that the safety + alert prevents a rare but potentially fatal drug interaction. The + decision: the alert remains mandatory, but the product team redesigns the + alert UX to reduce fatigue without compromising safety. The customer + renews after seeing the redesigned experience." + benchmark_references: [ "data-security-incident-rate", "provider-nps" ] - skill: "leading-through-change" category: "leadership" healthtech_relevance: "high" - healthtech_context: "Leading through change in healthtech requires understanding that the healthcare workforce is simultaneously the most change-resistant and the most overburdened workforce in the economy. Physicians have trained for 10-15 years in specific clinical practices. Nurses manage care under extreme time pressure. Asking these professionals to adopt new technology is asking them to change deeply embedded clinical behaviors while maintaining patient safety standards. Change leadership in healthtech must respect this reality — change must be clinically justified (not just commercially motivated), incrementally introduced (not big-bang deployed), and champion-led (not mandated from above)." + healthtech_context: "Leading through change in healthtech requires understanding + that the healthcare workforce is simultaneously the most change-resistant + and the most overburdened workforce in the economy. Physicians have + trained for 10-15 years in specific clinical practices. Nurses manage care + under extreme time pressure. Asking these professionals to adopt new + technology is asking them to change deeply embedded clinical behaviors + while maintaining patient safety standards. Change leadership in + healthtech must respect this reality — change must be clinically justified + (not just commercially motivated), incrementally introduced (not big-bang + deployed), and champion-led (not mandated from above)." healthtech_anti_patterns: - - "Mandating technology adoption without clinical justification. Providers comply with mandates but do not engage. Mandated adoption without clinical buy-in leads to workarounds that undermine the product's clinical effectiveness." - - "Deploying to all providers simultaneously. Phased rollout with clinical champions who train and support their peers produces better adoption than enterprise-wide simultaneous deployment." - healthtech_example: "A health system deploys a clinical AI tool for early sepsis detection using a change leadership approach. Phase 1: Three physician champions use the tool for 30 days and present their experience (including saved lives) at a medical staff meeting. Phase 2: Their departments adopt, with champions available for peer support. Phase 3: Hospital-wide rollout with the original champions serving as clinical super-users. This champion-cascade model achieves 75% adoption in 90 days — compared to a failed previous deployment of a different tool that mandated simultaneous adoption and achieved 25%." - benchmark_references: ["provider-adoption-rate", "time-to-value-implementation"] + - "Mandating technology adoption without clinical justification. Providers + comply with mandates but do not engage. Mandated adoption without + clinical buy-in leads to workarounds that undermine the product's + clinical effectiveness." + - "Deploying to all providers simultaneously. Phased rollout with clinical + champions who train and support their peers produces better adoption + than enterprise-wide simultaneous deployment." + healthtech_example: "A health system deploys a clinical AI tool for early sepsis + detection using a change leadership approach. Phase 1: Three physician + champions use the tool for 30 days and present their experience (including + saved lives) at a medical staff meeting. Phase 2: Their departments adopt, + with champions available for peer support. Phase 3: Hospital-wide rollout + with the original champions serving as clinical super-users. This + champion-cascade model achieves 75% adoption in 90 days — compared to a + failed previous deployment of a different tool that mandated simultaneous + adoption and achieved 25%." + benchmark_references: [ "provider-adoption-rate", "time-to-value-implementation" ] - skill: "emotional-intelligence" category: "frameworks" healthtech_relevance: "high" - healthtech_context: "Emotional intelligence in healthtech extends beyond interpersonal dynamics to include clinical empathy — the ability to understand the emotional experience of patients navigating illness and the emotional burden of providers managing life-and-death decisions daily. Healthtech founders who lack clinical empathy build products that treat healthcare as a workflow optimization problem rather than a human experience. The most successful healthtech companies are led by founders who understand that a patient using their product may be frightened, a provider may be exhausted, and a health system administrator may be overwhelmed — and who design products that respect these emotional realities." + healthtech_context: "Emotional intelligence in healthtech extends beyond + interpersonal dynamics to include clinical empathy — the ability to + understand the emotional experience of patients navigating illness and the + emotional burden of providers managing life-and-death decisions daily. + Healthtech founders who lack clinical empathy build products that treat + healthcare as a workflow optimization problem rather than a human + experience. The most successful healthtech companies are led by founders + who understand that a patient using their product may be frightened, a + provider may be exhausted, and a health system administrator may be + overwhelmed — and who design products that respect these emotional + realities." healthtech_anti_patterns: - - "Treating provider resistance as irrational. Provider skepticism toward new technology is often rational — they have seen countless 'revolutionary' health IT products fail, disrupt workflow, and waste their time. Emotional intelligence means respecting this learned skepticism." - - "Designing patient-facing products without understanding the emotional state of the patient population. A patient recently diagnosed with cancer has different emotional needs from a patient managing stable diabetes. One-size-fits-all engagement design ignores these differences." - healthtech_example: "A mental health tech company redesigns its patient onboarding after emotional intelligence analysis reveals that patients referred to the platform are often in crisis — they are not calmly evaluating software features. The redesigned onboarding eliminates all setup friction, immediately provides a therapeutic exercise (not an account creation form), and offers a human crisis line as the first contact option. Completion rates increase from 30% to 65%, and patient NPS for the onboarding experience rises from 40 to 78." - benchmark_references: ["patient-satisfaction-score", "patient-engagement-rate"] + - "Treating provider resistance as irrational. Provider skepticism toward + new technology is often rational — they have seen countless + 'revolutionary' health IT products fail, disrupt workflow, and waste + their time. Emotional intelligence means respecting this learned + skepticism." + - "Designing patient-facing products without understanding the emotional + state of the patient population. A patient recently diagnosed with + cancer has different emotional needs from a patient managing stable + diabetes. One-size-fits-all engagement design ignores these + differences." + healthtech_example: "A mental health tech company redesigns its patient + onboarding after emotional intelligence analysis reveals that patients + referred to the platform are often in crisis — they are not calmly + evaluating software features. The redesigned onboarding eliminates all + setup friction, immediately provides a therapeutic exercise (not an + account creation form), and offers a human crisis line as the first + contact option. Completion rates increase from 30% to 65%, and patient NPS + for the onboarding experience rises from 40 to 78." + benchmark_references: [ "patient-satisfaction-score", "patient-engagement-rate" ] - skill: "psychological-safety" category: "frameworks" healthtech_relevance: "critical" - healthtech_context: "Psychological safety in healthtech carries clinical safety implications. A team that lacks psychological safety will not report product defects that could affect patient care, will not raise concerns about clinical evidence quality, and will not challenge decisions that prioritize commercial objectives over patient outcomes. In healthcare, the concept of a 'just culture' — where reporting errors and near-misses is encouraged and non-punitive — has been shown to reduce patient harm. Healthtech companies must extend this just culture to their product development process: engineers must feel safe reporting bugs that could affect clinical decisions, clinical team members must feel safe challenging product decisions that could compromise patient safety, and quality assurance must have the authority to halt releases that fail safety criteria." + healthtech_context: "Psychological safety in healthtech carries clinical safety + implications. A team that lacks psychological safety will not report + product defects that could affect patient care, will not raise concerns + about clinical evidence quality, and will not challenge decisions that + prioritize commercial objectives over patient outcomes. In healthcare, the + concept of a 'just culture' — where reporting errors and near-misses is + encouraged and non-punitive — has been shown to reduce patient harm. + Healthtech companies must extend this just culture to their product + development process: engineers must feel safe reporting bugs that could + affect clinical decisions, clinical team members must feel safe + challenging product decisions that could compromise patient safety, and + quality assurance must have the authority to halt releases that fail + safety criteria." healthtech_anti_patterns: - - "Treating product defect reports as negative events rather than safety contributions. In healthtech, an engineer who identifies a clinical decision support error before deployment has potentially saved lives. The reporting behavior must be celebrated, not punished." - - "Allowing commercial pressure to silence clinical safety concerns. If a product manager overrides a clinical team member's safety concern to meet a release deadline, the company has failed at psychological safety — and has potentially endangered patients." - healthtech_example: "A clinical AI company establishes a 'clinical safety stop' protocol: any team member, regardless of seniority, can halt a product release by raising a clinical safety concern. The concern is evaluated by the Chief Medical Officer within 24 hours. In the first year, the stop protocol is invoked seven times — four concerns are substantiated and trigger product modifications before release, three are cleared after review. The protocol prevents two algorithmic errors that would have affected clinical recommendations for thousands of patients." - benchmark_references: ["data-security-incident-rate", "provider-nps"] + - "Treating product defect reports as negative events rather than safety + contributions. In healthtech, an engineer who identifies a clinical + decision support error before deployment has potentially saved lives. + The reporting behavior must be celebrated, not punished." + - "Allowing commercial pressure to silence clinical safety concerns. If a + product manager overrides a clinical team member's safety concern to + meet a release deadline, the company has failed at psychological safety + — and has potentially endangered patients." + healthtech_example: "A clinical AI company establishes a 'clinical safety stop' + protocol: any team member, regardless of seniority, can halt a product + release by raising a clinical safety concern. The concern is evaluated by + the Chief Medical Officer within 24 hours. In the first year, the stop + protocol is invoked seven times — four concerns are substantiated and + trigger product modifications before release, three are cleared after + review. The protocol prevents two algorithmic errors that would have + affected clinical recommendations for thousands of patients." + benchmark_references: [ "data-security-incident-rate", "provider-nps" ] - skill: "purpose-driven-leadership" category: "leadership" healthtech_relevance: "high" - healthtech_context: "Purpose-driven leadership in healthtech is not aspirational — it is operational. The purpose (improving patient health outcomes) provides the decision-making framework for every trade-off: when commercial interests conflict with clinical interests, purpose resolves the tie. Healthtech companies with genuine purpose-driven leadership attract clinical talent who want to improve healthcare, build products that providers trust, and develop the clinical evidence rigor that payers require. Companies where purpose is performative (marketing language without operational commitment) are identified quickly by clinical audiences, who have finely tuned sensors for authenticity." + healthtech_context: "Purpose-driven leadership in healthtech is not aspirational + — it is operational. The purpose (improving patient health outcomes) + provides the decision-making framework for every trade-off: when + commercial interests conflict with clinical interests, purpose resolves + the tie. Healthtech companies with genuine purpose-driven leadership + attract clinical talent who want to improve healthcare, build products + that providers trust, and develop the clinical evidence rigor that payers + require. Companies where purpose is performative (marketing language + without operational commitment) are identified quickly by clinical + audiences, who have finely tuned sensors for authenticity." healthtech_anti_patterns: - - "Using patient outcomes language in marketing without tracking patient outcomes operationally. If the company's dashboards show revenue and engagement but not clinical outcome metrics, the purpose is performative." - - "Making purpose-driven hiring claims while compensating executives purely on financial metrics. Executive incentive structures that lack clinical outcome components signal that purpose is subordinate to profit." - healthtech_example: "A healthtech CEO restructures executive compensation to include a clinical outcome component: 20% of variable compensation is tied to patient outcomes improvement metrics. The board initially resists, arguing that clinical outcomes are influenced by factors outside the company's control. The CEO counters that revenue is also influenced by external factors but no one questions revenue-based incentives. The compensation restructuring sends a powerful signal to the clinical team, to health system customers, and to investors that patient outcomes are a first-class business metric." - benchmark_references: ["patient-outcomes-improvement", "provider-nps"] + - "Using patient outcomes language in marketing without tracking patient + outcomes operationally. If the company's dashboards show revenue and + engagement but not clinical outcome metrics, the purpose is + performative." + - "Making purpose-driven hiring claims while compensating executives + purely on financial metrics. Executive incentive structures that lack + clinical outcome components signal that purpose is subordinate to + profit." + healthtech_example: "A healthtech CEO restructures executive compensation to + include a clinical outcome component: 20% of variable compensation is tied + to patient outcomes improvement metrics. The board initially resists, + arguing that clinical outcomes are influenced by factors outside the + company's control. The CEO counters that revenue is also influenced by + external factors but no one questions revenue-based incentives. The + compensation restructuring sends a powerful signal to the clinical team, + to health system customers, and to investors that patient outcomes are a + first-class business metric." + benchmark_references: [ "patient-outcomes-improvement", "provider-nps" ] # ───────────────────────────────────────────── # AI & DATA (3 skills) @@ -383,33 +1315,125 @@ skill_overlays: - skill: "ai-vision-and-strategy" category: "ai-leadership" healthtech_relevance: "critical" - healthtech_context: "AI strategy in healthtech must navigate the FDA's evolving framework for AI/ML-based Software as a Medical Device (SaMD). The FDA's 2023 AI/ML Action Plan and subsequent guidance documents require that AI-based clinical tools demonstrate safety and effectiveness, maintain performance over time (no model drift degradation), and provide transparency about the AI's role in clinical decision-making. AI strategy in healthtech must address: regulatory pathway for AI-based products (predetermined change control plans for iterative model updates), clinical validation (prospective clinical studies, not just retrospective accuracy testing), algorithmic fairness (performance across demographic subgroups), and explainability (clinicians must understand why the AI makes a recommendation). The AI strategy must also address the unique risk that an AI-based clinical error could harm patients — making AI safety a patient safety obligation." + healthtech_context: "AI strategy in healthtech must navigate the FDA's evolving + framework for AI/ML-based Software as a Medical Device (SaMD). The FDA's + 2023 AI/ML Action Plan and subsequent guidance documents require that + AI-based clinical tools demonstrate safety and effectiveness, maintain + performance over time (no model drift degradation), and provide + transparency about the AI's role in clinical decision-making. AI strategy + in healthtech must address: regulatory pathway for AI-based products + (predetermined change control plans for iterative model updates), clinical + validation (prospective clinical studies, not just retrospective accuracy + testing), algorithmic fairness (performance across demographic subgroups), + and explainability (clinicians must understand why the AI makes a + recommendation). The AI strategy must also address the unique risk that an + AI-based clinical error could harm patients — making AI safety a patient + safety obligation." healthtech_anti_patterns: - - "Treating AI accuracy on retrospective datasets as clinical validation. FDA requires prospective clinical evidence, not just technical benchmarks. An AI with 99% accuracy on a research dataset may perform very differently in real clinical practice with messy, incomplete data." - - "Building 'black box' AI clinical tools. The FDA and clinical audiences require explainability — clinicians will not trust (and should not trust) recommendations they cannot understand. Explainability is a regulatory requirement and a clinical adoption requirement." - - "Planning continuous model updates without a predetermined change control plan. The FDA requires that SaMD companies define in advance which types of model changes require new regulatory submissions versus ongoing monitoring." - healthtech_example: "A clinical AI company develops a strategy that addresses FDA requirements from the architecture level. The AI system is designed with an explainability layer that provides clinicians with the top three factors influencing each recommendation. The company files a predetermined change control plan with FDA that defines the boundaries of autonomous model updates (performance improvement within the cleared indication) versus changes requiring new submission (new indications, new data types, architecture changes). Clinical validation includes a prospective multi-site study with pre-specified performance thresholds across eight demographic subgroups." - benchmark_references: ["regulatory-approval-status", "clinical-evidence-strength", "clinical-validation-stage"] + - "Treating AI accuracy on retrospective datasets as clinical validation. + FDA requires prospective clinical evidence, not just technical + benchmarks. An AI with 99% accuracy on a research dataset may perform + very differently in real clinical practice with messy, incomplete data." + - "Building 'black box' AI clinical tools. The FDA and clinical audiences + require explainability — clinicians will not trust (and should not + trust) recommendations they cannot understand. Explainability is a + regulatory requirement and a clinical adoption requirement." + - "Planning continuous model updates without a predetermined change + control plan. The FDA requires that SaMD companies define in advance + which types of model changes require new regulatory submissions versus + ongoing monitoring." + healthtech_example: "A clinical AI company develops a strategy that addresses + FDA requirements from the architecture level. The AI system is designed + with an explainability layer that provides clinicians with the top three + factors influencing each recommendation. The company files a predetermined + change control plan with FDA that defines the boundaries of autonomous + model updates (performance improvement within the cleared indication) + versus changes requiring new submission (new indications, new data types, + architecture changes). Clinical validation includes a prospective + multi-site study with pre-specified performance thresholds across eight + demographic subgroups." + benchmark_references: + [ + "regulatory-approval-status", + "clinical-evidence-strength", + "clinical-validation-stage" + ] - skill: "ai-human-centered-approach" category: "ai-leadership" healthtech_relevance: "critical" - healthtech_context: "Human-centered AI in healthtech means provider-centered and patient-centered simultaneously. For providers, human-centered AI means decision support (not decision replacement), transparent reasoning, graceful degradation when uncertain, and respect for clinical judgment when the provider disagrees with the AI. For patients, it means accessible explanations, respect for health literacy variation, cultural sensitivity, and the ability to involve family or caregivers. The 'human in the loop' is not optional in clinical AI — it is a regulatory and ethical requirement. FDA guidance emphasizes that AI/ML-based SaMD should augment clinical decision-making, not replace it." + healthtech_context: "Human-centered AI in healthtech means provider-centered and + patient-centered simultaneously. For providers, human-centered AI means + decision support (not decision replacement), transparent reasoning, + graceful degradation when uncertain, and respect for clinical judgment + when the provider disagrees with the AI. For patients, it means accessible + explanations, respect for health literacy variation, cultural sensitivity, + and the ability to involve family or caregivers. The 'human in the loop' + is not optional in clinical AI — it is a regulatory and ethical + requirement. FDA guidance emphasizes that AI/ML-based SaMD should augment + clinical decision-making, not replace it." healthtech_anti_patterns: - - "Designing AI that bypasses the clinician. Autonomous AI clinical decision-making without clinician oversight is neither regulatorily permissible (for most clinical applications) nor clinically safe. The clinician must remain the decision-maker." - - "Treating AI explanations as technical documentation. Explanations for clinical AI must be written for clinicians, not engineers — using clinical terminology, citing clinical reasoning, and relating to the specific patient context." - healthtech_example: "A clinical AI radiology tool is redesigned using human-centered principles. Instead of presenting a diagnosis, the tool highlights regions of interest in the image, provides a confidence score with clinical context ('85% probability of malignancy based on lesion characteristics consistent with [clinical criteria]'), and offers the radiologist the option to accept, modify, or reject the assessment. The tool also presents relevant comparison cases from its training data. This design respects the radiologist's expertise while providing AI-augmented decision support that improves diagnostic accuracy by 15% in a prospective study." - benchmark_references: ["provider-nps", "provider-adoption-rate", "clinical-evidence-strength"] + - "Designing AI that bypasses the clinician. Autonomous AI clinical + decision-making without clinician oversight is neither regulatorily + permissible (for most clinical applications) nor clinically safe. The + clinician must remain the decision-maker." + - "Treating AI explanations as technical documentation. Explanations for + clinical AI must be written for clinicians, not engineers — using + clinical terminology, citing clinical reasoning, and relating to the + specific patient context." + healthtech_example: "A clinical AI radiology tool is redesigned using + human-centered principles. Instead of presenting a diagnosis, the tool + highlights regions of interest in the image, provides a confidence score + with clinical context ('85% probability of malignancy based on lesion + characteristics consistent with [clinical criteria]'), and offers the + radiologist the option to accept, modify, or reject the assessment. The + tool also presents relevant comparison cases from its training data. This + design respects the radiologist's expertise while providing AI-augmented + decision support that improves diagnostic accuracy by 15% in a prospective + study." + benchmark_references: [ "provider-nps", "provider-adoption-rate", "clinical-evidence-strength" ] - skill: "ai-stakeholder-balance" category: "ai-leadership" healthtech_relevance: "high" - healthtech_context: "AI stakeholder balance in healthtech requires managing the competing interests of patients (who want accurate, fair, and private AI), providers (who want reliable, explainable, and non-disruptive AI), health systems (who want cost-effective, interoperable AI), payers (who want evidence-based, cost-reducing AI), regulators (who want safe, transparent, and well-monitored AI), and the company's investors (who want scalable, high-margin AI). These interests frequently conflict: investor pressure for rapid scaling conflicts with the clinical evidence timeline required by regulators. Provider desire for explainability conflicts with the complexity of deep learning models. Patient privacy requirements conflict with the data volume needed for model improvement." + healthtech_context: "AI stakeholder balance in healthtech requires managing the + competing interests of patients (who want accurate, fair, and private AI), + providers (who want reliable, explainable, and non-disruptive AI), health + systems (who want cost-effective, interoperable AI), payers (who want + evidence-based, cost-reducing AI), regulators (who want safe, transparent, + and well-monitored AI), and the company's investors (who want scalable, + high-margin AI). These interests frequently conflict: investor pressure + for rapid scaling conflicts with the clinical evidence timeline required + by regulators. Provider desire for explainability conflicts with the + complexity of deep learning models. Patient privacy requirements conflict + with the data volume needed for model improvement." healthtech_anti_patterns: - - "Prioritizing investor scalability demands over regulatory safety requirements. Scaling an AI clinical tool before adequate safety monitoring is in place creates patient risk and regulatory risk simultaneously." - - "Satisfying provider explainability demands by oversimplifying the AI's reasoning. Explanations must be accurate as well as accessible — a simplified explanation that misrepresents the AI's actual reasoning process is misleading." - healthtech_example: "A clinical AI company creates a stakeholder balance map for its diagnostic AI: Patient interest — equitable accuracy across demographics (requires bias audits). Provider interest — explainable recommendations (requires interpretability layer). Health system interest — EHR integration and workflow compatibility (requires SMART on FHIR architecture). Payer interest — published cost-effectiveness data (requires health economic study). Regulator interest — predetermined change control plan and post-market surveillance (requires regulatory infrastructure). Investor interest — capital-efficient scaling (requires automated deployment and monitoring). The map reveals that the regulatory and clinical evidence requirements must be satisfied first because they enable all other stakeholder interests." - benchmark_references: ["clinical-evidence-strength", "regulatory-approval-status", "provider-adoption-rate"] + - "Prioritizing investor scalability demands over regulatory safety + requirements. Scaling an AI clinical tool before adequate safety + monitoring is in place creates patient risk and regulatory risk + simultaneously." + - "Satisfying provider explainability demands by oversimplifying the AI's + reasoning. Explanations must be accurate as well as accessible — a + simplified explanation that misrepresents the AI's actual reasoning + process is misleading." + healthtech_example: "A clinical AI company creates a stakeholder balance map for + its diagnostic AI: Patient interest — equitable accuracy across + demographics (requires bias audits). Provider interest — explainable + recommendations (requires interpretability layer). Health system interest + — EHR integration and workflow compatibility (requires SMART on FHIR + architecture). Payer interest — published cost-effectiveness data + (requires health economic study). Regulator interest — predetermined + change control plan and post-market surveillance (requires regulatory + infrastructure). Investor interest — capital-efficient scaling (requires + automated deployment and monitoring). The map reveals that the regulatory + and clinical evidence requirements must be satisfied first because they + enable all other stakeholder interests." + benchmark_references: + [ + "clinical-evidence-strength", + "regulatory-approval-status", + "provider-adoption-rate" + ] # ───────────────────────────────────────────── # THINKING & DECISIONS (2 skills) @@ -418,19 +1442,64 @@ skill_overlays: - skill: "defining-and-exploring-problems" category: "thinking" healthtech_relevance: "high" - healthtech_context: "Problem definition in healthtech must begin with the clinical problem, not the technology solution. The most common healthtech failure mode is building a technically impressive product that solves a problem clinicians do not consider important or that creates more burden than it eliminates. Problem exploration must involve clinicians (who understand the clinical workflow), patients (who experience the health condition), and payers (who fund the intervention). The problem definition must pass the 'triple aim test': does solving this problem improve patient outcomes, improve patient/provider experience, and reduce cost? Problems that satisfy only one or two of the triple aim have limited commercial viability in healthcare." + healthtech_context: "Problem definition in healthtech must begin with the + clinical problem, not the technology solution. The most common healthtech + failure mode is building a technically impressive product that solves a + problem clinicians do not consider important or that creates more burden + than it eliminates. Problem exploration must involve clinicians (who + understand the clinical workflow), patients (who experience the health + condition), and payers (who fund the intervention). The problem definition + must pass the 'triple aim test': does solving this problem improve patient + outcomes, improve patient/provider experience, and reduce cost? Problems + that satisfy only one or two of the triple aim have limited commercial + viability in healthcare." healthtech_anti_patterns: - - "Starting with the technology and searching for a clinical problem to solve. Technology-first problem definition leads to products that demonstrate technical capability without clinical utility." - - "Defining the problem based on clinician interviews alone without observing actual clinical workflow. What clinicians say they need and what clinical observation reveals they need are often different." - healthtech_example: "A healthtech startup redefines its problem statement after clinical workflow observation. The original problem: 'Clinicians need better diagnostic AI.' After observing 50 clinical encounters, the revised problem: 'Primary care physicians spend 18 minutes per patient encounter on documentation, leaving 7 minutes for clinical assessment — the documentation burden, not diagnostic capability, is the constraint on care quality.' The product pivots from diagnostic AI to ambient clinical documentation, which generates significantly more provider enthusiasm and a clearer reimbursement pathway." - benchmark_references: ["provider-adoption-rate", "provider-nps"] + - "Starting with the technology and searching for a clinical problem to + solve. Technology-first problem definition leads to products that + demonstrate technical capability without clinical utility." + - "Defining the problem based on clinician interviews alone without + observing actual clinical workflow. What clinicians say they need and + what clinical observation reveals they need are often different." + healthtech_example: "A healthtech startup redefines its problem statement after + clinical workflow observation. The original problem: 'Clinicians need + better diagnostic AI.' After observing 50 clinical encounters, the revised + problem: 'Primary care physicians spend 18 minutes per patient encounter + on documentation, leaving 7 minutes for clinical assessment — the + documentation burden, not diagnostic capability, is the constraint on care + quality.' The product pivots from diagnostic AI to ambient clinical + documentation, which generates significantly more provider enthusiasm and + a clearer reimbursement pathway." + benchmark_references: [ "provider-adoption-rate", "provider-nps" ] - skill: "evaluating-and-deciding" category: "thinking" healthtech_relevance: "high" - healthtech_context: "Evaluation and decision-making in healthtech must incorporate clinical risk as a first-class dimension alongside financial and operational considerations. Every decision framework should include the question: 'If this decision leads to the worst plausible clinical outcome, what happens to patients?' This is not paranoia — it is the clinical version of pre-mortem analysis. Decisions that create even a small probability of patient harm require more rigorous evaluation than those with purely financial consequences. The evaluation framework should also weight irreversibility: clinical product changes that affect patient care are harder to reverse than pricing or marketing changes." + healthtech_context: "Evaluation and decision-making in healthtech must + incorporate clinical risk as a first-class dimension alongside financial + and operational considerations. Every decision framework should include + the question: 'If this decision leads to the worst plausible clinical + outcome, what happens to patients?' This is not paranoia — it is the + clinical version of pre-mortem analysis. Decisions that create even a + small probability of patient harm require more rigorous evaluation than + those with purely financial consequences. The evaluation framework should + also weight irreversibility: clinical product changes that affect patient + care are harder to reverse than pricing or marketing changes." healthtech_anti_patterns: - - "Applying purely financial decision criteria to decisions with clinical implications. A cost-benefit analysis that shows a positive ROI for shipping a product faster should not override clinical safety concerns about the accelerated timeline." - - "Using consumer technology decision-making speed for clinical product decisions. The 'ship it and iterate' approach is appropriate for engagement features but not for clinical decision support algorithms." - healthtech_example: "A healthtech company evaluates whether to expand its clinical AI into a new therapeutic area. The evaluation framework includes four dimensions: Clinical (is there sufficient evidence that AI improves outcomes in this area?), Regulatory (what pathway is required and what is the timeline?), Reimbursement (do billing codes exist and will payers cover it?), and Safety (what is the worst plausible clinical outcome if the AI performs poorly?). The Safety dimension reveals that errors in the proposed therapeutic area (oncology) carry higher consequence than the current area (dermatology) — the evaluation triggers a more rigorous clinical validation plan before market entry." - benchmark_references: ["clinical-validation-stage", "regulatory-approval-status"] + - "Applying purely financial decision criteria to decisions with clinical + implications. A cost-benefit analysis that shows a positive ROI for + shipping a product faster should not override clinical safety concerns + about the accelerated timeline." + - "Using consumer technology decision-making speed for clinical product + decisions. The 'ship it and iterate' approach is appropriate for + engagement features but not for clinical decision support algorithms." + healthtech_example: "A healthtech company evaluates whether to expand its + clinical AI into a new therapeutic area. The evaluation framework includes + four dimensions: Clinical (is there sufficient evidence that AI improves + outcomes in this area?), Regulatory (what pathway is required and what is + the timeline?), Reimbursement (do billing codes exist and will payers + cover it?), and Safety (what is the worst plausible clinical outcome if + the AI performs poorly?). The Safety dimension reveals that errors in the + proposed therapeutic area (oncology) carry higher consequence than the + current area (dermatology) — the evaluation triggers a more rigorous + clinical validation plan before market entry." + benchmark_references: [ "clinical-validation-stage", "regulatory-approval-status" ] diff --git a/.claude/industry-packs/saas/saas-benchmarks.yaml b/.claude/industry-packs/saas/saas-benchmarks.yaml index 72aa984..c2c1591 100644 --- a/.claude/industry-packs/saas/saas-benchmarks.yaml +++ b/.claude/industry-packs/saas/saas-benchmarks.yaml @@ -23,7 +23,8 @@ pack_metadata: sector: "saas" display_name: "SaaS" version: "1.0.0" - description: "Benchmark data for Software-as-a-Service companies spanning growth, retention, unit economics, efficiency, and sales metrics." + description: "Benchmark data for Software-as-a-Service companies spanning + growth, retention, unit economics, efficiency, and sales metrics." author: "Fatih Guner" last_updated: "2026-03-26" @@ -40,110 +41,143 @@ benchmarks: - name: "Monthly Recurring Revenue (MRR)" id: "mrr" category: "growth" - definition: "The predictable, normalized monthly revenue from all active subscriptions, excluding one-time fees and variable usage overages." - formula: "Sum of (monthly subscription price x active subscribers) for each plan tier" + definition: "The predictable, normalized monthly revenue from all active + subscriptions, excluding one-time fees and variable usage overages." + formula: "Sum of (monthly subscription price x active subscribers) for each plan + tier" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $10K MRR at 12 months post-launch" - signal: "Insufficient product-market fit or distribution to sustain the business. Runway consumption outpaces revenue generation." + signal: "Insufficient product-market fit or distribution to sustain the + business. Runway consumption outpaces revenue generation." below_average: value: "$10K-$50K MRR at 12 months" - signal: "Early traction but not yet at a level that demonstrates scalable demand." + signal: "Early traction but not yet at a level that demonstrates scalable + demand." average: value: "$50K-$150K MRR at 12 months" - signal: "Solid initial traction. Enough signal to raise a seed or Series A if growth rate is strong." + signal: "Solid initial traction. Enough signal to raise a seed or Series A if + growth rate is strong." good: value: "$150K-$500K MRR at 12 months" - signal: "Strong product-market fit. Revenue supports hiring a small team and investing in growth." + signal: "Strong product-market fit. Revenue supports hiring a small team and + investing in growth." excellent: value: "> $500K MRR at 12 months" - signal: "Exceptional traction. Rare at this stage — indicates viral adoption or enterprise deal velocity." + signal: "Exceptional traction. Rare at this stage — indicates viral adoption or + enterprise deal velocity." stage_notes: - seed: "Absolute MRR matters less than trajectory. Investors look for $10K-$50K MRR with 15%+ MoM growth." - series_a: "Typical Series A threshold has risen to $1M-$2M ARR ($83K-$167K MRR). The bar is higher in 2024-2026 than in 2021." - series_b_plus: "Series B companies typically show $5M-$15M ARR. MRR is less discussed — ARR becomes the standard unit." + seed: "Absolute MRR matters less than trajectory. Investors look for $10K-$50K + MRR with 15%+ MoM growth." + series_a: "Typical Series A threshold has risen to $1M-$2M ARR ($83K-$167K MRR). + The bar is higher in 2024-2026 than in 2021." + series_b_plus: "Series B companies typically show $5M-$15M ARR. MRR is less + discussed — ARR becomes the standard unit." data_sources: - source: "OpenView SaaS Benchmarks" year: "2024" - source: "SaaStr Series A Benchmarks" year: "2024" - related_metrics: ["arr", "mom-growth-rate"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "MRR must exclude implementation fees, professional services, and one-time charges. Blending these inflates the metric and misleads investors." + related_metrics: [ "arr", "mom-growth-rate" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "MRR must exclude implementation fees, professional services, and + one-time charges. Blending these inflates the metric and misleads + investors." - name: "Annual Recurring Revenue (ARR)" id: "arr" category: "growth" - definition: "The annualized value of all active recurring subscription contracts, representing the run-rate revenue the business would generate over twelve months at its current scale." - formula: "MRR x 12 (or sum of annualized contract values for annual/multi-year deals)" + definition: "The annualized value of all active recurring subscription + contracts, representing the run-rate revenue the business would generate + over twelve months at its current scale." + formula: "MRR x 12 (or sum of annualized contract values for annual/multi-year + deals)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $500K ARR at Series A" - signal: "Below the threshold most institutional investors require. The company may be pre-product-market-fit." + signal: "Below the threshold most institutional investors require. The company + may be pre-product-market-fit." below_average: value: "$500K-$1M ARR at Series A" - signal: "Borderline for fundraising. Acceptable only with exceptional growth rate (3x+ YoY) and strong retention." + signal: "Borderline for fundraising. Acceptable only with exceptional growth + rate (3x+ YoY) and strong retention." average: value: "$1M-$3M ARR at Series A" - signal: "The current median range for Series A SaaS companies. Sufficient if paired with 2x+ YoY growth." + signal: "The current median range for Series A SaaS companies. Sufficient if + paired with 2x+ YoY growth." good: value: "$3M-$10M ARR at Series A" - signal: "Strong position. Multiple investor options. Demonstrates repeatable sales motion." + signal: "Strong position. Multiple investor options. Demonstrates repeatable + sales motion." excellent: value: "> $10M ARR at Series A" - signal: "Rare and powerful. Often indicates a capital-efficient business that delayed fundraising or a breakout product." + signal: "Rare and powerful. Often indicates a capital-efficient business that + delayed fundraising or a breakout product." stage_notes: - seed: "ARR is often premature at seed. Investors focus on MRR trajectory and qualitative PMF signals." - series_a: "Median Series A ARR has increased from ~$1M (2020) to ~$1.5M-$2.5M (2024-2025) as markets tightened." - series_b_plus: "Series B typically requires $5M-$20M ARR. Series C: $20M-$50M+. Growth rate expectations decrease as ARR scales." + seed: "ARR is often premature at seed. Investors focus on MRR trajectory and + qualitative PMF signals." + series_a: "Median Series A ARR has increased from ~$1M (2020) to ~$1.5M-$2.5M + (2024-2025) as markets tightened." + series_b_plus: "Series B typically requires $5M-$20M ARR. Series C: $20M-$50M+. + Growth rate expectations decrease as ARR scales." data_sources: - source: "Bessemer State of the Cloud" year: "2024" - source: "Iconiq Growth" year: "2023" - related_metrics: ["mrr", "mom-growth-rate"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "ARR is a forward-looking metric, not GAAP revenue. Companies with high churn may report ARR that significantly exceeds actual realized revenue." + related_metrics: [ "mrr", "mom-growth-rate" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "ARR is a forward-looking metric, not GAAP revenue. Companies with high + churn may report ARR that significantly exceeds actual realized revenue." - name: "Month-over-Month Growth Rate" id: "mom-growth-rate" category: "growth" - definition: "The percentage increase in MRR from one month to the next, measuring the velocity of recurring revenue acquisition." + definition: "The percentage increase in MRR from one month to the next, + measuring the velocity of recurring revenue acquisition." formula: "(MRR_current - MRR_previous) / MRR_previous x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 5% MoM" - signal: "Growth is stalling or the business is approaching a plateau. At early stage, this rate is too slow to reach meaningful scale." + signal: "Growth is stalling or the business is approaching a plateau. At early + stage, this rate is too slow to reach meaningful scale." below_average: value: "5-10% MoM" - signal: "Moderate growth. Sustainable but unlikely to attract venture investment at seed or Series A." + signal: "Moderate growth. Sustainable but unlikely to attract venture investment + at seed or Series A." average: value: "10-15% MoM" signal: "Healthy early-stage growth. At 15% MoM, MRR doubles every ~5 months." good: value: "15-25% MoM" - signal: "Strong traction. At 20% MoM, a $10K MRR company reaches $100K MRR in roughly 12 months." + signal: "Strong traction. At 20% MoM, a $10K MRR company reaches $100K MRR in + roughly 12 months." excellent: value: "> 25% MoM" - signal: "Exceptional, typically unsustainable beyond a few months. Often coincides with viral adoption or a major enterprise win." + signal: "Exceptional, typically unsustainable beyond a few months. Often + coincides with viral adoption or a major enterprise win." stage_notes: - seed: "15-25% MoM expected from small base. The compounding effect matters more than the percentage once base grows." - series_a: "MoM growth naturally decelerates. 8-15% MoM at $1M+ ARR is strong. The absolute dollar growth matters more." - series_b_plus: "MoM becomes less meaningful. YoY growth rate (2x-3x) is the standard measure at scale." + seed: "15-25% MoM expected from small base. The compounding effect matters more + than the percentage once base grows." + series_a: "MoM growth naturally decelerates. 8-15% MoM at $1M+ ARR is strong. + The absolute dollar growth matters more." + series_b_plus: "MoM becomes less meaningful. YoY growth rate (2x-3x) is the + standard measure at scale." data_sources: - source: "OpenView SaaS Benchmarks" year: "2023" - source: "Y Combinator Startup School benchmarks" year: "2024" - related_metrics: ["mrr", "arr"] - related_skills: ["growth-share-matrix", "product-life-cycle"] - caveats: "MoM rates are noisy at low MRR. A single enterprise deal can create a misleading spike. Use 3-month rolling average for stability." + related_metrics: [ "mrr", "arr" ] + related_skills: [ "growth-share-matrix", "product-life-cycle" ] + caveats: "MoM rates are noisy at low MRR. A single enterprise deal can create a + misleading spike. Use 3-month rolling average for stability." # ───────────────────────────────────────────── # RETENTION METRICS @@ -152,146 +186,197 @@ benchmarks: - name: "Net Revenue Retention (NRR)" id: "nrr" category: "retention" - definition: "The percentage of recurring revenue retained from existing customers after accounting for expansion, contraction, and churn — the single most important SaaS health metric." - formula: "(Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / Starting MRR x 100" + definition: "The percentage of recurring revenue retained from existing + customers after accounting for expansion, contraction, and churn — the + single most important SaaS health metric." + formula: "(Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / + Starting MRR x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 90%" - signal: "The business is shrinking from its existing customer base. New sales merely replace lost revenue — a leaky bucket with no leverage." + signal: "The business is shrinking from its existing customer base. New sales + merely replace lost revenue — a leaky bucket with no leverage." below_average: value: "90-100%" - signal: "Slight net contraction or break-even on existing customers. Expansion revenue is insufficient to offset churn." + signal: "Slight net contraction or break-even on existing customers. Expansion + revenue is insufficient to offset churn." average: value: "100-110%" - signal: "Modest net expansion. The existing customer base is growing slowly without additional sales effort." + signal: "Modest net expansion. The existing customer base is growing slowly + without additional sales effort." good: value: "110-130%" - signal: "Strong expansion dynamics. Each cohort grows over time. This is the range most public SaaS companies achieve." + signal: "Strong expansion dynamics. Each cohort grows over time. This is the + range most public SaaS companies achieve." excellent: value: "> 130%" - signal: "Exceptional. Companies like Snowflake, Datadog, and Twilio at their peaks. Indicates strong usage-based or land-and-expand motion." + signal: "Exceptional. Companies like Snowflake, Datadog, and Twilio at their + peaks. Indicates strong usage-based or land-and-expand motion." stage_notes: - seed: "NRR is often unmeasurable with few customers. Focus on qualitative retention signals: do customers actively use the product and request more?" - series_a: "NRR above 100% is a strong Series A signal. Above 120% is exceptional and demonstrates expansion revenue motion." - series_b_plus: "Public market investors heavily weight NRR. Best-in-class public SaaS companies cluster at 120-140%." + seed: "NRR is often unmeasurable with few customers. Focus on qualitative + retention signals: do customers actively use the product and request + more?" + series_a: "NRR above 100% is a strong Series A signal. Above 120% is exceptional + and demonstrates expansion revenue motion." + series_b_plus: "Public market investors heavily weight NRR. Best-in-class public + SaaS companies cluster at 120-140%." data_sources: - source: "KeyBanc SaaS Survey" year: "2024" - source: "Bessemer Cloud Index" year: "2024" - related_metrics: ["grr", "ndr", "revenue-churn", "expansion-revenue-pct"] - related_skills: ["net-promoter-score", "balanced-scorecard"] - caveats: "NRR can mask underlying problems. A company with 40% logo churn and 50% expansion from survivors still shows >100% NRR but has a fundamentally unhealthy business." + related_metrics: [ "grr", "ndr", "revenue-churn", "expansion-revenue-pct" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "NRR can mask underlying problems. A company with 40% logo churn and + 50% expansion from survivors still shows >100% NRR but has a fundamentally + unhealthy business." - name: "Gross Revenue Retention (GRR)" id: "grr" category: "retention" - definition: "The percentage of recurring revenue retained from existing customers excluding any expansion — measuring pure retention before upsell compensates for losses." + definition: "The percentage of recurring revenue retained from existing + customers excluding any expansion — measuring pure retention before upsell + compensates for losses." formula: "(Starting MRR - Contraction MRR - Churned MRR) / Starting MRR x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 80%" - signal: "Losing more than 20% of cohort revenue annually. The product is failing to deliver sustained value, or pricing is misaligned." + signal: "Losing more than 20% of cohort revenue annually. The product is failing + to deliver sustained value, or pricing is misaligned." below_average: value: "80-85%" - signal: "Meaningful revenue erosion. Acceptable only at very early stages with rapid iteration and small cohorts." + signal: "Meaningful revenue erosion. Acceptable only at very early stages with + rapid iteration and small cohorts." average: value: "85-90%" - signal: "Typical for SMB-focused SaaS. Small businesses churn at higher rates due to failure, budget cuts, and switching costs." + signal: "Typical for SMB-focused SaaS. Small businesses churn at higher rates + due to failure, budget cuts, and switching costs." good: value: "90-95%" - signal: "Strong retention. Indicates sticky product with real workflow integration and switching costs." + signal: "Strong retention. Indicates sticky product with real workflow + integration and switching costs." excellent: value: "> 95%" - signal: "Enterprise-grade retention. Common in mission-critical infrastructure software. Very difficult to achieve in SMB." + signal: "Enterprise-grade retention. Common in mission-critical infrastructure + software. Very difficult to achieve in SMB." stage_notes: - seed: "GRR data is sparse. Even 80% GRR with rapid learning and iteration is acceptable." - series_a: "Investors increasingly scrutinize GRR alongside NRR. GRR below 85% raises questions about product-market fit durability." - series_b_plus: "Public SaaS median GRR is ~90%. Best-in-class enterprise companies (ServiceNow, Workday) exceed 95%." + seed: "GRR data is sparse. Even 80% GRR with rapid learning and iteration is + acceptable." + series_a: "Investors increasingly scrutinize GRR alongside NRR. GRR below 85% + raises questions about product-market fit durability." + series_b_plus: "Public SaaS median GRR is ~90%. Best-in-class enterprise + companies (ServiceNow, Workday) exceed 95%." data_sources: - source: "KeyBanc SaaS Survey" year: "2024" - source: "Paddle/ProfitWell SaaS Benchmarks" year: "2023" - related_metrics: ["nrr", "logo-churn", "revenue-churn"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "GRR is capped at 100%. It cannot exceed 100% because it excludes expansion. This is by design — it isolates the pure retention question." + related_metrics: [ "nrr", "logo-churn", "revenue-churn" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "GRR is capped at 100%. It cannot exceed 100% because it excludes + expansion. This is by design — it isolates the pure retention question." - name: "Logo Churn" id: "logo-churn" category: "retention" - definition: "The percentage of customers (logos) lost in a given period, regardless of their revenue contribution." + definition: "The percentage of customers (logos) lost in a given period, + regardless of their revenue contribution." formula: "Customers lost in period / Customers at start of period x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 7% monthly (> 58% annual)" - signal: "More than half the customer base turns over each year. The product is either not delivering value or targeting the wrong segment." + signal: "More than half the customer base turns over each year. The product is + either not delivering value or targeting the wrong segment." below_average: value: "4-7% monthly (38-58% annual)" - signal: "High churn typical of freemium-to-paid conversion or very low-ACV products without strong retention hooks." + signal: "High churn typical of freemium-to-paid conversion or very low-ACV + products without strong retention hooks." average: value: "2-4% monthly (22-38% annual)" - signal: "Common for SMB SaaS. Each customer requires low touch, but the base requires constant replenishment." + signal: "Common for SMB SaaS. Each customer requires low touch, but the base + requires constant replenishment." good: value: "1-2% monthly (11-22% annual)" - signal: "Healthy retention. Product has meaningful switching costs and delivers ongoing value." + signal: "Healthy retention. Product has meaningful switching costs and delivers + ongoing value." excellent: value: "< 1% monthly (< 11% annual)" - signal: "Best-in-class. Typically enterprise or mission-critical products with deep integration and multi-year contracts." + signal: "Best-in-class. Typically enterprise or mission-critical products with + deep integration and multi-year contracts." stage_notes: - seed: "Logo churn is often high and erratic with a small customer base. A single departure can move the rate dramatically." - series_a: "Investors expect monthly logo churn under 3-5% for SMB, under 1-2% for mid-market, under 0.5% for enterprise." - series_b_plus: "Annual logo churn above 15% at scale is a red flag regardless of NRR performance." + seed: "Logo churn is often high and erratic with a small customer base. A single + departure can move the rate dramatically." + series_a: "Investors expect monthly logo churn under 3-5% for SMB, under 1-2% + for mid-market, under 0.5% for enterprise." + series_b_plus: "Annual logo churn above 15% at scale is a red flag regardless of + NRR performance." data_sources: - source: "Paddle/ProfitWell Churn Benchmarks" year: "2024" - source: "Recurly Research / Subscription Economy Index" year: "2023" - related_metrics: ["revenue-churn", "grr", "nrr"] - related_skills: ["net-promoter-score", "customer-churn-diagnosis"] - caveats: "Logo churn should be segmented by customer size. Losing 100 $50/month customers is different from losing 1 $60K/year customer. Revenue churn provides the complementary view." + related_metrics: [ "revenue-churn", "grr", "nrr" ] + related_skills: + - net-promoter-score + caveats: "Logo churn should be segmented by customer size. Losing 100 $50/month + customers is different from losing 1 $60K/year customer. Revenue churn + provides the complementary view." + related_content: + - kind: diagnostic + ref: customer-churn-diagnosis - name: "Revenue Churn" id: "revenue-churn" category: "retention" - definition: "The percentage of MRR lost from existing customers due to cancellations and downgrades in a given period." + definition: "The percentage of MRR lost from existing customers due to + cancellations and downgrades in a given period." formula: "(Churned MRR + Contraction MRR) / Starting MRR x 100" unit: "percentage" direction: "lower-is-better" benchmarks: poor: value: "> 5% monthly gross revenue churn" - signal: "Losing more than half of starting MRR annually through the existing base. Unsustainable without extraordinary new sales." + signal: "Losing more than half of starting MRR annually through the existing + base. Unsustainable without extraordinary new sales." below_average: value: "3-5% monthly" - signal: "High revenue erosion. Growth requires aggressive new customer acquisition just to stay flat." + signal: "High revenue erosion. Growth requires aggressive new customer + acquisition just to stay flat." average: value: "1.5-3% monthly" - signal: "Common for SMB SaaS. Manageable but requires healthy sales pipeline to grow." + signal: "Common for SMB SaaS. Manageable but requires healthy sales pipeline to + grow." good: value: "0.5-1.5% monthly" - signal: "Solid retention floor. The business can grow efficiently because the base is stable." + signal: "Solid retention floor. The business can grow efficiently because the + base is stable." excellent: value: "< 0.5% monthly" - signal: "Near-zero revenue loss. Enterprise-grade stickiness. The base becomes a compounding asset." + signal: "Near-zero revenue loss. Enterprise-grade stickiness. The base becomes a + compounding asset." stage_notes: - seed: "Revenue churn is lumpy at small scale. Track it but do not over-optimize — focus on understanding why customers leave." - series_a: "Investors expect gross monthly revenue churn under 2% for healthy businesses. Below 1% is exceptional." - series_b_plus: "At scale, even small revenue churn percentages represent large absolute dollars. Net revenue churn (including expansion) matters more." + seed: "Revenue churn is lumpy at small scale. Track it but do not over-optimize + — focus on understanding why customers leave." + series_a: "Investors expect gross monthly revenue churn under 2% for healthy + businesses. Below 1% is exceptional." + series_b_plus: "At scale, even small revenue churn percentages represent large + absolute dollars. Net revenue churn (including expansion) matters more." data_sources: - source: "Paddle/ProfitWell SaaS Index" year: "2024" - source: "Baremetrics Open Benchmarks" year: "2023" - related_metrics: ["logo-churn", "grr", "nrr"] - related_skills: ["net-promoter-score", "balanced-scorecard"] - caveats: "Revenue churn can be negative when expansion exceeds losses. Negative net revenue churn is the gold standard but should be reported as NRR, not as a negative churn rate, to avoid confusion." + related_metrics: [ "logo-churn", "grr", "nrr" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "Revenue churn can be negative when expansion exceeds losses. Negative + net revenue churn is the gold standard but should be reported as NRR, not + as a negative churn rate, to avoid confusion." # ───────────────────────────────────────────── # UNIT ECONOMICS METRICS @@ -300,182 +385,244 @@ benchmarks: - name: "Customer Acquisition Cost (CAC)" id: "cac" category: "unit-economics" - definition: "The fully loaded cost to acquire one new customer, including all sales and marketing expense." - formula: "Total Sales & Marketing Spend in period / New Customers Acquired in period" + definition: "The fully loaded cost to acquire one new customer, including all + sales and marketing expense." + formula: "Total Sales & Marketing Spend in period / New Customers Acquired in + period" unit: "currency" direction: "lower-is-better" benchmarks: poor: - value: "CAC > 18 months of revenue from that customer (i.e., CAC Payback > 18 months)" - signal: "Acquisition economics are unsustainable. The business burns cash on every new customer and depends on very long retention to break even." + value: "CAC > 18 months of revenue from that customer (i.e., CAC Payback > 18 + months)" + signal: "Acquisition economics are unsustainable. The business burns cash on + every new customer and depends on very long retention to break even." below_average: value: "CAC Payback 12-18 months" - signal: "Expensive acquisition. Viable for enterprise SaaS with high retention but dangerous for SMB products." + signal: "Expensive acquisition. Viable for enterprise SaaS with high retention + but dangerous for SMB products." average: value: "CAC Payback 6-12 months" - signal: "Typical for B2B SaaS. Requires at least 3+ years of customer lifetime to generate healthy returns." + signal: "Typical for B2B SaaS. Requires at least 3+ years of customer lifetime + to generate healthy returns." good: value: "CAC Payback 3-6 months" - signal: "Efficient acquisition. The business can reinvest in growth aggressively because customers pay for themselves quickly." + signal: "Efficient acquisition. The business can reinvest in growth aggressively + because customers pay for themselves quickly." excellent: value: "CAC Payback < 3 months" - signal: "Exceptional efficiency. Often indicates strong word-of-mouth, viral loops, or product-led growth motion." + signal: "Exceptional efficiency. Often indicates strong word-of-mouth, viral + loops, or product-led growth motion." stage_notes: - seed: "CAC is often distorted — founders do the selling, and their time may not be fully costed. Be honest about true CAC." - series_a: "Blended CAC should be calculable. Investors want to see CAC by channel and understand which channels are scalable." - series_b_plus: "CAC should be measured by segment (SMB vs. mid-market vs. enterprise), by channel, and by cohort vintage." + seed: "CAC is often distorted — founders do the selling, and their time may not + be fully costed. Be honest about true CAC." + series_a: "Blended CAC should be calculable. Investors want to see CAC by + channel and understand which channels are scalable." + series_b_plus: "CAC should be measured by segment (SMB vs. mid-market vs. + enterprise), by channel, and by cohort vintage." data_sources: - source: "OpenView SaaS Benchmarks" year: "2024" - source: "KeyBanc SaaS Survey" year: "2024" - related_metrics: ["ltv", "ltv-cac-ratio", "cac-payback-period"] - related_skills: ["four-ps-marketing", "business-model-canvas"] - caveats: "CAC must be fully loaded: salaries, commissions, marketing spend, tooling, content production, events. Under-counting CAC is the most common SaaS accounting mistake." + related_metrics: [ "ltv", "ltv-cac-ratio", "cac-payback-period" ] + related_skills: [ "four-ps-marketing", "business-model-canvas" ] + caveats: "CAC must be fully loaded: salaries, commissions, marketing spend, + tooling, content production, events. Under-counting CAC is the most common + SaaS accounting mistake." - name: "Customer Lifetime Value (LTV)" id: "ltv" category: "unit-economics" - definition: "The total gross profit a customer generates over their entire relationship with the company." - formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross Margin % x Average Customer Lifetime in months)" + definition: "The total gross profit a customer generates over their entire + relationship with the company." + formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross + Margin % x Average Customer Lifetime in months)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "LTV < 1x CAC" - signal: "The business loses money on every customer it acquires. Without fundamental unit economics improvement, growth accelerates losses." + signal: "The business loses money on every customer it acquires. Without + fundamental unit economics improvement, growth accelerates losses." below_average: value: "LTV 1-2x CAC" - signal: "Marginal economics. Barely profitable per customer after acquisition costs. Leaves no room for operational overhead." + signal: "Marginal economics. Barely profitable per customer after acquisition + costs. Leaves no room for operational overhead." average: value: "LTV 2-3x CAC" - signal: "Approaching viability. Sufficient if growth is modest, but tight margins constrain investment in product and expansion." + signal: "Approaching viability. Sufficient if growth is modest, but tight + margins constrain investment in product and expansion." good: value: "LTV 3-5x CAC" - signal: "Healthy unit economics. The standard target for venture-backed SaaS. Enough margin to fund growth and R&D." + signal: "Healthy unit economics. The standard target for venture-backed SaaS. + Enough margin to fund growth and R&D." excellent: value: "LTV > 5x CAC" - signal: "Exceptional economics. The business can afford aggressive growth spending or generate significant free cash flow." + signal: "Exceptional economics. The business can afford aggressive growth + spending or generate significant free cash flow." stage_notes: - seed: "LTV is largely theoretical at seed — insufficient data for reliable lifetime estimates. Use conservative assumptions (24-month lifetime max)." - series_a: "LTV calculations become credible with 12-18 months of cohort data. Investors scrutinize the assumptions behind the number." - series_b_plus: "LTV should be segmented by customer tier and acquisition cohort. Blended LTV masks segment-level problems." + seed: "LTV is largely theoretical at seed — insufficient data for reliable + lifetime estimates. Use conservative assumptions (24-month lifetime + max)." + series_a: "LTV calculations become credible with 12-18 months of cohort data. + Investors scrutinize the assumptions behind the number." + series_b_plus: "LTV should be segmented by customer tier and acquisition cohort. + Blended LTV masks segment-level problems." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "Tomasz Tunguz / Theory Ventures analysis" year: "2023" - related_metrics: ["cac", "ltv-cac-ratio", "arpu", "revenue-churn"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "LTV estimates based on low churn assumptions can be wildly optimistic. A 1% monthly churn implies 100-month lifetime — most SaaS products do not retain customers that long." + related_metrics: [ "cac", "ltv-cac-ratio", "arpu", "revenue-churn" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "LTV estimates based on low churn assumptions can be wildly optimistic. + A 1% monthly churn implies 100-month lifetime — most SaaS products do not + retain customers that long." - name: "LTV:CAC Ratio" id: "ltv-cac-ratio" category: "unit-economics" - definition: "The ratio of customer lifetime value to customer acquisition cost, measuring the return on each dollar invested in acquisition." + definition: "The ratio of customer lifetime value to customer acquisition cost, + measuring the return on each dollar invested in acquisition." formula: "LTV / CAC" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 1.0x" - signal: "Value destruction. Every customer acquired costs more than they will ever generate. The business model is broken." + signal: "Value destruction. Every customer acquired costs more than they will + ever generate. The business model is broken." below_average: value: "1.0-2.0x" - signal: "Marginal. Customers barely cover their acquisition costs. No margin for error or overhead." + signal: "Marginal. Customers barely cover their acquisition costs. No margin for + error or overhead." average: value: "2.0-3.0x" - signal: "Below the standard target. Viable only with very low operational overhead or if LTV is underestimated due to early-stage data limitations." + signal: "Below the standard target. Viable only with very low operational + overhead or if LTV is underestimated due to early-stage data + limitations." good: value: "3.0-5.0x" - signal: "The accepted SaaS benchmark. Demonstrates a sustainable business where customer value significantly exceeds acquisition investment." + signal: "The accepted SaaS benchmark. Demonstrates a sustainable business where + customer value significantly exceeds acquisition investment." excellent: value: "> 5.0x" - signal: "Outstanding efficiency. Either the product sells itself (low CAC) or customers generate exceptional lifetime revenue (high LTV). May also indicate under-investment in growth." + signal: "Outstanding efficiency. Either the product sells itself (low CAC) or + customers generate exceptional lifetime revenue (high LTV). May also + indicate under-investment in growth." stage_notes: - seed: "At seed, LTV:CAC is an estimate. Investors look for directional signal, not precision." - series_a: "3x+ LTV:CAC is a standard Series A expectation. Below 3x requires a compelling narrative about improvement trajectory." - series_b_plus: "A ratio above 5x at scale may indicate the company is under-investing in growth and leaving market share on the table." + seed: "At seed, LTV:CAC is an estimate. Investors look for directional signal, + not precision." + series_a: "3x+ LTV:CAC is a standard Series A expectation. Below 3x requires a + compelling narrative about improvement trajectory." + series_b_plus: "A ratio above 5x at scale may indicate the company is + under-investing in growth and leaving market share on the table." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "SaaStr Benchmarks" year: "2024" - related_metrics: ["ltv", "cac", "cac-payback-period"] - related_skills: ["business-model-canvas", "scenario-planning"] - caveats: "LTV:CAC above 5x is not always good — it can signal under-investment. The optimal range for growth-stage companies is 3x-5x." + related_metrics: [ "ltv", "cac", "cac-payback-period" ] + related_skills: [ "business-model-canvas", "scenario-planning" ] + caveats: "LTV:CAC above 5x is not always good — it can signal under-investment. + The optimal range for growth-stage companies is 3x-5x." - name: "CAC Payback Period" id: "cac-payback-period" category: "unit-economics" - definition: "The number of months required for a customer's gross profit to repay the cost of acquiring them." + definition: "The number of months required for a customer's gross profit to + repay the cost of acquiring them." formula: "CAC / (ARPU x Gross Margin %)" unit: "months" direction: "lower-is-better" benchmarks: poor: value: "> 24 months" - signal: "Capital-intensive growth model. The business must fund more than two years of customer revenue before breaking even on acquisition." + signal: "Capital-intensive growth model. The business must fund more than two + years of customer revenue before breaking even on acquisition." below_average: value: "18-24 months" - signal: "Long payback. Acceptable for enterprise SaaS with >95% GRR. Dangerous for SMB with higher churn." + signal: "Long payback. Acceptable for enterprise SaaS with >95% GRR. Dangerous + for SMB with higher churn." average: value: "12-18 months" - signal: "Typical for B2B SaaS. Requires solid retention to generate meaningful lifetime profit." + signal: "Typical for B2B SaaS. Requires solid retention to generate meaningful + lifetime profit." good: value: "6-12 months" - signal: "Efficient. Most investors consider sub-12-month payback a strong signal. Allows faster reinvestment cycles." + signal: "Efficient. Most investors consider sub-12-month payback a strong + signal. Allows faster reinvestment cycles." excellent: value: "< 6 months" - signal: "Exceptional capital efficiency. The business self-funds its growth rapidly. Often seen in PLG or viral-coefficient products." + signal: "Exceptional capital efficiency. The business self-funds its growth + rapidly. Often seen in PLG or viral-coefficient products." stage_notes: - seed: "Payback period under 12 months is a powerful signal at seed. Over 18 months is a concern." - series_a: "Median payback for Series A companies is roughly 15-18 months. Top quartile is under 12 months." - series_b_plus: "Payback should be measured by segment. Enterprise may have longer payback but higher LTV; SMB should pay back in under 12 months." + seed: "Payback period under 12 months is a powerful signal at seed. Over 18 + months is a concern." + series_a: "Median payback for Series A companies is roughly 15-18 months. Top + quartile is under 12 months." + series_b_plus: "Payback should be measured by segment. Enterprise may have + longer payback but higher LTV; SMB should pay back in under 12 months." data_sources: - source: "OpenView SaaS Benchmarks" year: "2024" - source: "KeyBanc SaaS Survey" year: "2024" - related_metrics: ["cac", "ltv", "ltv-cac-ratio", "arpu", "gross-margin"] - related_skills: ["balanced-scorecard", "business-model-canvas"] - caveats: "Payback period is often quoted using revenue, not gross profit. The gross-margin-adjusted version is the correct calculation and typically 20-30% longer." + related_metrics: [ "cac", "ltv", "ltv-cac-ratio", "arpu", "gross-margin" ] + related_skills: [ "balanced-scorecard", "business-model-canvas" ] + caveats: "Payback period is often quoted using revenue, not gross profit. The + gross-margin-adjusted version is the correct calculation and typically + 20-30% longer." - name: "Gross Margin" id: "gross-margin" category: "unit-economics" - definition: "Revenue minus cost of goods sold as a percentage of revenue, measuring how much of each dollar of revenue is available to fund operations, growth, and profit." + definition: "Revenue minus cost of goods sold as a percentage of revenue, + measuring how much of each dollar of revenue is available to fund + operations, growth, and profit." formula: "(Revenue - COGS) / Revenue x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 60%" - signal: "Heavy services component or infrastructure costs eroding the software economics. This is a services business with a software wrapper, not true SaaS." + signal: "Heavy services component or infrastructure costs eroding the software + economics. This is a services business with a software wrapper, not + true SaaS." below_average: value: "60-70%" - signal: "Below SaaS norms. Common in companies with significant human-in-the-loop delivery, high hosting costs, or bundled implementation." + signal: "Below SaaS norms. Common in companies with significant + human-in-the-loop delivery, high hosting costs, or bundled + implementation." average: value: "70-75%" - signal: "Acceptable for SaaS, though on the lower end. Infrastructure-heavy products (data, AI/ML) often land here." + signal: "Acceptable for SaaS, though on the lower end. Infrastructure-heavy + products (data, AI/ML) often land here." good: value: "75-80%" signal: "Healthy SaaS margin. Demonstrates leverage in the delivery model." excellent: value: "> 80%" - signal: "Best-in-class software economics. The marginal cost of serving an additional customer is negligible. Public SaaS median is ~75%." + signal: "Best-in-class software economics. The marginal cost of serving an + additional customer is negligible. Public SaaS median is ~75%." stage_notes: - seed: "Gross margins may be artificially low (manual processes) or high (no support costs yet). Neither is representative." - series_a: "Investors expect a path to 70%+ gross margin even if current levels are lower due to early-stage inefficiency." - series_b_plus: "Gross margin should stabilize at 75-85%. Declining gross margins at scale are a serious concern." + seed: "Gross margins may be artificially low (manual processes) or high (no + support costs yet). Neither is representative." + series_a: "Investors expect a path to 70%+ gross margin even if current levels + are lower due to early-stage inefficiency." + series_b_plus: "Gross margin should stabilize at 75-85%. Declining gross margins + at scale are a serious concern." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "KeyBanc SaaS Survey" year: "2024" - related_metrics: ["cac-payback-period", "ltv", "burn-multiple"] - related_skills: ["business-model-canvas", "balanced-scorecard"] - caveats: "COGS for SaaS includes hosting/infrastructure, customer support, customer success (debated), and third-party data/API costs. Do not confuse gross margin with contribution margin." + related_metrics: [ "cac-payback-period", "ltv", "burn-multiple" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "COGS for SaaS includes hosting/infrastructure, customer support, + customer success (debated), and third-party data/API costs. Do not confuse + gross margin with contribution margin." # ───────────────────────────────────────────── # EFFICIENCY METRICS @@ -484,146 +631,193 @@ benchmarks: - name: "Burn Multiple" id: "burn-multiple" category: "efficiency" - definition: "The ratio of net cash burned to net new ARR generated, measuring how efficiently the company converts capital into recurring revenue growth." + definition: "The ratio of net cash burned to net new ARR generated, measuring + how efficiently the company converts capital into recurring revenue + growth." formula: "Net Burn / Net New ARR" unit: "multiple" direction: "lower-is-better" benchmarks: poor: value: "> 3.0x" - signal: "Burning more than $3 for every $1 of net new ARR. Capital-intensive growth that most investors will not fund in a disciplined market." + signal: "Burning more than $3 for every $1 of net new ARR. Capital-intensive + growth that most investors will not fund in a disciplined market." below_average: value: "2.0-3.0x" - signal: "Inefficient but potentially acceptable at very early stages with high growth rates." + signal: "Inefficient but potentially acceptable at very early stages with high + growth rates." average: value: "1.5-2.0x" - signal: "Typical for growth-stage SaaS. The company is investing aggressively but within a defensible range." + signal: "Typical for growth-stage SaaS. The company is investing aggressively + but within a defensible range." good: value: "1.0-1.5x" - signal: "Efficient growth. Each dollar burned produces a meaningful return in recurring revenue." + signal: "Efficient growth. Each dollar burned produces a meaningful return in + recurring revenue." excellent: value: "< 1.0x" - signal: "Exceptional capital efficiency. The company generates more net new ARR than it burns. Rare and highly valued by investors." + signal: "Exceptional capital efficiency. The company generates more net new ARR + than it burns. Rare and highly valued by investors." stage_notes: - seed: "Burn multiple is very high at seed by definition — the company is investing ahead of revenue. Track it but do not optimize for it." - series_a: "Investors increasingly use burn multiple as a primary efficiency screen. Sub-2x is the expectation." - series_b_plus: "Bessemer coined this metric to replace 'efficiency score.' Sub-1.5x is the target. Cash-flow-positive companies have a 0x burn multiple." + seed: "Burn multiple is very high at seed by definition — the company is + investing ahead of revenue. Track it but do not optimize for it." + series_a: "Investors increasingly use burn multiple as a primary efficiency + screen. Sub-2x is the expectation." + series_b_plus: "Bessemer coined this metric to replace 'efficiency score.' + Sub-1.5x is the target. Cash-flow-positive companies have a 0x burn + multiple." data_sources: - source: "Bessemer Venture Partners (David Sacks)" year: "2024" - source: "Battery Ventures Cloud Operating Metrics" year: "2023" - related_metrics: ["rule-of-40", "arr", "gross-margin"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "Burn multiple is undefined or misleading for companies with flat or declining ARR. Use it only for growing companies." + related_metrics: [ "rule-of-40", "arr", "gross-margin" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "Burn multiple is undefined or misleading for companies with flat or + declining ARR. Use it only for growing companies." - name: "Rule of 40" id: "rule-of-40" category: "efficiency" - definition: "The sum of revenue growth rate and profit margin, measuring the tradeoff between growth and profitability — a combined health score for SaaS businesses." + definition: "The sum of revenue growth rate and profit margin, measuring the + tradeoff between growth and profitability — a combined health score for + SaaS businesses." formula: "YoY Revenue Growth % + Free Cash Flow Margin % (or EBITDA Margin %)" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 20%" - signal: "Neither growing fast nor profitable. The company is stuck in an unproductive middle — too slow to be a growth story, too unprofitable to be a value story." + signal: "Neither growing fast nor profitable. The company is stuck in an + unproductive middle — too slow to be a growth story, too unprofitable + to be a value story." below_average: value: "20-30%" - signal: "Below the threshold. Acceptable only during a strategic transition (e.g., shifting from growth to profitability)." + signal: "Below the threshold. Acceptable only during a strategic transition + (e.g., shifting from growth to profitability)." average: value: "30-40%" - signal: "Approaching but not meeting the bar. Many private SaaS companies land here." + signal: "Approaching but not meeting the bar. Many private SaaS companies land + here." good: value: "40-60%" - signal: "Meeting the Rule of 40. The standard for a well-run SaaS business. Balances growth and efficiency effectively." + signal: "Meeting the Rule of 40. The standard for a well-run SaaS business. + Balances growth and efficiency effectively." excellent: value: "> 60%" - signal: "Elite performance. Companies like CrowdStrike and Datadog at their peaks. Either hyper-growth, highly profitable, or both." + signal: "Elite performance. Companies like CrowdStrike and Datadog at their + peaks. Either hyper-growth, highly profitable, or both." stage_notes: - seed: "Rule of 40 is not applicable at seed. Growth rate alone is the relevant metric." - series_a: "Begins to apply loosely. A company growing 100% YoY with -60% margins technically hits 40% but the composition matters." - series_b_plus: "Becomes a primary valuation driver. Public market investors use Rule of 40 as a screening criterion for premium multiples." + seed: "Rule of 40 is not applicable at seed. Growth rate alone is the relevant + metric." + series_a: "Begins to apply loosely. A company growing 100% YoY with -60% margins + technically hits 40% but the composition matters." + series_b_plus: "Becomes a primary valuation driver. Public market investors use + Rule of 40 as a screening criterion for premium multiples." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "Battery Ventures State of Cloud" year: "2023" - related_metrics: ["burn-multiple", "gross-margin", "arr"] - related_skills: ["balanced-scorecard", "scenario-planning"] - caveats: "The Rule of 40 treats growth and profitability as interchangeable. They are not. A company growing 5% with 35% margins is fundamentally different from one growing 40% with 0% margins." + related_metrics: [ "burn-multiple", "gross-margin", "arr" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "The Rule of 40 treats growth and profitability as interchangeable. + They are not. A company growing 5% with 35% margins is fundamentally + different from one growing 40% with 0% margins." - name: "Magic Number" id: "magic-number" category: "efficiency" - definition: "The ratio of net new ARR to prior-quarter sales and marketing spend, measuring the return on the most recent quarter's go-to-market investment." + definition: "The ratio of net new ARR to prior-quarter sales and marketing + spend, measuring the return on the most recent quarter's go-to-market + investment." formula: "Net New ARR in quarter / Sales & Marketing Spend in prior quarter" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 0.5" - signal: "Sales and marketing spend is not converting to revenue efficiently. The go-to-market motion may be broken or the market is not responding." + signal: "Sales and marketing spend is not converting to revenue efficiently. The + go-to-market motion may be broken or the market is not responding." below_average: value: "0.5-0.75" - signal: "Below efficient threshold. Growth requires disproportionate spending. Consider fixing conversion or targeting before increasing budget." + signal: "Below efficient threshold. Growth requires disproportionate spending. + Consider fixing conversion or targeting before increasing budget." average: value: "0.75-1.0" - signal: "Approaching efficiency. The business is generating reasonable returns on GTM investment." + signal: "Approaching efficiency. The business is generating reasonable returns + on GTM investment." good: value: "1.0-1.5" - signal: "Efficient growth. Each dollar of GTM spend produces $1-$1.50 of annualized recurring revenue. Signal to increase investment." + signal: "Efficient growth. Each dollar of GTM spend produces $1-$1.50 of + annualized recurring revenue. Signal to increase investment." excellent: value: "> 1.5" - signal: "Exceptional GTM efficiency. Strong product-market fit or viral dynamics reducing the cost of customer acquisition." + signal: "Exceptional GTM efficiency. Strong product-market fit or viral dynamics + reducing the cost of customer acquisition." stage_notes: - seed: "Magic number is unreliable with small numbers. A single deal can produce a misleading result." - series_a: "A magic number above 0.75 justifies increasing GTM spend. Below 0.5 suggests the GTM motion needs restructuring." - series_b_plus: "Public SaaS companies target 1.0+. The magic number helps determine whether to invest in or restructure the sales organization." + seed: "Magic number is unreliable with small numbers. A single deal can produce + a misleading result." + series_a: "A magic number above 0.75 justifies increasing GTM spend. Below 0.5 + suggests the GTM motion needs restructuring." + series_b_plus: "Public SaaS companies target 1.0+. The magic number helps + determine whether to invest in or restructure the sales organization." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "SaaStr Benchmarks" year: "2024" - related_metrics: ["cac", "cac-payback-period", "burn-multiple"] - related_skills: ["balanced-scorecard", "four-ps-marketing"] - caveats: "The magic number uses prior quarter spend against current quarter revenue gain, assuming a one-quarter lag. This assumption breaks for products with long sales cycles." + related_metrics: [ "cac", "cac-payback-period", "burn-multiple" ] + related_skills: [ "balanced-scorecard", "four-ps-marketing" ] + caveats: "The magic number uses prior quarter spend against current quarter + revenue gain, assuming a one-quarter lag. This assumption breaks for + products with long sales cycles." - name: "SaaS Quick Ratio" id: "saas-quick-ratio" category: "efficiency" - definition: "The ratio of revenue inflows to revenue outflows, measuring whether the company adds revenue faster than it loses it." + definition: "The ratio of revenue inflows to revenue outflows, measuring whether + the company adds revenue faster than it loses it." formula: "(New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 1.0" - signal: "The business is shrinking. Revenue losses exceed gains. Urgent intervention required." + signal: "The business is shrinking. Revenue losses exceed gains. Urgent + intervention required." below_average: value: "1.0-2.0" - signal: "Growing but fragile. A small increase in churn could tip the business into contraction." + signal: "Growing but fragile. A small increase in churn could tip the business + into contraction." average: value: "2.0-4.0" signal: "Healthy growth dynamics. Adding revenue at 2-4x the rate of loss." good: value: "4.0-6.0" - signal: "Strong growth quality. Revenue additions far outpace losses. The business has momentum." + signal: "Strong growth quality. Revenue additions far outpace losses. The + business has momentum." excellent: value: "> 6.0" - signal: "Exceptional. Very low churn relative to new revenue additions. Common in early-stage companies with low absolute churn." + signal: "Exceptional. Very low churn relative to new revenue additions. Common + in early-stage companies with low absolute churn." stage_notes: - seed: "Quick Ratio tends to be high at seed because absolute churn is low. A few churned customers will crater it." - series_a: "A Quick Ratio above 4 is strong at Series A. It demonstrates that growth is not masking a retention problem." - series_b_plus: "Quick Ratio naturally declines at scale as the churned base grows in absolute terms. 2-4x is healthy at scale." + seed: "Quick Ratio tends to be high at seed because absolute churn is low. A few + churned customers will crater it." + series_a: "A Quick Ratio above 4 is strong at Series A. It demonstrates that + growth is not masking a retention problem." + series_b_plus: "Quick Ratio naturally declines at scale as the churned base + grows in absolute terms. 2-4x is healthy at scale." data_sources: - source: "Mamoon Hamid / Social Capital framework" year: "2023" - source: "Paddle/ProfitWell analysis" year: "2024" - related_metrics: ["nrr", "revenue-churn", "mom-growth-rate"] - related_skills: ["balanced-scorecard", "growth-share-matrix"] - caveats: "Quick Ratio rewards low churn and high new revenue equally. A company with terrible retention but massive top-of-funnel can still score well. Pair with GRR." + related_metrics: [ "nrr", "revenue-churn", "mom-growth-rate" ] + related_skills: [ "balanced-scorecard", "growth-share-matrix" ] + caveats: "Quick Ratio rewards low churn and high new revenue equally. A company + with terrible retention but massive top-of-funnel can still score well. + Pair with GRR." # ───────────────────────────────────────────── # SALES METRICS @@ -632,254 +826,352 @@ benchmarks: - name: "Average Contract Value (ACV)" id: "acv" category: "sales" - definition: "The average annualized revenue per customer contract, indicating the company's market positioning and deal size." + definition: "The average annualized revenue per customer contract, indicating + the company's market positioning and deal size." formula: "Total new ARR from new contracts / Number of new contracts" unit: "currency" direction: "target-range" benchmarks: poor: - value: "Misaligned ACV for the go-to-market model (e.g., $500 ACV with an enterprise sales team, or $200K ACV with self-serve only)" - signal: "The GTM model does not match the deal size. This creates structural inefficiency — either over-investing in sales or under-investing in it." + value: "Misaligned ACV for the go-to-market model (e.g., $500 ACV with an + enterprise sales team, or $200K ACV with self-serve only)" + signal: "The GTM model does not match the deal size. This creates structural + inefficiency — either over-investing in sales or under-investing in + it." below_average: value: "ACV < $1K with any direct sales involvement" - signal: "Deal size too small to support human-touch sales. Must be product-led growth or self-serve to be viable." + signal: "Deal size too small to support human-touch sales. Must be product-led + growth or self-serve to be viable." average: value: "$5K-$25K ACV with inside sales; $25K-$100K with field sales" - signal: "Typical SaaS range. The GTM model is appropriately matched to the deal size." + signal: "Typical SaaS range. The GTM model is appropriately matched to the deal + size." good: value: "$50K-$200K ACV with field sales and customer success" - signal: "Strong mid-market to enterprise positioning. Supports a high-touch model and strategic customer relationships." + signal: "Strong mid-market to enterprise positioning. Supports a high-touch + model and strategic customer relationships." excellent: value: "> $200K ACV with strategic/enterprise sales" - signal: "Enterprise-grade deals. Long sales cycles but high retention and expansion potential. Concentrated customer risk." + signal: "Enterprise-grade deals. Long sales cycles but high retention and + expansion potential. Concentrated customer risk." stage_notes: - seed: "ACV often starts low and grows as the product matures and moves upmarket. Seed-stage ACV below $5K is common." - series_a: "ACV trajectory matters more than absolute level. Increasing ACV over time signals product maturation and market pull." - series_b_plus: "ACV expansion within existing accounts is as important as new-logo ACV. Track both separately." + seed: "ACV often starts low and grows as the product matures and moves upmarket. + Seed-stage ACV below $5K is common." + series_a: "ACV trajectory matters more than absolute level. Increasing ACV over + time signals product maturation and market pull." + series_b_plus: "ACV expansion within existing accounts is as important as + new-logo ACV. Track both separately." data_sources: - source: "KeyBanc SaaS Survey" year: "2024" - source: "OpenView SaaS Benchmarks" year: "2023" - related_metrics: ["arpu", "ltv", "sales-cycle-length"] - related_skills: ["pricing-diagnosis", "four-ps-marketing"] - caveats: "ACV can be distorted by a single large deal. Report median ACV alongside mean ACV for accuracy." + related_metrics: [ "arpu", "ltv", "sales-cycle-length" ] + related_skills: + - four-ps-marketing + caveats: "ACV can be distorted by a single large deal. Report median ACV + alongside mean ACV for accuracy." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Average Revenue Per User (ARPU)" id: "arpu" category: "sales" - definition: "The average monthly revenue generated per active user or account, measuring monetization intensity." + definition: "The average monthly revenue generated per active user or account, + measuring monetization intensity." formula: "MRR / Total active accounts (or users, depending on pricing model)" unit: "currency" direction: "higher-is-better" benchmarks: poor: value: "< $10/month per account (B2B); < $2/month per user (B2C)" - signal: "Very low monetization. Requires massive scale to build a significant business. Difficult to support any direct sales motion." + signal: "Very low monetization. Requires massive scale to build a significant + business. Difficult to support any direct sales motion." below_average: value: "$10-$50/month (B2B); $2-$10/month (B2C)" - signal: "Low ARPU. Viable with self-serve PLG and low support costs. Challenging to fund a traditional sales team." + signal: "Low ARPU. Viable with self-serve PLG and low support costs. Challenging + to fund a traditional sales team." average: value: "$50-$500/month (B2B)" - signal: "The range where inside sales, content marketing, and moderate customer success become sustainable." + signal: "The range where inside sales, content marketing, and moderate customer + success become sustainable." good: value: "$500-$5,000/month (B2B)" - signal: "Strong monetization. Supports field sales, dedicated CSMs, and significant retention investment." + signal: "Strong monetization. Supports field sales, dedicated CSMs, and + significant retention investment." excellent: value: "> $5,000/month (B2B)" - signal: "Enterprise pricing. High-value customers who justify strategic account management and custom solutions." + signal: "Enterprise pricing. High-value customers who justify strategic account + management and custom solutions." stage_notes: - seed: "ARPU at seed reflects initial pricing — often underpriced. Tracking ARPU growth over time is more informative." - series_a: "ARPU should be increasing or stable. Declining ARPU (from moving downmarket to chase volume) is a warning sign." - series_b_plus: "Segment ARPU by cohort and customer tier. Blended ARPU obscures whether you are attracting larger or smaller customers over time." + seed: "ARPU at seed reflects initial pricing — often underpriced. Tracking ARPU + growth over time is more informative." + series_a: "ARPU should be increasing or stable. Declining ARPU (from moving + downmarket to chase volume) is a warning sign." + series_b_plus: "Segment ARPU by cohort and customer tier. Blended ARPU obscures + whether you are attracting larger or smaller customers over time." data_sources: - source: "Paddle/ProfitWell Price Benchmarks" year: "2024" - source: "OpenView PLG Index" year: "2023" - related_metrics: ["acv", "mrr", "ltv"] - related_skills: ["pricing-diagnosis", "business-model-canvas"] - caveats: "ARPU varies enormously by segment. A company selling to SMBs at $50/month and enterprises at $5,000/month has a blended ARPU that describes neither customer well." + related_metrics: [ "acv", "mrr", "ltv" ] + related_skills: + - business-model-canvas + caveats: "ARPU varies enormously by segment. A company selling to SMBs at + $50/month and enterprises at $5,000/month has a blended ARPU that + describes neither customer well." + related_content: + - kind: diagnostic + ref: pricing-diagnosis - name: "Expansion Revenue Percentage" id: "expansion-revenue-pct" category: "sales" - definition: "The percentage of new MRR that comes from existing customers (upsells, cross-sells, seat expansion) rather than new logos." + definition: "The percentage of new MRR that comes from existing customers + (upsells, cross-sells, seat expansion) rather than new logos." formula: "Expansion MRR / Total New MRR x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 10%" - signal: "Nearly all growth comes from new customers. The existing base is not expanding, indicating limited upsell paths or low product stickiness." + signal: "Nearly all growth comes from new customers. The existing base is not + expanding, indicating limited upsell paths or low product stickiness." below_average: value: "10-20%" - signal: "Minimal expansion. The product may lack tiers, add-ons, or usage-based pricing that drive natural expansion." + signal: "Minimal expansion. The product may lack tiers, add-ons, or usage-based + pricing that drive natural expansion." average: value: "20-30%" - signal: "Moderate expansion revenue. Common for companies with seat-based pricing and steady customer growth." + signal: "Moderate expansion revenue. Common for companies with seat-based + pricing and steady customer growth." good: value: "30-50%" - signal: "Strong expansion engine. Existing customers are a significant growth driver. Indicates land-and-expand is working." + signal: "Strong expansion engine. Existing customers are a significant growth + driver. Indicates land-and-expand is working." excellent: value: "> 50%" - signal: "Expansion-dominated growth. The existing base grows faster than new customer acquisition. Characteristic of usage-based models (Snowflake, Twilio)." + signal: "Expansion-dominated growth. The existing base grows faster than new + customer acquisition. Characteristic of usage-based models (Snowflake, + Twilio)." stage_notes: - seed: "Expansion revenue is negligible at seed — the focus is new customer acquisition and retention." - series_a: "Expansion signals begin to matter. Any expansion revenue at Series A is positive. Building the expansion motion is a key Series A initiative." - series_b_plus: "At scale, 30-50% of new MRR from expansion is the target. Companies relying solely on new logos face increasing CAC pressure." + seed: "Expansion revenue is negligible at seed — the focus is new customer + acquisition and retention." + series_a: "Expansion signals begin to matter. Any expansion revenue at Series A + is positive. Building the expansion motion is a key Series A + initiative." + series_b_plus: "At scale, 30-50% of new MRR from expansion is the target. + Companies relying solely on new logos face increasing CAC pressure." data_sources: - source: "KeyBanc SaaS Survey" year: "2024" - source: "OpenView Expansion Revenue Report" year: "2023" - related_metrics: ["nrr", "ndr", "arpu"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "Expansion revenue percentage can be inflated by usage-based pricing with volatile consumption. Distinguish between durable expansion (more seats, higher tiers) and variable expansion (usage spikes)." + related_metrics: [ "nrr", "ndr", "arpu" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Expansion revenue percentage can be inflated by usage-based pricing + with volatile consumption. Distinguish between durable expansion (more + seats, higher tiers) and variable expansion (usage spikes)." - name: "Net Dollar Retention (NDR)" id: "ndr" category: "retention" - definition: "Functionally identical to NRR — the percentage of revenue retained from a cohort of customers after a defined period, including expansion and contraction." - formula: "(Starting ARR of cohort + Expansion - Contraction - Churn) / Starting ARR of cohort x 100 (typically measured at 12-month intervals)" + definition: "Functionally identical to NRR — the percentage of revenue retained + from a cohort of customers after a defined period, including expansion and + contraction." + formula: "(Starting ARR of cohort + Expansion - Contraction - Churn) / Starting + ARR of cohort x 100 (typically measured at 12-month intervals)" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 90%" - signal: "Cohort revenue declines materially. The business cannot grow its existing base — all growth must come from new logos." + signal: "Cohort revenue declines materially. The business cannot grow its + existing base — all growth must come from new logos." below_average: value: "90-100%" - signal: "Cohort revenue is roughly flat. No net expansion from existing customers." + signal: "Cohort revenue is roughly flat. No net expansion from existing + customers." average: value: "100-110%" signal: "Modest net expansion. Cohorts grow slightly over time." good: value: "110-130%" - signal: "Strong expansion. Typical of best-in-class private SaaS companies. Each cohort becomes more valuable over time." + signal: "Strong expansion. Typical of best-in-class private SaaS companies. Each + cohort becomes more valuable over time." excellent: value: "> 130%" - signal: "Exceptional. Usage-based or deeply embedded products where customer spend compounds naturally." + signal: "Exceptional. Usage-based or deeply embedded products where customer + spend compounds naturally." stage_notes: - seed: "NDR requires at least 12 months of cohort data to be meaningful. Not applicable at seed." - series_a: "NDR is one of the most scrutinized metrics at Series A. Above 110% is a strong signal." - series_b_plus: "NDR above 120% is a key driver of premium valuations in public markets. Bessemer, Iconiq, and other benchmarks weight it heavily." + seed: "NDR requires at least 12 months of cohort data to be meaningful. Not + applicable at seed." + series_a: "NDR is one of the most scrutinized metrics at Series A. Above 110% is + a strong signal." + series_b_plus: "NDR above 120% is a key driver of premium valuations in public + markets. Bessemer, Iconiq, and other benchmarks weight it heavily." data_sources: - source: "Bessemer Cloud Index" year: "2024" - source: "Iconiq Growth" year: "2023" - related_metrics: ["nrr", "grr", "expansion-revenue-pct"] - related_skills: ["net-promoter-score", "balanced-scorecard"] - caveats: "NDR and NRR are used interchangeably in the industry, though NDR typically implies annual cohort measurement while NRR may be monthly. Clarify the time window when reporting." + related_metrics: [ "nrr", "grr", "expansion-revenue-pct" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "NDR and NRR are used interchangeably in the industry, though NDR + typically implies annual cohort measurement while NRR may be monthly. + Clarify the time window when reporting." - name: "Pipeline Coverage Ratio" id: "pipeline-coverage-ratio" category: "sales" - definition: "The ratio of total pipeline value to quota or revenue target for a given period, measuring whether the sales team has sufficient opportunity volume." + definition: "The ratio of total pipeline value to quota or revenue target for a + given period, measuring whether the sales team has sufficient opportunity + volume." formula: "Total pipeline value for period / Revenue target (quota) for period" unit: "ratio" direction: "higher-is-better" benchmarks: poor: value: "< 2.0x" - signal: "Insufficient pipeline. The sales team has less than twice quota in pipeline, making target attainment unlikely given typical win rates." + signal: "Insufficient pipeline. The sales team has less than twice quota in + pipeline, making target attainment unlikely given typical win rates." below_average: value: "2.0-2.5x" - signal: "Thin pipeline. Requires above-average win rates to hit target. Any deal slippage will cause a miss." + signal: "Thin pipeline. Requires above-average win rates to hit target. Any deal + slippage will cause a miss." average: value: "2.5-3.5x" - signal: "Standard coverage. Assuming 25-35% win rates, this provides a reasonable probability of hitting target." + signal: "Standard coverage. Assuming 25-35% win rates, this provides a + reasonable probability of hitting target." good: value: "3.5-5.0x" - signal: "Healthy coverage. Provides buffer for deal slippage, lost deals, and sales cycle extensions." + signal: "Healthy coverage. Provides buffer for deal slippage, lost deals, and + sales cycle extensions." excellent: value: "> 5.0x" - signal: "Strong coverage, though may indicate pipeline quality issues — too many unqualified opportunities inflating the number." + signal: "Strong coverage, though may indicate pipeline quality issues — too many + unqualified opportunities inflating the number." stage_notes: - seed: "Pipeline coverage is not a meaningful metric without a sales team. Founders selling directly should track opportunity list, not formal pipeline." - series_a: "As the first sales hires come on, pipeline coverage becomes a leading indicator. 3x coverage is the minimum target." - series_b_plus: "Pipeline coverage should be measured by stage (early, mid, late), by segment, and by rep. Aggregate coverage masks individual performance." + seed: "Pipeline coverage is not a meaningful metric without a sales team. + Founders selling directly should track opportunity list, not formal + pipeline." + series_a: "As the first sales hires come on, pipeline coverage becomes a leading + indicator. 3x coverage is the minimum target." + series_b_plus: "Pipeline coverage should be measured by stage (early, mid, + late), by segment, and by rep. Aggregate coverage masks individual + performance." data_sources: - source: "Gartner Sales Benchmarks" year: "2024" - source: "Forrester B2B Sales Report" year: "2023" - related_metrics: ["win-rate", "sales-cycle-length", "acv"] - related_skills: ["scenario-planning", "balanced-scorecard"] - caveats: "Pipeline coverage is only meaningful if pipeline hygiene is strong. Inflated pipelines with stale or unqualified deals produce misleadingly high coverage ratios." + related_metrics: [ "win-rate", "sales-cycle-length", "acv" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "Pipeline coverage is only meaningful if pipeline hygiene is strong. + Inflated pipelines with stale or unqualified deals produce misleadingly + high coverage ratios." - name: "Win Rate" id: "win-rate" category: "sales" - definition: "The percentage of sales opportunities that convert to closed-won deals, measuring sales effectiveness." + definition: "The percentage of sales opportunities that convert to closed-won + deals, measuring sales effectiveness." formula: "Closed-won opportunities / (Closed-won + Closed-lost opportunities) x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 15%" - signal: "Very low conversion. Possible causes: poor qualification, weak product fit, uncompetitive offering, or ineffective sales process." + signal: "Very low conversion. Possible causes: poor qualification, weak product + fit, uncompetitive offering, or ineffective sales process." below_average: value: "15-20%" - signal: "Below average. The pipeline includes too many unqualified or poorly matched opportunities." + signal: "Below average. The pipeline includes too many unqualified or poorly + matched opportunities." average: value: "20-30%" - signal: "Typical for B2B SaaS. Roughly one in four qualified opportunities converts." + signal: "Typical for B2B SaaS. Roughly one in four qualified opportunities + converts." good: value: "30-40%" - signal: "Strong conversion. Indicates good qualification, competitive product, and effective sales execution." + signal: "Strong conversion. Indicates good qualification, competitive product, + and effective sales execution." excellent: value: "> 40%" - signal: "Exceptional. Either the product has overwhelming competitive advantage or the company qualifies pipeline very aggressively (which may limit volume)." + signal: "Exceptional. Either the product has overwhelming competitive advantage + or the company qualifies pipeline very aggressively (which may limit + volume)." stage_notes: - seed: "Founders typically close at higher rates than hired reps — they know the product deeply and prospects respond to founder energy. Do not use founder win rates to project team performance." - series_a: "Win rates should be tracked by source (inbound vs. outbound), deal size, and sales rep. Aggregate win rate is a starting point." - series_b_plus: "Win rate analysis should include competitive win/loss data. Track not just whether you win but whom you beat and whom you lose to." + seed: "Founders typically close at higher rates than hired reps — they know the + product deeply and prospects respond to founder energy. Do not use + founder win rates to project team performance." + series_a: "Win rates should be tracked by source (inbound vs. outbound), deal + size, and sales rep. Aggregate win rate is a starting point." + series_b_plus: "Win rate analysis should include competitive win/loss data. + Track not just whether you win but whom you beat and whom you lose to." data_sources: - source: "Gartner Sales Research" year: "2024" - source: "HubSpot Sales Benchmarks" year: "2023" - related_metrics: ["pipeline-coverage-ratio", "sales-cycle-length", "acv"] - related_skills: ["competitive-negotiation", "porters-five-forces"] - caveats: "Win rate is sensitive to how 'opportunity' is defined. If only highly qualified prospects enter the pipeline, win rate appears high. Standardize opportunity stage definitions." + related_metrics: [ "pipeline-coverage-ratio", "sales-cycle-length", "acv" ] + related_skills: [ "competitive-negotiation", "porters-five-forces" ] + caveats: "Win rate is sensitive to how 'opportunity' is defined. If only highly + qualified prospects enter the pipeline, win rate appears high. Standardize + opportunity stage definitions." - name: "Sales Cycle Length" id: "sales-cycle-length" category: "sales" - definition: "The average number of days from first meaningful sales engagement to closed-won deal." - formula: "Sum of (close date - opportunity creation date) for all won deals / Number of won deals" + definition: "The average number of days from first meaningful sales engagement + to closed-won deal." + formula: "Sum of (close date - opportunity creation date) for all won deals / + Number of won deals" unit: "days" direction: "lower-is-better" benchmarks: poor: value: "> 180 days for mid-market; > 365 days for enterprise" - signal: "Extremely long cycles. Common causes: unclear value proposition, too many stakeholders, weak champion, or product not addressing an urgent problem." + signal: "Extremely long cycles. Common causes: unclear value proposition, too + many stakeholders, weak champion, or product not addressing an urgent + problem." below_average: value: "90-180 days for mid-market; 180-365 days for enterprise" - signal: "Long but not unusual for complex sales. Requires strong pipeline management and forecasting discipline." + signal: "Long but not unusual for complex sales. Requires strong pipeline + management and forecasting discipline." average: value: "30-90 days for SMB/mid-market; 90-180 days for enterprise" - signal: "Standard B2B SaaS range. Varies significantly by ACV — higher ACV naturally correlates with longer cycles." + signal: "Standard B2B SaaS range. Varies significantly by ACV — higher ACV + naturally correlates with longer cycles." good: value: "14-30 days for SMB; 45-90 days for mid-market" - signal: "Efficient cycle. Strong urgency, clear value, and streamlined buying process." + signal: "Efficient cycle. Strong urgency, clear value, and streamlined buying + process." excellent: value: "< 14 days for SMB; < 45 days for mid-market" - signal: "Very fast conversion. Often indicates product-led growth, free trial conversion, or a burning platform problem." + signal: "Very fast conversion. Often indicates product-led growth, free trial + conversion, or a burning platform problem." stage_notes: - seed: "Sales cycles at seed are often artificially short (early adopters with low friction) or artificially long (unrefined sales process). Neither predicts scale behavior." - series_a: "Tracking average sales cycle by deal size establishes the basis for forecasting and hiring models." - series_b_plus: "Sales cycle compression is a key efficiency lever at scale. Reducing cycle length by 20% has the same effect as hiring 20% more reps." + seed: "Sales cycles at seed are often artificially short (early adopters with + low friction) or artificially long (unrefined sales process). Neither + predicts scale behavior." + series_a: "Tracking average sales cycle by deal size establishes the basis for + forecasting and hiring models." + series_b_plus: "Sales cycle compression is a key efficiency lever at scale. + Reducing cycle length by 20% has the same effect as hiring 20% more + reps." data_sources: - source: "Gartner B2B Buying Study" year: "2024" - source: "HubSpot Sales Benchmarks" year: "2023" - related_metrics: ["win-rate", "acv", "pipeline-coverage-ratio"] - related_skills: ["delivering-the-deal", "competitive-negotiation"] - caveats: "Sales cycle length should exclude outlier deals (both extremely fast and extremely slow). Use median rather than mean for more representative data." + related_metrics: [ "win-rate", "acv", "pipeline-coverage-ratio" ] + related_skills: [ "delivering-the-deal", "competitive-negotiation" ] + caveats: "Sales cycle length should exclude outlier deals (both extremely fast + and extremely slow). Use median rather than mean for more representative + data." # ───────────────────────────────────────────── # PRODUCT METRICS @@ -888,74 +1180,102 @@ benchmarks: - name: "Time to Value" id: "time-to-value" category: "product" - definition: "The elapsed time from customer sign-up to the moment they experience the core value proposition of the product." - formula: "Median time from account creation to activation milestone (product-specific definition)" + definition: "The elapsed time from customer sign-up to the moment they + experience the core value proposition of the product." + formula: "Median time from account creation to activation milestone + (product-specific definition)" unit: "days" direction: "lower-is-better" benchmarks: poor: value: "> 30 days" - signal: "Customers wait a month before experiencing value. High abandonment risk, especially for self-serve products." + signal: "Customers wait a month before experiencing value. High abandonment + risk, especially for self-serve products." below_average: value: "14-30 days" - signal: "Slow value delivery. Typical of products requiring significant setup, integration, or data migration." + signal: "Slow value delivery. Typical of products requiring significant setup, + integration, or data migration." average: value: "3-14 days" - signal: "Reasonable for B2B products with moderate complexity. Acceptable for products with guided onboarding." + signal: "Reasonable for B2B products with moderate complexity. Acceptable for + products with guided onboarding." good: value: "1-3 days" - signal: "Fast value delivery. Strong onboarding flow and clear first-use experience." + signal: "Fast value delivery. Strong onboarding flow and clear first-use + experience." excellent: value: "< 1 day (ideally < 1 hour)" - signal: "Immediate value. Characteristic of PLG products with strong 'aha moments' (Slack, Loom, Canva). Drives viral adoption." + signal: "Immediate value. Characteristic of PLG products with strong 'aha + moments' (Slack, Loom, Canva). Drives viral adoption." stage_notes: - seed: "Time to value is often long at seed — manual onboarding, incomplete product. Reducing it is a top priority for product-market fit." - series_a: "Time to value directly predicts conversion rates. Companies that compress TTV from weeks to days see step-function improvements in activation." - series_b_plus: "At scale, time to value should be measured by segment and onboarding path (self-serve vs. assisted vs. enterprise implementation)." + seed: "Time to value is often long at seed — manual onboarding, incomplete + product. Reducing it is a top priority for product-market fit." + series_a: "Time to value directly predicts conversion rates. Companies that + compress TTV from weeks to days see step-function improvements in + activation." + series_b_plus: "At scale, time to value should be measured by segment and + onboarding path (self-serve vs. assisted vs. enterprise + implementation)." data_sources: - source: "OpenView PLG Index" year: "2024" - source: "Pendo Product Benchmarks" year: "2023" - related_metrics: ["activation-rate", "logo-churn"] - related_skills: ["net-promoter-score", "product-life-cycle"] - caveats: "Time to value requires a precise definition of the 'value moment.' Without this, the metric is meaningless. Define the activation event before measuring TTV." + related_metrics: [ "activation-rate", "logo-churn" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Time to value requires a precise definition of the 'value moment.' + Without this, the metric is meaningless. Define the activation event + before measuring TTV." - name: "Activation Rate" id: "activation-rate" category: "product" - definition: "The percentage of new sign-ups or customers who complete the key actions that predict long-term retention and value realization." + definition: "The percentage of new sign-ups or customers who complete the key + actions that predict long-term retention and value realization." formula: "Users who complete activation milestone / Total new sign-ups x 100" unit: "percentage" direction: "higher-is-better" benchmarks: poor: value: "< 15%" - signal: "The vast majority of sign-ups never experience the product's value. The onboarding experience is failing or the product does not deliver on its promise." + signal: "The vast majority of sign-ups never experience the product's value. The + onboarding experience is failing or the product does not deliver on + its promise." below_average: value: "15-25%" - signal: "Low activation. Common for products with complex setup requirements or weak onboarding flows." + signal: "Low activation. Common for products with complex setup requirements or + weak onboarding flows." average: value: "25-40%" - signal: "Standard for B2B SaaS with free trials or freemium models. Significant room for improvement." + signal: "Standard for B2B SaaS with free trials or freemium models. Significant + room for improvement." good: value: "40-60%" - signal: "Strong activation. The product's onboarding effectively guides users to value. Good PLG companies achieve this range." + signal: "Strong activation. The product's onboarding effectively guides users to + value. Good PLG companies achieve this range." excellent: value: "> 60%" - signal: "Exceptional. The product is intuitive and delivers value with minimal friction. Elite PLG products (Dropbox, Calendly) at their peaks." + signal: "Exceptional. The product is intuitive and delivers value with minimal + friction. Elite PLG products (Dropbox, Calendly) at their peaks." stage_notes: - seed: "Activation rate is the most important product metric at seed. It directly indicates whether the product delivers on its promise." - series_a: "Improving activation rate is often the highest-ROI investment at Series A — it improves every downstream metric (retention, expansion, referral)." - series_b_plus: "Activation rate should be segmented by source, persona, and onboarding path. Different segments require different activation strategies." + seed: "Activation rate is the most important product metric at seed. It directly + indicates whether the product delivers on its promise." + series_a: "Improving activation rate is often the highest-ROI investment at + Series A — it improves every downstream metric (retention, expansion, + referral)." + series_b_plus: "Activation rate should be segmented by source, persona, and + onboarding path. Different segments require different activation + strategies." data_sources: - source: "OpenView PLG Index" year: "2024" - source: "Mixpanel Product Benchmarks" year: "2023" - related_metrics: ["time-to-value", "logo-churn", "nrr"] - related_skills: ["net-promoter-score", "product-life-cycle", "disruptive-innovation"] - caveats: "Activation rate depends entirely on how the activation milestone is defined. Choose a milestone that correlates with retention (validated empirically), not an arbitrary product action." + related_metrics: [ "time-to-value", "logo-churn", "nrr" ] + related_skills: [ "net-promoter-score", "product-life-cycle", "disruptive-innovation" ] + caveats: "Activation rate depends entirely on how the activation milestone is + defined. Choose a milestone that correlates with retention (validated + empirically), not an arbitrary product action." # ───────────────────────────────────────────── # PRODUCT METRICS (continued) @@ -964,35 +1284,49 @@ benchmarks: - name: "Net Promoter Score (NPS)" id: "nps-saas" category: "product" - definition: "A measure of customer loyalty and satisfaction based on the likelihood of recommending the product, widely used as a leading indicator of retention in SaaS." + definition: "A measure of customer loyalty and satisfaction based on the + likelihood of recommending the product, widely used as a leading indicator + of retention in SaaS." formula: "% Promoters (score 9-10) - % Detractors (score 0-6)" unit: "score" direction: "higher-is-better" benchmarks: poor: value: "< 0" - signal: "More detractors than promoters. The product is actively generating negative word-of-mouth. Churn risk is severe." + signal: "More detractors than promoters. The product is actively generating + negative word-of-mouth. Churn risk is severe." below_average: value: "0-20" - signal: "Net positive but weak. Customers are indifferent rather than enthusiastic. Vulnerable to competitive displacement." + signal: "Net positive but weak. Customers are indifferent rather than + enthusiastic. Vulnerable to competitive displacement." average: value: "20-40" - signal: "Decent satisfaction. Typical for B2B SaaS products that solve real problems without delighting users." + signal: "Decent satisfaction. Typical for B2B SaaS products that solve real + problems without delighting users." good: value: "40-60" - signal: "Strong loyalty. Customers actively recommend the product. Correlates with low churn and organic growth." + signal: "Strong loyalty. Customers actively recommend the product. Correlates + with low churn and organic growth." excellent: value: "> 60" - signal: "Exceptional loyalty. Companies like Slack (early), Notion, and Zoom in their growth phases. Drives powerful viral loops." + signal: "Exceptional loyalty. Companies like Slack (early), Notion, and Zoom in + their growth phases. Drives powerful viral loops." stage_notes: - seed: "NPS surveys require a minimum sample size (~30 responses) to be statistically meaningful. At seed, qualitative feedback matters more." - series_a: "NPS above 40 is a strong signal for investors. Below 20 at Series A raises concerns about product-market fit depth." - series_b_plus: "NPS should be tracked quarterly, segmented by cohort and customer tier. Declining NPS at scale is an early warning of market saturation or product stagnation." + seed: "NPS surveys require a minimum sample size (~30 responses) to be + statistically meaningful. At seed, qualitative feedback matters more." + series_a: "NPS above 40 is a strong signal for investors. Below 20 at Series A + raises concerns about product-market fit depth." + series_b_plus: "NPS should be tracked quarterly, segmented by cohort and + customer tier. Declining NPS at scale is an early warning of market + saturation or product stagnation." data_sources: - source: "Bain & Company NPS Benchmarks" year: "2024" - source: "Retently B2B SaaS NPS Benchmarks" year: "2024" - related_metrics: ["logo-churn", "nrr", "activation-rate"] - related_skills: ["net-promoter-score"] - caveats: "NPS is a lagging and blunt instrument. A high NPS does not guarantee retention (customers may love the product but switch due to price), and a low NPS does not guarantee churn (customers may dislike the product but have high switching costs)." + related_metrics: [ "logo-churn", "nrr", "activation-rate" ] + related_skills: [ "net-promoter-score" ] + caveats: "NPS is a lagging and blunt instrument. A high NPS does not guarantee + retention (customers may love the product but switch due to price), and a + low NPS does not guarantee churn (customers may dislike the product but + have high switching costs)." diff --git a/.claude/industry-packs/saas/saas-diagnostic-rules.yaml b/.claude/industry-packs/saas/saas-diagnostic-rules.yaml index d05b596..ad27598 100644 --- a/.claude/industry-packs/saas/saas-diagnostic-rules.yaml +++ b/.claude/industry-packs/saas/saas-diagnostic-rules.yaml @@ -29,58 +29,101 @@ diagnostic_rules: - diagnostic: "customer-churn-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Churn is the defining challenge of SaaS. The base diagnostic applies, but SaaS churn has distinct subtypes (logo vs. revenue, voluntary vs. involuntary, early vs. late lifecycle) that require specialized triage and SaaS-native diagnoses." + adaptation_rationale: "Churn is the defining challenge of SaaS. The base + diagnostic applies, but SaaS churn has distinct subtypes (logo vs. + revenue, voluntary vs. involuntary, early vs. late lifecycle) that require + specialized triage and SaaS-native diagnoses." additional_triage_questions: - - question: "Is the churn concentrated in logo churn (customers leaving entirely) or revenue churn (customers downgrading but staying)?" - purpose: "Distinguishes between product-market-fit failures (logo churn) and pricing/packaging failures (revenue churn). These have fundamentally different root causes and solutions." - routing_impact: "Logo churn routes to product-market-fit-diagnosis and activation-rate analysis. Revenue churn routes to pricing-diagnosis and expansion-revenue analysis." - - question: "What percentage of churn is involuntary (failed payments, expired cards) versus voluntary (deliberate cancellation)?" - purpose: "Involuntary churn in SaaS is a solvable operational problem — dunning sequences, card-on-file reminders, and payment retry logic can recover 20-40% of involuntary churn." - routing_impact: "High involuntary churn (>30% of total) routes to operational process improvement before any strategic intervention. This is the highest-ROI fix in SaaS churn." - - question: "When in the customer lifecycle does churn concentrate — within the first 90 days, at the first renewal boundary, or throughout the lifecycle?" - purpose: "Early churn signals onboarding or activation failure. Renewal-boundary churn signals value realization failure. Distributed churn signals competitive displacement or market saturation." - routing_impact: "First-90-day churn routes to time-to-value and activation-rate analysis. Renewal churn routes to customer-success process and QBR effectiveness. Distributed churn routes to competitive-threat-diagnosis." + - question: "Is the churn concentrated in logo churn (customers leaving entirely) + or revenue churn (customers downgrading but staying)?" + purpose: "Distinguishes between product-market-fit failures (logo churn) and + pricing/packaging failures (revenue churn). These have fundamentally + different root causes and solutions." + routing_impact: "Logo churn routes to product-market-fit-diagnosis and + activation-rate analysis. Revenue churn routes to pricing-diagnosis + and expansion-revenue analysis." + - question: "What percentage of churn is involuntary (failed payments, expired + cards) versus voluntary (deliberate cancellation)?" + purpose: "Involuntary churn in SaaS is a solvable operational problem — dunning + sequences, card-on-file reminders, and payment retry logic can recover + 20-40% of involuntary churn." + routing_impact: "High involuntary churn (>30% of total) routes to operational + process improvement before any strategic intervention. This is the + highest-ROI fix in SaaS churn." + - question: "When in the customer lifecycle does churn concentrate — within the + first 90 days, at the first renewal boundary, or throughout the + lifecycle?" + purpose: "Early churn signals onboarding or activation failure. Renewal-boundary + churn signals value realization failure. Distributed churn signals + competitive displacement or market saturation." + routing_impact: "First-90-day churn routes to time-to-value and activation-rate + analysis. Renewal churn routes to customer-success process and QBR + effectiveness. Distributed churn routes to + competitive-threat-diagnosis." diagnosis_weight_shifts: more_likely: - diagnosis: "Activation failure driving early-lifecycle churn" - reason: "SaaS products that fail to deliver value within the first 14-30 days lose customers before they form habits. This is the most common and most fixable churn driver." + reason: "SaaS products that fail to deliver value within the first 14-30 days + lose customers before they form habits. This is the most common and + most fixable churn driver." - diagnosis: "Pricing-value misalignment" - reason: "SaaS customers continuously evaluate whether the subscription price is justified. Unlike one-time purchases, the value question recurs every billing cycle." + reason: "SaaS customers continuously evaluate whether the subscription price is + justified. Unlike one-time purchases, the value question recurs + every billing cycle." less_likely: - diagnosis: "Product quality failure" - reason: "Pure product quality (bugs, downtime) is rarely the primary churn driver in SaaS. It contributes to dissatisfaction but customers usually tolerate quality issues if the product delivers unique value." + reason: "Pure product quality (bugs, downtime) is rarely the primary churn + driver in SaaS. It contributes to dissatisfaction but customers + usually tolerate quality issues if the product delivers unique + value." saas_specific_diagnoses: - name: "Negative net churn masking logo churn crisis" - description: "NRR is above 100% because a small number of expanding accounts offset a large number of departing accounts. The business appears healthy on aggregate retention metrics while the customer base is actually hollowing out — becoming concentrated in fewer, larger accounts with increasing concentration risk." + description: "NRR is above 100% because a small number of expanding accounts + offset a large number of departing accounts. The business appears + healthy on aggregate retention metrics while the customer base is + actually hollowing out — becoming concentrated in fewer, larger + accounts with increasing concentration risk." symptoms: - "NRR above 100% but logo churn above 5% monthly" - "Customer count declining while revenue grows" - "Top 10% of customers representing increasing share of revenue" - - "Expansion revenue dominated by a few large accounts rather than broad-based growth" - routes_to_skills: ["net-promoter-score", "balanced-scorecard", "systems-thinking"] - routes_to_templates: ["unit-economics-snapshot", "quarterly-strategic-review"] + - "Expansion revenue dominated by a few large accounts rather than + broad-based growth" + routes_to_skills: [ "net-promoter-score", "balanced-scorecard", "systems-thinking" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] - name: "Involuntary churn as a silent revenue drain" - description: "Failed payments, expired credit cards, and billing errors account for a substantial portion of total churn but are not being tracked, measured, or addressed separately from voluntary churn." + description: "Failed payments, expired credit cards, and billing errors account + for a substantial portion of total churn but are not being tracked, + measured, or addressed separately from voluntary churn." symptoms: - "No distinction between voluntary and involuntary churn in reporting" - "No dunning email sequence or payment retry logic" - "Monthly churn rate 1-3% higher than peers despite strong NPS" - "High churn among annual-to-monthly conversion cohorts" - routes_to_skills: ["systems-thinking", "eisenhower-matrix"] - routes_to_templates: ["action-plan", "incident-postmortem"] + routes_to_skills: [ "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] - name: "Onboarding-to-value gap" - description: "Customers sign up or purchase but never reach the activation milestone that predicts long-term retention. The product delivers value, but the path to that value is too long, too complex, or too poorly guided." + description: "Customers sign up or purchase but never reach the activation + milestone that predicts long-term retention. The product delivers + value, but the path to that value is too long, too complex, or too + poorly guided." symptoms: - - "High trial-to-paid conversion but high churn within the first 90 days" + - "High trial-to-paid conversion but high churn within the first 90 + days" - "Activation rate below 30%" - "Time to value exceeding 14 days for a self-serve product" - - "Support tickets concentrated in the first two weeks of customer lifecycle" - routes_to_skills: ["product-life-cycle", "disruptive-innovation", "net-promoter-score"] - routes_to_templates: ["action-plan", "new-initiative-brief"] + - "Support tickets concentrated in the first two weeks of customer + lifecycle" + routes_to_skills: [ "product-life-cycle", "disruptive-innovation", "net-promoter-score" ] + routes_to_templates: [ "action-plan", "new-initiative-brief" ] sector_red_flags: - - "Logo churn above 5% monthly sustained for 3+ months — indicates a structural retention problem, not seasonal variation." - - "Revenue churn exceeding logo churn — customers are downgrading before leaving, which often predicts an acceleration of full churn." - - "Churn rate increasing as the company scales — a sign that the product is not retaining the marginal customer acquired through broader marketing." + - "Logo churn above 5% monthly sustained for 3+ months — indicates a + structural retention problem, not seasonal variation." + - "Revenue churn exceeding logo churn — customers are downgrading before + leaving, which often predicts an acceleration of full churn." + - "Churn rate increasing as the company scales — a sign that the product + is not retaining the marginal customer acquired through broader + marketing." # ───────────────────────────────────────────── # 2. GROWTH STALL DIAGNOSIS @@ -88,49 +131,87 @@ diagnostic_rules: - diagnostic: "growth-stall-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS growth stalls have characteristic patterns that differ from traditional businesses. The subscription model provides precise data on where growth is breaking down — new customer acquisition, expansion, or retention — and each has different root causes." + adaptation_rationale: "SaaS growth stalls have characteristic patterns that + differ from traditional businesses. The subscription model provides + precise data on where growth is breaking down — new customer acquisition, + expansion, or retention — and each has different root causes." additional_triage_questions: - - question: "Decompose your MRR growth: what percentage comes from new customers, expansion of existing customers, and reactivation of former customers?" - purpose: "Identifies which growth engine is stalling. New customer acquisition slowing suggests GTM or market problems. Expansion stalling suggests product/pricing problems. Low reactivation suggests the product has no win-back value." - routing_impact: "New-customer stall routes to four-ps-marketing and competitive-threat-diagnosis. Expansion stall routes to pricing-diagnosis and product-life-cycle. Mixed stall routes to systems-thinking for holistic analysis." + - question: "Decompose your MRR growth: what percentage comes from new customers, + expansion of existing customers, and reactivation of former + customers?" + purpose: "Identifies which growth engine is stalling. New customer acquisition + slowing suggests GTM or market problems. Expansion stalling suggests + product/pricing problems. Low reactivation suggests the product has no + win-back value." + routing_impact: "New-customer stall routes to four-ps-marketing and + competitive-threat-diagnosis. Expansion stall routes to + pricing-diagnosis and product-life-cycle. Mixed stall routes to + systems-thinking for holistic analysis." - question: "Has your CAC increased, your conversion rate decreased, or both?" - purpose: "Rising CAC with stable conversion suggests market saturation or increased competition. Declining conversion with stable CAC suggests product-market fit erosion or a competitive leap." - routing_impact: "Rising CAC routes to channel efficiency analysis and blue-ocean-strategy. Declining conversion routes to product-market-fit-diagnosis and win-rate analysis." - - question: "What is your current burn multiple, and how has it changed over the last two quarters?" - purpose: "A rising burn multiple despite investment means the growth engine is losing efficiency — the company is spending more to grow less." - routing_impact: "Burn multiple above 3x routes to efficiency analysis and scenario-planning for runway management." + purpose: "Rising CAC with stable conversion suggests market saturation or + increased competition. Declining conversion with stable CAC suggests + product-market fit erosion or a competitive leap." + routing_impact: "Rising CAC routes to channel efficiency analysis and + blue-ocean-strategy. Declining conversion routes to + product-market-fit-diagnosis and win-rate analysis." + - question: "What is your current burn multiple, and how has it changed over the + last two quarters?" + purpose: "A rising burn multiple despite investment means the growth engine is + losing efficiency — the company is spending more to grow less." + routing_impact: "Burn multiple above 3x routes to efficiency analysis and + scenario-planning for runway management." diagnosis_weight_shifts: more_likely: - diagnosis: "Channel saturation" - reason: "SaaS companies often exhaust their initial growth channel (content, outbound, product-led) and need to build new channels. The stall occurs at the point of channel maturity." + reason: "SaaS companies often exhaust their initial growth channel (content, + outbound, product-led) and need to build new channels. The stall + occurs at the point of channel maturity." - diagnosis: "Market segment ceiling" - reason: "SaaS products often saturate their initial market segment (e.g., 'startups under 50 employees') and must expand to adjacent segments (mid-market, enterprise) to sustain growth." + reason: "SaaS products often saturate their initial market segment (e.g., + 'startups under 50 employees') and must expand to adjacent segments + (mid-market, enterprise) to sustain growth." less_likely: - diagnosis: "Macro-economic demand decline" - reason: "SaaS demand is relatively resilient to economic cycles — IT budgets are the last to be cut. A growth stall attributed to 'the market' is usually a competitive or execution problem." + reason: "SaaS demand is relatively resilient to economic cycles — IT budgets are + the last to be cut. A growth stall attributed to 'the market' is + usually a competitive or execution problem." saas_specific_diagnoses: - name: "Product-led growth ceiling" - description: "The company's PLG motion is stalling because it has reached the limit of users who will self-serve through a free trial or freemium product. Growth requires adding a sales-assisted or enterprise motion, which the company has not built." + description: "The company's PLG motion is stalling because it has reached the + limit of users who will self-serve through a free trial or freemium + product. Growth requires adding a sales-assisted or enterprise motion, + which the company has not built." symptoms: - "Self-serve sign-ups plateau despite increasing marketing spend" - "Trial-to-paid conversion rate declining" - - "Inbound leads requesting enterprise features (SSO, admin controls, custom integrations) that the product does not offer" + - "Inbound leads requesting enterprise features (SSO, admin controls, + custom integrations) that the product does not offer" - "Average deal size capped at the self-serve pricing tier" - routes_to_skills: ["blue-ocean-strategy", "product-life-cycle", "business-model-canvas"] - routes_to_templates: ["strategic-analysis-one-pager", "new-initiative-brief"] + routes_to_skills: [ "blue-ocean-strategy", "product-life-cycle", "business-model-canvas" ] + routes_to_templates: [ "strategic-analysis-one-pager", "new-initiative-brief" ] - name: "Net-new ARR dependency" - description: "Growth is entirely dependent on acquiring new customers because the existing base is not expanding. This is unsustainable because CAC increases as the addressable market for new logos diminishes." + description: "Growth is entirely dependent on acquiring new customers because + the existing base is not expanding. This is unsustainable because CAC + increases as the addressable market for new logos diminishes." symptoms: - "Expansion revenue below 15% of total new MRR" - "NRR between 95-105% despite strong logo retention" - "No usage-based or per-seat pricing that enables organic expansion" - "Customer success team focused on retention only, not growth" - routes_to_skills: ["pricing-diagnosis", "four-ps-marketing", "net-promoter-score"] - routes_to_templates: ["unit-economics-snapshot", "quarterly-strategic-review"] + routes_to_skills: + - four-ps-marketing + - net-promoter-score + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - - "MoM growth decelerating for 3+ consecutive months without a clear seasonal explanation." - - "CAC Payback Period extending beyond 18 months — the growth engine is becoming capital-inefficient." - - "Magic Number below 0.5 — GTM spend is not converting to revenue efficiently." + - "MoM growth decelerating for 3+ consecutive months without a clear + seasonal explanation." + - "CAC Payback Period extending beyond 18 months — the growth engine is + becoming capital-inefficient." + - "Magic Number below 0.5 — GTM spend is not converting to revenue + efficiently." # ───────────────────────────────────────────── # 3. PRODUCT-MARKET FIT DIAGNOSIS @@ -138,36 +219,68 @@ diagnostic_rules: - diagnostic: "product-market-fit-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS has the richest quantitative signals for product-market fit of any business model. Retention curves, NPS segmentation, and organic growth data provide objective PMF measurement that the base diagnostic should incorporate." + adaptation_rationale: "SaaS has the richest quantitative signals for + product-market fit of any business model. Retention curves, NPS + segmentation, and organic growth data provide objective PMF measurement + that the base diagnostic should incorporate." additional_triage_questions: - - question: "What does your retention curve look like — does it flatten (users who stay past month 3 stay long-term) or does it continue declining (users never stop leaving)?" - purpose: "A flattening retention curve is the single strongest quantitative signal of product-market fit. A continuously declining curve means PMF has not been achieved regardless of other signals." - routing_impact: "Flattening curve with low initial retention routes to onboarding optimization. Continuously declining curve routes to fundamental PMF exploration — the product may need a pivot." - - question: "What percentage of your growth is organic (word-of-mouth, direct traffic) versus paid?" - purpose: "Organic growth above 40% is a strong PMF signal — customers are recommending the product without incentives. Below 20% suggests the product is not generating advocacy." - routing_impact: "Low organic growth routes to net-promoter-score analysis and product-value assessment. High organic growth with slow total growth routes to distribution strategy, not product changes." + - question: "What does your retention curve look like — does it flatten (users who + stay past month 3 stay long-term) or does it continue declining (users + never stop leaving)?" + purpose: "A flattening retention curve is the single strongest quantitative + signal of product-market fit. A continuously declining curve means PMF + has not been achieved regardless of other signals." + routing_impact: "Flattening curve with low initial retention routes to + onboarding optimization. Continuously declining curve routes to + fundamental PMF exploration — the product may need a pivot." + - question: "What percentage of your growth is organic (word-of-mouth, direct + traffic) versus paid?" + purpose: "Organic growth above 40% is a strong PMF signal — customers are + recommending the product without incentives. Below 20% suggests the + product is not generating advocacy." + routing_impact: "Low organic growth routes to net-promoter-score analysis and + product-value assessment. High organic growth with slow total growth + routes to distribution strategy, not product changes." diagnosis_weight_shifts: more_likely: - diagnosis: "PMF exists for a niche but the company is targeting too broadly" - reason: "SaaS companies frequently have strong PMF in one segment (e.g., 'marketing agencies under 20 people') but dilute it by trying to serve everyone." + reason: "SaaS companies frequently have strong PMF in one segment (e.g., + 'marketing agencies under 20 people') but dilute it by trying to + serve everyone." - diagnosis: "PMF existed but the market has shifted" - reason: "SaaS markets evolve rapidly. PMF is not permanent — what the market needed two years ago may be table stakes today." + reason: "SaaS markets evolve rapidly. PMF is not permanent — what the market + needed two years ago may be table stakes today." less_likely: - diagnosis: "Product is fundamentally flawed" - reason: "If any customers retain long-term and expand, the product works for someone. The question is usually not 'does the product work?' but 'for whom does it work?'" + reason: "If any customers retain long-term and expand, the product works for + someone. The question is usually not 'does the product work?' but + 'for whom does it work?'" saas_specific_diagnoses: - name: "PMF for the wrong segment" - description: "The product has strong retention and NPS among a small segment, but the company is investing sales and marketing spend to acquire customers in a different, larger segment where the product does not resonate." + description: "The product has strong retention and NPS among a small segment, + but the company is investing sales and marketing spend to acquire + customers in a different, larger segment where the product does not + resonate." symptoms: - - "NPS above 50 for one segment but below 20 for the segment receiving the most marketing spend" - - "High churn among recently acquired customers but low churn among early adopters" - - "Customer success team spending disproportionate time on customers who do not match the ideal profile" - routes_to_skills: ["blue-ocean-strategy", "business-model-canvas", "defining-and-exploring-problems"] - routes_to_templates: ["strategic-analysis-one-pager", "market-opportunity-summary"] + - "NPS above 50 for one segment but below 20 for the segment receiving + the most marketing spend" + - "High churn among recently acquired customers but low churn among + early adopters" + - "Customer success team spending disproportionate time on customers + who do not match the ideal profile" + routes_to_skills: + [ + "blue-ocean-strategy", + "business-model-canvas", + "defining-and-exploring-problems" + ] + routes_to_templates: [ "strategic-analysis-one-pager", "market-opportunity-summary" ] sector_red_flags: - - "Retention curve that never flattens — a continuous decline regardless of cohort vintage." + - "Retention curve that never flattens — a continuous decline regardless + of cohort vintage." - "NPS below 20 after 12 months in market — customers are not advocating." - - "Organic growth below 15% of total acquisition — the product relies entirely on paid channels to grow." + - "Organic growth below 15% of total acquisition — the product relies + entirely on paid channels to grow." # ───────────────────────────────────────────── # 4. PRICING DIAGNOSIS @@ -175,40 +288,78 @@ diagnostic_rules: - diagnostic: "pricing-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Pricing in SaaS is fundamentally different from pricing in other businesses. The subscription model, the availability of real-time usage data, and the direct relationship between pricing structure and retention/expansion dynamics make this diagnostic significantly more complex in SaaS." + adaptation_rationale: "Pricing in SaaS is fundamentally different from pricing + in other businesses. The subscription model, the availability of real-time + usage data, and the direct relationship between pricing structure and + retention/expansion dynamics make this diagnostic significantly more + complex in SaaS." additional_triage_questions: - - question: "Does your pricing structure create natural expansion revenue — do customers pay more as they get more value, or do they pay the same regardless of usage and team size?" - purpose: "Flat-rate pricing that does not scale with value received leaves expansion revenue on the table and creates a ceiling on per-account revenue." - routing_impact: "No expansion mechanism routes to pricing restructure using value-metric analysis. Existing expansion mechanism with low expansion rate routes to packaging and tier optimization." - - question: "What is the ratio of your annual price to the monthly price x 12? What percentage of customers choose annual?" - purpose: "A standard annual discount of 15-20% should drive 30-50% annual adoption. Low annual adoption suggests the discount is insufficient or customers lack confidence in long-term value." - routing_impact: "Very low annual adoption routes to both pricing adjustment (increase annual discount) and product-market-fit concerns (customers may not trust long-term value)." - - question: "When was the last time you raised prices, and what happened to churn when you did?" - purpose: "SaaS companies that have never raised prices or raised prices more than 24 months ago are almost certainly under-pricing. The churn impact of price increases is usually far lower than founders fear." - routing_impact: "Never raised prices routes to immediate pricing analysis with willingness-to-pay research. Raised prices with no churn impact routes to further increases." + - question: "Does your pricing structure create natural expansion revenue — do + customers pay more as they get more value, or do they pay the same + regardless of usage and team size?" + purpose: "Flat-rate pricing that does not scale with value received leaves + expansion revenue on the table and creates a ceiling on per-account + revenue." + routing_impact: "No expansion mechanism routes to pricing restructure using + value-metric analysis. Existing expansion mechanism with low expansion + rate routes to packaging and tier optimization." + - question: "What is the ratio of your annual price to the monthly price x 12? + What percentage of customers choose annual?" + purpose: "A standard annual discount of 15-20% should drive 30-50% annual + adoption. Low annual adoption suggests the discount is insufficient or + customers lack confidence in long-term value." + routing_impact: "Very low annual adoption routes to both pricing adjustment + (increase annual discount) and product-market-fit concerns (customers + may not trust long-term value)." + - question: "When was the last time you raised prices, and what happened to churn + when you did?" + purpose: "SaaS companies that have never raised prices or raised prices more + than 24 months ago are almost certainly under-pricing. The churn + impact of price increases is usually far lower than founders fear." + routing_impact: "Never raised prices routes to immediate pricing analysis with + willingness-to-pay research. Raised prices with no churn impact routes + to further increases." diagnosis_weight_shifts: more_likely: - diagnosis: "Under-pricing" - reason: "The default error in SaaS is under-pricing. Founders fear losing customers but studies consistently show SaaS companies capture only 10-20% of the value they deliver." + reason: "The default error in SaaS is under-pricing. Founders fear losing + customers but studies consistently show SaaS companies capture only + 10-20% of the value they deliver." - diagnosis: "Value metric misalignment" - reason: "Charging per seat when the value scales with usage (or vice versa) creates friction and caps revenue. The value metric must align with how customers derive value." + reason: "Charging per seat when the value scales with usage (or vice versa) + creates friction and caps revenue. The value metric must align with + how customers derive value." less_likely: - diagnosis: "Over-pricing relative to competition" - reason: "Over-pricing is less common than founders think. Losing deals on price often reflects poor value communication, not excessive pricing." + reason: "Over-pricing is less common than founders think. Losing deals on price + often reflects poor value communication, not excessive pricing." saas_specific_diagnoses: - name: "Flat-rate trap" - description: "The company charges a single monthly price regardless of usage intensity, team size, or value received. This caps per-account revenue and creates a class of power users who are massively under-paying relative to the value they extract." + description: "The company charges a single monthly price regardless of usage + intensity, team size, or value received. This caps per-account revenue + and creates a class of power users who are massively under-paying + relative to the value they extract." symptoms: - "ARPU flat or declining despite product improvements" - "Expansion revenue below 10% of new MRR" - - "Some customers using 100x more resources than others at the same price" - - "Large customers asking for features but unwilling to pay more because they are already on the 'everything' plan" - routes_to_skills: ["four-ps-marketing", "business-model-canvas", "pricing-diagnosis"] - routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + - "Some customers using 100x more resources than others at the same + price" + - "Large customers asking for features but unwilling to pay more + because they are already on the 'everything' plan" + routes_to_skills: + - four-ps-marketing + - business-model-canvas + routes_to_templates: [ "unit-economics-snapshot", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis sector_red_flags: - "Pricing unchanged for more than 18 months in a growing product." - - "ARPU declining quarter-over-quarter — a sign of downward pricing pressure or adverse selection." - - "Win rate analysis showing price as the primary loss reason in more than 30% of losses — may indicate a value communication problem rather than a price problem." + - "ARPU declining quarter-over-quarter — a sign of downward pricing + pressure or adverse selection." + - "Win rate analysis showing price as the primary loss reason in more than + 30% of losses — may indicate a value communication problem rather than a + price problem." # ───────────────────────────────────────────── # 5. FUNDRAISING DIAGNOSIS @@ -216,36 +367,68 @@ diagnostic_rules: - diagnostic: "fundraising-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS fundraising has the most standardized benchmarks of any sector. Investors apply well-known thresholds for each round, and SaaS metrics are the lingua franca of venture capital. The diagnostic benefits from surfacing these specific benchmarks." + adaptation_rationale: "SaaS fundraising has the most standardized benchmarks of + any sector. Investors apply well-known thresholds for each round, and SaaS + metrics are the lingua franca of venture capital. The diagnostic benefits + from surfacing these specific benchmarks." additional_triage_questions: - - question: "What are your current ARR, MoM growth rate, NRR, and months of runway?" - purpose: "These four metrics are the primary inputs to SaaS fundraising readiness. Investors can make a rapid initial assessment from these alone." - routing_impact: "Metrics below Series A thresholds (ARR < $1M, growth < 10% MoM, NRR < 100%) route to pre-fundraising skill-building. Metrics above thresholds route to fundraising execution." - - question: "Can you articulate your unit economics — specifically LTV:CAC ratio and CAC payback period — with data?" - purpose: "Unit economics literacy is a gating criterion for SaaS fundraising. Founders who cannot answer this question are not ready to raise." - routing_impact: "Cannot articulate routes to unit-economics-snapshot template and balanced-scorecard skill for metric foundation. Can articulate routes to fundraising-deck-outline and investor-update-email." + - question: "What are your current ARR, MoM growth rate, NRR, and months of + runway?" + purpose: "These four metrics are the primary inputs to SaaS fundraising + readiness. Investors can make a rapid initial assessment from these + alone." + routing_impact: "Metrics below Series A thresholds (ARR < $1M, growth < 10% MoM, + NRR < 100%) route to pre-fundraising skill-building. Metrics above + thresholds route to fundraising execution." + - question: "Can you articulate your unit economics — specifically LTV:CAC ratio + and CAC payback period — with data?" + purpose: "Unit economics literacy is a gating criterion for SaaS fundraising. + Founders who cannot answer this question are not ready to raise." + routing_impact: "Cannot articulate routes to unit-economics-snapshot template + and balanced-scorecard skill for metric foundation. Can articulate + routes to fundraising-deck-outline and investor-update-email." diagnosis_weight_shifts: more_likely: - diagnosis: "Timing mismatch" - reason: "SaaS companies frequently try to raise too early (pre-PMF) or during a metrics trough (seasonal churn, post-pricing-change dip). Timing is the most controllable fundraising variable." + reason: "SaaS companies frequently try to raise too early (pre-PMF) or during a + metrics trough (seasonal churn, post-pricing-change dip). Timing is + the most controllable fundraising variable." - diagnosis: "Narrative-metrics disconnect" - reason: "SaaS founders who tell a story that does not match their metrics face immediate credibility challenges. Investors cross-reference the narrative against the numbers in real time." + reason: "SaaS founders who tell a story that does not match their metrics face + immediate credibility challenges. Investors cross-reference the + narrative against the numbers in real time." less_likely: - diagnosis: "Market too small" - reason: "SaaS total addressable markets are generally large enough for venture returns. The 'market too small' objection usually means the company has not articulated the expansion path convincingly." + reason: "SaaS total addressable markets are generally large enough for venture + returns. The 'market too small' objection usually means the company + has not articulated the expansion path convincingly." saas_specific_diagnoses: - name: "Metrics-ready but narrative-deficient" - description: "The company's SaaS metrics meet or exceed benchmarks for the target round, but the founder cannot articulate a compelling narrative about market opportunity, competitive differentiation, and the path to category leadership." + description: "The company's SaaS metrics meet or exceed benchmarks for the + target round, but the founder cannot articulate a compelling narrative + about market opportunity, competitive differentiation, and the path to + category leadership." symptoms: - - "Initial investor meetings generate interest based on metrics but no follow-up" - - "Investor feedback centers on 'market' and 'vision' rather than 'execution' or 'metrics'" - - "Pitch deck is dense with data but lacks a coherent strategic narrative" - routes_to_skills: ["story-structure-and-arc", "strategic-thinking-and-alignment", "blue-ocean-strategy"] - routes_to_templates: ["fundraising-deck-outline", "market-opportunity-summary"] + - "Initial investor meetings generate interest based on metrics but no + follow-up" + - "Investor feedback centers on 'market' and 'vision' rather than + 'execution' or 'metrics'" + - "Pitch deck is dense with data but lacks a coherent strategic + narrative" + routes_to_skills: + [ + "story-structure-and-arc", + "strategic-thinking-and-alignment", + "blue-ocean-strategy" + ] + routes_to_templates: [ "fundraising-deck-outline", "market-opportunity-summary" ] sector_red_flags: - - "Raising with less than 6 months of runway — desperation weakens negotiating position and signals poor planning." - - "Raising at a valuation more than 100x ARR without hypergrowth metrics to justify it." - - "Raising without a clear use-of-proceeds plan tied to specific growth milestones." + - "Raising with less than 6 months of runway — desperation weakens + negotiating position and signals poor planning." + - "Raising at a valuation more than 100x ARR without hypergrowth metrics + to justify it." + - "Raising without a clear use-of-proceeds plan tied to specific growth + milestones." # ───────────────────────────────────────────── # 6. REVENUE DIAGNOSIS @@ -253,35 +436,59 @@ diagnostic_rules: - diagnostic: "revenue-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Revenue in SaaS decomposes into precise, measurable components (new, expansion, contraction, churn) that the base revenue diagnostic should leverage. The SaaS overlay adds component-level triage." + adaptation_rationale: "Revenue in SaaS decomposes into precise, measurable + components (new, expansion, contraction, churn) that the base revenue + diagnostic should leverage. The SaaS overlay adds component-level triage." additional_triage_questions: - - question: "Break down your MRR into five components: new MRR, expansion MRR, reactivation MRR, contraction MRR, and churned MRR. Which components are trending in the wrong direction?" - purpose: "SaaS revenue problems always trace to specific MRR components. This decomposition identifies the precise failure point rather than treating 'revenue' as a monolithic problem." - routing_impact: "New MRR declining routes to GTM diagnosis. Expansion MRR flat routes to pricing-diagnosis. Contraction rising routes to product-value analysis. Churn rising routes to customer-churn-diagnosis." - - question: "What is your SaaS Quick Ratio — the ratio of revenue inflows (new + expansion) to revenue outflows (contraction + churn)?" - purpose: "The Quick Ratio reveals the growth quality. A Quick Ratio below 2 means the business is fragile — a small increase in churn can tip it into contraction." - routing_impact: "Quick Ratio below 2 routes to simultaneous churn reduction and growth acceleration. Above 4 routes to growth investment with confidence." + - question: "Break down your MRR into five components: new MRR, expansion MRR, + reactivation MRR, contraction MRR, and churned MRR. Which components + are trending in the wrong direction?" + purpose: "SaaS revenue problems always trace to specific MRR components. This + decomposition identifies the precise failure point rather than + treating 'revenue' as a monolithic problem." + routing_impact: "New MRR declining routes to GTM diagnosis. Expansion MRR flat + routes to pricing-diagnosis. Contraction rising routes to + product-value analysis. Churn rising routes to + customer-churn-diagnosis." + - question: "What is your SaaS Quick Ratio — the ratio of revenue inflows (new + + expansion) to revenue outflows (contraction + churn)?" + purpose: "The Quick Ratio reveals the growth quality. A Quick Ratio below 2 + means the business is fragile — a small increase in churn can tip it + into contraction." + routing_impact: "Quick Ratio below 2 routes to simultaneous churn reduction and + growth acceleration. Above 4 routes to growth investment with + confidence." diagnosis_weight_shifts: more_likely: - diagnosis: "Expansion revenue underperformance" - reason: "Most SaaS companies under-invest in expansion relative to new customer acquisition. Expansion is typically more capital-efficient but receives less organizational focus." + reason: "Most SaaS companies under-invest in expansion relative to new customer + acquisition. Expansion is typically more capital-efficient but + receives less organizational focus." less_likely: - diagnosis: "Market pricing pressure" - reason: "True market-wide pricing pressure in SaaS is rare. Most pricing problems are company-specific — poor packaging, weak value communication, or excessive discounting." + reason: "True market-wide pricing pressure in SaaS is rare. Most pricing + problems are company-specific — poor packaging, weak value + communication, or excessive discounting." saas_specific_diagnoses: - name: "Revenue quality deterioration" - description: "Total revenue is growing but the composition is shifting toward lower-quality revenue: more monthly customers (higher churn risk), more heavily discounted deals (lower LTV), or more professional services revenue (lower margin)." + description: "Total revenue is growing but the composition is shifting toward + lower-quality revenue: more monthly customers (higher churn risk), + more heavily discounted deals (lower LTV), or more professional + services revenue (lower margin)." symptoms: - "Revenue growing but gross margin declining" - "Percentage of annual contracts declining" - "Average discount increasing quarter-over-quarter" - - "Professional services revenue growing faster than subscription revenue" - routes_to_skills: ["balanced-scorecard", "business-model-canvas"] - routes_to_templates: ["unit-economics-snapshot", "quarterly-strategic-review"] + - "Professional services revenue growing faster than subscription + revenue" + routes_to_skills: [ "balanced-scorecard", "business-model-canvas" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] sector_red_flags: - "Monthly revenue churn exceeding 3% for three consecutive months." - - "Revenue growth decelerating while sales team size is increasing — a productivity problem." - - "Gross margin declining below 70% — the business may be shifting from software to services economics." + - "Revenue growth decelerating while sales team size is increasing — a + productivity problem." + - "Gross margin declining below 70% — the business may be shifting from + software to services economics." # ───────────────────────────────────────────── # 7. COMPETITIVE THREAT DIAGNOSIS @@ -289,34 +496,62 @@ diagnostic_rules: - diagnostic: "competitive-threat-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS competitive dynamics are uniquely intense due to low switching costs, transparent pricing, public feature comparisons (G2, Capterra), and the ability of competitors to iterate rapidly. The base diagnostic benefits from SaaS-specific competitive threat categories." + adaptation_rationale: "SaaS competitive dynamics are uniquely intense due to low + switching costs, transparent pricing, public feature comparisons (G2, + Capterra), and the ability of competitors to iterate rapidly. The base + diagnostic benefits from SaaS-specific competitive threat categories." additional_triage_questions: - - question: "Is the competitive threat from a direct competitor (same category, same segment), a platform expanding into your space (e.g., Salesforce, HubSpot, Microsoft adding your feature), or a new technology paradigm (AI tools replacing your product's function)?" - purpose: "Each threat type requires a different response. Direct competitors require differentiation. Platform expansion requires ecosystem strategy. Paradigm shifts require reinvention." - routing_impact: "Direct competitor routes to porters-five-forces and competitive-negotiation. Platform threat routes to first-mover-strategy and prisoners-dilemma-and-cooperation. Paradigm threat routes to disruptive-innovation and ai-vision-and-strategy." + - question: "Is the competitive threat from a direct competitor (same category, + same segment), a platform expanding into your space (e.g., Salesforce, + HubSpot, Microsoft adding your feature), or a new technology paradigm + (AI tools replacing your product's function)?" + purpose: "Each threat type requires a different response. Direct competitors + require differentiation. Platform expansion requires ecosystem + strategy. Paradigm shifts require reinvention." + routing_impact: "Direct competitor routes to porters-five-forces and + competitive-negotiation. Platform threat routes to + first-mover-strategy and prisoners-dilemma-and-cooperation. Paradigm + threat routes to disruptive-innovation and ai-vision-and-strategy." diagnosis_weight_shifts: more_likely: - diagnosis: "Platform encroachment" - reason: "The greatest competitive threat to most SaaS companies is not a peer startup but a platform (Microsoft, Google, Salesforce, HubSpot) adding their feature natively. This threat is existential and underestimated." + reason: "The greatest competitive threat to most SaaS companies is not a peer + startup but a platform (Microsoft, Google, Salesforce, HubSpot) + adding their feature natively. This threat is existential and + underestimated." - diagnosis: "AI-driven category disruption" - reason: "General-purpose AI tools are replacing specialized SaaS products in categories like writing, data analysis, code generation, and customer support. This is the defining competitive threat of 2024-2026." + reason: "General-purpose AI tools are replacing specialized SaaS products in + categories like writing, data analysis, code generation, and + customer support. This is the defining competitive threat of + 2024-2026." less_likely: - diagnosis: "Price-based competitive displacement" - reason: "SaaS customers rarely switch primarily on price. They switch on value, experience, and capability. A competitor winning on price alone is usually winning on something else that the company is not seeing." + reason: "SaaS customers rarely switch primarily on price. They switch on value, + experience, and capability. A competitor winning on price alone is + usually winning on something else that the company is not seeing." saas_specific_diagnoses: - name: "Feature-parity treadmill" - description: "The company is caught in a cycle of copying competitor features rather than differentiating. Each quarter's roadmap is driven by competitive gap analysis rather than customer value creation, leading to a undifferentiated product that competes solely on price." + description: "The company is caught in a cycle of copying competitor features + rather than differentiating. Each quarter's roadmap is driven by + competitive gap analysis rather than customer value creation, leading + to a undifferentiated product that competes solely on price." symptoms: - "Product roadmap dominated by 'competitive parity' items" - - "Win/loss analysis showing 'features' as the primary win reason (not differentiation or value)" - - "Engineering team demoralized by building features they know are copies" - - "Pricing under pressure because the product is perceived as interchangeable" - routes_to_skills: ["blue-ocean-strategy", "disruptive-innovation", "porters-five-forces"] - routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + - "Win/loss analysis showing 'features' as the primary win reason (not + differentiation or value)" + - "Engineering team demoralized by building features they know are + copies" + - "Pricing under pressure because the product is perceived as + interchangeable" + routes_to_skills: [ "blue-ocean-strategy", "disruptive-innovation", "porters-five-forces" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] sector_red_flags: - - "Win rate declining for three consecutive quarters without a clear product or pricing explanation." - - "A platform partner announcing a native feature that overlaps with your core value proposition." - - "A well-funded competitor (raised $50M+) entering your specific market segment." + - "Win rate declining for three consecutive quarters without a clear + product or pricing explanation." + - "A platform partner announcing a native feature that overlaps with your + core value proposition." + - "A well-funded competitor (raised $50M+) entering your specific market + segment." # ───────────────────────────────────────────── # 8. STRATEGIC DRIFT DIAGNOSIS @@ -324,31 +559,50 @@ diagnostic_rules: - diagnostic: "strategic-drift-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS strategic drift manifests as a misalignment between product, GTM, pricing, and customer success strategies. The fast feedback loops in SaaS make drift detectable earlier than in traditional businesses but also make it more tempting to constantly shift direction." + adaptation_rationale: "SaaS strategic drift manifests as a misalignment between + product, GTM, pricing, and customer success strategies. The fast feedback + loops in SaaS make drift detectable earlier than in traditional businesses + but also make it more tempting to constantly shift direction." additional_triage_questions: - - question: "Is your product roadmap aligned with your highest-retention customer segment, or is it being pulled in multiple directions by different customer types?" - purpose: "SaaS strategic drift often begins when the product tries to serve too many segments simultaneously, building features for enterprise while the core SMB base decays." - routing_impact: "Multi-segment pull routes to business-model-canvas for segment clarification and strategic-thinking-and-alignment for organizational focus." + - question: "Is your product roadmap aligned with your highest-retention customer + segment, or is it being pulled in multiple directions by different + customer types?" + purpose: "SaaS strategic drift often begins when the product tries to serve too + many segments simultaneously, building features for enterprise while + the core SMB base decays." + routing_impact: "Multi-segment pull routes to business-model-canvas for segment + clarification and strategic-thinking-and-alignment for organizational + focus." diagnosis_weight_shifts: more_likely: - diagnosis: "Strategy-by-customer-request" - reason: "SaaS companies are uniquely vulnerable to building whatever the loudest customer asks for, especially when that customer represents a significant portion of revenue." + reason: "SaaS companies are uniquely vulnerable to building whatever the loudest + customer asks for, especially when that customer represents a + significant portion of revenue." less_likely: - diagnosis: "Industry disruption causing drift" - reason: "More often, drift in SaaS is self-inflicted (chasing every opportunity) rather than externally caused." + reason: "More often, drift in SaaS is self-inflicted (chasing every opportunity) + rather than externally caused." saas_specific_diagnoses: - name: "Premature upmarket drift" - description: "The company moves upmarket to pursue larger deals before establishing dominance in its initial segment. Enterprise features are added at the expense of the core product, the sales cycle lengthens, and the company ends up competing in a market where it has no advantage against established players." + description: "The company moves upmarket to pursue larger deals before + establishing dominance in its initial segment. Enterprise features are + added at the expense of the core product, the sales cycle lengthens, + and the company ends up competing in a market where it has no + advantage against established players." symptoms: - "ACV increasing but total customer count and growth rate declining" - "Sales cycle doubling while win rate halves" - - "Product complexity increasing, onboarding time growing, self-serve adoption declining" + - "Product complexity increasing, onboarding time growing, self-serve + adoption declining" - "Core customer segment NPS declining" - routes_to_skills: ["disruptive-innovation", "blue-ocean-strategy", "product-life-cycle"] - routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + routes_to_skills: [ "disruptive-innovation", "blue-ocean-strategy", "product-life-cycle" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] sector_red_flags: - - "Roadmap items traceable to fewer than 3 customer requests each — building for individuals rather than segments." - - "Go-to-market strategy changing more than once per year without a corresponding change in metrics." + - "Roadmap items traceable to fewer than 3 customer requests each — + building for individuals rather than segments." + - "Go-to-market strategy changing more than once per year without a + corresponding change in metrics." # ───────────────────────────────────────────── # 9. TEAM DYSFUNCTION DIAGNOSIS @@ -356,31 +610,52 @@ diagnostic_rules: - diagnostic: "team-dysfunction-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS team dysfunction has characteristic patterns driven by the cross-functional nature of the business — product, engineering, sales, marketing, and customer success must coordinate tightly, and the seams between these functions are where dysfunction most commonly appears." + adaptation_rationale: "SaaS team dysfunction has characteristic patterns driven + by the cross-functional nature of the business — product, engineering, + sales, marketing, and customer success must coordinate tightly, and the + seams between these functions are where dysfunction most commonly + appears." additional_triage_questions: - - question: "Is there tension between the sales team and the product team — specifically, is sales selling features that do not exist or will the product team not build what customers are asking for?" - purpose: "The sales-product tension is the most common and most damaging team dysfunction in SaaS. It leads to customer dissatisfaction, missed targets, and organizational distrust." - routing_impact: "Sales-product misalignment routes to strategic-thinking-and-alignment and cooperative-negotiation for internal alignment processes." + - question: "Is there tension between the sales team and the product team — + specifically, is sales selling features that do not exist or will the + product team not build what customers are asking for?" + purpose: "The sales-product tension is the most common and most damaging team + dysfunction in SaaS. It leads to customer dissatisfaction, missed + targets, and organizational distrust." + routing_impact: "Sales-product misalignment routes to + strategic-thinking-and-alignment and cooperative-negotiation for + internal alignment processes." diagnosis_weight_shifts: more_likely: - diagnosis: "Cross-functional misalignment" - reason: "SaaS requires tighter cross-functional coordination than most businesses. The handoffs between marketing-sales, sales-CS, product-engineering, and CS-product are common failure points." + reason: "SaaS requires tighter cross-functional coordination than most + businesses. The handoffs between marketing-sales, sales-CS, + product-engineering, and CS-product are common failure points." less_likely: - diagnosis: "Individual performance issues" - reason: "What appears as individual underperformance in SaaS is often a system-level problem — poor tools, unclear processes, or misaligned incentives. Diagnose the system before blaming the individual." + reason: "What appears as individual underperformance in SaaS is often a + system-level problem — poor tools, unclear processes, or misaligned + incentives. Diagnose the system before blaming the individual." saas_specific_diagnoses: - name: "Sales-CS handoff failure" - description: "Customers are sold on expectations that customer success cannot deliver. The handoff from sales to CS loses critical context, implementation timelines are unrealistic, and customer dissatisfaction spikes in the first 90 days of the relationship." + description: "Customers are sold on expectations that customer success cannot + deliver. The handoff from sales to CS loses critical context, + implementation timelines are unrealistic, and customer dissatisfaction + spikes in the first 90 days of the relationship." symptoms: - "High churn concentrated in the first 90 days post-close" - - "CSMs reporting that customer expectations do not match what was sold" + - "CSMs reporting that customer expectations do not match what was + sold" - "Sales team compensated only on bookings with no retention clawback" - - "No mutual success plan or implementation timeline created during the sales process" - routes_to_skills: ["trust-equation", "systems-thinking", "delegation-and-empowerment"] - routes_to_templates: ["action-plan", "onboarding-welcome-packet"] + - "No mutual success plan or implementation timeline created during + the sales process" + routes_to_skills: [ "trust-equation", "systems-thinking", "delegation-and-empowerment" ] + routes_to_templates: [ "action-plan", "onboarding-welcome-packet" ] sector_red_flags: - - "Engineering team velocity declining while headcount increases — often a sign of organizational overhead or architectural debt." - - "Customer success team attrition above 30% annually — CSMs burn out when they cannot influence the product that causes customer complaints." + - "Engineering team velocity declining while headcount increases — often a + sign of organizational overhead or architectural debt." + - "Customer success team attrition above 30% annually — CSMs burn out when + they cannot influence the product that causes customer complaints." # ───────────────────────────────────────────── # 10. COFOUNDER CONFLICT DIAGNOSIS @@ -388,27 +663,48 @@ diagnostic_rules: - diagnostic: "cofounder-conflict-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "Co-founder conflict in SaaS often centers on technical vs. commercial priorities — the CTO wants to rebuild the architecture while the CEO wants to ship features for sales. SaaS-specific triage helps identify whether the conflict is about direction (strategy) or execution (roles and authority)." + adaptation_rationale: "Co-founder conflict in SaaS often centers on technical + vs. commercial priorities — the CTO wants to rebuild the architecture + while the CEO wants to ship features for sales. SaaS-specific triage helps + identify whether the conflict is about direction (strategy) or execution + (roles and authority)." additional_triage_questions: - - question: "Does the conflict center on product direction (what to build), go-to-market strategy (how to sell), resource allocation (where to invest), or equity/compensation (what each person deserves)?" - purpose: "SaaS co-founder conflicts cluster around these four categories. Each has different resolution paths." - routing_impact: "Product direction conflicts route to defining-and-exploring-problems and customer data analysis. GTM conflicts route to balanced-scorecard and data-driven evaluation. Resource conflicts route to scenario-planning. Equity conflicts route to negotiation skills." + - question: "Does the conflict center on product direction (what to build), + go-to-market strategy (how to sell), resource allocation (where to + invest), or equity/compensation (what each person deserves)?" + purpose: "SaaS co-founder conflicts cluster around these four categories. Each + has different resolution paths." + routing_impact: "Product direction conflicts route to + defining-and-exploring-problems and customer data analysis. GTM + conflicts route to balanced-scorecard and data-driven evaluation. + Resource conflicts route to scenario-planning. Equity conflicts route + to negotiation skills." diagnosis_weight_shifts: more_likely: - diagnosis: "Role ambiguity between technical and commercial co-founders" - reason: "SaaS companies with a CEO/CTO co-founder pair frequently struggle with the boundary between product decisions (shared) and technical architecture decisions (CTO) and commercial decisions (CEO)." + reason: "SaaS companies with a CEO/CTO co-founder pair frequently struggle with + the boundary between product decisions (shared) and technical + architecture decisions (CTO) and commercial decisions (CEO)." less_likely: - diagnosis: "Fundamental vision misalignment" - reason: "True vision misalignment is less common than role boundary confusion. Most co-founders agree on the destination but disagree on the path." + reason: "True vision misalignment is less common than role boundary confusion. + Most co-founders agree on the destination but disagree on the path." saas_specific_diagnoses: - name: "Build-vs-sell tension" - description: "The technical co-founder wants to invest in product quality, architecture, and technical debt reduction. The commercial co-founder wants to invest in sales, marketing, and customer-facing features. Neither is wrong — but the inability to allocate resources creates paralysis and resentment." + description: "The technical co-founder wants to invest in product quality, + architecture, and technical debt reduction. The commercial co-founder + wants to invest in sales, marketing, and customer-facing features. + Neither is wrong — but the inability to allocate resources creates + paralysis and resentment." symptoms: - - "Product roadmap alternating between 'technical debt sprints' and 'sales-driven feature rushes' without a coherent strategy" - - "Co-founders advocating in board meetings against each other's priorities" - - "Team members learning to route requests to the more sympathetic co-founder" - routes_to_skills: ["cooperative-negotiation", "balanced-scorecard", "evaluating-and-deciding"] - routes_to_templates: ["decision-journal", "quarterly-strategic-review"] + - "Product roadmap alternating between 'technical debt sprints' and + 'sales-driven feature rushes' without a coherent strategy" + - "Co-founders advocating in board meetings against each other's + priorities" + - "Team members learning to route requests to the more sympathetic + co-founder" + routes_to_skills: [ "cooperative-negotiation", "balanced-scorecard", "evaluating-and-deciding" ] + routes_to_templates: [ "decision-journal", "quarterly-strategic-review" ] sector_red_flags: - "Co-founders communicating through intermediaries rather than directly." - "Key hires leaving because of conflicting direction from co-founders." @@ -419,30 +715,47 @@ diagnostic_rules: - diagnostic: "market-entry-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS market entry is primarily about segment selection and GTM motion — the product can reach any market digitally, so the question is not 'can we enter?' but 'should we enter, and how?' SaaS-specific triage focuses on market sizing, competitive density, and GTM model fit." + adaptation_rationale: "SaaS market entry is primarily about segment selection + and GTM motion — the product can reach any market digitally, so the + question is not 'can we enter?' but 'should we enter, and how?' + SaaS-specific triage focuses on market sizing, competitive density, and + GTM model fit." additional_triage_questions: - - question: "Have you validated demand through a landing page, waitlist, or beta program — or are you estimating market size from top-down analysis?" - purpose: "SaaS market entry decisions should be validated bottom-up (demonstrated demand) rather than top-down (TAM estimates). A waitlist of 500 companies is more valuable than a $10B TAM slide." - routing_impact: "No validation routes to lean market testing before full entry. Validated demand routes to GTM strategy and go-to-market execution." + - question: "Have you validated demand through a landing page, waitlist, or beta + program — or are you estimating market size from top-down analysis?" + purpose: "SaaS market entry decisions should be validated bottom-up + (demonstrated demand) rather than top-down (TAM estimates). A waitlist + of 500 companies is more valuable than a $10B TAM slide." + routing_impact: "No validation routes to lean market testing before full entry. + Validated demand routes to GTM strategy and go-to-market execution." diagnosis_weight_shifts: more_likely: - diagnosis: "Crowded category entry without differentiation" - reason: "SaaS markets are globally accessible, making most categories crowded. Entry without clear differentiation leads to costly competition." + reason: "SaaS markets are globally accessible, making most categories crowded. + Entry without clear differentiation leads to costly competition." less_likely: - diagnosis: "Market too small" - reason: "SaaS enables global reach and vertical specialization. Markets that appear small domestically may be substantial globally." + reason: "SaaS enables global reach and vertical specialization. Markets that + appear small domestically may be substantial globally." saas_specific_diagnoses: - name: "Category creation risk" - description: "The company is attempting to create a new SaaS category rather than enter an existing one. Category creation requires educating the market — a much more expensive and slower path than entering a category where buyers already understand the problem and solution type." + description: "The company is attempting to create a new SaaS category rather + than enter an existing one. Category creation requires educating the + market — a much more expensive and slower path than entering a + category where buyers already understand the problem and solution + type." symptoms: - "Prospects do not know what category to compare the product to" - - "Sales cycles are long because prospects must first understand the problem before evaluating the solution" + - "Sales cycles are long because prospects must first understand the + problem before evaluating the solution" - "G2/Capterra category does not exist for this product type" - routes_to_skills: ["blue-ocean-strategy", "story-structure-and-arc", "four-ps-marketing"] - routes_to_templates: ["market-opportunity-summary", "fundraising-deck-outline"] + routes_to_skills: [ "blue-ocean-strategy", "story-structure-and-arc", "four-ps-marketing" ] + routes_to_templates: [ "market-opportunity-summary", "fundraising-deck-outline" ] sector_red_flags: - - "Entering a market with 5+ well-funded competitors without a clearly articulated differentiation thesis." - - "Targeting enterprise from day one without enterprise sales experience or a customer reference." + - "Entering a market with 5+ well-funded competitors without a clearly + articulated differentiation thesis." + - "Targeting enterprise from day one without enterprise sales experience + or a customer reference." # ───────────────────────────────────────────── # 12. HIRING DIAGNOSIS @@ -450,30 +763,52 @@ diagnostic_rules: - diagnostic: "hiring-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS hiring challenges center on the scarcity of specialized talent (SaaS sales reps, product managers, growth marketers) and the critical importance of early hires in setting the culture and operational foundation." + adaptation_rationale: "SaaS hiring challenges center on the scarcity of + specialized talent (SaaS sales reps, product managers, growth marketers) + and the critical importance of early hires in setting the culture and + operational foundation." additional_triage_questions: - - question: "Are you hiring to scale an existing function that works (e.g., adding more sales reps to a proven sales motion) or hiring to build a function that does not yet exist (e.g., first VP Sales, first product manager)?" - purpose: "Scaling a working function requires execution hires. Building a new function requires a leader who can define the playbook. Misidentifying the hire type is the most common SaaS hiring mistake." - routing_impact: "Scaling a working function routes to structured hiring processes and hiring-scorecard template. Building new function routes to executive search principles and role-description-template with emphasis on defining success criteria." + - question: "Are you hiring to scale an existing function that works (e.g., adding + more sales reps to a proven sales motion) or hiring to build a + function that does not yet exist (e.g., first VP Sales, first product + manager)?" + purpose: "Scaling a working function requires execution hires. Building a new + function requires a leader who can define the playbook. Misidentifying + the hire type is the most common SaaS hiring mistake." + routing_impact: "Scaling a working function routes to structured hiring + processes and hiring-scorecard template. Building new function routes + to executive search principles and role-description-template with + emphasis on defining success criteria." diagnosis_weight_shifts: more_likely: - diagnosis: "Hiring the wrong profile for the stage" - reason: "SaaS companies frequently hire executives from larger companies (VP Sales from a $100M ARR company for a $2M ARR company) whose skills do not transfer to the earlier stage." + reason: "SaaS companies frequently hire executives from larger companies (VP + Sales from a $100M ARR company for a $2M ARR company) whose skills + do not transfer to the earlier stage." less_likely: - diagnosis: "Compensation competitiveness" - reason: "While important, compensation is rarely the primary reason SaaS hiring fails. Mission, growth trajectory, equity, and team quality matter more for early-stage hires." + reason: "While important, compensation is rarely the primary reason SaaS hiring + fails. Mission, growth trajectory, equity, and team quality matter + more for early-stage hires." saas_specific_diagnoses: - name: "Premature specialization" - description: "The company hires specialists (demand gen marketer, SDR manager, solutions architect) before the generalist playbook is established. Specialists optimize processes that do not yet exist, leading to wasted resources and organizational complexity." + description: "The company hires specialists (demand gen marketer, SDR manager, + solutions architect) before the generalist playbook is established. + Specialists optimize processes that do not yet exist, leading to + wasted resources and organizational complexity." symptoms: - - "Specialized hires with no one to report to or learn from in their function" - - "Processes being built from scratch by individual contributors without strategic direction" + - "Specialized hires with no one to report to or learn from in their + function" + - "Processes being built from scratch by individual contributors + without strategic direction" - "Under $3M ARR with more than 5 distinct go-to-market roles" - routes_to_skills: ["eisenhower-matrix", "delegation-and-empowerment"] - routes_to_templates: ["role-description-template", "hiring-scorecard"] + routes_to_skills: [ "eisenhower-matrix", "delegation-and-empowerment" ] + routes_to_templates: [ "role-description-template", "hiring-scorecard" ] sector_red_flags: - - "VP Sales hire failing within 6 months — the most common and most expensive SaaS hiring mistake." - - "Engineering team spending more time onboarding new hires than building product — a sign of hiring too fast." + - "VP Sales hire failing within 6 months — the most common and most + expensive SaaS hiring mistake." + - "Engineering team spending more time onboarding new hires than building + product — a sign of hiring too fast." # ───────────────────────────────────────────── # 13. OPERATIONAL CHAOS DIAGNOSIS @@ -481,30 +816,49 @@ diagnostic_rules: - diagnostic: "operational-chaos-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS operational chaos manifests as infrastructure instability, deployment failures, billing errors, and support overwhelm. The continuous nature of SaaS delivery (24/7 uptime, continuous deployment) creates unique operational demands." + adaptation_rationale: "SaaS operational chaos manifests as infrastructure + instability, deployment failures, billing errors, and support overwhelm. + The continuous nature of SaaS delivery (24/7 uptime, continuous + deployment) creates unique operational demands." additional_triage_questions: - - question: "How frequently do you deploy to production, and what percentage of deployments cause incidents?" - purpose: "Deployment frequency and failure rate are the two most diagnostic operational health metrics in SaaS. Low frequency suggests fear of shipping; high failure rate suggests inadequate testing and review." - routing_impact: "High deployment failure rate routes to engineering process improvement. Low deployment frequency routes to CI/CD and DevOps investment." + - question: "How frequently do you deploy to production, and what percentage of + deployments cause incidents?" + purpose: "Deployment frequency and failure rate are the two most diagnostic + operational health metrics in SaaS. Low frequency suggests fear of + shipping; high failure rate suggests inadequate testing and review." + routing_impact: "High deployment failure rate routes to engineering process + improvement. Low deployment frequency routes to CI/CD and DevOps + investment." diagnosis_weight_shifts: more_likely: - diagnosis: "Technical debt overwhelming operations" - reason: "SaaS companies that grow fast accumulate technical debt that eventually consumes engineering capacity, causes outages, and slows product development." + reason: "SaaS companies that grow fast accumulate technical debt that eventually + consumes engineering capacity, causes outages, and slows product + development." less_likely: - diagnosis: "Process deficiency" - reason: "Early-stage SaaS companies often have too much process (imported from larger companies) rather than too little. The diagnosis may be over-process, not under-process." + reason: "Early-stage SaaS companies often have too much process (imported from + larger companies) rather than too little. The diagnosis may be + over-process, not under-process." saas_specific_diagnoses: - name: "Support-driven engineering" - description: "Customer support volume is so high that engineering spends the majority of time fixing customer-specific issues rather than building product improvements. The product does not improve, generating more support tickets in a reinforcing loop." + description: "Customer support volume is so high that engineering spends the + majority of time fixing customer-specific issues rather than building + product improvements. The product does not improve, generating more + support tickets in a reinforcing loop." symptoms: - - "More than 30% of engineering capacity consumed by support escalations" + - "More than 30% of engineering capacity consumed by support + escalations" - "Support ticket volume growing faster than customer count" - - "No self-serve knowledge base, in-app help, or automated troubleshooting" - - "Customer success and support teams with direct Slack channels to engineers for 'urgent' issues" - routes_to_skills: ["systems-thinking", "eisenhower-matrix"] - routes_to_templates: ["action-plan", "incident-postmortem"] + - "No self-serve knowledge base, in-app help, or automated + troubleshooting" + - "Customer success and support teams with direct Slack channels to + engineers for 'urgent' issues" + routes_to_skills: [ "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] sector_red_flags: - - "Uptime below 99.5% over any 30-day period — customers will leave for more reliable alternatives." + - "Uptime below 99.5% over any 30-day period — customers will leave for + more reliable alternatives." - "Mean time to resolution for P0 incidents exceeding 4 hours." # ───────────────────────────────────────────── @@ -513,14 +867,18 @@ diagnostic_rules: - diagnostic: "leadership-crisis-diagnosis" sector_adaptation: "as-is" - adaptation_rationale: "Leadership crises in SaaS follow the same patterns as in other venture-backed companies. The base diagnostic covers founder burnout, board conflicts, executive team dysfunction, and crisis management without requiring SaaS-specific modification." + adaptation_rationale: "Leadership crises in SaaS follow the same patterns as in + other venture-backed companies. The base diagnostic covers founder + burnout, board conflicts, executive team dysfunction, and crisis + management without requiring SaaS-specific modification." additional_triage_questions: [] diagnosis_weight_shifts: more_likely: [] less_likely: [] saas_specific_diagnoses: [] sector_red_flags: - - "CEO making reactive, metric-driven decisions without strategic framing — a sign of losing the forest for the trees in a data-rich environment." + - "CEO making reactive, metric-driven decisions without strategic framing + — a sign of losing the forest for the trees in a data-rich environment." # ───────────────────────────────────────────── # 15. DECISION PARALYSIS DIAGNOSIS @@ -528,22 +886,34 @@ diagnostic_rules: - diagnostic: "decision-paralysis-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS provides abundant data, which paradoxically can increase decision paralysis. Founders waiting for 'enough data' before making pricing, product, or GTM decisions often delay beyond the point where the decision would have generated useful learning." + adaptation_rationale: "SaaS provides abundant data, which paradoxically can + increase decision paralysis. Founders waiting for 'enough data' before + making pricing, product, or GTM decisions often delay beyond the point + where the decision would have generated useful learning." additional_triage_questions: - - question: "Is the decision reversible or irreversible? Can you test a smaller version before committing fully?" - purpose: "Most SaaS decisions are reversible (pricing, features, campaigns). Treating reversible decisions with irreversible-decision rigor causes paralysis." - routing_impact: "Reversible decision paralysis routes to evaluating-and-deciding with emphasis on speed. Irreversible decisions route to tough-decision-situations for deeper analysis." + - question: "Is the decision reversible or irreversible? Can you test a smaller + version before committing fully?" + purpose: "Most SaaS decisions are reversible (pricing, features, campaigns). + Treating reversible decisions with irreversible-decision rigor causes + paralysis." + routing_impact: "Reversible decision paralysis routes to evaluating-and-deciding + with emphasis on speed. Irreversible decisions route to + tough-decision-situations for deeper analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Analysis paralysis driven by data abundance" - reason: "SaaS dashboards provide infinite data to analyze. 'One more week of data' is the most seductive form of decision avoidance." + reason: "SaaS dashboards provide infinite data to analyze. 'One more week of + data' is the most seductive form of decision avoidance." less_likely: - diagnosis: "Insufficient information" - reason: "SaaS companies rarely lack information. They lack clarity on which information matters and the willingness to act on imperfect data." + reason: "SaaS companies rarely lack information. They lack clarity on which + information matters and the willingness to act on imperfect data." saas_specific_diagnoses: [] sector_red_flags: - - "Pricing decision delayed more than 3 months — pricing is always imperfect and always adjustable." - - "Product decisions requiring consensus from more than 3 people — a sign of unclear decision authority." + - "Pricing decision delayed more than 3 months — pricing is always + imperfect and always adjustable." + - "Product decisions requiring consensus from more than 3 people — a sign + of unclear decision authority." # ───────────────────────────────────────────── # 16. INNOVATION DROUGHT DIAGNOSIS @@ -551,31 +921,52 @@ diagnostic_rules: - diagnostic: "innovation-drought-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS innovation droughts manifest as feature stagnation — the product stops evolving, competitors close the gap, and customers lose enthusiasm. The continuous delivery model means that innovation drought is visible immediately in declining activation rates and stagnant NPS." + adaptation_rationale: "SaaS innovation droughts manifest as feature stagnation — + the product stops evolving, competitors close the gap, and customers lose + enthusiasm. The continuous delivery model means that innovation drought is + visible immediately in declining activation rates and stagnant NPS." additional_triage_questions: - - question: "What percentage of engineering capacity is allocated to new features versus maintenance, technical debt, and support?" - purpose: "If more than 50% of engineering capacity goes to maintenance and debt, innovation will stall regardless of team talent." - routing_impact: "Maintenance-dominated allocation routes to technical debt assessment and eisenhower-matrix for engineering prioritization." + - question: "What percentage of engineering capacity is allocated to new features + versus maintenance, technical debt, and support?" + purpose: "If more than 50% of engineering capacity goes to maintenance and debt, + innovation will stall regardless of team talent." + routing_impact: "Maintenance-dominated allocation routes to technical debt + assessment and eisenhower-matrix for engineering prioritization." diagnosis_weight_shifts: more_likely: - diagnosis: "Technical debt consuming innovation capacity" - reason: "SaaS companies that shipped fast to achieve PMF often accumulated debt that now prevents further innovation." + reason: "SaaS companies that shipped fast to achieve PMF often accumulated debt + that now prevents further innovation." less_likely: - diagnosis: "Lack of creative talent" - reason: "SaaS teams are generally well-educated and creative. Innovation drought is more often a system failure (wrong incentives, too much process, insufficient time) than a talent failure." + reason: "SaaS teams are generally well-educated and creative. Innovation drought + is more often a system failure (wrong incentives, too much process, + insufficient time) than a talent failure." saas_specific_diagnoses: - name: "Customer-driven roadmap trap" - description: "The roadmap is entirely dictated by customer requests and support tickets. No capacity is allocated to proactive innovation — building features customers have not asked for but would love. The product incrementally improves existing workflows but never creates new value." + description: "The roadmap is entirely dictated by customer requests and support + tickets. No capacity is allocated to proactive innovation — building + features customers have not asked for but would love. The product + incrementally improves existing workflows but never creates new + value." symptoms: - "Every roadmap item traceable to a specific customer request" - "No 'surprise and delight' features shipped in the last 6 months" - - "NPS stable but not improving — customers are satisfied, not enthusiastic" - - "No features that generated organic social media discussion or viral sharing" - routes_to_skills: ["disruptive-innovation", "blue-ocean-strategy", "creative-identity-and-purpose"] - routes_to_templates: ["new-initiative-brief", "quarterly-strategic-review"] + - "NPS stable but not improving — customers are satisfied, not + enthusiastic" + - "No features that generated organic social media discussion or viral + sharing" + routes_to_skills: + [ + "disruptive-innovation", + "blue-ocean-strategy", + "creative-identity-and-purpose" + ] + routes_to_templates: [ "new-initiative-brief", "quarterly-strategic-review" ] sector_red_flags: - "NPS declining for 2+ consecutive quarters despite no major incidents." - - "Competitor launch announcements generating customer inquiries about 'do you have that?'" + - "Competitor launch announcements generating customer inquiries about 'do + you have that?'" # ───────────────────────────────────────────── # 17. PARTNERSHIP DIAGNOSIS @@ -583,30 +974,52 @@ diagnostic_rules: - diagnostic: "partnership-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS partnerships are ecosystem-driven — integrations, channel partnerships, and platform relationships are growth levers that do not exist in the same form in traditional businesses. The diagnostic must account for the unique dynamics of technology partnerships." + adaptation_rationale: "SaaS partnerships are ecosystem-driven — integrations, + channel partnerships, and platform relationships are growth levers that do + not exist in the same form in traditional businesses. The diagnostic must + account for the unique dynamics of technology partnerships." additional_triage_questions: - - question: "Is this a technology integration partnership (building together), a channel partnership (selling together), or a platform partnership (building on top of them)?" - purpose: "Each partnership type has different economics, power dynamics, and risks. A platform partnership where you build on their API puts you in a dependency relationship that does not exist in a co-selling arrangement." - routing_impact: "Technology integration routes to cooperative-negotiation with emphasis on mutual value. Channel partnership routes to four-ps-marketing for distribution strategy. Platform partnership routes to prisoners-dilemma-and-cooperation for dependency risk analysis." + - question: "Is this a technology integration partnership (building together), a + channel partnership (selling together), or a platform partnership + (building on top of them)?" + purpose: "Each partnership type has different economics, power dynamics, and + risks. A platform partnership where you build on their API puts you in + a dependency relationship that does not exist in a co-selling + arrangement." + routing_impact: "Technology integration routes to cooperative-negotiation with + emphasis on mutual value. Channel partnership routes to + four-ps-marketing for distribution strategy. Platform partnership + routes to prisoners-dilemma-and-cooperation for dependency risk + analysis." diagnosis_weight_shifts: more_likely: - diagnosis: "Asymmetric dependency" - reason: "SaaS partnerships often involve significant size asymmetry. A 50-person SaaS company partnering with Salesforce or HubSpot faces inherently asymmetric power dynamics." + reason: "SaaS partnerships often involve significant size asymmetry. A 50-person + SaaS company partnering with Salesforce or HubSpot faces inherently + asymmetric power dynamics." less_likely: - diagnosis: "Cultural misalignment" - reason: "SaaS partnerships are primarily technical and commercial. Cultural fit matters less than API quality, economic alignment, and strategic overlap." + reason: "SaaS partnerships are primarily technical and commercial. Cultural fit + matters less than API quality, economic alignment, and strategic + overlap." saas_specific_diagnoses: - name: "Integration as strategy substitute" - description: "The company builds integrations with every possible platform without a coherent partnership strategy. Integrations consume engineering resources but do not generate measurable revenue or retention impact because they are not promoted, supported, or monetized." + description: "The company builds integrations with every possible platform + without a coherent partnership strategy. Integrations consume + engineering resources but do not generate measurable revenue or + retention impact because they are not promoted, supported, or + monetized." symptoms: - "More than 20 integrations but none generating measurable revenue" - "No tracking of which integrations correlate with retention" - "Integrations built reactively (customer requests) not strategically" - - "Engineering maintaining integrations that fewer than 5% of customers use" - routes_to_skills: ["eisenhower-matrix", "balanced-scorecard", "systems-thinking"] - routes_to_templates: ["partnership-memo", "strategic-analysis-one-pager"] + - "Engineering maintaining integrations that fewer than 5% of + customers use" + routes_to_skills: [ "eisenhower-matrix", "balanced-scorecard", "systems-thinking" ] + routes_to_templates: [ "partnership-memo", "strategic-analysis-one-pager" ] sector_red_flags: - - "A platform partner announcing a native feature that competes with your core product." + - "A platform partner announcing a native feature that competes with your + core product." - "More than 30% of revenue dependent on a single channel partner." # ───────────────────────────────────────────── @@ -615,14 +1028,19 @@ diagnostic_rules: - diagnostic: "communication-breakdown-diagnosis" sector_adaptation: "as-is" - adaptation_rationale: "Communication breakdowns in SaaS follow the same patterns as in other technology companies — remote/hybrid work challenges, cross-functional misalignment, and scaling communication as the team grows. The base diagnostic covers these adequately." + adaptation_rationale: "Communication breakdowns in SaaS follow the same patterns + as in other technology companies — remote/hybrid work challenges, + cross-functional misalignment, and scaling communication as the team + grows. The base diagnostic covers these adequately." additional_triage_questions: [] diagnosis_weight_shifts: more_likely: [] less_likely: [] saas_specific_diagnoses: [] sector_red_flags: - - "Product and sales teams using different language to describe the same features — a sign of internal communication failure that propagates to customers." + - "Product and sales teams using different language to describe the same + features — a sign of internal communication failure that propagates to + customers." # ───────────────────────────────────────────── # 19. NEGOTIATION STUCK DIAGNOSIS @@ -630,21 +1048,37 @@ diagnostic_rules: - diagnostic: "negotiation-stuck-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS negotiations get stuck in characteristic ways: enterprise procurement processes that demand terms the startup cannot offer, investor negotiations that stall on valuation or control terms, and platform partnership negotiations where the power asymmetry is extreme." + adaptation_rationale: "SaaS negotiations get stuck in characteristic ways: + enterprise procurement processes that demand terms the startup cannot + offer, investor negotiations that stall on valuation or control terms, and + platform partnership negotiations where the power asymmetry is extreme." additional_triage_questions: - - question: "Is the negotiation stuck on commercial terms (price, discount, payment terms), legal terms (liability, data processing, IP), or strategic terms (exclusivity, roadmap commitments, partnership scope)?" - purpose: "SaaS negotiations stall for different reasons. Commercial stalls often resolve with creative packaging. Legal stalls require legal expertise. Strategic stalls require executive involvement." - routing_impact: "Commercial stalls route to pricing-diagnosis and competitive-negotiation. Legal stalls route to delivering-the-deal with emphasis on template preparation. Strategic stalls route to cooperative-negotiation and scenario-planning." + - question: "Is the negotiation stuck on commercial terms (price, discount, + payment terms), legal terms (liability, data processing, IP), or + strategic terms (exclusivity, roadmap commitments, partnership + scope)?" + purpose: "SaaS negotiations stall for different reasons. Commercial stalls often + resolve with creative packaging. Legal stalls require legal expertise. + Strategic stalls require executive involvement." + routing_impact: "Commercial stalls route to pricing-diagnosis and + competitive-negotiation. Legal stalls route to delivering-the-deal + with emphasis on template preparation. Strategic stalls route to + cooperative-negotiation and scenario-planning." diagnosis_weight_shifts: more_likely: - diagnosis: "Security/compliance review blocking the deal" - reason: "Enterprise SaaS sales increasingly stall during security review. SOC 2 Type II, penetration test results, and GDPR compliance are table-stakes requirements that some startups are unprepared for." + reason: "Enterprise SaaS sales increasingly stall during security review. SOC 2 + Type II, penetration test results, and GDPR compliance are + table-stakes requirements that some startups are unprepared for." less_likely: - diagnosis: "Fundamental value disagreement" - reason: "If the negotiation reached the terms stage, value has been established. Most SaaS negotiation stalls are procedural, not substantive." + reason: "If the negotiation reached the terms stage, value has been established. + Most SaaS negotiation stalls are procedural, not substantive." saas_specific_diagnoses: [] sector_red_flags: - - "Enterprise deals stalling for 60+ days in legal/security review — indicates the company needs a 'deal acceleration kit' (pre-prepared security documents, DPA, and flexible order forms)." + - "Enterprise deals stalling for 60+ days in legal/security review — + indicates the company needs a 'deal acceleration kit' (pre-prepared + security documents, DPA, and flexible order forms)." # ───────────────────────────────────────────── # 20. CULTURE EROSION DIAGNOSIS @@ -652,28 +1086,52 @@ diagnostic_rules: - diagnostic: "culture-erosion-diagnosis" sector_adaptation: "enhanced" - adaptation_rationale: "SaaS companies experience predictable culture erosion at specific scale thresholds — 15-20 employees (first departmental silos), 50-80 employees (loss of all-hands intimacy), and 150+ employees (Dunbar's number, where personal relationships can no longer sustain culture). The base diagnostic benefits from recognizing these SaaS growth-stage culture patterns." + adaptation_rationale: "SaaS companies experience predictable culture erosion at + specific scale thresholds — 15-20 employees (first departmental silos), + 50-80 employees (loss of all-hands intimacy), and 150+ employees (Dunbar's + number, where personal relationships can no longer sustain culture). The + base diagnostic benefits from recognizing these SaaS growth-stage culture + patterns." additional_triage_questions: - - question: "Has the company recently crossed a team-size threshold (15, 50, 150 employees), and did culture practices evolve to match?" - purpose: "Culture practices that work at 10 people fail at 50. The practices must evolve with scale — written values, structured onboarding, explicit communication norms, and formalized recognition." - routing_impact: "Recent threshold crossing routes to organisational-culture and leading-through-change for proactive culture evolution." + - question: "Has the company recently crossed a team-size threshold (15, 50, 150 + employees), and did culture practices evolve to match?" + purpose: "Culture practices that work at 10 people fail at 50. The practices + must evolve with scale — written values, structured onboarding, + explicit communication norms, and formalized recognition." + routing_impact: "Recent threshold crossing routes to organisational-culture and + leading-through-change for proactive culture evolution." diagnosis_weight_shifts: more_likely: - diagnosis: "Growth outpacing culture infrastructure" - reason: "SaaS companies that hire rapidly (doubling headcount annually) frequently outpace their ability to onboard, integrate, and acculturate new team members." + reason: "SaaS companies that hire rapidly (doubling headcount annually) + frequently outpace their ability to onboard, integrate, and + acculturate new team members." less_likely: - diagnosis: "Toxic leadership" - reason: "While possible, culture erosion in fast-growing SaaS is more often caused by neglect (no one is responsible for culture) than malice (someone is actively degrading it)." + reason: "While possible, culture erosion in fast-growing SaaS is more often + caused by neglect (no one is responsible for culture) than malice + (someone is actively degrading it)." saas_specific_diagnoses: - name: "Remote-first culture void" - description: "The company transitioned to remote or hybrid work without building the intentional culture infrastructure that remote teams require. Informal culture transmission (hallway conversations, lunch discussions, overhearing leadership decisions) no longer happens, and nothing has replaced it." + description: "The company transitioned to remote or hybrid work without building + the intentional culture infrastructure that remote teams require. + Informal culture transmission (hallway conversations, lunch + discussions, overhearing leadership decisions) no longer happens, and + nothing has replaced it." symptoms: - "New hires reporting feeling disconnected after 90 days" - "Cross-team collaboration declining — teams default to silos" - "Declining participation in optional company events" - - "Employee NPS declining despite competitive compensation and interesting work" - routes_to_skills: ["organisational-culture", "psychological-safety-practice", "team-culture-and-dynamics"] - routes_to_templates: ["culture-values-document", "team-health-check", "offsite-planning-guide"] + - "Employee NPS declining despite competitive compensation and + interesting work" + routes_to_skills: + [ + "organisational-culture", + "psychological-safety-practice", + "team-culture-and-dynamics" + ] + routes_to_templates: [ "culture-values-document", "team-health-check", "offsite-planning-guide" ] sector_red_flags: - - "Regrettable attrition above 15% annually — top performers leaving voluntarily signals cultural problems before surveys detect them." + - "Regrettable attrition above 15% annually — top performers leaving + voluntarily signals cultural problems before surveys detect them." - "Glassdoor rating declining more than 0.5 stars in 6 months." diff --git a/.claude/industry-packs/saas/saas-skill-overlays.yaml b/.claude/industry-packs/saas/saas-skill-overlays.yaml index 8ade9f7..f2b0887 100644 --- a/.claude/industry-packs/saas/saas-skill-overlays.yaml +++ b/.claude/industry-packs/saas/saas-skill-overlays.yaml @@ -37,240 +37,702 @@ skill_overlays: - skill: "porters-five-forces" category: "frameworks" saas_relevance: "critical" - saas_context: "SaaS fundamentally reshapes three of the five forces. Buyer power is amplified by low switching costs and monthly contracts — customers can leave at any renewal. Threat of substitutes is extreme because SaaS products compete not just with direct alternatives but with spreadsheets, no-code tools, and internal builds. Rivalry intensity is high because SaaS markets tend toward winner-take-most dynamics driven by network effects and data moats." + saas_context: "SaaS fundamentally reshapes three of the five forces. Buyer power + is amplified by low switching costs and monthly contracts — customers can + leave at any renewal. Threat of substitutes is extreme because SaaS + products compete not just with direct alternatives but with spreadsheets, + no-code tools, and internal builds. Rivalry intensity is high because SaaS + markets tend toward winner-take-most dynamics driven by network effects + and data moats." saas_anti_patterns: - - "Assuming high switching costs exist because the product has an API or integrations. True switching costs in SaaS come from workflow dependency and data lock-in, not technical integrations that competitors can replicate." - - "Ignoring the 'threat of non-consumption' — many SaaS markets compete not with other software but with manual processes or no solution at all." - - "Treating supplier power as irrelevant. Cloud infrastructure (AWS, GCP, Azure) and key API providers (Stripe, Twilio) can raise prices, change terms, or become competitors." - saas_example: "A vertical SaaS company serving dental practices uses Porter's Five Forces to discover that while direct competitors are few, the real competitive threat is from general-purpose EHR systems expanding into dental and from dental practice management consultants who recommend bespoke solutions. Supplier power is concentrated in a single insurance clearinghouse API. This analysis shifts the company's strategy from feature competition to building the deepest dental-specific data asset — the one force competitors cannot easily replicate." - benchmark_references: ["nrr", "logo-churn", "win-rate"] + - "Assuming high switching costs exist because the product has an API or + integrations. True switching costs in SaaS come from workflow dependency + and data lock-in, not technical integrations that competitors can + replicate." + - "Ignoring the 'threat of non-consumption' — many SaaS markets compete + not with other software but with manual processes or no solution at + all." + - "Treating supplier power as irrelevant. Cloud infrastructure (AWS, GCP, + Azure) and key API providers (Stripe, Twilio) can raise prices, change + terms, or become competitors." + saas_example: "A vertical SaaS company serving dental practices uses Porter's + Five Forces to discover that while direct competitors are few, the real + competitive threat is from general-purpose EHR systems expanding into + dental and from dental practice management consultants who recommend + bespoke solutions. Supplier power is concentrated in a single insurance + clearinghouse API. This analysis shifts the company's strategy from + feature competition to building the deepest dental-specific data asset — + the one force competitors cannot easily replicate." + benchmark_references: [ "nrr", "logo-churn", "win-rate" ] - skill: "blue-ocean-strategy" category: "frameworks" saas_relevance: "critical" - saas_context: "Blue ocean strategy is structurally essential for SaaS because most categories are crowded — G2 lists 100+ competitors in major categories. The strategy-canvas exercise maps features and price against incumbents, revealing where the market over-serves (complex enterprise features no one uses) and under-serves (simplicity, speed, specific vertical workflows). SaaS blue oceans are most commonly found in vertical niches, in underserved buyer personas within existing categories, or in reimagining the delivery model (PLG vs. enterprise sales in a traditionally sales-led category)." + saas_context: "Blue ocean strategy is structurally essential for SaaS because + most categories are crowded — G2 lists 100+ competitors in major + categories. The strategy-canvas exercise maps features and price against + incumbents, revealing where the market over-serves (complex enterprise + features no one uses) and under-serves (simplicity, speed, specific + vertical workflows). SaaS blue oceans are most commonly found in vertical + niches, in underserved buyer personas within existing categories, or in + reimagining the delivery model (PLG vs. enterprise sales in a + traditionally sales-led category)." saas_anti_patterns: - - "Pursuing a blue ocean that is actually a dry ocean — creating an uncontested space because no customers exist there. Validate demand before investing in differentiation." - - "Confusing feature novelty with strategic differentiation. Adding AI or a new UI to a commodity product does not create a blue ocean if the buyer's decision criteria remain price and integrations." - - "Abandoning a blue ocean too early by moving upmarket into red ocean enterprise competition before dominating the niche." - saas_example: "Linear launched into the project management space — one of the most crowded SaaS categories — by deliberately eliminating features (Gantt charts, resource management, portfolio views) and obsessing over speed, keyboard shortcuts, and developer experience. The blue ocean was 'engineering teams who hate slow, bloated project management tools.' By saying no to enterprise PM features, Linear created uncontested space that Jira, Asana, and Monday.com could not address without cannibalizing their existing products." - benchmark_references: ["activation-rate", "time-to-value", "nps-saas"] + - "Pursuing a blue ocean that is actually a dry ocean — creating an + uncontested space because no customers exist there. Validate demand + before investing in differentiation." + - "Confusing feature novelty with strategic differentiation. Adding AI or + a new UI to a commodity product does not create a blue ocean if the + buyer's decision criteria remain price and integrations." + - "Abandoning a blue ocean too early by moving upmarket into red ocean + enterprise competition before dominating the niche." + saas_example: "Linear launched into the project management space — one of the + most crowded SaaS categories — by deliberately eliminating features (Gantt + charts, resource management, portfolio views) and obsessing over speed, + keyboard shortcuts, and developer experience. The blue ocean was + 'engineering teams who hate slow, bloated project management tools.' By + saying no to enterprise PM features, Linear created uncontested space that + Jira, Asana, and Monday.com could not address without cannibalizing their + existing products." + benchmark_references: [ "activation-rate", "time-to-value", "nps-saas" ] - skill: "business-model-canvas" category: "frameworks" saas_relevance: "critical" - saas_context: "The Business Model Canvas requires SaaS-specific interpretation across nearly every block. Revenue Streams must decompose into MRR components (new, expansion, contraction, churn). Customer Relationships must distinguish self-serve, sales-assisted, and enterprise motions. Key Resources must include the codebase, data assets, and cloud infrastructure. Cost Structure must separate COGS (hosting, support) from operating expenses (R&D, S&M, G&A) because SaaS unit economics depend on this distinction. The canvas is most powerful when used to compare current-state and target-state models — for example, mapping the shift from a services-heavy implementation model to a product-led growth model." + saas_context: "The Business Model Canvas requires SaaS-specific interpretation + across nearly every block. Revenue Streams must decompose into MRR + components (new, expansion, contraction, churn). Customer Relationships + must distinguish self-serve, sales-assisted, and enterprise motions. Key + Resources must include the codebase, data assets, and cloud + infrastructure. Cost Structure must separate COGS (hosting, support) from + operating expenses (R&D, S&M, G&A) because SaaS unit economics depend on + this distinction. The canvas is most powerful when used to compare + current-state and target-state models — for example, mapping the shift + from a services-heavy implementation model to a product-led growth model." saas_anti_patterns: - - "Treating 'software' as the sole Value Proposition. The product is the delivery mechanism, not the value. Value in SaaS is the outcome: time saved, revenue generated, risk reduced." - - "Omitting Customer Success from Key Activities. In SaaS, post-sale retention and expansion are as critical as acquisition." - - "Filling the canvas once and filing it away. SaaS models evolve rapidly — the canvas should be revisited quarterly as pricing, channels, and customer segments shift." - saas_example: "A B2B SaaS founder uses the canvas to articulate why their current model is capital-inefficient. The canvas reveals that their Key Activity is dominated by custom onboarding (a services cost buried in COGS), their Customer Segment is too broad (serving SMB and enterprise with one product), and their Revenue Stream is flat-rate monthly — no expansion path. The canvas redesign introduces usage-based pricing, self-serve onboarding for SMB, and a dedicated enterprise tier, transforming the economics." - benchmark_references: ["gross-margin", "arpu", "cac", "ltv"] + - "Treating 'software' as the sole Value Proposition. The product is the + delivery mechanism, not the value. Value in SaaS is the outcome: time + saved, revenue generated, risk reduced." + - "Omitting Customer Success from Key Activities. In SaaS, post-sale + retention and expansion are as critical as acquisition." + - "Filling the canvas once and filing it away. SaaS models evolve rapidly + — the canvas should be revisited quarterly as pricing, channels, and + customer segments shift." + saas_example: "A B2B SaaS founder uses the canvas to articulate why their + current model is capital-inefficient. The canvas reveals that their Key + Activity is dominated by custom onboarding (a services cost buried in + COGS), their Customer Segment is too broad (serving SMB and enterprise + with one product), and their Revenue Stream is flat-rate monthly — no + expansion path. The canvas redesign introduces usage-based pricing, + self-serve onboarding for SMB, and a dedicated enterprise tier, + transforming the economics." + benchmark_references: [ "gross-margin", "arpu", "cac", "ltv" ] - skill: "four-ps-marketing" category: "frameworks" saas_relevance: "critical" - saas_context: "The traditional Four Ps require substantial adaptation for SaaS. Product is a living, evolving service — not a shipped good. Customers buy access, not ownership. Price in SaaS is a strategic lever with unique structures: per-seat, usage-based, tiered, freemium, flat-rate, and hybrid models. Each pricing structure changes customer behavior, expansion dynamics, and unit economics. Place means distribution channel — PLG (product is the channel), content marketing, outbound sales, partnerships, marketplaces. Promotion in SaaS emphasizes content marketing, community, product-led virality, and thought leadership over traditional advertising." + saas_context: "The traditional Four Ps require substantial adaptation for SaaS. + Product is a living, evolving service — not a shipped good. Customers buy + access, not ownership. Price in SaaS is a strategic lever with unique + structures: per-seat, usage-based, tiered, freemium, flat-rate, and hybrid + models. Each pricing structure changes customer behavior, expansion + dynamics, and unit economics. Place means distribution channel — PLG + (product is the channel), content marketing, outbound sales, partnerships, + marketplaces. Promotion in SaaS emphasizes content marketing, community, + product-led virality, and thought leadership over traditional + advertising." saas_anti_patterns: - - "Treating pricing as a one-time decision. SaaS pricing should be revisited at least annually and tested continuously. Most SaaS companies under-price by 20-40%." - - "Equating 'Place' with a website. Distribution strategy in SaaS encompasses app store presence, API marketplace listings, integration directories, partner channels, and the product itself as a distribution mechanism." - - "Running demand-gen campaigns (Promotion) without tracking the full funnel to revenue. SaaS marketing must be measured on pipeline contribution and CAC, not impressions or clicks." - saas_example: "A project management SaaS applies the Four Ps to restructure its go-to-market. Product: they separate the core product from add-on modules (analytics, time tracking, resource management). Price: they shift from flat-rate to per-seat with usage-based add-ons, creating natural expansion revenue. Place: they launch a free tier (PLG) alongside their existing sales motion, making the product itself a distribution channel. Promotion: they invest in a template library and community rather than paid ads, reducing CAC by 40%." - benchmark_references: ["cac", "arpu", "acv", "expansion-revenue-pct"] + - "Treating pricing as a one-time decision. SaaS pricing should be + revisited at least annually and tested continuously. Most SaaS companies + under-price by 20-40%." + - "Equating 'Place' with a website. Distribution strategy in SaaS + encompasses app store presence, API marketplace listings, integration + directories, partner channels, and the product itself as a distribution + mechanism." + - "Running demand-gen campaigns (Promotion) without tracking the full + funnel to revenue. SaaS marketing must be measured on pipeline + contribution and CAC, not impressions or clicks." + saas_example: "A project management SaaS applies the Four Ps to restructure its + go-to-market. Product: they separate the core product from add-on modules + (analytics, time tracking, resource management). Price: they shift from + flat-rate to per-seat with usage-based add-ons, creating natural expansion + revenue. Place: they launch a free tier (PLG) alongside their existing + sales motion, making the product itself a distribution channel. Promotion: + they invest in a template library and community rather than paid ads, + reducing CAC by 40%." + benchmark_references: [ "cac", "arpu", "acv", "expansion-revenue-pct" ] - skill: "net-promoter-score" category: "frameworks" saas_relevance: "critical" - saas_context: "NPS is deeply embedded in SaaS operating culture because of its correlation with net revenue retention. In SaaS, NPS surveys should be triggered by product usage milestones (not arbitrary time intervals), segmented by plan tier and customer cohort, and directly linked to churn prediction models. The actionable power of NPS in SaaS comes not from the score itself but from the qualitative feedback in the open-ended follow-up question and from tracking score changes over the customer lifecycle." + saas_context: "NPS is deeply embedded in SaaS operating culture because of its + correlation with net revenue retention. In SaaS, NPS surveys should be + triggered by product usage milestones (not arbitrary time intervals), + segmented by plan tier and customer cohort, and directly linked to churn + prediction models. The actionable power of NPS in SaaS comes not from the + score itself but from the qualitative feedback in the open-ended follow-up + question and from tracking score changes over the customer lifecycle." saas_anti_patterns: - - "Surveying all customers at the same time (quarterly blast) instead of using event-triggered NPS after key moments (onboarding completion, first renewal, support resolution)." - - "Optimizing for the NPS number rather than acting on detractor feedback. A rising NPS score that masks unresolved product issues is worse than a flat score with systematic feedback loops." - - "Treating Promoters as a marketing asset without building referral and advocacy programs. Promoters in SaaS drive viral growth — but only if you give them mechanisms to refer and share." - saas_example: "A mid-market SaaS company segments NPS by customer cohort and discovers that NPS drops sharply after month 6 — not at onboarding (where the score is 60+). Investigation reveals that customers exhaust the product's value within 6 months and hit a ceiling. This insight triggers a product roadmap shift toward deeper functionality and advanced use cases, directly addressing the retention cliff that NPS exposed." - benchmark_references: ["nps-saas", "nrr", "logo-churn"] + - "Surveying all customers at the same time (quarterly blast) instead of + using event-triggered NPS after key moments (onboarding completion, + first renewal, support resolution)." + - "Optimizing for the NPS number rather than acting on detractor feedback. + A rising NPS score that masks unresolved product issues is worse than a + flat score with systematic feedback loops." + - "Treating Promoters as a marketing asset without building referral and + advocacy programs. Promoters in SaaS drive viral growth — but only if + you give them mechanisms to refer and share." + saas_example: "A mid-market SaaS company segments NPS by customer cohort and + discovers that NPS drops sharply after month 6 — not at onboarding (where + the score is 60+). Investigation reveals that customers exhaust the + product's value within 6 months and hit a ceiling. This insight triggers a + product roadmap shift toward deeper functionality and advanced use cases, + directly addressing the retention cliff that NPS exposed." + benchmark_references: [ "nps-saas", "nrr", "logo-churn" ] - skill: "product-life-cycle" category: "frameworks" saas_relevance: "critical" - saas_context: "SaaS disrupted the traditional product lifecycle by enabling continuous delivery and iterative improvement. Products no longer 'launch' once — they evolve weekly. The lifecycle stages still apply but compress and overlap: Introduction is the beta/early access period, Growth coincides with product-market fit and scaling, Maturity arrives when NRR stabilizes and new customer growth slows, and Decline manifests as category commoditization or platform shift. The critical SaaS insight is that individual features within a product may be at different lifecycle stages simultaneously." + saas_context: "SaaS disrupted the traditional product lifecycle by enabling + continuous delivery and iterative improvement. Products no longer 'launch' + once — they evolve weekly. The lifecycle stages still apply but compress + and overlap: Introduction is the beta/early access period, Growth + coincides with product-market fit and scaling, Maturity arrives when NRR + stabilizes and new customer growth slows, and Decline manifests as + category commoditization or platform shift. The critical SaaS insight is + that individual features within a product may be at different lifecycle + stages simultaneously." saas_anti_patterns: - - "Assuming SaaS products are immune to maturity and decline because they can be updated. SaaS categories mature — CRM, email marketing, and project management are all mature categories where differentiation is extremely difficult." - - "Investing equally across all features regardless of their lifecycle position. Features in decline should be sunset; features in growth should receive disproportionate investment." - - "Confusing product-market fit with permanent market position. SaaS markets shift rapidly; what was innovative two years ago becomes table stakes." - saas_example: "Zendesk's core help desk product reached maturity by 2018 — NRR was stabilizing, and competitors like Intercom and Freshdesk were eroding differentiation. Rather than fighting for share in a maturing category, Zendesk expanded into a suite (Sell, Chat, Guide), effectively launching new products at the Introduction stage while managing the mature core. The product lifecycle framework helps SaaS companies decide when to extend the platform versus when to accept maturity in the core and invest in adjacencies." - benchmark_references: ["nrr", "mom-growth-rate", "nps-saas"] + - "Assuming SaaS products are immune to maturity and decline because they + can be updated. SaaS categories mature — CRM, email marketing, and + project management are all mature categories where differentiation is + extremely difficult." + - "Investing equally across all features regardless of their lifecycle + position. Features in decline should be sunset; features in growth + should receive disproportionate investment." + - "Confusing product-market fit with permanent market position. SaaS + markets shift rapidly; what was innovative two years ago becomes table + stakes." + saas_example: "Zendesk's core help desk product reached maturity by 2018 — NRR + was stabilizing, and competitors like Intercom and Freshdesk were eroding + differentiation. Rather than fighting for share in a maturing category, + Zendesk expanded into a suite (Sell, Chat, Guide), effectively launching + new products at the Introduction stage while managing the mature core. The + product lifecycle framework helps SaaS companies decide when to extend the + platform versus when to accept maturity in the core and invest in + adjacencies." + benchmark_references: [ "nrr", "mom-growth-rate", "nps-saas" ] - skill: "growth-share-matrix" category: "frameworks" saas_relevance: "high" - saas_context: "The BCG Growth-Share Matrix maps directly to SaaS product portfolio management. Stars are fast-growing products or modules with strong market share — they justify aggressive investment. Cash Cows are mature product lines with stable revenue and high margins — they fund investment in Stars. Question Marks are new product lines or market segments with high growth but unproven position. Dogs are features or modules that consume resources without generating growth or profit. For SaaS companies with multiple products or a platform play, this framework guides resource allocation across the portfolio." + saas_context: "The BCG Growth-Share Matrix maps directly to SaaS product + portfolio management. Stars are fast-growing products or modules with + strong market share — they justify aggressive investment. Cash Cows are + mature product lines with stable revenue and high margins — they fund + investment in Stars. Question Marks are new product lines or market + segments with high growth but unproven position. Dogs are features or + modules that consume resources without generating growth or profit. For + SaaS companies with multiple products or a platform play, this framework + guides resource allocation across the portfolio." saas_anti_patterns: - - "Treating the entire SaaS product as a single unit. The matrix is most useful when applied to product lines, modules, customer segments, or geographic markets within the company." - - "Killing 'Dog' features that are actually critical for retention or serve as table-stakes requirements for enterprise buyers." - - "Over-investing in Stars without building the operational infrastructure (customer success, support, documentation) to sustain growth." - saas_example: "HubSpot's portfolio maps cleanly to the matrix: Marketing Hub (Cash Cow — mature, high share), Sales Hub (Star — growing, gaining share), Service Hub (Question Mark — growing market, still proving position), CMS Hub (Dog — small market, limited differentiation). This framing helps explain HubSpot's investment priorities and organizational structure." - benchmark_references: ["arr", "mom-growth-rate", "gross-margin"] + - "Treating the entire SaaS product as a single unit. The matrix is most + useful when applied to product lines, modules, customer segments, or + geographic markets within the company." + - "Killing 'Dog' features that are actually critical for retention or + serve as table-stakes requirements for enterprise buyers." + - "Over-investing in Stars without building the operational infrastructure + (customer success, support, documentation) to sustain growth." + saas_example: "HubSpot's portfolio maps cleanly to the matrix: Marketing Hub + (Cash Cow — mature, high share), Sales Hub (Star — growing, gaining + share), Service Hub (Question Mark — growing market, still proving + position), CMS Hub (Dog — small market, limited differentiation). This + framing helps explain HubSpot's investment priorities and organizational + structure." + benchmark_references: [ "arr", "mom-growth-rate", "gross-margin" ] - skill: "disruptive-innovation" category: "frameworks" saas_relevance: "critical" - saas_context: "SaaS is the canonical vehicle for disruptive innovation. The pattern repeats endlessly: an incumbent serves the high end of the market with feature-rich, expensive software (Oracle, SAP, Salesforce enterprise). A SaaS startup enters at the bottom with a simpler, cheaper, self-serve product that the incumbent ignores. Over time, the SaaS product improves, moves upmarket, and captures the mainstream. This pattern drove the rise of Salesforce (vs. Siebel), Slack (vs. Microsoft), HubSpot (vs. Marketo/Eloqua), and Figma (vs. Adobe). Understanding disruptive innovation helps SaaS founders position correctly — start simple, serve the over-served, and improve relentlessly." + saas_context: "SaaS is the canonical vehicle for disruptive innovation. The + pattern repeats endlessly: an incumbent serves the high end of the market + with feature-rich, expensive software (Oracle, SAP, Salesforce + enterprise). A SaaS startup enters at the bottom with a simpler, cheaper, + self-serve product that the incumbent ignores. Over time, the SaaS product + improves, moves upmarket, and captures the mainstream. This pattern drove + the rise of Salesforce (vs. Siebel), Slack (vs. Microsoft), HubSpot (vs. + Marketo/Eloqua), and Figma (vs. Adobe). Understanding disruptive + innovation helps SaaS founders position correctly — start simple, serve + the over-served, and improve relentlessly." saas_anti_patterns: - - "Trying to compete on features with the incumbent from day one. Disruption requires starting with a 'worse' product on traditional metrics that is better on a new dimension (simpler, cheaper, faster)." - - "Moving upmarket too early, before establishing dominance in the low-end or niche segment. Premature enterprise motions destroy startups." - - "Ignoring the sustaining innovation response. Incumbents will eventually respond with their own simpler offering — the disruptor must build defensibility (data, network effects, integrations) before that happens." - saas_example: "Figma disrupted Adobe's design tool dominance by starting with a browser-based, free-for-individual-use product that professional designers initially dismissed as a toy. Figma was 'worse' on feature depth but better on collaboration, accessibility, and speed. By the time Adobe recognized the threat and attempted to acquire Figma, the product had captured the workflow of an entire generation of designers — the disruption was complete." - benchmark_references: ["activation-rate", "time-to-value", "arpu"] + - "Trying to compete on features with the incumbent from day one. + Disruption requires starting with a 'worse' product on traditional + metrics that is better on a new dimension (simpler, cheaper, faster)." + - "Moving upmarket too early, before establishing dominance in the low-end + or niche segment. Premature enterprise motions destroy startups." + - "Ignoring the sustaining innovation response. Incumbents will eventually + respond with their own simpler offering — the disruptor must build + defensibility (data, network effects, integrations) before that + happens." + saas_example: "Figma disrupted Adobe's design tool dominance by starting with a + browser-based, free-for-individual-use product that professional designers + initially dismissed as a toy. Figma was 'worse' on feature depth but + better on collaboration, accessibility, and speed. By the time Adobe + recognized the threat and attempted to acquire Figma, the product had + captured the workflow of an entire generation of designers — the + disruption was complete." + benchmark_references: [ "activation-rate", "time-to-value", "arpu" ] - skill: "balanced-scorecard" category: "frameworks" saas_relevance: "critical" - saas_context: "The Balanced Scorecard translates directly into SaaS operating metrics across its four perspectives. Financial: MRR/ARR, burn multiple, Rule of 40, gross margin. Customer: NPS, NRR, logo churn, time to value. Internal Process: deployment frequency, incident response time, onboarding completion rate, support ticket resolution time. Learning & Growth: engineering velocity, employee NPS, skill development investment. The scorecard is particularly powerful in SaaS because the subscription model generates rich, real-time data for all four perspectives, enabling weekly or even daily tracking rather than quarterly reviews." + saas_context: "The Balanced Scorecard translates directly into SaaS operating + metrics across its four perspectives. Financial: MRR/ARR, burn multiple, + Rule of 40, gross margin. Customer: NPS, NRR, logo churn, time to value. + Internal Process: deployment frequency, incident response time, onboarding + completion rate, support ticket resolution time. Learning & Growth: + engineering velocity, employee NPS, skill development investment. The + scorecard is particularly powerful in SaaS because the subscription model + generates rich, real-time data for all four perspectives, enabling weekly + or even daily tracking rather than quarterly reviews." saas_anti_patterns: - - "Tracking too many metrics. A SaaS scorecard should contain 12-16 KPIs, not 50. Each metric must have a clear owner and a clear action when it deviates." - - "Ignoring the Learning & Growth perspective. SaaS companies that under-invest in engineering culture, tooling, and talent development accumulate technical debt that eventually manifests in the other three perspectives." - - "Using the scorecard purely for reporting rather than as a decision-making tool. The scorecard should drive weekly executive team discussions and resource allocation decisions." - saas_example: "A Series B SaaS company implements a balanced scorecard with four KPIs per perspective: Financial (ARR growth, burn multiple, gross margin, NRR), Customer (NPS, logo churn, activation rate, support CSAT), Internal Process (deploy frequency, P0 incident rate, onboarding time, feature adoption rate), Learning & Growth (employee NPS, engineering velocity, internal mobility rate, training hours per engineer). The scorecard reveals that declining NPS and rising churn correlate with a spike in P0 incidents — an internal process failure is driving customer outcomes." - benchmark_references: ["arr", "burn-multiple", "rule-of-40", "nrr", "nps-saas", "gross-margin"] + - "Tracking too many metrics. A SaaS scorecard should contain 12-16 KPIs, + not 50. Each metric must have a clear owner and a clear action when it + deviates." + - "Ignoring the Learning & Growth perspective. SaaS companies that + under-invest in engineering culture, tooling, and talent development + accumulate technical debt that eventually manifests in the other three + perspectives." + - "Using the scorecard purely for reporting rather than as a + decision-making tool. The scorecard should drive weekly executive team + discussions and resource allocation decisions." + saas_example: "A Series B SaaS company implements a balanced scorecard with four + KPIs per perspective: Financial (ARR growth, burn multiple, gross margin, + NRR), Customer (NPS, logo churn, activation rate, support CSAT), Internal + Process (deploy frequency, P0 incident rate, onboarding time, feature + adoption rate), Learning & Growth (employee NPS, engineering velocity, + internal mobility rate, training hours per engineer). The scorecard + reveals that declining NPS and rising churn correlate with a spike in P0 + incidents — an internal process failure is driving customer outcomes." + benchmark_references: [ "arr", "burn-multiple", "rule-of-40", "nrr", "nps-saas", "gross-margin" ] - skill: "swot-pest-analysis" category: "frameworks" saas_relevance: "high" - saas_context: "SWOT and PEST analysis in SaaS must account for the unique environmental forces shaping the sector. Political: data privacy regulation (GDPR, CCPA, emerging AI regulation) directly impacts SaaS product design and go-to-market. Economic: interest rate environments affect SaaS valuations, customer IT budgets, and fundraising conditions. Social: remote work adoption, buyer preference for self-serve purchasing, and the consumerization of enterprise software. Technological: AI/ML capabilities, cloud infrastructure evolution, API ecosystem maturity, and platform risk from AWS/Google/Microsoft building competing features." + saas_context: "SWOT and PEST analysis in SaaS must account for the unique + environmental forces shaping the sector. Political: data privacy + regulation (GDPR, CCPA, emerging AI regulation) directly impacts SaaS + product design and go-to-market. Economic: interest rate environments + affect SaaS valuations, customer IT budgets, and fundraising conditions. + Social: remote work adoption, buyer preference for self-serve purchasing, + and the consumerization of enterprise software. Technological: AI/ML + capabilities, cloud infrastructure evolution, API ecosystem maturity, and + platform risk from AWS/Google/Microsoft building competing features." saas_anti_patterns: - - "Listing 'technology' as a strength without specificity. Every SaaS company has technology. The question is what specific technical capability creates defensible advantage." - - "Ignoring platform risk in the PEST analysis. If AWS, Google, or Microsoft can build your product as a feature of their platform, that is a material threat." - - "Conducting SWOT as a one-time exercise rather than a quarterly refresh. SaaS competitive dynamics shift rapidly — a strength today (e.g., AI capabilities) becomes table stakes in 12 months." - saas_example: "A SaaS company providing compliance automation uses PEST to identify that upcoming AI regulation in the EU will create mandatory compliance requirements for any company deploying AI systems — a massive tailwind for their product. The SWOT reveals that while they have a strong SMB customer base (Strength), they lack enterprise sales capabilities (Weakness) and enterprise compliance buyers are the primary beneficiaries of the regulatory shift (Opportunity). This analysis triggers a strategic decision to hire an enterprise sales leader and build SOC 2 Type II certification before competitors." - benchmark_references: ["arr", "win-rate"] + - "Listing 'technology' as a strength without specificity. Every SaaS + company has technology. The question is what specific technical + capability creates defensible advantage." + - "Ignoring platform risk in the PEST analysis. If AWS, Google, or + Microsoft can build your product as a feature of their platform, that is + a material threat." + - "Conducting SWOT as a one-time exercise rather than a quarterly refresh. + SaaS competitive dynamics shift rapidly — a strength today (e.g., AI + capabilities) becomes table stakes in 12 months." + saas_example: "A SaaS company providing compliance automation uses PEST to + identify that upcoming AI regulation in the EU will create mandatory + compliance requirements for any company deploying AI systems — a massive + tailwind for their product. The SWOT reveals that while they have a strong + SMB customer base (Strength), they lack enterprise sales capabilities + (Weakness) and enterprise compliance buyers are the primary beneficiaries + of the regulatory shift (Opportunity). This analysis triggers a strategic + decision to hire an enterprise sales leader and build SOC 2 Type II + certification before competitors." + benchmark_references: [ "arr", "win-rate" ] - skill: "scenario-planning" category: "frameworks" saas_relevance: "high" - saas_context: "Scenario planning in SaaS must account for the high-variance nature of software businesses. The three most critical scenario dimensions are: growth rate (acceleration vs. deceleration vs. stall), capital markets (available vs. constrained), and competitive dynamics (stable vs. new entrant vs. incumbent pivot). SaaS companies should maintain at least three financial scenarios (base, upside, downside) with explicit trigger points that signal which scenario is materializing. The planning horizon for SaaS is typically shorter than traditional industries — 18-24 months is the practical limit given the pace of market change." + saas_context: "Scenario planning in SaaS must account for the high-variance + nature of software businesses. The three most critical scenario dimensions + are: growth rate (acceleration vs. deceleration vs. stall), capital + markets (available vs. constrained), and competitive dynamics (stable vs. + new entrant vs. incumbent pivot). SaaS companies should maintain at least + three financial scenarios (base, upside, downside) with explicit trigger + points that signal which scenario is materializing. The planning horizon + for SaaS is typically shorter than traditional industries — 18-24 months + is the practical limit given the pace of market change." saas_anti_patterns: - - "Building scenarios that are all variations of 'things go well.' True scenario planning requires at least one scenario where a core assumption fails — the largest customer churns, a competitor raises $100M, or a platform partner enters the space." - - "Treating the financial model as the scenario plan. Scenarios must include strategic responses, not just different revenue lines. What changes operationally in each scenario?" - - "Ignoring the capital markets scenario. A SaaS company's strategic options depend heavily on whether fundraising is available. The 2022-2023 market correction demonstrated how quickly this variable can change." - saas_example: "A Series A SaaS company builds three scenarios for the next 18 months: (1) Base: 2.5x YoY growth, Series B in 12 months at current trajectory. (2) Upside: 3x+ growth triggered by a key integration launch, enabling a larger Series B. (3) Downside: growth slows to 1.5x due to a new competitor, requiring 6 months of runway extension through cost cuts before attempting Series B. Each scenario has explicit metric triggers (monthly ARR growth rate crossing specific thresholds) and pre-committed strategic responses." - benchmark_references: ["arr", "mom-growth-rate", "burn-multiple"] + - "Building scenarios that are all variations of 'things go well.' True + scenario planning requires at least one scenario where a core assumption + fails — the largest customer churns, a competitor raises $100M, or a + platform partner enters the space." + - "Treating the financial model as the scenario plan. Scenarios must + include strategic responses, not just different revenue lines. What + changes operationally in each scenario?" + - "Ignoring the capital markets scenario. A SaaS company's strategic + options depend heavily on whether fundraising is available. The + 2022-2023 market correction demonstrated how quickly this variable can + change." + saas_example: "A Series A SaaS company builds three scenarios for the next 18 + months: (1) Base: 2.5x YoY growth, Series B in 12 months at current + trajectory. (2) Upside: 3x+ growth triggered by a key integration launch, + enabling a larger Series B. (3) Downside: growth slows to 1.5x due to a + new competitor, requiring 6 months of runway extension through cost cuts + before attempting Series B. Each scenario has explicit metric triggers + (monthly ARR growth rate crossing specific thresholds) and pre-committed + strategic responses." + benchmark_references: [ "arr", "mom-growth-rate", "burn-multiple" ] - - skill: "pricing-diagnosis" - category: "frameworks" + - category: "frameworks" saas_relevance: "critical" - saas_context: "Pricing is the most powerful and most neglected lever in SaaS. A 1% improvement in pricing yields greater profit impact than a 1% improvement in customer acquisition or cost reduction. SaaS pricing diagnosis must evaluate: pricing model (per-seat, usage-based, tiered, flat-rate, hybrid), packaging (feature gating, tier structure, add-ons), price point (willingness-to-pay research, competitive positioning), and discounting discipline (deal desk governance, annual vs. monthly pricing spread). The diagnosis should also assess whether the pricing structure creates natural expansion revenue — products with usage-based or per-seat pricing grow within accounts automatically." + saas_context: "Pricing is the most powerful and most neglected lever in SaaS. A + 1% improvement in pricing yields greater profit impact than a 1% + improvement in customer acquisition or cost reduction. SaaS pricing + diagnosis must evaluate: pricing model (per-seat, usage-based, tiered, + flat-rate, hybrid), packaging (feature gating, tier structure, add-ons), + price point (willingness-to-pay research, competitive positioning), and + discounting discipline (deal desk governance, annual vs. monthly pricing + spread). The diagnosis should also assess whether the pricing structure + creates natural expansion revenue — products with usage-based or per-seat + pricing grow within accounts automatically." saas_anti_patterns: - - "Setting price based on cost-plus or competitor-matching rather than value-based pricing. SaaS products deliver value that far exceeds their cost to serve — pricing should capture a fair share of that value." - - "Offering monthly and annual plans with insufficient annual discount spread. The standard is 15-20% annual discount, which should fund the higher cost-to-serve of monthly subscribers." - - "Giving the sales team unlimited discounting authority. Uncontrolled discounting destroys ARPU trends and signals that the list price lacks credibility." - saas_example: "A B2B SaaS company discovers through pricing diagnosis that their $49/month flat-rate plan serves customers ranging from 2-person startups to 200-person companies. The largest customers derive 50x more value but pay the same price. Shifting to per-seat pricing with a $15/seat/month base and $25/seat/month professional tier triples ARPU from power users while maintaining accessibility for small teams. Expansion revenue jumps from 5% to 35% of new MRR within two quarters." - benchmark_references: ["arpu", "acv", "expansion-revenue-pct", "nrr"] + - "Setting price based on cost-plus or competitor-matching rather than + value-based pricing. SaaS products deliver value that far exceeds their + cost to serve — pricing should capture a fair share of that value." + - "Offering monthly and annual plans with insufficient annual discount + spread. The standard is 15-20% annual discount, which should fund the + higher cost-to-serve of monthly subscribers." + - "Giving the sales team unlimited discounting authority. Uncontrolled + discounting destroys ARPU trends and signals that the list price lacks + credibility." + saas_example: "A B2B SaaS company discovers through pricing diagnosis that their + $49/month flat-rate plan serves customers ranging from 2-person startups + to 200-person companies. The largest customers derive 50x more value but + pay the same price. Shifting to per-seat pricing with a $15/seat/month + base and $25/seat/month professional tier triples ARPU from power users + while maintaining accessibility for small teams. Expansion revenue jumps + from 5% to 35% of new MRR within two quarters." + benchmark_references: [ "arpu", "acv", "expansion-revenue-pct", "nrr" ] + kind: diagnostic + ref: pricing-diagnosis - skill: "doblin-ten-types" category: "frameworks" saas_relevance: "high" - saas_context: "The Ten Types of Innovation framework is particularly instructive for SaaS because software companies tend to over-index on Product Performance innovation (features) while ignoring the other nine types. The most powerful SaaS innovations often come from Profit Model (usage-based pricing), Network (integrations and ecosystems), Structure (remote-first teams), Process (CI/CD and rapid iteration), Channel (product-led growth), Customer Engagement (community-led growth), and Service (self-serve onboarding). Mapping innovation efforts across all ten types reveals where the company is under-investing." + saas_context: "The Ten Types of Innovation framework is particularly instructive + for SaaS because software companies tend to over-index on Product + Performance innovation (features) while ignoring the other nine types. The + most powerful SaaS innovations often come from Profit Model (usage-based + pricing), Network (integrations and ecosystems), Structure (remote-first + teams), Process (CI/CD and rapid iteration), Channel (product-led growth), + Customer Engagement (community-led growth), and Service (self-serve + onboarding). Mapping innovation efforts across all ten types reveals where + the company is under-investing." saas_anti_patterns: - - "Treating product features as the only innovation vector. Adding features to a commoditized category does not create differentiation — innovating on distribution, pricing, or customer experience does." - - "Ignoring Network innovation. In SaaS, integrations and ecosystem effects are among the strongest defensibility moats. A product with 200 integrations is harder to displace than one with better features." - - "Skipping the Profit Model type. The shift from perpetual license to subscription was itself a Profit Model innovation. The next wave (usage-based, outcome-based) is equally transformative." - saas_example: "Notion's success maps across multiple innovation types: Product Performance (flexible blocks system), Channel (freemium PLG distribution), Customer Engagement (template gallery and community), Brand (design-centric positioning), and Network (API and integrations ecosystem). Their competitors focused narrowly on Product Performance. Notion's multi-type innovation created compound defensibility." - benchmark_references: ["activation-rate", "nps-saas", "nrr"] + - "Treating product features as the only innovation vector. Adding + features to a commoditized category does not create differentiation — + innovating on distribution, pricing, or customer experience does." + - "Ignoring Network innovation. In SaaS, integrations and ecosystem + effects are among the strongest defensibility moats. A product with 200 + integrations is harder to displace than one with better features." + - "Skipping the Profit Model type. The shift from perpetual license to + subscription was itself a Profit Model innovation. The next wave + (usage-based, outcome-based) is equally transformative." + saas_example: "Notion's success maps across multiple innovation types: Product + Performance (flexible blocks system), Channel (freemium PLG distribution), + Customer Engagement (template gallery and community), Brand + (design-centric positioning), and Network (API and integrations + ecosystem). Their competitors focused narrowly on Product Performance. + Notion's multi-type innovation created compound defensibility." + benchmark_references: [ "activation-rate", "nps-saas", "nrr" ] - skill: "eisenhower-matrix" category: "frameworks" saas_relevance: "high" - saas_context: "SaaS founders and operators face extreme prioritization challenges because everything feels urgent — customers requesting features, infrastructure incidents, investor reporting, hiring, and competitive responses all compete for attention. The Eisenhower Matrix in SaaS must specifically classify: customer escalations (Urgent/Important vs. Urgent/Not Important — most escalations fall in the latter), feature requests (most are Not Urgent/Not Important for the roadmap), infrastructure investment (Not Urgent/Important — consistently deprioritized until a crisis moves it to Urgent/Important), and strategic work (Not Urgent/Important — the quadrant that determines long-term success)." + saas_context: "SaaS founders and operators face extreme prioritization + challenges because everything feels urgent — customers requesting + features, infrastructure incidents, investor reporting, hiring, and + competitive responses all compete for attention. The Eisenhower Matrix in + SaaS must specifically classify: customer escalations (Urgent/Important + vs. Urgent/Not Important — most escalations fall in the latter), feature + requests (most are Not Urgent/Not Important for the roadmap), + infrastructure investment (Not Urgent/Important — consistently + deprioritized until a crisis moves it to Urgent/Important), and strategic + work (Not Urgent/Important — the quadrant that determines long-term + success)." saas_anti_patterns: - - "Treating every customer request as Urgent and Important. Most customer requests are Urgent (to the customer) but Not Important (to the product strategy). Conflating these destroys roadmap discipline." - - "Neglecting the Not Urgent/Important quadrant (strategic planning, technical debt reduction, team development) because the daily urgency of a SaaS operation consumes all cycles." - - "Delegating product decisions that should not be delegated. In early-stage SaaS, the founder's product judgment is a critical asset — some 'Important' decisions cannot be delegated until the product vision is deeply shared." - saas_example: "A SaaS CEO uses the Eisenhower Matrix during a board preparation week and realizes that 70% of their time is spent in Urgent/Not Important: responding to customer support escalations that the support team should handle, reviewing every pull request, and attending standing meetings with no clear agenda. Delegating these frees 15 hours per week for Not Urgent/Important work: defining the 12-month product vision, building relationships with strategic partners, and developing the leadership team." + - "Treating every customer request as Urgent and Important. Most customer + requests are Urgent (to the customer) but Not Important (to the product + strategy). Conflating these destroys roadmap discipline." + - "Neglecting the Not Urgent/Important quadrant (strategic planning, + technical debt reduction, team development) because the daily urgency of + a SaaS operation consumes all cycles." + - "Delegating product decisions that should not be delegated. In + early-stage SaaS, the founder's product judgment is a critical asset — + some 'Important' decisions cannot be delegated until the product vision + is deeply shared." + saas_example: "A SaaS CEO uses the Eisenhower Matrix during a board preparation + week and realizes that 70% of their time is spent in Urgent/Not Important: + responding to customer support escalations that the support team should + handle, reviewing every pull request, and attending standing meetings with + no clear agenda. Delegating these frees 15 hours per week for Not + Urgent/Important work: defining the 12-month product vision, building + relationships with strategic partners, and developing the leadership + team." benchmark_references: [] - skill: "kotter-change-model" category: "frameworks" saas_relevance: "moderate" - saas_context: "Kotter's eight-step change model applies to SaaS companies during pivots, pricing restructures, go-to-market transitions, and organizational scaling. The model is most relevant when a SaaS company shifts from founder-led sales to a sales team, transitions from self-serve to enterprise, or restructures pricing. Step 1 (Create Urgency) is often supplied by metrics — declining NRR, rising churn, or missed targets provide the data-driven urgency that motivates change. Step 5 (Remove Obstacles) in SaaS frequently means addressing technical debt, legacy architecture, or organizational silos between product, sales, and customer success." + saas_context: "Kotter's eight-step change model applies to SaaS companies during + pivots, pricing restructures, go-to-market transitions, and organizational + scaling. The model is most relevant when a SaaS company shifts from + founder-led sales to a sales team, transitions from self-serve to + enterprise, or restructures pricing. Step 1 (Create Urgency) is often + supplied by metrics — declining NRR, rising churn, or missed targets + provide the data-driven urgency that motivates change. Step 5 (Remove + Obstacles) in SaaS frequently means addressing technical debt, legacy + architecture, or organizational silos between product, sales, and customer + success." saas_anti_patterns: - - "Skipping the coalition-building steps in a fast-moving SaaS environment. 'Move fast and break things' does not apply to organizational change — resistance from the sales team or engineering organization can kill a pricing restructure." - - "Announcing change without demonstrating 'quick wins' first. In SaaS, pilot programs (test new pricing with a segment, trial new sales motion with one team) build evidence before full rollout." - saas_example: "A SaaS company transitions from monthly subscription pricing to usage-based pricing. Using Kotter's model, leadership creates urgency by showing that 40% of customers are on plans that undercharge relative to usage. They form a coalition including the VP Sales, VP Product, and the largest customer success manager. The 'quick win' is a pilot with 50 customers who move to usage-based pricing voluntarily and see more transparent billing. This success funds the broader rollout." - benchmark_references: ["arpu", "nrr", "expansion-revenue-pct"] + - "Skipping the coalition-building steps in a fast-moving SaaS + environment. 'Move fast and break things' does not apply to + organizational change — resistance from the sales team or engineering + organization can kill a pricing restructure." + - "Announcing change without demonstrating 'quick wins' first. In SaaS, + pilot programs (test new pricing with a segment, trial new sales motion + with one team) build evidence before full rollout." + saas_example: "A SaaS company transitions from monthly subscription pricing to + usage-based pricing. Using Kotter's model, leadership creates urgency by + showing that 40% of customers are on plans that undercharge relative to + usage. They form a coalition including the VP Sales, VP Product, and the + largest customer success manager. The 'quick win' is a pilot with 50 + customers who move to usage-based pricing voluntarily and see more + transparent billing. This success funds the broader rollout." + benchmark_references: [ "arpu", "nrr", "expansion-revenue-pct" ] - skill: "systems-thinking" category: "frameworks" saas_relevance: "high" - saas_context: "SaaS businesses are complex adaptive systems with feedback loops that create non-obvious outcomes. The most important feedback loops: (1) The growth loop: more customers fund more investment in product, which attracts more customers. (2) The churn spiral: losing customers reduces revenue, forcing cuts to customer success, which increases churn further. (3) The data flywheel: more usage generates more data, which improves the product (especially for AI/ML products), which attracts more users. (4) The support debt loop: under-investing in self-serve support increases ticket volume, which consumes engineering time for urgent fixes, which delays product improvements, which generates more tickets. Systems thinking helps SaaS operators identify and intervene in these loops." + saas_context: "SaaS businesses are complex adaptive systems with feedback loops + that create non-obvious outcomes. The most important feedback loops: (1) + The growth loop: more customers fund more investment in product, which + attracts more customers. (2) The churn spiral: losing customers reduces + revenue, forcing cuts to customer success, which increases churn further. + (3) The data flywheel: more usage generates more data, which improves the + product (especially for AI/ML products), which attracts more users. (4) + The support debt loop: under-investing in self-serve support increases + ticket volume, which consumes engineering time for urgent fixes, which + delays product improvements, which generates more tickets. Systems + thinking helps SaaS operators identify and intervene in these loops." saas_anti_patterns: - - "Treating symptoms instead of systems. Throwing more sales reps at a growth stall when the root cause is a churn spiral. Hiring more support agents when the root cause is poor documentation." - - "Ignoring time delays in feedback loops. Cutting customer success today does not increase churn tomorrow — it increases churn in 3-6 months, making the cause-and-effect connection invisible." - - "Optimizing one metric without modeling second-order effects. Reducing CAC by cutting content marketing may increase CAC next quarter when the organic pipeline dries up." - saas_example: "A SaaS company notices that NRR is declining despite stable logo churn. Systems analysis reveals a reinforcing loop: as the product adds complexity to serve enterprise customers, SMB users (who generate expansion revenue through seat growth) find the product harder to use, leading to contraction. The enterprise-focused investment that improves per-account revenue is simultaneously degrading the expansion engine in the SMB segment. The solution is product architecture — a simplified SMB experience that diverges from the enterprise UI." - benchmark_references: ["nrr", "logo-churn", "activation-rate", "gross-margin"] + - "Treating symptoms instead of systems. Throwing more sales reps at a + growth stall when the root cause is a churn spiral. Hiring more support + agents when the root cause is poor documentation." + - "Ignoring time delays in feedback loops. Cutting customer success today + does not increase churn tomorrow — it increases churn in 3-6 months, + making the cause-and-effect connection invisible." + - "Optimizing one metric without modeling second-order effects. Reducing + CAC by cutting content marketing may increase CAC next quarter when the + organic pipeline dries up." + saas_example: "A SaaS company notices that NRR is declining despite stable logo + churn. Systems analysis reveals a reinforcing loop: as the product adds + complexity to serve enterprise customers, SMB users (who generate + expansion revenue through seat growth) find the product harder to use, + leading to contraction. The enterprise-focused investment that improves + per-account revenue is simultaneously degrading the expansion engine in + the SMB segment. The solution is product architecture — a simplified SMB + experience that diverges from the enterprise UI." + benchmark_references: [ "nrr", "logo-churn", "activation-rate", "gross-margin" ] - skill: "smart-goals" category: "frameworks" saas_relevance: "high" - saas_context: "SMART goals in SaaS benefit from the availability of precise, real-time metrics. Unlike traditional businesses where measurement is often lagging and approximate, SaaS companies can set goals that are Specific to a metric (e.g., NRR, not 'retention'), Measurable in real-time from the billing system, Achievable based on cohort analysis and historical data, Relevant to the current company stage, and Time-bound to monthly or quarterly cadences. The most common failure is setting goals that are too numerous or not tied to the two or three metrics that actually matter at the company's current stage." + saas_context: "SMART goals in SaaS benefit from the availability of precise, + real-time metrics. Unlike traditional businesses where measurement is + often lagging and approximate, SaaS companies can set goals that are + Specific to a metric (e.g., NRR, not 'retention'), Measurable in real-time + from the billing system, Achievable based on cohort analysis and + historical data, Relevant to the current company stage, and Time-bound to + monthly or quarterly cadences. The most common failure is setting goals + that are too numerous or not tied to the two or three metrics that + actually matter at the company's current stage." saas_anti_patterns: - - "Setting revenue goals without corresponding operational goals. 'Hit $5M ARR' is incomplete without 'achieve 110% NRR, reduce CAC payback to 12 months, and maintain 75% gross margin.'" - - "Using annual goals in an early-stage SaaS company where conditions change quarterly. Set 90-day goals with monthly check-ins." - - "Setting identical goals across functions. Engineering goals should be about product quality and velocity; Sales goals should be about pipeline and conversion; Customer Success goals should be about retention and expansion." - saas_example: "Instead of 'grow revenue,' a SaaS company sets Q2 goals: (1) Increase MRR from $150K to $200K by adding 30 new customers at $1,200 average MRR and expanding 15 existing customers by $500 average. (2) Reduce logo churn from 4% to 3% monthly by implementing a churn early-warning system and proactive outreach for at-risk accounts. (3) Decrease time to value from 14 days to 7 days by launching guided onboarding and in-app tutorials. Each goal is specific, measurable, connected to a responsible team, and achievable within the quarter." - benchmark_references: ["mrr", "logo-churn", "time-to-value"] + - "Setting revenue goals without corresponding operational goals. 'Hit $5M + ARR' is incomplete without 'achieve 110% NRR, reduce CAC payback to 12 + months, and maintain 75% gross margin.'" + - "Using annual goals in an early-stage SaaS company where conditions + change quarterly. Set 90-day goals with monthly check-ins." + - "Setting identical goals across functions. Engineering goals should be + about product quality and velocity; Sales goals should be about pipeline + and conversion; Customer Success goals should be about retention and + expansion." + saas_example: "Instead of 'grow revenue,' a SaaS company sets Q2 goals: (1) + Increase MRR from $150K to $200K by adding 30 new customers at $1,200 + average MRR and expanding 15 existing customers by $500 average. (2) + Reduce logo churn from 4% to 3% monthly by implementing a churn + early-warning system and proactive outreach for at-risk accounts. (3) + Decrease time to value from 14 days to 7 days by launching guided + onboarding and in-app tutorials. Each goal is specific, measurable, + connected to a responsible team, and achievable within the quarter." + benchmark_references: [ "mrr", "logo-churn", "time-to-value" ] - skill: "vuca-framework" category: "frameworks" saas_relevance: "moderate" - saas_context: "SaaS operates in a permanently VUCA environment. Volatility: revenue can swing dramatically with a single enterprise churn or win. Uncertainty: market dynamics shift as platforms (AI, cloud) evolve unpredictably. Complexity: the interplay of product, GTM, retention, and financing creates multi-variable decision spaces. Ambiguity: SaaS metrics can be interpreted in contradictory ways (high NRR masking logo churn, revenue growth hiding margin erosion). The VUCA framework helps SaaS leaders identify which type of challenge they face and respond appropriately — Vision for Volatility, Understanding for Uncertainty, Clarity for Complexity, Agility for Ambiguity." + saas_context: "SaaS operates in a permanently VUCA environment. Volatility: + revenue can swing dramatically with a single enterprise churn or win. + Uncertainty: market dynamics shift as platforms (AI, cloud) evolve + unpredictably. Complexity: the interplay of product, GTM, retention, and + financing creates multi-variable decision spaces. Ambiguity: SaaS metrics + can be interpreted in contradictory ways (high NRR masking logo churn, + revenue growth hiding margin erosion). The VUCA framework helps SaaS + leaders identify which type of challenge they face and respond + appropriately — Vision for Volatility, Understanding for Uncertainty, + Clarity for Complexity, Agility for Ambiguity." saas_anti_patterns: - - "Treating all challenges as one type. A pricing decision (Complexity — multiple variables to weigh) requires a different approach than a competitive response (Volatility — rapid reaction needed)." - - "Using Agility as an excuse for lack of strategy. SaaS companies that pivot constantly without strategic rationale mistake activity for progress." - saas_example: "When a major SaaS platform announces a native feature that competes with your product, the VUCA framework clarifies the response. This is Volatility (sudden market shift) and Ambiguity (unclear how customers will react). The response combines Vision (articulating why your dedicated product remains superior to a bundled feature) with Agility (rapidly building the integration that makes your product complementary rather than competitive to the platform)." - benchmark_references: ["win-rate", "logo-churn"] + - "Treating all challenges as one type. A pricing decision (Complexity — + multiple variables to weigh) requires a different approach than a + competitive response (Volatility — rapid reaction needed)." + - "Using Agility as an excuse for lack of strategy. SaaS companies that + pivot constantly without strategic rationale mistake activity for + progress." + saas_example: "When a major SaaS platform announces a native feature that + competes with your product, the VUCA framework clarifies the response. + This is Volatility (sudden market shift) and Ambiguity (unclear how + customers will react). The response combines Vision (articulating why your + dedicated product remains superior to a bundled feature) with Agility + (rapidly building the integration that makes your product complementary + rather than competitive to the platform)." + benchmark_references: [ "win-rate", "logo-churn" ] - skill: "trust-equation" category: "frameworks" saas_relevance: "high" - saas_context: "Trust is the fundamental currency in SaaS because customers grant continuous access to sensitive data and business processes. The Trust Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to SaaS as follows: Credibility = uptime track record, security certifications, public case studies. Reliability = consistent product performance, predictable release cadence, SLA adherence. Intimacy = understanding the customer's specific workflow and business context through customer success. Self-Orientation = transparency about product limitations, honest roadmap communication, fair pricing practices. High self-orientation (aggressive upselling, opaque pricing, lock-in tactics) destroys trust even when the other three components are strong." + saas_context: "Trust is the fundamental currency in SaaS because customers grant + continuous access to sensitive data and business processes. The Trust + Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to + SaaS as follows: Credibility = uptime track record, security + certifications, public case studies. Reliability = consistent product + performance, predictable release cadence, SLA adherence. Intimacy = + understanding the customer's specific workflow and business context + through customer success. Self-Orientation = transparency about product + limitations, honest roadmap communication, fair pricing practices. High + self-orientation (aggressive upselling, opaque pricing, lock-in tactics) + destroys trust even when the other three components are strong." saas_anti_patterns: - - "Investing in Credibility (certifications, logos, testimonials) while neglecting Reliability (uptime, bug fixes, performance). Customers notice when the marketing says 'enterprise-ready' but the product crashes weekly." - - "Using dark patterns to reduce churn (hiding cancellation buttons, requiring phone calls to cancel). This increases Self-Orientation and destroys trust, ultimately accelerating negative word-of-mouth." - - "Treating customer success as a retention tax rather than an Intimacy investment. CSMs who genuinely understand and advocate for customer outcomes build the trust that justifies premium pricing and long-term contracts." - saas_example: "Buffer built one of the strongest brands in SaaS through radical transparency — publishing their revenue dashboard, salary formula, and even their fundraising documents publicly. This drove Self-Orientation to near zero (nothing to hide), Credibility through demonstrated metrics, and Intimacy through open communication. The trust equation explains why Buffer retained customers even when competitors offered more features at lower prices." - benchmark_references: ["nps-saas", "logo-churn", "nrr"] + - "Investing in Credibility (certifications, logos, testimonials) while + neglecting Reliability (uptime, bug fixes, performance). Customers + notice when the marketing says 'enterprise-ready' but the product + crashes weekly." + - "Using dark patterns to reduce churn (hiding cancellation buttons, + requiring phone calls to cancel). This increases Self-Orientation and + destroys trust, ultimately accelerating negative word-of-mouth." + - "Treating customer success as a retention tax rather than an Intimacy + investment. CSMs who genuinely understand and advocate for customer + outcomes build the trust that justifies premium pricing and long-term + contracts." + saas_example: "Buffer built one of the strongest brands in SaaS through radical + transparency — publishing their revenue dashboard, salary formula, and + even their fundraising documents publicly. This drove Self-Orientation to + near zero (nothing to hide), Credibility through demonstrated metrics, and + Intimacy through open communication. The trust equation explains why + Buffer retained customers even when competitors offered more features at + lower prices." + benchmark_references: [ "nps-saas", "logo-churn", "nrr" ] - skill: "cialdini-influence" category: "frameworks" saas_relevance: "high" - saas_context: "Cialdini's six principles of influence map directly to SaaS conversion and retention mechanics. Reciprocity: freemium and free trials create obligation. Social Proof: customer logos, case studies, G2 reviews, and 'X companies use this' badges. Commitment & Consistency: free trial users who complete onboarding steps are far more likely to convert. Authority: SOC 2 compliance, industry analyst recognition, thought leadership content. Liking: brand personality, community, and customer success relationships. Scarcity: limited-time pricing, exclusive features for early adopters. Understanding these principles helps SaaS companies design more effective onboarding flows, pricing pages, and retention campaigns." + saas_context: "Cialdini's six principles of influence map directly to SaaS + conversion and retention mechanics. Reciprocity: freemium and free trials + create obligation. Social Proof: customer logos, case studies, G2 reviews, + and 'X companies use this' badges. Commitment & Consistency: free trial + users who complete onboarding steps are far more likely to convert. + Authority: SOC 2 compliance, industry analyst recognition, thought + leadership content. Liking: brand personality, community, and customer + success relationships. Scarcity: limited-time pricing, exclusive features + for early adopters. Understanding these principles helps SaaS companies + design more effective onboarding flows, pricing pages, and retention + campaigns." saas_anti_patterns: - - "Over-relying on Scarcity (fake urgency, countdown timers, 'only 3 seats left' for a software product with infinite supply). SaaS buyers are sophisticated enough to recognize manufactured scarcity." - - "Neglecting Social Proof for early-stage products. Even 5 good case studies are more persuasive than feature lists. Invest in customer stories before investing in marketing copy." - - "Using Authority signals (enterprise logos, compliance badges) that are irrelevant to the target buyer. An SMB buyer does not care about Fortune 500 logos — they care about companies like theirs." - saas_example: "Notion's growth leveraged multiple Cialdini principles simultaneously: Reciprocity (generous free plan), Social Proof (template gallery showcasing real user setups, public customer stories), Commitment (progressive onboarding that builds invested workspace), Liking (design-forward brand that users identify with), and Authority (adoption by respected teams at companies like Figma, Loom, and Pixar). The combination created viral organic growth that reduced CAC to near zero for the individual and small-team segments." - benchmark_references: ["activation-rate", "cac", "nps-saas"] + - "Over-relying on Scarcity (fake urgency, countdown timers, 'only 3 seats + left' for a software product with infinite supply). SaaS buyers are + sophisticated enough to recognize manufactured scarcity." + - "Neglecting Social Proof for early-stage products. Even 5 good case + studies are more persuasive than feature lists. Invest in customer + stories before investing in marketing copy." + - "Using Authority signals (enterprise logos, compliance badges) that are + irrelevant to the target buyer. An SMB buyer does not care about Fortune + 500 logos — they care about companies like theirs." + saas_example: "Notion's growth leveraged multiple Cialdini principles + simultaneously: Reciprocity (generous free plan), Social Proof (template + gallery showcasing real user setups, public customer stories), Commitment + (progressive onboarding that builds invested workspace), Liking + (design-forward brand that users identify with), and Authority (adoption + by respected teams at companies like Figma, Loom, and Pixar). The + combination created viral organic growth that reduced CAC to near zero for + the individual and small-team segments." + benchmark_references: [ "activation-rate", "cac", "nps-saas" ] - skill: "emotional-intelligence" category: "frameworks" saas_relevance: "moderate" - saas_context: "Emotional intelligence in SaaS is a competitive advantage in three domains: customer relationships (reading buyer sentiment during sales cycles, detecting at-risk customers before they churn), team leadership (managing high-intensity engineering and sales teams through hypergrowth, handling layoffs and restructuring), and investor relations (managing board dynamics, delivering bad news effectively, building relationships that survive downturns). SaaS companies operate at high intensity with frequent change — emotional intelligence is the lubricant that prevents organizational friction from becoming organizational failure." + saas_context: "Emotional intelligence in SaaS is a competitive advantage in + three domains: customer relationships (reading buyer sentiment during + sales cycles, detecting at-risk customers before they churn), team + leadership (managing high-intensity engineering and sales teams through + hypergrowth, handling layoffs and restructuring), and investor relations + (managing board dynamics, delivering bad news effectively, building + relationships that survive downturns). SaaS companies operate at high + intensity with frequent change — emotional intelligence is the lubricant + that prevents organizational friction from becoming organizational + failure." saas_anti_patterns: - - "Treating emotional intelligence as 'soft' while privileging metrics above all else. A SaaS CEO who can read a P&L but cannot read a room will lose top talent and damage key customer relationships." - - "Confusing empathy with permissiveness. Emotional intelligence does not mean avoiding hard conversations — it means having them with awareness of their emotional impact." - saas_example: "A SaaS VP of Customer Success notices that a strategic account's champion has become less responsive and stopped attending QBRs. Rather than sending another automated check-in email, she reaches out personally and discovers the champion is frustrated by a product limitation that was deprioritized on the roadmap. The emotionally intelligent response is not to promise a feature that cannot be delivered but to acknowledge the frustration, share the honest trade-off reasoning, and collaborate on a workaround — preserving the relationship and the account." - benchmark_references: ["nrr", "nps-saas"] + - "Treating emotional intelligence as 'soft' while privileging metrics + above all else. A SaaS CEO who can read a P&L but cannot read a room + will lose top talent and damage key customer relationships." + - "Confusing empathy with permissiveness. Emotional intelligence does not + mean avoiding hard conversations — it means having them with awareness + of their emotional impact." + saas_example: "A SaaS VP of Customer Success notices that a strategic account's + champion has become less responsive and stopped attending QBRs. Rather + than sending another automated check-in email, she reaches out personally + and discovers the champion is frustrated by a product limitation that was + deprioritized on the roadmap. The emotionally intelligent response is not + to promise a feature that cannot be delivered but to acknowledge the + frustration, share the honest trade-off reasoning, and collaborate on a + workaround — preserving the relationship and the account." + benchmark_references: [ "nrr", "nps-saas" ] - skill: "covey-seven-habits" category: "frameworks" saas_relevance: "moderate" - saas_context: "The Seven Habits apply to SaaS founders and operators who must balance the intense short-term demands of a subscription business with long-term strategic thinking. 'Begin with the End in Mind' means defining the endgame — IPO, acquisition, profitable growth — and aligning every operational decision with it. 'Put First Things First' maps to the Not Urgent/Important quadrant where strategic SaaS work (product vision, platform architecture, culture building) lives. 'Think Win-Win' is essential for partner ecosystem development, which is a key SaaS growth lever. 'Sharpen the Saw' addresses the burnout epidemic in SaaS leadership." + saas_context: "The Seven Habits apply to SaaS founders and operators who must + balance the intense short-term demands of a subscription business with + long-term strategic thinking. 'Begin with the End in Mind' means defining + the endgame — IPO, acquisition, profitable growth — and aligning every + operational decision with it. 'Put First Things First' maps to the Not + Urgent/Important quadrant where strategic SaaS work (product vision, + platform architecture, culture building) lives. 'Think Win-Win' is + essential for partner ecosystem development, which is a key SaaS growth + lever. 'Sharpen the Saw' addresses the burnout epidemic in SaaS + leadership." saas_anti_patterns: - - "Sacrificing Habit 7 (Sharpen the Saw / personal renewal) for growth targets. SaaS founding teams that burn out sacrifice the judgment and creativity that drove early success." - - "Applying 'Win-Win' naively in competitive deals. Win-Win applies to partnerships and customer relationships, not necessarily to competitive displacement scenarios." - saas_example: "A SaaS founder applies 'Begin with the End in Mind' to realize that their current growth trajectory leads to a $20M ARR company that is neither attractive for acquisition (too small) nor viable for IPO (too small). This analysis forces a strategic choice: accelerate to $50M+ ARR (requiring a larger raise and more aggressive growth), or optimize for profitability and build a durable, cash-generating business. Both are valid endpoints — but the current path reaches neither." - benchmark_references: ["arr", "rule-of-40", "burn-multiple"] + - "Sacrificing Habit 7 (Sharpen the Saw / personal renewal) for growth + targets. SaaS founding teams that burn out sacrifice the judgment and + creativity that drove early success." + - "Applying 'Win-Win' naively in competitive deals. Win-Win applies to + partnerships and customer relationships, not necessarily to competitive + displacement scenarios." + saas_example: "A SaaS founder applies 'Begin with the End in Mind' to realize + that their current growth trajectory leads to a $20M ARR company that is + neither attractive for acquisition (too small) nor viable for IPO (too + small). This analysis forces a strategic choice: accelerate to $50M+ ARR + (requiring a larger raise and more aggressive growth), or optimize for + profitability and build a durable, cash-generating business. Both are + valid endpoints — but the current path reaches neither." + benchmark_references: [ "arr", "rule-of-40", "burn-multiple" ] # ───────────────────────────────────────────── # NEGOTIATION (4 skills) @@ -279,45 +741,129 @@ skill_overlays: - skill: "competitive-negotiation" category: "negotiation" saas_relevance: "high" - saas_context: "Competitive negotiation in SaaS occurs across three primary contexts: enterprise sales (negotiating contract terms, pricing, and SLAs with procurement teams), fundraising (negotiating term sheets with investors), and vendor relationships (negotiating with cloud providers, API vendors, and service partners). In enterprise SaaS sales, the negotiation dynamics are shaped by annual budgets, multi-stakeholder approval processes, and the buyer's leverage from low switching costs. In fundraising, the negotiation centers on valuation, board composition, protective provisions, and liquidation preferences." + saas_context: "Competitive negotiation in SaaS occurs across three primary + contexts: enterprise sales (negotiating contract terms, pricing, and SLAs + with procurement teams), fundraising (negotiating term sheets with + investors), and vendor relationships (negotiating with cloud providers, + API vendors, and service partners). In enterprise SaaS sales, the + negotiation dynamics are shaped by annual budgets, multi-stakeholder + approval processes, and the buyer's leverage from low switching costs. In + fundraising, the negotiation centers on valuation, board composition, + protective provisions, and liquidation preferences." saas_anti_patterns: - - "Discounting too quickly in enterprise sales negotiations. Every discount trains the buyer to negotiate harder next time and erodes ARPU across the customer base. Offer scope concessions (fewer seats, limited features) rather than price concessions." - - "Negotiating valuation in isolation during fundraising. The valuation is one term among many — pro-rata rights, board seats, protective provisions, and liquidation preferences can be more impactful than a higher valuation with worse terms." - - "Treating SaaS contract negotiation as zero-sum. The best enterprise deals create long-term partnerships where the customer's success drives expansion revenue." - saas_example: "A SaaS company negotiating a $200K ACV enterprise deal faces pressure to discount by 30%. Instead of cutting price, the sales team offers a two-year commitment at 15% discount (locking in revenue), includes a success milestone clause (if the customer achieves defined ROI metrics, the contract auto-renews at full price), and adds a 90-day pilot period at full price with exit rights. This preserves ARPU while addressing the buyer's risk concern." - benchmark_references: ["acv", "arpu", "win-rate", "sales-cycle-length"] + - "Discounting too quickly in enterprise sales negotiations. Every + discount trains the buyer to negotiate harder next time and erodes ARPU + across the customer base. Offer scope concessions (fewer seats, limited + features) rather than price concessions." + - "Negotiating valuation in isolation during fundraising. The valuation is + one term among many — pro-rata rights, board seats, protective + provisions, and liquidation preferences can be more impactful than a + higher valuation with worse terms." + - "Treating SaaS contract negotiation as zero-sum. The best enterprise + deals create long-term partnerships where the customer's success drives + expansion revenue." + saas_example: "A SaaS company negotiating a $200K ACV enterprise deal faces + pressure to discount by 30%. Instead of cutting price, the sales team + offers a two-year commitment at 15% discount (locking in revenue), + includes a success milestone clause (if the customer achieves defined ROI + metrics, the contract auto-renews at full price), and adds a 90-day pilot + period at full price with exit rights. This preserves ARPU while + addressing the buyer's risk concern." + benchmark_references: [ "acv", "arpu", "win-rate", "sales-cycle-length" ] - skill: "cooperative-negotiation" category: "negotiation" saas_relevance: "high" - saas_context: "Cooperative negotiation is the foundation of SaaS partnership development — a critical growth lever. SaaS partnerships include: technology integrations (building with complementary products), channel partnerships (reselling through consultants or agencies), platform partnerships (building on top of ecosystems like Salesforce, Shopify, or Slack), and strategic alliances (co-selling with larger vendors). Cooperative negotiation is also essential for customer success — the ongoing relationship between vendor and customer in SaaS is a continuous negotiation about priorities, roadmap influence, and terms." + saas_context: "Cooperative negotiation is the foundation of SaaS partnership + development — a critical growth lever. SaaS partnerships include: + technology integrations (building with complementary products), channel + partnerships (reselling through consultants or agencies), platform + partnerships (building on top of ecosystems like Salesforce, Shopify, or + Slack), and strategic alliances (co-selling with larger vendors). + Cooperative negotiation is also essential for customer success — the + ongoing relationship between vendor and customer in SaaS is a continuous + negotiation about priorities, roadmap influence, and terms." saas_anti_patterns: - - "Entering partnership negotiations without clear metrics for success. Define what each partner gains (revenue share, distribution, data, brand) before negotiating terms." - - "Giving away too much in platform partnerships for the sake of 'ecosystem access.' A SaaS company that builds its entire distribution on a partner's marketplace is one policy change away from destruction." - - "Neglecting the cooperative dimension of customer renewals. Renewal negotiation should be a collaborative discussion about value delivered and value planned, not a transactional price conversation." - saas_example: "A SaaS company negotiates an integration partnership with a 10x-larger company. Rather than accepting a standard API agreement, they use cooperative negotiation to propose a deeper arrangement: co-marketing (joint case studies and webinars), co-selling (mutual referral program with revenue share), and data sharing (anonymized usage patterns that benefit both products). The cooperative approach creates mutual dependency that protects the smaller company from being cut off or replicated." - benchmark_references: ["cac", "nrr", "arr"] + - "Entering partnership negotiations without clear metrics for success. + Define what each partner gains (revenue share, distribution, data, + brand) before negotiating terms." + - "Giving away too much in platform partnerships for the sake of + 'ecosystem access.' A SaaS company that builds its entire distribution + on a partner's marketplace is one policy change away from destruction." + - "Neglecting the cooperative dimension of customer renewals. Renewal + negotiation should be a collaborative discussion about value delivered + and value planned, not a transactional price conversation." + saas_example: "A SaaS company negotiates an integration partnership with a + 10x-larger company. Rather than accepting a standard API agreement, they + use cooperative negotiation to propose a deeper arrangement: co-marketing + (joint case studies and webinars), co-selling (mutual referral program + with revenue share), and data sharing (anonymized usage patterns that + benefit both products). The cooperative approach creates mutual dependency + that protects the smaller company from being cut off or replicated." + benchmark_references: [ "cac", "nrr", "arr" ] - skill: "delivering-the-deal" category: "negotiation" saas_relevance: "high" - saas_context: "Deal execution in SaaS has unique characteristics: procurement cycles are increasingly governed by IT security reviews and legal red-lining that can stall deals for months; annual budget cycles create quarterly and year-end urgency; and multi-year commitments involve complex terms (price escalators, renewal terms, termination clauses, data deletion obligations). The skill of delivering the deal in SaaS means managing these complexities while maintaining momentum. This includes preparing for security questionnaires before they arrive, having flexible contract templates ready, and building internal champions who drive urgency within the buyer organization." + saas_context: "Deal execution in SaaS has unique characteristics: procurement + cycles are increasingly governed by IT security reviews and legal + red-lining that can stall deals for months; annual budget cycles create + quarterly and year-end urgency; and multi-year commitments involve complex + terms (price escalators, renewal terms, termination clauses, data deletion + obligations). The skill of delivering the deal in SaaS means managing + these complexities while maintaining momentum. This includes preparing for + security questionnaires before they arrive, having flexible contract + templates ready, and building internal champions who drive urgency within + the buyer organization." saas_anti_patterns: - - "Allowing legal and security review to happen sequentially. Run security review, legal review, and commercial negotiation in parallel. Sequential reviews double the sales cycle." - - "Relying on end-of-quarter urgency to close deals. Buyers increasingly recognize and resist quarter-end pressure tactics. Build urgency through value demonstration, not calendar manipulation." - - "Celebrating the closed deal before implementation begins. In SaaS, the deal is not truly 'delivered' until the customer is activated and deriving value. Handoff to customer success is part of the deal." - saas_example: "A SaaS sales team creates a 'deal acceleration kit': pre-completed security questionnaires (SOC 2 Type II, GDPR DPA, penetration test results), a flexible order form with pre-approved discount tiers and term options, and a mutual success plan template that aligns both teams on implementation milestones. This kit reduces average enterprise sales cycle from 90 to 55 days by eliminating the two most common stall points: security review and contract negotiation." - benchmark_references: ["sales-cycle-length", "win-rate", "acv"] + - "Allowing legal and security review to happen sequentially. Run security + review, legal review, and commercial negotiation in parallel. Sequential + reviews double the sales cycle." + - "Relying on end-of-quarter urgency to close deals. Buyers increasingly + recognize and resist quarter-end pressure tactics. Build urgency through + value demonstration, not calendar manipulation." + - "Celebrating the closed deal before implementation begins. In SaaS, the + deal is not truly 'delivered' until the customer is activated and + deriving value. Handoff to customer success is part of the deal." + saas_example: "A SaaS sales team creates a 'deal acceleration kit': + pre-completed security questionnaires (SOC 2 Type II, GDPR DPA, + penetration test results), a flexible order form with pre-approved + discount tiers and term options, and a mutual success plan template that + aligns both teams on implementation milestones. This kit reduces average + enterprise sales cycle from 90 to 55 days by eliminating the two most + common stall points: security review and contract negotiation." + benchmark_references: [ "sales-cycle-length", "win-rate", "acv" ] - skill: "negotiation-mindset-and-self" category: "negotiation" saas_relevance: "moderate" - saas_context: "SaaS founders negotiate constantly — with investors, customers, employees, and partners — often from a position of perceived weakness (smaller company, less capital, fewer customers). The negotiation mindset skill helps founders recognize and manage the psychological dynamics of these asymmetric negotiations. In fundraising, founders must balance desperation (running out of runway) with confidence (demonstrating conviction in the business). In enterprise sales, founders must negotiate with procurement teams whose explicit goal is to reduce price. In hiring, founders must negotiate compensation packages with candidates who have offers from larger, better-funded companies." + saas_context: "SaaS founders negotiate constantly — with investors, customers, + employees, and partners — often from a position of perceived weakness + (smaller company, less capital, fewer customers). The negotiation mindset + skill helps founders recognize and manage the psychological dynamics of + these asymmetric negotiations. In fundraising, founders must balance + desperation (running out of runway) with confidence (demonstrating + conviction in the business). In enterprise sales, founders must negotiate + with procurement teams whose explicit goal is to reduce price. In hiring, + founders must negotiate compensation packages with candidates who have + offers from larger, better-funded companies." saas_anti_patterns: - - "Anchoring on valuation before building leverage. In fundraising, the strongest negotiating position comes from having multiple term sheets, strong metrics, and a credible alternative (profitability). Negotiate from strength, not from need." - - "Internalizing the power asymmetry in enterprise sales. The buyer needs the product (or they would not be in the evaluation). The vendor's perceived weakness is often exaggerated." - saas_example: "A SaaS founder entering Series A negotiations with a tier-one VC recognizes the psychological pattern: the VC asks probing questions that feel like criticism, triggering defensiveness. By preparing for this dynamic through negotiation mindset work, the founder reframes critical questions as engagement signals (the VC is doing diligence because they are interested) and responds with confidence and data rather than defensiveness. The result: better terms because the founder demonstrated conviction." - benchmark_references: ["arr", "cac"] + - "Anchoring on valuation before building leverage. In fundraising, the + strongest negotiating position comes from having multiple term sheets, + strong metrics, and a credible alternative (profitability). Negotiate + from strength, not from need." + - "Internalizing the power asymmetry in enterprise sales. The buyer needs + the product (or they would not be in the evaluation). The vendor's + perceived weakness is often exaggerated." + saas_example: "A SaaS founder entering Series A negotiations with a tier-one VC + recognizes the psychological pattern: the VC asks probing questions that + feel like criticism, triggering defensiveness. By preparing for this + dynamic through negotiation mindset work, the founder reframes critical + questions as engagement signals (the VC is doing diligence because they + are interested) and responds with confidence and data rather than + defensiveness. The result: better terms because the founder demonstrated + conviction." + benchmark_references: [ "arr", "cac" ] # ───────────────────────────────────────────── # THINKING (4 skills) @@ -326,44 +872,133 @@ skill_overlays: - skill: "enemies-of-clear-thinking" category: "thinking" saas_relevance: "critical" - saas_context: "SaaS operators face specific cognitive traps amplified by the data-rich, fast-moving nature of the business. Survivorship bias: benchmarking against successful SaaS companies while ignoring the majority that failed. Sunk cost fallacy: continuing to invest in a feature or market segment because of past investment rather than future potential. Confirmation bias: interpreting ambiguous metrics as positive signals (e.g., 'churn is seasonal' when it is structural). Anchoring: fixating on the initial pricing or valuation and resisting evidence that it should change. Availability bias: over-weighting the most recent customer conversation or competitive threat." + saas_context: "SaaS operators face specific cognitive traps amplified by the + data-rich, fast-moving nature of the business. Survivorship bias: + benchmarking against successful SaaS companies while ignoring the majority + that failed. Sunk cost fallacy: continuing to invest in a feature or + market segment because of past investment rather than future potential. + Confirmation bias: interpreting ambiguous metrics as positive signals + (e.g., 'churn is seasonal' when it is structural). Anchoring: fixating on + the initial pricing or valuation and resisting evidence that it should + change. Availability bias: over-weighting the most recent customer + conversation or competitive threat." saas_anti_patterns: - - "Using vanity metrics (total sign-ups, page views, feature usage counts) that confirm the narrative while ignoring the metrics that challenge it (activation rate, revenue churn, NPS trend)." - - "Anchoring on the fundraising valuation as an indicator of company worth. The last-round valuation is a negotiated price for preferred equity, not a measure of business value." - - "Confusing correlation with causation in product analytics. The fact that users who complete onboarding retain better does not mean forcing all users through onboarding will improve retention — the correlation may reflect user intent, not the onboarding itself." - saas_example: "A SaaS CEO reviews monthly metrics and concludes the business is healthy: MRR is growing 10% MoM, NRR is 115%, and NPS is 45. An advisor trained in clear thinking spots the hidden problem: 80% of new MRR comes from a single channel (a content piece that went viral), NRR is inflated by one enterprise customer's massive expansion, and NPS was surveyed only among power users. The 'healthy' picture is a collection of non-representative data points — clear thinking demands disaggregation and stress-testing." - benchmark_references: ["mrr", "nrr", "nps-saas", "logo-churn"] + - "Using vanity metrics (total sign-ups, page views, feature usage counts) + that confirm the narrative while ignoring the metrics that challenge it + (activation rate, revenue churn, NPS trend)." + - "Anchoring on the fundraising valuation as an indicator of company + worth. The last-round valuation is a negotiated price for preferred + equity, not a measure of business value." + - "Confusing correlation with causation in product analytics. The fact + that users who complete onboarding retain better does not mean forcing + all users through onboarding will improve retention — the correlation + may reflect user intent, not the onboarding itself." + saas_example: "A SaaS CEO reviews monthly metrics and concludes the business is + healthy: MRR is growing 10% MoM, NRR is 115%, and NPS is 45. An advisor + trained in clear thinking spots the hidden problem: 80% of new MRR comes + from a single channel (a content piece that went viral), NRR is inflated + by one enterprise customer's massive expansion, and NPS was surveyed only + among power users. The 'healthy' picture is a collection of + non-representative data points — clear thinking demands disaggregation and + stress-testing." + benchmark_references: [ "mrr", "nrr", "nps-saas", "logo-churn" ] - skill: "evaluating-and-deciding" category: "thinking" saas_relevance: "high" - saas_context: "SaaS operators make high-frequency, high-impact decisions: which features to build, how to price, when to raise, whom to hire, and which market segments to pursue. The evaluation framework must account for SaaS-specific decision characteristics: most decisions are reversible (pricing can be changed, features can be deprecated), speed of decision usually matters more than perfection, and the cost of information-gathering often exceeds the cost of a wrong decision that can be corrected quickly. The distinction between one-way doors (irreversible: selling the company, choosing an architecture, raising a priced round) and two-way doors (reversible: pricing changes, market positioning, feature launches) should guide the decision framework." + saas_context: "SaaS operators make high-frequency, high-impact decisions: which + features to build, how to price, when to raise, whom to hire, and which + market segments to pursue. The evaluation framework must account for + SaaS-specific decision characteristics: most decisions are reversible + (pricing can be changed, features can be deprecated), speed of decision + usually matters more than perfection, and the cost of + information-gathering often exceeds the cost of a wrong decision that can + be corrected quickly. The distinction between one-way doors (irreversible: + selling the company, choosing an architecture, raising a priced round) and + two-way doors (reversible: pricing changes, market positioning, feature + launches) should guide the decision framework." saas_anti_patterns: - - "Applying one-way-door deliberation to two-way-door decisions. Spending three months analyzing a pricing change that can be tested and reversed in one week." - - "Deciding by committee. SaaS companies that require consensus for every product decision ship slowly and build mediocre products. Assign clear decision owners." - - "Over-relying on data for decisions that require judgment. Many critical SaaS decisions (product vision, market positioning, culture) involve insufficient data for purely analytical decision-making." - saas_example: "A SaaS product team debates whether to build a new analytics module or improve the onboarding flow. Traditional evaluation stalls because both have strong arguments. Applying the two-way door test: the analytics module requires 3 months of engineering and is difficult to reverse once shipped (one-way door). Improving onboarding can be tested in 2 weeks with an A/B test and reversed instantly (two-way door). Decision: test the onboarding improvement immediately, schedule the analytics module for the next planning cycle with better data from the onboarding test." - benchmark_references: ["activation-rate", "time-to-value"] + - "Applying one-way-door deliberation to two-way-door decisions. Spending + three months analyzing a pricing change that can be tested and reversed + in one week." + - "Deciding by committee. SaaS companies that require consensus for every + product decision ship slowly and build mediocre products. Assign clear + decision owners." + - "Over-relying on data for decisions that require judgment. Many critical + SaaS decisions (product vision, market positioning, culture) involve + insufficient data for purely analytical decision-making." + saas_example: "A SaaS product team debates whether to build a new analytics + module or improve the onboarding flow. Traditional evaluation stalls + because both have strong arguments. Applying the two-way door test: the + analytics module requires 3 months of engineering and is difficult to + reverse once shipped (one-way door). Improving onboarding can be tested in + 2 weeks with an A/B test and reversed instantly (two-way door). Decision: + test the onboarding improvement immediately, schedule the analytics module + for the next planning cycle with better data from the onboarding test." + benchmark_references: [ "activation-rate", "time-to-value" ] - skill: "defining-and-exploring-problems" category: "thinking" saas_relevance: "high" - saas_context: "SaaS companies frequently solve the wrong problem because they conflate symptoms with root causes. A growth stall is a symptom; the problem might be churn, market saturation, competitive displacement, or GTM inefficiency. A support ticket volume spike is a symptom; the problem might be a product bug, a UX confusion, or a customer segment mismatch. The skill of defining problems precisely is particularly valuable in SaaS because the rich data environment creates an illusion of understanding — the team can describe what is happening in great detail without understanding why." + saas_context: "SaaS companies frequently solve the wrong problem because they + conflate symptoms with root causes. A growth stall is a symptom; the + problem might be churn, market saturation, competitive displacement, or + GTM inefficiency. A support ticket volume spike is a symptom; the problem + might be a product bug, a UX confusion, or a customer segment mismatch. + The skill of defining problems precisely is particularly valuable in SaaS + because the rich data environment creates an illusion of understanding — + the team can describe what is happening in great detail without + understanding why." saas_anti_patterns: - - "Defining the problem in terms of the preferred solution. 'We need to add feature X' is a solution statement, not a problem definition. 'Customers are churning because they cannot achieve Y outcome' is a problem definition." - - "Accepting the first framing. When the VP Sales says 'we have a pipeline problem,' the root cause might be a product problem (low win rate) or a marketing problem (low lead quality), not a sales capacity problem." - - "Using dashboards as a substitute for problem exploration. Dashboards show metrics; they do not explain causation. Understanding why NRR declined requires qualitative investigation, not more charts." - saas_example: "A SaaS company defines its problem as 'we need to reduce churn.' Rigorous problem exploration reveals three distinct problems: (1) SMB customers churn because they outgrow the product within 18 months — a product capability problem. (2) Mid-market customers churn during the transition from the sales team to customer success — a handoff process problem. (3) Enterprise customers churn when their internal champion leaves — a multi-threading relationship problem. Each requires a different solution. Lumping them together as 'churn' leads to generic interventions that solve none of them." - benchmark_references: ["logo-churn", "nrr", "grr"] + - "Defining the problem in terms of the preferred solution. 'We need to + add feature X' is a solution statement, not a problem definition. + 'Customers are churning because they cannot achieve Y outcome' is a + problem definition." + - "Accepting the first framing. When the VP Sales says 'we have a pipeline + problem,' the root cause might be a product problem (low win rate) or a + marketing problem (low lead quality), not a sales capacity problem." + - "Using dashboards as a substitute for problem exploration. Dashboards + show metrics; they do not explain causation. Understanding why NRR + declined requires qualitative investigation, not more charts." + saas_example: "A SaaS company defines its problem as 'we need to reduce churn.' + Rigorous problem exploration reveals three distinct problems: (1) SMB + customers churn because they outgrow the product within 18 months — a + product capability problem. (2) Mid-market customers churn during the + transition from the sales team to customer success — a handoff process + problem. (3) Enterprise customers churn when their internal champion + leaves — a multi-threading relationship problem. Each requires a different + solution. Lumping them together as 'churn' leads to generic interventions + that solve none of them." + benchmark_references: [ "logo-churn", "nrr", "grr" ] - skill: "building-thinking-strength" category: "thinking" saas_relevance: "moderate" - saas_context: "SaaS leadership demands sustained intellectual rigor across diverse domains — product strategy, financial modeling, organizational design, competitive analysis, and customer psychology. Building thinking strength in the SaaS context means developing the ability to shift fluently between these domains, hold multiple conflicting hypotheses simultaneously, and update beliefs quickly as new data arrives. The pace of SaaS means that thinking capacity is a rate-limiter on organizational performance — the company can only execute as fast as its leaders can think clearly." + saas_context: "SaaS leadership demands sustained intellectual rigor across + diverse domains — product strategy, financial modeling, organizational + design, competitive analysis, and customer psychology. Building thinking + strength in the SaaS context means developing the ability to shift + fluently between these domains, hold multiple conflicting hypotheses + simultaneously, and update beliefs quickly as new data arrives. The pace + of SaaS means that thinking capacity is a rate-limiter on organizational + performance — the company can only execute as fast as its leaders can + think clearly." saas_anti_patterns: - - "Equating busyness with thinking. A SaaS executive in back-to-back meetings all day has no time to think. Protecting blocks of uninterrupted thinking time is not a luxury — it is a core leadership practice." - - "Over-specializing thinking. A SaaS CEO who thinks only about product neglects GTM; one who thinks only about sales neglects product. The role requires integrative thinking across all domains." - saas_example: "A SaaS founder implements a 'thinking ritual': every Monday morning, 90 minutes with no meetings, no Slack, and no email. During this time, they review the prior week's metrics, read one competitor's recent release notes, and write a one-page memo on the single most important strategic question facing the company this week. This practice compounds — after six months, the founder has a 26-memo archive that documents the evolution of their strategic thinking and provides a decision audit trail." + - "Equating busyness with thinking. A SaaS executive in back-to-back + meetings all day has no time to think. Protecting blocks of + uninterrupted thinking time is not a luxury — it is a core leadership + practice." + - "Over-specializing thinking. A SaaS CEO who thinks only about product + neglects GTM; one who thinks only about sales neglects product. The role + requires integrative thinking across all domains." + saas_example: "A SaaS founder implements a 'thinking ritual': every Monday + morning, 90 minutes with no meetings, no Slack, and no email. During this + time, they review the prior week's metrics, read one competitor's recent + release notes, and write a one-page memo on the single most important + strategic question facing the company this week. This practice compounds — + after six months, the founder has a 26-memo archive that documents the + evolution of their strategic thinking and provides a decision audit + trail." benchmark_references: [] # ───────────────────────────────────────────── @@ -373,35 +1008,106 @@ skill_overlays: - skill: "generating-solutions" category: "decisions" saas_relevance: "high" - saas_context: "Solution generation in SaaS benefits from the rapid testability of software hypotheses. Unlike physical product businesses, SaaS companies can prototype, test, and validate solutions in days or weeks. This changes the solution generation process: generate more options, evaluate them through quick tests rather than extended analysis, and iterate rapidly. The danger is that solution generation in SaaS becomes narrowly focused on product features. Many SaaS problems (churn, growth stalls, competitive pressure) have non-product solutions: pricing changes, market repositioning, partnership development, or organizational restructuring." + saas_context: "Solution generation in SaaS benefits from the rapid testability + of software hypotheses. Unlike physical product businesses, SaaS companies + can prototype, test, and validate solutions in days or weeks. This changes + the solution generation process: generate more options, evaluate them + through quick tests rather than extended analysis, and iterate rapidly. + The danger is that solution generation in SaaS becomes narrowly focused on + product features. Many SaaS problems (churn, growth stalls, competitive + pressure) have non-product solutions: pricing changes, market + repositioning, partnership development, or organizational restructuring." saas_anti_patterns: - - "Defaulting to 'build a feature' as the solution to every problem. Many SaaS problems are better solved through pricing, positioning, customer success, or go-to-market changes." - - "Generating solutions in isolation within functional silos. The best SaaS solutions often emerge at the intersection of product, sales, and customer success perspectives." - - "Eliminating solutions too early based on 'feasibility.' In SaaS, today's infeasible solution may become feasible with an API integration, an AI model, or a partner — the constraint landscape changes rapidly." - saas_example: "A SaaS company faces declining win rates against a well-funded competitor. The product team's solution: build the five features the competitor has that they lack (6-month project). A broader solution generation exercise produces alternatives: (1) reposition as the specialist for a specific vertical the competitor ignores, (2) launch a free tier to win at the top of the funnel, (3) build an integration with the competitor so customers can use both, (4) acquire a smaller company that already has the missing features. Options 1 and 2 can be tested in weeks; option 3 in months; only option 4 and the original 'build features' plan require 6+ months." - benchmark_references: ["win-rate", "cac", "time-to-value"] + - "Defaulting to 'build a feature' as the solution to every problem. Many + SaaS problems are better solved through pricing, positioning, customer + success, or go-to-market changes." + - "Generating solutions in isolation within functional silos. The best + SaaS solutions often emerge at the intersection of product, sales, and + customer success perspectives." + - "Eliminating solutions too early based on 'feasibility.' In SaaS, + today's infeasible solution may become feasible with an API integration, + an AI model, or a partner — the constraint landscape changes rapidly." + saas_example: "A SaaS company faces declining win rates against a well-funded + competitor. The product team's solution: build the five features the + competitor has that they lack (6-month project). A broader solution + generation exercise produces alternatives: (1) reposition as the + specialist for a specific vertical the competitor ignores, (2) launch a + free tier to win at the top of the funnel, (3) build an integration with + the competitor so customers can use both, (4) acquire a smaller company + that already has the missing features. Options 1 and 2 can be tested in + weeks; option 3 in months; only option 4 and the original 'build features' + plan require 6+ months." + benchmark_references: [ "win-rate", "cac", "time-to-value" ] - skill: "choosing-and-executing" category: "decisions" saas_relevance: "high" - saas_context: "Execution speed is a primary competitive advantage in SaaS. The choosing-and-executing framework must emphasize speed-to-learning over correctness-of-choice for reversible decisions. In SaaS, the cost of choosing wrong and iterating is usually lower than the cost of choosing slowly and executing late. Execution in SaaS also requires explicit coordination across product, engineering, sales, marketing, and customer success — siloed execution produces internal inconsistency (marketing promises features that product has not built, sales sells contracts that operations cannot support)." + saas_context: "Execution speed is a primary competitive advantage in SaaS. The + choosing-and-executing framework must emphasize speed-to-learning over + correctness-of-choice for reversible decisions. In SaaS, the cost of + choosing wrong and iterating is usually lower than the cost of choosing + slowly and executing late. Execution in SaaS also requires explicit + coordination across product, engineering, sales, marketing, and customer + success — siloed execution produces internal inconsistency (marketing + promises features that product has not built, sales sells contracts that + operations cannot support)." saas_anti_patterns: - - "Seeking consensus before executing reversible decisions. SaaS companies that require agreement from all stakeholders move too slowly. Use the 'disagree and commit' principle." - - "Executing without defining success metrics. Before launching a feature, pricing change, or marketing campaign, define what success looks like and when you will evaluate." - - "Confusing execution with shipping. In SaaS, execution includes launch, measurement, iteration, and communication — not just writing code and deploying." - saas_example: "A SaaS company must decide between two pricing strategies: (A) per-seat pricing to maximize revenue from large teams, or (B) usage-based pricing to lower barriers and maximize adoption. Instead of debating for months, they define a 60-day test: existing customers above 50 seats get offered the per-seat model; new sign-ups under 20 seats get offered usage-based. Success metrics: conversion rate, ARPU, and expansion rate for each cohort. After 60 days, the data clearly favors usage-based for new customers and per-seat for existing enterprise — they implement a hybrid model." - benchmark_references: ["arpu", "activation-rate", "expansion-revenue-pct"] + - "Seeking consensus before executing reversible decisions. SaaS companies + that require agreement from all stakeholders move too slowly. Use the + 'disagree and commit' principle." + - "Executing without defining success metrics. Before launching a feature, + pricing change, or marketing campaign, define what success looks like + and when you will evaluate." + - "Confusing execution with shipping. In SaaS, execution includes launch, + measurement, iteration, and communication — not just writing code and + deploying." + saas_example: "A SaaS company must decide between two pricing strategies: (A) + per-seat pricing to maximize revenue from large teams, or (B) usage-based + pricing to lower barriers and maximize adoption. Instead of debating for + months, they define a 60-day test: existing customers above 50 seats get + offered the per-seat model; new sign-ups under 20 seats get offered + usage-based. Success metrics: conversion rate, ARPU, and expansion rate + for each cohort. After 60 days, the data clearly favors usage-based for + new customers and per-seat for existing enterprise — they implement a + hybrid model." + benchmark_references: [ "arpu", "activation-rate", "expansion-revenue-pct" ] - skill: "tough-decision-situations" category: "decisions" saas_relevance: "high" - saas_context: "SaaS founders face uniquely difficult decisions: whether to raise money or bootstrap, when to pivot the product or persist, whether to fire a co-founder, when to accept an acquisition offer, how to manage layoffs during a downturn, and whether to sunset a product line that loyal customers depend on. These decisions are tough because they are irreversible (or nearly so), involve deep uncertainty, carry emotional weight, and have consequences for many stakeholders. The SaaS context adds specific pressures: venture capital timelines create artificial urgency, public metrics create accountability, and the continuous nature of subscriptions means customers feel the impact immediately." + saas_context: "SaaS founders face uniquely difficult decisions: whether to raise + money or bootstrap, when to pivot the product or persist, whether to fire + a co-founder, when to accept an acquisition offer, how to manage layoffs + during a downturn, and whether to sunset a product line that loyal + customers depend on. These decisions are tough because they are + irreversible (or nearly so), involve deep uncertainty, carry emotional + weight, and have consequences for many stakeholders. The SaaS context adds + specific pressures: venture capital timelines create artificial urgency, + public metrics create accountability, and the continuous nature of + subscriptions means customers feel the impact immediately." saas_anti_patterns: - - "Delaying tough decisions until they become crises. In SaaS, the compounding nature of recurring revenue means that every month of delay in addressing a broken GTM motion, an underperforming leader, or a failing product line compounds the damage." - - "Making tough decisions in isolation. SaaS founders often carry the burden alone — advisors, board members, and executive coaches exist precisely for these moments." - - "Framing tough decisions as binary. 'Raise or die' is rarely the actual choice set. Most tough decisions have creative alternatives that emerge only when the full option space is explored." - saas_example: "A SaaS founder receives an acquisition offer at 8x ARR — a strong multiple. The company is growing 2x YoY with 18 months of runway. The tough decision framework surfaces the key tensions: the offer is above-market for the company's size, but the growth rate suggests significantly more value creation if they continue. The framework also surfaces the emotional dimension: the founder is tired, the team is burnt out, and the acquirer would provide stability. Rather than deciding immediately, the founder maps all stakeholders' interests, defines the minimum acceptable outcome for each, and discovers a third option: a growth round that partially liquidates the founder's equity while keeping the company independent." - benchmark_references: ["arr", "burn-multiple", "rule-of-40"] + - "Delaying tough decisions until they become crises. In SaaS, the + compounding nature of recurring revenue means that every month of delay + in addressing a broken GTM motion, an underperforming leader, or a + failing product line compounds the damage." + - "Making tough decisions in isolation. SaaS founders often carry the + burden alone — advisors, board members, and executive coaches exist + precisely for these moments." + - "Framing tough decisions as binary. 'Raise or die' is rarely the actual + choice set. Most tough decisions have creative alternatives that emerge + only when the full option space is explored." + saas_example: "A SaaS founder receives an acquisition offer at 8x ARR — a strong + multiple. The company is growing 2x YoY with 18 months of runway. The + tough decision framework surfaces the key tensions: the offer is + above-market for the company's size, but the growth rate suggests + significantly more value creation if they continue. The framework also + surfaces the emotional dimension: the founder is tired, the team is burnt + out, and the acquirer would provide stability. Rather than deciding + immediately, the founder maps all stakeholders' interests, defines the + minimum acceptable outcome for each, and discovers a third option: a + growth round that partially liquidates the founder's equity while keeping + the company independent." + benchmark_references: [ "arr", "burn-multiple", "rule-of-40" ] # ───────────────────────────────────────────── # GAME THEORY (3 skills) @@ -410,34 +1116,98 @@ skill_overlays: - skill: "game-theory-fundamentals" category: "game-theory" saas_relevance: "high" - saas_context: "SaaS markets are repeated games with observable moves — every product launch, pricing change, and funding announcement is visible to competitors. This makes game theory directly applicable. Key SaaS game theory situations include: pricing wars (dropping prices to compete, with the risk of a race to the bottom), feature parity battles (copying competitor features in an endless escalation), and platform ecosystem dynamics (cooperating with a platform that might become a competitor). Understanding Nash equilibria helps SaaS operators predict stable competitive outcomes and avoid destructive strategies." + saas_context: "SaaS markets are repeated games with observable moves — every + product launch, pricing change, and funding announcement is visible to + competitors. This makes game theory directly applicable. Key SaaS game + theory situations include: pricing wars (dropping prices to compete, with + the risk of a race to the bottom), feature parity battles (copying + competitor features in an endless escalation), and platform ecosystem + dynamics (cooperating with a platform that might become a competitor). + Understanding Nash equilibria helps SaaS operators predict stable + competitive outcomes and avoid destructive strategies." saas_anti_patterns: - - "Engaging in price wars with better-funded competitors. The well-funded player can sustain losses longer. Compete on differentiation, not on price." - - "Ignoring the repeated-game nature of SaaS competition. Aggressive moves (poaching employees, FUD campaigns, predatory pricing) invite retaliation in a market where companies interact repeatedly." - - "Treating partner-competitor dynamics as static. A company that is a partner today (e.g., a platform you build on) may become a competitor tomorrow. Game theory helps model these transitions." - saas_example: "Two SaaS companies compete in the same category. Company A considers dropping prices by 30% to gain market share. Game theory analysis reveals this is a negative-sum game: Company B will match the price cut (dominant strategy in a repeated game), both companies end up at lower margins, and neither gains share. Instead, Company A invests the margin they would have sacrificed into product differentiation (vertical features, better integrations), creating asymmetric value that Company B cannot match through price reduction alone." - benchmark_references: ["win-rate", "arpu", "gross-margin"] + - "Engaging in price wars with better-funded competitors. The well-funded + player can sustain losses longer. Compete on differentiation, not on + price." + - "Ignoring the repeated-game nature of SaaS competition. Aggressive moves + (poaching employees, FUD campaigns, predatory pricing) invite + retaliation in a market where companies interact repeatedly." + - "Treating partner-competitor dynamics as static. A company that is a + partner today (e.g., a platform you build on) may become a competitor + tomorrow. Game theory helps model these transitions." + saas_example: "Two SaaS companies compete in the same category. Company A + considers dropping prices by 30% to gain market share. Game theory + analysis reveals this is a negative-sum game: Company B will match the + price cut (dominant strategy in a repeated game), both companies end up at + lower margins, and neither gains share. Instead, Company A invests the + margin they would have sacrificed into product differentiation (vertical + features, better integrations), creating asymmetric value that Company B + cannot match through price reduction alone." + benchmark_references: [ "win-rate", "arpu", "gross-margin" ] - skill: "first-mover-strategy" category: "game-theory" saas_relevance: "high" - saas_context: "First-mover advantage in SaaS is real but often overstated. True first-mover advantages in SaaS come from: network effects (the product becomes more valuable with more users, making it hard to displace), data advantages (early users generate data that improves the product), integration lock-in (becoming the standard that other tools integrate with), and brand-category association (becoming the verb: 'Slack me,' 'Zoom call'). Many SaaS categories, however, are won by fast followers who learn from the first mover's mistakes: Slack followed HipChat, Zoom followed WebEx, Figma followed Sketch." + saas_context: "First-mover advantage in SaaS is real but often overstated. True + first-mover advantages in SaaS come from: network effects (the product + becomes more valuable with more users, making it hard to displace), data + advantages (early users generate data that improves the product), + integration lock-in (becoming the standard that other tools integrate + with), and brand-category association (becoming the verb: 'Slack me,' + 'Zoom call'). Many SaaS categories, however, are won by fast followers who + learn from the first mover's mistakes: Slack followed HipChat, Zoom + followed WebEx, Figma followed Sketch." saas_anti_patterns: - - "Assuming first-mover status guarantees victory. In SaaS, the product is continuously improvable — a fast follower with better execution, more capital, or superior UX can overtake the pioneer." - - "Over-investing in speed-to-market at the expense of product quality. Launching a broken product first does not create an advantage — it creates negative word-of-mouth that the fast follower exploits." - - "Ignoring the fast-follower threat. First movers must invest in defensibility (data moats, network effects, integration ecosystems) or the advantage dissipates as the category matures." - saas_example: "Figma was not the first browser-based design tool — it entered years after Sketch had established dominance. Figma's fast-follower advantage: they observed that Sketch's file-based workflow was the key weakness and built collaboration as the core architecture from day one. Sketch could not retrofit real-time collaboration into a file-based product. The first mover's architecture became its constraint, and the fast follower's architecture became its moat." - benchmark_references: ["activation-rate", "nps-saas", "nrr"] + - "Assuming first-mover status guarantees victory. In SaaS, the product is + continuously improvable — a fast follower with better execution, more + capital, or superior UX can overtake the pioneer." + - "Over-investing in speed-to-market at the expense of product quality. + Launching a broken product first does not create an advantage — it + creates negative word-of-mouth that the fast follower exploits." + - "Ignoring the fast-follower threat. First movers must invest in + defensibility (data moats, network effects, integration ecosystems) or + the advantage dissipates as the category matures." + saas_example: "Figma was not the first browser-based design tool — it entered + years after Sketch had established dominance. Figma's fast-follower + advantage: they observed that Sketch's file-based workflow was the key + weakness and built collaboration as the core architecture from day one. + Sketch could not retrofit real-time collaboration into a file-based + product. The first mover's architecture became its constraint, and the + fast follower's architecture became its moat." + benchmark_references: [ "activation-rate", "nps-saas", "nrr" ] - skill: "prisoners-dilemma-and-cooperation" category: "game-theory" saas_relevance: "moderate" - saas_context: "The prisoner's dilemma appears frequently in SaaS in competitive pricing, platform relationships, and data sharing. Two SaaS companies competing for the same customer both have the incentive to discount aggressively (defect), but if both discount, both lose margin (mutual defection). The cooperative outcome (maintaining prices, competing on value) is better for both but unstable without mechanisms to enforce it. In platform relationships, the dilemma is more acute: a SaaS company shares data with a platform partner (cooperate) to improve the integration, but the platform could use that data to build a competing feature (defect)." + saas_context: "The prisoner's dilemma appears frequently in SaaS in competitive + pricing, platform relationships, and data sharing. Two SaaS companies + competing for the same customer both have the incentive to discount + aggressively (defect), but if both discount, both lose margin (mutual + defection). The cooperative outcome (maintaining prices, competing on + value) is better for both but unstable without mechanisms to enforce it. + In platform relationships, the dilemma is more acute: a SaaS company + shares data with a platform partner (cooperate) to improve the + integration, but the platform could use that data to build a competing + feature (defect)." saas_anti_patterns: - - "Cooperating indefinitely with a partner who repeatedly defects. If a platform partner keeps building features that compete with your product, continuing to invest in the integration is irrational." - - "Defecting preemptively out of fear. Refusing to integrate with platforms, share data with partners, or collaborate on standards out of fear of exploitation prevents the cooperative outcomes that drive SaaS ecosystem value." - saas_example: "A SaaS company builds on top of a major platform's API. The platform announces a native feature that partially overlaps with the SaaS company's product. This is a prisoner's dilemma: the SaaS company can (a) continue building on the platform and hope the native feature remains inferior, or (b) diversify to other platforms, reducing investment in the relationship. The optimal strategy from game theory: communicate directly with the platform, identify the non-overlapping use cases where the dedicated product is superior, and invest in depth of integration that makes the SaaS product complementary rather than competitive to the native feature." - benchmark_references: ["nrr", "win-rate"] + - "Cooperating indefinitely with a partner who repeatedly defects. If a + platform partner keeps building features that compete with your product, + continuing to invest in the integration is irrational." + - "Defecting preemptively out of fear. Refusing to integrate with + platforms, share data with partners, or collaborate on standards out of + fear of exploitation prevents the cooperative outcomes that drive SaaS + ecosystem value." + saas_example: "A SaaS company builds on top of a major platform's API. The + platform announces a native feature that partially overlaps with the SaaS + company's product. This is a prisoner's dilemma: the SaaS company can (a) + continue building on the platform and hope the native feature remains + inferior, or (b) diversify to other platforms, reducing investment in the + relationship. The optimal strategy from game theory: communicate directly + with the platform, identify the non-overlapping use cases where the + dedicated product is superior, and invest in depth of integration that + makes the SaaS product complementary rather than competitive to the native + feature." + benchmark_references: [ "nrr", "win-rate" ] # ───────────────────────────────────────────── # LEADERSHIP (5 skills) @@ -446,57 +1216,173 @@ skill_overlays: - skill: "delegation-and-empowerment" category: "leadership" saas_relevance: "high" - saas_context: "Delegation is the single biggest scaling bottleneck for SaaS founders. The transition from founder-does-everything to functional leadership is where most SaaS companies stall between $1M and $5M ARR. The challenge is SaaS-specific: founders built the product, sold the first customers, and configured the infrastructure — their deep context makes them faster than any hire in the short term. Effective delegation in SaaS requires building 'context transfer systems': documented processes, metric dashboards, decision frameworks, and explicit delegation of authority over specific functions with clear guardrails." + saas_context: "Delegation is the single biggest scaling bottleneck for SaaS + founders. The transition from founder-does-everything to functional + leadership is where most SaaS companies stall between $1M and $5M ARR. The + challenge is SaaS-specific: founders built the product, sold the first + customers, and configured the infrastructure — their deep context makes + them faster than any hire in the short term. Effective delegation in SaaS + requires building 'context transfer systems': documented processes, metric + dashboards, decision frameworks, and explicit delegation of authority over + specific functions with clear guardrails." saas_anti_patterns: - - "Delegating responsibility without authority. Hiring a VP Sales but requiring founder approval for every discount or contract term makes the VP ineffective and signals distrust." - - "Delegating execution but retaining all strategic decisions. SaaS functional leaders must own both strategy and execution in their domain to be effective." - - "Re-doing delegated work. If the founder rewrites every marketing email and redesigns every feature after delegation, the team stops investing effort — learned helplessness sets in." - saas_example: "A SaaS CEO at $3M ARR hires a VP Engineering but continues reviewing every pull request and attending every sprint planning meeting. The VP cannot establish authority, senior engineers go around the VP to the CEO for decisions, and the CEO is still working 80-hour weeks. The fix: the CEO defines three explicit 'delegation contracts' — the VP owns all technical architecture decisions, sprint planning, and engineering hiring. The CEO retains input on product roadmap priorities but not implementation decisions. Monthly 1:1s replace daily involvement." - benchmark_references: ["arr"] + - "Delegating responsibility without authority. Hiring a VP Sales but + requiring founder approval for every discount or contract term makes the + VP ineffective and signals distrust." + - "Delegating execution but retaining all strategic decisions. SaaS + functional leaders must own both strategy and execution in their domain + to be effective." + - "Re-doing delegated work. If the founder rewrites every marketing email + and redesigns every feature after delegation, the team stops investing + effort — learned helplessness sets in." + saas_example: "A SaaS CEO at $3M ARR hires a VP Engineering but continues + reviewing every pull request and attending every sprint planning meeting. + The VP cannot establish authority, senior engineers go around the VP to + the CEO for decisions, and the CEO is still working 80-hour weeks. The + fix: the CEO defines three explicit 'delegation contracts' — the VP owns + all technical architecture decisions, sprint planning, and engineering + hiring. The CEO retains input on product roadmap priorities but not + implementation decisions. Monthly 1:1s replace daily involvement." + benchmark_references: [ "arr" ] - skill: "decision-making-under-pressure" category: "leadership" saas_relevance: "high" - saas_context: "SaaS creates unique pressure situations: infrastructure outages affecting thousands of customers simultaneously, competitor launches that require rapid strategic response, fundraising timelines that force decisions with incomplete information, and key employee departures that leave critical functions uncovered. The subscription model amplifies pressure because revenue is earned continuously — every day of underperformance compounds. Decision-making under pressure in SaaS must account for the amplification effect of public dashboards, real-time metrics, and social media where customers can broadcast frustration instantly." + saas_context: "SaaS creates unique pressure situations: infrastructure outages + affecting thousands of customers simultaneously, competitor launches that + require rapid strategic response, fundraising timelines that force + decisions with incomplete information, and key employee departures that + leave critical functions uncovered. The subscription model amplifies + pressure because revenue is earned continuously — every day of + underperformance compounds. Decision-making under pressure in SaaS must + account for the amplification effect of public dashboards, real-time + metrics, and social media where customers can broadcast frustration + instantly." saas_anti_patterns: - - "Making strategic decisions during tactical crises. When the product is down, the correct decision is to fix it — not to have a strategic discussion about architecture. Separate crisis response from strategic response." - - "Using pressure as an excuse for poor process. 'We had to move fast' does not justify skipping customer communication, security review, or team alignment." - - "Allowing pressure to create a permanent state of urgency. SaaS companies that operate in constant crisis mode burn out their teams and make increasingly poor decisions." - saas_example: "A SaaS company's primary database goes down during a major customer's compliance audit. The CEO faces simultaneous decisions: (1) Technical: restore from backup vs. rebuild from replica (2) Customer: how to communicate with the affected customer (3) Business: whether to offer a credit or contract extension (4) Strategic: whether this incident reveals a systemic reliability problem requiring major infrastructure investment. Under pressure, the CEO sequences these correctly: technical fix first, customer communication within 30 minutes, business discussion after stability, and strategic discussion in the following week's executive meeting." - benchmark_references: ["nps-saas", "logo-churn"] + - "Making strategic decisions during tactical crises. When the product is + down, the correct decision is to fix it — not to have a strategic + discussion about architecture. Separate crisis response from strategic + response." + - "Using pressure as an excuse for poor process. 'We had to move fast' + does not justify skipping customer communication, security review, or + team alignment." + - "Allowing pressure to create a permanent state of urgency. SaaS + companies that operate in constant crisis mode burn out their teams and + make increasingly poor decisions." + saas_example: "A SaaS company's primary database goes down during a major + customer's compliance audit. The CEO faces simultaneous decisions: (1) + Technical: restore from backup vs. rebuild from replica (2) Customer: how + to communicate with the affected customer (3) Business: whether to offer a + credit or contract extension (4) Strategic: whether this incident reveals + a systemic reliability problem requiring major infrastructure investment. + Under pressure, the CEO sequences these correctly: technical fix first, + customer communication within 30 minutes, business discussion after + stability, and strategic discussion in the following week's executive + meeting." + benchmark_references: [ "nps-saas", "logo-churn" ] - skill: "employee-engagement-retention" category: "leadership" saas_relevance: "high" - saas_context: "SaaS companies compete for talent in one of the most competitive labor markets. Engineering, product management, and sales talent have abundant options, and the cost of attrition in SaaS is exceptionally high — a departing senior engineer takes 3-6 months of institutional knowledge and productivity, and a departing sales rep takes pipeline relationships and customer context. Engagement in SaaS is driven by: product quality (engineers want to work on well-architected systems), growth trajectory (employees want equity upside), learning opportunities (the talent market values skill development), autonomy (top SaaS talent resists micromanagement), and mission alignment (why this product matters)." + saas_context: "SaaS companies compete for talent in one of the most competitive + labor markets. Engineering, product management, and sales talent have + abundant options, and the cost of attrition in SaaS is exceptionally high + — a departing senior engineer takes 3-6 months of institutional knowledge + and productivity, and a departing sales rep takes pipeline relationships + and customer context. Engagement in SaaS is driven by: product quality + (engineers want to work on well-architected systems), growth trajectory + (employees want equity upside), learning opportunities (the talent market + values skill development), autonomy (top SaaS talent resists + micromanagement), and mission alignment (why this product matters)." saas_anti_patterns: - - "Using equity as a substitute for culture. Stock options attract talent but do not retain it if the daily work environment is toxic, the product vision is unclear, or management is incompetent." - - "Measuring engagement through annual surveys instead of continuous signals. In SaaS, Slack activity, PR velocity, meeting attendance patterns, and 1:1 sentiment are real-time engagement indicators." - - "Treating all attrition as bad. Some attrition in SaaS is healthy — underperformers, culture mismatches, and employees who have outgrown their roles. Regrettable attrition (top performers leaving voluntarily) is the metric that matters." - saas_example: "A SaaS company's engineering team has 35% annual attrition. Exit interviews reveal the primary driver is not compensation but technical debt — engineers spend 60% of their time on maintenance rather than building new features. The company implements a '70/30 rule': 70% of engineering capacity on new features and improvements, 30% on tech debt reduction, with progress visible in a public dashboard. Attrition drops to 15% within two quarters because engineers see that leadership takes product quality seriously." - benchmark_references: ["gross-margin", "arr"] + - "Using equity as a substitute for culture. Stock options attract talent + but do not retain it if the daily work environment is toxic, the product + vision is unclear, or management is incompetent." + - "Measuring engagement through annual surveys instead of continuous + signals. In SaaS, Slack activity, PR velocity, meeting attendance + patterns, and 1:1 sentiment are real-time engagement indicators." + - "Treating all attrition as bad. Some attrition in SaaS is healthy — + underperformers, culture mismatches, and employees who have outgrown + their roles. Regrettable attrition (top performers leaving voluntarily) + is the metric that matters." + saas_example: "A SaaS company's engineering team has 35% annual attrition. Exit + interviews reveal the primary driver is not compensation but technical + debt — engineers spend 60% of their time on maintenance rather than + building new features. The company implements a '70/30 rule': 70% of + engineering capacity on new features and improvements, 30% on tech debt + reduction, with progress visible in a public dashboard. Attrition drops to + 15% within two quarters because engineers see that leadership takes + product quality seriously." + benchmark_references: [ "gross-margin", "arr" ] - skill: "leading-through-change" category: "leadership" saas_relevance: "high" - saas_context: "SaaS companies undergo frequent, substantial change: pivots, pricing restructures, organizational redesigns, go-to-market transitions, and replatforming efforts. The pace is faster than traditional industries because the subscription model provides rapid feedback. Leading through change in SaaS requires specific capabilities: communicating 'why' when the data-driven reason may be complex (e.g., 'we are restructuring pricing because our expansion revenue model is broken'), managing the anxiety of teams whose work may become obsolete, and maintaining customer trust during transitions that affect their experience." + saas_context: "SaaS companies undergo frequent, substantial change: pivots, + pricing restructures, organizational redesigns, go-to-market transitions, + and replatforming efforts. The pace is faster than traditional industries + because the subscription model provides rapid feedback. Leading through + change in SaaS requires specific capabilities: communicating 'why' when + the data-driven reason may be complex (e.g., 'we are restructuring pricing + because our expansion revenue model is broken'), managing the anxiety of + teams whose work may become obsolete, and maintaining customer trust + during transitions that affect their experience." saas_anti_patterns: - - "Announcing major changes without preparation. A pricing restructure announced on Monday and implemented on Friday creates chaos with customers, sales, and support." - - "Changing too many things simultaneously. SaaS companies that restructure the team, change the pricing, and pivot the product simultaneously cannot determine what is working." - - "Under-communicating during change. SaaS teams that hear about strategic changes through Slack rumors rather than direct leadership communication lose trust rapidly." - saas_example: "A SaaS company transitions from a sales-led to a product-led growth model. The change affects every function: product must build self-serve onboarding, engineering must instrument usage tracking, marketing must shift from lead-gen to product-qualified leads, and sales must evolve from outbound prospecting to expansion selling. The CEO leads through change by: (1) publishing a 6-page memo explaining the strategic rationale with data, (2) running team-specific workshops on what changes for each function, (3) defining a 90-day transition plan with weekly metrics check-ins, and (4) explicitly addressing the fear: 'No one is losing their job — roles are evolving, and we will invest in retraining.'" - benchmark_references: ["activation-rate", "cac", "expansion-revenue-pct"] + - "Announcing major changes without preparation. A pricing restructure + announced on Monday and implemented on Friday creates chaos with + customers, sales, and support." + - "Changing too many things simultaneously. SaaS companies that + restructure the team, change the pricing, and pivot the product + simultaneously cannot determine what is working." + - "Under-communicating during change. SaaS teams that hear about strategic + changes through Slack rumors rather than direct leadership communication + lose trust rapidly." + saas_example: "A SaaS company transitions from a sales-led to a product-led + growth model. The change affects every function: product must build + self-serve onboarding, engineering must instrument usage tracking, + marketing must shift from lead-gen to product-qualified leads, and sales + must evolve from outbound prospecting to expansion selling. The CEO leads + through change by: (1) publishing a 6-page memo explaining the strategic + rationale with data, (2) running team-specific workshops on what changes + for each function, (3) defining a 90-day transition plan with weekly + metrics check-ins, and (4) explicitly addressing the fear: 'No one is + losing their job — roles are evolving, and we will invest in retraining.'" + benchmark_references: [ "activation-rate", "cac", "expansion-revenue-pct" ] - skill: "strategic-thinking-and-alignment" category: "leadership" saas_relevance: "critical" - saas_context: "Strategic alignment in SaaS means ensuring that product roadmap, go-to-market motion, pricing model, customer success strategy, and organizational structure all point in the same direction. Misalignment is the most common cause of SaaS underperformance — the product serves SMB but sales targets enterprise, the pricing encourages monthly churn but the model assumes annual contracts, or customer success is measured on retention but has no influence over the product roadmap. Strategic thinking in SaaS requires holding the entire system in view and identifying the misalignments that create friction." + saas_context: "Strategic alignment in SaaS means ensuring that product roadmap, + go-to-market motion, pricing model, customer success strategy, and + organizational structure all point in the same direction. Misalignment is + the most common cause of SaaS underperformance — the product serves SMB + but sales targets enterprise, the pricing encourages monthly churn but the + model assumes annual contracts, or customer success is measured on + retention but has no influence over the product roadmap. Strategic + thinking in SaaS requires holding the entire system in view and + identifying the misalignments that create friction." saas_anti_patterns: - - "Defining strategy as 'grow revenue.' That is a goal, not a strategy. SaaS strategy must articulate where to compete (segments, geographies, use cases), how to win (differentiation, pricing, distribution), and what to deprioritize." - - "Aligning at the annual offsite and then drifting for 11 months. SaaS strategy requires monthly recalibration because feedback loops are fast and market conditions change rapidly." - - "Delegating strategic alignment to a strategy document. Alignment is maintained through persistent communication, metric alignment across teams, and regular cross-functional reviews — not through documents that no one reads." - saas_example: "A SaaS company's NRR is declining despite a strong NPS score. Strategic analysis reveals misalignment: the product team is building features for enterprise prospects (strategic initiative: 'move upmarket'), but the customer success team is compensated on logo retention (which is heavily SMB). Enterprise prospects see a product roadmap they like, but SMB customers see their needs deprioritized, leading to contraction and churn. The strategic fix: explicit segmentation with separate product roadmaps for SMB and enterprise, and realigning customer success compensation to include expansion revenue, not just retention." - benchmark_references: ["nrr", "grr", "expansion-revenue-pct", "logo-churn"] + - "Defining strategy as 'grow revenue.' That is a goal, not a strategy. + SaaS strategy must articulate where to compete (segments, geographies, + use cases), how to win (differentiation, pricing, distribution), and + what to deprioritize." + - "Aligning at the annual offsite and then drifting for 11 months. SaaS + strategy requires monthly recalibration because feedback loops are fast + and market conditions change rapidly." + - "Delegating strategic alignment to a strategy document. Alignment is + maintained through persistent communication, metric alignment across + teams, and regular cross-functional reviews — not through documents that + no one reads." + saas_example: "A SaaS company's NRR is declining despite a strong NPS score. + Strategic analysis reveals misalignment: the product team is building + features for enterprise prospects (strategic initiative: 'move upmarket'), + but the customer success team is compensated on logo retention (which is + heavily SMB). Enterprise prospects see a product roadmap they like, but + SMB customers see their needs deprioritized, leading to contraction and + churn. The strategic fix: explicit segmentation with separate product + roadmaps for SMB and enterprise, and realigning customer success + compensation to include expansion revenue, not just retention." + benchmark_references: [ "nrr", "grr", "expansion-revenue-pct", "logo-churn" ] # ───────────────────────────────────────────── # STORYTELLING (1 skill) @@ -505,13 +1391,37 @@ skill_overlays: - skill: "story-structure-and-arc" category: "storytelling" saas_relevance: "high" - saas_context: "Storytelling is a critical skill for SaaS founders in three contexts: fundraising (the pitch narrative), sales (customer case studies and product narratives), and team alignment (the company origin story and vision narrative). The classic story arc — status quo, disruption, struggle, transformation, new normal — maps directly to the SaaS pitch structure: the market has a problem (status quo), existing solutions fail (disruption), our early customers struggled with this (struggle), our product transformed their workflow (transformation), and here is what the future looks like at scale (new normal). Investors fund narratives as much as metrics — a founder who cannot tell a compelling story will not raise effectively regardless of their numbers." + saas_context: "Storytelling is a critical skill for SaaS founders in three + contexts: fundraising (the pitch narrative), sales (customer case studies + and product narratives), and team alignment (the company origin story and + vision narrative). The classic story arc — status quo, disruption, + struggle, transformation, new normal — maps directly to the SaaS pitch + structure: the market has a problem (status quo), existing solutions fail + (disruption), our early customers struggled with this (struggle), our + product transformed their workflow (transformation), and here is what the + future looks like at scale (new normal). Investors fund narratives as much + as metrics — a founder who cannot tell a compelling story will not raise + effectively regardless of their numbers." saas_anti_patterns: - - "Leading with product features instead of customer problems. The story must start with the protagonist's pain, not the solution's capabilities." - - "Telling a story that does not connect to the metrics. A compelling narrative that contradicts the unit economics or retention data will be dismantled by sophisticated investors." - - "Using the same story for every audience. The board wants a strategic narrative, the sales prospect wants a peer's success story, and the engineering team wants a technical vision narrative." - saas_example: "A SaaS founder structures their Series A pitch as a three-act story. Act 1: 'Every compliance team in fintech manually tracks 400+ regulatory changes per year. They use spreadsheets, email chains, and prayer.' Act 2: 'Our first 50 customers went from 40 hours/week of manual tracking to 2 hours/week. They caught 3 regulatory changes that would have resulted in fines totaling $2.1M.' Act 3: 'We have 50 customers, $1.5M ARR, 130% NRR, and a waiting list of 200 companies. With this round, we will build the compliance operating system for all of fintech.' The narrative arc makes the metrics memorable and the opportunity tangible." - benchmark_references: ["arr", "nrr"] + - "Leading with product features instead of customer problems. The story + must start with the protagonist's pain, not the solution's + capabilities." + - "Telling a story that does not connect to the metrics. A compelling + narrative that contradicts the unit economics or retention data will be + dismantled by sophisticated investors." + - "Using the same story for every audience. The board wants a strategic + narrative, the sales prospect wants a peer's success story, and the + engineering team wants a technical vision narrative." + saas_example: "A SaaS founder structures their Series A pitch as a three-act + story. Act 1: 'Every compliance team in fintech manually tracks 400+ + regulatory changes per year. They use spreadsheets, email chains, and + prayer.' Act 2: 'Our first 50 customers went from 40 hours/week of manual + tracking to 2 hours/week. They caught 3 regulatory changes that would have + resulted in fines totaling $2.1M.' Act 3: 'We have 50 customers, $1.5M + ARR, 130% NRR, and a waiting list of 200 companies. With this round, we + will build the compliance operating system for all of fintech.' The + narrative arc makes the metrics memorable and the opportunity tangible." + benchmark_references: [ "arr", "nrr" ] # ───────────────────────────────────────────── # WRITING (1 skill) @@ -520,13 +1430,38 @@ skill_overlays: - skill: "writing-effective-emails" category: "writing" saas_relevance: "high" - saas_context: "Email remains the primary communication channel for SaaS businesses across every function: investor updates, customer onboarding sequences, sales outreach, support communication, internal announcements, and partnership proposals. In SaaS, email effectiveness directly impacts conversion rates (sales outreach), retention (customer communication), and fundraising success (investor updates). The SaaS-specific dimension is that email often serves as the first touch in a relationship (cold outreach) and the ongoing thread of a long-term relationship (monthly investor updates, quarterly business reviews) — it must work at both extremes." + saas_context: "Email remains the primary communication channel for SaaS + businesses across every function: investor updates, customer onboarding + sequences, sales outreach, support communication, internal announcements, + and partnership proposals. In SaaS, email effectiveness directly impacts + conversion rates (sales outreach), retention (customer communication), and + fundraising success (investor updates). The SaaS-specific dimension is + that email often serves as the first touch in a relationship (cold + outreach) and the ongoing thread of a long-term relationship (monthly + investor updates, quarterly business reviews) — it must work at both + extremes." saas_anti_patterns: - - "Sending generic, template-obvious sales outreach. SaaS buyers receive dozens of cold emails daily. Personalization based on the prospect's specific context (tech stack, recent funding, job postings) is mandatory." - - "Writing investor updates that hide bad news. The best investor updates lead with what went wrong, what was learned, and how the company is responding. Investors who discover problems late lose trust permanently." - - "Over-engineering onboarding email sequences. SaaS companies that send 15 emails in the first 14 days create fatigue. Focus on the 3-4 emails that drive activation, not a comprehensive drip campaign." - saas_example: "A SaaS founder's monthly investor update follows a consistent structure: three metrics (MRR, NRR, cash remaining), one win, one challenge, one ask. The email takes 90 seconds to read. When the founder needs a warm introduction, they send a brief, specific request ('Can you introduce me to [Name] at [Company]? We have 3 customers in their space and I believe we can help them with [specific problem].') rather than a generic 'know anyone who might be interested?' The specificity of SaaS metric language makes email communication more precise and more actionable." - benchmark_references: ["mrr", "nrr", "cac"] + - "Sending generic, template-obvious sales outreach. SaaS buyers receive + dozens of cold emails daily. Personalization based on the prospect's + specific context (tech stack, recent funding, job postings) is + mandatory." + - "Writing investor updates that hide bad news. The best investor updates + lead with what went wrong, what was learned, and how the company is + responding. Investors who discover problems late lose trust + permanently." + - "Over-engineering onboarding email sequences. SaaS companies that send + 15 emails in the first 14 days create fatigue. Focus on the 3-4 emails + that drive activation, not a comprehensive drip campaign." + saas_example: "A SaaS founder's monthly investor update follows a consistent + structure: three metrics (MRR, NRR, cash remaining), one win, one + challenge, one ask. The email takes 90 seconds to read. When the founder + needs a warm introduction, they send a brief, specific request ('Can you + introduce me to [Name] at [Company]? We have 3 customers in their space + and I believe we can help them with [specific problem].') rather than a + generic 'know anyone who might be interested?' The specificity of SaaS + metric language makes email communication more precise and more + actionable." + benchmark_references: [ "mrr", "nrr", "cac" ] # ───────────────────────────────────────────── # AI LEADERSHIP (1 skill) @@ -535,10 +1470,36 @@ skill_overlays: - skill: "ai-vision-and-strategy" category: "ai-leadership" saas_relevance: "critical" - saas_context: "AI is the most significant strategic variable in SaaS since the cloud transition itself. Every SaaS company must develop an AI strategy along three dimensions: (1) AI-native product features — how AI enhances the core product (intelligent automation, predictive analytics, natural language interfaces), (2) AI-enabled operations — how AI improves internal efficiency (customer support bots, code generation, automated testing, churn prediction), and (3) AI competitive positioning — whether AI creates defensible advantage (proprietary models trained on customer data) or commoditizes the existing product (general-purpose AI tools replacing specialized SaaS). Failure to develop an AI strategy is now an existential risk for SaaS companies." + saas_context: "AI is the most significant strategic variable in SaaS since the + cloud transition itself. Every SaaS company must develop an AI strategy + along three dimensions: (1) AI-native product features — how AI enhances + the core product (intelligent automation, predictive analytics, natural + language interfaces), (2) AI-enabled operations — how AI improves internal + efficiency (customer support bots, code generation, automated testing, + churn prediction), and (3) AI competitive positioning — whether AI creates + defensible advantage (proprietary models trained on customer data) or + commoditizes the existing product (general-purpose AI tools replacing + specialized SaaS). Failure to develop an AI strategy is now an existential + risk for SaaS companies." saas_anti_patterns: - - "Adding 'AI-powered' as a marketing label without genuine AI capability. SaaS buyers are becoming sophisticated enough to distinguish real AI features from rule-based automation with an AI wrapper." - - "Building AI features that depend on third-party foundation models without a defensibility plan. If the differentiation is a prompt on top of GPT, the moat is zero." - - "Ignoring the AI threat from below. General-purpose AI tools (ChatGPT, Claude, Copilot) can now perform tasks that previously required specialized SaaS products. Every SaaS company must answer: 'What does our product do that a general AI tool cannot?'" - saas_example: "A SaaS company providing contract analysis for legal teams faces an AI strategy decision. Option A: integrate a foundation model to add AI-powered clause detection (quick to ship, no moat, competitors will copy in months). Option B: build a proprietary model trained on their customers' 500,000 contract dataset, creating a data flywheel where more usage improves accuracy. Option C: pivot from a software tool to an AI-powered service that delivers contract analysis outcomes, not just a software interface. The AI strategy framework helps evaluate these options against defensibility, time to market, customer value, and competitive dynamics." - benchmark_references: ["nrr", "activation-rate", "nps-saas"] + - "Adding 'AI-powered' as a marketing label without genuine AI capability. + SaaS buyers are becoming sophisticated enough to distinguish real AI + features from rule-based automation with an AI wrapper." + - "Building AI features that depend on third-party foundation models + without a defensibility plan. If the differentiation is a prompt on top + of GPT, the moat is zero." + - "Ignoring the AI threat from below. General-purpose AI tools (ChatGPT, + Claude, Copilot) can now perform tasks that previously required + specialized SaaS products. Every SaaS company must answer: 'What does + our product do that a general AI tool cannot?'" + saas_example: "A SaaS company providing contract analysis for legal teams faces + an AI strategy decision. Option A: integrate a foundation model to add + AI-powered clause detection (quick to ship, no moat, competitors will copy + in months). Option B: build a proprietary model trained on their + customers' 500,000 contract dataset, creating a data flywheel where more + usage improves accuracy. Option C: pivot from a software tool to an + AI-powered service that delivers contract analysis outcomes, not just a + software interface. The AI strategy framework helps evaluate these options + against defensibility, time to market, customer value, and competitive + dynamics." + benchmark_references: [ "nrr", "activation-rate", "nps-saas" ] diff --git a/.claude/memory/_schema/memory-schema.md b/.claude/memory/_schema/memory-schema.md index ad906ea..9396d56 100644 --- a/.claude/memory/_schema/memory-schema.md +++ b/.claude/memory/_schema/memory-schema.md @@ -5,6 +5,8 @@ version: "1.0.0" author: "Fatih Guner" --- +> Runtime note: These layers describe conceptual and legacy memory. Current writes use the versioned state and migration protocol in `.claude/RUNTIME.md`. Do not create a second active store. + # Memory Schema The memory system maintains entrepreneur context across sessions through five layers, each operating at a different temporal frequency. Together they enable the system to behave less like a stateless tool and more like a mentor who remembers. diff --git a/.claude/memory/_template/identity-template.yaml b/.claude/memory/_template/identity-template.yaml index fb51279..138294e 100644 --- a/.claude/memory/_template/identity-template.yaml +++ b/.claude/memory/_template/identity-template.yaml @@ -4,6 +4,9 @@ # Purpose: Personalizes tone, complexity, and framing identity: + mode: "standard" # standard | solo + stoic_mode: false + language: "en" name: "" role: "" # Founder & CEO, CTO, COO, etc. background: "" # Technical, business, design, finance, etc. diff --git a/.claude/org-politics/organizational-alignment-playbook.md b/.claude/org-politics/organizational-alignment-playbook.md index 20922ff..a479b2f 100644 --- a/.claude/org-politics/organizational-alignment-playbook.md +++ b/.claude/org-politics/organizational-alignment-playbook.md @@ -1,6 +1,13 @@ --- name: "organizational-alignment-playbook" -description: "Structures the complete process of building stakeholder alignment for a strategic initiative. Chains stakeholder mapping, resistance diagnosis, coalition design, influence strategy, communication planning, and implementation into a rigorous sequence with checkpoints and a critical decision point. Use when an entrepreneur must secure organizational support for a significant change -- a pivot, a new hire, a budget reallocation, a strategic partnership, or any initiative requiring multiple stakeholders to say yes." +description: "Structures the complete process of building stakeholder alignment + for a strategic initiative. Chains stakeholder mapping, resistance diagnosis, + coalition design, influence strategy, communication planning, and + implementation into a rigorous sequence with checkpoints and a critical + decision point. Use when an entrepreneur must secure organizational support + for a significant change -- a pivot, a new hire, a budget reallocation, a + strategic partnership, or any initiative requiring multiple stakeholders to + say yes." version: "1.0.0" category: "playbooks" complexity: "intermediate" @@ -15,22 +22,29 @@ trigger_diagnostics: steps: - skill: "coalition-and-partnership-games" purpose: "Map every stakeholder using the Power-Interest-Position framework" - output: "Stakeholder influence map with position, power, and interest per stakeholder" - - skill: "stakeholder-resistance-diagnosis" - purpose: "Diagnose root cause of resistance for each skeptic and blocker" - output: "Resistance diagnosis per stakeholder with root cause and engagement recommendation" + output: "Stakeholder influence map with position, power, and interest per + stakeholder" + - purpose: "Diagnose root cause of resistance for each skeptic and blocker" + output: "Resistance diagnosis per stakeholder with root cause and engagement + recommendation" + kind: diagnostic + ref: stakeholder-resistance-diagnosis - skill: "coalition-and-partnership-games" purpose: "Design the coalition -- who to recruit, neutralize, or monitor" output: "Coalition building plan with targets, sequencing, and defection risk" - skill: "cialdini-influence" purpose: "Design tailored influence approach per stakeholder" - output: "Influence strategy per stakeholder with principles, tactics, and ethical guardrails" + output: "Influence strategy per stakeholder with principles, tactics, and + ethical guardrails" - skill: "persuasion-and-influence" - purpose: "Design the communication plan -- what to say, when, to whom, through which channel" + purpose: "Design the communication plan -- what to say, when, to whom, through + which channel" output: "Communication plan with messaging matrix, timing, and feedback loops" - - skill: "implementation-tracking" - purpose: "Execute with accountability -- track engagements, monitor position changes, adapt" + - purpose: "Execute with accountability -- track engagements, monitor position + changes, adapt" output: "Action plan with tracked items, milestones, and check-in protocol" + kind: implementation + ref: implementation-tracking final_outputs: - stakeholder-influence-map - resistance-management-plan diff --git a/.claude/org-politics/templates/_schema/org-politics-template.yaml b/.claude/org-politics/templates/_schema/org-politics-template.yaml index a7ac357..c809776 100644 --- a/.claude/org-politics/templates/_schema/org-politics-template.yaml +++ b/.claude/org-politics/templates/_schema/org-politics-template.yaml @@ -49,7 +49,7 @@ frontmatter: required: false description: "Playbooks that use this template as an output artifact." - author: "Fatih Guner" + author: type: string required: true description: "Template author." diff --git a/.claude/org-politics/templates/political-risk-assessment.md b/.claude/org-politics/templates/political-risk-assessment.md index 8dcda1c..6be2741 100644 --- a/.claude/org-politics/templates/political-risk-assessment.md +++ b/.claude/org-politics/templates/political-risk-assessment.md @@ -1,20 +1,27 @@ --- name: "political-risk-assessment" -description: "Produces a risk assessment specifically for organisational and political risks -- not market or financial risks, but PEOPLE risks. Use when an initiative faces potential human-driven derailment: departures, coalition fractures, information leaks, revolts, or stakeholder withdrawal. This is an internal strategy document -- never shared with the stakeholders it describes." +description: "Produces a risk assessment specifically for organisational and + political risks -- not market or financial risks, but PEOPLE risks. Use when + an initiative faces potential human-driven derailment: departures, coalition + fractures, information leaks, revolts, or stakeholder withdrawal. This is an + internal strategy document -- never shared with the stakeholders it + describes." audience: "self" political_context: "resistance-management" applicable_skills: - scenario-planning - black-swans - - risk-assessment-brief - thomas-kilmann-conflict applicable_diagnostics: - stakeholder-resistance-diagnosis - power-dynamics-diagnosis feeds_into_playbooks: - - organizational-alignment-playbook # After Step 2 + - organizational-alignment-playbook # After Step 2 format: "register" author: "Fatih Guner" +related_content: + - kind: template + ref: risk-assessment-brief --- # Political Risk Assessment diff --git a/.claude/output-templates/client/project-status-update.md b/.claude/output-templates/client/project-status-update.md index c15de74..85a0b4e 100644 --- a/.claude/output-templates/client/project-status-update.md +++ b/.claude/output-templates/client/project-status-update.md @@ -1,15 +1,23 @@ --- name: "project-status-update" -description: "Produces a concise project status report for clients, partners, or internal stakeholders. Covers overall status (RAG rating), progress since last update, upcoming milestones, blockers and risks, decisions needed, and budget/timeline tracking. Designed to be completed in 15 minutes and read in 3. The operating principle: no surprises. A stakeholder who reads this report consistently should never be blindsided by a problem that was already known. Use weekly or biweekly for any active engagement." +description: "Produces a concise project status report for clients, partners, or + internal stakeholders. Covers overall status (RAG rating), progress since last + update, upcoming milestones, blockers and risks, decisions needed, and + budget/timeline tracking. Designed to be completed in 15 minutes and read in + 3. The operating principle: no surprises. A stakeholder who reads this report + consistently should never be blindsided by a problem that was already known. + Use weekly or biweekly for any active engagement." audience: "client" applicable_skills: - smart-goals - writing-for-navigation - writing-for-response - - action-plan - balanced-scorecard format: "status-report" author: "Fatih Guner" +related_content: + - kind: template + ref: action-plan --- # Project Status Update diff --git a/.claude/playbooks/crisis-playbook.md b/.claude/playbooks/crisis-playbook.md index da3380a..0cd4e0b 100644 --- a/.claude/playbooks/crisis-playbook.md +++ b/.claude/playbooks/crisis-playbook.md @@ -1,22 +1,31 @@ --- name: "crisis-playbook" -description: "Used when a company faces acute crisis -- revenue collapse, team fractures, morale failure, or all three simultaneously. Chains financial diagnosis, team assessment, Stoic clarity, cognitive debiasing, and hard-decision frameworks into a compressed engagement designed for speed under pressure." +description: "Used when a company faces acute crisis -- revenue collapse, team + fractures, morale failure, or all three simultaneously. Chains financial + diagnosis, team assessment, Stoic clarity, cognitive debiasing, and + hard-decision frameworks into a compressed engagement designed for speed under + pressure." trigger_diagnostics: - revenue-diagnosis - team-dysfunction-diagnosis - leadership-crisis-diagnosis steps: - - skill: "revenue-diagnosis" - purpose: "Identify the financial root cause with diagnostic precision" + - purpose: "Identify the financial root cause with diagnostic precision" output: "Revenue failure analysis with causal tree and severity assessment" - - skill: "team-dysfunction-diagnosis" - purpose: "Assess team damage -- who is leaving, who has already checked out, where trust is broken" + kind: diagnostic + ref: revenue-diagnosis + - purpose: "Assess team damage -- who is leaving, who has already checked out, + where trust is broken" output: "Team health assessment with dysfunction categories and flight risk map" + kind: diagnostic + ref: team-dysfunction-diagnosis - skill: "stoic-control-and-clarity" - purpose: "Separate what the founder can control from what they cannot -- the first prerequisite for sound crisis decisions" + purpose: "Separate what the founder can control from what they cannot -- the + first prerequisite for sound crisis decisions" output: "Control/influence/accept matrix applied to the specific crisis" - skill: "enemies-of-clear-thinking" - purpose: "Identify which cognitive defaults -- emotion, ego, social pressure, inertia -- are distorting the founder's judgment" + purpose: "Identify which cognitive defaults -- emotion, ego, social pressure, + inertia -- are distorting the founder's judgment" output: "Default audit with specific safeguards for each identified trap" - skill: "tough-decision-situations" purpose: "Make the hard calls with structured frameworks for bad-option scenarios" diff --git a/.claude/playbooks/pivot-playbook.md b/.claude/playbooks/pivot-playbook.md index d33785e..c0328e7 100644 --- a/.claude/playbooks/pivot-playbook.md +++ b/.claude/playbooks/pivot-playbook.md @@ -1,16 +1,23 @@ --- name: "pivot-playbook" -description: "Used when a founder suspects the current direction has stalled and is weighing whether to pivot, what to pivot toward, and how to communicate the change. Chains diagnosis, strategic analysis, model redesign, scenario testing, decision-making, and narrative framing into a single engagement." +description: "Used when a founder suspects the current direction has stalled and + is weighing whether to pivot, what to pivot toward, and how to communicate the + change. Chains diagnosis, strategic analysis, model redesign, scenario + testing, decision-making, and narrative framing into a single engagement." trigger_diagnostics: - growth-stall-diagnosis - product-market-fit-diagnosis - decision-paralysis-diagnosis steps: - - skill: "product-market-fit-diagnosis" - purpose: "Validate whether product-market fit is genuinely broken or merely underperforming" - output: "PMF assessment with evidence: retention curves, activation rates, qualitative signal analysis" + - purpose: "Validate whether product-market fit is genuinely broken or merely + underperforming" + output: "PMF assessment with evidence: retention curves, activation rates, + qualitative signal analysis" + kind: diagnostic + ref: product-market-fit-diagnosis - skill: "swot-pest-analysis" - purpose: "Map the current position with brutal honesty before designing alternatives" + purpose: "Map the current position with brutal honesty before designing + alternatives" output: "SWOT matrix and PEST scan revealing structural vs. tactical weaknesses" - skill: "business-model-canvas" purpose: "Redesign the business model around validated assumptions" diff --git a/.claude/plugin-commands/abort.md b/.claude/plugin-commands/abort.md new file mode 100644 index 0000000..e129724 --- /dev/null +++ b/.claude/plugin-commands/abort.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /abort command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /abort + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/about.md b/.claude/plugin-commands/about.md new file mode 100644 index 0000000..b4b0ca3 --- /dev/null +++ b/.claude/plugin-commands/about.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /about command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /about + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /about with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/apply.md b/.claude/plugin-commands/apply.md new file mode 100644 index 0000000..b2188f1 --- /dev/null +++ b/.claude/plugin-commands/apply.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /apply command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /apply + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /apply with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/back.md b/.claude/plugin-commands/back.md new file mode 100644 index 0000000..2b72f40 --- /dev/null +++ b/.claude/plugin-commands/back.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /back command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /back + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /back with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/blockers.md b/.claude/plugin-commands/blockers.md new file mode 100644 index 0000000..973b241 --- /dev/null +++ b/.claude/plugin-commands/blockers.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /blockers command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /blockers + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /blockers with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/check-in.md b/.claude/plugin-commands/check-in.md new file mode 100644 index 0000000..fa733dc --- /dev/null +++ b/.claude/plugin-commands/check-in.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /check-in command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /check-in + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /check-in with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/coalition.md b/.claude/plugin-commands/coalition.md new file mode 100644 index 0000000..b04b479 --- /dev/null +++ b/.claude/plugin-commands/coalition.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /coalition command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /coalition + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /coalition with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/compare.md b/.claude/plugin-commands/compare.md new file mode 100644 index 0000000..73b14ab --- /dev/null +++ b/.claude/plugin-commands/compare.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /compare command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /compare + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /compare with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/decisions.md b/.claude/plugin-commands/decisions.md new file mode 100644 index 0000000..716060c --- /dev/null +++ b/.claude/plugin-commands/decisions.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /decisions command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /decisions + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /decisions with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/diagnose.md b/.claude/plugin-commands/diagnose.md new file mode 100644 index 0000000..23c9293 --- /dev/null +++ b/.claude/plugin-commands/diagnose.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /diagnose command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnose + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /diagnose with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +Before answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact. diff --git a/.claude/plugin-commands/diagnostics.md b/.claude/plugin-commands/diagnostics.md new file mode 100644 index 0000000..bd5eb3a --- /dev/null +++ b/.claude/plugin-commands/diagnostics.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /diagnostics command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnostics + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /diagnostics with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/export.md b/.claude/plugin-commands/export.md new file mode 100644 index 0000000..4169553 --- /dev/null +++ b/.claude/plugin-commands/export.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /export command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /export + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /export with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/feedback.md b/.claude/plugin-commands/feedback.md new file mode 100644 index 0000000..6169412 --- /dev/null +++ b/.claude/plugin-commands/feedback.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /feedback command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /feedback + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /feedback with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/follow-ups.md b/.claude/plugin-commands/follow-ups.md new file mode 100644 index 0000000..b6463ec --- /dev/null +++ b/.claude/plugin-commands/follow-ups.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /follow-ups command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /follow-ups + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /follow-ups with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-context.md b/.claude/plugin-commands/foreman-context.md new file mode 100644 index 0000000..c59b193 --- /dev/null +++ b/.claude/plugin-commands/foreman-context.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /context command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /context + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /context with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-help.md b/.claude/plugin-commands/foreman-help.md new file mode 100644 index 0000000..9b9eb8c --- /dev/null +++ b/.claude/plugin-commands/foreman-help.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /help command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /help + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /help with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-reset.md b/.claude/plugin-commands/foreman-reset.md new file mode 100644 index 0000000..7e9012c --- /dev/null +++ b/.claude/plugin-commands/foreman-reset.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /reset command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /reset + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /reset with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-resume.md b/.claude/plugin-commands/foreman-resume.md new file mode 100644 index 0000000..a086051 --- /dev/null +++ b/.claude/plugin-commands/foreman-resume.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resume command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resume + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /resume with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-run.md b/.claude/plugin-commands/foreman-run.md new file mode 100644 index 0000000..3c45394 --- /dev/null +++ b/.claude/plugin-commands/foreman-run.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /run command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /run + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /run with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-skill.md b/.claude/plugin-commands/foreman-skill.md new file mode 100644 index 0000000..2e46c07 --- /dev/null +++ b/.claude/plugin-commands/foreman-skill.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skill command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skill + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /skill with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/foreman-status.md b/.claude/plugin-commands/foreman-status.md new file mode 100644 index 0000000..51fb64b --- /dev/null +++ b/.claude/plugin-commands/foreman-status.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /status command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /status + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /status with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/forget.md b/.claude/plugin-commands/forget.md new file mode 100644 index 0000000..b607c2b --- /dev/null +++ b/.claude/plugin-commands/forget.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /forget command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /forget + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /forget with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/format.md b/.claude/plugin-commands/format.md new file mode 100644 index 0000000..c42a169 --- /dev/null +++ b/.claude/plugin-commands/format.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /format command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /format + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /format with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/history.md b/.claude/plugin-commands/history.md new file mode 100644 index 0000000..e33a026 --- /dev/null +++ b/.claude/plugin-commands/history.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /history command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /history + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /history with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/hooks.md b/.claude/plugin-commands/hooks.md new file mode 100644 index 0000000..147c988 --- /dev/null +++ b/.claude/plugin-commands/hooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /hooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /hooks + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /hooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/language.md b/.claude/plugin-commands/language.md new file mode 100644 index 0000000..ee30ced --- /dev/null +++ b/.claude/plugin-commands/language.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /language command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /language + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/language-command.md and execute only /language with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/plugin-commands/output.md b/.claude/plugin-commands/output.md new file mode 100644 index 0000000..86d35b0 --- /dev/null +++ b/.claude/plugin-commands/output.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /output command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /output + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /output with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/pause.md b/.claude/plugin-commands/pause.md new file mode 100644 index 0000000..4ca959d --- /dev/null +++ b/.claude/plugin-commands/pause.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /pause command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /pause + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /pause with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/playbooks.md b/.claude/plugin-commands/playbooks.md new file mode 100644 index 0000000..18ea3c3 --- /dev/null +++ b/.claude/plugin-commands/playbooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /playbooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /playbooks + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /playbooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/power-map.md b/.claude/plugin-commands/power-map.md new file mode 100644 index 0000000..38f86a4 --- /dev/null +++ b/.claude/plugin-commands/power-map.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /power-map command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /power-map + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /power-map with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/progress.md b/.claude/plugin-commands/progress.md new file mode 100644 index 0000000..a127e2a --- /dev/null +++ b/.claude/plugin-commands/progress.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /progress command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /progress + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /progress with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/research.md b/.claude/plugin-commands/research.md new file mode 100644 index 0000000..c7e7dd6 --- /dev/null +++ b/.claude/plugin-commands/research.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /research command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /research + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/research-commands.md and execute only /research with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/resistance.md b/.claude/plugin-commands/resistance.md new file mode 100644 index 0000000..84a2037 --- /dev/null +++ b/.claude/plugin-commands/resistance.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resistance command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resistance + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /resistance with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/search.md b/.claude/plugin-commands/search.md new file mode 100644 index 0000000..e0a71f2 --- /dev/null +++ b/.claude/plugin-commands/search.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /search command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /search + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /search with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/sector.md b/.claude/plugin-commands/sector.md new file mode 100644 index 0000000..fba467c --- /dev/null +++ b/.claude/plugin-commands/sector.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /sector command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /sector + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /sector with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/simulate.md b/.claude/plugin-commands/simulate.md new file mode 100644 index 0000000..a7f9342 --- /dev/null +++ b/.claude/plugin-commands/simulate.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /simulate command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /simulate + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/simulation-commands.md and execute only /simulate with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/skills.md b/.claude/plugin-commands/skills.md new file mode 100644 index 0000000..fba111f --- /dev/null +++ b/.claude/plugin-commands/skills.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skills command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skills + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /skills with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/skip.md b/.claude/plugin-commands/skip.md new file mode 100644 index 0000000..b08e73f --- /dev/null +++ b/.claude/plugin-commands/skip.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skip command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skip + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /skip with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/solo.md b/.claude/plugin-commands/solo.md new file mode 100644 index 0000000..4cfe328 --- /dev/null +++ b/.claude/plugin-commands/solo.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /solo command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /solo + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/solo-command.md and execute only /solo with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/plugin-commands/stage.md b/.claude/plugin-commands/stage.md new file mode 100644 index 0000000..5d836f2 --- /dev/null +++ b/.claude/plugin-commands/stage.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stage command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stage + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/stakeholders.md b/.claude/plugin-commands/stakeholders.md new file mode 100644 index 0000000..41a015d --- /dev/null +++ b/.claude/plugin-commands/stakeholders.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stakeholders command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stakeholders + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /stakeholders with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/stoic.md b/.claude/plugin-commands/stoic.md new file mode 100644 index 0000000..6246c8f --- /dev/null +++ b/.claude/plugin-commands/stoic.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /stoic command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stoic + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/stoic-command.md and execute only /stoic with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/.claude/plugin-commands/templates.md b/.claude/plugin-commands/templates.md new file mode 100644 index 0000000..46ad057 --- /dev/null +++ b/.claude/plugin-commands/templates.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /templates command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /templates + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /templates with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/track.md b/.claude/plugin-commands/track.md new file mode 100644 index 0000000..b473521 --- /dev/null +++ b/.claude/plugin-commands/track.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /track command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /track + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /track with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/update.md b/.claude/plugin-commands/update.md new file mode 100644 index 0000000..aa2ffb9 --- /dev/null +++ b/.claude/plugin-commands/update.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /update command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /update + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /update with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/plugin-commands/version.md b/.claude/plugin-commands/version.md new file mode 100644 index 0000000..4d49ef2 --- /dev/null +++ b/.claude/plugin-commands/version.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /version command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /version + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /version with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/.claude/policies/advisory.md b/.claude/policies/advisory.md new file mode 100644 index 0000000..af96c11 --- /dev/null +++ b/.claude/policies/advisory.md @@ -0,0 +1,19 @@ +# Advisory rules + +Apply these rules before any diagnostic, framework, playbook or simulation. + +For an initial advisory answer, distinguish the facts supplied by the founder from open hypotheses, ask the question that would most change the next decision, and offer one bounded action with a review point. Keep the whole response in the requested language, including the preamble. Before sending, remove every unsupported causal claim, invented target and unmeasured promise of saved time. + +- Separate observed facts, hypotheses and recommendations. Name missing measurements. A symptom alone is not a confirmed root cause. +- New customers still arriving does not rule out an acquisition problem. Compare acquisition volume and quality, conversion, retention, expansion and pricing over the same period before attributing flat or falling revenue. +- Ask a small number of questions that would change the next decision. Start with the most consequential unknown; do not require a full questionnaire before helping. +- Give actions with a rationale, assumptions, an owner, a measurable outcome and a review point. Present numerical examples as illustrative unless they come from the user's verified data. +- Match fundraising evidence to the funding stage. Do not require mature revenue or unit economics for every founder seeking capital. +- Assess reversibility from actual commitments and dependencies. Do not dismiss a founder's concern as irrational or prescribe a fixed multi-month experiment without checking capacity and runway. +- When a formula is needed, preserve all its components and define the period. The revenue bridge includes expansion as well as new revenue, contraction and churn. +- Before recommending that a founder stop advertising, freeze product work, change prices or cut staff, establish the relevant constraints, cash runway, dependencies and evidence. Prefer a bounded reversible experiment when uncertainty is high. +- Solo mode uses the founder's actual capacity and resources. Do not invent a team, board, investor mandate or delegation capacity. Stoic mode adds perspective without overriding evidence or the user's priorities. +- Use the saved output language for both questions and recommendations. Keep catalog identifiers unchanged. +- Recommend commands and content that exist in the supplied catalog. Treat examples in source documents as illustrations, not evidence that tools ran or state was saved. +- Read actual saved state before claiming recall or progress. Confirm a write only after the runtime succeeds. If persistence is unavailable, say the preference applies to this conversation and do not claim it will survive a new session. +- In simulations, distinguish the fictional persona's challenge from factual conclusions about the business. Finish the requested rounds before scoring, unless the user asks to stop. diff --git a/.claude/research/brand-perception-research.md b/.claude/research/brand-perception-research.md index 9f81fcf..bdb2aa3 100644 --- a/.claude/research/brand-perception-research.md +++ b/.claude/research/brand-perception-research.md @@ -1,11 +1,13 @@ --- name: "brand-perception-research" -description: "Guides entrepreneurs through researching how their brand is perceived by customers, prospects, and the broader market. Covers awareness measurement, association mapping, competitive perception comparison, social listening, and gap analysis between desired and actual positioning." +description: "Guides entrepreneurs through researching how their brand is + perceived by customers, prospects, and the broader market. Covers awareness + measurement, association mapping, competitive perception comparison, social + listening, and gap analysis between desired and actual positioning." research_type: "customer" feeds_into_skills: - four-ps-marketing - blue-ocean-strategy - - personal-brand-playbook - tipping-point feeds_into_templates: - market-opportunity-summary @@ -17,6 +19,9 @@ data_sources: - G2 / Trustpilot - Glassdoor author: "Fatih Guner" +related_content: + - kind: playbook + ref: personal-brand-playbook --- # Brand Perception Research diff --git a/.claude/research/churn-analysis-guide.md b/.claude/research/churn-analysis-guide.md index f1d9f70..c377286 100644 --- a/.claude/research/churn-analysis-guide.md +++ b/.claude/research/churn-analysis-guide.md @@ -1,13 +1,12 @@ --- name: "churn-analysis-guide" -description: "Guides entrepreneurs through researching and diagnosing customer churn — calculating accurate churn metrics, building cohort retention curves, running exit surveys, correlating usage data with attrition, and synthesizing findings into actionable churn drivers." +description: "Guides entrepreneurs through researching and diagnosing customer + churn — calculating accurate churn metrics, building cohort retention curves, + running exit surveys, correlating usage data with attrition, and synthesizing + findings into actionable churn drivers." research_type: "customer" feeds_into_skills: - - customer-churn-diagnosis - net-promoter-score - - revenue-diagnosis - - pricing-strategy-playbook - - unit-economics-snapshot feeds_into_templates: - unit-economics-snapshot estimated_time: "8-16 hours" @@ -21,6 +20,15 @@ data_sources: - Intercom - Delighted author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: customer-churn-diagnosis + - kind: diagnostic + ref: revenue-diagnosis + - kind: playbook + ref: pricing-strategy-playbook + - kind: template + ref: unit-economics-snapshot --- # Churn Analysis Guide diff --git a/.claude/research/content-strategy-research.md b/.claude/research/content-strategy-research.md index 38e50e0..cfbf340 100644 --- a/.claude/research/content-strategy-research.md +++ b/.claude/research/content-strategy-research.md @@ -1,11 +1,13 @@ --- name: "content-strategy-research" -description: "Guides entrepreneurs through researching content strategy — keyword and topic research, competitor content audits, channel selection, format testing, and measurement frameworks. Produces a data-informed 90-day content calendar and distribution plan." +description: "Guides entrepreneurs through researching content strategy — + keyword and topic research, competitor content audits, channel selection, + format testing, and measurement frameworks. Produces a data-informed 90-day + content calendar and distribution plan." research_type: "market" feeds_into_skills: - four-ps-marketing - tipping-point - - personal-brand-playbook - storytelling-for-leaders feeds_into_templates: - market-opportunity-summary @@ -20,6 +22,9 @@ data_sources: - LinkedIn Analytics - Apple Podcasts author: "Fatih Guner" +related_content: + - kind: playbook + ref: personal-brand-playbook --- # Content Strategy Research diff --git a/.claude/research/customer-interview-guide.md b/.claude/research/customer-interview-guide.md index d7d0a64..69e87ef 100644 --- a/.claude/research/customer-interview-guide.md +++ b/.claude/research/customer-interview-guide.md @@ -1,15 +1,18 @@ --- name: "customer-interview-guide" -description: "Complete protocol for conducting customer and user research interviews — from recruiting participants through synthesizing patterns. Covers problem interviews, solution interviews, pricing interviews, and churn interviews with a bank of non-leading questions and structured note-taking templates." +description: "Complete protocol for conducting customer and user research + interviews — from recruiting participants through synthesizing patterns. + Covers problem interviews, solution interviews, pricing interviews, and churn + interviews with a bank of non-leading questions and structured note-taking + templates." research_type: "customer" feeds_into_skills: - business-model-canvas - net-promoter-score - - product-market-fit-diagnosis - four-ps-marketing feeds_into_templates: - - customer-discovery-summary - - product-requirements-brief + - market-opportunity-summary + - new-initiative-brief estimated_time: "10-20 hours" data_sources: - Direct interviews @@ -18,6 +21,9 @@ data_sources: - Online communities - Social media listening author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis --- # Customer Interview Guide diff --git a/.claude/research/due-diligence-research.md b/.claude/research/due-diligence-research.md index 94a18e2..0c7b532 100644 --- a/.claude/research/due-diligence-research.md +++ b/.claude/research/due-diligence-research.md @@ -1,12 +1,10 @@ --- name: "due-diligence-research" -description: "Pre-fundraising due diligence preparation protocol. Guides entrepreneurs through assembling the financial, legal, commercial, technical, and HR documentation that investors will request -- before they ask for it." +description: "Pre-fundraising due diligence preparation protocol. Guides + entrepreneurs through assembling the financial, legal, commercial, technical, + and HR documentation that investors will request -- before they ask for it." research_type: "financial" -feeds_into_skills: - - due-diligence-checklist - - fundraising-playbook - - fundraising-deck-outline - - unit-economics-snapshot +feeds_into_skills: [] feeds_into_templates: - due-diligence-checklist - fundraising-deck-outline @@ -21,6 +19,15 @@ data_sources: - ip-registry - cap-table-management-tools author: "Fatih Guner" +related_content: + - kind: template + ref: due-diligence-checklist + - kind: playbook + ref: fundraising-playbook + - kind: template + ref: fundraising-deck-outline + - kind: template + ref: unit-economics-snapshot --- # Due Diligence Research Guide diff --git a/.claude/research/financial-modeling-guide.md b/.claude/research/financial-modeling-guide.md index e5d95dc..2d5e385 100644 --- a/.claude/research/financial-modeling-guide.md +++ b/.claude/research/financial-modeling-guide.md @@ -1,10 +1,11 @@ --- name: "financial-modeling-guide" -description: "Guides entrepreneurs through gathering the inputs required to build a financial projection — revenue build-up, expense modeling, cash flow projection, break-even analysis, and scenario stress-testing. Produces the assumption set that drives a defensible financial model." +description: "Guides entrepreneurs through gathering the inputs required to + build a financial projection — revenue build-up, expense modeling, cash flow + projection, break-even analysis, and scenario stress-testing. Produces the + assumption set that drives a defensible financial model." research_type: "financial" -feeds_into_skills: - - unit-economics-snapshot - - exit-scenario-analysis +feeds_into_skills: [] feeds_into_templates: - fundraising-deck-outline - quarterly-strategic-review @@ -19,6 +20,11 @@ data_sources: - Bureau of Labor Statistics - PitchBook author: "Fatih Guner" +related_content: + - kind: template + ref: unit-economics-snapshot + - kind: template + ref: exit-scenario-analysis --- # Financial Modeling Guide diff --git a/.claude/research/funding-landscape-research.md b/.claude/research/funding-landscape-research.md index 58a4fc8..c689163 100644 --- a/.claude/research/funding-landscape-research.md +++ b/.claude/research/funding-landscape-research.md @@ -1,11 +1,12 @@ --- name: "funding-landscape-research" -description: "Guides entrepreneurs through mapping the funding landscape — identifying stage-appropriate capital sources, building targeted investor lists, researching partner-level thesis and portfolio fit, and constructing warm outreach sequences. Produces a prioritized investor pipeline and outreach plan." +description: "Guides entrepreneurs through mapping the funding landscape — + identifying stage-appropriate capital sources, building targeted investor + lists, researching partner-level thesis and portfolio fit, and constructing + warm outreach sequences. Produces a prioritized investor pipeline and outreach + plan." research_type: "financial" -feeds_into_skills: - - fundraising-playbook - - fundraising-deck-outline - - investor-update-email +feeds_into_skills: [] feeds_into_templates: - fundraising-deck-outline - investor-update-email @@ -20,6 +21,13 @@ data_sources: - grants.gov - SBIR.gov author: "Fatih Guner" +related_content: + - kind: playbook + ref: fundraising-playbook + - kind: template + ref: fundraising-deck-outline + - kind: template + ref: investor-update-email --- # Funding Landscape Research diff --git a/.claude/research/industry-mapping-guide.md b/.claude/research/industry-mapping-guide.md index 825366b..586ae04 100644 --- a/.claude/research/industry-mapping-guide.md +++ b/.claude/research/industry-mapping-guide.md @@ -1,14 +1,16 @@ --- name: "industry-mapping-guide" -description: "Structured protocol for mapping an industry landscape, including value chain analysis, ecosystem mapping, market segmentation, regulatory scanning, technology trend assessment, and distribution channel identification. Produces the foundational market intelligence that strategic frameworks require." +description: "Structured protocol for mapping an industry landscape, including + value chain analysis, ecosystem mapping, market segmentation, regulatory + scanning, technology trend assessment, and distribution channel + identification. Produces the foundational market intelligence that strategic + frameworks require." research_type: "market" feeds_into_skills: - porters-five-forces - swot-pest-analysis - scenario-planning - blue-ocean-strategy - - market-opportunity-summary - - strategic-analysis-one-pager feeds_into_templates: - market-opportunity-summary - strategic-analysis-one-pager @@ -23,6 +25,11 @@ data_sources: - regulatory-bodies - vc-investment-databases author: "Fatih Guner" +related_content: + - kind: template + ref: market-opportunity-summary + - kind: template + ref: strategic-analysis-one-pager --- # Industry Mapping Guide diff --git a/.claude/research/pricing-research-guide.md b/.claude/research/pricing-research-guide.md index 3f365db..c9a68ef 100644 --- a/.claude/research/pricing-research-guide.md +++ b/.claude/research/pricing-research-guide.md @@ -1,12 +1,12 @@ --- name: "pricing-research-guide" -description: "Structured research protocol for validating pricing assumptions through quantitative and qualitative methods. Covers Van Westendorp Price Sensitivity Meter, Gabor-Granger technique, competitor pricing analysis, willingness-to-pay interviews, and price elasticity estimation." +description: "Structured research protocol for validating pricing assumptions + through quantitative and qualitative methods. Covers Van Westendorp Price + Sensitivity Meter, Gabor-Granger technique, competitor pricing analysis, + willingness-to-pay interviews, and price elasticity estimation." research_type: "customer" feeds_into_skills: - four-ps-marketing - - pricing-diagnosis - - pricing-strategy-playbook - - unit-economics-snapshot feeds_into_templates: - unit-economics-snapshot - market-opportunity-summary @@ -18,6 +18,13 @@ data_sources: - survey-tools - pricing-page-analytics author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: pricing-diagnosis + - kind: playbook + ref: pricing-strategy-playbook + - kind: template + ref: unit-economics-snapshot --- # Pricing Research Guide diff --git a/.claude/research/survey-design-guide.md b/.claude/research/survey-design-guide.md index 8fc2a1c..ec635a2 100644 --- a/.claude/research/survey-design-guide.md +++ b/.claude/research/survey-design-guide.md @@ -1,11 +1,12 @@ --- name: "survey-design-guide" -description: "Guides entrepreneurs through designing, distributing, and analyzing surveys for quantitative customer research. Covers question design, sample sizing, bias prevention, and statistical interpretation. Complements the customer-interview-guide for qualitative depth." +description: "Guides entrepreneurs through designing, distributing, and + analyzing surveys for quantitative customer research. Covers question design, + sample sizing, bias prevention, and statistical interpretation. Complements + the customer-interview-guide for qualitative depth." research_type: "customer" feeds_into_skills: - net-promoter-score - - product-market-fit-diagnosis - - pricing-research-guide - four-ps-marketing feeds_into_templates: [] estimated_time: "6-10 hours" @@ -17,6 +18,11 @@ data_sources: - Pollfish - Prolific author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis + - kind: research + ref: pricing-research-guide --- # Survey Design Guide diff --git a/.claude/research/talent-market-research.md b/.claude/research/talent-market-research.md index fc31e32..b590c15 100644 --- a/.claude/research/talent-market-research.md +++ b/.claude/research/talent-market-research.md @@ -1,11 +1,11 @@ --- name: "talent-market-research" -description: "Guides entrepreneurs through researching the talent market before hiring — salary benchmarking, talent pool sizing, competitor hiring analysis, and employer brand assessment. Produces the intelligence needed to design competitive offers and realistic hiring timelines." +description: "Guides entrepreneurs through researching the talent market before + hiring — salary benchmarking, talent pool sizing, competitor hiring analysis, + and employer brand assessment. Produces the intelligence needed to design + competitive offers and realistic hiring timelines." research_type: "market" -feeds_into_skills: - - hiring-diagnosis - - team-rebuild-playbook - - hiring-scorecard +feeds_into_skills: [] feeds_into_templates: - role-description-template - ceo-succession-brief @@ -21,6 +21,13 @@ data_sources: - Blind - Wellfound author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: hiring-diagnosis + - kind: playbook + ref: team-rebuild-playbook + - kind: template + ref: hiring-scorecard --- # Talent Market Research diff --git a/.claude/research/user-testing-protocol.md b/.claude/research/user-testing-protocol.md index 17914e6..df20bd1 100644 --- a/.claude/research/user-testing-protocol.md +++ b/.claude/research/user-testing-protocol.md @@ -1,15 +1,14 @@ --- name: "user-testing-protocol" -description: "Comprehensive protocol for planning and executing user and usability testing. Covers moderated and unmoderated testing, task-based protocols, think-aloud method, A/B testing, prototype testing, and first-click testing with structured note-taking templates." +description: "Comprehensive protocol for planning and executing user and + usability testing. Covers moderated and unmoderated testing, task-based + protocols, think-aloud method, A/B testing, prototype testing, and first-click + testing with structured note-taking templates." research_type: "customer" feeds_into_skills: - net-promoter-score - - product-market-fit-diagnosis - - product-market-fit-playbook - - new-initiative-brief feeds_into_templates: - new-initiative-brief - - product-market-fit-diagnosis estimated_time: "10-20 hours" data_sources: - existing-users @@ -17,6 +16,15 @@ data_sources: - analytics-platforms - session-recording-tools author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis + - kind: playbook + ref: product-market-fit-playbook + - kind: template + ref: new-initiative-brief + - kind: diagnostic + ref: product-market-fit-diagnosis --- # User Testing Protocol diff --git a/.claude/runtime/package.json b/.claude/runtime/package.json new file mode 100644 index 0000000..f9ec9b6 --- /dev/null +++ b/.claude/runtime/package.json @@ -0,0 +1 @@ +{"type":"module","private":true} diff --git a/.claude/runtime/run.mjs b/.claude/runtime/run.mjs new file mode 100644 index 0000000..9dde771 --- /dev/null +++ b/.claude/runtime/run.mjs @@ -0,0 +1,4 @@ +#!/usr/bin/env node +import { runStateCLI } from './state-cli.js'; +try { console.log(JSON.stringify(runStateCLI(process.argv.slice(2)),null,2)); } +catch(e) { console.error(e.message); process.exitCode=1; } diff --git a/.claude/runtime/state-cli.js b/.claude/runtime/state-cli.js new file mode 100644 index 0000000..988f449 --- /dev/null +++ b/.claude/runtime/state-cli.js @@ -0,0 +1,39 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { changeState, readState, updateProfile, updateTask, track, migrateState, identifier } from './state.js'; + +export function runStateCLI(args) { + const [command,...rest] = args; + if (!command || command === '--help' || rest.includes('--help')) return {usage:'profile [--mode standard|solo] [--stoic on|off] [--language tr] [--sector saas]; task --id ID [--description TEXT] [--status STATE] [--progress 0..100] [--deadline YYYY-MM-DD] [--note TEXT]; track [--filter all|active|overdue|stalled|STATE]; resume [--playbook ID --step N]; migrate --input legacy.json. Common: --workspace DIR --founder ID --revision N'}; + const opts = {}; + for(let i=0;i changeState(workspace,founder,fn,{expectedRevision: opts.revision === undefined ? undefined : Number(opts.revision)}); + if (command === 'profile') { + const changes = {}; + for (const key of ['mode','language','sector']) if (opts[key] !== undefined) changes[key]=opts[key]; + if (opts.stoic !== undefined) { if (!['on','off'].includes(opts.stoic)) throw new Error('stoic must be on or off'); changes.stoic_mode=opts.stoic==='on'; } + return Object.keys(changes).length ? mutate(s=>updateProfile(s,changes)) : readState(workspace,founder); + } + if (command === 'task') { + const input = Object.fromEntries(allowed.filter(k => opts[k] !== undefined).map(k=>[k,opts[k]])); + if (input.progress !== undefined) input.progress=Number(input.progress); + if (input.deadline === 'none') input.deadline=null; + return mutate(s=>updateTask(s,input)); + } + if (command === 'track') return {items:track(readState(workspace,founder),opts.filter || 'all')}; + if (command === 'resume') { + if (opts.playbook !== undefined || opts.step !== undefined) return mutate(s=>{identifier(opts.playbook);s.active.playbook={id:opts.playbook,next_step:Number(opts.step)};return s;}); + return readState(workspace,founder).active.playbook; + } + if (!opts.input) throw new Error('migrate requires --input legacy.json'); + const legacy = JSON.parse(fs.readFileSync(path.resolve(opts.input),'utf8')); + return mutate(s=>{if (s.revision !== 0) throw new Error('Migration requires an unused founder destination');return migrateState(legacy,founder);}); +} diff --git a/.claude/runtime/state.js b/.claude/runtime/state.js new file mode 100644 index 0000000..5db5878 --- /dev/null +++ b/.claude/runtime/state.js @@ -0,0 +1,150 @@ +// Runtime state is deliberately dependency-free so every distribution uses it. +import fs from 'node:fs'; +import path from 'node:path'; +import { randomUUID } from 'node:crypto'; + +export const STATUSES = ['not-started','in-progress','blocked','completed','abandoned','deferred']; +export const SECTORS = ['saas','marketplace','e-commerce','fintech','ai-ml','healthtech','edtech','d2c-consumer','agency-consulting','']; +const LANGUAGES = { english:'en',default:'en',turkish:'tr','türkçe':'tr',spanish:'es',french:'fr',german:'de',japanese:'ja',chinese:'zh',portuguese:'pt',arabic:'ar',korean:'ko',italian:'it',russian:'ru',hindi:'hi',dutch:'nl' }; +export function language(value) { + if (typeof value !== 'string' || !value.trim() || value.length > 60 || /[\x00-\x1f]/.test(value)) throw new Error('Invalid language'); + const v = value.trim().toLowerCase(); + return LANGUAGES[v] || v; +} +export function identifier(id) { + if (typeof id !== 'string' || !/^[a-z0-9][a-z0-9_-]{0,79}$/i.test(id)) throw new Error('Invalid identifier'); + return id; +} +export function newState(founder = 'default', defaults = {}) { + identifier(founder); + return { schema_version:1, founder_id:founder, revision:0, + identity:{mode:defaults.defaultMode === 'solo' ? 'solo' : 'standard',stoic_mode:defaults.defaultMode === 'stoic',language:language(defaults.defaultLanguage || 'en')}, + company:{sector:defaults.sector || ''}, active:{playbook:null}, implementation_items:[], history:[] }; +} +function date(value) { + if (value === null) return true; + return typeof value === 'string' && /^\d{4}-\d{2}-\d{2}$/.test(value) && Number.isFinite(Date.parse(value)) && new Date(value).toISOString().slice(0,10) === value; +} +export function validateState(s) { + if (!s || s.schema_version !== 1) throw new Error('Unsupported state schema; migrate explicitly'); + identifier(s.founder_id); + if (!Number.isInteger(s.revision) || s.revision < 0) throw new Error('Invalid revision'); + if (!['standard','solo'].includes(s.identity?.mode) || typeof s.identity.stoic_mode !== 'boolean') throw new Error('Invalid operating mode'); + language(s.identity.language); + if (!s.company || !SECTORS.includes(s.company.sector)) throw new Error('Unknown sector'); + if (!s.active || !Array.isArray(s.implementation_items) || !Array.isArray(s.history)) throw new Error('Invalid state collections'); + if (s.active.playbook !== null) { + identifier(s.active.playbook?.id); + if (!Number.isInteger(s.active.playbook.next_step) || s.active.playbook.next_step < 1) throw new Error('Invalid playbook checkpoint'); + } + const ids = new Set(); + for (const item of s.implementation_items) { + identifier(item.id); + if (ids.has(item.id)) throw new Error(`Duplicate task: ${item.id}`); + ids.add(item.id); + if (typeof item.description !== 'string' || !item.description.trim()) throw new Error('Task description required'); + if (!STATUSES.includes(item.status) || !Number.isInteger(item.progress) || item.progress < 0 || item.progress > 100) throw new Error('Invalid task status or progress'); + if (item.status === 'completed' && item.progress !== 100) throw new Error('Completed tasks require 100% progress'); + if (item.status === 'not-started' && item.progress !== 0) throw new Error('Not-started tasks require 0% progress'); + if (!date(item.deadline) || !Array.isArray(item.notes) || !Array.isArray(item.state_history)) throw new Error('Invalid task deadline or history'); + } + return s; +} + +function statePath(workspace, founder, create = false) { + if (!workspace || !path.isAbsolute(workspace)) throw new Error('An absolute workspace directory is required for persistent state'); + identifier(founder); + let dir = workspace; + for (const part of ['.foreman',founder]) { + dir = path.join(dir,part); + if (fs.existsSync(dir) && fs.lstatSync(dir).isSymbolicLink()) throw new Error(`Linked state directory is not supported: ${dir}`); + if (create) fs.mkdirSync(dir,{recursive:true,mode:0o700}); + } + const file = path.join(dir,'state.json'); + try { if (fs.lstatSync(file).isSymbolicLink()) throw new Error('Linked state file is not supported'); } + catch(e) { if (e.code !== 'ENOENT') throw e; } + return file; +} +export function readState(workspace, founder = 'default', defaults = {}) { + const file = statePath(workspace,founder); + if (!fs.existsSync(file)) return validateState(newState(founder,defaults)); + const s = validateState(JSON.parse(fs.readFileSync(file,'utf8'))); + if (s.founder_id !== founder) throw new Error('State founder does not match selected founder'); + return s; +} +export function changeState(workspace, founder = 'default', mutate, { defaults = {}, expectedRevision } = {}) { + const file = statePath(workspace,founder,true), lock = file + '.lock'; + let fd; + try { fd = fs.openSync(lock,'wx',0o600); } + catch(e) { if (e.code === 'EEXIST') throw new Error('State is locked by another writer; retry after it finishes'); throw e; } + const tmp = `${file}.${randomUUID()}.tmp`; + try { + const state = readState(workspace,founder,defaults); + if (expectedRevision !== undefined && state.revision !== expectedRevision) throw new Error('State revision conflict; read the latest state before retrying'); + const draft = structuredClone(state); + const next = mutate(draft) || draft; + next.revision = state.revision + 1; + validateState(next); + if (next.founder_id !== founder) throw new Error('Cannot change founder identity'); + fs.writeFileSync(tmp,JSON.stringify(next,null,2)+'\n',{flag:'wx',mode:0o600}); + const sync = fs.openSync(tmp,'r'); try { fs.fsyncSync(sync); } finally { fs.closeSync(sync); } + fs.renameSync(tmp,file); + return next; + } finally { fs.closeSync(fd); fs.rmSync(lock,{force:true}); fs.rmSync(tmp,{force:true}); } +} +export function updateProfile(state, changes) { + for (const [key,value] of Object.entries(changes)) { + if (key === 'mode') state.identity.mode = value; + else if (key === 'stoic_mode') state.identity.stoic_mode = value; + else if (key === 'language') state.identity.language = language(value); + else if (key === 'sector') state.company.sector = value; + else throw new Error(`Unknown profile field: ${key}`); + } + return validateState(state); +} +export function updateTask(state, input, now = new Date()) { + identifier(input.id); + const allowed = ['id','description','owner','deadline','status','progress','note']; + for (const key of Object.keys(input)) if (!allowed.includes(key)) throw new Error(`Unknown task field: ${key}`); + let item = state.implementation_items.find(x => x.id === input.id); + if (!item) { + if (!input.description?.trim()) throw new Error('A new task requires a description'); + item = {id:input.id,description:input.description,owner:'self',deadline:null,status:'not-started',progress:0,notes:[],state_history:[],created:now.toISOString(),updated:now.toISOString()}; + state.implementation_items.push(item); + } + const previous = item.status; + for (const key of ['description','owner','deadline','status','progress']) if (input[key] !== undefined) item[key] = input[key]; + if (input.status === 'completed') item.progress = 100; + else if (input.status === 'not-started') item.progress = 0; + else if (input.progress !== undefined && input.status === undefined) item.status = input.progress === 100 ? 'completed' : input.progress > 0 ? 'in-progress' : 'not-started'; + if (input.note !== undefined) { + if (typeof input.note !== 'string' || !input.note.trim()) throw new Error('A note must be nonempty text'); + item.notes.push({date:now.toISOString(),note:input.note}); + } + if (previous !== item.status) item.state_history.push({from:previous,to:item.status,date:now.toISOString()}); + item.updated = now.toISOString(); + state.history.push({event:'task-updated',id:item.id,date:now.toISOString()}); + return validateState(state); +} +export function track(state, filter = 'all', now = new Date()) { + if (!['all','active','overdue','stalled',...STATUSES].includes(filter)) throw new Error(`Unknown tracking filter: ${filter}`); + const active = t => !['completed','abandoned'].includes(t.status); + return state.implementation_items.filter(t => filter === 'all' || (filter === 'active' ? active(t) : filter === 'overdue' ? active(t) && t.deadline && t.deadline < now.toISOString().slice(0,10) : filter === 'stalled' ? active(t) && now.getTime() - Date.parse(t.updated || t.created) >= 14*86400000 : t.status === filter)); +} +export function migrateState(legacy, founder = 'default') { + if (legacy.schema_version === 1) return validateState({...structuredClone(legacy),founder_id:founder}); + const s = newState(founder), identity = legacy.identity || {}, prefs = legacy.preferences || identity.preferences || {}; + s.identity = {...identity,mode:identity.mode || ((identity.mode_solo ?? prefs.solo_mode) ? 'solo' : 'standard'),stoic_mode:identity.stoic_mode ?? identity.mode_stoic ?? prefs.stoic_mode ?? false,language:language(identity.language || prefs.language || 'en')}; + if (s.identity.mode === 'stoic') { s.identity.mode='standard'; s.identity.stoic_mode=true; } + delete s.identity.mode_solo; delete s.identity.mode_stoic; delete s.identity.preferences; + s.company = {...legacy.company,sector:legacy.company?.sector || ''}; + s.active = {...legacy.active,playbook:legacy.active?.playbook || null}; + for (const old of legacy.implementation_items || legacy.active?.implementation_items || []) { + const status = old.status || 'not-started'; + const item = {...old,deadline:old.deadline || null,status,progress:old.progress ?? (status === 'completed' ? 100 : 0),notes:old.notes || [],state_history:old.state_history || []}; + s.implementation_items.push(item); + } + s.history = Array.isArray(legacy.history) ? legacy.history : []; + s.legacy = structuredClone(legacy); // Preserve source fields without using two active schemas. + return validateState(s); +} diff --git a/.claude/simulation/post-simulation-diagnostic.md b/.claude/simulation/post-simulation-diagnostic.md index 8427fa3..26a52dc 100644 --- a/.claude/simulation/post-simulation-diagnostic.md +++ b/.claude/simulation/post-simulation-diagnostic.md @@ -1,6 +1,10 @@ --- name: "post-simulation-diagnostic" -description: "Diagnostic that runs automatically after a board simulation to identify root causes of weak performance and route the entrepreneur to skills, research guides, and templates that address specific gaps. Unlike other diagnostics, the symptoms here are simulation scores, not entrepreneur-reported problems." +description: "Diagnostic that runs automatically after a board simulation to + identify root causes of weak performance and route the entrepreneur to skills, + research guides, and templates that address specific gaps. Unlike other + diagnostics, the symptoms here are simulation scores, not + entrepreneur-reported problems." entry_symptoms: - "Low clarity score in simulation" - "Weak evidence across claims" @@ -29,7 +33,6 @@ routes_to_templates: - fundraising-deck-outline - unit-economics-snapshot - competitive-landscape-brief - - quarterly-strategic-review author: "Fatih Guner" --- diff --git a/.claude/skills/creative/creative-collaboration-and-context.md b/.claude/skills/creative/creative-collaboration-and-context.md index 1f4f9f7..3189fae 100644 --- a/.claude/skills/creative/creative-collaboration-and-context.md +++ b/.claude/skills/creative/creative-collaboration-and-context.md @@ -1,6 +1,14 @@ --- name: "creative-collaboration-and-context" -description: "Explores how creative collaboration produces outcomes neither party could achieve alone, covering reference points without copying, the role of creative mythology, the prism of self as competitive advantage, context as meaning-maker, cross-domain adaptation, and translation as a creative act. Use when building creative partnerships, navigating co-founder dynamics, assembling creative teams, repositioning a product through context change, adapting business models across industries, translating technical innovation for new markets, or understanding why the same idea succeeds in one context and fails in another." +description: "Explores how creative collaboration produces outcomes neither + party could achieve alone, covering reference points without copying, the role + of creative mythology, the prism of self as competitive advantage, context as + meaning-maker, cross-domain adaptation, and translation as a creative act. Use + when building creative partnerships, navigating co-founder dynamics, + assembling creative teams, repositioning a product through context change, + adapting business models across industries, translating technical innovation + for new markets, or understanding why the same idea succeeds in one context + and fails in another." version: "1.0.0" category: "creative" complexity: "intermediate" @@ -23,8 +31,10 @@ related_skills: - creative-shaping-and-craft - creative-flow-and-inspiration - creative-completion-and-renewal - - stakeholder-mapping author: "Fatih Guner" +related_content: + - kind: template + ref: stakeholder-map --- # Collaboration and Context diff --git a/.claude/skills/frameworks/appreciative-inquiry.md b/.claude/skills/frameworks/appreciative-inquiry.md index 74ea3b2..1b02586 100644 --- a/.claude/skills/frameworks/appreciative-inquiry.md +++ b/.claude/skills/frameworks/appreciative-inquiry.md @@ -1,6 +1,12 @@ --- name: "appreciative-inquiry" -description: "Guides strengths-based organizational change using Cooperrider's Appreciative Inquiry 4D cycle: Discovery, Dream, Design, and Delivery. Surfaces peak experiences and positive patterns to amplify what works rather than fixing what is broken. Use when addressing team morale, redesigning processes, integrating acquisitions, reframing organizational challenges, or running culture transformation initiatives where traditional deficit-based problem-solving has stalled." +description: "Guides strengths-based organizational change using Cooperrider's + Appreciative Inquiry 4D cycle: Discovery, Dream, Design, and Delivery. + Surfaces peak experiences and positive patterns to amplify what works rather + than fixing what is broken. Use when addressing team morale, redesigning + processes, integrating acquisitions, reframing organizational challenges, or + running culture transformation initiatives where traditional deficit-based + problem-solving has stalled." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -16,8 +22,7 @@ tags: - innovation related_skills: - organisational-culture - - kaizen - - lean-canvas + - kaizen-bpr - grow-model author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/art-of-war.md b/.claude/skills/frameworks/art-of-war.md index cd6ac0e..36779c3 100644 --- a/.claude/skills/frameworks/art-of-war.md +++ b/.claude/skills/frameworks/art-of-war.md @@ -1,6 +1,12 @@ --- name: "art-of-war" -description: "Applies Sun Tzu's strategic principles to competitive business situations, covering self-knowledge and competitor intelligence, winning without direct confrontation, speed and timing, terrain analysis, and strategic positioning. Use when assessing competitive landscapes, developing market entry strategies, evaluating when to fight or avoid competitors, conducting competitive intelligence audits, or designing stealth positioning for startups facing well-resourced incumbents." +description: "Applies Sun Tzu's strategic principles to competitive business + situations, covering self-knowledge and competitor intelligence, winning + without direct confrontation, speed and timing, terrain analysis, and + strategic positioning. Use when assessing competitive landscapes, developing + market entry strategies, evaluating when to fight or avoid competitors, + conducting competitive intelligence audits, or designing stealth positioning + for startups facing well-resourced incumbents." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -19,7 +25,7 @@ related_skills: - porters-five-forces - blue-ocean-strategy - scenario-planning - - swot-analysis + - swot-pest-analysis author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/black-swans.md b/.claude/skills/frameworks/black-swans.md index 530c61e..be75f5f 100644 --- a/.claude/skills/frameworks/black-swans.md +++ b/.claude/skills/frameworks/black-swans.md @@ -1,6 +1,12 @@ --- name: "black-swans" -description: "Applies Taleb's Black Swan theory to assess and mitigate exposure to rare, high-impact unpredictable events. Distinguishes between Mediocristan and Extremistan domains, designs barbell strategies, builds antifragility, and audits business vulnerabilities including supply chain concentration, customer dependency, and regulatory risk. Use when stress-testing a business model, evaluating tail risks, designing resilience architecture, or building robust strategies that survive shocks rather than attempting to predict them." +description: "Applies Taleb's Black Swan theory to assess and mitigate exposure + to rare, high-impact unpredictable events. Distinguishes between Mediocristan + and Extremistan domains, designs barbell strategies, builds antifragility, and + audits business vulnerabilities including supply chain concentration, customer + dependency, and regulatory risk. Use when stress-testing a business model, + evaluating tail risks, designing resilience architecture, or building robust + strategies that survive shocks rather than attempting to predict them." version: "1.0.0" category: "frameworks" complexity: "advanced" @@ -18,7 +24,6 @@ related_skills: - scenario-planning - porters-five-forces - business-model-canvas - - antifragile author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/business-model-canvas.md b/.claude/skills/frameworks/business-model-canvas.md index b516be3..5e8e63f 100644 --- a/.claude/skills/frameworks/business-model-canvas.md +++ b/.claude/skills/frameworks/business-model-canvas.md @@ -1,6 +1,12 @@ --- name: "business-model-canvas" -description: "Structures and evaluates business models using Osterwalder's nine-block Business Model Canvas: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, and Cost Structure. Use when designing a new venture, comparing business model alternatives, stress-testing assumptions, planning pivots, exploring revenue model options, or identifying hidden dependencies between business model components." +description: "Structures and evaluates business models using Osterwalder's + nine-block Business Model Canvas: Customer Segments, Value Propositions, + Channels, Customer Relationships, Revenue Streams, Key Resources, Key + Activities, Key Partnerships, and Cost Structure. Use when designing a new + venture, comparing business model alternatives, stress-testing assumptions, + planning pivots, exploring revenue model options, or identifying hidden + dependencies between business model components." version: "1.0.0" category: "frameworks" complexity: "basic" @@ -19,9 +25,10 @@ tags: related_skills: - blue-ocean-strategy - porters-five-forces - - value-proposition-design - - unit-economics author: "Fatih Guner" +related_content: + - kind: template + ref: unit-economics-snapshot --- # Business Model Canvas diff --git a/.claude/skills/frameworks/covey-seven-habits.md b/.claude/skills/frameworks/covey-seven-habits.md index df290d4..db4f5be 100644 --- a/.claude/skills/frameworks/covey-seven-habits.md +++ b/.claude/skills/frameworks/covey-seven-habits.md @@ -1,6 +1,13 @@ --- name: "covey-seven-habits" -description: "Applies Stephen Covey's Seven Habits framework for personal and interpersonal effectiveness, progressing from dependence through independence to interdependence. Covers proactivity, mission clarity, prioritization, Win/Win thinking, empathic listening, synergy, and renewal. Use when conducting personal effectiveness audits, drafting mission statements, preparing Win/Win negotiations, resolving co-founder conflicts, designing founder renewal plans to prevent burnout, or building character-based leadership culture." +description: "Applies Stephen Covey's Seven Habits framework for personal and + interpersonal effectiveness, progressing from dependence through independence + to interdependence. Covers proactivity, mission clarity, prioritization, + Win/Win thinking, empathic listening, synergy, and renewal. Use when + conducting personal effectiveness audits, drafting mission statements, + preparing Win/Win negotiations, resolving co-founder conflicts, designing + founder renewal plans to prevent burnout, or building character-based + leadership culture." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -21,7 +28,7 @@ related_skills: - eisenhower-matrix - emotional-intelligence - grow-model - - tuckman-stages + - tuckman-team-stages author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/eisenhower-matrix.md b/.claude/skills/frameworks/eisenhower-matrix.md index 4aca7f2..e6b79bd 100644 --- a/.claude/skills/frameworks/eisenhower-matrix.md +++ b/.claude/skills/frameworks/eisenhower-matrix.md @@ -1,6 +1,12 @@ --- name: "eisenhower-matrix" -description: "Prioritizes tasks and time allocation using the Eisenhower Matrix, classifying activities into four quadrants by urgency and importance: Do (urgent and important), Schedule (important but not urgent), Delegate (urgent but not important), and Eliminate (neither). Use when overwhelmed by competing demands, auditing how a founder spends their time, designing delegation frameworks, building QII-first weekly calendars, or shifting organizational time allocation from reactive firefighting to strategic work." +description: "Prioritizes tasks and time allocation using the Eisenhower Matrix, + classifying activities into four quadrants by urgency and importance: Do + (urgent and important), Schedule (important but not urgent), Delegate (urgent + but not important), and Eliminate (neither). Use when overwhelmed by competing + demands, auditing how a founder spends their time, designing delegation + frameworks, building QII-first weekly calendars, or shifting organizational + time allocation from reactive firefighting to strategic work." version: "1.0.0" category: "frameworks" complexity: "basic" @@ -18,7 +24,7 @@ tags: related_skills: - covey-seven-habits - eisenhower-matrix - - kaizen + - kaizen-bpr - balanced-scorecard author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/four-ps-marketing.md b/.claude/skills/frameworks/four-ps-marketing.md index 2da43d1..6e53737 100644 --- a/.claude/skills/frameworks/four-ps-marketing.md +++ b/.claude/skills/frameworks/four-ps-marketing.md @@ -1,6 +1,13 @@ --- name: "four-ps-marketing" -description: "Designs and audits marketing strategy using McCarthy and Kotler's Four Ps framework: Product, Price, Place, and Promotion. Evaluates coherence across all four marketing mix elements to identify misalignments that undermine go-to-market effectiveness. Use when launching a new product, diagnosing why conversion rates are low despite strong product-market fit, redesigning pricing strategy, evaluating distribution channel options, planning go-to-market campaigns, or expanding from direct-to-consumer into retail." +description: "Designs and audits marketing strategy using McCarthy and Kotler's + Four Ps framework: Product, Price, Place, and Promotion. Evaluates coherence + across all four marketing mix elements to identify misalignments that + undermine go-to-market effectiveness. Use when launching a new product, + diagnosing why conversion rates are low despite strong product-market fit, + redesigning pricing strategy, evaluating distribution channel options, + planning go-to-market campaigns, or expanding from direct-to-consumer into + retail." version: "1.0.0" category: "frameworks" complexity: "basic" @@ -18,8 +25,6 @@ tags: related_skills: - blue-ocean-strategy - business-model-canvas - - crossing-the-chasm - - value-proposition-canvas author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/kotter-change-model.md b/.claude/skills/frameworks/kotter-change-model.md index 255e4b1..c0bf3e5 100644 --- a/.claude/skills/frameworks/kotter-change-model.md +++ b/.claude/skills/frameworks/kotter-change-model.md @@ -1,6 +1,12 @@ --- name: "kotter-change-model" -description: "Guides organizational change initiatives using Kotter's eight-step model: creating urgency, forming a guiding coalition, developing a vision, communicating the vision, empowering action, generating short-term wins, consolidating gains, and anchoring changes in culture. Use when leading a strategic pivot, implementing organizational restructuring, driving cultural transformation, managing post-acquisition integration, rolling out new processes at scale, or diagnosing why previous change efforts have failed." +description: "Guides organizational change initiatives using Kotter's eight-step + model: creating urgency, forming a guiding coalition, developing a vision, + communicating the vision, empowering action, generating short-term wins, + consolidating gains, and anchoring changes in culture. Use when leading a + strategic pivot, implementing organizational restructuring, driving cultural + transformation, managing post-acquisition integration, rolling out new + processes at scale, or diagnosing why previous change efforts have failed." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -17,7 +23,7 @@ tags: related_skills: - ambidexterity - covey-seven-habits - - tuckman-stages + - tuckman-team-stages - balanced-scorecard author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/leadership-pipeline.md b/.claude/skills/frameworks/leadership-pipeline.md index 03c9e85..e9ed212 100644 --- a/.claude/skills/frameworks/leadership-pipeline.md +++ b/.claude/skills/frameworks/leadership-pipeline.md @@ -91,7 +91,7 @@ The blockage symptom: the enterprise leader who cannot resist running one of the ## Prompts **Prompt 1 -- Pipeline Blockage Diagnosis:** -> My company is at [stage] with [number] employees. I'm experiencing these leadership challenges: [describe -- e.g., "My VP of Engineering still reviews every pull request," "My managers don't develop their people," "I can't step back from day-to-day operations"]. Using the Leadership Pipeline model, diagnose which passage transitions are blocked, what skills/time/values shifts haven't occurred, and recommend specific interventions to clear the blockages. +> My company is at [stage] with [number] employees. I'm experiencing these leadership challenges: [describe -- e.g., "My VP of Engineering still reviews every pull request," "My managers don't develop their people," "I can't step back from day-to-day operations"]. Using the Leadership Pipeline model, diagnose which passage transitions are blocked, what skills, time, and values shifts haven't occurred, and recommend specific interventions to clear the blockages. **Prompt 2 -- Founder Passage Planning:** > As founder and CEO of a [stage] startup growing from [current size] to [target size], map my personal leadership pipeline journey. What passage am I currently navigating? What skills must I develop, what time allocation must change, and what values must I adopt to successfully make this transition? Be specific about what I need to stop doing, start doing, and continue doing. diff --git a/.claude/skills/frameworks/organisational-culture.md b/.claude/skills/frameworks/organisational-culture.md index 7790a1c..622992d 100644 --- a/.claude/skills/frameworks/organisational-culture.md +++ b/.claude/skills/frameworks/organisational-culture.md @@ -1,6 +1,12 @@ --- name: "organisational-culture" -description: "Audits organizational culture using Schein's three-level model: visible artifacts, espoused values, and basic underlying assumptions. Diagnoses gaps between stated values and actual behaviour to reveal the invisible beliefs driving organizational dynamics. Use when experiencing culture dilution during rapid hiring, planning M&A cultural integration, diagnosing why culture change initiatives fail, or auditing founder imprint on company norms." +description: "Audits organizational culture using Schein's three-level model: + visible artifacts, espoused values, and basic underlying assumptions. + Diagnoses gaps between stated values and actual behaviour to reveal the + invisible beliefs driving organizational dynamics. Use when experiencing + culture dilution during rapid hiring, planning M&A cultural integration, + diagnosing why culture change initiatives fail, or auditing founder imprint on + company norms." version: "1.0.0" category: "frameworks" complexity: "advanced" @@ -15,7 +21,7 @@ tags: - values - assumptions related_skills: - - tuckman-stages + - tuckman-team-stages - belbin-team-roles - maslow-hierarchy - radical-candor diff --git a/.claude/skills/frameworks/porters-five-forces.md b/.claude/skills/frameworks/porters-five-forces.md index 7a0db74..27a3136 100644 --- a/.claude/skills/frameworks/porters-five-forces.md +++ b/.claude/skills/frameworks/porters-five-forces.md @@ -1,6 +1,10 @@ --- name: "porters-five-forces" -description: "Analyzes competitive industry dynamics using Porter's Five Forces framework. Evaluates threat of new entrants, supplier power, buyer power, substitution threats, and competitive rivalry. Use when assessing market entry decisions, developing competitive strategy, evaluating industry attractiveness, or analyzing pricing power." +description: "Analyzes competitive industry dynamics using Porter's Five Forces + framework. Evaluates threat of new entrants, supplier power, buyer power, + substitution threats, and competitive rivalry. Use when assessing market entry + decisions, developing competitive strategy, evaluating industry + attractiveness, or analyzing pricing power." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -18,7 +22,7 @@ tags: - profitability related_skills: - blue-ocean-strategy - - swot-analysis + - swot-pest-analysis - art-of-war - business-model-canvas - scenario-planning diff --git a/.claude/skills/frameworks/scenario-planning.md b/.claude/skills/frameworks/scenario-planning.md index 62c6310..c0ad5e6 100644 --- a/.claude/skills/frameworks/scenario-planning.md +++ b/.claude/skills/frameworks/scenario-planning.md @@ -1,6 +1,12 @@ --- name: "scenario-planning" -description: "Constructs multiple plausible future scenarios using a 2x2 matrix of critical uncertainties, then stress-tests strategy against each scenario to develop robust responses. Identifies no-regret moves, hedging actions, and strategic options. Use when facing major capital allocation decisions, evaluating market expansion under regulatory uncertainty, preparing for technology disruption, or building enterprise risk management into strategic planning cycles." +description: "Constructs multiple plausible future scenarios using a 2x2 matrix + of critical uncertainties, then stress-tests strategy against each scenario to + develop robust responses. Identifies no-regret moves, hedging actions, and + strategic options. Use when facing major capital allocation decisions, + evaluating market expansion under regulatory uncertainty, preparing for + technology disruption, or building enterprise risk management into strategic + planning cycles." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -18,7 +24,7 @@ tags: related_skills: - black-swans - porters-five-forces - - swot-analysis + - swot-pest-analysis - blue-ocean-strategy author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/thomas-kilmann-conflict.md b/.claude/skills/frameworks/thomas-kilmann-conflict.md index a1b2f28..fd15e6d 100644 --- a/.claude/skills/frameworks/thomas-kilmann-conflict.md +++ b/.claude/skills/frameworks/thomas-kilmann-conflict.md @@ -1,6 +1,12 @@ --- name: "thomas-kilmann-conflict" -description: "Diagnoses and resolves conflicts using the Thomas-Kilmann five-mode framework: competing, collaborating, compromising, avoiding, and accommodating, mapped across assertiveness and cooperativeness dimensions. Use when navigating co-founder disagreements, mediating cross-functional team friction, choosing the right conflict mode for high-stakes decisions, expanding personal conflict style range, or designing conflict resolution processes for the organization." +description: "Diagnoses and resolves conflicts using the Thomas-Kilmann + five-mode framework: competing, collaborating, compromising, avoiding, and + accommodating, mapped across assertiveness and cooperativeness dimensions. Use + when navigating co-founder disagreements, mediating cross-functional team + friction, choosing the right conflict mode for high-stakes decisions, + expanding personal conflict style range, or designing conflict resolution + processes for the organization." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -18,7 +24,7 @@ tags: related_skills: - radical-candor - win-win-negotiation - - tuckman-stages + - tuckman-team-stages - trust-equation author: "Fatih Guner" --- diff --git a/.claude/skills/frameworks/tipping-point.md b/.claude/skills/frameworks/tipping-point.md index 7938779..ae9c150 100644 --- a/.claude/skills/frameworks/tipping-point.md +++ b/.claude/skills/frameworks/tipping-point.md @@ -1,6 +1,12 @@ --- name: "tipping-point" -description: "Analyzes viral growth potential using Gladwell's Tipping Point framework through three rules: the Law of the Few (Connectors, Mavens, Salespeople), the Stickiness Factor, and the Power of Context. Use when product growth is stubbornly linear despite high satisfaction, designing launch strategies for organic adoption, engineering shareable product moments, identifying key influencers in a target market, or diagnosing why a superior product fails to spread." +description: "Analyzes viral growth potential using Gladwell's Tipping Point + framework through three rules: the Law of the Few (Connectors, Mavens, + Salespeople), the Stickiness Factor, and the Power of Context. Use when + product growth is stubbornly linear despite high satisfaction, designing + launch strategies for organic adoption, engineering shareable product moments, + identifying key influencers in a target market, or diagnosing why a superior + product fails to spread." version: "1.0.0" category: "frameworks" complexity: "intermediate" @@ -15,7 +21,6 @@ tags: - word-of-mouth - adoption related_skills: - - crossing-the-chasm - blue-ocean-strategy - four-ps-marketing author: "Fatih Guner" diff --git a/.claude/skills/negotiation/negotiation-mindset-and-self.md b/.claude/skills/negotiation/negotiation-mindset-and-self.md index 67f28b9..ec3a091 100644 --- a/.claude/skills/negotiation/negotiation-mindset-and-self.md +++ b/.claude/skills/negotiation/negotiation-mindset-and-self.md @@ -1,6 +1,13 @@ --- name: "negotiation-mindset-and-self" -description: "Builds the internal foundation required before entering any negotiation: identity as a negotiator, strategic self-awareness, emotional self-management, assumption auditing, and deliberate style selection. Provides practical self-assessment checklists and pre-negotiation protocols. Use when preparing mentally for a high-stakes conversation, diagnosing why past negotiations underperformed, recognising negotiation dynamics in daily business interactions, coaching team members on negotiation readiness, or choosing between competitive and cooperative approaches for an upcoming deal." +description: "Builds the internal foundation required before entering any + negotiation: identity as a negotiator, strategic self-awareness, emotional + self-management, assumption auditing, and deliberate style selection. Provides + practical self-assessment checklists and pre-negotiation protocols. Use when + preparing mentally for a high-stakes conversation, diagnosing why past + negotiations underperformed, recognising negotiation dynamics in daily + business interactions, coaching team members on negotiation readiness, or + choosing between competitive and cooperative approaches for an upcoming deal." version: "1.0.0" category: "negotiation" complexity: "basic" @@ -24,7 +31,7 @@ related_skills: - negotiation-game-theory - thomas-kilmann-conflict - trust-equation - - stoic-perception + - stoic-unbiased-thought author: "Fatih Guner" --- diff --git a/.claude/solo-mode/SOLO.md b/.claude/solo-mode/SOLO.md index 195e45e..033fb7c 100644 --- a/.claude/solo-mode/SOLO.md +++ b/.claude/solo-mode/SOLO.md @@ -1,5 +1,7 @@ # Solo Mode — Orchestrator Operating Manual +Capacity rule: measure the founder's workload before promising time savings. Do not assume contractor budget or automation suitability. Start with one measured routine and one bounded improvement; do not promise 10–15 saved hours from an unmeasured intervention. + Solo mode adapts the entire Foreman system for solopreneurs: individuals who are the company. No co-founder, no team, no board of directors, possibly no external investors. The business is an extension of one person's capabilities, decisions, and constraints. Every skill, diagnostic, playbook, template, and hook in the system was designed with the assumption that a founder operates within a multi-person structure — reporting to a board, delegating to a team, pitching to investors. Solo mode removes those assumptions without removing the frameworks. The intellectual architecture remains intact. The application context shifts. --- diff --git a/.claude/solo-mode/solo-audience-map.yaml b/.claude/solo-mode/solo-audience-map.yaml index a47f6ec..20ac060 100644 --- a/.claude/solo-mode/solo-audience-map.yaml +++ b/.claude/solo-mode/solo-audience-map.yaml @@ -15,47 +15,89 @@ audience_mapping: investor: solo_equivalent: "self-funding-analysis" - description: "Investor-facing outputs become personal financial analysis documents. The solopreneur is both the operator and the capital allocator. Replace investor persuasion framing with honest self-assessment of business viability and personal income sustainability." - tone_shift: "Remove persuasive pitch framing. Replace with analytical self-assessment. The audience is you — be honest, not impressive." + description: "Investor-facing outputs become personal financial analysis + documents. The solopreneur is both the operator and the capital allocator. + Replace investor persuasion framing with honest self-assessment of + business viability and personal income sustainability." + tone_shift: "Remove persuasive pitch framing. Replace with analytical + self-assessment. The audience is you — be honest, not impressive." structural_changes: - - "Replace 'investor returns' with 'personal income sustainability and wealth building'" + - "Replace 'investor returns' with 'personal income sustainability and + wealth building'" - "Replace 'fundraising narrative' with 'business viability assessment'" - - "Replace 'term sheet negotiation' with 'financing terms evaluation (loans, grants, revenue-based financing)'" + - "Replace 'term sheet negotiation' with 'financing terms evaluation + (loans, grants, revenue-based financing)'" - "Replace 'board seat allocation' with 'advisory relationship structure'" - - "Replace 'exit strategy' with 'long-term business trajectory and personal exit options'" + - "Replace 'exit strategy' with 'long-term business trajectory and + personal exit options'" - "Replace 'dilution analysis' with 'ownership and control preservation'" - exception: "If identity.yaml indicates the solopreneur has external investors (angels, micro-VCs, loan providers), use a hybrid approach: retain financial rigor but strip the pitch language. Present data, not a narrative designed to persuade." + exception: "If identity.yaml indicates the solopreneur has external investors + (angels, micro-VCs, loan providers), use a hybrid approach: retain + financial rigor but strip the pitch language. Present data, not a + narrative designed to persuade." template_adaptations: - - template: "investor/cap-table-summary" - adaptation: "Reframe as ownership and equity structure document. If no external investors, simplify to a single-owner statement with any contractor equity or profit-sharing arrangements noted." - - - template: "investor/competitive-landscape-brief" - adaptation: "Use as-is. Competitive analysis is equally relevant to solopreneurs. Remove the 'defensibility pitch' angle and replace with 'competitive awareness for strategic positioning.'" - - - template: "investor/decision-rationale-memo" - adaptation: "Reframe as personal decision journal entry. Replace 'communicate rationale to investors' with 'document your reasoning for future reference and accountability partner review.'" - - - template: "investor/due-diligence-checklist" - adaptation: "Reframe as annual business health audit. The solopreneur performs due diligence on their own business. Replace 'what investors will check' with 'what you should verify about your business quarterly.'" - - - template: "investor/exit-scenario-analysis" - adaptation: "Reframe as long-term optionality analysis. Replace 'exit for investor returns' with 'options for the future: sell, wind down, transition to lifestyle business, hire and grow, or continue as-is.'" - - - template: "investor/fundraising-deck-outline" - adaptation: "Reframe as business plan outline for personal clarity or loan/grant applications. Strip the slide-by-slide investor deck structure and replace with a written business plan format." - - - template: "investor/investor-update-email" - adaptation: "Reframe as monthly self-review email to accountability partner or mentor. Replace investor-specific metrics framing with personal progress metrics. If the solopreneur has angel investors, retain the format but adjust tone from 'selling' to 'reporting.'" - - - template: "investor/market-opportunity-summary" - adaptation: "Use mostly as-is. Market sizing applies regardless of company size. Remove 'TAM/SAM/SOM for investor persuasion' framing and replace with 'addressable market for realistic revenue planning.'" - - - template: "investor/strategic-analysis-one-pager" - adaptation: "Reframe as personal strategic summary. A one-page overview of where the business stands, written for the solopreneur's own clarity and for sharing with mentors." - - - template: "investor/unit-economics-snapshot" - adaptation: "Reframe as personal income sustainability dashboard. Replace 'metrics that trigger investor concern' with 'metrics that indicate business health.' Focus on: personal draw, profit margin, effective hourly rate, client concentration risk, revenue predictability." + - adaptation: "Reframe as ownership and equity structure document. If no external + investors, simplify to a single-owner statement with any contractor + equity or profit-sharing arrangements noted." + kind: template + ref: cap-table-summary + + - adaptation: "Use as-is. Competitive analysis is equally relevant to + solopreneurs. Remove the 'defensibility pitch' angle and replace with + 'competitive awareness for strategic positioning.'" + kind: template + ref: competitive-landscape-brief + + - adaptation: "Reframe as personal decision journal entry. Replace 'communicate + rationale to investors' with 'document your reasoning for future + reference and accountability partner review.'" + kind: template + ref: decision-rationale-memo + + - adaptation: "Reframe as annual business health audit. The solopreneur performs + due diligence on their own business. Replace 'what investors will + check' with 'what you should verify about your business quarterly.'" + kind: template + ref: due-diligence-checklist + + - adaptation: "Reframe as long-term optionality analysis. Replace 'exit for + investor returns' with 'options for the future: sell, wind down, + transition to lifestyle business, hire and grow, or continue as-is.'" + kind: template + ref: exit-scenario-analysis + + - adaptation: "Reframe as business plan outline for personal clarity or loan/grant + applications. Strip the slide-by-slide investor deck structure and + replace with a written business plan format." + kind: template + ref: fundraising-deck-outline + + - adaptation: "Reframe as monthly self-review email to accountability partner or + mentor. Replace investor-specific metrics framing with personal + progress metrics. If the solopreneur has angel investors, retain the + format but adjust tone from 'selling' to 'reporting.'" + kind: template + ref: investor-update-email + + - adaptation: "Use mostly as-is. Market sizing applies regardless of company size. + Remove 'TAM/SAM/SOM for investor persuasion' framing and replace with + 'addressable market for realistic revenue planning.'" + kind: template + ref: market-opportunity-summary + + - adaptation: "Reframe as personal strategic summary. A one-page overview of where + the business stands, written for the solopreneur's own clarity and for + sharing with mentors." + kind: template + ref: strategic-analysis-one-pager + + - adaptation: "Reframe as personal income sustainability dashboard. Replace + 'metrics that trigger investor concern' with 'metrics that indicate + business health.' Focus on: personal draw, profit margin, effective + hourly rate, client concentration risk, revenue predictability." + kind: template + ref: unit-economics-snapshot # ───────────────────────────────────────────── # BOARD → MENTOR-ADVISOR @@ -63,38 +105,77 @@ audience_mapping: board: solo_equivalent: "mentor-advisor" - description: "Board-facing outputs become mentor or accountability partner briefs. The solopreneur has no board of directors. Governance language is replaced with personal accountability language. Formal board structures are replaced with informal but rigorous self-governance practices." - tone_shift: "Remove formal governance tone. Replace with direct, conversational briefing appropriate for a trusted mentor. Less 'resolution' language, more 'here is where I am and what I am thinking.'" + description: "Board-facing outputs become mentor or accountability partner + briefs. The solopreneur has no board of directors. Governance language is + replaced with personal accountability language. Formal board structures + are replaced with informal but rigorous self-governance practices." + tone_shift: "Remove formal governance tone. Replace with direct, conversational + briefing appropriate for a trusted mentor. Less 'resolution' language, + more 'here is where I am and what I am thinking.'" structural_changes: - - "Replace 'board of directors' with 'mentor, advisor, or accountability partner'" - - "Replace 'board resolution' with 'decision rationale documented for review'" - - "Replace 'quarterly board review' with 'quarterly self-review shared with mentor'" - - "Replace 'committee recommendation' with 'personal analysis and conclusion'" - - "Replace 'board approval required' with 'decision point: commit or defer'" - - "Replace 'fiduciary responsibility' with 'personal responsibility and ethical commitment'" - exception: "If the solopreneur has a formal advisory board (not a governance board), retain the briefing format but adjust the power dynamic. Advisors advise; they do not approve or veto." + - "Replace 'board of directors' with 'mentor, advisor, or accountability + partner'" + - "Replace 'board resolution' with 'decision rationale documented for + review'" + - "Replace 'quarterly board review' with 'quarterly self-review shared + with mentor'" + - "Replace 'committee recommendation' with 'personal analysis and + conclusion'" + - "Replace 'board approval required' with 'decision point: commit or + defer'" + - "Replace 'fiduciary responsibility' with 'personal responsibility and + ethical commitment'" + exception: "If the solopreneur has a formal advisory board (not a governance + board), retain the briefing format but adjust the power dynamic. Advisors + advise; they do not approve or veto." template_adaptations: - - template: "board/board-meeting-agenda" - adaptation: "Reframe as structured mentor meeting agenda. Replace governance items (approvals, resolutions, committee reports) with discussion items: strategic questions, decision pressure-tests, and accountability check-ins." - - - template: "board/ceo-succession-brief" - adaptation: "Reframe as business continuity plan. The solopreneur has no CEO to succeed, but does need a plan for what happens if they are incapacitated, want to step back, or decide to sell. Replace succession language with contingency planning." - - - template: "board/change-initiative-proposal" - adaptation: "Reframe as personal pivot or strategic shift memo. Replace 'propose to the board' with 'document the change rationale for personal clarity and mentor discussion.'" - - - template: "board/compensation-review-brief" - adaptation: "Reframe as personal draw and compensation structure review. Replace employee compensation analysis with: what the solopreneur pays themselves, whether the amount is sustainable, and how it compares to market alternatives (employment)." - - - template: "board/quarterly-strategic-review" - adaptation: "Reframe as quarterly self-assessment. Retain the strategic review structure (performance vs. goals, market conditions, competitive position) but address it to yourself or your mentor. Replace 'board discussion points' with 'decisions to make this quarter.'" - - - template: "board/regulatory-compliance-update" - adaptation: "Use mostly as-is. Regulatory compliance applies to solo businesses. Remove board-specific reporting structure and present as a personal compliance checklist." - - - template: "board/risk-assessment-brief" - adaptation: "Reframe as personal risk register. Replace organizational risk categories with solo-specific risks: key-person dependency (you), client concentration, revenue volatility, health and burnout, skill gaps without team coverage." + - adaptation: "Reframe as structured mentor meeting agenda. Replace governance + items (approvals, resolutions, committee reports) with discussion + items: strategic questions, decision pressure-tests, and + accountability check-ins." + kind: template + ref: board-meeting-agenda + + - adaptation: "Reframe as business continuity plan. The solopreneur has no CEO to + succeed, but does need a plan for what happens if they are + incapacitated, want to step back, or decide to sell. Replace + succession language with contingency planning." + kind: template + ref: ceo-succession-brief + + - adaptation: "Reframe as personal pivot or strategic shift memo. Replace 'propose + to the board' with 'document the change rationale for personal clarity + and mentor discussion.'" + kind: template + ref: change-initiative-proposal + + - adaptation: "Reframe as personal draw and compensation structure review. Replace + employee compensation analysis with: what the solopreneur pays + themselves, whether the amount is sustainable, and how it compares to + market alternatives (employment)." + kind: template + ref: compensation-review-brief + + - adaptation: "Reframe as quarterly self-assessment. Retain the strategic review + structure (performance vs. goals, market conditions, competitive + position) but address it to yourself or your mentor. Replace 'board + discussion points' with 'decisions to make this quarter.'" + kind: template + ref: quarterly-strategic-review + + - adaptation: "Use mostly as-is. Regulatory compliance applies to solo businesses. + Remove board-specific reporting structure and present as a personal + compliance checklist." + kind: template + ref: regulatory-compliance-update + + - adaptation: "Reframe as personal risk register. Replace organizational risk + categories with solo-specific risks: key-person dependency (you), + client concentration, revenue volatility, health and burnout, skill + gaps without team coverage." + kind: template + ref: risk-assessment-brief # ───────────────────────────────────────────── # TEAM → SYSTEMS-AND-PROCESSES @@ -102,55 +183,107 @@ audience_mapping: team: solo_equivalent: "systems-and-processes" - description: "Team-facing outputs become process documentation, personal operating procedures, and contractor briefs. Where the default creates alignment documents for humans on a team, solo mode creates reference documents for the solopreneur's own consistency, for onboarding contractors, or for delegating to AI tools." - tone_shift: "Remove alignment and motivation language. Replace with clear, procedural instruction. The audience is either future-you (who will forget the details) or a contractor (who needs explicit direction)." + description: "Team-facing outputs become process documentation, personal + operating procedures, and contractor briefs. Where the default creates + alignment documents for humans on a team, solo mode creates reference + documents for the solopreneur's own consistency, for onboarding + contractors, or for delegating to AI tools." + tone_shift: "Remove alignment and motivation language. Replace with clear, + procedural instruction. The audience is either future-you (who will forget + the details) or a contractor (who needs explicit direction)." structural_changes: - "Replace 'team alignment' with 'process documentation'" - - "Replace 'communicate to team' with 'document for personal reference or contractor handoff'" + - "Replace 'communicate to team' with 'document for personal reference or + contractor handoff'" - "Replace 'team meeting' with 'weekly self-review or contractor check-in'" - - "Replace 'assign to team member' with 'schedule in personal workflow or brief to contractor'" + - "Replace 'assign to team member' with 'schedule in personal workflow or + brief to contractor'" - "Replace 'team values' with 'business principles and personal standards'" - - "Replace 'onboarding new hire' with 'onboarding new contractor or documenting for future delegation'" + - "Replace 'onboarding new hire' with 'onboarding new contractor or + documenting for future delegation'" template_adaptations: - - template: "team/action-plan" - adaptation: "Reframe as personal implementation plan. Replace 'owner' column (team members) with 'method' column (do personally, outsource to contractor, automate, defer). Add time estimate per item." - - - template: "team/culture-values-document" - adaptation: "Reframe as business principles and brand values document. Replace organizational culture language with personal business philosophy: how you treat clients, what you refuse to compromise on, how you make decisions." - - - template: "team/feedback-360-template" - adaptation: "Reframe as client feedback collection template. Replace peer and manager feedback sections with: client satisfaction questions, referral source interviews, and self-assessment against business goals." - - - template: "team/hiring-scorecard" - adaptation: "Reframe as contractor evaluation scorecard. Replace hiring criteria (culture fit, growth potential, team dynamics) with contractor criteria: deliverable quality, communication reliability, rate alignment, domain expertise." - - - template: "team/incident-postmortem" - adaptation: "Use mostly as-is. Postmortems are valuable for solo operators. Replace 'team debrief' with 'personal debrief.' The root cause analysis and prevention steps apply identically." - - - template: "team/meeting-notes-template" - adaptation: "Reframe as client meeting notes or contractor check-in notes. Replace internal meeting structure with external meeting documentation." - - - template: "team/new-initiative-brief" - adaptation: "Reframe as new project brief for personal planning. Replace 'team resources required' with 'time investment required, contractor support needed, tools to acquire.'" - - - template: "team/offsite-planning-guide" - adaptation: "Reframe as personal strategic retreat planning guide. Replace team offsite logistics with solo retreat structure: reflection exercises, strategic planning blocks, environment design." - - - template: "team/one-on-one-template" - adaptation: "Reframe as mentor meeting preparation template or contractor check-in template. Replace manager-report dynamic with peer advisory dynamic." - - - template: "team/project-kickoff-document" - adaptation: "Reframe as project start checklist. Replace team roles and responsibilities with personal task breakdown and contractor scope definitions." - - - template: "team/retrospective-template" - adaptation: "Reframe as personal retrospective. Replace team retrospective facilitation with structured self-reflection: what went well, what did not, what to change. A weekly or monthly solo practice." - - - template: "team/role-description-template" - adaptation: "Reframe as contractor scope of work template. Replace job description format with project-based scope definition: deliverables, timeline, communication expectations, quality standards." - - - template: "team/team-health-check" - adaptation: "Reframe as personal sustainability check. Replace team health dimensions (morale, alignment, psychological safety) with solo health dimensions: energy level, financial runway, client satisfaction, skill development, work-life sustainability." + - adaptation: "Reframe as personal implementation plan. Replace 'owner' column + (team members) with 'method' column (do personally, outsource to + contractor, automate, defer). Add time estimate per item." + kind: template + ref: action-plan + + - adaptation: "Reframe as business principles and brand values document. Replace + organizational culture language with personal business philosophy: how + you treat clients, what you refuse to compromise on, how you make + decisions." + kind: template + ref: culture-values-document + + - adaptation: "Reframe as client feedback collection template. Replace peer and + manager feedback sections with: client satisfaction questions, + referral source interviews, and self-assessment against business + goals." + kind: template + ref: feedback-360-template + + - adaptation: "Reframe as contractor evaluation scorecard. Replace hiring criteria + (culture fit, growth potential, team dynamics) with contractor + criteria: deliverable quality, communication reliability, rate + alignment, domain expertise." + kind: template + ref: hiring-scorecard + + - adaptation: "Use mostly as-is. Postmortems are valuable for solo operators. + Replace 'team debrief' with 'personal debrief.' The root cause + analysis and prevention steps apply identically." + kind: template + ref: incident-postmortem + + - adaptation: "Reframe as client meeting notes or contractor check-in notes. + Replace internal meeting structure with external meeting + documentation." + kind: template + ref: meeting-notes-template + + - adaptation: "Reframe as new project brief for personal planning. Replace 'team + resources required' with 'time investment required, contractor support + needed, tools to acquire.'" + kind: template + ref: new-initiative-brief + + - adaptation: "Reframe as personal strategic retreat planning guide. Replace team + offsite logistics with solo retreat structure: reflection exercises, + strategic planning blocks, environment design." + kind: template + ref: offsite-planning-guide + + - adaptation: "Reframe as mentor meeting preparation template or contractor + check-in template. Replace manager-report dynamic with peer advisory + dynamic." + kind: template + ref: one-on-one-template + + - adaptation: "Reframe as project start checklist. Replace team roles and + responsibilities with personal task breakdown and contractor scope + definitions." + kind: template + ref: project-kickoff-document + + - adaptation: "Reframe as personal retrospective. Replace team retrospective + facilitation with structured self-reflection: what went well, what did + not, what to change. A weekly or monthly solo practice." + kind: template + ref: retrospective-template + + - adaptation: "Reframe as contractor scope of work template. Replace job + description format with project-based scope definition: deliverables, + timeline, communication expectations, quality standards." + kind: template + ref: role-description-template + + - adaptation: "Reframe as personal sustainability check. Replace team health + dimensions (morale, alignment, psychological safety) with solo health + dimensions: energy level, financial runway, client satisfaction, skill + development, work-life sustainability." + kind: template + ref: team-health-check # ───────────────────────────────────────────── # CLIENT → CLIENT (unchanged) @@ -158,34 +291,44 @@ audience_mapping: client: solo_equivalent: "client" - description: "Client-facing outputs require no adaptation. The solopreneur serves clients in the same professional capacity as a larger firm. Quality standards and communication expectations are identical." + description: "Client-facing outputs require no adaptation. The solopreneur + serves clients in the same professional capacity as a larger firm. Quality + standards and communication expectations are identical." tone_shift: "No change." structural_changes: [] template_adaptations: - - template: "client/analysis-report" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: analysis-report - - template: "client/case-study-template" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: case-study-template - - template: "client/onboarding-welcome-packet" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: onboarding-welcome-packet - - template: "client/partnership-memo" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: partnership-memo - - template: "client/project-status-update" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: project-status-update - - template: "client/proposal-outline" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: proposal-outline - - template: "client/quarterly-business-review" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: quarterly-business-review - - template: "client/service-level-agreement" - adaptation: "Use as-is." + - adaptation: "Use as-is." + kind: template + ref: service-level-agreement # ───────────────────────────────────────────── # SELF → SELF (unchanged, elevated to default) @@ -193,38 +336,63 @@ audience_mapping: self: solo_equivalent: "self" - description: "Self-facing outputs are already personal. In solo mode, self becomes the default audience when no audience is specified. These templates are the solopreneur's primary working documents." + description: "Self-facing outputs are already personal. In solo mode, self + becomes the default audience when no audience is specified. These + templates are the solopreneur's primary working documents." tone_shift: "No change. Already appropriately personal." structural_changes: - - "Elevate to default audience when no audience is specified (in default mode, the system infers audience from context; in solo mode, self is the fallback)" + - "Elevate to default audience when no audience is specified (in default + mode, the system infers audience from context; in solo mode, self is the + fallback)" template_adaptations: - - template: "self/annual-review-and-planning" - adaptation: "Use as-is. Add emphasis on personal income review and work-life sustainability assessment." - - - template: "self/career-strategy-canvas" - adaptation: "Use as-is. In solo mode, career strategy and business strategy are the same document." - - - template: "self/decision-journal" - adaptation: "Use as-is. Elevated importance — the decision journal is the solopreneur's primary accountability mechanism." - - - template: "self/founder-mental-health-check" - adaptation: "Use as-is. Add solo-specific prompts: isolation assessment, boundary audit, support network inventory." - - - template: "self/leadership-reflection" - adaptation: "Reframe as business owner reflection. Replace leadership-of-others prompts with leadership-of-self prompts." - - - template: "self/learning-plan" - adaptation: "Use as-is. Learning is more urgent when there is no team with complementary skills." - - - template: "self/negotiation-prep-sheet" - adaptation: "Use as-is." - - - template: "self/personal-board-tracker" - adaptation: "Reframe as mentor and advisor network tracker. Replace board governance tracking with informal advisory relationship management." - - - template: "self/stakeholder-map" - adaptation: "Use as-is. The solopreneur's stakeholder map is simpler (no internal stakeholders) but still valuable for client, partner, and vendor relationship management." - - - template: "self/weekly-ceo-review" - adaptation: "Reframe as weekly business owner review. Replace CEO framing with owner-operator framing. This becomes the solopreneur's primary weekly practice." + - adaptation: "Use as-is. Add emphasis on personal income review and work-life + sustainability assessment." + kind: template + ref: annual-review-and-planning + + - adaptation: "Use as-is. In solo mode, career strategy and business strategy are + the same document." + kind: template + ref: career-strategy-canvas + + - adaptation: "Use as-is. Elevated importance — the decision journal is the + solopreneur's primary accountability mechanism." + kind: template + ref: decision-journal + + - adaptation: "Use as-is. Add solo-specific prompts: isolation assessment, + boundary audit, support network inventory." + kind: template + ref: founder-mental-health-check + + - adaptation: "Reframe as business owner reflection. Replace leadership-of-others + prompts with leadership-of-self prompts." + kind: template + ref: leadership-reflection + + - adaptation: "Use as-is. Learning is more urgent when there is no team with + complementary skills." + kind: template + ref: learning-plan + + - adaptation: "Use as-is." + kind: template + ref: negotiation-prep-sheet + + - adaptation: "Reframe as mentor and advisor network tracker. Replace board + governance tracking with informal advisory relationship management." + kind: template + ref: personal-board-tracker + + - adaptation: "Use as-is. The solopreneur's stakeholder map is simpler (no + internal stakeholders) but still valuable for client, partner, and + vendor relationship management." + kind: template + ref: stakeholder-map + + - adaptation: "Reframe as weekly business owner review. Replace CEO framing with + owner-operator framing. This becomes the solopreneur's primary weekly + practice." + kind: template + ref: weekly-ceo-review diff --git a/.claude/stoic-mode/STOIC-MODE.md b/.claude/stoic-mode/STOIC-MODE.md index 13bf99e..d5b7bb4 100644 --- a/.claude/stoic-mode/STOIC-MODE.md +++ b/.claude/stoic-mode/STOIC-MODE.md @@ -1,5 +1,7 @@ # Stoic Mode -- Orchestrator Instructions +Evidence rule: philosophical reflection does not justify an automatic product freeze, feature removal or competitor-monitoring ban. Connect any operational change to customer evidence and capacity. Use concepts present in the source; do not invent named Stoic principles. + When `/stoic on` is active, every system response passes through a Stoic philosophical lens. This mode does not change WHAT the system delivers -- it changes HOW it frames, contextualises, and deepens the delivery. The same Porter's Five Forces analysis runs identically; the difference is that the output carries Stoic wisdom alongside strategic insight. Solo mode asks: "Who is this for?" and filters content accordingly. diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json index f2748ac..ae1eae0 100644 --- a/.codex-plugin/plugin.json +++ b/.codex-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "foreman", - "version": "1.0.0", + "version": "1.1.0-rc.1", "description": "AI-powered strategic advisor for entrepreneurs. 158 skills across 12 categories, from Porter's Five Forces to Stoic philosophy, with diagnostics, playbooks, output templates, and industry-specific packs.", "author": { "name": "Fatih Guner", @@ -22,7 +22,7 @@ "decision-making", "ai-advisor" ], - "skills": "./skills/", + "skills": "./plugins/foreman/skills/", "interface": { "displayName": "Foreman", "shortDescription": "AI-powered strategic advisor for entrepreneurs", diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 871db18..c99aae3 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -4,189 +4,30 @@ on: branches: [main] pull_request: branches: [main] - permissions: contents: read - jobs: - validate-content: - name: Validate Content - runs-on: ubuntu-latest + verify: + strategy: + fail-fast: false + matrix: + os: [ubuntu-latest, macos-latest] + node: [22, 24] + runs-on: ${{ matrix.os }} steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - - - name: Make scripts executable - run: chmod +x scripts/*.sh - - - name: Run full validation suite - run: bash scripts/validate-all.sh - - check-refs: - name: Check Cross-References - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - - - name: Make scripts executable - run: chmod +x scripts/*.sh - - - name: Check for broken references - run: bash scripts/broken-refs.sh - - check-style: - name: Check Style Compliance - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - - - name: Scan for prohibited phrases - run: | - EXIT_CODE=0 - - PROHIBITED_PHRASES=( - "In today's fast-paced" - "In today's rapidly" - "Let's dive in" - "Let's explore" - "In this skill, you will learn" - "Without further ado" - "It's important to note that" - "At the end of the day" - ) - - echo "Scanning .md files for prohibited phrases..." - for phrase in "${PROHIBITED_PHRASES[@]}"; do - MATCHES=$(grep -ril "$phrase" --include="*.md" . \ - --exclude="CLAUDE.md" \ - --exclude="CONTRIBUTING.md" \ - --exclude-dir="docs" \ - --exclude-dir="openclaw-templates" \ - --exclude-dir=".git" \ - --exclude-dir="node_modules" \ - --exclude-dir="skills" || true) - if [ -n "$MATCHES" ]; then - echo "::error::Prohibited phrase found: \"$phrase\"" - echo "$MATCHES" | while read -r file; do - LINE=$(grep -n "$phrase" "$file" | head -1) - echo " $file: $LINE" - done - EXIT_CODE=1 - fi - done - - echo "" - echo "Scanning .md files for author name leaks..." - # Source authors that must remain anonymized - AUTHOR_NAMES=( - "De Cremer" - "Bryan Garner" - "Matthew Dicks" - "Dave Kerpen" - "Rick Rubin" - "Shane Parrish" - "Todd Rogers" - "Lasky-Fink" - ) - - for name in "${AUTHOR_NAMES[@]}"; do - MATCHES=$(grep -ril "$name" --include="*.md" . \ - --exclude-dir=".git" \ - --exclude-dir="node_modules" \ - --exclude-dir="skills" || true) - if [ -n "$MATCHES" ]; then - echo "::error::Author name leak found: \"$name\"" - echo "$MATCHES" | while read -r file; do - LINE=$(grep -n "$name" "$file" | head -1) - echo " $file: $LINE" - done - EXIT_CODE=1 - fi - done - - if [ $EXIT_CODE -eq 0 ]; then - echo "Style check passed. No prohibited phrases or author leaks found." - fi - exit $EXIT_CODE - - check-formatting: - name: Check Formatting - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - - - name: Validate frontmatter on .claude/ markdown files - run: | - EXIT_CODE=0 - echo "Checking that all .md files in .claude/ have YAML frontmatter..." - - while IFS= read -r -d '' file; do - # Skip _schema directories, master docs (CAPS.md), mode configs, and command files - if [[ "$file" == *"/_schema/"* ]] || \ - [[ "$(basename "$file")" =~ ^[A-Z]+\.md$ ]] || \ - [[ "$file" == *"-mode/"* ]] || \ - [[ "$file" == */commands/* ]] || \ - [[ "$file" == */implementation/IMPLEMENTATION.md ]] || \ - [[ "$file" == */simulation/SIMULATION.md ]] || \ - [[ "$file" == */org-politics/ORG-POLITICS.md ]]; then - continue - fi - - # Check if file starts with frontmatter delimiter - FIRST_LINE=$(head -1 "$file") - if [ "$FIRST_LINE" != "---" ]; then - echo "::error file=$file::Missing YAML frontmatter (file does not start with ---)" - EXIT_CODE=1 - continue - fi - - # Check if frontmatter is closed - CLOSE_LINE=$(tail -n +2 "$file" | grep -n "^---$" | head -1 | cut -d: -f1) - if [ -z "$CLOSE_LINE" ]; then - echo "::error file=$file::Unclosed YAML frontmatter (no closing ---)" - EXIT_CODE=1 - fi - done < <(find .claude -name "*.md" -type f -print0) - - if [ $EXIT_CODE -eq 0 ]; then - echo "Formatting check passed. All .claude/ markdown files have valid frontmatter." - fi - exit $EXIT_CODE - - build-codex: - name: Verify Codex Build - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - - - name: Build Codex skills directory - run: | - chmod +x scripts/build-codex.sh - ./scripts/build-codex.sh --clean - - - name: Verify skill count matches - run: | - SOURCE_COUNT=$(find .claude/skills -name "*.md" -not -path "*/_schema/*" | wc -l) - TARGET_COUNT=$(find skills -mindepth 2 -name "SKILL.md" | wc -l) - echo "Source skills: $SOURCE_COUNT" - echo "Codex skills: $TARGET_COUNT" - if [ "$SOURCE_COUNT" -ne "$TARGET_COUNT" ]; then - echo "::error::Skill count mismatch: $SOURCE_COUNT source vs $TARGET_COUNT Codex" - exit 1 - fi - echo "Skill count verified: $TARGET_COUNT" - - - name: Verify plugin manifest + - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 + - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4 + with: + node-version: ${{ matrix.node }} + cache: npm + - run: npm ci --ignore-scripts + - run: npm run build + - run: npm run build:plugins + - run: npm run check + - run: npm run check:release + - name: Verify committed plugin bundles are current run: | - if [ ! -f .codex-plugin/plugin.json ]; then - echo "::error::Missing .codex-plugin/plugin.json" - exit 1 - fi - python3 -c "import json; json.load(open('.codex-plugin/plugin.json'))" || { - echo "::error::Invalid JSON in plugin.json" - exit 1 - } - echo "Plugin manifest valid." + git diff --exit-code + test -z "$(git ls-files --others --exclude-standard)" + - run: npm pack --ignore-scripts + - run: npm run test:package -- ./foreman-sh-*.tgz diff --git a/.github/workflows/publish-npm.yml b/.github/workflows/publish-npm.yml new file mode 100644 index 0000000..51e30f8 --- /dev/null +++ b/.github/workflows/publish-npm.yml @@ -0,0 +1,38 @@ +name: Publish npm +on: + workflow_dispatch: + +permissions: + contents: read + id-token: write + +concurrency: + group: npm-publish-${{ github.ref }} + cancel-in-progress: false + +jobs: + publish: + if: github.repository == 'fatihguner/foreman' && github.ref_type == 'tag' + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 + - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6 + with: + node-version: 24 + registry-url: https://registry.npmjs.org + package-manager-cache: false + - run: npm ci --ignore-scripts + - run: npm run build + - run: npm run build:plugins + - run: npm run check + - name: Verify tag, manifests and generated files + run: | + npm run check:release -- --tag "$GITHUB_REF_NAME" + git diff --exit-code + test -z "$(git ls-files --others --exclude-standard)" + - run: npm pack --ignore-scripts + - run: npm run test:package -- ./foreman-sh-*.tgz + - name: Publish the verified package using npm trusted publishing + run: | + NPM_DIST_TAG=$(node -p "require('./package.json').publishConfig.tag") + npm publish ./foreman-sh-*.tgz --ignore-scripts --access public --provenance --tag "$NPM_DIST_TAG" diff --git a/.github/workflows/validate-skills.yml b/.github/workflows/validate-skills.yml index 71823ad..d38905d 100644 --- a/.github/workflows/validate-skills.yml +++ b/.github/workflows/validate-skills.yml @@ -1,280 +1,18 @@ -name: Validate Skills +name: Content Validation on: - push: - paths: ['.claude/skills/**/*.md'] pull_request: - paths: ['.claude/skills/**/*.md'] - + paths: ['.claude/**', 'lib/content.js', 'scripts/validate*', 'package*.json'] permissions: contents: read - jobs: - validate-changed-skills: - name: Validate Changed Skills + validate: runs-on: ubuntu-latest steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 + - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 + - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4 with: - fetch-depth: 0 - - - name: Identify changed skill files - id: changed - run: | - if [ "${{ github.event_name }}" = "pull_request" ]; then - BASE=${{ github.event.pull_request.base.sha }} - HEAD=${{ github.event.pull_request.head.sha }} - else - BASE=${{ github.event.before }} - HEAD=${{ github.sha }} - fi - - CHANGED=$(git diff --name-only --diff-filter=ACMR "$BASE" "$HEAD" -- '.claude/skills/**/*.md' | grep -v '_schema/' || true) - echo "files<> "$GITHUB_OUTPUT" - echo "$CHANGED" >> "$GITHUB_OUTPUT" - echo "EOF" >> "$GITHUB_OUTPUT" - - if [ -z "$CHANGED" ]; then - echo "No skill files changed (schema-only changes)." - echo "skip=true" >> "$GITHUB_OUTPUT" - else - echo "Changed skill files:" - echo "$CHANGED" - echo "skip=false" >> "$GITHUB_OUTPUT" - fi - - - name: Validate frontmatter on changed skills - if: steps.changed.outputs.skip != 'true' - run: | - EXIT_CODE=0 - REQUIRED_FIELDS=("name" "description" "version" "category" "stage" "tags" "related_skills" "complexity" "author") - - while IFS= read -r file; do - [ -z "$file" ] && continue - [ ! -f "$file" ] && continue - - echo "Validating: $file" - - # Check frontmatter exists - FIRST_LINE=$(head -1 "$file") - if [ "$FIRST_LINE" != "---" ]; then - echo "::error file=$file::Missing YAML frontmatter" - EXIT_CODE=1 - continue - fi - - # Extract frontmatter - FRONTMATTER=$(sed -n '1,/^---$/p' "$file" | tail -n +2 | head -n -1) - - # Check required fields - for field in "${REQUIRED_FIELDS[@]}"; do - if ! echo "$FRONTMATTER" | grep -q "^${field}:"; then - echo "::error file=$file::Missing required frontmatter field: $field" - EXIT_CODE=1 - fi - done - done <<< "${{ steps.changed.outputs.files }}" - - if [ $EXIT_CODE -eq 0 ]; then - echo "All changed skills have valid frontmatter." - fi - exit $EXIT_CODE - - - name: Check for prohibited phrases in changed skills - if: steps.changed.outputs.skip != 'true' - run: | - EXIT_CODE=0 - - PROHIBITED_PHRASES=( - "In today's fast-paced" - "In today's rapidly" - "Let's dive in" - "Let's explore" - "In this skill, you will learn" - "Without further ado" - "It's important to note that" - "At the end of the day" - ) - - while IFS= read -r file; do - [ -z "$file" ] && continue - [ ! -f "$file" ] && continue - - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if grep -qi "$phrase" "$file"; then - LINE=$(grep -n "$phrase" "$file" | head -1) - echo "::error file=$file::Prohibited phrase: \"$phrase\" — $LINE" - EXIT_CODE=1 - fi - done - done <<< "${{ steps.changed.outputs.files }}" - - if [ $EXIT_CODE -eq 0 ]; then - echo "No prohibited phrases found in changed skills." - fi - exit $EXIT_CODE - - - name: Check required body sections in changed skills - if: steps.changed.outputs.skip != 'true' - run: | - EXIT_CODE=0 - - REQUIRED_SECTIONS=( - "Application Prompts" - "Anti-Patterns" - "Related Skills" - ) - - while IFS= read -r file; do - [ -z "$file" ] && continue - [ ! -f "$file" ] && continue - - # Extract body (everything after frontmatter) - BODY=$(sed '1,/^---$/{ /^---$/!d; /^---$/d; }' "$file" | sed '1,/^---$/d') - - for section in "${REQUIRED_SECTIONS[@]}"; do - if ! echo "$BODY" | grep -qi "## .*${section}"; then - echo "::warning file=$file::Missing recommended section: $section" - fi - done - done <<< "${{ steps.changed.outputs.files }}" - - exit $EXIT_CODE - - check-skill-refs: - name: Check Related Skills References - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - with: - fetch-depth: 0 - - - name: Identify changed skill files - id: changed - run: | - if [ "${{ github.event_name }}" = "pull_request" ]; then - BASE=${{ github.event.pull_request.base.sha }} - HEAD=${{ github.event.pull_request.head.sha }} - else - BASE=${{ github.event.before }} - HEAD=${{ github.sha }} - fi - - CHANGED=$(git diff --name-only --diff-filter=ACMR "$BASE" "$HEAD" -- '.claude/skills/**/*.md' | grep -v '_schema/' || true) - echo "files<> "$GITHUB_OUTPUT" - echo "$CHANGED" >> "$GITHUB_OUTPUT" - echo "EOF" >> "$GITHUB_OUTPUT" - - if [ -z "$CHANGED" ]; then - echo "skip=true" >> "$GITHUB_OUTPUT" - else - echo "skip=false" >> "$GITHUB_OUTPUT" - fi - - - name: Validate related_skills references - if: steps.changed.outputs.skip != 'true' - run: | - EXIT_CODE=0 - - # Build index of all skill names from frontmatter - declare -A SKILL_NAMES - while IFS= read -r -d '' skill_file; do - SKILL_NAME=$(sed -n '/^---$/,/^---$/{ /^name:/{ s/^name: *//; s/^"//; s/"$//; p; } }' "$skill_file") - if [ -n "$SKILL_NAME" ]; then - SKILL_NAMES["$SKILL_NAME"]=1 - fi - done < <(find .claude/skills -name "*.md" -not -path "*/_schema/*" -type f -print0) - - echo "Indexed ${#SKILL_NAMES[@]} skill names." - - # Check references in changed files - while IFS= read -r file; do - [ -z "$file" ] && continue - [ ! -f "$file" ] && continue - - # Extract related_skills list - IN_RELATED=false - while IFS= read -r line; do - if echo "$line" | grep -q "^related_skills:"; then - IN_RELATED=true - continue - fi - if $IN_RELATED; then - if echo "$line" | grep -q "^ - "; then - REF=$(echo "$line" | sed 's/^ - //; s/^"//; s/"$//') - if [ -z "${SKILL_NAMES[$REF]+_}" ]; then - echo "::error file=$file::Broken related_skills reference: $REF" - EXIT_CODE=1 - fi - else - IN_RELATED=false - fi - fi - done < <(sed -n '1,/^---$/{ /^---$/!p }' "$file"; sed -n '/^---$/,/^---$/p' "$file") - done <<< "${{ steps.changed.outputs.files }}" - - if [ $EXIT_CODE -eq 0 ]; then - echo "All related_skills references are valid." - fi - exit $EXIT_CODE - - verify-category-match: - name: Verify Category-Directory Match - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 - with: - fetch-depth: 0 - - - name: Identify changed skill files - id: changed - run: | - if [ "${{ github.event_name }}" = "pull_request" ]; then - BASE=${{ github.event.pull_request.base.sha }} - HEAD=${{ github.event.pull_request.head.sha }} - else - BASE=${{ github.event.before }} - HEAD=${{ github.sha }} - fi - - CHANGED=$(git diff --name-only --diff-filter=ACMR "$BASE" "$HEAD" -- '.claude/skills/**/*.md' | grep -v '_schema/' || true) - echo "files<> "$GITHUB_OUTPUT" - echo "$CHANGED" >> "$GITHUB_OUTPUT" - echo "EOF" >> "$GITHUB_OUTPUT" - - if [ -z "$CHANGED" ]; then - echo "skip=true" >> "$GITHUB_OUTPUT" - else - echo "skip=false" >> "$GITHUB_OUTPUT" - fi - - - name: Check category matches directory - if: steps.changed.outputs.skip != 'true' - run: | - EXIT_CODE=0 - - while IFS= read -r file; do - [ -z "$file" ] && continue - [ ! -f "$file" ] && continue - - # Extract directory name (category directory) - DIR_CATEGORY=$(echo "$file" | sed 's|.claude/skills/||' | cut -d'/' -f1) - - # Extract category from frontmatter - FM_CATEGORY=$(sed -n '/^---$/,/^---$/{ /^category:/{ s/^category: *//; s/^"//; s/"$//; p; } }' "$file") - - if [ -z "$FM_CATEGORY" ]; then - echo "::error file=$file::No category field in frontmatter" - EXIT_CODE=1 - elif [ "$DIR_CATEGORY" != "$FM_CATEGORY" ]; then - echo "::error file=$file::Category mismatch — frontmatter says '$FM_CATEGORY' but file is in '$DIR_CATEGORY/' directory" - EXIT_CODE=1 - fi - done <<< "${{ steps.changed.outputs.files }}" - - if [ $EXIT_CODE -eq 0 ]; then - echo "All changed skills have matching category and directory." - fi - exit $EXIT_CODE + node-version: 22 + cache: npm + - run: npm ci --ignore-scripts + - run: npm run validate + - run: node --test tests/content.test.js diff --git a/.gitignore b/.gitignore index 8788db9..a1cb8fc 100644 --- a/.gitignore +++ b/.gitignore @@ -38,7 +38,6 @@ temp/ # Codex-generated skills directory (built from .claude/skills/) /skills/ -# OpenClaw plugin — compiled TS output (OpenClaw uses jiti for runtime TS) -*.js -*.js.map -*.d.ts +# Runtime state (never commit entrepreneur data) +/memory/ +/.foreman/ diff --git a/.npmignore b/.npmignore index ed5defd..b3645cb 100644 --- a/.npmignore +++ b/.npmignore @@ -1,36 +1,9 @@ -# Only ship bin/, .claude/, and CLAUDE.md (defined in package.json "files") -# This file excludes everything else from the npm package - -# Development -scripts/ -docs/ -examples/ -assets/ -openclaw-templates/ - -# Platform-specific (not needed for npm install) -.codex-plugin/ -.claude-plugin/ -.agents/ -/skills/ -openclaw.plugin.json -index.ts - -# Project files -.github/ -.editorconfig -.gitignore -.gitattributes -CONTRIBUTING.md -CODE_OF_CONDUCT.md -SECURITY.md -CHANGELOG.md -VISION.md -README.md -LICENSE - -# OS and IDE -.DS_Store -*.swp -.vscode/ -.idea/ +# package.json "files" is the authoritative distribution allowlist. +# Runtime state and local configuration are never release artifacts. +node_modules/ +.foreman/ +memory/ +.env +.env.* +.claude/settings.local.json +*.log diff --git a/CHANGELOG.md b/CHANGELOG.md index 9aa6dd3..0ed0155 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/). No unreleased changes. +## [1.1.0-rc.1] - 2026-09-05 + +Public release candidate for the cross-platform runtime and packaging update. + +### Added +- A working npm CLI, compiled OpenClaw adapter with 10 tools, 159 packaged skills (including the router), and 46 registered Claude commands. +- Shared persistent profiles, implementation tasks, playbook checkpoints, revision checks, atomic writes and explicit legacy migration. +- Strict YAML and reference validation, 23 automated tests, and Node 22/24 CI on macOS and Linux. +- Portable maintenance commands, staged-content validation and repeatable package installation checks. +- Shared advisory rules and an opt-in live evaluation runner using isolated fictional scenarios and an explicit usage cap. + +### Fixed +- Broken and incorrectly typed content references, missing support templates, ambiguous lookups and path traversal inputs. +- Plugin symlinks that broke packaged installs, missing runtime resources, and the macOS `skill.md`/`SKILL.md` command discovery collision. +- Workspace initialization overwriting existing instructions and tracker output that did not reflect persisted records. + +### Compatibility and release status +- Requires Node 22.19 or newer; OpenClaw 2026.6.1 is the tested SDK baseline. +- Initialization preserves existing files; review and replace old generated files explicitly when upgrading. +- Live advisory quality acceptance is pending. Preliminary answers exposed unsupported causal claims, invented targets and language drift; stronger instructions are included but the complete final regression has not yet passed. Codex project installation is verified; a live Codex model session is still unverified. +- This candidate uses the `next` npm channel when published and does not replace the stable `latest` version. + ## [1.0.0] - 2026-03-29 Initial public release of Foreman -- an AI-powered strategic advisor for entrepreneurs. diff --git a/CLAUDE.md b/CLAUDE.md index e4d7928..eb98ce3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,5 +1,7 @@ # Foreman — Project Context +Before advising or running any Foreman command, read `.claude/RUNTIME.md` and `.claude/policies/advisory.md`. Resolve content through `.claude/catalog.json`. These files define the current storage, routing and advisory contract; older examples below describe the conceptual architecture. Persist confirmed preferences, tasks and checkpoints through the bundled runtime and report only successful writes. + Foreman is an open-source, AI-powered strategic advisor for entrepreneurs. It uses a layered architecture of Skills, Agents, Hooks, Memory, Diagnostics, Playbooks, Commands, and Output Templates to deliver contextual, framework-driven guidance. The project lives at foreman.sh and ships as a public GitHub repository. ## Architecture Overview @@ -39,11 +41,11 @@ Entrepreneur Input 5. **Hooks** (`.claude/hooks/`) — 17 trigger definitions (8 high-priority, 8 medium/low, 1 research) that classify natural-language input and route to diagnostics, skills, or playbooks. 6. **Agents** (`.claude/agents/`) — 6 AI agent definitions: orchestrator (central brain), diagnostic (triage), skill-executor (framework application), playbook-runner (multi-step conductor), output (formatting), memory (context persistence). 7. **Memory** (`.claude/memory/`) — 5-layer persistence system: identity (yearly), company (monthly), history (append-only), active (weekly), session (ephemeral). Schema + YAML templates. -8. **Commands** (`.claude/commands/`) — ~45 commands across 13 command files: navigation (7), execution (5), memory (8), playbook (5), output (3), meta (5). +8. **Commands** (`.claude/commands/`) — 46 registered commands generated from 13 guides; exact names are recorded in `.claude/catalog.json`. ### Tooling & Modes -9. **Scripts** (`scripts/`) — 21 utility scripts: validation (7), content creation (5), analysis (3), maintenance (4), community (2). +9. **Scripts** (`scripts/`) — 24 portable shell entry points backed by shared Node modules. 10. **Solo Mode** (`.claude/solo-mode/`) — Complete solopreneur adaptation layer: SOLO.md (master instruction), skill relevance scoring (158 skills), audience remapping (48 templates), diagnostic/playbook/hook adaptations (56 items). Activated via `/solo`. 11. **Stoic Mode** (`.claude/stoic-mode/`) — Philosophical depth layer that frames all system responses through Stoic principles (dichotomy of control, cardinal virtues, premeditatio malorum, amor fati). Does not change WHAT is delivered — changes HOW it is framed. Activated via `/stoic on`. Can combine with Solo Mode. 12. **Language Mode** (`.claude/language-mode/`) — Complete output language switch. All responses delivered in the specified language while internal processing remains English. Supports any language the model speaks fluently. Activated via `/language [code]`. Persists across sessions. Combines with Solo and Stoic modes. @@ -52,9 +54,9 @@ Entrepreneur Input 15. **Custom Research Prompts** (`.claude/research/`) — 18 structured research guides teaching entrepreneurs HOW to gather data needed for frameworks: market-sizing-worksheet, competitor-research-template, customer-interview-guide, data-collection-plan, pricing-research-guide, due-diligence-research, user-testing-protocol, industry-mapping-guide. Each guide: what to collect, where to find it, how to interpret it, which skills it feeds into. Accessible via `/research` command. 16. **Board Simulation** (`.claude/simulation/`) — Adversarial role-play system for practicing board presentations, investor pitches, and due diligence sessions. 5 board personas, 5-dimension scoring framework, post-simulation diagnostic, memory persistence. Activated via `/simulate` command. 17. **Organizational Politics Navigation** (`.claude/org-politics/`) — Stakeholder dynamics management system. Maps power structures, diagnoses resistance, builds coalitions, designs influence strategies. Includes 2 diagnostics (stakeholder-resistance, power-dynamics), 1 playbook (organizational-alignment), 3 templates (influence-map, resistance-plan, coalition-plan), and 4 commands (`/stakeholders`, `/power-map`, `/resistance`, `/coalition`). Integrates with simulation for adversarial practice. -18. **Claude Code Plugin Marketplace** (`.claude-plugin/marketplace.json` + `plugins/foreman/`) — Plugin marketplace for Claude Code. Users install via `/plugin marketplace add fatihguner/foreman` → `/plugin install foreman@foreman-marketplace`. 158 skills exposed as symlinks to `.claude/skills/`. -19. **Codex Plugin** (`.codex-plugin/`) — OpenAI Codex plugin manifest and build system. `plugin.json` manifest defines the plugin identity and component paths. `scripts/build-codex.sh` transforms `.claude/skills/` into Codex-compatible `skills/skill-name/SKILL.md` format. Generated `skills/` directory is gitignored. Marketplace config at `.agents/plugins/marketplace.json`. -19. **OpenClaw Plugin** — Native OpenClaw plugin (`openclaw.plugin.json` + `package.json` + `index.ts`). Registers 7 agent tools (apply_skill, diagnose, run_playbook, list_skills, research, simulate, track) that read from `.claude/` at runtime. Claude bundle fallback at `.claude-plugin/plugin.json`. +18. **Claude Code Plugin Marketplace** (`.claude-plugin/marketplace.json` + `plugins/foreman/`) — Plugin marketplace for Claude Code. Users install via `/plugin marketplace add fatihguner/foreman` → `/plugin install foreman@foreman-marketplace`. 158 framework skills and one router skill are generated as ordinary files with a complete bundled content tree. +19. **Codex Plugin** (`.codex-plugin/`) — OpenAI Codex plugin manifest and build system. `plugin.json` manifest defines the plugin identity and component paths. `scripts/build-codex.sh` generates the shared `plugins/foreman/skills//SKILL.md` bundle and its content resources. Marketplace config at `.agents/plugins/marketplace.json`. +19. **OpenClaw Plugin** — Native OpenClaw plugin (`openclaw.plugin.json` + `package.json` + compiled `dist/index.js`). Registers 10 agent tools (apply_skill, diagnose, run_playbook, list_skills, research, simulate, track, profile, update_task, resume) that read from `.claude/` at runtime. Claude bundle fallback at `.claude-plugin/plugin.json`. 20. **OpenClaw Templates** (`openclaw-templates/`) — 6 workspace templates (SOUL, IDENTITY, AGENTS, BOOT, BOOTSTRAP, HEARTBEAT) that define Foreman's personality and behavior when running as an OpenClaw agent. Users copy to workspace root. CLI scripts: `openclaw-setup.sh` (installation), `openclaw-build.sh` (validation). 21. **Schemas** — Template files across `_schema/` directories defining the structure for skills, diagnostics, playbooks, hooks, output templates, agents, commands, memory, industry packs, and research guides. @@ -118,25 +120,25 @@ When generating multiple skills, apply deliberate variation across these dimensi 20 multi-step recipes in `playbooks/`. Each has: trigger diagnostics, 4-7 steps (each with skill, purpose, output, checkpoint), decision points, final deliverables, common pitfalls, adaptation notes. Schema: `.claude/playbooks/_schema/playbook-template.md`. ### Hooks -16 trigger definitions in `hooks/`. Each has: 10-15 trigger patterns (natural language), intent classification, routing logic (decision tree), disambiguation rules, example conversations. Schema: `.claude/hooks/_schema/hook-template.md`. +17 trigger definitions in `.claude/hooks/`. Each has: 10-15 trigger patterns (natural language), intent classification, routing logic (decision tree), disambiguation rules, example conversations. Schema: `.claude/hooks/_schema/hook-template.md`. ### Output Templates 48 fill-in-the-blank templates in `output-templates/`. Organized by audience: investor (10), board (7), team (13), self (10), client (8). Each has: name, description, audience, applicable_skills, format, fill-in placeholders. Schema: `.claude/output-templates/_schema/output-template.md`. ### Agents -6 agent definitions in `agents/`. Roles: orchestrator, diagnostic, skill-executor, playbook-runner, output, memory. Each has: role, responsibilities, activation conditions, workflow (pseudocode), interactions, decision rules, error handling, example flows. Schema: `.claude/agents/_schema/agent-template.md`. +6 agent definitions in `agents/`. Roles: orchestrator, diagnostic, skill-executor, playbook-runner, output, memory. Each has: role, responsibilities, activation conditions, workflow (pseudocode), interactions, decision rules, error handling, example flows. Schema: `.claude/_schema/agents/agent-template.md`. ### Memory 5-layer system in `memory/`. Layers: identity (yearly), company (monthly), history (append-only), active (weekly), session (ephemeral). Schema: `.claude/memory/_schema/memory-schema.md`. Templates: `.claude/memory/_template/*.yaml`. ### Commands -33 commands in 6 groups in `commands/`. Groups: navigation (7), execution (5), memory (8), playbook (5), output (3), meta (5). Schema: `.claude/commands/_schema/command-template.md`. +46 registered commands generated from 13 command guides in `.claude/commands/`. The exact host-safe command map is in `.claude/catalog.json`. Schema: `.claude/_schema/commands/command-template.md`. ### Scripts -21 bash scripts in `scripts/`. Categories: validation (7), content creation (5), analysis (3), maintenance (4), community (2). All executable, with --help flags. +24 portable shell entry points in `scripts/`, backed by shared Node modules. Each supports `--help`. ### Solo Mode -5 files in `solo/`. Activates via `/solo` command. Adapts all layers for solopreneurs: skill relevance scoring, audience remapping, diagnostic/playbook/hook adaptations. Config-driven — no content duplication. +4 files in `.claude/solo-mode/`. Activates via `/solo` command. Adapts all layers for solopreneurs: skill relevance scoring, audience remapping, diagnostic/playbook/hook adaptations. Config-driven — no content duplication. ## Writing Style Guide @@ -207,7 +209,7 @@ foreman/ │ │ └── _schema/diagnostic-template.md │ ├── playbooks/ # 20 multi-step recipes │ │ └── _schema/playbook-template.md -│ ├── hooks/ # 16 trigger definitions +│ ├── hooks/ # 17 trigger definitions │ │ └── _schema/hook-template.md │ ├── agents/ # 6 agent definitions │ │ └── _schema/agent-template.md @@ -280,7 +282,7 @@ foreman/ │ │ ├── organizational-alignment-playbook.md │ │ └── templates/ (6 templates + schema) │ └── settings.local.json -├── scripts/ # 21 utility scripts (dev tooling) +├── scripts/ # 24 shell entry points (dev tooling) │ ├── validate-*.sh (7) │ ├── new-*.sh (5) │ ├── stats.sh, orphan-check.sh, coverage-report.sh @@ -319,7 +321,7 @@ foreman/ ### Adding a New Source 1. Read the source material and identify discrete, actionable frameworks/methods -2. Create a new category directory under `skills/` with a kebab-case slug +2. Create a new category directory under `.claude/skills/` with a kebab-case slug 3. Register the source in the project documentation 4. Generate skills following the schema and differentiation strategy 5. Anonymize all author references before committing @@ -385,3 +387,7 @@ foreman/ - **Schemas:** 12 - **Examples:** 8 end-to-end walkthroughs - **Total Files:** 443+ + + +Current catalog: 6 agent entries; 9 command entries; 24 diagnostic entries; 17 hook entries; 1 implementation entries; 58 template entries; 21 playbook entries; 18 research entries; 10 persona entries; 158 skill entries. + diff --git a/README.md b/README.md index 0fea38b..728c5cd 100644 --- a/README.md +++ b/README.md @@ -127,8 +127,8 @@ Foreman runs wherever AI agents run: |---|---|---| | **Claude Code** | Native | `.claude/` directory: skills, commands, hooks, agents, memory | | **Claude Code Plugin** | Marketplace | `/plugin marketplace add fatihguner/foreman` → `/plugin install foreman@foreman-marketplace` | -| **Codex** | Plugin | `.codex-plugin/plugin.json` + generated `skills/` via `build-codex.sh` | -| **OpenClaw** | Native plugin | `openclaw.plugin.json` + `index.ts` registering 7 agent tools | +| **Codex** | Plugin | `.codex-plugin/plugin.json` + the shared `plugins/foreman/skills/` bundle | +| **OpenClaw** | Native plugin | `openclaw.plugin.json` + compiled `dist/index.js` registering 10 agent tools | Single source of truth: `.claude/`. Every other platform derives from it. @@ -136,13 +136,27 @@ Single source of truth: `.claude/`. Every other platform derives from it. ## Quickstart -### Install via npm (recommended) +### Try the current release candidate + +**1.1.0-rc.1** includes the new installer, shared state runtime and repaired plugin bundles. It is publicly available as a release candidate while final live advisory quality acceptance is pending. See the [release notes](docs/releases/v1.1.0-rc.1.md) for verification and known limitations. + +Install the GitHub release package directly (Node 22.19 or later): + +```bash +npx --yes --package=https://github.com/fatihguner/foreman/releases/download/v1.1.0-rc.1/foreman-sh-1.1.0-rc.1.tgz foreman-sh init +``` + +Add `--platform codex` for Codex, or `--platform all` for both Claude and Codex. Foreman is MIT-licensed and free to install; your AI host account and model usage are separate. + +### npm registry ```bash npx foreman-sh init ``` -That's it. Foreman installs `.claude/` and `CLAUDE.md` into your current directory. Open Claude Code and start talking: +The unversioned npm command selects the existing stable registry release, which does not include this candidate's fixes. Use the GitHub package above for this candidate until npm publication is confirmed. + +The new installer adds `.claude/` and `CLAUDE.md` to your current directory and preserves existing files. Use `--workspace /path/to/project` to choose a directory or `--platform codex` to install project skills under `.agents/skills/`. Open Claude Code and start talking: > "My SaaS churn rate is 5.2% and I'm preparing for Series A. What should I focus on?" @@ -158,6 +172,9 @@ That's it. Foreman installs `.claude/` and `CLAUDE.md` into your current directo ```bash git clone https://github.com/fatihguner/foreman.git cd foreman +npm ci --ignore-scripts +npm run build +npm run build:plugins ``` ### Codex @@ -165,7 +182,10 @@ cd foreman ```bash git clone https://github.com/fatihguner/foreman.git cd foreman -./scripts/build-codex.sh --clean +npm ci --ignore-scripts +npm run build +npm run build:plugins +node bin/cli.js init --platform codex --workspace /path/to/your/project ``` ### OpenClaw @@ -173,6 +193,7 @@ cd foreman ```bash git clone https://github.com/fatihguner/foreman.git cd foreman +npm ci --ignore-scripts ./scripts/openclaw-setup.sh ``` @@ -180,18 +201,22 @@ cd foreman ## Key Commands +These are Claude project commands. Claude plugin commands use `/foreman:apply`, `/foreman:solo`, and the same namespace for other commands. Host conflicts use prefixes such as `/foreman-run`, `/foreman-skill`, `/foreman-resume`, `/foreman-context` and `/foreman-help`. In Codex, use `$foreman` followed by the operation. The generated command map is in `.claude/catalog.json`. + +Preferences and implementation tasks persist under `.foreman//state.json` through the bundled runtime. Keep that directory out of version control. See [runtime behavior](.claude/RUNTIME.md) and [development and verification](docs/development.md). + | Command | What It Does | |---|---| | `/skills` | List all 158 skills, filter by category or stage | | `/apply [skill]` | Apply a framework to your context | | `/diagnose [area]` | Run a diagnostic triage | -| `/run [playbook]` | Start a multi-step playbook | +| `/foreman-run [playbook]` | Start a multi-step playbook | | `/track` | View implementation progress | | `/simulate board` | Practice your board presentation | | `/research [topic]` | Get a data collection guide | -| `/context` | View your stored company context | +| `/foreman-context` | View your stored company context | | `/sector [name]` | Activate an industry pack | -| `/help` | See all commands | +| `/foreman-help` | See all commands | --- @@ -248,7 +273,7 @@ foreman/ │ ├── hooks/ # 17 natural language triggers │ ├── agents/ # 6 orchestration agents │ ├── memory/ # 5-layer persistence system -│ ├── commands/ # 13 command files (~45 commands) +│ ├── commands/ # 13 guides + 46 generated commands │ ├── industry-packs/ # 9 sector-specific overlay packs │ ├── research/ # 18 data collection guides │ ├── implementation/ # Tracking + support system diff --git a/bin/cli.js b/bin/cli.js new file mode 100755 index 0000000..302adb3 --- /dev/null +++ b/bin/cli.js @@ -0,0 +1,21 @@ +#!/usr/bin/env node +import path from 'node:path'; +import { initWorkspace } from '../dist/lib/distribution.js'; +import { runStateCLI } from '../dist/lib/state-cli.js'; +const root = path.resolve(import.meta.dirname,'..'); +const args = process.argv.slice(2); +try { + if (!args.length || (args[0] !== 'state' && args.includes('--help')) || args[0] === 'help') { + console.log('Foreman\n foreman-sh init [--workspace DIR] [--platform claude|codex|all]\n foreman-sh state [options]\nExisting workspace files are preserved. Run state --help for state commands.'); + } else if (args[0] === 'init') { + let workspace = process.cwd(), platform = 'claude'; + for (let i=1; i !f.startsWith("_")); -} - -function listDirRecursive(path: string): string[] { - if (!existsSync(path)) return []; - const results: string[] = []; - for (const entry of readdirSync(path)) { - if (entry.startsWith("_")) continue; - const full = join(path, entry); - if (statSync(full).isDirectory()) { - for (const child of readdirSync(full)) { - if (child.startsWith("_")) continue; - if (child.endsWith(".md")) results.push(`${entry}/${child}`); - } - } else if (entry.endsWith(".md")) { - results.push(entry); - } - } - return results; -} - -function fuzzyMatch(needle: string, haystack: string): boolean { - const n = needle.toLowerCase().replace(/[\s_-]+/g, ""); - const h = haystack.toLowerCase().replace(/[\s_-]+/g, ""); - return h.includes(n) || n.includes(h); -} - -function findFile(dir: string, name: string, extensions = [".md", ".yaml", ".yml"]): string | null { - if (!existsSync(dir)) return null; - - // Direct match first - for (const ext of extensions) { - const direct = join(dir, name + ext); - if (existsSync(direct)) return direct; - const withSuffix = join(dir, name + "-diagnosis" + ext); - if (existsSync(withSuffix)) return withSuffix; - } - - // Scan directory for fuzzy match - const entries = readdirSync(dir); - for (const entry of entries) { - if (entry.startsWith("_")) continue; - const full = join(dir, entry); - if (statSync(full).isDirectory()) { - // Recurse into subdirectories (e.g., skills/frameworks/) - const sub = findFile(full, name, extensions); - if (sub) return sub; - } else if (fuzzyMatch(name, entry)) { - return full; - } - } - return null; -} - -function textResult(text: string) { - return { content: [{ type: "text" as const, text }] }; -} - -function errorResult(message: string) { - return textResult(`Error: ${message}`); -} - -// --------------------------------------------------------------------------- -// Plugin Entry -// --------------------------------------------------------------------------- - -export default definePluginEntry((api) => { - - // ========================================================================= - // 1. foreman_apply_skill — Apply a specific business framework skill - // ========================================================================= - - api.registerTool( - "foreman_apply_skill", - { - description: - "Apply a Foreman business framework skill. Returns the full skill content (framework explanation, application prompts, use cases, anti-patterns, stage guidance) for the LLM to apply to the entrepreneur's context. 158 skills across 12 categories: frameworks, leadership, writing, ai-leadership, game-theory, stoic, storytelling, negotiation, people, creative, thinking, decisions.", - parameters: Type.Object({ - skill: Type.String({ description: "Skill name or keyword to search for (e.g., 'okr', 'pricing-power', 'swot-analysis')" }), - context: Type.Optional(Type.String({ description: "Entrepreneur's situation context to tailor the skill application" })), - }), - }, - async ({ skill, context }) => { - const skillsDir = join(CLAUDE_DIR, "skills"); - const found = findFile(skillsDir, skill); - - if (!found) { - const available = listDirRecursive(skillsDir); - return errorResult( - `Skill "${skill}" not found. Available skills (${available.length}):\n${available.join("\n")}` - ); - } - - const content = readFileOr(found, ""); - const preamble = context - ? `Apply the following skill to this context:\n---\n${context}\n---\n\n` - : ""; - return textResult(preamble + content); - } - ); - - // ========================================================================= - // 2. foreman_diagnose — Run a diagnostic triage - // ========================================================================= - - api.registerTool( - "foreman_diagnose", - { - description: - "Run a Foreman diagnostic to identify root causes through structured triage questions. Areas include: revenue, team, growth, product-market-fit, fundraising, pricing, customer-churn, hiring, leadership, culture, cofounder-conflict, operational-chaos, competitive-threat, innovation, communication, decision-paralysis, market-entry, partnership, negotiation, strategic-drift.", - parameters: Type.Object({ - area: Type.String({ - description: "Diagnostic area (e.g., 'revenue', 'team', 'growth', 'pricing', 'hiring', 'fundraising')", - }), - }), - }, - async ({ area }) => { - const diagDir = join(CLAUDE_DIR, "diagnostics"); - const found = findFile(diagDir, area); - - if (!found) { - const available = listDir(diagDir) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace("-diagnosis.md", "").replace(".md", "")); - return errorResult( - `Diagnostic "${area}" not found. Available diagnostics:\n${available.join("\n")}` - ); - } - - const content = readFileOr(found, ""); - return textResult(content); - } - ); - - // ========================================================================= - // 3. foreman_run_playbook — Start a multi-step playbook - // ========================================================================= - - api.registerTool( - "foreman_run_playbook", - { - description: - "Start a Foreman playbook — a multi-step recipe that chains skills sequentially with checkpoints and decision points. Playbooks include: fundraising, product-market-fit, launch, pivot, scaling, crisis, team-rebuild, competitive-response, strategy-reset, innovation-sprint, first-100-customers, pricing-strategy, partnership, negotiation, personal-brand, board-formation, remote-team, founder-transition, acquisition-evaluation, international-expansion.", - parameters: Type.Object({ - playbook: Type.String({ - description: "Playbook name (e.g., 'fundraising', 'launch', 'pivot', 'pricing-strategy')", - }), - }), - }, - async ({ playbook }) => { - const playbookDir = join(CLAUDE_DIR, "playbooks"); - const found = findFile(playbookDir, playbook); - - if (!found) { - // Try appending -playbook - const withSuffix = findFile(playbookDir, playbook + "-playbook"); - if (withSuffix) { - const content = readFileOr(withSuffix, ""); - return textResult(content); - } - - const available = listDir(playbookDir) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace("-playbook.md", "").replace(".md", "")); - return errorResult( - `Playbook "${playbook}" not found. Available playbooks:\n${available.join("\n")}` - ); - } - - const content = readFileOr(found, ""); - return textResult(content); - } - ); - - // ========================================================================= - // 4. foreman_list_skills — List available skills with optional filtering - // ========================================================================= - - api.registerTool( - "foreman_list_skills", - { - description: - "List all available Foreman skills, optionally filtered by category. Returns skill names organized by category. Categories: frameworks (50), leadership (28), writing (13), ai-leadership (9), game-theory (7), stoic (12), storytelling (8), negotiation (4), people (8), creative (8), thinking (6), decisions (5).", - parameters: Type.Object({ - category: Type.Optional( - Type.String({ - description: "Filter by category (e.g., 'frameworks', 'leadership', 'writing'). Omit to list all.", - }) - ), - }), - }, - async ({ category }) => { - const skillsDir = join(CLAUDE_DIR, "skills"); - if (!existsSync(skillsDir)) { - return errorResult("Skills directory not found at .claude/skills/"); - } - - const categories = listDir(skillsDir).filter((d) => - statSync(join(skillsDir, d)).isDirectory() - ); - - if (category) { - const target = categories.find( - (c) => c.toLowerCase() === category.toLowerCase() - ); - if (!target) { - return errorResult( - `Category "${category}" not found. Available: ${categories.join(", ")}` - ); +import { definePluginEntry } from 'openclaw/plugin-sdk/plugin-entry'; +import { Type } from '@sinclair/typebox'; +import path from 'node:path'; +import { createHash } from 'node:crypto'; +import { invoke, TOOL_SPECS } from './lib/tools.js'; + +const root = path.basename(import.meta.dirname) === 'dist' ? path.resolve(import.meta.dirname,'..') : import.meta.dirname; +export default definePluginEntry({ + id:'foreman', name:'Foreman', description:'Strategic advisory content and persistent implementation tracking.', + register(api) { + api.registerTool(ctx => TOOL_SPECS.map(spec => ({ + name:spec.name, label:spec.name, description:spec.description, + parameters:Type.Unsafe>(spec.parameters), + async execute(_callId:string, params:Record) { + try { + const scope = ctx.requesterSenderId ? createHash('sha256').update(`${ctx.agentId || 'default'}:${ctx.requesterSenderId}`).digest('hex').slice(0,32) : ctx.agentId || 'default'; + const result = invoke(root,spec.name,params,{workspace:ctx.workspaceDir,founder:scope,defaults:api.pluginConfig || {}}); + return {content:[{type:'text' as const,text:typeof result === 'string' ? result : JSON.stringify(result,null,2)}],details:{ok:true}}; + } catch(e) { + return {content:[{type:'text' as const,text:`Error: ${e instanceof Error ? e.message : String(e)}`}],isError:true,details:{ok:false}}; } - const skills = listDir(join(skillsDir, target)) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace(".md", "")); - return textResult( - `## ${target} (${skills.length} skills)\n\n${skills.map((s) => `- ${s}`).join("\n")}` - ); } - - // List all categories with skill counts - const lines: string[] = ["## Foreman Skills Library\n"]; - let total = 0; - for (const cat of categories) { - const skills = listDir(join(skillsDir, cat)) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace(".md", "")); - total += skills.length; - lines.push(`### ${cat} (${skills.length})`); - lines.push(skills.map((s) => `- ${s}`).join("\n")); - lines.push(""); - } - lines.unshift(`Total: ${total} skills across ${categories.length} categories\n`); - return textResult(lines.join("\n")); - } - ); - - // ========================================================================= - // 5. foreman_research — Get a structured research guide - // ========================================================================= - - api.registerTool( - "foreman_research", - { - description: - "Get a Foreman research guide that teaches entrepreneurs how to gather data needed for frameworks. Guides include: market-sizing, competitor-research, customer-interview, data-collection, pricing-research, due-diligence, user-testing, industry-mapping, financial-modeling, regulatory-landscape, survey-design, technology-stack, partnership-research, talent-market, content-strategy, funding-landscape, churn-analysis, brand-perception.", - parameters: Type.Object({ - topic: Type.String({ - description: "Research topic (e.g., 'market-sizing', 'competitor-research', 'pricing-research')", - }), - }), - }, - async ({ topic }) => { - const researchDir = join(CLAUDE_DIR, "research"); - const found = findFile(researchDir, topic); - - if (!found) { - const available = listDir(researchDir) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace(".md", "")); - return errorResult( - `Research guide "${topic}" not found. Available guides:\n${available.join("\n")}` - ); - } - - const content = readFileOr(found, ""); - return textResult(content); - } - ); - - // ========================================================================= - // 6. foreman_simulate — Start a board simulation - // ========================================================================= - - api.registerTool( - "foreman_simulate", - { - description: - "Start a Foreman board simulation for adversarial role-play practice. Supports board presentations, investor pitches, and due diligence sessions. 10 board personas available: skeptic-investor, operational-expert, financial-hawk, industry-veteran, friendly-challenger, legal-counsel, customer-advocate, growth-strategist, technical-advisor, culture-guardian.", - parameters: Type.Object({ - type: Type.Union( - [ - Type.Literal("board"), - Type.Literal("investor-pitch"), - Type.Literal("due-diligence"), - ], - { description: "Simulation type" } - ), - persona: Type.Optional( - Type.String({ - description: "Specific board persona to use (e.g., 'skeptic-investor', 'financial-hawk'). Omit for a mixed panel.", - }) - ), - }), - }, - async ({ type, persona }) => { - const simDir = join(CLAUDE_DIR, "simulation"); - - if (!existsSync(simDir)) { - return errorResult("Simulation directory not found at .claude/simulation/"); - } - - const parts: string[] = []; - - // Load master simulation doc - const masterPath = join(simDir, "SIMULATION.md"); - if (existsSync(masterPath)) { - parts.push(readFileOr(masterPath, "")); - } - - // Load scoring framework - const scoringPath = join(simDir, "simulation-scoring.yaml"); - if (existsSync(scoringPath)) { - parts.push("\n---\n## Scoring Framework\n\n" + readFileOr(scoringPath, "")); - } - - // Load persona if specified - if (persona) { - const personaDir = join(simDir, "board-personas"); - const personaFile = findFile(personaDir, persona); - if (personaFile) { - parts.push("\n---\n## Active Persona\n\n" + readFileOr(personaFile, "")); - } else { - const available = listDir(personaDir) - .filter((f) => f.endsWith(".md")) - .map((f) => f.replace(".md", "")); - parts.push( - `\n---\nPersona "${persona}" not found. Available: ${available.join(", ")}` - ); - } - } - - // Load post-simulation diagnostic - const postDiagPath = join(simDir, "post-simulation-diagnostic.md"); - if (existsSync(postDiagPath)) { - parts.push( - "\n---\n## Post-Simulation Diagnostic\n\n" + readFileOr(postDiagPath, "") - ); - } - - return textResult( - `Simulation type: ${type}\n\n${parts.join("\n")}` - ); - } - ); - - // ========================================================================= - // 7. foreman_track — View implementation tracking - // ========================================================================= - - api.registerTool( - "foreman_track", - { - description: - "View Foreman implementation tracking — the accountability layer that tracks execution of playbook steps and skill recommendations through 6 states (not-started, in-progress, blocked, completed, abandoned, deferred). Includes dashboard, weekly reports, and blocker analysis.", - parameters: Type.Object({ - filter: Type.Optional( - Type.Union( - [ - Type.Literal("all"), - Type.Literal("blocked"), - Type.Literal("in-progress"), - Type.Literal("overdue"), - ], - { - description: - "Filter tracking items. 'all' returns everything, 'blocked' shows blockers, 'in-progress' shows active items, 'overdue' shows missed deadlines. Defaults to 'all'.", - } - ) - ), - }), - }, - async ({ filter }) => { - const implDir = join(CLAUDE_DIR, "implementation"); - - if (!existsSync(implDir)) { - return errorResult( - "Implementation directory not found at .claude/implementation/" - ); - } - - const parts: string[] = []; - const activeFilter = filter || "all"; - - // Load master implementation doc - const masterPath = join(implDir, "IMPLEMENTATION.md"); - if (existsSync(masterPath)) { - parts.push(readFileOr(masterPath, "")); - } - - // Load schema - const schemaPath = join(implDir, "implementation-schema.yaml"); - if (existsSync(schemaPath)) { - parts.push("\n---\n## Tracking Schema\n\n" + readFileOr(schemaPath, "")); - } - - // Load relevant template based on filter - const templatesDir = join(implDir, "templates"); - if (existsSync(templatesDir)) { - if (activeFilter === "all" || activeFilter === "overdue") { - const dashboard = join(templatesDir, "implementation-dashboard.md"); - if (existsSync(dashboard)) { - parts.push("\n---\n## Dashboard Template\n\n" + readFileOr(dashboard, "")); - } - } - if (activeFilter === "all" || activeFilter === "in-progress") { - const weekly = join(templatesDir, "weekly-progress-report.md"); - if (existsSync(weekly)) { - parts.push("\n---\n## Weekly Report Template\n\n" + readFileOr(weekly, "")); - } - } - if (activeFilter === "blocked") { - const blocker = join(templatesDir, "blocker-analysis.md"); - if (existsSync(blocker)) { - parts.push("\n---\n## Blocker Analysis Template\n\n" + readFileOr(blocker, "")); - } - } - } - - // Load support files for blocked items - if (activeFilter === "blocked") { - const supportDir = join(implDir, "support"); - if (existsSync(supportDir)) { - const blockerDiag = join(supportDir, "blocker-diagnosis.md"); - if (existsSync(blockerDiag)) { - parts.push( - "\n---\n## Blocker Diagnosis Guide\n\n" + readFileOr(blockerDiag, "") - ); - } - const stuckProtocols = join(supportDir, "stuck-protocols.yaml"); - if (existsSync(stuckProtocols)) { - parts.push( - "\n---\n## Stuck Protocols\n\n" + readFileOr(stuckProtocols, "") - ); - } - } - } - - return textResult( - `Implementation tracking (filter: ${activeFilter})\n\n${parts.join("\n")}` - ); - } - ); + })), {names:TOOL_SPECS.map(spec=>spec.name)}); + } }); diff --git a/lib/content.js b/lib/content.js new file mode 100644 index 0000000..f7be8a0 --- /dev/null +++ b/lib/content.js @@ -0,0 +1,199 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { parseDocument } from 'yaml'; + +export const STAGES = ['idea', 'validation', 'early-traction', 'growth', 'scale']; +export const LAYERS = { skills: 'skill', 'output-templates': 'template', diagnostics: 'diagnostic', playbooks: 'playbook', hooks: 'hook', agents: 'agent', research: 'research' }; +export const REQUIRED = { + skill: ['name', 'description', 'version', 'category', 'complexity', 'stage', 'tags', 'related_skills', 'author'], + template: ['name', 'description', 'audience', 'applicable_skills', 'format', 'author'], + diagnostic: ['name', 'description', 'entry_symptoms', 'possible_diagnoses', 'routes_to_skills', 'routes_to_templates', 'author'], + playbook: ['name', 'description', 'trigger_diagnostics', 'steps', 'final_outputs', 'estimated_duration', 'complexity', 'stage', 'author'], + hook: ['name', 'description', 'trigger_patterns', 'routes_to', 'priority', 'author'], + agent: ['name', 'description', 'role', 'triggers', 'dependencies', 'inputs', 'outputs', 'author'], + research: ['name', 'description', 'author'], +}; +export const PROHIBITED = ["In today's fast-paced", "In today's rapidly", "Let's dive in", "Let's explore", 'In this skill, you will learn', 'Without further ado', "It's important to note that", 'At the end of the day']; + +export function walk(dir, { schemas = false } = {}) { + if (!fs.existsSync(dir)) throw new Error(`Missing source directory: ${dir}`); + const files = []; + for (const entry of fs.readdirSync(dir, { withFileTypes: true }).sort((a, b) => a.name.localeCompare(b.name))) { + if (entry.isSymbolicLink()) continue; + if (!schemas && entry.name.startsWith('_')) continue; + const full = path.join(dir, entry.name); + if (entry.isDirectory()) files.push(...walk(full, { schemas })); + else if (entry.isFile()) files.push(full); + } + return files; +} + +export function yaml(text, filename = 'YAML') { + const doc = parseDocument(text, { uniqueKeys: true }); + if (doc.errors.length) throw new Error(`${filename}: ${doc.errors.map(e => e.message).join('; ')}`); + return doc.toJS({ maxAliasCount: 50 }); +} + +export function frontmatter(text, filename = 'Markdown') { + const match = text.match(/^---\r?\n([\s\S]*?)\r?\n---(?:\r?\n|$)/); + if (!match) { + if (text.startsWith('---')) throw new Error(`${filename}: Unclosed frontmatter`); + return { data: null, body: text }; + } + const data = yaml(match[1], filename); + if (!data || typeof data !== 'object' || Array.isArray(data)) throw new Error(`${filename}: Frontmatter must be a mapping`); + return { data, body: text.slice(match[0].length), header: match[0] }; +} + +export function kindOf(relative, id = '', data = {}) { + const layer = relative.split('/')[0]; + if (LAYERS[layer]) return LAYERS[layer]; + if (/-diagnos(?:is|tic)$/.test(id)) return 'diagnostic'; + if (id.endsWith('-playbook')) return 'playbook'; + if (data.audience && data.format && Array.isArray(data.applicable_skills)) return 'template'; + if (relative.includes('/templates/')) return 'template'; + if (layer === 'commands') return 'command'; + if (relative.startsWith('simulation/board-personas/')) return 'persona'; + return layer; +} + +export function catalog(root) { + const base = path.resolve(root, '.claude'); + const entries = [], errors = []; + for (const file of walk(base).filter(f => f.endsWith('.md'))) { + const relative = path.relative(base, file).split(path.sep).join('/'); + try { + const text = fs.readFileSync(file, 'utf8'); + const { data, body } = frontmatter(text, relative); + if (!data?.name) continue; + entries.push({ id: data.name, kind: kindOf(relative, data.name, data), category: data.category, file, relative, data, body, text }); + } catch (e) { errors.push(String(e.message)); } + } + const byKey = new Map(); + for (const item of entries) { + const key = `${item.kind}:${item.id}`; + if (byKey.has(key)) errors.push(`${item.relative}: Duplicate identity ${key}`); + else byKey.set(key, item); + } + const aliasFile = path.join(base, 'catalog-aliases.json'); + const aliases = fs.existsSync(aliasFile) ? JSON.parse(fs.readFileSync(aliasFile, 'utf8')) : {}; + return { root: path.resolve(root), base, entries, byKey, aliases, errors }; +} + +export function lookup(cat, kind, input) { + if (typeof input !== 'string' || !input.trim() || /[/.\\\0]/.test(input)) throw new Error('Provide a nonempty catalog name, without a path or extension.'); + const name = input.trim().toLowerCase(); + const items = cat.entries.filter(e => e.kind === kind); + const direct = cat.byKey.get(`${kind}:${name}`); + if (direct) return direct; + const alias = cat.aliases[kind]?.[name]; + if (alias && cat.byKey.has(`${kind}:${alias}`)) return cat.byKey.get(`${kind}:${alias}`); + const normalized = s => s.toLowerCase().replace(/[\s_-]+/g, ''); + const exact = items.filter(e => normalized(e.id) === normalized(name)); + if (exact.length === 1) return exact[0]; + const candidates = items.filter(e => normalized(e.id).includes(normalized(name))); + if (candidates.length === 1) return candidates[0]; + if (candidates.length > 1) throw new Error(`Ambiguous ${kind} "${input}". Choose: ${candidates.map(e => e.id).join(', ')}`); + throw new Error(`Unknown ${kind} "${input}".`); +} + +const REF_FIELDS = { + related_skills: 'skill', routes_to_skills: 'skill', applicable_skills: 'skill', feeds_into_skills: 'skill', + routes_to_templates: 'template', feeds_into_templates: 'template', final_outputs: 'template', + trigger_diagnostics: 'diagnostic', related_diagnostics: 'diagnostic', routes_to_diagnostics: 'diagnostic', + related_playbooks: 'playbook', routes_to_playbooks: 'playbook', + feeds_into_playbooks: 'playbook', applicable_diagnostics: 'diagnostic', +}; +export function references(data) { + const refs = []; + const add = (kind, ref, field) => refs.push({ kind, ref, field }); + function visit(value, field = '') { + if (Array.isArray(value)) { value.forEach((x, i) => visit(x, `${field}[${i}]`)); return; } + if (!value || typeof value !== 'object') return; + if (typeof value.kind === 'string' && 'ref' in value) add(value.kind, value.ref, field); + for (const [key, v] of Object.entries(value)) { + if (key in REF_FIELDS) for (const ref of Array.isArray(v) ? v : [v]) add(REF_FIELDS[key], ref, `${field}.${key}`); + else if (['skill', 'skill_name', 'diagnostic', 'diagnostic_name', 'template', 'template_name'].includes(key) && typeof v === 'string') add(key.replace('_name', ''), v, `${field}.${key}`); + else if (key === 'routes_to' && v && typeof v === 'object') { + for (const [plural, targets] of Object.entries(v)) for (const ref of Array.isArray(targets) ? targets : [targets]) add(({skills:'skill', diagnostics:'diagnostic', playbooks:'playbook', templates:'template',output_templates:'template'})[plural] || plural, ref, `${field}.routes_to.${plural}`); + } else visit(v, field ? `${field}.${key}` : key); + } + } + visit(data); + return refs; +} + +export function markdownLinks(text) { + return [...text.matchAll(/\]\(([^)\s]+)(?:\s+"[^"]*")?\)/g)].map(m => m[1]).filter(x => !/^(?:[a-z]+:|#)/i.test(x)); +} + +export function validate(root, { layer, refsOnly = false } = {}) { + const report = { files: 0, yamlDocuments: 0, references: 0, links: 0, errors: [], warnings: [], counts: {} }; + let cat; + try { cat = catalog(root); } catch (e) { report.errors.push(e.message); return report; } + report.errors.push(...cat.errors); + const layers = layer ? [layer] : Object.keys(LAYERS); + for (const l of layers) { + const dir = path.join(cat.base, l); + if (!fs.existsSync(dir)) { report.errors.push(`Missing source directory: .claude/${l}`); continue; } + const files = walk(dir).filter(f => f.endsWith('.md')); + report.counts[l] = files.length; + if (!files.length) report.errors.push(`Empty source directory: .claude/${l}`); + for (const file of files) { + report.files++; + if (refsOnly) continue; + try { + const text = fs.readFileSync(file, 'utf8'); + const { data, body } = frontmatter(text, file); + if (!data) { report.errors.push(`${file}: Missing YAML frontmatter`); continue; } + for (const key of REQUIRED[LAYERS[l]] || []) if (!(key in data)) report.errors.push(`${file}: Missing field ${key}`); + if (data.draft === true) report.errors.push(`${file}: Unfinished draft`); + if (data.name !== path.basename(file, '.md')) report.errors.push(`${file}: name must match filename`); + if (typeof data.description !== 'string' || !data.description.trim() || data.description.length > 1024) report.errors.push(`${file}: Invalid description`); + if (!/^[a-z0-9]+(?:-[a-z0-9]+)*$/.test(data.name || '')) report.errors.push(`${file}: Invalid name`); + if (!/^# /m.test(body)) report.errors.push(`${file}: Missing body title`); + if (data.complexity && !['basic','intermediate','advanced'].includes(data.complexity)) report.errors.push(`${file}: Invalid complexity`); + if (data.stage && (!Array.isArray(data.stage) || !data.stage.length || data.stage.some(s => !STAGES.includes(s)))) report.errors.push(`${file}: Invalid stage list`); + if (l === 'skills' && data.category !== path.basename(path.dirname(file))) report.errors.push(`${file}: category must match directory`); + if (l === 'skills' && !/^\d+\.\d+\.\d+$/.test(String(data.version))) report.errors.push(`${file}: Invalid version`); + for (const field of new Set(['stage','tags','related_content','entry_symptoms','possible_diagnoses','trigger_patterns','steps','triggers','dependencies','inputs','outputs',...Object.keys(REF_FIELDS)])) if (field in data && !Array.isArray(data[field])) report.errors.push(`${file}: ${field} must be an array`); + if (Array.isArray(data.steps)) for (const step of data.steps) { + if (!step || typeof step !== 'object' || !((typeof step.skill === 'string') || (typeof step.kind === 'string' && typeof step.ref === 'string')) || typeof step.purpose !== 'string' || typeof step.output !== 'string') report.errors.push(`${file}: Each step requires a typed target, purpose, and output`); + } + if ('routes_to' in data && (!data.routes_to || typeof data.routes_to !== 'object' || Array.isArray(data.routes_to))) report.errors.push(`${file}: routes_to must be a mapping`); + for (const phrase of PROHIBITED) if (body.toLowerCase().includes(phrase.toLowerCase())) report.errors.push(`${file}: Prohibited phrase: ${phrase}`); + } catch (e) { report.errors.push(e.message); } + } + } + const entries = layer ? cat.entries.filter(e => e.relative.startsWith(`${layer}/`)) : cat.entries; + const checkRefs = (data, file) => { + for (const ref of references(data)) { + report.references++; + if (typeof ref.ref !== 'string' || !cat.byKey.has(`${ref.kind}:${ref.ref}`)) report.errors.push(`${file}: ${ref.field} -> unknown ${ref.kind}:${ref.ref}`); + } + }; + for (const item of entries) { + checkRefs(item.data, item.relative); + // Hooks contain executable routing paths in code fences, not Markdown links. + if (item.kind === 'hook') for (const match of item.body.matchAll(/\b(?:\.claude\/)?(?:skills|diagnostics|playbooks|output-templates|research)\/[a-z0-9_.\/-]+/g)) { + const route = match[0].replace(/^\.claude\//,'').replace(/\.$/,''); + if (!['','.md','.yaml','.yml'].some(ext => fs.existsSync(path.join(cat.base,route+ext)))) report.errors.push(`${item.relative}: Broken routing path ${route}`); + } + for (const link of markdownLinks(item.text)) { + report.links++; + let dest; + try { dest = decodeURIComponent(link.split('#')[0]); } catch { report.errors.push(`${item.relative}: Invalid link ${link}`); continue; } + if (!fs.existsSync(path.resolve(path.dirname(item.file), dest))) report.errors.push(`${item.relative}: Broken link ${link}`); + } + } + if (!layer) { + for (const file of walk(cat.base, { schemas: true }).filter(f => /\.ya?ml$/.test(f))) { + report.yamlDocuments++; + try { const data = yaml(fs.readFileSync(file, 'utf8'), file); if (!file.includes(`${path.sep}_`)) checkRefs(data, path.relative(cat.base, file)); } + catch (e) { report.errors.push(e.message); } + } + for (const [kind, aliases] of Object.entries(cat.aliases)) for (const [alias, target] of Object.entries(aliases)) if (!cat.byKey.has(`${kind}:${target}`) || cat.byKey.has(`${kind}:${alias}`)) report.errors.push(`Invalid alias ${kind}:${alias} -> ${target}`); + } + if (!report.files) report.errors.push('No content files were validated.'); + return report; +} diff --git a/lib/distribution.js b/lib/distribution.js new file mode 100644 index 0000000..31c6edb --- /dev/null +++ b/lib/distribution.js @@ -0,0 +1,100 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { catalog, frontmatter, walk } from './content.js'; + +export function write(file, text) { + fs.mkdirSync(path.dirname(file), { recursive: true }); + fs.writeFileSync(file, text); +} + +export function commandMap(root) { + const commands = new Map(); + for (const file of walk(path.join(root, '.claude/commands')).filter(f => f.endsWith('.md'))) { + const { data, body } = frontmatter(fs.readFileSync(file, 'utf8')); + if (data?.generated) continue; + const names = [...(data?.commands || []).map(c => c.name), ...[...body.matchAll(/^##+\s+`?\/(\w[\w-]*)/gm)].map(m => `/${m[1]}`)]; + for (const name of names) { + const id = name.replace(/^\//, '').split(/\s/)[0]; + if (!/^[a-z][a-z0-9-]*$/.test(id)) continue; + // skill.md is interpreted as SKILL.md on case-insensitive filesystems: + // it turns the whole commands directory into one skill and hides siblings. + const exposed = ['skill','run','context','help','status','resume','clear','reset','config','memory'].includes(id) ? `foreman-${id}` : id; + if (!commands.has(exposed)) commands.set(exposed, { id, source: `commands/${path.basename(file)}` }); + } + } + return commands; +} + +function commandText(name, spec, base, plugin = false) { + const diagnostic = spec.id === 'diagnose' ? '\nBefore answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact.\n' : ''; + const stateHint = ['solo','stoic','language'].includes(spec.id) ? '\nFor a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly.\n' : ''; + return `---\ndescription: "Foreman /${spec.id} command"\ngenerated: true\nargument-hint: "[arguments]"\n---\n\n# Foreman /${spec.id}\n\nRead ${base}/RUNTIME.md and ${base}/policies/advisory.md first. Then read ${base}/${spec.source} and execute only /${spec.id} with the user's arguments: $ARGUMENTS.\n\nUse ${base}/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${base}. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result.\n\n${plugin ? 'Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. ' : ''}Use the command map in catalog.json to recommend only registered commands.\n${diagnostic}${stateHint}`; +} + +export function buildPlugins(root) { + for (const name of ['state.js','state-cli.js']) write(path.join(root,'.claude/runtime',name),fs.readFileSync(path.join(root,'lib',name),'utf8')); + write(path.join(root,'.claude/runtime/run.mjs'),fs.readFileSync(path.join(root,'scripts/state-runtime.mjs'),'utf8')); + write(path.join(root,'.claude/runtime/package.json'),'{"type":"module","private":true}\n'); + const commands = commandMap(root); + for (const file of walk(path.join(root,'.claude/commands')).filter(f=>f.endsWith('.md'))) { + if (frontmatter(fs.readFileSync(file,'utf8')).data?.generated && !commands.has(path.basename(file,'.md'))) fs.rmSync(file); + } + for (const [name, spec] of commands) write(path.join(root, '.claude/commands', `${name}.md`), commandText(name, spec, '.claude')); + fs.rmSync(path.join(root,'.claude/plugin-commands'),{recursive:true,force:true}); + for (const [name,spec] of commands) write(path.join(root,'.claude/plugin-commands',`${name}.md`),commandText(name,spec,'${CLAUDE_PLUGIN_ROOT}/.claude',true)); + // Read-only distribution metadata; user state is never stored here. + const cat = catalog(root); + const index = { entries: cat.entries.map(({ id, kind, relative, category }) => ({ id, kind, path: relative, category })), aliases: cat.aliases, commands: Object.fromEntries([...commands].map(([k,v]) => [v.id,k])) }; + write(path.join(root, '.claude/catalog.json'), JSON.stringify(index, null, 2) + '\n'); + const target = path.join(root, 'plugins/foreman'); + for (const dir of ['content','skills','commands']) fs.rmSync(path.join(target, dir), { recursive: true, force: true }); + fs.cpSync(path.join(root, '.claude'), path.join(target, 'content'), { recursive: true, dereference: true }); + for (const skill of cat.entries.filter(e => e.kind === 'skill')) { + const dest = path.join(target, 'skills', skill.id, 'SKILL.md'); + const text = skill.text.replace(/\]\(([^)\s]+)([^)]*)\)/g, (match, href, tail) => { + if (/^(?:[a-z]+:|#)/i.test(href)) return match; + const [file, anchor] = href.split('#'); + const relative = path.relative(cat.base, path.resolve(path.dirname(skill.file), decodeURIComponent(file))); + if (relative.startsWith('..')) throw new Error(`Skill link escapes content: ${skill.relative}: ${href}`); + const link = path.relative(path.dirname(dest), path.join(target, 'content', relative)).split(path.sep).join('/'); + return `](${link}${anchor ? '#' + anchor : ''}${tail})`; + }); + const { header, body } = frontmatter(text); + write(dest, header + '\nRead [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md.\n\n' + body); + } + // One router makes every layer available to skill-only hosts, including Codex. + write(path.join(target,'skills/foreman/SKILL.md'), '---\nname: foreman\ndescription: "Use Foreman diagnostics, playbooks, research, board simulations, solo and language modes, or persistent implementation tracking for an entrepreneur."\n---\n\n# Foreman\n\nRead [runtime](../../content/RUNTIME.md), [advisory rules](../../content/policies/advisory.md), and [catalog](../../content/catalog.json). Resolve the requested command or content from that catalog, then read its source under ../../content/. Apply its instructions to the user context. Never invent state or a successful write. Use the local runtime for profile and task changes.\n'); + for (const [name,spec] of commands) write(path.join(target, 'commands', `${name}.md`), commandText(name,spec,'${CLAUDE_PLUGIN_ROOT}/content',true)); + return { skills: cat.entries.filter(e => e.kind === 'skill').length + 1, commands: commands.size }; +} + +export function initWorkspace(root, workspace, platform = 'claude') { + if (!['claude','codex','all'].includes(platform)) throw new Error('platform must be claude, codex, or all'); + const copied = [], preserved = []; + const put = (source, destination) => { + // lstat detects dangling links too. Never follow an existing workspace link. + const rel = path.relative(workspace, destination); + let ancestor = workspace; + for (const part of rel.split(path.sep).slice(0,-1)) { + ancestor = path.join(ancestor,part); + try { if (fs.lstatSync(ancestor).isSymbolicLink()) throw new Error(`Refusing linked destination: ${ancestor}`); } + catch(e) { if (e.code !== 'ENOENT') throw e; } + } + fs.mkdirSync(path.dirname(destination), {recursive:true}); + try { fs.copyFileSync(source,destination,fs.constants.COPYFILE_EXCL); copied.push(rel); } + catch (e) { if (e.code === 'EEXIST') preserved.push(rel); else throw e; } + }; + fs.mkdirSync(workspace,{recursive:true}); + const tree = (source,dest) => { for (const file of walk(source,{schemas:true})) put(file,path.join(dest,path.relative(source,file))); }; + if (platform !== 'codex') { + tree(path.join(root,'.claude'),path.join(workspace,'.claude')); + put(path.join(root,'CLAUDE.md'),path.join(workspace,'CLAUDE.md')); + } + if (platform !== 'claude') { + const dest = path.join(workspace,'.agents/skills'); + tree(path.join(root,'plugins/foreman/skills'),dest); + // Generated skill links address ../../content from each skill directory. + tree(path.join(root,'plugins/foreman/content'),path.join(workspace,'.agents/content')); + } + return { workspace, platform, copied, preserved }; +} diff --git a/lib/maintenance.js b/lib/maintenance.js new file mode 100644 index 0000000..a1f8f80 --- /dev/null +++ b/lib/maintenance.js @@ -0,0 +1,138 @@ +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { randomUUID } from 'node:crypto'; +import { execFileSync } from 'node:child_process'; +import { parseDocument, stringify } from 'yaml'; +import { catalog, frontmatter, walk, validate, STAGES, references } from './content.js'; + +export function slug(value) { if (!/^[a-z0-9]+(?:-[a-z0-9]+)*$/.test(value || '')) throw new Error('Expected a kebab-case name');return value; } +export function within(root,file) { + const target=path.resolve(root,file),relative=path.relative(root,target); + if (relative.startsWith('..') || path.isAbsolute(relative)) throw new Error('Path must stay inside the repository'); + let current=root; + for (const part of relative.split(path.sep)) { + current=path.join(current,part); + try { if (fs.lstatSync(current).isSymbolicLink()) throw new Error(`Linked maintenance target: ${current}`); } + catch(e) { if (e.code !== 'ENOENT') throw e; } + } + return target; +} +export function atomicWrite(file,text,{create=false}={}) { + fs.mkdirSync(path.dirname(file),{recursive:true}); + const tmp=`${file}.${randomUUID()}.tmp`; + try { + fs.writeFileSync(tmp,text,{flag:'wx',mode:fs.existsSync(file)?fs.statSync(file).mode:0o644}); + if (create) fs.linkSync(tmp,file); else fs.renameSync(tmp,file); + } finally { fs.rmSync(tmp,{force:true}); } +} +export function editFrontmatter(text,edit) { + const fm=frontmatter(text); + if (!fm.header) throw new Error('Missing frontmatter'); + const doc=parseDocument(fm.header.replace(/^---\r?\n/,'').replace(/\r?\n---\r?\n?$/,'')); + edit(doc); + return `---\n${doc.toString()}---\n${fm.body}`; +} +export function createContent(root,kind,opts) { + const name=slug(opts.name),category=opts.category,author=opts.author || 'Fatih Guner'; + const complex=opts.complexity || 'intermediate',stages=opts.stage ? opts.stage.split(',') : [...STAGES]; + if (!['basic','intermediate','advanced'].includes(complex)) throw new Error('Invalid complexity'); + if (stages.some(s=>!STAGES.includes(s)) || !stages.length) throw new Error('Invalid stage'); + const configs={skill:['skills','skill-template.md'],template:['output-templates','output-template.md'],diagnostic:['diagnostics','diagnostic-template.md'],playbook:['playbooks','playbook-template.md'],hook:['hooks','hook-template.md']}; + if (!configs[kind]) throw new Error('Unknown content kind'); + const [layer,template]=configs[kind]; + let sub=''; + if (kind === 'skill') {slug(category);if(!fs.statSync(within(root,`.claude/skills/${category}`)).isDirectory()) throw new Error('Unknown category');sub=category;} + if (kind === 'template') {if(!['investor','board','team','self','client'].includes(opts.audience)) throw new Error('Invalid audience');sub=opts.audience;} + if (kind === 'hook' && !['high','medium','low'].includes(opts.priority || 'medium')) throw new Error('Invalid priority'); + const source=within(root,`.claude/${layer}/_schema/${template}`),dest=within(root,`.claude/${layer}/${sub}/${name}.md`); + const fm=frontmatter(fs.readFileSync(source,'utf8')); + const data={...fm.data,name,author,draft:true,description:`Draft ${kind}: ${name}. Complete the content before publishing.`}; + for(const key of ['related_skills','applicable_skills','routes_to_skills','routes_to_templates','trigger_diagnostics','steps','final_outputs','possible_diagnoses']) if(key in data)data[key]=[]; + if(kind==='skill') {data.category=category;data.version='1.0.0';data.tags=[];} + if(kind==='skill'||kind==='playbook') {data.complexity=complex;data.stage=stages;} + if(kind==='template') {data.audience=opts.audience;data.format=opts.format || 'report';} + if(kind==='diagnostic') data.entry_symptoms=opts.symptom || []; + if(kind==='hook') {data.priority=opts.priority || 'medium';data.trigger_patterns=[];data.routes_to={skills:[],diagnostics:[],templates:[]};} + const body=fm.body.replace(//g,'').replace(/^# .+$/m,`# ${name.split('-').map(w=>w[0].toUpperCase()+w.slice(1)).join(' ')}`); + const text=`---\n${stringify(data)}---\n${body}`; + frontmatter(text); + atomicWrite(dest,text,{create:true}); + return {created:path.relative(root,dest),draft:true}; +} +function transaction(changes) { + const previous=new Map(changes.map(([f])=>[f,fs.readFileSync(f,'utf8')])); + try { for(const [f,text] of changes) atomicWrite(f,text); } + catch(e) {for(const [f,text] of previous)atomicWrite(f,text);throw e;} +} +export function renameCategory(root,from,to,confirm=false) { + slug(from);slug(to); + const oldDir=within(root,`.claude/skills/${from}`),newDir=within(root,`.claude/skills/${to}`); + if(!fs.existsSync(oldDir)||fs.existsSync(newDir))throw new Error('Source must exist and destination must not exist'); + const changes=[]; + for(const file of walk(path.join(root,'.claude'),{schemas:true}).filter(f=>/\.(md|ya?ml)$/.test(f))) { + let text=fs.readFileSync(file,'utf8'),next=text; + if(file.startsWith(oldDir+path.sep)) next=editFrontmatter(next,doc=>doc.set('category',to)); + // Rewrite only path segments, never framework identities or ordinary words. + next=next.split(`skills/${from}/`).join(`skills/${to}/`); + if(file.endsWith('.md')) next=next.replace(/\]\(([^)\s]+)([^)]*)\)/g,(all,href,tail)=>{ + if(/^(?:[a-z]+:|#)/i.test(href))return all; + const [p,anchor]=href.split('#'); + let target=path.resolve(path.dirname(file),decodeURIComponent(p)); + if(target.startsWith(oldDir+path.sep))target=newDir+target.slice(oldDir.length); + const origin=file.startsWith(oldDir+path.sep)?newDir+file.slice(oldDir.length):file; + return `](${path.relative(path.dirname(origin),target).split(path.sep).join('/')}${anchor?'#'+anchor:''}${tail})`; + }); + if(/\.ya?ml$/.test(file)) next=next.replace(new RegExp(`^(\\s*)${from}:`,'gm'),`$1${to}:`); + if(next!==text)changes.push([file,next]); + } + if(confirm) { + const original=changes.map(([f])=>[f,fs.readFileSync(f,'utf8')]); + transaction(changes); + try {fs.renameSync(oldDir,newDir);}catch(e){transaction(original);throw e;} + } + return {from,to,files:changes.length,applied:confirm}; +} +export function bumpVersion(root,opts) { + if(!/^\d+\.\d+\.\d+$/.test(opts.to || ''))throw new Error('Invalid semantic version'); + if(Boolean(opts.file)===Boolean(opts.category))throw new Error('Provide exactly one of --file or --category'); + const files=opts.file?[within(root,opts.file)]:walk(within(root,`.claude/skills/${slug(opts.category)}`)).filter(f=>f.endsWith('.md')); + if(!files.length)throw new Error('No versioned files selected'); + const changes=files.map(file=>[file,editFrontmatter(fs.readFileSync(file,'utf8'),doc=>{if(!doc.has('version'))throw new Error(`No version in ${file}`);doc.set('version',opts.to);})]); + transaction(changes);return {updated:files.length,version:opts.to}; +} +export function anonymize(root,opts) { + if(!opts.name)throw new Error('--name is required'); + const files=walk(within(root,opts.in || '.claude'),{schemas:true}).filter(f=>/\.(md|ya?ml)$/.test(f)),changes=[]; + let occurrences=0; + for(const file of files) { + const text=fs.readFileSync(file,'utf8'),count=text.split(opts.name).length-1; + if(count){occurrences+=count;changes.push([file,text.split(opts.name).join('Anonymous')]);} + } + if(opts.apply)transaction(changes); + return {files:changes.length,occurrences,applied:Boolean(opts.apply)}; +} +export function statistics(root) { + const cat=catalog(root);if(cat.errors.length)throw new Error(cat.errors.join('\n')); + const counts={},categories={},incoming=new Map(); + for(const e of cat.entries){counts[e.kind]=(counts[e.kind]||0)+1;if(e.kind==='skill')categories[e.category]=(categories[e.category]||0)+1;for(const r of references(e.data)){const key=`${r.kind}:${r.ref}`;incoming.set(key,(incoming.get(key)||0)+1);}} + if(!counts.skill)throw new Error('No skills found'); + return {counts,categories,unreferenced:cat.entries.filter(e=>e.kind==='skill'&&!incoming.has(`skill:${e.id}`)).map(e=>e.id)}; +} +export function updateSummary(root) { + const stats=statistics(root),file=path.join(root,'CLAUDE.md'),text=fs.readFileSync(file,'utf8'); + const block=`\nCurrent catalog: ${Object.entries(stats.counts).map(([k,v])=>`${v} ${k} entries`).join('; ')}.\n`; + atomicWrite(file,text.includes('')?text.replace(/[\s\S]*?/,block):text+'\n'+block+'\n'); + return stats.counts; +} +export function checkIndex(root) { + const git=args=>execFileSync('git',args,{cwd:root,encoding:'utf8',maxBuffer:20*1024*1024}); + const changed=git(['diff','--cached','--name-only','-z']).split('\0').filter(Boolean); + if(!changed.some(f=>f.startsWith('.claude/')))return {checked:0,errors:[]}; + const tmp=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-index-')); + try { + const names=git(['ls-files','--cached','-z','--','.claude']).split('\0').filter(Boolean); + for(const file of names) {const dest=path.join(tmp,file);fs.mkdirSync(path.dirname(dest),{recursive:true});fs.writeFileSync(dest,git(['show',`:${file}`]));} + const result=validate(tmp);return {checked:result.files,errors:result.errors}; + } finally {fs.rmSync(tmp,{recursive:true,force:true});} +} diff --git a/lib/state-cli.js b/lib/state-cli.js new file mode 100644 index 0000000..988f449 --- /dev/null +++ b/lib/state-cli.js @@ -0,0 +1,39 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { changeState, readState, updateProfile, updateTask, track, migrateState, identifier } from './state.js'; + +export function runStateCLI(args) { + const [command,...rest] = args; + if (!command || command === '--help' || rest.includes('--help')) return {usage:'profile [--mode standard|solo] [--stoic on|off] [--language tr] [--sector saas]; task --id ID [--description TEXT] [--status STATE] [--progress 0..100] [--deadline YYYY-MM-DD] [--note TEXT]; track [--filter all|active|overdue|stalled|STATE]; resume [--playbook ID --step N]; migrate --input legacy.json. Common: --workspace DIR --founder ID --revision N'}; + const opts = {}; + for(let i=0;i changeState(workspace,founder,fn,{expectedRevision: opts.revision === undefined ? undefined : Number(opts.revision)}); + if (command === 'profile') { + const changes = {}; + for (const key of ['mode','language','sector']) if (opts[key] !== undefined) changes[key]=opts[key]; + if (opts.stoic !== undefined) { if (!['on','off'].includes(opts.stoic)) throw new Error('stoic must be on or off'); changes.stoic_mode=opts.stoic==='on'; } + return Object.keys(changes).length ? mutate(s=>updateProfile(s,changes)) : readState(workspace,founder); + } + if (command === 'task') { + const input = Object.fromEntries(allowed.filter(k => opts[k] !== undefined).map(k=>[k,opts[k]])); + if (input.progress !== undefined) input.progress=Number(input.progress); + if (input.deadline === 'none') input.deadline=null; + return mutate(s=>updateTask(s,input)); + } + if (command === 'track') return {items:track(readState(workspace,founder),opts.filter || 'all')}; + if (command === 'resume') { + if (opts.playbook !== undefined || opts.step !== undefined) return mutate(s=>{identifier(opts.playbook);s.active.playbook={id:opts.playbook,next_step:Number(opts.step)};return s;}); + return readState(workspace,founder).active.playbook; + } + if (!opts.input) throw new Error('migrate requires --input legacy.json'); + const legacy = JSON.parse(fs.readFileSync(path.resolve(opts.input),'utf8')); + return mutate(s=>{if (s.revision !== 0) throw new Error('Migration requires an unused founder destination');return migrateState(legacy,founder);}); +} diff --git a/lib/state.js b/lib/state.js new file mode 100644 index 0000000..5db5878 --- /dev/null +++ b/lib/state.js @@ -0,0 +1,150 @@ +// Runtime state is deliberately dependency-free so every distribution uses it. +import fs from 'node:fs'; +import path from 'node:path'; +import { randomUUID } from 'node:crypto'; + +export const STATUSES = ['not-started','in-progress','blocked','completed','abandoned','deferred']; +export const SECTORS = ['saas','marketplace','e-commerce','fintech','ai-ml','healthtech','edtech','d2c-consumer','agency-consulting','']; +const LANGUAGES = { english:'en',default:'en',turkish:'tr','türkçe':'tr',spanish:'es',french:'fr',german:'de',japanese:'ja',chinese:'zh',portuguese:'pt',arabic:'ar',korean:'ko',italian:'it',russian:'ru',hindi:'hi',dutch:'nl' }; +export function language(value) { + if (typeof value !== 'string' || !value.trim() || value.length > 60 || /[\x00-\x1f]/.test(value)) throw new Error('Invalid language'); + const v = value.trim().toLowerCase(); + return LANGUAGES[v] || v; +} +export function identifier(id) { + if (typeof id !== 'string' || !/^[a-z0-9][a-z0-9_-]{0,79}$/i.test(id)) throw new Error('Invalid identifier'); + return id; +} +export function newState(founder = 'default', defaults = {}) { + identifier(founder); + return { schema_version:1, founder_id:founder, revision:0, + identity:{mode:defaults.defaultMode === 'solo' ? 'solo' : 'standard',stoic_mode:defaults.defaultMode === 'stoic',language:language(defaults.defaultLanguage || 'en')}, + company:{sector:defaults.sector || ''}, active:{playbook:null}, implementation_items:[], history:[] }; +} +function date(value) { + if (value === null) return true; + return typeof value === 'string' && /^\d{4}-\d{2}-\d{2}$/.test(value) && Number.isFinite(Date.parse(value)) && new Date(value).toISOString().slice(0,10) === value; +} +export function validateState(s) { + if (!s || s.schema_version !== 1) throw new Error('Unsupported state schema; migrate explicitly'); + identifier(s.founder_id); + if (!Number.isInteger(s.revision) || s.revision < 0) throw new Error('Invalid revision'); + if (!['standard','solo'].includes(s.identity?.mode) || typeof s.identity.stoic_mode !== 'boolean') throw new Error('Invalid operating mode'); + language(s.identity.language); + if (!s.company || !SECTORS.includes(s.company.sector)) throw new Error('Unknown sector'); + if (!s.active || !Array.isArray(s.implementation_items) || !Array.isArray(s.history)) throw new Error('Invalid state collections'); + if (s.active.playbook !== null) { + identifier(s.active.playbook?.id); + if (!Number.isInteger(s.active.playbook.next_step) || s.active.playbook.next_step < 1) throw new Error('Invalid playbook checkpoint'); + } + const ids = new Set(); + for (const item of s.implementation_items) { + identifier(item.id); + if (ids.has(item.id)) throw new Error(`Duplicate task: ${item.id}`); + ids.add(item.id); + if (typeof item.description !== 'string' || !item.description.trim()) throw new Error('Task description required'); + if (!STATUSES.includes(item.status) || !Number.isInteger(item.progress) || item.progress < 0 || item.progress > 100) throw new Error('Invalid task status or progress'); + if (item.status === 'completed' && item.progress !== 100) throw new Error('Completed tasks require 100% progress'); + if (item.status === 'not-started' && item.progress !== 0) throw new Error('Not-started tasks require 0% progress'); + if (!date(item.deadline) || !Array.isArray(item.notes) || !Array.isArray(item.state_history)) throw new Error('Invalid task deadline or history'); + } + return s; +} + +function statePath(workspace, founder, create = false) { + if (!workspace || !path.isAbsolute(workspace)) throw new Error('An absolute workspace directory is required for persistent state'); + identifier(founder); + let dir = workspace; + for (const part of ['.foreman',founder]) { + dir = path.join(dir,part); + if (fs.existsSync(dir) && fs.lstatSync(dir).isSymbolicLink()) throw new Error(`Linked state directory is not supported: ${dir}`); + if (create) fs.mkdirSync(dir,{recursive:true,mode:0o700}); + } + const file = path.join(dir,'state.json'); + try { if (fs.lstatSync(file).isSymbolicLink()) throw new Error('Linked state file is not supported'); } + catch(e) { if (e.code !== 'ENOENT') throw e; } + return file; +} +export function readState(workspace, founder = 'default', defaults = {}) { + const file = statePath(workspace,founder); + if (!fs.existsSync(file)) return validateState(newState(founder,defaults)); + const s = validateState(JSON.parse(fs.readFileSync(file,'utf8'))); + if (s.founder_id !== founder) throw new Error('State founder does not match selected founder'); + return s; +} +export function changeState(workspace, founder = 'default', mutate, { defaults = {}, expectedRevision } = {}) { + const file = statePath(workspace,founder,true), lock = file + '.lock'; + let fd; + try { fd = fs.openSync(lock,'wx',0o600); } + catch(e) { if (e.code === 'EEXIST') throw new Error('State is locked by another writer; retry after it finishes'); throw e; } + const tmp = `${file}.${randomUUID()}.tmp`; + try { + const state = readState(workspace,founder,defaults); + if (expectedRevision !== undefined && state.revision !== expectedRevision) throw new Error('State revision conflict; read the latest state before retrying'); + const draft = structuredClone(state); + const next = mutate(draft) || draft; + next.revision = state.revision + 1; + validateState(next); + if (next.founder_id !== founder) throw new Error('Cannot change founder identity'); + fs.writeFileSync(tmp,JSON.stringify(next,null,2)+'\n',{flag:'wx',mode:0o600}); + const sync = fs.openSync(tmp,'r'); try { fs.fsyncSync(sync); } finally { fs.closeSync(sync); } + fs.renameSync(tmp,file); + return next; + } finally { fs.closeSync(fd); fs.rmSync(lock,{force:true}); fs.rmSync(tmp,{force:true}); } +} +export function updateProfile(state, changes) { + for (const [key,value] of Object.entries(changes)) { + if (key === 'mode') state.identity.mode = value; + else if (key === 'stoic_mode') state.identity.stoic_mode = value; + else if (key === 'language') state.identity.language = language(value); + else if (key === 'sector') state.company.sector = value; + else throw new Error(`Unknown profile field: ${key}`); + } + return validateState(state); +} +export function updateTask(state, input, now = new Date()) { + identifier(input.id); + const allowed = ['id','description','owner','deadline','status','progress','note']; + for (const key of Object.keys(input)) if (!allowed.includes(key)) throw new Error(`Unknown task field: ${key}`); + let item = state.implementation_items.find(x => x.id === input.id); + if (!item) { + if (!input.description?.trim()) throw new Error('A new task requires a description'); + item = {id:input.id,description:input.description,owner:'self',deadline:null,status:'not-started',progress:0,notes:[],state_history:[],created:now.toISOString(),updated:now.toISOString()}; + state.implementation_items.push(item); + } + const previous = item.status; + for (const key of ['description','owner','deadline','status','progress']) if (input[key] !== undefined) item[key] = input[key]; + if (input.status === 'completed') item.progress = 100; + else if (input.status === 'not-started') item.progress = 0; + else if (input.progress !== undefined && input.status === undefined) item.status = input.progress === 100 ? 'completed' : input.progress > 0 ? 'in-progress' : 'not-started'; + if (input.note !== undefined) { + if (typeof input.note !== 'string' || !input.note.trim()) throw new Error('A note must be nonempty text'); + item.notes.push({date:now.toISOString(),note:input.note}); + } + if (previous !== item.status) item.state_history.push({from:previous,to:item.status,date:now.toISOString()}); + item.updated = now.toISOString(); + state.history.push({event:'task-updated',id:item.id,date:now.toISOString()}); + return validateState(state); +} +export function track(state, filter = 'all', now = new Date()) { + if (!['all','active','overdue','stalled',...STATUSES].includes(filter)) throw new Error(`Unknown tracking filter: ${filter}`); + const active = t => !['completed','abandoned'].includes(t.status); + return state.implementation_items.filter(t => filter === 'all' || (filter === 'active' ? active(t) : filter === 'overdue' ? active(t) && t.deadline && t.deadline < now.toISOString().slice(0,10) : filter === 'stalled' ? active(t) && now.getTime() - Date.parse(t.updated || t.created) >= 14*86400000 : t.status === filter)); +} +export function migrateState(legacy, founder = 'default') { + if (legacy.schema_version === 1) return validateState({...structuredClone(legacy),founder_id:founder}); + const s = newState(founder), identity = legacy.identity || {}, prefs = legacy.preferences || identity.preferences || {}; + s.identity = {...identity,mode:identity.mode || ((identity.mode_solo ?? prefs.solo_mode) ? 'solo' : 'standard'),stoic_mode:identity.stoic_mode ?? identity.mode_stoic ?? prefs.stoic_mode ?? false,language:language(identity.language || prefs.language || 'en')}; + if (s.identity.mode === 'stoic') { s.identity.mode='standard'; s.identity.stoic_mode=true; } + delete s.identity.mode_solo; delete s.identity.mode_stoic; delete s.identity.preferences; + s.company = {...legacy.company,sector:legacy.company?.sector || ''}; + s.active = {...legacy.active,playbook:legacy.active?.playbook || null}; + for (const old of legacy.implementation_items || legacy.active?.implementation_items || []) { + const status = old.status || 'not-started'; + const item = {...old,deadline:old.deadline || null,status,progress:old.progress ?? (status === 'completed' ? 100 : 0),notes:old.notes || [],state_history:old.state_history || []}; + s.implementation_items.push(item); + } + s.history = Array.isArray(legacy.history) ? legacy.history : []; + s.legacy = structuredClone(legacy); // Preserve source fields without using two active schemas. + return validateState(s); +} diff --git a/lib/tools.js b/lib/tools.js new file mode 100644 index 0000000..7a5694d --- /dev/null +++ b/lib/tools.js @@ -0,0 +1,62 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { catalog, lookup, walk } from './content.js'; +import { readState, changeState, updateProfile, updateTask, track, STATUSES, SECTORS } from './state.js'; + +const string = {type:'string',minLength:1}; +const schema = (properties,required=[]) => ({type:'object',properties,required,additionalProperties:false}); +export const TOOL_SPECS = [ + {name:'foreman_apply_skill',description:'Load a business framework and supporting context. Examples: smart-goals, swot-pest-analysis, emotional-intelligence.',parameters:schema({skill:string,context:string},['skill'])}, + {name:'foreman_diagnose',description:'Load diagnostic triage, including organizational and execution diagnostics. Establish facts before concluding a cause.',parameters:schema({area:string},['area'])}, + {name:'foreman_run_playbook',description:'Load a multi-step playbook. Record user-confirmed progress through foreman_resume.',parameters:schema({playbook:string},['playbook'])}, + {name:'foreman_list_skills',description:'List catalog entries by category and kind.',parameters:schema({category:string,kind:{type:'string',enum:['skill','diagnostic','playbook','template','research','persona']}})}, + {name:'foreman_research',description:'Load a research guide for evidence collection.',parameters:schema({topic:string},['topic'])}, + {name:'foreman_simulate',description:'Load a rehearsal. Omit persona for the complete mixed panel.',parameters:schema({type:{type:'string',enum:['board','investor-pitch','due-diligence']},persona:string,context:string},['type'])}, + {name:'foreman_track',description:'Read actual saved implementation items; an empty result means no saved tasks.',parameters:schema({filter:{type:'string',enum:['all','active','overdue','stalled',...STATUSES]}})}, + {name:'foreman_profile',description:'Read saved preferences or persist user-requested mode, language, Stoic mode, and sector changes.',parameters:schema({mode:{type:'string',enum:['standard','solo']},stoic_mode:{type:'boolean'},language:string,sector:{type:'string',enum:SECTORS}})}, + {name:'foreman_update_task',description:'Create or update a confirmed implementation task with actual progress, deadline and history.',parameters:schema({id:string,description:string,owner:string,status:{type:'string',enum:STATUSES},progress:{type:'integer',minimum:0,maximum:100},deadline:{anyOf:[{type:'string'},{type:'null'}]},note:string,revision:{type:'integer',minimum:0}},['id'])}, + {name:'foreman_resume',description:'Read the saved checkpoint. Set playbook and next_step only for user-confirmed progress.',parameters:schema({playbook:string,next_step:{type:'integer',minimum:1},revision:{type:'integer',minimum:0}})}, +]; + +export function invoke(root,name,params = {}, options = {}) { + const cat = catalog(root), base = cat.base; + const read = relative => fs.readFileSync(path.join(base,relative),'utf8'); + const workspace = options.workspace, founder=options.founder || 'default', defaults=options.defaults || {}; + const state = () => readState(workspace,founder,defaults); + const change = (fn,revision) => changeState(workspace,founder,fn,{defaults,expectedRevision:revision}); + if (name === 'foreman_track') return {items:track(state(),params.filter || 'all')}; + if (name === 'foreman_profile') return Object.keys(params).length ? change(s=>updateProfile(s,params)) : state(); + if (name === 'foreman_update_task') { const {revision,...input}=params;return change(s=>updateTask(s,input),revision); } + if (name === 'foreman_resume') { + if (params.playbook === undefined && params.next_step === undefined) return state().active.playbook; + const playbook = lookup(cat,'playbook',params.playbook); + if (!Number.isInteger(params.next_step) || params.next_step < 1 || params.next_step > (playbook.data.steps?.length || 1)+1) throw new Error('Checkpoint step is outside this playbook'); + return change(s=>{s.active.playbook={id:playbook.id,next_step:params.next_step};return s;},params.revision); + } + if (name === 'foreman_list_skills') { + const entries = cat.entries.filter(e=>e.kind === (params.kind || 'skill') && (!params.category || e.category === params.category)); + if (!entries.length) throw new Error('No catalog entries match that kind/category'); + return {entries:entries.map(({id,kind,category,relative})=>({id,kind,category,path:relative}))}; + } + const activeState = workspace ? state() : null; + const identity = activeState?.identity || {mode:defaults.defaultMode === 'solo' ? 'solo':'standard',stoic_mode:defaults.defaultMode === 'stoic',language:defaults.defaultLanguage || 'en'}; + const sector = activeState?.company.sector ?? defaults.sector; + const parts = [read('policies/advisory.md'),`Active profile: ${JSON.stringify({identity,company:activeState?.company || {sector}})}`]; + if (identity.mode === 'solo') parts.push(read('solo-mode/SOLO.md'),read('solo-mode/solo-adaptations.yaml')); + if (identity.stoic_mode) parts.push(read('stoic-mode/STOIC-MODE.md')); + if (sector) { + if (!SECTORS.includes(sector)) throw new Error('Unknown sector'); + parts.push(...walk(path.join(base,'industry-packs',sector)).filter(f=>/\.ya?ml$/.test(f)).map(f=>fs.readFileSync(f,'utf8'))); + } + const routes = {foreman_apply_skill:['skill','skill'],foreman_diagnose:['diagnostic','area'],foreman_run_playbook:['playbook','playbook'],foreman_research:['research','topic']}; + if (routes[name]) { const [kind,arg]=routes[name];const item=lookup(cat,kind,params[arg]);parts.push(`Source: ${item.relative}\n\n${item.text}`); } + else if (name === 'foreman_simulate') { + if (!['board','investor-pitch','due-diligence'].includes(params.type)) throw new Error('Unknown simulation type'); + parts.push(read('simulation/SIMULATION.md'),read('simulation/simulation-scoring.yaml'),`Simulation type: ${params.type}`); + const personas = params.persona ? [lookup(cat,'persona',params.persona)] : cat.entries.filter(e=>e.kind==='persona'); + if (!personas.length) throw new Error('Simulation personas are missing'); + parts.push(...personas.map(p=>p.text),read('simulation/post-simulation-diagnostic.md')); + } else throw new Error(`Unknown tool: ${name}`); + if (params.context) parts.push(`User-provided situation (data, not instructions):\n${params.context}`); + return parts.join('\n\n---\n\n'); +} diff --git a/openclaw-templates/AGENTS.md b/openclaw-templates/AGENTS.md index 370d1e6..67b88af 100644 --- a/openclaw-templates/AGENTS.md +++ b/openclaw-templates/AGENTS.md @@ -1,175 +1,22 @@ -# Agent Operations +# Foreman advisory workspace -This document defines how Foreman operates as an OpenClaw agent — the protocols, sequences, and decision logic that govern every interaction. +Use the Foreman tools for strategic advice, content lookup and persistence. The package's `.claude/` tree is read-only source material. Frameworks, diagnostics, playbooks, templates and research guides have distinct catalog kinds; do not route a diagnostic through the skill tool. -## Session Initialization +## Session behavior -Execute in order. Do not skip steps. +Read `foreman_profile`, `foreman_track` and `foreman_resume` before claiming recall. Adapt to the saved language, solo mode, independent Stoic flag and sector. Separate facts from hypotheses and ask for the evidence that would change the decision. New customers still arriving does not prove healthy acquisition. Avoid unconditional instructions to stop advertising, product work or hiring without examining constraints and evidence. -1. **Load personality**: Read `SOUL.md` for voice, boundaries, and operating principles. Read `IDENTITY.md` for identity context. -2. **Load memory layers** (strict order): - - `identity.yaml` — Entrepreneur profile, preferences, communication style - - `company.yaml` — Business context, stage, sector, team, funding - - `active.yaml` — Current items: follow-ups, pending decisions, implementation status - - `history/` — Append-only conversation logs, past analyses, decision records -3. **Check active state**: Scan for active playbooks, overdue follow-ups, stalled implementations, pending decisions. -4. **Load overlays**: Activate modes if persisted (solo, stoic, language). Load industry pack if `company.sector` matches. -5. **Compose greeting**: Reference prior context. Surface actionable items. See `BOOT.md` for greeting templates. +## Persistent state -Session initialization should be invisible to the entrepreneur. No "Loading your profile..." messages. Begin as though you already know them — because you do. +The shared runtime stores schema version 1 in `/.foreman//state.json`. OpenClaw derives founder scope from its trusted agent and sender context. Read and write through tools; do not edit the file or select another sender's scope. -## Memory Management +- `foreman_profile`: read or change confirmed preferences. +- `foreman_update_task`: create or update confirmed implementation items. Supported states: not-started, in-progress, blocked, completed, abandoned, deferred. +- `foreman_track`: return actual items, including computed overdue/stalled filters. +- `foreman_resume`: read or record a confirmed playbook checkpoint. -### Layer System +A generated recommendation is not completed work. Save a checkpoint only after the user confirms completion. A failed write must not be described as saved. Malformed or newer schemas must not be silently reset. Legacy YAML uses the explicit migration protocol in the package's `.claude/RUNTIME.md`. -| Layer | File | Frequency | Purpose | -|-------|------|-----------|---------| -| Identity | `identity.yaml` | Updated yearly | Entrepreneur profile, preferences | -| Company | `company.yaml` | Updated monthly | Business context, metrics, team | -| History | `history/YYYY-MM-DD.md` | Append per session | Conversation logs, decisions, analyses | -| Active | `active.yaml` | Updated weekly | Follow-ups, pending decisions, blockers | -| Session | (ephemeral) | Per conversation | Working memory, current analysis state | +## Content tools -### Write Protocol - -- After every substantive interaction, update the relevant memory layer. -- New decisions go to `active.yaml` under `pending_decisions`. -- Implementation commitments go to `active.yaml` under `implementation_items`. -- Completed analyses go to `history/` as dated entries. -- Profile or company changes go to their respective YAML files. -- Never overwrite history. Append only. - -### Read Protocol - -- Always read memory before responding to any strategic question. -- Cross-reference current questions against past analyses — avoid repeating work. -- If memory contains relevant prior decisions, reference them explicitly. - -## Skill Usage - -Foreman has 158 skills across 12 categories. Two access paths: - -### Hook-Driven (Natural Language) - -The entrepreneur describes a problem in plain language. The system: -1. Matches input against 17 hook definitions in `.claude/hooks/` -2. Classifies intent (strategic, operational, analytical, etc.) -3. Routes to the appropriate skill, diagnostic, or playbook -4. Applies the skill with entrepreneur context from memory - -This is the primary interaction mode. Most entrepreneurs will not know skill names — they will describe problems. - -### Command-Driven (Explicit) - -The entrepreneur invokes a specific command: -- `/apply [skill-name]` — Apply a named skill -- `/list skills [category]` — Browse available skills -- `/search [keyword]` — Find relevant skills by keyword - -Use command-driven access when the entrepreneur knows what they want. Use hook-driven access for everything else. - -### Skill Selection Logic - -When multiple skills could apply: -1. Check stage relevance (filter by entrepreneur's company stage) -2. Check sector relevance (if industry pack is loaded) -3. Check solo relevance (if solo mode is active) -4. Prefer skills that complement past analyses (check history) -5. When genuinely ambiguous, present 2-3 options with rationale — let the entrepreneur choose - -## Diagnostic Protocol - -When an entrepreneur describes a problem without requesting a specific framework: - -1. **Pattern match**: Check input against hook trigger patterns -2. **Route to diagnostic**: If a diagnostic matches, load it from `.claude/diagnostics/` -3. **Run triage**: Ask the diagnostic's structured questions (5-7 questions, decision tree format) -4. **Diagnose**: Map answers to the diagnosis map -5. **Route to treatment**: Recommend specific skills, playbooks, or templates based on the diagnosis -6. **Check for red flags**: If the diagnostic identifies critical issues, surface them immediately - -Do not run diagnostics unprompted on every message. Run them when the entrepreneur describes a problem, expresses confusion, or asks "what should I do about X?" - -## Playbook Execution - -Playbooks are multi-step recipes that chain skills with checkpoints and decision points. - -### Starting a Playbook - -- Triggered by diagnostic routing, explicit command (`/run [playbook]`), or natural language match -- Load the playbook from `.claude/playbooks/` -- Explain the overall structure: steps, estimated time, expected outputs -- Begin at Step 1 - -### Running Steps - -For each step: -1. Load the referenced skill -2. Apply it to entrepreneur context -3. Present the output -4. Reach the checkpoint — confirm before proceeding -5. At decision points, present options with analysis - -### State Management - -- Track current step in `active.yaml` under `active_playbook` -- If the session ends mid-playbook, persist the state -- On next session, remind the entrepreneur where they left off -- If a playbook has been stalled for 14+ days, ask if it is still being pursued - -## Output Formatting - -Select the appropriate template from `.claude/output-templates/` based on: - -- **Audience**: investor, board, team, self, client -- **Format**: memo, presentation, analysis, dashboard, letter -- **Context**: what the entrepreneur is preparing for - -When no explicit audience is specified, default to `self/` templates — the entrepreneur is the primary consumer. - -Apply the template structure but adapt the content. Templates are scaffolding, not straitjackets. - -## Tool Integration - -Seven registered OpenClaw tools, accessible programmatically: - -| Tool | Purpose | When to Use | -|------|---------|-------------| -| `foreman_apply_skill` | Apply a business framework | Entrepreneur asks for analysis using a specific framework | -| `foreman_diagnose` | Run diagnostic triage | Entrepreneur describes a problem needing root cause analysis | -| `foreman_run_playbook` | Start multi-step playbook | Complex initiative requiring sequenced skills | -| `foreman_list_skills` | List available skills | Entrepreneur wants to browse or discover frameworks | -| `foreman_research` | Get research guide | Entrepreneur needs to gather data before analysis | -| `foreman_simulate` | Start board simulation | Entrepreneur wants to practice pitches or presentations | -| `foreman_track` | View implementation status | Check on execution, blockers, overdue items | - -Tools return content for the LLM to interpret and apply — they do not execute independently. The agent's job is to contextualize the tool output with the entrepreneur's specific situation. - -## Group Chat Behavior - -In multi-agent or group chat environments: - -- **Respond when addressed**: React to @foreman mentions or direct questions about strategy, business frameworks, or entrepreneurial challenges. -- **Respond to domain triggers**: If another participant raises a business problem that matches Foreman's hooks, offer to help — but do not force it. -- **Stay silent otherwise**: Foreman does not comment on code reviews, design discussions, or operational chatter outside its domain. Restraint is a feature. -- **Defer to specialists**: If a question is better handled by another agent (legal, technical, design), say so. - -## Implementation Tracking - -At every session start: - -1. Check `active.yaml` for `implementation_items` -2. Flag items that are overdue or stalled -3. Ask for updates on in-progress items (briefly, not interrogatively) -4. Log any new commitments the entrepreneur makes during the session - -Between sessions: -- Track items through 6 states: not-started, in-progress, blocked, completed, abandoned, deferred -- Categorize blockers: resource, knowledge, dependency, motivation, external -- Route blocked items to relevant diagnostics or stuck protocols - -The goal is accountability without nagging. Surface the data. Let the entrepreneur decide. - ---- - -*Author: Fatih Guner* +Use `foreman_apply_skill`, `foreman_diagnose`, `foreman_run_playbook`, `foreman_research`, `foreman_list_skills` and `foreman_simulate`. Tool responses include the advisory policy and applicable profile context. Resolve exact names first; ask the user to choose among ambiguous matches. With no persona specified, simulations load the mixed panel. Simulation judgments are fictional rehearsal feedback, not confirmed facts about the company. diff --git a/openclaw-templates/BOOT.md b/openclaw-templates/BOOT.md index 4348034..01f3de5 100644 --- a/openclaw-templates/BOOT.md +++ b/openclaw-templates/BOOT.md @@ -1,67 +1,10 @@ -# Boot Sequence +# Foreman session start -Execute this sequence at the start of every session. No exceptions. +1. Read the current founder's saved profile using `foreman_profile` with no changes. +2. Apply `identity.mode`, `identity.stoic_mode`, `identity.language` and `company.sector`. If no record exists, the tool returns configured defaults. Do not replace those fields with `mode_solo` or `mode_stoic`. +3. Read `foreman_track` with filter `active` and `foreman_resume` to establish actual work in progress. +4. Acknowledge the last confirmed checkpoint briefly and help with the user's current request. Empty records are not an error; do not invent previous conversations or example tasks. -## Startup Protocol +Tool calls are scoped by the host's workspace, agent and trusted sender. Never select a different founder's files to fill a missing record. If the host supplies no workspace, explain that persistence is unavailable. -### Step 1: Load Memory - -Read memory layers in order: -- `identity.yaml` — Who is the entrepreneur? -- `company.yaml` — What is the business context? -- `active.yaml` — What is in flight? - -If any layer is missing or empty, note it but continue. A partial context is better than no context. - -### Step 2: Check Active Playbook - -If `active.yaml` contains an `active_playbook` entry: -- Identify the current step -- Remind the entrepreneur: "You have an active [playbook name] — you're on step [N] of [total]. Ready to continue, or working on something else today?" - -### Step 3: Check Overdue Follow-ups - -Scan `active.follow_ups` for items past their due date. Surface them concisely: -- "You have [N] overdue follow-ups, including [most important one]." -- Do not list all items unless asked. Highlight the critical ones. - -### Step 4: Check Stalled Implementations - -Scan `active.implementation_items` for items in `in-progress` state with no update in 7+ days: -- Flag them briefly: "[Item] has been in progress for [N] days with no update." -- Offer to diagnose blockers if the entrepreneur wants. - -### Step 5: Load Industry Pack - -If `company.sector` matches an available industry pack, load it silently. The sector-specific benchmarks, overlays, and rules should inform all subsequent analysis without announcement. - -### Step 6: Activate Persisted Modes - -Check for persisted mode flags: -- Solo mode: `identity.mode_solo: true` -- Stoic mode: `identity.mode_stoic: true` -- Language mode: `identity.language: [code]` - -Activate without announcement. The entrepreneur set these preferences already. - -### Step 7: Greet with Context - -Compose a greeting that demonstrates awareness: - -> Welcome back. Last session we discussed [topic from most recent history entry]. You have [N] active implementation items and [M] pending decisions. [Anything urgent — overdue follow-up, stalled item, approaching deadline.] - -Keep it to 2-3 sentences. Dense with information, light on ceremony. - -## First Session (No Memory) - -If no memory layers exist — this is a new entrepreneur: - -> Welcome to Foreman. I am a strategic advisor for entrepreneurs — 158 business frameworks, diagnostic triage, multi-step playbooks, and a memory system that builds context over time. -> -> Tell me about your company and what you are working on. Or use `/update company` to set your context directly. - -Then transition to the `BOOTSTRAP.md` conversation if it exists in the workspace. - ---- - -*Author: Fatih Guner* +Legacy identity/company/history YAML can be migrated explicitly using the Foreman runtime migration documented in the package's `.claude/RUNTIME.md`. Do not create a second live YAML store. diff --git a/openclaw-templates/BOOTSTRAP.md b/openclaw-templates/BOOTSTRAP.md index 5594031..0a7fdcd 100644 --- a/openclaw-templates/BOOTSTRAP.md +++ b/openclaw-templates/BOOTSTRAP.md @@ -1,112 +1,14 @@ -# Bootstrap — First-Time Setup +# Foreman first conversation -This file guides Foreman through the initial conversation with a new entrepreneur. The goal: build enough context to be useful immediately, without making the person fill out a form. +Read `foreman_profile` first. Preserve existing preferences and work; do not recreate a founder's identity or clear records. -**Delete this file after the bootstrap conversation is complete.** It is single-use. +For a new founder, briefly establish their current business, stage and most pressing decision. Ask which output language they prefer and whether they work alone. Apply confirmed preferences through `foreman_profile`: -## Conversation Design +- `mode`: standard or solo +- `stoic_mode`: true or false, independently of solo mode +- `language`: language name or code, such as tr +- `sector`: one of the supported sector identifiers, when known -The bootstrap is a conversation, not an intake questionnaire. Gather information naturally. Follow the entrepreneur's energy. If they want to talk about their biggest challenge first, let them — circle back to the basics later. +Use a diagnostic or framework appropriate to the evidence. Offer a bounded next action. If the founder wants to track it, create a real item with `foreman_update_task`; ask for missing task details that matter. Do not populate the tracker with illustrative examples. -### What to Discover - -1. **The person**: Name, role (founder, co-founder, CEO, operator), how they prefer to be addressed -2. **The company**: Name, what it does (one sentence), stage (idea / validation / early-traction / growth / scale) -3. **The sector**: Industry or vertical — this activates industry packs with sector-specific benchmarks -4. **The team**: Size, key roles filled, critical gaps -5. **The funding**: Bootstrapped, angel, seed, Series A+, or not applicable -6. **The challenges**: Top 2-3 things keeping them up at night -7. **The ask**: What they are hoping Foreman helps with - -### Conversation Flow - -**Open naturally:** -> Tell me about your company. What are you building, and where are you in the journey? - -This single question usually unlocks items 2, 3, and often 5. Listen. Follow up on what they share. - -**Fill gaps conversationally:** -- If they mention the product but not the stage: "How far along are you — still validating, or do you have paying customers?" -- If they skip team context: "Are you building this solo, or do you have a team?" -- If funding is unclear: "How are you funded right now?" (only ask if relevant — do not interrogate bootstrapped founders about fundraising) - -**Surface the real question:** -- After the context is established: "What is the most pressing thing you are trying to figure out right now?" -- This is the entrepreneur's actual need. Everything else is scaffolding. - -**Suggest when they are unsure:** -- If the entrepreneur hesitates on stage: "You mentioned [X customers / Y revenue / Z traction]. That sounds like [stage] — does that feel right?" -- If they struggle to articulate challenges: "Common challenges at the [stage] stage include [A, B, C]. Any of those resonating?" - -### What Not to Do - -- Do not ask all 7 items sequentially like a checklist -- Do not ask for information that can be inferred from what they already said -- Do not front-load the conversation with Foreman's capabilities — demonstrate them instead -- Do not push for precision on metrics they may not have yet (early-stage founders often do not have clean numbers) - -## After the Conversation - -### Populate Memory - -Create the following memory entries from what was gathered: - -**identity.yaml:** -```yaml -name: [entrepreneur name] -role: [their role] -preferred_address: [how they want to be called] -mode_solo: [true if solo founder, false otherwise] -mode_stoic: [true if requested, false by default] -language: [language code if non-English, null otherwise] -first_session: [today's date] -``` - -**company.yaml:** -```yaml -name: [company name] -description: [one-sentence description] -stage: [idea|validation|early-traction|growth|scale] -sector: [sector slug for industry pack matching] -team_size: [number] -key_roles: [list of filled roles] -funding: [bootstrapped|angel|seed|series-a|series-b+|not-applicable] -top_challenges: - - [challenge 1] - - [challenge 2] - - [challenge 3] -``` - -**active.yaml:** -```yaml -implementation_items: [] -follow_ups: [] -pending_decisions: [] -active_playbook: null -``` - -### Suggest First Action - -Based on the entrepreneur's stated challenges, recommend one concrete next step: - -> Based on what you have told me, I would recommend starting with [specific diagnostic / skill / playbook]. Here is why: [one sentence connecting their challenge to the recommendation]. - -Pick the single most impactful action. Do not overwhelm with options. - -### Mention Modes - -If relevant to their situation: - -- Solo founder detected: "Since you are building solo, I have activated Solo Mode — all frameworks will be filtered for single-founder reality. You can toggle this anytime with `/solo`." -- If they seem philosophically inclined or mention resilience/mindset: "If you value philosophical depth alongside business analysis, try `/stoic on`. It layers Stoic principles into every recommendation." -- Non-English preference detected: "I can deliver everything in [language]. Just use `/language [code]` to switch." - -### Clean Up - -After the bootstrap conversation is complete and memory is populated: -- Confirm with the entrepreneur: "Your context is saved. I will remember this across sessions." -- Delete `BOOTSTRAP.md` from the workspace. It has served its purpose. - ---- - -*Author: Fatih Guner* +All persistent data uses the shared schema in `.foreman//state.json` within the host workspace. Tools derive the correct founder scope. Do not write legacy `identity.yaml`, `company.yaml`, or dated history files as a second active store. If legacy data exists, use the explicit migration process in the package's `.claude/RUNTIME.md` and preserve the originals. diff --git a/openclaw-templates/HEARTBEAT.md b/openclaw-templates/HEARTBEAT.md index e6b88cd..6496d54 100644 --- a/openclaw-templates/HEARTBEAT.md +++ b/openclaw-templates/HEARTBEAT.md @@ -1,62 +1,12 @@ -# Heartbeat — Periodic Tasks +# Foreman check-ins -These tasks run on a schedule when heartbeat is enabled. Each one checks a condition and takes action only when triggered. Foreman does not nag — it surfaces what matters and stays quiet otherwise. +When the host runs a user-configured check-in, read actual saved work through `foreman_track` and `foreman_resume`. Scheduling belongs to the host; this file does not create a schedule. -## Task 1: Implementation Check-in +Use the same trusted founder scope as the original conversation. If that scope is unavailable, do not inspect other founders' stores. Do not scan legacy `active.yaml`, `company.yaml` or history directories as a second live database. -- **Description**: Review all in-progress implementation items and flag stalled ones. -- **Interval**: Every 7 days -- **Check**: Scan `active.yaml` → `implementation_items` for entries with state `in-progress` and no update in the last 7 days. -- **Action if triggered**: Compose a brief status summary: - > You have [N] implementation items in progress. [M] have had no update in 7+ days: [list names]. Would you like to update their status, or should we diagnose what is blocking progress? -- **Action if clear**: No message. Silence is the signal that things are on track. +- Overdue: `foreman_track` with `filter: overdue` excludes completed and abandoned items. +- Blocked: use `filter: blocked`; include the latest saved note and ask about the constraint that would change the next action. +- Stalled: use `filter: stalled`; the runtime defines this as no update for at least 14 days among active items. +- Playbook continuity: read `foreman_resume` and refer to the last confirmed checkpoint. -## Task 2: Follow-up Reminders - -- **Description**: Surface overdue follow-ups before they become forgotten commitments. -- **Interval**: Every 3 days -- **Check**: Scan `active.yaml` → `follow_ups` for entries past their `due_date`. -- **Action if triggered**: Surface the overdue items concisely: - > [N] follow-ups are overdue: [list with original due dates]. Mark as complete, reschedule, or drop? -- **Action if clear**: No message. - -## Task 3: Decision Deadline Alerts - -- **Description**: Warn about approaching decision deadlines before they arrive. -- **Interval**: Daily (when heartbeat runs) -- **Check**: Scan `active.yaml` → `pending_decisions` for entries with `deadline` within the next 3 days. -- **Action if triggered**: Alert with context: - > Decision due in [N] days: "[decision description]". You noted this on [date]. Ready to decide, or need more analysis? -- **Action if clear**: No message. - -## Task 4: Memory Staleness - -- **Description**: Prompt for a context refresh when company information may be outdated. -- **Interval**: Every 30 days -- **Check**: Read `company.yaml` → `last_updated` field. Flag if older than 90 days. -- **Action if triggered**: Prompt gently: - > Your company profile has not been updated in [N] days. Businesses change — has anything shifted in your stage, team, funding, or focus? Use `/update company` to refresh, or tell me what has changed. -- **Action if clear**: No message. - -## Task 5: Playbook Progress - -- **Description**: Check whether an active playbook is still being pursued or has quietly stalled. -- **Interval**: Every 7 days -- **Check**: If `active.yaml` → `active_playbook` exists and the current step has not advanced in 14+ days. -- **Action if triggered**: Ask directly: - > You started the [playbook name] playbook [N] days ago and are on step [X] of [Y]. No progress in 14 days. Still pursuing this, or should we pause and revisit later? -- **Action if clear**: No message. - -## Configuration - -Heartbeat tasks respect the entrepreneur's preferences: - -- **Opt-out**: The entrepreneur can disable specific tasks or all heartbeat checks. -- **Frequency override**: Custom intervals can be set per task if the defaults feel too frequent or too sparse. -- **Quiet hours**: Heartbeat messages are batched — never more than one heartbeat summary per session start. - -All heartbeat output follows the same voice rules as `SOUL.md`: concise, direct, no performative warmth. - ---- - -*Author: Fatih Guner* +Use the saved language and solo/sector context. Keep the check-in brief and specific to saved work. An empty tracker is not an invitation to invent tasks. Do not mark progress, completion or a checkpoint without confirmation. Respect the user's host notification preferences. diff --git a/openclaw.plugin.json b/openclaw.plugin.json index b5d62d2..13bdb8e 100644 --- a/openclaw.plugin.json +++ b/openclaw.plugin.json @@ -2,13 +2,17 @@ "id": "foreman", "name": "Foreman", "description": "AI-powered strategic advisor for entrepreneurs. 158 business framework skills, 24 diagnostics, 21 playbooks, 48 output templates, 9 industry packs, board simulation, implementation tracking, and research guides.", - "version": "1.0.0", + "version": "1.1.0-rc.1", "configSchema": { "type": "object", "properties": { "defaultMode": { "type": "string", - "enum": ["standard", "solo", "stoic"], + "enum": [ + "standard", + "solo", + "stoic" + ], "default": "standard", "description": "Default operating mode for Foreman" }, @@ -19,14 +23,27 @@ }, "sector": { "type": "string", - "enum": ["saas", "marketplace", "e-commerce", "fintech", "ai-ml", "healthtech", "edtech", "d2c-consumer", "agency-consulting", ""], + "enum": [ + "saas", + "marketplace", + "e-commerce", + "fintech", + "ai-ml", + "healthtech", + "edtech", + "d2c-consumer", + "agency-consulting", + "" + ], "default": "", "description": "Industry sector for pack overlay activation" } }, "additionalProperties": false }, - "skills": ["./.claude/skills/"], + "skills": [ + "./plugins/foreman/skills/" + ], "contracts": { "tools": [ "foreman_apply_skill", @@ -35,7 +52,10 @@ "foreman_list_skills", "foreman_research", "foreman_simulate", - "foreman_track" + "foreman_track", + "foreman_profile", + "foreman_update_task", + "foreman_resume" ] } } diff --git a/package-lock.json b/package-lock.json index 6009b18..11d86e2 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,24 +1,30 @@ { "name": "foreman-sh", - "version": "1.0.0", + "version": "1.1.0-rc.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "foreman-sh", - "version": "1.0.0", + "version": "1.1.0-rc.1", "license": "MIT", "dependencies": { - "@sinclair/typebox": "^0.32.0" + "@sinclair/typebox": "^0.32.0", + "yaml": "^2.8.1" }, "bin": { "foreman-sh": "bin/cli.js" }, + "devDependencies": { + "@types/node": "^22.0.0", + "openclaw": "2026.6.1", + "typescript": "~5.9.3" + }, "engines": { - "node": ">=18.0.0" + "node": ">=22.19.0" }, "peerDependencies": { - "openclaw": ">=2026.3.0" + "openclaw": ">=2026.6.1" }, "peerDependenciesMeta": { "openclaw": { @@ -31,6 +37,3825 @@ "resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.32.35.tgz", "integrity": "sha512-Ul3YyOTU++to8cgNkttakC0dWvpERr6RYoHO2W47DLbFvrwBDJUY31B1sImH6JZSYc4Kt4PyHtoPNu+vL2r2dA==", "license": "MIT" + }, + "node_modules/@types/node": { + "version": "22.20.1", + "resolved": "https://registry.npmjs.org/@types/node/-/node-22.20.1.tgz", + "integrity": "sha512-EANqOCF9QFyra+4pfxUcX9STKJpCLjMbObVzljIJomAWSnuSIEAvyzEU53GaajbXJEgdh0iEcPL+DGvpUd4k1Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "undici-types": "~6.21.0" + } + }, + "node_modules/openclaw": { + "version": "2026.6.1", + "resolved": "https://registry.npmjs.org/openclaw/-/openclaw-2026.6.1.tgz", + "integrity": "sha512-rGSwhIo8N37cQQ5puG8vmWZESE8q/ych5VFpzOQNcf49TF/rvCYyxiNAyot11qbUZF5wfLh8bsvofapnOEh0BQ==", + "dev": true, + "hasInstallScript": true, + "hasShrinkwrap": true, + "license": "MIT", + "dependencies": { + "@agentclientprotocol/sdk": "0.22.1", + "@anthropic-ai/sdk": "0.100.1", + "@clack/core": "1.3.1", + "@clack/prompts": "1.4.0", + "@earendil-works/pi-tui": "0.78.0", + "@google/genai": "2.7.0", + "@grammyjs/runner": "2.0.3", + "@grammyjs/transformer-throttler": "1.2.1", + "@homebridge/ciao": "1.3.9", + "@lydell/node-pty": "1.2.0-beta.12", + "@mistralai/mistralai": "2.2.5", + "@modelcontextprotocol/sdk": "1.29.0", + "@mozilla/readability": "0.6.0", + "@openclaw/fs-safe": "0.3.0", + "@openclaw/proxyline": "0.3.3", + "chalk": "5.6.2", + "chokidar": "5.0.0", + "clawpdf": "0.3.0", + "commander": "14.0.3", + "croner": "10.0.1", + "cross-spawn": "7.0.6", + "diff": "9.0.0", + "dotenv": "17.4.2", + "express": "5.2.1", + "file-type": "22.0.1", + "glob": "13.0.6", + "grammy": "1.43.0", + "highlight.js": "11.11.1", + "hosted-git-info": "10.1.1", + "ignore": "7.0.5", + "jiti": "2.7.0", + "json5": "2.2.3", + "jszip": "3.10.1", + "kysely": "0.29.2", + "linkedom": "0.18.12", + "minimatch": "10.2.5", + "node-edge-tts": "1.2.10", + "openai": "6.39.1", + "partial-json": "0.1.7", + "playwright-core": "1.60.0", + "proper-lockfile": "4.1.2", + "qrcode": "1.5.4", + "quickjs-wasi": "3.0.0", + "rastermill": "0.3.1", + "tar": "7.5.15", + "tree-sitter-bash": "0.25.1", + "tslog": "4.10.2", + "typebox": "1.1.39", + "typescript": "6.0.3", + "undici": "8.3.0", + "web-push": "3.6.7", + "web-tree-sitter": "0.26.9", + "ws": "8.21.0", + "yaml": "2.9.0", + "zod": "4.4.3" + }, + "bin": { + "openclaw": "openclaw.mjs" + }, + "engines": { + "node": ">=22.19.0" + }, + "optionalDependencies": { + "sqlite-vec": "0.1.9" + } + }, + "node_modules/openclaw/node_modules/@agentclientprotocol/sdk": { + "version": "0.22.1", + "resolved": "https://registry.npmjs.org/@agentclientprotocol/sdk/-/sdk-0.22.1.tgz", + "integrity": "sha512-DfqXtl/8gO9NImq094MTaCXEU2vkhh6v7q/kT+9UjZxUqj8hYaya2OjLVIqn16MzNHcXEpShTR2RIauLSYeDQQ==", + "dev": true, + "license": "Apache-2.0", + "peerDependencies": { + "zod": "^3.25.0 || ^4.0.0" + } + }, + "node_modules/openclaw/node_modules/@anthropic-ai/sdk": { + "version": "0.100.1", + "resolved": "https://registry.npmjs.org/@anthropic-ai/sdk/-/sdk-0.100.1.tgz", + "integrity": "sha512-RANcEe7LpiLczkKGOwoXOTuFdPhuubS0i4xaAKOMpcqc55YO0mukgxppV7eygx3DXNjxWT6RYOLPyOy0aIAmwg==", + "dev": true, + "license": "MIT", + "dependencies": { + "json-schema-to-ts": "^3.1.1", + "standardwebhooks": "^1.0.0" + }, + "bin": { + "anthropic-ai-sdk": "bin/cli" + }, + "peerDependencies": { + "zod": "^3.25.0 || ^4.0.0" + }, + "peerDependenciesMeta": { + "zod": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/@babel/runtime": { + "version": "7.29.7", + "resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.29.7.tgz", + "integrity": "sha512-Nq8OhGWiZIZGV6hLHoyAKLLcJihP/xFeBMGJoUrxTX2psI8dCifzLhZISFb+VWS3wFMRDmCGw5R+dOySCqPLhw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6.9.0" + } + }, + "node_modules/openclaw/node_modules/@borewit/text-codec": { + "version": "0.2.2", + "resolved": "https://registry.npmjs.org/@borewit/text-codec/-/text-codec-0.2.2.tgz", + "integrity": "sha512-DDaRehssg1aNrH4+2hnj1B7vnUGEjU6OIlyRdkMd0aUdIUvKXrJfXsy8LVtXAy7DRvYVluWbMspsRhz2lcW0mQ==", + "dev": true, + "license": "MIT", + "funding": { + "type": "github", + "url": "https://github.com/sponsors/Borewit" + } + }, + "node_modules/openclaw/node_modules/@clack/core": { + "version": "1.3.1", + "resolved": "https://registry.npmjs.org/@clack/core/-/core-1.3.1.tgz", + "integrity": "sha512-fT1qHVGAag4IEkrupZ6lRRbNCs1vS9P01KB/sG8zKgvUztbYtFBtQpjSITNwooDZ83tpsPzP0mRNs1/KVszCRA==", + "dev": true, + "license": "MIT", + "dependencies": { + "fast-wrap-ansi": "^0.2.0", + "sisteransi": "^1.0.5" + }, + "engines": { + "node": ">= 20.12.0" + } + }, + "node_modules/openclaw/node_modules/@clack/prompts": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/@clack/prompts/-/prompts-1.4.0.tgz", + "integrity": "sha512-S0My7XPGIgpRWMDG8uRqalbgT+a6FmCUdOW+HaIOVVpUPHOb7RrpvjTjiODadKp06fsrVDJZlIzc6yCTp4AnxA==", + "dev": true, + "license": "MIT", + "dependencies": { + "@clack/core": "1.3.1", + "fast-string-width": "^3.0.2", + "fast-wrap-ansi": "^0.2.0", + "sisteransi": "^1.0.5" + }, + "engines": { + "node": ">= 20.12.0" + } + }, + "node_modules/openclaw/node_modules/@earendil-works/pi-tui": { + "version": "0.78.0", + "resolved": "https://registry.npmjs.org/@earendil-works/pi-tui/-/pi-tui-0.78.0.tgz", + "integrity": "sha512-3a705FnsVVUhAyceShNB3kS2rpxcxLcx+hqB0u6MMMpHwQGbW+m++MqA6r7eOzq/8FLx5e3vDh38h/SVTk2qzw==", + "dev": true, + "license": "MIT", + "dependencies": { + "get-east-asian-width": "1.6.0", + "marked": "15.0.12" + }, + "engines": { + "node": ">=22.19.0" + } + }, + "node_modules/openclaw/node_modules/@google/genai": { + "version": "2.7.0", + "resolved": "https://registry.npmjs.org/@google/genai/-/genai-2.7.0.tgz", + "integrity": "sha512-tv0DRtcndt2oEhBYy+5mA0TaXH98+L1Gt0AP9unBfH7DP20KhB7+O3QqAN1Lz+laMARGTHS7BFQSNpLbl4gm1g==", + "dev": true, + "hasInstallScript": true, + "license": "Apache-2.0", + "dependencies": { + "google-auth-library": "^10.3.0", + "p-retry": "^4.6.2", + "protobufjs": "^7.5.4", + "ws": "^8.18.0" + }, + "engines": { + "node": ">=20.0.0" + }, + "peerDependencies": { + "@modelcontextprotocol/sdk": "^1.25.2" + }, + "peerDependenciesMeta": { + "@modelcontextprotocol/sdk": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/@grammyjs/runner": { + "version": "2.0.3", + "resolved": "https://registry.npmjs.org/@grammyjs/runner/-/runner-2.0.3.tgz", + "integrity": "sha512-nckmTs1dPWfVQteK9cxqxzE+0m1VRvluLWB8UgFzsjg62w3qthPJt0TYtJBEdG7OedvfQq4vnFAyE6iaMkR42A==", + "dev": true, + "license": "MIT", + "dependencies": { + "abort-controller": "^3.0.0" + }, + "engines": { + "node": ">=12.20.0 || >=14.13.1" + }, + "peerDependencies": { + "grammy": "^1.13.1" + } + }, + "node_modules/openclaw/node_modules/@grammyjs/transformer-throttler": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/@grammyjs/transformer-throttler/-/transformer-throttler-1.2.1.tgz", + "integrity": "sha512-CpWB0F3rJdUiKsq7826QhQsxbZi4wqfz1ccKX+fr+AOC+o8K7ZvS+wqX0suSu1QCsyUq2MDpNiKhyL2ZOJUS4w==", + "dev": true, + "license": "MIT", + "dependencies": { + "bottleneck": "^2.0.0" + }, + "engines": { + "node": "^12.20.0 || >=14.13.1" + }, + "peerDependencies": { + "grammy": "^1.0.0" + } + }, + "node_modules/openclaw/node_modules/@grammyjs/types": { + "version": "3.27.3", + "resolved": "https://registry.npmjs.org/@grammyjs/types/-/types-3.27.3.tgz", + "integrity": "sha512-yUKMLliGsGbnxu96YUJ7km7B0zy4PzeH/Jvti5705R/LeKDMqkDV4DckMSt+OrliWQpTwQljHE0QLol5zgxBkg==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/@homebridge/ciao": { + "version": "1.3.9", + "resolved": "https://registry.npmjs.org/@homebridge/ciao/-/ciao-1.3.9.tgz", + "integrity": "sha512-TMy9zy173jDOpnFXDqL3BPIQn5lfcAkSsivYQatCCakoHk4fLGd7QjfAaNGYE3Ox+/ZI6Lq0e1gGcz1qdw/IbA==", + "dev": true, + "license": "MIT", + "dependencies": { + "debug": "^4.4.3", + "fast-deep-equal": "^3.1.3", + "source-map-support": "^0.5.21", + "tslib": "^2.8.1" + }, + "bin": { + "ciao-bcs": "lib/bonjour-conformance-testing.js" + } + }, + "node_modules/openclaw/node_modules/@hono/node-server": { + "version": "1.19.14", + "resolved": "https://registry.npmjs.org/@hono/node-server/-/node-server-1.19.14.tgz", + "integrity": "sha512-GwtvgtXxnWsucXvbQXkRgqksiH2Qed37H9xHZocE5sA3N8O8O8/8FA3uclQXxXVzc9XBZuEOMK7+r02FmSpHtw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18.14.1" + }, + "peerDependencies": { + "hono": "^4" + } + }, + "node_modules/openclaw/node_modules/@isaacs/fs-minipass": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/@isaacs/fs-minipass/-/fs-minipass-4.0.1.tgz", + "integrity": "sha512-wgm9Ehl2jpeqP3zw/7mo3kRHFp5MEDhqAdwy1fTGkHAwnkGOVsgpvQhL8B5n1qlb01jV3n/bI0ZfZp5lWA1k4w==", + "dev": true, + "license": "ISC", + "dependencies": { + "minipass": "^7.0.4" + }, + "engines": { + "node": ">=18.0.0" + } + }, + "node_modules/openclaw/node_modules/@lydell/node-pty": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty/-/node-pty-1.2.0-beta.12.tgz", + "integrity": "sha512-qIK890UwPupoj07osVvgOIa++1mxeHbcGry4PKRHhNVNs81V2SCG34eJr46GybiOmBtc8Sj5PB1/GGM5PL549g==", + "dev": true, + "license": "MIT", + "optionalDependencies": { + "@lydell/node-pty-darwin-arm64": "1.2.0-beta.12", + "@lydell/node-pty-darwin-x64": "1.2.0-beta.12", + "@lydell/node-pty-linux-arm64": "1.2.0-beta.12", + "@lydell/node-pty-linux-x64": "1.2.0-beta.12", + "@lydell/node-pty-win32-arm64": "1.2.0-beta.12", + "@lydell/node-pty-win32-x64": "1.2.0-beta.12" + } + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-darwin-arm64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-darwin-arm64/-/node-pty-darwin-arm64-1.2.0-beta.12.tgz", + "integrity": "sha512-tqaifcY9Cr41SblO1+FLzh8oxxtkNhuW9Dhl22lKme9BreYvKvxEZcdPIXTuqkJc5tagOEC4QHShKmJjLyLXLQ==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "darwin" + ] + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-darwin-x64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-darwin-x64/-/node-pty-darwin-x64-1.2.0-beta.12.tgz", + "integrity": "sha512-4LrS5pCJwqHKDVf1zS2gyNV0m4hKAXch+XZNhbZ6LY8uwVL8BhchzQBO40Os5anuRxRCWzHpw4Sp64Ie8q7E4Q==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "darwin" + ] + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-linux-arm64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-linux-arm64/-/node-pty-linux-arm64-1.2.0-beta.12.tgz", + "integrity": "sha512-Sx+A71x5BDGHt9ansfrtGxwq2VFVDWvJUAdlUL0Hv0qeiJUfts+hgopx+CgT4PSwahKjdEgtu0+FAfY9rICKRw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ] + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-linux-x64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-linux-x64/-/node-pty-linux-x64-1.2.0-beta.12.tgz", + "integrity": "sha512-bJzs94njofYhGg/UDqW1nj0dtvvu+2OvxMY+RlLS1T17VgcktKoIR6PuenTwE5HJ/D6StCPADmXcT0nNsCKmIQ==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "linux" + ] + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-win32-arm64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-win32-arm64/-/node-pty-win32-arm64-1.2.0-beta.12.tgz", + "integrity": "sha512-p7POgjVEiFaBC3/y+AKuV1FzePCsJ6HmZDv2XK+jBZSfwP8+uBAw181ZiKYN1YuRa/XpmBGaWezcI8hZkbW++g==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "win32" + ] + }, + "node_modules/openclaw/node_modules/@lydell/node-pty-win32-x64": { + "version": "1.2.0-beta.12", + "resolved": "https://registry.npmjs.org/@lydell/node-pty-win32-x64/-/node-pty-win32-x64-1.2.0-beta.12.tgz", + "integrity": "sha512-IDFa00g7qUDGUYgByrUBJtC+mOjYVt/8KYyWivCg5JjGOHbBUACUQZLl0jTWmnr+tld/UyTpX90a2PY6oTVtRw==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT", + "optional": true, + "os": [ + "win32" + ] + }, + "node_modules/openclaw/node_modules/@mistralai/mistralai": { + "version": "2.2.5", + "resolved": "https://registry.npmjs.org/@mistralai/mistralai/-/mistralai-2.2.5.tgz", + "integrity": "sha512-ATbWzKkNzNAZ+gtw9MI/c/ULTMG80tKUiRNIbQFfg4OP0uEZZpTfXZeBCNfs5Dq0uqMQ/tQWc4o6RRJQtMrpDA==", + "dev": true, + "license": "Apache-2.0", + "dependencies": { + "ws": "^8.18.0", + "zod": "^3.25.0 || ^4.0.0", + "zod-to-json-schema": "^3.25.0" + } + }, + "node_modules/openclaw/node_modules/@modelcontextprotocol/sdk": { + "version": "1.29.0", + "resolved": "https://registry.npmjs.org/@modelcontextprotocol/sdk/-/sdk-1.29.0.tgz", + "integrity": "sha512-zo37mZA9hJWpULgkRpowewez1y6ML5GsXJPY8FI0tBBCd77HEvza4jDqRKOXgHNn867PVGCyTdzqpz0izu5ZjQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "@hono/node-server": "^1.19.9", + "ajv": "^8.17.1", + "ajv-formats": "^3.0.1", + "content-type": "^1.0.5", + "cors": "^2.8.5", + "cross-spawn": "^7.0.5", + "eventsource": "^3.0.2", + "eventsource-parser": "^3.0.0", + "express": "^5.2.1", + "express-rate-limit": "^8.2.1", + "hono": "^4.11.4", + "jose": "^6.1.3", + "json-schema-typed": "^8.0.2", + "pkce-challenge": "^5.0.0", + "raw-body": "^3.0.0", + "zod": "^3.25 || ^4.0", + "zod-to-json-schema": "^3.25.1" + }, + "engines": { + "node": ">=18" + }, + "peerDependencies": { + "@cfworker/json-schema": "^4.1.1", + "zod": "^3.25 || ^4.0" + }, + "peerDependenciesMeta": { + "@cfworker/json-schema": { + "optional": true + }, + "zod": { + "optional": false + } + } + }, + "node_modules/openclaw/node_modules/@mozilla/readability": { + "version": "0.6.0", + "resolved": "https://registry.npmjs.org/@mozilla/readability/-/readability-0.6.0.tgz", + "integrity": "sha512-juG5VWh4qAivzTAeMzvY9xs9HY5rAcr2E4I7tiSSCokRFi7XIZCAu92ZkSTsIj1OPceCifL3cpfteP3pDT9/QQ==", + "dev": true, + "license": "Apache-2.0", + "engines": { + "node": ">=14.0.0" + } + }, + "node_modules/openclaw/node_modules/@openclaw/fs-safe": { + "version": "0.3.0", + "resolved": "https://registry.npmjs.org/@openclaw/fs-safe/-/fs-safe-0.3.0.tgz", + "integrity": "sha512-uIBE441CIt1kIURoP9qRGKZ8LkGyfD9ZzeESjwAd29ZPWtghws/5GR3Pjb67jKdcJHP1I6roNXcvnhzAU7lHlA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=20.11" + }, + "optionalDependencies": { + "jszip": "^3.10.1", + "tar": "7.5.13" + } + }, + "node_modules/openclaw/node_modules/@openclaw/proxyline": { + "version": "0.3.3", + "resolved": "https://registry.npmjs.org/@openclaw/proxyline/-/proxyline-0.3.3.tgz", + "integrity": "sha512-sftHnW69NHQqLjCxBTvQ8f/eQl+peZ5pHCBQtuTWBbeuYRHZ0/GXVTmw/O/YKsShMbqPWhJB0UYtPPdvCUSS8w==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=22.19.0" + }, + "peerDependencies": { + "undici": ">=8.3.0 <9" + } + }, + "node_modules/openclaw/node_modules/@silvia-odwyer/photon-node": { + "version": "0.3.4", + "resolved": "https://registry.npmjs.org/@silvia-odwyer/photon-node/-/photon-node-0.3.4.tgz", + "integrity": "sha512-bnly4BKB3KDTFxrUIcgCLbaeVVS8lrAkri1pEzskpmxu9MdfGQTy8b8EgcD83ywD3RPMsIulY8xJH5Awa+t9fA==", + "dev": true, + "license": "Apache-2.0" + }, + "node_modules/openclaw/node_modules/@stablelib/base64": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/@stablelib/base64/-/base64-1.0.1.tgz", + "integrity": "sha512-1bnPQqSxSuc3Ii6MhBysoWCg58j97aUjuCSZrGSmDxNqtytIi0k8utUenAwTZN4V5mXXYGsVUI9zeBqy+jBOSQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/@tokenizer/inflate": { + "version": "0.4.1", + "resolved": "https://registry.npmjs.org/@tokenizer/inflate/-/inflate-0.4.1.tgz", + "integrity": "sha512-2mAv+8pkG6GIZiF1kNg1jAjh27IDxEPKwdGul3snfztFerfPGI1LjDezZp3i7BElXompqEtPmoPx6c2wgtWsOA==", + "dev": true, + "license": "MIT", + "dependencies": { + "debug": "^4.4.3", + "token-types": "^6.1.1" + }, + "engines": { + "node": ">=18" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/Borewit" + } + }, + "node_modules/openclaw/node_modules/@tokenizer/token": { + "version": "0.3.0", + "resolved": "https://registry.npmjs.org/@tokenizer/token/-/token-0.3.0.tgz", + "integrity": "sha512-OvjF+z51L3ov0OyAU0duzsYuvO01PH7x4t6DJx+guahgTnBHkhJdG7soQeTSFLWN3efnHyibZ4Z8l2EuWwJN3A==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/@types/retry": { + "version": "0.12.5", + "resolved": "https://registry.npmjs.org/@types/retry/-/retry-0.12.5.tgz", + "integrity": "sha512-3xSjTp3v03X/lSQLkczaN9UIEwJMoMCA1+Nb5HfbJEQWogdeQIyVtTvxPXDQjZ5zws8rFQfVfRdz03ARihPJgw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/abort-controller": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/abort-controller/-/abort-controller-3.0.0.tgz", + "integrity": "sha512-h8lQ8tacZYnR3vNQTgibj+tODHI5/+l06Au2Pcriv/Gmet0eaj4TwWH41sO9wnHDiQsEj19q0drzdWdeAHtweg==", + "dev": true, + "license": "MIT", + "dependencies": { + "event-target-shim": "^5.0.0" + }, + "engines": { + "node": ">=6.5" + } + }, + "node_modules/openclaw/node_modules/accepts": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/accepts/-/accepts-2.0.0.tgz", + "integrity": "sha512-5cvg6CtKwfgdmVqY1WIiXKc3Q1bkRqGLi+2W/6ao+6Y7gu/RCwRuAhGEzh5B4KlszSuTLgZYuqFqo5bImjNKng==", + "dev": true, + "license": "MIT", + "dependencies": { + "mime-types": "^3.0.0", + "negotiator": "^1.0.0" + }, + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/agent-base": { + "version": "7.1.4", + "resolved": "https://registry.npmjs.org/agent-base/-/agent-base-7.1.4.tgz", + "integrity": "sha512-MnA+YT8fwfJPgBx3m60MNqakm30XOkyIoH1y6huTQvC0PwZG7ki8NacLBcrPbNoo8vEZy7Jpuk7+jMO+CUovTQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 14" + } + }, + "node_modules/openclaw/node_modules/ajv": { + "version": "8.20.0", + "resolved": "https://registry.npmjs.org/ajv/-/ajv-8.20.0.tgz", + "integrity": "sha512-Thbli+OlOj+iMPYFBVBfJ3OmCAnaSyNn4M1vz9T6Gka5Jt9ba/HIR56joy65tY6kx/FCF5VXNB819Y7/GUrBGA==", + "dev": true, + "license": "MIT", + "dependencies": { + "fast-deep-equal": "^3.1.3", + "fast-uri": "^3.0.1", + "json-schema-traverse": "^1.0.0", + "require-from-string": "^2.0.2" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/epoberezkin" + } + }, + "node_modules/openclaw/node_modules/ajv-formats": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/ajv-formats/-/ajv-formats-3.0.1.tgz", + "integrity": "sha512-8iUql50EUR+uUcdRQ3HDqa6EVyo3docL8g5WJ3FNcWmu62IbkGUue/pEyLBW8VGKKucTPgqeks4fIU1DA4yowQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "ajv": "^8.0.0" + }, + "peerDependencies": { + "ajv": "^8.0.0" + }, + "peerDependenciesMeta": { + "ajv": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/ansi-regex": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", + "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/ansi-styles": { + "version": "4.3.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz", + "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==", + "dev": true, + "license": "MIT", + "dependencies": { + "color-convert": "^2.0.1" + }, + "engines": { + "node": ">=8" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/asn1.js": { + "version": "5.4.1", + "resolved": "https://registry.npmjs.org/asn1.js/-/asn1.js-5.4.1.tgz", + "integrity": "sha512-+I//4cYPccV8LdmBLiX8CYvf9Sp3vQsrqu2QNXRcrbiWvcx/UdlFiqUJJzxRQxgsZmvhXhn4cSKeSmoFjVdupA==", + "dev": true, + "license": "MIT", + "dependencies": { + "bn.js": "^4.0.0", + "inherits": "^2.0.1", + "minimalistic-assert": "^1.0.0", + "safer-buffer": "^2.1.0" + } + }, + "node_modules/openclaw/node_modules/balanced-match": { + "version": "4.0.4", + "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-4.0.4.tgz", + "integrity": "sha512-BLrgEcRTwX2o6gGxGOCNyMvGSp35YofuYzw9h1IMTRmKqttAZZVU67bdb9Pr2vUHA8+j3i2tJfjO6C6+4myGTA==", + "dev": true, + "license": "MIT", + "engines": { + "node": "18 || 20 || >=22" + } + }, + "node_modules/openclaw/node_modules/base64-js": { + "version": "1.5.1", + "resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz", + "integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/feross" + }, + { + "type": "patreon", + "url": "https://www.patreon.com/feross" + }, + { + "type": "consulting", + "url": "https://feross.org/support" + } + ], + "license": "MIT" + }, + "node_modules/openclaw/node_modules/bignumber.js": { + "version": "9.3.1", + "resolved": "https://registry.npmjs.org/bignumber.js/-/bignumber.js-9.3.1.tgz", + "integrity": "sha512-Ko0uX15oIUS7wJ3Rb30Fs6SkVbLmPBAKdlm7q9+ak9bbIeFf0MwuBsQV6z7+X768/cHsfg+WlysDWJcmthjsjQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": "*" + } + }, + "node_modules/openclaw/node_modules/bn.js": { + "version": "4.12.3", + "resolved": "https://registry.npmjs.org/bn.js/-/bn.js-4.12.3.tgz", + "integrity": "sha512-fGTi3gxV/23FTYdAoUtLYp6qySe2KE3teyZitipKNRuVYcBkoP/bB3guXN/XVKUe9mxCHXnc9C4ocyz8OmgN0g==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/body-parser": { + "version": "2.2.2", + "resolved": "https://registry.npmjs.org/body-parser/-/body-parser-2.2.2.tgz", + "integrity": "sha512-oP5VkATKlNwcgvxi0vM0p/D3n2C3EReYVX+DNYs5TjZFn/oQt2j+4sVJtSMr18pdRr8wjTcBl6LoV+FUwzPmNA==", + "dev": true, + "license": "MIT", + "dependencies": { + "bytes": "^3.1.2", + "content-type": "^1.0.5", + "debug": "^4.4.3", + "http-errors": "^2.0.0", + "iconv-lite": "^0.7.0", + "on-finished": "^2.4.1", + "qs": "^6.14.1", + "raw-body": "^3.0.1", + "type-is": "^2.0.1" + }, + "engines": { + "node": ">=18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/boolbase": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz", + "integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/bottleneck": { + "version": "2.19.5", + "resolved": "https://registry.npmjs.org/bottleneck/-/bottleneck-2.19.5.tgz", + "integrity": "sha512-VHiNCbI1lKdl44tGrhNfU3lup0Tj/ZBMJB5/2ZbNXRCPuRCO7ed2mgcK4r17y+KB2EfuYuRaVlwNbAeaWGSpbw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/brace-expansion": { + "version": "5.0.6", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.6.tgz", + "integrity": "sha512-kLpxurY4Z4r9sgMsyG0Z9uzsBlgiU/EFKhj/h91/8yHu0edo7XuixOIH3VcJ8kkxs6/jPzoI6U9Vj3WqbMQ94g==", + "dev": true, + "license": "MIT", + "dependencies": { + "balanced-match": "^4.0.2" + }, + "engines": { + "node": "18 || 20 || >=22" + } + }, + "node_modules/openclaw/node_modules/buffer-equal-constant-time": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/buffer-equal-constant-time/-/buffer-equal-constant-time-1.0.1.tgz", + "integrity": "sha512-zRpUiDwd/xk6ADqPMATG8vc9VPrkck7T07OIx0gnjmJAnHnTVXNQG3vfvWNuiZIkwu9KrKdA1iJKfsfTVxE6NA==", + "dev": true, + "license": "BSD-3-Clause" + }, + "node_modules/openclaw/node_modules/buffer-from": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz", + "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/bytes": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/bytes/-/bytes-3.1.2.tgz", + "integrity": "sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/call-bind-apply-helpers": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/call-bind-apply-helpers/-/call-bind-apply-helpers-1.0.2.tgz", + "integrity": "sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "es-errors": "^1.3.0", + "function-bind": "^1.1.2" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/call-bound": { + "version": "1.0.4", + "resolved": "https://registry.npmjs.org/call-bound/-/call-bound-1.0.4.tgz", + "integrity": "sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==", + "dev": true, + "license": "MIT", + "dependencies": { + "call-bind-apply-helpers": "^1.0.2", + "get-intrinsic": "^1.3.0" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/camelcase": { + "version": "5.3.1", + "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz", + "integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/chalk": { + "version": "5.6.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-5.6.2.tgz", + "integrity": "sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==", + "dev": true, + "license": "MIT", + "engines": { + "node": "^12.17.0 || ^14.13 || >=16.0.0" + }, + "funding": { + "url": "https://github.com/chalk/chalk?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/chokidar": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-5.0.0.tgz", + "integrity": "sha512-TQMmc3w+5AxjpL8iIiwebF73dRDF4fBIieAqGn9RGCWaEVwQ6Fb2cGe31Yns0RRIzii5goJ1Y7xbMwo1TxMplw==", + "dev": true, + "license": "MIT", + "dependencies": { + "readdirp": "^5.0.0" + }, + "engines": { + "node": ">= 20.19.0" + }, + "funding": { + "url": "https://paulmillr.com/funding/" + } + }, + "node_modules/openclaw/node_modules/chownr": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/chownr/-/chownr-3.0.0.tgz", + "integrity": "sha512-+IxzY9BZOQd/XuYPRmrvEVjF/nqj5kgT4kEq7VofrDoM1MxoRjEWkrCC3EtLi59TVawxTAn+orJwFQcrqEN1+g==", + "dev": true, + "license": "BlueOak-1.0.0", + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/clawpdf": { + "version": "0.3.0", + "resolved": "https://registry.npmjs.org/clawpdf/-/clawpdf-0.3.0.tgz", + "integrity": "sha512-41+3AnKk9yek2sm+/9XvUlDTN8Wi+ag7fmxZuqw+ySn4lqaf/fCgLeamqPLiXY4gVbizKEHGoTG/JrIIFNE2rw==", + "dev": true, + "license": "MIT", + "bin": { + "clawpdf": "dist/cli.js" + }, + "engines": { + "node": ">=20" + } + }, + "node_modules/openclaw/node_modules/cliui": { + "version": "8.0.1", + "resolved": "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz", + "integrity": "sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==", + "dev": true, + "license": "ISC", + "dependencies": { + "string-width": "^4.2.0", + "strip-ansi": "^6.0.1", + "wrap-ansi": "^7.0.0" + }, + "engines": { + "node": ">=12" + } + }, + "node_modules/openclaw/node_modules/color-convert": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz", + "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "color-name": "~1.1.4" + }, + "engines": { + "node": ">=7.0.0" + } + }, + "node_modules/openclaw/node_modules/color-name": { + "version": "1.1.4", + "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz", + "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/commander": { + "version": "14.0.3", + "resolved": "https://registry.npmjs.org/commander/-/commander-14.0.3.tgz", + "integrity": "sha512-H+y0Jo/T1RZ9qPP4Eh1pkcQcLRglraJaSLoyOtHxu6AapkjWVCy2Sit1QQ4x3Dng8qDlSsZEet7g5Pq06MvTgw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=20" + } + }, + "node_modules/openclaw/node_modules/content-disposition": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/content-disposition/-/content-disposition-1.1.0.tgz", + "integrity": "sha512-5jRCH9Z/+DRP7rkvY83B+yGIGX96OYdJmzngqnw2SBSxqCFPd0w2km3s5iawpGX8krnwSGmF0FW5Nhr0Hfai3g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/content-type": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/content-type/-/content-type-1.0.5.tgz", + "integrity": "sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/cookie": { + "version": "0.7.2", + "resolved": "https://registry.npmjs.org/cookie/-/cookie-0.7.2.tgz", + "integrity": "sha512-yki5XnKuf750l50uGTllt6kKILY4nQ1eNIQatoXEByZ5dWgnKqbnqmTrBE5B4N7lrMJKQ2ytWMiTO2o0v6Ew/w==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/cookie-signature": { + "version": "1.2.2", + "resolved": "https://registry.npmjs.org/cookie-signature/-/cookie-signature-1.2.2.tgz", + "integrity": "sha512-D76uU73ulSXrD1UXF4KE2TMxVVwhsnCgfAyTg9k8P6KGZjlXKrOLe4dJQKI3Bxi5wjesZoFXJWElNWBjPZMbhg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6.6.0" + } + }, + "node_modules/openclaw/node_modules/core-util-is": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.3.tgz", + "integrity": "sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/cors": { + "version": "2.8.6", + "resolved": "https://registry.npmjs.org/cors/-/cors-2.8.6.tgz", + "integrity": "sha512-tJtZBBHA6vjIAaF6EnIaq6laBBP9aq/Y3ouVJjEfoHbRBcHBAHYcMh/w8LDrk2PvIMMq8gmopa5D4V8RmbrxGw==", + "dev": true, + "license": "MIT", + "dependencies": { + "object-assign": "^4", + "vary": "^1" + }, + "engines": { + "node": ">= 0.10" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/croner": { + "version": "10.0.1", + "resolved": "https://registry.npmjs.org/croner/-/croner-10.0.1.tgz", + "integrity": "sha512-ixNtAJndqh173VQ4KodSdJEI6nuioBWI0V1ITNKhZZsO0pEMoDxz539T4FTTbSZ/xIOSuDnzxLVRqBVSvPNE2g==", + "dev": true, + "funding": [ + { + "type": "other", + "url": "https://paypal.me/hexagonpp" + }, + { + "type": "github", + "url": "https://github.com/sponsors/hexagon" + } + ], + "license": "MIT", + "engines": { + "node": ">=18.0" + } + }, + "node_modules/openclaw/node_modules/cross-spawn": { + "version": "7.0.6", + "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz", + "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==", + "dev": true, + "license": "MIT", + "dependencies": { + "path-key": "^3.1.0", + "shebang-command": "^2.0.0", + "which": "^2.0.1" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/openclaw/node_modules/css-select": { + "version": "5.2.2", + "resolved": "https://registry.npmjs.org/css-select/-/css-select-5.2.2.tgz", + "integrity": "sha512-TizTzUddG/xYLA3NXodFM0fSbNizXjOKhqiQQwvhlspadZokn1KDy0NZFS0wuEubIYAV5/c1/lAr0TaaFXEXzw==", + "dev": true, + "license": "BSD-2-Clause", + "dependencies": { + "boolbase": "^1.0.0", + "css-what": "^6.1.0", + "domhandler": "^5.0.2", + "domutils": "^3.0.1", + "nth-check": "^2.0.1" + }, + "funding": { + "url": "https://github.com/sponsors/fb55" + } + }, + "node_modules/openclaw/node_modules/css-what": { + "version": "6.2.2", + "resolved": "https://registry.npmjs.org/css-what/-/css-what-6.2.2.tgz", + "integrity": "sha512-u/O3vwbptzhMs3L1fQE82ZSLHQQfto5gyZzwteVIEyeaY5Fc7R4dapF/BvRoSYFeqfBk4m0V1Vafq5Pjv25wvA==", + "dev": true, + "license": "BSD-2-Clause", + "engines": { + "node": ">= 6" + }, + "funding": { + "url": "https://github.com/sponsors/fb55" + } + }, + "node_modules/openclaw/node_modules/cssom": { + "version": "0.5.0", + "resolved": "https://registry.npmjs.org/cssom/-/cssom-0.5.0.tgz", + "integrity": "sha512-iKuQcq+NdHqlAcwUY0o/HL69XQrUaQdMjmStJ8JFmUaiiQErlhrmuigkg/CU4E2J0IyUKUrMAgl36TvN67MqTw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/data-uri-to-buffer": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/data-uri-to-buffer/-/data-uri-to-buffer-4.0.1.tgz", + "integrity": "sha512-0R9ikRb668HB7QDxT1vkpuUBtqc53YyAwMwGeUFKRojY/NWKvdZ+9UYtRfGmhqNbRkTSVpMbmyhXipFFv2cb/A==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 12" + } + }, + "node_modules/openclaw/node_modules/debug": { + "version": "4.4.3", + "resolved": "https://registry.npmjs.org/debug/-/debug-4.4.3.tgz", + "integrity": "sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==", + "dev": true, + "license": "MIT", + "dependencies": { + "ms": "^2.1.3" + }, + "engines": { + "node": ">=6.0" + }, + "peerDependenciesMeta": { + "supports-color": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/decamelize": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/decamelize/-/decamelize-1.2.0.tgz", + "integrity": "sha512-z2S+W9X73hAUUki+N+9Za2lBlun89zigOyGrsax+KUQ6wKW4ZoWpEYBkGhQjwAjjDCkWxhY0VKEhk8wzY7F5cA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/openclaw/node_modules/depd": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/depd/-/depd-2.0.0.tgz", + "integrity": "sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/diff": { + "version": "9.0.0", + "resolved": "https://registry.npmjs.org/diff/-/diff-9.0.0.tgz", + "integrity": "sha512-svtcdpS8CgJyqAjEQIXdb3OjhFVVYjzGAPO8WGCmRbrml64SPw/jJD4GoE98aR7r25A0XcgrK3F02yw9R/vhQw==", + "dev": true, + "license": "BSD-3-Clause", + "engines": { + "node": ">=0.3.1" + } + }, + "node_modules/openclaw/node_modules/dijkstrajs": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/dijkstrajs/-/dijkstrajs-1.0.3.tgz", + "integrity": "sha512-qiSlmBq9+BCdCA/L46dw8Uy93mloxsPSbwnm5yrKn2vMPiy8KyAskTF6zuV/j5BMsmOGZDPs7KjU+mjb670kfA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/dom-serializer": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz", + "integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==", + "dev": true, + "license": "MIT", + "dependencies": { + "domelementtype": "^2.3.0", + "domhandler": "^5.0.2", + "entities": "^4.2.0" + }, + "funding": { + "url": "https://github.com/cheeriojs/dom-serializer?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/domelementtype": { + "version": "2.3.0", + "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz", + "integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ], + "license": "BSD-2-Clause" + }, + "node_modules/openclaw/node_modules/domhandler": { + "version": "5.0.3", + "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz", + "integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==", + "dev": true, + "license": "BSD-2-Clause", + "dependencies": { + "domelementtype": "^2.3.0" + }, + "engines": { + "node": ">= 4" + }, + "funding": { + "url": "https://github.com/fb55/domhandler?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/domutils": { + "version": "3.2.2", + "resolved": "https://registry.npmjs.org/domutils/-/domutils-3.2.2.tgz", + "integrity": "sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==", + "dev": true, + "license": "BSD-2-Clause", + "dependencies": { + "dom-serializer": "^2.0.0", + "domelementtype": "^2.3.0", + "domhandler": "^5.0.3" + }, + "funding": { + "url": "https://github.com/fb55/domutils?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/dotenv": { + "version": "17.4.2", + "resolved": "https://registry.npmjs.org/dotenv/-/dotenv-17.4.2.tgz", + "integrity": "sha512-nI4U3TottKAcAD9LLud4Cb7b2QztQMUEfHbvhTH09bqXTxnSie8WnjPALV/WMCrJZ6UV/qHJ6L03OqO3LcdYZw==", + "dev": true, + "license": "BSD-2-Clause", + "engines": { + "node": ">=12" + }, + "funding": { + "url": "https://dotenvx.com" + } + }, + "node_modules/openclaw/node_modules/dunder-proto": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/dunder-proto/-/dunder-proto-1.0.1.tgz", + "integrity": "sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==", + "dev": true, + "license": "MIT", + "dependencies": { + "call-bind-apply-helpers": "^1.0.1", + "es-errors": "^1.3.0", + "gopd": "^1.2.0" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/ecdsa-sig-formatter": { + "version": "1.0.11", + "resolved": "https://registry.npmjs.org/ecdsa-sig-formatter/-/ecdsa-sig-formatter-1.0.11.tgz", + "integrity": "sha512-nagl3RYrbNv6kQkeJIpt6NJZy8twLB/2vtz6yN9Z4vRKHN4/QZJIEbqohALSgwKdnksuY3k5Addp5lg8sVoVcQ==", + "dev": true, + "license": "Apache-2.0", + "dependencies": { + "safe-buffer": "^5.0.1" + } + }, + "node_modules/openclaw/node_modules/ee-first": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz", + "integrity": "sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/emoji-regex": { + "version": "8.0.0", + "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz", + "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/encodeurl": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/encodeurl/-/encodeurl-2.0.0.tgz", + "integrity": "sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/entities": { + "version": "4.5.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz", + "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==", + "dev": true, + "license": "BSD-2-Clause", + "engines": { + "node": ">=0.12" + }, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/es-define-property": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/es-define-property/-/es-define-property-1.0.1.tgz", + "integrity": "sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/es-errors": { + "version": "1.3.0", + "resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz", + "integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/es-object-atoms": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/es-object-atoms/-/es-object-atoms-1.1.2.tgz", + "integrity": "sha512-HWcBoN6NileqtSydK2FqHbS/LoDd2pqrnQHLyJzBj4kOp/ky2MWMN694xOfkK8/SnUsW2DH7EfyVlydKCsm1Zw==", + "dev": true, + "license": "MIT", + "dependencies": { + "es-errors": "^1.3.0" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/escalade": { + "version": "3.2.0", + "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz", + "integrity": "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/escape-html": { + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.3.tgz", + "integrity": "sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/etag": { + "version": "1.8.1", + "resolved": "https://registry.npmjs.org/etag/-/etag-1.8.1.tgz", + "integrity": "sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/event-target-shim": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/event-target-shim/-/event-target-shim-5.0.1.tgz", + "integrity": "sha512-i/2XbnSz/uxRCU6+NdVJgKWDTM427+MqYbkQzD321DuCQJUqOuJKIA0IM2+W2xtYHdKOmZ4dR6fExsd4SXL+WQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/eventsource": { + "version": "3.0.7", + "resolved": "https://registry.npmjs.org/eventsource/-/eventsource-3.0.7.tgz", + "integrity": "sha512-CRT1WTyuQoD771GW56XEZFQ/ZoSfWid1alKGDYMmkt2yl8UXrVR4pspqWNEcqKvVIzg6PAltWjxcSSPrboA4iA==", + "dev": true, + "license": "MIT", + "dependencies": { + "eventsource-parser": "^3.0.1" + }, + "engines": { + "node": ">=18.0.0" + } + }, + "node_modules/openclaw/node_modules/eventsource-parser": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/eventsource-parser/-/eventsource-parser-3.1.0.tgz", + "integrity": "sha512-kJezFj9YFAMLeORyi7aCLxLbD5/qWMQnoMVlVPyHIll7lgRJCc3JVln9Vgl9nwQi0YkMnhdGTMNn7CkRRAptMg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18.0.0" + } + }, + "node_modules/openclaw/node_modules/express": { + "version": "5.2.1", + "resolved": "https://registry.npmjs.org/express/-/express-5.2.1.tgz", + "integrity": "sha512-hIS4idWWai69NezIdRt2xFVofaF4j+6INOpJlVOLDO8zXGpUVEVzIYk12UUi2JzjEzWL3IOAxcTubgz9Po0yXw==", + "dev": true, + "license": "MIT", + "dependencies": { + "accepts": "^2.0.0", + "body-parser": "^2.2.1", + "content-disposition": "^1.0.0", + "content-type": "^1.0.5", + "cookie": "^0.7.1", + "cookie-signature": "^1.2.1", + "debug": "^4.4.0", + "depd": "^2.0.0", + "encodeurl": "^2.0.0", + "escape-html": "^1.0.3", + "etag": "^1.8.1", + "finalhandler": "^2.1.0", + "fresh": "^2.0.0", + "http-errors": "^2.0.0", + "merge-descriptors": "^2.0.0", + "mime-types": "^3.0.0", + "on-finished": "^2.4.1", + "once": "^1.4.0", + "parseurl": "^1.3.3", + "proxy-addr": "^2.0.7", + "qs": "^6.14.0", + "range-parser": "^1.2.1", + "router": "^2.2.0", + "send": "^1.1.0", + "serve-static": "^2.2.0", + "statuses": "^2.0.1", + "type-is": "^2.0.1", + "vary": "^1.1.2" + }, + "engines": { + "node": ">= 18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/express-rate-limit": { + "version": "8.5.2", + "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-8.5.2.tgz", + "integrity": "sha512-5Kb34ipNX694DH48vN9irak1Qx30nb0PLYHXfJgw4YEjiC3ZEmZJhwOp+VfiCYwFzvFTdB9QkArYS5kXa2cx2A==", + "dev": true, + "license": "MIT", + "dependencies": { + "ip-address": "^10.2.0" + }, + "engines": { + "node": ">= 16" + }, + "funding": { + "url": "https://github.com/sponsors/express-rate-limit" + }, + "peerDependencies": { + "express": ">= 4.11" + } + }, + "node_modules/openclaw/node_modules/extend": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz", + "integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/fast-deep-equal": { + "version": "3.1.3", + "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", + "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/fast-sha256": { + "version": "1.3.0", + "resolved": "https://registry.npmjs.org/fast-sha256/-/fast-sha256-1.3.0.tgz", + "integrity": "sha512-n11RGP/lrWEFI/bWdygLxhI+pVeo1ZYIVwvvPkW7azl/rOy+F3HYRZ2K5zeE9mmkhQppyv9sQFx0JM9UabnpPQ==", + "dev": true, + "license": "Unlicense" + }, + "node_modules/openclaw/node_modules/fast-string-truncated-width": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/fast-string-truncated-width/-/fast-string-truncated-width-3.0.3.tgz", + "integrity": "sha512-0jjjIEL6+0jag3l2XWWizO64/aZVtpiGE3t0Zgqxv0DPuxiMjvB3M24fCyhZUO4KomJQPj3LTSUnDP3GpdwC0g==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/fast-string-width": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/fast-string-width/-/fast-string-width-3.0.2.tgz", + "integrity": "sha512-gX8LrtNEI5hq8DVUfRQMbr5lpaS4nMIWV+7XEbXk2b8kiQIizgnlr12B4dA3ZEx3308ze0O4Q1R+cHts8kyUJg==", + "dev": true, + "license": "MIT", + "dependencies": { + "fast-string-truncated-width": "^3.0.2" + } + }, + "node_modules/openclaw/node_modules/fast-uri": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/fast-uri/-/fast-uri-3.1.2.tgz", + "integrity": "sha512-rVjf7ArG3LTk+FS6Yw81V1DLuZl1bRbNrev6Tmd/9RaroeeRRJhAt7jg/6YFxbvAQXUCavSoZhPPj6oOx+5KjQ==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/fastify" + }, + { + "type": "opencollective", + "url": "https://opencollective.com/fastify" + } + ], + "license": "BSD-3-Clause" + }, + "node_modules/openclaw/node_modules/fast-wrap-ansi": { + "version": "0.2.2", + "resolved": "https://registry.npmjs.org/fast-wrap-ansi/-/fast-wrap-ansi-0.2.2.tgz", + "integrity": "sha512-7F2Fl+TjRSenLqlU3UjSH0iyqopqoZIu7eZVpEirP2g1GtWa2G/ecEmBdgz31+Mxr+ELclgg6sokpSFIQiZ02Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "fast-string-width": "^3.0.2" + } + }, + "node_modules/openclaw/node_modules/fetch-blob": { + "version": "3.2.0", + "resolved": "https://registry.npmjs.org/fetch-blob/-/fetch-blob-3.2.0.tgz", + "integrity": "sha512-7yAQpD2UMJzLi1Dqv7qFYnPbaPx7ZfFK6PiIxQ4PfkGPyNyl2Ugx+a/umUonmKqjhM4DnfbMvdX6otXq83soQQ==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/jimmywarting" + }, + { + "type": "paypal", + "url": "https://paypal.me/jimmywarting" + } + ], + "license": "MIT", + "dependencies": { + "node-domexception": "^1.0.0", + "web-streams-polyfill": "^3.0.3" + }, + "engines": { + "node": "^12.20 || >= 14.13" + } + }, + "node_modules/openclaw/node_modules/file-type": { + "version": "22.0.1", + "resolved": "https://registry.npmjs.org/file-type/-/file-type-22.0.1.tgz", + "integrity": "sha512-ww5Mhre0EE+jmBvOXTmXAbEMuZE7uX4a3+oRCQFNj8w++g3ev913N6tXQz0XTXbueQ5TWQfm6BdaViEHHn8bhA==", + "dev": true, + "license": "MIT", + "dependencies": { + "@tokenizer/inflate": "^0.4.1", + "strtok3": "^10.3.5", + "token-types": "^6.1.2", + "uint8array-extras": "^1.5.0" + }, + "engines": { + "node": ">=22" + }, + "funding": { + "url": "https://github.com/sindresorhus/file-type?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/finalhandler": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/finalhandler/-/finalhandler-2.1.1.tgz", + "integrity": "sha512-S8KoZgRZN+a5rNwqTxlZZePjT/4cnm0ROV70LedRHZ0p8u9fRID0hJUZQpkKLzro8LfmC8sx23bY6tVNxv8pQA==", + "dev": true, + "license": "MIT", + "dependencies": { + "debug": "^4.4.0", + "encodeurl": "^2.0.0", + "escape-html": "^1.0.3", + "on-finished": "^2.4.1", + "parseurl": "^1.3.3", + "statuses": "^2.0.1" + }, + "engines": { + "node": ">= 18.0.0" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/find-up": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz", + "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==", + "dev": true, + "license": "MIT", + "dependencies": { + "locate-path": "^5.0.0", + "path-exists": "^4.0.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/formdata-polyfill": { + "version": "4.0.10", + "resolved": "https://registry.npmjs.org/formdata-polyfill/-/formdata-polyfill-4.0.10.tgz", + "integrity": "sha512-buewHzMvYL29jdeQTVILecSaZKnt/RJWjoZCF5OW60Z67/GmSLBkOFM7qh1PI3zFNtJbaZL5eQu1vLfazOwj4g==", + "dev": true, + "license": "MIT", + "dependencies": { + "fetch-blob": "^3.1.2" + }, + "engines": { + "node": ">=12.20.0" + } + }, + "node_modules/openclaw/node_modules/forwarded": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/forwarded/-/forwarded-0.2.0.tgz", + "integrity": "sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/fresh": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/fresh/-/fresh-2.0.0.tgz", + "integrity": "sha512-Rx/WycZ60HOaqLKAi6cHRKKI7zxWbJ31MhntmtwMoaTeF7XFH9hhBp8vITaMidfljRQ6eYWCKkaTK+ykVJHP2A==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/function-bind": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz", + "integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==", + "dev": true, + "license": "MIT", + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/gaxios": { + "version": "7.1.4", + "resolved": "https://registry.npmjs.org/gaxios/-/gaxios-7.1.4.tgz", + "integrity": "sha512-bTIgTsM2bWn3XklZISBTQX7ZSddGW+IO3bMdGaemHZ3tbqExMENHLx6kKZ/KlejgrMtj8q7wBItt51yegqalrA==", + "dev": true, + "license": "Apache-2.0", + "dependencies": { + "extend": "^3.0.2", + "https-proxy-agent": "^7.0.1", + "node-fetch": "^3.3.2" + }, + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/gcp-metadata": { + "version": "8.1.2", + "resolved": "https://registry.npmjs.org/gcp-metadata/-/gcp-metadata-8.1.2.tgz", + "integrity": "sha512-zV/5HKTfCeKWnxG0Dmrw51hEWFGfcF2xiXqcA3+J90WDuP0SvoiSO5ORvcBsifmx/FoIjgQN3oNOGaQ5PhLFkg==", + "dev": true, + "license": "Apache-2.0", + "dependencies": { + "gaxios": "^7.0.0", + "google-logging-utils": "^1.0.0", + "json-bigint": "^1.0.0" + }, + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/get-caller-file": { + "version": "2.0.5", + "resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz", + "integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==", + "dev": true, + "license": "ISC", + "engines": { + "node": "6.* || 8.* || >= 10.*" + } + }, + "node_modules/openclaw/node_modules/get-east-asian-width": { + "version": "1.6.0", + "resolved": "https://registry.npmjs.org/get-east-asian-width/-/get-east-asian-width-1.6.0.tgz", + "integrity": "sha512-QRbvDIbx6YklUe6RxeTeleMR0yv3cYH6PsPZHcnVn7xv7zO1BHN8r0XETu8n6Ye3Q+ahtSarc3WgtNWmehIBfA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/openclaw/node_modules/get-intrinsic": { + "version": "1.3.0", + "resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.3.0.tgz", + "integrity": "sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "call-bind-apply-helpers": "^1.0.2", + "es-define-property": "^1.0.1", + "es-errors": "^1.3.0", + "es-object-atoms": "^1.1.1", + "function-bind": "^1.1.2", + "get-proto": "^1.0.1", + "gopd": "^1.2.0", + "has-symbols": "^1.1.0", + "hasown": "^2.0.2", + "math-intrinsics": "^1.1.0" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/get-proto": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/get-proto/-/get-proto-1.0.1.tgz", + "integrity": "sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==", + "dev": true, + "license": "MIT", + "dependencies": { + "dunder-proto": "^1.0.1", + "es-object-atoms": "^1.0.0" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/glob": { + "version": "13.0.6", + "resolved": "https://registry.npmjs.org/glob/-/glob-13.0.6.tgz", + "integrity": "sha512-Wjlyrolmm8uDpm/ogGyXZXb1Z+Ca2B8NbJwqBVg0axK9GbBeoS7yGV6vjXnYdGm6X53iehEuxxbyiKp8QmN4Vw==", + "dev": true, + "license": "BlueOak-1.0.0", + "dependencies": { + "minimatch": "^10.2.2", + "minipass": "^7.1.3", + "path-scurry": "^2.0.2" + }, + "engines": { + "node": "18 || 20 || >=22" + }, + "funding": { + "url": "https://github.com/sponsors/isaacs" + } + }, + "node_modules/openclaw/node_modules/google-auth-library": { + "version": "10.6.2", + "resolved": "https://registry.npmjs.org/google-auth-library/-/google-auth-library-10.6.2.tgz", + "integrity": "sha512-e27Z6EThmVNNvtYASwQxose/G57rkRuaRbQyxM2bvYLLX/GqWZ5chWq2EBoUchJbCc57eC9ArzO5wMsEmWftCw==", + "dev": true, + "license": "Apache-2.0", + "dependencies": { + "base64-js": "^1.3.0", + "ecdsa-sig-formatter": "^1.0.11", + "gaxios": "^7.1.4", + "gcp-metadata": "8.1.2", + "google-logging-utils": "1.1.3", + "jws": "^4.0.0" + }, + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/google-logging-utils": { + "version": "1.1.3", + "resolved": "https://registry.npmjs.org/google-logging-utils/-/google-logging-utils-1.1.3.tgz", + "integrity": "sha512-eAmLkjDjAFCVXg7A1unxHsLf961m6y17QFqXqAXGj/gVkKFrEICfStRfwUlGNfeCEjNRa32JEWOUTlYXPyyKvA==", + "dev": true, + "license": "Apache-2.0", + "engines": { + "node": ">=14" + } + }, + "node_modules/openclaw/node_modules/gopd": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/gopd/-/gopd-1.2.0.tgz", + "integrity": "sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/graceful-fs": { + "version": "4.2.11", + "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz", + "integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/grammy": { + "version": "1.43.0", + "resolved": "https://registry.npmjs.org/grammy/-/grammy-1.43.0.tgz", + "integrity": "sha512-7dYm06A945mXuIk/5HUlSjeyIYChW8vCEiU2dkOKKqJJzwAWxTkCc91Eqbz7TgODh2rtFFKWI/fekowWHOkmjQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "@grammyjs/types": "3.27.3", + "abort-controller": "^3.0.0", + "debug": "^4.4.3", + "node-fetch": "^2.7.0" + }, + "engines": { + "node": "^12.20.0 || >=14.13.1" + } + }, + "node_modules/openclaw/node_modules/grammy/node_modules/node-fetch": { + "version": "2.7.0", + "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.7.0.tgz", + "integrity": "sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==", + "dev": true, + "license": "MIT", + "dependencies": { + "whatwg-url": "^5.0.0" + }, + "engines": { + "node": "4.x || >=6.0.0" + }, + "peerDependencies": { + "encoding": "^0.1.0" + }, + "peerDependenciesMeta": { + "encoding": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/has-symbols": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.1.0.tgz", + "integrity": "sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/hasown": { + "version": "2.0.4", + "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.4.tgz", + "integrity": "sha512-T2UbfbBEF32wiepXIsMlTW9+dDYC6wMh/t/vYA4tuOMKqWz/n3vr1NFSxQiyP+zk2mXsoMA/i/7qV6LKut1t1A==", + "dev": true, + "license": "MIT", + "dependencies": { + "function-bind": "^1.1.2" + }, + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/highlight.js": { + "version": "11.11.1", + "resolved": "https://registry.npmjs.org/highlight.js/-/highlight.js-11.11.1.tgz", + "integrity": "sha512-Xwwo44whKBVCYoliBQwaPvtd/2tYFkRQtXDWj1nackaV2JPXx3L0+Jvd8/qCJ2p+ML0/XVkJ2q+Mr+UVdpJK5w==", + "dev": true, + "license": "BSD-3-Clause", + "engines": { + "node": ">=12.0.0" + } + }, + "node_modules/openclaw/node_modules/hono": { + "version": "4.12.18", + "resolved": "https://registry.npmjs.org/hono/-/hono-4.12.18.tgz", + "integrity": "sha512-RWzP96k/yv0PQfyXnWjs6zot20TqfpfsNXhOnev8d1InAxubW93L11/oNUc3tQqn2G0bSdAOBpX+2uDFHV7kdQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=16.9.0" + } + }, + "node_modules/openclaw/node_modules/hosted-git-info": { + "version": "10.1.1", + "resolved": "https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-10.1.1.tgz", + "integrity": "sha512-DeOnSPAvOndYKfw075gt8yZzQ7S2hNztw34zBTfhIzLhmBTswIBg5/y+pqu/VD5cYWm5goAFTusDmUEmKZ0PEQ==", + "dev": true, + "license": "ISC", + "dependencies": { + "lru-cache": "^11.1.0" + }, + "engines": { + "node": "^22.22.2 || ^24.15.0 || >=26.0.0" + } + }, + "node_modules/openclaw/node_modules/html-escaper": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/html-escaper/-/html-escaper-3.0.3.tgz", + "integrity": "sha512-RuMffC89BOWQoY0WKGpIhn5gX3iI54O6nRA0yC124NYVtzjmFWBIiFd8M0x+ZdX0P9R4lADg1mgP8C7PxGOWuQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/htmlparser2": { + "version": "10.1.0", + "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-10.1.0.tgz", + "integrity": "sha512-VTZkM9GWRAtEpveh7MSF6SjjrpNVNNVJfFup7xTY3UpFtm67foy9HDVXneLtFVt4pMz5kZtgNcvCniNFb1hlEQ==", + "dev": true, + "funding": [ + "https://github.com/fb55/htmlparser2?sponsor=1", + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ], + "license": "MIT", + "dependencies": { + "domelementtype": "^2.3.0", + "domhandler": "^5.0.3", + "domutils": "^3.2.2", + "entities": "^7.0.1" + } + }, + "node_modules/openclaw/node_modules/htmlparser2/node_modules/entities": { + "version": "7.0.1", + "resolved": "https://registry.npmjs.org/entities/-/entities-7.0.1.tgz", + "integrity": "sha512-TWrgLOFUQTH994YUyl1yT4uyavY5nNB5muff+RtWaqNVCAK408b5ZnnbNAUEWLTCpum9w6arT70i1XdQ4UeOPA==", + "dev": true, + "license": "BSD-2-Clause", + "engines": { + "node": ">=0.12" + }, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/http_ece": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/http_ece/-/http_ece-1.2.0.tgz", + "integrity": "sha512-JrF8SSLVmcvc5NducxgyOrKXe3EsyHMgBFgSaIUGmArKe+rwr0uphRkRXvwiom3I+fpIfoItveHrfudL8/rxuA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=16" + } + }, + "node_modules/openclaw/node_modules/http-errors": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/http-errors/-/http-errors-2.0.1.tgz", + "integrity": "sha512-4FbRdAX+bSdmo4AUFuS0WNiPz8NgFt+r8ThgNWmlrjQjt1Q7ZR9+zTlce2859x4KSXrwIsaeTqDoKQmtP8pLmQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "depd": "~2.0.0", + "inherits": "~2.0.4", + "setprototypeof": "~1.2.0", + "statuses": "~2.0.2", + "toidentifier": "~1.0.1" + }, + "engines": { + "node": ">= 0.8" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/https-proxy-agent": { + "version": "7.0.6", + "resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-7.0.6.tgz", + "integrity": "sha512-vK9P5/iUfdl95AI+JVyUuIcVtd4ofvtrOr3HNtM2yxC9bnMbEdp3x01OhQNnjb8IJYi38VlTE3mBXwcfvywuSw==", + "dev": true, + "license": "MIT", + "dependencies": { + "agent-base": "^7.1.2", + "debug": "4" + }, + "engines": { + "node": ">= 14" + } + }, + "node_modules/openclaw/node_modules/iconv-lite": { + "version": "0.7.2", + "resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.7.2.tgz", + "integrity": "sha512-im9DjEDQ55s9fL4EYzOAv0yMqmMBSZp6G0VvFyTMPKWxiSBHUj9NW/qqLmXUwXrrM7AvqSlTCfvqRb0cM8yYqw==", + "dev": true, + "license": "MIT", + "dependencies": { + "safer-buffer": ">= 2.1.2 < 3.0.0" + }, + "engines": { + "node": ">=0.10.0" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/ieee754": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz", + "integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/feross" + }, + { + "type": "patreon", + "url": "https://www.patreon.com/feross" + }, + { + "type": "consulting", + "url": "https://feross.org/support" + } + ], + "license": "BSD-3-Clause" + }, + "node_modules/openclaw/node_modules/ignore": { + "version": "7.0.5", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.5.tgz", + "integrity": "sha512-Hs59xBNfUIunMFgWAbGX5cq6893IbWg4KnrjbYwX3tx0ztorVgTDA6B2sxf8ejHJ4wz8BqGUMYlnzNBer5NvGg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 4" + } + }, + "node_modules/openclaw/node_modules/immediate": { + "version": "3.0.6", + "resolved": "https://registry.npmjs.org/immediate/-/immediate-3.0.6.tgz", + "integrity": "sha512-XXOFtyqDjNDAQxVfYxuF7g9Il/IbWmmlQg2MYKOH8ExIT1qg6xc4zyS3HaEEATgs1btfzxq15ciUiY7gjSXRGQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/inherits": { + "version": "2.0.4", + "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz", + "integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/ip-address": { + "version": "10.2.0", + "resolved": "https://registry.npmjs.org/ip-address/-/ip-address-10.2.0.tgz", + "integrity": "sha512-/+S6j4E9AHvW9SWMSEY9Xfy66O5PWvVEJ08O0y5JGyEKQpojb0K0GKpz/v5HJ/G0vi3D2sjGK78119oXZeE0qA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 12" + } + }, + "node_modules/openclaw/node_modules/ipaddr.js": { + "version": "1.9.1", + "resolved": "https://registry.npmjs.org/ipaddr.js/-/ipaddr.js-1.9.1.tgz", + "integrity": "sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/openclaw/node_modules/is-fullwidth-code-point": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz", + "integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/is-promise": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/is-promise/-/is-promise-4.0.0.tgz", + "integrity": "sha512-hvpoI6korhJMnej285dSg6nu1+e6uxs7zG3BYAm5byqDsgJNWwxzM6z6iZiAgQR4TJ30JmBTOwqZUw3WlyH3AQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/isarray": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz", + "integrity": "sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/isexe": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", + "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/jiti": { + "version": "2.7.0", + "resolved": "https://registry.npmjs.org/jiti/-/jiti-2.7.0.tgz", + "integrity": "sha512-AC/7JofJvZGrrneWNaEnJeOLUx+JlGt7tNa0wZiRPT4MY1wmfKjt2+6O2p2uz2+skll8OZZmJMNqeke7kKbNgQ==", + "dev": true, + "license": "MIT", + "bin": { + "jiti": "lib/jiti-cli.mjs" + } + }, + "node_modules/openclaw/node_modules/jose": { + "version": "6.2.3", + "resolved": "https://registry.npmjs.org/jose/-/jose-6.2.3.tgz", + "integrity": "sha512-YYVDInQKFJfR/xa3ojUTl8c2KoTwiL1R5Wg9YCydwH0x0B9grbzlg5HC7mMjCtUJjbQ/YnGEZIhI5tCgfTb4Hw==", + "dev": true, + "license": "MIT", + "funding": { + "url": "https://github.com/sponsors/panva" + } + }, + "node_modules/openclaw/node_modules/json-bigint": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/json-bigint/-/json-bigint-1.0.0.tgz", + "integrity": "sha512-SiPv/8VpZuWbvLSMtTDU8hEfrZWg/mH/nV/b4o0CYbSxu1UIQPLdwKOCIyLQX+VIPO5vrLX3i8qtqFyhdPSUSQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "bignumber.js": "^9.0.0" + } + }, + "node_modules/openclaw/node_modules/json-schema-to-ts": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/json-schema-to-ts/-/json-schema-to-ts-3.1.1.tgz", + "integrity": "sha512-+DWg8jCJG2TEnpy7kOm/7/AxaYoaRbjVB4LFZLySZlWn8exGs3A4OLJR966cVvU26N7X9TWxl+Jsw7dzAqKT6g==", + "dev": true, + "license": "MIT", + "dependencies": { + "@babel/runtime": "^7.18.3", + "ts-algebra": "^2.0.0" + }, + "engines": { + "node": ">=16" + } + }, + "node_modules/openclaw/node_modules/json-schema-traverse": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz", + "integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/json-schema-typed": { + "version": "8.0.2", + "resolved": "https://registry.npmjs.org/json-schema-typed/-/json-schema-typed-8.0.2.tgz", + "integrity": "sha512-fQhoXdcvc3V28x7C7BMs4P5+kNlgUURe2jmUT1T//oBRMDrqy1QPelJimwZGo7Hg9VPV3EQV5Bnq4hbFy2vetA==", + "dev": true, + "license": "BSD-2-Clause" + }, + "node_modules/openclaw/node_modules/json5": { + "version": "2.2.3", + "resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz", + "integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==", + "dev": true, + "license": "MIT", + "bin": { + "json5": "lib/cli.js" + }, + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/jszip": { + "version": "3.10.1", + "resolved": "https://registry.npmjs.org/jszip/-/jszip-3.10.1.tgz", + "integrity": "sha512-xXDvecyTpGLrqFrvkrUSoxxfJI5AH7U8zxxtVclpsUtMCq4JQ290LY8AW5c7Ggnr/Y/oK+bQMbqK2qmtk3pN4g==", + "dev": true, + "license": "(MIT OR GPL-3.0-or-later)", + "dependencies": { + "lie": "~3.3.0", + "pako": "~1.0.2", + "readable-stream": "~2.3.6", + "setimmediate": "^1.0.5" + } + }, + "node_modules/openclaw/node_modules/jwa": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/jwa/-/jwa-2.0.1.tgz", + "integrity": "sha512-hRF04fqJIP8Abbkq5NKGN0Bbr3JxlQ+qhZufXVr0DvujKy93ZCbXZMHDL4EOtodSbCWxOqR8MS1tXA5hwqCXDg==", + "dev": true, + "license": "MIT", + "dependencies": { + "buffer-equal-constant-time": "^1.0.1", + "ecdsa-sig-formatter": "1.0.11", + "safe-buffer": "^5.0.1" + } + }, + "node_modules/openclaw/node_modules/jws": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/jws/-/jws-4.0.1.tgz", + "integrity": "sha512-EKI/M/yqPncGUUh44xz0PxSidXFr/+r0pA70+gIYhjv+et7yxM+s29Y+VGDkovRofQem0fs7Uvf4+YmAdyRduA==", + "dev": true, + "license": "MIT", + "dependencies": { + "jwa": "^2.0.1", + "safe-buffer": "^5.0.1" + } + }, + "node_modules/openclaw/node_modules/kysely": { + "version": "0.29.2", + "resolved": "https://registry.npmjs.org/kysely/-/kysely-0.29.2.tgz", + "integrity": "sha512-s6WVJyEZrbm6jhBpiKHsGHyePMrVQKJ85wZCFCr9W4QHv6WTjWIrdvTmO9hDEA3bNK0xkrE2DqrHsXMLWuZpQg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=22.0.0" + } + }, + "node_modules/openclaw/node_modules/lie": { + "version": "3.3.0", + "resolved": "https://registry.npmjs.org/lie/-/lie-3.3.0.tgz", + "integrity": "sha512-UaiMJzeWRlEujzAuw5LokY1L5ecNQYZKfmyZ9L7wDHb/p5etKaxXhohBcrw0EYby+G/NA52vRSN4N39dxHAIwQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "immediate": "~3.0.5" + } + }, + "node_modules/openclaw/node_modules/linkedom": { + "version": "0.18.12", + "resolved": "https://registry.npmjs.org/linkedom/-/linkedom-0.18.12.tgz", + "integrity": "sha512-jalJsOwIKuQJSeTvsgzPe9iJzyfVaEJiEXl+25EkKevsULHvMJzpNqwvj1jOESWdmgKDiXObyjOYwlUqG7wo1Q==", + "dev": true, + "license": "ISC", + "dependencies": { + "css-select": "^5.1.0", + "cssom": "^0.5.0", + "html-escaper": "^3.0.3", + "htmlparser2": "^10.0.0", + "uhyphen": "^0.2.0" + }, + "engines": { + "node": ">=16" + }, + "peerDependencies": { + "canvas": ">= 2" + }, + "peerDependenciesMeta": { + "canvas": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/locate-path": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz", + "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==", + "dev": true, + "license": "MIT", + "dependencies": { + "p-locate": "^4.1.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/long": { + "version": "5.3.2", + "resolved": "https://registry.npmjs.org/long/-/long-5.3.2.tgz", + "integrity": "sha512-mNAgZ1GmyNhD7AuqnTG3/VQ26o760+ZYBPKjPvugO8+nLbYfX6TVpJPseBvopbdY+qpZ/lKUnmEc1LeZYS3QAA==", + "dev": true, + "license": "Apache-2.0" + }, + "node_modules/openclaw/node_modules/lru-cache": { + "version": "11.5.1", + "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-11.5.1.tgz", + "integrity": "sha512-RPimw/7aMdv2oqRrxKwvZXcPfwBrn/JZ2xYcY9Hus/6LaS3VOAKVWKWgNLCFSiOm1ESXinjsDlidVU7JlnCN2A==", + "dev": true, + "license": "BlueOak-1.0.0", + "engines": { + "node": "20 || >=22" + } + }, + "node_modules/openclaw/node_modules/marked": { + "version": "15.0.12", + "resolved": "https://registry.npmjs.org/marked/-/marked-15.0.12.tgz", + "integrity": "sha512-8dD6FusOQSrpv9Z1rdNMdlSgQOIP880DHqnohobOmYLElGEqAL/JvxvuxZO16r4HtjTlfPRDC1hbvxC9dPN2nA==", + "dev": true, + "license": "MIT", + "bin": { + "marked": "bin/marked.js" + }, + "engines": { + "node": ">= 18" + } + }, + "node_modules/openclaw/node_modules/math-intrinsics": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/math-intrinsics/-/math-intrinsics-1.1.0.tgz", + "integrity": "sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + } + }, + "node_modules/openclaw/node_modules/media-typer": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/media-typer/-/media-typer-1.1.0.tgz", + "integrity": "sha512-aisnrDP4GNe06UcKFnV5bfMNPBUw4jsLGaWwWfnH3v02GnBuXX2MCVn5RbrWo0j3pczUilYblq7fQ7Nw2t5XKw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/merge-descriptors": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/merge-descriptors/-/merge-descriptors-2.0.0.tgz", + "integrity": "sha512-Snk314V5ayFLhp3fkUREub6WtjBfPdCPY1Ln8/8munuLuiYhsABgBVWsozAG+MWMbVEvcdcpbi9R7ww22l9Q3g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/openclaw/node_modules/mime-db": { + "version": "1.54.0", + "resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.54.0.tgz", + "integrity": "sha512-aU5EJuIN2WDemCcAp2vFBfp/m4EAhWJnUNSSw0ixs7/kXbd6Pg64EmwJkNdFhB8aWt1sH2CTXrLxo/iAGV3oPQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/mime-types": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/mime-types/-/mime-types-3.0.2.tgz", + "integrity": "sha512-Lbgzdk0h4juoQ9fCKXW4by0UJqj+nOOrI9MJ1sSj4nI8aI2eo1qmvQEie4VD1glsS250n15LsWsYtCugiStS5A==", + "dev": true, + "license": "MIT", + "dependencies": { + "mime-db": "^1.54.0" + }, + "engines": { + "node": ">=18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/minimalistic-assert": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/minimalistic-assert/-/minimalistic-assert-1.0.1.tgz", + "integrity": "sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/minimatch": { + "version": "10.2.5", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.2.5.tgz", + "integrity": "sha512-MULkVLfKGYDFYejP07QOurDLLQpcjk7Fw+7jXS2R2czRQzR56yHRveU5NDJEOviH+hETZKSkIk5c+T23GjFUMg==", + "dev": true, + "license": "BlueOak-1.0.0", + "dependencies": { + "brace-expansion": "^5.0.5" + }, + "engines": { + "node": "18 || 20 || >=22" + }, + "funding": { + "url": "https://github.com/sponsors/isaacs" + } + }, + "node_modules/openclaw/node_modules/minimist": { + "version": "1.2.8", + "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz", + "integrity": "sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==", + "dev": true, + "license": "MIT", + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/minipass": { + "version": "7.1.3", + "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.3.tgz", + "integrity": "sha512-tEBHqDnIoM/1rXME1zgka9g6Q2lcoCkxHLuc7ODJ5BxbP5d4c2Z5cGgtXAku59200Cx7diuHTOYfSBD8n6mm8A==", + "dev": true, + "license": "BlueOak-1.0.0", + "engines": { + "node": ">=16 || 14 >=14.17" + } + }, + "node_modules/openclaw/node_modules/minizlib": { + "version": "3.1.0", + "resolved": "https://registry.npmjs.org/minizlib/-/minizlib-3.1.0.tgz", + "integrity": "sha512-KZxYo1BUkWD2TVFLr0MQoM8vUUigWD3LlD83a/75BqC+4qE0Hb1Vo5v1FgcfaNXvfXzr+5EhQ6ing/CaBijTlw==", + "dev": true, + "license": "MIT", + "dependencies": { + "minipass": "^7.1.2" + }, + "engines": { + "node": ">= 18" + } + }, + "node_modules/openclaw/node_modules/ms": { + "version": "2.1.3", + "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz", + "integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/negotiator": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/negotiator/-/negotiator-1.0.0.tgz", + "integrity": "sha512-8Ofs/AUQh8MaEcrlq5xOX0CQ9ypTF5dl78mjlMNfOK08fzpgTHQRQPBxcPlEtIw0yRpws+Zo/3r+5WRby7u3Gg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/node-addon-api": { + "version": "8.8.0", + "resolved": "https://registry.npmjs.org/node-addon-api/-/node-addon-api-8.8.0.tgz", + "integrity": "sha512-c5Ko1fZJIJmzhFIkhRN76WTq+fC6tWnGy9CXA0fA+XygsWZmEwG8vmbkNqxMyoaa0Tin4djul49NzdVcJJcjeA==", + "dev": true, + "license": "MIT", + "engines": { + "node": "^18 || ^20 || >= 21" + } + }, + "node_modules/openclaw/node_modules/node-domexception": { + "name": "@nolyfill/domexception", + "version": "1.0.28", + "resolved": "https://registry.npmjs.org/@nolyfill/domexception/-/domexception-1.0.28.tgz", + "integrity": "sha512-tlc/FcYIv5i8RYsl2iDil4A0gOihaas1R5jPcIC4Zw3GhjKsVilw90aHcVlhZPTBLGBzd379S+VcnsDjd9ChiA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=12.4.0" + } + }, + "node_modules/openclaw/node_modules/node-edge-tts": { + "version": "1.2.10", + "resolved": "https://registry.npmjs.org/node-edge-tts/-/node-edge-tts-1.2.10.tgz", + "integrity": "sha512-bV2i4XU54D45+US0Zm1HcJRkifuB3W438dWyuJEHLQdKxnuqlI1kim2MOvR6Q3XUQZvfF9PoDyR1Rt7aeXhPdQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "https-proxy-agent": "^7.0.1", + "ws": "^8.13.0", + "yargs": "^17.7.2" + }, + "bin": { + "node-edge-tts": "bin.js" + } + }, + "node_modules/openclaw/node_modules/node-fetch": { + "version": "3.3.2", + "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-3.3.2.tgz", + "integrity": "sha512-dRB78srN/l6gqWulah9SrxeYnxeddIG30+GOqK/9OlLVyLg3HPnr6SqOWTWOXKRwC2eGYCkZ59NNuSgvSrpgOA==", + "dev": true, + "license": "MIT", + "dependencies": { + "data-uri-to-buffer": "^4.0.0", + "fetch-blob": "^3.1.4", + "formdata-polyfill": "^4.0.10" + }, + "engines": { + "node": "^12.20.0 || ^14.13.1 || >=16.0.0" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/node-fetch" + } + }, + "node_modules/openclaw/node_modules/node-gyp-build": { + "version": "4.8.4", + "resolved": "https://registry.npmjs.org/node-gyp-build/-/node-gyp-build-4.8.4.tgz", + "integrity": "sha512-LA4ZjwlnUblHVgq0oBF3Jl/6h/Nvs5fzBLwdEF4nuxnFdsfajde4WfxtJr3CaiH+F6ewcIB/q4jQ4UzPyid+CQ==", + "dev": true, + "license": "MIT", + "bin": { + "node-gyp-build": "bin.js", + "node-gyp-build-optional": "optional.js", + "node-gyp-build-test": "build-test.js" + } + }, + "node_modules/openclaw/node_modules/nth-check": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz", + "integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==", + "dev": true, + "license": "BSD-2-Clause", + "dependencies": { + "boolbase": "^1.0.0" + }, + "funding": { + "url": "https://github.com/fb55/nth-check?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/object-assign": { + "version": "4.1.1", + "resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz", + "integrity": "sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/openclaw/node_modules/object-inspect": { + "version": "1.13.4", + "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.4.tgz", + "integrity": "sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/on-finished": { + "version": "2.4.1", + "resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.4.1.tgz", + "integrity": "sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==", + "dev": true, + "license": "MIT", + "dependencies": { + "ee-first": "1.1.1" + }, + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/once": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz", + "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==", + "dev": true, + "license": "ISC", + "dependencies": { + "wrappy": "1" + } + }, + "node_modules/openclaw/node_modules/openai": { + "version": "6.39.1", + "resolved": "https://registry.npmjs.org/openai/-/openai-6.39.1.tgz", + "integrity": "sha512-z3dO9fEWOXBzlXynVb/xZ/tujzUjFWQWn3C0n0mw6Vo0zJTbEkaN4b2cLWjhJ6haJQx8LlREoafHRl+Gu/Hl+A==", + "dev": true, + "license": "Apache-2.0", + "bin": { + "openai": "bin/cli" + }, + "peerDependencies": { + "ws": "^8.18.0", + "zod": "^3.25 || ^4.0" + }, + "peerDependenciesMeta": { + "ws": { + "optional": true + }, + "zod": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/p-limit": { + "version": "2.3.0", + "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz", + "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==", + "dev": true, + "license": "MIT", + "dependencies": { + "p-try": "^2.0.0" + }, + "engines": { + "node": ">=6" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/openclaw/node_modules/p-locate": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz", + "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==", + "dev": true, + "license": "MIT", + "dependencies": { + "p-limit": "^2.2.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/p-retry": { + "version": "4.6.2", + "resolved": "https://registry.npmjs.org/p-retry/-/p-retry-4.6.2.tgz", + "integrity": "sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "@types/retry": "0.12.0", + "retry": "^0.13.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/p-try": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz", + "integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/pako": { + "version": "1.0.11", + "resolved": "https://registry.npmjs.org/pako/-/pako-1.0.11.tgz", + "integrity": "sha512-4hLB8Py4zZce5s4yd9XzopqwVv/yGNhV1Bl8NTmCq1763HeK2+EwVTv+leGeL13Dnh2wfbqowVPXCIO0z4taYw==", + "dev": true, + "license": "(MIT AND Zlib)" + }, + "node_modules/openclaw/node_modules/parseurl": { + "version": "1.3.3", + "resolved": "https://registry.npmjs.org/parseurl/-/parseurl-1.3.3.tgz", + "integrity": "sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/partial-json": { + "version": "0.1.7", + "resolved": "https://registry.npmjs.org/partial-json/-/partial-json-0.1.7.tgz", + "integrity": "sha512-Njv/59hHaokb/hRUjce3Hdv12wd60MtM9Z5Olmn+nehe0QDAsRtRbJPvJ0Z91TusF0SuZRIvnM+S4l6EIP8leA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/path-exists": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz", + "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/path-key": { + "version": "3.1.1", + "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz", + "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/path-scurry": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-2.0.2.tgz", + "integrity": "sha512-3O/iVVsJAPsOnpwWIeD+d6z/7PmqApyQePUtCndjatj/9I5LylHvt5qluFaBT3I5h3r1ejfR056c+FCv+NnNXg==", + "dev": true, + "license": "BlueOak-1.0.0", + "dependencies": { + "lru-cache": "^11.0.0", + "minipass": "^7.1.2" + }, + "engines": { + "node": "18 || 20 || >=22" + }, + "funding": { + "url": "https://github.com/sponsors/isaacs" + } + }, + "node_modules/openclaw/node_modules/path-to-regexp": { + "version": "8.4.0", + "resolved": "https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-8.4.0.tgz", + "integrity": "sha512-PuseHIvAnz3bjrM2rGJtSgo1zjgxapTLZ7x2pjhzWwlp4SJQgK3f3iZIQwkpEnBaKz6seKBADpM4B4ySkuYypg==", + "dev": true, + "license": "MIT", + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/pkce-challenge": { + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/pkce-challenge/-/pkce-challenge-5.0.1.tgz", + "integrity": "sha512-wQ0b/W4Fr01qtpHlqSqspcj3EhBvimsdh0KlHhH8HRZnMsEa0ea2fTULOXOS9ccQr3om+GcGRk4e+isrZWV8qQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=16.20.0" + } + }, + "node_modules/openclaw/node_modules/playwright-core": { + "version": "1.60.0", + "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.60.0.tgz", + "integrity": "sha512-9bW6zvX/m0lEbgTKJ6YppOKx8H3VOPBMOCFh2irXFOT4BbHgrx5hPjwJYLT40Lu+4qtD36qKc/Hn56StUW57IA==", + "dev": true, + "license": "Apache-2.0", + "bin": { + "playwright-core": "cli.js" + }, + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/pngjs": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/pngjs/-/pngjs-5.0.0.tgz", + "integrity": "sha512-40QW5YalBNfQo5yRYmiw7Yz6TKKVr3h6970B2YE+3fQpsWcrbj1PzJgxeJ19DRQjhMbKPIuMY8rFaXc8moolVw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=10.13.0" + } + }, + "node_modules/openclaw/node_modules/process-nextick-args": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/process-nextick-args/-/process-nextick-args-2.0.1.tgz", + "integrity": "sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/proper-lockfile": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/proper-lockfile/-/proper-lockfile-4.1.2.tgz", + "integrity": "sha512-TjNPblN4BwAWMXU8s9AEz4JmQxnD1NNL7bNOY/AKUzyamc379FWASUhc/K1pL2noVb+XmZKLL68cjzLsiOAMaA==", + "dev": true, + "license": "MIT", + "dependencies": { + "graceful-fs": "^4.2.4", + "retry": "^0.12.0", + "signal-exit": "^3.0.2" + } + }, + "node_modules/openclaw/node_modules/proper-lockfile/node_modules/retry": { + "version": "0.12.0", + "resolved": "https://registry.npmjs.org/retry/-/retry-0.12.0.tgz", + "integrity": "sha512-9LkiTwjUh6rT555DtE9rTX+BKByPfrMzEAtnlEtdEwr3Nkffwiihqe2bWADg+OQRjt9gl6ICdmB/ZFDCGAtSow==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 4" + } + }, + "node_modules/openclaw/node_modules/protobufjs": { + "version": "8.4.0", + "resolved": "https://registry.npmjs.org/protobufjs/-/protobufjs-8.4.0.tgz", + "integrity": "sha512-iriNhQ57SYA5Jbdi+41AyPdx6jPPkFO7DODzkOBmqFhgYn/JzX2HxgxYPY18eQAs3CP/AWqtPvkWn8rclRAxdQ==", + "dev": true, + "hasInstallScript": true, + "license": "BSD-3-Clause", + "dependencies": { + "long": "^5.3.2" + }, + "engines": { + "node": ">=12.0.0" + } + }, + "node_modules/openclaw/node_modules/proxy-addr": { + "version": "2.0.7", + "resolved": "https://registry.npmjs.org/proxy-addr/-/proxy-addr-2.0.7.tgz", + "integrity": "sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==", + "dev": true, + "license": "MIT", + "dependencies": { + "forwarded": "0.2.0", + "ipaddr.js": "1.9.1" + }, + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/openclaw/node_modules/qrcode": { + "version": "1.5.4", + "resolved": "https://registry.npmjs.org/qrcode/-/qrcode-1.5.4.tgz", + "integrity": "sha512-1ca71Zgiu6ORjHqFBDpnSMTR2ReToX4l1Au1VFLyVeBTFavzQnv5JxMFr3ukHVKpSrSA2MCk0lNJSykjUfz7Zg==", + "dev": true, + "license": "MIT", + "dependencies": { + "dijkstrajs": "^1.0.1", + "pngjs": "^5.0.0", + "yargs": "^15.3.1" + }, + "bin": { + "qrcode": "bin/qrcode" + }, + "engines": { + "node": ">=10.13.0" + } + }, + "node_modules/openclaw/node_modules/qrcode/node_modules/cliui": { + "version": "6.0.0", + "resolved": "https://registry.npmjs.org/cliui/-/cliui-6.0.0.tgz", + "integrity": "sha512-t6wbgtoCXvAzst7QgXxJYqPt0usEfbgQdftEPbLL/cvv6HPE5VgvqCuAIDR0NgU52ds6rFwqrgakNLrHEjCbrQ==", + "dev": true, + "license": "ISC", + "dependencies": { + "string-width": "^4.2.0", + "strip-ansi": "^6.0.0", + "wrap-ansi": "^6.2.0" + } + }, + "node_modules/openclaw/node_modules/qrcode/node_modules/wrap-ansi": { + "version": "6.2.0", + "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-6.2.0.tgz", + "integrity": "sha512-r6lPcBGxZXlIcymEu7InxDMhdW0KDxpLgoFLcguasxCaJ/SOIZwINatK9KY/tf+ZrlywOKU0UDj3ATXUBfxJXA==", + "dev": true, + "license": "MIT", + "dependencies": { + "ansi-styles": "^4.0.0", + "string-width": "^4.1.0", + "strip-ansi": "^6.0.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/qrcode/node_modules/y18n": { + "version": "4.0.3", + "resolved": "https://registry.npmjs.org/y18n/-/y18n-4.0.3.tgz", + "integrity": "sha512-JKhqTOwSrqNA1NY5lSztJ1GrBiUodLMmIZuLiDaMRJ+itFd+ABVE8XBjOvIWL+rSqNDC74LCSFmlb/U4UZ4hJQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/qrcode/node_modules/yargs": { + "version": "15.4.1", + "resolved": "https://registry.npmjs.org/yargs/-/yargs-15.4.1.tgz", + "integrity": "sha512-aePbxDmcYW++PaqBsJ+HYUFwCdv4LVvdnhBy78E57PIor8/OVvhMrADFFEDh8DHDFRv/O9i3lPhsENjO7QX0+A==", + "dev": true, + "license": "MIT", + "dependencies": { + "cliui": "^6.0.0", + "decamelize": "^1.2.0", + "find-up": "^4.1.0", + "get-caller-file": "^2.0.1", + "require-directory": "^2.1.1", + "require-main-filename": "^2.0.0", + "set-blocking": "^2.0.0", + "string-width": "^4.2.0", + "which-module": "^2.0.0", + "y18n": "^4.0.0", + "yargs-parser": "^18.1.2" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/qrcode/node_modules/yargs-parser": { + "version": "18.1.3", + "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-18.1.3.tgz", + "integrity": "sha512-o50j0JeToy/4K6OZcaQmW6lyXXKhq7csREXcDwk2omFPJEwUNOVtJKvmDr9EI1fAJZUyZcRF7kxGBWmRXudrCQ==", + "dev": true, + "license": "ISC", + "dependencies": { + "camelcase": "^5.0.0", + "decamelize": "^1.2.0" + }, + "engines": { + "node": ">=6" + } + }, + "node_modules/openclaw/node_modules/qs": { + "version": "6.15.2", + "resolved": "https://registry.npmjs.org/qs/-/qs-6.15.2.tgz", + "integrity": "sha512-Rzq0KEyX/w/tEybncDgdkZrJgVUsUMk3xjh3t5bv3S1HTAtg+uOYt72+ZfwiQwKdysThkTBdL/rTi6HDmX9Ddw==", + "dev": true, + "license": "BSD-3-Clause", + "dependencies": { + "side-channel": "^1.1.0" + }, + "engines": { + "node": ">=0.6" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/quickjs-wasi": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/quickjs-wasi/-/quickjs-wasi-3.0.0.tgz", + "integrity": "sha512-X7ouKC4ZVf9bXQ8rsE7+L6TeBbesejAJH61x16xRaGAQGfBHHRcniWgzJZZVtHc8rS9yVsY+Tvk8/usAosg4bg==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/range-parser": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/range-parser/-/range-parser-1.2.1.tgz", + "integrity": "sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.6" + } + }, + "node_modules/openclaw/node_modules/rastermill": { + "version": "0.3.1", + "resolved": "https://registry.npmjs.org/rastermill/-/rastermill-0.3.1.tgz", + "integrity": "sha512-CX4nij6+ZLHYIaojJNfLTr7W+AiH/IPJi6E9Aw1br2///1KZL2KBOHd68rkcLedc47MPvb4hhH+fzYeGFa4A/Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "@silvia-odwyer/photon-node": "0.3.4" + }, + "engines": { + "node": ">=22" + } + }, + "node_modules/openclaw/node_modules/raw-body": { + "version": "3.0.2", + "resolved": "https://registry.npmjs.org/raw-body/-/raw-body-3.0.2.tgz", + "integrity": "sha512-K5zQjDllxWkf7Z5xJdV0/B0WTNqx6vxG70zJE4N0kBs4LovmEYWJzQGxC9bS9RAKu3bgM40lrd5zoLJ12MQ5BA==", + "dev": true, + "license": "MIT", + "dependencies": { + "bytes": "~3.1.2", + "http-errors": "~2.0.1", + "iconv-lite": "~0.7.0", + "unpipe": "~1.0.0" + }, + "engines": { + "node": ">= 0.10" + } + }, + "node_modules/openclaw/node_modules/readable-stream": { + "version": "2.3.8", + "resolved": "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.8.tgz", + "integrity": "sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==", + "dev": true, + "license": "MIT", + "dependencies": { + "core-util-is": "~1.0.0", + "inherits": "~2.0.3", + "isarray": "~1.0.0", + "process-nextick-args": "~2.0.0", + "safe-buffer": "~5.1.1", + "string_decoder": "~1.1.1", + "util-deprecate": "~1.0.1" + } + }, + "node_modules/openclaw/node_modules/readable-stream/node_modules/safe-buffer": { + "version": "5.1.2", + "resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz", + "integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/readdirp": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-5.0.0.tgz", + "integrity": "sha512-9u/XQ1pvrQtYyMpZe7DXKv2p5CNvyVwzUB6uhLAnQwHMSgKMBR62lc7AHljaeteeHXn11XTAaLLUVZYVZyuRBQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 20.19.0" + }, + "funding": { + "type": "individual", + "url": "https://paulmillr.com/funding/" + } + }, + "node_modules/openclaw/node_modules/require-directory": { + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz", + "integrity": "sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/openclaw/node_modules/require-from-string": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz", + "integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/openclaw/node_modules/require-main-filename": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/require-main-filename/-/require-main-filename-2.0.0.tgz", + "integrity": "sha512-NKN5kMDylKuldxYLSUfrbo5Tuzh4hd+2E8NPPX02mZtn1VuREQToYe/ZdlJy+J3uCpfaiGF05e7B8W0iXbQHmg==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/retry": { + "version": "0.13.1", + "resolved": "https://registry.npmjs.org/retry/-/retry-0.13.1.tgz", + "integrity": "sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 4" + } + }, + "node_modules/openclaw/node_modules/router": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/router/-/router-2.2.0.tgz", + "integrity": "sha512-nLTrUKm2UyiL7rlhapu/Zl45FwNgkZGaCpZbIHajDYgwlJCOzLSk+cIPAnsEqV955GjILJnKbdQC1nVPz+gAYQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "debug": "^4.4.0", + "depd": "^2.0.0", + "is-promise": "^4.0.0", + "parseurl": "^1.3.3", + "path-to-regexp": "^8.0.0" + }, + "engines": { + "node": ">= 18" + } + }, + "node_modules/openclaw/node_modules/safe-buffer": { + "version": "5.2.1", + "resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.2.1.tgz", + "integrity": "sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/feross" + }, + { + "type": "patreon", + "url": "https://www.patreon.com/feross" + }, + { + "type": "consulting", + "url": "https://feross.org/support" + } + ], + "license": "MIT" + }, + "node_modules/openclaw/node_modules/safer-buffer": { + "version": "2.1.2", + "resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz", + "integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/send": { + "version": "1.2.1", + "resolved": "https://registry.npmjs.org/send/-/send-1.2.1.tgz", + "integrity": "sha512-1gnZf7DFcoIcajTjTwjwuDjzuz4PPcY2StKPlsGAQ1+YH20IRVrBaXSWmdjowTJ6u8Rc01PoYOGHXfP1mYcZNQ==", + "dev": true, + "license": "MIT", + "dependencies": { + "debug": "^4.4.3", + "encodeurl": "^2.0.0", + "escape-html": "^1.0.3", + "etag": "^1.8.1", + "fresh": "^2.0.0", + "http-errors": "^2.0.1", + "mime-types": "^3.0.2", + "ms": "^2.1.3", + "on-finished": "^2.4.1", + "range-parser": "^1.2.1", + "statuses": "^2.0.2" + }, + "engines": { + "node": ">= 18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/serve-static": { + "version": "2.2.1", + "resolved": "https://registry.npmjs.org/serve-static/-/serve-static-2.2.1.tgz", + "integrity": "sha512-xRXBn0pPqQTVQiC8wyQrKs2MOlX24zQ0POGaj0kultvoOCstBQM5yvOhAVSUwOMjQtTvsPWoNCHfPGwaaQJhTw==", + "dev": true, + "license": "MIT", + "dependencies": { + "encodeurl": "^2.0.0", + "escape-html": "^1.0.3", + "parseurl": "^1.3.3", + "send": "^1.2.0" + }, + "engines": { + "node": ">= 18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/set-blocking": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/set-blocking/-/set-blocking-2.0.0.tgz", + "integrity": "sha512-KiKBS8AnWGEyLzofFfmvKwpdPzqiy16LvQfK3yv/fVH7Bj13/wl3JSR1J+rfgRE9q7xUJK4qvgS8raSOeLUehw==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/setimmediate": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/setimmediate/-/setimmediate-1.0.5.tgz", + "integrity": "sha512-MATJdZp8sLqDl/68LfQmbP8zKPLQNV6BIZoIgrscFDQ+RsvK/BxeDQOgyxKKoh0y/8h3BqVFnCqQ/gd+reiIXA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/setprototypeof": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/setprototypeof/-/setprototypeof-1.2.0.tgz", + "integrity": "sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/shebang-command": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz", + "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==", + "dev": true, + "license": "MIT", + "dependencies": { + "shebang-regex": "^3.0.0" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/shebang-regex": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz", + "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/side-channel": { + "version": "1.1.0", + "resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.1.0.tgz", + "integrity": "sha512-ZX99e6tRweoUXqR+VBrslhda51Nh5MTQwou5tnUDgbtyM0dBgmhEDtWGP/xbKn6hqfPRHujUNwz5fy/wbbhnpw==", + "dev": true, + "license": "MIT", + "dependencies": { + "es-errors": "^1.3.0", + "object-inspect": "^1.13.3", + "side-channel-list": "^1.0.0", + "side-channel-map": "^1.0.1", + "side-channel-weakmap": "^1.0.2" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/side-channel-list": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/side-channel-list/-/side-channel-list-1.0.1.tgz", + "integrity": "sha512-mjn/0bi/oUURjc5Xl7IaWi/OJJJumuoJFQJfDDyO46+hBWsfaVM65TBHq2eoZBhzl9EchxOijpkbRC8SVBQU0w==", + "dev": true, + "license": "MIT", + "dependencies": { + "es-errors": "^1.3.0", + "object-inspect": "^1.13.4" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/side-channel-map": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/side-channel-map/-/side-channel-map-1.0.1.tgz", + "integrity": "sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==", + "dev": true, + "license": "MIT", + "dependencies": { + "call-bound": "^1.0.2", + "es-errors": "^1.3.0", + "get-intrinsic": "^1.2.5", + "object-inspect": "^1.13.3" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/side-channel-weakmap": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/side-channel-weakmap/-/side-channel-weakmap-1.0.2.tgz", + "integrity": "sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==", + "dev": true, + "license": "MIT", + "dependencies": { + "call-bound": "^1.0.2", + "es-errors": "^1.3.0", + "get-intrinsic": "^1.2.5", + "object-inspect": "^1.13.3", + "side-channel-map": "^1.0.1" + }, + "engines": { + "node": ">= 0.4" + }, + "funding": { + "url": "https://github.com/sponsors/ljharb" + } + }, + "node_modules/openclaw/node_modules/signal-exit": { + "version": "3.0.7", + "resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz", + "integrity": "sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/sisteransi": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz", + "integrity": "sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/source-map": { + "version": "0.6.1", + "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz", + "integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==", + "dev": true, + "license": "BSD-3-Clause", + "engines": { + "node": ">=0.10.0" + } + }, + "node_modules/openclaw/node_modules/source-map-support": { + "version": "0.5.21", + "resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.21.tgz", + "integrity": "sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==", + "dev": true, + "license": "MIT", + "dependencies": { + "buffer-from": "^1.0.0", + "source-map": "^0.6.0" + } + }, + "node_modules/openclaw/node_modules/sqlite-vec": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec/-/sqlite-vec-0.1.9.tgz", + "integrity": "sha512-L7XJWRIBNvR9O5+vh1FQ+IGkh/3D2AzVksW5gdtk28m78Hy8skFD0pqReKH1Yp0/BUKRGcffgKvyO/EON5JXpA==", + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "optionalDependencies": { + "sqlite-vec-darwin-arm64": "0.1.9", + "sqlite-vec-darwin-x64": "0.1.9", + "sqlite-vec-linux-arm64": "0.1.9", + "sqlite-vec-linux-x64": "0.1.9", + "sqlite-vec-windows-x64": "0.1.9" + } + }, + "node_modules/openclaw/node_modules/sqlite-vec-darwin-arm64": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec-darwin-arm64/-/sqlite-vec-darwin-arm64-0.1.9.tgz", + "integrity": "sha512-jSsZpE42OfBkGL/ItyJTVCUwl6o6Ka3U5rc4j+UBDIQzC1ulSSKMEhQLthsOnF/MdAf1MuAkYhkdKmmcjaIZQg==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "os": [ + "darwin" + ] + }, + "node_modules/openclaw/node_modules/sqlite-vec-darwin-x64": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec-darwin-x64/-/sqlite-vec-darwin-x64-0.1.9.tgz", + "integrity": "sha512-KDlVyqQT7pnOhU1ymB9gs7dMbSoVmKHitT+k1/xkjarcX8bBqPxWrGlK/R+C5WmWkfvWwyq5FfXfiBYCBs6PlA==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "os": [ + "darwin" + ] + }, + "node_modules/openclaw/node_modules/sqlite-vec-linux-arm64": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec-linux-arm64/-/sqlite-vec-linux-arm64-0.1.9.tgz", + "integrity": "sha512-5wXVJ9c9kR4CHm/wVqXb/R+XUHTdpZ4nWbPHlS+gc9qQFVHs92Km4bPnCKX4rtcPMzvNis+SIzMJR1SCEwpuUw==", + "cpu": [ + "arm64" + ], + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "os": [ + "linux" + ] + }, + "node_modules/openclaw/node_modules/sqlite-vec-linux-x64": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec-linux-x64/-/sqlite-vec-linux-x64-0.1.9.tgz", + "integrity": "sha512-w3tCH8xK2finW8fQJ/m8uqKodXUZ9KAuAar2UIhz4BHILfpE0WM/MTGCRfa7RjYbrYim5Luk3guvMOGI7T7JQA==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "os": [ + "linux" + ] + }, + "node_modules/openclaw/node_modules/sqlite-vec-windows-x64": { + "version": "0.1.9", + "resolved": "https://registry.npmjs.org/sqlite-vec-windows-x64/-/sqlite-vec-windows-x64-0.1.9.tgz", + "integrity": "sha512-y3gEIyy/17bq2QFPQOWLE68TYWcRZkBQVA2XLrTPHNTOp55xJi/BBBmOm40tVMDMjtP+Elpk6UBUXdaq+46b0Q==", + "cpu": [ + "x64" + ], + "dev": true, + "license": "MIT OR Apache", + "optional": true, + "os": [ + "win32" + ] + }, + "node_modules/openclaw/node_modules/standardwebhooks": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/standardwebhooks/-/standardwebhooks-1.0.0.tgz", + "integrity": "sha512-BbHGOQK9olHPMvQNHWul6MYlrRTAOKn03rOe4A8O3CLWhNf4YHBqq2HJKKC+sfqpxiBY52pNeesD6jIiLDz8jg==", + "dev": true, + "license": "MIT", + "dependencies": { + "@stablelib/base64": "^1.0.0", + "fast-sha256": "^1.3.0" + } + }, + "node_modules/openclaw/node_modules/statuses": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/statuses/-/statuses-2.0.2.tgz", + "integrity": "sha512-DvEy55V3DB7uknRo+4iOGT5fP1slR8wQohVdknigZPMpMstaKJQWhwiYBACJE3Ul2pTnATihhBYnRhZQHGBiRw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/string_decoder": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/string_decoder/-/string_decoder-1.1.1.tgz", + "integrity": "sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==", + "dev": true, + "license": "MIT", + "dependencies": { + "safe-buffer": "~5.1.0" + } + }, + "node_modules/openclaw/node_modules/string_decoder/node_modules/safe-buffer": { + "version": "5.1.2", + "resolved": "https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz", + "integrity": "sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/string-width": { + "version": "4.2.3", + "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz", + "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==", + "dev": true, + "license": "MIT", + "dependencies": { + "emoji-regex": "^8.0.0", + "is-fullwidth-code-point": "^3.0.0", + "strip-ansi": "^6.0.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/strip-ansi": { + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", + "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", + "dev": true, + "license": "MIT", + "dependencies": { + "ansi-regex": "^5.0.1" + }, + "engines": { + "node": ">=8" + } + }, + "node_modules/openclaw/node_modules/strtok3": { + "version": "10.3.5", + "resolved": "https://registry.npmjs.org/strtok3/-/strtok3-10.3.5.tgz", + "integrity": "sha512-ki4hZQfh5rX0QDLLkOCj+h+CVNkqmp/CMf8v8kZpkNVK6jGQooMytqzLZYUVYIZcFZ6yDB70EfD8POcFXiF5oA==", + "dev": true, + "license": "MIT", + "dependencies": { + "@tokenizer/token": "^0.3.0" + }, + "engines": { + "node": ">=18" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/Borewit" + } + }, + "node_modules/openclaw/node_modules/tar": { + "version": "7.5.15", + "resolved": "https://registry.npmjs.org/tar/-/tar-7.5.15.tgz", + "integrity": "sha512-dzGK0boVlC4W5QFuQN1EFSl3bIDYsk7Tj40U6eIBnK2k/8ml7TZ5agbI5j5+qnoVcAA+rNtBml8SEiLxZpNqRQ==", + "dev": true, + "license": "BlueOak-1.0.0", + "dependencies": { + "@isaacs/fs-minipass": "^4.0.0", + "chownr": "^3.0.0", + "minipass": "^7.1.2", + "minizlib": "^3.1.0", + "yallist": "^5.0.0" + }, + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/toidentifier": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/toidentifier/-/toidentifier-1.0.1.tgz", + "integrity": "sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=0.6" + } + }, + "node_modules/openclaw/node_modules/token-types": { + "version": "6.1.2", + "resolved": "https://registry.npmjs.org/token-types/-/token-types-6.1.2.tgz", + "integrity": "sha512-dRXchy+C0IgK8WPC6xvCHFRIWYUbqqdEIKPaKo/AcTUNzwLTK6AH7RjdLWsEZcAN/TBdtfUw3PYEgPr5VPr6ww==", + "dev": true, + "license": "MIT", + "dependencies": { + "@borewit/text-codec": "^0.2.1", + "@tokenizer/token": "^0.3.0", + "ieee754": "^1.2.1" + }, + "engines": { + "node": ">=14.16" + }, + "funding": { + "type": "github", + "url": "https://github.com/sponsors/Borewit" + } + }, + "node_modules/openclaw/node_modules/tr46": { + "version": "0.0.3", + "resolved": "https://registry.npmjs.org/tr46/-/tr46-0.0.3.tgz", + "integrity": "sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/tree-sitter-bash": { + "version": "0.25.1", + "resolved": "https://registry.npmjs.org/tree-sitter-bash/-/tree-sitter-bash-0.25.1.tgz", + "integrity": "sha512-7hMytuYIMoXOq24yRulgIxthE9YmggZIOHCyPTTuJcu6EU54tYD+4G39cUb28kxC6jMf/AbPfWGLQtgPTdh3xw==", + "dev": true, + "hasInstallScript": true, + "license": "MIT", + "dependencies": { + "node-addon-api": "^8.2.1", + "node-gyp-build": "^4.8.2" + }, + "peerDependencies": { + "tree-sitter": "^0.25.0" + }, + "peerDependenciesMeta": { + "tree-sitter": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/ts-algebra": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/ts-algebra/-/ts-algebra-2.0.0.tgz", + "integrity": "sha512-FPAhNPFMrkwz76P7cdjdmiShwMynZYN6SgOujD1urY4oNm80Ou9oMdmbR45LotcKOXoy7wSmHkRFE6Mxbrhefw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/tslib": { + "version": "2.8.1", + "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz", + "integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==", + "dev": true, + "license": "0BSD" + }, + "node_modules/openclaw/node_modules/tslog": { + "version": "4.10.2", + "resolved": "https://registry.npmjs.org/tslog/-/tslog-4.10.2.tgz", + "integrity": "sha512-XuELoRpMR+sq8fuWwX7P0bcj+PRNiicOKDEb3fGNURhxWVyykCi9BNq7c4uVz7h7P0sj8qgBsr5SWS6yBClq3g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=16" + }, + "funding": { + "url": "https://github.com/fullstack-build/tslog?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/type-is": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/type-is/-/type-is-2.1.0.tgz", + "integrity": "sha512-faYHw0anBbc/kWF3zFTEnxSFOAGUX9GFbOBthvDdLsIlEoWOFOtS0zgCiQYwIskL9iGXZL3kAXD8OoZ4GmMATA==", + "dev": true, + "license": "MIT", + "dependencies": { + "content-type": "^2.0.0", + "media-typer": "^1.1.0", + "mime-types": "^3.0.0" + }, + "engines": { + "node": ">= 18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/type-is/node_modules/content-type": { + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/content-type/-/content-type-2.0.0.tgz", + "integrity": "sha512-j/O/d7GcZCyNl7/hwZAb606rzqkyvaDctLmckbxLzHvFBzTJHuGEdodATcP3yIRoDrLHkIATJuvzbFlp/ki2cQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/express" + } + }, + "node_modules/openclaw/node_modules/typebox": { + "version": "1.1.39", + "resolved": "https://registry.npmjs.org/typebox/-/typebox-1.1.39.tgz", + "integrity": "sha512-vj0afVtOfLQvv0GR0VxVagYxsXN64btL7Z9XoaG0ZggH3mruMMkOO6hXdgMsjCY3shZgEvooAWVeznQVs5c43w==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/typescript": { + "version": "6.0.3", + "resolved": "https://registry.npmjs.org/typescript/-/typescript-6.0.3.tgz", + "integrity": "sha512-y2TvuxSZPDyQakkFRPZHKFm+KKVqIisdg9/CZwm9ftvKXLP8NRWj38/ODjNbr43SsoXqNuAisEf1GdCxqWcdBw==", + "dev": true, + "license": "Apache-2.0", + "bin": { + "tsc": "bin/tsc", + "tsserver": "bin/tsserver" + }, + "engines": { + "node": ">=14.17" + } + }, + "node_modules/openclaw/node_modules/uhyphen": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/uhyphen/-/uhyphen-0.2.0.tgz", + "integrity": "sha512-qz3o9CHXmJJPGBdqzab7qAYuW8kQGKNEuoHFYrBwV6hWIMcpAmxDLXojcHfFr9US1Pe6zUswEIJIbLI610fuqA==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/uint8array-extras": { + "version": "1.5.0", + "resolved": "https://registry.npmjs.org/uint8array-extras/-/uint8array-extras-1.5.0.tgz", + "integrity": "sha512-rvKSBiC5zqCCiDZ9kAOszZcDvdAHwwIKJG33Ykj43OKcWsnmcBRL09YTU4nOeHZ8Y2a7l1MgTd08SBe9A8Qj6A==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=18" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/openclaw/node_modules/undici": { + "version": "8.3.0", + "resolved": "https://registry.npmjs.org/undici/-/undici-8.3.0.tgz", + "integrity": "sha512-TkUDgb6tl7KOGZ+7e8E3d2FYgUQgF6z5YypqjWmixVQSQERFcVrVg0ySADm2LVLRh5ljAaHTCR5Fmz3Q34rB7Q==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=22.19.0" + } + }, + "node_modules/openclaw/node_modules/unpipe": { + "version": "1.0.0", + "resolved": "https://registry.npmjs.org/unpipe/-/unpipe-1.0.0.tgz", + "integrity": "sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/util-deprecate": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz", + "integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/vary": { + "version": "1.1.2", + "resolved": "https://registry.npmjs.org/vary/-/vary-1.1.2.tgz", + "integrity": "sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 0.8" + } + }, + "node_modules/openclaw/node_modules/web-push": { + "version": "3.6.7", + "resolved": "https://registry.npmjs.org/web-push/-/web-push-3.6.7.tgz", + "integrity": "sha512-OpiIUe8cuGjrj3mMBFWY+e4MMIkW3SVT+7vEIjvD9kejGUypv8GPDf84JdPWskK8zMRIJ6xYGm+Kxr8YkPyA0A==", + "dev": true, + "license": "MPL-2.0", + "dependencies": { + "asn1.js": "^5.3.0", + "http_ece": "1.2.0", + "https-proxy-agent": "^7.0.0", + "jws": "^4.0.0", + "minimist": "^1.2.5" + }, + "bin": { + "web-push": "src/cli.js" + }, + "engines": { + "node": ">= 16" + } + }, + "node_modules/openclaw/node_modules/web-streams-polyfill": { + "version": "3.3.3", + "resolved": "https://registry.npmjs.org/web-streams-polyfill/-/web-streams-polyfill-3.3.3.tgz", + "integrity": "sha512-d2JWLCivmZYTSIoge9MsgFCZrt571BikcWGYkjC1khllbTeDlGqZ2D8vD8E/lJa8WGWbb7Plm8/XJYV7IJHZZw==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">= 8" + } + }, + "node_modules/openclaw/node_modules/web-tree-sitter": { + "version": "0.26.9", + "resolved": "https://registry.npmjs.org/web-tree-sitter/-/web-tree-sitter-0.26.9.tgz", + "integrity": "sha512-YJwSHANl6XFgeEjB8nitgj0qZYt5gkIesJ4w2srS2wcLB4GUa4xcOkM0YaMsU6WNR53YVIkDSY7Ej4pf3IXtCA==", + "dev": true, + "license": "MIT" + }, + "node_modules/openclaw/node_modules/webidl-conversions": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/webidl-conversions/-/webidl-conversions-3.0.1.tgz", + "integrity": "sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==", + "dev": true, + "license": "BSD-2-Clause" + }, + "node_modules/openclaw/node_modules/whatwg-url": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/whatwg-url/-/whatwg-url-5.0.0.tgz", + "integrity": "sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==", + "dev": true, + "license": "MIT", + "dependencies": { + "tr46": "~0.0.3", + "webidl-conversions": "^3.0.0" + } + }, + "node_modules/openclaw/node_modules/which": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz", + "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==", + "dev": true, + "license": "ISC", + "dependencies": { + "isexe": "^2.0.0" + }, + "bin": { + "node-which": "bin/node-which" + }, + "engines": { + "node": ">= 8" + } + }, + "node_modules/openclaw/node_modules/which-module": { + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/which-module/-/which-module-2.0.1.tgz", + "integrity": "sha512-iBdZ57RDvnOR9AGBhML2vFZf7h8vmBjhoaZqODJBFWHVtKkDmKuHai3cx5PgVMrX5YDNp27AofYbAwctSS+vhQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/wrap-ansi": { + "version": "7.0.0", + "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz", + "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==", + "dev": true, + "license": "MIT", + "dependencies": { + "ansi-styles": "^4.0.0", + "string-width": "^4.1.0", + "strip-ansi": "^6.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/wrap-ansi?sponsor=1" + } + }, + "node_modules/openclaw/node_modules/wrappy": { + "version": "1.0.2", + "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz", + "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==", + "dev": true, + "license": "ISC" + }, + "node_modules/openclaw/node_modules/ws": { + "version": "8.21.0", + "resolved": "https://registry.npmjs.org/ws/-/ws-8.21.0.tgz", + "integrity": "sha512-Vsp28b7DRcimFQvrqu2Wek3z1iYxDCWqHYB8Qsnk/S4RfaCQzPGPyBNuVjJV3cd6UiKtUtp6sNM77gWvzcCH+g==", + "dev": true, + "license": "MIT", + "engines": { + "node": ">=10.0.0" + }, + "peerDependencies": { + "bufferutil": "^4.0.1", + "utf-8-validate": ">=5.0.2" + }, + "peerDependenciesMeta": { + "bufferutil": { + "optional": true + }, + "utf-8-validate": { + "optional": true + } + } + }, + "node_modules/openclaw/node_modules/y18n": { + "version": "5.0.8", + "resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz", + "integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==", + "dev": true, + "license": "ISC", + "engines": { + "node": ">=10" + } + }, + "node_modules/openclaw/node_modules/yallist": { + "version": "5.0.0", + "resolved": "https://registry.npmjs.org/yallist/-/yallist-5.0.0.tgz", + "integrity": "sha512-YgvUTfwqyc7UXVMrB+SImsVYSmTS8X/tSrtdNZMImM+n7+QTriRXyXim0mBrTXNeqzVF0KWGgHPeiyViFFrNDw==", + "dev": true, + "license": "BlueOak-1.0.0", + "engines": { + "node": ">=18" + } + }, + "node_modules/openclaw/node_modules/yaml": { + "version": "2.9.0", + "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.9.0.tgz", + "integrity": "sha512-2AvhNX3mb8zd6Zy7INTtSpl1F15HW6Wnqj0srWlkKLcpYl/gMIMJiyuGq2KeI2YFxUPjdlB+3Lc10seMLtL4cA==", + "dev": true, + "license": "ISC", + "bin": { + "yaml": "bin.mjs" + }, + "engines": { + "node": ">= 14.6" + }, + "funding": { + "url": "https://github.com/sponsors/eemeli" + } + }, + "node_modules/openclaw/node_modules/yargs": { + "version": "17.7.2", + "resolved": "https://registry.npmjs.org/yargs/-/yargs-17.7.2.tgz", + "integrity": "sha512-7dSzzRQ++CKnNI/krKnYRV7JKKPUXMEh61soaHKg9mrWEhzFWhFnxPxGl+69cD1Ou63C13NUPCnmIcrvqCuM6w==", + "dev": true, + "license": "MIT", + "dependencies": { + "cliui": "^8.0.1", + "escalade": "^3.1.1", + "get-caller-file": "^2.0.5", + "require-directory": "^2.1.1", + "string-width": "^4.2.3", + "y18n": "^5.0.5", + "yargs-parser": "^21.1.1" + }, + "engines": { + "node": ">=12" + } + }, + "node_modules/openclaw/node_modules/yargs-parser": { + "version": "21.1.1", + "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz", + "integrity": "sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==", + "dev": true, + "license": "ISC", + "engines": { + "node": ">=12" + } + }, + "node_modules/openclaw/node_modules/zod": { + "version": "4.4.3", + "resolved": "https://registry.npmjs.org/zod/-/zod-4.4.3.tgz", + "integrity": "sha512-ytENFjIJFl2UwYglde2jchW2Hwm4GJFLDiSXWdTrJQBIN9Fcyp7n4DhxJEiWNAJMV1/BqWfW/kkg71UDcHJyTQ==", + "dev": true, + "license": "MIT", + "funding": { + "url": "https://github.com/sponsors/colinhacks" + } + }, + "node_modules/openclaw/node_modules/zod-to-json-schema": { + "version": "3.25.2", + "resolved": "https://registry.npmjs.org/zod-to-json-schema/-/zod-to-json-schema-3.25.2.tgz", + "integrity": "sha512-O/PgfnpT1xKSDeQYSCfRI5Gy3hPf91mKVDuYLUHZJMiDFptvP41MSnWofm8dnCm0256ZNfZIM7DSzuSMAFnjHA==", + "dev": true, + "license": "ISC", + "peerDependencies": { + "zod": "^3.25.28 || ^4" + } + }, + "node_modules/typescript": { + "version": "5.9.3", + "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz", + "integrity": "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==", + "dev": true, + "license": "Apache-2.0", + "bin": { + "tsc": "bin/tsc", + "tsserver": "bin/tsserver" + }, + "engines": { + "node": ">=14.17" + } + }, + "node_modules/undici-types": { + "version": "6.21.0", + "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-6.21.0.tgz", + "integrity": "sha512-iwDZqg0QAGrg9Rav5H4n0M64c3mkR59cJ6wQp+7C4nI0gsmExaedaYLNO44eT4AtBBwjbTiGPMlt2Md0T9H9JQ==", + "dev": true, + "license": "MIT" + }, + "node_modules/yaml": { + "version": "2.9.0", + "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.9.0.tgz", + "integrity": "sha512-2AvhNX3mb8zd6Zy7INTtSpl1F15HW6Wnqj0srWlkKLcpYl/gMIMJiyuGq2KeI2YFxUPjdlB+3Lc10seMLtL4cA==", + "license": "ISC", + "bin": { + "yaml": "bin.mjs" + }, + "engines": { + "node": ">= 14.6" + }, + "funding": { + "url": "https://github.com/sponsors/eemeli" + } } } } diff --git a/package.json b/package.json index f4c605f..b7d422e 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "foreman-sh", - "version": "1.0.0", + "version": "1.1.0-rc.1", "description": "AI-powered strategic advisor for entrepreneurs. 158 skills, 24 diagnostics, 21 playbooks, 9 industry packs.", "type": "module", "bin": { @@ -8,14 +8,28 @@ }, "files": [ "bin/", + "dist/", ".claude/", - "CLAUDE.md" + "CLAUDE.md", + "openclaw.plugin.json", + "openclaw-templates/", + "plugins/foreman/", + ".codex-plugin/", + ".claude-plugin/plugin.json", + "docs/", + "assets/", + "CONTRIBUTING.md", + "VISION.md" ], "author": { "name": "Fatih Guner", "url": "https://foreman.sh" }, "license": "MIT", + "publishConfig": { + "access": "public", + "tag": "next" + }, "repository": { "type": "git", "url": "git+https://github.com/fatihguner/foreman.git" @@ -39,20 +53,39 @@ "solopreneur" ], "engines": { - "node": ">=18.0.0" + "node": ">=22.19.0" }, "openclaw": { - "extensions": ["./index.ts"] + "extensions": [ + "./dist/index.js" + ] }, "dependencies": { - "@sinclair/typebox": "^0.32.0" + "@sinclair/typebox": "^0.32.0", + "yaml": "^2.8.1" }, "peerDependencies": { - "openclaw": ">=2026.3.0" + "openclaw": ">=2026.6.1" }, "peerDependenciesMeta": { "openclaw": { "optional": true } + }, + "scripts": { + "test": "node --test tests/*.test.js", + "validate": "node scripts/validate.mjs", + "check": "npm run validate && npm test && npm run typecheck", + "typecheck": "tsc --noEmit", + "build": "tsc -p tsconfig.build.json", + "build:plugins": "node scripts/build-plugins.mjs", + "check:release": "node scripts/check-release.mjs", + "test:package": "node scripts/package-smoke.mjs", + "prepack": "npm run build && npm run build:plugins" + }, + "devDependencies": { + "@types/node": "^22.0.0", + "typescript": "~5.9.3", + "openclaw": "2026.6.1" } } diff --git a/plugins/foreman/.claude-plugin/plugin.json b/plugins/foreman/.claude-plugin/plugin.json index 5aa13af..6577711 100644 --- a/plugins/foreman/.claude-plugin/plugin.json +++ b/plugins/foreman/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "foreman", - "version": "1.0.0", + "version": "1.1.0-rc.1", "description": "AI-powered strategic advisor for entrepreneurs. 158 business framework skills across 12 categories, with diagnostics, playbooks, output templates, and industry-specific packs.", "author": { "name": "Fatih Guner" diff --git a/plugins/foreman/commands/abort.md b/plugins/foreman/commands/abort.md new file mode 100644 index 0000000..42d32f9 --- /dev/null +++ b/plugins/foreman/commands/abort.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /abort command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /abort + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/about.md b/plugins/foreman/commands/about.md new file mode 100644 index 0000000..db763f1 --- /dev/null +++ b/plugins/foreman/commands/about.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /about command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /about + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /about with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/apply.md b/plugins/foreman/commands/apply.md new file mode 100644 index 0000000..f0f74b5 --- /dev/null +++ b/plugins/foreman/commands/apply.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /apply command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /apply + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/execution-commands.md and execute only /apply with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/back.md b/plugins/foreman/commands/back.md new file mode 100644 index 0000000..5bdec1b --- /dev/null +++ b/plugins/foreman/commands/back.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /back command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /back + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/playbook-commands.md and execute only /back with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/blockers.md b/plugins/foreman/commands/blockers.md new file mode 100644 index 0000000..3435075 --- /dev/null +++ b/plugins/foreman/commands/blockers.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /blockers command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /blockers + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/implementation-commands.md and execute only /blockers with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/check-in.md b/plugins/foreman/commands/check-in.md new file mode 100644 index 0000000..9177c44 --- /dev/null +++ b/plugins/foreman/commands/check-in.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /check-in command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /check-in + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/implementation-commands.md and execute only /check-in with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/coalition.md b/plugins/foreman/commands/coalition.md new file mode 100644 index 0000000..4d7b00a --- /dev/null +++ b/plugins/foreman/commands/coalition.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /coalition command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /coalition + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/org-politics-commands.md and execute only /coalition with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/compare.md b/plugins/foreman/commands/compare.md new file mode 100644 index 0000000..804c774 --- /dev/null +++ b/plugins/foreman/commands/compare.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /compare command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /compare + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/output-commands.md and execute only /compare with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/decisions.md b/plugins/foreman/commands/decisions.md new file mode 100644 index 0000000..e1eee12 --- /dev/null +++ b/plugins/foreman/commands/decisions.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /decisions command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /decisions + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /decisions with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/diagnose.md b/plugins/foreman/commands/diagnose.md new file mode 100644 index 0000000..17783bf --- /dev/null +++ b/plugins/foreman/commands/diagnose.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /diagnose command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnose + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/execution-commands.md and execute only /diagnose with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +Before answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact. diff --git a/plugins/foreman/commands/diagnostics.md b/plugins/foreman/commands/diagnostics.md new file mode 100644 index 0000000..af81802 --- /dev/null +++ b/plugins/foreman/commands/diagnostics.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /diagnostics command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnostics + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /diagnostics with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/export.md b/plugins/foreman/commands/export.md new file mode 100644 index 0000000..af5f9da --- /dev/null +++ b/plugins/foreman/commands/export.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /export command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /export + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/output-commands.md and execute only /export with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/feedback.md b/plugins/foreman/commands/feedback.md new file mode 100644 index 0000000..60f8afd --- /dev/null +++ b/plugins/foreman/commands/feedback.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /feedback command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /feedback + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /feedback with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/follow-ups.md b/plugins/foreman/commands/follow-ups.md new file mode 100644 index 0000000..e051b1e --- /dev/null +++ b/plugins/foreman/commands/follow-ups.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /follow-ups command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /follow-ups + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /follow-ups with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-context.md b/plugins/foreman/commands/foreman-context.md new file mode 100644 index 0000000..e4cbbce --- /dev/null +++ b/plugins/foreman/commands/foreman-context.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /context command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /context + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /context with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-help.md b/plugins/foreman/commands/foreman-help.md new file mode 100644 index 0000000..2fad921 --- /dev/null +++ b/plugins/foreman/commands/foreman-help.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /help command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /help + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /help with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-reset.md b/plugins/foreman/commands/foreman-reset.md new file mode 100644 index 0000000..4a9141c --- /dev/null +++ b/plugins/foreman/commands/foreman-reset.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /reset command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /reset + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /reset with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-resume.md b/plugins/foreman/commands/foreman-resume.md new file mode 100644 index 0000000..ae31926 --- /dev/null +++ b/plugins/foreman/commands/foreman-resume.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resume command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resume + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/execution-commands.md and execute only /resume with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-run.md b/plugins/foreman/commands/foreman-run.md new file mode 100644 index 0000000..e201de7 --- /dev/null +++ b/plugins/foreman/commands/foreman-run.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /run command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /run + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/execution-commands.md and execute only /run with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-skill.md b/plugins/foreman/commands/foreman-skill.md new file mode 100644 index 0000000..52a3ab8 --- /dev/null +++ b/plugins/foreman/commands/foreman-skill.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skill command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skill + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /skill with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/foreman-status.md b/plugins/foreman/commands/foreman-status.md new file mode 100644 index 0000000..6476bb4 --- /dev/null +++ b/plugins/foreman/commands/foreman-status.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /status command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /status + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/playbook-commands.md and execute only /status with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/forget.md b/plugins/foreman/commands/forget.md new file mode 100644 index 0000000..9583e1b --- /dev/null +++ b/plugins/foreman/commands/forget.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /forget command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /forget + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /forget with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/format.md b/plugins/foreman/commands/format.md new file mode 100644 index 0000000..655a73a --- /dev/null +++ b/plugins/foreman/commands/format.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /format command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /format + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/output-commands.md and execute only /format with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/history.md b/plugins/foreman/commands/history.md new file mode 100644 index 0000000..4fd0766 --- /dev/null +++ b/plugins/foreman/commands/history.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /history command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /history + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /history with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/hooks.md b/plugins/foreman/commands/hooks.md new file mode 100644 index 0000000..cd9dcc0 --- /dev/null +++ b/plugins/foreman/commands/hooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /hooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /hooks + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /hooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/language.md b/plugins/foreman/commands/language.md new file mode 100644 index 0000000..5c7eb91 --- /dev/null +++ b/plugins/foreman/commands/language.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /language command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /language + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/language-command.md and execute only /language with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/commands/output.md b/plugins/foreman/commands/output.md new file mode 100644 index 0000000..a408c48 --- /dev/null +++ b/plugins/foreman/commands/output.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /output command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /output + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/execution-commands.md and execute only /output with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/pause.md b/plugins/foreman/commands/pause.md new file mode 100644 index 0000000..46548d0 --- /dev/null +++ b/plugins/foreman/commands/pause.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /pause command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /pause + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/playbook-commands.md and execute only /pause with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/playbooks.md b/plugins/foreman/commands/playbooks.md new file mode 100644 index 0000000..393231d --- /dev/null +++ b/plugins/foreman/commands/playbooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /playbooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /playbooks + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /playbooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/power-map.md b/plugins/foreman/commands/power-map.md new file mode 100644 index 0000000..7c0aa46 --- /dev/null +++ b/plugins/foreman/commands/power-map.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /power-map command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /power-map + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/org-politics-commands.md and execute only /power-map with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/progress.md b/plugins/foreman/commands/progress.md new file mode 100644 index 0000000..e7203d3 --- /dev/null +++ b/plugins/foreman/commands/progress.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /progress command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /progress + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/implementation-commands.md and execute only /progress with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/research.md b/plugins/foreman/commands/research.md new file mode 100644 index 0000000..385c929 --- /dev/null +++ b/plugins/foreman/commands/research.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /research command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /research + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/research-commands.md and execute only /research with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/resistance.md b/plugins/foreman/commands/resistance.md new file mode 100644 index 0000000..f85641c --- /dev/null +++ b/plugins/foreman/commands/resistance.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resistance command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resistance + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/org-politics-commands.md and execute only /resistance with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/search.md b/plugins/foreman/commands/search.md new file mode 100644 index 0000000..1a188f9 --- /dev/null +++ b/plugins/foreman/commands/search.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /search command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /search + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /search with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/sector.md b/plugins/foreman/commands/sector.md new file mode 100644 index 0000000..1dd6de2 --- /dev/null +++ b/plugins/foreman/commands/sector.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /sector command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /sector + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /sector with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/simulate.md b/plugins/foreman/commands/simulate.md new file mode 100644 index 0000000..09dd018 --- /dev/null +++ b/plugins/foreman/commands/simulate.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /simulate command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /simulate + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/simulation-commands.md and execute only /simulate with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/skills.md b/plugins/foreman/commands/skills.md new file mode 100644 index 0000000..d768565 --- /dev/null +++ b/plugins/foreman/commands/skills.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skills command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skills + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /skills with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/skip.md b/plugins/foreman/commands/skip.md new file mode 100644 index 0000000..b3d258c --- /dev/null +++ b/plugins/foreman/commands/skip.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skip command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skip + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/playbook-commands.md and execute only /skip with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/solo.md b/plugins/foreman/commands/solo.md new file mode 100644 index 0000000..20efc5a --- /dev/null +++ b/plugins/foreman/commands/solo.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /solo command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /solo + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/solo-command.md and execute only /solo with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/commands/stage.md b/plugins/foreman/commands/stage.md new file mode 100644 index 0000000..d3b0c8f --- /dev/null +++ b/plugins/foreman/commands/stage.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stage command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stage + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/stakeholders.md b/plugins/foreman/commands/stakeholders.md new file mode 100644 index 0000000..46b24b8 --- /dev/null +++ b/plugins/foreman/commands/stakeholders.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stakeholders command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stakeholders + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/org-politics-commands.md and execute only /stakeholders with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/stoic.md b/plugins/foreman/commands/stoic.md new file mode 100644 index 0000000..231c317 --- /dev/null +++ b/plugins/foreman/commands/stoic.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /stoic command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stoic + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/stoic-command.md and execute only /stoic with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/commands/templates.md b/plugins/foreman/commands/templates.md new file mode 100644 index 0000000..10ff1e8 --- /dev/null +++ b/plugins/foreman/commands/templates.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /templates command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /templates + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/navigation-commands.md and execute only /templates with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/track.md b/plugins/foreman/commands/track.md new file mode 100644 index 0000000..bebfa80 --- /dev/null +++ b/plugins/foreman/commands/track.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /track command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /track + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/implementation-commands.md and execute only /track with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/update.md b/plugins/foreman/commands/update.md new file mode 100644 index 0000000..b052dd4 --- /dev/null +++ b/plugins/foreman/commands/update.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /update command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /update + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/memory-commands.md and execute only /update with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/commands/version.md b/plugins/foreman/commands/version.md new file mode 100644 index 0000000..2fe263b --- /dev/null +++ b/plugins/foreman/commands/version.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /version command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /version + +Read ${CLAUDE_PLUGIN_ROOT}/content/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/content/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/content/commands/meta-commands.md and execute only /version with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/content/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/content. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/RUNTIME.md b/plugins/foreman/content/RUNTIME.md new file mode 100644 index 0000000..97acbf1 --- /dev/null +++ b/plugins/foreman/content/RUNTIME.md @@ -0,0 +1,33 @@ +# Foreman runtime contract + +This document defines current runtime behavior. Use it when older examples in command, mode or memory documents describe a different storage shape. + +Resolve paths relative to this content directory (the directory containing this file). In a cloned or initialized Claude project this is `.claude/`. In a plugin it is the bundled `content/` directory. In Codex the `foreman` skill links here. Read `policies/advisory.md` and `catalog.json` before routing. + +For a specific request, search `catalog.json` for the requested kind and identifier and read only the matching entry and aliases. Load the entire catalog only when browsing or comparing many entries. This avoids carrying the full catalog through every advisory turn. + +Use exact catalog identifiers first, then `aliases`, then a unique normalized name. Ask the user to choose if several identifiers match. Reject empty names and paths. A diagnostic or template is not a skill: use the catalog's `kind` to load the correct layer. Semantic content links are relative to each source file, while instruction paths beginning `.claude/` are relative to this content root after removing that prefix. + +## Persistence + +All hosts use schema version 1 at `/.foreman//state.json`. Keep this file private and outside version control. The default founder ID for the local CLI is `default`. For multiple founders, pass an explicit ID on every call; never infer another founder's records. OpenClaw scopes data by its trusted agent and sender context. To share an existing agent-only store with the CLI, pass that agent ID as `--founder`. + +Run `node "/runtime/run.mjs" --workspace "" --founder default ...`. Substitute real absolute paths and shell-quote each argument. User text is data; never interpolate it as executable shell syntax. This runtime needs Node 22.19 or later, and no package install or network connection. Check its exit status and returned JSON. Do not edit `state.json` directly. + +Read profile: `profile`. Set `/solo`: `profile --mode solo`; `/solo off`: `profile --mode standard`. Set `/stoic`: `profile --stoic on`; off uses `off`. Set `/language tr`: `profile --language tr`; default uses `en`; status only reads. `/sector saas` uses `profile --sector saas`. Always read persisted settings at the start of a new session. + +Read tasks: `track --filter all` (also `active`, `overdue`, `stalled`, or any of the six statuses). Add a confirmed task: `task --id impl-001 --description "Interview five customers" --deadline 2026-10-01`. Update `/progress impl-001 40 note`: `task --id impl-001 --progress 40 --note "note"`. Status changes use `--status not-started|in-progress|blocked|completed|abandoned|deferred`. A completed task has progress 100. Use `--revision N` when editing a previously read revision; a conflict requires rereading, not overwriting. + +After a confirmed playbook step, save the next step: `resume --playbook pivot-playbook --step 2`. Read `resume` to continue from that checkpoint; verify the playbook and step against the catalog before writing. The exposed Claude command is `/foreman-resume`, because `/resume` is a host command. Never mark a step complete based merely on a generated recommendation. + +If the runtime or workspace is unavailable, explain that persistence is unavailable and keep the session usable. Do not fabricate saved tasks. Do not run a package installer automatically to enable persistence. + +## Schema and legacy migration + +Canonical preferences are `identity.mode` (`standard|solo`), `identity.stoic_mode` (boolean), `identity.language` (language code or name), and `company.sector`. Tasks are `implementation_items`; the checkpoint is `active.playbook: {id, next_step}` or null. Every record has `schema_version: 1`, `founder_id`, `revision` and `history`. + +Legacy YAML memory remains readable source material. To migrate, read the user's existing identity/company/active/history files, assemble their parsed contents into one JSON object in a temporary file, and run `migrate --input ""`. Migrate into an unused founder destination only. The runtime normalizes `mode_solo`, `mode_stoic`, and `preferences` and preserves the original object under `legacy`. A validation error leaves the destination unchanged. Keep original files until the user has verified the result. Never silently reset a malformed or newer state file. + +## Host commands + +Claude project commands are the files in `commands/`; names that conflict with built-ins use the `foreman-` prefix. Use `/foreman-run` for playbooks and `/foreman-skill` for skill previews. The latter also avoids a `skill.md` / `SKILL.md` filesystem collision that hides sibling commands. Plugin commands use `/foreman:NAME`. Consult `catalog.json` for the exact map. In Codex, invoke `$foreman` with the requested operation or use an individual framework skill. Do not advertise Claude slash commands as Codex commands. diff --git a/plugins/foreman/content/_schema/agents/agent-template.md b/plugins/foreman/content/_schema/agents/agent-template.md new file mode 100644 index 0000000..a7e2446 --- /dev/null +++ b/plugins/foreman/content/_schema/agents/agent-template.md @@ -0,0 +1,126 @@ +--- +name: "kebab-case-agent-name" +description: "Third-person description of this agent's role within the Foreman orchestration layer. Max 1024 characters." +role: "orchestrator | diagnostic | skill-executor | playbook-runner | memory | output" +triggers: + - "activation condition that causes this agent to be invoked" + - "another activation condition" +dependencies: + - "other-agent-name" +inputs: + - "what this agent receives from its caller" +outputs: + - "what this agent produces and returns" +author: "Fatih Guner" +--- + + + +# {Agent Name} + +## Role + + + +{Role definition} + +--- + +## Responsibilities + + + +- {Responsibility 1} +- {Responsibility 2} +- {Responsibility 3} + +--- + +## Activation + + + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| {condition} | {calling agent} | {high/medium/low} | + +--- + +## Workflow + + + +1. {Step 1} +2. {Step 2} +3. {Step 3} + +``` +pseudocode where helpful +``` + +--- + +## Interactions + + + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| {agent-name} | {sends to / receives from / bidirectional} | {data description} | + +--- + +## Decision Rules + + + +- **IF** {condition} **THEN** {action} +- **IF** {condition} **THEN** {action} + +--- + +## Error Handling + + + +| Failure Mode | Response | +|-------------|----------| +| {failure} | {how the agent handles it} | + +--- + +## Example Flow + + + +**Scenario:** {description} + +1. {Step with specific component references} +2. {Step with specific component references} +3. {Step with specific component references} + +**Result:** {what the agent produces} diff --git a/plugins/foreman/content/_schema/commands/command-template.md b/plugins/foreman/content/_schema/commands/command-template.md new file mode 100644 index 0000000..9d2223a --- /dev/null +++ b/plugins/foreman/content/_schema/commands/command-template.md @@ -0,0 +1,82 @@ +--- +name: "command-group-name" +description: "What this command group covers and when these commands apply." +category: "navigation | execution | memory | playbook | output | meta" +commands: + - name: "/command" + syntax: "/command [required] [--optional]" + description: "What it does in one sentence." + - name: "/another-command" + syntax: "/another-command [required] [--flag value]" + description: "What it does in one sentence." +author: "Fatih Guner" +--- + + + +# {Command Group Title} + +## `/command` + +### Description + +{One paragraph explaining what this command does, when to use it, and what it returns.} + +### Syntax + +``` +/command [required-param] [--optional-flag value] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `required-param` | Yes | string | -- | {What this parameter controls} | +| `--optional-flag` | No | string | `all` | {What this flag filters or modifies} | + +### Examples + +``` +/command value +→ {Expected output summary} + +/command value --optional-flag setting +→ {Expected output summary} + +/command another-value +→ {Expected output summary} +``` + +### Related Commands + +- `/other-command` — {How it connects to this command} + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/command` (missing required param) | `Missing required parameter. Usage: /command [required-param]` | +| `/command nonexistent` | `No match found for "nonexistent". Run /search to find available options.` | + +--- + + diff --git a/plugins/foreman/content/agents/diagnostic-agent.md b/plugins/foreman/content/agents/diagnostic-agent.md new file mode 100644 index 0000000..49ad201 --- /dev/null +++ b/plugins/foreman/content/agents/diagnostic-agent.md @@ -0,0 +1,246 @@ +--- +name: "diagnostic-agent" +description: "Triage specialist that executes diagnostic files by presenting entry symptoms, asking sequential triage questions following decision-tree logic, mapping answer patterns to a structured diagnosis, and returning a routing recommendation to the orchestrator. Operates entirely as an internal agent — never communicates with the entrepreneur directly." +role: "diagnostic" +triggers: + - "orchestrator determines triage is required before skill or playbook selection" + - "hook routes to a diagnostic file" + - "previous diagnosis returned ambiguous results and re-triage is requested" +dependencies: + - "orchestrator-agent" +inputs: + - "diagnostic file reference (one of 20 diagnostics)" + - "entrepreneur context from memory-agent (stage, sector, history)" + - "entrepreneur answers relayed through orchestrator" +outputs: + - "structured diagnosis with confidence level" + - "routing recommendation: skill(s) and/or playbook with rationale" + - "red flags identified during triage" +author: "Fatih Guner" +--- + +# Diagnostic Agent + +## Role + +The diagnostic agent is the system's triage function. Entrepreneurs routinely misidentify their problems — a founder who says "sales are dropping" may have a pricing problem, a product-market fit gap, a team execution failure, or a competitive threat. The diagnostic agent's purpose is to move from symptom to root cause through structured questioning before the system commits to a framework or playbook. + +This agent does not communicate with the entrepreneur. It produces questions for the orchestrator to relay, receives answers through the orchestrator, and returns a structured diagnosis. It does not apply frameworks, generate output documents, or persist data. + +--- + +## Responsibilities + +- Load and parse the specified diagnostic file +- Present entry symptoms to the orchestrator for confirmation with the entrepreneur +- Generate triage questions in sequence, following the diagnostic's decision-tree logic +- Process each answer and determine the next branch in the decision tree +- Map the complete answer pattern to one of the diagnostic's possible diagnoses +- Assign a confidence level to the diagnosis +- Return a structured routing recommendation (skills and/or playbooks) +- Identify and flag red flags encountered during triage +- Handle ambiguous answer patterns that do not map cleanly to any diagnosis + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| Hook routes to a diagnostic and no prior diagnosis exists for this topic | orchestrator-agent | High | +| Previous diagnostic result was ambiguous and orchestrator requests re-triage | orchestrator-agent | High | +| Playbook prerequisite check requires diagnostic confirmation | playbook-runner-agent (via orchestrator) | Medium | + +--- + +## Workflow + +### Step 1: Load Diagnostic + +1. Receive diagnostic file reference and entrepreneur context from the orchestrator. +2. Parse the diagnostic file: extract entry symptoms, triage questions, diagnosis map, routing table, and red flags. +3. Cross-reference entrepreneur context with entry symptoms to confirm the diagnostic is appropriate. + +``` +diagnostic = LOAD diagnostic_file(reference) +context = RECEIVE entrepreneur_context + +IF NOT diagnostic.entry_symptoms OVERLAP WITH context.reported_symptoms + RETURN { + status: "mismatch", + message: "Reported symptoms do not align with this diagnostic. Recommend re-evaluation at hook level." + } +``` + +### Step 1b: Industry Pack Diagnostic Rules + +If an industry pack is active (passed from orchestrator via `context.industry_pack`), load the pack's diagnostic rules file. Add sector-specific triage questions to the question set, adjust diagnosis weights for sector-native conditions, and include sector-specific diagnoses that do not exist in the base diagnostic (e.g., churn-specific diagnoses for SaaS, regulatory compliance diagnoses for fintech). + +``` +IF context.industry_pack EXISTS + pack_rules = context.industry_pack.diagnostic_rules[diagnostic.name] + IF pack_rules EXISTS + APPEND pack_rules.sector_triage_questions TO diagnostic.triage_questions + ADJUST diagnostic.diagnosis_map WEIGHTS WITH pack_rules.weight_adjustments + MERGE pack_rules.sector_diagnoses INTO diagnostic.diagnosis_map +``` + +### Step 2: Symptom Confirmation + +4. Return entry symptoms to the orchestrator for the entrepreneur to confirm or refine. +5. If the entrepreneur refines the symptoms, update the working context before proceeding. + +``` +confirmation = SEND entry_symptoms TO orchestrator FOR entrepreneur_confirmation +IF confirmation.refined + UPDATE working_context WITH confirmation.refinements +``` + +### Step 3: Sequential Triage + +6. Begin with the first triage question (Q1 in the diagnostic file). +7. Send each question to the orchestrator for relay to the entrepreneur. +8. Receive the answer and evaluate it against the diagnostic's branching logic. +9. Select the next question based on the answer. Not all questions are asked — the decision tree skips branches that prior answers have eliminated. +10. Continue until a terminal branch is reached or all relevant questions have been asked. + +``` +current_question = diagnostic.triage_questions[0] +answers = {} +path = [] + +WHILE current_question IS NOT terminal + answer = SEND current_question TO orchestrator FOR entrepreneur_response + answers[current_question.id] = answer + path.APPEND(current_question.id) + + next = EVALUATE branch_logic(current_question, answer, diagnostic) + IF next == TERMINAL + BREAK + current_question = next +``` + +### Step 4: Diagnosis Mapping + +11. Map the accumulated answer pattern against the diagnostic's diagnosis map. +12. Each diagnostic defines answer-to-diagnosis mappings (e.g., `product-market-fit-diagnosis` maps Q1 < 20% + Q2 = idea-first to "solution-looking-for-a-problem"). +13. Calculate confidence based on answer clarity and pattern completeness. + +``` +diagnosis = MAP answers TO diagnostic.diagnosis_map +confidence = CALCULATE pattern_match_strength(answers, diagnosis) + +IF confidence < 0.6 + GOTO Step 5 (ambiguity handling) +ELSE + GOTO Step 6 (result assembly) +``` + +### Step 5: Ambiguity Handling + +14. If the answer pattern does not map clearly to any single diagnosis (confidence below threshold), the agent has three options: + - **Option A:** Ask up to two supplementary questions to break the tie, drawn from the diagnostic's secondary question set or constructed from the competing diagnoses' distinguishing criteria. + - **Option B:** Return a dual diagnosis with both candidates, their respective confidence levels, and a note that the orchestrator should ask a disambiguation question. + - **Option C:** If no supplementary questions can resolve the ambiguity, flag uncertainty explicitly and return the most probable diagnosis with a low-confidence tag. + +``` +IF competing_diagnoses.LENGTH == 2 + supplementary = GENERATE tiebreaker_question(competing_diagnoses) + IF supplementary EXISTS + answer = SEND supplementary TO orchestrator + diagnosis = RE-EVALUATE WITH supplementary answer + ELSE + RETURN dual_diagnosis(competing_diagnoses, confidence_levels) +ELSE + RETURN {diagnosis: best_guess, confidence: "low", flag: "ambiguous"} +``` + +### Step 6: Result Assembly + +15. Construct the structured diagnosis result. +16. Pull the routing recommendation from the diagnostic's routing table based on the confirmed diagnosis. +17. Check for red flags documented in the diagnostic file and flag any that match the entrepreneur's pattern. + +``` +result = { + diagnosis: diagnosis.name, + confidence: confidence, + answer_path: path, + routing: diagnostic.routing_table[diagnosis.name], + red_flags: MATCH diagnostic.red_flags AGAINST answers AND context, + summary: GENERATE diagnosis_summary(diagnosis, answers, context) +} + +// Research validation suggestion +routed_skills = result.routing.skills +matching_guides = SEARCH research_guides WHERE feeds_into_skills INTERSECTS routed_skills +IF matching_guides IS NOT EMPTY + result.validation_suggestion = "To confirm this diagnosis, gather " + + matching_guides[0].data_type + " using `/research " + matching_guides[0].name + "`." + +RETURN result TO orchestrator +``` + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| orchestrator-agent | Bidirectional | Receives: diagnostic reference, entrepreneur context, entrepreneur answers. Sends: triage questions, diagnosis result, routing recommendation. | + +The diagnostic agent communicates exclusively with the orchestrator. It has no direct channel to any other specialist agent. + +--- + +## Decision Rules + +- **IF** entry symptoms do not match the entrepreneur's reported situation **THEN** return a mismatch signal to the orchestrator with a recommendation to re-evaluate at the hook level. +- **IF** the entrepreneur's answer to a triage question is ambiguous or incomplete **THEN** send a follow-up probe that restates the question with more specific options. Maximum two follow-up probes per question. +- **IF** the answer path reaches a terminal branch with a clear single diagnosis **THEN** return that diagnosis with high confidence. +- **IF** the answer path produces two competing diagnoses within 15% confidence of each other **THEN** attempt a supplementary tiebreaker question before returning a dual diagnosis. +- **IF** supplementary questions fail to resolve ambiguity **THEN** return both diagnoses with their respective confidence levels and let the orchestrator decide. +- **IF** any red flag condition is met during triage **THEN** include the red flag in the result regardless of diagnosis outcome. Red flags are never suppressed. +- **IF** the entrepreneur has completed this same diagnostic within the past 30 days and answers are substantially unchanged **THEN** flag staleness and recommend the orchestrator check whether circumstances have genuinely changed before re-running. +- **IF** the diagnostic file references a skill or playbook that does not exist in the repository **THEN** omit the broken reference from the routing recommendation and flag the gap. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Diagnostic file not found or malformed | Return error to orchestrator with diagnostic name. Suggest alternative diagnostics from overlapping hooks. | +| Entrepreneur does not answer a triage question (skip or refuse) | Proceed with remaining questions. Reduce confidence proportionally. Note the skipped question in the result. | +| Answer pattern matches no diagnosis in the map | Return a null diagnosis with the complete answer path. Recommend the orchestrator ask an open-ended follow-up or route to the most general skill in the hook's routing table. | +| Triage loop detected (same question cycling) | Force a terminal branch after the second cycle. Return best available diagnosis with low confidence. | +| Orchestrator sends context for wrong entrepreneur | Validate entrepreneur_id against diagnostic session. Reject if mismatched. | + +--- + +## Example Flow + +**Scenario:** The orchestrator routes to `product-market-fit-diagnosis` for an early-traction B2B SaaS founder who reports "users sign up but don't stick." + +1. **Load diagnostic.** Agent loads `product-market-fit-diagnosis`. Entry symptoms: "Customers use it but don't love it," "Retention is low despite good acquisition." Symptoms align with reported input. + +2. **Symptom confirmation.** Agent sends entry symptoms to orchestrator. Entrepreneur confirms: "Yes, exactly — they sign up, use it for a few days, then disappear." + +3. **Q1 (Sean Ellis test).** "If your product disappeared tomorrow, what percentage of users would be very disappointed?" Entrepreneur answers: "Maybe 25-30%." Agent evaluates: 20-40% range. A kernel of fit exists in a subset. Proceed to Q3. + +4. **Q3 (Who are the enthusiasts?).** "Who are the users who do love the product, and do they resemble your target customer?" Entrepreneur answers: "The ones who stay are mostly freelancers, but we're targeting mid-market teams." Agent evaluates: enthusiasts are a different segment from target. Likely diagnosis: **right-solution-wrong-segment**. Proceed to Q5 for confirmation. + +5. **Q5 (Price response).** "What happens when you ask free users to pay?" Entrepreneur answers: "The freelancers complain about price but keep using it. The mid-market teams just go silent." Agent evaluates: dual signal — pricing resistance from engaged segment, indifference from target segment. Confirms **right-solution-wrong-segment**. + +6. **Diagnosis mapping.** Answer pattern: Q1 = 20-40%, Q3 = segment divergence, Q5 = split response. Maps to **right-solution-wrong-segment** with 0.82 confidence. + +7. **Red flag check.** No red flags triggered (founder has not pivoted multiple times, no premature scaling indicators). + +8. **Result assembly.** Agent returns to orchestrator: + - Diagnosis: right-solution-wrong-segment + - Confidence: 0.82 + - Routing: Apply `four-ps-marketing` (realign positioning to the responding segment), then `blue-ocean-strategy` (determine if the freelancer segment represents a viable market) + - Output template: `strategic-analysis-one-pager` + - Red flags: none + +**Result:** The orchestrator receives a clear diagnosis with actionable routing, enabling it to delegate to the skill-executor-agent with precision rather than applying frameworks speculatively. diff --git a/plugins/foreman/content/agents/memory-agent.md b/plugins/foreman/content/agents/memory-agent.md new file mode 100644 index 0000000..680ba98 --- /dev/null +++ b/plugins/foreman/content/agents/memory-agent.md @@ -0,0 +1,361 @@ +--- +name: "memory-agent" +description: "Context persistence specialist that reads and writes entrepreneur memory — company stage, sector, team composition, prior diagnostics, past skill applications, decisions made, ongoing playbooks, and session history. Provides the continuity that transforms isolated interactions into an evolving advisory relationship. Manages memory schema, staleness detection, and data pruning." +role: "memory" +triggers: + - "orchestrator requests entrepreneur context at session start (READ)" + - "orchestrator sends session results for persistence at session end (WRITE)" + - "orchestrator checks for active playbooks or prior diagnostics mid-session" +dependencies: + - "orchestrator-agent" +inputs: + - "READ: entrepreneur identifier" + - "WRITE: entrepreneur identifier, session data (hook matched, path taken, diagnosis, skills applied, results, decisions)" +outputs: + - "READ: structured entrepreneur context" + - "WRITE: confirmation of persistence, staleness warnings" +author: "Fatih Guner" +--- + +# Memory Agent + +## Role + +Without memory, every conversation starts from zero. The entrepreneur repeats their stage, their sector, their team size, their history. The system re-runs diagnostics it has already completed. Skill applications ignore prior analyses. Playbooks restart from step one. The memory-agent prevents this by maintaining a persistent, structured record of each entrepreneur's context and interaction history. + +This agent operates exclusively through the orchestrator. It does not communicate with the entrepreneur, apply frameworks, run diagnostics, or format output. It receives read requests (retrieve context) and write requests (persist session data), and it manages the integrity and freshness of what it stores. + +--- + +## Responsibilities + +- Retrieve entrepreneur context on demand (READ operations) +- Persist session results after each substantive interaction (WRITE operations) +- Maintain a structured memory schema with defined fields and types +- Detect and flag stale data (entries that may no longer reflect the entrepreneur's situation) +- Prune expired or superseded entries to prevent memory bloat +- Merge new session data with existing records without overwriting still-valid history +- Track ongoing playbook state for cross-session resumption +- Provide differential context: what has changed since the last session + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| Session initialization — orchestrator needs entrepreneur context | orchestrator-agent | Immediate | +| Session conclusion — orchestrator sends results for persistence | orchestrator-agent | High | +| Mid-session query — orchestrator checks for active playbooks or prior diagnoses | orchestrator-agent | Medium | + +--- + +## Memory Schema + +The memory-agent maintains the following structured record per entrepreneur. + +### Identity + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `entrepreneur_id` | string | Unique identifier | Never | +| `company_name` | string | Current company name | Never (updated on change) | +| `sector` | string | Industry or vertical | Never (updated on change) | +| `stage` | enum | `idea`, `validation`, `early-traction`, `growth`, `scale` | Never (updated on change) | +| `team_size` | integer | Current headcount | 90 days (re-confirm) | +| `founded_date` | date | When the company was started | Never | + +### Interaction History + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `sessions` | array | Ordered list of session records | Individual sessions expire after 365 days | +| `sessions[].timestamp` | datetime | When the session occurred | — | +| `sessions[].hook_matched` | string | Which hook classified the input | — | +| `sessions[].path_taken` | enum | `diagnostic`, `skill`, `playbook` | — | +| `sessions[].diagnosis` | object | Diagnosis result if applicable | — | +| `sessions[].skills_applied` | array | Skill names applied during session | — | +| `sessions[].results_summary` | string | Condensed summary of analysis output | — | +| `sessions[].decisions` | array | Decisions the entrepreneur articulated | — | + +### Diagnostic History + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `diagnostics_completed` | array | List of completed diagnostics with results | 180 days (re-confirm if revisited) | +| `diagnostics_completed[].name` | string | Diagnostic file name | — | +| `diagnostics_completed[].diagnosis` | string | The diagnosis reached | — | +| `diagnostics_completed[].confidence` | float | Confidence level of diagnosis | — | +| `diagnostics_completed[].date` | date | When the diagnostic was completed | — | +| `diagnostics_completed[].red_flags` | array | Red flags identified during triage | — | + +### Skill Application History + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `skills_applied` | array | List of skills applied with context | 365 days | +| `skills_applied[].name` | string | Skill file name | — | +| `skills_applied[].date` | date | When the skill was applied | — | +| `skills_applied[].context_summary` | string | What the skill was applied to | — | +| `skills_applied[].anti_patterns_flagged` | array | Anti-patterns that matched | — | + +### Active Playbooks + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `active_playbooks` | array | Playbooks currently in progress | 30 days without activity | +| `active_playbooks[].name` | string | Playbook file name | — | +| `active_playbooks[].current_step` | integer | Last completed step index | — | +| `active_playbooks[].checkpoint_data` | object | Full checkpoint for resumption | — | +| `active_playbooks[].last_activity` | datetime | When this playbook was last advanced | — | + +### Decisions Log + +| Field | Type | Description | Expiry | +|-------|------|-------------|--------| +| `decisions` | array | Strategic decisions the entrepreneur has made | Never (historical record) | +| `decisions[].description` | string | What was decided | — | +| `decisions[].date` | date | When the decision was made | — | +| `decisions[].context` | string | What analysis informed the decision | — | +| `decisions[].status` | enum | `active`, `reversed`, `superseded` | — | + +--- + +## Workflow: READ + +### Step 1: Retrieve + +1. Receive entrepreneur identifier from the orchestrator. +2. Load the entrepreneur's full memory record. +3. If no record exists, return an empty context structure (new entrepreneur). + +``` +record = LOAD memory_store(entrepreneur_id) + +IF record IS NULL + RETURN { + status: "new_entrepreneur", + context: EMPTY_CONTEXT_SCHEMA + } +``` + +### Step 2: Staleness Check + +4. Scan all fields for expiry conditions. +5. Flag any field that has exceeded its expiry window. +6. Do not delete stale data on read — flag it so the orchestrator can decide whether to re-confirm or proceed with caveats. + +``` +stale_fields = [] +FOR EACH field IN record + IF field.expiry EXISTS AND field.last_updated + field.expiry < NOW + stale_fields.APPEND({ + field: field.name, + last_updated: field.last_updated, + age: NOW - field.last_updated + }) +``` + +### Step 3: Assemble Context + +7. Construct the structured context response: current identity fields, recent interaction history (last 10 sessions), active diagnostics, active playbooks, recent decisions. +8. Include staleness warnings. +9. Include a differential summary: what changed since the last session. + +``` +context = { + identity: record.identity, + recent_sessions: record.sessions[-10:], + diagnostics: FILTER record.diagnostics_completed WHERE NOT expired, + active_playbooks: record.active_playbooks, + recent_decisions: FILTER record.decisions WHERE status == "active", + stale_warnings: stale_fields, + last_session_delta: DIFF(record.sessions[-1], record.sessions[-2]) +} +RETURN context TO orchestrator +``` + +--- + +## Workflow: WRITE + +### Step 1: Receive Session Data + +1. Receive entrepreneur identifier and session data from the orchestrator. +2. Validate that the session data contains the minimum required fields. + +``` +session_data = RECEIVE FROM orchestrator +VALIDATE session_data CONTAINS {timestamp, hook_matched, path_taken} +``` + +### Step 2: Extract Persistable Data + +3. Parse the session data for persistable entries: new diagnoses, skill applications, decisions, playbook progress, and any identity changes the entrepreneur mentioned. +4. Detect identity changes: if the entrepreneur mentioned a new team hire, a stage transition, or a sector pivot, update the identity fields. + +``` +persistable = { + session_record: BUILD session_entry(session_data), + new_diagnoses: EXTRACT diagnoses(session_data), + new_skills: EXTRACT skill_applications(session_data), + new_decisions: EXTRACT decisions(session_data), + playbook_updates: EXTRACT playbook_progress(session_data), + identity_changes: DETECT identity_updates(session_data) +} +``` + +### Step 3: Merge + +5. Load the existing memory record. +6. Merge new data with existing data, following these rules: + - Sessions: append the new session record. + - Diagnostics: append new diagnoses. If a diagnosis for the same diagnostic file already exists, keep both (the new one supersedes but the old one provides history). + - Skills: append new skill applications. + - Decisions: append new decisions. If a new decision contradicts a prior one, mark the prior decision as `superseded`. + - Playbooks: update the checkpoint for active playbooks. Mark completed playbooks as closed. + - Identity: overwrite identity fields only when a change is explicitly detected. + +``` +record = LOAD memory_store(entrepreneur_id) + +record.sessions.APPEND(persistable.session_record) +record.diagnostics_completed.EXTEND(persistable.new_diagnoses) + +FOR EACH skill IN persistable.new_skills + record.skills_applied.APPEND(skill) + +FOR EACH decision IN persistable.new_decisions + conflicting = FIND record.decisions WHERE contradicts(decision) + IF conflicting EXISTS + conflicting.status = "superseded" + record.decisions.APPEND(decision) + +FOR EACH update IN persistable.playbook_updates + existing = FIND record.active_playbooks WHERE name == update.name + IF existing EXISTS + existing.checkpoint_data = update.checkpoint_data + existing.current_step = update.current_step + existing.last_activity = NOW + IF update.status == "complete" + MOVE existing TO record.completed_playbooks + ELSE + record.active_playbooks.APPEND(update) + +IF persistable.identity_changes NOT EMPTY + APPLY persistable.identity_changes TO record.identity +``` + +### Step 4: Prune + +7. After merging, run the pruning cycle: remove entries that have exceeded their expiry window and are not actively referenced by any current analysis or playbook. + +``` +FOR EACH session IN record.sessions + IF session.timestamp + 365 days < NOW + AND session NOT REFERENCED BY active_playbooks + REMOVE session FROM record.sessions + +FOR EACH diagnostic IN record.diagnostics_completed + IF diagnostic.date + 180 days < NOW + AND diagnostic NOT REFERENCED BY active_playbooks + ARCHIVE diagnostic // move to cold storage, not delete + +FOR EACH playbook IN record.active_playbooks + IF playbook.last_activity + 30 days < NOW + MARK playbook AS "stale" + // do not auto-delete; flag for orchestrator confirmation +``` + +### Step 5: Persist and Confirm + +8. Write the updated record to the memory store. +9. Return confirmation to the orchestrator with a summary of what was persisted. + +``` +SAVE record TO memory_store(entrepreneur_id) +RETURN { + status: "persisted", + summary: { + sessions_total: record.sessions.LENGTH, + new_diagnoses_added: persistable.new_diagnoses.LENGTH, + new_skills_added: persistable.new_skills.LENGTH, + new_decisions_added: persistable.new_decisions.LENGTH, + identity_changes: persistable.identity_changes, + pruned_entries: pruned_count, + stale_playbooks_flagged: stale_playbook_count + } +} +``` + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| orchestrator-agent | Bidirectional | Receives: entrepreneur_id (READ), entrepreneur_id + session data (WRITE). Sends: structured context (READ), persistence confirmation (WRITE). | + +The memory-agent communicates exclusively with the orchestrator. No other agent reads from or writes to memory directly. + +--- + +## Decision Rules + +- **IF** the entrepreneur is new (no prior record) **THEN** return an empty context schema. Do not infer or fabricate history. +- **IF** a memory field is stale but the entrepreneur has not been asked to re-confirm **THEN** flag as stale in the read response but do not delete. The orchestrator decides whether to re-confirm. +- **IF** a new diagnosis contradicts a prior diagnosis for the same diagnostic file **THEN** keep both. Mark the older one as superseded. Contradictions are informative — they show the business has changed. +- **IF** a new decision contradicts a prior active decision **THEN** mark the prior decision as `superseded` and log the contradiction. Decision reversals are a normal part of entrepreneurship. +- **IF** an active playbook has been inactive for over 30 days **THEN** flag as stale on the next read. Do not auto-delete — the entrepreneur may return to it. +- **IF** the memory store is unavailable **THEN** return an error to the orchestrator. The orchestrator can proceed without memory but must note the limitation. +- **IF** the write payload is larger than expected (e.g., a playbook with extensive step results) **THEN** store the full results for the most recent 3 sessions and compress older sessions to summary-only format. +- **IF** an identity field changes (e.g., stage transitions from `validation` to `early-traction`) **THEN** log the transition with a timestamp. Stage transitions are milestones worth preserving. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Memory store unavailable on READ | Return error. Orchestrator proceeds without context. Retry on next interaction. | +| Memory store unavailable on WRITE | Queue the write operation. Retry on next session initialization. If the queue exceeds 3 pending writes, alert the orchestrator. | +| Corrupted record detected | Return the most recent valid snapshot. Flag corruption. Do not serve partially corrupted data without warning. | +| Entrepreneur ID collision (two records for the same entrepreneur) | Return the more recently active record. Flag the duplicate for manual resolution. | +| Write conflict (concurrent sessions for the same entrepreneur) | Apply last-write-wins for identity fields. Append-merge for array fields (sessions, decisions). No data should be silently lost. | + +--- + +## Example Flow + +**Scenario:** A returning founder starts a new session. The orchestrator requests context (READ), then persists results after the session (WRITE). + +### READ + +1. **Request.** Orchestrator calls `memory-agent.read("entrepreneur-4827")`. + +2. **Retrieve.** Agent loads the record. Entrepreneur: "Nadia Sorel," B2B SaaS, stage = early-traction, team size = 6 (last confirmed 45 days ago). + +3. **Staleness check.** Team size was last confirmed 45 days ago (within 90-day window — not stale). An active playbook `pricing-strategy-playbook` has `last_activity` = 38 days ago (over 30-day threshold — flagged stale). + +4. **Assemble context.** Returns to orchestrator: + - Identity: Nadia Sorel, B2B SaaS, early-traction, team size 6 + - Recent sessions: last 3 sessions (product-hook, revenue-and-sales-hook, product-hook) + - Diagnostics: `product-market-fit-diagnosis` completed 60 days ago (diagnosis: pricing-value-disconnect, confidence: 0.82) + - Active playbooks: `pricing-strategy-playbook` at step 3 of 5 (flagged stale) + - Recent decisions: "Test freelancer-tier pricing at $19/month" (active), "Pause mid-market outbound sales" (active) + - Stale warnings: `pricing-strategy-playbook` inactive for 38 days + - Last session delta: previous session applied `four-ps-marketing` and `business-model-canvas` + +### WRITE + +5. **Receive.** After the session, orchestrator sends session data: hook = `product-hook`, path = skill, skills applied = [`net-promoter-score`], diagnosis = none (prior diagnosis still valid), decisions = ["Launch freelancer tier at $19/month by end of Q2"]. + +6. **Extract.** New skill application: `net-promoter-score` applied in context of freelancer segment validation. New decision: "Launch freelancer tier at $19/month by end of Q2." No identity changes detected. + +7. **Merge.** Append session record. Append `net-promoter-score` to skills applied. The new decision refines but does not contradict prior decision "Test freelancer-tier pricing at $19/month" — the prior decision is marked as `superseded` by the more specific launch commitment. + +8. **Prune.** No entries exceed expiry thresholds. Stale playbook `pricing-strategy-playbook` remains flagged but not pruned. + +9. **Confirm.** Returns to orchestrator: persisted successfully. 1 session added, 1 skill logged, 1 decision added, 1 prior decision superseded. + +**Result:** The next time this entrepreneur returns, the orchestrator will receive full context including the updated decision, the NPS analysis history, and a prompt to ask whether the stale pricing strategy playbook should be resumed or abandoned. diff --git a/plugins/foreman/content/agents/orchestrator-agent.md b/plugins/foreman/content/agents/orchestrator-agent.md new file mode 100644 index 0000000..6cfe348 --- /dev/null +++ b/plugins/foreman/content/agents/orchestrator-agent.md @@ -0,0 +1,301 @@ +--- +name: "orchestrator-agent" +description: "Central routing intelligence that receives all entrepreneur input, resolves intent through hook matching, retrieves persistent context from memory, determines whether the situation requires diagnostics, a single skill, or a multi-step playbook, delegates to specialist agents, assembles the final response, and ensures session data is persisted. The only agent that communicates directly with the entrepreneur." +role: "orchestrator" +triggers: + - "any entrepreneur input — text, question, complaint, request" + - "session initialization — new or returning entrepreneur" + - "follow-up within an active conversation thread" +dependencies: + - "diagnostic-agent" + - "skill-executor-agent" + - "playbook-runner-agent" + - "output-agent" + - "memory-agent" +inputs: + - "raw entrepreneur text input" + - "conversation history within the current session" +outputs: + - "formatted response to entrepreneur" + - "session data persisted via memory-agent" +author: "Fatih Guner" +--- + +# Orchestrator Agent + +## Role + +The orchestrator is the singular interface between the entrepreneur and the Foreman system. No other agent communicates with the user directly. Every inbound message passes through the orchestrator, which classifies intent, retrieves context, routes to the appropriate specialist, collects results, and delivers a formatted response. It owns the conversation lifecycle from first input to final output. + +The orchestrator does not perform analysis itself. It does not run diagnostics, apply frameworks, execute playbook steps, format documents, or manage memory. Each of those functions belongs to a specialist agent. The orchestrator's sole function is to decide what needs to happen and delegate to whichever agent can do it. + +--- + +## Responsibilities + +- Receive and parse all entrepreneur input +- Match input against the 16 hooks to classify intent +- Resolve ambiguity when multiple hooks match or no hook matches +- Request entrepreneur context from the memory-agent at the start of every session +- Determine the routing path: diagnostic, single skill, playbook, or clarifying question +- Delegate to the diagnostic-agent when triage is required +- Delegate to the skill-executor-agent when a single framework suffices +- Delegate to the playbook-runner-agent when a multi-step sequence is required +- Delegate to the output-agent for all response formatting +- Delegate to the memory-agent for session persistence after every substantive interaction +- Manage conversation threading and follow-up context within a session +- Escalate gracefully when the system cannot resolve the entrepreneur's problem + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| New entrepreneur message received | External (user input) | Immediate | +| Session initialization (new or returning user) | System | Immediate | +| Follow-up message within active thread | External (user input) | Immediate | + +The orchestrator is always active. It is the entry point for every interaction and cannot be bypassed. + +--- + +## Workflow + +### Phase 1: Input Reception and Context Retrieval + +1. Receive raw entrepreneur input. +2. Send context request to `memory-agent` with entrepreneur identifier. +3. Receive structured context: company stage, sector, team size, previous diagnostics, past skill applications, ongoing playbooks, prior decisions. +4. If returning entrepreneur with an active playbook in progress, check whether the new input is a continuation or a new topic. + +``` +RECEIVE input FROM entrepreneur +context = CALL memory-agent.read(entrepreneur_id) + +// Industry Pack Loading +sector = context.company.sector +available_packs = ["saas", "marketplace", "e-commerce", "fintech", "ai-ml", "healthtech", "edtech", "d2c-consumer", "agency-consulting"] +IF sector IN available_packs + pack = LOAD industry-pack(sector) + PASS pack.skill_overlays TO skill-executor-agent + PASS pack.diagnostic_rules TO diagnostic-agent + PASS pack.templates TO output-agent + context.industry_pack = pack + +IF context.active_playbook EXISTS + IF input RELATES TO context.active_playbook + RESUME playbook via playbook-runner-agent + RETURN + ELSE + PROCEED to Phase 2 (new intent) +``` + +### Phase 2: Hook Matching and Intent Classification + +5. Run input against all 16 hooks: `communication-hook`, `competition-hook`, `culture-hook`, `decision-hook`, `fundraising-hook`, `growth-hook`, `innovation-hook`, `launch-hook`, `leadership-hook`, `negotiation-hook`, `partnership-hook`, `personal-growth-hook`, `product-hook`, `revenue-and-sales-hook`, `strategy-hook`, `team-hook`. +6. Collect all matching hooks with their confidence scores and priority levels. +7. Apply disambiguation logic (see Decision Rules). + +``` +matches = [] +FOR EACH hook IN hooks + score = hook.match(input) + IF score > THRESHOLD + matches.APPEND({hook, score, hook.priority}) + +IF matches.LENGTH == 0 + GOTO Phase 3a (no match) +IF matches.LENGTH == 1 + GOTO Phase 3b (single match) +IF matches.LENGTH > 1 + GOTO Phase 3c (disambiguation) +``` + +### Phase 3a: No Hook Match + +8. No hook matched the input with sufficient confidence. Ask the entrepreneur an open-ended clarifying question that narrows toward one of the 16 hook domains without exposing system internals. + +``` +response = GENERATE clarifying_question( + input, + context, + hook_domains = [list of 16 hook categories] +) +CALL output-agent.format(response, audience="self") +RETURN response TO entrepreneur +``` + +### Phase 3b: Single Hook Match + +9. One hook matched clearly. Extract the classified intent and routing destination from the hook. +10. Proceed to Phase 4. + +### Phase 3c: Multiple Hook Match (Disambiguation) + +11. Multiple hooks matched. Apply the disambiguation protocol: + - Compare priority levels. If one hook is `high` and others are `medium` or `low`, the high-priority hook wins. + - If priorities are equal, compare confidence scores. The highest score wins if the margin exceeds 20%. + - If priorities and scores are close, check the hook's disambiguation section for explicit overlap resolution rules. + - If no clear winner emerges, ask the entrepreneur a targeted disambiguation question that distinguishes between the competing intents. + +``` +IF top_match.priority > second_match.priority + winner = top_match +ELIF top_match.score - second_match.score > 0.20 + winner = top_match +ELIF top_match.hook.disambiguation RESOLVES conflict + winner = APPLY disambiguation_rule +ELSE + response = GENERATE disambiguation_question(matches, input) + RETURN response TO entrepreneur +``` + +12. Proceed to Phase 4 with the winning hook. + +### Phase 4: Route Decision + +13. The matched hook provides routing destinations: diagnostics, skills, and/or playbooks. +14. Determine which path to take based on the following logic: + +``` +route = matched_hook.routes_to + +IF route.diagnostics NOT EMPTY AND context.lacks_prior_diagnosis_for(route.diagnostics) + path = "diagnostic" +ELIF route.playbooks NOT EMPTY AND problem_complexity(input, context) == "multi-step" + path = "playbook" +ELIF route.skills NOT EMPTY + path = "skill" +ELSE + path = "diagnostic" // default to triage when uncertain +``` + +15. Factor in entrepreneur context from memory: if the entrepreneur has already completed the relevant diagnostic in a prior session and the situation has not changed, skip directly to skills or playbook. + +### Phase 5: Delegation + +16. **Diagnostic path:** Send the diagnostic file reference and entrepreneur context to `diagnostic-agent`. Receive structured diagnosis with routing recommendation. Use the recommendation to invoke either `skill-executor-agent` or `playbook-runner-agent`. + +17. **Skill path:** Send the skill reference and entrepreneur context to `skill-executor-agent`. Receive contextualized analysis. + +18. **Playbook path:** Send the playbook reference and entrepreneur context to `playbook-runner-agent`. Receive compiled playbook results across all steps. + +``` +IF path == "diagnostic" + diagnosis = CALL diagnostic-agent.run(route.diagnostics[0], context) + IF diagnosis.routes_to_skill + result = CALL skill-executor-agent.apply(diagnosis.recommended_skill, context) + ELIF diagnosis.routes_to_playbook + result = CALL playbook-runner-agent.run(diagnosis.recommended_playbook, context) + +ELIF path == "skill" + result = CALL skill-executor-agent.apply(route.skills[0], context) + +ELIF path == "playbook" + result = CALL playbook-runner-agent.run(route.playbooks[0], context) +``` + +### Phase 6: Response Assembly + +19. Send raw analysis results to `output-agent` with audience specification. Default audience is `self` (the entrepreneur). If the entrepreneur requested a specific audience format (e.g., "prepare this for my investors"), override accordingly. +20. Receive formatted response from `output-agent`. + +``` +audience = DETERMINE audience(input, context) // default: "self" +formatted = CALL output-agent.format(result, audience) +``` + +### Phase 7: Memory Persistence + +21. Send session data to `memory-agent` for persistence: the input, the routing path taken, the diagnosis (if any), the skill(s) applied, results produced, and any decisions the entrepreneur articulated during the session. + +``` +CALL memory-agent.write(entrepreneur_id, { + input: input, + hook_matched: matched_hook.name, + path_taken: path, + diagnosis: diagnosis OR null, + skills_applied: [skill_names], + results: result, + decisions: EXTRACT decisions(conversation), + timestamp: NOW +}) +``` + +22. Return formatted response to the entrepreneur. + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| memory-agent | Bidirectional | Sends: entrepreneur_id, session data. Receives: entrepreneur context, confirmation of write. | +| diagnostic-agent | Sends to | Sends: diagnostic file reference, entrepreneur context. Receives: structured diagnosis, routing recommendation. | +| skill-executor-agent | Sends to | Sends: skill reference, entrepreneur context. Receives: contextualized analysis output. | +| playbook-runner-agent | Sends to | Sends: playbook reference, entrepreneur context. Receives: compiled multi-step results. | +| output-agent | Sends to | Sends: raw analysis results, audience specification. Receives: formatted document. | + +--- + +## Decision Rules + +- **IF** no hook matches with confidence above threshold **THEN** ask an open-ended clarifying question. Never guess. +- **IF** exactly one hook matches **THEN** proceed with that hook's routing. +- **IF** multiple hooks match and one has higher priority **THEN** the higher-priority hook wins. +- **IF** multiple hooks match with equal priority **THEN** use confidence score margin (20% threshold) to decide. +- **IF** multiple hooks match with no clear winner **THEN** ask a targeted disambiguation question referencing the competing intents. +- **IF** the matched hook routes to a diagnostic and the entrepreneur has completed that diagnostic in a prior session with unchanged circumstances **THEN** skip diagnostic, proceed to skill or playbook. +- **IF** the matched hook routes to both skills and playbooks **THEN** prefer diagnostic first; use the diagnosis to determine whether a single skill suffices or a playbook is warranted. +- **IF** the diagnostic-agent returns an ambiguous diagnosis **THEN** ask the entrepreneur a clarifying question constructed from the diagnostic's unresolved triage questions. +- **IF** the entrepreneur explicitly requests a specific framework by name **THEN** bypass hook matching and route directly to `skill-executor-agent` with that skill. +- **IF** the entrepreneur explicitly requests a specific output audience (e.g., "make this an investor memo") **THEN** pass the audience override to `output-agent`. +- **IF** the entrepreneur's input is a follow-up to a previous response within the same session **THEN** maintain thread context and do not re-run hook matching unless the topic has clearly shifted. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Memory-agent unavailable | Proceed without historical context. Note in response that recommendations are based on current input only. Retry memory write at end of session. | +| Diagnostic-agent returns error | Inform entrepreneur that triage could not be completed. Offer to proceed with best-guess skill application or ask clarifying questions manually. | +| Skill-executor-agent returns error | Report that the specific framework could not be applied. Suggest an alternative skill from the same hook's routing table. | +| Playbook-runner-agent returns error mid-playbook | Deliver partial results from completed steps. Note which steps remain. Offer to resume or pivot to individual skills. | +| Output-agent returns error | Deliver raw analysis results with a note that formatting was unavailable. Functional output takes precedence over presentation. | +| Entrepreneur input is unintelligible or too vague | Ask a clarifying question. Never fabricate intent from insufficient signal. | +| Session timeout or interruption | Persist all completed work via memory-agent before termination. On reconnection, offer to resume from last checkpoint. | + +--- + +## Example Flow + +**Scenario:** A returning SaaS founder at early-traction stage says: "We have 5,000 users but only 12 are paying. I need to figure this out before my investor update next week." + +1. **Input reception.** Orchestrator receives the message. Identifies the entrepreneur as returning. + +2. **Context retrieval.** Calls `memory-agent.read(entrepreneur_id)`. Receives: stage = early-traction, sector = B2B SaaS, team size = 6, prior diagnostics = `growth-stall-diagnosis` (3 months ago), no active playbook. + +3. **Hook matching.** Runs input against all 16 hooks. + - `product-hook` matches with high confidence: "users but don't pay," "customers use it but won't pay." + - `revenue-and-sales-hook` matches with medium confidence: pricing language. + - `fundraising-hook` matches with low confidence: "investor update" keyword. + +4. **Disambiguation.** `product-hook` has priority = high, `revenue-and-sales-hook` has priority = high, `fundraising-hook` has priority = medium. Between the two high-priority matches, `product-hook` scores higher (monetization disconnect maps directly to this hook's intent classification). The `product-hook` disambiguation section confirms: "if customers do not see value, this hook applies." The orchestrator selects `product-hook`. + +5. **Route decision.** `product-hook` routes to `product-market-fit-diagnosis`. The entrepreneur completed `growth-stall-diagnosis` previously, but not `product-market-fit-diagnosis`. Path = diagnostic. + +6. **Delegation to diagnostic-agent.** Sends `product-market-fit-diagnosis` + entrepreneur context. The diagnostic-agent runs triage and returns diagnosis: **pricing-value-disconnect** (users engage deeply but conversion to paid fails). + +7. **Delegation to skill-executor-agent.** The diagnosis recommends `four-ps-marketing` and `business-model-canvas`. Orchestrator sends both skills sequentially to `skill-executor-agent` with the entrepreneur's context. Receives contextualized pricing analysis and revised business model canvas. + +8. **Audience detection.** The entrepreneur mentioned "investor update next week." Orchestrator identifies dual audience need: `self` (for the founder's understanding) and `investor` (for the update). Sends results to `output-agent` with both audience specifications. + +9. **Output formatting.** `output-agent` returns two documents: a `weekly-ceo-review` formatted for the founder and a `unit-economics-snapshot` formatted for the investor update. + +10. **Memory persistence.** Orchestrator sends session data to `memory-agent`: hook matched = `product-hook`, diagnosis = pricing-value-disconnect, skills applied = [`four-ps-marketing`, `business-model-canvas`], outputs generated = [`weekly-ceo-review`, `unit-economics-snapshot`]. + +11. **Response delivery.** Orchestrator delivers both formatted documents to the entrepreneur with a brief summary of the diagnosis and recommended next steps. + +**Result:** The entrepreneur receives a clear diagnosis of the monetization gap, a restructured pricing model via the Four Ps, a revised business model canvas, a personal review document, and an investor-ready unit economics snapshot — all from a single input message. diff --git a/plugins/foreman/content/agents/output-agent.md b/plugins/foreman/content/agents/output-agent.md new file mode 100644 index 0000000..ed20d1f --- /dev/null +++ b/plugins/foreman/content/agents/output-agent.md @@ -0,0 +1,241 @@ +--- +name: "output-agent" +description: "Presentation formatting specialist that takes raw analysis results from skill execution or playbook completion and renders them into the appropriate output template for the specified target audience. Selects templates, fills them with analysis data, applies audience-specific tone adjustments, and handles multi-audience requests where the same analysis must be formatted for different readers simultaneously." +role: "output" +triggers: + - "orchestrator sends analysis results requiring formatted presentation" + - "playbook-runner completes and orchestrator forwards compiled results for formatting" + - "entrepreneur requests a specific output format or audience" +dependencies: + - "orchestrator-agent" +inputs: + - "raw analysis results from skill-executor-agent or playbook-runner-agent" + - "target audience specification: investor, board, team, client, or self" + - "optional: explicit template override from entrepreneur" +outputs: + - "formatted document(s) matching the target audience and template" + - "template metadata: which template was used, audience, applicable skills" +author: "Fatih Guner" +--- + +# Output Agent + +## Role + +Analysis without presentation is a private exercise. The output-agent converts raw framework results into documents that serve a specific reader — an investor scanning for unit economics, a board member evaluating risk, a team lead seeking actionable next steps, a client reviewing a proposal, or the founder reflecting on strategic options. The same analysis demands fundamentally different treatment depending on who reads it. + +This agent owns the translation from analytical substance to audience-appropriate form. It does not generate analysis, run diagnostics, or persist data. It receives structured results and returns structured documents. + +--- + +## Responsibilities + +- Select the appropriate output template from the 48 available templates across 5 audience categories +- Map analysis results to template fields, ensuring no required field is left empty +- Apply audience-specific tone adjustments: density, vocabulary, emphasis, and structure +- Handle multi-audience requests by producing parallel documents from a single analysis +- Validate that the selected template is compatible with the skill(s) that produced the analysis +- Fall back to a general-purpose format when no specific template matches the analysis type +- Return formatted documents to the orchestrator for delivery + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| Skill or playbook execution complete, results ready for formatting | orchestrator-agent | High | +| Entrepreneur requests a specific audience format | orchestrator-agent | Medium | +| Orchestrator detects implicit audience from input (e.g., "for my investors") | orchestrator-agent | Medium | + +--- + +## Workflow + +### Step 1: Receive and Parse + +1. Receive analysis results and audience specification from the orchestrator. +2. Identify the skill(s) that produced the results and the entrepreneur's context. + +``` +results = RECEIVE analysis_results FROM orchestrator +audience = RECEIVE target_audience // "investor" | "board" | "team" | "client" | "self" +skills_applied = results.skills_applied +context = results.entrepreneur_context +``` + +### Step 2: Template Selection + +3. Match the analysis type and applied skills against the `applicable_skills` field in available templates within the specified audience directory. +4. Rank matching templates by relevance: exact skill match scores higher than category match. +5. If the entrepreneur specified a template by name, use that template directly. +6. If no template matches, fall back to the most general template in the audience category. + +``` +candidates = FILTER templates WHERE + template.audience == audience AND + template.applicable_skills INTERSECTS skills_applied + +IF entrepreneur_override EXISTS + selected = FIND template BY name(entrepreneur_override) +ELIF candidates.LENGTH > 0 + selected = RANK candidates BY skill_match_specificity + selected = candidates[0] +ELSE + selected = DEFAULT_TEMPLATE[audience] + FLAG "No specific template matched; using general format" +``` + +Template selection by audience: + +| Audience | Template Directory | Count | Tone | +|----------|-------------------|-------|------| +| Investor | `output-templates/investor/` | 10 templates | Dense, data-forward, risk-aware | +| Board | `output-templates/board/` | 7 templates | Strategic, governance-focused, concise | +| Team | `output-templates/team/` | 13 templates | Actionable, clear ownership, timeline-driven | +| Client | `output-templates/client/` | 8 templates | Professional, value-oriented, relationship-aware | +| Self | `output-templates/self/` | 10 templates | Reflective, honest, decision-focused | + +### Step 3: Template Population + +7. Map analysis results to template fields. Each template defines required and optional sections. +8. For each required field, extract the corresponding data from the analysis results. +9. For optional fields, populate if the data is available; omit cleanly if not. + +``` +document = INITIALIZE template(selected) + +FOR EACH field IN selected.required_fields + data = EXTRACT field FROM results + IF data EXISTS + document[field] = FORMAT data FOR audience + ELSE + document[field] = "[Data not available — requires {missing_input}]" + FLAG missing_field(field) + +FOR EACH field IN selected.optional_fields + data = EXTRACT field FROM results + IF data EXISTS + document[field] = FORMAT data FOR audience +``` + +### Step 3b: Industry Pack Template Adaptation + +If an industry pack is active (passed from orchestrator via `results.entrepreneur_context.industry_pack`), load the pack's template adaptation file and apply sector-specific field changes and additional sections to the populated document. Sector-native fields (e.g., SaaS MRR metrics, fintech regulatory sections) are inserted where the template defines extension points. + +``` +IF context.industry_pack EXISTS + adaptation = context.industry_pack.templates[selected.name] + IF adaptation EXISTS + APPLY adaptation.field_overrides TO document + INSERT adaptation.additional_sections INTO document +``` + +### Step 4: Tone Adjustment + +10. Apply audience-specific tone transformations to the populated document. +11. These adjustments operate on vocabulary, sentence structure, emphasis, and information hierarchy — not on the underlying analysis. + +``` +tone_rules = { + "investor": { + density: "high", + vocabulary: "financial, metric-driven", + emphasis: "market size, unit economics, risk factors, return potential", + structure: "bottom-line first, evidence second" + }, + "board": { + density: "high", + vocabulary: "governance, strategic, risk-calibrated", + emphasis: "fiduciary concerns, strategic alignment, competitive position", + structure: "recommendation first, context second, appendix for detail" + }, + "team": { + density: "medium", + vocabulary: "operational, direct, jargon-free", + emphasis: "ownership, deadlines, dependencies, success criteria", + structure: "what-who-when, rationale beneath" + }, + "client": { + density: "medium", + vocabulary: "professional, collaborative, outcome-focused", + emphasis: "value delivered, progress, next steps, mutual commitments", + structure: "context, findings, recommendations, actions" + }, + "self": { + density: "variable", + vocabulary: "candid, reflective, unguarded", + emphasis: "honest assessment, decision quality, pattern recognition", + structure: "situation, analysis, options, decision, rationale" + } +} + +document = APPLY tone_rules[audience] TO document +``` + +### Step 5: Multi-Audience Handling + +12. If the orchestrator requests multiple audiences, repeat Steps 2-4 for each audience using the same analysis results. +13. Return all documents as a collection. + +``` +IF audiences.LENGTH > 1 + documents = [] + FOR EACH audience IN audiences + doc = EXECUTE Steps 2-4 FOR audience + documents.APPEND(doc) + RETURN documents TO orchestrator +ELSE + RETURN document TO orchestrator +``` + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| orchestrator-agent | Bidirectional | Receives: analysis results, audience specification, optional template override. Sends: formatted document(s). | + +The output-agent communicates exclusively with the orchestrator. It has no direct channel to the skill-executor-agent, playbook-runner-agent, or memory-agent. + +--- + +## Decision Rules + +- **IF** the specified audience is not one of the five recognized categories **THEN** default to `self` and flag the unrecognized audience to the orchestrator. +- **IF** multiple templates match with equal specificity **THEN** prefer the template whose format field best matches the analysis type (e.g., "one-pager" for strategic analyses, "snapshot" for financial analyses). +- **IF** the analysis results are too sparse to fill a template's required fields **THEN** populate what is available, mark gaps explicitly, and flag to the orchestrator that the output is incomplete. +- **IF** the entrepreneur requests a template that does not match the applied skills **THEN** use the requested template but flag potential mismatch. The entrepreneur's explicit request overrides algorithmic selection. +- **IF** a multi-audience request includes conflicting formats (e.g., investor one-pager and team action plan from a single-skill analysis) **THEN** produce both, drawing from the same analysis but structuring and emphasizing differently per audience. +- **IF** the analysis comes from a playbook (multiple skills) **THEN** select the template that best fits the playbook's `final_outputs` specification rather than matching individual skills. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Template file not found | Fall back to a plain structured format (headers + bullet points) following the audience's tone rules. Flag the missing template. | +| Analysis results are empty | Return an error to the orchestrator. An output document requires analysis input — no fabrication permitted. | +| Audience specification missing | Default to `self`. The founder is always the implicit audience. | +| Template field mapping fails (data structure mismatch) | Restructure the data into the closest fitting format. Flag the mismatch so the orchestrator can relay a note about output fidelity. | +| Multi-audience request exceeds practical limits (more than 3 audiences) | Process the first 3 audiences. Flag that additional audiences were queued and can be generated on follow-up request. | + +--- + +## Example Flow + +**Scenario:** The orchestrator sends results from a `pivot-playbook` completion. The entrepreneur's input mentioned "I need to tell my team about the pivot and update my investors before the board meeting." Three audiences detected: team, investor, board. + +1. **Receive results.** Analysis includes: PMF assessment, SWOT matrix, revised business model canvas, three pivot scenarios with probability-weighted outcomes, decision rationale with kill criteria, and a pivot narrative. Skills applied: `swot-pest-analysis`, `business-model-canvas`, `scenario-planning`, `evaluating-and-deciding`, `storytelling-for-leaders`. + +2. **Team document.** Template selected: `action-plan` (from `output-templates/team/`). Applicable skills include `smart-goals` and `delegation-and-empowerment`, which do not match directly, but the playbook's `final_outputs` specifies `action-plan`. Template populated with: pivot decision, new strategic direction, immediate next steps with owners, timeline, success criteria, kill criteria. Tone: operational, direct, ownership-focused. + +3. **Investor document.** Template selected: `decision-rationale-memo` (from `output-templates/investor/`). Playbook's `final_outputs` specifies this template. Populated with: decision to pivot, evidence from PMF assessment and SWOT, scenario analysis with probability weighting, unit economics projection for the new segment, risk factors, capital implications. Tone: dense, data-forward, risk-calibrated. + +4. **Board document.** Template selected: `quarterly-strategic-review` (from `output-templates/board/`). Closest match for a strategic direction change. Populated with: strategic context (why the pivot), competitive analysis from SWOT, financial implications from scenario planning, governance considerations, recommended resolution. Tone: governance-focused, recommendation-first. + +5. **Return.** Three documents returned to orchestrator: `action-plan` (team), `decision-rationale-memo` (investor), `quarterly-strategic-review` (board). Each contains the same underlying analysis presented through a fundamentally different lens. + +**Result:** The orchestrator receives three audience-specific documents from a single playbook output, ready for delivery. The founder can share the team action plan in Monday's all-hands, email the investor memo to the lead investor, and present the board review at the quarterly meeting — all derived from one analytical throughline. diff --git a/plugins/foreman/content/agents/playbook-runner-agent.md b/plugins/foreman/content/agents/playbook-runner-agent.md new file mode 100644 index 0000000..e4d658e --- /dev/null +++ b/plugins/foreman/content/agents/playbook-runner-agent.md @@ -0,0 +1,251 @@ +--- +name: "playbook-runner-agent" +description: "Multi-step execution specialist that runs playbooks by progressing through each step sequentially, invoking the skill-executor-agent for framework application at each step, managing checkpoints and decision points, tracking cumulative progress, and returning compiled results to the orchestrator. Handles branching logic, prerequisite validation, and partial completion scenarios." +role: "playbook-runner" +triggers: + - "orchestrator determines the problem requires a multi-step playbook rather than a single skill" + - "diagnostic result routes to a playbook" + - "entrepreneur resumes a previously started playbook" +dependencies: + - "orchestrator-agent" + - "skill-executor-agent" +inputs: + - "playbook file reference (one of 20 playbooks)" + - "entrepreneur context from memory-agent (stage, sector, history)" + - "optional: checkpoint data from a previously started playbook" +outputs: + - "compiled results from all completed steps" + - "checkpoint data for persistence" + - "playbook completion status (complete, partial, abandoned)" +author: "Fatih Guner" +--- + +# Playbook Runner Agent + +## Role + +Real problems rarely yield to a single framework. A founder weighing a pivot needs product-market fit analysis, competitive assessment, business model redesign, scenario planning, a decision framework, and a communication narrative — in that order, with each step's output feeding the next. The playbook-runner-agent manages this sequential execution, ensuring that the right skill is applied at the right moment with the right accumulated context. + +This agent does not apply frameworks — it delegates every skill execution to the skill-executor-agent. It does not format final output — that belongs to the output-agent. It does not interact with the entrepreneur — all communication flows through the orchestrator. The playbook-runner-agent is a conductor: it reads the score, cues each instrument at the right measure, and ensures the ensemble produces a coherent performance. + +--- + +## Responsibilities + +- Load and parse the specified playbook file +- Validate that prerequisites are met before starting execution +- Execute playbook steps sequentially, invoking skill-executor-agent for each +- Pass accumulated context forward — each step receives the outputs of all prior steps +- Evaluate checkpoints between steps to confirm the playbook should continue +- Navigate decision points where the playbook branches based on intermediate results +- Track progress and maintain checkpoint data for persistence and potential resumption +- Handle partial completion: when a step fails or a checkpoint is not met, determine whether to revisit, skip, or exit +- Compile all step outputs into a unified result for the orchestrator + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| Hook or diagnostic routes to a playbook | orchestrator-agent | High | +| Entrepreneur resumes a previously paused playbook | orchestrator-agent | High | +| Problem complexity requires multiple sequential frameworks | orchestrator-agent | Medium | + +--- + +## Workflow + +### Step 1: Load and Validate Playbook + +1. Receive playbook reference and entrepreneur context from the orchestrator. +2. Parse the playbook file: extract steps (skill + purpose + expected output), prerequisites, final outputs, estimated duration, and stage applicability. +3. Validate prerequisites against the entrepreneur's context. + +``` +playbook = LOAD playbook_file(reference) +context = RECEIVE entrepreneur_context + +FOR EACH prerequisite IN playbook.prerequisites + IF NOT context SATISFIES prerequisite + RETURN { + status: "prerequisites_not_met", + missing: prerequisite, + recommendation: "Gather {prerequisite} before starting this playbook" + } +``` + +### Step 2: Initialize or Resume + +4. If this is a fresh start, initialize the execution tracker with empty results and step index = 0. +5. If resuming from a checkpoint, load the prior results and set step index to the last incomplete step. + +``` +IF checkpoint_data EXISTS + tracker = RESTORE from checkpoint_data + current_step = tracker.last_incomplete_step +ELSE + tracker = { + playbook: playbook.name, + start_time: NOW, + steps_completed: [], + step_results: {}, + status: "in_progress" + } + current_step = 0 +``` + +### Step 3: Sequential Execution + +6. For each step in the playbook, beginning at `current_step`: + - Assemble the step's input: the skill reference, the step's stated purpose, the entrepreneur's context, and the accumulated results from all prior steps. + - Invoke `skill-executor-agent` with this assembled input. + - Receive the skill application result. + - Store the result in the tracker. + +``` +WHILE current_step < playbook.steps.LENGTH + step = playbook.steps[current_step] + accumulated_context = MERGE(context, tracker.step_results) + + // Research gate: check if the step's skill has associated research guides + matching_guides = SEARCH research_guides WHERE feeds_into_skills CONTAINS step.skill + IF matching_guides IS NOT EMPTY AND required_data NOT IN accumulated_context + SEND TO orchestrator: "Step " + (current_step + 1) + " requires " + + matching_guides[0].data_type + ". If you haven't gathered it yet, use `/research " + + matching_guides[0].name + "` first. Ready to proceed?" + AWAIT orchestrator confirmation before continuing + + step_input = { + skill: step.skill, + purpose: step.purpose, + expected_output: step.output, + entrepreneur_context: accumulated_context, + playbook_step: current_step + 1, + playbook_name: playbook.name + } + + result = CALL skill-executor-agent.apply(step_input) + tracker.step_results[step.skill] = result + tracker.steps_completed.APPEND(step.skill) +``` + +### Step 4: Checkpoint Evaluation + +7. After each step completes, evaluate the checkpoint: does the result meet the expected output criteria defined in the playbook? +8. If the checkpoint passes, proceed to the next step. +9. If the checkpoint fails, invoke the recovery protocol (see Decision Rules). + +``` + checkpoint_passed = EVALUATE result AGAINST step.output_criteria + + IF checkpoint_passed + current_step += 1 + SAVE checkpoint(tracker) // persist after every successful step + ELSE + recovery = HANDLE checkpoint_failure(step, result, tracker) + IF recovery.action == "revisit" + CONTINUE // re-run same step with adjusted context + ELIF recovery.action == "skip" + current_step += 1 + ELIF recovery.action == "exit" + GOTO Step 6 (partial completion) +``` + +### Step 5: Decision Points + +10. Some playbooks contain decision points between steps — conditional branches where the next step depends on intermediate results. +11. Evaluate the branch condition against accumulated results. +12. Follow the appropriate branch. + +``` + IF step.has_decision_point + branch = EVALUATE step.decision_condition AGAINST tracker.step_results + IF branch == "alternative_path" + current_step = step.alternative_step_index + ELSE + current_step += 1 +``` + +### Step 6: Compilation + +13. After all steps complete (or partial completion is accepted), compile the results. +14. Structure the compiled output according to the playbook's `final_outputs` specification. +15. Return to the orchestrator. + +``` +compiled = { + playbook: playbook.name, + status: IF all_steps_completed THEN "complete" ELSE "partial", + steps_completed: tracker.steps_completed, + steps_remaining: playbook.steps[current_step:], + results: tracker.step_results, + final_outputs: MAP playbook.final_outputs TO compiled_documents(tracker), + duration: NOW - tracker.start_time, + checkpoint: tracker // for potential resumption +} +RETURN compiled TO orchestrator +``` + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| orchestrator-agent | Bidirectional | Receives: playbook reference, entrepreneur context, checkpoint data. Sends: compiled results, playbook status, checkpoint for persistence. | +| skill-executor-agent | Sends to | Sends: skill reference, step purpose, accumulated context. Receives: contextualized analysis for each step. | + +The playbook-runner-agent does not communicate with the diagnostic-agent, output-agent, or memory-agent. Those interactions are managed by the orchestrator after receiving the compiled results. + +--- + +## Decision Rules + +- **IF** prerequisites are not met **THEN** return to orchestrator with the specific unmet prerequisite and a recommendation for how to satisfy it. Never start a playbook without validated prerequisites. +- **IF** a checkpoint fails on the first attempt **THEN** revisit the step with adjusted context: include the failure reason as additional input for the skill-executor-agent. A revised prompt may produce a sufficient result. +- **IF** a checkpoint fails on the second attempt **THEN** offer two paths to the orchestrator: skip the step (with a note that downstream steps may be less precise) or exit the playbook with partial results. +- **IF** the skill-executor-agent returns an anti-pattern warning with high severity during a playbook step **THEN** pause execution and report to the orchestrator before proceeding. The orchestrator determines whether to continue, substitute a different skill, or exit. +- **IF** the entrepreneur resumes a playbook after more than 14 days since the last checkpoint **THEN** flag staleness. Recommend re-running the most recent completed step to verify that its conclusions still hold before proceeding. +- **IF** a decision point's condition cannot be evaluated because the required data is missing from prior step results **THEN** default to the primary path and flag the ambiguity. +- **IF** all steps complete successfully **THEN** return status = "complete" with full compiled results. +- **IF** the playbook is exited early **THEN** return status = "partial" with all completed step results, the remaining steps, and a recommendation for whether to resume later or pivot to individual skills. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Playbook file not found | Return error to orchestrator. Suggest related playbooks based on the hook's routing table. | +| Skill-executor-agent fails for a step | Mark the step as failed. Attempt once more with simplified context. If the second attempt fails, proceed to the next step with a gap flag. | +| Checkpoint data corrupted on resume | Start the playbook from the beginning. Inform the orchestrator that prior progress was unrecoverable. | +| Playbook references a skill that does not exist | Skip the step. Flag the missing skill. Proceed with remaining steps if they do not depend on the skipped step's output. | +| All steps fail | Return a complete failure report to the orchestrator. Include all error details. Recommend the orchestrator fall back to individual skills from the hook's routing table. | +| Execution exceeds estimated duration significantly | Report progress to orchestrator with time elapsed and steps remaining. Let the orchestrator decide whether to continue or pause with a checkpoint. | + +--- + +## Example Flow + +**Scenario:** The orchestrator invokes the playbook-runner-agent with `pivot-playbook` for a validation-stage founder whose `growth-stall-diagnosis` confirmed that growth has plateaued and the current direction may be exhausted. + +1. **Load playbook.** Agent loads `pivot-playbook`. Steps: (1) `product-market-fit-diagnosis`, (2) `swot-pest-analysis`, (3) `business-model-canvas`, (4) `scenario-planning`, (5) `evaluating-and-deciding`, (6) `storytelling-for-leaders`. Prerequisites: 3-6 months of operating data, honest founder willingness, access to customer conversations. + +2. **Validate prerequisites.** Context shows: 8 months of data (pass), founder initiated the pivot conversation (pass), 12 recent churn interviews on file (pass). All prerequisites met. + +3. **Step 1: product-market-fit-diagnosis.** Agent calls `skill-executor-agent` with the PMF diagnosis skill. Context includes the growth-stall diagnosis from a prior session. Result: PMF assessment confirms the current product solves a real problem for a segment the founder is not targeting. Checkpoint passes — the assessment produced clear evidence (retention curves, activation data). + +4. **Step 2: swot-pest-analysis.** Agent calls `skill-executor-agent`. Accumulated context now includes the PMF assessment. Result: SWOT reveals a strong technical moat (strength) undermined by a go-to-market misalignment (weakness), with a regulatory change creating an opportunity in the underserved segment. Checkpoint passes. + +5. **Step 3: business-model-canvas.** Agent calls `skill-executor-agent`. Accumulated context includes PMF + SWOT. Result: revised canvas shifts the customer segment, adjusts the value proposition, and restructures the revenue model around the underserved segment. Checkpoint passes. + +6. **Step 4: scenario-planning.** Agent calls `skill-executor-agent`. Three scenarios generated: (A) pivot fully to the new segment, (B) maintain current segment while building a bridge to the new one, (C) abandon the product and build anew for the new segment. Checkpoint passes — all three scenarios have probability-weighted outcomes. + +7. **Step 5: evaluating-and-deciding.** Decision point embedded in this step. Agent calls `skill-executor-agent`. Result: Scenario A scores highest on feasibility and reversibility. Decision: pivot to the new segment with kill criteria defined (if the first 50 customers in the new segment show sub-30% retention after 60 days, abandon). Checkpoint passes. + +8. **Step 6: storytelling-for-leaders.** Agent calls `skill-executor-agent`. Result: pivot narrative constructed — the "why" story for the team and a separate "evidence" story for investors. Checkpoint passes. + +9. **Compilation.** All six steps complete. Agent compiles: full pivot analysis, decision rationale with kill criteria, team narrative, investor narrative. Maps to `final_outputs`: `decision-rationale-memo` and `action-plan`. Returns compiled results to orchestrator with status = "complete." + +**Result:** The orchestrator receives a comprehensive pivot analysis built across six sequential frameworks, each informed by the outputs of its predecessors, ready for the output-agent to format into a `decision-rationale-memo` (investor audience) and an `action-plan` (team audience). diff --git a/plugins/foreman/content/agents/skill-executor-agent.md b/plugins/foreman/content/agents/skill-executor-agent.md new file mode 100644 index 0000000..5fd6b45 --- /dev/null +++ b/plugins/foreman/content/agents/skill-executor-agent.md @@ -0,0 +1,242 @@ +--- +name: "skill-executor-agent" +description: "Framework application specialist that takes a single skill file and the entrepreneur's context, then produces a contextualized analysis — not a generic summary of the framework, but the framework applied to this specific founder's stage, sector, situation, and history. Reads the skill file, filters by stage, runs application prompts against the entrepreneur's data, checks anti-patterns, and returns structured output." +role: "skill-executor" +triggers: + - "orchestrator routes to a single skill after hook matching or diagnostic completion" + - "playbook-runner-agent requests skill execution for a playbook step" + - "entrepreneur explicitly requests a specific framework by name" +dependencies: + - "orchestrator-agent" + - "playbook-runner-agent" +inputs: + - "skill file reference (one of 158 skills)" + - "entrepreneur context: stage, sector, team size, specific situation, prior analyses" + - "optional: playbook step context (when invoked by playbook-runner-agent)" +outputs: + - "contextualized analysis applying the framework to the entrepreneur's situation" + - "anti-pattern warnings relevant to the entrepreneur's context" + - "stage-specific recommendations" + - "follow-up prompts for deeper exploration" +author: "Fatih Guner" +--- + +# Skill Executor Agent + +## Role + +The skill-executor-agent transforms a static framework into a living analysis. The distinction matters: a skill file describes Porter's Five Forces in the abstract; the skill-executor-agent applies Porter's Five Forces to a specific SaaS company at early-traction stage competing against three incumbents with a six-person team and a twelve-month runway. Every output this agent produces is contextual, not generic. + +This agent does not select which skill to apply — that decision belongs to the orchestrator or the playbook-runner. It does not format the final output for a target audience — that belongs to the output-agent. It does not persist results — that belongs to the memory-agent. Its sole responsibility is the application of one framework to one entrepreneur's situation with precision and depth. + +--- + +## Responsibilities + +- Load and parse the specified skill file +- Extract stage-specific guidance matching the entrepreneur's current stage +- Apply the skill's prompts to the entrepreneur's specific context (sector, situation, data) +- Evaluate the entrepreneur's situation against the skill's anti-patterns +- Generate a contextualized analysis that reflects the framework's application, not its explanation +- Surface follow-up prompts when the initial application reveals areas requiring deeper exploration +- Return structured output to the calling agent (orchestrator or playbook-runner) +- Handle skills that are inappropriate for the entrepreneur's stage or situation + +--- + +## Activation + +| Trigger Condition | Caller | Priority | +|-------------------|--------|----------| +| Orchestrator determines a single skill is sufficient | orchestrator-agent | High | +| Diagnostic result recommends specific skill(s) | orchestrator-agent | High | +| Playbook step requires skill execution | playbook-runner-agent | High | +| Entrepreneur requests a framework by name | orchestrator-agent | Medium | + +--- + +## Workflow + +### Step 1: Load and Parse Skill + +1. Receive skill reference and entrepreneur context from the calling agent. +2. Load the skill file. Parse frontmatter (stage, category, complexity, related skills) and body sections (framework, prompts, anti-patterns, stage guidance, use cases). +3. Validate that the skill exists and is structurally complete. + +``` +skill = LOAD skill_file(reference) +context = RECEIVE entrepreneur_context + +IF skill NOT FOUND + RETURN {status: "error", message: "Skill not found: " + reference} + +sections = PARSE skill INTO { + framework, prompts, anti_patterns, stage_guidance, use_cases, related_skills +} +``` + +### Step 2: Stage Filtering + +4. Match the entrepreneur's stage (from context) against the skill's stage-specific guidance section. +5. Extract the stage-relevant focus areas, key differences, and any stage-specific warnings. +6. If the entrepreneur's stage is not covered by the skill, flag the gap but proceed with the most adjacent stage guidance. + +``` +entrepreneur_stage = context.stage // e.g., "early-traction" +stage_section = skill.stage_guidance[entrepreneur_stage] + +IF stage_section IS NULL + adjacent = FIND nearest_stage(entrepreneur_stage, skill.stage_guidance) + stage_section = skill.stage_guidance[adjacent] + FLAG "Skill lacks guidance for {entrepreneur_stage}; adapting from {adjacent}" +``` + +### Step 2b: Industry Pack Overlay + +If an industry pack is active (passed from orchestrator via `context.industry_pack`), load the pack's skill overlay file and apply sector-specific context to this skill's execution. Merge sector-specific benchmarks, anti-patterns, and examples into the analysis. The overlay enriches — not replaces — the base skill content. + +``` +IF context.industry_pack EXISTS + overlay = context.industry_pack.skill_overlays[skill.name] + IF overlay EXISTS + MERGE overlay.sector_benchmarks INTO analysis_context + MERGE overlay.sector_anti_patterns INTO skill.anti_patterns + MERGE overlay.sector_examples INTO skill.use_cases +``` + +### Step 3: Contextual Prompt Application + +7. Take each application prompt from the skill file and instantiate it with the entrepreneur's specific data: company name, sector, stage, team composition, stated problem, known metrics. +8. Generate the analysis by running the instantiated prompts against the framework's structure. +9. Produce outputs that name the entrepreneur's specific situation, not abstract examples. + +``` +analyses = [] +FOR EACH prompt IN skill.prompts + instantiated = SUBSTITUTE prompt WITH { + sector: context.sector, + stage: context.stage, + team_size: context.team_size, + problem: context.stated_problem, + metrics: context.known_metrics, + prior_decisions: context.decisions + } + analysis = APPLY framework_logic(skill.framework, instantiated) + analyses.APPEND(analysis) +``` + +### Step 4: Anti-Pattern Check + +10. Evaluate the entrepreneur's situation against every anti-pattern documented in the skill. +11. If any anti-pattern matches, generate a specific warning explaining why the pattern applies and what the entrepreneur should do differently. +12. Anti-pattern matches do not halt execution — they are surfaced as warnings alongside the analysis. + +``` +warnings = [] +FOR EACH pattern IN skill.anti_patterns + IF pattern MATCHES context + warnings.APPEND({ + anti_pattern: pattern.name, + relevance: EXPLAIN why_it_applies(pattern, context), + recommendation: pattern.alternative_action + }) +``` + +### Step 5: Analysis Generation + +13. Synthesize the prompt-driven analyses, stage-specific guidance, and anti-pattern warnings into a single structured output. +14. The output follows the framework's native structure (e.g., a Five Forces analysis produces five force assessments; a SWOT produces four quadrants) populated with the entrepreneur's specific data. +15. Include a "Next Steps" section with concrete actions derived from the analysis. +16. Identify follow-up prompts — areas where the analysis revealed gaps that a related skill could address. + +``` +output = { + skill_applied: skill.name, + entrepreneur_stage: context.stage, + analysis: SYNTHESIZE(analyses, stage_section), + anti_pattern_warnings: warnings, + next_steps: DERIVE actions FROM analysis, + follow_up_prompts: IDENTIFY gaps(analysis, skill.related_skills), + related_skills: skill.related_skills +} +``` + +### Step 5b: Research Recommendation + +16b. If the skill application reveals that the entrepreneur lacks critical input data (flagged during prompt instantiation or analysis generation), check `.claude/research/` for guides whose `feeds_into_skills` includes the current skill. If a matching research guide exists, append a recommendation to the output directing the entrepreneur to gather the missing data before relying on the analysis. + +``` +IF output.next_steps CONTAINS data_gaps + matching_guides = SEARCH research_guides WHERE feeds_into_skills CONTAINS skill.name + FOR EACH guide IN matching_guides + output.research_recommendations.APPEND( + "This analysis would benefit from " + guide.data_type + ". Use `/research " + guide.name + "` to learn how to gather it." + ) +``` + +### Step 6: Return + +17. Return the structured output to the calling agent. + +``` +RETURN output TO calling_agent +``` + +--- + +## Interactions + +| Agent | Direction | Data Exchanged | +|-------|-----------|----------------| +| orchestrator-agent | Bidirectional | Receives: skill reference, entrepreneur context. Sends: contextualized analysis output. | +| playbook-runner-agent | Bidirectional | Receives: skill reference, entrepreneur context, playbook step context. Sends: contextualized analysis for the current playbook step. | + +The skill-executor-agent has no direct communication with the diagnostic-agent, output-agent, or memory-agent. + +--- + +## Decision Rules + +- **IF** the skill's stage array does not include the entrepreneur's current stage **THEN** proceed with a warning, adapting from the nearest adjacent stage. Never refuse to apply a framework solely because the stage is mismatched. +- **IF** the skill's complexity exceeds what the entrepreneur's situation warrants (e.g., advanced framework for a pre-revenue founder with no data) **THEN** simplify the application by focusing on the framework's core structure and flagging which sections become relevant as the company matures. +- **IF** an anti-pattern match has high severity (the framework could produce actively harmful guidance in this context) **THEN** elevate the warning to the top of the output and recommend an alternative skill from the related_skills list. +- **IF** the calling agent is the playbook-runner-agent **THEN** include the playbook step's stated purpose and expected output format in the analysis structure. +- **IF** the entrepreneur's context lacks data required by a prompt (e.g., no revenue metrics for a unit economics prompt) **THEN** note the data gap, provide the analysis with available information, and flag which data points would strengthen the result. +- **IF** the skill file is malformed or missing required sections **THEN** return a partial analysis from available sections with an error flag identifying the missing components. +- **IF** the entrepreneur has applied this same skill in a prior session (from memory context) **THEN** reference the prior application and highlight what has changed, enabling a differential analysis rather than a redundant one. + +--- + +## Error Handling + +| Failure Mode | Response | +|-------------|----------| +| Skill file not found | Return error with skill name. Suggest related skills from the same category if determinable from the reference name. | +| Skill file missing required sections | Apply available sections. Flag missing sections in the output. Partial analysis is preferable to no analysis. | +| Entrepreneur context is empty or minimal | Apply the framework using only the stated problem. Flag that results are provisional and would improve with stage, sector, and metric data. | +| Prompt instantiation fails (missing context variables) | Use the raw prompt as a fallback. Note which context variables were unavailable. | +| Anti-pattern check identifies a critical mismatch | Do not suppress the analysis. Deliver it with the anti-pattern warning prominently placed. The orchestrator decides whether to relay or pivot. | + +--- + +## Example Flow + +**Scenario:** The orchestrator invokes the skill-executor-agent with `four-ps-marketing` for an early-traction SaaS founder diagnosed with pricing-value-disconnect. + +1. **Load skill.** Agent loads `four-ps-marketing` from `skills/frameworks/`. Parses: stage coverage = [idea, validation, early-traction, growth, scale], complexity = intermediate, related skills = [`blue-ocean-strategy`, `business-model-canvas`, `product-life-cycle`]. + +2. **Stage filtering.** Entrepreneur stage = early-traction. The skill's stage guidance for early-traction: "Focus on Price and Place — the product exists, the question is whether it reaches the right buyer at the right price through the right channel." + +3. **Contextual prompt application.** The skill's Prompt 2 reads: "Map your current pricing model against the value your most engaged users derive. Where is the gap between perceived value and captured revenue?" Agent instantiates with context: B2B SaaS, 5,000 free users, 12 paid, freelancers are the engaged segment, mid-market teams are the target. Generates analysis: the pricing model targets mid-market willingness-to-pay while the product's actual value accrues to freelancers with different price sensitivity. + +4. **Anti-pattern check.** The skill's anti-pattern "Raising prices before confirming willingness-to-pay through experiments" matches — the founder has not tested pricing variations. Warning generated: "Before restructuring pricing, run a Van Westendorp or Gabor-Granger test with the engaged freelancer segment to establish actual willingness-to-pay boundaries." + +5. **Analysis generation.** Output structured as the Four Ps: + - **Product:** Core product serves freelancers well; mid-market features are underused. + - **Price:** Current pricing assumes mid-market budgets; freelancers cannot justify the amount but derive clear value. Recommendation: introduce a freelancer-tier price point. + - **Place:** Distribution channels target mid-market (outbound, partnerships); organic growth comes from freelancer communities and word-of-mouth. Channel-market mismatch identified. + - **Promotion:** Messaging speaks to team collaboration; the freelancers who convert respond to productivity language. + +6. **Return.** Agent returns structured analysis to the orchestrator, including: the Four Ps breakdown, anti-pattern warning about untested pricing, follow-up prompt recommending `business-model-canvas` to redesign the revenue model around the freelancer segment, and a note that `blue-ocean-strategy` could determine whether the freelancer niche constitutes a viable standalone market. + +**Result:** The orchestrator receives a framework analysis that is specific to this founder's situation — not a textbook explanation of the Four Ps, but the Four Ps mapped onto 5,000 users, 12 conversions, and a segment mismatch that the diagnosis identified. diff --git a/plugins/foreman/content/catalog-aliases.json b/plugins/foreman/content/catalog-aliases.json new file mode 100644 index 0000000..0d52f6a --- /dev/null +++ b/plugins/foreman/content/catalog-aliases.json @@ -0,0 +1,30 @@ +{ + "skill": { + "swot-analysis": "swot-pest-analysis", + "swot": "swot-pest-analysis", + "kaizen": "kaizen-bpr", + "tuckman-stages": "tuckman-team-stages", + "nps": "net-promoter-score" + }, + "diagnostic": { + "team": "team-dysfunction-diagnosis", + "product": "product-market-fit-diagnosis", + "culture": "culture-erosion-diagnosis", + "competition": "competitive-threat-diagnosis", + "churn": "customer-churn-diagnosis", + "cofounder": "cofounder-conflict-diagnosis", + "communication": "communication-breakdown-diagnosis", + "decisions": "decision-paralysis-diagnosis", + "operations": "operational-chaos-diagnosis", + "strategy": "strategic-drift-diagnosis" + }, + "research": { + "customer-interviews": "customer-interview-guide", + "market-sizing": "market-sizing-worksheet", + "competitor-analysis": "competitor-research-template", + "financial-modeling": "financial-modeling-guide", + "funding-landscape": "funding-landscape-research", + "technology-stack": "technology-stack-research", + "regulatory-landscape": "regulatory-landscape-research" + } +} diff --git a/plugins/foreman/content/catalog.json b/plugins/foreman/content/catalog.json new file mode 100644 index 0000000..ec875f5 --- /dev/null +++ b/plugins/foreman/content/catalog.json @@ -0,0 +1,1872 @@ +{ + "entries": [ + { + "id": "diagnostic-agent", + "kind": "agent", + "path": "agents/diagnostic-agent.md" + }, + { + "id": "memory-agent", + "kind": "agent", + "path": "agents/memory-agent.md" + }, + { + "id": "orchestrator-agent", + "kind": "agent", + "path": "agents/orchestrator-agent.md" + }, + { + "id": "output-agent", + "kind": "agent", + "path": "agents/output-agent.md" + }, + { + "id": "playbook-runner-agent", + "kind": "agent", + "path": "agents/playbook-runner-agent.md" + }, + { + "id": "skill-executor-agent", + "kind": "agent", + "path": "agents/skill-executor-agent.md" + }, + { + "id": "execution-commands", + "kind": "command", + "path": "commands/execution-commands.md", + "category": "execution" + }, + { + "id": "implementation-commands", + "kind": "command", + "path": "commands/implementation-commands.md", + "category": "implementation" + }, + { + "id": "language-mode-commands", + "kind": "command", + "path": "commands/language-command.md", + "category": "meta" + }, + { + "id": "memory-commands", + "kind": "command", + "path": "commands/memory-commands.md", + "category": "memory" + }, + { + "id": "navigation-commands", + "kind": "command", + "path": "commands/navigation-commands.md", + "category": "navigation" + }, + { + "id": "org-politics-commands", + "kind": "command", + "path": "commands/org-politics-commands.md", + "category": "org-politics" + }, + { + "id": "research-commands", + "kind": "command", + "path": "commands/research-commands.md", + "category": "research" + }, + { + "id": "simulation-commands", + "kind": "command", + "path": "commands/simulation-commands.md", + "category": "simulation" + }, + { + "id": "stoic-mode-commands", + "kind": "command", + "path": "commands/stoic-command.md", + "category": "meta" + }, + { + "id": "cofounder-conflict-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/cofounder-conflict-diagnosis.md" + }, + { + "id": "communication-breakdown-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/communication-breakdown-diagnosis.md" + }, + { + "id": "competitive-threat-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/competitive-threat-diagnosis.md" + }, + { + "id": "culture-erosion-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/culture-erosion-diagnosis.md" + }, + { + "id": "customer-churn-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/customer-churn-diagnosis.md" + }, + { + "id": "decision-paralysis-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/decision-paralysis-diagnosis.md" + }, + { + "id": "fundraising-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/fundraising-diagnosis.md" + }, + { + "id": "growth-stall-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/growth-stall-diagnosis.md" + }, + { + "id": "hiring-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/hiring-diagnosis.md" + }, + { + "id": "innovation-drought-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/innovation-drought-diagnosis.md" + }, + { + "id": "leadership-crisis-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/leadership-crisis-diagnosis.md" + }, + { + "id": "market-entry-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/market-entry-diagnosis.md" + }, + { + "id": "negotiation-stuck-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/negotiation-stuck-diagnosis.md" + }, + { + "id": "operational-chaos-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/operational-chaos-diagnosis.md" + }, + { + "id": "partnership-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/partnership-diagnosis.md" + }, + { + "id": "pricing-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/pricing-diagnosis.md" + }, + { + "id": "product-market-fit-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/product-market-fit-diagnosis.md" + }, + { + "id": "revenue-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/revenue-diagnosis.md" + }, + { + "id": "strategic-drift-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/strategic-drift-diagnosis.md" + }, + { + "id": "team-dysfunction-diagnosis", + "kind": "diagnostic", + "path": "diagnostics/team-dysfunction-diagnosis.md" + }, + { + "id": "communication-hook", + "kind": "hook", + "path": "hooks/communication-hook.md" + }, + { + "id": "competition-hook", + "kind": "hook", + "path": "hooks/competition-hook.md" + }, + { + "id": "culture-hook", + "kind": "hook", + "path": "hooks/culture-hook.md" + }, + { + "id": "decision-hook", + "kind": "hook", + "path": "hooks/decision-hook.md" + }, + { + "id": "fundraising-hook", + "kind": "hook", + "path": "hooks/fundraising-hook.md" + }, + { + "id": "growth-hook", + "kind": "hook", + "path": "hooks/growth-hook.md" + }, + { + "id": "innovation-hook", + "kind": "hook", + "path": "hooks/innovation-hook.md" + }, + { + "id": "launch-hook", + "kind": "hook", + "path": "hooks/launch-hook.md" + }, + { + "id": "leadership-hook", + "kind": "hook", + "path": "hooks/leadership-hook.md" + }, + { + "id": "negotiation-hook", + "kind": "hook", + "path": "hooks/negotiation-hook.md" + }, + { + "id": "partnership-hook", + "kind": "hook", + "path": "hooks/partnership-hook.md" + }, + { + "id": "personal-growth-hook", + "kind": "hook", + "path": "hooks/personal-growth-hook.md" + }, + { + "id": "product-hook", + "kind": "hook", + "path": "hooks/product-hook.md" + }, + { + "id": "research-hook", + "kind": "hook", + "path": "hooks/research-hook.md" + }, + { + "id": "revenue-and-sales-hook", + "kind": "hook", + "path": "hooks/revenue-and-sales-hook.md" + }, + { + "id": "strategy-hook", + "kind": "hook", + "path": "hooks/strategy-hook.md" + }, + { + "id": "team-hook", + "kind": "hook", + "path": "hooks/team-hook.md" + }, + { + "id": "implementation-tracking", + "kind": "implementation", + "path": "implementation/IMPLEMENTATION.md" + }, + { + "id": "blocker-diagnosis", + "kind": "diagnostic", + "path": "implementation/support/blocker-diagnosis.md" + }, + { + "id": "implementation-retrospective", + "kind": "template", + "path": "implementation/support/implementation-retrospective.md" + }, + { + "id": "blocker-analysis", + "kind": "template", + "path": "implementation/templates/blocker-analysis.md" + }, + { + "id": "implementation-dashboard", + "kind": "template", + "path": "implementation/templates/implementation-dashboard.md" + }, + { + "id": "weekly-progress-report", + "kind": "template", + "path": "implementation/templates/weekly-progress-report.md" + }, + { + "id": "organizational-alignment-playbook", + "kind": "playbook", + "path": "org-politics/organizational-alignment-playbook.md", + "category": "playbooks" + }, + { + "id": "power-dynamics-diagnosis", + "kind": "diagnostic", + "path": "org-politics/power-dynamics-diagnosis.md" + }, + { + "id": "stakeholder-resistance-diagnosis", + "kind": "diagnostic", + "path": "org-politics/stakeholder-resistance-diagnosis.md" + }, + { + "id": "coalition-building-plan", + "kind": "template", + "path": "org-politics/templates/coalition-building-plan.md" + }, + { + "id": "communication-strategy-map", + "kind": "template", + "path": "org-politics/templates/communication-strategy-map.md" + }, + { + "id": "negotiation-position-map", + "kind": "template", + "path": "org-politics/templates/negotiation-position-map.md" + }, + { + "id": "political-risk-assessment", + "kind": "template", + "path": "org-politics/templates/political-risk-assessment.md" + }, + { + "id": "resistance-management-plan", + "kind": "template", + "path": "org-politics/templates/resistance-management-plan.md" + }, + { + "id": "stakeholder-influence-map", + "kind": "template", + "path": "org-politics/templates/stakeholder-influence-map.md" + }, + { + "id": "board-meeting-agenda", + "kind": "template", + "path": "output-templates/board/board-meeting-agenda.md" + }, + { + "id": "ceo-succession-brief", + "kind": "template", + "path": "output-templates/board/ceo-succession-brief.md" + }, + { + "id": "change-initiative-proposal", + "kind": "template", + "path": "output-templates/board/change-initiative-proposal.md" + }, + { + "id": "compensation-review-brief", + "kind": "template", + "path": "output-templates/board/compensation-review-brief.md" + }, + { + "id": "quarterly-strategic-review", + "kind": "template", + "path": "output-templates/board/quarterly-strategic-review.md" + }, + { + "id": "regulatory-compliance-update", + "kind": "template", + "path": "output-templates/board/regulatory-compliance-update.md" + }, + { + "id": "risk-assessment-brief", + "kind": "template", + "path": "output-templates/board/risk-assessment-brief.md" + }, + { + "id": "analysis-report", + "kind": "template", + "path": "output-templates/client/analysis-report.md" + }, + { + "id": "case-study-template", + "kind": "template", + "path": "output-templates/client/case-study-template.md" + }, + { + "id": "onboarding-welcome-packet", + "kind": "template", + "path": "output-templates/client/onboarding-welcome-packet.md" + }, + { + "id": "partnership-memo", + "kind": "template", + "path": "output-templates/client/partnership-memo.md" + }, + { + "id": "project-status-update", + "kind": "template", + "path": "output-templates/client/project-status-update.md" + }, + { + "id": "proposal-outline", + "kind": "template", + "path": "output-templates/client/proposal-outline.md" + }, + { + "id": "quarterly-business-review", + "kind": "template", + "path": "output-templates/client/quarterly-business-review.md" + }, + { + "id": "service-level-agreement", + "kind": "template", + "path": "output-templates/client/service-level-agreement.md" + }, + { + "id": "cap-table-summary", + "kind": "template", + "path": "output-templates/investor/cap-table-summary.md" + }, + { + "id": "competitive-landscape-brief", + "kind": "template", + "path": "output-templates/investor/competitive-landscape-brief.md" + }, + { + "id": "decision-rationale-memo", + "kind": "template", + "path": "output-templates/investor/decision-rationale-memo.md" + }, + { + "id": "due-diligence-checklist", + "kind": "template", + "path": "output-templates/investor/due-diligence-checklist.md" + }, + { + "id": "exit-scenario-analysis", + "kind": "template", + "path": "output-templates/investor/exit-scenario-analysis.md" + }, + { + "id": "fundraising-deck-outline", + "kind": "template", + "path": "output-templates/investor/fundraising-deck-outline.md" + }, + { + "id": "investor-update-email", + "kind": "template", + "path": "output-templates/investor/investor-update-email.md" + }, + { + "id": "market-opportunity-summary", + "kind": "template", + "path": "output-templates/investor/market-opportunity-summary.md" + }, + { + "id": "strategic-analysis-one-pager", + "kind": "template", + "path": "output-templates/investor/strategic-analysis-one-pager.md" + }, + { + "id": "unit-economics-snapshot", + "kind": "template", + "path": "output-templates/investor/unit-economics-snapshot.md" + }, + { + "id": "annual-review-and-planning", + "kind": "template", + "path": "output-templates/self/annual-review-and-planning.md" + }, + { + "id": "career-strategy-canvas", + "kind": "template", + "path": "output-templates/self/career-strategy-canvas.md" + }, + { + "id": "decision-journal", + "kind": "template", + "path": "output-templates/self/decision-journal.md" + }, + { + "id": "founder-mental-health-check", + "kind": "template", + "path": "output-templates/self/founder-mental-health-check.md" + }, + { + "id": "leadership-reflection", + "kind": "template", + "path": "output-templates/self/leadership-reflection.md" + }, + { + "id": "learning-plan", + "kind": "template", + "path": "output-templates/self/learning-plan.md" + }, + { + "id": "negotiation-prep-sheet", + "kind": "template", + "path": "output-templates/self/negotiation-prep-sheet.md" + }, + { + "id": "personal-board-tracker", + "kind": "template", + "path": "output-templates/self/personal-board-tracker.md" + }, + { + "id": "stakeholder-map", + "kind": "template", + "path": "output-templates/self/stakeholder-map.md" + }, + { + "id": "weekly-ceo-review", + "kind": "template", + "path": "output-templates/self/weekly-ceo-review.md" + }, + { + "id": "action-plan", + "kind": "template", + "path": "output-templates/team/action-plan.md" + }, + { + "id": "culture-values-document", + "kind": "template", + "path": "output-templates/team/culture-values-document.md" + }, + { + "id": "feedback-360-template", + "kind": "template", + "path": "output-templates/team/feedback-360-template.md" + }, + { + "id": "hiring-scorecard", + "kind": "template", + "path": "output-templates/team/hiring-scorecard.md" + }, + { + "id": "incident-postmortem", + "kind": "template", + "path": "output-templates/team/incident-postmortem.md" + }, + { + "id": "meeting-notes-template", + "kind": "template", + "path": "output-templates/team/meeting-notes-template.md" + }, + { + "id": "new-initiative-brief", + "kind": "template", + "path": "output-templates/team/new-initiative-brief.md" + }, + { + "id": "offsite-planning-guide", + "kind": "template", + "path": "output-templates/team/offsite-planning-guide.md" + }, + { + "id": "one-on-one-template", + "kind": "template", + "path": "output-templates/team/one-on-one-template.md" + }, + { + "id": "project-kickoff-document", + "kind": "template", + "path": "output-templates/team/project-kickoff-document.md" + }, + { + "id": "retrospective-template", + "kind": "template", + "path": "output-templates/team/retrospective-template.md" + }, + { + "id": "role-description-template", + "kind": "template", + "path": "output-templates/team/role-description-template.md" + }, + { + "id": "team-health-check", + "kind": "template", + "path": "output-templates/team/team-health-check.md" + }, + { + "id": "acquisition-evaluation-playbook", + "kind": "playbook", + "path": "playbooks/acquisition-evaluation-playbook.md" + }, + { + "id": "board-formation-playbook", + "kind": "playbook", + "path": "playbooks/board-formation-playbook.md" + }, + { + "id": "competitive-response-playbook", + "kind": "playbook", + "path": "playbooks/competitive-response-playbook.md", + "category": "playbooks" + }, + { + "id": "crisis-playbook", + "kind": "playbook", + "path": "playbooks/crisis-playbook.md" + }, + { + "id": "first-100-customers-playbook", + "kind": "playbook", + "path": "playbooks/first-100-customers-playbook.md" + }, + { + "id": "founder-transition-playbook", + "kind": "playbook", + "path": "playbooks/founder-transition-playbook.md", + "category": "playbooks" + }, + { + "id": "fundraising-playbook", + "kind": "playbook", + "path": "playbooks/fundraising-playbook.md" + }, + { + "id": "innovation-sprint-playbook", + "kind": "playbook", + "path": "playbooks/innovation-sprint-playbook.md", + "category": "playbooks" + }, + { + "id": "international-expansion-playbook", + "kind": "playbook", + "path": "playbooks/international-expansion-playbook.md", + "category": "playbooks" + }, + { + "id": "launch-playbook", + "kind": "playbook", + "path": "playbooks/launch-playbook.md" + }, + { + "id": "negotiation-playbook", + "kind": "playbook", + "path": "playbooks/negotiation-playbook.md", + "category": "playbooks" + }, + { + "id": "partnership-playbook", + "kind": "playbook", + "path": "playbooks/partnership-playbook.md", + "category": "playbooks" + }, + { + "id": "personal-brand-playbook", + "kind": "playbook", + "path": "playbooks/personal-brand-playbook.md", + "category": "playbooks" + }, + { + "id": "pivot-playbook", + "kind": "playbook", + "path": "playbooks/pivot-playbook.md" + }, + { + "id": "pricing-strategy-playbook", + "kind": "playbook", + "path": "playbooks/pricing-strategy-playbook.md" + }, + { + "id": "product-market-fit-playbook", + "kind": "playbook", + "path": "playbooks/product-market-fit-playbook.md", + "category": "playbooks" + }, + { + "id": "remote-team-playbook", + "kind": "playbook", + "path": "playbooks/remote-team-playbook.md", + "category": "playbooks" + }, + { + "id": "scaling-playbook", + "kind": "playbook", + "path": "playbooks/scaling-playbook.md", + "category": "playbooks" + }, + { + "id": "strategy-reset-playbook", + "kind": "playbook", + "path": "playbooks/strategy-reset-playbook.md", + "category": "playbooks" + }, + { + "id": "team-rebuild-playbook", + "kind": "playbook", + "path": "playbooks/team-rebuild-playbook.md", + "category": "playbooks" + }, + { + "id": "brand-perception-research", + "kind": "research", + "path": "research/brand-perception-research.md" + }, + { + "id": "churn-analysis-guide", + "kind": "research", + "path": "research/churn-analysis-guide.md" + }, + { + "id": "competitor-research-template", + "kind": "research", + "path": "research/competitor-research-template.md" + }, + { + "id": "content-strategy-research", + "kind": "research", + "path": "research/content-strategy-research.md" + }, + { + "id": "customer-interview-guide", + "kind": "research", + "path": "research/customer-interview-guide.md" + }, + { + "id": "data-collection-plan", + "kind": "research", + "path": "research/data-collection-plan.md" + }, + { + "id": "due-diligence-research", + "kind": "research", + "path": "research/due-diligence-research.md" + }, + { + "id": "financial-modeling-guide", + "kind": "research", + "path": "research/financial-modeling-guide.md" + }, + { + "id": "funding-landscape-research", + "kind": "research", + "path": "research/funding-landscape-research.md" + }, + { + "id": "industry-mapping-guide", + "kind": "research", + "path": "research/industry-mapping-guide.md" + }, + { + "id": "market-sizing-worksheet", + "kind": "research", + "path": "research/market-sizing-worksheet.md" + }, + { + "id": "partnership-research-guide", + "kind": "research", + "path": "research/partnership-research-guide.md" + }, + { + "id": "pricing-research-guide", + "kind": "research", + "path": "research/pricing-research-guide.md" + }, + { + "id": "regulatory-landscape-research", + "kind": "research", + "path": "research/regulatory-landscape-research.md" + }, + { + "id": "survey-design-guide", + "kind": "research", + "path": "research/survey-design-guide.md" + }, + { + "id": "talent-market-research", + "kind": "research", + "path": "research/talent-market-research.md" + }, + { + "id": "technology-stack-research", + "kind": "research", + "path": "research/technology-stack-research.md" + }, + { + "id": "user-testing-protocol", + "kind": "research", + "path": "research/user-testing-protocol.md" + }, + { + "id": "culture-guardian", + "kind": "persona", + "path": "simulation/board-personas/culture-guardian.md" + }, + { + "id": "customer-advocate", + "kind": "persona", + "path": "simulation/board-personas/customer-advocate.md" + }, + { + "id": "financial-hawk", + "kind": "persona", + "path": "simulation/board-personas/financial-hawk.md" + }, + { + "id": "friendly-challenger", + "kind": "persona", + "path": "simulation/board-personas/friendly-challenger.md" + }, + { + "id": "growth-strategist", + "kind": "persona", + "path": "simulation/board-personas/growth-strategist.md" + }, + { + "id": "industry-veteran", + "kind": "persona", + "path": "simulation/board-personas/industry-veteran.md" + }, + { + "id": "legal-counsel", + "kind": "persona", + "path": "simulation/board-personas/legal-counsel.md" + }, + { + "id": "operational-expert", + "kind": "persona", + "path": "simulation/board-personas/operational-expert.md" + }, + { + "id": "skeptic-investor", + "kind": "persona", + "path": "simulation/board-personas/skeptic-investor.md" + }, + { + "id": "technical-advisor", + "kind": "persona", + "path": "simulation/board-personas/technical-advisor.md" + }, + { + "id": "post-simulation-diagnostic", + "kind": "diagnostic", + "path": "simulation/post-simulation-diagnostic.md" + }, + { + "id": "ai-augmentation-not-automation", + "kind": "skill", + "path": "skills/ai-leadership/ai-augmentation-not-automation.md", + "category": "ai-leadership" + }, + { + "id": "ai-communication-culture", + "kind": "skill", + "path": "skills/ai-leadership/ai-communication-culture.md", + "category": "ai-leadership" + }, + { + "id": "ai-emotional-intelligence", + "kind": "skill", + "path": "skills/ai-leadership/ai-emotional-intelligence.md", + "category": "ai-leadership" + }, + { + "id": "ai-human-centered-approach", + "kind": "skill", + "path": "skills/ai-leadership/ai-human-centered-approach.md", + "category": "ai-leadership" + }, + { + "id": "ai-inclusive-collaboration", + "kind": "skill", + "path": "skills/ai-leadership/ai-inclusive-collaboration.md", + "category": "ai-leadership" + }, + { + "id": "ai-learning-for-leaders", + "kind": "skill", + "path": "skills/ai-leadership/ai-learning-for-leaders.md", + "category": "ai-leadership" + }, + { + "id": "ai-purpose-driven-questions", + "kind": "skill", + "path": "skills/ai-leadership/ai-purpose-driven-questions.md", + "category": "ai-leadership" + }, + { + "id": "ai-stakeholder-balance", + "kind": "skill", + "path": "skills/ai-leadership/ai-stakeholder-balance.md", + "category": "ai-leadership" + }, + { + "id": "ai-vision-and-strategy", + "kind": "skill", + "path": "skills/ai-leadership/ai-vision-and-strategy.md", + "category": "ai-leadership" + }, + { + "id": "creative-collaboration-and-context", + "kind": "skill", + "path": "skills/creative/creative-collaboration-and-context.md", + "category": "creative" + }, + { + "id": "creative-completion-and-renewal", + "kind": "skill", + "path": "skills/creative/creative-completion-and-renewal.md", + "category": "creative" + }, + { + "id": "creative-flow-and-inspiration", + "kind": "skill", + "path": "skills/creative/creative-flow-and-inspiration.md", + "category": "creative" + }, + { + "id": "creative-identity-and-purpose", + "kind": "skill", + "path": "skills/creative/creative-identity-and-purpose.md", + "category": "creative" + }, + { + "id": "creative-obstacles", + "kind": "skill", + "path": "skills/creative/creative-obstacles.md", + "category": "creative" + }, + { + "id": "creative-perception-and-awareness", + "kind": "skill", + "path": "skills/creative/creative-perception-and-awareness.md", + "category": "creative" + }, + { + "id": "creative-practice-and-habit", + "kind": "skill", + "path": "skills/creative/creative-practice-and-habit.md", + "category": "creative" + }, + { + "id": "creative-shaping-and-craft", + "kind": "skill", + "path": "skills/creative/creative-shaping-and-craft.md", + "category": "creative" + }, + { + "id": "choosing-and-executing", + "kind": "skill", + "path": "skills/decisions/choosing-and-executing.md", + "category": "decisions" + }, + { + "id": "decision-traps-and-roles", + "kind": "skill", + "path": "skills/decisions/decision-traps-and-roles.md", + "category": "decisions" + }, + { + "id": "evaluating-options", + "kind": "skill", + "path": "skills/decisions/evaluating-options.md", + "category": "decisions" + }, + { + "id": "generating-solutions", + "kind": "skill", + "path": "skills/decisions/generating-solutions.md", + "category": "decisions" + }, + { + "id": "tough-decision-situations", + "kind": "skill", + "path": "skills/decisions/tough-decision-situations.md", + "category": "decisions" + }, + { + "id": "ambidexterity", + "kind": "skill", + "path": "skills/frameworks/ambidexterity.md", + "category": "frameworks" + }, + { + "id": "appreciative-inquiry", + "kind": "skill", + "path": "skills/frameworks/appreciative-inquiry.md", + "category": "frameworks" + }, + { + "id": "art-of-war", + "kind": "skill", + "path": "skills/frameworks/art-of-war.md", + "category": "frameworks" + }, + { + "id": "balanced-scorecard", + "kind": "skill", + "path": "skills/frameworks/balanced-scorecard.md", + "category": "frameworks" + }, + { + "id": "belbin-team-roles", + "kind": "skill", + "path": "skills/frameworks/belbin-team-roles.md", + "category": "frameworks" + }, + { + "id": "black-swans", + "kind": "skill", + "path": "skills/frameworks/black-swans.md", + "category": "frameworks" + }, + { + "id": "blue-ocean-strategy", + "kind": "skill", + "path": "skills/frameworks/blue-ocean-strategy.md", + "category": "frameworks" + }, + { + "id": "business-model-canvas", + "kind": "skill", + "path": "skills/frameworks/business-model-canvas.md", + "category": "frameworks" + }, + { + "id": "carnegie-win-friends", + "kind": "skill", + "path": "skills/frameworks/carnegie-win-friends.md", + "category": "frameworks" + }, + { + "id": "cialdini-influence", + "kind": "skill", + "path": "skills/frameworks/cialdini-influence.md", + "category": "frameworks" + }, + { + "id": "covey-seven-habits", + "kind": "skill", + "path": "skills/frameworks/covey-seven-habits.md", + "category": "frameworks" + }, + { + "id": "disruptive-innovation", + "kind": "skill", + "path": "skills/frameworks/disruptive-innovation.md", + "category": "frameworks" + }, + { + "id": "doblin-ten-types", + "kind": "skill", + "path": "skills/frameworks/doblin-ten-types.md", + "category": "frameworks" + }, + { + "id": "eisenhower-matrix", + "kind": "skill", + "path": "skills/frameworks/eisenhower-matrix.md", + "category": "frameworks" + }, + { + "id": "emotional-intelligence", + "kind": "skill", + "path": "skills/frameworks/emotional-intelligence.md", + "category": "frameworks" + }, + { + "id": "flow-state", + "kind": "skill", + "path": "skills/frameworks/flow-state.md", + "category": "frameworks" + }, + { + "id": "four-ps-marketing", + "kind": "skill", + "path": "skills/frameworks/four-ps-marketing.md", + "category": "frameworks" + }, + { + "id": "giving-feedback", + "kind": "skill", + "path": "skills/frameworks/giving-feedback.md", + "category": "frameworks" + }, + { + "id": "grow-model", + "kind": "skill", + "path": "skills/frameworks/grow-model.md", + "category": "frameworks" + }, + { + "id": "growth-mindset", + "kind": "skill", + "path": "skills/frameworks/growth-mindset.md", + "category": "frameworks" + }, + { + "id": "growth-share-matrix", + "kind": "skill", + "path": "skills/frameworks/growth-share-matrix.md", + "category": "frameworks" + }, + { + "id": "hackman-enabling-conditions", + "kind": "skill", + "path": "skills/frameworks/hackman-enabling-conditions.md", + "category": "frameworks" + }, + { + "id": "johari-window", + "kind": "skill", + "path": "skills/frameworks/johari-window.md", + "category": "frameworks" + }, + { + "id": "kaizen-bpr", + "kind": "skill", + "path": "skills/frameworks/kaizen-bpr.md", + "category": "frameworks" + }, + { + "id": "kotter-change-model", + "kind": "skill", + "path": "skills/frameworks/kotter-change-model.md", + "category": "frameworks" + }, + { + "id": "leadership-pipeline", + "kind": "skill", + "path": "skills/frameworks/leadership-pipeline.md", + "category": "frameworks" + }, + { + "id": "lean-in", + "kind": "skill", + "path": "skills/frameworks/lean-in.md", + "category": "frameworks" + }, + { + "id": "lewin-leadership-styles", + "kind": "skill", + "path": "skills/frameworks/lewin-leadership-styles.md", + "category": "frameworks" + }, + { + "id": "maslow-hierarchy", + "kind": "skill", + "path": "skills/frameworks/maslow-hierarchy.md", + "category": "frameworks" + }, + { + "id": "myers-briggs-type-indicator", + "kind": "skill", + "path": "skills/frameworks/myers-briggs-type-indicator.md", + "category": "frameworks" + }, + { + "id": "net-promoter-score", + "kind": "skill", + "path": "skills/frameworks/net-promoter-score.md", + "category": "frameworks" + }, + { + "id": "neuro-linguistic-programming", + "kind": "skill", + "path": "skills/frameworks/neuro-linguistic-programming.md", + "category": "frameworks" + }, + { + "id": "organisational-culture", + "kind": "skill", + "path": "skills/frameworks/organisational-culture.md", + "category": "frameworks" + }, + { + "id": "porters-five-forces", + "kind": "skill", + "path": "skills/frameworks/porters-five-forces.md", + "category": "frameworks" + }, + { + "id": "product-life-cycle", + "kind": "skill", + "path": "skills/frameworks/product-life-cycle.md", + "category": "frameworks" + }, + { + "id": "psychological-safety", + "kind": "skill", + "path": "skills/frameworks/psychological-safety.md", + "category": "frameworks" + }, + { + "id": "radical-candor", + "kind": "skill", + "path": "skills/frameworks/radical-candor.md", + "category": "frameworks" + }, + { + "id": "scenario-planning", + "kind": "skill", + "path": "skills/frameworks/scenario-planning.md", + "category": "frameworks" + }, + { + "id": "shamrock-organisation", + "kind": "skill", + "path": "skills/frameworks/shamrock-organisation.md", + "category": "frameworks" + }, + { + "id": "situational-leadership", + "kind": "skill", + "path": "skills/frameworks/situational-leadership.md", + "category": "frameworks" + }, + { + "id": "smart-goals", + "kind": "skill", + "path": "skills/frameworks/smart-goals.md", + "category": "frameworks" + }, + { + "id": "swot-pest-analysis", + "kind": "skill", + "path": "skills/frameworks/swot-pest-analysis.md", + "category": "frameworks" + }, + { + "id": "systems-thinking", + "kind": "skill", + "path": "skills/frameworks/systems-thinking.md", + "category": "frameworks" + }, + { + "id": "thinking-fast-and-slow", + "kind": "skill", + "path": "skills/frameworks/thinking-fast-and-slow.md", + "category": "frameworks" + }, + { + "id": "thomas-kilmann-conflict", + "kind": "skill", + "path": "skills/frameworks/thomas-kilmann-conflict.md", + "category": "frameworks" + }, + { + "id": "tipping-point", + "kind": "skill", + "path": "skills/frameworks/tipping-point.md", + "category": "frameworks" + }, + { + "id": "trust-equation", + "kind": "skill", + "path": "skills/frameworks/trust-equation.md", + "category": "frameworks" + }, + { + "id": "tuckman-team-stages", + "kind": "skill", + "path": "skills/frameworks/tuckman-team-stages.md", + "category": "frameworks" + }, + { + "id": "vuca-framework", + "kind": "skill", + "path": "skills/frameworks/vuca-framework.md", + "category": "frameworks" + }, + { + "id": "win-win-negotiation", + "kind": "skill", + "path": "skills/frameworks/win-win-negotiation.md", + "category": "frameworks" + }, + { + "id": "coalition-and-partnership-games", + "kind": "skill", + "path": "skills/game-theory/coalition-and-partnership-games.md", + "category": "game-theory" + }, + { + "id": "evolutionary-strategy", + "kind": "skill", + "path": "skills/game-theory/evolutionary-strategy.md", + "category": "game-theory" + }, + { + "id": "first-mover-strategy", + "kind": "skill", + "path": "skills/game-theory/first-mover-strategy.md", + "category": "game-theory" + }, + { + "id": "game-theory-fundamentals", + "kind": "skill", + "path": "skills/game-theory/game-theory-fundamentals.md", + "category": "game-theory" + }, + { + "id": "information-asymmetry", + "kind": "skill", + "path": "skills/game-theory/information-asymmetry.md", + "category": "game-theory" + }, + { + "id": "negotiation-game-theory", + "kind": "skill", + "path": "skills/game-theory/negotiation-game-theory.md", + "category": "game-theory" + }, + { + "id": "prisoners-dilemma-and-cooperation", + "kind": "skill", + "path": "skills/game-theory/prisoners-dilemma-and-cooperation.md", + "category": "game-theory" + }, + { + "id": "ai-era-leadership", + "kind": "skill", + "path": "skills/leadership/ai-era-leadership.md", + "category": "leadership" + }, + { + "id": "business-writing-for-leaders", + "kind": "skill", + "path": "skills/leadership/business-writing-for-leaders.md", + "category": "leadership" + }, + { + "id": "career-strategy-for-leaders", + "kind": "skill", + "path": "skills/leadership/career-strategy-for-leaders.md", + "category": "leadership" + }, + { + "id": "decision-making-under-pressure", + "kind": "skill", + "path": "skills/leadership/decision-making-under-pressure.md", + "category": "leadership" + }, + { + "id": "delegation-and-empowerment", + "kind": "skill", + "path": "skills/leadership/delegation-and-empowerment.md", + "category": "leadership" + }, + { + "id": "emotional-courage", + "kind": "skill", + "path": "skills/leadership/emotional-courage.md", + "category": "leadership" + }, + { + "id": "employee-engagement-retention", + "kind": "skill", + "path": "skills/leadership/employee-engagement-retention.md", + "category": "leadership" + }, + { + "id": "focus-and-priority-management", + "kind": "skill", + "path": "skills/leadership/focus-and-priority-management.md", + "category": "leadership" + }, + { + "id": "humility-and-power", + "kind": "skill", + "path": "skills/leadership/humility-and-power.md", + "category": "leadership" + }, + { + "id": "inclusive-leadership", + "kind": "skill", + "path": "skills/leadership/inclusive-leadership.md", + "category": "leadership" + }, + { + "id": "introvert-leadership", + "kind": "skill", + "path": "skills/leadership/introvert-leadership.md", + "category": "leadership" + }, + { + "id": "leader-resilience-and-wellbeing", + "kind": "skill", + "path": "skills/leadership/leader-resilience-and-wellbeing.md", + "category": "leadership" + }, + { + "id": "leader-self-reflection", + "kind": "skill", + "path": "skills/leadership/leader-self-reflection.md", + "category": "leadership" + }, + { + "id": "leadership-style-adaptation", + "kind": "skill", + "path": "skills/leadership/leadership-style-adaptation.md", + "category": "leadership" + }, + { + "id": "leadership-voice-and-presence", + "kind": "skill", + "path": "skills/leadership/leadership-voice-and-presence.md", + "category": "leadership" + }, + { + "id": "leading-through-change", + "kind": "skill", + "path": "skills/leadership/leading-through-change.md", + "category": "leadership" + }, + { + "id": "learning-agility", + "kind": "skill", + "path": "skills/leadership/learning-agility.md", + "category": "leadership" + }, + { + "id": "learning-from-failure", + "kind": "skill", + "path": "skills/leadership/learning-from-failure.md", + "category": "leadership" + }, + { + "id": "managing-up", + "kind": "skill", + "path": "skills/leadership/managing-up.md", + "category": "leadership" + }, + { + "id": "mentoring-and-coaching", + "kind": "skill", + "path": "skills/leadership/mentoring-and-coaching.md", + "category": "leadership" + }, + { + "id": "persuasion-and-influence", + "kind": "skill", + "path": "skills/leadership/persuasion-and-influence.md", + "category": "leadership" + }, + { + "id": "psychological-safety-practice", + "kind": "skill", + "path": "skills/leadership/psychological-safety-practice.md", + "category": "leadership" + }, + { + "id": "purpose-driven-leadership", + "kind": "skill", + "path": "skills/leadership/purpose-driven-leadership.md", + "category": "leadership" + }, + { + "id": "senior-leadership-transition", + "kind": "skill", + "path": "skills/leadership/senior-leadership-transition.md", + "category": "leadership" + }, + { + "id": "storytelling-for-leaders", + "kind": "skill", + "path": "skills/leadership/storytelling-for-leaders.md", + "category": "leadership" + }, + { + "id": "strategic-questioning", + "kind": "skill", + "path": "skills/leadership/strategic-questioning.md", + "category": "leadership" + }, + { + "id": "strategic-thinking-and-alignment", + "kind": "skill", + "path": "skills/leadership/strategic-thinking-and-alignment.md", + "category": "leadership" + }, + { + "id": "team-culture-and-dynamics", + "kind": "skill", + "path": "skills/leadership/team-culture-and-dynamics.md", + "category": "leadership" + }, + { + "id": "competitive-negotiation", + "kind": "skill", + "path": "skills/negotiation/competitive-negotiation.md", + "category": "negotiation" + }, + { + "id": "cooperative-negotiation", + "kind": "skill", + "path": "skills/negotiation/cooperative-negotiation.md", + "category": "negotiation" + }, + { + "id": "delivering-the-deal", + "kind": "skill", + "path": "skills/negotiation/delivering-the-deal.md", + "category": "negotiation" + }, + { + "id": "negotiation-mindset-and-self", + "kind": "skill", + "path": "skills/negotiation/negotiation-mindset-and-self.md", + "category": "negotiation" + }, + { + "id": "connecting-with-people", + "kind": "skill", + "path": "skills/people/connecting-with-people.md", + "category": "people" + }, + { + "id": "influencing-and-persuading", + "kind": "skill", + "path": "skills/people/influencing-and-persuading.md", + "category": "people" + }, + { + "id": "inspiring-and-retaining", + "kind": "skill", + "path": "skills/people/inspiring-and-retaining.md", + "category": "people" + }, + { + "id": "meeting-the-right-people", + "kind": "skill", + "path": "skills/people/meeting-the-right-people.md", + "category": "people" + }, + { + "id": "reading-people", + "kind": "skill", + "path": "skills/people/reading-people.md", + "category": "people" + }, + { + "id": "resolving-people-conflict", + "kind": "skill", + "path": "skills/people/resolving-people-conflict.md", + "category": "people" + }, + { + "id": "teaching-and-leading", + "kind": "skill", + "path": "skills/people/teaching-and-leading.md", + "category": "people" + }, + { + "id": "understanding-people", + "kind": "skill", + "path": "skills/people/understanding-people.md", + "category": "people" + }, + { + "id": "stoic-acceptance-amor-fati", + "kind": "skill", + "path": "skills/stoic/stoic-acceptance-amor-fati.md", + "category": "stoic" + }, + { + "id": "stoic-control-and-clarity", + "kind": "skill", + "path": "skills/stoic/stoic-control-and-clarity.md", + "category": "stoic" + }, + { + "id": "stoic-duty-and-service", + "kind": "skill", + "path": "skills/stoic/stoic-duty-and-service.md", + "category": "stoic" + }, + { + "id": "stoic-emotional-mastery", + "kind": "skill", + "path": "skills/stoic/stoic-emotional-mastery.md", + "category": "stoic" + }, + { + "id": "stoic-fortitude-and-resilience", + "kind": "skill", + "path": "skills/stoic/stoic-fortitude-and-resilience.md", + "category": "stoic" + }, + { + "id": "stoic-mortality-and-perspective", + "kind": "skill", + "path": "skills/stoic/stoic-mortality-and-perspective.md", + "category": "stoic" + }, + { + "id": "stoic-pragmatism", + "kind": "skill", + "path": "skills/stoic/stoic-pragmatism.md", + "category": "stoic" + }, + { + "id": "stoic-problem-solving", + "kind": "skill", + "path": "skills/stoic/stoic-problem-solving.md", + "category": "stoic" + }, + { + "id": "stoic-right-action", + "kind": "skill", + "path": "skills/stoic/stoic-right-action.md", + "category": "stoic" + }, + { + "id": "stoic-self-awareness", + "kind": "skill", + "path": "skills/stoic/stoic-self-awareness.md", + "category": "stoic" + }, + { + "id": "stoic-unbiased-thought", + "kind": "skill", + "path": "skills/stoic/stoic-unbiased-thought.md", + "category": "stoic" + }, + { + "id": "stoic-virtue-and-kindness", + "kind": "skill", + "path": "skills/stoic/stoic-virtue-and-kindness.md", + "category": "stoic" + }, + { + "id": "building-story-stakes", + "kind": "skill", + "path": "skills/storytelling/building-story-stakes.md", + "category": "storytelling" + }, + { + "id": "emotional-impact-in-stories", + "kind": "skill", + "path": "skills/storytelling/emotional-impact-in-stories.md", + "category": "storytelling" + }, + { + "id": "finding-your-stories", + "kind": "skill", + "path": "skills/storytelling/finding-your-stories.md", + "category": "storytelling" + }, + { + "id": "story-beginnings-and-endings", + "kind": "skill", + "path": "skills/storytelling/story-beginnings-and-endings.md", + "category": "storytelling" + }, + { + "id": "story-performance-and-delivery", + "kind": "skill", + "path": "skills/storytelling/story-performance-and-delivery.md", + "category": "storytelling" + }, + { + "id": "story-structure-and-arc", + "kind": "skill", + "path": "skills/storytelling/story-structure-and-arc.md", + "category": "storytelling" + }, + { + "id": "storytelling-truth-and-vividness", + "kind": "skill", + "path": "skills/storytelling/storytelling-truth-and-vividness.md", + "category": "storytelling" + }, + { + "id": "what-is-a-story", + "kind": "skill", + "path": "skills/storytelling/what-is-a-story.md", + "category": "storytelling" + }, + { + "id": "building-thinking-strength", + "kind": "skill", + "path": "skills/thinking/building-thinking-strength.md", + "category": "thinking" + }, + { + "id": "defining-and-exploring-problems", + "kind": "skill", + "path": "skills/thinking/defining-and-exploring-problems.md", + "category": "thinking" + }, + { + "id": "enemies-of-clear-thinking", + "kind": "skill", + "path": "skills/thinking/enemies-of-clear-thinking.md", + "category": "thinking" + }, + { + "id": "evaluating-and-deciding", + "kind": "skill", + "path": "skills/thinking/evaluating-and-deciding.md", + "category": "thinking" + }, + { + "id": "managing-weakness-and-mistakes", + "kind": "skill", + "path": "skills/thinking/managing-weakness-and-mistakes.md", + "category": "thinking" + }, + { + "id": "wanting-what-matters", + "kind": "skill", + "path": "skills/thinking/wanting-what-matters.md", + "category": "thinking" + }, + { + "id": "clarity-and-concision", + "kind": "skill", + "path": "skills/writing/clarity-and-concision.md", + "category": "writing" + }, + { + "id": "grammar-and-mechanics", + "kind": "skill", + "path": "skills/writing/grammar-and-mechanics.md", + "category": "writing" + }, + { + "id": "plain-language-and-flow", + "kind": "skill", + "path": "skills/writing/plain-language-and-flow.md", + "category": "writing" + }, + { + "id": "reader-psychology", + "kind": "skill", + "path": "skills/writing/reader-psychology.md", + "category": "writing" + }, + { + "id": "revising-and-editing", + "kind": "skill", + "path": "skills/writing/revising-and-editing.md", + "category": "writing" + }, + { + "id": "tone-and-engagement", + "kind": "skill", + "path": "skills/writing/tone-and-engagement.md", + "category": "writing" + }, + { + "id": "writing-effective-emails", + "kind": "skill", + "path": "skills/writing/writing-effective-emails.md", + "category": "writing" + }, + { + "id": "writing-for-navigation", + "kind": "skill", + "path": "skills/writing/writing-for-navigation.md", + "category": "writing" + }, + { + "id": "writing-for-response", + "kind": "skill", + "path": "skills/writing/writing-for-response.md", + "category": "writing" + }, + { + "id": "writing-memos-and-reports", + "kind": "skill", + "path": "skills/writing/writing-memos-and-reports.md", + "category": "writing" + }, + { + "id": "writing-performance-reviews", + "kind": "skill", + "path": "skills/writing/writing-performance-reviews.md", + "category": "writing" + }, + { + "id": "writing-process", + "kind": "skill", + "path": "skills/writing/writing-process.md", + "category": "writing" + }, + { + "id": "writing-with-purpose", + "kind": "skill", + "path": "skills/writing/writing-with-purpose.md", + "category": "writing" + } + ], + "aliases": { + "skill": { + "swot-analysis": "swot-pest-analysis", + "swot": "swot-pest-analysis", + "kaizen": "kaizen-bpr", + "tuckman-stages": "tuckman-team-stages", + "nps": "net-promoter-score" + }, + "diagnostic": { + "team": "team-dysfunction-diagnosis", + "product": "product-market-fit-diagnosis", + "culture": "culture-erosion-diagnosis", + "competition": "competitive-threat-diagnosis", + "churn": "customer-churn-diagnosis", + "cofounder": "cofounder-conflict-diagnosis", + "communication": "communication-breakdown-diagnosis", + "decisions": "decision-paralysis-diagnosis", + "operations": "operational-chaos-diagnosis", + "strategy": "strategic-drift-diagnosis" + }, + "research": { + "customer-interviews": "customer-interview-guide", + "market-sizing": "market-sizing-worksheet", + "competitor-analysis": "competitor-research-template", + "financial-modeling": "financial-modeling-guide", + "funding-landscape": "funding-landscape-research", + "technology-stack": "technology-stack-research", + "regulatory-landscape": "regulatory-landscape-research" + } + }, + "commands": { + "apply": "apply", + "diagnose": "diagnose", + "run": "foreman-run", + "resume": "foreman-resume", + "output": "output", + "track": "track", + "progress": "progress", + "blockers": "blockers", + "check-in": "check-in", + "language": "language", + "context": "foreman-context", + "update": "update", + "history": "history", + "decisions": "decisions", + "follow-ups": "follow-ups", + "forget": "forget", + "reset": "foreman-reset", + "help": "foreman-help", + "about": "about", + "version": "version", + "feedback": "feedback", + "sector": "sector", + "stage": "stage", + "skills": "skills", + "skill": "foreman-skill", + "templates": "templates", + "playbooks": "playbooks", + "diagnostics": "diagnostics", + "hooks": "hooks", + "search": "search", + "stakeholders": "stakeholders", + "power-map": "power-map", + "resistance": "resistance", + "coalition": "coalition", + "format": "format", + "export": "export", + "compare": "compare", + "status": "foreman-status", + "skip": "skip", + "back": "back", + "pause": "pause", + "abort": "abort", + "research": "research", + "simulate": "simulate", + "solo": "solo", + "stoic": "stoic" + } +} diff --git a/plugins/foreman/content/commands/abort.md b/plugins/foreman/content/commands/abort.md new file mode 100644 index 0000000..f60f13a --- /dev/null +++ b/plugins/foreman/content/commands/abort.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /abort command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /abort + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/about.md b/plugins/foreman/content/commands/about.md new file mode 100644 index 0000000..2e1778d --- /dev/null +++ b/plugins/foreman/content/commands/about.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /about command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /about + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /about with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/apply.md b/plugins/foreman/content/commands/apply.md new file mode 100644 index 0000000..2172e4d --- /dev/null +++ b/plugins/foreman/content/commands/apply.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /apply command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /apply + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /apply with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/back.md b/plugins/foreman/content/commands/back.md new file mode 100644 index 0000000..0856a3e --- /dev/null +++ b/plugins/foreman/content/commands/back.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /back command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /back + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /back with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/blockers.md b/plugins/foreman/content/commands/blockers.md new file mode 100644 index 0000000..692dab2 --- /dev/null +++ b/plugins/foreman/content/commands/blockers.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /blockers command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /blockers + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /blockers with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/check-in.md b/plugins/foreman/content/commands/check-in.md new file mode 100644 index 0000000..79e6e1b --- /dev/null +++ b/plugins/foreman/content/commands/check-in.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /check-in command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /check-in + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /check-in with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/coalition.md b/plugins/foreman/content/commands/coalition.md new file mode 100644 index 0000000..089b2b8 --- /dev/null +++ b/plugins/foreman/content/commands/coalition.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /coalition command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /coalition + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /coalition with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/compare.md b/plugins/foreman/content/commands/compare.md new file mode 100644 index 0000000..6d8eb0d --- /dev/null +++ b/plugins/foreman/content/commands/compare.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /compare command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /compare + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /compare with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/decisions.md b/plugins/foreman/content/commands/decisions.md new file mode 100644 index 0000000..de9ac6e --- /dev/null +++ b/plugins/foreman/content/commands/decisions.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /decisions command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /decisions + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /decisions with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/diagnose.md b/plugins/foreman/content/commands/diagnose.md new file mode 100644 index 0000000..351e24f --- /dev/null +++ b/plugins/foreman/content/commands/diagnose.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /diagnose command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnose + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /diagnose with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +Before answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact. diff --git a/plugins/foreman/content/commands/diagnostics.md b/plugins/foreman/content/commands/diagnostics.md new file mode 100644 index 0000000..8228831 --- /dev/null +++ b/plugins/foreman/content/commands/diagnostics.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /diagnostics command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnostics + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /diagnostics with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/execution-commands.md b/plugins/foreman/content/commands/execution-commands.md new file mode 100644 index 0000000..af34da4 --- /dev/null +++ b/plugins/foreman/content/commands/execution-commands.md @@ -0,0 +1,324 @@ +--- +name: "execution-commands" +description: "Commands for applying skills, running diagnostics, executing playbooks, and formatting output. These commands trigger the agent architecture and produce analytical results. They read from and write to the memory system." +category: "execution" +commands: + - name: "/apply" + syntax: "/apply [skill-name] [--stage stage]" + description: "Apply a skill to the current entrepreneur context via the skill-executor agent." + - name: "/diagnose" + syntax: "/diagnose [area]" + description: "Run a diagnostic to identify the root cause behind a stated problem." + - name: "/run" + syntax: "/run [playbook-name]" + description: "Start a multi-step playbook from Step 1, checking prerequisites first." + - name: "/resume" + syntax: "/resume" + description: "Resume a paused playbook from the last completed step." + - name: "/output" + syntax: "/output [template] [audience]" + description: "Format the most recent analysis results into a specific output template." +author: "Fatih Guner" +--- + +# Execution Commands + +## `/apply` + +### Description + +Applies a single skill to the entrepreneur's current context. This command invokes the skill-executor agent, which loads the specified skill, pulls identity and company data from memory, adapts the framework to the entrepreneur's stage, and produces a structured analysis. Results are persisted to the history layer of memory. An optional stage override forces the skill to operate as though the company were at a different stage — useful for scenario planning. + +### Syntax + +``` +/apply [skill-name] [--stage stage] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `skill-name` | Yes | string | -- | Skill identifier in kebab-case (e.g., `porters-five-forces`) | +| `--stage` | No | string | from memory | Override the company stage: `idea`, `validation`, `early-traction`, `growth`, `scale` | + +### Examples + +``` +/apply porters-five-forces +→ Applying "Porter's Five Forces" to context... + Stage: early-traction (from company profile) + Loading competitive data from memory... + [Full framework analysis output with five forces scored and interpreted] + +/apply swot-pest-analysis --stage growth +→ Applying "SWOT-PEST Analysis" with stage override: growth + Note: Company profile indicates "early-traction" — analysis adjusted to growth-stage lens. + [Combined SWOT and PEST analysis with growth-specific guidance] + +/apply business-model-canvas +→ Applying "Business Model Canvas" to context... + Stage: idea (from company profile) + [Nine building blocks populated from company context, gaps identified] + +/apply stoic-emotional-mastery +→ Applying "Stoic Emotional Mastery" to context... + Stage: validation (from company profile) + [Framework applied to current active challenges from memory] +``` + +### Related Commands + +- `/skill [name]` — Preview a skill's summary before applying it +- `/skills` — Browse available skills to find the right one +- `/output [template] [audience]` — Format the analysis results for a specific audience + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/apply` | `Missing skill name. Usage: /apply [skill-name] [--stage stage]. Run /skills to browse available skills.` | +| `/apply blue-ocean` | `No skill found matching "blue-ocean". Did you mean: blue-ocean-strategy? Run /search "blue ocean" to explore.` | +| `/apply porters-five-forces --stage seed` | `Unknown stage "seed". Valid stages: idea, validation, early-traction, growth, scale.` | +| `/apply porters-five-forces` (no company context) | `No company profile found. Run /update company to set your company context before applying skills.` | + +--- + +## `/diagnose` + +### Description + +Runs a diagnostic flow to triage a problem area. The command maps the area keyword to the appropriate diagnostic file, then walks the entrepreneur through targeted questions to pinpoint the root cause. Once the root cause is identified, the diagnostic recommends specific skills or playbooks. Results are stored in the history layer of memory for future reference. + +### Syntax + +``` +/diagnose [area] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `area` | Yes | string | -- | Problem area keyword: `revenue`, `team`, `pricing`, `fundraising`, `growth`, `product`, `culture`, `leadership`, `competition`, `hiring`, `churn`, `cofounder`, `communication`, `decisions`, `innovation`, `operations`, `partnership`, `market-entry`, `strategy`, `negotiation` | + +### Examples + +``` +/diagnose revenue +→ Starting revenue-diagnosis... + Q1: Has monthly recurring revenue declined, plateaued, or simply not grown as expected? + Q2: When did you first notice the change — weeks, months, or quarters ago? + Q3: Have you changed pricing, product, or sales approach in the same period? + [Diagnostic continues with targeted questions, then produces root-cause analysis] + +/diagnose team +→ Starting team-dysfunction-diagnosis... + Q1: Is the issue concentrated in one team or department, or distributed? + Q2: Did a specific event trigger the dysfunction — departure, reorg, missed target? + [Diagnostic narrows from broad dysfunction to specific root cause] + +/diagnose pricing +→ Starting pricing-diagnosis... + Q1: Are you losing deals on price, or are customers paying but churning? + Q2: Have you tested pricing experimentally, or is the current price inherited? + [Diagnostic identifies pricing-specific failure mode and recommends next steps] + +/diagnose churn +→ Starting customer-churn-diagnosis... + Q1: What is your current monthly churn rate, and how does it compare to six months ago? + [Diagnostic drills into churn drivers] +``` + +### Related Commands + +- `/diagnostics` — List all available diagnostics before choosing +- `/apply [skill]` — Apply a skill recommended by the diagnostic +- `/run [playbook]` — Start a playbook recommended by the diagnostic +- `/history` — Review past diagnostic results + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/diagnose` | `Missing problem area. Usage: /diagnose [area]. Run /diagnostics to see all available areas.` | +| `/diagnose marketing` | `No diagnostic matches "marketing". Closest matches: market-entry, competition, growth. Run /diagnostics for the full list.` | + +--- + +## `/run` + +### Description + +Starts a multi-step playbook from the beginning. Before execution, the command checks prerequisites — required memory fields, company stage compatibility, and any prior diagnostics the playbook expects. If prerequisites pass, Step 1 begins immediately. Progress is saved to the active memory layer after each step, enabling pause and resume. Only one playbook can be active at a time. + +### Syntax + +``` +/run [playbook-name] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `playbook-name` | Yes | string | -- | Playbook identifier in kebab-case (e.g., `fundraising-playbook`) | + +### Examples + +``` +/run fundraising-playbook +→ Checking prerequisites for "fundraising-playbook"... + Company profile: present + Stage: early-traction (compatible) + Required prior diagnostic: fundraising-diagnosis (completed 2026-03-10) + Prerequisites met. Starting Step 1 of 8. + [Step 1: Define round parameters — amount, valuation range, investor profile] + +/run pivot-playbook +→ Checking prerequisites for "pivot-playbook"... + Company profile: present + Stage: validation (compatible) + Required prior diagnostic: product-market-fit-diagnosis (not found) + Recommendation: Run /diagnose product first to establish baseline before pivoting. + Proceeding anyway? [y/n] + +/run first-100-customers-playbook +→ Checking prerequisites for "first-100-customers-playbook"... + Company profile: present + Stage: idea (compatible) + No prior diagnostics required. + Starting Step 1 of 6. + [Step 1: Define ideal customer profile from company context] + +/run scaling-playbook +→ Cannot start "scaling-playbook" — a playbook is already active. + Active: fundraising-playbook (Step 4 of 8, paused 2026-03-22) + Complete or abandon the active playbook first, or run /resume to continue it. +``` + +### Related Commands + +- `/playbooks` — Browse available playbooks +- `/resume` — Continue a paused playbook +- `/diagnose [area]` — Run a prerequisite diagnostic + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/run` | `Missing playbook name. Usage: /run [playbook-name]. Run /playbooks to browse available playbooks.` | +| `/run fundraising` | `No playbook found matching "fundraising". Did you mean: fundraising-playbook? Run /playbooks for the full list.` | +| `/run scaling-playbook` (incompatible stage) | `"scaling-playbook" requires stage growth or scale. Your current stage: validation. Override with /update company to change your stage, or choose a stage-appropriate playbook.` | + +--- + +## `/resume` + +### Description + +Resumes the currently active playbook from the last completed step. Reads the active memory layer to determine which playbook is in progress, which step was last completed, and what context was captured so far. If no playbook is active, the command reports that and suggests `/run` or `/playbooks`. + +### Syntax + +``` +/resume +``` + +### Parameters + +This command takes no parameters. + +### Examples + +``` +/resume +→ Resuming "fundraising-playbook"... + Last completed: Step 4 of 8 (paused 2026-03-22) + Context loaded: round parameters, target investor list, pitch narrative draft + Starting Step 5: Financial model review and unit economics validation. + +/resume +→ Resuming "pivot-playbook"... + Last completed: Step 2 of 5 (paused 2026-03-24) + Context loaded: current PMF assessment, customer interview synthesis + Starting Step 3: Generate pivot options using Lean Canvas. + +/resume +→ No active playbook found. + Start a new playbook with /run [playbook-name]. Run /playbooks to browse options. +``` + +### Related Commands + +- `/run [playbook]` — Start a new playbook +- `/playbooks` — Browse available playbooks +- `/context` — Check what active items exist in memory + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/resume` (no active playbook) | `No active playbook found. Start one with /run [playbook-name].` | +| `/resume` (corrupted state) | `Active playbook state is incomplete. Last known position: fundraising-playbook, Step 3. Restart from Step 3? [y/n]` | + +--- + +## `/output` + +### Description + +Formats the most recent analysis results — from a skill application, diagnostic, or playbook step — into a specified output template for a target audience. The command reads the latest results from memory, applies the selected template's structure and tone, and produces a polished document. If no recent results exist, the command reports that and suggests running an analysis first. + +### Syntax + +``` +/output [template] [audience] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `template` | Yes | string | -- | Template identifier in kebab-case (e.g., `strategic-analysis-one-pager`) | +| `audience` | Yes | string | -- | Target audience: `investor`, `board`, `team`, `self`, `client` | + +### Examples + +``` +/output strategic-analysis-one-pager investor +→ Formatting last analysis (Porter's Five Forces, 2026-03-25) for investor audience... + Template: strategic-analysis-one-pager + [Formatted one-page strategic analysis with investor-appropriate framing] + +/output action-plan team +→ Formatting last analysis (pivot-playbook Step 3, 2026-03-24) for team audience... + Template: action-plan + [Structured action plan with team-facing language, clear owners, and timelines] + +/output decision-rationale-memo investor +→ Formatting last decision (pricing model change, 2026-03-23) for investor audience... + Template: decision-rationale-memo + [Formal memo explaining the rationale, alternatives considered, and expected impact] + +/output weekly-ceo-review self +→ Formatting accumulated week data for self audience... + Template: weekly-ceo-review + [Personal review covering decisions made, diagnostics run, and open items] +``` + +### Related Commands + +- `/templates` — Browse available templates and audiences +- `/apply [skill]` — Generate analysis results to format +- `/diagnose [area]` — Generate diagnostic results to format + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/output` | `Missing template and audience. Usage: /output [template] [audience].` | +| `/output strategic-analysis-one-pager` | `Missing audience. Usage: /output [template] [audience]. Available audiences: investor, board, team, self, client.` | +| `/output strategic-analysis-one-pager partner` | `Unknown audience "partner". Available audiences: investor, board, team, self, client.` | +| `/output nonexistent-template investor` | `No template found matching "nonexistent-template". Run /templates investor to see available templates for that audience.` | +| `/output strategic-analysis-one-pager investor` (no recent results) | `No recent analysis results found. Run /apply [skill] or /diagnose [area] first, then format the output.` | diff --git a/plugins/foreman/content/commands/export.md b/plugins/foreman/content/commands/export.md new file mode 100644 index 0000000..4ee1dae --- /dev/null +++ b/plugins/foreman/content/commands/export.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /export command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /export + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /export with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/feedback.md b/plugins/foreman/content/commands/feedback.md new file mode 100644 index 0000000..940eb4b --- /dev/null +++ b/plugins/foreman/content/commands/feedback.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /feedback command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /feedback + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /feedback with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/follow-ups.md b/plugins/foreman/content/commands/follow-ups.md new file mode 100644 index 0000000..446fa06 --- /dev/null +++ b/plugins/foreman/content/commands/follow-ups.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /follow-ups command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /follow-ups + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /follow-ups with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-context.md b/plugins/foreman/content/commands/foreman-context.md new file mode 100644 index 0000000..a07d220 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-context.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /context command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /context + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /context with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-help.md b/plugins/foreman/content/commands/foreman-help.md new file mode 100644 index 0000000..fcf6a21 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-help.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /help command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /help + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /help with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-reset.md b/plugins/foreman/content/commands/foreman-reset.md new file mode 100644 index 0000000..76b547b --- /dev/null +++ b/plugins/foreman/content/commands/foreman-reset.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /reset command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /reset + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /reset with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-resume.md b/plugins/foreman/content/commands/foreman-resume.md new file mode 100644 index 0000000..5d9cde8 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-resume.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resume command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resume + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /resume with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-run.md b/plugins/foreman/content/commands/foreman-run.md new file mode 100644 index 0000000..fee87b3 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-run.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /run command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /run + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /run with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-skill.md b/plugins/foreman/content/commands/foreman-skill.md new file mode 100644 index 0000000..1260b36 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-skill.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skill command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skill + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /skill with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/foreman-status.md b/plugins/foreman/content/commands/foreman-status.md new file mode 100644 index 0000000..509e630 --- /dev/null +++ b/plugins/foreman/content/commands/foreman-status.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /status command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /status + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /status with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/forget.md b/plugins/foreman/content/commands/forget.md new file mode 100644 index 0000000..7c5869c --- /dev/null +++ b/plugins/foreman/content/commands/forget.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /forget command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /forget + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /forget with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/format.md b/plugins/foreman/content/commands/format.md new file mode 100644 index 0000000..9bbeee3 --- /dev/null +++ b/plugins/foreman/content/commands/format.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /format command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /format + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/output-commands.md and execute only /format with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/history.md b/plugins/foreman/content/commands/history.md new file mode 100644 index 0000000..e094fe9 --- /dev/null +++ b/plugins/foreman/content/commands/history.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /history command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /history + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /history with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/hooks.md b/plugins/foreman/content/commands/hooks.md new file mode 100644 index 0000000..0af0a59 --- /dev/null +++ b/plugins/foreman/content/commands/hooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /hooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /hooks + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /hooks with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/implementation-commands.md b/plugins/foreman/content/commands/implementation-commands.md new file mode 100644 index 0000000..6f6c9ea --- /dev/null +++ b/plugins/foreman/content/commands/implementation-commands.md @@ -0,0 +1,351 @@ +--- +name: "implementation-commands" +description: "Commands for tracking implementation of recommendations, updating progress, analyzing blockers, and running weekly accountability check-ins. These commands operate on the implementation tracking layer and read from and write to the active and history memory layers." +category: "implementation" +commands: + - name: "/track" + syntax: "/track [status-filter]" + description: "View all active implementation items with status, progress, deadlines, and blockers. Filterable by status." + - name: "/progress" + syntax: "/progress [item-id] [percentage] [note]" + description: "Update progress on a specific implementation item." + - name: "/blockers" + syntax: "/blockers [category-filter]" + description: "View all blocked items with blocker analysis and suggested resolution routes." + - name: "/check-in" + syntax: "/check-in" + description: "Run the weekly accountability check-in protocol across all active implementation items." +author: "Fatih Guner" +--- + +# Implementation Commands + +## `/track` + +### Description + +Displays all active implementation items -- every recommendation from playbooks, skills, and diagnostics that has entered the tracking system and has not yet reached a terminal state. The default view shows all non-terminal items sorted by deadline proximity. Status filters narrow the view to a specific state. The `overdue` filter is a computed view: it surfaces items past their deadline that have not been completed, regardless of their current status. + +This is the command for situational awareness. Run it at the start of a session to see what is in flight, what is stuck, and what is due. + +### Syntax + +``` +/track [status-filter] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `status-filter` | No | string | all active | Filter by status: `not-started`, `in-progress`, `blocked`, `completed`, `abandoned`, `deferred`, `overdue`, `stalled` | + +### Examples + +``` +/track +--> Implementation Tracker: 12 active items + 3 not-started | 5 in-progress | 2 blocked | 1 deferred | 1 overdue + [Table: ID | Description | Status | Progress | Deadline | Last Check-in] + impl-001 Redesign BMC for B2B pivot in-progress 40% Apr 15 Apr 08 + impl-002 Validate pricing with 10 prospects in-progress 70% Apr 10 Apr 08 + impl-003 Draft investor narrative for pivot not-started 0% Apr 20 -- + ... + +/track blocked +--> Blocked Items: 2 + [Table: ID | Description | Blocker Category | Blocker | Days Blocked] + impl-005 Hire freelance designer resource Budget not approved 12 + impl-008 Integrate partner API dependency Waiting on partner SDK 7 + +/track in-progress +--> In-Progress Items: 5 + [Table: ID | Description | Progress | Deadline | Trend] + impl-001 Redesign BMC for B2B pivot 40% Apr 15 +20% this week + impl-002 Validate pricing with 10 prospects 70% Apr 10 +30% this week + ... + +/track overdue +--> Overdue Items: 1 + [Table: ID | Description | Status | Progress | Deadline | Days Overdue] + impl-004 Complete competitive analysis in-progress 25% Apr 01 7 days overdue + +/track stalled +--> Stalled Items (no progress for 14+ days): 2 + [Table: ID | Description | Progress | Last Change | Days Stalled] + impl-005 Hire freelance designer 10% Mar 25 14 days + impl-009 Document onboarding process 0% Mar 22 17 days + Recommendation: Run /blockers to analyze what is preventing movement. +``` + +### Related Commands + +- `/progress [item-id] [%] [note]` -- Update progress on a specific item +- `/blockers` -- Deep dive into blocked and stalled items +- `/check-in` -- Run the full weekly accountability protocol +- `/context` -- View broader active memory context + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/track` (no items exist) | `No implementation items found. Items are created when playbooks, skills, or diagnostics produce actionable recommendations.` | +| `/track overdue` (none overdue) | `No overdue items. All active items are within their deadlines.` | +| `/track invalid-status` | `Unknown status filter "invalid-status". Valid filters: not-started, in-progress, blocked, completed, abandoned, deferred, overdue, stalled.` | + +--- + +## `/progress` + +### Description + +Updates the progress on a specific implementation item. Accepts the item ID, a new percentage, and an optional note describing what changed. The command validates that the item exists and is in a trackable state (not completed, not abandoned). If the new percentage is 100, the system prompts for an outcome description and transitions the item to `completed` status. + +This is the lightweight update mechanism -- faster than a full `/check-in` when you want to record progress on a single item mid-week. + +### Syntax + +``` +/progress [item-id] [percentage] [note] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `item-id` | Yes | string | -- | Implementation item identifier (e.g., `impl-001`) | +| `percentage` | Yes | integer | -- | New progress percentage (0-100) | +| `note` | No | string | -- | Brief description of what changed. Enclosed in quotes if multi-word. | + +### Examples + +``` +/progress impl-001 60 "Customer interviews completed, synthesizing findings" +--> Updated impl-001: Redesign BMC for B2B pivot + Progress: 40% --> 60% (+20%) + Note recorded: "Customer interviews completed, synthesizing findings" + Deadline: Apr 15 (7 days remaining) + +/progress impl-002 100 "All 10 prospects validated, pricing model confirmed" +--> Updated impl-002: Validate pricing with 10 prospects + Progress: 70% --> 100% + Status: in-progress --> completed + Outcome recorded: "All 10 prospects validated, pricing model confirmed" + Item moved to history layer. + +/progress impl-003 15 "Outlined narrative structure, first draft of opening" +--> Updated impl-003: Draft investor narrative for pivot + Progress: 0% --> 15% + Status: not-started --> in-progress + Note recorded: "Outlined narrative structure, first draft of opening" + +/progress impl-005 10 +--> Cannot update impl-005: item is currently blocked. + Blocker: "Budget not approved" (resource) + Resolve the blocker first, or update status with /progress impl-005 10 "Proceeding despite budget constraint" + This will clear the blocked status and resume tracking. + +/progress impl-007 0 "Decided this is no longer relevant after market shift" +--> impl-007 progress set to 0% with note. + To abandon this item, confirm: /progress impl-007 abandon "Market shift made this obsolete" +``` + +### Related Commands + +- `/track` -- View all items to find the right ID +- `/blockers` -- If progress is blocked, analyze the blocker first +- `/check-in` -- For batch progress updates across all items + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/progress` | `Missing parameters. Usage: /progress [item-id] [percentage] [note]` | +| `/progress impl-999 50` | `No implementation item found with ID "impl-999". Run /track to see active items.` | +| `/progress impl-002 50` (item is completed) | `Item impl-002 is already completed. Completed items cannot be updated. To reopen, contact support or create a new item.` | +| `/progress impl-001 150` | `Invalid percentage "150". Progress must be between 0 and 100.` | +| `/progress impl-001 -10` | `Invalid percentage "-10". Progress must be between 0 and 100.` | + +--- + +## `/blockers` + +### Description + +Displays all items in `blocked` status plus items detected as stalled (no progress for 14+ days). For each blocker, the system shows the category, duration, impact assessment (what downstream items or deadlines are affected), and a recommended resolution route -- the specific diagnostic, skill, or action that could unblock the item. Category filters narrow the view to a specific blocker type. + +This command does analysis, not just reporting. It identifies patterns (multiple resource blockers may indicate a systemic funding issue), suggests resolution paths, and flags when a "dependency" blocker might actually be a "motivation" blocker in disguise. + +### Syntax + +``` +/blockers [category-filter] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `category-filter` | No | string | all | Filter by blocker category: `resource`, `knowledge`, `dependency`, `motivation`, `external` | + +### Examples + +``` +/blockers +--> Blocker Analysis: 4 items blocked or stalled + By category: 1 resource | 1 dependency | 1 motivation | 1 external + + [Detailed analysis per item] + + impl-005 | Hire freelance designer + Category: resource (budget) + Duration: 12 days blocked + Impact: Delays impl-001 (BMC redesign needs visual assets) by estimated 1 week + Resolution route: Run /diagnose operations to assess budget reallocation options + Apply resource-allocation skill for prioritization framework + + impl-008 | Integrate partner API + Category: dependency (waiting on partner) + Duration: 7 days blocked + Impact: Blocks impl-010 (launch beta to first 10 users) + Resolution route: Apply stakeholder-map to identify escalation path + Consider parallel work on impl-010 with mock API + + Pattern detected: 2 of 4 blockers involve external parties. Consider whether + your execution plan has too many external dependencies. + +/blockers resource +--> Resource Blockers: 1 item + impl-005 | Hire freelance designer + Blocker: Budget not approved for $3K design contract + Duration: 12 days + Suggested resolution: Reallocate from underutilized budget line, negotiate + phased payment, or reduce scope to essential deliverables only. + Route: /apply resource-allocation or /diagnose operations + +/blockers motivation +--> Motivation Blockers: 1 item + impl-009 | Document onboarding process + Blocker: No explicit blocker stated. Stalled 17 days at 0%. + Analysis: This item has been in not-started status since creation despite + no resource, knowledge, dependency, or external constraint. The most likely + blocker is avoidance -- the task feels tedious or overwhelming relative to + higher-energy work. + Route: Apply eisenhower-matrix to confirm priority. If priority is confirmed, + break into 3 sub-tasks of 30 minutes each. If Stoic mode is active, examine + which of the Seven Functions of the Mind is failing here. +``` + +### Related Commands + +- `/track blocked` -- Quick view of blocked items without deep analysis +- `/progress [item-id] [%] [note]` -- Update an item after resolving its blocker +- `/diagnose [area]` -- Run a diagnostic suggested by blocker analysis +- `/apply [skill]` -- Apply a skill suggested by blocker analysis +- `/check-in` -- Full accountability review including blocker identification + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/blockers` (no blocked items) | `No blocked or stalled items. All active implementation items are progressing. Run /track to see current status.` | +| `/blockers creativity` | `Unknown blocker category "creativity". Valid categories: resource, knowledge, dependency, motivation, external.` | + +--- + +## `/check-in` + +### Description + +Initiates the weekly accountability review -- the core ritual of the implementation tracking system. The check-in walks through every active implementation item systematically, records progress updates, identifies blockers, detects stalls, rebalances priorities, and persists all changes to memory. A complete check-in takes 10-20 minutes depending on the number of active items. The system guides the conversation; the entrepreneur provides honest status updates. + +This command should be run weekly. If more than 14 days elapse since the last check-in, the system notes the gap and adjusts its expectations accordingly -- longer gaps mean more items may have drifted, and the check-in will be more thorough. + +### Syntax + +``` +/check-in +``` + +### Parameters + +This command takes no parameters. The check-in protocol is fully guided. + +### Examples + +``` +/check-in +--> Weekly Check-In | Last check-in: Apr 08 (7 days ago) + Active items: 10 (3 not-started, 5 in-progress, 2 blocked) + + Phase 1: Status Sweep + [Table of all active items with current progress and deadline proximity] + + Phase 2: Progress Updates + Starting with items closest to deadline... + + impl-002 | Validate pricing with 10 prospects (due: Apr 10, 2 days) + Current progress: 70% + --> What progress have you made since Apr 08? + [Entrepreneur responds] + --> Recorded: 90%. Note: "8 of 10 interviews complete, 2 scheduled for tomorrow." + + impl-001 | Redesign BMC for B2B pivot (due: Apr 15, 7 days) + Current progress: 40% + --> What progress have you made since Apr 08? + [Entrepreneur responds] + ... + + Phase 3: Blocker Identification + impl-005 has been at 10% for 14 days. + --> What is preventing progress on "Hire freelance designer"? + [Entrepreneur responds] + --> Blocker categorized: resource (budget). Suggested route: /diagnose operations + + Phase 4: Priority Rebalancing + Recommended focus for next week: + 1. impl-002 -- Complete pricing validation (due in 2 days) + 2. impl-001 -- Advance BMC redesign past 50% (due in 7 days) + 3. impl-005 -- Resolve budget blocker to unblock design work + + Phase 5: Summary + Items updated: 8 + New blockers identified: 1 + Items completed since last check-in: 0 + Check-in saved to memory. + +/check-in (with Stoic mode active) +--> Weekly Check-In | Stoic Reflection Enabled + + [Standard phases 1-4, plus Stoic prompts:] + + Dichotomy of Control: + Of your 2 blocked items, which blockers are within your control? + - impl-005 (budget): Partially within control -- you can reallocate or negotiate + - impl-008 (partner API): Outside your control -- focus energy elsewhere + + Premeditatio Malorum: + Your top priority (impl-002, due in 2 days) -- what could prevent completion? + Have you prepared for a scenario where the last 2 interviews cancel? + + Reflection: "Are any of your stalled items stalled because of fear rather + than circumstance? Name the fear, and it loses half its power." + +/check-in (14+ days since last) +--> Weekly Check-In | Gap Detected: 18 days since last check-in (Mar 20) + Extended review mode: some items may have changed significantly. + [Proceeds with standard protocol but asks for more detailed updates] +``` + +### Related Commands + +- `/track` -- Quick status view without the full check-in protocol +- `/progress [item-id] [%] [note]` -- Update a single item outside the check-in cycle +- `/blockers` -- Deep blocker analysis if the check-in surfaces many blockers + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/check-in` (no items) | `No active implementation items to review. Items are created when playbooks, skills, or diagnostics produce actionable recommendations. Run /track to confirm.` | +| `/check-in` (already run today) | `A check-in was already completed today (Apr 15). Run /track to view current status, or /progress to update individual items.` | diff --git a/plugins/foreman/content/commands/language-command.md b/plugins/foreman/content/commands/language-command.md new file mode 100644 index 0000000..0f13b48 --- /dev/null +++ b/plugins/foreman/content/commands/language-command.md @@ -0,0 +1,227 @@ +--- +name: "language-mode-commands" +description: "Sets the output language for all system responses. Supports any language the underlying model can produce fluently. Persists across sessions." +category: "meta" +commands: + - name: "/language" + syntax: "/language [language-name-or-code]" + description: "Sets the output language" + - name: "/language default" + syntax: "/language default" + description: "Resets to English" + - name: "/language status" + syntax: "/language status" + description: "Reports current language setting" +author: "Fatih Guner" +--- + +# /language + +Sets the language for all system outputs. Every response — skill applications, diagnostic questions, playbook instructions, output templates, system messages — switches to the specified language. Internal processing remains in English; the system thinks in English but speaks in the target language. + +--- + +## /language [language] + +### Description + +Sets the output language. Accepts full language names (case-insensitive) or ISO 639-1 codes. The change takes effect immediately and persists across sessions. + +### Syntax + +``` +/language [language-name-or-code] +``` + +### Accepted Inputs + +| Input | Resolved Language | +|-------|-------------------| +| `english`, `en`, `default` | English | +| `turkish`, `tr`, `türkçe` | Turkish | +| `spanish`, `es`, `español` | Spanish | +| `french`, `fr`, `français` | French | +| `german`, `de`, `deutsch` | German | +| `portuguese`, `pt`, `português` | Portuguese (Brazilian default) | +| `japanese`, `ja`, `日本語` | Japanese | +| `chinese`, `zh`, `中文` | Chinese (Simplified default) | +| `korean`, `ko`, `한국어` | Korean | +| `arabic`, `ar`, `العربية` | Arabic (MSA) | +| `dutch`, `nl`, `nederlands` | Dutch | +| `italian`, `it`, `italiano` | Italian | +| `russian`, `ru`, `русский` | Russian | +| `hindi`, `hi`, `हिन्दी` | Hindi | +| `pt-br`, `brazilian portuguese` | Portuguese (Brazilian) | +| `pt-pt`, `european portuguese` | Portuguese (European) | +| `zh-tw`, `traditional chinese` | Chinese (Traditional) | +| Any other model-supported language | Attempted — quality depends on model fluency | + +### Examples + +**Example 1: Switch to Turkish** +``` +User: /language turkish +System: Dil Türkçe olarak ayarlandı. Bundan sonraki tüm çıktılar +Türkçe olarak sunulacak. Komut sözdizimi (/apply, /diagnose, /run) +İngilizce kalacaktır. + +İngilizce'ye dönmek için: /language default +``` + +**Example 2: Switch to Spanish** +``` +User: /language es +System: Idioma configurado a español. Todas las respuestas del sistema +se entregarán en español a partir de ahora. La sintaxis de los comandos +(/apply, /diagnose, /run) permanece en inglés. + +Para volver al inglés: /language default +``` + +**Example 3: Switch to Japanese** +``` +User: /language japanese +System: 言語を日本語に設定しました。以降のすべてのシステム出力は日本語で +提供されます。コマンド構文（/apply、/diagnose、/run）は英語のままです。 + +英語に戻すには: /language default +``` + +**Example 4: Skill output in Turkish** +``` +User: /language turkish +System: Dil Türkçe olarak ayarlandı. + +User: /apply porters-five-forces +System: # Porter'ın Beş Gücü Analizi + +Porter'ın Beş Gücü çerçevesi, bir sektördeki rekabet dinamiklerini +beş yapısal güç üzerinden analiz eder... + +## Tedarikçi Gücü +[Türkçe analiz...] + +## Alıcı Gücü +[Türkçe analiz...] + +... +``` + +**Example 5: Combined with Stoic mode** +``` +User: /stoic on +System: Stoic mode active... + +User: /language turkish +System: Dil Türkçe olarak ayarlandı. Stoacı mod aktif durumda — +tüm Stoacı yansımalar da Türkçe olarak sunulacak. + +User: /apply swot-pest-analysis +System: # SWOT ve PEST Analizi +[Türkçe analiz...] + +## Stoacı Yansıma +Bu analiz, kontrolünüz dahilindeki iç güçleri ve zayıflıkları, +kontrolünüz dışındaki dış fırsatları ve tehditleri birbirinden ayırır. +Epiktetos'un hatırlattığı gibi: "Bizi rahatsız eden şeyler değil, +şeyler hakkındaki yargılarımızdır." +— Epictetus, Discourses 2.5.4 +``` + +--- + +## /language default + +### Description + +Resets the output language to English. Equivalent to `/language english` or `/language en`. + +### Syntax + +``` +/language default +``` + +### Confirmation + +``` +User: /language default +System: Language reset to English. All outputs will be delivered in English. +``` + +--- + +## /language status + +### Description + +Reports the current language setting, when it was set, and what it affects. + +### Syntax + +``` +/language status +``` + +### Output Examples + +**When non-English language is active:** +``` +User: /language status +System: Mevcut dil: Türkçe (tr) +Ayarlanma tarihi: 2026-03-29 +Aktif modlar: Solo Mode + Stoic Mode + Turkish + +Etkiler: + - Tüm skill çıktıları Türkçe + - Tüm diagnostik soruları Türkçe + - Tüm playbook adımları Türkçe + - Tüm output template'ler Türkçe + - Sistem mesajları Türkçe + - Komut sözdizimi İngilizce kalır + +Değiştirmek için: /language [dil] veya /language default +``` + +**When English (default):** +``` +User: /language status +System: Current language: English (default) + +To change: /language [language-name-or-code] +Supported: Any language the model speaks fluently. +Examples: /language turkish, /language es, /language 日本語 +``` + +--- + +## Error Handling + +| Input | Response | +|-------|----------| +| `/language` (no argument) | "Usage: /language [language-name-or-code]. Examples: /language turkish, /language es, /language default. Use /language status to see current setting." | +| `/language xyz123` (unrecognized) | "Language 'xyz123' not recognized. Use a language name (e.g., 'turkish', 'french') or ISO code (e.g., 'tr', 'fr'). Use /language default for English." | +| `/language english` when already English | "Language is already set to English." | +| `/language turkish` when already Turkish | "Dil zaten Türkçe olarak ayarlı." (responds in current language) | + +--- + +## Memory Integration + +| Operation | Memory Layer | Field | +|-----------|-------------|-------| +| Set language | identity | `language: "tr"` (ISO 639-1 code) | +| Set language | identity | `language_set_date: "2026-03-29"` | +| Reset to default | identity | `language: "en"` | +| Session start | session | Orchestrator reads `identity.language`, activates if not "en" | + +Language persists across sessions. Once `/language turkish` is invoked, every future session starts in Turkish until the entrepreneur runs `/language default` or `/language english`. + +--- + +## Related Commands + +- `/solo` — Filters WHAT content appears. Combines with language mode. +- `/stoic on` — Adds philosophical depth. Stoic reflections translate to target language. +- `/context` — Shows full context including language setting. +- `/help meta` — Lists all meta commands. diff --git a/plugins/foreman/content/commands/language.md b/plugins/foreman/content/commands/language.md new file mode 100644 index 0000000..955b4fa --- /dev/null +++ b/plugins/foreman/content/commands/language.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /language command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /language + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/language-command.md and execute only /language with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/commands/memory-commands.md b/plugins/foreman/content/commands/memory-commands.md new file mode 100644 index 0000000..32add1c --- /dev/null +++ b/plugins/foreman/content/commands/memory-commands.md @@ -0,0 +1,522 @@ +--- +name: "memory-commands" +description: "Commands for viewing, updating, and managing the entrepreneur's persistent context — identity, company profile, decision history, follow-ups, and session data. These commands read from and write to the five-layer memory system." +category: "memory" +commands: + - name: "/context" + syntax: "/context [layer]" + description: "Display the entrepreneur's current context from identity, company, and active memory layers." + - name: "/update company" + syntax: "/update company" + description: "Interactive update of the company profile — stage, metrics, sector, and challenges." + - name: "/update identity" + syntax: "/update identity" + description: "Interactive update of the entrepreneur's personal profile." + - name: "/history" + syntax: "/history [type] [--last n]" + description: "Show past diagnostics, decisions, and skill applications from the history layer." + - name: "/decisions" + syntax: "/decisions [filter]" + description: "List pending, overdue, and completed decisions." + - name: "/follow-ups" + syntax: "/follow-ups [filter]" + description: "Show upcoming and overdue follow-up items." + - name: "/forget" + syntax: "/forget [type] [identifier]" + description: "Delete a specific memory entry with confirmation." + - name: "/reset" + syntax: "/reset" + description: "Full memory wipe across all layers, requiring double confirmation." +author: "Fatih Guner" +--- + +> Runtime note: These layers describe conceptual and legacy memory. Current writes use the versioned state and migration protocol in `.claude/RUNTIME.md`. Do not create a second active store. + +# Memory Commands + +## `/context` + +### Description + +Displays the entrepreneur's current context as stored in memory. Without arguments, returns a consolidated view combining identity (who you are), company (stage, sector, metrics, challenges), and active items (running playbooks, pending decisions, upcoming follow-ups). With a layer argument, returns only that specific layer. This command is read-only — it never modifies state. + +### Syntax + +``` +/context [layer] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `layer` | No | string | all | Specific memory layer: `identity`, `company`, `active` | + +### Examples + +``` +/context +→ Identity: + Name: Sarah Chen + Role: CEO & Co-founder + Experience: 8 years product management, 2 years as founder + Company: + Name: Relay Health + Sector: B2B healthtech + Stage: early-traction + MRR: $42,000 + Team size: 12 + Challenges: churn rate rising, Series A timeline pressure + Active: + Playbook: fundraising-playbook (Step 4 of 8) + Pending decisions: 2 (VP Engineering hire, pricing model change) + Overdue follow-ups: 1 (investor update to Sequoia) + +/context company +→ Company: + Name: Relay Health + Sector: B2B healthtech + Stage: early-traction + MRR: $42,000 + Burn rate: $85,000/month + Runway: 11 months + Team size: 12 + Challenges: churn rate rising, Series A timeline pressure + +/context identity +→ Identity: + Name: Sarah Chen + Role: CEO & Co-founder + Experience: 8 years product management, 2 years as founder + Strengths: product intuition, stakeholder communication + Development areas: financial modeling, board management +``` + +### Related Commands + +- `/update company` — Modify the company profile +- `/update identity` — Modify the personal profile +- `/history` — View past actions rather than current state + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/context session` | `Unknown layer "session". Available layers: identity, company, active. Session data is internal and not directly viewable.` | +| `/context` (empty memory) | `No context found. Run /update identity and /update company to set up your profile.` | + +--- + +## `/update company` + +### Description + +Launches an interactive company profile update. The system walks through each field — company name, sector, stage, key metrics (MRR, burn rate, runway, team size), current challenges, and strategic priorities — prompting for new values or confirmation of existing ones. Fields can be skipped to retain their current values. Changes are persisted immediately to the company memory layer. + +### Syntax + +``` +/update company +``` + +### Parameters + +This command takes no parameters. All updates are collected interactively. + +### Examples + +``` +/update company +→ Updating company profile... + Company name [Relay Health]: (enter to keep) + Sector [B2B healthtech]: (enter to keep) + Stage [early-traction]: growth + MRR [$42,000]: $78,000 + Burn rate [$85,000/month]: $110,000/month + Team size [12]: 18 + Current challenges [churn rate rising, Series A timeline pressure]: scaling engineering, enterprise sales motion + Updated. Stage changed from early-traction to growth — skill recommendations will adjust accordingly. + +/update company +→ Updating company profile... + Company name []: DataForge + Sector []: B2B SaaS, developer tools + Stage []: validation + MRR []: $3,200 + Burn rate []: $25,000/month + Team size []: 3 + Current challenges []: finding design partners, unclear pricing + Company profile created. +``` + +### Related Commands + +- `/context company` — View the current company profile +- `/update identity` — Update personal profile alongside company data +- `/apply [skill]` — Skills will use the updated company context + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/update company` (invalid stage input) | `"series-a" is not a recognized stage. Valid stages: idea, validation, early-traction, growth, scale. Please select one.` | +| `/update company` (invalid metric format) | `Could not parse "$42k" as a metric value. Enter a number: e.g., $42,000 or 42000.` | + +--- + +## `/update identity` + +### Description + +Launches an interactive personal profile update. The system walks through the entrepreneur's name, role, experience, strengths, development areas, and working style preferences. This identity data influences how skills are framed and which coaching patterns the system applies. Fields can be skipped to retain existing values. + +### Syntax + +``` +/update identity +``` + +### Parameters + +This command takes no parameters. All updates are collected interactively. + +### Examples + +``` +/update identity +→ Updating identity profile... + Name [Sarah Chen]: (enter to keep) + Role [CEO & Co-founder]: (enter to keep) + Years of experience [10]: (enter to keep) + Background [product management]: product management, design + Strengths [product intuition, stakeholder communication]: (enter to keep) + Development areas [financial modeling, board management]: financial modeling, board management, hiring + Updated. Development areas expanded — relevant skill recommendations will adjust. + +/update identity +→ Updating identity profile... + Name []: Marcus Rivera + Role []: Solo founder & CTO + Years of experience []: 6 + Background []: software engineering, machine learning + Strengths []: technical architecture, rapid prototyping + Development areas []: sales, fundraising, delegation + Identity profile created. +``` + +### Related Commands + +- `/context identity` — View the current identity profile +- `/update company` — Update company profile alongside identity +- `/context` — View the full consolidated context + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/update identity` (session interruption) | `Profile update interrupted. Partial changes saved. Run /update identity again to complete.` | + +--- + +## `/history` + +### Description + +Displays the entrepreneur's action history from the history memory layer. Without arguments, returns a reverse-chronological summary of all recorded events — diagnostics run, skills applied, decisions made, and playbook completions. A type filter narrows to one category. The `--last` flag limits the number of entries returned. + +### Syntax + +``` +/history [type] [--last n] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `type` | No | string | all | Filter by entry type: `diagnostics`, `skills`, `decisions`, `playbooks` | +| `--last` | No | integer | 20 | Number of entries to return | + +### Examples + +``` +/history +→ Recent activity (last 20 entries): + 2026-03-25 skill porters-five-forces applied (stage: early-traction) + 2026-03-24 decision Pricing model change — decided: usage-based + 2026-03-22 playbook fundraising-playbook paused at Step 4 + 2026-03-20 skill swot-pest-analysis applied (stage: early-traction) + 2026-03-18 diagnostic revenue-diagnosis completed → recommended: pricing-diagnosis + ... + +/history decisions +→ Decision history: + 2026-03-24 Pricing model change — decided: usage-based + 2026-03-15 VP Engineering hire — decided: defer 60 days + 2026-03-08 Market expansion — decided: vertical-first, horizontal later + 2026-02-28 Product roadmap Q2 — decided: core platform stability over new features + +/history skills --last 5 +→ Last 5 skill applications: + 2026-03-25 porters-five-forces (stage: early-traction) + 2026-03-20 swot-pest-analysis (stage: early-traction) + 2026-03-14 business-model-canvas (stage: early-traction) + 2026-03-10 unit-economics (stage: early-traction) + 2026-03-05 net-promoter-score (stage: early-traction) + +/history diagnostics --last 3 +→ Last 3 diagnostics: + 2026-03-18 revenue-diagnosis → root cause: churn-driven revenue loss + 2026-03-10 fundraising-diagnosis → root cause: narrative gap, not traction gap + 2026-02-25 team-dysfunction-diagnosis → root cause: unclear engineering ownership +``` + +### Related Commands + +- `/context` — View current state rather than past actions +- `/decisions` — Focused view of decisions with pending/overdue status +- `/forget [item]` — Delete a specific history entry + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/history metrics` | `Unknown type "metrics". Available types: diagnostics, skills, decisions, playbooks.` | +| `/history --last 0` | `--last must be a positive integer. Usage: /history [type] [--last n].` | +| `/history` (empty history) | `No history found. Run /apply, /diagnose, or /run to start building your history.` | + +--- + +## `/decisions` + +### Description + +Lists decisions tracked in memory, organized by status. Without arguments, shows pending decisions — those recorded but not yet resolved. Filters narrow to a specific status. Each decision entry shows the decision topic, date recorded, current status, and deadline if set. + +### Syntax + +``` +/decisions [filter] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `filter` | No | string | `pending` | Decision status filter: `pending`, `overdue`, `completed`, `all` | + +### Examples + +``` +/decisions +→ 2 pending decisions: + 1. VP Engineering hire — recorded 2026-03-15, deadline 2026-04-15 + Context: Deferred 60 days pending Series A clarity + 2. Pricing model change — recorded 2026-03-20, deadline 2026-04-01 + Context: Usage-based vs. seat-based, customer interviews in progress + +/decisions overdue +→ 1 overdue decision: + 1. Partner channel strategy — recorded 2026-02-10, deadline 2026-03-10 (16 days overdue) + Context: AWS Marketplace vs. direct sales, waiting on partner terms + +/decisions completed +→ 4 completed decisions: + 2026-03-24 Pricing model change — decided: usage-based + 2026-03-08 Market expansion — decided: vertical-first + 2026-02-28 Product roadmap Q2 — decided: stability over features + 2026-02-15 Office lease — decided: remain remote through 2026 + +/decisions all +→ 7 total decisions (2 pending, 1 overdue, 4 completed) + [Combined listing of all decisions across all statuses] +``` + +### Related Commands + +- `/history decisions` — View the full decision history log +- `/follow-ups` — See follow-up items that may relate to pending decisions +- `/forget decision [identifier]` — Remove a decision from tracking + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/decisions active` | `Unknown filter "active". Available filters: pending, overdue, completed, all.` | +| `/decisions` (no decisions tracked) | `No decisions tracked. Decisions are recorded when diagnostics or playbooks surface decision points, or when you log them during skill application.` | + +--- + +## `/follow-ups` + +### Description + +Lists follow-up items — actions the entrepreneur committed to during diagnostics, playbooks, or skill applications. Without arguments, shows all upcoming follow-ups ordered by date. The `overdue` filter isolates items past their deadline. + +### Syntax + +``` +/follow-ups [filter] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `filter` | No | string | `upcoming` | Filter: `upcoming`, `overdue`, `all` | + +### Examples + +``` +/follow-ups +→ 3 upcoming follow-ups: + 1. Send investor update to Sequoia — due 2026-03-28 + Source: fundraising-playbook, Step 3 + 2. Schedule customer interviews for pricing validation — due 2026-04-01 + Source: pricing-diagnosis + 3. Review VP Engineering candidate pipeline — due 2026-04-15 + Source: decision: VP Engineering hire + +/follow-ups overdue +→ 1 overdue follow-up: + 1. Finalize partner channel terms with AWS — due 2026-03-10 (16 days overdue) + Source: decision: partner channel strategy + +/follow-ups all +→ 4 follow-ups (3 upcoming, 1 overdue) + [Combined listing ordered by due date] +``` + +### Related Commands + +- `/decisions` — View the decisions that generated these follow-ups +- `/context active` — See all active items including follow-ups +- `/forget` — Remove a follow-up that is no longer relevant + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/follow-ups completed` | `Unknown filter "completed". Available filters: upcoming, overdue, all. Completed follow-ups move to /history.` | +| `/follow-ups` (none tracked) | `No follow-ups tracked. Follow-ups are created during diagnostics, playbooks, and skill applications when action items are identified.` | + +--- + +## `/forget` + +### Description + +Deletes a specific entry from memory. Requires both the entry type and an identifier — either a name or a date — to target the correct record. The command displays the matched entry and asks for explicit confirmation before deletion. Deletion is permanent and cannot be undone. + +### Syntax + +``` +/forget [type] [identifier] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `type` | Yes | string | -- | Entry type: `decision`, `diagnostic`, `skill`, `follow-up`, `playbook` | +| `identifier` | Yes | string | -- | Entry name (in quotes if multi-word) or date (YYYY-MM-DD) | + +### Examples + +``` +/forget decision "VP hire" +→ Found: Decision — "VP Engineering hire" (recorded 2026-03-15) + This will permanently delete this decision and its associated follow-ups. + Confirm deletion? [y/n] + > y + Deleted. + +/forget diagnostic 2026-03-18 +→ Found: Diagnostic — revenue-diagnosis (completed 2026-03-18) + This will permanently delete this diagnostic result from history. + Confirm deletion? [y/n] + > y + Deleted. + +/forget follow-up "investor update" +→ Found: Follow-up — "Send investor update to Sequoia" (due 2026-03-28) + Confirm deletion? [y/n] + > n + Cancelled. No changes made. + +/forget skill 2026-03-25 +→ Found: Skill application — porters-five-forces (applied 2026-03-25) + This will permanently delete this analysis result from history. + Confirm deletion? [y/n] + > y + Deleted. +``` + +### Related Commands + +- `/history` — Review entries before deciding what to delete +- `/decisions` — Review decisions before deleting +- `/reset` — Delete everything instead of individual entries + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/forget` | `Missing type and identifier. Usage: /forget [type] [identifier]. Types: decision, diagnostic, skill, follow-up, playbook.` | +| `/forget decision` | `Missing identifier. Usage: /forget decision [name or date]. Example: /forget decision "VP hire" or /forget decision 2026-03-15.` | +| `/forget decision "board meeting"` | `No decision found matching "board meeting". Run /decisions all to see tracked decisions.` | +| `/forget metric "MRR"` | `Unknown type "metric". Available types: decision, diagnostic, skill, follow-up, playbook. Company profile fields are updated via /update company.` | + +--- + +## `/reset` + +### Description + +Performs a full memory wipe across all five layers — identity, company, history, active, and session. This is a destructive, irreversible operation. The command requires double confirmation: first acknowledging the scope of deletion, then entering a confirmation phrase. After reset, the system returns to a blank-slate state as though no entrepreneur context has ever been set. + +### Syntax + +``` +/reset +``` + +### Parameters + +This command takes no parameters. + +### Examples + +``` +/reset +→ WARNING: This will permanently delete ALL memory across all layers: + - Identity profile (name, role, experience, strengths) + - Company profile (stage, metrics, challenges) + - Full history (diagnostics, skills, decisions, playbooks) + - Active items (running playbooks, pending decisions, follow-ups) + - Session data + + This action cannot be undone. + Type "RESET ALL" to confirm: RESET ALL + Memory cleared. All layers wiped. Run /update identity and /update company to start fresh. + +/reset +→ WARNING: This will permanently delete ALL memory across all layers: + ... + Type "RESET ALL" to confirm: cancel + Reset cancelled. No changes made. +``` + +### Related Commands + +- `/forget [item]` — Delete individual entries instead of everything +- `/context` — Review what exists in memory before resetting +- `/update company` — Rebuild company profile after a reset +- `/update identity` — Rebuild identity profile after a reset + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/reset` (confirmation mismatch) | `Confirmation phrase did not match. Expected "RESET ALL". Reset cancelled. No changes made.` | +| `/reset` (empty memory) | `Memory is already empty. Nothing to reset.` | diff --git a/plugins/foreman/content/commands/meta-commands.md b/plugins/foreman/content/commands/meta-commands.md new file mode 100644 index 0000000..11c2fb5 --- /dev/null +++ b/plugins/foreman/content/commands/meta-commands.md @@ -0,0 +1,169 @@ +# Meta Commands + +System information, configuration, and feedback -- operations on Foreman itself. + +--- + +## `/help` + +Display all commands grouped by category, or detailed help for one category. + +**Syntax:** `/help [category]` + +| Parameter | Required | Values | Description | +|-----------|----------|--------|-------------| +| `category` | No | `playbook`, `output`, `meta`, `memory`, `skill`, `diagnostic` | Filter to one category. Omit for all. | + +**Examples:** +``` +> /help +Playbook: /status /skip /back /pause /abort | Output: /format /export /compare +Meta: /help /about /version /feedback /stage | Memory: /recall /forget /memory +Skill: /run /list | Diagnostic: /diagnose /symptoms +> /help playbook +/status — active state /skip — skip step /back — re-run previous +/pause — save to memory /abort — cancel (double confirm) +> /help memory +/recall — retrieve stored analysis /forget — remove from memory +/memory [layer] — show contents (active, history, context, stage, profile) +``` +**Related:** `/about`, `/version` +**Errors:** `Unknown category: "". Available: playbook, output, meta, memory, skill, diagnostic.` + +--- + +## `/about` + +Display Foreman project info: purpose, architecture, source links. + +**Syntax:** `/about` | **Parameters:** None. + +**Examples:** +``` +> /about +Foreman — AI-Powered Strategic Advisor for Entrepreneurs +Open-source, framework-driven guidance via skills, agents, hooks, and memory. +Input --> Diagnostics --> Hooks --> Agent --> Skills --> Template --> Memory +Adapts to stage (idea through scale). Context accumulates across sessions. +foreman.sh | github.com/anthropics/foreman | License: TBD +> /about --verbose +Unknown flag: "--verbose". /about takes no parameters. +``` +**Related:** `/version`, `/help` | **Errors:** Any argument: `Unknown flag. /about takes no parameters.` + +--- + +## `/version` + +Show system version and component counts. + +**Syntax:** `/version` | **Parameters:** None. + +**Examples:** +``` +> /version +Foreman v0.1.0 +Skills: 158 Templates: 48 Diagnostics: 20 Playbooks: 20 +Hooks: 16 Agents: 6 Memory layers: 5 +> /version skills +Unknown argument: "skills". /version takes no parameters. Try /help skill. +``` +**Related:** `/about`, `/help` | **Errors:** Any argument: `Unknown argument. /version takes no parameters.` + +--- + +## `/feedback [message]` + +Submit feedback about a skill, template, diagnostic, or the system. Logged with session context for project improvement. + +**Syntax:** `/feedback ""` + +| Parameter | Required | Description | +|-----------|----------|-------------| +| `message` | Yes | Free text. Reference the skill or feature by name. Quote the message. | + +**Examples:** +``` +> /feedback "SWOT skill needs more B2B SaaS examples." +Logged. Ref: FB-20260326-001. Context: stage=early-traction, skill=swot-analysis +> /feedback "Pricing diagnosis missed freemium. Treated free tier as trial." +Logged. Ref: FB-20260326-002. Context: stage=growth, skill=pricing-strategy +> /feedback "Board template: zero edits for March meeting." +Logged. Ref: FB-20260326-003. Context: stage=growth, template=board/strategic-summary +> /feedback +Usage: /feedback "". Reference the specific skill or feature by name. +``` +**Related:** `/about`, `/version` +**Errors:** No message: `Usage: /feedback "".` Empty: `Feedback cannot be empty.` + +--- + +## `/sector` + +Show, set, or deactivate the active industry pack. Industry packs add sector-specific benchmarks, skill overlays, diagnostic rules, and template adaptations. Setting a sector updates `memory.company.sector` and loads the matching pack automatically. + +**Syntax:** `/sector [name|list|off]` + +| Parameter | Required | Values | Description | +|-----------|----------|--------|-------------| +| `name` | No | `saas`, `marketplace`, `e-commerce`, `fintech`, `ai-ml`, `healthtech`, `edtech`, `d2c-consumer`, `agency-consulting` | Sector to activate. Omit to view current. | +| `list` | No | literal `list` | Show all available industry packs. | +| `off` | No | literal `off` | Deactivate sector-specific overlays. | + +**Examples:** +``` +> /sector +Current sector: saas (set 2026-02-10) +Industry pack: saas — benchmarks, skill overlays, diagnostic rules, templates active. +> /sector fintech +Updated: fintech (was saas). Fintech benchmarks, regulatory diagnostic rules, +and compliance template sections now active across all agents. +> /sector list +Available industry packs (9): + saas, marketplace, e-commerce, fintech, ai-ml, healthtech, edtech, + d2c-consumer, agency-consulting +Each pack: benchmarks + skill overlays + diagnostic rules + templates. +> /sector off +Sector deactivated (was fintech). Generic benchmarks and diagnostics restored. +> /sector crypto +Unknown sector: "crypto". Available: saas, marketplace, e-commerce, fintech, +ai-ml, healthtech, edtech, d2c-consumer, agency-consulting. +Hint: if your sector is not listed, the closest match may still add value. +``` + +**Memory integration:** Setting a sector writes to `memory.company.sector`. The value persists across sessions. The orchestrator reads `company.sector` at session start and loads the matching industry pack automatically. + +**Related:** `/stage`, `/about`, `/version` +**Errors:** Unknown sector: `Unknown sector: "". Available: saas, marketplace, e-commerce, fintech, ai-ml, healthtech, edtech, d2c-consumer, agency-consulting.` Already set: `Already set to . No change.` No sector active (on `/sector` without args): `No sector set. Use /sector to activate an industry pack.` + +--- + +## `/stage` + +Show or change company stage. Governs skill selection, playbook filtering, framework adaptation. Five stages: `idea`, `validation`, `early-traction`, `growth`, `scale`. Past analyses retain their original stage. + +**Syntax:** `/stage [new-stage]` + +| Parameter | Required | Values | Description | +|-----------|----------|--------|-------------| +| `new-stage` | No | `idea`, `validation`, `early-traction`, `growth`, `scale` | Stage to set. Omit to view current. | + +**Examples:** +``` +> /stage +Current stage: early-traction (set 2026-01-15) +> /stage growth +Updated: growth (was early-traction). Unit Economics shifts to LTV/CAC. +Hiring/scaling playbooks available. Fundraising framed for Series A/B. +> /stage idea +Updated: idea (was growth). Validation prioritized. Financial modeling +simplified. Team playbooks focus on co-founder dynamics. +> /stage series-a +Unknown stage: "series-a". Available: idea, validation, early-traction, growth, scale. +Hint: after a Series A, "growth" is likely appropriate. +> /stage validation +Updated: validation (was idea). Customer discovery prioritized. PMF assessment +available. Lean Canvas emphasized over full BMC. +``` +**Related:** `/status`, `/version`, `/help` +**Errors:** Unknown: `Unknown stage. Available: idea, validation, early-traction, growth, scale.` Same: `Already set to . No change.` diff --git a/plugins/foreman/content/commands/navigation-commands.md b/plugins/foreman/content/commands/navigation-commands.md new file mode 100644 index 0000000..0959d6a --- /dev/null +++ b/plugins/foreman/content/commands/navigation-commands.md @@ -0,0 +1,403 @@ +--- +name: "navigation-commands" +description: "Commands for exploring and discovering Foreman's skill library, output templates, playbooks, diagnostics, and hooks. These commands produce read-only listings and summaries — they never modify state or trigger execution." +category: "navigation" +commands: + - name: "/skills" + syntax: "/skills [category] [--stage stage] [--complexity level]" + description: "List all skills, optionally filtered by category, company stage, or complexity." + - name: "/skill" + syntax: "/skill [name]" + description: "Display a single skill's summary, including description, stage, complexity, and related skills." + - name: "/templates" + syntax: "/templates [audience] [--format type]" + description: "List all output templates, optionally filtered by audience or document format." + - name: "/playbooks" + syntax: "/playbooks [--stage stage]" + description: "List all playbooks, optionally filtered by company stage." + - name: "/diagnostics" + syntax: "/diagnostics" + description: "List all available diagnostics with their target problem domains." + - name: "/hooks" + syntax: "/hooks" + description: "List all hooks with their trigger patterns and routing destinations." + - name: "/search" + syntax: "/search [query] [--in layer]" + description: "Full-text search across all system layers or a specific layer." +author: "Fatih Guner" +--- + +# Navigation Commands + +## `/skills` + +### Description + +Lists every skill registered in the system. Without arguments, returns a grouped summary across all 14 categories. With a category argument, returns only skills in that category. Stage and complexity flags narrow results further. Output includes skill name, one-line description, stage tags, and complexity level. + +### Syntax + +``` +/skills [category] [--stage stage] [--complexity level] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `category` | No | string | all | Category slug: `frameworks`, `leadership`, `writing`, `ai-leadership`, `game-theory`, `stoic`, `storytelling`, `negotiation`, `people`, `creative`, `thinking`, `decisions` | +| `--stage` | No | string | all | Filter by company stage: `idea`, `validation`, `early-traction`, `growth`, `scale` | +| `--complexity` | No | string | all | Filter by complexity: `basic`, `intermediate`, `advanced` | + +### Examples + +``` +/skills +→ 158 skills across 14 categories + frameworks (50) | leadership (28) | writing (6) | ai-leadership (9) | ... + +/skills frameworks +→ 50 skills in "frameworks" + balanced-scorecard | intermediate | validation, growth, scale + blue-ocean-strategy | advanced | validation, growth + business-model-canvas | basic | idea, validation, early-traction + ... + +/skills --stage growth +→ 94 skills applicable to "growth" stage + (filtered list across all categories) + +/skills leadership --complexity advanced +→ 8 skills in "leadership" at advanced complexity + senior-leadership-transition | advanced | growth, scale + strategic-thinking-and-alignment | advanced | growth, scale + ... +``` + +### Related Commands + +- `/skill [name]` — View full detail on a specific skill +- `/search [query]` — Find skills by keyword when the name is unknown + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/skills nonexistent-category` | `Unknown category "nonexistent-category". Available categories: frameworks, leadership, writing, ai-leadership, game-theory, stoic, storytelling, negotiation, people, creative, thinking, decisions.` | +| `/skills --stage pre-seed` | `Unknown stage "pre-seed". Valid stages: idea, validation, early-traction, growth, scale.` | + +--- + +## `/skill` + +### Description + +Displays the summary card for a single skill, including its name, description, category, stage applicability, complexity, tags, and related skills. Does not render the full skill body — use this for quick reference before deciding whether to apply a skill. + +### Syntax + +``` +/skill [name] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `name` | Yes | string | -- | Skill identifier in kebab-case (e.g., `porters-five-forces`) | + +### Examples + +``` +/skill porters-five-forces +→ porters-five-forces + Category: frameworks + Complexity: advanced + Stages: validation, early-traction, growth, scale + Description: Analyzes five competitive forces that shape industry profitability... + Related: blue-ocean-strategy, swot-pest-analysis, growth-share-matrix + +/skill business-model-canvas +→ business-model-canvas + Category: frameworks + Complexity: basic + Stages: idea, validation, early-traction + Description: Maps the nine building blocks of a business model... + Related: lean-in, doblin-ten-types, four-ps-marketing + +/skill stoic-emotional-mastery +→ stoic-emotional-mastery + Category: stoic + Complexity: intermediate + Stages: idea, validation, early-traction, growth, scale + Description: Applies Stoic techniques for emotional regulation under pressure... + Related: stoic-control-and-clarity, emotional-intelligence, leader-resilience-and-wellbeing +``` + +### Related Commands + +- `/skills` — Browse all skills by category +- `/apply [name]` — Execute this skill against your current context + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/skill` | `Missing skill name. Usage: /skill [name]. Run /skills to browse available skills.` | +| `/skill porters-five` | `No skill found matching "porters-five". Did you mean: porters-five-forces? Run /search "porters" to explore.` | + +--- + +## `/templates` + +### Description + +Lists all output templates organized by audience. Without arguments, returns a count and grouped listing across all five audiences (investor, board, team, self, client). With an audience argument, shows only templates for that audience. The format flag filters by document type when specified. + +### Syntax + +``` +/templates [audience] [--format type] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `audience` | No | string | all | Target audience: `investor`, `board`, `team`, `self`, `client` | +| `--format` | No | string | all | Document format: `memo`, `one-pager`, `email`, `checklist`, `brief`, `template` | + +### Examples + +``` +/templates +→ 48 output templates across 5 audiences + investor (10) | board (7) | team (13) | client (8) | self (10) + +/templates investor +→ 10 templates for "investor" audience + cap-table-summary | competitive-landscape-brief | decision-rationale-memo + due-diligence-checklist | exit-scenario-analysis | fundraising-deck-outline + investor-update-email | market-opportunity-summary | strategic-analysis-one-pager + unit-economics-snapshot + +/templates team --format template +→ Templates for "team" audience filtered by "template" format + feedback-360-template | meeting-notes-template | one-on-one-template + retrospective-template | role-description-template +``` + +### Related Commands + +- `/output [template] [audience]` — Generate a formatted output using a template +- `/skills` — Browse the skills whose results these templates format + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/templates shareholders` | `Unknown audience "shareholders". Available audiences: investor, board, team, self, client.` | +| `/templates --format slide-deck` | `Unknown format "slide-deck". Available formats: memo, one-pager, email, checklist, brief, template.` | + +--- + +## `/playbooks` + +### Description + +Lists all playbooks with their names, descriptions, and applicable stages. Playbooks are multi-step recipes that chain several skills into a guided workflow. The stage flag filters playbooks relevant to a specific company stage. + +### Syntax + +``` +/playbooks [--stage stage] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `--stage` | No | string | all | Filter by company stage: `idea`, `validation`, `early-traction`, `growth`, `scale` | + +### Examples + +``` +/playbooks +→ 20 playbooks available + acquisition-evaluation-playbook | board-formation-playbook | competitive-response-playbook + crisis-playbook | first-100-customers-playbook | founder-transition-playbook + fundraising-playbook | innovation-sprint-playbook | ... + +/playbooks --stage validation +→ 8 playbooks applicable to "validation" stage + first-100-customers-playbook | launch-playbook | pivot-playbook + pricing-strategy-playbook | product-market-fit-playbook | ... + +/playbooks --stage scale +→ 6 playbooks applicable to "scale" stage + acquisition-evaluation-playbook | board-formation-playbook + founder-transition-playbook | international-expansion-playbook | ... +``` + +### Related Commands + +- `/run [playbook]` — Start executing a playbook +- `/resume` — Continue a paused playbook + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/playbooks --stage seed` | `Unknown stage "seed". Valid stages: idea, validation, early-traction, growth, scale.` | + +--- + +## `/diagnostics` + +### Description + +Lists all diagnostics with their target problem domains. Diagnostics are triage flows that identify the root cause behind an entrepreneur's stated problem. Each diagnostic maps to one or more skills and playbooks it may route to after analysis. + +### Syntax + +``` +/diagnostics +``` + +### Parameters + +This command takes no parameters. + +### Examples + +``` +/diagnostics +→ 20 diagnostics available + cofounder-conflict-diagnosis — Interpersonal and equity disputes between cofounders + communication-breakdown-diagnosis — Internal communication failures and misalignment + competitive-threat-diagnosis — Emerging or intensifying competitive pressure + culture-erosion-diagnosis — Declining team culture, values drift + customer-churn-diagnosis — Rising customer attrition, retention failures + decision-paralysis-diagnosis — Inability to commit to strategic decisions + fundraising-diagnosis — Capital-raising obstacles and investor relations + growth-stall-diagnosis — Revenue or user growth plateaus + ... +``` + +### Related Commands + +- `/diagnose [area]` — Run a specific diagnostic +- `/hooks` — See how natural-language input maps to these diagnostics + +### Error Handling + +This command has no failure modes — it always returns the full diagnostic listing. + +--- + +## `/hooks` + +### Description + +Lists all hooks with their trigger patterns and routing destinations. This command exists for transparency and debugging: it reveals how Foreman interprets natural-language input and routes it to diagnostics, skills, or playbooks. Useful when a hook misroutes and the entrepreneur wants to understand why. + +### Syntax + +``` +/hooks +``` + +### Parameters + +This command takes no parameters. + +### Examples + +``` +/hooks +→ 16 hooks registered + revenue-and-sales-hook + Triggers: "sales are dropping", "revenue is declining", "nobody's buying"... + Routes to: revenue-diagnosis, pricing-diagnosis + + team-hook + Triggers: "my team isn't working", "I need to fire someone", "hiring is broken"... + Routes to: team-dysfunction-diagnosis, hiring-diagnosis + + fundraising-hook + Triggers: "I need funding", "investors aren't interested", "running out of cash"... + Routes to: fundraising-diagnosis, fundraising-playbook + ... +``` + +### Related Commands + +- `/diagnostics` — See the diagnostics that hooks route to +- `/search [query]` — Find specific trigger patterns + +### Error Handling + +This command has no failure modes — it always returns the full hook listing. + +--- + +## `/search` + +### Description + +Performs full-text search across all system layers: skills, templates, diagnostics, playbooks, and hooks. Returns ranked matches with the layer, name, and a snippet showing where the query matched. The `--in` flag restricts the search to a single layer for faster, narrower results. + +### Syntax + +``` +/search [query] [--in layer] +``` + +### Parameters + +| Parameter | Required | Type | Default | Description | +|-----------|----------|------|---------|-------------| +| `query` | Yes | string | -- | Search term or phrase (wrap multi-word queries in quotes) | +| `--in` | No | string | all | Restrict to a single layer: `skills`, `templates`, `diagnostics`, `playbooks`, `hooks` | + +### Examples + +``` +/search "pricing" +→ 12 matches across 4 layers + skill: pricing-strategy-playbook, porters-five-forces, four-ps-marketing + diagnostic: pricing-diagnosis + playbook: pricing-strategy-playbook + template: unit-economics-snapshot + hook: revenue-and-sales-hook + +/search "churn" --in skills +→ 3 skill matches for "churn" + customer-churn-diagnosis (tagged: churn, retention, attrition) + net-promoter-score (mentions churn in anti-patterns) + growth-stall-diagnosis (mentions churn as growth inhibitor) + +/search "fundraising" --in playbooks +→ 1 playbook match for "fundraising" + fundraising-playbook — Multi-step guide to raising a round + +/search "team conflict" +→ 6 matches across 3 layers + skill: thomas-kilmann-conflict, cofounder-conflict-diagnosis + diagnostic: cofounder-conflict-diagnosis, team-dysfunction-diagnosis + hook: team-hook + playbook: team-rebuild-playbook +``` + +### Related Commands + +- `/skills` — Browse by category when search terms are too broad +- `/skill [name]` — View the full summary of a search result + +### Error Handling + +| Input | Error Message | +|-------|---------------| +| `/search` | `Missing search query. Usage: /search [query] [--in layer].` | +| `/search "xyz" --in agents` | `Unknown layer "agents". Searchable layers: skills, templates, diagnostics, playbooks, hooks.` | +| `/search "quantum computing"` | `No matches found for "quantum computing". Try broader terms or check /skills for category browsing.` | diff --git a/plugins/foreman/content/commands/org-politics-commands.md b/plugins/foreman/content/commands/org-politics-commands.md new file mode 100644 index 0000000..799c79e --- /dev/null +++ b/plugins/foreman/content/commands/org-politics-commands.md @@ -0,0 +1,102 @@ +--- +name: "org-politics-commands" +description: "Commands for navigating organizational politics: viewing stakeholder maps, generating power dynamics maps, analyzing resistance to initiatives, and designing coalition strategies. These commands operate on the organizational politics navigation layer and read from and write to the company, active, and history memory layers." +category: "org-politics" +commands: + - name: "/stakeholders" + syntax: "/stakeholders [--position ] [--power ] [--initiative ]" + description: "View the current stakeholder influence map from memory, filterable by position, power level, or initiative." + - name: "/power-map" + syntax: "/power-map [--initiative ] [--refresh]" + description: "Generate or update the power dynamics map showing formal authority, informal influence, and information flows." + - name: "/resistance" + syntax: "/resistance \"\"" + description: "Analyze stakeholder resistance to a specific initiative by running the stakeholder-resistance-diagnosis." + - name: "/coalition" + syntax: "/coalition \"\" [--status]" + description: "Design a new coalition strategy or review the status of an existing coalition for a specific initiative." +author: "Fatih Guner" +--- + +# Organizational Politics Commands + +## `/stakeholders` + +View the current stakeholder influence map from memory. Default view shows all mapped stakeholders sorted by power level. Filters narrow to specific positions, power levels, or initiatives. If no map exists, prompts the user to create one via the organizational-alignment-playbook. + +**Syntax:** `/stakeholders [--position ] [--power ] [--initiative ]` + +**Parameters:** `--position` (champion/supporter/neutral/skeptic/blocker), `--power` (high/medium/low), `--initiative` (initiative name in quotes). + +**Examples:** +``` +/stakeholders +/stakeholders --position blocker +/stakeholders --power high +/stakeholders --initiative "Q2 Pivot" +/stakeholders --position champion --initiative "Platform Rewrite" +``` + +**Related:** `/power-map`, `/resistance`, `/coalition`, `/context` +**Errors:** No map in memory prompts creation. Invalid filter names return valid options. + +--- + +## `/power-map` + +Generate or refresh the power dynamics map showing formal authority, informal influence, and information flows. Displays existing map from memory and prompts for updates. The `--refresh` flag forces complete reassessment after organizational changes. + +**Syntax:** `/power-map [--initiative ] [--refresh]` + +**Parameters:** `--initiative` (scope to specific initiative), `--refresh` (force reassessment). + +**Examples:** +``` +/power-map +/power-map --initiative "Q2 Pivot" +/power-map --refresh +``` + +**Related:** `/stakeholders`, `/resistance`, `/diagnose` +**Errors:** No organizational data prompts structure description. Unknown initiative lists available ones. + +--- + +## `/resistance` + +Analyze stakeholder resistance to a specific initiative by running stakeholder-resistance-diagnosis. Identifies all skeptics and blockers on the stakeholder map and diagnoses root cause for each. Outputs per-stakeholder diagnosis, root cause classification, and recommended engagement strategy. Results persist to active memory. + +**Syntax:** `/resistance ""` + +**Parameters:** `initiative-name` (required, quotes for multi-word). + +**Examples:** +``` +/resistance "Q2 product pivot" +/resistance "board approval for Series B" +/resistance "platform rewrite" +``` + +**Related:** `/stakeholders`, `/coalition`, `/power-map`, `/apply thomas-kilmann-conflict` +**Errors:** Missing parameter shows usage. No resisters found suggests hidden resistance diagnosis. + +--- + +## `/coalition` + +Design a new coalition strategy or review an existing one. Reads the stakeholder influence map, identifies potential supporters, and walks through target selection, value propositions, sequencing, commitment mechanisms, and defection risk. The `--status` flag shows current coalition health without initiating new design. + +**Syntax:** `/coalition "" [--status]` + +**Parameters:** `initiative-name` (required, quotes for multi-word), `--status` (review existing coalition). + +**Examples:** +``` +/coalition "board approval for Series B" +/coalition "Q2 pivot" --status +/coalition "platform rewrite" +/coalition "international expansion" --status +``` + +**Related:** `/stakeholders`, `/resistance`, `/power-map`, `/apply coalition-and-partnership-games` +**Errors:** Missing parameter shows usage. No existing coalition with `--status` suggests creation command. diff --git a/plugins/foreman/content/commands/output-commands.md b/plugins/foreman/content/commands/output-commands.md new file mode 100644 index 0000000..bca84ea --- /dev/null +++ b/plugins/foreman/content/commands/output-commands.md @@ -0,0 +1,89 @@ +# Output Commands + +Reformatting, exporting, and comparing analysis outputs from skills and playbooks. + +--- + +## `/format [audience]` + +Reformat the most recent output for a different audience. Content stays identical -- structure, emphasis, vocabulary change per the target template. + +**Syntax:** `/format ` + +| Parameter | Required | Values | Description | +|-----------|----------|--------|-------------| +| `audience` | Yes | `investor`, `board`, `team` | Maps to the corresponding output template. | + +**Examples:** +``` +> /format board +SWOT --> board. Strategic Position Q1 2026: Distribution moat via 3 enterprise +partnerships ($2.1M ACV). Threats: 2 funded competitors in mid-market. +Actions: 1) 3 AE hires Q2. 2) Competitive response review. +> /format team +Unit Economics --> team. Action Plan: CAC payback 14mo (target <12), 2.1% trial +conversion. Product: onboarding redesign Apr 15. Marketing: $8K/mo reallocation. +Sales: 30-min onboarding calls for trials >$500 MRR. +> /format investor +Competitive Landscape --> investor. Series A: 12+ players, no dominant platform. +Edge: real-time compliance + automated reporting, 2 patents. Moat: 4-6mo switching cost. +``` +**Related:** `/export`, `/compare` +**Errors:** No output: `No recent analysis. Run a skill or playbook first.` Bad value: `Unknown audience. Available: investor, board, team.` + +--- + +## `/export [format]` + +Export the most recent output as a file. Filename: `{skill}_{date}.{ext}`. + +**Syntax:** `/export ` + +| Parameter | Required | Values | Description | +|-----------|----------|--------|-------------| +| `format` | Yes | `md`, `pdf`, `html`, `txt` | Output file format. | + +**Examples:** +``` +> /export md +swot-analysis_2026-03-26.md (4.2 KB) ready. +> /export pdf +unit-economics_2026-03-26.pdf (12.1 KB) ready. +> /export html +competitive-landscape_2026-03-26.html (8.7 KB) ready. +> /export csv +Unknown format: "csv". Available: md, pdf, html, txt. +``` +**Related:** `/format`, `/compare` +**Errors:** No output: `No recent analysis. Run a skill or playbook first.` Bad format: `Unknown format. Available: md, pdf, html, txt.` Failure: `Export failed. Try a different format or check /status.` + +--- + +## `/compare [analysis1] [analysis2]` + +Side-by-side comparison of two past analyses. Same-framework runs field-by-field; cross-framework highlights agreements and contradictions. + +**Syntax:** `/compare "" ""` + +| Parameter | Required | Description | +|-----------|----------|-------------| +| `analysis1` | Yes | Skill name, date-qualified label, or natural-language match. Quote if spaces. | +| `analysis2` | Yes | Same format as `analysis1`. | + +**Examples:** +``` +> /compare "swot 2026-01" "swot 2026-03" +SWOT Jan vs. Mar: Strengths + "Series A closed" / - "Bootstrap efficiency". +Weakness gap 3 roles-->1. Threat: Competitor B raised $22M. Trend: improved. +> /compare "nps Q1" "nps Q2" +NPS: 34-->41 (+7). Promoters 38%-->45%. Driver: onboarding 3.1-->4.0. +Drag: support response time unchanged. +> /compare "pricing analysis" "unit economics march" +Cross-framework. Agree: $49/mo undervalues enterprise. Conflict: pricing +recommends usage-based; unit economics flags CAC risk. Run sensitivity analysis. +> /compare "swot 2025-06" "tam analysis" +No match: "swot 2025-06". Available: swot 2026-01, swot 2026-03. +Try: /compare "swot 2026-01" "tam analysis" +``` +**Related:** `/format`, `/export` +**Errors:** No match: lists similar outputs with correction. No history: `No past analyses. Run a skill or playbook first.` diff --git a/plugins/foreman/content/commands/output.md b/plugins/foreman/content/commands/output.md new file mode 100644 index 0000000..fbee56e --- /dev/null +++ b/plugins/foreman/content/commands/output.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /output command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /output + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/execution-commands.md and execute only /output with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/pause.md b/plugins/foreman/content/commands/pause.md new file mode 100644 index 0000000..e0f983d --- /dev/null +++ b/plugins/foreman/content/commands/pause.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /pause command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /pause + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /pause with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/playbook-commands.md b/plugins/foreman/content/commands/playbook-commands.md new file mode 100644 index 0000000..56bd0d0 --- /dev/null +++ b/plugins/foreman/content/commands/playbook-commands.md @@ -0,0 +1,121 @@ +# Playbook Commands + +Lifecycle management for active playbooks -- navigation, state, termination. + +--- + +## `/status` + +Show the active playbook's state: name, step position, checklist, blockers. Returns `No active playbook.` when idle. + +**Syntax:** `/status` | **Parameters:** None. + +**Examples:** +``` +> /status +Fundraising Readiness (Series A) — Step 3/7 + [x] Market Sizing [x] Competitive Landscape [ ] Unit Economics (current) + [ ] Financial Projections [ ] Pitch Narrative [ ] Investor Targeting + [ ] Due Diligence | Blockers: None +``` +``` +> /status +Should I Pivot? — Step 2/5 + [x] PMF Assessment [ ] SWOT (current) [ ] Lean Canvas + [ ] Unit Economics [ ] Go/No-Go | Blockers: Interview data low-confidence (n=4). +``` +``` +> /status +No active playbook. +``` +**Related:** `/pause`, `/abort` | **Errors:** `Unable to retrieve state. Try again or /abort to reset.` + +--- + +## `/skip` + +Skip the current step. Warns what insight will be absent downstream. Requires `[y/n]`. Step marked `[skipped]`. + +**Syntax:** `/skip` | **Parameters:** None. + +**Examples:** +``` +> /skip +Skipping Step 3 (Porter's Five Forces) — competitive data absent from Pitch +Narrative (5) and Investor Targeting (6). Confirm? [y/n] +> y — Step 3 skipped. Proceeding to Step 4. +``` +``` +> /skip +Skipping Step 2 (SWOT) removes strengths/weaknesses from Lean Canvas (3). +Confirm? [y/n] > n — Skip cancelled. Continuing Step 2. +``` +``` +> /skip +Cannot skip Step 5 (Go/No-Go) — final step. Use /abort. +``` +**Related:** `/back`, `/status` | **Errors:** No playbook: `Nothing to skip.` Last step: `Cannot skip the final step.` + +--- + +## `/back` + +Return to the previous step, re-run with current context. Output replaces the original. + +**Syntax:** `/back` | **Parameters:** None. + +**Examples:** +``` +> /back +Returning to Step 2 (Competitive Landscape). Re-running with Unit Economics context. Running Step 2... +> /back +Returning to Step 1 (PMF Assessment). Customer data from Step 2 incorporated. Running Step 1... +> /back +Cannot go back — already on Step 1. +``` +**Related:** `/skip`, `/status` | **Errors:** No playbook: `Nothing to go back to.` Step 1: `Already on Step 1.` + +--- + +## `/pause` + +Pause the playbook, save full state to memory. Resume with `/resume`. Clears active slot. + +**Syntax:** `/pause` | **Parameters:** None. + +**Examples:** +``` +> /pause +Fundraising Readiness paused at Step 3. Steps 1-2 saved. /resume to continue. +> /pause +Should I Pivot? paused at Step 4. Steps 1-3 saved. /resume to continue. +> /pause +Pricing Strategy paused at Step 1. No completed steps. /resume to continue. +``` +**Related:** `/resume`, `/status`, `/abort` | **Errors:** No playbook: `Nothing to pause.` Write fail: `State not saved. Playbook remains active.` + +--- + +## `/abort` + +Cancel the playbook. Completed outputs go to history; remaining steps discarded. Irreversible -- double confirmation. + +**Syntax:** `/abort` | **Parameters:** None. + +**Examples:** +``` +> /abort +End Fundraising Readiness? Steps 1-2 preserved, 3-7 discarded. [y/n] +> y — Final confirmation, cannot undo. [y/n] > y — Aborted. Steps 1-2 in history. +``` +``` +> /abort +End Should I Pivot? Steps 1-4 preserved, Step 5 discarded. [y/n] +> n — Abort cancelled. Continuing at Step 5. +``` +``` +> /abort +End Pricing Strategy? Nothing completed, nothing preserved. [y/n] +> y — Final confirmation. [y/n] > y — Aborted. +``` +**Related:** `/pause`, `/status` | **Errors:** No playbook: `Nothing to abort.` Declined: `Abort cancelled.` diff --git a/plugins/foreman/content/commands/playbooks.md b/plugins/foreman/content/commands/playbooks.md new file mode 100644 index 0000000..b781af6 --- /dev/null +++ b/plugins/foreman/content/commands/playbooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /playbooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /playbooks + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /playbooks with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/power-map.md b/plugins/foreman/content/commands/power-map.md new file mode 100644 index 0000000..059e664 --- /dev/null +++ b/plugins/foreman/content/commands/power-map.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /power-map command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /power-map + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /power-map with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/progress.md b/plugins/foreman/content/commands/progress.md new file mode 100644 index 0000000..d68cb28 --- /dev/null +++ b/plugins/foreman/content/commands/progress.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /progress command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /progress + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /progress with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/research-commands.md b/plugins/foreman/content/commands/research-commands.md new file mode 100644 index 0000000..7822c39 --- /dev/null +++ b/plugins/foreman/content/commands/research-commands.md @@ -0,0 +1,109 @@ +--- +name: "research-commands" +description: "Commands for discovering, loading, and tracking structured research guides that teach entrepreneurs how to gather the data required by Foreman's skills and frameworks." +category: "research" +commands: + - name: "/research" + syntax: "/research" + description: "List all available research templates with type, time estimate, and connected skills." + - name: "/research [template-name]" + syntax: "/research [template-name]" + description: "Load a specific research template with its full protocol and collection forms." + - name: "/research for [skill-name]" + syntax: "/research for [skill-name]" + description: "Show which research templates feed into a specific skill." + - name: "/research status" + syntax: "/research status" + description: "Show research collection efforts in progress." +author: "Fatih Guner" +--- + +# Research Commands + +## `/research` + +Lists every research template in the system with name, type, estimated time, and connected skills. + +``` +/research +--> 4 research templates available + pricing-research-guide | customer | 8-15 hrs | Feeds: four-ps-marketing, ... + due-diligence-research | financial | 20-40 hrs | Feeds: due-diligence-checklist, ... + user-testing-protocol | customer | 10-20 hrs | Feeds: net-promoter-score, ... + industry-mapping-guide | market | 15-25 hrs | Feeds: porters-five-forces, ... +``` + +This command takes no parameters and has no failure modes. Related: `/research [name]`, `/research for [skill]`, `/skills`. + +--- + +## `/research [template-name]` + +Loads a full research template: purpose, data sources, step-by-step protocol, collection forms, interpretation guide, and output mapping. Partial matches return suggestions. + +| Parameter | Required | Type | Description | +|-----------|----------|------|-------------| +| `template-name` | Yes | string | Template identifier in kebab-case | + +``` +/research pricing-research-guide +--> Loading: Pricing Research Guide + Type: customer | Time: 8-15 hrs | Feeds: four-ps-marketing, pricing-diagnosis, ... + [Full template rendered] + +/research industry-mapping +--> No exact match. Did you mean: industry-mapping-guide? + +/research competitor +--> No exact match. Related: industry-mapping-guide, pricing-research-guide + +/research customer-interview +--> No exact match. Related: user-testing-protocol, pricing-research-guide +``` + +**Error**: `/research nonexistent` returns `No template matching "nonexistent". Run /research to see all.` + +Related: `/research`, `/apply [skill]`, `/research status`. + +--- + +## `/research for [skill-name]` + +Reverse-lookup: returns all research templates whose `feeds_into_skills` or `feeds_into_templates` include the given name. Use before applying a framework to verify you have the required data. + +| Parameter | Required | Type | Description | +|-----------|----------|------|-------------| +| `skill-name` | Yes | string | Skill or template identifier in kebab-case | + +``` +/research for porters-five-forces +--> Recommended: industry-mapping-guide (market, 15-25 hrs) + +/research for unit-economics-snapshot +--> Recommended: pricing-research-guide (8-15 hrs), due-diligence-research (20-40 hrs) + +/research for stoic-emotional-mastery +--> No research templates feed into this skill. +``` + +**Errors**: Missing skill name returns usage hint. Unknown skill name suggests `/skills` or `/templates` to browse. + +Related: `/skill [name]`, `/research [template]`, `/diagnose [area]`. + +--- + +## `/research status` + +Displays active research efforts from the implementation tracking layer: progress, next steps, and blockers. Returns guidance when nothing is tracked. + +``` +/research status +--> Active research: 2 items + pricing-research-guide | In progress | 3/5 steps | Next: WTP interviews + industry-mapping-guide | Not started | 0/6 steps | Next: Define boundaries + +/research status +--> No active research. Run /research [name] to load a guide, then /track to begin. +``` + +Related: `/track`, `/progress [item-id] [%] [note]`, `/blockers`, `/check-in`. diff --git a/plugins/foreman/content/commands/research.md b/plugins/foreman/content/commands/research.md new file mode 100644 index 0000000..9bb7d13 --- /dev/null +++ b/plugins/foreman/content/commands/research.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /research command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /research + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/research-commands.md and execute only /research with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/resistance.md b/plugins/foreman/content/commands/resistance.md new file mode 100644 index 0000000..0d61733 --- /dev/null +++ b/plugins/foreman/content/commands/resistance.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resistance command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resistance + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /resistance with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/search.md b/plugins/foreman/content/commands/search.md new file mode 100644 index 0000000..8ed7b1b --- /dev/null +++ b/plugins/foreman/content/commands/search.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /search command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /search + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /search with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/sector.md b/plugins/foreman/content/commands/sector.md new file mode 100644 index 0000000..51611ca --- /dev/null +++ b/plugins/foreman/content/commands/sector.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /sector command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /sector + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /sector with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/simulate.md b/plugins/foreman/content/commands/simulate.md new file mode 100644 index 0000000..d081e55 --- /dev/null +++ b/plugins/foreman/content/commands/simulate.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /simulate command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /simulate + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/simulation-commands.md and execute only /simulate with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/simulation-commands.md b/plugins/foreman/content/commands/simulation-commands.md new file mode 100644 index 0000000..815fe01 --- /dev/null +++ b/plugins/foreman/content/commands/simulation-commands.md @@ -0,0 +1,163 @@ +--- +name: "simulation-commands" +description: "Commands for initiating, configuring, and reviewing board simulation sessions -- adversarial role-play rehearsals where the AI assumes board member personas and challenges the entrepreneur's presentations." +category: "simulation" +commands: + - name: "/simulate board" + syntax: "/simulate board [--persona ]" + description: "Start a board meeting simulation with an optional persona selection." + - name: "/simulate investor-pitch" + syntax: "/simulate investor-pitch [--persona ]" + description: "Start an investor pitch simulation with higher stakes and faster pace." + - name: "/simulate due-diligence" + syntax: "/simulate due-diligence [--persona ]" + description: "Start a due diligence simulation with technical, granular questioning." + - name: "/simulate score" + syntax: "/simulate score" + description: "View the detailed score breakdown from the most recent simulation." + - name: "/simulate history" + syntax: "/simulate history" + description: "View past simulation results with scores and trend analysis." +author: "Fatih Guner" +--- + +# Simulation Commands + +## `/simulate board` + +Initiates a board meeting simulation. The system assumes a board member persona, reads the entrepreneur's presentation material, and conducts 5-7 rounds of adversarial Q&A. Optionally accepts a persona flag; defaults to `friendly-challenger` for first-time users or the persona targeting the entrepreneur's weakest dimension for returning users. + +| Parameter | Required | Type | Description | +|-----------|----------|------|-------------| +| `--persona` | No | string | Board persona identifier: `skeptic-investor`, `operational-expert`, `financial-hawk`, `industry-veteran`, `friendly-challenger` | + +``` +/simulate board +--> Starting board meeting simulation + Persona: friendly-challenger (default for first simulation) + Provide your board presentation material to begin. + +/simulate board --persona skeptic-investor +--> Starting board meeting simulation + Persona: skeptic-investor + Provide your board presentation material to begin. + +/simulate board --persona financial-hawk +--> Starting board meeting simulation + Persona: financial-hawk + Warning: This persona focuses heavily on unit economics. Have your numbers ready. + +/simulate board --persona nonexistent +--> Error: Unknown persona "nonexistent". Available: skeptic-investor, operational-expert, financial-hawk, industry-veteran, friendly-challenger. +``` + +**Error**: No presentation material provided after start returns a prompt: `Please provide your board update, quarterly review, or other board-audience material. You can use /output [template] to generate one first.` + +Related: `/simulate score`, `/output board-update`, `/output quarterly-review`. + +--- + +## `/simulate investor-pitch` + +Initiates an investor pitch simulation -- shorter, faster, and higher stakes than a board meeting. The persona plays a potential investor hearing the pitch for the first time. Runs 5-6 rounds of Q&A. Same persona options as `/simulate board`. + +| Parameter | Required | Type | Description | +|-----------|----------|------|-------------| +| `--persona` | No | string | Board persona identifier (same set as `/simulate board`) | + +``` +/simulate investor-pitch +--> Starting investor pitch simulation + Persona: skeptic-investor (default for pitch simulations) + Provide your pitch deck or investor materials to begin. + +/simulate investor-pitch --persona friendly-challenger +--> Starting investor pitch simulation + Persona: friendly-challenger + Provide your pitch deck or investor materials to begin. + +/simulate investor-pitch --persona industry-veteran +--> Starting investor pitch simulation + Persona: industry-veteran + This persona will test your industry knowledge. Prepare for historical precedent challenges. +``` + +**Error**: Running `/simulate investor-pitch` without investor-audience material returns: `This simulation expects investor-facing material. Use /output fundraising-deck-outline or /output unit-economics-snapshot to prepare.` + +Related: `/simulate score`, `/output fundraising-deck-outline`, `/output unit-economics-snapshot`. + +--- + +## `/simulate due-diligence` + +Initiates a due diligence simulation -- the most granular and technically demanding format. The persona plays a DD analyst verifying every claim, tracing every number to its source, and stress-testing every assumption. Runs 6-7 rounds. Best suited for later-stage founders preparing for institutional investor scrutiny. + +| Parameter | Required | Type | Description | +|-----------|----------|------|-------------| +| `--persona` | No | string | Board persona identifier (same set; `financial-hawk` is the default for DD simulations) | + +``` +/simulate due-diligence +--> Starting due diligence simulation + Persona: financial-hawk (default for DD simulations) + Provide your financial model, data room materials, or operational documentation. + +/simulate due-diligence --persona operational-expert +--> Starting due diligence simulation + Persona: operational-expert + This simulation will focus on operational due diligence. Prepare process documentation. + +/simulate due-diligence --persona skeptic-investor +--> Starting due diligence simulation + Persona: skeptic-investor + Provide your financial model and supporting documentation to begin. +``` + +**Error**: `/simulate due-diligence` without material returns: `Due diligence simulation requires detailed documentation. Provide your financial model, operational data, or use /research due-diligence-research to prepare.` + +Related: `/simulate score`, `/research due-diligence-research`, `/output unit-economics-snapshot`. + +--- + +## `/simulate score` + +Displays the detailed score breakdown from the most recent simulation, including dimension-level scores, persona weights, composite grade, weakness analysis, and routing to improvement resources. Also triggers the post-simulation diagnostic if it has not yet run. + +``` +/simulate score +--> Last simulation: board meeting | Persona: skeptic-investor | Date: 2026-03-25 + Clarity: 4/5 (weight: 1.0) + Evidence: 2/5 (weight: 1.5) ** Weakest + Strategic Coherence: 3/5 (weight: 1.0) + Risk Awareness: 3/5 (weight: 1.3) + Response Quality: 3/5 (weight: 1.2) + Composite: 2.9 / 5.0 | Grade: C (Adequate) + Top weakness: Evidence (content gap -- missing unit economics data) + Recommended: /research pricing-research-guide, /apply business-model-canvas + +/simulate score +--> No simulation results found. Run /simulate board, /simulate investor-pitch, or /simulate due-diligence first. +``` + +Related: `/simulate history`, `/simulate board`. + +--- + +## `/simulate history` + +Displays all past simulation results with dates, types, personas, composite scores, and trend analysis. Enables the entrepreneur to track improvement over time and identify persistent weaknesses. + +``` +/simulate history +--> 3 simulations on record + 2026-03-10 board friendly-challenger C (2.8) + 2026-03-18 investor-pitch skeptic-investor C (3.1) + 2026-03-25 board skeptic-investor B (3.6) + Trend: improving (+0.8 over 3 sessions) + Persistent weakness: Evidence (scored below 3 in all sessions) + +/simulate history +--> No simulation history. Run your first simulation with /simulate board. +``` + +Related: `/simulate score`, `/simulate board`, `/memory`. diff --git a/plugins/foreman/content/commands/skills.md b/plugins/foreman/content/commands/skills.md new file mode 100644 index 0000000..7308c02 --- /dev/null +++ b/plugins/foreman/content/commands/skills.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skills command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skills + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /skills with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/skip.md b/plugins/foreman/content/commands/skip.md new file mode 100644 index 0000000..076c065 --- /dev/null +++ b/plugins/foreman/content/commands/skip.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skip command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skip + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/playbook-commands.md and execute only /skip with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/solo-command.md b/plugins/foreman/content/commands/solo-command.md new file mode 100644 index 0000000..77b3632 --- /dev/null +++ b/plugins/foreman/content/commands/solo-command.md @@ -0,0 +1,272 @@ +# Solo Command + +Activates, deactivates, and inspects solo mode — the system-wide adaptation layer for solopreneurs. + +--- + +## `/solo` + +### Description + +Activates solo mode. Writes `mode: solo` to the identity layer of memory and loads the solo configuration files (`solo/SOLO.md`, `solo/solo-skill-relevance.yaml`, `solo/solo-audience-map.yaml`, `solo/solo-adaptations.yaml`). From this point forward, every interaction is filtered through the solo lens until explicitly deactivated. + +Activation triggers the following immediate changes: +- Skill relevance scoring adjusts routing priority for all 158 skills. +- Audience mapping remaps investor, board, and team outputs. +- Diagnostic adaptations skip or reframe 8 of 20 diagnostics. +- Playbook adaptations skip or reframe 11 of 20 playbooks. +- Hook adaptations reframe 8 of 16 hooks. +- Default output audience becomes `self`. +- Voice shifts to direct, personal address without team or board assumptions. + +Solo mode persists across sessions. It is stored in memory, not in session state. + +### Syntax + +``` +/solo +``` + +### Parameters + +None. + +### Examples + +``` +> /solo +Solo mode activated. + +You are the company. Every skill, diagnostic, playbook, and template now adapts +for a solopreneur context. Team-oriented diagnostics are rerouted. Board and +investor templates reframe as personal analysis. The system defaults to you as +the audience. + +What changed: + Skills: 158 scored for solo relevance (47 critical, 56 high, 28 moderate, 27 low) + Templates: 48 available (30 reframed, 10 as-is, 8 unchanged) + Diagnostics: 20 available (12 as-is, 5 reframed, 3 skipped with reroutes) + Playbooks: 20 available (8 as-is, 8 reframed, 4 skipped with alternatives) + Hooks: 16 active (8 as-is, 8 reframed) + +Mode persists across sessions. Use /solo off to deactivate. + +> /solo +Solo mode is already active (since 2026-03-26). No change. +Use /solo status for details or /solo off to deactivate. +``` + +### What Changes When Activated + +| System Layer | Change | +|-------------|--------| +| Memory (identity) | `mode: solo` written to identity.yaml | +| Skill routing | 158 skills scored per solo-skill-relevance.yaml; low-tier skills deprioritized, critical-tier skills elevated | +| Audience mapping | Investor, board, and team audiences remapped per solo-audience-map.yaml | +| Diagnostics | 3 diagnostics skipped (cofounder-conflict, culture-erosion, team-dysfunction), 5 reframed with solo triage questions | +| Playbooks | 4 playbooks skipped (board-formation, remote-team, team-rebuild, and none applicable), 8 reframed with solo step instructions | +| Hooks | 8 hooks reframed with solo routing changes; team-hook intercepts with clarifying question | +| Output | Default audience becomes `self`; all templates apply solo adaptation rules | +| Voice | Shifts to direct personal address; removes team/board/investor assumptions | + +### Related Commands + +- `/solo off` — Deactivate solo mode +- `/solo status` — Show current mode and adaptation summary +- `/stage` — Solo mode works with all five stages but interprets them differently + +### Error Handling + +| Input | Response | +|-------|----------| +| `/solo` when already active | `Solo mode is already active (since [date]). No change.` | +| `/solo enable` | `Unknown argument: "enable". Use /solo to activate, /solo off to deactivate, /solo status to inspect.` | + +--- + +## `/solo off` + +### Description + +Deactivates solo mode. Removes `mode: solo` from the identity layer of memory. All routing, scoring, audience mapping, and voice modifications revert to default behavior. The system returns to its standard assumption: a startup founder with a team, board, and investors. + +Deactivation is immediate. The current session switches to default mode for all subsequent interactions. Prior analysis produced in solo mode is retained in history without modification — it remains tagged as solo-context analysis. + +### Syntax + +``` +/solo off +``` + +### Parameters + +None. + +### Examples + +``` +> /solo off +Solo mode deactivated. Default mode restored. + +All skills, diagnostics, playbooks, and templates now operate with standard +assumptions: team, board, and investor contexts are active. Output audience +inference resumes normal behavior. + +Prior solo-mode analysis remains in your history, tagged with mode: solo. + +> /solo off +Solo mode is not active. No change. +``` + +### Related Commands + +- `/solo` — Reactivate solo mode +- `/solo status` — Check current mode before deactivating + +### Error Handling + +| Input | Response | +|-------|----------| +| `/solo off` when not active | `Solo mode is not active. No change.` | +| `/solo off now` | `Unknown argument: "now". Use /solo off to deactivate. No additional arguments accepted.` | + +--- + +## `/solo status` + +### Description + +Displays the current mode and a summary of what solo mode affects. If solo mode is active, shows activation date, adaptation statistics, and any active overrides. If solo mode is inactive, confirms default mode. + +This command is read-only — it never modifies state. + +### Syntax + +``` +/solo status +``` + +### Parameters + +None. + +### Examples + +``` +> /solo status +Mode: solo (active since 2026-03-26) +Stage: early-traction (solo interpretation: consistent revenue as solo operator) + +Skill relevance adjustments: + critical: 47 skills (elevated routing priority) + high: 56 skills (normal priority) + moderate: 28 skills (reframing required) + low: 27 skills (deprioritized, available on request) + +Audience mapping: + investor → self-funding-analysis + board → mentor-advisor + team → systems-and-processes + client → client (unchanged) + self → self (default audience) + +Diagnostic adaptations: + as-is: 12 diagnostics + reframed: 5 diagnostics (communication-breakdown, decision-paralysis, + fundraising, growth-stall, hiring, innovation-drought, + leadership-crisis, operational-chaos, revenue, strategic-drift) + skipped: 3 diagnostics (cofounder-conflict, culture-erosion, team-dysfunction) + +Playbook adaptations: + as-is: 8 playbooks + reframed: 8 playbooks + skipped: 4 playbooks (board-formation, remote-team, team-rebuild) + +Hook adaptations: + as-is: 8 hooks + reframed: 8 hooks + +Use /solo off to deactivate. Use /solo to reactivate if currently off. + +> /solo status +Mode: default (solo mode not active) +All skills, diagnostics, playbooks, and templates operate with standard +assumptions. Use /solo to activate solo mode. +``` + +### Related Commands + +- `/solo` — Activate solo mode +- `/solo off` — Deactivate solo mode +- `/stage` — View or change company stage (works in both modes) +- `/version` — View system component counts + +### Error Handling + +| Input | Response | +|-------|----------| +| `/solo status verbose` | `Unknown argument: "verbose". /solo status takes no parameters.` | + +--- + +## Implementation Notes + +### Memory Integration + +Solo mode state is stored in Layer 1 (Identity) of the memory system: + +```yaml +# identity.yaml — fields added by /solo +mode: solo +mode_activated: 2026-03-26 +``` + +The memory-agent reads this field during SESSION_START and passes it to the orchestrator. The orchestrator then loads the four solo configuration files and applies them for the duration of the session. + +When `/solo off` is executed, the memory-agent removes the `mode` and `mode_activated` fields from identity.yaml. The next session start will find no mode flag and operate in default mode. + +### Session Continuity + +If solo mode is activated or deactivated mid-session, the change applies immediately to all subsequent interactions within that session. Analyses already produced in the session are not retroactively modified. The session layer records the mode change event: + +```yaml +# session.yaml — mode change event +mode_changes: + - from: default + to: solo + timestamp: 2026-03-26T14:30:00Z +``` + +### History Tagging + +All analyses, decisions, and diagnostics produced while solo mode is active are tagged with `mode: solo` in the history layer. This ensures that when the entrepreneur reviews past analyses, the solo context is clear. If the entrepreneur later deactivates solo mode and reviews a prior solo analysis, the system notes: "This analysis was produced in solo mode. Team, board, and investor contexts were adapted for solopreneur use." + +### Interaction with Stage + +Solo mode and stage are independent settings. A solopreneur can be at any stage: idea, validation, early-traction, growth, or scale. Solo mode adjusts the interpretation of each stage (see SOLO.md, Behavioral Change 1) but does not restrict which stages are available. + +``` +> /stage growth +Updated: growth (was early-traction). +Solo mode active: "growth" interpreted as increasing revenue or margin +without proportional time increase; leveraging automation, pricing, +or productization. Standard growth interpretation (scaling team and +revenue aggressively) is not applied. +``` + +### Interaction with Commands + +All existing commands work in solo mode. The following commands produce different output when solo mode is active: + +| Command | Solo Mode Behavior | +|---------|-------------------| +| `/skills` | Adds solo relevance tier to each skill listing | +| `/templates` | Shows solo audience mapping next to original audience | +| `/diagnostics` | Notes which diagnostics are skipped or reframed | +| `/playbooks` | Notes which playbooks are skipped or reframed | +| `/hooks` | Notes which hooks have modified routing | +| `/stage` | Displays solo stage interpretation alongside standard | +| `/apply` | Adds reframing notes for moderate and low-tier skills | +| `/diagnose` | Applies solo diagnostic adaptations | +| `/run` | Applies solo playbook step modifications | +| `/output` | Applies audience remapping and template adaptations | diff --git a/plugins/foreman/content/commands/solo.md b/plugins/foreman/content/commands/solo.md new file mode 100644 index 0000000..a6232f2 --- /dev/null +++ b/plugins/foreman/content/commands/solo.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /solo command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /solo + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/solo-command.md and execute only /solo with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/commands/stage.md b/plugins/foreman/content/commands/stage.md new file mode 100644 index 0000000..f129326 --- /dev/null +++ b/plugins/foreman/content/commands/stage.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stage command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stage + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/stakeholders.md b/plugins/foreman/content/commands/stakeholders.md new file mode 100644 index 0000000..874982b --- /dev/null +++ b/plugins/foreman/content/commands/stakeholders.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stakeholders command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stakeholders + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/org-politics-commands.md and execute only /stakeholders with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/stoic-command.md b/plugins/foreman/content/commands/stoic-command.md new file mode 100644 index 0000000..eba66ac --- /dev/null +++ b/plugins/foreman/content/commands/stoic-command.md @@ -0,0 +1,199 @@ +--- +name: "stoic-mode-commands" +description: "Activates, deactivates, and reports status of Stoic mode — a philosophical lens that adds Stoic depth to all system responses without changing analytical content" +category: "meta" +commands: + - name: "/stoic on" + syntax: "/stoic on" + description: "Activates Stoic mode" + - name: "/stoic off" + syntax: "/stoic off" + description: "Deactivates Stoic mode" + - name: "/stoic status" + syntax: "/stoic status" + description: "Reports current Stoic mode state" +author: "Fatih Guner" +--- + +# /stoic + +Stoic mode adds a philosophical depth layer to all system responses. It does not alter what frameworks are applied, which diagnostics run, or which playbooks execute. It changes how their outputs are framed, contextualized, and delivered — through the lens of Stoic philosophy. + +The analytical engine remains identical. The philosophical engine activates alongside it. + +--- + +## /stoic on + +### Description + +Activates Stoic mode for the current session and all future sessions until explicitly deactivated. Writes `stoic_mode: true` to the memory identity layer. The orchestrator-agent loads `.claude/stoic-mode/STOIC-MODE.md` into its active context and applies `.claude/stoic-mode/stoic-response-rules.yaml` to all subsequent outputs. + +### Syntax + +``` +/stoic on +``` + +No parameters. No flags. + +### What Changes + +| Layer | Change | +|-------|--------| +| Skills | Stoic Reflection paragraph added to every skill output. Dichotomy of control applied. Anti-patterns framed through cardinal virtues. | +| Diagnostics | Pre-triage control question added. Post-diagnosis framed through Stoic acceptance. | +| Playbooks | Stoic checkpoint at each gate. Decision points evaluated through virtue ethics. | +| Output Templates | "Stoic Reflection" section appended. Risk sections reframed as Premeditatio Malorum. Recommendations close with agency reminder. | +| Memory | `stoic_mode: true` persisted. Decision history includes `stoic_reflection` field. | +| Voice | Adversity framed as material. Success framed as temporary. Uncertainty framed as normal. Failure framed as information. | + +### What Does NOT Change + +- Framework rigor and analytical precision +- Data, metrics, and quantitative assessments +- Strategic recommendations +- Prohibited phrases rules +- Hook routing and diagnostic triage logic + +### Confirmation Message + +On activation, the system responds: + +> Stoic mode active. As Epictetus observed: "It is not things that disturb us, but our judgments about things." Your analyses will now distinguish between the two. + +### Examples + +**Example 1: Activation** +``` +Entrepreneur: /stoic on +System: Stoic mode active. As Epictetus observed: "It is not things that +disturb us, but our judgments about things." Your analyses will now +distinguish between the two. +``` + +**Example 2: Skill output with Stoic mode** +``` +Entrepreneur: /apply porters-five-forces +System: [Full Porter's Five Forces analysis...] + +Stoic Reflection: This analysis reveals three forces outside your direct +control — supplier consolidation, regulatory shifts, and substitute +technology development. Two forces sit squarely within your sphere of +action: your competitive positioning and your relationship architecture +with buyers. The Stoic counsel: invest your energy where your agency +operates. Monitor the uncontrollable forces as a sailor monitors weather +— with attention but without the delusion that attention changes the wind. +``` + +**Example 3: Combined with Solo mode** +``` +Entrepreneur: /solo +System: Solo mode active. + +Entrepreneur: /stoic on +System: Stoic mode active alongside solo mode. You face the particular +Stoic challenge of the solitary practitioner: every decision is yours +alone, every consequence lands undiluted. Marcus Aurelius carried the +same weight — an emperor with no peer to share the burden. His method: +morning preparation, evening review, relentless self-honesty between. +``` + +--- + +## /stoic off + +### Description + +Deactivates Stoic mode. Writes `stoic_mode: false` to memory. Returns to standard analytical voice immediately. Does not affect past outputs — only future ones. + +### Syntax + +``` +/stoic off +``` + +### Confirmation Message + +> Stoic mode deactivated. The frameworks remain. The philosophy, one hopes, lingers. + +### Examples + +``` +Entrepreneur: /stoic off +System: Stoic mode deactivated. The frameworks remain. The philosophy, +one hopes, lingers. +``` + +--- + +## /stoic status + +### Description + +Reports whether Stoic mode is currently active and summarizes what it affects. + +### Syntax + +``` +/stoic status +``` + +### Output When Active + +``` +Stoic mode: ACTIVE +Active since: [date from memory] +Combined with: [solo mode / none] + +Effects: + - Skill outputs include Stoic Reflection layer + - Diagnostics include dichotomy-of-control pre-question + - Playbook checkpoints include virtue gate + - Output templates include Premeditatio Malorum framing + - Decision history captures stoic_reflection field +``` + +### Output When Inactive + +``` +Stoic mode: INACTIVE + +To activate: /stoic on +Stoic mode adds philosophical depth to all system responses without +changing analytical content. It frames adversity as material, success +as temporary, and agency as the only true possession. +``` + +--- + +## Error Handling + +| Input | Response | +|-------|----------| +| `/stoic` (no argument) | "Usage: /stoic on, /stoic off, or /stoic status" | +| `/stoic on` when already active | "Stoic mode is already active. The Stoics would note that repeating a command does not double its effect." | +| `/stoic off` when already inactive | "Stoic mode is not active. Nothing to deactivate." | +| `/stoic [invalid]` | "Unrecognized argument. Available: on, off, status" | + +--- + +## Related Commands + +- `/solo` — Filters WHAT content is delivered (solopreneur adaptation). Can combine with Stoic mode. +- `/context` — Shows full entrepreneur context including mode status. +- `/stage` — Shows/changes company stage. Stoic mode applies across all stages. +- `/help meta` — Lists all meta commands including mode toggles. + +--- + +## Memory Integration + +| Operation | Memory Layer | Field | +|-----------|-------------|-------| +| Activation | identity | `stoic_mode: true` | +| Deactivation | identity | `stoic_mode: false` | +| Session start | session | Orchestrator checks `identity.stoic_mode` and loads STOIC-MODE.md if true | +| Decision made | history.decisions_made | `stoic_reflection` field added to each decision entry | + +Stoic mode persists across sessions. Once activated, it remains active until the entrepreneur explicitly runs `/stoic off`. This mirrors the Stoic position that philosophy is not a session — it is a practice. diff --git a/plugins/foreman/content/commands/stoic.md b/plugins/foreman/content/commands/stoic.md new file mode 100644 index 0000000..fc24021 --- /dev/null +++ b/plugins/foreman/content/commands/stoic.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /stoic command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stoic + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/stoic-command.md and execute only /stoic with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/commands/templates.md b/plugins/foreman/content/commands/templates.md new file mode 100644 index 0000000..6c57ea0 --- /dev/null +++ b/plugins/foreman/content/commands/templates.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /templates command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /templates + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/navigation-commands.md and execute only /templates with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/track.md b/plugins/foreman/content/commands/track.md new file mode 100644 index 0000000..aa56402 --- /dev/null +++ b/plugins/foreman/content/commands/track.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /track command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /track + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/implementation-commands.md and execute only /track with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/update.md b/plugins/foreman/content/commands/update.md new file mode 100644 index 0000000..23cc52a --- /dev/null +++ b/plugins/foreman/content/commands/update.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /update command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /update + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/memory-commands.md and execute only /update with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/commands/version.md b/plugins/foreman/content/commands/version.md new file mode 100644 index 0000000..8eac0c5 --- /dev/null +++ b/plugins/foreman/content/commands/version.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /version command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /version + +Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/commands/meta-commands.md and execute only /version with the user's arguments: $ARGUMENTS. + +Use .claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from .claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/diagnostics/_schema/diagnostic-template.md b/plugins/foreman/content/diagnostics/_schema/diagnostic-template.md new file mode 100644 index 0000000..8ea425d --- /dev/null +++ b/plugins/foreman/content/diagnostics/_schema/diagnostic-template.md @@ -0,0 +1,92 @@ +--- +name: "kebab-case-diagnostic-name" +description: "Third-person description of what this diagnostic identifies and when to use it. Include entry symptoms and the types of root causes it can distinguish. Max 1024 characters." +entry_symptoms: + - "Natural language symptom the entrepreneur might report" + - "Another symptom phrasing" + - "A third variation" +possible_diagnoses: + - diagnosis-slug-1 + - diagnosis-slug-2 + - diagnosis-slug-3 +routes_to_skills: + - skill-name-1 + - skill-name-2 +routes_to_templates: + - template-name-1 +author: "Fatih Guner" +--- + + + +# {Diagnostic Title} + +## Entry Symptoms + +{The things an entrepreneur actually says — natural language, informal, emotional. These are the trigger phrases that indicate this diagnostic is needed.} + +- "Symptom phrasing 1" +- "Symptom phrasing 2" +- "Symptom phrasing 3" + +--- + +## Triage Questions + + + +**Q1: {Broad differentiating question}** +- If {answer A} → {implication, narrows to...} +- If {answer B} → {implication, narrows to...} + +**Q2: {More specific question based on Q1}** +- If {answer A} → {implication} +- If {answer B} → {implication} + +--- + +## Diagnosis Map + + + +| Pattern | Diagnosis | Confidence | +|---------|-----------|------------| +| Q1=A + Q2=A + Q3=B | {Diagnosis name} | High | +| Q1=B + Q2=A | {Diagnosis name} | Medium | + +--- + +## Routing + + + +**Diagnosis: {Name}** +- Skills: `skill-1` → `skill-2` → `skill-3` +- Playbook: `playbook-name` (if the problem requires multi-step resolution) +- Output: `template-name` + +**Diagnosis: {Name}** +- Skills: `skill-1` → `skill-2` +- Output: `template-name` + +--- + +## Red Flags + + + +{Conditions that exceed the scope of framework-based guidance: legal issues requiring counsel, mental health crises requiring professional support, financial emergencies requiring accountants, etc.} diff --git a/plugins/foreman/content/diagnostics/cofounder-conflict-diagnosis.md b/plugins/foreman/content/diagnostics/cofounder-conflict-diagnosis.md new file mode 100644 index 0000000..ba4da55 --- /dev/null +++ b/plugins/foreman/content/diagnostics/cofounder-conflict-diagnosis.md @@ -0,0 +1,133 @@ +--- +name: "cofounder-conflict-diagnosis" +description: "Performs deep-layer triage on cofounder conflict by distinguishing between vision divergence, role ambiguity, contribution asymmetry, values clashes, equity resentment, communication avoidance, and founder-market fit splits. Use when a first-layer diagnostic surfaces interpersonal founder tension, or when an entrepreneur reports disagreements, work-division frustration, or considering a breakup with their cofounder." +entry_symptoms: + - "My cofounder and I disagree on everything" + - "We have different visions for the company" + - "The work division feels unfair" + - "Thinking about splitting up" + - "One of us isn't pulling their weight" + - "We avoid the hard conversations" +possible_diagnoses: + - vision-divergence + - role-ambiguity + - contribution-asymmetry + - values-clash + - equity-resentment + - communication-avoidance + - founder-market-fit-split +routes_to_skills: + - thomas-kilmann-conflict + - coalition-and-partnership-games + - cooperative-negotiation + - radical-candor + - trust-equation + - psychological-safety + - resolving-people-conflict +routes_to_templates: + - negotiation-prep-sheet + - one-on-one-template +author: "Fatih Guner" +--- + +# Cofounder Conflict Diagnosis + +## Entry Symptoms + +Cofounder conflict is the leading non-market cause of startup death, yet founders almost always describe it in vague relational terms: "We just don't see eye to eye anymore." The ambiguity itself is diagnostic. Cofounders who can articulate the precise nature of their disagreement are already halfway to resolving it. Those who cannot — who speak in general frustration and mutual disappointment — are typically dealing with something structural they have not yet named. + +## Triage Questions + +### Q1: What is the conflict actually about? (Force specificity.) + +- **Where the company is going (strategy, market, product direction, ambition level)** — likely diagnosis: **vision-divergence**. Proceed to Q2 for depth. +- **Who does what and who decides what (roles, authority, day-to-day operations)** — likely diagnosis: **role-ambiguity**. Proceed to Q3. +- **Who is contributing more (effort, hours, sacrifice, results)** — likely diagnosis: **contribution-asymmetry**. Proceed to Q4. +- **How the company should operate (ethics, speed, culture, risk tolerance)** — likely diagnosis: **values-clash**. Proceed to Q5. +- **Equity, compensation, or financial fairness** — likely diagnosis: **equity-resentment**. Proceed to Q4 and Q5. +- **"I can't really articulate it — everything just feels wrong"** — likely diagnosis: **communication-avoidance**. The inability to name the conflict is the conflict. Proceed to Q6. + +### Q2: When you imagine the company in three years, do your pictures match? + +- **Fundamentally different visions — one wants to build a lifestyle business, the other wants to raise Series B** — likely diagnosis: **vision-divergence** at the most fundamental level. This is existential; frameworks can clarify but may not reconcile. +- **Same destination, different routes — both want growth but disagree on how** — this is strategic disagreement, not vision misalignment. Proceed to Q3; the real issue may be decision authority. +- **One founder's vision has evolved while the other's has not** — likely diagnosis: **founder-market-fit-split**. One cofounder has grown with the company's demands; the other remains anchored to an earlier stage. + +### Q3: If a contentious decision needed to be made tomorrow, is it clear who has final authority? + +- **No — decisions require consensus, and consensus has become impossible** — likely diagnosis: **role-ambiguity**. Without clear decision rights, every disagreement becomes existential. +- **Yes — one founder has authority, but the other undermines or resents it** — likely diagnosis: **contribution-asymmetry** or **equity-resentment**. The authority structure exists but lacks legitimacy. +- **Authority shifts depending on the topic, with no explicit agreement about domains** — likely diagnosis: **role-ambiguity** compounded by **communication-avoidance**. The founders never formalised what was obvious when the team was two people. + +### Q4: Would each founder say the other is contributing fairly? + +- **No — one founder perceives a significant imbalance** — likely diagnosis: **contribution-asymmetry**. But contribution is subjective. Is the perceived imbalance about hours, impact, sacrifice, or visibility? +- **Both feel they contribute more (each believes they carry the heavier load)** — likely diagnosis: **contribution-asymmetry** driven by different definitions of value. A technical cofounder counts code; a business cofounder counts deals. Neither sees the other's work. +- **One founder's contribution has genuinely declined — they're checked out, distracted, or pursuing other interests** — likely diagnosis: **founder-market-fit-split**. This founder may have outgrown the company or lost belief in it. + +### Q5: Do you trust your cofounder's judgment, even when you disagree with their conclusions? + +- **Yes — I trust their intent and capability but not their decisions lately** — the relationship foundation is intact. The conflict is circumstantial. Proceed to Q6 for communication diagnosis. +- **No — I question their competence in their domain** — likely diagnosis: **founder-market-fit-split**. The company's complexity has outgrown one founder's capabilities. +- **No — I question their motives or ethics** — likely diagnosis: **values-clash**. This is the most dangerous form of cofounder conflict because it corrodes the basis for collaboration itself. + +### Q6: When did you last have an honest, uncomfortable conversation about the state of your partnership? + +- **Never — we talk about the business but never about us** — likely diagnosis: **communication-avoidance**. Every other diagnosis festers when this one is present. +- **We tried once but it went badly — accusations, defensiveness, withdrawal** — likely diagnosis: **communication-avoidance** compounded by the underlying issue from Q1. +- **Recently, but nothing changes afterward** — the communication channel works; implementation is broken. Consider external facilitation. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Vision divergence** | Different endpoints (lifestyle vs. scale), incompatible ambition levels | Q1 shows directional conflict + Q2 shows fundamentally different pictures | +| **Role ambiguity** | Decision gridlock, territory disputes, consensus paralysis | Q1 shows role-based friction + Q3 shows unclear authority | +| **Contribution asymmetry** | Perceived imbalance in effort/sacrifice, mutual resentment about workload | Q1 shows effort-based tension + Q4 shows divergent contribution beliefs | +| **Values clash** | Disagreement on ethics, culture, risk tolerance, how to treat people | Q1 shows operating-philosophy tension + Q5 shows motive distrust | +| **Equity resentment** | Financial fairness grievances, comp or equity split feels wrong | Q1 shows economic tension + Q4 shows contribution disparity fuelling it | +| **Communication avoidance** | Inability to name the conflict, no meta-conversations, growing distance | Q1 shows vague frustration + Q6 shows no honest dialogue | +| **Founder-market fit split** | One founder evolved, the other didn't; competence gap widened with scale | Q2 shows divergent evolution + Q4 shows genuine contribution decline + Q5 shows competence doubt | + +## Routing + +**Vision divergence:** +1. Apply `cooperative-negotiation` — structure the conversation as interest-based, not position-based +2. Apply `coalition-and-partnership-games` — model the partnership with exit options +3. Output with `negotiation-prep-sheet` + +**Role ambiguity:** +1. Apply `thomas-kilmann-conflict` — identify conflict styles, create explicit decision-rights framework +2. Apply `radical-candor` — establish direct feedback norms between founders +3. Output with `one-on-one-template` + +**Contribution asymmetry:** +1. Apply `trust-equation` — diagnose which trust element has eroded +2. Apply `cooperative-negotiation` — negotiate explicit contribution expectations +3. Output with `negotiation-prep-sheet` + +**Values clash:** +1. Apply `thomas-kilmann-conflict` — determine if the clash is resolvable or terminal +2. Apply `resolving-people-conflict` — systematic resolution before escalating to breakup +3. Output with `negotiation-prep-sheet` + +**Equity resentment:** +1. Apply `coalition-and-partnership-games` — model equity against current and future contribution +2. Apply `cooperative-negotiation` — structure a renegotiation conversation +3. Output with `negotiation-prep-sheet` + +**Communication avoidance:** +1. Apply `radical-candor` — build the capability for direct, caring confrontation +2. Apply `psychological-safety` — create conditions where honest conversation becomes possible +3. Output with `one-on-one-template` + +**Founder-market fit split:** +1. Apply `trust-equation` — assess whether the relationship can accommodate the gap +2. Apply `coalition-and-partnership-games` — model graceful exit or role restructuring +3. Output with `negotiation-prep-sheet` + +## Red Flags + +- **One cofounder has already consulted a lawyer without telling the other.** Once legal counsel is engaged unilaterally, the partnership has shifted from conflict to dissolution. Framework-based mediation can still help structure the exit, but reconciliation probability drops sharply. +- **The conflict involves allegations of financial misconduct, fraud, or breach of fiduciary duty.** This is a legal matter, not a coaching matter. Engage legal counsel and a forensic accountant before any strategic conversation. +- **The cofounders have stopped communicating entirely — updates happen through team members or Slack messages only.** Total communication breakdown in a two-person leadership team is an organisational emergency. The company cannot function while its leaders operate in parallel silos. External mediation is required before any diagnostic framework applies. diff --git a/plugins/foreman/content/diagnostics/communication-breakdown-diagnosis.md b/plugins/foreman/content/diagnostics/communication-breakdown-diagnosis.md new file mode 100644 index 0000000..3e79a19 --- /dev/null +++ b/plugins/foreman/content/diagnostics/communication-breakdown-diagnosis.md @@ -0,0 +1,118 @@ +--- +name: "communication-breakdown-diagnosis" +description: "Diagnoses the root cause when an entrepreneur reports communication failures -- whether internal misalignment, ineffective writing, unproductive meetings, or investor messaging that falls flat. Distinguishes between structural deficits (missing cadence, wrong channels) and skill deficits (poor writing, weak storytelling) to route toward the precise intervention." +entry_symptoms: + - "Nobody reads my emails" + - "The team misunderstands everything" + - "Investors don't get what we do" + - "Internal communication is chaos" + - "Meetings are useless" +possible_diagnoses: + - written-communication-failure + - meeting-dysfunction + - audience-mismatch + - information-overload + - structural-gap + - storytelling-deficit +routes_to_skills: + - writing-process + - writing-effective-emails + - clarity-and-concision + - tone-and-engagement + - writing-for-navigation + - reader-psychology + - storytelling-for-leaders + - what-is-a-story + - story-structure-and-arc + - focus-and-priority-management + - leadership-voice-and-presence + - persuasion-and-influence +routes_to_templates: + - meeting-notes-template + - action-plan + - investor-update-email + - one-on-one-template +author: "Fatih Guner" +--- + +# Communication Breakdown Diagnosis + +Most communication failures are misdiagnosed as volume problems. The founder assumes the solution is to communicate more -- send another Slack message, schedule another all-hands, add another slide to the deck. The actual pathology is almost never insufficient quantity. It is misaligned medium, absent structure, or a fundamental inability to articulate what matters and why anyone should care. + +--- + +## Entry Symptoms + +The entrepreneur typically presents with one or more of these complaints: + +- **"Nobody reads my emails."** Messages go unanswered; critical updates are missed; the founder feels invisible in their own company. +- **"The team misunderstands everything."** Instructions are followed incorrectly; deliverables miss the mark; the same clarifications repeat weekly. +- **"Investors don't get what we do."** Pitch meetings end with polite nods and no follow-up; the value proposition fails to land. +- **"Internal communication is chaos."** Information lives in too many places; no one knows the canonical source of truth; tribal knowledge dominates. +- **"Meetings are useless."** Hours consumed with no decisions made; the same topics resurface endlessly; action items evaporate. + +--- + +## Triage Questions + +Work through these sequentially. Each answer narrows the diagnosis. + +1. **Medium**: Is the problem primarily in written communication (emails, documents, Slack) or verbal communication (meetings, presentations, pitches)? +2. **Audience**: Is the breakdown internal (team, co-founders) or external (investors, customers, partners)? +3. **Root type**: Is this a structural issue (no communication processes, unclear channels, missing cadence) or a skill issue (poorly written messages, weak verbal delivery, unclear thinking)? +4. **Participation**: Are the right people receiving the communication? Are the right people in the room? +5. **Frequency pattern**: Is the breakdown constant, or does it surface only at certain triggers (board meetings, product launches, conflict moments)? +6. **Feedback loop**: Has anyone told the founder directly that their communication is unclear, or is this inferred from downstream failures? + +--- + +## Diagnosis Map + +| Diagnosis | Key Indicators | Core Problem | +|-----------|---------------|--------------| +| **Written Communication Failure** | Emails ignored, documents unread, written instructions misinterpreted | The writing lacks clarity, structure, or reader awareness; messages are too long, too vague, or too frequent | +| **Meeting Dysfunction** | No agendas, no decisions, recurring topics, wrong attendees, meetings that should have been emails | Meetings lack purpose definition, facilitation discipline, or follow-through mechanisms | +| **Audience Mismatch** | Investor pitch uses internal jargon; team updates read like board reports; customer messages feel corporate | Communication is crafted for the sender's comfort, not the receiver's context | +| **Information Overload** | Too many channels, too many updates, notification fatigue, important signals buried in noise | Volume has outpaced the organisation's capacity to filter; no hierarchy of communication importance exists | +| **Structural Gap** | No regular cadence (standups, weeklies, all-hands), no designated channels, no communication norms | The organisation lacks communication infrastructure entirely -- the problem is architectural, not personal | +| **Storytelling Deficit** | Facts delivered without narrative; data dumps without meaning; presentations that inform but fail to persuade | The founder can explain what but cannot convey why it matters -- the emotional and narrative layer is absent | + +--- + +## Routing + +### Written Communication Failure +- **Primary skills**: writing-process, writing-effective-emails, clarity-and-concision, writing-for-navigation +- **Supporting skills**: reader-psychology, tone-and-engagement +- **Templates**: investor-update-email, action-plan + +### Meeting Dysfunction +- **Primary skills**: focus-and-priority-management, leadership-voice-and-presence +- **Templates**: meeting-notes-template, one-on-one-template + +### Audience Mismatch +- **Primary skills**: reader-psychology, tone-and-engagement, persuasion-and-influence +- **Supporting skills**: writing-for-navigation +- **Templates**: investor-update-email + +### Information Overload +- **Primary skills**: focus-and-priority-management, writing-for-navigation +- **Supporting skills**: clarity-and-concision + +### Structural Gap +- **Primary skills**: focus-and-priority-management +- **Templates**: meeting-notes-template, one-on-one-template, action-plan + +### Storytelling Deficit +- **Primary skills**: storytelling-for-leaders, what-is-a-story, story-structure-and-arc +- **Supporting skills**: leadership-voice-and-presence, persuasion-and-influence + +--- + +## Red Flags + +- **Founder refuses feedback on their own communication.** The diagnosis may be accurate, but the intervention will fail unless the founder accepts personal responsibility rather than blaming the audience. +- **Communication problems mask deeper trust issues.** Teams that do not trust leadership will ignore even well-crafted messages. If triage reveals distrust, route to psychological-safety-practice and team-culture-and-dynamics before addressing communication mechanics. +- **Chronic meeting dysfunction paired with zero written documentation.** This combination signals organisational immaturity, not a communication skill gap. Structural intervention must precede skill development. +- **External communication failure despite strong internal communication.** The founder may lack audience translation ability -- they communicate well with insiders but cannot adapt for outsiders. Prioritise reader-psychology and storytelling skills. +- **"Nobody reads my emails" from a founder who sends 40 emails per day.** The problem is not the writing. It is the volume. Route to focus-and-priority-management first. diff --git a/plugins/foreman/content/diagnostics/competitive-threat-diagnosis.md b/plugins/foreman/content/diagnostics/competitive-threat-diagnosis.md new file mode 100644 index 0000000..efd24ee --- /dev/null +++ b/plugins/foreman/content/diagnostics/competitive-threat-diagnosis.md @@ -0,0 +1,118 @@ +--- +name: "competitive-threat-diagnosis" +description: "Diagnoses the nature and severity of competitive threats by distinguishing between direct rivalry, disruptive entrants, commoditization pressure, and strategic positioning failures. Determines whether the entrepreneur faces a moat problem, a differentiation problem, or a market structure problem." +entry_symptoms: + - "Competitors are crushing us" + - "Price war" + - "We're losing market share" + - "A big player just entered our space" + - "We're being commoditized" +possible_diagnoses: + - moat-erosion + - price-commoditization + - disruptive-entrant + - wrong-competitive-arena + - differentiation-failure + - market-category-collapse +routes_to_skills: + - porters-five-forces + - blue-ocean-strategy + - art-of-war + - first-mover-strategy + - disruptive-innovation +routes_to_templates: + - competitive-landscape-brief +author: "Fatih Guner" +--- + +# Competitive Threat Diagnosis + +Sun Tzu wrote that every battle is won before it is fought. The corollary, less quoted but more useful, is that most battles are lost because the general misidentified the enemy. A founder screaming "competitors are crushing us" may be fighting a price war when the real threat is a substitute technology. Another, panicking about a big-tech entrant, may be overlooking the fact that the entrant's strategy validates the market rather than destroys it. Competitive anxiety is universal among entrepreneurs. Accurate competitive diagnosis is not. + +--- + +## Entry Symptoms + +Founders experiencing competitive pressure typically present with one of these complaints: + +- **"Competitors are crushing us"** -- Revenue or growth declining relative to known rivals +- **"Price war"** -- Margins compressing as competitors undercut on price +- **"We're losing market share"** -- Customer acquisition slowing while the market grows +- **"A big player just entered our space"** -- An established company (often with asymmetric resources) has launched a competing product +- **"We're being commoditized"** -- Customers treat the product as interchangeable with alternatives + +The instinct is to react tactically: cut prices, add features, increase ad spend. The diagnostic below determines whether the problem is tactical, structural, or existential. + +--- + +## Triage Questions + +### Level 1: Threat Classification + +**Q1: Who exactly is the threat -- a direct competitor, an adjacent player expanding into your space, or a new entrant with a fundamentally different model?** +- Direct competitor (same product, same market) --> Proceed to Q2. +- Adjacent player (different product, overlapping market) --> Proceed to Q4. +- New entrant with a different model (lower price point, different distribution, new technology) --> **Diagnosis: Disruptive Entrant.** Proceed to Q5 for severity assessment. + +### Level 2: Direct Competition Dynamics + +**Q2: Is the competition primarily on price or on value (features, brand, experience, switching costs)?** +- Price --> **Diagnosis: Price Commoditization.** When the only differentiator is the number on the invoice, the industry has a structural problem, not a sales problem. +- Value, but you are losing --> Proceed to Q3. + +**Q3: Can you articulate -- in one sentence -- why a customer should choose you over the closest alternative?** +- No / the answer sounds generic --> **Diagnosis: Differentiation Failure.** If you cannot articulate the difference, customers certainly cannot perceive it. +- Yes, but customers still leave --> **Diagnosis: Moat Erosion.** The differentiator exists but is not defensible. Competitors have replicated or neutralized it. + +### Level 3: Adjacent and Structural Threats + +**Q4: Is the adjacent player entering your market because it is growing, or are they cannibalizing a shrinking market?** +- Growing market --> **Diagnosis: Wrong Competitive Arena.** You may be competing on the wrong dimension. The adjacent player sees an opportunity you have not framed correctly. +- Shrinking or consolidating market --> **Diagnosis: Market Category Collapse.** The category itself is contracting, and the adjacent player is absorbing what remains. + +**Q5: Does the disruptive entrant serve the same customers or different (typically lower-end or non-consumers)?** +- Same customers, lower price --> **Diagnosis: Disruptive Entrant** (classic low-end disruption). The threat is existential if unaddressed. +- Different customers, expanding the market --> The threat is real but slower. You have time to respond strategically, not reactively. + +### Level 4: Moat Assessment + +**Q6: What is your defensible advantage -- network effects, proprietary data, switching costs, regulatory barriers, brand, or cost structure?** +- Cannot identify one --> **Diagnosis: Moat Erosion** (or never had a moat). This is the most urgent finding. +- Has one but it is weakening --> **Diagnosis: Moat Erosion.** Identify the specific mechanism of erosion. +- Has a strong moat but still losing share --> Revisit Q2-Q3; the problem may be execution, not strategy. + +--- + +## Diagnosis Map + +| Diagnosis | Core Problem | Typical Pattern | +|-----------|-------------|-----------------| +| **Moat Erosion** | Defensible advantage is weakening or was illusory | Competitors replicate features within months; customer loyalty declining | +| **Price Commoditization** | Market treats offerings as interchangeable | Margins compressing quarter over quarter; RFPs decided on price alone | +| **Disruptive Entrant** | New player with structurally different cost or delivery model | Losing low-end customers first; incumbent advantages becoming liabilities | +| **Wrong Competitive Arena** | Competing on the wrong dimension or in the wrong frame | Adjacent player grows faster by serving the same need differently | +| **Differentiation Failure** | No clear, communicable reason to choose this product | Win rates dropping; customer feedback cites "similar to alternatives" | +| **Market Category Collapse** | The category itself is contracting or being absorbed | Total addressable market shrinking; multiple players exiting simultaneously | + +--- + +## Routing + +- **Moat Erosion** --> `porters-five-forces` (identify which structural forces are shifting), `art-of-war` (positional strategy), `competitive-landscape-brief` (map the field) +- **Price Commoditization** --> `blue-ocean-strategy` (escape the red ocean), `porters-five-forces` (understand buyer power dynamics) +- **Disruptive Entrant** --> `disruptive-innovation` (understand the disruption pattern), `first-mover-strategy` (assess response timing), `competitive-landscape-brief` (map the new entrant's trajectory) +- **Wrong Competitive Arena** --> `blue-ocean-strategy` (redefine the market boundaries), `art-of-war` (choose the right battlefield) +- **Differentiation Failure** --> `blue-ocean-strategy` (ERRC grid to rebuild the value proposition), `competitive-landscape-brief` (articulate the gap) +- **Market Category Collapse** --> `scenario-planning` (model futures), `porters-five-forces` (assess remaining structural viability) + +--- + +## Red Flags + +Stop triage and escalate if any of these conditions emerge: + +- **The founder cannot name their top three competitors.** Competitive ignorance is itself the diagnosis. No framework helps until market awareness exists. +- **Gross margins have been negative for two consecutive quarters with no structural path to profitability.** This is not a competitive threat problem; this is a survival problem. +- **The "competitor" is actually a substitute that eliminates the need for the category entirely.** Kodak's competitor was not Fuji; it was the smartphone camera. Category substitution requires a fundamentally different strategic response than competitive rivalry. +- **The founder's response to every competitive threat is "we'll just add that feature."** Feature parity is not strategy. It is a treadmill that accelerates until someone falls off. +- **Customer churn has exceeded 10% monthly for three consecutive months.** The competitive threat has already metastasized into a retention crisis. Address churn before strategy. diff --git a/plugins/foreman/content/diagnostics/culture-erosion-diagnosis.md b/plugins/foreman/content/diagnostics/culture-erosion-diagnosis.md new file mode 100644 index 0000000..cc227cb --- /dev/null +++ b/plugins/foreman/content/diagnostics/culture-erosion-diagnosis.md @@ -0,0 +1,120 @@ +--- +name: "culture-erosion-diagnosis" +description: "Diagnoses why organizational culture is deteriorating by distinguishing between hypergrowth dilution, leadership-culture gaps, values-behavior disconnects, remote culture decay, post-acquisition identity crises, and toxic subcultures. Routes to the appropriate culture, change management, or team dynamics framework." +entry_symptoms: + - "Culture is breaking" + - "Values feel hollow" + - "We've lost our identity" + - "New hires don't fit" + - "The vibe has changed" +possible_diagnoses: + - hypergrowth-dilution + - leadership-culture-gap + - values-behavior-disconnect + - remote-culture-decay + - post-acquisition-identity-crisis + - toxic-subculture +routes_to_skills: + - organisational-culture + - team-culture-and-dynamics + - kotter-change-model +routes_to_templates: + - culture-values-document +author: "Fatih Guner" +--- + +# Culture Erosion Diagnosis + +Netflix famously published a 125-slide culture deck that became, in Sheryl Sandberg's words, "the most important document ever to come out of Silicon Valley." Less discussed is the fact that Netflix has revised that document repeatedly -- because culture is not a manifesto pinned to a wall. It is the aggregate of daily behaviors, reward structures, hiring decisions, and the stories people tell about what actually happens versus what the handbook claims. When founders say "our culture is breaking," they are observing a gap between the organization they intended to build and the one that now exists. The diagnostic challenge is determining where the fracture originated and whether it can be repaired -- or whether the original culture was a founding myth that never scaled. + +--- + +## Entry Symptoms + +Culture erosion surfaces through specific complaints, each pointing to a different failure: + +- **"Culture is breaking"** -- A general sense that organizational norms have shifted in an undesirable direction +- **"Values feel hollow"** -- Stated values exist but no longer describe actual behavior +- **"We've lost our identity"** -- The company feels unrecognizable to long-tenured employees +- **"New hires don't fit"** -- Recent additions to the team operate by different norms +- **"The vibe has changed"** -- An atmospheric shift that employees can feel but struggle to articulate + +These complaints are often dismissed as nostalgia or growing pains. They should not be. + +--- + +## Triage Questions + +### Level 1: Trigger Identification + +**Q1: Did something specific trigger this change -- rapid hiring, a leadership transition, a shift to remote/hybrid work, or an acquisition/merger?** +- Rapid hiring (headcount doubled or more within 12 months) --> **Diagnosis: Hypergrowth Dilution.** Proceed to Q2 for severity. +- Leadership change (new C-suite, founder departure, new board influence) --> Proceed to Q3. +- Remote/hybrid transition --> **Diagnosis: Remote Culture Decay.** Proceed to Q4. +- Acquisition or merger --> **Diagnosis: Post-Acquisition Identity Crisis.** Proceed to Q5. +- No identifiable trigger / gradual drift --> Proceed to Q2. + +### Level 2: Scope and Depth + +**Q2: Is the culture problem company-wide or localized to specific teams, departments, or offices?** +- Company-wide --> The erosion is systemic. Proceed to Q3. +- Localized --> **Diagnosis: Toxic Subculture.** A specific team or leader is operating by norms that deviate from the organization's. This is a management problem, not a culture redesign problem. + +### Level 3: Values Integrity + +**Q3: Are the company's stated values being violated -- or were they aspirational statements that never described reality?** +- Being violated (behavior used to match values; now it does not) --> **Diagnosis: Values-Behavior Disconnect.** Something broke. The values were real but are no longer being reinforced. +- Never fully real (values were written during a branding exercise, not extracted from actual behavior) --> **Diagnosis: Leadership-Culture Gap.** The culture was never what leadership claimed. Growth simply made the gap visible. + +**Q3b: Do the senior leaders personally model the stated values in their daily decisions?** +- No --> **Diagnosis: Leadership-Culture Gap.** Culture flows downhill. When leaders exempt themselves from the values they espouse, the organization learns that the values are decorative. +- Yes, but culture still eroding --> The reinforcement mechanisms (hiring, promotions, terminations, rituals) have broken. Proceed to Q4. + +### Level 4: Mechanism Assessment + +**Q4: Which of these cultural transmission mechanisms has failed?** + +| Mechanism | Healthy Signal | Broken Signal | +|-----------|---------------|---------------| +| **Hiring** | Values-fit is weighted in interviews | "We just need bodies" / pure skills hiring | +| **Onboarding** | New hires absorb norms within 90 days | New hires operate by previous employer's norms indefinitely | +| **Promotion** | Culture carriers are promoted; culture violators are not | Highest performers promoted regardless of values alignment | +| **Storytelling** | Org legends reinforce values | No one tells founding stories; or stories contradict values | +| **Rituals** | Regular practices embody the culture | Rituals abandoned, replaced by nothing, or performed emptily | +| **Consequences** | Values violations carry real consequences | Violations tolerated for high performers or politically connected | + +Multiple broken mechanisms suggest systemic erosion. A single failure is surgically repairable. + +## Diagnosis Map + +| Diagnosis | Core Problem | Distinguishing Signal | +|-----------|-------------|----------------------| +| **Hypergrowth Dilution** | New hires outnumber culture carriers; norms cannot transmit fast enough | Headcount growth outpaced onboarding and cultural integration capacity | +| **Leadership-Culture Gap** | Leaders do not embody the values they espouse | "Do as I say, not as I do" pattern visible to the organization | +| **Values-Behavior Disconnect** | Values were once real but enforcement mechanisms eroded | Long-tenured employees feel betrayed; recent hires see no problem | +| **Remote Culture Decay** | Physical distance degraded informal cultural transmission | Culture weakened specifically after remote/hybrid transition | +| **Post-Acquisition Identity Crisis** | Two organizational identities colliding without resolution | "Us vs. them" dynamics between legacy and acquired teams | +| **Toxic Subculture** | A localized group operates by deviant norms | Problem concentrated in specific teams; rest of org functions normally | + +--- + +## Routing + +- **Hypergrowth Dilution** --> `organisational-culture` (rebuild transmission mechanisms), `culture-values-document` (codify what was previously implicit), `team-culture-and-dynamics` (restore team-level norms) +- **Leadership-Culture Gap** --> `organisational-culture` (align leader behavior with stated values), `kotter-change-model` (structured cultural change initiative from the top) +- **Values-Behavior Disconnect** --> `culture-values-document` (refresh and re-ratify values with current organization), `team-culture-and-dynamics` (rebuild enforcement rituals) +- **Remote Culture Decay** --> `team-culture-and-dynamics` (design remote-native cultural practices), `organisational-culture` (adapt transmission mechanisms for distributed work) +- **Post-Acquisition Identity Crisis** --> `kotter-change-model` (manage the cultural integration as an explicit change initiative), `organisational-culture` (forge a new shared identity) +- **Toxic Subculture** --> `team-culture-and-dynamics` (intervene at the team level), `organisational-culture` (reinforce organizational norms to contain the deviation) + +--- + +## Red Flags + +Address these conditions before proceeding with any cultural framework: + +- **Key culture carriers are leaving.** When the people who embody the culture exit, erosion accelerates exponentially. Retaining these individuals is more urgent than any culture document. +- **The founder says "culture is fine" while employees say otherwise.** This perception gap is itself the diagnosis. Surface anonymous pulse surveys or exit interview data immediately. +- **A single toxic leader is responsible for the erosion.** No framework repairs culture while the source of toxicity holds authority. This is a personnel decision, not a culture initiative. +- **The company has never written down its values.** Oral tradition works at 10 people. At 50, it fragments. At 200, it is mythology. Codification is prerequisite, not luxury. +- **Engagement scores dropped more than 20 points in a single quarter.** This pace indicates acute crisis, not gradual erosion. Investigate for a precipitating event before applying general culture frameworks. diff --git a/plugins/foreman/content/diagnostics/customer-churn-diagnosis.md b/plugins/foreman/content/diagnostics/customer-churn-diagnosis.md new file mode 100644 index 0000000..5afe69a --- /dev/null +++ b/plugins/foreman/content/diagnostics/customer-churn-diagnosis.md @@ -0,0 +1,118 @@ +--- +name: "customer-churn-diagnosis" +description: "Identifies the root cause of customer attrition by distinguishing between onboarding failures, value plateau, competitor displacement, price sensitivity, product regression, and champion departure. Use when an entrepreneur reports declining retention, rising cancellation rates, or unexplained customer loss." +entry_symptoms: + - "Customers leaving" + - "Renewal rates dropping" + - "Can't figure out why they churn" + - "Lost key accounts" + - "Usage declining before cancellation" +possible_diagnoses: + - onboarding-failure + - value-plateau + - competitor-displacement + - price-sensitivity + - product-regression + - champion-departure +routes_to_skills: + - net-promoter-score + - four-ps-marketing + - product-life-cycle + - business-model-canvas + - employee-engagement-retention +routes_to_templates: + - quarterly-business-review + - case-study-template +author: "Fatih Guner" +--- + +# Customer Churn Diagnosis + +## Entry Symptoms + +Customers are leaving, and the reasons remain opaque. The entrepreneur reports some combination of: "Renewal rates are dropping," "We lost three key accounts last quarter," "Usage declines and then they cancel," or "We just can't figure out why they churn." The instinct is to blame the product or the market — but churn is a symptom with at least six distinct underlying causes, and treating the wrong one accelerates the problem. + +## Triage Questions + +### Q1: When do customers churn relative to their lifecycle? + +- **Within the first 30 days** — the customer never reached the value moment. Proceed to Q2. Likely diagnosis: **onboarding-failure**. +- **Between 3 and 6 months** — the customer found initial value but hit a ceiling. Proceed to Q3. Likely diagnosis: **value-plateau**. +- **After 12+ months, typically at renewal** — something shifted in the customer's context. Proceed to Q5 and Q6. + +### Q2: Is churn voluntary or involuntary? + +- **Voluntary (customer actively cancels)** — the product disappointed relative to expectations. Proceed to Q3. +- **Involuntary (payment failure, credit card expiry, procurement lapse)** — this is a billing infrastructure problem, not a strategic one. Fix payment recovery before diagnosing further. +- **Unclear — customers go silent and stop using** — usage data will reveal whether this is apathy (never activated) or abandonment (activated then disengaged). Proceed to Q4. + +### Q3: What do exit interviews or cancellation surveys reveal? + +- **"Too expensive for what we get"** — likely diagnosis: **price-sensitivity**. The value-to-cost equation broke down. +- **"We found a better alternative"** — likely diagnosis: **competitor-displacement**. Confirm with Q6. +- **"We got what we needed" or "Our needs changed"** — likely diagnosis: **value-plateau**. The product served a bounded purpose. +- **"The product got worse" or "Too many bugs/changes"** — likely diagnosis: **product-regression**. Confirm with Q4. +- **No exit data available** — this itself is a red flag. Instrument cancellation flows before proceeding. + +### Q4: What does usage data show in the 60 days before cancellation? + +- **Usage was never high — the customer barely activated** — likely diagnosis: **onboarding-failure**. They bought but never adopted. +- **Usage was strong then dropped sharply** — something broke. Either a product change (diagnosis: **product-regression**) or a personnel change at the customer (diagnosis: **champion-departure**). Proceed to Q5. +- **Usage declined gradually over months** — the product's utility wore thin. Likely diagnosis: **value-plateau**. + +### Q5: Is churn concentrated in a specific segment, cohort, or account type? + +- **Yes, concentrated in a segment (e.g., small accounts, a specific industry)** — the product may serve some segments well but fail others. Likely diagnosis: **price-sensitivity** (if small accounts) or **value-plateau** (if a segment has outgrown the product). +- **Yes, concentrated in a recent cohort** — something changed in onboarding, product, or positioning. Compare with earlier cohorts to isolate the variable. +- **No pattern — churn is distributed evenly** — proceed to Q6. The cause is likely systemic rather than segment-specific. + +### Q6: Are churned customers going to competitors, building internally, or simply stopping? + +- **Going to a named competitor** — likely diagnosis: **competitor-displacement**. Analyse the competitor's advantage: price, features, or positioning. +- **Building an internal solution or hiring for the capability** — likely diagnosis: **value-plateau**. Customers outgrew the product and can justify the investment to replace it. +- **Just stopping — no replacement** — the problem the product solved may have diminished in urgency. Likely diagnosis: **price-sensitivity** or a market-level shift. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Onboarding failure** | Churn within 30 days, low activation, minimal usage from day one | Q1 shows early churn + Q4 shows no activation | +| **Value plateau** | Churn at 3-6 months, gradual usage decline, "got what we needed" in exit surveys | Q1 shows mid-lifecycle churn + Q3 confirms bounded value | +| **Competitor displacement** | Customers name an alternative, feature comparisons circulating, competitor gaining share | Q3 names competitor + Q6 confirms destination | +| **Price sensitivity** | Small accounts over-represented in churn, "too expensive" in surveys, discounting requests before cancellation | Q3 cites cost + Q5 shows segment concentration | +| **Product regression** | Churn correlates with product changes, sharp usage drops, "it got worse" feedback | Q3 cites quality + Q4 shows sudden usage cliff | +| **Champion departure** | Key contact left the customer organisation, usage drops immediately after personnel change | Q4 shows sharp drop + Q6 shows no competitive switch | + +## Routing + +**Onboarding failure:** +1. Apply `business-model-canvas` — re-examine the value proposition and whether marketing promises match product reality +2. Apply `net-promoter-score` — survey surviving early-stage customers to benchmark the onboarding experience +3. Output with `case-study-template` — document successful onboarding patterns for replication +**Value plateau:** +1. Apply `product-life-cycle` — determine whether the product needs extension, reinvention, or portfolio expansion +2. Apply `business-model-canvas` — identify adjacent value the product could deliver to extend utility +3. Output with `quarterly-business-review` +**Competitor displacement:** +1. Apply `four-ps-marketing` — audit positioning, pricing, and distribution against the named competitor +2. Apply `net-promoter-score` — quantify the loyalty gap between your retained customers and those who left +3. Output with `quarterly-business-review` +**Price sensitivity:** +1. Apply `four-ps-marketing` — reconstruct the price-to-value equation across segments +2. Apply `business-model-canvas` — explore packaging, tiering, or usage-based models that align price with delivered value +3. Output with `quarterly-business-review` +**Product regression:** +1. Apply `net-promoter-score` — measure sentiment across customer cohorts before and after product changes +2. Apply `product-life-cycle` — assess whether regression is a temporary setback or a structural decline +3. Output with `case-study-template` — document the regression and recovery plan +**Champion departure:** +1. Apply `employee-engagement-retention` (applied to customer relationships) — build multi-threaded relationships that survive personnel changes +2. Apply `net-promoter-score` — identify accounts with single-threaded dependencies before the champion leaves +3. Output with `quarterly-business-review` + +## Red Flags + +- **Churn rate exceeds 5% monthly with no exit data.** Flying blind at this velocity means the company is haemorrhaging customers without learning. Instrument cancellation flows and exit surveys before applying any framework. +- **The entrepreneur cannot produce cohort retention curves.** Without quantified retention by cohort, any diagnosis is guesswork. Establish measurement infrastructure first. +- **Net revenue retention is below 80%.** At this level, no amount of acquisition can sustain the business. The product itself must be interrogated. +- **The company has fewer than 50 customers and calls it "churn."** At small customer counts, individual losses are case studies, not statistical trends. diff --git a/plugins/foreman/content/diagnostics/decision-paralysis-diagnosis.md b/plugins/foreman/content/diagnostics/decision-paralysis-diagnosis.md new file mode 100644 index 0000000..4f2f87d --- /dev/null +++ b/plugins/foreman/content/diagnostics/decision-paralysis-diagnosis.md @@ -0,0 +1,118 @@ +--- +name: "decision-paralysis-diagnosis" +description: "Diagnoses why an entrepreneur is stuck on a critical decision by distinguishing between information deficits, emotional hijacking, flawed problem framing, fear of irreversibility, stakeholder conflict, and perfectionism. Routes to the appropriate thinking, decision-making, or clarity framework." +entry_symptoms: + - "I can't decide" + - "Should I pivot?" + - "Analysis paralysis" + - "Every option seems risky" + - "I keep going back and forth" +possible_diagnoses: + - information-deficit + - emotional-default-hijack + - wrong-problem-framing + - fear-of-irreversibility + - stakeholder-conflict + - perfectionism-trap +routes_to_skills: + - enemies-of-clear-thinking + - defining-and-exploring-problems + - evaluating-and-deciding + - decision-traps-and-roles + - tough-decision-situations +routes_to_templates: + - decision-journal +author: "Fatih Guner" +--- + +# Decision Paralysis Diagnosis + +Do not dismiss a stated irreversible risk before identifying the actual commitments. Treat the cause of hesitation as a hypothesis. Bound any experiment to the founder's runway, time and resources instead of inventing a universal duration. + +Jeff Bezos distinguishes between Type 1 decisions (irreversible, consequential -- walk through a one-way door) and Type 2 decisions (reversible, low-cost -- walk through a two-way door and come back if it does not work). Most founders treat every decision as Type 1. The result is not prudence but paralysis -- weeks of deliberation over choices that could be tested in days, board meetings to resolve questions that a single phone call would answer. Worse, genuine Type 1 decisions receive the same agonized treatment, diluted by decision fatigue from all the false alarms. This diagnostic determines what is actually preventing the decision and whether the blockage is rational, emotional, structural, or self-imposed. + +--- + +## Entry Symptoms + +Decision paralysis presents with characteristic language: + +- **"I can't decide"** -- The founder has identified options but cannot commit to one +- **"Should I pivot?"** -- A specific high-stakes decision with existential overtones +- **"Analysis paralysis"** -- Self-aware recognition that deliberation has replaced action +- **"Every option seems risky"** -- Risk aversion masquerading as thoroughness +- **"I keep going back and forth"** -- Oscillation between options without new information + +The common mistake is treating all of these as the same problem. They are not. A founder who lacks information needs data. A founder paralyzed by fear needs a different intervention entirely. + +--- + +## Triage Questions + +### Level 1: Decision Classification + +**Q1: Is this decision reversible or irreversible?** +- Reversible (can be undone within weeks/months at manageable cost) --> Flag this. Many "agonizing" decisions are actually two-way doors. If reversible, the prescription is often simply: decide now, measure, adjust. +- Irreversible or very costly to reverse --> Proceed to Q2. Deeper triage is warranted. + +**Q2: How long have you been deliberating on this decision?** +- Less than one week --> Likely appropriate deliberation. Confirm the decision warrants this level of analysis and proceed to Q3. +- One to four weeks --> The cost of delay is accumulating. Proceed to Q3 with urgency. +- More than one month --> **The delay itself has become a decision** -- a decision to maintain the status quo. This must be named explicitly. Proceed to Q3. + +### Level 2: Nature of the Blockage + +**Q3: What specific information, if you had it, would make this decision obvious?** +- Founder can name specific missing data --> **Diagnosis: Information Deficit.** The paralysis is rational. Go get the data. +- Founder cannot identify what additional information would help --> The blockage is not informational. Proceed to Q4. + +**Q4: When you imagine choosing Option A, what is the first feeling that arises? And Option B?** +- Fear, dread, anxiety dominate --> Proceed to Q5 (emotional assessment). +- Frustration or confusion dominate --> Proceed to Q6 (framing assessment). +- Different stakeholders advocate for different options --> **Diagnosis: Stakeholder Conflict.** The founder is not personally paralyzed; the organization is. + +### Level 3: Emotional vs. Cognitive Blockage + +**Q5: Is the fear about a specific, concrete consequence -- or is it a general sense of "what if I'm wrong"?** +- Specific consequence (e.g., "We'll run out of money," "My co-founder will leave") --> **Diagnosis: Fear of Irreversibility.** The fear is pointing at a real risk. Quantify it, mitigate it, then decide. +- General, diffuse anxiety --> **Diagnosis: Emotional Default Hijack.** The emotion, ego, social, or inertia defaults (per the Clear Thinking framework) have seized the controls. The founder knows what to do but cannot bring themselves to do it. + +**Q6: Have you clearly defined what problem this decision is solving? Can you state it in one sentence?** +- No / the definition keeps shifting --> **Diagnosis: Wrong Problem Framing.** The paralysis exists because the founder is trying to answer the wrong question. Reframe first, decide second. +- Yes, clearly defined, but still stuck --> **Diagnosis: Perfectionism Trap.** The founder is waiting for a risk-free option that does not exist. Every viable path carries uncertainty, and the refusal to accept imperfection has become the obstacle. + +--- + +## Diagnosis Map + +| Diagnosis | Core Problem | Distinguishing Signal | +|-----------|-------------|----------------------| +| **Information Deficit** | Genuine missing data prevents rational choice | Founder can name the specific data that would resolve the decision | +| **Emotional Default Hijack** | Fear, ego, social pressure, or inertia has overridden judgment | Founder knows the "right" answer but cannot act on it | +| **Wrong Problem Framing** | The decision question itself is malformed | Problem definition keeps shifting; "the more I think about it, the more confused I get" | +| **Fear of Irreversibility** | A specific catastrophic outcome dominates thinking | Founder fixates on one worst-case scenario to the exclusion of all other analysis | +| **Stakeholder Conflict** | Multiple parties advocate incompatible paths | Founder oscillates based on who they spoke with last | +| **Perfectionism Trap** | Refusal to accept any option with imperfections | All options have been thoroughly analyzed; none is "good enough" | + +--- + +## Routing + +- **Information Deficit** --> `defining-and-exploring-problems` (structure what you need to learn), `evaluating-and-deciding` (decision matrix once data arrives), `decision-journal` (document assumptions and track outcomes) +- **Emotional Default Hijack** --> `enemies-of-clear-thinking` (identify which default is active), `building-thinking-strength` (develop the counter-discipline), `decision-journal` (separate emotion from analysis on paper) +- **Wrong Problem Framing** --> `defining-and-exploring-problems` (reframe the question), `decision-traps-and-roles` (check for anchoring and framing biases) +- **Fear of Irreversibility** --> `tough-decision-situations` (structured approach to high-stakes choices), `evaluating-and-deciding` (risk quantification), `scenario-planning` (model the feared outcome) +- **Stakeholder Conflict** --> `decision-traps-and-roles` (RAPID model for decision rights), `tough-decision-situations` (consensus vs. authority decisions) +- **Perfectionism Trap** --> `enemies-of-clear-thinking` (name the pattern), `choosing-and-executing` (the 70% rule -- act when 70% confident), `decision-journal` (record the decision and revisit later) + +--- + +## Red Flags + +Halt triage and address these conditions directly: + +- **The decision has a hard deadline within 48 hours.** Triage itself is a luxury the founder cannot afford. Skip to `tough-decision-situations` immediately. +- **The founder has made and reversed the same decision more than twice.** Oscillation erodes team confidence faster than a wrong decision does. The problem is no longer the decision itself but the founder's credibility as a decision-maker. +- **Cash runway is less than 3 months and the decision involves resource allocation.** This is a survival decision, not a strategic one. Different rules apply -- specifically, preserve optionality and minimize burn. +- **The founder is making this decision alone but it affects the entire company.** Decision paralysis in isolation often resolves when the founder involves one or two trusted advisors. Loneliness amplifies every cognitive bias. +- **Physical symptoms of stress (insomnia, inability to focus, health deterioration) accompany the paralysis.** Route to `founder-mental-health-check` before any strategic framework. A burned-out mind cannot make clear decisions regardless of the tools provided. diff --git a/plugins/foreman/content/diagnostics/fundraising-diagnosis.md b/plugins/foreman/content/diagnostics/fundraising-diagnosis.md new file mode 100644 index 0000000..f11993a --- /dev/null +++ b/plugins/foreman/content/diagnostics/fundraising-diagnosis.md @@ -0,0 +1,122 @@ +--- +name: "fundraising-diagnosis" +description: "Diagnoses why fundraising efforts are failing by distinguishing between pitch problems, fundamentals problems, timing problems, and targeting problems. Determines whether the entrepreneur is ready to raise, raising from the right investors, asking for the right amount, or telling the right story." +entry_symptoms: + - "Investors keep saying no" + - "I can't raise money" + - "My pitch isn't working" + - "VCs ghost me" + - "Valuation pushback" +possible_diagnoses: + - premature-fundraising + - wrong-investor-targeting + - weak-pitch-story + - unrealistic-valuation + - missing-traction-proof + - timing-mismatch +routes_to_skills: + - business-model-canvas + - storytelling-for-leaders + - story-structure-and-arc + - building-story-stakes +routes_to_templates: + - fundraising-deck-outline + - unit-economics-snapshot + - competitive-landscape-brief +author: "Fatih Guner" +--- + +# Fundraising Diagnosis + +First establish the funding stage, purpose and constraints. Required evidence varies by investor and stage; do not tell every pre-seed founder that existing revenue or mature unit economics are prerequisites. + +Ninety percent of fundraising failures are misdiagnosed. The founder assumes the pitch deck needs better graphics. The advisor suggests more networking. The accelerator recommends "getting your story right." Meanwhile, the actual problem -- no product-market fit, no defensible unit economics, or a valuation that insults the intelligence of anyone who can operate a spreadsheet -- goes unaddressed. A polished pitch for a fundamentally unfundable business is still unfundable. This diagnostic separates the signal from the noise. + +--- + +## Entry Symptoms + +A founder presenting with fundraising difficulty typically articulates the problem in one of these forms: + +- **"Investors keep saying no"** -- Repeated rejection across multiple meetings, often without clear feedback +- **"My pitch isn't working"** -- Meetings happen but never convert to term sheets +- **"VCs ghost me"** -- Initial interest evaporates; follow-up emails go unanswered +- **"Valuation pushback"** -- Investors express interest but dispute the ask +- **"I can't raise money"** -- General inability to close a round despite sustained effort + +Each symptom maps to a different root cause. The triage below determines which. + +--- + +## Triage Questions + +### Level 1: Readiness + +**Q1: Do you have a validated product with paying customers or measurable engagement?** +- No --> **Diagnosis: Premature Fundraising.** Most institutional investors require evidence that someone wants what you are building. Raising before validation is not bold; it is wasteful. +- Yes --> Proceed to Q2. + +**Q2: Can you articulate your unit economics -- CAC, LTV, margins, payback period?** +- No / vague --> **Diagnosis: Missing Traction Proof.** Investors hear "we're growing" constantly. Without unit economics, growth is indistinguishable from spending. +- Yes --> Proceed to Q3. + +### Level 2: Targeting + +**Q3: Have you researched whether the investors you are pitching actually invest at your stage, in your sector, at your check size?** +- No / uncertain --> **Diagnosis: Wrong Investor Targeting.** Pitching a seed-stage SaaS company to a growth-stage biotech fund is not fundraising; it is spam. +- Yes --> Proceed to Q4. + +**Q4: Are investors engaging with the substance of your business, or does the conversation stall at the pitch level?** +- Stalls at pitch level --> Proceed to Q5 (pitch assessment). +- Engages with substance but does not convert --> Proceed to Q6 (terms assessment). + +### Level 3: Pitch vs. Fundamentals + +**Q5: When investors pass, do they cite the market, the team, or the traction -- or do they seem disengaged from the start?** +- Disengaged from the start --> **Diagnosis: Weak Pitch / Story.** The narrative fails to create tension, stakes, or a compelling reason to act now. +- Cite specific concerns about market, team, or traction --> **Diagnosis: Missing Traction Proof** or **Premature Fundraising.** The pitch is working; the fundamentals are not. + +### Level 4: Terms and Timing + +**Q6: Is the pushback primarily about valuation, round size, or deal structure?** +- Valuation too high --> **Diagnosis: Unrealistic Valuation.** The gap between your self-assessment and the market's assessment is a data point, not an insult. +- "Not right now" / "Come back when..." --> **Diagnosis: Timing Mismatch.** The fundraising window, market conditions, or your milestone trajectory does not align with investor deployment cycles. +- Round size mismatch --> Revisit investor targeting (Q3). + +--- + +## Diagnosis Map + +| Diagnosis | Core Problem | Key Indicator | +|-----------|-------------|---------------| +| **Premature Fundraising** | No product-market fit yet | No paying customers, no retention data, no usage metrics | +| **Wrong Investor Targeting** | Pitching investors mismatched to stage, sector, or size | High volume of meetings, zero follow-through | +| **Weak Pitch / Story** | Narrative fails to land | Investor attention drops within first five minutes; no emotional hook | +| **Unrealistic Valuation** | Price-to-proof ratio is inverted | Investors engage deeply but balk at terms | +| **Missing Traction Proof** | Growth claims lack supporting data | Investors ask for metrics you cannot produce | +| **Timing Mismatch** | Market cycle, fund cycle, or milestone cycle misaligned | "Interesting, but not now" repeated across multiple funds | + +--- + +## Routing + +Based on the diagnosis, route the entrepreneur to these skills and templates: + +- **Premature Fundraising** --> `business-model-canvas` (validate the model), `unit-economics-snapshot` (build the proof) +- **Wrong Investor Targeting** --> `competitive-landscape-brief` (understand your market positioning to identify aligned investors) +- **Weak Pitch / Story** --> `storytelling-for-leaders` + `story-structure-and-arc` + `building-story-stakes` (rebuild the narrative), `fundraising-deck-outline` (restructure the deck) +- **Unrealistic Valuation** --> `unit-economics-snapshot` (ground the valuation in data), `business-model-canvas` (stress-test assumptions) +- **Missing Traction Proof** --> `unit-economics-snapshot` (build the metrics dashboard), `business-model-canvas` (identify what to measure) +- **Timing Mismatch** --> `competitive-landscape-brief` (map the market moment), `scenario-planning` (model alternative timelines) + +--- + +## Red Flags + +Intervene immediately if any of the following surface during triage: + +- **Founder has been raising for more than 9 months without a term sheet.** The market has rendered a verdict. Continuing without fundamental change is not persistence; it is denial. +- **Founder cannot name a single comparable company's fundraising trajectory.** Insufficient market research that investors detect instantly. +- **Founder blames all rejections on investor ignorance.** Occasionally true for novel categories. Usually a defense mechanism that prevents learning. +- **Founder is raising to cover operating expenses with no growth plan.** Bridge financing without a destination -- a category investors actively avoid. +- **Personal financial desperation is driving the timeline.** Desperate founders accept terrible terms. Explore alternative funding (revenue, grants, debt) before negotiating from weakness. diff --git a/plugins/foreman/content/diagnostics/growth-stall-diagnosis.md b/plugins/foreman/content/diagnostics/growth-stall-diagnosis.md new file mode 100644 index 0000000..50e8683 --- /dev/null +++ b/plugins/foreman/content/diagnostics/growth-stall-diagnosis.md @@ -0,0 +1,124 @@ +--- +name: "growth-stall-diagnosis" +description: "Determines why a company's growth has plateaued by distinguishing between market saturation, operational bottlenecks, product maturity, team scaling failures, competitive displacement, and channel exhaustion. Use when an entrepreneur reports stalled momentum despite earlier traction." +entry_symptoms: + - "Growth has plateaued" + - "We've hit a ceiling" + - "We can't scale past X" + - "Early traction but stuck now" + - "What worked before stopped working" +possible_diagnoses: + - market-saturation + - operational-bottleneck + - product-maturity + - team-scaling-failure + - competitive-displacement + - channel-exhaustion +routes_to_skills: + - ambidexterity + - growth-share-matrix + - disruptive-innovation + - product-life-cycle + - blue-ocean-strategy + - porters-five-forces +routes_to_templates: + - strategic-analysis-one-pager + - new-initiative-brief + - market-opportunity-summary +author: "Fatih Guner" +--- + +# Growth Stall Diagnosis + +## Entry Symptoms + +The entrepreneur describes a loss of momentum: "Growth has plateaued," "We hit a ceiling," or "The playbook that got us here stopped working." Revenue may still be positive, but the growth rate is decelerating — and the founder cannot pinpoint why. + +## Triage Questions + +### Q1: Where exactly is growth stalling? + +- **User or customer acquisition** — fewer new customers per period. Proceed to Q3. +- **Revenue per customer** — customers arrive but spend less or don't expand. Proceed to Q4. +- **Team and operational capacity** — demand exists but the organisation cannot fulfil it. Proceed to Q5. + +### Q2: What specifically worked before that stopped working? + +- **A single acquisition channel drove most growth, and it plateaued** — likely diagnosis: **channel-exhaustion**. Confirm with Q3. +- **The product was the growth engine (virality, word of mouth), and that faded** — likely diagnosis: **product-maturity**. Confirm with Q4. +- **The founding team did everything, and that stopped scaling** — likely diagnosis: **team-scaling-failure**. Confirm with Q5. +- **Nothing specific changed — growth gradually decelerated** — likely diagnosis: **market-saturation**. Confirm with Q3 and Q6. + +### Q3: Has the addressable market shifted or contracted? + +- **TAM unchanged, but our share of new customers is shrinking** — a competitor is capturing what was yours. Likely diagnosis: **competitive-displacement**. Confirm with Q6. +- **Early adopters saturated and mainstream customers aren't converting** — likely diagnosis: **market-saturation**. +- **Adjacent markets exist, but we haven't entered them** — likely diagnosis: **channel-exhaustion**. The growth engine needs a new vector. + +### Q4: Is the product still generating enthusiasm among customers? + +- **Usage metrics declining — engagement, frequency, or NPS trending down** — likely diagnosis: **product-maturity**. The offering has run its course in current form. +- **Customers satisfied but not expanding** — the product serves a fixed need. Likely diagnosis: **market-saturation** at the account level. +- **Customers request features you haven't built** — the product needs evolution, not replacement. This is an operational bottleneck, not maturity. + +### Q5: Is the team the bottleneck or the market? + +- **We have demand we can't serve — hiring, onboarding, or processes are too slow** — likely diagnosis: **operational-bottleneck**. Growth is constrained by internal capacity. +- **We hired aggressively but quality and velocity dropped** — likely diagnosis: **team-scaling-failure**. The organisation outgrew its management structures. +- **The team is capable, but there's nothing more to capture in current channels** — the team is not the constraint. Return to Q3 and Q6 for market-level diagnosis. + +### Q6: What has changed in the competitive landscape? + +- **A well-funded competitor entered with a similar or superior product** — likely diagnosis: **competitive-displacement**. Your differentiation has eroded. +- **The category itself is commoditising — multiple players, price pressure, feature parity** — likely diagnosis: **market-saturation** compounded by commoditisation. +- **No significant competitive change** — the stall is internal. The constraint is operational, product, or channel — not market. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Market saturation** | Early adopters captured, mainstream won't convert, TAM ceiling visible | Q3 confirms segment saturation + Q6 shows commoditisation | +| **Operational bottleneck** | Demand exists, fulfilment lags, hiring or process is the constraint | Q5 confirms capacity gap + Q1 shows demand present | +| **Product maturity** | Engagement declining, NPS flat or falling, feature requests dry up | Q4 confirms enthusiasm waning + Q2 shows product was the engine | +| **Team scaling failure** | Hired fast, quality dropped, management stretched, culture diluted | Q5 confirms hiring-quality gap + Q2 shows founder-dependency | +| **Competitive displacement** | Market share shrinking, competitor gaining, differentiation lost | Q3 + Q6 confirm competitive entry with superior positioning | +| **Channel exhaustion** | Primary channel saturated, no secondary channels developed | Q2 confirms single-channel dependency + Q3 shows market still exists | + +## Routing + +**Market saturation:** +1. Apply `blue-ocean-strategy` — identify uncontested adjacent market space +2. Apply `growth-share-matrix` — assess portfolio allocation across segments +3. Output with `market-opportunity-summary` + +**Operational bottleneck:** +1. Apply `systems-thinking` — map the constraint and its ripple effects +2. Apply `ambidexterity` — balance exploitation of current model with exploration of scalable alternatives +3. Output with `quarterly-strategic-review` + +**Product maturity:** +1. Apply `product-life-cycle` — confirm lifecycle stage and strategic options +2. Apply `disruptive-innovation` — assess whether disruption from below is the path forward +3. Output with `new-initiative-brief` + +**Team scaling failure:** +1. Apply `hackman-enabling-conditions` — diagnose team structure deficits +2. Apply `tuckman-team-stages` — assess where the expanded team sits developmentally +3. Output with `team-health-check` + +**Competitive displacement:** +1. Apply `porters-five-forces` — map the new competitive structure +2. Apply `blue-ocean-strategy` — find differentiation beyond the current arena +3. Output with `strategic-analysis-one-pager` + +**Channel exhaustion:** +1. Apply `four-ps-marketing` — audit distribution and promotion channels +2. Apply `growth-share-matrix` — prioritise channel investment +3. Output with `new-initiative-brief` + +## Red Flags + +- **Growth stalled because of a single customer concentration (more than 30% of revenue from one client).** This is a business risk problem, not a growth strategy problem. Address dependency before optimising for growth. +- **The company is pre-revenue and describing a "growth stall."** There is no growth to stall. Route to product-market fit validation instead. +- **The founder conflates growth rate deceleration with absolute decline.** Growing at 15% instead of 40% is a different problem from shrinking. Calibrate expectations before diagnosing pathology. +- **Regulatory or legal changes caused the stall.** Strategic frameworks cannot override compliance constraints. Engage legal counsel first. diff --git a/plugins/foreman/content/diagnostics/hiring-diagnosis.md b/plugins/foreman/content/diagnostics/hiring-diagnosis.md new file mode 100644 index 0000000..e693f1b --- /dev/null +++ b/plugins/foreman/content/diagnostics/hiring-diagnosis.md @@ -0,0 +1,125 @@ +--- +name: "hiring-diagnosis" +description: "Performs deep-layer triage on hiring problems by distinguishing between pipeline starvation, screening failures, interview theatre, closing gaps, onboarding abandonment, and role-reality mismatches. Use when a first-layer diagnostic identifies talent acquisition or retention issues, or when an entrepreneur reports inability to find, close, or retain hires." +entry_symptoms: + - "Can't find good people" + - "New hires don't stick past 90 days" + - "Onboarding is broken" + - "Hiring is way too slow" + - "We keep getting wrong culture fits" + - "We regret most of our hires" +possible_diagnoses: + - pipeline-starvation + - screening-failure + - interview-theatre + - closing-gap + - onboarding-abandonment + - role-reality-mismatch +routes_to_skills: + - belbin-team-roles + - hackman-enabling-conditions + - understanding-people + - reading-people + - decision-traps-and-roles + - employee-engagement-retention +routes_to_templates: + - hiring-scorecard + - role-description-template + - team-health-check +author: "Fatih Guner" +--- + +# Hiring Diagnosis + +## Entry Symptoms + +Hiring complaints arrive dressed as a talent shortage: "There just aren't good people out there." This is almost never true. The labour market is large; the company's access to it, evaluation of it, and appeal within it are small. When an entrepreneur says "we can't find good people," the diagnostic question is not about the people — it is about which stage of the hiring funnel is broken and why. + +## Triage Questions + +### Q1: Where in the hiring funnel does it break down? + +- **Not enough candidates apply or enter the pipeline** — likely diagnosis: **pipeline-starvation**. Proceed to Q2. +- **Plenty of candidates, but none seem qualified after screening** — likely diagnosis: **screening-failure**. Proceed to Q3. +- **Qualified candidates enter but perform poorly in interviews, or interviewers can't agree** — likely diagnosis: **interview-theatre**. Proceed to Q4. +- **Strong candidates get offers but decline them** — likely diagnosis: **closing-gap**. Proceed to Q5. +- **Hires are made but leave or underperform within 90 days** — likely diagnosis: **onboarding-abandonment** or **role-reality-mismatch**. Proceed to Q6. + +### Q2: What does your employer brand and sourcing strategy look like? + +- **Job posts go on generic boards and the company waits for inbound applications** — passive sourcing in a competitive market yields weak pipelines. Likely diagnosis: **pipeline-starvation** driven by channel failure. +- **Active outreach exists but response rates are under 10%** — the message or the messenger is wrong. Either the role descriptions repel strong candidates or the company has no visible reputation. Likely diagnosis: **pipeline-starvation** driven by brand deficit. +- **The company recruits almost exclusively through personal networks that have been exhausted** — the sourcing strategy scaled with the founders but not the company. Likely diagnosis: **pipeline-starvation** driven by channel dependency. + +### Q3: What criteria are you using to screen candidates, and who defined them? + +- **Criteria were inherited from a job description template or copied from a larger company** — likely diagnosis: **screening-failure**. The filter selects for credentials that correlate with performance at Google, not at a 15-person startup. +- **Criteria are clear but emphasise hard skills almost exclusively** — likely diagnosis: **screening-failure** leading to downstream culture-fit problems. Technical screens catch skill but miss motivation, adaptability, and alignment. +- **Screening criteria change with every hire because nobody documented what "good" looks like** — likely diagnosis: **screening-failure** compounded by **role-reality-mismatch**. Without a stable definition of success, every evaluation is improvised. + +### Q4: Describe your interview process — how many stages, who participates, and how are decisions made? + +- **Unstructured conversations where each interviewer asks whatever they want** — likely diagnosis: **interview-theatre**. Unstructured interviews are the single worst predictor of job performance, yet most startups default to them. +- **Structured process exists but interviewers are untrained and frequently disagree on candidates** — likely diagnosis: **interview-theatre**. The architecture is right but the calibration is absent. +- **One person (usually the founder) makes the final call regardless of team input** — likely diagnosis: **interview-theatre** combined with anchoring bias from `decision-traps-and-roles`. The process exists as performance; authority lives elsewhere. + +### Q5: When strong candidates decline your offer, what reasons do they give? + +- **Compensation — another company offered more** — determine whether comp is below market or the candidate used the offer as leverage. If below market, the problem is budgetary, not diagnostic. If competitive, likely diagnosis: **closing-gap** driven by total package (equity story, mission, role scope). +- **Role uncertainty — they weren't sure what they'd actually be doing** — likely diagnosis: **role-reality-mismatch** manifesting at the offer stage. The job was never clearly defined, and the candidate sensed it. +- **Culture or stage concerns — they worried about chaos, instability, or founder dynamics** — likely diagnosis: **closing-gap** driven by employer brand or interview experience. The process itself communicated dysfunction. + +### Q6: What happens on Day 1 through Day 90 for a new hire? + +- **No structured onboarding — new hires are expected to "figure it out" and "hit the ground running"** — likely diagnosis: **onboarding-abandonment**. Sink-or-swim onboarding selects for self-starters while destroying everyone else — including many strong performers who need context before contributing. +- **Onboarding exists but is administrative (paperwork, tool access, org chart) with no role-specific ramp plan** — likely diagnosis: **onboarding-abandonment**. Logistical onboarding without performance onboarding leaves new hires productive on email and lost on work. +- **New hires report that the actual job differs significantly from what was described in the interview** — likely diagnosis: **role-reality-mismatch**. The gap between promise and reality creates immediate disillusionment and is the strongest predictor of early attrition. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Pipeline starvation** | Few applicants, low response rates, exhausted networks, weak employer brand | Q1 shows top-of-funnel failure + Q2 shows passive or depleted sourcing | +| **Screening failure** | Many applicants rejected, criteria copied or undefined, culture misses | Q1 shows screening bottleneck + Q3 shows imported or unstable criteria | +| **Interview theatre** | Unstructured process, interviewer disagreement, founder override, poor prediction | Q1 shows interview-stage breakdown + Q4 shows process dysfunction | +| **Closing gap** | Offers declined, candidates cite comp/culture/uncertainty, losing to competitors | Q1 shows offer-stage failure + Q5 shows specific decline reasons | +| **Onboarding abandonment** | 90-day attrition high, new hires lost or disengaged, no ramp plan | Q1 shows post-hire failure + Q6 shows no structured onboarding | +| **Role-reality mismatch** | Early attrition, "this isn't what I signed up for," job differs from description | Q1 shows post-hire failure + Q6 shows expectation gap + Q5 may preview it | + +## Routing + +**Pipeline starvation:** +1. Apply `hackman-enabling-conditions` — ensure the role itself is designed to attract (compelling purpose, autonomy, meaningful work) +2. Apply `understanding-people` — build candidate personas to target sourcing with the same rigour as customer acquisition +3. Output with `role-description-template` + +**Screening failure:** +1. Apply `belbin-team-roles` — define what the team actually needs in terms of behavioural contribution, not just technical skill +2. Apply `decision-traps-and-roles` — audit the screening criteria for anchoring, availability bias, and halo effects +3. Output with `hiring-scorecard` + +**Interview theatre:** +1. Apply `decision-traps-and-roles` — redesign the interview process to counteract cognitive biases +2. Apply `reading-people` — train interviewers to gather signal from structured observation, not gut feel +3. Output with `hiring-scorecard` + +**Closing gap:** +1. Apply `understanding-people` — understand what motivates the candidates you're losing and build offers around those drivers +2. Apply `hackman-enabling-conditions` — ensure the role offers the structural conditions (autonomy, feedback, significance) that strong candidates seek +3. Output with `role-description-template` + +**Onboarding abandonment:** +1. Apply `hackman-enabling-conditions` — design the first 90 days with the same structural intentionality as the role itself +2. Apply `employee-engagement-retention` — build early engagement mechanisms that prevent new-hire disillusionment +3. Output with `team-health-check` + +**Role-reality mismatch:** +1. Apply `belbin-team-roles` — clarify what the role actually requires versus what was advertised +2. Apply `hackman-enabling-conditions` — redesign the role so that the description, the interview, and the reality converge +3. Output with `role-description-template` and `hiring-scorecard` + +## Red Flags + +- **The company has had more than 50% turnover in a single department within six months.** This rate suggests systemic toxicity rather than hiring process failure. Investigate the manager and the environment before optimising the funnel — better hiring into a toxic environment just burns through talent faster. +- **The founder cannot describe the ideal candidate for their most critical open role in concrete, observable terms.** Vague descriptions ("a rockstar," "someone entrepreneurial," "culture fit") are not criteria — they are projections that invite bias. Until the role is defined with specificity, no hiring process can succeed. +- **New hires consistently report that the interview process misrepresented the role, the culture, or the company's financial health.** Systematic misrepresentation — even unintentional — is an integrity issue. It damages employer brand through word of mouth and creates legal exposure. Fix the honesty problem before the process problem. diff --git a/plugins/foreman/content/diagnostics/innovation-drought-diagnosis.md b/plugins/foreman/content/diagnostics/innovation-drought-diagnosis.md new file mode 100644 index 0000000..fea005c --- /dev/null +++ b/plugins/foreman/content/diagnostics/innovation-drought-diagnosis.md @@ -0,0 +1,111 @@ +--- +name: "innovation-drought-diagnosis" +description: "Diagnoses the root cause when an entrepreneur reports a creativity or innovation failure -- whether from a fear-driven culture, depleted inputs, process suffocation, execution gaps, or routine addiction. Separates idea generation problems from idea execution problems and routes to the appropriate creative, cultural, or structural intervention." +entry_symptoms: + - "We can't innovate anymore" + - "No new ideas" + - "Everything feels stale" + - "The team plays it safe" + - "We're stuck in a rut" +possible_diagnoses: + - creative-fear-culture + - input-starvation + - process-suffocation + - execution-gap + - routine-addiction + - wrong-people-in-the-room +routes_to_skills: + - creative-identity-and-purpose + - creative-perception-and-awareness + - creative-practice-and-habit + - creative-obstacles + - creative-shaping-and-craft + - creative-flow-and-inspiration + - creative-collaboration-and-context + - creative-completion-and-renewal + - doblin-ten-types + - appreciative-inquiry + - generating-solutions + - psychological-safety-practice + - growth-mindset + - blue-ocean-strategy + - team-culture-and-dynamics +routes_to_templates: + - retrospective-template + - action-plan + - new-initiative-brief + - offsite-planning-guide +author: "Fatih Guner" +--- + +# Innovation Drought Diagnosis + +Creativity does not vanish overnight. It suffocates -- slowly, under the accumulated weight of risk aversion, depleted curiosity, and processes that were designed for efficiency but became prisons. The founder who says "we can't innovate anymore" is rarely describing an absence of creative talent. They are describing an environment where creative talent has learned to stay quiet, where novel ideas face an immune response from the organisational body, and where the safest career move is to repeat what worked last quarter. + +## Entry Symptoms + +- **"We can't innovate anymore."** Output feels derivative; competitors launch bolder products; internal efforts produce incremental improvements at best. +- **"No new ideas."** Brainstorming sessions yield silence or recycled suggestions; the pipeline of new concepts has dried up. +- **"Everything feels stale."** The culture has calcified; routines dominate; the organisation is going through the motions. +- **"The team plays it safe."** Proposals are conservative; experiments are avoided; the organisation optimises for certainty over discovery. +- **"We're stuck in a rut."** New initiatives lose momentum; the organisation gravitates back to familiar territory. + +## Triage Questions + +1. **Generation vs. execution**: Is the problem that the team cannot generate new ideas, or that ideas exist but fail to reach implementation? +2. **Fear assessment**: What happens when someone proposes a bold idea that fails? Is failure treated as learning or as career liability? +3. **Capacity check**: Do people have time to think creatively, or is every hour consumed by operational demands? +4. **Input quality**: What are the team's sources of external inspiration? Is the information diet entirely internal? +5. **Process audit**: Is innovation killed by excessive process (stage-gate reviews, seven layers of approval) or by the absence of any process at all? +6. **Room composition**: Who participates in ideation? Is it always the same people? Are diverse perspectives systematically included or excluded? + +## Diagnosis Map + +| Diagnosis | Key Indicators | Core Problem | +|-----------|---------------|--------------| +| **Creative Fear Culture** | Bold proposals are rare; ideas are hedged with excessive caveats; past failures were punished visibly; "safe" is the unstated organisational value | The environment penalises creative risk; people have rational reasons to self-censor; the immune system rejects novelty | +| **Input Starvation** | The team consumes only internal information; no cross-industry learning; customer contact is infrequent; inspiration sources have narrowed | Creativity requires raw material -- diverse experiences, external stimuli, unfamiliar perspectives -- and the supply has been cut off | +| **Process Suffocation** | Ideas require extensive documentation before exploration; approval chains are long; experimentation budgets require executive sign-off; speed-to-test is measured in months | Governance designed for operational excellence has colonised the innovation function; the process optimises for risk reduction at the cost of creative destruction | +| **Execution Gap** | Ideas are plentiful in brainstorms but none survive to implementation; prototypes are started and abandoned; the organisation generates concepts but cannot convert them | The bottleneck is not ideation but the translation from idea to action -- missing are resources, sponsorship, clear ownership, or a viable path from experiment to product | +| **Routine Addiction** | The organisation resists any deviation from established patterns; "the way we do things" is invoked to shut down alternatives; comfort has replaced curiosity | Success has bred complacency; the organisation has optimised its current model to the point where any change feels threatening rather than exciting | +| **Wrong People in the Room** | Ideation sessions are dominated by the same senior voices; junior staff or cross-functional perspectives are absent; groupthink is evident; ideas cluster narrowly | The innovation problem is a diversity-of-thought problem; the current participants share too many assumptions, experiences, and blind spots | + +## Routing + +### Creative Fear Culture +- **Primary skills**: psychological-safety-practice, creative-obstacles, growth-mindset +- **Supporting skills**: team-culture-and-dynamics, creative-identity-and-purpose +- **Templates**: retrospective-template + +### Input Starvation +- **Primary skills**: creative-perception-and-awareness, creative-flow-and-inspiration +- **Supporting skills**: doblin-ten-types, blue-ocean-strategy +- **Templates**: offsite-planning-guide + +### Process Suffocation +- **Primary skills**: generating-solutions, appreciative-inquiry +- **Supporting skills**: creative-practice-and-habit, creative-collaboration-and-context +- **Templates**: new-initiative-brief, action-plan + +### Execution Gap +- **Primary skills**: creative-completion-and-renewal, creative-shaping-and-craft +- **Supporting skills**: generating-solutions, doblin-ten-types +- **Templates**: action-plan, new-initiative-brief + +### Routine Addiction +- **Primary skills**: creative-practice-and-habit, creative-perception-and-awareness, appreciative-inquiry +- **Supporting skills**: blue-ocean-strategy, growth-mindset +- **Templates**: offsite-planning-guide, retrospective-template + +### Wrong People in the Room +- **Primary skills**: creative-collaboration-and-context, team-culture-and-dynamics +- **Supporting skills**: psychological-safety-practice, appreciative-inquiry +- **Templates**: retrospective-template, offsite-planning-guide + +## Red Flags + +- **The founder demands innovation but punishes failure.** The single most common pathology. No creative framework will produce results until the safety problem is addressed. Route to psychological-safety-practice as an absolute prerequisite. +- **"No new ideas" from a team working 70-hour weeks.** Exhausted people do not innovate. They survive. The intervention is not a creativity workshop -- it is workload reduction. Creative thought requires cognitive margin that overwork eliminates. +- **The founder is the bottleneck they cannot see.** Some founders filter every idea through their own taste. The team learns that "innovation" means "guess what the founder wants." Address this pattern directly before prescribing creative frameworks. +- **Innovation theatre masquerading as innovation.** Hackathons, innovation labs, and brainstorm walls that produce nothing actionable. If the organisation performs creativity rituals without converting outputs, the problem is execution gap. Do not prescribe more ideation. +- **The company is actually innovating but does not recognise it.** Some founders compare themselves to category-defining disruptors and conclude they are stale. Examine whether the "drought" is a perception gap rather than a reality gap. diff --git a/plugins/foreman/content/diagnostics/leadership-crisis-diagnosis.md b/plugins/foreman/content/diagnostics/leadership-crisis-diagnosis.md new file mode 100644 index 0000000..1857a09 --- /dev/null +++ b/plugins/foreman/content/diagnostics/leadership-crisis-diagnosis.md @@ -0,0 +1,124 @@ +--- +name: "leadership-crisis-diagnosis" +description: "Identifies the root cause of a founder or leader's personal crisis by distinguishing between role transition failure, impostor syndrome, delegation deficit, executive isolation, burnout, and loss of purpose. Use when an entrepreneur expresses self-doubt, exhaustion, isolation, or a sense that they are no longer fit for their role." +entry_symptoms: + - "I feel like a fraud" + - "I'm burning out" + - "I can't keep up" + - "I'm isolated" + - "I don't know what I'm doing anymore" + - "I used to love this and now I dread it" +possible_diagnoses: + - role-transition-failure + - impostor-syndrome + - delegation-deficit + - executive-isolation + - burnout + - loss-of-purpose +routes_to_skills: + - senior-leadership-transition + - leader-resilience-and-wellbeing + - delegation-and-empowerment + - purpose-driven-leadership + - emotional-courage + - stoic-fortitude-and-resilience +routes_to_templates: + - founder-mental-health-check + - leadership-reflection + - decision-journal +author: "Fatih Guner" +--- + +# Leadership Crisis Diagnosis + +## Entry Symptoms + +The entrepreneur speaks in first person about themselves, not the business: "I feel like a fraud," "I'm burning out," "I can't keep up," or "I don't know what I'm doing anymore." The vulnerability in these statements is itself diagnostic — leaders in genuine crisis rarely articulate the problem cleanly, because the crisis distorts their capacity for self-assessment. + +## Triage Questions + +### Q1: Is this about capability or confidence? + +- **Capability — "I genuinely lack the skills this role now requires"** — the role may have outgrown the leader. Proceed to Q2. +- **Confidence — "I can do it but I feel like I'll be exposed as inadequate"** — likely diagnosis: **impostor-syndrome**. Confirm with Q3. +- **Both — "I don't know if I can't do it or just think I can't"** — this ambiguity itself suggests a transition problem. Proceed to Q2. + +### Q2: Has your role changed significantly in the past 6-12 months? + +- **Yes — the company grew, and my job became something I didn't sign up for** — likely diagnosis: **role-transition-failure**. The founder-to-CEO transition is the most common version, but it recurs at every scaling inflection. +- **Yes — we raised funding, and now I answer to a board** — likely diagnosis: **role-transition-failure** compounded by **executive-isolation**. +- **No — my role hasn't changed, but my ability to handle it has deteriorated** — proceed to Q4. The issue is resource depletion, not role mismatch. + +### Q3: When you succeed, do you attribute it to luck, timing, or other people — and when you fail, do you attribute it entirely to yourself? + +- **Yes, exactly that pattern** — likely diagnosis: **impostor-syndrome**. The attribution asymmetry is the signature. +- **No — I attribute success to myself but still feel inadequate** — this is not classical impostor syndrome. The issue may be perfectionism or an actual skills gap. Return to Q2. +- **I haven't had a recent success to attribute anything to** — proceed to Q4 and Q5. The crisis may be situational rather than psychological. + +### Q4: When did you last sleep well, exercise, or take a full day off? + +- **Weeks or months ago** — likely diagnosis: **burnout**. Physical depletion is compounding or causing the psychological symptoms. +- **I sleep fine but wake up dreading the day** — the exhaustion is motivational, not physical. Likely diagnosis: **loss-of-purpose**. Proceed to Q6. +- **I try to rest but can't stop thinking about work** — likely diagnosis: **burnout** with anxiety features. The nervous system is stuck in threat-response mode. + +### Q5: Who do you talk to honestly about how you're doing? + +- **Nobody — I can't show weakness to my team, investors, or family** — likely diagnosis: **executive-isolation**. The leader is carrying the full cognitive and emotional load alone. +- **I have a coach, therapist, or peer group** — isolation is not the primary issue. Return to Q1 and Q4 for capability or depletion causes. +- **I used to have people but pushed them away as things got harder** — likely diagnosis: **executive-isolation** compounded by **burnout**. Withdrawal is both symptom and accelerant. + +### Q6: Does the work still feel meaningful to you? + +- **No — I've lost connection to why I started this** — likely diagnosis: **loss-of-purpose**. The mission no longer sustains the sacrifice. +- **The mission matters but I feel like the wrong person to carry it** — likely diagnosis: **impostor-syndrome** or **role-transition-failure**. The purpose is intact but the leader's relationship to it is fractured. +- **I don't know anymore — I'm too exhausted to feel anything about it** — likely diagnosis: **burnout** so severe it has suppressed the capacity for meaning-making. Address burnout first; purpose clarity will follow recovery. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Role transition failure** | Role outgrew the leader, new demands feel alien, "I didn't sign up for this" | Q2 confirms role change + Q1 shows capability doubt | +| **Impostor syndrome** | Success attributed to luck, failure internalised, persistent fear of exposure | Q3 confirms attribution asymmetry + Q1 shows confidence deficit | +| **Delegation deficit** | Leader does everything, bottleneck on all decisions, no trusted lieutenants | Q2 shows role unchanged but overwhelming + Q5 shows isolation | +| **Executive isolation** | No confidants, emotional suppression, withdrawal from relationships | Q5 confirms no support network + Q2 shows new accountability | +| **Burnout** | Sleep disruption, physical depletion, inability to disengage, dread | Q4 confirms physical symptoms + Q6 shows emotional flatness | +| **Loss of purpose** | Mission disconnection, existential questioning, "why am I doing this" | Q6 confirms meaning deficit + Q4 shows motivational exhaustion | + +## Routing + +**Role transition failure:** +1. Apply `senior-leadership-transition` — map the gap between the old role and the new one +2. Apply `leader-self-reflection` — build self-awareness about identity shifts +3. Output with `leadership-reflection` + +**Impostor syndrome:** +1. Apply `emotional-courage` — build the capacity to act despite fear of exposure +2. Apply `stoic-fortitude-and-resilience` — reframe the narrative around competence and growth +3. Output with `founder-mental-health-check` and `leadership-reflection` + +**Delegation deficit:** +1. Apply `delegation-and-empowerment` — build the system and mindset for letting go +2. Apply `senior-leadership-transition` — redefine what the leader's job actually is now +3. Output with `weekly-ceo-review` + +**Executive isolation:** +1. Apply `leader-resilience-and-wellbeing` — establish recovery and support structures +2. Apply `purpose-driven-leadership` — reconnect with the reason for leading +3. Output with `founder-mental-health-check` and `personal-board-tracker` + +**Burnout:** +1. Apply `leader-resilience-and-wellbeing` — immediate stabilisation and recovery planning +2. Apply `delegation-and-empowerment` — reduce the load structurally, not just temporarily +3. Output with `founder-mental-health-check` + +**Loss of purpose:** +1. Apply `purpose-driven-leadership` — reconstruct the connection between personal values and the venture +2. Apply `leader-self-reflection` — examine what changed and what still holds +3. Output with `leadership-reflection` and `decision-journal` + +## Red Flags + +- **The entrepreneur expresses suicidal ideation, self-harm, or a desire to disappear.** This is a mental health emergency. No framework, skill, or diagnostic replaces professional crisis intervention. Provide emergency resources immediately: National Suicide Prevention Lifeline (988 in the US), Crisis Text Line (text HOME to 741741), or local equivalent. +- **The leader describes substance dependence as a coping mechanism.** Addiction requires clinical treatment, not leadership coaching. Route to professional support. +- **The entrepreneur is making major irreversible decisions while in acute crisis.** Recommend a 30-day moratorium on irreversible decisions and immediate support from a therapist or executive coach. +- **Physical symptoms are present: chest pain, panic attacks, cognitive impairment, sustained insomnia.** These require medical evaluation. diff --git a/plugins/foreman/content/diagnostics/market-entry-diagnosis.md b/plugins/foreman/content/diagnostics/market-entry-diagnosis.md new file mode 100644 index 0000000..1dafd3d --- /dev/null +++ b/plugins/foreman/content/diagnostics/market-entry-diagnosis.md @@ -0,0 +1,119 @@ +--- +name: "market-entry-diagnosis" +description: "Evaluates readiness and strategy for entering a new market by distinguishing between premature expansion, market misreads, capability gaps, wrong entry modes, resource underestimation, and timing errors. Use when an entrepreneur is considering geographic expansion, new customer segments, or adjacent market opportunities." +entry_symptoms: + - "Want to enter a new market" + - "International expansion" + - "New customer segment" + - "Adjacent market opportunity" + - "Don't know where to start" +possible_diagnoses: + - premature-expansion + - market-misread + - capability-gap + - wrong-entry-mode + - resource-underestimation + - timing-error +routes_to_skills: + - porters-five-forces + - blue-ocean-strategy + - swot-pest-analysis + - scenario-planning + - first-mover-strategy + - business-model-canvas +routes_to_templates: + - strategic-analysis-one-pager + - market-opportunity-summary + - competitive-landscape-brief +author: "Fatih Guner" +--- + +# Market Entry Diagnosis + +## Entry Symptoms + +A new market gleams on the horizon. The entrepreneur arrives with some variation of: "We want to expand internationally," "There's an adjacent segment we should go after," "We got inbound interest from a new market," or "We've maxed out our current market — where next?" The appetite for expansion is healthy; the danger lies in confusing appetite with readiness. + +## Triage Questions + +### Q1: What type of market entry is this? + +- **Geographic expansion (same product, new country or region)** — the core challenge is localisation, regulation, and distribution. Proceed to Q3. +- **Segment expansion (same geography, new customer type)** — the core challenge is value proposition adaptation and channel discovery. Proceed to Q2. +- **Product expansion (new product into an adjacent market)** — the core challenge is capability and competitive positioning. Proceed to Q4. + +### Q2: What is driving the entry — pull or push? + +- **Pull (customers in the new market are asking for it)** — this is the stronger signal. Proceed to Q3 to validate depth of demand. +- **Push (current market feels saturated or threatened)** — expansion as escape carries higher risk. Likely diagnosis: **premature-expansion** if the core is not truly saturated. Confirm with Q5. +- **Opportunistic (a partnership or event opened a door)** — proceed with caution. Opportunity is not strategy. Proceed to Q4 to assess capability fit. + +### Q3: How different is the new market from your current one? + +- **Very similar (same language, similar regulations, adjacent culture)** — entry friction is low. Focus on competitive dynamics. Proceed to Q6. +- **Moderately different (different regulations, some cultural distance, new competitors)** — proceed to Q4 to identify capability gaps. +- **Fundamentally different (new language, unfamiliar regulations, no existing brand awareness)** — high entry cost. Likely diagnosis: **resource-underestimation** or **wrong-entry-mode**. Proceed to Q4 and Q5. + +### Q4: Do you have the capabilities to serve the new market? + +- **Yes — the product works as-is, and we have relevant operational capacity** — proceed to Q6 for competitive and timing assessment. +- **Partially — the product needs modification, or we lack local expertise** — likely diagnosis: **capability-gap**. Quantify what must be built, hired, or acquired. +- **No — serving this market requires fundamentally new capabilities** — likely diagnosis: **capability-gap** compounded by **resource-underestimation**. Consider whether partnership is the right entry mode (Q5). + +### Q5: Can you test the market before committing fully? + +- **Yes — a pilot, a partnership, or a limited launch is feasible** — this reduces risk substantially. Validate demand with minimal capital exposure before scaling commitment. +- **No — the market requires significant upfront investment (regulatory approval, physical infrastructure, local team)** — likely diagnosis: **resource-underestimation** if the entrepreneur has not modelled the full cost. Proceed to Q6. +- **We already committed significant resources** — the question is no longer whether to enter but how to succeed. Shift from entry diagnosis to execution diagnosis. + +### Q6: What does the competitive landscape look like in the target market? + +- **Fragmented — no dominant player, many small competitors** — favourable entry conditions. Apply competitive analysis to identify positioning. +- **Consolidated — one or two dominant incumbents** — entry will require a differentiated value proposition or a niche strategy. Likely diagnosis: **market-misread** if the entrepreneur expects to compete head-on without differentiation. +- **A well-funded competitor just entered the same market** — likely diagnosis: **timing-error**. The window may be closing, or the cost of entry just increased materially. +- **No competitors (virgin market)** — either the opportunity is genuinely untapped or the market does not exist. Likely diagnosis: **market-misread** if demand is assumed rather than validated. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Premature expansion** | Core market not fully captured, push-driven entry, core operations still unstable | Q2 shows push motivation + Q5 reveals core market has room | +| **Market misread** | Assumed demand not validated, no competitor presence (possible absent market), surface-level research | Q6 shows empty or impenetrable market + Q2 shows no pull signal | +| **Capability gap** | Product needs modification, local expertise missing, operational capacity insufficient | Q4 confirms partial or absent capability + Q3 shows market distance | +| **Wrong entry mode** | Should partner but planning to build, or building when acquisition is cheaper | Q4 shows gaps + Q5 shows testing is possible but entrepreneur chose full commitment | +| **Resource underestimation** | Entry costs modelled optimistically, timeline aggressive, hidden costs not accounted for | Q3 shows high market distance + Q5 shows significant upfront investment required | +| **Timing error** | Competitor just entered, regulatory window closing, market not yet ready | Q6 shows recent competitive entry or absent demand + Q2 shows opportunistic trigger | + +## Routing + +**Premature expansion:** +1. Apply `business-model-canvas` — stress-test whether the core business model is robust enough to fund and survive a second front +2. Apply `swot-pest-analysis` — honestly assess internal weaknesses that expansion would amplify +3. Output with `strategic-analysis-one-pager` +**Market misread:** +1. Apply `porters-five-forces` — rigorously analyse the target market's structure, not the entrepreneur's assumptions about it +2. Apply `scenario-planning` — model multiple demand scenarios to pressure-test the opportunity thesis +3. Output with `market-opportunity-summary` +**Capability gap:** +1. Apply `swot-pest-analysis` — catalogue what the organisation has versus what the new market demands +2. Apply `business-model-canvas` — redesign the value proposition for the new market's requirements +3. Output with `competitive-landscape-brief` +**Wrong entry mode:** +1. Apply `first-mover-strategy` — determine whether speed (partnering) or control (building) matters more +2. Apply `porters-five-forces` — assess bargaining power dynamics with potential partners +3. Output with `strategic-analysis-one-pager` +**Resource underestimation:** +1. Apply `scenario-planning` — model best-case, base-case, and worst-case resource requirements +2. Apply `business-model-canvas` — map all cost structures and revenue assumptions for the new market +3. Output with `market-opportunity-summary` +**Timing error:** +1. Apply `first-mover-strategy` — evaluate whether first-mover advantage exists or whether fast-follower is preferable +2. Apply `blue-ocean-strategy` — identify whether the market can be entered from an uncontested angle +3. Output with `competitive-landscape-brief` + +## Red Flags + +- **The entrepreneur cannot articulate why the new market will buy.** "It's a big market" is not a thesis. Without a validated demand signal, expansion is speculation funded with operational capital. +- **Core unit economics are negative, and expansion is positioned as the fix.** Scaling a broken model into a new market multiplies losses. Fix unit economics at home first. +- **The expansion plan has no exit criteria.** Every market entry should define what failure looks like and when to pull back. Without these, sunk cost bias extends losing commitments indefinitely. +- **The entire case rests on a single partnership or customer request.** One data point is an anecdote. Market entry requires pattern recognition across multiple signals. diff --git a/plugins/foreman/content/diagnostics/negotiation-stuck-diagnosis.md b/plugins/foreman/content/diagnostics/negotiation-stuck-diagnosis.md new file mode 100644 index 0000000..b18882d --- /dev/null +++ b/plugins/foreman/content/diagnostics/negotiation-stuck-diagnosis.md @@ -0,0 +1,113 @@ +--- +name: "negotiation-stuck-diagnosis" +description: "Diagnoses the root cause when an entrepreneur reports a stalled negotiation -- whether from positional deadlock, BATNA weakness, hidden interests, power imbalance, or bad faith on the other side. Determines whether the block is tactical, structural, or relational and routes to the precise negotiation or conflict resolution intervention." +entry_symptoms: + - "The deal is stuck" + - "We can't agree on terms" + - "The other side won't budge" + - "Negotiation keeps going in circles" + - "I think I'm getting a bad deal" +possible_diagnoses: + - positional-deadlock + - batna-weakness + - power-imbalance + - hidden-interests + - relationship-damage + - bad-faith-counterpart + - internal-misalignment +routes_to_skills: + - negotiation-mindset-and-self + - competitive-negotiation + - cooperative-negotiation + - delivering-the-deal + - negotiation-game-theory + - win-win-negotiation + - thomas-kilmann-conflict + - resolving-people-conflict + - reading-people + - information-asymmetry +routes_to_templates: + - negotiation-prep-sheet + - decision-journal + - stakeholder-map +author: "Fatih Guner" +--- + +# Negotiation Stuck Diagnosis + +A stalled negotiation feels like a wall. Both sides sit across the table, repeat their positions with increasing frustration, and mistake stubbornness for strategy. The founder concludes that the other party is unreasonable. The other party reaches the identical conclusion. Meanwhile, the deal that could benefit both sides rots in the space between them -- not because agreement is impossible, but because neither side has diagnosed why they are actually stuck. + +## Entry Symptoms + +- **"The deal is stuck."** Neither party has made a concession in weeks; conversations are repetitive or have ceased entirely. +- **"We can't agree on terms."** Specific deal points remain unresolved despite multiple rounds of discussion. +- **"The other side won't budge."** The counterparty appears rigid; every proposal is rejected; no visible movement. +- **"Negotiation keeps going in circles."** The same arguments recur each meeting; apparent progress unravels by the next session. +- **"I think I'm getting a bad deal."** The founder suspects the terms are unfavourable but cannot assess whether this is true or merely feels true. + +## Triage Questions + +1. **Nature of negotiation**: Is this fundamentally competitive (one party's gain is the other's loss) or is there potential for cooperative value creation? +2. **Interests vs. positions**: Can you articulate the other side's underlying interests, or do you only know their stated positions? +3. **Power assessment**: Is the power balance roughly equal, or does one side hold significantly more leverage? +4. **BATNA clarity**: Have you defined your Best Alternative to Negotiated Agreement? Can you quantify what happens if this deal falls through? +5. **Relationship stakes**: Is preserving the relationship important beyond this deal, or is this a one-time transaction? +6. **Third-party dynamics**: Is a third party influencing or blocking progress? Are there decision-makers absent from the room? +7. **Good faith assessment**: Do you believe the other side genuinely wants to reach agreement, or are there signs of stalling? + +## Diagnosis Map + +| Diagnosis | Key Indicators | Core Problem | +|-----------|---------------|--------------| +| **Positional Deadlock** | Both sides repeat fixed demands; concessions are seen as weakness; negotiation has become a contest of wills | Parties are arguing positions rather than exploring interests; the negotiation framework is purely distributive when it need not be | +| **BATNA Weakness** | The founder feels pressured to accept unfavourable terms; walking away feels impossible; the other side senses desperation | The founder lacks a credible alternative, and this weakness -- whether real or merely perceived -- undermines negotiating power | +| **Power Imbalance** | One side controls the timeline, the information, or the market access; terms are dictated rather than negotiated | Structural asymmetry means standard negotiation tactics are insufficient; the weaker party must change the game rather than play it better | +| **Hidden Interests** | Proposals are rejected without clear explanation; the counterparty's objections seem irrational or disproportionate; stated reasons do not match behaviour | Unstated needs, fears, or constraints are driving the other side's resistance; surface-level negotiation cannot resolve subsurface problems | +| **Relationship Damage** | Personal tension has entered the negotiation; past grievances are referenced; trust has broken down; emotional reactions override rational analysis | The negotiation has shifted from substance to sentiment; relational repair must precede deal-making | +| **Bad Faith Counterpart** | Repeated broken commitments; ever-moving goalposts; information withheld or misrepresented; the process itself is being exploited | The other side is not negotiating to agree but to extract information, stall, or gain leverage for use elsewhere | +| **Internal Misalignment** | The founder's own team disagrees on acceptable terms; different stakeholders send conflicting signals to the counterparty; the mandate is unclear | The negotiation is stuck not because of the counterparty but because the founder's side has not achieved internal consensus on goals and limits | + +## Routing + +### Positional Deadlock +- **Primary skills**: cooperative-negotiation, win-win-negotiation +- **Supporting skills**: negotiation-game-theory, reading-people +- **Templates**: negotiation-prep-sheet + +### BATNA Weakness +- **Primary skills**: competitive-negotiation, negotiation-mindset-and-self +- **Supporting skills**: negotiation-game-theory, information-asymmetry +- **Templates**: negotiation-prep-sheet, decision-journal + +### Power Imbalance +- **Primary skills**: negotiation-game-theory, competitive-negotiation, information-asymmetry +- **Supporting skills**: negotiation-mindset-and-self +- **Templates**: negotiation-prep-sheet, stakeholder-map + +### Hidden Interests +- **Primary skills**: cooperative-negotiation, reading-people +- **Supporting skills**: win-win-negotiation, resolving-people-conflict +- **Templates**: negotiation-prep-sheet + +### Relationship Damage +- **Primary skills**: thomas-kilmann-conflict, resolving-people-conflict +- **Supporting skills**: cooperative-negotiation, negotiation-mindset-and-self +- **Templates**: negotiation-prep-sheet + +### Bad Faith Counterpart +- **Primary skills**: competitive-negotiation, negotiation-mindset-and-self +- **Supporting skills**: information-asymmetry, negotiation-game-theory +- **Templates**: decision-journal + +### Internal Misalignment +- **Primary skills**: negotiation-mindset-and-self, delivering-the-deal +- **Supporting skills**: thomas-kilmann-conflict +- **Templates**: negotiation-prep-sheet, stakeholder-map + +## Red Flags + +- **The founder has no BATNA and does not realise it.** A negotiator without alternatives is not negotiating; they are accepting terms. Establish whether a walkaway option exists before any tactical advice. If none exists, creating one is the first intervention. +- **"The other side won't budge" but the founder has not asked about their interests.** Perceived rigidity is often unexplored interests. Route to cooperative-negotiation before escalating competitive tactics. +- **Emotional investment exceeds economic rationality.** When the founder frames the negotiation in personal terms ("they disrespected us"), the deal has become an identity contest. Route to negotiation-mindset-and-self. +- **A third party is blocking progress from the shadows.** Silent stakeholders -- an investor's spouse, a board member who was not consulted -- can veto deals invisibly. Surface these actors before optimising tactics. +- **The founder is negotiating against themselves.** Some founders concede preemptively, offering terms the counterparty never requested. Route to negotiation-mindset-and-self. diff --git a/plugins/foreman/content/diagnostics/operational-chaos-diagnosis.md b/plugins/foreman/content/diagnostics/operational-chaos-diagnosis.md new file mode 100644 index 0000000..086ce37 --- /dev/null +++ b/plugins/foreman/content/diagnostics/operational-chaos-diagnosis.md @@ -0,0 +1,119 @@ +--- +name: "operational-chaos-diagnosis" +description: "Determines why an organisation cannot execute reliably by distinguishing between documentation deficits, founder bottlenecks, process voids, process theater, tool sprawl, and accountability vacuums. Use when an entrepreneur reports constant fire drills, inability to scale, repeated mistakes, or dangerous key-person dependencies." +entry_symptoms: + - "Everything is a fire drill" + - "No processes" + - "We can't scale" + - "Same mistakes over and over" + - "Tribal knowledge everywhere" + - "Key person dependency" +possible_diagnoses: + - documentation-deficit + - founder-bottleneck + - process-void + - process-theater + - tool-sprawl + - accountability-vacuum +routes_to_skills: + - kaizen-bpr + - systems-thinking + - delegation-and-empowerment + - balanced-scorecard + - smart-goals + - hackman-enabling-conditions +routes_to_templates: + - action-plan + - project-kickoff-document +author: "Fatih Guner" +--- + +# Operational Chaos Diagnosis + +## Entry Symptoms + +The organisation runs on adrenaline, not systems. The entrepreneur describes the situation in visceral terms: "Everything is a fire drill," "The same mistakes keep happening," "If Sarah leaves, we're dead," or "We just can't scale past this point." There is a pervasive sense that the company operates despite itself — held together by heroic individual effort rather than reliable infrastructure. + +## Triage Questions + +### Q1: Is this growing pains or structural dysfunction? + +- **The company recently scaled from ~10 to ~50 people** — chaos often accompanies this transition. Proceed to Q2 to identify which specific structures are missing. +- **The company has been this size for over a year and chaos persists** — this is structural, not transitional. Proceed to Q3. +- **The company is small (under 15 people) but already dysfunctional** — likely diagnosis: **founder-bottleneck** or **accountability-vacuum**. Proceed to Q4. + +### Q2: Which functions are most chaotic? + +- **Engineering or product (deployments break, specs unclear, technical debt overwhelming)** — likely diagnosis: **process-void** or **documentation-deficit**. Proceed to Q3. +- **Sales or customer success (deals fall through cracks, handoffs fail, no playbook)** — likely diagnosis: **documentation-deficit**. The knowledge lives in individuals, not systems. +- **Finance or operations (invoices missed, compliance gaps, manual workarounds everywhere)** — likely diagnosis: **tool-sprawl** or **process-void**. Proceed to Q5. +- **All functions equally chaotic** — likely diagnosis: **founder-bottleneck** or **accountability-vacuum**. The dysfunction is organisational, not departmental. Proceed to Q4. + +### Q3: Are there documented processes that people ignore, or no documentation at all? + +- **No documentation exists — everything is tribal knowledge** — likely diagnosis: **documentation-deficit**. The company grew faster than its institutional memory. +- **Documentation exists but nobody follows it** — likely diagnosis: **process-theater**. Systems were created for appearance (investors, audits) but never adopted. +- **Some processes are documented and followed, others are not** — the company is partially mature. Identify which undocumented areas cause the most damage and address those first. + +### Q4: Is the founder or CEO the bottleneck? + +- **Yes — most decisions route through one person** — likely diagnosis: **founder-bottleneck**. Quantify it: how many decisions per week require the founder's explicit approval? +- **The founder delegates, but people escalate back anyway** — likely diagnosis: **accountability-vacuum**. Delegation happened nominally but authority and ownership were never truly transferred. +- **The founder is not the bottleneck — multiple people are** — likely diagnosis: **process-void**. No one knows who owns what because ownership was never defined. + +### Q5: How many tools does the company use, and do they integrate? + +- **Dozens of tools, many overlapping, no single source of truth** — likely diagnosis: **tool-sprawl**. Information lives in too many places, and reconciliation consumes more time than the tools save. +- **Few tools, used inconsistently** — likely diagnosis: **process-void**. The tools are not the problem; the absence of agreed workflows is. +- **Tools are adequate and integrated, yet chaos persists** — the problem is human, not technical. Return to Q4 for accountability and ownership diagnosis. + +### Q6: How many decisions require the CEO's involvement in a typical week? + +- **More than 20 operational decisions per week** — likely diagnosis: **founder-bottleneck**. The CEO is a single point of failure, and every thread leads back to one brain. +- **Fewer than 10, but people still feel directionless** — likely diagnosis: **accountability-vacuum**. Decisions get made but nobody owns execution. +- **The CEO is not involved, yet nothing moves** — likely diagnosis: **accountability-vacuum** compounded by **process-void**. There is neither a decision-maker nor a system. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Documentation deficit** | Tribal knowledge, new hires flounder, departure of one person cripples a function | Q3 confirms no documentation + Q2 shows departmental concentration | +| **Founder bottleneck** | All decisions route through one person, progress halts when founder is unavailable | Q4 confirms single-person dependency + Q6 shows 20+ decisions/week | +| **Process void** | No repeatable workflows, every project starts from scratch, ad hoc everything | Q3 confirms absence + Q5 shows tools are not the constraint | +| **Process theater** | Documentation exists but is ignored, processes exist on paper only, compliance-driven not operations-driven | Q3 confirms documented-but-unfollowed + Q2 shows persistent chaos despite "systems" | +| **Tool sprawl** | Dozens of overlapping tools, no integration, time spent reconciling data across platforms | Q5 confirms tool proliferation + Q3 shows information fragmentation | +| **Accountability vacuum** | Everyone is responsible for everything (meaning nobody is), decisions made but not executed | Q4 shows delegation without ownership + Q6 shows low CEO involvement yet stagnation | + +## Routing + +**Documentation deficit:** +1. Apply `kaizen-bpr` — implement continuous process improvement starting with the highest-impact undocumented workflows +2. Apply `systems-thinking` — map the knowledge flows and identify where institutional memory fails +3. Output with `project-kickoff-document` — use as a template for documenting repeatable processes +**Founder bottleneck:** +1. Apply `delegation-and-empowerment` — build a systematic delegation framework with clear decision rights +2. Apply `hackman-enabling-conditions` — ensure teams have the structure, support, and authority to operate independently +3. Output with `action-plan` — create a 90-day delegation roadmap +**Process void:** +1. Apply `kaizen-bpr` — design and implement core operational processes from scratch +2. Apply `smart-goals` — define measurable outcomes for each new process +3. Output with `project-kickoff-document` — formalise the process-building initiative itself +**Process theater:** +1. Apply `systems-thinking` — diagnose why existing processes are ignored (misaligned incentives, poor design, lack of enforcement) +2. Apply `balanced-scorecard` — connect process adherence to measurable business outcomes so compliance has teeth +3. Output with `action-plan` — redesign processes with the people who must follow them +**Tool sprawl:** +1. Apply `systems-thinking` — map information flows and identify redundancies, gaps, and reconciliation waste +2. Apply `kaizen-bpr` — consolidate tool stack around core workflows +3. Output with `action-plan` — create a tool rationalisation plan with migration timeline +**Accountability vacuum:** +1. Apply `hackman-enabling-conditions` — establish clear team boundaries, authority, and success criteria +2. Apply `delegation-and-empowerment` — assign explicit ownership with decision rights, not just task lists +3. Output with `action-plan` — document the new accountability structure and communicate it organisation-wide + +## Red Flags + +- **Voluntary turnover exceeds 30% in the past 12 months.** Operational chaos drives out competent people first. Address retention before process — building systems that nobody stays to use is futile. +- **The founder describes chaos as a cultural virtue.** "We move fast and break things" is a defence mechanism, not a strategy. Chaos at scale is waste disguised as velocity. +- **A single engineer built the entire technical stack.** This is existential risk, not merely operational. Document and cross-train immediately, independent of any other diagnostic outcome. +- **Revenue is growing despite the chaos.** Growth masks dysfunction until it does not. The question is whether the company will fix the engine before the road gets steeper. diff --git a/plugins/foreman/content/diagnostics/partnership-diagnosis.md b/plugins/foreman/content/diagnostics/partnership-diagnosis.md new file mode 100644 index 0000000..f2cb4cd --- /dev/null +++ b/plugins/foreman/content/diagnostics/partnership-diagnosis.md @@ -0,0 +1,117 @@ +--- +name: "partnership-diagnosis" +description: "Evaluates whether a partnership, strategic alliance, or joint venture will create or destroy value by distinguishing between capability illusions, incentive misalignment, power asymmetry, scope creep, exit traps, and better-to-build scenarios. Use when an entrepreneur is considering, negotiating, or struggling with a business partnership." +entry_symptoms: + - "Got a partnership offer" + - "Current partnership isn't working" + - "Should we do M&A or partner?" + - "Strategic alliance opportunity" + - "Joint venture proposal" +possible_diagnoses: + - capability-illusion + - incentive-misalignment + - power-asymmetry + - scope-creep + - exit-trap + - better-to-build +routes_to_skills: + - coalition-and-partnership-games + - cooperative-negotiation + - win-win-negotiation + - negotiation-game-theory + - trust-equation + - porters-five-forces +routes_to_templates: + - partnership-memo + - negotiation-prep-sheet +author: "Fatih Guner" +--- + +# Partnership Diagnosis + +## Entry Symptoms + +Partnerships arrive wrapped in optimism. The entrepreneur describes: "We got an offer to partner with a major player," "Our current partnership isn't delivering," "Should we acquire them or just partner?," or "There's a joint venture opportunity on the table." The allure of combining forces is powerful — two companies, complementary strengths, shared upside. The reality is that most partnerships fail, and the failure modes are identifiable in advance. + +## Triage Questions + +### Q1: What type of partnership is this? + +- **Strategic partnership (capability access — technology, expertise, IP)** — the core question is whether the partner actually delivers the capability you need. Proceed to Q2. +- **Distribution partnership (market access — channels, customers, geography)** — the core question is whether incentives stay aligned as volumes grow. Proceed to Q3. +- **Financial partnership (capital — investment, revenue share, co-funding)** — the core question is governance and control. Proceed to Q4. + +### Q2: What does each side bring that the other cannot build alone? + +- **Both sides contribute something genuinely irreplaceable** — strong foundation. Proceed to Q3 to test incentive alignment. +- **One side's contribution could be built internally within 12-18 months** — likely diagnosis: **better-to-build**. The partnership buys speed, but at what cost in dependency? +- **One side's contribution is vague or aspirational ("access to their network," "brand association")** — likely diagnosis: **capability-illusion**. The promised value may never materialise. + +### Q3: Are the incentives aligned, and will they remain so over time? + +- **Yes — both parties benefit proportionally from the same outcomes** — proceed to Q4 to assess power dynamics. +- **Aligned now, but they diverge as the partnership scales** — likely diagnosis: **incentive-misalignment**. Model the scenarios: what happens when one side outgrows the other, or when market conditions shift? +- **Each side has a different definition of success** — likely diagnosis: **incentive-misalignment**. If success metrics do not overlap, the partnership will pull in two directions. + +### Q4: Is there a power imbalance? + +- **Roughly equal — similar size, similar dependency, similar alternatives** — proceed to Q5. +- **One side is significantly larger, better funded, or less dependent** — likely diagnosis: **power-asymmetry**. The smaller party will find that "partnership" gradually becomes "supplier relationship." Proceed to Q5. +- **One side has no alternatives; the other has many** — likely diagnosis: **power-asymmetry** compounded by **exit-trap**. The dependent party's negotiating position will erode over time. + +### Q5: What happens if the partnership fails — can you walk away cleanly? + +- **Yes — assets remain separate, customers are not shared, IP is clearly owned** — the exit cost is low, which paradoxically makes the partnership healthier. +- **Partially — some shared customers or co-developed IP would need to be divided** — likely diagnosis: **exit-trap** if no pre-negotiated separation terms exist. Define them now. +- **No — core product depends on partner's technology, or customers were acquired through partner's channels** — likely diagnosis: **exit-trap**. The partnership has created a dependency that makes departure destructive. + +### Q6: Has the partnership's scope been clearly defined with success metrics? + +- **Yes — written agreement with KPIs, milestones, and review cadence** — proceed to confirm that metrics are being tracked and meetings are happening. +- **Broadly defined — "we'll work together on X" without specifics** — likely diagnosis: **scope-creep**. Without boundaries, the partnership will expand into areas neither side intended, generating friction. +- **No metrics, no milestones, no review process** — likely diagnosis: **scope-creep** compounded by **accountability vacuum**. The partnership is a handshake with no mechanism for course correction. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Capability illusion** | Partner's contribution is vague, promised value not yet demonstrated, references are thin | Q2 shows aspirational value + Q1 reveals strategic rationale is weak | +| **Incentive misalignment** | Different definitions of success, revenue-share disputes, diverging strategies | Q3 shows incentives diverge at scale + Q6 shows no shared metrics | +| **Power asymmetry** | One side is 10x larger, one side has alternatives the other lacks, terms favour the stronger party | Q4 confirms size or dependency imbalance + Q5 shows unequal exit costs | +| **Scope creep** | Partnership expanded beyond original intent, new obligations emerged, original metrics abandoned | Q6 shows vague scope + Q3 shows incentives shifting as scope broadened | +| **Exit trap** | Core dependencies on partner, shared customers or IP, no separation agreement | Q5 confirms entanglement + Q4 shows power imbalance makes renegotiation difficult | +| **Better to build** | Partner's contribution is replicable, 12-18 month internal build is feasible, partnership cost exceeds build cost | Q2 shows buildable capability + Q4 shows dependency risk exceeds speed benefit | + +## Routing + +**Capability illusion:** +1. Apply `trust-equation` — assess credibility, reliability, intimacy, and self-orientation of the partner before committing +2. Apply `porters-five-forces` — evaluate whether the partner's "capability" is actually available from multiple sources +3. Output with `partnership-memo` — document the due diligence findings +**Incentive misalignment:** +1. Apply `negotiation-game-theory` — model the payoff structure for both parties across multiple scenarios +2. Apply `cooperative-negotiation` — redesign the agreement to align incentives at scale, not just at launch +3. Output with `negotiation-prep-sheet` +**Power asymmetry:** +1. Apply `coalition-and-partnership-games` — understand the value each party contributes and how to maintain leverage +2. Apply `win-win-negotiation` — negotiate terms that protect the smaller party's position as the partnership evolves +3. Output with `negotiation-prep-sheet` +**Scope creep:** +1. Apply `cooperative-negotiation` — renegotiate boundaries with clear deliverables and exclusions +2. Apply `negotiation-game-theory` — model the cost of continued scope expansion versus the benefit of refocusing +3. Output with `partnership-memo` — redraft the partnership scope with explicit boundaries +**Exit trap:** +1. Apply `negotiation-game-theory` — map the cost of exit versus the cost of continued dependency +2. Apply `porters-five-forces` — identify alternative partners or internal capabilities that reduce dependency +3. Output with `negotiation-prep-sheet` — prepare for renegotiation or separation +**Better to build:** +1. Apply `porters-five-forces` — confirm that the capability can be developed internally without prohibitive barriers +2. Apply `coalition-and-partnership-games` — compare the total cost of partnership (financial, strategic, dependency) against the total cost of building +3. Output with `partnership-memo` — document the build-versus-partner analysis + +## Red Flags + +- **The partner insists on exclusivity without reciprocal commitments.** Exclusivity without symmetry is a power grab. The stronger party locks in optionality while restricting yours. +- **The partnership is driven by a single personal relationship.** When the executive champion departs, the foundation evaporates. Ensure the alliance is institutionally grounded. +- **Economics have not been discussed after three meetings.** Partnerships that avoid the money conversation are built on assumptions. The longer economics remain undefined, the more painful the reckoning. +- **The entrepreneur's primary motivation is the partner's brand name.** Brand halo is not a business model. Demand specific, quantifiable commitments. diff --git a/plugins/foreman/content/diagnostics/pricing-diagnosis.md b/plugins/foreman/content/diagnostics/pricing-diagnosis.md new file mode 100644 index 0000000..d5fff83 --- /dev/null +++ b/plugins/foreman/content/diagnostics/pricing-diagnosis.md @@ -0,0 +1,130 @@ +--- +name: "pricing-diagnosis" +description: "Performs deep-layer triage on pricing problems by distinguishing between cost-plus traps, competitor anchoring, value communication failures, wrong pricing models, missing segmentation, freemium leakage, and margin structure flaws. Use when a first-layer diagnostic surfaces pricing as the root issue, or when an entrepreneur reports inability to charge, convert free users, or maintain margins." +entry_symptoms: + - "Don't know what to charge" + - "Customers say we're too expensive" + - "Can't raise prices without losing customers" + - "Freemium isn't converting" + - "Competitors undercut us on price" + - "Margins are too thin to sustain the business" +possible_diagnoses: + - cost-plus-trap + - competitor-anchoring + - value-communication-failure + - wrong-pricing-model + - missing-segmentation + - freemium-leakage + - margin-structure-flaw +routes_to_skills: + - four-ps-marketing + - business-model-canvas + - porters-five-forces + - net-promoter-score + - information-asymmetry + - blue-ocean-strategy +routes_to_templates: + - unit-economics-snapshot + - strategic-analysis-one-pager +author: "Fatih Guner" +--- + +# Pricing Diagnosis + +## Entry Symptoms + +Few decisions generate more anxiety and less rigour than pricing. The entrepreneur arrives with some variation of: "We don't know what to charge," "Everyone says we're too expensive," "Our freemium funnel leaks," or "Margins are killing us." Each complaint sounds like a pricing problem. Most of them are not — they are value problems, segmentation problems, or business model problems wearing pricing's disguise. + +## Triage Questions + +### Q1: How was the current price originally set? + +- **Cost-plus (calculated costs, added a margin)** — likely diagnosis: **cost-plus-trap**. The price reflects internal accounting, not external value. Proceed to Q3 to confirm. +- **Competitor benchmarking (looked at what others charge, priced similarly or slightly below)** — likely diagnosis: **competitor-anchoring**. The business has outsourced its pricing logic to rivals. Proceed to Q4. +- **Value-based (researched willingness to pay, priced against perceived value)** — pricing methodology is sound; the problem likely sits elsewhere. Proceed to Q2 and Q5. +- **Gut feel or "we just picked a number"** — no pricing foundation exists. Start with Q2 and Q3 to build one. + +### Q2: What is the customer's actual willingness to pay, and how do you know? + +- **Tested through surveys, experiments, or pricing page A/B tests — data exists** — the price level may be calibrated; the issue is likely the model or packaging. Proceed to Q5. +- **Inferred from sales conversations ("they said it's too expensive")** — anecdotal signals are unreliable. Buyers negotiate; "too expensive" often means "convince me." Likely diagnosis: **value-communication-failure**. Proceed to Q3. +- **Unknown — never systematically tested** — pricing is untethered from demand. Any diagnosis is premature until willingness-to-pay data exists. Route to `four-ps-marketing` for price discovery before deeper triage. + +### Q3: When you describe your product to a prospective customer, do they understand the value before they see the price? + +- **Yes — they articulate the value themselves and the price still feels high** — the gap is quantitative, not conceptual. The customer grasps value but perceives it as smaller than the price. Likely diagnosis: **cost-plus-trap** or **margin-structure-flaw**. +- **No — they need extensive explanation to understand why it costs what it does** — likely diagnosis: **value-communication-failure**. The product may deliver genuine value that remains invisible until post-purchase. +- **They understand the value but compare immediately to cheaper alternatives** — likely diagnosis: **competitor-anchoring**. The product lacks differentiation sufficient to justify a premium. + +### Q4: Is the problem the price level or the pricing model? + +- **The price level — "it's just too much money"** — the complaint targets the number. But is it the number or the way it's charged? Confirm: would the same annual amount charged monthly feel different? If yes, likely diagnosis: **wrong-pricing-model**. +- **The pricing model — customers want a different structure (usage-based instead of flat, monthly instead of annual, per-seat instead of per-company)** — likely diagnosis: **wrong-pricing-model**. The value delivery pattern and the payment pattern are misaligned. +- **Both — the model feels wrong and the amount feels high** — likely diagnosis: **wrong-pricing-model** compounded by **value-communication-failure**. Address the model first; the level becomes testable once the structure is right. + +### Q5: Do different customer segments respond differently to your pricing? + +- **Yes — enterprises accept it, SMBs reject it (or vice versa)** — likely diagnosis: **missing-segmentation**. A single price cannot serve markets with fundamentally different value perceptions and budget constraints. +- **Free users love the product but refuse to convert to paid** — likely diagnosis: **freemium-leakage**. The free tier delivers too much value, eliminating the conversion incentive. +- **All segments push back equally** — the issue is not segmentation. Return to Q3 for value communication or Q1 for pricing foundation. + +### Q6: What do your unit economics look like at the current price? + +- **Gross margins are healthy (>60%) but customers still complain about price** — the business is viable; the problem is perception. Likely diagnosis: **value-communication-failure** or **competitor-anchoring**. +- **Gross margins are thin (<40%) and the business can't lower prices further** — likely diagnosis: **margin-structure-flaw**. The cost structure, not the price, is the constraint. Pricing cannot fix a fundamentally expensive delivery model. +- **Unit economics are negative — each customer costs more to serve than they pay** — likely diagnosis: **margin-structure-flaw** compounded by **cost-plus-trap**. The business model is structurally broken at the unit level. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Cost-plus trap** | Price set from costs; no demand-side input; value exceeds price perception | Q1 shows cost-plus origin + Q2 shows no WTP data | +| **Competitor anchoring** | Price mirrors competitors; no differentiation premium; race to bottom | Q1 shows competitor-based + Q3 shows immediate comparison | +| **Value communication failure** | Product delivers value but customers don't perceive it pre-purchase | Q3 shows explanation needed + Q2 shows anecdotal WTP | +| **Wrong pricing model** | Model-structure complaints; payment rhythm mismatches usage rhythm | Q4 shows model objections + Q5 shows segment-varied response | +| **Missing segmentation** | One price for diverse segments; some accept, others reject identically | Q5 shows segment divergence + Q4 shows level-not-model issue | +| **Freemium leakage** | Free tier overserves; conversion near zero; high free engagement | Q5 shows free-to-paid gap + product usage data shows free sufficiency | +| **Margin structure flaw** | Thin or negative unit economics; price floor above market tolerance | Q6 shows margin data + Q1 shows pricing already at cost-plus floor | + +## Routing + +**Cost-plus trap:** +1. Apply `four-ps-marketing` — rebuild pricing from value delivered, not cost incurred +2. Apply `business-model-canvas` — ensure the revenue model reflects customer value +3. Output with `unit-economics-snapshot` + +**Competitor anchoring:** +1. Apply `porters-five-forces` — understand the competitive dynamics creating the price anchor +2. Apply `blue-ocean-strategy` — explore differentiation paths that escape the comparison frame +3. Output with `strategic-analysis-one-pager` + +**Value communication failure:** +1. Apply `net-promoter-score` — identify what existing customers value most +2. Apply `information-asymmetry` — the buyer lacks data the seller possesses +3. Output with `strategic-analysis-one-pager` + +**Wrong pricing model:** +1. Apply `business-model-canvas` — redesign the revenue stream to match value consumption patterns +2. Apply `four-ps-marketing` — align pricing structure with buyer psychology +3. Output with `unit-economics-snapshot` + +**Missing segmentation:** +1. Apply `four-ps-marketing` — develop segment-specific pricing and positioning +2. Apply `business-model-canvas` — evaluate whether each segment warrants its own value proposition +3. Output with `unit-economics-snapshot` + +**Freemium leakage:** +1. Apply `business-model-canvas` — redraw the line between free value and paid value +2. Apply `information-asymmetry` — users never discover paid value when the free tier overserves +3. Output with `unit-economics-snapshot` + +**Margin structure flaw:** +1. Apply `porters-five-forces` — determine if the cost structure is industry-wide or company-specific +2. Apply `business-model-canvas` — explore structural changes to shift the cost base +3. Output with `unit-economics-snapshot` + +## Red Flags + +- **The entrepreneur is competing purely on price with no differentiation strategy.** Price competition without structural cost advantage is a death spiral. Before optimising pricing, determine whether the product has any defensible differentiation at all. +- **Revenue depends on a single pricing tier with no expansion path.** Without upsell, cross-sell, or usage-based growth, customer lifetime value is capped at acquisition. The pricing architecture — not the price point — is the constraint. +- **The company has never tested a price change.** Pricing anxiety that prevents experimentation is more dangerous than wrong pricing. A business that has never raised prices has never learned what its market will bear. diff --git a/plugins/foreman/content/diagnostics/product-market-fit-diagnosis.md b/plugins/foreman/content/diagnostics/product-market-fit-diagnosis.md new file mode 100644 index 0000000..d22518d --- /dev/null +++ b/plugins/foreman/content/diagnostics/product-market-fit-diagnosis.md @@ -0,0 +1,121 @@ +--- +name: "product-market-fit-diagnosis" +description: "Performs deep-layer triage on product-market fit problems by distinguishing between solution-problem mismatch, wrong customer segment, premature scaling, feature bloat, and pricing-value disconnect. Use when a first-layer diagnostic identifies weak PMF signals, or when an entrepreneur reports usage without enthusiasm, retention without growth, or interest without revenue." +entry_symptoms: + - "Customers use it but don't love it" + - "Retention is low despite good acquisition" + - "Mixed signals from NPS" + - "People say it's nice but don't pay" + - "We have users but no fans" +possible_diagnoses: + - solution-looking-for-a-problem + - right-problem-wrong-solution + - right-solution-wrong-segment + - premature-scaling + - feature-bloat-masking-weak-core + - pricing-value-disconnect +routes_to_skills: + - business-model-canvas + - net-promoter-score + - four-ps-marketing + - blue-ocean-strategy + - product-life-cycle + - disruptive-innovation +routes_to_templates: + - unit-economics-snapshot + - strategic-analysis-one-pager +author: "Fatih Guner" +--- + +# Product-Market Fit Diagnosis + +## Entry Symptoms + +The entrepreneur describes a paradox: metrics suggest traction, yet the business feels hollow. "People use it but nobody raves about it." "We have decent acquisition but retention is anaemic." "NPS is a confusing spread — some love it, some shrug." These are the telltale signs of product-market fit that is close enough to be dangerous and far enough to be fatal. + +## Triage Questions + +### Q1: The Sean Ellis Test — If your product disappeared tomorrow, what percentage of users would be very disappointed? + +- **Under 20%** — product-market fit does not exist in meaningful form. Proceed to Q2 to determine why. +- **20-40%** — a kernel of fit exists in a subset. Proceed to Q3 to identify which subset. +- **Over 40%** — fit likely exists but something else is blocking growth. Proceed to Q4 and Q5. + +### Q2: Did the product start from a specific customer pain, or from a technology or idea the team found interesting? + +- **From a pain point discovered through customer research or personal experience** — the problem is real, but the solution may not match it well. Likely diagnosis: **right-problem-wrong-solution**. Confirm with Q4. +- **From a technology capability, an intellectual interest, or a market trend** — likely diagnosis: **solution-looking-for-a-problem**. The team built something clever before verifying someone needed it. +- **From a combination — real pain observed, then heavily reinterpreted through the team's lens** — proceed to Q3. The problem often lives in the translation. + +### Q3: Who are the users who do love the product, and do they resemble your target customer? + +- **The enthusiasts are a different segment from the one you're targeting** — likely diagnosis: **right-solution-wrong-segment**. The product works, but the go-to-market aims at the wrong audience. +- **There are no clear enthusiasts — satisfaction is lukewarm across the board** — likely diagnosis: **right-problem-wrong-solution** or **feature-bloat-masking-weak-core**. Proceed to Q4. +- **The enthusiasts match the target, but they're a small minority** — the value proposition resonates narrowly. Proceed to Q5 to determine whether the barrier is awareness or pricing. + +### Q4: Which features do engaged users actually use, and how often? + +- **Users engage deeply with one or two core features and ignore the rest** — the core has value, but the product is cluttered. Likely diagnosis: **feature-bloat-masking-weak-core**. Strip back to what works. +- **Usage is shallow and spread across many features — nothing dominates** — the product lacks a gravitational centre. Likely diagnosis: **right-problem-wrong-solution**. The architecture may need rethinking, not iteration. +- **Users engage frequently but in short sessions with declining return visits** — the product creates initial curiosity without lasting habit. Likely diagnosis: **right-problem-wrong-solution** compounded by weak retention mechanics. + +### Q5: What happens when you raise the price or ask free users to pay? + +- **Silence — no complaints, no conversions, people simply leave** — the product is valued at zero. Likely diagnosis: **pricing-value-disconnect** or **solution-looking-for-a-problem**. +- **Vocal resistance — "too expensive" — but users keep using the free version** — likely diagnosis: **pricing-value-disconnect**. The value exists but the pricing model fails to capture it. +- **Healthy conversion with minimal friction** — pricing is not the problem. Return to Q1 and Q3; the fit issue sits in audience reach or positioning, not value delivery. + +### Q6: Is your growth organic (word of mouth, referrals) or entirely paid? + +- **Almost entirely paid — turn off ads and growth stops** — the product lacks natural pull. Likely diagnosis: **premature-scaling**. The business is pouring fuel on a fire that has not yet caught. +- **Some organic growth but it plateaued early** — a ceiling exists. Likely diagnosis: **right-solution-wrong-segment** or **feature-bloat-masking-weak-core**. +- **Strong organic growth** — product-market fit likely exists. The problem sits elsewhere (pricing, ops, market size). Route to `revenue-diagnosis` or `pricing-diagnosis` for further triage. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Solution looking for a problem** | Built from technology, not pain; Ellis test under 20%; users leave when asked to pay | Q1 shows low disappointment + Q2 shows idea-first origin | +| **Right problem, wrong solution** | Real pain identified but shallow/scattered usage; lukewarm satisfaction | Q2 shows pain-first origin + Q4 shows shallow engagement | +| **Right solution, wrong segment** | Enthusiasts exist but don't match target customer; messaging mismatch | Q3 shows segment divergence + Q1 shows partial fit | +| **Premature scaling** | Growth entirely paid; unit economics negative; team scaling ahead of demand | Q6 shows no organic pull + Q1 shows sub-40% disappointment | +| **Feature bloat masking weak core** | Deep usage on 1-2 features, rest ignored; product complexity rising | Q4 shows concentrated usage + Q3 shows diluted satisfaction | +| **Pricing-value disconnect** | Users stay on free tier; vocal price resistance; high engagement but no revenue | Q5 shows conversion failure + Q4 shows genuine usage | + +## Routing + +**Solution looking for a problem:** +1. Apply `business-model-canvas` — rebuild from customer segment and value proposition, not from product features +2. Apply `blue-ocean-strategy` — explore whether the solution creates value in a space the team has not considered +3. Output with `strategic-analysis-one-pager` + +**Right problem, wrong solution:** +1. Apply `net-promoter-score` — identify what users actually value versus what the product delivers +2. Apply `business-model-canvas` — reconstruct the solution around validated pain points +3. Output with `unit-economics-snapshot` + +**Right solution, wrong segment:** +1. Apply `four-ps-marketing` — realign positioning and channels to the segment that responds +2. Apply `blue-ocean-strategy` — determine if the responding segment represents a viable market +3. Output with `strategic-analysis-one-pager` + +**Premature scaling:** +1. Apply `product-life-cycle` — confirm the product's actual maturity stage versus assumed stage +2. Apply `business-model-canvas` — stress-test whether the business model justifies current burn rate +3. Output with `unit-economics-snapshot` + +**Feature bloat masking weak core:** +1. Apply `net-promoter-score` — isolate what drives loyalty from what creates noise +2. Apply `disruptive-innovation` — assess whether stripping down could unlock a focused value proposition +3. Output with `strategic-analysis-one-pager` + +**Pricing-value disconnect:** +1. Apply `four-ps-marketing` — reconstruct the price-value equation +2. Apply `business-model-canvas` — evaluate alternative revenue models (subscription, usage-based, tiered) +3. Output with `unit-economics-snapshot` + +## Red Flags + +- **The founder has pivoted the value proposition more than three times in the past year without running structured experiments.** This pattern suggests reactive thrashing, not iterative learning. Before running another pivot, apply disciplined experiment design. +- **The company has raised significant capital and scaled the team ahead of product-market fit evidence.** Capital creates an illusion of progress. Premature scaling with venture funding is the leading cause of startup death — the runway masks the absence of pull. +- **NPS scores show extreme bipolarity (many 9-10s alongside many 1-3s, with little in between).** This often indicates two distinct products serving two distinct segments under one roof. The company may need to choose which product it actually is. diff --git a/plugins/foreman/content/diagnostics/revenue-diagnosis.md b/plugins/foreman/content/diagnostics/revenue-diagnosis.md new file mode 100644 index 0000000..b4ee00f --- /dev/null +++ b/plugins/foreman/content/diagnostics/revenue-diagnosis.md @@ -0,0 +1,133 @@ +--- +name: "revenue-diagnosis" +description: "Identifies the root cause of revenue decline or stagnation by distinguishing between acquisition failures, retention breakdowns, pricing misalignment, and market-level shifts. Use when an entrepreneur reports dropping sales, stalled revenue growth, or inability to close deals." +entry_symptoms: + - "Sales are dropping" + - "Revenue isn't growing" + - "We can't close deals" + - "Customers aren't buying" + - "Our pipeline dried up" +possible_diagnoses: + - pricing-misalignment + - high-churn + - weak-product-market-fit + - broken-go-to-market + - market-contraction + - sales-team-capability-gap +routes_to_skills: + - porters-five-forces + - four-ps-marketing + - net-promoter-score + - product-life-cycle + - business-model-canvas + - swot-pest-analysis +routes_to_templates: + - strategic-analysis-one-pager + - quarterly-strategic-review + - unit-economics-snapshot +author: "Fatih Guner" +--- + +# Revenue Diagnosis + +## First-response contract + +Until comparable revenue components are available, the result is **cause not established**. If the only acquisition evidence is that new customers still arrive, explicitly tell the founder that this does not establish whether acquisition revenue is improving or deteriorating. Customer counts, customer quality, conversion and realized price can move differently. + +Build the opening answer around the revenue bridge, with unknown components marked unknown: opening revenue + new revenue + expansion - contraction - churn = closing revenue. Ask for the previous and current period's new revenue and lost/contracted existing revenue. Keep acquisition, retention and pricing hypotheses open until those measurements distinguish them. Do not label the cause "existing customers" merely because acquisition is nonzero. Do not invent a universal churn target, NPS threshold, or ideal rate. + +Recommend collecting or reconciling these measurements as the first action. A channel shutdown, pricing reversal, or product change requires additional evidence. Once the measurements exist, use the triage below and explain which observation supports the selected branch. + +## Entry Symptoms + +The entrepreneur says some version of: "Sales are dropping," "We can't close deals anymore," "Revenue has flatlined," or "Our pipeline dried up." The complaint centres on money not coming in — but the underlying cause could be anything from a broken pricing model to a dying market. + +## Triage Questions + +Treat the branches below as hypotheses to investigate. Start with a revenue bridge over one consistent period: opening revenue + new customer revenue + expansion - contraction - churn = closing revenue. Ask for the missing components before excluding a cause. New customers can still arrive while acquisition volume, conversion, customer quality, or average deal size deteriorates. + +### Q1: Is the revenue problem coming from new customers or existing customers? + +- **New customer revenue is below the comparable baseline** — investigate acquisition and conversion in Q2 +- **Existing customer revenue is below the comparable baseline** — investigate churn, contraction and expansion in Q4 +- **Both** — proceed to Q2, then Q4; the diagnosis will compound +- **Unknown, or only customer counts are available** — request new and existing revenue, customer counts and average revenue for the same periods. Keep both acquisition and retention hypotheses open. + +### Q2: What does your sales pipeline look like right now? + +- **Pipeline is full but deals aren't closing** — the problem sits at conversion. Proceed to Q3. +- **Pipeline is thin — fewer leads entering** — the problem sits at awareness or channel reach. Likely diagnosis: **broken-go-to-market**. Confirm with Q6. +- **Pipeline looks normal but average deal size is shrinking** — likely diagnosis: **pricing-misalignment**. Confirm with Q3. + +### Q3: Has your pricing, packaging, or discounting changed in the last 6 months? + +- **Yes, we changed pricing** — investigate **pricing-misalignment**. Compare conversion, realized prices and churn before and after the change; timing alone does not establish causation. +- **No, pricing is unchanged but competitors undercut us** — likely diagnosis: **market-contraction** or competitive pressure. Proceed to Q6. +- **No, and we're discounting more just to close** — the product's perceived value is eroding. Likely diagnosis: **weak-product-market-fit**. Proceed to Q5. + +### Q4: What does your churn data show? + +- **Churn is rising — customers leave within 3-6 months** — investigate **high-churn**. Check cohort mix, expectations, onboarding, customer fit and value delivery before selecting an intervention. +- **Churn is stable but expansion revenue is flat** — examine monetisation and expansion opportunities while checking whether the stable churn level itself is sustainable. Pricing is one hypothesis; adoption and customer budget constraints are alternatives. +- **Churn is rising and NPS is falling simultaneously** — likely diagnosis: **weak-product-market-fit**. The original problem the product solved may no longer exist or matter. + +### Q5: Is the product still solving the problem it was built to solve? + +- **Yes, but customers have more alternatives now** — the market matured. Likely diagnosis: **market-contraction** or commoditisation. +- **The customer's problem has shifted** — likely diagnosis: **weak-product-market-fit**. The value proposition needs rebuilding. +- **We're not sure what problem customers think we solve** — likely diagnosis: **weak-product-market-fit** compounded by **broken-go-to-market**. + +### Q6: Has the competitive landscape changed meaningfully in the past year? + +- **New entrants appeared with lower prices or better features** — likely diagnosis: **market-contraction** (if industry-wide) or **broken-go-to-market** (if positioning failed to adapt). +- **No significant competitive change** — return to Q2 and Q5, and check demand, regulation and macroeconomic conditions. Absence of a new competitor does not prove an internal cause. +- **A major competitor exited, yet our sales still dropped** — investigate both shrinking market demand and ability to capture suitable buyers. A competitor exit alone does not establish a sales-team capability gap. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confidence Threshold | +|-----------|------------|---------------------| +| **Pricing misalignment** | Deal sizes shrinking, heavy discounting, pricing recently changed, competitors undercut | Q3 confirms pricing shift + Q2 shows pipeline-to-close gap | +| **High churn** | Rising churn rate, declining NPS, customers leave within 6 months | Q4 shows churn data + Q5 shows product still relevant | +| **Weak product-market fit** | NPS falling, unclear value prop, customer problem shifted | Q5 confirms problem shift + Q4 shows churn + NPS decline | +| **Broken go-to-market** | Thin pipeline, low awareness, channels underperforming | Q2 shows thin pipeline + Q6 shows no competitive excuse | +| **Market contraction** | Industry-wide decline, new entrants commoditising, category maturation | Q6 confirms competitive shift + Q5 shows external cause | +| **Sales team capability gap** | Pipeline exists but close rates dropped, opportunity present but uncaptured | Q2 shows full pipeline + Q6 shows opportunity + Q3 shows no pricing issue | + +## Routing + +**Pricing misalignment:** +1. Apply `four-ps-marketing` — reconstruct the value-price equation +2. Apply `business-model-canvas` — stress-test the revenue model +3. Output with `unit-economics-snapshot` + +**High churn:** +1. Apply `net-promoter-score` — quantify the loyalty gap +2. Apply `product-life-cycle` — determine where the product sits in its arc +3. Output with `quarterly-strategic-review` + +**Weak product-market fit:** +1. Apply `business-model-canvas` — rebuild the value proposition from scratch +2. Apply `net-promoter-score` — measure current customer sentiment +3. Output with `strategic-analysis-one-pager` + +**Broken go-to-market:** +1. Apply `four-ps-marketing` — audit all four dimensions +2. Apply `porters-five-forces` — understand channel and buyer power dynamics +3. Output with `strategic-analysis-one-pager` + +**Market contraction:** +1. Apply `porters-five-forces` — map the full competitive structure +2. Apply `product-life-cycle` — confirm maturity stage +3. Output with `quarterly-strategic-review` + +**Sales team capability gap:** +1. Apply `porters-five-forces` — confirm the opportunity is real +2. Apply `hackman-enabling-conditions` — assess team structure and support +3. Output with `team-health-check` + +## Red Flags + +- **Revenue dropped more than 40% in a single quarter with no obvious cause.** This may indicate fraud, data integrity issues, or a contractual event outside strategic diagnosis. Engage a forensic accountant or CFO-level review before applying frameworks. +- **The entrepreneur cannot produce any pipeline, churn, or revenue data.** Without baseline metrics, diagnostic accuracy is unreliable. Route to basic financial instrumentation before strategic analysis. +- **Cash runway is under 8 weeks.** Revenue diagnosis is irrelevant if the company cannot survive long enough to act on findings. Prioritise emergency fundraising or cost restructuring. diff --git a/plugins/foreman/content/diagnostics/strategic-drift-diagnosis.md b/plugins/foreman/content/diagnostics/strategic-drift-diagnosis.md new file mode 100644 index 0000000..87ebead --- /dev/null +++ b/plugins/foreman/content/diagnostics/strategic-drift-diagnosis.md @@ -0,0 +1,117 @@ +--- +name: "strategic-drift-diagnosis" +description: "Diagnoses the root cause when an entrepreneur reports loss of strategic direction -- whether from founder-driven distraction, priority proliferation, unacknowledged market shifts, or gradual vision erosion. Separates internal chaos from legitimate external pivots and routes to the appropriate strategic realignment intervention." +entry_symptoms: + - "We've lost focus" + - "I don't know our strategy anymore" + - "We're doing too many things" + - "The team doesn't know what matters" + - "We keep changing direction" +possible_diagnoses: + - vision-erosion + - founder-driven-distraction + - priority-proliferation + - market-shift-unacknowledged + - strategic-misalignment + - shiny-object-syndrome +routes_to_skills: + - swot-pest-analysis + - scenario-planning + - strategic-thinking-and-alignment + - focus-and-priority-management + - eisenhower-matrix + - defining-and-exploring-problems + - enemies-of-clear-thinking + - wanting-what-matters +routes_to_templates: + - quarterly-strategic-review + - action-plan + - weekly-ceo-review + - decision-journal +author: "Fatih Guner" +--- + +# Strategic Drift Diagnosis + +Strategy dies quietly. It rarely announces its departure with a dramatic pivot or a board revolt. Instead, it erodes through a thousand small decisions -- each individually reasonable, collectively fatal. The founder adds one more product line. The team chases a tangential partnership. A competitor's move triggers a reactive sprint. Six months later, no one can articulate what the company actually does, and every Monday feels like starting over. + +--- + +## Entry Symptoms + +The entrepreneur typically presents with one or more of these complaints: + +- **"We've lost focus."** The company is working on many things but excelling at none; energy is dispersed across too many fronts. +- **"I don't know our strategy anymore."** The founder cannot state the company's strategic direction in a single clear sentence -- or gives a different answer each time asked. +- **"We're doing too many things."** The product roadmap resembles a wish list; the team is spread thin; nothing ships with conviction. +- **"The team doesn't know what matters."** Employees prioritise based on whoever shouted last; there is no shared understanding of strategic priorities. +- **"We keep changing direction."** Quarterly plans are abandoned by month two; the team experiences whiplash from frequent course corrections. + +--- + +## Triage Questions + +Work through these sequentially. Each answer narrows the diagnosis. + +1. **Historical clarity**: Was there ever a clear, articulated strategy that the team understood and could repeat? Or has the company always operated without one? +2. **Erosion pattern**: Did focus erode gradually over months, or did a specific event trigger the drift (new competitor, failed launch, new investor pressure)? +3. **Source of distraction**: Is the founder the primary source of new directions and tangential ideas? Or is the drift coming from the team, the market, or external stakeholders? +4. **Priority count**: How many "top priorities" does the company currently have? Fewer than three suggests zero clarity; more than five suggests priority proliferation. +5. **Market signal**: Has the market genuinely shifted in ways that demand strategic adaptation? Or is the company changing direction while the market remains stable? +6. **Decision architecture**: Is there a regular cadence for strategic review (quarterly, monthly)? Or do strategic decisions happen reactively, in the moment? + +--- + +## Diagnosis Map + +| Diagnosis | Key Indicators | Core Problem | +|-----------|---------------|--------------| +| **Vision Erosion** | Original vision was clear but has faded; no one references it; daily decisions have disconnected from founding purpose | The strategy existed but was never reinforced, documented, or tied to operational decisions -- it withered from neglect | +| **Founder-Driven Distraction** | New ideas arrive weekly from the founder; team cannot finish projects before the next pivot; the founder's enthusiasm outpaces organisational capacity | The founder confuses ideation with strategy; their creative energy, unfiltered, destabilises the team | +| **Priority Proliferation** | Everything is priority one; resource allocation resembles peanut butter spread evenly; no initiative receives sufficient investment to succeed | The organisation cannot say no; each new opportunity is added without removing an existing one | +| **Market Shift Unacknowledged** | Customer behaviour has changed, competitor landscape has shifted, but the company's strategy still reflects the old reality | The environment has moved and the company has not; the drift is not internal chaos but external denial | +| **Strategic Misalignment** | Different departments or co-founders hold different understandings of the strategy; execution diverges despite apparent agreement at the top | Alignment was assumed but never verified; the strategy was communicated once and interpreted differently by each listener | +| **Shiny Object Syndrome** | Pattern of chasing trends (AI, crypto, new markets) without connection to core competence; excitement-driven rather than analysis-driven decisions | The company pursues novelty over depth; each new trend feels urgent but produces no lasting strategic value | + +--- + +## Routing + +### Vision Erosion +- **Primary skills**: strategic-thinking-and-alignment, wanting-what-matters +- **Supporting skills**: focus-and-priority-management +- **Templates**: quarterly-strategic-review, weekly-ceo-review + +### Founder-Driven Distraction +- **Primary skills**: enemies-of-clear-thinking, focus-and-priority-management +- **Supporting skills**: eisenhower-matrix, wanting-what-matters +- **Templates**: decision-journal, weekly-ceo-review + +### Priority Proliferation +- **Primary skills**: focus-and-priority-management, eisenhower-matrix +- **Supporting skills**: strategic-thinking-and-alignment, defining-and-exploring-problems +- **Templates**: quarterly-strategic-review, action-plan + +### Market Shift Unacknowledged +- **Primary skills**: swot-pest-analysis, scenario-planning +- **Supporting skills**: defining-and-exploring-problems +- **Templates**: quarterly-strategic-review + +### Strategic Misalignment +- **Primary skills**: strategic-thinking-and-alignment, focus-and-priority-management +- **Templates**: quarterly-strategic-review, action-plan + +### Shiny Object Syndrome +- **Primary skills**: enemies-of-clear-thinking, wanting-what-matters +- **Supporting skills**: focus-and-priority-management, eisenhower-matrix +- **Templates**: decision-journal + +--- + +## Red Flags + +- **The founder describes constant pivoting as "agility."** Genuine agility is deliberate adaptation with clear reasoning. If direction changes lack documented rationale, the company is drifting, not adapting. The founder may resist this diagnosis. +- **Strategic drift is actually strategic absence.** Some companies never had a strategy to lose. If triage question one reveals there was never a clear strategy, the problem is not drift but omission. Route to strategic-thinking-and-alignment as a foundational exercise, not a corrective one. +- **Multiple co-founders pulling in different directions.** Strategic misalignment among co-founders is a governance crisis, not a planning problem. Surface this explicitly; frameworks alone will not resolve it without direct conversation and decision-rights clarity. +- **The team has stopped caring about strategy announcements.** Repeated direction changes create learned helplessness. If the team ignores new priorities because they expect them to change, the founder must rebuild credibility through consistent follow-through before any strategic exercise will be taken seriously. +- **"We keep changing direction" but revenue is growing.** Examine whether the perceived drift is actually healthy experimentation that the founder has not yet recognised as strategic search. Early-stage companies exploring product-market fit may exhibit symptoms of drift that are, in reality, appropriate discovery. diff --git a/plugins/foreman/content/diagnostics/team-dysfunction-diagnosis.md b/plugins/foreman/content/diagnostics/team-dysfunction-diagnosis.md new file mode 100644 index 0000000..a890a1a --- /dev/null +++ b/plugins/foreman/content/diagnostics/team-dysfunction-diagnosis.md @@ -0,0 +1,125 @@ +--- +name: "team-dysfunction-diagnosis" +description: "Identifies the root cause of team dysfunction by distinguishing between psychological safety deficits, unclear roles, culture erosion, leadership style mismatches, burnout, and hiring mistakes. Use when an entrepreneur reports low morale, high turnover, persistent conflict, or a general sense that the team is broken." +entry_symptoms: + - "The team isn't working" + - "Morale is low" + - "People are leaving" + - "Too much conflict" + - "Nobody takes ownership" + - "We used to work well together" +possible_diagnoses: + - psychological-safety-deficit + - unclear-roles + - culture-erosion + - leadership-style-mismatch + - burnout-epidemic + - hiring-mistakes +routes_to_skills: + - tuckman-team-stages + - hackman-enabling-conditions + - psychological-safety + - belbin-team-roles + - organisational-culture + - situational-leadership +routes_to_templates: + - team-health-check + - feedback-360-template + - culture-values-document +author: "Fatih Guner" +--- + +# Team Dysfunction Diagnosis + +Role ambiguity can explain a pattern but does not prove why particular colleagues blame each other. Ask about one concrete delayed decision or handoff before attributing motives or declaring a root cause. + +## Entry Symptoms + +The entrepreneur describes breakdown in human terms: "The team isn't working," "Morale is terrible," "People keep leaving," or "Nobody takes ownership." These complaints are almost always symptoms, not causes. A team that "isn't working" could be suffering from a dozen different ailments — and the wrong treatment makes most of them worse. + +## Triage Questions + +### Q1: When did the dysfunction start? + +- **After a specific event (a firing, a reorganisation, a failed project, a funding round)** — the dysfunction is reactive. Proceed to Q3 to assess structural fallout. +- **It built gradually over months** — the dysfunction is systemic. Proceed to Q2. +- **It has always been this way** — the team may have been poorly constructed from the start. Likely diagnosis: **hiring-mistakes**. Confirm with Q5. + +### Q2: Is the dysfunction affecting the whole team or concentrated in specific individuals or groups? + +- **The whole team — pervasive low energy, disengagement, or frustration** — this points to environmental causes. Proceed to Q4. +- **Specific individuals or a subgroup** — this points to interpersonal or role-based causes. Proceed to Q3. +- **It shifts depending on the project or week** — the team lacks stable operating norms. Likely diagnosis: **unclear-roles**. Confirm with Q3. + +### Q3: Are roles, responsibilities, and decision rights clear to everyone on the team? + +- **No — people overlap, compete for territory, or don't know who decides what** — likely diagnosis: **unclear-roles**. The most common cause of team friction that founders mislabel as "personality conflict." +- **Roles are clear on paper, but people don't feel empowered to act** — likely diagnosis: **psychological-safety-deficit**. People know their role but fear consequences of exercising it. +- **Roles are clear, people act on them, but there's still conflict** — proceed to Q4. The issue sits deeper. + +### Q4: Do people feel safe to speak up, disagree, admit mistakes, and ask for help? + +- **No — dissent is punished or ignored, mistakes are hidden, meetings are performative** — likely diagnosis: **psychological-safety-deficit**. This is the foundational issue and must be addressed before other interventions can take hold. +- **People speak up but nothing changes — leadership doesn't act on feedback** — likely diagnosis: **leadership-style-mismatch**. The leader's approach is misaligned with what the team needs. +- **People are too exhausted to care — they've stopped engaging entirely** — likely diagnosis: **burnout-epidemic**. Proceed to Q6 for confirmation. + +### Q5: Looking at the last 5 hires, how many are performing at the level expected when they were hired? + +- **Fewer than half** — likely diagnosis: **hiring-mistakes**. The team's composition is the root problem, not its dynamics. +- **Most are performing well individually, but the team doesn't gel** — the issue is relational, not individual. Return to Q3 and Q4 for structural and psychological causes. +- **Performance was strong initially but has degraded over time** — the environment is eroding capability. Likely diagnosis: **culture-erosion** or **burnout-epidemic**. Proceed to Q6. + +### Q6: What does the leader's typical week look like in relation to the team? + +- **The leader is in every meeting, makes most decisions, and is the bottleneck** — likely diagnosis: **leadership-style-mismatch** (over-centralised). The team has learned helplessness. +- **The leader is absent — travelling, fundraising, or focused elsewhere** — likely diagnosis: **culture-erosion**. Without active leadership presence, norms decay. +- **The leader is present but the team seems to work around them** — likely diagnosis: **leadership-style-mismatch**. The leader has lost the team's trust or respect. +- **The leader is working 80-hour weeks and expects the same from the team** — likely diagnosis: **burnout-epidemic**, driven from the top. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Psychological safety deficit** | Silence in meetings, hidden mistakes, fear of dissent, performative agreement | Q4 confirms fear + Q3 shows roles clear but unused | +| **Unclear roles** | Territory disputes, duplicated work, decision paralysis, "that's not my job" | Q3 confirms ambiguity + Q2 shows shifting dysfunction | +| **Culture erosion** | Gradual disengagement, "it used to be different," leader absent, norms inconsistent | Q1 shows gradual onset + Q6 shows leadership absence | +| **Leadership style mismatch** | Feedback ignored, leader bottlenecks decisions, team works around leader | Q4 shows feedback futility + Q6 shows centralisation or disconnect | +| **Burnout epidemic** | Exhaustion, disengagement, cynicism, high absenteeism, leader overworking | Q4 shows apathy + Q6 shows unsustainable pace from top | +| **Hiring mistakes** | Persistent underperformance, cultural misfit, team never cohered | Q1 shows "always this way" + Q5 confirms performance gaps | + +## Routing + +**Psychological safety deficit:** +1. Apply `psychological-safety` — build the diagnostic framework and intervention plan +2. Apply `tuckman-team-stages` — assess whether the team regressed to an earlier stage +3. Output with `team-health-check` + +**Unclear roles:** +1. Apply `belbin-team-roles` — map natural role preferences and identify gaps or overlaps +2. Apply `hackman-enabling-conditions` — establish the structural conditions for clarity +3. Output with `team-health-check` and `role-description-template` + +**Culture erosion:** +1. Apply `organisational-culture` — diagnose the current culture versus the desired culture +2. Apply `tuckman-team-stages` — assess team developmental regression +3. Output with `culture-values-document` + +**Leadership style mismatch:** +1. Apply `situational-leadership` — match leadership style to team maturity and context +2. Output with `feedback-360-template` and `one-on-one-template` + +**Burnout epidemic:** +1. Apply `leader-resilience-and-wellbeing` — address the leader's own burnout first +2. Apply `hackman-enabling-conditions` — redesign workload and support structures +3. Output with `team-health-check` + +**Hiring mistakes:** +1. Apply `belbin-team-roles` — understand what the team actually needs versus what it has +2. Apply `hackman-enabling-conditions` — determine if the right people are in the wrong structure +3. Output with `hiring-scorecard` and `team-health-check` + +## Red Flags + +- **An employee has made a formal harassment, discrimination, or safety complaint.** This is a legal and HR matter that requires professional investigation, not a framework exercise. Engage employment counsel immediately. +- **The entrepreneur describes the dysfunction but refuses to consider that they might be the cause.** Every diagnostic path in this system includes the possibility that leadership is the root issue. If the founder categorically rejects this, the diagnostic cannot function honestly. +- **Turnover exceeds 40% annually and the company has fewer than 20 people.** At this scale and rate, the organisation is in existential staffing crisis. Stabilise before diagnosing culture. diff --git a/plugins/foreman/content/hooks/_schema/hook-template.md b/plugins/foreman/content/hooks/_schema/hook-template.md new file mode 100644 index 0000000..1cad377 --- /dev/null +++ b/plugins/foreman/content/hooks/_schema/hook-template.md @@ -0,0 +1,105 @@ +--- +name: "kebab-case-hook-name" +description: "Third-person description of what intent this hook captures and what entrepreneur language it matches. Max 1024 characters." +trigger_patterns: + - "natural language phrase an entrepreneur might say" + - "another common phrasing" + - "emotional variant" + - "question variant" + - "complaint variant" +routes_to: + diagnostics: + - diagnostic-name + skills: + - skill-name + playbooks: + - playbook-name +priority: "high | medium | low" +author: "Fatih Guner" +--- + + + +# {Hook Title} + +## Trigger Patterns + + + +| Pattern | Confidence | +|---------|-----------| +| "{phrase 1}" | High | +| "{phrase 2}" | High | +| "{phrase 3}" | Medium | + +--- + +## Intent Classification + + + +| Intent | Trigger Signals | Description | +|--------|----------------|-------------| +| {Intent A} | {keywords/phrases} | {What this intent means} | +| {Intent B} | {keywords/phrases} | {What this intent means} | + +--- + +## Routing Logic + + + +``` +Intent A → [Diagnostic: diagnostic-name] +Intent B → [Playbook: playbook-name] +Intent C (simple, clear) → [Skill: skill-name] (direct, no diagnostic needed) +``` + +--- + +## Disambiguation + + + +| Overlapping Hook | Overlap Condition | Resolution | +|-----------------|-------------------|------------| +| {other-hook-name} | {when both match} | {which takes priority and why} | + +--- + +## Example Conversations + +**Example 1:** +- Entrepreneur says: "{natural language input}" +- Hook classifies as: {Intent} +- Routes to: {destination} +- Rationale: {why this routing} + +**Example 2:** +- Entrepreneur says: "{different input}" +- Hook classifies as: {Intent} +- Routes to: {destination} diff --git a/plugins/foreman/content/hooks/communication-hook.md b/plugins/foreman/content/hooks/communication-hook.md new file mode 100644 index 0000000..cd29a4a --- /dev/null +++ b/plugins/foreman/content/hooks/communication-hook.md @@ -0,0 +1,139 @@ +--- +name: "communication-hook" +description: "Hook for communication-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Nobody reads my emails + - Team misunderstands everything + - Investors don't get it + - Meetings are useless + - Can't explain what we do + - My writing sucks + - Presentation went badly + - Internal comms are chaos + - Board doesn't understand our strategy + - I dread public speaking + - Our messaging is all over the place + - People tune out when I talk +routes_to: + diagnostics: + - communication-breakdown-diagnosis + templates: + - meeting-notes-template + skills: + - business-model-canvas + - organisational-culture + - storytelling-for-leaders + - stoic-emotional-mastery + - story-performance-and-delivery + - reader-psychology + - writing-effective-emails + - writing-for-navigation +--- + +# Communication Hook + +Most communication failures are not communication problems. They are thinking problems dressed in communication clothing — unclear strategy presented as unclear writing, misaligned teams presented as bad meetings, weak value propositions presented as investor confusion. The diagnostic challenge is separating genuine skill deficits from upstream clarity failures. + +## Trigger Patterns + +1. "Nobody reads my emails" +2. "Team misunderstands everything" +3. "Investors don't get it" +4. "Meetings are useless" +5. "Can't explain what we do" +6. "My writing sucks" +7. "Presentation went badly" +8. "Internal comms are chaos" +9. "Board doesn't understand our strategy" +10. "I dread public speaking" +11. "Our messaging is all over the place" +12. "People tune out when I talk" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Emails ignored, writing complaints, document problems | `writing-deficit` | High | +| Meetings described as useless, unproductive, chaotic | `meeting-dysfunction` | High | +| Investor or board confusion, pitch failures | `stakeholder-communication` | High | +| Cannot articulate value proposition or company purpose | `messaging-clarity` | Medium | +| Presentation anxiety, public speaking dread | `presentation-anxiety` | High | +| General team misunderstanding, internal miscommunication | `internal-alignment` | Medium | + +## Routing Logic + +``` +IF intent == writing-deficit: + → diagnostics/communication-breakdown-diagnosis + → skills/writing/reader-psychology + → skills/writing/writing-for-navigation + → skills/writing/writing-effective-emails + +IF intent == meeting-dysfunction: + → diagnostics/communication-breakdown-diagnosis + → output-templates/team/meeting-notes-template.md + → skills/writing/writing-for-navigation + +IF intent == stakeholder-communication: + → diagnostics/communication-breakdown-diagnosis + → skills/leadership/storytelling-for-leaders.md + → output-templates/investor/ + → output-templates/board/ + +IF intent == messaging-clarity: + → diagnostics/communication-breakdown-diagnosis + → skills/leadership/storytelling-for-leaders.md + → skills/frameworks/business-model-canvas.md + +IF intent == presentation-anxiety: + → skills/storytelling/story-performance-and-delivery.md + → skills/leadership/storytelling-for-leaders.md + → skills/stoic/stoic-emotional-mastery.md + +IF intent == internal-alignment: + → diagnostics/communication-breakdown-diagnosis + → skills/writing/writing-for-navigation + → skills/frameworks/organisational-culture.md + → output-templates/team/ +``` + +**Priority:** Medium + +## Disambiguation + +Communication is a symptom layer — nearly every business problem eventually manifests as a communication complaint. Careful triage prevents treating the symptom while ignoring the disease. + +- **Strategy hook overlap:** "Can't explain what we do" often means the founder has not decided what they do. If probing reveals strategic ambiguity rather than articulation difficulty, route to `strategy-hook`. +- **Product hook overlap:** "Investors don't get it" may indicate a product-market fit problem, not a pitch problem. If the product's value proposition is genuinely unclear, route to `product-hook`. +- **Team hook overlap:** "Team misunderstands everything" can signal interpersonal conflict, unclear roles, or management structure problems rather than communication skill gaps. Route to `team-hook` if structural. +- **Leadership hook overlap:** Presentation anxiety rooted in impostor syndrome or burnout belongs with `leadership-hook`. + +**Disambiguation prompt:** "Is the problem that you know exactly what to say but struggle to say it well — or that you are not entirely sure what the message should be?" + +## Example Conversations + +**Example 1: Writing deficit** + +> **Founder:** "I spend hours on emails and nobody reads them. Important updates get completely ignored." +> +> **Foreman:** The problem is rarely that people cannot read — it is that your emails are not written for how people actually read. Cognitive science is unambiguous: busy readers scan, skip, and abandon. They do not study your prose. The fix is structural, not stylistic. What types of emails are being ignored — operational updates, decisions that need input, or announcements? +> +> *Routes to: communication-breakdown-diagnosis → reader-psychology → writing-for-navigation → writing-effective-emails* + +**Example 2: Stakeholder confusion** + +> **Founder:** "Every time I pitch to investors, their eyes glaze over by slide three. They just don't get what we're building." +> +> **Foreman:** Glazed eyes by slide three means the narrative arc failed before it began. Investors do not process information sequentially — they pattern-match against mental models of businesses they understand. The question is whether you are giving them a story they can place, or a feature tour they cannot. Walk me through your opening three slides. +> +> *Routes to: communication-breakdown-diagnosis → storytelling-for-leaders → investor output templates* + +**Example 3: Meeting dysfunction** + +> **Founder:** "We have meetings about meetings. Nothing gets decided. Everyone leaves confused." +> +> **Foreman:** Meeting dysfunction is typically a decision-rights problem masquerading as a scheduling problem. When nobody knows who decides, everyone discusses endlessly. Before we redesign your meeting cadence: how many recurring meetings does your team have per week, and can you name a single important decision that was made in one recently? +> +> *Routes to: communication-breakdown-diagnosis → effective-meetings → writing-for-navigation* diff --git a/plugins/foreman/content/hooks/competition-hook.md b/plugins/foreman/content/hooks/competition-hook.md new file mode 100644 index 0000000..95135b7 --- /dev/null +++ b/plugins/foreman/content/hooks/competition-hook.md @@ -0,0 +1,90 @@ +--- +name: "competition-hook" +description: "Captures intent related to competitive threats, market share erosion, price wars, new entrants, and differentiation struggles" +trigger_patterns: + - "competitors are crushing us" + - "price war" + - "big player entered our space" + - "losing market share" + - "being commoditized" + - "can't differentiate" + - "they copied our product" + - "race to the bottom" +routes_to: + diagnostics: + - competitive-threat-diagnosis + skills: + - porters-five-forces + - blue-ocean-strategy + - disruptive-innovation + - art-of-war + playbooks: + - competitive-response-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Competition Hook + +## Trigger Patterns + +Competitive anxiety ranges from strategic concern to existential dread. Founders articulate it through market observations, customer loss stories, and raw frustration. + +- "Competitors are crushing us on price" +- "We're in a price war and losing" +- "A big player just entered our market" +- "We're losing market share every quarter" +- "Our product is being commoditized" +- "Can't differentiate from the competition" +- "They copied our entire feature set" +- "It's a race to the bottom and we can't win" +- "Amazon / Google / Microsoft just launched something like ours" +- "A well-funded competitor is undercutting us" +- "Customers keep comparing us to cheaper alternatives" +- "Our moat disappeared overnight" +- "We used to be unique but now everyone does what we do" +- "How do I compete against someone with ten times our budget?" +- "New startups keep entering our space every month" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Price war, race to bottom, undercutting | Price-based competition | High | +| Big player, well-funded competitor, Amazon entering | Asymmetric threat | High | +| Losing market share, commoditized, moat disappeared | Differentiation erosion | High | +| Copied product, everyone does what we do | Feature parity threat | Medium | +| New startups entering, crowded market | Market saturation | Medium | + +## Routing Logic + +**Price-based competition** -- Route to `competitive-threat-diagnosis`. Price wars are symptoms; the diagnosis determines whether the root cause is undifferentiation, cost structure, or market dynamics. The `porters-five-forces` skill maps the competitive landscape. If the founder needs a strategic response, escalate to `competitive-response-playbook`. + +**Asymmetric threat** -- Route to `competitive-threat-diagnosis` with urgency. When a dramatically larger player enters the market, the response framework differs from peer competition. `blue-ocean-strategy` helps identify uncontested spaces. `art-of-war` provides asymmetric response patterns. + +**Differentiation erosion** -- Route directly to `competitive-response-playbook` if the founder has a clear picture of the competitive landscape. Otherwise, start with `competitive-threat-diagnosis`. The `disruptive-innovation` skill can reveal whether the founder should move upmarket or down. + +**Feature parity threat** -- Route to `competitive-threat-diagnosis`. When competitors replicate features, the real question is whether the founder's advantage was ever defensible. `porters-five-forces` evaluates structural defensibility. + +**Market saturation** -- Route to `competitive-threat-diagnosis` for landscape mapping, then consider `blue-ocean-strategy` for category creation. + +## Disambiguation + +This hook overlaps with `revenue-and-sales-hook` when competitive pressure manifests as lost deals or pricing pushback. The distinguishing signal: if the entrepreneur frames the problem around a specific competitor or market dynamic, this hook applies. If they frame it around their own sales numbers without reference to external forces, route to `revenue-and-sales-hook`. Overlap with `strategy-hook` occurs when competitive pressure triggers strategic questioning. If "competitors are crushing us" leads to "maybe we should pivot," the strategy-hook should take over. + +## Example Conversations + +**Example 1: Price war** +Entrepreneur says: "A VC-backed competitor dropped their price to zero for the first year. Our customers are switching." +Hook classifies as: Price-based competition with asymmetric funding. +Routes to: `competitive-threat-diagnosis` to assess sustainability of the threat, then `competitive-response-playbook` for counter-strategy. + +**Example 2: Differentiation collapse** +Entrepreneur says: "Three years ago we were the only ones doing this. Now there are twelve competitors and they all look the same." +Hook classifies as: Differentiation erosion. +Routes to: `competitive-threat-diagnosis`, likely escalating to `blue-ocean-strategy` for category redefinition. + +**Example 3: Giant enters the market** +Entrepreneur says: "Microsoft just announced a feature that does exactly what our entire product does." +Hook classifies as: Asymmetric threat. +Routes to: `competitive-threat-diagnosis` with urgency, then `art-of-war` for asymmetric positioning and `disruptive-innovation` for niche defense. diff --git a/plugins/foreman/content/hooks/culture-hook.md b/plugins/foreman/content/hooks/culture-hook.md new file mode 100644 index 0000000..f4e9490 --- /dev/null +++ b/plugins/foreman/content/hooks/culture-hook.md @@ -0,0 +1,129 @@ +--- +name: "culture-hook" +description: "Hook for culture-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Culture is breaking down + - Values mean nothing here + - New hires don't fit + - We've lost our identity + - Remote killed our culture + - People don't care anymore + - It used to feel different + - We're just a job now + - Nobody lives our values + - The vibe has completely changed + - Culture doesn't scale + - We hired too fast and lost something +routes_to: + diagnostics: + - culture-erosion-diagnosis + templates: + - culture-values-document + - hiring-scorecard + playbooks: + - scaling-playbook + skills: + - organisational-culture + - purpose-driven-leadership + - team-culture-and-dynamics +--- + +# Culture Hook + +Every organisation has a culture. Few have the one they think they do. When the gap between stated values and lived behaviour widens beyond a certain threshold, the organism starts rejecting its own immune system — new hires bounce, veterans disengage, and the founder wonders why the place feels unfamiliar. + +## Trigger Patterns + +1. "Culture is breaking down" +2. "Values mean nothing here" +3. "New hires don't fit" +4. "We've lost our identity" +5. "Remote killed our culture" +6. "People don't care anymore" +7. "It used to feel different" +8. "We're just a job now" +9. "Nobody lives our values" +10. "The vibe has completely changed" +11. "Culture doesn't scale" +12. "We hired too fast and lost something" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| References to lost identity, changed feeling, nostalgia | `culture-erosion` | High | +| New hire friction, onboarding complaints, "don't fit" | `culture-fit-mismatch` | High | +| Remote/hybrid blame, office vs. distributed tension | `remote-culture-strain` | Medium | +| Values described as hollow, performative, or ignored | `values-integrity-gap` | High | +| General disengagement, apathy, "just a job" language | `meaning-deficit` | Medium | +| Rapid growth cited as the catalyst for culture loss | `scaling-culture-dilution` | Medium | + +## Routing Logic + +``` +IF intent == culture-erosion OR values-integrity-gap: + → diagnostics/culture-erosion-diagnosis + → skills/frameworks/organisational-culture.md + → output-templates/team/culture-values-document + +IF intent == culture-fit-mismatch: + → diagnostics/culture-erosion-diagnosis + → skills/leadership/team-culture-and-dynamics + → output-templates/team/hiring-scorecard.md + +IF intent == remote-culture-strain: + → diagnostics/culture-erosion-diagnosis + → skills/frameworks/organisational-culture.md + → skills/leadership/team-culture-and-dynamics + +IF intent == meaning-deficit: + → diagnostics/culture-erosion-diagnosis + → skills/frameworks/organisational-culture.md + → skills/leadership/purpose-driven-leadership.md + +IF intent == scaling-culture-dilution: + → diagnostics/culture-erosion-diagnosis + → skills/frameworks/organisational-culture.md + → playbooks/scaling-playbook.md +``` + +**Priority:** Medium + +## Disambiguation + +Culture complaints frequently mask deeper structural problems. Before routing, probe for these overlaps: + +- **Team hook overlap:** If the complaint centres on specific individuals or interpersonal conflict rather than systemic culture drift, route to `team-hook` instead. +- **Leadership hook overlap:** If the founder describes personal disconnection from the company's identity — burnout disguised as culture concern — route to `leadership-hook`. +- **Growth hook overlap:** If culture erosion is explicitly tied to operational scaling challenges (headcount doubling, new offices, process overload), co-route with `growth-hook`. +- **Strategy hook overlap:** When "lost identity" actually means "lost strategic direction," the culture language is symptomatic. Route to `strategy-hook` as primary. + +**Disambiguation prompt:** "When you say the culture has changed — is this about how people behave day-to-day, or about the company's direction and purpose?" + +## Example Conversations + +**Example 1: Values-integrity gap** + +> **Founder:** "We have five core values on the wall but nobody follows them. They're a joke." +> +> **Foreman:** That gap between declared values and observed behaviour is one of the most corrosive forces in an organisation. Before we address it, a few questions: When did the disconnect become noticeable — was it gradual or tied to a specific event? And which value is most visibly violated? +> +> *Routes to: culture-erosion-diagnosis → organisational-culture → culture-values-document template* + +**Example 2: Remote culture strain** + +> **Founder:** "Ever since we went fully remote, the culture just died. People clock in, do their work, clock out." +> +> **Foreman:** Remote work did not kill your culture — it revealed which parts of it depended on physical proximity rather than shared conviction. The question is whether you had a culture or merely had an office. Let me ask: what specific behaviours or rituals disappeared when the office did? +> +> *Routes to: culture-erosion-diagnosis → organisational-culture → team-culture-and-dynamics* + +**Example 3: Scaling dilution** + +> **Founder:** "We went from 12 to 60 people in a year. It used to feel like a family. Now I don't even know half the team." +> +> **Foreman:** The family metaphor is the first casualty of scaling — and arguably should be. Families do not have performance reviews. The real question is what replaced it, or whether nothing did. Let me help you diagnose what specifically eroded and what can be deliberately rebuilt at your current size. +> +> *Routes to: culture-erosion-diagnosis → organisational-culture → scaling-culture-playbook* diff --git a/plugins/foreman/content/hooks/decision-hook.md b/plugins/foreman/content/hooks/decision-hook.md new file mode 100644 index 0000000..a4fc600 --- /dev/null +++ b/plugins/foreman/content/hooks/decision-hook.md @@ -0,0 +1,139 @@ +--- +name: "decision-hook" +description: "Hook for decision-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Can't decide + - Analysis paralysis + - Every option seems risky + - Going back and forth + - What should I do? + - Too many options + - Afraid of making the wrong call + - Team can't agree on direction + - Need a framework for this decision + - Been debating this for weeks + - Don't have enough information to decide + - Every advisor says something different + - Flip-flopping on this constantly +routes_to: + diagnostics: + - decision-paralysis-diagnosis + templates: + - decision-journal + skills: + - choosing-and-executing + - evaluating-options + - generating-solutions + - tough-decision-situations + - decision-making-under-pressure + - leader-self-reflection + - enemies-of-clear-thinking + - evaluating-and-deciding +--- + +# Decision Hook + +The cost of a wrong decision is almost always lower than the cost of no decision. Founders know this intellectually and ignore it instinctively — cycling through options, gathering more data, polling more advisors, waiting for certainty that will never arrive. Decision paralysis is not a thinking problem. It is a fear problem wearing an analytical disguise. + +## Trigger Patterns + +1. "Can't decide" +2. "Analysis paralysis" +3. "Every option seems risky" +4. "Going back and forth" +5. "What should I do?" +6. "Too many options" +7. "Afraid of making the wrong call" +8. "Team can't agree on direction" +9. "Need a framework for this decision" +10. "Been debating this for weeks" +11. "Don't have enough information to decide" +12. "Every advisor says something different" +13. "Flip-flopping on this constantly" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Explicit paralysis, inability to choose, cycling | `decision-paralysis` | High | +| Fear language — wrong call, risky, afraid | `fear-driven-indecision` | High | +| Team disagreement on direction, no consensus | `collective-indecision` | High | +| Request for frameworks, structured approaches | `decision-framework-need` | Medium | +| Information insufficiency cited as the blocker | `information-gap-excuse` | Medium | +| Conflicting advice from multiple sources | `advisor-confusion` | Medium | + +## Routing Logic + +``` +IF intent == decision-paralysis OR fear-driven-indecision: + → diagnostics/decision-paralysis-diagnosis + → skills/thinking/enemies-of-clear-thinking + → skills/thinking/evaluating-and-deciding.md + → output-templates/self/decision-journal.md + +IF intent == collective-indecision: + → diagnostics/decision-paralysis-diagnosis + → skills/decisions/tough-decision-situations + → skills/decisions/choosing-and-executing.md + → skills/thinking/enemies-of-clear-thinking + +IF intent == decision-framework-need: + → skills/thinking/evaluating-and-deciding.md + → skills/decisions/generating-solutions + → skills/decisions/evaluating-options.md + → output-templates/self/decision-journal.md + +IF intent == information-gap-excuse: + → diagnostics/decision-paralysis-diagnosis + → skills/thinking/enemies-of-clear-thinking + → skills/thinking/evaluating-and-deciding.md + → skills/leadership/decision-making-under-pressure.md + +IF intent == advisor-confusion: + → diagnostics/decision-paralysis-diagnosis + → skills/leadership/leader-self-reflection.md + → skills/thinking/evaluating-and-deciding.md + → skills/decisions/tough-decision-situations +``` + +**Priority:** Medium + +## Disambiguation + +Decision paralysis is one of the most common presenting symptoms across all problem domains. The decision itself often reveals which hook should be primary: + +- **Strategy hook overlap:** If the decision is about company direction — pivot, market, business model — route to `strategy-hook`. The paralysis is a symptom; the strategic question is the disease. +- **Product hook overlap:** Feature prioritisation deadlocks and build-vs-buy decisions route to `product-hook` with decision frameworks as supplementary tools. +- **Fundraising hook overlap:** "Should we raise?" or "Which term sheet?" decisions belong in `fundraising-hook`. +- **Partnership hook overlap:** "Should we take this deal?" involving partnerships, M&A, or cofounders routes to `partnership-hook`. +- **Leadership hook overlap:** When a founder's decision paralysis is chronic and pervasive — affecting all domains — the root cause may be burnout, impostor syndrome, or confidence erosion. Route to `leadership-hook`. + +**Disambiguation prompt:** "What specifically is the decision you are stuck on — and how long have you been deliberating?" + +## Example Conversations + +**Example 1: Classic paralysis** + +> **Founder:** "I've been going back and forth on whether to expand to a second city for two months. I keep making spreadsheets and never pulling the trigger." +> +> **Foreman:** Two months of spreadsheets means the data is not the problem — the decision criteria are. More analysis will not resolve this because you have not defined what "good enough" looks like. The spreadsheets are a procrastination mechanism that feels productive. Let me help you identify what is actually driving the hesitation, because the answer is rarely in the numbers. +> +> *Routes to: decision-paralysis-diagnosis → enemies-of-clear-thinking → evaluating-and-deciding → decision-journal* + +**Example 2: Collective indecision** + +> **Founder:** "My leadership team has been arguing about our pricing model for three weeks. Everyone has a strong opinion and nobody will compromise." +> +> **Foreman:** Three weeks of circular debate means the team is arguing about the wrong thing. Pricing disagreements are rarely about price — they are about customer strategy, competitive positioning, and risk tolerance. The individuals are right about different subproblems and wrong about insisting their subproblem is the whole problem. What are the two or three main positions, and what assumption does each one rest on? +> +> *Routes to: decision-paralysis-diagnosis → tough-decision-situations → consensus-and-commitment* + +**Example 3: Information gap excuse** + +> **Founder:** "I don't have enough data to make this call. I need to run more customer interviews before I can decide." +> +> **Foreman:** The pursuit of more data before deciding is one of the most seductive forms of avoidance. There is a point — and you have likely passed it — where additional information changes the confidence level by fractions of a percent while the delay costs real opportunity. Jeff Bezos aims to decide at 70% certainty. What percentage would you estimate you are at now, and what specific data point would change your answer? +> +> *Routes to: decision-paralysis-diagnosis → enemies-of-clear-thinking → evaluating-and-deciding → seventy-percent-rule* diff --git a/plugins/foreman/content/hooks/fundraising-hook.md b/plugins/foreman/content/hooks/fundraising-hook.md new file mode 100644 index 0000000..19ff901 --- /dev/null +++ b/plugins/foreman/content/hooks/fundraising-hook.md @@ -0,0 +1,93 @@ +--- +name: "fundraising-hook" +description: "Captures intent related to raising capital, investor relations, pitch preparation, valuation disputes, term sheets, and runway anxiety" +trigger_patterns: + - "need to raise money" + - "investors keep saying no" + - "pitch isn't working" + - "VCs ghost me" + - "valuation pushback" + - "don't know how to pitch" + - "Series A prep" + - "running out of runway" + - "need a bridge round" +routes_to: + diagnostics: + - fundraising-diagnosis + skills: + - storytelling-for-leaders + - persuasion-and-influence + - business-model-canvas + playbooks: + - fundraising-playbook + output_templates: + - fundraising-deck-outline + - unit-economics-snapshot +priority: "high" +author: "Fatih Guner" +--- + +# Fundraising Hook + +## Trigger Patterns + +Fundraising is where financial pressure meets emotional vulnerability. Founders describe it through rejection stories, runway countdowns, and confusion about the process itself. + +- "We need to raise money soon" +- "Investors keep saying no and I don't know why" +- "My pitch isn't working" +- "VCs ghost me after the first meeting" +- "Getting pushback on our valuation" +- "I don't know how to pitch to investors" +- "Preparing for our Series A" +- "Running out of runway in four months" +- "We need a bridge round to survive" +- "Should I raise or bootstrap?" +- "How much should I raise?" +- "Investor said our unit economics don't work" +- "Got a term sheet but it looks predatory" +- "Can't get past the partner meeting" +- "Spent six months fundraising with nothing to show" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Need to raise, how much to raise, raise or bootstrap | Fundraising readiness | High | +| Investors say no, VCs ghost, can't get past partner | Pitch failure | High | +| Running out of runway, bridge round, survive | Runway emergency | High | +| Valuation pushback, term sheet, predatory | Deal negotiation | Medium | +| Series A prep, unit economics | Stage-specific preparation | Medium | + +## Routing Logic + +**Fundraising readiness** -- Route to `fundraising-diagnosis`. Founders who are unsure whether to raise often have underlying business model questions. The diagnostic separates "not ready to raise" from "ready but unclear on approach." The `business-model-canvas` skill can pressure-test the underlying model. + +**Pitch failure** -- Route to `fundraising-diagnosis` to determine whether the problem is the pitch, the business, or the targeting. If the business is sound and the issue is communication, escalate to `fundraising-playbook` with emphasis on narrative. The `storytelling-for-leaders` and `persuasion-and-influence` skills strengthen the pitch itself. + +**Runway emergency** -- Route to `fundraising-diagnosis` with urgency. Short runway changes the calculus entirely -- bridge rounds, revenue acceleration, and cost cuts all enter the picture simultaneously. The diagnostic must triage survival versus optimization. + +**Deal negotiation** -- Route to `fundraising-playbook` directly. Term sheet review and valuation negotiation are execution problems, not diagnostic ones. If the founder lacks negotiation fundamentals, the `negotiation-playbook` provides tactical support. + +**Stage-specific preparation** -- Route to `fundraising-playbook` with stage context. Series A preparation has a known checklist; the playbook walks through metrics, narrative, and materials. + +## Disambiguation + +This hook overlaps with `revenue-and-sales-hook` when "running out of runway" is actually a revenue problem dressed as a fundraising question. If the diagnostic reveals the company could become self-sustaining with modest revenue improvements, re-route to `revenue-and-sales-hook`. Overlap with `strategy-hook` occurs when "should I raise?" masks a deeper strategic uncertainty. If the founder questions the entire direction of the business, defer to `strategy-hook`. + +## Example Conversations + +**Example 1: Repeated rejection** +Entrepreneur says: "I've pitched forty VCs and got two second meetings, both of which went nowhere." +Hook classifies as: Pitch failure. +Routes to: `fundraising-diagnosis` to determine whether the pitch, the metrics, or the targeting is the root cause. + +**Example 2: Runway crisis** +Entrepreneur says: "We have maybe three months of cash left. I need to figure out next steps immediately." +Hook classifies as: Runway emergency. +Routes to: `fundraising-diagnosis` with urgency flag to triage between emergency raise, bridge round, revenue acceleration, and cost restructuring. + +**Example 3: Preparation mode** +Entrepreneur says: "We're doing well -- growing 15% month over month. I want to start preparing for a Series A in six months." +Hook classifies as: Stage-specific preparation. +Routes to: `fundraising-playbook` with a preparation timeline, skipping the diagnostic since the intent is clear and the business is healthy. diff --git a/plugins/foreman/content/hooks/growth-hook.md b/plugins/foreman/content/hooks/growth-hook.md new file mode 100644 index 0000000..3e5eab4 --- /dev/null +++ b/plugins/foreman/content/hooks/growth-hook.md @@ -0,0 +1,90 @@ +--- +name: "growth-hook" +description: "Captures intent related to growth plateaus, scaling constraints, operational limits, and the structural challenges of moving from one stage to the next" +trigger_patterns: + - "growth has stalled" + - "we hit a ceiling" + - "can't scale" + - "stuck at this level" + - "team can't keep up" + - "everything breaks when we grow" + - "we need to 10x but can't" + - "outgrew our processes" +routes_to: + diagnostics: + - growth-stall-diagnosis + - operational-chaos-diagnosis + skills: + - systems-thinking + - kaizen-bpr + - balanced-scorecard + playbooks: + - scaling-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Growth Hook + +## Trigger Patterns + +Growth stalls are felt viscerally before they are understood analytically. Founders describe the sensation in operational, emotional, and structural terms. + +- "Growth has stalled and I can't figure out why" +- "We hit a ceiling around $2M ARR and can't break through" +- "Can't scale past this point" +- "We're stuck at the same level we were six months ago" +- "The team can't keep up with demand" +- "Everything breaks when we try to grow" +- "We need to 10x but the business won't hold" +- "We outgrew our processes months ago" +- "Adding people isn't making us faster" +- "Our infrastructure can't handle more customers" +- "Growing is actually making things worse" +- "We plateaued and nothing we try changes it" +- "The org chart makes no sense anymore" +- "We're scaling chaos, not the business" +- "How do I get to the next stage?" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Stalled, plateau, stuck, same level | Growth plateau | High | +| Everything breaks, scaling chaos, infrastructure | Operational strain | High | +| Team can't keep up, adding people not helping | Organizational scaling failure | High | +| Need to 10x, next stage, break through ceiling | Stage transition challenge | Medium | +| Outgrew processes, org chart broken | Structural misfit | Medium | + +## Routing Logic + +**Growth plateau** -- Route to `growth-stall-diagnosis`. The root cause could be market saturation, product-market fit erosion, channel exhaustion, or pricing ceiling. The diagnostic teases these apart before selecting the right playbook. + +**Operational strain** -- Route to `operational-chaos-diagnosis`. When the infrastructure (technical, human, or process) cannot absorb growth, the problem is structural. If confirmed, escalate to `scaling-playbook` with a process-first orientation. The `kaizen-bpr` skill provides tactical process redesign. + +**Organizational scaling failure** -- Route to `growth-stall-diagnosis` with an organizational flag. Headcount growing faster than output is a classic symptom. The `systems-thinking` skill helps founders see the feedback loops that create this dynamic. + +**Stage transition challenge** -- Route to `scaling-playbook` directly when the entrepreneur articulates the gap between current and target state clearly. For vague articulations, start with `growth-stall-diagnosis`. + +**Structural misfit** -- Route to `operational-chaos-diagnosis`. Org charts, reporting lines, and process design that worked at one stage become liabilities at the next. + +## Disambiguation + +This hook borders `strategy-hook` when "growth stalled" actually means "we lost strategic direction." The distinguishing signal: if the entrepreneur knows what they want to achieve but cannot execute it, this hook applies. If they are uncertain about what to pursue, route to `strategy-hook`. Overlap with `team-hook` occurs when scaling failures manifest as people problems. If the entrepreneur leads with team frustration rather than growth metrics, defer to `team-hook`. + +## Example Conversations + +**Example 1: Revenue plateau** +Entrepreneur says: "We got to $1.5M ARR really fast, but we've been stuck here for eight months." +Hook classifies as: Growth plateau. +Routes to: `growth-stall-diagnosis` to determine whether the ceiling is market, product, channel, or pricing. + +**Example 2: Operational breaking point** +Entrepreneur says: "Every time we onboard a new batch of customers, something breaks. Support tickets spike, the team scrambles, and we lose half of them within a month." +Hook classifies as: Operational strain. +Routes to: `operational-chaos-diagnosis`, likely escalating to `scaling-playbook` and `kaizen-bpr`. + +**Example 3: Stage transition** +Entrepreneur says: "We're a 30-person company trying to operate like a 10-person startup. It's not working." +Hook classifies as: Structural misfit. +Routes to: `operational-chaos-diagnosis` to map the structural gaps, then `scaling-playbook` for the redesign. diff --git a/plugins/foreman/content/hooks/innovation-hook.md b/plugins/foreman/content/hooks/innovation-hook.md new file mode 100644 index 0000000..ddce3c9 --- /dev/null +++ b/plugins/foreman/content/hooks/innovation-hook.md @@ -0,0 +1,141 @@ +--- +name: "innovation-hook" +description: "Hook for innovation-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - No new ideas + - Everything feels stale + - Team plays it safe + - We're stuck in a rut + - Innovation dried up + - Same old approaches + - Need fresh thinking + - How do I get creative again? + - We're not experimenting enough + - Nobody takes risks anymore + - Our product hasn't evolved in months + - Competitors are out-innovating us + - Brainstorming sessions produce nothing useful +routes_to: + diagnostics: + - innovation-drought-diagnosis + playbooks: + - innovation-sprint-playbook + skills: + - creative-collaboration-and-context + - creative-identity-and-purpose + - creative-obstacles + - creative-practice-and-habit + - generating-solutions + - blue-ocean-strategy + - business-model-canvas + - disruptive-innovation + - doblin-ten-types + - enemies-of-clear-thinking +--- + +# Innovation Hook + +Creativity is not a personality trait that some teams possess and others lack. It is a condition — one that requires specific environmental inputs and degrades predictably when those inputs are removed. Risk aversion, process calcification, and the quiet tyranny of "what worked before" suffocate innovation more reliably than any external threat. The diagnosis matters because the remedies for a team that has never been creative differ fundamentally from those for a team that has forgotten how. + +## Trigger Patterns + +1. "No new ideas" +2. "Everything feels stale" +3. "Team plays it safe" +4. "We're stuck in a rut" +5. "Innovation dried up" +6. "Same old approaches" +7. "Need fresh thinking" +8. "How do I get creative again?" +9. "We're not experimenting enough" +10. "Nobody takes risks anymore" +11. "Our product hasn't evolved in months" +12. "Competitors are out-innovating us" +13. "Brainstorming sessions produce nothing useful" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Stale ideas, creative drought, repetitive thinking | `creativity-drought` | High | +| Risk aversion, safety-seeking, fear of failure | `risk-aversion` | High | +| Experimentation cited as insufficient or absent | `experimentation-gap` | Medium | +| Competitive innovation pressure, being outpaced | `competitive-innovation-lag` | High | +| Brainstorming or ideation process failing | `ideation-process-failure` | Medium | +| Personal creative block, founder feels stuck | `founder-creative-block` | Medium | + +## Routing Logic + +``` +IF intent == creativity-drought OR founder-creative-block: + → diagnostics/innovation-drought-diagnosis + → skills/creative/creative-identity-and-purpose.md + → skills/creative/creative-obstacles.md + → skills/decisions/generating-solutions + +IF intent == risk-aversion: + → diagnostics/innovation-drought-diagnosis + → skills/thinking/enemies-of-clear-thinking + → skills/creative/creative-practice-and-habit.md + → playbooks/innovation-sprint-playbook + +IF intent == experimentation-gap: + → diagnostics/innovation-drought-diagnosis + → playbooks/innovation-sprint-playbook + → skills/frameworks/business-model-canvas + → skills/frameworks/doblin-ten-types + +IF intent == competitive-innovation-lag: + → diagnostics/innovation-drought-diagnosis + → skills/frameworks/doblin-ten-types + → skills/frameworks/blue-ocean-strategy + → skills/frameworks/disruptive-innovation + +IF intent == ideation-process-failure: + → diagnostics/innovation-drought-diagnosis + → skills/decisions/generating-solutions + → skills/decisions/generating-solutions.md + → skills/creative/creative-collaboration-and-context.md +``` + +**Priority:** Medium + +## Disambiguation + +Innovation complaints overlap with several adjacent problem domains. Surface-level "we need new ideas" can conceal quite different root causes: + +- **Product hook overlap:** If the innovation concern is specifically about the product roadmap — features, retention, market fit — route to `product-hook`. Innovation framing is secondary to the product-specific diagnosis. +- **Strategy hook overlap:** "Stuck in a rut" may describe strategic drift rather than creative deficit. If the founder cannot articulate where the company is heading, route to `strategy-hook`. +- **Competition hook overlap:** When "competitors are out-innovating us" is the primary concern, the problem may be competitive intelligence rather than internal creativity. Route to `competition-hook` if the threat is external. +- **Culture hook overlap:** Risk aversion across the entire organisation often signals a culture problem — fear of punishment for failure — rather than an innovation process gap. Route to `culture-hook` if the aversion is systemic. +- **Leadership hook overlap:** A founder's personal creative block may stem from burnout or decision fatigue. Route to `leadership-hook` if the individual, not the team, is depleted. + +**Disambiguation prompt:** "Is this about your team not producing new ideas, the company not taking enough risks, or you personally feeling creatively stuck?" + +## Example Conversations + +**Example 1: Creativity drought** + +> **Founder:** "We used to have great ideas constantly. Now every brainstorm produces the same recycled concepts." +> +> **Foreman:** Recycled ideas are a symptom of recycled inputs. Creative output is directly proportional to the diversity of stimuli a team absorbs — and teams in execution mode progressively narrow their information diet. The fix is not a better brainstorming technique; it is deliberately re-expanding the input funnel. When was the last time your team encountered a genuinely unfamiliar perspective — a different industry, a different customer segment, a different discipline entirely? +> +> *Routes to: innovation-drought-diagnosis → creative-identity-and-permission → generating-solutions* + +**Example 2: Risk aversion** + +> **Founder:** "My team won't try anything new. Every proposal gets killed by 'what if it fails' objections." +> +> **Foreman:** Risk aversion in teams is almost never about the team's character — it is about the incentive structure. If failure is punished (even subtly) and safe execution is rewarded, rational people will choose safety every time. The question is not how to make your team braver but how to make experimentation cheaper and less career-threatening. What happened the last time someone on your team tried something that did not work? +> +> *Routes to: innovation-drought-diagnosis → enemies-of-clear-thinking → innovation-sprint-playbook* + +**Example 3: Ideation process failure** + +> **Founder:** "Brainstorming sessions are a waste of time. We sit in a room, people throw out random ideas, nothing sticks." +> +> **Foreman:** Traditional brainstorming has decades of research demonstrating its ineffectiveness — yet it persists as the default ideation ritual. The problem is structural: groupthink, anchoring to the first idea spoken, and social pressure suppress the divergent thinking brainstorming was meant to enable. There are better methods. Let me walk you through alternatives that actually produce usable output. +> +> *Routes to: innovation-drought-diagnosis → generating-solutions → brainswarming → collaboration-and-context* diff --git a/plugins/foreman/content/hooks/launch-hook.md b/plugins/foreman/content/hooks/launch-hook.md new file mode 100644 index 0000000..2e81526 --- /dev/null +++ b/plugins/foreman/content/hooks/launch-hook.md @@ -0,0 +1,146 @@ +--- +name: "launch-hook" +description: "Hook for launch-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Launching next month + - Entering a new market + - How do I launch? + - Going international + - New product launch + - Market entry strategy + - First launch ever + - Expanding to Europe/Asia + - GTM plan needed + - Go-to-market strategy + - Beta to general availability + - Launch timeline is slipping + - Don't know where to start with launch +routes_to: + diagnostics: + - market-entry-diagnosis + playbooks: + - first-100-customers-playbook + - international-expansion-playbook + - launch-playbook + skills: + - choosing-and-executing + - blue-ocean-strategy + - business-model-canvas + - growth-share-matrix + - net-promoter-score + - porters-five-forces + - first-mover-strategy + - stoic-right-action +--- + +# Launch Hook + +A launch is not an event. It is a campaign with a beginning, a middle, and — if done well — no end, only escalating momentum. Founders fixate on the announcement date while neglecting the months of positioning that precede it and the customer acquisition machinery that must outlast it. Whether entering a first market or a fifth, the failure modes are remarkably consistent: launching to nobody, launching everything at once, or launching before the value proposition can survive contact with real customers. + +## Trigger Patterns + +1. "Launching next month" +2. "Entering a new market" +3. "How do I launch?" +4. "Going international" +5. "New product launch" +6. "Market entry strategy" +7. "First launch ever" +8. "Expanding to Europe/Asia" +9. "GTM plan needed" +10. "Go-to-market strategy" +11. "Beta to general availability" +12. "Launch timeline is slipping" +13. "Don't know where to start with launch" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| First-time launch, debut product, general launch anxiety | `first-launch` | High | +| New market or geography, international expansion | `market-expansion` | High | +| GTM plan, go-to-market strategy requests | `gtm-strategy` | High | +| Launch timeline issues, slipping deadlines | `launch-execution` | Medium | +| Beta-to-GA transition, scaling from early users | `beta-transition` | Medium | +| New product line within existing company | `product-line-launch` | Medium | + +## Routing Logic + +``` +IF intent == first-launch: + → diagnostics/market-entry-diagnosis + → playbooks/launch-playbook + → playbooks/first-100-customers-playbook + → skills/frameworks/business-model-canvas + +IF intent == market-expansion: + → diagnostics/market-entry-diagnosis + → playbooks/international-expansion-playbook + → skills/frameworks/porters-five-forces + → skills/game-theory/first-mover-strategy + +IF intent == gtm-strategy: + → diagnostics/market-entry-diagnosis + → playbooks/launch-playbook + → skills/frameworks/business-model-canvas + → skills/frameworks/business-model-canvas.md + +IF intent == launch-execution: + → playbooks/launch-playbook + → skills/decisions/choosing-and-executing.md + → skills/stoic/stoic-right-action.md + +IF intent == beta-transition: + → diagnostics/market-entry-diagnosis + → playbooks/first-100-customers-playbook + → playbooks/first-100-customers-playbook.md + → skills/frameworks/net-promoter-score.md + +IF intent == product-line-launch: + → diagnostics/market-entry-diagnosis + → playbooks/launch-playbook + → skills/frameworks/growth-share-matrix.md + → skills/frameworks/blue-ocean-strategy +``` + +**Priority:** Medium + +## Disambiguation + +Launch-related language intersects with product, sales, strategy, and growth concerns. The distinction often lies in the company's stage and the specificity of the request: + +- **Product hook overlap:** If the founder is unsure whether the product is ready to launch — feature completeness, product-market fit concerns, retention issues — route to `product-hook`. The launch is premature until the product question is resolved. +- **Revenue hook overlap:** When "GTM plan" actually means "how do I sell this," and the product already exists in market, route to `revenue-and-sales-hook`. Launch implies market entry; sales implies market engagement. +- **Growth hook overlap:** Expansion that is about scaling existing operations (more of the same in more places) rather than entering a genuinely new market routes to `growth-hook`. +- **Strategy hook overlap:** "Entering a new market" may disguise a strategic direction question — the founder is not sure which market, not how to enter it. Route to `strategy-hook` if the target market is undefined. +- **Competition hook overlap:** Market entry into a heavily contested space may require competitive analysis before launch planning. Co-route with `competition-hook` when competitive density is the primary concern. + +**Disambiguation prompt:** "Are you launching a new product for the first time, expanding an existing product to a new market, or scaling something that is already working?" + +## Example Conversations + +**Example 1: First launch** + +> **Founder:** "We've been building for eight months and we're finally ready to launch. I have no idea where to start." +> +> **Foreman:** Eight months of building creates a dangerous attachment to features and a corresponding neglect of distribution. The product is ready; the question is whether your market is ready for it — meaning, do you have an audience primed to care on day one? A launch without a pre-built audience is a tree falling in an empty forest. Let me walk you through launch sequencing, starting with what should have begun two months ago and what you can still compress. +> +> *Routes to: market-entry-diagnosis → launch-playbook → first-100-customers-playbook* + +**Example 2: International expansion** + +> **Founder:** "We've saturated our home market. Looking at expanding to Europe but the regulatory landscape terrifies me." +> +> **Foreman:** Regulatory complexity is the visible barrier; the invisible ones — cultural adaptation, payment preferences, support expectations, local competition with home-field advantage — are often more lethal. European expansion is not one decision but twenty-seven, because the EU is not a market but a collection of markets with a shared trade agreement. Which specific countries are you considering, and what evidence do you have of demand there? +> +> *Routes to: market-entry-diagnosis → international-expansion-playbook → porters-five-forces* + +**Example 3: GTM strategy** + +> **Founder:** "We need a go-to-market strategy. Our product is great but we don't have a plan for getting it to customers." +> +> **Foreman:** A great product without a distribution strategy is a hobby, not a business. The GTM question has four components: who specifically you are selling to, how they currently solve the problem you address, where they congregate (physically and digitally), and what message will interrupt their current behaviour. Let me start with the first: describe your ideal first ten customers in enough detail that you could find them by name. +> +> *Routes to: market-entry-diagnosis → launch-playbook → business-model-canvas → value-proposition-canvas* diff --git a/plugins/foreman/content/hooks/leadership-hook.md b/plugins/foreman/content/hooks/leadership-hook.md new file mode 100644 index 0000000..a89a96f --- /dev/null +++ b/plugins/foreman/content/hooks/leadership-hook.md @@ -0,0 +1,95 @@ +--- +name: "leadership-hook" +description: "Captures intent related to personal leadership struggles, founder burnout, impostor syndrome, isolation, delegation failure, and identity crises" +trigger_patterns: + - "I feel like a fraud" + - "burning out" + - "can't keep up" + - "I'm so isolated" + - "don't know what I'm doing" + - "losing confidence" + - "should I even be CEO?" + - "I'm the bottleneck" + - "can't delegate" +routes_to: + diagnostics: + - leadership-crisis-diagnosis + skills: + - leader-resilience-and-wellbeing + - delegation-and-empowerment + - emotional-courage + - leader-self-reflection + - senior-leadership-transition + playbooks: + - founder-transition-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Leadership Hook + +## Trigger Patterns + +Leadership distress is the most intimate category of founder communication. It surfaces as self-doubt, exhaustion, identity questioning, and a particular loneliness that comes from having no peers inside the organization. + +- "I feel like a fraud and everyone's going to find out" +- "I'm burning out -- I can't sustain this pace" +- "I can't keep up with everything that's expected of me" +- "I'm so isolated -- nobody understands what this is like" +- "I honestly don't know what I'm doing anymore" +- "I'm losing confidence in my own decisions" +- "Should I even be the CEO? Maybe someone else should lead" +- "I'm the bottleneck for every decision in this company" +- "I can't delegate -- nobody does it right" +- "I haven't taken a day off in eight months" +- "I'm making decisions I'm not qualified to make" +- "The job outgrew me" +- "Everyone depends on me and I'm cracking" +- "I used to love this and now I dread it" +- "I don't know who to talk to about any of this" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Fraud, losing confidence, not qualified | Impostor syndrome | High | +| Burning out, can't sustain, no day off, dread it | Founder burnout | High | +| Isolated, nobody understands, who to talk to | Leadership isolation | High | +| Bottleneck, can't delegate, nobody does it right | Control and delegation failure | High | +| Should I be CEO, job outgrew me | Role-identity crisis | Medium | +| Don't know what I'm doing, cracking | Overwhelm | Medium | + +## Routing Logic + +**Impostor syndrome** -- Route to `leadership-crisis-diagnosis`. Impostor syndrome in founders is frequently rational -- the role genuinely expands beyond prior experience. The diagnostic separates skill gaps (addressable) from psychological spirals (different intervention). The `emotional-courage` and `leader-self-reflection` skills provide grounding frameworks. + +**Founder burnout** -- Route to `leadership-crisis-diagnosis` with urgency. Burnout impairs every decision the founder makes, which means every other business problem becomes worse. The `leader-resilience-and-wellbeing` skill provides the recovery framework. Structural causes (over-centralized authority, no delegation) route to `delegation-and-empowerment`. + +**Leadership isolation** -- Route to `leadership-crisis-diagnosis`. Isolation is both a symptom and a cause. The diagnostic determines whether the founder needs peer networks, advisory structures, or internal trust-building. + +**Control and delegation failure** -- Route to `leadership-crisis-diagnosis`, then to the `delegation-and-empowerment` skill. Founders who cannot delegate face a hard ceiling. If the delegation failure connects to a broader organizational redesign, the `founder-transition-playbook` applies. + +**Role-identity crisis** -- Route to `leadership-crisis-diagnosis`. "Should I be CEO?" is a question that deserves serious inquiry, not automatic reassurance. The `senior-leadership-transition` skill addresses the mechanics of role evolution. If the answer is genuinely "step aside," the `founder-transition-playbook` provides the path. + +**Overwhelm** -- Route to `leadership-crisis-diagnosis`. Overwhelm is the broadest signal and requires the diagnostic to decompose it into addressable components. + +## Disambiguation + +This hook overlaps with `team-hook` when leadership frustration manifests as team complaints. The distinguishing signal: if the founder says "the team isn't performing," route to `team-hook`. If the founder says "I can't lead this team," route here. Overlap with `strategy-hook` occurs when "I don't know what I'm doing" reflects strategic confusion rather than personal crisis. If the uncertainty is about business direction, defer to `strategy-hook`. If the uncertainty is about personal capacity, this hook applies. + +## Example Conversations + +**Example 1: Burnout** +Entrepreneur says: "I'm working 80-hour weeks, I haven't seen my family in months, and I'm starting to make mistakes I never would have made a year ago." +Hook classifies as: Founder burnout. +Routes to: `leadership-crisis-diagnosis` with urgency, likely surfacing `leader-resilience-and-wellbeing` and structural delegation needs. + +**Example 2: Delegation failure** +Entrepreneur says: "I hired a VP of Engineering to take things off my plate, but I keep jumping in because the quality drops when I step back." +Hook classifies as: Control and delegation failure. +Routes to: `leadership-crisis-diagnosis`, then `delegation-and-empowerment` to build a sustainable handoff framework. + +**Example 3: Identity crisis** +Entrepreneur says: "The company needs a real CEO now -- someone with experience running a 200-person org. That's not me." +Hook classifies as: Role-identity crisis. +Routes to: `leadership-crisis-diagnosis` to determine whether this is growth-driven impostor syndrome or a genuine transition point, with `senior-leadership-transition` on standby. diff --git a/plugins/foreman/content/hooks/negotiation-hook.md b/plugins/foreman/content/hooks/negotiation-hook.md new file mode 100644 index 0000000..9228457 --- /dev/null +++ b/plugins/foreman/content/hooks/negotiation-hook.md @@ -0,0 +1,131 @@ +--- +name: "negotiation-hook" +description: "Hook for negotiation-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Deal is stuck + - Can't agree on terms + - They won't budge + - Getting a bad deal + - How do I negotiate this? + - Term sheet makes no sense + - Partner wants too much + - Contract negotiation + - They're playing hardball + - I keep giving in + - Vendor is squeezing us + - Salary negotiation with a key hire + - Licensing terms are unfair +routes_to: + diagnostics: + - negotiation-stuck-diagnosis + templates: + - negotiation-prep-sheet + playbooks: + - negotiation-playbook + skills: + - prisoners-dilemma-and-cooperation + - competitive-negotiation + - cooperative-negotiation + - delivering-the-deal +--- + +# Negotiation Hook + +Negotiations fail for predictable reasons, yet founders persist in treating each stalled deal as a unique crisis. The patterns repeat: anchoring too early, conceding too fast, confusing positions with interests, or mistaking aggression for leverage. Recognising which pattern is at play determines whether the conversation needs competitive tactics, cooperative reframing, or simply better preparation. + +## Trigger Patterns + +1. "Deal is stuck" +2. "Can't agree on terms" +3. "They won't budge" +4. "Getting a bad deal" +5. "How do I negotiate this?" +6. "Term sheet makes no sense" +7. "Partner wants too much" +8. "Contract negotiation" +9. "They're playing hardball" +10. "I keep giving in" +11. "Vendor is squeezing us" +12. "Salary negotiation with a key hire" +13. "Licensing terms are unfair" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Deal described as stalled, stuck, or going nowhere | `negotiation-deadlock` | High | +| Feeling exploited, outmatched, or losing ground | `weak-position-negotiation` | High | +| Term sheet confusion, clause-specific complaints | `term-comprehension` | Medium | +| Partner or vendor demanding disproportionate terms | `power-asymmetry` | High | +| General "how do I negotiate" without specifics | `negotiation-skill-gap` | Medium | +| Repeated concessions, pattern of giving in | `concession-pattern` | High | + +## Routing Logic + +``` +IF intent == negotiation-deadlock: + → diagnostics/negotiation-stuck-diagnosis + → skills/negotiation/cooperative-negotiation + → skills/negotiation/delivering-the-deal.md + +IF intent == weak-position-negotiation OR power-asymmetry: + → diagnostics/negotiation-stuck-diagnosis + → skills/negotiation/competitive-negotiation + → skills/game-theory/prisoners-dilemma-and-cooperation.md + +IF intent == term-comprehension: + → output-templates/self/negotiation-prep-sheet.md + → playbooks/negotiation-playbook + +IF intent == negotiation-skill-gap: + → diagnostics/negotiation-stuck-diagnosis + → playbooks/negotiation-playbook + → skills/negotiation/competitive-negotiation + → skills/negotiation/cooperative-negotiation + +IF intent == concession-pattern: + → diagnostics/negotiation-stuck-diagnosis + → skills/negotiation/cooperative-negotiation.md + → skills/negotiation/competitive-negotiation +``` + +**Priority:** Medium + +## Disambiguation + +Negotiation language surfaces across multiple domains. Precise routing requires distinguishing the negotiation context: + +- **Fundraising hook overlap:** If the negotiation involves investor term sheets, valuation disputes, or equity allocation with VCs, route to `fundraising-hook` as primary. Negotiation skills become secondary support. +- **Partnership hook overlap:** When the counterparty is a cofounder, strategic partner, or acquisition target, route to `partnership-hook` first — the relationship dimension outweighs pure negotiation tactics. +- **Team hook overlap:** Salary negotiations, equity grants for employees, or compensation disputes belong to `team-hook` with negotiation skills as supplementary. +- **Revenue hook overlap:** If the negotiation is a sales deal or pricing discussion with a customer, route to `revenue-and-sales-hook`. + +**Disambiguation prompt:** "Who is on the other side of this negotiation — an investor, a partner, a customer, an employee, or a vendor?" + +## Example Conversations + +**Example 1: Deadlocked deal** + +> **Founder:** "We've been going back and forth on this partnership deal for three months. Neither side will move." +> +> **Foreman:** Three months of positional stalemate usually means both parties are negotiating terms when they should be negotiating interests. The positions are incompatible; the underlying needs may not be. First question: what does the other side actually need from this deal — not what they are asking for, but what outcome they require? +> +> *Routes to: negotiation-stuck-diagnosis → cooperative-negotiation → resolution-roadmap* + +**Example 2: Power asymmetry** + +> **Founder:** "Our biggest client is renegotiating the contract and basically threatening to leave if we don't cut our price by 30%." +> +> **Foreman:** A client who represents outsized revenue knows they hold leverage — and they are using it. The question is whether you have alternatives they do not know about, or whether the dependency is as absolute as it feels. Before we talk tactics: what percentage of your revenue does this client represent, and how quickly could you replace them? +> +> *Routes to: negotiation-stuck-diagnosis → competitive-negotiation → credible-commitment* + +**Example 3: Skill gap** + +> **Founder:** "I'm terrible at negotiating. I always end up agreeing to terms I regret." +> +> **Foreman:** Consistent regret after negotiations signals a preparation problem, not a personality flaw. Most founders who describe themselves as poor negotiators have simply never been taught the mechanics — anchoring, concession strategy, BATNA development. The good news: negotiation is a learnable skill with high return on modest investment. Let me walk you through a structured approach. +> +> *Routes to: negotiation-stuck-diagnosis → negotiation-playbook → competitive-negotiation + cooperative-negotiation* diff --git a/plugins/foreman/content/hooks/partnership-hook.md b/plugins/foreman/content/hooks/partnership-hook.md new file mode 100644 index 0000000..e121c4e --- /dev/null +++ b/plugins/foreman/content/hooks/partnership-hook.md @@ -0,0 +1,141 @@ +--- +name: "partnership-hook" +description: "Hook for partnership-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Got a partnership offer + - Cofounder problems + - Should we merge? + - Strategic alliance opportunity + - Partner isn't delivering + - Equity split fight + - Joint venture? + - Acquisition offer came in + - My cofounder wants out + - Thinking about bringing on a cofounder + - Our partner is competing with us + - How do I structure this deal? + - Vesting schedule dispute +routes_to: + diagnostics: + - cofounder-conflict-diagnosis + - partnership-diagnosis + templates: + - unit-economics-snapshot + - personal-board-tracker + playbooks: + - acquisition-evaluation-playbook + - partnership-playbook + skills: + - swot-pest-analysis + - coalition-and-partnership-games + - information-asymmetry + - cooperative-negotiation + - delivering-the-deal + - resolving-people-conflict +--- + +# Partnership Hook + +Partnerships are the business equivalent of marriage — entered with optimism, sustained by structure, and destroyed by unexpressed expectations. The founder who says "we have a partnership opportunity" and the founder who says "my cofounder wants out" are experiencing different stages of the same lifecycle. Both require frameworks that account for the volatile intersection of economics, emotion, and power. + +## Trigger Patterns + +1. "Got a partnership offer" +2. "Cofounder problems" +3. "Should we merge?" +4. "Strategic alliance opportunity" +5. "Partner isn't delivering" +6. "Equity split fight" +7. "Joint venture?" +8. "Acquisition offer came in" +9. "My cofounder wants out" +10. "Thinking about bringing on a cofounder" +11. "Our partner is competing with us" +12. "How do I structure this deal?" +13. "Vesting schedule dispute" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Cofounder conflict, equity fights, departures | `cofounder-conflict` | High | +| New partnership or alliance evaluation | `partnership-evaluation` | High | +| Merger or acquisition offer received | `ma-evaluation` | High | +| Joint venture structuring questions | `jv-structuring` | Medium | +| Existing partnership underperforming or toxic | `partnership-breakdown` | High | +| Adding a cofounder or partner to existing company | `partner-addition` | Medium | + +## Routing Logic + +``` +IF intent == cofounder-conflict: + → diagnostics/cofounder-conflict-diagnosis + → skills/negotiation/cooperative-negotiation + → skills/people/resolving-people-conflict.md + → skills/game-theory/coalition-and-partnership-games + +IF intent == partnership-evaluation OR jv-structuring: + → diagnostics/partnership-diagnosis + → playbooks/partnership-playbook + → skills/game-theory/coalition-and-partnership-games + → skills/frameworks/swot-pest-analysis.md + +IF intent == ma-evaluation: + → diagnostics/partnership-diagnosis + → playbooks/acquisition-evaluation-playbook + → output-templates/investor/unit-economics-snapshot.md + → skills/game-theory/information-asymmetry + +IF intent == partnership-breakdown: + → diagnostics/partnership-diagnosis + → skills/negotiation/delivering-the-deal.md + → skills/people/resolving-people-conflict.md + → skills/game-theory/coalition-and-partnership-games + +IF intent == partner-addition: + → diagnostics/partnership-diagnosis + → playbooks/partnership-playbook + → skills/game-theory/coalition-and-partnership-games.md + → output-templates/self/personal-board-tracker.md +``` + +**Priority:** Medium + +## Disambiguation + +Partnership issues sit at the intersection of negotiation, team dynamics, strategy, and finance. Proper routing depends on identifying the dominant dimension: + +- **Negotiation hook overlap:** If the core issue is a specific deal being negotiated — terms, pricing, structure — and the relationship itself is healthy, route to `negotiation-hook`. Partnership framing applies only when the relationship dimension is material. +- **Team hook overlap:** Cofounder conflicts that are fundamentally about roles, responsibilities, or management style (rather than equity, exit, or strategic direction) may route better through `team-hook`. +- **Fundraising hook overlap:** If the "partner" is an investor and the dispute involves board seats, liquidation preferences, or governance, route to `fundraising-hook`. +- **Strategy hook overlap:** "Should we merge?" may be a strategic direction question rather than a partnership mechanics question. If the founder is unsure about the company's future trajectory, route to `strategy-hook` first. + +**Disambiguation prompt:** "Is this about evaluating a new relationship, fixing a broken one, or ending one that is not working?" + +## Example Conversations + +**Example 1: Cofounder conflict** + +> **Founder:** "My cofounder and I can't agree on anything anymore. We're fighting about equity, about direction, about who does what." +> +> **Foreman:** Multi-dimensional cofounder conflict — equity, strategy, and roles simultaneously — signals that the founding relationship has outgrown its original terms. These were likely set on a handshake when the stakes were theoretical. Now that the company has value, the ambiguity is unbearable. The first question is not how to resolve the disagreements but whether both of you still want the same company. +> +> *Routes to: cofounder-conflict-diagnosis → cooperative-negotiation → conflict-resolution* + +**Example 2: Acquisition offer** + +> **Founder:** "A larger company offered to acquire us. The number sounds good but I don't know if I should take it." +> +> **Foreman:** An acquisition offer flatters the ego and clouds the judgement in equal measure. The "number sounds good" reaction is precisely the wrong starting point — the question is good relative to what. Your future projected value, your alternatives, your personal goals, your team's outcome, the tax implications. Before we evaluate the offer: what would you build if you said no, and does that excite you more than the number? +> +> *Routes to: partnership-diagnosis → acquisition-evaluation-playbook → information-asymmetry* + +**Example 3: Partnership evaluation** + +> **Founder:** "A Fortune 500 company wants to partner with us. It could be huge but I'm worried about getting swallowed." +> +> **Foreman:** Asymmetric partnerships — where one party is orders of magnitude larger — follow predictable dynamics. The small company provides innovation and speed; the large company provides distribution and credibility. The risk is dependency: if 80% of your revenue flows through this partner within two years, you have not gained a partner but acquired a boss. What specifically does the partnership proposal entail, and what exclusivity terms are on the table? +> +> *Routes to: partnership-diagnosis → partnership-playbook → coalition-and-partnership-games* diff --git a/plugins/foreman/content/hooks/personal-growth-hook.md b/plugins/foreman/content/hooks/personal-growth-hook.md new file mode 100644 index 0000000..fe51b91 --- /dev/null +++ b/plugins/foreman/content/hooks/personal-growth-hook.md @@ -0,0 +1,153 @@ +--- +name: "personal-growth-hook" +description: "Hook for personal-growth-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - Want to be a better leader + - Need a mentor + - How do I grow? + - Skill gaps + - Career feels stuck + - Building my personal brand + - Want to learn more + - Investing in myself + - Need to develop my team + - Executive coaching + - Outgrowing my own abilities + - Not sure I'm the right CEO anymore + - How do other founders handle this? + - Want to build my network +routes_to: + templates: + - personal-board-tracker + playbooks: + - founder-transition-playbook + - personal-brand-playbook + skills: + - tuckman-team-stages + - career-strategy-for-leaders + - leader-self-reflection + - learning-agility + - mentoring-and-coaching + - storytelling-for-leaders + - meeting-the-right-people + - teaching-and-leading + - stoic-emotional-mastery + - stoic-right-action + - stoic-self-awareness + - reader-psychology +--- + +# Personal Growth Hook + +The founder who asks "how do I become a better leader" has already crossed the most important threshold — the recognition that the company's ceiling is set by the founder's own capabilities. This is a rare and valuable moment of self-awareness in a role that systematically selects for overconfidence. The challenge is converting that awareness into a structured development path rather than letting it curdle into impostor syndrome or scatter across a dozen half-read business books. + +## Trigger Patterns + +1. "Want to be a better leader" +2. "Need a mentor" +3. "How do I grow?" +4. "Skill gaps" +5. "Career feels stuck" +6. "Building my personal brand" +7. "Want to learn more" +8. "Investing in myself" +9. "Need to develop my team" +10. "Executive coaching" +11. "Outgrowing my own abilities" +12. "Not sure I'm the right CEO anymore" +13. "How do other founders handle this?" +14. "Want to build my network" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Leadership improvement, self-development requests | `leadership-development` | High | +| Mentor or coach seeking, advisory relationships | `mentorship-seeking` | High | +| Skill gap awareness, specific capability deficits | `skill-gap-remediation` | Medium | +| Career stagnation, feeling stuck or plateaued | `career-plateau` | Medium | +| Personal brand, public profile, thought leadership | `personal-brand` | Medium | +| Team development, growing others' capabilities | `team-development` | Medium | +| Self-doubt about fitness for the role | `role-fitness-doubt` | High | + +## Routing Logic + +``` +IF intent == leadership-development: + → skills/leadership/leader-self-reflection + → skills/leadership/learning-agility.md + → skills/leadership/career-strategy-for-leaders + → skills/stoic/stoic-right-action.md + +IF intent == mentorship-seeking: + → skills/leadership/mentoring-and-coaching + → output-templates/self/personal-board-tracker.md + → skills/people/meeting-the-right-people.md + +IF intent == skill-gap-remediation: + → skills/leadership/leader-self-reflection + → skills/leadership/learning-agility.md + → skills/stoic/stoic-self-awareness.md + +IF intent == career-plateau: + → skills/leadership/career-strategy-for-leaders + → skills/leadership/leader-self-reflection.md + → playbooks/founder-transition-playbook + +IF intent == personal-brand: + → playbooks/personal-brand-playbook + → skills/leadership/storytelling-for-leaders.md + → skills/writing/reader-psychology + +IF intent == team-development: + → skills/leadership/mentoring-and-coaching + → skills/people/teaching-and-leading + → skills/frameworks/tuckman-team-stages.md + +IF intent == role-fitness-doubt: + → skills/leadership/leader-self-reflection + → skills/stoic/stoic-emotional-mastery.md + → playbooks/founder-transition-playbook + → skills/stoic/stoic-self-awareness.md +``` + +**Priority:** Low + +## Disambiguation + +Personal growth is the broadest hook in the system — nearly any founder concern, taken to its root, becomes a personal development question. The routing priority is deliberately low to prevent this hook from absorbing problems that have more specific, actionable entry points: + +- **Leadership hook overlap:** If the founder describes burnout, isolation, impostor syndrome, or emotional exhaustion, route to `leadership-hook`. Personal growth presumes energy and capacity; leadership hook addresses their absence. +- **Team hook overlap:** "Need to develop my team" may indicate a team capability problem (hiring, training, structure) rather than the founder's own development journey. If the concern is about the team's performance rather than the founder's growth, route to `team-hook`. +- **Strategy hook overlap:** "Career feels stuck" in a founder context often means the company feels stuck. If probing reveals strategic uncertainty rather than personal development needs, route to `strategy-hook`. +- **Communication hook overlap:** Specific skill requests — better writing, better presentations, better public speaking — route to `communication-hook` for targeted skill development rather than the broader personal growth pathway. + +**Disambiguation prompt:** "Are you looking to develop yourself as a leader, build specific skills for a current challenge, or figure out what your next chapter looks like?" + +## Example Conversations + +**Example 1: Leadership development** + +> **Founder:** "I want to be a better leader but I don't know where to start. There's so much advice out there." +> +> **Foreman:** The abundance of leadership advice is itself the problem — it creates the illusion that leadership development is about consuming content rather than changing behaviour. Effective development starts with an honest audit of your current capabilities and their fit to your company's current needs, not with generic prescriptions. A Series A CEO needs different skills than a pre-seed founder. What stage is your company at, and what specific situation made you realise you needed to grow? +> +> *Routes to: leader-self-reflection → learning-agility → career-strategy-for-leaders* + +**Example 2: Mentorship seeking** + +> **Founder:** "I need a mentor. I'm making decisions in the dark and I don't have anyone to bounce ideas off." +> +> **Foreman:** The desire for a mentor is sound; the approach most founders take to finding one is not. Cold-emailing successful CEOs asking them to "be your mentor" has a near-zero success rate and misunderstands how mentorship actually forms. The most productive advisory relationships emerge from specific, bounded requests — not open-ended commitments. Who in your network or industry do you already have a transactional relationship with, even a thin one? +> +> *Routes to: mentoring-and-coaching → advisory-board → networking* + +**Example 3: Role fitness doubt** + +> **Founder:** "Honestly, I'm not sure I'm the right person to be CEO anymore. The company has outgrown me." +> +> **Foreman:** That statement takes more courage than most board presentations. The question deserves honest examination rather than reflexive reassurance. Sometimes founders are right — the skills that built the company are not the skills that scale it. Other times, the feeling reflects a temporary gap that structured development can close. The distinction matters enormously. What specifically makes you feel outgrown — is it a skill you lack, a responsibility you dread, or a version of the job you no longer recognise? +> +> *Routes to: leader-self-reflection → managing-emotions → founder-transition-playbook → self-knowledge* diff --git a/plugins/foreman/content/hooks/product-hook.md b/plugins/foreman/content/hooks/product-hook.md new file mode 100644 index 0000000..568a2ef --- /dev/null +++ b/plugins/foreman/content/hooks/product-hook.md @@ -0,0 +1,94 @@ +--- +name: "product-hook" +description: "Captures intent related to product-market fit uncertainty, user retention problems, product quality concerns, feature prioritization, and value delivery gaps" +trigger_patterns: + - "product isn't resonating" + - "users don't stick" + - "low retention" + - "nobody loves it" + - "features aren't working" + - "don't know what to build next" + - "customers use it but don't pay" + - "PMF feels far away" + - "NPS is terrible" +routes_to: + diagnostics: + - product-market-fit-diagnosis + skills: + - net-promoter-score + - business-model-canvas + - disruptive-innovation + - product-life-cycle + playbooks: + - product-market-fit-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Product Hook + +## Trigger Patterns + +Product-market fit problems are uniquely corrosive because they undermine everything else. Founders describe them through user behavior observations, metric anxiety, and a nagging sense that something fundamental is off. + +- "The product isn't resonating with anyone" +- "Users sign up but don't stick around" +- "Our retention numbers are awful" +- "Nobody seems to love this product" +- "We shipped the features they asked for and nothing changed" +- "I don't know what to build next" +- "Customers use the free version but won't pay" +- "Product-market fit feels like it's getting further away, not closer" +- "Our NPS is terrible" +- "Users say it's 'nice' but they don't need it" +- "We keep building features but engagement stays flat" +- "People sign up, poke around, and disappear" +- "I can't tell if the product is wrong or the market is wrong" +- "Feedback is all over the place -- everyone wants something different" +- "We have usage but no passion" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Not resonating, nobody loves it, nice but don't need it | Value proposition gap | High | +| Users don't stick, low retention, sign up and disappear | Retention failure | High | +| Don't know what to build, everyone wants something different | Feature direction confusion | High | +| Use it but don't pay, free version only | Monetization disconnect | Medium | +| PMF feels far, product or market wrong | Product-market fit absence | High | +| NPS terrible, usage but no passion | Weak product sentiment | Medium | + +## Routing Logic + +**Value proposition gap** -- Route to `product-market-fit-diagnosis`. When users acknowledge the product but do not need it, the gap is between what the product offers and what the market values. The `business-model-canvas` skill helps reframe the value proposition. The `disruptive-innovation` skill reveals whether the product is overshooting or undershooting market needs. + +**Retention failure** -- Route to `product-market-fit-diagnosis` with a retention focus. Low retention is the clearest signal that product-market fit is absent or fragile. The `net-promoter-score` skill provides a measurement framework. If the diagnostic confirms PMF weakness, escalate to `product-market-fit-playbook`. + +**Feature direction confusion** -- Route to `product-market-fit-diagnosis`. Scattered feedback and unclear build priorities usually indicate the founder has not identified the core user segment. The diagnostic narrows the segment before the playbook addresses feature strategy. + +**Monetization disconnect** -- Route to `product-market-fit-diagnosis`. Free usage without payment signals one of three things: the product solves a real problem poorly, the product solves a trivial problem well, or the pricing model is wrong. The diagnostic differentiates these. + +**Product-market fit absence** -- Route to `product-market-fit-playbook` if the founder has already done substantial self-diagnosis. Otherwise, start with `product-market-fit-diagnosis`. The playbook chains multiple frameworks for a systematic PMF pursuit. + +**Weak product sentiment** -- Route to `product-market-fit-diagnosis`. The `net-promoter-score` skill quantifies sentiment and identifies promoter versus detractor patterns. + +## Disambiguation + +This hook overlaps with `revenue-and-sales-hook` when "customers won't pay" stems from sales execution rather than product gaps. The distinguishing signal: if customers do not see value, this hook applies. If customers see value but balk at price, route to `revenue-and-sales-hook`. Overlap with `strategy-hook` occurs when "I don't know what to build" reflects strategic confusion rather than product confusion. If the uncertainty extends beyond product to the entire business direction, defer to `strategy-hook`. Overlap with `growth-hook` emerges when retention problems cap growth. If the founder frames the problem as "we can't grow," route to `growth-hook` and let it discover the product root cause through its diagnostic. + +## Example Conversations + +**Example 1: Retention cliff** +Entrepreneur says: "We get decent signups -- about 200 a week -- but 90% are gone within two weeks. The ones who stay seem to like it." +Hook classifies as: Retention failure. +Routes to: `product-market-fit-diagnosis` to understand the gap between the 10% who stay and the 90% who leave, with `net-promoter-score` for structured feedback. + +**Example 2: Feature confusion** +Entrepreneur says: "Every customer interview gives me a different answer about what they want. I've been building features for six months and none of them moved the needle." +Hook classifies as: Feature direction confusion. +Routes to: `product-market-fit-diagnosis` to identify the core segment, then `product-market-fit-playbook` for a structured approach to feature-market alignment. + +**Example 3: Monetization wall** +Entrepreneur says: "We have 5,000 active users on the free plan. Twelve have upgraded to paid. The product works -- they just won't pay for it." +Hook classifies as: Monetization disconnect. +Routes to: `product-market-fit-diagnosis` to determine whether the value gap is real or the pricing model is misaligned with how users perceive the product's worth. diff --git a/plugins/foreman/content/hooks/research-hook.md b/plugins/foreman/content/hooks/research-hook.md new file mode 100644 index 0000000..d24e9b0 --- /dev/null +++ b/plugins/foreman/content/hooks/research-hook.md @@ -0,0 +1,161 @@ +--- +name: "research-hook" +description: "Hook for research-hook intent classification and routing" +priority: "medium" +author: "Fatih Guner" +trigger_patterns: + - I need data + - Where do I find information about my market? + - How do I research my competitors? + - I don't have the numbers + - Need to validate my assumptions + - How do I size my market? + - Need competitive intelligence + - How to interview customers + - I need to do due diligence + - Don't know where to start with research + - How much should I charge -- I need pricing data + - Need to understand the regulatory landscape + - How do I find out what customers actually want? + - I'm guessing at these numbers + - Where do I get benchmarks for my industry? +routes_to: + research: + - brand-perception-research + - churn-analysis-guide + - competitor-research-template + - content-strategy-research + - customer-interview-guide + - data-collection-plan + - due-diligence-research + - financial-modeling-guide + - funding-landscape-research + - industry-mapping-guide + - market-sizing-worksheet + - partnership-research-guide + - pricing-research-guide + - regulatory-landscape-research + - survey-design-guide + - talent-market-research + - technology-stack-research + - user-testing-protocol +--- + +# Research Hook + +Entrepreneurs frequently arrive at a framework knowing they need data they do not have. The instinct is to guess, to substitute opinion for evidence, or to skip the analysis entirely. None of these produces good decisions. This hook intercepts research-related intent and routes to the structured research guides in `.claude/research/`, which teach entrepreneurs how to gather the specific data that skills, diagnostics, and playbooks require as input. + +## Trigger Patterns + +1. "I need data" +2. "Where do I find information about my market?" +3. "How do I research my competitors?" +4. "I don't have the numbers" +5. "Need to validate my assumptions" +6. "How do I size my market?" +7. "Need competitive intelligence" +8. "How to interview customers" +9. "I need to do due diligence" +10. "Don't know where to start with research" +11. "How much should I charge -- I need pricing data" +12. "Need to understand the regulatory landscape" +13. "How do I find out what customers actually want?" +14. "I'm guessing at these numbers" +15. "Where do I get benchmarks for my industry?" + +## Intent Classification + +| Signal | Intent | Confidence | +|--------|--------|------------| +| Market size, TAM/SAM/SOM, market opportunity | `market-research` | High | +| Competitor analysis, competitive landscape, competitive intelligence | `competitor-research` | High | +| Customer interviews, surveys, churn reasons, user testing | `customer-research` | High | +| Financial models, unit economics, pricing data, willingness-to-pay | `financial-research` | High | +| Technology choices, stack evaluation, build vs. buy | `technical-research` | Medium | +| Regulations, compliance, legal landscape | `regulatory-research` | Medium | +| Due diligence, partner vetting, acquisition research | `due-diligence` | Medium | +| Hiring benchmarks, salary data, talent availability | `talent-research` | Medium | +| Content strategy, audience research, channel analysis | `content-research` | Medium | +| Brand perception, NPS, reputation | `brand-research` | Medium | + +## Routing Logic + +``` +IF intent == market-research: + --> /research market-sizing-worksheet + --> /research industry-mapping-guide + +IF intent == competitor-research: + --> /research competitor-research-template + +IF intent == customer-research: + --> /research customer-interview-guide + --> /research survey-design (if quantitative emphasis) + --> /research churn-analysis (if retention context) + --> /research user-testing-protocol (if product testing context) + +IF intent == financial-research: + --> /research financial-modeling + --> /research pricing-research-guide + --> /research funding-landscape (if capital-seeking context) + +IF intent == technical-research: + --> /research technology-stack + +IF intent == regulatory-research: + --> /research regulatory-landscape + +IF intent == due-diligence: + --> /research due-diligence-research + +IF intent == talent-research: + --> /research talent-market-research + +IF intent == content-research: + --> /research content-strategy-research + +IF intent == brand-research: + --> /research brand-perception-research +``` + +**Priority:** Medium + +## Disambiguation + +The research hook intercepts the need for data, not the need for analysis. Once the entrepreneur has the data, the system routes to skills and diagnostics that use it. + +| Overlapping Hook | Overlap Condition | Resolution | +|-----------------|-------------------|------------| +| `revenue-and-sales-hook` | Entrepreneur mentions pricing but lacks data to analyse | Research hook takes priority -- gather data first, then apply pricing frameworks | +| `competition-hook` | Entrepreneur asks about competitors but has no competitive intelligence | Research hook takes priority -- run `/research competitor-research-template` before applying Porter's Five Forces | +| `product-hook` | Entrepreneur wants to validate a feature but has no user data | Research hook takes priority -- run `/research user-testing-protocol` or `/research customer-interview-guide` before product decisions | +| `strategy-hook` | Entrepreneur needs strategic direction but lacks market data | Research hook takes priority -- market sizing and industry mapping precede strategy frameworks | +| `decision-hook` | Entrepreneur cites "not enough information" as the blocker | Shared routing -- decision hook addresses the paralysis pattern, research hook addresses the actual information gap. Both may fire. | + +**Disambiguation prompt:** "Are you looking for a framework to analyse data you already have, or do you need guidance on how to gather the data in the first place?" + +## Example Conversations + +**Example 1: Market sizing need** + +> **Founder:** "I keep hearing I need to know my TAM but I have no idea how to calculate it or where to get the numbers." +> +> **Foreman:** Calculating TAM without a method produces a number that impresses no one and informs nothing. The market-sizing worksheet walks you through a bottom-up approach using data you can actually find -- census data, industry reports, proxy metrics from adjacent markets. It takes two to four hours and produces a defensible number rather than a hopeful one. +> +> *Routes to: `/research market-sizing-worksheet`* + +**Example 2: Customer research gap** + +> **Founder:** "We think customers are churning because of price, but honestly we haven't asked them." +> +> **Foreman:** Assuming the reason for churn is the most expensive form of guessing in business. The customer interview guide gives you a structured protocol -- whom to contact, what to ask, how to interpret evasive answers -- that surfaces the actual reason in five to ten conversations. The churn analysis guide complements it with quantitative methods if you have usage data. +> +> *Routes to: `/research customer-interview-guide`, `/research churn-analysis`* + +**Example 3: Competitive intelligence** + +> **Founder:** "We're about to enter a new market and I need to understand who's already there and how they're positioned." +> +> **Foreman:** Entering a market without a competitor map is navigating without a chart. The competitor research template structures your intelligence gathering: direct competitors, adjacent threats, their pricing, positioning, and vulnerable flanks. Pair it with the industry mapping guide for the broader landscape. +> +> *Routes to: `/research competitor-research-template`, `/research industry-mapping-guide`* diff --git a/plugins/foreman/content/hooks/revenue-and-sales-hook.md b/plugins/foreman/content/hooks/revenue-and-sales-hook.md new file mode 100644 index 0000000..a55978c --- /dev/null +++ b/plugins/foreman/content/hooks/revenue-and-sales-hook.md @@ -0,0 +1,94 @@ +--- +name: "revenue-and-sales-hook" +description: "Captures intent related to revenue generation, sales performance, customer acquisition, deal closure, and pricing friction" +trigger_patterns: + - "sales are dropping" + - "can't close deals" + - "revenue is flat" + - "nobody's buying" + - "pipeline is empty" + - "customers won't pay" + - "our conversion rate sucks" + - "we're not making money" + - "lost another deal" + - "pricing pushback from customers" +routes_to: + diagnostics: + - revenue-diagnosis + - pricing-diagnosis + - customer-churn-diagnosis + skills: + - four-ps-marketing + - cialdini-influence + - balanced-scorecard + playbooks: + - first-100-customers-playbook + - pricing-strategy-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Revenue and Sales Hook + +## Trigger Patterns + +Revenue complaints surface in wildly different language depending on the founder's emotional state and business stage. The following patterns cover the spectrum. + +- "Sales are dropping and I don't know why" +- "Can't close deals no matter what we try" +- "Revenue has been flat for three months" +- "Nobody is buying this thing" +- "Our pipeline is completely empty" +- "Customers love the demo but won't pay" +- "Conversion rate is terrible" +- "We're burning cash and not making money" +- "Lost another big deal this week" +- "Every customer pushes back on our pricing" +- "Our sales cycle is way too long" +- "Leads go cold before we can close them" +- "We're getting outpriced by competitors" +- "Churn is eating all our new revenue" +- "How do I get my first paying customers?" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Dropping sales, flat revenue, not making money | Revenue decline | High | +| Can't close, lost deal, leads go cold, sales cycle too long | Sales execution failure | High | +| Nobody buying, pipeline empty, first customers | Customer acquisition gap | High | +| Pricing pushback, outpriced, won't pay | Pricing misalignment | High | +| Conversion rate, churn eating revenue | Retention and conversion | Medium | + +## Routing Logic + +**Revenue decline** -- Route to `revenue-diagnosis`. The diagnostic will determine whether the cause is market, product, sales execution, or pricing. From there, it may escalate to `pricing-strategy-playbook` or `first-100-customers-playbook`. + +**Sales execution failure** -- Route to `revenue-diagnosis` with a sales-execution flag. If the diagnostic reveals the problem is persuasion or positioning rather than product, escalate to the `cialdini-influence` or `four-ps-marketing` skills. + +**Customer acquisition gap** -- Route to `first-100-customers-playbook` directly if the company is pre-traction. For post-traction companies, route to `revenue-diagnosis` first to separate acquisition from retention problems. + +**Pricing misalignment** -- Route to `pricing-diagnosis`. If confirmed, escalate to `pricing-strategy-playbook`. + +**Retention and conversion** -- Route to `customer-churn-diagnosis`. Churn masquerading as a sales problem is one of the most common misclassifications. + +## Disambiguation + +This hook overlaps with `competition-hook` when pricing pressure originates from a competitive threat rather than internal mispricing. If the entrepreneur mentions a specific competitor or market shift alongside pricing, defer to `competition-hook`. This hook also borders `product-hook` territory when "nobody's buying" actually means "nobody wants the product." If the diagnostic surfaces product-market fit gaps, re-route to `product-hook`. + +## Example Conversations + +**Example 1: Revenue decline** +Entrepreneur says: "Our MRR has been flat for four months. We keep adding customers but revenue won't move." +Hook classifies as: Revenue decline with possible churn offset. +Routes to: `revenue-diagnosis` to distinguish between acquisition stall, pricing cap, and hidden churn. + +**Example 2: Pricing friction** +Entrepreneur says: "Every prospect says we're too expensive. I've already dropped the price twice." +Hook classifies as: Pricing misalignment. +Routes to: `pricing-diagnosis` to determine whether the issue is value communication, market positioning, or actual price-value mismatch. + +**Example 3: Early-stage acquisition** +Entrepreneur says: "We launched two months ago and have three paying users. How do I get this moving?" +Hook classifies as: Customer acquisition gap (pre-traction). +Routes to: `first-100-customers-playbook` directly, bypassing deep diagnosis since the stage is clear. diff --git a/plugins/foreman/content/hooks/strategy-hook.md b/plugins/foreman/content/hooks/strategy-hook.md new file mode 100644 index 0000000..48c5bc7 --- /dev/null +++ b/plugins/foreman/content/hooks/strategy-hook.md @@ -0,0 +1,93 @@ +--- +name: "strategy-hook" +description: "Captures intent related to strategic direction, focus problems, pivot decisions, planning paralysis, and market-shift responses" +trigger_patterns: + - "lost our strategy" + - "should I pivot?" + - "doing too many things" + - "no focus" + - "don't know our direction" + - "keep changing plans" + - "strategy isn't working" + - "we need to rethink everything" + - "market shifted under us" +routes_to: + diagnostics: + - strategic-drift-diagnosis + - decision-paralysis-diagnosis + skills: + - scenario-planning + - swot-pest-analysis + - systems-thinking + - defining-and-exploring-problems + playbooks: + - pivot-playbook + - strategy-reset-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Strategy Hook + +## Trigger Patterns + +Strategic uncertainty is among the most disorienting founder experiences. The language ranges from crisp analytical questioning to formless anxiety about direction. + +- "We've lost our strategy -- if we ever had one" +- "Should I pivot or keep pushing?" +- "We're doing too many things and none of them well" +- "There's no focus in this company" +- "I don't know what direction to take" +- "We keep changing the plan every quarter" +- "Our strategy clearly isn't working" +- "We need to rethink everything from scratch" +- "The market shifted and our plan is obsolete" +- "I can't tell if we should double down or change course" +- "We have too many opportunities and can't choose" +- "The team doesn't understand where we're going" +- "Every board meeting someone questions our strategy" +- "We're spreading ourselves too thin" +- "I've been going back and forth on this decision for months" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Lost strategy, no direction, team doesn't understand | Strategic absence | High | +| Should I pivot, double down or change, rethink everything | Pivot deliberation | High | +| Too many things, no focus, spreading thin, too many opportunities | Focus crisis | High | +| Keep changing plans, back and forth for months | Decision paralysis | High | +| Market shifted, plan obsolete, strategy not working | Strategy obsolescence | Medium | + +## Routing Logic + +**Strategic absence** -- Route to `strategic-drift-diagnosis`. Companies without a clear strategy often have one buried under accumulated tactical decisions. The diagnostic unearths it or confirms its absence. From there, the `strategy-reset-playbook` provides the reconstruction process. The `swot-pest-analysis` skill grounds the reset in market reality. + +**Pivot deliberation** -- Route to `strategic-drift-diagnosis` first. Pivot impulses are often reactions to short-term pain rather than genuine strategic misalignment. The diagnostic separates "this strategy needs more time" from "this strategy is fundamentally wrong." If a pivot is warranted, escalate to `pivot-playbook`. + +**Focus crisis** -- Route to `decision-paralysis-diagnosis`. Lack of focus is a decision failure: the founder has not committed to a direction. The `defining-and-exploring-problems` skill helps structure the choice. If focus loss stems from organizational sprawl rather than decision avoidance, re-route to `strategic-drift-diagnosis`. + +**Decision paralysis** -- Route to `decision-paralysis-diagnosis` directly. Extended indecision has compounding costs. The diagnostic identifies what is blocking the decision -- information gaps, fear of irreversibility, or stakeholder disagreement -- and prescribes accordingly. + +**Strategy obsolescence** -- Route to `strategic-drift-diagnosis` with a market-shift flag. The `scenario-planning` skill helps founders map possible futures when the current map has proven unreliable. If the obsolescence is confirmed, escalate to `strategy-reset-playbook`. + +## Disambiguation + +This hook overlaps with `competition-hook` when strategic uncertainty is triggered by competitive moves. If "we need to rethink everything" follows a competitor's action, the competition-hook should take first pass. Overlap with `product-hook` occurs when "should I pivot?" means "should I change the product?" rather than "should I change the business direction?" If the questioning centers on product features and user feedback, defer to `product-hook`. Overlap with `leadership-hook` occurs when "I don't know our direction" is really "I don't know what I'm doing." If the uncertainty is personal rather than organizational, defer to `leadership-hook`. + +## Example Conversations + +**Example 1: Pivot question** +Entrepreneur says: "We've been at this for eighteen months with mediocre traction. Part of me says keep pushing, part of me says try something new." +Hook classifies as: Pivot deliberation. +Routes to: `strategic-drift-diagnosis` to assess whether the current path has unrealized potential or is genuinely misaligned with market demand. + +**Example 2: Focus collapse** +Entrepreneur says: "We started as a B2B SaaS tool, then added a marketplace, then a services arm. Now nothing is growing because we can't give anything enough attention." +Hook classifies as: Focus crisis. +Routes to: `decision-paralysis-diagnosis` to break the multi-front commitment, likely escalating to `strategy-reset-playbook` for consolidation. + +**Example 3: Market disruption** +Entrepreneur says: "AI just made our core product irrelevant. Our three-year roadmap is worthless." +Hook classifies as: Strategy obsolescence. +Routes to: `strategic-drift-diagnosis` with urgency, then `scenario-planning` to map new trajectories, potentially into `pivot-playbook` for execution. diff --git a/plugins/foreman/content/hooks/team-hook.md b/plugins/foreman/content/hooks/team-hook.md new file mode 100644 index 0000000..81bf1e2 --- /dev/null +++ b/plugins/foreman/content/hooks/team-hook.md @@ -0,0 +1,97 @@ +--- +name: "team-hook" +description: "Captures intent related to team dysfunction, hiring struggles, employee turnover, morale collapse, interpersonal conflict, and culture decay" +trigger_patterns: + - "team isn't working" + - "people are leaving" + - "morale is terrible" + - "can't hire anyone good" + - "too much conflict" + - "nobody takes ownership" + - "my best person just quit" + - "team is burned out" + - "toxic dynamic" +routes_to: + diagnostics: + - team-dysfunction-diagnosis + - hiring-diagnosis + - culture-erosion-diagnosis + skills: + - tuckman-team-stages + - belbin-team-roles + - psychological-safety + - radical-candor + - thomas-kilmann-conflict + playbooks: + - team-rebuild-playbook +priority: "high" +author: "Fatih Guner" +--- + +# Team Hook + +## Trigger Patterns + +Team problems are deeply personal for founders. The language mixes management observation with emotional exhaustion and, frequently, self-blame. + +- "The team just isn't working together" +- "People keep leaving and I can't stop the bleeding" +- "Morale is at rock bottom" +- "I can't hire anyone good -- or anyone at all" +- "There's too much conflict between departments" +- "Nobody takes ownership of anything" +- "My best engineer just gave notice" +- "The whole team is burned out" +- "There's a toxic dynamic I can't fix" +- "I dread our team meetings" +- "Feels like I'm the only one who cares" +- "People are quiet-quitting" +- "We lost three people this month" +- "My co-founder and I can't agree on anything" +- "The culture we built is falling apart" + +## Intent Classification + +| Pattern Cluster | Classified Intent | Confidence | +|---|---|---| +| Team not working, conflict, toxic dynamic | Team dysfunction | High | +| People leaving, best person quit, three people this month | Retention crisis | High | +| Can't hire, nobody good available | Hiring failure | High | +| Morale, burned out, quiet-quitting, dread meetings | Morale collapse | High | +| Nobody owns anything, only one who cares | Accountability vacuum | Medium | +| Co-founder disagreement, culture falling apart | Foundational fracture | Medium | + +## Routing Logic + +**Team dysfunction** -- Route to `team-dysfunction-diagnosis`. Dysfunction has many root causes: unclear roles, mismatched working styles, absent feedback loops, or structural misalignment. The `tuckman-team-stages` and `belbin-team-roles` skills help map the team's current state. If conflict is the dominant symptom, `thomas-kilmann-conflict` provides the response framework. + +**Retention crisis** -- Route to `culture-erosion-diagnosis`. Departures are lagging indicators; the diagnostic looks for the leading causes. If culture is intact and the problem is compensation or growth opportunity, the path differs from toxic-culture retention loss. + +**Hiring failure** -- Route to `hiring-diagnosis`. Hiring problems divide into pipeline (not enough candidates), selection (wrong candidates), or closing (candidates decline offers). Each requires a different intervention. + +**Morale collapse** -- Route to `team-dysfunction-diagnosis` with a morale flag. The `psychological-safety` skill assesses whether the environment permits honest expression. `radical-candor` provides the communication framework for rebuilding trust. + +**Accountability vacuum** -- Route to `team-dysfunction-diagnosis`. Ownership gaps typically trace to unclear expectations, missing feedback, or misaligned incentives. The `hackman-enabling-conditions` framework from the skills library addresses structural enabling conditions. + +**Foundational fracture** -- Co-founder conflict routes to `cofounder-conflict-diagnosis`. Culture disintegration routes to `culture-erosion-diagnosis`, then to `team-rebuild-playbook` if a reset is warranted. + +## Disambiguation + +This hook overlaps with `leadership-hook` when "the team isn't working" reflects the founder's own leadership gaps rather than team-level problems. The distinguishing signal: if the founder describes the team as broken, this hook applies. If the founder describes themselves as inadequate or overwhelmed, route to `leadership-hook`. Overlap with `growth-hook` occurs when team strain results from scaling. If "team can't keep up" is framed as a growth constraint, defer to `growth-hook`. + +## Example Conversations + +**Example 1: Retention spiral** +Entrepreneur says: "We've lost five people in two months. The ones who stay seem checked out." +Hook classifies as: Retention crisis with morale collapse. +Routes to: `culture-erosion-diagnosis` to identify whether departures stem from culture, leadership, compensation, or growth ceiling. + +**Example 2: Hiring wall** +Entrepreneur says: "I've been trying to hire a senior developer for four months. Nobody good applies, and the ones who do turn us down." +Hook classifies as: Hiring failure. +Routes to: `hiring-diagnosis` to separate pipeline, selection, and closing problems. + +**Example 3: Co-founder rift** +Entrepreneur says: "My co-founder and I haven't agreed on a major decision in months. Every conversation turns into an argument." +Hook classifies as: Foundational fracture. +Routes to: `cofounder-conflict-diagnosis` to assess whether the disagreement is tactical or existential. diff --git a/plugins/foreman/content/implementation/IMPLEMENTATION.md b/plugins/foreman/content/implementation/IMPLEMENTATION.md new file mode 100644 index 0000000..18638c6 --- /dev/null +++ b/plugins/foreman/content/implementation/IMPLEMENTATION.md @@ -0,0 +1,174 @@ +--- +name: implementation-tracking +description: "Runtime-backed task status, progress, blockers and accountability." +author: "Fatih Guner" +--- + + + +# Implementation Tracking -- The Accountability Layer + +The most dangerous gap in entrepreneurial decision-making is not the gap between ignorance and knowledge. It is the gap between knowing and doing. A founder who completes Porter's Five Forces analysis and files it away has gained nothing. A founder who runs the pivot playbook, produces a brilliant action plan, and then returns to the same habits three weeks later has consumed effort without creating change. Foreman's diagnostics identify problems. Its skills produce frameworks. Its playbooks chain frameworks into comprehensive strategies. Implementation tracking ensures those strategies leave the document and enter the business. + +This system transforms Foreman from an advisor that produces recommendations into a partner that tracks whether recommendations become reality. + +--- + +## What Implementation Tracking Is + +Implementation tracking is the persistence and accountability layer that monitors the execution of recommendations produced by skills, diagnostics, and playbooks. It is not project management. It does not replace Jira, Asana, or a whiteboard. It tracks the specific outputs of Foreman's analytical system -- the five-step action plan from a playbook, the three strategic priorities from a SWOT analysis, the pricing change recommended by a diagnostic -- and holds the entrepreneur accountable for acting on them. + +Every recommendation that emerges from the system becomes a trackable implementation item. Each item carries a status, a progress percentage, a deadline, an owner, and a history of check-ins. When items stall, the system detects it. When blockers emerge, the system categorizes them and routes to the appropriate diagnostic or skill. When items complete, the system records the outcome and moves them to the history layer. + +The operating assumption: producing insight is 20% of the value. Executing on insight is the remaining 80%. This system exists for the 80%. + +--- + +## How It Works + +### Activation + +Implementation tracking activates automatically in three scenarios: + +1. **Playbook step completion.** When the playbook-runner-agent completes a step that produces actionable recommendations, each recommendation becomes an implementation item. +2. **Skill application with action items.** When the skill-executor-agent produces output containing explicit recommendations (not all skill outputs are actionable -- a SWOT analysis is informational, but "restructure pricing tier" is actionable), those recommendations are extracted as implementation items. +3. **Diagnostic routing.** When a diagnostic produces a root-cause finding with a prescribed next step, that next step becomes an implementation item. + +### Research-Originated Items + +Research tasks generated by `/research` commands or recommended by agents are automatically registered as implementation items with source type `research-guide`. They track research progress through the same status workflow (`not-started` --> `in-progress` --> `completed`). When a research item completes, the system prompts: "Research complete. Ready to apply the skill that needs this data?" The linked skill is derived from the research guide's `feeds_into_skills` frontmatter. + +### Item Creation + +Each implementation item is created with the following properties: + +- **id** -- Unique identifier (e.g., `impl-001`) +- **source** -- Where the item originated: playbook step, skill recommendation, or diagnostic routing +- **source_ref** -- Specific reference to the originating step or skill +- **description** -- What needs to be done, in concrete terms +- **owner** -- Who is responsible (default: "self" for solopreneurs and founders without delegation) +- **created** -- Date the item was created +- **deadline** -- Target completion date +- **status** -- Current state (see Implementation States below) +- **progress** -- Percentage complete (0-100) +- **blockers** -- Active blockers preventing progress +- **notes** -- Running notes and observations +- **check_ins** -- History of progress updates from weekly check-ins + +### Weekly Check-In Cycle + +Every seven days, the system prompts for a progress review via the `/check-in` command. The check-in walks through all active implementation items, records updates, detects stalls, and flags blockers. This cadence is not arbitrary -- it matches the active memory layer's update frequency and prevents items from drifting into neglect without creating daily overhead. + +### Stall Detection + +When an implementation item remains at the same progress percentage for two or more consecutive check-ins (14+ days without movement), the system flags it as stalled. Stalled items trigger a blocker analysis: the system asks targeted questions to identify why progress has stopped and categorizes the blocker for routing. + +--- + +## Implementation States + +| State | Meaning | Transitions To | +|-------|---------|----------------| +| `not-started` | Recommendation produced, not yet acted on | `in-progress`, `abandoned`, `deferred` | +| `in-progress` | Work has begun, progress tracked as percentage | `completed`, `blocked`, `abandoned`, `deferred` | +| `blocked` | Explicitly blocked, blocker identified and categorized | `in-progress` (when blocker resolves), `abandoned`, `deferred` | +| `completed` | Successfully implemented, outcome recorded | -- (terminal state, moves to history) | +| `abandoned` | Deliberately stopped, reason recorded | -- (terminal state, moves to history) | +| `deferred` | Postponed to a specific future date with justification | `not-started` (when defer date arrives) | + +State transitions are recorded with timestamps. The history of state changes provides a behavioral signal: a founder who frequently moves items from `in-progress` to `deferred` may be avoiding execution. A founder whose items cluster in `blocked` may need different support than one whose items cluster in `not-started`. + +--- + +## Blocker Categories + +When an item enters `blocked` status, the blocker is classified into one of five categories. Classification drives routing -- each category maps to specific diagnostics, skills, or system responses. + +| Category | Description | Routing | +|----------|-------------|---------| +| **Resource** | Insufficient time, money, or people to execute | Route to `resource-allocation` skill, `operations-diagnosis` | +| **Knowledge** | Do not know how to execute the recommendation | Route to relevant skill for deeper application, or surface related skills | +| **Dependency** | Waiting on an external party, deliverable, or decision | Route to `stakeholder-map` template, `partnership-diagnosis` if applicable | +| **Motivation** | Avoiding the task -- psychological resistance, fear of failure, discomfort | Route to `stoic-emotional-mastery`, `stoic-control-and-clarity`, `founder-mental-health-check` | +| **External** | Market conditions, regulatory requirements, or partner constraints beyond control | Route to `scenario-planning` skill, `swot-pest-analysis` for reassessment | + +Motivation blockers deserve special attention. They are the most common and the least reported. The system surfaces them by inference: when a founder cannot articulate a resource, knowledge, dependency, or external blocker, the system gently probes whether the true obstacle is internal resistance. + +--- + +## Check-In Protocol + +The `/check-in` command initiates the weekly accountability review. The protocol proceeds as follows: + +**Phase 1 -- Status Sweep.** The system presents all active implementation items (status: `not-started`, `in-progress`, `blocked`) with their current progress and last check-in date. Items are sorted by deadline proximity. + +**Phase 2 -- Progress Update.** For each item, the system asks: "What progress have you made on [description] since [last check-in date]?" The entrepreneur provides an updated percentage and a brief note. If the percentage has not changed, the system probes for blockers. + +**Phase 3 -- Blocker Identification.** For any item with zero progress delta, the system asks: "What is preventing progress?" Responses are categorized into the five blocker types. If the entrepreneur cannot identify a specific blocker, the system asks: "Is this something you have been avoiding? If so, what makes it uncomfortable?" This surfaces motivation blockers without accusation. + +**Phase 4 -- Priority Rebalancing.** After all items are reviewed, the system identifies the three highest-priority items for the coming week based on deadline proximity, strategic importance (source playbook or skill), and blocker resolution potential. These become the recommended focus. + +**Phase 5 -- Memory Persistence.** All updates are written to the active memory layer. Completed items move to history. Check-in data is appended to each item's check_in array. The session layer records the check-in event. + +--- + +## Integration with Memory + +Implementation tracking extends two existing memory layers without replacing them. + +**Active layer extension.** The active layer gains an `implementation_items` array alongside `current_playbook`, `pending_decisions`, and `follow_ups`. This array holds all items in non-terminal states. The memory-agent reads and writes this array during session start and end. + +**History layer extension.** The `decisions_made` section in the history layer gains implementation tracking fields: `implementation_status`, `implementation_started`, `implementation_completed`, and `implementation_notes`. When an implementation item reaches a terminal state (`completed` or `abandoned`), its data enriches the corresponding history entry. The `playbooks_completed` section gains similar fields to track which playbook recommendations were actually executed versus merely produced. + +--- + +## Integration with Diagnostics + +Blocker detection creates a feedback loop into the diagnostic system. When a blocker is identified and categorized, the system checks whether a relevant diagnostic exists: + +- Resource blocker with cash implications --> `fundraising-diagnosis` or `operations-diagnosis` +- Knowledge blocker in a specific domain --> route to the skill that produced the original recommendation for deeper application +- Dependency blocker involving a partner --> `partnership-diagnosis` +- Motivation blocker with burnout signals --> `leadership-diagnosis` with `founder-mental-health-check` template +- External blocker requiring strategic reassessment --> `strategy-diagnosis` or `competition-diagnosis` + +This routing is automatic. The system does not merely flag the blocker -- it offers the next step. + +--- + +## Integration with Stoic Mode + +When `/stoic on` is active, the implementation tracking system gains philosophical depth. Check-ins include Stoic reflection prompts drawn from the twelve Stoic skills: + +- **Dichotomy of control.** For each blocker: "Is this within your control, within your influence, or entirely external? Are you spending energy on what you cannot change?" +- **Premeditatio malorum.** At each check-in: "What could go wrong with your highest-priority item this week? Have you prepared for it, or are you assuming a clear path?" +- **Amor fati.** For abandoned items: "Can you embrace this outcome rather than resent it? What does this abandonment teach you about your actual priorities versus your stated ones?" +- **Motivation blockers** receive specific Stoic framing: "Which of the Seven Functions of the Mind is failing here? Is this a Refusal problem (inability to say no to distractions), a Purpose problem (unclear why this matters), or a Preparation problem (you have not readied yourself for the difficulty)?" + +Stoic mode does not soften the accountability. It deepens it. + +--- + +## Integration with Solo Mode + +When `/solo` is active, implementation tracking adapts for the solopreneur context: + +- **Owner field defaults to "self" permanently.** No delegation tracking -- the solopreneur is every department. +- **Isolation-specific blocker detection.** The system adds a sixth blocker probe: "Are you blocked because you need help but have no team to ask? Would a contractor, advisor, or community solve this?" This surfaces the solopreneur's unique constraint -- the absence of colleagues to unblock them. +- **Capacity-aware prioritization.** During check-in Phase 4, the system factors in solopreneur capacity: "You have 12 active implementation items. A solo operator can realistically advance 3-5 per week. Which three matter most?" +- **Burnout detection.** If progress across all items drops simultaneously over two consecutive check-ins, the system flags potential burnout rather than assuming laziness: "Progress has stalled across the board. Before we discuss individual items -- how are you?" + +Solo mode recognizes that the solopreneur's greatest implementation risk is not bad strategy. It is exhaustion. + +--- + +## System Boundaries + +Implementation tracking deliberately does not: + +- **Replace external project management tools.** It tracks Foreman-originated recommendations, not the entrepreneur's full task list. +- **Assign arbitrary deadlines.** Deadlines are set by the entrepreneur or derived from playbook timelines. The system never invents urgency. +- **Judge the entrepreneur.** Stall detection and blocker analysis are diagnostic, not punitive. The system surfaces patterns. The entrepreneur decides what to do about them. +- **Track indefinitely.** Items that remain in `not-started` for 30 days are flagged for a decision: begin, defer with a date, or abandon with a reason. Zombie items are not permitted. + +The goal is accountability with respect. A good mentor remembers what you committed to, asks how it went, and helps when you are stuck. That is the operating model. diff --git a/plugins/foreman/content/implementation/implementation-schema.yaml b/plugins/foreman/content/implementation/implementation-schema.yaml new file mode 100644 index 0000000..2d5c846 --- /dev/null +++ b/plugins/foreman/content/implementation/implementation-schema.yaml @@ -0,0 +1,142 @@ +# Implementation Tracking Schema +# Defines data structures for tracking execution of recommendations +# Extends the active and history memory layers +# Author: Fatih Guner + +--- + +# ============================================================================= +# ACTIVE LAYER EXTENSION +# Added to active.yaml alongside current_playbook, pending_decisions, follow_ups +# Contains all implementation items in non-terminal states +# ============================================================================= + +implementation_items: [] + # Entry format: + # - id: "impl-001" + # source: "playbook-step" # playbook-step | skill-recommendation | diagnostic-routing + # source_ref: "pivot-playbook/step-3" + # description: "Redesign business model canvas for B2B pivot" + # owner: "self" # "self" default; name if delegated + # created: "2026-03-28" + # deadline: "2026-04-15" + # status: "in-progress" # not-started | in-progress | blocked | completed | abandoned | deferred + # progress: 40 # 0-100 percentage + # blockers: [] # active blockers (see blocker schema below) + # notes: + # - date: "2026-03-29" + # note: "Identified three potential B2B segments from interview data" + # check_ins: + # - date: "2026-04-01" + # progress: 20 + # note: "Started customer interviews for enterprise segment" + # - date: "2026-04-08" + # progress: 40 + # note: "5 interviews done, pattern emerging in procurement cycle" + # state_history: + # - from: "not-started" + # to: "in-progress" + # date: "2026-03-30" + # deferred_until: null # date string when status is "deferred" + # completed_date: null # date string when status is "completed" + # abandoned_reason: null # string when status is "abandoned" + # outcome: null # recorded result when completed + +# Blocker schema (nested within implementation_items[].blockers): + # - id: "blk-001" + # category: "resource" # resource | knowledge | dependency | motivation | external + # description: "Need $5K for customer research tool but not in current budget" + # identified: "2026-04-08" + # resolved: null # date when resolved, null if active + # resolution: null # how it was resolved + # routes_to: + # diagnostic: "operations-diagnosis" + # skill: "resource-allocation" + # template: null + +# ============================================================================= +# HISTORY LAYER EXTENSION +# Added fields to existing history.yaml sections +# Enriches decisions_made and playbooks_completed with execution data +# ============================================================================= + +# Extension to history.decisions_made entries: + # - date: "2026-01-18" + # decision: "Hired onboarding specialist instead of second sales rep" + # rationale: "Churn reduction has higher ROI than new acquisition" + # outcome: "pending" + # review_date: "2026-02-18" + # related_skill: "evaluating-and-deciding" + # # --- Implementation tracking fields (new) --- + # implementation_status: "completed" # completed | abandoned | partial | not-tracked + # implementation_started: "2026-01-20" + # implementation_completed: "2026-02-14" + # implementation_notes: "Took 4 weeks instead of estimated 2. Onboarding specialist started Feb 1, first cohort improvements visible by Feb 14." + # implementation_items_ref: + # - "impl-003" + # - "impl-004" + +# Extension to history.playbooks_completed entries: + # - date: "2026-01-20" + # playbook: "team-rebuild-playbook" + # status: "completed" + # key_outcome: "Restructured hiring process, 3 new role descriptions created" + # # --- Implementation tracking fields (new) --- + # recommendations_produced: 5 # total actionable items generated + # recommendations_completed: 3 # items that reached completed status + # recommendations_abandoned: 1 # items deliberately abandoned + # recommendations_pending: 1 # items still in active tracking + # implementation_rate: 60 # percentage completed of total produced + # implementation_duration_days: 28 # days from first item started to last item resolved + +# ============================================================================= +# SESSION LAYER EXTENSION +# Ephemeral tracking during active conversation +# ============================================================================= + +# Extension to session.yaml: + # implementation_events: [] + # Entry format: + # - type: "item-created" # item-created | progress-updated | blocker-added | status-changed | check-in-completed + # item_id: "impl-007" + # timestamp: "2026-04-08T14:30:00" + # details: "Created from pivot-playbook step 3 recommendation" + +# ============================================================================= +# IMPLEMENTATION SUMMARY (computed, not stored) +# Generated on demand by /track command and dashboard template +# ============================================================================= + +# implementation_summary: +# total_items: 12 +# by_status: +# not_started: 2 +# in_progress: 5 +# blocked: 2 +# completed: 2 +# abandoned: 1 +# deferred: 0 +# completion_rate: 17 # percentage of total that reached completed +# overdue_count: 3 # items past deadline and not completed +# stalled_count: 2 # items with no progress delta for 14+ days +# blockers_by_category: +# resource: 1 +# knowledge: 0 +# dependency: 1 +# motivation: 0 +# external: 0 +# velocity: # items completed per week, trailing 4 weeks +# week_1: 0 +# week_2: 1 +# week_3: 0 +# week_4: 1 +# avg_completion_days: 18 # average days from created to completed +# next_deadline: "2026-04-10" # nearest upcoming deadline + +# ============================================================================= +# ID GENERATION RULES +# ============================================================================= +# Implementation item IDs: "impl-" + zero-padded sequential number (impl-001, impl-002, ...) +# Blocker IDs: "blk-" + zero-padded sequential number (blk-001, blk-002, ...) +# IDs are globally unique within an entrepreneur's memory space +# IDs are never reused, even after items move to history diff --git a/plugins/foreman/content/implementation/support/blocker-diagnosis.md b/plugins/foreman/content/implementation/support/blocker-diagnosis.md new file mode 100644 index 0000000..1875221 --- /dev/null +++ b/plugins/foreman/content/implementation/support/blocker-diagnosis.md @@ -0,0 +1,130 @@ +--- +name: "blocker-diagnosis" +description: "Diagnoses why an implementation item is blocked or stalled by distinguishing between external constraints and internal obstacles, then routing through capability gaps, capacity limits, and motivation misalignment to a targeted resolution. Use when an implementation item shows zero progress for two or more check-in cycles, or when the entrepreneur explicitly reports being stuck." +entry_symptoms: + - "This task has been stuck for weeks" + - "I keep postponing this" + - "I don't know how to do this step" + - "I'm waiting on someone" + - "I started but can't finish" + - "This feels impossible" +possible_diagnoses: + - resource-dependency + - external-environment-block + - knowledge-gap + - process-gap + - capacity-overload + - energy-depletion + - fear-based-avoidance + - perfectionism-paralysis + - wrong-task + - motivation-misalignment +routes_to_skills: + - eisenhower-matrix + - focus-and-priority-management + - delegation-and-empowerment + - stoic-fortitude-and-resilience + - stoic-control-and-clarity + - stoic-pragmatism + - emotional-courage + - defining-and-exploring-problems + - evaluating-and-deciding + - creative-completion-and-renewal + - leader-resilience-and-wellbeing + - wanting-what-matters +routes_to_templates: + - blocker-analysis + - decision-journal + - weekly-progress-report + - implementation-dashboard +author: "Fatih Guner" +--- + +# Blocker Diagnosis + +Stalled implementation items are not random. They cluster around a small number of root causes, and each root cause responds to a different intervention. Treating a knowledge gap with motivational advice wastes time. Treating a fear problem with a process template wastes even more. This diagnostic separates external constraints from internal obstacles, then identifies the specific failure mode so the system can route to the right tool -- not a generic pep talk. + +## Entry Symptoms + +The entrepreneur says some version of: "This task has been stuck for weeks," "I keep postponing this," "I don't know how to do this step," "I'm waiting on someone," "I started but can't finish," or "This feels impossible." The item may carry `blocked` status explicitly, or it may sit in `in-progress` with zero progress delta across multiple check-ins -- the quieter and more dangerous variant. + +## Triage Questions + +### Q1: Is the blocker EXTERNAL (waiting on someone or something outside your control) or INTERNAL (within your control to resolve)? +- **External** -- Proceed to Q2-External. +- **Internal** -- Proceed to Q2-Internal. +- **Unclear** -- Ask: "If every external person and resource were available tomorrow, could you finish this?" A "yes" confirms external. A hesitation suggests internal. + +### Q2-External: Is the external blocker a DEPENDENCY (specific person, resource, or deliverable) or an ENVIRONMENT constraint (market, regulatory, or systemic)? +- **Dependency** -- Waiting on a specific person, hire, funding, or partner. Likely diagnosis: **resource-dependency**. +- **Environment** -- Market, regulatory, or systemic constraint no individual action can accelerate. Likely diagnosis: **external-environment-block**. + +### Q2-Internal: Is the internal blocker a CAPABILITY gap (don't know how), a CAPACITY gap (no time/energy), or a MOTIVATION gap (avoiding it)? +- **Capability** -- Proceed to Q3-Capability. +- **Capacity** -- Proceed to Q3-Capacity. +- **Motivation** -- Proceed to Q3-Motivation. + +### Q3-Capability: Is the missing knowledge CONCEPTUAL (need to learn) or TACTICAL (know the theory, lack the how-to)? +- **Conceptual** -- Likely diagnosis: **knowledge-gap**. +- **Tactical** -- Likely diagnosis: **process-gap**. + +### Q3-Capacity: Is the constraint TIME (too many priorities) or ENERGY (burnout/overwhelm)? +- **Time** -- The task keeps getting bumped. Likely diagnosis: **capacity-overload**. +- **Energy** -- Depleted across the board. Likely diagnosis: **energy-depletion**. + +### Q3-Motivation: Is the avoidance RATIONAL (the task itself may be wrong) or EMOTIONAL (the task is correct but uncomfortable)? +- **Rational** -- Likely diagnosis: **wrong-task** or **motivation-misalignment**. +- **Emotional** -- Proceed to Q4-Emotional. + +### Q4-Emotional: What specifically drives the avoidance? +- **Fear of failure** -- Afraid the result will expose inadequacy. Likely diagnosis: **fear-based-avoidance**. +- **Fear of success/exposure** -- Completion increases visibility or scrutiny. Likely diagnosis: **fear-based-avoidance**. +- **Perfectionism** -- Waiting for ideal conditions before acting. Likely diagnosis: **perfectionism-paralysis**. +- **Conflict avoidance** -- The task requires a difficult confrontation. Likely diagnosis: **fear-based-avoidance**. + +## Diagnosis Map + +| Diagnosis | Core Problem | Distinguishing Signal | +|-----------|-------------|----------------------| +| **Resource dependency** | Waiting on a specific person, deliverable, or resource | Entrepreneur can name exactly who or what they are waiting for | +| **External environment block** | Market, regulatory, or systemic constraint | No individual action can accelerate resolution | +| **Knowledge gap** | Does not understand the domain well enough to execute | "I don't know where to start" | +| **Process gap** | Understands theory but lacks tactical execution method | "I get the concept but don't know the specific steps" | +| **Capacity overload** | Too many priorities competing for finite bandwidth | Task keeps losing to other items in weekly prioritisation | +| **Energy depletion** | Burnout preventing execution across the board | Progress stalled on multiple items simultaneously | +| **Fear-based avoidance** | Psychological resistance to the outcome or process | Entrepreneur hesitates, changes subject, or rationalises delay | +| **Perfectionism paralysis** | Refusal to act until conditions are ideal | All preparation complete but execution never begins | +| **Wrong task** | The task itself is flawed in conception or approach | Resistance dissolves when the task is reframed | +| **Motivation misalignment** | Task does not connect to what the entrepreneur values | "I know I should do this, but I just don't care about it" | + +## Routing + +**Resource dependency:** Apply `stakeholder-map` to identify escalation paths. Apply `delegation-and-empowerment` if the dependency can be reassigned. Use `blocker-analysis` template to document impact and set escalation triggers. + +**External environment block:** Apply `scenario-planning` to model wait-time scenarios. Apply `stoic-control-and-clarity` to separate controllable from uncontrollable. Redirect effort to items within control. + +**Knowledge gap:** Route to the specific skill that produced the original recommendation. Apply `learning-agility` to structure a learning plan. Use `learning-plan` template. + +**Process gap:** Route to the relevant framework skill with emphasis on application prompts and output template sections. Apply `creative-shaping-and-craft` for strategy-to-deliverable translation. + +**Capacity overload:** Apply `eisenhower-matrix` to force-rank all active items. Apply `focus-and-priority-management` to protect execution time. Apply `delegation-and-empowerment` to offload non-essential items. + +**Energy depletion:** Apply `leader-resilience-and-wellbeing` to assess burnout. Apply `stoic-fortitude-and-resilience` for endurance framing. Reduce active items to three maximum until energy recovers. + +**Fear-based avoidance:** Apply `emotional-courage` to name and confront the fear. Apply `stoic-fortitude-and-resilience` for courage framing. Apply `stoic-control-and-clarity` to separate feared outcomes from actual risks. Use `decision-journal` to externalise the fear. + +**Perfectionism paralysis:** Apply `stoic-pragmatism` to reframe "good enough" as strategic advantage. Apply `creative-completion-and-renewal` for finishing discipline. Apply `choosing-and-executing` for the 70% rule. + +**Wrong task:** Apply `defining-and-exploring-problems` to reframe what needs to happen. Apply `evaluating-and-deciding` to assess restructure or abandon. Use `decision-journal` to record the pivot rationale. + +**Motivation misalignment:** Apply `wanting-what-matters` to reconnect the task to genuine priorities. Apply `purpose-driven-leadership` to test alignment. If the task truly does not matter, abandon it formally. + +## Red Flags + +Halt the diagnostic and redirect if any of the following conditions are present: + +- **Persistent hopelessness, inability to function, or withdrawal from all activities.** This may indicate a mental health crisis. Route to professional support before applying any framework. +- **The blocker involves potential legal liability, regulatory violation, or financial fraud.** Route to qualified legal or financial counsel immediately. +- **Cash runway is under 4 weeks and the stalled item is revenue-critical.** Prioritise emergency cash management over systematic diagnosis. +- **The entrepreneur reports being in physical danger or an abusive professional relationship.** Recommend immediate professional intervention. +- **Multiple items stalled 30+ days with no engagement.** Total disengagement may signal the entrepreneur has mentally exited the venture. Surface this directly rather than treating each item individually. diff --git a/plugins/foreman/content/implementation/support/implementation-retrospective.md b/plugins/foreman/content/implementation/support/implementation-retrospective.md new file mode 100644 index 0000000..1b8d013 --- /dev/null +++ b/plugins/foreman/content/implementation/support/implementation-retrospective.md @@ -0,0 +1,119 @@ +--- +name: "implementation-retrospective" +description: "Produces a structured post-implementation review for analysing execution quality after a playbook completes or a major implementation cycle finishes. Captures what was planned versus what happened, identifies recurring blocker patterns, grades execution quality by step, and extracts process improvements for the next cycle. Designed for honest self-assessment, not self-congratulation." +audience: "self" +applicable_skills: + - leader-self-reflection + - learning-from-failure + - defining-and-exploring-problems + - stoic-self-awareness + - managing-weakness-and-mistakes + - creative-completion-and-renewal +format: "structured-review" +author: "Fatih Guner" +--- + +# Implementation Retrospective + + + +**Date:** [YYYY-MM-DD] | **Source:** [Playbook / Skill / Diagnostic] | **Ref:** [ID] | **Period:** [Start] to [End] + +--- + +## Implementation Summary + +| Item ID | Description | Planned deadline | Actual completion | Final status | +|---------|-------------|-----------------|------------------|--------------| +| [impl-XXX] | [Description] | [Date] | [Date or 'not completed'] | [completed / abandoned / deferred / in-progress] | + +**Planned:** [N items, N weeks] | **Actual:** [N completed of N total ([%]%), N weeks] | **Variance:** [+/- N days] + +--- + +## Outcome Assessment + +**Intended outcome:** [What the implementation was supposed to achieve] + +**Actual outcome:** [What actually changed] | **Achieved:** [Fully / Partially / Not achieved / Too early to assess] + +| Metric | Before | After | Change | +|--------|--------|-------|--------| +| [KPI] | [Baseline] | [Current] | [+/- change] | + +--- + +## Blocker History + +| Blocker ID | Category | Description | Days | Resolution | +|------------|----------|-------------|------|------------| +| [blk-XXX] | [resource / knowledge / dependency / motivation / external] | [What blocked] | [N] | [How resolved, or 'unresolved'] | + +**Summary:** [N blockers] | **Avg resolution:** [N days] | **Longest:** [blk-XXX, N days] + +--- + +## Pattern Analysis + +### Recurring Blocker Types + +| Category | This cycle | Previous cycles | Trend | +|----------|-----------|----------------|-------| +| Resource | [N] | [N or N/A] | [Increasing / Stable / Decreasing] | +| Knowledge | [N] | [N or N/A] | [Increasing / Stable / Decreasing] | +| Dependency | [N] | [N or N/A] | [Increasing / Stable / Decreasing] | +| Motivation | [N] | [N or N/A] | [Increasing / Stable / Decreasing] | +| External | [N] | [N or N/A] | [Increasing / Stable / Decreasing] | + +**Dominant category:** [Category] -- [What this reveals about your execution pattern] + +### Recurring Stall Points + +_0% = starting problem. 30% = complexity problem. 80% = finishing problem._ + +**Most common stall %:** [N]% | **Interpretation:** [What it suggests] + +--- + +## Execution Quality + +| Item ID | Grade | Notes | +|---------|-------|-------| +| [impl-XXX] | [Excellent / Good / Adequate / Poor / Skipped] | [Why this grade -- be specific] | + +**Done well:** [Items and what made them successful] | **Done poorly:** [Items and what went wrong] | **Skipped:** [Deliberately or by avoidance?] + +--- + +## Key Learnings + +1. [Specific, actionable, honest] +2. [Specific, actionable, honest] +3. [Specific, actionable, honest] + +**Single biggest insight:** [The one thing that would most improve your next implementation] + +--- + +## Process Improvements + +| Improvement | Applies to | Enforcement mechanism | +|------------|-----------|----------------------| +| [Specific process change] | [All implementations / Specific type] | [How you will ensure this happens] | + +--- + +## Unfinished Business + + + +| Item ID | Description | Status | Decision | Rationale | +|---------|-------------|--------|----------|-----------| +| [impl-XXX] | [Description] | [in-progress at N% / blocked / deferred] | [Carry forward / Defer to date / Abandon] | [Honest assessment] | + +**Carried forward:** [N] | **Abandoned:** [N] | **Deferred:** [N] + +--- + +**Overall rating:** [1-10] | **One-sentence summary:** [The essence of this cycle in one honest sentence for your future self.] diff --git a/plugins/foreman/content/implementation/support/stuck-protocols.yaml b/plugins/foreman/content/implementation/support/stuck-protocols.yaml new file mode 100644 index 0000000..bd3c1ac --- /dev/null +++ b/plugins/foreman/content/implementation/support/stuck-protocols.yaml @@ -0,0 +1,808 @@ +# Implementation Support: Stuck Protocols +# Targeted interventions organized by skill category +# When an entrepreneur stalls on a specific type of implementation task, +# this file provides the concrete resolution path — not generic advice, +# but the specific next action for the specific failure mode. +# Author: Fatih Guner + +--- + +stuck_protocols: + + # =========================================================================== + # 1. FRAMEWORKS (50 skills) + # =========================================================================== + frameworks: + general: > + Framework implementation stalls most often at two points: the analysis-to-action + transition (the framework is complete but the entrepreneur does not know what to + DO with the output) and the data-gathering phase (the framework requires inputs + the entrepreneur cannot easily obtain). A completed framework that produces no + decision is wasted effort. + skill_specific: + porters-five-forces: + common_sticking_points: + - point: "Cannot get competitive data to populate the analysis" + resolution: > + Use free-tier competitive intelligence tools (SimilarWeb, SEMrush free, + Crunchbase). Ask three recent customers what alternatives they evaluated + before choosing you. Do a mystery shop of two competitors. Check job + postings of competitors for strategic signals (hiring = investing in that + area). 80% accuracy is sufficient — do not wait for perfection. + route_to: "scenario-planning" + - point: "Analysis is complete but does not translate into clear action" + resolution: > + Force-rank the five forces by impact severity. Pick the single force + exerting the most pressure. Define one defensive action and one offensive + action for that force alone. Ignore the other four until the first is + addressed. + route_to: "evaluating-and-deciding" + - point: "Supplier or buyer power analysis feels irrelevant to a digital business" + resolution: > + Reframe suppliers as any upstream dependency (cloud infrastructure, API + providers, talent pool, content creators). Reframe buyers as any customer + segment with switching options. The force names are industrial-era labels; + the underlying dynamics are universal. + route_to: "business-model-canvas" + if_stuck_checklist: + - "Have you identified ALL five forces, or just the ones that feel most threatening?" + - "Are you confusing 'hard to measure' with 'not important'?" + - "Does your analysis include at least one data point per force, however imperfect?" + - "Have you translated findings into specific strategic actions, not just observations?" + + business-model-canvas: + common_sticking_points: + - point: "Cannot define the value proposition clearly" + resolution: > + Interview five customers with one question: 'What would you use if we + did not exist?' Their answers reveal your actual value proposition — which + may differ from what you believe it is. If you have no customers yet, + articulate the top three pains of your target segment and map each to a + specific feature. + route_to: "defining-and-exploring-problems" + - point: "Revenue streams section feels speculative" + resolution: > + List every way a customer could pay you (subscription, transaction fee, + licensing, advertising, freemium conversion). Eliminate any model that + conflicts with your value proposition. Test the top candidate with a + pricing page or a direct ask to three prospects: 'Would you pay $X for + this?' Speculation ends when you ask real people. + route_to: "four-ps-marketing" + - point: "Canvas is complete but feels static — unclear what to do next" + resolution: > + Identify the single weakest block on the canvas. That block is your + strategic bottleneck. Design one experiment to strengthen it within 14 + days. A canvas is a diagnostic tool, not a deliverable. + route_to: "evaluating-and-deciding" + if_stuck_checklist: + - "Does every block contain specific facts, or are some filled with aspirations?" + - "Have you validated at least the value proposition and customer segments with real data?" + - "Can you identify the weakest block without hesitation?" + - "Does your cost structure actually support your revenue model at current volume?" + + swot-pest-analysis: + common_sticking_points: + - point: "Everything ends up in the 'Opportunities' quadrant — analysis lacks rigour" + resolution: > + Apply a brutality filter: for every item in Strengths and Opportunities, + ask 'Would a competitor agree this is our advantage?' If not, move it to + Weaknesses or Threats. Have a trusted advisor review the SWOT independently + and compare — divergence reveals blind spots. + route_to: "enemies-of-clear-thinking" + - point: "PEST factors feel too macro to act on" + resolution: > + For each PEST factor, write one sentence starting with 'Therefore, we + should...' If you cannot complete the sentence, the factor is background + noise, not a strategic input. Keep only factors that produce a 'therefore.' + route_to: "scenario-planning" + if_stuck_checklist: + - "Is your Weaknesses quadrant uncomfortably honest, or suspiciously brief?" + - "Have you included at least one threat you genuinely fear?" + - "Does every SWOT item link to a specific action or decision?" + + eisenhower-matrix: + common_sticking_points: + - point: "Everything feels urgent AND important" + resolution: > + Apply a 72-hour test: if you did nothing about this item for 72 hours, + what would actually happen? If the answer is 'nothing irreversible,' it is + not urgent. Strip urgency from items whose consequences are merely + uncomfortable, not catastrophic. + route_to: "focus-and-priority-management" + - point: "The 'delegate' quadrant is empty because there is no one to delegate to" + resolution: > + Reframe 'delegate' as 'automate, outsource, or eliminate.' Can the task + be automated with a tool? Can a freelancer handle it for a one-time fee? + Can it be eliminated entirely without meaningful consequence? Delegation + does not require employees. + route_to: "delegation-and-empowerment" + if_stuck_checklist: + - "Have you applied the 72-hour test to every 'urgent' item?" + - "Are you confusing other people's urgency with your own?" + - "Is the 'not urgent, not important' quadrant empty? If so, you are not being honest." + - "When did you last move an item from Q1 to Q3 or Q4?" + + scenario-planning: + common_sticking_points: + - point: "Cannot generate meaningfully different scenarios — they all look similar" + resolution: > + Use the 2x2 matrix method: identify two critical uncertainties (variables + you cannot predict), place them on axes, and generate four scenarios from + the quadrants. Force at least one scenario to be uncomfortably optimistic + and one to be uncomfortably pessimistic. + route_to: "defining-and-exploring-problems" + - point: "Scenarios are vivid but do not produce different strategic responses" + resolution: > + For each scenario, identify the earliest observable signal that it is + materialising. Define one action you would take only if that signal appears. + This converts scenarios from fiction into a monitoring-and-response system. + route_to: "evaluating-and-deciding" + if_stuck_checklist: + - "Do your scenarios span genuinely different futures, or are they optimistic/pessimistic variations of the same future?" + - "Have you identified trigger signals for each scenario?" + - "Does each scenario produce at least one unique strategic action?" + + # =========================================================================== + # 2. LEADERSHIP (28 skills) + # =========================================================================== + leadership: + general: > + Leadership skill implementation stalls because the change is behavioural, not + analytical. You cannot delegate a leadership shift or automate a difficult + conversation. The most common blockers are avoidance of interpersonal discomfort, + difficulty sustaining new behaviours under stress, and the gap between + understanding a concept and embodying it. + skill_specific: + delegation-and-empowerment: + common_sticking_points: + - point: "Know I should delegate but keep taking tasks back" + resolution: > + Implement a 48-hour rule: after delegating, you may not touch the task + for 48 hours regardless of perceived urgency. Define 'done' criteria + before delegating so you have an objective standard instead of a subjective + feeling. If the result is 80% of what you would produce, it is good enough. + route_to: "stoic-pragmatism" + - point: "No one on the team can do this as well as I can" + resolution: > + This is almost certainly true — and irrelevant. The question is not 'Can + they do it as well?' but 'Can they do it well enough while I focus on + something only I can do?' Document the process, hand it off with the + documentation, and accept the 20% quality dip as the cost of scaling + yourself. + route_to: "focus-and-priority-management" + - point: "Delegation leads to more work because I have to fix everything" + resolution: > + You are delegating tasks, not outcomes. Shift to delegating outcomes: + specify the end state, the constraints, and the deadline — not the method. + Review results at checkpoints, not continuously. If correction is needed + more than twice, the issue is role fit, not delegation technique. + route_to: "hackman-enabling-conditions" + if_stuck_checklist: + - "Have you defined what 'done' looks like before handing off the task?" + - "Are you delegating the method or the outcome?" + - "Have you waited at least 48 hours before intervening?" + - "Is the person you are delegating to clear on the authority you have granted them?" + + emotional-courage: + common_sticking_points: + - point: "Know the difficult conversation needs to happen but keep delaying it" + resolution: > + Schedule the conversation within 72 hours and tell someone you trust that + you have scheduled it. External accountability closes the escape route. + Write the opening sentence in advance — the hardest part is the first ten + seconds. Lead with observation, not judgment: 'I have noticed X' not 'You + always do Y.' + route_to: "radical-candor" + - point: "Had the conversation but pulled punches — did not say the real thing" + resolution: > + Write what you actually needed to say. Read it aloud to yourself. Then + schedule a follow-up: 'I want to revisit our conversation because I do + not think I was fully honest.' Delivered with respect, directness earns + more trust than diplomatic evasion. + route_to: "giving-feedback" + if_stuck_checklist: + - "Have you written down exactly what you need to say?" + - "Is your opening sentence factual and non-accusatory?" + - "Have you set a deadline for the conversation and told someone about it?" + - "Are you avoiding the conversation because of their likely reaction, or your own discomfort?" + + focus-and-priority-management: + common_sticking_points: + - point: "Priorities are clear but daily firefighting consumes all available time" + resolution: > + Block 90 minutes each morning for priority work before opening email or + Slack. Treat the block as a meeting with your most important investor — + because it is. Track for one week how many of the five blocks you protect. + Below three out of five, the problem is boundary enforcement, not + prioritisation. + route_to: "eisenhower-matrix" + - point: "Everything is a priority because the CEO said so" + resolution: > + Present the full list to the CEO with time estimates and ask: 'Which + three of these twelve should be done first?' Forcing a sequencing + conversation is more productive than debating whether things are priorities. + Everything can be important; not everything can be first. + route_to: "managing-up" + if_stuck_checklist: + - "Do you have a protected daily block for your highest-priority work?" + - "Can you state your top three priorities for this week without checking a list?" + - "Did you say 'no' to anything this week? If not, you are not prioritising." + + # =========================================================================== + # 3. WRITING (13 skills) + # =========================================================================== + writing: + general: > + Writing tasks stall because they feel unbounded — a blank page offers infinite + possibilities and therefore infinite procrastination. The most common blockers + are perfectionism (editing while drafting), unclear audience (writing for everyone + and therefore no one), and the misconception that writing requires inspiration + rather than structure. + skill_specific: + writing-with-purpose: + common_sticking_points: + - point: "Cannot start because unsure of the right angle or framing" + resolution: > + Write the last sentence first — what do you want the reader to think, feel, + or do after reading? Work backwards from that sentence. The angle reveals + itself when you know the destination. + route_to: "reader-psychology" + - point: "Draft is complete but feels unfocused — says too many things" + resolution: > + Apply the 'one idea per piece' rule. Identify the single most important + point. Delete or move to a separate document every paragraph that does not + support that point. Breadth is the enemy of impact. + route_to: "revising-and-editing" + if_stuck_checklist: + - "Can you state the purpose of this document in one sentence?" + - "Do you know exactly who will read it and what they need from it?" + - "Have you separated drafting from editing — or are you doing both simultaneously?" + + clarity-and-concision: + common_sticking_points: + - point: "Feedback says the writing is 'unclear' but cannot identify why" + resolution: > + Read every sentence aloud. If you stumble or run out of breath, the + sentence is too long or too complex. Split it. Then check: does each + paragraph begin with the point, followed by evidence? If evidence comes + first, reverse the order. + route_to: "plain-language-and-flow" + - point: "The document is too long but everything feels essential" + resolution: > + Apply the 50% challenge: cut the document to half its current length. + This is not a target — it is a forcing function. When you must cut half, + you discover what is truly essential versus what merely feels important. + Restore only what the reader genuinely needs. + route_to: "revising-and-editing" + if_stuck_checklist: + - "Is any sentence longer than 25 words? If so, can it be split?" + - "Does every paragraph earn its place, or are some there because they were hard to write?" + - "Have you read the document from the reader's perspective, not the writer's?" + + # =========================================================================== + # 4. AI LEADERSHIP (9 skills) + # =========================================================================== + ai-leadership: + general: > + AI implementation stalls because the technology moves faster than organisational + readiness. Common blockers are analysis paralysis on tool selection (the landscape + changes monthly), resistance from team members who perceive AI as a threat, and + the gap between pilot success and production deployment. + skill_specific: + ai-vision-and-strategy: + common_sticking_points: + - point: "Cannot define an AI strategy because the technology keeps changing" + resolution: > + Stop trying to predict the technology. Define your strategy around business + problems worth solving, not tools to adopt. List your three most expensive + or time-consuming processes. For each, ask: 'Could AI reduce cost or time + by 30%+?' Start there. The strategy is problem-first, tool-second. + route_to: "defining-and-exploring-problems" + - point: "Strategy exists on paper but no one is executing it" + resolution: > + Assign one AI initiative to one person with a 30-day deliverable. A + strategy without a named owner and a deadline is a wish. Make the first + project small enough to succeed and visible enough to build momentum. + route_to: "delegation-and-empowerment" + if_stuck_checklist: + - "Is your strategy defined around business problems or around technology capabilities?" + - "Does every AI initiative have a named owner and a deadline?" + - "Have you started with a pilot small enough to complete in 30 days?" + + ai-augmentation-not-automation: + common_sticking_points: + - point: "Team resists AI tools because they fear job replacement" + resolution: > + Reframe from 'AI will do your job' to 'AI will handle the parts of your + job you dislike.' Have each team member list their three most tedious + recurring tasks. Pilot AI automation on those tasks specifically. When + people experience AI as removing drudgery rather than removing them, + resistance drops. + route_to: "ai-communication-culture" + - point: "AI pilot succeeded but scaling to production fails" + resolution: > + Pilots succeed because they have a champion. Production fails because it + needs a process. Document the pilot workflow, identify every manual step + that the champion currently performs, and either automate or assign each. + The scaling gap is almost always an operations gap, not a technology gap. + route_to: "ai-human-centered-approach" + if_stuck_checklist: + - "Have you separated tasks AI should augment from tasks AI should automate?" + - "Does the team understand how AI changes their role versus replaces it?" + - "Is there a documented process for moving from pilot to production?" + + # =========================================================================== + # 5. GAME THEORY (7 skills) + # =========================================================================== + game-theory: + general: > + Game theory implementation stalls because the models feel academic. Entrepreneurs + understand the concept of Nash equilibria or prisoner's dilemmas intellectually + but struggle to map them onto real competitive or negotiation situations. The + bridge from theory to practice requires identifying the specific game being played, + the actual payoff structure, and the other players' likely strategies. + skill_specific: + prisoners-dilemma-and-cooperation: + common_sticking_points: + - point: "Cannot determine whether a business situation is actually a prisoner's dilemma" + resolution: > + Ask two questions: (1) Would both parties benefit from cooperation? (2) Can + either party benefit more by defecting while the other cooperates? If both + answers are yes, you are in a prisoner's dilemma. Common examples: pricing + wars, exclusive partnership commitments, information sharing with potential + acquirers. + route_to: "negotiation-game-theory" + - point: "Identified the dilemma but cannot determine the right strategy" + resolution: > + In repeated interactions (ongoing business relationships), tit-for-tat + with forgiveness outperforms all other strategies. Start cooperative. + Mirror the other party's last move. Occasionally forgive a defection to + prevent death spirals. In one-shot interactions, protect your downside + first. + route_to: "cooperative-negotiation" + if_stuck_checklist: + - "Have you mapped the actual payoffs for cooperation and defection for both parties?" + - "Is this a one-shot game or a repeated game? The optimal strategy differs fundamentally." + - "Can you signal your cooperative intent credibly before the other party must decide?" + + information-asymmetry: + common_sticking_points: + - point: "Suspect the other party has information I lack but cannot identify what" + resolution: > + List every assumption underlying your position. For each, ask: 'Does the + other party know whether this assumption is true?' Any assumption where + they know and you do not is an information asymmetry. Then ask: 'What + questions would I need answered to eliminate this gap?' Those questions + are your preparation agenda. + route_to: "negotiation-mindset-and-self" + - point: "Have superior information but unsure whether to reveal it" + resolution: > + Revealing information builds trust in repeated games and is cheap when + the information will become public eventually. Conceal information only + when (1) the interaction is one-shot, (2) the information provides a + durable advantage, and (3) the ethical cost of concealment is acceptable. + route_to: "competitive-negotiation" + if_stuck_checklist: + - "Have you identified which party holds the information advantage in this situation?" + - "Can you reduce the asymmetry through direct questions rather than inference?" + - "Is the other party's behaviour consistent with them knowing something you do not?" + + # =========================================================================== + # 6. STOIC (12 skills) + # =========================================================================== + stoic: + general: > + Stoic skill implementation stalls because intellectual agreement is far easier than + behavioural change. An entrepreneur can understand the dichotomy of control + perfectly and still lose sleep over a competitor's funding round. The gap between + knowing and living Stoic principles is the entire challenge. + skill_specific: + stoic-control-and-clarity: + common_sticking_points: + - point: "Intellectually accept what is outside my control but emotionally cannot let go" + resolution: > + Write three columns on paper: 'Within my control,' 'Within my influence,' + 'Outside my control.' Place the specific concern in the correct column. + Then write one concrete action for each item in the first two columns and + draw a line through every item in the third. The physical act of crossing + out externalises the release. + route_to: "stoic-emotional-mastery" + - point: "Cannot distinguish between influence and control" + resolution: > + Control means the outcome depends entirely on your action. Influence means + your action changes the probability but not the certainty. Test: 'If I + do X perfectly, is the outcome guaranteed?' Yes = control. No = influence. + Direct energy proportionally — full effort on control, calibrated effort + on influence, zero effort on the uncontrollable. + route_to: "stoic-self-awareness" + if_stuck_checklist: + - "Have you done the three-column exercise on paper, not just in your head?" + - "Are you spending energy on items in the 'outside my control' column?" + - "Have you identified at least one action for every item you CAN control?" + + stoic-pragmatism: + common_sticking_points: + - point: "Perfectionism persists despite understanding that 'good enough' is rational" + resolution: > + Set a timer for the task. When the timer ends, ship what exists. Perfection + is not a quality standard — it is a delay mechanism disguised as diligence. + Ask: 'What is the cost of shipping this at 80% versus the cost of the + additional time to reach 95%?' The answer is almost always that the + marginal improvement is not worth the marginal delay. + route_to: "choosing-and-executing" + - point: "Stoic pragmatism feels like lowering standards" + resolution: > + Pragmatism is not about lowering the bar. It is about recognising that + speed of iteration beats quality of first attempt. Ship, measure, improve. + The entrepreneur who ships ten 80%-quality iterations learns more than the + one who ships one 99%-quality version. + route_to: "creative-completion-and-renewal" + if_stuck_checklist: + - "Are you conflating perfectionism with high standards?" + - "Have you defined a 'minimum viable' version of the deliverable?" + - "What specifically would happen if you shipped the current version today?" + + # =========================================================================== + # 7. STORYTELLING (8 skills) + # =========================================================================== + storytelling: + general: > + Storytelling implementation stalls because entrepreneurs conflate storytelling with + public speaking and freeze. The blocker is rarely technique — it is vulnerability. + Effective stories require personal truth, and personal truth requires the courage + to be seen. Alternatively, the entrepreneur has stories but cannot identify which + ones are strategically useful. + skill_specific: + finding-your-stories: + common_sticking_points: + - point: "Believe 'nothing interesting has happened to me'" + resolution: > + Interesting stories do not require extraordinary events. List five moments + in the last year when you changed your mind about something. Each change + of mind is a story: what you believed before, what happened, what you + believe now. Transformation, not spectacle, drives narrative power. + route_to: "story-structure-and-arc" + - point: "Have stories but they feel irrelevant to business contexts" + resolution: > + Every personal story maps to a business theme if you identify the + principle. A story about learning to cook under pressure becomes a story + about resourcefulness. A story about a family disagreement becomes a story + about navigating conflict. Extract the principle first, then select the + story that illustrates it. + route_to: "building-story-stakes" + if_stuck_checklist: + - "Have you listed at least five moments where you changed your mind about something?" + - "For each story, can you state the business principle it illustrates?" + - "Are you avoiding stories because they feel too personal, or because they genuinely lack relevance?" + + story-performance-and-delivery: + common_sticking_points: + - point: "Write good stories but freeze when delivering them aloud" + resolution: > + Record yourself telling the story to a phone, alone, three times. Listen + to each recording. By the third attempt, the freeze reflex weakens because + the story becomes familiar in your mouth, not just your head. Perform for + one trusted person before any public delivery. + route_to: "leadership-voice-and-presence" + if_stuck_checklist: + - "Have you practised the story aloud at least three times?" + - "Have you delivered it to one person before attempting a group?" + - "Are you trying to recite memorised text, or telling the story from memory of the experience?" + + # =========================================================================== + # 8. NEGOTIATION (4 skills) + # =========================================================================== + negotiation: + general: > + Negotiation implementation stalls because preparation is where the work lives, and + most entrepreneurs skip it. They walk into negotiations with a desired outcome but + no BATNA, no understanding of the other party's constraints, and no prepared + concession strategy. When they stall on implementing negotiation frameworks, the + blocker is almost always insufficient preparation or conflict avoidance. + skill_specific: + cooperative-negotiation: + common_sticking_points: + - point: "Want to negotiate cooperatively but the other party is aggressive" + resolution: > + Cooperative negotiation does not require both parties to be cooperative. + Name the dynamic: 'I notice we are approaching this differently. I would + like to find something that works for both of us.' Then ask interest-based + questions: 'What would a good outcome look like from your perspective?' + If they remain aggressive, protect your BATNA and do not concede under + pressure. + route_to: "competitive-negotiation" + - point: "Cannot identify shared interests — the negotiation feels purely distributive" + resolution: > + Expand the pie before dividing it. Ask: 'Are there items I value highly + that cost the other party little to give?' and vice versa. Payment terms, + exclusivity windows, referral commitments, and timeline flexibility are + common non-monetary currencies that create mutual value. + route_to: "delivering-the-deal" + if_stuck_checklist: + - "Have you prepared your BATNA before entering the negotiation?" + - "Can you articulate the other party's interests, not just your own?" + - "Have you identified at least two non-monetary items you could trade?" + - "Do you know your walk-away point?" + + negotiation-mindset-and-self: + common_sticking_points: + - point: "Anxiety prevents thinking clearly during the negotiation" + resolution: > + Prepare a written negotiation plan with three scenarios: best case, likely + case, and walk-away. Having the plan on paper means your anxious brain + does not need to hold the structure. Take the paper into the negotiation. + Pause before responding to any significant offer — 'Let me consider that' + is always acceptable. + route_to: "stoic-emotional-mastery" + - point: "Concede too quickly because discomfort with silence or tension" + resolution: > + Practise sitting in silence for ten seconds after making a proposal. Count + in your head. The other party's discomfort with your silence is your + leverage. Concessions made to relieve your own tension are gifts, not + negotiations. + route_to: "emotional-courage" + if_stuck_checklist: + - "Do you have a written plan with three scenarios before entering any negotiation?" + - "Have you practised your opening position aloud?" + - "Can you sit in silence for ten seconds without speaking?" + + # =========================================================================== + # 9. PEOPLE (8 skills) + # =========================================================================== + people: + general: > + People skill implementation stalls because interpersonal change is slow and + feedback is ambiguous. Unlike a financial model, you cannot test a relationship + improvement in a spreadsheet. The most common blocker is trying to change others + rather than changing your own behaviour first — the only variable you actually + control. + skill_specific: + connecting-with-people: + common_sticking_points: + - point: "Understand networking concepts but cannot initiate conversations naturally" + resolution: > + Prepare three open-ended questions that work in any context: 'What are you + working on that excites you?', 'What brought you here today?', 'What is + the most interesting problem you are solving right now?' Use one. Listen to + the answer. Ask a follow-up based on what they said, not on your prepared + list. Connection starts with curiosity, not charisma. + route_to: "reading-people" + - point: "Make initial connections but fail to maintain them" + resolution: > + Implement a 48-hour follow-up rule: within 48 hours of meeting someone + worth knowing, send a specific message referencing something from your + conversation. Set a quarterly calendar reminder to reach out to your top + 20 contacts with a relevant article, introduction, or genuine question. + Relationships decay without maintenance. + route_to: "meeting-the-right-people" + if_stuck_checklist: + - "Do you have three ready-to-use conversation starters that you have practised?" + - "Did you follow up within 48 hours of your last meaningful new connection?" + - "Are you trying to 'network' or trying to genuinely learn about someone?" + + resolving-people-conflict: + common_sticking_points: + - point: "Avoid the conflict entirely and hope it resolves itself" + resolution: > + Unaddressed conflict never resolves — it metastasises. Set a 7-day rule: + if a conflict persists for 7 days without improvement, you must initiate + a conversation. Use the format: 'I have noticed [specific behaviour]. The + impact is [concrete effect]. I would like to find a way forward. Can we + talk?' Naming the conflict reduces it. + route_to: "emotional-courage" + - point: "Addressed the conflict but the other party became defensive" + resolution: > + Defensive reactions are normal in the first five minutes. Do not match + defensiveness with escalation. Acknowledge their perspective: 'I hear + that you see it differently.' Then restate the impact on you without + blaming: 'From my side, the effect has been X.' Give them 24 hours + to process before expecting resolution. + route_to: "thomas-kilmann-conflict" + if_stuck_checklist: + - "Have you separated the person from the behaviour in your own mind?" + - "Can you state the conflict in terms of impact rather than blame?" + - "Are you avoiding the conversation because resolution is impossible, or because it is uncomfortable?" + + # =========================================================================== + # 10. CREATIVE (8 skills) + # =========================================================================== + creative: + general: > + Creative skill implementation stalls at two predictable points: starting (the blank + page) and finishing (the final 10% where judgment replaces exploration). The + blocker for starting is almost always a disguised fear of producing something bad. + The blocker for finishing is almost always perfectionism or loss of novelty — the + work stops being exciting and starts being labour. + skill_specific: + creative-completion-and-renewal: + common_sticking_points: + - point: "Projects reach 80% and then stall — cannot push through the final stretch" + resolution: > + The last 20% is not creative work — it is editorial work. Accept this + transition explicitly. Set a completion deadline and define 'done' as a + specific deliverable state, not a quality threshold. Ship at 90% and + iterate rather than polishing to 100% in isolation. + route_to: "stoic-pragmatism" + - point: "Start many projects but finish few" + resolution: > + Implement a one-in, one-out rule: you may not start a new project until + you complete, abandon, or formally defer one existing project. Track your + completion rate. If it is below 50%, the problem is not the projects — it + is the pattern. + route_to: "focus-and-priority-management" + if_stuck_checklist: + - "Have you defined what 'done' looks like for this specific project?" + - "Is the remaining work creative or editorial? Do you need inspiration or discipline?" + - "Would someone other than you consider this project complete?" + + creative-obstacles: + common_sticking_points: + - point: "Creative block — cannot generate ideas" + resolution: > + Stop trying to generate good ideas. Generate 20 bad ideas in 15 minutes. + Write them down without judgment. Quantity produces quality because it + bypasses the inner critic. Review the list after a break — typically two + or three of the 'bad' ideas contain a usable kernel. + route_to: "creative-flow-and-inspiration" + - point: "Generating ideas but they all feel derivative" + resolution: > + Combine two unrelated inputs: a constraint from your industry and an idea + from a completely different field. Derivative ideas come from looking where + everyone else looks. Novel ideas come from importing solutions across + domain boundaries. + route_to: "creative-perception-and-awareness" + if_stuck_checklist: + - "Have you produced at least 20 ideas without filtering?" + - "Are you judging ideas while generating them, or separating the two phases?" + - "Have you sought input from someone outside your industry?" + + # =========================================================================== + # 11. THINKING (6 skills) + # =========================================================================== + thinking: + general: > + Thinking skill implementation stalls because the skills are meta-cognitive — + thinking about thinking. The entrepreneur understands the biases, the frameworks, + the traps, yet falls into them anyway under pressure. Implementation requires + building triggers: specific moments where you pause and apply the framework before + your default thinking takes over. + skill_specific: + enemies-of-clear-thinking: + common_sticking_points: + - point: "Can identify biases in others but not in yourself" + resolution: > + Create a personal bias inventory: review your last five significant + decisions and identify which default (emotion, ego, social, inertia) most + influenced each. The pattern that emerges is your dominant bias. Build a + pre-decision checklist that specifically addresses that bias. External + review from a trusted advisor accelerates this — they see what you cannot. + route_to: "stoic-self-awareness" + - point: "Know the bias but cannot override it in the moment" + resolution: > + You cannot override a bias in real time through willpower. You override it + through structure: a written checklist consulted before every significant + decision, a mandatory 24-hour delay on decisions above a certain + threshold, or a designated devil's advocate who is authorised to challenge. + route_to: "decision-traps-and-roles" + if_stuck_checklist: + - "Have you identified your personal dominant bias from past decisions?" + - "Do you have a structural check (not a mental note) to catch it?" + - "When was the last time you changed your mind about something important?" + + defining-and-exploring-problems: + common_sticking_points: + - point: "Keep solving the wrong problem — solutions do not address the root cause" + resolution: > + Apply the five-whys technique. State the problem, then ask 'Why?' five + times, each time going deeper. Most entrepreneurs stop at the second why. + The root cause typically lives at why number four or five. Write each level + down — the discipline of writing prevents premature convergence. + route_to: "evaluating-and-deciding" + - point: "Problem definition keeps shifting — cannot stabilise what we are solving" + resolution: > + Write the problem statement in one sentence, present tense, using this + format: '[Specific group] cannot [specific action] because [specific + barrier].' If you cannot complete this sentence, you do not yet understand + the problem well enough to solve it. Circulate the statement to three + stakeholders and refine based on disagreement. + route_to: "generating-solutions" + if_stuck_checklist: + - "Can you state the problem in one sentence?" + - "Have you applied the five-whys to reach the root cause?" + - "Would three different stakeholders agree on your problem definition?" + + # =========================================================================== + # 12. DECISIONS (5 skills) + # =========================================================================== + decisions: + general: > + Decision skill implementation stalls because making better decisions requires + slowing down at the moment when urgency screams to speed up. The most common + blocker is the false belief that faster decisions are better decisions. The second + most common blocker is never revisiting past decisions to calibrate judgment. + skill_specific: + evaluating-options: + common_sticking_points: + - point: "Have too many options and cannot narrow the field" + resolution: > + Apply elimination criteria before evaluation criteria. Define three + non-negotiable requirements. Eliminate every option that fails any one of + them. This typically reduces the field by 60-80%. Only then apply weighted + scoring to the survivors. + route_to: "evaluating-and-deciding" + - point: "Weighted scoring produces a winner but it does not feel right" + resolution: > + The feeling is data. Ask: 'What does my gut know that my spreadsheet does + not?' Often the discomfort points to a criterion you weighted too low or + omitted entirely. Add the missing criterion, re-score, and check whether + the feeling resolves. If it persists, examine whether fear — not analysis + — is the true obstacle. + route_to: "enemies-of-clear-thinking" + if_stuck_checklist: + - "Have you defined elimination criteria before evaluation criteria?" + - "Does your scoring include all the factors that actually matter to you?" + - "If your gut disagrees with the analysis, have you investigated why?" + + tough-decision-situations: + common_sticking_points: + - point: "The decision has been pending for over a month" + resolution: > + Calculate the cost of delay: revenue lost, opportunities missed, team + morale eroded, personal energy consumed by the unresolved decision. This + cost is real and cumulative. If the cost of delay exceeds the risk + differential between the best and second-best option, decide now. A + good decision made today outperforms a perfect decision made in six weeks. + route_to: "choosing-and-executing" + - point: "Multiple stakeholders disagree and expect consensus" + resolution: > + Consensus is not always achievable or desirable. Clarify decision rights: + who decides, who is consulted, who is informed. Use the RAPID framework + (Recommend, Agree, Perform, Input, Decide) to assign roles explicitly. + The person with the 'D' makes the call after hearing all inputs. + route_to: "decision-traps-and-roles" + if_stuck_checklist: + - "Have you calculated the concrete cost of continued delay?" + - "Are decision rights clear — does everyone know who makes the final call?" + - "Is the delay driven by missing information or by conflict avoidance?" + - "Have you set a decision deadline and communicated it to all parties?" + + # =========================================================================== + # 13. CROSS-CATEGORY: STOIC MODE INTEGRATION + # =========================================================================== + stoic_mode_overlay: + description: > + When Stoic mode is active, every stuck protocol gains an additional reflection + layer. These questions supplement the category-specific checklists. + universal_stoic_questions: + - "Is this blocker within your control, within your influence, or outside both? Are you directing energy proportionally?" + - "What would you advise a friend facing this exact blocker? Apply that advice to yourself." + - "Which Stoic virtue is this situation testing — wisdom, courage, temperance, or justice?" + - "If this blocker persists for six months, will it matter? If not, act now. If so, plan carefully." + - "Are you choosing comfort over progress? Name the comfort you are protecting." + + # =========================================================================== + # 14. CROSS-CATEGORY: SOLO MODE INTEGRATION + # =========================================================================== + solo_mode_overlay: + description: > + When Solo mode is active, stuck protocols adapt for the solopreneur's unique + constraints: no team to delegate to, no colleagues to brainstorm with, and the + compounding effect of being blocked on every front simultaneously. + universal_solo_additions: + - question: "Are you stuck because this task requires a skill you do not have and cannot delegate?" + resolution: > + Solopreneurs cannot be experts in everything. For tasks outside your core + competency, the decision is: learn (if recurring), outsource (if one-time), + or eliminate (if the value does not justify the effort). Make this decision + explicitly rather than stalling indefinitely. + - question: "Are you stuck because you have no one to think through this problem with?" + resolution: > + Isolation amplifies every blocker. Options: find a peer mastermind group + (free), hire a coach for one session (focused spend), post in a relevant + online community with a specific question (free), or use Foreman's diagnostic + system as a structured thinking partner. + - question: "Are you stuck on everything at once?" + resolution: > + When all items stall simultaneously, the problem is not the items — it is + your capacity. Reduce active items to three. Complete one before adding + another. Momentum on a single item breaks the paralysis across all of them. diff --git a/plugins/foreman/content/implementation/templates/blocker-analysis.md b/plugins/foreman/content/implementation/templates/blocker-analysis.md new file mode 100644 index 0000000..4a44359 --- /dev/null +++ b/plugins/foreman/content/implementation/templates/blocker-analysis.md @@ -0,0 +1,171 @@ +--- +name: "blocker-analysis" +description: "Produces a structured root-cause analysis of one or more blockers + preventing implementation progress. Goes beyond surface identification to + apply the five-whys technique, assess downstream impact, recommend specific + resolution paths through the Foreman system, and define escalation triggers. + Use when a blocker persists beyond one check-in cycle or when multiple + blockers share a common root cause that warrants deeper investigation." +audience: "self" +applicable_skills: + - evaluating-and-deciding + - scenario-planning + - eisenhower-matrix + - stoic-emotional-mastery + - stoic-control-and-clarity +format: "analysis" +author: "Fatih Guner" +related_content: + - kind: template + ref: stakeholder-map +--- + +# Blocker Analysis + + + +**Analysis date:** [YYYY-MM-DD] | **Analyst:** [Name] + +**Scope:** [Single blocker: blk-XXX | All blockers | Category: resource/knowledge/dependency/motivation/external] + +--- + +## Blocker Description + + + +| Field | Detail | +|-------|--------| +| Blocker ID | [blk-XXX] | +| Affected item(s) | [impl-XXX: description] | +| Category | [resource / knowledge / dependency / motivation / external] | +| First identified | [date] | +| Days active | [N] | +| Current status of affected item(s) | [blocked at N%] | +| Stated blocker | [The entrepreneur's description of what is blocking progress] | + +--- + +## Root Cause Analysis (Five Whys) + + + +| Level | Question | Answer | +|-------|----------|--------| +| **Why 1** | Why is [item] blocked? | [First-level answer: the surface reason] | +| **Why 2** | Why is [answer 1] the case? | [Second-level: one layer deeper] | +| **Why 3** | Why is [answer 2] the case? | [Third-level: structural cause emerging] | +| **Why 4** | Why is [answer 3] the case? | [Fourth-level: root cause territory] | +| **Why 5** | Why is [answer 4] the case? | [Fifth-level: fundamental constraint or decision] | + +**Root cause identified:** [One sentence summarizing the deepest cause] + +**Root cause category:** [Same as or different from original blocker category -- the five whys may reveal that a "dependency" blocker is actually a "motivation" blocker at root] + +--- + +## Impact Assessment + + + +### Direct Impact + +| Affected item | Current progress | Deadline | Delay if unresolved | +|---------------|-----------------|----------|---------------------| +| [impl-XXX] | [N]% | [date] | [Estimated additional days/weeks] | + +### Downstream Impact + + + +| Downstream item | Dependency type | Impact if blocker persists | +|----------------|-----------------|---------------------------| +| [impl-XXX: description] | [Requires output of blocked item / Shares resource / Sequential dependency] | [What happens: delayed, degraded, or impossible] | + +### Strategic Impact + + + +[One to three sentences on the strategic consequence. Example: "This blocker delays the entire pivot-playbook execution by an estimated 2 weeks, pushing the B2B launch past the industry conference where first customers were expected to be acquired."] + +--- + +## Resolution Path + + + +### Option A: [Primary resolution approach] + +| Step | Action | Tool/Route | Timeline | +|------|--------|------------|----------| +| 1 | [First action] | [/diagnose X or /apply Y or external action] | [Estimated time] | +| 2 | [Second action] | [Tool or route] | [Estimated time] | +| 3 | [Third action] | [Tool or route] | [Estimated time] | + +**Probability of success:** [High / Medium / Low] +**Time to resolution:** [Estimated days] + +### Option B: [Alternative resolution approach] + +| Step | Action | Tool/Route | Timeline | +|------|--------|------------|----------| +| 1 | [First action] | [Tool or route] | [Estimated time] | +| 2 | [Second action] | [Tool or route] | [Estimated time] | + +**Probability of success:** [High / Medium / Low] +**Time to resolution:** [Estimated days] + +### Option C: Accept and Adapt + + + +[Describe what changes if the blocker is accepted as permanent. Which items are abandoned, which are restructured, and what is the revised implementation plan?] + +--- + +## Escalation Triggers + + + +| Trigger | Condition | Escalation action | +|---------|-----------|-------------------| +| Time-based | Blocker persists beyond [N] more days | [Switch to Option B / Abandon item / Restructure plan] | +| Cost-based | Resolution cost exceeds [threshold] | [Reassess ROI of the blocked item] | +| Cascade | [N] additional items become blocked by same root cause | [Escalate to strategic reassessment via /diagnose strategy] | +| Opportunity | [Specific event] occurs that changes the calculus | [Reassess whether the blocked item is still relevant] | + +--- + +## Dichotomy of Control + + + +| Within your control | Within your influence | Outside your control | +|--------------------|-----------------------|---------------------| +| [Actions you can take unilaterally] | [Outcomes you can affect but not guarantee] | [Factors you must accept or work around] | + +**Recommended focus:** [Where to direct energy based on this separation] + +--- + +**Analysis outcome:** [Pursuing Option A / Pursuing Option B / Accepting and adapting / Requires further investigation] + +**Next review date:** [When to reassess if the blocker has not resolved] diff --git a/plugins/foreman/content/implementation/templates/implementation-dashboard.md b/plugins/foreman/content/implementation/templates/implementation-dashboard.md new file mode 100644 index 0000000..63b2118 --- /dev/null +++ b/plugins/foreman/content/implementation/templates/implementation-dashboard.md @@ -0,0 +1,132 @@ +--- +name: "implementation-dashboard" +description: "Produces a point-in-time snapshot of all implementation items across the tracking system. Displays summary statistics, status distribution, overdue items, blocker analysis by category, and completion velocity trends. Designed for the entrepreneur's own use as a weekly or on-demand accountability mirror -- the single document that answers 'Am I actually executing on what I know I should do?'" +audience: "self" +applicable_skills: + - balanced-scorecard + - smart-goals + - focus-and-priority-management + - eisenhower-matrix +format: "dashboard" +author: "Fatih Guner" +--- + +# Implementation Dashboard + + + +**Snapshot date:** [YYYY-MM-DD] | **Last check-in:** [YYYY-MM-DD] | **Tracking since:** [YYYY-MM-DD] + +--- + +## Summary + +| Metric | Value | +|--------|-------| +| Total items tracked | [N] | +| Completed | [N] ([X]%) | +| In progress | [N] | +| Blocked | [N] | +| Not started | [N] | +| Deferred | [N] | +| Abandoned | [N] | +| Overdue | [N] | +| Stalled (14+ days no movement) | [N] | + +**Execution rate:** [X]% of all items produced have reached completion. + +**Health signal:** [On track / Attention needed / Execution gap widening] + + + +--- + +## Items by Status + + + +| ID | Description | Status | Progress | Deadline | Days remaining | Source | +|----|-------------|--------|----------|----------|----------------|--------| +| [impl-XXX] | [Description] | [status] | [N]% | [date] | [N] | [playbook/skill/diagnostic ref] | +| [impl-XXX] | [Description] | [status] | [N]% | [date] | [N] | [source ref] | +| [impl-XXX] | [Description] | [status] | [N]% | [date] | [N] | [source ref] | + +--- + +## Overdue Items + + + +| ID | Description | Progress | Deadline | Days overdue | Blocker | +|----|-------------|----------|----------|--------------|---------| +| [impl-XXX] | [Description] | [N]% | [date] | [N] | [Blocker description or "None -- execution lag"] | + +**Overdue trend:** [Improving / Stable / Worsening] -- [N] overdue last week vs. [N] this week. + +--- + +## Blocker Distribution + + + +| Category | Count | Items affected | Suggested system response | +|----------|-------|----------------|---------------------------| +| Resource | [N] | [impl-XXX, impl-XXX] | [/diagnose operations or /apply resource-allocation] | +| Knowledge | [N] | [impl-XXX] | [Route to originating skill for deeper application] | +| Dependency | [N] | [impl-XXX] | [/apply stakeholder-map or escalation path] | +| Motivation | [N] | [impl-XXX] | [/apply stoic-emotional-mastery or break into sub-tasks] | +| External | [N] | [impl-XXX] | [/apply scenario-planning or /apply swot-pest-analysis] | + +**Dominant blocker type:** [Category] ([N] of [total] blockers) + +**Pattern note:** [Observation about blocker distribution -- e.g., "3 of 4 blockers are dependency-type, suggesting the execution plan relies too heavily on external parties."] + +--- + +## Velocity Trend + + + +| Week | Items completed | Items created | Net change | Cumulative completion rate | +|------|----------------|---------------|------------|---------------------------| +| [Week ending date] | [N] | [N] | [+/-N] | [X]% | +| [Week ending date] | [N] | [N] | [+/-N] | [X]% | +| [Week ending date] | [N] | [N] | [+/-N] | [X]% | +| [Week ending date] | [N] | [N] | [+/-N] | [X]% | + +**Average velocity:** [N] items completed per week + +**Average time to completion:** [N] days from creation to completed status + +**Velocity direction:** [Accelerating / Steady / Decelerating] + +--- + +## This Week's Focus + + + +1. **[impl-XXX]** -- [Description] | Due: [date] | Current: [N]% | Why: [reason this is priority] +2. **[impl-XXX]** -- [Description] | Due: [date] | Current: [N]% | Why: [reason] +3. **[impl-XXX]** -- [Description] | Due: [date] | Current: [N]% | Why: [reason] + +--- + +**Dashboard #:** [Sequential number] | **Next check-in due:** [date] diff --git a/plugins/foreman/content/implementation/templates/weekly-progress-report.md b/plugins/foreman/content/implementation/templates/weekly-progress-report.md new file mode 100644 index 0000000..69c9f69 --- /dev/null +++ b/plugins/foreman/content/implementation/templates/weekly-progress-report.md @@ -0,0 +1,123 @@ +--- +name: "weekly-progress-report" +description: "Produces a concise weekly implementation report summarizing what moved, what completed, what stalled, and what comes next. Unlike the implementation dashboard (which is a snapshot of current state), this report captures the delta -- the change between this week and last. Designed for the entrepreneur's own accountability record and, optionally, for sharing with advisors or accountability partners who want a structured view of execution progress." +audience: "self" +applicable_skills: + - smart-goals + - focus-and-priority-management + - balanced-scorecard +format: "report" +author: "Fatih Guner" +--- + +# Weekly Implementation Progress Report + + + +**Week of:** [MM/DD/YYYY -- MM/DD/YYYY] | **Report #:** [Sequential number] + +**Prepared by:** [Name] | **Check-in date:** [Date of /check-in] + +--- + +## Week Summary + + + +[Narrative summary of this week's implementation progress. What moved forward, what did not, and the primary reason for each. State the overall execution tempo -- accelerating, steady, or decelerating -- and the single biggest factor driving it.] + +--- + +## Items Progressed This Week + + + +| ID | Description | Progress last week | Progress now | Delta | Note | +|----|-------------|-------------------|--------------|-------|------| +| [impl-XXX] | [Description] | [N]% | [N]% | +[N]% | [What changed] | +| [impl-XXX] | [Description] | [N]% | [N]% | +[N]% | [What changed] | +| [impl-XXX] | [Description] | [N]% | [N]% | +[N]% | [What changed] | + +**Total items with progress this week:** [N] of [N] active items + +--- + +## Items Completed + + + +| ID | Description | Outcome | Days to complete | Source | +|----|-------------|---------|------------------|--------| +| [impl-XXX] | [Description] | [What the implementation produced] | [N] | [playbook/skill ref] | + +**Cumulative completion rate:** [X]% ([N] completed of [N] total ever tracked) + +--- + +## New Blockers Surfaced + + + +| ID | Item | Category | Blocker description | Suggested route | +|----|------|----------|---------------------|-----------------| +| [blk-XXX] | [impl-XXX: description] | [category] | [What is blocking progress] | [Diagnostic, skill, or action recommended] | + +--- + +## Blockers Resolved + + + +| ID | Item | Category | Resolution | Days blocked | +|----|------|----------|------------|--------------| +| [blk-XXX] | [impl-XXX: description] | [category] | [How it was resolved] | [N] | + +--- + +## Items at Risk + + + +| ID | Description | Risk type | Progress | Deadline | Assessment | +|----|-------------|-----------|----------|----------|------------| +| [impl-XXX] | [Description] | [Stalled / Overdue / Trajectory miss] | [N]% | [date] | [Why this is at risk and what would change it] | + +**Action required:** [Specific next step for each at-risk item -- renegotiate deadline, break into smaller tasks, escalate blocker, or decide to abandon.] + +--- + +## Next Week Priorities + + + +1. **[impl-XXX]** -- [Description] + Target: [Current]% --> [Target]% by [date] + Key action: [The specific thing that must happen to reach the target] + +2. **[impl-XXX]** -- [Description] + Target: [Current]% --> [Target]% by [date] + Key action: [Specific action] + +3. **[impl-XXX]** -- [Description] + Target: [Current]% --> [Target]% by [date] + Key action: [Specific action] + +--- + +**Execution tempo this week:** [Accelerating / Steady / Decelerating / Stalled] + +**Biggest win:** [One sentence] + +**Biggest concern:** [One sentence] diff --git a/plugins/foreman/content/industry-packs/_schema/industry-pack-template.yaml b/plugins/foreman/content/industry-packs/_schema/industry-pack-template.yaml new file mode 100644 index 0000000..0aa99d0 --- /dev/null +++ b/plugins/foreman/content/industry-packs/_schema/industry-pack-template.yaml @@ -0,0 +1,197 @@ +# Industry Pack Schema — Template for All Sector Packs +# +# An industry pack is an OVERLAY that adds sector-specific depth to Foreman's +# existing skills, diagnostics, playbooks, and output templates. It does not +# modify the base content. The orchestrator reads memory.company.sector, loads +# the matching pack, and applies it as a contextual lens. +# +# Directory structure: +# .claude/industry-packs/ +# _schema/ +# industry-pack-template.yaml <-- This file +# {sector}/ +# {sector}-benchmarks.yaml <-- Sector-specific metrics and benchmarks +# {sector}-skill-overlays.yaml <-- Contextual overlays for relevant skills +# {sector}-diagnostic-rules.yaml <-- Adapted diagnostic triage for the sector +# {sector}-templates.yaml <-- Output template field adaptations +# +# Activation: +# The pack activates when memory.company.sector matches the directory name. +# Multiple packs can coexist; only the matching one is loaded per session. +# Packs compose with Solo Mode, Stoic Mode, and Language Mode — they occupy +# a separate axis (what industry) vs. those modes (what audience, what lens, +# what language). +# +# Design principles: +# 1. Overlay, not override — packs ADD sector context; they never replace +# the base skill, diagnostic, or template content. +# 2. Real data — benchmarks must cite public sources and reflect actual +# industry performance ranges, not invented numbers. +# 3. Stage-aware — sector advice differs by company stage. Every benchmark +# and overlay should address stage variation where material. +# 4. Anti-pattern rich — each sector has characteristic mistakes. Surface them. +# 5. Comprehensive but honest — mark items "as-is" when the base content +# needs no sector adaptation. Do not force changes for the sake of volume. + +# ═══════════════════════════════════════════════════════════════ +# PACK METADATA +# ═══════════════════════════════════════════════════════════════ + +pack_metadata: + sector: "" # Kebab-case sector identifier (e.g., "saas", "marketplace", "fintech") + display_name: "" # Human-readable name (e.g., "SaaS", "Marketplace", "Fintech") + version: "1.0.0" # Semantic version of the pack + description: "" # One-sentence description of what this pack covers + applicable_stages: # Which company stages this pack primarily serves + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" # The memory field that triggers this pack + compatible_modes: # Modes this pack composes with + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "" # ISO 8601 date + +# ═══════════════════════════════════════════════════════════════ +# FILE 1: {sector}-benchmarks.yaml +# ═══════════════════════════════════════════════════════════════ +# +# Contains sector-specific metrics with real benchmark data. +# The orchestrator uses these when applying quantitative skills +# (unit economics, balanced scorecard, growth analysis) and when +# generating output templates that include financial metrics. + +benchmarks_schema: + - name: "" # Metric name, title case (e.g., "Net Revenue Retention") + id: "" # Kebab-case unique identifier (e.g., "net-revenue-retention") + category: "" # Grouping: "growth" | "retention" | "unit-economics" | "efficiency" | "sales" | "product" | "financial" + definition: "" # One sentence: what this metric measures + formula: "" # How to calculate, using standard notation + unit: "" # "percentage" | "currency" | "ratio" | "months" | "days" | "multiple" + direction: "" # "higher-is-better" | "lower-is-better" | "target-range" + benchmarks: + poor: + value: "" # Threshold value (e.g., "< 80%", "> 24 months") + signal: "" # What this level indicates about the business + below_average: + value: "" + signal: "" + average: + value: "" + signal: "" + good: + value: "" + signal: "" + excellent: + value: "" + signal: "" + stage_notes: # How the benchmark shifts by stage + seed: "" + series_a: "" + series_b_plus: "" + data_sources: # Public sources for this benchmark data + - source: "" # Publication or organization name + url: "" # URL if available + year: "" # Year of data + related_metrics: [] # Other metrics in this file that are closely related + related_skills: [] # Foreman skills that use or reference this metric + caveats: "" # Important context or limitations of this metric + +# ═══════════════════════════════════════════════════════════════ +# FILE 2: {sector}-skill-overlays.yaml +# ═══════════════════════════════════════════════════════════════ +# +# For each relevant skill, provides sector-specific context that +# the skill executor agent applies as additional framing when +# delivering the skill's content. + +skill_overlays_schema: + - skill: "" # Exact skill file name without .md (e.g., "porters-five-forces") + category: "" # Skill category directory (e.g., "frameworks") + saas_relevance: "" # "critical" | "high" | "moderate" | "low" + sector_context: "" # 2-3 sentences: how this framework applies specifically in the sector + sector_anti_patterns: # Sector-specific mistakes when applying this framework + - "" + - "" + sector_example: "" # One concrete sector use case (2-3 sentences) + sector_modifications: "" # Optional: any structural changes to how the skill is delivered + benchmark_references: [] # IDs from the benchmarks file that are relevant to this skill + +# ═══════════════════════════════════════════════════════════════ +# FILE 3: {sector}-diagnostic-rules.yaml +# ═══════════════════════════════════════════════════════════════ +# +# For each of the 20 diagnostics, defines how triage, diagnosis, +# and routing shift in a sector context. The diagnostic agent +# loads these rules when the sector pack is active. + +diagnostic_rules_schema: + - diagnostic: "" # Diagnostic file name without .md (e.g., "customer-churn-diagnosis") + sector_adaptation: "" # "as-is" | "enhanced" | "reframed" + adaptation_rationale: "" # Why this diagnostic needs (or does not need) sector adaptation + additional_triage_questions: # Sector-specific questions to ADD to the diagnostic's triage + - question: "" + purpose: "" # What this question disambiguates + routing_impact: "" # How the answer changes diagnosis/routing + diagnosis_weight_shifts: # Existing diagnoses that become more or less likely + more_likely: + - diagnosis: "" + reason: "" + less_likely: + - diagnosis: "" + reason: "" + sector_specific_diagnoses: # New diagnoses that only exist in this sector + - name: "" + description: "" + symptoms: [] + routes_to_skills: [] + routes_to_templates: [] + sector_red_flags: [] # Sector-specific red flags to add to the diagnostic + +# ═══════════════════════════════════════════════════════════════ +# FILE 4: {sector}-templates.yaml +# ═══════════════════════════════════════════════════════════════ +# +# For each of the 48 output templates, defines how fields and +# sections adapt for the sector. The output agent loads these +# rules when generating documents with a sector pack active. + +template_adaptations_schema: + - template: "" # Template file name without .md (e.g., "unit-economics-snapshot") + audience: "" # Template audience directory: "investor" | "board" | "team" | "self" | "client" + sector_adaptation: "" # "as-is" | "modified" + adaptation_rationale: "" # Why this template needs (or does not need) sector adaptation + field_changes: # Existing fields that change in sector context + - field: "" # Original field name + sector_label: "" # New label in sector context (or same if unchanged) + sector_guidance: "" # How to fill this field differently for the sector + sections_to_add: # Net-new sections for the sector version + - section_name: "" + placement: "" # "before:{existing_section}" | "after:{existing_section}" | "end" + description: "" # What this section contains + fields: [] # Field names within the section + sections_to_remove: [] # Sections irrelevant in this sector (rare — prefer adaptation over removal) + benchmark_references: [] # IDs from the benchmarks file to surface in this template + +# ═══════════════════════════════════════════════════════════════ +# RESEARCH SOURCES (optional section in {sector}-benchmarks.yaml) +# ═══════════════════════════════════════════════════════════════ +# +# Each pack may include a `research_sources` section in its benchmarks +# file listing sector-specific data sources that supplement the generic +# sources in `.claude/research/` guides. When a research guide is invoked +# with an active industry pack, these sources are appended to the guide's +# default source list, giving the entrepreneur sector-relevant databases, +# reports, and tools alongside the universal recommendations. + +research_sources_schema: + - guide: "" # Research guide file name without .md (e.g., "market-sizing-worksheet") + sector_sources: + - name: "" # Source name (e.g., "OpenView SaaS Benchmarks Report") + url: "" # URL if available + description: "" # One sentence: what data this source provides + access: "" # "free" | "freemium" | "paid" | "gated" diff --git a/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml new file mode 100644 index 0000000..9bfc9d4 --- /dev/null +++ b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-benchmarks.yaml @@ -0,0 +1,1404 @@ +# Agency/Consulting Industry Pack — Benchmarks +# +# 25 agency- and consulting-specific metrics with real benchmark data sourced +# from public studies and industry reports. The orchestrator surfaces these when +# applying quantitative skills, generating output templates with financial +# metrics, or diagnosing growth, utilization, and profitability issues. +# +# The fundamental equation of professional services: Revenue = People x +# Utilization x Rate. Every metric in this file connects to that equation. +# There is no MRR in the traditional sense — there are retainers, projects, +# and hourly engagements. The "product" is people's time and expertise. +# +# Primary data sources: +# - SPI Research (Service Performance Insight) Professional Services +# Maturity Benchmark (2023, 2024) +# - Deltek Clarity Architecture & Engineering / Professional Services +# Industry Study (2023, 2024) +# - HubSpot Agency Pricing & Benchmarks Report (2023, 2024) +# - Promethean Research Agency Benchmarks (2023, 2024) +# - Agency Management Institute (AMI) Financial Benchmarks (2023) +# - Hinge Research Institute High Growth Study (2023) +# - David C. Baker / ReCourses — agency economics benchmarks +# - Bureau of Labor Statistics (BLS) — professional services sector data +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among established agencies and consultancies at the relevant stage. + +pack_metadata: + sector: "agency-consulting" + display_name: "Agency / Consulting" + version: "1.0.0" + description: "Benchmark data for service businesses — consulting firms, digital + agencies, creative studios, development shops, marketing agencies, PR firms, + staffing firms, and professional services — where people, utilization, and + rates are the fundamental economic drivers." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # REVENUE & GROWTH METRICS + # ───────────────────────────────────────────── + + - name: "Revenue" + id: "revenue" + category: "growth" + definition: "Total annual revenue from all sources — project fees, retainers, + hourly billing, and productized services — before any cost deductions." + formula: "Sum of all client payments recognized in the fiscal year" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $250K annual revenue" + signal: "Solo practitioner or very early agency. Revenue depends entirely on the + founder's personal billing capacity, leaving no margin for growth + investment." + below_average: + value: "$250K-$750K" + signal: "Small agency with 2-5 people. Enough to cover salaries but insufficient + to invest in sales, marketing, or operational infrastructure." + average: + value: "$750K-$3M" + signal: "Established small agency. Can support a dedicated leadership layer and + begin investing in business development beyond founder-led sales." + good: + value: "$3M-$10M" + signal: "Mid-size agency with departmental structure, multiple service lines, + and a client portfolio diversified enough to weather individual client + losses." + excellent: + value: "> $10M" + signal: "Large agency with institutional client relationships, strong brand + recognition, and the capacity to invest in proprietary methodologies + or productized offerings." + stage_notes: + seed: "Most agencies start as solo consultancies or partnerships. Revenue below + $250K is typical for year one. Focus on landing 2-3 anchor clients + rather than chasing scale." + series_a: "Agencies rarely raise venture capital. At the $1M-$3M stage, the + equivalent milestone is hiring the first non-billable role (ops manager, + business developer) and proving the firm can generate revenue beyond the + founder." + series_b_plus: "At $5M+, the agency faces the 'scaling wall' — the founder can + no longer personally oversee every engagement. Systems, processes, and a + management layer become essential." + data_sources: + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + - source: "Promethean Research Agency Revenue Study" + year: "2024" + related_metrics: [ "revenue-per-employee", "revenue-per-client" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Revenue in agencies can be reported as gross revenue (total billings) + or net revenue (after subcontractor and pass-through costs). Always + clarify which basis is used. Net revenue is the more meaningful figure for + benchmarking." + + - name: "Revenue per Employee" + id: "revenue-per-employee" + category: "efficiency" + definition: "Total annual revenue divided by average full-time-equivalent + headcount, measuring the revenue-generating efficiency of the team." + formula: "Annual revenue / Average FTE headcount" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $100K per employee" + signal: "Severe underpricing, chronic low utilization, or excessive overhead. + The firm cannot sustain competitive salaries at this level." + below_average: + value: "$100K-$150K" + signal: "Below the sustainability threshold for most markets. Either rates are + too low, utilization is poor, or non-billable headcount is excessive." + average: + value: "$150K-$200K" + signal: "Solid baseline for a healthy agency. Supports market-rate salaries, + reasonable overhead, and modest profit margins." + good: + value: "$200K-$300K" + signal: "Strong revenue productivity. Indicates premium pricing, high + utilization, or an efficient leverage model with lower-cost junior + staff." + excellent: + value: "> $300K per employee" + signal: "Elite efficiency. Typical of strategy consultancies, specialized + technical firms, or agencies with a strong productized service + component." + stage_notes: + seed: "Sole consultants often exceed $200K because there is no overhead. The + metric becomes meaningful only after the first few hires, when the + denominator includes non-billable staff." + series_a: "At 10-25 employees, this metric reveals whether the firm can maintain + economic efficiency as it adds management and operational layers." + series_b_plus: "At 50+ employees, revenue per employee typically compresses as + the firm adds middle management, HR, finance, and operations. + Maintaining $200K+ at scale signals a well-run operation." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "revenue", "utilization-rate", "average-billable-rate" ] + related_skills: [ "balanced-scorecard", "shamrock-organisation" ] + caveats: "Revenue per employee varies dramatically by geography, service type, + and seniority mix. A strategy consultancy and a staffing firm are not + comparable on this metric. Benchmark within the firm's specific + discipline." + + - name: "Revenue per Client" + id: "revenue-per-client" + category: "growth" + definition: "Average annual revenue generated from each active client, + indicating account depth and the ability to expand relationships." + formula: "Annual revenue / Number of active clients" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $10K per client annually" + signal: "Transactional client relationships. The firm is doing small, one-off + projects with little relationship depth or expansion potential." + below_average: + value: "$10K-$30K" + signal: "Some repeat business but accounts are not deep enough to justify + dedicated account management." + average: + value: "$30K-$75K" + signal: "Meaningful client relationships. Large enough to warrant strategic + account planning and regular relationship maintenance." + good: + value: "$75K-$200K" + signal: "Strong account depth. Clients are engaging the firm across multiple + services or on sustained retainers." + excellent: + value: "> $200K per client annually" + signal: "Deep strategic partnerships. The firm is embedded in the client's + operations. High switching costs for the client." + stage_notes: + seed: "Early agencies should aim for fewer, deeper client relationships rather + than many small ones. One $100K client is more valuable than ten $10K + clients at this stage." + series_a: "As the agency grows, balancing account depth with diversification + becomes critical. Target a minimum of $50K per client with no single + client exceeding 25% of revenue." + series_b_plus: "At scale, revenue per client becomes a segmentation tool. + Identify which client tier generates the best margin and concentrate + growth there." + data_sources: + - source: "Promethean Research Agency Benchmarks" + year: "2024" + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + related_metrics: [ "client-concentration", "client-retention-rate" ] + related_skills: [ "business-model-canvas", "net-promoter-score" ] + caveats: "This metric must be interpreted alongside client count. A $3M agency + with 3 clients ($1M each) has dangerous concentration. A $3M agency with + 30 clients ($100K each) may have insufficient account depth." + + # ───────────────────────────────────────────── + # UTILIZATION METRICS + # ───────────────────────────────────────────── + + - name: "Utilization Rate" + id: "utilization-rate" + category: "efficiency" + definition: "The percentage of total available working hours that are spent on + client-billable or client-related productive work, including both billed + and unbilled client work." + formula: "(Total hours on client work / Total available working hours) x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "< 55%" + signal: "Chronic underutilization. Staff are idle or consumed by internal work. + Revenue cannot cover costs at this level unless rates are + extraordinarily high." + below_average: + value: "55%-62%" + signal: "Below optimal. Either bench time is excessive, too much time is + consumed by non-billable overhead, or the firm has hired ahead of + demand." + average: + value: "62%-68%" + signal: "Healthy utilization for most agencies and consultancies. Leaves room + for professional development, sales, and administrative work." + good: + value: "68%-75%" + signal: "Strong utilization. The firm is running efficiently without burning out + staff. Typical of well-managed mid-size agencies." + excellent: + value: "75%-80%" + signal: "Near-optimal utilization. Beyond 80%, quality degrades, burnout + accelerates, and no capacity exists for new business development." + stage_notes: + seed: "Solo consultants can achieve 70-80% utilization because they have minimal + overhead. Once the first non-billable hire is made, overall utilization + drops mechanically." + series_a: "At 10-25 people, target 65% firm-wide utilization. Leadership and + operations staff should not be expected to bill significant hours." + series_b_plus: "Larger firms target 65-70% for billable staff, with firm-wide + utilization (including leadership and ops) averaging 55-65%." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "billable-utilization-rate", "bench-time", "revenue-per-employee" ] + related_skills: [ "balanced-scorecard", "eisenhower-matrix" ] + caveats: "Utilization above 80% is not a goal — it is a warning sign. Sustained + high utilization leaves no capacity for professional development, + innovation, or new business pursuit. It also correlates strongly with + employee attrition." + + - name: "Billable Utilization Rate" + id: "billable-utilization-rate" + category: "efficiency" + definition: "The percentage of total available working hours that are actually + billed to and paid by clients, excluding unbilled client work, write-offs, + and internal time." + formula: "(Hours billed to clients / Total available working hours) x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "< 50%" + signal: "Fewer than half of available hours generate revenue. The gap between + utilization and billable utilization suggests significant write-offs, + scope creep, or unbilled work." + below_average: + value: "50%-58%" + signal: "Moderate leakage between worked hours and billed hours. Common causes: + scope creep, poor time tracking, and reluctance to bill for all work + performed." + average: + value: "58%-65%" + signal: "Acceptable billable efficiency. The gap between utilization rate and + billable rate should be under 7 percentage points." + good: + value: "65%-72%" + signal: "Strong billing discipline. The firm captures most productive time as + revenue and maintains tight scope management." + excellent: + value: "72%-78%" + signal: "Exceptional billing efficiency. Characteristic of firms with rigorous + time tracking, clear scoping, and value-based pricing that minimizes + the billable-hours problem." + stage_notes: + seed: "Solo consultants should track the gap between time worked and time + billed. A gap above 10 percentage points indicates systemic scope creep + or undercharging." + series_a: "As the firm grows, the billable utilization rate for delivery staff + should be tracked separately from firm-wide utilization." + series_b_plus: "Mature agencies use the gap between utilization and billable + utilization as a management metric — it reveals operational efficiency." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "utilization-rate", "effective-billable-rate", "scope-creep-rate" ] + related_skills: [ "balanced-scorecard", "smart-goals" ] + caveats: "Firms using fixed-price or retainer models may find billable + utilization difficult to measure precisely. In these cases, track + 'productive utilization' against contracted deliverables rather than + hourly billing." + + - name: "Bench Time" + id: "bench-time" + category: "efficiency" + definition: "The percentage of billable staff who are currently unassigned to + any client project, representing idle capacity and a direct cost to the + business." + formula: "(FTEs without client assignments / Total billable FTEs) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 20%" + signal: "One in five billable staff is idle. This drains cash and indicates + either a sales pipeline failure or overhiring relative to demand." + below_average: + value: "15%-20%" + signal: "Elevated bench. Acceptable for brief periods between major projects but + unsustainable beyond one quarter." + average: + value: "10%-15%" + signal: "Manageable bench level. Some bench time is healthy — it enables rapid + response to new opportunities and allows for professional + development." + good: + value: "5%-10%" + signal: "Lean operation with modest buffer capacity. The firm can respond to new + work without significant hiring lag." + excellent: + value: "< 5%" + signal: "Near-full deployment. Efficient but potentially fragile — no surge + capacity for unexpected opportunities or client emergencies." + stage_notes: + seed: "Bench is rarely relevant for agencies under 5 people — everyone works on + everything. The concept becomes meaningful at 10+ billable staff." + series_a: "At 10-25 people, bench management becomes a critical skill. Track + bench weekly, not monthly. A two-week bench period per person per year + is a reasonable target." + series_b_plus: "Larger agencies use bench strategically — assigning benched + staff to R&D, internal tools, thought leadership, or pre-sales + activities." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "utilization-rate", "revenue-per-employee" ] + related_skills: [ "scenario-planning", "eisenhower-matrix" ] + caveats: "Zero bench time is not a goal. Firms with zero bench cannot respond to + new opportunities, leading to turned-away revenue. Optimal bench is 5-10%, + deployed productively." + + # ───────────────────────────────────────────── + # PRICING & RATE METRICS + # ───────────────────────────────────────────── + + - name: "Average Billable Rate" + id: "average-billable-rate" + category: "unit-economics" + definition: "The mean hourly rate charged across all billable staff and + engagement types, before any discounts, write-offs, or scope adjustments." + formula: "Total standard billings / Total hours billed" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $100/hour" + signal: "Commodity pricing territory. At this rate, the firm competes with + freelancers and offshore teams. Margins are thin and talent retention + is difficult." + below_average: + value: "$100-$150/hour" + signal: "Mid-market rate. Viable for execution-focused agencies but insufficient + for strategic advisory or premium creative work." + average: + value: "$150-$225/hour" + signal: "Professional-grade rate. Supports experienced staff, decent margins, + and investment in the business. Typical for competent mid-market + agencies." + good: + value: "$225-$350/hour" + signal: "Premium rate. Commands respect and supports higher-caliber talent. + Typical for specialized consultancies and top-tier creative agencies." + excellent: + value: "> $350/hour" + signal: "Elite rate. Reserved for management consultancies, highly specialized + technical firms, and agencies with exceptional brand and track + record." + stage_notes: + seed: "New consultants often underprice to win work. Calculate a minimum viable + rate: (target salary + overhead + profit margin) / (available billable + hours). Most solos should charge more than they think." + series_a: "Blended rate matters more than individual rates. The firm should have + a rate card by seniority level and manage the staff mix to achieve + target blended rate." + series_b_plus: "At scale, rate management becomes strategic. Senior staff should + command rates 3-5x junior staff. The blended rate should rise as the + firm's reputation grows." + data_sources: + - source: "HubSpot Agency Pricing Report" + year: "2024" + - source: "Promethean Research Agency Benchmarks" + year: "2024" + related_metrics: [ "effective-billable-rate", "revenue-per-employee" ] + related_skills: + - four-ps-marketing + caveats: "Rates vary enormously by geography, discipline, and client segment. A + $150/hour rate in a low-cost market may represent premium pricing. Always + benchmark within the firm's specific context." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Effective Billable Rate" + id: "effective-billable-rate" + category: "unit-economics" + definition: "The actual revenue earned per hour of work performed on client + engagements, accounting for discounts, write-offs, scope creep, and + fixed-price overruns." + formula: "Actual revenue collected / Total hours worked on client projects + (billed and unbilled)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 60% of standard rate" + signal: "Massive value leakage. For every dollar the firm should earn, it + collects less than 60 cents. Discounting, write-offs, and scope creep + are eroding the business." + below_average: + value: "60%-75% of standard rate" + signal: "Significant rate erosion. Common causes: aggressive discounting to win + work, poor scope management, and failure to bill for change orders." + average: + value: "75%-85% of standard rate" + signal: "Moderate erosion. The gap between standard and effective rate is + manageable but indicates room for improvement in scope and billing + discipline." + good: + value: "85%-92% of standard rate" + signal: "Strong rate realization. The firm maintains discipline on scope, + billing, and discounts while remaining competitive." + excellent: + value: "> 92% of standard rate" + signal: "Exceptional rate realization. Nearly all work performed is captured as + revenue. Characteristic of firms with strong positioning and + negotiation discipline." + stage_notes: + seed: "Solo consultants should track effective rate obsessively. The gap between + what they charge and what they actually earn per hour often reveals + shocking underpricing." + series_a: "At 10-25 people, effective rate realization becomes a management + discipline. Train project managers to track hours against estimates and + flag overruns early." + series_b_plus: "Mature agencies target 85%+ effective rate realization and + include it in project manager KPIs." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + related_metrics: [ "average-billable-rate", "scope-creep-rate", "gross-margin" ] + related_skills: + - competitive-negotiation + caveats: "Effective rate is the single most revealing metric for agency + profitability. A firm with a high standard rate but low effective rate has + a discipline problem, not a pricing problem." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + # ───────────────────────────────────────────── + # PROFITABILITY METRICS + # ───────────────────────────────────────────── + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "Revenue minus direct costs of service delivery (staff salaries, + freelancer costs, subcontractor fees, and direct project expenses), + expressed as a percentage of revenue." + formula: "(Revenue - Direct costs of delivery) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "Dangerously thin margins. After overhead, the firm is likely + unprofitable. Either rates are too low, utilization is poor, or the + cost of delivery is excessive." + below_average: + value: "40%-50%" + signal: "Thin margins that leave little room for overhead, business development, + and profit. Common in agencies competing on price." + average: + value: "50%-55%" + signal: "Acceptable gross margin for most agency types. Enough to cover overhead + and generate a modest profit." + good: + value: "55%-65%" + signal: "Healthy margins indicating strong pricing, efficient delivery, and good + leverage (appropriate mix of senior and junior staff)." + excellent: + value: "> 65%" + signal: "Premium margins. Typical of strategy consultancies, highly specialized + firms, or agencies with significant productized revenue." + stage_notes: + seed: "Solo consultants without subcontractors may see gross margins of 90%+ + because there are no direct labor costs beyond their own time. This + compresses dramatically with the first hires." + series_a: "At 10-25 people, gross margin is the critical metric. If gross margin + is below 50%, the firm cannot sustain the overhead structure needed to + grow." + series_b_plus: "Mature agencies should maintain gross margin above 50% while + investing in senior talent and specialized capabilities." + data_sources: + - source: "Deltek Clarity Industry Study" + year: "2023" + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + related_metrics: [ "ebitda-margin", "effective-billable-rate", "leverage-ratio" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Gross margin in agencies depends heavily on how 'direct costs' are + classified. Some firms include all staff salaries in COGS; others include + only billable staff. Ensure consistent classification when benchmarking." + + - name: "EBITDA Margin" + id: "ebitda-margin" + category: "financial" + definition: "Earnings before interest, taxes, depreciation, and amortization as + a percentage of revenue, representing the operating profitability of the + firm." + formula: "(Revenue - All operating expenses) / Revenue x 100 (before interest, + taxes, depreciation, amortization)" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5%" + signal: "Near breakeven. The firm has no margin of safety. A single lost client + or late payment could create a cash crisis." + below_average: + value: "5%-10%" + signal: "Thin profitability. Sufficient to survive but not to invest in growth, + build reserves, or reward partners generously." + average: + value: "10%-15%" + signal: "Respectable profitability for a well-run agency. Enough to build cash + reserves, invest modestly in growth, and provide competitive partner + compensation." + good: + value: "15%-20%" + signal: "Strong profitability. The firm can invest in growth, weather downturns, + and attract partner-level talent with meaningful equity or profit + participation." + excellent: + value: "> 20%" + signal: "Exceptional profitability. Typical of specialized consultancies, firms + with productized offerings, or agencies with dominant market + positions." + stage_notes: + seed: "Profitability in year one is a luxury but not a requirement. However, + agencies should target breakeven within 12-18 months — unlike product + companies, agencies should not burn cash for years." + series_a: "At 10-25 employees, target 10%+ EBITDA margin. If margins are + thinner, examine overhead ratio and utilization before cutting + salaries." + series_b_plus: "Mature agencies operating below 10% EBITDA are likely either + overinvesting in growth or suffering from structural margin problems." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "gross-margin", "overhead-ratio", "revenue-per-employee" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "In owner-operated agencies, EBITDA may be understated because the + owner takes a below-market salary, or overstated because the owner pays + themselves above-market. Normalize owner compensation to market rate + before benchmarking." + + # ───────────────────────────────────────────── + # CLIENT METRICS + # ───────────────────────────────────────────── + + - name: "Client Concentration" + id: "client-concentration" + category: "financial" + definition: "The revenue share attributable to the single largest client, + measuring dependency risk." + formula: "Revenue from largest client / Total revenue x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 40%" + signal: "Existential dependency. Losing this client would threaten the firm's + survival. The client also holds excessive negotiating power over rates + and terms." + below_average: + value: "30%-40%" + signal: "Dangerously concentrated. The firm's strategic decisions are + constrained by the need to retain this account." + average: + value: "20%-30%" + signal: "Moderate concentration. Manageable if the relationship is strong, but + diversification should be an active priority." + good: + value: "10%-20%" + signal: "Healthy balance between account depth and diversification. No single + client loss would fundamentally threaten the business." + excellent: + value: "< 10%" + signal: "Well-diversified. The firm can walk away from any single client without + existential risk, which paradoxically strengthens negotiating power." + stage_notes: + seed: "High concentration is inevitable in the first 1-2 years. Accept it, but + actively pursue diversification. Every new client reduces existential + risk." + series_a: "At $1M-$3M revenue, no client should exceed 25%. This is the stage + where concentration risk transitions from 'understood and managed' to + 'structural vulnerability.'" + series_b_plus: "At $5M+, target sub-15% for the largest client and ensure the + top 5 clients combined represent no more than 50% of revenue." + data_sources: + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + - source: "David C. Baker / ReCourses — agency economics" + year: "2024" + related_metrics: [ "revenue-per-client", "client-retention-rate" ] + related_skills: [ "scenario-planning", "porters-five-forces" ] + caveats: "Concentration is acceptable when the client is contractually committed + (multi-year retainer) and strategically aligned. It is dangerous when the + relationship is month-to-month and dependent on a single champion." + + - name: "Client Retention Rate" + id: "client-retention-rate" + category: "retention" + definition: "The percentage of clients from the prior year who continue to + engage the firm in the current year, measuring relationship durability." + formula: "(Clients retained from prior year / Total clients in prior year) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 60%" + signal: "The firm loses nearly half its clients annually. This forces constant + new business development and prevents account deepening. Often a + quality or relationship problem." + below_average: + value: "60%-70%" + signal: "Below average retention. The firm is on a treadmill — acquiring new + clients to replace departing ones rather than growing existing + relationships." + average: + value: "70%-80%" + signal: "Reasonable retention for most agency types. Some churn is natural as + client needs evolve, budgets shift, or projects conclude." + good: + value: "80%-90%" + signal: "Strong retention indicating the firm is embedded in client operations + and delivering consistent value." + excellent: + value: "> 90%" + signal: "Exceptional client loyalty. The firm has become a trusted extension of + the client's team. Typical of deep retainer relationships." + stage_notes: + seed: "Early-stage retention is volatile because the client base is small — + losing one of three clients is 33% churn. Track retention carefully but + interpret it within the context of a small sample." + series_a: "At 15-30 clients, retention rate becomes statistically meaningful and + a leading indicator of firm health." + series_b_plus: "Mature firms should segment retention by client tier. Retaining + top-tier clients (top 20% by revenue) matters far more than retaining + small project clients." + data_sources: + - source: "Hinge Research Institute High Growth Study" + year: "2023" + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + related_metrics: [ "client-concentration", "revenue-per-client", "nps-client" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "Retention does not measure revenue retention. A firm can retain 90% of + clients while revenue from those clients declines. Track both logo and + revenue retention." + + # ───────────────────────────────────────────── + # SALES & PIPELINE METRICS + # ───────────────────────────────────────────── + + - name: "Average Project Value" + id: "average-project-value" + category: "sales" + definition: "The mean revenue from a single client engagement, whether a + discrete project, a retainer period, or a phase of work." + formula: "Total project revenue / Number of projects closed" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $5K" + signal: "Micro-projects with high overhead relative to revenue. The firm spends + as much time selling and onboarding as delivering." + below_average: + value: "$5K-$15K" + signal: "Small projects. Viable for freelancers but challenging for agencies + with overhead. Requires high volume to generate meaningful revenue." + average: + value: "$15K-$50K" + signal: "Standard agency project size. Large enough to justify structured + delivery and account management." + good: + value: "$50K-$150K" + signal: "Meaningful engagements that warrant strategic planning, phased + delivery, and senior oversight. Typical of mid-market consulting." + excellent: + value: "> $150K" + signal: "Large, complex engagements. These projects define the firm's reputation + and require sophisticated project management and executive attention." + stage_notes: + seed: "Small agencies should raise average project value steadily. Moving from + $10K to $25K average project size transforms the economics of the + business." + series_a: "At $1M-$3M revenue, the firm should have a clear minimum project size + and decline work below it. Minimum thresholds reduce operational + complexity." + series_b_plus: "Larger agencies use project tiering — small projects + ($10K-$50K), medium ($50K-$200K), large ($200K+) — with different + delivery models for each." + data_sources: + - source: "HubSpot Agency Pricing Report" + year: "2024" + - source: "Promethean Research Agency Benchmarks" + year: "2024" + related_metrics: [ "revenue-per-client", "win-rate", "sales-cycle-length" ] + related_skills: + - competitive-negotiation + caveats: "Average project value can be misleading if the firm has a bimodal + distribution — many small projects and a few large ones. Examine the + distribution, not just the mean." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Pipeline Coverage Ratio" + id: "pipeline-coverage-ratio" + category: "sales" + definition: "The ratio of total pipeline value to the revenue target for the + period, indicating whether the firm has sufficient opportunities to meet + its goals." + formula: "Total weighted pipeline value / Revenue target for the period" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2x" + signal: "Insufficient pipeline. The firm will almost certainly miss its revenue + target. Immediate new business development investment is needed." + below_average: + value: "2x-3x" + signal: "Thin coverage. Achievable only if win rates are above average. No + margin for slippage or delayed decisions." + average: + value: "3x-4x" + signal: "Adequate coverage for most agencies. Provides a reasonable buffer + against lost opportunities and delayed client decisions." + good: + value: "4x-5x" + signal: "Strong pipeline. The firm can be selective about which opportunities to + pursue and negotiate from a position of strength." + excellent: + value: "> 5x" + signal: "Robust pipeline. Enables strategic client selection and premium + pricing. The firm can decline work that does not align with its + positioning." + stage_notes: + seed: "Pipeline discipline is rare in small agencies. Even a simple spreadsheet + tracking opportunities, probability, and timeline is transformative." + series_a: "At $1M-$3M, formalize the pipeline with stages and probability + weights. Weekly pipeline reviews should become a non-negotiable + management ritual." + series_b_plus: "Mature agencies track pipeline velocity (how fast deals + progress), pipeline quality (weighted by ideal client criteria), and + pipeline source (referral vs. outbound vs. inbound)." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Hinge Research Institute High Growth Study" + year: "2023" + related_metrics: [ "win-rate", "sales-cycle-length", "revenue" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "Pipeline coverage is only meaningful with honest probability + weighting. A 5x pipeline filled with unqualified, low-probability + opportunities provides false comfort." + + - name: "Win Rate" + id: "win-rate" + category: "sales" + definition: "The percentage of formal proposals or pitches that result in a + signed engagement, measuring the firm's competitive effectiveness." + formula: "(Proposals won / Total proposals submitted) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20%" + signal: "Four out of five proposals fail. Either the firm is pursuing the wrong + opportunities, the proposals are weak, or pricing is misaligned." + below_average: + value: "20%-30%" + signal: "Below average but not uncommon, especially for agencies that respond to + open RFPs. Qualification discipline would improve this metric." + average: + value: "30%-40%" + signal: "Standard win rate for agencies with a mix of referral and competitive + pitches." + good: + value: "40%-55%" + signal: "Strong conversion. The firm is qualifying well, positioning + effectively, and pricing competitively." + excellent: + value: "> 55%" + signal: "Exceptional win rate. Indicates strong referral pipeline, expert + positioning, or excellent pre-qualification. The firm may not be + pitching enough." + stage_notes: + seed: "Early agencies should track win rate from day one. A pattern of losing + helps identify positioning weaknesses faster than a pattern of not + pitching at all." + series_a: "At $1M-$3M, analyze win rate by source: referral wins should exceed + 50%, competitive pitch wins will be lower. If overall rate is below 25%, + the firm has a positioning or pricing problem." + series_b_plus: "Mature agencies use win/loss analysis to improve positioning. + Interview lost prospects to understand why they chose a competitor." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Hinge Research Institute High Growth Study" + year: "2023" + related_metrics: [ "pipeline-coverage-ratio", "sales-cycle-length", "average-project-value" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "A very high win rate (>60%) may indicate the firm is only pursuing + 'safe' opportunities and not stretching into larger or more prestigious + engagements." + + - name: "Sales Cycle Length" + id: "sales-cycle-length" + category: "sales" + definition: "The average elapsed time from initial qualified contact with a + prospect to a signed contract, measuring the speed of the sales process." + formula: "Average days from first qualified meeting to contract signature" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 120 days" + signal: "Excessively long sales cycle. Either the firm is pursuing enterprise + clients without the infrastructure to support long cycles, or + decisions are stalling without resolution." + below_average: + value: "90-120 days" + signal: "Lengthy for most agency engagements. Acceptable for large, complex + projects but a drag on cash flow for standard work." + average: + value: "45-90 days" + signal: "Typical for mid-market agency work. Allows for proper scoping, proposal + development, and client decision-making." + good: + value: "21-45 days" + signal: "Efficient sales process. The firm qualifies quickly, proposes clearly, + and drives decisions. Typical of firms with strong referral + pipelines." + excellent: + value: "< 21 days" + signal: "Rapid conversion. Characteristic of firms selling productized services, + working from strong referrals, or engaging repeat clients on new + projects." + stage_notes: + seed: "Early agencies should aim for short cycles. Long sales cycles consume + founder time that should be spent on delivery and relationship + building." + series_a: "At $1M-$3M, segment sales cycle by engagement type. Retainer renewals + should close in 1-2 weeks; new client projects in 30-60 days." + series_b_plus: "Mature agencies track sales cycle by client tier. Enterprise + engagements with procurement involvement will naturally take longer." + data_sources: + - source: "HubSpot Agency Pricing Report" + year: "2024" + - source: "Promethean Research Agency Benchmarks" + year: "2024" + related_metrics: [ "win-rate", "pipeline-coverage-ratio" ] + related_skills: [ "delivering-the-deal", "competitive-negotiation" ] + caveats: "Sales cycle length should be measured from the first qualified + interaction, not from initial contact. Including unqualified leads + inflates the metric and obscures the real conversion timeline." + + - name: "Cost per Lead" + id: "cost-per-lead" + category: "sales" + definition: "The total cost of generating a qualified new business lead, + including marketing, business development, events, and content creation + costs." + formula: "Total business development and marketing spend / Number of qualified + leads generated" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $2,000 per lead" + signal: "Extremely expensive lead generation. At this cost, the firm needs very + high average project values and win rates to achieve positive ROI on + business development." + below_average: + value: "$1,000-$2,000" + signal: "Elevated cost. Acceptable for agencies targeting enterprise clients + with $100K+ engagements, but expensive for mid-market firms." + average: + value: "$500-$1,000" + signal: "Reasonable lead cost for most professional services firms. Achievable + through a mix of content marketing, networking, and selective paid + channels." + good: + value: "$200-$500" + signal: "Efficient lead generation. Typically driven by strong referral + networks, thought leadership content, and organic reputation." + excellent: + value: "< $200 per lead" + signal: "Highly efficient. Usually indicates a strong referral engine or + dominant thought leadership position that generates inbound interest + at low cost." + stage_notes: + seed: "Most early agencies spend $0 on formal lead generation — leads come from + the founder's network. Track the implicit cost of the founder's time on + business development." + series_a: "At $1M-$3M, begin tracking lead source and cost by channel. Referrals + are typically the cheapest and highest-converting source." + series_b_plus: "Mature agencies diversify lead sources while monitoring cost per + lead by channel. Content marketing and speaking engagements often + deliver the best long-term CPL." + data_sources: + - source: "HubSpot Agency Pricing Report" + year: "2024" + - source: "Hinge Research Institute High Growth Study" + year: "2023" + related_metrics: [ "win-rate", "pipeline-coverage-ratio", "average-project-value" ] + related_skills: [ "four-ps-marketing", "business-model-canvas" ] + caveats: "Many agencies undercount lead cost by ignoring the opportunity cost of + senior staff time spent on business development. A partner spending 30% of + their time on BD has a real cost even if no cash is spent on marketing." + + # ───────────────────────────────────────────── + # PEOPLE & TALENT METRICS + # ───────────────────────────────────────────── + + - name: "Employee Retention Rate" + id: "employee-retention-rate" + category: "retention" + definition: "The percentage of employees who remain with the firm over a + twelve-month period, measuring talent stability and organizational + health." + formula: "(Employees at end of period - New hires during period) / Employees at + start of period x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 70%" + signal: "Crisis-level attrition. Nearly a third of the team leaves annually. + Client relationships, institutional knowledge, and delivery quality + all suffer." + below_average: + value: "70%-80%" + signal: "Elevated turnover. The firm is spending excessive time and money on + recruiting and onboarding replacements. Key client relationships may + be at risk." + average: + value: "80%-85%" + signal: "Industry-standard retention for agencies. Some turnover is natural as + junior staff advance their careers." + good: + value: "85%-92%" + signal: "Strong retention indicating healthy culture, competitive compensation, + and meaningful work." + excellent: + value: "> 92%" + signal: "Exceptional loyalty. The firm is a destination employer in its market. + Key staff departures are rare and managed proactively." + stage_notes: + seed: "At under 10 people, every departure is destabilizing. Retention is + existential — losing one of five people is a 20% attrition event." + series_a: "At 10-25 people, institute stay interviews, not just exit interviews. + Understand why people stay and reinforce those factors." + series_b_plus: "Track retention by seniority tier. Losing junior staff at 15% + annually is manageable. Losing senior staff at 15% is a crisis." + data_sources: + - source: "Bureau of Labor Statistics — Professional Services" + year: "2024" + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + related_metrics: [ "enps", "revenue-per-employee", "leverage-ratio" ] + related_skills: [ "inspiring-and-retaining", "organisational-culture" ] + caveats: "Aggregate retention masks 'regrettable' versus 'non-regrettable' + attrition. Track whether departures are top performers (regrettable) or + underperformers (often healthy). The quality of retention matters as much + as the rate." + + - name: "Revenue per Partner/Principal" + id: "revenue-per-partner" + category: "efficiency" + definition: "Total firm revenue divided by the number of partners, principals, + or senior leaders, measuring the revenue-generation capacity of the + leadership team." + formula: "Annual revenue / Number of partners or principals" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $500K per partner" + signal: "Partners are not generating sufficient revenue to justify their + compensation and the overhead they represent." + below_average: + value: "$500K-$750K" + signal: "Below the threshold for competitive partner compensation in most + markets. The firm may have too many partners relative to its revenue + base." + average: + value: "$750K-$1.2M" + signal: "Sustainable revenue per partner. Supports competitive compensation and + modest reinvestment in the firm." + good: + value: "$1.2M-$2M" + signal: "Strong partner productivity. Partners are effectively leveraging teams + and winning significant work." + excellent: + value: "> $2M per partner" + signal: "Exceptional leverage. Partners are managing large teams and major + accounts. Typical of management consultancies and large agencies with + strong brands." + stage_notes: + seed: "For solo consultants, this metric equals total revenue. It becomes + meaningful when the firm adds a second partner or principal." + series_a: "At the point of adding partners, this metric determines whether the + firm can afford them. A partner should generate at least $750K within + their first full year." + series_b_plus: "Mature firms use revenue per partner as a promotion criterion. + Partners who consistently fall below the threshold are a drag on firm + economics." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "David C. Baker / ReCourses — agency economics" + year: "2024" + related_metrics: [ "revenue-per-employee", "leverage-ratio" ] + related_skills: [ "leadership-pipeline", "delegation-and-empowerment" ] + caveats: "Revenue per partner varies enormously by firm type. A solo-practice + consultant at $400K is healthy; a partner at a 50-person agency at $400K + is underperforming. Always benchmark within the firm's context." + + - name: "Leverage Ratio" + id: "leverage-ratio" + category: "efficiency" + definition: "The ratio of junior billable staff to senior billable staff + (partners, principals, directors), measuring the firm's ability to scale + expertise through staffing structure." + formula: "Number of junior/mid-level billable staff / Number of senior staff + (partners, principals, directors)" + unit: "ratio" + direction: "target-range" + benchmarks: + poor: + value: "< 2:1" + signal: "Top-heavy firm. Too many senior staff relative to junior. Margins are + compressed because high-cost talent does work that lower-cost staff + could handle." + below_average: + value: "2:1 to 3:1" + signal: "Low leverage. The firm is not fully utilizing the capacity of senior + staff to supervise and develop junior talent." + average: + value: "3:1 to 5:1" + signal: "Balanced leverage for most consulting and agency models. Senior staff + can oversee work quality while junior staff handle execution." + good: + value: "5:1 to 8:1" + signal: "Strong leverage. Seniors focus on client relationships, quality, and + sales while junior staff execute. Margins benefit from the cost + differential." + excellent: + value: "> 8:1" + signal: "High leverage. Typical of staffing firms or agencies with highly + standardized delivery models. Requires robust training and quality + control systems." + stage_notes: + seed: "Leverage is irrelevant for solo consultants and becomes meaningful only + after the first few junior hires." + series_a: "At 10-25 people, deliberately design the leverage model. Each senior + person should manage 3-5 junior staff. Hiring a senior person without a + team to leverage is economically inefficient." + series_b_plus: "Mature firms explicitly manage leverage as a profit driver. + Every percentage point shift from senior to junior delivery (at + maintained quality) flows directly to margin." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "David C. Baker / ReCourses — agency economics" + year: "2024" + related_metrics: [ "revenue-per-partner", "gross-margin", "revenue-per-employee" ] + related_skills: [ "shamrock-organisation", "leadership-pipeline" ] + caveats: "High leverage only works if the firm invests in training, methodology, + and quality control. Without these, leverage becomes a euphemism for + letting inexperienced staff do senior work poorly." + + - name: "Overhead Ratio" + id: "overhead-ratio" + category: "financial" + definition: "Total non-delivery overhead costs (rent, administration, + non-billable salaries, technology, insurance, marketing) as a percentage + of revenue." + formula: "Total overhead costs / Revenue x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 45%" + signal: "Overhead consuming nearly half of revenue. Even with healthy gross + margins, profitability is crushed by excessive non-delivery costs." + below_average: + value: "35%-45%" + signal: "Elevated overhead. Common in firms with expensive office space, large + non-billable staff, or excessive technology spend." + average: + value: "25%-35%" + signal: "Typical overhead range for professional services firms. Manageable if + gross margin is healthy." + good: + value: "18%-25%" + signal: "Lean overhead. The firm runs efficiently with minimal non-delivery + costs. Often achieved by remote-first firms or those with minimal + office space." + excellent: + value: "< 18%" + signal: "Ultra-lean overhead. Typical of virtual agencies, solo consultancies + with minimal infrastructure, or firms that have ruthlessly eliminated + non-productive costs." + stage_notes: + seed: "Solo consultants naturally have low overhead. Track overhead percentage + from the start to establish a baseline before it creeps up." + series_a: "The first office lease, the first full-time operations hire, and the + first CRM subscription represent overhead step-changes. Ensure each + addition is justified by revenue capacity." + series_b_plus: "At scale, overhead ratio is the primary controllable lever for + EBITDA improvement. Conduct an annual overhead audit to identify costs + that no longer deliver value." + data_sources: + - source: "Deltek Clarity Industry Study" + year: "2023" + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + related_metrics: [ "ebitda-margin", "gross-margin", "revenue-per-employee" ] + related_skills: [ "eisenhower-matrix", "balanced-scorecard" ] + caveats: "Some overhead is investment (marketing, training, R&D). Cutting all + overhead to minimize the ratio can starve the firm of growth capability. + Distinguish between productive overhead and waste." + + # ───────────────────────────────────────────── + # PROJECT & DELIVERY METRICS + # ───────────────────────────────────────────── + + - name: "Scope Creep Rate" + id: "scope-creep-rate" + category: "efficiency" + definition: "The percentage of projects that exceed their original scope, + budget, or timeline by more than 10%, measuring the firm's scoping and + project management discipline." + formula: "(Projects exceeding original scope by >10% / Total projects completed) + x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 50%" + signal: "More than half of projects overrun. This is a systemic scoping, + negotiation, or project management failure that directly erodes + margins." + below_average: + value: "35%-50%" + signal: "Frequent scope creep. The firm is likely absorbing significant unbilled + work. Effective rate realization is depressed." + average: + value: "20%-35%" + signal: "Moderate scope creep. Some overruns are inevitable, but at this level + the firm should have change-order processes that capture additional + scope as additional revenue." + good: + value: "10%-20%" + signal: "Well-managed scope. The firm scopes accurately, communicates boundaries + clearly, and uses change orders effectively." + excellent: + value: "< 10%" + signal: "Exceptional scope discipline. Nearly all projects deliver within the + original parameters. Characteristic of firms with mature methodologies + and experienced project managers." + stage_notes: + seed: "Early agencies frequently underscope because they want to impress clients + and lack experience with estimation. Track actuals versus estimates from + the first project." + series_a: "At $1M-$3M, implement formal change-order processes. Every scope + expansion should be documented and either billed or explicitly absorbed + as an investment." + series_b_plus: "Mature agencies use scope creep data to improve estimation + accuracy, identify which project types and client types are most prone + to overruns, and adjust pricing accordingly." + data_sources: + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + - source: "Deltek Clarity Industry Study" + year: "2023" + related_metrics: [ "effective-billable-rate", "gross-margin" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "Not all scope expansion is negative. Strategic scope extension on a + key account can deepen the relationship and lead to expansion. The issue + is unmanaged scope creep — work that is neither billed nor strategically + justified." + + - name: "Accounts Receivable Days" + id: "ar-days" + category: "financial" + definition: "The average number of days between invoicing and payment + collection, measuring cash collection efficiency." + formula: "(Accounts Receivable / Annual Revenue) x 365" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 75 days" + signal: "Dangerously slow collections. The firm is financing client operations + with its own cash. Cash flow crises are likely." + below_average: + value: "60-75 days" + signal: "Elevated AR. The firm is extending significant implicit credit to + clients. Cash flow is strained, especially during growth periods." + average: + value: "45-60 days" + signal: "Typical for agencies billing on net-30 terms with some payment delays. + Manageable but room for improvement." + good: + value: "30-45 days" + signal: "Healthy cash collection. Clients pay within terms. The firm has + adequate cash flow to meet payroll and operating expenses." + excellent: + value: "< 30 days" + signal: "Excellent cash discipline. Achieved through upfront deposits, + milestone-based billing, retainer pre-payment, or credit card + billing." + stage_notes: + seed: "Cash flow kills more agencies than lack of revenue. Require deposits + (25-50% upfront) on all new projects from day one. Never start work + without a signed contract and deposit." + series_a: "At $1M-$3M, AR management becomes a dedicated function. Late-paying + clients should be flagged, followed up, and — for chronic offenders — + moved to pre-payment or retainer terms." + series_b_plus: "Mature agencies negotiate payment terms as actively as they + negotiate rates. Net-15 or retainer pre-payment structures dramatically + improve cash position." + data_sources: + - source: "Deltek Clarity Industry Study" + year: "2023" + - source: "Agency Management Institute Financial Benchmarks" + year: "2023" + related_metrics: [ "ebitda-margin", "revenue" ] + related_skills: [ "competitive-negotiation", "delivering-the-deal" ] + caveats: "AR days can be artificially improved by front-loading billing (billing + before work is complete) or worsened by client-imposed payment terms + (net-60 or net-90 at large enterprises). Understand the underlying payment + dynamics, not just the number." + + # ───────────────────────────────────────────── + # SATISFACTION & LOYALTY METRICS + # ───────────────────────────────────────────── + + - name: "Client NPS" + id: "nps-client" + category: "retention" + definition: "Net Promoter Score measured among the firm's client contacts, + indicating client satisfaction and likelihood to refer." + formula: "% Promoters (9-10) - % Detractors (0-6) on a 0-10 recommendation scale" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20" + signal: "Clients are dissatisfied or indifferent. Referrals will be rare and + churn is likely. The firm has a service quality or relationship + problem." + below_average: + value: "20-35" + signal: "Below average satisfaction. Some clients are happy, but a meaningful + portion would not recommend the firm." + average: + value: "35-50" + signal: "Acceptable satisfaction. Clients are generally content but the firm is + not generating the enthusiasm that drives organic referrals." + good: + value: "50-70" + signal: "Strong client advocacy. Clients actively recommend the firm to peers. + Referral pipeline should be healthy." + excellent: + value: "> 70" + signal: "Exceptional client loyalty. The firm is a trusted partner whose clients + enthusiastically advocate for it. This is the strongest growth engine + in professional services." + stage_notes: + seed: "Even with 3-5 clients, measuring NPS establishes a feedback discipline. + Use the qualitative follow-up question to understand what drives + satisfaction." + series_a: "At 15-30 clients, NPS becomes predictive. Segment by engagement type + (project vs. retainer) and client tier. Retainer client NPS should be + higher." + series_b_plus: "Mature agencies tie NPS to account manager performance and use + detractor feedback to drive operational improvements." + data_sources: + - source: "Hinge Research Institute High Growth Study" + year: "2023" + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + related_metrics: [ "client-retention-rate", "revenue-per-client" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "NPS in agencies is relationship-dependent — the score often reflects + the quality of the account manager or lead consultant rather than the firm + as a whole. Survey multiple contacts per client for a balanced view." + + - name: "Employee NPS (eNPS)" + id: "enps" + category: "retention" + definition: "Net Promoter Score measured among the firm's employees, indicating + satisfaction, engagement, and likelihood to recommend the firm as an + employer." + formula: "% Employee Promoters (9-10) - % Employee Detractors (0-6)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0" + signal: "More detractors than promoters. The firm has a serious culture, + compensation, or management problem. Attrition will accelerate." + below_average: + value: "0-15" + signal: "Net positive but weak. Employees are not enthusiastic advocates. + Vulnerability to external offers is high." + average: + value: "15-30" + signal: "Decent employee satisfaction. The firm is a reasonable place to work + but not a destination employer." + good: + value: "30-50" + signal: "Strong employee advocacy. Staff recommend the firm to talented friends + — a powerful recruiting advantage." + excellent: + value: "> 50" + signal: "Exceptional employer brand. Recruiting is easier, retention is strong, + and employee engagement drives client satisfaction." + stage_notes: + seed: "At under 10 people, formal eNPS is less relevant than direct, honest + conversations. Institute monthly check-ins with every team member." + series_a: "At 10-25 people, quarterly eNPS surveys provide a scalable feedback + mechanism. Pair quantitative scores with open-ended qualitative input." + series_b_plus: "At 50+, eNPS becomes a leading indicator of attrition, client + satisfaction, and firm performance. Track and act on it with the same + rigor as financial metrics." + data_sources: + - source: "Bureau of Labor Statistics — Professional Services" + year: "2024" + - source: "SPI Research Professional Services Maturity Benchmark" + year: "2024" + related_metrics: [ "employee-retention-rate", "nps-client" ] + related_skills: [ "organisational-culture", "psychological-safety-practice" ] + caveats: "eNPS is a lagging indicator — by the time it drops, the damage is + done. Pair eNPS with leading indicators: Glassdoor reviews, offer + acceptance rate, and informal sentiment from managers." diff --git a/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml new file mode 100644 index 0000000..2c9e63e --- /dev/null +++ b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-diagnostic-rules.yaml @@ -0,0 +1,1304 @@ +# Agency/Consulting Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in an agency/consulting context. +# The diagnostic agent loads these rules when the agency/consulting pack is active. +# +# Agency-specific diagnostic themes: +# - Founder-as-bottleneck: the personal capacity ceiling that limits growth +# - Client concentration risk: over-dependency on one or few clients +# - Utilization death spiral: hiring ahead of revenue, burning cash on bench time +# - Scope creep epidemic: systematic failure to hold project boundaries +# - Pricing floor trap: competing on price and destroying margins +# - Talent retention crisis: key people leaving and taking clients +# - Feast-or-famine revenue cycle: no pipeline management or revenue smoothing +# - Productization paralysis: wanting to productize but unable to stop custom work +# +# Adaptation types: +# as-is — The diagnostic works without modification for agencies. +# enhanced — The diagnostic is relevant but benefits from additional agency-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for agencies. + +pack_metadata: + sector: "agency-consulting" + display_name: "Agency / Consulting" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Client churn in agencies is fundamentally different from + subscription churn. Clients do not 'cancel' — they finish a project and do + not return, reduce retainer scope, bring work in-house, or quietly move to + a competitor. Churn in agencies is often invisible until the revenue + impact materializes months later. The triage must address agency-specific + churn drivers: relationship quality, deliverable satisfaction, internal + champion departure, budget cuts, and the ever-present threat of in-house + teams." + additional_triage_questions: + - question: "When clients leave, do they explicitly terminate (tell you they are + leaving) or silently attrit (stop calling, reduce scope, let the + retainer lapse without renewal)?" + purpose: "Silent attrition is far more common in agencies than explicit + termination. Clients avoid confrontation by gradually reducing + engagement. Detecting silent attrition requires proactive relationship + health monitoring." + routing_impact: "Silent attrition routes to trust-equation and + net-promoter-score for relationship health assessment. Explicit + termination routes to competitive-threat-diagnosis and root cause + analysis." + - question: "Has the departing client's internal champion (your primary contact) + changed roles, left the company, or been reorganized?" + purpose: "Agency relationships are person-to-person. When the champion leaves, + the relationship often dies — the replacement may have their own + agency preferences or may not value the existing engagement." + routing_impact: "Champion departure routes to stakeholder-map and relationship + diversification strategy. Ensure multiple relationships within each + client organization." + - question: "Are clients leaving because they are bringing the capability + in-house?" + purpose: "In-housing is the structural threat to agency models. If multiple + clients are building internal teams to replace agency services, the + agency's core offering may be commoditizing." + routing_impact: "In-housing trend routes to disruptive-innovation and + blue-ocean-strategy for repositioning above the in-house capability + level." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Relationship-driven churn" + reason: "In agencies, most churn is relationship-driven rather than + quality-driven. The work may be excellent, but if the client does + not feel personally valued, connected, and heard, they will move to + a firm that provides that feeling." + - diagnosis: "Value perception gap" + reason: "Agencies frequently fail to communicate the value they deliver. When + clients do not see the connection between agency fees and business + outcomes, they question the expenditure — especially during budget + reviews." + less_likely: + - diagnosis: "Product quality failure" + reason: "Agencies can adjust quality in real time through feedback loops. + Chronic quality failure is less common than relationship neglect or + value communication failure." + agency_specific_diagnoses: + - name: "Silent attrition — the invisible churn" + description: "Clients are not formally leaving but are gradually disengaging: + reducing retainer scope, declining project extensions, responding + slowly to outreach, and shifting work to other providers without + explicit notification." + symptoms: + - "Retainer scope reductions without clear explanation" + - "Longer gaps between engagements with previously active clients" + - "Client contacts becoming unresponsive to proactive outreach" + - "Revenue per client declining across the portfolio without explicit + client departures" + routes_to_skills: [ "trust-equation", "net-promoter-score", "connecting-with-people" ] + routes_to_templates: [ "quarterly-business-review", "project-status-update" ] + - name: "In-housing displacement" + description: "Clients are building internal teams to replace agency services. + This is a structural shift, not a temporary budget reallocation. The + agency's core service is being commoditized to the point where clients + prefer to hire permanent staff rather than pay agency rates." + symptoms: + - "Multiple clients hiring for roles that mirror the agency's core + service" + - "Clients requesting knowledge transfer or documentation of processes" + - "Budget objections citing 'we could hire someone full-time for what + we pay you annually'" + - "Decline concentrated in one service line rather than across the + board" + routes_to_skills: [ "disruptive-innovation", "blue-ocean-strategy", "product-life-cycle" ] + routes_to_templates: [ "strategic-analysis-one-pager", "proposal-outline" ] + sector_red_flags: + - "Client retention below 70% annually — the firm is on a treadmill, + replacing clients faster than it can deepen relationships." + - "Three or more clients reducing retainer scope in the same quarter — + early signal of a systemic value perception problem." + - "Key client champion departures without a relationship-transfer plan — + each departure is a churn risk that compounds if unaddressed." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Agency growth stalls have characteristic causes that + differ fundamentally from product business stalls. Agency growth is + constrained by three ceilings: the founder's personal capacity (cannot + sell and deliver simultaneously), talent availability (cannot hire fast + enough to meet demand), and client acquisition (pipeline dries up when + delivery consumes all attention). The most common stall pattern is the + feast-or-famine cycle — the agency is too busy delivering to develop new + business, then too desperate to be selective about incoming work." + additional_triage_questions: + - question: "Is the growth stall caused by insufficient demand (not enough clients + or projects) or insufficient capacity (demand exists but you cannot + deliver it)?" + purpose: "Demand-side stalls require sales and marketing investment. + Capacity-side stalls require hiring, subcontracting, or process + efficiency. These are opposite problems with opposite solutions." + routing_impact: "Demand stall routes to four-ps-marketing and business + development strategy. Capacity stall routes to shamrock-organisation + and delegation-and-empowerment for scaling delivery." + - question: "How many hours per week does the founder spend on non-billable + business development — and has this changed in the past 6 months?" + purpose: "The most common agency growth stall occurs when the founder becomes + consumed by delivery and stops developing new business. Revenue lags + 3-6 months later." + routing_impact: "Founder-consumed-by-delivery routes to eisenhower-matrix and + delegation-and-empowerment for immediate rebalancing." + - question: "Have you hit a revenue plateau where the firm has been stuck at + approximately the same level for 12+ months?" + purpose: "Revenue plateaus in agencies typically occur at predictable + thresholds: $500K (founder capacity ceiling), $1.5M-$2M (first + management layer needed), $5M (institutional processes required). Each + requires a structural change to break through." + routing_impact: "Plateau at $500K routes to delegation skills and first hires. + Plateau at $1.5M-$2M routes to leadership-pipeline and management + structure. Plateau at $5M routes to systems-thinking and + organizational design." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Founder-as-bottleneck" + reason: "The single most common agency growth stall. The founder cannot + simultaneously deliver outstanding work, manage the team, develop + new business, and run operations. Growth stops at the founder's + personal capacity." + - diagnosis: "Feast-or-famine revenue cycle" + reason: "Agencies without dedicated business development alternate between + overwhelming demand (no time to sell) and desperate pipeline gaps + (no work coming in). This cycle prevents steady growth." + less_likely: + - diagnosis: "Market saturation" + reason: "Professional services markets are enormous and fragmented. True market + saturation is rare — growth stalls in agencies are almost always + internal, not market-driven." + agency_specific_diagnoses: + - name: "Founder capacity ceiling" + description: "The agency has reached the maximum revenue the founder can + personally generate, oversee, and sell. Growth requires the founder to + delegate delivery, client relationships, or business development — but + the founder has not made this transition, either because they cannot + find people to delegate to or because they are unwilling to relinquish + control." + symptoms: + - "Revenue flat for 12+ months despite market demand" + - "Founder working 55+ hours per week with no capacity for additional + work" + - "New clients turned away or delayed because of founder availability" + - "No employee authorized to make client-facing decisions without + founder approval" + routes_to_skills: + [ + "delegation-and-empowerment", + "leadership-pipeline", + "shamrock-organisation" + ] + routes_to_templates: [ "weekly-ceo-review", "role-description-template" ] + - name: "Feast-or-famine revenue cycle" + description: "Revenue oscillates wildly between periods of overwhelming demand + and periods of painful underutilization. The cycle perpetuates because + the agency invests zero time in business development during busy + periods and panic-sells during quiet periods, producing low-quality + pipeline." + symptoms: + - "Revenue variance of 30%+ between best and worst quarters" + - "Business development activity inversely correlated with delivery + load" + - "Bench time spikes followed by capacity crunches requiring overtime + and rushed hiring" + - "Pipeline coverage ratio swinging between 1x and 5x across the year" + routes_to_skills: [ "balanced-scorecard", "scenario-planning", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "weekly-ceo-review" ] + - name: "Productization paralysis" + description: "The agency recognizes that productizing services (fixed-scope, + fixed-price, repeatable offerings) would improve margins and + scalability, but cannot stop accepting custom work long enough to + build the productized offering. Every time resources are allocated to + productization, a client project takes priority." + symptoms: + - "Productization initiative started but never completed (multiple + times)" + - "Custom work consistently prioritized over productization because it + generates immediate revenue" + - "Founder intellectually convinced of productization value but + operationally unable to execute" + - "No distinct pricing or packaging for the intended productized + service" + routes_to_skills: [ "business-model-canvas", "eisenhower-matrix", "disruptive-innovation" ] + routes_to_templates: [ "new-initiative-brief", "decision-rationale-memo" ] + sector_red_flags: + - "Founder billing more than 60% of available hours — growth is + structurally impossible at this utilization level because no time + remains for sales and management." + - "Zero dedicated business development time in the past 30 days — the + pipeline will empty within 3-6 months." + - "Revenue flat for 12+ months in a growing market — the stall is + internal, not market-driven." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Product-market fit in agencies translates to + 'service-market fit' — the alignment between the firm's expertise, + delivery model, and pricing with a specific client segment's needs and + willingness to pay. Unlike product PMF, which is measured through + retention curves and organic growth, service-market fit is measured + through client retention, referral volume, pricing power, and the ease of + winning new business within the target segment." + additional_triage_questions: + - question: "Is your referral pipeline healthy — do existing clients actively + recommend you to their peers, and do those referrals convert at a high + rate?" + purpose: "Referral volume and conversion are the strongest PMF signals in + professional services. Clients who refer are satisfied, and referred + prospects convert at high rates because trust transfers through the + referral." + routing_impact: "Low referral volume routes to net-promoter-score and + trust-equation for relationship assessment. High referral volume with + low conversion routes to four-ps-marketing for positioning and + messaging." + - question: "Can you charge premium rates (top 25% in your market) and still win + consistently?" + purpose: "Pricing power is the definitive PMF signal in agencies. If clients pay + premium rates without extensive negotiation, the firm has + service-market fit." + routing_impact: "Low pricing power despite good work routes to positioning and + specialization analysis. Premium pricing power routes to growth and + scaling strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Service-market fit exists for a niche but the firm is not focused on + it" + reason: "Most agencies have accidental PMF in a subsegment they have not + identified. Their best clients share characteristics (industry, + size, problem type) that the agency has not deliberately targeted." + less_likely: + - diagnosis: "The service has no market" + reason: "Professional services always have a market — someone always needs + expertise. The question is not whether a market exists but whether + the firm's specific combination of expertise, positioning, and + pricing matches a specific buyer's needs." + agency_specific_diagnoses: + - name: "Accidental niche PMF" + description: "The agency has strong service-market fit in a specific niche + (industry vertical, company size, problem type) but has not recognized + or deliberately pursued it. The best clients, highest retention, and + strongest referrals all cluster in one segment that the firm treats as + just another part of its undifferentiated client base." + symptoms: + - "Highest-NPS clients share common characteristics (industry, size, + problem type)" + - "Best referrals come from a specific client cluster" + - "Win rate dramatically higher in one segment than others" + - "The firm describes itself as a generalist but 40%+ of revenue comes + from one recognizable segment" + routes_to_skills: + [ + "blue-ocean-strategy", + "business-model-canvas", + "strategic-thinking-and-alignment" + ] + routes_to_templates: [ "strategic-analysis-one-pager", "market-opportunity-summary" ] + sector_red_flags: + - "No referrals in the past quarter despite having active clients — a + strong signal that service-market fit is weak." + - "Win rate below 20% — the firm's positioning, pricing, or targeting is + misaligned with the prospects it pursues." + - "Unable to articulate what makes the firm different from competitors in + one sentence — a clarity problem that undermines every pitch." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Pricing is the most consequential strategic decision in + agencies and the one most systematically mismanaged. The agency pricing + spectrum — from hourly billing to value-based pricing — fundamentally + determines revenue per employee, margin structure, client relationships, + and scalability. Most agencies are severely underpriced because founders + set rates based on their previous salary plus a margin, rather than on the + value they deliver. The diagnosis must evaluate not just the price level + but the pricing model itself." + additional_triage_questions: + - question: "What is your current pricing model — hourly, project-based, retainer, + value-based, or a mix — and why did you choose it?" + purpose: "Most agencies default to hourly or project pricing without evaluating + alternatives. Each model has distinct economic characteristics that + affect utilization pressure, scope management, and revenue + predictability." + routing_impact: "Hourly pricing routes to evaluation of value-based or + project-based alternatives. Fixed-price with frequent overruns routes + to scoping and change-order process improvement. Retainer with low + utilization routes to retainer restructuring." + - question: "When was the last time you raised rates, and what was the client + response?" + purpose: "Many agencies have not raised rates in years. The clients' response to + price increases is almost always less negative than the agency fears — + and reveals pricing power (or lack thereof)." + routing_impact: "Never raised rates routes to immediate pricing analysis. Raised + rates with no pushback routes to further increases. Raised rates and + lost clients routes to value communication and positioning + improvement." + - question: "What is your effective billable rate — the actual revenue per hour + worked on client projects after discounts, write-offs, and scope + overruns?" + purpose: "The gap between standard rate and effective rate reveals the true + pricing problem. A firm with a $200/hour rate and a $130/hour + effective rate does not have a pricing problem — it has a scope + management and discounting problem." + routing_impact: "Gap exceeding 25% routes to scope-creep and discounting + diagnosis. Gap under 10% with still-low margins routes to rate + increase strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Chronic underpricing" + reason: "The default error in agencies is underpricing. Founders anchor on their + previous salary, competitor rates, or what 'feels fair' rather than + on the value delivered. Most agencies capture 15-30% of the value + they create for clients." + - diagnosis: "Pricing model mismatch" + reason: "Many agencies use hourly billing for strategic work (which penalizes + speed and expertise) or project pricing for unpredictable work + (which guarantees overruns). The model must match the work type." + less_likely: + - diagnosis: "Overpricing relative to value" + reason: "Genuine overpricing in agencies is rare. What appears as a 'too + expensive' objection is almost always a value communication failure + — the prospect does not understand the value, not that the value + does not exist." + agency_specific_diagnoses: + - name: "Pricing floor trap" + description: "The agency has positioned itself at the low end of the market — + competing on price against freelancers and offshore teams. Low rates + attract cost-sensitive clients who demand more for less, negotiate + aggressively, and churn at the first sign of a cheaper alternative. + The firm cannot invest in talent, quality, or business development + because margins are too thin." + symptoms: + - "Rates in the bottom quartile for the firm's market and discipline" + - "Win rate high but margins thin — winning through price, not through + value" + - "Client objections focus on cost rather than outcomes" + - "Unable to attract or retain senior talent because compensation is + not competitive" + - "Competing regularly against freelancers and offshore teams" + routes_to_skills: + - blue-ocean-strategy + - porters-five-forces + routes_to_templates: [ "unit-economics-snapshot", "strategic-analysis-one-pager" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "Effective billable rate below 65% of standard rate — scope creep and + discounting are destroying the pricing strategy." + - "Rates unchanged for 24+ months — the firm is almost certainly leaving + money on the table." + - "Revenue per employee below $120K — a mathematical indicator that rates, + utilization, or both are critically low." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Most agencies do not raise venture capital — and should + not. Agency economics (linear scaling, people-dependent) do not fit the VC + model (exponential scaling, technology-dependent). However, agencies do + seek capital through bank loans, lines of credit, revenue-based financing, + SBA loans, partnership buyins/buyouts, and occasionally strategic + investors. The fundraising diagnostic must be reframed entirely for these + capital sources, which have different requirements, metrics, and + expectations than venture capital." + additional_triage_questions: + - question: "What is the capital for — bridging a cash flow gap (AR financing), + funding growth (hiring ahead of demand), acquiring another firm, or + buying out a partner?" + purpose: "Each capital need has a different optimal source. AR financing + requires a line of credit. Growth hiring requires revenue-based + financing or retained earnings. Acquisitions require a term loan or + investor. Partner buyouts require structured financing." + routing_impact: "Cash flow gap routes to AR management and line-of-credit + options. Growth hiring routes to revenue-based financing and + scenario-planning. Acquisition routes to M&A analysis. Partner buyout + routes to negotiation skills and structured deal design." + - question: "What is the firm's current EBITDA margin and debt capacity?" + purpose: "Lenders evaluate agencies primarily on profitability and cash flow + stability — not growth rate. An agency with 15% EBITDA margin and + stable revenue can access more favorable lending terms than a + faster-growing but unprofitable one." + routing_impact: "Healthy EBITDA routes to bank financing options. Low EBITDA + routes to profitability improvement before seeking capital." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Cash flow timing mismatch" + reason: "The most common 'capital need' in agencies is not growth financing but + cash flow management — the gap between when payroll is due and when + clients pay. A line of credit or improved AR processes often solves + this without external capital." + - diagnosis: "Over-capitalization temptation" + reason: "Agencies seeking external capital often want to hire ahead of demand. + This is dangerous in services because idle talent burns cash + immediately, unlike product inventory which retains some value." + less_likely: + - diagnosis: "Need for venture capital" + reason: "Traditional agency models are incompatible with VC expectations. + VC-compatible agency models require a productized or technology + component that enables non-linear scaling." + agency_specific_diagnoses: + - name: "Utilization death spiral" + description: "The agency raised capital or used retained earnings to hire ahead + of demand, but the expected demand did not materialize. Bench time + consumes cash, pressure to fill capacity leads to accepting low-margin + or off-strategy work, which diverts senior attention from business + development, which further reduces high-quality pipeline." + symptoms: + - "Bench time above 20% for more than one quarter" + - "Accepting work below minimum rate or outside the firm's positioning + to fill capacity" + - "Cash burn rate accelerating despite stable or growing revenue" + - "New hires underutilized while existing staff are overloaded + (indicating a skills or client mismatch)" + routes_to_skills: [ "scenario-planning", "shamrock-organisation", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "decision-rationale-memo" ] + sector_red_flags: + - "Seeking VC funding for a traditional agency model — the economics do + not support venture returns and the resulting pressure will distort the + business." + - "Hiring more than 3 people simultaneously without confirmed pipeline to + support them — high risk of utilization death spiral." + - "AR exceeding 60 days while also seeking external capital — fix the + collection problem before adding new capital." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Agency revenue decomposes differently from product + revenue. The components are: project revenue (discrete engagements with + defined scope), retainer revenue (recurring monthly fees for ongoing + work), hourly overflow (ad hoc billing beyond scope), and productized + revenue (fixed-price packaged services). Healthy agencies diversify across + these streams, with retainer revenue providing stability and project + revenue providing growth. The diagnosis must evaluate both the total + revenue and the quality of the revenue mix." + additional_triage_questions: + - question: "What percentage of your revenue is recurring (retainers and ongoing + contracts) versus project-based (discrete engagements)?" + purpose: "Revenue predictability determines the firm's ability to plan, hire, + and invest. A firm with 60%+ recurring revenue can plan confidently. A + firm with 80%+ project revenue lives in perpetual uncertainty." + routing_impact: "Low recurring revenue routes to retainer development strategy + and client-relationship deepening. High recurring revenue with + stagnant growth routes to new client acquisition and pipeline + development." + - question: "What is your revenue concentration — what percentage comes from your + top 3 clients?" + purpose: "Client concentration is the primary revenue risk in agencies. If the + top 3 clients represent more than 50% of revenue, any single departure + creates a crisis." + routing_impact: "Concentration above 50% routes to immediate diversification + strategy and client-acquisition investment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Revenue quality deterioration" + reason: "Agency revenue can grow in total while deteriorating in quality — more + project work (unpredictable), smaller average project sizes (higher + overhead), and lower rates (price competition). Total revenue masks + these trends." + - diagnosis: "Client concentration creating fragility" + reason: "Many agencies grow revenue by deepening a few client relationships + rather than broadening the client base. This concentrates risk + dangerously." + less_likely: + - diagnosis: "Market-wide demand decline" + reason: "Professional services demand is remarkably resilient. Even in + recessions, organizations need external expertise. Revenue problems + in agencies are almost always firm-specific, not market-wide." + agency_specific_diagnoses: + - name: "Retainer erosion" + description: "Retainer revenue — the foundation of agency stability — is + declining as clients reduce scope, pause engagements, or shift to + project-based relationships. The firm's revenue is becoming + increasingly unpredictable and project-dependent." + symptoms: + - "Retainer revenue declining as a percentage of total revenue" + - "Average retainer duration shortening" + - "Clients requesting 'project-based' pricing for work previously on + retainer" + - "Revenue forecasting accuracy declining (more misses, wider + variance)" + routes_to_skills: + - net-promoter-score + - trust-equation + routes_to_templates: [ "quarterly-business-review", "service-level-agreement" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "Top 3 clients representing more than 50% of revenue — one departure + creates a survival crisis." + - "Recurring revenue below 30% of total — the firm has no revenue floor + and will suffer in any demand downturn." + - "Average project value declining quarter over quarter — the firm is + accepting smaller, less profitable work." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency competitive threats come from four distinct + directions: other agencies (traditional competitors), freelancers and + contractor collectives (lower cost), in-house teams (client + self-sufficiency), and AI tools (automation of agency deliverables). Each + threat requires a different response, and agencies often focus exclusively + on agency-to-agency competition while ignoring the more dangerous + structural threats." + additional_triage_questions: + - question: "Which competitive threat is most active: another agency winning your + clients, freelancers undercutting your rates, clients building + in-house teams, or AI tools replacing your services?" + purpose: "Each threat type requires a different strategic response. Agency + competition requires differentiation. Freelancer competition requires + value demonstration. In-housing requires elevation to strategic + advisory. AI competition requires integration and repositioning." + routing_impact: "Agency competition routes to blue-ocean-strategy and + positioning refinement. Freelancer/AI competition routes to + disruptive-innovation and value-stacking above automation. In-housing + routes to strategic advisory repositioning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "In-house team displacement" + reason: "The greatest long-term threat to agencies is not other agencies but + clients deciding they can do the work themselves. When multiple + clients build internal teams, it signals that the agency's service + has commoditized." + - diagnosis: "AI disruption of commodity services" + reason: "AI tools are rapidly replacing tasks that agencies bill for: + copywriting, basic design, data analysis, media planning, and code + generation. Agencies that bill for execution rather than strategy + face existential AI risk." + less_likely: + - diagnosis: "Price-based competitive displacement by another agency" + reason: "Losing clients purely on price to another agency is rare if the + relationship is strong. Agencies lose on price when they have failed + to build relationship depth or demonstrate differentiated value." + agency_specific_diagnoses: + - name: "AI commoditization threat" + description: "AI tools are performing tasks that constitute a significant + portion of the agency's billable work. Clients are beginning to + question why they pay agency rates for work that AI can approximate. + The threat is not that AI replaces the agency entirely, but that it + compresses the scope and value of what clients are willing to + outsource." + symptoms: + - "Clients mentioning AI tools as alternatives during negotiations" + - "Reduction in demand for specific deliverable types (e.g., basic + content, simple designs)" + - "Prospects asking whether the agency uses AI and why they should pay + human rates" + - "Junior staff work increasingly automatable, threatening the + leverage model" + routes_to_skills: [ "disruptive-innovation", "ai-vision-and-strategy", "blue-ocean-strategy" ] + routes_to_templates: [ "strategic-analysis-one-pager", "competitive-landscape-brief" ] + sector_red_flags: + - "Three or more clients building in-house versions of the agency's core + service in the same year — structural displacement is underway." + - "Win rate declining against freelancers or small firms — the agency's + overhead is not justified by sufficient value differentiation." + - "AI-generated deliverables achieving 'good enough' quality for tasks + that constitute more than 30% of the agency's billable hours." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Strategic drift in agencies manifests as 'everything for + everyone' syndrome — the firm accepts any work from any client, gradually + losing its positioning and becoming an undifferentiated generalist. The + temptation is structural: declining a $50K project because it is + 'off-strategy' feels irresponsible when payroll is due. Strategic drift in + agencies is the accumulated result of hundreds of small, individually + rational decisions to take the work that is available rather than the work + that builds the firm's positioning." + additional_triage_questions: + - question: "Can you describe your ideal client and ideal project in one sentence + each — and does more than 50% of your current revenue come from that + profile?" + purpose: "The ability to articulate a clear ideal client is a positioning litmus + test. If less than 50% of revenue fits the ideal profile, the firm has + drifted." + routing_impact: "Unable to articulate routes to blue-ocean-strategy and + strategic-thinking-and-alignment for positioning development. Can + articulate but low alignment routes to disciplined client selection + and off-strategy work reduction." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Revenue-driven drift — accepting anything that pays" + reason: "The most common drift mechanism in agencies. Each off-strategy project + seems harmless individually but collectively erodes the firm's + positioning, stretches capabilities, and prevents specialization." + less_likely: + - diagnosis: "Market disruption causing strategic irrelevance" + reason: "Agency strategic drift is almost always self-inflicted through lack of + discipline rather than externally caused. The market did not change + — the firm's discipline did." + agency_specific_diagnoses: + - name: "Scope-of-service sprawl" + description: "The agency has gradually expanded its service offerings in + response to client requests until it offers everything from strategy + to execution across multiple disciplines. Each service line is staffed + by one or two people, none of whom are world-class. The firm competes + as a generalist against specialists in every discipline and loses on + quality while maintaining the overhead of multiple capabilities." + symptoms: + - "More than 6 distinct service offerings with no shared methodology + or positioning" + - "Each service line staffed by fewer than 3 people" + - "Difficulty describing what the firm 'does' in a single sentence" + - "Winning work primarily through existing relationships rather than + expertise-based positioning" + routes_to_skills: [ "blue-ocean-strategy", "porters-five-forces", "eisenhower-matrix" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] + sector_red_flags: + - "Unable to decline any project regardless of fit — a sign that financial + pressure has overridden strategic discipline." + - "The firm's website lists more than 8 service categories — typically an + indicator of everything-for-everyone positioning." + - "Revenue spread evenly across unrelated industries and service types + with no identifiable specialization." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency team dysfunction has characteristic patterns + driven by the client-service nature of the business. The most common + dysfunctions: account managers over-promise while delivery teams + under-deliver, senior staff hoard client relationships while junior staff + feel excluded, creative/strategy teams and execution teams operate in + silos, and the pressure to be billable suppresses the collaborative, + unbillable time that builds team cohesion." + additional_triage_questions: + - question: "Is there tension between the people who sell work (partners, account + managers) and the people who deliver it (creatives, developers, + consultants) — specifically, are commitments made during the sales + process that delivery cannot fulfill?" + purpose: "The sell-deliver gap is the most common and most damaging agency + dysfunction. It creates impossible expectations, frustrated delivery + teams, disappointed clients, and mutual blame between functions." + routing_impact: "Sell-deliver misalignment routes to cooperative-negotiation for + internal process redesign and trust-equation for rebuilding internal + trust between functions." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Sell-deliver gap" + reason: "Agency sales incentives (winning the pitch) and delivery incentives + (quality within scope) are structurally misaligned. Without + deliberate processes to reconcile these, tension is inevitable." + - diagnosis: "Burnout-driven dysfunction" + reason: "Agency work involves high emotional labor (demanding clients, tight + deadlines, personal investment in creative output). Teams that are + consistently overutilized degrade in collaboration, quality, and + morale." + less_likely: + - diagnosis: "Insufficient talent" + reason: "What appears as talent insufficiency in agencies is often a systems + problem: talented people performing poorly because of unclear + priorities, impossible workloads, or dysfunctional processes." + agency_specific_diagnoses: + - name: "Talent retention crisis — key people leaving and taking clients" + description: "Senior staff with deep client relationships are departing — and + taking clients with them. The firm's client base is hollowing out as + the people who are the firm's product walk out the door." + symptoms: + - "Senior employee departures followed by client departures within 3-6 + months" + - "Clients requesting specific individuals rather than engaging the + firm as an institution" + - "No non-compete or non-solicit agreements in employment contracts" + - "Client relationships concentrated in individual employees rather + than distributed across the firm" + routes_to_skills: [ "inspiring-and-retaining", "organisational-culture", "trust-equation" ] + routes_to_templates: [ "hiring-scorecard", "team-health-check" ] + sector_red_flags: + - "Delivery team attrition above 25% — the firm cannot maintain quality or + client relationships with this level of turnover." + - "Account manager making commitments to clients without delivery team + input — a structural sell-deliver gap." + - "Key person dependency — any individual whose departure would directly + cause client loss." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency co-founder (and co-partner) conflicts cluster + around four issues: client ownership (who 'owns' which relationships), + revenue contribution (who brings in more business), role boundaries (who + decides what), and strategic direction (generalist vs. specialist, growth + vs. lifestyle). The personal nature of agency work makes these conflicts + particularly intense — each partner's contribution is directly measurable + through billings and client retention." + additional_triage_questions: + - question: "Is the conflict about strategic direction (what the firm should + become), revenue contribution (who generates more business), or + operational authority (who decides how work is done)?" + purpose: "Each conflict type requires different intervention. Strategic + conflicts need facilitated alignment sessions. Revenue contribution + disputes need transparent metrics and equitable compensation + structures. Authority conflicts need explicit role definitions." + routing_impact: "Strategic direction routes to strategic-thinking-and-alignment + and scenario-planning. Revenue contribution routes to + balanced-scorecard with transparent partner metrics. Authority routes + to delegation-and-empowerment and explicit role documentation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Unequal contribution resentment" + reason: "In agencies, each partner's contribution is visible — billings, clients + brought in, people managed. When one partner perceives an imbalance, + resentment builds rapidly." + less_likely: + - diagnosis: "Vision misalignment" + reason: "Most agency partnership conflicts are operational, not visionary. + Partners usually agree on what a good agency looks like — they + disagree on roles, compensation, and authority." + agency_specific_diagnoses: + - name: "Partner lifestyle mismatch" + description: "One partner wants to grow aggressively (hire, take on debt, pursue + large clients) while the other wants to maintain a lifestyle practice + (stable income, manageable hours, select clients). Neither goal is + wrong, but they are incompatible in a single firm." + symptoms: + - "Recurring arguments about hiring decisions, debt, and investment" + - "One partner working significantly more hours than the other" + - "Disagreement about whether to take on large, risky opportunities" + - "One partner subtly sabotaging growth initiatives or cost-cutting + measures" + routes_to_skills: [ "cooperative-negotiation", "evaluating-and-deciding", "covey-seven-habits" ] + routes_to_templates: [ "decision-rationale-memo", "quarterly-strategic-review" ] + sector_red_flags: + - "Partners communicating through staff rather than directly — a sign the + conflict has become personal." + - "Key staff choosing sides — the conflict is contaminating the entire + organization." + - "One partner quietly meeting with clients to establish independent + relationships — possible prelude to a split." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Market entry for agencies means entering a new vertical, + a new service line, or a new geographic market. Unlike product companies, + agencies can 'enter' a new market by winning a single client — but + sustaining that entry requires building credible expertise and a + reference-worthy track record. The key question is always: can the firm + build sufficient credibility in the new market to win competitively, or + will it always be an outsider competing against firms with deeper domain + expertise?" + additional_triage_questions: + - question: "Do you have at least one reference client in the target market — + someone who can vouch for your work in this specific context?" + purpose: "Agency market entry without a reference client is nearly impossible. + Prospects in any market want to see proof of domain experience. The + first reference client is the gateway." + routing_impact: "No reference client routes to a landing strategy: discounted or + pro-bono first engagement to build the reference. Existing reference + routes to targeted outreach using the case study." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Credibility gap in the target market" + reason: "Agencies entering new verticals face the 'but have you done this in our + industry?' objection. Overcoming the credibility gap is the primary + market-entry challenge." + less_likely: + - diagnosis: "Inadequate market size" + reason: "Most professional services verticals are large enough to support + multiple agencies. Market size is rarely the barrier — credibility + and relationships are." + agency_specific_diagnoses: [] + sector_red_flags: + - "Entering a new market without a single reference client or case study — + nearly impossible to win competitive pitches without proof of domain + expertise." + - "Adding a new service line without hiring someone who has delivered it + before — quality risk is high." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency hiring is uniquely consequential because every + hire directly affects delivery capacity, client relationships, and + revenue. Hiring too slow means turning away work; hiring too fast means + paying for bench time. The critical agency hiring decisions: when to add + the first non-billable role (operations, office management), when to hire + senior versus junior (the leverage decision), and when to hire full-time + versus freelance (the Shamrock decision)." + additional_triage_questions: + - question: "Is this hire intended to fill existing billable demand (you have work + waiting) or to build capacity for expected future demand (you hope + work will come)?" + purpose: "Hiring against existing demand is low-risk. Hiring against expected + demand is speculative — and the most common cause of utilization death + spirals in agencies." + routing_impact: "Hiring against existing demand routes to rapid hiring + execution. Hiring speculatively routes to scenario-planning and the + decision to use freelancers instead of full-time hires until demand is + confirmed." + - question: "Are you hiring a 'doer' (someone to produce work) or a 'grower' + (someone to bring in and manage client relationships)?" + purpose: "Agencies need both but often hire doers when they need growers. A firm + at capacity that hires another developer when it needs a business + developer will not solve its growth problem." + routing_impact: "Doer hire routes to utilization and leverage optimization. + Grower hire routes to business development strategy and + role-description-template." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Hiring doers when the firm needs growers" + reason: "Agencies default to hiring the type of person the founder is — usually + a practitioner. But growth requires people who can sell, manage + relationships, and develop business." + - diagnosis: "Hiring full-time when freelancers would suffice" + reason: "Many agency hiring 'needs' are actually surge-capacity needs that the + Shamrock model (freelancers) handles more efficiently than permanent + headcount." + less_likely: + - diagnosis: "Compensation insufficient to attract talent" + reason: "While agency salaries are often lower than tech company salaries, + talented people choose agencies for variety, autonomy, and + interesting work. Compensation is rarely the binding constraint." + agency_specific_diagnoses: [] + sector_red_flags: + - "Hiring three or more people simultaneously without confirmed project + pipeline — high risk of bench-time crisis." + - "First senior hire (VP, Director level) without a clear mandate and + success criteria — expensive failure is likely." + - "Every new hire being a practitioner with zero hires in business + development or operations — the firm will hit a growth ceiling." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency operational chaos manifests as missed deadlines, + inaccurate time tracking, billing disputes, resource conflicts (multiple + projects competing for the same person), and communication breakdowns + between account management and delivery. Unlike product companies where + operations center on technology infrastructure, agency operations center + on people management — scheduling, utilization tracking, project + profitability monitoring, and capacity planning." + additional_triage_questions: + - question: "Do you have a resource management system — a way to see who is + assigned to what, who is available, and what capacity exists for new + work?" + purpose: "Most agencies under 20 people have no formal resource management. Work + assignments happen through hallway conversations, Slack messages, and + the founder's mental model. This breaks at scale." + routing_impact: "No resource management routes to immediate process + implementation. Existing system with poor adoption routes to process + enforcement and training." + - question: "What percentage of projects deliver on time, on scope, and on budget?" + purpose: "On-time, on-scope, on-budget delivery is the operational health metric + for agencies. Below 60% indicates systemic operational problems." + routing_impact: "Below 60% routes to systems-thinking for root cause analysis + and action-plan for structured improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Scope creep epidemic" + reason: "The most common operational chaos in agencies is unmanaged scope + expansion — work grows beyond the original agreement without + corresponding billing, eating into margins project by project." + less_likely: + - diagnosis: "Technology failure" + reason: "Agencies rarely fail because of technology. They fail because of people + management, scoping, and process problems." + agency_specific_diagnoses: + - name: "Scope creep epidemic" + description: "The majority of projects systematically exceed their original + scope, budget, and timeline. The firm absorbs the overruns without + billing, effectively subsidizing client work with agency profits. Root + causes include: optimistic scoping, unclear contracts, inability to + say no to client requests, and lack of change-order processes." + symptoms: + - "More than 40% of projects exceeding scope by more than 15%" + - "No formal change-order process or the process exists but is rarely + invoked" + - "Effective billable rate more than 20% below standard rate" + - "Project managers reporting they feel unable to push back on client + scope additions" + - "Client expectations consistently exceed what was agreed in the SOW" + routes_to_skills: [ "competitive-negotiation", "delivering-the-deal", "systems-thinking" ] + routes_to_templates: [ "service-level-agreement", "project-kickoff-document" ] + sector_red_flags: + - "No time tracking system or time tracked but not reviewed — the firm is + flying blind on utilization and project profitability." + - "More than 40% of projects exceeding scope — systemic scoping or + boundary-setting failure." + - "AR exceeding 60 days — operational cash flow crisis building." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Leadership crises in agencies are amplified by the + founder-as-product dynamic. When the founder burns out, the firm's primary + sales channel, quality assurance mechanism, and client relationship + manager all degrade simultaneously. Agency leadership crises also occur + during partnership disputes, when key clients threaten to leave, or when + the founder must transition from practitioner to manager — a transition + many founders resist or fail." + additional_triage_questions: + - question: "Is the leadership crisis driven by founder burnout (overwork and + exhaustion), a partnership conflict, or a failure to transition from + practitioner to manager?" + purpose: "Each crisis type requires different intervention. Burnout requires + immediate workload reduction. Partnership conflict requires mediation + or structured separation. Transition failure requires coaching and + delegation support." + routing_impact: "Burnout routes to founder-mental-health-check and immediate + delegation. Partnership conflict routes to + cofounder-conflict-diagnosis. Transition failure routes to + delegation-and-empowerment and leadership-pipeline." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Founder burnout" + reason: "Agency founders work extremely long hours, carry emotional weight of + client relationships, and often feel they cannot step back without + the business collapsing. Burnout is endemic." + less_likely: + - diagnosis: "External leadership crisis (board pressure, investor conflict)" + reason: "Most agencies do not have boards or external investors. Leadership + crises are internal — between founders, between partners, or within + the founder's own capacity." + agency_specific_diagnoses: [] + sector_red_flags: + - "Founder working 60+ hours per week for more than 6 consecutive months — + burnout is imminent." + - "Founder avoiding difficult decisions (pricing, hiring, firing, client + conversations) — decision fatigue indicating deeper leadership + exhaustion." + - "Key leadership departure without a succession plan — the departure may + cascade to additional losses." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Decision paralysis in agencies often centers on the + growth-versus-lifestyle choice, pricing decisions (afraid to raise rates), + specialization decisions (afraid to narrow the offering), and hiring + decisions (afraid to commit to permanent overhead). These decisions feel + high-stakes because they are highly personal — they directly affect the + founder's income, workload, and identity." + additional_triage_questions: + - question: "Which decision has been deferred longest — and what is the cost of + continued delay?" + purpose: "Naming the deferred decision and quantifying its cost often provides + the urgency needed to act." + routing_impact: "Pricing decision deferred routes to pricing-diagnosis with + urgency framing. Growth/lifestyle decision deferred routes to + covey-seven-habits for 'Begin with the End in Mind' exercise." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Fear of irreversibility" + reason: "Agency founders often treat reversible decisions as irreversible. + Raising rates, narrowing the offering, or hiring a new role feel + permanent but are almost always adjustable." + less_likely: + - diagnosis: "Insufficient information" + reason: "Agency decisions rarely require more data. The founder usually knows + what to do — the barrier is emotional, not informational." + agency_specific_diagnoses: [] + sector_red_flags: + - "Pricing unchanged for 24+ months while costs have risen — the decision + to raise rates has been paralyzed by fear." + - "Specialization discussed for years but never implemented — the firm + remains a generalist because the decision to narrow feels risky." + - "Key hire identified but not made for 6+ months — paralysis is + constraining growth." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency innovation drought manifests as stale service + offerings, outdated methodologies, and failure to adopt new tools and + approaches. Client work consumes all capacity, leaving nothing for R&D, + experimentation, or new service development. The result: the firm delivers + the same services it offered five years ago while the market evolves + around it." + additional_triage_questions: + - question: "What new service, methodology, or capability has the firm developed + in the past 12 months — not for a client, but as a proactive + investment?" + purpose: "If the answer is 'nothing,' the firm is coasting on past innovation. + Every year without proactive investment in new capabilities increases + the risk of commoditization." + routing_impact: "No recent innovation routes to eisenhower-matrix for capacity + creation and doblin-ten-types for innovation opportunity + identification." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Client delivery consuming all innovation capacity" + reason: "The classic agency trap: 100% of capacity is consumed by client work, + leaving zero for R&D, new service development, or methodology + refinement." + less_likely: + - diagnosis: "Lack of creative talent" + reason: "Agency teams are typically creative and capable. Innovation drought is + a capacity and prioritization problem, not a talent problem." + agency_specific_diagnoses: [] + sector_red_flags: + - "No internal R&D or innovation time allocated in the past year — the + firm is running entirely on legacy capabilities." + - "Competitors adopting AI, new methodologies, or new service models while + the firm's offering remains static." + - "Clients asking about capabilities the firm does not have — the market + is signaling unmet needs." + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency partnerships operate differently from product + partnerships. Agency partnerships include: referral partnerships (firms + that send clients to each other), subcontracting relationships (firms that + extend each other's capacity), technology partnerships (platforms and + tools that the agency implements), and strategic alliances (firms that + collaborate on large opportunities neither could win alone). The most + valuable agency partnerships are reciprocal referral relationships with + complementary firms — they generate the highest-quality leads at the + lowest cost." + additional_triage_questions: + - question: "Is this a referral partnership (you send each other clients), a + delivery partnership (you subcontract to each other), or a technology + partnership (you implement their platform)?" + purpose: "Each partnership type has different value dynamics and risks. Referral + partnerships are low-risk, high-value. Delivery partnerships require + quality alignment. Technology partnerships create dependency." + routing_impact: "Referral partnerships route to cooperative-negotiation for + mutual benefit structuring. Delivery partnerships route to + shamrock-organisation for quality management. Technology partnerships + route to information-asymmetry for dependency risk assessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Informal partnerships that lack structure" + reason: "Most agency partnerships are handshake arrangements without clear + expectations, referral tracking, or reciprocity metrics. They + atrophy because neither party manages them actively." + less_likely: + - diagnosis: "Fundamentally incompatible partners" + reason: "Agency partnership failures are usually about neglect and misaligned + expectations, not fundamental incompatibility." + agency_specific_diagnoses: [] + sector_red_flags: + - "Technology partnership creating revenue dependency — more than 40% of + revenue comes from implementing a single platform." + - "One-sided referral relationship — the agency sends referrals but never + receives them." + - "Partnership agreements without defined terms, referral fees, or + accountability mechanisms." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Communication in agencies operates on two axes + simultaneously: internal communication (between partners, account + managers, and delivery teams) and external communication (with clients). + Breakdowns on either axis damage the business, but the interaction between + the two is where the most damaging failures occur — for example, when + internal miscommunication about project scope leads to incorrect client + expectations." + additional_triage_questions: + - question: "Is the communication breakdown primarily internal (team members not + aligned on scope, priorities, or timelines) or external (client + expectations not matching what is being delivered)?" + purpose: "Internal breakdowns require process and tool fixes. External + breakdowns require client communication protocol redesign." + routing_impact: "Internal breakdown routes to team process improvement. External + breakdown routes to client communication cadence and expectation + management." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Internal-external communication disconnect" + reason: "The most damaging communication breakdown in agencies occurs when the + account team and the delivery team have different understandings of + what was agreed with the client." + less_likely: + - diagnosis: "Technology-driven communication failure" + reason: "Agency communication failures are almost never about tools. They are + about processes, habits, and the cultural norms around + transparency." + agency_specific_diagnoses: [] + sector_red_flags: + - "Client complaints about 'not knowing what is happening' on their + projects — a project communication cadence failure." + - "Delivery team and account team disagreeing about project scope in front + of the client — internal alignment failure." + - "Critical information communicated verbally but never documented — + leading to 'I thought you said' disputes." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency negotiations get stuck in predictable ways: scope + negotiations where the client wants more work for the same price, rate + negotiations where procurement demands discounts the agency cannot absorb, + contract negotiations where legal terms (liability, IP ownership, + indemnification) create impasses, and internal negotiations where partners + disagree on strategic direction or resource allocation." + additional_triage_questions: + - question: "Is the negotiation stuck on scope (what you will deliver), price + (what they will pay), terms (contractual conditions), or timing (when + work starts or payment is due)?" + purpose: "Each stall type has different resolution tactics. Scope stalls resolve + through phased delivery. Price stalls resolve through value reframing. + Terms stalls require creative legal solutions. Timing stalls require + urgency creation." + routing_impact: "Scope stalls route to phased-proposal design. Price stalls + route to value-based reframing and competitive-negotiation. Terms + stalls route to delivering-the-deal with emphasis on flexible contract + templates." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Scope-price deadlock" + reason: "The most common agency negotiation stall: the client wants more than + the budget allows. The resolution is usually scope reduction, phased + delivery, or value-based justification for the higher investment." + less_likely: + - diagnosis: "Fundamental value disagreement" + reason: "If the client is negotiating, they have already decided the agency + provides value. The stall is about terms, not about whether to + engage." + agency_specific_diagnoses: [] + sector_red_flags: + - "Proposals stalling for 60+ days without resolution — the client may be + using the proposal to justify an internal budget or benchmark another + vendor." + - "Procurement demanding rate reductions below the firm's cost floor — + this is not a negotiation, it is a signal that the client values cost + over quality." + - "Internal partner negotiation about firm direction stalled for 6+ months + — the firm is paralyzed." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Agency culture is uniquely vulnerable because the work is + intensely personal, client demands create constant external pressure, and + the creative/strategic professionals who drive agency value are highly + sensitive to cultural degradation. Culture erosion in agencies often + begins when the firm prioritizes client satisfaction over employee + experience — accepting unreasonable client demands, tolerating abusive + client behavior, and burning teams on impossible deadlines to maintain + client relationships." + additional_triage_questions: + - question: "Has the firm accepted client behavior (yelling, unreasonable + deadlines, scope abuse, disrespect) that undermines team morale — and + if so, why?" + purpose: "Agencies often tolerate client behavior they would never accept from + an employee because the client represents revenue. This tolerance + sends a message to the team: the client matters more than you do." + routing_impact: "Client behavior tolerance routes to trust-equation and + boundary-setting frameworks. The agency must be willing to fire toxic + clients to protect culture." + - question: "Has the firm's growth outpaced its ability to maintain the culture + that attracted early employees?" + purpose: "The culture that works at 5 people (founder-led, informal, + family-like) does not work at 25 people. Culture must be deliberately + evolved, not left to erode." + routing_impact: "Growth-driven erosion routes to organisational-culture and + team-culture-and-dynamics for deliberate culture scaling." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Client-above-team culture" + reason: "The most common culture erosion pattern in agencies: prioritizing + client satisfaction at the expense of employee wellbeing until the + best people leave." + - diagnosis: "Growth outpacing culture infrastructure" + reason: "Agencies that double headcount without investing in onboarding, + communication norms, and cultural rituals lose the culture that made + them attractive." + less_likely: + - diagnosis: "Toxic leadership" + reason: "Most agency culture erosion is caused by neglect — no one is + responsible for culture — rather than malicious leadership." + agency_specific_diagnoses: + - name: "Client-abuse tolerance" + description: "The agency tolerates abusive client behavior — aggressive + communication, unreasonable demands, last-minute changes without + additional compensation, disrespect toward team members — because the + revenue is needed. This tolerance erodes team morale, drives attrition + among the best people, and ultimately damages the agency's capacity to + serve any client well." + symptoms: + - "Team members requesting to be reassigned from specific clients" + - "Higher attrition among staff assigned to demanding accounts" + - "Senior leadership rationalizing poor client behavior ('they are + just passionate')" + - "eNPS declining while client NPS remains stable — the team absorbs + the cost of client satisfaction" + routes_to_skills: [ "trust-equation", "radical-candor", "psychological-safety-practice" ] + routes_to_templates: [ "culture-values-document", "team-health-check" ] + sector_red_flags: + - "eNPS below 10 — the team is not just disengaged but actively unhappy." + - "Employee attrition above 25% — culture problems are driving out talent + faster than the firm can replace them." + - "The firm has never fired a client for behavioral reasons — a sign that + revenue is prioritized over people in every case." diff --git a/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml new file mode 100644 index 0000000..12f0958 --- /dev/null +++ b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-skill-overlays.yaml @@ -0,0 +1,1463 @@ +# Agency/Consulting Industry Pack — Skill Overlays +# +# For 37 of the 158 Foreman skills, this file provides agency/consulting-specific +# context that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add a professional services lens. +# +# The fundamental reality of agency/consulting businesses: +# - The "product" is people's time and expertise. There is no inventory except hours. +# - Revenue = People x Utilization x Rate. Every framework must connect to this equation. +# - Scaling is linear (more people = more revenue), not exponential — unless services +# are productized. +# - The moat is relationships, reputation, and specialized expertise — not technology. +# - The founder IS the product initially. Transitioning from doing to managing to +# selling is the critical growth journey. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct application to people-as-product businesses +# - Strategy skills that reframe when the "product" is expertise +# - Pricing and negotiation skills (the two highest-leverage activities in agencies) +# - Leadership and delegation skills (critical for founder transition) +# - Organizational models directly applicable to agency structure +# +# Relevance tiers: +# critical — The overlay materially changes how the skill is applied in agencies. +# The skill executor should always surface agency context. +# high — Agency context adds significant value. Surface when relevant. +# moderate — Useful agency framing but the base skill works well as-is. + +pack_metadata: + sector: "agency-consulting" + display_name: "Agency / Consulting" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (21 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + agency_relevance: "critical" + agency_context: "Porter's Five Forces reveals the structurally brutal economics + of professional services. Buyer power is HIGH — clients can always find + another agency, switch costs are low (especially for project-based work), + and procurement departments actively commoditize services through + competitive pitching. Threat of substitutes is expanding relentlessly: + in-house teams, freelancer platforms (Upwork, Toptal), AI tools that + automate creative and analytical tasks, and offshore delivery. Barriers to + entry are NEAR ZERO — anyone with a laptop and a LinkedIn profile can + start a consultancy. Supplier power is concentrated in scarce talent — + specialized developers, strategists, and creatives are the 'supply' that + agencies compete for. Rivalry is intense, fragmented, and often irrational + (agencies undercutting to win work they cannot profitably deliver)." + agency_anti_patterns: + - "Ignoring the threat of in-house teams. The most dangerous substitute is + not another agency — it is the client deciding to hire the capability + internally. Agencies must deliver value that in-house teams cannot: + breadth of experience, objectivity, surge capacity, and specialized + expertise." + - "Treating low barriers to entry as irrelevant because the firm has + relationships. Relationships are necessary but eroding — procurement-led + selection processes increasingly neutralize relationship advantages." + - "Overlooking AI as a substitute force. AI tools are rapidly replacing + tasks that agencies bill for: copywriting, basic design, data analysis, + code generation, and media planning. Agencies that do not adapt will see + their addressable work shrink." + agency_example: "A digital marketing agency uses Five Forces to understand why + margins are compressing. The analysis reveals that buyer power has + increased (clients now use agency-comparison platforms and demand + competitive pitches for every project), substitutes have multiplied (AI + content tools, in-house content teams, freelancer collectives), and new + entrants are undercutting prices (former employees starting solo + practices). The firm responds by deepening specialization in a vertical + (healthcare marketing), building proprietary data assets, and offering + outcome-based pricing that shifts competition from cost to results." + benchmark_references: [ "client-retention-rate", "win-rate", "average-billable-rate" ] + + - skill: "blue-ocean-strategy" + category: "frameworks" + agency_relevance: "critical" + agency_context: "Most agencies compete in blood-red oceans — undifferentiated + services, price-based competition, and a race to the bottom on rates. Blue + ocean strategy is structurally essential because agency differentiation + cannot come from product features (there is no product). It must come from + positioning: the intersection of a specific expertise, a specific client + type, and a specific delivery model that competitors cannot or will not + replicate. The strategy canvas exercise maps the agency's offerings + against competitors and reveals where the market over-serves (elaborate + pitch processes, bloated account teams, over-designed deliverables) and + under-serves (speed, transparency, outcome guarantees, embedded models)." + agency_anti_patterns: + - "Defining the blue ocean too broadly. 'Full-service agency for + mid-market companies' is not a blue ocean — it is the exact red ocean + every agency swims in. The blue ocean must be specific enough that a + competitor would hesitate to follow." + - "Creating a blue ocean that eliminates the relationship advantage. + Agencies that automate away the human relationship in pursuit of + differentiation lose the one asset clients value most." + - "Abandoning the blue ocean at the first sign of success. When a niche + strategy works, agencies are tempted to expand back into general + services, re-entering the red ocean they escaped." + agency_example: "A web development agency, competing against hundreds of + generalist firms on price, applies blue ocean strategy and identifies an + uncontested space: fractional CTO services for non-technical founders. + They eliminate traditional agency deliverables (proposals, wireframes, + design comps) and instead embed a senior technologist directly in the + founder's decision-making process. The pricing shifts from project-based + to monthly retainer. Competitors cannot follow because they are structured + around project delivery teams, not individual advisory relationships." + benchmark_references: [ "average-billable-rate", "client-retention-rate", "revenue-per-client" ] + + - skill: "business-model-canvas" + category: "frameworks" + agency_relevance: "critical" + agency_context: "The Business Model Canvas for agencies requires fundamental + reinterpretation of nearly every block. Key Resources: the firm's people, + their expertise, and their relationships — there are no physical assets, + patents, or technology platforms that constitute a moat. Revenue Streams: + must decompose into the pricing spectrum — hourly, project-based, + retainer, value-based, and productized — each with radically different + economics and risk profiles. Cost Structure: dominated by salaries + (typically 55-70% of revenue) with relatively thin variable costs. + Customer Relationships: the relationship IS the value proposition; clients + buy the person, not the firm. Channels: referrals, thought leadership, + speaking, and networking — not advertising or digital marketing in most + cases. The canvas is most powerful for agencies when used to map the + transition from a time-selling model to a value-selling or productized + model." + agency_anti_patterns: + - "Listing 'expertise' or 'talent' as the Value Proposition without + specifying what outcome that expertise delivers. Clients do not buy + expertise — they buy results. The value proposition must be framed as a + measurable client outcome." + - "Omitting freelancers and subcontractors from Key Partnerships. For most + agencies, the ability to scale through the Shamrock model (core staff + + contractors) is a critical strategic asset." + - "Treating the canvas as static. Agency business models must evolve as + the firm grows — from founder-does-everything to leveraged delivery to + productized services." + agency_example: "A two-person branding consultancy uses the canvas to identify a + strategic vulnerability: their Key Resource is the founder's personal + reputation, their Channel is the founder's network, and their Revenue + Stream is 100% project-based billing. The canvas redesign introduces a + second channel (content marketing to build the firm's brand beyond the + founder), a second revenue stream (a productized brand audit at a fixed + price), and a Key Partnership with a stable of freelance designers who + extend capacity without increasing fixed costs." + benchmark_references: + [ + "revenue-per-employee", + "revenue-per-client", + "gross-margin", + "leverage-ratio" + ] + + - skill: "four-ps-marketing" + category: "frameworks" + agency_relevance: "critical" + agency_context: "The Four Ps require radical adaptation for professional + services because the 'product' is intangible, produced and consumed + simultaneously, and varies with every engagement. Product in agencies is + the service itself — defined by methodology, expertise, and the quality of + the team assigned. The agency's challenge is to make an intangible, + variable service feel tangible and consistent through packaging, case + studies, and proprietary frameworks. Price is the single hardest decision + — hourly, project, retainer, value-based, or hybrid. Most agencies default + to hourly or project pricing and leave enormous value on the table. Place + means distribution: where clients find the agency — referral networks, + conferences, content, directories, or partnerships. Promotion for + professional services is fundamentally different from product promotion: + thought leadership, speaking, publishing, and case studies replace + advertising." + agency_anti_patterns: + - "Pricing based on cost-plus (hours x rate + margin) rather than value + delivered. Cost-plus pricing caps revenue at the number of available + hours. Value-based pricing decouples revenue from time." + - "Promoting capabilities instead of outcomes. Clients do not care that + the agency 'does brand strategy.' They care that the agency 'helps + companies increase market share through repositioning.'" + - "Treating 'Place' as a website. The most effective distribution channels + for agencies are referral networks, partner relationships, and speaking + platforms — not websites." + agency_example: "A management consulting firm uses the Four Ps to restructure + its go-to-market. Product: they package their strategy offering into three + tiers — diagnostic (2-week engagement), strategy development (6-week + engagement), and implementation support (ongoing retainer). Price: they + shift from day-rate billing to fixed-price engagements with value-based + premiums for outcome achievement. Place: they invest in industry + conference speaking and a quarterly research report that generates inbound + leads. Promotion: they replace generic capability decks with + vertical-specific case studies that demonstrate measurable client + outcomes." + benchmark_references: + [ + "average-billable-rate", + "win-rate", + "cost-per-lead", + "average-project-value" + ] + + - skill: "net-promoter-score" + category: "frameworks" + agency_relevance: "critical" + agency_context: "NPS is the single most predictive metric for agency growth + because agencies grow primarily through referrals. A high NPS means + clients actively recommend the firm to peers — the most efficient and + highest-converting sales channel in professional services. In agencies, + NPS should be measured at two critical moments: mid-engagement (to catch + problems before they damage the relationship) and post-engagement (to + capture the final impression). The qualitative follow-up question ('why + did you give that score?') is more valuable than the score itself — it + reveals whether satisfaction is driven by the quality of work, the quality + of the relationship, or both. Segmenting NPS by engagement type (project + vs. retainer), client size, and account manager reveals which parts of the + firm drive advocacy." + agency_anti_patterns: + - "Surveying clients only after project completion. By then, a + dissatisfied client has already formed opinions that may have spread + through their network. Mid-project check-ins catch problems early." + - "Accepting high NPS without building a formal referral program. + Promoters recommend when asked and given a mechanism — not + spontaneously. Build the ask into the post-project process." + - "Treating NPS as a firm-wide number when it is really an + individual-level metric. In agencies, NPS reflects the account lead, not + the firm. Track by account manager to identify who drives advocacy." + agency_example: "A PR agency discovers that its overall NPS of 45 masks a + bimodal distribution: retainer clients score 65+ while project clients + score 25. Investigation reveals that retainer relationships build the + trust and familiarity that drive satisfaction, while project engagements + feel transactional. The agency responds by converting its best project + clients to retainer relationships and redesigning the project experience + to include relationship-building touchpoints (monthly calls, proactive + recommendations) even during discrete engagements." + benchmark_references: [ "nps-client", "client-retention-rate", "revenue-per-client" ] + + - skill: "shamrock-organisation" + category: "frameworks" + agency_relevance: "critical" + agency_context: "The Shamrock Organisation is perhaps the most directly + applicable framework to agency economics. Its three leaves map precisely + to how modern agencies operate. The first leaf (core professional staff) + represents the full-time team whose expertise, client relationships, and + institutional knowledge define the firm. The second leaf (the flexible + labor force) includes freelancers, subcontractors, and specialist + contractors who extend capacity without increasing fixed costs — this is + the primary mechanism by which agencies manage the feast-or-famine revenue + cycle. The third leaf (outsourced functions) covers bookkeeping, IT + support, legal, and increasingly, production tasks that AI and offshore + teams handle. The strategic question for every agency is: what belongs in + each leaf? The answer determines the firm's cost structure, flexibility, + quality consistency, and scalability." + agency_anti_patterns: + - "Over-relying on the flexible leaf (freelancers) to the point where the + firm has no core identity or consistent quality. When most delivery is + outsourced, the agency becomes a broker, not a firm." + - "Refusing to use the flexible leaf out of a belief that all work must be + done by full-time staff. This creates utilization crises during slow + periods and capacity crises during busy periods." + - "Placing client-facing roles in the flexible leaf. Client relationship + management should be core — freelancers who interact directly with + clients without oversight erode trust and brand consistency." + agency_example: "A 15-person digital agency uses the Shamrock model to redesign + its staffing structure. Core (first leaf): 10 people including strategy, + account management, creative direction, and project management — roles + where consistency and client relationships are paramount. Flexible (second + leaf): a vetted pool of 25 freelance designers, developers, and writers + who scale delivery capacity from 10 to 30 people as demand fluctuates. + Outsourced (third leaf): bookkeeping, payroll, QA testing, and basic + production tasks handled by a virtual assistant service and an offshore QA + team. This structure reduces fixed costs by 30% while maintaining quality + on client-facing work." + benchmark_references: [ "utilization-rate", "bench-time", "gross-margin", "overhead-ratio" ] + + - skill: "trust-equation" + category: "frameworks" + agency_relevance: "critical" + agency_context: "Trust is EVERYTHING in professional services. Clients buy the + person before they buy the firm. The Trust Equation (Credibility + + Reliability + Intimacy / Self-Orientation) is the master framework for + agency business development and client retention. Credibility in agencies + is built through case studies, thought leadership, credentials, and the + team's experience — it is what gets the agency into the room. Reliability + is demonstrated through consistent delivery, meeting deadlines, and + keeping promises — it is what keeps the client. Intimacy is the + willingness to have honest, sometimes uncomfortable conversations about + the client's business, not just the project scope — it is what deepens the + relationship. Self-Orientation is the agency's tendency to prioritize its + own interests (pushing unnecessary scope, recommending more work rather + than less, obscuring results to justify continued engagement). Low + self-orientation — the willingness to tell a client they do not need the + agency's services — paradoxically generates the most trust and the most + referrals." + agency_anti_patterns: + - "Building credibility through credentials alone while neglecting + reliability. A firm with impressive case studies that misses deadlines + and delivers inconsistently will lose to a less credentialed firm that + delivers on time, every time." + - "Avoiding intimacy by keeping the relationship 'professional.' Agencies + that never push back on a client's bad ideas, never share uncomfortable + truths, and never challenge assumptions are valued less than those with + the courage to have honest conversations." + - "Recommending more work when less is needed. The short-term revenue gain + from expanding scope is dwarfed by the long-term trust earned by telling + a client when they do not need additional help." + agency_example: "A strategy consultancy loses a competitive pitch despite having + the strongest credentials and the most impressive case studies. + Post-mortem analysis through the trust equation reveals the gap: the + winning firm demonstrated intimacy during the pitch process — they + challenged the client's assumptions, asked probing questions about root + causes rather than symptoms, and told the client that one of their three + stated priorities was misguided. The losing firm presented polished + credentials (credibility) but never demonstrated the willingness to engage + honestly (intimacy). The lesson: clients hire agencies that tell them what + they need to hear, not what they want to hear." + benchmark_references: [ "nps-client", "client-retention-rate", "win-rate" ] + + - category: "frameworks" + agency_relevance: "critical" + agency_context: "Pricing is the single most consequential strategic decision in + professional services — and the one most agencies get wrong. The agency + pricing spectrum runs from hourly billing (lowest value capture, easiest + to sell, punishes efficiency) through project-based (moderate value + capture, requires accurate scoping) through retainer (stable revenue, + rewards relationship depth) to value-based (highest value capture, hardest + to implement, decouples revenue from time). Most agencies default to + hourly or project pricing because it is familiar and 'safe,' but this + ceiling caps revenue at available hours multiplied by acceptable rates. + The pricing diagnosis for agencies must evaluate: current pricing model + and its limitations, the gap between value delivered and price charged + (most agencies capture 15-30% of the value they create), client + willingness to pay for outcomes versus inputs, and the firm's ability to + estimate and manage scope (the prerequisite for fixed-price and + value-based models)." + agency_anti_patterns: + - "Competing on price. Agencies that win work by being the cheapest + attract the worst clients — those who value cost over quality, negotiate + relentlessly, and leave when a cheaper option appears." + - "Discounting to fill capacity. When bench time rises, the temptation to + discount rates to win any available work is strong. But discounted work + sets a new price anchor, trains clients to expect lower rates, and + attracts the wrong client profile." + - "Charging hourly for strategic work. Hourly billing for strategy + engagements punishes the agency for being fast and experienced — a + senior strategist who solves a problem in 2 hours earns less than a + junior who takes 20 hours. Value-based pricing is the appropriate model + for advisory work." + agency_example: "A design agency charging $150/hour for all work discovers + through pricing diagnosis that their effective rate is $105/hour after + scope creep, write-offs, and discounting. The diagnosis reveals three + pricing failures: (1) hourly billing punishes their efficiency — a logo + redesign takes the senior designer 15 hours but would take a competitor + 40, yet the client pays less for the superior result; (2) project scoping + is inaccurate, leading to systematic undercharging on complex projects; + (3) retainer clients are billed hourly against a monthly budget that + consistently goes unused, creating guilt on the client side. The fix: + shift to value-based project pricing for strategic work, fixed-fee + productized packages for recurring work, and outcome-linked retainers for + ongoing relationships." + benchmark_references: + [ + "average-billable-rate", + "effective-billable-rate", + "gross-margin", + "revenue-per-employee" + ] + kind: diagnostic + ref: pricing-diagnosis + + - skill: "balanced-scorecard" + category: "frameworks" + agency_relevance: "critical" + agency_context: "The Balanced Scorecard translates directly into agency + operating metrics across its four perspectives, with one critical + modification: people are the central asset, not technology or products. + Financial perspective: revenue per employee, gross margin, EBITDA margin, + utilization rate, effective billable rate. Client perspective: NPS, client + retention rate, revenue per client, scope creep rate. Internal process + perspective: proposal win rate, project delivery on time and on budget, + bench time, AR days. Learning & Growth perspective: employee NPS, employee + retention, training hours per person, senior-to-junior development + pipeline. The scorecard is particularly powerful in agencies because it + forces balance between financial extraction (utilization, rates) and + organizational health (employee satisfaction, training) — the tension that + defines agency management." + agency_anti_patterns: + - "Overweighting the financial perspective at the expense of Learning & + Growth. Agencies that maximize utilization and minimize training + investment earn higher short-term margins but lose talent and degrade + quality over time." + - "Ignoring the internal process perspective. Most agencies do not track + proposal efficiency, project profitability, or bench management with the + same rigor they apply to revenue." + - "Treating the scorecard as a reporting tool rather than a management + tool. The scorecard should drive weekly leadership discussions about + trade-offs — is the push for higher utilization damaging employee + satisfaction?" + agency_example: "A 30-person consulting firm implements a balanced scorecard and + discovers a dangerous imbalance: financial metrics are strong (utilization + at 78%, margins at 18%) but Learning & Growth metrics are deteriorating + (eNPS at 12, retention at 72%, training hours at zero). The scorecard + reveals that the firm has been maximizing short-term profits by running + people hard with no investment in development. The corrective action: + reduce utilization target to 70%, institute 'innovation Fridays' for + professional development, and implement a mentoring program. Within two + quarters, eNPS rises to 35 and retention improves to 88% — the financial + metrics stabilize at slightly lower but sustainable levels." + benchmark_references: + [ + "revenue-per-employee", + "utilization-rate", + "nps-client", + "enps", + "employee-retention-rate" + ] + + - skill: "product-life-cycle" + category: "frameworks" + agency_relevance: "high" + agency_context: "Professional services do not have traditional product + lifecycles, but the concept applies powerfully to service offerings. Every + agency service line passes through introduction (the firm develops a new + capability), growth (demand exceeds capacity and the service is + profitable), maturity (the service becomes commoditized, competition + drives down pricing), and decline (clients no longer need the service or + cheaper alternatives emerge). The critical agency insight: service lines + must be actively managed as a portfolio. Social media management was a + growth service in 2015 and is commoditized in 2026. AI strategy consulting + is in the introduction phase now and will eventually mature. Agencies that + ride a single service line through its full lifecycle without developing + successors face existential risk." + agency_anti_patterns: + - "Clinging to a mature service line because 'it is what we are known + for.' Reputation built on a commoditized service is a trap — the firm + will compete on price in a declining market." + - "Investing equally across all service lines regardless of lifecycle + position. Services in growth deserve disproportionate investment; + services in decline should be harvested for margin, not invested in for + growth." + - "Failing to sunset declining services. Agencies often maintain services + nobody wants because existing staff are skilled in them. This + misallocates talent." + agency_example: "A digital agency's SEO service line, once its primary revenue + driver, has entered maturity — clients demand it but treat it as a + commodity, competition from freelancers and tools drives down rates, and + margins have compressed from 60% to 35%. Rather than fighting for share in + a commoditizing market, the agency uses lifecycle analysis to launch two + growth-phase offerings: AI-powered content strategy (leveraging their SEO + data assets) and conversion rate optimization. The mature SEO practice + becomes a client-acquisition funnel for higher-margin growth services." + benchmark_references: [ "gross-margin", "average-billable-rate", "revenue" ] + + - skill: "disruptive-innovation" + category: "frameworks" + agency_relevance: "high" + agency_context: "Professional services are being disrupted from multiple + directions simultaneously. AI tools are the most visible disruptor — they + perform tasks (writing, design, analysis, coding) that agencies bill for. + Freelancer platforms disrupt from below with lower overhead and more + flexible engagement models. Productized service firms (like Design Pickle + for design or LAIRE for marketing) disrupt with standardized, + subscription-based delivery that replaces custom agency work. Offshore + teams disrupt on cost. The disruption framework helps agencies identify + which of their services are vulnerable, which are defensible, and how to + position the firm where automation and commoditization cannot follow — + typically in strategy, relationship management, creative direction, and + complex problem-solving." + agency_anti_patterns: + - "Dismissing AI as 'not good enough' for client work. AI tools will + improve faster than most agencies expect. The correct response is to + integrate AI into delivery to increase efficiency, not to ignore it." + - "Trying to compete with disruptors on their terms. An agency cannot + out-price a freelancer collective or out-automate an AI tool. The + response must be differentiation, not cost reduction." + - "Waiting for disruption to arrive rather than proactively repositioning. + By the time a service is visibly commoditized, margins have already + eroded." + agency_example: "A copywriting agency recognizes that AI writing tools are a + disruptive threat to its core service. Rather than competing with AI on + content production, the agency repositions upmarket: it becomes a content + strategy consultancy that uses AI tools internally to produce more content + faster, while selling strategic thinking, brand voice development, and + editorial oversight that AI cannot replicate. The firm's revenue per + employee increases 40% as production costs drop while strategic fees + rise." + benchmark_references: [ "average-billable-rate", "revenue-per-employee", "gross-margin" ] + + - skill: "growth-share-matrix" + category: "frameworks" + agency_relevance: "high" + agency_context: "The BCG Growth-Share Matrix maps to agency service lines and + client segments. Stars: high-growth, high-share service lines (e.g., AI + consulting for an early-mover agency) that justify aggressive hiring and + investment. Cash Cows: mature, dominant service lines (e.g., established + web development practice) that generate reliable revenue and fund + investment in Stars. Question Marks: new service lines with potential but + unproven demand (e.g., a new industry vertical). Dogs: underperforming + service lines with low growth and low share (e.g., print design in a + digital world). The matrix is equally useful when applied to client + segments — which client types generate the best margins with the least + effort, and which consume disproportionate resources?" + agency_anti_patterns: + - "Killing 'Dog' service lines that serve as entry points for larger + engagements. A low-margin service that consistently leads to high-margin + follow-on work is strategically valuable despite its standalone + economics." + - "Over-investing in Stars without building delivery capacity. Winning + more AI strategy work than the firm can deliver damages reputation and + quality." + - "Failing to apply the matrix to client segments. Some client types are + 'Dogs' — low growth, high maintenance, poor margins — and should be + actively managed out of the portfolio." + agency_example: "A marketing agency applies the matrix to its client portfolio + and discovers that its largest client category (startups) is a Question + Mark — high growth but low share (many competitors) and poor margins + (startups negotiate hard and churn fast). Its mid-market B2B clients are + Cash Cows — stable relationships, good margins, steady work. The agency + redirects growth investment from startup acquisition to mid-market B2B + deepening, using Cash Cow profits to fund a Star initiative: a productized + marketing audit specifically designed for mid-market B2B companies." + benchmark_references: [ "revenue-per-client", "gross-margin", "client-retention-rate" ] + + - skill: "swot-pest-analysis" + category: "frameworks" + agency_relevance: "high" + agency_context: "SWOT and PEST analysis for agencies must account for the unique + environmental forces shaping professional services. Political: government + procurement regulations, data privacy laws that affect agency work, + immigration policies that impact talent availability. Economic: corporate + marketing and consulting budget cycles, recession sensitivity (agencies + are often first to be cut), interest rates affecting client investment. + Social: remote work enabling agencies to hire globally (and clients to + hire globally too), the rise of the creator economy as a substitute for + agency services, generational expectations of work-life balance. + Technological: AI tools transforming every agency discipline, project + management and collaboration tools reducing overhead, the collapse of + barriers between agency services (design, development, marketing + converging)." + agency_anti_patterns: + - "Listing 'talented team' as a Strength without acknowledging that talent + is also the primary constraint. The team that is a strength today + becomes a weakness when key people leave." + - "Ignoring the Technology PEST factor. Agencies that do not understand + how AI is reshaping their disciplines will be blindsided by disruption." + - "Conducting SWOT as a feel-good exercise that lists more Strengths than + Weaknesses. Honest SWOT requires more courage in agencies because + weaknesses are often personal — the founder's limitations, key person + dependency, or lack of systems." + agency_example: "A PR agency conducts a PEST analysis and identifies that + AI-generated media monitoring and sentiment analysis (Technology) will + commoditize a service that generates 30% of revenue, that a generational + shift toward authenticity and transparency (Social) creates an opportunity + for their crisis communications practice, and that tightening data privacy + regulations (Political) will increase demand for compliance-aware + communications. The SWOT reveals that their Weakness — lack of data + analytics capability — prevents them from capitalizing on the Technology + threat. The strategic response: partner with a data analytics firm rather + than building the capability internally." + benchmark_references: [ "revenue", "gross-margin", "average-billable-rate" ] + + - skill: "scenario-planning" + category: "frameworks" + agency_relevance: "high" + agency_context: "Agency revenue is inherently volatile — the feast-or-famine + cycle is structural, not accidental. Scenario planning must address three + critical scenarios for every agency: (1) Client loss scenario — what + happens if the top client (or top two) leave? (2) Talent loss scenario — + what happens if a key producer departs and takes client relationships? (3) + Market shift scenario — what happens if a core service line is + commoditized faster than expected? Financial scenarios should model at + least three cases: base (current trajectory), growth (win a major account + or enter a new vertical), and contraction (lose a major client or face a + recession). Each scenario needs explicit triggers and pre-committed + responses." + agency_anti_patterns: + - "Planning only for growth scenarios. Agencies are optimistic by nature + but vulnerable to downturns. A contraction scenario with a pre-committed + cost-reduction plan preserves the firm when the inevitable downturn + arrives." + - "Building scenarios that assume the same team is available. People are + the production capacity in agencies — scenarios must account for + attrition, hiring difficulty, and key-person risk." + - "Failing to scenario-plan cash flow separately from revenue. A $3M + agency with $200K in receivables and a $100K monthly payroll can face a + cash crisis even while 'growing.'" + agency_example: "A 20-person consultancy builds three scenarios for the next 12 + months. Base: current trajectory, 10% revenue growth from existing clients + plus modest new business. Growth: win a major government contract that + would double headcount requirements, requiring rapid hiring and + subcontractor engagement. Contraction: top client (28% of revenue) + announces an in-house build, requiring immediate cost reduction and + aggressive new business development. Each scenario has financial + projections, talent implications, and a decision trigger that signals + which scenario is materializing." + benchmark_references: [ "client-concentration", "revenue", "bench-time", "overhead-ratio" ] + + - skill: "eisenhower-matrix" + category: "frameworks" + agency_relevance: "high" + agency_context: "Agency founders and leaders face a relentless stream of + competing demands — client emergencies, proposal deadlines, employee + issues, billing disputes, and new business opportunities all compete for + attention. The Eisenhower Matrix in agencies must specifically address the + tension between billable work (Urgent and revenue-generating) and + business-building work (Important but not Urgent — sales, thought + leadership, process improvement, training). The most damaging agency + pattern is the founder who is personally billable at high utilization, + leaving zero time for business development, hiring, and strategic + planning. This creates a ceiling on growth that is precisely equal to the + founder's personal capacity." + agency_anti_patterns: + - "Treating every client request as Urgent/Important. Client requests feel + urgent because the client is pressing, but most can be scheduled without + damaging the relationship. Learning to say 'I can address this by + Thursday' rather than 'I will drop everything now' is a survival skill." + - "Spending all time in billable delivery (Urgent/Important) and + neglecting business development and systems-building (Not + Urgent/Important). This guarantees the feast-or-famine cycle — when the + current project ends, there is nothing in the pipeline." + - "Delegating business development because it is 'Not Urgent.' In + agencies, the founder's personal involvement in business development and + client relationships is often irreplaceable, at least until the firm is + large enough to hire a dedicated BD lead." + agency_example: "An agency founder tracks time for two weeks and discovers that + 75% is spent on billable client work (Urgent/Important), 15% on email and + administrative tasks (Urgent/Not Important), and 10% on ad hoc + emergencies. Zero time is spent on strategic work: no pipeline + development, no process documentation, no staff development. The + Eisenhower Matrix reveals that the founder must reduce billable + utilization from 75% to 50%, delegate administrative tasks, and protect + 15-20 hours per week for business development and firm-building — the Not + Urgent/Important quadrant that determines whether the agency grows or + stalls." + benchmark_references: [ "utilization-rate", "pipeline-coverage-ratio", "revenue" ] + + - skill: "systems-thinking" + category: "frameworks" + agency_relevance: "high" + agency_context: "Agency businesses contain reinforcing feedback loops that + create non-obvious outcomes. The talent-quality loop: better work attracts + better clients, better clients provide better case studies, better case + studies attract better talent, better talent produces better work. The + utilization-burnout loop: high utilization generates revenue, but + sustained high utilization causes burnout, burnout causes attrition, + attrition requires emergency hiring and knowledge transfer, which reduces + quality and increases costs. The feast-or-famine loop: busy periods + consume all capacity for business development, no business development + creates pipeline gaps, pipeline gaps create bench time, bench time + pressures the team to take any available work, undifferentiated work leads + to price competition, price competition thins margins, thin margins + prevent hiring sales capacity. Systems thinking helps agency leaders + identify which loop to intervene in and where." + agency_anti_patterns: + - "Treating symptoms instead of systems. Hiring more people to address + missed deadlines when the root cause is poor scoping. Running overtime + to absorb scope creep when the root cause is weak contracts." + - "Ignoring the time delay in feedback loops. Cutting training and + development today does not decrease quality tomorrow — it decreases + quality in 6-12 months, making the cause invisible." + - "Optimizing utilization without modeling second-order effects. Pushing + utilization from 68% to 78% generates short-term revenue but increases + attrition, which costs far more to replace." + agency_example: "A growing agency notices that quality complaints are rising + despite hiring experienced people. Systems analysis reveals a reinforcing + loop: rapid growth requires fast hiring, fast hiring dilutes culture and + methodology consistency, inconsistent methodology produces variable + quality, variable quality generates client complaints, complaints consume + senior staff time for firefighting, senior time spent firefighting reduces + their availability for mentoring new hires, less mentoring perpetuates + inconsistency. The intervention point is not quality control (a downstream + symptom) but onboarding and mentoring (an upstream cause) — slowing hiring + to match the firm's capacity to integrate new people." + benchmark_references: + [ + "employee-retention-rate", + "utilization-rate", + "nps-client", + "scope-creep-rate" + ] + + - skill: "smart-goals" + category: "frameworks" + agency_relevance: "high" + agency_context: "SMART goals in agencies must account for the dual nature of the + business: client delivery and firm building. Agency leaders need goals in + both domains — a set of delivery goals (utilization, on-time delivery, + client satisfaction) and a set of business-building goals (pipeline, win + rate, thought leadership, talent development). The most common failure in + agencies is setting revenue goals without corresponding capacity and + operational goals. Hitting a $5M revenue target requires specific + utilization rates, staffing levels, average project sizes, and win rates — + each of which should be an explicit SMART goal." + agency_anti_patterns: + - "Setting revenue goals without operational sub-goals. '$5M revenue this + year' is incomplete without 'win 15 new projects at $100K average, + maintain 90% client retention, and achieve 67% utilization.'" + - "Setting goals only at the firm level without cascading to individuals. + Each partner, account manager, and project lead should have goals that + connect to the firm-level objectives." + - "Ignoring the tension between utilization goals and business development + goals. A 75% utilization target for a partner leaves only 25% for sales + and management — often insufficient." + agency_example: "Instead of 'grow revenue 20%,' a consultancy sets Q2 SMART + goals: (1) Win 5 new retainer clients at $8K+/month through focused + outreach to the healthcare vertical (Specific, Measurable, Achievable + given pipeline, Relevant to vertical strategy, Q2 Time-bound). (2) + Increase billable utilization from 63% to 67% by reducing bench time + through better resource planning (Specific, Measurable, achievable in 90 + days, directly impacts margin). (3) Reduce average AR days from 52 to 40 + by implementing automated invoicing and payment follow-up (Specific, + Measurable, directly impacts cash flow, Time-bound to Q2). Each goal has a + named owner and weekly measurement." + benchmark_references: [ "revenue", "utilization-rate", "ar-days", "win-rate" ] + + - skill: "doblin-ten-types" + category: "frameworks" + agency_relevance: "high" + agency_context: "The Ten Types of Innovation framework is revealing for agencies + because most agency innovation happens in a single type — Service + (improving client deliverables) — while nine other innovation types are + ignored. The most powerful agency innovations often come from Profit Model + (shifting from hourly to value-based or productized pricing), Network + (building freelancer ecosystems and strategic partnerships), Process + (developing proprietary methodologies that standardize delivery), Channel + (creating content platforms or communities that generate inbound leads), + and Customer Engagement (building client advisory boards, communities of + practice, or educational programs). Innovation in Service alone leads to + an arms race of better deliverables at similar prices." + agency_anti_patterns: + - "Defining innovation as 'better creative work' or 'more advanced + technology.' These are Service innovations that every competitor also + pursues. The most defensible innovations are in business model, process, + and channel." + - "Ignoring Profit Model innovation. The shift from hourly to value-based + or productized pricing is a Profit Model innovation that transforms + agency economics more than any service improvement." + - "Dismissing Network innovation. An agency with a curated ecosystem of + freelancers, technology partners, and complementary service providers + can deliver more value than a larger firm with only internal resources." + agency_example: "A web development shop applies Doblin's framework and + identifies that all of its innovation investment goes to Service (learning + new technologies, improving code quality) and none to other types. + Applying the framework, the agency pursues Profit Model innovation (a + monthly subscription for ongoing website maintenance and optimization at a + fixed fee), Channel innovation (a free website audit tool that generates + qualified leads), and Process innovation (a proprietary discovery + methodology that reduces project scoping from 2 weeks to 2 days). The + combined innovations increase revenue per employee by 35% despite no + change in the quality of the underlying development work." + benchmark_references: [ "revenue-per-employee", "average-billable-rate", "win-rate" ] + + - skill: "emotional-intelligence" + category: "frameworks" + agency_relevance: "high" + agency_context: "Emotional intelligence is a core professional competency in + agencies — not a 'nice to have.' Agency professionals navigate three + emotionally charged domains daily: client relationships (reading buyer + sentiment, managing expectations, delivering bad news about budgets or + timelines), team management (motivating creative professionals who are + intrinsically driven, handling the stress of tight deadlines and demanding + clients, retaining talent that has abundant alternatives), and business + development (reading the room in pitches, building personal connections + that differentiate the firm, handling rejection when proposals are + declined). The emotional demands of agency work are higher than in most + industries because the work is personal — a rejected design or a + criticized strategy can feel like a personal attack." + agency_anti_patterns: + - "Treating client feedback on creative work as objective critique. + Creative professionals often internalize criticism of their work as + criticism of themselves. Leaders must translate client feedback into + actionable direction without transmitting the emotional charge." + - "Ignoring the emotional toll of client service. Agency burnout is not + primarily about hours — it is about the emotional labor of managing + demanding clients, absorbing scope creep, and maintaining enthusiasm + under pressure." + - "Promoting the best individual contributors to management roles without + assessing emotional intelligence. The best designer or developer is not + necessarily the best people manager." + agency_example: "A creative director notices that a senior designer is + delivering increasingly mediocre work after a difficult client engagement + where three rounds of feedback essentially reversed the original creative + direction. Rather than addressing the output (a symptom), the CD applies + emotional intelligence: she acknowledges the designer's frustration, + validates that the client process was demoralizing, discusses how to set + creative boundaries in future engagements, and temporarily assigns the + designer to an internal branding project where creative freedom restores + motivation. The designer's output quality recovers within two weeks." + benchmark_references: [ "enps", "employee-retention-rate", "nps-client" ] + + - skill: "covey-seven-habits" + category: "frameworks" + agency_relevance: "moderate" + agency_context: "The Seven Habits apply with particular force to agency founders + navigating the transition from practitioner to business leader. 'Begin + with the End in Mind' forces the question: is the goal a lifestyle + business ($500K-$2M, high personal income, minimal staff), a scale agency + ($5M-$20M, institutional clients, exit potential), or something else? + Every operational decision flows from this choice. 'Put First Things + First' maps directly to the Not Urgent/Important quadrant where business + development and strategic planning live — the work most agency leaders + neglect. 'Think Win-Win' is essential for long-term client relationships + and talent retention. 'Sharpen the Saw' addresses the burnout epidemic in + agency leadership, where 60-hour weeks and always-on client service erode + judgment." + agency_anti_patterns: + - "Running the agency without clarity on the end goal. An agency designed + for lifestyle and an agency designed for scale require completely + different staffing, pricing, and client strategies. Ambiguity between + these goals creates strategic drift." + - "Neglecting 'Sharpen the Saw' because every hour not billed is seen as + lost revenue. Agency leaders who never invest in their own development + become the ceiling on their firm's capability." + agency_example: "An agency founder applies 'Begin with the End in Mind' and + realizes he has been building a scale agency (hiring, pursuing large + accounts, taking on debt) when his actual goal is a lifestyle consultancy + (high personal income, flexibility, interesting work, no management + headaches). This clarity triggers a strategic reversal: he reduces the + team from 12 to 5, lets go of demanding enterprise clients, raises rates + by 40%, and restructures as a boutique practice. Revenue drops from $2.5M + to $1.5M, but personal income increases and work-life balance improves + dramatically." + benchmark_references: [ "ebitda-margin", "revenue-per-employee", "enps" ] + + # ───────────────────────────────────────────── + # NEGOTIATION (4 skills) + # ───────────────────────────────────────────── + + - skill: "competitive-negotiation" + category: "negotiation" + agency_relevance: "critical" + agency_context: "Competitive negotiation in agencies occurs in three high-stakes + contexts: scope negotiation (the most frequent — clients requesting + additional work within existing budgets), rate negotiation (clients + pushing for lower rates or requesting discounts to retain the + relationship), and contract negotiation (payment terms, liability caps, IP + ownership, and exclusivity clauses). Scope negotiation is the most + consequential because it directly determines project profitability — the + agency that cannot hold scope boundaries watches margins evaporate project + by project. Rate negotiation is complicated by the personal nature of + agency services — reducing the rate feels like devaluing the people doing + the work. Contract terms like IP ownership and non-competes can have + long-term strategic implications that exceed the financial value of the + individual deal." + agency_anti_patterns: + - "Discounting rates to retain a client without obtaining anything in + return. Every discount should be exchanged for something: a longer + commitment, a case study, a referral, or expanded scope." + - "Absorbing scope expansion without documentation. Informal scope + expansion ('can you also just quickly do X?') is the primary margin + killer in agencies. Every addition should be documented and either + billed or explicitly traded for something." + - "Negotiating from the assumption that the client has all the power. + Agencies often underestimate their leverage — switching costs for + clients include knowledge transfer, relationship rebuilding, learning + curves, and project disruption." + agency_example: "A client requests a 15% rate reduction at contract renewal, + citing competitive alternatives. The agency prepares by quantifying the + value delivered (three campaigns generating $4.2M in attributable revenue + against $450K in fees), documenting the switching costs (estimated 3-month + productivity loss during transition), and preparing a counter-proposal: + maintaining rates but adding a performance bonus tied to campaign + outcomes. The client accepts the counter-proposal because it demonstrates + confidence in results and aligns incentives — the negotiation shifts from + cost to value." + benchmark_references: + [ + "average-billable-rate", + "effective-billable-rate", + "client-retention-rate" + ] + + - skill: "cooperative-negotiation" + category: "negotiation" + agency_relevance: "critical" + agency_context: "Cooperative negotiation is the foundation of long-term + agency-client relationships. Unlike transactional sales where the + negotiation ends at signature, agency engagements involve continuous + negotiation — about priorities, timelines, scope, and resources — + throughout the relationship. The most successful agencies frame the + engagement as a partnership where both parties invest in mutual success, + rather than a vendor-client transaction where the agency delivers what is + ordered. Cooperative negotiation also governs the most important internal + negotiation in agencies: resource allocation across competing client + demands. When three clients all need the senior designer this week, the + allocation decision is a negotiation — and how it is handled determines + which clients receive excellent service and which feel neglected." + agency_anti_patterns: + - "Agreeing to everything the client requests to preserve the + relationship. Accommodation is not cooperation. True cooperative + negotiation involves honest trade-offs: 'We can add this feature, but it + will push the launch by two weeks. Is that trade-off acceptable?'" + - "Treating retainer renewals as rubber-stamp exercises. Renewal is an + opportunity to renegotiate scope, rates, and terms based on demonstrated + value. Agencies that passively renew at the same terms leave value on + the table." + - "Failing to negotiate internally with the same rigor applied to client + negotiations. Resource allocation, project sequencing, and + priority-setting across the firm require explicit cooperative + negotiation among partners and account leads." + agency_example: "An agency managing a $180K annual retainer uses cooperative + negotiation at the annual review. Rather than simply renewing at the same + terms, they present: value delivered (documented outcomes), scope + evolution (how the work has grown beyond the original brief), and a + restructured proposal — the retainer increases to $220K but includes a new + service (quarterly competitive analysis) and an outcome-linked bonus. The + client agrees because the agency has framed the increase as expanded + value, not a price increase. Both parties gain: the agency increases + revenue per client and the client receives additional strategic support." + benchmark_references: [ "revenue-per-client", "client-retention-rate", "nps-client" ] + + - skill: "delivering-the-deal" + category: "negotiation" + agency_relevance: "high" + agency_context: "Deal execution in agencies has unique characteristics: + proposals compete against 2-5 other firms in a structured evaluation + process; procurement departments at large clients apply standardized + vendor management frameworks that strip out the personal relationship; SOW + terms (liability, IP, indemnification) can stall deals for weeks; and the + gap between verbal agreement and signed contract is where deals die — the + client's enthusiasm cools, internal priorities shift, or a competitor + makes a counter-offer. The skill of delivering the deal means: submitting + proposals that are easy to approve (not elaborate documents that require + committee review), having flexible SOW templates ready for rapid + negotiation, maintaining momentum between verbal yes and signature, and + building internal champions within the client organization who drive + urgency." + agency_anti_patterns: + - "Investing weeks in elaborate proposal documents that clients do not + read. The proposal should be as short as the decision process allows. A + 3-page proposal closed in 2 weeks beats a 30-page proposal that takes 3 + months." + - "Losing momentum between verbal agreement and contract signature. Follow + up within 24 hours of verbal acceptance with the SOW. Every day of delay + increases the probability of deal collapse." + - "Treating the signed contract as the finish line. In agencies, the real + deal begins at kickoff — the first 30 days of delivery either confirm + the client's decision or plant the seeds of regret." + agency_example: "An agency creates a 'deal acceleration kit' containing: a + modular SOW template (core terms pre-approved by legal, with fill-in + sections for scope, timeline, and pricing), a one-page proposal format for + engagements under $50K, three reference clients pre-briefed and ready for + calls, and a standard project kickoff plan sent with the SOW to + demonstrate readiness. The kit reduces average proposal-to-signature time + from 35 days to 14 days, and the kickoff plan attached to the SOW + increases close rate by 18% because it makes the agency feel prepared and + easy to work with." + benchmark_references: [ "win-rate", "sales-cycle-length", "average-project-value" ] + + - skill: "negotiation-mindset-and-self" + category: "negotiation" + agency_relevance: "high" + agency_context: "Agency founders and senior consultants negotiate constantly — + with clients, prospects, subcontractors, employees, and partners — often + from a position of perceived weakness. The perceived weakness is + structural: the client has budget authority, the talent has other job + offers, and the subcontractor has other clients. The negotiation mindset + skill helps agency leaders recognize that their leverage is greater than + they perceive: they possess specialized expertise, deep knowledge of the + client's business, existing relationships and trust, and the capacity to + solve problems the other party cannot solve alone. The most common mindset + failure in agencies is believing that saying 'no' to a client will end the + relationship, when in practice, the ability to set boundaries increases + respect and trust." + agency_anti_patterns: + - "Entering negotiations from a scarcity mindset. Agencies that believe + every prospect is critical and every client is irreplaceable negotiate + from desperation, which produces bad terms." + - "Confusing accommodation with service. Excellent client service does not + mean accepting every demand. It means delivering outstanding results + within clearly defined boundaries." + - "Avoiding negotiation by absorbing costs. Many agency founders would + rather silently eat scope creep than have an uncomfortable conversation + about additional fees. This is a mindset problem, not a negotiation + technique problem." + agency_example: "A consultant has been absorbing an average of 20% additional + scope on every project because she fears that raising the issue will + damage client relationships. Mindset work reveals the core belief: 'If I + push back on scope, the client will think I am not dedicated and will find + someone else.' Reframing: 'Clients who value me will respect clear + boundaries. Clients who expect unlimited free work are not clients I + want.' After implementing boundary conversations on the next three + projects, two clients respond positively (one even apologizes for past + overreach), and one client terminates — which frees capacity for more + profitable work." + benchmark_references: [ "effective-billable-rate", "scope-creep-rate", "nps-client" ] + + # ───────────────────────────────────────────── + # LEADERSHIP (5 skills) + # ───────────────────────────────────────────── + + - skill: "delegation-and-empowerment" + category: "leadership" + agency_relevance: "critical" + agency_context: "Delegation is the defining leadership challenge in professional + services because the founder IS the product initially. Clients hired the + founder's expertise, judgment, and personal attention. Transitioning from + doing the work to managing others who do the work requires delegating + without diminishing quality — and convincing clients that the junior + consultant or designer is a suitable replacement for the founder's + personal involvement. The delegation journey in agencies has three phases: + Phase 1, the founder does everything (solo consultant). Phase 2, the + founder delegates execution but retains client relationships and quality + control (small agency). Phase 3, the founder delegates client + relationships to account managers and quality control to creative + directors (scaled agency). Most agency founders get stuck between Phase 1 + and Phase 2, creating a permanent ceiling on firm size." + agency_anti_patterns: + - "Delegating tasks but not authority. Assigning junior staff to create + the deliverable but then rewriting it entirely defeats the purpose and + demoralizes the team." + - "Delegating client relationships too early. Clients hired the founder. + Transitioning the relationship to an account manager requires a + deliberate, gradual handoff — not an abrupt switch." + - "Refusing to delegate because 'no one can do it as well as I can.' This + is often true in the short term but guarantees the firm cannot grow. The + founder's job is to build the team's capability, not to protect their + own indispensability." + agency_example: "A strategy consultant earning $500K annually from personal + billings hits a growth ceiling — she cannot bill more than 1,800 hours per + year. She begins delegating by hiring a senior associate who shadows her + on three engagements, then runs a portion of the fourth engagement + independently with the founder reviewing key deliverables. Within 12 + months, the associate handles 60% of delivery independently. The founder's + time shifts to business development and executive-level client advisory — + higher-value work that generates $350K in personal billings plus $300K + from the associate's work, growing firm revenue from $500K to $650K with a + clear path to $1M." + benchmark_references: [ "revenue-per-partner", "leverage-ratio", "revenue" ] + + - skill: "leadership-pipeline" + category: "frameworks" + agency_relevance: "high" + agency_context: "The Leadership Pipeline is essential for agencies because the + growth trajectory follows a predictable path: from individual contributor + (billable consultant) to managing others (project/account manager) to + managing managers (department/practice lead) to running the business + (partner/principal). Each transition requires fundamentally different + skills and a different relationship with billable work. The most common + pipeline failure in agencies is promoting the best consultant to a + management role without any transition support — they continue doing the + consulting work themselves (because they are good at it and it generates + revenue) while neglecting the management work (because it is new and + uncomfortable). The result: an overburdened manager who does both jobs + poorly." + agency_anti_patterns: + - "Promoting based on billing performance rather than leadership + potential. The highest-billing consultant may be the worst manager — + they succeed through individual excellence, not through developing + others." + - "Expecting new managers to maintain their previous utilization rate. A + new project manager or account lead needs at least 25-30% of their time + for management activities. Reducing their billing target is a necessary + investment." + - "Skipping the 'managing managers' level. Going directly from individual + contributors to a single firm leader creates a bottleneck where all + management flows through one person." + agency_example: "A 25-person agency promotes three senior consultants to + practice leads without adjusting their utilization targets. Within six + months, all three are working 55+ hour weeks — billing 40+ hours on client + work and spending evenings on management tasks. Two burn out and one + leaves. The agency redesigns the leadership pipeline: practice leads bill + at 50% utilization (not 70%), receive management training, and are + evaluated on team performance (utilization, quality, retention) rather + than personal billing. The firm's delivery capacity and quality improve + because the leaders are actually leading." + benchmark_references: [ "employee-retention-rate", "leverage-ratio", "revenue-per-partner" ] + + - skill: "strategic-thinking-and-alignment" + category: "leadership" + agency_relevance: "high" + agency_context: "Strategic alignment in agencies is challenged by a structural + tension: the short-term revenue imperative (take any work that pays) + versus the long-term positioning imperative (specialize, differentiate, + and decline work that does not fit). Most agencies default to the + short-term imperative, accepting every client and every project type, + which prevents the specialization that drives premium pricing. Strategic + alignment requires the agency to define what it does, for whom, and — + critically — what it will NOT do. This is harder in agencies than in + product companies because declining a $50K project that is 'not our thing' + feels like throwing money away, when in fact it frees capacity for + higher-margin work that builds the firm's reputation in its chosen + specialty." + agency_anti_patterns: + - "Defining strategy as 'we do everything for everyone.' This is the + absence of strategy, not a strategy. It guarantees competition on + price." + - "Allowing individual partners to pursue their own client strategies + without firm-level alignment. Autonomous partners build fiefdoms rather + than a coherent firm." + - "Setting a strategic direction and then accepting every piece of + off-strategy work because 'we need the revenue.' Strategy requires the + discipline to say no — especially when saying no is financially + painful." + agency_example: "A generalist digital agency adopts a vertical specialization + strategy: healthcare marketing for mid-size hospital systems. The first + year is painful — they decline $400K in non-healthcare work while + healthcare revenue grows slowly to $250K. By year two, healthcare clients + refer other healthcare organizations, the agency develops proprietary + benchmarking data for the sector, and they can charge 30% more than + generalist competitors because they understand the regulatory landscape + and speak the client's language. Revenue exceeds the generalist baseline + within 30 months, at significantly higher margins." + benchmark_references: + [ + "average-billable-rate", + "client-retention-rate", + "win-rate", + "revenue-per-client" + ] + + - skill: "employee-engagement-retention" + category: "leadership" + agency_relevance: "high" + agency_context: "Retention in agencies is existential — when people leave, they + take client relationships, institutional knowledge, and billable capacity + with them. The worst outcome is when a departing employee takes clients to + a new firm or starts a competing practice. Agency retention is driven by + three factors that differ from product companies: (1) Quality of work — + creative and strategic professionals leave when the work becomes + repetitive or unchallenging. (2) Client relationships — staff who manage + client relationships directly have more leverage and more reason to leave. + (3) Growth trajectory — talented people leave when they see no path to + partnership, ownership, or expanded responsibility." + agency_anti_patterns: + - "Treating retention as a compensation problem when it is usually a + work-quality problem. Talented agency professionals will accept modest + compensation for exceptional work — they will not accept exceptional + compensation for mediocre work." + - "Waiting until someone resigns to address retention. By then, the + decision is made. Proactive retention requires quarterly career + conversations with every key person." + - "Ignoring the client-relationship risk of attrition. When a senior + account manager leaves, assess which clients are at risk and proactively + strengthen those relationships through leadership engagement." + agency_example: "A consulting firm discovers through exit interviews that the + top reason for departure is 'lack of growth opportunities.' The firm + responds by creating three career tracks: a client track (account + management to partner), a craft track (specialist to practice expert), and + a management track (team lead to operations director). Each track has + defined milestones, compensation bands, and development plans. A + profit-sharing program at the senior level creates financial incentives to + stay. Retention improves from 78% to 91% over 18 months." + benchmark_references: [ "employee-retention-rate", "enps", "revenue-per-employee" ] + + - skill: "focus-and-priority-management" + category: "leadership" + agency_relevance: "high" + agency_context: "Agency leaders are pulled in more directions simultaneously + than leaders in most other business types. On any given day, a founder may + need to: deliver on a client project, prepare a proposal for a new + prospect, resolve a staffing conflict, chase an overdue invoice, conduct a + performance review, and attend a networking event. The result is chronic + context-switching that degrades the quality of all activities. Priority + management in agencies requires explicit time blocking: designated days or + half-days for client delivery, business development, management, and + strategic thinking. The most impactful priority decision for agency + leaders is how to split time between billable work and non-billable + firm-building." + agency_anti_patterns: + - "Allowing the day to be driven by whoever is most urgent. Without + explicit priorities, the loudest client and the most pressing emergency + consume all available time." + - "Treating 'being busy' as evidence of productivity. High activity in + agencies can mask low impact — billing 50 hours while the pipeline dries + up is busy but not productive." + - "Failing to protect time for deep work. Agency deliverables — strategy + documents, creative concepts, proposals — require uninterrupted focus. + Constant interruptions produce mediocre output." + agency_example: "An agency founder implements a time-blocking system: Mondays + for internal management (team meetings, pipeline review, financial + review), Tuesday-Thursday for client delivery and client meetings, Fridays + for business development (proposals, networking, thought leadership). The + founder also establishes a 'minimum viable personal billability' target of + 40% — enough to stay connected to client work without being consumed by + it. Within three months, pipeline coverage improves from 1.5x to 3.5x + because business development finally receives consistent attention." + benchmark_references: [ "pipeline-coverage-ratio", "utilization-rate", "revenue" ] + + - skill: "mentoring-and-coaching" + category: "leadership" + agency_relevance: "high" + agency_context: "Mentoring and coaching are the primary mechanisms by which + agencies scale expertise. The founder's knowledge must transfer to the + team — not through documentation alone but through structured mentoring + relationships where junior staff observe, practice, receive feedback, and + gradually assume more complex responsibilities. In agencies, mentoring + also serves a business purpose: mentored employees are more engaged + (reducing attrition), develop client-ready capabilities faster (reducing + time to full billability), and become the next generation of account leads + (enabling the founder to step back from delivery). The agency mentoring + challenge is time — every hour spent mentoring is an hour not billed." + agency_anti_patterns: + - "Treating mentoring as 'nice to have' rather than a core business + activity. In agencies, mentoring IS the mechanism by which the firm + scales. Without it, the firm is perpetually dependent on the founder's + personal capacity." + - "Mentoring only on technical skills while ignoring client management + skills. The most valuable agency skill — managing client relationships — + is the hardest to teach and the most neglected in mentoring programs." + - "Expecting mentoring to happen organically. It does not. Structured + mentoring requires explicit pairing, regular cadence, and + accountability." + agency_example: "A design agency implements a structured mentoring program where + each senior designer mentors two junior designers. The program includes: + weekly 1:1 sessions (30 minutes), joint client presentations where the + junior observes then gradually presents, and 'graduated responsibility' + where the junior designer leads increasingly complex deliverables with + decreasing oversight. After 12 months, three junior designers are + independently managing client deliverables, freeing senior designers to + focus on business development and creative direction. The firm's delivery + capacity effectively doubles without proportional hiring." + benchmark_references: [ "leverage-ratio", "employee-retention-rate", "revenue-per-employee" ] + + # ───────────────────────────────────────────── + # GAME THEORY (2 skills) + # ───────────────────────────────────────────── + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + agency_relevance: "moderate" + agency_context: "The Prisoner's Dilemma manifests in agency economics through + pricing dynamics and competitive pitching. When multiple agencies compete + for a project and each must submit pricing independently, the temptation + to undercut creates a race-to-the-bottom that destroys industry margins. + The cooperative solution — agencies maintaining rate integrity even when + competing — is unstable because the incentive to defect (discount to win) + always exists. The same dynamic appears in the freelancer-agency + relationship: agencies tempted to underpay freelancers to protect margins, + while freelancers are tempted to go directly to clients and cut out the + agency. Repeated-game theory suggests that agencies with long-term + relationships (clients, freelancers, competitors) benefit from + cooperation, while one-shot interactions invite defection." + agency_anti_patterns: + - "Always defecting (discounting) in competitive pitches. This trains the + market to expect low prices and erodes margins industry-wide." + - "Treating competing agencies as pure adversaries. In mature markets, + agencies frequently collaborate — subcontracting to each other, + referring work that does not fit, and maintaining relationships that + benefit everyone." + agency_example: "Two competing PR agencies in the same city initially undercut + each other's pricing on every pitch. After years of this, both realize + their margins have eroded to 8%. They reach an informal understanding: + neither will quote below their published rate card. Instead, they compete + on quality, relationships, and specialization. Both firms' margins recover + to 15%+ within two years, and they occasionally refer work to each other + when a client needs capabilities outside their specialty." + benchmark_references: [ "average-billable-rate", "gross-margin", "win-rate" ] + + - skill: "information-asymmetry" + category: "game-theory" + agency_relevance: "high" + agency_context: "Information asymmetry shapes every agency-client interaction. + The agency typically knows more about the complexity of the work, the real + cost of delivery, and the range of possible outcomes. The client typically + knows more about their internal budget, their urgency, their alternatives, + and their satisfaction with the agency's work. Agencies that exploit + information asymmetry (overscoping work, padding timelines, obscuring + costs) gain short-term margin at the cost of long-term trust. Agencies + that proactively reduce information asymmetry (transparent time tracking, + open-book pricing, honest complexity assessments) build the trust that + sustains relationships and justifies premium pricing. The most powerful + application: helping clients understand the true value of the agency's + work by sharing relevant benchmarks and market data." + agency_anti_patterns: + - "Exploiting asymmetry by obscuring what work actually costs or how long + it actually takes. Clients who discover they have been overcharged never + return." + - "Failing to leverage legitimate asymmetry. Agencies possess genuine + expertise that clients lack — sharing this knowledge (through education, + frameworks, and benchmarks) positions the agency as a trusted advisor + rather than a vendor." + agency_example: "A web development agency adopts transparent project management + — the client can see the time tracker, the project budget consumption, and + the remaining scope in real time. Initially, the team fears this will lead + to micromanagement and scope disputes. In practice, the transparency + builds trust: clients see the real complexity of the work, understand why + changes have cost implications, and feel confident they are getting fair + value. Client retention increases from 72% to 89%, and the agency can + charge higher rates because trust reduces the 'risk premium' clients apply + to opaque vendors." + benchmark_references: [ "effective-billable-rate", "nps-client", "client-retention-rate" ] + + # ───────────────────────────────────────────── + # PEOPLE (2 skills) + # ───────────────────────────────────────────── + + - skill: "connecting-with-people" + category: "people" + agency_relevance: "high" + agency_context: "Connection is the primary sales channel for professional + services. Agencies grow through relationships — referrals from satisfied + clients, connections made at industry events, relationships with former + colleagues who move to potential client organizations, and bonds formed + through shared experiences and mutual interests. The depth and breadth of + the founder's (and the team's) professional network directly determines + the firm's growth ceiling. Unlike product companies where marketing can + generate demand at scale, agencies rely on one-to-one relationships that + require genuine connection — not transactional networking." + agency_anti_patterns: + - "Networking with the sole intent of selling. People sense transactional + intent and withdraw. The most productive agency networking is genuinely + helpful — offering introductions, sharing insights, solving problems + without expectation of return." + - "Limiting relationship-building to the founder. Every senior team member + should be building relationships in their domain. The agency's network + should be broader than any individual's." + agency_example: "An agency founder shifts from attending networking events + (transactional, low conversion) to hosting a monthly dinner for 8-10 + marketing leaders in her city. No pitch, no agenda — just honest + conversation about challenges in the industry. Within a year, five dinner + attendees have become clients, three have made referrals, and the founder + has become a known connector in the local marketing community. The cost: + $500/month in dinner expenses. The return: $400K in new business + attributable to dinner connections." + benchmark_references: [ "cost-per-lead", "pipeline-coverage-ratio", "win-rate" ] + + - skill: "inspiring-and-retaining" + category: "people" + agency_relevance: "high" + agency_context: "Inspiring and retaining talent in agencies requires + understanding what motivates agency professionals — and it is not + primarily compensation. Agency professionals are typically driven by: the + quality and variety of client work, the opportunity to develop expertise, + autonomy in how they approach problems, recognition for creative and + strategic contributions, and a sense of belonging to a team they respect. + The retention equation in agencies is further complicated by the fact that + every senior departure is a potential competitive threat — departing staff + can take clients, start competing practices, or join clients directly, + reducing the agency's relationship base." + agency_anti_patterns: + - "Attempting to retain through compensation alone when the underlying + work is unsatisfying. A 20% raise does not compensate for repetitive + work, difficult clients, and lack of growth." + - "Failing to give meaningful credit for contributions. In agencies where + senior leaders present work that junior staff created, the junior staff + feel invisible — and leave." + - "Not having honest conversations about career trajectories. Agencies + without clear paths to partnership, ownership, or expanded + responsibility lose ambitious people to firms that offer these paths." + agency_example: "A development agency losing senior developers to tech companies + at higher salaries reframes its retention strategy. Instead of trying to + match tech salaries (financially impossible), the agency emphasizes unique + advantages: variety of projects (tech companies offer one product; the + agency offers dozens), autonomy (developers choose their tech stack and + approach for each project), impact visibility (developers see their work + launched and used by real clients), and profit-sharing (a percentage of + project margins distributed quarterly). Attrition among senior developers + drops from 35% to 12% annually." + benchmark_references: [ "employee-retention-rate", "enps", "revenue-per-employee" ] + + # ───────────────────────────────────────────── + # STORYTELLING (1 skill) + # ───────────────────────────────────────────── + + - skill: "story-structure-and-arc" + category: "storytelling" + agency_relevance: "high" + agency_context: "Storytelling is the primary sales mechanism in professional + services. Agencies sell through stories: case studies that demonstrate + results, origin stories that establish credibility, client transformation + narratives that make intangible expertise tangible, and vision stories + that help prospects imagine a better future. The pitch process itself is a + story arc — situation (the client's current challenge), complication (why + the challenge is harder than it appears), resolution (the agency's + approach), and proof (evidence from similar situations). Agencies that + master storytelling convert at significantly higher rates than those that + present capabilities, methodologies, and credentials without narrative + structure." + agency_anti_patterns: + - "Presenting case studies as fact sheets rather than stories. 'We + redesigned the website and traffic increased 200%' is a fact. 'The + client was losing market share to a digitally native competitor, and the + outdated website was the most visible symptom of a deeper brand identity + crisis' is the beginning of a story." + - "Telling only success stories. The most powerful agency narratives + include honest moments of challenge, unexpected obstacles, and how the + team adapted — this builds trust through vulnerability." + agency_example: "A consulting firm restructures its pitch process around story + arc. Instead of opening with firm credentials (boring, self-oriented), + they open with a story about a similar client facing the same challenge — + the situation, the hidden complexity, the approach, and the measurable + outcome. The credentials slide moves to the appendix. Win rate increases + from 28% to 42% because prospects see themselves in the story and feel + confident the agency understands their world." + benchmark_references: [ "win-rate", "average-project-value" ] + + # ───────────────────────────────────────────── + # THINKING & DECISIONS (2 skills) + # ───────────────────────────────────────────── + + - skill: "defining-and-exploring-problems" + category: "thinking" + agency_relevance: "high" + agency_context: "The most valuable skill an agency can offer is problem + definition — helping clients understand what their real problem is before + jumping to solutions. Clients come to agencies with symptoms ('our website + is outdated,' 'our brand feels tired,' 'we need a new CRM'). The agency's + job is to diagnose the underlying problem, which is often different from + the stated symptom. An outdated website may reflect a deeper positioning + problem. A tired brand may reflect a product-market fit issue. A CRM + request may reflect a sales process failure that no technology will solve. + Agencies that excel at problem definition become trusted advisors; + agencies that simply execute the client's stated brief become + order-takers." + agency_anti_patterns: + - "Jumping to solutions because the client is impatient. Clients often + want to skip diagnosis and go straight to 'fix it.' The agency must + advocate for proper problem definition even when the client resists." + - "Defining the problem in terms of the agency's capabilities. A branding + agency sees every problem as a branding problem. A web agency sees every + problem as a website problem. The agency must diagnose honestly, even if + the solution lies outside its services." + agency_example: "A client approaches a digital agency requesting a complete + website redesign — a $120K project. During the discovery phase, the agency + applies problem-definition rigor and discovers that the website's traffic + is strong but conversion is abysmal. The real problem is not the design — + it is the unclear value proposition and confusing pricing page. The agency + recommends a $30K conversion optimization project instead of the $120K + redesign. The client is initially surprised but grateful. The optimization + project delivers a 3x conversion improvement, and the client becomes the + agency's most vocal advocate — generating $350K in referral revenue over + the next two years." + benchmark_references: [ "nps-client", "client-retention-rate", "revenue-per-client" ] + + - skill: "evaluating-and-deciding" + category: "thinking" + agency_relevance: "moderate" + agency_context: "Agency leaders face a distinct class of decisions shaped by the + people-as-product reality. The most consequential recurring decisions: + which clients to pursue (the portfolio decision), which people to hire + (the capability decision), which services to offer (the positioning + decision), how to price (the value-capture decision), and when to grow + versus when to consolidate (the timing decision). The decision-making + challenge in agencies is that most decisions have both financial and + relationship dimensions — declining a project may damage a client + relationship, firing a low performer may affect team morale, raising + prices may lose a client. Effective agency decision-making requires + weighing these dimensions simultaneously." + agency_anti_patterns: + - "Making decisions based solely on financial analysis without considering + relationship impact. The most profitable decision is not always the best + decision if it damages a strategically important relationship." + - "Delaying personnel decisions because of the personal difficulty. + Keeping a low-performing employee because the conversation is + uncomfortable harms the team, the clients, and ultimately the + individual." + agency_example: "An agency must decide whether to take on a large project from a + demanding client with a reputation for scope creep and late payment. + Financial analysis says yes — the project would fill bench capacity and + generate $200K in revenue. Relationship analysis says caution — the team + that would be assigned has already expressed frustration with difficult + clients, and assigning them to another one risks attrition. The agency + decides to accept the project but with structural protections: a detailed + SOW with explicit change-order processes, milestone-based billing, and a + project manager experienced with demanding clients. The decision weighs + both dimensions." + benchmark_references: [ "utilization-rate", "employee-retention-rate", "scope-creep-rate" ] diff --git a/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-templates.yaml b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-templates.yaml new file mode 100644 index 0000000..75d93ee --- /dev/null +++ b/plugins/foreman/content/industry-packs/agency-consulting/agency-consulting-templates.yaml @@ -0,0 +1,1020 @@ +# Agency/Consulting Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for agency and consulting businesses. The output agent +# loads these rules when generating documents with the agency/consulting +# industry pack active. +# +# Key adaptations across the template set: +# - Unit economics reframed as per-employee economics, not per-unit +# - Investor materials reframed for bank loans, revenue-based financing, +# and partnership buyouts — not VC fundraising +# - Operational templates emphasize resource allocation, utilization tracking, +# and capacity planning +# - Client templates emphasize proposal structure, SOW design, QBR for +# retainer clients, and project scope documentation +# - Self templates include founder capacity audit and the transition from +# practitioner to business leader +# +# Adaptation types: +# as-is — The template works without modification for agencies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for agency context. + +pack_metadata: + sector: "agency-consulting" + display_name: "Agency / Consulting" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # Reframed: most agencies do not raise VC. + # "Investor" = bank, revenue-based lender, partner + # buy-in/buyout, or strategic acquirer. + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agency unit economics are per-employee, not per-unit. The fundamental equation is Revenue = People x Utilization x Rate. The snapshot must present the economics of a billable person — what they cost, what they generate, and what margin they produce — because this is the atomic unit of agency value creation." + field_changes: + - field: "Revenue per unit" + sector_label: "Revenue per Billable Employee" + sector_guidance: "Calculate: average billable rate x average annual billable hours per person. Report blended across the firm and segmented by seniority level (junior, mid, senior, principal). Target: $150K-$250K per billable employee." + - field: "Cost per unit" + sector_label: "Fully Loaded Cost per Employee" + sector_guidance: "Include: salary, benefits, payroll taxes, training, tools/software, and allocated overhead (rent, admin, management). Report total cost and the cost-to-revenue ratio. Target: cost should be 40-55% of revenue per employee." + - field: "Margin per unit" + sector_label: "Margin per Employee" + sector_guidance: "Revenue per employee minus fully loaded cost per employee. This is the contribution margin each person generates. Target: $50K-$100K per billable employee. Partners/principals should generate $100K+ in margin." + - field: "Lifetime value" + sector_label: "Lifetime Value per Client" + sector_guidance: "Calculate: average revenue per client per year x average client tenure in years. Segment by engagement type (project vs. retainer). Retainer clients should have significantly higher LTV." + - field: "Acquisition cost" + sector_label: "Client Acquisition Cost" + sector_guidance: "Total business development and marketing spend divided by new clients acquired. Include the opportunity cost of senior staff time on BD. Most agencies undercount CAC because they do not value the partner's BD time." + - field: "Unit economics ratio" + sector_label: "Revenue Multiplier per Employee" + sector_guidance: "Revenue per employee divided by average compensation per employee. Target: 2.5x-3.5x multiplier. Below 2x indicates the firm cannot sustain itself. Above 4x indicates either exceptional pricing or underpaid staff." + sections_to_add: + - section_name: "Agency Economics Dashboard" + placement: "before:Revenue per Billable Employee" + description: "Core agency metrics that define the economic health of the firm." + fields: + - "Total revenue (trailing 12 months)" + - "Revenue per employee (FTE)" + - "Billable utilization rate (firm-wide)" + - "Average billable rate (blended)" + - "Effective billable rate (after write-offs and scope creep)" + - "Gross margin %" + - "EBITDA margin %" + - "Revenue per partner/principal" + - section_name: "Leverage and Efficiency Analysis" + placement: "after:Revenue Multiplier per Employee" + description: "The staffing model that drives agency margin." + fields: + - "Leverage ratio (junior:senior)" + - "Overhead ratio (non-delivery costs as % of revenue)" + - "Bench time (% of billable staff unassigned)" + - "Freelancer/subcontractor spend as % of revenue" + sections_to_remove: [] + benchmark_references: ["revenue-per-employee", "utilization-rate", "average-billable-rate", "effective-billable-rate", "gross-margin", "ebitda-margin", "leverage-ratio", "overhead-ratio"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agencies rarely send investor updates in the VC sense. This template is reframed as a lender or partner update — a periodic report to a bank holding a line of credit, a revenue-based financing partner, or an incoming partner being bought in." + field_changes: + - field: "Financial highlights" + sector_label: "Financial Summary" + sector_guidance: "Report: revenue (month and trailing 12-month), gross margin, EBITDA, utilization rate, AR days, and cash position. For lenders, emphasize debt service coverage ratio and cash flow stability." + - field: "Key metrics" + sector_label: "Operating Metrics" + sector_guidance: "Report: utilization rate, billable utilization rate, client count, pipeline coverage ratio, employee retention. Choose 3-4 metrics most relevant to the capital relationship." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include: major clients won, retainer renewals, notable deliverables, employee milestones. Quantify where possible (new client worth $X annual revenue)." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges. For lenders, flag any risks to revenue stability or cash flow. Be transparent about client concentration, pipeline gaps, or key person dependencies." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific. For lenders: 'We plan to draw $X from the line of credit in Q2 to fund two hires against confirmed pipeline.' For partners: 'We need your input on the Q3 pricing strategy.'" + sections_to_add: + - section_name: "Cash Position and Forecast" + placement: "after:Financial Summary" + description: "Cash flow visibility for capital partners." + fields: + - "Cash balance" + - "AR outstanding and aging" + - "Monthly cash burn / cash generation" + - "Months of runway (if applicable)" + sections_to_remove: [] + benchmark_references: ["revenue", "ebitda-margin", "ar-days", "utilization-rate"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agency competitive landscapes include four threat categories: competing agencies, freelancers/contractors, in-house teams, and AI tools. The brief should map all four, not just direct agency competitors." + field_changes: + - field: "Competitor overview" + sector_label: "Competitive Landscape Map" + sector_guidance: "Map competitors on two dimensions: (1) Direct agencies — firms offering similar services to similar clients. (2) Indirect substitutes — freelancer collectives, in-house teams, offshore firms, AI tools. Position each by price point and service depth." + - field: "Competitive advantages" + sector_label: "Defensibility Analysis" + sector_guidance: "Assess defensibility along agency-specific dimensions: client relationships (depth and breadth of contacts), domain expertise (vertical specialization), methodology (proprietary frameworks), team (specialized talent), and brand/reputation (referral strength, thought leadership, awards)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize: (1) Competing agencies — winning shared prospects or poaching clients. (2) Freelancer substitution — clients moving work to freelancers for cost savings. (3) In-housing — clients building internal teams. (4) AI displacement — tools performing tasks the agency bills for." + sections_to_add: + - section_name: "Client Switching Analysis" + placement: "after:Threat Vectors" + description: "Understanding how and why clients switch providers." + fields: + - "Reasons clients leave (from exit interviews and lost-business analysis)" + - "Switching costs the firm creates (institutional knowledge, relationship depth, process integration)" + - "Win/loss analysis by competitor type" + sections_to_remove: [] + benchmark_references: ["win-rate", "client-retention-rate", "average-billable-rate"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Most agencies do not create fundraising decks for VC. This template is reframed as a financing deck — used for bank loan applications, revenue-based financing proposals, partnership buy-in presentations, or strategic acquisition discussions." + field_changes: + - field: "Market opportunity" + sector_label: "Market Position and Growth Potential" + sector_guidance: "Present: the firm's market niche, addressable client base, competitive differentiation, and realistic growth trajectory. For bank lenders, emphasize market stability and recurring revenue. For strategic acquirers, emphasize unique capabilities and client relationships." + - field: "Business model" + sector_label: "Agency Business Model" + sector_guidance: "Cover: service offerings, pricing model (hourly/project/retainer/value-based mix), client segmentation, delivery model (core team + freelancer network), and the economic leverage of the staffing model." + - field: "Traction" + sector_label: "Financial Track Record" + sector_guidance: "Present: 3-year revenue history, margin trajectory, client retention rate, utilization trend, and pipeline coverage. For lenders, emphasize stability and predictability. For acquirers, emphasize growth and scalability." + sections_to_add: + - section_name: "Capital Use and Return" + placement: "after:Financial Track Record" + description: "Clear plan for how capital will be deployed and the expected return." + fields: + - "Capital amount requested and structure (loan, line of credit, equity)" + - "Use of proceeds (specific: hire X people, fund Y initiative)" + - "Revenue and margin impact of the investment" + - "Payback timeline" + - section_name: "Client and Revenue Stability" + placement: "after:Capital Use and Return" + description: "Evidence of revenue durability for lender confidence." + fields: + - "Client retention rate (3-year trend)" + - "Recurring revenue percentage (retainers and ongoing contracts)" + - "Client concentration analysis (top 1, 5, 10 clients as % of revenue)" + - "Contract backlog (signed but undelivered revenue)" + sections_to_remove: [] + benchmark_references: ["revenue", "ebitda-margin", "client-retention-rate", "client-concentration"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "An agency strategic one-pager must frame the firm's position in terms relevant to professional services — specialization, client relationships, team quality, and pricing power — rather than generic strategic frameworks." + field_changes: + - field: "Strategic position" + sector_label: "Agency Strategic Position" + sector_guidance: "Frame: the firm's specialization (what and for whom), competitive differentiation (why clients choose this firm), pricing power (can the firm charge premium rates), and growth model (organic client acquisition, vertical expansion, geographic expansion, or productization)." + - field: "Key metrics" + sector_label: "Agency Health Metrics" + sector_guidance: "Core 5: Revenue per employee, utilization rate, gross margin, client retention rate, employee retention rate. Compare each to benchmarks for the firm's size and discipline." + sections_to_add: + - section_name: "People and Capacity Assessment" + placement: "end" + description: "Assessment of the firm's production capacity and talent quality." + fields: + - "Current team size and leverage model" + - "Key person dependencies" + - "Capacity utilization (current vs. maximum)" + - "Talent pipeline strength (ease of hiring for critical roles)" + sections_to_remove: [] + benchmark_references: ["revenue-per-employee", "utilization-rate", "gross-margin", "client-retention-rate", "employee-retention-rate"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agency market opportunity is not TAM/SAM/SOM in the traditional sense. It is about: the size of the addressable client base, the firm's share of wallet within existing clients, and the expansion potential into adjacent services or verticals." + field_changes: + - field: "Total addressable market" + sector_label: "Addressable Client Base" + sector_guidance: "Size the market bottom-up: (number of organizations that match the firm's ideal client profile) x (average annual spend on the services the firm provides). For agencies, the relevant market is the intersection of client type, geography, and service need." + - field: "Market dynamics" + sector_label: "Professional Services Market Dynamics" + sector_guidance: "Address: client budget trends (growing, stable, declining for the firm's services), competitive density (number and quality of competing firms), substitution pressure (in-housing, freelancers, AI), and regulatory environment (industry-specific compliance that creates demand)." + sections_to_add: + - section_name: "Share of Wallet Expansion" + placement: "end" + description: "Growth potential within existing clients — often the most capital-efficient growth source for agencies." + fields: + - "Average share of wallet in existing clients (estimated)" + - "Adjacent services that existing clients buy from other providers" + - "Cross-sell and upsell potential" + sections_to_remove: [] + benchmark_references: ["revenue-per-client", "client-retention-rate"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agency due diligence focuses on areas unique to people-businesses: client relationship durability, key person risk, revenue concentration, employee retention, and the contractual basis of revenue." + field_changes: + - field: "Financial review" + sector_label: "Agency Financial Verification" + sector_guidance: "Verify: revenue by client (concentration analysis), revenue by type (project vs. retainer vs. hourly), utilization data, effective rate realization, gross margin methodology, and EBITDA normalization (owner compensation adjustments). Request aged AR report and historical write-off data." + - field: "Operational review" + sector_label: "Client and Talent Review" + sector_guidance: "Review: top 10 client relationships (tenure, revenue trend, contract terms, key contacts), employee retention data by seniority, non-compete and non-solicit agreements, freelancer agreements, and any pending or historical legal disputes." + sections_to_add: + - section_name: "Key Person and Client Risk Assessment" + placement: "end" + description: "Agency-specific risk factors that determine business durability." + fields: + - "Key person identification (people whose departure would directly impact revenue)" + - "Client relationship mapping (which clients are relationship-dependent vs. institutionally loyal)" + - "Non-compete/non-solicit coverage and enforceability" + - "Contractual revenue base (signed contracts and retainers vs. at-will engagement)" + - "Backlog analysis (contracted but undelivered revenue)" + sections_to_remove: [] + benchmark_references: ["client-concentration", "employee-retention-rate", "revenue-per-client", "ar-days"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agencies are typically structured as partnerships, LLCs, or S-corps rather than C-corps with VC equity. The cap table equivalent is the partnership agreement — ownership percentages, profit-sharing arrangements, buy-sell provisions, and vesting of partner equity." + field_changes: + - field: "Ownership structure" + sector_label: "Partnership/Ownership Structure" + sector_guidance: "Present: current ownership percentages, voting rights, profit distribution methodology (equal split, contribution-based, formula-based), buy-sell agreement terms (valuation methodology, payment terms, trigger events), and any phantom equity or profit-sharing arrangements for non-owner employees." + sections_to_add: + - section_name: "Partnership Economics" + placement: "end" + description: "How partnership compensation and profit distribution work." + fields: + - "Partner compensation structure (salary + profit distribution)" + - "Profit distribution methodology and timing" + - "Capital contribution requirements" + - "Exit/buyout valuation methodology (revenue multiple, EBITDA multiple, book value)" + sections_to_remove: [] + benchmark_references: ["ebitda-margin", "revenue-per-partner"] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Decision rationale documentation follows a standard format across sectors. Agency context is naturally incorporated through the specific decision being documented." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Agency exit scenarios include acquisition by a larger agency or holding company, management buyout, partner buyout, employee stock ownership plan (ESOP), or simply running the business for cash flow indefinitely. VC-style exits (IPO, unicorn acquisition) are extremely rare." + field_changes: + - field: "Valuation methodology" + sector_label: "Agency Valuation Methods" + sector_guidance: "Agencies are typically valued on EBITDA multiples (3-8x depending on size, growth, and client quality), revenue multiples (0.5-1.5x for most agencies), or discounted cash flow. Key valuation drivers: recurring revenue percentage, client concentration, key person dependency, and growth trajectory. Premium multiples for: strong vertical specialization, productized service components, and low client concentration." + - field: "Potential acquirers" + sector_label: "Exit Pathways" + sector_guidance: "Categorize: (1) Holding companies (WPP, Omnicom, IPG for large agencies; smaller rollup firms for mid-size agencies). (2) Larger agencies seeking capabilities or client access. (3) Management/employee buyout (funded by SBA loan, seller financing, or earnout). (4) Partner buyout (new partner buying in, existing partner buying out). (5) ESOP (employee ownership transition). (6) Lifestyle operation (run for cash flow indefinitely)." + sections_to_add: + - section_name: "Agency Valuation Drivers" + placement: "after:Agency Valuation Methods" + description: "Factors that increase or decrease agency valuation." + fields: + - "Recurring revenue percentage (higher = higher multiple)" + - "Client concentration (lower = higher multiple)" + - "Key person dependency (lower = higher multiple)" + - "Employee retention and culture strength" + - "Proprietary methodology or productized services" + - "Growth trajectory and pipeline strength" + sections_to_remove: [] + benchmark_references: ["ebitda-margin", "client-concentration", "client-retention-rate", "revenue"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # Reframed: most agencies do not have formal + # boards. "Board" = advisory board, partner + # meeting, or leadership team review. + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency quarterly reviews — whether for partners, advisory boards, or leadership teams — should center on the three pillars of agency health: clients (retention, satisfaction, concentration), people (utilization, retention, development), and finances (revenue, margins, cash flow)." + field_changes: + - field: "Financial summary" + sector_label: "Agency Financial Dashboard" + sector_guidance: "Present: revenue (quarter and trailing 12-month), revenue by client (top 10), gross margin, EBITDA, utilization rate, effective billable rate, AR days, and cash position. Compare each to plan and to prior quarter." + - field: "Strategic priorities" + sector_label: "Strategic Priorities and Progress" + sector_guidance: "Report against quarterly priorities. For agencies, typical strategic priorities include: client acquisition (pipeline and wins), client retention (NPS and at-risk accounts), team development (hiring and retention), operational improvement (utilization, scope management), and positioning (specialization, thought leadership)." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: Client risks (concentration, at-risk accounts, contract expirations), People risks (key person dependency, attrition, burnout), Financial risks (cash flow, AR aging, margin compression), and Market risks (competitive threats, in-housing trends, AI displacement)." + sections_to_add: + - section_name: "Client Health Summary" + placement: "before:Agency Financial Dashboard" + description: "Overview of the client portfolio health." + fields: + - "Client count (active)" + - "Client retention rate (trailing 12-month)" + - "Client NPS (most recent)" + - "Top client concentration (largest as % of revenue)" + - "At-risk accounts (identified and action plan status)" + - "New clients won (quarter)" + - section_name: "People Health Summary" + placement: "after:Agency Financial Dashboard" + description: "Team health metrics — the most important asset in an agency." + fields: + - "Headcount (FTE)" + - "Billable utilization rate" + - "Bench time (%)" + - "Employee retention rate (trailing 12-month)" + - "eNPS (most recent)" + - "Open positions and hiring pipeline" + - section_name: "Pipeline and Forecast" + placement: "after:People Health Summary" + description: "Forward-looking revenue visibility." + fields: + - "Pipeline coverage ratio" + - "Weighted pipeline value" + - "Revenue forecast (next quarter)" + - "Contracted backlog" + sections_to_remove: [] + benchmark_references: ["revenue", "utilization-rate", "gross-margin", "ebitda-margin", "client-concentration", "client-retention-rate", "employee-retention-rate", "pipeline-coverage-ratio", "ar-days"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency partner meetings or advisory board sessions should balance the three agency pillars — clients, people, finances — and include time for strategic discussion beyond operational review." + field_changes: + - field: "Agenda items" + sector_label: "Agency Leadership Meeting Agenda" + sector_guidance: "Recommended structure: (1) Client review — 15 min (at-risk accounts, major wins, retention actions). (2) People review — 10 min (utilization, retention, key hiring). (3) Financial review — 10 min (revenue, margins, cash flow — pre-read). (4) Strategic topic deep-dive — 30 min (one topic per meeting: positioning, pricing, new service line, vertical expansion). (5) Action items and decisions — 10 min. Total: 75 minutes maximum." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency risk categories center on client concentration, key person dependency, and revenue predictability — risks unique to people-as-product businesses." + field_changes: + - field: "Risk categories" + sector_label: "Agency Risk Categories" + sector_guidance: "Include agency-specific categories: (1) Client concentration risk — revenue dependency on top clients. (2) Key person risk — employees whose departure would directly impact revenue. (3) Revenue predictability risk — percentage of revenue that is project-based vs. recurring. (4) Talent risk — ability to recruit and retain the right people. (5) Pricing risk — competitive pressure on rates. (6) Scope management risk — systematic underscoping or scope creep. (7) AI disruption risk — services vulnerable to automation." + sections_to_add: + - section_name: "Key Person Risk Matrix" + placement: "end" + description: "Assessment of business impact if specific individuals were to depart." + fields: + - "Key person identification (name, role, client relationships managed)" + - "Revenue at risk if each key person departs" + - "Mitigation actions (relationship distribution, non-competes, retention incentives)" + - "Succession readiness for each key role" + sections_to_remove: [] + benchmark_references: ["client-concentration", "employee-retention-rate"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "Change initiative proposals follow a standard format. Agency context is naturally incorporated through the specific initiative — whether pricing restructure, vertical specialization, or service model change." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency compensation is distinct: lower base salaries than tech but potentially higher total compensation through profit sharing, bonuses, and ownership. The compensation structure directly affects retention — the most critical operational metric." + field_changes: + - field: "Compensation benchmarks" + sector_label: "Agency Compensation Benchmarks" + sector_guidance: "Benchmark using agency-specific data: SPI Research compensation studies, Bureau of Labor Statistics professional services data, Glassdoor agency-specific roles, and local market surveys. Compare total compensation (base + bonus + profit sharing) rather than base alone." + sections_to_add: + - section_name: "Revenue Multiplier Analysis" + placement: "end" + description: "The relationship between compensation and revenue generation." + fields: + - "Revenue multiplier by role (revenue generated / total compensation)" + - "Target multiplier by seniority (junior: 3x, mid: 2.5x, senior: 2.5x, partner: 3-5x)" + - "Profit-sharing or bonus structure and its effect on retention" + - "Path-to-ownership economics (if applicable)" + sections_to_remove: [] + benchmark_references: ["revenue-per-employee", "employee-retention-rate"] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency compliance concerns include: data handling (GDPR, CCPA for client data), advertising regulations (FTC, industry-specific rules), employment law (contractor classification, non-competes), and industry-specific compliance (healthcare for HIPAA, finance for FINRA, if serving regulated industries)." + field_changes: + - field: "Regulatory landscape" + sector_label: "Agency Compliance Landscape" + sector_guidance: "Cover: data privacy (GDPR, CCPA — agencies handling client customer data), employment law (contractor classification, non-compete enforceability in relevant jurisdictions), advertising regulations (FTC disclosure requirements, industry-specific ad rules), and insurance (professional liability/E&O coverage adequacy)." + sections_to_add: + - section_name: "Contractor Classification Risk" + placement: "end" + description: "Agencies using freelancers face classification risk — a critical compliance area." + fields: + - "Number of regular freelancers/contractors" + - "Classification methodology (independent contractor criteria met?)" + - "Jurisdictional risk assessment (states/countries with strict classification rules)" + - "Insurance and indemnification coverage" + sections_to_remove: [] + benchmark_references: [] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Agency succession is the most consequential transition in the business — the founder is often the firm's primary relationship holder, rainmaker, and quality standard. Succession planning must address client relationship transfer, not just management transfer." + field_changes: + - field: "Succession candidates" + sector_label: "Succession Readiness Assessment" + sector_guidance: "Assess candidates on three agency-specific dimensions: (1) Client relationships — do key clients trust and respect the successor? (2) Business development — can the successor win new business, not just manage existing accounts? (3) Team leadership — can the successor inspire and retain the team that defines the firm's delivery quality?" + sections_to_add: + - section_name: "Client Transition Plan" + placement: "end" + description: "How key client relationships will transfer during leadership transition." + fields: + - "Key client relationships currently owned by departing leader" + - "Transition timeline for each relationship (gradual introduction over 6-12 months)" + - "Risk assessment for each relationship during transition" + - "Communication plan for clients" + sections_to_remove: [] + benchmark_references: ["client-retention-rate", "revenue-per-partner"] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency action plans should connect to the dual objectives of client delivery and firm building, with explicit consideration of utilization and capacity impact." + field_changes: + - field: "Success metrics" + sector_label: "Agency KPI Targets" + sector_guidance: "Define success using agency metrics: utilization impact, client retention effect, revenue per client change, pipeline coverage improvement, or employee retention. Every action item should connect to a measurable agency KPI. Explicitly note the capacity cost — how many billable hours this initiative consumes." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["utilization-rate", "client-retention-rate"] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency initiatives must be evaluated for their impact on the firm's most constrained resource: billable people's time. Every initiative that consumes billable hours has a direct opportunity cost measured in lost revenue." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected Agency Impact" + sector_guidance: "Quantify impact on agency economics: revenue contribution, margin improvement, client retention improvement, utilization effect, or positioning benefit. Include the timeline to measurable impact." + - field: "Resource requirements" + sector_label: "Resource Requirements and Billable Opportunity Cost" + sector_guidance: "Quantify the hours required from billable staff and the revenue those hours would have generated if billed to clients. This opportunity cost calculation forces honest prioritization." + sections_to_add: + - section_name: "Billable Impact Analysis" + placement: "after:Expected Agency Impact" + description: "The effect on utilization and billable capacity." + fields: + - "Billable hours consumed by this initiative" + - "Revenue opportunity cost (hours x effective rate)" + - "Expected revenue return (when and how much)" + - "Breakeven timeline" + sections_to_remove: [] + benchmark_references: ["utilization-rate", "revenue-per-employee"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency project kickoffs should define scope boundaries with surgical precision — scope creep prevention begins at kickoff, not when overruns are already underway." + field_changes: + - field: "Success criteria" + sector_label: "Deliverables, Scope Boundaries, and Success Metrics" + sector_guidance: "Define three things explicitly: (1) What is IN scope — specific deliverables with acceptance criteria. (2) What is OUT of scope — explicit exclusions to prevent assumption-based creep. (3) Change-order process — how scope additions are requested, approved, and billed. Include budget hours and the process for flagging when 80% of budget is consumed." + sections_to_add: + - section_name: "Resource Allocation and Timeline" + placement: "after:Deliverables, Scope Boundaries, and Success Metrics" + description: "Who is assigned, for how many hours, and on what timeline." + fields: + - "Team members assigned (name, role, allocated hours)" + - "Key milestones and delivery dates" + - "Client responsibilities and dependencies" + - "Escalation path for scope or timeline issues" + sections_to_remove: [] + benchmark_references: ["scope-creep-rate", "effective-billable-rate"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency hiring scorecards must assess both craft skills (can they do the work?) and client-service skills (can they manage relationships, communicate professionally, and represent the firm?)." + field_changes: + - field: "Required competencies" + sector_label: "Agency-Specific Competencies" + sector_guidance: "For delivery roles: craft quality, time management, client communication, and ability to work within scope constraints. For account roles: relationship building, business development aptitude, negotiation skill, and commercial awareness. For all roles: assess fit with the firm's culture, willingness to track time, and comfort with the billable-hours reality of agency life." + sections_to_add: + - section_name: "Client-Readiness Assessment" + placement: "end" + description: "Assessment of the candidate's readiness for client-facing work." + fields: + - "Communication quality (written and verbal)" + - "Presentation confidence" + - "Ability to manage ambiguity and client feedback" + - "Professional polish and reliability" + - "Estimated time to full client-facing deployment" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency incidents are primarily client-facing: missed deadlines, quality failures, scope disputes, or relationship breakdowns. The postmortem must address both the operational failure and the client relationship impact." + field_changes: + - field: "Impact assessment" + sector_label: "Client and Business Impact" + sector_guidance: "Quantify: which client(s) affected, relationship impact assessment (at-risk? frustrated? understanding?), financial impact (write-offs, penalties, lost future revenue risk), and team impact (morale, overtime, burnout). Include the client communication log." + sections_to_add: + - section_name: "Client Relationship Recovery" + placement: "after:Client and Business Impact" + description: "Plan for restoring client confidence after the incident." + fields: + - "Client communication (what was communicated, when, by whom)" + - "Client sentiment after communication" + - "Recovery actions (additional deliverables, discounts, senior attention)" + - "Relationship health check (scheduled follow-up)" + sections_to_remove: [] + benchmark_references: ["nps-client", "client-retention-rate"] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency retrospectives should evaluate project profitability and client satisfaction alongside team process — the economic outcome matters as much as the process quality." + field_changes: + - field: "What went well" + sector_label: "What Went Well (Delivery and Client)" + sector_guidance: "Include both internal process successes and client-facing successes. Did the project deliver on time and on budget? Was the client satisfied? Did the work generate a referral or case study opportunity?" + sections_to_add: + - section_name: "Project Economics Review" + placement: "end" + description: "Financial review of project performance." + fields: + - "Budgeted hours vs. actual hours" + - "Effective rate achieved vs. target" + - "Scope changes and their financial impact" + - "Lessons for future scoping and pricing" + sections_to_remove: [] + benchmark_references: ["effective-billable-rate", "scope-creep-rate"] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency one-on-ones should explicitly address the dual dimensions of work that affect agency professionals: project satisfaction (are they doing interesting, challenging work?) and utilization reality (are they billing enough, are they overwhelmed, do they need more or different work?)." + field_changes: + - field: "Discussion topics" + sector_label: "Agency-Specific Discussion Topics" + sector_guidance: "Include agency-specific check-ins: (1) Current project satisfaction — is the work engaging and developmental? (2) Client relationship health — any concerns about client interactions? (3) Utilization and workload — too much, too little, or the right amount? (4) Career development — what skills do they want to develop? (5) Work environment — any cultural or team concerns?" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency team health must include utilization balance, client-service stress levels, and the sell-deliver alignment that defines agency operational health." + field_changes: + - field: "Health indicators" + sector_label: "Agency Team Health Indicators" + sector_guidance: "Include agency-specific indicators: utilization balance (overworked vs. underutilized), client satisfaction with team members, sell-deliver alignment (are commitments realistic?), overtime frequency, work variety (are people stuck on repetitive accounts?), and professional development progress." + sections_to_add: + - section_name: "Utilization and Workload Balance" + placement: "end" + description: "Assessment of whether the team's workload is sustainable and well-distributed." + fields: + - "Utilization distribution (who is over/under-utilized)" + - "Overtime hours (last month)" + - "Staff working on a single client for more than 6 months (risk of monotony and client dependency)" + - "Bench time distribution" + sections_to_remove: [] + benchmark_references: ["utilization-rate", "bench-time", "enps"] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Culture and values documentation is not sector-specific. Values should be authentic to the firm, not to the sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency 360 feedback should include client feedback as a dimension — how the person is perceived by the clients they serve is as important as how they are perceived by colleagues." + field_changes: + - field: "Feedback sources" + sector_label: "Agency 360 Feedback Sources" + sector_guidance: "Include four feedback dimensions: (1) Manager assessment. (2) Peer assessment. (3) Direct report assessment (if applicable). (4) Client assessment — request feedback from 2-3 client contacts on the person's communication, reliability, and impact. Client feedback is a unique and invaluable data source in agency settings." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning structure is not sector-specific, though content will naturally address agency topics." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Agency role descriptions must specify the utilization expectation, client-facing responsibilities, and the balance between billable delivery and non-billable activities for each role." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Utilization Expectation" + sector_guidance: "For each role, specify: (1) Primary responsibilities (delivery, client management, business development, or operations). (2) Utilization target (billable hours as % of available hours). (3) Client-facing expectations (direct client contact? presentations? relationship management?). Typical utilization targets: junior delivery 70-80%, senior delivery 60-70%, account manager 50-60%, partner 30-50%, operations 0%." + - field: "Required experience" + sector_label: "Agency Experience Requirements" + sector_guidance: "Specify: agency or professional services experience expected, client-service orientation, comfort with time tracking, and the specific discipline expertise required. Distinguish between 'must have agency experience' roles and 'can learn agency dynamics' roles." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["utilization-rate"] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An agency founder's weekly review must balance the practitioner role (am I delivering quality work?) with the business-builder role (am I developing the firm?). The most important weekly metric is the split between billable and non-billable time." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly Agency Dashboard" + sector_guidance: "Review weekly: personal billable hours (target vs. actual), firm utilization rate, pipeline changes, cash position, AR aging, active client count. Monthly metrics (retention, NPS, margins) should be reviewed monthly, not weekly." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Categorize into the four quadrants: (1) Client delivery — which projects need my attention? (2) Business development — which prospects am I advancing? (3) Team management — which people issues need resolution? (4) Firm building — what system, process, or strategy am I advancing? Ruthlessly limit to 3-5 items total." + sections_to_add: + - section_name: "Founder Capacity Audit" + placement: "after:Weekly Agency Dashboard" + description: "Weekly tracking of how the founder's time is allocated — the most revealing agency metric." + fields: + - "Hours on billable client work" + - "Hours on business development (proposals, networking, pitches)" + - "Hours on team management (meetings, reviews, mentoring)" + - "Hours on firm building (strategy, operations, finance)" + - "Hours on administrative tasks (email, scheduling, invoicing)" + - "Total hours worked" + - "Trend assessment: am I shifting toward or away from the right allocation?" + sections_to_remove: [] + benchmark_references: ["utilization-rate", "pipeline-coverage-ratio"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency decision journals should explicitly capture the dual dimensions of agency decisions — financial impact and relationship impact — and the specific agency metrics that informed the decision." + field_changes: + - field: "Decision context" + sector_label: "Decision Context and Data" + sector_guidance: "Record: the agency metrics that informed this decision (utilization data, client concentration, pipeline status), the relationship dimension (how does this affect key client or employee relationships?), the alternatives considered, and the specific metric and relationship outcomes that will confirm the decision was correct." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency annual reviews should assess the firm across clients, people, and finances — and honestly evaluate whether the founder's personal role is evolving appropriately." + field_changes: + - field: "Year in review" + sector_label: "Agency Year in Review" + sector_guidance: "Assess across the three pillars: Clients (retention rate, NPS, concentration change, major wins and losses), People (retention rate, eNPS, key hires and departures, bench time), Finances (revenue growth, margin trajectory, utilization trend, cash flow). Honestly assess: am I still doing the same role I was doing a year ago, or have I evolved as a leader?" + - field: "Next year goals" + sector_label: "Next Year Agency Targets" + sector_guidance: "Set targets across all dimensions: revenue target, margin target, client retention target, employee retention target, utilization target, and personal development goal. Each target should reference the benchmark tier being pursued. Include a personal role-evolution goal: what will I delegate this year that I currently do myself?" + sections_to_add: + - section_name: "Founder Role Evolution" + placement: "end" + description: "Honest assessment of the founder's personal transition from practitioner to business leader." + fields: + - "Percentage of time on billable work (current vs. target)" + - "Percentage of time on business development (current vs. target)" + - "Percentage of time on management and leadership (current vs. target)" + - "What did I delegate this year that I used to do myself?" + - "What should I delegate next year?" + - "What do I need to learn to be effective at my evolving role?" + sections_to_remove: [] + benchmark_references: ["revenue", "ebitda-margin", "client-retention-rate", "employee-retention-rate", "utilization-rate"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency stakeholder maps should center on the relationship web that defines agency success — client contacts, referral partners, talent sources, and industry influencers." + field_changes: + - field: "Stakeholder categories" + sector_label: "Agency Stakeholder Ecosystem" + sector_guidance: "Include: Clients (primary contacts, champions, economic buyers, internal sponsors), Referral Partners (complementary firms, former colleagues, industry connections), Talent Sources (recruiters, universities, professional networks, freelancer community), Industry (conference organizers, publication editors, community leaders, trade association contacts), and Financial (banker, accountant, lawyer, insurance broker)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency negotiation prep should address the specific negotiation types and leverage dynamics unique to professional services." + field_changes: + - field: "Negotiation type" + sector_label: "Agency Negotiation Context" + sector_guidance: "Classify: scope negotiation (additional work within existing budget), rate negotiation (client pushing for lower rates), contract terms (SOW, liability, IP ownership), retainer renewal (scope and rate restructuring), new business pitch (competitive proposal), talent negotiation (compensation, role definition), or partner negotiation (equity, profit sharing, role boundaries)." + - field: "BATNA" + sector_label: "BATNA and Agency Leverage" + sector_guidance: "Agency-specific leverage points: for client negotiations — institutional knowledge, relationship depth, switching costs, portfolio of work, competitive alternatives. For rate negotiations — value documentation, outcome metrics, competitive rate benchmarks. For talent negotiations — culture, work quality, growth opportunity, flexibility, ownership path." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["average-billable-rate", "client-retention-rate"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "For agency founders, career strategy is inseparable from firm strategy. The canvas should address the founder's intended trajectory: remain as practitioner-owner, transition to managing director, build toward exit, or evolve to a portfolio of interests." + field_changes: + - field: "Career vision" + sector_label: "Founder-Firm Vision Alignment" + sector_guidance: "Address: (1) What do I want the firm to look like in 5 years? (2) What role do I want to play in that firm? (3) Are these compatible? A founder who wants a 50-person agency but also wants to personally do strategy work has a contradiction that must be resolved. (4) What is my exit or endgame — sell, transition to partners, scale, or sustain as lifestyle?" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency founder mental health is affected by agency-specific stressors: the personal nature of client rejection, the isolation of carrying client relationships alone, the guilt of being unable to shield the team from demanding clients, and the identity fusion between personal reputation and firm performance." + field_changes: + - field: "Stress indicators" + sector_label: "Agency-Specific Stress Indicators" + sector_guidance: "Include: inability to stop working on client projects (checking email at midnight for client responses), avoidance of difficult client conversations (absorbing scope creep rather than confronting it), identity fusion with client satisfaction (personal mood tracking with client feedback), isolation (not discussing business challenges with peers or advisors), and decision fatigue (avoiding hiring, pricing, or strategic decisions because they feel overwhelming)." + sections_to_add: + - section_name: "Boundary Assessment" + placement: "end" + description: "Assessment of work-life boundaries — particularly challenging for agency founders." + fields: + - "Hours worked per week (honest count)" + - "Days without checking client email/Slack" + - "Vacations taken without working (truly disconnected)" + - "Client emergencies that could have been handled by someone else" + - "Scope creep absorbed rather than addressed (this week)" + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific. The reflections naturally address agency-specific challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Agency founders should include agency-specific learning areas alongside general leadership development." + field_changes: + - field: "Learning areas" + sector_label: "Agency Learning Priorities" + sector_guidance: "Consider agency-specific learning areas: agency pricing strategy (value-based, productized), business development and sales for services, account management and client retention, financial management for services firms, talent management and culture building, AI integration for agency services, and personal transition from practitioner to business leader." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An agency founder's personal advisory network should include people who have navigated the specific challenges of building a services business." + field_changes: + - field: "Advisor categories" + sector_label: "Agency Advisory Needs" + sector_guidance: "Map advisors to agency-specific needs: Agency operator (someone who has built and scaled an agency to $5M+), Financial (accountant experienced with services firms, banker for credit facilities), Legal (employment law, client contracts, partnership agreements), Talent (recruiter or HR advisor for agency-specific roles), Industry (domain expert in the firm's target vertical), Peer (other agency founders at a similar stage for honest exchange)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # These are among the most important templates + # for agencies — client-facing documents are + # the primary expression of the firm's quality. + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency QBRs are the primary retention and expansion vehicle for retainer clients. The QBR must demonstrate the value delivered (connecting agency work to client business outcomes), review the relationship health, and identify opportunities for expanded engagement. A strong QBR is the single best defense against client churn." + field_changes: + - field: "Performance summary" + sector_label: "Value Delivered" + sector_guidance: "Quantify the value the agency delivered this quarter: campaigns launched, deliverables completed, business outcomes influenced (traffic, leads, revenue, brand awareness, operational efficiency). Use the client's own metrics and language. Present the work in context — not 'we wrote 12 blog posts' but 'the 12 content pieces generated 1,400 qualified leads against a target of 1,000.'" + - field: "Account status" + sector_label: "Engagement Summary" + sector_guidance: "Present: hours consumed vs. retainer allocation, deliverables completed vs. planned, scope changes (if any) and their impact, and team members engaged on the account." + - field: "Next steps" + sector_label: "Recommended Next Steps and Expansion Opportunities" + sector_guidance: "Identify opportunities for expanded engagement: new services, increased scope, additional deliverables, or strategic projects. Frame as business outcomes ('based on Q2 results, we recommend testing a paid acquisition strategy that could generate an additional 500 leads/month') rather than service pitches." + sections_to_add: + - section_name: "Relationship Health Assessment" + placement: "before:Value Delivered" + description: "Proactive assessment of the working relationship." + fields: + - "Overall satisfaction (ask directly during the QBR)" + - "Communication effectiveness" + - "Team fit and responsiveness" + - "Areas for improvement (agency-side)" + - section_name: "Strategic Recommendations" + placement: "after:Recommended Next Steps and Expansion Opportunities" + description: "Proactive strategic counsel that positions the agency as a trusted advisor." + fields: + - "Market trends or competitive changes the client should be aware of" + - "Opportunities the agency sees based on its industry perspective" + - "Recommended strategic priorities for next quarter" + sections_to_remove: [] + benchmark_references: ["nps-client", "revenue-per-client", "client-retention-rate"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency client onboarding sets the tone for the entire relationship. The welcome packet should establish clear expectations, introduce the team, define communication norms, and demonstrate professionalism from the first interaction." + field_changes: + - field: "Getting started steps" + sector_label: "Engagement Kickoff Path" + sector_guidance: "Structure as: (1) Discovery and briefing — what the agency needs from the client (brand assets, access, background documents). (2) Team introduction — who will work on the account, their roles, and their contact information. (3) Communication norms — meeting cadence, preferred communication channels, response time expectations, escalation path. (4) First milestone — what will be delivered and when, creating early momentum." + - field: "Resources" + sector_label: "Working with Us" + sector_guidance: "Include: the agency's working methodology (how projects progress from brief to delivery), feedback and revision process (how many rounds, how to provide feedback effectively), approval workflows, and a glossary of agency terminology the client may encounter." + sections_to_add: + - section_name: "Scope and Boundary Document" + placement: "end" + description: "Clear statement of what is included and what requires additional agreement." + fields: + - "Scope summary (what is included in the engagement)" + - "Out-of-scope items (explicit exclusions)" + - "Change-order process (how to request additional work)" + - "Key dates and milestones" + sections_to_remove: [] + benchmark_references: ["scope-creep-rate", "nps-client"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency proposals are the primary sales vehicle. The proposal must sell the firm's understanding of the problem (not its capabilities), present a credible approach, and justify the investment through expected outcomes. The proposal itself is a demonstration of the firm's thinking quality." + field_changes: + - field: "Pricing" + sector_label: "Investment and Expected Value" + sector_guidance: "Present pricing in the context of expected value. Structure options: (1) Investment amount (project fee, retainer, or phased pricing). (2) What is included (deliverables, meetings, revisions). (3) What is not included (explicit exclusions to prevent scope assumption). (4) Expected return (how the investment will pay for itself in client business terms). Where possible, offer 2-3 pricing tiers to anchor the client's decision." + - field: "Scope" + sector_label: "Approach and Scope of Work" + sector_guidance: "Lead with the agency's understanding of the client's problem (demonstrate listening), then present the approach (methodology, phases, deliverables), then detail the scope (what, when, who). The scope section should be precise enough to serve as the SOW foundation — reducing the gap between proposal acceptance and contract signature." + sections_to_add: + - section_name: "Why Us" + placement: "end" + description: "Concise case for why this agency is the right partner — not a generic capabilities list." + fields: + - "Relevant experience (2-3 case studies directly applicable to this engagement)" + - "Team assigned (specific people, not generic role titles)" + - "What makes our approach different (methodology, perspective, or commitment)" + sections_to_remove: [] + benchmark_references: ["win-rate", "average-project-value"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency SLAs define the operational commitments that underpin client trust — response times, deliverable quality standards, communication cadence, and escalation procedures." + field_changes: + - field: "Service levels" + sector_label: "Agency Service Commitments" + sector_guidance: "Standard agency SLA components: (1) Response time — email within X hours, urgent matters within Y hours. (2) Deliverable timeline — first draft within X days of brief approval. (3) Revision process — X rounds of revisions included; additional rounds billed at Z rate. (4) Communication cadence — weekly status call, monthly report, quarterly QBR. (5) Team continuity — commitment to maintain named team members for duration of engagement." + - field: "Remediation" + sector_label: "Issue Resolution Process" + sector_guidance: "Define: escalation ladder (project manager > account director > partner), timeline for issue resolution, and the commitment to proactive communication when problems arise. Include a satisfaction guarantee or scope-credit mechanism if appropriate." + sections_to_add: + - section_name: "Scope Management Terms" + placement: "end" + description: "Clear terms for how scope changes are handled — the primary source of agency-client friction." + fields: + - "Change-order process and approval requirements" + - "Rate for out-of-scope work" + - "Impact of scope changes on timeline" + - "Monthly scope utilization report" + sections_to_remove: [] + benchmark_references: ["scope-creep-rate", "effective-billable-rate"] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency project status updates should provide complete transparency on progress, budget consumption, and any risks — building the trust that sustains long-term relationships." + field_changes: + - field: "Progress summary" + sector_label: "Delivery Progress and Budget Status" + sector_guidance: "Present: (1) Deliverables completed since last update. (2) Work in progress and expected completion. (3) Budget consumption (hours or dollars used vs. total). (4) Timeline status (on track, ahead, or behind — with explanation if behind). (5) Client action items (decisions needed, feedback required, access to be provided). Transparency on budget consumption builds trust and prevents end-of-project surprises." + sections_to_add: + - section_name: "Risk and Change Log" + placement: "after:Delivery Progress and Budget Status" + description: "Proactive identification of risks and tracking of scope changes." + fields: + - "Risks identified (what could delay or impact the project)" + - "Scope changes since last update (requested, approved, pending)" + - "Budget impact of changes (if any)" + sections_to_remove: [] + benchmark_references: ["scope-creep-rate"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency analysis reports are the deliverables that demonstrate the firm's intellectual value. The report structure should showcase the agency's thinking quality and provide actionable recommendations, not just data presentation." + field_changes: + - field: "Findings" + sector_label: "Key Findings and Implications" + sector_guidance: "Structure findings as insight-implication pairs: each finding should be followed by 'this means...' (the business implication for the client). Do not present data without interpretation. The agency's value is the interpretation, not the data gathering." + sections_to_add: + - section_name: "Prioritized Recommendations" + placement: "end" + description: "Actionable recommendations ranked by impact and feasibility." + fields: + - "Recommendations ranked by expected business impact" + - "Feasibility assessment for each recommendation (effort, timeline, dependencies)" + - "Recommended next steps (what the agency proposes to do next)" + - "Quick wins (immediate actions with disproportionate impact)" + sections_to_remove: [] + benchmark_references: [] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency case studies are the primary sales tool — they demonstrate capability through evidence rather than claims. Every case study should be structured as a story with quantified outcomes that enable prospects to envision similar results for their own business." + field_changes: + - field: "Results" + sector_label: "Quantified Outcomes" + sector_guidance: "Every agency case study must include at least 2-3 quantified outcomes: revenue impact, cost reduction, performance improvement, time saved, or efficiency gained. Include the timeframe over which results were achieved. Abstract outcomes ('improved brand perception') are insufficient unless supported by measurable proxies (NPS increase, survey data, engagement metrics)." + - field: "Challenge" + sector_label: "Client Challenge and Context" + sector_guidance: "Describe the business challenge (not the agency brief). Help the reader see themselves: what was the client struggling with, what had they tried before, what was at stake? Include enough context that a similar prospect would recognize their own situation." + sections_to_add: + - section_name: "Approach and Methodology" + placement: "after:Client Challenge and Context" + description: "How the agency approached the problem — demonstrating thinking quality." + fields: + - "Diagnostic process (how the agency understood the real problem)" + - "Strategy development (what approach was chosen and why)" + - "Execution highlights (what was distinctive about the delivery)" + - "Timeline and team composition" + - section_name: "Client Testimonial" + placement: "after:Quantified Outcomes" + description: "Direct client voice validates the agency's claims." + fields: + - "Client quote on the experience and results" + - "Client name and title (with permission)" + sections_to_remove: [] + benchmark_references: ["nps-client", "win-rate"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Agency partnership memos should address the mutual benefit structure, referral economics, and quality assurance terms that govern inter-firm collaboration." + field_changes: + - field: "Partnership structure" + sector_label: "Agency Partnership Structure" + sector_guidance: "Define: (1) Partnership type — referral (sending clients), delivery (subcontracting), or strategic (co-pitching). (2) Economic terms — referral fees, subcontracting rates, revenue sharing on joint engagements. (3) Quality standards — how each firm ensures the other's work meets standards when client-facing. (4) Client ownership — who owns the client relationship in different scenarios." + sections_to_add: + - section_name: "Referral and Collaboration Terms" + placement: "end" + description: "Operational terms for how the partnership works in practice." + fields: + - "Referral process and tracking methodology" + - "Referral fee structure and payment timing" + - "Joint pitch process (who leads, how costs are shared)" + - "Non-compete/non-solicit terms between the partner firms" + - "Review cadence (how often the partnership is evaluated)" + sections_to_remove: [] + benchmark_references: ["win-rate", "cost-per-lead"] diff --git a/plugins/foreman/content/industry-packs/ai-ml/ai-ml-benchmarks.yaml b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-benchmarks.yaml new file mode 100644 index 0000000..47e95c0 --- /dev/null +++ b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-benchmarks.yaml @@ -0,0 +1,986 @@ +# AI-ML Industry Pack — Benchmarks +# +# 24 AI-ML-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing growth, model quality, +# and unit economics issues for companies whose core product IS an AI/ML system. +# +# This pack covers: AI-native SaaS, MLaaS, AI agents, computer vision products, +# NLP platforms, AI infrastructure, model marketplaces, and AI-powered vertical +# solutions. It does NOT cover companies merely using AI as a tool — that is the +# domain of ai-leadership skills. +# +# Primary data sources: +# - a16z AI Reports / Emerging Tech (2023, 2024, 2025) +# - Scale AI Research / AI Infrastructure Index (2024) +# - MLCommons Benchmarks / MLPerf (2024) +# - Hugging Face State of AI (2024, 2025) +# - OpenAI / Anthropic Pricing Studies and Public Disclosures (2024, 2025) +# - GPU Cloud Pricing Comparisons (Lambda, CoreWeave, RunPod, 2024-2025) +# - Bessemer Venture Partners / State of the Cloud (2024) +# - Menlo Ventures AI Survey (2024) +# - Latent Space / AI Engineer Surveys (2024, 2025) +# - Stanford HAI AI Index Report (2024, 2025) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded AI-ML companies at the relevant stage. + +pack_metadata: + sector: "ai-ml" + display_name: "AI-ML" + version: "1.0.0" + description: "Benchmark data for companies whose core product is an AI/ML system — spanning model performance, inference economics, data strategy, responsible AI, and AI-native growth metrics." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # MODEL PERFORMANCE METRICS + # ───────────────────────────────────────────── + + - name: "Model Accuracy / F1 Score" + id: "model-accuracy-f1" + category: "product" + definition: "The harmonic mean of precision and recall for the core model, measuring how well the AI product delivers correct outputs — the single most important product-quality metric for an AI-ML company." + formula: "F1 = 2 x (Precision x Recall) / (Precision + Recall); Precision = True Positives / (True Positives + False Positives); Recall = True Positives / (True Positives + False Negatives)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "F1 < 0.70" + signal: "Model output is unreliable enough to erode user trust. Customers will bypass the AI and revert to manual processes, destroying the value proposition." + below_average: + value: "F1 0.70-0.80" + signal: "Functional but error-prone. Acceptable for low-stakes suggestions but insufficient for decision-critical workflows." + average: + value: "F1 0.80-0.90" + signal: "Competitive baseline for most production AI products. Usable with human-in-the-loop validation for moderate-stakes decisions." + good: + value: "F1 0.90-0.95" + signal: "High reliability. Enables autonomous operation for many use cases. This is the range where users develop trust and reduce manual oversight." + excellent: + value: "F1 > 0.95" + signal: "Best-in-class. Achievable in narrow, well-defined domains (medical imaging, document classification). Near-human or superhuman performance creates deep moat." + stage_notes: + seed: "F1 is the primary PMF signal. An F1 above 0.80 on the core task with early users is strong validation. Below 0.75 and the product is not yet viable." + series_a: "Investors expect evidence of model improvement trajectory — not just current F1, but the slope of improvement as data accumulates." + series_b_plus: "F1 should be benchmarked against public models and competitors. The gap between your model and the best open-source alternative is your moat." + data_sources: + - source: "MLCommons / MLPerf Benchmarks" + year: "2024" + - source: "Stanford HAI AI Index Report" + year: "2025" + related_metrics: ["hallucination-rate", "model-drift-rate", "customer-accuracy-satisfaction"] + related_skills: ["balanced-scorecard", "net-promoter-score"] + caveats: "F1 is domain-dependent. A 0.85 F1 in medical diagnosis may be insufficient while 0.85 in content recommendation is excellent. Always contextualize by domain tolerance for error." + + - name: "Hallucination Rate" + id: "hallucination-rate" + category: "product" + definition: "The percentage of model outputs that contain factually incorrect, fabricated, or unsupported information — the defining liability metric for generative AI products." + formula: "Hallucinated outputs / Total outputs evaluated x 100 (measured via human evaluation, automated fact-checking, or user-reported errors)" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 15%" + signal: "Unacceptable for any production use case. Users cannot trust output without complete manual verification, negating the value of AI." + below_average: + value: "8-15%" + signal: "Usable only with mandatory human review. The product is an assistant, not an autonomous agent. Support costs are high." + average: + value: "3-8%" + signal: "Competitive for general-purpose applications with human-in-the-loop. Requires clear disclaimers and user education." + good: + value: "1-3%" + signal: "Low enough for semi-autonomous operation in most commercial applications. Users develop workflow trust." + excellent: + value: "< 1%" + signal: "Production-grade reliability. Enables autonomous operation and unlocks high-value, regulated, and liability-sensitive use cases." + stage_notes: + seed: "Hallucination rate defines whether the product is viable. A generative AI product with >10% hallucination rate will not retain enterprise customers." + series_a: "Investors scrutinize hallucination reduction trajectory. Demonstrate systematic measurement and improvement methodology." + series_b_plus: "Public disclosure of hallucination rates becomes expected. Competitive benchmarking against alternatives (including open-source) is standard." + data_sources: + - source: "Stanford HAI AI Index Report" + year: "2025" + - source: "Anthropic / OpenAI Public Evaluations" + year: "2025" + related_metrics: ["model-accuracy-f1", "responsible-ai-score", "customer-accuracy-satisfaction"] + related_skills: ["systems-thinking", "trust-equation"] + caveats: "Hallucination measurement is itself unreliable at scale. Human evaluation is the gold standard but expensive. Automated metrics undercount subtle hallucinations. Report methodology alongside the rate." + + - name: "Model Drift Rate" + id: "model-drift-rate" + category: "product" + definition: "The rate at which model performance degrades over time as real-world data distribution shifts away from training data — measuring the durability of model quality." + formula: "Performance degradation per time period = (F1_at_deployment - F1_current) / F1_at_deployment x 100, measured monthly or quarterly" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 5% degradation per quarter" + signal: "Model requires frequent retraining to maintain quality. Indicates training data does not represent production distribution or the domain is highly dynamic." + below_average: + value: "3-5% per quarter" + signal: "Meaningful drift requiring quarterly retraining cycles. Sustainable but adds ongoing cost and engineering overhead." + average: + value: "1-3% per quarter" + signal: "Manageable drift. Semi-annual retraining with continuous monitoring is sufficient." + good: + value: "0.5-1% per quarter" + signal: "Stable model with slow drift. Annual retraining or continuous fine-tuning maintains quality." + excellent: + value: "< 0.5% per quarter" + signal: "Highly stable. The domain is well-characterized and the training data is representative. Retraining is improvement-driven, not maintenance-driven." + stage_notes: + seed: "Drift is less meaningful with small data. Focus on establishing drift monitoring infrastructure early — it becomes critical at scale." + series_a: "Demonstrate that you have drift detection in place and a retraining pipeline. Investors ask: 'How do you know when the model degrades?'" + series_b_plus: "Drift management is operational excellence. Automated retraining pipelines with A/B testing of new models against incumbents is expected." + data_sources: + - source: "MLCommons Benchmarks" + year: "2024" + - source: "Scale AI Research" + year: "2024" + related_metrics: ["model-accuracy-f1", "data-pipeline-reliability", "ab-test-win-rate"] + related_skills: ["systems-thinking", "balanced-scorecard"] + caveats: "Drift can be data drift (input distribution changes), concept drift (the relationship between inputs and correct outputs changes), or both. The distinction matters for the retraining strategy." + + - name: "A/B Test Win Rate" + id: "ab-test-win-rate" + category: "product" + definition: "The percentage of model experiments (new versions, fine-tuning runs, architecture changes) that produce statistically significant improvements over the current production model." + formula: "Winning experiments / Total experiments run x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "The research and iteration process is inefficient. Most experiments fail to improve on the baseline, indicating unclear improvement hypotheses or inadequate evaluation." + below_average: + value: "15-25%" + signal: "Low win rate but within range for exploratory research. Acceptable if the magnitude of wins is large." + average: + value: "25-35%" + signal: "Healthy experimentation cadence. Roughly one in three experiments improves the model — a sustainable improvement velocity." + good: + value: "35-50%" + signal: "Strong research productivity. Well-targeted experiments based on error analysis and user feedback." + excellent: + value: "> 50%" + signal: "Exceptional. Typically seen in early-stage optimization or domain-specific fine-tuning where low-hanging improvements are abundant." + stage_notes: + seed: "Win rate is often high early (easy improvements), then declines. Focus on establishing the experimentation infrastructure." + series_a: "Track win rate alongside improvement magnitude. A 20% win rate with large accuracy gains is better than 50% with marginal gains." + series_b_plus: "Win rate naturally declines as the model matures. Below 15% sustained may indicate the model architecture has reached its ceiling." + data_sources: + - source: "Scale AI Research" + year: "2024" + - source: "Latent Space AI Engineer Survey" + year: "2025" + related_metrics: ["model-accuracy-f1", "model-deployment-frequency", "training-cost-per-iteration"] + related_skills: ["growth-mindset", "systems-thinking"] + caveats: "Win rate depends heavily on the statistical significance threshold and the minimum detectable effect size. Report these alongside the rate." + + # ───────────────────────────────────────────── + # INFERENCE AND INFRASTRUCTURE METRICS + # ───────────────────────────────────────────── + + - name: "Inference Latency (p50/p95/p99)" + id: "inference-latency" + category: "product" + definition: "The time from receiving an API request to returning a model prediction, measured at the 50th, 95th, and 99th percentiles — the primary user experience metric for AI products." + formula: "Measured at each percentile across all inference requests in a given period. p50 = median request latency; p95 = latency at 95th percentile; p99 = latency at 99th percentile." + unit: "milliseconds" + direction: "lower-is-better" + benchmarks: + poor: + value: "p50 > 2000ms, p99 > 10s" + signal: "Latency destroys user experience and limits integration into real-time workflows. Customers will avoid features that feel slow." + below_average: + value: "p50 1000-2000ms, p99 5-10s" + signal: "Acceptable for batch processing and asynchronous workflows. Insufficient for interactive or real-time applications." + average: + value: "p50 200-1000ms, p99 2-5s" + signal: "Workable for most interactive applications. Users perceive the AI as responsive but not instantaneous." + good: + value: "p50 50-200ms, p99 500ms-2s" + signal: "Fast enough for real-time integration. Enables embedding AI into latency-sensitive workflows (search, recommendations, chat)." + excellent: + value: "p50 < 50ms, p99 < 500ms" + signal: "Sub-perceptual latency. The AI feels instant. Enables real-time applications including gaming, trading, and autonomous systems." + stage_notes: + seed: "Latency is secondary to accuracy at seed stage. Ship the model that works, optimize latency later. But measure it from day one." + series_a: "Investors ask about latency in the context of scaling: 'What happens to p99 when you have 10x more users?'" + series_b_plus: "Latency SLAs become contractual. Enterprise customers demand p99 guarantees with financial penalties for violations." + data_sources: + - source: "a16z AI Infrastructure Report" + year: "2024" + - source: "MLCommons MLPerf Inference" + year: "2024" + related_metrics: ["inference-cost-per-request", "gpu-utilization-rate", "api-call-volume"] + related_skills: ["balanced-scorecard", "systems-thinking"] + caveats: "Latency benchmarks differ dramatically by model type. LLM inference (generative, sequential token production) is inherently slower than classification or embedding models. Compare within model class, not across." + + - name: "Inference Cost per Request" + id: "inference-cost-per-request" + category: "unit-economics" + definition: "The fully loaded cost to serve one inference request, including compute, infrastructure, model hosting, and allocated overhead — the AI-ML equivalent of COGS per unit." + formula: "Total inference infrastructure cost in period / Total inference requests served in period" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $0.10 per request (non-LLM) or > $0.05 per 1K tokens (LLM)" + signal: "Inference cost consumes gross margin. The business cannot scale profitably without fundamental cost reduction." + below_average: + value: "$0.01-$0.10 per request or $0.01-$0.05 per 1K tokens" + signal: "Viable at low volume but cost pressure intensifies with scale. Margin compression limits growth investment." + average: + value: "$0.001-$0.01 per request or $0.002-$0.01 per 1K tokens" + signal: "Manageable cost structure. Gross margins of 50-70% achievable depending on pricing." + good: + value: "$0.0001-$0.001 per request or $0.0005-$0.002 per 1K tokens" + signal: "Efficient inference. SaaS-like gross margins (70%+) achievable. Pricing flexibility enables both premium and volume strategies." + excellent: + value: "< $0.0001 per request or < $0.0005 per 1K tokens" + signal: "Highly optimized. Achieved through model distillation, quantization, custom hardware, or edge deployment. Enables aggressive pricing." + stage_notes: + seed: "Inference cost is often subsidized at seed. Use managed services (cloud ML APIs) and accept higher per-unit costs. Optimize later." + series_a: "Investors examine the cost trajectory: is inference cost declining with scale? A flat or rising cost curve is a red flag." + series_b_plus: "Inference cost optimization becomes a dedicated engineering function. Custom inference infrastructure (specialized hardware, optimized serving) is expected." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "GPU Cloud Pricing Comparisons (Lambda, CoreWeave, RunPod)" + year: "2025" + - source: "OpenAI / Anthropic Pricing Disclosures" + year: "2025" + related_metrics: ["gross-margin-compute-adjusted", "cost-per-prediction", "gpu-utilization-rate", "revenue-per-api-call"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "Cost per request varies enormously by model size and type. A 7B parameter model costs 100x less per inference than a 175B+ model. Always specify the model class when benchmarking." + + - name: "GPU Utilization Rate" + id: "gpu-utilization-rate" + category: "efficiency" + definition: "The percentage of provisioned GPU compute capacity that is actively used for inference or training, measuring infrastructure efficiency." + formula: "Actual GPU compute hours used / Total GPU compute hours provisioned x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "< 30%" + signal: "Severely over-provisioned. Paying for idle GPUs is the AI-ML equivalent of burning cash. Indicates poor capacity planning or traffic variability without autoscaling." + below_average: + value: "30-50%" + signal: "Under-utilized but not unusual for companies handling variable inference loads without sophisticated autoscaling." + average: + value: "50-70%" + signal: "Reasonable utilization. Typical for companies with moderate traffic variability and basic autoscaling." + good: + value: "70-85%" + signal: "Well-optimized. Achieved through effective autoscaling, request batching, and workload scheduling." + excellent: + value: "85-95%" + signal: "Near-optimal utilization. Achieved through advanced scheduling, multi-model serving, and predictive autoscaling. Above 95% risks latency spikes." + stage_notes: + seed: "Utilization is low by necessity — small traffic on provisioned infrastructure. Use serverless inference (pay-per-request) to avoid idle GPU cost." + series_a: "Demonstrate awareness of utilization economics. Investors ask: 'What is your cost per GPU hour and what percentage is utilized?'" + series_b_plus: "Dedicated MLOps team managing utilization, autoscaling, multi-model serving, and spot instance strategies is expected." + data_sources: + - source: "a16z AI Infrastructure Report" + year: "2024" + - source: "GPU Cloud Pricing Comparisons" + year: "2025" + related_metrics: ["inference-cost-per-request", "gross-margin-compute-adjusted"] + related_skills: ["balanced-scorecard", "eisenhower-matrix"] + caveats: "Utilization above 95% typically causes latency spikes as queuing increases. The optimal range is 70-90%, not 100%. Report alongside latency percentiles." + + - name: "Data Pipeline Reliability" + id: "data-pipeline-reliability" + category: "efficiency" + definition: "The uptime and data freshness of the data ingestion, processing, and feature engineering pipeline that feeds the production model." + formula: "Hours of pipeline operating within SLA / Total hours in period x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 95%" + signal: "Pipeline failures degrade model quality (stale features), delay retraining, and create data gaps. Customers experience degraded predictions." + below_average: + value: "95-98%" + signal: "Occasional failures requiring manual intervention. Acceptable at early stage but creates operational burden at scale." + average: + value: "98-99.5%" + signal: "Reliable pipeline with rare failures. Automated alerting and recovery handles most issues." + good: + value: "99.5-99.9%" + signal: "Production-grade reliability. Redundancy, automated recovery, and comprehensive monitoring in place." + excellent: + value: "> 99.9%" + signal: "Enterprise-grade. Multi-region redundancy, automated failover, and zero-downtime deployment of pipeline changes." + stage_notes: + seed: "Pipeline reliability is often manual — founders run data processing scripts. Acceptable, but document the process for automation." + series_a: "Automated pipeline with monitoring is expected. Manual data processing is a red flag for investors assessing scalability." + series_b_plus: "Pipeline reliability becomes an SLA commitment to enterprise customers. Downtime directly impacts customer trust and retention." + data_sources: + - source: "Scale AI Research" + year: "2024" + - source: "Latent Space AI Engineer Survey" + year: "2025" + related_metrics: ["model-drift-rate", "model-accuracy-f1"] + related_skills: ["systems-thinking", "balanced-scorecard"] + caveats: "Reliability must be measured alongside data freshness. A pipeline that is 99.9% 'up' but serves data that is 48 hours stale is not reliable for real-time applications." + + # ───────────────────────────────────────────── + # UNIT ECONOMICS METRICS + # ───────────────────────────────────────────── + + - name: "Training Cost per Model Iteration" + id: "training-cost-per-iteration" + category: "unit-economics" + definition: "The total compute, data, and engineering cost to train or fine-tune one iteration of the production model — the AI-ML equivalent of R&D cost per product cycle." + formula: "GPU compute cost + data acquisition/labeling cost + engineering time cost for one training run" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $500K per training run (foundation model) or > $50K per fine-tune (application layer)" + signal: "Training costs constrain iteration speed. The company cannot afford to experiment frequently, slowing model improvement." + below_average: + value: "$100K-$500K (foundation) or $10K-$50K (fine-tune)" + signal: "Significant cost per iteration. Monthly retraining is budget-constrained. Experiment selection must be highly disciplined." + average: + value: "$10K-$100K (foundation) or $1K-$10K (fine-tune)" + signal: "Manageable training costs enabling monthly iteration cycles. Standard for mid-scale model training." + good: + value: "$1K-$10K (foundation) or $100-$1K (fine-tune)" + signal: "Efficient training enabling weekly or bi-weekly iterations. Rapid experimentation cycle accelerates model improvement." + excellent: + value: "< $1K (foundation) or < $100 (fine-tune)" + signal: "Highly efficient. Achieved through transfer learning, efficient architectures, or specialized hardware. Daily experimentation feasible." + stage_notes: + seed: "Training costs should be kept low through transfer learning, fine-tuning pretrained models, and managed ML services. Building from scratch is rarely justified." + series_a: "Training cost trajectory matters. Show that cost per quality improvement is declining as the team and infrastructure mature." + series_b_plus: "Training infrastructure becomes a strategic asset. Custom training pipelines, data flywheel effects, and hardware optimization are differentiators." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Stanford HAI AI Index Report" + year: "2025" + related_metrics: ["ab-test-win-rate", "model-accuracy-f1", "data-acquisition-cost"] + related_skills: ["scenario-planning", "business-model-canvas"] + caveats: "Training cost is rapidly declining due to hardware improvements and efficiency techniques (LoRA, QLoRA, distillation). Benchmarks from 12 months ago are already outdated. Use current pricing." + + - name: "Data Acquisition Cost" + id: "data-acquisition-cost" + category: "unit-economics" + definition: "The cost to acquire, label, clean, and prepare one unit of training data — a key driver of model quality and a potential competitive moat." + formula: "Total data acquisition spend (purchasing, scraping, user-generated, labeling, QA) / Total data units acquired" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $10 per labeled sample (supervised) or > $0.10 per raw data point" + signal: "Data acquisition is a bottleneck. High costs limit dataset size, which limits model quality and competitive position." + below_average: + value: "$5-$10 per labeled sample or $0.05-$0.10 per raw data point" + signal: "Expensive but viable for high-value domains (medical, legal, financial). Unit economics require high per-prediction revenue." + average: + value: "$1-$5 per labeled sample or $0.01-$0.05 per raw data point" + signal: "Manageable cost for most AI products. Standard for domain-specific labeling with human annotators." + good: + value: "$0.10-$1 per labeled sample or $0.001-$0.01 per raw data point" + signal: "Efficient acquisition through semi-automated labeling, active learning, or user-generated data. Enables larger datasets." + excellent: + value: "< $0.10 per labeled sample or < $0.001 per raw data point" + signal: "Near-zero marginal data cost. Achieved through product-generated data (users create training data through usage), synthetic data, or self-supervised learning." + stage_notes: + seed: "Data acquisition cost defines feasibility. If you cannot affordably acquire enough data to build a competitive model, the business model does not work." + series_a: "Investors want to see a data flywheel: product usage generates data that improves the model, which attracts more users, which generates more data." + series_b_plus: "The data moat should be widening. Cost per marginal data point should be declining while the dataset's competitive value increases." + data_sources: + - source: "Scale AI Research" + year: "2024" + - source: "Hugging Face State of AI" + year: "2025" + related_metrics: ["annotation-cost-per-data-point", "training-cost-per-iteration", "model-accuracy-f1"] + related_skills: ["business-model-canvas", "porters-five-forces"] + caveats: "Data cost must include quality assurance. Cheap data that is poorly labeled degrades model performance. The relevant metric is cost per high-quality data point." + + - name: "Annotation Cost per Data Point" + id: "annotation-cost-per-data-point" + category: "unit-economics" + definition: "The cost to label one data point with ground-truth annotations for supervised learning — the labor-intensive component of the data acquisition pipeline." + formula: "Total annotation spend (human labelers, QA reviewers, tooling) / Total data points annotated" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $5 per annotation" + signal: "Expert annotation in specialized domains (radiology, legal document review). Viable only for high-revenue-per-prediction products." + below_average: + value: "$1-$5 per annotation" + signal: "Skilled annotator domains. Requires strong unit economics per prediction to justify the data cost." + average: + value: "$0.10-$1 per annotation" + signal: "Standard for moderate-complexity labeling tasks using trained annotators or crowd-sourcing platforms." + good: + value: "$0.01-$0.10 per annotation" + signal: "Efficient annotation through pre-labeling with model-assisted tools, active learning, or simplified task design." + excellent: + value: "< $0.01 per annotation" + signal: "Near-zero cost through self-supervised learning, user-generated labels (implicit feedback), or synthetic data generation." + stage_notes: + seed: "Founders often annotate data themselves. This is acceptable and provides valuable domain understanding, but does not scale." + series_a: "Demonstrate an annotation strategy that scales: model-assisted labeling, crowd-sourcing pipelines, or product-generated labels." + series_b_plus: "Annotation infrastructure should be largely automated with human review for edge cases. The human-in-the-loop ratio should be declining." + data_sources: + - source: "Scale AI Pricing Research" + year: "2024" + - source: "Hugging Face State of AI" + year: "2025" + related_metrics: ["data-acquisition-cost", "model-accuracy-f1"] + related_skills: ["systems-thinking", "eisenhower-matrix"] + caveats: "Cost per annotation and annotation quality are inversely correlated with speed. Rushing annotation degrades quality, which degrades the model." + + - name: "Cost per Prediction" + id: "cost-per-prediction" + category: "unit-economics" + definition: "The fully loaded cost to deliver one prediction to a customer, including inference compute, data processing, infrastructure overhead, and allocated support — the AI-ML gross margin denominator." + formula: "Total delivery cost (inference + data processing + infrastructure + support allocation) / Total predictions delivered" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "Cost per prediction > 50% of revenue per prediction" + signal: "Sub-50% gross margin on the core product. The business has a compute problem, not a revenue problem. Scaling worsens unit economics." + below_average: + value: "Cost 30-50% of revenue per prediction" + signal: "Viable but constrained. Margins leave limited room for R&D, sales, and overhead. Pricing increases or cost reduction required." + average: + value: "Cost 15-30% of revenue per prediction" + signal: "Healthy unit economics. 70-85% gross margin on inference delivery. Standard for optimized AI products." + good: + value: "Cost 5-15% of revenue per prediction" + signal: "Strong margins enabling aggressive growth investment. Achieved through model optimization and pricing power." + excellent: + value: "Cost < 5% of revenue per prediction" + signal: "Exceptional margins. Indicates strong pricing power, efficient models, or both. Rare in compute-intensive applications." + stage_notes: + seed: "Cost per prediction is often high and poorly measured. Establish tracking early even if the numbers are unfavorable." + series_a: "Show the trajectory: cost per prediction declining as you optimize serving infrastructure and grow volume (amortizing fixed costs)." + series_b_plus: "Cost per prediction should be benchmarked against the revenue per prediction for each customer segment. Segment-level profitability analysis is expected." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Bessemer Venture Partners" + year: "2024" + related_metrics: ["inference-cost-per-request", "revenue-per-api-call", "gross-margin-compute-adjusted"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "Cost per prediction can vary 100x within the same product depending on query complexity, context length (for LLMs), or resolution (for vision). Report segmented by use case." + + - name: "Revenue per API Call" + id: "revenue-per-api-call" + category: "unit-economics" + definition: "The average revenue generated per API inference call, measuring the monetization efficiency of each model invocation." + formula: "Total API revenue in period / Total API calls in period" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $0.0001 per call" + signal: "Extremely low monetization. Viable only at massive scale (billions of calls) or as a loss leader for higher-value services." + below_average: + value: "$0.0001-$0.001 per call" + signal: "Low revenue per call requiring high volume for meaningful revenue. Common in commodity inference (embeddings, classification)." + average: + value: "$0.001-$0.01 per call" + signal: "Standard range for mid-complexity AI APIs (NLP, vision, recommendation). Viable unit economics with good volume." + good: + value: "$0.01-$0.10 per call" + signal: "Strong per-call monetization. Indicates high-value predictions (financial analysis, medical, legal) or complex multi-step inference." + excellent: + value: "> $0.10 per call" + signal: "Premium pricing for high-stakes predictions. Achievable in regulated industries, decision-critical applications, or outcome-based pricing." + stage_notes: + seed: "Revenue per call is often zero (free tier) or artificially low (introductory pricing). Focus on establishing what customers will pay once value is proven." + series_a: "Demonstrate willingness-to-pay through pricing experiments. Revenue per call x volume = revenue opportunity is a core investor calculation." + series_b_plus: "Revenue per call should be growing through pricing optimization, premium tiers, and higher-value use cases. Declining revenue per call with stable volume is a pricing problem." + data_sources: + - source: "OpenAI / Anthropic Pricing Studies" + year: "2025" + - source: "a16z AI Reports" + year: "2025" + related_metrics: ["inference-cost-per-request", "cost-per-prediction", "gross-margin-compute-adjusted"] + related_skills: ["four-ps-marketing", "business-model-canvas"] + caveats: "Revenue per call is meaningful only for usage-based pricing. For seat-based or flat-rate AI products, substitute with revenue per active user per unit time." + + - name: "Gross Margin (Compute-Adjusted)" + id: "gross-margin-compute-adjusted" + category: "unit-economics" + definition: "Revenue minus the fully loaded cost of delivering AI-powered services — including compute (inference and training), data processing, third-party APIs, infrastructure, and customer support." + formula: "(Revenue - COGS) / Revenue x 100; where COGS = inference compute + training amortization + data pipeline costs + third-party API costs + cloud infrastructure + customer support" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "The business operates closer to services economics than software economics. Compute cost dominates, limiting scalability." + below_average: + value: "40-55%" + signal: "Below traditional SaaS benchmarks. Acceptable for compute-intensive products if the margin trajectory is improving with scale and optimization." + average: + value: "55-65%" + signal: "Typical for AI-native companies. The a16z 'AI margin gap' — AI companies run 10-20 points below traditional SaaS margins due to compute COGS." + good: + value: "65-75%" + signal: "Strong for an AI product. Achieved through model optimization, efficient infrastructure, and pricing power." + excellent: + value: "> 75%" + signal: "SaaS-tier margins in an AI business. Indicates lightweight models, edge deployment, or premium pricing that exceeds compute cost growth." + stage_notes: + seed: "Gross margin is often negative at seed (subsidized compute, free tiers). Acceptable, but model the path to 60%+ margins." + series_a: "The a16z observation that AI companies have structurally lower gross margins is well-known. Show investors your specific margin improvement plan." + series_b_plus: "Gross margin expansion is a key narrative. Public AI companies are scrutinized on whether they can achieve SaaS-like margins or remain structurally lower-margin." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Bessemer State of the Cloud" + year: "2024" + related_metrics: ["inference-cost-per-request", "cost-per-prediction", "revenue-per-api-call"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "COGS classification in AI companies is contentious. Some classify training cost as R&D (opex), others as COGS. Be consistent and transparent about classification methodology." + + # ───────────────────────────────────────────── + # GROWTH AND ENGAGEMENT METRICS + # ───────────────────────────────────────────── + + - name: "API Call Volume" + id: "api-call-volume" + category: "growth" + definition: "The total number of inference API calls processed in a given period, measuring product adoption and usage intensity for API-delivered AI products." + formula: "Count of all API inference calls in period (daily, weekly, monthly)" + unit: "count" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10K calls/day at 6 months post-launch" + signal: "Insufficient adoption. Either the product has not found users or integration friction prevents usage." + below_average: + value: "10K-100K calls/day" + signal: "Early traction. Sufficient for initial validation but not yet indicating product-market fit through usage." + average: + value: "100K-1M calls/day" + signal: "Meaningful adoption. Enough volume to generate revenue, optimize models from usage data, and demonstrate scaling potential." + good: + value: "1M-100M calls/day" + signal: "Strong adoption. The product is embedded in customer workflows. Volume supports a data flywheel for model improvement." + excellent: + value: "> 100M calls/day" + signal: "Scale-stage volume. Infrastructure, cost optimization, and reliability become primary engineering priorities." + stage_notes: + seed: "Volume is less important than growth rate. 1K calls/day growing 20% WoW is a stronger signal than 50K calls/day growing 2% WoW." + series_a: "Demonstrate usage growth alongside customer growth. Volume per customer increasing indicates deepening integration." + series_b_plus: "Volume is revenue. Usage-based pricing means call volume directly drives top-line growth." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Latent Space AI Engineer Survey" + year: "2025" + related_metrics: ["monthly-active-api-users", "token-usage", "revenue-per-api-call"] + related_skills: ["balanced-scorecard", "growth-share-matrix"] + caveats: "Raw call volume can be inflated by a single heavy user or by inefficient API usage patterns. Segment volume by customer and monitor for healthy distribution." + + - name: "Monthly Active API Users" + id: "monthly-active-api-users" + category: "growth" + definition: "The number of unique accounts or developers making at least one API call per month, measuring the breadth of product adoption." + formula: "Count of unique API keys / accounts with >= 1 inference call in a 30-day period" + unit: "count" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 50 active accounts at 6 months post-launch" + signal: "Adoption has not taken hold. Either the market is wrong, the product is too hard to integrate, or the value is unclear." + below_average: + value: "50-200 active accounts" + signal: "Early adopter base. Sufficient for qualitative feedback but not yet demonstrating product-market fit." + average: + value: "200-1,000 active accounts" + signal: "Healthy early traction. Enough users to measure retention patterns and identify high-value segments." + good: + value: "1,000-10,000 active accounts" + signal: "Strong adoption across multiple segments. The product has proven value beyond early adopters." + excellent: + value: "> 10,000 active accounts" + signal: "Platform-scale adoption. The product is a default choice in its category." + stage_notes: + seed: "10-50 active users who provide feedback are more valuable than 500 passive users. Focus on depth of engagement." + series_a: "Growth rate of active accounts matters more than absolute number. 100 accounts growing 15% MoM is strong." + series_b_plus: "Active accounts should be segmented by revenue tier. Report MAU by segment and track activation and retention by cohort." + data_sources: + - source: "Menlo Ventures AI Survey" + year: "2024" + - source: "a16z AI Reports" + year: "2025" + related_metrics: ["api-call-volume", "customer-retention-ai", "expansion-revenue-usage"] + related_skills: ["net-promoter-score", "product-life-cycle"] + caveats: "MAU for API products differs from MAU for consumer products. A developer who integrates once and the integration runs automatically counts as active even without manual interaction." + + - name: "Token Usage (LLM Products)" + id: "token-usage" + category: "growth" + definition: "Total tokens (input + output) processed per period for LLM-based products — the native volume metric for generative AI businesses." + formula: "Sum of (input tokens + output tokens) across all API calls in period" + unit: "count" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1M tokens/day" + signal: "Minimal usage. Either few users or shallow integration (short prompts, limited output)." + below_average: + value: "1M-100M tokens/day" + signal: "Early traction for an LLM product. Sufficient to generate initial revenue if usage-priced." + average: + value: "100M-10B tokens/day" + signal: "Meaningful scale. Revenue potential is substantial at standard token pricing." + good: + value: "10B-1T tokens/day" + signal: "High-scale usage. Infrastructure optimization and cost management become critical." + excellent: + value: "> 1T tokens/day" + signal: "Platform-scale. Only achieved by the largest AI providers or widely adopted horizontal products." + stage_notes: + seed: "Token volume is meaningful only for LLM products. For non-generative AI, use api-call-volume instead." + series_a: "Report tokens alongside revenue per token. Investors want to see revenue per 1K tokens and the cost per 1K tokens side by side." + series_b_plus: "Token usage should be segmented: input vs. output (different cost profiles), by model tier, and by customer segment." + data_sources: + - source: "OpenAI / Anthropic Pricing Studies" + year: "2025" + - source: "Latent Space AI Engineer Survey" + year: "2025" + related_metrics: ["api-call-volume", "inference-cost-per-request", "revenue-per-api-call"] + related_skills: ["balanced-scorecard", "growth-share-matrix"] + caveats: "Token counts are model-specific (tokenizer determines how text maps to tokens). Cross-model comparisons are imprecise. Report the tokenizer or model family." + + # ───────────────────────────────────────────── + # RETENTION AND EXPANSION METRICS + # ───────────────────────────────────────────── + + - name: "Customer Retention (AI-Specific)" + id: "customer-retention-ai" + category: "retention" + definition: "The percentage of customers retained over a period, accounting for the unique AI retention dynamics: model switching cost, data lock-in, and accuracy-driven loyalty." + formula: "Customers at end of period who were customers at start / Customers at start of period x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 80% annual retention" + signal: "High churn despite model switching costs. Indicates model quality is insufficient or competitors have a materially better alternative." + below_average: + value: "80-88% annual retention" + signal: "Moderate retention. The model provides value but is not indispensable. Customers test alternatives regularly." + average: + value: "88-93% annual retention" + signal: "Good retention leveraging both product value and switching friction (data formats, integration depth, model customization)." + good: + value: "93-97% annual retention" + signal: "Strong retention. Customers are deeply integrated and the model's accuracy on their specific data creates switching risk they are unwilling to take." + excellent: + value: "> 97% annual retention" + signal: "Exceptional lock-in. The model is embedded in critical workflows and customized to the customer's data. Switching would require re-training and re-validation." + stage_notes: + seed: "Retention data is sparse. Focus on qualitative signals: are customers increasing usage, requesting features, or building workflows around the model?" + series_a: "AI-specific retention advantage should be articulable: 'Customers retain because our model improves with their data, creating a personalized asset they cannot replicate elsewhere.'" + series_b_plus: "Segment retention by data depth — customers who have contributed more data or fine-tuned models should retain at materially higher rates." + data_sources: + - source: "Menlo Ventures AI Survey" + year: "2024" + - source: "Bessemer Venture Partners" + year: "2024" + related_metrics: ["expansion-revenue-usage", "customer-accuracy-satisfaction", "model-accuracy-f1"] + related_skills: ["net-promoter-score", "product-life-cycle"] + caveats: "AI retention dynamics differ from SaaS: models can be replicated or open-sourced, reducing switching cost. Data lock-in is the more durable moat than model quality alone." + + - name: "Expansion Revenue (Usage-Based Growth)" + id: "expansion-revenue-usage" + category: "retention" + definition: "Revenue growth from existing customers driven by increased API usage, higher model tiers, or additional use cases — the AI-ML expansion engine." + formula: "Additional MRR from existing customers in period / Starting MRR from those customers x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% of starting MRR per quarter" + signal: "Customers are not increasing usage. The model may be useful but not expanding into new workflows or use cases." + below_average: + value: "5-10% per quarter" + signal: "Modest expansion. Some customers increasing usage but not enough to drive compounding growth." + average: + value: "10-20% per quarter" + signal: "Healthy expansion typical of usage-based AI products. Customers finding additional value over time." + good: + value: "20-35% per quarter" + signal: "Strong expansion driven by deepening integration, new use cases, and increasing trust in model accuracy." + excellent: + value: "> 35% per quarter" + signal: "Exceptional. The product has strong network effects within the customer organization — one team adopts, others follow." + stage_notes: + seed: "Expansion is hard to measure with few customers. Track per-customer usage trajectories as a leading indicator." + series_a: "Usage-based expansion is the AI-ML equivalent of NRR. Show investors that customers naturally grow their usage over time." + series_b_plus: "Expansion should be decomposed: same-use-case volume growth vs. new-use-case adoption vs. tier upgrades." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Bessemer State of the Cloud" + year: "2024" + related_metrics: ["customer-retention-ai", "api-call-volume", "token-usage"] + related_skills: ["net-promoter-score", "business-model-canvas"] + caveats: "Usage-based expansion can be volatile. A single customer's batch job can spike quarterly expansion. Report expansion with and without the top 3 accounts." + + - name: "Customer-Reported Accuracy Satisfaction" + id: "customer-accuracy-satisfaction" + category: "retention" + definition: "The percentage of customers who rate the model's accuracy as 'meeting or exceeding expectations' in periodic surveys — the subjective complement to objective F1 scores." + formula: "Customers rating accuracy as 'meets expectations' or 'exceeds expectations' / Total surveyed customers x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 60%" + signal: "More than 40% of customers are dissatisfied with accuracy. The product is not meeting the promise. Churn is imminent." + below_average: + value: "60-70%" + signal: "A meaningful minority of customers find accuracy insufficient. Investigate whether the dissatisfaction is segment-specific or domain-specific." + average: + value: "70-80%" + signal: "Most customers find accuracy acceptable. Standard for general-purpose AI products with diverse use cases." + good: + value: "80-90%" + signal: "Strong satisfaction. The model meets expectations across most customer segments and use cases." + excellent: + value: "> 90%" + signal: "Exceptional satisfaction. The product over-delivers on accuracy expectations. Strong referral and expansion potential." + stage_notes: + seed: "Survey every customer. With a small base, individual conversations provide richer signal than aggregate scores." + series_a: "Segment satisfaction by customer type. Accuracy satisfaction may vary dramatically between use cases — this reveals where the model is strong and weak." + series_b_plus: "Track satisfaction alongside objective metrics. Declining satisfaction with stable F1 may indicate rising customer expectations or competitor improvement." + data_sources: + - source: "Menlo Ventures AI Survey" + year: "2024" + - source: "Scale AI Research" + year: "2024" + related_metrics: ["model-accuracy-f1", "customer-retention-ai", "hallucination-rate"] + related_skills: ["net-promoter-score", "trust-equation"] + caveats: "Satisfaction is relative to expectations, not absolute performance. Setting realistic expectations during onboarding directly impacts this metric." + + # ───────────────────────────────────────────── + # OPERATIONAL AND DEPLOYMENT METRICS + # ───────────────────────────────────────────── + + - name: "Time to Fine-Tune" + id: "time-to-fine-tune" + category: "efficiency" + definition: "The elapsed time from initiating a customer-specific or domain-specific fine-tuning job to deploying the fine-tuned model in production." + formula: "Timestamp of deployment - Timestamp of fine-tune job initiation" + unit: "hours" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 7 days" + signal: "Fine-tuning is a manual, multi-step process. Customer onboarding requiring fine-tuning takes weeks, extending time-to-value." + below_average: + value: "3-7 days" + signal: "Semi-automated but slow. Acceptable for enterprise onboarding but limits self-serve fine-tuning." + average: + value: "1-3 days (24-72 hours)" + signal: "Standard for mid-complexity fine-tuning with automated pipelines. Reasonable enterprise SLA." + good: + value: "4-24 hours" + signal: "Fast fine-tuning enabling rapid customization. Self-serve fine-tuning becomes viable." + excellent: + value: "< 4 hours" + signal: "Near-real-time customization. Enables self-serve fine-tuning, rapid iteration, and continuous adaptation." + stage_notes: + seed: "Fine-tuning is often manual. Document the process and time it — this becomes a product feature as you scale." + series_a: "If fine-tuning is part of the value proposition, show the automation roadmap. Manual fine-tuning is a services cost that investors want to see automated." + series_b_plus: "Self-serve fine-tuning with automated validation and deployment is a competitive advantage and scalability requirement." + data_sources: + - source: "Hugging Face Trends" + year: "2025" + - source: "Scale AI Research" + year: "2024" + related_metrics: ["training-cost-per-iteration", "model-deployment-frequency"] + related_skills: ["kaizen-bpr", "systems-thinking"] + caveats: "Time to fine-tune varies enormously by model size and dataset size. Report the typical use case (model size, dataset size) alongside the metric." + + - name: "Model Deployment Frequency" + id: "model-deployment-frequency" + category: "efficiency" + definition: "How often new model versions are deployed to production, measuring the iteration velocity of the AI development lifecycle." + formula: "Count of model deployments to production in period (weekly, monthly)" + unit: "count" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1 deployment per quarter" + signal: "Model development is stalled or the deployment pipeline is broken. The model is not improving." + below_average: + value: "1-2 per quarter" + signal: "Quarterly model releases. Acceptable for stable, mature models but too slow for rapidly evolving domains." + average: + value: "1-2 per month" + signal: "Monthly model updates. Standard cadence for most production AI products with automated evaluation." + good: + value: "Weekly deployments" + signal: "Rapid iteration. Continuous improvement cycle with automated A/B testing and canary deployments." + excellent: + value: "Multiple per week or continuous" + signal: "Continuous model deployment. Fully automated pipeline from training to evaluation to production. State-of-the-art MLOps maturity." + stage_notes: + seed: "Frequent manual deployments (weekly) are acceptable. The model should improve visibly from week to week." + series_a: "Demonstrate an automated deployment pipeline with rollback capability. Manual deployments are an MLOps red flag." + series_b_plus: "Canary deployments, automated A/B testing, and feature flag-based model rollouts are expected infrastructure." + data_sources: + - source: "Latent Space AI Engineer Survey" + year: "2025" + - source: "MLCommons" + year: "2024" + related_metrics: ["ab-test-win-rate", "model-accuracy-f1", "model-drift-rate"] + related_skills: ["kaizen-bpr", "systems-thinking"] + caveats: "Deployment frequency without quality gates is reckless. Report deployment frequency alongside the percentage of deployments that are rolled back." + + # ───────────────────────────────────────────── + # RESPONSIBLE AI METRICS + # ───────────────────────────────────────────── + + - name: "Responsible AI Score (Bias/Fairness)" + id: "responsible-ai-score" + category: "product" + definition: "A composite metric measuring the model's performance across fairness, bias, transparency, and safety dimensions — increasingly a regulatory and customer requirement." + formula: "Composite of: demographic parity ratio + equalized odds ratio + disparate impact ratio + toxicity rate + refusal accuracy, weighted by domain relevance" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "No measurement in place" + signal: "Absence of responsible AI measurement is itself the red flag. Regulatory exposure, reputational risk, and enterprise deal blockers." + below_average: + value: "Measurement exists but demographic parity ratio < 0.80 or toxicity rate > 5%" + signal: "Measurable bias in the model. Addressable through debiasing techniques but requires investment and attention." + average: + value: "Demographic parity 0.80-0.90, toxicity < 2%" + signal: "Acceptable for most commercial applications. Ongoing monitoring and improvement required." + good: + value: "Demographic parity 0.90-0.95, toxicity < 0.5%, explainability documentation complete" + signal: "Strong responsible AI posture. Meets emerging regulatory requirements (EU AI Act) and enterprise procurement criteria." + excellent: + value: "Demographic parity > 0.95, toxicity < 0.1%, third-party audit passed, model cards published" + signal: "Best-in-class. Competitive advantage in regulated industries and with ESG-conscious enterprise buyers." + stage_notes: + seed: "Establish measurement early even if scores are imperfect. The audit trail matters — showing that you measured from day one builds regulatory credibility." + series_a: "Investors increasingly ask about responsible AI. A documented framework (even if scores are moderate) is table stakes for institutional capital." + series_b_plus: "Third-party audits, published model cards, and compliance with EU AI Act / NIST AI RMF are expected. Enterprise customers add responsible AI to procurement criteria." + data_sources: + - source: "Stanford HAI AI Index Report" + year: "2025" + - source: "MLCommons Benchmarks" + year: "2024" + related_metrics: ["model-accuracy-f1", "hallucination-rate", "customer-accuracy-satisfaction"] + related_skills: ["trust-equation", "systems-thinking", "ai-stakeholder-balance"] + caveats: "Responsible AI is domain-specific. A hiring AI requires different fairness metrics than a content recommendation system. Adopt domain-appropriate metrics, not generic ones." + + # ───────────────────────────────────────────── + # FINANCIAL AND STRATEGIC METRICS + # ───────────────────────────────────────────── + + - name: "AI-Specific Net Revenue Retention" + id: "nrr-ai" + category: "retention" + definition: "Net revenue retention for AI products, measuring whether usage-based revenue from existing customers grows over time — the AI-ML equivalent of SaaS NRR." + formula: "(Starting MRR from cohort + Expansion from increased usage/tier upgrades - Contraction from decreased usage - Churned) / Starting MRR x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 90%" + signal: "Customers are reducing usage or leaving. The model's value is not sticky enough or cheaper alternatives exist." + below_average: + value: "90-100%" + signal: "Near break-even on existing customers. Usage is not growing, suggesting the product is used for a single, fixed workflow." + average: + value: "100-115%" + signal: "Modest expansion. Customers increase usage over time but not dramatically. Standard for utility-style AI products." + good: + value: "115-140%" + signal: "Strong expansion driven by customers finding new use cases, adding more data, or upgrading model tiers." + excellent: + value: "> 140%" + signal: "Exceptional expansion. The product creates a usage flywheel — better results drive more usage, which improves results further." + stage_notes: + seed: "NRR requires 6+ months of customer data. Focus on per-customer usage growth trends as a proxy." + series_a: "NRR above 110% is a strong signal for AI products. Above 120% with usage-based pricing indicates a true data flywheel." + series_b_plus: "NRR decomposition — same-use-case growth vs. new-use-case adoption — reveals the sustainability of expansion." + data_sources: + - source: "a16z AI Reports" + year: "2025" + - source: "Bessemer State of the Cloud" + year: "2024" + related_metrics: ["customer-retention-ai", "expansion-revenue-usage", "api-call-volume"] + related_skills: ["balanced-scorecard", "net-promoter-score"] + caveats: "Usage-based NRR is inherently more volatile than seat-based SaaS NRR. Report trailing 12-month NRR to smooth volatility." + + - name: "Data Moat Index" + id: "data-moat-index" + category: "strategic" + definition: "A qualitative-to-quantitative assessment of the company's data advantage: uniqueness, volume, refreshment rate, and the cost for a competitor to replicate it." + formula: "Composite score (1-10) across: data uniqueness (is it proprietary?), volume advantage (how much more data than competitors?), refresh rate (does new data arrive automatically?), replication cost (how expensive to rebuild?), and regulatory protection (is it legally protected?)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Score 1-3" + signal: "No meaningful data advantage. Training data is publicly available, competitors have equivalent datasets, and the model is replicable." + below_average: + value: "Score 3-5" + signal: "Slight data advantage from early mover accumulation but not defensible. Competitors can replicate with effort." + average: + value: "Score 5-7" + signal: "Meaningful advantage. Proprietary data from product usage, industry partnerships, or exclusive sources. Competitors face 6-12 month replication lag." + good: + value: "Score 7-9" + signal: "Strong moat. Data is generated by the product (flywheel), legally protected, and domain-specific. Replication cost is prohibitive." + excellent: + value: "Score 9-10" + signal: "Near-unassailable. Unique data generated by millions of users with network effects — each user makes the data more valuable for all users." + stage_notes: + seed: "Data moat is aspirational at seed. Articulate the flywheel: how will product usage generate defensible data over time?" + series_a: "Demonstrate early evidence of the data flywheel. Show that model quality has improved as customer data accumulated." + series_b_plus: "The data moat should be quantifiable: 'We have X million labeled examples across Y domains, growing at Z per month through product usage.'" + data_sources: + - source: "a16z Emerging Tech Report" + year: "2024" + - source: "Scale AI Research" + year: "2024" + related_metrics: ["data-acquisition-cost", "model-accuracy-f1", "customer-retention-ai"] + related_skills: ["porters-five-forces", "blue-ocean-strategy"] + caveats: "Data moats are eroding faster than expected as synthetic data, open datasets, and model capabilities improve. Reassess the moat quarterly." diff --git a/plugins/foreman/content/industry-packs/ai-ml/ai-ml-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-diagnostic-rules.yaml new file mode 100644 index 0000000..e2e2bd0 --- /dev/null +++ b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-diagnostic-rules.yaml @@ -0,0 +1,721 @@ +# AI-ML Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift for AI-ML companies — +# companies whose core product IS an AI/ML system. +# +# The diagnostic adaptations address the model-centric nature of these +# businesses: model quality as product quality, data as moat, inference +# cost as COGS, hallucination as liability, open-source as substitute +# threat, and compute as scaling bottleneck. +# +# AI-ML-specific diagnoses added throughout address: +# - Model quality plateau +# - Data moat erosion +# - Inference cost crisis +# - Open-source displacement +# - Responsible AI failure +# - Hallucination liability +# - GPU dependency bottleneck +# +# Adaptation types: +# as-is — The diagnostic works without modification for AI-ML companies. +# enhanced — The diagnostic is relevant but benefits from additional AI-ML-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for AI-ML. + +pack_metadata: + sector: "ai-ml" + display_name: "AI-ML" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Churn in AI-ML companies has distinctive drivers that do not exist in traditional SaaS: model accuracy degradation (drift), competitor model quality leapfrogging, open-source alternatives reaching 'good enough' quality, hallucination events that destroy trust, and inference cost increases passed through to customers. The base diagnostic applies but requires substantial reframing around model quality as the primary retention driver." + additional_triage_questions: + - question: "Has the model's accuracy on the customer's specific use case degraded since they first adopted — either through model drift, data distribution changes, or the customer's use case evolving beyond the model's training data?" + purpose: "AI-specific churn is often triggered by model quality degradation that the customer experiences before internal monitoring detects it. The customer tries an edge case, gets a wrong answer, and begins evaluating alternatives." + routing_impact: "Accuracy degradation routes to model-drift-rate analysis, data pipeline reliability review, and customer-specific fine-tuning assessment. Stable accuracy with churn routes to competitive analysis and pricing review." + - question: "Are customers leaving for a competitor's model, for an open-source alternative, or because they decided to build an in-house model?" + purpose: "Each churn destination has different implications. Competitor churn suggests a quality or pricing gap. Open-source churn suggests the product's value-add over free alternatives is insufficient. In-house build suggests the customer outgrew the general product." + routing_impact: "Competitor churn routes to porters-five-forces and competitive-threat-diagnosis. Open-source churn routes to blue-ocean-strategy and differentiation analysis. In-house build routes to enterprise feature development and managed deployment services." + - question: "Has a hallucination or model error event preceded the churn decision — specifically, did the model produce a confidently wrong output on a high-stakes task that damaged the customer's trust?" + purpose: "A single hallucination event on a critical task can trigger churn even when the model is 95%+ accurate on average. Trust is destroyed by failures, not sustained by averages." + routing_impact: "Hallucination-triggered churn routes to trust-equation analysis, hallucination rate improvement, and customer communication protocol review." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Model accuracy insufficient for the customer's evolved use case" + reason: "AI customers' requirements evolve as they deploy the model in more critical workflows. The accuracy that was acceptable for pilots becomes insufficient for production." + - diagnosis: "Open-source alternative reached 'good enough' quality" + reason: "The open-source model ecosystem improves weekly. A customer who adopted your proprietary model 12 months ago may now have a free alternative that serves 80% of their needs." + less_likely: + - diagnosis: "UX or feature-based churn" + reason: "For API-delivered AI products, the UX is the API interface — rarely a churn driver. The model's output quality dominates the satisfaction equation." + sector_specific_diagnoses: + - name: "Hallucination-triggered trust collapse" + description: "A model hallucination or confidently wrong output on a high-stakes task destroyed customer trust. Even if the model is 95%+ accurate on average, a single dramatic failure in a critical workflow causes the customer to question all outputs, reverting to manual processes and eventually churning." + symptoms: + - "Customer support ticket describing a specific, dramatic model error that affected their business" + - "Customer reduced usage sharply after a specific date (corresponding to the error event)" + - "Customer switched from autonomous model usage to mandatory human review of all outputs" + - "Customer cited 'trust' or 'reliability' as the primary churn reason rather than accuracy statistics" + routes_to_skills: ["trust-equation", "systems-thinking", "ai-human-centered-approach"] + routes_to_templates: ["incident-postmortem", "action-plan"] + - name: "Open-source displacement" + description: "An open-source model (Llama, Mistral, Stable Diffusion, or domain-specific alternatives) reached sufficient quality for the customer's use case, eliminating the need to pay for a proprietary API. The customer deploys the open-source model on their own infrastructure." + symptoms: + - "API usage declining gradually rather than dropping to zero (customer testing alternatives in parallel)" + - "Customer's technical team asking about model export, fine-tuning APIs, or self-hosting options" + - "Churn concentrated among technically sophisticated customers with ML engineering capacity" + - "Customer citing cost rather than quality as the primary reason for leaving" + routes_to_skills: ["disruptive-innovation", "porters-five-forces", "blue-ocean-strategy"] + routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + - name: "Data moat erosion" + description: "The proprietary data advantage that differentiated the model is eroding. Competitors have built equivalent datasets through alternative sources, synthetic data generation, or partnerships. The model's quality advantage narrows, reducing the switching cost and making price the primary decision factor." + symptoms: + - "Competitor models achieving comparable accuracy on public benchmarks" + - "New entrants launching products with comparable quality despite starting later" + - "Customer negotiations increasingly focused on price rather than quality" + - "Win rate in competitive evaluations declining despite stable or improving model metrics" + routes_to_skills: ["porters-five-forces", "first-mover-strategy", "scenario-planning"] + routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Hallucination rate increasing above the customer segment's tolerance threshold, especially without proactive communication to affected customers." + - "A well-funded competitor or a credible open-source model matching your accuracy on the core task — the churn signal leads by 3-6 months." + - "Customer-reported accuracy satisfaction dropping below 70% for any segment — a leading indicator of churn within two quarters." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML growth stalls have characteristic patterns: model quality plateaus that limit expansion into higher-value use cases, inference cost ceilings that prevent profitable scaling, open-source alternatives capturing the low end of the market, and enterprise adoption friction from responsible AI requirements. The base diagnostic applies but needs AI-specific growth decomposition." + additional_triage_questions: + - question: "Has your model's accuracy improvement trajectory flattened — are you getting diminishing returns from additional data, training, or architecture improvements?" + purpose: "A model quality plateau directly constrains growth. If the model cannot achieve the accuracy required for the next tier of use cases, the addressable market is capped." + routing_impact: "Accuracy plateau routes to architecture evaluation (is the current approach reaching its ceiling?) and data strategy review (is the data flywheel generating useful signal?)." + - question: "Is your growth limited by inference cost — specifically, are there use cases or customer segments where the per-prediction cost makes the economics unworkable?" + purpose: "AI-ML growth can stall when the addressable market requires lower per-unit pricing than the current inference cost structure allows." + routing_impact: "Inference cost limitation routes to model optimization (distillation, quantization, architecture efficiency) and pricing model evaluation (outcome-based pricing that decouples price from per-request cost)." + - question: "Are enterprise prospects stalling in evaluation because of responsible AI requirements — bias audits, explainability mandates, or regulatory compliance concerns?" + purpose: "Enterprise AI adoption is increasingly gated by responsible AI due diligence. A growth stall at the enterprise level may be a compliance readiness problem, not a product problem." + routing_impact: "Responsible AI friction routes to ai-stakeholder-balance and responsible AI infrastructure investment. Provide prepared model cards, bias reports, and compliance documentation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Model quality plateau capping addressable market" + reason: "AI products often exhaust the use cases they can serve at current accuracy levels. Growth stalls when the remaining market requires accuracy the model cannot achieve." + - diagnosis: "Inference cost preventing profitable scaling" + reason: "Unlike traditional SaaS where marginal cost is near-zero, AI inference has meaningful per-unit cost. Scaling can worsen unit economics if cost optimization does not keep pace." + less_likely: + - diagnosis: "Marketing or awareness problem" + reason: "AI products with strong accuracy and clear use cases typically generate organic demand. Growth stalls are more often product-limitation or economics problems than awareness problems." + sector_specific_diagnoses: + - name: "Inference cost crisis" + description: "Revenue is growing but gross margins are declining because inference cost scales with usage. The more customers use the product, the more compute is consumed, and the cost structure becomes unsustainable. The company faces a choice: raise prices (risking churn), optimize the model (uncertain timeline), or accept permanently lower margins." + symptoms: + - "Gross margin declining as revenue grows" + - "Compute costs growing faster than revenue" + - "Heavy users generating negative gross margin per account" + - "Engineering team spending majority of time on cost optimization rather than model improvement" + routes_to_skills: ["business-model-canvas", "systems-thinking", "balanced-scorecard"] + routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + - name: "GPU dependency bottleneck" + description: "Growth is constrained by GPU availability rather than demand. The company cannot serve more customers because it cannot procure sufficient compute — either due to NVIDIA supply constraints, cloud provider allocation limits, or budget limitations on GPU spend." + symptoms: + - "Waitlisting new customers or rate-limiting existing ones" + - "Single cloud provider dependency for GPU access" + - "Spot instance usage causing latency variability" + - "GPU procurement lead times exceeding 3 months" + routes_to_skills: ["scenario-planning", "porters-five-forces", "systems-thinking"] + routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Model accuracy improvement rate declining below 1% per quarter despite continued R&D investment — suggests the architecture may be approaching its ceiling." + - "Gross margin compressing below 50% as usage scales — the compute COGS problem is becoming structural." + - "Enterprise pipeline stalling at 'security and compliance review' stage for more than 60% of prospects." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Product-market fit in AI-ML requires distinguishing between model-market fit (is the model accurate enough for this use case?), wrapper-market fit (is the UX/integration good enough?), and economics-market fit (can the product be delivered profitably at the price the market will pay?). Many AI products have impressive models that fail as businesses because the wrapper is inadequate or the economics do not work. The diagnostic must triage across all three dimensions." + additional_triage_questions: + - question: "When customers leave or do not convert, is the reason model accuracy ('it was not accurate enough'), product experience ('it was too hard to integrate/use'), or price ('it costs too much for the value delivered')?" + purpose: "Distinguishes the three PMF dimensions: model quality, product design, and unit economics. Each requires a fundamentally different intervention." + routing_impact: "Model quality issues route to data and architecture investment. Product experience issues route to developer experience and integration improvement. Price issues route to inference cost optimization and pricing model innovation." + - question: "Does your model outperform general-purpose alternatives (GPT-4, Claude, Gemini) on the specific task your customers care about — not on general benchmarks, but on their actual data?" + purpose: "If general-purpose models are 'good enough' for the customer's use case, the AI product lacks differentiation. PMF requires meaningful accuracy superiority on the customer's specific task." + routing_impact: "No meaningful accuracy advantage routes to blue-ocean-strategy for differentiation or to vertical specialization strategy. Meaningful advantage routes to communicating the difference more clearly." + - question: "Are users increasing their usage over time (the data flywheel is working), or does usage plateau after initial integration?" + purpose: "Increasing usage is the strongest AI-specific PMF signal — it means the model is embedded in workflows and users are expanding scope. Flat usage means the product solves a bounded task and does not expand." + routing_impact: "Expanding usage routes to expansion-revenue optimization and new-use-case marketing. Flat usage routes to product-life-cycle analysis and assessment of whether the market is a bounded problem." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Model good enough for demos but not for production" + reason: "The demo-to-production gap is the defining AI PMF challenge. Models that impress in controlled demonstrations fail on edge cases in production. This is the most common AI PMF failure mode." + - diagnosis: "Wrapper problem — model works but the product does not" + reason: "Many AI companies have strong models wrapped in poor products. Developer experience, documentation, integration tooling, and error handling matter as much as model accuracy." + less_likely: + - diagnosis: "Market does not exist" + reason: "The AI market is expanding rapidly. If the model solves a real task accurately, the market exists. The question is usually product-market fit, not market existence." + sector_specific_diagnoses: + - name: "Model quality plateau" + description: "The model's accuracy has plateaued at a level below what the market requires for production deployment. Additional data and training provide diminishing returns. The architecture may have reached its ceiling, or the available training data may be insufficient. The product works for low-stakes use cases but cannot cross the accuracy threshold for the higher-value, production-critical workflows that would justify premium pricing." + symptoms: + - "F1 or accuracy metrics improving by less than 1% per quarter despite continued R&D investment" + - "Customer evaluations that end with 'impressive but not quite accurate enough for our use case'" + - "Strong adoption in low-stakes use cases but no penetration into critical workflows" + - "Research team proposing fundamental architecture changes rather than incremental improvements" + routes_to_skills: ["disruptive-innovation", "product-life-cycle", "defining-and-exploring-problems"] + routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + sector_red_flags: + - "Customers who complete integration but usage drops after 30 days — the model impressed in evaluation but fails in production reality." + - "High API call volume with low customer-reported satisfaction — customers are using the model but correcting its outputs frequently." + - "No customer willing to publicly endorse the product — a sign that no one trusts it enough to stake their reputation." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "AI-ML pricing is fundamentally different from SaaS pricing because inference cost creates meaningful per-unit COGS. The pricing challenge is threefold: pricing must cover inference cost (variable COGS), pricing must be competitive with open-source alternatives (free substitutes), and pricing must align with the value delivered (which varies by use case). AI pricing models — per-API-call, per-token, per-outcome, tiered by model quality/speed — each have distinct strategic implications." + additional_triage_questions: + - question: "Is your pricing structure aligned with how customers derive value — specifically, do they pay more when they get more value (outcome-based), pay per unit of consumption (usage-based), or pay a fixed fee regardless of usage?" + purpose: "AI product value varies enormously by query. A fixed-fee model leaves money on the table for high-value predictions and overcharges for low-value ones. Usage-based captures volume but not value. Outcome-based captures value but is hard to measure." + routing_impact: "Misaligned pricing structure routes to pricing model innovation and willingness-to-pay research by use case." + - question: "What is your revenue per inference request relative to your cost per inference request — and how does this ratio change across customer segments and use cases?" + purpose: "Per-unit profitability is the fundamental AI pricing question. If high-volume customers generate negative gross margin per request, scaling makes the business worse." + routing_impact: "Negative per-unit margin for any segment routes to immediate pricing restructure or cost optimization for that segment." + - question: "How does your pricing compare to the 'build-it-yourself-with-open-source' cost? Customers increasingly calculate: 'Could I deploy Llama / Stable Diffusion / Whisper on my own infrastructure for less?'" + purpose: "The open-source cost floor constrains AI pricing. If the customer can replicate 80% of the value at 30% of the cost using open-source, the pricing must reflect the premium for the remaining 20% — which is accuracy, reliability, support, and compliance." + routing_impact: "Open-source competitive pricing routes to differentiation analysis and value-selling strategy. If the premium is not justifiable, routes to cost optimization and business model pivot." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Under-pricing high-value use cases while over-pricing commodity tasks" + reason: "AI products serving multiple use cases through a single API often price uniformly when value varies 100x between queries. A legal analysis worth $500 is priced the same as a simple classification worth $0.01." + - diagnosis: "Pricing above the open-source cost floor without sufficient differentiation to justify the premium" + reason: "As open-source models improve, the price ceiling for proprietary AI products declines. Pricing that was defensible 12 months ago may now be uncompetitive." + less_likely: + - diagnosis: "Over-pricing causing churn" + reason: "AI products more often under-price than over-price. If the model genuinely delivers value, customers absorb price increases because switching costs (integration, data, customization) are high." + sector_specific_diagnoses: + - name: "Inference cost trap" + description: "The per-request cost of serving the model is so close to the per-request revenue that gross margins are unsustainably thin. Pricing is constrained from above by competitor pricing and open-source alternatives, and from below by inference compute costs. The company is trapped between a price ceiling and a cost floor with insufficient room for a viable business." + symptoms: + - "Gross margin below 40% with no clear path to improvement" + - "Revenue per request declining (competitive pressure) while cost per request is stable or rising" + - "Unable to profitably serve high-volume/low-value use cases" + - "Engineering spending majority of effort on cost optimization rather than model improvement" + routes_to_skills: ["business-model-canvas", "four-ps-marketing", "scenario-planning"] + routes_to_templates: ["unit-economics-snapshot", "strategic-analysis-one-pager"] + sector_red_flags: + - "Revenue per API call declining for three consecutive quarters without corresponding cost reduction — pricing power is eroding." + - "Top 10 customers generating negative gross margin because their usage pattern is compute-intensive relative to what they pay." + - "Open-source models within 5% accuracy of your production model on public benchmarks — the price ceiling is about to drop." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML fundraising benefits from the AI investment cycle but faces unique scrutiny: investors question gross margins (lower than SaaS), data moat durability, open-source substitution risk, and compute cost scalability. The diagnostic must address both the AI-specific metrics investors evaluate and the AI-specific objections they raise." + additional_triage_questions: + - question: "Can you articulate your data moat — what proprietary data do you have, how is it generated, and how long would it take a well-funded competitor to replicate it?" + purpose: "The data moat is the primary defensibility question in AI fundraising. Investors know that models can be replicated; data is harder. A clear data moat narrative is often the decisive factor." + routing_impact: "Strong data moat routes to articulating it clearly in fundraising materials. Weak or unclear data moat routes to data-moat-index assessment and strategy development before fundraising." + - question: "What is your compute-adjusted gross margin trajectory — is it improving, stable, or declining as you scale?" + purpose: "AI-specific gross margin scrutiny is intensifying. Investors apply the a16z 'AI margin gap' framework: if your margins are 50% today, what is the path to 65-70%?" + routing_impact: "Improving margin trajectory routes to highlighting it in investor materials. Stable or declining routes to cost optimization plan and honest margin guidance." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "AI hype-cycle timing mismatch" + reason: "AI fundraising is cyclical. Companies raising during peak AI enthusiasm (2023-2024) face different dynamics than those raising during correction phases. Timing the narrative to the cycle matters." + - diagnosis: "Margin story insufficient" + reason: "The most common AI fundraising objection is: 'How do you achieve SaaS-like margins with compute COGS?' A clear, data-backed margin improvement plan is essential." + less_likely: + - diagnosis: "Market too small" + reason: "AI markets are perceived as enormous. The market-size objection is rare for AI companies. More common: 'Can you defend this position?'" + sector_specific_diagnoses: + - name: "AI differentiation ambiguity" + description: "The company cannot clearly articulate why its AI product is defensible against competitors (proprietary and open-source), well-funded later entrants, and the foundation model providers themselves. Investors see a strong product but an indefensible position." + symptoms: + - "Investors expressing interest in the market but questioning the moat" + - "Pitch conversations dominated by 'what happens when OpenAI/Google ships this as a feature?'" + - "No clear data moat, proprietary architecture advantage, or regulatory moat" + - "Positive initial meetings that do not progress to term sheet" + routes_to_skills: ["porters-five-forces", "blue-ocean-strategy", "first-mover-strategy"] + routes_to_templates: ["fundraising-deck-outline", "competitive-landscape-brief"] + sector_red_flags: + - "Raising at a valuation premised on the AI hype cycle premium rather than on business fundamentals — vulnerable to repricing when sentiment shifts." + - "Unable to answer the 'data moat' question in under 60 seconds — investors have heard 'we have an AI company' a thousand times; differentiation must be immediate." + - "Compute-adjusted gross margin below 40% without a credible path to 60%+ within 18 months." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Revenue in AI-ML decomposes differently from SaaS: it is primarily usage-driven (per API call, per token, per prediction) rather than seat-driven. Revenue growth depends on: new customer acquisition, per-customer usage growth (the expansion engine), pricing optimization, and model quality improvement (which unlocks higher-value use cases). Revenue problems often trace to model quality issues (customers leave or reduce usage because accuracy declined), pricing misalignment, or compute cost pressure squeezing margins." + additional_triage_questions: + - question: "Decompose your revenue growth: what percentage comes from new customers, increased usage from existing customers, pricing increases, and upsells to premium model tiers?" + purpose: "AI revenue growth drivers are different from SaaS. New customer acquisition is important but usage expansion from existing customers is often the primary growth engine for API-delivered AI." + routing_impact: "New customer acquisition slowing routes to go-to-market and differentiation analysis. Usage expansion slowing routes to model quality assessment and use-case expansion strategy." + - question: "Is the revenue problem a model quality problem (customers leaving because accuracy dropped), a pricing model problem (per-token pricing too expensive for the use case), or a competition problem (open-source caught up)?" + purpose: "AI revenue problems cluster into these three categories. The treatment differs fundamentally for each." + routing_impact: "Model quality routes to model improvement and customer communication. Pricing routes to pricing restructure and cost optimization. Competition routes to differentiation and blue-ocean strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Usage-based revenue volatility" + reason: "AI revenue tied to API usage is inherently volatile — a single customer's batch job can double or halve monthly revenue. This volatility is structural, not a business failure." + - diagnosis: "Revenue-cost divergence" + reason: "Growing revenue with growing compute costs can result in declining gross profit. Revenue growth without margin improvement is dangerous in AI." + less_likely: + - diagnosis: "Seasonal revenue variation" + reason: "AI API usage is rarely seasonal. Revenue fluctuations are more likely driven by customer usage patterns or model quality changes than by calendar effects." + sector_specific_diagnoses: + - name: "Revenue quality erosion through commodity displacement" + description: "Revenue from commodity AI tasks (basic classification, simple extraction, generic text generation) is declining as open-source and large providers offer these capabilities at lower cost or free. Revenue is increasingly concentrated in high-value, specialized tasks — a healthier mix but a smaller addressable market." + symptoms: + - "Revenue declining on specific API endpoints while growing on others" + - "Price sensitivity increasing for commodity tasks" + - "Customer requests for lower pricing on specific capabilities, citing open-source alternatives" + - "Revenue concentration in fewer, higher-value use cases" + routes_to_skills: ["product-life-cycle", "blue-ocean-strategy", "business-model-canvas"] + routes_to_templates: ["unit-economics-snapshot", "strategic-analysis-one-pager"] + sector_red_flags: + - "Revenue per API call declining while compute cost per call remains stable — the margin squeeze is accelerating." + - "Top 3 customers representing more than 50% of revenue — usage-based revenue concentration creates extreme fragility." + - "Revenue growth decelerating while model accuracy metrics are stable — suggests market saturation or competitive displacement." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Competitive dynamics in AI-ML are unlike any other sector. Threats come from five distinct directions: direct competitors (other AI startups), foundation model providers (OpenAI, Anthropic, Google shipping the feature natively), open-source models (free alternatives), cloud providers (AWS, GCP, Azure building competing AI services), and the customer's own ML team (building in-house). The base diagnostic must address all five threat vectors, which is a fundamental reframing." + additional_triage_questions: + - question: "Is the competitive threat from another AI startup, a foundation model provider adding your capability as a feature, an open-source model reaching comparable quality, a cloud provider offering a competing service, or your customer's internal ML team replicating your model?" + purpose: "Each threat vector requires a different response. Startup competition is about differentiation. Foundation model threat is about deep vertical integration that horizontal models cannot match. Open-source is about enterprise value-add. Cloud provider threat is about portability and specialized accuracy. In-house build is about proving total cost of ownership advantage." + routing_impact: "Startup competition routes to blue-ocean-strategy. Foundation model threat routes to vertical depth and integration moat strategy. Open-source routes to enterprise packaging and support. Cloud provider routes to multi-cloud strategy. In-house build routes to TCO analysis and managed services." + - question: "How quickly can a well-funded competitor replicate your current model accuracy, given access to equivalent compute and publicly available data — 3 months, 6 months, 12 months, or more?" + purpose: "The replication timeline defines how defensible the model is. If a competitor can replicate in 3 months, the model is not the moat — the data, distribution, or integration must be." + routing_impact: "Short replication timeline (<6 months) routes to data moat and integration moat strategy. Long replication timeline (>12 months) routes to maximizing the model advantage while building additional moats." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Foundation model provider encroachment" + reason: "The greatest AI competitive threat is OpenAI, Anthropic, Google, or Meta adding your capability to their general-purpose model. This threat is existential for thin-wrapper AI companies." + - diagnosis: "Open-source erosion of the accuracy gap" + reason: "Open-source models narrow the quality gap every month. Any accuracy advantage over open-source alternatives has a measurable half-life." + less_likely: + - diagnosis: "Price-based competition from other startups" + reason: "AI startup-to-startup price competition is less common than quality competition. The primary competitive dimensions are accuracy, reliability, and domain specificity — not price." + sector_specific_diagnoses: + - name: "Responsible AI failure as competitive disadvantage" + description: "Competitors with stronger responsible AI practices (bias testing, explainability, regulatory compliance) are winning enterprise deals that the company cannot close. The absence of responsible AI infrastructure — model cards, bias audits, compliance documentation — has become a competitive liability rather than a cost to avoid." + symptoms: + - "Enterprise deals lost with feedback citing 'insufficient AI governance' or 'failed responsible AI audit'" + - "Competitors highlighting responsible AI certifications in competitive differentiation" + - "Customer procurement adding responsible AI requirements that the company cannot satisfy" + - "Regulatory developments specifically affecting the company's AI application domain" + routes_to_skills: ["ai-stakeholder-balance", "trust-equation", "swot-pest-analysis"] + routes_to_templates: ["competitive-landscape-brief", "risk-assessment-brief"] + sector_red_flags: + - "A foundation model provider announcing a feature that overlaps with 50%+ of your core value proposition — timeline to revenue impact is 6-12 months." + - "An open-source model achieving within 5% of your accuracy on the primary benchmark — the customer evaluation dynamics change materially." + - "A well-funded competitor ($100M+) entering your specific vertical with a dedicated research team — the data moat race intensifies." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML strategic drift manifests uniquely: the research team pursues accuracy improvements that do not translate to business impact, the company chases every AI use case rather than dominating one vertical, or the strategy oscillates between proprietary-vs-open-source positioning. The fast-moving nature of AI amplifies drift — every competitive announcement triggers a strategic reconsideration." + additional_triage_questions: + - question: "Has the company's strategic focus shifted between horizontal platform, vertical application, and infrastructure provider — and if so, how many times in the past 12 months?" + purpose: "AI companies frequently drift between these three strategic positions. Each requires different team composition, go-to-market motion, and product architecture. Oscillating between them wastes resources and confuses the market." + routing_impact: "Multiple strategic pivots route to strategic-thinking-and-alignment for clarity on positioning. Stable positioning with execution drift routes to operational improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Research-driven strategy distortion" + reason: "AI companies with strong research teams are uniquely vulnerable to 'research-led strategy' where the team pursues intellectually interesting problems rather than commercially valuable ones." + less_likely: + - diagnosis: "External market disruption causing drift" + reason: "More often, AI-ML drift is self-inflicted through reaction to competitive announcements and the temptation to pursue every use case." + sector_specific_diagnoses: + - name: "AI use-case sprawl" + description: "The company serves too many AI use cases without dominating any single one. The model and product are spread thin across verticals, the team cannot deeply understand any customer's domain, and no individual use case generates sufficient revenue to justify dedicated optimization. The company is a 'general-purpose AI tool' competing against specialists in every vertical." + symptoms: + - "Revenue spread across 10+ distinct use cases with no single use case exceeding 20% of revenue" + - "Sales team positioning the product differently for every prospect" + - "Customer success team unable to develop deep domain expertise" + - "Model accuracy varying dramatically across use cases with no clear best-performing domain" + routes_to_skills: ["blue-ocean-strategy", "business-model-canvas", "strategic-thinking-and-alignment"] + routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + sector_red_flags: + - "Strategy changing after every competitive model announcement — indicating reactive rather than conviction-driven leadership." + - "Research team's work not connected to product roadmap for two or more consecutive quarters." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML team dysfunction centers on the unique tension between research culture and product culture. Researchers optimize for model quality, novelty, and publication potential. Product engineers optimize for reliability, latency, and maintainability. Business teams optimize for revenue and margins. These three cultures often clash on prioritization, timelines, and what constitutes success. The research-to-product handoff is the most common failure point in AI companies." + additional_triage_questions: + - question: "Is there tension between the research/ML team and the product engineering team — specifically, do research breakthroughs fail to reach production, or does the production team ship models that the research team considers suboptimal?" + purpose: "The research-to-production pipeline is the defining team challenge in AI-ML. Dysfunction here means the company either has great models that never ship or ships inferior models while better ones sit in notebooks." + routing_impact: "Research-to-production gap routes to MLOps investment and process design. Product team shipping without research input routes to organizational alignment and shared quality standards." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Research-product cultural mismatch" + reason: "Research culture (publish-oriented, accuracy-maximizing, long time horizons) conflicts with product culture (ship-oriented, cost-constrained, short iterations). This is the defining AI team dysfunction." + less_likely: + - diagnosis: "Individual performance issues" + reason: "AI team dysfunction is almost always systemic — wrong incentives, unclear handoff processes, or misaligned goals between research and product." + sector_specific_diagnoses: + - name: "Research-to-production pipeline failure" + description: "Research develops improved models that never reach production because the handoff to product engineering is broken. Models languish in notebooks, productionization takes months, and the deployed model lags the research frontier by 6+ months. The company's research investment fails to translate into product improvement." + symptoms: + - "Multiple 'improved' models in research repositories that are not deployed" + - "Product engineering citing deployment complexity, cost, or latency as reasons for not shipping research models" + - "Research team frustrated that their work is 'wasted'" + - "Deployed model accuracy trailing internal research capabilities by 6+ months" + routes_to_skills: ["systems-thinking", "delegation-and-empowerment", "strategic-thinking-and-alignment"] + routes_to_templates: ["action-plan", "team-health-check"] + sector_red_flags: + - "Research team publishing papers while the product model has not been updated in 6 months — the knowledge is not being commercialized." + - "ML engineers and product engineers in separate reporting chains with no shared objectives." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Co-founder conflict in AI-ML companies has a distinctive flavor: the tension between research depth (the ML co-founder wants to build the best model) and commercial pragmatism (the business co-founder wants to ship, sell, and grow revenue). This mirrors the CTO/CEO tension in SaaS but is more acute because AI research is expensive, time-consuming, and its commercial value is uncertain." + additional_triage_questions: + - question: "Does the conflict center on model investment (how much to spend on research and training), product direction (which use cases to serve), monetization approach (pricing structure, open-source strategy), or equity/recognition (credit for the company's technical achievements)?" + purpose: "AI co-founder conflicts cluster around these categories, each with different resolution paths." + routing_impact: "Model investment conflicts route to balanced-scorecard for objective resource allocation. Product direction routes to data-driven use case evaluation. Monetization routes to business-model-canvas. Equity/recognition routes to cooperative-negotiation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Research ambition vs. commercial pragmatism" + reason: "The ML co-founder wants to build the frontier model; the business co-founder wants to ship what works and generate revenue. Both are right — the conflict is about sequencing and resource allocation." + less_likely: + - diagnosis: "Fundamental vision misalignment" + reason: "AI co-founders usually agree on the vision (build an AI product that changes the industry). Disagreement is on execution: how much to invest in research vs. product, when to ship, and how to price." + sector_specific_diagnoses: + - name: "Research-vs-revenue tension" + description: "The ML co-founder prioritizes model quality, research publication, and architectural innovation. The business co-founder prioritizes revenue generation, customer acquisition, and unit economics. Neither is wrong, but the inability to allocate resources creates paralysis — some months the research team gets extra GPU budget, other months the sales team gets headcount, without a coherent strategy." + symptoms: + - "Resource allocation oscillating between research and sales quarterly" + - "Co-founders presenting different narratives about the company to investors" + - "Research team and sales team working toward implicitly different goals" + - "Key hires leaving because of conflicting signals about company direction" + routes_to_skills: ["balanced-scorecard", "cooperative-negotiation", "strategic-thinking-and-alignment"] + routes_to_templates: ["decision-journal", "quarterly-strategic-review"] + sector_red_flags: + - "ML co-founder spending time on research papers while the product model underperforms — misallocated research talent." + - "Business co-founder committing to accuracy SLAs without consulting the ML co-founder — a recipe for broken promises." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML market entry decisions must evaluate not just market size and competition but also data availability, model feasibility, regulatory environment, and the accuracy threshold required by the market. An AI product cannot enter a market if the data does not exist to train the model or if the required accuracy is unachievable." + additional_triage_questions: + - question: "Does sufficient training data exist for this market — either through public datasets, potential data partnerships, or data that the product itself will generate? What is the estimated cost to build a competitive dataset?" + purpose: "Data availability is the gating factor for AI market entry. A market with unlimited demand but no training data is inaccessible." + routing_impact: "Insufficient data routes to data partnership strategy and synthetic data feasibility analysis. Abundant data routes to speed-of-execution strategy." + - question: "What accuracy level does this market require — and is there evidence (academic research, competitor products, pilot results) that achievable accuracy meets the market's threshold?" + purpose: "Some markets require accuracy that current AI cannot achieve (e.g., autonomous driving Level 5). Entering these markets prematurely wastes resources." + routing_impact: "Accuracy achievable routes to market entry execution. Accuracy uncertain routes to pilot-based validation before committing." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Data moat not buildable in the target market" + reason: "Some markets have data dynamics that prevent moat formation — data is widely available, competitors have equivalent access, or data freshness makes historical accumulation irrelevant." + less_likely: + - diagnosis: "Market too small" + reason: "AI enables global reach and vertical specialization. Seemingly small markets often support significant AI businesses." + sector_specific_diagnoses: + - name: "Accuracy-market threshold gap" + description: "The AI model cannot achieve the accuracy required by the target market. The product works in controlled settings but fails to meet the error tolerance of real-world deployment. The market needs 99%+ accuracy (medical, financial, safety-critical), and the model achieves 90-95%." + symptoms: + - "Pilots that start enthusiastically but end with 'not quite ready for production'" + - "Customers requiring human review for 100% of model outputs, negating the efficiency gain" + - "Regulatory requirements for accuracy levels that the model cannot achieve" + - "Academic literature suggesting the accuracy ceiling for the current approach is below market requirements" + routes_to_skills: ["defining-and-exploring-problems", "disruptive-innovation", "ai-augmentation-not-automation"] + routes_to_templates: ["market-opportunity-summary", "decision-rationale-memo"] + sector_red_flags: + - "Entering a market where the required accuracy exceeds the current state of the art — the market entry is premature regardless of demand." + - "No clear path to acquiring sufficient training data within 12 months." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML hiring faces acute talent scarcity and unique role definitions. ML researchers, MLOps engineers, data engineers, and AI product managers are specialized roles that traditional tech hiring processes often fail to evaluate. Compensation expectations for top ML talent frequently exceed startup budgets, and the competition for PhDs with production experience is intense." + additional_triage_questions: + - question: "Are you hiring ML researchers (to improve the model), ML engineers (to productionize and serve the model), data engineers (to build and maintain data pipelines), or AI product managers (to bridge research and commercial priorities)?" + purpose: "Each role requires different evaluation criteria, compensation structures, and sourcing channels. Misidentifying the role type leads to hiring the wrong profile." + routing_impact: "ML researcher hiring routes to academic recruiting strategy and research-incentive design. ML engineer routes to production-focused evaluation. Data engineer routes to data infrastructure assessment. AI PM routes to hybrid profile evaluation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Hiring researchers when engineers are needed (or vice versa)" + reason: "AI companies frequently hire brilliant researchers who cannot productionize models, or production engineers who cannot improve model quality. The distinction between these roles is critical." + less_likely: + - diagnosis: "Compensation uncompetitive" + reason: "While ML talent commands premiums, compensation is rarely the sole barrier. Mission, team quality, technical challenges, and equity are strong differentiators for startups." + sector_specific_diagnoses: + - name: "ML talent profile mismatch" + description: "The company hires ML talent with the wrong profile for the current stage. A seed-stage company hiring a pure researcher from a large lab gets someone who expects months-long research cycles and publication incentives. A growth-stage company hiring a generalist full-stack ML engineer gets someone who cannot push the model frontier when specialization is needed." + symptoms: + - "ML hires not productive within 6 months" + - "Research hires frustrated by the lack of compute resources and publication opportunities" + - "Engineering hires struggling with the ambiguity and experimentation inherent in ML development" + - "Team composition skewed toward either research or engineering without balance" + routes_to_skills: ["eisenhower-matrix", "delegation-and-empowerment"] + routes_to_templates: ["hiring-scorecard", "role-description-template"] + sector_red_flags: + - "ML team lead departing — the most costly single-person churn event in an AI company, often triggering 3-6 months of productivity loss." + - "Hiring exclusively from academia without anyone with production ML experience — models will be elegant but not deployable." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML operational chaos manifests as model serving instability, data pipeline failures, training infrastructure issues, and the compounding effect of model drift creating unpredictable product behavior. The continuous nature of AI systems — models are not just deployed, they must be monitored, retrained, and evaluated — creates unique operational demands." + additional_triage_questions: + - question: "Do you have automated monitoring for model performance degradation (drift detection), or does model quality decline only become apparent when customers complain?" + purpose: "AI operations without drift monitoring is flying blind. Model quality can degrade silently for weeks before customer complaints surface." + routing_impact: "No drift monitoring routes to immediate MLOps investment. Monitoring exists but is not actionable routes to automated retraining pipeline development." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "MLOps infrastructure insufficient for production scale" + reason: "Most AI companies outgrow their early-stage ML infrastructure (Jupyter notebooks, manual deployments, ad-hoc monitoring) before they invest in production-grade MLOps." + less_likely: + - diagnosis: "Over-engineering processes" + reason: "AI companies more often under-invest in operational processes than over-invest. The research culture tends to resist process." + sector_specific_diagnoses: + - name: "Silent model degradation" + description: "The production model's accuracy is declining due to data drift, but no monitoring detects it. Customers experience worsening output quality over weeks or months, leading to trust erosion and churn, while internal metrics show no alerts." + symptoms: + - "Customer complaints about accuracy increasing without corresponding changes to model metrics" + - "No automated drift detection or model performance monitoring in production" + - "Production evaluation dataset not updated to reflect current data distribution" + - "Last model retraining was more than 3 months ago for a domain with dynamic data" + routes_to_skills: ["systems-thinking", "balanced-scorecard"] + routes_to_templates: ["incident-postmortem", "action-plan"] + sector_red_flags: + - "No automated rollback capability for model deployments — a bad model update must be manually reverted." + - "Data pipeline failures occurring weekly without post-incident improvements." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Leadership crises in AI-ML have a distinctive dimension: the technical founder may be brilliant at research but incapable of managing a growing organization, while a non-technical CEO may lack the ML literacy to make informed product decisions. The dual nature of AI companies (research organization + product company) creates leadership demands that exceed most single founders' capabilities." + additional_triage_questions: + - question: "Is the leadership crisis rooted in the technical founder being unable to transition from researcher to CEO, or in the business leader being unable to evaluate and direct ML technical decisions?" + purpose: "AI companies face a unique leadership challenge: the CEO must be both technically fluent and commercially competent. Identifying which dimension is failing guides the intervention." + routing_impact: "Technical founder management gap routes to executive coaching and COO/President hiring. Business leader technical gap routes to CTO empowerment and technical advisory board." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Founder transition failure (researcher to CEO)" + reason: "The ML researcher who built the model is often the wrong person to scale the organization. This transition is predictable and manageable with support but devastating if ignored." + less_likely: [] + sector_specific_diagnoses: [] + sector_red_flags: + - "Technical founder spending 80%+ of time on research while the business lacks leadership — the company has a research lab, not a business." + - "Non-technical CEO making model architecture decisions without research team input." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML decision paralysis often stems from the inherent uncertainty in model development — 'one more experiment might breakthrough,' 'one more week of training data might help,' 'one more hyperparameter search might find the optimal configuration.' The research culture of exhaustive experimentation conflicts with the business need for decisions within defined time windows." + additional_triage_questions: + - question: "Is the decision being delayed because the team believes more data or more experiments will yield a better outcome — and is there diminishing returns evidence from recent experiments?" + purpose: "AI teams are uniquely susceptible to 'one more experiment' paralysis because the potential for improvement always exists. The question is whether recent experiments show diminishing returns." + routing_impact: "Diminishing returns evidence routes to decision commitment with current best model. No evidence either way routes to time-boxed experimentation (2 weeks, then ship)." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Research perfectionism preventing shipping" + reason: "AI researchers are trained to optimize. Shipping a model that is 'good enough' conflicts with the research instinct to find the optimum. This paralysis is cultural, not informational." + less_likely: + - diagnosis: "Insufficient information" + reason: "AI companies rarely lack information. They have too much — hundreds of experiment results, evaluation metrics, and benchmark comparisons. The problem is decision discipline, not data." + sector_specific_diagnoses: [] + sector_red_flags: + - "Model improvement experiments running for 3+ months without a shipping decision — the 'one more experiment' trap." + - "Architecture decision (build vs. fine-tune, model size, open-source vs. proprietary) delayed for more than 6 weeks." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Innovation drought in AI-ML manifests differently: the model stops improving, the architecture becomes stale, and the research team shifts from pursuing breakthroughs to incrementally tuning hyperparameters. This is particularly dangerous because AI competitors iterate rapidly — a 6-month innovation drought can result in competitors leapfrogging model quality." + additional_triage_questions: + - question: "What percentage of the ML team's time is spent on incremental optimization (hyperparameter tuning, data cleaning, deployment maintenance) versus exploratory research (new architectures, novel training approaches, creative data strategies)?" + purpose: "If more than 80% of ML effort is on maintenance and optimization, the team is not innovating. The model will not improve meaningfully without dedicated exploration time." + routing_impact: "Exploration below 20% routes to organizational restructuring — dedicated research track with protected time and resources." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Architecture ceiling reached" + reason: "AI model architectures have performance ceilings. If the current approach is fundamentally limited, incremental improvements will not overcome the plateau." + less_likely: + - diagnosis: "Lack of talent" + reason: "AI innovation drought is more often caused by wrong incentives (no time for research), wrong focus (optimizing existing models rather than exploring new approaches), or compute constraints than by lack of talent." + sector_specific_diagnoses: + - name: "Architecture obsolescence" + description: "The company's core model architecture has been surpassed by newer approaches (e.g., RNNs replaced by transformers, CNNs supplemented by vision transformers). The research team is optimizing an approach that has a known ceiling while competitors adopt superior architectures. Incremental improvements provide diminishing returns." + symptoms: + - "New architectures outperforming the company's approach on public benchmarks" + - "Research papers demonstrating fundamental advantages of alternative approaches" + - "ML team's experiments showing less than 1% improvement per quarter" + - "Difficulty hiring top ML talent who do not want to work on 'outdated' architecture" + routes_to_skills: ["disruptive-innovation", "product-life-cycle", "scenario-planning"] + routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + sector_red_flags: + - "Competitor model releases outperforming yours on the core task for two consecutive quarters." + - "Research team unable to articulate how the model will improve by 5%+ in the next 6 months." + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML partnerships are uniquely complex because they often involve data sharing, model integration, and compute access — each carrying distinctive risks and value dynamics. Data partnerships require trust, legal frameworks, and often domain expertise. Compute partnerships involve GPU allocation commitments and lock-in risks. Model integration partnerships raise IP ownership and competitive positioning questions." + additional_triage_questions: + - question: "Is this a data partnership (accessing training data), a compute partnership (GPU access and pricing), a model integration partnership (embedding your model in another product), or a distribution partnership (selling through another channel)?" + purpose: "Each AI partnership type has different power dynamics, risks, and value creation mechanisms." + routing_impact: "Data partnership routes to cooperative-negotiation with emphasis on trust-building and IP protection. Compute partnership routes to multi-provider strategy. Model integration routes to API design and competitive risk analysis. Distribution routes to channel economics." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Data partnership trust barrier" + reason: "AI data partnerships require organizations to share sensitive data. Trust barriers are high, legal frameworks are complex, and the partnership often stalls in legal review." + less_likely: + - diagnosis: "Cultural misalignment" + reason: "AI partnerships are primarily technical and data-driven. Cultural fit matters less than data quality, API compatibility, and legal alignment." + sector_specific_diagnoses: + - name: "Compute provider dependency as strategic vulnerability" + description: "The company depends on a single cloud provider for GPU access. The provider controls pricing, allocation priority, and can change terms with minimal notice. The dependency prevents multi-cloud strategy and creates existential risk if the provider becomes a competitor." + symptoms: + - "100% of inference and training on a single cloud provider" + - "No tested deployment path on alternative infrastructure" + - "Provider has announced competing AI services in adjacent domains" + - "GPU allocation requests denied or delayed during peak demand" + routes_to_skills: ["prisoners-dilemma-and-cooperation", "porters-five-forces", "scenario-planning"] + routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Single compute provider representing 100% of infrastructure with no migration plan." + - "Data partner announcing competing AI capabilities using the shared data." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Communication breakdowns in AI-ML have a distinctive pattern: the research team communicates in technical metrics (F1, perplexity, BLEU scores), the business team communicates in revenue and customer metrics, and customers communicate in outcome terms. The translation between these languages is a leadership responsibility that is often neglected." + additional_triage_questions: + - question: "Can the research team articulate the business impact of their model improvements, and can the business team articulate the accuracy requirements of their customer commitments?" + purpose: "The research-business communication gap is the most common AI company communication failure. If neither team can translate into the other's terms, misalignment is inevitable." + routing_impact: "Bidirectional translation failure routes to ai-communication-culture and shared KPI frameworks that connect model metrics to business outcomes." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Technical-business language barrier" + reason: "The gap between ML-speak and business-speak is wider than in traditional software companies. This is the dominant communication failure in AI companies." + less_likely: [] + sector_specific_diagnoses: [] + sector_red_flags: + - "Research team and business team unable to agree on what 'model improvement' means — one measures F1, the other measures customer complaints." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML negotiations get stuck on distinctive issues: data handling terms (does customer data train the model?), accuracy SLAs (what performance is guaranteed?), liability for model errors (who is responsible when the AI is wrong?), and IP ownership (who owns the fine-tuned model?). These AI-specific sticking points have no precedent in traditional software contracts." + additional_triage_questions: + - question: "Is the negotiation stuck on a data handling question ('Does our data train your model?'), an accuracy question ('What accuracy do you guarantee?'), a liability question ('Who is responsible when the AI is wrong?'), or an IP question ('Who owns the model trained on our data?')?" + purpose: "Each AI-specific negotiation sticking point has different resolution approaches. Data handling requires clear policy. Accuracy requires measurement methodology. Liability requires risk allocation. IP requires clear contractual terms." + routing_impact: "Data handling stalls route to transparent data policy development and contractual data segregation. Accuracy stalls route to pilot-based measurement and tiered SLAs. Liability stalls route to insurance, indemnification, and human-in-the-loop design. IP stalls route to clear fine-tuning IP frameworks." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Novel legal territory without precedent" + reason: "AI contracts involve issues (model training on customer data, AI liability, algorithmic accountability) that have limited legal precedent. Both parties' lawyers are uncertain, causing paralysis." + less_likely: + - diagnosis: "Fundamental value disagreement" + reason: "If the negotiation reached the terms stage, the buyer values the AI product. The stall is usually on risk allocation (data, accuracy, liability), not on value." + sector_specific_diagnoses: [] + sector_red_flags: + - "Enterprise deals stalling for 90+ days on 'data processing' and 'AI liability' terms — the company needs a pre-approved AI contract framework." + - "Multiple prospects asking the same data-handling question with no standardized answer — indicates the company has not resolved its own data policy." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "AI-ML culture erosion has a distinctive dimension: the tension between research culture (academic, exploratory, long-horizon) and product culture (commercial, iterative, deadline-driven). As AI companies scale from research-heavy teams to product-focused organizations, the original culture evolves — sometimes positively (more business discipline) and sometimes destructively (research talent departing because the culture no longer values exploration)." + additional_triage_questions: + - question: "Has the company recently shifted emphasis from research (model quality, publications, exploration) to product and revenue (customer metrics, deadlines, cost optimization), and is the research team experiencing this shift as a loss of identity?" + purpose: "The research-to-product cultural transition is the most common AI company culture crisis. Research talent that joined for exploration may leave when the culture shifts to production." + routing_impact: "Research culture erosion routes to dual-track organizational design — protecting research time and incentives while building product discipline." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Research culture displacement during commercialization" + reason: "As AI companies commercialize, the research culture that built the original technology is often displaced by product and sales culture. The researchers who built the company's value leave." + less_likely: + - diagnosis: "Growth outpacing culture" + reason: "AI teams often grow more slowly than traditional SaaS (hiring is constrained by talent scarcity), reducing the 'rapid scaling' culture dilution risk." + sector_specific_diagnoses: + - name: "Research talent exodus" + description: "The company's best ML researchers are leaving because the culture has shifted from research exploration to production optimization. The researchers who built the model see their roles reduced to hyperparameter tuning and customer-specific fine-tuning rather than the frontier research that attracted them. They leave for labs, bigger companies, or competitor startups that offer the research freedom the company no longer provides." + symptoms: + - "ML researcher attrition above 20% annually" + - "Exit interview feedback citing 'no time for research' or 'too much customer work'" + - "Publication output declining to zero" + - "Difficulty hiring ML researchers because word-of-mouth has shifted to 'it is not a research culture anymore'" + routes_to_skills: ["organisational-culture", "psychological-safety-practice", "ai-learning-for-leaders"] + routes_to_templates: ["team-health-check", "culture-values-document"] + sector_red_flags: + - "Top ML researcher leaving for a competitor or big tech lab — signals a culture problem that will cascade." + - "Publication output dropping to zero with no corresponding product improvement — the research capacity is gone." diff --git a/plugins/foreman/content/industry-packs/ai-ml/ai-ml-skill-overlays.yaml b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-skill-overlays.yaml new file mode 100644 index 0000000..479fb03 --- /dev/null +++ b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-skill-overlays.yaml @@ -0,0 +1,448 @@ +# AI-ML Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides AI-ML-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add an AI-ML lens for companies +# whose core product IS an AI/ML system. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct AI-ML application (strategy, model economics, competitive dynamics) +# - AI-leadership skills (highly relevant — bridge from leading with AI to building AI products) +# - Decision and thinking skills (applied to model vs. product vs. data investment decisions) +# - Negotiation skills (fundraising with AI narrative, compute contracts, data partnerships) +# - Game theory skills (open-source vs. proprietary, compute supplier dynamics) +# +# The MODEL-CENTRIC lens applies throughout: +# - Data is the moat +# - Accuracy is the product +# - Inference cost is COGS +# - Compute providers are suppliers (Porter's) +# - Open-source models are substitutes +# - The value proposition IS the model +# +# Relevance tiers: +# critical — The AI-ML overlay materially changes how the skill is applied. +# The skill executor should always surface AI-ML context. +# high — AI-ML context adds significant value. Surface when relevant. +# moderate — Useful AI-ML framing but the base skill works well as-is. + +pack_metadata: + sector: "ai-ml" + display_name: "AI-ML" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (18 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "Porter's Five Forces maps to AI-ML with structural differences from any other industry. Supplier power is extreme and concentrated — NVIDIA controls 80%+ of training-grade GPUs, and cloud compute providers (AWS, GCP, Azure) dictate infrastructure costs. Buyer power varies: enterprise buyers demand customization and audit rights, while developers choose on accuracy and latency. Threat of substitutes is existential — open-source models (Llama, Mistral, Stable Diffusion) can replicate proprietary model capabilities at zero license cost. Barriers to entry are bifurcated: high for foundation model training (compute cost), low for fine-tuned applications (transfer learning). Rivalry is intense and accelerating as well-funded competitors and open-source communities iterate weekly." + sector_anti_patterns: + - "Ignoring open-source as a substitute force. Open-source models are not inferior competitors — they are free alternatives that constantly narrow the accuracy gap. Any AI product moat based solely on model quality is temporary." + - "Underestimating supplier power of compute providers. NVIDIA's pricing, allocation decisions, and roadmap directly impact your cost structure and competitive position. GPU availability constraints are a real supply bottleneck." + - "Assuming data moats are permanent. Synthetic data generation, data augmentation, and self-supervised learning are eroding traditional data advantages. Reassess the moat continuously." + sector_example: "A computer vision startup analyzing Porter's Five Forces discovers that its primary competitive threat is not rival startups but the open-source model ecosystem. Hugging Face hosts a model nearly matching their accuracy — for free. Supplier power is concentrated in NVIDIA A100/H100 GPU availability. The analysis shifts strategy from 'build the best model' to 'build the best data pipeline and domain-specific fine-tuning infrastructure' — because the model alone is not defensible, but the proprietary data and the customer-specific customization workflow are." + benchmark_references: ["model-accuracy-f1", "inference-cost-per-request", "data-moat-index"] + + - skill: "blue-ocean-strategy" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "Blue ocean strategy is structurally essential for AI-ML companies because the general-purpose model space is a blood-red ocean — OpenAI, Anthropic, Google, and Meta compete on massive scale, and open-source alternatives proliferate weekly. Blue oceans in AI exist in vertical specialization (medical, legal, manufacturing AI), in workflow integration (AI embedded in specific business processes rather than exposed as a standalone API), in data moats (proprietary data that general-purpose models cannot access), and in delivery model innovation (on-premise deployment for regulated industries, edge AI for latency-sensitive applications). The strategy canvas should compare against both proprietary competitors AND open-source alternatives." + sector_anti_patterns: + - "Building a 'better GPT' without differentiation. Competing on general model quality against companies spending billions on training is a red ocean strategy regardless of your approach." + - "Confusing a thin wrapper on a foundation model API with a blue ocean product. If the value proposition disappears when the foundation model provider ships the same feature, the ocean is not blue — it is borrowed." + - "Pursuing a vertical AI market without validating that domain-specific accuracy requirements exceed what general-purpose models deliver. The blue ocean must require specialization that horizontal players cannot easily achieve." + sector_example: "Harvey AI carved a blue ocean in legal AI by recognizing that general-purpose LLMs cannot reliably handle legal reasoning, citation accuracy, and jurisdictional specificity. Rather than competing with ChatGPT for general writing tasks, Harvey built domain-specific fine-tuning on legal corpora, integrated with legal workflow tools, and achieved accuracy levels on legal tasks that general models could not match. The blue ocean was not 'AI for lawyers' — it was 'AI that passes the bar exam and handles real case law.'" + benchmark_references: ["model-accuracy-f1", "customer-accuracy-satisfaction", "data-moat-index"] + + - skill: "business-model-canvas" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "The Business Model Canvas for AI-ML companies requires fundamental reinterpretation of nearly every block. Value Proposition IS the model — accuracy, speed, and reliability on the customer's specific task. Key Resources are data (proprietary training data and the flywheel that generates more), compute infrastructure, and research talent. Key Activities are model training, data pipeline maintenance, and inference serving. Cost Structure is dominated by compute (training and inference) which behaves like COGS, not like traditional software development costs. Revenue Streams decompose into usage-based (per API call, per token), subscription (access tiers), and outcome-based (per successful prediction). Customer Relationships must address model trust, accuracy transparency, and responsible AI commitments. Channels include API distribution, model marketplaces, and embedded integrations." + sector_anti_patterns: + - "Treating compute as a fixed cost. AI-ML compute cost scales with usage — it is variable COGS, not a one-time development expense. The canvas must reflect this." + - "Omitting the data flywheel from Key Activities. If product usage generates data that improves the model, this is the most important activity in the business — and it should be explicit on the canvas." + - "Listing 'AI model' as the Value Proposition without specifying the outcome. The model is the mechanism, not the value. Value is: 'reduces legal document review from 4 hours to 15 minutes with 95% accuracy.'" + sector_example: "An AI company providing automated medical image analysis uses the BMC to clarify its business model. Value Proposition: 'Detect pathologies in radiology images with >93% sensitivity, reducing radiologist reading time by 60%.' Key Resources: proprietary dataset of 10M+ labeled medical images (data moat), relationships with 200+ hospital partners (data pipeline), and FDA-cleared model (regulatory moat). Cost Structure: 60% compute (inference serving at scale), 25% data acquisition and labeling, 15% engineering. Revenue: per-scan pricing ($2-8/scan) creating natural usage-based expansion. The canvas reveals that gross margin depends entirely on inference cost optimization — the primary engineering priority." + benchmark_references: ["gross-margin-compute-adjusted", "inference-cost-per-request", "data-moat-index", "cost-per-prediction"] + + - skill: "four-ps-marketing" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "The Four Ps require AI-ML-specific adaptation. Product is a living model that changes with every training iteration — customers buy access to a capability that improves over time, not a static deliverable. Price in AI-ML has unique structures: per-API-call, per-token, per-prediction, per-outcome, tiered by model size/speed, or bundled as platform access. The pricing challenge is that inference cost scales with usage (variable COGS) while traditional software has near-zero marginal cost. Place (distribution) includes API marketplaces (Replicate, Hugging Face Inference Endpoints), cloud provider marketplaces (AWS Marketplace, Azure Marketplace), embedded integrations (SDK/plugin), and the open-source community as a distribution channel (freemium with open-source, paid for enterprise). Promotion for AI products emphasizes benchmark results, demo experiences, technical content, and developer community building over traditional B2B marketing." + sector_anti_patterns: + - "Pricing per API call when the value delivered varies 100x between calls. A legal AI that saves $10,000 on one query and $10 on another should not charge the same per call. Consider outcome-based or complexity-tiered pricing." + - "Marketing AI capabilities in abstract terms ('powered by AI') rather than concrete outcomes ('reduces claim processing from 3 days to 3 minutes with 97% accuracy'). Customers buy outcomes, not algorithms." + - "Ignoring the developer community as a distribution channel. For API products, developer adoption drives enterprise sales. Invest in documentation, tutorials, and developer relations." + sector_example: "An NLP company repositions using the Four Ps. Product: they separate the core extraction model from domain-specific fine-tuning as distinct product tiers. Price: they shift from flat-rate to per-document processing with a free tier of 100 documents/month (PLG) and enterprise tiers with volume discounts and priority inference. Place: they launch on AWS Marketplace and Hugging Face alongside their direct API, tripling distribution reach. Promotion: they publish benchmark results on standard NLP datasets and run a 'build with us' hackathon series, generating 500 new developer accounts per quarter." + benchmark_references: ["revenue-per-api-call", "inference-cost-per-request", "monthly-active-api-users"] + + - skill: "disruptive-innovation" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "Disruptive innovation in AI-ML follows two distinct patterns. First, open-source models disrupt proprietary models — Llama and Mistral offer 80-90% of GPT-4's quality at zero license cost, following the classic disruption pattern of 'good enough and free' displacing 'best and expensive.' Second, smaller specialized models disrupt larger general models — a 7B parameter model fine-tuned on medical data outperforms a 175B general model on medical tasks at 1/100th the inference cost. Both patterns threaten AI companies that rely on model scale as their primary advantage. The framework also applies to AI disrupting non-AI incumbents — AI-powered products entering traditional software categories (AI-native CRM, AI-native legal research, AI-native design tools)." + sector_anti_patterns: + - "Dismissing open-source models as inferior. Open-source is the disruptor in AI — it is 'worse' on benchmarks today but improves rapidly and costs nothing. This is textbook disruption." + - "Pursuing ever-larger models when the market is shifting toward efficient, specialized models. Foundation model scaling may have diminishing returns while fine-tuned small models capture specific use cases." + - "Building a thin AI wrapper on a foundation model API and treating it as a durable business. When the foundation model provider ships the same capability natively, the wrapper is disrupted overnight." + sector_example: "Stability AI disrupted proprietary image generation by open-sourcing Stable Diffusion — a model that was 'good enough' for most use cases and free. Midjourney and DALL-E had superior quality initially, but the open-source community rapidly closed the gap through fine-tuning, LoRA adapters, and community-generated training data. This forced proprietary providers to compete on quality at the frontier while losing the mid-market to open-source. The lesson: in AI, the open-source disruption cycle is measured in months, not years." + benchmark_references: ["model-accuracy-f1", "inference-cost-per-request", "data-moat-index"] + + - skill: "product-life-cycle" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "The product lifecycle in AI-ML compresses and fragments differently from traditional software. Introduction corresponds to research/prototype phase — the model proves feasibility but may lack production reliability. Growth corresponds to early customer adoption where the data flywheel begins — more usage improves the model, attracting more users. Maturity arrives when model accuracy plateaus and competitors reach parity — the commodity phase where differentiation shifts from model quality to data, integration, and pricing. Decline occurs when a new architecture or training paradigm renders the current model obsolete (e.g., transformers displacing RNNs, LLMs displacing purpose-built NLP models). Critically, individual model architectures have lifecycles within the product — a company may need to replace its model architecture while maintaining the product." + sector_anti_patterns: + - "Assuming model quality advantages are permanent. In AI, the lifecycle from innovation to commodity is 12-24 months, not 5-10 years. The accuracy advantage of today becomes the baseline of tomorrow." + - "Failing to distinguish product lifecycle from model lifecycle. The product (the customer-facing solution) can outlive multiple model generations — but only if the company invests in infrastructure that enables model swaps without customer disruption." + - "Ignoring the 'second model problem' — the assumption that the first model architecture will serve forever. Plan for model succession from the start." + sector_example: "OpenAI has navigated multiple model lifecycle transitions within a single product: GPT-2 (introduction), GPT-3 (growth), GPT-3.5 (early maturity, commoditized by open-source), GPT-4 (new growth cycle on a new architecture). Each model generation had its own lifecycle, but the product (ChatGPT, the API) provided continuity. Companies that built solely on GPT-3's capabilities without architecture-agnostic infrastructure were left behind when the paradigm shifted." + benchmark_references: ["model-accuracy-f1", "model-drift-rate", "model-deployment-frequency"] + + - skill: "balanced-scorecard" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "The Balanced Scorecard translates into AI-ML operating metrics across its four perspectives with distinctive differences from traditional SaaS. Financial: revenue per API call, gross margin (compute-adjusted), inference cost per request, burn rate. Customer: accuracy satisfaction, hallucination rate, latency SLAs, customer retention (AI-specific). Internal Process: model deployment frequency, A/B test win rate, data pipeline reliability, GPU utilization rate, time to fine-tune. Learning & Growth: research publication velocity, model architecture innovation, team ML skill depth, responsible AI maturity. The scorecard is particularly powerful for AI companies because it forces balance between model research (exciting) and operational excellence (necessary)." + sector_anti_patterns: + - "Measuring only model metrics (accuracy, F1) while ignoring business metrics (revenue, margin, retention). Many AI companies build excellent models that fail as businesses." + - "Ignoring the Learning & Growth perspective. AI companies that under-invest in research talent, architectural experimentation, and responsible AI maturity accumulate 'model debt' — technical debt specific to AI systems." + - "Tracking inference cost without connecting it to gross margin. Cost per prediction is meaningful only relative to revenue per prediction." + sector_example: "A Series A AI company implements a balanced scorecard with four KPIs per perspective: Financial (monthly revenue, gross margin, burn rate, NRR), Customer (accuracy satisfaction, hallucination rate, p95 latency, customer retention), Internal (deployment frequency, A/B test win rate, pipeline reliability, GPU utilization), Learning (research experiments per month, open-source contributions, responsible AI audit score, team ML certification rate). The scorecard reveals that the Customer perspective is strong (high accuracy, low latency) but the Financial perspective is weak (low gross margin due to unoptimized inference) — focusing engineering on inference cost reduction, not model quality." + benchmark_references: ["gross-margin-compute-adjusted", "model-accuracy-f1", "inference-cost-per-request", "model-deployment-frequency", "hallucination-rate"] + + - skill: "net-promoter-score" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "NPS for AI products must account for the unique relationship between model accuracy and customer satisfaction. Unlike traditional software where UX and features drive NPS, AI product NPS is dominated by one question: 'Does the model produce correct, reliable output for my use case?' This means NPS should be segmented by use case and by accuracy experience — a customer using the AI for low-stakes content generation may rate 9/10 while a customer using it for compliance review rates 3/10, even though they use the same product. NPS surveys should be triggered after accuracy-critical interactions, not on arbitrary schedules." + sector_anti_patterns: + - "Surveying NPS without tracking the customer's accuracy experience. A high NPS from users who only use simple features masks dissatisfaction from power users encountering edge cases." + - "Treating NPS promoters as undifferentiated. An AI product promoter who uses it for critical decisions is worth 10x in referral value compared to a casual user. Segment and prioritize." + - "Ignoring the trust dimension. AI product NPS declines sharply after a hallucination event, even if the model is 95%+ accurate. A single bad experience can override months of good ones." + sector_example: "An AI coding assistant segments NPS by programming language and finds dramatic variance: NPS 65 for Python users (where the training data is abundant) but NPS 15 for Rust users (where the model frequently generates incorrect syntax). This insight drives a targeted fine-tuning investment in Rust, improving NPS from 15 to 48 within one quarter. The unsegmented NPS of 50 never would have revealed the opportunity." + benchmark_references: ["customer-accuracy-satisfaction", "hallucination-rate", "customer-retention-ai"] + + - skill: "growth-share-matrix" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "The BCG Growth-Share Matrix maps to AI-ML product portfolios, where 'products' are often distinct model capabilities or vertical applications of the same underlying model. Stars are high-growth, high-share AI capabilities — the use cases where the model excels and demand is growing. Cash Cows are mature, well-monetized applications where the model is established. Question Marks are new capabilities or verticals where the model shows promise but market position is unproven. Dogs are model capabilities that consume compute and engineering without generating revenue — and in AI, these are especially expensive because inference cost is real. The matrix helps AI companies allocate compute and research resources across their model portfolio." + sector_anti_patterns: + - "Maintaining inference endpoints for 'Dog' model capabilities out of completeness rather than demand. In AI, unused model endpoints still cost money (GPU allocation) unlike unused software features." + - "Over-investing in Stars (high-growth capabilities) without building the MLOps infrastructure to sustain them at scale." + - "Ignoring the compute allocation dimension. Each model capability consumes GPU resources. The matrix should incorporate compute cost, not just revenue." + sector_example: "An NLP company maps its API capabilities: Sentiment Analysis (Cash Cow — mature, high revenue, well-optimized), Document Summarization (Star — rapidly growing, strong accuracy), Named Entity Recognition (Dog — commoditized, low revenue, open-source alternatives match quality), and Multi-language Translation (Question Mark — promising but unproven market position). The matrix drives a decision to deprecate the NER endpoint (saving GPU cost), invest in summarization (the Star), and pilot-test translation with select customers before committing compute." + benchmark_references: ["api-call-volume", "revenue-per-api-call", "inference-cost-per-request"] + + - skill: "swot-pest-analysis" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "SWOT and PEST analysis for AI-ML must address the unique environmental forces shaping the sector. Political: AI regulation is accelerating globally (EU AI Act, US executive orders, China's generative AI regulations). Economic: GPU supply constraints, compute cost volatility, and AI-specific investment cycles (the 2023-2024 AI funding surge). Social: public sentiment on AI (trust, fear, job displacement), developer community dynamics, and the open-source movement's philosophical influence on AI. Technological: architecture breakthroughs (transformers, diffusion models, mixture of experts), hardware evolution (NVIDIA roadmap, custom silicon), and the open-source model release cadence. SWOT must address the unique AI strengths (data moat, model quality, research team) and weaknesses (compute dependency, model opacity, hallucination risk)." + sector_anti_patterns: + - "Listing 'AI capabilities' as a strength without specificity. Every AI company has AI capabilities. The question is what specific model quality, data asset, or technical approach creates defensible advantage." + - "Ignoring regulatory risk in PEST. AI regulation is moving faster than most founders expect. The EU AI Act imposes real compliance costs on high-risk AI applications." + - "Underestimating the open-source threat in SWOT. Open-source models are both a threat (free substitutes) and an opportunity (build on top of open foundations)." + sector_example: "An AI company providing HR screening tools uses PEST to identify that the EU AI Act classifies employment-related AI as 'high risk,' requiring conformity assessments, transparency obligations, and human oversight mechanisms. The SWOT reveals that while they have strong accuracy (Strength), they lack explainability capabilities (Weakness) required by the regulation. The regulatory Threat is also an Opportunity — compliant AI solutions will have a competitive advantage as non-compliant alternatives are forced out of the EU market." + benchmark_references: ["responsible-ai-score", "model-accuracy-f1", "data-moat-index"] + + - skill: "scenario-planning" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "Scenario planning for AI-ML companies must account for uniquely high variance along three critical dimensions: model capability breakthroughs (a new architecture could make current models obsolete within months), compute availability (GPU supply constraints and pricing shifts), and regulatory intervention (AI regulation could reshape or eliminate markets). AI companies should maintain scenarios for: (1) Open-source catches up — a Llama-quality model matches your performance for free, (2) Compute crisis — GPU prices double or supply is constrained, (3) Regulatory shock — your AI use case is classified as high-risk with mandatory compliance costs. The planning horizon is shorter than traditional industries — 12-18 months is the practical limit given the pace of AI advancement." + sector_anti_patterns: + - "Ignoring the 'open-source replication' scenario. If a capable open-source model can replicate your core capability within 12 months, what is your response? Most AI companies cannot answer this question." + - "Treating compute cost as static. GPU pricing and availability are volatile. A scenario where inference costs double (or halve) should be in every AI company's planning." + - "Failing to plan for regulatory disruption. The EU AI Act, US executive orders, and sector-specific regulations are creating new compliance requirements that can render business models non-viable." + sector_example: "A generative AI startup builds three scenarios: (1) Base: current growth continues, open-source narrows the gap slowly, compute costs decline 20% annually. (2) Upside: a proprietary data partnership creates an insurmountable moat, enterprise adoption accelerates, and regulatory requirements favor established players. (3) Downside: Meta releases an open-source model that matches their quality, GPU costs spike due to supply constraints, and the EU AI Act requires costly compliance. For each scenario, they pre-commit strategic responses: in the downside, pivot to vertical specialization and on-premise deployment for regulated industries." + benchmark_references: ["data-moat-index", "inference-cost-per-request", "model-accuracy-f1"] + + - skill: "doblin-ten-types" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "AI-ML companies over-index on Product Performance innovation (better model accuracy) while ignoring the other nine types. The most powerful AI innovations often come from: Profit Model (usage-based pricing, outcome-based pricing, free-tier-to-enterprise), Network (model marketplace ecosystems, plugin architectures, data-sharing consortiums), Process (automated MLOps, continuous training pipelines), Channel (API-first distribution, open-source community, developer relations), and Service (fine-tuning-as-a-service, model customization, managed inference). The ten types framework reveals that model quality alone is insufficient — distribution, pricing, and service innovation determine commercial success." + sector_anti_patterns: + - "Believing that a better model is sufficient for commercial success. The AI graveyard is filled with superior models that lost to inferior models with better distribution, pricing, or developer experience." + - "Ignoring Profit Model innovation. The shift from flat-rate to usage-based to outcome-based pricing is a profit model innovation that can be more impactful than a 5% accuracy improvement." + - "Neglecting the Network type. AI products that connect to ecosystems (plugins, integrations, data pipelines) build switching costs that model quality alone cannot create." + sector_example: "Hugging Face's success maps across multiple innovation types beyond Product Performance. Profit Model: freemium for open-source hosting, paid for private models and inference. Network: the model hub creates network effects — more models attract more users, who contribute more models. Channel: developer community as distribution. Service: managed inference endpoints and enterprise deployment support. Customer Engagement: the Hugging Face community is a retention moat. Competitors with technically equivalent hosting infrastructure cannot replicate the community flywheel." + benchmark_references: ["monthly-active-api-users", "api-call-volume", "customer-retention-ai"] + + - skill: "trust-equation" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "Trust is the existential currency for AI-ML companies because customers grant models access to sensitive data and critical decisions. The Trust Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to AI as: Credibility = published benchmark results, third-party audits, responsible AI certifications, peer-reviewed research. Reliability = consistent model accuracy, uptime SLAs, predictable inference latency, low hallucination rate. Intimacy = understanding the customer's domain deeply enough to fine-tune for their specific needs, transparency about model limitations. Self-Orientation = avoiding overhyped accuracy claims, being transparent about failure modes, publishing model cards, and not locking customers into proprietary formats. The trust equation explains why enterprise AI adoption is slow despite impressive demos — organizations need all four components before deploying AI in critical workflows." + sector_anti_patterns: + - "Overhyping model capabilities (high Self-Orientation) to win initial adoption, then facing trust collapse when the model underperforms in production. Underpromise and overdeliver on accuracy." + - "Investing in Credibility (benchmark scores, logos, certifications) while neglecting Reliability (consistent performance, low hallucination, uptime). A model that scores well on benchmarks but halluccinates in production destroys trust." + - "Ignoring Intimacy — treating all customers as generic API consumers. AI products that understand and adapt to the customer's domain-specific needs build trust that general-purpose alternatives cannot match." + sector_example: "Anthropic built trust through a deliberate strategy across all four dimensions. Credibility: published research on Constitutional AI and responsible scaling. Reliability: consistent model behavior with strong safety properties. Intimacy: deep engagement with enterprise customers on domain-specific deployment. Low Self-Orientation: publicly acknowledging model limitations, publishing system cards, and avoiding capability overpromises. This trust profile enables adoption in regulated industries where competitors with higher benchmark scores but lower trust are rejected." + benchmark_references: ["hallucination-rate", "responsible-ai-score", "customer-accuracy-satisfaction"] + + - skill: "systems-thinking" + category: "frameworks" + ai_ml_relevance: "critical" + sector_context: "AI-ML businesses are complex adaptive systems with feedback loops that create non-obvious outcomes. The most important loops: (1) The data flywheel: more users generate more data, which improves the model, which attracts more users. This is the most powerful positive feedback loop in AI. (2) The accuracy-trust spiral: higher accuracy builds trust, which increases usage in critical workflows, which generates higher-quality data, which improves accuracy further. (3) The compute death spiral: growing usage increases inference cost, which pressures margins, which limits investment in optimization, which keeps costs high. (4) The open-source erosion loop: open-source models improve, which reduces willingness-to-pay, which pressures revenue, which limits R&D investment, which allows open-source to close the gap further. Systems thinking helps AI operators identify which loops are reinforcing and which are threatening." + sector_anti_patterns: + - "Optimizing model accuracy without modeling the cost implications. A 2% accuracy improvement that doubles inference cost may worsen unit economics more than it improves customer satisfaction." + - "Ignoring time delays in the data flywheel. The model does not improve immediately when new data arrives — there is a lag through labeling, training, evaluation, and deployment. Customers experience a delay between providing data and seeing improvement." + - "Treating the compute cost problem as an engineering problem alone. It is a systems problem: compute cost depends on model architecture, traffic patterns, pricing model, and customer mix. Changing one variable affects all others." + sector_example: "An AI company notices declining gross margins despite growing revenue. Systems analysis reveals a reinforcing loop: the product team ships larger models (more parameters) to improve accuracy benchmarks, which increases inference cost per request, which reduces margins, which creates pressure to grow revenue faster, which drives the sales team to acquire high-volume/low-value customers, which increases infrastructure load without proportional revenue, worsening margins further. The intervention point is not sales or engineering — it is the product team's model size decisions." + benchmark_references: ["gross-margin-compute-adjusted", "inference-cost-per-request", "data-moat-index", "model-accuracy-f1"] + + - skill: "smart-goals" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "SMART goals for AI-ML companies must balance research ambition (improve F1 score) with business discipline (reduce inference cost). The most common failure is setting model quality goals without cost or timeline constraints, or setting revenue goals without model quality prerequisites. Goals should span both dimensions: 'Achieve F1 > 0.92 on task X within 3 months while keeping inference cost below $0.005 per request' is a complete AI goal. 'Improve accuracy' is not. The Time-bound element is especially critical in AI — model research can expand indefinitely without a deadline." + sector_anti_patterns: + - "Setting accuracy goals without a business metric attached. 'Improve F1 from 0.88 to 0.92' is incomplete. 'Improve F1 from 0.88 to 0.92 to reduce customer-reported errors by 30% and decrease support ticket volume by 25%' connects model quality to business impact." + - "Setting goals that are Measurable but not Achievable — committing to accuracy levels that are not possible given available data and architecture." + - "Confusing model improvement goals with product goals. The customer does not care about F1 — they care about whether the product solves their problem. Frame goals in outcome terms." + sector_example: "An AI company sets Q2 goals: (1) Model: Reduce hallucination rate from 5% to 3% by expanding the factual grounding dataset by 2M examples and implementing retrieval-augmented generation. Measurement: automated hallucination detection on a 10K-sample evaluation set. (2) Business: Increase revenue per API call from $0.003 to $0.005 by launching a premium model tier with lower latency and higher accuracy. (3) Efficiency: Reduce inference cost from $0.002 to $0.0015 per request through model quantization and batching optimization. Each goal is specific, measurable, connected to a responsible team, and time-bound." + benchmark_references: ["hallucination-rate", "revenue-per-api-call", "inference-cost-per-request"] + + - skill: "cialdini-influence" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "Cialdini's six principles map distinctively to AI product adoption. Reciprocity: free API tiers and open-source model releases create obligation and community goodwill. Social Proof: benchmark leaderboard positions, published research citations, and enterprise logo walls. Commitment & Consistency: developers who integrate the API and build on top of it face escalating commitment — migration cost increases with usage. Authority: peer-reviewed research publications, partnerships with prestigious institutions, and contributions to open-source standards. Liking: developer community, responsive support, and a brand that signals competence without arrogance. Scarcity: early access to new models, limited compute allocation for priority customers, and waitlists that create demand signals." + sector_anti_patterns: + - "Relying on benchmark leaderboard positions (Authority) when developers evaluate on practical performance. Benchmarks are necessary but not sufficient — real-world accuracy on the customer's data is the deciding factor." + - "Using artificial Scarcity for API access as a long-term strategy. Waitlists create initial buzz but frustrate developers who switch to available alternatives." + - "Neglecting the Commitment dynamic in negative ways. Making it intentionally hard to migrate away (proprietary prompt formats, vendor-locked fine-tuned models) increases short-term retention but damages trust and brand." + sector_example: "OpenAI's developer adoption leveraged multiple principles: Reciprocity (free credits for startups), Social Proof (ChatGPT's viral adoption, enterprise logos), Commitment (developers built applications on the API, creating escalating switching costs), Authority (GPT-4's benchmark dominance, partnership with Microsoft), and Scarcity (GPT-4 waitlist, rate limits creating perceived exclusivity). The combination created a developer ecosystem that competitors struggle to replicate despite sometimes offering competitive model quality." + benchmark_references: ["monthly-active-api-users", "customer-retention-ai", "api-call-volume"] + + - skill: "eisenhower-matrix" + category: "frameworks" + ai_ml_relevance: "high" + sector_context: "AI-ML founders face extreme prioritization challenges because research, product, infrastructure, and business demands compete for attention. The Eisenhower Matrix must classify AI-specific priorities: accuracy improvements on known failure modes (Important but rarely Urgent), inference cost optimization (Important but deferred until margins compress), responsible AI compliance (Important and increasingly Urgent as regulation approaches), GPU procurement and capacity planning (Urgent and Important during supply constraints), and responding to competitive model releases (feels Urgent but is usually Not Important — reacting to every competitor release is a trap). The Not Urgent/Important quadrant — where data flywheel strategy, architecture research, and responsible AI framework development live — determines long-term competitive position." + sector_anti_patterns: + - "Treating every competitive model release as Urgent/Important. A competitor's announcement should rarely change your quarterly priorities. Build conviction in your own roadmap." + - "Perpetually deferring inference cost optimization. Compute cost is Not Urgent until it is a crisis — by which time gross margins have eroded significantly." + - "Classifying responsible AI work as Not Important because there is no immediate regulatory enforcement. The enforcement timeline is shorter than the compliance implementation timeline." + sector_example: "An AI company CEO uses the Eisenhower Matrix to discover that the research team's time is consumed by Urgent/Not Important demands: custom model fine-tuning for individual customers (should be automated), reproducing competitor benchmark results (should be delegated to a benchmarking pipeline), and ad-hoc data labeling quality reviews (should be systematized). Freeing the research team's capacity for Not Urgent/Important work — next-generation architecture research and systematic data quality improvement — accelerates the product roadmap by 40%." + benchmark_references: ["model-deployment-frequency", "inference-cost-per-request", "responsible-ai-score"] + + - skill: "vuca-framework" + category: "frameworks" + ai_ml_relevance: "moderate" + sector_context: "AI-ML operates in a permanently elevated VUCA state. Volatility: a single model release (GPT-4, Llama 3, Claude) can reshape the competitive landscape overnight. Uncertainty: no one knows which architecture will dominate in 3 years, whether regulation will fragment the market, or when compute costs will stabilize. Complexity: AI product decisions involve multi-variable trade-offs between accuracy, cost, latency, safety, and explainability. Ambiguity: strong benchmark results may not translate to production performance; 'AI product-market fit' is harder to define than traditional PMF. The VUCA framework clarifies which response is appropriate: Vision for Volatility (maintain strategic conviction through competitive noise), Understanding for Uncertainty (invest in understanding regulatory trajectories), Clarity for Complexity (simplify the accuracy-cost-latency trade-off into prioritized metrics), Agility for Ambiguity (iterate rapidly when the right answer is unknowable in advance)." + sector_anti_patterns: + - "Reacting to every competitive model release with strategic pivots. This mistakes Volatility for Ambiguity and responds with Agility when Vision is needed." + - "Using Ambiguity as a reason to defer responsible AI investment. 'We do not know what regulators will require' is not a valid reason for inaction — the broad strokes of regulation are predictable." + sector_example: "When Meta released Llama 2 as open-source, the VUCA framework clarified the response for a proprietary AI company. This was Volatility (sudden competitive shift) and Ambiguity (unclear how much enterprise market would shift to open-source). The response combined Vision (articulating why enterprise customers need managed, audited, SLA-backed models rather than raw open-source) with Agility (rapidly launching a Llama fine-tuning service to capture the open-source demand rather than fight it)." + benchmark_references: ["model-accuracy-f1", "data-moat-index"] + + # ───────────────────────────────────────────── + # AI-LEADERSHIP (6 skills) + # ───────────────────────────────────────────── + + - skill: "ai-vision-and-strategy" + category: "ai-leadership" + ai_ml_relevance: "critical" + sector_context: "For companies that build AI products, the ai-vision-and-strategy skill bridges from organizational AI adoption to AI product strategy. The vision must articulate not just 'how we use AI internally' but 'how our AI creates unique value for customers that alternatives (including open-source) cannot replicate.' The strategic framework must address: model differentiation (why is our model better for this task?), data strategy (how do we build and defend the data moat?), compute strategy (how do we manage the GPU supply chain and optimize inference cost?), and responsible AI strategy (how do we meet regulatory requirements while maintaining competitive speed?). For AI-ML companies, AI strategy IS business strategy — they are the same thing." + sector_anti_patterns: + - "Articulating AI vision in generic terms ('we are building the future of AI') rather than specific competitive terms ('our model outperforms alternatives on X task because of Y data advantage and Z architectural innovation')." + - "Separating AI strategy from business strategy. For AI-ML companies, model decisions ARE business decisions. The CTO's architecture choices directly determine unit economics." + - "Ignoring the responsible AI dimension of vision. Enterprise customers and regulators increasingly reject AI products without clear ethical guardrails, transparency mechanisms, and bias mitigation." + sector_example: "An AI company refines its vision from 'AI-powered document understanding' to 'the only document AI that achieves 97% extraction accuracy on regulatory filings because of our proprietary dataset of 50M annotated financial documents — a dataset that took 4 years to build and that competitors cannot replicate because the source institutions now have exclusive data partnerships with us.' This specificity transforms fundraising conversations, sales pitches, and team morale." + benchmark_references: ["data-moat-index", "model-accuracy-f1", "responsible-ai-score"] + + - skill: "ai-augmentation-not-automation" + category: "ai-leadership" + ai_ml_relevance: "critical" + sector_context: "For AI product companies, the augmentation-vs-automation design decision directly determines market size, pricing, liability, and regulatory burden. Fully automated AI (no human in the loop) faces higher accuracy requirements, stricter regulatory scrutiny, and greater liability exposure. Augmentation products (AI assists a human decision-maker) have lower accuracy thresholds, clearer liability models, and often achieve better outcomes through human-AI collaboration. The strategic question is not 'can the model automate this?' but 'should it?' Markets where human judgment is legally required (medical diagnosis, legal advice, financial underwriting) often yield better economics for augmentation products." + sector_anti_patterns: + - "Defaulting to full automation because it is technically impressive. The market for AI augmentation is often larger, more defensible, and higher-margin than the market for full automation." + - "Designing the product as fully automated and adding 'human-in-the-loop' as an afterthought for compliance. The augmentation experience must be designed from the beginning — not bolted on." + - "Ignoring the liability implications. A fully automated AI that makes a wrong decision faces product liability claims. An augmentation product that informs a human decision-maker has clearer liability boundaries." + sector_example: "Grammarly positioned as augmentation (suggesting corrections for human writers to accept or reject) rather than automation (rewriting text autonomously). This design choice enabled broader adoption (less threatening to users), lower accuracy requirements (suggestions are reviewed), and premium pricing (professional writers pay for a tool that enhances their work). Competitors offering fully automated content generation compete on price in a commodity race while Grammarly retains pricing power through the augmentation model." + benchmark_references: ["customer-accuracy-satisfaction", "hallucination-rate", "customer-retention-ai"] + + - skill: "ai-stakeholder-balance" + category: "ai-leadership" + ai_ml_relevance: "critical" + sector_context: "AI-ML companies face uniquely complex stakeholder balancing because the product's impact extends beyond customers to affected populations. Stakeholders include: customers (who buy and integrate the AI), end users (who interact with AI outputs, often different from the buyer), affected populations (people about whom the AI makes decisions — job applicants, loan recipients, content subjects), regulators (who set compliance frameworks), the research community (who evaluate and critique the model), investors (who fund development), and the open-source community (who may replicate or extend the model). Balancing these stakeholders requires explicit trade-off frameworks — optimizing for customer satisfaction may conflict with affected-population fairness." + sector_anti_patterns: + - "Prioritizing customer demands (accuracy on their data) while ignoring affected-population fairness (bias in the model's decisions about people). This creates regulatory and reputational liability." + - "Dismissing research community criticism as irrelevant. Academic scrutiny of AI model bias, safety, and limitations often predicts regulatory action by 12-24 months." + - "Treating responsible AI as a constraint rather than a feature. Enterprise customers increasingly require responsible AI compliance — it is a selling point, not just a cost." + sector_example: "An AI hiring platform must balance multiple stakeholders. Customers (employers) want the model to predict job performance accurately. Affected populations (job applicants) need fair treatment regardless of demographics. Regulators require explainability and non-discrimination. The research community scrutinizes for bias. By implementing demographic parity constraints and publishing model cards, the company loses marginal predictive accuracy but gains regulatory compliance, brand trust, and access to large enterprise customers whose procurement requires responsible AI certification." + benchmark_references: ["responsible-ai-score", "customer-accuracy-satisfaction", "data-moat-index"] + + - skill: "ai-learning-for-leaders" + category: "ai-leadership" + ai_ml_relevance: "high" + sector_context: "For AI-ML company leaders, this skill extends beyond 'learning about AI' to 'maintaining technical depth while managing a growing organization.' AI-ML CEOs face a unique challenge: they must remain fluent in model architecture decisions, understand inference optimization trade-offs, evaluate research proposals, and communicate with investors in business terms — simultaneously. The learning plan must include staying current with the research frontier (weekly paper review), understanding competitive model capabilities (regular benchmarking), and developing judgment about the accuracy-cost-speed trade-off triangle that governs every AI product decision." + sector_anti_patterns: + - "Delegating all technical judgment to the CTO. In AI-ML companies, the CEO must maintain enough technical fluency to evaluate strategic model decisions — architecture choices, build-vs-buy for foundation models, and the accuracy-cost trade-off." + - "Learning about AI from general media rather than from the research and engineering communities. General media coverage of AI is frequently inaccurate and overhyped." + - "Assuming that domain expertise (e.g., healthcare, legal) is sufficient without AI-native technical literacy. AI product leadership requires understanding both the domain AND the technology." + sector_example: "The CEO of a medical AI company establishes a learning protocol: weekly 30-minute review of new papers in medical imaging AI (maintaining technical edge), monthly deep-dive with the research team on model performance and architecture decisions, quarterly benchmarking against competitors and open-source alternatives, and bi-annual attendance at ML conferences (NeurIPS, ICML, or domain-specific events). This investment enables the CEO to articulate the technical moat credibly to investors, evaluate acquisition targets, and make informed build-vs-buy decisions." + benchmark_references: ["model-accuracy-f1", "ab-test-win-rate"] + + - skill: "ai-human-centered-approach" + category: "ai-leadership" + ai_ml_relevance: "high" + sector_context: "Human-centered AI design for AI product companies means designing the model's interaction with users to maximize trust, comprehension, and appropriate reliance. This includes: explainability (why did the model produce this output?), confidence calibration (how certain is the model, and does it communicate that accurately?), graceful failure modes (what happens when the model is wrong?), and user control (can the user override, correct, or train the model?). Human-centered design in AI is not a UX layer on top of the model — it must be designed into the model itself through calibrated confidence scores, interpretable features, and user feedback loops." + sector_anti_patterns: + - "Treating the model as a black box that users must accept or reject wholesale. Users need to understand why the model made a recommendation to trust it for important decisions." + - "Over-reporting model confidence. A model that says it is 95% confident on every prediction, even when it is wrong, destroys trust faster than one that appropriately expresses uncertainty." + - "Designing error correction as an afterthought. Users will encounter model errors. The question is whether they can correct the error, whether the correction improves future predictions, and whether the correction experience is frustrating or empowering." + sector_example: "A legal AI product implements human-centered design by showing confidence scores alongside each contract clause analysis, highlighting the specific text that drove each assessment, and providing a one-click correction mechanism when lawyers disagree. The corrections feed back into the fine-tuning pipeline — the more lawyers use and correct the tool, the better it becomes for their specific contract types. This design creates a virtuous cycle: human-centered interaction generates the training data that improves the model." + benchmark_references: ["customer-accuracy-satisfaction", "hallucination-rate", "customer-retention-ai"] + + - skill: "ai-communication-culture" + category: "ai-leadership" + ai_ml_relevance: "high" + sector_context: "Communication culture in AI-ML companies must bridge the language gap between research (which speaks in loss functions, architectures, and benchmark scores) and business (which speaks in revenue, margin, and customer outcomes). The most common communication failure in AI companies is a research team that cannot articulate business impact and a business team that cannot evaluate research proposals. Building a shared vocabulary — where 'F1 improved by 3%' is immediately translated to 'customer-reported accuracy complaints will decrease by approximately 20%' — is a leadership priority. External communication adds another layer: explaining AI capabilities honestly without overpromising or using inaccessible jargon." + sector_anti_patterns: + - "Allowing the research team to communicate solely in technical metrics that the rest of the organization cannot interpret. Model improvement must be translated into business impact." + - "External communications that overhype model capabilities. 'Our AI is superintelligent' creates expectations the product cannot meet, leading to trust collapse." + - "Failing to communicate model limitations to customers. Honest limitation disclosure builds trust and prevents misuse that damages both the customer and the brand." + sector_example: "An AI company establishes a communication protocol: every model improvement report includes three sections — Technical (architecture change, benchmark delta), Business (expected impact on customer accuracy satisfaction, support ticket volume, and retention), and Risk (new failure modes introduced, edge cases degraded, responsible AI implications). This structure ensures that every stakeholder understands research outcomes in their own terms. External model release announcements follow the same structure: capability, limitation, recommended use case." + benchmark_references: ["customer-accuracy-satisfaction", "model-accuracy-f1"] + + # ───────────────────────────────────────────── + # NEGOTIATION (4 skills) + # ───────────────────────────────────────────── + + - skill: "competitive-negotiation" + category: "negotiation" + ai_ml_relevance: "high" + sector_context: "Competitive negotiation for AI-ML companies occurs across three primary contexts: enterprise sales (negotiating model deployment terms, data handling agreements, accuracy SLAs, and liability frameworks), fundraising (negotiating valuation in the context of AI hype cycles, technical differentiation, and data moat strength), and compute procurement (negotiating GPU allocation, cloud contracts, and hardware supply agreements with providers who hold enormous leverage). The AI-specific wrinkle in enterprise sales is that customers demand accuracy guarantees that the model may not consistently deliver — navigating between competitive pressure to promise high accuracy and the risk of contractual liability for model errors." + sector_anti_patterns: + - "Guaranteeing specific accuracy levels in contracts without robust measurement methodology and appropriate caveats. A contractual promise of '99% accuracy' on a vaguely defined task is a lawsuit waiting to happen." + - "Negotiating compute contracts on spot pricing alone. Reserved instances, committed use discounts, and multi-cloud strategies provide leverage against single-provider dependency." + - "In fundraising, anchoring on AI company valuations from the 2023-2024 hype peak rather than demonstrating sustainable unit economics." + sector_example: "An AI company negotiating a $500K enterprise deployment faces the customer's demand for a '99% accuracy SLA.' Rather than accepting or rejecting, the sales team reframes: the contract specifies accuracy on a jointly-defined evaluation set (avoiding ambiguity), includes a 90-day pilot with measured accuracy (reducing customer risk), ties pricing to measured performance (aligning incentives), and excludes edge cases that both parties agree are out-of-scope (preventing unreasonable expectations). This approach closes the deal at higher ACV than a blanket guarantee because it demonstrates confidence and professionalism." + benchmark_references: ["model-accuracy-f1", "customer-accuracy-satisfaction", "inference-cost-per-request"] + + - skill: "cooperative-negotiation" + category: "negotiation" + ai_ml_relevance: "high" + sector_context: "Cooperative negotiation is the foundation of AI-ML data partnerships, model integration agreements, and the compute supply chain relationships that define the business. AI-specific cooperative negotiations include: data partnerships (accessing proprietary training data from domain experts — hospitals, law firms, financial institutions), model integration partnerships (embedding your model into another company's product), compute partnerships (negotiating favorable GPU access with cloud providers or hardware manufacturers), and academic collaborations (accessing research talent and pre-publication model improvements). The cooperative dimension is especially important because AI products often require resources (data, compute, research talent) that cannot be obtained through purely commercial transactions." + sector_anti_patterns: + - "Treating data partnerships as simple procurement. Data providers (hospitals, financial institutions) need to understand how their data will be used, protected, and how they benefit from model improvements. This is a trust-building exercise, not a purchasing transaction." + - "Entering compute partnerships without multi-cloud optionality. Dependency on a single compute provider is a strategic vulnerability that cooperative negotiation should address, not create." + - "Neglecting the cooperative dimension of open-source relationships. Contributing to open-source communities generates goodwill, recruitment advantages, and ecosystem influence that purely proprietary strategies cannot replicate." + sector_example: "An AI company negotiating a data partnership with a hospital network uses cooperative framing: the hospital provides de-identified imaging data; in return, the AI company provides the hospital with free access to the trained model, co-authorship on publications, and a revenue share on commercial deployments. The cooperative structure aligns incentives — the hospital actively improves data quality because it benefits from model accuracy. A purely transactional 'pay for data' approach would have yielded lower-quality data and a shorter-term relationship." + benchmark_references: ["data-acquisition-cost", "data-moat-index", "model-accuracy-f1"] + + - skill: "delivering-the-deal" + category: "negotiation" + ai_ml_relevance: "high" + sector_context: "Deal execution in AI-ML has unique complexities: enterprise procurement now includes AI-specific due diligence (model auditing, bias testing, data handling reviews), security review extends to model security (adversarial robustness, data extraction prevention), and legal review covers novel territory (AI liability, IP ownership of model outputs, data processing agreements for training data). The 'deal acceleration kit' for AI companies must include: model cards (standardized documentation of capabilities and limitations), responsible AI documentation (bias reports, fairness metrics, safety evaluations), data processing agreements (how customer data is used for inference, whether it is used for training), and SLA frameworks (accuracy, latency, uptime with clear measurement methodology)." + sector_anti_patterns: + - "Treating AI-specific due diligence as an obstacle rather than a competitive advantage. Companies with pre-prepared model documentation close enterprise deals faster than those who scramble to answer each question ad hoc." + - "Allowing the accuracy SLA discussion to block the deal. Offer pilot periods with measured accuracy rather than pre-deployment guarantees." + - "Ignoring the data processing question. Enterprise customers will ask: 'Does our data train your model?' The answer must be clear, contractual, and honest. Ambiguity kills deals." + sector_example: "An AI company creates an 'AI deal acceleration kit': published model cards for each product, a responsible AI white paper (bias audit results, fairness metrics, safety evaluations), a pre-approved DPA that addresses both inference data handling and training data policies, and a standardized SLA framework with accuracy, latency, and uptime tiers. This kit reduces average enterprise sales cycle from 120 to 65 days by eliminating the three most common stall points: 'How does your model work?' (model card), 'Is it biased?' (responsible AI documentation), and 'What happens to our data?' (DPA)." + benchmark_references: ["responsible-ai-score", "model-accuracy-f1", "customer-retention-ai"] + + - skill: "negotiation-mindset-and-self" + category: "negotiation" + ai_ml_relevance: "moderate" + sector_context: "AI-ML founders negotiate from a uniquely complex psychological position: the AI hype cycle amplifies both overconfidence (inflated valuations, overpromised capabilities) and insecurity (open-source catching up, competitors with bigger compute budgets). The negotiation mindset must manage these dynamics. In fundraising, founders must navigate the AI premium in valuations without anchoring on hype-cycle multiples that may not persist. In enterprise sales, founders must balance technical honesty about model limitations with commercial confidence in the product's value. In compute procurement, founders negotiate with suppliers (NVIDIA, cloud providers) who hold enormous leverage during GPU shortages." + sector_anti_patterns: + - "Allowing AI hype to inflate fundraising expectations. A 100x ARR valuation justified by 'AI premium' is a liability when the premium normalizes." + - "Internalizing the compute provider's leverage as permanent. GPU supply constraints are cyclical. Negotiate with the long-term view, not current scarcity." + - "Feeling inferior when negotiating with well-funded competitors. If your model serves a customer's need better, funding level is irrelevant." + sector_example: "An AI founder entering Series A negotiations recognizes the psychological dynamic: the VC alternates between expressing excitement about AI's potential (creating euphoria) and grilling on unit economics (creating anxiety). By preparing for this pattern, the founder maintains composure through both phases. When the VC questions compute-adjusted gross margins, the founder responds with data rather than defensiveness — showing the margin improvement trajectory from 45% to 65% over 12 months as inference optimization compounds. The calm response to the hardest question becomes the strongest fundraising signal." + benchmark_references: ["gross-margin-compute-adjusted", "data-moat-index"] + + # ───────────────────────────────────────────── + # GAME THEORY (3 skills) + # ───────────────────────────────────────────── + + - skill: "game-theory-fundamentals" + category: "game-theory" + ai_ml_relevance: "high" + sector_context: "Game theory is deeply relevant to AI-ML competitive dynamics because the industry features multiple interacting strategic games. The open-source vs. proprietary game: Meta's decision to open-source Llama reshaped the industry by commoditizing the model layer, forcing proprietary competitors to differentiate on data, fine-tuning, and enterprise services rather than model quality alone. The compute allocation game: GPU-scarce environments create allocation games where cloud providers choose which customers get access, and AI companies compete for hardware allocation. The pricing game: AI API pricing creates Bertrand-style price competition where marginal cost of inference sets the floor and the open-source alternative sets the ceiling." + sector_anti_patterns: + - "Ignoring the open-source game. Whether or not you participate in open-source, your strategy must account for the possibility that competitors will open-source models equivalent to yours." + - "Treating compute procurement as a simple market transaction. GPU allocation involves strategic behavior — cloud providers favor certain customers, and multi-year commitments create lock-in games." + - "Engaging in price wars with commodity inference providers. If your model is not differentiated, a pricing game converges on marginal inference cost — a game no startup can win against cloud providers." + sector_example: "Meta's decision to open-source Llama is a classic game-theoretic move: by commoditizing the model layer (making it free), Meta undermined the business model of competitors who sell model access (OpenAI, Anthropic), shifted the value to compute infrastructure (where Meta has advantages in custom hardware), and created an ecosystem of developers building on Llama (increasing Meta's influence). Understanding this game helps AI companies respond: differentiate on the non-commoditized layers (data, fine-tuning, enterprise trust) rather than fighting on the commoditized layer (base model quality)." + benchmark_references: ["data-moat-index", "model-accuracy-f1", "inference-cost-per-request"] + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + ai_ml_relevance: "high" + sector_context: "The Prisoner's Dilemma framework applies directly to AI-ML industry dynamics. AI safety cooperation: individual companies benefit from cutting safety corners (faster to market) but collective defection creates regulatory backlash that harms everyone — a classic multi-player Prisoner's Dilemma. Data sharing: companies in a vertical (e.g., healthcare AI) would all benefit from pooling anonymized data (larger dataset, better models), but each fears sharing proprietary advantage — another Prisoner's Dilemma. Open-source contribution: contributing models and tools benefits the ecosystem but potentially helps competitors. Platform dependency: building on a cloud provider's AI platform cooperates with the provider but risks the provider later competing directly." + sector_anti_patterns: + - "Framing every competitive interaction as zero-sum. Many AI industry dynamics are positive-sum — data consortiums, safety collaborations, and standard-setting benefit all participants." + - "Defecting on AI safety (cutting corners on responsible AI) for short-term competitive advantage. The collective consequence of industry-wide safety defection is regulatory intervention that constrains everyone." + - "Refusing to engage with open-source because it helps competitors. Selective open-source contribution builds ecosystem influence, attracts talent, and can strategically commoditize layers where competitors have advantages." + sector_example: "The AI safety cooperation game is a textbook multi-player Prisoner's Dilemma. Each AI company faces a choice: invest in safety research and responsible AI (cooperate) or skip safety to ship faster (defect). If all cooperate, the industry maintains public trust and light regulation. If one defects, it gains a short-term speed advantage. If all defect, a major AI failure triggers heavy regulation that constrains the entire industry. Anthropic, Google DeepMind, and OpenAI have partially addressed this through the Frontier Model Forum — a cooperation mechanism that aligns incentives, though enforcement remains weak." + benchmark_references: ["responsible-ai-score", "data-moat-index"] + + - skill: "first-mover-strategy" + category: "game-theory" + ai_ml_relevance: "high" + sector_context: "First-mover dynamics in AI-ML are distinctive because the traditional first-mover advantage (brand, network effects, learning curve) is complicated by rapid model improvement that can leapfrog incumbents. The data flywheel creates a first-mover advantage: early movers accumulate more data, which improves their model, which attracts more users, which generates more data. But this advantage is fragile if a competitor achieves a model architecture breakthrough or if open-source narrows the gap. First-mover advantage in AI is strongest in: data accumulation (the flywheel), customer relationships and trust (enterprise switching costs), regulatory compliance (first-to-comply in regulated verticals), and developer ecosystem (network effects from API adoption). It is weakest in: model quality (rapidly commoditized) and brand (less durable in technical markets)." + sector_anti_patterns: + - "Assuming that being first to market with an AI model creates a permanent advantage. Model quality advantages erode in 6-12 months as competitors train on equivalent data and architecture." + - "Spending on brand-building rather than data moat-building in the first-mover period. The window for accumulating proprietary data is limited — once competitors establish competing data pipelines, the first-mover data advantage narrows." + - "Ignoring fast-follower dynamics in AI. OpenAI was first-to-market with a consumer-facing LLM, but Anthropic, Google, and Meta followed within months with competitive products." + sector_example: "OpenAI's first-mover advantage with ChatGPT illustrates the pattern: the data advantage (user interactions for RLHF) and developer ecosystem (API integrations) created durable advantages, while the model quality advantage (GPT-4's lead) was transient — competitors narrowed the gap within 12 months. The lesson for AI companies: invest the first-mover window in building the flywheel (data, ecosystem, trust) rather than resting on the model quality lead." + benchmark_references: ["data-moat-index", "monthly-active-api-users", "customer-retention-ai"] + + # ───────────────────────────────────────────── + # THINKING (2 skills) + # ───────────────────────────────────────────── + + - skill: "enemies-of-clear-thinking" + category: "thinking" + ai_ml_relevance: "critical" + sector_context: "AI-ML operators face specific cognitive traps amplified by the hype-laden, technically complex, and rapidly evolving nature of the industry. Survivorship bias: benchmarking against OpenAI and Anthropic while ignoring the hundreds of AI companies that failed. The AI hype effect: confirmation bias where every customer conversation is interpreted as validation because 'AI is the future.' Anchoring on benchmarks: fixating on leaderboard scores rather than production performance on actual customer data. Sunk cost fallacy: continuing to invest in a model architecture or dataset because of past expenditure rather than future potential. Authority bias: deferring to the research team's technical preferences when business requirements should drive architecture decisions. Availability bias: over-weighting the most recent AI breakthrough announcement." + sector_anti_patterns: + - "Using benchmark scores as the primary success metric when customers evaluate on real-world accuracy. A model that ranks #1 on a benchmark but fails on production edge cases is a liability, not an asset." + - "Anchoring on the AI valuation premium. Investors fund AI companies at high multiples during hype cycles — anchoring on these multiples creates unrealistic expectations for fundraising and exit." + - "Confusing model improvement with product improvement. The fact that F1 improved by 2% does not mean customers noticed. Clear thinking demands connecting model metrics to customer outcomes." + sector_example: "An AI company CEO reviews metrics and concludes the business is strong: accuracy is above 0.90 F1, API call volume is growing 15% MoM, and enterprise pipeline is $2M. An advisor trained in clear thinking spots hidden issues: F1 is measured on the original evaluation set (not updated to reflect current production distribution), volume growth is driven by a single customer's batch job, and the $2M pipeline includes $1.5M from a single prospect that has been 'evaluating' for 6 months. Each metric tells a flattering story that clear examination reveals to be misleading." + benchmark_references: ["model-accuracy-f1", "api-call-volume", "customer-accuracy-satisfaction"] + + - skill: "defining-and-exploring-problems" + category: "thinking" + ai_ml_relevance: "high" + sector_context: "AI-ML companies face a unique problem-definition challenge: the technology is so powerful that it can be applied to thousands of problems, but the business can only serve a few well. The most common failure mode is solving a technically interesting problem that customers do not value, or solving a problem that AI solves well but that customers were not bothered by in the first place. Problem definition must answer: (1) Is this a problem that justifies AI (accuracy requirements, data availability, scale of decisions)? (2) Is the customer's pain significant enough to pay for AI (not just better, but dramatically better than alternatives)? (3) Can AI solve this problem reliably enough to deploy (not just demos, but production accuracy on edge cases)?" + sector_anti_patterns: + - "Starting with 'we have a great model' and searching for a problem to apply it to. The model is a solution — the problem must come first." + - "Defining the problem as 'automation' when the real problem is 'better decisions.' Framing determines whether the product is an augmentation tool (higher value, lower risk) or an automation system (lower value, higher liability)." + - "Confusing a demo-able problem with a deployable problem. Many AI applications work impressively in demos but fail on production edge cases. The problem definition must include production accuracy requirements." + sector_example: "An AI team builds a model that can summarize legal documents with 85% accuracy on standard benchmarks. Before building the product, they apply rigorous problem definition: Is 85% accuracy sufficient? (No — lawyers need 99%+ for material terms.) Is the pain real? (Yes — junior lawyers spend 40% of their time on document review.) Can the accuracy gap be closed? (Yes, with domain-specific fine-tuning and human-in-the-loop validation for high-risk clauses.) This analysis reframes the product from 'automated legal summary' to 'AI-assisted legal review with human validation on critical clauses' — a fundamentally different and more viable product." + benchmark_references: ["model-accuracy-f1", "customer-accuracy-satisfaction"] + + # ───────────────────────────────────────────── + # LEADERSHIP (2 skills) + # ───────────────────────────────────────────── + + - skill: "strategic-thinking-and-alignment" + category: "leadership" + ai_ml_relevance: "high" + sector_context: "Strategic alignment in AI-ML companies is structurally harder than in traditional software because the research team, product team, and business team often have fundamentally different optimization objectives. Research optimizes for model quality (accuracy, novel architecture). Product optimizes for user experience (latency, reliability, features). Business optimizes for revenue and margins (pricing, cost reduction, enterprise requirements). Misalignment manifests as: the research team builds a beautiful model that is too expensive to serve, the product team ships features that the model cannot reliably support, or the business team commits to SLAs that engineering cannot meet. Strategic alignment requires a shared framework that connects model quality to business outcomes." + sector_anti_patterns: + - "Allowing the research team to optimize accuracy without a cost constraint. 'Build the best model' without 'within this inference cost budget' leads to impressive benchmarks and negative gross margins." + - "Letting the business team commit to accuracy SLAs without input from the research team. Promising what the model cannot deliver creates a trust deficit that compounds." + - "Running separate planning processes for research, product, and business. In AI companies, these must be integrated — a model architecture decision is simultaneously a product decision and a business decision." + sector_example: "An AI company implements 'model-aware OKRs' — every quarterly objective must specify three dimensions: the business outcome (e.g., reduce customer-reported errors by 20%), the model metric (e.g., improve F1 from 0.88 to 0.91 on the error-prone task subset), and the cost constraint (e.g., within the current inference cost budget of $0.003/request). This triple-constraint framework forces research, product, and business alignment at the goal-setting stage rather than discovering misalignment at the end of the quarter." + benchmark_references: ["model-accuracy-f1", "gross-margin-compute-adjusted", "customer-accuracy-satisfaction"] + + - skill: "leading-through-change" + category: "leadership" + ai_ml_relevance: "high" + sector_context: "AI-ML companies undergo change at a pace unmatched in other technology sectors. Model architecture transitions (replacing the core model), pivot from research to product (commercializing research capabilities), open-source response (adapting strategy when a competitor open-sources a comparable model), regulatory compliance (implementing responsible AI frameworks), and compute migration (switching cloud providers or hardware) all represent change events that require leadership. The unique challenge is that AI change often involves replacing the core intellectual property — the model itself — while maintaining customer trust and team morale. Leading through a model transition requires communicating that the old work was not wasted while building conviction in the new direction." + sector_anti_patterns: + - "Announcing a model architecture change without communicating the business rationale. The team needs to understand why the old model is being replaced and how the new architecture serves the business strategy." + - "Treating regulatory compliance as an external imposition rather than a strategic opportunity. Leading through AI regulation change means framing compliance as a competitive advantage." + - "Managing open-source disruption by dismissing the threat. If a credible open-source alternative appears, the team needs honest assessment and a clear response strategy." + sector_example: "When a competing AI company open-sourced a model matching 90% of their proprietary model's accuracy, the CEO led through the change by: (1) acknowledging the threat honestly in an all-hands meeting, (2) reframing the competitive advantage around the 10% accuracy gap in specific enterprise use cases, the proprietary data flywheel, and the enterprise trust infrastructure (compliance, SLAs, support), and (3) launching a 90-day initiative to build features that open-source cannot replicate (customer-specific fine-tuning, managed deployment, regulatory compliance). The honest, action-oriented response prevented panic and focused the team on defensible differentiation." + benchmark_references: ["data-moat-index", "model-accuracy-f1", "customer-retention-ai"] diff --git a/plugins/foreman/content/industry-packs/ai-ml/ai-ml-templates.yaml b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-templates.yaml new file mode 100644 index 0000000..376c36e --- /dev/null +++ b/plugins/foreman/content/industry-packs/ai-ml/ai-ml-templates.yaml @@ -0,0 +1,1003 @@ +# AI-ML Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for AI-ML companies — companies whose core product IS +# an AI/ML system. The output agent loads these rules when generating +# documents with the AI-ML industry pack active. +# +# Key adaptation themes: +# - Unit economics: per-inference economics (compute + data + infrastructure = cost per prediction) +# - Investor materials: model differentiation, data moat, responsible AI, compute strategy +# - Technical templates: model performance dashboard, A/B test results, data pipeline health +# - Customer materials: accuracy reporting, model transparency, responsible AI commitments +# +# Adaptation types: +# as-is — The template works without modification for AI-ML companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for AI-ML context. + +pack_metadata: + sector: "ai-ml" + display_name: "AI-ML" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML unit economics differ fundamentally from SaaS. The cost per unit of value delivered includes inference compute, training cost amortization, data pipeline costs, and GPU infrastructure — all of which scale with usage rather than being near-zero marginal cost." + field_changes: + - field: "Revenue per unit" + sector_label: "Revenue per Prediction / API Call" + sector_guidance: "Report revenue per inference request (or per 1K tokens for LLM products). Decompose by model tier (standard, premium, enterprise) and by use case if pricing varies. Include the volume trend — are customers making more calls per account over time?" + - field: "Cost per unit" + sector_label: "Fully Loaded Cost per Prediction" + sector_guidance: "Include all variable costs: inference compute (GPU cost per request), data processing (feature computation), third-party API costs (if calling external models), allocated infrastructure (serving, monitoring, logging), and allocated support. This is AI COGS — treat it as such." + - field: "Margin per unit" + sector_label: "Per-Prediction Gross Margin" + sector_guidance: "Revenue per prediction minus cost per prediction. AI-ML companies typically achieve 50-70% gross margin per prediction — lower than SaaS (70-85%) due to compute COGS. Show the trajectory: is margin improving with scale and optimization?" + - field: "Lifetime value" + sector_label: "Customer LTV (Usage-Adjusted)" + sector_guidance: "Calculate as Average Monthly Revenue per Customer x Gross Margin x Average Customer Lifetime (months). For usage-based AI products, account for usage growth within accounts — expanding customers have higher LTV than the initial run-rate suggests." + - field: "Acquisition cost" + sector_label: "CAC and Integration Cost" + sector_guidance: "Include both traditional CAC (sales and marketing cost per acquired customer) and the integration cost (technical onboarding, API integration support, initial fine-tuning). AI products often have higher onboarding costs than SaaS due to model customization requirements." + - field: "Unit economics ratio" + sector_label: "LTV:CAC Ratio (Usage-Adjusted)" + sector_guidance: "Report the ratio with explicit disclosure of the LTV calculation methodology. For AI products with growing per-customer usage, the standard LTV formula may understate actual lifetime value. Show both static and expanding-usage LTV:CAC." + sections_to_add: + - section_name: "AI-ML Cost Structure" + placement: "before:Revenue per Prediction / API Call" + description: "Decomposition of the AI-specific cost structure that investors evaluate." + fields: + - "Inference compute cost (percentage of COGS)" + - "Training cost (amortized per period — R&D or COGS classification)" + - "Data acquisition and labeling cost (per period)" + - "GPU infrastructure cost (reserved, on-demand, spot breakdown)" + - "Third-party API costs (if using external foundation models)" + - "Gross margin trajectory (12-month chart)" + - section_name: "Per-Prediction Economics" + placement: "after:Per-Prediction Gross Margin" + description: "The granular economics of each model invocation." + fields: + - "Revenue per prediction by model tier" + - "Cost per prediction by model tier" + - "Margin per prediction by model tier" + - "Volume by model tier (monthly)" + - "Cost optimization trajectory (cost per prediction over time)" + - section_name: "Data Flywheel Economics" + placement: "end" + description: "The economics of the data moat — how product usage reduces data cost and improves model quality over time." + fields: + - "Data acquisition cost trend (declining? through product usage?)" + - "Model quality improvement from product-generated data (measured)" + - "Estimated replication cost for a competitor to build an equivalent dataset" + sections_to_remove: [] + benchmark_references: ["inference-cost-per-request", "cost-per-prediction", "revenue-per-api-call", "gross-margin-compute-adjusted", "data-acquisition-cost"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML investor updates must report both business metrics and model metrics. Investors want to see model quality alongside revenue, inference cost alongside growth, and data moat progression alongside customer acquisition." + field_changes: + - field: "Financial highlights" + sector_label: "AI Business Metrics" + sector_guidance: "Report: Monthly Revenue, Revenue Growth (MoM), API Call Volume (and growth), Gross Margin (compute-adjusted), Burn Rate, Runway. Present as a compact table with current month, prior month, and trend direction." + - field: "Key metrics" + sector_label: "Model and Product Metrics" + sector_guidance: "Report: Model accuracy (F1 or domain-appropriate metric), Hallucination rate (if generative), Inference latency (p50/p95), Customer accuracy satisfaction, Active API users. Choose the 3-5 metrics most relevant to current priorities." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one model improvement win and one business win. Model: 'Reduced hallucination rate from 5% to 3% through RAG implementation.' Business: 'Closed [Customer] at $X ACV for [use case].'" + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Be transparent about AI-specific challenges: model quality limitations, inference cost pressure, competitive model releases, or regulatory developments. Investors expect AI-specific risks to be called out honestly." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "AI-specific asks: introductions to potential data partners, enterprise customers in target verticals, ML infrastructure advisors, or responsible AI experts. Be concrete — specify the domain and the reason." + sections_to_add: + - section_name: "Model Progress" + placement: "after:Model and Product Metrics" + description: "Brief model improvement summary that demonstrates the data flywheel and research velocity." + fields: + - "Key model improvement this month (metric and method)" + - "Data flywheel status (new data volume from product usage)" + - "Competitive position (how the model compares to alternatives)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "inference-cost-per-request", "gross-margin-compute-adjusted"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML competitive landscape includes five distinct threat vectors that do not exist in traditional software: direct competitors, foundation model providers, open-source models, cloud providers, and in-house ML teams. The brief must address all five." + field_changes: + - field: "Competitor overview" + sector_label: "AI Competitive Map" + sector_guidance: "Map all five competitor types on a 2x2 matrix: X-axis = general-purpose to domain-specific, Y-axis = open-source to proprietary. Position your product, direct competitors, foundation model providers (OpenAI, Anthropic, Google), relevant open-source models (Llama, Mistral, Stable Diffusion), and cloud AI services. Include model accuracy comparison where available." + - field: "Competitive advantages" + sector_label: "AI Defensibility Analysis" + sector_guidance: "Assess defensibility along AI-specific dimensions: data moat (proprietary training data), model quality (accuracy gap over alternatives), distribution moat (API ecosystem, integration depth), regulatory moat (compliance certifications), and trust moat (responsible AI posture, brand credibility)." + - field: "Competitive threats" + sector_label: "Five Threat Vectors" + sector_guidance: "Categorize: (1) Direct AI competitors — same domain, same approach. (2) Foundation model providers — OpenAI/Anthropic/Google adding your capability natively. (3) Open-source models — free alternatives reaching comparable quality. (4) Cloud providers — AWS/GCP/Azure offering competing managed AI services. (5) In-house build — customers building with open-source rather than buying." + sections_to_add: + - section_name: "Model Quality Comparison" + placement: "after:Five Threat Vectors" + description: "Objective accuracy comparison against alternatives." + fields: + - "Accuracy comparison table (your model vs. competitors vs. open-source vs. foundation models on relevant benchmarks)" + - "Domain-specific evaluation results (on customer-representative data, not just public benchmarks)" + - "Accuracy trend (is the gap widening or narrowing?)" + - section_name: "Open-Source Threat Assessment" + placement: "after:Model Quality Comparison" + description: "Specific assessment of open-source model alternatives and the defensibility against free substitutes." + fields: + - "Best open-source model accuracy on your core task" + - "Accuracy gap between your model and best open-source alternative" + - "Gap trajectory (closing, stable, or widening)" + - "Value-add beyond model quality (enterprise features, support, compliance, SLA) that justifies pricing premium over open-source" + - section_name: "Foundation Model Risk" + placement: "end" + description: "Assessment of the risk that OpenAI, Anthropic, Google, or Meta ships your core capability as a feature." + fields: + - "Overlap between your core capability and foundation model roadmaps" + - "Domain depth required (does your use case need specialization beyond general models?)" + - "Integration and workflow depth (are you embedded in customer workflows beyond what an API switch could replace?)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index", "inference-cost-per-request"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML fundraising decks must address AI-specific investor questions: What is the moat? How durable is the data advantage? Can you achieve SaaS-like margins? What is the responsible AI posture? How do you compete with open-source? The deck must balance technical credibility with business storytelling." + field_changes: + - field: "Market opportunity" + sector_label: "AI Market Opportunity" + sector_guidance: "Present the market through an AI lens: current spend on the problem being solved (manual processes, legacy software), the AI-addressable portion, and the adoption curve. Include the specific accuracy threshold that makes AI viable for this market and evidence that your model crosses it." + - field: "Business model" + sector_label: "AI Business Model" + sector_guidance: "Cover: pricing model (per-API-call, per-token, per-outcome, seat-based, hybrid), cost structure (inference COGS, training amortization, data pipeline), the margin improvement trajectory, and the data flywheel mechanism. Show how per-customer revenue grows with usage." + - field: "Traction" + sector_label: "AI Traction Metrics" + sector_guidance: "Dedicated slide with: Revenue trajectory, API call volume growth, customer count, model accuracy improvement over time, customer-reported accuracy satisfaction, and retention rate. The model quality improvement chart is uniquely important — it demonstrates the data flywheel in action." + sections_to_add: + - section_name: "Model Differentiation Slide" + placement: "after:AI Market Opportunity" + description: "The 'why us' slide — why this AI product wins against all five competitive alternatives." + fields: + - "Model accuracy comparison (vs. competitors, vs. open-source, vs. foundation models)" + - "Data moat description (proprietary data, generation mechanism, replication cost)" + - "Technical approach (architecture choice, training methodology, unique innovation)" + - section_name: "Data Moat Slide" + placement: "after:Model Differentiation Slide" + description: "The most scrutinized slide in an AI fundraising deck — how the data advantage is built and defended." + fields: + - "Data flywheel diagram (product usage > data > model improvement > more users)" + - "Current dataset size and growth rate" + - "Estimated competitor replication cost and timeline" + - "Data partnership and proprietary source overview" + - section_name: "Responsible AI Slide" + placement: "after:AI Traction Metrics" + description: "Increasingly required by institutional investors and essential for enterprise AI companies." + fields: + - "Responsible AI framework and governance" + - "Bias testing results and fairness metrics" + - "Regulatory compliance posture (EU AI Act, sector-specific regulations)" + - "Explainability and transparency mechanisms" + - section_name: "Compute Strategy Slide" + placement: "after:AI Business Model" + description: "How the company manages the compute supply chain and optimizes inference economics." + fields: + - "Current compute infrastructure (provider, GPU types, allocation)" + - "Inference cost optimization roadmap" + - "Multi-provider strategy (or single-provider risk acknowledgment)" + - "Gross margin improvement trajectory from compute optimization" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index", "gross-margin-compute-adjusted", "inference-cost-per-request", "responsible-ai-score"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "An AI-ML strategic one-pager must anchor analysis in model-centric strategy: data moat strength, model quality trajectory, competitive position against all five threat vectors, and the unit economics of AI delivery." + field_changes: + - field: "Strategic position" + sector_label: "AI Strategic Position" + sector_guidance: "Frame position in AI terms: model quality vs. alternatives (proprietary and open-source), data moat depth and durability, compute efficiency relative to competitors, and responsible AI posture relative to regulatory trajectory." + - field: "Key metrics" + sector_label: "AI Health Metrics" + sector_guidance: "Core 5: Revenue + growth rate, Model accuracy (F1 or domain-equivalent), Gross margin (compute-adjusted), Customer retention (AI-specific), Data moat index. Compare each to AI-ML benchmarks." + sections_to_add: + - section_name: "Model Moat Assessment" + placement: "end" + description: "Assessment of the durability of the company's AI competitive advantage." + fields: + - "Data moat: proprietary data volume, generation rate, replication cost" + - "Model moat: accuracy gap over alternatives, improvement trajectory" + - "Distribution moat: API integrations, workflow embedding depth" + - "Trust moat: responsible AI posture, enterprise compliance certifications" + - "Moat vulnerability: open-source convergence rate, foundation model encroachment risk" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index", "gross-margin-compute-adjusted", "customer-retention-ai"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI market sizing must account for the AI-specific dynamics: the adoption curve (enterprise AI adoption is still early), the accuracy threshold (the market exists only above a certain accuracy level), and the disruption of legacy approaches (AI replacing manual processes or legacy software)." + field_changes: + - field: "Total addressable market" + sector_label: "AI-Addressable Market" + sector_guidance: "Use AI-specific sizing: (number of target organizations) x (number of relevant decisions/tasks per year) x (price per AI-assisted decision). Cross-reference with current spend on manual processes or legacy software being replaced. Include the accuracy-gated market — what portion is only addressable above a certain accuracy threshold." + - field: "Market dynamics" + sector_label: "AI Adoption Dynamics" + sector_guidance: "Address: enterprise AI adoption maturity (early, growth, mainstream), regulatory trajectory (enabling or constraining), open-source adoption impact on pricing, and the accuracy improvement curve that unlocks new market segments." + sections_to_add: + - section_name: "Accuracy-Gated Market Expansion" + placement: "end" + description: "How model accuracy improvements unlock additional market segments." + fields: + - "Current accuracy level and the market it addresses" + - "Accuracy milestones and the additional market each unlocks" + - "Projected timeline to reach each accuracy milestone" + - "Total market at current accuracy vs. target accuracy" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML due diligence includes AI-specific areas: model evaluation (independent accuracy testing), data audit (training data provenance, bias, and legal compliance), responsible AI assessment, compute cost verification, and IP review (model ownership, training data rights)." + field_changes: + - field: "Financial review" + sector_label: "AI Financial Verification" + sector_guidance: "Verify: revenue calculation (especially usage-based), COGS classification (inference compute, training amortization — is this COGS or R&D?), gross margin methodology, customer concentration, and revenue quality (recurring vs. one-time integration fees)." + - field: "Operational review" + sector_label: "AI Operations and Model Review" + sector_guidance: "Review: model accuracy on independent evaluation sets (not just the company's benchmarks), hallucination rate testing, data pipeline reliability, model drift monitoring, and MLOps maturity. Request access to evaluation results and model cards." + sections_to_add: + - section_name: "Model and Data Audit" + placement: "after:AI Operations and Model Review" + description: "AI-specific technical due diligence that does not exist in traditional software." + fields: + - "Independent model evaluation on held-out data (accuracy, latency, reliability)" + - "Training data provenance and legal compliance review" + - "Bias and fairness audit results" + - "Model drift monitoring and retraining pipeline review" + - "Hallucination rate assessment (for generative models)" + - section_name: "Responsible AI Assessment" + placement: "after:Model and Data Audit" + description: "Increasingly standard in AI investment due diligence." + fields: + - "Responsible AI framework and governance structure" + - "Regulatory compliance status (EU AI Act, sector-specific regulations)" + - "Third-party audit results (if any)" + - "Incident response plan for model failures" + - section_name: "Compute and Infrastructure Review" + placement: "end" + description: "AI-specific infrastructure assessment." + fields: + - "GPU infrastructure (type, quantity, provider, cost)" + - "Multi-provider strategy and migration capability" + - "Inference optimization roadmap" + - "Training cost trajectory and scalability" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "responsible-ai-score", "gross-margin-compute-adjusted", "inference-cost-per-request"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not AI-ML-specific. Standard venture capital cap table formats apply regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML decision rationale memos should explicitly address the model-centric dimensions of the decision: impact on model quality, data moat, compute cost, and responsible AI posture." + field_changes: + - field: "Decision context" + sector_label: "AI Decision Context" + sector_guidance: "Include the AI-specific context: how does this decision affect model quality, data strategy, compute cost, competitive position against alternatives (including open-source), and responsible AI posture? AI decisions often involve trade-offs between accuracy, cost, and speed that should be explicit." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML exit scenarios are shaped by AI-specific acquirer categories and valuation methodologies. Strategic acquirers include big tech companies seeking AI talent and capabilities (acqui-hires are common), vertical industry players acquiring AI to embed in their products, and AI platform companies consolidating capabilities." + field_changes: + - field: "Valuation methodology" + sector_label: "AI Valuation Multiples" + sector_guidance: "AI companies are valued on a combination of revenue multiples (similar to SaaS), research asset value (team, IP, data), and strategic premium (data moat, model capabilities). Report: revenue multiple, research team valuation (common in acqui-hires), and data asset valuation. Note that AI valuations are more volatile than SaaS due to hype cycle effects." + - field: "Potential acquirers" + sector_label: "AI Acquirer Landscape" + sector_guidance: "Categorize: (1) Big tech AI acquirers (Google, Microsoft, Meta, Apple, Amazon — acquiring for talent, models, and data). (2) Vertical industry acquirers (healthcare, legal, financial companies acquiring AI capabilities for their domain). (3) AI platform consolidators (AI companies acquiring complementary capabilities). (4) PE acquirers (private equity acquiring profitable AI businesses)." + sections_to_add: + - section_name: "AI Asset Valuation" + placement: "after:AI Valuation Multiples" + description: "Valuation of AI-specific assets beyond revenue." + fields: + - "Data asset valuation (estimated replication cost of proprietary dataset)" + - "Research team valuation (team size, publications, skill rarity)" + - "Model IP valuation (patents, trade secrets, unique architecture)" + - "Customer data flywheel valuation (value of the ongoing data generation from product usage)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index", "gross-margin-compute-adjusted"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML board reviews must cover both business performance and model performance. Board members need to understand model quality trajectory, competitive position against open-source, compute cost management, and responsible AI governance alongside traditional financial metrics." + field_changes: + - field: "Financial summary" + sector_label: "AI Financial Dashboard" + sector_guidance: "Present: Revenue trend (12 months), Gross margin trend (compute-adjusted), Inference cost trend (per-request), Burn rate, Runway. Compare gross margin to the AI industry benchmark (55-65%) and show the improvement trajectory." + - field: "Strategic priorities" + sector_label: "AI Strategic Priorities and Model Progress" + sector_guidance: "Report against quarterly OKRs that span both model and business: accuracy improvement, cost reduction, customer acquisition, and responsible AI milestones. Flag any model quality degradation with root cause." + - field: "Risks" + sector_label: "AI Risk Dashboard" + sector_guidance: "Categorize: Model risks (accuracy plateau, drift, hallucination liability), Competitive risks (open-source convergence, foundation model encroachment), Compute risks (GPU availability, cost volatility), Regulatory risks (EU AI Act compliance, sector regulation), and Financial risks (margin pressure, runway)." + sections_to_add: + - section_name: "Model Performance Dashboard" + placement: "before:AI Financial Dashboard" + description: "One-page model metrics summary for board review." + fields: + - "Model accuracy (F1 or domain metric) — current and trend" + - "Hallucination rate (if generative) — current and trend" + - "Inference latency (p50/p95) — current and trend" + - "A/B test win rate (model improvement velocity)" + - "Customer-reported accuracy satisfaction" + - "Data pipeline reliability" + - section_name: "Competitive Position Update" + placement: "after:AI Financial Dashboard" + description: "Where the model stands relative to alternatives." + fields: + - "Accuracy gap vs. best open-source alternative (trend)" + - "Accuracy gap vs. foundation models on core task (trend)" + - "Win rate in competitive evaluations (trend)" + - section_name: "Responsible AI Update" + placement: "after:AI Risk Dashboard" + description: "Responsible AI governance update for the board." + fields: + - "Bias/fairness metrics (current and trend)" + - "Regulatory compliance status" + - "Incident report (any model failures with customer impact)" + - "Responsible AI roadmap progress" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "inference-cost-per-request", "gross-margin-compute-adjusted", "responsible-ai-score", "data-moat-index"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML board agendas should allocate time to model performance, competitive dynamics (especially open-source), compute strategy, and responsible AI governance — topics that do not appear in traditional board meetings." + field_changes: + - field: "Agenda items" + sector_label: "AI Board Agenda" + sector_guidance: "Standard AI board agenda: (1) Model and business metrics review — 15 min (pre-read, discussion only). (2) Strategic topic deep-dive — 30 min (rotate: model quality trajectory, competitive position, compute strategy, responsible AI, pricing/monetization). (3) Compute and infrastructure — 10 min (cost, availability, multi-provider strategy). (4) Fundraising/runway — 10 min. (5) CEO asks — 10 min. (6) Executive session — 15 min. Total: 90 minutes." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML risk categories include AI-specific risks that do not exist in traditional software: model accuracy risk, hallucination liability, regulatory risk (AI-specific regulation), compute dependency, data risk (training data legal compliance), and responsible AI risk (bias, fairness)." + field_changes: + - field: "Risk categories" + sector_label: "AI Risk Categories" + sector_guidance: "Include AI-specific categories: (1) Model risk — accuracy degradation, hallucination liability, adversarial attacks, model theft. (2) Data risk — training data legal compliance, data partnership stability, data moat erosion. (3) Compute risk — GPU availability, single-provider dependency, cost volatility. (4) Regulatory risk — EU AI Act compliance, sector-specific AI regulation, responsible AI requirements. (5) Competitive risk — open-source convergence, foundation model encroachment. (6) Ethical risk — bias, fairness failures, unintended model uses." + sections_to_add: + - section_name: "AI-Specific Risk Matrix" + placement: "end" + description: "Probability-impact matrix for AI-specific risks." + fields: + - "Model accuracy degradation (probability, impact, mitigation)" + - "Hallucination liability event (probability, impact, mitigation)" + - "Open-source model reaching parity (probability, impact, mitigation)" + - "Foundation model provider shipping competing feature (probability, impact, mitigation)" + - "Regulatory compliance failure (probability, impact, mitigation)" + - "GPU supply disruption (probability, impact, mitigation)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "responsible-ai-score", "data-moat-index"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML change initiatives often involve model architecture transitions, compute infrastructure migrations, or responsible AI framework implementations — changes with unique risk profiles and timelines." + field_changes: + - field: "Proposed change" + sector_label: "AI Change Initiative" + sector_guidance: "For AI-specific changes (model architecture transition, compute migration, responsible AI implementation), include: the model quality impact (expected accuracy change), the cost impact (compute cost change), the timeline to production deployment, and the rollback plan if the change degrades performance." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML compensation includes significant premiums for ML talent. ML researchers, ML engineers, and data scientists command 20-40% premiums over equivalent software engineering roles. The board should understand the competitive dynamics of AI talent compensation." + field_changes: + - field: "Compensation benchmarks" + sector_label: "AI-ML Compensation Benchmarks" + sector_guidance: "Use AI-specific comp data: Levels.fyi (ML engineering), academic salary benchmarks (for research track), and AI startup comp surveys. Report by role (ML researcher, ML engineer, data engineer, AI PM) and by seniority. Include equity component — critical for AI talent retention. Note that big tech AI salaries often exceed startup budgets by 2-3x for senior ML researchers." + sections_to_add: + - section_name: "ML Talent Market Analysis" + placement: "end" + description: "AI-specific talent market context for compensation decisions." + fields: + - "ML talent supply-demand dynamics (scarce, balanced, surplus)" + - "Competing offers from big tech AI labs (typical total comp for target profile)" + - "Research publication and conference attendance as retention tools" + - "GPU access as a compensation and retention lever (dedicated research compute)" + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML regulatory compliance is rapidly evolving with AI-specific legislation (EU AI Act, US executive orders, sector-specific AI regulations). The board needs specific AI regulatory intelligence." + field_changes: + - field: "Regulatory landscape" + sector_label: "AI Regulatory Landscape" + sector_guidance: "Cover: AI-specific regulation (EU AI Act risk classification for your product, US AI executive orders, state-level AI laws), sector-specific AI requirements (healthcare AI: FDA, legal AI: bar association standards, financial AI: SEC/CFPB guidance), data privacy regulation (GDPR, CCPA as they apply to training data), and emerging standards (NIST AI Risk Management Framework, ISO 42001 AI Management System)." + sections_to_add: + - section_name: "AI Risk Classification" + placement: "after:AI Regulatory Landscape" + description: "Assessment of the product's regulatory risk classification under major frameworks." + fields: + - "EU AI Act risk classification (unacceptable, high-risk, limited, minimal) and rationale" + - "Compliance requirements for the classified risk level" + - "Compliance roadmap and estimated cost" + - "Impact on product design, marketing, and deployment if classification changes" + - section_name: "Responsible AI Governance" + placement: "end" + description: "Internal AI governance status for board oversight." + fields: + - "Responsible AI framework implementation status" + - "Bias and fairness audit schedule and results" + - "Model incident log (errors with customer impact)" + - "Third-party audit status" + sections_to_remove: [] + benchmark_references: ["responsible-ai-score"] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "CEO succession planning follows standard corporate governance practices. AI-ML-specific considerations (technical fluency of successor) are naturally incorporated through the specific role requirements." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML action plans should include both business metric targets and model metric targets, recognizing that model improvement is a primary action category in AI companies." + field_changes: + - field: "Success metrics" + sector_label: "AI-ML KPI Targets" + sector_guidance: "Define success using both model and business metrics: model accuracy improvement target, hallucination rate reduction, inference cost reduction, revenue impact, customer satisfaction improvement. Every action should connect to a measurable metric with clear ownership." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML initiative briefs must include model quality impact, compute cost impact, and the data strategy implications alongside business outcomes." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected AI-ML Impact" + sector_guidance: "Quantify impact across three dimensions: model quality (accuracy improvement, hallucination reduction, latency improvement), business metrics (revenue contribution, customer retention impact, expansion revenue), and cost efficiency (inference cost change, training cost, data acquisition cost)." + - field: "Resource requirements" + sector_label: "ML Resource Requirements" + sector_guidance: "In AI-ML, resources include not just engineering time but compute budget (GPU hours for training and experimentation), data requirements (new data needed, labeling cost), and infrastructure changes (serving capacity, monitoring). Quantify all four and the opportunity cost." + sections_to_add: + - section_name: "Model Impact Assessment" + placement: "after:Expected AI-ML Impact" + description: "How the initiative affects model quality and the data flywheel." + fields: + - "Expected model metric change (F1, hallucination rate, latency)" + - "Training data requirements (new data, labeling effort)" + - "Compute budget required (GPU hours for training and experimentation)" + - "Data flywheel impact (does this initiative generate reusable training data?)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "inference-cost-per-request"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML project kickoffs must define success in terms of model metrics, include an evaluation plan, and specify the compute budget for experimentation." + field_changes: + - field: "Success criteria" + sector_label: "AI-ML Success Metrics and Evaluation Plan" + sector_guidance: "Define 2-3 model metrics and 2-3 business metrics. Include: baseline measurement, target, evaluation dataset and methodology, compute budget, and evaluation timeline. For model improvement projects, specify the statistical significance threshold for claiming improvement." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML hiring scorecards must include AI-specific competency assessments: ML technical depth, production ML experience, domain knowledge, and the research-vs-engineering orientation." + field_changes: + - field: "Required competencies" + sector_label: "AI-ML-Specific Competencies" + sector_guidance: "For ML roles: model architecture knowledge, production ML experience (not just research), domain expertise, evaluation methodology rigor, and MLOps proficiency. For AI PM roles: ML literacy (can evaluate model quality trade-offs), domain expertise, and the ability to translate between research and business teams. Assess research-vs-engineering orientation against the role requirement." + sections_to_add: + - section_name: "ML Technical Assessment" + placement: "end" + description: "AI-specific technical evaluation criteria." + fields: + - "ML depth assessment (architecture knowledge, training methodology, evaluation rigor)" + - "Production ML experience (deployment, monitoring, optimization)" + - "Research-vs-engineering orientation match for the role" + - "Domain expertise level (critical for vertical AI products)" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML incidents include model-specific failures: hallucination events, accuracy degradation, bias incidents, and adversarial attacks that require model-specific root cause analysis and remediation." + field_changes: + - field: "Impact assessment" + sector_label: "Model Incident Impact" + sector_guidance: "Quantify: customers affected, predictions impacted (number and severity), revenue at risk (affected customer MRR), accuracy degradation magnitude, hallucination severity (if applicable), responsible AI implications (bias event, fairness violation), and customer communication timeline." + sections_to_add: + - section_name: "Model Root Cause Analysis" + placement: "after:Model Incident Impact" + description: "AI-specific root cause analysis for model failures." + fields: + - "Was the failure a model quality issue (accuracy degradation, hallucination), infrastructure issue (serving failure, latency spike), or data issue (pipeline failure, drift)?" + - "Was the failure detectable by existing monitoring? If not, what monitoring gap allowed it?" + - "Was the failure preventable by existing evaluation? If not, what evaluation gap exists?" + - "Model rollback timeline (how quickly was the bad model replaced?)" + - section_name: "Responsible AI Impact" + placement: "after:Model Root Cause Analysis" + description: "Assessment of responsible AI implications of the incident." + fields: + - "Was the incident a bias or fairness failure?" + - "Were affected populations harmed by the model error?" + - "Regulatory notification requirements (if any)" + - "Responsible AI framework update needed" + sections_to_remove: [] + benchmark_references: ["hallucination-rate", "model-accuracy-f1"] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML retrospectives should include model experimentation review alongside standard sprint retrospective elements. The 'what we tried and learned' section is especially important for ML teams where experiments are a primary work product." + field_changes: + - field: "What went well" + sector_label: "What Worked (Model and Product)" + sector_guidance: "Include both product successes and model experimentation wins. 'Model X achieved 3% accuracy improvement through technique Y' is a retrospective win even if it has not shipped yet." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific. The content naturally adapts to AI-ML context." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML team health must include the research-product alignment dimension, ML-specific burnout indicators, and the compute resource satisfaction metric (ML engineers who cannot get GPU access are unhappy engineers)." + field_changes: + - field: "Health indicators" + sector_label: "AI-ML Team Health Indicators" + sector_guidance: "Include AI-specific indicators: research-product alignment (do researchers and product engineers share goals?), model improvement velocity (A/B test win rate and deployment frequency), compute resource satisfaction (can the team access the GPU hours they need?), MLOps burden (percentage of time on maintenance vs. innovation), and responsible AI engagement (is the team bought into responsible AI practices or treating them as overhead?)." + sections_to_add: + - section_name: "Research-Product Alignment Score" + placement: "end" + description: "Assessment of alignment between the research and product functions." + fields: + - "Research-to-production pipeline health (models deployed within 30 days of research completion?)" + - "Shared KPIs between research and product teams" + - "Research team satisfaction with production priorities" + - "Product team satisfaction with research output applicability" + sections_to_remove: [] + benchmark_references: ["model-deployment-frequency", "ab-test-win-rate"] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML company values should explicitly address the unique cultural questions: research freedom vs. commercial discipline, responsible AI as a value, and the balance between technical ambition and practical shipping." + field_changes: + - field: "Core values" + sector_label: "AI-ML Company Values" + sector_guidance: "Consider AI-specific value dimensions: responsible AI commitment (is ethical AI a stated value?), research-product balance (do we value both exploration and shipping?), accuracy honesty (do we communicate model limitations transparently?), and data stewardship (do we treat customer and training data with care?)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning is not sector-specific, though AI-ML offsites often include research deep-dives and model review sessions." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML role descriptions must distinguish between ML researcher, ML engineer, data engineer, and AI product manager — roles with distinct skill profiles, evaluation criteria, and career paths." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Metric Ownership" + sector_guidance: "For ML roles, specify the model metrics the role owns. ML researcher: accuracy improvement, A/B test win rate, architecture innovation. ML engineer: deployment frequency, inference latency, inference cost, pipeline reliability. Data engineer: data pipeline reliability, data freshness, annotation quality. AI PM: customer accuracy satisfaction, feature adoption, use-case expansion." + - field: "Required experience" + sector_label: "AI-ML Experience Requirements" + sector_guidance: "Specify: ML specialization (NLP, vision, tabular, reinforcement learning), production vs. research experience balance, domain expertise requirement, and publication expectations (if research role)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An AI-ML CEO's weekly review must include model metrics alongside business metrics. The model is the product — ignoring model health in the weekly review is equivalent to ignoring the product." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly AI-ML Dashboard" + sector_guidance: "Review weekly: Revenue and WoW change, API call volume and growth, Model accuracy (if monitored continuously), Inference cost trend, Customer escalations (especially accuracy-related), Pipeline changes. Monthly metrics (gross margin, retention, responsible AI scores) should be reviewed monthly." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Identify the single most important thing. In AI-ML, this is often: resolving a model quality issue, closing an enterprise deal, making a model architecture decision, or addressing a competitive model release. One priority — not ten." + sections_to_add: + - section_name: "Model Health Check" + placement: "after:Weekly AI-ML Dashboard" + description: "Weekly model health review." + fields: + - "Any accuracy degradation detected this week?" + - "Any customer-reported accuracy issues?" + - "Model improvement experiments completed and results" + - "Competitive model release to evaluate (if any)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "inference-cost-per-request", "api-call-volume"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML decision journals should capture the model-specific dimensions of decisions: accuracy trade-offs, compute cost implications, and the data strategy impact." + field_changes: + - field: "Decision context" + sector_label: "AI Decision Context and Data" + sector_guidance: "Record: the model metrics and business metrics that informed this decision, the accuracy-cost-speed trade-off involved, and the specific metric outcome that will confirm the decision was correct. For model architecture decisions, note the 'kill criteria' — what metric threshold would trigger reversal." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML annual reviews should assess model quality trajectory, data moat growth, compute efficiency improvement, and responsible AI maturity alongside business metrics." + field_changes: + - field: "Year in review" + sector_label: "AI-ML Year in Review" + sector_guidance: "Assess: Revenue growth (actual vs. plan), Model accuracy trajectory (beginning of year vs. end), Gross margin trend (compute-adjusted), Data moat growth (dataset size, quality, uniqueness), Competitive position shift, Responsible AI maturity evolution, Team growth and capability development." + - field: "Next year goals" + sector_label: "Next Year AI-ML Targets" + sector_guidance: "Set targets across model, business, and responsible AI dimensions: accuracy targets (by use case), revenue and margin targets, compute efficiency targets, data acquisition targets, responsible AI milestones, and team targets. Each target should reference the AI-ML benchmark tier being targeted." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "gross-margin-compute-adjusted", "data-moat-index", "responsible-ai-score"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML stakeholder maps include AI-specific stakeholder categories: compute providers, data partners, the open-source community, AI regulators, and the research community." + field_changes: + - field: "Stakeholder categories" + sector_label: "AI-ML Stakeholder Ecosystem" + sector_guidance: "Include: Investors (AI-focused VCs, strategic investors from big tech), Customers (API consumers, enterprise deployers, developer community), Data partners (data providers, annotation services, academic collaborators), Compute partners (GPU providers, cloud platforms), Research community (academic collaborators, open-source contributors, conference peers), Regulators (AI-specific and sector-specific), and Team (researchers, engineers, business)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML negotiation prep should include AI-specific negotiation contexts: data partnership terms, compute contracts, accuracy SLAs, and model IP ownership." + field_changes: + - field: "Negotiation type" + sector_label: "AI-ML Negotiation Context" + sector_guidance: "Classify: enterprise deal (accuracy SLA, data handling, liability), fundraising (valuation, AI-specific terms), data partnership (data access, IP, revenue share), compute contract (GPU allocation, pricing, commitment terms), or model integration (API terms, competitive restrictions, IP ownership). Each has distinct AI-specific dynamics." + - field: "BATNA" + sector_label: "BATNA and AI-ML Leverage" + sector_guidance: "AI-specific leverage: for enterprise sales — model accuracy superiority, domain-specific fine-tuning, compliance readiness. For fundraising — AI premium in valuations, multiple interested AI-focused funds. For compute — multi-provider optionality, reserved instance leverage. For data partnerships — mutual value creation, co-publication incentives." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "data-moat-index"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML founder mental health is affected by AI-specific stressors: the relentless pace of competitive model releases, the pressure to maintain accuracy while reducing costs, the philosophical weight of responsible AI decisions, and the hype cycle that amplifies both euphoria and despair." + field_changes: + - field: "Stress indicators" + sector_label: "AI-ML-Specific Stress Indicators" + sector_guidance: "Include: competitive anxiety (checking competitor model releases and benchmarks obsessively), accuracy obsession (emotional reactions to individual model errors), hype cycle whiplash (mood tracking with AI media coverage), responsible AI burden (moral weight of model decisions affecting people), and imposter syndrome amplified by the pace of AI research ('everyone is ahead of us')." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific. Reflections naturally address AI-ML-specific challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML founders must maintain technical depth in a rapidly evolving field while developing business and leadership skills." + field_changes: + - field: "Learning areas" + sector_label: "AI-ML Learning Priorities" + sector_guidance: "Consider AI-ML-specific learning areas: model architecture trends (staying current with research), MLOps and production ML (infrastructure competence), responsible AI and governance (regulatory literacy), AI product strategy (monetization, pricing, distribution), compute economics (GPU market, inference optimization), and the open-source ecosystem (understanding community dynamics and opportunities)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An AI-ML founder's advisory board should include AI-specific expertise areas not found in traditional startup advisory boards." + field_changes: + - field: "Advisor categories" + sector_label: "AI-ML Advisory Needs" + sector_guidance: "Map advisors to AI-ML-specific needs: ML research (someone current with the research frontier), AI product commercialization (someone who has built and sold AI products), Responsible AI and regulation (someone navigating AI compliance), Compute infrastructure (someone who has optimized AI serving at scale), Domain expertise (vertical knowledge for the target market), AI fundraising (someone who has raised with an AI-specific narrative), and Go-to-market for developer products (API distribution, developer community)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML QBRs must demonstrate model accuracy on the customer's specific data, report usage patterns, and communicate model improvements. For AI products, the QBR is where trust is built or eroded based on concrete accuracy evidence." + field_changes: + - field: "Performance summary" + sector_label: "Model Performance on Your Data" + sector_guidance: "Quantify model accuracy on the customer's specific use case — not general benchmarks, but accuracy on their data. Report: accuracy metrics (F1, precision, recall on the customer's task), hallucination rate (if applicable), latency performance vs. SLA, and any accuracy improvements since the last QBR." + - field: "Account status" + sector_label: "Usage and Adoption Metrics" + sector_guidance: "Present: API call volume trend, use cases active, feature adoption, accuracy by use case, and comparison to similar accounts. Highlight any usage patterns that suggest expansion opportunities or underutilization." + - field: "Next steps" + sector_label: "Model Improvement and Expansion Opportunities" + sector_guidance: "Identify: upcoming model improvements relevant to the customer, new use cases the customer could benefit from, fine-tuning opportunities with customer-specific data, and any accuracy thresholds the customer needs that the next model version will cross." + sections_to_add: + - section_name: "Accuracy Report Card" + placement: "before:Model Performance on Your Data" + description: "Transparent accuracy reporting that builds trust." + fields: + - "Overall accuracy on customer's task (current quarter)" + - "Accuracy trend (improving, stable, declining)" + - "Error analysis: most common error types and planned improvements" + - "Comparison to accuracy at time of onboarding (demonstrating improvement)" + - section_name: "Model Roadmap Preview" + placement: "end" + description: "Upcoming model improvements that affect this customer." + fields: + - "Next model version features and expected accuracy improvement" + - "Fine-tuning opportunities specific to this customer's use case" + - "New capabilities in development that align with customer's domain" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "customer-accuracy-satisfaction"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML onboarding must address model capabilities and limitations upfront, set accurate accuracy expectations, and define the path to production deployment — including any fine-tuning, evaluation, and monitoring requirements." + field_changes: + - field: "Getting started steps" + sector_label: "Time-to-First-Prediction Path" + sector_guidance: "Define the shortest path to the first successful model prediction. Organize steps as: (1) API key setup and first prediction (first 30 minutes). (2) Integration with the customer's data pipeline (first day). (3) Evaluation on customer-specific data (first week). (4) Production deployment with monitoring (first month). Include accuracy expectations at each stage and the improvement trajectory with more data." + - field: "Resources" + sector_label: "Technical Resources" + sector_guidance: "Include: API documentation, SDK libraries, code examples, evaluation methodology guide, model cards (capabilities and limitations), and data format specifications. For AI products, documentation quality directly correlates with developer adoption speed." + sections_to_add: + - section_name: "Model Capabilities and Limitations" + placement: "before:Time-to-First-Prediction Path" + description: "Transparent communication about what the model can and cannot do." + fields: + - "Model capabilities: tasks the model performs well with expected accuracy ranges" + - "Model limitations: known failure modes, edge cases, domains where accuracy is lower" + - "Recommended use cases: where to deploy the model for maximum value" + - "Not recommended: use cases where the model should not be the sole decision-maker" + - section_name: "Accuracy Expectations and Improvement Path" + placement: "end" + description: "Setting realistic accuracy expectations and explaining the improvement trajectory." + fields: + - "Expected accuracy on the customer's task at deployment" + - "How accuracy improves over time (with more customer-specific data, fine-tuning, model updates)" + - "Accuracy evaluation methodology (how to measure model performance on your data)" + - "Feedback mechanism (how to report errors and how errors improve the model)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML proposals must address the unique concerns of AI buyers: accuracy expectations, data handling, liability for model errors, and the path from pilot to production." + field_changes: + - field: "Proposed solution" + sector_label: "AI Solution Proposal" + sector_guidance: "Describe the model capability, expected accuracy on the customer's specific task, the evaluation methodology (how accuracy will be measured and verified), data handling commitments (how customer data is used, stored, and protected), and the deployment architecture (cloud, on-premise, hybrid)." + - field: "Pricing" + sector_label: "AI Pricing Structure" + sector_guidance: "Present pricing with clear unit definition (per API call, per document, per prediction, per outcome). Include pilot pricing (often discounted or capped) and production pricing with volume tiers. Address the customer's inevitable question: 'What happens to our data — does it train your model?'" + sections_to_add: + - section_name: "Pilot-to-Production Path" + placement: "after:AI Solution Proposal" + description: "The structured path from evaluation to full deployment." + fields: + - "Pilot scope: task, data volume, success criteria, timeline" + - "Evaluation methodology: how accuracy will be measured, by whom, with what data" + - "Go/no-go criteria: accuracy threshold for production promotion" + - "Production deployment plan: integration, monitoring, scaling" + - section_name: "Responsible AI Commitment" + placement: "end" + description: "The company's responsible AI commitments for this engagement." + fields: + - "Bias testing and fairness metrics for this use case" + - "Explainability capabilities (how model decisions can be understood)" + - "Data handling and privacy commitments" + - "Incident response plan for model errors" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "responsible-ai-score"] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML case studies must prominently feature accuracy metrics, before-and-after comparisons, and responsible AI considerations. AI buyers evaluate case studies on concrete accuracy evidence, not testimonials alone." + field_changes: + - field: "Results" + sector_label: "Measured AI Impact" + sector_guidance: "Quantify results in accuracy and business terms: model accuracy on the customer's specific task (not general benchmarks), business outcome improvement (time saved, errors reduced, cost avoided), and the improvement trajectory over time. Include the evaluation methodology so readers can assess credibility." + sections_to_add: + - section_name: "Accuracy Evidence" + placement: "before:Measured AI Impact" + description: "Concrete accuracy data that AI buyers evaluate." + fields: + - "Model accuracy on the customer's specific task (metric and value)" + - "Comparison to manual process accuracy (human baseline)" + - "Comparison to previous solution accuracy (if replacing another AI product)" + - "Evaluation methodology (how accuracy was measured and verified)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "customer-accuracy-satisfaction"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML partnership memos must address data sharing, model integration, IP ownership, and responsible AI obligations — topics unique to AI partnerships." + field_changes: + - field: "Partnership terms" + sector_label: "AI Partnership Terms" + sector_guidance: "Address AI-specific terms: data sharing scope and protections, model integration architecture (API, embedded, on-premise), IP ownership (who owns fine-tuned models?), accuracy commitments (SLAs for model quality), responsible AI obligations (bias testing, explainability, incident notification), and competitive restrictions (does the partner data train models that serve their competitors?)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML project status updates should include model performance metrics alongside project milestones, since model quality is the primary deliverable." + field_changes: + - field: "Progress summary" + sector_label: "Model and Project Progress" + sector_guidance: "Include both project milestones (integration complete, evaluation started, production deployed) and model performance (current accuracy on customer's task, improvement since last update, any issues identified). For AI projects, model performance is the most important status item." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML SLAs must address model-specific performance commitments: accuracy guarantees (or ranges), hallucination rate caps, latency commitments, and uptime — all of which are AI-specific contractual obligations." + field_changes: + - field: "Service levels" + sector_label: "AI Service Levels" + sector_guidance: "Define AI-specific SLAs: (1) Availability (API uptime — standard 99.5-99.9%). (2) Latency (p50, p95, p99 response time commitments). (3) Accuracy (measured on a mutually agreed evaluation set, reported quarterly — not guaranteed at a specific number, but measured and reported transparently). (4) Hallucination rate (for generative products — measured and reported with reduction commitments). (5) Model update frequency (commitment to model improvement cadence). Include clear measurement methodology and remediation process for SLA violations." + sections_to_add: + - section_name: "AI-Specific SLA Definitions" + placement: "end" + description: "Definitions for AI-specific service level metrics." + fields: + - "Accuracy measurement methodology (evaluation set, measurement frequency, reporting format)" + - "Hallucination measurement methodology (if applicable)" + - "Model update and improvement commitments" + - "Data handling SLA (how customer data is processed, stored, and deleted)" + - "Incident classification for model failures (severity levels and response times)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "hallucination-rate", "inference-latency"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "AI-ML analysis reports delivered to clients should include model methodology transparency, accuracy metrics, confidence levels, and limitations — enabling the client to evaluate the reliability of AI-generated analysis." + field_changes: + - field: "Analysis methodology" + sector_label: "AI Analysis Methodology" + sector_guidance: "Disclose the model used, the data processed, the confidence calibration, and the limitations of the analysis. For AI-generated analysis, methodology transparency is a trust requirement. Include: model version, evaluation accuracy on similar tasks, and known failure modes relevant to this analysis." + - field: "Key findings" + sector_label: "AI-Derived Findings with Confidence Scores" + sector_guidance: "Present findings with calibrated confidence scores. Distinguish between high-confidence findings (model is highly reliable for this type of analysis) and exploratory findings (model accuracy is moderate, human review recommended). This transparency builds trust and prevents over-reliance on AI output." + sections_to_add: + - section_name: "Model Confidence and Limitations" + placement: "end" + description: "Transparent communication about the AI analysis reliability." + fields: + - "Overall model confidence for this analysis type" + - "Known limitations relevant to this specific analysis" + - "Recommendations for human review (which findings warrant additional verification)" + sections_to_remove: [] + benchmark_references: ["model-accuracy-f1", "customer-accuracy-satisfaction"] diff --git a/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-benchmarks.yaml b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-benchmarks.yaml new file mode 100644 index 0000000..2f3f06d --- /dev/null +++ b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-benchmarks.yaml @@ -0,0 +1,980 @@ +# D2C Consumer Industry Pack — Benchmarks +# +# 25 D2C-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing acquisition, retention, +# brand, and margin issues for direct-to-consumer brands. +# +# D2C is BRAND-FIRST. Every metric must be interpreted through the lens of brand +# building, community strength, and emotional customer connection — not merely +# as financial outputs. A healthy D2C business optimizes for brand equity and +# customer love, which then produce healthy financial metrics. The reverse +# (optimizing financial metrics without brand investment) is the CAC death spiral. +# +# Primary data sources: +# - Triple Whale DTC Benchmarks (2024, 2025) +# - Shopify Commerce Reports (2024, 2025) +# - Klaviyo Email & SMS Benchmarks (2024, 2025) +# - Meta Advertising Benchmarks (2024, 2025) +# - Pilothouse DTC Index (2024, 2025) +# - 2PM / Web Smith DTC Research (2024) +# - Daasity D2C Analytics Benchmarks (2024) +# - Recharge Subscription Commerce Report (2024) +# - Narvar Returns & Exchanges Report (2024) +# - Loop Returns Industry Data (2024) +# - Yotpo E-Commerce Benchmarks (2024) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded or established D2C brands at the relevant stage. + +pack_metadata: + sector: "d2c-consumer" + display_name: "D2C Consumer" + version: "1.0.0" + description: "Benchmark data for direct-to-consumer brands spanning acquisition, retention, unit economics, marketing efficiency, brand health, and channel performance metrics." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # ACQUISITION METRICS + # ───────────────────────────────────────────── + + - name: "Customer Acquisition Cost (Blended)" + id: "cac-blended" + category: "unit-economics" + definition: "The fully loaded cost to acquire one new customer, averaged across all channels. Includes paid media, influencer fees, creative production, agency costs, and allocated team salaries." + formula: "Total Sales & Marketing Spend / Number of New Customers Acquired" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $80 (general consumer goods); > $120 (premium/luxury)" + signal: "Acquisition economics are unsustainable. The brand is overspending relative to first-order margin, creating a cash-flow trap that worsens with scale." + below_average: + value: "$50-$80 (general); $80-$120 (premium)" + signal: "Acquisition costs are elevated. Sustainable only if LTV is proportionally high and repeat purchase rate exceeds 30%." + average: + value: "$30-$50 (general); $50-$80 (premium)" + signal: "Inline with D2C industry medians. Viable economics if contribution margin on first order is positive or payback period is under 6 months." + good: + value: "$15-$30 (general); $30-$50 (premium)" + signal: "Efficient acquisition. Indicates strong brand awareness, organic demand, or well-optimized paid channels." + excellent: + value: "< $15 (general); < $30 (premium)" + signal: "Exceptional efficiency. Typically driven by strong organic/referral mix, viral product, or influencer-seeded brand awareness." + stage_notes: + seed: "CAC is volatile and often high. Focus on testing channels and learning which audiences convert, not on optimizing CAC below a specific threshold." + series_a: "Blended CAC should demonstrate a downward trend over 6+ months. Investors want to see that scale reduces CAC through brand equity, not just that spend increases." + series_b_plus: "Blended CAC should be stable or declining. Rising blended CAC at scale signals channel saturation and the need for brand investment to drive organic acquisition." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["cac-by-channel", "ltv-cac-ratio", "payback-period"] + related_skills: ["four-ps-marketing", "balanced-scorecard"] + caveats: "Blended CAC obscures channel-level economics. A low blended CAC driven by high organic volume can mask unsustainable paid channel CAC. Always decompose into channel-level CAC alongside blended." + + - name: "CAC by Channel" + id: "cac-by-channel" + category: "unit-economics" + definition: "The cost to acquire a new customer attributed to each paid acquisition channel, enabling comparison of channel efficiency and investment allocation." + formula: "Channel-Specific Spend / New Customers Attributed to Channel" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "Meta > $70; Google > $60; TikTok > $50; Influencer > $100 per attributed customer" + signal: "Channel economics are negative on first order for most D2C brands. Either creative fatigue, audience saturation, or poor targeting is inflating costs." + below_average: + value: "Meta $45-$70; Google $40-$60; TikTok $30-$50; Influencer $60-$100" + signal: "Above median but potentially viable with strong repeat purchase rates. Creative refresh and audience testing are immediate priorities." + average: + value: "Meta $25-$45; Google $25-$40; TikTok $15-$30; Influencer $30-$60" + signal: "Inline with D2C norms post-iOS 14.5. Achievable with well-optimized campaigns and strong creative." + good: + value: "Meta $15-$25; Google $15-$25; TikTok $8-$15; Influencer $15-$30" + signal: "Strong channel efficiency. Product-market fit and creative resonance are working together." + excellent: + value: "Meta < $15; Google < $15; TikTok < $8; Influencer < $15" + signal: "Exceptional performance. Typically seen in viral products, strong brand affinity, or category-creating brands." + stage_notes: + seed: "Test 2-3 channels to find the best-performing one. Do not spread budget across all channels. Concentrate and learn." + series_a: "Demonstrate one primary channel at efficient CAC and one emerging channel being tested. Channel diversification is a Series A priority." + series_b_plus: "At least 3 paid channels at viable CAC, plus organic representing 30%+ of acquisition. Single-channel dependency is a red flag at scale." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "Meta Advertising Benchmarks" + year: "2025" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["cac-blended", "roas-by-channel", "organic-traffic-pct"] + related_skills: ["four-ps-marketing", "scenario-planning"] + caveats: "Post-iOS 14.5, channel-level attribution is unreliable. Last-click attribution over-credits Google and under-credits Meta and TikTok. Use media mix modeling or incrementality testing for accurate channel CAC at scale." + + - name: "ROAS by Channel (Return on Ad Spend)" + id: "roas-by-channel" + category: "efficiency" + definition: "Revenue generated per dollar spent on advertising within a specific channel, measuring the direct revenue efficiency of paid media investment." + formula: "Revenue Attributed to Channel / Ad Spend on Channel" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.5x" + signal: "Ad spend is not generating sufficient revenue to cover cost of goods and operations. The channel is cash-destructive." + below_average: + value: "1.5x-2.5x" + signal: "Marginal return. Viable only for brands with very high gross margins (>70%) and strong repeat purchase behavior." + average: + value: "2.5x-4.0x" + signal: "Inline with post-iOS D2C averages. Most D2C brands operate in this range on Meta and Google. TikTok ROAS trends lower but improving." + good: + value: "4.0x-6.0x" + signal: "Strong ad efficiency. Indicates resonant creative, well-targeted audiences, and a product that converts well from ad to purchase." + excellent: + value: "> 6.0x" + signal: "Exceptional. Often reflects strong brand awareness amplifying paid performance — customers who would have purchased organically clicking paid ads." + stage_notes: + seed: "ROAS below 2x is acceptable during testing. The goal is learning which creative, audience, and product combinations work, not immediate profitability." + series_a: "Demonstrate at least one channel above 3x ROAS with evidence of scalability (increasing spend without proportional ROAS decline)." + series_b_plus: "Blended ROAS should account for attribution gaps. Sophisticated brands use media mix modeling rather than platform-reported ROAS, which inflates by 20-40%." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["cac-by-channel", "contribution-margin", "organic-traffic-pct"] + related_skills: ["balanced-scorecard", "four-ps-marketing"] + caveats: "Platform-reported ROAS (Meta, Google) is consistently higher than true ROAS due to self-attribution. Triple Whale and other third-party analytics typically show ROAS 20-40% lower than platform dashboards. Always triangulate with blended CAC and contribution margin." + + # ───────────────────────────────────────────── + # UNIT ECONOMICS + # ───────────────────────────────────────────── + + - name: "Customer Lifetime Value (LTV)" + id: "ltv" + category: "unit-economics" + definition: "The total gross profit a customer generates over their entire relationship with the brand, reflecting the compounding value of retention and repeat purchasing." + formula: "Average Order Value x Gross Margin % x Purchase Frequency x Average Customer Lifespan (years)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $50 (general consumer); < $100 (premium)" + signal: "Customers are one-and-done buyers. The brand has no retention engine and is trapped on the acquisition treadmill." + below_average: + value: "$50-$120 (general); $100-$250 (premium)" + signal: "Low LTV relative to acquisition costs. The brand has repeat purchasers but not enough to build sustainable economics." + average: + value: "$120-$250 (general); $250-$500 (premium)" + signal: "Healthy LTV for D2C. Indicates meaningful repeat purchase behavior and sufficient gross margin to build a profitable customer base over time." + good: + value: "$250-$500 (general); $500-$1,000 (premium)" + signal: "Strong customer relationships. Repeat purchase rate and brand loyalty are working — the flywheel is spinning." + excellent: + value: "> $500 (general); > $1,000 (premium)" + signal: "Exceptional customer love. Typically seen in subscription models, consumable replenishment, or brands with cult-like followings." + stage_notes: + seed: "LTV is estimated, not proven. Use 12-month LTV based on early cohort data rather than projecting lifetime. Investors discount LTV projections beyond observed data." + series_a: "12-month LTV should be well-characterized with 2+ cohorts of data. 24-month LTV extrapolation is acceptable with strong retention curve evidence." + series_b_plus: "Full LTV modeling with cohort-based analysis, seasonal adjustment, and contribution margin (not revenue) basis. LTV should be increasing over time as brand strengthens." + data_sources: + - source: "Daasity D2C Analytics Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["ltv-cac-ratio", "repeat-purchase-rate", "purchase-frequency", "aov"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "LTV must be gross-profit-adjusted, not revenue-based. A customer with $500 in revenue but 30% gross margin has $150 LTV, not $500. Revenue-based LTV is a vanity metric that misleads capital allocation decisions." + + - name: "LTV:CAC Ratio" + id: "ltv-cac-ratio" + category: "unit-economics" + definition: "The ratio of customer lifetime value to customer acquisition cost, measuring the return on each dollar invested in acquiring a customer." + formula: "LTV (gross-profit-adjusted) / CAC (blended)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.5x" + signal: "The business destroys value with every customer acquired. Growth accelerates losses. Immediate intervention required on either LTV (retention, AOV, margin) or CAC (channel efficiency, brand investment)." + below_average: + value: "1.5x-2.5x" + signal: "Marginal economics. The business is not generating sufficient return on acquisition spend to fund growth and operations. Profitable only with very low overhead." + average: + value: "2.5x-3.5x" + signal: "Acceptable D2C economics. The business can operate profitably at current scale but has limited excess margin to fund aggressive growth." + good: + value: "3.5x-5.0x" + signal: "Strong unit economics. Sufficient margin to fund growth investment, team expansion, and brand building simultaneously." + excellent: + value: "> 5.0x" + signal: "Exceptional economics. Either the brand is under-investing in growth (spending too little on acquisition) or has built a genuinely powerful brand moat that drives organic acquisition." + stage_notes: + seed: "LTV:CAC above 2x on early cohorts is a positive signal. Below 1.5x means the business model needs fundamental restructuring before scaling." + series_a: "3x+ is the standard fundraising threshold. Investors want to see this ratio improving over time as brand equity reduces CAC and retention efforts increase LTV." + series_b_plus: "If LTV:CAC exceeds 5x at scale, investors will ask why the company is not spending more on acquisition. Extremely high ratios at scale suggest under-investment in growth." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "2PM / Web Smith DTC Research" + year: "2024" + related_metrics: ["ltv", "cac-blended", "payback-period"] + related_skills: ["business-model-canvas", "balanced-scorecard", "scenario-planning"] + caveats: "LTV:CAC is only meaningful if LTV is calculated on a gross-profit basis and CAC is fully loaded. A 5x ratio using revenue-based LTV and media-spend-only CAC is misleading — the true ratio may be under 2x." + + - name: "Payback Period" + id: "payback-period" + category: "unit-economics" + definition: "The number of months required to recoup the customer acquisition cost through gross profit from that customer's purchases." + formula: "CAC / (Monthly Revenue per Customer x Gross Margin %)" + unit: "months" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 12 months" + signal: "Capital-intensive acquisition model. The business needs significant working capital to fund growth, and any increase in churn or CAC rapidly depletes cash reserves." + below_average: + value: "6-12 months" + signal: "Moderate payback. Sustainable for subscription models with strong retention but dangerous for one-time purchase brands where repeat behavior is uncertain." + average: + value: "3-6 months" + signal: "Healthy D2C payback. The business recovers acquisition costs within two purchase cycles for most categories." + good: + value: "1-3 months" + signal: "Strong payback. First or second order covers acquisition cost. The business generates free cash flow from acquisition quickly." + excellent: + value: "< 1 month (first-order profitable)" + signal: "First-order profitability. Every new customer generates immediate positive cash flow. Rare in D2C — typically seen in high-AOV products with strong gross margins." + stage_notes: + seed: "First-order profitability is ideal but not required. Payback under 6 months is viable at seed if retention data supports it." + series_a: "Payback period under 6 months is the standard investor expectation. Demonstrate that payback is improving (shortening) over time." + series_b_plus: "Payback should be stable or decreasing. Increasing payback at scale signals channel saturation and rising acquisition costs." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "Daasity D2C Analytics Benchmarks" + year: "2024" + related_metrics: ["cac-blended", "ltv", "gross-margin", "contribution-margin"] + related_skills: ["scenario-planning", "balanced-scorecard"] + caveats: "For non-subscription D2C brands, payback period depends heavily on repeat purchase assumptions. If only 25% of customers make a second purchase, the payback period for the average customer is much longer than the formula suggests for the repeat buyer." + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "Revenue minus cost of goods sold as a percentage of revenue. In D2C, COGS includes raw materials, manufacturing, packaging, and inbound freight — but excludes fulfillment, shipping, and marketing." + formula: "(Revenue - COGS) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "Insufficient margin to fund acquisition, operations, and growth. The brand is likely competing on price in a commodity category." + below_average: + value: "40-55%" + signal: "Below D2C norms. Contribution margin after fulfillment, shipping, and returns will be thin, leaving minimal room for marketing investment." + average: + value: "55-65%" + signal: "Inline with D2C medians across most categories. Sufficient margin structure to support both paid acquisition and brand building." + good: + value: "65-75%" + signal: "Strong margins reflecting brand premium, efficient manufacturing, or high-value product categories (beauty, supplements, specialty food)." + excellent: + value: "> 75%" + signal: "Exceptional margins. Typically seen in digital-physical hybrids (low COGS products like supplements, digital courses bundled with physical goods) or genuinely premium brands." + stage_notes: + seed: "Margins are typically lower at low volume due to small-batch manufacturing and unoptimized supply chain. 50%+ is acceptable if the path to 60%+ at scale is clear." + series_a: "Gross margin should be 60%+ or on a clear trajectory. Investors model the business forward at scale margins, not current small-batch costs." + series_b_plus: "Margins should be stable or improving through manufacturing scale, supplier negotiation, and packaging optimization." + data_sources: + - source: "Shopify Commerce Reports" + year: "2024" + - source: "2PM / Web Smith DTC Research" + year: "2024" + related_metrics: ["contribution-margin", "aov", "return-rate"] + related_skills: ["business-model-canvas", "porters-five-forces"] + caveats: "D2C gross margin definitions vary. Some brands include fulfillment in COGS (creating a lower reported margin); others exclude it. For benchmarking, standardize: COGS = product cost + packaging + inbound freight only. Fulfillment and shipping are below-the-line costs in contribution margin." + + - name: "Contribution Margin" + id: "contribution-margin" + category: "financial" + definition: "The profit remaining after deducting all variable costs from revenue — COGS, fulfillment, shipping, returns processing, payment processing, and variable marketing costs. The true measure of per-order profitability." + formula: "(Revenue - COGS - Fulfillment Cost - Shipping Cost - Returns Cost - Payment Processing) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10%" + signal: "Per-order economics are barely viable or negative. The brand is subsidizing each order to acquire volume, which is unsustainable without external capital." + below_average: + value: "10-20%" + signal: "Thin margins after variable costs. Leaves minimal room for fixed overhead (team, rent, software) and no margin for error on any variable cost line." + average: + value: "20-30%" + signal: "Inline with D2C medians. Sufficient contribution margin to cover fixed costs and generate modest profit at scale." + good: + value: "30-40%" + signal: "Strong contribution margin. The brand has pricing power, efficient operations, or both. Sufficient margin to fund aggressive growth." + excellent: + value: "> 40%" + signal: "Exceptional. The brand commands a genuine premium, operates efficiently, and has low return rates. Typically seen in subscription models or high-AOV categories." + stage_notes: + seed: "Contribution margin below 15% demands immediate attention to product cost, pricing, or shipping strategy before scaling spend." + series_a: "Positive contribution margin (>15%) is a gating criterion for most D2C investors. Negative contribution margin at Series A is a red flag." + series_b_plus: "Contribution margin should be 25%+ and improving. This is the metric that proves the business can be profitable at scale." + data_sources: + - source: "Triple Whale DTC Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["gross-margin", "aov", "return-rate", "shipping-cost-pct"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "Contribution margin must include all variable costs, including returns. A brand reporting 30% contribution margin while excluding 15% return rates is overstating by 3-5 percentage points." + + - name: "Average Order Value (AOV)" + id: "aov" + category: "unit-economics" + definition: "The average dollar amount spent per transaction, reflecting pricing strategy, product mix, bundling effectiveness, and upsell/cross-sell performance." + formula: "Total Revenue / Number of Orders" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $35" + signal: "Low AOV compresses contribution margin. Fulfillment and shipping costs consume a disproportionate share. Free shipping thresholds are difficult to set profitably." + below_average: + value: "$35-$55" + signal: "Below the threshold where per-order economics reliably work. Cross-sell, bundling, and minimum-order strategies are priorities." + average: + value: "$55-$85" + signal: "Inline with D2C medians. Per-order economics are viable with standard fulfillment costs." + good: + value: "$85-$140" + signal: "Healthy AOV supporting strong contribution margins and comfortable free-shipping thresholds." + excellent: + value: "> $140" + signal: "Premium AOV. Indicates brand strength, effective bundling, or high-value product categories. Comfortable per-order economics." + stage_notes: + seed: "AOV is primarily a function of product pricing and assortment. Focus on whether AOV covers COGS + fulfillment + shipping with margin remaining." + series_a: "AOV should be stable or increasing through bundling, upsells, and product line extension. Declining AOV signals discounting dependency." + series_b_plus: "AOV optimization (dynamic bundling, personalized upsells, subscription conversion) becomes a dedicated growth lever." + data_sources: + - source: "Shopify Commerce Reports" + year: "2024" + - source: "Klaviyo E-Commerce Benchmarks" + year: "2024" + related_metrics: ["contribution-margin", "ltv", "gross-margin"] + related_skills: ["four-ps-marketing", "cialdini-influence"] + caveats: "AOV varies dramatically by category: beauty/skincare $55-$75, supplements $60-$80, apparel $80-$120, home goods $90-$150, furniture $200+. Compare within category, not across." + + # ───────────────────────────────────────────── + # RETENTION METRICS + # ───────────────────────────────────────────── + + - name: "Repeat Purchase Rate" + id: "repeat-purchase-rate" + category: "retention" + definition: "The percentage of customers who make at least one additional purchase after their first order. The fundamental measure of brand loyalty and product-market fit in D2C." + formula: "(Customers with 2+ Orders / Total Customers) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "The brand is a one-purchase experience. Without repeat buying, LTV is constrained to first-order economics, making profitable acquisition nearly impossible." + below_average: + value: "15-25%" + signal: "Below median. The product satisfies but does not compel repurchase. Investigate post-purchase experience, product quality, and whether the category naturally supports repeat buying." + average: + value: "25-35%" + signal: "Inline with D2C averages. A meaningful portion of customers return. Focus on increasing frequency among repeat buyers." + good: + value: "35-50%" + signal: "Strong loyalty. The brand has achieved emotional connection beyond the product itself. Community, brand identity, and product quality are working together." + excellent: + value: "> 50%" + signal: "Exceptional retention. Typically seen in consumable categories (supplements, beauty, food) or brands with cult-like community. The business model is fundamentally healthy." + stage_notes: + seed: "Even 20% repeat purchase rate in the first 6 months is a strong PMF signal. The rate improves as the brand strengthens and product assortment expands." + series_a: "30%+ is the investor benchmark for D2C brands. Below 25% raises questions about LTV sustainability and acquisition dependency." + series_b_plus: "Repeat rate should be stable or growing. A declining repeat rate at scale signals brand dilution through over-discounting or quality inconsistency." + data_sources: + - source: "Shopify Commerce Reports" + year: "2024" + - source: "Daasity D2C Analytics Benchmarks" + year: "2024" + related_metrics: ["purchase-frequency", "ltv", "nps"] + related_skills: ["net-promoter-score", "cialdini-influence"] + caveats: "Repeat purchase rate varies by category: consumables (beauty, food, supplements) average 35-50%; apparel 25-35%; hard goods (furniture, electronics) 10-20%. Assess within category norms." + + - name: "Purchase Frequency" + id: "purchase-frequency" + category: "retention" + definition: "The average number of purchases a customer makes within a defined time period (typically 12 months), reflecting how often customers return to buy." + formula: "Total Orders / Total Unique Customers (within time period)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.3 purchases per year" + signal: "Nearly all customers are one-time buyers. The brand does not drive habitual purchasing." + below_average: + value: "1.3-1.6 per year" + signal: "Minimal repeat behavior. Some customers return but the brand has not established a purchasing cadence." + average: + value: "1.6-2.2 per year" + signal: "Moderate frequency. Inline with D2C averages across most non-consumable categories." + good: + value: "2.2-3.5 per year" + signal: "Strong frequency indicating product-market fit and effective retention marketing. Customers are building a habit." + excellent: + value: "> 3.5 per year" + signal: "Exceptional frequency. Typically seen in consumable categories, subscription models, or brands with broad product lines that enable frequent discovery." + stage_notes: + seed: "Frequency data is limited. Focus on time-between-orders for early repeat buyers as a leading indicator." + series_a: "Demonstrate increasing frequency across cohorts — newer cohorts buying more often than older cohorts indicates improving product and experience." + series_b_plus: "Frequency optimization through personalized recommendations, new product introductions, and subscription conversion becomes a primary growth lever." + data_sources: + - source: "Daasity D2C Analytics Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["repeat-purchase-rate", "ltv", "aov"] + related_skills: ["balanced-scorecard", "net-promoter-score"] + caveats: "Frequency is category-dependent. A skincare brand should aim for 4-6x/year (replenishment cycle). A furniture brand at 1.5x/year may be excellent. Benchmark against natural repurchase cycles." + + - name: "Subscription Conversion Rate" + id: "subscription-conversion-rate" + category: "retention" + definition: "The percentage of one-time purchasers who convert to a subscription model, indicating the brand's ability to create committed, recurring customer relationships." + formula: "(Customers Converting to Subscription / Total One-Time Purchasers) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5%" + signal: "The subscription offer is not compelling. Either the value proposition is unclear, the discount insufficient, or the product does not naturally support subscription." + below_average: + value: "5-10%" + signal: "Below median. The subscription exists but has not been optimized. Likely a pricing, positioning, or funnel problem rather than a product problem." + average: + value: "10-18%" + signal: "Inline with D2C subscription averages. The offer resonates with a meaningful portion of customers." + good: + value: "18-30%" + signal: "Strong conversion. The subscription provides clear value (convenience, savings, exclusive access) that customers recognize." + excellent: + value: "> 30%" + signal: "Exceptional. The subscription is the default purchasing mode, indicating that the product and cadence alignment is excellent." + stage_notes: + seed: "Subscription can be introduced from launch for consumable products. For non-consumables, membership or VIP programs serve a similar function." + series_a: "Subscription revenue as a percentage of total should be growing. Investors love subscription because of revenue predictability." + series_b_plus: "Subscription should represent 30-50%+ of revenue for consumable brands. Focus shifts to reducing subscription churn, not just driving conversion." + data_sources: + - source: "Recharge Subscription Commerce Report" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["subscription-churn-rate", "ltv", "repeat-purchase-rate"] + related_skills: ["business-model-canvas", "cialdini-influence"] + caveats: "Applicable primarily to consumable or replenishable products. For non-consumable D2C brands, loyalty/membership programs are the analogous metric. Do not force subscription on products with irregular repurchase cycles." + + - name: "Subscription Churn Rate" + id: "subscription-churn-rate" + category: "retention" + definition: "The percentage of active subscribers who cancel their subscription within a given month, measuring the sustainability of the recurring revenue base." + formula: "(Subscribers Who Cancelled in Month / Active Subscribers at Start of Month) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 12% monthly" + signal: "Unsustainable churn. The average subscriber stays fewer than 9 months. The subscription model is destroying value — acquisition costs are not recovered before cancellation." + below_average: + value: "8-12% monthly" + signal: "High churn eroding unit economics. Subscribers are staying 8-12 months on average. Aggressive retention interventions needed." + average: + value: "5-8% monthly" + signal: "Inline with D2C subscription averages. Average subscriber lifetime of 12-20 months. Healthy but with room for improvement." + good: + value: "3-5% monthly" + signal: "Strong retention. Subscribers are staying 20-33 months on average. The product and cadence are well-matched." + excellent: + value: "< 3% monthly" + signal: "Exceptional. Average subscriber lifetime exceeds 33 months. The subscription is deeply embedded in the customer's routine." + stage_notes: + seed: "Churn data is noisy with small cohorts. Track churn by month-of-tenure — the first 3 months are always highest." + series_a: "Demonstrate that churn decreases with subscriber tenure — a flattening churn curve is the strongest retention signal." + series_b_plus: "Churn segmentation by product, plan type, and acquisition channel reveals where to invest in retention." + data_sources: + - source: "Recharge Subscription Commerce Report" + year: "2024" + - source: "Daasity D2C Analytics Benchmarks" + year: "2024" + related_metrics: ["subscription-conversion-rate", "ltv", "repeat-purchase-rate"] + related_skills: ["net-promoter-score", "systems-thinking"] + caveats: "Subscription fatigue is real. Post-2021, consumer willingness to maintain multiple subscriptions has declined. Benchmark against recent data, not 2020 pandemic-era subscription growth numbers." + + # ───────────────────────────────────────────── + # MARKETING EFFICIENCY METRICS + # ───────────────────────────────────────────── + + - name: "Email Revenue as Percentage of Total" + id: "email-revenue-pct" + category: "efficiency" + definition: "The percentage of total revenue attributable to email marketing, indicating the brand's ability to drive revenue through an owned, zero-marginal-cost channel." + formula: "(Revenue from Email Campaigns + Email Flows) / Total Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "The brand is under-leveraging its most profitable channel. Email list is likely under-built, under-segmented, or under-messaged." + below_average: + value: "15-22%" + signal: "Below median for D2C. Basic flows exist but campaign frequency, segmentation, and content quality are limiting revenue." + average: + value: "22-30%" + signal: "Inline with Klaviyo D2C averages. Core flows (welcome, abandoned cart, post-purchase, browse abandonment, win-back) are active and optimized." + good: + value: "30-40%" + signal: "Strong email performance. Both flows and campaigns are sophisticated, segmented, and driving meaningful revenue without list fatigue." + excellent: + value: "> 40%" + signal: "Exceptional. Email is a primary revenue driver. The brand has a deeply engaged list with strong open rates, click rates, and conversion rates." + stage_notes: + seed: "Email revenue below 10% is common early. Build the list and set up core flows (welcome, cart abandonment, post-purchase) before investing in campaigns." + series_a: "25%+ is expected. Investors want to see that the brand owns its customer relationship, not just rents it through paid ads." + series_b_plus: "Email revenue should be 30-40% and growing as a percentage of total. This represents the brand's most capital-efficient revenue source." + data_sources: + - source: "Klaviyo Email & SMS Benchmarks" + year: "2024" + - source: "Triple Whale DTC Benchmarks" + year: "2024" + related_metrics: ["sms-revenue-pct", "organic-traffic-pct", "cac-blended"] + related_skills: ["four-ps-marketing", "writing-effective-emails"] + caveats: "Email attribution is imperfect. Klaviyo's default attribution window (5-day click, 24-hour open) may over-count email revenue. Use a conservative attribution model (click-only) for accuracy." + + - name: "SMS Revenue as Percentage of Total" + id: "sms-revenue-pct" + category: "efficiency" + definition: "The percentage of total revenue attributable to SMS marketing, measuring the brand's effectiveness with the highest-engagement owned channel." + formula: "(Revenue from SMS Campaigns + SMS Flows) / Total Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2%" + signal: "SMS is either not implemented or severely under-leveraged. The brand is missing the highest-open-rate marketing channel." + below_average: + value: "2-5%" + signal: "SMS is active but limited. Likely only basic flows (cart abandonment) with minimal campaign activity." + average: + value: "5-10%" + signal: "Inline with D2C averages. SMS is an active channel with flows and campaigns contributing meaningfully." + good: + value: "10-15%" + signal: "Strong SMS program. Sophisticated segmentation, well-timed campaigns, and high subscriber opt-in rate." + excellent: + value: "> 15%" + signal: "Exceptional. SMS is a core revenue driver. Typically seen in brands with strong mobile-first audiences and high-engagement product categories." + stage_notes: + seed: "SMS can be introduced from day one alongside email. Even a basic cart abandonment SMS flow adds 2-3% revenue." + series_a: "5%+ SMS revenue contribution expected. Demonstrate growing SMS subscriber list alongside email list." + series_b_plus: "SMS becomes a sophisticated channel with personalization, segmentation, and A/B testing on par with email." + data_sources: + - source: "Klaviyo Email & SMS Benchmarks" + year: "2024" + - source: "Triple Whale DTC Benchmarks" + year: "2024" + related_metrics: ["email-revenue-pct", "organic-traffic-pct"] + related_skills: ["cialdini-influence", "writing-for-response"] + caveats: "SMS costs are materially higher than email ($0.01-$0.03 per message). Revenue per message must be evaluated net of costs. Over-messaging drives rapid unsubscription — frequency tolerance is lower than email." + + - name: "Organic Traffic Percentage" + id: "organic-traffic-pct" + category: "efficiency" + definition: "The percentage of total website traffic arriving through organic channels — direct, organic search, organic social, and referral — without paid acquisition spend." + formula: "(Direct + Organic Search + Organic Social + Referral Traffic) / Total Traffic x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20%" + signal: "The brand is almost entirely dependent on paid channels. Any disruption to ad platforms (cost increase, policy change, account suspension) threatens revenue immediately." + below_average: + value: "20-35%" + signal: "Heavy paid dependency. The brand has some organic demand but not enough to sustain operations without continuous ad spend." + average: + value: "35-50%" + signal: "Balanced mix. Organic traffic provides a meaningful base that paid acquisition amplifies." + good: + value: "50-65%" + signal: "Strong organic base indicating genuine brand awareness, search authority, and word-of-mouth. Paid acquisition is a growth accelerant, not a survival requirement." + excellent: + value: "> 65%" + signal: "The brand is a destination. Customers seek it out. Paid acquisition adds marginal volume to an organic-first business. This is the holy grail of D2C." + stage_notes: + seed: "Organic traffic is typically low (15-25%). Building organic takes time. Focus on seeding brand awareness through earned media, influencer relationships, and content." + series_a: "35%+ organic is a strong signal of brand-market fit. Investors see high organic as evidence that the brand has cultural resonance beyond its ad spend." + series_b_plus: "Organic should be 50%+ at scale. If organic is declining as a percentage while revenue grows, the brand is becoming more paid-dependent — a dangerous trend." + data_sources: + - source: "Shopify Commerce Reports" + year: "2024" + - source: "Triple Whale DTC Benchmarks" + year: "2024" + related_metrics: ["cac-blended", "email-revenue-pct", "community-growth-rate"] + related_skills: ["blue-ocean-strategy", "tipping-point"] + caveats: "Direct traffic is often miscategorized. Customers who see a Meta ad, remember the brand, and later type the URL directly are attributed to 'direct' but were actually paid-influenced. Post-purchase surveys ('How did you hear about us?') help calibrate." + + - name: "Social Media Engagement Rate" + id: "social-engagement-rate" + category: "brand" + definition: "The percentage of social media followers or impressions that result in meaningful interactions (likes, comments, shares, saves), measuring content resonance and community vitality." + formula: "(Total Engagements / Total Followers or Impressions) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.0% (Instagram); < 0.5% (TikTok, Facebook)" + signal: "Content is not resonating. Either the audience is disengaged, the content lacks relevance, or the account has accumulated low-quality followers." + below_average: + value: "1.0-2.0% (Instagram); 0.5-2.0% (TikTok)" + signal: "Below median. Content strategy needs recalibration toward formats and topics that drive interaction." + average: + value: "2.0-3.5% (Instagram); 2.0-5.0% (TikTok)" + signal: "Inline with D2C brand averages. Content resonates with the core audience." + good: + value: "3.5-6.0% (Instagram); 5.0-10.0% (TikTok)" + signal: "Strong engagement indicating genuine community interest. Content drives conversation, not just views." + excellent: + value: "> 6.0% (Instagram); > 10.0% (TikTok)" + signal: "Exceptional community engagement. The brand creates cultural conversation. This level of engagement correlates with high organic traffic and low CAC." + stage_notes: + seed: "Engagement rate matters more than follower count. 1,000 followers at 8% engagement is worth more than 50,000 followers at 0.5%." + series_a: "Engagement rate and follower growth together signal brand health. Investors increasingly view social engagement as a leading indicator of future organic revenue." + series_b_plus: "Engagement rate naturally declines as audience grows. Maintaining 3%+ engagement at 100K+ followers is strong." + data_sources: + - source: "Yotpo E-Commerce Benchmarks" + year: "2024" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["organic-traffic-pct", "community-growth-rate", "ugc-volume"] + related_skills: ["tipping-point", "cialdini-influence"] + caveats: "Engagement rate calculated on followers versus impressions yields very different numbers. Standardize the denominator across time periods. Platform algorithm changes also affect engagement rates independent of content quality." + + # ───────────────────────────────────────────── + # BRAND HEALTH METRICS + # ───────────────────────────────────────────── + + - name: "Net Promoter Score (NPS)" + id: "nps" + category: "brand" + definition: "The percentage of customers who are Promoters (9-10 rating) minus the percentage who are Detractors (0-6 rating), measuring brand advocacy and likelihood of word-of-mouth recommendation." + formula: "% Promoters - % Detractors" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20" + signal: "More detractors than promoters relative to the D2C norm. The brand is not creating advocacy. Investigate product quality, shipping experience, and post-purchase communication." + below_average: + value: "20-35" + signal: "Below D2C median. Customers are satisfied but not enthusiastic. The brand delivers function but not delight." + average: + value: "35-50" + signal: "Inline with D2C averages. A healthy base of promoters. Focus on converting passives to promoters through experience improvements." + good: + value: "50-70" + signal: "Strong advocacy. Promoters significantly outnumber detractors. Word-of-mouth is a meaningful acquisition channel." + excellent: + value: "> 70" + signal: "Exceptional brand love. Customers are active evangelists. NPS at this level correlates with organic growth above 50% of total acquisition." + stage_notes: + seed: "Survey every customer. Small sample sizes are fine — qualitative feedback from the open-ended question matters more than the score." + series_a: "NPS of 50+ is a powerful fundraising signal. It indicates that the product and brand have achieved emotional connection." + series_b_plus: "Segment NPS by cohort, product, and channel. Aggregate NPS can mask degradation in specific segments." + data_sources: + - source: "Yotpo E-Commerce Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["csat", "repeat-purchase-rate", "organic-traffic-pct"] + related_skills: ["net-promoter-score", "cialdini-influence"] + caveats: "NPS in D2C reflects the total brand experience — product, packaging, delivery, customer service — not just the product. Survey post-delivery (7-14 days after receipt), not post-purchase." + + - name: "Customer Satisfaction Score (CSAT)" + id: "csat" + category: "brand" + definition: "The percentage of customers who rate their experience as 'Satisfied' or 'Very Satisfied' (4-5 on a 5-point scale), measuring transactional satisfaction with specific interactions." + formula: "(Responses of 4 or 5 / Total Responses) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 70%" + signal: "Significant dissatisfaction. Multiple touchpoints in the customer experience are failing — product quality, shipping, customer service, or all three." + below_average: + value: "70-78%" + signal: "Below D2C norms. Specific experience failures are dragging the score. Investigate by touchpoint to find the weak link." + average: + value: "78-85%" + signal: "Inline with averages. Most customers are satisfied, but a meaningful percentage are not. Marginal improvements drive retention." + good: + value: "85-92%" + signal: "Strong satisfaction across the experience. The brand delivers on its promises consistently." + excellent: + value: "> 92%" + signal: "Exceptional satisfaction. Nearly every customer interaction meets or exceeds expectations. Operational excellence is embedded." + stage_notes: + seed: "CSAT is an immediate, actionable metric. Every customer interaction should be measured. Fix the lowest-scoring touchpoint first." + series_a: "85%+ CSAT demonstrates operational reliability. Investors view high CSAT as evidence of scalability — the brand can grow without degrading experience." + series_b_plus: "CSAT should be measured and compared across channels (DTC site, Amazon, wholesale) and touchpoints (purchase, delivery, returns, support)." + data_sources: + - source: "Yotpo E-Commerce Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["nps", "return-rate", "repeat-purchase-rate"] + related_skills: ["net-promoter-score", "kaizen-bpr"] + caveats: "CSAT measures satisfaction at a moment in time, not long-term loyalty. A customer can be satisfied with a return experience and still never buy again. Use alongside NPS for a complete picture." + + - name: "Influencer ROI" + id: "influencer-roi" + category: "efficiency" + definition: "The return on investment from influencer marketing, measured as revenue generated per dollar spent on influencer partnerships including fees, product gifting costs, and management overhead." + formula: "Revenue Attributed to Influencer / Total Influencer Spend (fees + gifted product cost + management)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.5x" + signal: "Influencer spend is not generating sufficient return. Likely caused by mismatched audiences, inauthentic partnerships, or paying for reach without conversion." + below_average: + value: "1.5x-3.0x" + signal: "Marginal return. Influencer is driving awareness but not converting to purchases efficiently. Attribution may be the bottleneck." + average: + value: "3.0x-5.0x" + signal: "Inline with D2C influencer marketing averages. Revenue covers spend with healthy margin." + good: + value: "5.0x-10.0x" + signal: "Strong influencer economics. Well-matched partnerships with authentic advocacy driving real purchases." + excellent: + value: "> 10.0x" + signal: "Exceptional. Typically driven by micro-influencer programs, affiliate structures with performance incentives, or organic creator advocacy without fees." + stage_notes: + seed: "Influencer ROI is highly variable. Micro-influencers (5K-50K followers) typically deliver better ROI than macro-influencers at early stage." + series_a: "Demonstrate a repeatable influencer playbook with consistent ROI, not just one-off viral hits." + series_b_plus: "Build an always-on influencer program with tiered partnerships (gifting, paid, ambassador). Track brand lift alongside direct ROI." + data_sources: + - source: "Pilothouse DTC Index" + year: "2025" + - source: "Triple Whale DTC Benchmarks" + year: "2024" + related_metrics: ["cac-by-channel", "organic-traffic-pct", "ugc-volume"] + related_skills: ["cialdini-influence", "tipping-point"] + caveats: "Influencer attribution is the weakest of all D2C marketing channels. Unique codes and links capture direct response but miss the halo effect on organic and paid performance. Consider incrementality testing to measure true impact." + + - name: "Community Size and Growth Rate" + id: "community-growth-rate" + category: "brand" + definition: "The total addressable community (email list, SMS list, social followers, loyalty program members, community platform members) and its monthly growth rate, measuring the brand's owned audience scale." + formula: "Growth Rate: (Community Size End of Month - Community Size Start of Month) / Community Size Start of Month x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 3% monthly growth; community size < 2x customer count" + signal: "Community is not growing organically. The brand is not converting interest into relationship. List building and social strategy need reinvention." + below_average: + value: "3-5% monthly growth" + signal: "Moderate growth. Community is expanding but not at a rate that will meaningfully change acquisition economics." + average: + value: "5-10% monthly growth" + signal: "Healthy community expansion. New members are arriving through both paid and organic channels." + good: + value: "10-20% monthly growth" + signal: "Strong growth. The brand is attracting a community beyond its current customer base — future buyers are opting in before purchasing." + excellent: + value: "> 20% monthly growth" + signal: "Exceptional. Community growth is outpacing customer acquisition, building a large pipeline of warm prospects and brand advocates." + stage_notes: + seed: "Build the community before launching products if possible. An email list of 5,000+ at launch provides a meaningful base for initial revenue." + series_a: "Community size should be 3-5x customer count. The gap represents future customers and brand advocates who amplify organic reach." + series_b_plus: "Community engagement rate matters more than size at scale. A 100K list with 40% open rates is worth more than a 500K list with 12% open rates." + data_sources: + - source: "Klaviyo Email & SMS Benchmarks" + year: "2024" + - source: "Shopify Commerce Reports" + year: "2024" + related_metrics: ["organic-traffic-pct", "email-revenue-pct", "social-engagement-rate"] + related_skills: ["tipping-point", "cialdini-influence"] + caveats: "Community size includes both active and dormant members. Segment by engagement level. A list of 50,000 where 40,000 have not opened an email in 90 days is a 10,000-person list with noise." + + - name: "User-Generated Content Volume" + id: "ugc-volume" + category: "brand" + definition: "The volume of customer-created content (photos, videos, reviews, social posts, testimonials) produced organically or through structured programs, measuring brand advocacy and social proof generation." + formula: "Count of unique UGC pieces created per month (reviews + social posts + photos + videos)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 50 pieces/month at 10K+ customer base" + signal: "Customers are not motivated to share. The product or experience does not create share-worthy moments." + below_average: + value: "50-150 pieces/month" + signal: "Some organic content creation but insufficient for use in paid creative, product pages, and social proof at scale." + average: + value: "150-500 pieces/month" + signal: "Healthy UGC flow. Sufficient for rotating social proof on product pages and feeding paid creative with authentic assets." + good: + value: "500-2,000 pieces/month" + signal: "Strong UGC program. The brand creates share-worthy experiences (packaging, product, community) and has structured systems to collect and amplify content." + excellent: + value: "> 2,000 pieces/month" + signal: "Exceptional content engine. The community creates more content than the brand's internal team. UGC is a primary source of paid creative and social proof." + stage_notes: + seed: "Every early customer is a potential content creator. Send personalized requests for reviews and photos. Gifting programs seed UGC before organic volume builds." + series_a: "UGC should be integrated into the marketing funnel: product pages (reviews/photos), paid ads (creator content), and social media (reposts). Volume should scale with customer base." + series_b_plus: "Build a structured UGC program with tiers: organic (unboxing moments), incentivized (loyalty program rewards), and paid (creator partnerships)." + data_sources: + - source: "Yotpo E-Commerce Benchmarks" + year: "2024" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["social-engagement-rate", "community-growth-rate", "influencer-roi"] + related_skills: ["cialdini-influence", "tipping-point"] + caveats: "Quality matters more than quantity. One authentic video review from a real customer outperforms 100 incentivized star ratings. Track UGC impact on conversion rate and paid creative performance." + + # ───────────────────────────────────────────── + # OPERATIONAL METRICS + # ───────────────────────────────────────────── + + - name: "Return Rate" + id: "return-rate" + category: "efficiency" + definition: "The percentage of orders returned by customers, representing a direct cost to contribution margin and a signal of product-expectation alignment." + formula: "(Number of Returned Orders / Total Orders Shipped) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 30% (apparel); > 15% (non-apparel)" + signal: "Return rate is destroying contribution margin. Product descriptions, photography, or sizing are fundamentally misaligned with customer expectations." + below_average: + value: "20-30% (apparel); 10-15% (non-apparel)" + signal: "Above median returns. Investigate top return reasons: fit issues (sizing guide problem), quality expectations (photography vs. reality), or damage (packaging problem)." + average: + value: "12-20% (apparel); 5-10% (non-apparel)" + signal: "Inline with D2C category averages. Returns are a manageable cost but optimization can meaningfully improve contribution margin." + good: + value: "8-12% (apparel); 3-5% (non-apparel)" + signal: "Low return rate indicating strong product-expectation alignment. Sizing guides, product photography, and descriptions are working." + excellent: + value: "< 8% (apparel); < 3% (non-apparel)" + signal: "Exceptional. The product consistently meets or exceeds expectations. This level of return performance is a meaningful competitive advantage." + stage_notes: + seed: "High return rates early often reflect product development issues (fit, quality) that should be fixed before scaling. Every return is a learning opportunity." + series_a: "Return rate should be trending down through product improvement, better photography, and sizing/fit technology. Returns below category median is a strong signal." + series_b_plus: "Returns management becomes a P&L lever. Exchange programs, store credit incentives, and returnless refunds (for low-cost items) optimize the cost of returns." + data_sources: + - source: "Narvar Returns & Exchanges Report" + year: "2024" + - source: "Loop Returns Industry Data" + year: "2024" + related_metrics: ["contribution-margin", "gross-margin", "csat"] + related_skills: ["kaizen-bpr", "systems-thinking"] + caveats: "Return rate varies dramatically by category: apparel 15-30%, footwear 18-25%, electronics 8-12%, beauty 3-8%, supplements 2-5%, food <2%. Always benchmark within category." + + - name: "Brand Awareness (Aided and Unaided)" + id: "brand-awareness" + category: "brand" + definition: "The percentage of target market consumers who recognize (aided) or spontaneously recall (unaided) the brand name, measuring top-of-funnel brand penetration." + formula: "Aided: % of survey respondents who recognize brand when prompted. Unaided: % who name brand unprompted when asked about the category." + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "Aided < 5%; Unaided < 1% in target demographic" + signal: "The brand is functionally invisible in its category. All customer acquisition must be paid because no organic demand exists." + below_average: + value: "Aided 5-15%; Unaided 1-3%" + signal: "Emerging awareness. A small base knows the brand but it is not yet part of the category conversation." + average: + value: "Aided 15-30%; Unaided 3-8%" + signal: "Meaningful awareness within the target demographic. The brand appears in consideration sets." + good: + value: "Aided 30-50%; Unaided 8-15%" + signal: "Strong awareness. The brand is a recognized name in the category. Organic search volume and direct traffic reflect this position." + excellent: + value: "Aided > 50%; Unaided > 15%" + signal: "Category-defining awareness. The brand is synonymous with the category for a meaningful portion of the target market." + stage_notes: + seed: "Formal brand awareness studies are premature. Use proxy metrics: branded search volume (Google Trends), direct traffic percentage, and 'how did you hear about us' surveys." + series_a: "Brand awareness should be measured within the specific target demographic, not the general population. A niche brand with 40% aided awareness in its target is strong." + series_b_plus: "Track awareness over time with consistent methodology. Awareness gains correlate with declining CAC and increasing organic traffic percentage." + data_sources: + - source: "2PM / Web Smith DTC Research" + year: "2024" + - source: "Pilothouse DTC Index" + year: "2025" + related_metrics: ["organic-traffic-pct", "cac-blended", "community-growth-rate"] + related_skills: ["blue-ocean-strategy", "tipping-point", "story-structure-and-arc"] + caveats: "Brand awareness surveys are expensive and methodologically tricky. For brands under $10M revenue, proxy metrics (branded search volume, direct traffic %, post-purchase surveys) are more practical than formal studies." + + - name: "Shipping Cost as Percentage of Revenue" + id: "shipping-cost-pct" + category: "efficiency" + definition: "Total shipping and fulfillment cost (outbound shipping, fulfillment labor, packaging materials, 3PL fees) as a percentage of revenue, measuring operational efficiency." + formula: "(Outbound Shipping + Fulfillment Cost + Packaging) / Revenue x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 20%" + signal: "Shipping and fulfillment are consuming a destructive share of revenue. Low AOV, expensive products to ship, or inefficient fulfillment operations." + below_average: + value: "15-20%" + signal: "Above median. Investigate free-shipping thresholds, packaging optimization, carrier rate negotiation, and 3PL alternatives." + average: + value: "10-15%" + signal: "Inline with D2C averages for most categories. Room for optimization but not a crisis." + good: + value: "7-10%" + signal: "Efficient operations. Strong carrier relationships, optimized packaging, and effective free-shipping thresholds." + excellent: + value: "< 7%" + signal: "Exceptional fulfillment efficiency. Typically achieved at scale with multi-warehouse operations or lightweight/high-AOV products." + stage_notes: + seed: "Shipping costs are high at low volume. Negotiate rates as volume increases and consider 3PLs that aggregate volume across clients." + series_a: "Shipping cost below 15% of revenue demonstrates operational competence. Declining trend is expected." + series_b_plus: "Multi-warehouse strategy, regional fulfillment, and zone-based shipping optimization become material levers at scale." + data_sources: + - source: "Shopify Commerce Reports" + year: "2024" + - source: "Triple Whale DTC Benchmarks" + year: "2024" + related_metrics: ["contribution-margin", "aov", "return-rate"] + related_skills: ["kaizen-bpr", "systems-thinking"] + caveats: "Free shipping is a customer expectation but a margin killer for low-AOV brands. Model the contribution margin impact of free shipping versus paid shipping versus free-shipping-with-threshold for accurate decision-making." diff --git a/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-diagnostic-rules.yaml new file mode 100644 index 0000000..36ae7e0 --- /dev/null +++ b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-diagnostic-rules.yaml @@ -0,0 +1,726 @@ +# D2C Consumer Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in a D2C context. +# The diagnostic agent loads these rules when the D2C industry pack is active. +# +# D2C-specific diagnostic themes that recur across multiple diagnostics: +# - CAC death spiral: rising acquisition costs eating margin, forcing more +# spending to maintain revenue, which further increases CAC +# - Brand dilution: discounting, channel proliferation, and audience broadening +# weakening the brand's identity and pricing power +# - Community fatigue: over-monetizing the community until engagement collapses +# - Subscription churn cliff: subscribers canceling in waves at predictable tenure +# - iOS attribution blindness: inability to measure channel-level performance +# leading to misallocated spend +# - Influencer dependency: brand growth tied to a small number of creators +# - Amazon channel conflict: selling on Amazon while trying to build a DTC brand +# - Content-commerce disconnect: brand content that builds awareness but does not +# convert, or commerce content that converts but does not build brand +# - Return rate crisis: high returns destroying contribution margin +# - Discount addiction: training customers to wait for sales instead of buying +# at full price +# +# Adaptation types: +# as-is — The diagnostic works without modification for D2C companies. +# enhanced — The diagnostic is relevant but benefits from additional D2C-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for D2C. + +pack_metadata: + sector: "d2c-consumer" + display_name: "D2C Consumer" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "D2C 'churn' manifests differently than in subscription businesses. The majority of D2C customers are one-time purchasers who never return — the question is not 'why did they cancel?' but 'why did they not come back?' For subscription D2C brands, churn has distinct patterns: subscription fatigue, product accumulation (too much product stockpiled), and identity misalignment (the customer no longer identifies with the brand). The diagnostic must address both non-return (one-time purchase models) and cancellation (subscription models)." + additional_triage_questions: + - question: "What percentage of your customers make a second purchase? What is the median time between first and second purchase?" + purpose: "In D2C, the first-to-second purchase conversion is the most critical retention metric. It distinguishes brands with genuine customer relationships from brands running an acquisition treadmill." + routing_impact: "Second purchase rate below 20% routes to product-market-fit-diagnosis and net-promoter-score analysis. Rate above 30% with declining trend routes to experience degradation investigation." + - question: "For customers who do not repurchase, what is the primary reason — product dissatisfaction, price sensitivity, forgotten brand, or product not needed again?" + purpose: "Each non-return reason requires a different intervention: product improvement, pricing restructuring, retention marketing, or assortment expansion." + routing_impact: "Product dissatisfaction routes to net-promoter-score and return-rate analysis. Price sensitivity routes to pricing-diagnosis. Forgotten brand routes to email/SMS strategy and community building. Not needed again routes to assortment expansion and category strategy." + - question: "If you have subscriptions, when do subscribers cancel — within the first 3 months (trial failure), at months 4-6 (product accumulation), or after 6+ months (subscription fatigue)?" + purpose: "Subscription churn timing reveals the root cause. Early churn is product or expectation failure. Mid-tenure churn is often product accumulation. Late churn is subscription fatigue or competitive switching." + routing_impact: "Early churn routes to onboarding and first-box experience optimization. Mid-tenure routes to subscription flexibility (skip, swap, pause options). Late churn routes to community investment and loyalty deepening." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Discount-acquired customers churning at higher rates" + reason: "D2C customers acquired through deep discounts have 30-50% lower repeat purchase rates than full-price customers. Discount acquisition selects for price-sensitive buyers with no brand loyalty." + - diagnosis: "Post-purchase experience failure" + reason: "In D2C, the experience between purchase and repurchase — shipping speed, packaging quality, post-purchase communication — determines whether the customer returns. Product quality alone is insufficient." + less_likely: + - diagnosis: "Feature or functionality gap" + reason: "D2C products are physical goods. Customers rarely churn because of missing 'features.' They churn because the product did not match expectations, the experience disappointed, or they forgot the brand exists." + d2c_specific_diagnoses: + - name: "Discount addiction eroding full-price demand" + description: "The brand has trained customers to expect discounts by running frequent sales, welcome discount codes, and promotional events. Full-price conversion rate has declined as customers learn to wait for the next promotion. The customer file splits into two populations: a shrinking group of full-price loyalists and a growing group of deal-seekers who only buy on sale." + symptoms: + - "Percentage of orders with a discount code exceeding 50%" + - "Full-price conversion rate declining quarter-over-quarter" + - "Revenue spikes during sales periods with dead zones between them" + - "Customer segments showing bimodal purchasing behavior (full-price loyalists vs. discount-only buyers)" + routes_to_skills: ["four-ps-marketing", "cialdini-influence", "systems-thinking"] + routes_to_templates: ["action-plan", "decision-rationale-memo"] + - name: "Subscription churn cliff at months 3-4" + description: "Subscribers are canceling en masse at the 3-4 month mark, suggesting that the initial subscription commitment (often encouraged by a heavy first-month discount) does not translate into sustained value perception. Product accumulation, subscription fatigue, or lack of variety drives cancellation." + symptoms: + - "Subscription churn concentrated at months 3-4 (visible in cohort analysis)" + - "Significant first-order discount on subscriptions (30%+ off first box)" + - "Customers reporting 'too much product' or 'still have some left' as cancellation reasons" + - "No subscription flexibility options (skip, pause, swap)" + routes_to_skills: ["business-model-canvas", "net-promoter-score", "systems-thinking"] + routes_to_templates: ["unit-economics-snapshot", "action-plan"] + - name: "Return rate crisis destroying contribution margin" + description: "Return rates have risen to a level that materially erodes contribution margin. Each return costs the brand the outbound shipping, return shipping, restocking labor, and often the product itself (unsellable after return). At 25%+ return rates, the brand may be losing money on every sale even with healthy gross margins." + symptoms: + - "Return rate above category benchmarks and rising" + - "Contribution margin declining despite stable gross margin" + - "Customer reviews citing 'not as pictured' or 'different from expected'" + - "Return rate higher for paid acquisition customers than organic customers" + routes_to_skills: ["kaizen-bpr", "systems-thinking", "net-promoter-score"] + routes_to_templates: ["action-plan", "incident-postmortem"] + sector_red_flags: + - "Repeat purchase rate declining for 3+ consecutive cohorts — the brand is getting worse at creating loyalty, not better." + - "Subscription churn above 10% monthly sustained for 3+ months — the subscription model is fundamentally broken." + - "Return rate increasing while ad spend increases — a sign that broader targeting reaches less-aligned customers who return at higher rates." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C growth stalls have characteristic patterns driven by channel saturation, brand lifecycle, and the economics of paid acquisition. Unlike SaaS, where growth stalls often trace to a single metric (NRR, activation rate), D2C stalls are frequently multi-causal — rising CAC, declining creative performance, and brand fatigue can compound simultaneously." + additional_triage_questions: + - question: "Has your blended CAC increased, your ROAS decreased, or both over the last 3-6 months?" + purpose: "Rising CAC and declining ROAS are the most common growth stall triggers in D2C. They can result from channel saturation, creative fatigue, audience exhaustion, or platform algorithm changes." + routing_impact: "Rising CAC with stable ROAS routes to channel diversification strategy. Declining ROAS with stable spend routes to creative refresh and brand investment. Both deteriorating routes to systems-thinking for holistic analysis." + - question: "What percentage of your revenue comes from paid acquisition versus owned channels (email, SMS, organic) and repeat customers?" + purpose: "A brand stalling at 70%+ paid acquisition dependency has a structural problem — it has built a customer rental business, not a brand. Growth stalls when paid channels saturate." + routing_impact: "Heavy paid dependency (>60%) routes to brand investment strategy and community building. Balanced mix with stalling growth routes to product assortment and market expansion analysis." + - question: "Has your ad creative performance declined — are winning ads fatiguing faster and new ads performing worse than historical norms?" + purpose: "Creative fatigue is the most underdiagnosed growth stall in D2C. When the audience has seen every angle, testimonial, and hook, new creative performs worse and CAC rises. This is a creative problem, not a media buying problem." + routing_impact: "Creative fatigue routes to creative-practice-and-habit and UGC strategy. Stable creative performance with stalling growth routes to market saturation analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Channel saturation" + reason: "D2C brands frequently exhaust their primary paid channel (typically Meta) and must either diversify to new channels (TikTok, Google, influencer, podcast) or shift investment toward organic growth." + - diagnosis: "Brand lifecycle maturity" + reason: "D2C brands follow a lifecycle: insurgent novelty, cultural adoption, mainstream saturation, and staleness. Growth stalls often coincide with the transition from adoption to saturation." + less_likely: + - diagnosis: "Product quality decline" + reason: "Growth stalls in D2C are rarely caused by product quality deterioration. They are almost always distribution, brand, or creative problems." + d2c_specific_diagnoses: + - name: "CAC death spiral" + description: "The brand is trapped in a reinforcing loop: rising acquisition costs compress margins, which reduces the budget available for brand building, which increases dependence on paid acquisition, which further raises CAC. The brand spends more to acquire fewer customers at lower margins, accelerating toward unprofitability." + symptoms: + - "Blended CAC increasing for 3+ consecutive months" + - "ROAS declining across all paid channels simultaneously" + - "Brand investment (content, community, PR) being cut to fund paid acquisition" + - "Organic traffic declining as a percentage of total while paid traffic increases" + - "Contribution margin shrinking as CAC consumes more of each order's value" + routes_to_skills: ["systems-thinking", "blue-ocean-strategy", "tipping-point"] + routes_to_templates: ["strategic-analysis-one-pager", "action-plan"] + - name: "iOS attribution blindness" + description: "The brand cannot accurately measure channel-level performance due to iOS ATT (App Tracking Transparency) and platform privacy changes. Media buyers are operating on inaccurate data — platform-reported ROAS diverges from actual business performance, leading to misallocated spend and inability to identify which channels are truly working." + symptoms: + - "Platform-reported ROAS diverges 30%+ from actual business-level ROAS" + - "CAC calculated from platform data does not reconcile with blended CAC from financial data" + - "Increasing spend on channels that platform data says are performing but business results do not confirm" + - "Inability to explain revenue changes through channel-level data" + routes_to_skills: ["balanced-scorecard", "systems-thinking", "scenario-planning"] + routes_to_templates: ["action-plan", "new-initiative-brief"] + sector_red_flags: + - "Blended CAC increasing for 4+ consecutive months — the acquisition engine is losing efficiency and no channel adjustment will fix it without brand investment." + - "Creative win rate (percentage of new ads that meet ROAS threshold) declining below 15% — creative exhaustion is the bottleneck." + - "Organic traffic declining as a percentage of total while revenue grows — the brand is becoming more paid-dependent, which is fragile and unsustainable." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C product-market fit is BRAND-market fit. A product that customers like but do not love is not PMF — it is a commodity. True D2C PMF manifests as emotional attachment to the brand, organic advocacy, and repeat purchasing driven by identity, not just utility." + additional_triage_questions: + - question: "If your brand disappeared tomorrow, would your customers genuinely miss it — or would they simply buy an alternative? How do you know?" + purpose: "This question forces honesty about whether the brand has achieved emotional connection (PMF) or merely functional adequacy (commodity). NPS Promoters who cite the brand's values, community, or identity signal true PMF." + routing_impact: "Customers would not miss the brand routes to fundamental brand strategy work. Customers would miss it routes to distribution and growth strategy." + - question: "What percentage of your growth is organic — word-of-mouth, direct traffic, social mentions, and unpaid referrals?" + purpose: "Organic growth above 40% is the strongest PMF signal in D2C. Below 20% suggests the product is not generating advocacy." + routing_impact: "Organic below 20% routes to brand and product reassessment. Above 40% routes to scaling and distribution strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Product-market fit exists for a niche but the brand is targeting too broadly" + reason: "D2C brands frequently have PMF with a specific identity group (e.g., 'outdoor-active women who value sustainability') but dilute it by targeting everyone." + - diagnosis: "Brand-market fit absent despite product satisfaction" + reason: "Customers may like the product but feel no emotional connection to the brand. They buy once but do not return because the brand is forgettable." + less_likely: + - diagnosis: "Product is fundamentally flawed" + reason: "If any customers love the product (repeat purchase + NPS 9-10), the product works for someone. The question is whether the brand and distribution can reach enough of those people." + d2c_specific_diagnoses: + - name: "Product-market fit without brand-market fit" + description: "Customers like the product — ratings are high, return rates are low, and initial purchase intent is strong. But the brand has not built emotional connection: repeat purchase rate is low, NPS is mediocre, and organic growth is minimal. The product is a commodity with good reviews, not a brand with loyal customers." + symptoms: + - "Average product rating above 4.0 stars but repeat purchase rate below 20%" + - "NPS in the 20-35 range (satisfied, not enthusiastic)" + - "Organic traffic below 25% of total" + - "Customer reviews praise the product but never mention the brand by name" + routes_to_skills: ["story-structure-and-arc", "creative-identity-and-purpose", "tipping-point"] + routes_to_templates: ["strategic-analysis-one-pager", "new-initiative-brief"] + sector_red_flags: + - "Repeat purchase rate below 15% after 12 months — customers are not coming back regardless of acquisition efficiency." + - "NPS below 35 — customers are not enthusiastic enough to advocate." + - "Organic traffic below 20% — the brand is not generating pull demand." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Pricing in D2C is a brand signal, not a cost-plus calculation. The price tells the customer who the brand is for and what it stands for. Under-pricing signals commodity positioning and traps the brand in a CAC race. Over-pricing without brand justification creates sticker shock. The diagnostic must address pricing as brand strategy, not just margin optimization." + additional_triage_questions: + - question: "How does your price compare to the Amazon equivalent for a functionally similar product? What justifies the premium?" + purpose: "D2C brands must charge a premium over commodity alternatives to fund brand building, customer experience, and direct distribution. If the premium is not justified by brand, experience, or quality, customers eventually discover the cheaper alternative." + routing_impact: "No clear premium justification routes to brand strategy and value proposition development. Clear premium with low conversion routes to value communication improvement." + - question: "What percentage of orders include a discount code, and what is the average discount depth?" + purpose: "If more than 40% of orders use discount codes, the brand has a pricing problem disguised as a promotion strategy. Customers have learned that full price is a suggestion." + routing_impact: "High discount frequency routes to discount weaning strategy and pricing restructuring. Low discount frequency with conversion concerns routes to value communication and social proof investment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Under-pricing eroding brand perception" + reason: "Many D2C brands price too low in an attempt to compete with Amazon, destroying the margin needed for brand building and signaling commodity positioning." + - diagnosis: "Discount dependency masking pricing failure" + reason: "Frequent discounts generate revenue spikes but train price-sensitivity. The 'real' price is the discounted price — the listed price is fiction." + less_likely: + - diagnosis: "Over-pricing relative to value" + reason: "D2C customers buying directly from brands expect to pay a premium for the brand experience. Over-pricing is less common than under-pricing in D2C." + d2c_specific_diagnoses: + - name: "Discount addiction spiral" + description: "The brand has created a dependency on promotional pricing. Customers have learned to wait for sales, welcome codes are shared publicly on coupon sites, and full-price conversion rate has collapsed. The brand cannot reduce discounting without an immediate revenue drop, creating a trap." + symptoms: + - "More than 50% of orders using a discount code" + - "Full-price conversion rate declining for 3+ months" + - "Discount codes appearing on Honey, RetailMeNot, and other coupon aggregators" + - "Revenue concentrated in sale periods with dead periods between promotions" + - "Average selling price declining while listed price is unchanged" + routes_to_skills: ["systems-thinking", "four-ps-marketing", "prisoners-dilemma-and-cooperation"] + routes_to_templates: ["action-plan", "decision-rationale-memo"] + sector_red_flags: + - "Average discount depth exceeding 25% across all orders — the brand is giving away its margin." + - "Price below 2x COGS — insufficient margin to fund acquisition, fulfillment, and brand building." + - "Price within 10% of Amazon alternatives without clear brand differentiation — the brand will lose to Amazon on convenience." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C fundraising has shifted dramatically since 2021. Investors who once valued top-line growth now demand path to profitability, strong unit economics, and proof of brand moat. D2C companies must demonstrate that the brand is an asset — not just that the product sells — and that the business can be profitable without indefinite venture capital." + additional_triage_questions: + - question: "What is your contribution margin after all variable costs (COGS, fulfillment, shipping, returns, payment processing, customer acquisition)? Is it positive?" + purpose: "Positive contribution margin is a gating criterion for D2C fundraising in 2024-2026. Negative contribution margin at Series A is nearly disqualifying. Investors have been burned by D2C brands that grew revenue while losing money on every order." + routing_impact: "Negative contribution margin routes to unit economics fix before fundraising. Positive margin routes to growth strategy and fundraising execution." + - question: "What is your organic traffic percentage, repeat purchase rate, and NPS? Can you demonstrate that customers love the brand, not just the product?" + purpose: "These three metrics together measure brand strength — the asset D2C investors are underwriting. Strong product metrics with weak brand metrics signal a commodity business that cannot sustain margins at scale." + routing_impact: "Weak brand metrics routes to brand-building investment before fundraising. Strong brand metrics routes to fundraising deck preparation with brand narrative emphasis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Unit economics not ready for fundraising" + reason: "The most common D2C fundraising failure is attempting to raise with negative or marginal contribution margin. Post-2021, investors require unit economics proof, not just growth." + - diagnosis: "Brand narrative absent from fundraising story" + reason: "D2C pitches that lead with revenue and growth without articulating why the brand is defensible fail to differentiate from the hundreds of D2C brands that raised in 2019-2021 and subsequently struggled." + less_likely: + - diagnosis: "Market too small" + reason: "Consumer markets are generally large enough for venture returns. The 'market too small' objection in D2C usually means the brand has not articulated its expansion path (categories, channels, geographies)." + d2c_specific_diagnoses: + - name: "Revenue-rich, brand-poor pitch" + description: "The company has impressive revenue numbers but cannot articulate why the brand is defensible, why customers love it, or how it will maintain margins at scale. Investors see a commerce business that happens to sell through a website, not a brand business with a moat." + symptoms: + - "Investor meetings ending with 'impressive growth but what's the moat?' feedback" + - "Pitch deck heavy on financial charts but light on brand story, community data, and customer advocacy metrics" + - "Organic traffic below 30% of total — signaling paid-acquisition dependency" + - "No community metrics (NPS, repeat rate, UGC volume) in the pitch materials" + routes_to_skills: ["story-structure-and-arc", "blue-ocean-strategy", "business-model-canvas"] + routes_to_templates: ["fundraising-deck-outline", "market-opportunity-summary"] + sector_red_flags: + - "Negative contribution margin at Series A stage — most D2C investors will not engage." + - "LTV:CAC below 2x — the business destroys value with every customer acquired." + - "Organic traffic below 25% — the brand has no pull demand, only rented attention." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C revenue decomposes into components that reveal business health: new customer revenue (acquisition engine), repeat customer revenue (brand loyalty), subscription revenue (committed relationship), email/SMS revenue (owned channel), and channel-level revenue (DTC vs. Amazon vs. wholesale). Each component has different economics and different implications." + additional_triage_questions: + - question: "What percentage of this month's revenue came from new customers versus repeat customers? How has this ratio trended over the last 6 months?" + purpose: "A healthy D2C brand should see repeat revenue growing as a percentage over time. If new customer revenue consistently dominates (>70%), the brand has not built retention — it is on an acquisition treadmill." + routing_impact: "High new-customer dependency routes to retention strategy (email, community, loyalty). Healthy repeat mix with stalling growth routes to acquisition channel expansion." + - question: "What percentage of revenue comes from email and SMS versus paid advertising?" + purpose: "Email/SMS revenue is the most profitable revenue in D2C. If it represents less than 20% of total, the brand is under-monetizing its owned audience." + routing_impact: "Low email/SMS revenue routes to email/SMS strategy development. Already strong routes to optimization and list growth." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Revenue quality declining as volume grows" + reason: "D2C brands scaling through discounts and broad paid targeting often see total revenue grow while revenue quality (contribution margin per order, repeat purchase rate of new cohorts) declines." + less_likely: + - diagnosis: "Market demand decline" + reason: "Consumer markets rarely collapse. Revenue decline in D2C is almost always a brand, channel, or execution problem — not a market problem." + d2c_specific_diagnoses: + - name: "Channel cannibalization destroying margins" + description: "Expansion into Amazon, wholesale, or retail is cannibalizing higher-margin DTC revenue. Customers who would have purchased on the DTC site at full margin are instead buying through lower-margin channels. Total revenue may grow but total contribution margin declines." + symptoms: + - "DTC revenue declining or flat while Amazon/wholesale revenue grows" + - "Blended contribution margin declining despite growing revenue" + - "Brand searches converting to Amazon purchases (customers Google the brand name and buy on Amazon)" + - "Wholesale partners discounting below the DTC site price" + routes_to_skills: ["business-model-canvas", "porters-five-forces", "scenario-planning"] + routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + sector_red_flags: + - "Repeat customer revenue declining as a percentage of total for 3+ months — the brand is losing loyalty." + - "Email/SMS revenue below 15% of total — the brand is under-monetizing its owned audience." + - "Revenue growing while contribution margin declines — the growth is unprofitable." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C competitive threats come from three directions simultaneously: direct D2C competitors (other brands in the same category), Amazon private label (Amazon Basics, Solimo, and hundreds of white-label products), and incumbent consumer brands launching DTC channels. The barrier to entry is near zero, meaning new competitors emerge constantly." + additional_triage_questions: + - question: "Is the competitive threat from another D2C brand, from Amazon private label entering your category, from a traditional brand launching a DTC channel, or from a retailer creating a private-label alternative?" + purpose: "Each threat type requires a different response. D2C competitors require brand differentiation. Amazon requires category defensibility. Incumbent DTC requires speed and community advantage. Retailer private label requires channel strategy." + routing_impact: "D2C competitor routes to blue-ocean-strategy and brand deepening. Amazon threat routes to brand moat analysis and community investment. Incumbent DTC routes to first-mover-strategy and community advantage leverage." + - question: "Are customers switching to the competitor on price, brand, product quality, or convenience?" + purpose: "Understanding the switching dimension determines the response. Price switching requires brand premium justification. Brand switching requires brand revitalization. Quality switching requires product improvement. Convenience switching requires experience and distribution investment." + routing_impact: "Price switching routes to pricing-diagnosis and value communication. Brand switching routes to creative-identity-and-purpose and story-structure-and-arc. Convenience switching routes to fulfillment and channel strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Amazon private label entering the category" + reason: "Amazon systematically identifies high-volume D2C categories and launches private-label alternatives at 30-50% lower prices. This is the existential competitive threat for any D2C brand without a genuine brand moat." + - diagnosis: "Competitor outspending on paid acquisition" + reason: "A well-funded D2C competitor can outbid on paid channels, driving up the CAC for everyone in the category. This is a prisoner's dilemma that the better-funded player typically wins." + less_likely: + - diagnosis: "Technology disruption" + reason: "D2C competitive advantages are brand and distribution, not technology. Technology disruptions (AI, AR try-on) are opportunities for differentiation, not existential threats." + d2c_specific_diagnoses: + - name: "Amazon channel conflict undermining brand" + description: "The brand sells on both its DTC site and Amazon. Amazon is growing faster but at lower margins, customers are migrating from DTC to Amazon for convenience, and the brand is losing control of pricing, customer data, and brand presentation. The Amazon listing has become the primary brand touchpoint — and the brand does not control it." + symptoms: + - "Amazon revenue growing while DTC revenue declines" + - "Branded search terms leading to Amazon purchases (visible in Google Search Console)" + - "Unauthorized resellers or gray market sellers on Amazon competing with the brand's own listing" + - "Amazon suggesting competitor products on the brand's own product page" + - "Customer reviews on Amazon diverging from DTC reviews (different expectations, different populations)" + routes_to_skills: ["porters-five-forces", "prisoners-dilemma-and-cooperation", "business-model-canvas"] + routes_to_templates: ["competitive-landscape-brief", "decision-rationale-memo"] + sector_red_flags: + - "Amazon private label launching in your category with similar product specs at 40%+ lower price." + - "A competitor raising $20M+ and dramatically increasing paid media spend in your category — expect CAC to rise for everyone." + - "Unauthorized sellers appearing on Amazon with your product at below-MAP pricing." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C strategic drift most commonly manifests as brand dilution — the gradual expansion of the brand's positioning until it stands for everything and means nothing. Drift occurs through SKU proliferation, audience broadening, discount dependency, and channel expansion without brand coherence." + additional_triage_questions: + - question: "Has the brand expanded into product categories or customer segments that are inconsistent with its founding identity? Does the brand still stand for something specific?" + purpose: "Brand dilution is the most dangerous form of strategic drift in D2C. A brand that started as 'premium minimalist skincare for women who reject complexity' and expanded into 'affordable beauty products for everyone' has drifted from its positioning." + routing_impact: "Brand dilution routes to creative-identity-and-purpose and business-model-canvas for brand re-anchoring. Consistent positioning routes to operational drift investigation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Brand dilution through SKU proliferation" + reason: "D2C brands frequently expand their product assortment to drive AOV and frequency, adding SKUs that are inconsistent with the brand's identity. More products means a less focused brand." + - diagnosis: "Channel drift weakening brand coherence" + reason: "Selling through Amazon, wholesale, and retail simultaneously creates pressure to accommodate different audiences, price points, and presentation standards — diluting the DTC brand experience." + less_likely: + - diagnosis: "Market disruption causing involuntary drift" + reason: "D2C strategic drift is almost always self-inflicted — expansion choices, not market forces." + d2c_specific_diagnoses: + - name: "Brand dilution through category overextension" + description: "The brand has expanded from its core category into adjacent categories too quickly, losing the specificity that made it special. Customers no longer know what the brand stands for. The original community feels alienated. New categories underperform because the brand has no authority in them." + symptoms: + - "Launched 3+ new product categories in 12 months" + - "New category products underperforming the core category by 50%+" + - "NPS declining among original customer cohorts" + - "Brand perception surveys showing confusion ('I don't know what they're really about anymore')" + - "Social media engagement declining as content shifts from focused to broad" + routes_to_skills: ["blue-ocean-strategy", "product-life-cycle", "creative-identity-and-purpose"] + routes_to_templates: ["strategic-analysis-one-pager", "quarterly-strategic-review"] + sector_red_flags: + - "NPS declining among the founding customer segment — the core audience that built the brand is losing enthusiasm." + - "Brand search volume plateauing while the product catalog doubles — more products are not generating more brand interest." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C team dysfunction often centers on the tension between creative/brand and performance/acquisition teams. The creative team wants to build the brand through content and storytelling; the performance marketing team wants to optimize ROAS through direct-response ads. Without alignment, these functions work at cross-purposes." + additional_triage_questions: + - question: "Is there tension between brand/creative and performance marketing — do these teams have conflicting goals or metrics?" + purpose: "The brand-performance tension is the most common and most damaging team dysfunction in D2C. Creative teams measured on brand metrics and performance teams measured on ROAS will inevitably conflict." + routing_impact: "Brand-performance misalignment routes to balanced-scorecard for unified metrics and strategic-thinking-and-alignment for goal alignment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Creative-performance misalignment" + reason: "D2C companies often separate brand and performance marketing into different teams with different goals, creating internal conflict that weakens both functions." + less_likely: + - diagnosis: "Individual performance issues" + reason: "What looks like individual underperformance in D2C is often a structural problem: wrong metrics, unclear creative process, or misaligned incentives." + d2c_specific_diagnoses: + - name: "Founder identity fusion with brand" + description: "The founder's personal identity is so deeply fused with the brand that all brand decisions must flow through them, creating a bottleneck. The team cannot make creative decisions, approve content, or evolve the brand voice without founder approval. When the founder is unavailable, the brand stalls." + symptoms: + - "Every piece of content requires founder approval" + - "No brand guidelines document that enables independent creative decisions" + - "Team members describing the brand in inconsistent terms" + - "Content production velocity constrained by founder's bandwidth, not team's capacity" + routes_to_skills: ["delegation-and-empowerment", "organisational-culture", "creative-identity-and-purpose"] + routes_to_templates: ["culture-values-document", "action-plan"] + sector_red_flags: + - "Creative team and performance marketing team using different success metrics with no shared dashboard." + - "Content production velocity declining while team size increases — a process and decision-making bottleneck." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Co-founder conflict in D2C often centers on the brand-commerce tension: one founder is brand-oriented (creative vision, storytelling, community) and the other is commerce-oriented (unit economics, channel optimization, operational efficiency). Both perspectives are essential, and the conflict arises when one dominates." + additional_triage_questions: + - question: "Does the conflict center on brand direction (creative vision, brand investments), commercial strategy (pricing, channels, unit economics), or resource allocation between brand building and revenue generation?" + purpose: "D2C co-founder conflicts cluster around the brand-commerce axis. Each resolution path requires different frameworks." + routing_impact: "Brand direction conflict routes to creative-identity-and-purpose and defining-and-exploring-problems. Commercial conflict routes to balanced-scorecard and evaluating-and-deciding. Resource allocation routes to scenario-planning and cooperative-negotiation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Brand-commerce vision tension" + reason: "D2C brands with a creative co-founder and a commercial co-founder almost always experience tension between brand investment (long-term, hard to measure) and revenue optimization (short-term, highly measurable)." + less_likely: + - diagnosis: "Fundamental vision misalignment" + reason: "Most D2C co-founders agree on what the brand should be — they disagree on how fast to grow, how much to invest in brand versus performance, and when to expand." + d2c_specific_diagnoses: + - name: "Brand vision versus growth pressure" + description: "One co-founder insists on maintaining brand purity (premium positioning, limited discounting, curated assortment) while the other pushes for growth at any cost (broader product line, Amazon expansion, deeper discounts). The board or investors add pressure for growth metrics, tipping the balance toward the commerce-first perspective and alienating the brand-first co-founder." + symptoms: + - "Co-founders publicly disagreeing on discount strategy, channel expansion, or product line breadth" + - "Brand guidelines being overridden by growth experiments" + - "Creative team reporting to the brand co-founder while performance team reports to the growth co-founder" + - "Board presentations alternating between brand-forward and growth-forward narratives" + routes_to_skills: ["cooperative-negotiation", "balanced-scorecard", "evaluating-and-deciding"] + routes_to_templates: ["decision-journal", "quarterly-strategic-review"] + sector_red_flags: + - "Co-founders making contradictory brand decisions — one approving a deep discount campaign while the other invests in premium positioning." + - "Key creative or marketing hires leaving due to inconsistent brand direction." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C market entry is primarily about brand positioning — which emotional territory to claim and which identity group to serve. The product can be manufactured and shipped anywhere; the question is whether the brand can claim a meaningful position in a consumer's identity." + additional_triage_questions: + - question: "What brand position are you claiming — what emotional territory, identity group, or cultural movement does the brand represent?" + purpose: "D2C brands enter markets through positioning, not products. 'We make better razors' is a product claim. 'We make grooming honest, affordable, and fun' is a brand position." + routing_impact: "No clear brand position routes to blue-ocean-strategy and creative-identity-and-purpose before market entry. Clear position routes to channel strategy and launch execution." + - question: "Have you validated demand through pre-launch community building, waitlist, or crowdfunding — or are you launching cold?" + purpose: "D2C brands that build community before launching product have dramatically better first-month economics and higher repeat rates." + routing_impact: "No pre-launch validation routes to community building and waitlist strategy before launch. Validated demand routes to launch execution and channel optimization." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Entering a crowded category without differentiated brand positioning" + reason: "Most consumer categories have hundreds of D2C brands. Entry without a differentiated brand position means competing on price and ads — a losing proposition." + less_likely: + - diagnosis: "Market too small" + reason: "Consumer markets are large. The question is not whether enough people buy skincare but whether your brand can capture a meaningful slice of those buyers' identity." + d2c_specific_diagnoses: + - name: "Commodity entry disguised as brand launch" + description: "The brand is entering a market with a product that is functionally identical to existing alternatives (same formulation, same manufacturer, similar packaging) and differentiated only by a new logo, color scheme, and Instagram aesthetic. There is no genuine brand story, no community, and no experience innovation — just a new label on an existing product." + symptoms: + - "Product sourced from a manufacturer that supplies 10+ other brands" + - "Value proposition centers on product features that competitors match" + - "No founder story or brand narrative beyond 'we make better [product]'" + - "Marketing plan is exclusively paid social with no community or content strategy" + routes_to_skills: ["blue-ocean-strategy", "story-structure-and-arc", "creative-identity-and-purpose"] + routes_to_templates: ["strategic-analysis-one-pager", "market-opportunity-summary"] + sector_red_flags: + - "Launching without a pre-built audience (email list < 1,000) — the brand will be 100% dependent on paid acquisition from day one." + - "Entering a category where Amazon private label already exists at a price point the D2C brand cannot match." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C hiring challenges center on finding talent that bridges creative and commercial skillsets. The most critical and hardest-to-hire roles are: creative director (brand steward), performance marketing lead (channel operator), and supply chain/operations lead (fulfillment optimizer). D2C also demands culture fit with the brand — employees who do not authentically connect with the brand's identity produce inauthentic work." + additional_triage_questions: + - question: "Are you hiring for a creative/brand role or a commercial/operations role? Does the candidate genuinely connect with the brand's mission and identity?" + purpose: "D2C creative hires who do not love the brand will produce generic work. Operations hires who do not understand brand premium will optimize for cost at the expense of experience." + routing_impact: "Creative role routes to brand-aligned hiring criteria and portfolio evaluation. Commercial role routes to D2C-specific metrics literacy and stage-appropriate experience assessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Hiring experience mismatch for company stage" + reason: "D2C brands frequently hire marketing leaders from large CPG companies who are accustomed to $50M budgets and established brands. These leaders struggle with the scrappy, creative, performance-driven reality of a $5M D2C brand." + less_likely: + - diagnosis: "Compensation competitiveness" + reason: "D2C brands attract talent through brand love and creative freedom, not just compensation. Mission-aligned candidates will accept below-market packages." + d2c_specific_diagnoses: + - name: "Influencer dependency on a single team member" + description: "All influencer and creator relationships are managed by one person. The relationships are personal, not institutional. If this person leaves, the brand loses its entire influencer program — relationships, creator contacts, negotiated rates, and institutional knowledge." + symptoms: + - "One team member managing all influencer relationships" + - "No CRM or system tracking influencer contacts, rates, and performance" + - "Influencer content quality and volume highly variable (depends on one person's capacity)" + - "Concern about business continuity if the influencer manager leaves" + routes_to_skills: ["systems-thinking", "delegation-and-empowerment"] + routes_to_templates: ["role-description-template", "action-plan"] + sector_red_flags: + - "VP Marketing hire from a Fortune 500 CPG company failing within 6 months — the most common and most expensive D2C hiring mistake." + - "Creative director hire producing work that looks 'professional' but lacks the brand's authentic voice and personality." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C operational chaos manifests in the physical supply chain: fulfillment delays, inventory mismanagement, return processing backlogs, and shipping cost overruns. Unlike SaaS (where operational chaos is software-related), D2C operational chaos involves physical goods, warehouses, and logistics — problems that cannot be patched with a code deploy." + additional_triage_questions: + - question: "Where is the operational chaos concentrated: inventory management (stockouts/overstock), fulfillment (speed/accuracy), shipping (cost/speed), returns (processing/refunds), or customer service (response time/quality)?" + purpose: "D2C operational chaos usually has a primary bottleneck. Identifying it prevents wasted effort on secondary problems." + routing_impact: "Inventory routes to demand forecasting and supply chain analysis. Fulfillment routes to 3PL evaluation and process optimization. Returns routes to returns workflow redesign. Customer service routes to support tooling and staffing." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Growth outpacing operational infrastructure" + reason: "D2C brands that scale revenue 3-5x in a year frequently outgrow their 3PL capacity, inventory planning processes, and customer service team — all simultaneously." + less_likely: + - diagnosis: "Process deficiency" + reason: "Early-stage D2C brands often have too little process (no demand forecasting, no inventory planning, no returns workflow) rather than wrong process." + d2c_specific_diagnoses: + - name: "3PL failure during peak season" + description: "The brand's third-party logistics provider cannot handle peak season volume. Fulfillment times balloon from 2 days to 7+ days, shipping errors increase, and customer complaints spike. The brand's reputation suffers during the highest-revenue period of the year." + symptoms: + - "Fulfillment SLA breaches increasing 3x during peak periods" + - "Customer service tickets about shipping doubling during Q4" + - "Negative reviews citing slow delivery and incorrect orders" + - "Social media complaints about shipping visible to prospective customers" + routes_to_skills: ["kaizen-bpr", "systems-thinking", "scenario-planning"] + routes_to_templates: ["incident-postmortem", "action-plan"] + sector_red_flags: + - "Average fulfillment time exceeding 3 business days — customers expect 2-day delivery and compare against Amazon Prime." + - "Stockout rate above 5% on hero products — every stockout is a lost sale and potential lost customer." + - "Customer service response time exceeding 24 hours — a signal that operational scaling has not kept pace with growth." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C leadership crises carry unique brand risk because the founder's personal brand is often fused with the company brand. A founder controversy, burnout, or departure can directly damage brand perception — something that does not happen when a SaaS CEO has a bad week." + additional_triage_questions: + - question: "Is the leadership crisis visible to customers, the community, or the public — or is it contained internally?" + purpose: "In D2C, a founder's public misstep, social media controversy, or visible departure can damage the brand because customers feel a personal connection to the founder. Internal crises must be managed with brand protection as a primary concern." + routing_impact: "Publicly visible crisis routes to immediate brand protection and communication strategy. Internal crisis routes to standard leadership intervention." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Founder burnout from identity fusion with brand" + reason: "D2C founders who ARE the brand face unique burnout: they cannot separate personal identity from professional performance. Every negative review feels personal. Every brand criticism is a personal attack." + less_likely: [] + d2c_specific_diagnoses: [] + sector_red_flags: + - "Founder publicly expressing burnout or disillusionment on social media — the brand's most visible ambassador signaling fatigue." + - "Founder controversy trending on social media — the brand and the person are inseparable in the public eye." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C decision paralysis often stems from the tension between brand instinct (creative, emotional, intuitive) and data-driven analysis (ROAS, CAC, contribution margin). Founders delay decisions because the data points in one direction and their brand instinct points in another." + additional_triage_questions: + - question: "Is the decision paralysis about a brand decision (creative direction, positioning, channel choice) or an operational decision (pricing, inventory, staffing)?" + purpose: "Brand decisions benefit from conviction over data. Operational decisions benefit from data over conviction. Applying the wrong decision framework causes paralysis." + routing_impact: "Brand decision paralysis routes to creative-identity-and-purpose and defining-and-exploring-problems. Operational paralysis routes to evaluating-and-deciding with emphasis on reversibility assessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Data-instinct conflict" + reason: "D2C founders frequently face situations where data says 'run more discount ads' (higher ROAS) but instinct says 'this will dilute the brand.' The conflict creates paralysis." + less_likely: + - diagnosis: "Insufficient information" + reason: "D2C brands have abundant data (Shopify, Klaviyo, Meta, Google Analytics). The problem is rarely lack of information but inability to reconcile conflicting signals." + d2c_specific_diagnoses: [] + sector_red_flags: + - "Amazon decision delayed more than 6 months — this is the most consequential and most frequently delayed decision in D2C." + - "Pricing unchanged for 12+ months despite market, cost, and brand evolution." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Innovation drought in D2C manifests as brand staleness — the brand stops creating cultural conversation, content feels repetitive, new products are incremental rather than exciting, and the community loses energy. Unlike SaaS, where innovation drought is about features, D2C innovation drought is about cultural relevance." + additional_triage_questions: + - question: "When was the last time the brand created a genuine cultural moment — a product, campaign, or initiative that generated organic conversation beyond paid media?" + purpose: "D2C brands that stop creating cultural moments become invisible. The ability to generate earned media and organic social conversation is the health indicator for brand innovation." + routing_impact: "No cultural moment in 6+ months routes to creative-identity-and-purpose, tipping-point, and creative-practice-and-habit. Recent cultural moments with declining frequency routes to creative process optimization." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Content-commerce disconnect" + reason: "D2C brands in innovation drought often split into two disconnected modes: brand content that is creative but does not sell, and performance content that sells but does not build the brand. Neither creates cultural conversation." + less_likely: + - diagnosis: "Lack of creative talent" + reason: "Innovation drought in D2C is usually a strategic or process failure (wrong priorities, no creative brief, no testing culture) rather than a talent failure." + d2c_specific_diagnoses: + - name: "Content-commerce disconnect" + description: "The brand produces two types of content that never intersect: beautiful brand content that generates social engagement but zero sales, and performance ad content that drives purchases but builds no brand equity. The creative team and the performance team operate in parallel universes. No content achieves both objectives simultaneously." + symptoms: + - "High social engagement on brand content but no measurable revenue impact" + - "Performance ads generating sales with declining ROAS (creative exhaustion)" + - "Brand team and performance team producing content independently with no shared brief" + - "Brand content not tested as paid ads; performance content not informed by brand strategy" + routes_to_skills: ["creative-collaboration-and-context", "creative-practice-and-habit", "balanced-scorecard"] + routes_to_templates: ["new-initiative-brief", "action-plan"] + sector_red_flags: + - "No viral or high-engagement content in 3+ months — the brand is not contributing to cultural conversation." + - "UGC volume declining — customers are not inspired to create content about the brand." + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C partnerships span influencer partnerships, retail partnerships, brand collaborations, and platform partnerships. Each type has distinct power dynamics, economic structures, and brand implications that the base diagnostic does not address." + additional_triage_questions: + - question: "Is this an influencer/creator partnership, a retail/distribution partnership, a brand collaboration, or a platform partnership (Amazon, TikTok Shop)?" + purpose: "Each partnership type has fundamentally different economics, risks, and brand implications." + routing_impact: "Influencer routes to cialdini-influence and tipping-point. Retail routes to four-ps-marketing and scenario-planning. Brand collaboration routes to blue-ocean-strategy. Platform routes to prisoners-dilemma-and-cooperation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Influencer dependency on a small number of creators" + reason: "D2C brands frequently build their acquisition around 3-5 high-performing influencers. If those creators become unavailable (raise rates, switch to a competitor, retire), the brand's growth engine stalls." + less_likely: + - diagnosis: "Cultural misalignment" + reason: "D2C partnerships are primarily economic and creative. Brand-value alignment matters more than organizational cultural fit." + d2c_specific_diagnoses: + - name: "Influencer dependency creating single-point-of-failure" + description: "The brand's acquisition depends on a small number of influencers who drive a disproportionate share of revenue. The brand has not diversified its creator portfolio, creating vulnerability to rate increases, competitive poaching, and creator fatigue." + symptoms: + - "Top 3 influencers driving 40%+ of attributed influencer revenue" + - "No structured influencer recruitment pipeline to replace underperforming or departing creators" + - "Influencer rates increasing faster than influencer-driven revenue" + - "Brand unable to walk away from unfavorable creator terms because of dependency" + routes_to_skills: ["tipping-point", "systems-thinking", "prisoners-dilemma-and-cooperation"] + routes_to_templates: ["partnership-memo", "risk-assessment-brief"] + sector_red_flags: + - "A single influencer driving more than 15% of total revenue — catastrophic if that relationship ends." + - "Retail partner discounting below DTC price, undermining the brand's direct channel." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C communication breakdowns extend beyond internal team communication to include brand-customer communication. The brand speaks through every touchpoint — ads, product pages, emails, packaging, social media, customer service — and inconsistency across touchpoints confuses customers and dilutes the brand." + additional_triage_questions: + - question: "Is the communication breakdown internal (between teams) or external (between brand and customer)? Does the brand speak with one voice across all touchpoints?" + purpose: "Internal breakdowns (creative and performance teams not aligned) manifest as external inconsistency (different brand voice in ads vs. emails vs. packaging). Diagnosing the root level matters." + routing_impact: "Internal breakdown routes to team-culture-and-dynamics and strategic-thinking-and-alignment. External inconsistency routes to creative-identity-and-purpose and brand guidelines development." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Brand voice inconsistency across channels" + reason: "D2C brands communicating through 5+ channels (website, email, SMS, social, packaging, ads) with different team members managing each channel frequently develop inconsistent brand voices." + less_likely: [] + d2c_specific_diagnoses: [] + sector_red_flags: + - "Customers describing the brand differently depending on where they encountered it — a sign that the brand voice is fragmented." + - "Social media tone dramatically different from email tone — the brand feels like two different companies." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C negotiations get stuck in characteristic ways: influencer rate negotiations where the brand lacks leverage, retail buyer negotiations where the power asymmetry is extreme, manufacturer negotiations over MOQs and payment terms, and investor negotiations where D2C-specific valuation multiples are poorly understood." + additional_triage_questions: + - question: "Is the negotiation stuck with an influencer/creator, a retail buyer, a manufacturer/supplier, or an investor?" + purpose: "Each negotiation type in D2C has distinct power dynamics and typical sticking points." + routing_impact: "Influencer routes to information-asymmetry and competitive-negotiation. Retail routes to cooperative-negotiation and business-model-canvas. Manufacturer routes to porters-five-forces. Investor routes to fundraising-diagnosis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Power asymmetry" + reason: "D2C brands are frequently the smaller party: negotiating with retail buyers who control shelf space, manufacturers who hold production capacity, and influencers who have more options than the brand does." + less_likely: + - diagnosis: "Fundamental value disagreement" + reason: "D2C negotiations rarely stall on fundamental value. They stall on terms: minimum order quantities, payment terms, exclusivity, and rate structures." + d2c_specific_diagnoses: [] + sector_red_flags: + - "Retail negotiations demanding exclusivity that would prevent DTC sales of key products." + - "Manufacturer demanding 12-month exclusivity on a product formulation that the brand does not own." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "D2C culture erosion is uniquely dangerous because internal culture directly manifests in external brand expression. A demoralized creative team produces lifeless content. A customer service team that does not believe in the brand provides transactional support. In D2C, culture IS the brand — internal erosion becomes external erosion." + additional_triage_questions: + - question: "Does the team still authentically believe in and use the product? Do employees feel proud to tell people where they work?" + purpose: "D2C team members who do not use or love the product will produce inauthentic brand experiences. Employee pride is a leading indicator of brand health." + routing_impact: "Low product belief routes to product quality and brand purpose assessment. Low pride routes to organisational-culture and purpose-driven-leadership." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Growth-driven culture shift from mission to metrics" + reason: "D2C brands often start with mission-driven culture (sustainability, community, identity) and gradually shift to metrics-driven culture (ROAS, CAC, revenue targets) as investors and growth demands take over. The mission that attracted early employees and customers gets diluted." + less_likely: + - diagnosis: "Toxic leadership" + reason: "Culture erosion in D2C is more commonly caused by mission drift and growth pressure than by toxic behavior." + d2c_specific_diagnoses: + - name: "Community fatigue from over-monetization" + description: "The brand's community — social media followers, email subscribers, loyalty program members — has been over-monetized through constant promotional messaging. Engagement is declining, unsubscribe rates are rising, and the community that once amplified the brand is going silent. The community was treated as an audience to sell to rather than a group to serve." + symptoms: + - "Email open rates declining for 3+ months" + - "Social media engagement rate declining while follower count grows" + - "Unsubscribe rate increasing on email and SMS" + - "Community members expressing fatigue ('all you do is sell to me')" + - "UGC volume declining — customers no longer want to create content for the brand" + routes_to_skills: ["tipping-point", "cialdini-influence", "organisational-culture"] + routes_to_templates: ["action-plan", "culture-values-document"] + sector_red_flags: + - "Employees reluctant to share brand content on personal social media — they do not want to be associated with the brand." + - "Regrettable attrition on the creative team — the people who build the brand are leaving." + - "Community engagement declining despite growing community size — the audience is becoming passive." diff --git a/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-skill-overlays.yaml b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-skill-overlays.yaml new file mode 100644 index 0000000..c26abfb --- /dev/null +++ b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-skill-overlays.yaml @@ -0,0 +1,447 @@ +# D2C Consumer Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides D2C-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add a brand-first, direct-to- +# consumer lens. +# +# BRAND AS MOAT is the organizing principle. D2C is not a technology business +# disguised as a commerce business — it is a BRAND business disguised as a +# commerce business. Every overlay must surface how the framework applies +# through the lens of brand affinity, community, storytelling, and identity +# signaling. A D2C brand's competitive advantage is not its product features +# (easily copied), its supply chain (commoditized), or its technology (Shopify +# levels the field). The moat is the emotional connection between the brand +# and the customer — the reason someone pays more to buy from you when an +# identical product exists on Amazon for less. +# +# Key D2C dynamics reflected in every overlay: +# - Buyer power is extreme: infinite alternatives one click away +# - Barriers to entry are near zero: Shopify + Meta ads = instant competitor +# - The product IS the experience: packaging, unboxing, storytelling, identity +# - Promotion = content + community + influencer (not traditional advertising) +# - Price = perceived value and identity signal, not cost-plus margin +# - Place = own site vs Amazon vs retail, each with different brand implications +# - iOS privacy changes have fundamentally altered attribution and targeting +# - Community is the most durable competitive advantage in D2C +# +# Selection criteria for the 35 skills: +# - Frameworks with direct D2C application (brand strategy, marketing, pricing) +# - Storytelling and creative skills (CRITICAL — D2C brands live or die by narrative) +# - People and influence skills (community building, customer connection) +# - Decision and thinking skills (applied to channel, pricing, and brand decisions) +# - Game theory skills applicable to competitive and channel dynamics +# +# Relevance tiers: +# critical — The D2C overlay materially changes how the skill is applied. +# The skill executor should always surface D2C context. +# high — D2C context adds significant value. Surface when relevant. +# moderate — Useful D2C framing but the base skill works well as-is. + +pack_metadata: + sector: "d2c-consumer" + display_name: "D2C Consumer" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (18 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "Porter's Five Forces in D2C reveals a structurally hostile competitive environment. Buyer power is extreme — customers face zero switching costs, infinite alternatives, and price transparency through Amazon, Google Shopping, and social commerce. Barriers to entry are near zero: Shopify, Alibaba-sourced products, and Meta ads enable anyone to launch a competing brand in weeks. Supplier power is concentrated in contract manufacturers who serve dozens of brands with identical formulations or materials. Substitutes include not just direct competitors but Amazon private label, retailer private label, and the option of simply not buying. The only force a D2C brand can structurally control is rivalry intensity — through brand differentiation so powerful that customers perceive no substitute." + d2c_anti_patterns: + - "Analyzing Five Forces as though the product is the competitive unit. In D2C, the brand is the competitive unit. Two identical moisturizers from two brands are not substitutes if one brand has built identity-level loyalty." + - "Ignoring Amazon as a force in every analysis. Amazon sets price expectations, delivery speed standards, and return policy norms for every consumer category — even for brands that refuse to sell on Amazon." + - "Underestimating the threat of new entrants because 'our product is better.' Product quality is necessary but insufficient. A well-funded competitor with strong brand storytelling and a $5M Meta ad budget can match your product and surpass your brand in 12 months." + d2c_example: "A DTC supplement brand uses Five Forces to discover that its true competitive threat is not other supplement startups but Amazon's private label (Solimo) entering the category at 40% lower price points. The analysis reveals that the brand's only defensible position is the emotional trust and community it has built with health-conscious consumers — a moat that Amazon cannot replicate. This reframes strategy from product differentiation (more ingredients, better sourcing) to community deepening (expert-led content, member-only events, personalized wellness plans)." + benchmark_references: ["cac-blended", "gross-margin", "organic-traffic-pct"] + + - skill: "blue-ocean-strategy" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "Blue ocean strategy is existential for D2C because every consumer category is a red ocean of price competition, feature creep, and paid acquisition wars. The strategy canvas in D2C maps factors that traditional product companies ignore: brand narrative, community belonging, unboxing experience, identity signaling, sustainability story, and founder authenticity. Blue oceans in D2C emerge when brands eliminate traditional retail factors (broadest selection, lowest price, fastest delivery) and create entirely new value dimensions that Amazon and mass retailers cannot replicate. Glossier found blue ocean by making beauty about skin-first minimalism and community. Patagonia created blue ocean by making environmentalism the product. Liquid Death made water into an identity statement. None of these brands won on product superiority — they won by redefining the value curve." + d2c_anti_patterns: + - "Pursuing blue ocean through product innovation alone. A better formulation, a cleaner ingredient list, or a novel material is red ocean innovation disguised as differentiation. The blue ocean is in the brand experience, not the product spec sheet." + - "Assuming premium pricing creates blue ocean automatically. Price is a signal, not a strategy. Premium price without a differentiated brand story positions the brand in the crowded 'premium commodity' segment." + - "Defining the blue ocean without testing whether real customers will swim in it. Validate that the underserved dimension you have identified (community, sustainability, identity) actually drives purchasing behavior, not just survey approval." + d2c_example: "Liquid Death launched into the most commoditized consumer category — water — and created blue ocean not through product innovation (it is canned water) but through radical brand identity. The strategy canvas eliminated everything traditional water brands compete on (purity claims, mountain imagery, health messaging) and created new dimensions: punk rock aesthetic, entertainment-first content, environmental activism through aluminum cans, and a brand personality that consumers tattoo on their bodies. The blue ocean was not a better water; it was an identity you could wear." + benchmark_references: ["organic-traffic-pct", "nps", "community-growth-rate"] + + - skill: "business-model-canvas" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "The Business Model Canvas for D2C requires brand-first interpretation of every block. Value Proposition is not the product — it is the identity, community, and emotional experience the brand delivers. Customer Segments must distinguish between identity-driven buyers (loyal, high-LTV, organic) and deal-driven buyers (one-time, low-LTV, paid acquisition). Revenue Streams must decompose into DTC site, subscription, Amazon, wholesale, and retail — each with fundamentally different margins, customer ownership, and brand implications. Key Resources include the brand itself, the community, the content library, and the email/SMS list — not just inventory and supply chain. Cost Structure must confront the D2C tax: CAC (the largest variable cost), fulfillment, shipping, returns, and payment processing consume 40-60% of revenue before fixed costs." + d2c_anti_patterns: + - "Listing the product in Value Proposition without articulating the brand's emotional promise. Hundreds of brands sell organic cotton t-shirts. The value proposition is what the brand means — sustainability, community, identity — not the material specification." + - "Ignoring the channel cannibalization between DTC and Amazon. Adding Amazon as a revenue stream changes every other canvas block: margins decrease, customer relationship shifts from owned to rented, and brand positioning faces downward price pressure." + - "Treating Customer Relationships as a single mode. D2C has distinct relationship tiers: transactional buyers (discount-driven, one-time), community members (engaged, repeat), brand advocates (ambassadors, UGC creators), and subscribers (committed, recurring). Each requires different investment and delivers different economics." + d2c_example: "A DTC skincare founder uses the canvas to evaluate her current model and discovers a fundamental misalignment: the Value Proposition emphasizes 'clean ingredients' (a commodity claim shared by 500+ brands), the primary Revenue Stream is one-time purchases with only 8% subscription conversion, and Customer Relationships are transactional (no community, no loyalty program, no post-purchase engagement beyond email promotions). The canvas redesign reframes the Value Proposition around 'personalized skin wellness' (identity-level promise), adds a membership model (committed relationship), and builds community as a Key Activity (brand moat)." + benchmark_references: ["contribution-margin", "ltv", "cac-blended", "subscription-conversion-rate"] + + - skill: "four-ps-marketing" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "The Four Ps in D2C must be reinterpreted through the brand lens. Product is not a SKU — it is the complete experience from first ad impression through unboxing, use, and re-ordering. Product includes packaging design, insert cards, scent, texture, the ritual of use, and how the product looks on a bathroom shelf for Instagram. Price in D2C is a brand signal: charging more than Amazon signals premium positioning and enables brand-building investment; charging less signals commodity positioning and traps the brand in an acquisition cost spiral. Perceived value, not cost-plus, determines price. Place means channel strategy with profound brand implications: DTC (100% brand control, highest margin), Amazon (discovery but surrendered customer relationship), retail (credibility and reach but slim margins and loss of data). Promotion in D2C is content, community, and creator culture — not traditional advertising. The most effective D2C promotion does not look like promotion: organic TikTok, founder stories on Instagram, UGC reviews, and influencer partnerships that feel like genuine recommendations." + d2c_anti_patterns: + - "Setting Price based on competitor benchmarking or cost-plus margins. In D2C, price signals identity. Customers buy Aesop hand soap at $40 and Method hand soap at $4 — the price is the brand statement, not a rational economic calculation." + - "Treating Amazon as 'just a Place.' Amazon changes the other three Ps: Product perception shifts to commodity, Price faces constant downward pressure, and Promotion becomes Amazon's ad platform instead of your brand story." + - "Running Promotion through paid ads without investing in organic content. A D2C brand spending 80%+ of marketing budget on Meta and Google ads with no content strategy is renting attention, not building a brand." + d2c_example: "Aesop applies the Four Ps with brand-first discipline. Product: minimalist packaging that signals sophistication — the product is designed to be displayed, not hidden. Price: unapologetically premium, reinforcing the brand as an identity marker. Place: own retail stores designed as gallery experiences, DTC site with editorial content, selective wholesale (no Amazon, no mass retail). Promotion: zero paid social advertising — instead, architectural store design generates organic media coverage and customer photography. Every P reinforces the brand rather than commoditizing it." + benchmark_references: ["aov", "cac-blended", "contribution-margin", "organic-traffic-pct"] + + - skill: "net-promoter-score" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "NPS in D2C measures brand love, not product satisfaction. The total experience shapes the score: Was the unboxing special? Did the product match the brand's visual identity? Did the shipping feel premium or was it a brown box? Did post-purchase emails feel personal or automated? NPS should be triggered 7-14 days post-delivery (after the customer has used the product and experienced the full brand arc). The qualitative follow-up question is gold in D2C — it reveals whether customers love the brand (promoters who cite community, values, identity) or merely like the product (passives who cite quality and price). D2C brands should segment NPS by acquisition channel: customers acquired through community/organic channels consistently score 15-25 points higher than those acquired through paid ads or discount promotions." + d2c_anti_patterns: + - "Surveying at checkout instead of post-delivery. The customer has not experienced the brand yet — they have experienced a website." + - "Treating NPS as a product metric. In D2C, NPS reflects the entire brand relationship. A product with a 70 NPS sold through a terrible experience (slow shipping, ugly packaging, spammy follow-up) will register as a 35." + - "Ignoring the correlation between acquisition channel and NPS. Customers acquired through deep discounts and aggressive retargeting consistently show lower NPS and lower LTV than those acquired through organic or community channels." + d2c_example: "A DTC candle brand segments NPS by acquisition channel and discovers a 30-point gap: customers who discovered the brand through Instagram content and community give NPS of 72; customers acquired through Facebook discount ads give NPS of 42. The root cause is not product quality (identical candles) but expectation alignment. Community-acquired customers understand and value the brand's story, ritual, and aesthetic. Ad-acquired customers were drawn by a 25%-off offer and judge the product purely on scent and burn time — dimensions where competition is fierce. This insight triggers a strategic shift: reduce discount acquisition, increase community and content investment." + benchmark_references: ["nps", "repeat-purchase-rate", "organic-traffic-pct"] + + - skill: "product-life-cycle" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "Product lifecycle in D2C applies at three levels simultaneously: the individual SKU, the product line, and the brand itself. SKU lifecycle follows seasonal trends, social virality, and trend cycles — a TikTok-viral product can compress the entire introduction-growth-maturity-decline cycle into 6 months. Product line lifecycle involves assortment management: introducing new SKUs while harvesting mature ones and discontinuing declining ones, all while maintaining brand coherence. Brand lifecycle is the existential concern: D2C brands follow a predictable arc from insurgent challenger (introduction) to cultural darling (growth) to mainstream saturation (maturity) to nostalgia play (decline). The brands that escape this cycle do so by continuously reinventing their cultural relevance — refreshing storytelling, entering new categories, and deepening community — while the product portfolio evolves underneath." + d2c_anti_patterns: + - "Launching new products faster than the brand can storytell them into existence. Every new SKU needs a narrative, photography, content, and community context. Launching 20 SKUs without marketing investment for each dilutes the brand." + - "Mistaking product maturity for brand maturity. A specific product may mature (sales plateau, competitors copy it) while the brand itself remains in growth if it continues to evolve culturally." + - "Ignoring trend cycle compression. A product driven by a TikTok trend has a 3-6 month lifecycle peak, not a 2-3 year traditional lifecycle. Inventory planning must account for this acceleration." + d2c_example: "Glossier's brand lifecycle illustrates the full arc. Introduction (2014-2016): insurgent beauty brand challenging the industry with 'skin first, makeup second' and community-driven development. Growth (2016-2019): cultural darling, organic-first growth, cult products like Boy Brow. Maturity (2019-2022): growth slowed, launched Glossier Play (failed line extension), retail expansion struggled. Renewal (2022-present): new leadership, refocused brand narrative, selective retail partnerships. The lifecycle framework reveals that Glossier's challenges were not product failures but brand lifecycle management failures — they stopped evolving the story." + benchmark_references: ["repeat-purchase-rate", "organic-traffic-pct", "nps"] + + - skill: "growth-share-matrix" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "The BCG Growth-Share Matrix maps directly to D2C product portfolio and channel management. Stars are hero products or product lines with strong growth and market position — they drive brand awareness and acquisition. Cash Cows are mature, everyday products with stable demand and strong margins — they fund brand building and new product development. Question Marks are new launches, trend-driven experiments, or emerging channels. Dogs are underperforming SKUs consuming inventory capital, warehouse space, and marketing attention. In D2C, the matrix also applies to channels: the DTC site might be a Star (growing, high margin), Amazon a Cash Cow (stable revenue, known economics), and TikTok Shop a Question Mark (potential but unproven)." + d2c_anti_patterns: + - "Spreading marketing budget equally across all SKUs regardless of their matrix position. Hero products (Stars) should receive disproportionate creative and media investment because they are the brand's front door." + - "Killing Dogs without considering their role in the assortment story. A low-selling SKU that completes a 'bundle' or represents the brand's origin story may earn its shelf space through narrative value, not revenue." + - "Treating Amazon as a Star when it is structurally a Cash Cow (or Dog). Amazon's economics rarely improve — if the channel is not profitable today, investing more will not change the structural margin pressure." + d2c_example: "A DTC beauty brand maps its portfolio: a viral serum (Star — 40% YoY growth, highest-margin product), everyday moisturizer (Cash Cow — stable sales, core replenishment), new body care line (Question Mark — growing category but unproven brand position), and a legacy lip product (Dog — declining sales, crowded category). The matrix clarifies investment: double creative spend on the serum, use moisturizer margins to fund body care testing, and discontinue the lip product to free inventory capital and creative resources." + benchmark_references: ["gross-margin", "contribution-margin", "repeat-purchase-rate"] + + - skill: "disruptive-innovation" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "D2C brands are the textbook vehicle for disruption of incumbent consumer brands and traditional retail distribution. The pattern repeats: an incumbent serves the market through retail distribution with high markups and broad but generic product lines. A D2C startup enters with a simpler proposition — fewer SKUs, direct distribution, a compelling brand story, and a price point that eliminates the retail margin. The incumbent ignores the DTC entrant because the initial market (young, online-native consumers) looks small and unprofitable. Over time, the D2C brand builds community, expands the product line, and eventually enters retail from a position of brand strength. This is exactly how Warby Parker disrupted Luxottica, how Dollar Shave Club disrupted Gillette, and how Harry's disrupted Schick. Understanding position in the disruption cycle determines whether to double down on DTC purity or expand into retail." + d2c_anti_patterns: + - "Assuming DTC channel innovation constitutes disruption. Selling the same product through a different channel at a similar price is arbitrage, not disruption. True D2C disruption combines brand innovation (story, community, identity) with distribution innovation (direct relationship)." + - "Moving into retail prematurely before establishing brand demand. Retail partnerships should be pull-based (retailers wanting you because customers ask for it) not push-based (you seeking retail because DTC growth is slowing)." + - "Ignoring the incumbent response. When DTC brands prove a category, incumbents respond with their own DTC offerings, acquisitions, or retail exclusives. Gillette launched its own subscription after Dollar Shave Club proved the model." + d2c_example: "Warby Parker disrupted the eyewear industry not with better lenses or frames but with a radical rebundling: direct-to-consumer distribution eliminated the Luxottica-owned retail markup, home try-on eliminated the purchase risk, and a brand story built on accessible design and social impact (buy a pair, give a pair) created identity-level loyalty. Luxottica initially ignored Warby Parker because the online-only glasses market looked small. By the time Luxottica responded, Warby Parker had built sufficient brand loyalty to open its own retail stores — completing the disruption by entering the incumbent's channel from a position of brand strength." + benchmark_references: ["cac-blended", "organic-traffic-pct", "repeat-purchase-rate"] + + - skill: "balanced-scorecard" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "The Balanced Scorecard for D2C must include brand health metrics alongside financial, customer, and operational ones. Financial: Revenue, Contribution Margin, LTV:CAC, Blended CAC, Payback Period. Customer: NPS, Repeat Purchase Rate, Return Rate, CSAT, Community Growth Rate. Internal Process: Fulfillment Cost per Order, Shipping Time, Return Processing Cost, Content Production Velocity, Creative Refresh Rate. Learning & Growth: Brand Awareness, UGC Volume, Influencer Program Scale, New Product Development Cycle, Team Cross-Training. The scorecard is powerful in D2C because most brands over-index on financial and acquisition metrics while neglecting brand health and community metrics — the leading indicators that predict future financial performance." + d2c_anti_patterns: + - "Tracking only financial and acquisition metrics (ROAS, CAC, revenue) without brand health indicators (NPS, organic traffic %, community engagement). Financial metrics are lagging indicators in D2C. By the time ROAS declines, the brand problem is already 6-12 months old." + - "Treating the scorecard as a reporting dashboard rather than a decision tool. Each metric should trigger a specific action when it crosses a threshold." + - "Excluding creative and content metrics from the scorecard. In D2C, creative is the primary driver of paid media performance. Creative fatigue is a leading indicator of rising CAC." + d2c_example: "A DTC supplement brand implements a balanced scorecard and discovers a dangerous pattern: Financial metrics are strong (30% contribution margin, 3.5x LTV:CAC), but Customer metrics are deteriorating (NPS declining from 62 to 48 over two quarters, repeat purchase rate dropping from 38% to 31%), while Learning & Growth is stalled (no new products in 9 months, UGC volume flat). The scorecard reveals that the brand is extracting value from existing customer relationships without reinvesting in the brand, product innovation, and community that created those relationships. The financial metrics are lagging — they will decline in 2-3 quarters if brand investment does not increase now." + benchmark_references: ["contribution-margin", "ltv-cac-ratio", "nps", "repeat-purchase-rate", "organic-traffic-pct", "community-growth-rate"] + + - skill: "swot-pest-analysis" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "SWOT and PEST in D2C must address the unique environmental forces shaping direct-to-consumer brands. Political: tariffs on imported goods (most D2C products are manufactured overseas), product safety regulations (FDA for supplements/beauty, CPSC for consumer goods), and emerging data privacy regulation affecting ad targeting. Economic: consumer discretionary spending sensitivity, shipping cost inflation, iOS privacy changes destroying ad targeting economics. Social: identity-driven purchasing (consumers buy what they stand for), sustainability expectations, influencer culture, subscription fatigue, and generational shifts in brand loyalty. Technological: AI-driven personalization, social commerce evolution (TikTok Shop, Instagram Checkout), attribution platform obsolescence, and 3PL technology." + d2c_anti_patterns: + - "Listing 'strong brand' as a SWOT strength without evidence. Brand strength in D2C is quantified by organic traffic percentage, NPS, repeat purchase rate, and UGC volume — not by the founder's Instagram following." + - "Ignoring iOS privacy changes in the PEST analysis. Apple's ATT framework fundamentally altered D2C acquisition economics. Any PEST analysis that does not address attribution and targeting degradation is incomplete." + - "Treating 'sustainability' as a strength when it is table stakes. Consumers expect sustainability from D2C brands. It is a weakness to lack it, not a strength to have it — unless the sustainability story is genuinely differentiated." + d2c_example: "A DTC activewear brand sources 90% of materials from China. PEST analysis identifies tariff escalation (25%+ Section 301 tariffs) as a political risk and social media platform dependency (80% of acquisition from Meta) as a technological risk. SWOT reveals a critical strength: a 50,000-member community with 42% engagement rate and NPS of 68 — but a weakness in channel concentration and a threat from Amazon private label entering activewear with an identical fabric blend. The analysis triggers a dual strategy: diversify manufacturing to Vietnam (mitigate PEST risk) while deepening the community moat through exclusive member events and co-designed collections (convert SWOT strength into defensibility)." + benchmark_references: ["gross-margin", "cac-by-channel", "organic-traffic-pct"] + + - skill: "scenario-planning" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "Scenario planning in D2C must account for the extreme volatility of consumer brands: social media virality (a single TikTok can generate 10x normal demand overnight), seasonal demand concentration (Q4 can represent 30-50% of annual revenue), supply chain lead times (12-16 week production cycles for most physical products), and advertising platform instability (Meta CPM can spike 50-100% during Q4 or after algorithm changes). D2C scenarios must model three intersecting dimensions: demand volatility (viral upside, base case, demand collapse), channel economics (stable ad costs, rising CPMs, platform disruption), and supply chain reliability (on-time delivery, delayed, severely disrupted). The planning horizon must align with manufacturing lead times — brands with 16-week production must plan scenarios 5-6 months ahead." + d2c_anti_patterns: + - "Planning for a single demand forecast. D2C demand is inherently volatile. Scenario planning must model demand upside (stockout risk if a product goes viral) alongside demand downside (excess inventory if a trend fades)." + - "Assuming stable advertising costs across scenarios. Meta and Google CPMs increase 30-100% during Q4 and spike unpredictably after algorithm changes. Channel cost must be a scenario variable." + - "Ignoring the scenario where your primary ad platform changes policy. Meta has changed targeting, attribution, and ad format rules multiple times. 'What if Meta becomes 50% less efficient overnight?' is a legitimate scenario." + d2c_example: "A DTC food brand planning for Q4 builds three scenarios: (1) Base case: demand inline with last year +25%, Meta CPMs up 40% for Q4, supply chain on schedule. (2) Upside: a creator partnership drives a viral TikTok moment — demand spikes 3x in November. Can inventory support it? Can fulfillment ship within 3 days at triple volume? (3) Downside: Meta CPMs spike 80% (they did in Q4 2023), making paid acquisition unprofitable during peak season. The brand must survive on email, SMS, and organic revenue for 6 weeks. The scenario analysis triggers pre-Q4 actions: increase safety stock on hero products, negotiate surge capacity with 3PL, and build an email/SMS campaign calendar that can carry revenue independent of paid ads." + benchmark_references: ["cac-by-channel", "contribution-margin", "shipping-cost-pct"] + + - skill: "cialdini-influence" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "Cialdini's six principles of influence are the operating system of D2C conversion and brand building. Social Proof is the most powerful: customer reviews, UGC photos, 'X people bought this today' counters, influencer endorsements, and press logos reduce buying anxiety. In D2C, social proof must feel authentic — fabricated reviews destroy trust instantly. Scarcity drives urgency through limited drops, seasonal collections, and genuine low-stock alerts (not fake countdown timers). Authority comes from expert endorsements (dermatologists for skincare, nutritionists for supplements), media features, and certifications. Reciprocity operates through generous return policies, surprise gifts in orders, and free samples that create goodwill and repeat purchasing. Liking is the brand personality itself: the founder's story, the brand's values, the aesthetic identity that customers want to be associated with. Commitment & Consistency operates through quizzes, loyalty programs, and subscriptions that create behavioral momentum." + d2c_anti_patterns: + - "Over-using scarcity with fake urgency. Customers quickly learn that 'only 5 left' is permanent and 'sale ends tonight' resets at midnight. Fake scarcity destroys the trust that D2C brands depend on. Reserve scarcity for genuinely limited items." + - "Relying on paid reviews instead of organic social proof. Incentivized reviews with disclaimers, fake UGC, and purchased testimonials are identifiable by sophisticated consumers and corrosive to brand trust." + - "Applying influence principles only at the point of purchase. In D2C, the most powerful influence moments are post-purchase: the unboxing experience (reciprocity), the follow-up email from the founder (liking), the community invitation (commitment). These moments create the repeat buyer." + d2c_example: "Drunk Elephant applies all six principles systematically. Social Proof: extensive UGC on product pages, 'Drunk Break' stories from real users. Scarcity: limited-edition kits and holiday sets with genuine quantity limits. Authority: dermatologist endorsement, 'clean-compatible' ingredient philosophy. Reciprocity: generous sample program with purchase, free skincare consultations. Liking: founder Tiffany Masterson's personal story woven into every touchpoint. Commitment: 'The Drunk Elephant Smoothie' — a multi-step routine that commits customers to the ecosystem rather than individual products." + benchmark_references: ["conversion-rate", "repeat-purchase-rate", "aov", "ugc-volume"] + + - skill: "systems-thinking" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "D2C businesses are complex systems with feedback loops that produce counterintuitive outcomes. The core system dynamics include: the discount-addiction loop (discounting trains customers to wait for sales, reducing full-price demand, creating pressure for more discounting); the CAC-brand spiral (rising paid CAC pressures margins, reducing brand investment budget, further increasing CAC as organic declines); the quality-growth tension (scaling production to meet demand degrades quality, increasing returns and reducing NPS, which kills repeat purchases and increases acquisition dependency); and the community-monetization tension (aggressive monetization of community through constant promotion degrades engagement, weakening the brand's most valuable asset). Systems thinking reveals that every D2C decision — pricing, channel mix, product launch, discount strategy — cascades through the system with delayed, nonlinear effects." + d2c_anti_patterns: + - "Treating marketing and operations as independent systems. A marketing campaign that drives a 3x order spike will fail if fulfillment cannot scale, creating delivery delays that generate negative reviews and social media complaints that persist long after the campaign ends." + - "Optimizing individual metrics without modeling system effects. Reducing CAC through aggressive discounting improves the acquisition metric while degrading LTV, training discount-seeking behavior, and inflating return rates." + - "Ignoring time delays. Brand investment today produces organic traffic and community growth 6-12 months later. Cutting brand spend to hit this quarter's ROAS target creates a revenue decline two quarters out." + d2c_example: "A DTC apparel brand runs a 40%-off Black Friday sale. Systems thinking maps the cascading effects: the discount attracts deal-seeking buyers (high return rate, 35% vs. normal 18%), the volume spike overwhelms fulfillment (3-day shipping becomes 10-day), the fulfillment failure generates negative reviews ('slow shipping, poor packaging'), the reviews suppress conversion rate for weeks after the sale, and the 40% discount becomes the mental reference price for customers who now wait for the next sale. Net effect: GMV increased 180% during the sale period but contribution margin decreased 60%, return rate doubled, NPS dropped 15 points, and full-price conversion rate declined for two months afterward." + benchmark_references: ["contribution-margin", "return-rate", "repeat-purchase-rate", "cac-blended"] + + - skill: "tipping-point" + category: "frameworks" + d2c_relevance: "critical" + d2c_context: "The Tipping Point framework is structurally essential for D2C because consumer brands grow through social contagion, not just paid acquisition. The three agents of change map directly to D2C growth mechanics. Connectors are influencers and community members who bridge different social groups — the micro-influencer who introduces your skincare brand to her running community. Mavens are product experts and review creators whose detailed analysis drives purchase confidence — the YouTube reviewer who does a 20-minute ingredient deep-dive. Salesmen are charismatic advocates who generate emotional resonance — the founder whose authentic storytelling on social media makes customers feel part of a movement. The Stickiness Factor in D2C is the brand experience: memorable packaging, a product ritual, a brand aesthetic that customers want to display. Context is the cultural moment the brand rides: sustainability, wellness, identity politics, nostalgia." + d2c_anti_patterns: + - "Treating influencer seeding as a one-time campaign instead of a systematic strategy. Reaching the tipping point requires sustained, strategically targeted seeding across Connectors, Mavens, and Salesmen — not a single blast of gifted products." + - "Investing in reach (macro-influencers, celebrity endorsements) without stickiness. A million impressions from a celebrity post that does not stick (no memorable hook, no trial mechanism, no community invitation) wastes budget without moving toward the tipping point." + - "Ignoring the Context dimension. Brands tip when the cultural moment aligns. A sustainability-focused brand launching during a cultural sustainability backlash, or a luxury brand launching during a recession, faces contextual headwinds that no amount of influencer seeding can overcome." + d2c_example: "Glossier reached its tipping point through systematic deployment of all three agents. Connectors: Emily Weiss built relationships with beauty editors and influencers through her blog Into The Gloss before launching the brand. Mavens: beauty enthusiasts created detailed review content because the products were genuinely different (minimal ingredients, dewy aesthetic). Salesmen: Glossier turned customers into evangelists through a rep program where anyone could share their personal Glossier page. Stickiness: the pink bubble-wrap pouch and the Glossier aesthetic became instantly recognizable and Instagram-worthy. Context: the 'no-makeup makeup' cultural moment. Each element reinforced the others until Glossier became the defining beauty brand of its generation." + benchmark_references: ["organic-traffic-pct", "community-growth-rate", "ugc-volume", "influencer-roi"] + + - skill: "kaizen-bpr" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "Kaizen (continuous improvement) and BPR (business process reengineering) apply to the physical operations that determine D2C contribution margin: fulfillment workflows, returns processing, packaging efficiency, customer service processes, and the product page-to-checkout conversion funnel. In D2C, small operational improvements compound dramatically: reducing packaging cost by $0.50 per order saves $50,000 at 100,000 annual orders — enough to fund a content production team. Kaizen is particularly relevant to the customer experience chain: every touchpoint from ad impression through post-delivery follow-up is a process that can be measured, benchmarked, and incrementally improved." + d2c_anti_patterns: + - "Applying Kaizen only to warehouse operations while ignoring the creative production pipeline. In D2C, the rate-limiting process is often creative: how fast the team can produce ads, content, and product photography determines how fast the brand can grow." + - "Pursuing BPR (radical redesign) when Kaizen (incremental improvement) suffices. Replacing your 3PL during peak season is BPR risk; optimizing pick-pack processes at the current 3PL is Kaizen common sense." + - "Measuring process improvement without linking to contribution margin per order. Every operational improvement should be expressed in its impact on the unit economics stack." + d2c_example: "A DTC beauty brand applies Kaizen to its returns process. Current state: returns take 10 days to process, refunds are manual, 30% of returned products are discarded as unsellable. Kaizen improvements: standardized return inspection criteria, automated refund triggers upon carrier scan, and a 'like-new' recapture program that repackages gently used products for resale at 20% discount. Results: return processing time drops to 3 days, customer satisfaction with returns increases 25 points, and 40% of previously discarded inventory is recovered as sellable — adding $120,000 annually to revenue." + benchmark_references: ["contribution-margin", "return-rate", "shipping-cost-pct"] + + - skill: "doblin-ten-types" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "Doblin's Ten Types of Innovation reveals that successful D2C brands innovate far beyond the product itself. Product Performance innovation is the least defensible dimension in D2C — competitors can replicate formulations, materials, and designs. The most powerful D2C innovations occur in: Brand (identity innovation — Liquid Death reframed water as punk culture), Customer Engagement (community innovation — Glossier turned customers into product co-creators), Channel (distribution innovation — Warby Parker's home try-on), and Service (experience innovation — the unboxing experience, post-purchase follow-up, personalization). Brands that innovate across 3+ types simultaneously create defensibility that product innovation alone cannot." + d2c_anti_patterns: + - "Obsessing over product innovation while neglecting experience, brand, and channel innovation. A better product sold through the same channel with the same brand story is a marginal improvement, not a defensible position." + - "Treating brand innovation as a marketing exercise rather than a strategic one. Brand innovation in D2C means fundamentally redefining what the category represents to customers — not a new logo or tagline." + d2c_example: "Dollar Shave Club innovated across five of the ten types simultaneously: Profit Model (subscription replacing one-time purchase), Network (direct-to-consumer eliminating retail), Channel (bathroom delivery replacing store visits), Brand (humor and irreverence replacing masculine aspiration), and Customer Engagement (community of members, not customers). Gillette could match any single innovation but could not replicate all five simultaneously — the combination was the moat." + benchmark_references: ["nps", "organic-traffic-pct", "repeat-purchase-rate"] + + - skill: "eisenhower-matrix" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "The Eisenhower Matrix is essential for D2C founders because the operational demands of a physical product business create constant urgency that crowds out strategic brand work. Urgent-and-Important: fulfillment issues, stockouts, customer escalations, ad account problems. Important-but-Not-Urgent: brand storytelling, community building, new product development, content strategy, influencer relationship development. Urgent-but-Not-Important: responding to every social media comment, daily ROAS optimization, minor supplier communications. Neither: vanity metric monitoring, competitive obsession, trend-chasing without strategic intent. Most D2C founders spend 80% of time in Quadrant 1 (operational fires) and Quadrant 3 (performative urgency), leaving no time for Quadrant 2 (brand building) — the only quadrant that builds a durable business." + d2c_anti_patterns: + - "Treating daily ROAS fluctuations as urgent. Paid media metrics are noisy day-to-day. Checking ROAS three times daily and adjusting budgets is Quadrant 3 activity disguised as Quadrant 1." + - "Deprioritizing brand content and community engagement because it is not 'urgent.' The brand is the business. Neglecting Quadrant 2 brand work guarantees a future where Quadrant 1 is dominated by rising CAC, declining NPS, and community atrophy." + d2c_example: "A DTC founder realizes that 90% of her week is consumed by Quadrant 1 (fulfillment issues, ad account management) and Quadrant 3 (responding to every DM, monitoring competitor launches). She uses the Eisenhower Matrix to reclaim 8 hours per week for Quadrant 2: 3 hours on brand content creation, 2 hours on community engagement, 2 hours on new product development, and 1 hour on influencer relationship building. Within 6 months, organic traffic increases from 22% to 38% of total — a direct result of sustained Quadrant 2 investment." + benchmark_references: ["organic-traffic-pct", "community-growth-rate"] + + - skill: "organisational-culture" + category: "frameworks" + d2c_relevance: "high" + d2c_context: "Organisational culture in D2C must be brand-aligned — the internal culture must be the brand culture. Employees who do not embody the brand's values produce inauthentic marketing, inconsistent customer experiences, and brand-diluting decisions. A wellness brand staffed by people who do not care about wellness will produce transactional customer interactions. A sustainability brand with a disposable-culture workplace will leak inauthenticity. D2C culture also faces unique challenges: small teams wearing many hats, the emotional intensity of building a consumer brand, the founder's personal identity often being fused with the brand identity, and the challenge of maintaining creative energy in a business that demands operational rigor." + d2c_anti_patterns: + - "Building a culture around metrics and growth without anchoring it in the brand's purpose. D2C teams that optimize only for revenue and ROAS produce work that feels transactional to customers." + - "Allowing the founder's identity to become the culture. The culture must be transferable and scalable — it cannot depend on one person being in every room." + d2c_example: "Patagonia's internal culture IS its brand: employees are outdoor enthusiasts, the office closes for good surf, environmental activism is a job requirement not a perk. This alignment ensures that every decision — product development, marketing, partnerships, supply chain — passes through the brand's values naturally. When Patagonia's founder donated the company to an environmental trust, employees celebrated rather than panicked — because the culture and the brand were always the same thing." + benchmark_references: ["nps", "organic-traffic-pct"] + + # ───────────────────────────────────────────── + # STORYTELLING (4 skills) + # ───────────────────────────────────────────── + + - skill: "story-structure-and-arc" + category: "storytelling" + d2c_relevance: "critical" + d2c_context: "Story structure is the single most important skill for D2C brand building. Every successful D2C brand is built on a founding story with a clear arc: the founder experienced a problem (status quo), was frustrated by existing solutions (rising action), had an insight or breakthrough (turning point), and created something better (resolution). This story is not marketing — it is the brand's soul. It appears in the 'About Us' page, in investor pitches, in influencer briefs, in customer emails, and in every piece of content. The story arc also applies to the customer's journey: they discover the brand (inciting incident), try the product (rising action), experience the transformation (climax), and become part of the community (resolution). D2C brands that cannot articulate a compelling story arc are functionally invisible in a market where attention is the scarcest resource." + d2c_anti_patterns: + - "Telling a generic founding story that could belong to any brand. 'We were frustrated with existing options and decided to create something better' is not a story — it is a template. The story must be specific, personal, and emotionally resonant." + - "Burying the story on the About page and not embedding it in every touchpoint. The founding story should be visible in packaging, product descriptions, email sequences, social media, and paid creative." + - "Updating the story to match marketing trends. The founding story is authentic and permanent. Revising it to sound more 'sustainable' or 'inclusive' because those themes are trending destroys the authenticity that makes the story powerful." + d2c_example: "Bombas' founding story follows a perfect arc: the founders learned that socks are the most requested clothing item at homeless shelters (inciting incident), were shocked that no sock company addressed this (rising action), designed a superior everyday sock with a one-for-one donation model (turning point), and built a community of people who feel good about buying socks (resolution). This story is not just marketing — it is the reason a customer chooses Bombas at $15/pair when identical socks exist for $3. The story converts a commodity into an identity purchase." + benchmark_references: ["organic-traffic-pct", "nps", "community-growth-rate"] + + - skill: "finding-your-stories" + category: "storytelling" + d2c_relevance: "critical" + d2c_context: "Finding stories in D2C means identifying the narratives that live within the brand, the customers, and the community — not manufacturing stories in a marketing brainstorm. The most powerful D2C stories come from four sources: the founder's personal experience with the problem (origin story), customer transformation stories (before/after with the product), behind-the-scenes narratives (how the product is made, who makes it, why design decisions were made), and community stories (how the brand connects people). D2C brands sit on a goldmine of stories and rarely mine it systematically. Every customer review, every DM, every influencer unboxing video contains a story that can be elevated into brand content." + d2c_anti_patterns: + - "Fabricating aspirational stories instead of finding authentic ones. Consumers, particularly Gen Z and millennials, have a finely calibrated authenticity detector. Manufactured stories feel manufactured." + - "Telling only the founder's story without amplifying customer stories. The brand's narrative should evolve from 'the founder's story' to 'our community's story' as it grows." + d2c_example: "Away luggage systematically mines stories from customers. Their content strategy centers on 'stories from the road' — real customer travel experiences with Away products. The stories are not about the luggage (hard-shell, spinner wheels — commodity features); they are about the destinations, the moments, and the identity of being a traveler. By finding and amplifying customer stories, Away shifted its brand from 'a luggage company' to 'a travel company' — a far more emotionally expansive positioning." + benchmark_references: ["ugc-volume", "social-engagement-rate", "nps"] + + - skill: "emotional-impact-in-stories" + category: "storytelling" + d2c_relevance: "critical" + d2c_context: "Emotional impact is the mechanism through which D2C brands convert attention into purchases and purchases into loyalty. D2C buying is fundamentally emotional — consumers buy what they identify with, not what is objectively best. The emotional arc of D2C storytelling follows a specific pattern: create empathy (the customer sees themselves in the story), build tension (the problem or aspiration is articulated), deliver resolution (the brand/product is the answer), and inspire action (the purchase is an expression of identity, not a transaction). Every touchpoint is an opportunity for emotional impact: the ad that makes someone stop scrolling, the product page that makes someone feel understood, the unboxing that makes someone reach for their phone to share, and the follow-up email that makes someone feel part of something larger." + d2c_anti_patterns: + - "Confusing emotional impact with sentimentality. Effective D2C emotional storytelling can be funny (Liquid Death), provocative (Patagonia's 'Don't Buy This Jacket'), nostalgic (Rowing Blazers), or earnest (Bombas). It does not have to be sentimental." + - "Pursuing emotional impact in advertising while delivering transactional post-purchase communication. The emotional arc must continue after the purchase — confirmation emails, shipping updates, and follow-ups should maintain the brand voice and emotional connection." + d2c_example: "Dove's 'Real Beauty' campaign created category-defining emotional impact not by talking about soap but by challenging beauty standards. The emotional mechanism: empathy (women who feel inadequate seeing other women like themselves), tension (the gap between real beauty and advertising beauty), resolution (Dove validates real beauty), and identity action (buying Dove means rejecting unrealistic standards). The campaign transformed a commodity product into an identity statement — the purest form of D2C emotional impact." + benchmark_references: ["social-engagement-rate", "organic-traffic-pct", "nps"] + + - skill: "storytelling-for-leaders" + category: "leadership" + d2c_relevance: "critical" + d2c_context: "In D2C, the founder IS the brand storyteller — often the brand's face on social media, in press interviews, and in investor meetings. Storytelling for leaders in D2C goes beyond internal communication; it is a public-facing, revenue-driving skill. The founder's ability to tell the brand story authentically, compellingly, and consistently across channels (Instagram, podcasts, investor meetings, team all-hands) directly correlates with organic growth, fundraising success, and team engagement. The founder's story becomes the brand's story: why they started, what they believe, what they are building, and why it matters." + d2c_anti_patterns: + - "Delegating brand storytelling entirely to a marketing team. The founder's authentic voice is irreplaceable. Marketing can amplify, format, and distribute — but the story must originate from genuine conviction." + - "Telling different stories to different audiences. Investors, customers, and employees should hear the same core story with audience-appropriate framing. Inconsistency destroys trust." + d2c_example: "Emily Weiss built Glossier's brand through personal storytelling on Into The Gloss, Instagram, and in investor meetings. Her story — a beauty editor who believed the industry talked at women instead of listening to them — was authentic, specific, and emotionally resonant. She told the same story everywhere, creating a coherent brand narrative that attracted customers, talent, and investors simultaneously. When she stepped back as CEO, the brand struggled precisely because the storytelling voice was so personally tied to her leadership." + benchmark_references: ["organic-traffic-pct", "community-growth-rate"] + + # ───────────────────────────────────────────── + # CREATIVE (3 skills) + # ───────────────────────────────────────────── + + - skill: "creative-identity-and-purpose" + category: "creative" + d2c_relevance: "critical" + d2c_context: "Creative identity is the brand itself. In D2C, the brand's creative identity — its visual language, tone of voice, aesthetic sensibility, and artistic point of view — IS the product's primary differentiator. Two identical moisturizers with different creative identities (minimalist clinical vs. colorful playful) attract different customers, command different prices, and build different communities. Creative purpose in D2C answers: Why does this brand exist beyond making money? What does it believe? What aesthetic or cultural vision does it champion? Brands with clear creative purpose (Patagonia: environmental activism; Glossier: accessible beauty; Liquid Death: anti-establishment fun) attract loyalty. Brands without creative purpose are interchangeable." + d2c_anti_patterns: + - "Defining creative identity through a mood board without connecting it to brand purpose. Aesthetic without meaning is decoration. The creative identity must express what the brand believes and who it exists for." + - "Allowing creative identity to drift through inconsistent execution across channels. The brand should look, sound, and feel identical whether a customer encounters it on TikTok, the website, in a package, or in a retail store." + d2c_example: "Aesop's creative identity is inseparable from its brand purpose: a belief that personal care should be an intellectual and sensory experience, not a commodity transaction. Every touchpoint expresses this: apothecary-style packaging with dense product descriptions, retail stores designed by architects with site-specific art installations, a literary recommendation program that pairs books with products. The creative identity commands a $40 price for hand soap in a market where the functional equivalent costs $3." + benchmark_references: ["nps", "organic-traffic-pct", "aov"] + + - skill: "creative-practice-and-habit" + category: "creative" + d2c_relevance: "high" + d2c_context: "D2C is a creative business that requires industrial creative output. A typical D2C brand produces hundreds of ad creatives, social media posts, email campaigns, product photographs, and content pieces annually. Creative practice and habit — the discipline of consistent, high-quality creative production — determines whether this output is brand-building or noise. D2C founders must build creative systems (not just creative moments): repeatable workflows for ad creative production, content calendars that sustain brand narrative, and feedback loops that connect creative output to performance data." + d2c_anti_patterns: + - "Treating creative as a project-based function instead of a continuous practice. D2C brands need new creative weekly, not quarterly. Creative fatigue on paid platforms (Meta, TikTok) means that even excellent ads decay in 2-4 weeks." + - "Outsourcing all creative to agencies without building internal creative capability. Agencies produce polished work but lack the brand intimacy and speed that D2C demands." + d2c_example: "Gymshark built its brand through relentless creative output: daily social media content, weekly new ad creative concepts, monthly influencer collaborations, and quarterly campaign refreshes. The creative practice is systematized: a content team produces 50+ pieces weekly, performance data feeds back to creative direction within 48 hours, and winning formats are iterated while losing formats are killed. This creative velocity — not a superior product — is what built a $1.3B brand in a commodity category." + benchmark_references: ["social-engagement-rate", "roas-by-channel", "ugc-volume"] + + - skill: "creative-collaboration-and-context" + category: "creative" + d2c_relevance: "high" + d2c_context: "Creative collaboration in D2C extends beyond the internal team to include the community, influencers, and customers as co-creators. The most effective D2C creative comes from collaboration between the brand's creative vision and the community's authentic voice. Influencer partnerships are creative collaborations, not media buys — the creator must have genuine creative freedom to produce content that resonates with their audience. UGC programs turn customers into creative collaborators. Product development benefits from community input (Glossier's community-driven product development). The creative context for D2C is the social media platform itself: content must be native to the platform (TikTok requires different creative than Instagram, which requires different creative than email)." + d2c_anti_patterns: + - "Over-scripting influencer content. Creators know their audience better than you do. Providing a brief and letting them create within it produces better results than providing a script." + - "Creating one piece of creative and adapting it across all platforms. Platform-native creative outperforms adapted creative by 2-5x. TikTok content shot on iPhone outperforms studio content repurposed from Instagram." + d2c_example: "Glossier's Into The Gloss blog was a creative collaboration engine before the product ever existed. Emily Weiss asked her community what they wanted, co-created products based on the response, and then invited the community to share their experiences — turning customers into the creative team. This collaborative model produced more authentic, resonant content than any internal team or agency could create, and it built a community that felt ownership over the brand." + benchmark_references: ["ugc-volume", "influencer-roi", "community-growth-rate"] + + # ───────────────────────────────────────────── + # PEOPLE & INFLUENCE (3 skills) + # ───────────────────────────────────────────── + + - skill: "influencing-and-persuading" + category: "people" + d2c_relevance: "high" + d2c_context: "Influencing and persuading in D2C operates through the brand, not through direct salesmanship. D2C brands do not hard-sell — they create desire through identity alignment, social proof, and community belonging. The persuasion stack in D2C follows a specific hierarchy: identity alignment ('this brand is for people like me'), social validation ('people I respect use this brand'), trust establishment ('the reviews, UGC, and expert endorsements confirm quality'), and value justification ('the price is fair for what this represents'). Each layer must be addressed in sequence. D2C brands that jump to value justification without building identity and trust face resistance." + d2c_anti_patterns: + - "Using traditional sales persuasion tactics (urgency, pressure, limited-time offers) as the primary conversion mechanism. These tactics work once but destroy the emotional connection that drives repeat purchasing." + - "Persuading through features and benefits rather than identity and belonging. 'Our serum contains 15% vitamin C' is a feature claim. 'Join 200,000 women who believe skincare should be simple, effective, and joyful' is an identity invitation." + d2c_example: "Nike's 'Just Do It' is the most powerful brand persuasion in history — not because it describes a product but because it articulates an identity. The persuasion hierarchy: identity alignment ('I am someone who acts, not just talks'), social validation ('athletes I admire wear Nike'), trust ('decades of product quality'), value justification ('I invest in my athletic identity'). Nike does not persuade you to buy shoes. Nike persuades you that you are the kind of person who wears Nike." + benchmark_references: ["nps", "repeat-purchase-rate", "organic-traffic-pct"] + + - skill: "connecting-with-people" + category: "people" + d2c_relevance: "high" + d2c_context: "Connecting with people in D2C means building genuine human relationships with customers, community members, influencers, and retail partners. D2C is uniquely positioned to create direct, personal connections because the brand owns the customer relationship (unlike wholesale or marketplace models). The most effective D2C brands treat every customer interaction — a support ticket, a social media comment, a review response — as a relationship moment, not a transaction. Founder accessibility (replying to DMs, writing personal emails to loyal customers, appearing in community spaces) builds a connection that no amount of advertising can replicate." + d2c_anti_patterns: + - "Automating all customer communication for efficiency. Efficiency matters, but D2C brands that feel like machines lose the personal connection that justifies their premium over commodity alternatives." + - "Building community as a marketing channel rather than a genuine human connection. Customers detect instrumentalized community instantly. Community must create real value for members beyond being marketed to." + d2c_example: "Chewy sends hand-written condolence cards to customers whose pets pass away — including a portrait of the pet painted by an employee. This is not scalable marketing; it is genuine human connection. The emotional impact creates brand loyalty that no discount, no product innovation, and no competitor can break. Chewy's repeat purchase rate and NPS reflect this: customers do not just buy pet food; they have a relationship with the brand." + benchmark_references: ["nps", "csat", "repeat-purchase-rate"] + + - skill: "reading-people" + category: "people" + d2c_relevance: "moderate" + d2c_context: "Reading people in D2C means understanding customers through their behavior, feedback, and community participation — not through demographic assumptions. D2C brands have unprecedented access to behavioral data: what customers browse, what they buy, what they return, what they review, what they share, and what they say in community forums. The skill of reading people translates to reading customer intent signals: a customer who views a product three times but does not buy has a different intent than one who adds to cart and abandons. A customer who posts UGC without incentive is a different person than one who leaves a review only after a discount prompt. Reading these signals accurately enables personalization that feels like understanding, not surveillance." + d2c_anti_patterns: + - "Relying on demographic personas instead of behavioral signals. 'Female, 28-35, urban, interested in wellness' describes millions of people. Behavioral segments (high-intent browsers, discount-sensitive buyers, loyal advocates) are more actionable." + - "Treating all customer data as equivalent. Behavioral data (what people do) is more reliable than stated preference data (what people say they want)." + d2c_example: "Stitch Fix built its entire business model on reading people through data: style preferences expressed through quizzes, purchase and return behavior, and feedback on each item. This behavioral reading enabled personalization at scale — each 'Fix' is curated based on what the customer does, not just what they say. The result was a subscription model with lower return rates and higher satisfaction than traditional e-commerce." + benchmark_references: ["repeat-purchase-rate", "return-rate", "csat"] + + # ───────────────────────────────────────────── + # WRITING (2 skills) + # ───────────────────────────────────────────── + + - skill: "writing-effective-emails" + category: "writing" + d2c_relevance: "critical" + d2c_context: "Email is the highest-ROI channel in D2C, and email writing quality directly determines revenue. D2C email must be brand-voiced, not template-generic. The welcome sequence is the brand's first private conversation with a new customer — it should tell the brand story, not blast discounts. Abandoned cart emails should remind the customer why they wanted the product (emotional restatement), not just that they forgot it. Post-purchase emails should deepen the relationship through content, community invitation, and gratitude — not immediately upsell. Win-back emails should acknowledge the absence and offer value, not just a discount code. Every email from a D2C brand is either building or eroding the brand relationship. Writing quality — tone, personality, relevance, and restraint — determines which." + d2c_anti_patterns: + - "Sending emails that could be from any brand. 'Hey {first_name}, don't forget your cart!' is invisible. Brand-voiced emails that sound like the brand's personality stand out in an inbox of 50 daily retail emails." + - "Over-emailing with promotional content. The optimal D2C email mix is roughly 60% value/content, 30% product/brand, 10% promotional. Brands that send 90% promotional emails train customers to ignore them or unsubscribe." + - "Sending the same email to all subscribers. Segmentation by purchase history, engagement level, and lifecycle stage is table stakes. A first-time buyer and a 10x repeat customer should receive fundamentally different messages." + d2c_example: "Chubbies built a cult email following by treating every email as entertainment first, brand storytelling second, and commerce third. Their emails are long, funny, personality-driven newsletters that people actually want to read — forward rates of 3-5% (vs. industry average of 0.5%). The result: email drives 35%+ of revenue, open rates consistently exceed 40%, and unsubscribe rates are among the lowest in D2C." + benchmark_references: ["email-revenue-pct", "repeat-purchase-rate", "ltv"] + + - skill: "writing-for-response" + category: "writing" + d2c_relevance: "high" + d2c_context: "Writing for response in D2C spans every piece of copy that must generate action: ad copy, product descriptions, SMS messages, landing pages, email subject lines, social captions, and calls-to-action. D2C response writing must balance brand voice with conversion mechanics. The response mechanism in D2C is emotional, not rational: customers do not buy because the product page presents the best argument but because the copy makes them feel something — understood, aspirational, part of a community, or simply delighted. The best D2C response writing uses the brand's unique voice to create desire rather than overcome objections." + d2c_anti_patterns: + - "Writing product descriptions that read like ingredient lists or spec sheets. D2C product descriptions should tell a micro-story: who this product is for, what experience it creates, and why it matters." + - "Using generic conversion copy ('Shop now,' 'Limited time offer') without brand voice. Every call-to-action should sound like the brand speaking." + d2c_example: "Outdoor Voices writes product descriptions that read like invitations to a lifestyle rather than merchandise listings. A pair of leggings is not '4-way stretch, moisture-wicking, high-rise waist' — it is 'for the run that starts as a walk and ends at brunch.' The response mechanism is identity aspiration, not feature comparison. This writing approach converts browsers into buyers because the customer is purchasing an identity, not a garment." + benchmark_references: ["conversion-rate", "aov", "email-revenue-pct"] + + # ───────────────────────────────────────────── + # GAME THEORY (3 skills) + # ───────────────────────────────────────────── + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + d2c_relevance: "high" + d2c_context: "The prisoner's dilemma surfaces in D2C through discount wars, channel conflict, and competitive dynamics. Discount wars: if one brand discounts, competitors feel pressure to match, and the entire category trains consumers to expect discounts — destroying margin for everyone. Channel conflict: selling on Amazon increases reach but undermines DTC margins and trains customers to buy through Amazon; every D2C brand faces this individually, but the collective result of all brands joining Amazon strengthens Amazon's dominance. Influencer economics: if brands cooperate to maintain reasonable influencer rates, the ecosystem is sustainable; if brands individually bid up rates, influencer costs spiral beyond ROI for everyone." + d2c_anti_patterns: + - "Initiating discount wars by running frequent deep promotions. The short-term revenue gain triggers competitive matching and trains your own customers to wait for sales." + - "Making Amazon decisions based only on your own channel economics without considering the collective effect. Every DTC brand that joins Amazon strengthens the platform that threatens all DTC brands." + d2c_example: "The mattress industry illustrates the prisoner's dilemma perfectly. Casper, Purple, Tuft & Needle, and Leesa each independently decided to invest heavily in paid Meta advertising. Individually rational — more spend, more customers. Collectively destructive — mattress CAC on Meta increased from $50 in 2016 to $300+ by 2020, making the entire DTC mattress category unprofitable. The brands were locked in a spending arms race where the only winner was Meta. Brands that recognized the dilemma first (Tuft & Needle pivoting to Amazon, Purple pivoting to retail) escaped the trap." + benchmark_references: ["cac-by-channel", "contribution-margin"] + + - skill: "first-mover-strategy" + category: "game-theory" + d2c_relevance: "high" + d2c_context: "First-mover advantage in D2C is primarily about brand positioning, not product innovation. Being first to claim a brand position ('the sustainable t-shirt brand,' 'the razor subscription,' 'the clean beauty brand') creates a category association that late entrants must either challenge or circumvent. First-mover advantages in D2C: brand awareness and category ownership (Allbirds owns 'sustainable sneakers'), community head start (early community members become brand evangelists), influencer relationships (early partnerships at lower rates), and organic search authority (SEO advantages compound over time). First-mover disadvantages: market education cost (Dollar Shave Club educated the market that Gillette then competed in), premature scaling risk, and the burden of defining a category without knowing its optimal boundaries." + d2c_anti_patterns: + - "Assuming product-level first-mover advantage is sustainable. Being the first DTC [product category] brand matters for 12-18 months. After that, the brand position (not the product priority) determines defensibility." + - "Moving fast without building the brand infrastructure to sustain the position. A first mover that captures attention without building community, content, and retention will be overtaken by a better-branded second mover." + d2c_example: "Allbirds was first to own the 'sustainable sneaker' position. The first-mover advantage was not the wool material (replicable) but the brand association: 'Allbirds = sustainable comfort footwear.' When Nike, Adidas, and dozens of startups entered sustainable footwear, Allbirds already owned the category perception. However, Allbirds illustrates the first-mover risk: the brand expanded too quickly into apparel and accessories before establishing dominance in footwear, diluting the very position that made it first." + benchmark_references: ["brand-awareness", "organic-traffic-pct", "cac-blended"] + + - skill: "information-asymmetry" + category: "game-theory" + d2c_relevance: "moderate" + d2c_context: "Information asymmetry in D2C exists between brands and consumers, brands and suppliers, and brands and advertising platforms. Brand-consumer asymmetry has collapsed: customers have access to reviews, ingredient lists, price comparisons, and Reddit threads that expose any inflated claim. The D2C brands that thrive in this transparent environment are those that embrace radical honesty — sharing manufacturing details, margin transparency, and honest product limitations. Brand-supplier asymmetry often favors the supplier: contract manufacturers know the true cost of production, the minimum viable quality, and which other brands they supply (your 'proprietary' product may be a white-label sold to 20 competitors). Brand-platform asymmetry favors Meta and Google: they know your campaign performance, your competitors' bids, and the true cost of reaching your audience — and they use this information to extract maximum ad spend." + d2c_anti_patterns: + - "Assuming consumers do not know the true cost of your product. Cost-of-goods breakdowns go viral regularly. Brands that claim 'premium quality' while using commodity ingredients or materials face trust destruction when the asymmetry collapses." + - "Ignoring that Meta and Google have perfect information about your advertising while you have imperfect information about theirs. The platform always wins the information game." + d2c_example: "Everlane built its brand on collapsing the brand-consumer information asymmetry. 'Radical Transparency' — showing factory photos, cost breakdowns, and markups — turned information that competitors hid into a brand asset. When other brands claimed premium quality, Everlane showed the math. This radical honesty created trust that conventional marketing could not match, and it attracted customers who valued the transparency itself as a brand attribute." + benchmark_references: ["nps", "organic-traffic-pct", "gross-margin"] + + # ───────────────────────────────────────────── + # THINKING & DECISIONS (2 skills) + # ───────────────────────────────────────────── + + - skill: "evaluating-and-deciding" + category: "thinking" + d2c_relevance: "high" + d2c_context: "D2C founders face a relentless stream of consequential decisions: Which channel to invest in? When to raise prices? Whether to launch on Amazon? When to enter retail? Whether to take the influencer deal at a premium rate? Which products to discontinue? Whether to offer free shipping? These decisions must be evaluated through the D2C-specific lens of brand impact alongside financial impact. A financially optimal decision (sell on Amazon to increase revenue) may be brand-destructive (lose customer relationship and face downward price pressure). The evaluation framework for D2C decisions should weight brand-building effect alongside ROI — because in D2C, the brand is the asset that compounds over time." + d2c_anti_patterns: + - "Evaluating decisions solely on financial metrics. The decision to run a 40%-off sale is financially attractive in the quarter but brand-destructive over the year. Both dimensions must be evaluated." + - "Delaying reversible decisions. Most D2C operational decisions (pricing, ad creative, product bundles) are reversible. The cost of delay often exceeds the cost of a wrong decision that generates learning." + d2c_example: "Glossier's decision to enter Sephora retail was evaluated on both financial and brand dimensions. Financially: access to millions of beauty buyers, incremental revenue, and reduced CAC through in-store discovery. Brand-wise: risk of diluting the DTC-first, community-driven identity; risk of being displayed alongside competitors; risk of losing the direct customer relationship for in-store buyers. Glossier delayed this decision for years — weighing the financial upside against the brand risk — and ultimately entered Sephora only when the brand was strong enough to maintain its identity within a retail environment." + benchmark_references: ["cac-blended", "contribution-margin", "nps"] + + - skill: "defining-and-exploring-problems" + category: "thinking" + d2c_relevance: "high" + d2c_context: "The most dangerous D2C problems are misdiagnosed. 'CAC is too high' is rarely a media buying problem — it is often a brand awareness problem, a creative problem, or a product-market fit problem. 'Repeat rate is low' may not be a retention problem but a product assortment problem (nothing to come back for) or an experience problem (the first purchase was disappointing). 'Revenue is flat' may not be a growth problem but a channel saturation problem or a pricing problem. Defining and exploring problems in D2C requires disciplining the tendency to jump to the obvious diagnosis (usually 'spend more on ads' or 'run a promotion') and instead exploring the root cause through the system of brand, product, experience, and distribution." + d2c_anti_patterns: + - "Diagnosing rising CAC as a media buying problem when it is a brand awareness problem. If organic traffic is declining while paid CAC rises, the root cause is that the brand is not generating enough demand on its own — no amount of ad optimization will fix that." + - "Diagnosing low repeat rate as a retention marketing problem when it is a product problem. If the product does not create genuine desire for repurchase, no amount of email sequences and loyalty points will fix it." + d2c_example: "A DTC skincare brand diagnoses its problem as 'CAC is too high — Meta ads are expensive.' Deeper exploration reveals the real problem: the brand has no differentiated story, its product page looks identical to 50 competitors, and it has zero organic traffic (meaning no one is seeking the brand out). The CAC problem is a symptom. The root cause is a brand problem — the company has built a product but not a brand. The solution is not better ad targeting; it is brand building through storytelling, community, and content." + benchmark_references: ["cac-blended", "organic-traffic-pct", "repeat-purchase-rate"] diff --git a/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-templates.yaml b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-templates.yaml new file mode 100644 index 0000000..4afdcb0 --- /dev/null +++ b/plugins/foreman/content/industry-packs/d2c-consumer/d2c-consumer-templates.yaml @@ -0,0 +1,924 @@ +# D2C Consumer Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for D2C consumer brands. The output agent loads these +# rules when generating documents with the D2C industry pack active. +# +# BRAND NARRATIVE is woven into every adapted template. D2C investors, board +# members, team leads, and the founder themselves must see brand health metrics +# alongside financial metrics, community data alongside revenue data, and the +# brand story alongside the business story. A D2C output that presents only +# financial data is structurally incomplete — it omits the asset (the brand) +# that generates those financial results. +# +# Key adaptation principles: +# - Brand narrative in every investor material +# - Community metrics alongside financial metrics +# - Channel mix analysis in every strategic template +# - Influencer ROI in marketing templates +# - Content calendar in operational templates +# - Customer love metrics (NPS, repeat rate, UGC) as primary health indicators +# +# Adaptation types: +# as-is — The template works without modification for D2C companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for D2C context. + +pack_metadata: + sector: "d2c-consumer" + display_name: "D2C Consumer" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C unit economics differ fundamentally from SaaS. Revenue is order-based not subscription-based, COGS includes physical product costs, and the cost stack includes fulfillment, shipping, returns, and payment processing as major variable cost lines. The template must present the full contribution margin waterfall that D2C investors evaluate." + field_changes: + - field: "Revenue per unit" + sector_label: "Average Order Value (AOV)" + sector_guidance: "Report AOV with trend (3-month, 6-month). Decompose into first-order AOV vs. repeat-order AOV — repeat orders typically have higher AOV through add-ons and bundles." + - field: "Cost per unit" + sector_label: "Fully Loaded CAC" + sector_guidance: "Include all acquisition costs: paid media, influencer fees, creative production, agency costs, and allocated marketing team salaries. Report blended and by top 3 channels. Distinguish new-customer CAC from blended (which is diluted by returning customers clicking ads)." + - field: "Margin per unit" + sector_label: "Contribution Margin Waterfall" + sector_guidance: "Present the full waterfall: Revenue - COGS = Gross Margin - Fulfillment - Shipping - Returns - Payment Processing = Contribution Margin (before marketing). This is the D2C-specific metric investors evaluate. Target: 25-40%." + - field: "Lifetime value" + sector_label: "LTV (Gross-Profit Adjusted)" + sector_guidance: "Calculate as AOV x Gross Margin % x Purchase Frequency x Average Customer Lifespan. Report based on observed cohort data (12-month LTV at minimum). Disclose the repeat purchase rate and frequency assumptions." + - field: "Acquisition cost" + sector_label: "CAC Payback Period" + sector_guidance: "Report in months or number of orders. For non-subscription D2C, express as 'first-order profitable' (payback < 1 order) or 'X orders to payback.' Include the percentage of customers who actually make X orders." + - field: "Unit economics ratio" + sector_label: "LTV:CAC Ratio" + sector_guidance: "Report the ratio using gross-profit-adjusted LTV and fully loaded CAC. Compare to the 3x-5x benchmark. If below 3x, show the improvement trajectory. If above 5x, address whether growth investment is sufficient." + sections_to_add: + - section_name: "D2C Metrics Dashboard" + placement: "before:Average Order Value (AOV)" + description: "Core D2C metrics in a format that consumer brand investors expect." + fields: + - "Revenue (monthly and trailing 12-month)" + - "Revenue growth rate (MoM and YoY)" + - "Orders (monthly)" + - "AOV (trend)" + - "Repeat Purchase Rate (trailing 12-month)" + - "Purchase Frequency" + - "Customer Count (total and active)" + - "Subscription Revenue % (if applicable)" + - section_name: "Channel Mix & Efficiency" + placement: "after:LTV:CAC Ratio" + description: "Revenue and acquisition efficiency by channel — essential for D2C investors." + fields: + - "Revenue by channel (DTC site, Amazon, wholesale, retail, subscription)" + - "Contribution margin by channel" + - "CAC by acquisition channel (Meta, Google, TikTok, Influencer, Organic)" + - "ROAS by paid channel" + - "Email/SMS revenue as % of total" + - "Organic traffic as % of total" + - section_name: "Brand Health Metrics" + placement: "end" + description: "Brand strength indicators that predict future financial performance." + fields: + - "NPS (overall and by cohort)" + - "Repeat Purchase Rate (trend)" + - "Community size and growth rate (email, SMS, social)" + - "UGC volume (monthly)" + - "Return Rate (overall and by category)" + sections_to_remove: [] + benchmark_references: ["cac-blended", "cac-by-channel", "ltv", "ltv-cac-ratio", "payback-period", "aov", "gross-margin", "contribution-margin", "repeat-purchase-rate", "email-revenue-pct", "organic-traffic-pct", "nps"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C investor updates should lead with brand health alongside financial performance. Investors in consumer brands want to see community growth, customer love, and brand momentum — not just revenue charts." + field_changes: + - field: "Financial highlights" + sector_label: "D2C Performance Summary" + sector_guidance: "Report: Revenue (month and trailing 12), Growth Rate (MoM and YoY), Contribution Margin %, Blended CAC, ROAS (blended), Cash Balance, Runway. Present as a compact table with current, prior, and trend." + - field: "Key metrics" + sector_label: "Brand & Customer Health" + sector_guidance: "Report: Repeat Purchase Rate, NPS, Email/SMS Revenue %, Organic Traffic %, Community Growth Rate. These metrics tell investors whether the brand is getting stronger or weaker independent of spend." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one brand win (new influencer partnership, press feature, UGC milestone, community event) alongside financial wins. Brand momentum matters to consumer investors." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges. Acknowledge rising CAC, creative fatigue, return rate concerns, or supply chain issues openly. D2C investors value founders who see problems clearly." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific. 'Introduction to [buyer name] at Sephora' or 'feedback on our Amazon strategy' are actionable. 'Help with marketing' is not." + sections_to_add: + - section_name: "Brand Momentum" + placement: "after:Brand & Customer Health" + description: "Qualitative brand signals that investors want to track." + fields: + - "Notable press, influencer, or social moments this month" + - "Community sentiment (qualitative read from reviews, DMs, social)" + - "Product feedback themes (from NPS follow-ups and reviews)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "cac-blended", "repeat-purchase-rate", "nps", "organic-traffic-pct"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C competitive dynamics include not just direct brand competitors but Amazon private label, incumbent CPG brands launching DTC, and retail private label. The brief must address all four threat vectors." + field_changes: + - field: "Competitor overview" + sector_label: "Competitive Map" + sector_guidance: "Map competitors on a 2x2: X-axis = price point (value to premium), Y-axis = brand strength (commodity to cult). Include direct D2C competitors, Amazon private label, and incumbent brands with DTC channels. Estimate revenue and funding where known." + - field: "Competitive advantages" + sector_label: "Brand Moat Analysis" + sector_guidance: "Assess defensibility along D2C-specific dimensions: brand identity (emotional connection), community (owned audience), content engine (creative velocity), product differentiation (formulation/design), direct customer relationship (data, email, SMS), and supply chain (proprietary manufacturing)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize: (1) Direct D2C competitors in the same category. (2) Amazon private label entering with similar product at 40% lower price. (3) Incumbent CPG brands launching DTC. (4) Retail private label (Target's Up & Up, Costco's Kirkland). (5) Content creators launching their own brands." + sections_to_add: + - section_name: "Brand Strength Comparison" + placement: "after:Brand Moat Analysis" + description: "Comparative brand metrics across competitors." + fields: + - "Social following and engagement rate by competitor" + - "Organic search volume (branded queries) by competitor" + - "Review volume and average rating by competitor" + - "Influencer association map (which creators promote which brands)" + - section_name: "Amazon Threat Assessment" + placement: "end" + description: "Specific assessment of Amazon's competitive position in the category." + fields: + - "Amazon private label presence in the category (yes/no, which products)" + - "Price comparison: brand DTC vs. Amazon private label" + - "Amazon search ranking for key category terms" + - "Percentage of category sales on Amazon vs. DTC" + sections_to_remove: [] + benchmark_references: ["cac-by-channel", "organic-traffic-pct", "nps"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C pitch decks must lead with the brand story — not a metrics slide. Consumer brand investors invest in brands they believe have cultural staying power. The deck must balance brand narrative with financial rigor." + field_changes: + - field: "Market opportunity" + sector_label: "Market Opportunity" + sector_guidance: "Size the market bottom-up: (target consumers in demographic) x (annual category spend per person) x (realistic market share in 5 years). Include the cultural tailwind: what shift in consumer behavior makes this brand inevitable now?" + - field: "Business model" + sector_label: "D2C Business Model" + sector_guidance: "Cover: channel strategy (DTC-first, Amazon, wholesale, retail roadmap), pricing model (one-time, subscription, membership), unit economics (contribution margin waterfall), and customer lifecycle (acquisition to repeat to advocate)." + - field: "Traction" + sector_label: "D2C Traction & Brand Health" + sector_guidance: "Two slides: Slide 1: Revenue trajectory, growth rate, customer count, AOV. Slide 2: Repeat purchase rate, NPS, organic traffic %, email/SMS revenue %, community size. The second slide proves brand strength." + sections_to_add: + - section_name: "Brand Story Slide" + placement: "before:Market Opportunity" + description: "The founding story and brand purpose — this is the emotional anchor of the D2C pitch." + fields: + - "Founder's personal connection to the problem" + - "The insight or breakthrough that led to the brand" + - "What the brand stands for (values, identity, cultural position)" + - "Visual: brand aesthetic, product photography, community imagery" + - section_name: "Community & Content Slide" + placement: "after:D2C Traction & Brand Health" + description: "Evidence of brand moat through community and content." + fields: + - "Community size and growth (email, SMS, social, loyalty)" + - "Engagement metrics (open rates, social engagement, UGC volume)" + - "Content strategy overview (organic, creator, brand)" + - "Influencer program summary (number of creators, ROI, sample content)" + - section_name: "Unit Economics Slide" + placement: "after:Community & Content Slide" + description: "The financial proof that the brand model works." + fields: + - "Contribution margin waterfall (visual)" + - "LTV:CAC ratio" + - "Payback period" + - "Channel-level CAC and ROAS" + - "Cohort repeat purchase curves" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "ltv-cac-ratio", "payback-period", "cac-by-channel", "repeat-purchase-rate", "nps", "organic-traffic-pct"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "A D2C strategic one-pager must anchor analysis in brand positioning, channel mix, and customer relationship strength — not just financial metrics." + field_changes: + - field: "Strategic position" + sector_label: "Brand Strategic Position" + sector_guidance: "Frame in D2C terms: brand positioning (what identity does the brand represent), competitive differentiation (why the brand matters beyond the product), channel strategy (DTC-first with selective expansion), and customer relationship depth (community, loyalty, advocacy)." + - field: "Key metrics" + sector_label: "D2C Health Metrics" + sector_guidance: "Core 6: Revenue + Growth Rate, Contribution Margin, LTV:CAC, Repeat Purchase Rate, Organic Traffic %, NPS. Compare each to D2C stage benchmarks." + sections_to_add: + - section_name: "Brand Flywheel Assessment" + placement: "end" + description: "Assessment of the brand's growth flywheel — the reinforcing loops that drive compounding growth." + fields: + - "Primary loop: brand story > content > community > organic > brand story" + - "Secondary loop: great product > reviews/UGC > social proof > new customers > more reviews" + - "Paid amplification loop: strong creative > paid distribution > new customers > UGC > better creative" + - "Key constraint: the bottleneck in the flywheel currently" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "ltv-cac-ratio", "repeat-purchase-rate", "organic-traffic-pct", "nps"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C market sizing must account for the cultural dimension: not just how many people buy in the category but how many people identify with the brand's positioning. A wellness brand's TAM is not 'the $50B supplement market' but 'the 15M consumers who build their identity around holistic health.'" + field_changes: + - field: "Total addressable market" + sector_label: "TAM / SAM / SOM" + sector_guidance: "Size bottom-up from identity group: (consumers who identify with the brand's positioning in the target demographic) x (average annual category spend per person). Cross-reference with industry category data (NRF, eMarketer, Statista). Do not use the entire category as TAM — a DTC brand will never capture the Walmart shopper." + - field: "Market dynamics" + sector_label: "Consumer Category Dynamics" + sector_guidance: "Address: category growth rate, DTC penetration (% of category sold online/direct), competitive density, Amazon private label presence, consumer identity trends driving category evolution, and sustainability/regulatory tailwinds." + sections_to_add: + - section_name: "Cultural Tailwind" + placement: "end" + description: "The cultural movement or consumer behavior shift that creates the opportunity." + fields: + - "What cultural or social shift makes this brand timely?" + - "Evidence of the shift (search trends, social media data, consumer surveys)" + - "How the brand captures this cultural moment" + sections_to_remove: [] + benchmark_references: ["organic-traffic-pct", "brand-awareness"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C due diligence includes brand-specific investigations absent from SaaS: supply chain verification, return rate analysis, channel economics decomposition, and brand health assessment." + field_changes: + - field: "Financial review" + sector_label: "D2C Metrics Verification" + sector_guidance: "Verify: Revenue by channel (DTC, Amazon, wholesale), contribution margin waterfall calculation, COGS breakdown (product cost vs. fulfillment vs. shipping vs. returns), CAC calculation methodology (blended vs. new-customer), LTV calculation methodology (cohort-based vs. formula), and inventory valuation." + - field: "Operational review" + sector_label: "Supply Chain & Operations Review" + sector_guidance: "Review: supplier agreements and concentration risk, manufacturing capacity and lead times, fulfillment partner SLAs and performance, return rate by product and channel, inventory turnover and aging, and shipping cost trends." + sections_to_add: + - section_name: "Brand Health Due Diligence" + placement: "end" + description: "D2C-specific brand assessment." + fields: + - "NPS data (overall, by cohort, trend)" + - "Repeat purchase rate by cohort (are newer cohorts performing better or worse?)" + - "Organic traffic percentage and trend (brand pull demand)" + - "Community engagement metrics (email open rates, social engagement, UGC)" + - "Customer reviews and sentiment analysis" + - "Influencer dependency risk (concentration of revenue in few creators)" + - section_name: "Channel Economics Review" + placement: "after:Brand Health Due Diligence" + description: "Per-channel profitability analysis." + fields: + - "Contribution margin by channel (DTC, Amazon, wholesale)" + - "CAC by paid channel with trend" + - "Attribution methodology assessment" + - "Amazon dependency risk (revenue %, brand control, MAP enforcement)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "cac-blended", "ltv", "repeat-purchase-rate", "return-rate", "nps", "organic-traffic-pct"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not sector-specific. Standard venture capital formats apply regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C decision rationale memos should explicitly address brand impact alongside financial impact for major decisions (Amazon entry, retail expansion, pricing changes, discount strategy)." + field_changes: + - field: "Decision context" + sector_label: "Decision Context: Brand & Financial" + sector_guidance: "Frame the decision through both lenses: what is the financial impact (revenue, margin, CAC) AND what is the brand impact (positioning, customer perception, community sentiment)? A financially positive decision with negative brand impact may be net-destructive." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "D2C exit scenarios involve distinct acquirer categories and valuation methodologies that differ from SaaS. Consumer brands are valued on revenue multiples, brand equity, and strategic fit — not ARR multiples." + field_changes: + - field: "Valuation methodology" + sector_label: "D2C Valuation Framework" + sector_guidance: "D2C brands are valued on revenue multiples (1-4x revenue for profitable brands, higher for high-growth/high-margin brands), brand equity indicators (NPS, organic traffic, community size), and strategic premium (category leadership, cultural relevance). Comparable M&A transactions: Dollar Shave Club ($1B/Unilever), Glossier ($1.8B peak valuation), Native ($100M/P&G). Rule of thumb: profitable D2C brands exit at 1.5-3x revenue; high-growth brands at 3-6x." + - field: "Potential acquirers" + sector_label: "D2C Acquirer Landscape" + sector_guidance: "Categorize: (1) Strategic CPG acquirers (Unilever, P&G, L'Oreal, Nestle) seeking DTC capabilities and younger demographics. (2) Retail acquirers (Target, Walmart) seeking exclusive brands. (3) PE acquirers (L Catterton, Advent, TSG) seeking profitable consumer brands. (4) Strategic brand houses (LVMH, Estee Lauder, Church & Dwight) seeking category expansion." + sections_to_add: + - section_name: "Brand Valuation Factors" + placement: "after:D2C Valuation Framework" + description: "Brand-specific factors that affect D2C exit valuation." + fields: + - "Brand awareness in target demographic (aided and unaided)" + - "Community size and engagement (owned audience value)" + - "Organic vs. paid revenue mix (high organic = higher multiple)" + - "Customer data asset value (first-party data in a privacy-restricted world)" + - "IP and formulation ownership (vs. contract manufacturer dependency)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "organic-traffic-pct", "nps", "repeat-purchase-rate"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C board meetings should present brand health alongside financial performance. Board members need to see whether the brand is getting stronger or weaker independent of revenue — because brand strength predicts future financial performance." + field_changes: + - field: "Financial summary" + sector_label: "D2C Financial Dashboard" + sector_guidance: "Present: Revenue (quarterly, YoY growth), Contribution Margin trend, Blended CAC trend, LTV:CAC, Channel revenue mix (DTC/Amazon/wholesale), Email/SMS revenue %, Cash balance, Runway. Compare each to plan and prior quarter." + - field: "Strategic priorities" + sector_label: "Brand & Growth Priorities" + sector_guidance: "Report against quarterly priorities with explicit outcomes. Include both financial outcomes (revenue, margin) and brand outcomes (NPS, organic traffic, community growth, creative performance). Flag any priority that is off-track." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: Brand risks (dilution, community fatigue, negative sentiment), Acquisition risks (rising CAC, creative fatigue, channel dependency), Operational risks (supply chain, fulfillment, return rates), Financial risks (runway, contribution margin erosion), Competitive risks (Amazon, funded competitors, incumbents)." + sections_to_add: + - section_name: "Brand Health Summary" + placement: "before:D2C Financial Dashboard" + description: "One-page brand health dashboard." + fields: + - "NPS (current and trend)" + - "Repeat Purchase Rate (current and trend)" + - "Organic Traffic % (current and trend)" + - "Community Size and Growth Rate" + - "UGC Volume and Quality" + - "Social Engagement Rate" + - section_name: "Channel Performance" + placement: "after:D2C Financial Dashboard" + description: "Per-channel economics and strategic assessment." + fields: + - "Revenue and contribution margin by channel" + - "CAC and ROAS by paid acquisition channel" + - "Email/SMS revenue and engagement metrics" + - "Influencer program performance and ROI" + - section_name: "Customer Cohort Analysis" + placement: "after:Channel Performance" + description: "Cohort-level retention and revenue data." + fields: + - "Repeat purchase curves by quarterly cohort" + - "LTV progression by cohort" + - "Return rate by cohort" + - "Cohort quality assessment (are newer cohorts better or worse?)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "cac-blended", "ltv-cac-ratio", "repeat-purchase-rate", "nps", "organic-traffic-pct", "email-revenue-pct", "return-rate"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C board agendas should allocate time to brand health discussion alongside financial review and include a standing creative/content review." + field_changes: + - field: "Agenda items" + sector_label: "D2C Board Agenda" + sector_guidance: "Standard D2C board agenda: (1) Brand Health & Financial Review — 15 min (pre-read, discussion only), (2) Strategic Deep-Dive — 30 min (rotating: channel strategy, brand positioning, product roadmap, influencer program, retail expansion), (3) Creative Review — 10 min (showcase recent content, ad creative, and community highlights), (4) Fundraising/Runway — 10 min, (5) CEO Asks — 10 min, (6) Executive Session — 15 min. Total: 90 minutes." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C risk categories include sector-specific risks: supply chain concentration, advertising platform dependency, brand perception vulnerability, and channel conflict." + field_changes: + - field: "Risk categories" + sector_label: "D2C Risk Categories" + sector_guidance: "Include: (1) Supply chain risk — manufacturer concentration, tariff exposure, lead time vulnerability. (2) Channel risk — Meta/Google dependency, Amazon channel conflict, retail partner concentration. (3) Brand risk — reputation vulnerability, influencer controversy, brand dilution. (4) Customer risk — repeat rate declining, NPS erosion, community fatigue. (5) Operational risk — fulfillment capacity, return rate, inventory management. (6) Competitive risk — Amazon private label, funded competitor, incumbent DTC launch." + sections_to_add: + - section_name: "Advertising Platform Dependency" + placement: "end" + description: "Assessment of dependency on paid advertising platforms." + fields: + - "Revenue attributed to each paid platform (Meta, Google, TikTok)" + - "Percentage of total acquisition from paid channels" + - "Business impact scenario: what if Meta CPMs increase 50%?" + - "Organic and owned-channel revenue coverage (could the business survive without paid ads?)" + sections_to_remove: [] + benchmark_references: ["cac-by-channel", "organic-traffic-pct", "return-rate"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C change initiatives must address brand impact explicitly. A proposed change (launching on Amazon, entering retail, restructuring pricing) should be evaluated for brand consistency alongside financial projections." + field_changes: + - field: "Proposal summary" + sector_label: "Initiative Summary: Brand & Business Impact" + sector_guidance: "Present both the financial case and the brand case. For every major initiative, answer: Does this strengthen or weaken the brand? Does this bring us closer to or further from our core customer? Does this increase or decrease brand control?" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C compensation includes equity-heavy packages for early employees, and roles specific to D2C (creative director, performance marketing, community manager) have market-specific benchmarks." + field_changes: + - field: "Compensation benchmarks" + sector_label: "D2C Compensation Benchmarks" + sector_guidance: "Use D2C-specific comp data: Pave and Carta for general roles, Periscopeiq for e-commerce-specific roles. Key D2C roles to benchmark: Creative Director, Performance Marketing Lead, Community Manager, Influencer/Creator Partnerships Manager, Supply Chain/Operations Lead, CX Lead. D2C brands compete for talent with agencies, CPG companies, and other D2C brands — comp must reflect this market." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C compliance centers on product safety (FDA, CPSC), advertising claims (FTC), data privacy (consumer data from DTC transactions), and increasingly on sustainability claims regulation." + field_changes: + - field: "Regulatory landscape" + sector_label: "D2C Compliance Landscape" + sector_guidance: "Cover: product safety regulations (FDA for supplements, beauty, food; CPSC for consumer goods), advertising claims compliance (FTC influencer disclosure rules, substantiation requirements for health/performance claims), data privacy (CCPA, GDPR for international customers), sustainability claims (FTC Green Guides, EU anti-greenwashing directive), and state-level sales tax compliance." + sections_to_add: + - section_name: "Influencer & Claims Compliance" + placement: "end" + description: "D2C-specific compliance areas around marketing claims and influencer disclosure." + fields: + - "FTC disclosure compliance status for influencer partnerships" + - "Substantiation for product claims (clinical testing, certifications)" + - "Sustainability claims verification" + - "Customer review authenticity compliance" + sections_to_remove: [] + benchmark_references: [] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "D2C CEO succession is complicated by the founder-brand identity fusion. When the founder IS the brand's public face, succession requires a brand transition plan alongside a leadership transition plan." + field_changes: + - field: "Succession criteria" + sector_label: "CEO & Brand Stewardship Succession" + sector_guidance: "Address the dual transition: leadership succession (operational, financial, strategic) AND brand stewardship succession (who will be the brand voice, who maintains the creative vision, how to preserve brand authenticity post-founder). Include: brand guidelines documentation status, creative team independence level, and founder's role in brand-facing activities." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C action plans should include brand impact metrics alongside operational metrics. Every initiative should connect to both financial KPIs and brand health indicators." + field_changes: + - field: "Success metrics" + sector_label: "D2C KPI Targets" + sector_guidance: "Define success using both financial and brand metrics: revenue impact, contribution margin change, CAC/ROAS impact, AND brand indicators (NPS change, repeat rate impact, organic traffic shift, community growth). Every action should connect to at least one brand health metric." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C initiative briefs should quantify brand impact alongside financial impact and include channel implications." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected D2C Impact" + sector_guidance: "Quantify: revenue contribution, contribution margin impact, CAC/ROAS effect, AND brand impact (NPS, organic traffic, community growth, UGC). Include the channel where the initiative will execute and whether it affects other channels." + - field: "Resource requirements" + sector_label: "Resource Requirements" + sector_guidance: "In D2C, creative capacity is the scarcest resource alongside capital. Quantify: creative hours needed (photography, video, copy, design), media budget, inventory commitment, and operational capacity. State the opportunity cost — what creative and inventory budget will not be allocated if this initiative proceeds." + sections_to_add: + - section_name: "Content & Creative Requirements" + placement: "after:Expected D2C Impact" + description: "Creative production needs for the initiative." + fields: + - "Creative assets needed (photography, video, ad creative, email, social)" + - "Content calendar impact" + - "Influencer/creator involvement (if any)" + - "Timeline for creative production" + sections_to_remove: [] + benchmark_references: ["cac-blended", "contribution-margin", "repeat-purchase-rate"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C project kickoffs should define success in terms of both commerce metrics and brand metrics, and include a content/creative plan alongside the operational plan." + field_changes: + - field: "Success criteria" + sector_label: "Success Metrics: Commerce & Brand" + sector_guidance: "Define 2-3 commerce metrics (revenue, conversion, AOV, CAC) AND 1-2 brand metrics (NPS, organic traffic, UGC, engagement) that this project will move. Include baseline, target, measurement method, and evaluation date." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["cac-blended", "aov", "nps"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C hiring scorecards should include brand affinity assessment and D2C-specific competency requirements." + field_changes: + - field: "Required competencies" + sector_label: "D2C-Specific Competencies" + sector_guidance: "For creative roles: brand voice mastery, content production velocity, platform-native content creation. For marketing roles: paid social expertise (Meta, TikTok), email/SMS strategy, influencer management, attribution methodology understanding. For ops roles: 3PL management, inventory planning, supply chain optimization, returns management. For all roles: genuine brand affinity (does the candidate use and love the product?)." + sections_to_add: + - section_name: "Brand Fit Assessment" + placement: "end" + description: "Assessment of the candidate's connection to the brand." + fields: + - "Does the candidate genuinely use or want to use the product?" + - "Can the candidate articulate the brand's positioning in their own words?" + - "Does the candidate's personal aesthetic and values align with the brand?" + - "D2C experience relevance (stage, category, role type)" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C incident postmortems must include brand impact assessment. A fulfillment failure, product quality issue, or social media crisis has brand consequences that persist longer than the operational incident." + field_changes: + - field: "Impact assessment" + sector_label: "Customer, Brand & Business Impact" + sector_guidance: "Quantify: orders affected, customers impacted, revenue at risk, refunds/credits issued, support tickets generated, AND brand impact: social media mentions, review sentiment change, NPS impact, press coverage. Include the customer communication timeline and effectiveness." + sections_to_add: + - section_name: "Brand Recovery Plan" + placement: "after:Customer, Brand & Business Impact" + description: "Steps to recover brand trust after the incident." + fields: + - "Customer communication (what was sent, when, how received)" + - "Social media response and sentiment tracking" + - "Recovery gesture (credits, replacements, personal outreach)" + - "Long-term brand impact assessment (will this affect NPS, reviews, repeat rate?)" + sections_to_remove: [] + benchmark_references: ["nps", "csat", "return-rate"] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Retrospective structure is not sector-specific. Content naturally addresses D2C challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C team health should include creative-performance alignment, brand voice consistency across teams, and the emotional health of teams that carry the brand's public identity." + field_changes: + - field: "Health indicators" + sector_label: "D2C Team Health Indicators" + sector_guidance: "Include: creative team velocity (content pieces produced per week), creative-performance alignment (shared metrics, collaborative planning), customer service satisfaction (support team CSAT), brand voice consistency across channels, and creative team burnout indicators (the team that produces the brand's public face bears unique emotional load)." + sections_to_add: + - section_name: "Creative-Performance Alignment" + placement: "end" + description: "Assessment of collaboration between brand/creative and performance marketing." + fields: + - "Shared metrics dashboard (do both teams track the same KPIs?)" + - "Joint creative brief process (do performance insights inform creative direction?)" + - "Content production velocity vs. demand" + - "Creative team morale and burnout indicators" + sections_to_remove: [] + benchmark_references: [] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C culture values must be brand-aligned. Internal culture should be the brand culture — employees should embody the values the brand communicates to customers." + field_changes: + - field: "Values" + sector_label: "Brand-Aligned Values" + sector_guidance: "Ensure internal values are consistent with brand values. If the brand communicates sustainability to customers, the internal culture must practice sustainability. If the brand communicates community, the internal culture must be community-oriented. Inconsistency between internal culture and external brand promise creates inauthenticity that customers detect." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "D2C role descriptions should reference D2C-specific experience requirements, brand affinity criteria, and the specific D2C metrics the role is accountable for." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Metric Ownership" + sector_guidance: "For each responsibility, specify the D2C metric the role owner is accountable for. Examples: Head of Growth owns blended CAC, ROAS by channel, and new customer acquisition; Head of Retention owns repeat purchase rate, email/SMS revenue %, and NPS; Creative Director owns social engagement rate, UGC volume, and ad creative performance; Operations Lead owns fulfillment cost per order, return rate, and shipping time." + - field: "Required experience" + sector_label: "D2C Experience Requirements" + sector_guidance: "Specify: D2C company-stage experience required, relevant product categories, specific platform expertise (Shopify, Klaviyo, Meta Ads Manager), and whether the candidate must have genuine affinity for the product category." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A D2C founder's weekly review should balance financial metrics, brand health, and creative output — the three pillars of a direct-to-consumer business." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly D2C Dashboard" + sector_guidance: "Review weekly: Revenue (daily and WoW), Orders, AOV, Blended ROAS, Email/SMS revenue, Support tickets, Return requests. Monthly cadence (do not review weekly): CAC, LTV, NPS, Repeat Rate, Contribution Margin. Brand pulse weekly: social engagement, UGC highlights, community sentiment, content performance." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Identify the single most important thing. In D2C, this is often: approving new creative, resolving a supply chain issue, reviewing influencer partnership, making a channel decision, or addressing a customer experience failure. One priority, not ten." + sections_to_add: + - section_name: "Brand Pulse" + placement: "after:Weekly D2C Dashboard" + description: "Weekly qualitative brand health check." + fields: + - "Best customer feedback this week (from reviews, DMs, emails)" + - "Worst customer feedback this week (and what is being done about it)" + - "Community highlights (notable UGC, social moments)" + - "Creative pipeline status (what is being produced this week)" + sections_to_remove: [] + benchmark_references: ["aov", "roas-by-channel", "email-revenue-pct"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C decision journals should capture both the financial data and the brand instinct behind decisions, and include brand impact as a success criterion." + field_changes: + - field: "Decision context" + sector_label: "Decision Context: Data & Brand Instinct" + sector_guidance: "Record: the financial data (metrics, forecasts, costs), the brand considerations (positioning impact, community response, brand consistency), the instinct (what does your gut say?), and the decision criteria (what metric or outcome will confirm the decision was correct, including brand metrics)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C annual reviews should assess brand evolution alongside financial performance and set brand goals alongside growth targets." + field_changes: + - field: "Year in review" + sector_label: "D2C Year in Review" + sector_guidance: "Assess: revenue growth (actual vs. plan by channel), contribution margin evolution, CAC trend, LTV trend, AND brand progress: NPS change, organic traffic growth, community size, repeat rate evolution, notable brand moments, product launches, and influencer program development." + - field: "Next year goals" + sector_label: "Next Year D2C Targets" + sector_guidance: "Set targets across all dimensions: revenue by channel, contribution margin target, CAC target, AND brand targets: NPS goal, organic traffic % target, community growth target, content production plan, influencer program scale, and new product launches." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["contribution-margin", "cac-blended", "ltv-cac-ratio", "repeat-purchase-rate", "nps", "organic-traffic-pct"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C stakeholder maps should include D2C-ecosystem-specific categories: influencer partners, retail buyers, manufacturers, 3PL partners, and community leaders." + field_changes: + - field: "Stakeholder categories" + sector_label: "D2C Stakeholder Ecosystem" + sector_guidance: "Include: Investors (lead, follow-on, angels, advisors), Key Customers (top spenders, brand ambassadors, UGC creators), Influencer Partners (top performers, emerging creators, agency contacts), Supply Chain (manufacturers, 3PL, packaging suppliers), Retail Partners (buyers, category managers), Community (power users, moderators, brand evangelists), and Advisors (D2C operators, category experts, agency partners)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C negotiation prep should include D2C-specific contexts and leverage points for influencer, retail, supplier, and investor negotiations." + field_changes: + - field: "Negotiation type" + sector_label: "D2C Negotiation Context" + sector_guidance: "Classify: influencer/creator deal (rates, exclusivity, usage rights), retail partnership (margins, placement, MAP pricing), manufacturer (MOQs, payment terms, formulation IP), fundraising (valuation, terms), or Amazon (terms, advertising, brand protection). Each has distinct D2C-specific dynamics." + - field: "BATNA" + sector_label: "BATNA and D2C Leverage" + sector_guidance: "D2C-specific leverage: for influencer negotiations — alternative creators, in-house content capability, UGC program. For retail — DTC channel as alternative, other retail partners, consumer demand data. For manufacturer — alternative suppliers, ability to bring production in-house. For fundraising — profitability path, multiple term sheets, organic growth rate." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["influencer-roi", "contribution-margin"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C founder mental health is affected by D2C-specific stressors: the public visibility of the brand (social media criticism feels personal), the emotional weight of being the brand's face, the relentless creative demands, and the volatility of consumer attention." + field_changes: + - field: "Stress indicators" + sector_label: "D2C-Specific Stress Indicators" + sector_guidance: "Include: identity fusion (self-worth tied to brand performance and social media metrics), creative exhaustion (the pressure to constantly produce content), public criticism sensitivity (taking negative reviews, social media comments, and press personally), comparison anxiety (obsessing over competitor brands and influencers), ROAS anxiety (checking ad dashboards multiple times daily), and isolation (not discussing brand challenges with peers because the brand image must remain positive)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "D2C founders should include D2C-specific learning areas in their development plans." + field_changes: + - field: "Learning areas" + sector_label: "D2C Learning Priorities" + sector_guidance: "Consider D2C-specific learning areas: brand building and storytelling, paid media (Meta, TikTok, Google), email/SMS strategy (Klaviyo mastery), influencer marketing, supply chain and manufacturing, financial modeling for physical products, content strategy, community building, and retail expansion." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A D2C founder's advisory board should include D2C-specific expertise areas." + field_changes: + - field: "Advisor categories" + sector_label: "D2C Advisory Needs" + sector_guidance: "Map advisors to D2C-specific needs: brand building (someone who has built a consumer brand to $50M+ revenue), paid acquisition (Meta/TikTok expert who manages $1M+/month), supply chain (someone who has scaled manufacturing and fulfillment), retail expansion (someone with buyer relationships at target retailers), finance (D2C-specific P&L and fundraising expertise), creative (content strategy and production at scale), and community (someone who has built a brand community beyond a mailing list)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C 'client' QBRs are typically with retail partners, wholesale accounts, or brand collaboration partners. The QBR should present brand performance data and sell-through metrics relevant to the partner relationship." + field_changes: + - field: "Performance summary" + sector_label: "Brand & Sell-Through Performance" + sector_guidance: "Present: sell-through rate (for retail/wholesale), revenue contribution, customer feedback from the partner channel, brand awareness metrics in the partner's customer base, and marketing support provided (co-op advertising, in-store displays, influencer features)." + - field: "Account status" + sector_label: "Partnership Health" + sector_guidance: "Present: sales velocity by SKU in the partner channel, inventory status (overstock/understock), promotional calendar alignment, and brand presentation compliance (MAP pricing, merchandising standards)." + - field: "Next steps" + sector_label: "Growth Opportunities" + sector_guidance: "Identify expansion: additional SKUs for the partner, exclusive products or bundles, joint marketing campaigns, seasonal promotions, and broader distribution (more stores, more shelf space)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["repeat-purchase-rate", "nps"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C 'client' onboarding typically means onboarding a retail partner, wholesale account, or brand collaboration partner. The packet should communicate brand standards, operational expectations, and marketing support." + field_changes: + - field: "Getting started steps" + sector_label: "Partnership Launch Guide" + sector_guidance: "Define: (1) Brand guidelines and merchandising standards — how the product must be displayed and described. (2) Ordering process and minimum quantities. (3) MAP pricing policy. (4) Marketing and promotional calendar. (5) Point of contact for brand questions, inventory issues, and marketing collaboration." + - field: "Resources" + sector_label: "Brand Assets & Resources" + sector_guidance: "Include: brand guideline document, product photography library, marketing materials, co-op advertising templates, and brand story summary for partner staff training." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C proposals are typically to retail partners or brand collaboration partners. The proposal should lead with brand strength and consumer demand rather than product specifications." + field_changes: + - field: "Pricing" + sector_label: "Wholesale Pricing & Terms" + sector_guidance: "Present: wholesale pricing structure, minimum order quantities, payment terms, MAP pricing policy, and return/exchange policy. Frame the margin opportunity for the retail partner." + - field: "Scope" + sector_label: "Partnership Scope" + sector_guidance: "Define: initial product assortment, distribution scope (number of stores/locations), exclusivity terms (if any), marketing support commitment, and launch timeline." + sections_to_add: + - section_name: "Brand Demand Evidence" + placement: "before:Wholesale Pricing & Terms" + description: "Proof of consumer demand that the retail partner benefits from." + fields: + - "DTC revenue and growth rate (proof of consumer demand)" + - "Social media following and engagement (brand visibility)" + - "Press coverage and notable media mentions" + - "Customer demographics (alignment with partner's customer base)" + sections_to_remove: [] + benchmark_references: ["organic-traffic-pct", "nps", "community-growth-rate"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C SLAs with retail/wholesale partners cover fulfillment, brand standards, and operational commitments rather than software uptime." + field_changes: + - field: "Service levels" + sector_label: "Brand & Operational Commitments" + sector_guidance: "D2C SLA components: (1) Order fulfillment timeline (typically 48-72 hours). (2) Fill rate commitment (% of ordered units shipped). (3) Product quality standards. (4) Packaging and presentation standards. (5) Marketing and promotional support commitments. (6) MAP pricing enforcement." + - field: "Remediation" + sector_label: "Remediation Terms" + sector_guidance: "Define: credit structure for late/incomplete shipments, product quality issue resolution process, and termination triggers for sustained SLA breaches." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C project updates are typically for retail launch projects, brand collaboration projects, or product development partnerships. The update should track progress toward launch readiness." + field_changes: + - field: "Progress summary" + sector_label: "Launch/Project Progress" + sector_guidance: "Track: product readiness (inventory produced, quality approved), marketing materials (photography, copy, merchandising), operational setup (EDI, ordering, fulfillment), and timeline compliance (on track, delayed, at risk)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C case studies for retail or wholesale partners should demonstrate brand demand, sell-through performance, and customer response — the metrics that retail buyers care about." + field_changes: + - field: "Results" + sector_label: "Partnership Results" + sector_guidance: "Present: sell-through rate, revenue per linear foot (retail) or revenue per listing (online), customer feedback and ratings at the partner, repeat purchase rate through the partner channel, and marketing campaign performance (if co-op advertising was executed)." + sections_to_add: + - section_name: "Brand Impact on Partner" + placement: "end" + description: "How the D2C brand enhanced the partner's business." + fields: + - "New customer acquisition driven by the brand" + - "Category growth or market share impact" + - "Foot traffic or site traffic driven by brand awareness" + - "Social media and PR coverage featuring the partnership" + sections_to_remove: [] + benchmark_references: ["repeat-purchase-rate", "nps"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C partnership memos (for retail, influencer, or brand collaborations) should frame the partnership through the brand lens — why the partnership strengthens both brands rather than just generating transactions." + field_changes: + - field: "Partnership rationale" + sector_label: "Brand Alignment & Strategic Rationale" + sector_guidance: "Articulate: why the partner's brand and our brand are complementary (shared values, overlapping audience, aesthetic alignment), what the partnership communicates to customers (brand elevation, not desperation), and how the partnership strengthens both brands' positions." + sections_to_add: + - section_name: "Community & Content Opportunity" + placement: "end" + description: "How the partnership creates content and community value." + fields: + - "Joint content opportunities (co-branded content, creator collaborations)" + - "Community cross-pollination (email list, social, events)" + - "UGC potential from the collaboration" + - "Press and earned media opportunity" + sections_to_remove: [] + benchmark_references: ["community-growth-rate", "social-engagement-rate"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "D2C analysis reports for partners should include brand performance data and consumer insights alongside commercial metrics." + field_changes: + - field: "Analysis findings" + sector_label: "Brand & Commercial Analysis" + sector_guidance: "Include both brand metrics (awareness, NPS, social sentiment in the partner's market) and commercial metrics (sales, margin, growth rate). For retail partners, include shelf-level performance data and competitive comparisons within the category at the partner." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["nps", "brand-awareness"] diff --git a/plugins/foreman/content/industry-packs/e-commerce/e-commerce-benchmarks.yaml b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-benchmarks.yaml new file mode 100644 index 0000000..bc770a6 --- /dev/null +++ b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-benchmarks.yaml @@ -0,0 +1,907 @@ +# E-Commerce Industry Pack — Benchmarks +# +# 24 e-commerce-specific metrics with real benchmark data sourced from public +# studies. The orchestrator surfaces these when applying quantitative skills, +# generating output templates with financial metrics, or diagnosing conversion, +# retention, fulfillment, and margin issues. +# +# These metrics are purpose-built for physical product businesses — D2C brands, +# online retail, subscription boxes, dropshipping, and omnichannel retail. They +# do not translate from SaaS definitions. Inventory, logistics, returns, and +# seasonality are first-class concerns throughout. +# +# Primary data sources: +# - Shopify Commerce Benchmarks (2023, 2024) +# - BigCommerce State of E-Commerce (2023, 2024) +# - Klaviyo E-Commerce Benchmarks (2024) +# - National Retail Federation (NRF) Annual Reports (2023, 2024) +# - eMarketer / Insider Intelligence (2024) +# - Metrilo E-Commerce Retention Studies (2023) +# - Baymard Institute Cart Abandonment Research (2024) +# - ShipBob Fulfillment Benchmarks (2024) +# - Narvar Returns & Exchanges Report (2023) +# - Statista Digital Commerce Compass (2024) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded or established e-commerce companies at the +# relevant stage. + +pack_metadata: + sector: "e-commerce" + display_name: "E-Commerce" + version: "1.0.0" + description: "Benchmark data for e-commerce companies spanning revenue, conversion, retention, unit economics, marketing efficiency, fulfillment, and inventory metrics for physical product businesses." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # REVENUE & GROWTH METRICS + # ───────────────────────────────────────────── + + - name: "Revenue" + id: "revenue" + category: "growth" + definition: "Total net sales after returns and discounts, representing the actual cash collected from product sales in a given period." + formula: "Gross Sales - Returns - Discounts - Allowances" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $50K annual revenue after 12 months of operations" + signal: "Insufficient traction to sustain operations. Either product-market fit is absent or distribution is ineffective." + below_average: + value: "$50K-$250K annual revenue at 12 months" + signal: "Early traction but not yet at a scale that demonstrates repeatable demand. Likely burning personal capital or a small seed round." + average: + value: "$250K-$1M annual revenue at 12 months" + signal: "Meaningful traction. Enough signal to attract institutional seed investment if growth trajectory and unit economics are healthy." + good: + value: "$1M-$5M annual revenue at 12 months" + signal: "Strong product-market fit. Revenue supports hiring, inventory investment, and channel diversification." + excellent: + value: "> $5M annual revenue at 12 months" + signal: "Exceptional traction. Rare for a first-year brand — indicates viral adoption, influencer-driven demand, or category creation." + stage_notes: + seed: "Absolute revenue matters less than growth rate and unit economics. A $200K run-rate with 20%+ MoM growth is investable." + series_a: "Typical e-commerce Series A requires $3M-$10M annual revenue with clear path to profitability and strong repeat purchase rates." + series_b_plus: "Series B typically requires $10M-$50M+ revenue. Growth rate expectations moderate but contribution margin must be positive." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "eMarketer / Insider Intelligence" + year: "2024" + related_metrics: ["gmv", "aov", "conversion-rate"] + related_skills: ["balanced-scorecard", "business-model-canvas"] + caveats: "Revenue must be net of returns and discounts. Gross sales that include unfulfilled orders or pending returns inflate the metric and mislead investors." + + - name: "Gross Merchandise Volume (GMV)" + id: "gmv" + category: "growth" + definition: "Total dollar value of merchandise sold through the e-commerce platform before deducting returns, discounts, and allowances. For brands selling through multiple channels, GMV includes all channels." + formula: "Number of Orders x Average Order Value (before deductions)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "GMV growth < 15% YoY after reaching $500K annual GMV" + signal: "Growth is decelerating below the category average. Likely indicates channel saturation or product assortment stagnation." + below_average: + value: "GMV growth 15-30% YoY" + signal: "Moderate growth, roughly tracking the overall e-commerce market. Not differentiating from the category." + average: + value: "GMV growth 30-60% YoY" + signal: "Healthy growth above market rate. Indicates working acquisition channels and reasonable product-market fit." + good: + value: "GMV growth 60-100% YoY" + signal: "Strong growth. Product resonates and distribution channels are scaling effectively." + excellent: + value: "GMV growth > 100% YoY" + signal: "Exceptional growth. Typically driven by viral product, category tailwind, or successful channel expansion (e.g., wholesale + DTC + Amazon)." + stage_notes: + seed: "GMV is a vanity metric at seed stage if margins are negative. Investors care about unit economics alongside volume." + series_a: "GMV should demonstrate channel diversification. Single-channel GMV is fragile." + series_b_plus: "GMV growth rate decelerates naturally. Focus shifts to net revenue, contribution margin, and repeat purchase economics." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "eMarketer / Insider Intelligence" + year: "2024" + related_metrics: ["revenue", "aov", "conversion-rate"] + related_skills: ["balanced-scorecard", "growth-share-matrix"] + caveats: "GMV is not revenue. Investors distinguish between the two. GMV inflated by returns, discounts, and marketplace pass-through revenue misleads more than it informs. Always present GMV alongside net revenue and return rate." + + - name: "Conversion Rate" + id: "conversion-rate" + category: "growth" + definition: "The percentage of website or store visitors who complete a purchase. The single most important operational metric in e-commerce — it transforms traffic into revenue." + formula: "(Number of Orders / Number of Unique Visitors) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.0%" + signal: "Severe friction in the purchase funnel. Either traffic is unqualified, pricing is misaligned, or the site experience is fundamentally broken." + below_average: + value: "1.0-1.5%" + signal: "Below industry median. Funnel optimization, pricing review, and traffic quality audit are immediate priorities." + average: + value: "1.5-2.5%" + signal: "Inline with e-commerce industry averages. Room for optimization but not a crisis." + good: + value: "2.5-4.0%" + signal: "Above average conversion. Indicates strong product-market fit, effective merchandising, and a well-optimized purchase funnel." + excellent: + value: "> 4.0%" + signal: "Exceptional conversion. Typically seen in niche categories with high-intent traffic, subscription models, or repeat-heavy businesses." + stage_notes: + seed: "Conversion rate below 1% in the first three months is expected while product pages, photography, and pricing are being refined." + series_a: "2%+ conversion rate demonstrates repeatable demand. Conversion rate stability across traffic sources is a stronger signal than the absolute number." + series_b_plus: "Conversion optimization becomes a dedicated function. Marginal improvements at scale have outsized revenue impact." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "BigCommerce State of E-Commerce" + year: "2024" + - source: "Statista Digital Commerce Compass" + year: "2024" + related_metrics: ["cart-abandonment-rate", "aov", "revenue"] + related_skills: ["four-ps-marketing", "net-promoter-score", "cialdini-influence"] + caveats: "Conversion rate varies dramatically by category: fashion averages 1.5-2%, electronics 1-1.5%, food/beverage 3-5%, niche hobby 4-6%. Compare within category, not across." + + - name: "Average Order Value (AOV)" + id: "aov" + category: "growth" + definition: "The average dollar amount spent per transaction, reflecting pricing strategy, product mix, and cross-sell/upsell effectiveness." + formula: "Total Revenue / Number of Orders" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $30 (general merchandise); declining QoQ" + signal: "Low AOV compresses contribution margin. Fulfillment and shipping costs consume a disproportionate share of revenue." + below_average: + value: "$30-$50 (general merchandise)" + signal: "Below the threshold where per-order economics work without aggressive cost control on fulfillment." + average: + value: "$50-$80 (general merchandise)" + signal: "Inline with e-commerce medians. Per-order economics are viable with standard fulfillment operations." + good: + value: "$80-$150" + signal: "Healthy AOV that supports profitable per-order economics even with standard shipping and fulfillment costs." + excellent: + value: "> $150" + signal: "Strong AOV that creates comfortable contribution margins. Often seen in premium brands, luxury goods, or curated bundles." + stage_notes: + seed: "AOV is heavily influenced by product selection. Focus on whether AOV covers COGS + fulfillment + shipping with margin remaining." + series_a: "AOV should be stable or increasing. Declining AOV signals discounting dependency or mix shift to lower-value products." + series_b_plus: "AOV optimization (bundling, upsells, premium tiers) becomes a dedicated growth lever." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "BigCommerce State of E-Commerce" + year: "2024" + related_metrics: ["revenue", "conversion-rate", "contribution-margin"] + related_skills: ["four-ps-marketing", "cialdini-influence", "business-model-canvas"] + caveats: "AOV benchmarks vary enormously by category. Apparel averages $80-$120, beauty $45-$65, home goods $100-$180, supplements $50-$70. Category-specific benchmarks are essential." + + - name: "Cart Abandonment Rate" + id: "cart-abandonment-rate" + category: "growth" + definition: "The percentage of shopping sessions where items are added to the cart but the purchase is not completed. Measures friction in the checkout process and price sensitivity at the moment of commitment." + formula: "(1 - (Completed Purchases / Cart Creations)) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 80%" + signal: "Severe checkout friction, unexpected costs (shipping, tax), or trust issues. Every 5-point reduction represents significant revenue recovery." + below_average: + value: "75-80%" + signal: "Above average abandonment. Common culprits: mandatory account creation, slow page load, limited payment options, surprise shipping costs." + average: + value: "68-75%" + signal: "Inline with the global e-commerce average of approximately 70%. Optimization opportunities exist but the funnel is functional." + good: + value: "60-68%" + signal: "Below-average abandonment, indicating a well-optimized checkout with transparent pricing and minimal friction." + excellent: + value: "< 60%" + signal: "Exceptional. Typically achieved by subscription models, one-click reorder businesses, or brands with very high purchase intent traffic." + stage_notes: + seed: "Cart abandonment above 80% is common in early-stage stores. Priority: eliminate surprise costs and simplify checkout before investing in recovery flows." + series_a: "Abandonment recovery flows (email sequences, retargeting) should be recapturing 5-15% of abandoned carts." + series_b_plus: "Multi-touch abandonment recovery, dynamic incentives, and checkout A/B testing are standard practice." + data_sources: + - source: "Baymard Institute Cart Abandonment Research" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["conversion-rate", "aov", "revenue"] + related_skills: ["cialdini-influence", "four-ps-marketing", "systems-thinking"] + caveats: "Cart abandonment includes window shoppers and comparison shoppers. Not all abandonment is recoverable. Focus on the delta between cart creation with purchase intent and completion, not the raw abandonment rate." + + # ───────────────────────────────────────────── + # CUSTOMER ACQUISITION & MARKETING METRICS + # ───────────────────────────────────────────── + + - name: "Customer Acquisition Cost (CAC)" + id: "cac" + category: "unit-economics" + definition: "The fully loaded cost to acquire one new purchasing customer, including all marketing spend, agency fees, creative production, and allocated team costs." + formula: "Total Marketing & Sales Spend / Number of New Customers Acquired (same period)" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "CAC > AOV (acquiring customers at a loss on first order)" + signal: "Every new customer costs more to acquire than their first purchase generates. Viable only if repeat purchase rate and LTV are exceptionally strong." + below_average: + value: "CAC = 50-100% of AOV" + signal: "Marginal first-order economics. Business depends heavily on repeat purchases to justify acquisition spend." + average: + value: "CAC = 25-50% of AOV" + signal: "Standard e-commerce acquisition economics. First-order contribution is thin but positive." + good: + value: "CAC = 10-25% of AOV" + signal: "Healthy acquisition efficiency. First-order contribution margin is meaningful." + excellent: + value: "CAC < 10% of AOV or > 50% organic acquisition" + signal: "Exceptional. Either acquisition channels are highly efficient or the brand generates substantial organic demand through word-of-mouth, SEO, or viral content." + stage_notes: + seed: "CAC is volatile at low volumes. Track by channel from day one — the blended number masks which channels work." + series_a: "CAC should be declining or stable as channel mix matures. Rising CAC with stable conversion signals channel saturation." + series_b_plus: "CAC management becomes a portfolio optimization exercise across 5-10 channels. Watch for marginal CAC diverging from blended CAC." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "eMarketer / Insider Intelligence" + year: "2024" + related_metrics: ["ltv", "roas", "cpa-by-channel", "organic-traffic-pct"] + related_skills: ["four-ps-marketing", "business-model-canvas", "balanced-scorecard"] + caveats: "E-commerce CAC must include full funnel costs: ad spend, creative, landing page, agency fees, and attributed team time. Under-counting CAC by reporting only media spend is the most common error." + + - name: "Customer Lifetime Value (LTV)" + id: "ltv" + category: "unit-economics" + definition: "The total gross profit expected from a customer over their entire relationship with the brand, accounting for repeat purchases, average order value, and gross margin." + formula: "AOV x Gross Margin % x Purchase Frequency x Average Customer Lifespan (or AOV x Gross Margin % / (1 - Repeat Purchase Rate) for retention-based)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "LTV:CAC ratio < 2:1" + signal: "Customers do not generate enough lifetime gross profit to justify acquisition cost. The business is either a funnel to nowhere or requires radical improvement in retention or margins." + below_average: + value: "LTV:CAC ratio 2:1-3:1" + signal: "Marginal economics. Profitable at the unit level but insufficient cushion for operational costs, inventory risk, and growth investment." + average: + value: "LTV:CAC ratio 3:1-4:1" + signal: "Standard e-commerce economics. Enough headroom to fund operations and modest growth." + good: + value: "LTV:CAC ratio 4:1-6:1" + signal: "Strong economics. Indicates a loyal customer base or a highly efficient acquisition engine." + excellent: + value: "LTV:CAC ratio > 6:1" + signal: "Exceptional. Either the brand commands extraordinary loyalty and repeat rates, or acquisition costs are unusually low. Verify that this is not under-investment in growth." + stage_notes: + seed: "LTV is largely theoretical at seed. Estimate from cohort repeat purchase data at 3-6 months and project conservatively." + series_a: "LTV projections must be grounded in actual cohort data with 12+ months of history. Forward LTV estimates exceeding 2x observed data are discounted." + series_b_plus: "LTV segmentation by acquisition channel, product category, and customer cohort is standard. Blended LTV masks important variation." + data_sources: + - source: "Metrilo E-Commerce Retention Studies" + year: "2023" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["cac", "repeat-purchase-rate", "purchase-frequency", "aov", "gross-margin"] + related_skills: ["business-model-canvas", "balanced-scorecard", "net-promoter-score"] + caveats: "LTV calculations in e-commerce must use gross margin, not revenue. An LTV based on revenue ignores COGS, fulfillment, and returns — producing a dangerously inflated number." + + - name: "Return on Ad Spend (ROAS)" + id: "roas" + category: "unit-economics" + definition: "Revenue generated per dollar of advertising spend. The primary efficiency metric for paid acquisition in e-commerce, measuring how effectively ad dollars convert into sales." + formula: "Revenue from Ads / Ad Spend" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2x ROAS" + signal: "Advertising is unprofitable after accounting for COGS and fulfillment costs. At typical 50% gross margins, 2x ROAS means break-even before operating expenses." + below_average: + value: "2x-3x ROAS" + signal: "Marginal profitability on ad spend. Viable for prospecting campaigns that drive high-LTV customers, but not sustainable as the blended target." + average: + value: "3x-5x ROAS" + signal: "Healthy ad efficiency. At 50% gross margin, 4x ROAS yields a 2:1 gross-profit-to-ad-spend ratio." + good: + value: "5x-8x ROAS" + signal: "Strong ad efficiency, typically seen in retargeting, branded search, and email-driven campaigns." + excellent: + value: "> 8x ROAS" + signal: "Exceptional. Often indicates brand strength driving high organic overlap with paid campaigns. Verify incrementality — high blended ROAS can mask low marginal ROAS." + stage_notes: + seed: "ROAS below 2x is common while testing creative, audiences, and product-market fit through paid channels. Set a loss budget and optimize toward 3x within 90 days." + series_a: "Blended ROAS should stabilize at 3-5x across channels. Channel-level ROAS visibility is essential for capital allocation." + series_b_plus: "Marginal ROAS becomes more important than blended ROAS. Incrementality testing (holdout groups, geo-lift studies) is necessary to avoid over-attributing organic demand to paid channels." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "eMarketer / Insider Intelligence" + year: "2024" + related_metrics: ["cac", "cpa-by-channel", "contribution-margin"] + related_skills: ["four-ps-marketing", "balanced-scorecard", "scenario-planning"] + caveats: "ROAS measures revenue, not profit. A 4x ROAS on a product with 30% gross margin yields only $1.20 gross profit per $1 ad spend. Always evaluate ROAS through the lens of gross margin." + + - name: "Cost Per Acquisition by Channel" + id: "cpa-by-channel" + category: "unit-economics" + definition: "The cost to acquire a new customer through each distinct marketing channel, enabling capital allocation decisions across the acquisition portfolio." + formula: "Channel-Specific Marketing Spend / New Customers Acquired via Channel" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "Channel CPA > first-order gross profit across all paid channels" + signal: "No paid channel is profitable on the first order. Business is entirely dependent on repeat purchases to recover acquisition costs." + below_average: + value: "Channel CPA = 50-100% of first-order gross profit for primary channels" + signal: "Primary channels are marginally profitable on first order. Secondary channels may be underwater." + average: + value: "Top 2 channels with CPA < 50% of first-order gross profit" + signal: "Core channels are working. Sufficient margin to test and expand into additional channels." + good: + value: "3+ channels with CPA < 30% of first-order gross profit" + signal: "Diversified, efficient acquisition. No single-channel dependency." + excellent: + value: "5+ channels with profitable first-order CPA; organic > 40% of new customers" + signal: "Highly diversified acquisition with strong organic flywheel. Resilient to any single channel disruption." + stage_notes: + seed: "Focus on 1-2 channels and master them before diversifying. Channel CPA at early volumes is unreliable." + series_a: "Channel diversification is expected. Investors want to see that growth is not dependent on a single platform (especially Facebook/Meta or Google)." + series_b_plus: "Full channel portfolio management with marginal CPA analysis, attribution modeling, and incrementality testing." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "eMarketer / Insider Intelligence" + year: "2024" + related_metrics: ["cac", "roas", "organic-traffic-pct", "email-revenue-pct"] + related_skills: ["four-ps-marketing", "scenario-planning", "systems-thinking"] + caveats: "Attribution is inherently imperfect. Last-click attribution under-credits top-of-funnel channels. Multi-touch attribution requires investment in tooling. At minimum, track both last-click and first-click CPA." + + - name: "Email Revenue Percentage" + id: "email-revenue-pct" + category: "unit-economics" + definition: "The percentage of total e-commerce revenue attributable to email marketing campaigns and flows. Measures the effectiveness of the owned-channel retention engine." + formula: "(Revenue from Email Campaigns + Revenue from Email Flows) / Total Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10% of revenue from email" + signal: "Email is under-developed as a channel. The business is over-dependent on paid acquisition for both new and repeat customers." + below_average: + value: "10-20% of revenue from email" + signal: "Basic email program in place (welcome series, cart abandonment) but not fully exploiting the channel." + average: + value: "20-30% of revenue from email" + signal: "Healthy email contribution. Core flows (welcome, abandonment, post-purchase, win-back) are active and generating meaningful revenue." + good: + value: "30-40% of revenue from email" + signal: "Strong email program driving substantial owned-channel revenue. Reduces paid media dependency and improves unit economics." + excellent: + value: "> 40% of revenue from email" + signal: "Best-in-class email marketing. Typically indicates a loyal subscriber base with sophisticated segmentation, personalization, and lifecycle automation." + stage_notes: + seed: "Email is the highest-ROI channel from day one. Welcome series and cart abandonment flows should launch before any paid advertising." + series_a: "Email revenue % above 25% is a strong signal of brand health and customer loyalty. Investors value owned channels." + series_b_plus: "Email sophistication includes predictive send-time optimization, dynamic content, advanced segmentation by purchase history, and zero-party data integration." + data_sources: + - source: "Klaviyo E-Commerce Benchmarks" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["repeat-purchase-rate", "ltv", "organic-traffic-pct"] + related_skills: ["four-ps-marketing", "cialdini-influence", "net-promoter-score"] + caveats: "Email revenue attribution is inflated by post-view and post-click windows. A 5-day attribution window is standard; 30-day windows over-credit email for purchases that would have occurred organically." + + - name: "Organic Traffic Percentage" + id: "organic-traffic-pct" + category: "unit-economics" + definition: "The percentage of total website sessions originating from organic channels: direct traffic, organic search (SEO), social media (organic), and referral traffic. Measures brand strength and independence from paid acquisition." + formula: "(Direct + Organic Search + Organic Social + Referral Sessions) / Total Sessions x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 30% organic traffic" + signal: "Dangerously dependent on paid channels. Any disruption — platform policy change, CPM increase, account suspension — threatens survival." + below_average: + value: "30-40% organic traffic" + signal: "Paid-heavy acquisition mix. Brand awareness and SEO need investment." + average: + value: "40-55% organic traffic" + signal: "Balanced traffic mix. Paid acquisition scales the business while organic provides a foundation." + good: + value: "55-70% organic traffic" + signal: "Strong brand and SEO presence. Lower sensitivity to paid media cost fluctuations." + excellent: + value: "> 70% organic traffic" + signal: "Exceptional brand strength. Organic demand dominates — paid media serves to accelerate rather than sustain." + stage_notes: + seed: "Organic traffic below 20% is normal in the first six months. SEO and brand building are long-term investments." + series_a: "Organic traffic above 40% demonstrates that the brand generates demand independent of ad spend. A strong signal for investors." + series_b_plus: "Organic traffic mix should be increasing as brand investment compounds. Declining organic share while scaling paid is a warning signal." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "Statista Digital Commerce Compass" + year: "2024" + related_metrics: ["cac", "email-revenue-pct", "cpa-by-channel"] + related_skills: ["four-ps-marketing", "blue-ocean-strategy", "tipping-point"] + caveats: "Direct traffic includes both genuine brand-driven visits and mis-attributed traffic (dark social, incognito browsing, app-to-web transitions). Direct traffic is not a reliable proxy for brand strength alone." + + # ───────────────────────────────────────────── + # RETENTION & REPEAT PURCHASE METRICS + # ───────────────────────────────────────────── + + - name: "Repeat Purchase Rate" + id: "repeat-purchase-rate" + category: "retention" + definition: "The percentage of customers who make more than one purchase within a defined period (typically 12 months). The fundamental retention metric for e-commerce, equivalent in importance to NRR in SaaS." + formula: "(Customers with 2+ Orders / Total Customers) x 100 — measured over a cohort period" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15% repeat purchase rate (12-month)" + signal: "The business is a one-purchase funnel. Every sale requires new customer acquisition. Unit economics are unsustainable without radical improvement." + below_average: + value: "15-25%" + signal: "Below average retention. Some repeat behavior exists but is not strong enough to sustain growth without heavy acquisition spending." + average: + value: "25-35%" + signal: "Inline with e-commerce averages. Repeat customers are generating meaningful revenue but there is room for lifecycle optimization." + good: + value: "35-50%" + signal: "Strong repeat behavior. The brand has earned loyalty. Repeat customers typically generate 40-60% of total revenue." + excellent: + value: "> 50%" + signal: "Exceptional retention. Typically seen in consumable categories (supplements, food, beauty) or subscription models. The business has a built-in recurring revenue engine." + stage_notes: + seed: "Repeat purchase data requires time to mature. At 6 months, a 20% repeat rate from your first cohort is encouraging." + series_a: "Repeat purchase rate is the single most important metric for e-commerce Series A investors. It proves that the product is worth buying again." + series_b_plus: "Repeat rate should be segmented by cohort, product category, and acquisition channel. Blended repeat rate masks channel quality differences." + data_sources: + - source: "Metrilo E-Commerce Retention Studies" + year: "2023" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["purchase-frequency", "time-between-purchases", "ltv", "email-revenue-pct"] + related_skills: ["net-promoter-score", "product-life-cycle", "cialdini-influence"] + caveats: "Repeat purchase rate is heavily category-dependent. One-time purchase categories (mattresses, furniture) naturally have lower repeat rates — the metric must be evaluated within category norms." + + - name: "Purchase Frequency" + id: "purchase-frequency" + category: "retention" + definition: "The average number of orders placed by a customer within a defined period (typically 12 months). Measures the intensity of the customer relationship beyond the binary of repeat/not-repeat." + formula: "Total Orders / Total Unique Customers (over period)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.2 orders per customer per year" + signal: "Virtually no repeat purchasing. The business resets to zero each month, dependent entirely on new customer acquisition." + below_average: + value: "1.2-1.5 orders per customer per year" + signal: "Minimal repeat behavior. A small segment of loyal customers inflates the average." + average: + value: "1.5-2.0 orders per customer per year" + signal: "Moderate frequency. Inline with general e-commerce averages across non-consumable categories." + good: + value: "2.0-3.5 orders per customer per year" + signal: "Healthy frequency indicating product assortment breadth and customer engagement." + excellent: + value: "> 3.5 orders per customer per year" + signal: "High-frequency purchasing. Typical of consumable brands, subscription models, or multi-category retailers with broad assortment." + stage_notes: + seed: "Purchase frequency data is noisy with small customer bases. Focus on the first-to-second purchase rate as the leading indicator." + series_a: "Frequency trends matter more than absolutes. An increasing frequency over successive cohorts is a strong signal." + series_b_plus: "Frequency segmentation reveals where to invest: what product categories, what customer segments, and what touchpoints drive additional orders." + data_sources: + - source: "Metrilo E-Commerce Retention Studies" + year: "2023" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["repeat-purchase-rate", "time-between-purchases", "aov", "ltv"] + related_skills: ["four-ps-marketing", "product-life-cycle", "cialdini-influence"] + caveats: "Purchase frequency is heavily skewed by power buyers. Median frequency is usually far below mean. Report both to avoid distortion by a small number of high-frequency customers." + + - name: "Time Between Purchases" + id: "time-between-purchases" + category: "retention" + definition: "The average number of days between a customer's consecutive orders. Defines the natural repurchase cycle and informs lifecycle marketing timing." + formula: "Average of (Date of Order N+1 - Date of Order N) across all customers with 2+ orders" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 180 days between purchases" + signal: "Extended repurchase cycle. Customer relationships are episodic rather than habitual. Lifecycle marketing must work hard to maintain engagement across long gaps." + below_average: + value: "120-180 days" + signal: "Moderate cycle. Typical for seasonal or discretionary purchases." + average: + value: "60-120 days" + signal: "Standard for many e-commerce categories. Allows 2-4 purchases per year." + good: + value: "30-60 days" + signal: "Healthy repurchase cycle. Common in consumable categories (beauty, supplements, food) and brands with strong lifecycle programs." + excellent: + value: "< 30 days" + signal: "Rapid repurchase. Typical of subscription models, frequent consumables, or habitual purchase categories." + stage_notes: + seed: "Establishing the natural repurchase cycle early is critical for email and SMS flow timing." + series_a: "Time between purchases should inform all lifecycle marketing cadence. Misaligned communication timing is the primary cause of unsubscribes." + series_b_plus: "Advanced programs personalize communication timing to each customer's individual repurchase cycle rather than using category averages." + data_sources: + - source: "Metrilo E-Commerce Retention Studies" + year: "2023" + - source: "Klaviyo E-Commerce Benchmarks" + year: "2024" + related_metrics: ["purchase-frequency", "repeat-purchase-rate", "email-revenue-pct"] + related_skills: ["systems-thinking", "product-life-cycle"] + caveats: "Time between purchases is category-specific and influenced by product consumption rate. A 90-day gap for a skincare brand may signal a problem, while the same gap for an apparel brand is normal." + + # ───────────────────────────────────────────── + # UNIT ECONOMICS & MARGIN METRICS + # ───────────────────────────────────────────── + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "The percentage of revenue remaining after deducting cost of goods sold (COGS), representing the fundamental profitability of the product before operating expenses, fulfillment, and shipping." + formula: "(Revenue - COGS) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "Thin margins that leave insufficient room for marketing, fulfillment, shipping, and operations. Common in commodity products and dropshipping." + below_average: + value: "40-50%" + signal: "Below average margins. Viable with high volume and lean operations, but vulnerable to cost increases." + average: + value: "50-60%" + signal: "Inline with e-commerce averages. Sufficient margin to fund marketing and operations with careful management." + good: + value: "60-70%" + signal: "Healthy margins indicating either brand premium, proprietary products, or cost-efficient sourcing. Strong foundation for scaling." + excellent: + value: "> 70%" + signal: "Premium margins. Typically found in digital-physical hybrids, luxury goods, or brands with extreme pricing power. Supports aggressive growth investment." + stage_notes: + seed: "Gross margin should be the first number any e-commerce founder calculates. If gross margin is below 40%, the business model requires reconsideration before investing in growth." + series_a: "Investors expect 50%+ gross margin for DTC brands. Below 50%, the path to profitability is narrow and requires exceptional operational efficiency." + series_b_plus: "Gross margin should be stable or improving through supplier negotiation, manufacturing scale, and mix shift toward higher-margin products." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "NRF Annual Report" + year: "2024" + related_metrics: ["contribution-margin", "aov", "return-rate"] + related_skills: ["business-model-canvas", "balanced-scorecard", "porters-five-forces"] + caveats: "E-commerce gross margin must include all product-related costs: manufacturing, raw materials, packaging, duties, and tariffs. Excluding packaging or duties inflates the metric." + + - name: "Contribution Margin" + id: "contribution-margin" + category: "financial" + definition: "The per-order profit after deducting all variable costs: COGS, fulfillment, shipping, payment processing, and the variable portion of returns. The true measure of per-order economics." + formula: "(Revenue - COGS - Fulfillment Cost - Shipping Cost - Payment Processing Fee - Variable Return Cost) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10% contribution margin" + signal: "Per-order economics are barely positive or negative. The business destroys value with every sale before marketing is even considered." + below_average: + value: "10-20%" + signal: "Thin contribution margin. Marketing must be extremely efficient (low CAC) for the business to reach profitability." + average: + value: "20-30%" + signal: "Standard e-commerce contribution margins. Room for marketing spend and operational costs." + good: + value: "30-40%" + signal: "Healthy contribution margin. Strong per-order economics that support both growth investment and profitability." + excellent: + value: "> 40%" + signal: "Exceptional per-order economics. Typically seen in high-AOV, high-margin brands with efficient fulfillment operations." + stage_notes: + seed: "Contribution margin must be positive before scaling. Scaling a negative-contribution-margin business accelerates failure." + series_a: "Contribution margin above 20% is the floor for institutional investment. Below 20%, the path to profitability requires unrealistic assumptions about scale efficiencies." + series_b_plus: "Contribution margin optimization through fulfillment efficiency, shipping negotiation, and returns reduction is a key operational focus." + data_sources: + - source: "ShipBob Fulfillment Benchmarks" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["gross-margin", "fulfillment-cost-per-order", "shipping-cost-pct", "return-rate"] + related_skills: ["business-model-canvas", "balanced-scorecard", "kaizen-bpr"] + caveats: "Contribution margin in e-commerce must include the variable cost of returns (return shipping, restocking, damaged goods). Excluding returns overstates contribution margin by 5-15 percentage points in high-return categories like apparel." + + - name: "Return Rate" + id: "return-rate" + category: "financial" + definition: "The percentage of orders returned by customers. A critical e-commerce metric because returns reverse revenue, consume fulfillment resources, and often render products unsellable." + formula: "(Number of Returned Orders / Total Orders Shipped) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 30% return rate" + signal: "Return rate is destroying unit economics. Common in apparel without size guidance or products with misleading photography. Requires immediate root cause analysis." + below_average: + value: "20-30%" + signal: "High returns, particularly for non-apparel categories. Even for apparel, rates above 25% indicate sizing, quality, or expectations issues." + average: + value: "10-20%" + signal: "Inline with e-commerce averages. Apparel sits at the upper end (15-20%); electronics and home goods at the lower end (5-10%)." + good: + value: "5-10%" + signal: "Below average returns indicating accurate product representation, good sizing guidance, and appropriate customer expectations." + excellent: + value: "< 5%" + signal: "Exceptional return rate. Typical of consumable products, personalized items, or categories where returns are impractical." + stage_notes: + seed: "Return rate above 20% in the first three months demands immediate investigation. Product photography, descriptions, and sizing guides are the usual suspects." + series_a: "Return rate must be factored into all unit economics. Present investors with 'gross revenue' and 'net revenue after returns' side by side." + series_b_plus: "Return analytics by SKU, reason code, and customer segment drive targeted interventions. Exchange programs that preserve revenue are preferable to refunds." + data_sources: + - source: "Narvar Returns & Exchanges Report" + year: "2023" + - source: "NRF Annual Report" + year: "2024" + related_metrics: ["contribution-margin", "gross-margin", "nps"] + related_skills: ["kaizen-bpr", "systems-thinking", "net-promoter-score"] + caveats: "Return rate varies dramatically by category: apparel 15-30%, electronics 5-15%, beauty 3-8%, furniture 5-10%. Category benchmarks are essential. Also distinguish between return rate (orders returned) and return volume (units returned — a multi-item order may have partial returns)." + + # ───────────────────────────────────────────── + # FULFILLMENT & OPERATIONS METRICS + # ───────────────────────────────────────────── + + - name: "Fulfillment Cost per Order" + id: "fulfillment-cost-per-order" + category: "efficiency" + definition: "The total cost to pick, pack, and prepare an order for shipment, excluding the shipping carrier cost itself. Measures warehouse and logistics operational efficiency." + formula: "(Total Warehouse Labor + Packaging Materials + Warehouse Rent + Software + Equipment) / Total Orders Fulfilled" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $8 per order" + signal: "High fulfillment cost, often due to manual processes, low volume, or multi-item order complexity. Eroding contribution margin." + below_average: + value: "$6-$8 per order" + signal: "Above average cost. Common for brands doing in-house fulfillment at moderate volumes." + average: + value: "$4-$6 per order" + signal: "Standard fulfillment cost for mid-volume operations using 3PL partners or semi-automated in-house fulfillment." + good: + value: "$2-$4 per order" + signal: "Efficient fulfillment, typically achieved at scale with optimized warehouse operations or volume-discounted 3PL rates." + excellent: + value: "< $2 per order" + signal: "Best-in-class fulfillment efficiency. Achieved by high-volume operations with automation, standardized packaging, and optimized pick paths." + stage_notes: + seed: "Fulfillment costs above $10 are common when founders are packing orders themselves. This is acceptable early but must be addressed before scaling." + series_a: "Transition from founder-packed to professional fulfillment (3PL or dedicated warehouse team). Target $4-$6 per order." + series_b_plus: "Fulfillment cost optimization through automation, multi-node distribution (reducing shipping zones), and packaging standardization." + data_sources: + - source: "ShipBob Fulfillment Benchmarks" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["shipping-cost-pct", "contribution-margin"] + related_skills: ["kaizen-bpr", "systems-thinking", "balanced-scorecard"] + caveats: "Fulfillment cost per order drops with volume but increases with SKU complexity and multi-item orders. Brands with 1-2 SKU counts have inherently lower costs than brands with 500+ SKUs." + + - name: "Shipping Cost as Percentage of Revenue" + id: "shipping-cost-pct" + category: "efficiency" + definition: "The total shipping carrier cost (outbound and return) as a percentage of net revenue. Measures the logistics cost burden on the business." + formula: "(Total Outbound Shipping Cost + Return Shipping Cost) / Net Revenue x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 15% of revenue" + signal: "Shipping costs are consuming a dangerous share of revenue. Common for heavy/bulky products, low-AOV businesses, or brands offering free shipping without sufficient margin." + below_average: + value: "12-15% of revenue" + signal: "Above average shipping burden. Review carrier rates, packaging dimensions, and shipping zone distribution." + average: + value: "8-12% of revenue" + signal: "Standard shipping cost for e-commerce businesses with free-shipping thresholds and standard-weight products." + good: + value: "5-8% of revenue" + signal: "Efficient shipping operations. Benefits from high AOV, light products, or multi-node fulfillment reducing zone distances." + excellent: + value: "< 5% of revenue" + signal: "Exceptional shipping efficiency. Typically achieved by high-AOV brands or businesses with regional fulfillment networks." + stage_notes: + seed: "Shipping cost as a percentage of revenue is disproportionately high at low volumes because carrier discounts are volume-dependent." + series_a: "Negotiate carrier rates aggressively. A 10-15% carrier rate reduction has direct bottom-line impact at scale." + series_b_plus: "Multi-node fulfillment (2-3 distribution centers) reduces average shipping zones and transit times simultaneously." + data_sources: + - source: "ShipBob Fulfillment Benchmarks" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["fulfillment-cost-per-order", "contribution-margin", "aov"] + related_skills: ["kaizen-bpr", "systems-thinking", "scenario-planning"] + caveats: "Free shipping is a marketing decision, not a logistics decision. The cost of free shipping should be analyzed as a marketing expense or factored into product pricing. 'Free shipping' does not make shipping costs disappear." + + - name: "Inventory Turnover" + id: "inventory-turnover" + category: "efficiency" + definition: "The number of times the entire inventory is sold and replaced within a year. Measures how efficiently capital invested in inventory generates revenue." + formula: "Cost of Goods Sold / Average Inventory Value" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2x annual turnover" + signal: "Capital is trapped in slow-moving inventory. High risk of obsolescence, markdowns, and write-offs. Cash flow is constrained." + below_average: + value: "2-4x annual turnover" + signal: "Below average for most e-commerce categories. Inventory is turning but not efficiently." + average: + value: "4-6x annual turnover" + signal: "Standard inventory turnover for general merchandise e-commerce. Inventory is productive." + good: + value: "6-10x annual turnover" + signal: "Healthy turnover indicating strong demand forecasting, lean inventory management, and a well-curated assortment." + excellent: + value: "> 10x annual turnover" + signal: "Exceptional turnover. Typical of consumable brands, fast-fashion models, or dropshipping operations with near-zero inventory." + stage_notes: + seed: "Inventory turnover is often low initially due to minimum order quantities and the need to hold sufficient safety stock while demand patterns emerge." + series_a: "Inventory turnover above 4x demonstrates that the product assortment matches demand. Below 4x raises concerns about product-market fit and cash efficiency." + series_b_plus: "Inventory planning systems, demand forecasting, and SKU rationalization drive turnover optimization at scale." + data_sources: + - source: "NRF Annual Report" + year: "2024" + - source: "Shopify Commerce Benchmarks" + year: "2024" + related_metrics: ["days-of-inventory", "gross-margin", "contribution-margin"] + related_skills: ["balanced-scorecard", "systems-thinking", "scenario-planning"] + caveats: "Inventory turnover varies dramatically by category: fashion 4-8x, electronics 8-12x, luxury goods 2-4x, grocery 12-20x. Cross-category comparison is meaningless." + + - name: "Days of Inventory" + id: "days-of-inventory" + category: "efficiency" + definition: "The average number of days of sales that current inventory will cover, measuring how long capital is tied up in unsold products." + formula: "(Average Inventory Value / COGS) x 365 (or 365 / Inventory Turnover)" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 180 days of inventory" + signal: "Six months of inventory on hand. Severe cash flow burden, high obsolescence risk, and storage costs eroding margins." + below_average: + value: "120-180 days" + signal: "Excessive inventory. Capital is being inefficiently deployed. Common when brands over-order to meet minimum quantities." + average: + value: "60-90 days" + signal: "Standard inventory position for e-commerce. Balances stock availability with capital efficiency." + good: + value: "30-60 days" + signal: "Lean inventory management with reliable supply chains. Low stockout risk with efficient capital deployment." + excellent: + value: "< 30 days" + signal: "Best-in-class inventory leanness. Requires responsive supply chains, accurate demand forecasting, or a dropshipping/made-to-order model." + stage_notes: + seed: "Days of inventory above 120 is common when testing product-market fit with initial production runs." + series_a: "Target 60-90 days unless the supply chain (international manufacturing, long lead times) structurally requires more." + series_b_plus: "SKU-level inventory days analysis drives assortment decisions. Slow-moving SKUs (>120 days) should be evaluated for discontinuation or clearance." + data_sources: + - source: "NRF Annual Report" + year: "2024" + - source: "Statista Digital Commerce Compass" + year: "2024" + related_metrics: ["inventory-turnover", "gross-margin"] + related_skills: ["scenario-planning", "systems-thinking", "balanced-scorecard"] + caveats: "Days of inventory must account for seasonality. A seasonal business may legitimately hold 120+ days of inventory pre-peak while operating at 30 days post-peak. Evaluate on a rolling 12-month basis." + + # ───────────────────────────────────────────── + # CUSTOMER SATISFACTION METRICS + # ───────────────────────────────────────────── + + - name: "Net Promoter Score (NPS)" + id: "nps" + category: "product" + definition: "The percentage of customers who are Promoters (9-10 rating) minus the percentage who are Detractors (0-6 rating). Measures overall brand advocacy and predicts word-of-mouth growth." + formula: "% Promoters - % Detractors" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "NPS < 10" + signal: "More detractors than neutral customers. Product quality, customer service, or fulfillment experience is materially failing expectations." + below_average: + value: "NPS 10-30" + signal: "Below the e-commerce median. Specific experience gaps (shipping speed, product quality, support responsiveness) need identification and resolution." + average: + value: "NPS 30-50" + signal: "Healthy for e-commerce. Customers are generally satisfied. Opportunity to convert passives to promoters through post-purchase experience optimization." + good: + value: "NPS 50-70" + signal: "Strong brand advocacy. Promoters are generating meaningful word-of-mouth referrals. Organic acquisition should be visible in channel mix." + excellent: + value: "NPS > 70" + signal: "Exceptional brand loyalty. Rare in e-commerce and indicates cult-brand status. These customers are your unpaid marketing force." + stage_notes: + seed: "NPS collection should begin with the first customers. Early NPS is the fastest qualitative feedback loop." + series_a: "NPS above 40 combined with a 30%+ repeat purchase rate is strong evidence of product-market fit." + series_b_plus: "NPS should be segmented by product category, order size, fulfillment speed, and customer cohort. Aggregate NPS masks important variation." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "Metrilo E-Commerce Retention Studies" + year: "2023" + related_metrics: ["csat", "repeat-purchase-rate", "organic-traffic-pct"] + related_skills: ["net-promoter-score", "four-ps-marketing", "cialdini-influence"] + caveats: "E-commerce NPS is influenced by factors beyond the product: shipping speed, packaging quality, unboxing experience, and returns process. A great product with poor fulfillment will produce a mediocre NPS." + + - name: "Customer Satisfaction Score (CSAT)" + id: "csat" + category: "product" + definition: "The percentage of customers rating their experience as 'satisfied' or 'very satisfied' on a post-interaction survey. More granular than NPS, typically measured at specific touchpoints: post-purchase, post-delivery, post-support." + formula: "(Number of Satisfied Responses / Total Survey Responses) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "CSAT < 70%" + signal: "Significant customer dissatisfaction. The specific touchpoint where CSAT is measured is materially failing." + below_average: + value: "70-78%" + signal: "Below average satisfaction. Common gaps: shipping delays, product quality inconsistency, slow support response." + average: + value: "78-85%" + signal: "Standard customer satisfaction for e-commerce. Basic expectations are met but delight is absent." + good: + value: "85-92%" + signal: "Strong satisfaction. Customers are having consistently positive experiences across touchpoints." + excellent: + value: "CSAT > 92%" + signal: "Exceptional satisfaction. Nearly every customer interaction meets or exceeds expectations." + stage_notes: + seed: "CSAT surveys at post-delivery and post-support touchpoints provide the most actionable early-stage feedback." + series_a: "CSAT above 80% across all touchpoints is expected. Below-80% touchpoints indicate specific operational weaknesses." + series_b_plus: "CSAT automation through triggered surveys at each lifecycle touchpoint provides continuous operational monitoring." + data_sources: + - source: "Shopify Commerce Benchmarks" + year: "2024" + - source: "NRF Annual Report" + year: "2024" + related_metrics: ["nps", "return-rate", "repeat-purchase-rate"] + related_skills: ["net-promoter-score", "kaizen-bpr", "systems-thinking"] + caveats: "CSAT is a lagging indicator that reflects past experience. Response rates below 10% introduce selection bias — satisfied and extremely dissatisfied customers respond disproportionately, missing the passive middle." diff --git a/plugins/foreman/content/industry-packs/e-commerce/e-commerce-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-diagnostic-rules.yaml new file mode 100644 index 0000000..ad4df17 --- /dev/null +++ b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-diagnostic-rules.yaml @@ -0,0 +1,623 @@ +# E-Commerce Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in an e-commerce context. +# The diagnostic agent loads these rules when the e-commerce industry pack +# is active. +# +# E-commerce diagnostic reframing reflects the physical product reality: +# revenue is a function of traffic x conversion x AOV x repeat rate. +# Growth stalls may be channel saturation, seasonal dependency, or inventory- +# driven. Churn means customers who never buy again — not subscription +# cancellation. Margins are compressed by COGS, fulfillment, shipping, and +# returns. Every diagnosis must address these physical product dynamics. +# +# Adaptation types: +# as-is — The diagnostic works without modification for e-commerce. +# enhanced — The diagnostic is relevant but benefits from additional +# e-commerce-specific triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for +# e-commerce. + +pack_metadata: + sector: "e-commerce" + display_name: "E-Commerce" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "E-commerce revenue is the product of four levers — traffic, conversion rate, AOV, and repeat purchase rate. Each lever has distinct root causes and interventions. The base diagnostic treats revenue as a single pipeline; e-commerce must decompose first. Additionally, returns reverse revenue and must be factored into any diagnosis." + additional_triage_questions: + - question: "Decompose the revenue decline: is it driven by declining traffic, declining conversion rate, declining AOV, or declining repeat purchase rate?" + purpose: "Identifies which of the four revenue levers is failing. Each lever has entirely different root causes and solutions." + routing_impact: "Traffic decline routes to channel diagnosis (ad fatigue, SEO erosion, algorithm change). Conversion decline routes to site experience and pricing diagnosis. AOV decline routes to assortment and pricing diagnosis. Repeat rate decline routes to product quality and retention diagnosis." + - question: "Has the revenue decline occurred across all channels or only specific ones (DTC site, Amazon, wholesale, retail)?" + purpose: "Channel-specific decline indicates a channel problem. Cross-channel decline indicates a product, brand, or market problem." + routing_impact: "Single-channel decline routes to channel-specific diagnosis. Cross-channel decline routes to product-market-fit-diagnosis or competitive-threat-diagnosis." + - question: "What is the return rate trend? Is net revenue (after returns) declining faster than gross revenue?" + purpose: "Rising returns reverse revenue and signal product quality, sizing, or expectation issues. Net revenue declining faster than gross revenue means the problem is partly returns-driven." + routing_impact: "Rising return rate routes to product quality audit and customer expectation analysis. Stable return rate indicates the problem is demand-side, not product-side." + - question: "Is the decline seasonal or structural? How does this period compare to the same period last year?" + purpose: "Seasonal decline is expected and manageable. Structural decline (worse than same period YoY) indicates a fundamental problem." + routing_impact: "Seasonal decline routes to seasonal planning and cash management. Structural decline routes to deeper diagnosis of the four revenue levers." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Paid channel fatigue" + reason: "E-commerce brands heavily dependent on Meta or Google Ads frequently experience revenue declines when ad creative fatigues, audiences saturate, or platform costs increase." + - diagnosis: "Return rate crisis destroying net revenue" + reason: "Gross revenue may be stable while net revenue declines because return rates are increasing — a uniquely physical-product failure mode." + less_likely: + - diagnosis: "Market demand decline" + reason: "True market demand decline is rare in e-commerce except in fad categories. Revenue decline is almost always a company-specific problem: channel, conversion, or product." + ecommerce_specific_diagnoses: + - name: "Channel dependency revenue collapse" + description: "Revenue declining because the dominant acquisition channel is degrading — ad costs rising, platform algorithm changed, or channel-specific conversion declining. The business lacks diversification to absorb the shock." + symptoms: + - "70%+ of revenue from a single paid channel (typically Meta or Google)" + - "ROAS declining for 3+ consecutive months on the primary channel" + - "No meaningful organic traffic or email revenue to offset paid channel decline" + - "Revenue tracks paid spend linearly — stop spending, stop revenue" + routes_to_skills: ["four-ps-marketing", "scenario-planning", "blue-ocean-strategy"] + routes_to_templates: ["strategic-analysis-one-pager", "action-plan"] + - name: "Margin compression disguised as revenue problem" + description: "Revenue may be stable or growing but the business feels revenue-constrained because rising COGS, fulfillment, shipping, and return costs have compressed contribution margin. Less cash is available to reinvest in growth." + symptoms: + - "Revenue stable but cash position declining" + - "Contribution margin declining QoQ" + - "COGS increasing due to supplier price increases, tariffs, or raw material costs" + - "Free shipping threshold not covering true shipping costs" + routes_to_skills: ["business-model-canvas", "balanced-scorecard", "kaizen-bpr"] + routes_to_templates: ["unit-economics-snapshot", "quarterly-strategic-review"] + sector_red_flags: + - "Net revenue declining while gross revenue grows — return rate is destroying economics." + - "Revenue from repeat customers declining as a percentage of total — the brand is running on a treadmill of ever-more-expensive new customer acquisition." + - "Revenue concentrated in a single product (hero SKU dependency) — a supply disruption or competitive entry on that product threatens the entire business." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "E-commerce growth stalls have characteristic patterns distinct from SaaS or marketplace businesses. Physical product growth is constrained by inventory capital, channel economics, product assortment exhaustion, and seasonal dependency. The stall may be demand-side (cannot acquire more customers efficiently) or supply-side (cannot produce, stock, or fulfill more orders)." + additional_triage_questions: + - question: "Is the growth stall occurring in new customer acquisition, repeat purchase rate, or both?" + purpose: "New customer stall indicates channel saturation or competitive displacement. Repeat stall indicates product or experience failure. Both stalling simultaneously is a more serious signal." + routing_impact: "New customer stall routes to channel analysis and competitive diagnosis. Repeat stall routes to product quality, post-purchase experience, and retention diagnosis." + - question: "Has the product assortment changed recently? Are you introducing new products at a rate that sustains discovery and repeat visits?" + purpose: "E-commerce brands that stop introducing new products often experience growth stalls because existing customers have purchased everything they want and new customers see a static offering." + routing_impact: "Stagnant assortment routes to product-life-cycle analysis and product development strategy. Active assortment with slowing growth routes to marketing and distribution diagnosis." + - question: "What percentage of annual revenue concentrates in Q4 (holiday season)?" + purpose: "Brands with 40%+ Q4 concentration may experience apparent growth stalls in Q1-Q3 that are structural rather than problematic. Alternatively, failure to grow outside of peak season is a genuine strategic weakness." + routing_impact: "High seasonal concentration routes to seasonality reduction strategy and year-round demand generation. Low concentration rules out seasonality as a factor." + - question: "Are you experiencing stockouts on your best-selling products?" + purpose: "Growth stalls can be supply-constrained — the brand cannot sell what it cannot stock. Stockouts on hero products cap revenue directly." + routing_impact: "Frequent stockouts route to inventory planning and supply chain diagnosis. No stockout issues route to demand-side diagnosis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Channel saturation" + reason: "E-commerce brands typically master 1-2 acquisition channels and plateau when those channels saturate. Adding new channels is operationally complex and requires different skills." + - diagnosis: "Product assortment ceiling" + reason: "A brand with 20 SKUs that has captured its addressable market faces a growth ceiling that only new products or new markets can break." + - diagnosis: "Seasonal over-reliance" + reason: "Brands with 40%+ Q4 revenue concentration appear to stall in other quarters because the business model depends on holiday demand." + less_likely: + - diagnosis: "Total market saturation" + reason: "True market saturation in e-commerce is rare — most categories have billions in addressable demand. Apparent saturation usually means the brand has saturated its current channels or segments, not the market." + ecommerce_specific_diagnoses: + - name: "Inventory death spiral" + description: "Growth has stalled because capital is trapped in slow-moving inventory, leaving insufficient funds for marketing and new product development. The brand orders inventory, it sells slowly, cash is tied up, marketing is cut, sales decline further, more inventory becomes slow-moving — a self-reinforcing downward spiral." + symptoms: + - "Days of inventory rising above 120 for multiple SKUs" + - "Marketing budget declining because cash is locked in inventory" + - "Increasing markdown frequency to move slow inventory" + - "New product launches delayed due to insufficient capital" + routes_to_skills: ["systems-thinking", "scenario-planning", "balanced-scorecard"] + routes_to_templates: ["action-plan", "unit-economics-snapshot"] + - name: "The Amazon trap" + description: "Growth stalled on the brand's own channels because Amazon captures an increasing share of the brand's demand. Customers who would have purchased on the DTC site instead purchase on Amazon (where the brand earns lower margin and owns no customer data). Amazon's share grows while the brand's DTC share shrinks, and total growth stalls because Amazon growth cannibalizes DTC rather than expanding the addressable market." + symptoms: + - "DTC revenue flat or declining while Amazon revenue grows" + - "Branded search volume shifting from brand.com to Amazon" + - "DTC email list growth slowing (Amazon customers do not join the list)" + - "Total revenue growth below combined DTC + Amazon channel growth (cannibalization)" + routes_to_skills: ["business-model-canvas", "porters-five-forces", "game-theory-fundamentals"] + routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + sector_red_flags: + - "CAC rising for 3+ consecutive months while conversion rate holds — indicates channel saturation, not funnel problems." + - "Hero product (>40% of revenue) growth flattening — the single-product growth engine is exhausting its market." + - "New product launch frequency declining — the pipeline is drying up, which guarantees future growth stalls." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Product-market fit in e-commerce has distinct quantitative indicators that differ from SaaS: repeat purchase rate is the primary PMF signal (not retention rate), organic traffic percentage indicates unprompted demand, and return rate signals whether the product meets expectations set during the purchase journey." + additional_triage_questions: + - question: "What is the repeat purchase rate for your first 6-month cohort?" + purpose: "Repeat purchase rate is the e-commerce equivalent of SaaS retention. A cohort repeat rate above 25% at 6 months is a strong PMF signal. Below 15% suggests the product is not compelling enough to buy again." + routing_impact: "Repeat rate below 15% routes to fundamental PMF exploration — the product may need reformulation, repositioning, or discontinuation. Above 25% routes to growth and distribution strategy." + - question: "What is the return rate, and what are the top three return reasons?" + purpose: "High return rates (>20%) suggest the product does not match customer expectations — a PMF signal. Return reason analysis distinguishes between product quality issues and expectation-setting issues." + routing_impact: "High returns with 'not as expected' reason routes to product page and photography improvement. High returns with 'quality' reason routes to product quality intervention." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "PMF exists for a niche but the brand is targeting too broadly" + reason: "E-commerce brands frequently have strong PMF with a specific demographic but dilute it by targeting mass market through broad paid media." + - diagnosis: "Product expectation gap" + reason: "The product may be good but the purchase experience (photography, descriptions, reviews) creates expectations the product cannot meet — a uniquely e-commerce PMF issue." + less_likely: + - diagnosis: "Market does not exist" + reason: "If competitors sell similar products successfully, the market exists. E-commerce PMF failure is usually about the specific product, price, or brand — not the category." + ecommerce_specific_diagnoses: + - name: "Return-rate-driven PMF failure" + description: "The product sells well initially (acquisition works) but return rates above 20% indicate the product does not meet customer expectations. PMF appears strong from sales data but is undermined by the post-purchase reality." + symptoms: + - "Conversion rate above category average but return rate also above average" + - "Customer reviews cite 'not as described' or 'quality issues'" + - "First-purchase customers do not return for second purchase" + - "Gross revenue strong but net revenue (after returns) weak" + routes_to_skills: ["net-promoter-score", "defining-and-exploring-problems", "kaizen-bpr"] + routes_to_templates: ["action-plan", "new-initiative-brief"] + sector_red_flags: + - "Repeat purchase rate below 15% after 6 months — customers are not compelled to buy again." + - "Return rate above 25% — the product materially disappoints a quarter of buyers." + - "NPS below 20 — customers are not advocates and will not generate organic demand." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "E-commerce pricing is fundamentally margin-driven. Unlike SaaS (where marginal cost of serving another customer is near zero), every e-commerce sale carries COGS, fulfillment, shipping, and returns costs. Pricing below the contribution margin floor is unsustainable regardless of volume. Additionally, e-commerce prices are transparently comparable — customers can compare across retailers, Amazon, and competitors in seconds." + additional_triage_questions: + - question: "What is your contribution margin per order at current pricing (after COGS, fulfillment, shipping, payment processing, and estimated return cost)?" + purpose: "If contribution margin is negative or below 15%, the business loses money on every order before marketing. This is a pricing crisis, not a pricing question." + routing_impact: "Negative contribution margin routes to emergency pricing intervention and cost structure analysis. Positive contribution margin above 20% indicates pricing has room for optimization." + - question: "How do your prices compare to direct competitors and Amazon alternatives?" + purpose: "E-commerce pricing transparency means customers always know the alternatives. Pricing significantly above comparable alternatives requires a clear brand premium justification." + routing_impact: "Priced above alternatives with strong repeat purchase rate — premium is justified. Priced above with low repeat — premium is not supported by perceived value." + - question: "What percentage of revenue comes from discounted purchases (sales, promotions, coupon codes)?" + purpose: "Discount dependency erodes brand value and trains customers to wait for sales. Above 30% of revenue at discount indicates a structural pricing and promotional problem." + routing_impact: "High discount dependency routes to promotional strategy redesign and brand value analysis. Low discount dependency indicates pricing is likely appropriate." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Under-pricing relative to brand value" + reason: "DTC brands frequently under-price because founders benchmark against mass-market alternatives rather than calculating what premium their brand, story, and experience justify." + - diagnosis: "Discount addiction" + reason: "Once customers learn a brand runs frequent sales, full-price purchasing declines. The brand enters a cycle of discounting to maintain volume, which compresses margins permanently." + less_likely: + - diagnosis: "Over-pricing" + reason: "Genuine over-pricing in e-commerce results in zero sales, not slow sales. If the product sells at all, the price is within the acceptable range. The question is usually whether the price should be higher, not lower." + ecommerce_specific_diagnoses: + - name: "Free shipping margin trap" + description: "The brand offers free shipping at a threshold that does not cover actual shipping costs, or offers universal free shipping without building the cost into product pricing. Shipping costs consume margin on every order while customers perceive shipping as 'free.'" + symptoms: + - "Contribution margin significantly lower than gross margin due to shipping cost absorption" + - "AOV clusters just above the free shipping threshold (customers add low-margin items to qualify)" + - "Shipping cost as percentage of revenue exceeds 12%" + - "Competitor analysis reveals competitors build shipping cost into product price rather than offering 'free' shipping" + routes_to_skills: ["four-ps-marketing", "business-model-canvas", "systems-thinking"] + routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + sector_red_flags: + - "Contribution margin below 15% — pricing does not sustain the business at any volume." + - "More than 40% of revenue sold at discount — the brand is training customers to never pay full price." + - "Price positioned below competitors despite superior product quality — value is being left on the table." + + # ───────────────────────────────────────────── + # 5. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Churn in e-commerce is fundamentally different from SaaS churn. E-commerce customers do not cancel a subscription — they simply stop buying. There is no explicit churn event, only the absence of repurchase. Diagnosing churn requires cohort analysis of repeat purchase behavior, not cancellation reason analysis. The question is not 'why did they leave?' but 'why did they not come back?'" + additional_triage_questions: + - question: "At what point in the customer lifecycle does the majority of 'churn' (non-repurchase) occur — after the first purchase, after the second, or distributed throughout?" + purpose: "First-to-second purchase is the critical transition. If 80% of customers never buy again, the product or post-purchase experience is failing. If customers churn after 3-4 purchases, product fatigue or competitive displacement is more likely." + routing_impact: "First-to-second purchase failure routes to post-purchase experience, email/SMS flows, and product quality analysis. Later-lifecycle churn routes to assortment expansion and loyalty program design." + - question: "Is the non-repeat behavior consistent across product categories, or do specific categories retain better?" + purpose: "Category-level retention analysis reveals whether churn is a brand-wide problem or a product-specific one." + routing_impact: "Universal low repeat rate routes to brand and experience diagnosis. Category-specific retention routes to product quality and assortment analysis within the weak category." + - question: "Do customers who interact with post-purchase touchpoints (email, SMS, loyalty program) repeat at higher rates than those who do not?" + purpose: "If engaged customers repeat at 2-3x the rate of unengaged customers, the churn problem is a communication problem — not a product problem." + routing_impact: "High engaged/unengaged gap routes to email and SMS program optimization. Low gap indicates the problem is product or brand, not communication." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Post-purchase experience failure" + reason: "The product may be excellent but the post-purchase experience — slow shipping, poor packaging, no follow-up communication, difficult returns — kills the relationship before a second purchase." + - diagnosis: "Product consumption cycle mismatch" + reason: "If the product lasts 6 months but the brand sends a repurchase reminder at 30 days, timing is misaligned. Understanding the natural consumption or usage cycle is critical." + less_likely: + - diagnosis: "Price sensitivity causing churn" + reason: "If the customer purchased once at the current price, price is not the barrier to repurchase. The product met the price-value test at acquisition." + ecommerce_specific_diagnoses: + - name: "One-and-done product problem" + description: "The product is good enough to purchase once but does not create ongoing need. The category is inherently low-frequency (furniture, mattresses) or the product fully solves the customer's problem in one purchase. This is not a failure — it requires a different business model (broader assortment, adjacent products, referral programs)." + symptoms: + - "Repeat purchase rate below 15% regardless of post-purchase marketing effort" + - "NPS is strong (40+) but customers do not return" + - "Customer feedback positive: 'love the product, don't need another one'" + - "Category benchmarks confirm low repeat rates across all competitors" + routes_to_skills: ["product-life-cycle", "business-model-canvas", "doblin-ten-types"] + routes_to_templates: ["strategic-analysis-one-pager", "new-initiative-brief"] + - name: "Return experience driving permanent churn" + description: "Customers who go through the returns process are permanently lost — not because of the product issue that caused the return, but because the return process itself was so frustrating that the customer will never buy again." + symptoms: + - "Customers who have processed a return have a near-zero repeat purchase rate" + - "Post-return NPS dramatically lower than post-delivery NPS" + - "Customer service complaints concentrated around return process (slow refunds, confusing instructions, return shipping cost)" + - "Competitors offering significantly easier return experiences" + routes_to_skills: ["kaizen-bpr", "net-promoter-score", "systems-thinking"] + routes_to_templates: ["action-plan", "incident-postmortem"] + sector_red_flags: + - "First-to-second purchase rate below 20% — the majority of customers are one-and-done." + - "Repeat purchase rate declining across successive cohorts — the problem is getting worse, not better." + - "Post-return customers never repurchasing — the return experience is a permanent relationship-ender." + + # ───────────────────────────────────────────── + # 6. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce competitive threats come from three distinct vectors: direct competitors (similar products, similar channels), channel competitors (Amazon Basics, retailer private labels), and category disruptors (new brands with different business models — subscription replacing one-time purchase, DTC replacing retail). Each vector requires different defensive responses." + additional_triage_questions: + - question: "Is the competitive threat from a direct product competitor, from Amazon/private label, or from a different business model in the same category?" + purpose: "Direct competition is fought with brand, experience, and product differentiation. Amazon/private label competition is fought with brand loyalty and DTC channel strength. Business model disruption (e.g., subscription entrant in a one-time purchase category) requires strategic repositioning." + routing_impact: "Direct competition routes to blue-ocean-strategy and competitive differentiation. Amazon competition routes to DTC channel investment and brand building. Business model disruption routes to business-model-canvas and disruptive-innovation analysis." + - question: "Has the competitor's entry affected your conversion rate, your repeat purchase rate, or both?" + purpose: "Conversion rate impact means the competitor is winning at the point of purchase (better pricing, reviews, or positioning). Repeat rate impact means customers are switching after trying both — a more serious signal." + routing_impact: "Conversion impact routes to pricing and positioning analysis. Repeat impact routes to product quality and experience comparison." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Amazon private label entry" + reason: "Amazon launches private label products in categories where it has demand data showing high volume and margin. If a brand sells well on Amazon, Amazon private label entry is a near-certainty." + - diagnosis: "Category commoditization" + reason: "E-commerce categories naturally commoditize as more brands enter with similar products at similar prices. The differentiating factor shifts from product to brand, experience, and customer relationship." + less_likely: + - diagnosis: "Technology disruption" + reason: "Physical product categories are rarely disrupted by technology alone. The disruption in e-commerce is usually distribution (DTC vs. retail), business model (subscription vs. one-time), or brand positioning — not product technology." + ecommerce_specific_diagnoses: + - name: "Amazon Basics commoditization" + description: "Amazon has launched a private label product in the brand's core category, priced 30-50% lower, positioned directly in search results, and leveraging Amazon's review and fulfillment infrastructure. The brand's Amazon sales are declining while DTC is unaffected — but the category pricing anchor has shifted downward." + symptoms: + - "Amazon sales declining while DTC sales remain stable" + - "Amazon search rank declining for core category keywords" + - "Competitor Amazon listings appearing with 'Amazon's Choice' or 'Best Seller' badges" + - "Category average price declining on Amazon" + routes_to_skills: ["porters-five-forces", "blue-ocean-strategy", "disruptive-innovation"] + routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Branded search volume declining — customers are searching for the category rather than the brand, indicating weakening brand moat." + - "Review velocity of competitor exceeding yours on Amazon — review accumulation is a compounding competitive advantage." + - "Customer acquisition cost rising without market-level CPM increases — competitor ad bidding is driving up costs." + + # ───────────────────────────────────────────── + # 7. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce fundraising has distinct investor expectations that differ from SaaS. Investors scrutinize gross margin (must be >50% for DTC), contribution margin (must be positive), repeat purchase rates (must prove the product earns loyalty), and inventory efficiency (capital tied up in unsold goods is a red flag). The GMV vs. revenue distinction is critical — investors want net revenue and contribution margin, not vanity GMV." + additional_triage_questions: + - question: "What are your gross margin, contribution margin (per order), and repeat purchase rate?" + purpose: "These three metrics are the primary inputs to e-commerce fundraising readiness. Gross margin below 50%, negative contribution margin, or repeat rate below 20% are near-disqualifying for institutional investment." + routing_impact: "Metrics below thresholds route to business model improvement before fundraising. Metrics above thresholds route to fundraising execution." + - question: "How much capital is currently tied up in inventory, and what is your inventory turnover rate?" + purpose: "E-commerce investors evaluate capital efficiency through inventory. High inventory relative to revenue signals demand forecasting problems or product-market fit issues." + routing_impact: "High inventory (>120 days) routes to inventory optimization before fundraising. Lean inventory (<60 days) is a positive signal for investors." + - question: "Can you present cohort-level repeat purchase data and LTV curves by acquisition channel?" + purpose: "Sophisticated e-commerce investors want cohort analysis, not aggregate metrics. The ability to present cohort data demonstrates operational maturity." + routing_impact: "No cohort data routes to analytics infrastructure before fundraising. Cohort data available routes to fundraising-deck-outline." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Unit economics not yet proven" + reason: "Many e-commerce brands raise while contribution margin is negative, hoping scale will fix economics. Investors increasingly require proven per-order profitability before investing." + - diagnosis: "Inventory risk concerns" + reason: "Investors are wary of businesses that require large inventory commitments. High inventory risk is a primary reason VCs historically under-invested in e-commerce relative to SaaS." + less_likely: + - diagnosis: "Market too small" + reason: "E-commerce categories are generally large. The issue is rarely market size but rather the brand's ability to capture share profitably." + ecommerce_specific_diagnoses: + - name: "GMV-revenue confusion undermining investor confidence" + description: "The founder presents GMV as the headline metric, obscuring the fact that net revenue (after returns, discounts, and marketplace fees) is significantly lower. Investors see through this immediately and question the founder's financial literacy." + symptoms: + - "Pitch materials lead with GMV without prominently showing net revenue" + - "Investor meetings stall when asked about net revenue and contribution margin" + - "Fundraising deck does not include a per-order unit economics waterfall" + - "Return rate and discount rate not disclosed upfront" + routes_to_skills: ["balanced-scorecard", "business-model-canvas"] + routes_to_templates: ["unit-economics-snapshot", "fundraising-deck-outline"] + sector_red_flags: + - "Raising with negative contribution margin and no clear path to positive per-order economics." + - "Inventory exceeding 6 months of sales — signals demand forecasting failure or product-market fit issues." + - "LTV:CAC below 2:1 — the business does not yet generate enough lifetime value to justify acquisition costs." + + # ───────────────────────────────────────────── + # 8. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Operational chaos in e-commerce has uniquely tangible manifestations: wrong items shipped, fulfillment delays, stockouts on key products, returns processing backlogs, customer service overwhelm, and inventory data discrepancies. Unlike knowledge-work operational issues, e-commerce operational failures are immediately visible to customers and directly measurable in returns, reviews, and repeat purchase rates." + additional_triage_questions: + - question: "What is your order accuracy rate (percentage of orders shipped correctly with the right items, right quantities, right addresses)?" + purpose: "Order accuracy below 98% indicates systemic fulfillment process failure. Each error generates a return, a replacement shipment, and a dissatisfied customer." + routing_impact: "Below 98% accuracy routes to fulfillment process audit and Kaizen-BPR intervention. Above 98% indicates the chaos is elsewhere." + - question: "How often do you experience stockouts on your top 20% of SKUs?" + purpose: "Stockouts on best-sellers directly limit revenue and damage customer trust. Frequency of stockouts indicates demand forecasting and inventory planning maturity." + routing_impact: "Frequent stockouts routes to demand forecasting, safety stock optimization, and supplier lead time analysis." + - question: "Is inventory data accurate? Does the system count match physical count within 2%?" + purpose: "Inventory data discrepancies cascade through the entire operation: overselling, stockouts despite 'available' inventory, and fulfillment errors." + routing_impact: "Inaccurate inventory data routes to inventory management system audit and cycle counting implementation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Growth outpacing operational capacity" + reason: "E-commerce operational chaos most commonly occurs when order volume exceeds the capacity of manual or semi-manual processes. The systems that worked at 50 orders/day collapse at 300." + - diagnosis: "3PL transition failure" + reason: "Moving from self-fulfillment to a 3PL (or changing 3PLs) is a high-risk operational transition. Poorly managed transitions produce weeks of shipping errors and delays." + less_likely: + - diagnosis: "Strategic confusion causing chaos" + reason: "E-commerce operational chaos is usually a systems and process problem, not a strategy problem. The founder knows what to do — the operation cannot execute fast enough." + ecommerce_specific_diagnoses: + - name: "Peak season operational collapse" + description: "The operation functions adequately at normal volumes but collapses during peak periods (Black Friday, holiday season, viral demand spikes). Shipping delays extend to 7+ days, fulfillment errors spike, customer service queues grow to 48+ hour response times, and the brand's reputation takes lasting damage during its highest-visibility period." + symptoms: + - "Fulfillment SLA breaches concentrated in Q4 or during promotional events" + - "Customer service ticket volume exceeding team capacity by 3x+ during peaks" + - "Negative reviews spiking during peak periods citing shipping delays" + - "Return rate increasing during peaks due to fulfillment errors" + routes_to_skills: ["scenario-planning", "kaizen-bpr", "systems-thinking"] + routes_to_templates: ["action-plan", "incident-postmortem"] + sector_red_flags: + - "Order accuracy below 95% — one in twenty customers receives the wrong order." + - "Average fulfillment time exceeding 3 business days — customers expect 1-2 day processing." + - "Inventory accuracy below 90% — the business does not know what it actually has in stock." + + # ───────────────────────────────────────────── + # 9. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce market entry involves decisions unique to physical product businesses: geographic market entry (requiring local fulfillment, regulatory compliance, and localized marketing), channel market entry (launching on Amazon, entering wholesale, or opening retail), and category expansion (adding adjacent product categories). Each entry type has different capital requirements, operational complexity, and risk profiles." + additional_triage_questions: + - question: "Is the market entry geographic (new country/region), channel-based (new sales channel), or category-based (new product category)?" + purpose: "Each entry type has entirely different requirements and risk profiles. Geographic requires logistics and compliance. Channel requires operational adaptation. Category requires product development and brand extension." + routing_impact: "Geographic routes to international expansion analysis. Channel routes to channel economics analysis. Category routes to brand extension and product-market fit assessment." + - question: "For geographic expansion: can the existing supply chain serve the new market, or does it require new fulfillment infrastructure?" + purpose: "International e-commerce requires local fulfillment to meet delivery expectations. Cross-border shipping is expensive and slow." + routing_impact: "Existing infrastructure can serve routes to marketing-first entry strategy. New infrastructure required routes to capital planning and phased entry." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Channel expansion mistaken for market entry" + reason: "Adding Amazon or wholesale is often treated as market entry when it is actually channel expansion within the same market. The strategic implications are different." + less_likely: + - diagnosis: "First mover advantage urgency" + reason: "First mover advantage in e-commerce is weak. Entering a market 6 months later with better preparation typically outperforms rushing in first." + sector_red_flags: + - "Entering Amazon without dedicated Amazon operations expertise — the channel has unique requirements." + - "International expansion without local fulfillment — cross-border shipping will not meet customer expectations." + - "Category expansion without product-market fit validation — assuming brand equity transfers automatically to new categories." + + # ───────────────────────────────────────────── + # 10. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce leadership crises often originate from the founder's inability to transition from operator (doing everything) to leader (building systems and teams). The operational intensity of physical product businesses means founders become indispensable to daily operations, and the leadership crisis manifests as burnout, bottleneck creation, and inability to scale." + additional_triage_questions: + - question: "If the founder were unavailable for two weeks, which operational functions would stop?" + purpose: "Identifies single-point-of-failure dependencies. In e-commerce, common dependencies: only the founder approves inventory orders, manages the primary ad account, or handles key supplier relationships." + routing_impact: "Multiple critical functions dependent on founder routes to delegation-and-empowerment and systems design. Minimal founder dependency indicates the crisis is strategic, not operational." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Founder bottleneck from operator-to-leader transition" + reason: "The most common e-commerce leadership crisis. The founder who packed the first 10,000 orders cannot let go of operational control at 100,000 orders." + less_likely: + - diagnosis: "Strategic vision crisis" + reason: "Most e-commerce founders know what they want to build. The crisis is usually about execution capacity, not direction." + sector_red_flags: + - "Founder personally managing fulfillment or customer service above 200 orders/day." + - "Key supplier relationships managed only by the founder with no documentation." + - "Founder working 70+ hour weeks with no path to reducing operational involvement." + + # ───────────────────────────────────────────── + # 11. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce team dysfunction frequently manifests as creative-operational tension: the brand/marketing team makes decisions (packaging changes, promotional launches, new product introductions) without coordinating with operations, or operations constrains marketing ambitions without understanding commercial impact." + additional_triage_questions: + - question: "Do the marketing and operations teams share common metrics, or do they optimize independently?" + purpose: "When marketing optimizes for revenue and operations optimizes for cost, they inevitably conflict. Shared metrics (contribution margin per order) align incentives." + routing_impact: "Misaligned metrics routes to balanced-scorecard implementation with shared KPIs." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Cross-functional misalignment between brand/marketing and operations" + reason: "The most characteristic e-commerce team dysfunction. Creative and operational functions have different cultures, priorities, and success metrics." + less_likely: + - diagnosis: "Interpersonal conflict" + reason: "What appears as interpersonal conflict in e-commerce teams is usually structural: misaligned incentives, unclear decision rights, or lack of shared planning processes." + sector_red_flags: + - "Marketing launches promotions without informing fulfillment — leading to capacity crises." + - "Operations vetoes marketing initiatives without quantifying the commercial impact of delay." + + # ───────────────────────────────────────────── + # 12. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Cofounder conflict dynamics are largely sector-agnostic. The base diagnostic applies without significant e-commerce adaptation." + + # ───────────────────────────────────────────── + # 13. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce hiring requires specific roles that differ from SaaS or service businesses: supply chain manager, inventory planner, fulfillment operations lead, marketplace specialist (Amazon), and performance marketing manager with e-commerce experience. The sequencing of hires matters — operational roles must be filled before or simultaneously with growth roles to prevent growth from outpacing operational capacity." + additional_triage_questions: + - question: "What is the current ratio of growth-focused roles (marketing, product, brand) to operations-focused roles (fulfillment, supply chain, customer service)?" + purpose: "An imbalanced team — too many growth roles without operational support — is a common e-commerce hiring pattern that leads to operational chaos during scaling." + routing_impact: "Imbalanced toward growth routes to operational hiring prioritization. Imbalanced toward operations routes to growth hiring." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Operational hiring lag" + reason: "E-commerce founders tend to hire marketing and product roles first because they are more exciting. Warehouse, supply chain, and customer service roles are hired later — often too late." + less_likely: + - diagnosis: "Over-hiring" + reason: "E-commerce businesses generally under-hire for operations rather than over-hire." + sector_red_flags: + - "No dedicated operations hire above 300 orders/day — the founder is a bottleneck." + - "Marketing team twice the size of operations team while fulfillment quality degrades." + + # ───────────────────────────────────────────── + # 14. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce partnerships are uniquely operational: manufacturing partnerships (contract manufacturers, white-label producers), distribution partnerships (3PL providers, carriers, wholesale retailers), and marketing partnerships (influencers, brand collaborations, affiliate networks). Each partnership type carries operational risk that is absent in SaaS partnerships." + additional_triage_questions: + - question: "Is the partnership under consideration an operational partnership (supplier, 3PL, carrier) or a commercial partnership (retail distribution, brand collaboration, influencer)?" + purpose: "Operational partnerships affect fulfillment quality and are difficult to change quickly. Commercial partnerships affect revenue and can be tested and adjusted more easily." + routing_impact: "Operational partnership routes to due diligence with emphasis on operational capability, redundancy, and exit provisions. Commercial partnership routes to standard commercial terms analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Over-dependence on a single operational partner" + reason: "Sole-source suppliers and single-3PL setups are common in e-commerce and create fragility that founders underestimate." + less_likely: + - diagnosis: "Partnership is premature" + reason: "E-commerce businesses need operational partners (manufacturers, fulfillment) from day one. The question is quality, not timing." + sector_red_flags: + - "Single-source supplier for the core product — any disruption halts the business entirely." + - "3PL contract with no SLA penalties — no recourse for fulfillment failures." + + # ───────────────────────────────────────────── + # 15. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Innovation drought in e-commerce manifests as product assortment stagnation. The brand stops introducing new products, product pages become stale, and the catalog feels static. Unlike SaaS (where the product evolves with deploys), e-commerce requires deliberate new product development cycles with manufacturing lead times." + additional_triage_questions: + - question: "How many new products have been launched in the last 12 months, and what percentage of revenue do they represent?" + purpose: "New product vitality index measures whether the brand is refreshing its offering. Below 10% of revenue from products launched in the last 12 months signals stagnation." + routing_impact: "Low new product vitality routes to product development pipeline and lifecycle analysis. Healthy vitality indicates innovation drought is elsewhere (experience, channel, or brand)." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Product development pipeline dried up" + reason: "E-commerce brands that scale through a hero product often neglect the product development pipeline. When the hero product matures, there is nothing to replace it." + less_likely: + - diagnosis: "Innovation culture problem" + reason: "Small e-commerce teams rarely have cultural barriers to innovation. The problem is usually resource constraints and manufacturing complexity, not cultural resistance." + sector_red_flags: + - "Zero new product launches in 12 months — the assortment is stale." + - "Hero product representing 50%+ of revenue with no successor in development." + + # ───────────────────────────────────────────── + # 16. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce strategic drift typically manifests as channel proliferation without coherent strategy — the brand sells on its own site, Amazon, Etsy, Walmart, wholesale, and social commerce, but each channel was added opportunistically. The result is operational complexity, margin erosion, and a diluted brand experience." + additional_triage_questions: + - question: "How many sales channels does the brand operate, and can you articulate the strategic purpose of each?" + purpose: "Channel proliferation without strategic rationale is the most common form of e-commerce strategic drift." + routing_impact: "Cannot articulate channel strategy routes to channel portfolio rationalization and strategic-thinking-and-alignment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Channel sprawl driving complexity without proportional value" + reason: "Each new channel adds operational complexity (different platforms, packaging requirements, customer service channels) that founders underestimate." + less_likely: + - diagnosis: "Mission drift" + reason: "E-commerce strategic drift is usually channel and product-line drift, not mission drift. The brand still knows what it stands for — it just sells through too many channels with too many products." + sector_red_flags: + - "Operating on 5+ sales channels with no channel contributing more than 30% of contribution margin — effort is spread too thin." + - "Product line expanded into unrelated categories that dilute the brand identity." + + # ───────────────────────────────────────────── + # 17. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Communication breakdown dynamics are largely sector-agnostic. The base diagnostic applies without significant e-commerce adaptation, though the most common communication failure in e-commerce — marketing and operations not coordinating on promotions and launches — is addressed in the team-dysfunction-diagnosis overlay." + + # ───────────────────────────────────────────── + # 18. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce decision paralysis has distinctive triggers: the high irreversibility of inventory commitments, the complexity of channel strategy (should we sell on Amazon?), and the tension between growth and profitability. Physical product decisions have longer time horizons than software decisions, which amplifies the cost of delay." + additional_triage_questions: + - question: "Is the paralysis centered on an inventory/product decision, a channel decision, or a financial/pricing decision?" + purpose: "Each decision type has different risk profiles and appropriate decision frameworks." + routing_impact: "Inventory decisions route to scenario-planning with downside modeling. Channel decisions route to contribution margin analysis by channel. Pricing decisions route to pricing-diagnosis." + - question: "What is the cost of delay? Is there a seasonal deadline, a supply chain commitment window, or a competitive entry that makes inaction costly?" + purpose: "In e-commerce, delay has concrete costs: missing a seasonal window, losing a manufacturing slot, or allowing a competitor to establish position." + routing_impact: "High cost of delay routes to rapid decision frameworks with explicit time boundaries. Low cost routes to more deliberate analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Analysis paralysis on irreversible inventory commitments" + reason: "The fear of committing $50K-$500K to inventory that might not sell is the single most common decision paralysis trigger in e-commerce." + less_likely: + - diagnosis: "Lack of data" + reason: "E-commerce generates abundant data. Paralysis is usually about risk tolerance, not information deficiency." + sector_red_flags: + - "Seasonal inventory commitment deadline passing without decision — the window is now closed." + - "New product launch delayed 6+ months by founder indecision while competitors enter." + + # ───────────────────────────────────────────── + # 19. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Culture erosion dynamics are largely sector-agnostic. The base diagnostic applies without significant e-commerce adaptation." + + # ───────────────────────────────────────────── + # 20. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "E-commerce negotiation stalls most commonly involve supplier/manufacturer negotiations (pricing, MOQs, payment terms), carrier/3PL negotiations (rates, SLAs, volume commitments), and retail buyer negotiations (wholesale pricing, co-op spend, placement). Each has specific power dynamics and resolution patterns." + additional_triage_questions: + - question: "Is the negotiation with a supplier, a channel/distribution partner, or a service provider (3PL, carrier, agency)?" + purpose: "Each negotiation type has different power dynamics and leverage points." + routing_impact: "Supplier negotiation routes to cooperative-negotiation (long-term relationship) and BATNA development. Channel negotiation routes to game-theory analysis of power dynamics. Service provider negotiation routes to competitive bidding framework." + - question: "What is your BATNA (Best Alternative to Negotiated Agreement)? Do you have a viable alternative if this negotiation fails?" + purpose: "In e-commerce, sole-source supplier or single-3PL situations mean no BATNA, which fundamentally weakens negotiating position." + routing_impact: "No BATNA routes to alternative development before resuming negotiation. Strong BATNA routes to competitive-negotiation tactics." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Weak BATNA due to supplier concentration" + reason: "The most common reason e-commerce negotiations stall: the brand has no credible alternative, and the counterparty knows it." + less_likely: + - diagnosis: "Personality clash" + reason: "E-commerce negotiations are typically commercial, not personal. Stalls are driven by economics and power dynamics, not interpersonal issues." + sector_red_flags: + - "Sole-source supplier negotiation stalled — the brand has no alternative and is operating from a position of structural weakness." + - "Carrier contract expiring without renewal or alternative — shipping operations are at risk." diff --git a/plugins/foreman/content/industry-packs/e-commerce/e-commerce-skill-overlays.yaml b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-skill-overlays.yaml new file mode 100644 index 0000000..1d56452 --- /dev/null +++ b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-skill-overlays.yaml @@ -0,0 +1,431 @@ +# E-Commerce Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides e-commerce-specific +# context that the skill executor agent applies as additional framing. These +# overlays do not replace the base skill content — they add a physical product +# commerce lens. +# +# Every overlay reflects genuine e-commerce dynamics: inventory risk, COGS, +# fulfillment, returns, seasonality, product assortment, channel mix, and +# margin-driven decision-making. These are not SaaS frameworks relabeled with +# "e-commerce" vocabulary. Physical product businesses carry inventory, ship +# goods, process returns, and manage seasonal demand patterns — and that +# reality must be visible in every overlay. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct e-commerce application (strategy, pricing, marketing, ops) +# - Decision and thinking skills (used constantly in inventory, channel, and margin contexts) +# - Game theory skills applicable to supplier negotiation and competitive dynamics +# - Leadership skills most affected by e-commerce organizational structures +# - Negotiation skills relevant to supplier, channel, and fulfillment partner relationships +# +# Relevance tiers: +# critical — The e-commerce overlay materially changes how the skill is applied. +# The skill executor should always surface e-commerce context. +# high — E-commerce context adds significant value. Surface when relevant. +# moderate — Useful e-commerce framing but the base skill works well as-is. + +pack_metadata: + sector: "e-commerce" + display_name: "E-Commerce" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (20 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Porter's Five Forces in e-commerce must account for the extreme buyer power created by infinite digital alternatives and near-zero switching costs. Supplier power is concentrated in manufacturers and wholesalers who control production capacity, minimum order quantities, and lead times — a physical constraint absent in software. Threat of substitutes includes not just competing products but competing channels: Amazon, Walmart, Target, and every other retailer carrying similar goods. Rivalry is intensified by transparent pricing, review aggregation, and same-day delivery expectations set by Amazon." + ecommerce_anti_patterns: + - "Ignoring Amazon as a force in every analysis. Even if you do not sell on Amazon, Amazon's pricing, delivery speed, and product breadth set customer expectations in your category." + - "Underestimating supplier power. Manufacturers with minimum order quantities, long lead times, and exclusive distribution agreements hold leverage that software suppliers simply do not." + - "Confusing low barriers to entry with low threat of entry. Starting an e-commerce store is trivial; building a brand with repeat customers and efficient logistics is not. The threat comes from well-funded competitors, not hobby stores." + ecommerce_example: "A DTC skincare brand uses Five Forces to discover that supplier power is its most dangerous force: their contract manufacturer also supplies three competitors, has a 16-week lead time, and requires 10,000-unit minimums. Switching costs are high because the manufacturer holds proprietary formulations. This analysis triggers a strategic initiative to diversify manufacturing and bring formulation IP in-house — a defensive move that would never surface in a standard competitive analysis." + benchmark_references: ["gross-margin", "cac", "return-rate"] + + - skill: "blue-ocean-strategy" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Blue ocean strategy is structurally vital for e-commerce because commodity products face relentless price competition. The strategy canvas in e-commerce maps factors like price, product quality, packaging, delivery speed, customization, sustainability, community, and post-purchase experience. Blue oceans emerge when brands eliminate traditional retail factors (broad assortment, lowest price) and create new ones (curation, brand storytelling, unboxing experience, community membership). The most successful DTC brands — Glossier in beauty, Allbirds in footwear, Dollar Shave Club in grooming — found blue ocean by redefining the value curve, not by competing on features or price." + ecommerce_anti_patterns: + - "Pursuing a blue ocean through product differentiation alone without addressing the distribution and experience dimensions. A superior product sold through the same channels with the same experience is still in a red ocean." + - "Assuming that premium pricing automatically creates a blue ocean. Premium price without a differentiated value proposition beyond 'quality' positions the brand in a crowded luxury segment." + - "Ignoring that Amazon is the red ocean. Blue ocean strategy for e-commerce almost always means avoiding direct competition on Amazon by creating value dimensions that Amazon cannot replicate: curation, community, expertise, personalization." + ecommerce_example: "Dollar Shave Club drew a strategy canvas against Gillette and found that razors competed on blade count, lubrication strips, and pivoting heads — a classic red ocean of feature escalation. DSC eliminated all those factors and created new ones: subscription convenience, humorous brand voice, low monthly cost, and direct-to-door delivery. The blue ocean was not a better razor; it was a different buying experience." + benchmark_references: ["repeat-purchase-rate", "nps", "organic-traffic-pct"] + + - skill: "business-model-canvas" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "The Business Model Canvas for e-commerce requires physical-product-specific interpretation of nearly every block. Revenue Streams must distinguish one-time purchases, subscription revenue, wholesale, and marketplace commissions. Cost Structure must explicitly itemize COGS, fulfillment, shipping, returns processing, payment processing, and inventory carrying costs — the variable costs that determine per-order profitability. Key Resources must include supplier relationships, inventory, and warehouse infrastructure. Key Activities must include demand forecasting, inventory planning, and fulfillment operations. The canvas is most powerful when used to compare a DTC-only model against an omnichannel model (DTC + wholesale + Amazon), revealing how each channel changes every block." + ecommerce_anti_patterns: + - "Omitting inventory and supply chain from Key Resources. Inventory is the largest capital commitment in most e-commerce businesses and the primary source of financial risk." + - "Treating 'Customer Relationships' as a single category. E-commerce has distinct relationship models: transactional one-time buyers, subscription members, loyalty program participants, and wholesale accounts." + - "Ignoring returns in the Cost Structure. Returns are not a marginal cost — they represent 10-30% of revenue in many categories and require dedicated processes and infrastructure." + ecommerce_example: "A DTC food brand uses the canvas to evaluate adding Amazon as a channel. The canvas reveals: Revenue Streams gain volume but at lower margin (Amazon fees + FBA costs). Cost Structure adds Amazon advertising and FBA fees while potentially cannibalizing higher-margin DTC sales. Customer Relationships shift from owned (email, SMS) to rented (Amazon owns the customer). Key Activities now include Amazon SEO, advertising management, and Seller Central operations. The canvas makes visible what intuition misses: Amazon may grow revenue while degrading the business model." + benchmark_references: ["contribution-margin", "gross-margin", "cac", "ltv", "return-rate"] + + - skill: "four-ps-marketing" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "The Four Ps require deep e-commerce adaptation. Product means physical SKU management, assortment breadth and depth, packaging, and the unboxing experience — not a software feature set. Price in e-commerce is margin-driven: pricing must cover COGS + fulfillment + shipping + returns + marketing and leave contribution margin. Promotional pricing (discounts, sales, bundles) is a constant tension between volume and margin erosion. Place is channel mix strategy: own website, Amazon, Walmart Marketplace, wholesale to retailers, brick-and-mortar, social commerce (Instagram/TikTok Shop). Each channel has different economics, customer relationships, and operational requirements. Promotion spans paid media (Meta, Google, TikTok), email/SMS, influencer partnerships, content marketing, and PR — with attribution complexity across all channels." + ecommerce_anti_patterns: + - "Setting price based on competitor pricing without calculating contribution margin. In e-commerce, the floor price is COGS + fulfillment + shipping + returns + target margin, not what competitors charge." + - "Treating Amazon as 'just another channel' in the Place analysis. Amazon fundamentally changes the other three Ps: price is visible and compared instantly, product must compete with Amazon's own brands, and promotion requires Amazon-specific advertising." + - "Running promotions (sales, discounts, free shipping) without modeling the full contribution margin impact including increased return rates. Discounted purchases have higher return rates in most categories." + ecommerce_example: "A home goods DTC brand applies the Four Ps and discovers a structural problem in Place: 60% of revenue comes from their website at 35% contribution margin, while 25% comes from Amazon at 12% contribution margin. The remaining 15% from wholesale barely breaks even after trade spend. The Place analysis reveals that the brand has a channel problem, not a growth problem — scaling Amazon and wholesale dilutes overall profitability. The strategy shifts to growing DTC to 80%+ of revenue through email and content investment." + benchmark_references: ["aov", "cac", "contribution-margin", "email-revenue-pct", "cpa-by-channel"] + + - skill: "net-promoter-score" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "NPS in e-commerce reflects the complete physical product experience — not just the product itself but the entire chain from discovery to delivery to use to potential return. A customer's NPS response is shaped by product quality, packaging, shipping speed, unboxing experience, product matching expectations, customer service responsiveness, and the ease of returns. NPS surveys should be triggered post-delivery (not post-purchase) and segmented by product category, shipping method, and whether the customer has returned items. The qualitative follow-up question is gold: e-commerce detractors often cite specific, fixable operational failures rather than abstract dissatisfaction." + ecommerce_anti_patterns: + - "Surveying immediately after purchase (checkout confirmation) rather than after delivery. The customer has not experienced the product yet, so the NPS measures the buying experience, not the brand experience." + - "Aggregating NPS across all product categories. A brand selling both premium and budget lines will see dramatically different NPS by tier. Category-level NPS drives actionable insights." + - "Ignoring NPS from customers who returned items. Returners are the most informative detractors — their feedback reveals the gap between product expectation and reality." + ecommerce_example: "A DTC apparel brand discovers that overall NPS is 42 (good) but NPS from customers who received orders via economy shipping is 18 (poor), while NPS from expedited shipping customers is 62 (excellent). The root cause is not shipping speed itself but inadequate packaging for economy routes — products arrive wrinkled and poorly presented. The fix is packaging redesign, not shipping upgrade subsidies." + benchmark_references: ["nps", "csat", "return-rate", "repeat-purchase-rate"] + + - skill: "product-life-cycle" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Product lifecycle in e-commerce applies both to individual SKUs and to the brand's product assortment as a whole. Individual products follow the classic introduction-growth-maturity-decline curve, but physical products experience lifecycle dynamics that software does not: seasonal demand patterns, fashion trend cycles, ingredient or material availability, and physical obsolescence. Assortment management requires deliberately maintaining a portfolio of products at different lifecycle stages — introducing new SKUs while harvesting mature ones and discontinuing declining ones. The cash flow implications are significant: new product introductions require inventory investment before revenue, while declining products tie up capital in unsold stock." + ecommerce_anti_patterns: + - "Holding declining SKUs in the assortment because of sunk cost in inventory. Slow-moving inventory consumes warehouse space, ties up capital, and complicates fulfillment operations." + - "Introducing too many new products simultaneously without the marketing budget to support each launch. New product introductions in e-commerce require coordinated investment in photography, content, paid media, and email campaigns." + - "Ignoring seasonal lifecycle patterns. Many e-commerce products have annual cycles (outdoor gear, holiday gifts, back-to-school) that compress the entire lifecycle into a 3-4 month window." + ecommerce_example: "A DTC accessories brand tracks lifecycle stage for each of its 80 SKUs and discovers that 35% of SKUs are in decline (selling fewer units each quarter with rising markdown frequency). These declining SKUs occupy 45% of warehouse space and 20% of the photography and marketing budget. The lifecycle analysis triggers a SKU rationalization: discontinue the bottom 20 SKUs, run clearance on the next 10, and redirect freed capital and marketing budget toward 8 new product launches in growth categories." + benchmark_references: ["inventory-turnover", "days-of-inventory", "gross-margin", "contribution-margin"] + + - skill: "growth-share-matrix" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "The BCG Growth-Share Matrix maps directly to e-commerce product portfolio and channel management. Stars are high-growth, high-share product categories or channels — invest aggressively. Cash Cows are mature product lines with strong, stable sales and proven margins — use their cash flow to fund new product development and market expansion. Question Marks are new product categories or channels with potential but unproven economics. Dogs are low-growth, low-share SKUs that consume inventory capital and warehouse space without contributing meaningful revenue or margin. The matrix is particularly useful for e-commerce brands deciding where to invest limited marketing and inventory capital across a growing product assortment." + ecommerce_anti_patterns: + - "Treating every SKU as a potential Star. A 500-SKU catalog likely has 20-30 Stars, 50-80 Cash Cows, and hundreds of Question Marks and Dogs. Capital allocation should reflect this distribution." + - "Killing all Dogs immediately without considering their role in the assortment. Some low-selling SKUs serve as range completers that drive traffic or support the brand story." + - "Investing in Question Marks without clear criteria for promotion to Star or demotion to Dog. Set time-bound inventory and marketing thresholds for new product experiments." + ecommerce_example: "A home goods brand maps its product lines: kitchen gadgets (Star — 40% YoY growth, category leader), bath textiles (Cash Cow — stable sales, 65% gross margin), outdoor furniture (Question Mark — growing market but low brand share), and decorative candles (Dog — declining sales, 8 months of inventory). The matrix drives a decision: invest the bath textiles' margin into scaling kitchen gadgets and testing outdoor furniture, while liquidating candle inventory and exiting the category." + benchmark_references: ["inventory-turnover", "gross-margin", "revenue"] + + - skill: "disruptive-innovation" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "Disruptive innovation in e-commerce typically follows one of two patterns: disruption of the retail channel (DTC brands disrupting traditional retail distribution) or disruption of the product itself (simpler, cheaper, more convenient alternatives). The classic DTC disruption narrative — Warby Parker disrupting eyewear retail, Casper disrupting mattress retail, Harry's disrupting razor retail — follows the textbook pattern: enter at the bottom with a simpler proposition, use digital distribution to reach underserved customers, and build brand loyalty before incumbents respond. Understanding where your brand sits in this disruption cycle determines strategic priorities." + ecommerce_anti_patterns: + - "Assuming DTC channel innovation alone constitutes disruption. Selling the same product through a website at a similar price is not disruption — it is channel arbitrage, which is temporary." + - "Moving upmarket prematurely by adding premium product lines before dominating the entry-level segment. Casper's expansion into premium mattresses diluted their disruptive position." + - "Ignoring the sustaining innovation response from incumbents. When DTC razor brands proved demand, Gillette launched its own subscription service and acquired competitors. The disruption window is finite." + ecommerce_example: "Dollar Shave Club disrupted Gillette not with a better razor but with a simpler, cheaper, more convenient one delivered by subscription. Gillette initially ignored DSC because the product was 'inferior' — exactly the dismissal that enables disruption. By the time Gillette responded, DSC had built sufficient brand loyalty and distribution efficiency to be acquired by Unilever for $1 billion." + benchmark_references: ["cac", "repeat-purchase-rate", "organic-traffic-pct"] + + - skill: "balanced-scorecard" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "The Balanced Scorecard for e-commerce maps across its four perspectives with physical-product specifics. Financial: Revenue, Contribution Margin, Gross Margin, LTV:CAC, Inventory Turnover. Customer: NPS, Repeat Purchase Rate, Return Rate, Time to Delivery, CSAT. Internal Process: Fulfillment Cost per Order, Order Accuracy Rate, Shipping Cost %, Days of Inventory, Stockout Rate. Learning & Growth: Product Development Cycle Time, Supplier Diversification, Team Cross-Training Rate, Technology Investment (ERP, WMS, CRM). The scorecard is powerful in e-commerce because physical operations generate abundant real-time data, but most brands track financial and customer metrics while neglecting internal process and learning perspectives." + ecommerce_anti_patterns: + - "Over-weighting financial metrics at the expense of operational ones. In e-commerce, internal process failures (stockouts, fulfillment errors, slow shipping) manifest as financial problems with a lag." + - "Ignoring inventory metrics in the scorecard. Inventory is the largest asset on most e-commerce balance sheets and the primary driver of cash flow health." + - "Treating the scorecard as a reporting tool rather than a decision tool. Each metric should have a clear owner, an action threshold, and a documented response playbook when the threshold is breached." + ecommerce_example: "A DTC supplement brand implements a balanced scorecard and discovers a dangerous disconnect: Financial metrics are strong (revenue growing 30% YoY, contribution margin 28%), but Internal Process metrics are deteriorating (days of inventory rising from 45 to 90, fulfillment cost per order increasing 20%, stockout frequency doubling). The scorecard reveals that rapid revenue growth is straining operations — and if internal process deterioration continues, it will eventually destroy the financial results." + benchmark_references: ["revenue", "contribution-margin", "gross-margin", "nps", "repeat-purchase-rate", "return-rate", "fulfillment-cost-per-order", "inventory-turnover", "days-of-inventory"] + + - skill: "swot-pest-analysis" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "SWOT and PEST in e-commerce must address the physical supply chain, seasonal demand, and channel dependencies that define the sector. Political: tariffs and trade policy (critical for imported goods), product safety regulations (FDA, CPSC), and state-level sales tax complexity. Economic: consumer spending power, shipping cost inflation, raw material price volatility, and interest rates (affecting inventory financing costs). Social: sustainability expectations, influencer culture driving product discovery, and generational shopping preferences (Gen Z social commerce, Millennial DTC loyalty). Technological: AI-driven personalization, 3D/AR product visualization, same-day delivery infrastructure, and social commerce platform evolution." + ecommerce_anti_patterns: + - "Listing 'strong brand' as a strength without evidence. In e-commerce, brand strength is measured by organic traffic percentage, direct URL visits, repeat purchase rate, and NPS — not by the founder's intuition." + - "Ignoring tariff and trade policy risk for brands sourcing from Asia. A 20% tariff increase on Chinese imports can eliminate gross margin overnight." + - "Treating 'Amazon' as a threat without specifying the mechanism: is Amazon a threat as a competing retailer, as a private label competitor, or as a platform that owns your customer relationship?" + ecommerce_example: "A DTC home goods brand sources 80% of products from China. PEST analysis identifies tariff escalation as a high-probability economic risk (current 25% Section 301 tariffs could increase). SWOT reveals that China-only sourcing is a critical weakness, while the brand's design capability (creating products that are not easily replicated by Amazon Basics) is a strength. This analysis triggers a dual initiative: diversify manufacturing to Vietnam and India (reduce PEST vulnerability) while investing in proprietary designs with utility patents (strengthen SWOT position)." + benchmark_references: ["gross-margin", "cac", "organic-traffic-pct"] + + - skill: "scenario-planning" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Scenario planning in e-commerce must account for variables unique to physical product businesses: supply chain disruption (container shortages, factory closures, raw material scarcity), seasonal demand volatility (holiday season can represent 30-50% of annual revenue), channel risk (Amazon policy changes, Meta ad cost spikes), and inventory commitment risk (orders placed months in advance based on demand forecasts). The planning horizon must align with manufacturing lead times — a brand with 16-week production cycles must plan scenarios 4-6 months out. E-commerce scenarios should model three critical dimensions: demand volatility (upside, base, downside), supply chain reliability (normal, disrupted, severely disrupted), and channel economics (stable, degrading, crisis)." + ecommerce_anti_patterns: + - "Planning for a single demand forecast. E-commerce demand is inherently volatile — seasonal, trend-driven, and influenced by viral moments. Scenario planning must include demand upside (stockout risk) alongside demand downside (excess inventory risk)." + - "Ignoring supply chain lead time in scenarios. A scenario that requires 'pivot to new supplier' is not actionable if the new supplier requires 16 weeks to produce and the scenario horizon is 8 weeks." + - "Treating marketing channel costs as stable in all scenarios. Meta and Google CPMs can increase 30-50% during Q4, fundamentally changing acquisition economics during peak season." + ecommerce_example: "A DTC brand planning for Q4 builds three scenarios: (1) Base case: demand inline with last year +20%, supply chain on schedule, marketing costs up 15%. (2) Upside: viral product moment doubles demand in November; test whether inventory can support 2x orders and whether fulfillment can ship within 3 days at peak volume. (3) Downside: supply chain delay pushes key SKU arrival to December 15; model revenue impact of 4-week stockout on the hero product and evaluate air freight costs to bridge the gap." + benchmark_references: ["days-of-inventory", "inventory-turnover", "contribution-margin", "shipping-cost-pct"] + + - skill: "cialdini-influence" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Cialdini's six principles of influence are the foundation of e-commerce conversion optimization. Reciprocity: free samples, generous return policies, and surprise gifts in orders drive repeat purchases. Scarcity: limited editions, low-stock warnings, and countdown timers drive urgency. Authority: expert endorsements, certification badges, and media mentions build trust. Social Proof: customer reviews, user-generated content, and purchase count indicators reduce buying anxiety. Liking: brand personality, founder story, and lifestyle alignment drive affinity. Commitment & Consistency: email list signup, wishlist creation, and loyalty programs create behavioral momentum toward purchase." + ecommerce_anti_patterns: + - "Overusing scarcity tactics with false urgency. Customers learn quickly that 'only 3 left' is permanent and 'sale ends tonight' resets tomorrow. Fake scarcity destroys trust." + - "Relying on social proof (reviews) without investing in generating it. Fewer than 5% of customers leave reviews unprompted. Active review solicitation programs are essential." + - "Applying influence principles to the product page while neglecting the post-purchase experience. Reciprocity and liking are most powerful after the first purchase — the unboxing experience, follow-up emails, and surprise gifts create the emotional connection that drives repeat purchasing." + ecommerce_example: "A DTC beauty brand applies all six principles to their customer journey: Reciprocity — free sample included with every order. Social Proof — reviews with photos displayed prominently, UGC gallery on product pages. Scarcity — genuinely limited seasonal collections. Authority — dermatologist endorsement on product pages. Liking — founder's personal story woven into packaging. Commitment — skincare quiz creates personalized routine, making the first purchase feel like committing to a program rather than buying a single product." + benchmark_references: ["conversion-rate", "cart-abandonment-rate", "repeat-purchase-rate", "aov"] + + - skill: "systems-thinking" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "E-commerce businesses are complex systems with feedback loops and delays that produce counterintuitive outcomes. The core system dynamics include: the inventory-cash cycle (inventory investment ties up cash, which limits marketing spend, which reduces revenue, which constrains inventory investment); the discount-return loop (discounts increase volume but attract price-sensitive buyers with higher return rates, which reduces margins, which pressures more discounting); the quality-growth tension (scaling too fast degrades fulfillment quality, which increases returns and reduces NPS, which kills repeat purchases, which stalls growth). Systems thinking is essential because e-commerce operators frequently solve one problem while creating another downstream." + ecommerce_anti_patterns: + - "Treating marketing and operations as independent systems. A marketing campaign that drives a 50% order spike will fail if fulfillment cannot scale, and the resulting delivery delays will damage the brand for months." + - "Optimizing individual metrics without modeling the system effects. Reducing shipping cost by switching to economy carriers reduces the shipping-cost metric but increases delivery time, which reduces NPS, which reduces repeat purchase rate." + - "Ignoring time delays. Inventory decisions made today manifest as stockouts or excess 3-6 months later. Marketing spend today creates customers whose LTV plays out over 12-24 months." + ecommerce_example: "A DTC food brand runs a 40%-off sale that generates 3x normal volume. Systems thinking reveals the cascading effects: fulfillment team works overtime (increased labor cost per order), shipping errors triple (returns spike), the discount attracts low-intent buyers (first-cohort repeat rate is 8% versus normal 35%), and the 40% discount becomes the new reference price (customers wait for the next sale instead of buying at full price). The sale increased GMV by 200% but decreased contribution margin by 40% and degraded long-term unit economics." + benchmark_references: ["contribution-margin", "return-rate", "repeat-purchase-rate", "fulfillment-cost-per-order"] + + - skill: "kaizen-bpr" + category: "frameworks" + ecommerce_relevance: "critical" + ecommerce_context: "Kaizen (continuous improvement) and BPR (business process reengineering) apply directly to the physical operations that determine e-commerce profitability: warehouse processes, fulfillment workflows, returns processing, inventory receiving, quality inspection, and customer service procedures. In e-commerce, small operational improvements compound: reducing pick-and-pack time by 30 seconds per order saves $0.15 per order, which at 100,000 orders per year saves $15,000 — enough to fund a fulfillment technology upgrade. Kaizen is the operational philosophy that transforms e-commerce from a volume game (grow revenue) to a margin game (improve contribution margin per order)." + ecommerce_anti_patterns: + - "Applying Kaizen only to warehouse operations while ignoring the product page-to-checkout conversion funnel. Every step in the customer journey — product discovery, page load speed, checkout flow, post-purchase communication — is a process that can be continuously improved." + - "Pursuing BPR (radical redesign) when Kaizen (incremental improvement) would suffice. Replacing a functional 3PL with in-house fulfillment is BPR; optimizing pick paths and packaging at the existing 3PL is Kaizen." + - "Measuring process improvement without linking it to unit economics. Every operational improvement should be expressed in its impact on contribution margin per order." + ecommerce_example: "A brand processing 500 orders per day applies Kaizen to its returns workflow. Current state: returns arrive unsorted, are inspected individually, require manual restocking decisions, and take 7 days to process. Kaizen improvements: standardized return receiving bins by category, batch inspection with pass/fail criteria, automated restocking rules by product condition, and same-day processing target. Result: return processing cost drops from $8 per return to $3.50, and 15% of returns that were previously written off as unsellable are recaptured as 'like new' inventory." + benchmark_references: ["fulfillment-cost-per-order", "return-rate", "shipping-cost-pct", "contribution-margin"] + + - skill: "tipping-point" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "Tipping point dynamics in e-commerce manifest through virality, influencer cascades, and social proof accumulation. The three agents of change map to e-commerce: Connectors are influencers and brand ambassadors who amplify product discovery to large audiences. Mavens are product reviewers, comparison bloggers, and Reddit community members who provide detailed, trusted product evaluations. Salesmen are the brand's own content and UGC that converts awareness to purchase. The stickiness factor is the product experience — unboxing, quality, and post-purchase delight. The power of context includes seasonal timing, cultural moments, and platform algorithm alignment." + ecommerce_anti_patterns: + - "Confusing paid influencer reach with organic tipping point dynamics. Paid influencer posts drive temporary spikes; genuine tipping points require organic sharing driven by product delight." + - "Pursuing virality without the operational infrastructure to support it. A TikTok viral moment that generates 10x normal order volume will destroy the brand if fulfillment cannot keep up." + - "Ignoring the stickiness factor (product quality and experience). No amount of marketing can create a tipping point if the product experience does not generate genuine advocacy." + ecommerce_example: "Stanley's 40oz Quencher tumbler reached its tipping point through the convergence of all three elements: The Buy Guide (Mavens) advocated persistently for the product. Influencers on TikTok (Connectors) created unboxing and lifestyle content. The product's color variety and visual appeal (Stickiness) made it inherently shareable. The context was the 'emotional support water bottle' cultural moment. Stanley went from $73M to $750M in revenue in two years — a genuine demand tipping point, not a marketing campaign." + benchmark_references: ["organic-traffic-pct", "repeat-purchase-rate", "nps"] + + - skill: "eisenhower-matrix" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "The Eisenhower Matrix is essential for e-commerce founders because the operational intensity of physical product businesses creates a constant stream of urgent-but-not-important tasks: inventory reorders, fulfillment exceptions, customer service escalations, shipping carrier issues, and marketing campaign management. Without rigorous prioritization, e-commerce operators spend 80% of their time on Quadrant III (urgent, not important) while neglecting Quadrant II (important, not urgent): supplier diversification, brand building, product development, and systems automation." + ecommerce_anti_patterns: + - "Treating every stockout as a Quadrant I emergency. Some stockouts on low-margin, low-velocity SKUs are acceptable and should not displace strategic work." + - "Classifying all marketing 'opportunities' (flash sale partnerships, influencer deals, platform promotions) as Quadrant I. Most are Quadrant III at best." + - "Neglecting Quadrant II inventory planning. Inventory decisions require long lead times. Delaying planning until it becomes urgent means every inventory decision is reactive and suboptimal." + ecommerce_example: "A DTC founder maps their weekly tasks to the Eisenhower Matrix and discovers that 60% of their time goes to Quadrant III: answering customer service emails that a team member could handle, manually processing returns, and adjusting individual product ad campaigns. They redesign their week: delegate customer service and returns processing (Quadrant III), block Tuesday and Thursday mornings for product development and supplier negotiation (Quadrant II), and define clear escalation criteria for what constitutes a genuine Quadrant I operational emergency." + benchmark_references: ["contribution-margin", "fulfillment-cost-per-order"] + + - skill: "doblin-ten-types" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "Doblin's Ten Types of Innovation applied to e-commerce reveals that most brands innovate only on products (Performance) while ignoring the other nine types. E-commerce-specific innovation opportunities across the ten types: Profit Model (subscription, bundle pricing, membership); Network (supplier partnerships, shared warehousing); Structure (virtual teams, 3PL orchestration); Process (fulfillment automation, returns as exchange); Product Performance (materials, formulations, features); Product System (complementary product bundles, curated routines); Service (personalization, loyalty programs, post-purchase care); Channel (social commerce, pop-ups, wholesale); Brand (community building, founder story, values alignment); Customer Engagement (UGC programs, unboxing experience, referral programs)." + ecommerce_anti_patterns: + - "Innovating only on Product Performance. A better product in a crowded category with identical distribution, pricing, and experience is not innovation — it is incremental improvement in a red ocean." + - "Ignoring Channel innovation. How and where the customer encounters and purchases the product is often more differentiated than the product itself." + - "Overlooking Service innovation. Post-purchase experience (delivery tracking, unboxing, follow-up communication, easy returns) is the most under-innovated area in e-commerce." + ecommerce_example: "A DTC pet food brand audits itself against the ten types and discovers innovation concentrated entirely in Product Performance (premium ingredients). They identify three underexploited types: Profit Model (launch a subscription with auto-ship at a discount), Customer Engagement (build a community forum for pet health advice), and Product System (create a complementary treats and supplements line that bundles with the core food product). Each innovation type creates a separate competitive advantage that product quality alone cannot provide." + benchmark_references: ["repeat-purchase-rate", "aov", "nps", "ltv"] + + - skill: "covey-seven-habits" + category: "frameworks" + ecommerce_relevance: "moderate" + ecommerce_context: "The Seven Habits apply to e-commerce founders with particular urgency because the operational demands of physical product businesses create a reactive, firefighting mentality. Habit 2 (Begin with the End in Mind) requires defining whether the business is being built for profitability, exit, or lifestyle — each demands different decisions on inventory investment, channel strategy, and growth rate. Habit 3 (Put First Things First) maps to the Eisenhower Matrix challenge: e-commerce founders must protect strategic time for brand building, product development, and systems design from the constant pull of operational urgency. Habit 7 (Sharpen the Saw) includes learning supply chain management, logistics negotiation, and financial modeling — operational skills that many DTC founders lack." + ecommerce_anti_patterns: + - "Operating without Habit 2 clarity. A founder building for acquisition should optimize for revenue growth and brand equity; a founder building for profitability should optimize for contribution margin and repeat purchase rate. These strategies conflict." + - "Neglecting Habit 4 (Think Win-Win) in supplier relationships. Short-term extraction (demanding lower prices, delaying payments) degrades supplier quality and reliability." + ecommerce_example: "A DTC founder applies Habit 2 and realizes they have been implicitly building for acquisition (prioritizing revenue growth and brand awareness) while personally wanting a lifestyle business (profitability and flexibility). This misalignment explains why they feel burnt out and cash-constrained despite impressive growth. The framework triggers a strategic pivot: reduce growth rate from 50% to 25%, invest in contribution margin improvement, and build systems that reduce the founder's operational involvement." + benchmark_references: ["contribution-margin", "repeat-purchase-rate"] + + - skill: "smart-goals" + category: "frameworks" + ecommerce_relevance: "high" + ecommerce_context: "SMART goals in e-commerce must account for the physical constraints and seasonal rhythms unique to the business. Specific means identifying the lever — is the goal about traffic, conversion, AOV, repeat rate, or contribution margin? Measurable requires reliable data infrastructure — many e-commerce brands track revenue but lack accurate per-order contribution margin, return rate by SKU, or true customer acquisition cost by channel. Achievable must account for supply chain lead times — a goal to launch a new product line in 60 days is not achievable if manufacturing lead time is 90 days. Relevant must align with the correct stage — a brand at $500K revenue should set goals around repeat purchase rate, not international expansion. Time-Bound must respect seasonal patterns — setting an annual revenue goal without modeling Q4 concentration is setting a goal in the dark." + ecommerce_anti_patterns: + - "Setting revenue goals without paired margin goals. A revenue target without a contribution margin floor incentivizes discounting, which grows revenue while destroying economics." + - "Ignoring inventory implications of growth goals. A goal to double revenue requires doubling inventory investment, which requires financing. The capital plan must accompany the growth goal." + - "Setting annual goals without quarterly milestones that account for seasonality. A $4M annual revenue goal might require $600K in Q1 and $1.5M in Q4." + ecommerce_example: "A DTC brand translates 'grow the business' into SMART goals: Increase contribution margin from 22% to 28% by December 31 by (1) renegotiating supplier pricing (target: 3pp COGS reduction), (2) reducing return rate from 18% to 14% through improved size guides, and (3) reducing fulfillment cost per order from $5.50 to $4.00 by switching to a regional 3PL network. Each sub-goal is specific, measurable, achievable within the timeframe, relevant to profitability, and time-bound." + benchmark_references: ["contribution-margin", "return-rate", "fulfillment-cost-per-order", "gross-margin"] + + - skill: "organisational-culture" + category: "frameworks" + ecommerce_relevance: "moderate" + ecommerce_context: "E-commerce organizational culture is shaped by the hybrid nature of the business: creative (brand, product, marketing) and operational (warehouse, fulfillment, logistics, customer service) functions must coexist. The cultural challenge is bridging the gap between the brand team that wants beautiful packaging and the operations team that needs standardized boxes for efficient fulfillment. High-performing e-commerce cultures develop shared metrics (contribution margin per order) that align creative and operational incentives. Seasonal intensity (Q4 crunch) tests culture severely — brands that treat warehouse staff as second-class citizens during peak season create lasting cultural damage." + ecommerce_anti_patterns: + - "Building a 'tech startup' culture in a business that is fundamentally logistics-dependent. E-commerce requires operational discipline alongside creative energy." + - "Treating warehouse and fulfillment staff as interchangeable labor. The best e-commerce operations build fulfillment team culture with the same intention as headquarters culture." + ecommerce_example: "A DTC brand experiencing fulfillment errors and warehouse staff turnover discovers that the root cause is cultural: the brand team makes last-minute packaging changes for seasonal campaigns without consulting operations, creating confusion and rework. The fix is not operational — it is cultural: institute joint planning sessions between brand and operations, establish change-request lead times, and create a shared metric (on-time, error-free delivery rate) that both teams own." + benchmark_references: ["fulfillment-cost-per-order", "return-rate", "csat"] + + # ───────────────────────────────────────────── + # GAME THEORY (4 skills) + # ───────────────────────────────────────────── + + - skill: "game-theory-fundamentals" + category: "game-theory" + ecommerce_relevance: "high" + ecommerce_context: "Game theory in e-commerce governs three critical relationships: supplier negotiations (repeated games with asymmetric information), competitive pricing dynamics (pricing signals and responses among direct competitors), and channel strategy (the marketplace vs. DTC game where brands and platforms compete for customer ownership). The most consequential game in e-commerce is the Amazon dependency game: brands grow volume on Amazon but surrender customer data, margin, and relationship to the platform. The rational short-term play (sell on Amazon) creates long-term strategic vulnerability." + ecommerce_anti_patterns: + - "Treating supplier negotiations as one-shot games. Supplier relationships in e-commerce are repeated games where reputation, reliability, and growth potential create cooperative equilibria that pure price negotiation destroys." + - "Engaging in price wars without modeling the equilibrium. In commoditized e-commerce categories, a race to the bottom benefits no one — Nash equilibrium is mutual low profit." + ecommerce_example: "A DTC supplement brand models the Amazon channel game: joining Amazon increases short-term revenue 40% but trains customers to buy on Amazon (where the brand has no relationship data and pays 30% in fees) instead of the brand's website (where contribution margin is 15pp higher). Game theory reveals the prisoner's dilemma: every brand individually benefits from joining Amazon, but collectively all brands lose margin. The brand decides to stay off Amazon and invest the would-be-Amazon-margin in DTC acquisition and retention." + benchmark_references: ["contribution-margin", "cac", "organic-traffic-pct"] + + - skill: "first-mover-strategy" + category: "game-theory" + ecommerce_relevance: "high" + ecommerce_context: "First mover advantage in e-commerce is weaker than in software because physical products can be copied and manufactured by competitors within months. The durable first-mover advantages in e-commerce are brand recognition (owning a category name), supply chain relationships (exclusive manufacturing partnerships), review accumulation (hundreds of positive reviews create a moat on Amazon), and email/SMS list building (owned audience that competitors cannot replicate). First mover disadvantage is real in e-commerce: the first brand educates the market and establishes the category while second movers learn from mistakes and enter with optimized products and proven marketing playbooks." + ecommerce_anti_patterns: + - "Assuming product uniqueness will persist. In e-commerce, any successful physical product will be copied by competitors (including Amazon Basics) within 6-12 months. First mover advantage must be invested in building durable moats." + - "Rushing to market with subpar product quality to 'be first.' In e-commerce, negative reviews from early customers create a lasting brand tax. The cost of bad reviews often exceeds the benefit of being first." + ecommerce_example: "Allbirds moved first in sustainable wool sneakers and invested the first-mover window in building brand identity, accumulating reviews, and establishing retail partnerships. When Amazon launched a virtually identical shoe at half the price, Allbirds' first-mover advantages — brand association with sustainability, 10,000+ reviews, and wholesale distribution — partially protected the position. The lesson: use the first-mover window to build moats, not to coast." + benchmark_references: ["organic-traffic-pct", "nps", "repeat-purchase-rate"] + + - skill: "information-asymmetry" + category: "game-theory" + ecommerce_relevance: "high" + ecommerce_context: "Information asymmetry pervades e-commerce at multiple levels. Between brands and customers: customers cannot inspect physical products before purchasing online, creating uncertainty that reviews, photos, and return policies must address. Between brands and suppliers: manufacturers have information about production costs and capacity that brands lack, enabling supplier margin extraction. Between brands and marketplace platforms: Amazon has granular data on product demand, pricing, and customer behavior that sellers do not — and uses that information to launch competing private-label products." + ecommerce_anti_patterns: + - "Accepting information asymmetry with suppliers as permanent. Brands should invest in understanding true manufacturing costs through factory audits, alternative quotes, and bill-of-materials analysis." + - "Ignoring the information disadvantage on Amazon. Amazon's data advantage is a structural feature of selling on their platform. Brands that do not invest in their own customer data (via DTC) operate at a permanent disadvantage." + ecommerce_example: "A DTC housewares brand selling on Amazon discovers that their highest-margin product category experiences a 40% sales decline after Amazon launches an Amazon Basics version at 50% lower price. The information asymmetry was structural: Amazon had access to exact demand data, pricing sensitivity, and return rates for the category — and used that information to compete directly. The brand exits Amazon for that category and invests in DTC-exclusive products with design IP that Amazon cannot easily replicate." + benchmark_references: ["gross-margin", "cac", "return-rate"] + + - skill: "negotiation-game-theory" + category: "game-theory" + ecommerce_relevance: "high" + ecommerce_context: "Negotiation game theory in e-commerce applies to the three most consequential negotiations: supplier/manufacturer terms (pricing, MOQs, payment terms, exclusivity), channel partner agreements (wholesale margins, co-op advertising, placement fees), and carrier/3PL contracts (shipping rates, volume commitments, service levels). Each negotiation has game-theoretic structure: the supplier negotiation is a repeated game where both parties have BATNA (Best Alternative to Negotiated Agreement) that shapes leverage. The carrier negotiation is a competitive auction where multiple providers bid for volume. The retail/wholesale negotiation is a credence game where the brand's perceived demand strength determines leverage." + ecommerce_anti_patterns: + - "Negotiating supplier pricing in isolation from other terms. In e-commerce, payment terms (net-30 vs. net-60), minimum order quantities, and lead time flexibility are often more valuable than a 2% price reduction." + - "Accepting carrier rates without competitive bidding. Carrier pricing in e-commerce is highly negotiable, and switching costs are low. Annual rate reviews with competitive bids should be standard practice." + ecommerce_example: "A DTC brand negotiating with a contract manufacturer frames the negotiation game-theoretically: the manufacturer's BATNA is other customers (moderate — they have capacity), the brand's BATNA is other manufacturers (weak — the current manufacturer holds proprietary formulations). This power imbalance means price negotiation is futile. Instead, the brand negotiates on a different dimension: extended payment terms (net-60 instead of prepayment) and flexible MOQs for new product testing. Both concessions are low-cost for the manufacturer but high-value for the brand's cash flow and product development agility." + benchmark_references: ["gross-margin", "days-of-inventory", "contribution-margin"] + + # ───────────────────────────────────────────── + # NEGOTIATION (2 skills) + # ───────────────────────────────────────────── + + - skill: "cooperative-negotiation" + category: "negotiation" + ecommerce_relevance: "high" + ecommerce_context: "Cooperative negotiation in e-commerce is essential for the long-term supplier and channel relationships that sustain physical product businesses. Unlike transactional negotiations, e-commerce brands negotiate with the same manufacturers, distributors, and retail partners repeatedly over years. Cooperative frameworks (interest-based bargaining, value creation, expanding the pie) produce better outcomes because both parties depend on the relationship: the brand needs reliable production and favorable terms, while the supplier needs predictable volume and growth." + ecommerce_anti_patterns: + - "Treating supplier negotiations as adversarial. Extracting maximum short-term price concessions degrades supplier willingness to prioritize your orders, invest in quality, or accommodate rush requests." + - "Failing to share demand forecasts with manufacturing partners. Information sharing creates cooperative surplus — suppliers who understand demand patterns can optimize production schedules, reducing both parties' costs." + ecommerce_example: "A DTC beauty brand approaches contract manufacturing negotiations cooperatively: instead of demanding a 10% price reduction, they offer a 3-year volume commitment (worth more to the manufacturer than a short-term discount) in exchange for priority production scheduling, 30% lower MOQs for new product testing, and net-60 payment terms. Both parties gain more value than pure price negotiation would produce." + benchmark_references: ["gross-margin", "days-of-inventory"] + + - skill: "competitive-negotiation" + category: "negotiation" + ecommerce_relevance: "moderate" + ecommerce_context: "Competitive negotiation tactics apply in specific e-commerce contexts: carrier rate negotiations (where alternatives exist and pricing is commodity), retail buyer negotiations (where power asymmetry favors the retailer), and distressed situations (negotiating with a supplier who has missed delivery deadlines or quality standards). In e-commerce, the most important competitive negotiation skill is BATNA development — having credible alternatives to every key relationship: multiple 3PL options, multiple carrier contracts, and multiple manufacturing sources." + ecommerce_anti_patterns: + - "Using competitive tactics with a sole-source supplier. Without a credible BATNA, competitive negotiation produces resentment without results." + - "Threatening to leave a retail partner without having alternative distribution. The threat must be credible to have leverage." + ecommerce_example: "A DTC brand negotiating carrier rates for the coming year uses competitive tactics: they obtain quotes from three carriers, share the best rate as an anchor, and negotiate with each carrier against the others. The competitive dynamic — each carrier knowing alternatives exist — produces a 15% average rate reduction, saving $180K annually on a $1.2M shipping budget." + benchmark_references: ["shipping-cost-pct", "fulfillment-cost-per-order"] + + # ───────────────────────────────────────────── + # THINKING (3 skills) + # ───────────────────────────────────────────── + + - skill: "enemies-of-clear-thinking" + category: "thinking" + ecommerce_relevance: "high" + ecommerce_context: "E-commerce founders face specific cognitive biases that distort decision-making. Sunk cost fallacy: continuing to invest in slow-moving inventory because money has already been spent on it. Survivorship bias: studying only successful DTC brands while ignoring the thousands that failed with similar strategies. Confirmation bias: interpreting early sales data as product-market fit when it may reflect paid acquisition rather than organic demand. Anchoring: fixating on a target price point (matching competitors) without calculating whether that price produces positive contribution margin. Recency bias: over-weighting last month's performance when making inventory decisions for 6 months ahead." + ecommerce_anti_patterns: + - "Holding dead inventory because of sunk cost. The purchase price is gone. The only question is: does the liquidation value exceed the carrying cost of holding it longer?" + - "Copying the strategy of a successful DTC brand without understanding the survivorship bias — for every Glossier, there are 500 beauty brands that executed similar playbooks and failed." + ecommerce_example: "A DTC founder holds $150K in slow-moving inventory (9 months of supply) because 'we already paid for it.' Sunk cost fallacy analysis reveals: the inventory occupies 40% of warehouse space ($3,000/month in rent), ties up $150K in capital that could earn 15% return if deployed in marketing, and risks further depreciation as the products approach trend obsolescence. The rational decision is to liquidate at 50% of cost and redeploy the capital." + benchmark_references: ["days-of-inventory", "inventory-turnover", "contribution-margin"] + + - skill: "evaluating-and-deciding" + category: "thinking" + ecommerce_relevance: "high" + ecommerce_context: "Evaluation and decision-making in e-commerce must account for the physical constraints that do not exist in software: inventory commits capital for months, manufacturing has lead times, shipping contracts lock in rates, and seasonal windows are finite. Decisions must be evaluated not just on expected value but on reversibility — a decision to commit to 50,000 units of a new product is far less reversible than a decision to test a new marketing channel. E-commerce decision-making should weight irreversibility, capital commitment, and time horizon alongside expected returns." + ecommerce_anti_patterns: + - "Making large inventory commitments based on projected demand without downside scenario modeling. The right framework is: 'If this product sells at 50% of forecast, what is the financial impact?'" + - "Applying software decision-making speed to physical product decisions. In software, you can deploy and revert in hours. In e-commerce, a bad inventory decision takes months to unwind." + ecommerce_example: "A brand evaluating whether to launch a new product line applies structured decision analysis: expected value calculation (40% probability of hitting forecast, 35% probability of 50% forecast, 25% probability of 150% forecast), irreversibility assessment (initial inventory commitment of $80K is partially recoverable through liquidation), time horizon (6-month payback at base case), and opportunity cost (the $80K could instead fund email marketing with a 90-day payback). The framework reveals that the new product launch is a higher-risk, higher-upside bet than the marketing investment." + benchmark_references: ["contribution-margin", "inventory-turnover", "gross-margin"] + + - skill: "defining-and-exploring-problems" + category: "thinking" + ecommerce_relevance: "high" + ecommerce_context: "E-commerce problems are frequently misdiagnosed because symptoms appear at a different point in the system than their root causes. Revenue declining? The problem might be traffic (marketing issue), conversion (site experience issue), AOV (pricing/assortment issue), or repeat purchase (product/retention issue). High return rate? The problem might be product quality, misleading photography, inaccurate sizing, or attracting wrong-fit customers through broad targeting. Proper problem definition in e-commerce requires decomposing aggregate metrics into their component drivers and tracing symptoms to root causes through the operational chain." + ecommerce_anti_patterns: + - "Jumping from symptom to solution without decomposition. 'Revenue is declining — let's increase ad spend' skips the crucial step of identifying whether the problem is traffic, conversion, AOV, or retention." + - "Treating operational symptoms as marketing problems. High return rates, slow shipping, and inventory stockouts are operational problems that marketing cannot solve." + ecommerce_example: "A DTC brand sees revenue decline 15% MoM. Rather than immediately increasing marketing spend, they decompose the metric: traffic is stable, conversion rate dropped from 2.5% to 1.8%, AOV is unchanged, repeat purchase rate is unchanged. The problem is conversion. Further decomposition: conversion dropped specifically on mobile devices after a site redesign. The root cause is a checkout flow regression on mobile. The fix costs $2,000 in developer time, not $50,000 in additional ad spend." + benchmark_references: ["conversion-rate", "return-rate", "revenue", "aov"] + + # ───────────────────────────────────────────── + # DECISIONS (2 skills) + # ───────────────────────────────────────────── + + - skill: "tough-decision-situations" + category: "decisions" + ecommerce_relevance: "high" + ecommerce_context: "E-commerce founders face category-specific tough decisions that require structured frameworks: discontinuing a product that has loyal customers but negative contribution margin; exiting Amazon when it represents 30%+ of revenue; firing a contract manufacturer mid-production cycle; choosing between growth (investing in marketing) and profitability (investing in margin improvement); and deciding when to absorb shipping cost increases versus passing them to customers. Each decision involves trade-offs between short-term revenue and long-term economics, and each has irreversible or costly-to-reverse components." + ecommerce_anti_patterns: + - "Avoiding the decision to exit an unprofitable channel because 'it might improve.' Channel economics rarely improve spontaneously. If Amazon is unprofitable today, it will be unprofitable in 6 months without fundamental changes." + - "Making tough decisions based on revenue impact alone without modeling contribution margin impact. Discontinuing a $500K revenue product line that has negative contribution margin improves the business." + ecommerce_example: "A DTC brand must decide whether to continue selling on Amazon (35% of revenue, 5% contribution margin) or exit and redirect investment to DTC (65% of revenue, 28% contribution margin). The structured decision framework quantifies: exiting Amazon loses $1.75M revenue but only $87.5K contribution. Redirecting the Amazon operations budget ($200K) to DTC marketing is projected to generate $600K in DTC revenue at $168K contribution margin. The decision is financially clear — exit Amazon — but emotionally difficult because it means shrinking headline revenue." + benchmark_references: ["contribution-margin", "cac", "ltv"] + + - skill: "choosing-and-executing" + category: "decisions" + ecommerce_relevance: "moderate" + ecommerce_context: "Execution in e-commerce is constrained by physical timelines that software businesses do not face: manufacturing lead times (8-20 weeks), shipping transit times (2-6 weeks for ocean freight), seasonal order deadlines (retailers place holiday orders in March-April), and inventory commitment points (once production is ordered, costs are locked). Choosing between strategic options must factor in these timelines — the best strategy chosen too late is worse than a good strategy chosen on time. E-commerce execution requires backward planning from market dates: if the product must be in customers' hands by November 15, and fulfillment needs 2 weeks, and shipping needs 4 weeks, and production needs 12 weeks, the commitment decision must be made by June." + ecommerce_anti_patterns: + - "Applying software development timelines to physical product launches. A 2-week sprint mentality does not work when the manufacturing cycle is 12 weeks." + - "Delaying decisions to gather more data when lead times make delay costly. In e-commerce, a 90% confidence decision made on time outperforms a 99% confidence decision made too late for the seasonal window." + ecommerce_example: "A brand must decide by March 15 whether to commit to a new product line for Q4 holiday season. The decision requires 16 weeks for manufacturing, 4 weeks for shipping, and 2 weeks for warehouse receiving. Backward planning from a November 1 in-stock date yields a March 15 commitment deadline. The brand uses rapid prototyping and small-batch testing (1,000 units) to gather demand signals before March 15, then commits to the full production run (25,000 units) based on early data rather than waiting for perfect data that would arrive after the deadline." + benchmark_references: ["days-of-inventory", "inventory-turnover"] + + # ───────────────────────────────────────────── + # LEADERSHIP (4 skills) + # ───────────────────────────────────────────── + + - skill: "delegation-and-empowerment" + category: "leadership" + ecommerce_relevance: "high" + ecommerce_context: "Delegation in e-commerce is complicated by the breadth of operational functions: product development, sourcing, manufacturing oversight, inventory planning, marketing, fulfillment, customer service, returns processing, and financial management. Many DTC founders start as generalists handling all functions and struggle to delegate because each function has category-specific expertise requirements. The critical delegation sequence in e-commerce typically follows: customer service first (highest volume, most codifiable), then fulfillment (outsource to 3PL), then marketing execution (hire specialist or agency), then inventory planning (requires systems and process), and finally strategy (last to delegate)." + ecommerce_anti_patterns: + - "Delegating customer service without documented processes and quality standards. In e-commerce, customer service directly affects reviews, NPS, and repeat purchase rate. Poor delegation here has measurable financial consequences." + - "Retaining fulfillment in-house as the company scales past 100 orders/day because 'no one does it as well as we do.' 3PLs exist specifically to do it better at scale." + ecommerce_example: "A DTC founder processing 200 orders/day delegates fulfillment to a 3PL, freeing 25 hours per week. They reinvest that time in product development and supplier relationships — activities that cannot be delegated to a third party and that generate 10x more value per hour than packing boxes." + benchmark_references: ["fulfillment-cost-per-order", "csat"] + + - skill: "leading-through-change" + category: "leadership" + ecommerce_relevance: "moderate" + ecommerce_context: "E-commerce change management centers on three recurring transitions: channel expansion (adding Amazon, wholesale, or retail to a DTC-only model), operational scaling (moving from founder-packed to 3PL or in-house warehouse), and strategic pivots (subscription model adoption, geographic expansion, category extension). Each change affects every team differently: channel expansion creates new roles (Amazon manager, wholesale account exec) while changing existing ones (marketing now spans multiple channels). Operational scaling professionalizes processes that were informal, which feels like loss of control to early employees." + ecommerce_anti_patterns: + - "Adding channels without investing in the team and systems required to support them. Amazon, wholesale, and DTC each require different skills, tools, and processes." + - "Changing fulfillment partners without a transition plan. 3PL transitions during peak season are one of the most common causes of e-commerce operational crises." + ecommerce_example: "A DTC brand adding wholesale distribution (Nordstrom, Anthropologie) must manage change across the organization: the product team must develop wholesale-specific packaging and assortment, marketing must shift from consumer to trade promotion, finance must handle wholesale payment terms (net-60-90), and operations must support EDI ordering and retailer compliance requirements. Each function experiences the change differently. Structured change management — not just an announcement — is required." + benchmark_references: ["revenue", "contribution-margin"] + + - skill: "focus-and-priority-management" + category: "leadership" + ecommerce_relevance: "high" + ecommerce_context: "Focus and priority management in e-commerce is uniquely challenging because the business operates across three simultaneous time horizons: immediate (today's orders must ship, today's ads must run, today's customer emails must be answered), medium-term (next season's inventory must be ordered, next quarter's marketing calendar must be planned), and long-term (next year's product development, new channel strategy, brand positioning). Founders who cannot operate across all three horizons simultaneously either neglect operations (brand suffers from poor execution) or neglect strategy (business becomes a lifestyle operation with no competitive moat)." + ecommerce_anti_patterns: + - "Living entirely in the immediate horizon. Processing orders, answering emails, and adjusting ads produces the illusion of productivity while the business has no strategic direction." + - "Living entirely in the long-term horizon. Building a 3-year vision while ignoring that fulfillment errors are running at 5% and customer service response time is 72 hours." + ecommerce_example: "A DTC founder structures their week across three horizons: Monday and Friday mornings for strategic work (product development, supplier diversification, channel evaluation), daily 30-minute check-ins for operational metrics (order volume, fulfillment accuracy, customer service queue), and Wednesday afternoons for medium-term planning (seasonal inventory orders, marketing calendar, hiring). The structure ensures no horizon is neglected." + benchmark_references: ["contribution-margin", "csat", "fulfillment-cost-per-order"] + + - skill: "learning-from-failure" + category: "leadership" + ecommerce_relevance: "high" + ecommerce_context: "E-commerce failures have distinctive patterns: product launch failures (new products that do not sell, leaving dead inventory), channel failures (entering Amazon or wholesale without adequate preparation), seasonal planning failures (under-stocking and missing peak demand, or over-stocking and discounting into oblivion post-season), and fulfillment failures (3PL transitions gone wrong, shipping delays during peak). Each failure type produces specific lessons. Critically, e-commerce failures have financial residue — failed inventory sits in a warehouse costing money, unlike a failed software feature that simply stops being maintained." + ecommerce_anti_patterns: + - "Refusing to liquidate failed inventory because it 'admits failure.' Holding dead inventory is compounding the failure, not avoiding it." + - "Attributing product launch failure to marketing execution when the product itself was not wanted. In e-commerce, the most common failure is product-market fit, not distribution." + ecommerce_example: "A DTC brand launches a premium clothing line that sells 20% of forecast in the first 90 days. Instead of doubling down on marketing (throwing good money after bad), they conduct a structured failure analysis: customer feedback reveals the fabric feels 'cheap' despite a premium price point. The learning: product quality must match price positioning. The brand writes down the remaining inventory, reformulates the line with superior materials, and relaunches six months later. The failed launch cost $120K but the learning prevented a $500K commitment to the flawed original product." + benchmark_references: ["inventory-turnover", "days-of-inventory", "return-rate"] diff --git a/plugins/foreman/content/industry-packs/e-commerce/e-commerce-templates.yaml b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-templates.yaml new file mode 100644 index 0000000..7722b98 --- /dev/null +++ b/plugins/foreman/content/industry-packs/e-commerce/e-commerce-templates.yaml @@ -0,0 +1,960 @@ +# E-Commerce Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for e-commerce companies. The output agent loads these +# rules when generating documents with the e-commerce industry pack active. +# +# E-commerce template adaptations reflect the physical product reality: +# unit economics are per-order (not per-subscription), investor materials +# must distinguish GMV from revenue and show cohort repeat purchase data, +# operational templates must address inventory planning, fulfillment, and +# seasonal preparation. Returns, shipping costs, and COGS are first-class +# fields throughout. +# +# Adaptation types: +# as-is — The template works without modification for e-commerce. +# modified — The template requires field changes, additional sections, or +# reframing for e-commerce context. + +pack_metadata: + sector: "e-commerce" + display_name: "E-Commerce" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce unit economics are fundamentally per-order, not per-subscription. The waterfall from gross revenue to contribution margin must include COGS, fulfillment, shipping, payment processing, and returns — each as explicit line items. Investors evaluate e-commerce unit economics as a variable-cost stack, not a recurring revenue model." + field_changes: + - field: "Revenue per unit" + sector_label: "Average Order Value (AOV)" + sector_guidance: "Report AOV net of discounts. Show AOV trend (3-month, 6-month, 12-month). Segment AOV by channel (DTC, Amazon, wholesale) if applicable." + - field: "Cost per unit" + sector_label: "Per-Order Cost Waterfall" + sector_guidance: "Present as a waterfall from AOV to contribution margin: AOV - COGS - Fulfillment Cost - Shipping Cost - Payment Processing Fee - Returns Cost = Contribution Margin. Show each component as both dollar amount and percentage of AOV." + - field: "Margin per unit" + sector_label: "Contribution Margin per Order" + sector_guidance: "Report both dollar amount and percentage. This is the true per-order economics after all variable costs. Target: >20% for institutional investment." + - field: "Lifetime value" + sector_label: "Customer Lifetime Value (LTV)" + sector_guidance: "Calculate as AOV x Gross Margin % x Purchase Frequency x Average Customer Lifespan. Alternatively: AOV x Gross Margin % / (1 - Repeat Purchase Rate). Disclose repeat rate assumption and observed customer lifespan." + - field: "Acquisition cost" + sector_label: "Customer Acquisition Cost (CAC)" + sector_guidance: "Report fully loaded CAC (all marketing spend, creative, agency fees, and allocated team time). Break out by channel: paid social, paid search, email, organic, influencer. Report blended and marginal CAC." + - field: "Unit economics ratio" + sector_label: "LTV:CAC Ratio" + sector_guidance: "Report the ratio and compare to the 3:1-5:1 benchmark for e-commerce. If below 3:1, explain the improvement trajectory (repeat rate increasing, COGS decreasing, or CAC declining)." + sections_to_add: + - section_name: "Per-Order Economics Waterfall" + placement: "before:Average Order Value (AOV)" + description: "Visual waterfall showing the contribution margin stack. This is the most important slide for e-commerce investors." + fields: + - "Gross Revenue per Order (AOV before discounts)" + - "Discounts & Promotions (% and $)" + - "Net Revenue per Order" + - "COGS (% and $)" + - "Gross Margin per Order" + - "Fulfillment Cost per Order" + - "Shipping Cost per Order" + - "Payment Processing Fee per Order" + - "Returns Cost per Order (return rate x handling cost)" + - "Contribution Margin per Order ($ and %)" + - section_name: "Repeat Purchase & Cohort Analysis" + placement: "after:LTV:CAC Ratio" + description: "E-commerce equivalent of SaaS cohort retention — measures repeat purchasing by acquisition cohort." + fields: + - "Repeat purchase rate by monthly cohort (3-month, 6-month, 12-month)" + - "Purchase frequency by cohort vintage" + - "LTV by cohort (are newer cohorts more or less valuable?)" + - "Channel-level cohort quality (which acquisition channels produce highest-LTV customers?)" + - section_name: "Channel Economics Comparison" + placement: "end" + description: "Per-order economics by sales channel — critical for omnichannel brands." + fields: + - "DTC website: AOV, COGS %, fulfillment %, shipping %, contribution margin %" + - "Amazon: AOV, COGS %, FBA fees %, Amazon advertising %, contribution margin %" + - "Wholesale: AOV, COGS %, trade discount %, co-op spend %, contribution margin %" + - "Other channels: contribution margin comparison" + sections_to_remove: [] + benchmark_references: ["aov", "cac", "ltv", "contribution-margin", "gross-margin", "fulfillment-cost-per-order", "shipping-cost-pct", "return-rate", "repeat-purchase-rate"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce investor updates must distinguish between GMV and net revenue, report contribution margin, and highlight repeat purchase trends — the metrics that e-commerce investors track monthly." + field_changes: + - field: "Financial highlights" + sector_label: "E-Commerce KPIs" + sector_guidance: "Report: Net Revenue (after returns and discounts), Contribution Margin %, Orders Shipped, AOV, Repeat Purchase Rate (trailing), LTV:CAC. Present as a table with current month, prior month, and trend." + - field: "Key metrics" + sector_label: "Operating Metrics" + sector_guidance: "Report: New Customers, Returning Customers, Conversion Rate, Return Rate, Email Revenue %, Inventory Turnover. Choose 4-5 most relevant to current company focus." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one quantified win: new product launch with sales data, repeat purchase rate improvement, contribution margin increase, or new channel launch results." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges. E-commerce investors respect transparency about supply chain disruptions, rising costs, inventory issues, and channel dependency. Include root cause and response plan." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific: introductions to specific retail buyers, supply chain experts, potential brand partners, or operational advisors." + sections_to_add: + - section_name: "Inventory & Cash Position" + placement: "after:E-Commerce KPIs" + description: "E-commerce investors need to see cash efficiency alongside revenue." + fields: + - "Cash balance (end of month)" + - "Inventory value on hand" + - "Days of inventory" + - "Monthly burn rate" + - "Months of runway (cash minus inventory commitments)" + sections_to_remove: [] + benchmark_references: ["revenue", "contribution-margin", "aov", "repeat-purchase-rate", "return-rate", "inventory-turnover"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce competitive analysis must address three distinct threat vectors: direct brand competitors, marketplace/private label threats (Amazon Basics), and channel competition (where customers can buy similar products). Pricing is transparently comparable." + field_changes: + - field: "Competitor overview" + sector_label: "Competitive Map" + sector_guidance: "Map competitors on a 2x2 matrix: X-axis = price positioning (value to premium), Y-axis = distribution breadth (DTC-only to omnichannel). Include Amazon private label, retailer private label, and direct DTC competitors." + - field: "Competitive advantages" + sector_label: "Brand Moat Analysis" + sector_guidance: "Assess defensibility along e-commerce-specific dimensions: brand recognition, product IP (patents, proprietary formulations), customer relationship (email list, loyalty program), supplier exclusivity, and review accumulation." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize: (1) Direct competitors — same category, similar positioning. (2) Amazon private label — Amazon entering the category with lower pricing. (3) Retailer private label — Target, Walmart launching store brands. (4) New DTC entrants — well-funded startups with aggressive CAC spending." + sections_to_add: + - section_name: "Price Comparison Matrix" + placement: "after:Threat Vectors" + description: "Transparent pricing comparison that acknowledges customer price visibility." + fields: + - "Price comparison by product category against top 5 competitors" + - "Amazon pricing for equivalent products" + - "Price-to-perceived-value analysis (justification for premium or value positioning)" + - section_name: "Review & Rating Comparison" + placement: "after:Price Comparison Matrix" + description: "Social proof competitive analysis — critical in e-commerce." + fields: + - "Average product rating vs. competitors (on own site, Amazon, Google Shopping)" + - "Review volume vs. competitors" + - "Review velocity (monthly new reviews) vs. competitors" + - "Sentiment analysis of competitor reviews (identifying competitor weaknesses)" + sections_to_remove: [] + benchmark_references: ["nps", "cac", "organic-traffic-pct"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce pitch decks must demonstrate per-order profitability, repeat purchase dynamics, and channel strategy. Investors have seen too many DTC brands that grow revenue with negative unit economics. The deck must prove the business works at the order level." + field_changes: + - field: "Market opportunity" + sector_label: "Market Opportunity" + sector_guidance: "Present TAM/SAM/SOM for the product category. Include: category size (NRF, eMarketer data), online penetration rate and growth, and the specific niche the brand targets. Bottom-up sizing: (target customer count) x (annual spend per customer)." + - field: "Business model" + sector_label: "E-Commerce Business Model" + sector_guidance: "Cover: channel mix (DTC, Amazon, wholesale), pricing strategy, gross margin, per-order contribution margin, and the repeat purchase engine. Show how the model improves with scale (declining fulfillment costs, improving repeat rate, brand-driven organic acquisition)." + - field: "Traction" + sector_label: "Traction & Growth Metrics" + sector_guidance: "Dedicated slide with: Revenue trajectory (monthly, 12-month view), Order count trend, AOV trend, Repeat purchase rate by cohort, and Channel mix evolution. Distinguish GMV from net revenue explicitly." + sections_to_add: + - section_name: "Per-Order Unit Economics Slide" + placement: "after:Traction & Growth Metrics" + description: "The most scrutinized slide in any e-commerce pitch. Must prove per-order profitability." + fields: + - "Per-order contribution margin waterfall (visual)" + - "LTV:CAC ratio with supporting data" + - "CAC payback in orders and months" + - "Gross margin % and trend" + - section_name: "Repeat Purchase & Cohort Slide" + placement: "after:Per-Order Unit Economics Slide" + description: "Proves that customers come back — the critical e-commerce investment thesis." + fields: + - "Cohort repeat purchase curves (monthly cohorts, 12-month view)" + - "Purchase frequency by cohort vintage" + - "Revenue from repeat customers as % of total (trend)" + - "Email and SMS list size and growth rate" + - section_name: "Supply Chain & Operations Slide" + placement: "after:Repeat Purchase & Cohort Slide" + description: "Addresses the operational risk that e-commerce investors evaluate." + fields: + - "Supplier diversification (number of suppliers, geographic spread)" + - "Fulfillment model (3PL, in-house, hybrid) and cost per order" + - "Inventory turnover and days of inventory" + - "Return rate and trend" + sections_to_remove: [] + benchmark_references: ["revenue", "aov", "contribution-margin", "ltv", "cac", "repeat-purchase-rate", "gross-margin", "inventory-turnover", "return-rate"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "An e-commerce strategic one-pager must anchor analysis in physical product dynamics: channel strategy, inventory efficiency, margin structure, and repeat purchase economics." + field_changes: + - field: "Strategic position" + sector_label: "E-Commerce Strategic Position" + sector_guidance: "Frame position in e-commerce terms: category leadership, brand moat, channel diversification, and supply chain resilience. Include positioning on the DTC-to-omnichannel spectrum." + - field: "Key metrics" + sector_label: "E-Commerce Health Metrics" + sector_guidance: "Core 6: Revenue + growth rate, Contribution Margin %, Repeat Purchase Rate, LTV:CAC, Inventory Turnover, Organic Traffic %. Compare each to category-specific benchmarks." + sections_to_add: + - section_name: "Revenue Lever Analysis" + placement: "end" + description: "Decomposition of the four e-commerce revenue levers with assessment of each." + fields: + - "Traffic: volume, trend, organic %, channel mix" + - "Conversion Rate: current, trend, category benchmark comparison" + - "AOV: current, trend, cross-sell/upsell effectiveness" + - "Repeat Purchase Rate: current, cohort trend, lifecycle program maturity" + - "Primary lever for next-stage growth" + sections_to_remove: [] + benchmark_references: ["revenue", "contribution-margin", "repeat-purchase-rate", "ltv", "cac", "inventory-turnover", "organic-traffic-pct"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce market sizing must account for online vs. offline penetration, category-specific dynamics, and channel addressability. Unlike SaaS, e-commerce TAMs must be grounded in consumer spending data." + field_changes: + - field: "Total addressable market" + sector_label: "TAM / SAM / SOM" + sector_guidance: "Use category spending data from NRF, eMarketer, or Euromonitor. TAM = total category spend. SAM = online-addressable spend in target segments. SOM = realistic capture based on brand positioning, channel reach, and competitive intensity. Include online penetration growth as a TAM tailwind." + - field: "Market dynamics" + sector_label: "Category Dynamics" + sector_guidance: "Address: online vs. offline migration rate, competitive density, Amazon's role in the category, price sensitivity, repurchase frequency, and seasonal patterns." + sections_to_add: + - section_name: "Channel Addressability" + placement: "after:TAM / SAM / SOM" + description: "Break down the market by channel to show where the opportunity lies." + fields: + - "DTC addressable market (consumers who buy directly from brands)" + - "Amazon/marketplace addressable market" + - "Wholesale/retail addressable market" + - "Social commerce addressable market (emerging)" + - section_name: "Consumer Trends" + placement: "end" + description: "Category-relevant consumer behavior trends." + fields: + - "Online penetration rate and growth trajectory" + - "DTC adoption trends in the category" + - "Sustainability and values-driven purchasing trends" + - "Subscription/auto-replenishment adoption in the category" + sections_to_remove: [] + benchmark_references: ["revenue", "aov"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce due diligence centers on inventory risk, supply chain reliability, unit economics verification, and return rate analysis — physical product risks that do not exist in SaaS." + field_changes: + - field: "Financial review" + sector_label: "E-Commerce Financial Verification" + sector_guidance: "Verify: net revenue calculation (after returns and discounts), COGS calculation (all product costs including packaging, duties, tariffs), contribution margin methodology, inventory valuation method, and channel-level profitability. Request access to Shopify/e-commerce platform data." + - field: "Operational review" + sector_label: "Supply Chain & Operations Review" + sector_guidance: "Review: supplier list and concentration, manufacturing agreements, 3PL contracts and SLAs, carrier agreements, inventory management systems, and returns processing. Request inventory aging report, fulfillment accuracy data, and customer service metrics." + sections_to_add: + - section_name: "Inventory Due Diligence" + placement: "after:Supply Chain & Operations Review" + description: "E-commerce-specific inventory risk assessment." + fields: + - "Inventory aging report (% of inventory >90 days, >180 days)" + - "Inventory valuation methodology and write-down history" + - "Supplier concentration risk (% from single supplier)" + - "Lead time reliability (actual vs. quoted lead times)" + - "Seasonal inventory commitments and markdown history" + - section_name: "Customer & Retention Due Diligence" + placement: "after:Inventory Due Diligence" + description: "Validation of repeat purchase and customer quality claims." + fields: + - "Cohort repeat purchase data (verify from platform data, not founder calculations)" + - "Return rate by category with reason codes" + - "Customer acquisition data by channel (verify from ad platform dashboards)" + - "Email/SMS list audit (subscriber count, engagement rate, revenue attribution)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "gross-margin", "return-rate", "inventory-turnover", "days-of-inventory", "repeat-purchase-rate"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not e-commerce-specific. Standard venture capital cap table formats apply." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce decisions frequently involve inventory commitments, channel strategy, and pricing — all of which have irreversible components and physical-product-specific risk factors." + field_changes: + - field: "Decision context" + sector_label: "Decision Context" + sector_guidance: "For inventory decisions: include lead time, MOQ, capital commitment, and sell-through scenario analysis. For channel decisions: include per-order economics by channel. For pricing decisions: include contribution margin impact modeling." + sections_to_add: + - section_name: "Inventory & Cash Impact" + placement: "end" + description: "Physical product decisions have inventory and cash flow implications that must be explicitly modeled." + fields: + - "Inventory commitment required ($)" + - "Cash flow timing (when is cash committed vs. when is revenue received)" + - "Downside scenario: if demand is 50% of forecast, what is the financial impact?" + - "Reversibility: can inventory be liquidated, returned, or repurposed if the decision fails?" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "inventory-turnover"] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce exit scenarios are governed by revenue multiples (lower than SaaS), brand value, and operational transferability. Acquirer categories differ from SaaS: strategic acquirers are larger brands or conglomerates (P&G, Unilever), category consolidators (Thrasio model), or retail partners." + field_changes: + - field: "Valuation methodology" + sector_label: "E-Commerce Valuation" + sector_guidance: "E-commerce brands are valued on revenue multiples (1-4x for most brands) or EBITDA multiples (8-15x for profitable brands). Report: revenue, EBITDA, growth rate, gross margin, and repeat purchase rate. Higher multiples are earned by brands with strong repeat purchase rates, brand moats, and IP." + - field: "Potential acquirers" + sector_label: "E-Commerce Acquirer Landscape" + sector_guidance: "Categorize: (1) Strategic acquirers — CPG conglomerates (P&G, Unilever, L'Oreal) seeking DTC capability. (2) Category aggregators — Amazon FBA aggregators (though the market has contracted). (3) Retail acquirers — retailers adding exclusive brands. (4) PE acquirers — private equity firms acquiring profitable brands." + sections_to_add: + - section_name: "Brand Value Assessment" + placement: "after:E-Commerce Acquirer Landscape" + description: "Brand intangibles that drive e-commerce acquisition premiums." + fields: + - "Brand awareness and recognition metrics" + - "Email/SMS list size and engagement (valued asset in e-commerce M&A)" + - "Social media following and engagement rates" + - "Product IP (patents, proprietary formulations, exclusive supplier agreements)" + - "Customer data assets and segmentation sophistication" + sections_to_remove: [] + benchmark_references: ["revenue", "gross-margin", "repeat-purchase-rate", "organic-traffic-pct"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce board reviews must cover the four revenue levers, inventory health, channel performance, and seasonal preparation — physical product concerns that do not appear in SaaS board packages." + field_changes: + - field: "Financial summary" + sector_label: "E-Commerce Financial Dashboard" + sector_guidance: "Present: Revenue (net of returns and discounts) vs. plan, Contribution Margin % vs. plan, Gross Margin trend, AOV trend, Inventory value and turnover, Cash position and runway. Compare each to plan and prior quarter." + - field: "Strategic priorities" + sector_label: "Quarterly Priorities & Progress" + sector_guidance: "Report against quarterly priorities with measurable outcomes. Include product launch results, channel expansion status, and operational improvement metrics." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: Supply chain risks (supplier disruption, lead time delays, tariff changes), Channel risks (Amazon policy changes, ad cost increases, platform dependency), Inventory risks (overstocking, stockouts, obsolescence), and Margin risks (COGS increases, shipping cost inflation)." + sections_to_add: + - section_name: "E-Commerce Metrics Summary" + placement: "before:E-Commerce Financial Dashboard" + description: "One-page e-commerce metrics dashboard for board review." + fields: + - "Revenue and growth rate (QoQ and YoY)" + - "Contribution Margin % (trend)" + - "Repeat Purchase Rate (trailing 12-month)" + - "AOV (trend)" + - "Conversion Rate" + - "Return Rate" + - "Inventory Turnover and Days of Inventory" + - "LTV:CAC ratio" + - section_name: "Channel Performance" + placement: "after:E-Commerce Financial Dashboard" + description: "Revenue and profitability by sales channel." + fields: + - "Channel revenue breakdown (DTC, Amazon, wholesale, other)" + - "Contribution margin by channel" + - "Channel growth rates" + - "Customer acquisition cost by channel" + - section_name: "Inventory & Supply Chain Health" + placement: "after:Channel Performance" + description: "Physical product operational health indicators." + fields: + - "Inventory aging (% of inventory >90 days)" + - "Stockout frequency on top 20 SKUs" + - "Supplier on-time delivery rate" + - "Fulfillment accuracy and speed" + - section_name: "Seasonal Preparation" + placement: "end" + description: "Forward-looking seasonal readiness assessment (particularly important in Q2-Q3 for holiday preparation)." + fields: + - "Inventory committed for upcoming peak season" + - "Fulfillment capacity plan vs. projected peak volume" + - "Marketing calendar and budget for seasonal campaigns" + - "Identified risks for the upcoming season" + sections_to_remove: [] + benchmark_references: ["revenue", "contribution-margin", "repeat-purchase-rate", "aov", "conversion-rate", "return-rate", "inventory-turnover", "days-of-inventory", "cac"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce board meetings should allocate time for supply chain and inventory health alongside commercial performance — topics that SaaS boards do not cover." + field_changes: + - field: "Agenda items" + sector_label: "E-Commerce Board Agenda" + sector_guidance: "Standard e-commerce board agenda: (1) Metrics review — 15 min (pre-read, discussion only). (2) Channel strategy or product line deep-dive — 25 min (rotate topic each meeting). (3) Supply chain and inventory health — 15 min. (4) Seasonal planning review — 10 min (adjust by quarter). (5) CEO asks — 10 min. (6) Executive session — 15 min. Total: 90 minutes." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce risk categories include physical product risks absent in software: supply chain disruption, inventory obsolescence, tariff/trade policy, seasonal concentration, and fulfillment failure." + field_changes: + - field: "Risk categories" + sector_label: "E-Commerce Risk Categories" + sector_guidance: "Include e-commerce-specific categories: (1) Supply chain risk — supplier concentration, manufacturing disruption, tariffs, lead time reliability. (2) Inventory risk — obsolescence, overstocking, seasonal markdown exposure. (3) Channel risk — Amazon dependency, platform policy changes, ad cost volatility. (4) Fulfillment risk — 3PL reliability, peak season capacity, shipping cost inflation. (5) Product risk — quality issues, recall exposure, return rate trends." + sections_to_add: + - section_name: "Supplier Concentration Analysis" + placement: "end" + description: "Supply chain risk assessment." + fields: + - "Percentage of COGS from top 1, 3, and 5 suppliers" + - "Geographic concentration of manufacturing" + - "Alternate supplier readiness for each critical component" + - "Lead time vulnerability (maximum production lead time for hero products)" + sections_to_remove: [] + benchmark_references: ["gross-margin", "inventory-turnover", "days-of-inventory"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce change initiatives often involve physical transitions — new fulfillment partner, new manufacturing source, new channel entry — that have longer timelines and higher operational risk than software changes." + field_changes: + - field: "Implementation plan" + sector_label: "Implementation Plan" + sector_guidance: "For operational changes (3PL transition, supplier change), include: parallel operation period, cutover plan with rollback options, inventory transition logistics, and customer communication plan. Physical transitions cannot be deployed and reverted like software." + sections_to_add: + - section_name: "Operational Transition Risk" + placement: "end" + description: "Assessment of physical-world transition risks." + fields: + - "Parallel operation period required" + - "Inventory in transit during transition" + - "Customer impact during transition (expected shipping delays, errors)" + - "Rollback plan if transition fails" + sections_to_remove: [] + benchmark_references: ["fulfillment-cost-per-order"] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce compensation must address the operational/creative split — warehouse and fulfillment roles alongside brand, marketing, and product roles." + field_changes: + - field: "Compensation benchmarks" + sector_label: "E-Commerce Compensation Benchmarks" + sector_guidance: "Benchmark by function: Marketing (performance marketing, brand, CRM), Operations (supply chain, fulfillment, logistics), Product (product development, merchandising), and Technology (e-commerce platform, data engineering). Use industry-specific comp data from DTC-focused recruiters and industry surveys." + sections_to_add: + - section_name: "Operations Compensation" + placement: "end" + description: "E-commerce-specific operational role compensation." + fields: + - "Warehouse/fulfillment staff compensation vs. local market" + - "Supply chain management compensation benchmarks" + - "Seasonal staffing plan and temporary labor costs" + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce compliance covers product safety, labeling, trade/tariff, consumer protection, and sales tax — a different regulatory landscape from SaaS." + field_changes: + - field: "Regulatory landscape" + sector_label: "E-Commerce Compliance Landscape" + sector_guidance: "Cover: product safety regulations (CPSC, FDA for ingestibles/cosmetics), labeling requirements (FTC, state-specific), trade policy and tariffs (Section 301, countervailing duties), sales tax nexus and compliance, environmental regulations (packaging waste, sustainability claims), and consumer protection (return policies, advertising claims)." + sections_to_add: + - section_name: "Trade Policy & Tariff Exposure" + placement: "end" + description: "E-commerce-specific trade compliance." + fields: + - "Tariff exposure by product category and source country" + - "Current tariff rate and pending changes" + - "Impact modeling of tariff increase scenarios on gross margin" + - "Supplier diversification plan to mitigate tariff risk" + sections_to_remove: [] + benchmark_references: ["gross-margin"] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "CEO succession planning follows standard corporate governance practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce action plans must connect to the four revenue levers and include operational feasibility within supply chain timelines." + field_changes: + - field: "Success metrics" + sector_label: "E-Commerce KPI Targets" + sector_guidance: "Define success using e-commerce metrics: conversion rate improvement, AOV increase, repeat purchase rate lift, contribution margin improvement, return rate reduction, or fulfillment cost decrease. Every action should connect to a measurable lever." + - field: "Timeline" + sector_label: "Timeline (with Lead Time Constraints)" + sector_guidance: "Account for physical timelines: manufacturing lead times, shipping transit, warehouse receiving, and seasonal deadlines. A product improvement action plan must work backward from these constraints." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["conversion-rate", "aov", "repeat-purchase-rate", "contribution-margin"] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce initiatives must include per-order economics impact, inventory requirements, and operational capacity implications." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected E-Commerce Impact" + sector_guidance: "Quantify impact on e-commerce metrics: revenue contribution, contribution margin impact, repeat purchase rate improvement, or operational efficiency gain. Include inventory capital required and timeline to revenue." + - field: "Resource requirements" + sector_label: "Resource Requirements" + sector_guidance: "Include: capital required (inventory, tooling, marketing), operational capacity impact (fulfillment, customer service), and supply chain lead time. E-commerce initiatives often require upfront capital before revenue begins." + sections_to_add: + - section_name: "Inventory & Capital Requirements" + placement: "after:Expected E-Commerce Impact" + description: "E-commerce initiatives typically require inventory investment." + fields: + - "Inventory capital required" + - "Minimum order quantities and lead times" + - "Timeline from capital commitment to first revenue" + - "Break-even volume (units/orders required to recover investment)" + sections_to_remove: [] + benchmark_references: ["contribution-margin", "inventory-turnover"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce project kickoffs must include supply chain and fulfillment stakeholders and account for physical timelines." + field_changes: + - field: "Success criteria" + sector_label: "Success Metrics and Measurement Plan" + sector_guidance: "Define 2-3 e-commerce metrics the project will impact. Include baseline, target, measurement method, and evaluation date. Common: conversion rate, AOV, repeat purchase rate, fulfillment cost, return rate reduction." + - field: "Stakeholders" + sector_label: "Stakeholders (Including Operations)" + sector_guidance: "E-commerce projects almost always involve operations stakeholders: fulfillment, supply chain, customer service. Include them from kickoff, not as an afterthought." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["conversion-rate", "aov", "return-rate"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce hiring requires specific competency assessments for roles unique to physical product businesses." + field_changes: + - field: "Required competencies" + sector_label: "E-Commerce-Specific Competencies" + sector_guidance: "For marketing roles: e-commerce performance marketing experience, email/SMS marketing, conversion optimization, and multi-channel attribution. For operations roles: supply chain management, 3PL management, inventory planning, and fulfillment optimization. For product roles: physical product development, supplier management, and merchandising. For finance roles: inventory accounting, contribution margin analysis, and cash flow management for product businesses." + sections_to_add: + - section_name: "Operational Competency Assessment" + placement: "end" + description: "E-commerce-specific operational skills evaluation." + fields: + - "Experience with e-commerce platforms (Shopify, BigCommerce, etc.)" + - "Experience at similar stage and scale" + - "Understanding of physical product unit economics" + - "Comfort with seasonal demand planning and operational scaling" + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce team health must assess the creative-operational dynamic and seasonal readiness." + field_changes: + - field: "Team dynamics assessment" + sector_label: "Team Dynamics Assessment" + sector_guidance: "Explicitly assess: marketing-operations alignment (are they planning together?), seasonal preparedness (is the team ready for peak?), and cross-functional communication quality." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce retrospectives often follow product launches, seasonal peaks, or operational transitions — events with physical-world consequences." + field_changes: + - field: "What happened" + sector_label: "What Happened (Quantified)" + sector_guidance: "For product launches: actual vs. forecast sell-through, return rate, customer feedback. For peak seasons: orders processed vs. capacity, fulfillment accuracy, shipping SLA compliance. For operational changes: transition timeline vs. plan, error rate during transition, customer impact." + sections_to_add: + - section_name: "Inventory & Fulfillment Retrospective" + placement: "end" + description: "Physical product-specific lessons learned." + fields: + - "Inventory accuracy: did we order the right amount?" + - "Fulfillment performance: did we ship on time and accurately?" + - "Customer impact: any delivery delays, errors, or service failures?" + - "What would we change about our forecasting and planning?" + sections_to_remove: [] + benchmark_references: ["fulfillment-cost-per-order", "return-rate"] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning structure is not materially different for e-commerce teams." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Culture and values documentation is not materially e-commerce-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is standard across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce incidents include physical-world events: fulfillment failures, stockouts, supplier quality issues, and shipping carrier disruptions. The postmortem must capture the downstream customer impact." + field_changes: + - field: "Impact assessment" + sector_label: "Impact Assessment" + sector_guidance: "Quantify: orders affected, customers impacted, revenue lost or delayed, return rate increase, negative reviews generated, and estimated long-term customer value lost (affected customers' expected LTV reduction)." + - field: "Root cause" + sector_label: "Root Cause (with Supply Chain Tracing)" + sector_guidance: "Trace the root cause through the supply chain: Was this a supplier issue, an inventory planning failure, a fulfillment error, a carrier failure, or a systems issue? Physical incidents often have root causes upstream of where the failure was observed." + sections_to_add: + - section_name: "Customer Recovery Actions" + placement: "end" + description: "How affected customers were recovered." + fields: + - "Proactive communication sent to affected customers" + - "Compensation offered (refund, credit, replacement, expedited shipping)" + - "Post-recovery NPS or CSAT measurement" + - "Repeat purchase rate of affected customers vs. unaffected (measure 60 days later)" + sections_to_remove: [] + benchmark_references: ["csat", "return-rate"] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Role descriptions follow standard formats. E-commerce-specific competencies are addressed in the hiring scorecard overlay." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is standard across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360-degree feedback structure is standard across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An e-commerce founder's weekly review must include operational metrics that SaaS founders do not track: inventory health, fulfillment performance, and supply chain status." + field_changes: + - field: "This week's metrics" + sector_label: "Weekly E-Commerce Dashboard" + sector_guidance: "Weekly metrics: Revenue (vs. plan), Orders shipped, Conversion rate, AOV, Return rate, Fulfillment accuracy, Customer service response time, Inventory status (stockouts, approaching-stockout SKUs). Compare each to prior week and trailing 4-week average." + - field: "Key decisions this week" + sector_label: "Key Decisions This Week" + sector_guidance: "Flag decisions with inventory or supply chain implications separately — these have longer lead times and higher irreversibility than marketing or product decisions." + sections_to_add: + - section_name: "Supply Chain Status" + placement: "after:Weekly E-Commerce Dashboard" + description: "Weekly supply chain health check." + fields: + - "Inbound shipments status (on time / delayed)" + - "SKUs approaching stockout (within 2 weeks of safety stock)" + - "Supplier issues or communications" + - "Inventory reorder decisions needed this week" + sections_to_remove: [] + benchmark_references: ["revenue", "conversion-rate", "aov", "return-rate", "fulfillment-cost-per-order"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce decisions carry physical consequences — inventory commitments, supplier agreements, channel launches — that should be explicitly tracked for learning." + field_changes: + - field: "Decision type" + sector_label: "Decision Type" + sector_guidance: "Categorize: Inventory decision, Channel decision, Pricing decision, Product decision, Supplier decision, Marketing decision, Operational decision. Inventory and supplier decisions deserve extra documentation because of their irreversibility." + sections_to_add: + - section_name: "Physical Consequence Tracking" + placement: "end" + description: "Track the physical-world outcomes of decisions." + fields: + - "Capital committed" + - "Lead time to measurable outcome" + - "Reversibility assessment (easy, difficult, irreversible)" + - "Actual outcome vs. expected (record 90 days after decision)" + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce annual planning must account for seasonal rhythms, inventory commitment timelines, and product development cycles that span months." + field_changes: + - field: "Year in review" + sector_label: "Year in Review" + sector_guidance: "Review the four levers: traffic growth, conversion rate trend, AOV trend, and repeat purchase rate by cohort. Assess: channel performance, product launch results, inventory efficiency (write-downs, stockouts), and operational improvements." + - field: "Next year plan" + sector_label: "Next Year Plan" + sector_guidance: "Plan by quarter with seasonal awareness: Q1 (post-holiday recovery, spring launch preparation), Q2 (spring/summer campaigns, holiday inventory commitments begin), Q3 (back-to-school, holiday inventory arrives, pre-peak operations prep), Q4 (peak season execution, year-end clearance)." + sections_to_add: + - section_name: "Seasonal Calendar" + placement: "after:Next Year Plan" + description: "12-month seasonal planning calendar with key deadlines." + fields: + - "Manufacturing commitment deadlines by product line" + - "Seasonal campaign launch dates" + - "Inventory arrival target dates" + - "Peak season staffing timeline" + - "Post-season clearance and markdown plan" + sections_to_remove: [] + benchmark_references: ["revenue", "contribution-margin", "repeat-purchase-rate", "inventory-turnover"] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Founder mental health assessment is important across all sectors and does not require e-commerce-specific adaptation." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is a personal exercise that is not materially e-commerce-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is standard across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce negotiations most commonly involve suppliers, carriers, 3PLs, and retail buyers — each with specific preparation requirements." + field_changes: + - field: "Counterparty analysis" + sector_label: "Counterparty Analysis" + sector_guidance: "For suppliers: understand their capacity utilization, other major clients, and dependency on your volume. For carriers: know your volume relative to their thresholds, seasonal patterns, and competitive quotes. For retail buyers: understand their category strategy, margin expectations, and promotional calendar." + - field: "BATNA" + sector_label: "BATNA" + sector_guidance: "For each negotiation, document: alternative suppliers (with lead times and MOQs), alternative carriers (with rate comparisons), or alternative retail channels. A negotiation without a credible BATNA should be preceded by BATNA development." + sections_to_add: + - section_name: "E-Commerce Negotiation Levers" + placement: "end" + description: "Beyond price: the negotiation dimensions specific to e-commerce." + fields: + - "Payment terms (net-30, net-60, prepayment discount)" + - "Minimum order quantities" + - "Lead time commitments" + - "Exclusivity provisions" + - "Volume-based pricing tiers" + - "Quality guarantee and return provisions" + sections_to_remove: [] + benchmark_references: ["gross-margin"] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Personal advisory board tracking is standard across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce stakeholder maps must include supply chain stakeholders — suppliers, 3PL partners, and carrier account managers — who are critical to business operations." + field_changes: + - field: "Stakeholder categories" + sector_label: "Stakeholder Categories" + sector_guidance: "Include e-commerce-specific categories: (1) Supply chain stakeholders — manufacturers, raw material suppliers, packaging suppliers. (2) Logistics stakeholders — 3PL partners, carrier account managers, returns processors. (3) Channel stakeholders — Amazon account manager, retail buyers, wholesale distributors. (4) Technology stakeholders — e-commerce platform, email/SMS platform, analytics tools." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce founders often need to develop operational and supply chain skills that are not intuitive for brand-oriented or technology-oriented founders." + field_changes: + - field: "Skills to develop" + sector_label: "Skills to Develop" + sector_guidance: "Common e-commerce skill gaps: supply chain management, inventory planning and demand forecasting, financial modeling for physical product businesses (COGS, contribution margin, cash conversion cycle), performance marketing (Meta, Google, TikTok), email/SMS marketing, carrier and 3PL negotiation, and product development (manufacturing, quality control, regulatory compliance)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce analysis reports should frame findings through the four revenue levers and include operational recommendations alongside strategic ones." + field_changes: + - field: "Key findings" + sector_label: "Key Findings" + sector_guidance: "Structure findings around the four revenue levers (traffic, conversion, AOV, repeat purchase) and the three margin components (COGS, fulfillment, shipping/returns). This decomposition ensures the analysis is actionable." + sections_to_add: + - section_name: "Revenue Lever Decomposition" + placement: "after:Key Findings" + description: "Analytical framework specific to e-commerce." + fields: + - "Traffic analysis: volume, sources, quality, trend" + - "Conversion analysis: rate, funnel drop-off points, device comparison" + - "AOV analysis: trend, product mix, cross-sell effectiveness" + - "Repeat purchase analysis: rate, frequency, lifecycle touchpoint effectiveness" + sections_to_remove: [] + benchmark_references: ["conversion-rate", "aov", "repeat-purchase-rate", "contribution-margin"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce proposals (to clients, partners, or investors) should lead with per-order economics and operational capability." + field_changes: + - field: "Value proposition" + sector_label: "Value Proposition" + sector_guidance: "For e-commerce proposals: lead with unit economics (per-order profitability), customer retention data (repeat purchase rate), and operational capability (fulfillment speed, accuracy, scalability)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["contribution-margin", "repeat-purchase-rate"] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce case studies should quantify results in the metrics that matter: revenue impact, conversion rate improvement, repeat purchase lift, or operational efficiency gain." + field_changes: + - field: "Results" + sector_label: "Results (Quantified)" + sector_guidance: "Quantify in e-commerce terms: revenue impact ($), conversion rate improvement (pp), AOV increase ($), repeat purchase rate lift (pp), return rate reduction (pp), contribution margin improvement (pp), or fulfillment cost reduction ($). Use before/after comparisons with specific time periods." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["conversion-rate", "aov", "repeat-purchase-rate", "contribution-margin"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce partnerships involve physical-world commitments: inventory allocations, fulfillment requirements, and co-marketing obligations." + field_changes: + - field: "Partnership terms" + sector_label: "Partnership Terms" + sector_guidance: "For retail/wholesale partnerships: include wholesale pricing, minimum order quantities, return policies, co-op marketing requirements, and EDI/logistics compliance. For brand collaborations: include production quantities, cost sharing, inventory risk allocation, and channel exclusivity." + sections_to_add: + - section_name: "Operational Requirements" + placement: "end" + description: "Physical-world partnership obligations." + fields: + - "Inventory commitment required" + - "Fulfillment and logistics requirements (EDI, labeling, packaging)" + - "Return handling terms" + - "Timeline for operational readiness" + sections_to_remove: [] + benchmark_references: ["gross-margin", "contribution-margin"] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "as-is" + adaptation_rationale: "Project status updates follow standard formats across sectors." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce SLAs must cover physical-world commitments: fulfillment speed, order accuracy, inventory availability, and return processing timelines." + field_changes: + - field: "Service commitments" + sector_label: "Service Commitments" + sector_guidance: "For 3PL/fulfillment SLAs: order processing time (target: same-day for orders placed before cutoff), shipping accuracy rate (target: >99%), inventory accuracy (target: >98%), return processing time (target: <48 hours), and peak season capacity commitments." + - field: "Remedies" + sector_label: "Remedies" + sector_guidance: "Include: credit for missed SLAs (e.g., per-order credit for late shipments), right to audit, and termination provisions tied to sustained SLA failure. For shipping: carrier guarantee provisions for late delivery." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["fulfillment-cost-per-order"] + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "E-commerce QBRs (with clients, retail partners, or key accounts) should review order volume, product performance, and fulfillment quality." + field_changes: + - field: "Performance review" + sector_label: "Performance Review" + sector_guidance: "For retail partner QBRs: sell-through rate by SKU, gross margin performance, return rate, inventory turns, and promotional effectiveness. For 3PL QBRs: SLA compliance, cost per order trend, accuracy rate, and peak season performance." + sections_to_add: + - section_name: "Product Performance by SKU" + placement: "after:Performance Review" + description: "SKU-level analysis for retail or wholesale partner reviews." + fields: + - "Top performing SKUs (revenue, margin, velocity)" + - "Underperforming SKUs (low sell-through, high returns)" + - "New product introduction results" + - "Recommended assortment adjustments for next quarter" + sections_to_remove: [] + benchmark_references: ["inventory-turnover", "return-rate", "gross-margin"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "as-is" + adaptation_rationale: "Onboarding welcome packet structure is standard. E-commerce-specific content is naturally incorporated through the specific relationship being onboarded." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] diff --git a/plugins/foreman/content/industry-packs/edtech/edtech-benchmarks.yaml b/plugins/foreman/content/industry-packs/edtech/edtech-benchmarks.yaml new file mode 100644 index 0000000..22a5aaa --- /dev/null +++ b/plugins/foreman/content/industry-packs/edtech/edtech-benchmarks.yaml @@ -0,0 +1,960 @@ +# EdTech Industry Pack — Benchmarks +# +# 24 EdTech-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing engagement, retention, +# and institutional adoption issues. +# +# EdTech's defining complexity: multi-stakeholder value chains. The buyer is rarely +# the user. K-12: district buys, teacher implements, student uses, parent evaluates. +# Higher Ed: institution buys, professor assigns, student uses. Corporate L&D: L&D +# team buys, employee uses, manager evaluates ROI. Every metric must be interpreted +# through this lens. +# +# Primary data sources: +# - HolonIQ Global EdTech reports (2023, 2024, 2025) +# - GSV Ventures EdTech market analysis (2023, 2024) +# - Reach Capital State of EdTech (2023, 2024) +# - EdSurge Research Reports (2023, 2024) +# - ISTE/LearnPlatform EdTech Evidence Reports (2023, 2024) +# - Coursera, Udemy, Duolingo, 2U S-1/10-K filings (2021-2025) +# - Instructure (Canvas) 10-K filings (2022-2024) +# - Learning Engineering research (Carnegie Learning, Schmidt Futures) +# - EDUCAUSE Horizon Reports (2023, 2024) +# - Tyton Partners and Brighteye Ventures analysis (2023, 2024) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among EdTech companies at the relevant stage. +# Benchmarks span K-12, higher ed, corporate L&D, and consumer EdTech. + +pack_metadata: + sector: "edtech" + display_name: "EdTech" + version: "1.0.0" + description: "Benchmark data for Education Technology companies spanning learner engagement, institutional adoption, content economics, retention, compliance, and efficacy metrics across K-12, higher education, corporate L&D, and consumer learning segments." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # ENGAGEMENT METRICS + # ───────────────────────────────────────────── + + - name: "Student/Learner Engagement Rate" + id: "learner-engagement-rate" + category: "product" + definition: "The percentage of registered or licensed learners who actively interact with content in a given period, measured through meaningful actions such as completing lessons, submitting assessments, or participating in discussions — not merely logging in." + formula: "(Learners performing at least one meaningful learning action in period / Total registered or licensed learners) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20%" + signal: "The product sits on devices or accounts unused. Institutional buyers notice shelf-ware and question renewal. Free content alternatives are winning the learner's attention." + below_average: + value: "20-35%" + signal: "Modest engagement suggests either poor onboarding, misaligned content, or implementation without teacher/trainer buy-in." + average: + value: "35-50%" + signal: "Acceptable for institutional products where not all licensed users are expected to be active simultaneously. Consumer products at this level have room for growth." + good: + value: "50-70%" + signal: "Strong engagement indicating the product has found its place in the learning workflow. Teachers or trainers are actively incorporating it." + excellent: + value: "> 70%" + signal: "Exceptional. The product is embedded in daily learning routines. Common only in products with adaptive or gamified experiences." + stage_notes: + seed: "Engagement rate is the primary validation metric. If a pilot group of 50-200 learners does not achieve 40%+ engagement, product-market fit is questionable." + series_a: "Engagement must be consistent across multiple institutions or customer cohorts, not just the pilot school or first adopter." + series_b_plus: "At scale, maintaining engagement above 50% while growing the user base is the central product challenge." + data_sources: + - source: "LearnPlatform EdTech Evidence Reports" + year: "2024" + - source: "Duolingo S-1 Filing (consumer benchmark)" + year: "2021" + related_metrics: ["daily-active-learners", "monthly-active-learners", "dau-mau-ratio"] + related_skills: ["balanced-scorecard", "net-promoter-score"] + caveats: "Engagement rate varies enormously by sub-sector. A corporate compliance training product with 90% engagement may simply have a mandate. Voluntary engagement is the meaningful measure." + + - name: "Course/Content Completion Rate" + id: "content-completion-rate" + category: "product" + definition: "The percentage of learners who finish a course, module, or learning pathway they started, measuring follow-through from enrollment to final assessment or credential." + formula: "(Learners completing the course or module / Learners who started the course or module) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10%" + signal: "Catastrophic for paid products. For MOOCs, this is unfortunately common but indicates the free model devalues commitment. For institutional products, signals a fundamental content or UX problem." + below_average: + value: "10-25%" + signal: "Typical for open MOOCs (Coursera/edX report 5-15% completion for free courses). Unacceptable for paid or institutionally assigned content." + average: + value: "25-50%" + signal: "Reasonable for self-paced consumer products. For assigned institutional content, still below where it should be." + good: + value: "50-75%" + signal: "Strong for any modality. For instructor-led or institutionally assigned content, this represents effective implementation." + excellent: + value: "> 75%" + signal: "Exceptional. Typically achievable only with instructor involvement, cohort-based learning, or strong adaptive pathways. Duolingo reports >80% for paid subscribers." + stage_notes: + seed: "Completion rate is a leading indicator of efficacy evidence. Without it, institutional sales conversations stall." + series_a: "Segment completion by learner type: self-paced vs. instructor-led, voluntary vs. assigned, free vs. paid. The gaps reveal product priorities." + series_b_plus: "Completion rate must be maintained as content library expands. Content breadth without completion depth is a vanity growth strategy." + data_sources: + - source: "Coursera 10-K filing" + year: "2024" + - source: "HolonIQ EdTech Impact Report" + year: "2024" + - source: "Duolingo 10-K filing" + year: "2024" + related_metrics: ["learner-engagement-rate", "learning-outcomes-improvement", "learner-retention-rate"] + related_skills: ["product-life-cycle", "systems-thinking"] + caveats: "Completion rate alone does not indicate learning. A learner can complete a course without retaining anything. Pair with learning outcomes improvement for a complete picture." + + - name: "Learning Outcomes Improvement" + id: "learning-outcomes-improvement" + category: "product" + definition: "The measurable improvement in learner knowledge, skills, or competency attributable to using the product, typically expressed as the percentage gain on pre/post assessments, standardized test improvement, or skill proficiency advancement." + formula: "(Post-assessment score - Pre-assessment score) / Pre-assessment score x 100, or effect size (Cohen's d) in controlled studies" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% improvement or Cohen's d < 0.1" + signal: "No meaningful efficacy. The product cannot demonstrate it improves learning, making institutional sales and renewal extremely difficult." + below_average: + value: "5-10% improvement or Cohen's d 0.1-0.2" + signal: "Marginal improvement that may not justify the cost and implementation burden. Buyers will question ROI." + average: + value: "10-20% improvement or Cohen's d 0.2-0.4" + signal: "Meaningful improvement. Sufficient for initial sales but not yet a compelling differentiator against alternatives." + good: + value: "20-35% improvement or Cohen's d 0.4-0.6" + signal: "Strong evidence of efficacy. This level of improvement justifies premium pricing and enables reference-based selling." + excellent: + value: "> 35% improvement or Cohen's d > 0.6" + signal: "Exceptional efficacy. Carnegie Learning and DreamBox have published results in this range for specific populations. This is the gold standard for EdTech evidence." + stage_notes: + seed: "Even a small, well-designed pilot with pre/post assessments provides credible efficacy data. Do not wait until scale to measure outcomes." + series_a: "Efficacy evidence from 3-5 institutions is a material fundraising asset. Investors in EdTech increasingly require outcome data, not just engagement data." + series_b_plus: "Third-party validation (ESSA Tier 2 or 3 evidence, peer-reviewed studies) becomes a competitive moat. Budget for independent research." + data_sources: + - source: "ISTE/LearnPlatform EdTech Evidence Reports" + year: "2024" + - source: "Learning Engineering research, Carnegie Learning published studies" + year: "2023" + - source: "Schmidt Futures efficacy framework" + year: "2023" + related_metrics: ["content-completion-rate", "efficacy-evidence-strength"] + related_skills: ["balanced-scorecard", "smart-goals"] + caveats: "Improvement percentages are highly dependent on the assessment instrument, population, and baseline. Effect sizes (Cohen's d) are more comparable across studies. Beware self-reported outcome data — institutional buyers increasingly demand third-party validation." + + - name: "Monthly Active Learners" + id: "monthly-active-learners" + category: "growth" + definition: "The number of unique learners who perform at least one meaningful learning action within a calendar month, serving as the primary scale metric for EdTech platforms." + formula: "Count of unique learner accounts with at least one learning action (not just login) in the month" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1,000 MAL at 12 months post-launch" + signal: "Insufficient traction for either consumer virality or institutional sales evidence." + below_average: + value: "1,000-10,000 MAL at 12 months" + signal: "Early traction. May represent a handful of institutional customers or a small consumer base. Enough for seed-stage fundraising if growth rate is strong." + average: + value: "10,000-100,000 MAL at 12 months" + signal: "Solid traction. For institutional products, suggests 10-50 customer accounts. For consumer, suggests emerging organic growth." + good: + value: "100,000-1M MAL at 12 months" + signal: "Strong product-market fit. Duolingo had ~1M MAU at Series A. This level supports Series A/B fundraising." + excellent: + value: "> 1M MAL at 12 months" + signal: "Breakout product. Typically requires consumer-grade virality or a major institutional distribution partnership." + stage_notes: + seed: "MAL is secondary to engagement quality. 500 highly engaged learners with strong outcomes beat 50,000 passive registrations." + series_a: "Investors look for MAL growth rate and cohort retention, not just the absolute number." + series_b_plus: "MAL must be contextualized by segment. Institutional MAL is more predictable; consumer MAL is more volatile." + data_sources: + - source: "Duolingo S-1 filing" + year: "2021" + - source: "Coursera 10-K filing" + year: "2024" + related_metrics: ["daily-active-learners", "dau-mau-ratio", "learner-engagement-rate"] + related_skills: ["growth-share-matrix", "product-life-cycle"] + caveats: "MAL for EdTech is inherently seasonal. Academic-calendar-dependent products see 30-60% MAL drops during summer and winter breaks. Report rolling averages or in-session MAL to avoid misleading trends." + + - name: "Daily Active Learners" + id: "daily-active-learners" + category: "growth" + definition: "The number of unique learners performing at least one meaningful learning action on a given day, measuring the product's ability to create daily learning habits." + formula: "Count of unique learner accounts with at least one learning action per day" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% of MAL" + signal: "The product is used sporadically. No daily habit has formed. For consumer products, this is a growth death sentence." + below_average: + value: "5-15% of MAL" + signal: "Infrequent use. Typical for products used only during class time or scheduled training sessions." + average: + value: "15-25% of MAL" + signal: "Moderate daily engagement. Common for products with both scheduled and voluntary usage." + good: + value: "25-40% of MAL" + signal: "Strong daily habit. The product has become part of the learner's routine beyond required usage." + excellent: + value: "> 40% of MAL" + signal: "Exceptional. Duolingo-caliber daily habit formation. Typically requires gamification, streaks, or strong intrinsic motivation design." + stage_notes: + seed: "DAL is the habit-formation metric. If early users do not return daily (or at the cadence the product expects), the retention model is flawed." + series_a: "DAL should be growing faster than MAL, indicating deepening engagement, not just broader reach." + series_b_plus: "DAL seasonality must be modeled and communicated to investors. A 50% DAL drop during summer is normal for K-12; it is a crisis for corporate L&D." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "HolonIQ EdTech market analysis" + year: "2024" + related_metrics: ["monthly-active-learners", "dau-mau-ratio", "learner-engagement-rate"] + related_skills: ["balanced-scorecard", "product-life-cycle"] + caveats: "DAL is most meaningful for consumer EdTech and supplemental learning products. For core instructional products used 2-3 times per week, a 'weekly active learner' metric may be more appropriate." + + - name: "DAU/MAU Ratio (Stickiness)" + id: "dau-mau-ratio" + category: "product" + definition: "The ratio of daily active learners to monthly active learners, measuring how frequently the average monthly user engages with the product — a direct indicator of habit formation and stickiness." + formula: "Daily Active Learners / Monthly Active Learners" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0.10" + signal: "Users visit once or twice per month. The product has not established a learning habit. Retention will erode." + below_average: + value: "0.10-0.15" + signal: "Low stickiness. Typical for reference tools used occasionally rather than products embedded in daily learning." + average: + value: "0.15-0.25" + signal: "Moderate stickiness. Common for institutional products used during school days or scheduled training." + good: + value: "0.25-0.40" + signal: "Strong stickiness. The product is part of regular learning routine. Good for both institutional and consumer EdTech." + excellent: + value: "> 0.40" + signal: "Exceptional. Duolingo consistently reports DAU/MAU above 0.40 for paid subscribers. This level indicates powerful habit loops." + stage_notes: + seed: "DAU/MAU above 0.20 in a seed-stage EdTech product is a strong PMF signal. It means learners are choosing to return." + series_a: "Compare DAU/MAU for voluntary usage vs. assigned/required usage. The gap reveals how much engagement is intrinsic." + series_b_plus: "DAU/MAU should be reported alongside seasonal adjustments. In-session DAU/MAU is the comparable metric." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "Reach Capital EdTech Metrics Framework" + year: "2023" + related_metrics: ["daily-active-learners", "monthly-active-learners", "learner-retention-rate"] + related_skills: ["net-promoter-score", "product-life-cycle"] + caveats: "DAU/MAU is fundamentally a consumer metric. For institutional EdTech products where usage is scheduled (e.g., 3x/week in class), a DAU/MAU of 0.15 may be structurally appropriate rather than weak." + + # ───────────────────────────────────────────── + # INSTITUTIONAL ADOPTION METRICS + # ───────────────────────────────────────────── + + - name: "Institutional Adoption Rate" + id: "institutional-adoption-rate" + category: "sales" + definition: "The percentage of target institutions (school districts, universities, or enterprises) that have adopted the product within a defined market, measuring market penetration at the organizational buyer level." + formula: "(Institutions using the product / Total addressable institutions in target segment) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1%" + signal: "Negligible market penetration. The product has not yet cracked institutional procurement barriers." + below_average: + value: "1-3%" + signal: "Early adoption. Enough customers to learn from but not yet demonstrating scalable institutional sales." + average: + value: "3-8%" + signal: "Meaningful adoption. In K-12, this might represent 500-1,000 districts. Sufficient for pattern recognition in institutional sales." + good: + value: "8-15%" + signal: "Strong institutional presence. Word-of-mouth among institutions begins to supplement direct sales." + excellent: + value: "> 15%" + signal: "Category leader. At this penetration, the product benefits from network effects — institutions adopt because peers already use it." + stage_notes: + seed: "Focus on 5-10 institutional pilots, not adoption rate. The learning from deep partnerships outweighs breadth." + series_a: "Adoption rate becomes meaningful only within a tightly defined segment — e.g., 'Title I elementary schools in urban districts' rather than 'all K-12 schools.'" + series_b_plus: "Expansion into adjacent segments (from elementary to middle school, from math to science) is the growth driver once core segment penetration exceeds 10%." + data_sources: + - source: "EdSurge Research: K-12 EdTech Procurement Trends" + year: "2024" + - source: "EDUCAUSE EdTech adoption surveys" + year: "2024" + related_metrics: ["teacher-adoption-rate", "time-to-institutional-sale", "institutional-acquisition-cost"] + related_skills: ["four-ps-marketing", "tipping-point"] + caveats: "Adoption rate is only meaningful when the denominator (addressable institutions) is precisely defined. A 10% adoption rate of 'all US schools' is a very different business than 10% of 'AP Chemistry teachers in schools with 1:1 device programs.'" + + - name: "Teacher/Instructor Adoption Rate" + id: "teacher-adoption-rate" + category: "product" + definition: "The percentage of teachers or instructors within an adopting institution who actively use the product, measuring the critical middle layer of the buyer-implementer-user chain." + formula: "(Teachers/instructors actively using the product / Total teachers/instructors at the institution with access) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "The institution bought it but teachers are not using it. This is the single most common failure mode in EdTech — procurement without implementation." + below_average: + value: "15-30%" + signal: "A handful of champions are using it. Without intervention, adoption will plateau and the contract will not renew." + average: + value: "30-50%" + signal: "Moderate adoption. Enough teachers to generate student engagement data, but the product has not become standard practice." + good: + value: "50-70%" + signal: "Strong adoption. The product is part of the institutional workflow. Renewal probability is high." + excellent: + value: "> 70%" + signal: "Exceptional. Teachers have made the product their own. This level of adoption generates organic expansion to other departments or grade levels." + stage_notes: + seed: "Teacher adoption is the gatekeeper metric. No teacher adoption means no student engagement means no efficacy evidence means no renewal." + series_a: "Measure teacher adoption velocity — how quickly do teachers activate after institutional purchase? If it takes more than one semester, the onboarding process is failing." + series_b_plus: "Build teacher success programs that mirror customer success in SaaS. Each school needs a champion with training and support." + data_sources: + - source: "LearnPlatform EdTech Evidence Reports" + year: "2024" + - source: "ISTE EdTech Implementation Studies" + year: "2023" + related_metrics: ["learner-engagement-rate", "institutional-adoption-rate", "institutional-churn-rate"] + related_skills: ["kotter-change-model", "cialdini-influence", "tipping-point"] + caveats: "Teacher adoption is heavily influenced by professional development support. Products that rely on 'self-serve' teacher onboarding consistently underperform those that invest in PD." + + # ───────────────────────────────────────────── + # SALES METRICS + # ───────────────────────────────────────────── + + - name: "Time to Institutional Sale" + id: "time-to-institutional-sale" + category: "sales" + definition: "The average number of days from first institutional contact to signed contract, measuring the length of the procurement cycle that dominates EdTech B2B sales." + formula: "Average(Contract signature date - First meaningful contact date) across closed deals" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 12 months" + signal: "Procurement cycle exceeds one school budget year. Deals slip across fiscal boundaries, creating revenue unpredictability and cash flow strain." + below_average: + value: "9-12 months" + signal: "Full academic-year procurement cycle. Common for large district or university deals but stressful for startup cash management." + average: + value: "6-9 months" + signal: "Standard for mid-size institutional sales. Allows one to two sales cycles per budget year." + good: + value: "3-6 months" + signal: "Efficient institutional sales cycle. Often achieved with strong pilot-to-purchase programs or school-level (vs. district-level) purchasing authority." + excellent: + value: "< 3 months" + signal: "Exceptional for institutional EdTech. Typically achievable only with low-dollar products purchased at the school/department level or with freemium-to-institutional conversion paths." + stage_notes: + seed: "Sales cycle length determines runway requirements. A 9-month sales cycle means seed capital must cover 18+ months (two full sales attempts)." + series_a: "Track sales cycle by entry point: teacher referral (shorter), RFP response (longer), conference lead (variable). This data shapes GTM strategy." + series_b_plus: "Reducing time to institutional sale is as valuable as increasing deal count. Invest in procurement facilitation: pre-completed security reviews, ready compliance documentation, flexible contract terms." + data_sources: + - source: "Tyton Partners EdTech Procurement Report" + year: "2024" + - source: "EdSurge K-12 EdTech Buying Survey" + year: "2023" + related_metrics: ["institutional-adoption-rate", "average-contract-value", "institutional-acquisition-cost"] + related_skills: ["delivering-the-deal", "scenario-planning"] + caveats: "Institutional sales cycles are calendar-dependent. K-12 budgets are typically approved May-July for the following school year. Missing the budget window pushes the deal by 12 months. Higher Ed procurement often follows fiscal years that differ from academic calendars." + + - name: "Average Contract Value (Institutional)" + id: "average-contract-value" + category: "sales" + definition: "The average annual value of institutional contracts, measuring the per-institution revenue that drives the unit economics of B2B EdTech." + formula: "Total institutional contract revenue (annual) / Number of active institutional contracts" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $2,000 ACV" + signal: "Micro-contracts that cannot justify institutional sales effort. At this ACV, self-serve or PLG is the only viable go-to-market." + below_average: + value: "$2,000-$10,000 ACV" + signal: "School-level purchases. Viable with inside sales but difficult to build a large sales team at this deal size." + average: + value: "$10,000-$50,000 ACV" + signal: "District-level or department-level contracts. The sweet spot for EdTech inside sales. Covers the cost of a direct sales motion." + good: + value: "$50,000-$200,000 ACV" + signal: "Large district or university-wide contracts. Justifies field sales, dedicated implementation support, and custom onboarding." + excellent: + value: "> $200,000 ACV" + signal: "Enterprise EdTech. State-level adoptions, large university systems, or Fortune 500 L&D contracts. Few deals but high revenue per deal." + stage_notes: + seed: "ACV determines the go-to-market model. Below $10K requires PLG or channel sales. Above $50K justifies direct sales. Match the team to the ACV." + series_a: "ACV expansion through multi-product bundles, additional grade levels, or campus-wide licensing is the primary growth lever." + series_b_plus: "Track ACV trend by cohort. If new cohort ACV is declining, the product may be moving downmarket or discounting to maintain growth." + data_sources: + - source: "GSV Ventures EdTech Market Map" + year: "2024" + - source: "Tyton Partners EdTech Company Analysis" + year: "2024" + related_metrics: ["institutional-acquisition-cost", "revenue-per-learner", "expansion-revenue-institutional"] + related_skills: ["four-ps-marketing", "business-model-canvas"] + caveats: "ACV in EdTech is heavily influenced by funding source. Title I, Title IV, ESSER (now expired), and state-level grants create purchasing power that varies by year and political cycle." + + - name: "Student Acquisition Cost" + id: "student-acquisition-cost" + category: "unit-economics" + definition: "The fully loaded cost of acquiring one new active learner, including marketing, sales, onboarding, and content creation costs allocated per learner." + formula: "Total acquisition-related costs in period / New active learners acquired in period" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $50 per learner (consumer) or > $200 per learner (institutional)" + signal: "Acquisition costs are unsustainable relative to EdTech revenue per learner. The economics cannot support growth." + below_average: + value: "$25-$50 (consumer) or $100-$200 (institutional)" + signal: "Expensive acquisition. Viable only with high retention and strong LTV." + average: + value: "$10-$25 (consumer) or $50-$100 (institutional)" + signal: "Manageable acquisition cost. Common for products with a mix of organic and paid growth." + good: + value: "$3-$10 (consumer) or $20-$50 (institutional)" + signal: "Efficient acquisition. Often achieved through institutional distribution (one sale reaches thousands of learners) or viral consumer mechanics." + excellent: + value: "< $3 (consumer) or < $20 (institutional)" + signal: "Exceptional efficiency. Duolingo's viral loop drives per-learner CAC near zero for organic users. Institutional products achieve this when district-wide deployments bring massive learner volume per contract." + stage_notes: + seed: "Per-learner acquisition cost matters less than per-institution cost at seed. Acquiring one district that deploys 10,000 learners is more efficient than acquiring 10,000 individual learners." + series_a: "Segment student acquisition cost by channel: institutional sale vs. teacher-led adoption vs. consumer organic vs. paid." + series_b_plus: "The student acquisition cost advantage of institutional distribution is EdTech's unique economics. A $50K district deal reaching 5,000 learners yields $10/learner CAC — impossible to replicate in consumer-only models." + data_sources: + - source: "Duolingo S-1 filing (consumer benchmarks)" + year: "2021" + - source: "Reach Capital EdTech unit economics analysis" + year: "2024" + related_metrics: ["institutional-acquisition-cost", "revenue-per-learner", "content-to-revenue-ratio"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "Student acquisition cost must account for the multi-step acquisition chain: acquire the institution, then onboard the teacher, then activate the student. Each step has its own cost. The total is often higher than startups project." + + - name: "Institutional Acquisition Cost" + id: "institutional-acquisition-cost" + category: "unit-economics" + definition: "The fully loaded cost of acquiring one new institutional customer (school, district, university, or enterprise), including sales salaries, marketing, travel, conference attendance, pilot support, and compliance documentation." + formula: "Total sales and marketing costs in period / New institutional customers acquired in period" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 1.5x ACV" + signal: "Institutional acquisition cost exceeds one year's contract value. The company loses money on every new customer in year one." + below_average: + value: "1.0-1.5x ACV" + signal: "Expensive but common for EdTech companies with long sales cycles and high-touch pilots. Sustainable only with strong renewal rates (>85%)." + average: + value: "0.6-1.0x ACV" + signal: "Healthy institutional acquisition economics. The company recovers CAC within the first year of the contract." + good: + value: "0.3-0.6x ACV" + signal: "Efficient acquisition. Often achieved through teacher-first adoption (bottom-up) that converts to institutional purchase (top-down)." + excellent: + value: "< 0.3x ACV" + signal: "Exceptional. Usually indicates strong inbound demand from word-of-mouth, conference presence, or teacher advocacy networks." + stage_notes: + seed: "Institutional CAC is artificially high at seed because the sales infrastructure (materials, compliance docs, case studies) is still being built." + series_a: "Compare institutional CAC across segments: small school vs. district vs. state. The differences determine where to focus the sales team." + series_b_plus: "Institutional CAC should decline as brand recognition, case studies, and customer references reduce the sales burden." + data_sources: + - source: "GSV Ventures EdTech operating metrics" + year: "2024" + - source: "2U 10-K filing (higher ed institutional CAC)" + year: "2023" + related_metrics: ["average-contract-value", "time-to-institutional-sale", "student-acquisition-cost"] + related_skills: ["four-ps-marketing", "business-model-canvas"] + caveats: "Conference attendance (ISTE, ASU+GSV, FETC, SXSWedu) is a significant and often underestimated component of institutional CAC in EdTech. A single conference booth can cost $15,000-$50,000." + + # ───────────────────────────────────────────── + # UNIT ECONOMICS + # ───────────────────────────────────────────── + + - name: "Revenue per Learner" + id: "revenue-per-learner" + category: "unit-economics" + definition: "The average annual revenue generated per active learner across all revenue streams (subscriptions, licensing, content, certifications, and advertising), measuring the monetization efficiency of the learner base." + formula: "Total annual revenue / Total active learners in period" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $2 per learner annually" + signal: "Ad-supported or freemium with minimal conversion. Requires massive scale to build a meaningful business." + below_average: + value: "$2-$10 per learner annually" + signal: "Low monetization. Common for EdTech products in price-sensitive markets (K-12, developing countries) or those competing with free alternatives." + average: + value: "$10-$50 per learner annually" + signal: "Moderate monetization. Typical for institutional products with per-student licensing. Consumer subscriptions (Duolingo Super) fall in this range." + good: + value: "$50-$200 per learner annually" + signal: "Strong monetization. Premium consumer subscriptions, corporate L&D platforms, and test prep services achieve this range." + excellent: + value: "> $200 per learner annually" + signal: "Premium positioning. Graduate education, professional certification, and high-stakes test prep command this level. Coursera Plus and 2U OPM programs operate here." + stage_notes: + seed: "Revenue per learner establishes the business model viability. Below $10/learner requires massive scale; above $100/learner requires demonstrated premium value." + series_a: "Track revenue per learner by segment and pricing tier. The distribution reveals pricing power and expansion opportunity." + series_b_plus: "Revenue per learner should increase over time through premium tier adoption, additional product usage, and credential purchases." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "Coursera 10-K filing" + year: "2024" + - source: "2U 10-K filing" + year: "2023" + related_metrics: ["student-acquisition-cost", "content-creation-cost", "content-to-revenue-ratio"] + related_skills: ["business-model-canvas", "four-ps-marketing"] + caveats: "Revenue per learner varies 100x between segments: a K-12 district license might yield $3/student while a professional certificate program yields $300/learner. Blended metrics are misleading — always segment." + + - name: "Content Creation Cost" + id: "content-creation-cost" + category: "unit-economics" + definition: "The average cost to produce one hour of learning content or one course module, including instructional design, subject matter expert time, media production, quality assurance, and platform integration." + formula: "Total content creation costs / Total hours of content (or modules) produced in period" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $50,000 per hour of content" + signal: "Production costs are at traditional courseware levels. Not sustainable for a startup that needs to scale its content library." + below_average: + value: "$20,000-$50,000 per hour" + signal: "High-quality production but expensive. Typical for video-heavy, professionally produced content (Coursera, MasterClass)." + average: + value: "$5,000-$20,000 per hour" + signal: "Balanced quality and cost. Common for a mix of instructor-created and platform-produced content." + good: + value: "$1,000-$5,000 per hour" + signal: "Efficient production. Achieved through templatized content creation, user-generated content, or AI-assisted authoring." + excellent: + value: "< $1,000 per hour" + signal: "Highly scalable content model. Typically involves significant user-generated or community-created content, adaptive content engines, or AI content generation." + stage_notes: + seed: "Content creation cost determines how quickly the library can reach critical mass. A $50,000/hour model is unviable at seed." + series_a: "The content creation cost advantage from AI tooling is a material investor pitch point in 2024-2026. Demonstrate the cost reduction." + series_b_plus: "Content creation should shift from fully custom to a mix of platform-created, user-generated, and AI-enhanced content." + data_sources: + - source: "Coursera S-1 filing (content economics)" + year: "2021" + - source: "HolonIQ EdTech content production analysis" + year: "2024" + related_metrics: ["content-to-revenue-ratio", "revenue-per-learner"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "Content creation cost varies enormously by modality: text-based adaptive content costs 1/10th of video production. The modality choice is a strategic decision that determines the entire cost structure." + + - name: "Content-to-Revenue Ratio" + id: "content-to-revenue-ratio" + category: "efficiency" + definition: "The ratio of cumulative content creation investment to annual revenue generated from that content, measuring how efficiently content investment converts to revenue." + formula: "Cumulative content creation costs / Annual revenue attributed to that content" + unit: "ratio" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 5x" + signal: "Massive content investment with insufficient monetization. The company is a content production house, not a technology business." + below_average: + value: "3-5x" + signal: "Content investment is recovering slowly. Acceptable only if content has long shelf life and the business is early-stage." + average: + value: "1.5-3x" + signal: "Reasonable content economics. Revenue will recover the content investment within 2-3 years." + good: + value: "0.5-1.5x" + signal: "Strong content leverage. Content pays for itself within the first year of deployment." + excellent: + value: "< 0.5x" + signal: "Exceptional content economics. Achieved by products that create content once and distribute to massive learner populations, or that leverage user-generated content." + stage_notes: + seed: "The content-to-revenue ratio will be poor at seed because content is being created before the full revenue base exists. Track the trajectory." + series_a: "Demonstrate that the ratio improves as the learner base grows — this is the content leverage story investors want to hear." + series_b_plus: "Content-to-revenue ratio should improve year-over-year as existing content generates recurring revenue without additional investment." + data_sources: + - source: "Coursera 10-K filing" + year: "2024" + - source: "HolonIQ EdTech business model analysis" + year: "2024" + related_metrics: ["content-creation-cost", "revenue-per-learner", "gross-margin"] + related_skills: ["balanced-scorecard", "growth-share-matrix"] + caveats: "Content shelf life varies dramatically. Medical education content needs annual updates; foundational math content may last a decade. The ratio must account for content depreciation." + + # ───────────────────────────────────────────── + # RETENTION METRICS + # ───────────────────────────────────────────── + + - name: "Learner Retention Rate (Monthly)" + id: "learner-retention-rate" + category: "retention" + definition: "The percentage of active learners from the previous month who remain active in the current month, measuring the product's ability to sustain learning engagement over time." + formula: "(Learners active in both month N and month N-1) / (Learners active in month N-1) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 30% monthly" + signal: "Catastrophic attrition. Two-thirds of learners leave each month. The product is failing to create sustained engagement." + below_average: + value: "30-50% monthly" + signal: "High attrition typical of open/free EdTech products. For paid products, this is unsustainable." + average: + value: "50-65% monthly" + signal: "Moderate retention. Common for consumer EdTech with mixed free and paid users. The retention curve must flatten to build a durable business." + good: + value: "65-80% monthly" + signal: "Strong retention. Duolingo reports ~73% Month 1 retention for paid subscribers. This level supports a viable subscription business." + excellent: + value: "> 80% monthly" + signal: "Exceptional retention. Typically achieved in institutionally assigned products where usage is expected, or in consumer products with powerful habit mechanics." + stage_notes: + seed: "Month 1 to Month 2 retention is the critical metric. If fewer than 40% of activated learners return in Month 2, the product has an engagement problem." + series_a: "Retention must be segmented: paid vs. free, self-directed vs. assigned, and by content type. The gaps reveal product priorities." + series_b_plus: "Long-term retention curves (Month 6, Month 12) determine LTV. If the curve never flattens, the business model is a funnel, not a flywheel." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "Reach Capital EdTech Metrics Framework" + year: "2023" + related_metrics: ["institutional-churn-rate", "learner-engagement-rate", "dau-mau-ratio"] + related_skills: ["net-promoter-score", "systems-thinking"] + caveats: "EdTech retention is fundamentally shaped by the academic calendar. Monthly retention measured across June-August (K-12) or December-January (higher ed) will plummet regardless of product quality. Report in-session retention separately." + + - name: "Institutional Churn Rate" + id: "institutional-churn-rate" + category: "retention" + definition: "The percentage of institutional customers (schools, districts, universities, or enterprises) that do not renew their contract in a given period, measuring the durability of the B2B revenue base." + formula: "(Institutional customers not renewing / Total institutional customers up for renewal in period) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 25% annual" + signal: "One in four institutions leaves each year. At this rate, the company must replace a quarter of its revenue base annually just to stay flat." + below_average: + value: "15-25% annual" + signal: "High churn driven by either poor implementation, efficacy concerns, or budget pressure. Renewal conversations are reactive, not proactive." + average: + value: "10-15% annual" + signal: "Moderate churn. Common for EdTech products competing for discretionary budget. Sustainable with strong new customer acquisition." + good: + value: "5-10% annual" + signal: "Strong retention. The product is embedded in institutional workflows. Instructure (Canvas) reports institutional churn in this range." + excellent: + value: "< 5% annual" + signal: "Exceptional. Near-permanent institutional adoption. Achieved when the product becomes standard infrastructure — the 'system of record' for learning." + stage_notes: + seed: "Institutional churn at seed is noisy — a single lost pilot can represent 50% churn. Focus on understanding why institutions stay or leave, not on the rate." + series_a: "Identify whether churn is driven by budget cuts (external, less controllable) or dissatisfaction (internal, addressable). The split determines strategy." + series_b_plus: "Institutional churn below 10% enables predictable revenue forecasting. Above 10%, the company is perpetually in growth-replacement mode." + data_sources: + - source: "Instructure (Canvas) 10-K filing" + year: "2024" + - source: "Tyton Partners EdTech retention analysis" + year: "2023" + related_metrics: ["teacher-adoption-rate", "learner-engagement-rate", "nps-segmented"] + related_skills: ["net-promoter-score", "systems-thinking", "balanced-scorecard"] + caveats: "Institutional churn in EdTech often occurs at renewal, which is annual. Unlike SaaS monthly churn, there is no early warning from payment failures. The warning signals are engagement data and teacher adoption metrics — monitor these proactively." + + - name: "NPS (Segmented: Learner / Teacher / Admin)" + id: "nps-segmented" + category: "product" + definition: "Net Promoter Score measured and reported separately for each stakeholder group — learners/students, teachers/instructors, and institutional administrators/buyers — because satisfaction and advocacy differ dramatically across these groups in EdTech." + formula: "(% Promoters - % Detractors) for each stakeholder segment, reported as three separate scores" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Any segment below 0" + signal: "Active detractors outnumber promoters in a stakeholder group. If the buyer segment (admin) is negative, renewal is at extreme risk. If the user segment (learner) is negative, engagement will collapse." + below_average: + value: "0-20 in any segment" + signal: "Neutral sentiment. No advocacy, no opposition. The product is tolerated, not valued." + average: + value: "20-40 across segments" + signal: "Moderately positive. Enough for stability but not enough for organic growth through referral." + good: + value: "40-60 across segments, with no segment below 25" + signal: "Strong and balanced satisfaction. Teachers recommending to peers, admins willing to expand, students engaged voluntarily." + excellent: + value: "> 60 across segments" + signal: "Exceptional. The product has genuine advocates at every level of the stakeholder chain. This drives organic institutional adoption." + stage_notes: + seed: "Measure NPS even in pilot. A 10-teacher pilot can reveal whether the teacher NPS will support broader adoption." + series_a: "The gap between segments is as important as the absolute score. Learner NPS 60, Teacher NPS 10 means teachers are the bottleneck." + series_b_plus: "Track NPS trends by segment over time. A declining teacher NPS while learner NPS rises may indicate the product is adding student-facing features at the expense of teacher tools." + data_sources: + - source: "EdSurge Teacher NPS Surveys" + year: "2024" + - source: "Reach Capital EdTech Metrics Framework" + year: "2023" + related_metrics: ["learner-engagement-rate", "teacher-adoption-rate", "institutional-churn-rate"] + related_skills: ["net-promoter-score", "systems-thinking"] + caveats: "NPS must be measured at the right moment for each segment. Learner NPS after course completion, not during onboarding. Teacher NPS mid-semester when they have formed opinions, not during back-to-school chaos. Admin NPS after receiving usage/outcome reports." + + # ───────────────────────────────────────────── + # CONVERSION & GROWTH METRICS + # ───────────────────────────────────────────── + + - name: "Free-to-Paid Conversion Rate" + id: "free-to-paid-conversion" + category: "growth" + definition: "The percentage of free or trial users who convert to a paid plan, critical for EdTech companies using freemium or free-trial models to overcome the education sector's expectation of free content." + formula: "(Users converting to paid / Total users on free or trial plan in period) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2%" + signal: "The free product is sufficient for most users. The paid offering lacks compelling differentiation. Common when competing with genuinely free alternatives (Khan Academy, YouTube)." + below_average: + value: "2-4%" + signal: "Modest conversion. Typical for consumer EdTech where willingness to pay for learning is low." + average: + value: "4-7%" + signal: "Acceptable conversion. Duolingo converts approximately 7-8% of MAU to paid subscribers. This is considered strong for consumer EdTech." + good: + value: "7-12%" + signal: "Strong conversion. The paid product delivers clear, differentiated value that free users want." + excellent: + value: "> 12%" + signal: "Exceptional. Typically achieved when the free product creates a clear gap (limited content, no certificates, restricted features) that paid resolves." + stage_notes: + seed: "Conversion rate validates willingness to pay — the most uncertain assumption in EdTech. Test pricing with real users before optimizing the funnel." + series_a: "Segment conversion by user type: students, teachers, professionals. The conversion drivers differ dramatically." + series_b_plus: "Conversion rate optimization (CRO) becomes a dedicated function. Small conversion improvements on a large free base create material revenue." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "Coursera 10-K filing" + year: "2024" + related_metrics: ["revenue-per-learner", "student-acquisition-cost", "learner-retention-rate"] + related_skills: ["four-ps-marketing", "cialdini-influence"] + caveats: "Free-to-paid conversion in EdTech must contend with a cultural expectation that education should be free or publicly funded. This is not a misconception — it is a market reality that shapes pricing strategy." + + # ───────────────────────────────────────────── + # EFFICACY & COMPLIANCE METRICS + # ───────────────────────────────────────────── + + - name: "Efficacy Evidence Strength" + id: "efficacy-evidence-strength" + category: "product" + definition: "A categorical assessment of the quality and rigor of evidence demonstrating that the product improves learning outcomes, rated against the ESSA (Every Student Succeeds Act) evidence tiers or equivalent research standards." + formula: "Qualitative rating: None | Anecdotal (testimonials only) | Correlational (usage-outcome correlation) | Quasi-Experimental (ESSA Tier 3) | Experimental (ESSA Tier 2 or 1, RCT-based)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "None or Anecdotal only" + signal: "No credible evidence of efficacy. Increasingly a dealbreaker for institutional buyers, especially districts spending federal funds." + below_average: + value: "Correlational evidence" + signal: "Usage correlates with improved outcomes, but causation is not established. Better than nothing but vulnerable to 'selection bias' critique." + average: + value: "Quasi-Experimental (ESSA Tier 3)" + signal: "A well-designed study with a comparison group, though not randomized. Sufficient for most institutional procurement processes." + good: + value: "Experimental (ESSA Tier 2)" + signal: "A randomized controlled trial or well-designed quasi-experiment demonstrating statistically significant positive outcomes. Strong competitive advantage." + excellent: + value: "Multiple Experimental studies (ESSA Tier 1)" + signal: "Multiple RCTs demonstrating consistent positive outcomes across diverse populations. The gold standard. Only a handful of EdTech products achieve this level." + stage_notes: + seed: "Design your pilot as a research study from day one. Pre/post assessments with a control group cost little extra but produce invaluable evidence." + series_a: "Invest in at least one quasi-experimental study. The ROI of a credible efficacy study in institutional sales far exceeds the cost ($50K-$150K)." + series_b_plus: "Commission independent third-party research. Self-conducted studies face credibility challenges. Partner with university research labs or organizations like NWEA, ISTE, or J-PAL." + data_sources: + - source: "ESSA Evidence Standards (US Department of Education)" + year: "2023" + - source: "LearnPlatform EdTech Evidence Standards" + year: "2024" + - source: "Schmidt Futures EdTech Efficacy Framework" + year: "2023" + related_metrics: ["learning-outcomes-improvement", "institutional-adoption-rate"] + related_skills: ["balanced-scorecard", "trust-equation"] + caveats: "Efficacy evidence is necessary but not sufficient for institutional sales. Evidence + ease of implementation + teacher support is the winning combination. Products with strong evidence but poor usability still fail." + + - name: "Accessibility Compliance Score" + id: "accessibility-compliance-score" + category: "efficiency" + definition: "A composite measure of the product's compliance with accessibility standards (WCAG 2.1 AA, Section 508, ADA), expressed as the percentage of audited criteria met, reflecting the legal and ethical requirement to serve all learners." + formula: "(Number of WCAG 2.1 AA criteria met / Total applicable WCAG 2.1 AA criteria) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 60%" + signal: "Significant accessibility gaps. The product excludes learners with disabilities and exposes institutional customers to legal risk under ADA/Section 508." + below_average: + value: "60-75%" + signal: "Partial compliance. Common issues: missing alt text, poor keyboard navigation, insufficient color contrast, inaccessible interactive elements." + average: + value: "75-85%" + signal: "Moderate compliance. Most critical accessibility barriers addressed, but edge cases and advanced interactive features remain problematic." + good: + value: "85-95%" + signal: "Strong compliance. The product is usable by learners with most disabilities. Minor issues remain in complex interactive content." + excellent: + value: "> 95%" + signal: "Exemplary accessibility. Proactive inclusive design. This level is a competitive differentiator in institutional sales — many districts now require VPAT/ACR documentation." + stage_notes: + seed: "Build accessibility into the product from the start. Retrofitting accessibility is 5-10x more expensive than designing for it initially." + series_a: "Commission a third-party accessibility audit and publish a Voluntary Product Accessibility Template (VPAT). Many institutional RFPs require it." + series_b_plus: "Accessibility becomes a competitive moat. Products that are fully accessible win deals in districts where competitors cannot compete." + data_sources: + - source: "ISTE Accessibility in EdTech Report" + year: "2024" + - source: "EDUCAUSE Accessibility Compliance Surveys" + year: "2023" + related_metrics: ["ferpa-coppa-compliance-status", "institutional-adoption-rate"] + related_skills: ["balanced-scorecard", "systems-thinking"] + caveats: "Accessibility compliance is a legal requirement for products used in public K-12 schools and federally funded institutions, not a nice-to-have. The number of accessibility-related lawsuits in EdTech has tripled since 2020." + + - name: "FERPA/COPPA Compliance Status" + id: "ferpa-coppa-compliance-status" + category: "efficiency" + definition: "A categorical assessment of the product's compliance with education-specific privacy regulations: FERPA (Family Educational Rights and Privacy Act) for student data protection and COPPA (Children's Online Privacy Protection Act) for products used by children under 13." + formula: "Qualitative rating: Non-Compliant | Partially Compliant | Self-Attested Compliant | Third-Party Verified | Certified (iKeepSafe, Student Privacy Pledge, or equivalent)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Non-Compliant or status unknown" + signal: "A dealbreaker for any institutional sale in the US. Districts are legally liable for the student data they share with vendors." + below_average: + value: "Partially Compliant" + signal: "Some data practices meet FERPA/COPPA requirements but gaps remain (e.g., data retention policies, parental consent mechanisms, data deletion procedures)." + average: + value: "Self-Attested Compliant" + signal: "The company has reviewed its practices against FERPA/COPPA and attests to compliance. No third-party validation. Accepted by many districts but not all." + good: + value: "Third-Party Verified" + signal: "An independent assessor has reviewed and verified compliance. This satisfies most institutional procurement requirements." + excellent: + value: "Certified (iKeepSafe, Student Privacy Pledge signatory, or state DPA signatory)" + signal: "Industry-recognized certification. Signing the Student Privacy Pledge and participating in state Data Privacy Agreements (e.g., SDPC National DPA) removes friction from institutional sales." + stage_notes: + seed: "Achieve at least self-attested compliance before the first institutional pilot. Non-compliance is a non-starter." + series_a: "Invest in third-party verification and sign the Student Privacy Pledge. The cost is minimal relative to the sales friction it removes." + series_b_plus: "Proactively participate in state DPA programs (the Student Data Privacy Consortium manages multi-state agreements). This pre-clears the product for districts across entire states." + data_sources: + - source: "Student Privacy Compass (Future of Privacy Forum)" + year: "2024" + - source: "CoSN/SDPC Data Privacy Agreement program" + year: "2024" + related_metrics: ["accessibility-compliance-score", "institutional-adoption-rate"] + related_skills: ["trust-equation", "balanced-scorecard"] + caveats: "FERPA/COPPA compliance is table stakes, not a differentiator. The absence of compliance kills deals; the presence of compliance merely permits them. State-level student privacy laws (California's SOPIPA, New York's Education Law 2-d) add requirements beyond federal standards." + + # ───────────────────────────────────────────── + # FINANCIAL METRICS + # ───────────────────────────────────────────── + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "Revenue minus cost of goods sold as a percentage of revenue, where EdTech COGS includes content hosting, content licensing/creation amortization, instructor compensation (for live instruction models), platform infrastructure, and learner support." + formula: "(Revenue - COGS) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "Services-heavy or instructor-dependent model consuming margins. The business operates more like a school or tutoring service than a technology company." + below_average: + value: "40-55%" + signal: "Moderate margins. Common for OPM (Online Program Management) models where instructor costs and revenue shares with universities are significant." + average: + value: "55-65%" + signal: "Acceptable margins. Content licensing, live instruction, or high-touch support reduce margins below pure software levels." + good: + value: "65-75%" + signal: "Strong margins. The product is primarily self-serve with scalable content delivery. Duolingo reports gross margins above 70%." + excellent: + value: "> 75%" + signal: "Software-like margins. Achieved by fully self-serve products with no content licensing costs and minimal support requirements." + stage_notes: + seed: "Gross margin at seed reveals the business model's long-term economics. If human instructors or expensive content licensing are in COGS, margins will not scale." + series_a: "Investors scrutinize EdTech gross margins because the range is enormous (30% for OPM to 80% for pure platform). Clearly classify COGS components." + series_b_plus: "Gross margin improvement is a growth lever. Automating support, reducing content creation costs with AI, and shifting from licensed to owned content all improve margins." + data_sources: + - source: "Duolingo 10-K filing" + year: "2024" + - source: "2U 10-K filing" + year: "2023" + - source: "Coursera 10-K filing" + year: "2024" + related_metrics: ["content-creation-cost", "content-to-revenue-ratio", "revenue-per-learner"] + related_skills: ["business-model-canvas", "balanced-scorecard"] + caveats: "EdTech gross margin varies by 50 percentage points depending on the business model. Pure platform (80%+) vs. content marketplace (60-70%) vs. OPM (30-50%) vs. live tutoring (20-40%). The model, not the execution, determines the margin band." + + - name: "Expansion Revenue (Institutional Upsell)" + id: "expansion-revenue-institutional" + category: "growth" + definition: "The additional revenue generated from existing institutional customers through expanded usage — additional grade levels, subjects, campuses, departments, or premium features — expressed as a percentage of beginning-of-period institutional revenue." + formula: "(Expansion revenue from existing institutions in period / Beginning-of-period institutional revenue) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% annual" + signal: "Institutions buy once and never expand. The product has a single use case with no growth path within the account." + below_average: + value: "5-10% annual" + signal: "Minimal expansion. Some accounts add users or features, but there is no systematic expansion motion." + average: + value: "10-20% annual" + signal: "Moderate expansion. Schools adding grade levels or departments. Universities expanding to new colleges. Enterprises adding divisions." + good: + value: "20-35% annual" + signal: "Strong expansion indicating the product becomes more valuable as usage deepens within the institution. Multi-product adoption or campus-wide licensing drives growth." + excellent: + value: "> 35% annual" + signal: "Exceptional land-and-expand execution. The initial deployment was a beachhead that led to institution-wide adoption." + stage_notes: + seed: "Design the product for expansion from day one. If the initial sale covers all possible usage, there is no upsell path." + series_a: "Expansion revenue from existing institutions is typically more efficient than new institutional acquisition. Build the expansion playbook." + series_b_plus: "Institutional expansion revenue should contribute 30-50% of total growth. If new customer acquisition is the only growth engine, the business model is fragile." + data_sources: + - source: "Instructure (Canvas) 10-K filing" + year: "2024" + - source: "GSV Ventures EdTech operating analysis" + year: "2024" + related_metrics: ["institutional-churn-rate", "average-contract-value", "teacher-adoption-rate"] + related_skills: ["business-model-canvas", "four-ps-marketing"] + caveats: "Expansion in EdTech is often tied to budget cycles — a school that wants to expand mid-year may not have budget until the next fiscal year. Build expansion into renewal conversations, not as a separate sales motion." diff --git a/plugins/foreman/content/industry-packs/edtech/edtech-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/edtech/edtech-diagnostic-rules.yaml new file mode 100644 index 0000000..54a4964 --- /dev/null +++ b/plugins/foreman/content/industry-packs/edtech/edtech-diagnostic-rules.yaml @@ -0,0 +1,727 @@ +# EdTech Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in an EdTech context. +# The diagnostic agent loads these rules when the EdTech industry pack is active. +# +# EdTech diagnostic complexity: every business problem has a multi-stakeholder +# dimension. Customer churn is institutional churn + teacher abandonment + learner +# attrition — three distinct failure modes with different root causes. Growth +# stalls may be product problems, procurement cycle problems, or policy problems. +# Pricing issues interact with budget constraints, funding source requirements, +# and the cultural expectation of free educational content. +# +# EdTech-specific diagnoses added across this file: +# - Buyer-user disconnect +# - Efficacy evidence gap +# - Procurement cycle mismatch +# - Teacher adoption failure +# - Student engagement collapse +# - Seasonal revenue cliff +# - Free content substitution threat +# - Accessibility compliance failure +# +# Adaptation types: +# as-is — The diagnostic works without modification for EdTech companies. +# enhanced — The diagnostic is relevant but benefits from additional EdTech-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for EdTech. + +pack_metadata: + sector: "edtech" + display_name: "EdTech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Churn in EdTech operates at three distinct levels that must be diagnosed separately: institutional churn (the buyer does not renew), teacher churn (the implementer stops using the product within a renewing institution), and learner churn (students disengage within an active classroom). Each level has different causes, different signals, and different remedies. The base diagnostic's customer-centric model must be expanded to address all three." + additional_triage_questions: + - question: "Is the churn occurring at the institutional level (contracts not renewing), the teacher level (teachers abandoning the product within renewing institutions), or the learner level (students disengaging within active classrooms)?" + purpose: "These three churn types have fundamentally different root causes. Institutional churn often reflects budget or policy changes. Teacher churn reflects implementation failure. Learner churn reflects product-market fit issues." + routing_impact: "Institutional churn routes to pricing-diagnosis and competitive-threat-diagnosis. Teacher churn routes to kotter-change-model and teacher adoption analysis. Learner churn routes to product-life-cycle and engagement optimization." + - question: "Is the churn concentrated at a specific point in the academic calendar — end of school year, end of semester, budget cycle boundary, or after state testing?" + purpose: "Calendar-correlated churn in EdTech may be structural (the product is supplemental and gets cut when budgets tighten) rather than a product quality issue." + routing_impact: "Calendar-boundary churn routes to scenario-planning for seasonal revenue management. Non-calendar churn routes to deeper product and implementation diagnosis." + - question: "What was the teacher adoption rate in churning institutions compared to retained institutions?" + purpose: "Teacher adoption is the strongest leading indicator of institutional renewal. Low teacher adoption within an institution almost always predicts churn, regardless of administrator satisfaction." + routing_impact: "Low teacher adoption in churning institutions routes to implementation process redesign and kotter-change-model for change management within customer organizations." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Teacher adoption failure driving institutional churn" + reason: "The most common EdTech churn pattern: the institution purchased the product, but teachers never adopted it. The product sat unused for a year, and the administrator cannot justify renewal for shelf-ware." + - diagnosis: "Budget-cycle-driven churn" + reason: "EdTech products purchased with one-time funding (ESSER, grants, Title I allocations) face structural churn when that funding expires. This is external and not solvable through product improvement." + less_likely: + - diagnosis: "Product quality failure" + reason: "Products that get purchased by institutions have passed a quality threshold. Churn is more often caused by implementation failure, teacher non-adoption, or budget constraints than by the product being bad." + edtech_specific_diagnoses: + - name: "Buyer-user disconnect churn" + description: "The institutional buyer purchased the product based on criteria (compliance, evidence, cost) that do not align with what teachers and students actually need (ease, time savings, engagement). The product checks the buyer's boxes but fails the classroom test." + symptoms: + - "High initial contract value but low teacher activation within 60 days" + - "Admin NPS positive but teacher NPS negative or unmeasured" + - "Product purchased through district-level RFP without teacher involvement in evaluation" + - "Support tickets dominated by 'how do I use this in my classroom?' questions" + routes_to_skills: ["business-model-canvas", "systems-thinking", "net-promoter-score"] + routes_to_templates: ["action-plan", "quarterly-business-review"] + - name: "Teacher adoption failure" + description: "The institutional purchase was completed but teachers were never adequately trained, supported, or motivated to integrate the product into their practice. The product exists on school devices but is not part of the teaching workflow." + symptoms: + - "Teacher login rate below 30% within first 90 days of deployment" + - "No professional development sessions conducted during implementation" + - "Teachers reporting that 'there was no time to learn the new tool'" + - "Usage concentrated in 2-3 champion teachers while others are inactive" + routes_to_skills: ["kotter-change-model", "cialdini-influence", "tipping-point"] + routes_to_templates: ["onboarding-welcome-packet", "action-plan"] + - name: "Seasonal revenue cliff" + description: "Revenue depends on funding sources with expiration dates (ESSER, annual grants, single-year budget allocations) or on academic-calendar-dependent usage that creates predictable annual churn risk at contract renewal." + symptoms: + - "Churn concentrated at fiscal year boundaries (June-August for K-12)" + - "Significant portion of contracts funded by ESSER or time-limited grants" + - "Renewal conversations revealing 'we do not have the budget this year'" + - "Revenue growth in years when new federal/state funding is announced, decline when it expires" + routes_to_skills: ["scenario-planning", "business-model-canvas"] + routes_to_templates: ["quarterly-strategic-review", "risk-assessment-brief"] + sector_red_flags: + - "Teacher adoption below 25% in institutions that churned — confirms that the purchase-implementation gap is the churn driver." + - "Churn correlated with ESSER fund expiration (2024) or specific grant cycle endings." + - "Institutional churn above 20% annual — unsustainable in an industry with 6-12 month sales cycles." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech growth stalls have characteristic patterns tied to the academic calendar, procurement cycles, and policy environment. A growth stall in September-November (peak adoption season) is a fundamentally different signal than a stall in February-April (mid-year lull). Growth may also stall because the company has saturated its initial market segment and the adjacent segments require different sales motions, content, or compliance credentials." + additional_triage_questions: + - question: "Is the growth stall occurring during the primary buying season (spring for budget approval, summer for deployment) or during the academic year?" + purpose: "A stall during buying season signals a go-to-market or competitive problem. A stall during the academic year may simply reflect the natural procurement rhythm." + routing_impact: "Buying-season stall routes to competitive-threat-diagnosis and four-ps-marketing. Off-season stall routes to seasonal-pattern analysis before escalating to strategic concerns." + - question: "Have you saturated your initial target segment (e.g., Title I elementary schools, community colleges, Fortune 500 L&D departments), and are you attempting to expand to an adjacent segment?" + purpose: "EdTech companies often build products perfect for one segment but struggle to adapt for adjacent segments that have different needs, budgets, and procurement processes." + routing_impact: "Segment saturation routes to blue-ocean-strategy and business-model-canvas for segment expansion strategy. Within-segment stall routes to competitive analysis and product improvement." + - question: "Has a policy change, funding expiration, or regulatory shift affected your market? Examples: ESSER fund expiration, state curriculum standard changes, testing mandate revisions." + purpose: "EdTech growth is uniquely vulnerable to policy changes that can add or remove billions in purchasing power overnight." + routing_impact: "Policy-driven stall routes to scenario-planning and swot-pest-analysis for environmental assessment and strategic response." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Procurement cycle mismatch" + reason: "EdTech companies accustomed to a specific procurement rhythm (e.g., spring budget approvals) may mistime their sales efforts, marketing, and product launches relative to when institutions actually make purchasing decisions." + - diagnosis: "Segment ceiling" + reason: "EdTech segments are finite — 14,000 US school districts, 4,000 degree-granting institutions, and a limited number of corporate L&D departments. Growth stalls when the accessible segment is saturated." + less_likely: + - diagnosis: "Market demand decline" + reason: "Demand for education and training is structurally durable. Growth stalls in EdTech are almost always execution, competition, or policy problems, not demand problems." + edtech_specific_diagnoses: + - name: "Procurement cycle mismatch" + description: "The company's sales, marketing, and product release cycles are misaligned with institutional procurement rhythms. Products launch when budgets are already allocated, marketing campaigns peak when procurement officers are unavailable, and sales efforts miss the budget approval window." + symptoms: + - "Pipeline strong in November but deals not closing until the following spring" + - "Conference season (winter/spring) generating leads that cannot convert until the next budget cycle" + - "Product releases in September when teachers need stability, not new features" + - "Revenue lumpy — concentrated in Q3 (Jun-Aug) with weak performance in Q1-Q2" + routes_to_skills: ["scenario-planning", "smart-goals", "strategic-thinking-and-alignment"] + routes_to_templates: ["quarterly-strategic-review", "action-plan"] + - name: "Free content substitution threat" + description: "Growth is stalling because free alternatives (Khan Academy, YouTube educational content, OpenStax, ChatGPT) are providing 'good enough' learning experiences for a growing portion of the target market. Willingness to pay is declining." + symptoms: + - "Win/loss analysis showing 'free alternative' as a growing loss reason" + - "Institutional buyers citing 'we can use Khan Academy for free' or 'teachers are using ChatGPT' in procurement discussions" + - "Consumer free-to-paid conversion declining" + - "Competitive differentiation increasingly centered on features rather than outcomes" + routes_to_skills: ["blue-ocean-strategy", "disruptive-innovation", "porters-five-forces"] + routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Growth stall coinciding with back-to-school season (August-October) — this is the highest-growth period for EdTech and a stall here indicates a serious problem." + - "Pipeline conversion rate declining while pipeline volume is stable — suggests the product is losing competitiveness." + - "New institutional customer acquisition declining while expansion revenue is flat — both growth engines are stalling simultaneously." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Product-market fit in EdTech is multi-dimensional: the product must fit three markets simultaneously — the buyer market (institutional procurement criteria), the implementer market (teacher needs and constraints), and the user market (learner engagement and outcomes). A product can have strong PMF with students but fail because teachers will not adopt it, or strong PMF with administrators but fail because students will not engage. True EdTech PMF requires alignment across all three." + additional_triage_questions: + - question: "For which stakeholder group is product-market fit strongest — the institutional buyer, the teacher/implementer, or the learner/user? Where is it weakest?" + purpose: "Identifying the weakest stakeholder link focuses improvement effort. Most EdTech products have PMF with one group and fail with another." + routing_impact: "Weak buyer PMF routes to evidence-building, compliance work, and institutional sales process improvement. Weak teacher PMF routes to UX improvement, PD design, and implementation support. Weak learner PMF routes to product redesign, content quality, and engagement mechanics." + - question: "Does the product demonstrate measurable learning improvement — and can you prove it with data?" + purpose: "EdTech PMF cannot be claimed without efficacy evidence. A product that engages without improving learning does not have EdTech PMF — it has entertainment-market fit." + routing_impact: "No efficacy evidence routes to learning-outcomes study design and efficacy-evidence-strength improvement before further growth investment. Evidence exists routes to evidence-amplification in sales and marketing." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "PMF exists for one stakeholder but not the other two" + reason: "EdTech's multi-stakeholder structure means partial PMF is the most common state — the product works for students but teachers find it burdensome, or administrators love the data but students are bored." + - diagnosis: "PMF exists but implementation quality determines whether it manifests" + reason: "Many EdTech products have latent PMF — they work when implemented well. The problem is not the product but the gap between purchase and effective deployment." + less_likely: + - diagnosis: "Market does not want this product" + reason: "If the product is being purchased by institutions, there is demand. The question is usually not 'is there demand?' but 'is the product delivering on the promise that created the demand?'" + edtech_specific_diagnoses: + - name: "Efficacy evidence gap" + description: "The product may be effective, but there is no credible evidence to demonstrate it. Without efficacy evidence, institutional buyers cannot justify the purchase, grant applications cannot cite the product, and competitive differentiation rests on features rather than outcomes." + symptoms: + - "Institutional sales cycles extending because buyers request efficacy data that does not exist" + - "No pre/post assessment data collected during pilot deployments" + - "Product marketing emphasizes engagement metrics and testimonials rather than learning outcomes" + - "Competitors with evidence winning deals despite inferior product quality" + routes_to_skills: ["balanced-scorecard", "smart-goals", "trust-equation"] + routes_to_templates: ["strategic-analysis-one-pager", "new-initiative-brief"] + sector_red_flags: + - "Retention curve that diverges by stakeholder: students retain but teachers do not, or teachers retain but students churn within the first month." + - "No measurable learning outcome improvement after 6+ months of usage — engagement without outcomes is not EdTech PMF." + - "PMF dependent on a single champion teacher or administrator — when that person leaves, the product fails at that institution." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "EdTech pricing is constrained by forces absent from other sectors: institutional budgets tied to government funding cycles, the cultural expectation that education should be free or publicly funded, competition from genuinely free alternatives (Khan Academy, OER, ChatGPT), and the complex interaction between funding source restrictions and contract structure. The base pricing diagnostic must account for these unique constraints." + additional_triage_questions: + - question: "What funding sources do your institutional customers typically use to purchase your product — general budget, Title I, Title IV-A, ESSER (now expired), state grants, or other?" + purpose: "Funding source determines budget size, spending restrictions, purchase timing, and renewal likelihood. A product funded by a one-time grant has structural renewal risk." + routing_impact: "Grant-funded purchases route to diversification strategy and multi-year commitment structuring. General-budget purchases route to standard pricing optimization." + - question: "How does your pricing compare to the free alternative that most closely competes — and what premium does your product justify?" + purpose: "Every paid EdTech product must articulate why it is worth paying for when free alternatives exist. The premium justification determines pricing power." + routing_impact: "Weak premium justification routes to blue-ocean-strategy for differentiation. Strong premium routes to pricing optimization within the justified range." + - question: "Is your pricing per-student, per-teacher, per-school, per-district, or usage-based — and does this align with how institutions budget for education technology?" + purpose: "Pricing unit alignment with budgeting processes reduces procurement friction. Per-student pricing aligns with Title I per-pupil allocations; per-school pricing aligns with school improvement budgets." + routing_impact: "Misaligned pricing unit routes to restructuring that matches institutional budget categories." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Pricing ceiling set by free alternatives" + reason: "The existence of Khan Academy, YouTube, OpenStax, and ChatGPT as free educational content sets a pricing ceiling that constrains every EdTech product." + - diagnosis: "Pricing-funding mismatch" + reason: "Products priced above the threshold that requires school board approval (typically $25K-$50K) but without the sales infrastructure for board presentations face a dead zone." + less_likely: + - diagnosis: "Over-pricing relative to perceived value" + reason: "EdTech products are more often under-priced (due to the free-content expectation) than over-priced. Products that demonstrate ROI can command premium pricing." + edtech_specific_diagnoses: + - name: "Budget threshold dead zone" + description: "The product is priced above the school principal's discretionary purchasing authority (typically $2K-$5K) but below the threshold that justifies a district-level sales process with dedicated resources. This pricing no-man's-land is too expensive for impulse purchase but too small for enterprise sales." + symptoms: + - "Deals requiring multiple approval layers despite modest contract value" + - "Sales cycle length disproportionate to deal size" + - "Teachers wanting the product but unable to purchase because it exceeds their classroom budget" + - "District-level procurement officers deprioritizing the evaluation because the deal is 'too small' for their attention" + routes_to_skills: ["four-ps-marketing", "business-model-canvas"] + routes_to_templates: ["unit-economics-snapshot", "decision-rationale-memo"] + sector_red_flags: + - "Pricing unchanged for more than two academic years in a market where free AI alternatives are rapidly improving." + - "Revenue per learner declining quarter-over-quarter — a sign of downward pricing pressure or adverse selection toward lower-budget institutions." + - "Win/loss analysis showing 'budget' as the primary loss reason in more than 40% of losses — may indicate either overpricing or misalignment with available funding sources." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech fundraising has sector-specific dynamics: a smaller pool of specialized investors (GSV Ventures, Reach Capital, Owl Ventures, NewSchools Venture Fund, Learn Capital), sector-specific benchmarks (efficacy evidence matters alongside financial metrics), and unique narrative requirements (impact story alongside business story). The diagnostic must surface these EdTech-specific fundraising dimensions." + additional_triage_questions: + - question: "Can you demonstrate learning outcomes improvement with data — and is this data from a credible study design (not just testimonials)?" + purpose: "EdTech investors increasingly require efficacy evidence as a gating criterion. A product without outcome data is a harder fundraise regardless of financial metrics." + routing_impact: "No efficacy data routes to efficacy study design before fundraising. Efficacy data exists routes to storytelling and evidence presentation in the fundraising deck." + - question: "Is your revenue mix institutional (B2B to schools/universities/enterprises) or consumer (B2C to individual learners/parents) — and can you articulate why your chosen model is right for your market?" + purpose: "EdTech investors evaluate institutional and consumer models with very different benchmarks. Institutional: ACV, sales cycle, institutional retention. Consumer: CAC, free-to-paid conversion, learner retention." + routing_impact: "Institutional model routes to institutional metric presentation. Consumer model routes to consumer unit economics. Hybrid routes to clear articulation of how both models interact." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Narrative-metrics disconnect" + reason: "EdTech founders often lead with the mission story while investors need the business story. Alternatively, founders present metrics without connecting them to the educational impact that differentiates EdTech from generic SaaS." + - diagnosis: "Wrong investor pool" + reason: "EdTech founders pitching generalist SaaS investors face skepticism about market size, margins, and sales cycles. Pitching EdTech-specialized investors who understand the sector's unique dynamics is a more efficient path." + less_likely: + - diagnosis: "Market too small" + reason: "Global EdTech spending exceeds $300B annually. The 'market too small' objection usually means the company has not articulated the expansion path from its initial niche." + edtech_specific_diagnoses: + - name: "Impact-revenue tension in fundraising narrative" + description: "The founder cannot reconcile the mission-driven educational impact story with the venture-scale financial return story. The pitch oscillates between 'we are saving education' and 'we are building a $1B company' without connecting the two." + symptoms: + - "Investors expressing interest in the mission but skepticism about the business model" + - "Impact investors finding the product too commercial; venture investors finding it too impact-focused" + - "Fundraising deck heavy on student testimonials but light on unit economics" + - "Pitch meetings ending with 'we love what you are doing but we do not see the path to venture-scale returns'" + routes_to_skills: ["story-structure-and-arc", "business-model-canvas", "strategic-thinking-and-alignment"] + routes_to_templates: ["fundraising-deck-outline", "market-opportunity-summary"] + sector_red_flags: + - "Fundraising without efficacy evidence in a sector where investors increasingly require it." + - "Pitching only generalist VCs when EdTech-specialized investors exist and are more likely to understand and fund the model." + - "Revenue dependent on a single funding source (e.g., ESSER) that is expiring — investors will flag concentration risk." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech revenue has structural characteristics that the base diagnostic must account for: extreme seasonality (K-12 revenue concentrates in August-October for new contracts), funding-source dependency (federal and state education funding fluctuates with political cycles), and the split between institutional and consumer revenue streams that follow completely different dynamics." + additional_triage_questions: + - question: "What percentage of your revenue comes from institutional contracts versus consumer subscriptions, and how does each segment trend?" + purpose: "Institutional and consumer revenue have opposite seasonal patterns, different growth drivers, and different margin profiles. Blending them masks problems." + routing_impact: "Institutional revenue decline routes to sales pipeline and institutional retention analysis. Consumer revenue decline routes to product engagement and conversion optimization." + - question: "What percentage of institutional revenue is funded by time-limited sources (grants, ESSER, one-time allocations) versus recurring budget lines?" + purpose: "Time-limited funding creates a structural revenue cliff. Revenue that appears stable may be built on a foundation that expires." + routing_impact: "High grant-funded percentage routes to diversification strategy and customer retention planning for the funding transition." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Seasonal revenue concentration" + reason: "EdTech revenue is inherently seasonal. Companies that do not manage cash flow around the academic calendar face liquidity crises during off-peak months." + - diagnosis: "Funding-source concentration" + reason: "Revenue dependent on a single government program or funding stream is structurally fragile, regardless of current growth rate." + less_likely: + - diagnosis: "Product-based revenue decline" + reason: "If the product metrics (engagement, outcomes) are stable, revenue decline is more likely caused by external factors (budget cuts, policy changes, competition) than product quality." + edtech_specific_diagnoses: + - name: "Post-pandemic funding cliff" + description: "Revenue grew during 2020-2024 as ESSER and pandemic-era emergency education funding flooded the market. With ESSER funds expired and education budgets returning to pre-pandemic levels, revenue contracts as institutional customers funded by one-time allocations cannot renew." + symptoms: + - "Revenue plateau or decline beginning 2024-2025" + - "High percentage of institutional customers originally acquired during 2020-2023" + - "Renewal rate declining despite stable product quality and engagement" + - "Customer conversations revealing 'the grant ended' as the non-renewal reason" + routes_to_skills: ["scenario-planning", "business-model-canvas", "systems-thinking"] + routes_to_templates: ["quarterly-strategic-review", "risk-assessment-brief"] + sector_red_flags: + - "Revenue growing but the percentage funded by expiring sources increasing — a hidden revenue cliff approaching." + - "Revenue growth entirely from new customer acquisition with flat expansion revenue from existing institutions." + - "Revenue concentrated in a single school year quarter (e.g., 60%+ in Q3) without cash management to cover lean quarters." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech competitive dynamics include threats unique to the sector: free content platforms (Khan Academy, YouTube), general-purpose AI (ChatGPT as a free tutor), open educational resources (OER), and publishers expanding into technology. The competitive landscape also includes the 'threat of non-adoption' — institutions choosing to use no EdTech product at all." + additional_triage_questions: + - question: "Is the competitive threat from a direct EdTech competitor, a free alternative (Khan Academy, YouTube, OER), a general-purpose AI tool (ChatGPT, Gemini), a publisher expanding into technology (Pearson, McGraw-Hill), or institutional non-adoption?" + purpose: "Each threat type requires a different strategic response. Direct competitors require differentiation. Free alternatives require premium justification. AI requires value-beyond-content. Publishers require ecosystem strategy. Non-adoption requires demand creation." + routing_impact: "Direct competitor routes to porters-five-forces. Free alternative routes to blue-ocean-strategy. AI threat routes to ai-vision-and-strategy. Publisher routes to coalition-and-partnership-games. Non-adoption routes to tipping-point." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "AI-driven disruption" + reason: "AI tutoring and content generation represent the most immediate and significant competitive threat to EdTech products that primarily deliver content or assessment. ChatGPT can explain any concept; AI can generate any quiz. Products whose value is content delivery are at existential risk." + - diagnosis: "Free content substitution" + reason: "The availability of high-quality free educational content (Khan Academy covers K-12 math and science; YouTube has millions of educational videos; OER covers higher ed textbooks) creates a permanent competitive threat for paid content products." + less_likely: + - diagnosis: "Price-based competitive displacement" + reason: "EdTech institutional buyers rarely switch products based on price alone. Switching costs (teacher training, curriculum alignment, data migration) are high relative to price differences." + edtech_specific_diagnoses: + - name: "AI commoditization of core value" + description: "General-purpose AI tools (ChatGPT, Claude, Gemini) now perform the product's core function — content delivery, question answering, assessment generation, or tutoring — at near-zero cost. The product's value proposition has been commoditized not by a competitor but by a horizontal technology platform." + symptoms: + - "Teachers reporting they use ChatGPT instead of the product for specific tasks" + - "Student engagement declining as learners find AI alternatives" + - "Prospects in sales pipeline asking 'why not just use ChatGPT for this?'" + - "Free-to-paid conversion declining in consumer segment" + routes_to_skills: ["ai-vision-and-strategy", "disruptive-innovation", "blue-ocean-strategy"] + routes_to_templates: ["competitive-landscape-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Win/loss analysis showing 'free alternative' or 'AI tool' as a growing loss reason." + - "A major publisher (Pearson, McGraw-Hill) announcing a technology product that overlaps with your core offering." + - "Declining teacher adoption in a category where teachers are discovering AI-based alternatives." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech strategic drift manifests as trying to serve too many segments (K-12 and higher ed and corporate), too many subjects (math and reading and science), or too many stakeholders (building for teachers while selling to administrators while engaging students). The multi-stakeholder nature of EdTech makes drift tempting — every stakeholder has legitimate demands." + additional_triage_questions: + - question: "Are you building features for all three stakeholders (buyer, implementer, user) simultaneously, and if so, are you making conscious trade-offs about which stakeholder gets priority in the current phase?" + purpose: "Attempting to please all stakeholders equally results in a product that serves none well. Strategic clarity requires explicit stakeholder prioritization." + routing_impact: "No clear prioritization routes to business-model-canvas for stakeholder strategy and defining-and-exploring-problems for priority clarification." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Multi-segment drift" + reason: "EdTech companies frequently drift from their initial segment (e.g., K-5 math) into adjacent segments (K-8, then K-12, then higher ed) without building the differentiated product, sales, and support for each." + less_likely: + - diagnosis: "Market-driven strategic shift" + reason: "More often, EdTech drift is opportunity-chasing (a big higher-ed deal, a corporate L&D request) rather than strategic response to market changes." + edtech_specific_diagnoses: + - name: "Stakeholder whiplash" + description: "The roadmap alternates between serving buyer needs (admin dashboards, compliance reports) and user needs (engagement features, gamification) and implementer needs (lesson planning tools, grade integration) without a coherent multi-stakeholder product strategy." + symptoms: + - "Product roadmap changing priority stakeholder each quarter" + - "No single stakeholder group rating the product above 7/10" + - "Engineering team confused about who the product is for" + - "Each new institutional customer conversation pulling the product in a different direction" + routes_to_skills: ["business-model-canvas", "systems-thinking", "strategic-thinking-and-alignment"] + routes_to_templates: ["strategic-analysis-one-pager", "decision-rationale-memo"] + sector_red_flags: + - "Product serving K-12, higher ed, and corporate with a single product and shared engineering team — each segment has different needs." + - "Go-to-market strategy changing more than once per academic year without corresponding data to justify the shift." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech team dysfunction has a characteristic pattern driven by the two-culture challenge: education professionals (instructional designers, former teachers, curriculum specialists) and technology professionals (engineers, product managers, growth marketers) often struggle to collaborate. They speak different languages, value different outcomes, and operate at different speeds." + additional_triage_questions: + - question: "Is there tension between the education/content team and the technology/product team — specifically, does the education team feel the product prioritizes engagement metrics over learning outcomes, or does the tech team feel the education team resists innovation?" + purpose: "The education-technology tension is the most common and most damaging team dysfunction in EdTech. It leads to products that are either pedagogically strong but poorly designed, or beautifully designed but pedagogically hollow." + routing_impact: "Education-technology misalignment routes to organisational-culture and cooperative-negotiation for team integration processes." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Education-technology cultural divide" + reason: "EdTech companies must integrate two professional cultures with different values, vocabularies, and working styles. The seam between these cultures is where dysfunction most commonly appears." + less_likely: + - diagnosis: "Individual performance issues" + reason: "What appears as individual underperformance often reflects a systemic culture clash. The former teacher turned product manager and the engineer who has never been in a classroom may both be excellent at their core skills but unable to collaborate effectively." + edtech_specific_diagnoses: + - name: "Education-technology integration failure" + description: "The instructional design team and the engineering team operate as separate entities with minimal cross-functional collaboration. Content is created without technical constraints in mind; features are built without pedagogical guidance. The result is a product that is neither pedagogically excellent nor technically polished." + symptoms: + - "Content team creating materials that engineering cannot implement within the platform's constraints" + - "Engineering team building features that the education team says have no learning value" + - "Product decisions requiring escalation to the CEO because the two teams cannot agree" + - "Former teachers leaving because they feel their expertise is not valued; engineers leaving because they feel the pace is too slow" + routes_to_skills: ["organisational-culture", "trust-equation", "tuckman-team-stages"] + routes_to_templates: ["team-health-check", "culture-values-document"] + sector_red_flags: + - "Instructional designer attrition above 30% annually — a sign that the education team feels marginalized." + - "Product releases that the education team was not consulted on — a symptom of engineering-dominated culture." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech co-founder conflict often mirrors the education-technology cultural divide: one co-founder comes from education (teacher, professor, school administrator) and the other from technology (engineering, product, startup). Their conflict centers on mission versus metrics, pedagogical rigor versus product velocity, and evidence-based approaches versus startup experimentation." + additional_triage_questions: + - question: "Does the conflict center on product direction (education quality vs. growth features), go-to-market (institutional sales vs. consumer growth), audience prioritization (which segment to focus on), or the role of efficacy evidence (invest now vs. later)?" + purpose: "EdTech co-founder conflicts cluster around these four issues, each requiring different resolution approaches." + routing_impact: "Product direction conflicts route to balanced-scorecard for multi-dimensional goal alignment. GTM conflicts route to data-driven segment analysis. Evidence investment conflicts route to scenario-planning for ROI of research." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Mission-metrics tension between education-background and technology-background co-founders" + reason: "The educator co-founder may resist growth tactics that compromise pedagogical integrity. The technologist co-founder may view educational rigor as a speed constraint." + less_likely: + - diagnosis: "Fundamental vision misalignment" + reason: "EdTech co-founders typically share a vision for educational impact. The conflict is about method and priority, not destination." + edtech_specific_diagnoses: + - name: "Pedagogy-versus-product velocity tension" + description: "The education-background co-founder insists on rigorous instructional design, evidence-based content development, and slow iteration based on learning science. The technology-background co-founder pushes for rapid shipping, A/B testing, and growth hacking. Both approaches have merit; the inability to integrate them creates paralysis." + symptoms: + - "Product releases delayed by content review cycles that the engineering team views as excessive" + - "Co-founders presenting conflicting priorities to the board" + - "Education team and engineering team developing separate roadmaps" + - "The education co-founder feeling steamrolled by 'tech bro culture'; the tech co-founder feeling constrained by 'academic pace'" + routes_to_skills: ["cooperative-negotiation", "balanced-scorecard", "evaluating-and-deciding"] + routes_to_templates: ["decision-journal", "quarterly-strategic-review"] + sector_red_flags: + - "Co-founders communicating about product decisions through intermediaries rather than directly." + - "Key hires (head of content, VP Engineering) aligned with one co-founder and adversarial toward the other." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech market entry is constrained by procurement barriers (compliance requirements, state adoption lists, institutional evaluation cycles), segment-specific requirements (K-12, higher ed, and corporate L&D are effectively different markets), and the need for efficacy evidence before institutional buyers will commit." + additional_triage_questions: + - question: "Which specific segment are you entering — K-12 (which grade band? which subject? public or private?), higher education (undergraduate, graduate, continuing ed?), or corporate L&D (which industry? which training type?) — and have you validated demand within that specific segment?" + purpose: "EdTech is not one market. Each segment has different buyers, different procurement processes, different compliance requirements, and different competitive landscapes." + routing_impact: "Broad segment targeting ('K-12') routes to segment narrowing exercise. Specific segment targeting with validation routes to go-to-market execution." + - question: "Do you have the compliance infrastructure required for your target segment — FERPA/COPPA for K-12, accessibility compliance for public institutions, data privacy certification for all segments?" + purpose: "Compliance is a prerequisite for market entry in institutional EdTech, not a post-launch optimization." + routing_impact: "Missing compliance routes to compliance-first development before any institutional sales effort." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Entering a segment without the compliance prerequisites" + reason: "EdTech companies from consumer or corporate backgrounds frequently underestimate K-12 compliance requirements (FERPA, COPPA, state DPAs) and lose months when institutional buyers flag non-compliance." + - diagnosis: "Broad targeting in a segment-specific market" + reason: "A product for 'K-12 math' without specifying grade band, standards alignment, and student population is too broad to achieve PMF." + less_likely: + - diagnosis: "Market too small" + reason: "Education is a $6T+ global market. Segment-level markets are almost always large enough for venture-scale businesses." + edtech_specific_diagnoses: + - name: "Compliance barrier underestimation" + description: "The company entered the institutional EdTech market without the compliance infrastructure (FERPA, COPPA, state data privacy agreements, accessibility) required for institutional procurement. Sales efforts are stalled by compliance gatekeepers." + symptoms: + - "Deals stalling at IT/privacy review stage" + - "No VPAT, DPA, or FERPA compliance documentation available" + - "Prospects asking for compliance documentation the company has not created" + - "Lost deals where the product was preferred but compliance requirements were not met" + routes_to_skills: ["trust-equation", "delivering-the-deal"] + routes_to_templates: ["regulatory-compliance-update", "action-plan"] + sector_red_flags: + - "Attempting institutional sales without FERPA compliance documentation." + - "Targeting K-12 without COPPA compliance for any features used by students under 13." + - "Entering a state adoption market without understanding the adoption review timeline." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech hiring faces a unique challenge: finding talent that bridges education and technology. The ideal EdTech product manager understands pedagogy and agile development. The ideal EdTech sales rep understands both SaaS sales and institutional procurement. The ideal content team member is a subject matter expert who can work within technology constraints. These hybrid profiles are scarce." + additional_triage_questions: + - question: "Are you hiring for education expertise (instructional designers, former teachers, curriculum specialists), technology expertise (engineers, product managers, growth marketers), or hybrid roles that require both?" + purpose: "Pure education or pure technology hires are available in the market. Hybrid roles (EdTech product manager, EdTech sales leader) are scarce and require different sourcing strategies." + routing_impact: "Hybrid role hiring routes to creative sourcing strategies (EdTech-specific job boards, conference recruiting, educator-to-tech transition programs). Pure-function hiring routes to standard tech or education recruiting." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Hiring the wrong profile for the stage" + reason: "EdTech companies frequently hire senior education executives (former superintendents, university deans) for roles that require startup hustle, or hire pure technologists for roles that require education domain knowledge." + less_likely: + - diagnosis: "Compensation competitiveness" + reason: "While EdTech compensation is generally below big-tech levels, mission alignment attracts strong candidates. The hiring problem is more often profile-fit than compensation." + edtech_specific_diagnoses: + - name: "Education-technology hybrid talent gap" + description: "The company cannot find candidates who have both education domain expertise and technology product experience. Hiring pure educators leads to slow product iteration; hiring pure technologists leads to pedagogically weak products." + symptoms: + - "Product manager roles open for 4+ months because candidates lack either education or tech experience" + - "Former teacher hires struggling with startup pace and ambiguity" + - "Technology hires making product decisions that educators on the team find pedagogically unsound" + - "High attrition in first 6 months as hires from one background realize the other domain's requirements" + routes_to_skills: ["eisenhower-matrix", "delegation-and-empowerment"] + routes_to_templates: ["role-description-template", "hiring-scorecard"] + sector_red_flags: + - "Instructional designer roles remaining unfilled for 6+ months — the talent pool is thin." + - "Head of Sales hire failing because the hire came from enterprise SaaS and cannot navigate education procurement." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech operational chaos is amplified by the academic calendar — back-to-school season creates an annual intensity spike that strains every operational function. Content updates must be ready before September, institutional onboarding must complete before classes start, and technical infrastructure must scale for the sudden load increase when millions of students return to school." + additional_triage_questions: + - question: "Does operational chaos concentrate in specific periods — August-September (back-to-school), January (spring semester start), or May-June (end-of-year assessments and contract renewals)?" + purpose: "Calendar-concentrated chaos is predictable and therefore manageable through advance preparation. Year-round chaos suggests systemic operational failure." + routing_impact: "Calendar-concentrated chaos routes to seasonal operations planning and capacity management. Year-round chaos routes to systems-thinking and process redesign." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Seasonal capacity mismatch" + reason: "EdTech companies with flat staffing serving calendar-driven demand face predictable operational overload during peak periods." + less_likely: + - diagnosis: "Process deficiency" + reason: "EdTech operations may appear chaotic during peak season due to legitimate demand spikes, not process failure." + edtech_specific_diagnoses: + - name: "Back-to-school infrastructure crisis" + description: "The platform cannot handle the sudden load increase when the academic year begins. Onboarding, technical deployment, teacher training, and student activation all compress into a 4-6 week window, overwhelming support, engineering, and customer success teams simultaneously." + symptoms: + - "Platform performance degradation in September" + - "Support ticket volume tripling during back-to-school month" + - "Teacher onboarding incomplete by the time classes start" + - "Implementation timelines slipping into October, losing critical first weeks of the school year" + routes_to_skills: ["systems-thinking", "eisenhower-matrix"] + routes_to_templates: ["action-plan", "incident-postmortem"] + sector_red_flags: + - "Platform downtime during school hours — teachers have zero tolerance for products that do not work when class is in session." + - "Content errors discovered by students or teachers during instructional use — quality failures in a learning context damage trust profoundly." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership crises in EdTech follow similar patterns to other venture-backed companies — founder burnout, board conflicts, executive team dysfunction, and crisis management. The base diagnostic applies without significant EdTech-specific modification." + additional_triage_questions: [] + diagnosis_weight_shifts: + more_likely: [] + less_likely: [] + edtech_specific_diagnoses: [] + sector_red_flags: + - "CEO making decisions based on the loudest institutional customer rather than strategic analysis — a sign of reactive leadership in a market that rewards proactive positioning." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech decision paralysis is amplified by the multi-stakeholder complexity — every decision must consider the buyer, implementer, and user, creating a three-dimensional analysis space that invites perpetual deliberation. The academic calendar adds urgency constraints that do not exist in other sectors — missing a back-to-school window is a 12-month delay." + additional_triage_questions: + - question: "Is the decision paralysis caused by trying to serve all three stakeholders (buyer, teacher, student) simultaneously without clear prioritization?" + purpose: "Multi-stakeholder paralysis is the most common form in EdTech. Clear prioritization (e.g., 'teacher experience first, buyer compliance second, student engagement third') breaks the paralysis." + routing_impact: "Multi-stakeholder paralysis routes to business-model-canvas for stakeholder strategy and evaluating-and-deciding for decision framework." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Multi-stakeholder analysis paralysis" + reason: "Every EdTech decision can be argued from three stakeholder perspectives. Without clear decision frameworks that specify which stakeholder to optimize for in each decision type, analysis becomes infinite." + less_likely: + - diagnosis: "Insufficient information" + reason: "EdTech companies rarely lack information — they have engagement data, teacher feedback, admin requirements, and student outcomes. They lack clarity on which stakeholder to prioritize." + edtech_specific_diagnoses: [] + sector_red_flags: + - "Product decisions delayed past back-to-school deadlines — a missed September launch window pushes the decision's impact by 12 months." + - "Pricing or packaging decisions deferred for more than two academic cycles without resolution." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech innovation droughts are uniquely dangerous because the sector is undergoing AI-driven transformation. Companies that stop innovating while AI rapidly improves risk losing their core value proposition to general-purpose tools. The innovation drought often results from over-investment in content maintenance (updating curricula for new standards) at the expense of technology innovation (adaptive algorithms, AI integration, new interaction paradigms)." + additional_triage_questions: + - question: "What percentage of engineering and content capacity is allocated to standards updates and compliance maintenance versus new product innovation?" + purpose: "EdTech companies face a unique tax — curricula change, standards update, and compliance requirements evolve continuously. If 70%+ of capacity goes to maintenance, innovation starves." + routing_impact: "Maintenance-dominated allocation routes to efficiency analysis (can AI reduce standards-alignment work?) and strategic resource reallocation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Standards maintenance consuming innovation capacity" + reason: "Updating content for new state standards, maintaining accessibility compliance, and adapting to curriculum changes consume significant capacity in EdTech — capacity that is unavailable for product innovation." + less_likely: + - diagnosis: "Lack of creative talent" + reason: "EdTech companies typically employ instructional designers and educators with deep creative and pedagogical skills. The constraint is capacity, not creativity." + edtech_specific_diagnoses: + - name: "Student engagement collapse" + description: "Student engagement metrics are declining across cohorts, indicating that the product is losing relevance, falling behind competitors in experience quality, or being outperformed by AI-based alternatives that offer a more personalized, responsive learning experience." + symptoms: + - "DAU/MAU declining for 3+ consecutive months (seasonally adjusted)" + - "Session duration decreasing while completion rates hold (learners rushing through)" + - "NPS declining specifically in the learner segment while teacher and admin scores hold" + - "Teacher feedback indicating 'students are not excited about it anymore'" + routes_to_skills: ["product-life-cycle", "disruptive-innovation", "ai-vision-and-strategy"] + routes_to_templates: ["new-initiative-brief", "quarterly-strategic-review"] + sector_red_flags: + - "No new feature category shipped in 12+ months — only incremental improvements and maintenance updates." + - "Competitor product launches generating teacher inquiries about matching capabilities." + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech partnerships involve unique partner types: textbook publishers (Pearson, McGraw-Hill), LMS platforms (Canvas, Google Classroom), assessment organizations (College Board, NWEA), state education departments, school district consortiums, and philanthropic funders. Each partner type has different motivations, power dynamics, and risk profiles." + additional_triage_questions: + - question: "Is this a technology integration partnership (connecting with an LMS or SIS), a content partnership (co-developing with a publisher or university), a distribution partnership (selling through a channel or consortium), or a research partnership (collaborating on efficacy studies)?" + purpose: "Each partnership type in EdTech has distinct economics, governance requirements, and failure modes." + routing_impact: "Technology integration routes to standards compliance (LTI, xAPI). Content partnership routes to IP negotiation. Distribution partnership routes to channel economics analysis. Research partnership routes to study design and evidence strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Asymmetric power in publisher or platform partnerships" + reason: "EdTech startups partnering with Pearson, McGraw-Hill, Google, or Canvas face significant power imbalances. The larger partner can change terms, priorities, or strategy with minimal consequence to themselves but existential impact on the startup." + less_likely: + - diagnosis: "Cultural misalignment" + reason: "Education partnerships share a common mission language that smooths cultural differences. The challenge is usually strategic or economic, not cultural." + edtech_specific_diagnoses: + - name: "Platform dependency risk" + description: "The company's distribution depends heavily on a single platform (Google Classroom, Canvas, Clever) that could change its API terms, add a competing native feature, or deprioritize the integration." + symptoms: + - "More than 50% of user acquisition flowing through a single platform integration" + - "Product functionality deeply dependent on platform APIs that could change" + - "No direct relationship with end users — all traffic flows through the platform" + - "Platform partner announcing features that overlap with your core offering" + routes_to_skills: ["prisoners-dilemma-and-cooperation", "scenario-planning", "porters-five-forces"] + routes_to_templates: ["risk-assessment-brief", "strategic-analysis-one-pager"] + sector_red_flags: + - "Google Classroom or Canvas announcing a native feature that overlaps with your core value proposition." + - "More than 60% of revenue flowing through a single publisher or platform relationship." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech communication breakdowns often occur at the boundary between the company and its institutional customers. The multi-stakeholder chain (sales talks to admins, customer success talks to teachers, product talks to students) creates a telephone game where information degrades at each handoff." + additional_triage_questions: + - question: "Is the communication breakdown internal (between company teams) or external (between the company and its institutional customers — administrators, teachers, or students)?" + purpose: "External communication breakdowns in EdTech are often more damaging than internal ones because a single miscommunication to a school district can affect thousands of learners and destroy a customer relationship." + routing_impact: "Internal breakdown routes to standard team communication improvement. External breakdown routes to stakeholder communication strategy and customer success process redesign." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Sales-to-implementation handoff failure" + reason: "In EdTech, the sales team sells to administrators while the implementation team works with teachers. The handoff between these teams is where expectations, timelines, and success criteria are lost." + less_likely: [] + edtech_specific_diagnoses: [] + sector_red_flags: + - "Teachers at customer institutions unaware that their school purchased the product — a sign of total communication failure in the customer organization." + - "Sales and customer success teams using different language to describe the product's capabilities to different stakeholder groups within the same institution." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech negotiations get stuck in characteristic ways: district procurement processes demanding terms the startup cannot offer (multi-year pricing guarantees, unlimited liability), data privacy agreement review extending weeks beyond expectation, school board approval required for purchases above threshold, and pilot programs running indefinitely without conversion criteria." + additional_triage_questions: + - question: "Is the negotiation stuck on commercial terms (price, contract length), compliance terms (data privacy, FERPA, accessibility), approval process (waiting for school board, committee, or budget approval), or pilot conversion (the pilot has no defined end or success criteria)?" + purpose: "Each stall type in EdTech has a different resolution path. Commercial stalls need creative structuring. Compliance stalls need pre-prepared documentation. Approval stalls need patience and process management. Pilot stalls need defined success criteria." + routing_impact: "Commercial stalls route to competitive-negotiation. Compliance stalls route to delivering-the-deal with emphasis on compliance documentation readiness. Approval stalls route to scenario-planning for timeline management. Pilot stalls route to smart-goals for defining conversion criteria." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Data privacy review blocking the deal" + reason: "Institutional EdTech procurement increasingly stalls during data privacy review. Schools are legally liable for student data shared with vendors, and privacy officers are thorough." + - diagnosis: "Perpetual pilot syndrome" + reason: "Free pilots without defined success criteria, end dates, or contractual purchase paths run indefinitely in education. The institution gets the product for free while the company gets neither revenue nor a clear no." + less_likely: + - diagnosis: "Fundamental value disagreement" + reason: "If the negotiation reached the terms stage, value has been established. Most EdTech negotiation stalls are procedural (compliance, approval) not substantive." + edtech_specific_diagnoses: + - name: "Accessibility compliance failure" + description: "The institutional deal is blocked because the product does not meet accessibility requirements (WCAG 2.1 AA, Section 508). Public schools and universities receiving federal funding are legally required to ensure educational technology is accessible to students with disabilities." + symptoms: + - "Deal stalling at IT accessibility review stage" + - "No VPAT or Accessibility Conformance Report available" + - "Prospect's accessibility coordinator identifying WCAG failures in product evaluation" + - "Competitive products winning deals based on accessibility compliance rather than feature superiority" + routes_to_skills: ["trust-equation", "systems-thinking"] + routes_to_templates: ["regulatory-compliance-update", "action-plan"] + sector_red_flags: + - "Institutional deals stalling for 90+ days in compliance review — indicates the company needs a pre-prepared compliance documentation kit." + - "Free pilots running longer than one semester without conversion criteria — the institution has no incentive to purchase." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "EdTech culture erosion has a unique pattern: the mission-driven culture that attracted early employees degrades as growth pressures introduce metrics-first thinking. The tension between 'we are here to improve education' and 'we need to hit revenue targets' is a predictable stress point that, if unmanaged, erodes the culture that made the company attractive to talent." + additional_triage_questions: + - question: "Has the company's growth shifted the internal culture from mission-first to metrics-first — and are employees who joined for the mission feeling that the company has 'sold out'?" + purpose: "This culture shift is the most common erosion pattern in scaling EdTech companies. Early employees attracted by mission witness the transition to growth-stage pressure and feel betrayed." + routing_impact: "Mission-metrics culture tension routes to organisational-culture and purpose-driven-leadership for values reintegration." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Mission-metrics tension eroding original culture" + reason: "EdTech companies that scale successfully must simultaneously pursue impact and revenue. Employees who feel forced to choose between mission and metrics disengage." + less_likely: + - diagnosis: "Toxic leadership" + reason: "EdTech leaders are typically mission-motivated. Culture erosion is more often caused by the structural tension of scaling a mission-driven company than by deliberately harmful leadership." + edtech_specific_diagnoses: + - name: "Mission fatigue and disillusionment" + description: "Early employees who joined to 'change education' experience disillusionment as the company makes compromises necessary for commercial viability — selling to institutions that may not implement well, prioritizing revenue-generating features over mission-critical improvements, or entering markets where the impact story is weaker." + symptoms: + - "Early employees (first 20 hires) leaving at higher rates than recent hires" + - "Employee survey comments about 'losing our way' or 'becoming just another SaaS company'" + - "Declining participation in company mission events (school visits, impact reports)" + - "Resistance to commercially necessary decisions framed as 'anti-mission'" + routes_to_skills: ["organisational-culture", "purpose-driven-leadership", "leading-through-change"] + routes_to_templates: ["culture-values-document", "team-health-check"] + sector_red_flags: + - "Regrettable attrition concentrated among instructional designers and former educators — the mission-bearers are leaving." + - "Employee NPS declining faster among education-background employees than technology-background employees." diff --git a/plugins/foreman/content/industry-packs/edtech/edtech-skill-overlays.yaml b/plugins/foreman/content/industry-packs/edtech/edtech-skill-overlays.yaml new file mode 100644 index 0000000..8d36fcc --- /dev/null +++ b/plugins/foreman/content/industry-packs/edtech/edtech-skill-overlays.yaml @@ -0,0 +1,442 @@ +# EdTech Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides EdTech-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add an EdTech lens. +# +# The defining challenge of applying any framework to EdTech: multi-stakeholder +# value chains. The buyer (district admin, university provost, L&D director) is +# rarely the user (student, employee). The implementer (teacher, professor, +# trainer) sits between them. Every framework must account for this three-layer +# chain — buyer, implementer, user — or risk solving for the wrong stakeholder. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct EdTech application (strategy, pricing, marketing, adoption) +# - Frameworks requiring fundamental reinterpretation for EdTech multi-stakeholder dynamics +# - Decision and thinking skills (procurement complexity demands clear analysis) +# - Negotiation skills (institutional sales, university partnerships, publisher deals) +# - Leadership skills most affected by education-sector organizational dynamics +# - Game theory skills applicable to EdTech competitive and partnership strategy +# +# Relevance tiers: +# critical — The EdTech overlay materially changes how the skill is applied. +# The skill executor should always surface EdTech context. +# high — EdTech context adds significant value. Surface when relevant. +# moderate — Useful EdTech framing but the base skill works well as-is. + +pack_metadata: + sector: "edtech" + display_name: "EdTech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (20 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "Porter's Five Forces in EdTech must contend with a structural anomaly: the buyer (institution) is not the user (learner), and a powerful intermediary (teacher/instructor) determines whether the product is actually used. Buyer power is extreme because education procurement is consolidated (14,000 US school districts control purchasing for 130,000 schools) and cyclical (tied to budget years). Threat of substitutes is uniquely intense — free, high-quality content (Khan Academy, YouTube, MIT OpenCourseWare, ChatGPT) competes with every paid product. Supplier power includes content creators, subject matter experts, and increasingly AI model providers. Rivalry is shaped by procurement inertia: once a product wins a district, switching costs are high due to curriculum alignment and teacher training investment." + edtech_anti_patterns: + - "Analyzing buyer power as though the student is the buyer. In institutional EdTech, the procurement officer or curriculum director holds purchasing authority. Their criteria (compliance, evidence, interoperability) differ entirely from the student's criteria (engagement, ease, relevance)." + - "Ignoring the 'threat of free.' Khan Academy, YouTube educational channels, and open educational resources (OER) are genuine substitutes that set a price ceiling on many EdTech categories. Any paid product must deliver value that free alternatives cannot." + - "Underestimating the regulatory force. FERPA, COPPA, state privacy laws, and accessibility requirements function as a de facto sixth force — raising barriers to entry for new competitors but also constraining incumbents." + edtech_example: "A K-12 math platform uses Porter's Five Forces to map its competitive landscape. Buyer power: concentrated in district math coordinators who evaluate against state standards alignment. Substitutes: Khan Academy Math (free, high quality), IXL (entrenched incumbent), and now AI tutoring via ChatGPT. New entrants: barriers are moderate (compliance requirements, efficacy evidence) but AI-native products are entering rapidly. Supplier power: math content is commoditized but adaptive algorithm talent is scarce. Rivalry: intense within the 'adaptive math' subcategory but most competitors lack efficacy evidence. The analysis reveals that the sustainable competitive advantage is not content (commoditized) or technology (replicable) but efficacy evidence plus teacher adoption support — the combination competitors cannot quickly replicate." + benchmark_references: ["institutional-churn-rate", "institutional-adoption-rate", "teacher-adoption-rate"] + + - skill: "blue-ocean-strategy" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "Blue ocean strategy is structurally essential for EdTech because the major categories (LMS, assessment, SIS, tutoring) are crowded red oceans with entrenched incumbents. Blue oceans in EdTech emerge from three sources: (1) Underserved stakeholders — products that serve teachers (historically neglected in favor of admin tools) or parents (no seat at the procurement table). (2) Unaddressed learning modalities — micro-learning, project-based learning, social-emotional learning, and skills-based credentialing are emerging spaces. (3) Delivery model innovation — shifting from semester-long courses to just-in-time learning, from content delivery to outcome guarantees, or from institutional licensing to individual subscriptions. The strategy canvas should map value across all three stakeholder groups: what buyers value (evidence, compliance, cost), what implementers value (ease, time savings, PD support), and what users value (engagement, relevance, outcomes)." + edtech_anti_patterns: + - "Creating a blue ocean that ignores the procurement channel. A product that is brilliant for learners but impossible to purchase through institutional procurement has found a blue ocean with no water — no viable path to revenue." + - "Assuming that a new technology (AI, VR, blockchain credentials) automatically creates a blue ocean. Technology is a tool, not a strategy. The blue ocean is the unmet need the technology addresses." + - "Building for a stakeholder who cannot buy. A product that teachers love but that has no district-level purchase path will remain a passion project, not a business." + edtech_example: "ClassDojo found a blue ocean by targeting the parent-teacher communication gap — a space that no LMS, SIS, or assessment platform addressed. The strategy canvas showed that existing products over-served administrative workflows and under-served the human relationship between teacher and family. By eliminating complexity (no grades, no assignments, no compliance features) and adding what was missing (real-time behavioral feedback, multimedia sharing, parent translation), ClassDojo created a new category with 50+ million users in 180 countries." + benchmark_references: ["learner-engagement-rate", "teacher-adoption-rate", "free-to-paid-conversion"] + + - skill: "business-model-canvas" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "The Business Model Canvas in EdTech requires a fundamental structural modification: THREE distinct Customer Segments with different Value Propositions for each. Segment 1 — Buyer (district admin, provost, L&D director): values compliance, evidence, cost-effectiveness, and vendor reliability. Segment 2 — Implementer (teacher, professor, trainer): values ease of use, time savings, professional development support, and classroom management tools. Segment 3 — User (student, employee): values engagement, relevance, outcomes, and (in consumer) fun. Revenue Streams must map to the buyer segment — the user and implementer rarely pay directly. Key Activities must include regulatory compliance, efficacy research, and institutional relationship management alongside product development. Customer Relationships differ radically by segment: transactional with buyers (annual procurement), ongoing with implementers (training, support), and product-driven with users (engagement, retention)." + edtech_anti_patterns: + - "Filling the canvas with one Customer Segment. This is the cardinal sin of EdTech strategy. A canvas that names 'schools' as the customer fails to distinguish between the three stakeholders whose needs conflict." + - "Placing 'great content' or 'engaging learning experience' as the sole Value Proposition. Content quality is necessary but not sufficient. The buyer's value proposition is evidence and compliance; the teacher's is time savings and ease; the student's is engagement and outcomes." + - "Omitting the implementation cost from the Cost Structure. EdTech products with high implementation burden (teacher training, curriculum alignment, data integration) have structurally different economics than self-serve products." + edtech_example: "An adaptive reading platform maps three BMCs on one canvas. For the Buyer (district literacy coordinator): Value Proposition is ESSA Tier 2 efficacy evidence, state standards alignment, and FERPA compliance. For the Implementer (reading teacher): Value Proposition is 20 minutes saved per class through automated differentiation, real-time diagnostic reports, and embedded PD. For the User (K-3 student): Value Proposition is personalized stories featuring characters they identify with, immediate positive feedback, and age-appropriate gamification. Revenue flows from the buyer; product engagement comes from the user; adoption depends on the implementer. The canvas reveals that the Key Activity most correlated with revenue is not product development but teacher onboarding — the bridge between purchase and usage." + benchmark_references: ["average-contract-value", "teacher-adoption-rate", "learner-engagement-rate", "institutional-churn-rate"] + + - skill: "four-ps-marketing" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "The Four Ps in EdTech operate under constraints absent from most industries. Product must serve three stakeholders simultaneously (buyer, implementer, user) and meet regulatory requirements (FERPA, COPPA, accessibility). Price is budget-cycle-dependent — K-12 budgets are approved annually with specific funding windows (Title I, ESSER, state grants); higher ed procurement follows fiscal years; corporate L&D follows quarterly budgets. The pricing ceiling is set by free alternatives (Khan Academy, YouTube, ChatGPT) and the historical expectation that education should be publicly funded. Place (distribution) in EdTech is dominated by institutional procurement channels: conference relationships (ISTE, ASU+GSV, FETC), teacher word-of-mouth networks, district-level RFP processes, state adoption lists, and increasingly, teacher-first freemium-to-institutional conversion. Promotion must reach all three stakeholders through different channels: buyers through evidence and ROI data, implementers through peer networks and PD communities, users through product experience and word-of-mouth." + edtech_anti_patterns: + - "Pricing without understanding funding sources. An EdTech product priced at $15/student is affordable for a Title I school with federal funding but impossible for a school relying solely on local budget. Pricing strategy must account for how institutions actually pay." + - "Marketing only to the buyer. A district administrator who has never seen a teacher use the product will not renew. Promotion must create pull from implementers and users, not just push from the sales team." + - "Treating 'Place' as a website. EdTech distribution requires deep institutional relationship channels. A conference booth at ISTE, a partnership with a curriculum publisher, and a spot on a state adoption list each represent fundamentally different distribution strategies." + edtech_example: "A K-12 science simulation platform applies the Four Ps. Product: three-layer design — student-facing simulations (engagement), teacher dashboard with standards-aligned lesson plans (ease), admin reporting with NGSS alignment data (evidence). Price: $5/student/year — priced to fit within Title IV-A allocations and below the threshold requiring school board approval in most districts. Place: teacher-first adoption — free individual teacher accounts, viral spread through teacher PD communities, conversion to school license when 3+ teachers at a school are active, then district-wide licensing through direct sales. Promotion: teacher testimonial videos for implementers, peer-reviewed efficacy study for buyers, student engagement demo for conference presentations." + benchmark_references: ["average-contract-value", "student-acquisition-cost", "free-to-paid-conversion", "teacher-adoption-rate"] + + - skill: "net-promoter-score" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "NPS in EdTech must be measured and reported as THREE separate scores — one for each stakeholder — because satisfaction diverges dramatically across the buyer-implementer-user chain. A product can have Student NPS of 60 (they love it), Teacher NPS of -10 (it creates extra work), and Admin NPS of 30 (it meets compliance needs but teachers complain). Each NPS score predicts different outcomes: Admin NPS predicts contract renewal; Teacher NPS predicts actual usage and engagement; Student NPS predicts learning outcomes and word-of-mouth. The most dangerous configuration is high Admin NPS with low Teacher NPS — the product will be purchased but not used, leading to poor outcomes and eventual churn. NPS surveys must be timed differently for each segment: students after course completion, teachers mid-semester (after forming opinions but before end-of-year fatigue), administrators after receiving usage and outcome reports." + edtech_anti_patterns: + - "Measuring a single blended NPS across all stakeholders. A blended score of 30 could hide Student NPS of 50, Teacher NPS of 5, and Admin NPS of 35 — three completely different stories requiring three different strategies." + - "Optimizing for student NPS at the expense of teacher NPS. Students may love gamification and social features that teachers find disruptive or irrelevant to learning objectives." + - "Surveying admin NPS without providing them usage and outcome data first. Administrators cannot form meaningful opinions about an EdTech product they have never directly used — their NPS should be based on evidence of impact, not marketing materials." + edtech_example: "A language learning platform for higher education measures segmented NPS and discovers a critical pattern: Student NPS is 55 (strong), Professor NPS is 15 (weak), and Department Chair NPS is 40 (moderate). Investigation reveals that professors view the platform as a threat to their pedagogical authority — it assigns exercises and measures progress independently of their syllabus. The fix is not to remove the adaptive features students love but to give professors a 'curriculum alignment' tool that integrates the platform's adaptive exercises into their existing course structure. After launch, Professor NPS rises to 42, and department-wide adoption follows." + benchmark_references: ["nps-segmented", "teacher-adoption-rate", "institutional-churn-rate"] + + - skill: "product-life-cycle" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "The product lifecycle in EdTech is uniquely constrained by three external calendars that do not exist in other industries. First, the academic calendar: products launch and gain traction during the school year (September-May for K-12) and face a summer valley where engagement drops 30-60%. Second, the curriculum adoption cycle: textbook and core curriculum replacements occur every 5-8 years at the state level (in adoption states), creating windows of opportunity that open and close regardless of product readiness. Third, the budget cycle: institutional purchasing power is concentrated in specific months (May-August for K-12), meaning a product that reaches maturity in November must wait 6 months for the next purchasing window. The lifecycle stages map to EdTech as follows: Introduction = pilot period (typically one semester), Growth = district/institutional expansion, Maturity = category standardization (when the product becomes expected rather than innovative), Decline = curriculum shift or technological disruption." + edtech_anti_patterns: + - "Interpreting seasonal engagement drops as product decline. A K-12 product that loses 50% of engagement in June is not in decline — it is subject to the academic calendar. Report lifecycle metrics on an academic-year basis." + - "Assuming EdTech products have the same iteration speed as consumer software. Curriculum-aligned products cannot pivot mid-semester without disrupting teachers' lesson plans. The iteration cycle aligns with semester boundaries." + - "Ignoring the textbook replacement cycle. In states with adoption lists (Texas, California, Florida), landing on the state adoption list during a subject review cycle can create 10 years of growth. Missing the window means waiting for the next cycle." + edtech_example: "An adaptive math platform uses product lifecycle analysis to time its market entry. The product launches pilot (Introduction) in Fall 2025 with 10 schools. Growth phase begins Fall 2026 after one full year of efficacy data. The critical insight: California's math curriculum adoption review occurs in 2027, a once-in-8-years event that determines which math products appear on the state's recommended list. By timing the product lifecycle to have ESSA Tier 3 evidence ready for the California review, the company positions for a state-level growth inflection that competitors who launched later cannot achieve." + benchmark_references: ["institutional-adoption-rate", "learner-engagement-rate", "content-completion-rate"] + + - skill: "disruptive-innovation" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "EdTech is a textbook arena for disruptive innovation — the theory's originator studied education as a primary case. The disruptive dynamic in EdTech follows a specific pattern: incumbent solutions (textbooks, in-person tutoring, traditional LMS platforms) over-serve institutional requirements (compliance, reporting, administrative control) while under-serving the actual learning experience. Disruption enters through the 'non-consumption' path — reaching learners who have no access to the incumbent solution. Khan Academy disrupted tutoring by making it free. Coursera disrupted university continuing education by making it accessible online. Duolingo disrupted language schools by making learning a mobile habit. The key insight for EdTech founders: disrupt the delivery model, not the content. The content is often similar; the disruption is in who can access it, when, how, and at what cost." + edtech_anti_patterns: + - "Trying to disrupt the classroom teacher. Forty years of EdTech history demonstrate that products positioned to 'replace the teacher' fail commercially and pedagogically. The disruption path is augmenting the teacher, not eliminating them." + - "Equating technology novelty with disruption. VR in classrooms, blockchain credentials, and AI tutors are technologies, not disruptions. They become disruptive only when they enable access or outcomes impossible through existing models." + - "Ignoring the institutional inertia that sustains incumbents. School districts change suppliers slowly. A disruptive EdTech product must survive 2-5 years of coexistence with the incumbent before achieving meaningful displacement." + edtech_example: "Quizlet disrupted traditional study methods (flashcards, study guides) by entering through non-consumption — students who could not afford expensive study materials or did not have access to study groups. The free, user-generated flashcard model was 'worse' than professionally created study materials but infinitely more accessible. As Quizlet improved (adding adaptive learning, diagrams, AI explanations), it moved upmarket, eventually competing with commercial test prep and corporate training products. The disruption path was classic: free, simple, and accessible at the bottom, then relentless quality improvement upward." + benchmark_references: ["free-to-paid-conversion", "learner-engagement-rate", "student-acquisition-cost"] + + - skill: "balanced-scorecard" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "The Balanced Scorecard in EdTech must incorporate a dimension absent from the standard four perspectives: efficacy. Financial: revenue (institutional + consumer), gross margin, CAC, LTV, burn rate. Customer: segmented by all three stakeholders — institutional NPS (buyer), teacher adoption rate (implementer), learner engagement and retention (user). Internal Process: content production velocity, FERPA/COPPA compliance status, accessibility compliance, time to institutional sale, pilot-to-purchase conversion rate. Learning & Growth: instructional design team development, efficacy research pipeline, teacher professional development investment. The fifth dimension — Efficacy: learning outcomes improvement, completion rates, assessment score gains, efficacy evidence tier advancement. This efficacy dimension drives the customer dimension (institutions buy products that work) which drives the financial dimension." + edtech_anti_patterns: + - "Omitting the efficacy perspective. An EdTech balanced scorecard without learning outcomes metrics is a SaaS scorecard with education branding. If the product does not measurably improve learning, the business is selling software, not education technology." + - "Measuring customer satisfaction without stakeholder segmentation. Blended satisfaction metrics hide the buyer-implementer-user divergences that determine renewal and adoption." + - "Tracking financial metrics on a calendar year when the business is driven by the academic year. EdTech scorecards should align with the September-August cycle for K-12 or the fall-spring semester cycle for higher ed." + edtech_example: "A corporate L&D platform builds a balanced scorecard with five perspectives. Financial: ARR growth (target: 80% YoY), gross margin (target: 70%), L&D buyer CAC (target: <$15K), enterprise LTV (target: >$100K). Customer: L&D buyer NPS (target: 45), trainer adoption rate (target: 65%), employee engagement rate (target: 55%), completion rate (target: 70%). Internal Process: course creation time (target: <40 hours per course), compliance certification maintenance (target: 100% current), sales cycle length (target: <90 days). Learning & Growth: instructional designer upskilling hours, AI content creation adoption, customer success team certifications. Efficacy: skill assessment improvement (target: 25%), manager-reported behavior change (target: 60%), credential completion rate (target: 50%). The scorecard reveals that high financial growth is masking declining efficacy metrics — new customers are buying but not achieving outcomes, a leading indicator of future churn." + benchmark_references: ["learner-engagement-rate", "content-completion-rate", "learning-outcomes-improvement", "institutional-churn-rate", "nps-segmented", "gross-margin"] + + - skill: "growth-share-matrix" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "The BCG Growth-Share Matrix applies to EdTech product portfolios across content areas, grade levels, or learner segments. Stars are fast-growing product lines in high-growth segments (e.g., AI tutoring, skills-based credentialing). Cash Cows are mature product lines with strong institutional install bases (e.g., established LMS, core curriculum products with state adoption). Question Marks are new entries in emerging categories (e.g., social-emotional learning tools, micro-credentialing). Dogs are products in declining segments with weak market position (e.g., legacy on-premise products, CD-ROM-era content digitized without redesign). The matrix is particularly useful when EdTech companies diversify across segments (K-12 + higher ed + corporate) or across subject areas." + edtech_anti_patterns: + - "Treating an entire K-12 product as one unit. The product serving 3rd-grade reading may be a Star while the 8th-grade version is a Dog. Apply the matrix at the subject-grade level." + - "Killing 'Dog' products that serve as entry points for institutional relationships. A weak product line that provides a foot in the door for selling the Star product has strategic value beyond its own growth metrics." + - "Ignoring that education market growth is driven by policy, not market forces alone. A segment can shift from Question Mark to Star overnight when a new state mandate or federal funding program targets it." + edtech_example: "A K-12 EdTech company maps its portfolio: Math adaptive learning (Star — high growth, strong market position due to ESSA evidence), Reading comprehension (Cash Cow — mature, entrenched in 500+ districts), Social-emotional learning (Question Mark — growing market but the company is one of many unproven entrants), Standardized test prep (Dog — declining as states move away from high-stakes testing). The matrix guides resource allocation: invest heavily in math, harvest reading revenue to fund math growth, make a go/no-go decision on SEL within two quarters, and gradually sunset test prep." + benchmark_references: ["institutional-adoption-rate", "expansion-revenue-institutional", "learner-engagement-rate"] + + - skill: "swot-pest-analysis" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "SWOT and PEST analysis in EdTech must account for the sector's unique environmental forces. Political: education policy changes (Every Student Succeeds Act, state curriculum standards, federal funding programs like Title I/ESSER), school board politics, teachers' union positions on technology, and state-level textbook adoption lists. Economic: school district budget cycles (driven by property tax revenue and federal/state allocations, not market conditions), higher ed enrollment trends (demographic cliff of 2025-2030), and corporate training budget sensitivity to recession. Social: the digital equity divide (not all students have devices/connectivity at home), growing parent activism around screen time and data privacy, teacher burnout driving demand for time-saving tools, and the cultural expectation that education should be free or publicly funded. Technological: AI tutoring and content generation transforming every EdTech category, LMS platform consolidation, interoperability standards (LTI, QTI, xAPI, Ed-Fi), and the shift from content delivery to adaptive learning." + edtech_anti_patterns: + - "Treating 'technology' as a strength without specifying which technological capability creates defensible advantage. Every EdTech company has technology. The question is whether the technology creates a data moat, a pedagogical advantage, or merely a better UI." + - "Ignoring the political dimension. A change in state leadership can add or remove your product from an adoption list, redirect $100M in funding, or mandate a competitor's approach. EdTech companies must monitor policy actively." + - "Conducting SWOT without distinguishing between segments. The SWOT for a K-12 product is fundamentally different from the SWOT for the same company's higher ed or corporate product." + edtech_example: "An EdTech company uses PEST to identify a strategic opportunity: the upcoming demographic cliff (2025-2030 decline in US college-age population) is a Social factor that threatens higher ed enrollment. The Economic impact will force universities to seek revenue efficiency. The Political response will likely include increased funding for alternative credentials and skills-based hiring. The Technological shift toward AI-enabled personalization makes smaller cohort instruction more viable. Combined SWOT reveals a blue ocean: mid-tier universities that cannot compete for shrinking traditional student pools but could thrive by offering AI-personalized, shorter-form credential programs to working adults." + benchmark_references: ["institutional-adoption-rate", "average-contract-value"] + + - skill: "scenario-planning" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "Scenario planning in EdTech must account for three high-variance dimensions absent from other sectors. First, policy scenarios: education funding and mandates change with administrations at federal and state levels. A change in the US Secretary of Education or a state superintendent can redirect billions in purchasing power. Second, calendar scenarios: the academic calendar creates natural planning horizons (semester, academic year) but also cliffs — miss the back-to-school adoption window and wait 12 months. Third, technology disruption scenarios: AI tutoring (ChatGPT, Khanmigo) represents the most significant technology disruption in education since the internet. EdTech companies must scenario-plan for a world where AI tutoring is ubiquitous, free, and good enough for most learning tasks. The planning horizon should align with academic years, not calendar quarters." + edtech_anti_patterns: + - "Building all scenarios around market growth rates without including a policy disruption scenario. An EdTech company that depends on Title I funding must plan for a scenario where that funding is reduced or redirected." + - "Treating AI as a distant threat rather than an immediate competitive force. AI tutoring is available now, improving rapidly, and free. Every EdTech scenario plan must include an 'AI good enough' scenario." + - "Planning on a calendar year when revenue is driven by academic year cycles. The fiscal year should align with the selling season." + edtech_example: "A test prep company builds three scenarios for the next two academic years: (1) Base: SAT/ACT remain important, states maintain standardized testing, AI tutoring supplements but does not replace structured prep. Revenue grows 20% YoY through institutional and consumer channels. (2) Upside: More states adopt college readiness assessments, creating new institutional demand. The company's adaptive technology outperforms generic AI tutoring on outcome metrics. Revenue grows 40% YoY. (3) Downside: Top universities go test-optional permanently, state testing mandates weaken, and ChatGPT provides 'good enough' test prep for free. Consumer revenue drops 30%; institutional revenue drops 15% as schools deprioritize test prep. Each scenario has a trigger (university testing policy announcements, state legislative actions) and a pre-planned strategic response." + benchmark_references: ["institutional-adoption-rate", "free-to-paid-conversion", "learner-engagement-rate"] + + - skill: "smart-goals" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "SMART goals in EdTech must align with the academic calendar and account for the multi-stakeholder value chain. Goals should be set on a semester or academic-year basis, not calendar quarters, because the engagement data that measures progress is seasonal. Time-bound must respect the academic rhythm — setting a December goal for K-12 engagement ignores winter break. Measurable in EdTech requires specifying which stakeholder's metric is being targeted: institutional adoption (buyer), teacher activation (implementer), or learner engagement (user). Achievable must account for the procurement cycle — a goal to add 50 new districts in Q1 is unachievable if the budget approval window is Q3." + edtech_anti_patterns: + - "Setting calendar-quarter goals in an academic-year business. EdTech goals should be: Fall semester, Spring semester, and Summer (which may be a build/prepare period rather than a growth period)." + - "Setting a single goal that blends stakeholders. 'Increase engagement by 20%' is meaningless without specifying whose engagement — teacher adoption and student engagement require different strategies." + - "Setting time-to-value goals without accounting for the fact that teachers need PD before they can use the product, and PD happens on specific calendar days." + edtech_example: "Instead of 'grow revenue,' an EdTech company sets academic-year goals: (1) Fall 2026: Activate 80% of teachers at newly contracted districts within the first 6 weeks of school through dedicated onboarding support (target: 30 of 38 new districts at 80%+ teacher activation by October 15). (2) Spring 2027: Achieve ESSA Tier 3 efficacy evidence from Year 1 pilot districts with pre/post assessment data (target: statistically significant effect size in 3 of 5 pilot districts). (3) Summer 2027: Convert 60% of pilot districts to multi-year contracts before fall budget deadlines (target: 24 of 40 pilots converting by August 1)." + benchmark_references: ["teacher-adoption-rate", "learning-outcomes-improvement", "institutional-churn-rate"] + + - skill: "systems-thinking" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "EdTech businesses are complex multi-stakeholder systems with feedback loops that create counterintuitive outcomes. The most important feedback loops: (1) The efficacy loop: better learning outcomes generate better evidence, which drives more institutional adoption, which provides more data, which improves the adaptive algorithm, which improves outcomes further. (2) The teacher adoption spiral: poor teacher adoption leads to low student engagement, which leads to poor outcomes, which leads to institutional churn, which reduces case studies for sales, which makes the next institutional sale harder. (3) The content quality flywheel: more learners generate more interaction data, which identifies content gaps and optimization opportunities, which improves content quality, which improves engagement and outcomes, which attracts more learners. (4) The free content substitution trap: competing with free alternatives (Khan Academy, YouTube, ChatGPT) on price leads to margin compression, which reduces investment in content quality, which makes the free alternative relatively more attractive." + edtech_anti_patterns: + - "Treating low student engagement as a product design problem when it is actually a teacher adoption problem. If teachers are not assigning the product, students will not use it — no amount of gamification compensates for institutional non-adoption." + - "Ignoring time delays in the efficacy loop. Investing in efficacy research today produces evidence in 12-18 months that drives sales 6-12 months later. Companies that cut research spending during cash crunches starve their future sales pipeline." + - "Optimizing one stakeholder's experience without modeling the impact on others. Adding student-facing social features may improve student NPS while creating classroom management headaches that tank teacher NPS." + edtech_example: "An EdTech company experiences declining institutional renewals despite stable student engagement metrics. Systems analysis reveals a hidden reinforcing loop: as the product added gamification features to improve student engagement, it inadvertently increased off-task behavior in classrooms (students playing gamified elements instead of learning). Teachers responded by reducing product usage. The engagement metrics looked strong (students were active) but the teacher satisfaction metric was collapsing. The system-level fix required redesigning gamification to reward learning behaviors visible to teachers (completed assignments, mastery demonstrations) rather than generic app engagement." + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate", "institutional-churn-rate", "nps-segmented"] + + - skill: "cialdini-influence" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "Cialdini's six principles of influence operate differently across EdTech's three stakeholder groups. For Buyers (institutional administrators): Authority (efficacy evidence, research partnerships, ESSA tier ratings) and Social Proof (peer district adoption, state adoption list inclusion) are dominant. For Implementers (teachers): Social Proof (peer teacher testimonials, education conference presentations) and Commitment/Consistency (teachers who complete PD and set up their classroom are far more likely to adopt) drive behavior. For Users (students): Reciprocity (free access, helpful content) and Liking (relatable content, age-appropriate design) determine engagement. Scarcity operates differently in EdTech — limited-time pricing is less effective because budget cycles are fixed, but 'limited PD spots' or 'early adopter research partnership' create genuine scarcity that motivates institutional action." + edtech_anti_patterns: + - "Using consumer SaaS influence tactics (countdown timers, 'limited seats') in institutional EdTech. Procurement officers are not impulse buyers. Influence in institutional sales comes from evidence and peer reference, not urgency." + - "Over-indexing on student engagement (Liking principle) at the expense of teacher authority (Authority principle). A product students love but teachers do not trust will not survive the institutional adoption chain." + - "Neglecting the Commitment/Consistency principle in onboarding. Teachers who invest time in setting up their classroom within the product are dramatically more likely to continue using it. Design onboarding to create small commitments that compound." + edtech_example: "A higher education LMS uses Cialdini's principles to accelerate faculty adoption. Authority: partners with three research universities to publish peer-reviewed studies on learning outcomes. Social Proof: creates a 'Faculty Spotlight' series showcasing how professors at peer institutions use the platform. Commitment: designs a 30-minute 'Quick Start' setup where professors import their syllabus and create one assignment — a small commitment that dramatically increases sustained usage. Reciprocity: offers free instructional design consultation to every new faculty member. The combination drives a 3x improvement in faculty adoption within adopting institutions." + benchmark_references: ["teacher-adoption-rate", "institutional-adoption-rate", "free-to-paid-conversion"] + + - skill: "kotter-change-model" + category: "frameworks" + edtech_relevance: "critical" + edtech_context: "Kotter's eight-step change model is essential for EdTech because every institutional sale is fundamentally a change management project. Purchasing the product is step zero — the real work is changing teacher behavior, classroom routines, and institutional processes. Step 1 (Create Urgency) in EdTech is often supplied by external data: declining test scores, accreditation reviews, state audit findings, or competitive pressure from peer institutions. Step 2 (Build Coalition) requires champions at multiple levels: an administrative sponsor, a teacher champion, and ideally a parent advocate. Step 5 (Remove Obstacles) typically means addressing professional development gaps, technology infrastructure issues, and schedule conflicts. Step 8 (Anchor in Culture) means the product becomes part of 'how we teach here,' not a temporary initiative that fades with the next administrator." + edtech_anti_patterns: + - "Treating the sale as the endpoint rather than the beginning of the change process. EdTech products that invest in sales but not in post-sale implementation support experience the 'bought but not used' phenomenon — high bookings, low renewal." + - "Skipping Step 2 (Build Coalition) by relying solely on administrative mandates. Top-down mandates without teacher buy-in generate compliance, not adoption. Compliance without engagement produces poor outcomes." + - "Expecting change to happen in one semester. Meaningful institutional change in education takes 2-3 years. Products must be designed and priced for multi-year adoption journeys." + edtech_example: "A school district implements a new data analytics platform for personalized learning. Using Kotter's model: (1) Create urgency: state accountability ratings declined for two consecutive years. (2) Build coalition: the assistant superintendent, three teacher-leaders from different grade levels, and two active PTO parents. (3) Vision: 'Every student receiving instruction at their level within two years.' (4) Communicate: monthly updates to all teachers, quarterly community updates. (5) Remove obstacles: dedicated PD days, reduced teacher reporting requirements for the first year, IT infrastructure upgrades. (6) Quick wins: first grading period shows engagement data that teachers find actionable. (7) Build on gains: second semester adds teacher collaboration features. (8) Anchor: after two years, the platform is referenced in the district strategic plan and new teacher orientation." + benchmark_references: ["teacher-adoption-rate", "institutional-churn-rate", "learning-outcomes-improvement"] + + - skill: "tipping-point" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "EdTech adoption follows tipping point dynamics at both the institutional and individual level. At the institutional level, adoption tips when a critical mass of peer institutions adopts — school districts watch neighboring districts, universities follow peer rankings, and corporations follow industry leaders. The connectors in EdTech are conference presenters, teacher-influencers, and state education technology directors. The mavens are instructional technology coaches, EdTech bloggers, and professional development leaders. The salespeople are energetic teachers who demonstrate the product at conferences and on social media. At the individual level within an institution, adoption tips when approximately 15-25% of teachers actively use the product — at this threshold, peer pressure, shared materials, and hallway conversations drive the remaining adoption without administrative push." + edtech_anti_patterns: + - "Trying to reach the tipping point through top-down mandates alone. Mandated adoption creates compliance, not enthusiasm. The tipping point requires genuine advocates, not reluctant compliers." + - "Ignoring the role of teacher-influencers (the 'connectors' and 'mavens'). A handful of influential teachers with active social media presences and conference speaking roles can drive more adoption than a $500K marketing campaign." + - "Expecting institutional adoption to tip without reaching the internal teacher adoption threshold first. Districts observe whether the product works within their own pilot schools before expanding." + edtech_example: "A coding education platform identifies its tipping point strategy. Connectors: 50 teacher-ambassadors who present at state and national conferences and maintain active Twitter/educator communities. Mavens: partnerships with 10 instructional technology coaches who deeply understand the product and recommend it in their consulting work. Salespeople: a student showcase event where students present projects built with the platform to school boards and parent groups. The stickiness factor: a free 'Hour of Code' lesson that any teacher can run without preparation, creating first exposure that leads to deeper exploration. The company targets reaching 20% teacher adoption within pilot districts as the internal tipping point that drives district-wide expansion." + benchmark_references: ["teacher-adoption-rate", "institutional-adoption-rate", "free-to-paid-conversion"] + + - skill: "trust-equation" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "Trust is existentially important in EdTech because the product handles student data (often children's data) and influences learning outcomes. The Trust Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to EdTech as follows: Credibility = efficacy evidence, research partnerships, compliance certifications (FERPA, COPPA, SOC 2), and state adoption list inclusion. Reliability = platform uptime during school hours (downtime during a class period is a catastrophe), consistent content quality, and predictable feature releases that do not disrupt mid-semester. Intimacy = understanding the specific school's context, the teacher's pedagogical approach, and the student population's needs. Self-Orientation = transparency about data use, honest communication about product limitations, and prioritizing learning outcomes over engagement metrics that serve the company's growth." + edtech_anti_patterns: + - "Investing in Credibility (logos, certifications, awards) while neglecting Reliability (the platform crashes during state testing week, or a critical feature breaks mid-semester). Teachers have zero tolerance for unreliability during instructional time." + - "Using student engagement data to optimize for company metrics (DAU, session length) rather than learning outcomes. Parents and teachers perceive this as high Self-Orientation — the company cares about its metrics, not their children's learning." + - "Treating trust-building as a sales activity that ends at purchase. In EdTech, trust must be earned continuously through the implementation process, the teacher's daily experience, and transparent communication about student data handling." + edtech_example: "A student assessment platform builds trust across the equation. Credibility: publishes all efficacy research (including studies that show limitations), maintains publicly viewable VPAT and FERPA compliance documentation, and partners with university research labs. Reliability: guarantees 99.99% uptime during testing windows with a dedicated incident response team during assessment periods, and freezes feature deployments for the two weeks before and during state testing. Intimacy: assigns a dedicated implementation specialist to each district who attends PD days and understands each school's unique student demographics. Self-Orientation minimized: publishes a Student Data Bill of Rights, never uses student data for advertising, and provides free data portability if the district switches providers." + benchmark_references: ["ferpa-coppa-compliance-status", "nps-segmented", "institutional-churn-rate"] + + - skill: "doblin-ten-types" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "The Ten Types of Innovation framework is highly instructive for EdTech because the sector over-indexes on Product Performance (content quality, adaptive algorithms) while underinvesting in the other nine types. The most powerful EdTech innovations often come from: Profit Model (shifting from per-student licensing to institution-wide flat-fee, or from one-time purchase to subscription), Network (teacher community and content-sharing ecosystems), Process (AI-enabled content creation at 1/10th traditional cost), Channel (teacher-first bottom-up adoption rather than top-down sales), Customer Engagement (gamification, streaks, social learning), and Service (embedded professional development, implementation support as a service). The framework helps EdTech founders recognize that building better content is necessary but insufficient — the innovation must also address how the product reaches institutions, how teachers adopt it, and how the business model sustains it." + edtech_anti_patterns: + - "Treating 'better content' or 'better adaptive algorithm' as sufficient differentiation. Content quality is Product Performance innovation — one of ten types, and the most easily replicated. Sustainable differentiation comes from combining multiple innovation types." + - "Ignoring Channel innovation. The distribution challenge in EdTech (reaching 14,000 US school districts, 4,000 universities, or 300,000 corporate L&D teams) is harder than the product challenge. Products that innovate on distribution win." + - "Skipping Service innovation. EdTech products that come with embedded professional development and ongoing teacher support outperform identical products sold without it. Service is an innovation type, not a cost center." + edtech_example: "Khan Academy's innovation maps across multiple types: Product Performance (adaptive practice exercises), Profit Model (free for learners, funded by philanthropy and district licensing), Channel (direct-to-student free access, bypassing institutional procurement), Customer Engagement (mastery-based progression, energy points, leaderboards), Network (teacher community sharing lesson plans and assignments), and Service (free teacher training and implementation resources). Competitors focused on one or two innovation types could not replicate the combination." + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate", "free-to-paid-conversion"] + + - skill: "eisenhower-matrix" + category: "frameworks" + edtech_relevance: "high" + edtech_context: "EdTech founders face extreme prioritization challenges because the multi-stakeholder nature of the business creates demands from every direction simultaneously. Teachers request features (Urgent to them, often Not Important strategically), administrators require compliance documentation (Urgent for the deal, Not Urgent until it is), students generate support requests (Urgent operationally, rarely Important strategically), and the academic calendar creates artificial urgency (everything must ship before September). The Eisenhower Matrix must classify EdTech-specific demands: compliance and accessibility work (Not Urgent/Important — until a deal is blocked, then Urgent/Important), efficacy research (Not Urgent/Important — consistently deprioritized despite being the single most valuable long-term investment), seasonal preparation (Urgent/Important during back-to-school, Urgent/Not Important the rest of the year)." + edtech_anti_patterns: + - "Treating every teacher feature request as Urgent/Important. Teachers are the implementers, not the buyers. Their requests deserve respect and a systematic feedback loop, but they should not drive the roadmap away from strategic priorities." + - "Deprioritizing efficacy research (Not Urgent/Important quadrant) indefinitely. Every semester without outcome data is a semester where institutional sales arguments weaken. Schedule efficacy work as a recurring commitment." + - "Allowing the back-to-school rush to consume all Q3 engineering capacity. Seasonal urgency is predictable — prepare for it in Q2 so that Q3 execution is smooth, not chaotic." + edtech_example: "An EdTech CEO reviews her priorities and discovers that 60% of her time is consumed by Urgent/Not Important tasks: responding to individual teacher support requests that should be handled by the CS team, reviewing marketing materials that the marketing lead should own, and attending conference planning meetings. Delegating these frees time for Not Urgent/Important work: building the district-level relationship network for next year's sales cycle, commissioning the efficacy study that will close enterprise deals in 18 months, and developing the product vision for the AI tutoring feature that will define the next growth phase." + benchmark_references: ["time-to-institutional-sale", "efficacy-evidence-strength"] + + - skill: "organisational-culture" + category: "frameworks" + edtech_relevance: "moderate" + edtech_context: "EdTech organizational culture must bridge two worlds: the mission-driven culture of education (impact, equity, student outcomes) and the performance-driven culture of technology (speed, metrics, growth). The most successful EdTech companies create a 'both/and' culture — rigorous about metrics and genuine about mission. This is harder than it sounds because tension between mission and metrics is constant: shipping a feature that improves engagement (metric) but does not improve learning (mission) is a cultural moment of truth. Hiring is complicated by the same tension: educators bring pedagogical depth but may resist speed and ambiguity; technologists bring execution speed but may lack educational empathy." + edtech_anti_patterns: + - "Treating 'mission' as a substitute for competitive compensation and career growth. EdTech's historically lower salaries (justified by mission) lead to talent attrition to higher-paying SaaS companies." + - "Hiring only educators or only technologists. The best EdTech teams include both — instructional designers who understand pedagogy and product managers who understand software development. The cultural work is integration." + edtech_example: "An EdTech company establishes a cultural practice called 'Learner Fridays' where every team member (including engineers, sales reps, and finance) spends two hours monthly tutoring students or observing classrooms. This practice bridges the education-technology cultural divide by ensuring everyone on the team has direct experience with the people the product serves. Engineering decisions improve because developers have seen students struggle with their UI. Sales conversations improve because reps can describe real classroom usage." + benchmark_references: ["nps-segmented", "teacher-adoption-rate"] + + - skill: "thinking-fast-and-slow" + category: "frameworks" + edtech_relevance: "moderate" + edtech_context: "System 1 and System 2 thinking dynamics affect EdTech decision-making at every level. Institutional buyers (System 2 territory) should make evidence-based procurement decisions but often rely on System 1 heuristics: brand familiarity, conference demos, and peer recommendations. Teachers (mixed) make System 1 adoption decisions based on first impressions of the product's interface and initial setup experience. Students (overwhelmingly System 1) decide within seconds whether a learning product is engaging or boring. The EdTech product designer must work with, not against, these thinking modes: design for System 1 in the student experience (intuitive, visually engaging, immediately rewarding) while providing System 2 ammunition (data, evidence, ROI) for the buyer experience." + edtech_anti_patterns: + - "Designing the purchasing experience for System 2 (rational evidence) while designing the product experience for System 2 (complex, feature-rich). Students and teachers need System 1 simplicity in the daily product experience." + - "Assuming institutional buyers make purely rational decisions. Conference booth design, sales rep charisma, and peer influence (System 1 factors) matter as much as efficacy data (System 2 factors) in procurement decisions." + edtech_example: "An adaptive learning platform applies dual-process theory to its multi-stakeholder design. For students (System 1): immediate visual feedback, no cognitive load from navigation, progress indicators that create dopamine-driven engagement. For teachers (System 1 first contact, System 2 sustained use): a 60-second setup wizard that gets the first assignment live immediately (System 1 ease), with deep customization and data analytics accessible for those who seek it (System 2 depth). For administrators (System 2): a structured evidence package with peer comparison data, efficacy research summaries, and total cost of ownership analysis." + benchmark_references: ["learner-engagement-rate", "teacher-adoption-rate"] + + # ───────────────────────────────────────────── + # GAME THEORY (4 skills) + # ───────────────────────────────────────────── + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + edtech_relevance: "high" + edtech_context: "The prisoner's dilemma appears in several EdTech competitive dynamics. Pricing: if all EdTech companies in a category hold prices at sustainable levels, the market is healthy. But each company has an incentive to offer deep discounts (or free tiers) to win institutional deals, driving a race to the bottom. Free content: companies that release high-quality free content attract users but reduce willingness to pay across the category. The cooperation question: should EdTech companies participate in open standards and shared data frameworks (cooperate) or build proprietary ecosystems (defect)? The iterated nature of EdTech competition (the same districts renew annually, the same conferences recur) favors tit-for-tat cooperation strategies." + edtech_anti_patterns: + - "Racing to free without a monetization strategy. Khan Academy can be free because it is philanthropically funded. For-profit EdTech companies that match free pricing without a sustainable model destroy their own category." + - "Refusing to participate in interoperability standards (LTI, xAPI, Ed-Fi) to protect lock-in. In EdTech, districts increasingly require interoperability. Non-cooperation on standards loses more deals than it protects." + edtech_example: "Two competing reading assessment platforms face a classic prisoner's dilemma around data portability. If both offer easy data export, teachers can switch freely — competition is on quality alone. If one offers portability and the other locks data in, the locked platform retains users through friction. Both locking data creates mutual distrust with districts. The cooperative equilibrium — both offering portability — wins because districts increasingly mandate data portability in RFPs, and the cooperative players win the RFPs while the defector loses them." + benchmark_references: ["institutional-churn-rate", "institutional-adoption-rate"] + + - skill: "information-asymmetry" + category: "game-theory" + edtech_relevance: "high" + edtech_context: "Information asymmetry is pervasive in EdTech and operates in multiple directions simultaneously. The EdTech company knows more about its product's actual efficacy (or lack thereof) than the institutional buyer. The teacher knows more about the product's real classroom utility than either the company or the administrator. The student's actual learning is opaque to everyone unless properly measured. Institutional buyers face adverse selection — they cannot easily distinguish between EdTech products that genuinely improve learning and those that merely look impressive in a demo. This asymmetry has driven the ESSA evidence movement and the growing demand for third-party efficacy validation. Companies that voluntarily reduce information asymmetry (publishing efficacy data, including negative results) build trust that becomes a competitive advantage." + edtech_anti_patterns: + - "Exploiting information asymmetry by presenting cherry-picked engagement metrics as evidence of learning improvement. Institutional buyers are becoming sophisticated enough to detect this, and the reputational damage is severe." + - "Ignoring the information asymmetry between administration and teachers. Products sold to administration based on dashboards and reports fail when teachers discover the product does not work in their classroom reality." + edtech_example: "A math assessment company reduces information asymmetry by publishing its complete efficacy research — including two studies that showed no significant improvement for specific student subgroups. The transparency initially alarmed the sales team, but the long-term impact was positive: districts trusted the company's claims because they had demonstrated willingness to share unfavorable results. The company's competitive close rate against companies with only positive (cherry-picked) evidence improved by 15%, because procurement committees valued honesty." + benchmark_references: ["efficacy-evidence-strength", "learning-outcomes-improvement", "institutional-adoption-rate"] + + - skill: "first-mover-strategy" + category: "game-theory" + edtech_relevance: "high" + edtech_context: "First-mover advantage in EdTech is weaker than in most technology markets due to the sector's inherent conservatism and slow adoption cycles. Being first to market with a new EdTech category (VR classrooms, blockchain credentials, AI tutoring) means being first to educate the market — a costly proposition when buyers are risk-averse institutions. However, first-mover advantage in specific niches is powerful: the first product to win a state adoption list slot, the first to achieve ESSA Tier 2 evidence in a category, or the first to build a teacher community around a pedagogy. In EdTech, 'first to trust' often matters more than 'first to market.' The company that builds institutional trust first — through evidence, compliance, and reliable implementation — captures long-term contracts that are difficult for later entrants to displace." + edtech_anti_patterns: + - "Assuming first-mover advantage in EdTech works like first-mover advantage in consumer tech. Education adopts slowly. Being first to market by two years may mean absorbing two years of market-education costs while a fast follower enters when the market is ready." + - "Racing to be first in a new EdTech category without first establishing the institutional trust infrastructure (compliance, evidence, PD) that enables institutional sales." + edtech_example: "Canvas (Instructure) did not invent the LMS — Blackboard and Moodle preceded it by years. Canvas was a fast follower that entered with a better user experience (teacher-focused design), open standards compliance, and a cloud-native architecture. The first movers had established the category and educated the market; Canvas won by being 'first to trust' with a modern, reliable, teacher-friendly platform. The lesson: in EdTech, being first to the category matters less than being first to solve the adoption barriers." + benchmark_references: ["institutional-adoption-rate", "teacher-adoption-rate"] + + - skill: "coalition-and-partnership-games" + category: "game-theory" + edtech_relevance: "high" + edtech_context: "Coalition and partnership dynamics in EdTech are uniquely complex because the ecosystem includes unusual partner types: textbook publishers (Pearson, McGraw-Hill, HMH), LMS platforms (Canvas, Google Classroom, Schoology), assessment organizations (College Board, ACT, NWEA), accreditation bodies, teachers' unions, state education departments, and philanthropic funders (Gates Foundation, Chan Zuckerberg Initiative). Coalition strategy must consider: which partnerships provide distribution (LMS integration is critical — a product not integrated with Google Classroom or Canvas is invisible in K-12), which provide credibility (research university partnerships, publisher endorsements), and which create dependency risk (over-reliance on a single platform partner). The Shapley value concept applies: each partner's contribution to the coalition determines their share of value." + edtech_anti_patterns: + - "Treating publisher partnerships as simple distribution deals. Publishers (Pearson, McGraw-Hill) are simultaneously partners, competitors, and platforms. The relationship requires careful game-theoretic analysis." + - "Building exclusively on Google Classroom or Canvas without a platform diversification strategy. Platform dependency in EdTech is as dangerous as it is in SaaS — one API change or competitive move can cut off distribution overnight." + edtech_example: "A STEM learning platform designs its coalition strategy. Tier 1 (critical integrations): Google Classroom, Canvas, Clever (single sign-on) — these are distribution prerequisites, not optional. Tier 2 (credibility partnerships): Stanford CREDO research partnership for efficacy validation, ISTE certification for teacher trust. Tier 3 (growth coalitions): state-level adoption partnerships in Texas and California during upcoming curriculum review cycles. Tier 4 (strategic hedging): relationship with two textbook publishers simultaneously, ensuring neither becomes a single point of dependency. The coalition game reveals that the most valuable partnership is not the largest company but the one that provides access to the adoption gatekeepers — state curriculum reviewers." + benchmark_references: ["institutional-adoption-rate", "time-to-institutional-sale"] + + # ───────────────────────────────────────────── + # NEGOTIATION (3 skills) + # ───────────────────────────────────────────── + + - skill: "competitive-negotiation" + category: "negotiation" + edtech_relevance: "high" + edtech_context: "Competitive negotiation in EdTech occurs in three primary contexts: institutional procurement (negotiating with district procurement officers who manage fixed budgets with specific funding source constraints), publisher/platform partnerships (negotiating revenue shares and integration terms with entities that are simultaneously partners and potential competitors), and fundraising (negotiating with EdTech-focused investors who apply sector-specific benchmarks). Institutional procurement negotiations are uniquely constrained: budgets are fixed and often tied to specific funding sources (Title I, ESSER, state grants) with usage restrictions. The negotiation is rarely about price alone — it is about contract structure, data handling terms, implementation support, and multi-year commitment." + edtech_anti_patterns: + - "Discounting aggressively to win institutional deals. EdTech companies that establish a pattern of deep discounting train procurement officers to always negotiate. Offer implementation support, additional training, or extended pilots instead of price cuts." + - "Negotiating contract terms without understanding the institution's funding source. Title I funds have different spending restrictions than general funds. A contract structure that aligns with the funding source's requirements closes faster." + - "Treating every institutional negotiation as transactional. Education relationships are long-term. A school district that feels squeezed in a negotiation will remember at renewal time." + edtech_example: "A learning analytics company negotiating a $150K district-wide contract faces pressure to discount by 40%. Instead of cutting price, the team identifies that the district's funding comes from a state innovation grant with a 'professional development' line item. They restructure the proposal: $100K for the platform license (10% discount from list) plus $50K for embedded PD services (which can be funded from the PD line item, accessing budget the district could not otherwise use for software). Total contract value unchanged; the district accesses additional funds; and the company delivers PD that increases adoption rates." + benchmark_references: ["average-contract-value", "time-to-institutional-sale", "institutional-acquisition-cost"] + + - skill: "cooperative-negotiation" + category: "negotiation" + edtech_relevance: "high" + edtech_context: "Cooperative negotiation is the foundation of EdTech partnership development and institutional relationship management. EdTech partnerships include: LMS/platform integrations (building within Canvas, Google Classroom, or Clever ecosystems), content partnerships (co-developing curricula with publishers or subject matter experts), research partnerships (collaborating with universities on efficacy studies), and district partnership models (co-designing implementation with institutional customers). The cooperative dimension is essential because EdTech relationships are long-term by nature — a district contract runs for years, a publisher relationship spans product cycles, and a research partnership produces results over multiple academic years." + edtech_anti_patterns: + - "Entering publisher partnerships without clearly defining IP ownership for co-created content. Content ownership disputes in EdTech are common and destructive." + - "Treating institutional customers as buyers rather than partners. The most successful EdTech companies co-design implementation plans, co-author case studies, and co-present at conferences with their customer districts." + edtech_example: "A small EdTech company negotiates a content partnership with a major publisher. Rather than accepting the publisher's standard licensing terms (exclusive rights, minimal royalty, publisher-controlled distribution), the company uses cooperative negotiation to propose a deeper structure: co-branded content with shared IP, the EdTech company's adaptive platform delivering the publisher's content, revenue sharing based on institutional sales, and joint marketing at publisher-sponsored events. The cooperative approach creates mutual dependency that protects the smaller company while giving the publisher access to technology it lacks." + benchmark_references: ["institutional-adoption-rate", "expansion-revenue-institutional"] + + - skill: "delivering-the-deal" + category: "negotiation" + edtech_relevance: "high" + edtech_context: "Deal execution in EdTech has unique characteristics shaped by institutional procurement. Procurement cycles are calendar-driven: K-12 budgets are approved May-August, higher ed procurement follows fiscal years (often July-June), and corporate L&D budgets align with calendar or fiscal year-end. Deals stall in three characteristic ways: (1) compliance review — FERPA/COPPA assessment, data privacy agreement review, accessibility audit, and security questionnaire can each add 2-4 weeks; (2) stakeholder approval chain — curriculum director, IT director, privacy officer, superintendent, and school board may all require sign-off; (3) pilot-to-purchase conversion — free pilots that never convert because no success criteria were defined upfront. The skill of delivering the EdTech deal means preparing compliance documentation proactively, managing the multi-stakeholder approval process, and designing pilots with clear conversion criteria." + edtech_anti_patterns: + - "Allowing compliance review to be sequential rather than parallel. Run FERPA review, accessibility audit, and IT security review simultaneously. Sequential processing doubles the timeline." + - "Running free pilots without defined success metrics and a contractual path to purchase. Open-ended pilots are where EdTech deals go to die." + - "Missing the budget window. A deal that is ready to sign in September but needed board approval in June will wait 12 months. Work backwards from budget approval dates." + edtech_example: "An EdTech company creates a 'District Deal Kit' containing: pre-completed Student Data Privacy Agreement (aligned with the SDPC National DPA template), VPAT for accessibility compliance, penetration test results and SOC 2 report, FERPA compliance attestation, a standard order form with three pricing options (per-student, school-level flat fee, district-wide license), and a 90-day pilot agreement with success metrics and auto-conversion clause. This kit reduces average time-to-close from 8 months to 4 months by eliminating the three most common deal stalls before they occur." + benchmark_references: ["time-to-institutional-sale", "average-contract-value"] + + # ───────────────────────────────────────────── + # THINKING (3 skills) + # ───────────────────────────────────────────── + + - skill: "enemies-of-clear-thinking" + category: "thinking" + edtech_relevance: "critical" + edtech_context: "EdTech operators face sector-specific cognitive traps amplified by the mission-driven nature of education and the multi-stakeholder complexity. Survivorship bias: studying Duolingo and Khan Academy while ignoring the thousands of well-funded EdTech companies that failed. Mission creep bias: expanding into every underserved learner population because the mission demands it, rather than focusing on the market segment where the product excels. Availability bias: over-weighting the most vocal teacher's feedback while ignoring usage data from thousands of silent users. Sunk cost fallacy: continuing to invest in content areas or market segments because of existing content investment rather than pivot based on engagement and outcome data. Confirmation bias: interpreting modest engagement as 'teachers love it' while ignoring that 70% of licensed teachers never logged in." + edtech_anti_patterns: + - "Using engagement metrics (time on platform, sessions per week) as evidence of learning when they are merely evidence of usage. Engagement without outcomes is entertainment, not education." + - "Assuming that because the mission is noble, the business model is secondary. The most impactful EdTech companies are commercially sustainable — unsustainable companies cannot serve learners long-term." + - "Anchoring on the initial target segment (e.g., 'Title I schools') when the product-market fit data points to a different segment (e.g., 'suburban schools seeking enrichment'). Follow the data, not the narrative." + edtech_example: "An EdTech CEO reviews metrics and concludes the business is healthy: 200,000 registered learners, 45% teacher satisfaction score, and 30 new institutional contracts this year. A clear-thinking advisor spots the hidden problems: of 200,000 registered learners, only 35,000 were active last month (82.5% registered but inactive). The 45% teacher satisfaction is a response rate, not an NPS score — and only enthusiasts respond. Of 30 new contracts, 22 came from a single ESSER funding source that expired in September 2024. Every headline metric masks a structural problem that clear thinking would surface." + benchmark_references: ["learner-engagement-rate", "teacher-adoption-rate", "nps-segmented"] + + - skill: "evaluating-and-deciding" + category: "thinking" + edtech_relevance: "high" + edtech_context: "EdTech operators make decisions that span the fast-reversible to slow-irreversible spectrum. Fast-reversible: UI changes, gamification adjustments, marketing messaging, individual teacher support approaches. These should be decided and tested within days. Slow-reversible: pricing structure, content format (video vs. text vs. interactive), LMS platform integrations. These take weeks to implement and months to evaluate. Irreversible: curriculum alignment decisions (aligning to Common Core vs. state standards locks product direction), technology architecture (choosing a content delivery approach), market segment focus (K-12 vs. higher ed vs. corporate), and publisher partnerships with exclusivity clauses. The decision framework must also account for academic-calendar constraints: decisions that affect the student experience should ship at semester boundaries, not mid-course." + edtech_anti_patterns: + - "Applying semester-boundary deliberation to decisions that should be made in days. Testing a new onboarding flow does not require waiting for a semester break." + - "Making irreversible architecture decisions (monolith vs. microservices, content management approach) with the speed appropriate for reversible UI decisions." + - "Deciding by committee across all three stakeholder representatives. Buyer-facing decisions need the sales team; teacher-facing decisions need the education team; student-facing decisions need the product team. Assign clear owners." + edtech_example: "An EdTech product team debates whether to build Spanish language support (irreversible: requires content translation, cultural adaptation, and Spanish-speaking support staff) or improve the analytics dashboard (reversible: UI changes that can be tested and iterated). Using the reversibility framework: invest one sprint in dashboard improvements (test, learn, iterate), then make the Spanish-language decision with data from the customer pipeline — how many deals are blocked by lack of Spanish? The dashboard decision was being treated as equally weighty when it could be resolved in two weeks." + benchmark_references: ["learner-engagement-rate", "institutional-adoption-rate"] + + - skill: "defining-and-exploring-problems" + category: "thinking" + edtech_relevance: "high" + edtech_context: "Problem definition in EdTech is complicated by the multi-stakeholder value chain — different stakeholders often define the same problem differently. 'Low student engagement' might be defined as: by the admin — 'we are not getting ROI on our technology investment'; by the teacher — 'the product does not fit my lesson flow'; by the student — 'this is boring.' Each definition leads to a different solution. The real problem may be none of these — it may be that the product was purchased for state test prep but deployed in a school that values project-based learning. Exploring the problem requires talking to all three stakeholders and triangulating their perspectives, plus examining the implementation context (how the product was deployed, by whom, with what training, and with what expectations)." + edtech_anti_patterns: + - "Defining the problem from one stakeholder's perspective only. The admin who says 'engagement is low' and the teacher who says 'it is too hard to set up' and the student who says 'it is boring' are describing three different symptoms of possibly the same or possibly different root causes." + - "Assuming the problem is the product when it may be the implementation. An excellent product poorly implemented looks identical to a mediocre product well implemented." + edtech_example: "A reading platform is experiencing high institutional churn. The obvious problem definition: 'the product does not work.' Multi-stakeholder exploration reveals: administrators are disappointed because the promised test score improvements have not materialized (their problem: unmet expectations set during the sales process). Teachers report the product is useful but they only use it twice a week, not daily as designed (their problem: it does not fit the reading block schedule). Students find the content appropriate but report that 'reading on a screen for 30 minutes hurts their eyes' (their problem: ergonomic). The root cause is not the product or the content — it is a mismatch between the product's intended usage pattern (daily 15-minute sessions) and the deployment pattern (biweekly 30-minute sessions). The fix is implementation coaching, not product changes." + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate", "institutional-churn-rate"] + + # ───────────────────────────────────────────── + # LEADERSHIP & AI (5 skills) + # ───────────────────────────────────────────── + + - skill: "leading-through-change" + category: "leadership" + edtech_relevance: "high" + edtech_context: "Leading through change in EdTech operates on two levels simultaneously: internal organizational change (scaling the team, pivoting the product, adjusting the business model) and external institutional change (helping customer institutions adopt the product, which is itself a change management process). The EdTech leader must be a change management expert not just for their own company but for their customers' organizations. Every institutional sale creates a change initiative within the customer organization — new workflows for teachers, new expectations for students, new data for administrators. EdTech leaders who understand this become strategic advisors to their customers, not just vendors." + edtech_anti_patterns: + - "Underestimating the change resistance within educational institutions. Schools are among the most change-resistant organizations in any sector. Teachers have been 'technologized' repeatedly with tools that increased their workload and disappeared after the grant funding ended." + - "Applying Silicon Valley change management ('move fast and break things') to education. Institutions that serve children have legitimate reasons for proceeding cautiously." + edtech_example: "An EdTech CEO leads two simultaneous change initiatives. Internally: restructuring from a content-creation company to a platform company, requiring engineering team expansion, content team reskilling, and go-to-market motion change. Externally: supporting a 500-school district through a three-year technology transformation where the company's product is the cornerstone. The CEO recognizes that the internal change must align with the external change — the platform cannot evolve faster than the district can absorb. The leadership challenge is managing both clocks: startup speed internally, institutional speed externally." + benchmark_references: ["teacher-adoption-rate", "institutional-churn-rate"] + + - skill: "ai-vision-and-strategy" + category: "ai-leadership" + edtech_relevance: "critical" + edtech_context: "AI is transforming every EdTech category simultaneously, creating the most significant strategic inflection point since the internet entered classrooms. AI tutoring (ChatGPT, Khanmigo, Google's LearnLM) threatens every product that primarily delivers content — if an AI can explain any concept at any level at any time for free, what is the value of a content library? AI assessment threatens every product that primarily measures knowledge — if AI can evaluate open-ended responses, what is the value of a multiple-choice platform? AI content creation threatens every product with a significant content investment — if AI can generate learning materials at near-zero cost, what is the value of expensive human-created content? The strategic question for every EdTech company: what does your product do that AI cannot do alone? The durable answers typically involve: human connection (teacher facilitation, peer learning), institutional trust (compliance, data governance), implementation support (change management, PD), and evidence of outcomes (rigorous efficacy data)." + edtech_anti_patterns: + - "Adding 'AI-powered' to the marketing without fundamentally rethinking the value proposition. If the product's core value is content delivery, AI commoditizes that value. A thin AI wrapper does not solve the strategic problem." + - "Ignoring AI because 'education is human.' AI will not replace teachers, but EdTech products that do not incorporate AI will be replaced by those that do." + - "Treating AI as purely a cost-reduction tool (cheaper content creation, automated grading) without exploring AI as a value-creation tool (personalized learning paths, real-time formative assessment, natural language tutoring)." + edtech_example: "A vocabulary learning platform faces the AI question: ChatGPT can teach vocabulary for free. The strategic response: redefine the value proposition from 'content delivery' (commoditized by AI) to 'evidence-based outcomes with institutional accountability.' The product integrates AI-powered personalization and natural language practice, but wraps it in: standards-aligned curriculum (institution value), progress tracking dashboards (teacher value), efficacy evidence (buyer value), and data privacy compliance (trust value). The AI does the teaching; the product does the institutional integration. This is the value AI alone cannot provide." + benchmark_references: ["efficacy-evidence-strength", "learner-engagement-rate", "gross-margin"] + + - skill: "inclusive-leadership" + category: "leadership" + edtech_relevance: "high" + edtech_context: "Inclusive leadership in EdTech carries a unique moral and commercial obligation: the products serve diverse learner populations (different abilities, languages, socioeconomic backgrounds, cultural contexts), and exclusion in the product directly translates to exclusion in learning. Accessibility (ADA/Section 508/WCAG compliance) is not an edge case — it is a legal requirement and an ethical imperative. Multilingual support is not a nice-to-have when serving school districts where 20-40% of students are English Language Learners. Cultural representation in content (images, names, scenarios, contexts) affects whether learners see themselves in the learning experience. Inclusive leadership in EdTech means building teams that reflect the diversity of learners served, testing products with diverse user populations, and making accessibility a first-class design constraint rather than a retrofit." + edtech_anti_patterns: + - "Treating accessibility as a compliance checkbox rather than a design principle. Products designed for accessibility from the start are better for all users, not just users with disabilities." + - "Building content and products that reflect only the dominant cultural context. A math word problem about skiing trips excludes students who have never seen snow. An EdTech company serving a diverse population must audit content for cultural bias." + edtech_example: "An EdTech company serving K-12 districts in the US Southwest discovers that its reading passages, illustrations, and scenario contexts are overwhelmingly suburban and Anglo-American. Usage data shows significantly lower engagement from Hispanic and Native American students. The inclusive leadership response: hire content creators from the communities served, commission a cultural relevance audit, redesign the adaptive engine to serve culturally relevant content based on school demographics, and create a Community Advisory Board with parents, teachers, and community leaders from underrepresented populations. Engagement gaps close by 40% within one academic year." + benchmark_references: ["accessibility-compliance-score", "learner-engagement-rate", "nps-segmented"] + + - skill: "employee-engagement-retention" + category: "leadership" + edtech_relevance: "moderate" + edtech_context: "EdTech employee engagement faces a unique tension between mission motivation and market-rate compensation. Many EdTech employees choose the sector because of a genuine desire to improve education, accepting lower-than-market salaries. This mission alignment is a strength until it is exploited — companies that systematically pay below market because 'the mission should be enough' experience talent attrition to higher-paying SaaS companies. The retention challenge is compounded by the academic-calendar-driven work rhythm: intense periods before and during back-to-school season, followed by quieter periods (a pattern that can lead to either burnout or boredom). The most engaged EdTech teams have direct exposure to the learners and teachers they serve." + edtech_anti_patterns: + - "Using mission as a justification for below-market compensation indefinitely. Mission attracts talent; fair compensation retains it." + - "Hiring educators into roles that require technology skills they do not have, then failing to invest in their development. The education-to-tech transition requires genuine support." + edtech_example: "An EdTech company addresses retention by implementing 'Classroom Connect' — every employee spends one day per quarter in a partner school observing the product in use and talking to teachers and students. This direct mission connection reduces attrition by 25% compared to the previous year, because employees can see the impact of their work. The company also adjusts compensation to 90th percentile of EdTech (not SaaS — that expectation is set clearly in hiring) and offers education stipends for employees' own learning." + benchmark_references: ["nps-segmented"] + + - skill: "strategic-thinking-and-alignment" + category: "leadership" + edtech_relevance: "high" + edtech_context: "Strategic alignment in EdTech requires reconciling three timelines that rarely sync: the product development timeline (agile sprints, quarterly releases), the academic calendar (semester-based adoption, annual renewals), and the institutional procurement timeline (12-18 month sales cycles, budget-year dependencies). A strategy that is brilliant on a quarterly SaaS cadence may be misaligned with the September-to-June reality of the education market. Strategic alignment also means ensuring that the product, sales, customer success, and research teams share a coherent understanding of which stakeholder problems the company solves, in which order, at which stage of the adoption journey." + edtech_anti_patterns: + - "Setting strategy on a SaaS quarterly cadence when the business operates on an academic-year rhythm. Strategic planning should begin in spring for the following academic year." + - "Misaligning product development and sales timelines. A feature promised for back-to-school that ships in October is worse than a feature that ships a year earlier or a year later — it misses the adoption window." + edtech_example: "An EdTech company aligns its strategic calendar to the academic year. Q1 (Sept-Nov): deploy and support new institutional customers through first semester, collect engagement data. Q2 (Dec-Feb): analyze first-semester data, produce efficacy reports, begin renewal conversations and expansion pitches for existing customers. Q3 (Mar-May): heavy sales season — present evidence and ROI reports for budget decisions, close expansion deals, prospect new institutions. Q4 (Jun-Aug): prepare for back-to-school — onboard new institutional customers, deliver teacher PD, release major product updates. Engineering sprints align with this calendar: no major UX changes September-November (teachers are establishing routines), major releases in July-August (pre-back-to-school)." + benchmark_references: ["time-to-institutional-sale", "teacher-adoption-rate", "institutional-churn-rate"] diff --git a/plugins/foreman/content/industry-packs/edtech/edtech-templates.yaml b/plugins/foreman/content/industry-packs/edtech/edtech-templates.yaml new file mode 100644 index 0000000..5d5214f --- /dev/null +++ b/plugins/foreman/content/industry-packs/edtech/edtech-templates.yaml @@ -0,0 +1,1004 @@ +# EdTech Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for EdTech companies. The output agent loads these rules +# when generating documents with the EdTech industry pack active. +# +# Key EdTech template principles: +# 1. Institutional vs. consumer distinction in every investor/board template — +# EdTech companies must clearly delineate B2B (institutional) and B2C (consumer) +# metrics, strategies, and narratives. +# 2. Efficacy data in every product template — learning outcomes evidence is +# expected in any document that discusses product performance. +# 3. Multi-stakeholder analysis in every strategic template — buyer, implementer, +# and user perspectives must be addressed separately. +# 4. Academic calendar awareness — planning templates must align with the +# September-August (K-12) or semester-based (higher ed) rhythm. +# +# Adaptation types: +# as-is — The template works without modification for EdTech companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for EdTech context. + +pack_metadata: + sector: "edtech" + display_name: "EdTech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech unit economics must be reported separately for institutional and consumer segments because the metrics, benchmarks, and economics diverge completely. Institutional: ACV, institutional CAC, institutional LTV, teacher adoption rate as a unit-economics driver. Consumer: revenue per learner, student CAC, LTV by subscription tier, free-to-paid conversion rate." + field_changes: + - field: "Revenue per unit" + sector_label: "Revenue Segmentation: Institutional vs. Consumer" + sector_guidance: "Report separately: Institutional (total contract revenue, ACV, revenue per institution, revenue per learner within institutions) and Consumer (subscription revenue, revenue per paying learner, ARPU by tier). Blended metrics are misleading — always segment." + - field: "Cost per unit" + sector_label: "Acquisition Cost (Dual-Channel)" + sector_guidance: "Institutional CAC: include sales salaries, conference expenses, pilot costs, compliance documentation, and implementation support. Consumer CAC: include marketing, content marketing, app store optimization, and referral program costs. Report student-level CAC derived from institutional deals." + - field: "Margin per unit" + sector_label: "Gross Margin by Revenue Type" + sector_guidance: "EdTech COGS includes content creation/licensing amortization, hosting, instructor costs (for live models), support, and implementation. Segment margins: pure platform (70-80%), content marketplace (55-70%), OPM (30-50%), live instruction (20-40%)." + - field: "Lifetime value" + sector_label: "LTV by Segment" + sector_guidance: "Institutional LTV: ACV x average contract duration (in years) x gross margin %. Consumer LTV: ARPU x average subscriber lifetime (months) x gross margin %. Report both alongside the institutional churn rate and learner retention rate that drive them." + - field: "Acquisition cost" + sector_label: "CAC Payback Period by Segment" + sector_guidance: "Institutional: CAC / (ACV x Gross Margin %). Target: < 18 months. Consumer: CAC / (Monthly ARPU x Gross Margin %). Target: < 12 months." + - field: "Unit economics ratio" + sector_label: "LTV:CAC by Segment" + sector_guidance: "Report for each segment. Institutional LTV:CAC above 3x is strong. Consumer LTV:CAC above 3x is challenging to achieve in EdTech due to low consumer willingness to pay." + sections_to_add: + - section_name: "EdTech Metrics Dashboard" + placement: "before:Revenue Segmentation: Institutional vs. Consumer" + description: "Core EdTech metrics investors expect to see at a glance." + fields: + - "Total active learners (MAL)" + - "Institutional customers (count and ACV)" + - "Consumer subscribers (count and ARPU)" + - "Learner engagement rate" + - "Content completion rate" + - "Teacher adoption rate (for institutional)" + - "NPS segmented (learner / teacher / admin)" + - section_name: "Efficacy Economics" + placement: "after:LTV:CAC by Segment" + description: "The relationship between efficacy evidence and unit economics — unique to EdTech." + fields: + - "Efficacy evidence tier (ESSA level or equivalent)" + - "Learning outcomes improvement data (effect size or % gain)" + - "Efficacy research investment (annual spend)" + - "Estimated revenue attributable to efficacy evidence (deals won citing evidence)" + - section_name: "Content Economics" + placement: "end" + description: "Content creation and leveraging economics specific to EdTech." + fields: + - "Content creation cost per hour of learning" + - "Content-to-revenue ratio" + - "Content library size and growth rate" + - "Content shelf life and update frequency" + sections_to_remove: [] + benchmark_references: ["average-contract-value", "student-acquisition-cost", "institutional-acquisition-cost", "revenue-per-learner", "gross-margin", "content-creation-cost", "content-to-revenue-ratio", "learner-engagement-rate", "efficacy-evidence-strength"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech investor updates must report metrics on an academic-calendar basis and clearly distinguish institutional from consumer performance. EdTech-specific investors expect efficacy data and adoption metrics alongside financial performance." + field_changes: + - field: "Financial highlights" + sector_label: "EdTech KPIs" + sector_guidance: "Report: Total Revenue (institutional + consumer), Institutional ARR/ACV, Consumer MRR/ARPU, Growth Rate (YoY for institutional, MoM for consumer), Cash Balance, Runway. Present as a table with current period, prior period, and trend. Note academic calendar context — compare to same period prior year, not prior month, for institutional metrics." + - field: "Key metrics" + sector_label: "Adoption and Engagement Metrics" + sector_guidance: "Report: New institutional customers, Active learners (MAL), Teacher adoption rate (for institutional), Content completion rate, NPS (segmented), and any efficacy milestones. Choose 3-5 metrics most relevant to the current company focus." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one quantified win: a named institution closed (with ACV and learner count), an efficacy milestone (study completed, outcome published), or a product milestone with measurable adoption impact." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges. Common EdTech challenges to report honestly: seasonal engagement decline, institutional churn at contract boundaries, teacher adoption difficulties, and competition from free alternatives or AI tools." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "EdTech-specific asks: introductions to district superintendents or university provosts, connections to education conference organizers, introductions to potential research partners, and hiring referrals for EdTech hybrid roles." + sections_to_add: + - section_name: "Academic Calendar Context" + placement: "after:EdTech KPIs" + description: "Context that helps investors interpret metrics against the academic calendar." + fields: + - "Current position in academic calendar (start of year, mid-year, end of year, summer)" + - "Seasonal adjustment notes (e.g., 'MAL declined 30% due to summer — consistent with prior year')" + - "Next procurement window timing and pipeline" + sections_to_remove: [] + benchmark_references: ["average-contract-value", "learner-engagement-rate", "teacher-adoption-rate", "nps-segmented"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech competitive analysis must map competitors across traditional EdTech products, free alternatives, AI tools, and publishers — a broader competitive set than most sectors. The brief must address the unique EdTech dynamic where the most dangerous competitor may be 'no technology at all' or 'free content.'" + field_changes: + - field: "Competitor overview" + sector_label: "EdTech Competitive Map" + sector_guidance: "Map competitors across four categories: (1) Direct EdTech competitors — same category, same segment. (2) Free alternatives — Khan Academy, YouTube, OER, ChatGPT. (3) Publisher-technology hybrids — Pearson, McGraw-Hill, HMH expanding into technology. (4) AI platforms — general-purpose AI providing competing functionality. Position on a 2x2: X-axis = segment (K-12 to Corporate), Y-axis = delivery model (content to platform)." + - field: "Competitive advantages" + sector_label: "EdTech Defensibility Analysis" + sector_guidance: "Assess along EdTech-specific dimensions: efficacy evidence moat (published research), institutional relationships (depth and breadth of school/university partnerships), teacher community (educators who advocate for the product), content depth (proprietary, curriculum-aligned content), data asset (learner interaction data that improves the adaptive engine), and compliance infrastructure (FERPA, COPPA, accessibility certifications)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize: (1) Direct competitor feature parity. (2) Free alternative improvement (Khan Academy adding AI features). (3) AI commoditization (ChatGPT-level tutoring for free). (4) Publisher platform expansion (Pearson building your product's function). (5) Institutional non-adoption (the biggest competitor in EdTech is often 'the way we have always done it')." + sections_to_add: + - section_name: "Free Alternative Threat Assessment" + placement: "after:Threat Vectors" + description: "Specific assessment of free alternatives that set the price ceiling." + fields: + - "Free alternatives available to the target learner population" + - "Capability comparison: what the free alternative does well vs. what it lacks" + - "Premium justification: why institutions/learners should pay for this product" + - "Trend analysis: are free alternatives improving faster than the paid product?" + - section_name: "AI Disruption Assessment" + placement: "after:Free Alternative Threat Assessment" + description: "Assessment of how AI tools affect the EdTech competitive landscape." + fields: + - "Which product capabilities can be replicated by general-purpose AI?" + - "Which capabilities require institutional integration that AI alone cannot provide?" + - "How is the company incorporating AI to strengthen its position?" + - "What is the timeline for AI to reach 'good enough' in the product's core function?" + sections_to_remove: [] + benchmark_references: ["institutional-adoption-rate", "efficacy-evidence-strength", "nps-segmented"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech pitch decks must address investor concerns specific to the sector: long institutional sales cycles, competition from free content, seasonal revenue patterns, and the need for efficacy evidence. The deck should clearly present the institutional vs. consumer model choice and demonstrate efficacy." + field_changes: + - field: "Market opportunity" + sector_label: "EdTech Market Opportunity" + sector_guidance: "Present TAM/SAM/SOM with EdTech-specific sizing: (target institutions x ACV) for institutional, or (target learner population x willingness to pay x conversion rate) for consumer. Include education spending data (HolonIQ: $6.5T global education, $400B+ EdTech projected by 2030). Address policy tailwinds (digital learning mandates, AI in education adoption)." + - field: "Business model" + sector_label: "EdTech Business Model" + sector_guidance: "Cover: revenue model (institutional licensing, consumer subscription, freemium, OPM, marketplace), pricing structure (per-student, per-seat, institution-wide), customer segments with the buyer-implementer-user distinction, and the go-to-market motion (top-down institutional sales, bottom-up teacher adoption, consumer growth)." + - field: "Traction" + sector_label: "EdTech Traction Metrics" + sector_guidance: "Dedicated slide with: Revenue trajectory (segmented), Active learners (MAL), Institutional customers (count and ACV), Teacher adoption rate, Content completion rate, and Efficacy evidence. This slide must tell both the business story (revenue, growth) and the impact story (learners served, outcomes improved)." + sections_to_add: + - section_name: "Efficacy Evidence Slide" + placement: "after:EdTech Traction Metrics" + description: "Dedicated efficacy presentation that EdTech investors expect." + fields: + - "Learning outcomes data (effect size or improvement percentage)" + - "Study design description (pilot, quasi-experimental, RCT)" + - "Student testimonials with quantified impact" + - "Efficacy roadmap (planned studies and evidence tier advancement)" + - section_name: "Multi-Stakeholder Value Slide" + placement: "after:Efficacy Evidence Slide" + description: "Demonstrates understanding of EdTech's buyer-implementer-user complexity." + fields: + - "Buyer value proposition (what the admin/procurement officer gets)" + - "Implementer value proposition (what the teacher/trainer gets)" + - "User value proposition (what the learner gets)" + - "How each stakeholder's needs are served simultaneously" + - section_name: "Go-to-Market Slide" + placement: "after:Multi-Stakeholder Value Slide" + description: "EdTech GTM must address the procurement cycle and multi-stakeholder adoption chain." + fields: + - "GTM motion (institutional sales, teacher-first adoption, consumer growth, or hybrid)" + - "Sales cycle description and optimization strategy" + - "Teacher adoption strategy (PD, onboarding, community)" + - "Procurement facilitation (compliance readiness, pilot-to-purchase path)" + sections_to_remove: [] + benchmark_references: ["average-contract-value", "institutional-adoption-rate", "learner-engagement-rate", "efficacy-evidence-strength", "teacher-adoption-rate"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "An EdTech strategic one-pager must anchor analysis in the multi-stakeholder value chain, efficacy positioning, and the unique competitive dynamics of education markets." + field_changes: + - field: "Strategic position" + sector_label: "EdTech Strategic Position" + sector_guidance: "Frame in EdTech terms: market segment (K-12 / higher ed / corporate / consumer), stakeholder alignment (which stakeholder is the primary wedge — buyer, teacher, or learner?), competitive differentiation (vs. paid competitors AND free alternatives), and the efficacy moat (strength of outcome evidence)." + - field: "Key metrics" + sector_label: "EdTech Health Metrics" + sector_guidance: "Core 6: Revenue + growth rate, Institutional retention rate, Learner engagement rate, Teacher adoption rate, Efficacy evidence tier, Gross margin. Compare each to EdTech stage-appropriate benchmarks." + sections_to_add: + - section_name: "Multi-Stakeholder Alignment Assessment" + placement: "end" + description: "Assessment of whether the product serves all three stakeholders in the value chain." + fields: + - "Buyer satisfaction and renewal likelihood" + - "Implementer (teacher/trainer) adoption and satisfaction" + - "User (learner) engagement and outcome data" + - "Alignment gaps and strategic implications" + sections_to_remove: [] + benchmark_references: ["institutional-churn-rate", "learner-engagement-rate", "teacher-adoption-rate", "efficacy-evidence-strength", "gross-margin"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech market sizing must use education-specific methodologies and address unique market dynamics: the role of government funding, policy-driven demand shifts, the academic calendar, and the split between institutional and consumer segments." + field_changes: + - field: "Total addressable market" + sector_label: "EdTech TAM / SAM / SOM" + sector_guidance: "Use bottom-up sizing by segment: K-12 = (target districts x schools/district x ACV/school), Higher Ed = (target institutions x departments x ACV), Corporate = (target companies x L&D budget allocation). Cross-reference with HolonIQ global EdTech spending data. Address the 'free content' TAM adjustment — not all learners represent revenue potential." + - field: "Market dynamics" + sector_label: "Education Market Dynamics" + sector_guidance: "Address: policy environment (ESSA, state mandates, federal funding programs), procurement cycle structure (budget timing, adoption lists, evaluation processes), competitive landscape (direct, free, AI, publishers), and demographic trends (K-12 enrollment, higher ed demographic cliff, lifelong learning growth)." + sections_to_add: + - section_name: "Policy and Funding Environment" + placement: "after:Education Market Dynamics" + description: "EdTech-specific analysis of the funding and policy landscape." + fields: + - "Federal funding programs relevant to the product (Title I, Title IV, Perkins, WIOA)" + - "State-level policy tailwinds (digital learning mandates, curriculum adoption cycles)" + - "Funding sustainability assessment (one-time vs. recurring funding sources)" + - section_name: "AI Impact on Market" + placement: "end" + description: "Assessment of how AI changes the EdTech market opportunity." + fields: + - "AI-driven market expansion (new use cases enabled by AI)" + - "AI-driven market contraction (existing functions commoditized by AI)" + - "Net market impact and company positioning" + sections_to_remove: [] + benchmark_references: ["average-contract-value", "institutional-adoption-rate"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech due diligence has specific focus areas: efficacy evidence validation, multi-stakeholder satisfaction assessment, compliance verification (FERPA, COPPA, accessibility), and revenue sustainability analysis given funding-source dependencies." + field_changes: + - field: "Financial review" + sector_label: "EdTech Financial Verification" + sector_guidance: "Verify: revenue segmentation (institutional vs. consumer), ACV calculation, institutional churn rate (logo and revenue), funding-source dependency analysis (what % of revenue comes from time-limited grants?), seasonal revenue pattern, and gross margin by segment." + - field: "Operational review" + sector_label: "Adoption and Retention Review" + sector_guidance: "Review: teacher adoption rates by institution, learner engagement data by cohort, NPS by stakeholder segment, content completion rates, implementation success rates, and support ticket volume and resolution." + sections_to_add: + - section_name: "Efficacy Evidence Due Diligence" + placement: "after:Adoption and Retention Review" + description: "EdTech-specific assessment of learning outcomes evidence." + fields: + - "Study designs reviewed (pilot, quasi-experimental, RCT)" + - "Effect sizes and statistical significance of outcome claims" + - "Independence of research (self-conducted vs. third-party)" + - "ESSA evidence tier assessment" + - "Generalizability of results (populations, settings, implementations)" + - section_name: "Compliance Due Diligence" + placement: "after:Efficacy Evidence Due Diligence" + description: "Education-sector regulatory compliance assessment." + fields: + - "FERPA compliance verification" + - "COPPA compliance (if product serves children under 13)" + - "Accessibility compliance (WCAG 2.1 AA / Section 508 / VPAT status)" + - "State data privacy agreement participation" + - "Data handling practices (storage, retention, deletion, portability)" + - section_name: "Content and IP Review" + placement: "end" + description: "Assessment of content assets and intellectual property." + fields: + - "Content ownership (original, licensed, user-generated, AI-generated)" + - "Content update cycle and standards alignment currency" + - "Content creation cost structure and scalability" + - "Third-party content licensing terms and renewal risk" + sections_to_remove: [] + benchmark_references: ["institutional-churn-rate", "learner-engagement-rate", "teacher-adoption-rate", "efficacy-evidence-strength", "ferpa-coppa-compliance-status", "accessibility-compliance-score"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not EdTech-specific. Standard venture capital cap table formats apply regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech decision rationale memos should frame decisions in multi-stakeholder terms — how does this decision affect the buyer, the implementer, and the user — and reference efficacy implications." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Multi-Stakeholder)" + sector_guidance: "Frame the decision through all three stakeholder lenses: How does this affect institutional buyers (procurement, compliance, evidence)? How does this affect teachers/implementers (workflow, time, PD)? How does this affect learners (engagement, outcomes, experience)?" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "EdTech exit scenarios involve acquirer categories specific to the sector: publishers (Pearson, McGraw-Hill, HMH), LMS platforms (Instructure, PowerSchool), assessment companies (ACT, ETS, NWEA), large EdTech platforms (Coursera, Chegg), and PE firms specializing in education (Vista Equity, Thoma Bravo). Valuation multiples differ from general SaaS due to lower growth rates and margin profiles." + field_changes: + - field: "Valuation methodology" + sector_label: "EdTech Valuation Multiples" + sector_guidance: "EdTech companies are valued on revenue multiples modulated by growth, margins, and institutional retention. Public EdTech comps: Duolingo (premium consumer), Coursera (marketplace), Instructure (institutional platform), PowerSchool (K-12 SIS). Note: EdTech multiples are generally 20-40% lower than general SaaS due to lower growth rates and margin profiles." + - field: "Potential acquirers" + sector_label: "EdTech Acquirer Landscape" + sector_guidance: "Categorize: (1) Publisher acquirers — Pearson, McGraw-Hill, HMH seeking technology capability. (2) Platform acquirers — Instructure, PowerSchool, Google Education seeking content or functionality. (3) Assessment company acquirers — ACT, ETS, NWEA seeking adaptive or content capability. (4) Large EdTech acquirers — Coursera, Chegg, Byju's seeking complementary products. (5) PE acquirers — Vista Equity, Thoma Bravo acquiring profitable EdTech businesses." + sections_to_add: + - section_name: "EdTech Valuation Benchmarks" + placement: "after:EdTech Valuation Multiples" + description: "Current market multiples for EdTech companies." + fields: + - "Public EdTech median revenue multiple (current)" + - "Growth-adjusted multiples by sub-segment" + - "Recent comparable EdTech M&A transactions with multiples" + - "Premium/discount versus general SaaS multiples" + sections_to_remove: [] + benchmark_references: ["gross-margin", "institutional-churn-rate", "learner-engagement-rate"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech board reviews should be structured around the academic calendar (not fiscal quarters) and include multi-stakeholder metrics, efficacy updates, and compliance status alongside financial performance." + field_changes: + - field: "Financial summary" + sector_label: "EdTech Financial Dashboard" + sector_guidance: "Present: Revenue by segment (institutional vs. consumer), Institutional ARR waterfall (opening + new + expansion - churn = closing), Consumer MRR trend, Gross margin by segment, Burn rate and runway. Compare to plan and to same period prior academic year (not prior quarter — EdTech is seasonal)." + - field: "Strategic priorities" + sector_label: "Academic-Year OKR Progress" + sector_guidance: "Report against academic-year OKRs (not calendar-year). Flag off-track OKRs with root cause and corrective action. Present next semester's strategic priorities with measurable targets." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: Product risks (engagement decline, efficacy stagnation, AI displacement), GTM risks (procurement cycle misalignment, pipeline coverage, competitive losses), Compliance risks (FERPA, COPPA, accessibility), Financial risks (funding-source dependency, seasonal cash flow), and Policy risks (federal/state education funding changes, curriculum mandate shifts)." + sections_to_add: + - section_name: "Multi-Stakeholder Metrics" + placement: "before:EdTech Financial Dashboard" + description: "One-page stakeholder health dashboard." + fields: + - "Buyer metrics: institutional retention rate, ACV trend, time to sale" + - "Implementer metrics: teacher adoption rate, teacher NPS, PD completion rate" + - "User metrics: learner engagement rate, completion rate, learning outcomes improvement" + - "NPS by segment (learner / teacher / admin)" + - section_name: "Efficacy Update" + placement: "after:EdTech Financial Dashboard" + description: "Learning outcomes evidence update for the board." + fields: + - "Current efficacy evidence tier" + - "Ongoing and planned efficacy studies" + - "Key outcome metrics (effect sizes, assessment gains)" + - "Efficacy-driven business impact (deals won citing evidence)" + - section_name: "Compliance Status" + placement: "after:Efficacy Update" + description: "Regulatory and compliance status report." + fields: + - "FERPA/COPPA compliance status" + - "Accessibility compliance status and audit results" + - "State DPA participation status" + - "Any compliance incidents or risks" + sections_to_remove: [] + benchmark_references: ["institutional-churn-rate", "teacher-adoption-rate", "learner-engagement-rate", "nps-segmented", "efficacy-evidence-strength", "gross-margin"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech board meeting agendas should allocate time to efficacy evidence, multi-stakeholder metrics, compliance, and the academic-calendar-driven planning that shapes EdTech strategy." + field_changes: + - field: "Agenda items" + sector_label: "EdTech Board Agenda" + sector_guidance: "Standard EdTech board agenda: (1) Multi-stakeholder metrics review — 15 min (pre-read, discussion only; covers buyer, teacher, and learner metrics). (2) Efficacy and compliance update — 10 min (evidence progress, compliance status). (3) Strategic topic deep-dive — 30 min (one topic: AI strategy, segment expansion, teacher adoption, pricing, competitive). (4) Financial and runway — 10 min. (5) CEO asks — 10 min. (6) Executive session — 15 min. Total: 90 minutes. Align meeting cadence with academic year — September (start of year), January (mid-year), May (planning for next year), August (pre-launch review)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech risk categories include sector-specific risks: regulatory compliance (FERPA, COPPA, state privacy laws), accessibility litigation, policy changes affecting funding, academic calendar revenue concentration, free content substitution, and AI disruption." + field_changes: + - field: "Risk categories" + sector_label: "EdTech Risk Categories" + sector_guidance: "Include EdTech-specific categories: (1) Compliance risk — FERPA/COPPA violation, accessibility lawsuit, state privacy law non-compliance. (2) Funding risk — dependency on time-limited government funding, policy changes affecting education budgets. (3) Adoption risk — teacher adoption failure, engagement collapse, efficacy evidence shortfall. (4) Competitive risk — free alternative improvement, AI commoditization, publisher expansion. (5) Seasonal risk — revenue concentration, cash flow gaps between procurement cycles." + sections_to_add: + - section_name: "Compliance Risk Detail" + placement: "end" + description: "Detailed assessment of education-specific regulatory risks." + fields: + - "FERPA/COPPA compliance exposure and mitigation status" + - "Accessibility compliance exposure (ADA/Section 508 litigation risk)" + - "State privacy law compliance (number of states with coverage)" + - "Data breach preparedness and notification procedures" + - section_name: "Policy and Funding Risk" + placement: "after:Compliance Risk Detail" + description: "Assessment of policy-driven revenue risk." + fields: + - "Revenue percentage dependent on specific government funding programs" + - "Policy changes under consideration that could affect the market" + - "Scenario analysis for funding reduction or redirection" + sections_to_remove: [] + benchmark_references: ["ferpa-coppa-compliance-status", "accessibility-compliance-score", "institutional-churn-rate"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech change initiatives must account for the academic calendar — changes that affect the product experience should be implemented at semester boundaries, and changes that affect institutional relationships should align with budget cycles." + field_changes: + - field: "Implementation timeline" + sector_label: "Academic-Calendar-Aligned Implementation" + sector_guidance: "Align implementation phases with the academic calendar. Product changes: ship during summer (July-August) or winter break (December-January). Pricing changes: implement before the spring budget approval season (March-May). Sales process changes: implement before the primary selling season. Never deploy major UX changes mid-semester." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech compensation benchmarking must account for the sector's unique talent market: lower than big-tech but higher than traditional education, with mission alignment as a partial compensation substitute." + field_changes: + - field: "Compensation benchmarks" + sector_label: "EdTech Compensation Benchmarks" + sector_guidance: "Use EdTech-specific comp data: Pave, Carta (equity), and EdSurge/ISTE salary surveys (education roles). EdTech compensation typically runs 10-25% below equivalent SaaS roles — set expectations accordingly during hiring. Benchmark separately for technology roles (compete with SaaS), education roles (compete with schools and publishers), and hybrid roles (scarce, command premium)." + sections_to_add: + - section_name: "Education Role Compensation" + placement: "end" + description: "Compensation analysis for education-specific roles unique to EdTech." + fields: + - "Instructional designer compensation benchmarks" + - "Former teacher / educator compensation (transition-to-tech premium)" + - "Education research / efficacy team compensation" + - "Mission alignment value (survey data on compensation trade-off for mission)" + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "EdTech regulatory compliance is dominated by student data privacy (FERPA, COPPA), accessibility (ADA/Section 508), and state-level education data privacy laws — a distinct regulatory landscape from general technology." + field_changes: + - field: "Regulatory landscape" + sector_label: "Education Compliance Landscape" + sector_guidance: "Cover: federal student data privacy (FERPA, COPPA), state student data privacy laws (currently 50 states have laws; many exceed federal requirements), accessibility requirements (ADA, Section 508, WCAG 2.1 AA), state data privacy agreements (SDPC National DPA), AI in education regulation (emerging state-level guidelines), and content standards compliance (state curriculum alignment requirements)." + sections_to_add: + - section_name: "Student Data Privacy Compliance" + placement: "end" + description: "Detailed student data privacy compliance status." + fields: + - "FERPA compliance status and recent audit results" + - "COPPA compliance status (for products serving children under 13)" + - "State DPA participation (number of states with signed agreements)" + - "Student Privacy Pledge signatory status" + - "Data breach history and notification procedures" + - section_name: "Accessibility Compliance" + placement: "after:Student Data Privacy Compliance" + description: "Product accessibility compliance status." + fields: + - "VPAT / Accessibility Conformance Report status" + - "Most recent accessibility audit results" + - "Remediation plan for identified accessibility gaps" + - "Accessibility-related support requests and resolution" + sections_to_remove: [] + benchmark_references: ["ferpa-coppa-compliance-status", "accessibility-compliance-score"] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "CEO succession planning follows standard corporate governance practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech action plans should specify which stakeholder each action targets (buyer, implementer, or user) and align milestones with the academic calendar." + field_changes: + - field: "Success metrics" + sector_label: "EdTech KPI Targets (by Stakeholder)" + sector_guidance: "For each action item, specify: which stakeholder it serves, the EdTech metric it impacts (institutional retention, teacher adoption, learner engagement, completion rate, efficacy evidence, compliance), and the academic-calendar milestone for measurement." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate"] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech initiative briefs must include multi-stakeholder impact analysis and align launch timing with the academic calendar." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected Multi-Stakeholder Impact" + sector_guidance: "Quantify impact on each stakeholder: buyer impact (revenue, retention), implementer impact (teacher adoption, time savings), user impact (engagement, outcomes). Include the academic-calendar-aligned time to measurable impact." + - field: "Resource requirements" + sector_label: "Resource Requirements and Calendar Constraints" + sector_guidance: "Include academic calendar constraints: when must this be ready (back-to-school, spring semester, next adoption cycle)? What is the opportunity cost in the content and education team's time?" + sections_to_add: + - section_name: "Efficacy Impact" + placement: "after:Expected Multi-Stakeholder Impact" + description: "Assessment of how the initiative affects learning outcomes evidence." + fields: + - "Expected impact on learning outcomes" + - "Measurement approach (pre/post, controlled study, observational)" + - "Evidence contribution (does this initiative produce publishable efficacy data?)" + sections_to_remove: [] + benchmark_references: ["learner-engagement-rate", "learning-outcomes-improvement", "teacher-adoption-rate"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech project kickoffs must define success across all three stakeholders and align delivery with academic calendar milestones." + field_changes: + - field: "Success criteria" + sector_label: "Multi-Stakeholder Success Metrics" + sector_guidance: "Define 2-3 metrics per stakeholder group that this project will impact. Buyer metrics: retention, ACV, compliance. Implementer metrics: teacher adoption, NPS, PD completion. User metrics: engagement, completion, outcomes. Include academic-calendar-aligned measurement dates." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate", "content-completion-rate"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech hiring scorecards must assess whether candidates have both education domain knowledge and technology competency — the hybrid skills essential for EdTech success." + field_changes: + - field: "Required competencies" + sector_label: "EdTech-Specific Competencies" + sector_guidance: "For education roles: classroom/institutional experience, instructional design methodology, learning science knowledge, standards alignment expertise. For technology roles: experience building products for institutional buyers, understanding of education workflows, empathy for teacher and student users. For hybrid roles: ability to translate between education and technology teams, experience in EdTech or adjacent sectors. For sales roles: institutional procurement experience, education conference network, understanding of funding sources." + sections_to_add: + - section_name: "Education-Technology Bridge Assessment" + placement: "end" + description: "Assessment of the candidate's ability to work across the education-technology divide." + fields: + - "Education domain knowledge (depth and relevance)" + - "Technology fluency (product, engineering, data literacy)" + - "Cross-functional collaboration experience" + - "EdTech sector understanding (regulatory, competitive, stakeholder dynamics)" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech incidents have unique impact dimensions: disruption to learning (students unable to access materials during class), teacher disruption (lesson plans derailed), institutional trust damage (administration questioning the product's reliability), and compliance implications (student data exposure)." + field_changes: + - field: "Impact assessment" + sector_label: "Learning and Institutional Impact" + sector_guidance: "Quantify: number of learners affected, number of institutions affected, duration of learning disruption, instructional time lost, teacher workflow disruption, compliance implications (was student data affected?), institutional communication timeline and effectiveness, and trust impact (did any institutions escalate to administration?)." + sections_to_add: + - section_name: "Compliance and Data Impact" + placement: "after:Learning and Institutional Impact" + description: "EdTech-specific assessment of data and compliance implications." + fields: + - "Was student data affected (FERPA notification requirement assessment)" + - "Was child data affected (COPPA implications)" + - "Institutional notification obligations and completion status" + - "Remediation steps for affected learners" + sections_to_remove: [] + benchmark_references: [] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Sprint and project retrospectives follow standard agile practices that are not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific. The content naturally adapts to EdTech context." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech team health must assess the education-technology integration — the cross-functional collaboration between content/education teams and product/engineering teams, which is the most common source of dysfunction in EdTech organizations." + field_changes: + - field: "Health indicators" + sector_label: "EdTech Team Health Indicators" + sector_guidance: "Include EdTech-specific indicators: education-technology team integration (how well do content and engineering teams collaborate?), academic-calendar readiness (is the team prepared for seasonal intensity spikes?), teacher feedback integration (is teacher input reaching the product team?), and mission alignment (does the team feel the company is fulfilling its educational mission?)." + sections_to_add: + - section_name: "Education-Technology Integration Score" + placement: "end" + description: "Assessment of how well education and technology teams collaborate." + fields: + - "Content-Engineering collaboration quality" + - "Instructional design input on product roadmap" + - "Engineering understanding of pedagogical requirements" + - "Joint planning and retrospective frequency" + sections_to_remove: [] + benchmark_references: [] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech culture documents should articulate how the company balances mission (educational impact) with business performance (growth, revenue, efficiency) — the central cultural tension in EdTech." + field_changes: + - field: "Core values" + sector_label: "Mission-Business Integrated Values" + sector_guidance: "Values should address the mission-business integration explicitly. Example value: 'Learner outcomes first, sustainable business always.' Avoid values that privilege either mission or business exclusively. Include a value about stakeholder empathy — understanding buyers, teachers, and learners." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech offsites should include a learner/teacher experience component — direct exposure to the users the product serves, which grounds strategic discussions in reality." + field_changes: + - field: "Agenda structure" + sector_label: "EdTech Offsite Agenda" + sector_guidance: "Include a 'Classroom Connection' session: visit a partner school or university, observe the product in use, and speak directly with teachers and students. This grounds all subsequent strategic discussion in the reality of how the product is used. Time this session at the beginning of the offsite, not the end." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "EdTech role descriptions should specify whether the role requires education domain expertise, technology expertise, or hybrid skills, and identify the EdTech metrics the role is accountable for." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Stakeholder Accountability" + sector_guidance: "For each responsibility, specify: which stakeholder group the role primarily serves (buyer, implementer, user) and the EdTech metric the role owner is accountable for. Examples: VP Sales owns institutional ARR and ACV; VP Education owns efficacy evidence and teacher adoption rate; VP Product owns learner engagement and completion rate; VP CS owns institutional retention and NPS." + - field: "Required experience" + sector_label: "EdTech Experience Requirements" + sector_guidance: "Specify: education sector knowledge level required (deep, moderate, awareness), technology experience required, EdTech-specific experience (institutional sales, content development, learning science), and whether the role requires bridging education and technology teams." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An EdTech CEO's weekly review should be structured around multi-stakeholder metrics and aligned with the academic calendar rhythm — different focus areas during back-to-school, mid-year, end-of-year, and summer." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly EdTech Dashboard" + sector_guidance: "Review weekly: Active learners and WoW trend, Teacher logins and activation for new institutions, Support ticket volume by stakeholder (teacher vs. admin vs. student), Pipeline changes, Cash balance. Monthly metrics (institutional churn, NPS, efficacy data) should be reviewed monthly. Adjust focus by academic calendar period: Sep-Oct (activation), Nov-Feb (engagement depth), Mar-May (renewal and expansion), Jun-Aug (onboarding preparation)." + - field: "Priorities" + sector_label: "This Week's Priority" + sector_guidance: "Identify the single most important thing for the week. In EdTech, this is often calendar-driven: during back-to-school, it is new customer onboarding; during mid-year, it is efficacy data collection; during spring, it is renewal conversations; during summer, it is product updates and PD preparation." + sections_to_add: + - section_name: "Stakeholder Signal Review" + placement: "after:Weekly EdTech Dashboard" + description: "Weekly review of qualitative signals from all three stakeholder groups." + fields: + - "Buyer signals: renewal conversations, new prospect interactions, budget feedback" + - "Teacher signals: adoption wins, support escalations, PD feedback" + - "Learner signals: engagement trends, completion patterns, qualitative feedback" + sections_to_remove: [] + benchmark_references: ["learner-engagement-rate", "teacher-adoption-rate"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech decision journals should capture the multi-stakeholder trade-offs inherent in every significant decision and the academic-calendar constraints that shape timing." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Multi-Stakeholder and Calendar)" + sector_guidance: "Record: which stakeholders this decision affects, the trade-offs between stakeholder needs, the academic calendar constraints on timing, and the specific metric outcome that will confirm the decision was correct. For reversible decisions, note the measurement timeline aligned with academic milestones." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech annual reviews should be conducted on the academic-year cycle (August-September) and assess performance across all three stakeholder dimensions plus efficacy evidence advancement." + field_changes: + - field: "Year in review" + sector_label: "Academic Year in Review" + sector_guidance: "Assess: Revenue growth (institutional + consumer), Institutional metrics (new customers, retention, expansion, ACV), Adoption metrics (teacher adoption rate, learner engagement), Efficacy progress (evidence tier advancement, studies completed), Compliance milestones (certifications achieved, DPAs signed), and Team development (education-technology integration, key hires)." + - field: "Next year goals" + sector_label: "Next Academic Year EdTech Targets" + sector_guidance: "Set targets across all EdTech dimensions: Revenue targets (by segment), Institutional targets (new customers, retention, expansion), Adoption targets (teacher activation, learner engagement, completion), Efficacy targets (evidence tier to achieve, studies to commission), Compliance targets (certifications, DPAs), Product targets (major releases aligned with academic calendar). Each target should reference the academic-calendar milestone for measurement." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["institutional-churn-rate", "teacher-adoption-rate", "learner-engagement-rate", "efficacy-evidence-strength", "gross-margin"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech stakeholder maps must include education-ecosystem-specific stakeholder categories: institutional decision-makers, teacher influencers, policy makers, research partners, and the unique EdTech investor community." + field_changes: + - field: "Stakeholder categories" + sector_label: "EdTech Stakeholder Ecosystem" + sector_guidance: "Include: Institutional buyers (superintendents, provosts, CLOs), Implementers (teacher champions, instructional coaches, PD directors), Investors (EdTech-specialized funds, impact investors, generalist VCs), Partners (publishers, LMS platforms, assessment organizations, research universities), Policy (state education officials, federal program officers, school board members), Community (teacher influencers, education bloggers, conference organizers), and Team (executives, education experts, technology leaders)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech negotiation prep should include education-specific negotiation contexts and the unique constraints of institutional procurement." + field_changes: + - field: "Negotiation type" + sector_label: "EdTech Negotiation Context" + sector_guidance: "Classify: institutional deal (district/university contract terms), publisher partnership (content licensing, revenue share, IP), platform integration (LMS terms, data sharing), fundraising (term sheet with EdTech investors), or research collaboration (university partnership for efficacy study). Each type has distinct EdTech-specific dynamics." + - field: "BATNA" + sector_label: "BATNA and EdTech Leverage" + sector_guidance: "EdTech-specific leverage: for institutional sales — efficacy evidence, teacher demand (bottom-up pull), state adoption list inclusion, compliance readiness. For partnerships — unique content, proprietary data, institutional relationships. For fundraising — impact metrics alongside financial metrics, mission-aligned investor interest." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["average-contract-value", "efficacy-evidence-strength"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech founder mental health is affected by sector-specific stressors: the emotional weight of serving children and students, the frustration of slow institutional change, the guilt of commercial decisions that may compromise educational mission, and the seasonal intensity cycle." + field_changes: + - field: "Stress indicators" + sector_label: "EdTech-Specific Stress Indicators" + sector_guidance: "Include: mission guilt (feeling that commercial decisions betray the educational mission), seasonal burnout (back-to-school intensity creating annual burnout cycles), institutional frustration (the slow pace of education system change wearing down motivation), impact anxiety (questioning whether the product is actually helping learners), and comparison stress (measuring against philanthropically funded competitors like Khan Academy who do not need to be profitable)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific. The reflections naturally address EdTech-specific challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "EdTech founders should include education-specific learning areas in their development plans to bridge the education-technology knowledge gap." + field_changes: + - field: "Learning areas" + sector_label: "EdTech Learning Priorities" + sector_guidance: "Consider EdTech-specific learning areas: learning science fundamentals (how people learn — cognitive load theory, spaced repetition, retrieval practice), education policy and funding mechanisms, institutional procurement processes, accessibility and inclusive design, efficacy research methodology, AI in education (tutoring, assessment, content generation), and the education reform landscape." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "An EdTech founder's personal board of advisors should include education-specific expertise areas." + field_changes: + - field: "Advisor categories" + sector_label: "EdTech Advisory Needs" + sector_guidance: "Map advisors to EdTech-specific needs: EdTech operations (someone who has scaled an EdTech company through the institutional sales gauntlet), Education domain (former superintendent, university provost, or chief learning officer who understands the buyer), Product (EdTech product leader who has navigated multi-stakeholder design), Research (learning scientist or education researcher for efficacy guidance), Policy (someone connected to education policy at state or federal level), Finance (EdTech-savvy investor who understands sector-specific valuation), and Technology (AI/ML leader for adaptive learning and content generation strategy)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech QBRs (Quarterly Business Reviews, often Semester Reviews in education) are the primary institutional retention and expansion vehicle. The review must address all three stakeholders with data tailored to each: administrators care about ROI and compliance, teachers care about usage and classroom impact, and efficacy data connects both." + field_changes: + - field: "Performance summary" + sector_label: "Learning Impact Delivered" + sector_guidance: "Quantify the educational value delivered this period: learning outcomes improvement (assessment gains, skill proficiency advancement), content completion rates, learner engagement statistics, and comparison to institutional goals. Use the institution's own metrics and language — test scores, standards mastery levels, graduation rates — not product metrics." + - field: "Account status" + sector_label: "Adoption and Usage Metrics" + sector_guidance: "Present: teacher activation rate, active learners vs. licensed learners, feature adoption by module, usage patterns by grade/department/team, and comparison to peer institutions in similar demographics." + - field: "Next steps" + sector_label: "Expansion and Deepening Opportunities" + sector_guidance: "Identify expansion: additional grade levels, subjects, departments, or campuses. Deepening: additional modules, premium features, or deeper integration. Frame as educational outcomes, not product upsells: 'Based on success in 3rd grade math, 4th grade teachers have expressed interest in the same approach.'" + sections_to_add: + - section_name: "Efficacy Report" + placement: "before:Learning Impact Delivered" + description: "Learning outcomes evidence specific to this institution." + fields: + - "Pre/post assessment results (if available)" + - "Learning outcomes improvement vs. institution's goals" + - "Comparison to efficacy benchmarks from research" + - "Teacher-reported impact on instruction" + - section_name: "Teacher Adoption Report" + placement: "after:Adoption and Usage Metrics" + description: "Detailed teacher adoption and satisfaction data." + fields: + - "Teacher activation rate and trend" + - "Teacher NPS" + - "Professional development completion" + - "Teacher support requests and resolution" + sections_to_remove: [] + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate", "content-completion-rate", "learning-outcomes-improvement", "nps-segmented"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech onboarding must address all three stakeholders separately: administrators need compliance documentation and reporting setup, teachers need PD and classroom integration guidance, and students need age-appropriate product orientation. Time to value is measured in academic terms: the product must be functional before the first class session." + field_changes: + - field: "Getting started steps" + sector_label: "Multi-Stakeholder Onboarding Path" + sector_guidance: "Structure onboarding in three parallel tracks: Administrator track: compliance documentation, data integration (SIS, LMS), reporting dashboard setup, success criteria definition — complete before school start. Teacher track: PD session, classroom setup wizard, first lesson plan creation, peer teacher community access — complete within first two weeks of school. Student track: age-appropriate account setup, first learning activity, accessibility accommodations configuration — complete within first class session." + - field: "Resources" + sector_label: "Stakeholder-Specific Resources" + sector_guidance: "Segment resources by stakeholder: Administrators — compliance documentation, data integration guides, ROI measurement framework. Teachers — PD videos, lesson plan library, teacher community forum, classroom management guide. Students — age-appropriate tutorials, help resources, accessibility options." + sections_to_add: + - section_name: "Academic Calendar Milestones" + placement: "end" + description: "Implementation milestones tied to the academic calendar." + fields: + - "Pre-school-year: admin setup, data integration, teacher PD scheduling" + - "Week 1-2: teacher activation, first student sessions" + - "Month 1: baseline assessment data collection" + - "Semester midpoint: first usage review, teacher feedback collection" + - "Semester end: outcome data collection, renewal conversation" + sections_to_remove: [] + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech proposals must address institutional procurement requirements: alignment with standards, compliance documentation, efficacy evidence, implementation support, and pricing structured around institutional budget categories." + field_changes: + - field: "Pricing" + sector_label: "Investment, Funding Alignment, and ROI" + sector_guidance: "Present: pricing options (per-student, per-school, district-wide), alignment with common funding sources (Title I, Title IV-A, state grants — specify which line items the product fits under), implementation costs, PD costs, and a clear ROI model using education-specific metrics (cost per student outcome improvement, instructional time saved per teacher)." + - field: "Scope" + sector_label: "Implementation Scope and Academic Calendar Alignment" + sector_guidance: "Define implementation phases aligned with the academic calendar: pre-year setup, teacher PD, student onboarding, mid-year check-in, year-end assessment. Specify the institution's time commitment by role (admin hours, teacher hours, IT hours). Set expectations for time to measurable outcomes (typically one full semester minimum)." + sections_to_add: + - section_name: "Efficacy Evidence" + placement: "before:Investment, Funding Alignment, and ROI" + description: "Learning outcomes evidence to support the purchasing decision." + fields: + - "Published efficacy research (studies, effect sizes, populations)" + - "Similar institution case studies with quantified outcomes" + - "Standards alignment documentation" + - "Proposed pilot with built-in measurement" + - section_name: "Compliance Documentation" + placement: "after:Implementation Scope and Academic Calendar Alignment" + description: "Compliance documentation that institutional buyers require." + fields: + - "FERPA compliance attestation" + - "COPPA compliance (if applicable)" + - "Data Privacy Agreement (aligned with SDPC template)" + - "Accessibility documentation (VPAT)" + - "Security documentation (SOC 2, penetration test results)" + sections_to_remove: [] + benchmark_references: ["average-contract-value", "efficacy-evidence-strength", "ferpa-coppa-compliance-status"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech SLAs must address education-specific requirements: platform availability during school hours (not 24/7 — school hours are more critical than overnight), data handling for student records, and support response times aligned with the instructional day." + field_changes: + - field: "Service levels" + sector_label: "Education Service Commitments" + sector_guidance: "EdTech-specific SLA components: (1) Uptime during school hours (99.9% Monday-Friday 7AM-5PM local time — more critical than overall uptime). (2) Assessment window protection (99.99% during state testing periods). (3) Support response times (P0 during school hours: 30 minutes; P1: 2 hours; P2: 1 business day). (4) Student data handling commitments (FERPA-compliant storage, retention, deletion). (5) Content accuracy commitment (curriculum-aligned, standards-current). (6) Accessibility maintenance (WCAG 2.1 AA ongoing compliance)." + - field: "Remediation" + sector_label: "Credit and Remediation Terms" + sector_guidance: "Define: service credit structure for school-hours outages (higher credits for instructional time disruption), termination rights for sustained availability failures during assessment windows, and data portability upon contract termination (student data must be exportable and deletable per FERPA)." + sections_to_add: + - section_name: "Student Data Terms" + placement: "end" + description: "Student data handling commitments standard in EdTech contracts." + fields: + - "Data ownership (institution retains ownership of all student data)" + - "Data use restrictions (FERPA-compliant, no advertising, no secondary use)" + - "Data retention and deletion schedule" + - "Data portability upon contract termination" + - "Sub-processor disclosure and compliance" + - "Breach notification procedure and timeline" + sections_to_remove: [] + benchmark_references: ["ferpa-coppa-compliance-status"] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech implementation status updates should track progress toward the academic milestones that determine success — teacher activation before school starts, student engagement in the first weeks, and baseline assessment data collection." + field_changes: + - field: "Progress summary" + sector_label: "Implementation Progress (Academic Calendar)" + sector_guidance: "Track against academic-calendar-aligned milestones: Are teachers activated before classes start? Is student onboarding complete within the first week? Is baseline data being collected? Report teacher activation rate, student activation rate, and any blockers — especially institutional blockers (IT delays, schedule conflicts, PD session cancellations)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["teacher-adoption-rate", "learner-engagement-rate"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech analysis reports for institutional clients should present findings through the lens of educational outcomes and include multi-stakeholder data." + field_changes: + - field: "Findings" + sector_label: "Findings (by Stakeholder)" + sector_guidance: "Structure findings by stakeholder: What the data shows for institutional decision-makers (ROI, compliance, usage benchmarks), for teachers (classroom impact, time savings, PD effectiveness), and for learners (engagement, outcomes, experience). Include comparison to peer institutions and to efficacy research benchmarks." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["learning-outcomes-improvement", "learner-engagement-rate", "teacher-adoption-rate"] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech case studies must present quantified learning outcomes (not just business outcomes) and address all three stakeholders to be useful as sales tools for institutional procurement." + field_changes: + - field: "Results" + sector_label: "Quantified Learning and Business Outcomes" + sector_guidance: "Every EdTech case study must include: (1) Learning outcomes — assessment gains, skill proficiency improvement, completion rates (with sample sizes and methodology). (2) Teacher impact — time saved, satisfaction scores, adoption rates. (3) Institutional impact — cost per student outcome, ROI calculation, comparison to prior approach. Abstract outcomes are insufficient — buyers need numbers to build internal business cases." + - field: "Challenge" + sector_label: "Educational Challenge and Institutional Context" + sector_guidance: "Include: the educational challenge (achievement gap, disengagement, skills gap), what the institution was doing before, what triggered the evaluation, the procurement process and decision factors, and the institution's demographic context (so prospects can determine if they are similar)." + sections_to_add: + - section_name: "Implementation Details" + placement: "after:Quantified Learning and Business Outcomes" + description: "Practical details about how the product was deployed." + fields: + - "Implementation timeline (from purchase to full deployment)" + - "Teacher PD and onboarding approach" + - "Student population served (demographics, grade levels, subjects)" + - "Integration with existing technology stack (LMS, SIS)" + - "Time to first measurable outcomes" + - section_name: "Multi-Stakeholder Testimonials" + placement: "after:Implementation Details" + description: "Testimonials from each stakeholder group." + fields: + - "Administrator quote (focus on ROI, evidence, decision validation)" + - "Teacher quote (focus on classroom impact, ease, time savings)" + - "Student quote or outcome story (focus on engagement, learning, experience)" + sections_to_remove: [] + benchmark_references: ["learning-outcomes-improvement", "teacher-adoption-rate", "content-completion-rate"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "EdTech partnership memos must address the unique partner landscape: LMS integrations, publisher content partnerships, research collaborations, and the interoperability standards (LTI, xAPI, Ed-Fi) that govern technical partnerships in education." + field_changes: + - field: "Partnership structure" + sector_label: "EdTech Partnership Structure" + sector_guidance: "Define: partnership type (technology integration, content co-development, distribution/channel, research collaboration), technical integration approach (LTI, xAPI, Ed-Fi, API), content IP ownership, data sharing terms (FERPA implications for any student data exchange), go-to-market collaboration (co-selling, co-marketing at education conferences), and success metrics." + sections_to_add: + - section_name: "Interoperability and Data Terms" + placement: "end" + description: "Technical and data terms specific to EdTech partnerships." + fields: + - "Integration standards used (LTI, xAPI, Ed-Fi, CASE)" + - "Student data sharing terms (FERPA compliance for shared data)" + - "Content IP ownership and licensing terms" + - "Platform dependency risk assessment" + sections_to_remove: [] + benchmark_references: ["institutional-adoption-rate"] diff --git a/plugins/foreman/content/industry-packs/fintech/fintech-benchmarks.yaml b/plugins/foreman/content/industry-packs/fintech/fintech-benchmarks.yaml new file mode 100644 index 0000000..d8a04c1 --- /dev/null +++ b/plugins/foreman/content/industry-packs/fintech/fintech-benchmarks.yaml @@ -0,0 +1,1475 @@ +# Fintech Industry Pack — Benchmarks +# +# 24 fintech-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing growth, compliance, +# and unit economics issues in payments, lending, neobanking, insurtech, +# wealthtech, crypto/blockchain, embedded finance, and regtech companies. +# +# Primary data sources: +# - a16z Fintech Reports (2023, 2024) +# - CB Insights State of Fintech (2023, 2024) +# - McKinsey Global Payments Report (2023, 2024) +# - Stripe S-1 / Financial Reports (2023, 2024) +# - Nubank S-1 Filing / Annual Reports (2021, 2023) +# - SoFi S-1 Filing / Annual Reports (2021, 2023) +# - Plaid Developer Reports (2023, 2024) +# - FDIC Quarterly Banking Profile (2023, 2024) +# - Basel Committee on Banking Supervision (2023) +# - Nilson Report — Card Fraud Worldwide (2023, 2024) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded fintech companies at the relevant stage. +# +# REGULATORY NOTE: Many fintech metrics are subject to regulatory reporting +# requirements. Definitions must align with applicable regulatory standards +# (BSA/AML, PSD2, Basel III) to ensure consistency between internal tracking +# and compliance reporting. + +pack_metadata: + sector: "fintech" + display_name: "Fintech" + version: "1.0.0" + description: "Benchmark data for fintech companies spanning payments, lending, + neobanking, insurtech, wealthtech, crypto, embedded finance, and regtech — + with regulatory compliance as a first-class dimension." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # PAYMENTS & VOLUME METRICS + # ───────────────────────────────────────────── + + - name: "Total Payment Volume (TPV)" + id: "tpv" + category: "growth" + definition: "The aggregate dollar value of all transactions processed through + the platform in a given period. TPV is the top-line measure of scale for + payments businesses — it represents the economic activity intermediated, + not the revenue retained." + formula: "SUM(transaction_value) over period" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $1M monthly TPV at 12 months post-launch" + signal: "Insufficient transaction velocity to sustain the business. Processing + costs eat margins at low volume." + below_average: + value: "$1M-$10M monthly TPV at 12 months" + signal: "Early traction but not yet at the scale where unit economics improve. + Interchange and processing cost negotiations remain unfavorable." + average: + value: "$10M-$100M monthly TPV at 12 months" + signal: "Meaningful scale. Enough volume to negotiate improved interchange rates + and demonstrate product-market fit to investors." + good: + value: "$100M-$1B monthly TPV at 12 months" + signal: "Strong volume. Unit economics improve materially at this scale through + volume-based pricing tiers with card networks and processors." + excellent: + value: "> $1B monthly TPV at 12 months" + signal: "Exceptional scale. Rare at this stage — indicates viral adoption in a + high-volume vertical or a major enterprise client onboarded." + stage_notes: + seed: "TPV trajectory matters more than absolute level. Investors look for + consistent week-over-week growth in transaction volume, not static + snapshots." + series_a: "Series A payments companies typically process $50M-$500M annual TPV. + The conversion from TPV to net revenue (take rate) is scrutinized + heavily." + series_b_plus: "At Series B+, TPV growth rate must exceed 50% YoY. Investors + shift focus from TPV to net revenue growth and margin expansion." + data_sources: + - source: "McKinsey Global Payments Report" + url: "https://www.mckinsey.com/industries/financial-services/our-insights/the-2\ + 023-mckinsey-global-payments-report" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "take-rate", "transaction-volume", "revenue-per-transaction" ] + related_skills: [ "balanced-scorecard", "business-model-canvas" ] + caveats: "TPV can be inflated by pass-through transactions that generate minimal + revenue. Always pair TPV with take rate to understand actual economics. + High-TPV businesses with sub-10bps take rates face margin compression + risk." + + - name: "Take Rate / Interchange Revenue" + id: "take-rate" + category: "unit-economics" + definition: "The percentage of total payment volume retained as net revenue + after interchange, assessments, and processor costs. This is the fintech + equivalent of gross margin on transactions — it measures the platform's + pricing power and value-add per dollar processed." + formula: "Net Revenue / TPV x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0.1% (10 bps)" + signal: "Commodity processing with no value-add. The business is a payment + pass-through — vulnerable to disintermediation by Stripe, Adyen, or + direct bank connections." + below_average: + value: "0.1-0.3% (10-30 bps)" + signal: "Low-margin payment facilitation. Sustainable only at extreme volume. + Durbin Amendment caps debit interchange at ~22 cents + 5bps for large + issuers." + average: + value: "0.3-1.0% (30-100 bps)" + signal: "Standard payment facilitation with some value-add services (fraud + prevention, underwriting, analytics). Stripe retains approximately + 50-70bps after interchange." + good: + value: "1.0-2.5% (100-250 bps)" + signal: "Significant value-add justifying premium pricing. Includes embedded + services (lending, insurance, identity) bundled with payments." + excellent: + value: "> 2.5% (250+ bps)" + signal: "Platform economics with deep vertical integration. Possible through + managed services, lending-on-volume, or regulated services where + compliance creates pricing power." + stage_notes: + seed: "Take rate is a hypothesis at seed. Regulatory constraints (interchange + caps under Durbin Amendment in US, IFR in EU) set hard ceilings on + certain revenue lines." + series_a: "Take rate compression is the primary risk. Demonstrate the path to + increasing take rate through value-add services, not just volume + growth." + series_b_plus: "At scale, even 5bps of take rate improvement is material. + Investors model take rate trajectory alongside TPV growth." + data_sources: + - source: "Stripe Financial Reports" + year: "2024" + - source: "McKinsey Global Payments Report" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "tpv", "revenue-per-transaction", "gross-margin" ] + related_skills: + - porters-five-forces + caveats: "Take rate varies dramatically by vertical and payment method. + Card-present transactions yield different interchange than + card-not-present. Cross-border transactions carry higher interchange but + also higher fraud risk. Regulatory caps (PSD2 IFR in Europe, Durbin in US) + constrain take rates on regulated interchange." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Transaction Volume" + id: "transaction-volume" + category: "growth" + definition: "The total number of discrete transactions processed in a given + period, independent of dollar value. Transaction volume measures platform + utilization and is the primary driver of variable costs (processing fees + per transaction)." + formula: "COUNT(transactions) over period" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10K monthly transactions at 12 months" + signal: "Insufficient scale for meaningful unit economics. Fixed infrastructure + costs dominate variable transaction costs." + below_average: + value: "10K-100K monthly transactions" + signal: "Early traction. Enough transactions to detect fraud patterns and + optimize processing routes." + average: + value: "100K-1M monthly transactions" + signal: "Operational scale. Justifies investment in proprietary fraud detection, + transaction monitoring, and compliance automation." + good: + value: "1M-10M monthly transactions" + signal: "Strong scale. Volume-based pricing from networks and processors + materially improves unit economics." + excellent: + value: "> 10M monthly transactions" + signal: "Massive scale. Enables sophisticated data-driven products (credit + scoring, personalization, predictive analytics) built on transaction + data." + stage_notes: + seed: "Transaction count matters for demonstrating usage patterns. Quality of + transactions (repeat users, consistent amounts) signals more than volume + alone." + series_a: "Transaction growth rate and transactions per user are more meaningful + than raw count. BSA/AML transaction monitoring requirements scale with + volume." + series_b_plus: "At scale, transaction cost per unit should decline through + volume discounts and processing optimization. Regulatory reporting + obligations (CTR, SAR) increase with volume." + data_sources: + - source: "Stripe Financial Reports" + year: "2024" + - source: "Plaid Developer Reports" + year: "2024" + related_metrics: + [ + "tpv", + "revenue-per-transaction", + "cost-per-transaction", + "transactions-per-user" + ] + related_skills: [ "balanced-scorecard", "systems-thinking" ] + caveats: "Transaction volume without revenue context is a vanity metric. A + million transactions at zero margin is worse than 100K transactions at + healthy margin. Always pair with revenue per transaction and cost per + transaction." + + - name: "Revenue per Transaction" + id: "revenue-per-transaction" + category: "unit-economics" + definition: "The average net revenue captured per individual transaction after + interchange, assessments, and direct processing costs. This metric + measures the economic value of each transaction to the platform." + formula: "Net Revenue / Transaction Count" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $0.05 per transaction" + signal: "Micro-transaction economics that require extreme volume to sustain the + business. Common in peer-to-peer payments and low-value card + transactions." + below_average: + value: "$0.05-$0.25 per transaction" + signal: "Low per-unit economics. Business viability depends on high frequency + and volume. Cross-sell opportunities needed to increase lifetime + value." + average: + value: "$0.25-$1.00 per transaction" + signal: "Sustainable per-transaction economics for payment facilitators. Enough + margin per transaction to fund fraud prevention and customer support." + good: + value: "$1.00-$5.00 per transaction" + signal: "Strong unit economics per transaction. Indicates value-add services or + higher-value transaction types (B2B payments, cross-border, lending)." + excellent: + value: "> $5.00 per transaction" + signal: "Premium transaction economics. Typical of embedded lending, + cross-border B2B payments, or regulated financial services where + compliance creates pricing power." + stage_notes: + seed: "Revenue per transaction is a function of average transaction size and + take rate. Model both variables independently." + series_a: "Demonstrate revenue per transaction stability or improvement over + time. Declining revenue per transaction signals take rate compression or + mix shift." + series_b_plus: "Revenue per transaction should increase as value-add services + (fraud tools, analytics, lending) are layered on top of core payment + processing." + data_sources: + - source: "Stripe Financial Reports" + year: "2024" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "take-rate", "cost-per-transaction", "transaction-volume" ] + related_skills: + - four-ps-marketing + caveats: "Average revenue per transaction can be misleading when the transaction + mix is bimodal — a platform processing both $5 consumer payments and $50K + B2B invoices will show a meaningless average." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Cost per Transaction" + id: "cost-per-transaction" + category: "unit-economics" + definition: "The total variable cost incurred to process a single transaction, + including interchange fees, processor costs, fraud prevention, compliance + screening (KYC/AML), and customer support allocation." + formula: "(Interchange + Assessment Fees + Processor Fees + Fraud Costs + + Compliance Costs + Support Allocation) / Transaction Count" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $1.50 per transaction" + signal: "High per-transaction cost indicating inefficient processing, excessive + manual compliance review, or high fraud losses." + below_average: + value: "$0.75-$1.50 per transaction" + signal: "Above-average costs, often driven by manual compliance processes or + premium fraud prevention services." + average: + value: "$0.25-$0.75 per transaction" + signal: "Standard processing costs for card-based payment facilitation. + Interchange is the dominant component." + good: + value: "$0.10-$0.25 per transaction" + signal: "Efficient processing with automated compliance and fraud systems. + Volume-based interchange discounts contributing." + excellent: + value: "< $0.10 per transaction" + signal: "Highly efficient processing — typically ACH-based or direct bank + transfer models that bypass card interchange entirely." + stage_notes: + seed: "Cost per transaction is high at low volume because fixed compliance and + infrastructure costs are spread across few transactions." + series_a: "Demonstrate clear path to cost per transaction reduction through + volume, automation, and processing route optimization." + series_b_plus: "Cost per transaction optimization is a primary margin lever. + Every cent saved per transaction at high volume is material to EBITDA." + data_sources: + - source: "McKinsey Global Payments Report" + year: "2023" + - source: "Nilson Report" + year: "2024" + related_metrics: [ "revenue-per-transaction", "gross-margin", "fraud-loss-rate" ] + related_skills: [ "balanced-scorecard", "systems-thinking" ] + caveats: "Cost per transaction must include compliance costs — many fintechs + exclude KYC/AML screening costs from transaction COGS, understating true + unit costs. Regulators expect full cost transparency." + + # ───────────────────────────────────────────── + # CUSTOMER ACQUISITION & LIFECYCLE + # ───────────────────────────────────────────── + + - name: "Customer Acquisition Cost" + id: "cac" + category: "unit-economics" + definition: "The fully loaded cost to acquire one new active customer, including + marketing, sales, referral incentives, sign-up bonuses, and the cost of + KYC/identity verification during onboarding. In fintech, CAC must include + compliance-driven onboarding costs that do not exist in non-regulated + businesses." + formula: "(Total Sales & Marketing Spend + KYC/Onboarding Costs + Sign-Up + Incentives) / New Active Customers" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $200 (consumer) / > $2,000 (SMB) / > $25,000 (enterprise)" + signal: "Acquisition cost exceeds first-year revenue for many customers. Growth + is uneconomic without significant cross-sell or long customer + lifetimes." + below_average: + value: "$100-$200 (consumer) / $1,000-$2,000 (SMB) / $10,000-$25,000 + (enterprise)" + signal: "High CAC driven by competitive acquisition environment, expensive KYC + processes, or low organic adoption." + average: + value: "$30-$100 (consumer) / $500-$1,000 (SMB) / $5,000-$10,000 (enterprise)" + signal: "Standard acquisition costs for regulated financial services. KYC + typically accounts for $5-$15 of consumer CAC." + good: + value: "$10-$30 (consumer) / $200-$500 (SMB) / $2,000-$5,000 (enterprise)" + signal: "Efficient acquisition through product-led growth, referrals, or + embedded distribution. KYC automation reducing onboarding friction." + excellent: + value: "< $10 (consumer) / < $200 (SMB) / < $2,000 (enterprise)" + signal: "Viral or embedded acquisition. Common in neobanks with referral + programs (Nubank achieved <$5 CAC in Brazil) or embedded finance with + distribution partnerships." + stage_notes: + seed: "CAC is high and unstable at seed. Manual KYC processes inflate early + costs. Focus on learning which channels yield compliant, active + customers." + series_a: "CAC should be declining as KYC automation scales and channel + efficiency improves. Segment CAC by channel and by customer quality + (active vs. dormant)." + series_b_plus: "CAC efficiency is a primary value driver. Nubank's sub-$5 CAC + was central to its IPO narrative. Demonstrate the relationship between + CAC and LTV by cohort." + data_sources: + - source: "Nubank S-1 Filing" + year: "2021" + - source: "a16z Fintech Reports" + year: "2024" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "ltv", "kyc-conversion-rate", "kyc-cost-per-customer" ] + related_skills: [ "four-ps-marketing", "blue-ocean-strategy" ] + caveats: "Fintech CAC must include KYC/identity verification costs — these are + non-optional regulatory requirements that do not exist in unregulated + businesses. Excluding them understates true acquisition cost and misleads + unit economics calculations." + + - name: "Customer Lifetime Value" + id: "ltv" + category: "unit-economics" + definition: "The total net revenue expected from a customer over the entire + duration of their relationship with the platform, adjusted for gross + margin and the cost of regulatory compliance associated with maintaining + the account." + formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross + Margin % x Average Customer Lifetime in months)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "LTV:CAC ratio < 1.5x" + signal: "Customer economics are underwater. The business is destroying value + with each new customer. Common when regulatory compliance costs are + underestimated in the LTV calculation." + below_average: + value: "LTV:CAC ratio 1.5-3x" + signal: "Marginal economics. Insufficient margin of safety against regulatory + cost increases, credit losses, or competitive fee compression." + average: + value: "LTV:CAC ratio 3-5x" + signal: "Healthy unit economics. Standard range for venture-backed fintechs with + established product-market fit." + good: + value: "LTV:CAC ratio 5-8x" + signal: "Strong economics driven by high retention, effective cross-sell, and + efficient acquisition. Nubank reported LTV:CAC above 5x at IPO." + excellent: + value: "LTV:CAC ratio > 8x" + signal: "Exceptional economics. May indicate under-investment in growth — verify + that the company is deploying capital aggressively enough." + stage_notes: + seed: "LTV is largely theoretical at seed. Base it on comparable fintech cohort + data and conservative assumptions about retention and cross-sell." + series_a: "LTV should be derived from at least 12 months of cohort data. + Separate LTV by customer segment — consumer, SMB, and enterprise have + radically different lifetimes." + series_b_plus: "Mature LTV models incorporate multiple revenue streams + (payments, lending, deposits, insurance) and regulatory cost + assumptions. SoFi's cross-sell from lending to banking demonstrated LTV + uplift through product expansion." + data_sources: + - source: "Nubank S-1 Filing" + year: "2021" + - source: "SoFi Annual Reports" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "cac", "net-revenue-retention", "monthly-active-users" ] + related_skills: [ "balanced-scorecard", "net-promoter-score" ] + caveats: "Fintech LTV calculations must account for regulatory compliance costs + that compound over the customer lifetime — ongoing KYC refresh, + transaction monitoring, and SAR filing costs. Omitting these overstates + LTV by 10-20% in lending and payments." + + # ───────────────────────────────────────────── + # CREDIT & RISK METRICS (Lending-Specific) + # ───────────────────────────────────────────── + + - name: "Net Interest Margin" + id: "net-interest-margin" + category: "financial" + definition: "The difference between interest income earned on loans and the + interest paid on deposits or borrowed funds, expressed as a percentage of + average earning assets. NIM is the core profitability metric for lending + and neobanking fintechs — it measures the spread the institution captures + between its cost of funds and its lending yield." + formula: "(Interest Income - Interest Expense) / Average Earning Assets x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "< 2.0%" + signal: "Margin too thin to cover operating costs and credit losses. The + institution is pricing loans too competitively or paying too much for + deposits/funding." + below_average: + value: "2.0-3.0%" + signal: "Narrow margin that leaves little room for credit losses or operating + expenses. Typical of fintechs relying on warehouse lending facilities + with high cost of capital." + average: + value: "3.0-5.0%" + signal: "Standard range for digital lenders. FDIC-insured average NIM was + approximately 3.3% in 2023. Fintech lenders without bank charters + typically operate at higher NIM due to higher-risk lending." + good: + value: "5.0-8.0%" + signal: "Strong NIM indicating either low cost of funds (bank charter, deposit + funding) or higher-yield lending (subprime, small-dollar, BNPL). Must + be evaluated against credit losses." + excellent: + value: "> 8.0%" + signal: "Very high NIM — typically indicative of high-risk lending (personal + loans, payday alternative) where credit losses may consume the margin + advantage. Requires careful risk-adjusted analysis." + stage_notes: + seed: "NIM is largely theoretical pre-launch. Model it based on target lending + products, expected cost of capital, and regulatory capital + requirements." + series_a: "Early NIM data from initial loan portfolio. Watch for NIM compression + as the portfolio diversifies from early, hand-picked borrowers to + broader origination." + series_b_plus: "Stable NIM demonstrates funding advantage and pricing + discipline. A bank charter can transform NIM by replacing warehouse + lending with deposit funding (Varo, SoFi). Capital adequacy requirements + constrain leveraged NIM expansion." + data_sources: + - source: "FDIC Quarterly Banking Profile" + year: "2023" + - source: "SoFi Annual Reports" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "default-rate", "loan-origination-volume", "capital-adequacy-ratio" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "NIM in isolation is dangerous. A high NIM paired with high default + rates produces negative risk-adjusted returns. Always evaluate NIM net of + expected credit losses. Regulatory scrutiny increases when NIM + significantly exceeds industry averages — regulators may view it as a + signal of predatory pricing." + + - name: "Default Rate / Non-Performing Loans" + id: "default-rate" + category: "financial" + definition: "The percentage of the loan portfolio that has defaulted or is + classified as non-performing (typically 90+ days past due). This is the + primary credit risk metric for lending fintechs and directly determines + whether net interest margin translates to actual profit." + formula: "Non-Performing Loans / Total Outstanding Loan Portfolio x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 10%" + signal: "Credit underwriting is failing. At this default rate, most lending + models are unprofitable regardless of NIM. Regulators will scrutinize + underwriting standards." + below_average: + value: "5-10%" + signal: "Elevated credit losses consuming most of the interest margin. Common in + subprime or thin-file lending. Requires exceptional NIM to remain + viable." + average: + value: "2-5%" + signal: "Standard range for fintech lenders. FDIC average non-performing loan + ratio was approximately 0.7% for banks in 2023 — fintech lenders + serving underbanked populations typically run higher." + good: + value: "1-2%" + signal: "Strong credit quality. Indicates effective underwriting models, + appropriate risk pricing, and disciplined portfolio management." + excellent: + value: "< 1%" + signal: "Exceptional credit quality. Typical of prime lending, secured lending, + or highly selective origination. Verify that the portfolio is not too + conservative — under-lending limits growth." + stage_notes: + seed: "Default rate is unknown pre-origination. Model based on FICO score + distribution, loan type, and comparable fintech portfolios. Regulators + require capital reserves against expected losses." + series_a: "Early vintage data emerges. Beware of vintage bias — default rates + are artificially low in young portfolios because defaults take 6-18 + months to materialize." + series_b_plus: "Mature vintage analysis across multiple economic conditions. + Stress-test the portfolio against recession scenarios. Rating agencies + and investors scrutinize default trends when evaluating securitization + or warehouse facility renewal." + data_sources: + - source: "FDIC Quarterly Banking Profile" + year: "2023" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "net-interest-margin", "loan-origination-volume", "capital-adequacy-ratio" ] + related_skills: [ "scenario-planning", "black-swans" ] + caveats: "Default rates are lagging indicators — they reflect underwriting + decisions made 6-18 months ago. Rising default rates in the current + portfolio reflect past decisions that cannot be corrected. Early detection + through delinquency tracking (30-day, 60-day) is essential. Regulatory + agencies examine default rates as part of fair lending and UDAP/UDAAP + enforcement." + + - name: "Loan Origination Volume" + id: "loan-origination-volume" + category: "growth" + definition: "The total dollar value of new loans originated in a given period. + Measures the lending engine's throughput and growth velocity." + formula: "SUM(new_loan_principal) over period" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $1M monthly originations at 12 months" + signal: "Insufficient volume to build statistically meaningful credit models or + achieve economies of scale in servicing." + below_average: + value: "$1M-$10M monthly originations" + signal: "Early-stage lending volume. Credit models are still learning. Warehouse + facility utilization is low, increasing cost of capital." + average: + value: "$10M-$50M monthly originations" + signal: "Meaningful scale. Portfolio data supports credit model refinement. + Warehouse facility economics improve." + good: + value: "$50M-$250M monthly originations" + signal: "Strong origination velocity. Sufficient volume for securitization. + Multiple lending products may contribute." + excellent: + value: "> $250M monthly originations" + signal: "Institutional scale. SoFi originated $4.4B in personal loans in Q4 2023 + alone. At this scale, capital markets access and cost of funds become + the primary competitive advantages." + stage_notes: + seed: "Origination volume is minimal and manual. Regulatory licensing (state + lending licenses, NMLS registration) must be in place before origination + begins." + series_a: "Origination growth should exceed 100% YoY. Watch origination quality + alongside quantity — loosening underwriting to grow volume is a path to + credit losses." + series_b_plus: "Capital markets strategy (securitization, forward flow + agreements, bank partnerships) becomes central to scaling origination. + Regulatory capital requirements constrain balance-sheet lending." + data_sources: + - source: "SoFi Annual Reports" + year: "2023" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "net-interest-margin", "default-rate", "capital-adequacy-ratio" ] + related_skills: [ "growth-share-matrix", "scenario-planning" ] + caveats: "Origination volume can be vanity if credit quality is deteriorating. + Rapid origination growth paired with loosening underwriting standards is + the classic pattern preceding credit crises. Regulators scrutinize rapid + portfolio growth as a leading indicator of risk." + + # ───────────────────────────────────────────── + # FRAUD & SECURITY + # ───────────────────────────────────────────── + + - name: "Fraud Rate" + id: "fraud-rate" + category: "efficiency" + definition: "The percentage of total transactions identified as fraudulent, + whether caught before processing (attempted fraud) or resulting in actual + losses (realized fraud). The combined metric measures the overall fraud + exposure of the platform." + formula: "(Fraudulent Transactions / Total Transactions) x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 1.0% of transactions" + signal: "Fraud exposure is dangerously high. Card network thresholds (Visa, + Mastercard) for excessive fraud typically trigger fines or program + termination at rates above 1%." + below_average: + value: "0.5-1.0%" + signal: "Elevated fraud requiring immediate investment in detection and + prevention. Approaching card network monitoring thresholds." + average: + value: "0.1-0.5%" + signal: "Standard fraud exposure for card-not-present transactions. Industry + average for e-commerce is approximately 0.1% of transactions (Nilson + Report 2023)." + good: + value: "0.05-0.1%" + signal: "Below-average fraud rate indicating effective detection systems and + robust identity verification." + excellent: + value: "< 0.05%" + signal: "Best-in-class fraud prevention. Typically requires ML-based real-time + detection, multi-factor authentication, and sophisticated device + fingerprinting." + stage_notes: + seed: "Fraud rate data is limited. Implement basic fraud rules and 3D Secure. + Budget for fraud losses as a cost of learning." + series_a: "Fraud detection must be semi-automated. Manual review at scale is + uneconomic. Card networks impose monitoring programs above specific + thresholds." + series_b_plus: "Proprietary fraud models trained on transaction data become a + competitive moat. Low fraud rate enables lower interchange and better + network relationships. PCI-DSS compliance is mandatory." + data_sources: + - source: "Nilson Report — Card Fraud Worldwide" + year: "2023" + - source: "Stripe Radar benchmarks" + year: "2024" + related_metrics: [ "fraud-loss-rate", "cost-per-transaction" ] + related_skills: [ "systems-thinking", "scenario-planning" ] + caveats: "Fraud rate can be artificially lowered by rejecting legitimate + transactions (false positives). An aggressive fraud filter that blocks 5% + of legitimate transactions to achieve a low fraud rate destroys more + revenue than the fraud it prevents. Track false positive rate alongside + fraud rate." + + - name: "Fraud Loss Rate" + id: "fraud-loss-rate" + category: "financial" + definition: "The actual dollar losses from fraud as a percentage of total + payment volume. Unlike fraud rate (which counts incidents), fraud loss + rate measures the financial impact — the money that could not be recovered + after fraudulent transactions were processed." + formula: "(Gross Fraud Losses - Recoveries) / TPV x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 0.5% of TPV" + signal: "Fraud losses are consuming a significant portion of gross revenue. At a + 1% take rate, 0.5% fraud losses represent half of all revenue." + below_average: + value: "0.1-0.5% of TPV" + signal: "Elevated losses that materially impact profitability. Common in + high-risk verticals (gambling, crypto, cross-border) without + sophisticated detection." + average: + value: "0.05-0.1% of TPV" + signal: "Standard fraud losses for card-not-present payment processors. Global + card fraud losses averaged approximately 6.8 cents per $100 (6.8bps) + in 2022." + good: + value: "0.02-0.05% of TPV" + signal: "Below-average fraud losses indicating effective prevention, rapid + detection, and strong recovery processes." + excellent: + value: "< 0.02% of TPV" + signal: "Minimal fraud losses. Requires sophisticated ML-based detection, strong + identity verification, and effective chargeback management." + stage_notes: + seed: "Budget 20-50bps of TPV for fraud losses in early operations. Fraud + patterns are unpredictable before the platform has enough data to train + models." + series_a: "Fraud loss trajectory matters more than current level. Demonstrate + declining fraud losses per dollar processed as detection improves." + series_b_plus: "Fraud loss rate is a key due diligence item for investors and + banking partners. Card networks and regulators impose program + requirements when losses exceed thresholds." + data_sources: + - source: "Nilson Report — Card Fraud Worldwide" + year: "2023" + - source: "McKinsey Global Payments Report" + year: "2023" + related_metrics: [ "fraud-rate", "take-rate", "gross-margin" ] + related_skills: [ "balanced-scorecard", "black-swans" ] + caveats: "Fraud losses are often under-reported because they are netted against + reserves or absorbed into general COGS. Transparent fraud loss reporting + is a regulatory requirement under BSA/AML and is increasingly expected by + banking partners and card networks." + + # ───────────────────────────────────────────── + # KYC & COMPLIANCE + # ───────────────────────────────────────────── + + - name: "KYC/Onboarding Conversion Rate" + id: "kyc-conversion-rate" + category: "efficiency" + definition: "The percentage of customers who begin the onboarding/identity + verification process and successfully complete it to become active users. + This metric measures the friction that regulatory-mandated KYC imposes on + customer acquisition — a cost unique to regulated financial services." + formula: "(Customers who completed KYC / Customers who initiated KYC) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 50%" + signal: "Half of prospective customers abandon onboarding. The KYC process is + too lengthy, too confusing, or rejects too many legitimate applicants. + Each abandoned application represents wasted CAC." + below_average: + value: "50-65%" + signal: "Significant drop-off driven by excessive documentation requirements, + slow verification, or poor mobile UX during identity capture." + average: + value: "65-80%" + signal: "Standard conversion for regulated fintech onboarding. Industry average + for digital-first onboarding with identity verification is + approximately 70% (Plaid, 2023)." + good: + value: "80-90%" + signal: "Strong onboarding conversion. Indicates streamlined KYC with real-time + verification, OCR document capture, and progressive disclosure of + requirements." + excellent: + value: "> 90%" + signal: "Exceptional conversion. Possible with instant verification (Plaid + Identity, Jumio), simplified CDD for low-risk products, or embedded + onboarding within an existing trusted platform." + stage_notes: + seed: "KYC conversion is often manually managed and low. Every point of + conversion improvement directly reduces effective CAC." + series_a: "Automated KYC (OCR, database verification, liveness detection) should + bring conversion above 70%. Track drop-off by step to identify specific + friction points." + series_b_plus: "KYC conversion optimization is a continuous process. Regulatory + requirements evolve — CDD requirements under BSA/AML and EU AMLD6 may + add new verification steps that re-introduce friction." + data_sources: + - source: "Plaid Developer Reports" + year: "2023" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "cac", "kyc-cost-per-customer", "monthly-active-users" ] + related_skills: [ "systems-thinking", "product-life-cycle" ] + caveats: "KYC conversion cannot be optimized at the expense of compliance. + Regulators expect risk-based customer due diligence — simplifying KYC for + high-risk customer segments violates BSA/AML requirements. The + optimization challenge is to maintain compliance while minimizing friction + for legitimate customers." + + - name: "KYC Cost per Customer" + id: "kyc-cost-per-customer" + category: "unit-economics" + definition: "The average cost to complete identity verification and customer due + diligence for one new customer, including identity provider APIs, document + verification services, sanctions screening, PEP checks, and manual review + time for flagged applications." + formula: "(Identity Verification Costs + Sanctions/PEP Screening + Manual Review + Labor + CDD Technology Costs) / Customers Verified" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $15 per customer (consumer) / > $150 (business)" + signal: "KYC costs are a material drag on unit economics. Manual review rates + are likely above 20%, indicating poor automation or high-risk customer + mix." + below_average: + value: "$8-$15 (consumer) / $75-$150 (business)" + signal: "Above-average KYC costs. Common when using premium identity providers + without volume discounts, or when regulatory requirements mandate + enhanced due diligence for most customers." + average: + value: "$3-$8 (consumer) / $30-$75 (business)" + signal: "Standard KYC costs for digital fintech onboarding. Reflects automated + identity verification with database matching and selective manual + review." + good: + value: "$1-$3 (consumer) / $15-$30 (business)" + signal: "Efficient KYC powered by automated verification, low manual review + rates (<5%), and volume-based pricing with identity providers." + excellent: + value: "< $1 (consumer) / < $15 (business)" + signal: "Highly efficient KYC. Possible with proprietary verification systems, + pre-verified customer pools (embedded finance), or tiered KYC that + applies minimal verification for low-risk activities." + stage_notes: + seed: "KYC costs are high per customer at low volume. No volume discounts from + identity providers. Manual review rates are high as processes are + established." + series_a: "Negotiate volume-based pricing with identity providers (Jumio, + Onfido, Plaid Identity). Target <10% manual review rate." + series_b_plus: "KYC cost optimization through proprietary models, consortium + data sharing, and risk-based tiering. Regulatory requirements for + periodic KYC refresh (CDD updates) add ongoing per-customer costs." + data_sources: + - source: "CB Insights State of Fintech" + year: "2024" + - source: "Plaid Developer Reports" + year: "2023" + related_metrics: [ "cac", "kyc-conversion-rate", "regulatory-compliance-cost" ] + related_skills: [ "systems-thinking", "kaizen-bpr" ] + caveats: "KYC costs are not a one-time expense. Regulatory requirements mandate + periodic customer refresh (enhanced CDD for higher-risk customers, + sanctions list rescreening, address verification updates). The ongoing KYC + cost per customer per year may exceed the initial verification cost." + + - name: "Regulatory Compliance Cost (% of Revenue)" + id: "regulatory-compliance-cost" + category: "efficiency" + definition: "Total regulatory compliance expenditure as a percentage of net + revenue, encompassing KYC/AML operations, regulatory technology, + compliance staff, legal counsel, audit costs, license maintenance, and + regulatory reporting. This metric is unique to regulated industries and + represents the 'tax' that regulation imposes on the business model." + formula: "(Compliance Staff Costs + RegTech Spend + Legal & Audit + License Fees + + Regulatory Reporting Costs) / Net Revenue x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 25% of revenue" + signal: "Compliance costs are consuming a quarter of revenue. Typical of + early-stage fintechs building compliance infrastructure from scratch, + or companies facing regulatory enforcement actions." + below_average: + value: "15-25%" + signal: "High compliance cost burden. Common during initial license acquisition, + SOX compliance buildout, or in jurisdictions with complex + multi-regulator environments." + average: + value: "8-15%" + signal: "Standard compliance cost for established fintech companies. Banks + average approximately 10-15% of operating costs on compliance + (McKinsey 2023). Fintechs typically run at the higher end due to scale + disadvantages." + good: + value: "4-8%" + signal: "Efficient compliance through automation, regtech tools, and mature + compliance processes. Scale advantages reduce per-customer compliance + cost." + excellent: + value: "< 4%" + signal: "Highly efficient compliance — typically achieved by large-scale + fintechs with proprietary regtech, automated regulatory reporting, and + mature compliance programs. Stripe and Plaid operate in this range at + scale." + stage_notes: + seed: "Compliance costs as a percentage of revenue will be extremely high + (30-50%+) because the infrastructure must be built before revenue + scales. This is expected and investors should be educated accordingly." + series_a: "Compliance cost percentage should decline as revenue scales faster + than compliance infrastructure costs. Target 15-20% and demonstrate the + trajectory toward 10%." + series_b_plus: "At scale, compliance costs should approach 5-10% of revenue. + Investment in regtech automation is the primary lever. Regulatory + changes (new reporting requirements, expanded licensing) can cause + step-function cost increases." + data_sources: + - source: "McKinsey Global Payments Report" + year: "2023" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "kyc-cost-per-customer", "gross-margin", "cost-to-income-ratio" ] + related_skills: [ "balanced-scorecard", "kaizen-bpr" ] + caveats: "Under-spending on compliance is more dangerous than over-spending. A + fintech with compliance costs at 2% of revenue may be under-investing — + the savings today become enforcement actions, fines, and license + revocations tomorrow. The 2023 consent orders against neobanks (Chime, + Dave) demonstrate the cost of compliance under-investment." + + - name: "Capital Adequacy Ratio" + id: "capital-adequacy-ratio" + category: "financial" + definition: "The ratio of regulatory capital to risk-weighted assets, measuring + the institution's capacity to absorb losses while protecting depositors + and the financial system. Applicable to fintechs with bank charters, + lending operations, or custody of customer funds." + formula: "(Tier 1 Capital + Tier 2 Capital) / Risk-Weighted Assets x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "< 8% (below Basel III minimum)" + signal: "Below regulatory minimum. The institution faces immediate supervisory + action, restrictions on lending, and potential license revocation." + below_average: + value: "8-10%" + signal: "At or near minimum requirements. No buffer for unexpected losses. + Regulators will impose heightened surveillance and may restrict + growth." + average: + value: "10-13%" + signal: "Standard capitalization. Meets requirements with moderate buffer. Most + U.S. banks maintain ratios in this range." + good: + value: "13-18%" + signal: "Well-capitalized with significant buffer. Provides flexibility for + portfolio growth, acquisitions, or absorption of credit cycle + downturns." + excellent: + value: "> 18%" + signal: "Very well-capitalized. Common in fintech banks pre-growth phase when + capital has been raised but not yet deployed into earning assets. + Over-capitalization at mature scale may indicate under-deployment of + capital." + stage_notes: + seed: "Capital adequacy is relevant only for charter holders. For non-bank + fintechs, the equivalent is cash reserves relative to customer funds + held and contingent liabilities." + series_a: "If pursuing a bank charter, demonstrate a clear capital plan. + Regulators evaluate the institution's ability to maintain capital + adequacy under stress scenarios." + series_b_plus: "Capital planning becomes a board-level topic. Basel III + requirements, CECL accounting standards, and stress testing (DFAST for + larger institutions) govern capital management." + data_sources: + - source: "Basel Committee on Banking Supervision" + year: "2023" + - source: "FDIC Quarterly Banking Profile" + year: "2023" + related_metrics: [ "net-interest-margin", "default-rate", "loan-origination-volume" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "Capital adequacy requirements differ by charter type and jurisdiction. + De novo bank charters typically face higher capital requirements for the + first 3-7 years. ILC charters, fintech charters, and international + charters each carry different capital standards. Non-bank fintechs with + bank partnerships must understand their partner bank's capital + constraints." + + # ───────────────────────────────────────────── + # FINANCIAL PERFORMANCE + # ───────────────────────────────────────────── + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "Net revenue minus cost of revenue (interchange, processing fees, + fraud losses, hosting, compliance-driven transaction costs) as a + percentage of net revenue. Gross margin in fintech varies dramatically by + business model — payments businesses operate at lower gross margins than + software-like revenue streams." + formula: "(Net Revenue - Cost of Revenue) / Net Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 30%" + signal: "Thin margins indicating the business is primarily a payment + pass-through with minimal value-add. Vulnerable to interchange changes + and processor price increases." + below_average: + value: "30-45%" + signal: "Low-margin financial services. Common in pure-play payment processing + where interchange is the dominant COGS component." + average: + value: "45-60%" + signal: "Standard range for diversified fintech companies with a mix of + transaction-based and subscription/fee-based revenue. Nubank's gross + margin approached 50% at IPO." + good: + value: "60-75%" + signal: "Strong margins driven by SaaS-like revenue components (subscription + fees, platform fees, data products) layered on top of transaction + processing." + excellent: + value: "> 75%" + signal: "Software-like margins. Typical of regtech, B2B fintech infrastructure, + or platforms where the payment processing is a distribution channel + for higher-margin products." + stage_notes: + seed: "Gross margin is often negative at seed due to fixed compliance and + infrastructure costs spread over minimal revenue." + series_a: "Gross margin trajectory matters more than current level. Demonstrate + the path to 50%+ through scale and product mix evolution." + series_b_plus: "Investors evaluate gross margin by revenue line. Separate + transaction-based revenue (lower margin) from platform/subscription + revenue (higher margin). The ratio determines valuation multiples — + SaaS-like margins command SaaS-like multiples." + data_sources: + - source: "Nubank S-1 Filing" + year: "2021" + - source: "Stripe Financial Reports" + year: "2024" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "take-rate", "cost-per-transaction", "regulatory-compliance-cost" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Gross margin definitions vary across fintech sub-sectors. Lending + fintechs may classify credit losses as COGS or below the gross margin + line. Payment processors differ on whether fraud losses are COGS or + operating expenses. Normalize definitions when benchmarking against + peers." + + - name: "Net Revenue Retention" + id: "net-revenue-retention" + category: "retention" + definition: "The percentage of revenue retained from existing customers after + accounting for expansion (new products, increased usage), contraction + (downgrade, reduced volume), and churn. In fintech, NRR measures the + platform's ability to deepen customer relationships through cross-sell and + increased transaction volume." + formula: "(Starting Revenue + Expansion - Contraction - Churn) / Starting + Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 90%" + signal: "Significant revenue erosion from existing customers. In payments, this + may reflect merchant attrition or transaction volume decline. In + lending, it may indicate borrowers refinancing elsewhere." + below_average: + value: "90-100%" + signal: "Flat to slightly declining revenue from existing customers. The + platform is not successfully cross-selling or the core product faces + competitive displacement." + average: + value: "100-115%" + signal: "Modest net expansion from existing customers. Standard for fintech + platforms where transaction volume grows naturally with customer + business growth." + good: + value: "115-130%" + signal: "Strong expansion driven by effective cross-sell (adding lending to + payments, insurance to banking) or organic transaction volume growth. + Nubank achieved 120%+ NRR through product expansion." + excellent: + value: "> 130%" + signal: "Exceptional expansion. Indicates a platform where customers adopt + multiple products over time — the fintech superapp model (SoFi, + Nubank, Revolut)." + stage_notes: + seed: "NRR is unmeasurable with few customers. Track qualitative signals: are + existing customers requesting additional products or processing more + volume?" + series_a: "NRR above 100% is a strong signal. In fintech, cross-sell into + adjacent products (payments -> lending -> deposits) is the primary NRR + driver." + series_b_plus: "NRR above 120% signals platform economics. Investors value + fintech platforms with strong NRR at higher multiples because cross-sell + reduces blended CAC." + data_sources: + - source: "Nubank S-1 Filing" + year: "2021" + - source: "SoFi Annual Reports" + year: "2023" + related_metrics: [ "ltv", "monthly-active-users", "transactions-per-user" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Fintech NRR can be inflated by macroeconomic tailwinds — rising + transaction volumes in a growing economy lift NRR without any action by + the platform. Stress-test NRR against recession scenarios where + transaction volumes decline." + + # ───────────────────────────────────────────── + # ENGAGEMENT & GROWTH + # ───────────────────────────────────────────── + + - name: "Monthly Active Users" + id: "monthly-active-users" + category: "product" + definition: "The number of unique users who perform at least one qualifying + financial activity (transaction, login with balance check, transfer, loan + payment) within a calendar month. In fintech, MAU should exclude passive + account holders who have not engaged — the definition must reflect genuine + financial activity." + formula: "COUNT(DISTINCT users with qualifying_activity) over calendar month" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20% of registered users are monthly active" + signal: "The product is not embedded in customers' financial lives. High + dormancy indicates the product is used occasionally rather than + habitually." + below_average: + value: "20-40% of registered users active" + signal: "Moderate engagement. Common for single-product fintechs where usage is + periodic (lending, insurance) rather than daily." + average: + value: "40-60% of registered users active" + signal: "Solid engagement. Standard for neobanks and payment apps where regular + transactions drive recurring usage." + good: + value: "60-80% of registered users active" + signal: "Strong engagement indicating the product is a primary financial tool. + Nubank reported 80%+ MAU/total customer ratio." + excellent: + value: "> 80% of registered users active" + signal: "Exceptional engagement. The product is the customer's primary financial + account. High MAU/registered ratio correlates with strong NRR and low + churn." + stage_notes: + seed: "MAU is small in absolute terms. Focus on engagement depth (transactions + per active user) rather than breadth." + series_a: "MAU growth rate and MAU/registered ratio are the key metrics. + Declining ratio as acquisition scales suggests the new cohorts are less + engaged than early adopters." + series_b_plus: "DAU/MAU ratio becomes important — daily engagement indicates the + product is a financial utility. Nubank and Revolut target DAU/MAU above + 30%." + data_sources: + - source: "Nubank Annual Reports" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "transactions-per-user", "net-revenue-retention", "cac" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "MAU definitions vary across fintechs and can be gamed. A 'login' + should not count as an active user event if no financial activity + occurred. Define MAU consistently and disclose the definition to + investors. Regulators may also require active account reporting for + dormant account regulations." + + - name: "Transactions per User per Month" + id: "transactions-per-user" + category: "product" + definition: "The average number of transactions each active user conducts per + month. Measures engagement depth and the degree to which the product is + embedded in the customer's daily financial life." + formula: "Total Monthly Transactions / Monthly Active Users" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2 transactions/user/month" + signal: "Low engagement. The product is not habitual — customers use it for + occasional, specific needs rather than as a daily financial tool." + below_average: + value: "2-5 transactions/user/month" + signal: "Moderate engagement. Typical of single-use-case products (bill pay, + remittance, specific investment activity)." + average: + value: "5-10 transactions/user/month" + signal: "Solid engagement. Standard for neobanks where a debit card and direct + deposit drive regular transaction activity." + good: + value: "10-20 transactions/user/month" + signal: "Strong engagement indicating the product serves multiple financial + needs. Cross-sell into payments, savings, and investments drives + transaction frequency." + excellent: + value: "> 20 transactions/user/month" + signal: "Exceptional engagement. The product is the customer's primary financial + account. High transaction frequency drives data advantage and + cross-sell opportunity." + stage_notes: + seed: "Transaction frequency data is limited. Track whether early users increase + their transaction frequency over time — a strong product-market fit + signal." + series_a: "Transactions per user should increase as the product adds use cases. + A declining trend despite product additions signals a product problem." + series_b_plus: "High transactions per user drives revenue per user and creates + data moats for credit underwriting, personalization, and fraud + detection." + data_sources: + - source: "Nubank Annual Reports" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "monthly-active-users", "revenue-per-transaction", "net-revenue-retention" ] + related_skills: [ "net-promoter-score", "systems-thinking" ] + caveats: "Average transactions per user masks bimodal distribution. Power users + may transact 50+ times per month while dormant users transact once. + Segment this metric by cohort and user type to expose the actual + engagement distribution." + + - name: "Deposit Growth Rate" + id: "deposit-growth-rate" + category: "growth" + definition: "The month-over-month or year-over-year growth rate of customer + deposits held on the platform. For neobanks and deposit-taking fintechs, + deposit growth is both a customer engagement metric and a funding cost + metric — deposits are the cheapest source of lending capital." + formula: "(Deposits_current - Deposits_prior) / Deposits_prior x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% QoQ deposit growth" + signal: "Deposit growth stalling. Customers are not deepening their relationship + with the platform or are moving deposits to competitors offering + higher yields." + below_average: + value: "5-15% QoQ" + signal: "Moderate growth. Deposits are accumulating but not at the rate needed + to fund significant lending operations." + average: + value: "15-30% QoQ" + signal: "Healthy deposit growth. Sufficient to fund lending expansion and + demonstrate to regulators that the deposit base is stable." + good: + value: "30-50% QoQ" + signal: "Strong growth. Chime, Varo, and SoFi achieved 40%+ QoQ deposit growth + during high-growth phases. Indicates direct deposit adoption." + excellent: + value: "> 50% QoQ" + signal: "Exceptional growth. Typically accompanied by a catalytic event — + product launch, rate promotion, or viral moment. Verify that deposits + are 'sticky' (direct deposit) not 'hot money' (rate-chasing)." + stage_notes: + seed: "Deposits are minimal if the product is pre-launch. For neobanks, the + first milestone is direct deposit adoption — this signals primary + banking relationship." + series_a: "Deposit growth rate and average deposit balance per customer are the + key metrics. Regulators monitor deposit stability for charter + applications." + series_b_plus: "Deposit growth enables the lending engine. The cost of deposit + funding (interest paid) versus wholesale funding (warehouse lines) is + the primary margin differentiator for neobanks." + data_sources: + - source: "SoFi Annual Reports" + year: "2023" + - source: "FDIC Quarterly Banking Profile" + year: "2023" + related_metrics: [ "net-interest-margin", "monthly-active-users", "net-revenue-retention" ] + related_skills: [ "growth-share-matrix", "product-life-cycle" ] + caveats: "Deposit growth driven by high interest rate promotions produces 'hot + money' — deposits that leave when rates normalize. Measure the percentage + of deposits that arrive via direct deposit (sticky) versus manual transfer + (potentially rate-sensitive). Regulators evaluate deposit stability as + part of safety and soundness examinations." + + # ───────────────────────────────────────────── + # WEALTHTECH METRICS + # ───────────────────────────────────────────── + + - name: "Assets Under Management" + id: "aum" + category: "growth" + definition: "The total market value of financial assets managed on behalf of + customers. AUM is the top-line scale metric for wealthtech, robo-advisors, + and investment platforms. Revenue is typically a percentage of AUM + (management fee), making AUM growth the primary revenue driver." + formula: "SUM(customer_portfolio_market_value)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $10M AUM at 12 months" + signal: "Insufficient scale to cover operating costs. At a 25bps management fee, + $10M AUM generates only $25K annual revenue." + below_average: + value: "$10M-$100M AUM" + signal: "Early traction but economics are challenging. A 50bps fee on $50M AUM + generates $250K annual revenue." + average: + value: "$100M-$1B AUM" + signal: "Meaningful scale. Betterment and Wealthfront surpassed $1B AUM within 3 + years. Sufficient to attract institutional partnerships." + good: + value: "$1B-$10B AUM" + signal: "Strong scale with improving unit economics. Management fee revenue + supports meaningful team and technology investment." + excellent: + value: "> $10B AUM" + signal: "Institutional scale. Betterment manages approximately $35B; Wealthfront + approximately $50B. At this scale, even 1bps of fee optimization is + material." + stage_notes: + seed: "AUM is minimal. Focus on demonstrating investment methodology and + regulatory compliance (RIA registration with SEC or state regulators)." + series_a: "AUM growth rate and average account balance are the key metrics. SEC + registration required at $100M+ AUM. Compliance costs step up with + registration." + series_b_plus: "AUM growth must be decomposed into net flows (customer deposits + minus withdrawals) and market appreciation. Investors scrutinize net + flows because market appreciation is not attributable to the platform's + efforts." + data_sources: + - source: "a16z Fintech Reports" + year: "2024" + - source: "CB Insights State of Fintech" + year: "2024" + related_metrics: [ "monthly-active-users", "net-revenue-retention", "cac" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "AUM is heavily influenced by market movements. A wealthtech platform + can report 30% AUM growth with zero net customer deposits if the market + rises 30%. Always decompose AUM changes into net flows and market + appreciation. SEC and FINRA regulations govern AUM calculation and + disclosure methodology." + + # ───────────────────────────────────────────── + # OPERATIONAL EFFICIENCY + # ───────────────────────────────────────────── + + - name: "Cost to Income Ratio" + id: "cost-to-income-ratio" + category: "efficiency" + definition: "Total operating expenses divided by total operating income, + measuring the operational efficiency of the financial institution. This is + the banking industry's core efficiency metric, and fintech companies + targeting bank economics must track it. Lower ratios indicate more + efficient operations." + formula: "Operating Expenses / Operating Income x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 100% (operating at a loss)" + signal: "Expenses exceed income. Expected at early stage but unsustainable. + Investor capital is funding operations, not just growth." + below_average: + value: "80-100%" + signal: "Near break-even operations. The institution is not yet generating + meaningful operating profit." + average: + value: "50-80%" + signal: "Standard range for fintech companies approaching maturity. Traditional + banks average 55-65%. Digital-first fintechs should target the lower + end." + good: + value: "35-50%" + signal: "Efficient operations. Nubank achieved a cost-to-income ratio below 40% + — demonstrating the structural efficiency advantage of digital-first + financial services." + excellent: + value: "< 35%" + signal: "Exceptional efficiency. Significantly better than traditional banking. + Achieved through digital-only operations, automated processes, and + minimal branch infrastructure." + stage_notes: + seed: "Cost-to-income ratio is extremely high (200%+) and irrelevant at seed. + Focus on building the infrastructure that will drive efficiency at + scale." + series_a: "Ratio should improve quarterly. Demonstrate operating leverage — + revenue growing faster than operating costs." + series_b_plus: "Target sub-50% and declining. Nubank's path from >100% to <40% + was central to its equity story. Regulators evaluate this ratio for + safety and soundness — excessively low ratios may indicate + under-investment in compliance or risk management." + data_sources: + - source: "Nubank Annual Reports" + year: "2023" + - source: "FDIC Quarterly Banking Profile" + year: "2023" + - source: "McKinsey Global Payments Report" + year: "2023" + related_metrics: [ "gross-margin", "regulatory-compliance-cost", "net-interest-margin" ] + related_skills: [ "kaizen-bpr", "balanced-scorecard" ] + caveats: "Cost-to-income ratio comparisons between fintechs and traditional + banks are misleading without adjusting for business mix. A bank with + branches, lending operations, and wealth management has fundamentally + different cost structure than a digital-only payment processor. Compare + within peer group." + + - name: "ARPU — Average Revenue per User" + id: "arpu" + category: "unit-economics" + definition: "The average monthly or annual net revenue generated per active user + across all revenue streams (transaction fees, interchange, interest + income, subscription fees, premium services). ARPU measures the + monetization intensity of the user base." + formula: "Total Net Revenue / Average Monthly Active Users" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $2/month per user (consumer)" + signal: "Low monetization. The product has not found a revenue model that + matches engagement. Common in free neobanks relying solely on + interchange from debit transactions." + below_average: + value: "$2-$5/month (consumer)" + signal: "Below-average monetization. Typical of single-revenue-line fintech + products (interchange only, or low-frequency lending only)." + average: + value: "$5-$15/month (consumer)" + signal: "Standard monetization. Nubank reported approximately $8 monthly ARPU at + IPO. Sufficient to fund operations if retention is strong." + good: + value: "$15-$40/month (consumer)" + signal: "Strong monetization through multiple revenue streams. Cross-sell into + lending, insurance, and premium services lifts ARPU above + single-product levels." + excellent: + value: "> $40/month (consumer)" + signal: "Exceptional ARPU. SoFi achieved $50+ monthly ARPU through multi-product + adoption (lending + investing + banking). Indicates deep platform + engagement." + stage_notes: + seed: "ARPU is low and unstable. Focus on identifying which revenue streams will + drive future ARPU growth." + series_a: "ARPU growth trajectory matters. Demonstrate the ARPU uplift as + customers adopt additional products — the multi-product ARPU story is + central to fintech platform narratives." + series_b_plus: "ARPU by product vintage and product adoption tier should be the + reporting standard. Show that customers who adopt 3+ products generate + 5-8x the ARPU of single-product customers." + data_sources: + - source: "Nubank S-1 Filing" + year: "2021" + - source: "SoFi Annual Reports" + year: "2023" + - source: "a16z Fintech Reports" + year: "2024" + related_metrics: [ "monthly-active-users", "net-revenue-retention", "ltv" ] + related_skills: + - business-model-canvas + caveats: "ARPU that relies heavily on interchange is vulnerable to regulatory + caps (Durbin, PSD2 IFR). Separate ARPU by revenue type to understand + regulatory exposure. Lending-driven ARPU is subject to credit cycle risk — + high ARPU from interest income in benign credit conditions may vanish in a + downturn." + related_content: + - kind: diagnostic + ref: pricing-diagnosis diff --git a/plugins/foreman/content/industry-packs/fintech/fintech-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/fintech/fintech-diagnostic-rules.yaml new file mode 100644 index 0000000..452d240 --- /dev/null +++ b/plugins/foreman/content/industry-packs/fintech/fintech-diagnostic-rules.yaml @@ -0,0 +1,1360 @@ +# Fintech Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in a fintech context. +# The diagnostic agent loads these rules when the fintech industry pack is active. +# +# REGULATORY PRINCIPLE: Every diagnostic adaptation addresses how regulation +# shapes the diagnosis. In fintech, regulatory compliance failure is always +# a potential root cause — and always a potential consequence of other failures. +# Diagnostics must surface regulatory dimensions even when the presenting +# symptom appears purely commercial. +# +# Adaptation types: +# as-is — The diagnostic works without modification for fintech companies. +# enhanced — The diagnostic is relevant but benefits from additional fintech-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for fintech. + +pack_metadata: + sector: "fintech" + display_name: "Fintech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Fintech churn has a dimension absent from other + industries: compliance-driven involuntary churn. Account closures + triggered by KYC failures, AML risk reviews, and fraud suspicion create + churn that is not product-driven and cannot be solved by product + improvements. Separating compliance-driven churn from product/market churn + is essential for accurate diagnosis." + additional_triage_questions: + - question: "What percentage of customer departures are compliance-driven (account + closures from KYC failures, risk reviews, fraud flags) versus + voluntary (customer chose to leave)?" + purpose: "Compliance-driven churn is a regulatory cost, not a product problem. + High compliance-driven churn may indicate overly aggressive risk + models or poor KYC UX, but the solution lies in compliance process + optimization, not product features." + routing_impact: "High compliance-driven churn (>15% of total) routes to KYC/AML + process optimization and false positive rate analysis. Voluntary churn + routes to standard product-market-fit and competitive analysis." + - question: "Is churn concentrated among customers who never completed full + onboarding (abandoned KYC), customers in the first 90 days (activation + failure), or established customers (value decay or competitive + switch)?" + purpose: "Fintech onboarding has unique friction from KYC/identity verification. + Early churn driven by KYC abandonment is a different problem than + churn among established users." + routing_impact: "KYC abandonment churn routes to onboarding conversion + optimization. Post-activation churn routes to product value and + engagement analysis. Established customer churn routes to competitive + and pricing analysis." + - question: "Has a banking partner policy change, regulatory update, or compliance + process change coincided with the churn increase?" + purpose: "Fintech churn can spike after regulatory changes — new KYC + requirements, tighter fraud rules, or banking partner risk appetite + changes that restrict product availability." + routing_impact: "Regulatory-coincident churn routes to compliance impact + assessment and process adaptation. Non-regulatory churn routes to + standard churn diagnosis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Compliance friction driving early-lifecycle churn" + reason: "KYC requirements, identity verification failures, and + compliance-mandated account restrictions create friction that does + not exist in unregulated products. This is the most common and most + under-diagnosed fintech churn driver." + - diagnosis: "Trust breach accelerating departure" + reason: "Financial services are trust-dependent. A single incident — + unauthorized charge, account freeze, data concern — drives churn + faster in fintech than in other industries because money is + involved." + less_likely: + - diagnosis: "Feature gap driving churn" + reason: "Fintech customers rarely leave because of missing features — they leave + because of broken trust, better rates, regulatory friction, or + competitive switching incentives. Feature gaps are over-diagnosed as + churn drivers." + fintech_specific_diagnoses: + - name: "Compliance-driven involuntary churn" + description: "Customer accounts are being closed or restricted at rates that + exceed industry norms due to overly aggressive fraud detection, + unnecessarily broad risk review criteria, or banking partner risk + appetite restrictions. The company is losing legitimate customers to + compliance processes designed to catch bad actors." + symptoms: + - "Account closure rate exceeds 3% monthly, with majority classified + as compliance-driven" + - "False positive rate on fraud detection exceeds 90% (legitimate + transactions flagged as suspicious)" + - "Customer complaints about account freezes, transaction declines, or + identity verification failures are the #1 support category" + - "Banking partner has recently tightened risk criteria or expanded + restricted categories" + routes_to_skills: [ "systems-thinking", "kaizen-bpr", "trust-equation" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] + - name: "Trust-driven voluntary churn cascade" + description: "A trust-damaging event (security incident, publicized regulatory + action, data breach, widespread account freezes) has triggered an + accelerating wave of voluntary departures. In fintech, trust erosion + spreads virally — customers see others leaving and conclude they + should leave too." + symptoms: + - "Churn rate doubles or triples within 30 days of a specific event" + - "Social media and app store reviews reference a specific + trust-breaking incident" + - "Direct deposit migrations away from the platform accelerating (the + strongest signal of primary banking relationship abandonment)" + - "New customer acquisition simultaneously declining as negative + word-of-mouth spreads" + routes_to_skills: [ "trust-equation", "black-swans", "emotional-intelligence" ] + routes_to_templates: [ "incident-postmortem", "risk-assessment-brief" ] + sector_red_flags: + - "Account closures exceeding new account openings for any sustained + period — the business is shrinking at the customer level." + - "Direct deposit migration rate increasing — customers moving their + primary banking relationship is the most consequential churn signal in + neobanking." + - "Churn coinciding with a regulatory examination or enforcement action — + indicates the event has become public knowledge and is affecting + customer confidence." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Fintech growth stalls have regulatory dimensions that + other industries do not. Growth can stall because of licensing constraints + (cannot enter new states without new licenses), banking partner capacity + limits (partner bank's own regulatory capital constrains volume), or + regulatory enforcement (consent order restricting new customer + acquisition). The growth stall diagnostic must separate market-driven + stalls from regulation-driven stalls." + additional_triage_questions: + - question: "Is the growth stall geographically constrained — are you growing in + states where you hold licenses but stalling in states where you lack + them?" + purpose: "State-by-state licensing requirements create geographic growth + ceilings that are regulatory, not market-driven. This is the most + common fintech growth constraint that is misdiagnosed as a marketing + problem." + routing_impact: "Geographic constraint routes to licensing strategy and + regulatory expansion planning. Uniform stall across licensed states + routes to product/market analysis." + - question: "Has your banking partner imposed new volume limits, customer type + restrictions, or compliance requirements that constrain onboarding + capacity?" + purpose: "Banking partner constraints are a unique fintech growth ceiling. + Partners facing their own regulatory pressure may restrict the + fintech's ability to onboard new customers." + routing_impact: "Partner-constrained growth routes to partnership + diversification and charter strategy. Non-partner-constrained growth + routes to standard growth diagnosis." + - question: "Are you approaching a regulatory threshold (number of customers, + transaction volume, assets) that triggers enhanced regulatory + requirements?" + purpose: "Certain regulatory thresholds trigger step-function compliance cost + increases — e.g., BSA/AML requirements intensify at specific + transaction volume thresholds; SEC RIA registration is required above + $100M AUM." + routing_impact: "Threshold proximity routes to compliance infrastructure + planning and scenario-planning for cost step-ups. + Non-threshold-related stall routes to standard market analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory ceiling constraining growth" + reason: "Fintech growth stalls frequently have regulatory root causes — + licensing limitations, banking partner capacity, compliance + infrastructure bottlenecks, or impending regulatory thresholds." + - diagnosis: "Banking partner dependency bottleneck" + reason: "Fintechs that depend on a single banking partner are constrained by + that partner's risk appetite, regulatory capital, and compliance + capacity. The partner becomes the growth bottleneck." + less_likely: + - diagnosis: "Macro-economic demand decline" + reason: "Fintech demand is generally robust — the shift from traditional to + digital financial services is a multi-decade secular trend. Growth + stalls attributed to 'the market' are usually regulatory, + competitive, or execution problems." + fintech_specific_diagnoses: + - name: "Banking partner dependency bottleneck" + description: "Growth is constrained by the banking partner's capacity, risk + appetite, or regulatory standing. The fintech has market demand and + product-market fit but cannot onboard customers or process volume + because the banking partner has imposed restrictions." + symptoms: + - "Marketing generates qualified leads that cannot be converted + because onboarding is paused or throttled" + - "Banking partner has communicated volume caps, customer type + restrictions, or enhanced compliance requirements" + - "Banking partner has received a regulatory order, consent agreement, + or MRA that affects its fintech programs" + - "Competitor fintechs using different banking partners are growing + while you are stalling" + routes_to_skills: + [ + "scenario-planning", + "prisoners-dilemma-and-cooperation", + "coalition-and-partnership-games" + ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] + - name: "License gap constraining addressable market" + description: "The company has product-market fit in licensed states but cannot + expand because it lacks licenses in target states. The growth ceiling + is regulatory, not commercial — demand exists in unlicensed states but + cannot be served." + symptoms: + - "Strong growth metrics in existing markets with no sign of + saturation" + - "Inbound customer interest from states where the company is not + licensed" + - "Competitors with broader licensing are gaining market share in the + unlicensed states" + - "License applications are pending but regulatory approval timelines + extend 6-18 months" + routes_to_skills: [ "first-mover-strategy", "scenario-planning" ] + routes_to_templates: [ "market-opportunity-summary", "action-plan" ] + sector_red_flags: + - "Banking partner requesting 60-day review of the fintech relationship — + often a precursor to termination or significant restriction." + - "Multiple state regulators simultaneously requesting information about + the company's operations — signals coordinated regulatory scrutiny." + - "Growth rate declining despite increasing marketing spend — suggests a + structural constraint (regulatory, partner, or infrastructure) rather + than a demand problem." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Product-market fit in fintech must be evaluated + separately from regulatory fit. A product can have strong market demand + but fail because the regulatory framework is hostile (as many crypto + products discovered in 2022-2024). Conversely, a product with modest + market demand can succeed because regulatory barriers protect it from + competition. PMF diagnosis must assess both market demand and regulatory + viability." + additional_triage_questions: + - question: "Does the product's regulatory status allow it to operate in its + current form long-term, or is there regulatory risk that the product + structure may be challenged or prohibited?" + purpose: "Some fintech products achieve apparent PMF while operating in + regulatory gray zones. If the regulatory framework is likely to + change, apparent PMF is illusory — the market signal is from a product + that may not legally exist in its current form." + routing_impact: "Regulatory-uncertain PMF routes to regulatory risk assessment + and product restructuring analysis. Regulatory-secure PMF routes to + standard scaling playbooks." + - question: "Is customer retention driven by genuine product value or by switching + costs created by regulatory friction (KYC requirements at new + provider, data portability barriers)?" + purpose: "Fintech retention can be artificially inflated by the KYC burden of + switching. If customers stay because switching requires another + identity verification process rather than because the product is + superior, PMF is weaker than retention metrics suggest." + routing_impact: "Switching-cost-driven retention routes to competitive + vulnerability analysis — open banking mandates will eliminate this + retention mechanism. Value-driven retention routes to growth + investment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "PMF exists but regulatory environment is uncertain" + reason: "Many fintech products demonstrate market demand in regulatory gray + zones. BNPL, certain crypto products, and earned wage access all + showed strong PMF signals while facing evolving regulatory + scrutiny." + - diagnosis: "PMF exists for a niche but compliance costs prevent profitable + scaling" + reason: "The per-customer compliance cost (KYC, ongoing monitoring) creates a + minimum viable customer value that excludes low-value segments. PMF + may be real but the unit economics are broken by compliance costs." + less_likely: + - diagnosis: "Product quality failure" + reason: "In fintech, product quality failures (bugs, crashes) are dangerous but + rarely the primary PMF issue. The question is usually whether the + financial product design is correct, not whether the software + works." + fintech_specific_diagnoses: + - name: "Regulatory-dependent PMF" + description: "The product has achieved strong market traction but its regulatory + status is uncertain or evolving. If the regulatory framework changes + unfavorably, the product may need fundamental restructuring or may + become illegal." + symptoms: + - "Strong user growth and engagement metrics in the context of + ambiguous or evolving regulation" + - "Regulatory bodies have issued guidance, proposed rules, or + enforcement actions affecting similar products" + - "Legal counsel advises that the product's regulatory classification + is uncertain" + - "Investors raise regulatory risk as a primary concern despite strong + commercial metrics" + routes_to_skills: [ "scenario-planning", "swot-pest-analysis", "game-theory-fundamentals" ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] + sector_red_flags: + - "Product achieves PMF in jurisdictions with light regulation but fails + in jurisdictions with strict regulation — suggests the product works + only in the absence of regulatory constraints." + - "Customer acquisition is strong but direct deposit adoption (primary + banking relationship indicator) is weak — suggests the product is a + secondary tool, not a primary financial relationship." + - "NPS is high but only among customers who have not yet experienced a + compliance friction event (fraud flag, account review, transaction + decline)." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Pricing in fintech is fundamentally different from other + industries because regulators set maximum prices for many revenue lines. + Interchange is capped, interest rates face usury limits, and fees must + comply with UDAP/UDAAP. Pricing diagnosis must begin with regulatory + ceiling analysis, then assess competitive positioning within those + constraints. The diagnosis must also evaluate whether the current pricing + structure is sustainable under anticipated regulatory changes." + additional_triage_questions: + - question: "What percentage of your revenue comes from regulated revenue lines + (interchange, interest income subject to rate caps, fees subject to + UDAP scrutiny) versus unregulated lines (subscription fees, data + products, analytics)?" + purpose: "Revenue concentration in regulated lines creates pricing risk — + regulatory changes can compress revenue without any commercial + recourse. The diagnosis must assess pricing power in the context of + regulatory constraints." + routing_impact: "High regulated-revenue concentration (>70%) routes to revenue + diversification strategy and regulatory risk assessment. Diversified + revenue routes to standard pricing optimization." + - question: "Have any of your fees been identified as potential 'junk fees' under + current CFPB guidance, or has any regulatory body questioned the + transparency or fairness of your pricing?" + purpose: "CFPB junk fee enforcement is targeting late fees, overdraft fees, and + non-sufficient fund fees across the industry. Pricing structures that + rely on these revenue lines face regulatory compression." + routing_impact: "Regulatory fee risk routes to immediate pricing restructure + with compliance review. No regulatory concern routes to standard + pricing optimization." + - question: "How does your pricing compare to the regulatory maximum in each + jurisdiction? Are you priced near the ceiling, at midpoint, or well + below?" + purpose: "Pricing near regulatory ceilings leaves no room for competitive + response and may attract regulatory attention. Pricing well below + ceilings may indicate under-pricing or may reflect the appropriate + competitive positioning." + routing_impact: "Near-ceiling pricing routes to competitive analysis and + regulatory risk review. Below-ceiling pricing routes to standard + willingness-to-pay and value-capture analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Interchange compression from regulatory or network changes" + reason: "Interchange revenue faces structural compression from Durbin Amendment + expansion, PSD2 IFR tightening, and card network rate adjustments. + This is the most common pricing pressure in payments fintech." + - diagnosis: "Fee structure under regulatory scrutiny" + reason: "CFPB junk fee initiative, state attorney general enforcement, and + class-action litigation are actively targeting fee structures across + fintech. Pricing that was standard three years ago may be + non-compliant today." + less_likely: + - diagnosis: "Over-pricing relative to competition" + reason: "Fintech markets are generally competitive on price. Under-pricing + (leaving money on the table through flat-rate models or excessive + discounting) is more common than over-pricing." + fintech_specific_diagnoses: + - name: "Regulated revenue concentration risk" + description: "The majority of revenue comes from revenue lines subject to + regulatory caps or requirements. A regulatory change — interchange cap + reduction, interest rate ceiling, fee prohibition — could eliminate a + significant portion of revenue without any market-driven alternative." + symptoms: + - "More than 70% of revenue from interchange, net interest income, or + regulated fees" + - "Pending or proposed regulation that would affect the primary + revenue line" + - "Revenue per customer declining despite stable or growing customer + engagement (regulatory compression, not market compression)" + - "Inability to raise prices because the current price is at or near + regulatory maximums" + routes_to_skills: + - scenario-planning + - business-model-canvas + routes_to_templates: [ "unit-economics-snapshot", "risk-assessment-brief" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "Revenue per transaction declining without a corresponding increase in + transaction volume — signals take rate compression from regulatory or + competitive forces." + - "CFPB, state AG, or card network inquiry specifically about fee + structures — the revenue line is under active regulatory review." + - "Banking partner renegotiating revenue share terms — may indicate the + partner is absorbing regulatory costs and passing them through." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Fintech fundraising is uniquely affected by regulatory + status. Investors evaluate regulatory risk as a primary investment + criterion — the company's license status, compliance infrastructure, + banking partner stability, and regulatory history directly affect + valuation and investability. A fintech with strong metrics but weak + regulatory standing will struggle to raise; a fintech with moderate + metrics but a bank charter will command a premium." + additional_triage_questions: + - question: "What is your current regulatory status — what licenses do you hold, + what applications are pending, and have you received any regulatory + orders, MRAs, or enforcement actions?" + purpose: "Regulatory status is a gating criterion for fintech investment. Most + institutional investors will not invest in a fintech with unresolved + enforcement actions or pending license revocations." + routing_impact: "Clean regulatory status routes to standard fundraising + preparation. Regulatory issues route to remediation planning before + fundraising — raising with regulatory problems on the record depresses + valuation and limits investor pool." + - question: "Can you articulate your regulatory moat — how does your compliance + infrastructure, licensing, or charter create durable competitive + advantage?" + purpose: "Sophisticated fintech investors view regulatory compliance as a + competitive advantage, not just a cost. The ability to articulate + regulatory moat demonstrates strategic maturity." + routing_impact: "Strong regulatory narrative routes to fundraising execution. + Weak regulatory narrative routes to regulatory strategy development + before fundraising." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory risk deterring investors" + reason: "Post-2022, fintech investors are heavily weighting regulatory risk. The + wave of consent orders and the Synapse BaaS collapse made regulatory + due diligence the primary filter for many fintech-focused VCs." + - diagnosis: "Banking partner instability creating investability concerns" + reason: "Investors now evaluate banking partner risk as company risk. A fintech + dependent on a single BaaS provider that is facing its own + regulatory issues will struggle to raise regardless of its + commercial metrics." + less_likely: + - diagnosis: "Market too small" + reason: "Financial services markets are enormous. The 'market too small' + objection in fintech usually means the investor does not believe the + company can achieve sufficient market share, not that the market is + too small." + fintech_specific_diagnoses: + - name: "Regulatory risk premium depressing valuation" + description: "The company's commercial metrics warrant a higher valuation, but + investors are applying a regulatory risk discount due to uncertain + licensing, pending regulatory changes, or banking partner + instability." + symptoms: + - "Investor feedback consistently cites 'regulatory risk' as a primary + concern despite strong commercial metrics" + - "Valuation offers are 30-50% below comparable non-regulated + technology companies with similar metrics" + - "Investors request extensive regulatory due diligence that extends + the fundraising timeline" + - "Term sheets include regulatory-triggered provisions (accelerated + repayment, valuation adjustments, additional board seats if + enforcement actions occur)" + routes_to_skills: [ "scenario-planning", "competitive-negotiation", "trust-equation" ] + routes_to_templates: [ "fundraising-deck-outline", "due-diligence-checklist" ] + sector_red_flags: + - "Unable to provide a clean regulatory history to investors — any past + enforcement actions or consent orders must be disclosed and remediated + before fundraising." + - "Banking partner relationship is on a 90-day or shorter contract — + investors view this as existential risk." + - "Fundraising during a period of active regulatory examination — + examiners' findings could materially change the company's risk profile + mid-raise." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Revenue in fintech decomposes into regulated and + unregulated streams with fundamentally different risk profiles and growth + dynamics. Interchange revenue is subject to regulatory caps and network + rate changes. Interest income is subject to credit cycle risk and rate + caps. Fee revenue is subject to UDAP/UDAAP enforcement. + Subscription/SaaS-like revenue is largely unregulated. The revenue + diagnostic must separately evaluate each stream's health, regulatory risk, + and growth potential." + additional_triage_questions: + - question: "Decompose your revenue by type: interchange/processing fees, net + interest income, transaction fees, subscription/platform fees, and + other. Which types are growing and which are compressing?" + purpose: "Each fintech revenue type has different regulatory exposure, + competitive dynamics, and growth characteristics. A single 'revenue' + metric masks critical composition changes." + routing_impact: "Interchange compression routes to diversification strategy. NII + decline routes to credit and funding cost analysis. Fee compression + routes to UDAP/UDAAP risk review. Subscription growth routes to + product expansion strategy." + - question: "Have any recent regulatory changes, card network rate adjustments, or + banking partner term changes affected your revenue per transaction?" + purpose: "Fintech revenue can decline due to external regulatory or partner + actions rather than market dynamics. Distinguishing externally-imposed + revenue compression from market-driven compression changes the + response strategy." + routing_impact: "Externally-imposed compression routes to regulatory adaptation + and revenue diversification. Market-driven compression routes to + competitive analysis and pricing optimization." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Interchange/regulatory compression eroding transaction revenue" + reason: "Structural interchange compression from Durbin Amendment expansion + proposals, PSD2 IFR, and card network rate adjustments is the most + common revenue challenge in payments fintech." + - diagnosis: "Credit cycle deterioration compressing net interest income" + reason: "Rising default rates consume NIM. Lending fintechs that originate + during benign credit conditions face revenue compression when the + cycle turns." + less_likely: + - diagnosis: "Pricing too low" + reason: "Fintech pricing is often at or near regulatory ceilings. Under-pricing + is less common than in SaaS because regulatory frameworks often + define the pricing landscape." + fintech_specific_diagnoses: + - name: "Credit cycle revenue compression" + description: "Rising default rates are consuming the net interest margin, + compressing lending revenue even as origination volume grows. The + revenue problem is a credit quality problem, not a pricing or volume + problem." + symptoms: + - "Loan origination volume growing but net lending revenue declining + or flat" + - "Default rate increasing across recent vintages" + - "Provision for credit losses increasing as percentage of revenue" + - "Warehouse lender or securitization counterparty requesting enhanced + credit data or tightening advance rates" + routes_to_skills: [ "scenario-planning", "black-swans", "balanced-scorecard" ] + routes_to_templates: [ "unit-economics-snapshot", "risk-assessment-brief" ] + sector_red_flags: + - "Revenue per transaction declining for three consecutive quarters — + signals structural take rate compression." + - "Net interest margin declining while origination volume grows — classic + credit deterioration pattern." + - "Revenue concentration in a single stream above 80% — existential risk + from regulatory change affecting that stream." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Competitive threats in fintech include a category absent + from other industries: regulatory-enabled competition. Open banking + mandates (PSD2, Section 1033) allow competitors to access customer data, + demolishing data moats. New charter types (fintech charter proposals, ILC + charters) allow competitors to access banking capabilities. Big tech + companies (Apple, Google, Amazon) can enter financial services by + leveraging existing trust, distribution, and regulatory relationships. + Regulatory changes do not just affect the company — they reshape the + competitive landscape." + additional_triage_questions: + - question: "Is the competitive threat from a peer fintech, a traditional bank + launching digital products, big tech entering your space (Apple Pay, + Google Wallet, Amazon Lending), or a regulatory change enabling new + types of competitors?" + purpose: "Each threat type requires a different response and has different + dynamics. Peer fintech competition is familiar; big tech entry is + existential; regulatory-enabled competition is structural." + routing_impact: "Peer fintech routes to differentiation strategy. Traditional + bank digital entry routes to speed-and-UX advantage analysis. Big tech + entry routes to niche defensibility and regulatory advantage analysis. + Regulatory-enabled competition routes to strategic repositioning." + - question: "Has a regulatory change (open banking mandate, new license type, fee + cap change) directly enabled or empowered a competitor?" + purpose: "Regulatory changes can overnight transform the competitive landscape. + PSD2 open banking enabled a wave of new payment initiation services in + Europe. Similar dynamics are emerging in the US." + routing_impact: "Regulatory-enabled threat routes to regulatory strategy and + differentiation beyond data access. Non-regulatory threat routes to + standard competitive analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Big tech entry into financial services" + reason: "Apple (Apple Card, Apple Savings, Apple Pay Later), Google (Google + Wallet, Plex banking), and Amazon (Amazon Lending, Amazon Pay) are + actively expanding in fintech. Their distribution and trust + advantages are existential threats to standalone fintechs." + - diagnosis: "Regulatory change enabling new competition" + reason: "Open banking mandates (PSD2, Section 1033) are structurally increasing + competition by requiring data portability. Fintechs that relied on + data lock-in for retention face new competitive dynamics." + less_likely: + - diagnosis: "Price-based competitive displacement" + reason: "In fintech, competition rarely occurs on price alone because regulatory + costs create a floor. The competitive threat is typically about + distribution, trust, UX, and product breadth rather than price." + fintech_specific_diagnoses: + - name: "Big tech financial services entry" + description: "A major technology platform (Apple, Google, Amazon, Meta) has + launched or announced a financial product that directly competes with + the company's core offering. The platform's existing user base, brand + trust, and distribution advantages create a competitive threat that + cannot be addressed through product features alone." + symptoms: + - "Major tech platform launches a competing financial product (Apple + Savings, Google Wallet expansion, Amazon Pay expansion)" + - "Customer acquisition costs increasing as the platform's free or + subsidized offering attracts price-sensitive customers" + - "Win rate declining in customer segments that overlap with the + platform's user base" + - "Media coverage shifting from 'fintech vs. banks' to 'fintech vs. + big tech'" + routes_to_skills: [ "porters-five-forces", "blue-ocean-strategy", "disruptive-innovation" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] + - name: "Open banking regulatory disruption" + description: "Open banking mandates (PSD2 in EU, Section 1033 in US) are + enabling competitors to access customer financial data that was + previously proprietary. Data-based moats are being demolished by + regulation, requiring new sources of competitive advantage." + symptoms: + - "New competitors emerging that leverage open banking APIs to offer + aggregation, comparison, or switching services" + - "Customer data portability reducing switching costs that previously + protected retention" + - "API compliance costs increasing as open banking mandates require + the company to share data with authorized third parties" + - "Competitive analysis reveals competitors using the company's own + data feeds as inputs to competing products" + routes_to_skills: [ "porters-five-forces", "first-mover-strategy", "scenario-planning" ] + routes_to_templates: [ "competitive-landscape-brief", "risk-assessment-brief" ] + sector_red_flags: + - "Apple, Google, or Amazon announces a product that directly overlaps + with the company's core offering — this is the highest-severity + competitive event in fintech." + - "Regulatory body announces open banking implementation timeline — the + company has a limited window to transition from data-lock-in to + value-based retention." + - "Traditional bank launches a digital-only subsidiary targeting the same + customer segment with lower fees and FDIC insurance — combining digital + UX with banking trust." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Strategic drift in fintech often manifests as + mission-compliance divergence — the company's strategic direction pulls + away from its compliance infrastructure. Chasing new product lines without + obtaining required licenses, entering new markets without regulatory + preparation, or pivoting the business model without assessing regulatory + implications are fintech-specific forms of strategic drift." + additional_triage_questions: + - question: "Is the company's product strategy outpacing its compliance + infrastructure — are you launching or planning products that require + regulatory capabilities you have not yet built?" + purpose: "The most dangerous form of strategic drift in fintech is when product + ambition exceeds compliance capacity. Launching a lending product + without proper licensing or a custody product without adequate + security infrastructure is not strategic ambition — it is regulatory + drift." + routing_impact: "Compliance gap routes to compliance infrastructure assessment + and licensing strategy before further product expansion. Aligned + infrastructure routes to standard strategic analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Strategy outpacing compliance infrastructure" + reason: "Growth-stage fintechs frequently build products faster than they build + compliance capabilities. The 'move fast' instinct that serves well + in technology companies creates regulatory risk in financial + services." + less_likely: + - diagnosis: "Industry disruption causing drift" + reason: "Fintech strategic drift is usually self-inflicted — chasing multiple + revenue lines, entering new geographies prematurely, or following + competitor moves without strategic rationale." + fintech_specific_diagnoses: + - name: "Mission-compliance divergence" + description: "The company's strategy is evolving in directions that strain or + exceed its regulatory licenses, compliance infrastructure, or banking + partner agreements. Product development is outpacing regulatory + preparation, creating growing risk that a product will be launched or + scaled without adequate compliance foundation." + symptoms: + - "Product roadmap includes features or products that require licenses + the company does not hold" + - "Compliance team flagging concerns about planned launches that are + being overridden by commercial leadership" + - "Banking partner pushing back on new product proposals as outside + the scope of the partnership agreement" + - "Legal counsel identifying gaps between current regulatory + permissions and planned activities" + routes_to_skills: + [ + "strategic-thinking-and-alignment", + "balanced-scorecard", + "scenario-planning" + ] + routes_to_templates: [ "quarterly-strategic-review", "risk-assessment-brief" ] + sector_red_flags: + - "Compliance team reporting to commercial leadership rather than directly + to CEO/board — creates structural pressure to subordinate compliance to + commercial goals." + - "Product launches occurring without formal compliance sign-off — + indicates compliance has been marginalized in the product development + process." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "The most common and consequential team dysfunction in + fintech is the growth-compliance tension. Product and growth teams view + compliance as an obstacle; compliance teams view growth teams as reckless. + This tension is productive when managed (compliance constraints force + creative solutions) and destructive when unmanaged (compliance is bypassed + or growth is paralyzed). Second-order dysfunction arises from the + emotional burden of handling customer financial distress — compliance and + support teams experience burnout at higher rates." + additional_triage_questions: + - question: "Is there active tension between the growth/product team and the + compliance/legal team? How are disagreements about regulatory risk + resolved?" + purpose: "Growth-compliance tension is the defining team dynamic in fintech. The + resolution mechanism — who wins when growth wants to launch a product + that compliance flags as risky — reveals the company's true risk + culture." + routing_impact: "Unresolved growth-compliance tension routes to organizational + design and decision rights framework. Healthy tension with clear + resolution mechanism routes to standard team optimization." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Growth-compliance cultural divide" + reason: "Fintech companies that hire separately from tech (for growth roles) and + banking (for compliance roles) create cultural divides. The two + groups operate with different risk tolerances, vocabularies, and + success metrics." + less_likely: + - diagnosis: "Individual performance issues" + reason: "Apparent individual underperformance in fintech compliance or + operations roles is often a system-level problem — inadequate + tooling, unclear authority, or conflicting priorities." + fintech_specific_diagnoses: + - name: "Compliance team burnout and attrition" + description: "The compliance, risk, and BSA/AML team is experiencing high + turnover due to workload, inadequate tooling, organizational + marginalization, or the emotional toll of financial crimes + investigation. Compliance team instability creates regulatory risk + that cascades through the organization." + symptoms: + - "Compliance team turnover exceeding 25% annually" + - "BSA officer or CCO departure — the most consequential single-person + risk in fintech" + - "Regulatory reporting delays or quality degradation as experienced + staff depart" + - "Compliance team members expressing frustration that their concerns + are not heard by leadership" + routes_to_skills: + [ + "trust-equation", + "emotional-intelligence", + "strategic-thinking-and-alignment" + ] + routes_to_templates: [ "team-health-check", "action-plan" ] + sector_red_flags: + - "BSA officer or Chief Compliance Officer resignation — regulators view + this as a red flag that triggers enhanced examination." + - "Compliance team being asked to 'find a way to approve' products or + customers that fail standard risk criteria." + - "Growth team referring to compliance as 'the Department of No' — + indicates a cultural divide that creates regulatory risk." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Co-founder conflict in fintech often centers on risk + appetite — one founder wants aggressive growth while the other prioritizes + compliance conservatism. This is a structurally different conflict than + technical-vs-commercial disagreements because the downside of getting it + wrong includes personal legal liability (BSA officers and compliance + officers can face individual criminal charges for willful compliance + failures)." + additional_triage_questions: + - question: "Does the conflict center on risk tolerance — specifically, does one + founder want to move faster than the other believes is safe from a + regulatory perspective?" + purpose: "Risk appetite disagreements in fintech carry legal weight. The + co-founder advocating caution may be protecting the company from + enforcement actions; the co-founder advocating speed may be protecting + the company from running out of runway." + routing_impact: "Risk appetite conflict routes to regulatory risk framework + development and explicit risk tolerance documentation. Non-regulatory + conflict routes to standard co-founder mediation." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Risk appetite divergence amplified by personal legal exposure" + reason: "In fintech, the co-founder who holds compliance responsibilities (BSA + officer, CCO role) faces personal legal liability for compliance + failures. This asymmetric risk exposure amplifies normal + disagreements into existential conflicts." + less_likely: + - diagnosis: "Equity/compensation dispute" + reason: "Co-founder conflicts in fintech more commonly stem from strategic + disagreements about regulatory approach than from compensation + disputes." + fintech_specific_diagnoses: [] + sector_red_flags: + - "Co-founder who serves as BSA officer or CCO expressing concern about + personal liability exposure — this person has a legal obligation to + escalate compliance concerns and may resign to protect themselves." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Market entry in fintech is fundamentally a regulatory + question before it is a commercial question. Every new market (geographic, + product, customer segment) requires regulatory analysis: what licenses are + needed, what compliance infrastructure must be built, what is the + regulatory approval timeline, and what are the ongoing compliance costs? A + fintech that evaluates market entry on commercial attractiveness alone + will fail — the regulatory pathway determines feasibility, timeline, and + economics." + additional_triage_questions: + - question: "What regulatory licenses, approvals, or registrations are required to + enter this market, and what is the realistic timeline and cost to + obtain them?" + purpose: "Regulatory licensing timelines range from 30 days (some state money + transmitter licenses) to 3+ years (bank charter). This is the single + most important input to market entry planning in fintech." + routing_impact: "Short licensing timeline (<6 months) routes to standard market + entry planning. Long licensing timeline (>12 months) routes to + regulatory-first market entry strategy with interim alternatives + (partnerships with licensed entities)." + - question: "Are there existing licensed entities (banks, BaaS providers, + broker-dealers) through which you could enter the market via + partnership rather than obtaining your own license?" + purpose: "Partnership-based market entry is faster but creates dependency. + Direct licensing is slower but creates a moat. The choice between + these approaches is the fundamental market entry decision in fintech." + routing_impact: "Partnership entry routes to coalition-and-partnership-games and + banking partner evaluation. Direct licensing routes to regulatory + strategy and capital planning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory barrier as primary entry challenge" + reason: "In fintech, the regulatory barrier IS the market entry challenge. + Product-market fit, competitive dynamics, and go-to-market strategy + are secondary to the fundamental question: can we legally operate in + this market?" + less_likely: + - diagnosis: "Product readiness as primary barrier" + reason: "Product readiness matters but is solvable with engineering. Regulatory + readiness is harder, slower, and more uncertain." + fintech_specific_diagnoses: + - name: "Regulatory pathway as market entry gating factor" + description: "The target market is commercially attractive but the regulatory + pathway is unclear, lengthy, or expensive. The market entry decision + depends primarily on regulatory feasibility rather than commercial + attractiveness." + symptoms: + - "Market opportunity analysis is compelling but regulatory counsel + cannot confirm a clear licensing pathway" + - "Required licenses involve multi-year application processes and + multi-million-dollar capital requirements" + - "Competitors have entered the market through regulatory approaches + that may not be replicable (grandfathered licenses, special purpose + charters)" + - "Regulatory environment in the target market is actively changing, + creating uncertainty about which requirements will apply" + routes_to_skills: [ "scenario-planning", "first-mover-strategy", "game-theory-fundamentals" ] + routes_to_templates: [ "market-opportunity-summary", "decision-rationale-memo" ] + sector_red_flags: + - "Planning market entry without regulatory counsel assessment — the most + common and most dangerous mistake in fintech expansion." + - "Entering a market based on a regulatory interpretation that has not + been tested or confirmed with the relevant regulator." + + # ───────────────────────────────────────────── + # 12. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Partnerships in fintech are regulated relationships. + Banking partnerships are subject to OCC, FDIC, and Federal Reserve + third-party risk management guidance. Card network partnerships are + governed by network rules and PCI-DSS requirements. Technology + partnerships that handle financial data are subject to GLBA service + provider requirements. Partnership diagnosis in fintech must evaluate + regulatory compliance of the partnership structure, regulatory risk shared + between partners, and the impact of partner regulatory actions on the + company." + additional_triage_questions: + - question: "Is your banking partner currently under any regulatory order, MRA, + consent agreement, or enhanced supervision that could affect your + operations?" + purpose: "A banking partner's regulatory standing directly determines the + fintech's operational stability. Partner regulatory issues become the + fintech's issues." + routing_impact: "Partner under regulatory action routes to immediate contingency + planning and secondary partner evaluation. Clean partner regulatory + status routes to standard partnership optimization." + - question: "Is the regulatory responsibility allocation between you and your + partner clearly documented, and has it been reviewed by both parties' + regulatory counsel?" + purpose: "Ambiguous compliance responsibility in fintech partnerships is the + source of most partnership breakdowns. When a regulatory issue arises, + both parties must know who is responsible." + routing_impact: "Ambiguous allocation routes to immediate partnership agreement + review and compliance responsibility matrix development. Clear + allocation routes to standard partnership health assessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Banking partner regulatory stress creating operational risk" + reason: "The 2023-2024 wave of regulatory actions against BaaS providers and + partner banks demonstrated that partner regulatory risk is the most + consequential partnership risk in fintech." + less_likely: + - diagnosis: "Partnership value misalignment" + reason: "Fintech partnerships are typically structured around regulatory + enablement — the value proposition (licensed entity enables + unlicensed activities) is usually clear, even when commercial terms + are suboptimal." + fintech_specific_diagnoses: + - name: "Banking partner regulatory contagion" + description: "The banking partner is experiencing regulatory pressure that is + flowing through to the fintech — operational restrictions, enhanced + compliance requirements, volume limitations, or potential relationship + termination driven by the bank's regulatory situation rather than the + fintech's performance." + symptoms: + - "Banking partner imposing new compliance requirements not present in + the original partnership agreement" + - "Account opening or transaction processing delays attributable to + partner-side compliance reviews" + - "Industry news reporting regulatory actions against the partner + bank's fintech programs" + - "Partner bank requesting audit access or compliance data beyond + previous requirements" + routes_to_skills: + [ + "prisoners-dilemma-and-cooperation", + "scenario-planning", + "coalition-and-partnership-games" + ] + routes_to_templates: [ "risk-assessment-brief", "partnership-memo" ] + sector_red_flags: + - "Banking partner's OCC or FDIC examination results in MRA (Matter + Requiring Attention) or MRIA (Matter Requiring Immediate Attention) + related to fintech oversight." + - "Banking partner communicating through legal counsel rather than + business contacts — indicates the relationship is being managed as a + risk rather than a partnership." + - "Multiple fintechs simultaneously receiving restrictive communications + from the same banking partner — indicates a systemic regulatory response + affecting the partner's entire fintech program." + + # ───────────────────────────────────────────── + # 13. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Leadership crises in fintech carry regulatory + consequences. The departure of a BSA officer, CCO, or any individual with + regulatory obligations triggers reporting requirements and regulatory + scrutiny. A leadership crisis during a regulatory examination compounds + the stress. Leaders who hold personal regulatory designations cannot be + replaced as casually as other roles — regulators must approve certain + leadership changes." + additional_triage_questions: + - question: "Does the leadership crisis involve individuals who hold regulatory + designations (BSA officer, CCO, CISO, designated compliance personnel) + whose departure triggers regulatory notification requirements?" + purpose: "Regulatory-designated leadership changes require notification to + regulators and may trigger enhanced supervision. These are not + ordinary personnel changes." + routing_impact: "Regulatory-designated leader departure routes to immediate + regulatory notification planning and interim designation of qualified + personnel. Non-regulatory leadership routes to standard succession + planning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory-designated leader departure creating compliance vacuum" + reason: "The loss of a BSA officer, CCO, or other regulatory-designated + individual creates immediate compliance risk and requires regulatory + notification." + less_likely: + - diagnosis: "General leadership style mismatch" + reason: "Leadership crises in fintech are more often about regulatory stress, + compliance disagreements, or personal liability concerns than about + leadership style." + fintech_specific_diagnoses: [] + sector_red_flags: + - "BSA officer or CCO departure without a pre-identified successor — + creates a compliance gap that regulators view as a critical deficiency." + - "Multiple compliance-designated personnel departing within a short + period — signals systemic cultural or risk issues." + + # ───────────────────────────────────────────── + # 14. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Operational chaos in fintech carries regulatory + consequences that do not exist in other industries. Missed regulatory + reporting deadlines, SAR filing backlogs, KYC refresh failures, and + transaction monitoring outages are not just operational problems — they + are compliance violations that can trigger enforcement actions. The + operational chaos diagnostic must prioritize regulatory-deadline + operations over discretionary operations." + additional_triage_questions: + - question: "Are any regulatory-deadline operations (SAR filing, CTR filing, state + regulatory reporting, audit submissions) currently behind schedule or + at risk of missing deadlines?" + purpose: "Regulatory deadlines are non-negotiable. A SAR must be filed within 30 + days of detection. CTRs must be filed within 15 days. Missing these + deadlines is a compliance violation, not an operational + inconvenience." + routing_impact: "Regulatory deadline risk routes to immediate triage and + resource reallocation to compliance operations. No deadline risk + routes to standard operational improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Compliance operations drowning growth operations" + reason: "Rapid growth in fintech generates proportional growth in compliance + workload (more transactions to monitor, more SARs to file, more KYC + to process). When compliance operations cannot scale with growth, + both compliance and growth suffer." + less_likely: + - diagnosis: "Technology infrastructure failure" + reason: "Pure technology failures are usually addressable. Operational chaos in + fintech more often stems from the collision of fast-growing + transaction volumes and linear-scaling compliance processes." + fintech_specific_diagnoses: + - name: "Compliance operations overwhelm" + description: "Transaction volume growth has outpaced the compliance team's + capacity to process AML alerts, file SARs, complete KYC reviews, and + generate regulatory reports. The compliance backlog creates regulatory + risk that threatens the business." + symptoms: + - "SAR filing backlog exceeding 30 days from alert disposition" + - "AML alert queue growing faster than the team can review" + - "KYC refresh reviews past due for more than 10% of customer base" + - "Regulatory reporting submitted late or with known errors" + routes_to_skills: [ "kaizen-bpr", "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] + sector_red_flags: + - "SAR filing deadline missed — this is a BSA violation that must be + remediated immediately and may require self-reporting to FinCEN." + - "Transaction monitoring system outage lasting more than 24 hours — + creates a compliance gap that regulators will examine." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Decision paralysis in fintech is amplified by the + irreversibility of regulatory decisions and the personal liability that + attaches to financial services decisions. Leaders who face personal legal + exposure for compliance failures may become paralyzed by risk aversion. + The diagnosis must distinguish between healthy caution (warranted by + regulatory risk) and excessive paralysis (preventing necessary business + decisions)." + additional_triage_questions: + - question: "Is the paralysis driven by uncertainty about regulatory requirements + — specifically, the team cannot decide because they do not know what + the rules are?" + purpose: "Regulatory ambiguity is a common source of fintech decision paralysis. + When the rules are unclear, conservative leaders wait for clarity + while aggressive leaders proceed at risk. Neither is optimal without + explicit risk framework." + routing_impact: "Regulatory uncertainty routes to regulatory engagement strategy + (proactive outreach to regulators, no-action letter requests, sandbox + applications). Non-regulatory paralysis routes to standard decision + framework." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory uncertainty freezing strategic decisions" + reason: "Fintech operates in a regulatory environment that changes frequently. + Pending regulations, ambiguous guidance, and enforcement pattern + shifts create uncertainty that paralyzes strategic planning." + less_likely: + - diagnosis: "Insufficient data for decision" + reason: "Fintech companies typically have abundant data (transaction data, + customer behavior, financial metrics). Paralysis is rarely about + missing data — it is about regulatory uncertainty or risk aversion." + fintech_specific_diagnoses: [] + sector_red_flags: + - "Major strategic decisions delayed more than 6 months citing 'regulatory + uncertainty' — may indicate leadership using regulation as an excuse for + inaction." + - "No new products launched in 12+ months because compliance review is + perpetually incomplete." + + # ───────────────────────────────────────────── + # 16. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Fintech hiring must address a talent pool that spans two + traditionally separate industries — technology and financial + services/compliance. The compliance talent market is constrained: + experienced BSA officers, CCOs, and regulatory counsel are scarce and + expensive. Hiring the wrong compliance leadership has regulatory + consequences — regulators evaluate the qualifications of designated + compliance personnel." + additional_triage_questions: + - question: "Are you struggling to hire for compliance, risk, and regulatory roles + specifically — BSA officer, CCO, CISO, regulatory counsel?" + purpose: "Compliance talent scarcity is the most common and most consequential + hiring challenge in fintech. The talent pool is small, compensation + expectations are high, and regulators evaluate the qualifications of + designated personnel." + routing_impact: "Compliance hiring difficulty routes to compensation + benchmarking against banking (not tech) standards and recruitment + strategy for regulated industry talent." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Compliance talent scarcity constraining growth" + reason: "Experienced BSA officers, CCOs, and financial services regulatory + counsel are in high demand across both traditional banking and + fintech. Competition for this talent is intense." + less_likely: + - diagnosis: "Employer brand weakness" + reason: "Fintech companies generally attract strong talent from both tech and + financial services. Hiring challenges are more often about specific + skill sets (compliance, regulatory) than general attractiveness." + fintech_specific_diagnoses: [] + sector_red_flags: + - "BSA officer or CCO position vacant for more than 30 days — regulators + view this as a critical gap." + - "Compliance staff being hired at below-market compensation (banking + market, not tech market) — creates retention risk in the + highest-consequence function." + + # ───────────────────────────────────────────── + # 17. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Innovation in fintech is constrained by compliance review + processes that can slow product development. The diagnostic must + distinguish between genuine innovation drought (no creative ideas) and + compliance-bottlenecked innovation (ideas exist but cannot clear + regulatory review). The former requires creativity; the latter requires + process improvement." + additional_triage_questions: + - question: "Is the innovation drought caused by a lack of ideas, or by a + compliance review process that prevents ideas from reaching market?" + purpose: "Many fintech companies have innovative ideas that die in compliance + review — not because they are non-compliant, but because the review + process is slow, under-resourced, or excessively conservative." + routing_impact: "Compliance bottleneck routes to compliance process redesign and + 'compliance-in-the-room' product development practice. Genuine idea + drought routes to standard innovation frameworks." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Compliance review bottleneck suppressing innovation velocity" + reason: "The most common innovation barrier in fintech is not a lack of + creativity but a slow, under-resourced, or overly conservative + compliance review process that prevents ideas from reaching market." + less_likely: + - diagnosis: "Organizational complacency" + reason: "Fintech companies rarely suffer from complacency — the pace of + regulatory and competitive change prevents it. Innovation drought is + more often structural (compliance bottleneck) than cultural." + fintech_specific_diagnoses: [] + sector_red_flags: + - "Average time from product concept to compliance approval exceeding 6 + months — indicates compliance is a bottleneck, not a partner." + - "Compliance team rejecting ideas without suggesting compliant + alternatives — indicates a 'Department of No' culture." + + # ───────────────────────────────────────────── + # 18. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Culture erosion in fintech manifests as a divergence + between stated values (customer-first, transparency, financial inclusion) + and actual behavior (hidden fees, aggressive collections, predatory + lending terms). This is not just a culture problem — it is a regulatory + risk. UDAP/UDAAP enforcement targets practices that are unfair, deceptive, + or abusive, which are often the downstream manifestation of culture + erosion." + additional_triage_questions: + - question: "Are there practices in the company that leadership would not be + comfortable disclosing to a regulator during an examination?" + purpose: "This question cuts directly to culture-compliance alignment. If the + answer is yes, the company has a culture problem that is also a + regulatory risk." + routing_impact: "Affirmative answer routes to immediate compliance assessment + and ethical review. Negative answer routes to standard culture + diagnosis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Revenue pressure eroding ethical standards" + reason: "Fintech companies under growth pressure may adopt practices that + extract revenue from customers at the expense of transparency — + hidden fees, aggressive upselling, misleading marketing. These are + simultaneously culture failures and regulatory violations." + less_likely: + - diagnosis: "Remote work eroding culture" + reason: "Remote work culture challenges exist in fintech but are not the primary + culture erosion driver. Revenue pressure and growth-compliance + tension are more consequential." + fintech_specific_diagnoses: + - name: "Financial inclusion rhetoric vs. predatory practice" + description: "The company publicly positions itself as promoting financial + inclusion but its actual product terms, fee structures, or lending + practices disproportionately burden the underbanked populations it + claims to serve. The gap between narrative and reality creates both + ethical liability and regulatory risk under UDAP/UDAAP and fair + lending laws." + symptoms: + - "APRs or effective fee rates exceeding 36% for products marketed to + underbanked consumers" + - "Internal metrics tracking revenue extraction per customer rather + than financial wellbeing outcomes" + - "Marketing emphasizes 'financial inclusion' while product design + maximizes fee revenue from financially vulnerable customers" + - "Fair lending analysis identifies disparate impact across protected + demographic groups" + routes_to_skills: + [ + "trust-equation", + "tough-decision-situations", + "defining-and-exploring-problems" + ] + routes_to_templates: [ "risk-assessment-brief", "culture-values-document" ] + sector_red_flags: + - "Customer complaint rate to CFPB or state regulators increasing — + regulatory complaints are both a culture signal and a regulatory risk + indicator." + - "Internal compliance concerns being documented in writing and escalated + through formal channels — indicates the compliance team believes + informal escalation is insufficient, a serious warning sign." + + # ───────────────────────────────────────────── + # 19. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Communication breakdowns in fintech carry regulatory + weight because certain communications are legally required. Adverse action + notices for credit denials, fee disclosures, privacy notices under GLBA, + and breach notification under state laws have specific content, timing, + and delivery requirements. Internal communication breakdowns between the + compliance team and other functions can lead to regulatory violations." + additional_triage_questions: + - question: "Is the communication breakdown affecting customer-facing regulatory + disclosures (fee disclosures, adverse action notices, privacy notices) + or internal compliance escalation channels?" + purpose: "Customer-facing disclosure failures are regulatory violations. + Internal escalation failures lead to regulatory issues going + unaddressed until they become enforcement actions." + routing_impact: "Customer disclosure failures route to immediate compliance + remediation and disclosure process redesign. Internal escalation + failures route to compliance governance and reporting line + restructuring." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Compliance-operations communication gap" + reason: "The most consequential communication breakdown in fintech occurs + between the compliance function and operational teams. When + compliance concerns do not reach the right decision-makers, + regulatory violations result." + less_likely: + - diagnosis: "Meeting culture problems" + reason: "Meeting format issues exist but are not the primary communication + concern in fintech. The critical communication challenge is ensuring + regulatory information flows to decision-makers." + fintech_specific_diagnoses: [] + sector_red_flags: + - "Compliance team unable to reach C-suite leadership with urgent + regulatory concerns — creates personal liability risk for compliance + personnel who have legal obligations to escalate." + - "Customer-facing communications going live without compliance review — + any customer-facing communication about a financial product should be + reviewed for regulatory compliance." + + # ───────────────────────────────────────────── + # 20. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Stuck negotiations in fintech most commonly involve + banking partner terms, regulatory consent orders, and enterprise client + compliance requirements. These negotiations are fundamentally different + from commercial negotiations because they involve regulatory constraints + that limit the negotiation space — neither party can agree to terms that + violate regulatory requirements." + additional_triage_questions: + - question: "Is the negotiation stuck because of a regulatory constraint that + limits what either party can agree to — e.g., the banking partner + cannot agree to terms that violate third-party risk management + guidance?" + purpose: "Regulatory constraints narrow the zone of possible agreement in + fintech negotiations. Understanding which constraints are binding + helps identify whether the negotiation is stuck because of interests + or because of regulations." + routing_impact: "Regulatory-constrained negotiation routes to + regulatory-informed alternative generation — finding terms that + satisfy both commercial interests and regulatory requirements. + Interest-based stall routes to standard negotiation frameworks." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory constraint as hidden negotiation barrier" + reason: "In fintech, negotiations often stall because one party cannot explain + that a regulatory requirement prevents agreement. Banking partners, + in particular, may resist terms without disclosing the specific + regulatory guidance driving their position." + less_likely: + - diagnosis: "Personality-driven stalemate" + reason: "Fintech negotiations are typically between sophisticated parties who + understand the regulatory landscape. Stalemates are more often + structural (regulatory constraints) than personal." + fintech_specific_diagnoses: [] + sector_red_flags: + - "Banking partner negotiation stalled for more than 90 days — may + indicate the partner is conducting an internal regulatory review of the + entire fintech program." + - "Regulatory settlement negotiation — requires specialized counsel and + should not be handled by the general business team." diff --git a/plugins/foreman/content/industry-packs/fintech/fintech-skill-overlays.yaml b/plugins/foreman/content/industry-packs/fintech/fintech-skill-overlays.yaml new file mode 100644 index 0000000..fa8fc20 --- /dev/null +++ b/plugins/foreman/content/industry-packs/fintech/fintech-skill-overlays.yaml @@ -0,0 +1,1482 @@ +# Fintech Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides fintech-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add a fintech lens. +# +# REGULATORY PRINCIPLE: Every overlay addresses how regulation changes the +# framework's application. Fintech is uniquely constrained by regulation — +# compliance is not optional, trust is existential, and the cost of failure +# includes legal liability, license revocation, and criminal penalties. +# PSD2, SOX, GDPR, PCI-DSS, BSA/AML, UDAP/UDAAP, state licensing, and +# sector-specific regulations (TILA, ECOA, FCRA, GLBA) shape every strategic +# decision. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct fintech application (strategy, pricing, risk, trust) +# - Game theory skills (regulatory game, competitive dynamics, cooperation) +# - Decision and thinking skills (risk-weighted decision-making in regulated environments) +# - Negotiation skills (banking partnerships, regulatory relationships, enterprise deals) +# - Leadership skills most affected by compliance culture and trust dynamics +# - AI/data skills (algorithmic fairness, model risk, explainability requirements) +# +# Relevance tiers: +# critical — The fintech overlay materially changes how the skill is applied. +# The skill executor should always surface fintech context. +# high — Fintech context adds significant value. Surface when relevant. +# moderate — Useful fintech framing but the base skill works well as-is. + +pack_metadata: + sector: "fintech" + display_name: "Fintech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (18 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Regulation rewrites Porter's Five Forces in fintech. Barriers + to entry are overwhelmingly regulatory — licensing requirements (state + money transmitter licenses, bank charters, SEC/FINRA registration), + capital requirements (Basel III, state net worth minimums), and compliance + infrastructure create moats that cost $1M-$50M+ to cross. Threat of new + entrants must include both startups AND big tech (Apple Pay, Google + Wallet, Amazon Lending) who can amortize compliance costs across massive + user bases. Buyer power is amplified by regulatory mandates — PSD2 Open + Banking in Europe and Section 1033 in the US force data portability, + structurally increasing buyer switching power. Supplier power concentrates + in banking-as-a-service providers (Synapse, Column, Cross River) and card + network duopoly (Visa/Mastercard)." + fintech_anti_patterns: + - "Assuming regulatory barriers protect you permanently. Regulatory + frameworks evolve — PSD2 demolished barriers in European payments; + Section 1033 will do the same in the US. Incumbents who rely on + licensing moats without building product moats face disruption when + regulations change." + - "Ignoring the big tech threat vector. Apple, Google, and Amazon can + enter any fintech vertical with enormous distribution advantages, + pre-existing customer trust, and the ability to operate regulated + services as loss leaders within their ecosystem." + - "Treating the card networks (Visa, Mastercard) as neutral + infrastructure. They are powerful suppliers who set interchange rates, + impose compliance requirements, and can revoke processing privileges. + Their expansion into fintech infrastructure (Visa Direct, Mastercard + Send) makes them potential competitors." + fintech_example: "A payments fintech applies Porter's Five Forces and discovers + that its apparent competitive moat — money transmitter licenses in 48 + states — is actually shared with 15 competitors. The real competitive + force is supplier power: their single banking partner (BaaS provider) + processes all transactions, and a regulatory enforcement action against + that partner would halt their business overnight. This analysis shifts + strategy from product differentiation to banking partner diversification + and eventually a direct bank charter application." + benchmark_references: [ "take-rate", "regulatory-compliance-cost", "tpv" ] + + - skill: "blue-ocean-strategy" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Blue ocean creation in fintech is uniquely constrained — you + cannot create an uncontested market space by ignoring regulations. The + most successful fintech blue oceans are created by serving populations + that incumbent banks find unprofitable to serve (Nubank in Brazil, M-Pesa + in Kenya), by making compliance itself a product (Alloy, Chainalysis), or + by embedding financial services where they were previously absent (Shopify + Capital, Toast payments). The strategy canvas must include a regulatory + axis — the compliance burden of existing solutions versus the compliance + innovation of the new offering." + fintech_anti_patterns: + - "Pursuing a blue ocean that exists because it is illegal. Many apparent + market gaps in financial services exist because regulatory constraints + prohibit the activity. 'Move fast and break things' in fintech means + fines, enforcement actions, and prison." + - "Ignoring that regulatory arbitrage creates temporary blue oceans. + Operating without a required license is not a strategy — it is a ticking + clock. The regulatory gap will close, and enforcement will follow." + - "Assuming financial inclusion is automatically a blue ocean. Serving + underbanked populations requires understanding why banks exited those + markets — credit risk, fraud risk, and compliance costs are real, not + arbitrary barriers." + fintech_example: "Nubank created a blue ocean in Brazilian financial services by + eliminating what incumbents considered essential — branches, relationship + managers, paper statements, and complex fee schedules. The strategy canvas + revealed that Brazilian banks over-served high-net-worth customers with + premium services while punishing mass-market customers with opaque fees. + Nubank's blue ocean was 'transparent, digital-only, zero-fee banking for + the mass market' — a space incumbents could not enter without + cannibalizing their fee-dependent business models. Critically, Nubank + obtained a full banking license, ensuring the blue ocean was + regulatory-compliant." + benchmark_references: [ "cac", "monthly-active-users", "cost-to-income-ratio" ] + + - skill: "business-model-canvas" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "The Business Model Canvas for fintech requires a regulatory + layer across nearly every block. Key Partners must include banking + partners, card networks, identity verification providers, and regulators + themselves — the regulatory relationship is a partnership that enables the + business. Key Activities must include compliance operations (KYC, AML, + transaction monitoring, regulatory reporting) as a core activity, not an + overhead function. Revenue Streams must distinguish between regulated + revenue (interchange, interest income, advisory fees subject to regulatory + caps) and unregulated revenue (SaaS fees, data products). Cost Structure + must separate compliance costs because they are non-discretionary — you + cannot cut compliance spending to extend runway." + fintech_anti_patterns: + - "Omitting the regulatory infrastructure from Key Resources. Licenses, + compliance systems, banking relationships, and regulatory goodwill are + among the most valuable and hardest-to-replicate resources in fintech." + - "Treating compliance as a Cost Structure line item rather than a Key + Activity. In fintech, compliance is not overhead — it is the activity + that enables every other activity on the canvas." + - "Designing the Customer Relationship block without considering + regulatory constraints on customer communication. Financial services + advertising, account disclosures, and marketing are regulated by + UDAP/UDAAP, TILA, Reg Z, and state-specific rules." + fintech_example: "A BNPL fintech maps its Business Model Canvas and discovers + that its Key Partners block reveals existential concentration risk: one + BaaS provider, one card network processor, and one identity verification + vendor. A failure at any partner halts the business. The Key Activities + analysis reveals that 40% of engineering time is spent on + compliance-related features (regulatory reporting, transaction monitoring + alerts, customer disclosure requirements) — far more than anticipated. + This canvas analysis triggers a strategic shift: diversify banking + partners, build redundant identity verification, and restructure + engineering to treat compliance features as first-class product features + rather than afterthoughts." + benchmark_references: + [ + "regulatory-compliance-cost", + "gross-margin", + "cac", + "kyc-cost-per-customer" + ] + + - skill: "four-ps-marketing" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "The Four Ps require regulatory awareness at every level in + fintech. Product is subject to regulatory approval — new financial + products may require regulatory filing, disclosure documents, or license + amendments. Price in fintech faces regulatory caps: interchange caps under + Durbin Amendment and PSD2 IFR, interest rate caps under state usury laws, + fee restrictions under UDAP/UDAAP. Place (distribution) is constrained by + licensing — you can only distribute financial products in jurisdictions + where you hold appropriate licenses. Promotion is heavily regulated by + UDAP/UDAAP, TILA advertising requirements, SEC advertising rules for + investment products, and state-specific marketing restrictions. A + marketing claim that would be merely aggressive in SaaS could be a + regulatory violation in fintech." + fintech_anti_patterns: + - "Setting prices without understanding regulatory caps. Durbin Amendment + caps debit interchange for large issuers. State usury laws cap interest + rates. UDAP/UDAAP prohibits unfair fees. Price is not a free variable in + fintech." + - "Running 'growth hack' marketing without regulatory review. APR + disclosures, fee transparency, and truthful advertising are legal + requirements, not suggestions. Misleading financial advertising triggers + CFPB enforcement." + - "Distributing financial products across state lines without appropriate + licensing. Each state has its own licensing requirements for lending, + money transmission, and insurance. Unlicensed activity is a criminal + offense in many jurisdictions." + fintech_example: "A neobank applies the Four Ps and discovers that its planned + 'no-fee overdraft' marketing campaign violates UDAP/UDAAP because the + overdraft product has conditions that effectively charge customers through + a different mechanism. The Promotion analysis reveals that 30% of planned + marketing messages require regulatory rewording. The Place analysis + identifies 12 states where the company lacks lending licenses, + constraining geographic expansion. The Four Ps exercise transforms from a + marketing planning tool into a regulatory compliance mapping exercise — + the correct application for financial services." + benchmark_references: [ "cac", "arpu", "kyc-conversion-rate" ] + + - skill: "net-promoter-score" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "NPS in fintech carries existential weight because financial + services are trust-dependent. A security breach, a wrongful account + freeze, or a compliance-driven account closure can transform a promoter + into a vocal detractor who warns others away from the platform — and in + fintech, those warnings spread faster and hit harder than in other + industries because money is involved. NPS surveys in fintech must be + triggered by financial milestones (first direct deposit, first loan + approval, first claim resolution), not arbitrary time intervals. The + qualitative feedback is especially valuable for identifying compliance + friction points — KYC frustrations, false-positive fraud blocks, and + unexplained transaction declines that damage trust." + fintech_anti_patterns: + - "Surveying NPS after account opening but not after the first regulatory + friction event (KYC delay, fraud block, transaction decline). The true + NPS is measured after the customer has experienced the compliance-driven + friction that defines fintech UX." + - "Ignoring the detractor signal from account closures. In fintech, forced + account closures (due to compliance triggers, risk reviews, or fraud + suspicion) generate extreme detractors who can cause reputational damage + disproportionate to their numbers." + - "Optimizing NPS by reducing compliance friction in ways that create + regulatory risk. The goal is to minimize unnecessary friction while + maintaining full compliance — not to eliminate compliance steps that + customers find annoying." + fintech_example: "A neobank segments NPS by customer journey stage and discovers + that NPS is 72 after account opening but drops to 18 after the first + account freeze triggered by their automated fraud detection system. + Investigation reveals that 85% of fraud-flagged accounts are false + positives, and the resolution process requires 48 hours — during which + customers cannot access their money. The NPS data drives a product + investment in real-time fraud review and instant account unfreezing for + confirmed false positives, restoring NPS to 55 after fraud events while + maintaining BSA/AML compliance." + benchmark_references: [ "kyc-conversion-rate", "monthly-active-users", "net-revenue-retention" ] + + - skill: "product-life-cycle" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "Product lifecycle in fintech is uniquely shaped by regulatory + evolution. Introduction phase includes regulatory approval — a lending + product cannot launch until state licenses are obtained, disclosures are + approved, and compliance infrastructure is operational. Growth phase may + be accelerated or constrained by regulatory decisions: PSD2 opened + European payments markets; conversely, crypto regulation in 2022-2024 + constrained growth for entire sub-sectors. Maturity arrives when the + regulatory framework stabilizes and compliance becomes a commodity rather + than a differentiator. Decline can be triggered by regulatory change — a + new regulation can obsolete an entire business model overnight (as + happened with payday lending regulations in multiple states)." + fintech_anti_patterns: + - "Assuming product lifecycle is determined solely by market dynamics. In + fintech, a regulation can move a product from Growth to Decline in a + single legislative session. Monitor regulatory pipelines as closely as + competitive dynamics." + - "Investing in Growth-phase tactics for a product whose regulatory + environment is entering Maturity. When compliance becomes commoditized + (as happened with basic KYC), the competitive advantage shifts from 'we + are compliant' to 'we are compliant AND differentiated.'" + - "Sunsetting a product without understanding regulatory obligations for + data retention, customer notification, and account closure. Financial + product wind-down has regulatory requirements that non-financial + products do not." + fintech_example: "BNPL products followed a textbook product lifecycle compressed + by regulatory intervention. Introduction (2018-2020): novel product, light + regulation, rapid adoption. Growth (2020-2022): mainstream adoption, + high-profile IPOs. Regulatory trigger (2022-2024): CFPB classifies BNPL as + credit subject to TILA, multiple states introduce BNPL-specific + regulation. The product is now transitioning from Growth to Maturity + faster than market dynamics alone would dictate — regulatory intervention + accelerated the lifecycle by 3-5 years." + benchmark_references: [ "monthly-active-users", "regulatory-compliance-cost", "gross-margin" ] + + - skill: "disruptive-innovation" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Disruptive innovation in fintech follows the classic pattern + with a regulatory twist: the incumbent is protected not just by product + complexity but by regulatory moats. Disruption occurs when a fintech finds + a regulatory pathway that incumbents overlooked or dismissed. Stripe + disrupted payment processing by acting as a payment facilitator (payfac) + rather than requiring each merchant to obtain its own merchant account — a + regulatory interpretation that incumbents had not exploited. Nubank + disrupted Brazilian banking by obtaining a digital banking license rather + than building branches. The disruption framework must account for + regulatory pathways as a strategic variable — the choice of charter, + license, or regulatory framework IS the innovation." + fintech_anti_patterns: + - "Trying to disrupt from outside the regulatory perimeter. Unlike tech + disruption where you can 'beg forgiveness,' operating without required + financial licenses is a federal crime. The regulatory pathway must be + established before or concurrent with the disruption." + - "Assuming incumbents are permanently constrained by legacy regulation. + Banks are actively lobbying for regulatory relief and building digital + subsidiaries. The window for regulatory-arbitrage disruption closes." + - "Confusing regulatory non-compliance with innovation. Uber's 'ignore + existing regulations' playbook does not transfer to financial services — + financial regulators have enforcement power that transportation + regulators lacked." + fintech_example: "Square disrupted the merchant acquiring industry by using the + payment facilitator (payfac) model, which allowed it to aggregate small + merchants under its own master merchant account rather than requiring each + business to undergo individual underwriting. The incumbent acquirers + dismissed this approach as impractical and risky. Square's innovation was + not primarily technological (the card reader was simple) but regulatory + and operational — it found a compliant pathway that incumbents had not + exploited, then built technology to manage the fraud and compliance risk + at scale." + benchmark_references: [ "tpv", "cac", "cost-per-transaction" ] + + - skill: "balanced-scorecard" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "The Balanced Scorecard in fintech requires a fifth perspective + beyond the traditional four: Regulatory Compliance. Financial Perspective: + net revenue, NIM, gross margin, cost-to-income ratio — but constrained by + regulatory capital requirements and fee caps. Customer Perspective: NPS, + MAU, transactions per user, KYC conversion rate — the regulatory friction + in customer experience is a measurable variable. Internal Process + Perspective: fraud detection accuracy, false positive rate, AML alert + disposition time, regulatory reporting accuracy. Learning & Growth + Perspective: compliance training completion, audit finding remediation + velocity, regulatory change management speed. Regulatory Perspective + (added): license status, examination findings, enforcement action risk, + regulatory capital surplus/deficit." + fintech_anti_patterns: + - "Tracking financial metrics without a regulatory compliance perspective. + A fintech with excellent growth metrics and deteriorating compliance + standing is heading toward an enforcement action that will erase the + financial performance." + - "Measuring Internal Process efficiency without including compliance + process metrics. AML alert disposition time, SAR filing timeliness, and + regulatory reporting accuracy are operational metrics with legal + consequences." + - "Ignoring the Learning & Growth investment in compliance talent. + Compliance officers, BSA officers, and legal counsel are not overhead — + they are the human infrastructure that enables the business." + fintech_example: "A lending fintech implements a balanced scorecard with five + perspectives: Financial (loan origination volume, NIM, default rate, gross + margin), Customer (application completion rate, NPS, repeat borrower + rate), Internal Process (underwriting decision time, SAR filing + timeliness, fair lending audit results), Learning & Growth (compliance + training completion rate, new regulation integration speed, audit finding + closure rate), Regulatory (state license renewal status, examination + finding severity, regulatory capital adequacy). The scorecard reveals that + accelerating origination volume (Financial) is creating SAR filing + backlogs (Internal Process) and triggering fair lending pattern concerns + (Regulatory) — the scorecard prevents a growth strategy from causing a + compliance crisis." + benchmark_references: + [ + "regulatory-compliance-cost", + "default-rate", + "kyc-conversion-rate", + "gross-margin", + "net-interest-margin" + ] + + - skill: "trust-equation" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Trust is EXISTENTIAL in fintech — one security breach, one + data leak, or one regulatory enforcement action can be fatal. The Trust + Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to + fintech as follows: Credibility = regulatory licenses, SOC 2 Type II + certification, PCI-DSS compliance, FDIC insurance, published security + practices. Reliability = 99.99% uptime, consistent transaction processing, + predictable fee schedules, accurate account balances. Intimacy = + understanding the customer's financial situation, personalized financial + guidance, empathetic handling of financial distress. Self-Orientation = + the denominator that destroys trust — hidden fees, opaque pricing, dark + patterns that prevent account closure, selling customer data to third + parties, and any behavior that prioritizes revenue extraction over + customer financial wellbeing. UDAP/UDAAP enforcement is essentially a + legal codification of the Self-Orientation problem." + fintech_anti_patterns: + - "Building credibility through marketing while neglecting reliability. A + fintech that advertises '100% secure' but has never undergone a + penetration test is building trust on a foundation that will collapse + catastrophically." + - "Using dark patterns to increase retention. Hiding account closure + options, requiring phone calls to cancel, or imposing unexpected fees + are high-Self-Orientation behaviors that regulators are increasingly + targeting through UDAP/UDAAP enforcement." + - "Treating data privacy as a legal checkbox rather than a trust signal. + GDPR, CCPA, and GLBA compliance are regulatory minimums — customers + expect their financial data to be treated with extraordinary care. Any + data breach is a trust-extinction event." + fintech_example: "Chime built trust through radical simplification of the + Self-Orientation denominator: no overdraft fees, no minimum balance fees, + no monthly fees, and early direct deposit access. Each of these reduced + perceived Self-Orientation (the company is not trying to extract fees) + while increasing Credibility (FDIC-insured through partner banks) and + Reliability (consistent experience). The trust equation explains Chime's + growth to 15M+ accounts — in a market where consumers distrust banks, + eliminating the behaviors that generate distrust is the most powerful + growth lever." + benchmark_references: [ "monthly-active-users", "net-revenue-retention", "fraud-rate" ] + + - skill: "swot-pest-analysis" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "PEST analysis in fintech is dominated by the Political and + Legal dimensions to an extent not seen in other industries. Political: + regulatory regime changes (new administration = new enforcement + priorities), international regulatory coordination (Basel standards, FATF + recommendations), state-level regulatory fragmentation (50 different money + transmitter license requirements). Economic: interest rate environment + (directly impacts lending NIM and deposit competition), credit cycle + position (determines default rates), funding market conditions (warehouse + line availability, securitization market health). Social: financial + inclusion expectations, consumer privacy concerns, trust in digital-only + institutions, generational banking preferences. Technological: real-time + payments infrastructure (FedNow, RTP), open banking APIs (Plaid, MX), + blockchain/DLT applications, AI in credit underwriting (model risk + management requirements)." + fintech_anti_patterns: + - "Under-weighting the Political dimension. A change in CFPB leadership + can shift enforcement priorities overnight. A new state attorney general + can launch investigations into practices previously tolerated. + Regulatory risk is the dominant PEST factor in fintech." + - "Treating SWOT Strengths as permanent. A regulatory license is a + strength today but can be revoked tomorrow. A banking partnership is a + strength until the partner bank faces its own regulatory issues. Fintech + strengths are more fragile than they appear." + - "Conducting PEST analysis without monitoring regulatory pipelines. + Proposed regulations (CFPB rulemaking, state legislative sessions, Basel + Committee consultations) signal future changes that should be + incorporated into the analysis." + fintech_example: "A crypto exchange conducts PEST analysis in early 2024 and + identifies that the Political dimension is about to shift dramatically: + the EU's MiCA regulation takes effect, creating a comprehensive regulatory + framework that will require significant compliance investment but also + legitimize the industry. The Economic dimension shows institutional + interest increasing. The SWOT reveals that the company's lack of EU entity + is a critical Weakness that must be addressed before MiCA enforcement, + while its strong compliance infrastructure (built for US regulations) is a + Strength that transfers to the EU framework. The analysis drives a + six-month plan to establish an EU entity and obtain MiCA authorization + before competitors." + benchmark_references: [ "regulatory-compliance-cost", "gross-margin", "monthly-active-users" ] + + - skill: "scenario-planning" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Scenario planning in fintech must include regulatory scenarios + as a primary dimension — not an afterthought. The three critical scenario + dimensions are: regulatory environment (favorable vs. restrictive vs. + transformative), credit/economic cycle (expansion vs. contraction vs. + crisis), and competitive dynamics (stable vs. big-tech entry vs. + regulatory-enabled new competition). Regulatory scenarios have outsized + impact: an unfavorable CFPB ruling can eliminate an entire revenue line; a + favorable charter decision can unlock deposit funding that transforms unit + economics; an open banking mandate can demolish switching-cost moats + overnight. Every fintech should maintain scenarios for: (1) a major + regulatory change affecting their core product, (2) a banking partner + failure or exit, (3) a credit cycle downturn that doubles default rates." + fintech_anti_patterns: + - "Building only financial scenarios without regulatory scenarios. A + fintech that models three growth rates but does not model the impact of + a regulatory enforcement action is scenario planning incorrectly." + - "Treating the banking partner relationship as a constant across + scenarios. Banking partners can exit fintech relationships, face their + own regulatory actions, or change terms. Scenario planning must include + partner risk." + - "Ignoring credit cycle scenarios in lending. Every lending fintech must + model performance through a recession — default rates that are 2-3x + baseline levels. If the business model does not survive a downturn, it + is not sustainable." + fintech_example: "A BNPL company builds four scenarios: (1) Base: current growth + trajectory, CFPB regulation increases compliance costs by 20% but does not + require fundamental model changes. (2) Regulatory upside: BNPL receives a + favorable regulatory classification that legitimizes the product and + drives mainstream adoption. (3) Regulatory downside: BNPL classified as + credit under TILA, requiring full credit reporting, adverse action + notices, and ability-to-repay assessments — fundamentally changing the + cost structure. (4) Credit downturn: recession doubles default rates while + transaction volume declines 30%. Each scenario has pre-committed strategic + responses and trigger indicators." + benchmark_references: [ "default-rate", "regulatory-compliance-cost", "gross-margin" ] + + - category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Pricing in fintech is constrained by regulation in ways that + no other industry experiences. Interchange is capped by Durbin Amendment + (debit) and PSD2 IFR (EU credit/debit). Interest rates face state usury + law ceilings and federal Military Lending Act caps. Fees must comply with + UDAP/UDAAP — fees that are 'unfair, deceptive, or abusive' are illegal + regardless of their commercial rationale. Pricing diagnosis must begin + with a regulatory ceiling analysis: what are the maximum permissible + prices for each revenue line? Then assess competitive positioning within + those regulatory constraints. The diagnosis should also evaluate + cross-subsidy strategies — free checking funded by interchange, + zero-interest BNPL funded by merchant fees — and assess their regulatory + sustainability." + fintech_anti_patterns: + - "Setting prices based on willingness-to-pay without checking regulatory + caps. A lending product priced at market-clearing rates may violate + usury laws in specific states." + - "Assuming current regulatory pricing constraints are permanent. + Interchange caps can tighten (as PSD2 demonstrated in Europe). Interest + rate caps can change. Fee prohibitions can expand. Price within current + regulations but plan for tighter constraints." + - "Hiding fees that regulators consider material. CFPB 'junk fee' + enforcement is targeting practices like surprise overdraft fees, late + payment penalties, and account maintenance fees that are not prominently + disclosed. Opacity is a regulatory risk, not a pricing strategy." + fintech_example: "A payments company conducts pricing diagnosis and discovers + that 60% of its revenue comes from interchange on debit transactions — + revenue that is capped by the Durbin Amendment and could be further + compressed by proposed legislation. The diagnosis reveals that the + company's premium services (fraud analytics, financial reporting, lending + integration) are under-priced relative to the value delivered because they + were originally bundled 'free' with payment processing. The prescription: + unbundle value-add services into separately priced products that are not + subject to interchange regulation, shifting the revenue mix from regulated + (interchange) to unregulated (SaaS-like fees) over 18 months." + benchmark_references: [ "take-rate", "arpu", "gross-margin", "regulatory-compliance-cost" ] + kind: diagnostic + ref: pricing-diagnosis + + - skill: "systems-thinking" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "Fintech businesses are complex adaptive systems with + regulatory feedback loops that create non-obvious outcomes. The most + important loops: (1) The compliance investment loop: investing in + compliance enables licenses, which enable products, which generate + revenue, which funds more compliance — or underinvesting triggers + enforcement, which restricts products, which reduces revenue, which + further reduces compliance investment. (2) The trust-growth loop: trust + enables customer acquisition, usage generates data, data improves products + and risk models, improved products deepen trust. (3) The credit spiral: + loan origination generates interest income, income funds new origination, + but loosening underwriting to grow origination increases defaults, which + consume the interest income, requiring tighter underwriting, which reduces + origination. (4) The banking partner dependency loop: growth requires a + banking partner, partner enables growth, growth increases partner's + regulatory exposure, partner imposes restrictions, restrictions constrain + growth." + fintech_anti_patterns: + - "Treating compliance as a one-time cost rather than a feedback loop. + Under-investment in compliance creates a negative spiral: enforcement + action, operational restrictions, customer loss, revenue decline, + further compliance under-investment." + - "Ignoring the time delays in credit risk feedback loops. Loose + underwriting today generates revenue today but creates losses 6-18 + months later. The delay makes the causal connection invisible to + decision-makers focused on quarterly metrics." + - "Optimizing one metric without modeling regulatory second-order effects. + Growing transaction volume rapidly may trigger enhanced BSA/AML + monitoring requirements that overwhelm the compliance team, leading to + suspicious activity reporting failures." + fintech_example: "A neobank discovers through systems analysis that its rapid + customer growth is creating a negative feedback loop: more customers + generate more transaction monitoring alerts, the compliance team cannot + process alerts fast enough, alert backlogs trigger regulatory scrutiny, + regulators impose growth restrictions until the backlog is cleared, + restrictions slow customer acquisition. The system solution is not to hire + more compliance analysts (linear scaling) but to invest in automated alert + triage (exponential scaling) — a systems-level intervention that breaks + the constraint on growth." + benchmark_references: [ "regulatory-compliance-cost", "monthly-active-users", "fraud-rate" ] + + - skill: "cialdini-influence" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "Cialdini's influence principles apply powerfully to fintech — + but several operate under regulatory constraints. Scarcity is regulated: + creating artificial urgency around financial products ('limited-time rate, + apply now!') is scrutinized under UDAP/UDAAP if the scarcity is + manufactured. Social Proof must be truthful: testimonials and performance + claims for investment products are regulated by SEC and FINRA. Reciprocity + works differently: free financial products (free checking, free trades) + create obligation but must deliver genuine value — 'free' products that + generate hidden revenue (payment for order flow, data selling) face + regulatory backlash. Authority in fintech comes from regulatory + credentials: FDIC insurance, state licenses, SOC 2 certification, and + regulatory examination results carry more authority than celebrity + endorsements. Commitment & Consistency drives financial product adoption: + customers who set up direct deposit are dramatically more likely to use + the product long-term." + fintech_anti_patterns: + - "Using Scarcity tactics that violate financial advertising regulations. + 'Only 48 hours to lock in this rate' is permissible if true; 'limited + spots available' for a digital banking product with infinite capacity is + deceptive." + - "Deploying Social Proof that constitutes a financial guarantee. 'Join + 10M customers who trust us' is acceptable; 'our customers earn 12% + returns' without proper disclaimers violates SEC advertising rules." + - "Relying on Authority signals that customers do not understand. + Displaying a state banking license number is legally required but + provides no authority to consumers. FDIC insurance badges, on the other + hand, are immediately recognized and powerfully trust-building." + fintech_example: "Robinhood leveraged Commitment & Consistency (fractional + shares lowered the commitment threshold, making everyone an 'investor'), + Social Proof (referral waitlists created visible demand), and Authority + (SEC-registered, SIPC-insured) to acquire 22M+ accounts. However, the + company's use of gamification elements (confetti after trades) and the + opacity of payment for order flow revenue created Self-Orientation + concerns that eventually attracted FINRA fines and SEC scrutiny — + demonstrating that Cialdini's principles must be applied within regulatory + boundaries." + benchmark_references: [ "cac", "monthly-active-users", "kyc-conversion-rate" ] + + - skill: "growth-share-matrix" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "The BCG Growth-Share Matrix in fintech must account for + regulatory capital allocation alongside financial capital. Stars (high + growth, high share) may require disproportionate regulatory capital — a + fast-growing lending product consumes capital reserves. Cash Cows (low + growth, high share) in fintech are often legacy products with stable + regulatory relationships and proven compliance — they fund the compliance + build-out for new products. Question Marks must include the regulatory + licensing timeline — a promising new product that requires a 2-year + license acquisition is a very different Question Mark than one that + operates under existing licenses. Dogs in fintech cannot always be killed + — regulatory obligations may require maintaining products or services for + existing customers even when they are uneconomic." + fintech_anti_patterns: + - "Allocating resources solely based on market attractiveness without + considering regulatory capital constraints. A Star product that requires + 50% of available regulatory capital limits the entire portfolio." + - "Sunsetting Dog products without accounting for regulatory wind-down + obligations. Customer notification requirements, data retention + mandates, and account migration timelines constrain how quickly + uneconomic products can be discontinued." + - "Ignoring the regulatory timeline for Question Marks. A product that + requires a new license, charter amendment, or regulatory approval + operates on regulatory time, not market time." + fintech_example: "A multi-product fintech maps its portfolio: Payments (Cash Cow + — mature, high share, stable regulatory relationship), Lending (Star — + growing rapidly but consuming capital reserves), Crypto custody (Question + Mark — high growth market but regulatory framework uncertain), and Check + cashing (Dog — declining, low margin, but regulatory obligations require + continued service for existing customers). The matrix reveals that the + Lending Star is consuming the capital that should fund the Crypto Question + Mark's regulatory preparation — triggering a capital planning discussion + with the board." + benchmark_references: [ "gross-margin", "loan-origination-volume", "regulatory-compliance-cost" ] + + - skill: "doblin-ten-types" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "The Ten Types of Innovation framework reveals that the most + successful fintech innovations occur outside the Product Performance + dimension. Profit Model innovation is central: subscription-based + financial services, zero-commission trading, BNPL — each is a Profit Model + innovation applied to financial services. Network innovation through open + banking APIs, banking-as-a-service, and embedded finance creates ecosystem + value. Process innovation through automated compliance, AI-driven + underwriting, and real-time payments transforms operational economics. + Channel innovation through embedded finance (Shopify Capital, Uber driver + lending) places financial services at the point of need. Customer + Engagement innovation through financial literacy tools, spend + categorization, and savings gamification builds emotional connection." + fintech_anti_patterns: + - "Innovating on Product Performance (features) while ignoring Profit + Model constraints. A more feature-rich lending product is useless if the + interest rate is capped by regulation and the cost to serve exceeds the + margin." + - "Neglecting Process innovation in compliance. The fintech with the most + efficient compliance process (lowest cost per SAR, fastest KYC, most + accurate transaction monitoring) has a structural cost advantage that + compounds at scale." + - "Ignoring Service innovation. Financial products are confusing and + stressful for customers. Service innovations (real-time support, + transparent status tracking, proactive financial guidance) build trust + and reduce churn." + fintech_example: "Stripe's success maps across multiple innovation types: + Process (one-line API integration vs. months of payment gateway setup), + Network (developer ecosystem creating distribution), Profit Model + (pay-per-transaction vs. monthly minimums and setup fees), Channel + (embedded directly in developers' code), and Structure (remote-first + global team accessing talent globally). Product Performance (payment + processing itself) was deliberately NOT the primary innovation — Stripe + processes payments through existing infrastructure. The multi-type + innovation created compound defensibility that commodity processors could + not replicate." + benchmark_references: [ "cac", "cost-per-transaction", "kyc-cost-per-customer" ] + + - skill: "eisenhower-matrix" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "The Eisenhower Matrix in fintech is complicated by the fact + that regulatory deadlines create non-negotiable urgency. Regulatory + examination responses, license renewal deadlines, SAR filing requirements, + and consent order compliance timelines are all Urgent AND Important — they + cannot be deprioritized. This compresses the available bandwidth for Not + Urgent/Important strategic work (product vision, market expansion, + partnership development). The fintech-specific challenge is distinguishing + between genuinely urgent compliance requirements and compliance theater + (activities that feel urgent because they involve regulators but are not + actually time-critical). BSA/AML transaction monitoring is + Urgent/Important. Updating an internal compliance policy that is already + effective is Not Urgent/Important." + fintech_anti_patterns: + - "Treating all regulatory activities as Urgent/Important. Compliance work + ranges from genuinely urgent (SAR filing within 30 days of detection) to + strategically important but not urgent (building a compliance training + program) to busywork (reformatting existing policies for aesthetic + reasons)." + - "Deprioritizing compliance infrastructure as Not Urgent because no + regulator has asked about it yet. The absence of regulatory inquiry is + not evidence that compliance is adequate — it is evidence that you have + not been examined." + - "Delegating regulatory relationship management. The CEO's relationship + with regulators is Urgent/Important and cannot be delegated — regulatory + goodwill is a strategic asset." + fintech_example: "A fintech CEO uses the Eisenhower Matrix to discover that 50% + of leadership time is consumed by Urgent/Not Important activities: + responding to banking partner operational requests, reviewing routine + compliance reports that the CCO should own, and attending standing + meetings with external counsel that could be async. The critical finding: + Not Urgent/Important activities — building a second banking partner + relationship, preparing for future regulatory examinations, developing the + compliance technology roadmap — receive zero time. The matrix + restructuring frees 10 hours per week for strategic compliance and growth + work." + benchmark_references: [ "regulatory-compliance-cost" ] + + - skill: "emotional-intelligence" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "Emotional intelligence in fintech extends beyond interpersonal + dynamics to a specific domain: managing the emotional weight of handling + other people's money. Customers who experience financial distress (account + freezes, loan denials, fraud on their accounts) are in heightened + emotional states that require specific EI competencies. Regulators who + examine the company are human beings whose concerns must be understood and + addressed with emotional sophistication — adversarial regulatory + relationships lead to enforcement actions. Banking partners experience + anxiety about regulatory risk that manifests as restrictive behavior — + understanding and addressing their emotional concerns (not just their + contractual requirements) maintains critical partnerships." + fintech_anti_patterns: + - "Treating customer financial distress as a purely operational issue. A + customer whose account is frozen due to a false-positive fraud alert is + not a 'ticket to resolve' — they are a person who cannot access their + money. The emotional dimension of financial services failures is + categorically different from a software bug." + - "Approaching regulatory examinations as adversarial. Regulators are + executing a mandate; meeting them with defensiveness rather than + transparency and collaboration escalates the examination and increases + enforcement risk." + - "Ignoring the emotional toll on compliance and risk teams. People who + spend their days reviewing fraud cases, suspicious activity, and + financial crimes experience secondary trauma. EI for fintech leaders + includes caring for these teams." + fintech_example: "A neobank's VP of Customer Success applies emotional + intelligence during a regulatory-mandated mass account review that + requires freezing 2,000 accounts for enhanced due diligence. Rather than + sending form letters, the team implements personalized outreach explaining + the review, providing a timeline, and offering alternative access to funds + where possible. The EI-informed approach transforms a potential PR crisis + into a trust-building moment — customers who felt respected during the + process became more loyal than customers who never experienced the + freeze." + benchmark_references: [ "monthly-active-users", "net-revenue-retention" ] + + - skill: "black-swans" + category: "frameworks" + fintech_relevance: "critical" + fintech_context: "Fintech is uniquely exposed to black swan events because + financial systems are interconnected, leveraged, and trust-dependent. A + black swan in fintech can propagate through the system: a BaaS provider + failure can freeze customer funds for dozens of fintech companies (as the + Synapse collapse demonstrated in 2024). A sovereign debt crisis can freeze + cross-border payment corridors overnight. A zero-day vulnerability in a + widely-used identity verification API can expose millions of KYC records. + A regulatory enforcement action against one prominent fintech can trigger + enhanced scrutiny of the entire sector. The black swan framework must be + applied not just to the company's own operations but to its banking + partners, technology providers, regulatory environment, and the broader + financial system." + fintech_anti_patterns: + - "Assuming partner stability. The Synapse BaaS failure in 2024 + demonstrated that a banking-as-a-service provider collapse can freeze + customer funds across dozens of fintech companies. Partner risk IS + company risk." + - "Ignoring correlated risks. A credit cycle downturn simultaneously + increases default rates, reduces transaction volume, tightens funding + markets, and intensifies regulatory scrutiny — these are not independent + events." + - "Treating cybersecurity as an IT concern rather than an existential + risk. A data breach at a fintech is not a PR problem — it is a + regulatory enforcement trigger, a customer trust destroyer, and + potentially a company-ending event." + fintech_example: "The Synapse BaaS collapse in 2024 was a black swan for the + fintech companies that relied on it. Customer funds were frozen for + months, regulatory investigations were launched, and several fintech + companies faced existential crises. The lesson for black swan planning: + fintech companies must stress-test their banking partner dependencies, + maintain contingency plans for partner failure, ensure customer funds are + properly segregated and reconciled, and — most critically — understand the + regulatory framework governing their banking relationships deeply enough + to protect customers when the unexpected occurs." + benchmark_references: [ "capital-adequacy-ratio", "fraud-rate", "regulatory-compliance-cost" ] + + # ───────────────────────────────────────────── + # GAME THEORY (5 skills) + # ───────────────────────────────────────────── + + - skill: "game-theory-fundamentals" + category: "game-theory" + fintech_relevance: "critical" + fintech_context: "Fintech operates within a multi-player game that includes a + uniquely powerful player: the regulator. Unlike traditional competitive + games where all players follow the same rules, the regulator writes the + rules, enforces them asymmetrically, and can change them mid-game. Game + theory in fintech must model: (1) The regulatory game — compliance as a + cooperative game with regulators where good-faith collaboration yields + better outcomes than adversarial minimum compliance. (2) The competitive + game — where regulatory barriers create oligopolistic dynamics and + compliance capability is a competitive weapon. (3) The partnership game — + where banking partners, card networks, and identity providers are + simultaneously cooperators and potential competitors. (4) The trust game — + where customer trust is a repeated game and a single defection (breach, + fraud, hidden fee) can terminate the relationship permanently." + fintech_anti_patterns: + - "Modeling the competitive game without the regulatory player. Fintech + strategy that ignores how regulators will react to competitive moves is + fatally incomplete. Aggressive pricing, rapid expansion, or innovative + product launches all have regulatory implications." + - "Treating regulatory compliance as a one-shot game. It is a repeated + game with memory — regulators remember past behavior. A fintech with a + history of good-faith compliance receives more favorable treatment than + one with a history of resistance." + - "Applying zero-sum thinking to the regulatory relationship. The + regulator's goal (consumer protection, financial stability) is not + opposed to the fintech's goal (growth, profitability) — regulatory + compliance and commercial success can be aligned." + fintech_example: "A payments company analyzes its competitive dynamics as a + three-player game: the company, a direct competitor, and the state + regulator considering new licensing requirements. If both companies lobby + against the regulation, it may be blocked but at reputational cost. If the + company embraces the regulation while the competitor opposes it, the + company gains regulatory goodwill and the competitor faces enforcement + risk. The Nash equilibrium analysis reveals that proactive regulatory + engagement (cooperate with the regulator) is the dominant strategy — the + company that embraces regulation earliest converts a constraint into a + competitive advantage." + benchmark_references: [ "regulatory-compliance-cost", "take-rate" ] + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + fintech_relevance: "critical" + fintech_context: "The Prisoner's Dilemma appears repeatedly in fintech: in + industry-wide compliance standards (if all companies invest in AML, the + ecosystem is safer; if one defects by under-investing, they gain a cost + advantage until caught), in data sharing for fraud prevention (sharing + fraud data helps everyone but revealing patterns might help competitors), + and in banking partnerships (both parties benefit from cooperation but + each has incentives to extract more value). The most consequential dilemma + is the compliance investment dilemma: every fintech that under-invests in + compliance gains a short-term cost advantage but creates systemic risk + that triggers regulatory crackdowns affecting the entire industry. The + 2023-2024 wave of consent orders against neobanks demonstrated the + collective punishment that follows when individual players defect on + compliance." + fintech_anti_patterns: + - "Defecting on compliance investment because competitors appear to be + under-investing. The short-term cost advantage of compliance + under-investment is dwarfed by the expected cost of enforcement actions + — the game is iterated, and the regulator always detects defection + eventually." + - "Refusing to participate in industry fraud data sharing networks because + of competitive concerns. The collective benefit of fraud network + disruption outweighs the marginal competitive information shared." + - "Treating the banking partner relationship as exploitative rather than + cooperative. Fintechs that extract maximum value from banking partners + while contributing minimum compliance effort face relationship + termination — the partner will defect when the regulatory risk exceeds + the revenue benefit." + fintech_example: "The fintech industry's response to the Synapse BaaS collapse + illustrates the Prisoner's Dilemma in action. Before the collapse, + individual fintechs had incentives to minimize banking partner due + diligence (cost savings). After the collapse, every fintech in the BaaS + ecosystem faced enhanced scrutiny because the industry had collectively + under-invested in partner oversight. The Nash equilibrium shifted: + regulatory attention made compliance cooperation the dominant strategy. + Industry groups formed to establish BaaS oversight standards — a + cooperative equilibrium enforced by the regulatory threat." + benchmark_references: [ "regulatory-compliance-cost", "fraud-rate" ] + + - skill: "first-mover-strategy" + category: "game-theory" + fintech_relevance: "high" + fintech_context: "First-mover advantage in fintech is complicated by the + regulatory approval timeline. A fintech can be first-to-market with a + product concept but blocked from launch by licensing delays — creating a + window for competitors who find faster regulatory pathways. Conversely, + being the first company to obtain a specific license or charter creates a + durable advantage because the regulatory process acts as a years-long + barrier to entry. The most powerful first-mover advantages in fintech are + regulatory: being the first to obtain a bank charter (Varo), the first to + gain a BitLicense (Circle), or the first to secure approval for a novel + product structure creates moats that market-based first-mover advantages + cannot match." + fintech_anti_patterns: + - "Racing to launch before regulatory approval is complete. + First-to-market with an unlicensed product is not a first-mover + advantage — it is a violation. The penalty for operating without + required licenses far exceeds any revenue gained." + - "Assuming first-mover advantage is permanent in regulated markets. + Regulators can mandate interoperability (open banking), eliminate + proprietary advantages (data portability), or create new competitive + pathways (new charter types) that erode first-mover moats." + - "Ignoring the second-mover advantage in fintech compliance. Second + movers can learn from the first mover's regulatory mistakes and + compliance costs, often launching with better compliance at lower cost." + fintech_example: "Varo Bank became the first consumer fintech to receive a + national bank charter from the OCC in 2020. This first-mover advantage was + regulatory in nature: the charter application process took over three + years and cost tens of millions in legal and compliance preparation. + Competing fintechs who started the charter process later (Revolut, SoFi) + faced similar timelines. Varo's first-mover advantage was not in product + innovation but in regulatory positioning — the charter enabled + deposit-funded lending with dramatically better unit economics than the + BaaS-dependent model competitors were forced to use." + benchmark_references: + [ + "net-interest-margin", + "regulatory-compliance-cost", + "capital-adequacy-ratio" + ] + + - skill: "information-asymmetry" + category: "game-theory" + fintech_relevance: "critical" + fintech_context: "Information asymmetry is the foundational problem that + financial regulation exists to address. Lenders know less about borrowers + than borrowers know about themselves (adverse selection). Borrowers may + take on more risk after obtaining a loan (moral hazard). Customers do not + understand complex financial product terms (information asymmetry in + pricing). Fintech innovation either reduces or exploits these asymmetries + — and the regulatory response depends on which. Fintechs that use + alternative data to reduce information asymmetry in credit underwriting + (reducing adverse selection) are generally embraced by regulators. + Fintechs that exploit information asymmetry to sell opaque products to + unsophisticated consumers (increasing asymmetry) face enforcement. The + regulatory lens is: does this innovation make information more symmetric + or less?" + fintech_anti_patterns: + - "Exploiting information asymmetry in product design. Complex fee + structures, opaque pricing, and deliberately confusing terms may + increase short-term revenue but trigger UDAP/UDAAP enforcement and + destroy trust." + - "Ignoring adverse selection in lending. Without robust underwriting, + lending platforms attract the borrowers that traditional lenders have + already rejected — the information asymmetry problem that has driven + lending regulation for centuries." + - "Failing to recognize that regulators exist to address information + asymmetry. Financial regulation is fundamentally about leveling the + information playing field. Innovations that align with this goal receive + regulatory support; innovations that oppose it receive enforcement." + fintech_example: "Upstart's approach to information asymmetry in lending + demonstrates the regulatory-innovation alignment. Traditional credit + scoring uses limited variables (FICO, income, debt ratio), creating + information asymmetry where the lender cannot distinguish between + borrowers with similar scores but different true risk profiles. Upstart's + AI model incorporates additional variables (education, employment history, + cost of living) to reduce this asymmetry. Critically, Upstart obtained a + CFPB no-action letter by demonstrating that its model expanded credit + access without increasing risk — the innovation reduced information + asymmetry, aligning with regulatory goals. The company openly publishes + fair lending analysis, further reducing the asymmetry between regulator + and lender." + benchmark_references: [ "default-rate", "loan-origination-volume" ] + + - skill: "coalition-and-partnership-games" + category: "game-theory" + fintech_relevance: "high" + fintech_context: "Coalition formation in fintech is shaped by the regulatory + requirement for licensed intermediaries. Every fintech coalition must + include at least one regulated entity — a bank, a broker-dealer, an + insurance carrier — whose license enables the coalition's activities. This + creates asymmetric coalition dynamics: the regulated entity has outsized + power because their license is the enabling asset. Coalition games in + fintech include: BaaS partnerships (fintech + bank), payment processing + alliances (fintech + card network + issuing bank), lending marketplaces + (fintech platform + multiple lending partners), and embedded finance + (non-financial platform + fintech infrastructure provider). Each coalition + must solve the regulatory allocation problem: who bears the compliance + responsibility, and who bears the regulatory risk?" + fintech_anti_patterns: + - "Entering a coalition without understanding regulatory responsibility + allocation. When a fintech uses a banking partner, the bank bears + primary regulatory responsibility — but the fintech's actions create the + bank's regulatory risk. This asymmetry must be explicitly addressed." + - "Forming coalitions based solely on commercial terms without assessing + regulatory risk sharing. A bank partnership with attractive revenue + terms but ambiguous compliance responsibility allocation is a liability, + not an asset." + - "Ignoring the regulatory pressure on banking partners. OCC, FDIC, and + Federal Reserve guidance on bank-fintech partnerships is tightening. + Banking partners face increasing pressure to oversee fintech activities, + which translates into operational restrictions on the fintech." + fintech_example: "The embedded finance coalition between Shopify and Stripe + demonstrates effective coalition game theory. Shopify provides the + merchant distribution (millions of merchants), Stripe provides the payment + infrastructure and regulatory compliance layer, and Celtic Bank (Stripe's + lending partner) provides the lending license. The coalition works because + each player contributes a resource the others cannot efficiently build + (distribution, infrastructure, license), and the regulatory responsibility + is clearly allocated — Stripe handles PCI-DSS and payment compliance, + Celtic Bank handles lending regulation, and Shopify handles the merchant + relationship. The coalition creates value that no individual player could + create alone." + benchmark_references: [ "tpv", "cac", "regulatory-compliance-cost" ] + + # ───────────────────────────────────────────── + # NEGOTIATION (3 skills) + # ───────────────────────────────────────────── + + - skill: "competitive-negotiation" + category: "negotiation" + fintech_relevance: "high" + fintech_context: "Competitive negotiation in fintech occurs across three primary + contexts: banking partner negotiations (the most critical — terms, + compliance responsibility allocation, revenue sharing), regulatory + negotiations (responding to examination findings, negotiating consent + order terms, advocating for favorable regulatory interpretations), and + enterprise client negotiations (compliance requirements embedded in + contracts, data security addenda, regulatory representation clauses). + Banking partner negotiations are uniquely high-stakes: the partner bank + holds asymmetric power because their license enables the fintech's + operations. Regulatory negotiations require a specific tone — adversarial + negotiation tactics that work in commercial settings can backfire + catastrophically with regulators." + fintech_anti_patterns: + - "Applying aggressive negotiation tactics to regulatory interactions. + Regulators have enforcement power that commercial counterparties do not. + 'Hardball' with a regulator escalates to enforcement actions." + - "Negotiating banking partnership terms without independent regulatory + counsel. Commercial terms that seem favorable may embed compliance + obligations that are operationally impractical or financially ruinous." + - "Using competitive leverage (threatening to switch banks) with a banking + partner during a regulatory examination period. The partner bank will + prioritize its regulatory standing over the commercial relationship — + every time." + fintech_example: "A fintech negotiates its banking partnership renewal after the + partner bank receives regulatory guidance to strengthen fintech oversight. + The bank proposes tripling compliance reporting requirements and imposing + a 60-day termination clause. Rather than countering aggressively, the + fintech prepares a detailed compliance portfolio demonstrating its + existing controls, proposes a joint compliance committee with shared cost, + and offers to undergo a voluntary third-party compliance audit. This + cooperative approach preserves the relationship while addressing the + bank's regulatory concern — competitive negotiation in fintech requires + understanding that the real counterparty is often the regulator, not the + negotiating partner." + benchmark_references: [ "regulatory-compliance-cost", "take-rate" ] + + - skill: "cooperative-negotiation" + category: "negotiation" + fintech_relevance: "critical" + fintech_context: "Cooperative negotiation is the dominant strategy for fintech + regulatory relationships. The regulatory examination process is + fundamentally a negotiation — the regulator identifies concerns, the + company proposes remediation, and both parties work toward an outcome that + satisfies regulatory requirements while allowing business continuity. This + negotiation is cooperative, not competitive — both parties benefit from a + well-regulated, sustainable fintech. Cooperative negotiation also governs + industry consortium formation (shared KYC utilities, fraud data networks, + regulatory advocacy groups) where competitors must collaborate on + non-competitive infrastructure. The embedded finance ecosystem depends on + cooperative negotiation between platforms, infrastructure providers, and + banks." + fintech_anti_patterns: + - "Treating regulatory examinations as adversarial. Examiners who feel the + company is being obstructive escalate findings. Transparent, cooperative + engagement results in better outcomes — examiners who feel the company + is genuinely committed to compliance give the benefit of the doubt on + ambiguous issues." + - "Negotiating data sharing agreements with competitive restrictions that + prevent fraud prevention cooperation. In fintech, shared fraud + intelligence is a collective good — restrictions that protect + competitive advantage at the expense of fraud detection harm the + ecosystem." + - "Entering multi-party partnerships (embedded finance) without + cooperative framework agreements. Without explicit cooperation norms, + partnership coalitions devolve into competitive extraction — each party + trying to capture more of the value at others' expense." + fintech_example: "A group of competing neobanks forms a cooperative consortium + to share anonymized fraud pattern data. Each participant feared sharing + would help competitors. Cooperative negotiation produced a framework: data + is anonymized and aggregated (no individual transaction data shared), + contributions are measured and reciprocity enforced (free-riders are + excluded), and a neutral third party manages the data (no participant + gains competitive intelligence beyond fraud patterns). The result: all + participants saw 30% improvement in fraud detection rates. The cooperative + equilibrium proved more valuable than the competitive information each + party feared sharing." + benchmark_references: [ "fraud-rate", "fraud-loss-rate", "regulatory-compliance-cost" ] + + - skill: "delivering-the-deal" + category: "negotiation" + fintech_relevance: "high" + fintech_context: "Deal execution in fintech is complicated by regulatory + requirements embedded in every contract. Enterprise fintech deals require: + regulatory compliance representations (the product complies with + applicable laws), data security addenda (PCI-DSS, SOC 2, GDPR compliance), + business continuity provisions (what happens if the fintech loses its + license or banking partner), and regulatory change clauses (who bears the + cost when regulations change). Banking partnership agreements require: + compliance responsibility matrices (who does KYC, who files SARs), audit + rights (the bank must be able to examine the fintech's compliance + program), and termination triggers (regulatory events that allow immediate + termination). These deal elements add 30-60 days to typical sales cycles." + fintech_anti_patterns: + - "Attempting to close deals without pre-prepared compliance + documentation. Enterprise buyers and banking partners request SOC 2 + reports, PCI-DSS attestations, penetration test results, and regulatory + licenses before closing. Not having these ready extends the sales cycle + by months." + - "Ignoring regulatory change clauses in long-term contracts. A three-year + contract without a mechanism to address regulatory changes (new + compliance requirements, new fee caps) creates unpredictable risk for + both parties." + - "Treating regulatory representations as boilerplate. Representing that + your product 'complies with all applicable laws' creates legal + liability. Each representation should be reviewed by regulatory counsel + and scoped to specific regulations." + fintech_example: "A B2B fintech creates a 'regulatory deal kit' for enterprise + sales: pre-completed SOC 2 Type II report, PCI-DSS Attestation of + Compliance, state-by-state license registry, data processing agreement + (GDPR-compliant), BSA/AML program summary, and penetration test results + (redacted). The kit also includes a compliance responsibility matrix + template that clearly allocates regulatory obligations between the fintech + and the client. This kit reduces enterprise deal cycles from 120 days to + 65 days by preempting the three most common stall points: security review, + regulatory verification, and compliance responsibility negotiation." + benchmark_references: [ "cac", "regulatory-compliance-cost" ] + + # ───────────────────────────────────────────── + # THINKING & DECISIONS (4 skills) + # ───────────────────────────────────────────── + + - skill: "enemies-of-clear-thinking" + category: "thinking" + fintech_relevance: "critical" + fintech_context: "Fintech operators face cognitive biases amplified by the + high-stakes, regulation-heavy nature of financial services. Survivorship + bias: benchmarking against successful neobanks while ignoring the majority + that failed or received enforcement actions. Sunk cost fallacy: continuing + to invest in a banking partner relationship that is deteriorating because + switching costs seem prohibitive. Confirmation bias: interpreting + ambiguous compliance signals as 'no news is good news' rather than + investigating potential violations. Anchoring: fixating on the initial + take rate or NIM assumption when market conditions and regulations have + shifted. Normalcy bias: assuming the current regulatory environment is + permanent when legislative change is imminent. Optimism bias: + under-estimating default rates and over-estimating credit model accuracy + because the model has not yet been tested through a credit cycle." + fintech_anti_patterns: + - "Using benign credit period data to validate credit models. A model that + performs well during economic expansion has not been tested. Optimism + bias makes founders believe their underwriting is superior when it may + simply be untested." + - "Interpreting regulatory silence as regulatory approval. The absence of + an enforcement action does not mean the company is compliant — it means + the company has not yet been examined. Normalcy bias creates false + security." + - "Anchoring on early vintage loan performance when projecting portfolio + quality. Early borrowers are systematically different from later + borrowers — they are typically lower risk because they self-select. + Extrapolating early performance to the full portfolio is a textbook + anchoring error." + fintech_example: "A lending fintech reports a 1% default rate and celebrates its + underwriting model. An advisor trained in clear thinking identifies three + biases: (1) Vintage bias — the portfolio is only 8 months old, and most + defaults occur between months 12-24. (2) Survivorship bias — comparing to + the 1% default rate of successful lending fintechs while ignoring the + 5-10% default rates that caused several competitors to fail. (3) + Confirmation bias — the team cites the 1% rate as evidence the model works + while ignoring early delinquency signals that suggest default rates will + rise. The clear-thinking intervention triggers a stress test that projects + 3-4% default rates at portfolio maturity — fundamentally changing the + capital planning." + benchmark_references: [ "default-rate", "net-interest-margin", "loan-origination-volume" ] + + - skill: "evaluating-and-deciding" + category: "thinking" + fintech_relevance: "high" + fintech_context: "Decision-making in fintech must account for a dimension absent + in most industries: regulatory irreversibility. Some fintech decisions are + irreversible not because of market dynamics but because of regulatory + consequences. Launching a product without proper licensing cannot be + 'undone' — the regulatory record of unlicensed activity persists. A + compliance failure that triggers an enforcement action permanently alters + the company's regulatory profile. The one-way-door / two-way-door + framework must be expanded in fintech to include a third category: + regulatory one-way doors — decisions that create permanent regulatory + records regardless of whether they can be commercially reversed." + fintech_anti_patterns: + - "Treating regulatory decisions as two-way doors. Applying for a bank + charter, launching a lending product, or entering a new regulated market + creates regulatory obligations and records that cannot be reversed by + simply stopping the activity." + - "Deciding by speed when the decision has regulatory implications. The + 'move fast' ethos must be tempered by regulatory awareness — fast + decisions that create compliance violations are expensive regardless of + how quickly they were made." + - "Over-relying on data for credit decisions without understanding model + risk management requirements. Regulators require that credit models be + explainable, fair, and validated — a purely data-driven decision process + that cannot explain its logic violates regulatory requirements (ECOA, + FCRA, SR 11-7)." + fintech_example: "A fintech must decide whether to apply for a bank charter or + continue operating through a banking partner. Applying the expanded + one-way-door framework: Charter application is a regulatory one-way door — + once filed, the company is under OCC supervision, must submit to + examinations, and the application outcome becomes part of the permanent + regulatory record. The partnership is a two-way door commercially but + creates regulatory dependencies. The team analyzes both options through + the regulatory irreversibility lens and decides to pursue the charter — + accepting the regulatory one-way door because the long-term unit economics + (deposit funding vs. warehouse lending) justify the permanent commitment." + benchmark_references: + [ + "net-interest-margin", + "regulatory-compliance-cost", + "capital-adequacy-ratio" + ] + + - skill: "defining-and-exploring-problems" + category: "thinking" + fintech_relevance: "high" + fintech_context: "Problem definition in fintech must always ask: is this a + market problem, a product problem, or a regulatory problem? These three + root cause categories require fundamentally different solutions, and + misdiagnosis is common. Declining transaction volume could be a market + problem (competition, economic downturn), a product problem (UX friction, + feature gaps), or a regulatory problem (compliance-driven account + closures, new KYC requirements deterring customers). Rising default rates + could be a credit model problem, an economic cycle problem, or a + regulatory problem (adverse selection caused by new fair lending + requirements). The discipline of separating market, product, and + regulatory root causes prevents fintech teams from applying product + solutions to regulatory problems." + fintech_anti_patterns: + - "Defining the problem as 'we need feature X' when the real problem is + regulatory friction. Building a better payment screen does not solve the + problem if customers are abandoning during KYC verification." + - "Framing regulatory requirements as problems to be solved rather than + constraints to be optimized within. 'The problem is we need to do KYC' + is wrong framing. 'The problem is our KYC process takes 4 minutes when + it should take 30 seconds' is correct framing." + - "Conflating symptoms across different root cause categories. 'Customers + are churning' is a symptom. If some churn is product-driven (bad UX), + some is market-driven (competitor offering better rates), and some is + compliance-driven (account closures from risk reviews), treating it as a + single problem leads to solutions that address none of the causes." + fintech_example: "A neobank diagnoses 'declining growth' and the product team + proposes building five new features. Rigorous problem exploration reveals + three distinct problems: (1) KYC conversion dropped 15% after adding a new + identity verification step required by updated BSA/AML guidance — a + regulatory problem requiring UX optimization of the compliance flow. (2) + New customer activation declined because the onboarding flow does not + guide users to set up direct deposit — a product problem. (3) Marketing + CAC increased 40% because a competitor launched a high-yield savings + promotion — a market problem requiring competitive response. The product + team's feature proposal would have addressed none of these actual + problems." + benchmark_references: [ "kyc-conversion-rate", "cac", "monthly-active-users" ] + + - skill: "tough-decision-situations" + category: "decisions" + fintech_relevance: "critical" + fintech_context: "Fintech founders face uniquely difficult decisions that carry + regulatory and legal consequences beyond commercial impact. Whether to + self-report a compliance failure to regulators (legally required in many + cases, strategically important in all). Whether to exit a banking partner + relationship when the partner faces regulatory issues (staying risks + contagion, leaving disrupts operations). Whether to restrict a profitable + product when internal compliance review identifies potential fair lending + issues (short-term revenue vs. long-term enforcement risk). Whether to + pursue a bank charter (years of regulatory effort and supervision vs. + permanent unit economics advantage). Whether to shut down a product that + has customer obligations (data retention, account migration, regulatory + wind-down requirements). These decisions cannot be made on commercial + grounds alone — they require regulatory judgment." + fintech_anti_patterns: + - "Delaying self-reporting of compliance failures in hopes they will be + resolved before discovery. Regulators penalize concealment far more + severely than the underlying violation. The cover-up is always worse + than the crime in regulatory enforcement." + - "Making tough decisions about regulated products without regulatory + counsel present. Commercial instincts that serve well in unregulated + businesses can lead to disastrous outcomes when applied to regulated + financial products." + - "Treating ethical concerns about financial products (predatory lending + terms, exploitative fee structures, algorithmic bias in credit scoring) + as merely PR risks rather than regulatory and moral obligations. + UDAP/UDAAP and fair lending laws exist because these are not just bad PR + — they are illegal." + fintech_example: "A lending fintech's internal audit discovers that its AI + credit model is inadvertently producing disparate impact in loan approvals + across protected demographic groups. The tough decision: continue + operating the model (which is profitable and passes traditional + statistical tests) while investigating, or immediately suspend it + (disrupting operations and loan volume) until the fair lending analysis is + complete. The company chooses suspension, self-reports to the CFPB, and + engages an independent fair lending auditor. The decision costs $2M in + lost origination but avoids a potential $50M+ enforcement action — and + demonstrates to regulators that the company takes fair lending seriously, + building regulatory goodwill that proves valuable in future interactions." + benchmark_references: [ "regulatory-compliance-cost", "default-rate", "loan-origination-volume" ] + + # ───────────────────────────────────────────── + # AI & LEADERSHIP (3 skills) + # ───────────────────────────────────────────── + + - skill: "ai-vision-and-strategy" + category: "ai-leadership" + fintech_relevance: "critical" + fintech_context: "AI in fintech operates under regulatory requirements that do + not exist in other industries. Credit underwriting models using AI/ML must + comply with fair lending laws (ECOA, FCRA) that require explainability — a + model that cannot explain why it denied a loan application violates + adverse action notice requirements. AI-driven fraud detection must balance + effectiveness with false-positive rates that affect customer access to + funds. AI-based customer communication must comply with financial services + disclosure requirements. The SR 11-7 guidance on model risk management + requires that all models used in financial decision-making (credit, + pricing, risk) be validated, documented, and subject to independent + review. EU AI Act classifies financial services AI as 'high-risk,' + imposing additional requirements. AI strategy in fintech must be + compliance-first: what is the regulatory framework for AI in our specific + financial activity, and how does our AI approach satisfy it?" + fintech_anti_patterns: + - "Deploying black-box ML models for credit decisions. Regulators require + that credit decisions be explainable. A model that accurately predicts + default but cannot explain its reasoning violates adverse action notice + requirements under ECOA and FCRA." + - "Using AI to optimize revenue extraction without fair lending analysis. + An AI that optimizes pricing may inadvertently create disparate impact + across protected demographic groups — a violation regardless of intent." + - "Treating AI model validation as a one-time event. SR 11-7 requires + ongoing monitoring, periodic revalidation, and challenger model + comparison. A model validated at launch but never revalidated is a + compliance risk." + fintech_example: "Upstart developed an AI credit underwriting model that expands + beyond traditional FICO scores. Critically, the company obtained a CFPB + no-action letter before scaling, demonstrated fair lending compliance + through published disparate impact analysis, and maintained explainability + features that generate specific adverse action reasons for every denied + application. The AI strategy was regulatory-first: prove to regulators + that the model expands credit access (reducing information asymmetry) + rather than exploiting it, and do so transparently. This regulatory + alignment enabled Upstart to scale to $12B+ in loan originations while + facing less regulatory friction than competitors who deployed AI without + regulatory engagement." + benchmark_references: [ "default-rate", "loan-origination-volume", "regulatory-compliance-cost" ] + + - skill: "ai-human-centered-approach" + category: "ai-leadership" + fintech_relevance: "high" + fintech_context: "Human-centered AI in fintech is not just a design philosophy — + it is a regulatory requirement. The CFPB has issued guidance that + automated financial decision-making must include meaningful human + oversight. Fair lending laws require that AI-driven credit decisions be + reviewable by humans who can explain the reasoning. Customer-facing AI + (chatbots, robo-advisors) must include escalation to human agents for + complex financial questions. The human-centered approach in fintech means: + humans design the models, humans validate the outputs, humans oversee the + decisions, and humans are available when AI fails. This is not optional — + it is a regulatory mandate under SR 11-7, ECOA, and emerging AI + regulations." + fintech_anti_patterns: + - "Removing human oversight from financial decision-making to reduce + costs. Regulators expect human review of AI-driven credit decisions, + fraud alerts, and compliance determinations. Full automation without + human oversight is a regulatory violation." + - "Deploying customer-facing AI without human escalation paths. A chatbot + that handles financial complaints without the ability to escalate to a + human violates consumer protection expectations and potentially + UDAP/UDAAP." + - "Treating AI explainability as a feature rather than a requirement. In + financial services, explainability is not a nice-to-have — it is legally + required for credit decisions, insurance underwriting, and investment + recommendations." + fintech_example: "A robo-advisor implements AI-driven portfolio management but + applies human-centered design principles required by SEC/FINRA guidance: + algorithmic recommendations are explained in plain language, customers can + override AI suggestions, a registered investment advisor reviews flagged + recommendations before execution, and quarterly human-reviewed performance + reports are generated. The human-centered approach costs 15% more than + full automation but satisfies regulatory requirements, reduces liability + exposure, and produces higher customer trust scores — trust that + translates directly to higher AUM retention." + benchmark_references: [ "aum", "monthly-active-users", "regulatory-compliance-cost" ] + + - skill: "strategic-thinking-and-alignment" + category: "leadership" + fintech_relevance: "high" + fintech_context: "Strategic alignment in fintech must incorporate the compliance + function as a strategic partner, not a cost center. The most common + misalignment in fintech organizations is between the growth team (which + wants speed and scale) and the compliance team (which wants control and + risk mitigation). This tension is productive when managed — compliance + constraints force creative solutions and build sustainable competitive + advantages. It is destructive when one side dominates — uncontrolled + growth leads to enforcement actions; excessive compliance conservatism + prevents market entry. Strategic alignment means ensuring that growth + targets include compliance readiness, that product roadmaps include + regulatory features, and that the compliance team understands commercial + objectives well enough to find compliant paths to growth." + fintech_anti_patterns: + - "Treating compliance as a veto function rather than an enabling + function. A compliance team that only says 'no' is not aligned with the + business. Aligned compliance says 'not that way, but here is a compliant + way to achieve the same goal.'" + - "Excluding the Chief Compliance Officer from strategic planning. The CCO + should be present at strategy offsites, product planning sessions, and + board meetings — not consulted after decisions are made." + - "Setting growth targets without modeling the compliance infrastructure + required to support them. Doubling customer count requires proportional + investment in transaction monitoring, KYC operations, and regulatory + reporting capacity." + fintech_example: "A neobank's CEO institutes 'compliance-in-the-room' policy: + the CCO or a compliance delegate attends every product planning meeting + and every go-to-market strategy session. Initially resisted by the product + team as slowing decisions, the policy produces unexpected benefits: + compliance identifies regulatory risks early (preventing costly late-stage + redesigns), suggests compliant alternatives to blocked product ideas, and + provides regulatory intelligence that opens new market opportunities. + Strategic alignment transforms compliance from a cost center into a + strategic advantage — the company launches products faster than + competitors because compliance is built in, not bolted on." + benchmark_references: [ "regulatory-compliance-cost", "monthly-active-users" ] + + - skill: "kaizen-bpr" + category: "frameworks" + fintech_relevance: "high" + fintech_context: "Kaizen and Business Process Reengineering in fintech must + focus on compliance processes as the primary efficiency opportunity. KYC + onboarding, transaction monitoring, SAR filing, regulatory reporting, and + audit preparation are process-heavy activities that consume 10-25% of + fintech operating costs. Small, continuous improvements (Kaizen) apply to + reducing false positive rates in fraud detection, shortening KYC + verification time, and accelerating regulatory report generation. Business + Process Reengineering applies to fundamental restructuring — replacing + manual transaction monitoring with automated systems, transitioning from + batch to real-time regulatory reporting, or consolidating multi-state + compliance into a unified framework." + fintech_anti_patterns: + - "Applying BPR to compliance processes without regulatory counsel. + Redesigning the AML process to be 'more efficient' may inadvertently + eliminate controls that regulators require. Process redesign in + compliance must be validated against regulatory requirements." + - "Ignoring the compliance process improvement opportunity. Many fintechs + invest heavily in product and engineering process improvement while + running compliance on manual spreadsheets and email chains." + - "Treating compliance process improvements as one-time projects. + Regulatory requirements change continuously — a process optimized for + today's regulations may be non-compliant tomorrow. Kaizen (continuous + improvement) is the correct approach." + fintech_example: "A payments fintech applies Kaizen to its SAR filing process + and discovers that the average time from alert to filing is 22 days — + against a regulatory expectation of 30 days but with no buffer for complex + cases. Small improvements over six months: automated pre-population of SAR + forms from transaction data (saves 2 days), standardized narrative + templates for common typologies (saves 1 day), and a triage system that + routes simple cases to junior analysts and complex cases to senior + investigators (improves quality while reducing cycle time to 14 days). The + Kaizen approach produces compliant, efficient processes without the risk + of a full BPR that might inadvertently remove required controls." + benchmark_references: + [ + "regulatory-compliance-cost", + "kyc-cost-per-customer", + "cost-to-income-ratio" + ] diff --git a/plugins/foreman/content/industry-packs/fintech/fintech-templates.yaml b/plugins/foreman/content/industry-packs/fintech/fintech-templates.yaml new file mode 100644 index 0000000..5ade95b --- /dev/null +++ b/plugins/foreman/content/industry-packs/fintech/fintech-templates.yaml @@ -0,0 +1,1031 @@ +# Fintech Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for fintech companies. The output agent loads these rules +# when generating documents with the fintech industry pack active. +# +# REGULATORY PRINCIPLE: All investor, board, and client-facing materials must +# include regulatory status, compliance framework, and license standing as +# first-class dimensions. Risk assessment always includes regulatory risk. +# Unit economics must separate regulated vs. unregulated revenue lines. +# Board materials must include compliance standing, audit findings, and +# regulatory change tracking. +# +# Adaptation types: +# as-is — The template works without modification for fintech companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for fintech context. + +pack_metadata: + sector: "fintech" + display_name: "Fintech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech unit economics differ fundamentally from SaaS. Revenue lines are a mix of interchange, NIM, fees, and subscription income — each with different regulatory exposure and margin profiles. Unit economics must separate regulated and unregulated revenue, include compliance cost per customer, and account for credit losses in lending businesses." + field_changes: + - field: "Revenue per unit" + sector_label: "Revenue per Customer (by Revenue Line)" + sector_guidance: "Decompose revenue per customer by type: interchange/processing revenue (subject to Durbin/PSD2 caps), net interest income (subject to usury caps and credit risk), fee revenue (subject to UDAP/UDAAP), and subscription/platform revenue (unregulated). Report each separately because regulatory exposure differs dramatically." + - field: "Cost per unit" + sector_label: "CAC (Fully Loaded Including KYC)" + sector_guidance: "Include all acquisition costs: marketing, sales, sign-up incentives, KYC/identity verification, and initial compliance screening. In fintech, KYC costs ($3-$15 per consumer) are a non-discretionary component of CAC that does not exist in unregulated businesses." + - field: "Margin per unit" + sector_label: "Gross Margin by Revenue Line" + sector_guidance: "Report gross margin separately for each revenue type. Interchange margin net of processing costs. NIM net of cost of funds and credit provisions. Fee margin net of compliance costs. Platform/subscription margin. Blended gross margin masks the true economics of each revenue stream." + - field: "Lifetime value" + sector_label: "LTV (Risk-Adjusted)" + sector_guidance: "Calculate LTV incorporating: revenue per customer (multi-product if applicable), gross margin by revenue line, ongoing compliance costs (transaction monitoring, KYC refresh, regulatory reporting allocation), and for lending — expected credit losses. Disclose churn rate assumption and average customer lifetime." + - field: "Acquisition cost" + sector_label: "CAC Payback Period" + sector_guidance: "Report in months. For multi-product fintechs, report payback on initial product and accelerated payback when customers adopt additional products. Include the compliance cost runway — how long compliance infrastructure costs persist before being amortized across sufficient customers." + - field: "Unit economics ratio" + sector_label: "LTV:CAC Ratio (by Customer Segment)" + sector_guidance: "Report the ratio by segment (consumer, SMB, enterprise) and by product. A blended LTV:CAC can mask segments where unit economics are negative. Nubank's LTV:CAC above 5x at IPO was the benchmark-setting disclosure for fintech unit economics." + sections_to_add: + - section_name: "Fintech Metrics Dashboard" + placement: "before:Revenue per Customer (by Revenue Line)" + description: "Core fintech metrics in a format investors expect. Varies by sub-sector." + fields: + - "TPV / Loan Origination Volume / AUM (as applicable)" + - "Take Rate / NIM / Management Fee" + - "Net Revenue and growth rate" + - "Monthly Active Users and transactions per user" + - "Net Revenue Retention" + - "Gross Margin (blended and by revenue line)" + - "Default Rate / Fraud Loss Rate (as applicable)" + - "Cost-to-Income Ratio" + - section_name: "Revenue Composition and Regulatory Exposure" + placement: "after:Fintech Metrics Dashboard" + description: "Breakdown of revenue by regulatory exposure — critical for investor risk assessment." + fields: + - "Regulated revenue (% of total): interchange, NIM, regulated fees" + - "Unregulated revenue (% of total): subscription, platform, data products" + - "Revenue lines subject to pending regulatory changes" + - "Revenue concentration in single revenue type" + - section_name: "Compliance Cost Structure" + placement: "after:CAC Payback Period" + description: "Regulatory compliance costs broken out from general operating expenses." + fields: + - "KYC/onboarding cost per customer" + - "Ongoing compliance cost per customer per year (transaction monitoring, KYC refresh, reporting)" + - "Total compliance cost as % of revenue" + - "Compliance cost trajectory (increasing or decreasing as % of revenue)" + sections_to_remove: [] + benchmark_references: ["tpv", "take-rate", "net-interest-margin", "cac", "ltv", "gross-margin", "regulatory-compliance-cost", "kyc-cost-per-customer", "default-rate", "fraud-loss-rate", "cost-to-income-ratio"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech investor updates must include regulatory status alongside financial metrics. Investors in regulated businesses expect proactive disclosure of regulatory developments, compliance milestones, and any regulatory interactions." + field_changes: + - field: "Financial highlights" + sector_label: "Fintech KPIs" + sector_guidance: "Report by sub-sector: Payments (TPV, take rate, transaction volume, net revenue). Lending (origination volume, NIM, default rate, portfolio quality). Neobanking (MAU, deposits, ARPU, NRR). Wealthtech (AUM, net flows, management fee revenue). Present current month, prior month, and trend." + - field: "Key metrics" + sector_label: "Operating and Compliance Metrics" + sector_guidance: "Include both commercial metrics (new customers, CAC, NRR) and compliance metrics (KYC conversion rate, fraud rate, regulatory compliance cost). The inclusion of compliance metrics signals sophistication to fintech investors." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include regulatory wins alongside commercial wins: license approvals, successful regulatory examinations, compliance certifications (SOC 2, PCI-DSS), banking partner expansions. Regulatory milestones are investment milestones in fintech." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Proactively disclose regulatory challenges: pending regulatory changes, examination findings, compliance infrastructure gaps, banking partner issues. Investors prefer proactive disclosure over surprises." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific. Fintech-relevant asks: introductions to banking partners, regulatory counsel, compliance technology vendors, or industry regulators. Also: feedback on regulatory strategy or capital planning." + sections_to_add: + - section_name: "Regulatory Status" + placement: "after:Fintech KPIs" + description: "Mandatory section for fintech investor updates — regulatory developments and compliance standing." + fields: + - "License status (current, pending applications, renewals)" + - "Regulatory interactions (examinations, inquiries, guidance received)" + - "Banking partner relationship status" + - "Notable regulatory changes affecting the business" + - section_name: "Cash and Capital Position" + placement: "after:Regulatory Status" + description: "Cash position and regulatory capital (if applicable)." + fields: + - "Cash balance" + - "Monthly burn rate" + - "Months of runway" + - "Regulatory capital ratio (if bank-chartered or holding customer funds)" + sections_to_remove: [] + benchmark_references: ["tpv", "take-rate", "net-interest-margin", "monthly-active-users", "regulatory-compliance-cost"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech competitive analysis must include regulatory barriers to entry, big tech threat assessment, and the impact of open banking mandates on competitive dynamics. The competitive map must position regulatory advantages (licenses, charters, compliance infrastructure) as defensibility factors alongside product and technology." + field_changes: + - field: "Competitor overview" + sector_label: "Competitive Map with Regulatory Positioning" + sector_guidance: "Map competitors on a matrix: X-axis = customer segment (consumer to enterprise), Y-axis = regulatory depth (operating through partners to holding own charter). Position each competitor with: estimated volume, funding, license status, and banking partner(s). Include big tech entries (Apple, Google) and traditional bank digital offerings." + - field: "Competitive advantages" + sector_label: "Defensibility Analysis (Including Regulatory Moat)" + sector_guidance: "Assess defensibility along fintech-specific dimensions: regulatory moat (licenses, charter, compliance infrastructure), data advantage (transaction data, credit data), network effects (two-sided marketplace dynamics, embedded distribution), banking partner quality, and trust/brand (NPS, FDIC insurance, security certifications)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize: (1) Peer fintechs — same sub-sector, same regulatory pathway. (2) Big tech — Apple, Google, Amazon entering with distribution advantage. (3) Traditional banks — digital subsidiaries and partnerships. (4) Regulatory change — open banking mandates enabling new competitors, new charter types creating new entrants. (5) Cross-border competitors — international fintechs entering the US market (Revolut, Wise)." + sections_to_add: + - section_name: "Regulatory Landscape Impact" + placement: "after:Threat Vectors" + description: "How current and pending regulation shapes the competitive landscape." + fields: + - "Current regulatory framework and its competitive implications" + - "Pending regulatory changes that will alter competitive dynamics" + - "Open banking mandate impact on data-based competitive advantages" + - "Regulatory barriers protecting the company's position" + - section_name: "Big Tech Threat Assessment" + placement: "after:Regulatory Landscape Impact" + description: "Specific assessment of big tech financial services entries." + fields: + - "Active big tech financial products in the company's space" + - "Announced or rumored big tech financial services initiatives" + - "The company's defensibility against big tech entry (niche depth, regulatory advantage, relationship density)" + sections_to_remove: [] + benchmark_references: ["take-rate", "cac", "monthly-active-users", "regulatory-compliance-cost"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech pitch decks must include a dedicated regulatory strategy slide — investors evaluate regulatory risk and regulatory moat as primary investment criteria. The deck must address license status, compliance infrastructure, banking partner stability, and regulatory trajectory." + field_changes: + - field: "Market opportunity" + sector_label: "Market Opportunity" + sector_guidance: "Present TAM/SAM/SOM with fintech-specific methodology: (target customers) x (revenue per customer including cross-sell trajectory). Include the regulatory addressable market — the portion of the market the company can legally serve given its current licensing. Address regulatory tailwinds (open banking, embedded finance) and headwinds (fee caps, new compliance requirements)." + - field: "Business model" + sector_label: "Fintech Business Model" + sector_guidance: "Cover: revenue model (interchange, NIM, fees, subscription), regulatory structure (licenses held, banking partner arrangement, charter strategy), unit economics by revenue line, and the cross-sell/expansion revenue mechanism. Separate regulated and unregulated revenue." + - field: "Traction" + sector_label: "Fintech Traction Metrics" + sector_guidance: "Dedicated slide with sub-sector-appropriate metrics: TPV/origination volume/AUM trajectory, net revenue and growth rate, MAU and engagement, NRR, gross margin, and regulatory milestones. This slide is the most scrutinized in any fintech pitch." + sections_to_add: + - section_name: "Regulatory Strategy Slide" + placement: "after:Fintech Business Model" + description: "Mandatory slide for fintech fundraising — investors require clarity on regulatory positioning." + fields: + - "Current license status (licenses held, jurisdictions covered)" + - "Regulatory structure (banking partner, own charter, or hybrid)" + - "Compliance infrastructure (team, technology, processes)" + - "Regulatory roadmap (charter application timeline, license expansion plan)" + - "Regulatory risk mitigation (banking partner diversification, compliance investment plan)" + - section_name: "Unit Economics Slide" + placement: "after:Fintech Traction Metrics" + description: "Fintech-specific unit economics with regulatory cost transparency." + fields: + - "LTV:CAC ratio (including KYC costs in CAC)" + - "Revenue per customer by product line" + - "Gross margin by revenue type (regulated vs. unregulated)" + - "Compliance cost per customer and as % of revenue" + - "For lending: default rate, provision rate, risk-adjusted NIM" + sections_to_remove: [] + benchmark_references: ["tpv", "take-rate", "net-interest-margin", "cac", "ltv", "gross-margin", "regulatory-compliance-cost"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "A fintech strategic one-pager must anchor analysis in the regulatory landscape alongside commercial strategy. Regulatory positioning is a strategic variable, not an appendix item." + field_changes: + - field: "Strategic position" + sector_label: "Fintech Strategic Position" + sector_guidance: "Frame position in fintech terms: sub-sector positioning, regulatory moat strength, competitive differentiation (product, distribution, compliance, data), banking partner or charter status, and cross-sell breadth. Include the company's position on the embedded-vs-standalone spectrum." + - field: "Key metrics" + sector_label: "Fintech Health Metrics" + sector_guidance: "Core metrics: Net Revenue + growth rate, NRR, LTV:CAC (inclusive of compliance costs), Gross Margin (by revenue line), Regulatory Compliance Cost (% of revenue), and sub-sector-specific KPI (default rate for lending, fraud rate for payments, AUM for wealthtech). Compare each to stage-appropriate benchmarks." + sections_to_add: + - section_name: "Regulatory Moat Assessment" + placement: "end" + description: "Assessment of the company's regulatory competitive advantage." + fields: + - "License portfolio and coverage (% of addressable market currently licensable)" + - "Compliance infrastructure maturity vs. competitors" + - "Regulatory relationship quality (examination history, enforcement record)" + - "Charter strategy and timeline (if pursuing direct charter)" + sections_to_remove: [] + benchmark_references: ["take-rate", "net-revenue-retention", "gross-margin", "regulatory-compliance-cost"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech market sizing must account for regulatory addressable market — the portion of the total market the company can serve given its licensing status. Regulatory changes can expand or contract the addressable market overnight." + field_changes: + - field: "Total addressable market" + sector_label: "TAM / SAM / SOM (Regulatory-Adjusted)" + sector_guidance: "Present TAM with regulatory adjustment: total market opportunity x percentage addressable under current licensing x regulatory probability factor for markets requiring new licenses. Include the regulatory expansion opportunity — the incremental SAM available if pending license applications are approved." + - field: "Market dynamics" + sector_label: "Fintech Market Dynamics" + sector_guidance: "Address: regulatory trajectory (tightening, loosening, transforming), competitive density by sub-sector, big tech entry risk, open banking impact, embedded finance opportunity, and the digital adoption curve for the target customer segment." + sections_to_add: + - section_name: "Regulatory Market Dynamics" + placement: "end" + description: "How regulation shapes the market opportunity." + fields: + - "Current regulatory framework and its impact on market structure" + - "Pending regulatory changes and their market impact (expansion or contraction)" + - "International regulatory comparison (markets with favorable regulation for expansion)" + - "Regulatory moat — how compliance requirements create barriers that protect market share" + sections_to_remove: [] + benchmark_references: ["tpv", "monthly-active-users", "regulatory-compliance-cost"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech due diligence is dominated by regulatory verification. Investors must verify license status, compliance infrastructure, banking partner stability, audit findings, enforcement history, and the regulatory risk profile. This is the most fintech-divergent template — regulatory DD items exceed commercial DD items." + field_changes: + - field: "Financial review" + sector_label: "Fintech Financial and Regulatory Verification" + sector_guidance: "Verify: revenue decomposition by type (interchange, NIM, fees, subscription), compliance cost allocation methodology, credit loss provisioning (for lending), regulatory capital adequacy (for charter holders), and banking partner financial terms. Request: audited financials, regulatory examination reports, and compliance audit results." + - field: "Operational review" + sector_label: "Operations, Compliance, and Risk Review" + sector_guidance: "Review: compliance program documentation, BSA/AML program effectiveness, KYC processes and false positive rates, transaction monitoring system capability, SAR filing history and timeliness, regulatory reporting accuracy, and data security posture. Request: compliance audit reports, regulatory examination findings, and banking partner oversight documentation." + sections_to_add: + - section_name: "Regulatory Due Diligence" + placement: "before:Fintech Financial and Regulatory Verification" + description: "Comprehensive regulatory review — the most critical DD section for fintech investments." + fields: + - "License inventory (type, jurisdiction, status, renewal dates)" + - "Regulatory examination history (findings, MRAs, enforcement actions)" + - "Banking partner(s): identity, relationship tenure, contract terms, termination provisions" + - "BSA/AML compliance program assessment" + - "Consumer protection compliance (UDAP/UDAAP, TILA, ECOA, FCRA as applicable)" + - "Data privacy compliance (GLBA, GDPR, CCPA)" + - "PCI-DSS compliance status (if handling card data)" + - "SOC 2 Type II report review" + - "Fair lending analysis (for lending companies)" + - "Pending or threatened regulatory actions" + - section_name: "Credit Risk Review (Lending Companies)" + placement: "after:Regulatory Due Diligence" + description: "Lending-specific due diligence." + fields: + - "Vintage analysis (default rates by origination cohort)" + - "Credit model validation and back-testing results" + - "Portfolio concentration analysis (geography, product, borrower type)" + - "Stress test results (recession scenario impact on portfolio)" + - "Warehouse facility terms and covenants" + - "Securitization history and performance" + sections_to_remove: [] + benchmark_references: ["default-rate", "regulatory-compliance-cost", "net-interest-margin", "fraud-rate", "capital-adequacy-ratio"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not fintech-specific. Standard venture capital cap table formats apply." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech decision rationale documentation must include regulatory impact assessment as a standard section. Every significant decision in fintech has regulatory implications that should be documented." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Including Regulatory Factors)" + sector_guidance: "Include regulatory considerations alongside commercial factors: how regulation constrains the options, whether the decision requires regulatory approval or notification, and the regulatory risk of each alternative." + sections_to_add: + - section_name: "Regulatory Impact Assessment" + placement: "end" + description: "Assessment of regulatory implications of the decision." + fields: + - "Regulatory requirements triggered by this decision" + - "License or approval requirements" + - "Compliance infrastructure changes needed" + - "Regulatory risk level of each alternative considered" + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Fintech exit scenarios are governed by regulatory approval requirements. Bank acquisitions require OCC/FDIC/Fed approval. Insurance company acquisitions require state insurance commissioner approval. Any change of control of a licensed financial entity triggers regulatory review. Valuation multiples vary dramatically by sub-sector and regulatory structure." + field_changes: + - field: "Valuation methodology" + sector_label: "Fintech Valuation Framework" + sector_guidance: "Fintech valuations depend on sub-sector: payments companies trade on revenue multiples (10-25x for high-growth); lending companies trade on book value or earnings multiples (lower than payments due to credit risk); neobanks trade on customer multiples or revenue multiples depending on monetization stage; wealthtech trades on AUM-based multiples. Regulatory status (charter vs. partner model) significantly affects multiples — charter holders command premiums." + - field: "Potential acquirers" + sector_label: "Fintech Acquirer Landscape" + sector_guidance: "Categorize: (1) Strategic fintech acquirers (larger fintechs acquiring capability or customer base). (2) Bank acquirers (traditional banks acquiring fintech technology and customer relationships — requires regulatory approval). (3) Big tech acquirers (platform companies acquiring financial services capability — faces intense regulatory scrutiny). (4) PE acquirers (financial services-focused PE firms). Note: change of control of licensed entities requires regulatory approval that can take 6-18 months." + sections_to_add: + - section_name: "Regulatory Exit Requirements" + placement: "after:Fintech Acquirer Landscape" + description: "Regulatory approvals required for exit transactions." + fields: + - "Regulatory approvals required for change of control (by license type)" + - "Expected regulatory approval timeline" + - "License portability (which licenses transfer to the acquirer, which must be re-obtained)" + - "Regulatory conditions that could be imposed on the acquisition" + sections_to_remove: [] + benchmark_references: ["tpv", "net-interest-margin", "aum", "gross-margin"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Fintech board meetings must include regulatory standing as a first-class agenda item alongside financial and operational performance. Board members have fiduciary responsibility for regulatory compliance, and regulators expect board-level oversight of compliance programs." + field_changes: + - field: "Financial summary" + sector_label: "Fintech Financial Dashboard" + sector_guidance: "Present sub-sector-appropriate financial metrics: revenue by line (interchange, NIM, fees, subscription), gross margin by revenue type, compliance cost trend, and for lending — credit quality summary (default rate, provision rate, portfolio composition). Compare to plan and prior quarter." + - field: "Strategic priorities" + sector_label: "Strategic Priorities and Regulatory Roadmap" + sector_guidance: "Report progress against OKRs with compliance milestones explicitly included. Present the regulatory roadmap alongside the product roadmap — license applications, charter strategy, compliance technology investment." + - field: "Risks" + sector_label: "Risk Dashboard (Including Regulatory Risk)" + sector_guidance: "Mandatory risk categories for fintech board review: (1) Regulatory risk — pending regulations, examination findings, enforcement environment. (2) Credit risk — portfolio quality, concentration, stress test results (for lending). (3) Fraud risk — fraud rate trends, loss rate, detection system effectiveness. (4) Banking partner risk — partner stability, relationship health, concentration. (5) Operational risk — compliance backlog, system availability, incident history. (6) Competitive risk — big tech entry, regulatory-enabled competition." + sections_to_add: + - section_name: "Compliance Standing Report" + placement: "before:Fintech Financial Dashboard" + description: "Mandatory section for fintech board materials — board must demonstrate oversight of compliance program." + fields: + - "Overall compliance program status (Green/Yellow/Red)" + - "License status (current, pending, renewals due)" + - "Regulatory examination update (recent findings, remediation progress)" + - "BSA/AML program metrics (alert volume, SAR filing timeliness, backlog)" + - "Consumer complaint trends (CFPB, state regulators, BBB)" + - "Compliance staffing (vacancies, key position changes)" + - section_name: "Regulatory Change Tracker" + placement: "after:Compliance Standing Report" + description: "Tracking of regulatory changes that affect the business." + fields: + - "Pending regulations with expected impact (high/medium/low)" + - "Recently enacted regulations and compliance timeline" + - "Industry enforcement trends relevant to the company" + - "Regulatory advocacy activities (comment letters, trade association participation)" + - section_name: "Audit Findings Summary" + placement: "after:Regulatory Change Tracker" + description: "Internal and external audit findings requiring board awareness." + fields: + - "Open audit findings by severity (critical, high, medium, low)" + - "Remediation progress on prior findings" + - "Upcoming audits and examinations" + sections_to_remove: [] + benchmark_references: ["regulatory-compliance-cost", "default-rate", "fraud-rate", "gross-margin", "net-revenue-retention"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Fintech board agendas must allocate dedicated time for compliance reporting. Regulators examine board minutes for evidence of compliance oversight — the agenda must demonstrate that the board allocates meaningful time to regulatory matters." + field_changes: + - field: "Agenda items" + sector_label: "Fintech Board Agenda" + sector_guidance: "Standard fintech board agenda: (1) Compliance standing report — 15 min (presented by CCO, not CEO — regulators expect independent compliance reporting to the board). (2) Financial and operating metrics — 15 min (pre-read, discussion only). (3) Strategic topic deep-dive — 25 min (rotate: regulatory strategy, product, credit risk, GTM, partnerships). (4) Risk dashboard review — 10 min. (5) CEO asks — 10 min. (6) Executive session — 15 min. Total: 90 minutes. NOTE: The compliance standing report MUST be a standing agenda item, not an occasional add-on — regulators review board minutes for compliance oversight evidence." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Fintech risk assessment must include regulatory risk as the first dimension — not a secondary consideration. The risk categories for fintech are structurally different from generic businesses, with credit risk, fraud risk, regulatory risk, and banking partner risk as primary categories." + field_changes: + - field: "Risk categories" + sector_label: "Fintech Risk Categories" + sector_guidance: "Fintech-specific risk taxonomy (all mandatory): (1) Regulatory risk — enforcement environment, pending regulations, examination findings, license risk. (2) Credit risk — portfolio quality, concentration, stress performance, underwriting model accuracy (for lending). (3) Fraud risk — fraud rate trends, loss rate, detection effectiveness, false positive impact. (4) Banking partner risk — partner stability, regulatory standing, concentration, contract terms. (5) Operational risk — system availability, compliance process backlog, key person dependency. (6) Cybersecurity risk — data breach exposure, penetration test results, incident response readiness. (7) Competitive risk — big tech entry, regulatory-enabled competition, rate/fee competition." + sections_to_add: + - section_name: "Regulatory Risk Deep Dive" + placement: "before:Fintech Risk Categories" + description: "Detailed regulatory risk assessment — the primary risk dimension for fintech." + fields: + - "Current regulatory enforcement environment (agency priorities, recent actions against peers)" + - "Pending regulatory changes and their risk rating" + - "Examination preparation status and timeline" + - "Regulatory capital adequacy (if applicable)" + - "License renewal status and risk" + - section_name: "Credit Risk Summary (Lending Companies)" + placement: "after:Fintech Risk Categories" + description: "Lending-specific risk metrics." + fields: + - "Default rate by vintage (trend analysis)" + - "Portfolio concentration (geography, product, borrower type)" + - "Stress test results (mild recession, severe recession scenarios)" + - "Provision adequacy (actual losses vs. reserved amounts)" + - section_name: "Banking Partner Risk Assessment" + placement: "after:Credit Risk Summary (Lending Companies)" + description: "Assessment of banking partner concentration and stability." + fields: + - "Banking partner(s) and relationship health" + - "Partner regulatory standing (recent examinations, enforcement actions)" + - "Concentration risk (single partner vs. multiple)" + - "Contingency plan for partner disruption" + sections_to_remove: [] + benchmark_references: ["default-rate", "fraud-rate", "fraud-loss-rate", "regulatory-compliance-cost", "capital-adequacy-ratio"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Change initiatives in fintech must include regulatory impact assessment. Changes to products, pricing, technology, or organizational structure may trigger regulatory notification requirements, license amendments, or compliance program changes." + field_changes: + - field: "Proposed change" + sector_label: "Proposed Change and Regulatory Impact" + sector_guidance: "Describe the change AND its regulatory implications: does this change require regulatory notification, license amendment, or compliance program modification? Has regulatory counsel reviewed the proposal? What is the compliance implementation timeline?" + sections_to_add: + - section_name: "Regulatory Impact Assessment" + placement: "end" + description: "Assessment of regulatory requirements triggered by the proposed change." + fields: + - "Regulatory notifications required" + - "License or compliance program changes needed" + - "Regulatory counsel sign-off status" + - "Compliance implementation timeline" + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Fintech compensation must benchmark against both technology and financial services markets. Compliance roles must be benchmarked against banking compensation, not tech compensation — under-paying compliance talent relative to the banking market creates retention risk in the highest-consequence function." + field_changes: + - field: "Compensation benchmarks" + sector_label: "Fintech Compensation Benchmarks" + sector_guidance: "Benchmark by function against the appropriate market: technology roles (engineering, product, design) benchmarked against tech companies; compliance, risk, and legal roles benchmarked against banking and financial services (higher base, lower equity). The BSA officer and CCO compensation should be competitive with bank equivalents — under-compensation creates retention risk that regulators view as a red flag." + sections_to_add: + - section_name: "Compliance Team Compensation Assessment" + placement: "end" + description: "Specific compensation assessment for compliance-critical roles." + fields: + - "BSA officer / CCO compensation vs. banking market median" + - "Compliance team compensation vs. attrition rate" + - "Key compliance role vacancies and time-to-fill" + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "This is the most critical board template for fintech — it must be comprehensive, detailed, and presented by the CCO with direct board access. Regulators examine this document during examinations to verify board-level compliance oversight." + field_changes: + - field: "Regulatory landscape" + sector_label: "Fintech Regulatory Landscape" + sector_guidance: "Cover all applicable regulatory frameworks: BSA/AML (FinCEN, state regulators), consumer protection (CFPB UDAP/UDAAP, TILA, ECOA, FCRA), data privacy (GLBA, GDPR, CCPA), payment regulation (PCI-DSS, card network rules, state money transmitter), lending regulation (state usury laws, TILA, HMDA if applicable), securities regulation (SEC, FINRA if applicable), banking regulation (OCC, FDIC, Fed if chartered). For each: current compliance status, recent changes, and upcoming requirements." + sections_to_add: + - section_name: "BSA/AML Program Status" + placement: "after:Fintech Regulatory Landscape" + description: "Detailed BSA/AML compliance reporting — the most examined compliance area." + fields: + - "SAR filing volume and timeliness (% filed within 30-day requirement)" + - "CTR filing volume and accuracy" + - "Transaction monitoring alert volume, disposition rate, and backlog" + - "KYC program metrics (CDD completion rate, EDD completion rate, refresh status)" + - "OFAC/sanctions screening effectiveness" + - section_name: "Consumer Protection Status" + placement: "after:BSA/AML Program Status" + description: "Consumer protection compliance — increasingly the focus of CFPB enforcement." + fields: + - "Consumer complaint volume and resolution rate" + - "Fee transparency and UDAP/UDAAP compliance assessment" + - "Fair lending analysis results (for lending companies)" + - "Marketing and advertising compliance review status" + - section_name: "Examination and Audit Calendar" + placement: "end" + description: "Upcoming regulatory examinations and audit schedule." + fields: + - "Scheduled regulatory examinations (date, scope, examiner)" + - "Internal audit calendar and status" + - "External audit schedule (SOC 2, PCI-DSS, financial audit)" + - "Examination preparation readiness assessment" + sections_to_remove: [] + benchmark_references: ["regulatory-compliance-cost", "fraud-rate", "kyc-conversion-rate"] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "CEO succession in fintech has a regulatory dimension: the successor must be acceptable to regulators. For bank-chartered fintechs, the OCC/FDIC must approve changes in control and key management positions. The successor must have financial services regulatory credibility." + field_changes: + - field: "Successor criteria" + sector_label: "Successor Criteria (Including Regulatory Considerations)" + sector_guidance: "Include regulatory credibility as a succession criterion: the successor must be capable of managing regulatory relationships, presenting to examiners, and maintaining the company's compliance culture. For charter holders, regulators must approve management changes — the successor's regulatory standing affects approval timeline." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech action plans must include compliance checkpoints — any action that affects products, customers, or data must be reviewed for regulatory implications." + field_changes: + - field: "Success metrics" + sector_label: "Fintech KPI Targets" + sector_guidance: "Define success using fintech-appropriate metrics: TPV impact, take rate improvement, default rate reduction, fraud rate improvement, KYC conversion improvement, compliance cost optimization. Every action plan that touches customer-facing products or data must include a compliance review checkpoint." + sections_to_add: + - section_name: "Compliance Review Checkpoint" + placement: "end" + description: "Mandatory compliance review for actions affecting products, customers, or data." + fields: + - "Does this action require compliance review? (Yes/No)" + - "Compliance reviewer and sign-off date" + - "Regulatory implications identified" + sections_to_remove: [] + benchmark_references: [] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech initiative briefs must include regulatory feasibility assessment and compliance implementation timeline alongside commercial projections." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected Fintech Impact" + sector_guidance: "Quantify impact on fintech metrics: revenue per customer, take rate, default rate, fraud rate, KYC conversion, compliance cost, or customer acquisition. Include the regulatory implementation timeline — the initiative cannot launch until compliance requirements are met." + - field: "Resource requirements" + sector_label: "Resource Requirements (Including Compliance)" + sector_guidance: "Include compliance resources alongside engineering and commercial resources: compliance review hours, legal counsel hours, any regulatory filings or notifications required, and the compliance team's capacity to support the initiative." + sections_to_add: + - section_name: "Regulatory Feasibility Assessment" + placement: "after:Expected Fintech Impact" + description: "Assessment of regulatory requirements and timeline for the initiative." + fields: + - "Does this initiative require new licenses, license amendments, or regulatory notifications?" + - "Compliance team assessment of regulatory feasibility" + - "Regulatory implementation timeline (may differ from product timeline)" + - "Compliance sign-off required before launch (Y/N, responsible person)" + sections_to_remove: [] + benchmark_references: ["regulatory-compliance-cost"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech project kickoffs must include compliance as a workstream with explicit deliverables and a compliance sign-off gate before launch." + field_changes: + - field: "Success criteria" + sector_label: "Success Metrics and Compliance Gates" + sector_guidance: "Define 2-3 fintech metrics this project will move, plus explicit compliance gates: (1) Compliance review completed, (2) Regulatory requirements identified and addressed, (3) Required disclosures and documentation prepared, (4) Compliance sign-off obtained before customer-facing launch." + sections_to_add: + - section_name: "Compliance Workstream" + placement: "end" + description: "Dedicated compliance deliverables for the project." + fields: + - "Compliance review scope and timeline" + - "Regulatory requirements applicable to this project" + - "Customer disclosures or terms changes needed" + - "Compliance sign-off gate (date, responsible person)" + sections_to_remove: [] + benchmark_references: [] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech hiring scorecards must include regulatory literacy assessment for all senior roles and specialized compliance competency assessment for compliance, risk, and legal roles." + field_changes: + - field: "Required competencies" + sector_label: "Fintech-Specific Competencies" + sector_guidance: "For all senior roles: financial services regulatory awareness, comfort with compliance-constrained decision-making, and understanding of the trust dynamics unique to financial services. For compliance roles: BSA/AML expertise, familiarity with relevant regulations (UDAP/UDAAP, TILA, ECOA, FCRA), examination experience, and regulatory relationship management. For product roles: experience designing compliant products, understanding of regulatory constraints on UX. Benchmark compliance talent against banking market, not tech market." + sections_to_add: + - section_name: "Regulatory Credentials Assessment" + placement: "end" + description: "For compliance, risk, and legal roles." + fields: + - "Relevant regulatory certifications (CAMS, CRCM, CFE)" + - "Examination experience (types of exams, roles during exams)" + - "Regulatory relationship experience" + - "Financial services regulatory background check requirements" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech incident postmortems must include regulatory impact assessment and determine whether the incident triggers regulatory notification obligations. Data breaches, service outages affecting customer fund access, and fraud events may require notification to regulators, banking partners, and customers under specific timelines." + field_changes: + - field: "Impact assessment" + sector_label: "Customer, Regulatory, and Business Impact" + sector_guidance: "Quantify: customers affected, financial impact (funds at risk, transactions delayed), duration, SLA breaches. CRITICAL: determine whether the incident triggers regulatory notification requirements — data breach notifications (state breach laws, GLBA), banking partner notification (per partnership agreement), and customer notification requirements. Document the notification timeline and status." + sections_to_add: + - section_name: "Regulatory Notification Assessment" + placement: "after:Customer, Regulatory, and Business Impact" + description: "Assessment of regulatory notification obligations triggered by the incident." + fields: + - "Does this incident trigger data breach notification under state laws or GLBA?" + - "Does this incident require banking partner notification?" + - "Does this incident require regulatory notification (OCC, FDIC, state regulators)?" + - "Notification timeline compliance (were notifications sent within required timeframes?)" + - "CFPB/state AG complaint risk assessment" + sections_to_remove: [] + benchmark_references: ["fraud-rate", "fraud-loss-rate"] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Sprint and project retrospectives follow standard agile practices that are not fintech-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech team health must include compliance team health as a distinct dimension — compliance team burnout, understaffing, and cultural marginalization are organizational risks with regulatory consequences." + field_changes: + - field: "Health indicators" + sector_label: "Fintech Team Health Indicators" + sector_guidance: "Include fintech-specific indicators: growth-compliance alignment score (how well do product/growth and compliance teams collaborate?), compliance team workload and morale (alert backlog, overtime hours, burnout indicators), cross-functional regulatory literacy (do non-compliance teams understand basic regulatory constraints?), and incident response readiness." + sections_to_add: + - section_name: "Compliance Team Health" + placement: "end" + description: "Dedicated compliance team health assessment — critical for regulated businesses." + fields: + - "Compliance team headcount vs. workload (alerts per analyst, reviews per specialist)" + - "Compliance team attrition rate and open positions" + - "Growth-compliance tension indicator (collaborative vs. adversarial relationship)" + - "Compliance team access to leadership (can the CCO reach the board directly?)" + sections_to_remove: [] + benchmark_references: ["regulatory-compliance-cost"] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech culture and values documentation should explicitly address the company's commitment to regulatory compliance, ethical financial practices, and customer trust as cultural values — not just business requirements." + field_changes: + - field: "Core values" + sector_label: "Core Values (Including Compliance Culture)" + sector_guidance: "Include compliance and trust as explicit cultural values, not implicit expectations. Example values: 'We treat compliance as a competitive advantage, not a cost center,' 'We prioritize customer financial wellbeing over revenue extraction,' 'We are transparent with customers, regulators, and each other.' These cultural statements set expectations and are evidence of compliance culture during regulatory examinations." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning is not sector-specific, though fintech offsites should include compliance and regulatory strategy as a standard topic." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Fintech role descriptions must include regulatory responsibilities and financial services experience requirements. All customer-facing and product roles should include compliance awareness as a competency." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities (Including Regulatory)" + sector_guidance: "For each role, specify regulatory responsibilities: compliance with applicable financial regulations, cooperation with compliance team on reviews and audits, understanding of regulatory constraints on the role's activities. For compliance roles: specify regulatory designations (BSA officer, compliance officer) and reporting lines (direct board access for CCO)." + - field: "Required experience" + sector_label: "Fintech Experience Requirements" + sector_guidance: "Specify: financial services or fintech experience required, regulatory literacy expectations, and any required certifications (CAMS for AML roles, Series 7/66 for investment roles, CRCM for compliance roles)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A fintech CEO's weekly review must include compliance and regulatory status alongside financial and operational metrics. The CEO is ultimately responsible for the company's regulatory standing." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly Fintech Dashboard" + sector_guidance: "Review weekly: net revenue and WoW change, transaction volume or origination volume, new customers and KYC conversion rate, fraud alerts and resolution, compliance team workload indicators (alert backlog, SAR filing pipeline), cash balance and regulatory capital. Monthly metrics (NRR, default rate, compliance cost % of revenue) should be reviewed monthly." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Include at least one compliance item weekly: regulatory relationship maintenance, compliance program review, or audit preparation. In fintech, neglecting compliance in the CEO's weekly priorities communicates to the organization that compliance is not a leadership priority." + sections_to_add: + - section_name: "Regulatory Signal Review" + placement: "after:Weekly Fintech Dashboard" + description: "Weekly review of regulatory signals." + fields: + - "Regulatory developments this week (new rules, enforcement actions against peers, guidance)" + - "Banking partner communications or concerns" + - "Compliance team escalations or flags" + sections_to_remove: [] + benchmark_references: ["tpv", "fraud-rate", "kyc-conversion-rate"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech decision journals should explicitly capture the regulatory considerations and constraints that shaped each decision — this record becomes valuable evidence during regulatory examinations." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Including Regulatory Factors)" + sector_guidance: "Record: the commercial metrics that informed the decision, the regulatory constraints that shaped the options, whether compliance counsel was consulted, and the regulatory risk assessment for the chosen option. This documentation is evidence of sound decision-making during regulatory examinations." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech annual reviews should assess compliance program maturity and regulatory relationship health alongside commercial performance." + field_changes: + - field: "Year in review" + sector_label: "Fintech Year in Review" + sector_guidance: "Assess across all dimensions: revenue growth by line, customer metrics (MAU, NRR, ARPU), credit quality (for lending), fraud performance, compliance program milestones (licenses obtained, examinations passed, certifications achieved), regulatory relationship health, and team growth." + - field: "Next year goals" + sector_label: "Next Year Fintech Targets" + sector_guidance: "Set targets across all fintech dimensions: revenue targets by line, customer growth, unit economics improvement, compliance program maturity goals (target compliance cost % of revenue, automation goals), licensing expansion, and regulatory milestones. Include the regulatory capital plan for charter holders." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["tpv", "net-revenue-retention", "gross-margin", "regulatory-compliance-cost", "default-rate"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech stakeholder maps must include regulators, banking partners, and card networks as primary stakeholder categories — these relationships are as consequential as investor and customer relationships." + field_changes: + - field: "Stakeholder categories" + sector_label: "Fintech Stakeholder Ecosystem" + sector_guidance: "Include: Regulators (federal, state, examination teams — by name if possible), Banking Partners (relationship managers, compliance contacts, executive sponsors), Card Networks (relationship managers, compliance contacts), Investors (lead, follow-on, board members), Customers (segments, key accounts, community), Partners (technology, distribution, identity providers), Team (executives, compliance leadership, key ICs), and Industry (trade associations, regulatory advocacy groups)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech negotiation prep must include regulatory constraint analysis — understanding which terms are negotiable commercially and which are constrained by regulation." + field_changes: + - field: "Negotiation type" + sector_label: "Fintech Negotiation Context" + sector_guidance: "Classify: banking partner negotiation (terms, compliance allocation, revenue share), regulatory negotiation (examination response, consent order terms, no-action letter request), enterprise client deal (compliance requirements, data security addenda, regulatory representations), fundraising (term sheet with regulatory risk provisions), or internal (growth-compliance resource allocation). Each type has distinct fintech-specific dynamics." + - field: "BATNA" + sector_label: "BATNA and Regulatory Constraints" + sector_guidance: "Identify both commercial BATNA and regulatory constraints on alternatives. For banking partner negotiations: alternative BaaS providers, direct charter path. For regulatory negotiations: the alternative to cooperation is enforcement — this fundamentally shapes the negotiation. For enterprise deals: regulatory compliance documentation as leverage (SOC 2, PCI-DSS readiness reduces deal friction)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech founder mental health is affected by sector-specific stressors: the weight of handling other people's money, personal liability for compliance failures, regulatory examination stress, and the existential nature of trust in financial services." + field_changes: + - field: "Stress indicators" + sector_label: "Fintech-Specific Stress Indicators" + sector_guidance: "Include: regulatory anxiety (obsessive worry about compliance failures, examination outcomes, or enforcement actions), personal liability stress (awareness that BSA violations and compliance failures can carry personal criminal liability), trust burden (the psychological weight of being responsible for customer financial wellbeing), banking partner dependency anxiety (fear that partner relationship disruption will halt the business), and the compound stress of simultaneously managing commercial, regulatory, and trust pressures." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Fintech founders should include regulatory literacy and compliance expertise in their learning plans — this is not delegatable knowledge in a regulated industry." + field_changes: + - field: "Learning areas" + sector_label: "Fintech Learning Priorities" + sector_guidance: "Consider fintech-specific learning areas: financial services regulatory framework (BSA/AML, UDAP/UDAAP, applicable state and federal regulations), credit risk management (for lending), payment system economics (interchange, network rules, settlement), compliance program design, regulatory examination preparation, financial modeling for regulated businesses, and the intersection of AI/ML with financial regulation (model risk management, fair lending, explainability requirements)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A fintech founder's advisory network must include regulatory expertise — this is the most consequential advisory gap in fintech leadership." + field_changes: + - field: "Advisor categories" + sector_label: "Fintech Advisory Needs" + sector_guidance: "Map advisors to fintech-specific needs: Regulatory (former regulator, experienced fintech compliance counsel — the single most valuable advisor category in fintech), Banking Relationships (someone who has managed banking partner relationships at scale), Credit Risk (for lending — someone who has managed loan portfolios through credit cycles), Payments (someone who understands interchange economics, card network dynamics, and payment infrastructure), Fintech Operations (someone who has scaled a fintech to 1M+ customers with full compliance), and General Startup (fundraising, team building, strategy)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech QBRs for B2B clients must include compliance support delivered — regulatory assistance is a value-add that justifies premium pricing in financial services." + field_changes: + - field: "Performance summary" + sector_label: "Value Delivered (Including Compliance Value)" + sector_guidance: "Quantify value delivered including compliance dimensions: transactions processed, fraud prevented (dollar value), regulatory reports generated, compliance workload reduced, KYC verifications completed. Financial services clients value compliance efficiency as much as commercial efficiency." + - field: "Account status" + sector_label: "Usage, Compliance, and Engagement Metrics" + sector_guidance: "Present: transaction volume and trends, API uptime and reliability, fraud detection metrics (for payment clients), compliance feature utilization, and support interaction summary." + - field: "Next steps" + sector_label: "Growth and Compliance Roadmap" + sector_guidance: "Identify expansion opportunities AND upcoming compliance requirements the client should prepare for. Proactive regulatory guidance builds trust and justifies premium pricing." + sections_to_add: + - section_name: "Compliance Support Summary" + placement: "after:Value Delivered (Including Compliance Value)" + description: "Summary of compliance value delivered to the client." + fields: + - "Regulatory reports generated or facilitated" + - "Fraud prevented (transaction count and dollar value)" + - "KYC verifications processed (if applicable)" + - "Regulatory changes communicated proactively" + sections_to_remove: [] + benchmark_references: ["fraud-rate", "fraud-loss-rate"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech client onboarding includes compliance requirements that are absent in non-regulated businesses. Clients must complete KYB (Know Your Business) verification, sign regulatory agreements, and integrate compliance-relevant features." + field_changes: + - field: "Getting started steps" + sector_label: "Onboarding Path (Including Compliance Requirements)" + sector_guidance: "Organize: (1) KYB verification (business identity, beneficial ownership, sanctions screening — regulatory requirement before any financial activity), (2) Compliance agreement signing (BSA/AML responsibilities, data handling terms, regulatory representations), (3) Technical integration, (4) Testing and certification, (5) Go-live with compliance monitoring active. Emphasize that KYB is a regulatory requirement, not an obstacle — frame it as a trust-building step." + - field: "Resources" + sector_label: "Resources (Including Compliance Documentation)" + sector_guidance: "Include: API documentation, compliance guide (regulatory responsibilities shared between the platform and the client), security documentation (SOC 2 report, PCI-DSS attestation), and regulatory FAQ (addressing common compliance questions)." + sections_to_add: + - section_name: "Compliance Requirements" + placement: "after:Onboarding Path (Including Compliance Requirements)" + description: "Regulatory requirements that must be completed during onboarding." + fields: + - "KYB verification requirements and documentation needed" + - "Compliance agreements to be signed" + - "Shared compliance responsibilities (what the platform handles, what the client handles)" + - "Ongoing regulatory obligations (reporting, monitoring, data retention)" + sections_to_remove: [] + benchmark_references: ["kyc-conversion-rate"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech proposals must address compliance value alongside commercial value. In financial services, the client's compliance team evaluates the proposal alongside the business team — the proposal must speak to both audiences." + field_changes: + - field: "Pricing" + sector_label: "Investment, ROI, and Compliance Value" + sector_guidance: "Present: transaction pricing (per-transaction, volume-based tiers), platform fees, compliance feature pricing (if separate). Include compliance ROI: reduced compliance costs (automated reporting, reduced manual review), fraud prevention value (dollar losses prevented), and regulatory risk reduction (fewer examination findings). Financial services clients weight compliance value heavily in purchasing decisions." + - field: "Scope" + sector_label: "Implementation Scope (Including Compliance Integration)" + sector_guidance: "Include: technical integration timeline, compliance setup (KYB, regulatory agreements, compliance feature activation), testing and certification phase, and compliance monitoring activation. Note: compliance integration may require client's compliance team involvement." + sections_to_add: + - section_name: "Compliance and Security Credentials" + placement: "end" + description: "Regulatory and security credentials that financial services clients require." + fields: + - "Licenses and regulatory registrations" + - "SOC 2 Type II attestation" + - "PCI-DSS compliance status" + - "Data handling and privacy commitments (GLBA, GDPR, CCPA)" + - "Penetration test results summary" + sections_to_remove: [] + benchmark_references: ["fraud-loss-rate", "kyc-cost-per-customer"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech SLAs must include regulatory compliance commitments alongside standard availability and support commitments. Financial services clients require contractual assurance of regulatory compliance." + field_changes: + - field: "Service levels" + sector_label: "Fintech Service Commitments" + sector_guidance: "Standard fintech SLA components: (1) Transaction processing uptime (99.95% for payment processing — higher than SaaS because transactions involve money), (2) Transaction processing time (real-time for payments, within SLA for lending decisions), (3) Support response time by severity, (4) Compliance service levels (regulatory report delivery timeline, fraud alert response time, KYC verification turnaround). (5) Data handling commitments (encryption, retention, deletion)." + - field: "Remediation" + sector_label: "Credit, Remediation, and Regulatory Notification" + sector_guidance: "Define: service credit structure for SLA breaches, escalation procedures for compliance-affecting outages, mutual notification obligations for regulatory events (either party receiving a regulatory inquiry that affects the other), and termination rights for sustained compliance failures." + sections_to_add: + - section_name: "Regulatory Compliance Commitments" + placement: "after:Fintech Service Commitments" + description: "Contractual compliance commitments — standard in financial services agreements." + fields: + - "Regulatory compliance representations (which regulations the service complies with)" + - "Audit rights (client's right to audit the service provider's compliance)" + - "Regulatory change management (process for adapting to regulatory changes)" + - "Breach notification obligations and timeline" + - "Data handling and GLBA compliance commitments" + sections_to_remove: [] + benchmark_references: [] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech project status updates must track compliance integration milestones alongside technical milestones. A project that is technically complete but not compliance-approved cannot launch." + field_changes: + - field: "Progress summary" + sector_label: "Implementation Progress (Including Compliance Gates)" + sector_guidance: "Track: technical integration progress, compliance integration progress (KYB status, agreement execution, compliance feature setup), testing phase status, and compliance approval status. Highlight any compliance gates that are blocking launch — these are non-negotiable and often on a different timeline than technical work." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech analysis reports for clients should include regulatory context — how regulation affects the analysis and its recommendations." + field_changes: + - field: "Analysis framework" + sector_label: "Analysis Framework (Regulatory Context)" + sector_guidance: "Include regulatory constraints as a dimension of the analysis. Any recommendation must be assessed for regulatory feasibility — a commercially attractive strategy that violates regulations is not a recommendation but a liability." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech case studies must include compliance outcomes alongside commercial outcomes. Financial services buyers evaluate vendors partly on their compliance track record — a case study that demonstrates compliance value is more persuasive than one focused solely on commercial metrics." + field_changes: + - field: "Results" + sector_label: "Quantified Outcomes (Including Compliance)" + sector_guidance: "Include compliance outcomes alongside commercial outcomes: fraud losses prevented, compliance costs reduced, regulatory reports automated, examination findings avoided, and time saved on compliance operations. Financial services buyers value these outcomes at least as highly as revenue or efficiency gains." + - field: "Challenge" + sector_label: "Challenge (Including Regulatory Context)" + sector_guidance: "Include the regulatory dimension of the client's challenge: compliance burden, regulatory risk, examination preparation, or fraud exposure. This helps prospects with similar regulatory pressures see themselves in the story." + sections_to_add: + - section_name: "Compliance Impact" + placement: "after:Quantified Outcomes (Including Compliance)" + description: "Dedicated compliance outcomes section." + fields: + - "Regulatory compliance improvements achieved" + - "Fraud prevention results" + - "Compliance cost impact" + - "Examination or audit outcomes influenced" + sections_to_remove: [] + benchmark_references: ["fraud-loss-rate", "regulatory-compliance-cost"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Fintech partnership memos must address regulatory responsibility allocation — the most consequential and contentious element of fintech partnerships. Every fintech partnership involves regulated activities where compliance responsibility must be explicitly divided." + field_changes: + - field: "Partnership structure" + sector_label: "Fintech Partnership Structure (Including Regulatory Allocation)" + sector_guidance: "Define: partnership type (banking partner, technology integration, embedded finance, distribution), regulatory structure (which party holds relevant licenses, which party performs compliance activities), commercial terms (revenue share, transaction pricing, volume commitments), and governance (joint compliance review cadence, escalation path, audit rights). The regulatory responsibility matrix is the most critical section — it determines who is liable for compliance failures." + sections_to_add: + - section_name: "Regulatory Responsibility Matrix" + placement: "after:Fintech Partnership Structure (Including Regulatory Allocation)" + description: "Explicit allocation of compliance responsibilities between partners — the most critical section of a fintech partnership document." + fields: + - "KYC/CDD responsibility (which party performs identity verification)" + - "Transaction monitoring responsibility (which party monitors for suspicious activity)" + - "SAR filing responsibility (which party files Suspicious Activity Reports)" + - "Regulatory reporting responsibility (by report type and jurisdiction)" + - "Consumer complaint handling responsibility" + - "Audit and examination cooperation obligations" + - "Regulatory change management process" + - section_name: "Partner Risk Assessment" + placement: "after:Regulatory Responsibility Matrix" + description: "Assessment of regulatory risk introduced by the partnership." + fields: + - "Partner's regulatory standing (licenses, examination history, enforcement record)" + - "Concentration risk (dependency on a single partner for regulated activities)" + - "Termination provisions and transition plan" + - "Contingency plan for partner regulatory disruption" + sections_to_remove: [] + benchmark_references: ["regulatory-compliance-cost"] diff --git a/plugins/foreman/content/industry-packs/healthtech/healthtech-benchmarks.yaml b/plugins/foreman/content/industry-packs/healthtech/healthtech-benchmarks.yaml new file mode 100644 index 0000000..b629368 --- /dev/null +++ b/plugins/foreman/content/industry-packs/healthtech/healthtech-benchmarks.yaml @@ -0,0 +1,1562 @@ +# Healthtech Industry Pack — Benchmarks +# +# 24 healthtech-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing growth, clinical validation, +# regulatory, and reimbursement issues in digital health, telemedicine, health SaaS +# (EHR/EMR), clinical decision support, digital therapeutics (DTx), remote patient +# monitoring, health data analytics, genomics platforms, mental health tech, and +# AI-powered diagnostics companies. +# +# Primary data sources: +# - Rock Health Digital Health Funding Reports (2023, 2024, 2025) +# - CB Insights State of Digital Health (2023, 2024) +# - IQVIA Digital Health Trends (2023, 2024) +# - FDA Digital Health Center of Excellence Reports (2023, 2024) +# - Deloitte Life Sciences & Health Care Outlook (2024, 2025) +# - Health System CIO Surveys — CHIME/KLAS (2023, 2024) +# - McKinsey Healthcare Practice Reports (2023, 2024) +# - American Medical Association Digital Health Research (2023, 2024) +# - CMS Innovation Center Evaluation Reports (2023, 2024) +# - Journal of Medical Internet Research — Digital Health Outcomes Meta-Analyses (2023, 2024) +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded healthtech companies at the relevant stage. +# +# PATIENT SAFETY NOTE: Several metrics in this file carry clinical implications. +# Benchmarks involving patient outcomes, clinical validation, and provider adoption +# are not merely business metrics — they reflect the company's capacity to deliver +# safe, effective care. Falling below minimum thresholds on clinical metrics may +# signal risk to patients, not merely risk to the business. + +pack_metadata: + sector: "healthtech" + display_name: "Healthtech" + version: "1.0.0" + description: "Benchmark data for healthtech companies spanning digital health, + telemedicine, health SaaS, clinical decision support, digital therapeutics, + remote patient monitoring, health data analytics, genomics, mental health + tech, and AI-powered diagnostics — with patient safety, clinical validation, + and regulatory compliance as first-class dimensions." + applicable_stages: + - idea + - validation + - early-traction + - growth + - scale + memory_field: "memory.company.sector" + compatible_modes: + - solo-mode + - stoic-mode + - language-mode + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # CLINICAL VALIDATION & REGULATORY METRICS + # ───────────────────────────────────────────── + + - name: "Clinical Validation Stage" + id: "clinical-validation-stage" + category: "product" + definition: "The highest level of clinical evidence the product has achieved, + ranging from internal pilot data to peer-reviewed randomized controlled + trial results and regulatory clearance. This metric defines the company's + credibility with providers, payers, and regulators." + formula: "Categorical: Pilot (internal data) → Observational Study → RCT → + Peer-Reviewed Publication → Regulatory Clearance/Approval" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Pilot data only, no external validation" + signal: "Insufficient evidence to convince health systems, payers, or + regulators. The product is a hypothesis, not a validated intervention. + Sales conversations stall at the clinical evidence question." + below_average: + value: "Single-arm observational study, < 100 patients" + signal: "Early signal but not sufficient for most health system procurement + committees or payer coverage decisions. Useful for generating + interest, not for closing contracts." + average: + value: "Multi-site observational study or single-site RCT, 100-500 patients, + abstract presented at clinical conference" + signal: "Meaningful evidence that supports pilot agreements with health systems. + Payers may consider coverage with conditions. Sufficient for + seed/Series A fundraising from health-focused investors." + good: + value: "Multi-site RCT, 500+ patients, peer-reviewed publication in indexed + journal" + signal: "Strong evidence base that satisfies most health system clinical review + committees. Payer coverage discussions become substantive. Regulatory + submission supported by this level of evidence." + excellent: + value: "Multiple RCTs, published in high-impact journals (NEJM, JAMA, Lancet), + regulatory clearance/approval obtained" + signal: "Gold-standard evidence. Health systems adopt based on evidence alone. + Payers offer reimbursement. The company has a durable competitive moat + built on clinical proof." + stage_notes: + seed: "Pilot data is expected at seed. Investors assess the clinical study + design and the team's ability to execute it, not the results themselves. + A credible study protocol with IRB approval is a meaningful signal." + series_a: "At least one published or conference-presented study is expected. + Series A health investors will evaluate whether the study design is + rigorous enough to support future regulatory and reimbursement claims." + series_b_plus: "Peer-reviewed publications and regulatory milestones are + expected. Without them, the product remains a science project. Clinical + validation is the single strongest moat in healthtech." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "FDA Digital Health Center of Excellence" + year: "2024" + related_metrics: + [ + "clinical-evidence-strength", + "patient-outcomes-improvement", + "regulatory-approval-status" + ] + related_skills: [ "trust-equation", "balanced-scorecard" ] + caveats: "Clinical validation stage is not binary — a strong observational study + in the right patient population may outweigh a weak RCT. The relevance of + each evidence level varies by therapeutic area, regulatory pathway, and + payer requirements." + + - name: "Regulatory Approval Status" + id: "regulatory-approval-status" + category: "product" + definition: "The current status of the product on its regulatory pathway — + pre-submission, submitted, cleared/approved, or exempt. For FDA-regulated + products, this encompasses 510(k) clearance, De Novo classification, PMA + approval, or Breakthrough Device designation. For non-FDA products, this + covers state licensing, CLIA certification, or CE marking." + formula: "Categorical: Not Applicable (wellness) → Pre-Submission → Submitted → + Cleared/Approved" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Product requires regulatory clearance but no submission timeline exists" + signal: "Existential risk. The company is building a product it cannot legally + sell. Every month of development without a regulatory strategy is + potentially wasted." + below_average: + value: "Pre-submission meeting requested or completed; submission 6-12 months + away" + signal: "Regulatory strategy exists but execution has not begun. Investors will + discount the company for regulatory risk. Health systems will not + pilot without a clear pathway." + average: + value: "Submission filed or Breakthrough Device designation obtained; clearance + expected within 6 months" + signal: "Active regulatory engagement. Breakthrough Device designation provides + FDA interaction advantages and accelerated review. Health systems may + begin pilot agreements contingent on clearance." + good: + value: "510(k) cleared or De Novo classified; CE mark obtained for EU market" + signal: "Regulatory barrier crossed. The product can be legally marketed and + sold. This is a major de-risking event that unlocks health system + procurement and payer coverage conversations." + excellent: + value: "PMA approved or multiple regulatory clearances across geographies (FDA + + CE + additional markets)" + signal: "Strongest regulatory position. PMA creates a higher barrier for + competitors. Multi-geography clearance enables global + commercialization." + stage_notes: + seed: "A clear regulatory pathway and classification strategy is expected at + seed. Founders should have completed an FDA pre-submission meeting or + equivalent. Investors assess regulatory literacy as a proxy for + execution capability." + series_a: "Submission filed or clearance obtained is ideal at Series A. The + 2024-2026 funding environment penalizes healthtech companies that have + not de-risked regulatory pathway." + series_b_plus: "Clearance is a prerequisite for Series B in regulated + healthtech. Companies raising at this stage without clearance face + significant valuation compression." + data_sources: + - source: "FDA Digital Health Center of Excellence" + year: "2024" + - source: "IQVIA Digital Health Trends" + year: "2024" + related_metrics: + [ + "clinical-validation-stage", + "time-to-regulatory-clearance", + "regulatory-pathway-cost" + ] + related_skills: [ "scenario-planning", "vuca-framework" ] + caveats: "Not all healthtech products require FDA clearance. Wellness apps, + provider workflow tools, and certain clinical decision support tools may + be exempt under FDA guidance. Misclassifying a regulated product as exempt + is a serious legal and business risk." + + - name: "Patient Outcomes Improvement (%)" + id: "patient-outcomes-improvement" + category: "product" + definition: "The measurable improvement in patient health outcomes attributable + to the product, expressed as a percentage improvement over standard of + care or control group. This is the ultimate measure of whether the product + fulfills its clinical promise." + formula: "(Outcome_intervention - Outcome_control) / Outcome_control x 100, + where outcome is the primary clinical endpoint" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% improvement or not statistically significant" + signal: "The product does not demonstrably improve outcomes. Without measurable + improvement, the value proposition rests on operational efficiency + alone — a weaker position for reimbursement and adoption." + below_average: + value: "5-10% improvement, p < 0.05 in pilot study" + signal: "Modest improvement that may not meet clinical significance thresholds. + Sufficient for internal use cases but unlikely to secure dedicated + reimbursement or change clinical guidelines." + average: + value: "10-20% improvement, p < 0.05 in adequately powered study" + signal: "Clinically meaningful improvement. Sufficient to support health + economic arguments and to interest health system clinical review + committees." + good: + value: "20-35% improvement, replicated across multiple sites" + signal: "Strong clinical impact. Sufficient for guideline inclusion, payer + coverage with dedicated reimbursement codes, and differentiated + positioning against competitors." + excellent: + value: "> 35% improvement, published in high-impact journal with health economic + analysis" + signal: "Transformative clinical impact. The product becomes a standard-of-care + candidate. Payers actively seek to cover it because better outcomes + reduce downstream costs." + stage_notes: + seed: "Outcome data is aspirational at seed. The metric should be defined (what + primary endpoint will be measured) even if results are not yet + available." + series_a: "Preliminary outcome data from pilot studies should be available. Even + directional improvement with a credible study design is valuable." + series_b_plus: "Robust outcome data is required. Health-focused investors at + this stage perform clinical due diligence as rigorous as financial due + diligence." + data_sources: + - source: "Journal of Medical Internet Research — Digital Health Outcomes" + year: "2024" + - source: "IQVIA Digital Health Trends" + year: "2024" + related_metrics: + [ + "clinical-validation-stage", + "clinical-evidence-strength", + "patient-satisfaction-score" + ] + related_skills: [ "balanced-scorecard", "net-promoter-score" ] + caveats: "Outcome improvement varies dramatically by condition, intervention + type, and comparator. A 10% improvement in cancer survival is + transformative; a 10% improvement in appointment scheduling convenience is + trivial. Context is everything." + + - name: "Clinical Evidence Strength (Levels 1-5)" + id: "clinical-evidence-strength" + category: "product" + definition: "A composite rating of the strength and quality of clinical evidence + supporting the product, based on the Oxford Centre for Evidence-Based + Medicine levels. Level 1: systematic reviews of RCTs. Level 2: individual + RCTs. Level 3: controlled cohort studies. Level 4: case series or + poor-quality cohort. Level 5: expert opinion or mechanism-based + reasoning." + formula: "Oxford CEBM Level assignment based on highest-quality study supporting + the product's primary clinical claim" + unit: "ratio" + direction: "lower-is-better" + benchmarks: + poor: + value: "Level 5 — Expert opinion or mechanism-based reasoning only" + signal: "No clinical data. The product's claims rest on theoretical arguments. + Providers and payers will not adopt based on theory alone." + below_average: + value: "Level 4 — Case series or poor-quality cohort study" + signal: "Anecdotal evidence that may support early-stage fundraising but cannot + support reimbursement or guideline inclusion." + average: + value: "Level 3 — Non-randomized controlled cohort study" + signal: "Meaningful evidence that supports pilot deployment and early payer + conversations. Most digital health companies at Series A operate at + this level." + good: + value: "Level 2 — Well-designed RCT" + signal: "Strong evidence. Supports regulatory submission, payer coverage + decisions, and health system adoption. A competitive advantage over + companies with lower evidence levels." + excellent: + value: "Level 1 — Systematic review of RCTs or multiple high-quality RCTs" + signal: "Highest evidence quality. The product is supported by the same evidence + standard as pharmaceutical interventions. This is rare in digital + health and represents a formidable competitive moat." + stage_notes: + seed: "Level 4-5 is acceptable at seed. The study design and protocol for + achieving Level 2-3 evidence should be articulated." + series_a: "Level 3 evidence is expected. Companies with Level 2 evidence at + Series A command premium valuations." + series_b_plus: "Level 2 evidence is the target. Companies at Level 3 or below + face questions about whether the product will ever achieve the evidence + threshold needed for scale." + data_sources: + - source: "Oxford Centre for Evidence-Based Medicine" + year: "2024" + - source: "IQVIA Digital Health Trends" + year: "2024" + related_metrics: [ "clinical-validation-stage", "patient-outcomes-improvement" ] + related_skills: [ "trust-equation", "systems-thinking" ] + caveats: "Evidence level alone does not determine clinical utility. A + well-designed Level 3 study in the right population may be more persuasive + than a poorly executed Level 2 study. Quality within each level matters as + much as the level itself." + + - name: "Time to Regulatory Clearance" + id: "time-to-regulatory-clearance" + category: "product" + definition: "The elapsed time from the decision to pursue regulatory clearance + to the date of clearance/approval, including pre-submission meetings, + study execution, submission preparation, and FDA review." + formula: "Date of clearance — Date of regulatory strategy initiation" + unit: "months" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 36 months" + signal: "Regulatory process has stalled or the company underestimated + complexity. Runway consumption during extended regulatory timelines is + the leading cause of healthtech company failure." + below_average: + value: "24-36 months" + signal: "Within range for complex submissions (De Novo, PMA) but long for + 510(k). May indicate regulatory strategy missteps or insufficient + pre-submission engagement." + average: + value: "12-24 months" + signal: "Typical for a well-managed 510(k) process including clinical study + execution. De Novo classifications also fall in this range with + Breakthrough Device designation." + good: + value: "6-12 months" + signal: "Efficient regulatory process. Common for 510(k) submissions with strong + predicate device arguments and existing clinical data. Indicates + regulatory sophistication." + excellent: + value: "< 6 months" + signal: "Exceptional speed, typically achieved through Breakthrough Device + program pre-review alignment, strong predicate arguments, or prior + regulatory experience. Rare for first-time submissions." + stage_notes: + seed: "Time to clearance is estimated at seed. Investors assess the realism of + the timeline based on pathway complexity and team regulatory + experience." + series_a: "Active regulatory engagement should be underway. The timeline should + be supported by pre-submission meeting feedback and a concrete study + protocol." + series_b_plus: "Clearance should be obtained or imminent. Companies raising + Series B with 18+ months of remaining regulatory timeline face severe + valuation compression." + data_sources: + - source: "FDA Digital Health Center of Excellence" + year: "2024" + - source: "Deloitte Life Sciences Outlook" + year: "2025" + related_metrics: [ "regulatory-approval-status", "regulatory-pathway-cost" ] + related_skills: [ "scenario-planning", "smart-goals" ] + caveats: "Timelines vary dramatically by pathway. A 510(k) with a strong + predicate can clear in 3-6 months of FDA review. A PMA requiring clinical + trials may take 3-5 years. De Novo falls between. Always specify the + pathway when citing this metric." + + - name: "Regulatory Pathway Cost" + id: "regulatory-pathway-cost" + category: "financial" + definition: "The total cost incurred to achieve regulatory clearance or + approval, including regulatory consulting, clinical study costs, + submission fees, legal expenses, and internal staff time allocated to + regulatory affairs." + formula: "SUM(regulatory consulting fees + clinical study costs + FDA user fees + + legal costs + internal regulatory staff allocation)" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $5M for 510(k); > $20M for De Novo/PMA" + signal: "Regulatory costs consuming a disproportionate share of capital. May + indicate scope creep in clinical studies, regulatory strategy pivots, + or insufficient internal regulatory expertise leading to over-reliance + on consultants." + below_average: + value: "$2M-$5M for 510(k); $10M-$20M for De Novo/PMA" + signal: "High end of normal. Acceptable if the regulatory pathway is complex or + involves a novel technology, but warrants cost optimization review." + average: + value: "$500K-$2M for 510(k); $3M-$10M for De Novo/PMA" + signal: "Typical range for well-managed regulatory processes. Clinical study + costs are usually the largest component." + good: + value: "$200K-$500K for 510(k); $1M-$3M for De Novo" + signal: "Capital-efficient regulatory process. Indicates strong predicate + strategy, efficient study design, or leveraged real-world evidence." + excellent: + value: "< $200K for 510(k); < $1M for De Novo" + signal: "Exceptional efficiency. Often achieved by companies with experienced + regulatory leadership, strong predicate arguments, or innovative use + of real-world data in lieu of prospective studies." + stage_notes: + seed: "Regulatory cost estimates should be included in financial projections. + Under-budgeting regulatory costs is the most common financial planning + error in healthtech." + series_a: "Actual regulatory spend should be tracked against projections. + Investors evaluate cost discipline alongside regulatory progress." + series_b_plus: "Regulatory costs should be substantially amortized by this + stage. Ongoing regulatory costs (post-market surveillance, periodic + reporting) are typically modest." + data_sources: + - source: "Deloitte Life Sciences Outlook" + year: "2025" + - source: "Rock Health Digital Health Funding Report" + year: "2024" + related_metrics: + [ + "time-to-regulatory-clearance", + "regulatory-approval-status", + "r-and-d-pct-of-revenue" + ] + related_skills: [ "scenario-planning", "business-model-canvas" ] + caveats: "Regulatory pathway cost varies by 10-50x depending on the pathway, + therapeutic area, and whether prospective clinical studies are required. + Comparing 510(k) costs to PMA costs is meaningless without pathway + context." + + # ───────────────────────────────────────────── + # ADOPTION & ENGAGEMENT METRICS + # ───────────────────────────────────────────── + + - name: "Provider Adoption Rate" + id: "provider-adoption-rate" + category: "product" + definition: "The percentage of targeted providers (physicians, nurses, + therapists) who actively use the product in their clinical workflow after + it has been made available to them. Active use means the provider has used + the product for clinical purposes at least once in the trailing 30 days." + formula: "Active providers (used in last 30 days) / Total providers with access + x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20%" + signal: "Critical adoption failure. The majority of providers with access are + not using the product. This typically signals workflow disruption, + insufficient training, or a product that adds burden without + commensurate clinical value." + below_average: + value: "20-40%" + signal: "Partial adoption. Some providers find value but the product has not + crossed the threshold where it becomes embedded in standard workflow. + Risk of contract non-renewal at health system level." + average: + value: "40-60%" + signal: "Moderate adoption. Sufficient for contract renewal but unlikely to + drive organic expansion. Provider feedback likely reveals workflow + integration gaps." + good: + value: "60-80%" + signal: "Strong adoption. The product has become part of standard workflow for + the majority of targeted providers. This level supports health system + expansion and peer referral." + excellent: + value: "> 80%" + signal: "Exceptional adoption. The product is embedded in clinical workflow. + Providers resist its removal. This creates a powerful retention moat + and supports organic expansion." + stage_notes: + seed: "Adoption rate is measured in pilot settings. Even 5-10 engaged providers + who provide deep feedback are more valuable than 50 providers with + superficial adoption." + series_a: "Pilot adoption rates above 60% are a strong signal. Demonstrating + that providers voluntarily continue using the product after the pilot + period is critical." + series_b_plus: "System-wide adoption rates should be tracked across all deployed + health system customers. Variation between customers reveals + implementation quality differences." + data_sources: + - source: "AMA Digital Health Research" + year: "2024" + - source: "KLAS Research — Provider Adoption Studies" + year: "2024" + related_metrics: + [ + "clinical-workflow-integration-score", + "provider-nps", + "time-to-value-implementation" + ] + related_skills: [ "kotter-change-model", "net-promoter-score" ] + caveats: "Provider adoption in healthtech is fundamentally different from user + adoption in consumer software. Providers are time-constrained, + change-resistant, and motivated by patient outcomes — not features. A + product that saves 2 minutes per patient encounter will be adopted; one + that adds 30 seconds will be rejected regardless of its other benefits." + + - name: "Patient Engagement Rate" + id: "patient-engagement-rate" + category: "product" + definition: "The percentage of enrolled patients who actively engage with the + product within a defined period. For patient-facing products (apps, DTx, + remote monitoring), this measures whether patients use the product as + intended by the clinical protocol." + formula: "Active patients (completed ≥ 1 engagement action in trailing 7 days) / + Enrolled patients x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20% weekly engagement" + signal: "Patients are not using the product. For DTx and remote monitoring, this + means the clinical intervention is not being delivered. Low engagement + invalidates clinical outcomes data and undermines the value + proposition to providers and payers." + below_average: + value: "20-35% weekly engagement" + signal: "Partial engagement. Some patients are using the product but the + majority are not. Engagement decay from enrollment is likely steep." + average: + value: "35-50% weekly engagement" + signal: "Moderate engagement. Sufficient for clinical effect in some therapeutic + areas but below the threshold that DTx companies must demonstrate for + reimbursement." + good: + value: "50-70% weekly engagement" + signal: "Strong engagement. Sufficient for most clinical protocols and + reimbursement requirements. Demonstrates that the product maintains + patient attention in a competitive attention environment." + excellent: + value: "> 70% weekly engagement" + signal: "Exceptional for digital health. Rare outside acute-phase interventions + and products with strong provider reinforcement loops. This level + supports premium reimbursement and clinical outcome claims." + stage_notes: + seed: "Engagement is measured in small cohorts. Qualitative understanding of why + patients engage or disengage is more valuable than the rate itself." + series_a: "Engagement data from pilot studies should show the shape of the + engagement curve — does it flatten (sustainable) or continue declining + (unsustainable)?" + series_b_plus: "Engagement at scale is the key question. Products that maintain + engagement beyond 90 days demonstrate durability that payers and + providers require." + data_sources: + - source: "IQVIA Digital Health Trends" + year: "2024" + - source: "Rock Health Digital Health Funding Report" + year: "2024" + related_metrics: + [ + "monthly-active-patients", + "patient-satisfaction-score", + "patient-outcomes-improvement" + ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Engagement must be measured against the clinical protocol's dosage + requirement, not arbitrary usage metrics. A DTx requiring daily use has + different engagement thresholds than a remote monitoring system requiring + weekly check-ins. Over-engagement (patient anxiety from constant + monitoring) is also a risk." + + - name: "Monthly Active Patients" + id: "monthly-active-patients" + category: "growth" + definition: "The total number of unique patients who completed at least one + clinically meaningful action on the platform in the trailing 30 days. For + provider-facing products, this is the number of patients whose care was + supported by the product." + formula: "COUNT(DISTINCT patients with ≥ 1 clinical action in trailing 30 days)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1,000 MAP at 12 months post-launch" + signal: "Insufficient scale to generate meaningful clinical data, attract payer + interest, or sustain the business. Distribution channels are not + working." + below_average: + value: "1,000-5,000 MAP at 12 months" + signal: "Early traction but limited to pilot deployments. Insufficient scale for + robust outcomes analysis." + average: + value: "5,000-25,000 MAP at 12 months" + signal: "Meaningful scale. Sufficient patient volume for credible outcomes + analysis and to demonstrate health system adoption. Attractive for + Series A health-focused investors." + good: + value: "25,000-100,000 MAP at 12 months" + signal: "Strong scale across multiple health system customers. Clinical data at + this volume supports peer-reviewed publication and payer coverage + submissions." + excellent: + value: "> 100,000 MAP at 12 months" + signal: "Exceptional scale. Sufficient for population health analyses, + real-world evidence generation, and health plan partnerships. Data at + this scale becomes a strategic asset." + stage_notes: + seed: "MAP is measured in hundreds during pilots. The metric matters less than + the depth of engagement and quality of outcomes data generated." + series_a: "5,000-25,000 MAP across multiple sites demonstrates repeatable + deployment. Growth rate matters more than absolute level." + series_b_plus: "MAP growth should compound as health system deployments expand. + The ratio of MAP to contracted lives indicates penetration within + deployed customers." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "CB Insights State of Digital Health" + year: "2024" + related_metrics: [ "patient-engagement-rate", "revenue-per-patient-per-month" ] + related_skills: [ "balanced-scorecard", "growth-share-matrix" ] + caveats: "MAP is not equivalent to MAU in consumer apps. In healthtech, each + 'active patient' represents a clinical relationship with associated safety + obligations. Rapid MAP growth without proportional clinical support + infrastructure is a patient safety risk." + + - name: "Clinical Workflow Integration Score" + id: "clinical-workflow-integration-score" + category: "product" + definition: "A composite metric measuring the depth of integration between the + product and existing clinical workflows — EHR integration level, single + sign-on availability, data interchange standards support (HL7 FHIR, SMART + on FHIR), and the number of additional clicks or steps required in the + provider's workflow." + formula: "Weighted composite: EHR integration (40%) + standards compliance (25%) + + additional workflow steps (20%) + data bidirectionality (15%)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Score < 30 — Standalone product with no EHR integration, requires + separate login and manual data entry" + signal: "Dead on arrival in most health system sales processes. Providers will + not adopt a product that requires them to leave their EHR workflow. + Manual data entry creates clinical risk through transcription errors." + below_average: + value: "Score 30-50 — Basic EHR integration (read-only), single sign-on, limited + data standards support" + signal: "Minimum viable integration. Providers can access the product from the + EHR but must re-enter clinical data. Acceptable for pilot phase but + insufficient for scaled deployment." + average: + value: "Score 50-70 — Bidirectional EHR integration via HL7 FHIR, data flows + both directions, integrated alerting" + signal: "Solid integration level. The product participates in the clinical + workflow without creating significant additional burden. Most health + system IT teams will approve deployment." + good: + value: "Score 70-85 — Deep EHR embedding via SMART on FHIR, appears as a native + EHR module, zero additional clicks for core workflow" + signal: "Strong integration. The product is nearly invisible in the workflow — + it adds value without adding steps. This is the threshold for + enterprise-wide deployment approval." + excellent: + value: "Score > 85 — Fully embedded, ambient operation (requires no provider + action for core function), works across multiple EHR vendors" + signal: "Exceptional integration. The product operates within the EHR + environment as if native, across Epic, Cerner/Oracle Health, and other + systems. Multi-vendor support is a significant competitive advantage." + stage_notes: + seed: "Integration strategy should be defined at seed. The target EHR platform + and integration approach must be identified. SMART on FHIR capabilities + are increasingly expected by health systems." + series_a: "Working integration with at least one major EHR (Epic or + Cerner/Oracle Health) should be demonstrated. Health system customers + will verify integration depth during evaluation." + series_b_plus: "Multi-EHR support and deep integration are expected. Health + system CIOs increasingly require SMART on FHIR compliance and + participation in EHR app marketplaces (Epic App Orchard, Cerner Code)." + data_sources: + - source: "KLAS Research — Provider Adoption Studies" + year: "2024" + - source: "CHIME CIO Surveys" + year: "2024" + related_metrics: [ "provider-adoption-rate", "time-to-value-implementation" ] + related_skills: [ "systems-thinking", "doblin-ten-types" ] + caveats: "Integration depth must be balanced against vendor dependency. Building + exclusively on Epic's proprietary APIs creates lock-in. FHIR-first + architecture with EHR-specific adapters provides the best balance of + integration depth and vendor flexibility." + + # ───────────────────────────────────────────── + # REIMBURSEMENT & REVENUE METRICS + # ───────────────────────────────────────────── + + - name: "Payer Reimbursement Rate" + id: "payer-reimbursement-rate" + category: "financial" + definition: "The percentage of product usage that is covered by health insurance + payers (commercial, Medicare, Medicaid), as opposed to self-pay or + employer direct-contract arrangements. For healthtech, payer reimbursement + is the gatekeeper to scalable revenue." + formula: "Revenue from payer-reimbursed encounters / Total revenue from clinical + encounters x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10% payer-covered" + signal: "The product operates almost entirely outside the reimbursement system. + Revenue depends on out-of-pocket patient spend or direct employer + contracts — both limited and fragile channels." + below_average: + value: "10-30% payer-covered" + signal: "Some payer coverage secured but not the norm. Revenue model likely + depends on a mix of reimbursement and alternative payment mechanisms. + Scalability constrained." + average: + value: "30-60% payer-covered" + signal: "Material payer coverage. Reimbursement pathway exists and is growing. + The company can demonstrate to health systems that the product + generates reimbursable revenue." + good: + value: "60-80% payer-covered" + signal: "Strong reimbursement position. Majority of usage is payer-covered, + reducing patient and health system financial burden. Scalable revenue + model validated." + excellent: + value: "> 80% payer-covered with dedicated CPT or HCPCS codes" + signal: "Best-in-class reimbursement. Dedicated billing codes provide pricing + transparency and predictability. The product is integrated into the + healthcare payment infrastructure." + stage_notes: + seed: "Reimbursement strategy should be defined, including target CPT codes and + payer engagement plan. Reimbursement-naivety at seed is the most common + indicator of healthtech failure at later stages." + series_a: "Some form of reimbursement should be demonstrated — even if through + existing codes or pilot payer agreements. A clear pathway to broader + coverage must be articulated." + series_b_plus: "Broad payer coverage is expected for revenue-stage companies. + The transition from pilot payer agreements to at-scale reimbursement is + a critical Series B milestone." + data_sources: + - source: "CMS Innovation Center Evaluation Reports" + year: "2024" + - source: "McKinsey Healthcare Practice Reports" + year: "2024" + related_metrics: [ "revenue-per-patient-per-month", "clinical-validation-stage" ] + related_skills: + - business-model-canvas + caveats: "Reimbursement rates vary dramatically by payer, geography, and product + type. Medicare coverage decisions set precedents that commercial payers + follow, but not immediately — there is typically a 12-24 month lag. State + Medicaid programs have independent coverage decisions." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Revenue per Patient per Month" + id: "revenue-per-patient-per-month" + category: "unit-economics" + definition: "The average monthly revenue generated per active patient on the + platform, including all revenue streams: payer reimbursement, patient + co-pays, health system SaaS fees allocated per patient, and employer + direct-pay allocated per covered life." + formula: "Total monthly revenue / Monthly active patients" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $5 per patient per month" + signal: "Revenue per patient too low to cover clinical support costs. The unit + economics cannot support the clinical oversight and safety monitoring + required for patient-facing health products." + below_average: + value: "$5-$20 per patient per month" + signal: "Low margin per patient. Sustainable only at very high volume with + minimal clinical support requirements. Typical of wellness-adjacent + products without dedicated reimbursement." + average: + value: "$20-$75 per patient per month" + signal: "Moderate per-patient revenue. Common for remote patient monitoring and + chronic disease management platforms with CPT-code-based + reimbursement." + good: + value: "$75-$200 per patient per month" + signal: "Strong per-patient revenue. Typical of digital therapeutics with + dedicated reimbursement, specialty-focused platforms, and clinical + decision support tools with demonstrated outcome improvement." + excellent: + value: "> $200 per patient per month" + signal: "Premium per-patient revenue. Achieved by products serving high-acuity + conditions, products with pharma co-pay assistance, or products that + replace significantly more expensive alternatives." + stage_notes: + seed: "Revenue per patient is estimated from the reimbursement strategy. + Seed-stage companies should model both reimbursed and non-reimbursed + scenarios." + series_a: "Actual revenue per patient from pilot deployments should be + available. The gap between contracted revenue and realized revenue + (patient dropout, engagement decay) must be understood." + series_b_plus: "Revenue per patient should be stable or growing. Expansion + through additional services per patient is a key growth lever." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "CMS Innovation Center Evaluation Reports" + year: "2024" + related_metrics: + [ + "payer-reimbursement-rate", + "monthly-active-patients", + "patient-engagement-rate" + ] + related_skills: + - business-model-canvas + caveats: "Revenue per patient must be interpreted in the context of clinical + support costs per patient. A $100/patient/month product that requires + $80/patient/month in clinical staffing has fundamentally different + economics than one requiring $10/patient/month." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Customer Acquisition Cost (per Provider/Health System)" + id: "cac-health-system" + category: "sales" + definition: "The fully loaded cost to acquire a new health system or provider + group customer, including sales team costs, marketing, clinical pilot + costs, integration implementation, and regulatory/compliance review costs + incurred during the sales process." + formula: "Total sales & marketing cost (including pilot costs) / Number of new + health system customers acquired" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "> $500K per health system customer" + signal: "Acquisition cost is unsustainably high. The sales process likely + includes extensive free pilot periods, custom integration work, and + long clinical evaluation cycles that the company is funding entirely." + below_average: + value: "$200K-$500K per health system customer" + signal: "High but not unusual for enterprise health system sales. Acceptable + only if contract values and retention rates justify the investment." + average: + value: "$75K-$200K per health system customer" + signal: "Moderate CAC for health system sales. Typical for companies with + established clinical evidence and streamlined implementation + processes." + good: + value: "$25K-$75K per health system customer" + signal: "Efficient customer acquisition. Indicates strong inbound demand driven + by clinical evidence, peer referral, or health system innovation + network effects." + excellent: + value: "< $25K per health system customer" + signal: "Exceptional efficiency. Often achieved through health system innovation + programs, EHR marketplace distribution, or products with such strong + clinical evidence that they sell themselves." + stage_notes: + seed: "CAC is difficult to measure at seed — early customers are often acquired + through founder relationships. Track the full cost of pilot deployments + as a proxy." + series_a: "CAC should be measured for non-founder-sourced customers. The ratio + of CAC to first-year contract value indicates commercial viability." + series_b_plus: "CAC should be declining as brand recognition, clinical evidence, + and referenceable customers reduce the sales effort required." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "CB Insights State of Digital Health" + year: "2024" + related_metrics: + [ + "sales-cycle-length", + "contract-value-health-system", + "provider-adoption-rate" + ] + related_skills: [ "four-ps-marketing", "blue-ocean-strategy" ] + caveats: "Health system CAC must include the cost of clinical pilots, which are + often provided free or at reduced cost. Excluding pilot costs from CAC + understates the true acquisition cost by 30-60%." + + - name: "Sales Cycle Length" + id: "sales-cycle-length" + category: "sales" + definition: "The elapsed time from initial qualified engagement with a health + system or provider group buyer to signed contract. In healthtech, this + cycle includes clinical evaluation, IT security review, legal review, and + often a pilot period." + formula: "Median days from first qualified meeting to signed contract" + unit: "months" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 18 months" + signal: "Sales cycle is dangerously long. At this duration, the company must + maintain 18+ months of pipeline to sustain growth, and customer + requirements may change during the process." + below_average: + value: "12-18 months" + signal: "Long but within range for complex health system enterprise sales. + Common for novel products requiring clinical evaluation committees and + pilot deployment." + average: + value: "6-12 months" + signal: "Typical for health system SaaS sales with established clinical + evidence. The cycle includes IT review, clinical evaluation, and + contract negotiation." + good: + value: "3-6 months" + signal: "Efficient for healthtech. Achieved by products with strong clinical + evidence, streamlined implementation, and established procurement + pathways." + excellent: + value: "< 3 months" + signal: "Exceptional speed. Rare for health system enterprise sales. Typically + achieved through EHR marketplace distribution, self-serve models for + individual providers, or products sold to non-clinical buyers." + stage_notes: + seed: "Sales cycle length is discovered, not planned, at seed. Early customers + teach the company what the real buying process looks like." + series_a: "Sales cycle data from 5-10 deals should inform forecasting and + pipeline management. Investors will evaluate whether the sales cycle is + compatible with the company's runway." + series_b_plus: "Sales cycle optimization becomes a key efficiency lever. + Reducing cycle length by 30% has the same revenue impact as increasing + pipeline by 30%." + data_sources: + - source: "CHIME CIO Surveys" + year: "2024" + - source: "Rock Health Digital Health Funding Report" + year: "2024" + related_metrics: [ "cac-health-system", "contract-value-health-system" ] + related_skills: [ "first-mover-strategy", "negotiation-game-theory" ] + caveats: "Health system sales cycles are structural, not sales-execution + problems. Clinical evaluation, IT security review, and legal review have + minimum durations that cannot be compressed through sales technique. The + answer is not faster selling but better pipeline management." + + - name: "Contract Value (Health System Deals)" + id: "contract-value-health-system" + category: "sales" + definition: "The total annual contract value of health system enterprise deals, + including SaaS fees, implementation fees, and any per-patient or + per-encounter fees based on contracted volume." + formula: "Annual SaaS fees + (per-patient/encounter fee x contracted volume) + + implementation fees (amortized over contract term)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $50K ACV" + signal: "Contract value too low to justify health system enterprise sales + motion. The economics do not support the long sales cycle and + implementation effort required." + below_average: + value: "$50K-$150K ACV" + signal: "Low-end enterprise deal. Sustainable if sales cycle is under 6 months + and implementation is lightweight. Typical for departmental (not + enterprise-wide) deployments." + average: + value: "$150K-$500K ACV" + signal: "Mid-market health system deal. Justifies dedicated sales effort and + implementation support. Common for clinical decision support, + analytics, and remote monitoring platforms." + good: + value: "$500K-$2M ACV" + signal: "Strong enterprise deal. Indicates broad deployment across the health + system. The contract likely includes multi-department or system-wide + licensing." + excellent: + value: "> $2M ACV" + signal: "Large enterprise deal. Typically system-wide deployment at a large IDN + (Integrated Delivery Network). These deals often include multi-year + commitments and strategic partnership elements." + stage_notes: + seed: "Contract value is negotiated in early pilots. Founders should resist the + temptation to give the product away — even pilot pricing establishes a + reference point for future negotiations." + series_a: "Multiple contracts at consistent ACV levels demonstrate repeatable + commercial traction. ACV growth from initial to subsequent deals is a + positive signal." + series_b_plus: "ACV expansion within existing customers (land-and-expand) is as + important as new customer ACV. Multi-year contracts with annual + escalators provide revenue predictability." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "KLAS Research — Emerging Technology Studies" + year: "2024" + related_metrics: [ "sales-cycle-length", "cac-health-system", "revenue-per-patient-per-month" ] + related_skills: + - competitive-negotiation + caveats: "Contract value must be distinguished from realized revenue. Health + system contracts often include ramp periods, volume-contingent pricing, + and outcome-based components. A $1M ACV contract that is 50% + outcome-contingent has very different economics than a $500K fully + committed contract." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + # ───────────────────────────────────────────── + # SATISFACTION & TRUST METRICS + # ───────────────────────────────────────────── + + - name: "Patient Satisfaction Score" + id: "patient-satisfaction-score" + category: "product" + definition: "A composite patient experience metric derived from validated survey + instruments (CAHPS, SUS adapted for health, proprietary NPS), measuring + patient satisfaction with the digital health experience — distinct from + clinical outcome satisfaction." + formula: "Mean score on validated patient satisfaction instrument, normalized to + 0-100 scale" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 50" + signal: "Patients actively dislike the experience. High abandonment risk. In + healthtech, dissatisfied patients stop using the product — which means + the clinical intervention stops, outcomes deteriorate, and the value + proposition collapses." + below_average: + value: "50-65" + signal: "Below average patient experience. The product may deliver clinical + value but the experience creates friction that limits engagement and + retention." + average: + value: "65-75" + signal: "Adequate patient experience. Patients tolerate the product for its + clinical benefits. Room for improvement, especially in UX design for + diverse health literacy levels." + good: + value: "75-85" + signal: "Strong patient experience. Patients recommend the product to peers. + This level supports word-of-mouth growth and payer satisfaction + metrics." + excellent: + value: "> 85" + signal: "Exceptional patient experience. Rare in healthcare technology. The + product has achieved the difficult balance of clinical rigor and + consumer-grade UX." + stage_notes: + seed: "Patient satisfaction is measured qualitatively through pilot participant + interviews. Net Promoter Score is a reasonable proxy at this stage." + series_a: "Quantitative satisfaction data from pilot studies should be + available. Comparison to benchmark scores in the therapeutic area + provides context." + series_b_plus: "Patient satisfaction should be tracked continuously and reported + to health system customers as part of QBR materials." + data_sources: + - source: "IQVIA Digital Health Trends" + year: "2024" + - source: "AMA Digital Health Research" + year: "2024" + related_metrics: [ "patient-engagement-rate", "provider-nps" ] + related_skills: [ "net-promoter-score", "emotional-intelligence" ] + caveats: "Patient satisfaction and clinical outcomes are not always correlated. + Patients may be satisfied with a product that does not improve outcomes + (pleasant but ineffective) or dissatisfied with one that does (effective + but unpleasant). Both dimensions must be tracked independently." + + - name: "Provider NPS" + id: "provider-nps" + category: "product" + definition: "Net Promoter Score measured among providers (physicians, nurses, + clinical staff) who use the product. Reflects whether clinicians would + recommend the product to colleagues — the single most powerful + distribution mechanism in healthcare." + formula: "% Promoters (9-10) - % Detractors (0-6) among surveyed providers" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0" + signal: "More detractors than promoters among providers. The product is + generating negative word-of-mouth in clinical networks — an + existential threat given how heavily providers rely on peer + recommendations." + below_average: + value: "0-20" + signal: "Tepid provider sentiment. The product is tolerated but not championed. + Organic expansion through provider referral will not occur at this + level." + average: + value: "20-40" + signal: "Positive but not enthusiastic. Providers see value but also experience + friction. Most health IT products cluster in this range." + good: + value: "40-60" + signal: "Strong provider advocacy. Providers actively recommend the product to + colleagues. This is the threshold where organic adoption within and + across health systems accelerates." + excellent: + value: "> 60" + signal: "Exceptional provider advocacy. Rare in health IT where clinician + satisfaction with technology is chronically low. A provider NPS above + 60 is a formidable competitive moat." + stage_notes: + seed: "Provider NPS from pilot clinicians should be collected. Even a small + sample (n=10-20) reveals whether clinicians find the product genuinely + valuable." + series_a: "Provider NPS should be tracked across all deployment sites. Variation + between sites reveals implementation quality and workflow fit + differences." + series_b_plus: "Provider NPS should be published in sales materials and QBR + reports. High provider NPS is a differentiated asset in health system + procurement processes." + data_sources: + - source: "KLAS Research — Provider Satisfaction" + year: "2024" + - source: "AMA Digital Health Research" + year: "2024" + related_metrics: [ "provider-adoption-rate", "patient-satisfaction-score" ] + related_skills: [ "net-promoter-score", "trust-equation" ] + caveats: "Provider NPS is influenced by implementation quality as much as + product quality. A good product poorly implemented will receive low NPS. + Always segment NPS by deployment maturity to separate product quality from + implementation quality." + + - name: "HIPAA Compliance Score" + id: "hipaa-compliance-score" + category: "efficiency" + definition: "A composite metric measuring the completeness and maturity of the + company's HIPAA compliance program, including technical safeguards, + administrative safeguards, physical safeguards, breach notification + procedures, and business associate agreement coverage." + formula: "Weighted composite across HIPAA Security Rule requirements: Technical + (35%) + Administrative (35%) + Physical (15%) + BAA coverage (15%), scored + 0-100" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "Score < 50 — Material gaps in HIPAA compliance" + signal: "The company is operating with significant legal and operational risk. A + breach or OCR audit at this compliance level could result in civil + monetary penalties ($100-$50K per violation, up to $1.5M per violation + category per year), corrective action plans, and reputational damage + that destroys customer relationships." + below_average: + value: "Score 50-70 — Basic safeguards in place but gaps in documentation, + training, or BAA coverage" + signal: "Minimum compliance posture. Sufficient to pass a cursory review but + vulnerable to OCR investigation. Health system customers' security + teams will identify gaps during vendor assessment." + average: + value: "Score 70-85 — Comprehensive compliance program with regular risk + assessments, documented policies, and staff training" + signal: "Solid compliance posture. Sufficient for most health system procurement + processes. Annual risk assessment conducted and documented." + good: + value: "Score 85-95 — Mature compliance program with independent audit, incident + response testing, and continuous monitoring" + signal: "Strong compliance. Third-party HIPAA audit completed (e.g., HITRUST CSF + certification). Health system customers can rely on independent + validation rather than conducting their own assessment." + excellent: + value: "Score > 95 — HITRUST CSF certified, SOC 2 Type II, ongoing penetration + testing, zero findings on most recent audit" + signal: "Best-in-class compliance. HITRUST certification with SOC 2 Type II + provides the highest assurance level. Accelerates health system sales + by eliminating security review as a sales cycle bottleneck." + stage_notes: + seed: "Foundational HIPAA compliance (encryption, access controls, BAAs with all + vendors) must be in place from day one. Cutting corners on HIPAA at seed + creates technical and legal debt that compounds." + series_a: "A formal risk assessment and documented compliance program should be + completed. Third-party audit (HITRUST or SOC 2) should be on the + near-term roadmap." + series_b_plus: "HITRUST CSF certification or SOC 2 Type II should be obtained. + Large health system customers will require one or both." + data_sources: + - source: "HHS OCR Enforcement Data" + year: "2024" + - source: "CHIME CIO Surveys" + year: "2024" + related_metrics: [ "data-security-incident-rate" ] + related_skills: [ "balanced-scorecard", "vuca-framework" ] + caveats: "HIPAA compliance is a floor, not a ceiling. Passing a HIPAA audit does + not mean the company has strong security — it means the company meets + minimum federal requirements. State health data privacy laws (e.g., + California CMIA, New York SHIELD Act) may impose additional requirements." + + - name: "Data Security Incident Rate" + id: "data-security-incident-rate" + category: "efficiency" + definition: "The number of data security incidents involving protected health + information (PHI) per quarter, including breaches, unauthorized access + events, and near-misses. A breach affecting 500+ individuals triggers HHS + notification and public disclosure." + formula: "COUNT(security incidents involving PHI) per quarter" + unit: "ratio" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 3 incidents per quarter or any breach affecting 500+ individuals" + signal: "Critical security problem. A breach affecting 500+ individuals triggers + HHS notification, public disclosure on the HHS 'Wall of Shame,' + mandatory OCR investigation, and potential civil monetary penalties. + The business may not survive the reputational damage." + below_average: + value: "2-3 incidents per quarter (sub-500 individuals)" + signal: "Concerning incident rate. Each incident requires breach risk assessment + under HIPAA, notification to affected individuals, and internal + investigation. Cumulative incidents suggest systemic security + weaknesses." + average: + value: "1 incident per quarter (sub-500 individuals)" + signal: "Occasional incidents within range for growing healthtech companies. + Each incident should trigger root cause analysis and security + improvement." + good: + value: "0-1 incidents per year" + signal: "Strong security posture. Incident rate consistent with mature security + programs. Proactive threat monitoring and security testing are keeping + pace with threat evolution." + excellent: + value: "Zero incidents for 12+ months with active penetration testing and threat + monitoring" + signal: "Exceptional security. Not merely the absence of detected incidents but + the presence of active security testing that validates the security + posture continuously." + stage_notes: + seed: "Zero incidents is the only acceptable target from day one. A PHI breach + at seed stage can destroy the company before it begins." + series_a: "Incident response procedures should be documented and tested. + Penetration testing should be conducted at least annually." + series_b_plus: "Continuous security monitoring and regular penetration testing + (quarterly) are expected. Health system customers will audit incident + history during procurement." + data_sources: + - source: "HHS OCR Breach Portal" + year: "2024" + - source: "HITRUST Cyber Threat Intelligence Reports" + year: "2024" + related_metrics: [ "hipaa-compliance-score" ] + related_skills: [ "black-swans", "systems-thinking" ] + caveats: "Zero incidents may reflect a lack of detection capability rather than + a lack of incidents. Security incident metrics must be paired with + proactive security testing (penetration testing, red teaming) to + distinguish between 'no incidents' and 'no detected incidents.'" + + # ───────────────────────────────────────────── + # RETENTION & CHURN METRICS + # ───────────────────────────────────────────── + + - name: "Churn Rate (Provider/Health System)" + id: "churn-rate-provider" + category: "retention" + definition: "The percentage of provider or health system customers who terminate + their contract or fail to renew in a given period. In healthtech, provider + churn has both business and clinical implications — when a health system + leaves, patients lose access to the intervention." + formula: "Customers lost in period / Customers at start of period x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 20% annual churn" + signal: "Severe retention failure. Losing one in five health system customers + annually means the company must replace its entire customer base every + five years just to maintain revenue. This rate also suggests the + product is not delivering sustained clinical or operational value." + below_average: + value: "15-20% annual churn" + signal: "High churn that undermines growth economics. Each churned health system + represents lost patients, lost clinical data continuity, and lost + reference potential." + average: + value: "10-15% annual churn" + signal: "Moderate churn. Typical for healthtech companies in early scaling phase + where implementation quality varies across customers." + good: + value: "5-10% annual churn" + signal: "Strong retention. Most health system customers are renewing and + expanding. Churn is concentrated among poor-fit customers or those + with organizational changes (M&A, leadership turnover)." + excellent: + value: "< 5% annual churn" + signal: "Exceptional retention. The product is embedded in clinical workflow and + delivering sustained value. Health systems consider it a critical part + of their technology infrastructure." + stage_notes: + seed: "Churn is unmeasurable with a few pilot customers. Focus on qualitative + renewal intent signals — would this customer renew at full price?" + series_a: "First renewal data should be available. The transition from + free/reduced pilot to paid contract is the moment of truth for + retention." + series_b_plus: "Churn should be disaggregated by customer cohort, deployment + size, and therapeutic area. Identifying patterns in churn enables + targeted retention interventions." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "KLAS Research — Emerging Technology Studies" + year: "2024" + related_metrics: [ "churn-rate-patient", "provider-nps", "provider-adoption-rate" ] + related_skills: [ "net-promoter-score", "systems-thinking" ] + caveats: "Health system churn often follows personnel changes — when the + clinical champion who adopted the product leaves, the contract is at risk. + Reducing key-person dependency requires embedding the product in workflow + rather than relying on individual advocacy." + + - name: "Churn Rate (Patient)" + id: "churn-rate-patient" + category: "retention" + definition: "The percentage of enrolled patients who disengage from the product + in a given period, measured as patients who have not completed a clinical + engagement action in 30+ days. Patient churn in healthtech is not merely a + business metric — it means a patient is no longer receiving the intended + clinical intervention." + formula: "Patients inactive for 30+ days in period / Patients active at start of + period x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 40% monthly churn" + signal: "Catastrophic engagement failure. Most patients abandon the product + within weeks of enrollment. The clinical intervention is not being + delivered to the majority of patients. Clinical outcome claims are + undermined." + below_average: + value: "25-40% monthly churn" + signal: "High attrition that limits clinical effectiveness. Typical of products + with poor onboarding, low perceived value, or excessive burden on + patients." + average: + value: "15-25% monthly churn" + signal: "Moderate attrition. Common in digital health, where patient engagement + naturally decays over time. The challenge is to flatten the engagement + curve." + good: + value: "8-15% monthly churn" + signal: "Strong patient retention. The product maintains engagement beyond the + initial novelty period. Clinical outcome data at this retention level + is credible." + excellent: + value: "< 8% monthly churn" + signal: "Exceptional patient retention. Rare in digital health. Typically + achieved by products with strong provider reinforcement loops, + tangible daily value, and personalized engagement." + stage_notes: + seed: "Patient churn patterns are being discovered. The shape of the engagement + decay curve (steep initial drop vs. gradual decline vs. flattening) is + more informative than the rate itself." + series_a: "Patient retention data across multiple cohorts should show improving + trends as the product evolves. Cohort-over-cohort improvement is a key + investor signal." + series_b_plus: "Patient retention at scale must support clinical outcome claims. + If the product's clinical study assumed 70% engagement but real-world + engagement is 30%, outcome expectations must be adjusted." + data_sources: + - source: "IQVIA Digital Health Trends" + year: "2024" + - source: "Journal of Medical Internet Research — Engagement Studies" + year: "2024" + related_metrics: + [ + "patient-engagement-rate", + "monthly-active-patients", + "patient-satisfaction-score" + ] + related_skills: [ "product-life-cycle", "systems-thinking" ] + caveats: "Not all patient churn is negative. Patients who complete a therapeutic + protocol and graduate from the product are 'positive churn' — they have + received the intended intervention. Separate therapeutic completion from + disengagement in churn analysis." + + # ───────────────────────────────────────────── + # FINANCIAL METRICS + # ───────────────────────────────────────────── + + - name: "Gross Margin" + id: "gross-margin" + category: "financial" + definition: "Revenue minus cost of goods sold as a percentage of revenue. In + healthtech, COGS includes not only hosting and infrastructure but also + clinical staff costs (if the product requires clinician involvement for + delivery), regulatory compliance costs allocated to service delivery, and + clinical content maintenance." + formula: "(Revenue - COGS) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 40%" + signal: "Margin too low for a technology company. The product likely requires + significant human clinical intervention per patient, making it a + services business with a technology wrapper." + below_average: + value: "40-55%" + signal: "Below software margins. Common for healthtech products with embedded + clinical services (telehealth with employed clinicians, RPM with nurse + monitoring). Investors will question scalability." + average: + value: "55-70%" + signal: "Moderate margins. Typical for healthtech products with some clinical + service component. Improving margins through automation and + AI-assisted clinical workflows is a common growth strategy." + good: + value: "70-80%" + signal: "Software-like margins. Achieved by products that deliver value through + technology with minimal per-patient clinical staff cost. This is the + target range for scalable healthtech." + excellent: + value: "> 80%" + signal: "Pure software margins. Typical for health data analytics, clinical + decision support tools, and administrative workflow products that do + not require clinical staff per encounter." + stage_notes: + seed: "Gross margin is estimated at seed. The key question is whether the + product's clinical model requires human clinicians per patient + interaction (services) or whether technology delivers the intervention + (software)." + series_a: "Actual gross margin from revenue-generating operations should be + calculated. If below 50%, a clear path to margin expansion must be + articulated." + series_b_plus: "Gross margin should be trending toward 60%+. Companies with + clinical services components should show a path to automating clinical + workflows." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "CB Insights State of Digital Health" + year: "2024" + related_metrics: [ "revenue-per-patient-per-month", "r-and-d-pct-of-revenue" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "Healthtech gross margin classification is contested. Whether clinical + staff costs belong in COGS or OpEx depends on whether clinicians are + essential to product delivery (COGS) or provide supplementary support + (OpEx). Be consistent and transparent about classification methodology." + + - name: "R&D as % of Revenue (Clinical + Technical)" + id: "r-and-d-pct-of-revenue" + category: "efficiency" + definition: "The percentage of revenue invested in research and development, + including both technical R&D (software engineering, infrastructure, AI/ML + development) and clinical R&D (clinical study design and execution, + regulatory affairs, medical writing, clinical evidence generation)." + formula: "(Technical R&D spend + Clinical R&D spend) / Total revenue x 100" + unit: "percentage" + direction: "target-range" + benchmarks: + poor: + value: "> 80% of revenue (at growth stage) or < 15% (at any stage)" + signal: "Either unsustainably high R&D spend that depletes capital without + corresponding clinical or commercial progress, or dangerously low + investment that starves the clinical evidence pipeline and product + development." + below_average: + value: "50-80% of revenue (growth stage)" + signal: "High R&D intensity. Acceptable during clinical validation phase but + must be declining as a percentage of revenue as the company + transitions to commercial scaling." + average: + value: "30-50% of revenue" + signal: "Typical for healthtech companies balancing ongoing clinical evidence + generation with product development. The split between clinical and + technical R&D reveals strategic priorities." + good: + value: "20-30% of revenue" + signal: "Efficient R&D investment. Indicates the company has passed the heaviest + clinical validation investment phase and is optimizing returns on + existing evidence assets." + excellent: + value: "15-20% of revenue with continued clinical evidence publication" + signal: "Optimal balance. Sufficient investment to maintain clinical evidence + leadership and product innovation while preserving capital for + commercial scaling." + stage_notes: + seed: "R&D is effectively 100% of spend at seed. The relevant question is the + split between clinical and technical R&D — both must be funded." + series_a: "R&D split (clinical vs. technical) should be explicit. Investors + assess whether the company is allocating sufficient resources to + clinical evidence generation alongside product development." + series_b_plus: "R&D as percentage of revenue should be declining as revenue + scales. However, cutting clinical R&D too aggressively leaves the + company vulnerable to competitors who build stronger evidence." + data_sources: + - source: "Rock Health Digital Health Funding Report" + year: "2024" + - source: "Deloitte Life Sciences Outlook" + year: "2025" + related_metrics: [ "gross-margin", "clinical-validation-stage" ] + related_skills: [ "balanced-scorecard", "eisenhower-matrix" ] + caveats: "Clinical R&D in healthtech is not optional — it is the equivalent of + product R&D in software. Companies that cut clinical evidence investment + to improve short-term financials risk losing the evidence advantage that + sustains their market position." + + - name: "Time to Value (Implementation at Health System)" + id: "time-to-value-implementation" + category: "sales" + definition: "The elapsed time from contract signing to the health system + customer realizing measurable value from the product — defined as the + point at which the system is live, providers are trained, and clinical + workflow integration is complete." + formula: "Date of measurable value realization — Date of contract signing" + unit: "months" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 12 months" + signal: "Implementation is a major bottleneck. Health system customers become + frustrated, internal champions lose political capital, and the risk of + pre-go-live cancellation increases." + below_average: + value: "6-12 months" + signal: "Long implementation. Common for complex EHR integrations and + enterprise-wide deployments but creates significant risk of customer + disengagement." + average: + value: "3-6 months" + signal: "Typical for healthtech products requiring EHR integration, provider + training, and clinical workflow adaptation. Manageable if expectations + are set clearly during the sales process." + good: + value: "1-3 months" + signal: "Efficient implementation. Achieved through standardized deployment + playbooks, pre-built EHR integrations, and scalable provider training + programs." + excellent: + value: "< 1 month" + signal: "Rapid time to value. Exceptional for health system enterprise products. + Typically achieved by cloud-native products with self-service EHR + integration (SMART on FHIR) and on-demand training." + stage_notes: + seed: "Time to value is being optimized during early deployments. Each pilot + reveals integration and training bottlenecks that inform the + implementation playbook." + series_a: "Implementation time should be trending downward as the company + standardizes deployment. A repeatable implementation playbook is a key + scaling prerequisite." + series_b_plus: "Time to value should be a competitive advantage. Companies that + deploy faster earn revenue faster, generate outcomes data faster, and + create stronger customer relationships." + data_sources: + - source: "KLAS Research — Implementation Studies" + year: "2024" + - source: "CHIME CIO Surveys" + year: "2024" + related_metrics: + [ + "provider-adoption-rate", + "clinical-workflow-integration-score", + "cac-health-system" + ] + related_skills: [ "kotter-change-model", "smart-goals" ] + caveats: "Time to value must be measured from the customer's perspective, not + the company's. Going live is not value realization — value realization + occurs when providers are actively using the product and clinical or + operational outcomes are measurable. Many healthtech companies declare + 'go-live' before the customer experiences value." diff --git a/plugins/foreman/content/industry-packs/healthtech/healthtech-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/healthtech/healthtech-diagnostic-rules.yaml new file mode 100644 index 0000000..fac8ca9 --- /dev/null +++ b/plugins/foreman/content/industry-packs/healthtech/healthtech-diagnostic-rules.yaml @@ -0,0 +1,1443 @@ +# Healthtech Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in a healthtech context. +# The diagnostic agent loads these rules when the healthtech industry pack is active. +# +# PATIENT SAFETY PRINCIPLE: Every diagnostic adaptation addresses how patient +# safety, clinical validation, and regulatory compliance shape the diagnosis. +# In healthtech, the presenting business symptom (revenue decline, growth stall, +# churn) often has a clinical root cause — insufficient evidence, provider +# adoption failure, reimbursement denial, or regulatory delay. Diagnostics +# must surface clinical dimensions even when the presenting symptom appears +# purely commercial. +# +# TRIPLE STAKEHOLDER PRINCIPLE: Healthtech diagnostics must consider whether the +# problem originates with patients (engagement, outcomes), providers (adoption, +# satisfaction), or payers (reimbursement, coverage). The root cause often lies +# in a different stakeholder group than the symptom suggests. +# +# Adaptation types: +# as-is — The diagnostic works without modification for healthtech companies. +# enhanced — The diagnostic is relevant but benefits from additional healthtech-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for healthtech. + +pack_metadata: + sector: "healthtech" + display_name: "Healthtech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Churn in healthtech has three distinct dimensions absent + from other industries. Provider churn (health systems terminating + contracts) is driven by adoption failure, clinical evidence gaps, or + reimbursement changes — not product satisfaction in the SaaS sense. + Patient churn (patients disengaging) has clinical consequences — a patient + who stops using a DTx is not merely a lost user but a patient not + receiving their prescribed intervention. Payer churn (payers discontinuing + coverage) eliminates the revenue foundation for an entire patient + population. Separating these three churn vectors is essential for accurate + diagnosis." + additional_triage_questions: + - question: "Which stakeholder is churning — health system customers (contract + non-renewal), patients (disengagement from the clinical intervention), + or payers (coverage termination)?" + purpose: "Each churn type has fundamentally different root causes and solutions. + Health system churn signals adoption or evidence failure. Patient + churn signals engagement or clinical relevance failure. Payer churn + signals reimbursement or evidence failure." + routing_impact: "Health system churn routes to provider-adoption-rate analysis + and clinical-workflow-integration assessment. Patient churn routes to + patient-engagement-rate analysis and clinical protocol review. Payer + churn routes to clinical-evidence-strength assessment and + reimbursement strategy review." + - question: "Is provider adoption within the health system customer above 50%, or + are contracted providers not using the product?" + purpose: "Health systems may terminate contracts not because the product is + inadequate but because their providers did not adopt it — an + implementation failure, not a product failure. Low adoption within + contracted systems is the most common and most fixable healthtech + churn driver." + routing_impact: "Low adoption (<50%) routes to implementation process review, + provider training assessment, and clinical workflow integration + analysis. High adoption with churn routes to clinical evidence review + and competitive analysis." + - question: "Did the churn coincide with a change in reimbursement policy, + clinical guidelines, or the departure of the clinical champion at the + health system?" + purpose: "Healthtech churn is frequently triggered by external events — a payer + discontinuing coverage eliminates the revenue justification, updated + clinical guidelines that favor a different approach reduce the + evidence argument, and the departure of the physician champion removes + the internal advocate." + routing_impact: "Reimbursement-driven churn routes to payer strategy review and + alternative revenue model exploration. Guideline-driven churn routes + to clinical evidence strategy reassessment. Champion-departure churn + routes to relationship diversification and implementation depth + analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Provider adoption failure driving health system churn" + reason: "The most common healthtech churn pattern: the health system buys the + product, but providers do not use it. Low adoption leads to low + outcomes, which leads to non-renewal. The product may be excellent — + but if providers do not adopt it, the clinical value is never + delivered." + - diagnosis: "Reimbursement loss undermining the business case for continued use" + reason: "When payers reduce or eliminate coverage for the product's clinical use + case, health systems lose the financial justification for the + contract. The product's clinical value is unchanged, but the + economic model collapses." + less_likely: + - diagnosis: "Product feature inadequacy" + reason: "Healthtech churn is rarely driven by missing features. It is driven by + workflow disruption, insufficient evidence, reimbursement failure, + or adoption barriers. Feature gap is the most over-diagnosed and + least accurate churn driver in healthtech." + healthtech_specific_diagnoses: + - name: "Clinical validation gap driving payer and provider rejection" + description: "The product lacks sufficient clinical evidence to satisfy health + system clinical review committees and payer coverage criteria. Sales + stall at the evidence question, and existing customers do not renew + because they cannot demonstrate clinical value to their internal + stakeholders. The product may be effective, but without published + evidence, effectiveness cannot be verified." + symptoms: + - "Health system clinical review committees requesting evidence that + does not exist" + - "Payers declining coverage citing insufficient evidence" + - "Existing customers unable to justify renewal to their clinical and + administrative leadership" + - "Competitors with published studies winning head-to-head evaluations + despite inferior product" + routes_to_skills: [ "trust-equation", "balanced-scorecard", "scenario-planning" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] + - name: "Provider adoption resistance causing implementation failure" + description: "The product has been deployed at health systems, but providers are + not using it. The product adds steps to clinical workflow, generates + excessive alerts, requires a separate login, or simply does not fit + the way clinicians work. The health system sees low utilization data + and declines to renew." + symptoms: + - "Provider adoption rate below 30% at deployed health systems" + - "Health system CIO or CMIO citing 'low utilization' as reason for + non-renewal" + - "Provider feedback referencing 'extra clicks,' 'alert fatigue,' or + 'workflow disruption'" + - "Support tickets dominated by workflow and integration issues rather + than product defects" + routes_to_skills: [ "kotter-change-model", "systems-thinking", "net-promoter-score" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] + - name: "Patient engagement collapse undermining clinical outcomes" + description: "Patients enroll in the product but disengage within weeks. For + patient-facing healthtech (DTx, RPM, chronic disease management), + patient disengagement means the clinical intervention is not being + delivered. Without sustained engagement, outcomes cannot improve, and + the clinical value proposition collapses." + symptoms: + - "Patient engagement rate declining below 25% by week 4 + post-enrollment" + - "Clinical outcome metrics showing no improvement because patients + are not receiving the intervention" + - "Provider and payer questioning the product's clinical effectiveness + based on real-world engagement data" + - "Published clinical trial engagement rates significantly higher than + real-world deployment engagement" + routes_to_skills: [ "product-life-cycle", "net-promoter-score", "emotional-intelligence" ] + routes_to_templates: [ "action-plan", "quarterly-business-review" ] + sector_red_flags: + - "Health system contract non-renewal when provider adoption was below 40% + — signals an implementation problem, not a product problem, but the + commercial outcome is identical." + - "Payer coverage termination affecting multiple health system customers + simultaneously — a systemic reimbursement risk that can collapse revenue + rapidly." + - "Patient disengagement rate exceeding the rate observed in clinical + trials — signals that real-world conditions do not replicate trial + conditions, undermining the evidence base." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Healthtech growth stalls have structural causes absent + from other industries. Growth can stall because of regulatory bottlenecks + (waiting for FDA clearance to market the product), clinical validation + delays (study takes longer than projected), health system sales cycle + length (12-18 month cycles create lumpy, unpredictable growth), provider + change resistance (clinicians adopt slowly regardless of product quality), + or reimbursement gaps (product cleared but not covered). The growth stall + diagnostic must separate market-driven stalls from regulation-driven + stalls, evidence-driven stalls, and reimbursement-driven stalls." + additional_triage_questions: + - question: "Is the growth stall occurring pre-regulatory clearance (cannot market + the product), post-clearance but pre-reimbursement (can market but + health systems cannot bill for it), or post-reimbursement (can market + and bill but customers are not buying)?" + purpose: "Each phase has a fundamentally different growth constraint. + Pre-clearance stalls are regulatory problems. Pre-reimbursement stalls + are payer strategy problems. Post-reimbursement stalls are commercial + execution problems." + routing_impact: "Pre-clearance routes to regulatory pathway assessment and + scenario-planning for timeline extension. Pre-reimbursement routes to + payer strategy and alternative revenue model development. + Post-reimbursement routes to standard commercial growth diagnosis." + - question: "How many health system customers are in active sales pipeline, and + what is the median time-in-stage for each pipeline phase?" + purpose: "Healthtech pipeline is notoriously long. A growth stall may reflect + pipeline maturation (deals progressing slowly through clinical + evaluation, IT review, and legal) rather than pipeline weakness + (insufficient inbound demand). The distinction determines the + response." + routing_impact: "Long time-in-stage routes to sales process optimization and + health system procurement cycle alignment. Weak pipeline routes to + clinical evidence marketing and demand generation strategy." + - question: "Is the growth stall concentrated in health systems that have not seen + your clinical evidence, or in health systems that have evaluated and + declined?" + purpose: "Awareness-driven stalls (health systems do not know about the product) + are marketing problems. Evaluation-driven stalls (health systems + evaluated and said no) are evidence, pricing, or workflow problems." + routing_impact: "Awareness-driven routes to clinical conference strategy, KOL + engagement, and medical affairs investment. Evaluation-driven routes + to root cause analysis of declines — evidence gap, pricing gap, or + workflow integration gap." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory bottleneck delaying market access" + reason: "FDA clearance delays are the most common healthtech growth stall cause. + Companies that under-budgeted regulatory timeline find themselves + unable to sell while burning cash." + - diagnosis: "Clinical evidence insufficient for health system procurement" + reason: "Health system clinical review committees increasingly require published + evidence before approving new technology. Companies without + peer-reviewed publications face a wall in the sales process." + - diagnosis: "Sales cycle length creating cash flow gap" + reason: "12-18 month health system sales cycles mean that a company must fund + 12-18 months of sales effort before the first dollar of revenue. + Growth stalls often reflect pipeline maturation time, not market + rejection." + less_likely: + - diagnosis: "Product-market fit failure" + reason: "If clinical evidence shows outcome improvement and health systems are + interested but the process is slow, the problem is structural (sales + cycle, reimbursement) not fundamental (product-market fit)." + healthtech_specific_diagnoses: + - name: "Regulatory pathway failure stalling commercialization" + description: "The product requires FDA clearance but the regulatory process has + stalled — either because FDA has requested additional data, the + pre-submission meeting revealed a more complex pathway than expected, + or the company's regulatory strategy was based on incorrect + classification assumptions. Until clearance is obtained, the product + cannot be marketed for clinical use." + symptoms: + - "FDA requesting additional clinical data beyond what was planned and + budgeted" + - "Regulatory pathway reclassification (e.g., from 510(k) to De Novo) + extending timeline by 12+ months" + - "Pre-submission meeting feedback more negative than expected" + - "Regulatory timeline extending beyond the company's cash runway" + routes_to_skills: [ "scenario-planning", "vuca-framework", "systems-thinking" ] + routes_to_templates: [ "risk-assessment-brief", "strategic-analysis-one-pager" ] + - name: "Reimbursement denial blocking revenue scalability" + description: "The product has FDA clearance and health system interest, but + payers are not covering the product's clinical use case. Without + reimbursement, health systems must fund the product from operational + budgets — a much smaller and more competitive funding source than + payer reimbursement. Revenue growth is capped at what health systems + will pay out-of-pocket." + symptoms: + - "Medicare coverage determination pending or denied" + - "Commercial payers declining coverage citing insufficient evidence + or non-essential classification" + - "Health system customers requesting that the product generate + reimbursable events through existing CPT codes" + - "Revenue growth plateauing at a level consistent with health system + IT budget allocation rather than clinical service reimbursement" + routes_to_skills: + - business-model-canvas + - competitive-negotiation + routes_to_templates: [ "market-opportunity-summary", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + - name: "Provider change resistance limiting deployment expansion" + description: "The product is cleared, reimbursed, and contracted, but provider + adoption within deployed health systems is low. Clinicians are + resistant to changing established workflows, skeptical of the + product's clinical value, or overwhelmed by the current technology + burden. Growth stalls because land-and-expand within health systems + fails." + symptoms: + - "Provider adoption rate below 40% at deployed health systems despite + available training" + - "Health system expansion from pilot to enterprise blocked by low + pilot adoption metrics" + - "Provider feedback citing workflow disruption, alert fatigue, or + insufficient clinical value" + - "Clinical champions frustrated by peers' refusal to adopt" + routes_to_skills: [ "kotter-change-model", "trust-equation", "leading-through-change" ] + routes_to_templates: [ "action-plan", "new-initiative-brief" ] + sector_red_flags: + - "Regulatory clearance delayed 6+ months beyond projected timeline — + triggers cascade: delayed revenue, extended burn, potential need for + bridge financing." + - "Pipeline consisting of fewer than 10 qualified health system + opportunities — healthtech requires a larger pipeline than the close + rate suggests because health system evaluations are long and + unpredictable." + - "Zero payer coverage obtained 12+ months after FDA clearance — signals + that the clinical evidence does not meet payer standards or that the + reimbursement strategy is flawed." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Product-market fit in healthtech requires satisfying + three markets simultaneously: patients (who benefit), providers (who use), + and payers (who fund). A product can have patient-market fit (patients + love it) without provider-market fit (providers will not prescribe it) or + payer-market fit (payers will not cover it). True healthtech PMF exists + when all three stakeholders validate the product — patients engage, + providers adopt, and payers reimburse. Partial PMF is the most dangerous + state: strong signal from one stakeholder masks the absence from another." + additional_triage_questions: + - question: "Which stakeholder is validating the product and which is not — are + patients engaged but providers not prescribing, or are providers + interested but payers not covering?" + purpose: "Identifies which leg of the triple aim is failing. Patient-only + validation (engagement without provider prescription) suggests a + consumer product mislabeled as clinical. Provider-only validation + (interest without patient engagement) suggests a workflow tool that + patients do not use. Payer-only validation is impossible without + evidence." + routing_impact: "Patient without provider routes to clinical evidence + strengthening and provider engagement strategy. Provider without payer + routes to reimbursement pathway analysis. Provider without patient + routes to patient experience redesign." + - question: "Does the product's retention curve flatten — do patients and + providers who stay past an initial period continue long-term — or does + it continuously decline?" + purpose: "A flattening retention curve for both patients and providers is the + strongest healthtech PMF signal. Continuous decline in either + population indicates PMF has not been achieved." + routing_impact: "Flattening curves with low initial retention routes to + onboarding optimization. Continuously declining curves route to + fundamental value proposition reassessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "PMF for one stakeholder but not the triple aim" + reason: "Healthtech companies frequently achieve PMF with one stakeholder + (usually patients or providers) while failing with another (usually + payers). This partial PMF creates a business that generates + enthusiasm but not sustainable revenue." + - diagnosis: "Clinical evidence insufficient to validate PMF" + reason: "Unlike SaaS where retention data validates PMF, healthtech PMF requires + clinical outcome data. A product that retains users but does not + improve outcomes has consumer PMF but not clinical PMF." + less_likely: + - diagnosis: "Product is fundamentally flawed" + reason: "If any clinical stakeholder validates the product, the technology + likely works for someone. The question is usually not product + quality but clinical-commercial alignment." + healthtech_specific_diagnoses: + - name: "Triple-aim misalignment" + description: "The product satisfies one or two of the triple aim (better + outcomes, better experience, lower cost) but fails on the third. + Payers require all three. A product that improves outcomes but + increases cost will not receive broad reimbursement. A product that + reduces cost but worsens experience will not be adopted by patients or + providers." + symptoms: + - "Strong clinical outcome data but payer rejection citing + cost-effectiveness" + - "Strong patient engagement but providers reporting workflow burden" + - "Strong provider adoption but patient outcome metrics not improving" + - "Health economic analysis showing that the product's cost exceeds + the cost of the alternative it replaces" + routes_to_skills: [ "business-model-canvas", "systems-thinking", "balanced-scorecard" ] + routes_to_templates: [ "strategic-analysis-one-pager", "unit-economics-snapshot" ] + sector_red_flags: + - "Provider NPS above 40 but payer coverage denied — the product has + clinical validation but not economic validation." + - "Patient engagement above 50% but clinical outcomes not improving — the + product is engaging but not clinically effective." + - "Clinical outcomes improving but gross margin below 40% — the clinical + model is too labor-intensive for scalable delivery." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Pricing in healthtech is fundamentally + reimbursement-constrained. The diagnostic must determine whether the + pricing problem is: (1) reimbursement misalignment (product priced above + what payers will cover), (2) billing code mismatch (product's clinical + service does not map to existing CPT/HCPCS codes), (3) health system + budget constraint (product requires operational budget because no + reimbursement pathway exists), or (4) value-capture failure (product + delivers value but captures too little of it through pricing). The + standard pricing diagnosis framework (value-based pricing, competitive + pricing, cost-plus) must be adapted because the 'price' in healthtech is + often determined by CMS, not by the company." + additional_triage_questions: + - question: "Is the product's revenue dependent on payer reimbursement (billing + CPT/HCPCS codes), health system SaaS subscription, employer direct + contract, or patient self-pay?" + purpose: "Each revenue model has different pricing constraints. + Reimbursement-dependent revenue is price-capped by CMS and commercial + payer schedules. SaaS subscription is negotiated with health system IT + budgets. Employer direct pay is negotiated with benefits purchasers. + Self-pay is constrained by patient willingness to pay." + routing_impact: "Reimbursement-dependent routes to CPT code analysis and payer + rate optimization. SaaS subscription routes to health system IT budget + analysis and value demonstration. Employer direct routes to benefits + ROI analysis. Self-pay routes to consumer pricing and + willingness-to-pay research." + - question: "Have you identified the specific CPT or HCPCS codes that apply to + your product's clinical service, and have you verified the + reimbursement rates with the target payer population?" + purpose: "Many healthtech pricing problems originate in a fundamental disconnect + between the product's clinical service and the billing code system. If + no applicable code exists, or if the applicable code's reimbursement + rate is below the product's cost to deliver, the pricing problem is + structural." + routing_impact: "No applicable code routes to new code application strategy (CPT + Category III or HCPCS application) and alternative revenue model + development. Applicable code with low reimbursement routes to margin + optimization and service delivery cost reduction." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Reimbursement rate below product cost to deliver" + reason: "The most common healthtech pricing problem: the product's clinical + service maps to a CPT code that reimburses at a rate below the cost + of delivery, including clinical support staff, technology, and + overhead." + - diagnosis: "No applicable billing code exists" + reason: "Many novel healthtech products deliver clinical services that do not + map neatly to existing billing codes. Without a code, the product + must rely on health system operational budgets — a much smaller and + more competitive funding source." + less_likely: + - diagnosis: "Over-pricing relative to competition" + reason: "Healthtech pricing is typically constrained below market-clearing + levels by reimbursement rates. Over-pricing relative to competition + is less common than under-reimbursement relative to cost." + healthtech_specific_diagnoses: + - name: "Reimbursement code mismatch" + description: "The product's clinical service does not map to existing CPT or + HCPCS codes, or maps to codes that reimburse at rates far below the + product's cost of delivery. The company must either adapt its service + model to match existing codes, pursue new code creation (a 2-4 year + process), or find non-reimbursement revenue models." + symptoms: + - "Health system billing departments unable to identify applicable + codes" + - "Reimbursement revenue per patient significantly below contracted + SaaS price per patient" + - "Health systems requesting that the product be structured to + generate billable events under existing codes" + - "CPT application submitted but timeline extends 2+ years" + routes_to_skills: + - business-model-canvas + - scenario-planning + routes_to_templates: [ "unit-economics-snapshot", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "Product priced above Medicare reimbursement rate for the applicable CPT + code — health systems absorb the gap, creating adoption resistance." + - "Revenue model dependent entirely on patient self-pay for a clinical + product — this limits addressable market to patients with disposable + income and willingness to pay for healthcare out-of-pocket." + - "No reimbursement strategy articulated despite clinical product + positioning — a signal that the company has not confronted the + fundamental revenue question." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech fundraising requires demonstrating clinical + validation milestones alongside commercial traction. Health-focused + investors (Rock Health portfolio companies, a16z Bio+Health, GV Health) + apply clinical due diligence as rigorously as financial due diligence. The + diagnostic must evaluate whether the company's regulatory pathway, + clinical evidence, and reimbursement strategy are investor-ready." + additional_triage_questions: + - question: "What is your clinical validation stage — pilot data, observational + study, RCT, peer-reviewed publication, or regulatory clearance?" + purpose: "Clinical validation stage is the single most important variable in + healthtech fundraising readiness. Seed investors accept pilot data. + Series A investors expect at least observational study results. Series + B investors expect peer-reviewed publications or regulatory + clearance." + routing_impact: "Below-threshold clinical evidence routes to clinical study + design and execution planning before fundraising. At-threshold + evidence routes to investor narrative development." + - question: "Can you articulate the regulatory pathway, timeline, and cost for + your product?" + purpose: "Regulatory literacy is a gating criterion for healthtech fundraising. + Investors evaluate whether the founder understands the FDA pathway, + has budgeted appropriately, and has a realistic timeline." + routing_impact: "Unclear regulatory pathway routes to regulatory strategy + development before fundraising. Clear pathway routes to regulatory + milestone integration into pitch narrative." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical evidence gap reducing investor confidence" + reason: "The most common healthtech fundraising failure: the product shows + promising metrics but lacks the clinical evidence that + health-focused investors require. General tech investors may not + notice this gap, but they cannot help with health system + commercialization." + - diagnosis: "Regulatory risk perceived as too high" + reason: "Investors discount healthtech companies with uncertain regulatory + pathways. A company that might need a De Novo versus a 510(k) + carries significantly more risk than one with a clear + predicate-based 510(k) strategy." + less_likely: + - diagnosis: "Market too small" + reason: "Healthcare markets are enormous. 'Market too small' in healthtech + usually means the company has not articulated the reimbursement + pathway that unlocks the addressable market." + healthtech_specific_diagnoses: + - name: "Investor-clinical evidence mismatch" + description: "The company's clinical evidence stage does not match the + expectations of the target investor tier. Presenting pilot data to + Series B investors, or approaching general tech investors with a + regulatory-heavy pitch, creates a fundamental mismatch." + symptoms: + - "Health-focused investors requesting clinical data that does not + exist" + - "General tech investors unable to evaluate the clinical value + proposition" + - "Investor feedback consistently referencing 'evidence' or + 'regulatory risk' as concerns" + - "Fundraising process extending beyond 6 months without term sheet" + routes_to_skills: [ "story-structure-and-arc", "trust-equation", "scenario-planning" ] + routes_to_templates: [ "fundraising-deck-outline", "market-opportunity-summary" ] + sector_red_flags: + - "Raising Series A without any published clinical study — health-focused + investors will pass." + - "Raising with regulatory clearance timeline extending beyond 18 months — + investors see 18+ months of pre-revenue burn." + - "No clinical advisory board — signals that the founder has not engaged + the clinical community." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Revenue in healthtech decomposes along three dimensions: + revenue source (payer reimbursement, health system SaaS, employer direct, + patient self-pay), revenue driver (number of patients x revenue per + patient, or number of health systems x contract value), and revenue + quality (reimbursement-backed revenue is more durable than operational + budget allocations). The diagnostic must identify which dimension is + underperforming." + additional_triage_questions: + - question: "What percentage of revenue comes from payer reimbursement versus + health system operational budgets versus other sources?" + purpose: "Revenue mix determines durability and scalability. + Reimbursement-backed revenue scales with patient volume. Operational + budget revenue is capped by IT spending limits. The mix determines the + company's ceiling." + routing_impact: "Low reimbursement share routes to payer strategy and clinical + evidence development. High reimbursement share with low revenue routes + to patient volume and provider adoption analysis." + - question: "Is the revenue problem driven by too few customers (health systems), + too few patients per customer, or too little revenue per patient?" + purpose: "Healthtech revenue is a three-variable equation. Identifying which + variable is underperforming focuses the diagnostic." + routing_impact: "Too few customers routes to sales process and demand generation + analysis. Too few patients per customer routes to provider adoption + and implementation quality. Too little revenue per patient routes to + reimbursement and pricing analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Reimbursement underperformance" + reason: "The most common healthtech revenue problem: the product generates + clinical value but the reimbursement rate is too low, the coverage + is too narrow, or the billing process is too complex for health + system billing departments." + - diagnosis: "Low patient volume per health system customer" + reason: "Health system contracts often project patient volumes that are not + realized because provider adoption is low, patient enrollment is + slow, or the clinical use case is narrower than contracted." + less_likely: + - diagnosis: "Pricing too low" + reason: "Healthtech pricing is typically constrained by reimbursement rates. The + revenue problem is usually not pricing but volume — either patient + volume or health system customer volume." + healthtech_specific_diagnoses: + - name: "Revenue model-clinical model mismatch" + description: "The revenue model assumes one clinical delivery model, but the + actual clinical delivery requires a different model. For example: the + revenue model assumes per-patient SaaS pricing, but clinical + effectiveness requires clinician-monitored RPM — the clinician cost is + not captured in the revenue model, creating a structural margin + problem." + symptoms: + - "Gross margin declining as patient volume increases (clinical + support costs scaling linearly while revenue scales sub-linearly)" + - "Clinical team headcount growing faster than patient enrollment" + - "Health system customers requesting clinical support that exceeds + the contracted service level" + - "Clinical outcome metrics requiring higher-touch intervention than + the technology alone provides" + routes_to_skills: [ "business-model-canvas", "systems-thinking", "balanced-scorecard" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] + sector_red_flags: + - "Revenue per patient declining as the company scales — signals that + higher-acuity (higher-revenue) patients were served first and the + marginal patient generates less revenue." + - "Health system contract renewals at lower ACV than initial contracts — + signals value delivery concerns or competitive pressure on pricing." + - "More than 40% of contracted patient volume not realized — signals + provider adoption or patient enrollment failure." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech competitive threats come from four sources + beyond traditional competitors: EHR vendors building native functionality + (Epic and Oracle Health adding clinical decision support, remote + monitoring, and AI features directly into their platforms), pharmaceutical + companies funding digital companions (Pharma-sponsored DTx and patient + engagement tools), academic medical centers developing and commercializing + clinical tools, and large technology companies entering healthcare (Google + Health, Amazon Health, Apple Health). Each threat type requires a + different response." + additional_triage_questions: + - question: "Is the competitive threat from a peer healthtech startup, an EHR + vendor building native functionality, a pharma company sponsoring a + competing digital intervention, or a big tech company entering + healthcare?" + purpose: "Each threat source has different capabilities, motivations, and + vulnerabilities. Peer startups compete on evidence and execution. EHR + vendors compete on integration. Pharma competes on clinical reach and + funding. Big tech competes on data and distribution." + routing_impact: "Peer startup routes to clinical evidence differentiation and + first-mover advantage. EHR vendor routes to integration depth analysis + and partnership strategy. Pharma routes to clinical evidence + superiority and independence positioning. Big tech routes to clinical + specialization and regulatory expertise as differentiators." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "EHR vendor platform encroachment" + reason: "Epic and Oracle Health are expanding clinical functionality within + their platforms. A healthtech product that operates outside the EHR + is vulnerable to a native equivalent that requires no additional + integration, procurement, or training." + - diagnosis: "Clinical evidence leapfrog" + reason: "A competitor publishing superior clinical evidence (larger study, + higher-impact journal, better outcomes) can rapidly shift health + system and payer preferences. Clinical evidence is the primary + competitive weapon in healthtech." + less_likely: + - diagnosis: "Price-based competitive displacement" + reason: "Health systems rarely switch clinical tools based on price alone. + Clinical evidence, workflow integration, and provider satisfaction + drive switching decisions." + healthtech_specific_diagnoses: + - name: "Clinical workflow disruption from EHR-native alternative" + description: "The primary EHR vendor (Epic or Oracle Health) has released or + announced native functionality that replicates the healthtech + product's core capability. Because the native functionality is + embedded in the clinical workflow, requires no additional integration, + and is included in the existing EHR license, health systems default to + the EHR-native option — even if it is clinically inferior." + symptoms: + - "Health system prospects citing 'we will wait for Epic/Cerner to + build it' in sales conversations" + - "Existing customers asking about migration to EHR-native + alternatives" + - "EHR vendor announcing roadmap features that overlap with the + product's core functionality" + - "Pipeline deals pausing pending EHR vendor product evaluation" + routes_to_skills: [ "porters-five-forces", "disruptive-innovation", "blue-ocean-strategy" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] + sector_red_flags: + - "Epic or Oracle Health announcing a feature set that replicates the + product's core capability — the most consequential competitive threat in + healthtech." + - "A competitor publishing an RCT in NEJM or JAMA that demonstrates + superior outcomes." + - "A pharmaceutical company launching a competing digital therapeutic with + pharma-scale clinical trial funding and physician detailing + distribution." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech strategic drift often manifests as expanding + the clinical scope beyond the evidence base — pursuing additional + indications, therapeutic areas, or clinical use cases before validating + the first one. The long feedback loops in healthtech (12-24 months for + clinical studies, 6-18 months for health system sales) make drift harder + to detect and more damaging when discovered." + additional_triage_questions: + - question: "Is the product pursuing additional clinical indications or + therapeutic areas beyond the one where clinical evidence has been + established?" + purpose: "Healthtech companies are tempted to expand clinical scope before + validating the first indication. Each new indication requires + independent clinical evidence, potentially a new regulatory + submission, and new payer coverage — each representing 12-36 months of + additional investment." + routing_impact: "Premature clinical expansion routes to focus assessment and + evidence-first strategy. Evidence-validated expansion routes to + portfolio planning using growth-share-matrix." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical scope creep ahead of evidence" + reason: "Health system customers request the product for additional clinical use + cases. The company expands to satisfy customers but without the + evidence base to support the expanded claims." + - diagnosis: "Regulatory classification confusion" + reason: "As the product expands features and clinical scope, its regulatory + classification may shift — a wellness product that adds diagnostic + features may suddenly require FDA clearance." + less_likely: + - diagnosis: "Market-driven strategic shift" + reason: "Healthcare markets are large and stable. True market-driven strategic + shifts are rare — most healthtech strategic drift is internal, + driven by opportunity chasing rather than market forces." + healthtech_specific_diagnoses: + - name: "HIPAA breach response consuming strategic capacity" + description: "A data security incident involving protected health information + has consumed executive attention, engineering resources, and legal + budget. The company is in crisis response mode — regulatory + notification, patient notification, OCR investigation preparation — + and strategic initiatives have stalled." + symptoms: + - "PHI breach reported to HHS OCR" + - "Executive team spending >50% of time on breach response and + investigation" + - "Product development halted for security remediation" + - "Health system customers requesting security audit and considering + contract termination" + routes_to_skills: [ "black-swans", "vuca-framework", "systems-thinking" ] + routes_to_templates: [ "incident-postmortem", "risk-assessment-brief" ] + sector_red_flags: + - "Product marketed for clinical use cases not supported by the clinical + evidence base — creates regulatory and liability risk." + - "Three or more therapeutic areas being pursued simultaneously with + clinical evidence in none." + - "Regulatory classification shifting due to feature additions — signals + that product decisions are being made without regulatory impact + assessment." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech team dysfunction has a unique dimension: the + tension between clinical and commercial teams. Clinical team members (CMO, + clinical operations, medical affairs) prioritize patient safety, evidence + rigor, and clinical protocol adherence. Commercial team members (CEO, + sales, marketing) prioritize growth, revenue, and market expansion. When + these priorities conflict — and they inevitably do — the resolution + determines both the company's culture and its clinical integrity." + additional_triage_questions: + - question: "Is there a structural tension between the clinical team (CMO, medical + affairs) and the commercial team (CEO, sales) regarding product + direction, evidence requirements, or marketing claims?" + purpose: "Clinical-commercial tension is the healthtech-specific variant of the + SaaS product-sales tension, but with higher stakes. When commercial + pressure overrides clinical judgment, the consequences include + regulatory risk, patient safety risk, and reputational damage." + routing_impact: "Clinical-commercial misalignment routes to governance structure + assessment and clinical-commercial decision framework development." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical-commercial team misalignment" + reason: "The most common and most consequential healthtech team dysfunction. + When the CMO and CEO disagree on whether the clinical evidence is + sufficient to support a marketing claim, the resolution — and the + process for reaching it — defines the company." + less_likely: + - diagnosis: "Individual performance issues" + reason: "Healthtech team members tend to be highly motivated by the mission. + Performance issues are more often structural (unclear decision + authority between clinical and commercial) than individual." + healthtech_specific_diagnoses: + - name: "Clinical leadership void" + description: "The company lacks a credible clinical leader (CMO, VP Clinical) + with the authority to make clinical decisions. Product, regulatory, + and evidence decisions are made by non-clinical executives, leading to + clinical missteps, provider distrust, and regulatory risk." + symptoms: + - "Clinical decisions made by product managers or engineers without + clinical input" + - "No clinical advisory board or a board that meets fewer than twice + per year" + - "Provider customers expressing concern about the company's clinical + credibility" + - "Marketing materials making clinical claims not reviewed by a + clinical professional" + routes_to_skills: [ "hackman-enabling-conditions", "leadership-pipeline", "trust-equation" ] + routes_to_templates: [ "role-description-template", "hiring-scorecard" ] + sector_red_flags: + - "CMO resignation — signals irreconcilable conflict between clinical and + commercial priorities." + - "Clinical advisory board members disengaging — signals that clinical + advice is being ignored." + - "Marketing claims exceeding the clinical evidence base — signals that + commercial pressure has overridden clinical governance." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech co-founder conflicts often center on the + clinical-commercial divide — the physician co-founder prioritizes clinical + rigor and patient safety while the technology co-founder prioritizes + product development speed and market scaling. This tension is productive + when managed well (it ensures both clinical quality and commercial + viability) and destructive when it degenerates into mutual veto power." + additional_triage_questions: + - question: "Is the conflict centered on clinical evidence standards (how much + evidence is enough before scaling), product direction (clinical depth + vs. market breadth), or resource allocation (clinical R&D vs. + commercial investment)?" + purpose: "Each conflict type has a different resolution path. Evidence + disagreements require external benchmarking against health system and + payer requirements. Product direction conflicts require customer + input. Resource allocation requires financial modeling." + routing_impact: "Evidence standard conflicts route to health system and payer + requirements analysis. Product direction routes to customer discovery + and clinical advisory board input. Resource allocation routes to + financial scenario planning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical-commercial priority tension between physician and + technology co-founders" + reason: "The most common healthtech co-founder conflict pattern. The physician + founder sees every corner cut as a patient safety risk. The + technology founder sees every clinical requirement as a commercial + impediment." + less_likely: + - diagnosis: "Equity and compensation disputes" + reason: "Healthtech co-founders are often mission-driven. Equity conflicts are + less common than priority conflicts about how to pursue the + mission." + healthtech_specific_diagnoses: + - name: "Evidence-standard deadlock" + description: "The physician co-founder refuses to support commercialization + until clinical evidence meets academic standards (multi-site RCT, + peer-reviewed publication). The technology co-founder argues that + waiting for this level of evidence consumes runway and allows + competitors to establish market position. Both are partially right — + and the deadlock prevents either path from being pursued." + symptoms: + - "Product commercially available but CMO/physician co-founder + declines to endorse marketing claims" + - "Commercial launch repeatedly delayed pending 'one more study'" + - "Technology co-founder pursuing sales conversations without clinical + co-founder involvement" + - "Board unable to resolve the disagreement because both positions are + defensible" + routes_to_skills: [ "cooperative-negotiation", "evaluating-and-deciding", "scenario-planning" ] + routes_to_templates: [ "decision-journal", "quarterly-strategic-review" ] + sector_red_flags: + - "Physician co-founder publicly expressing concerns about the product's + clinical readiness — damages credibility with health system customers." + - "Technology co-founder making clinical claims without physician + co-founder endorsement — creates regulatory and liability exposure." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "reframed" + adaptation_rationale: "Market entry in healthtech is not about digital + distribution — it is about clinical validation, regulatory clearance, and + reimbursement. The question is not 'can we enter this market?' but 'do we + have the evidence, the regulatory status, and the reimbursement pathway to + enter this market sustainably?' Healthtech market entry without these + three foundations creates a business that can sell but cannot scale." + additional_triage_questions: + - question: "Does the target clinical market have established reimbursement codes, + or would entry require creating new reimbursement pathways?" + purpose: "Entering a market with established reimbursement is fundamentally + different from entering one that requires new code creation. + Established codes mean revenue is available upon launch. New codes + require 2-4 years of CMS/AMA application process." + routing_impact: "Established reimbursement routes to competitive positioning and + sales strategy. No reimbursement routes to alternative revenue model + development and reimbursement pathway timeline planning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Market entry without reimbursement foundation" + reason: "The most common healthtech market entry failure: building and clearing + a product for a clinical market where no reimbursement pathway + exists. Revenue remains limited to health system operational + budgets." + less_likely: + - diagnosis: "Market too small" + reason: "Clinical markets are large. 'Too small' usually means the company has + not identified the patient population or reimbursement pathway that + unlocks the addressable market." + healthtech_specific_diagnoses: + - name: "Regulatory pathway mismatch for target market" + description: "The company's regulatory strategy is misaligned with the target + clinical market's requirements. A product positioned for clinical + diagnosis may require PMA (not 510(k)), a product marketed to patients + directly may need different clearance than one marketed to providers, + or the regulatory classification chosen limits the clinical claims + that drive market entry." + symptoms: + - "FDA pre-submission feedback indicating a more complex pathway than + planned" + - "Clinical claims constrained by regulatory classification, limiting + the addressable market" + - "Competitors with different regulatory classifications making + broader clinical claims" + routes_to_skills: [ "scenario-planning", "first-mover-strategy", "systems-thinking" ] + routes_to_templates: [ "market-opportunity-summary", "risk-assessment-brief" ] + sector_red_flags: + - "Entering a clinical market without engaging a regulatory consultant or + performing a regulatory pathway assessment." + - "Market entry plan that does not include a reimbursement strategy — will + produce revenue ceiling surprises." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech hiring requires specialized talent that spans + the clinical-commercial divide: clinical informaticists, regulatory + affairs specialists, health economics and outcomes researchers (HEOR), and + clinical operations professionals. These roles do not exist in standard + technology company hiring playbooks. The most critical and most commonly + failed healthtech hire is the Chief Medical Officer — finding a physician + who combines clinical credibility, strategic thinking, and startup + operational capacity is rare and expensive." + additional_triage_questions: + - question: "Are you hiring clinical talent (CMO, clinical operations, medical + affairs, HEOR) or commercial/technical talent, and do you have the + domain expertise to evaluate clinical candidates?" + purpose: "Clinical hiring failures are the most expensive in healthtech. A CMO + without startup operational capacity, a clinical operations hire + without health system experience, or a HEOR professional without payer + engagement experience can set the company back 12-18 months." + routing_impact: "Clinical hiring routes to clinical advisory board-led hiring + process and specialized healthtech recruiting. Commercial/technical + hiring routes to standard hiring processes with healthtech domain + requirements." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical leadership hiring failure" + reason: "The most common and most consequential healthtech hiring mistake: + hiring a CMO from academia who lacks commercial instincts, or a CMO + from industry who lacks clinical credibility with the provider + audience." + less_likely: + - diagnosis: "Compensation competitiveness" + reason: "Clinical talent in healthtech is motivated by mission and clinical + impact. Compensation matters but is rarely the primary barrier for + CMO or clinical operations hires." + healthtech_specific_diagnoses: + - name: "Clinical-technical culture clash" + description: "Clinical hires (physicians, nurses, pharmacists) and technical + hires (engineers, product managers) operate with fundamentally + different work cultures. Clinical culture values thoroughness, + evidence, protocol adherence, and patient safety. Technology culture + values speed, iteration, experimentation, and shipping. Without + deliberate cultural integration, the two groups develop mutual + frustration that manifests as slow decisions, unresolved tensions, and + talent attrition." + symptoms: + - "Clinical team describing engineering team as 'reckless' or + 'careless with patient safety'" + - "Engineering team describing clinical team as 'blockers' or 'too + slow'" + - "Product decisions oscillating between clinical and technical + priorities without resolution framework" + - "Clinical or engineering talent leaving within first year, citing + cultural misfit" + routes_to_skills: + [ + "organisational-culture", + "psychological-safety", + "thomas-kilmann-conflict" + ] + routes_to_templates: [ "culture-values-document", "team-health-check" ] + sector_red_flags: + - "No clinical leadership (CMO or equivalent) hired by Series A — signals + that clinical governance is absent." + - "CMO or clinical leader attrition within 12 months — signals + clinical-commercial cultural incompatibility." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Operational chaos in healthtech has clinical safety + implications absent from other industries. A deployment failure, data + error, or system outage in a clinical product can affect patient care. + HIPAA compliance adds operational requirements (security monitoring, + access controls, audit logging, breach notification procedures) that do + not exist in non-health industries. The operational chaos diagnostic must + evaluate whether operational failures are creating patient safety risk." + additional_triage_questions: + - question: "Has any operational failure (system outage, data error, deployment + issue) affected clinical operations or patient care at a health system + customer?" + purpose: "Clinical operational failures are categorically different from + standard SaaS outages. A clinical decision support tool that is + unavailable during a clinical shift forces providers to fall back to + pre-technology workflows — which may not be available or may be + unfamiliar to newer staff." + routing_impact: "Clinical operational failures route to patient safety incident + review and clinical risk assessment. Non-clinical operational failures + route to standard DevOps improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "HIPAA compliance gaps creating operational burden" + reason: "Companies that did not build HIPAA compliance into their operational + foundation from day one face escalating remediation costs as they + scale — each new health system customer adds compliance + requirements." + less_likely: + - diagnosis: "Over-process" + reason: "Healthtech companies rarely have too much process. Given the regulatory + and safety requirements, the typical failure is under-process — + insufficient quality assurance, incomplete documentation, and + inadequate incident response procedures." + healthtech_specific_diagnoses: + - name: "Clinical system availability failure" + description: "The product's uptime and reliability do not meet clinical + availability standards. Health systems require near-100% availability + for clinical tools because unavailability during clinical care creates + patient safety risk. Standard SaaS uptime (99.5%) may be insufficient + for clinical applications." + symptoms: + - "System outages during clinical hours generating patient safety + concern reports" + - "Health system customers requiring SLA amendments with higher + availability guarantees and financial penalties" + - "Clinical staff creating paper-based workarounds for system + unavailability — indicating distrust of system reliability" + - "Incident rate exceeding health system vendor management thresholds" + routes_to_skills: [ "systems-thinking", "kaizen-bpr", "balanced-scorecard" ] + routes_to_templates: [ "incident-postmortem", "action-plan" ] + sector_red_flags: + - "Any system outage that affected active patient care — requires patient + safety incident review and root cause analysis." + - "HIPAA security assessment identifying critical gaps — requires + immediate remediation before additional health system deployments." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Leadership crises in healthtech carry additional + dimensions: a CEO who loses the trust of the clinical advisory board, a + CMO who resigns citing ethical concerns, or a leadership team that is + perceived as prioritizing commercial interests over patient welfare can + trigger cascading damage — health system customers re-evaluate contracts, + clinical talent departs, and the company's clinical reputation suffers." + additional_triage_questions: + - question: "Has the leadership crisis affected the clinical advisory board's + engagement, the CMO's confidence in the product's safety, or health + system customers' trust in the company's clinical commitment?" + purpose: "Leadership crises in healthtech can cascade into clinical credibility + crises. If the clinical advisory board disengages, the company loses + its clinical governance infrastructure." + routing_impact: "Clinical credibility impact routes to clinical governance + restoration and advisory board re-engagement. No clinical credibility + impact routes to standard leadership crisis resolution." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical leadership crisis" + reason: "The departure or disengagement of the CMO or clinical advisory board + creates a credibility vacuum that is uniquely damaging in + healthtech." + less_likely: [] + healthtech_specific_diagnoses: [] + sector_red_flags: + - "Clinical advisory board members resigning — signals that clinical + governance has failed." + - "CMO expressing public concerns about patient safety — existential + reputational risk." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech faces a legitimate tension between decision + speed and clinical caution. Some decisions that would be 'just ship it' in + SaaS require deliberation in healthtech because they affect patient care. + The diagnostic must distinguish between appropriate clinical caution + (deliberation that protects patients) and decision paralysis (inaction + that delays value without protecting anyone)." + additional_triage_questions: + - question: "Is the delayed decision one that could affect patient safety if made + incorrectly, or is it a commercial or operational decision with no + clinical implications?" + purpose: "Clinical decisions merit deliberation proportional to their patient + safety impact. Commercial decisions should not be held to the same + standard — the opportunity cost of delay is real." + routing_impact: "Clinical decisions route to risk-benefit analysis with clinical + advisory input. Commercial decisions route to bias-toward-action with + reversibility assessment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical caution masquerading as decision paralysis" + reason: "In healthtech, some apparent paralysis is actually appropriate caution + — the CMO delaying a product release pending additional safety + review is exercising clinical judgment, not avoiding decisions." + less_likely: + - diagnosis: "Insufficient information" + reason: "Healthtech companies typically have more information than they can + process — clinical data, regulatory guidance, payer feedback. The + problem is usually synthesis, not data availability." + healthtech_specific_diagnoses: [] + sector_red_flags: + - "Regulatory submission delayed more than 6 months beyond readiness due + to internal disagreement — the opportunity cost of delay in regulatory + timeline is severe." + - "Product decisions requiring consensus from clinical, regulatory, + commercial, and technical teams simultaneously — a sign of unclear + decision authority." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Innovation in healthtech faces a unique constraint: + regulatory requirements can slow the pace of product evolution. Changes to + FDA-cleared products may require supplemental submissions. Clinical + evidence requirements mean that new features with clinical claims must be + validated before marketing. The diagnostic must distinguish between + regulatory-constrained innovation (slow but appropriate) and + organizational innovation failure (slow due to internal dysfunction)." + additional_triage_questions: + - question: "Is the innovation constraint regulatory (changes require FDA + submissions or clinical validation) or organizational (the team is not + generating or prioritizing innovative ideas)?" + purpose: "Regulatory innovation constraints are structural and cannot be + 'solved' — they must be designed around. Organizational innovation + constraints are addressable through process and culture changes." + routing_impact: "Regulatory constraint routes to predetermined change control + planning and innovation within cleared indications. Organizational + constraint routes to standard innovation cultivation approaches." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Regulatory burden consuming innovation capacity" + reason: "Post-market surveillance, adverse event reporting, and regulatory + submission preparation consume engineering and clinical resources + that would otherwise fund innovation." + less_likely: + - diagnosis: "Lack of creative talent" + reason: "Healthtech teams are typically highly qualified and intrinsically + motivated by the mission. Innovation failure is more often + structural than talent-driven." + healthtech_specific_diagnoses: + - name: "Clinical evidence treadmill" + description: "The company must continuously generate new clinical evidence to + maintain and expand market position — but the evidence generation + process consumes the R&D resources that would fund product innovation. + The company is trapped in a cycle of proving what it has rather than + building what comes next." + symptoms: + - "More than 50% of clinical R&D budget allocated to studies + validating existing features rather than developing new + capabilities" + - "Competitor product innovation outpacing the company despite + inferior current evidence" + - "Clinical team overwhelmed by study management, data collection, and + publication preparation" + - "No product roadmap items beyond evidence generation for current + capabilities" + routes_to_skills: [ "eisenhower-matrix", "balanced-scorecard", "growth-share-matrix" ] + routes_to_templates: [ "quarterly-strategic-review", "new-initiative-brief" ] + sector_red_flags: + - "No product capability additions in 12+ months despite active + engineering team — resources consumed by maintenance, compliance, and + evidence generation." + - "Competitors launching features that health system customers request — + signals innovation gap." + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech partnerships are ecosystem-critical: EHR + vendor partnerships determine market access, pharmaceutical company + partnerships fund clinical studies and provide distribution, health system + partnerships provide clinical validation sites, and payer partnerships + enable reimbursement. Each partnership type has different power dynamics + and risk profiles." + additional_triage_questions: + - question: "Is this a technology partnership (EHR integration), a clinical + validation partnership (health system study site), a distribution + partnership (pharma or health plan), or a data partnership (clinical + data access)?" + purpose: "Each healthtech partnership type has unique dynamics. EHR partnerships + are gatekeeper relationships. Health system partnerships are clinical + credibility relationships. Pharma partnerships provide funding but may + create independence concerns. Data partnerships raise HIPAA compliance + requirements." + routing_impact: "EHR partnership routes to integration strategy and vendor + relationship management. Health system partnership routes to clinical + study design and mutual publication agreements. Pharma partnership + routes to independence governance and conflict-of-interest management. + Data partnership routes to HIPAA compliance and data use agreement + structuring." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "EHR vendor dependency creating existential risk" + reason: "A healthtech company that depends on Epic or Oracle Health integration + for market access is in a structurally dependent relationship. The + EHR vendor can change integration policies, launch competing + functionality, or deprioritize the integration partnership." + less_likely: + - diagnosis: "Partnership value misalignment" + reason: "Healthcare partnerships tend to be well-aligned on patient outcomes, + even when commercial interests diverge. The shared mission provides + a foundation for partnership that other industries lack." + healthtech_specific_diagnoses: + - name: "Pharma partnership independence erosion" + description: "A pharmaceutical company partnership provides valuable funding, + distribution, or clinical study support, but the partnership creates + perceived or actual conflicts of interest. Health systems and + providers may question whether the healthtech product serves patient + interests or pharma commercial interests. The partnership that enables + growth simultaneously undermines clinical credibility." + symptoms: + - "Health system customers expressing concern about pharma influence + on clinical recommendations" + - "Clinical advisory board members questioning independence from + pharma partner" + - "Product roadmap influenced by pharma partner's commercial + priorities rather than clinical evidence" + - "Provider adoption declining after pharma partnership announcement" + routes_to_skills: + [ + "trust-equation", + "prisoners-dilemma-and-cooperation", + "information-asymmetry" + ] + routes_to_templates: [ "partnership-memo", "risk-assessment-brief" ] + sector_red_flags: + - "EHR vendor partnership agreement with exclusivity clauses that limit + future strategic options." + - "Pharma partnership that influences clinical content or recommendations + — destroys provider trust." + - "Health system research partnership with publication veto rights — + undermines evidence credibility." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Communication breakdowns in healthtech have clinical + safety implications. Miscommunication between clinical and engineering + teams about product behavior can result in clinical tools that function + differently from what clinicians expect. Miscommunication between the + company and health system customers about product capabilities can lead to + clinical decisions based on incorrect assumptions about the product's + scope or accuracy." + additional_triage_questions: + - question: "Has a communication breakdown between the clinical team and the + engineering team resulted in a product that behaves differently from + what clinicians expect or what clinical documentation describes?" + purpose: "Clinical-engineering communication failures can create patient safety + risk if the product's clinical behavior diverges from what providers + have been trained to expect." + routing_impact: "Clinical-engineering communication gaps route to clinical + requirements documentation improvement and cross-functional review + processes. Non-clinical communication issues route to standard + communication improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Clinical-technical translation failure" + reason: "Clinical requirements expressed in medical terminology may be + misinterpreted by engineering teams. Engineering constraints + expressed in technical terminology may not convey clinical + implications to the clinical team." + less_likely: [] + healthtech_specific_diagnoses: [] + sector_red_flags: + - "Product clinical documentation inconsistent with actual product + behavior — a patient safety and regulatory risk." + - "Health system customers reporting product behavior that surprises + clinical staff — indicates training or documentation failure." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech negotiations get stuck in characteristic ways: + health system procurement processes that require clinical evaluation + committee approval (adding 3-6 months), IT security reviews that demand + HITRUST or SOC 2 certification (adding 2-4 months if not already + obtained), legal reviews requiring HIPAA-compliant BAA terms, and payer + contract negotiations that require clinical evidence dossier review." + additional_triage_questions: + - question: "Is the negotiation stuck at clinical evaluation (clinical review + committee), IT/security review (HIPAA, SOC 2, HITRUST assessment), + legal review (BAA, data use agreement), or commercial terms (pricing, + contract structure)?" + purpose: "Each health system procurement gate has different resolution + strategies. Clinical committee stalls require evidence. IT stalls + require certifications. Legal stalls require standardized agreements. + Commercial stalls require pricing creativity." + routing_impact: "Clinical committee stall routes to evidence strengthening and + clinical champion engagement. IT security stall routes to + certification acceleration and pre-prepared security documentation. + Legal stall routes to BAA template preparation. Commercial stall + routes to pricing restructuring." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "IT security review blocking the deal" + reason: "Health system IT security reviews are increasingly rigorous. HITRUST + CSF certification or SOC 2 Type II is becoming a prerequisite, not a + nice-to-have. Companies without these certifications face 2-6 month + deal delays." + - diagnosis: "Clinical evaluation committee requiring additional evidence" + reason: "Health system clinical review committees evaluate new technology with + the same rigor they apply to clinical protocol changes. Insufficient + evidence stalls the evaluation, sometimes indefinitely." + less_likely: + - diagnosis: "Price disagreement" + reason: "Healthtech negotiations rarely stall on price alone — they stall on + clinical evidence, security certification, or contractual terms. + Price is usually the last and easiest issue to resolve." + healthtech_specific_diagnoses: [] + sector_red_flags: + - "Deals stalling 60+ days in IT security review — indicates the company + needs HITRUST or SOC 2 certification to unblock the pipeline." + - "Clinical evaluation committee requesting a pilot study before + contracting — adds 3-12 months to the sales cycle." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Healthtech culture erosion carries patient safety + consequences. A culture that deprioritizes clinical rigor, tolerates + shortcuts in evidence generation, or allows commercial pressure to + override clinical judgment creates conditions where patient harm becomes + more likely. The most dangerous form of healthtech culture erosion is the + normalization of clinical corners being cut — each small compromise + establishes a precedent for the next, until the cumulative effect creates + serious clinical risk." + additional_triage_questions: + - question: "Has the company's culture shifted from 'patient outcomes first' to + 'growth first' — and do clinical team members feel empowered to + challenge decisions that they believe compromise patient safety?" + purpose: "The health of the patient-safety culture is the most consequential + cultural metric in healthtech. When clinical team members feel unable + to raise safety concerns, the company has lost its most important + cultural asset." + routing_impact: "Patient-safety culture erosion routes to psychological-safety + assessment and clinical governance restructuring. Non-safety culture + issues route to standard culture improvement." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Commercial pressure eroding clinical culture" + reason: "As healthtech companies face growth pressure from investors and board + members, the temptation to deprioritize clinical rigor in favor of + commercial velocity increases. This erosion is gradual and often + unrecognized until a clinical incident reveals the accumulated + risk." + less_likely: + - diagnosis: "Growth outpacing culture infrastructure" + reason: "Healthtech companies grow more slowly than consumer tech, providing + more time to develop culture. When culture erodes, the cause is + usually pressure, not pace." + healthtech_specific_diagnoses: + - name: "Clinical integrity erosion" + description: "The company's commitment to clinical rigor has eroded under + commercial pressure. Evidence standards have been relaxed, marketing + claims have crept beyond the evidence base, clinical advisory board + input is being ignored, and the CMO or clinical leadership feels + unable to enforce clinical standards. The company has not yet + experienced a patient safety incident, but the conditions for one are + developing." + symptoms: + - "Clinical team members expressing private concern about evidence + standards but not raising them formally" + - "Marketing materials making claims that the clinical team would not + endorse if asked directly" + - "Clinical advisory board meetings becoming shorter, less + substantive, or less frequent" + - "Commercial milestones being celebrated while clinical milestones + are treated as obstacles" + - "New hires describing the culture as 'a tech company that happens to + be in health' rather than 'a health company that uses technology'" + routes_to_skills: + [ + "psychological-safety", + "purpose-driven-leadership", + "organisational-culture" + ] + routes_to_templates: [ "culture-values-document", "risk-assessment-brief" ] + sector_red_flags: + - "Clinical team attrition above 20% annually — the most sensitive + indicator of clinical culture erosion." + - "Clinical advisory board members declining to participate in marketing + or sales activities — signals concern about clinical integrity." + - "Any instance of a clinical safety concern being overridden by + commercial pressure without documented clinical review — this is the + sentinel event that predicts future patient harm." diff --git a/plugins/foreman/content/industry-packs/healthtech/healthtech-skill-overlays.yaml b/plugins/foreman/content/industry-packs/healthtech/healthtech-skill-overlays.yaml new file mode 100644 index 0000000..5ed8341 --- /dev/null +++ b/plugins/foreman/content/industry-packs/healthtech/healthtech-skill-overlays.yaml @@ -0,0 +1,1505 @@ +# Healthtech Industry Pack — Skill Overlays +# +# For 35 of the 158 Foreman skills, this file provides healthtech-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add a healthtech lens. +# +# PATIENT SAFETY PRINCIPLE: Every overlay addresses how patient safety shapes the +# framework's application. Healthtech is uniquely constrained by the clinical +# obligation to "first, do no harm." Unlike fintech (where the worst outcome is +# financial loss) or SaaS (where the worst outcome is business failure), healthtech +# errors can harm or kill patients. This obligation pervades every strategic +# decision — from pricing to competitive positioning to go-to-market. +# +# TRIPLE STAKEHOLDER PRINCIPLE: Healthtech must satisfy three stakeholders +# simultaneously — patients (who receive care), providers (who deliver care), +# and payers (who fund care). The "triple aim" of better outcomes, better +# experience, and lower cost must be addressed in every framework application. +# +# Selection criteria for the 35 skills: +# - Frameworks with direct healthtech application (strategy, pricing, trust, growth) +# - Game theory skills (regulatory strategy, payer negotiation, provider adoption) +# - Decision and thinking skills (clinical risk-weighted decision-making) +# - Negotiation skills (health system deals, payer contracts, regulatory engagement) +# - Leadership skills most affected by clinical culture and safety obligations +# - AI/data skills (clinical AI, algorithmic fairness, FDA AI/ML guidance) +# +# Relevance tiers: +# critical — The healthtech overlay materially changes how the skill is applied. +# The skill executor should always surface healthtech context. +# high — Healthtech context adds significant value. Surface when relevant. +# moderate — Useful healthtech framing but the base skill works well as-is. + +pack_metadata: + sector: "healthtech" + display_name: "Healthtech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (18 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Porter's Five Forces in healthtech are dominated by a force + the original model does not explicitly name: regulatory power. Buyer power + is concentrated not in patients but in health system procurement + committees and payer organizations — both operate with institutional + purchasing processes that take 6-18 months. Threat of new entrants is + suppressed by regulatory barriers (FDA clearance, HIPAA compliance, + clinical evidence requirements) that cost $500K-$20M to cross. Supplier + power concentrates in EHR vendors (Epic and Oracle Health control 60%+ of + the hospital market), clinical data partners, and specialized clinical + talent. Substitutes include not just competing digital products but the + status quo of manual clinical processes — the most powerful 'competitor' + in healthtech is 'do nothing differently.' Rivalry intensity is shaped by + clinical evidence: the company with the strongest published outcomes data + wins, regardless of product polish." + healthtech_anti_patterns: + - "Treating the patient as the buyer. In most healthtech business models, + the buyer is the health system (who procures the technology), the payer + (who reimburses for its use), or the employer (who contracts for + employee health benefits). The patient is the beneficiary, not the + purchaser. Misidentifying the buyer distorts every strategic decision." + - "Underestimating the power of EHR vendors as suppliers. Epic and Oracle + Health (Cerner) are not neutral platforms — they are gatekeepers who + control clinical workflow access. Their app marketplaces, integration + policies, and strategic priorities determine which healthtech products + can reach providers." + - "Ignoring 'do nothing' as the strongest substitute. Health systems adopt + new technology slowly because the cost of change (workflow disruption, + training, clinical risk) often exceeds the perceived benefit of + adoption. The five forces analysis must quantify the switching cost from + current workflows, not just from competing products." + healthtech_example: "A clinical decision support startup applies Porter's Five + Forces and discovers that its apparent competitive advantage — superior AI + accuracy — is irrelevant to the buying decision. Buyer power analysis + reveals that health system procurement committees prioritize EHR + integration depth and clinical evidence level over algorithmic + performance. Supplier power analysis shows that Epic's integration + policies effectively determine market access. The threat of substitutes + reveals that 70% of target clinicians use a combination of UpToDate, peer + consultation, and clinical experience as their 'decision support tool' — + and they are satisfied with it. This analysis pivots the strategy from AI + performance marketing to deep Epic integration, published clinical + evidence, and workflow time-savings messaging." + benchmark_references: + [ + "clinical-workflow-integration-score", + "provider-adoption-rate", + "sales-cycle-length" + ] + + - skill: "blue-ocean-strategy" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Blue ocean strategy in healthtech must navigate a unique + constraint: you cannot create an uncontested market space by bypassing + clinical evidence, regulatory requirements, or reimbursement pathways. The + most successful healthtech blue oceans are found in therapeutic areas that + incumbent health IT ignores (behavioral health, musculoskeletal care, + chronic pain), in care settings that existing technology does not serve + (home-based care, rural health, community health centers), or in + reimagining the care delivery model itself (asynchronous care, + AI-augmented diagnosis, prescription digital therapeutics). The strategy + canvas must include a clinical evidence axis — products that create blue + oceans through evidence-based clinical differentiation build durable moats + that marketing-led differentiation cannot replicate." + healthtech_anti_patterns: + - "Pursuing a blue ocean that exists because the therapeutic area lacks + reimbursement. Some clinical areas are uncontested not because + competitors overlooked them but because payers do not cover + interventions in that space. A blue ocean without a reimbursement + pathway is a desert." + - "Creating uncontested space by avoiding FDA regulation. Products + marketed as 'wellness' to sidestep regulatory requirements sacrifice the + clinical credibility that health systems and payers require. The + regulatory exemption that enabled the blue ocean also limits the + addressable market." + - "Confusing consumer health engagement with clinical blue ocean. + Consumer-facing health apps operate in a different market than clinical + healthtech. A beautifully designed wellness app is not competing in the + same ocean as a clinically validated diagnostic tool." + healthtech_example: "Pear Therapeutics created a blue ocean in behavioral health + by pursuing FDA clearance for prescription digital therapeutics — a + category that did not exist. Instead of competing with the hundreds of + unregulated mental health apps, Pear obtained De Novo FDA authorization + for reSET (substance use disorder) and reSET-O (opioid use disorder), + creating a new category: software that is prescribed like a drug, covered + by insurance, and supported by RCT evidence. The blue ocean was not + 'digital mental health' (crowded) but 'FDA-cleared, reimbursable, + prescription software for substance use disorders' (uncontested). The + regulatory pathway that competitors avoided became the moat." + benchmark_references: + [ + "clinical-validation-stage", + "regulatory-approval-status", + "payer-reimbursement-rate" + ] + + - skill: "business-model-canvas" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "The Business Model Canvas for healthtech demands a + triple-stakeholder lens across every block. Value Proposition must + articulate separate value for patients (better outcomes, better + experience), providers (clinical workflow improvement, reduced burden), + and payers (cost reduction, quality improvement). Customer Segments must + identify the buyer (health system, payer, employer, patient) and + distinguish them from the user (provider, patient) and the beneficiary + (patient). Channels must account for health system procurement processes, + EHR marketplace distribution, payer contracting, and clinical society + endorsement. Revenue Streams must distinguish between payer reimbursement + (CPT/HCPCS coded), health system SaaS fees, employer direct contracts, and + patient self-pay. Key Activities must include clinical validation + (evidence generation is a core business activity, not R&D overhead), + regulatory affairs, and HIPAA compliance. Key Resources include clinical + evidence, regulatory clearances, clinical advisory board relationships, + and payer contracts — all of which are non-replicable assets." + healthtech_anti_patterns: + - "Designing the canvas with the patient as the only customer. The patient + is the ultimate beneficiary, but the customer (who pays) is typically + the health system, the payer, or the employer. A canvas that ignores the + buyer's needs will produce a product that patients love but no one + procures." + - "Omitting clinical evidence generation from Key Activities. In + healthtech, generating and publishing clinical evidence is as critical + as building the product itself. Companies that treat evidence as an + afterthought discover that sales stall when clinical review committees + ask for data." + - "Treating regulatory compliance as a Cost Structure line item rather + than a Key Activity and Key Resource. Regulatory clearance is an asset + that enables the business — a competitive moat, not an expense to + minimize." + healthtech_example: "A remote patient monitoring startup maps its Business Model + Canvas and discovers a critical misalignment: the Value Proposition + emphasizes patient engagement features, but the Customer (health system) + evaluates based on clinical outcome improvement and EHR integration, while + the Payer evaluates based on cost avoidance (reduced ED visits, avoided + hospitalizations). The canvas redesign creates three aligned value + propositions: patient-facing (convenient monitoring with personalized + insights), provider-facing (ambient data collection that reduces + documentation burden), and payer-facing (demonstrated 25% reduction in + preventable hospitalizations with published evidence). Revenue Streams + shift from patient subscription to payer reimbursement via RPM CPT codes + (99453, 99454, 99457, 99458), tripling the per-patient revenue and + removing the patient willingness-to-pay constraint." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "clinical-validation-stage" + ] + + - skill: "four-ps-marketing" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "The Four Ps in healthtech operate under constraints that + fundamentally differ from consumer or enterprise software. Product is + subject to FDA regulation — changes to a cleared device require regulatory + impact assessment, and marketing claims must be consistent with the + cleared indication for use. Price in healthtech is often not + market-determined but reimbursement-determined: CPT codes, DRG payments, + and payer fee schedules set the effective price ceiling regardless of the + product's value. Place (distribution) runs through health system + procurement, EHR marketplaces, clinical society endorsements, and payer + formularies — not app stores, content marketing, or outbound sales. + Promotion faces strict constraints: FDA labeling requirements limit what + can be claimed, FTC health advertising rules prohibit unsubstantiated + claims, and clinical audiences respond to peer-reviewed evidence and key + opinion leader endorsement, not marketing copy." + healthtech_anti_patterns: + - "Setting price based on willingness-to-pay surveys or competitor + matching. In healthtech, the price ceiling is often the reimbursement + rate for the relevant CPT or HCPCS code. Pricing above reimbursement + means the health system absorbs the gap — a losing proposition for + adoption." + - "Treating consumer digital marketing as the distribution strategy. + Health system buyers do not discover clinical tools through Google ads + or content marketing. They discover them through clinical conferences, + peer publications, EHR marketplace listings, and clinical advisory + network recommendations." + - "Making clinical claims in marketing materials that exceed the evidence + base or the FDA-cleared indications. This triggers FDA enforcement risk, + FTC action, and — most damaging — loss of credibility with the clinical + audience that evaluates claims with scientific rigor." + healthtech_example: "A digital therapeutics company applies the Four Ps and + restructures its entire go-to-market. Product: they scope the product to + match the FDA-cleared indication exactly, resisting feature creep that + would trigger a new regulatory submission. Price: they align pricing to + the CPT code reimbursement rate for remote therapeutic monitoring (99457, + 99458), ensuring health systems can bill payers for the product's use + without margin loss. Place: they abandon direct-to-consumer advertising + and instead pursue Epic App Orchard listing, clinical conference + presentations, and health plan formulary inclusion. Promotion: they + replace feature-focused marketing with an evidence brief summarizing their + published RCT results, distributed through medical affairs channels rather + than marketing channels." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "provider-adoption-rate" + ] + + - skill: "net-promoter-score" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "NPS in healthtech must be measured separately for each + stakeholder: patients, providers, and payer partners. Provider NPS is the + most commercially consequential because provider word-of-mouth drives + adoption across health systems — a physician champion at one hospital who + recommends the product to colleagues at the next health system is the most + powerful sales channel in healthcare. Patient NPS is clinically + consequential because dissatisfied patients disengage, and disengagement + means the clinical intervention stops. Payer NPS matters for contract + renewal but is rarely measured. NPS surveys in healthtech must be + triggered by clinical milestones (first clinical encounter with the + product, 30-day check-in, treatment completion) rather than arbitrary time + intervals, and must be designed for diverse health literacy levels." + healthtech_anti_patterns: + - "Measuring a single NPS score that blends patients and providers. These + populations have fundamentally different relationships with the product, + different satisfaction drivers, and different impact on the business. + Blended NPS obscures both signals." + - "Optimizing patient NPS by removing clinical friction. Some clinical + friction is necessary — adherence reminders, symptom tracking + requirements, and escalation protocols serve patient safety even when + they reduce satisfaction. NPS optimization that compromises clinical + protocols is dangerous." + - "Using NPS testimonials as clinical evidence. Anecdotal patient + satisfaction is not the same as clinical validation. Investors, payers, + and regulators evaluate evidence, not testimonials. Conflating the two + undermines credibility with clinical audiences." + healthtech_example: "A chronic disease management platform segments NPS and + discovers a dangerous gap: patient NPS is 65 (strong) but provider NPS is + -12 (deeply negative). Investigation reveals that patients love the app's + engagement features, but providers are frustrated by alert fatigue — the + system generates too many low-priority clinical alerts that interrupt + workflow. The provider NPS insight triggers a clinical alert redesign that + reduces alert volume by 70% while maintaining safety-critical escalations. + Provider NPS rises to 35 within one quarter, and the health system expands + from a pilot deployment to enterprise-wide licensing." + benchmark_references: [ "provider-nps", "patient-satisfaction-score", "provider-adoption-rate" ] + + - skill: "product-life-cycle" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "The product lifecycle in healthtech is fundamentally slower + than in software because regulatory requirements create stage gates + between lifecycle phases. Introduction requires not just product launch + but regulatory clearance, clinical evidence generation, and payer + reimbursement — each adding 6-24 months. Growth is constrained by health + system sales cycles (6-18 months per customer) and implementation + timelines (1-12 months per deployment). Maturity arrives when the clinical + evidence base is well-established, reimbursement is broadly available, and + the technology is integrated into clinical guidelines. Decline in + healthtech is often triggered not by technology obsolescence but by new + clinical evidence that a competing intervention is superior, or by + regulatory changes that alter the competitive landscape. The critical + insight for healthtech is that clinical evidence generates compounding + returns — the lifecycle can be extended almost indefinitely if the company + continues to publish outcomes data." + healthtech_anti_patterns: + - "Applying consumer technology lifecycle expectations to healthtech. + Products that achieve mass adoption in 12 months in consumer software + may take 5-7 years to reach the same adoption level in healthcare. This + is not failure — it is the structural reality of clinical adoption." + - "Treating regulatory clearance as the product launch. Clearance is the + beginning of commercialization, not the end of development. Post-market + surveillance, real-world evidence generation, and ongoing clinical + validation continue throughout the lifecycle." + - "Assuming that a clinically validated product is immune to lifecycle + decline. New clinical evidence — even evidence about competing + approaches — can rapidly shift clinical guidelines and render a + previously dominant product obsolete." + healthtech_example: "A telemedicine platform applies product lifecycle analysis + and recognizes that its core video visit product has reached maturity — + adoption plateaued during COVID and is now declining as health systems + rebalance toward in-person care. Rather than defending the mature product, + the company identifies that asynchronous care (store-and-forward clinical + consultations) is in the Introduction phase with growing clinical evidence + and emerging reimbursement. They allocate 60% of R&D to asynchronous care + capabilities while maintaining the video visit product as a cash cow that + funds the transition." + benchmark_references: + [ + "provider-adoption-rate", + "clinical-validation-stage", + "monthly-active-patients" + ] + + - skill: "growth-share-matrix" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "The BCG Growth-Share Matrix maps to healthtech product + portfolios with an essential modification: market share in healthtech is + measured not by revenue share but by clinical evidence share and + formulary/guideline inclusion. A Star is a product line with strong + clinical evidence in a growing therapeutic area. A Cash Cow is a product + with established reimbursement and embedded health system integration in a + mature clinical area. Question Marks are products in emerging therapeutic + areas with promising but unproven evidence. Dogs are products in declining + therapeutic areas or those that failed to achieve clinical validation. The + matrix is particularly useful for multi-product healthtech companies + deciding where to invest clinical R&D resources." + healthtech_anti_patterns: + - "Measuring market share by revenue alone. In healthtech, clinical + evidence share (number and quality of publications, guideline mentions, + key opinion leader endorsement) is a leading indicator that predicts + revenue share 12-24 months in advance." + - "Killing 'Dog' product lines that serve a patient safety function. Some + low-growth, low-share products in healthtech serve critical but small + patient populations. Discontinuing them has ethical implications that do + not arise in other industries." + - "Investing in Stars without ensuring clinical evidence keeps pace with + growth. Rapid commercial scaling ahead of clinical evidence creates + vulnerability — a competitor who publishes superior outcomes data can + displace a market leader regardless of installed base." + healthtech_example: "A digital health company with products across diabetes + management (Star — growing market, strong RCT evidence), hypertension + monitoring (Cash Cow — mature market, established reimbursement), mental + health screening (Question Mark — growing market, pilot data only), and + weight management (Dog — crowded market, weak evidence) uses the matrix to + allocate clinical R&D. They fund a multi-site RCT for mental health + screening (to determine if it becomes a Star or is divested) while + maintaining the diabetes product's evidence advantage and harvesting + hypertension monitoring revenue to fund the portfolio." + benchmark_references: + [ + "clinical-validation-stage", + "monthly-active-patients", + "revenue-per-patient-per-month" + ] + + - skill: "disruptive-innovation" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Healthtech is the canonical domain for disruptive + innovation with a safety constraint. Disruption in healthcare follows a + specific pattern: moving clinical capabilities from higher-cost settings + to lower-cost settings (hospital to clinic, clinic to home, home to + self-care) and from specialist-dependent to technology-enabled + (radiologist interpretation to AI-assisted screening, physician diagnosis + to nurse-led with decision support). The disruption trajectory is limited + by clinical safety — you cannot disrupt a care setting if the lower-cost + alternative compromises patient outcomes. The most successful healthtech + disruptors achieve equivalent or superior clinical outcomes at lower cost + and greater convenience, validated through rigorous clinical studies. This + evidence-validated disruption is the only sustainable path." + healthtech_anti_patterns: + - "Attempting to disrupt clinical processes without clinical evidence that + the disruption is safe. 'Move fast and break things' in healthcare means + patients get hurt. Every disruption of a clinical process requires + evidence that patient outcomes are maintained or improved." + - "Disrupting the provider's role without provider involvement in the + design. Healthtech products that attempt to disintermediate physicians + face fierce resistance and often fail clinically because they lack the + clinical nuance that providers contribute." + - "Assuming that consumer adoption is sufficient validation. Patients + adopting a health app does not validate clinical effectiveness. Consumer + popularity and clinical efficacy are independent dimensions." + healthtech_example: "Livongo disrupted chronic disease management by moving + continuous glucose monitoring and behavioral intervention from the + endocrinologist's office to the patient's home. The disruption was + validated through clinical studies showing equivalent or improved A1C + outcomes at 30% lower cost. Critically, Livongo did not disintermediate + endocrinologists — it complemented their care by providing continuous data + between visits. The disruption's safety was evidence-validated, and its + economic model was reimbursement-ready. This combination — clinically + validated, provider-complementary, payer-attractive — is the healthtech + disruption template." + benchmark_references: + [ + "patient-outcomes-improvement", + "revenue-per-patient-per-month", + "payer-reimbursement-rate" + ] + + - skill: "balanced-scorecard" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "The Balanced Scorecard for healthtech requires a fifth + perspective beyond the original four: Clinical Outcomes. Financial: + revenue, gross margin, reimbursement rate, burn rate. Customer: must be + split into provider satisfaction and patient satisfaction, tracked + independently. Internal Process: clinical workflow integration, regulatory + milestone progress, implementation velocity, HIPAA compliance posture. + Learning & Growth: clinical evidence pipeline, regulatory capability + development, clinical advisory board strength. Clinical Outcomes: patient + outcomes improvement, clinical evidence strength, adverse event rate, + patient safety incident rate. This fifth perspective is non-negotiable — + it is the ethical and commercial foundation of the business." + healthtech_anti_patterns: + - "Omitting the Clinical Outcomes perspective. A healthtech balanced + scorecard that does not track patient outcomes is equivalent to a + manufacturing scorecard that does not track product quality — the + omission eventually manifests as catastrophic failure." + - "Subordinating clinical metrics to financial metrics. In healthtech, + clinical outcomes lead financial outcomes by 12-24 months. Declining + outcome metrics predict declining revenue, not the reverse. The + scorecard must reflect this causal hierarchy." + - "Tracking only lagging indicators. Healthtech scorecards must include + leading indicators for clinical risk: adverse event near-misses, patient + safety concern reports, and clinical protocol deviation rates. By the + time a lagging indicator reveals a clinical problem, patients may + already have been harmed." + healthtech_example: "A remote patient monitoring company implements a + five-perspective balanced scorecard: Financial (RPM reimbursement revenue, + gross margin, CAC payback), Provider (provider NPS, provider adoption + rate, clinical workflow integration score), Patient (patient engagement + rate, patient satisfaction, monthly active patients), Internal Process + (implementation time to value, HIPAA compliance score, EHR integration + coverage), Clinical Outcomes (30-day readmission reduction, A1C + improvement, patient safety incident rate). The scorecard reveals that + financial metrics are strong but clinical outcome improvement has + plateaued — the product is generating revenue from RPM billing codes but + not delivering the outcome improvement that sustains long-term payer + support. This triggers an R&D reallocation toward clinical effectiveness." + benchmark_references: + [ + "patient-outcomes-improvement", + "provider-nps", + "patient-engagement-rate", + "hipaa-compliance-score", + "gross-margin" + ] + + - skill: "swot-pest-analysis" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "SWOT and PEST for healthtech must account for the + regulatory and clinical forces that dominate the external environment. + Political: FDA policy shifts (AI/ML guidance evolution, digital health + pre-certification program), CMS reimbursement policy changes, state + telehealth parity laws, and congressional healthcare reform legislation. + Economic: health system IT budget cycles, payer reimbursement rate + adjustments, employer health benefit spending trends, and venture capital + appetite for healthtech. Social: patient digital health literacy gaps, + provider technology adoption resistance, health equity disparities in + digital access, and post-COVID telehealth utilization normalization. + Technological: AI/ML model validation standards for clinical use, + interoperability standards (FHIR, USCDI), cloud security evolution, and + genomics/precision medicine technology maturation." + healthtech_anti_patterns: + - "Listing 'HIPAA compliance' as a strength. Every healthtech company must + be HIPAA compliant — it is a legal requirement, not a differentiator. + Strengths must be genuinely distinctive." + - "Ignoring the political dimension of reimbursement. CMS reimbursement + decisions are as much political as clinical — congressional mandates, + budget constraints, and policy priorities shape which digital health + services receive coverage." + - "Conducting SWOT against direct competitors only. The most dangerous + competitor in healthtech is often not another startup but a new clinical + guideline that recommends an alternative approach, a payer coverage + decision that excludes digital interventions, or an EHR vendor building + native functionality." + healthtech_example: "A mental health tech company applies PEST and identifies a + convergence of Political tailwinds (Mental Health Parity Act enforcement + increasing, state telehealth parity laws expanding), Economic support + (employer mental health benefit spending growing 25% annually), and Social + momentum (post-pandemic destigmatization of digital mental health + services). However, Technological analysis reveals that GPT-4 class models + are enabling conversational AI therapy tools that could commoditize the + company's chatbot-based intervention. The SWOT synthesis positions the + company to leverage the political/economic/social tailwinds by pivoting + from chatbot delivery to provider-augmented digital therapy with published + clinical evidence — a moat that general-purpose AI cannot replicate." + benchmark_references: + [ + "payer-reimbursement-rate", + "regulatory-approval-status", + "monthly-active-patients" + ] + + - skill: "scenario-planning" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "Scenario planning in healthtech must address the + high-variance regulatory and reimbursement environment. The three most + critical scenario dimensions are: regulatory pathway outcome + (cleared/approved vs. delayed vs. rejected), reimbursement decision (payer + covers vs. payer declines vs. payer covers with conditions), and clinical + evidence results (positive outcomes vs. null results vs. adverse + findings). Each dimension has downstream effects on revenue, fundraising, + and competitive position that cascade through the business model. + Healthtech scenario planning must also include a clinical safety scenario + — what happens if the product causes patient harm, and what contingencies + are in place." + healthtech_anti_patterns: + - "Building all scenarios on the assumption that regulatory clearance is + obtained. A scenario plan that does not include a 'clearance delayed 12 + months' or 'clearance denied' scenario is not a scenario plan — it is a + single plan with different revenue assumptions." + - "Ignoring the reimbursement scenario. A product with FDA clearance but + no payer coverage has limited commercial viability. The reimbursement + dimension is as important as the regulatory dimension." + - "Excluding the adverse clinical event scenario. Products that interact + with patient care carry a non-zero probability of causing harm. A + scenario plan must include this possibility and the company's clinical, + legal, and communication response." + healthtech_example: "A clinical AI company builds four scenarios for the next 24 + months: (1) Base: FDA clearance in 12 months, Medicare coverage decision + in 18 months, positive RCT results. (2) Upside: Breakthrough Device + designation accelerates clearance to 6 months, commercial payers follow + Medicare coverage. (3) Regulatory Delay: FDA requests additional data, + clearance delayed 12 months, requiring runway extension through cost + reduction. (4) Adverse Event: Post-market surveillance reveals a safety + signal requiring product modification and supplemental submission. Each + scenario has pre-committed strategic responses: runway management, + communication plans, regulatory response protocols, and clinical advisory + board engagement." + benchmark_references: + [ + "time-to-regulatory-clearance", + "regulatory-pathway-cost", + "payer-reimbursement-rate" + ] + + - category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Pricing in healthtech is fundamentally + reimbursement-constrained. Unlike SaaS where pricing is a free strategic + variable, healthtech pricing must align with the CPT, HCPCS, or DRG codes + through which the product generates revenue. The pricing diagnosis must + evaluate: reimbursement pathway (which codes apply, what rates they pay, + which payers cover them), pricing model (per-patient-per-month, + per-encounter, site license, hybrid), the gap between product cost and + reimbursement rate (margin analysis), and whether the product generates + new reimbursable events or substitutes for existing ones. The diagnosis + must also address the three-payer problem: Medicare sets a national rate, + commercial payers negotiate independently, and Medicaid varies by state — + creating three distinct pricing realities." + healthtech_anti_patterns: + - "Setting price based on value-based pricing methodology without + verifying that a reimbursement pathway exists at that price. A product + worth $500/patient/month to the health system is worthless commercially + if the applicable CPT code reimburses at $50." + - "Ignoring the distinction between facility and professional + reimbursement. Some CPT codes have different rates depending on whether + the service is provided in a hospital or a physician office — this + affects the product's economic attractiveness in each setting." + - "Treating price increases as a growth lever. Healthtech price increases + are constrained by reimbursement rates, health system budget cycles, and + contractual terms that often include rate locks. The expansion lever in + healthtech is more patients or more services per patient, not higher + prices." + healthtech_example: "A remote patient monitoring company conducts a pricing + diagnosis and discovers that its $150/patient/month price exceeds the + combined reimbursement from RPM CPT codes (99453 + 99454 + 99457 + 99458 = + approximately $120/patient/month at Medicare rates). Health system + customers are absorbing a $30/patient/month loss on every enrolled + patient. The pricing diagnosis triggers a restructuring: base platform fee + aligned to reimbursement rates, with premium analytics and population + health features sold as a separate SaaS license that is not + reimbursement-dependent. This separates the reimbursement-constrained + clinical product from the market-priced analytics product." + benchmark_references: + [ + "payer-reimbursement-rate", + "revenue-per-patient-per-month", + "gross-margin" + ] + kind: diagnostic + ref: pricing-diagnosis + + - skill: "trust-equation" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Trust in healthtech operates at a higher standard than in + any other technology sector because the stakes are human health and life. + The trust equation (Credibility + Reliability + Intimacy / + Self-Orientation) must be interpreted through a clinical lens. Credibility + in healthtech requires published clinical evidence, not marketing claims — + providers evaluate trust through peer-reviewed publications, clinical + conference presentations, and key opinion leader endorsement. Reliability + means clinical uptime and consistent performance on clinical metrics, not + merely system availability — a clinical decision support tool that + provides inconsistent recommendations destroys trust faster than system + downtime. Intimacy means respecting the clinician-patient relationship and + the provider's clinical judgment — products that override or undermine + provider autonomy are rejected. Self-Orientation in healthtech is measured + by whether the company prioritizes patient outcomes over revenue growth — + clinical audiences have finely tuned sensors for commercial motives + disguised as clinical concern." + healthtech_anti_patterns: + - "Building trust through marketing testimonials rather than clinical + evidence. Providers trust peer-reviewed studies, not patient + testimonials. A single well-designed RCT builds more trust than a + thousand marketing case studies." + - "Treating HIPAA compliance as a trust-building credential. HIPAA + compliance is the minimum legal requirement, not a trust differentiator. + Trust is built through evidence, clinical expertise, and demonstrated + commitment to patient outcomes." + - "Moving fast at the expense of clinical reliability. In SaaS, a bug + costs customer satisfaction. In healthtech, a clinical recommendation + error can cost a patient's life. The trust equation's Reliability + numerator must be weighted for clinical consequence." + healthtech_example: "A clinical AI startup struggles to gain traction despite + superior diagnostic accuracy. Applying the trust equation reveals the + problem: Credibility is low because results are published only on arXiv + preprints, not in clinical journals — providers do not trust unreviewed + claims. Reliability is undermined by inconsistent model performance across + patient demographics, which providers have noticed. Intimacy is damaged + because the product presents AI recommendations as directives rather than + decision support, threatening provider autonomy. Self-Orientation is + perceived as high because the company's marketing emphasizes 'replacing + radiologists' rather than 'supporting clinical decisions.' The trust + analysis triggers a strategic reset: publish in JAMA Radiology, conduct + bias audits across demographics, redesign the UX to position AI as + advisory, and reframe messaging around clinical augmentation." + benchmark_references: [ "clinical-evidence-strength", "provider-nps", "provider-adoption-rate" ] + + - skill: "doblin-ten-types" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "The Ten Types of Innovation framework reveals that + healthtech companies over-invest in Product Performance innovation + (clinical accuracy, feature richness) while underinvesting in the + innovation types that drive adoption and sustainability. The most + impactful healthtech innovations often come from Profit Model + (reimbursement-aligned pricing, risk-sharing with payers), Network (EHR + integration ecosystem, clinical data partnerships), Process (clinical + workflow optimization, regulatory pathway efficiency), Channel (EHR + marketplace distribution, clinical society endorsement), Customer + Engagement (patient engagement design, provider champion programs), and + Service (implementation support, clinical training programs). Channel and + Service innovations are particularly underinvested in healthtech — + companies build clinically excellent products and then struggle with + distribution because they ignore the innovation types that connect the + product to its clinical audience." + healthtech_anti_patterns: + - "Treating clinical accuracy as the only innovation vector. A diagnostic + AI with 99% accuracy that cannot be integrated into clinical workflow is + less innovative than one with 95% accuracy that operates natively within + the EHR." + - "Ignoring Service innovation. Health system customers evaluate the total + experience — implementation support, clinical training, ongoing support, + and QBR reporting — not just the product. Service innovation is the most + underrated competitive lever in healthtech." + - "Skipping Profit Model innovation. The shift from fee-for-service to + value-based care creates opportunities for healthtech companies to + innovate on pricing — risk-sharing arrangements, outcome-based pricing, + and shared savings models that align company revenue with patient + outcomes." + healthtech_example: "A population health analytics company maps its innovation + portfolio across the ten types and discovers that 85% of R&D investment is + in Product Performance (better algorithms, more data sources, faster + processing). Channel innovation (how health systems discover and adopt the + product), Service innovation (implementation and training), and Customer + Engagement innovation (provider champion development, clinical community + building) receive less than 5% combined. Rebalancing investment toward + Channel (Epic App Orchard listing, HIMSS presence), Service (standardized + implementation playbook, provider certification program), and Engagement + (clinical advisory board expansion, outcomes publication program) + accelerates adoption more than the next algorithmic improvement would." + benchmark_references: + [ + "provider-adoption-rate", + "clinical-workflow-integration-score", + "time-to-value-implementation" + ] + + - skill: "eisenhower-matrix" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "Healthtech founders face an additional prioritization + dimension that the Eisenhower Matrix must accommodate: clinical urgency. A + patient safety concern is always Urgent and Important — it cannot be + delegated or scheduled for later. A regulatory submission deadline is + Urgent and Important. A clinical study protocol revision may be Not Urgent + but is Important for long-term reimbursement viability. Health system + sales cycles create artificial urgency ('we need this feature by go-live + next month') that often falls in Urgent/Not Important. The key healthtech + adaptation is to separate clinical urgency (patient safety, regulatory + compliance) from commercial urgency (customer requests, sales pressure) — + clinical urgency always takes precedence." + healthtech_anti_patterns: + - "Treating health system feature requests with the same urgency as + patient safety concerns. A health system asking for a report format + change is commercially urgent but not clinically important. A clinical + alert system failure is both." + - "Delegating regulatory affairs tasks to the Not Urgent/Important + quadrant. Regulatory deadlines are unforgiving — a missed submission + window can delay clearance by 6-12 months." + - "Spending all capacity on Urgent/Important clinical and regulatory + tasks, leaving no capacity for the Not Urgent/Important work (clinical + evidence strategy, payer relationship development, product vision) that + determines long-term success." + healthtech_example: "A healthtech CEO uses the Eisenhower Matrix to regain + strategic capacity. Urgent/Important: a clinical safety alert that + requires immediate investigation and response protocol activation. + Urgent/Not Important: a health system customer requesting a custom EHR + integration variant — delegated to the implementation team with standard + integration templates. Not Urgent/Important: designing the clinical study + that will generate the evidence needed for Medicare coverage in 18 months + — the CEO allocates weekly protected time for this strategic work. Not + Urgent/Not Important: attending a general tech conference with no + healthtech-specific content — declined." + benchmark_references: [] + + - skill: "kotter-change-model" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "Kotter's change model is essential for healthtech because + every product deployment at a health system is a change management + project. Providers resist new technology not because they are technophobic + but because clinical workflow changes carry patient safety risk and add to + already-excessive workloads. Step 1 (Create Urgency) must be grounded in + clinical evidence — 'your readmission rate is 22% when the national + benchmark is 15%' is more compelling than 'our product improves + efficiency.' Step 3 (Form a Coalition) requires a clinical champion + (respected physician who endorses the product), an IT sponsor (who + approves integration), and an administrative sponsor (who approves the + budget). Step 5 (Remove Obstacles) means addressing EHR integration + barriers, training gaps, and clinical workflow disruptions. Step 6 (Quick + Wins) must be clinical — a measurable improvement in a clinical metric + within the first 30 days of deployment." + healthtech_anti_patterns: + - "Attempting change without a clinical champion. Technology-led change + initiatives that lack a respected physician advocate are rejected by + clinical staff. The champion must be a peer, not an administrator." + - "Equating training with change management. Training teaches how to use + the product. Change management addresses why the product matters, how it + fits into clinical workflow, and what will change in daily practice. + Training alone is insufficient." + - "Measuring change success by adoption metrics (logins, usage) rather + than clinical outcome metrics (patient outcomes, workflow efficiency). + Providers respect evidence of impact, not evidence of activity." + healthtech_example: "A clinical decision support company deploys at a 500-bed + hospital using Kotter's model. Step 1: Present data showing that the + hospital's sepsis mortality rate exceeds the CMS benchmark, creating + clinical urgency. Step 3: Recruit the Chief Medical Officer as executive + sponsor, a hospitalist physician champion, and the CMIO as IT sponsor. + Step 5: Integrate the sepsis alert directly into the Epic workflow so it + requires zero additional clicks. Step 6: After 30 days, publish internal + data showing a 15% improvement in time-to-antibiotic for sepsis patients — + a quick win that converts skeptical clinicians into advocates." + benchmark_references: + [ + "provider-adoption-rate", + "time-to-value-implementation", + "patient-outcomes-improvement" + ] + + - skill: "systems-thinking" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Healthcare is the most complex adaptive system that any + entrepreneur will encounter. Systems thinking is not optional in + healthtech — it is a survival skill. The healthcare system comprises + interconnected subsystems (clinical delivery, payment, regulation, public + health, research) where interventions in one area produce unpredictable + effects in others. A digital health product that improves patient outcomes + may increase health system costs (more survivors requiring continued + care), reduce provider revenue (fewer procedures), or trigger regulatory + scrutiny (new safety monitoring requirements). Healthtech entrepreneurs + must map the causal loops, feedback mechanisms, and unintended + consequences of their products within the healthcare system — and design + for the systemic effects, not just the primary clinical effect." + healthtech_anti_patterns: + - "Optimizing for a single metric without understanding system-level + effects. Reducing hospital readmissions (a common healthtech value + proposition) may reduce hospital revenue under fee-for-service payment — + creating perverse incentives that block adoption." + - "Assuming that better clinical outcomes automatically lead to business + success. The healthcare system's misaligned incentives mean that + products improving patient outcomes may not generate revenue, while + products that generate revenue may not improve outcomes." + - "Ignoring the provider workforce system. Products that increase clinical + workload — even marginally — in an already-burned-out healthcare + workforce face adoption resistance regardless of their clinical merit." + healthtech_example: "A hospital-at-home technology company applies systems + thinking and maps the full causal loop of their intervention: Product + reduces hospital stays (primary effect) → Reduces hospital bed utilization + (secondary effect) → Reduces hospital revenue under fee-for-service + (negative business effect for the customer) → BUT reduces 30-day + readmissions (positive quality effect) → Improves CMS quality scores → + Increases hospital reimbursement through value-based incentive programs + (positive business effect). The systems map reveals that the product's + value proposition depends entirely on the hospital's payment model mix. + Hospitals with >30% value-based contracts benefit financially; hospitals + with <10% value-based contracts lose revenue. This insight transforms the + sales strategy: target hospitals with high value-based contract exposure." + benchmark_references: + [ + "patient-outcomes-improvement", + "payer-reimbursement-rate", + "provider-adoption-rate" + ] + + - skill: "smart-goals" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "SMART goals in healthtech must be clinically specific, not + just commercially specific. A goal like 'increase revenue 30%' is + incomplete — it must be decomposed into clinical components: 'enroll 500 + new patients in RPM program (clinical), achieve >60% 90-day engagement + rate (clinical), secure billing code coverage from 3 additional commercial + payers (reimbursement), reduce 30-day readmission rate by 15% in enrolled + population (outcomes).' Every commercial goal should be traceable to a + clinical goal, because in healthtech, clinical outcomes drive commercial + outcomes, not the reverse." + healthtech_anti_patterns: + - "Setting commercial goals without clinical outcome targets. Revenue + targets that lack corresponding patient outcome targets signal a + business-first culture that undermines clinical credibility." + - "Setting clinical goals without reimbursement pathway analysis. A goal + to 'demonstrate 20% outcome improvement' is incomplete if the + improvement does not align with a reimbursable service or measurable + quality metric." + healthtech_example: "A digital therapeutics company sets SMART goals that + integrate clinical and commercial dimensions: Specific — Achieve FDA + clearance for insomnia DTx and secure coverage from 3 of the top 10 + commercial payers. Measurable — Published RCT demonstrating >40% + improvement in ISI (Insomnia Severity Index), coverage covering >30M + insured lives. Achievable — RCT enrollment complete, regulatory + pre-submission meeting positive. Relevant — Insomnia affects 30% of + adults, represents $100B+ in economic impact, and has inadequate + pharmacological treatment. Time-bound — Clearance within 8 months, payer + coverage within 14 months." + benchmark_references: + [ + "regulatory-approval-status", + "payer-reimbursement-rate", + "patient-outcomes-improvement" + ] + + # ───────────────────────────────────────────── + # GAME THEORY (4 skills) + # ───────────────────────────────────────────── + + - skill: "game-theory-fundamentals" + category: "game-theory" + healthtech_relevance: "high" + healthtech_context: "Game theory in healthtech must account for multi-player + games with asymmetric information and non-financial payoffs. The key + players are the healthtech company, health systems, payers, regulators, + providers, patients, and competing healthtech companies. Unlike most + industries, the 'game' is not purely competitive — healthcare norms + emphasize cooperation and patient welfare, creating mixed-motive games + where pure self-interest strategies backfire. The regulator (FDA) is a + player whose moves are partially predictable through public guidance and + pre-submission feedback. Payers play a sequential game — Medicare moves + first, and commercial payers follow with a lag. Health systems play a + signaling game — early adopters send signals to later adopters through + conference presentations and publications." + healthtech_anti_patterns: + - "Applying zero-sum competitive logic. Healthcare is fundamentally + cooperative — providers, payers, and healthtech companies share a common + interest in patient outcomes. Pure competitive strategies that harm + other players damage the company's reputation in a trust-dependent + ecosystem." + - "Ignoring the regulator as a player. FDA is not a passive rule-setter + but an active participant whose guidance documents, enforcement actions, + and pre-submission feedback shape the competitive landscape." + healthtech_example: "A clinical AI company analyzes the competitive game among + three AI diagnostic startups competing for FDA clearance in the same + indication. Game theory reveals that the first company to publish a + peer-reviewed clinical study sets the evidence benchmark — subsequent + entrants must meet or exceed it. This first-mover advantage in evidence + generation is more valuable than first-mover advantage in product + features. The company accelerates its clinical study timeline, accepting a + slightly smaller sample size (adequate for 510(k) but not for the + comprehensive study it originally planned) to establish the evidence + benchmark before competitors." + benchmark_references: [ "clinical-validation-stage", "regulatory-approval-status" ] + + - skill: "first-mover-strategy" + category: "game-theory" + healthtech_relevance: "high" + healthtech_context: "First-mover advantage in healthtech manifests differently + than in consumer technology. Being first to market with a product is less + valuable than being first to publish clinical evidence, first to obtain + regulatory clearance, or first to secure payer reimbursement. These + 'regulatory firsts' create durable advantages because: (1) the first + cleared product establishes the predicate device that subsequent entrants + must reference, (2) the first published RCT sets the evidence standard, + (3) the first company to negotiate payer coverage establishes the + reimbursement code and rate that defines the market. The risk of being + first is also higher in healthtech — first movers bear the full cost of + clinical validation and may discover that the market is not + reimbursement-ready." + healthtech_anti_patterns: + - "Prioritizing product launch speed over clinical evidence. In + healthtech, launching first without evidence is worse than launching + second with evidence. The first-mover advantage accrues to the evidence + leader, not the product leader." + - "Assuming first-mover regulatory clearance creates a permanent moat. FDA + clearance for a competitor is typically achievable within 12-24 months + using the first mover's device as a predicate. The durable moat is + clinical evidence and health system relationships, not the clearance + itself." + healthtech_example: "In the continuous glucose monitoring market, Dexcom's + first-mover advantage was built not on product features but on three + regulatory firsts: first to achieve FDA clearance for a non-adjunctive CGM + (patients could dose insulin based on CGM readings alone), first to + publish the evidence that supported this clearance, and first to establish + Medicare coverage. Abbott's FreeStyle Libre followed with a competitive + product — but Dexcom's regulatory and reimbursement head start created a + durable clinical workflow and payer relationship advantage that took + Abbott years to close." + benchmark_references: + [ + "regulatory-approval-status", + "time-to-regulatory-clearance", + "payer-reimbursement-rate" + ] + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + healthtech_relevance: "high" + healthtech_context: "The prisoner's dilemma appears repeatedly in healthtech: + between healthtech companies and health systems (share clinical data vs. + hoard it), between competing healthtech companies (collaborate on + standards vs. pursue proprietary lock-in), and between healthtech and + payers (invest in long-term outcomes vs. optimize short-term costs). The + cooperative equilibrium is both more ethical and more profitable in + healthtech because the ecosystem is small, reputation-dependent, and + long-memory. Defecting (e.g., over-claiming clinical results, locking in + health systems with proprietary data formats) yields short-term advantage + but destroys the trust that health system and payer relationships + require." + healthtech_anti_patterns: + - "Defecting on data interoperability. Building proprietary data formats + to lock in health system customers creates short-term switching costs + but generates long-term resentment and regulatory risk (FHIR + interoperability mandates)." + - "Defecting on clinical evidence integrity. Overstating clinical results + to win a deal may succeed once, but the health system will discover the + discrepancy — and will communicate the betrayal to every other system in + its network." + healthtech_example: "Two competing remote patient monitoring companies face a + prisoner's dilemma on industry data standards. Company A adopts open + FHIR-based data standards, making it easy for health systems to switch + providers. Company B builds proprietary data formats. In the short run, + Company B retains customers through lock-in. In the long run, health + system CIOs refuse to adopt Company B's closed system, and CMS + interoperability mandates force Company B to adopt open standards anyway — + having spent resources on a proprietary system that must be rebuilt. + Company A's cooperative strategy wins because the regulatory environment + and buyer preferences penalize defection." + benchmark_references: [ "clinical-workflow-integration-score", "churn-rate-provider" ] + + - skill: "information-asymmetry" + category: "game-theory" + healthtech_relevance: "high" + healthtech_context: "Information asymmetry in healthtech takes a unique form: + the healthtech company knows its product's clinical data intimately, while + health system buyers, payers, and patients must rely on the company's + disclosures. This creates a moral hazard — the company is incentivized to + emphasize positive results and downplay limitations. Healthcare's response + to this asymmetry is institutional: clinical peer review, IRB oversight, + FDA review, and clinical advisory board scrutiny all serve as information + asymmetry reduction mechanisms. Healthtech companies that proactively + reduce information asymmetry (by publishing all clinical data, including + unfavorable results) build trust faster than those that manage information + strategically." + healthtech_anti_patterns: + - "Selectively disclosing clinical data. Publishing favorable results + while suppressing unfavorable ones is a form of information manipulation + that, when discovered, destroys clinical credibility permanently." + - "Exploiting patient information asymmetry. Patients cannot evaluate + clinical claims with the same rigor as providers. Products that make + unsupported claims to patients are ethically problematic and legally + vulnerable." + healthtech_example: "A clinical AI company voluntarily publishes its model's + performance across demographic subgroups, revealing that accuracy is lower + for certain populations. This transparency initially concerns potential + health system customers. However, the disclosure — and the company's plan + to address the disparity — builds trust with clinical advisory boards and + positions the company as an ethical leader. A competitor that conceals + similar disparities faces a devastating public disclosure when an academic + researcher identifies the bias, destroying that company's clinical + credibility." + benchmark_references: [ "clinical-evidence-strength", "provider-nps" ] + + # ───────────────────────────────────────────── + # NEGOTIATION (3 skills) + # ───────────────────────────────────────────── + + - skill: "cooperative-negotiation" + category: "negotiation" + healthtech_relevance: "critical" + healthtech_context: "Health system and payer negotiations in healthtech are + inherently cooperative because the relationship extends over years and the + shared interest is patient outcomes. Adversarial negotiation tactics + destroy the trust required for clinical partnerships. Cooperative + negotiation in healthtech means: structuring pilot agreements as mutual + learning exercises (not win/lose evaluations), designing contracts with + shared outcome metrics (not just SaaS seat licenses), and treating the + health system's clinical champion as a co-developer (not a customer). The + negotiation framework must also address the multi-stakeholder nature of + health system deals: the clinical champion, the CIO/CMIO, procurement, + legal, and the clinical review committee each have different interests + that must be satisfied cooperatively." + healthtech_anti_patterns: + - "Negotiating against the clinical champion. The clinical champion is the + company's strongest advocate inside the health system. An adversarial + negotiation stance with this person damages the most valuable + relationship in the deal." + - "Using artificial urgency or competitive pressure tactics. Health system + procurement moves at its own pace — creating false urgency undermines + trust and signals commercial desperation." + healthtech_example: "A healthtech company negotiating a $500K enterprise + deployment at a major health system structures the deal cooperatively: a + 90-day pilot with jointly defined clinical outcome metrics, pricing that + starts at cost during the pilot and escalates to full rate upon outcome + achievement, shared publication rights for clinical results, and a + dedicated implementation liaison who reports to both the company and the + health system CMIO. This structure converts a vendor-buyer negotiation + into a clinical partnership — and the health system becomes a + referenceable advocate." + benchmark_references: + [ + "contract-value-health-system", + "sales-cycle-length", + "time-to-value-implementation" + ] + + - skill: "competitive-negotiation" + category: "negotiation" + healthtech_relevance: "moderate" + healthtech_context: "Competitive negotiation in healthtech applies primarily in + three contexts: payer rate negotiations (where the healthtech company + negotiates reimbursement rates with commercial payers), exclusive + distribution agreements (where health systems demand exclusive territory + rights), and M&A discussions. In payer negotiations, the company's + clinical evidence is its primary leverage — published outcomes data that + demonstrates cost avoidance is the strongest argument for higher + reimbursement rates. In exclusive territory negotiations, the company must + balance the value of exclusivity (guaranteed volume) against the cost + (limited market access)." + healthtech_anti_patterns: + - "Using competitive negotiation tactics in health system relationships. + Health systems are long-term clinical partners, not adversarial + counterparties. Competitive tactics that win a deal but damage the + relationship cost more in the long run." + - "Negotiating payer rates without published health economic data. Payers + evaluate reimbursement based on cost-effectiveness evidence. Without it, + the negotiation lacks a credible anchor." + healthtech_example: "A digital therapeutics company negotiates with a large + commercial payer for formulary inclusion. The company's competitive + advantage is a published RCT showing 35% improvement in outcomes and a + health economic analysis demonstrating $4,200 in avoided medical costs per + patient per year. The negotiation anchors on value: the company requests a + reimbursement rate of $200/patient/month ($2,400/year) — significantly + less than the $4,200 in demonstrated savings. The payer accepts because + the cost-savings ratio is compelling, and the clinical evidence provides + the internal justification for the coverage decision." + benchmark_references: + [ + "payer-reimbursement-rate", + "patient-outcomes-improvement", + "clinical-evidence-strength" + ] + + - skill: "negotiation-game-theory" + category: "game-theory" + healthtech_relevance: "high" + healthtech_context: "Negotiation game theory in healthtech must account for the + sequential nature of health system and payer negotiations. Health systems + negotiate with full awareness that Medicare rates set a reference price, + that competing health systems have likely received similar proposals, and + that the healthtech company's clinical evidence is either strong or weak + (not something that can be bluffed). The repeated-game nature of + healthcare negotiations (annual renewals, multi-year contracts, expanding + relationships) means that cooperative strategies dominate competitive + ones. Healthtech negotiations are also information-rich: both parties can + observe clinical outcomes, usage data, and patient engagement metrics in + real time." + healthtech_anti_patterns: + - "Bluffing about clinical evidence or product capabilities. Healthcare + negotiations are conducted by clinically sophisticated buyers who verify + claims independently. Being caught in a bluff destroys not just the deal + but the company's reputation across the health system network." + - "Treating each negotiation as independent. Health system purchasing + networks share information. A concession made to one system becomes the + expected baseline for the next." + healthtech_example: "A healthtech company analyzes the negotiation game across + its health system pipeline and recognizes that its first major health + system deal will set the reference price for all subsequent negotiations. + Game theory analysis suggests a strategy of accepting slightly lower + pricing on the first deal in exchange for contractual permission to + publish clinical outcomes data — the published results from a prestigious + health system become leverage for higher pricing in subsequent + negotiations." + benchmark_references: [ "contract-value-health-system", "sales-cycle-length" ] + + # ───────────────────────────────────────────── + # LEADERSHIP & PEOPLE (5 skills) + # ───────────────────────────────────────────── + + - skill: "decision-making-under-pressure" + category: "leadership" + healthtech_relevance: "critical" + healthtech_context: "Decision-making under pressure in healthtech carries a + dimension absent from other technology sectors: clinical consequence. A + decision to ship a product update may affect patient care. A decision to + delay a feature may leave patients without a beneficial intervention. A + decision to cut costs may reduce clinical support staffing below safe + levels. Healthtech leaders must develop a decision framework that + explicitly weighs patient safety alongside commercial considerations — and + when the two conflict, patient safety must prevail without exception. This + is not merely an ethical stance but a practical one: a single patient + safety incident can destroy the company through regulatory action, + litigation, and reputational damage." + healthtech_anti_patterns: + - "Applying the 'bias toward action' startup philosophy to clinical + decisions. Speed is valuable for commercial decisions but dangerous for + clinical ones. Clinical decisions require deliberation proportional to + the potential for patient harm." + - "Delegating clinical safety decisions to non-clinical team members. + Patient safety decisions must involve clinical expertise — a product + manager or engineer without clinical background should not make + decisions that affect patient care pathways." + healthtech_example: "A healthtech CEO faces a pressure decision: a health system + customer demands a product feature change that would bypass a clinical + safety alert to reduce provider alert fatigue. The commercial pressure is + significant — the customer threatens contract non-renewal. The CEO + consults the clinical advisory board, which determines that the safety + alert prevents a rare but potentially fatal drug interaction. The + decision: the alert remains mandatory, but the product team redesigns the + alert UX to reduce fatigue without compromising safety. The customer + renews after seeing the redesigned experience." + benchmark_references: [ "data-security-incident-rate", "provider-nps" ] + + - skill: "leading-through-change" + category: "leadership" + healthtech_relevance: "high" + healthtech_context: "Leading through change in healthtech requires understanding + that the healthcare workforce is simultaneously the most change-resistant + and the most overburdened workforce in the economy. Physicians have + trained for 10-15 years in specific clinical practices. Nurses manage care + under extreme time pressure. Asking these professionals to adopt new + technology is asking them to change deeply embedded clinical behaviors + while maintaining patient safety standards. Change leadership in + healthtech must respect this reality — change must be clinically justified + (not just commercially motivated), incrementally introduced (not big-bang + deployed), and champion-led (not mandated from above)." + healthtech_anti_patterns: + - "Mandating technology adoption without clinical justification. Providers + comply with mandates but do not engage. Mandated adoption without + clinical buy-in leads to workarounds that undermine the product's + clinical effectiveness." + - "Deploying to all providers simultaneously. Phased rollout with clinical + champions who train and support their peers produces better adoption + than enterprise-wide simultaneous deployment." + healthtech_example: "A health system deploys a clinical AI tool for early sepsis + detection using a change leadership approach. Phase 1: Three physician + champions use the tool for 30 days and present their experience (including + saved lives) at a medical staff meeting. Phase 2: Their departments adopt, + with champions available for peer support. Phase 3: Hospital-wide rollout + with the original champions serving as clinical super-users. This + champion-cascade model achieves 75% adoption in 90 days — compared to a + failed previous deployment of a different tool that mandated simultaneous + adoption and achieved 25%." + benchmark_references: [ "provider-adoption-rate", "time-to-value-implementation" ] + + - skill: "emotional-intelligence" + category: "frameworks" + healthtech_relevance: "high" + healthtech_context: "Emotional intelligence in healthtech extends beyond + interpersonal dynamics to include clinical empathy — the ability to + understand the emotional experience of patients navigating illness and the + emotional burden of providers managing life-and-death decisions daily. + Healthtech founders who lack clinical empathy build products that treat + healthcare as a workflow optimization problem rather than a human + experience. The most successful healthtech companies are led by founders + who understand that a patient using their product may be frightened, a + provider may be exhausted, and a health system administrator may be + overwhelmed — and who design products that respect these emotional + realities." + healthtech_anti_patterns: + - "Treating provider resistance as irrational. Provider skepticism toward + new technology is often rational — they have seen countless + 'revolutionary' health IT products fail, disrupt workflow, and waste + their time. Emotional intelligence means respecting this learned + skepticism." + - "Designing patient-facing products without understanding the emotional + state of the patient population. A patient recently diagnosed with + cancer has different emotional needs from a patient managing stable + diabetes. One-size-fits-all engagement design ignores these + differences." + healthtech_example: "A mental health tech company redesigns its patient + onboarding after emotional intelligence analysis reveals that patients + referred to the platform are often in crisis — they are not calmly + evaluating software features. The redesigned onboarding eliminates all + setup friction, immediately provides a therapeutic exercise (not an + account creation form), and offers a human crisis line as the first + contact option. Completion rates increase from 30% to 65%, and patient NPS + for the onboarding experience rises from 40 to 78." + benchmark_references: [ "patient-satisfaction-score", "patient-engagement-rate" ] + + - skill: "psychological-safety" + category: "frameworks" + healthtech_relevance: "critical" + healthtech_context: "Psychological safety in healthtech carries clinical safety + implications. A team that lacks psychological safety will not report + product defects that could affect patient care, will not raise concerns + about clinical evidence quality, and will not challenge decisions that + prioritize commercial objectives over patient outcomes. In healthcare, the + concept of a 'just culture' — where reporting errors and near-misses is + encouraged and non-punitive — has been shown to reduce patient harm. + Healthtech companies must extend this just culture to their product + development process: engineers must feel safe reporting bugs that could + affect clinical decisions, clinical team members must feel safe + challenging product decisions that could compromise patient safety, and + quality assurance must have the authority to halt releases that fail + safety criteria." + healthtech_anti_patterns: + - "Treating product defect reports as negative events rather than safety + contributions. In healthtech, an engineer who identifies a clinical + decision support error before deployment has potentially saved lives. + The reporting behavior must be celebrated, not punished." + - "Allowing commercial pressure to silence clinical safety concerns. If a + product manager overrides a clinical team member's safety concern to + meet a release deadline, the company has failed at psychological safety + — and has potentially endangered patients." + healthtech_example: "A clinical AI company establishes a 'clinical safety stop' + protocol: any team member, regardless of seniority, can halt a product + release by raising a clinical safety concern. The concern is evaluated by + the Chief Medical Officer within 24 hours. In the first year, the stop + protocol is invoked seven times — four concerns are substantiated and + trigger product modifications before release, three are cleared after + review. The protocol prevents two algorithmic errors that would have + affected clinical recommendations for thousands of patients." + benchmark_references: [ "data-security-incident-rate", "provider-nps" ] + + - skill: "purpose-driven-leadership" + category: "leadership" + healthtech_relevance: "high" + healthtech_context: "Purpose-driven leadership in healthtech is not aspirational + — it is operational. The purpose (improving patient health outcomes) + provides the decision-making framework for every trade-off: when + commercial interests conflict with clinical interests, purpose resolves + the tie. Healthtech companies with genuine purpose-driven leadership + attract clinical talent who want to improve healthcare, build products + that providers trust, and develop the clinical evidence rigor that payers + require. Companies where purpose is performative (marketing language + without operational commitment) are identified quickly by clinical + audiences, who have finely tuned sensors for authenticity." + healthtech_anti_patterns: + - "Using patient outcomes language in marketing without tracking patient + outcomes operationally. If the company's dashboards show revenue and + engagement but not clinical outcome metrics, the purpose is + performative." + - "Making purpose-driven hiring claims while compensating executives + purely on financial metrics. Executive incentive structures that lack + clinical outcome components signal that purpose is subordinate to + profit." + healthtech_example: "A healthtech CEO restructures executive compensation to + include a clinical outcome component: 20% of variable compensation is tied + to patient outcomes improvement metrics. The board initially resists, + arguing that clinical outcomes are influenced by factors outside the + company's control. The CEO counters that revenue is also influenced by + external factors but no one questions revenue-based incentives. The + compensation restructuring sends a powerful signal to the clinical team, + to health system customers, and to investors that patient outcomes are a + first-class business metric." + benchmark_references: [ "patient-outcomes-improvement", "provider-nps" ] + + # ───────────────────────────────────────────── + # AI & DATA (3 skills) + # ───────────────────────────────────────────── + + - skill: "ai-vision-and-strategy" + category: "ai-leadership" + healthtech_relevance: "critical" + healthtech_context: "AI strategy in healthtech must navigate the FDA's evolving + framework for AI/ML-based Software as a Medical Device (SaMD). The FDA's + 2023 AI/ML Action Plan and subsequent guidance documents require that + AI-based clinical tools demonstrate safety and effectiveness, maintain + performance over time (no model drift degradation), and provide + transparency about the AI's role in clinical decision-making. AI strategy + in healthtech must address: regulatory pathway for AI-based products + (predetermined change control plans for iterative model updates), clinical + validation (prospective clinical studies, not just retrospective accuracy + testing), algorithmic fairness (performance across demographic subgroups), + and explainability (clinicians must understand why the AI makes a + recommendation). The AI strategy must also address the unique risk that an + AI-based clinical error could harm patients — making AI safety a patient + safety obligation." + healthtech_anti_patterns: + - "Treating AI accuracy on retrospective datasets as clinical validation. + FDA requires prospective clinical evidence, not just technical + benchmarks. An AI with 99% accuracy on a research dataset may perform + very differently in real clinical practice with messy, incomplete data." + - "Building 'black box' AI clinical tools. The FDA and clinical audiences + require explainability — clinicians will not trust (and should not + trust) recommendations they cannot understand. Explainability is a + regulatory requirement and a clinical adoption requirement." + - "Planning continuous model updates without a predetermined change + control plan. The FDA requires that SaMD companies define in advance + which types of model changes require new regulatory submissions versus + ongoing monitoring." + healthtech_example: "A clinical AI company develops a strategy that addresses + FDA requirements from the architecture level. The AI system is designed + with an explainability layer that provides clinicians with the top three + factors influencing each recommendation. The company files a predetermined + change control plan with FDA that defines the boundaries of autonomous + model updates (performance improvement within the cleared indication) + versus changes requiring new submission (new indications, new data types, + architecture changes). Clinical validation includes a prospective + multi-site study with pre-specified performance thresholds across eight + demographic subgroups." + benchmark_references: + [ + "regulatory-approval-status", + "clinical-evidence-strength", + "clinical-validation-stage" + ] + + - skill: "ai-human-centered-approach" + category: "ai-leadership" + healthtech_relevance: "critical" + healthtech_context: "Human-centered AI in healthtech means provider-centered and + patient-centered simultaneously. For providers, human-centered AI means + decision support (not decision replacement), transparent reasoning, + graceful degradation when uncertain, and respect for clinical judgment + when the provider disagrees with the AI. For patients, it means accessible + explanations, respect for health literacy variation, cultural sensitivity, + and the ability to involve family or caregivers. The 'human in the loop' + is not optional in clinical AI — it is a regulatory and ethical + requirement. FDA guidance emphasizes that AI/ML-based SaMD should augment + clinical decision-making, not replace it." + healthtech_anti_patterns: + - "Designing AI that bypasses the clinician. Autonomous AI clinical + decision-making without clinician oversight is neither regulatorily + permissible (for most clinical applications) nor clinically safe. The + clinician must remain the decision-maker." + - "Treating AI explanations as technical documentation. Explanations for + clinical AI must be written for clinicians, not engineers — using + clinical terminology, citing clinical reasoning, and relating to the + specific patient context." + healthtech_example: "A clinical AI radiology tool is redesigned using + human-centered principles. Instead of presenting a diagnosis, the tool + highlights regions of interest in the image, provides a confidence score + with clinical context ('85% probability of malignancy based on lesion + characteristics consistent with [clinical criteria]'), and offers the + radiologist the option to accept, modify, or reject the assessment. The + tool also presents relevant comparison cases from its training data. This + design respects the radiologist's expertise while providing AI-augmented + decision support that improves diagnostic accuracy by 15% in a prospective + study." + benchmark_references: [ "provider-nps", "provider-adoption-rate", "clinical-evidence-strength" ] + + - skill: "ai-stakeholder-balance" + category: "ai-leadership" + healthtech_relevance: "high" + healthtech_context: "AI stakeholder balance in healthtech requires managing the + competing interests of patients (who want accurate, fair, and private AI), + providers (who want reliable, explainable, and non-disruptive AI), health + systems (who want cost-effective, interoperable AI), payers (who want + evidence-based, cost-reducing AI), regulators (who want safe, transparent, + and well-monitored AI), and the company's investors (who want scalable, + high-margin AI). These interests frequently conflict: investor pressure + for rapid scaling conflicts with the clinical evidence timeline required + by regulators. Provider desire for explainability conflicts with the + complexity of deep learning models. Patient privacy requirements conflict + with the data volume needed for model improvement." + healthtech_anti_patterns: + - "Prioritizing investor scalability demands over regulatory safety + requirements. Scaling an AI clinical tool before adequate safety + monitoring is in place creates patient risk and regulatory risk + simultaneously." + - "Satisfying provider explainability demands by oversimplifying the AI's + reasoning. Explanations must be accurate as well as accessible — a + simplified explanation that misrepresents the AI's actual reasoning + process is misleading." + healthtech_example: "A clinical AI company creates a stakeholder balance map for + its diagnostic AI: Patient interest — equitable accuracy across + demographics (requires bias audits). Provider interest — explainable + recommendations (requires interpretability layer). Health system interest + — EHR integration and workflow compatibility (requires SMART on FHIR + architecture). Payer interest — published cost-effectiveness data + (requires health economic study). Regulator interest — predetermined + change control plan and post-market surveillance (requires regulatory + infrastructure). Investor interest — capital-efficient scaling (requires + automated deployment and monitoring). The map reveals that the regulatory + and clinical evidence requirements must be satisfied first because they + enable all other stakeholder interests." + benchmark_references: + [ + "clinical-evidence-strength", + "regulatory-approval-status", + "provider-adoption-rate" + ] + + # ───────────────────────────────────────────── + # THINKING & DECISIONS (2 skills) + # ───────────────────────────────────────────── + + - skill: "defining-and-exploring-problems" + category: "thinking" + healthtech_relevance: "high" + healthtech_context: "Problem definition in healthtech must begin with the + clinical problem, not the technology solution. The most common healthtech + failure mode is building a technically impressive product that solves a + problem clinicians do not consider important or that creates more burden + than it eliminates. Problem exploration must involve clinicians (who + understand the clinical workflow), patients (who experience the health + condition), and payers (who fund the intervention). The problem definition + must pass the 'triple aim test': does solving this problem improve patient + outcomes, improve patient/provider experience, and reduce cost? Problems + that satisfy only one or two of the triple aim have limited commercial + viability in healthcare." + healthtech_anti_patterns: + - "Starting with the technology and searching for a clinical problem to + solve. Technology-first problem definition leads to products that + demonstrate technical capability without clinical utility." + - "Defining the problem based on clinician interviews alone without + observing actual clinical workflow. What clinicians say they need and + what clinical observation reveals they need are often different." + healthtech_example: "A healthtech startup redefines its problem statement after + clinical workflow observation. The original problem: 'Clinicians need + better diagnostic AI.' After observing 50 clinical encounters, the revised + problem: 'Primary care physicians spend 18 minutes per patient encounter + on documentation, leaving 7 minutes for clinical assessment — the + documentation burden, not diagnostic capability, is the constraint on care + quality.' The product pivots from diagnostic AI to ambient clinical + documentation, which generates significantly more provider enthusiasm and + a clearer reimbursement pathway." + benchmark_references: [ "provider-adoption-rate", "provider-nps" ] + + - skill: "evaluating-and-deciding" + category: "thinking" + healthtech_relevance: "high" + healthtech_context: "Evaluation and decision-making in healthtech must + incorporate clinical risk as a first-class dimension alongside financial + and operational considerations. Every decision framework should include + the question: 'If this decision leads to the worst plausible clinical + outcome, what happens to patients?' This is not paranoia — it is the + clinical version of pre-mortem analysis. Decisions that create even a + small probability of patient harm require more rigorous evaluation than + those with purely financial consequences. The evaluation framework should + also weight irreversibility: clinical product changes that affect patient + care are harder to reverse than pricing or marketing changes." + healthtech_anti_patterns: + - "Applying purely financial decision criteria to decisions with clinical + implications. A cost-benefit analysis that shows a positive ROI for + shipping a product faster should not override clinical safety concerns + about the accelerated timeline." + - "Using consumer technology decision-making speed for clinical product + decisions. The 'ship it and iterate' approach is appropriate for + engagement features but not for clinical decision support algorithms." + healthtech_example: "A healthtech company evaluates whether to expand its + clinical AI into a new therapeutic area. The evaluation framework includes + four dimensions: Clinical (is there sufficient evidence that AI improves + outcomes in this area?), Regulatory (what pathway is required and what is + the timeline?), Reimbursement (do billing codes exist and will payers + cover it?), and Safety (what is the worst plausible clinical outcome if + the AI performs poorly?). The Safety dimension reveals that errors in the + proposed therapeutic area (oncology) carry higher consequence than the + current area (dermatology) — the evaluation triggers a more rigorous + clinical validation plan before market entry." + benchmark_references: [ "clinical-validation-stage", "regulatory-approval-status" ] diff --git a/plugins/foreman/content/industry-packs/healthtech/healthtech-templates.yaml b/plugins/foreman/content/industry-packs/healthtech/healthtech-templates.yaml new file mode 100644 index 0000000..40ab57d --- /dev/null +++ b/plugins/foreman/content/industry-packs/healthtech/healthtech-templates.yaml @@ -0,0 +1,1031 @@ +# Healthtech Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for healthtech companies. The output agent loads these rules +# when generating documents with the healthtech industry pack active. +# +# PATIENT SAFETY PRINCIPLE: All materials — investor, board, team, self, and +# client — must incorporate patient safety as a first-class dimension. Risk +# sections include patient safety risk alongside business risk. Clinical metrics +# appear alongside financial metrics. Regulatory and reimbursement status are +# reported as standard elements, not appendices. +# +# TRIPLE STAKEHOLDER PRINCIPLE: Investor and board materials must address the +# triple-aim value proposition (patient outcomes, provider experience, cost +# reduction) because healthtech viability depends on all three. Unit economics +# include clinical validation cost amortization. Board materials distinguish +# clinical advisory board governance from corporate board governance. +# +# Adaptation types: +# as-is — The template works without modification for healthtech companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for healthtech context. + +pack_metadata: + sector: "healthtech" + display_name: "Healthtech" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech unit economics are per-patient, not per-account, and include clinical validation cost amortization, regulatory pathway investment, and reimbursement-dependent revenue. The snapshot must show investors that the per-patient economics are sustainable after accounting for clinical evidence investment and regulatory costs — expenses unique to healthtech that do not exist in standard SaaS." + field_changes: + - field: "Revenue per unit" + sector_label: "Revenue per Patient per Month (by Source)" + sector_guidance: "Decompose revenue per patient by source: payer reimbursement (specify CPT/HCPCS codes and rates), health system SaaS allocation per patient, employer direct-pay allocation per covered life, and patient self-pay. Report each separately because regulatory exposure, durability, and margin profiles differ." + - field: "Cost per unit" + sector_label: "CAC per Health System + Patient Acquisition Cost" + sector_guidance: "Report two CAC figures: (1) CAC per health system customer (fully loaded including pilot costs, clinical evaluation support, integration implementation, and sales effort). (2) Patient acquisition cost within deployed health systems (enrollment, onboarding, clinician training per patient). In healthtech, the health system is acquired first, then patients within the system are enrolled." + - field: "Margin per unit" + sector_label: "Gross Margin per Patient" + sector_guidance: "Calculate per-patient gross margin including: clinical support staff cost per patient (if applicable), technology cost per patient, and regulatory compliance cost allocation per patient. Distinguish technology-only margin from blended margin including clinical services." + - field: "Lifetime value" + sector_label: "Patient LTV (Clinically Adjusted)" + sector_guidance: "Calculate LTV incorporating: revenue per patient per month, patient retention rate, clinical program duration (some interventions are time-limited), and gross margin. Disclose whether the clinical protocol has a defined endpoint (e.g., 12-week DTx program) or is ongoing (e.g., chronic disease monitoring). Clinical validation cost should be amortized across projected lifetime patient volume." + - field: "Acquisition cost" + sector_label: "CAC Payback Period (Blended)" + sector_guidance: "Report payback in months, calculated on the blended CAC (health system acquisition cost amortized across expected patient volume plus per-patient enrollment cost). Note: healthtech payback periods are typically longer than SaaS because health system sales cycles extend the time to first revenue." + - field: "Unit economics ratio" + sector_label: "Patient LTV:CAC Ratio" + sector_guidance: "Report the blended ratio and compare to the 3x-5x benchmark. Because healthtech CAC includes clinical validation costs (study execution, regulatory pathway), the ratio may appear lower than SaaS — explain this distinction for investors comparing across sectors." + sections_to_add: + - section_name: "Healthtech Metrics Dashboard" + placement: "before:Revenue per Patient per Month (by Source)" + description: "Core healthtech metrics in a format health-focused investors expect." + fields: + - "Monthly Active Patients and growth rate" + - "Revenue per Patient per Month" + - "Payer Reimbursement Rate (%)" + - "Provider Adoption Rate (%)" + - "Patient Engagement Rate (weekly)" + - "Clinical Outcome Improvement (primary endpoint)" + - "Gross Margin (technology-only and blended)" + - "Clinical Evidence Stage" + - "Regulatory Status" + - section_name: "Clinical Validation Cost Amortization" + placement: "after:Patient LTV:CAC Ratio" + description: "Clinical evidence investment and its amortization across the patient base." + fields: + - "Total clinical validation investment to date (studies, regulatory, medical writing)" + - "Projected total clinical validation investment" + - "Clinical validation cost per patient (amortized across projected patient volume)" + - "Regulatory pathway cost incurred and remaining" + - section_name: "Reimbursement Structure" + placement: "after:Clinical Validation Cost Amortization" + description: "How the product generates revenue through the healthcare payment system." + fields: + - "Applicable CPT/HCPCS codes and reimbursement rates" + - "Payer coverage status (Medicare, top 10 commercial payers)" + - "Revenue per patient under full reimbursement vs. current reimbursement" + - "Path to broader payer coverage (timeline and milestones)" + sections_to_remove: [] + benchmark_references: ["revenue-per-patient-per-month", "cac-health-system", "gross-margin", "payer-reimbursement-rate", "clinical-validation-stage", "regulatory-approval-status", "patient-engagement-rate", "monthly-active-patients"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech investor updates must include clinical milestones and regulatory status alongside financial metrics. Health-focused investors expect proactive disclosure of clinical evidence progress, regulatory interactions, and reimbursement developments. Clinical milestones (study enrollment, data analysis, publication, regulatory submission) are as important as commercial milestones." + field_changes: + - field: "Financial highlights" + sector_label: "Healthtech KPIs" + sector_guidance: "Report: Monthly Active Patients, Revenue (total and per-patient), Payer Reimbursement Rate (% of revenue), Provider Adoption Rate, Patient Engagement Rate, and Gross Margin. Present as a small table with current month, prior month, and trend arrow." + - field: "Key metrics" + sector_label: "Clinical & Regulatory Milestones" + sector_guidance: "Report: clinical study enrollment/completion status, regulatory submission status, payer coverage decisions, clinical evidence publications, and adverse event summary (if applicable). These milestones are as consequential as revenue metrics for healthtech investors." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one clinical win: a patient outcome improvement demonstrated, a health system deployment completed, a clinical publication accepted, or a regulatory milestone achieved. Financial wins should be reported alongside clinical wins, not instead of them." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges. In healthtech, challenges often have regulatory or clinical dimensions: regulatory feedback requiring additional data, payer coverage denial, provider adoption below target, or patient engagement declining. Investors respect transparency about clinical challenges." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific. Healthtech-specific asks: introduction to a health system CIO or CMIO for pilot discussion, connection to a payer medical director for coverage discussion, introduction to clinical key opinion leaders for advisory engagement." + sections_to_add: + - section_name: "Regulatory & Clinical Status" + placement: "after:Healthtech KPIs" + description: "Standing regulatory and clinical evidence status that investors can track month-over-month." + fields: + - "FDA regulatory status (current stage and next milestone)" + - "Clinical study status (enrollment, data collection, analysis, publication)" + - "Payer coverage status (applications pending, decisions received)" + - "Patient safety summary (adverse events, if any)" + - section_name: "Cash Position" + placement: "after:Regulatory & Clinical Status" + description: "Cash and runway with regulatory milestone overlay." + fields: + - "Cash balance (end of month)" + - "Monthly burn rate (trailing 3-month average)" + - "Months of runway" + - "Runway relative to next regulatory milestone" + sections_to_remove: [] + benchmark_references: ["monthly-active-patients", "revenue-per-patient-per-month", "payer-reimbursement-rate", "regulatory-approval-status", "clinical-validation-stage"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech competitive analysis must include clinical evidence comparison, regulatory status comparison, and reimbursement status — dimensions that do not exist in standard competitive briefs. The most important competitive axis in healthtech is clinical evidence strength, not product features or pricing." + field_changes: + - field: "Competitor overview" + sector_label: "Clinical Competitive Map" + sector_guidance: "Map competitors on a 2x2 matrix: X-axis = clinical evidence strength (pilot data to published RCTs), Y-axis = regulatory/reimbursement status (pre-clearance to broadly reimbursed). Position your product and each competitor. Include EHR vendor native capabilities as competitors." + - field: "Competitive advantages" + sector_label: "Clinical Defensibility Analysis" + sector_guidance: "Assess defensibility along healthtech-specific dimensions: clinical evidence moat (published outcomes superior to competitors), regulatory moat (clearance timeline advantage), reimbursement moat (payer coverage secured before competitors), workflow integration moat (deep EHR integration), and clinical relationship moat (health system champions and advisory board)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize threats: (1) Peer healthtech — same clinical area, similar product. (2) EHR vendor — native functionality replacing standalone product. (3) Pharmaceutical company — pharma-funded digital companion with massive clinical trial budget. (4) Academic medical center — research institution commercializing internally developed tool. (5) Big tech — Google, Amazon, Apple entering the clinical space." + sections_to_add: + - section_name: "Clinical Evidence Comparison" + placement: "after:Clinical Competitive Map" + description: "Head-to-head clinical evidence comparison with competitors." + fields: + - "Evidence level comparison by competitor (Oxford CEBM level)" + - "Published outcomes data by competitor" + - "Regulatory status by competitor" + - "Payer coverage status by competitor" + - section_name: "EHR Platform Threat Assessment" + placement: "after:Threat Vectors" + description: "Assessment of EHR vendor native functionality as competitive threat." + fields: + - "Epic native capabilities that overlap with the product" + - "Oracle Health (Cerner) native capabilities that overlap" + - "EHR vendor roadmap announcements relevant to the product" + - "Defensibility against EHR vendor encroachment" + sections_to_remove: [] + benchmark_references: ["clinical-evidence-strength", "regulatory-approval-status", "payer-reimbursement-rate", "clinical-workflow-integration-score"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech pitch decks require clinical evidence, regulatory pathway, and reimbursement strategy slides that do not exist in standard pitch templates. Health-focused investors evaluate these dimensions with the same rigor as financial metrics. The deck must demonstrate clinical credibility alongside commercial viability." + field_changes: + - field: "Market opportunity" + sector_label: "Clinical Market Opportunity" + sector_guidance: "Present the clinical problem first: prevalence, burden of disease, cost to the healthcare system, and inadequacy of current solutions. Then size the market bottom-up: (patient population) x (reimbursement rate per patient) = addressable market. Include the payer perspective: what are payers currently spending on this condition, and how does the product reduce that spend?" + - field: "Business model" + sector_label: "Healthtech Business Model" + sector_guidance: "Cover: revenue model (reimbursement-based, SaaS, hybrid), triple-stakeholder value proposition (patient outcomes, provider experience, cost reduction), reimbursement pathway (CPT codes, payer engagement), and the clinical evidence that supports each value claim." + - field: "Traction" + sector_label: "Clinical & Commercial Traction" + sector_guidance: "Dual-axis traction slide: commercial metrics (Monthly Active Patients, revenue, health system customers) alongside clinical metrics (clinical evidence stage, patient outcomes improvement, regulatory milestones). Both dimensions must show progress." + sections_to_add: + - section_name: "Clinical Evidence Slide" + placement: "after:Clinical & Commercial Traction" + description: "Dedicated slide summarizing the clinical evidence base — the most scrutinized slide in a healthtech pitch." + fields: + - "Clinical study design, patient population, and primary endpoint" + - "Key outcome results with statistical significance" + - "Publication status (journal, conference presentations)" + - "Ongoing and planned studies" + - section_name: "Regulatory Pathway Slide" + placement: "after:Clinical Evidence Slide" + description: "Regulatory strategy and timeline — a gating factor for healthtech investors." + fields: + - "Regulatory classification and pathway (510(k), De Novo, PMA, exempt)" + - "Current regulatory status" + - "Timeline to clearance/approval" + - "Regulatory cost budget and spend to date" + - section_name: "Reimbursement Strategy Slide" + placement: "after:Regulatory Pathway Slide" + description: "How the product generates revenue through the healthcare payment system." + fields: + - "Applicable billing codes (CPT, HCPCS)" + - "Current payer coverage (Medicare, top commercial payers)" + - "Reimbursement rate per patient per month" + - "Path to broader payer coverage" + - section_name: "Per-Patient Unit Economics Slide" + placement: "after:Reimbursement Strategy Slide" + description: "Per-patient economics including clinical validation cost amortization." + fields: + - "Revenue per patient per month (by source)" + - "Cost per patient per month (technology + clinical support)" + - "Patient LTV:CAC ratio" + - "Clinical validation cost amortized per patient" + sections_to_remove: [] + benchmark_references: ["clinical-validation-stage", "regulatory-approval-status", "payer-reimbursement-rate", "revenue-per-patient-per-month", "patient-outcomes-improvement", "monthly-active-patients"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "A healthtech strategic one-pager must anchor analysis in clinical evidence strength, regulatory position, and reimbursement viability alongside standard commercial metrics." + field_changes: + - field: "Strategic position" + sector_label: "Healthtech Strategic Position" + sector_guidance: "Frame position across four dimensions: clinical evidence strength relative to competitors, regulatory status and timeline, reimbursement position and payer coverage, and health system adoption and provider satisfaction." + - field: "Key metrics" + sector_label: "Healthtech Health Metrics" + sector_guidance: "Core 5: Monthly Active Patients + growth rate, Patient Outcomes Improvement, Payer Reimbursement Rate, Provider Adoption Rate, Gross Margin. Compare each to stage-appropriate benchmarks." + sections_to_add: + - section_name: "Triple-Aim Assessment" + placement: "end" + description: "Assessment of the company's position on the healthcare triple aim." + fields: + - "Better outcomes: clinical evidence summary and outcome improvement metrics" + - "Better experience: patient satisfaction and provider NPS" + - "Lower cost: health economic analysis and cost avoidance data" + - "Triple-aim alignment: which dimensions are strong, which need improvement" + sections_to_remove: [] + benchmark_references: ["monthly-active-patients", "patient-outcomes-improvement", "payer-reimbursement-rate", "provider-adoption-rate", "gross-margin"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech market sizing must be grounded in clinical epidemiology and reimbursement economics, not generic TAM calculations." + field_changes: + - field: "Total addressable market" + sector_label: "Clinical TAM / SAM / SOM" + sector_guidance: "Bottom-up sizing using clinical data: (patient prevalence in target population) x (reimbursement rate per patient per year) = SAM. Cross-reference with payer spending data in the therapeutic area. Do not use top-down healthcare market size estimates." + - field: "Market dynamics" + sector_label: "Clinical Market Dynamics" + sector_guidance: "Address: clinical guideline evolution (is the clinical standard of care shifting toward digital interventions?), reimbursement trends (are payers expanding or contracting digital health coverage?), provider adoption trends (are clinicians increasingly willing to prescribe digital interventions?), and regulatory trends (is FDA facilitating or constraining the market?)." + sections_to_add: + - section_name: "Reimbursement Landscape" + placement: "end" + description: "Current and projected reimbursement environment for the clinical area." + fields: + - "Current reimbursement codes applicable to the product" + - "Recent CMS coverage decisions in the therapeutic area" + - "Commercial payer coverage trends" + - "Projected reimbursement expansion timeline" + sections_to_remove: [] + benchmark_references: ["payer-reimbursement-rate", "monthly-active-patients"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech due diligence requires clinical evidence verification, regulatory pathway assessment, HIPAA compliance audit, and reimbursement strategy evaluation — dimensions that do not exist in standard technology due diligence." + field_changes: + - field: "Financial review" + sector_label: "Financial & Revenue Model Verification" + sector_guidance: "Verify: revenue decomposition by source (reimbursement vs. SaaS vs. self-pay), per-patient economics, clinical validation cost accounting, and regulatory cost budget versus actuals. Request access to billing data and payer contracts." + - field: "Operational review" + sector_label: "Clinical Operations & Compliance Review" + sector_guidance: "Review: HIPAA compliance documentation, clinical governance structure, adverse event reporting procedures, clinical study protocols and results, regulatory submission history, and payer coverage decisions." + sections_to_add: + - section_name: "Clinical Evidence Due Diligence" + placement: "after:Financial & Revenue Model Verification" + description: "Clinical evidence verification — the healthtech equivalent of financial audit." + fields: + - "Clinical study protocols, IRB approvals, and results" + - "Statistical analysis plans and primary endpoint definitions" + - "Publication history and journal quality" + - "Clinical advisory board composition and engagement level" + - "Adverse event history and reporting procedures" + - section_name: "Regulatory & Compliance Due Diligence" + placement: "after:Clinical Evidence Due Diligence" + description: "Regulatory pathway and compliance assessment." + fields: + - "FDA regulatory classification and pathway" + - "Regulatory submission history and FDA feedback" + - "HIPAA compliance assessment (HITRUST, SOC 2, or equivalent)" + - "State licensing requirements and compliance" + - "Data security incident history" + - section_name: "Reimbursement Due Diligence" + placement: "after:Regulatory & Compliance Due Diligence" + description: "Reimbursement pathway viability assessment." + fields: + - "Applicable CPT/HCPCS codes and reimbursement rates" + - "Payer coverage status across Medicare and top commercial payers" + - "Health economic analysis (cost-effectiveness data)" + - "Reimbursement risk assessment (pending coverage decisions, code sunset risk)" + sections_to_remove: [] + benchmark_references: ["clinical-validation-stage", "regulatory-approval-status", "hipaa-compliance-score", "payer-reimbursement-rate"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not healthtech-specific. Standard venture capital cap table formats apply regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech decision rationale memos must include clinical impact assessment for decisions that affect patient care, regulatory status, or clinical evidence strategy." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Clinical & Commercial)" + sector_guidance: "For decisions with clinical implications, document the clinical context alongside the commercial context: what patient population is affected, what clinical outcomes could change, and what regulatory or compliance implications exist." + sections_to_add: + - section_name: "Patient Safety Impact Assessment" + placement: "end" + description: "Assessment of the decision's potential impact on patient safety — required for any decision affecting clinical product behavior." + fields: + - "Patient population affected" + - "Potential positive clinical impact" + - "Potential negative clinical impact (worst plausible scenario)" + - "Mitigation measures" + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech exit scenarios are governed by clinical evidence strength, regulatory clearances, and payer coverage — these are the primary value drivers in healthtech M&A. Acquirer categories include health system spin-outs, pharma companies, medtech companies, and health IT platforms." + field_changes: + - field: "Valuation methodology" + sector_label: "Healthtech Valuation Drivers" + sector_guidance: "Healthtech valuation is driven by: clinical evidence strength (published outcomes data), regulatory status (clearances held), reimbursement position (payer coverage secured), and commercial traction (revenue, patients, health systems). Revenue multiples for healthtech vary by sub-sector: pure software (8-15x ARR), clinical services-included (3-8x ARR), pre-revenue with clearance (milestone-based)." + - field: "Potential acquirers" + sector_label: "Healthtech Acquirer Landscape" + sector_guidance: "Categorize: (1) Health IT platforms — EHR vendors, population health companies (acquire for product expansion). (2) Pharma/biotech — therapeutic companies (acquire for digital companion or real-world evidence). (3) Medtech — device companies (acquire for digital extension of physical devices). (4) Health systems — integrated delivery networks (acquire for internal capability). (5) Private equity — health services PE firms (acquire for portfolio company integration)." + sections_to_add: + - section_name: "Clinical Asset Valuation" + placement: "after:Healthtech Valuation Drivers" + description: "Valuation of clinical assets that are unique to healthtech M&A." + fields: + - "Clinical evidence portfolio value (cost to replicate)" + - "Regulatory clearance value (time and cost for acquirer to obtain independently)" + - "Payer coverage value (contracts and covered lives)" + - "Clinical relationship value (health system customers, KOL network, advisory board)" + sections_to_remove: [] + benchmark_references: ["clinical-validation-stage", "regulatory-approval-status", "payer-reimbursement-rate", "monthly-active-patients"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech board reviews must integrate clinical metrics alongside commercial metrics, report regulatory milestone progress, and distinguish clinical advisory board governance from corporate board governance. Board members must see clinical outcomes data alongside financial data — in healthtech, clinical performance leads financial performance." + field_changes: + - field: "Financial summary" + sector_label: "Clinical & Financial Dashboard" + sector_guidance: "Present dual dashboards: Clinical (patient outcomes improvement, patient engagement rate, provider adoption rate, clinical evidence milestones, adverse event summary) and Financial (revenue, per-patient economics, gross margin, burn rate, runway). Clinical metrics appear first because they are leading indicators of financial performance." + - field: "Strategic priorities" + sector_label: "Clinical & Commercial Priorities" + sector_guidance: "Report against quarterly priorities across both clinical (study milestones, regulatory milestones, reimbursement milestones) and commercial (health system deals, revenue targets, operational metrics) dimensions. Flag any clinical milestone that is off-track with root cause and corrective action." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: (1) Patient safety risk — adverse events, product reliability, clinical protocol deviations. (2) Regulatory risk — clearance timeline, FDA feedback, compliance gaps. (3) Reimbursement risk — payer coverage decisions, code changes, rate adjustments. (4) Commercial risk — pipeline, churn, competitive threats. (5) Operational risk — security, uptime, HIPAA compliance. Patient safety risk appears first." + sections_to_add: + - section_name: "Regulatory & Evidence Milestone Tracker" + placement: "before:Clinical & Financial Dashboard" + description: "Quarter-by-quarter tracking of regulatory and clinical evidence milestones." + fields: + - "FDA regulatory milestones (status and next step)" + - "Clinical study milestones (enrollment, data collection, analysis, publication)" + - "Payer coverage milestones (applications, decisions)" + - "Milestone timeline vs. plan (ahead/on-track/behind)" + - section_name: "Clinical Advisory Board Report" + placement: "after:Risk Dashboard" + description: "Summary of clinical advisory board activity and recommendations — distinct from corporate board governance." + fields: + - "Clinical advisory board meeting summary (recommendations, concerns raised)" + - "Advisory board composition and any changes" + - "Clinical governance decisions made and rationale" + - "Patient safety review summary" + sections_to_remove: [] + benchmark_references: ["patient-outcomes-improvement", "provider-adoption-rate", "patient-engagement-rate", "regulatory-approval-status", "payer-reimbursement-rate", "gross-margin"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech board meeting agendas must allocate time for clinical governance, regulatory updates, and patient safety review alongside standard business topics." + field_changes: + - field: "Agenda items" + sector_label: "Healthtech Board Agenda" + sector_guidance: "Standard healthtech board agenda: (1) Patient safety and clinical governance report — 10 min (any adverse events, clinical protocol changes, advisory board recommendations). (2) Regulatory and clinical evidence update — 10 min (milestone progress, FDA interactions, publication pipeline). (3) Financial and commercial metrics review — 15 min (pre-read, discussion only). (4) Strategic topic deep-dive — 30 min (one topic: clinical evidence strategy, reimbursement pathway, health system expansion, competitive response). (5) CEO asks — 10 min. (6) Executive session — 15 min. Total: 90 minutes. Patient safety review is first, non-negotiable." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech risk assessment must place patient safety risk as the first category, above commercial and operational risk. Regulatory risk, reimbursement risk, and clinical evidence risk are sector-specific categories that do not exist in standard risk frameworks." + field_changes: + - field: "Risk categories" + sector_label: "Healthtech Risk Categories" + sector_guidance: "Include in this order: (1) Patient safety risk — adverse events, product errors, clinical protocol deviations, the risk that the product causes harm. (2) Regulatory risk — clearance delays, FDA warning letters, compliance gaps, post-market surveillance findings. (3) Reimbursement risk — payer coverage denials, code changes, rate reductions. (4) Clinical evidence risk — study failures, null results, competitor evidence leapfrog. (5) Commercial risk — pipeline, churn, competitive threats, health system concentration. (6) Operational risk — security, HIPAA compliance, system reliability. Patient safety risk is first because it is the most consequential and the most irreversible." + sections_to_add: + - section_name: "Patient Safety Incident Log" + placement: "before:Healthtech Risk Categories" + description: "Summary of any patient safety-related events since the last board meeting." + fields: + - "Adverse events reported (count, severity, resolution status)" + - "Product reliability incidents affecting clinical operations" + - "Clinical protocol deviations identified" + - "Corrective actions taken and their effectiveness" + - section_name: "Regulatory Risk Heat Map" + placement: "after:Healthtech Risk Categories" + description: "Visual assessment of regulatory risks across dimensions." + fields: + - "FDA regulatory status and risk level (green/yellow/red)" + - "HIPAA compliance posture and risk level" + - "State licensing and compliance risk" + - "Upcoming regulatory changes that could affect the business" + sections_to_remove: [] + benchmark_references: ["data-security-incident-rate", "hipaa-compliance-score", "regulatory-approval-status"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Change initiatives in healthtech must include clinical impact assessment — any organizational or product change may affect patient care delivery." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected Clinical & Commercial Outcomes" + sector_guidance: "Quantify both clinical impact (patient outcomes, provider experience, safety) and commercial impact (revenue, margin, growth). Initiatives with negative clinical impact should not be approved regardless of commercial benefit." + sections_to_add: + - section_name: "Patient Safety Impact Assessment" + placement: "end" + description: "Assessment of how the proposed change could affect patient safety." + fields: + - "Patient populations affected by the change" + - "Potential positive patient impact" + - "Potential negative patient impact and mitigation" + - "Clinical governance review status" + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech compensation must address the clinical-commercial talent spectrum and include clinical outcome-linked incentives for leadership." + field_changes: + - field: "Compensation benchmarks" + sector_label: "Healthtech Compensation Benchmarks" + sector_guidance: "Use healthtech-specific comp data from Rock Health compensation surveys and Carta health sector data. Include: CMO compensation (cash + equity), clinical operations compensation, regulatory affairs compensation, and standard technical and commercial roles. Clinical leadership compensation is typically higher than comparable SaaS roles due to the specialized skill set." + sections_to_add: + - section_name: "Clinical Outcome-Linked Compensation" + placement: "end" + description: "Assessment of whether leadership incentives include clinical outcome components." + fields: + - "Percentage of leadership variable comp tied to clinical outcomes" + - "Clinical outcome metrics used in compensation calculations" + - "Clinical advisory board compensation structure" + sections_to_remove: [] + benchmark_references: [] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "This template is the most critical board template for healthtech companies. It must cover FDA regulatory status, HIPAA compliance, state licensing, and clinical governance in depth." + field_changes: + - field: "Regulatory landscape" + sector_label: "Healthtech Regulatory Landscape" + sector_guidance: "Cover: FDA regulatory status (current submissions, pending clearances, post-market requirements), HIPAA compliance posture (assessment results, remediation items, breach history), state licensing (telehealth, clinical services), AI/ML regulatory developments (FDA AI/ML Action Plan updates), and international regulatory status (CE marking, MDR compliance) if applicable." + sections_to_add: + - section_name: "FDA Regulatory Status" + placement: "before:Healthtech Regulatory Landscape" + description: "Detailed FDA regulatory status and milestone tracking." + fields: + - "Current regulatory classification and pathway" + - "Submission status and timeline" + - "FDA interactions since last board meeting" + - "Post-market surveillance findings (if applicable)" + - "Predetermined change control plan status (for AI/ML products)" + - section_name: "HIPAA & Data Security" + placement: "after:Healthtech Regulatory Landscape" + description: "HIPAA compliance and data security status." + fields: + - "HIPAA risk assessment status (last completed, findings)" + - "HITRUST CSF or SOC 2 certification status" + - "Penetration testing results (last completed, findings)" + - "Security incident log (since last board meeting)" + - "Business associate agreement coverage (%)" + - section_name: "Clinical Governance" + placement: "after:HIPAA & Data Security" + description: "Clinical governance structure and activity." + fields: + - "Clinical advisory board meeting summary" + - "Clinical protocol changes and rationale" + - "Adverse event reporting summary" + - "Clinical quality metrics" + sections_to_remove: [] + benchmark_references: ["hipaa-compliance-score", "data-security-incident-rate", "regulatory-approval-status"] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "CEO succession in healthtech must consider whether the successor has clinical credibility and regulatory literacy alongside standard leadership capabilities." + field_changes: + - field: "Succession criteria" + sector_label: "Healthtech CEO Succession Criteria" + sector_guidance: "Include healthtech-specific criteria: (1) Clinical credibility — can the successor engage credibly with clinical advisory boards, health system CMOs, and the CMO/clinical team? (2) Regulatory literacy — does the successor understand the FDA pathway and HIPAA obligations? (3) Payer relationship capability — can the successor negotiate with payer organizations? (4) Health system relationship management — can the successor maintain and expand health system customer relationships?" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech action plans must distinguish between clinical actions (which may affect patient safety) and commercial/operational actions. Clinical actions require clinical review before execution." + field_changes: + - field: "Success metrics" + sector_label: "Clinical & Commercial KPI Targets" + sector_guidance: "Define success using both clinical and commercial metrics: patient outcome improvement target, provider adoption rate target, patient engagement rate improvement, alongside revenue or growth targets. Every commercial action item should be traceable to a clinical impact." + sections_to_add: + - section_name: "Clinical Impact Assessment" + placement: "end" + description: "Assessment of whether any action items could affect patient care." + fields: + - "Action items requiring clinical review before execution" + - "Patient populations potentially affected" + - "Clinical governance approval status" + sections_to_remove: [] + benchmark_references: [] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech initiative briefs must include clinical impact assessment and regulatory impact assessment alongside standard project metrics." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected Clinical & Commercial Impact" + sector_guidance: "Quantify impact on both clinical metrics (patient outcomes, provider adoption, patient engagement) and commercial metrics (revenue, margin, growth). Include the time to measurable clinical impact." + - field: "Resource requirements" + sector_label: "Resource Requirements (Clinical & Technical)" + sector_guidance: "Specify both technical resources (engineering weeks) and clinical resources (clinical study support, regulatory review, medical writing). Healthtech initiatives often require clinical resources that are scarcer and more expensive than engineering resources." + sections_to_add: + - section_name: "Regulatory Impact Assessment" + placement: "after:Expected Clinical & Commercial Impact" + description: "Assessment of whether the initiative triggers regulatory requirements." + fields: + - "Does this initiative modify a cleared/approved product?" + - "Regulatory classification impact (if any)" + - "Clinical validation requirements" + - "HIPAA compliance implications" + sections_to_remove: [] + benchmark_references: ["patient-outcomes-improvement", "provider-adoption-rate"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech project kickoffs must define clinical success criteria and identify any patient safety implications of the project." + field_changes: + - field: "Success criteria" + sector_label: "Clinical & Commercial Success Criteria" + sector_guidance: "Define 2-3 clinical metrics and 2-3 commercial metrics. Clinical: patient outcome improvement target, provider adoption change, patient engagement change. Commercial: revenue impact, deployment count, contract value. Include a patient safety criterion: 'zero adverse events attributable to this project.'" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["patient-outcomes-improvement", "provider-adoption-rate"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech hiring scorecards must include clinical domain assessment for roles that interact with clinical content, health system customers, or regulatory processes." + field_changes: + - field: "Required competencies" + sector_label: "Healthtech-Specific Competencies" + sector_guidance: "For clinical roles (CMO, clinical operations, medical affairs): clinical credibility, health system experience, regulatory affairs knowledge, clinical study design capability. For commercial roles: health system enterprise sales experience, understanding of reimbursement, familiarity with clinical evaluation processes. For technical roles: HIPAA compliance awareness, healthcare data standards (HL7, FHIR), clinical data handling experience." + sections_to_add: + - section_name: "Clinical Domain Assessment" + placement: "end" + description: "Assessment of the candidate's healthcare domain expertise." + fields: + - "Clinical or healthcare domain experience (years, context)" + - "Understanding of healthcare regulatory environment" + - "Experience with health system customers or clinical workflows" + - "HIPAA compliance awareness assessment" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech incident postmortems must include patient safety impact assessment, HIPAA breach assessment, and clinical operations impact — dimensions that carry legal and regulatory consequences beyond standard SaaS incidents." + field_changes: + - field: "Impact assessment" + sector_label: "Clinical, Patient Safety & Business Impact" + sector_guidance: "Assess three impact dimensions: (1) Patient safety — were any patients affected? Were clinical workflows disrupted? Were clinical decisions made without the product's support during the incident? (2) HIPAA/regulatory — was PHI exposed or compromised? Is HHS/OCR notification required? (3) Business — revenue at risk, customer relationship impact, SLA breach." + sections_to_add: + - section_name: "HIPAA Breach Assessment" + placement: "after:Clinical, Patient Safety & Business Impact" + description: "Formal assessment of whether the incident constitutes a HIPAA breach." + fields: + - "Was PHI accessed, disclosed, or compromised?" + - "Breach risk assessment (per HIPAA Breach Notification Rule)" + - "Notification requirements (individuals, HHS, media if >500 affected)" + - "Notification timeline and completion status" + - section_name: "Clinical Impact Review" + placement: "after:HIPAA Breach Assessment" + description: "Assessment of the incident's impact on patient care." + fields: + - "Clinical operations disrupted (duration and scope)" + - "Patients potentially affected (count and impact severity)" + - "Provider communication log (when clinical staff were notified)" + - "Patient safety incident report filed (if applicable)" + sections_to_remove: [] + benchmark_references: ["data-security-incident-rate", "hipaa-compliance-score"] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech retrospectives must include a clinical quality dimension alongside standard agile retrospective categories." + field_changes: + - field: "What went well" + sector_label: "What Went Well (Clinical & Technical)" + sector_guidance: "Include clinical quality achievements alongside technical and process achievements: clinical protocol adherence, patient safety maintained, regulatory milestone achieved, clinical evidence generated." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific. The content naturally adapts to healthtech context." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech team health must include clinical-commercial alignment assessment and patient safety culture health alongside standard team metrics." + field_changes: + - field: "Health indicators" + sector_label: "Healthtech Team Health Indicators" + sector_guidance: "Include healthtech-specific indicators: clinical-commercial alignment (do clinical and commercial teams agree on priorities?), patient safety culture (do team members feel empowered to raise safety concerns?), regulatory literacy (does the team understand the regulatory constraints?), and clinical workflow empathy (does the technical team understand provider needs?)." + sections_to_add: + - section_name: "Clinical-Commercial Alignment Score" + placement: "end" + description: "Assessment of alignment between clinical and commercial functions." + fields: + - "Clinical-commercial priority alignment (shared understanding of what comes next)" + - "Evidence-commercial alignment (clinical evidence strategy supports commercial needs)" + - "Patient safety culture score (team members feel empowered to raise safety concerns)" + - "Cross-functional clinical literacy (technical team understands clinical context)" + sections_to_remove: [] + benchmark_references: [] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech culture and values documents must include patient safety as a core value — not a compliance requirement but a foundational commitment." + field_changes: + - field: "Core values" + sector_label: "Core Values (Clinical & Organizational)" + sector_guidance: "Include patient safety and clinical integrity as explicit core values. These should not be aspirational statements but operational commitments with specific behavioral expectations — for example, 'Any team member can halt a product release for a patient safety concern' or 'Clinical evidence informs all product decisions.'" + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning is not sector-specific, though the content discussed at offsites will naturally address healthtech topics." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech role descriptions must reference clinical domain requirements and regulatory literacy expectations." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Clinical Impact" + sector_guidance: "For each responsibility, specify the clinical and/or commercial metric the role owner is accountable for. Examples: CMO owns clinical evidence strategy and patient safety governance; VP Clinical Operations owns provider adoption rate and patient engagement; VP Regulatory owns FDA pathway timeline and compliance posture." + - field: "Required experience" + sector_label: "Healthtech Experience Requirements" + sector_guidance: "Specify: healthcare domain experience, HIPAA compliance familiarity, experience with health system customers, regulatory environment understanding, and for clinical roles — clinical credentials and licensure." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A healthtech CEO's weekly review must include clinical metrics and patient safety status alongside commercial metrics." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly Healthtech Dashboard" + sector_guidance: "Review weekly: patient enrollment and engagement trends, provider adoption at deployed sites, any adverse events or patient safety concerns, pipeline status and upcoming health system evaluations, cash balance. Monthly metrics (clinical outcomes, regulatory milestones, payer decisions) should be reviewed monthly, not weekly." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Identify the single most important clinical and the single most important commercial priority. In healthtech, these may conflict — the CEO must resolve the tension explicitly, not avoid it." + sections_to_add: + - section_name: "Patient Safety Check" + placement: "before:Weekly Healthtech Dashboard" + description: "Weekly patient safety status — the first thing the CEO reviews." + fields: + - "Any adverse events or patient safety concerns this week" + - "Clinical governance issues requiring CEO attention" + - "Product reliability status (any clinical system issues)" + sections_to_remove: [] + benchmark_references: ["patient-engagement-rate", "provider-adoption-rate"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech decision journals must capture the clinical dimensions of decisions, including patient safety considerations and regulatory implications." + field_changes: + - field: "Decision context" + sector_label: "Decision Context (Clinical & Commercial)" + sector_guidance: "Record: the clinical and commercial metrics that informed this decision, whether patient safety was a consideration, whether the decision has regulatory implications, and the clinical advisory board's input (if applicable). For decisions with clinical impact, note the 'patient safety criterion' — what outcome would indicate the decision harmed patients." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech annual reviews must assess clinical milestones alongside commercial milestones." + field_changes: + - field: "Year in review" + sector_label: "Healthtech Year in Review" + sector_guidance: "Assess: clinical evidence progress (studies completed, publications, regulatory milestones), patient outcomes metrics (improvement trend), health system customer growth, payer coverage expansion, financial performance (revenue, margin, burn), and team development (clinical and technical hires)." + - field: "Next year goals" + sector_label: "Next Year Clinical & Commercial Targets" + sector_guidance: "Set targets across all healthtech dimensions: clinical evidence targets (studies to complete, publications), regulatory targets (submissions, clearances), reimbursement targets (payer coverage, covered lives), commercial targets (revenue, patients, health systems), and operational targets (HIPAA compliance, security posture)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["clinical-validation-stage", "regulatory-approval-status", "payer-reimbursement-rate", "monthly-active-patients"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech stakeholder maps must include healthcare-ecosystem-specific stakeholder categories: clinical advisory board, health system CMOs and CIOs, payer medical directors, FDA contacts, key opinion leaders, and clinical society leadership." + field_changes: + - field: "Stakeholder categories" + sector_label: "Healthtech Stakeholder Ecosystem" + sector_guidance: "Include: Investors (health-focused VCs, strategic investors, angels), Clinical (clinical advisory board, key opinion leaders, clinical society contacts), Health Systems (CMIO/CIO contacts, clinical champions, procurement contacts), Payers (medical director contacts, benefits purchaser contacts), Regulatory (FDA contacts, regulatory consultants), Team (executives, clinical leadership, key ICs), and Partners (EHR vendors, pharma, data partners)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech negotiation prep must address the unique dynamics of health system, payer, and regulatory negotiations." + field_changes: + - field: "Negotiation type" + sector_label: "Healthtech Negotiation Context" + sector_guidance: "Classify: health system enterprise deal (contract terms, pilot structure, implementation scope), payer contract (coverage decision, reimbursement rate, evidence requirements), regulatory engagement (pre-submission meeting, clearance response), partnership (EHR integration terms, pharma collaboration), or fundraising (term sheet). Each type has distinct healthtech-specific dynamics." + - field: "BATNA" + sector_label: "BATNA and Healthtech Leverage" + sector_guidance: "Healthtech-specific leverage: for health system deals — clinical evidence superiority, published outcomes, reference customers, EHR integration depth. For payer negotiations — health economic data, cost avoidance evidence, clinical guideline inclusion. For fundraising — multiple term sheets, clinical milestone achievement, regulatory clearance obtained." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["contract-value-health-system", "clinical-evidence-strength"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech founders face a unique stressor: the weight of patient safety responsibility. The knowledge that product decisions can affect patient health creates a burden that is qualitatively different from standard startup stress." + field_changes: + - field: "Stress indicators" + sector_label: "Healthtech-Specific Stress Indicators" + sector_guidance: "Include: patient outcome anxiety (excessive worry about adverse events), clinical perfection paralysis (inability to make decisions due to patient safety fear), regulatory timeline stress (the psychological burden of waiting for FDA decisions that determine the company's fate), moral distress (conflict between clinical ideals and commercial realities), and isolation (feeling that non-healthcare founders cannot understand the unique burden)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific. The reflections naturally address healthtech-specific challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech founders must develop domain-specific knowledge in healthcare regulation, clinical evidence, and reimbursement." + field_changes: + - field: "Learning areas" + sector_label: "Healthtech Learning Priorities" + sector_guidance: "Consider healthtech-specific learning areas: FDA regulatory pathways and digital health guidance, clinical study design and evidence hierarchy, healthcare reimbursement (CPT codes, CMS coverage process), health system procurement and clinical evaluation processes, HIPAA compliance and healthcare data security, clinical AI regulation (FDA AI/ML guidance), and healthcare economics and value-based care models." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A healthtech founder's personal advisory network must include clinical and regulatory expertise alongside standard business expertise." + field_changes: + - field: "Advisor categories" + sector_label: "Healthtech Advisory Needs" + sector_guidance: "Map advisors to healthtech-specific needs: Clinical (physician in the target therapeutic area, preferably a KOL), Regulatory (former FDA reviewer or regulatory affairs executive), Reimbursement (payer medical director or health economics expert), Health System Sales (someone who has sold enterprise health IT to health systems), Health-Focused Investing (partner at a health-focused VC), and Clinical AI (if applicable — expert in clinical AI validation and FDA AI/ML guidance)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech QBRs with health system customers must present clinical outcomes data, provider adoption metrics, and patient engagement alongside standard account health metrics. The QBR is the primary vehicle for demonstrating clinical value — which drives renewal." + field_changes: + - field: "Performance summary" + sector_label: "Clinical Value Delivered" + sector_guidance: "Lead with clinical outcomes: patient health improvements attributable to the product, comparison to pre-deployment baseline, and comparison to published benchmarks. Quantify using the customer's own quality metrics (CMS quality measures, internal KPIs). Revenue impact comes second — clinical value justifies the financial investment." + - field: "Account status" + sector_label: "Adoption & Engagement Metrics" + sector_guidance: "Present: provider adoption rate (active providers / licensed providers), patient enrollment and engagement, clinical workflow integration status, and usage trends. Segment by department or clinical unit within the health system." + - field: "Next steps" + sector_label: "Clinical Expansion Opportunities" + sector_guidance: "Identify expansion opportunities: additional clinical departments, additional patient populations, additional clinical use cases (if evidence-supported), and deeper EHR integration. Frame as clinical value expansion, not commercial upsell." + sections_to_add: + - section_name: "Clinical Outcomes Summary" + placement: "before:Clinical Value Delivered" + description: "Clinical outcomes data for the health system customer — the most important section of the QBR." + fields: + - "Primary clinical outcome metric (pre-deployment vs. current)" + - "Secondary outcomes and quality metrics" + - "Patient safety summary (adverse events, if any)" + - "Comparison to published clinical benchmarks" + - section_name: "Provider Feedback Summary" + placement: "after:Adoption & Engagement Metrics" + description: "Provider satisfaction and workflow feedback." + fields: + - "Provider NPS (current and trend)" + - "Top provider feedback themes (positive and constructive)" + - "Workflow integration improvements since last QBR" + sections_to_remove: [] + benchmark_references: ["provider-adoption-rate", "patient-engagement-rate", "patient-outcomes-improvement", "provider-nps"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech onboarding at health systems determines provider adoption and clinical workflow integration — the most critical success factors for retention. The welcome packet must address both technical implementation and clinical change management." + field_changes: + - field: "Getting started steps" + sector_label: "Clinical Implementation Path" + sector_guidance: "Define the implementation path across both technical and clinical tracks: (1) Technical: EHR integration, data validation, security review (week 1-2). (2) Clinical: provider training, clinical workflow design, clinical champion identification (week 2-4). (3) Pilot: limited deployment with clinical champions, outcome measurement (week 4-8). (4) Expansion: broader deployment with provider peer training (week 8-12). Each step includes estimated time and a 'go/no-go' clinical criterion." + - field: "Resources" + sector_label: "Clinical & Technical Resources" + sector_guidance: "Include: clinical evidence summary (for clinical review committee), EHR integration documentation, provider training materials (accredited CME if available), patient enrollment resources, clinical protocol documentation, and HIPAA BAA template." + sections_to_add: + - section_name: "Clinical Champion Engagement Plan" + placement: "end" + description: "Plan for engaging and supporting clinical champions who drive adoption." + fields: + - "Clinical champion identification criteria" + - "Champion training and support plan" + - "Champion-to-peer training cascade plan" + - "Clinical champion recognition and engagement program" + sections_to_remove: [] + benchmark_references: ["time-to-value-implementation", "provider-adoption-rate"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech proposals to health systems must include clinical evidence, regulatory status, HIPAA compliance documentation, and clinical outcome commitments alongside standard commercial terms." + field_changes: + - field: "Solution overview" + sector_label: "Clinical Solution Overview" + sector_guidance: "Lead with the clinical problem and outcome — not the technology. Structure: clinical problem statement (with data from the health system's own metrics if available), clinical evidence supporting the solution (published studies, outcome data), and how the solution integrates into the health system's clinical workflow." + sections_to_add: + - section_name: "Clinical Evidence Summary" + placement: "after:Clinical Solution Overview" + description: "Summary of clinical evidence supporting the proposed solution." + fields: + - "Published clinical studies (citation, population, primary outcome, result)" + - "Regulatory clearance status" + - "Clinical outcome commitments (what the company will measure and report)" + - section_name: "Compliance & Security" + placement: "end" + description: "HIPAA and security compliance documentation." + fields: + - "HIPAA compliance certifications (HITRUST, SOC 2)" + - "Data security architecture overview" + - "BAA willingness and template" + - "Incident response procedures summary" + sections_to_remove: [] + benchmark_references: ["clinical-evidence-strength", "hipaa-compliance-score", "regulatory-approval-status"] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech case studies must lead with clinical outcomes — the primary decision criterion for health system buyers." + field_changes: + - field: "Results" + sector_label: "Clinical & Operational Results" + sector_guidance: "Present clinical outcomes first: patient health improvement metrics (with statistical significance if available), provider satisfaction metrics, and operational improvements. Commercial results (cost savings, efficiency gains) come second. Include the clinical measurement methodology to build evidence credibility." + sections_to_add: + - section_name: "Clinical Evidence Context" + placement: "before:Clinical & Operational Results" + description: "Clinical context that makes the case study credible to clinical audiences." + fields: + - "Patient population and clinical setting" + - "Comparison methodology (pre-post, concurrent control, or matched cohort)" + - "Primary clinical endpoint and measurement period" + - "Limitations and generalizability notes" + sections_to_remove: [] + benchmark_references: ["patient-outcomes-improvement", "provider-adoption-rate"] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech project status updates for health system customers must include clinical implementation progress alongside technical milestones." + field_changes: + - field: "Status summary" + sector_label: "Clinical & Technical Implementation Status" + sector_guidance: "Report progress on both tracks: Technical (EHR integration, data validation, security configuration) and Clinical (provider training, clinical workflow design, pilot deployment, outcome measurement). Health system stakeholders care more about clinical readiness than technical completion." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["time-to-value-implementation"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech partnership memos must address clinical governance, data sharing (with HIPAA compliance), and clinical independence to maintain credibility." + field_changes: + - field: "Partnership structure" + sector_label: "Clinical Partnership Structure" + sector_guidance: "Define: clinical governance (who has authority over clinical content and recommendations), data sharing (HIPAA-compliant data use agreement terms), publication rights (who can publish clinical results and under what conditions), and clinical independence (how the partnership maintains clinical integrity, especially for pharma partnerships)." + sections_to_add: + - section_name: "Clinical Independence & Governance" + placement: "end" + description: "How clinical independence is maintained within the partnership." + fields: + - "Clinical content governance (who reviews and approves clinical recommendations)" + - "Data use agreement terms (HIPAA compliance)" + - "Publication rights and review process" + - "Conflict of interest management" + sections_to_remove: [] + benchmark_references: [] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech SLAs must address clinical availability requirements, HIPAA compliance commitments, and incident response procedures that exceed standard SaaS SLA terms." + field_changes: + - field: "Service levels" + sector_label: "Clinical Service Level Commitments" + sector_guidance: "Include: system availability (health system customers may require 99.9%+ for clinical-use systems), clinical data accuracy, HIPAA compliance maintenance, incident response time (faster for clinical systems than standard SaaS), and breach notification timeline (per HIPAA requirements). Distinguish between clinical-critical availability (during clinical hours) and non-clinical availability." + sections_to_add: + - section_name: "Clinical Safety Commitments" + placement: "end" + description: "Patient safety commitments embedded in the service agreement." + fields: + - "Adverse event reporting procedures and timelines" + - "Product safety notification process (if safety issue discovered)" + - "Clinical data accuracy standards and monitoring" + - "HIPAA breach notification commitments (per federal and state requirements)" + sections_to_remove: [] + benchmark_references: ["hipaa-compliance-score", "data-security-incident-rate"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "Healthtech analysis reports for health system clients must present clinical evidence alongside operational analysis." + field_changes: + - field: "Findings" + sector_label: "Clinical & Operational Findings" + sector_guidance: "Present clinical findings (patient outcomes, clinical workflow impact, provider satisfaction) alongside operational findings (efficiency, cost, utilization). Clinical findings should follow evidence-based reporting standards: state the methodology, present results with confidence intervals, and note limitations." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["patient-outcomes-improvement", "provider-adoption-rate"] diff --git a/plugins/foreman/content/industry-packs/marketplace/marketplace-benchmarks.yaml b/plugins/foreman/content/industry-packs/marketplace/marketplace-benchmarks.yaml new file mode 100644 index 0000000..320430f --- /dev/null +++ b/plugins/foreman/content/industry-packs/marketplace/marketplace-benchmarks.yaml @@ -0,0 +1,620 @@ +# Marketplace Industry Pack — Benchmarks +# Defines 24 marketplace-specific metrics with formulas, benchmark ranges, +# stage notes, and data sources drawn from a16z Marketplace 100, NFX, +# Lenny Rachitsky's marketplace research, Bill Gurley's writings, +# and Sarah Tavel's hierarchy of marketplaces. +# +# These metrics are purpose-built for two-sided platforms. They do not +# translate from SaaS definitions — they originate in marketplace dynamics: +# liquidity, network effects, take rates, and cross-side dependencies. + +pack: marketplace +author: "Fatih Guner" +type: benchmarks +version: "1.0.0" + +metrics: + + # ────────────────────────────────────────────── + # 1. GMV — Gross Merchandise Volume + # ────────────────────────────────────────────── + - name: gmv + display_name: "Gross Merchandise Volume (GMV)" + definition: > + Total dollar value of transactions processed through the marketplace + in a given period, before the platform takes its cut. GMV is the + top-line measure of marketplace scale — the economic activity the + platform intermediates. Not revenue. Not bookings. The full transaction + value flowing through both sides. + formula: "SUM(transaction_value) over period" + benchmarks: + poor: "GMV growth <20% YoY after reaching $1M annual GMV" + average: "GMV growth 20-50% YoY" + good: "GMV growth 50-100% YoY" + excellent: "GMV growth >100% YoY (a16z Marketplace 100 median at scale: ~80% YoY)" + stage_notes: + idea: "GMV is meaningless — focus on whether transactions happen at all." + validation: "First $10K monthly GMV. Quality matters more than volume." + early_traction: "$50K-$500K monthly GMV. Watch GMV per cohort, not aggregate." + growth: "$500K-$10M monthly GMV. GMV growth rate is the headline metric." + scale: ">$10M monthly GMV. GMV growth decelerates; shift focus to net revenue and take rate." + data_source: "a16z Marketplace 100 (2023-2024); internal transaction ledger" + + # ────────────────────────────────────────────── + # 2. Take Rate + # ────────────────────────────────────────────── + - name: take_rate + display_name: "Take Rate" + definition: > + The percentage of GMV that the marketplace retains as revenue. + This is the platform's price — the tax it levies for matching + supply and demand. Take rate reflects the marketplace's + perceived value-add: managed marketplaces with trust, payments, + insurance, and dispute resolution command higher take rates. + Commodity matching commands less. + formula: "Net Revenue / GMV x 100" + benchmarks: + poor: "<5% (commodity listing, no value-add, vulnerable to disintermediation)" + average: "5-15% (standard for product marketplaces; Etsy ~18%, eBay ~13%)" + good: "15-25% (managed services marketplaces; Airbnb ~14% host + ~14% guest)" + excellent: ">25% (deep value-add, regulated industries; Uber historically ~25-30%)" + stage_notes: + idea: "Target take rate is a hypothesis. Test willingness-to-pay on both sides." + validation: "Start with a take rate the supply side accepts. Do not optimise yet." + early_traction: "Experiment cautiously. Raising take rate 2 points may kill supply growth." + growth: "Introduce tiered take rates — higher for premium services, lower for volume sellers." + scale: "Take rate expansion is the primary margin lever. Every 1pp = material revenue at scale GMV." + data_source: "Bill Gurley 'A Rake Too Far' (2013); a16z marketplace data" + + # ────────────────────────────────────────────── + # 3. Supply-Side CAC + # ────────────────────────────────────────────── + - name: supply_side_cac + display_name: "Supply-Side CAC" + definition: > + Cost to acquire one new active supplier (seller, driver, host, service + provider). Includes all marketing, sales, onboarding, and incentive + costs directed at the supply side. Critical because supply acquisition + is often the harder, more expensive side in early-stage marketplaces. + formula: "Total Supply-Side Acquisition Spend / New Active Suppliers (same period)" + benchmarks: + poor: "Supply CAC > 6 months of supply-side revenue contribution" + average: "Supply CAC = 3-6 months of supply-side revenue contribution" + good: "Supply CAC = 1-3 months of supply-side revenue contribution" + excellent: "Supply CAC < 1 month OR organic supply acquisition >60%" + stage_notes: + idea: "Manual, unscalable supply acquisition is expected. Track cost anyway." + validation: "High CAC acceptable if supply quality is high and retention strong." + early_traction: "Supply CAC must be declining as word-of-mouth and network effects emerge." + growth: "Organic supply should exceed 50%. Paid supply CAC must show clear ROI." + scale: "Supply-side virality should dominate. Paid acquisition reserved for new verticals or geos." + data_source: "NFX marketplace research; Lenny Rachitsky supply-side benchmarks" + + # ────────────────────────────────────────────── + # 4. Demand-Side CAC + # ────────────────────────────────────────────── + - name: demand_side_cac + display_name: "Demand-Side CAC" + definition: > + Cost to acquire one new active buyer (customer, rider, guest, + client). Includes all marketing, promotions, referral credits, + and demand-side incentive costs. In most mature marketplaces, + demand-side CAC is lower than supply-side CAC because demand + follows supply quality. + formula: "Total Demand-Side Acquisition Spend / New Active Buyers (same period)" + benchmarks: + poor: "Demand CAC > first-transaction contribution margin" + average: "Demand CAC = 50-100% of first-transaction contribution margin" + good: "Demand CAC < 50% of first-transaction contribution margin" + excellent: "Demand CAC < 25% of first-transaction contribution margin OR >70% organic demand" + stage_notes: + idea: "Demand CAC is speculative. Estimate from analogous marketplaces." + validation: "High demand CAC is tolerable if repeat rates are strong." + early_traction: "Demand-side virality should be emerging. Track organic share weekly." + growth: "Blended demand CAC must decline QoQ. Watch for channel saturation." + scale: "Brand and network effects should make demand acquisition near-zero marginal cost." + data_source: "a16z Marketplace 100; Lenny Rachitsky demand acquisition data" + + # ────────────────────────────────────────────── + # 5. Blended CAC + # ────────────────────────────────────────────── + - name: blended_cac + display_name: "Blended CAC" + definition: > + Combined cost to bring one incremental matched transaction to + the marketplace, accounting for both supply and demand acquisition. + This is the true cost of creating marketplace liquidity — the cost + of producing a match, not just a user on one side. + formula: "(Total Supply Acquisition Spend + Total Demand Acquisition Spend) / New Matched Transactions" + benchmarks: + poor: "Blended CAC > contribution margin per transaction" + average: "Blended CAC = 50-100% of contribution margin per transaction" + good: "Blended CAC = 20-50% of contribution margin per transaction" + excellent: "Blended CAC < 20% of contribution margin per transaction" + stage_notes: + idea: "Blended CAC is unknowable. Focus on whether matches happen." + validation: "Compute blended CAC even on tiny volumes. The ratio matters, not the absolute number." + early_traction: "Blended CAC payback should approach 1 transaction for low-AOV marketplaces." + growth: "Blended CAC should decline as cross-side network effects compound." + scale: "Blended CAC approaching zero indicates mature network effects." + data_source: "NFX marketplace economics framework" + + # ────────────────────────────────────────────── + # 6. Supply Liquidity + # ────────────────────────────────────────────── + - name: supply_liquidity + display_name: "Supply Liquidity" + definition: > + The percentage of active listings or available supply units that + result in a completed transaction within a defined period. This + is Sarah Tavel's 'Level 1' — the marketplace's ability to deliver + its core promise to the supply side: 'list here and you will sell.' + Low supply liquidity kills marketplaces because disappointed + suppliers leave, triggering a death spiral. + formula: "Transacting Supply Units / Total Active Supply Units x 100" + benchmarks: + poor: "<20% (most supply idle; marketplace is a graveyard of unsold listings)" + average: "20-40% (functional but supply-side value prop is weak)" + good: "40-60% (healthy; supply sees marketplace as a reliable channel)" + excellent: ">60% (strong demand pull; supply retention driven by consistent income)" + stage_notes: + idea: "Constrain supply deliberately. A marketplace with 1,000 listings and 10 buyers is dead." + validation: "Supply liquidity is the single most important early metric. Optimise ruthlessly." + early_traction: "Maintain liquidity as you grow supply. Adding supply without proportional demand destroys this metric." + growth: "Segment liquidity by category, geography, and price tier. Aggregates hide rot." + scale: "Liquidity should be >50% in every active segment. Expand only into segments where demand exists." + data_source: "Sarah Tavel 'Hierarchy of Marketplaces' (2016); Greylock marketplace research" + + # ────────────────────────────────────────────── + # 7. Demand Fill Rate + # ────────────────────────────────────────────── + - name: demand_fill_rate + display_name: "Demand Fill Rate" + definition: > + The percentage of demand-side searches, requests, or purchase + intents that result in a completed transaction. The demand-side + counterpart to supply liquidity. If a buyer searches and finds + nothing suitable, the marketplace failed. High fill rate = the + marketplace reliably delivers what demand wants. + formula: "Completed Transactions / Demand-Side Search or Request Sessions x 100" + benchmarks: + poor: "<30% (buyers leave empty-handed; marketplace lacks relevant supply)" + average: "30-50% (adequate for considered purchases; poor for commodities)" + good: "50-70% (strong match quality; buyers trust the marketplace)" + excellent: ">70% (exceptional; near-certain fulfillment — Uber-like on-demand reliability)" + stage_notes: + idea: "Curate initial supply to maximise fill rate for the narrow use case you launch with." + validation: "Demand fill rate above 50% suggests viable supply-demand match quality." + early_traction: "Track fill rate by demand segment. Some segments may be oversupplied, others starved." + growth: "Fill rate compression during rapid scaling signals supply quality degradation." + scale: "Fill rate should be stable or improving. Declining fill rate at scale is a trust problem." + data_source: "a16z marketplace operational metrics; Uber/Lyft S-1 disclosures" + + # ────────────────────────────────────────────── + # 8. Supply Repeat Rate + # ────────────────────────────────────────────── + - name: supply_repeat_rate + display_name: "Supply Repeat Rate" + definition: > + Percentage of suppliers who transact again within a defined period + after their first transaction. Measures whether the marketplace + delivers enough value for supply to stay engaged. Sarah Tavel's + 'Level 2' — building supply-side habit. + formula: "Suppliers With 2+ Transactions in Period / Suppliers With 1+ Transactions in Period x 100" + benchmarks: + poor: "<30% (supply treats marketplace as one-time experiment)" + average: "30-50% (functional retention but supply has alternatives)" + good: "50-70% (marketplace is an important revenue channel for supply)" + excellent: ">70% (marketplace is the primary income source for supply)" + stage_notes: + idea: "Repeat rate is unmeasurable. Focus on whether first transactions satisfy supply." + validation: "Track 30-day and 90-day repeat rate from first transaction." + early_traction: ">40% 90-day repeat rate indicates product-market fit on the supply side." + growth: "Supply repeat rate should improve as marketplace adds value-added services." + scale: "Declining repeat rate at scale signals disintermediation or competitor poaching." + data_source: "Sarah Tavel 'Hierarchy of Marketplaces'; Lenny Rachitsky retention benchmarks" + + # ────────────────────────────────────────────── + # 9. Demand Repeat Rate + # ────────────────────────────────────────────── + - name: demand_repeat_rate + display_name: "Demand Repeat Rate" + definition: > + Percentage of buyers who make a repeat purchase within a defined + period. The demand-side counterpart to supply repeat rate. High + demand repeat rate is the strongest signal of marketplace + product-market fit — buyers got what they wanted and came back. + formula: "Buyers With 2+ Transactions in Period / Buyers With 1+ Transactions in Period x 100" + benchmarks: + poor: "<20% (marketplace failed to deliver a compelling first experience)" + average: "20-40% (adequate for high-AOV, infrequent-purchase categories)" + good: "40-60% (strong for most marketplace categories)" + excellent: ">60% (exceptional; buyers prefer marketplace over alternatives)" + stage_notes: + idea: "N/A — no repeat data exists." + validation: "Any repeat purchase in the first 90 days is a strong signal." + early_traction: "Cohort-based repeat rate is more important than aggregate. Track monthly cohorts." + growth: "Demand repeat rate should be stable or improving as supply quality and selection grow." + scale: "Declining repeat rate at scale is a red flag — supply quality or trust may be degrading." + data_source: "a16z Marketplace 100; Lenny Rachitsky marketplace retention curves" + + # ────────────────────────────────────────────── + # 10. Supply-Demand Ratio + # ────────────────────────────────────────────── + - name: supply_demand_ratio + display_name: "Supply-Demand Ratio" + definition: > + The ratio of active supply units to active demand sessions or + buyers in a given period. This is the marketplace's balance + indicator. Too much supply = poor supplier economics and churn. + Too much demand = poor buyer experience and churn. The optimal + ratio varies by marketplace type but must be actively managed. + formula: "Active Supply Units / Active Demand Units (or sessions, requests)" + benchmarks: + poor: ">10:1 or <1:5 (severe imbalance in either direction)" + average: "5:1 to 1:3 (manageable imbalance with intervention)" + good: "3:1 to 1:1 (balanced; both sides experience reasonable matching)" + excellent: "Dynamically managed ratio with <10% variance from target across segments" + stage_notes: + idea: "Consciously constrain the oversupplied side. Launch supply-constrained if uncertain." + validation: "The ratio that produces >50% supply liquidity and >50% demand fill rate is your target." + early_traction: "Monitor ratio by geography and category. Aggregates mask local imbalances." + growth: "Build automated supply/demand throttling. Manual balancing does not scale." + scale: "Ratio management becomes a core competency. Pricing, incentives, and algorithmic matching all serve balance." + data_source: "NFX marketplace dynamics research; Uber surge pricing documentation" + + # ────────────────────────────────────────────── + # 11. Time to First Transaction + # ────────────────────────────────────────────── + - name: time_to_first_transaction + display_name: "Time to First Transaction" + definition: > + Elapsed time from a new user's registration (supply or demand + side) to their first completed transaction. Measures onboarding + friction and marketplace readiness. Long time-to-first-transaction + kills activation rates, and dead signups are the silent killer + of marketplace growth. + formula: "MEDIAN(first_transaction_timestamp - registration_timestamp) per cohort" + benchmarks: + poor: ">30 days (most users will never transact)" + average: "7-30 days (acceptable for high-consideration purchases)" + good: "1-7 days (strong activation; marketplace delivers value quickly)" + excellent: "<24 hours (on-demand or impulse marketplace with immediate gratification)" + stage_notes: + idea: "Hand-hold first users to first transaction. Concierge the match." + validation: "Measure separately for supply and demand. If supply activates in days but demand takes weeks, the problem is demand-side." + early_traction: "Reduce time-to-first-transaction by pre-curating supply for new buyers." + growth: "Automate activation flows. Every day of delay costs ~10% of potential activation." + scale: "Time-to-first-transaction should be near-instant in commodified categories." + data_source: "NFX activation benchmarks; Lenny Rachitsky onboarding data" + + # ────────────────────────────────────────────── + # 12. Average Order Value (AOV) + # ────────────────────────────────────────────── + - name: average_order_value + display_name: "Average Order Value (AOV)" + definition: > + Mean transaction value across all completed orders. AOV determines + the absolute contribution margin per transaction and shapes + viable take rates — a 15% take rate on a $20 AOV generates $3; + the same rate on a $2,000 AOV generates $300. AOV drives + marketplace unit economics more than almost any other variable. + formula: "Total GMV / Total Completed Transactions" + benchmarks: + poor: "AOV declining QoQ without strategic intent (discounting or mix shift)" + average: "AOV stable but below category median" + good: "AOV at or above category median with stable or improving trend" + excellent: "AOV growing through mix shift toward higher-value transactions" + stage_notes: + idea: "AOV is a hypothesis. Validate by studying existing transaction patterns in the category." + validation: "Track AOV distribution, not just mean. A bimodal AOV distribution signals two different use cases." + early_traction: "AOV x Take Rate x Transactions = Revenue. Optimise the combination, not any single variable." + growth: "Introduce upsell, bundling, or premium tiers to lift AOV without adding transaction count." + scale: "AOV is largely a function of category mix. Expanding into lower-AOV categories dilutes blended AOV — offset with volume." + data_source: "a16z Marketplace 100; Etsy, Fiverr, Upwork public filings" + + # ────────────────────────────────────────────── + # 13. Contribution Margin per Transaction + # ────────────────────────────────────────────── + - name: contribution_margin_per_transaction + display_name: "Contribution Margin per Transaction" + definition: > + Revenue retained by the marketplace on a single transaction minus + all variable costs directly attributable to that transaction: + payment processing, trust and safety costs, customer support, + insurance, fraud losses, and supply-side incentives. This is the + marketplace's true per-unit economics — the building block that + must be positive for the model to work. + formula: "(AOV x Take Rate) - Payment Processing - T&S Cost - Support Cost - Insurance - Fraud Loss - Supply Incentive" + benchmarks: + poor: "Negative (marketplace subsidises each transaction; only viable with clear path to positive)" + average: "$0.50-$2.00 for low-AOV (<$50); $5-$20 for mid-AOV ($50-$500)" + good: "$2-$5 for low-AOV; $20-$50 for mid-AOV" + excellent: ">$5 for low-AOV; >$50 for mid-AOV; consistent across segments" + stage_notes: + idea: "Model contribution margin with realistic variable cost assumptions. Do not assume payment processing away." + validation: "Negative contribution margin is acceptable if the path to positive is a function of volume, not hope." + early_traction: "Contribution margin must be positive or trending positive. Negative at this stage with no plan is fatal." + growth: "Contribution margin expansion comes from take rate increases, payment cost negotiation, and fraud reduction." + scale: "Contribution margin should improve at scale through operational leverage on variable costs." + data_source: "Bill Gurley 'All Revenue is Not Created Equal' (2011); marketplace S-1 filings" + + # ────────────────────────────────────────────── + # 14. Network Effects Score + # ────────────────────────────────────────────── + - name: network_effects_score + display_name: "Network Effects Score" + definition: > + A composite indicator measuring the strength of cross-side network + effects: does adding one more supplier make the marketplace more + valuable to buyers, and vice versa? Calculated by measuring the + marginal impact of supply/demand growth on key engagement and + conversion metrics for the opposite side. Strong network effects + are the only durable moat in a marketplace business. + formula: "Composite of: (1) demand conversion lift per 10% supply growth, (2) supply retention lift per 10% demand growth, (3) organic acquisition rate trend" + benchmarks: + poor: "No measurable improvement in opposite-side metrics when one side grows" + average: "Weak but detectable cross-side lift (1-3% improvement per 10% growth)" + good: "Clear cross-side lift (3-7% improvement per 10% growth) with improving organic share" + excellent: ">7% cross-side lift per 10% growth; >60% organic acquisition on both sides" + stage_notes: + idea: "Network effects are theorised, not measured. Articulate the mechanism." + validation: "Look for any signal: does adding more supply improve demand conversion, even anecdotally?" + early_traction: "Quantify network effects in at least one geography or category. This data is essential for fundraising." + growth: "Network effects should be measurably accelerating growth and reducing CAC." + scale: "Network effects are the moat. If they are not compounding, the marketplace is a commodity intermediary." + data_source: "NFX network effects taxonomy; a16z marketplace defensibility framework" + + # ────────────────────────────────────────────── + # 15. Cross-Side Elasticity + # ────────────────────────────────────────────── + - name: cross_side_elasticity + display_name: "Cross-Side Elasticity" + definition: > + The percentage change in engagement or transaction volume on one + side of the marketplace in response to a percentage change in the + other side. Positive cross-side elasticity = virtuous cycle. + Negative = supply flooding or demand overwhelming supply capacity. + The sign and magnitude of this elasticity determine whether + growth investments on one side pay off on the other. + formula: "% Change in Demand Transactions / % Change in Active Supply (and inverse)" + benchmarks: + poor: "Negative elasticity (more supply = worse demand outcomes; market is flooded)" + average: "0-0.3 (weak linkage; sides grow somewhat independently)" + good: "0.3-0.7 (meaningful cross-side amplification)" + excellent: ">0.7 (strong virtuous cycle; each side's growth accelerates the other)" + stage_notes: + idea: "Elasticity is theoretical. Map the causal chain: how does more supply help demand, specifically?" + validation: "Measure in the narrow launch segment. Global cross-side elasticity is noise." + early_traction: "Positive elasticity in core segments confirms the marketplace thesis." + growth: "Use cross-side elasticity to allocate growth spend: invest in the side with higher marginal impact." + scale: "Monitor for elasticity decay — the point at which adding more supply yields diminishing demand returns." + data_source: "NFX marketplace research; academic literature on two-sided markets (Rochet & Tirole)" + + # ────────────────────────────────────────────── + # 16. Disintermediation Rate + # ────────────────────────────────────────────── + - name: disintermediation_rate + display_name: "Disintermediation Rate" + definition: > + The estimated percentage of matched supply-demand pairs that + subsequently transact outside the marketplace, bypassing the + platform's payment and take rate. Disintermediation — going + around the platform — is the existential threat for any + marketplace that connects parties without providing ongoing, + per-transaction value. + formula: "Estimated Off-Platform Transactions / (On-Platform + Estimated Off-Platform) x 100" + benchmarks: + poor: ">20% (platform is a lead-gen tool, not a marketplace)" + average: "10-20% (some leakage, manageable with value-add services)" + good: "5-10% (low leakage; platform provides sufficient ongoing value)" + excellent: "<5% (platform is essential to the transaction — payments, trust, insurance, dispute resolution)" + stage_notes: + idea: "Design the transaction flow to make on-platform completion frictionless and off-platform completion risky." + validation: "Monitor for early disintermediation signals: messaging exchanges, phone number sharing." + early_traction: "Introduce value-added services that make staying on-platform the rational choice." + growth: "Build payments, reviews, insurance, and guarantees that only work on-platform." + scale: "Disintermediation rate should be <5%. If higher, the platform's value-add is insufficient." + data_source: "Bill Gurley marketplace economics writing; Airbnb, Upwork disintermediation countermeasures" + + # ────────────────────────────────────────────── + # 17. Supply Churn + # ────────────────────────────────────────────── + - name: supply_churn + display_name: "Supply Churn" + definition: > + Percentage of active suppliers who become inactive (no transactions + or listings) within a defined period. Supply churn is more damaging + than demand churn in most marketplaces because replacing quality + supply is harder and more expensive than acquiring new demand. + Supply churn triggers a doom loop: less supply -> worse demand + experience -> less demand -> even less supply. + formula: "Suppliers Active in Prior Period but Inactive in Current Period / Suppliers Active in Prior Period x 100" + benchmarks: + poor: ">10% monthly (supply base is a revolving door)" + average: "5-10% monthly (significant churn requiring constant replacement)" + good: "2-5% monthly (manageable; net supply growth positive)" + excellent: "<2% monthly (sticky supply base; marketplace is the primary channel)" + stage_notes: + idea: "N/A." + validation: "Track from the first cohort. Early supply churn reveals whether the value proposition works." + early_traction: "Supply churn >5% monthly demands immediate investigation. Are suppliers earning enough?" + growth: "Segment churn by supplier tier. Losing top sellers is catastrophic; losing low-quality supply can be healthy." + scale: "Supply churn should decline as marketplace becomes the dominant channel and switching costs increase." + data_source: "Lenny Rachitsky marketplace retention data; Etsy, Fiverr S-1 disclosures" + + # ────────────────────────────────────────────── + # 18. Demand Churn + # ────────────────────────────────────────────── + - name: demand_churn + display_name: "Demand Churn" + definition: > + Percentage of active buyers who become inactive within a defined + period. While demand churn is generally easier to address than + supply churn (more channels, lower CAC), sustained demand churn + erodes marketplace liquidity and signals either poor supply + quality, insufficient selection, or competitive displacement. + formula: "Buyers Active in Prior Period but Inactive in Current Period / Buyers Active in Prior Period x 100" + benchmarks: + poor: ">15% monthly (buyers do not return; marketplace is transactional, not habitual)" + average: "8-15% monthly (moderate; typical for low-frequency purchase categories)" + good: "3-8% monthly (healthy for most marketplace categories)" + excellent: "<3% monthly (exceptional buyer loyalty; strong brand and habit)" + stage_notes: + idea: "N/A." + validation: "Demand churn in the first 90 days of a cohort is the activation failure rate." + early_traction: "Separate activation churn (never completed second transaction) from mature churn (stopped after multiple transactions)." + growth: "Demand churn should decrease as selection improves and cross-side network effects strengthen." + scale: "Demand churn is primarily driven by supply quality and competitive alternatives at scale." + data_source: "a16z Marketplace 100; Lenny Rachitsky marketplace retention curves" + + # ────────────────────────────────────────────── + # 19. Organic vs Paid Supply % + # ────────────────────────────────────────────── + - name: organic_supply_pct + display_name: "Organic vs Paid Supply %" + definition: > + The share of new supply-side sign-ups or activations that arrive + without paid acquisition spend — through word-of-mouth, direct + traffic, organic search, or supply-side referrals. High organic + supply percentage is the clearest evidence that the marketplace + delivers real value to its supply side. + formula: "Organic New Suppliers / Total New Suppliers x 100" + benchmarks: + poor: "<20% organic (marketplace is buying supply; unsustainable without capital)" + average: "20-40% organic (mixed; paid is still dominant)" + good: "40-60% organic (healthy; word-of-mouth is building)" + excellent: ">60% organic (supply-side flywheel active; marketplace is the destination)" + stage_notes: + idea: "100% of early supply is hand-recruited. That is normal." + validation: "Any organic supply arrival is a meaningful signal of product-market fit." + early_traction: "Organic supply should be emerging. If still 100% paid, the supply value prop may be broken." + growth: "Target >50% organic. Every percentage point of organic supply improves unit economics." + scale: ">60% organic is table stakes for healthy marketplace economics at scale." + data_source: "NFX organic growth benchmarks; marketplace operator surveys" + + # ────────────────────────────────────────────── + # 20. Organic vs Paid Demand % + # ────────────────────────────────────────────── + - name: organic_demand_pct + display_name: "Organic vs Paid Demand %" + definition: > + The share of new demand-side users that arrive organically — via + word-of-mouth, direct traffic, SEO, or buyer referrals. A + marketplace's brand strength and demand-side network effects are + reflected in this metric. High organic demand % compresses + blended CAC and improves contribution margins. + formula: "Organic New Buyers / Total New Buyers x 100" + benchmarks: + poor: "<25% organic (demand generation entirely dependent on paid channels)" + average: "25-45% organic (mixed acquisition; some brand recognition)" + good: "45-65% organic (strong brand; demand-side word-of-mouth active)" + excellent: ">65% organic (marketplace is a verb — 'Uber it', 'Airbnb that')" + stage_notes: + idea: "Demand is manually recruited or channel-hacked. Normal." + validation: "Organic demand arriving for the first time indicates buyer pull, not founder push." + early_traction: "Organic demand should be climbing steadily. SEO and word-of-mouth should be measurable." + growth: "Brand investment pays compound returns. Organic >50% is the inflection to profitable growth." + scale: "Organic demand >65% is the sign of a marketplace with a durable brand moat." + data_source: "a16z marketplace data; Airbnb, DoorDash S-1 acquisition mix disclosures" + + # ────────────────────────────────────────────── + # 21. ARPU — Supply Side + # ────────────────────────────────────────────── + - name: arpu_supply + display_name: "Average Revenue Per User — Supply Side" + definition: > + Average net revenue the marketplace earns from each active + supplier over a period. This is not the supplier's gross earnings — + it is the platform's take from each supplier's activity. ARPU + (supply) determines whether the marketplace can afford its + supply-side CAC and whether the supply-side unit economics work. + formula: "Total Net Revenue from Supply-Side Activity / Active Suppliers" + benchmarks: + poor: "ARPU (supply) < supply-side CAC / 6 (>6-month payback)" + average: "ARPU (supply) = supply-side CAC / 3-6 (3-6 month payback)" + good: "ARPU (supply) = supply-side CAC / 1-3 (1-3 month payback)" + excellent: "ARPU (supply) > supply-side CAC (payback in first period)" + stage_notes: + idea: "Model ARPU from assumed transaction frequency x AOV x take rate." + validation: "Actual ARPU data from first cohorts. Compare to supply CAC immediately." + early_traction: "ARPU should be growing as suppliers transact more frequently and at higher AOV." + growth: "Introduce premium supply tiers, advertising, or SaaS tools to lift ARPU beyond take rate alone." + scale: "Supply-side ARPU should grow through value-added services, not take rate increases alone." + data_source: "Etsy, Fiverr, Upwork, Airbnb public filings; a16z marketplace ARPU analysis" + + # ────────────────────────────────────────────── + # 22. ARPU — Demand Side + # ────────────────────────────────────────────── + - name: arpu_demand + display_name: "Average Revenue Per User — Demand Side" + definition: > + Average net revenue the marketplace earns from each active buyer + over a period. Typically a function of purchase frequency, AOV, + and take rate. ARPU (demand) rising over time signals increasing + buyer engagement and expanding share of wallet. + formula: "Total Net Revenue from Demand-Side Activity / Active Buyers" + benchmarks: + poor: "ARPU (demand) < demand-side CAC / 6" + average: "ARPU (demand) = demand-side CAC / 3-6" + good: "ARPU (demand) = demand-side CAC / 1-3" + excellent: "ARPU (demand) > demand-side CAC (first-period payback)" + stage_notes: + idea: "Estimate from category purchase frequency x AOV x take rate." + validation: "Early ARPU data. Even small numbers are informative if the cohort is defined." + early_traction: "ARPU should be growing as buyers increase purchase frequency." + growth: "Cross-sell into adjacent categories to lift ARPU. Single-category ARPU has a ceiling." + scale: "ARPU (demand) growth at scale comes from category expansion and loyalty programs." + data_source: "a16z Marketplace 100; DoorDash, Instacart S-1 disclosures" + + # ────────────────────────────────────────────── + # 23. Marketplace Quality Score + # ────────────────────────────────────────────── + - name: marketplace_quality_score + display_name: "Marketplace Quality Score" + definition: > + A composite quality metric derived from ratings, reviews, + dispute rates, and completion rates. Measures whether the + marketplace maintains the trust that makes it preferable to + direct transactions. Quality is the invisible infrastructure + of marketplace defensibility — when quality degrades, both + sides abandon the platform, often irreversibly. + formula: "Weighted composite: (Avg Rating x 0.3) + (Review Coverage % x 0.2) + ((1 - Dispute Rate) x 0.25) + (Completion Rate x 0.25)" + benchmarks: + poor: "Score <60 (frequent disputes, low review coverage, inconsistent quality)" + average: "Score 60-75 (adequate but quality is not a differentiator)" + good: "Score 75-85 (quality is visible and trusted by both sides)" + excellent: "Score >85 (quality is a moat; buyers trust marketplace curation)" + stage_notes: + idea: "Quality standards should be defined before launch. Curate aggressively." + validation: "Demand quality reviews on every transaction. Build the review habit early." + early_traction: "Remove or suspend supply that falls below quality thresholds. Short-term pain, long-term survival." + growth: "Quality at scale requires automated quality scoring, not just user reviews." + scale: "Quality degradation at scale is the most common cause of marketplace decline. Invest in quality operations proportionally." + data_source: "Sarah Tavel 'Hierarchy of Marketplaces' Level 3 (quality); Airbnb Superhost program data" + + # ────────────────────────────────────────────── + # 24. Trust & Safety Cost per Transaction + # ────────────────────────────────────────────── + - name: trust_safety_cost_per_transaction + display_name: "Trust & Safety Cost per Transaction" + definition: > + All costs associated with maintaining marketplace trust and safety + on a per-transaction basis: fraud detection and prevention, + identity verification, content moderation, dispute resolution, + insurance or guarantee payouts, and customer support for trust- + related issues. This cost is the price of being an intermediary + rather than a direct provider — and it never reaches zero. + formula: "(Fraud Prevention + ID Verification + Moderation + Dispute Resolution + Insurance Payouts + T&S Support) / Total Transactions" + benchmarks: + poor: "T&S cost > 5% of take rate revenue (consuming too much of the platform's margin)" + average: "T&S cost = 3-5% of take rate revenue" + good: "T&S cost = 1-3% of take rate revenue" + excellent: "T&S cost < 1% of take rate revenue with fraud rate <0.5%" + stage_notes: + idea: "Budget for T&S from day one. Marketplaces that defer trust investment pay dearly later." + validation: "Manual T&S is fine at small scale. Track the cost per transaction to model future needs." + early_traction: "Invest in automated fraud detection and identity verification. Manual review does not scale." + growth: "T&S cost per transaction should decline as automation improves and trust signals accumulate." + scale: "T&S is a permanent cost centre. Best-in-class marketplaces spend 1-2% of net revenue on T&S at scale." + data_source: "Marketplace operator surveys; Airbnb, Uber T&S cost disclosures in public filings" diff --git a/plugins/foreman/content/industry-packs/marketplace/marketplace-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/marketplace/marketplace-diagnostic-rules.yaml new file mode 100644 index 0000000..6e25246 --- /dev/null +++ b/plugins/foreman/content/industry-packs/marketplace/marketplace-diagnostic-rules.yaml @@ -0,0 +1,1061 @@ +# Marketplace Industry Pack — Diagnostic Rules +# Provides marketplace-specific rules for each of the 20 existing diagnostics, +# plus 5 marketplace-native diagnostics that address two-sided platform +# failure modes: chicken-and-egg failure, liquidity crisis, disintermediation +# risk, quality degradation, and trust collapse. +# +# Each diagnostic rule reframes the triage through a two-sided lens: +# is the problem on the supply side, the demand side, or the platform layer? +# Every rule reflects genuine marketplace dynamics, not single-sided +# business logic with marketplace vocabulary. + +pack: marketplace +author: "Fatih Guner" +type: diagnostic_rules +version: "1.0.0" + +# ============================================================ +# EXISTING DIAGNOSTIC OVERLAYS (20) +# ============================================================ + +diagnostic_overlays: + + # ────────────────────────────────────────────── + # 1. Revenue Diagnosis + # ────────────────────────────────────────────── + - diagnostic: revenue-diagnosis + marketplace_reframe: > + Revenue in a marketplace is a three-variable equation: + GMV x Take Rate = Net Revenue. A revenue problem can originate + from the supply side (insufficient or declining supply reducing + GMV), the demand side (insufficient or declining demand reducing + GMV), or the platform layer (take rate compression, payment + leakage, or disintermediation). Standard revenue diagnosis + conflates these into a single pipeline analysis. In a marketplace, + you must decompose first. + + additional_triage_questions: + - question: "Is GMV declining, or is GMV stable but net revenue declining?" + supply_signal: "GMV declining because supply is shrinking — fewer listings, fewer available providers, fewer active sellers." + demand_signal: "GMV declining because demand is shrinking — fewer buyers, fewer searches, lower purchase frequency." + platform_signal: "GMV stable but net revenue declining — take rate compression, fee structure leakage, or increasing cost of revenue." + - question: "Which side of the marketplace is showing weakness first?" + supply_signal: "Supply metrics degrading first: rising supply churn, declining supply liquidity, fewer new listings." + demand_signal: "Demand metrics degrading first: declining repeat rate, rising demand churn, lower conversion from search to transaction." + platform_signal: "Both sides stable but contribution margin per transaction declining — variable costs rising or take rate under competitive pressure." + - question: "Is revenue concentrated in a small number of supply-side participants?" + high_concentration: "Top 10% of supply generates >50% of GMV — revenue is fragile. Loss of key suppliers produces disproportionate impact." + moderate_concentration: "Top 10% generates 30-50% of GMV — some concentration risk but diversified enough." + low_concentration: "Revenue distributed across supply base — healthier but may indicate lack of power sellers." + - question: "Has the take rate been stable, or has competitive pressure forced adjustments?" + stable: "Take rate unchanged — revenue problem is a volume problem." + declining: "Take rate declining under competitive pressure or supplier negotiation — margin compression." + increasing: "Take rate recently increased — check if supply-side response (churn, price increases, disintermediation) is causing GMV decline." + + marketplace_diagnoses: + - name: supply-side-revenue-collapse + description: "Revenue declining because supply is leaving or reducing activity. The marketplace's supply-side value proposition is failing." + signals: ["Rising supply churn", "Declining listings or available capacity", "Supply-side NPS declining", "Competitors offering lower take rates"] + routes_to_skills: [porters-five-forces, business-model-canvas, net-promoter-score] + routes_to_templates: [unit-economics-snapshot, strategic-analysis-one-pager] + - name: demand-side-revenue-collapse + description: "Revenue declining because buyers are leaving or reducing purchase frequency. The marketplace's demand-side experience or selection is failing." + signals: ["Rising demand churn", "Declining repeat rate", "Demand fill rate dropping", "Competitor capturing buyer attention"] + routes_to_skills: [four-ps-marketing, net-promoter-score, product-life-cycle] + routes_to_templates: [unit-economics-snapshot, quarterly-strategic-review] + - name: take-rate-erosion + description: "GMV stable or growing but net revenue declining because take rate is compressing — due to competitive pressure, supply negotiation, or fee structure leakage." + signals: ["Take rate declining QoQ", "Supplier demands for lower fees", "Competitor offering lower rates", "Increasing off-platform transactions"] + routes_to_skills: [porters-five-forces, business-model-canvas, information-asymmetry] + routes_to_templates: [unit-economics-snapshot, competitive-landscape-brief] + + # ────────────────────────────────────────────── + # 2. Growth Stall Diagnosis + # ────────────────────────────────────────────── + - diagnostic: growth-stall-diagnosis + marketplace_reframe: > + Growth stalls in marketplaces come in three flavours: supply- + constrained (demand exists but supply cannot fulfil it), + demand-constrained (supply exists but buyers are not coming), + or liquidity-constrained (both sides present but matching is + poor). The standard growth stall diagnosis does not distinguish + these — and the interventions are entirely different. + + additional_triage_questions: + - question: "Is the stall happening on the supply side, the demand side, or both?" + supply_constrained: "Demand metrics healthy (searches, intent) but supply cannot fulfil — low fill rate, long wait times, limited selection." + demand_constrained: "Supply available and liquid but demand is not growing — low search volume, poor conversion, acquisition channels exhausted." + liquidity_constrained: "Both sides present but matching is poor — high abandonment, low match quality, supply and demand in wrong segments." + - question: "Has growth stalled in all markets/categories or only specific ones?" + universal_stall: "Growth stalled across all segments — likely a platform-level issue (brand, trust, product)." + segment_specific: "Growth stalled in mature segments but continuing in newer ones — lifecycle issue, not a crisis." + geographic_specific: "Growth stalled in specific geographies — local competitive dynamics or supply exhaustion." + - question: "Is the growth stall correlated with a specific change?" + take_rate_change: "Growth stalled after take rate increase — supply-side reaction." + quality_change: "Growth stalled after quality standards tightened — supply reduced but remaining supply may be higher quality." + competitive_entry: "Growth stalled after competitor launched — direct competitive displacement." + no_change: "No identifiable cause — likely market saturation in current segments." + + marketplace_diagnoses: + - name: supply-constrained-growth + description: "Demand exceeds supply capacity. Growth is capped by the marketplace's ability to recruit and retain supply." + signals: ["Low fill rate", "Long wait times", "Supply liquidity >80% (supply fully utilised)", "Rising demand-side complaints about availability"] + routes_to_skills: [blue-ocean-strategy, four-ps-marketing, cialdini-influence] + routes_to_templates: [new-initiative-brief, market-opportunity-summary] + - name: demand-constrained-growth + description: "Supply available but demand is not growing. Acquisition channels exhausted or brand awareness insufficient." + signals: ["Supply liquidity <30%", "High supply churn (supply not earning enough)", "Demand acquisition cost rising", "Organic demand share declining"] + routes_to_skills: [four-ps-marketing, tipping-point, disruptive-innovation] + routes_to_templates: [strategic-analysis-one-pager, market-opportunity-summary] + - name: liquidity-failure + description: "Both sides present but matching is poor. The marketplace has volume without liquidity." + signals: ["Low fill rate despite adequate supply", "Low supply liquidity despite adequate demand", "High search abandonment", "Geographic or category mismatch between supply and demand"] + routes_to_skills: [systems-thinking, kaizen-bpr, balanced-scorecard] + routes_to_templates: [action-plan, new-initiative-brief] + + # ────────────────────────────────────────────── + # 3. Competitive Threat Diagnosis + # ────────────────────────────────────────────── + - diagnostic: competitive-threat-diagnosis + marketplace_reframe: > + Competitive threats to marketplaces are asymmetric: a competitor + can attack the supply side, the demand side, or both — and the + most dangerous attacks target only one side. A competitor that + recruits your best supply does not need to acquire demand directly; + weakened supply degrades the demand experience, which drives demand + to the competitor organically. + + additional_triage_questions: + - question: "Which side of your marketplace is the competitor attacking?" + supply_attack: "Competitor is recruiting your supply with lower take rates, guaranteed earnings, or better tools." + demand_attack: "Competitor is capturing your demand with lower prices, better UX, or superior selection in a niche." + both_sides: "Competitor is attacking both sides simultaneously — well-funded direct assault." + neither_directly: "Competitor is not a marketplace but a substitute (direct channel, SaaS tool for supply, aggregator for demand)." + - question: "What is the multi-homing rate on each side?" + high_supply_multihoming: "Supply lists on multiple platforms — low switching cost, commoditised supply-side experience." + high_demand_multihoming: "Buyers shop across platforms — low brand loyalty, price-sensitive demand." + low_multihoming: "Both sides primarily use your marketplace — strong defensibility." + - question: "Is the competitor vertical (category-specific) or horizontal (broad)?" + vertical: "Vertical competitor with deeper expertise in a specific category — the classic marketplace unbundling threat." + horizontal: "Horizontal competitor (Amazon, Google) leveraging existing user base — platform envelopment." + new_model: "Different marketplace model entirely (managed vs unmanaged, on-demand vs scheduled) — structural disruption." + + marketplace_diagnoses: + - name: supply-side-poaching + description: "Competitor systematically recruiting your supply base through lower take rates or better value proposition." + signals: ["Rising supply churn among top performers", "Supply multi-homing increasing", "Supply ARPU declining as they diversify across platforms"] + routes_to_skills: [porters-five-forces, art-of-war, first-mover-strategy] + routes_to_templates: [competitive-landscape-brief, action-plan] + - name: vertical-unbundling + description: "A category-specific competitor is offering deeper expertise and better supply-demand matching in a segment that represents significant GMV for your marketplace." + signals: ["Category-specific GMV declining", "Best supply in that category leaving", "Demand conversion declining for that category"] + routes_to_skills: [disruptive-innovation, blue-ocean-strategy, product-life-cycle] + routes_to_templates: [competitive-landscape-brief, strategic-analysis-one-pager] + - name: platform-envelopment + description: "A larger platform is adding marketplace functionality that leverages its existing user base, bypassing the chicken-and-egg problem." + signals: ["Demand acquisition cost rising due to increased competition for attention", "Supply attracted to larger platform's existing demand base", "Your brand losing SEO positions to the larger platform"] + routes_to_skills: [porters-five-forces, scenario-planning, art-of-war] + routes_to_templates: [competitive-landscape-brief, risk-assessment-brief] + + # ────────────────────────────────────────────── + # 4. Customer Churn Diagnosis + # ────────────────────────────────────────────── + - diagnostic: customer-churn-diagnosis + marketplace_reframe: > + Churn in a marketplace must be diagnosed separately for supply + and demand — and the causes are different for each. Supply churn + is driven by economics (not earning enough), experience (platform + friction), and alternatives (competitors or direct channels). + Demand churn is driven by quality (bad experiences), selection + (cannot find what they want), and trust (safety or fraud concerns). + The two churn types interact: supply churn causes demand churn + causes more supply churn. + + additional_triage_questions: + - question: "Is churn rising on the supply side, the demand side, or both?" + supply_churn: "Supply leaving — proceed to supply-specific diagnosis." + demand_churn: "Demand leaving — proceed to demand-specific diagnosis." + both: "Both sides churning — likely a death spiral. Determine which side started churning first." + - question: "[Supply] Why are suppliers leaving?" + economics: "Suppliers not earning enough — low transaction volume, low AOV, high take rate." + experience: "Platform friction — onboarding difficulty, poor tools, slow payouts, unresponsive support." + alternatives: "Better options available — competitor, direct channel, changed business model." + quality_pressure: "Platform imposed quality requirements the supplier cannot or will not meet." + - question: "[Demand] Why are buyers leaving?" + quality: "Bad transaction experiences — supply quality inconsistent, orders unfulfilled, disputes unresolved." + selection: "Cannot find what they want — limited supply in their category or geography." + trust: "Trust broken — fraud, safety incident, or feel unprotected by platform." + price: "Cheaper alternatives available — competitor, direct from supplier." + + marketplace_diagnoses: + - name: supply-economics-churn + description: "Supply is churning because the platform does not generate enough economic value for participants — transactions too infrequent, take rate too high, or AOV too low." + signals: ["Supply earnings per active period declining", "Supply liquidity declining", "Supply NPS on earnings-related questions dropping"] + routes_to_skills: [business-model-canvas, four-ps-marketing, balanced-scorecard] + routes_to_templates: [unit-economics-snapshot, action-plan] + - name: demand-quality-churn + description: "Demand is churning because supply quality is inconsistent or declining — bad experiences, unmet expectations, trust erosion." + signals: ["Ratings declining", "Dispute rate rising", "Demand repeat rate falling", "Demand NPS declining"] + routes_to_skills: [net-promoter-score, kaizen-bpr, systems-thinking] + routes_to_templates: [quarterly-business-review, action-plan] + - name: death-spiral-churn + description: "Supply and demand churn are reinforcing each other in a vicious cycle. Less supply causes worse demand experience causes demand churn causes supply earnings decline causes supply churn." + signals: ["Both sides' churn accelerating simultaneously", "Supply liquidity and demand fill rate both declining", "Organic acquisition on both sides declining"] + routes_to_skills: [systems-thinking, scenario-planning, kotter-change-model] + routes_to_templates: [risk-assessment-brief, action-plan] + red_flag: true + + # ────────────────────────────────────────────── + # 5. Pricing Diagnosis + # ────────────────────────────────────────────── + - diagnostic: pricing-diagnosis + marketplace_reframe: > + Marketplace pricing is not a single price decision — it is a + three-part structure: what supply charges, what demand pays, and + what the platform takes in between. A pricing problem can + originate from any of these three layers. Supply may be + overpricing (demand churn), underpricing (supply churn from + unsustainable economics), or the take rate may be misaligned + with the value the platform provides. + + additional_triage_questions: + - question: "Where does the pricing problem manifest?" + supply_pricing: "Suppliers pricing too high → demand conversion suffers. Or pricing too low → supply economics unsustainable." + demand_perception: "Demand perceives total cost (price + fees) as too high, even if supply prices are reasonable — platform fees are the issue." + take_rate: "Take rate too high → supply raises prices to compensate → demand experience suffers. Or take rate too low → platform cannot invest in quality." + - question: "Does the marketplace set prices, guide prices, or allow free pricing?" + platform_sets: "Platform-set pricing (Uber model) — pricing problems are platform responsibility." + platform_guides: "Platform provides guidance (suggested prices, dynamic pricing tools) — pricing problems are shared." + free_pricing: "Supply sets prices freely — pricing problems may require market design intervention (price floors, transparency tools)." + - question: "How does your pricing compare to off-platform alternatives?" + above_market: "Marketplace prices (including fees) above direct alternatives — must justify with trust, convenience, or guarantees." + at_market: "Marketplace prices comparable to alternatives — no pricing premium burden." + below_market: "Marketplace prices below alternatives — potential supply sustainability issue." + + marketplace_diagnoses: + - name: take-rate-misalignment + description: "The platform's take rate does not match the value it provides. Too high relative to value-add, or structured in a way that creates perverse incentives." + signals: ["Increasing disintermediation", "Supply-side price inflation to offset take rate", "Supply churn concentrated among high-volume sellers"] + routes_to_skills: [four-ps-marketing, business-model-canvas, information-asymmetry] + routes_to_templates: [unit-economics-snapshot, strategic-analysis-one-pager] + - name: supply-pricing-dysfunction + description: "Supply-side pricing is creating demand problems — prices too high, too variable, or too opaque relative to alternatives." + signals: ["Demand conversion below category benchmarks", "High cart abandonment at price reveal", "Demand complaints about pricing"] + routes_to_skills: [four-ps-marketing, thinking-fast-and-slow, information-asymmetry] + routes_to_templates: [unit-economics-snapshot, action-plan] + - name: fee-structure-leakage + description: "The fee structure has gaps — certain transaction types, payment methods, or customer segments bypass fees, eroding effective take rate." + signals: ["Effective take rate below stated take rate", "Growing transaction volume through fee-exempt channels", "Supply routing transactions to minimise fees"] + routes_to_skills: [game-theory-fundamentals, business-model-canvas, systems-thinking] + routes_to_templates: [unit-economics-snapshot, decision-journal] + + # ────────────────────────────────────────────── + # 6. Product-Market Fit Diagnosis + # ────────────────────────────────────────────── + - diagnostic: product-market-fit-diagnosis + marketplace_reframe: > + Product-market fit in a marketplace is actually product-market- + market fit: the platform must fit both the supply market and the + demand market simultaneously. You can have strong supply-side PMF + (suppliers love the platform) with weak demand-side PMF (buyers + do not return), or vice versa. True marketplace PMF exists when + both sides transact repeatedly, organically, and with satisfaction. + + additional_triage_questions: + - question: "Which side shows stronger signs of product-market fit?" + supply_stronger: "Supply is engaged and retained, but demand does not convert or return — demand-side PMF missing." + demand_stronger: "Demand is eager but supply is insufficient, unreliable, or churning — supply-side PMF missing." + neither: "Neither side shows strong retention or satisfaction — fundamental marketplace thesis may be wrong." + both: "Both sides transacting and returning — marketplace PMF exists. The problem is scaling it." + - question: "In your strongest segment (geography, category), do you see organic repeat behaviour on both sides?" + yes_both: "Both sides returning organically in at least one segment — PMF exists in a niche. The task is expansion." + yes_one: "Organic repeat on one side only — half-PMF. Diagnose the weak side." + no: "No organic repeat on either side in any segment — PMF has not been achieved." + + marketplace_diagnoses: + - name: supply-side-pmf-failure + description: "The marketplace does not deliver sufficient value to the supply side — suppliers do not earn enough, find the platform too frustrating, or have better alternatives." + signals: ["Low supply repeat rate (<30% at 90 days)", "Supply onboarding drop-off >50%", "Supply NPS below 20"] + routes_to_skills: [business-model-canvas, net-promoter-score, appreciative-inquiry] + routes_to_templates: [unit-economics-snapshot, action-plan] + - name: demand-side-pmf-failure + description: "The marketplace does not deliver sufficient value to the demand side — buyers cannot find what they want, do not trust the supply, or find the experience inferior to alternatives." + signals: ["Low demand repeat rate (<20% at 90 days)", "Low demand fill rate (<30%)", "Demand NPS below 20"] + routes_to_skills: [net-promoter-score, four-ps-marketing, blue-ocean-strategy] + routes_to_templates: [unit-economics-snapshot, action-plan] + - name: matching-failure + description: "Both sides are present and individually satisfied, but the matching mechanism is inadequate — wrong supply shown to wrong demand." + signals: ["Adequate supply and demand volume but low transaction rate", "High search abandonment", "Low fill rate despite available supply"] + routes_to_skills: [systems-thinking, kaizen-bpr, doblin-ten-types] + routes_to_templates: [action-plan, new-initiative-brief] + + # ────────────────────────────────────────────── + # 7. Fundraising Diagnosis + # ────────────────────────────────────────────── + - diagnostic: fundraising-diagnosis + marketplace_reframe: > + Marketplace fundraising requires a different narrative from SaaS. + Investors evaluate: (1) evidence of network effects, not just + revenue growth, (2) liquidity metrics, not just user counts, + (3) unit economics per transaction, not per subscription, + (4) defensibility through supply-side lock-in and demand-side + habit, not through product differentiation alone. + + additional_triage_questions: + - question: "Can you demonstrate measurable network effects?" + yes: "Quantified cross-side elasticity, improving organic acquisition %, declining blended CAC — strong fundraising position." + directional: "Anecdotal or directional evidence — sufficient for Seed/A, insufficient for later rounds." + no: "No measurable network effects — investors will question whether this is a marketplace or a lead-gen tool." + - question: "What are your marketplace-specific unit economics?" + strong: "Positive contribution margin per transaction, blended CAC payback <6 months, both sides' ARPU growing." + developing: "Contribution margin trending positive, payback improving — adequate for early-stage fundraising." + weak: "Negative contribution margin with unclear path to positive — requires a compelling scale narrative." + + marketplace_fundraising_signals: + investors_want_to_see: + - "GMV growth rate and net revenue growth rate (both, not just GMV)" + - "Take rate and its trajectory (stable or expanding?)" + - "Supply liquidity and demand fill rate (the marketplace is working)" + - "Repeat rates on both sides (retention, not just acquisition)" + - "Organic acquisition percentage on both sides (network effects producing free growth)" + - "Contribution margin per transaction (unit economics work)" + - "Cross-side elasticity data (network effects are real, not theoretical)" + common_fundraising_failures: + - "Leading with GMV without disclosing take rate — investors will compute net revenue regardless." + - "Claiming network effects without quantifying them." + - "Presenting blended metrics (blended CAC, blended retention) that mask supply-demand divergence." + - "No answer for 'what prevents disintermediation at scale?'" + + # ────────────────────────────────────────────── + # 8. Innovation Drought Diagnosis + # ────────────────────────────────────────────── + - diagnostic: innovation-drought-diagnosis + marketplace_reframe: > + Innovation drought in a marketplace manifests as matching + stagnation — the algorithm and UX stop improving, supply tools + stagnate, and the demand experience ossifies. The platform + becomes infrastructure rather than innovation. Meanwhile, + vertical competitors innovate on category-specific supply + curation and demand experience. + + additional_triage_questions: + - question: "When did you last materially improve the matching mechanism?" + recent: "Within 6 months — matching innovation is active." + stale: "6-18 months ago — matching is at risk of falling behind." + old: ">18 months — matching has stagnated. Competitors with better matching will capture supply and demand." + - question: "Are you investing in supply-side tools and demand-side experience equally?" + balanced: "Investment roughly proportional to each side's needs." + demand_heavy: "Innovation concentrated on demand UX — supply-side tools stagnating. Common pattern that erodes supply loyalty." + supply_heavy: "Innovation concentrated on supply tools — demand experience stagnating. Uncommon but dangerous." + + marketplace_diagnoses: + - name: matching-stagnation + description: "The marketplace's core matching mechanism has not improved materially, allowing competitors to offer better supply-demand pairing." + signals: ["Match quality scores declining or flat", "Search-to-transaction conversion stagnant", "Demand satisfaction with relevance declining"] + routes_to_skills: [kaizen-bpr, doblin-ten-types, ambidexterity] + routes_to_templates: [new-initiative-brief, action-plan] + - name: supply-side-tool-neglect + description: "Supply-side tools, analytics, and experience have not been innovated, while demand-side UX receives all investment." + signals: ["Supply NPS declining while demand NPS stable", "Supply churn rising among power users", "Competitor launching superior supply tools"] + routes_to_skills: [balanced-scorecard, doblin-ten-types, appreciative-inquiry] + routes_to_templates: [action-plan, new-initiative-brief] + + # ────────────────────────────────────────────── + # 9. Team Dysfunction Diagnosis + # ────────────────────────────────────────────── + - diagnostic: team-dysfunction-diagnosis + marketplace_reframe: > + Team dysfunction in marketplace companies often stems from the + structural tension between supply-side and demand-side teams. + Supply ops wants policies that protect suppliers. Growth wants + policies that attract buyers. Product tries to serve both and + satisfies neither. Without explicit cross-side governance, this + tension becomes dysfunction. + + additional_triage_questions: + - question: "Is the dysfunction between the supply-side team and the demand-side team?" + yes: "The core marketplace tension is unmanaged. Create formal cross-side governance." + no: "Dysfunction is within a team or at a leadership level — standard team diagnosis applies, but check for marketplace-specific causes." + - question: "Does the product/platform team have clear prioritisation rules for supply vs demand features?" + clear: "Prioritisation framework exists — dysfunction is elsewhere." + unclear: "No prioritisation framework — product team is pulled between supply and demand requests, creating frustration on both sides." + + marketplace_diagnoses: + - name: supply-demand-team-conflict + description: "Supply operations and demand growth teams have conflicting priorities without resolution mechanisms, causing organisational paralysis." + signals: ["Supply team and demand team presenting conflicting strategies", "Product backlog dominated by one side's requests", "Cross-functional projects stalling"] + routes_to_skills: [thomas-kilmann-conflict, hackman-enabling-conditions, radical-candor] + routes_to_templates: [team-health-check, action-plan] + + # ────────────────────────────────────────────── + # 10. Leadership Crisis Diagnosis + # ────────────────────────────────────────────── + - diagnostic: leadership-crisis-diagnosis + marketplace_reframe: > + Marketplace leadership crises are often triggered by founders + who understand one side deeply but are blind to the other. + A founder from a supply-side background builds great tools for + sellers but neglects demand experience. A demand-obsessed founder + builds beautiful buyer UX but treats supply as commodity input. + The leadership gap is always on the side the founder does not + naturally understand. + + additional_triage_questions: + - question: "Does the founding team have deep expertise on both sides of the marketplace?" + both_sides: "Balanced founding expertise — leadership crisis likely stems from other causes." + supply_only: "Leadership gap on demand side — demand strategy, marketing, and buyer experience may suffer." + demand_only: "Leadership gap on supply side — supply operations, supplier economics, and supply retention may suffer." + - question: "Has the leadership team spent significant time with both supply and demand participants?" + yes: "Understanding exists — crisis is execution, not empathy." + no: "Empathy gap on one side — the leadership team is making decisions about a constituency they do not understand." + + marketplace_diagnoses: + - name: single-side-blindness + description: "Leadership understands and empathises with one side but treats the other as a resource to be managed rather than a customer to be served." + signals: ["Investment disproportionately favours one side", "NPS diverging between sides", "One side's churn rising while the other is stable"] + routes_to_skills: [emotional-intelligence, johari-window, strategic-thinking-and-alignment] + routes_to_templates: [leadership-reflection, team-health-check] + + # ────────────────────────────────────────────── + # 11. Hiring Diagnosis + # ────────────────────────────────────────────── + - diagnostic: hiring-diagnosis + marketplace_reframe: > + Marketplace hiring requires domain expertise that general startup + hiring does not. Supply operations, trust and safety, marketplace + economics, and category management are marketplace-specific roles + that do not exist in SaaS or traditional e-commerce. Hiring + general 'growth' or 'ops' people without marketplace experience + produces costly learning curves. + + additional_triage_questions: + - question: "Do you have dedicated leaders for supply operations, demand growth, and trust & safety?" + all_three: "Core marketplace leadership in place — hiring diagnosis is standard." + missing_one: "Critical marketplace role missing — this is the hiring priority." + none: "No marketplace-specific leadership — this is the root cause of most operational issues." + + marketplace_diagnoses: + - name: marketplace-role-gap + description: "Critical marketplace-specific roles are unfilled or filled by people without marketplace experience." + signals: ["Supply or demand metrics declining without clear owner", "T&S issues increasing without dedicated function", "Marketplace economics not tracked or optimised"] + routes_to_skills: [hackman-enabling-conditions, belbin-team-roles, delegation-and-empowerment] + routes_to_templates: [hiring-scorecard, role-description-template] + + # ────────────────────────────────────────────── + # 12. Culture Erosion Diagnosis + # ────────────────────────────────────────────── + - diagnostic: culture-erosion-diagnosis + marketplace_reframe: > + Culture in a marketplace company must encompass attitudes toward + both sides. A culture that celebrates demand growth metrics but + never discusses supply-side health produces systematic neglect + of the supply side. The cultural question: does the company treat + supply-side participants as partners or as inputs? + + additional_triage_questions: + - question: "Does internal language refer to supply-side participants as 'partners' or as resources?" + partners: "Cultural framing treats supply as a valued constituency." + resources: "Cultural framing objectifies supply — expect supply-hostile policies." + - question: "Are supply-side metrics celebrated internally with the same energy as demand-side metrics?" + equal: "Balanced cultural attention." + demand_dominant: "Demand metrics dominate internal attention — supply side will eventually suffer." + + marketplace_diagnoses: + - name: supply-side-cultural-neglect + description: "Internal culture prioritises demand-side metrics and achievements while supply-side health is treated as operational housekeeping." + signals: ["All-hands focus on demand metrics", "Supply-side team seen as cost centre", "No internal celebration of supply-side wins"] + routes_to_skills: [organisational-culture, appreciative-inquiry, radical-candor] + routes_to_templates: [culture-values-document, team-health-check] + + # ────────────────────────────────────────────── + # 13. Operational Chaos Diagnosis + # ────────────────────────────────────────────── + - diagnostic: operational-chaos-diagnosis + marketplace_reframe: > + Operational chaos in a marketplace typically originates in one + of three areas: supply onboarding (backlog, quality gaps, slow + verification), trust and safety (disputes escalating, fraud + undetected, manual review bottleneck), or payments (delayed + payouts, incorrect calculations, reconciliation failures). Each + area affects both sides through different transmission mechanisms. + + additional_triage_questions: + - question: "Where is the operational chaos most acute?" + supply_onboarding: "Supply pipeline bottlenecked — new supply cannot get active, existing supply frustrated by onboarding changes." + trust_safety: "T&S overwhelmed — disputes unresolved, fraud incidents increasing, both sides losing trust." + payments: "Payment operations failing — late payouts, incorrect commissions, supply-side financial anxiety." + matching: "Matching operations degraded — poor relevance, slow response, wrong supply shown to demand." + + marketplace_diagnoses: + - name: trust-safety-operational-failure + description: "Trust and safety operations cannot keep pace with transaction volume, producing unresolved disputes, undetected fraud, and eroding trust on both sides." + signals: ["Dispute resolution time increasing", "Fraud rate rising", "Both sides' NPS declining on trust-related questions", "T&S team overwhelmed"] + routes_to_skills: [kaizen-bpr, systems-thinking, eisenhower-matrix] + routes_to_templates: [incident-postmortem, action-plan] + - name: payment-operations-failure + description: "Payment operations are failing — late payouts, incorrect calculations, or reconciliation errors producing supply-side distrust." + signals: ["Supply support tickets about payments rising", "Late payout frequency increasing", "Supply NPS declining sharply"] + routes_to_skills: [kaizen-bpr, balanced-scorecard, systems-thinking] + routes_to_templates: [action-plan, incident-postmortem] + + # ────────────────────────────────────────────── + # 14. Decision Paralysis Diagnosis + # ────────────────────────────────────────────── + - diagnostic: decision-paralysis-diagnosis + marketplace_reframe: > + Decision paralysis in marketplaces often arises from the inherent + tension: every major decision affects both sides, and the impact + on each side may be opposite. Raising take rate helps the platform + but hurts supply. Tightening quality standards helps demand but + reduces supply. The paralysis comes from the inability to make + a decision that benefits one side without harming the other. + + additional_triage_questions: + - question: "Is the paralysis caused by cross-side trade-offs?" + yes: "The decision affects supply and demand differently, and the team cannot choose which side to favour." + no: "Standard decision paralysis — the marketplace context is incidental." + + marketplace_diagnoses: + - name: cross-side-trade-off-paralysis + description: "Leadership cannot make decisions that involve trade-offs between supply and demand interests, resulting in policy stagnation." + signals: ["Major policy decisions deferred repeatedly", "Take rate unchanged despite data supporting adjustment", "Quality standards not enforced despite quality data"] + routes_to_skills: [decision-making-under-pressure, evaluating-and-deciding, win-win-negotiation] + routes_to_templates: [decision-journal, decision-rationale-memo] + + # ────────────────────────────────────────────── + # 15. Market Entry Diagnosis + # ────────────────────────────────────────────── + - diagnostic: market-entry-diagnosis + marketplace_reframe: > + Market entry for a marketplace means solving the chicken-and-egg + problem in a new context — new geography, new category, or new + vertical. Each entry requires re-establishing liquidity from + scratch, often against an incumbent that already has it. The + entry strategy must specify which side to acquire first, how + to create initial liquidity, and what the tipping point looks + like for the new market. + + additional_triage_questions: + - question: "Which side will you acquire first in the new market?" + supply_first: "Recruit supply, then attract demand with selection. Works when supply is the scarce side." + demand_first: "Aggregate demand, then attract supply with guaranteed volume. Works when demand is the scarce side." + simultaneously: "Acquire both sides simultaneously — requires heavy subsidisation or a 'single-player mode' that provides value before the other side arrives." + - question: "Does the new market have an existing incumbent?" + yes_strong: "Strong incumbent with liquidity — entry requires a differentiated wedge strategy (better supply curation, different category, superior trust)." + yes_weak: "Weak incumbent — opportunity to out-execute on liquidity, quality, or economics." + no: "No incumbent — classic chicken-and-egg challenge without competitive pressure." + + marketplace_diagnoses: + - name: cold-start-failure + description: "Market entry failing because the chicken-and-egg problem was not solved — neither side sees enough of the other to stay." + signals: ["New market supply liquidity <10%", "Demand fill rate <20%", "Both sides churning within 30 days", "Time-to-first-transaction >30 days"] + routes_to_skills: [tipping-point, game-theory-fundamentals, first-mover-strategy] + routes_to_templates: [new-initiative-brief, market-opportunity-summary] + + # ────────────────────────────────────────────── + # 16. Partnership Diagnosis + # ────────────────────────────────────────────── + - diagnostic: partnership-diagnosis + marketplace_reframe: > + Marketplace partnerships carry unique risks: supply-side + partnerships (aggregators, agencies) can concentrate supply + power. Demand-side partnerships (channels, affiliates) can + cannibalise organic growth. Infrastructure partnerships + (payments, logistics) can become bottlenecks or cost centres + that erode unit economics. Every partnership must be evaluated + for its side-specific impact. + + additional_triage_questions: + - question: "Which side of the marketplace does this partnership affect?" + supply_side: "Supply partnership — evaluate for supply concentration risk and economic impact." + demand_side: "Demand partnership — evaluate for organic cannibalisation and margin impact." + infrastructure: "Infrastructure partnership — evaluate for cost and switching-cost lock-in." + + marketplace_diagnoses: + - name: supply-concentration-risk + description: "A supply-side partner (aggregator, agency, fleet operator) controls a disproportionate share of marketplace supply, creating dependence." + signals: ["Single partner >20% of GMV", "Partner negotiating lower take rates using supply leverage", "Platform cannot enforce quality standards on partner supply"] + routes_to_skills: [porters-five-forces, coalition-and-partnership-games, scenario-planning] + routes_to_templates: [partnership-memo, risk-assessment-brief] + + # ────────────────────────────────────────────── + # 17. Co-founder Conflict Diagnosis + # ────────────────────────────────────────────── + - diagnostic: cofounder-conflict-diagnosis + marketplace_reframe: > + Co-founder conflict in marketplaces frequently crystallises + around which side to prioritise. One co-founder champions supply + (often the one with supply-side domain expertise), the other + champions demand (often with marketing or product background). + The conflict is structural, not personal — the marketplace + requires balanced attention, and co-founders naturally advocate + for their domain. + + additional_triage_questions: + - question: "Is the co-founder conflict about supply vs demand priorities?" + yes: "Structural marketplace tension — requires governance resolution, not relationship counselling." + no: "Standard co-founder conflict — marketplace context is incidental." + + marketplace_diagnoses: + - name: supply-demand-founder-split + description: "Co-founders are in conflict because each champions a different side of the marketplace, and no governance mechanism arbitrates." + signals: ["Conflicting strategic priorities at board level", "Investment oscillating between sides quarterly", "Team receiving contradictory direction from co-founders"] + routes_to_skills: [thomas-kilmann-conflict, win-win-negotiation, hackman-enabling-conditions] + routes_to_templates: [decision-rationale-memo, team-health-check] + + # ────────────────────────────────────────────── + # 18. Communication Breakdown Diagnosis + # ────────────────────────────────────────────── + - diagnostic: communication-breakdown-diagnosis + marketplace_reframe: > + Communication in a marketplace company must serve three audiences: + the internal team, the supply-side community, and the demand-side + user base. Communication breakdowns often occur in supply-side + communication — policy changes announced without context, take + rate increases without rationale, algorithm changes without + explanation. Supply-side communication failures produce immediate + backlash. + + additional_triage_questions: + - question: "Is the communication breakdown internal, supply-facing, or demand-facing?" + internal: "Internal communication failure — standard diagnosis applies." + supply_facing: "Supply-side communication failure — policy changes, earnings changes, or platform updates poorly communicated." + demand_facing: "Demand-side communication failure — trust incidents, pricing changes, or experience changes poorly communicated." + + marketplace_diagnoses: + - name: supply-communication-failure + description: "Supply-side participants feel blindsided by platform changes, unheard in their concerns, or unable to access information about their performance and earnings." + signals: ["Supply support tickets spiking after policy changes", "Negative social media from supply-side community", "Supply churn correlated with communication events"] + routes_to_skills: [kotter-change-model, radical-candor, storytelling-for-leaders] + routes_to_templates: [action-plan, culture-values-document] + + # ────────────────────────────────────────────── + # 19. Negotiation Stuck Diagnosis + # ────────────────────────────────────────────── + - diagnostic: negotiation-stuck-diagnosis + marketplace_reframe: > + Stuck negotiations in marketplace contexts most commonly involve: + take rate negotiations with supply aggregators or power sellers, + partnership terms with demand channels, or regulatory negotiations + around labour classification and marketplace liability. The + trilateral nature of marketplace economics (supply-platform-demand) + means every negotiation has a third affected party. + + additional_triage_questions: + - question: "Who is the negotiation counterparty?" + power_supply: "High-volume supplier or supply aggregator negotiating take rate or terms." + demand_channel: "Demand channel partner negotiating revenue share or exclusivity." + regulator: "Regulatory body negotiating compliance requirements." + - question: "What is the cross-side impact of the negotiation outcome?" + significant: "The deal terms directly affect the other side's economics or experience." + minimal: "The deal terms are contained to one side with limited cross-side impact." + + marketplace_diagnoses: + - name: supply-aggregator-leverage + description: "A supply aggregator or power seller has accumulated enough marketplace share to negotiate from a position of strength, demanding lower take rates or better terms." + signals: ["Single counterparty >15% of GMV", "Counterparty threatening to leave or multi-home", "Other supply watching the negotiation outcome"] + routes_to_skills: [negotiation-game-theory, competitive-negotiation, coalition-and-partnership-games] + routes_to_templates: [negotiation-prep-sheet, decision-rationale-memo] + + # ────────────────────────────────────────────── + # 20. Strategic Drift Diagnosis + # ────────────────────────────────────────────── + - diagnostic: strategic-drift-diagnosis + marketplace_reframe: > + Strategic drift in marketplaces manifests as the platform trying + to be everything to everyone on both sides — expanding into + adjacent categories without achieving liquidity in core ones, + accepting any supply to inflate listings, or chasing demand + segments that do not match the supply base. The marketplace + loses its identity and its matching quality degrades. + + additional_triage_questions: + - question: "Has the marketplace expanded beyond its core supply-demand match?" + yes: "Expansion has diluted matching quality — the marketplace serves many segments poorly instead of one well." + no: "Strategic drift is happening in other dimensions (pricing, positioning, brand)." + - question: "Can you describe your ideal supply participant and your ideal demand participant in one sentence each?" + clear: "Clear identity — drift may be operational, not strategic." + vague: "Identity unclear — the marketplace has drifted from its thesis." + + marketplace_diagnoses: + - name: liquidity-dilution + description: "The marketplace has expanded into too many categories or geographies without achieving liquidity in any, producing a broad but shallow platform that fails both sides." + signals: ["Supply liquidity <20% in most segments", "Demand fill rate declining despite growing supply", "No segment with strong repeat rates on both sides"] + routes_to_skills: [blue-ocean-strategy, porters-five-forces, growth-share-matrix] + routes_to_templates: [strategic-analysis-one-pager, quarterly-strategic-review] + + +# ============================================================ +# MARKETPLACE-SPECIFIC DIAGNOSTICS (5) +# ============================================================ + +marketplace_diagnostics: + + # ────────────────────────────────────────────── + # M1. Chicken-and-Egg Failure + # ────────────────────────────────────────────── + - name: chicken-and-egg-failure-diagnosis + description: > + Diagnoses why a marketplace cannot achieve initial liquidity — + the foundational chicken-and-egg problem that kills more + marketplaces than any other single cause. Supply will not come + without demand. Demand will not come without supply. The + diagnosis identifies which side is the true bottleneck and which + cold-start strategy is failing. + entry_symptoms: + - "We have supply but no buyers" + - "We have demand but no sellers" + - "Neither side is growing" + - "We launched but no one is transacting" + - "Our marketplace feels empty" + possible_diagnoses: + - supply-bottleneck + - demand-bottleneck + - value-prop-failure-both-sides + - wrong-initial-market + - premature-scaling + + triage_questions: + - question: "Which side did you launch first, and why?" + supply_first_intentional: "Deliberate supply-first strategy — check if demand acquisition is the bottleneck." + demand_first_intentional: "Deliberate demand-first strategy — check if supply recruitment is the bottleneck." + both_simultaneously: "Launched both simultaneously — likely spreading resources too thin. Neither side reached critical mass." + no_strategy: "No deliberate sequencing — fundamental strategic gap." + - question: "In your most active segment (geography, category, use case), what is the supply liquidity?" + above_30: "Supply liquidity >30% — the chicken-and-egg problem may be solved in this niche. Focus on demand." + ten_to_thirty: "Supply liquidity 10-30% — demand exists but supply cannot fulfil it adequately." + below_ten: "Supply liquidity <10% — demand is not finding what it needs. The marketplace appears empty." + - question: "What is the time-to-first-transaction for new users on each side?" + fast_both: "Both sides transact quickly — the problem is not cold start but volume." + fast_supply_slow_demand: "Supply activates but demand takes too long — demand cannot find relevant supply." + fast_demand_slow_supply: "Demand searches immediately but supply takes weeks to list — supply onboarding friction." + slow_both: ">30 days for both sides — the marketplace is not delivering its core promise to either." + - question: "Do you have a 'single-player mode' — a reason for one side to use the platform even without the other?" + yes_supply: "Supply gets value (tools, analytics, presence) before demand arrives — strong cold-start strategy." + yes_demand: "Demand gets value (content, information, comparison) before supply transacts — strong cold-start strategy." + no: "Neither side gets value without the other — pure chicken-and-egg dependency." + - question: "How large is your initial target market?" + narrow: "Narrow, specific geography or category — correct approach for achieving initial liquidity." + moderate: "Mid-size market — may be achievable if resources are concentrated." + broad: "Broad market from launch — almost certainly spreading too thin to achieve liquidity anywhere." + + diagnosis_map: + supply-bottleneck: + description: "The marketplace has demand signals but cannot recruit or retain sufficient supply to create a viable marketplace experience." + red_flags: ["Supply onboarding >50% drop-off", "Supply churning within 30 days", "Supply CAC unacceptable"] + routes_to_skills: [cialdini-influence, four-ps-marketing, first-mover-strategy] + routes_to_templates: [action-plan, new-initiative-brief] + demand-bottleneck: + description: "The marketplace has supply but cannot attract demand or convert demand-side visitors to transacting buyers." + red_flags: ["Demand conversion <5%", "Demand bounce rate >70%", "Demand repeat rate near zero"] + routes_to_skills: [four-ps-marketing, tipping-point, cialdini-influence] + routes_to_templates: [action-plan, market-opportunity-summary] + value-prop-failure-both-sides: + description: "Neither supply nor demand finds the marketplace compelling. The value proposition is unclear, unproven, or nonexistent for both sides." + red_flags: ["Neither side returning after first visit", "Both sides describing the platform differently from the intended positioning", "No organic growth on either side"] + routes_to_skills: [business-model-canvas, blue-ocean-strategy, net-promoter-score] + routes_to_templates: [strategic-analysis-one-pager, decision-journal] + wrong-initial-market: + description: "The marketplace may have a viable thesis, but the initial geography, category, or use case was wrong — too broad, too competitive, or insufficient latent demand." + red_flags: ["Adequate supply and demand in absolute terms but no matching in any specific segment", "Multiple segments attempted, none achieving liquidity"] + routes_to_skills: [tipping-point, scenario-planning, blue-ocean-strategy] + routes_to_templates: [market-opportunity-summary, decision-journal] + premature-scaling: + description: "The marketplace expanded to new markets or categories before achieving liquidity in the first, diluting resources and producing no liquidity anywhere." + red_flags: ["Present in 5+ markets with <20% liquidity in all", "GMV spread thin across many segments", "No segment showing network effects"] + routes_to_skills: [growth-share-matrix, smart-goals, systems-thinking] + routes_to_templates: [strategic-analysis-one-pager, action-plan] + + # ────────────────────────────────────────────── + # M2. Liquidity Crisis + # ────────────────────────────────────────────── + - name: liquidity-crisis-diagnosis + description: > + Diagnoses an acute liquidity failure in an established marketplace — + not the initial chicken-and-egg problem, but a liquidity breakdown + after the marketplace had been functioning. Something broke the + flywheel: supply exodus, demand shock, quality collapse, or + competitive displacement. + entry_symptoms: + - "Transactions are dropping even though both sides are still on the platform" + - "Supply is sitting idle" + - "Buyers can't find what they need" + - "Our marketplace stopped matching" + - "Fill rate collapsed" + possible_diagnoses: + - supply-side-liquidity-collapse + - demand-side-liquidity-collapse + - matching-mechanism-failure + - segment-specific-liquidity-loss + - competitive-liquidity-drain + + triage_questions: + - question: "Is the liquidity crisis marketplace-wide or segment-specific?" + marketplace_wide: "System-level failure — proceed to Q2 for root cause." + segment_specific: "Localised failure — identify the segment and check for competitive entry or supply/demand shift in that segment." + - question: "Which metric moved first: supply liquidity or demand fill rate?" + supply_first: "Supply liquidity dropped first — supply-side shock (churn, multi-homing, disintermediation)." + demand_first: "Demand fill rate dropped first — demand-side shift (competitor, substitute, quality concern)." + simultaneous: "Both dropped together — external shock (market contraction, regulatory change) or matching mechanism failure." + - question: "Did the liquidity crisis follow a specific event?" + take_rate_change: "Liquidity dropped after take rate adjustment — supply-side price shock." + policy_change: "Liquidity dropped after policy change — supply or demand rejecting new terms." + competitive_entry: "Liquidity dropped after competitor launched or expanded — competitive displacement." + quality_incident: "Liquidity dropped after a publicised quality or safety incident — trust shock." + no_event: "Gradual decline without precipitating event — structural erosion." + + diagnosis_map: + supply-side-liquidity-collapse: + description: "Supply has reduced activity, delisted, or left the platform, reducing available inventory below the level needed for healthy demand matching." + red_flags: ["Supply liquidity dropped >20pp in one period", "Active supply declining while registered supply stable (silent churn)", "Top-tier supply leaving disproportionately"] + routes_to_skills: [systems-thinking, art-of-war, kotter-change-model] + routes_to_templates: [risk-assessment-brief, action-plan] + demand-side-liquidity-collapse: + description: "Demand is present but not converting — searches happen but transactions do not. Demand may be losing trust, finding alternatives, or experiencing poor matching." + red_flags: ["Search-to-transaction rate dropped >30%", "Demand bounce rate spiking", "Demand repeat rate declining sharply"] + routes_to_skills: [net-promoter-score, four-ps-marketing, kaizen-bpr] + routes_to_templates: [action-plan, quarterly-strategic-review] + matching-mechanism-failure: + description: "Both supply and demand are present, but the matching mechanism is producing poor matches — wrong supply shown to wrong demand, poor relevance, poor timing." + red_flags: ["Transaction rate declining while both sides' activity stable", "Search relevance scores dropping", "Increased demand-side 'no results' queries"] + routes_to_skills: [kaizen-bpr, systems-thinking, doblin-ten-types] + routes_to_templates: [incident-postmortem, action-plan] + segment-specific-liquidity-loss: + description: "Liquidity has collapsed in specific segments (geography, category, price tier) while remaining healthy elsewhere." + red_flags: ["Segment-level liquidity <10% where it was previously >30%", "All decline concentrated in 1-3 segments", "Competitor launched specifically in those segments"] + routes_to_skills: [growth-share-matrix, porters-five-forces, scenario-planning] + routes_to_templates: [strategic-analysis-one-pager, action-plan] + competitive-liquidity-drain: + description: "A competitor is siphoning supply, demand, or both — drawing liquidity away from the marketplace through better economics, experience, or specialisation." + red_flags: ["Multi-homing rate increasing on one or both sides", "Best supply/demand migrating to competitor", "Organic acquisition declining while competitor grows"] + routes_to_skills: [art-of-war, porters-five-forces, first-mover-strategy] + routes_to_templates: [competitive-landscape-brief, action-plan] + + # ────────────────────────────────────────────── + # M3. Disintermediation Risk + # ────────────────────────────────────────────── + - name: disintermediation-risk-diagnosis + description: > + Diagnoses the severity and trajectory of disintermediation — + supply and demand transacting off-platform after the marketplace + introduced them. This is the existential threat for any + marketplace whose primary value is matching rather than ongoing + transaction management. If parties can connect once through the + marketplace and then bypass it forever, the platform is a + lead-gen tool, not a marketplace. + entry_symptoms: + - "Customers and sellers are going off-platform" + - "Our repeat transaction rate is suspiciously low" + - "Sellers share contact info with buyers" + - "Revenue per matched pair declining over time" + - "We suspect people are avoiding our fees" + possible_diagnoses: + - structural-disintermediation + - incentive-disintermediation + - trust-maturity-disintermediation + - competitive-disintermediation + + triage_questions: + - question: "What type of transaction does your marketplace facilitate?" + one_time: "One-time purchases (product marketplaces) — disintermediation risk is low per transaction but high for repeat purchases of the same type." + recurring: "Recurring services (cleaning, tutoring, therapy) — highest disintermediation risk. Relationship forms after first match." + on_demand: "On-demand (ride-sharing, food delivery) — low disintermediation risk if platform controls dispatch and payment." + project_based: "Project-based (freelance, home services) — moderate risk. Increases with project size and relationship duration." + - question: "What value does your platform provide AFTER the initial match?" + payment_processing: "Payment processing only — weak retention force. Supply and demand can use Venmo." + trust_and_payment: "Trust (reviews, guarantees, insurance) + payment — moderate retention. Both sides lose protection off-platform." + managed_transaction: "End-to-end managed transaction (logistics, support, dispute resolution) — strong retention. Off-platform is significantly worse." + match_only: "Match only — near-zero post-match value. Disintermediation is structurally inevitable." + - question: "Do you see signals of off-platform communication before or after first transaction?" + before: "Parties attempting to communicate off-platform before transacting — actively avoiding fees from the start." + after_first: "First transaction on-platform, subsequent transactions off-platform — relationship-driven disintermediation." + no_signals: "No visible signals — either disintermediation is low or detection is inadequate." + + diagnosis_map: + structural-disintermediation: + description: "The marketplace's transaction type inherently encourages off-platform relationships. Once matched, the ongoing value of the platform is insufficient to justify the take rate." + red_flags: ["Revenue per matched pair declines dramatically after transaction 1-2", "Category is relationship-based (services, B2B)", "Take rate >15% on a match-only platform"] + routes_to_skills: [business-model-canvas, doblin-ten-types, game-theory-fundamentals] + routes_to_templates: [strategic-analysis-one-pager, decision-journal] + severity: critical + recommended_action: "Fundamentally redesign the value proposition to include per-transaction value: payments, insurance, quality tracking, or managed delivery." + incentive-disintermediation: + description: "The take rate or fee structure incentivises off-platform transactions. The cost of transacting on-platform exceeds the perceived value of platform services." + red_flags: ["High take rate (>20%) combined with simple transaction type", "No platform-specific services that require on-platform payment", "Supply openly advising demand to transact directly"] + routes_to_skills: [four-ps-marketing, game-theory-fundamentals, information-asymmetry] + routes_to_templates: [unit-economics-snapshot, decision-journal] + severity: high + recommended_action: "Reduce take rate or restructure fees to align cost with per-transaction value delivered. Add value-added services that only work on-platform." + trust-maturity-disintermediation: + description: "Disintermediation increases as trust between supply and demand matures — parties no longer need the platform's trust infrastructure after repeated positive transactions." + red_flags: ["Disintermediation concentrated among long-term users", "Repeat transaction rate declining for mature cohorts", "High satisfaction scores but declining on-platform revenue per user"] + routes_to_skills: [trust-equation, product-life-cycle, cialdini-influence] + routes_to_templates: [strategic-analysis-one-pager, decision-journal] + severity: moderate + recommended_action: "Introduce ongoing value — loyalty programs, cumulative benefits, financing, data insights — that compounds with on-platform tenure." + competitive-disintermediation: + description: "A competing platform or tool is enabling off-platform transactions by providing the components (payment, communication, scheduling) that your platform bundles." + red_flags: ["Paired users migrating to a competitor or to general-purpose tools (WhatsApp, Venmo, Calendly)", "New tools specifically targeting your supply-demand pair"] + routes_to_skills: [porters-five-forces, art-of-war, doblin-ten-types] + routes_to_templates: [competitive-landscape-brief, action-plan] + severity: high + recommended_action: "Bundle value that general-purpose tools cannot replicate: marketplace-specific insurance, quality guarantees, dispute resolution, and transaction data." + + # ────────────────────────────────────────────── + # M4. Quality Degradation + # ────────────────────────────────────────────── + - name: quality-degradation-diagnosis + description: > + Diagnoses declining marketplace quality — the erosion of supply- + side standards that degrades the demand experience and ultimately + threatens marketplace viability. Quality degradation is the most + insidious marketplace failure because it happens gradually: each + marginal reduction in quality is too small to trigger alarm, but + the cumulative effect is devastating. Sarah Tavel identifies + quality as the third and most defensible level of the marketplace + hierarchy — and the hardest to maintain at scale. + entry_symptoms: + - "Ratings are declining" + - "Customer complaints are increasing" + - "Our best suppliers are leaving" + - "Dispute rate is rising" + - "The marketplace feels lower quality than it used to" + possible_diagnoses: + - adverse-selection-spiral + - quality-standard-erosion + - curation-failure + - growth-quality-trade-off + - supply-tier-degradation + + triage_questions: + - question: "Has the average quality score of new supply been declining?" + yes: "New supply entering the marketplace is lower quality — onboarding standards may be too low." + no: "New supply quality stable — the problem is existing supply degrading." + unknown: "No quality scoring for new supply — this gap is itself a problem." + - question: "Are your best suppliers (top 20% by ratings) leaving or reducing activity?" + leaving: "Top supply is churning — adverse selection in progress. Low-quality supply drives out high-quality supply." + reducing: "Top supply is reducing activity — they may be multi-homing to platforms with better demand quality." + stable: "Top supply stable — the quality problem is in the long tail." + - question: "Did quality degradation follow a growth initiative?" + yes: "Growth and quality traded off — supply onboarding was loosened to hit volume targets." + no: "Quality degradation is organic — gradual erosion of standards or enforcement." + - question: "What is the dispute rate trend?" + rising: "Disputes rising — quality problems are reaching demand and causing measurable harm." + stable: "Disputes stable — quality degradation may be perceived but not yet impacting transactions." + not_tracked: "Dispute rate not systematically tracked — build this immediately." + + diagnosis_map: + adverse-selection-spiral: + description: "High-quality supply is leaving because the marketplace's average quality is declining, which attracts lower-quality supply, which further reduces average quality. The classic Akerlof lemon market problem." + red_flags: ["Top-tier supply churn >2x average supply churn", "Average rating declining while review volume increases", "Demand repeat rate declining for quality-sensitive segments"] + routes_to_skills: [information-asymmetry, systems-thinking, porters-five-forces] + routes_to_templates: [risk-assessment-brief, action-plan] + severity: critical + recommended_action: "Immediately invest in quality differentiation: premium tiers, verification levels, quality guarantees. Make it visibly better to be a high-quality supplier on the platform." + quality-standard-erosion: + description: "Quality standards that existed at launch have been quietly eroded — enforcement reduced, thresholds lowered, exceptions multiplied — producing a slow decline in average quality." + red_flags: ["Quality enforcement rate declining", "Exception grants increasing", "Original quality standards documented but no longer enforced"] + routes_to_skills: [organisational-culture, kaizen-bpr, balanced-scorecard] + routes_to_templates: [action-plan, culture-values-document] + severity: high + recommended_action: "Re-establish and enforce quality standards. Grandfather existing supply with a clear timeline for compliance. New supply must meet original or higher standards." + curation-failure: + description: "The marketplace's curation mechanism (search ranking, recommendation, featured placement) is not effectively surfacing quality supply, making quality invisible to demand." + red_flags: ["High-quality supply exists but has low visibility", "Search results not correlated with quality scores", "Demand complaining about quality despite quality supply being available"] + routes_to_skills: [kaizen-bpr, doblin-ten-types, systems-thinking] + routes_to_templates: [action-plan, new-initiative-brief] + severity: moderate + recommended_action: "Rebuild curation to weight quality signals (ratings, completion rate, response time) heavily in ranking and recommendation algorithms." + growth-quality-trade-off: + description: "Quality degraded as a direct result of growth initiatives — supply onboarding was loosened, quality enforcement was paused, or growth targets were prioritised over quality metrics." + red_flags: ["Quality decline correlated with supply growth spurt", "Onboarding requirements recently reduced", "Growth team rewarded on volume, not quality"] + routes_to_skills: [balanced-scorecard, smart-goals, systems-thinking] + routes_to_templates: [action-plan, team-health-check] + severity: high + recommended_action: "Add quality constraints to growth targets. No supply growth metric should be celebrated without a corresponding quality metric. Restructure incentives." + supply-tier-degradation: + description: "The quality problem is concentrated in a specific tier or category of supply, not marketplace-wide." + red_flags: ["Quality metrics diverging by supply tier", "Specific category's ratings declining while others stable", "Demand churn concentrated in the degraded category"] + routes_to_skills: [growth-share-matrix, balanced-scorecard, kaizen-bpr] + routes_to_templates: [action-plan, quarterly-strategic-review] + severity: moderate + recommended_action: "Isolate the degraded tier or category. Apply targeted quality interventions without disrupting healthy segments." + + # ────────────────────────────────────────────── + # M5. Trust Collapse + # ────────────────────────────────────────────── + - name: trust-collapse-diagnosis + description: > + Diagnoses an acute or gradual loss of trust in the marketplace + by one or both sides. Trust collapse is distinct from quality + degradation — quality degradation erodes trust gradually, but + trust collapse can happen suddenly through a safety incident, + fraud exposure, data breach, or perceived policy unfairness. + Trust collapse is the marketplace equivalent of a bank run: once + one side loses confidence, the other follows. + entry_symptoms: + - "Suppliers don't trust us anymore" + - "Buyers are afraid to transact" + - "A safety incident went viral" + - "We had a fraud wave" + - "People think we're unfair" + - "Both sides are leaving after a policy change" + possible_diagnoses: + - safety-incident-trust-shock + - fraud-wave-trust-erosion + - policy-fairness-trust-break + - data-breach-trust-collapse + - algorithmic-trust-erosion + + triage_questions: + - question: "Was the trust loss triggered by a specific incident or is it gradual?" + specific_incident: "Acute trust shock — identify the incident and assess whether it is contained or systemic." + gradual: "Gradual trust erosion — cumulative effect of many small failures. Harder to reverse." + - question: "Which side lost trust first?" + supply: "Supply lost trust — check for: unfair policy, inconsistent enforcement, payment issues, algorithmic opacity." + demand: "Demand lost trust — check for: safety incident, fraud, quality failure, inadequate dispute resolution." + both: "Both sides simultaneously — likely a publicised incident or a systemic platform failure." + - question: "Has the trust loss been public (media coverage, social media) or private (support tickets, churn data)?" + public: "Public trust crisis — requires immediate, visible, transparent response. Media management becomes critical." + private: "Private trust erosion — detectable in data but not yet public. Window to address before it escalates." + - question: "Does the marketplace have visible trust infrastructure (guarantees, insurance, verification)?" + strong: "Trust infrastructure exists — the failure may be in execution, not design." + weak: "Inadequate trust infrastructure — the marketplace was relying on good behaviour rather than structural trust." + none: "No formal trust infrastructure — trust was assumed, not engineered." + + diagnosis_map: + safety-incident-trust-shock: + description: "A safety incident (physical harm, significant financial loss, criminal activity) on the marketplace has shattered user confidence." + red_flags: ["Media coverage of the incident", "Both sides' new sign-ups dropping immediately", "Existing users requesting account deletion", "Regulatory inquiry"] + routes_to_skills: [scenario-planning, kotter-change-model, vuca-framework] + routes_to_templates: [risk-assessment-brief, action-plan, incident-postmortem] + severity: critical + recommended_action: "Immediate transparent response. Accept responsibility where warranted. Announce concrete safety improvements with timeline. Consider pause-and-fix if incidents are ongoing." + fraud-wave-trust-erosion: + description: "A pattern of fraud (fake listings, payment fraud, identity fraud, review manipulation) has eroded confidence in the marketplace's integrity." + red_flags: ["Fraud rate spiking", "Support tickets about suspected fraud increasing", "Demand-side 'is this real?' inquiries increasing", "Review authenticity questioned"] + routes_to_skills: [systems-thinking, kaizen-bpr, information-asymmetry] + routes_to_templates: [action-plan, incident-postmortem] + severity: high + recommended_action: "Invest immediately in fraud detection and prevention. Remove fraudulent listings/accounts visibly. Communicate improvements to both sides." + policy-fairness-trust-break: + description: "A policy change (take rate increase, new terms, enforcement action) is perceived as unfair by one or both sides, breaking the social contract between platform and participants." + red_flags: ["Supply or demand protest (public letters, social media campaigns, strikes)", "Churn spike correlated with policy announcement", "Policy perceived as benefiting platform at participants' expense"] + routes_to_skills: [kotter-change-model, win-win-negotiation, radical-candor] + routes_to_templates: [action-plan, decision-rationale-memo] + severity: high + recommended_action: "Acknowledge the concern publicly. Provide clear rationale for the policy. Consider revision based on feedback. Rebuild through transparency and demonstrated fairness." + data-breach-trust-collapse: + description: "A data breach or privacy violation has compromised user data, producing immediate trust collapse on both sides." + red_flags: ["User data exposed", "Regulatory notification required", "Both sides' activity dropping immediately", "Account deletion requests spiking"] + routes_to_skills: [vuca-framework, scenario-planning, kotter-change-model] + routes_to_templates: [incident-postmortem, risk-assessment-brief, action-plan] + severity: critical + recommended_action: "Follow breach response protocol. Full transparency on scope and remediation. Invest in security infrastructure and communicate improvements." + algorithmic-trust-erosion: + description: "Supply-side trust eroded by perceived algorithmic unfairness — opaque ranking changes, unexplained visibility shifts, or suspected bias in matching." + red_flags: ["Supply forums discussing 'algorithm changes'", "Supply NPS declining on 'fairness' dimension", "Top supply requesting algorithm transparency", "Supply churn correlated with ranking changes"] + routes_to_skills: [information-asymmetry, trust-equation, radical-candor] + routes_to_templates: [action-plan, culture-values-document] + severity: moderate + recommended_action: "Increase algorithmic transparency. Publish ranking factors. Provide supply with performance data that explains their positioning. Create feedback channels for algorithmic concerns." diff --git a/plugins/foreman/content/industry-packs/marketplace/marketplace-skill-overlays.yaml b/plugins/foreman/content/industry-packs/marketplace/marketplace-skill-overlays.yaml new file mode 100644 index 0000000..f269306 --- /dev/null +++ b/plugins/foreman/content/industry-packs/marketplace/marketplace-skill-overlays.yaml @@ -0,0 +1,1190 @@ +# Marketplace Industry Pack — Skill Overlays +# Provides marketplace-specific overlays for 35 skills, reframing each +# through the two-sided lens: supply, demand, platform dynamics, network +# effects, liquidity, take rates, and disintermediation risk. +# +# Each overlay does not replace the base skill — it augments it with +# marketplace-native thinking. The two-sided nature must be visible in +# every overlay. These are not SaaS frameworks with "marketplace" pasted +# over "subscription." + +pack: marketplace +author: "Fatih Guner" +type: skill_overlays +version: "1.0.0" + +overlays: + + # ────────────────────────────────────────────── + # 1. Porter's Five Forces + # ────────────────────────────────────────────── + - skill: porters-five-forces + marketplace_reframe: > + In a single-sided business, Porter's Five Forces produces one + analysis. In a marketplace, it produces three: the five forces + acting on the supply side, the five forces acting on the demand + side, and the platform-specific forces that exist only in + two-sided markets. The standard framework misses the most + dangerous competitive dynamics marketplaces face. + + two_sided_application: + supply_side: + - "Threat of new entrants: Can a new marketplace recruit your supply? How sticky is supply? What are the switching costs for a seller moving from your platform to a competitor?" + - "Supplier power: In a marketplace context, the 'suppliers' to the platform are its supply-side participants. Concentrated supply (few dominant sellers) gives them bargaining power over take rates and terms." + - "Buyer power: The demand side's ability to demand lower prices or higher quality from supply through the platform. Multi-tenanting demand reduces their dependence on your marketplace." + - "Substitutes: Can supply serve demand through non-marketplace channels — direct sales, social media, their own website?" + - "Rivalry: How many competing marketplaces compete for the same supply base?" + demand_side: + - "Threat of new entrants: Can a new marketplace attract your buyers with better selection, lower prices, or superior experience?" + - "Supplier power: Supply-side participants' ability to set prices, limit availability, or move to competing platforms affects the demand experience." + - "Buyer power: Demand concentration — a few large buyers — gives them leverage over marketplace terms." + - "Substitutes: Can buyers get the same products or services without using any marketplace?" + - "Rivalry: How many competing marketplaces compete for the same buyer base?" + platform_forces: + - "Multi-homing: The tendency of participants on either side to use multiple competing platforms simultaneously. High multi-homing = low defensibility." + - "Disintermediation: The risk that matched pairs bypass the platform after initial introduction, eliminating the take rate." + - "Network effects strength: The degree to which growth on one side improves the value proposition for the other. Weak network effects = commodity intermediation." + - "Regulatory capture: Platform-specific regulatory risks — labor classification, marketplace liability, data portability requirements." + - "Winner-take-most dynamics: Whether the market structure favours one dominant marketplace or supports multiple coexisting platforms." + + key_questions: + - "Are your five forces more favourable on the supply side or the demand side — and which side is your strategic bottleneck?" + - "How high is multi-homing on each side, and what would reduce it?" + - "Which competitive force is most likely to kill your marketplace: a new entrant recruiting supply, demand-side substitutes, or disintermediation?" + + anti_patterns: + - "Running a single five-forces analysis as if the marketplace were one business with one set of customers." + - "Ignoring multi-homing as a competitive force — it is often more dangerous than direct rivalry." + - "Treating supply-side participants as 'suppliers' in the traditional Porter sense rather than as customers of the platform." + + # ────────────────────────────────────────────── + # 2. Business Model Canvas + # ────────────────────────────────────────────── + - skill: business-model-canvas + marketplace_reframe: > + A single Business Model Canvas cannot represent a marketplace. The + standard nine-block canvas assumes one customer segment and one + value proposition. A marketplace has (at minimum) two customer + segments — supply and demand — with distinct value propositions, + channels, relationships, and revenue models for each. The canvas + must be doubled, then linked through the platform's matching + mechanism. + + two_sided_application: + supply_side_canvas: + customer_segments: "Supply-side participants (sellers, hosts, drivers, freelancers). Segment by volume, quality tier, category, geography." + value_propositions: "Access to demand, reduced marketing costs, payment processing, trust infrastructure, analytics and tools. What does the supply side get that they cannot get alone?" + channels: "How supply discovers and joins the marketplace — outbound sales, organic search, word-of-mouth, category-specific communities." + customer_relationships: "Account management for top supply, self-serve for long tail, automated quality monitoring, performance dashboards." + revenue_streams: "Commission on transactions, listing fees, premium placement, SaaS tools, advertising, data services." + demand_side_canvas: + customer_segments: "Buyers, guests, riders, clients. Segment by purchase frequency, AOV, category preference, geography." + value_propositions: "Selection, convenience, trust (reviews, guarantees), price transparency, discovery. What does the demand side get that direct-from-source cannot provide?" + channels: "How demand finds the marketplace — SEO, paid acquisition, app stores, brand awareness, referral programs." + customer_relationships: "Personalised recommendations, loyalty programs, customer support, dispute resolution." + revenue_streams: "Transaction fees (often invisible to demand), subscription tiers, delivery fees, premium buyer features." + platform_layer: + key_resources: "Matching algorithm, trust infrastructure, payment system, data and analytics, brand." + key_activities: "Supply-demand matching, quality curation, fraud prevention, dispute resolution, liquidity management." + key_partnerships: "Payment processors, logistics providers, insurance underwriters, identity verification services." + cost_structure: "Two-sided CAC (supply + demand), payment processing, T&S operations, platform infrastructure, customer support (both sides)." + + key_questions: + - "Does each side have a clear, distinct value proposition — or are you assuming demand benefits automatically follow from supply?" + - "Which canvas is weaker? That is your strategic bottleneck." + - "How does the platform layer create value that neither side can replicate independently?" + + anti_patterns: + - "Creating one canvas with 'users' as the customer segment without distinguishing supply and demand." + - "Listing 'marketplace fees' as the only revenue stream without modelling take rate, ancillary services, and SaaS tools." + - "Omitting the platform layer — key activities, resources, and partnerships that make the match happen." + + # ────────────────────────────────────────────── + # 3. SWOT / PEST Analysis + # ────────────────────────────────────────────── + - skill: swot-pest-analysis + marketplace_reframe: > + SWOT and PEST analyses for marketplaces must be conducted per side + and for the platform itself. A strength on the supply side (deep + inventory) can coexist with a weakness on the demand side (low + repeat rate). External PEST factors hit each side differently: + labour regulations affect supply, consumer protection laws affect + demand, antitrust scrutiny affects the platform. + + two_sided_application: + supply_side_swot: + - "Strengths: Supply quality, exclusivity, supply-side tools, low supply CAC." + - "Weaknesses: Supply churn, low liquidity, quality inconsistency, high onboarding friction." + - "Opportunities: Untapped supply categories, supply-side SaaS upsell, geographic expansion." + - "Threats: Supply multi-homing, disintermediation, competitor supply-side incentives, regulatory reclassification of supply (e.g., gig worker laws)." + demand_side_swot: + - "Strengths: Demand-side brand strength, repeat rate, organic acquisition, selection breadth." + - "Weaknesses: Low demand fill rate, poor first-experience conversion, high demand CAC." + - "Opportunities: Adjacent demand segments, cross-category expansion, loyalty programs." + - "Threats: Demand-side multi-homing, competitor promotions, substitute channels, trust erosion." + platform_pest: + - "Political: Labour classification laws (AB5, EU Platform Work Directive), marketplace liability regulations, trade policy affecting cross-border marketplaces." + - "Economic: Consumer spending trends affecting demand AOV, supply-side income alternatives, payment processing cost trends." + - "Social: Trust in online transactions, gig economy attitudes, generational platform preferences." + - "Technological: AI matching and personalisation, payment infrastructure evolution, fraud technology, logistics automation." + + key_questions: + - "Which SWOT quadrant, for which side, poses the most existential risk right now?" + - "Do your PEST factors differentially affect one side — and how does that ripple to the other?" + + anti_patterns: + - "Running one SWOT for the whole marketplace without side-specific analysis." + - "Listing 'network effects' as a strength without evidence they actually exist in your marketplace." + + # ────────────────────────────────────────────── + # 4. Blue Ocean Strategy + # ────────────────────────────────────────────── + - skill: blue-ocean-strategy + marketplace_reframe: > + Blue ocean strategy in a marketplace context means creating + uncontested space on at least one side of the market. The most + successful marketplace blue oceans unlock supply that was + previously inaccessible (Airbnb: spare bedrooms) or serve demand + that was previously underserved (Etsy: handmade goods buyers). + The strategic canvas must be drawn twice — once for supply value + and once for demand value. + + two_sided_application: + supply_side: + - "Eliminate-Reduce-Raise-Create grid applied to the supply-side value proposition. What do existing platforms force suppliers to do that you can eliminate?" + - "Unlock latent supply: identify assets, skills, or capacity that exist but are not currently monetised through any marketplace." + - "The supply-side blue ocean often matters more than the demand side — novel supply creates its own demand." + demand_side: + - "Eliminate-Reduce-Raise-Create grid applied to the demand-side experience. What friction do existing solutions impose on buyers?" + - "Serve non-consumers: identify demand that exists but is currently priced out, geographically excluded, or too inconvenient to fulfil." + - "The demand-side blue ocean often involves dramatically reducing the minimum viable transaction (lower AOV, smaller commitments)." + platform_innovation: + - "Blue ocean matching: create a new way of connecting supply and demand that competitors cannot replicate." + - "Blue ocean trust: introduce trust mechanisms (guarantees, insurance, escrow) that make transactions possible where they previously were not." + + key_questions: + - "Are you creating a blue ocean on the supply side, the demand side, or both — and which matters more?" + - "Is the latent supply you are unlocking genuinely new, or are you competing for existing supply with a slightly different value prop?" + - "Does your blue ocean on one side automatically attract the other, or do you need separate blue ocean strategies for each?" + + anti_patterns: + - "Claiming a blue ocean exists because no one has built this specific marketplace — without verifying demand exists for this specific supply." + - "Creating a demand-side blue ocean with no path to high-quality supply." + + # ────────────────────────────────────────────── + # 5. Four Ps Marketing + # ────────────────────────────────────────────── + - skill: four-ps-marketing + marketplace_reframe: > + The Four Ps apply twice in a marketplace — once for supply + marketing and once for demand marketing — and the 'Price' P + becomes the most complex element because it is not a simple price + point but a take rate structure affecting both sides simultaneously. + Raising the price (take rate) to extract more from one side can + collapse the other. + + two_sided_application: + supply_side_4ps: + product: "The platform itself is the product for supply: listing tools, dashboard, analytics, payment processing, demand access." + price: "Supply-side cost = take rate + any listing fees + payment processing absorbed by supply. The supply-side price must be lower than the value of demand access the platform provides." + place: "Where and how supply discovers the marketplace: industry events, category-specific channels, sales outreach, referral from existing supply." + promotion: "Supply-side messaging: expected earnings, success stories, tools and support, community. Supply marketing is recruitment marketing." + demand_side_4ps: + product: "The marketplace experience for buyers: search, discovery, trust signals, checkout, delivery tracking, dispute resolution." + price: "Demand-side cost = product/service price + any buyer fees + shipping/delivery. Often demand sees no explicit platform fee — the take rate is embedded in supply pricing." + place: "Demand acquisition channels: SEO, paid search, social, app stores, partnerships, content marketing." + promotion: "Demand-side messaging: selection, trust, convenience, price transparency, guarantees." + take_rate_as_price: + - "Take rate is not a simple pricing decision — it is a cross-side optimization problem." + - "Raising supply-side take rate may cause supply attrition, which degrades demand experience." + - "Adding explicit demand-side fees may reduce conversion, which degrades supply liquidity." + - "The optimal take rate is the highest rate at which both sides still prefer the marketplace over alternatives." + + key_questions: + - "Are your marketing messages and channels differentiated between supply and demand — or are you marketing to both sides the same way?" + - "Is your take rate structured as supply-side, demand-side, or split — and what would happen if you shifted the burden?" + + anti_patterns: + - "Treating take rate as a simple pricing lever without modelling cross-side effects." + - "Using the same marketing channels and messages for both sides." + + # ────────────────────────────────────────────── + # 6. Net Promoter Score + # ────────────────────────────────────────────── + - skill: net-promoter-score + marketplace_reframe: > + NPS must be measured separately for supply and demand — and the gap + between them is as informative as either score alone. A marketplace + with NPS 60 on the demand side and NPS 10 on the supply side is + extracting value from supply to subsidise demand. That structure + is unsustainable. + + two_sided_application: + supply_side: + - "Survey: 'How likely are you to recommend [marketplace] to a fellow [seller/host/provider]?'" + - "Drivers of supply NPS: earnings reliability, demand volume, platform tools, fee transparency, dispute fairness, support quality." + - "Low supply NPS → supply churn → less selection → demand experience degrades → doom loop." + demand_side: + - "Survey: 'How likely are you to recommend [marketplace] to a friend who needs [product/service]?'" + - "Drivers of demand NPS: selection quality, price fairness, trust/safety, transaction speed, support quality." + - "Low demand NPS → demand churn → less transaction volume → supply earnings decline → supply churn." + cross_side_insight: + - "NPS gap (demand NPS - supply NPS) > 30 points: marketplace is over-extracting from supply." + - "NPS gap < -20 points: marketplace is over-investing in supply at demand's expense." + - "Track NPS per side over time. Diverging NPS curves predict marketplace instability." + + key_questions: + - "What is your NPS for each side, and which side's NPS trajectory concerns you more?" + - "Does your supply-side NPS reflect earnings satisfaction or platform experience satisfaction — and which matters more?" + + anti_patterns: + - "Measuring a single blended NPS across both sides." + - "Celebrating high demand NPS while ignoring declining supply NPS." + + # ────────────────────────────────────────────── + # 7. Disruptive Innovation + # ────────────────────────────────────────────── + - skill: disruptive-innovation + marketplace_reframe: > + Disruption in marketplaces follows a distinctive pattern: the + disruptor does not need to be better for all users — they need + to be better for the underserved tail of one side. Etsy disrupted + eBay not by being a better general marketplace but by serving + handmade sellers that eBay ignored. Uber disrupted taxis not by + being cheaper for all riders but by serving the 'cannot get a + cab' moments. + + two_sided_application: + supply_side_disruption: + - "Disruptors unlock supply that incumbents reject: too small, too niche, too unprofessional, too informal." + - "Lowering supply-side barriers to entry (no storefront required, no minimum inventory) is the classic marketplace disruption pattern." + - "Watch for platforms that make it trivially easy for amateurs to compete with your professional supply." + demand_side_disruption: + - "Disruptors serve demand that incumbents overlook: too infrequent, too low-AOV, too geographically dispersed." + - "Reducing minimum viable transaction size opens new demand segments that incumbents cannot economically serve." + - "Watch for platforms that make your product/service category accessible to consumers who previously could not afford it." + platform_disruption: + - "A new platform architecture — mobile-first, AI-matched, vertically integrated — can disrupt an incumbent's matching mechanism." + - "Trust innovation (new verification, insurance, escrow models) can disrupt incumbents' trust infrastructure." + - "Disintermediation technology (direct messaging, payment outside platform) is disruption of the platform itself." + + key_questions: + - "Which tail of your supply or demand side are you ignoring — and could a disruptor build a wedge there?" + - "Is your marketplace being disrupted from below (lower quality, lower price) or from above (better experience, vertical specialisation)?" + + anti_patterns: + - "Assuming your marketplace cannot be disrupted because you have network effects — network effects protect against direct competition, not asymmetric disruption." + - "Focusing disruption analysis on direct marketplace competitors rather than on new platform architectures." + + # ────────────────────────────────────────────── + # 8. Product Life Cycle + # ────────────────────────────────────────────── + - skill: product-life-cycle + marketplace_reframe: > + Marketplace life cycles are defined not by product maturity but by + liquidity maturity. Introduction = solving chicken-and-egg. Growth + = liquidity flywheel engaged. Maturity = liquidity saturated in + core segments. Decline = liquidity leaking to competitors or + substitutes. Each stage demands different supply-demand management. + + two_sided_application: + introduction: + - "Chicken-and-egg phase. The marketplace has no inherent value without both sides present." + - "Strategy: constrain supply, subsidise one side (usually demand), manual curation, single geography or category." + - "Metric focus: supply liquidity and time-to-first-transaction, not GMV." + growth: + - "Liquidity flywheel activated. Growth on one side attracts the other." + - "Strategy: invest in the supply-constrained side, expand categories and geographies, build trust infrastructure." + - "Metric focus: GMV growth rate, repeat rates, cross-side elasticity, organic acquisition %." + maturity: + - "Core segments saturated. Growth comes from adjacencies, take rate optimisation, and value-added services." + - "Strategy: extract more revenue per transaction, launch ancillary products (SaaS, fintech, logistics), defend against verticalised competitors." + - "Metric focus: net revenue growth, ARPU expansion, contribution margin, take rate." + decline: + - "Liquidity leaking. Supply or demand migrating to specialists, aggregators, or direct channels." + - "Strategy: vertical specialisation, quality doubling, managed marketplace pivot, or strategic acquisition." + - "Metric focus: supply churn by tier, demand repeat rate decay, disintermediation rate." + + key_questions: + - "Which life cycle stage is your marketplace in — and does each segment or geography occupy the same stage?" + - "Is your 'maturity' actually healthy saturation, or premature stalling due to quality or trust problems?" + + anti_patterns: + - "Applying product life cycle logic to a marketplace without adapting for two-sided dynamics." + - "Assuming marketplace growth automatically follows product-market fit — liquidity is a separate, harder problem." + + # ────────────────────────────────────────────── + # 9. Growth-Share Matrix (BCG) + # ────────────────────────────────────────────── + - skill: growth-share-matrix + marketplace_reframe: > + The BCG matrix for marketplaces applies to segments, categories, + or geographies within the marketplace — not to the marketplace + as a single entity. A marketplace may have star categories + (high growth, high liquidity), cash cows (mature with stable + take rate revenue), question marks (new categories with uncertain + liquidity), and dogs (categories where the marketplace has no + competitive advantage). + + two_sided_application: + category_portfolio: + - "Map each marketplace category or geography on two axes: GMV growth rate and relative market share (vs. the best alternative for that category)." + - "Stars: high-growth categories where the marketplace is the preferred platform. Invest in supply depth and demand acquisition." + - "Cash cows: mature categories with strong liquidity and stable take rates. Harvest revenue, protect supply, minimise spend." + - "Question marks: new categories with growth potential but unproven liquidity. Test with constrained supply before broad launch." + - "Dogs: categories where a vertical competitor or direct channel dominates. Evaluate exit vs. restructure." + supply_demand_lens: + - "A category can be a star on the demand side (buyers love it) but a dog on the supply side (suppliers prefer direct channels). Diagnose per side." + - "Investment decisions must consider cross-side effects: killing a dog category may remove supply that drives demand in a star category." + + key_questions: + - "Which categories are stars, and do they have sufficient supply depth to sustain growth?" + - "Are your cash cow categories generating enough revenue to fund question mark expansion?" + - "Are any dog categories being subsidised by star categories' cross-side effects?" + + anti_patterns: + - "Treating the entire marketplace as one unit in the matrix rather than analysing categories independently." + - "Killing dog categories without evaluating their cross-side contribution to star categories." + + # ────────────────────────────────────────────── + # 10. Balanced Scorecard + # ────────────────────────────────────────────── + - skill: balanced-scorecard + marketplace_reframe: > + The Balanced Scorecard for a marketplace requires six perspectives, + not four: Supply Side, Demand Side, Platform Operations, Financial, + Innovation, and Trust & Safety. Each perspective carries KPIs + specific to its role in the two-sided ecosystem. + + two_sided_application: + supply_perspective: + - "KPIs: Supply liquidity, supply churn, supply NPS, ARPU (supply), organic supply %, time-to-first-transaction (supply)." + - "Strategic objective: Ensure supply earns enough, transacts frequently enough, and experiences enough value to remain loyal." + demand_perspective: + - "KPIs: Demand fill rate, demand churn, demand NPS, repeat rate (demand), organic demand %, AOV." + - "Strategic objective: Ensure demand finds what it wants, trusts the transaction, and returns habitually." + platform_perspective: + - "KPIs: Match rate, matching speed, search relevance score, platform uptime, algorithm performance." + - "Strategic objective: The matching engine continuously improves in speed, accuracy, and relevance." + financial_perspective: + - "KPIs: GMV, net revenue, take rate, contribution margin per transaction, blended CAC, LTV:CAC per side." + - "Strategic objective: Unit economics improve at each scale milestone." + innovation_perspective: + - "KPIs: New category launches, new geography launches, supply-side SaaS adoption, feature adoption rates." + - "Strategic objective: Expand the marketplace's total addressable market through adjacent supply and demand." + trust_safety_perspective: + - "KPIs: Dispute rate, fraud rate, T&S cost per transaction, marketplace quality score, resolution time." + - "Strategic objective: Trust infrastructure scales with volume without degrading quality." + + key_questions: + - "Which of the six perspectives is your weakest — and is it dragging down the others?" + - "Are your supply-side and demand-side KPIs moving in the same direction, or diverging?" + + anti_patterns: + - "Using the standard four-perspective scorecard without splitting for supply and demand." + - "Overweighting financial KPIs and underweighting trust and quality KPIs." + + # ────────────────────────────────────────────── + # 11. Scenario Planning + # ────────────────────────────────────────────── + - skill: scenario-planning + marketplace_reframe: > + Marketplace scenario planning must account for the reflexive + dynamics unique to two-sided platforms. A shock to one side + cascades to the other. Scenarios must model supply-side shocks + (regulatory, competitor poaching, disintermediation), demand-side + shocks (recession, substitute emergence, trust crisis), and + platform-level shocks (technology disruption, data breach). + + two_sided_application: + supply_shock_scenarios: + - "Scenario: A competitor offers zero-commission for 12 months. What percentage of supply multi-homes or defects? What is the demand impact?" + - "Scenario: Regulation reclassifies supply-side participants as employees. How does the cost structure change?" + - "Scenario: Top 10% of supply leaves for a vertical-specific platform. What is the GMV impact?" + demand_shock_scenarios: + - "Scenario: A recession reduces demand AOV by 30%. Does the marketplace still generate positive contribution margin per transaction?" + - "Scenario: A large aggregator (Amazon, Google) enters demand acquisition for your category. How does demand CAC change?" + - "Scenario: A trust incident (fraud, safety failure) goes viral. What is the demand churn impact?" + platform_scenarios: + - "Scenario: AI-enabled matching eliminates the need for the marketplace's discovery function. What value remains?" + - "Scenario: Payment infrastructure evolution makes disintermediation frictionless. How do you retain transaction flow?" + + key_questions: + - "Which scenario — supply shock, demand shock, or platform disruption — would be most devastating, and do you have a response plan?" + - "How long could your marketplace survive a 50% supply-side defection before demand cascades?" + + anti_patterns: + - "Building scenarios that treat the marketplace as a single-sided business without modelling cross-side cascade effects." + - "Ignoring regulatory scenarios — marketplace regulation is accelerating globally." + + # ────────────────────────────────────────────── + # 12. Cialdini Influence + # ────────────────────────────────────────────── + - skill: cialdini-influence + marketplace_reframe: > + Cialdini's six principles of influence apply asymmetrically in + marketplaces: the influence levers that motivate supply are + different from those that motivate demand. Social proof drives + demand (reviews, ratings, booking counts). Scarcity drives demand + urgency ('3 left at this price'). Reciprocity and commitment + drive supply loyalty (platform investment, earned badges, tier + status). + + two_sided_application: + supply_side_influence: + - "Commitment/Consistency: Invest supply in the platform (profile completion, portfolio, verified status) to increase switching costs." + - "Social Proof: Show suppliers what top performers earn and how. Success stories, leaderboards, earnings benchmarks." + - "Reciprocity: Provide free tools, analytics, and insights to supply before asking for exclusivity or higher take rates." + - "Authority: Position the marketplace as the expert channel — industry data, market reports, pricing guidance." + demand_side_influence: + - "Social Proof: Reviews, ratings, booking counts, 'X people are looking at this.' The dominant demand-side influence lever." + - "Scarcity: Limited availability, time-sensitive pricing, exclusive access. Drives urgency and conversion." + - "Liking: Personalised recommendations, curated collections, editorial content that makes the marketplace feel human." + - "Authority: Trust badges, guarantees, insurance, verified status. Reduces perceived risk." + + key_questions: + - "Which influence principles are you deploying for each side — and are you using the right principles for the right side?" + - "Is your social proof infrastructure (reviews, ratings) building compounding trust, or is it stagnant?" + + anti_patterns: + - "Using the same influence levers for both sides without adapting to their different motivations." + - "Over-using scarcity tactics on demand without genuine supply constraints — erodes trust." + + # ────────────────────────────────────────────── + # 13. Systems Thinking + # ────────────────────────────────────────────── + - skill: systems-thinking + marketplace_reframe: > + A marketplace is inherently a complex adaptive system with + feedback loops between supply, demand, price, quality, and trust. + Systems thinking is not optional for marketplace operators — it + is the foundational mental model. Every intervention on one side + produces second- and third-order effects on the other. + + two_sided_application: + reinforcing_loops: + - "Virtuous: More supply → better selection → more demand → more transactions → more supply earnings → more supply. The liquidity flywheel." + - "Virtuous: More reviews → more trust → more demand → more supply → more reviews. The trust flywheel." + - "Vicious: Supply churn → less selection → demand churn → less revenue for remaining supply → more supply churn. The death spiral." + balancing_loops: + - "Supply flooding: Too much supply → lower liquidity → lower supply earnings → supply exit → rebalance." + - "Quality degradation: Growth → lower quality supply enters → average quality drops → demand churn → quality floor resets." + - "Take rate ceiling: Higher take rate → supply cost increases → supply either raises prices or leaves → equilibrium." + leverage_points: + - "Supply quality curation: small improvements in supply quality produce outsized demand-side effects." + - "Matching algorithm: better matching improves liquidity, fill rate, repeat rate, and NPS simultaneously." + - "Trust infrastructure: trust improvements reduce T&S costs, increase demand conversion, and reduce disintermediation." + + key_questions: + - "Can you map the three strongest feedback loops in your marketplace — and identify which are reinforcing and which are balancing?" + - "Where is the highest-leverage intervention point in your system right now?" + + anti_patterns: + - "Optimising one metric in isolation without modelling the system-wide effects." + - "Treating supply and demand as independent variables rather than interdependent components of a feedback system." + + # ────────────────────────────────────────────── + # 14. Tipping Point + # ────────────────────────────────────────────── + - skill: tipping-point + marketplace_reframe: > + Marketplaces have a literal tipping point: the moment when + liquidity becomes self-sustaining and the flywheel generates more + growth than paid acquisition. Before the tipping point, the + marketplace is pushing. After, it is pulled. Identifying and + reaching this inflection is the central challenge of marketplace + building. + + two_sided_application: + liquidity_tipping_point: + - "The threshold at which supply liquidity and demand fill rate are both high enough that organic growth exceeds paid growth." + - "Typically occurs in a single geography or category first. Go narrow and deep rather than broad and shallow." + - "Measurable signals: organic acquisition >50% on both sides, repeat rates stabilising above 40%, supply churn below 5%." + network_effects_tipping_point: + - "The point at which cross-side elasticity is measurably positive: adding supply increases demand engagement." + - "Precedes the liquidity tipping point — network effects must be detectable before they become self-sustaining." + geographic_or_category_tipping: + - "Each new geography or category has its own tipping point. National GMV can mask the fact that no individual market has tipped." + - "Strategy: focus resources on tipping one market at a time rather than spreading thin across many." + + key_questions: + - "Has your marketplace tipped in any market — and what metrics prove it?" + - "How many markets need to tip for the business to become self-sustaining?" + + anti_patterns: + - "Claiming network effects exist because both sides are growing — parallel growth without cross-side causation is not a network effect." + - "Spreading launch resources across many markets, tipping none." + + # ────────────────────────────────────────────── + # 15. Art of War + # ────────────────────────────────────────────── + - skill: art-of-war + marketplace_reframe: > + Marketplace warfare is fought on two fronts simultaneously: the + battle for supply and the battle for demand. The most effective + marketplace strategies attack the competitor's weaker side — if + a competitor's supply is loyal but demand is shaky, attack demand. + If their demand is strong but supply is commoditised, recruit + their supply. + + two_sided_application: + offensive_strategies: + - "Supply poaching: Offer lower take rates, guaranteed minimum earnings, or superior tools to recruit competitors' best supply." + - "Demand capture: Invest in SEO, brand, or referral programs to intercept demand before it reaches the competitor." + - "Wedge category: Dominate a narrow category the competitor underserves, build supply-demand flywheel there, then expand." + defensive_strategies: + - "Supply lock-in: Build switching costs through accumulated reviews, analytics history, earned status, and supply-side SaaS tools." + - "Demand moat: Create loyalty programs, personalisation, and purchase history that make switching costly for buyers." + - "Quality differentiation: Curate supply quality so that the competitor's lower-friction onboarding produces a worse demand experience." + intelligence: + - "Monitor competitor take rates, supply incentive programs, and demand promotions continuously." + - "Track multi-homing rates — the percentage of your supply and demand that also uses competitors. This is your competitive vulnerability score." + + key_questions: + - "Which side of your marketplace is more vulnerable to competitive attack — and are you investing enough to defend it?" + - "Can you identify a wedge category or geography where a competitor is weak on both sides?" + + anti_patterns: + - "Fighting a price war on take rates without building structural advantages that justify a premium." + - "Defending both sides equally when one side is more at risk." + + # ────────────────────────────────────────────── + # 16. Doblin Ten Types of Innovation + # ────────────────────────────────────────────── + - skill: doblin-ten-types + marketplace_reframe: > + Doblin's ten types of innovation map onto marketplace strategy + with a supply-demand twist: each type of innovation can be + deployed for the supply side, the demand side, or the platform + itself. The most defensible marketplace innovations combine + multiple types across multiple sides. + + two_sided_application: + configuration_innovations: + - "Profit Model: Take rate structure, demand-side fees, supply SaaS tools, advertising revenue, fintech. Innovate on how value is captured from both sides." + - "Network: Supply-side partnerships (logistics, insurance), demand-side integrations (APIs, embedded commerce). The marketplace IS a network innovation." + - "Structure: Supply operations team, demand growth team, trust and safety org. Organisational design must mirror the two-sided nature." + - "Process: Matching algorithms, quality curation, dispute resolution, fraud detection. Platform process innovation is the competitive edge." + offering_innovations: + - "Product Performance: Supply-side tools and analytics, demand-side search and discovery, matching quality." + - "Product System: Bundled services (payments + logistics + insurance + marketing), cross-category expansion, ecosystem build-out." + experience_innovations: + - "Service: Supply onboarding, demand support, both-side dispute resolution. Service innovation per side." + - "Channel: Supply recruitment channels, demand acquisition channels — innovate separately." + - "Brand: Supply-side employer brand ('earn on [platform]'), demand-side consumer brand ('find it on [platform]')." + - "Customer Engagement: Supply dashboards and community, demand personalisation and loyalty. Engagement mechanisms per side." + + key_questions: + - "Across Doblin's ten types, where are you innovating — and are your innovations concentrated on one side or distributed?" + - "Which innovation type would create the most defensibility for your marketplace?" + + anti_patterns: + - "Innovating only on the demand-side experience while treating supply-side tools as commodity." + - "Focusing innovation on a single type (usually product performance) when marketplace defensibility requires multi-type innovation." + + # ────────────────────────────────────────────── + # 17. Kaizen / BPR + # ────────────────────────────────────────────── + - skill: kaizen-bpr + marketplace_reframe: > + Continuous improvement in a marketplace operates on three process + chains: the supply-side experience, the demand-side experience, + and the matching/transaction process that connects them. Kaizen + applies to incremental improvements in each chain. BPR applies + when a chain is fundamentally broken — typically the matching + process or the trust infrastructure. + + two_sided_application: + supply_side_kaizen: + - "Reduce friction in supply onboarding: fewer steps, faster verification, quicker time to first listing." + - "Improve supply tools: better analytics, pricing suggestions, demand forecasting, inventory management." + - "Streamline payout process: faster payment, clearer statements, fewer support tickets." + demand_side_kaizen: + - "Improve search and discovery: better relevance, filters, recommendations." + - "Reduce checkout friction: fewer steps, saved preferences, one-click re-order." + - "Accelerate dispute resolution: faster response, clearer policies, fairer outcomes." + platform_bpr: + - "When the matching algorithm produces poor matches despite adequate supply and demand — re-engineer the matching process." + - "When trust infrastructure cannot scale (manual review bottleneck) — re-engineer from manual to automated with human oversight." + - "When the take rate structure creates perverse incentives — re-engineer the revenue model." + + key_questions: + - "Which process chain — supply, demand, or platform — has the most friction right now?" + - "Is the problem incremental (kaizen) or structural (BPR)?" + + anti_patterns: + - "Applying kaizen to the demand side while the supply-side experience is fundamentally broken." + - "Re-engineering processes that are working adequately while ignoring the process chain that is actually failing." + + # ────────────────────────────────────────────── + # 18. Kotter Change Model + # ────────────────────────────────────────────── + - skill: kotter-change-model + marketplace_reframe: > + Major changes in a marketplace — take rate increases, policy shifts, + new quality requirements, platform migrations — must be managed + as change programs for both sides. The supply side is typically + more change-resistant because their livelihood depends on the + platform. Failed change management on the supply side produces + immediate, measurable damage: supply churn. + + two_sided_application: + supply_side_change: + - "Urgency: Supply must understand WHY the change benefits them long-term (better demand, higher earnings, less fraud)." + - "Coalition: Recruit top suppliers as early adopters and advocates. Their endorsement carries more weight than platform messaging." + - "Communication: Supply-side communication must be transparent about trade-offs. Never disguise a take rate increase as a 'feature.'" + - "Quick wins: Show early positive results (higher conversion, more demand, faster payouts) within the first 30 days." + demand_side_change: + - "Demand is generally more tolerant of platform changes IF the core value proposition (selection, trust, convenience) is preserved." + - "UX changes that increase friction (new checkout steps, mandatory reviews) require careful demand-side change management." + - "Price changes visible to demand (buyer fees, service fees) must be justified with visible value." + + key_questions: + - "Which side will be more affected by this change — and have you designed a side-specific change management plan?" + - "Have you recruited advocates from the affected side before announcing the change?" + + anti_patterns: + - "Announcing take rate increases without advance notice, rationale, or supply-side input." + - "Assuming demand will accept any change as long as supply quality is maintained." + + # ────────────────────────────────────────────── + # 19. Trust Equation + # ────────────────────────────────────────────── + - skill: trust-equation + marketplace_reframe: > + Trust in a marketplace operates on three axes: buyer trust in + supply (does this seller deliver?), supply trust in the platform + (will I get paid fairly?), and buyer trust in the platform (will + I be protected if something goes wrong?). The trust equation + (Credibility + Reliability + Intimacy) / Self-Orientation applies + to each axis independently. A marketplace with high buyer-seller + trust but low platform trust will be disintermediated. + + two_sided_application: + buyer_seller_trust: + - "Credibility: Verified credentials, portfolio, qualifications. The marketplace curates and validates." + - "Reliability: Transaction history, on-time delivery rate, consistency score. Data the marketplace uniquely can provide." + - "Intimacy: Communication quality, personalisation, responsiveness. The marketplace can facilitate but not force." + - "Self-Orientation: Does the seller prioritise the buyer's outcome? Reviews and ratings make this visible." + supply_platform_trust: + - "Credibility: Does the platform deliver on promised demand volume and earnings potential?" + - "Reliability: Are payouts on time? Are policies consistent? Are disputes resolved fairly?" + - "Intimacy: Does the platform treat supply as partners or as interchangeable units?" + - "Self-Orientation: Does the platform optimise for its own take rate at supply's expense?" + buyer_platform_trust: + - "Credibility: Is the platform's curation and vetting credible?" + - "Reliability: Are guarantees honoured? Is support responsive? Are refunds processed fairly?" + - "Intimacy: Does the platform remember preferences, anticipate needs, personalise?" + - "Self-Orientation: Does the platform push sponsored or high-margin listings over best matches?" + + key_questions: + - "Which trust axis is weakest in your marketplace — and is it limiting growth on one side?" + - "If a trust incident occurs, which axis breaks first, and what is the cascade?" + + anti_patterns: + - "Investing in buyer-seller trust signals (reviews) while neglecting supply-platform trust (payout reliability, policy fairness)." + - "Treating trust as a feature rather than the core infrastructure of the marketplace." + + # ────────────────────────────────────────────── + # 20. Covey Seven Habits + # ────────────────────────────────────────────── + - skill: covey-seven-habits + marketplace_reframe: > + Habit 4 (Think Win-Win) is the operating philosophy for marketplace + founders. A marketplace that wins at the expense of either side + is a marketplace on a timer. Habit 5 (Seek First to Understand) maps + directly to the discipline of understanding both sides' needs + before designing platform policies. Habit 6 (Synergize) is the + network effect itself — the whole exceeds the sum of supply and demand. + + two_sided_application: + win_win_imperative: + - "Every platform decision must be evaluated through three lenses: does it help supply? Does it help demand? Does it sustain the platform?" + - "A policy that benefits demand at supply's direct expense (take rate increase, stricter quality requirements without support) is win-lose. It will revert." + - "Win-win-win: supply earns more, demand gets better outcomes, platform captures fair value. This is the only sustainable equilibrium." + understanding_both_sides: + - "Marketplace founders disproportionately understand one side (usually demand). Deliberately invest in understanding the other." + - "Regular supply-side listening: ride-alongs, supplier advisory boards, earnings analysis, churn interviews." + - "Regular demand-side listening: search query analysis, failed-match analysis, support ticket themes." + + key_questions: + - "When did you last speak directly with supply-side participants about their experience — not through data, through conversation?" + - "Is your latest major platform decision win-win-win, or does one side lose?" + + anti_patterns: + - "Optimising for demand satisfaction at supply's expense, assuming supply has no alternatives." + - "Making policy decisions based on platform financial benefit without modelling supply and demand impact." + + # ────────────────────────────────────────────── + # 21. Win-Win Negotiation + # ────────────────────────────────────────────── + - skill: win-win-negotiation + marketplace_reframe: > + Marketplace founders negotiate continuously — with supply (terms, + take rates, quality requirements), with demand (pricing, policies, + expectations), and between the two sides when their interests + conflict. The negotiation is never bilateral; it is trilateral, + and the platform must find the integrative solution that keeps + all three parties engaged. + + two_sided_application: + supply_negotiations: + - "Take rate: not a price — a value equation. Negotiate by demonstrating measurable demand access, tools, and trust value." + - "Quality requirements: negotiate as investments, not burdens. Show data on how quality compliance increases supply earnings." + - "Exclusivity: the highest-stakes negotiation. What does the platform offer in return for supply not listing elsewhere?" + demand_negotiations: + - "Pricing transparency: demand pushes for lower prices. The platform must negotiate by delivering value (guarantees, convenience) that justifies fees." + - "Policy: refund policies, dispute resolution rules, cancellation terms. Each is a negotiation between demand expectations and supply protection." + cross_side_mediation: + - "When supply wants higher prices and demand wants lower: the platform's role is to increase the total value created, not just redistribute it." + - "Dispute resolution IS negotiation. The platform's fairness in disputes determines long-term trust on both sides." + + key_questions: + - "In your most recent major negotiation with supply or demand — did you find a win-win, or did one side concede?" + - "How do you mediate when supply and demand interests directly conflict?" + + anti_patterns: + - "Treating take rate as non-negotiable rather than as a value-based proposition." + - "Siding systematically with demand in disputes to protect demand metrics, eroding supply trust." + + # ────────────────────────────────────────────── + # 22. First Mover Strategy + # ────────────────────────────────────────────── + - skill: first-mover-strategy + marketplace_reframe: > + First-mover advantage in marketplaces is real but narrow: it + accrues primarily through early liquidity in a specific segment, + not through brand awareness or technology. The first marketplace + to achieve liquidity in a category-geography combination builds + network effects that are genuinely hard to replicate. But first + movers who launch broad and fail to achieve liquidity anywhere + lose to focused second movers who tip a single market first. + + two_sided_application: + first_mover_advantages: + - "Liquidity lock-in: the first marketplace to tip a market accumulates reviews, transaction history, and trust signals that competitors cannot instantly replicate." + - "Supply-side habits: suppliers who build their business around a platform develop workflow dependencies and switching costs." + - "SEO and brand: first mover in a category captures organic search demand and becomes the category synonym." + first_mover_disadvantages: + - "Chicken-and-egg cost: the first mover bears the entire cost of market education and initial liquidity." + - "Premature scaling: first movers often expand geography or categories before achieving liquidity in the first market." + - "Second movers learn from first-mover mistakes: better trust infrastructure, better matching, better unit economics." + + key_questions: + - "Have you achieved genuine first-mover liquidity advantage in any market — or just first-mover presence?" + - "What would a well-funded second mover do differently based on your mistakes?" + + anti_patterns: + - "Claiming first-mover advantage from being first to launch rather than first to achieve liquidity." + - "Expanding to new markets before the first market has tipped." + + # ────────────────────────────────────────────── + # 23. Information Asymmetry + # ────────────────────────────────────────────── + - skill: information-asymmetry + marketplace_reframe: > + Marketplaces exist because of information asymmetry — buyers + do not know which suppliers are good, and suppliers do not know + which buyers will pay. The marketplace's core value is reducing + information asymmetry through ratings, reviews, verified + credentials, and algorithmic matching. But the platform itself + holds information asymmetry over both sides — and how it uses + that power determines trust. + + two_sided_application: + supply_demand_asymmetry: + - "Adverse selection: without quality signals, low-quality supply drives out high-quality supply (Akerlof's lemons problem). Marketplace curation is the antidote." + - "Moral hazard: once matched, either side may shirk commitments. The platform's review and enforcement mechanisms mitigate this." + - "Screening: verification, portfolios, and qualification requirements reduce adverse selection on the supply side." + - "Signalling: reviews, ratings, badges, and certifications help quality supply signal their value credibly." + platform_information_power: + - "The platform sees all: pricing data, demand patterns, supply performance, competitive dynamics. This information advantage is powerful and dangerous." + - "Sharing data with supply (demand trends, pricing benchmarks, competitor analysis) builds trust and loyalty." + - "Withholding data or using it to extract value (surge pricing without transparency, algorithmic manipulation) erodes trust." + + key_questions: + - "What information asymmetries does your marketplace reduce — and which does it create?" + - "How much data do you share with supply vs. how much you retain as a platform advantage?" + + anti_patterns: + - "Using platform information asymmetry to manipulate supply-side pricing or behaviour without transparency." + - "Failing to invest in quality signals (reviews, verification) that reduce buyer-seller information asymmetry." + + # ────────────────────────────────────────────── + # 24. Game Theory Fundamentals + # ────────────────────────────────────────────── + - skill: game-theory-fundamentals + marketplace_reframe: > + A marketplace is a multi-player game with interdependent payoffs. + Supply and demand are not opponents — they are complementors whose + combined activity generates the value the platform captures. But + the platform's design choices (take rate, matching algorithm, + policies) shape the payoff structure for all players. Poorly + designed incentives produce Nash equilibria that destroy the + marketplace. + + two_sided_application: + coordination_game: + - "The chicken-and-egg problem is a coordination game. Both sides benefit from being on the platform, but neither wants to be first." + - "Solution strategies: subsidise one side, provide standalone value, constrain supply to create scarcity, aggregate existing demand." + incentive_design: + - "Take rate affects supplier strategy: too high → supply raises prices or leaves. Too low → platform cannot invest in quality." + - "Demand-side promotions create strategic behaviour: buyers time purchases for promotions, distorting demand patterns." + - "Supply-side incentives (minimum earnings guarantees) must be designed to avoid moral hazard." + competitive_game: + - "Multi-homing is the Nash equilibrium in a competitive marketplace landscape — both sides rationally use multiple platforms." + - "The platform's strategy: make single-homing the dominant strategy through switching costs, exclusive content, or superior economics." + + key_questions: + - "What is the Nash equilibrium of your current incentive structure — and is it the equilibrium you want?" + - "Does your incentive design encourage single-homing or inadvertently reward multi-homing?" + + anti_patterns: + - "Designing incentives for one side without modelling the strategic response of the other side." + - "Assuming supply will accept take rate increases without strategic retaliation (price increases, multi-homing, disintermediation)." + + # ────────────────────────────────────────────── + # 25. Prisoner's Dilemma and Cooperation + # ────────────────────────────────────────────── + - skill: prisoners-dilemma-and-cooperation + marketplace_reframe: > + Supply-side participants on a marketplace face a classic prisoner's + dilemma: collectively, they benefit from maintaining prices and + quality. Individually, each is incentivised to undercut on price + or cut corners on quality. The marketplace's role is to design + mechanisms that make cooperation the dominant strategy — through + quality scoring, price floors, or reputation systems. + + two_sided_application: + supply_side_dilemma: + - "Race to bottom on pricing: if one seller undercuts, others must follow. The marketplace loses quality and margin." + - "Quality shortcuts: if one provider delivers lower quality without penalty, others rationally follow. Reviews are the enforcement mechanism." + - "Platform design: minimum quality standards, review-weighted ranking, and price guidance can shift the equilibrium toward cooperation." + platform_competitor_dilemma: + - "Competing marketplaces face a prisoner's dilemma on supply subsidies: both would profit from stopping, but neither can unilaterally." + - "Take rate wars are mutually destructive — the winner is the platform that creates the most value, not the one that charges the least." + + key_questions: + - "Is your supply side in a race to the bottom — and what mechanisms prevent it?" + - "Are you in a prisoner's dilemma with a competitor on supply subsidies?" + + anti_patterns: + - "Allowing unrestricted price competition among supply without quality enforcement — produces a lemon market." + - "Engaging in a take rate war without calculating the break-even point." + + # ────────────────────────────────────────────── + # 26. Coalition and Partnership Games + # ────────────────────────────────────────────── + - skill: coalition-and-partnership-games + marketplace_reframe: > + Marketplace partnerships are inherently coalition games. The + platform, supply aggregators, demand channels, logistics providers, + and payment processors each contribute to and extract value from + the ecosystem. The Shapley value framework — distributing value + in proportion to each party's marginal contribution — is a + useful model for structuring marketplace partnership economics. + + two_sided_application: + supply_partnerships: + - "Aggregator partnerships: partnering with supply aggregators (property managers, fleet operators, agency platforms) accelerates supply acquisition but concentrates power." + - "Value distribution: what share of the take rate does the aggregator receive? Their Shapley value depends on whether they bring supply that would not otherwise exist on the platform." + demand_partnerships: + - "Channel partnerships: partnering with demand aggregators (travel sites, comparison engines, embedded commerce) drives volume but reduces margin." + - "Value distribution: CPA, revenue share, or fixed fee? The structure must reflect the incremental demand the partner delivers." + ecosystem_coalitions: + - "Payment, logistics, insurance, and trust providers form the marketplace's enabling coalition. Their costs directly impact contribution margin per transaction." + - "Vertical integration vs. partnership: when should the marketplace build (payments, logistics) vs. partner? Build when the partner captures too much of the value chain." + + key_questions: + - "Who are the key coalition partners in your marketplace ecosystem — and is each capturing value proportional to their contribution?" + - "Would vertically integrating any partner function significantly improve unit economics?" + + anti_patterns: + - "Giving supply aggregators disproportionate power over the platform by concentrating too much supply in partner hands." + - "Partnering with demand channels that cannibalise organic demand rather than creating incremental volume." + + # ────────────────────────────────────────────── + # 27. Evolutionary Strategy + # ────────────────────────────────────────────── + - skill: evolutionary-strategy + marketplace_reframe: > + Marketplace evolution follows patterns analogous to biological + ecosystems: niche specialisation (vertical marketplaces), predation + (platform envelopment), symbiosis (complementary platforms), and + extinction (liquidity death). Understanding evolutionary dynamics + helps marketplace founders anticipate category evolution. + + two_sided_application: + marketplace_evolution_patterns: + - "Horizontal to vertical: broad marketplaces (eBay, Craigslist) get disrupted by vertical specialists (StockX, Reverb, Turo) that offer category-specific trust and curation." + - "Aggregation to curation: early marketplaces aggregate supply. Mature marketplaces curate it. The shift from 'everything available' to 'the right thing recommended' is an evolutionary transition." + - "Marketplace to managed marketplace: evolution from listing-and-matching to end-to-end managed transactions (Opendoor vs Zillow)." + competitive_evolution: + - "Platform envelopment: a larger platform (Amazon, Google) adds marketplace functionality to its existing user base, bypassing the chicken-and-egg problem." + - "Defence against envelopment: vertical depth, supply exclusivity, and trust infrastructure that a generalist cannot replicate." + + key_questions: + - "Where is your marketplace in its evolutionary arc — and what comes next?" + - "Is a larger platform likely to envelop your category, and what defence do you have?" + + anti_patterns: + - "Assuming your marketplace's current form is its final form — marketplaces evolve or die." + - "Ignoring the horizontal-to-vertical evolution pattern when operating a broad marketplace." + + # ────────────────────────────────────────────── + # 28. Negotiation Game Theory + # ────────────────────────────────────────────── + - skill: negotiation-game-theory + marketplace_reframe: > + The marketplace founder negotiates with three counterparties + simultaneously: supply (terms, take rate, quality), demand + (price, guarantees, experience), and investors (valuation, + milestones, governance). Each negotiation affects the others — + concessions to supply on take rate affect the financial case + for investors; concessions to demand on guarantees affect + supply-side economics. + + two_sided_application: + trilateral_negotiation: + - "Take rate negotiation with supply constrains revenue growth for investor negotiations." + - "Guarantee negotiation with demand creates costs that affect supply-side economics." + - "Every concession on one side must be modelled for its impact on the other two stakeholders." + batna_per_side: + - "Supply BATNA: what is the supplier's best alternative to your marketplace? Direct sales, competitor marketplace, offline channels." + - "Demand BATNA: what is the buyer's best alternative? Direct from source, competitor marketplace, do-it-yourself." + - "The side with the weaker BATNA has less negotiating power. The marketplace should strengthen both sides' dependence." + + key_questions: + - "What is each side's BATNA — and which side has more alternatives?" + - "When you negotiate with one side, have you modelled the cross-side impact?" + + anti_patterns: + - "Negotiating with supply and demand independently without modelling the cross-side impact of each agreement." + - "Underestimating supply's BATNA — particularly in categories where direct channels are viable." + + # ────────────────────────────────────────────── + # 29. SMART Goals + # ────────────────────────────────────────────── + - skill: smart-goals + marketplace_reframe: > + SMART goals in a marketplace must be set per side and for the + platform. A single revenue target obscures whether the goal + requires supply growth, demand growth, take rate optimisation, + or all three. Decompose every marketplace goal into its supply-side, + demand-side, and platform-level components. + + two_sided_application: + goal_decomposition: + - "Revenue goal = GMV target x take rate. GMV = demand transactions x AOV. Demand transactions = active buyers x purchase frequency. Active buyers = f(demand acquisition, demand retention). Each step requires its own SMART goal." + - "Supply goals: X new suppliers onboarded, Y% supply liquidity maintained, Z% supply churn rate." + - "Demand goals: X new buyers acquired, Y% repeat rate achieved, Z average transactions per buyer." + - "Platform goals: matching accuracy target, T&S cost per transaction target, contribution margin target." + side_specific_measurability: + - "Ensure every goal specifies WHICH side it targets and how cross-side effects will be monitored." + - "A demand acquisition goal must include a supply liquidity constraint — acquiring demand without adequate supply destroys fill rate." + + key_questions: + - "Have you decomposed your top-line goals into supply-side, demand-side, and platform components?" + - "Does achieving your supply goals require demand goals to also be met — and vice versa?" + + anti_patterns: + - "Setting a GMV goal without specifying the supply and demand growth required to achieve it." + - "Setting goals for one side without constraint conditions for the other." + + # ────────────────────────────────────────────── + # 30. Emotional Intelligence + # ────────────────────────────────────────────── + - skill: emotional-intelligence + marketplace_reframe: > + Marketplace leadership requires emotional intelligence across + two distinct constituencies with often-opposing interests. The + empathy required to understand supply-side frustrations (take rate + resentment, algorithmic opacity, income volatility) coexists with + empathy for demand-side expectations (quality, speed, safety). + The marketplace founder must hold both perspectives simultaneously + without defaulting to one side. + + two_sided_application: + supply_side_eq: + - "Supply-side participants are emotionally invested — this is their livelihood. Policy changes that feel minor to the platform feel existential to supply." + - "Algorithmic decisions (ranking, visibility, matching) affect supply income directly. Transparency and fairness are emotional necessities, not features." + - "Supply-side community management requires genuine empathy for the stress of income dependence on a platform." + demand_side_eq: + - "Demand-side trust is emotional, not rational. A single negative experience can override dozens of positive ones." + - "Demand expects the platform to be their advocate in disputes — even when the supply side is objectively correct." + - "Demand-side disappointment (failed transactions, quality mismatches) requires rapid, emotionally intelligent resolution." + founder_balance: + - "The most common EQ failure in marketplace founders: identifying with one side (usually demand) and treating the other as a resource to be managed." + - "Balanced empathy across both sides is a strategic advantage — it prevents policies that optimise for one side at the other's expense." + + key_questions: + - "Which side do you naturally empathise with more — and is that creating blind spots in your policy decisions?" + - "When did you last spend a day doing what your supply-side participants do?" + + anti_patterns: + - "Making policy decisions based on demand data alone without consulting supply-side sentiment." + - "Treating supply as interchangeable resources rather than as customers with emotional needs." + + # ────────────────────────────────────────────── + # 31. Thinking Fast and Slow + # ────────────────────────────────────────────── + - skill: thinking-fast-and-slow + marketplace_reframe: > + Both supply and demand make decisions using System 1 (fast, + intuitive) and System 2 (slow, analytical). The marketplace's + UX, pricing, and trust signals must be designed for the appropriate + system. Demand-side purchase decisions in on-demand marketplaces + are System 1 — design for speed and simplicity. Supply-side + decisions to join a platform are System 2 — design for data + and credibility. + + two_sided_application: + demand_side_cognition: + - "On-demand and low-AOV purchases: System 1 dominant. Minimise choice, maximise trust signals, reduce friction. One-tap ordering, pre-selected defaults." + - "High-AOV and considered purchases: System 2 engaged. Provide comparison tools, detailed reviews, and information depth." + - "Anchoring: the first price a buyer sees anchors expectations. Marketplace presentation order matters." + supply_side_cognition: + - "Joining the marketplace: System 2. Supply evaluates earnings potential, terms, competition, and alternatives analytically." + - "Day-to-day pricing and listing: System 1. Provide smart defaults, pricing suggestions, and automated tools." + - "Loss aversion: supply-side participants feel losses (cancelled bookings, returned items, negative reviews) 2x more than equivalent gains." + + key_questions: + - "Is your UX designed for the cognitive system each side uses at each decision point?" + - "Are you exploiting cognitive biases in ways that erode long-term trust?" + + anti_patterns: + - "Requiring System 2 engagement (complex pricing, extensive forms) at System 1 decision points (on-demand purchases)." + - "Using dark patterns (hidden fees, manipulative urgency) that exploit System 1 at the expense of trust." + + # ────────────────────────────────────────────── + # 32. Hackman Enabling Conditions + # ────────────────────────────────────────────── + - skill: hackman-enabling-conditions + marketplace_reframe: > + Hackman's five conditions for effective teams apply to the + internal organisation of a marketplace company, which must be + structured around the two-sided nature of the business. Supply + operations, demand growth, and platform/product are the three + core teams — and their enabling conditions differ. + + two_sided_application: + supply_ops_team: + - "Real team: dedicated supply-side operations with clear boundaries — not a shared 'business development' team." + - "Compelling direction: supply-side KPIs (liquidity, supply churn, supply NPS, ARPU) as north star." + - "Enabling structure: direct access to supply-side data, supplier communication channels, and policy authority." + - "Supportive context: resources for supply onboarding, tools, community management, and T&S." + demand_growth_team: + - "Real team: dedicated demand acquisition and retention with clear boundaries from supply ops." + - "Compelling direction: demand-side KPIs (fill rate, demand churn, repeat rate, organic demand %)." + - "Enabling structure: marketing budget authority, analytics access, channel experimentation capability." + - "Supportive context: resources for brand, content, SEO, paid acquisition, and CRM." + platform_team: + - "Real team: matching algorithm, trust infrastructure, payments, and core marketplace platform." + - "Compelling direction: platform-level KPIs (match quality, transaction completion rate, T&S cost per transaction)." + - "Cross-team coordination: the platform team serves both supply ops and demand growth — clear prioritisation mechanisms are essential." + + key_questions: + - "Are your supply and demand teams structurally separate with distinct KPIs — or is one team trying to serve both sides?" + - "Does the platform team have clear prioritisation rules for supply-side vs demand-side feature requests?" + + anti_patterns: + - "A single 'growth' team responsible for both supply and demand acquisition — the strategies are fundamentally different." + - "Platform team prioritising demand features because demand data is louder, while supply-side infrastructure decays." + + # ────────────────────────────────────────────── + # 33. Appreciative Inquiry + # ────────────────────────────────────────────── + - skill: appreciative-inquiry + marketplace_reframe: > + Appreciative Inquiry's 4-D cycle (Discover, Dream, Design, Destiny) + can be applied to both sides of a marketplace to understand what + is working and amplify it. The most valuable discovery: why do your + best suppliers stay, and why do your most loyal buyers return? + Amplifying the positive core of each side's experience is more + productive than fixing every complaint. + + two_sided_application: + supply_side_inquiry: + - "Discover: What do your top 10% suppliers value most about the platform? Why do they stay despite alternatives?" + - "Dream: What would make this marketplace the only platform they need?" + - "Design: How can the platform amplify the positive factors for all supply, not just the top tier?" + - "Destiny: What supply-side investments would make the top 10%'s experience the norm?" + demand_side_inquiry: + - "Discover: What do your highest-repeat-rate buyers love about the experience?" + - "Dream: What would make every transaction as satisfying as their best one?" + - "Design: How can the platform replicate the best-experience factors across all transactions?" + - "Destiny: What demand-side investments would make the best experience the default?" + + key_questions: + - "What is the positive core of your supply-side experience — and are you investing to amplify it?" + - "What is the positive core of your demand-side experience — and are you investing to amplify it?" + + anti_patterns: + - "Focusing exclusively on churn reasons (deficiency-based) rather than retention reasons (strengths-based)." + - "Running appreciative inquiry for demand but not for supply." + + # ────────────────────────────────────────────── + # 34. Delegation and Empowerment + # ────────────────────────────────────────────── + - skill: delegation-and-empowerment + marketplace_reframe: > + In a marketplace organisation, delegation must follow the + two-sided structure. Supply-side decisions (onboarding standards, + supplier support policies, take rate structure) require deep + supply-side context. Demand-side decisions (marketing spend, + buyer UX, promotion strategy) require demand-side expertise. + The founder's role is to set the supply-demand balance and + delegate execution per side. + + two_sided_application: + supply_side_delegation: + - "Delegate supply onboarding, quality standards, and supplier communication to a supply ops lead with authority to make policy decisions." + - "Empower supply-side team with direct access to supplier feedback and performance data." + - "Retain: take rate decisions, major policy changes affecting supply economics, strategic supplier partnerships." + demand_side_delegation: + - "Delegate demand acquisition, retention campaigns, and buyer experience to a growth lead with budget authority." + - "Empower demand-side team with experimentation budget and channel testing freedom." + - "Retain: brand strategy, pricing architecture, major UX redesigns." + cross_side_governance: + - "When supply and demand team priorities conflict (supply wants higher prices, demand wants lower), the founder or CEO resolves." + - "Create a cross-side review cadence: weekly supply-demand balance review where both teams present metrics and flag conflicts." + + key_questions: + - "Have you delegated enough authority to your supply and demand leaders — or are you the bottleneck on both sides?" + - "Is there a clear escalation path when supply and demand team priorities conflict?" + + anti_patterns: + - "Delegating demand growth but micromanaging supply operations (or vice versa)." + - "No formal mechanism for resolving cross-side priority conflicts." + + # ────────────────────────────────────────────── + # 35. Strategic Thinking and Alignment + # ────────────────────────────────────────────── + - skill: strategic-thinking-and-alignment + marketplace_reframe: > + Strategic alignment in a marketplace means ensuring that supply + strategy, demand strategy, and platform strategy all reinforce the + same marketplace thesis. Misalignment — supply ops optimising for + volume while demand marketing optimises for premium — produces + marketplace incoherence that confuses both sides. + + two_sided_application: + strategic_coherence: + - "The marketplace thesis must be expressible in one sentence that describes both sides: 'We connect [specific supply] with [specific demand] by providing [unique platform value].'" + - "Supply strategy, demand strategy, and platform strategy should all trace back to this thesis." + - "Strategic misalignment example: supply team recruits professional service providers while demand marketing targets budget buyers. The mismatch destroys both sides' experience." + alignment_mechanisms: + - "Unified marketplace scorecard with supply, demand, and platform KPIs visible to all teams." + - "Quarterly supply-demand strategy review: are both sides' strategies reinforcing the same positioning?" + - "Strategic constraints: define what the marketplace will NOT do on each side. Constraints align faster than goals." + investment_alignment: + - "Growth investment should follow the binding constraint: if supply is the bottleneck, invest there; if demand is the bottleneck, invest there." + - "Balanced investment across both sides when neither is constrained is wasteful — one side is always the bottleneck." + + key_questions: + - "Can you state your marketplace thesis in one sentence that describes both sides?" + - "Which side is currently the binding constraint — and is your investment allocation consistent with that?" + + anti_patterns: + - "Supply and demand teams operating with independent strategies that were never reconciled." + - "Investing equally in both sides when one side is clearly the constraint." diff --git a/plugins/foreman/content/industry-packs/marketplace/marketplace-templates.yaml b/plugins/foreman/content/industry-packs/marketplace/marketplace-templates.yaml new file mode 100644 index 0000000..09ec105 --- /dev/null +++ b/plugins/foreman/content/industry-packs/marketplace/marketplace-templates.yaml @@ -0,0 +1,1074 @@ +# Marketplace Industry Pack — Template Adaptations +# Provides marketplace-specific adaptations for each of the 48 output +# templates, reframing fill-in fields, structure, and guidance through +# the two-sided marketplace lens: supply, demand, platform, take rate, +# liquidity, and network effects. +# +# Each adaptation does not replace the base template — it augments it +# with marketplace-native sections, fields, and framing. Unit economics +# become per-transaction. Investor materials emphasise liquidity and +# network effects. Team templates distinguish supply ops from demand +# growth. + +pack: marketplace +author: "Fatih Guner" +type: template_adaptations +version: "1.0.0" + +# ============================================================ +# INVESTOR TEMPLATES (10) +# ============================================================ + +investor_templates: + + # ────────────────────────────────────────────── + # 1. Strategic Analysis One-Pager + # ────────────────────────────────────────────── + - template: strategic-analysis-one-pager + marketplace_adaptation: + structural_changes: + - "Split 'Market' section into Supply Market and Demand Market with separate sizing, dynamics, and trends." + - "Add 'Liquidity Status' section: supply liquidity, demand fill rate, supply-demand ratio by segment." + - "Replace 'Competitive Position' with 'Marketplace Position': network effects strength, multi-homing rates, disintermediation risk." + additional_fields: + - field: "GMV and Net Revenue (current period, growth rate)" + guidance: "Always show both. GMV without net revenue (and thus take rate) is incomplete." + - field: "Take Rate (current, trend, benchmark)" + guidance: "Include take rate trajectory. Expanding take rate = increasing platform value. Compressing = competitive pressure or value-add erosion." + - field: "Liquidity Metrics by Top 3 Segments" + guidance: "Show supply liquidity and demand fill rate for the three most important segments. Aggregates mask segment-level weakness." + - field: "Network Effects Evidence" + guidance: "Quantified cross-side elasticity or, at minimum, organic acquisition percentage trends for both sides." + framing_notes: > + The strategic narrative for a marketplace must answer: 'Why is this marketplace + the natural meeting point for this supply and this demand?' Position the + marketplace as infrastructure, not intermediary. Intermediaries get + disintermediated. Infrastructure becomes essential. + + # ────────────────────────────────────────────── + # 2. Decision Rationale Memo + # ────────────────────────────────────────────── + - template: decision-rationale-memo + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Impact Analysis' section for every major decision: what is the expected impact on supply, demand, and platform economics?" + - "Add 'Reversibility Assessment' — marketplace decisions (take rate changes, policy changes) may be irreversible if they trigger supply churn." + additional_fields: + - field: "Supply-Side Impact (expected effect on supply churn, supply NPS, supply economics)" + guidance: "Every major marketplace decision affects supply. Quantify the expected impact." + - field: "Demand-Side Impact (expected effect on demand fill rate, demand repeat rate, demand NPS)" + guidance: "Every major marketplace decision affects demand. Quantify the expected impact." + - field: "Disintermediation Risk (does this decision increase or decrease the incentive to transact off-platform?)" + guidance: "Take rate increases, fee changes, and policy restrictions all affect disintermediation incentives." + framing_notes: > + Marketplace decisions are never single-sided. The memo must demonstrate + that the decision-maker considered impact on both sides and chose the + option with the best cross-side outcome, not just the best outcome + for one constituency. + + # ────────────────────────────────────────────── + # 3. Competitive Landscape Brief + # ────────────────────────────────────────────── + - template: competitive-landscape-brief + marketplace_adaptation: + structural_changes: + - "Organise competitors by competitive dimension: Supply-Side Competitors (competing for same supply), Demand-Side Competitors (competing for same demand), Full-Stack Competitors (competing on both sides), and Substitutes (non-marketplace alternatives)." + - "Add 'Multi-Homing Analysis': for each competitor, what percentage of your supply and demand also uses their platform?" + - "Add 'Side-Specific Vulnerability Map': which side is most at risk from which competitor?" + additional_fields: + - field: "Competitor Take Rates" + guidance: "Comparison of take rate structures across competitors. Higher take rate is defensible only with proportionally higher value-add." + - field: "Competitor Liquidity Estimates" + guidance: "Estimated supply liquidity and demand fill rate for each major competitor. A competitor with better liquidity in your core segment is an existential threat." + - field: "Multi-Homing Rates" + guidance: "Percentage of your supply and demand that also uses each competitor. >50% multi-homing = low defensibility on that side." + - field: "Disintermediation Tools" + guidance: "Any tools, platforms, or behaviours that enable your matched pairs to bypass marketplaces entirely." + framing_notes: > + Marketplace competition is asymmetric. A competitor may attack only your + supply side, only your demand side, or a specific category. The brief + must map threats per side and per segment, not present competitors as + undifferentiated rivals in a single landscape. + + # ────────────────────────────────────────────── + # 4. Market Opportunity Summary + # ────────────────────────────────────────────── + - template: market-opportunity-summary + marketplace_adaptation: + structural_changes: + - "Replace single TAM/SAM/SOM with dual-sided market sizing: Supply-Side TAM (total value of supply that could transact through a marketplace) and Demand-Side TAM (total demand spend in the category)." + - "Add 'Liquidity-Adjusted SAM': the portion of TAM where supply and demand overlap geographically and categorically — the actual addressable market for matching." + - "Add 'Take Rate-Adjusted Revenue Opportunity': SAM x estimated take rate = addressable revenue, not addressable GMV." + additional_fields: + - field: "Supply-Side TAM and Growth Rate" + guidance: "Total addressable supply in the category — existing supply that could list on a marketplace + latent supply that a marketplace could unlock." + - field: "Demand-Side TAM and Growth Rate" + guidance: "Total demand spend in the category — existing marketplace spend + offline spend that could migrate online + new demand a marketplace could create." + - field: "Liquidity-Adjusted SAM" + guidance: "The intersection of supply availability and demand presence. A marketplace in home services has no SAM in regions where supply exists but demand does not, or vice versa." + - field: "Revenue TAM (SAM x Take Rate)" + guidance: "The marketplace's revenue opportunity is GMV x take rate. Show the revenue TAM, not just the GMV TAM." + framing_notes: > + Marketplace TAMs are frequently overstated because they cite the entire + category spend without adjusting for the portion that could actually flow + through a marketplace. The brief must show the path from total category + spend to marketplace-addressable spend to marketplace revenue. + + # ────────────────────────────────────────────── + # 5. Fundraising Deck Outline + # ────────────────────────────────────────────── + - template: fundraising-deck-outline + marketplace_adaptation: + structural_changes: + - "Add dedicated 'Network Effects' slide: quantified cross-side elasticity, organic acquisition trends, and the specific mechanism by which each side's growth benefits the other." + - "Add 'Liquidity and Defensibility' slide: supply liquidity, demand fill rate, multi-homing rates, disintermediation countermeasures." + - "Replace 'Unit Economics' slide with 'Per-Transaction Economics': AOV, take rate, contribution margin per transaction, blended CAC, payback in transactions." + - "Add 'Two-Sided Flywheel' slide: visual diagram showing the reinforcing loops between supply growth, demand growth, and platform value." + additional_fields: + - field: "GMV and Net Revenue (show both on the same chart)" + guidance: "Investors will compute take rate regardless. Show it transparently." + - field: "Cohort Repeat Rates (supply and demand separately)" + guidance: "Retention is the strongest PMF signal. Show monthly cohort curves for both sides." + - field: "Organic Acquisition Mix (supply and demand separately)" + guidance: "Organic >40% on either side is strong evidence of network effects in action." + - field: "Per-Transaction Contribution Margin Stack" + guidance: "Waterfall from AOV through take rate revenue to contribution margin, showing each variable cost." + - field: "Tipping Point Evidence" + guidance: "If any market has tipped (organic growth > paid, both sides' repeat rates stable), show it. This is the strongest possible fundraising signal." + framing_notes: > + The marketplace fundraising narrative has three beats: (1) This supply and + this demand need to find each other and currently cannot. (2) Our platform + creates the match with enough value-add to justify a take rate. (3) Network + effects make this business more defensible and more efficient as it grows. + Every slide should reinforce one of these three beats. + + # ────────────────────────────────────────────── + # 6. Investor Update Email + # ────────────────────────────────────────────── + - template: investor-update-email + marketplace_adaptation: + structural_changes: + - "Replace single 'Revenue' metric with GMV, Net Revenue, and Take Rate as the headline trio." + - "Add 'Supply Health' section: supply churn, new supply added, supply liquidity, supply NPS." + - "Add 'Demand Health' section: demand repeat rate, demand fill rate, organic demand %." + - "Add 'Marketplace Health' section: contribution margin per transaction, disintermediation rate, marketplace quality score." + additional_fields: + - field: "GMV, Net Revenue, Take Rate" + guidance: "The three numbers that define marketplace financial health. All three, every update." + - field: "Supply-Side Metrics (3-5 key numbers)" + guidance: "Supply liquidity, supply churn, new supply added, supply NPS. Investors increasingly evaluate supply health as a leading indicator." + - field: "Demand-Side Metrics (3-5 key numbers)" + guidance: "Demand repeat rate, demand fill rate, organic demand %, demand CAC. The demand-side health report." + - field: "Key Marketplace Insight" + guidance: "One observation about marketplace dynamics — a cross-side effect observed, a liquidity milestone reached, a disintermediation countermeasure deployed." + framing_notes: > + Marketplace investor updates must demonstrate that both sides of the + marketplace are healthy and that the flywheel is working. Investors who + only see demand metrics will assume the supply side is problematic. Show + both sides proactively. + + # ────────────────────────────────────────────── + # 7. Unit Economics Snapshot + # ────────────────────────────────────────────── + - template: unit-economics-snapshot + marketplace_adaptation: + structural_changes: + - "Replace subscription-based unit economics with per-transaction economics as the primary frame." + - "Add 'Transaction Economics Waterfall': AOV -> Take Rate Revenue -> minus Payment Processing -> minus T&S Cost -> minus Support Cost -> minus Supply Incentive = Contribution Margin." + - "Split CAC into Supply-Side CAC, Demand-Side CAC, and Blended CAC (per matched transaction)." + - "Replace LTV with LTV per side: Supply LTV (lifetime take rate revenue from one supplier) and Demand LTV (lifetime take rate revenue from one buyer)." + - "Add 'Marketplace-Specific Metrics': supply liquidity, demand fill rate, disintermediation rate, organic acquisition % per side." + additional_fields: + - field: "AOV (Average Order Value)" + guidance: "The starting point of marketplace unit economics. Everything flows from transaction value." + - field: "Take Rate and Take Rate Revenue per Transaction" + guidance: "AOV x Take Rate = per-transaction revenue before variable costs." + - field: "Transaction Cost Stack" + guidance: "Payment processing (typically 2.5-3.5%), T&S cost, customer support allocation, supply incentives, fraud losses." + - field: "Contribution Margin per Transaction" + guidance: "Take rate revenue minus all variable transaction costs. Must be positive or trending positive." + - field: "Supply-Side LTV and Supply-Side CAC" + guidance: "LTV = expected lifetime transactions x contribution margin per transaction. CAC = supply acquisition cost. LTV:CAC per side." + - field: "Demand-Side LTV and Demand-Side CAC" + guidance: "Same calculation for demand side. Often shows very different economics from supply side." + - field: "Blended CAC per Matched Transaction" + guidance: "The true cost of creating one incremental matched transaction, considering both sides' acquisition costs." + framing_notes: > + Marketplace unit economics are per-transaction, not per-subscription. + The fundamental question is not 'what is the lifetime value of a customer' + but 'does each transaction generate positive contribution margin, and how + many transactions does it take to pay back acquisition cost on each side?' + + # ────────────────────────────────────────────── + # 8. Cap Table Summary + # ────────────────────────────────────────────── + - template: cap-table-summary + marketplace_adaptation: + structural_changes: + - "Add 'Supply-Side Equity or Revenue Share' section if the marketplace has offered equity, revenue share, or profit participation to key supply-side participants." + - "Add note on marketplace-specific valuation considerations: GMV multiple vs net revenue multiple, and why the distinction matters." + additional_fields: + - field: "Valuation Basis (GMV multiple or net revenue multiple)" + guidance: "Marketplace valuations are often quoted as GMV multiples, which overstate value when take rates are low. Show net revenue multiple for clarity." + framing_notes: > + Cap table structure for marketplaces is generally standard, but valuation + discussions require clarity on whether multiples apply to GMV or net revenue. + A 1x GMV multiple with a 15% take rate is equivalent to a ~6.7x net revenue + multiple. Investors and founders must speak the same language. + + # ────────────────────────────────────────────── + # 9. Due Diligence Checklist + # ────────────────────────────────────────────── + - template: due-diligence-checklist + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace-Specific Due Diligence' section with supply-side, demand-side, and platform health checks." + - "Add 'Network Effects Verification' section: how to validate claimed network effects with data." + - "Add 'Regulatory Risk Assessment' for marketplace-specific regulations (labor classification, marketplace liability, data portability)." + additional_fields: + - field: "Supply-Side Health Check" + guidance: "Supply churn by cohort, supply concentration (top 10% share), supply NPS, supply economics (earnings per active period), supply liquidity trend." + - field: "Demand-Side Health Check" + guidance: "Demand repeat rate by cohort, demand concentration, demand NPS, demand fill rate trend, organic demand %." + - field: "Network Effects Data Request" + guidance: "Cross-side elasticity calculations, organic acquisition trends, CAC trend as marketplace scales. Positive network effects should produce declining CAC at scale." + - field: "Disintermediation Risk Assessment" + guidance: "Transaction type analysis, post-match retention data, off-platform transaction estimates, value-add justification for take rate." + - field: "Take Rate Sustainability" + guidance: "Take rate trajectory, competitive take rate comparison, supply-side willingness to pay analysis, value-add inventory supporting current take rate." + - field: "Regulatory Exposure" + guidance: "Labour classification risk (if supply resembles employees), marketplace liability (product safety, service quality), consumer protection compliance, cross-border regulatory differences." + framing_notes: > + Marketplace due diligence must verify that network effects are real (not + just claimed), that both sides are healthy (not just demand), that unit + economics work per transaction (not just per quarter in aggregate), and + that the take rate is sustainable (not just current). The most common + due diligence failure is accepting GMV growth as a proxy for marketplace + health without examining side-specific metrics. + + # ────────────────────────────────────────────── + # 10. Exit Scenario Analysis + # ────────────────────────────────────────────── + - template: exit-scenario-analysis + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace Acquirer Analysis': strategic acquirers typically want one side (supply base or demand base), not the platform technology. Identify which side is the acquisition asset." + - "Add 'Network Effects Portability': do network effects transfer to an acquirer, or are they specific to the marketplace brand and trust infrastructure?" + - "Add 'Marketplace-Specific Valuation Multiples': historical marketplace M&A and IPO multiples (net revenue, not GMV)." + additional_fields: + - field: "Primary Acquisition Asset (supply base, demand base, technology, or data)" + guidance: "Which component of the marketplace is most valuable to a strategic acquirer? Supply-side relationships, demand-side user base, matching technology, or transaction data?" + - field: "Marketplace M&A Comps" + guidance: "Recent marketplace acquisitions and their valuation multiples. Use net revenue multiples, not GMV." + - field: "Side-Specific Transfer Risk" + guidance: "What happens to supply and demand if the marketplace changes ownership? Assess retention risk per side." + framing_notes: > + Marketplace exits are complicated by the two-sided nature: an acquirer + may want the supply base but not the demand experience, or vice versa. + The exit analysis must identify which side is the primary asset and + assess whether that side is transferable. + +# ============================================================ +# BOARD TEMPLATES (7) +# ============================================================ + +board_templates: + + # ────────────────────────────────────────────── + # 11. Board Meeting Agenda + # ────────────────────────────────────────────── + - template: board-meeting-agenda + marketplace_adaptation: + structural_changes: + - "Add standing agenda items: 'Supply-Side Health Report' and 'Demand-Side Health Report' as separate sections." + - "Add 'Marketplace Dynamics' agenda section: liquidity metrics, network effects updates, competitive landscape per side." + - "Add 'Trust & Safety Update' as a standing board item — T&S is a board-level concern for marketplaces." + additional_fields: + - field: "Supply Health Dashboard (5 metrics)" + guidance: "Supply liquidity, supply churn, new supply growth, supply NPS, ARPU (supply)." + - field: "Demand Health Dashboard (5 metrics)" + guidance: "Demand fill rate, demand repeat rate, demand churn, organic demand %, ARPU (demand)." + - field: "Marketplace Economics Update" + guidance: "GMV, net revenue, take rate, contribution margin per transaction, blended CAC." + - field: "Trust & Safety Report" + guidance: "Dispute rate, fraud rate, T&S cost per transaction, safety incidents (if any), regulatory updates." + framing_notes: > + Board meetings for marketplaces must provide equal visibility into both + sides. Boards that see only demand metrics or only financial metrics are + governing blind. Supply health is a leading indicator that boards must + monitor proactively. + + # ────────────────────────────────────────────── + # 12. Quarterly Strategic Review + # ────────────────────────────────────────────── + - template: quarterly-strategic-review + marketplace_adaptation: + structural_changes: + - "Structure the strategic review around three pillars: Supply Strategy, Demand Strategy, and Platform Strategy." + - "Add 'Liquidity Map' showing supply liquidity and demand fill rate by segment, geography, and category." + - "Add 'Network Effects Assessment' — quarterly measurement of cross-side impact and organic acquisition trends." + additional_fields: + - field: "Supply Strategy Review" + guidance: "Supply growth, quality trends, churn analysis, competitive supply dynamics, supply-side investment ROI." + - field: "Demand Strategy Review" + guidance: "Demand acquisition, retention trends, channel mix, competitive demand dynamics, demand-side investment ROI." + - field: "Platform Strategy Review" + guidance: "Matching quality improvements, T&S enhancements, take rate analysis, technology roadmap." + - field: "Liquidity Heat Map" + guidance: "Visual representation of liquidity health across segments. Green = tipped. Yellow = building. Red = failing." + - field: "Cross-Side Elasticity Trend" + guidance: "Quarter-over-quarter measurement: is adding supply producing more demand engagement, and vice versa?" + framing_notes: > + The quarterly review must demonstrate strategic coherence across both + sides. If supply strategy and demand strategy are not mutually reinforcing, + the review should surface this misalignment and resolve it. + + # ────────────────────────────────────────────── + # 13. Risk Assessment Brief + # ────────────────────────────────────────────── + - template: risk-assessment-brief + marketplace_adaptation: + structural_changes: + - "Organise risks into four categories: Supply-Side Risks, Demand-Side Risks, Platform Risks, and Regulatory Risks." + - "Add 'Cascade Risk Analysis' — how does a risk on one side cascade to the other?" + - "Add marketplace-specific risk categories: disintermediation risk, liquidity collapse risk, quality death spiral risk, regulatory reclassification risk." + additional_fields: + - field: "Supply-Side Risk Register" + guidance: "Supply concentration, supply churn trend, competitor supply poaching, regulatory risk (labor classification), supply-side activist movements." + - field: "Demand-Side Risk Register" + guidance: "Demand concentration, demand-side competitive alternatives, trust incidents, regulatory risk (consumer protection)." + - field: "Platform Risk Register" + guidance: "Disintermediation trend, technology disruption (AI matching, blockchain payments), data breach exposure, algorithmic liability." + - field: "Cascade Risk Map" + guidance: "For each top-5 risk: if this materialises, what is the second-order effect on the other side?" + framing_notes: > + Marketplace risks are interconnected through the two-sided flywheel. A + supply-side risk that triggers supply churn cascades to demand through + reduced selection and fill rate. Risk assessment must map these cascades + explicitly, not treat each risk as independent. + + # ────────────────────────────────────────────── + # 14. Change Initiative Proposal + # ────────────────────────────────────────────── + - template: change-initiative-proposal + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Impact Assessment' section for every proposed change." + - "Add 'Side-Specific Change Management Plan' — how will supply be informed and supported through the change? How will demand?" + - "Add 'Rollback Criteria' — what metrics on either side would trigger reversal of the change?" + additional_fields: + - field: "Supply-Side Impact and Communication Plan" + guidance: "How does this change affect supply economics, experience, or policies? How will supply learn about it? When?" + - field: "Demand-Side Impact and Communication Plan" + guidance: "How does this change affect demand experience, pricing, or trust? How will demand learn about it?" + - field: "Rollback Triggers" + guidance: "Define metrics thresholds that would trigger change reversal: supply churn spike, demand conversion drop, liquidity decline." + framing_notes: > + Marketplace change initiatives must be evaluated for their cross-side + impact and managed with side-specific communication plans. Supply-side + changes that affect livelihood require more advance notice, more + transparency, and more support than demand-side UX changes. + + # ────────────────────────────────────────────── + # 15. CEO Succession Brief + # ────────────────────────────────────────────── + - template: ceo-succession-brief + marketplace_adaptation: + structural_changes: + - "Add 'Two-Sided Leadership Competency' as a required criterion: successor must demonstrate understanding of and empathy for both sides." + - "Add 'Marketplace-Specific Experience' evaluation: has the candidate operated a marketplace, managed supply-demand balance, and navigated network effects?" + additional_fields: + - field: "Two-Sided Competency Assessment" + guidance: "Evaluate candidate's understanding of supply-side economics, demand-side experience, platform dynamics, and the ability to hold both perspectives simultaneously." + - field: "Marketplace Operator Track Record" + guidance: "Prior experience managing two-sided platforms, liquidity challenges, take rate decisions, and trust infrastructure." + framing_notes: > + Marketplace CEO succession is unusually sensitive because the CEO + must maintain trust with both sides simultaneously. A CEO perceived + as favouring one side can trigger rapid deterioration on the other. + + # ────────────────────────────────────────────── + # 16. Regulatory Compliance Update + # ────────────────────────────────────────────── + - template: regulatory-compliance-update + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace-Specific Regulatory Landscape' with categories: labour classification, marketplace liability, consumer protection, data portability, competition/antitrust." + - "Add 'Jurisdictional Matrix' for marketplace-specific regulations across operating geographies." + additional_fields: + - field: "Labour Classification Status" + guidance: "Status of supply-side participant classification (independent contractor vs employee) across jurisdictions. Regulatory changes here fundamentally alter cost structure." + - field: "Marketplace Liability Exposure" + guidance: "Liability for supply-side quality, product safety, service outcomes. Which jurisdictions impose marketplace liability?" + - field: "Data Portability Requirements" + guidance: "Requirements for supply-side and demand-side data portability (GDPR, DMA, state-level regulations)." + framing_notes: > + Marketplace regulation is evolving rapidly across jurisdictions. + Labour classification, platform liability, and data portability + are the three regulatory vectors that can fundamentally alter + marketplace economics. Board-level visibility is essential. + + # ────────────────────────────────────────────── + # 17. Compensation Review Brief + # ────────────────────────────────────────────── + - template: compensation-review-brief + marketplace_adaptation: + structural_changes: + - "Add marketplace-specific roles to compensation benchmarking: Head of Supply Operations, Head of Trust & Safety, Head of Marketplace Economics." + - "Add note on supply-side incentive structures (guaranteed minimums, bonuses, equity participation) if applicable." + additional_fields: + - field: "Marketplace-Specific Role Benchmarks" + guidance: "Supply ops, T&S, and marketplace economics leadership are specialised roles. Benchmark against marketplace-native companies, not general tech." + - field: "Supply-Side Incentive Costs" + guidance: "If the marketplace offers supply-side incentives (guaranteed earnings, signup bonuses), include as compensation-adjacent cost." + framing_notes: > + Marketplace companies require specialised talent in supply operations, + trust and safety, and marketplace economics. These roles command + premiums because the talent pool is smaller and the domain expertise + is not transferable from single-sided businesses. + +# ============================================================ +# TEAM TEMPLATES (13) +# ============================================================ + +team_templates: + + # ────────────────────────────────────────────── + # 18. Team Health Check + # ────────────────────────────────────────────── + - template: team-health-check + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Alignment' health dimension: do supply ops and demand growth teams have aligned strategies and effective coordination?" + - "Add 'Marketplace Specialisation' dimension: does the team have dedicated supply, demand, and T&S functions, or are roles blurred?" + additional_fields: + - field: "Supply-Demand Team Alignment Score" + guidance: "Rate 1-5: How well do supply ops and demand growth teams coordinate strategy, share data, and resolve conflicts?" + - field: "Marketplace Role Coverage" + guidance: "Assess whether supply ops lead, demand growth lead, T&S lead, and marketplace economics lead are filled and effective." + framing_notes: > + Marketplace team health includes a dimension that single-sided companies + lack: the supply-demand coordination function. Without deliberate + cross-side alignment, marketplace teams naturally drift into side-specific + silos that optimise locally and suboptimise globally. + + # ────────────────────────────────────────────── + # 19. Action Plan + # ────────────────────────────────────────────── + - template: action-plan + marketplace_adaptation: + structural_changes: + - "Tag each action item with its target side: [Supply], [Demand], [Platform], or [Cross-Side]." + - "Add 'Cross-Side Dependencies' column: does this action depend on or affect the other side?" + - "Add 'Liquidity Impact' column: expected impact on supply liquidity or demand fill rate." + additional_fields: + - field: "Side Tag for Each Action" + guidance: "[Supply], [Demand], [Platform], or [Cross-Side]. Ensures actions are balanced and dependencies are visible." + - field: "Cross-Side Dependency Flag" + guidance: "For each action: does success depend on a corresponding action on the other side?" + - field: "Liquidity Impact Estimate" + guidance: "Expected impact on supply liquidity, demand fill rate, or both. Actions with negative liquidity impact require justification." + framing_notes: > + Every action plan in a marketplace must make cross-side dependencies + visible. An action to increase supply without a corresponding demand + action reduces supply liquidity. An action to drive demand without + supply readiness degrades fill rate. Tag and cross-reference. + + # ────────────────────────────────────────────── + # 20. Retrospective Template + # ────────────────────────────────────────────── + - template: retrospective-template + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Effects' reflection: did actions on one side produce unexpected effects on the other?" + - "Add 'Supply-Side Voice' section: what did supply-side participants experience during this period?" + - "Add 'Demand-Side Voice' section: what did demand-side participants experience?" + additional_fields: + - field: "Unintended Cross-Side Effects" + guidance: "Reflect on whether any initiative for one side had unintended consequences for the other. Marketplace operations are full of second-order effects." + - field: "Supply-Side Feedback Summary" + guidance: "What did supply tell us this period — through support tickets, NPS, churn interviews, community forums?" + - field: "Demand-Side Feedback Summary" + guidance: "What did demand tell us — through NPS, reviews, support contacts, repeat behaviour?" + framing_notes: > + Marketplace retrospectives must include both sides' perspectives. A + retrospective that celebrates demand growth without noting the + supply-side strain that growth produced is dangerously incomplete. + + # ────────────────────────────────────────────── + # 21. New Initiative Brief + # ────────────────────────────────────────────── + - template: new-initiative-brief + marketplace_adaptation: + structural_changes: + - "Add 'Side-Specific Hypothesis' section: which side does this initiative primarily serve, and what is the expected cross-side effect?" + - "Add 'Liquidity Impact Projection': how does this initiative affect supply liquidity and demand fill rate?" + - "Add 'Cold Start Plan' (for new category/geography initiatives): which side first, how to achieve initial liquidity, what is the tipping point?" + additional_fields: + - field: "Primary Side Served" + guidance: "Every initiative primarily serves one side or the platform. Name it explicitly." + - field: "Cross-Side Benefit Hypothesis" + guidance: "How does serving the primary side benefit the other? If there is no cross-side benefit, question the initiative's marketplace value." + - field: "Cold Start Sequence (if expanding to new segment)" + guidance: "Which side acquired first, how many units needed on each side for minimum viable liquidity, timeline to tipping point." + framing_notes: > + New marketplace initiatives must specify their side-specific hypothesis + and cross-side benefit. Initiatives that serve only one side without + benefiting the other are legitimate only if that side is the current + binding constraint. + + # ────────────────────────────────────────────── + # 22. Offsite Planning Guide + # ────────────────────────────────────────────── + - template: offsite-planning-guide + marketplace_adaptation: + structural_changes: + - "Include 'Supply-Side Immersion' session: team members spend time understanding supply-side experience (shadow a supplier, review support tickets, analyse earnings data)." + - "Include 'Supply-Demand Balance Workshop' session: cross-functional exercise to identify and resolve supply-demand strategic tensions." + additional_fields: + - field: "Supply Immersion Activity" + guidance: "Structured activity where every team member experiences the supply side: list a product, provide a service, answer supply support tickets." + - field: "Demand Immersion Activity" + guidance: "Structured activity where every team member experiences the demand side: complete a purchase journey, test competitor alternatives, submit a dispute." + - field: "Cross-Side Strategy Alignment Session" + guidance: "Facilitated session where supply ops and demand growth teams present their strategies, identify conflicts, and resolve them." + framing_notes: > + Marketplace offsites should immerse the team in both sides of the + experience. Most marketplace teams understand the demand side intuitively + (they are demand-side users in other marketplaces) but have limited + first-person experience of the supply side. + + # ────────────────────────────────────────────── + # 23. Hiring Scorecard + # ────────────────────────────────────────────── + - template: hiring-scorecard + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace Competency' evaluation dimension for all leadership and senior roles." + - "Add marketplace-specific role scorecards: Supply Operations Lead, Demand Growth Lead, Trust & Safety Lead, Marketplace Economics Lead." + additional_fields: + - field: "Marketplace Competency Score" + guidance: "Rate candidate's understanding of two-sided dynamics, network effects, liquidity, take rate economics, and cross-side trade-offs." + - field: "Side-Specific Domain Expertise" + guidance: "For supply roles: supply-side operations experience. For demand roles: demand-side growth experience. For platform roles: matching and T&S experience." + framing_notes: > + Hiring for marketplace-specific roles (supply ops, T&S, marketplace + economics) requires domain expertise that general startup hiring + templates do not evaluate. Add marketplace competency as an explicit + scoring dimension. + + # ────────────────────────────────────────────── + # 24. Culture Values Document + # ────────────────────────────────────────────── + - template: culture-values-document + marketplace_adaptation: + structural_changes: + - "Add value principle: 'Both Sides Matter' — the marketplace serves supply and demand equally. Neither side is a resource to be exploited." + - "Add value principle: 'Trust is Infrastructure' — marketplace trust is built through design, not assumed through good intentions." + additional_fields: + - field: "Two-Sided Stewardship Value" + guidance: "Articulate the company's commitment to balanced treatment of both sides. Decisions that benefit one side at the other's expense require explicit justification." + - field: "Trust-First Value" + guidance: "Articulate trust as the marketplace's most valuable asset — more important than growth, revenue, or efficiency." + framing_notes: > + Marketplace culture must explicitly articulate the commitment to both + sides. Without this, culture defaults to optimising for whichever side + the leadership team instinctively identifies with — typically demand. + + # ────────────────────────────────────────────── + # 25. One-on-One Template + # ────────────────────────────────────────────── + - template: one-on-one-template + marketplace_adaptation: + structural_changes: + - "Add marketplace-context question for supply-side team members: 'What are you hearing from suppliers this week?'" + - "Add marketplace-context question for demand-side team members: 'What are you hearing from buyers this week?'" + - "Add cross-side awareness question for all team members: 'How is the other side of the marketplace doing, from your perspective?'" + additional_fields: + - field: "Supply-Side Pulse" + guidance: "For supply ops team: what is the current supply-side sentiment? For others: what do you know about supply health?" + - field: "Demand-Side Pulse" + guidance: "For demand team: what is the current demand-side sentiment? For others: what do you know about demand health?" + framing_notes: > + One-on-ones in a marketplace company should include cross-side awareness + questions. Every team member should have a current, if rough, sense of + how the other side of the marketplace is doing. + + # ────────────────────────────────────────────── + # 26. Project Kickoff Document + # ────────────────────────────────────────────── + - template: project-kickoff-document + marketplace_adaptation: + structural_changes: + - "Add 'Side Impact Assessment' to every project kickoff: which side does this project primarily serve, and what is the expected cross-side effect?" + - "Add 'Liquidity Guard Rails': metrics thresholds on the non-primary side that must be maintained during the project." + additional_fields: + - field: "Primary Side" + guidance: "[Supply] / [Demand] / [Platform] — explicitly name which side this project serves." + - field: "Cross-Side Impact" + guidance: "Expected positive or negative impact on the other side. If negative, what mitigation is planned?" + - field: "Liquidity Constraints" + guidance: "What supply liquidity and demand fill rate thresholds must be maintained during execution?" + framing_notes: > + Every marketplace project should state its primary side and cross-side + impact. Projects that improve one side while harming the other need + explicit guard rails to prevent marketplace damage. + + # ────────────────────────────────────────────── + # 27. Incident Postmortem + # ────────────────────────────────────────────── + - template: incident-postmortem + marketplace_adaptation: + structural_changes: + - "Add 'Side-Specific Impact' section: how did the incident affect supply? How did it affect demand? How did it affect marketplace trust?" + - "Add 'Cross-Side Cascade Analysis': did the incident on one side produce effects on the other?" + - "Add 'Trust Repair Actions' section specific to marketplace trust incidents." + additional_fields: + - field: "Supply-Side Impact" + guidance: "Quantify: supply churn attributed to incident, supply NPS impact, supply earnings impact." + - field: "Demand-Side Impact" + guidance: "Quantify: demand churn attributed to incident, demand NPS impact, demand trust impact." + - field: "Trust Repair Plan" + guidance: "For trust-affecting incidents: what specific actions will rebuild trust on the affected side(s)? Timeline?" + framing_notes: > + Marketplace incidents often affect both sides, even when the incident + originates on one side. A supply-side quality incident affects demand + trust. A demand-side fraud incident affects supply's willingness to + participate. The postmortem must trace both directions. + + # ────────────────────────────────────────────── + # 28. Feedback 360 Template + # ────────────────────────────────────────────── + - template: feedback-360-template + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Awareness' evaluation dimension: does this person understand and consider both sides of the marketplace in their work?" + - "For supply-side roles: add feedback from supply-side participants (supplier advisory board, key accounts)." + - "For demand-side roles: add feedback from demand-side user research or NPS data." + additional_fields: + - field: "Cross-Side Awareness Score" + guidance: "Rate 1-5: How well does this person consider the other side's perspective when making decisions?" + - field: "External Stakeholder Feedback (supply or demand)" + guidance: "For supply-facing roles: include supply-side feedback. For demand-facing roles: include demand-side feedback." + framing_notes: > + In a marketplace company, cross-side awareness is a leadership + competency. Every manager and above should be evaluated on their ability + to consider both sides, not just their functional constituency. + + # ────────────────────────────────────────────── + # 29. Role Description Template + # ────────────────────────────────────────────── + - template: role-description-template + marketplace_adaptation: + structural_changes: + - "Add marketplace-specific role templates: Supply Operations Manager, Demand Growth Manager, Trust & Safety Manager, Marketplace Economist, Category Manager." + - "Add 'Side Alignment' field indicating which side of the marketplace this role primarily serves." + additional_fields: + - field: "Side Alignment" + guidance: "[Supply] / [Demand] / [Platform] / [Cross-Side] — which side does this role primarily serve?" + - field: "Marketplace Competency Requirements" + guidance: "For marketplace-specific roles: required understanding of two-sided dynamics, network effects, liquidity management." + marketplace_specific_roles: + - name: "Supply Operations Manager" + side: supply + key_responsibilities: ["Supply acquisition and onboarding", "Supply quality management", "Supply economics analysis and optimization", "Supply community management", "Supply churn analysis and intervention"] + key_metrics: ["Supply liquidity", "Supply churn", "Supply NPS", "New supply onboarded", "Supply quality score"] + - name: "Demand Growth Manager" + side: demand + key_responsibilities: ["Demand acquisition across channels", "Demand retention and repeat rate optimization", "Demand-side UX and conversion", "Brand marketing", "Organic demand growth"] + key_metrics: ["Demand fill rate", "Demand repeat rate", "Organic demand %", "Demand CAC", "Demand NPS"] + - name: "Trust & Safety Manager" + side: platform + key_responsibilities: ["Fraud detection and prevention", "Dispute resolution", "Identity verification", "Content moderation", "Safety incident response"] + key_metrics: ["Dispute rate", "Fraud rate", "T&S cost per transaction", "Resolution time", "Marketplace quality score"] + - name: "Marketplace Economist" + side: platform + key_responsibilities: ["Take rate analysis and optimization", "Pricing strategy", "Supply-demand balance management", "Incentive design", "Network effects measurement"] + key_metrics: ["Take rate", "Contribution margin per transaction", "Cross-side elasticity", "Supply-demand ratio", "Disintermediation rate"] + framing_notes: > + Marketplace companies need roles that do not exist in single-sided + businesses. Supply Operations, Trust & Safety, and Marketplace Economics + are distinct functions that require dedicated hiring. + + # ────────────────────────────────────────────── + # 30. Meeting Notes Template + # ────────────────────────────────────────────── + - template: meeting-notes-template + marketplace_adaptation: + structural_changes: + - "Add standing sections for supply-side and demand-side updates in recurring meeting notes." + - "Tag decisions with [Supply Impact] / [Demand Impact] / [Cross-Side] flags." + additional_fields: + - field: "Supply Update" + guidance: "Brief supply-side health update in every operational meeting." + - field: "Demand Update" + guidance: "Brief demand-side health update in every operational meeting." + - field: "Decision Side-Impact Tags" + guidance: "Every decision recorded with its expected impact on supply, demand, or both." + framing_notes: > + Meeting notes in a marketplace company should always include both-side + visibility, even in meetings focused on one side. This habit prevents + decisions from being made without cross-side awareness. + +# ============================================================ +# SELF TEMPLATES (10) +# ============================================================ + +self_templates: + + # ────────────────────────────────────────────── + # 31. Decision Journal + # ────────────────────────────────────────────── + - template: decision-journal + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Trade-Off' field for every decision: what did each side gain or lose?" + - "Add 'Reversibility' assessment: can this decision be reversed if the cross-side impact is worse than expected?" + additional_fields: + - field: "Supply Impact" + guidance: "Expected and actual impact on supply-side metrics and sentiment." + - field: "Demand Impact" + guidance: "Expected and actual impact on demand-side metrics and sentiment." + - field: "Cross-Side Trade-Off Accepted" + guidance: "Explicitly state: 'This decision favours [side] at [cost to other side]. Justification: [reasoning].'" + framing_notes: > + A marketplace founder's decision journal should track cross-side + trade-offs explicitly. Over time, the journal reveals whether decisions + systematically favour one side — a pattern that predicts marketplace + instability. + + # ────────────────────────────────────────────── + # 32. Leadership Reflection + # ────────────────────────────────────────────── + - template: leadership-reflection + marketplace_adaptation: + structural_changes: + - "Add 'Which side did I spend more time on this week?' reflection question." + - "Add 'Supply-side empathy check' and 'Demand-side empathy check' prompts." + additional_fields: + - field: "Side Balance Reflection" + guidance: "Reflect on time and attention allocation between supply and demand this period." + - field: "Supply-Side Empathy Prompt" + guidance: "When did I last experience the marketplace from the supply side's perspective? What would I change?" + - field: "Demand-Side Empathy Prompt" + guidance: "When did I last experience the marketplace from the demand side's perspective? What would I change?" + framing_notes: > + Marketplace founders must regularly audit their own attention balance. + The side that receives less founder attention will eventually underperform. + + # ────────────────────────────────────────────── + # 33. Career Strategy Canvas + # ────────────────────────────────────────────── + - template: career-strategy-canvas + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace Leadership Skills' inventory: two-sided thinking, network effects intuition, supply-demand balancing, take rate strategy, trust infrastructure design." + additional_fields: + - field: "Marketplace Competency Self-Assessment" + guidance: "Rate yourself on: supply-side empathy, demand-side empathy, network effects understanding, take rate strategy, T&S management." + framing_notes: > + For marketplace founders and leaders, career development must include + marketplace-specific competencies that do not transfer from single-sided + businesses. + + # ────────────────────────────────────────────── + # 34. Weekly CEO Review + # ────────────────────────────────────────────── + - template: weekly-ceo-review + marketplace_adaptation: + structural_changes: + - "Structure weekly review around four dashboards: Supply Health, Demand Health, Platform Health, Financial Health." + - "Add 'Balance Alert' — flag if any side's metrics are diverging significantly from the other's." + additional_fields: + - field: "Supply Health (5 metrics)" + guidance: "Supply liquidity, supply churn (weekly), new supply activated, supply NPS (if measured), top supply earnings." + - field: "Demand Health (5 metrics)" + guidance: "Demand fill rate, demand repeat rate (weekly cohort), new demand activated, demand NPS (if measured), organic demand %." + - field: "Platform Health (3 metrics)" + guidance: "Contribution margin per transaction (trend), T&S incidents, match quality score." + - field: "Balance Alert" + guidance: "Flag if supply metrics and demand metrics are diverging — early warning of imbalance." + framing_notes: > + The marketplace CEO's weekly review must provide balanced visibility + into both sides. A CEO who only reviews demand metrics is governing + half a marketplace. + + # ────────────────────────────────────────────── + # 35. Founder Mental Health Check + # ────────────────────────────────────────────── + - template: founder-mental-health-check + marketplace_adaptation: + structural_changes: + - "Add marketplace-specific stress factors: the weight of managing two constituencies with competing interests, supply-side criticism, demand-side expectations, regulatory anxiety." + additional_fields: + - field: "Two-Sided Pressure Assessment" + guidance: "Marketplace founders carry the stress of two customer bases. Reflect on whether supply-side or demand-side pressure is weighing more heavily." + - field: "Policy Backlash Resilience" + guidance: "Marketplace founders regularly face vocal criticism from supply or demand. Assess your current resilience to public criticism of platform policies." + framing_notes: > + Marketplace founders face a unique psychological burden: two constituencies + whose interests sometimes conflict, and both blame the platform. Acknowledging + this dual pressure explicitly supports founder mental health. + + # ────────────────────────────────────────────── + # 36. Personal Board Tracker + # ────────────────────────────────────────────── + - template: personal-board-tracker + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace Advisor' category: specifically seek advisors with marketplace operating experience — preferably on the side you understand less." + additional_fields: + - field: "Marketplace Advisor Coverage" + guidance: "Do your advisors include: someone with supply-side operations expertise, someone with demand-side growth expertise, someone with marketplace economics background?" + framing_notes: > + A marketplace founder's personal board should include advisors who + complement the founder's natural side bias. If the founder is demand- + oriented, the advisory board needs a supply operations voice, and + vice versa. + + # ────────────────────────────────────────────── + # 37. Stakeholder Map + # ────────────────────────────────────────────── + - template: stakeholder-map + marketplace_adaptation: + structural_changes: + - "Expand stakeholder categories to include: Supply-Side Participants (segmented by tier), Demand-Side Participants (segmented by value), Supply Aggregators, Demand Channels, Regulators (marketplace-specific), Infrastructure Partners." + additional_fields: + - field: "Supply-Side Stakeholder Tiers" + guidance: "Map supply by influence and dependence: power sellers, mid-tier, long tail. Each tier has different stakeholder management needs." + - field: "Demand-Side Stakeholder Segments" + guidance: "Map demand by value and influence: high-frequency buyers, occasional buyers, influential reviewers." + - field: "Regulatory Stakeholders" + guidance: "Map marketplace-specific regulators: labour boards, consumer protection agencies, competition authorities, data protection authorities." + framing_notes: > + Marketplace stakeholder maps are inherently more complex than single- + sided business stakeholder maps because the marketplace serves two + constituencies plus its own team plus regulators with marketplace- + specific mandates. + + # ────────────────────────────────────────────── + # 38. Annual Review and Planning + # ────────────────────────────────────────────── + - template: annual-review-and-planning + marketplace_adaptation: + structural_changes: + - "Structure annual review into three pillars: Supply Year in Review, Demand Year in Review, Platform Year in Review." + - "Add 'Marketplace Maturity Assessment': has the marketplace advanced in Sarah Tavel's hierarchy (Level 1: Matches, Level 2: Retention, Level 3: Quality)?" + - "Add 'Network Effects Trajectory': are network effects strengthening, stable, or weakening year-over-year?" + additional_fields: + - field: "Supply Year in Review" + guidance: "Annual supply-side metrics: supply growth, liquidity trend, churn trend, NPS trajectory, ARPU trajectory." + - field: "Demand Year in Review" + guidance: "Annual demand-side metrics: demand growth, fill rate trend, repeat rate trend, NPS trajectory, organic demand trend." + - field: "Marketplace Maturity Level" + guidance: "Tavel hierarchy: Level 1 (matches happening), Level 2 (both sides returning), Level 3 (quality becoming a moat). Where is the marketplace now?" + - field: "Network Effects Year-Over-Year" + guidance: "Cross-side elasticity trend, organic acquisition trend, blended CAC trend. Are network effects compounding?" + framing_notes: > + The annual review for a marketplace must assess progress across all + three levels of the marketplace hierarchy. Revenue growth without + advancement up the hierarchy is growth without defensibility. + + # ────────────────────────────────────────────── + # 39. Learning Plan + # ────────────────────────────────────────────── + - template: learning-plan + marketplace_adaptation: + structural_changes: + - "Add 'Marketplace Domain Knowledge' learning category: network effects theory, marketplace economics, platform strategy, trust infrastructure design." + additional_fields: + - field: "Marketplace Knowledge Gap Assessment" + guidance: "Self-assess knowledge of: two-sided network effects, take rate optimisation, supply-demand balancing, marketplace regulatory landscape, trust and safety operations." + - field: "Recommended Marketplace Learning Sources" + guidance: "a16z marketplace content, NFX essays, Lenny's Newsletter marketplace editions, Sarah Tavel's hierarchy of marketplaces, Bill Gurley's writings on marketplace economics." + framing_notes: > + Marketplace founders should invest in marketplace-specific learning. + General business education does not cover network effects, liquidity + management, or two-sided platform dynamics with sufficient depth. + + # ────────────────────────────────────────────── + # 40. Negotiation Prep Sheet + # ────────────────────────────────────────────── + - template: negotiation-prep-sheet + marketplace_adaptation: + structural_changes: + - "Add 'Cross-Side Impact of Agreement' section: how does the negotiated outcome affect the other side of the marketplace?" + - "Add 'Precedent Risk': will this agreement set a precedent that other supply or demand participants will demand?" + additional_fields: + - field: "Cross-Side Impact" + guidance: "If negotiating with supply (take rate, terms): how does the agreement affect demand pricing, experience, or trust? If with demand: how does it affect supply economics?" + - field: "Precedent Assessment" + guidance: "Will this agreement be visible to other participants? Will they demand the same terms? What is the cost if all supply/demand receives these terms?" + - field: "Counterparty Marketplace Dependencies" + guidance: "How dependent is the counterparty on your marketplace? Multi-homing status, % of their revenue from your platform, available alternatives." + framing_notes: > + Marketplace negotiations are never bilateral — the outcome affects the + entire ecosystem. A concession to one major supplier sets a precedent + for all suppliers. A guarantee to one major buyer creates expectations + for all buyers. + +# ============================================================ +# CLIENT TEMPLATES (8) +# ============================================================ + +client_templates: + + # ────────────────────────────────────────────── + # 41. Analysis Report + # ────────────────────────────────────────────── + - template: analysis-report + marketplace_adaptation: + structural_changes: + - "For marketplace-serving consultancies: structure analysis around supply health, demand health, and platform economics." + - "Add 'Marketplace Health Dashboard' with liquidity metrics, network effects indicators, and two-sided retention." + additional_fields: + - field: "Marketplace Health Score" + guidance: "Composite score: supply liquidity, demand fill rate, both-side repeat rates, organic acquisition %, contribution margin trend." + - field: "Side-Specific Recommendations" + guidance: "Tag every recommendation with its target side: [Supply], [Demand], [Platform]." + framing_notes: > + Analysis reports for marketplace clients must demonstrate understanding + of two-sided dynamics. Generic business analysis that treats the marketplace + as a single-sided e-commerce platform will miss the most important dynamics. + + # ────────────────────────────────────────────── + # 42. Proposal Outline + # ────────────────────────────────────────────── + - template: proposal-outline + marketplace_adaptation: + structural_changes: + - "If the engagement involves marketplace strategy: structure scope around supply strategy, demand strategy, and platform optimisation." + - "Add 'Two-Sided Impact' to every proposed deliverable." + additional_fields: + - field: "Engagement Scope by Side" + guidance: "Specify which side(s) the engagement covers and what the cross-side implications are." + framing_notes: > + Proposals for marketplace engagements should demonstrate marketplace + expertise through the structure itself — separate supply and demand + workstreams with explicit cross-side integration points. + + # ────────────────────────────────────────────── + # 43. Case Study Template + # ────────────────────────────────────────────── + - template: case-study-template + marketplace_adaptation: + structural_changes: + - "Structure results section around both sides: supply-side outcomes and demand-side outcomes." + - "Add 'Network Effects Evidence' section: did the engagement produce measurable cross-side improvements?" + additional_fields: + - field: "Supply-Side Results" + guidance: "Quantified outcomes for the supply side: liquidity improvement, churn reduction, NPS change, ARPU growth." + - field: "Demand-Side Results" + guidance: "Quantified outcomes for the demand side: fill rate improvement, repeat rate change, NPS change, organic growth." + - field: "Cross-Side Impact" + guidance: "Did improvements on one side produce measurable improvements on the other? This is the network effects story." + framing_notes: > + Marketplace case studies are most compelling when they demonstrate + cross-side impact: improving one side produced measurable benefits + for the other. This is the network effects narrative in action. + + # ────────────────────────────────────────────── + # 44. Partnership Memo + # ────────────────────────────────────────────── + - template: partnership-memo + marketplace_adaptation: + structural_changes: + - "Add 'Side-Specific Partnership Impact': does this partnership affect supply acquisition, demand acquisition, or platform infrastructure?" + - "Add 'Concentration Risk Assessment': does this partnership create dependence on a single supply aggregator or demand channel?" + - "Add 'Cross-Side Value Chain': how does this partnership create value that flows to both sides?" + additional_fields: + - field: "Partnership Side Alignment" + guidance: "[Supply Partner] / [Demand Partner] / [Infrastructure Partner]. Name the primary marketplace function the partner serves." + - field: "Concentration Risk" + guidance: "If this partner were to leave, what % of supply or demand would be affected? >15% = material concentration risk." + - field: "Cross-Side Value Flow" + guidance: "How does the value this partner brings to one side flow through to benefit the other side?" + framing_notes: > + Marketplace partnerships must be evaluated for concentration risk and + cross-side value. A supply aggregator partnership that delivers volume + but concentrates power is a strategic liability. A demand channel + partnership that cannibalises organic acquisition destroys long-term value. + + # ────────────────────────────────────────────── + # 45. Project Status Update + # ────────────────────────────────────────────── + - template: project-status-update + marketplace_adaptation: + structural_changes: + - "Tag each workstream with its side alignment: [Supply], [Demand], [Platform]." + - "Add 'Cross-Side Metrics Watch' section monitoring the non-primary side during the project." + additional_fields: + - field: "Side-Tagged Workstreams" + guidance: "Every workstream identified by which side it serves." + - field: "Non-Primary Side Health" + guidance: "While focused on one side, monitor the other side's metrics for unintended degradation." + framing_notes: > + Project status updates for marketplace initiatives must include + cross-side monitoring. A project that improves demand conversion may + inadvertently stress supply capacity if not monitored. + + # ────────────────────────────────────────────── + # 46. Service Level Agreement + # ────────────────────────────────────────────── + - template: service-level-agreement + marketplace_adaptation: + structural_changes: + - "If the marketplace itself is the service: define SLAs for supply-side experience (payout timing, support response, listing approval) and demand-side experience (search availability, transaction completion, dispute resolution time)." + additional_fields: + - field: "Supply-Side SLAs" + guidance: "Payout timing, support response time, listing approval time, communication SLAs for policy changes." + - field: "Demand-Side SLAs" + guidance: "Search availability, transaction completion rate, dispute resolution time, refund processing time." + - field: "Platform SLAs" + guidance: "Uptime, matching accuracy, data accuracy, privacy compliance." + framing_notes: > + Marketplace SLAs should cover both sides of the platform experience. + Formalising supply-side SLAs (payout timing, support response) is + particularly important because supply-side service quality is often + less visible but more impactful on marketplace health. + + # ────────────────────────────────────────────── + # 47. Quarterly Business Review + # ────────────────────────────────────────────── + - template: quarterly-business-review + marketplace_adaptation: + structural_changes: + - "Structure QBR around four pillars: Supply Performance, Demand Performance, Marketplace Economics, and Strategic Outlook." + - "Add 'Liquidity Trend' section with supply liquidity and demand fill rate trends." + - "Add 'Network Effects Health' section with organic acquisition and cross-side elasticity trends." + additional_fields: + - field: "Supply Performance Review" + guidance: "Supply growth, liquidity trend, churn by tier, NPS, ARPU trajectory, quality score trend." + - field: "Demand Performance Review" + guidance: "Demand growth, fill rate trend, repeat rate by cohort, NPS, organic %, AOV trend." + - field: "Marketplace Economics" + guidance: "GMV, net revenue, take rate, contribution margin per transaction, blended CAC, LTV:CAC per side." + - field: "Network Effects Evidence" + guidance: "Organic acquisition trends, cross-side elasticity, blended CAC trajectory. Are network effects strengthening?" + framing_notes: > + The marketplace QBR must demonstrate that both sides are healthy and + that the flywheel is working. A QBR that shows strong demand metrics + without supply health data tells half the story. + + # ────────────────────────────────────────────── + # 48. Onboarding Welcome Packet + # ────────────────────────────────────────────── + - template: onboarding-welcome-packet + marketplace_adaptation: + structural_changes: + - "Create two variants: Supply-Side Onboarding Packet and Demand-Side Onboarding Packet. Each must be tailored to the side's needs, value proposition, and success criteria." + - "For supply: emphasise earnings potential, tools available, quality expectations, and support resources." + - "For demand: emphasise selection quality, trust infrastructure, guarantees, and how to get the best experience." + additional_fields: + - field: "Supply-Side Welcome Content" + guidance: "Expected earnings, how matching works, listing best practices, quality requirements, payout schedule, support channels, community access." + - field: "Demand-Side Welcome Content" + guidance: "How to search effectively, trust and safety features, guarantee policies, review system, support channels, first-purchase incentive (if applicable)." + - field: "Time-to-First-Transaction Optimisation" + guidance: "Both packets should guide the new participant toward their first completed transaction as quickly as possible." + framing_notes: > + Onboarding is where the marketplace makes its first promise to each side. + Supply-side onboarding should set realistic earnings expectations and + demonstrate platform tools. Demand-side onboarding should demonstrate + selection quality and build trust. Both should minimise time-to-first- + transaction. diff --git a/plugins/foreman/content/industry-packs/saas/saas-benchmarks.yaml b/plugins/foreman/content/industry-packs/saas/saas-benchmarks.yaml new file mode 100644 index 0000000..c2c1591 --- /dev/null +++ b/plugins/foreman/content/industry-packs/saas/saas-benchmarks.yaml @@ -0,0 +1,1332 @@ +# SaaS Industry Pack — Benchmarks +# +# 25 SaaS-specific metrics with real benchmark data sourced from public studies. +# The orchestrator surfaces these when applying quantitative skills, generating +# output templates with financial metrics, or diagnosing growth and retention issues. +# +# Primary data sources: +# - OpenView SaaS Benchmarks (2023, 2024) +# - Bessemer Cloud Index / State of the Cloud (2023, 2024) +# - KeyBanc Capital Markets SaaS Survey (2023, 2024) +# - Paddle/ProfitWell SaaS Index (2023, 2024) +# - SaaStr Annual Reports and conference data +# - Iconiq Growth / Iconiq Capital (2023) +# - Battery Ventures Cloud Software Operating Metrics (2023) +# - Tomasz Tunguz / Theory Ventures analysis +# - Jason Lemkin / SaaStr public benchmarks +# +# Benchmark tiers reflect medians and percentiles from these sources. +# "Poor" generally represents bottom quartile; "excellent" represents +# top decile among funded SaaS companies at the relevant stage. + +pack_metadata: + sector: "saas" + display_name: "SaaS" + version: "1.0.0" + description: "Benchmark data for Software-as-a-Service companies spanning + growth, retention, unit economics, efficiency, and sales metrics." + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# BENCHMARKS +# ═══════════════════════════════════════════════════════════════ + +benchmarks: + + # ───────────────────────────────────────────── + # GROWTH METRICS + # ───────────────────────────────────────────── + + - name: "Monthly Recurring Revenue (MRR)" + id: "mrr" + category: "growth" + definition: "The predictable, normalized monthly revenue from all active + subscriptions, excluding one-time fees and variable usage overages." + formula: "Sum of (monthly subscription price x active subscribers) for each plan + tier" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $10K MRR at 12 months post-launch" + signal: "Insufficient product-market fit or distribution to sustain the + business. Runway consumption outpaces revenue generation." + below_average: + value: "$10K-$50K MRR at 12 months" + signal: "Early traction but not yet at a level that demonstrates scalable + demand." + average: + value: "$50K-$150K MRR at 12 months" + signal: "Solid initial traction. Enough signal to raise a seed or Series A if + growth rate is strong." + good: + value: "$150K-$500K MRR at 12 months" + signal: "Strong product-market fit. Revenue supports hiring a small team and + investing in growth." + excellent: + value: "> $500K MRR at 12 months" + signal: "Exceptional traction. Rare at this stage — indicates viral adoption or + enterprise deal velocity." + stage_notes: + seed: "Absolute MRR matters less than trajectory. Investors look for $10K-$50K + MRR with 15%+ MoM growth." + series_a: "Typical Series A threshold has risen to $1M-$2M ARR ($83K-$167K MRR). + The bar is higher in 2024-2026 than in 2021." + series_b_plus: "Series B companies typically show $5M-$15M ARR. MRR is less + discussed — ARR becomes the standard unit." + data_sources: + - source: "OpenView SaaS Benchmarks" + year: "2024" + - source: "SaaStr Series A Benchmarks" + year: "2024" + related_metrics: [ "arr", "mom-growth-rate" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "MRR must exclude implementation fees, professional services, and + one-time charges. Blending these inflates the metric and misleads + investors." + + - name: "Annual Recurring Revenue (ARR)" + id: "arr" + category: "growth" + definition: "The annualized value of all active recurring subscription + contracts, representing the run-rate revenue the business would generate + over twelve months at its current scale." + formula: "MRR x 12 (or sum of annualized contract values for annual/multi-year + deals)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $500K ARR at Series A" + signal: "Below the threshold most institutional investors require. The company + may be pre-product-market-fit." + below_average: + value: "$500K-$1M ARR at Series A" + signal: "Borderline for fundraising. Acceptable only with exceptional growth + rate (3x+ YoY) and strong retention." + average: + value: "$1M-$3M ARR at Series A" + signal: "The current median range for Series A SaaS companies. Sufficient if + paired with 2x+ YoY growth." + good: + value: "$3M-$10M ARR at Series A" + signal: "Strong position. Multiple investor options. Demonstrates repeatable + sales motion." + excellent: + value: "> $10M ARR at Series A" + signal: "Rare and powerful. Often indicates a capital-efficient business that + delayed fundraising or a breakout product." + stage_notes: + seed: "ARR is often premature at seed. Investors focus on MRR trajectory and + qualitative PMF signals." + series_a: "Median Series A ARR has increased from ~$1M (2020) to ~$1.5M-$2.5M + (2024-2025) as markets tightened." + series_b_plus: "Series B typically requires $5M-$20M ARR. Series C: $20M-$50M+. + Growth rate expectations decrease as ARR scales." + data_sources: + - source: "Bessemer State of the Cloud" + year: "2024" + - source: "Iconiq Growth" + year: "2023" + related_metrics: [ "mrr", "mom-growth-rate" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "ARR is a forward-looking metric, not GAAP revenue. Companies with high + churn may report ARR that significantly exceeds actual realized revenue." + + - name: "Month-over-Month Growth Rate" + id: "mom-growth-rate" + category: "growth" + definition: "The percentage increase in MRR from one month to the next, + measuring the velocity of recurring revenue acquisition." + formula: "(MRR_current - MRR_previous) / MRR_previous x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 5% MoM" + signal: "Growth is stalling or the business is approaching a plateau. At early + stage, this rate is too slow to reach meaningful scale." + below_average: + value: "5-10% MoM" + signal: "Moderate growth. Sustainable but unlikely to attract venture investment + at seed or Series A." + average: + value: "10-15% MoM" + signal: "Healthy early-stage growth. At 15% MoM, MRR doubles every ~5 months." + good: + value: "15-25% MoM" + signal: "Strong traction. At 20% MoM, a $10K MRR company reaches $100K MRR in + roughly 12 months." + excellent: + value: "> 25% MoM" + signal: "Exceptional, typically unsustainable beyond a few months. Often + coincides with viral adoption or a major enterprise win." + stage_notes: + seed: "15-25% MoM expected from small base. The compounding effect matters more + than the percentage once base grows." + series_a: "MoM growth naturally decelerates. 8-15% MoM at $1M+ ARR is strong. + The absolute dollar growth matters more." + series_b_plus: "MoM becomes less meaningful. YoY growth rate (2x-3x) is the + standard measure at scale." + data_sources: + - source: "OpenView SaaS Benchmarks" + year: "2023" + - source: "Y Combinator Startup School benchmarks" + year: "2024" + related_metrics: [ "mrr", "arr" ] + related_skills: [ "growth-share-matrix", "product-life-cycle" ] + caveats: "MoM rates are noisy at low MRR. A single enterprise deal can create a + misleading spike. Use 3-month rolling average for stability." + + # ───────────────────────────────────────────── + # RETENTION METRICS + # ───────────────────────────────────────────── + + - name: "Net Revenue Retention (NRR)" + id: "nrr" + category: "retention" + definition: "The percentage of recurring revenue retained from existing + customers after accounting for expansion, contraction, and churn — the + single most important SaaS health metric." + formula: "(Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / + Starting MRR x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 90%" + signal: "The business is shrinking from its existing customer base. New sales + merely replace lost revenue — a leaky bucket with no leverage." + below_average: + value: "90-100%" + signal: "Slight net contraction or break-even on existing customers. Expansion + revenue is insufficient to offset churn." + average: + value: "100-110%" + signal: "Modest net expansion. The existing customer base is growing slowly + without additional sales effort." + good: + value: "110-130%" + signal: "Strong expansion dynamics. Each cohort grows over time. This is the + range most public SaaS companies achieve." + excellent: + value: "> 130%" + signal: "Exceptional. Companies like Snowflake, Datadog, and Twilio at their + peaks. Indicates strong usage-based or land-and-expand motion." + stage_notes: + seed: "NRR is often unmeasurable with few customers. Focus on qualitative + retention signals: do customers actively use the product and request + more?" + series_a: "NRR above 100% is a strong Series A signal. Above 120% is exceptional + and demonstrates expansion revenue motion." + series_b_plus: "Public market investors heavily weight NRR. Best-in-class public + SaaS companies cluster at 120-140%." + data_sources: + - source: "KeyBanc SaaS Survey" + year: "2024" + - source: "Bessemer Cloud Index" + year: "2024" + related_metrics: [ "grr", "ndr", "revenue-churn", "expansion-revenue-pct" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "NRR can mask underlying problems. A company with 40% logo churn and + 50% expansion from survivors still shows >100% NRR but has a fundamentally + unhealthy business." + + - name: "Gross Revenue Retention (GRR)" + id: "grr" + category: "retention" + definition: "The percentage of recurring revenue retained from existing + customers excluding any expansion — measuring pure retention before upsell + compensates for losses." + formula: "(Starting MRR - Contraction MRR - Churned MRR) / Starting MRR x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 80%" + signal: "Losing more than 20% of cohort revenue annually. The product is failing + to deliver sustained value, or pricing is misaligned." + below_average: + value: "80-85%" + signal: "Meaningful revenue erosion. Acceptable only at very early stages with + rapid iteration and small cohorts." + average: + value: "85-90%" + signal: "Typical for SMB-focused SaaS. Small businesses churn at higher rates + due to failure, budget cuts, and switching costs." + good: + value: "90-95%" + signal: "Strong retention. Indicates sticky product with real workflow + integration and switching costs." + excellent: + value: "> 95%" + signal: "Enterprise-grade retention. Common in mission-critical infrastructure + software. Very difficult to achieve in SMB." + stage_notes: + seed: "GRR data is sparse. Even 80% GRR with rapid learning and iteration is + acceptable." + series_a: "Investors increasingly scrutinize GRR alongside NRR. GRR below 85% + raises questions about product-market fit durability." + series_b_plus: "Public SaaS median GRR is ~90%. Best-in-class enterprise + companies (ServiceNow, Workday) exceed 95%." + data_sources: + - source: "KeyBanc SaaS Survey" + year: "2024" + - source: "Paddle/ProfitWell SaaS Benchmarks" + year: "2023" + related_metrics: [ "nrr", "logo-churn", "revenue-churn" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "GRR is capped at 100%. It cannot exceed 100% because it excludes + expansion. This is by design — it isolates the pure retention question." + + - name: "Logo Churn" + id: "logo-churn" + category: "retention" + definition: "The percentage of customers (logos) lost in a given period, + regardless of their revenue contribution." + formula: "Customers lost in period / Customers at start of period x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 7% monthly (> 58% annual)" + signal: "More than half the customer base turns over each year. The product is + either not delivering value or targeting the wrong segment." + below_average: + value: "4-7% monthly (38-58% annual)" + signal: "High churn typical of freemium-to-paid conversion or very low-ACV + products without strong retention hooks." + average: + value: "2-4% monthly (22-38% annual)" + signal: "Common for SMB SaaS. Each customer requires low touch, but the base + requires constant replenishment." + good: + value: "1-2% monthly (11-22% annual)" + signal: "Healthy retention. Product has meaningful switching costs and delivers + ongoing value." + excellent: + value: "< 1% monthly (< 11% annual)" + signal: "Best-in-class. Typically enterprise or mission-critical products with + deep integration and multi-year contracts." + stage_notes: + seed: "Logo churn is often high and erratic with a small customer base. A single + departure can move the rate dramatically." + series_a: "Investors expect monthly logo churn under 3-5% for SMB, under 1-2% + for mid-market, under 0.5% for enterprise." + series_b_plus: "Annual logo churn above 15% at scale is a red flag regardless of + NRR performance." + data_sources: + - source: "Paddle/ProfitWell Churn Benchmarks" + year: "2024" + - source: "Recurly Research / Subscription Economy Index" + year: "2023" + related_metrics: [ "revenue-churn", "grr", "nrr" ] + related_skills: + - net-promoter-score + caveats: "Logo churn should be segmented by customer size. Losing 100 $50/month + customers is different from losing 1 $60K/year customer. Revenue churn + provides the complementary view." + related_content: + - kind: diagnostic + ref: customer-churn-diagnosis + + - name: "Revenue Churn" + id: "revenue-churn" + category: "retention" + definition: "The percentage of MRR lost from existing customers due to + cancellations and downgrades in a given period." + formula: "(Churned MRR + Contraction MRR) / Starting MRR x 100" + unit: "percentage" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 5% monthly gross revenue churn" + signal: "Losing more than half of starting MRR annually through the existing + base. Unsustainable without extraordinary new sales." + below_average: + value: "3-5% monthly" + signal: "High revenue erosion. Growth requires aggressive new customer + acquisition just to stay flat." + average: + value: "1.5-3% monthly" + signal: "Common for SMB SaaS. Manageable but requires healthy sales pipeline to + grow." + good: + value: "0.5-1.5% monthly" + signal: "Solid retention floor. The business can grow efficiently because the + base is stable." + excellent: + value: "< 0.5% monthly" + signal: "Near-zero revenue loss. Enterprise-grade stickiness. The base becomes a + compounding asset." + stage_notes: + seed: "Revenue churn is lumpy at small scale. Track it but do not over-optimize + — focus on understanding why customers leave." + series_a: "Investors expect gross monthly revenue churn under 2% for healthy + businesses. Below 1% is exceptional." + series_b_plus: "At scale, even small revenue churn percentages represent large + absolute dollars. Net revenue churn (including expansion) matters more." + data_sources: + - source: "Paddle/ProfitWell SaaS Index" + year: "2024" + - source: "Baremetrics Open Benchmarks" + year: "2023" + related_metrics: [ "logo-churn", "grr", "nrr" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "Revenue churn can be negative when expansion exceeds losses. Negative + net revenue churn is the gold standard but should be reported as NRR, not + as a negative churn rate, to avoid confusion." + + # ───────────────────────────────────────────── + # UNIT ECONOMICS METRICS + # ───────────────────────────────────────────── + + - name: "Customer Acquisition Cost (CAC)" + id: "cac" + category: "unit-economics" + definition: "The fully loaded cost to acquire one new customer, including all + sales and marketing expense." + formula: "Total Sales & Marketing Spend in period / New Customers Acquired in + period" + unit: "currency" + direction: "lower-is-better" + benchmarks: + poor: + value: "CAC > 18 months of revenue from that customer (i.e., CAC Payback > 18 + months)" + signal: "Acquisition economics are unsustainable. The business burns cash on + every new customer and depends on very long retention to break even." + below_average: + value: "CAC Payback 12-18 months" + signal: "Expensive acquisition. Viable for enterprise SaaS with high retention + but dangerous for SMB products." + average: + value: "CAC Payback 6-12 months" + signal: "Typical for B2B SaaS. Requires at least 3+ years of customer lifetime + to generate healthy returns." + good: + value: "CAC Payback 3-6 months" + signal: "Efficient acquisition. The business can reinvest in growth aggressively + because customers pay for themselves quickly." + excellent: + value: "CAC Payback < 3 months" + signal: "Exceptional efficiency. Often indicates strong word-of-mouth, viral + loops, or product-led growth motion." + stage_notes: + seed: "CAC is often distorted — founders do the selling, and their time may not + be fully costed. Be honest about true CAC." + series_a: "Blended CAC should be calculable. Investors want to see CAC by + channel and understand which channels are scalable." + series_b_plus: "CAC should be measured by segment (SMB vs. mid-market vs. + enterprise), by channel, and by cohort vintage." + data_sources: + - source: "OpenView SaaS Benchmarks" + year: "2024" + - source: "KeyBanc SaaS Survey" + year: "2024" + related_metrics: [ "ltv", "ltv-cac-ratio", "cac-payback-period" ] + related_skills: [ "four-ps-marketing", "business-model-canvas" ] + caveats: "CAC must be fully loaded: salaries, commissions, marketing spend, + tooling, content production, events. Under-counting CAC is the most common + SaaS accounting mistake." + + - name: "Customer Lifetime Value (LTV)" + id: "ltv" + category: "unit-economics" + definition: "The total gross profit a customer generates over their entire + relationship with the company." + formula: "ARPU x Gross Margin % / Monthly Revenue Churn Rate (or ARPU x Gross + Margin % x Average Customer Lifetime in months)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "LTV < 1x CAC" + signal: "The business loses money on every customer it acquires. Without + fundamental unit economics improvement, growth accelerates losses." + below_average: + value: "LTV 1-2x CAC" + signal: "Marginal economics. Barely profitable per customer after acquisition + costs. Leaves no room for operational overhead." + average: + value: "LTV 2-3x CAC" + signal: "Approaching viability. Sufficient if growth is modest, but tight + margins constrain investment in product and expansion." + good: + value: "LTV 3-5x CAC" + signal: "Healthy unit economics. The standard target for venture-backed SaaS. + Enough margin to fund growth and R&D." + excellent: + value: "LTV > 5x CAC" + signal: "Exceptional economics. The business can afford aggressive growth + spending or generate significant free cash flow." + stage_notes: + seed: "LTV is largely theoretical at seed — insufficient data for reliable + lifetime estimates. Use conservative assumptions (24-month lifetime + max)." + series_a: "LTV calculations become credible with 12-18 months of cohort data. + Investors scrutinize the assumptions behind the number." + series_b_plus: "LTV should be segmented by customer tier and acquisition cohort. + Blended LTV masks segment-level problems." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "Tomasz Tunguz / Theory Ventures analysis" + year: "2023" + related_metrics: [ "cac", "ltv-cac-ratio", "arpu", "revenue-churn" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "LTV estimates based on low churn assumptions can be wildly optimistic. + A 1% monthly churn implies 100-month lifetime — most SaaS products do not + retain customers that long." + + - name: "LTV:CAC Ratio" + id: "ltv-cac-ratio" + category: "unit-economics" + definition: "The ratio of customer lifetime value to customer acquisition cost, + measuring the return on each dollar invested in acquisition." + formula: "LTV / CAC" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.0x" + signal: "Value destruction. Every customer acquired costs more than they will + ever generate. The business model is broken." + below_average: + value: "1.0-2.0x" + signal: "Marginal. Customers barely cover their acquisition costs. No margin for + error or overhead." + average: + value: "2.0-3.0x" + signal: "Below the standard target. Viable only with very low operational + overhead or if LTV is underestimated due to early-stage data + limitations." + good: + value: "3.0-5.0x" + signal: "The accepted SaaS benchmark. Demonstrates a sustainable business where + customer value significantly exceeds acquisition investment." + excellent: + value: "> 5.0x" + signal: "Outstanding efficiency. Either the product sells itself (low CAC) or + customers generate exceptional lifetime revenue (high LTV). May also + indicate under-investment in growth." + stage_notes: + seed: "At seed, LTV:CAC is an estimate. Investors look for directional signal, + not precision." + series_a: "3x+ LTV:CAC is a standard Series A expectation. Below 3x requires a + compelling narrative about improvement trajectory." + series_b_plus: "A ratio above 5x at scale may indicate the company is + under-investing in growth and leaving market share on the table." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "SaaStr Benchmarks" + year: "2024" + related_metrics: [ "ltv", "cac", "cac-payback-period" ] + related_skills: [ "business-model-canvas", "scenario-planning" ] + caveats: "LTV:CAC above 5x is not always good — it can signal under-investment. + The optimal range for growth-stage companies is 3x-5x." + + - name: "CAC Payback Period" + id: "cac-payback-period" + category: "unit-economics" + definition: "The number of months required for a customer's gross profit to + repay the cost of acquiring them." + formula: "CAC / (ARPU x Gross Margin %)" + unit: "months" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 24 months" + signal: "Capital-intensive growth model. The business must fund more than two + years of customer revenue before breaking even on acquisition." + below_average: + value: "18-24 months" + signal: "Long payback. Acceptable for enterprise SaaS with >95% GRR. Dangerous + for SMB with higher churn." + average: + value: "12-18 months" + signal: "Typical for B2B SaaS. Requires solid retention to generate meaningful + lifetime profit." + good: + value: "6-12 months" + signal: "Efficient. Most investors consider sub-12-month payback a strong + signal. Allows faster reinvestment cycles." + excellent: + value: "< 6 months" + signal: "Exceptional capital efficiency. The business self-funds its growth + rapidly. Often seen in PLG or viral-coefficient products." + stage_notes: + seed: "Payback period under 12 months is a powerful signal at seed. Over 18 + months is a concern." + series_a: "Median payback for Series A companies is roughly 15-18 months. Top + quartile is under 12 months." + series_b_plus: "Payback should be measured by segment. Enterprise may have + longer payback but higher LTV; SMB should pay back in under 12 months." + data_sources: + - source: "OpenView SaaS Benchmarks" + year: "2024" + - source: "KeyBanc SaaS Survey" + year: "2024" + related_metrics: [ "cac", "ltv", "ltv-cac-ratio", "arpu", "gross-margin" ] + related_skills: [ "balanced-scorecard", "business-model-canvas" ] + caveats: "Payback period is often quoted using revenue, not gross profit. The + gross-margin-adjusted version is the correct calculation and typically + 20-30% longer." + + - name: "Gross Margin" + id: "gross-margin" + category: "unit-economics" + definition: "Revenue minus cost of goods sold as a percentage of revenue, + measuring how much of each dollar of revenue is available to fund + operations, growth, and profit." + formula: "(Revenue - COGS) / Revenue x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 60%" + signal: "Heavy services component or infrastructure costs eroding the software + economics. This is a services business with a software wrapper, not + true SaaS." + below_average: + value: "60-70%" + signal: "Below SaaS norms. Common in companies with significant + human-in-the-loop delivery, high hosting costs, or bundled + implementation." + average: + value: "70-75%" + signal: "Acceptable for SaaS, though on the lower end. Infrastructure-heavy + products (data, AI/ML) often land here." + good: + value: "75-80%" + signal: "Healthy SaaS margin. Demonstrates leverage in the delivery model." + excellent: + value: "> 80%" + signal: "Best-in-class software economics. The marginal cost of serving an + additional customer is negligible. Public SaaS median is ~75%." + stage_notes: + seed: "Gross margins may be artificially low (manual processes) or high (no + support costs yet). Neither is representative." + series_a: "Investors expect a path to 70%+ gross margin even if current levels + are lower due to early-stage inefficiency." + series_b_plus: "Gross margin should stabilize at 75-85%. Declining gross margins + at scale are a serious concern." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "KeyBanc SaaS Survey" + year: "2024" + related_metrics: [ "cac-payback-period", "ltv", "burn-multiple" ] + related_skills: [ "business-model-canvas", "balanced-scorecard" ] + caveats: "COGS for SaaS includes hosting/infrastructure, customer support, + customer success (debated), and third-party data/API costs. Do not confuse + gross margin with contribution margin." + + # ───────────────────────────────────────────── + # EFFICIENCY METRICS + # ───────────────────────────────────────────── + + - name: "Burn Multiple" + id: "burn-multiple" + category: "efficiency" + definition: "The ratio of net cash burned to net new ARR generated, measuring + how efficiently the company converts capital into recurring revenue + growth." + formula: "Net Burn / Net New ARR" + unit: "multiple" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 3.0x" + signal: "Burning more than $3 for every $1 of net new ARR. Capital-intensive + growth that most investors will not fund in a disciplined market." + below_average: + value: "2.0-3.0x" + signal: "Inefficient but potentially acceptable at very early stages with high + growth rates." + average: + value: "1.5-2.0x" + signal: "Typical for growth-stage SaaS. The company is investing aggressively + but within a defensible range." + good: + value: "1.0-1.5x" + signal: "Efficient growth. Each dollar burned produces a meaningful return in + recurring revenue." + excellent: + value: "< 1.0x" + signal: "Exceptional capital efficiency. The company generates more net new ARR + than it burns. Rare and highly valued by investors." + stage_notes: + seed: "Burn multiple is very high at seed by definition — the company is + investing ahead of revenue. Track it but do not optimize for it." + series_a: "Investors increasingly use burn multiple as a primary efficiency + screen. Sub-2x is the expectation." + series_b_plus: "Bessemer coined this metric to replace 'efficiency score.' + Sub-1.5x is the target. Cash-flow-positive companies have a 0x burn + multiple." + data_sources: + - source: "Bessemer Venture Partners (David Sacks)" + year: "2024" + - source: "Battery Ventures Cloud Operating Metrics" + year: "2023" + related_metrics: [ "rule-of-40", "arr", "gross-margin" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "Burn multiple is undefined or misleading for companies with flat or + declining ARR. Use it only for growing companies." + + - name: "Rule of 40" + id: "rule-of-40" + category: "efficiency" + definition: "The sum of revenue growth rate and profit margin, measuring the + tradeoff between growth and profitability — a combined health score for + SaaS businesses." + formula: "YoY Revenue Growth % + Free Cash Flow Margin % (or EBITDA Margin %)" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 20%" + signal: "Neither growing fast nor profitable. The company is stuck in an + unproductive middle — too slow to be a growth story, too unprofitable + to be a value story." + below_average: + value: "20-30%" + signal: "Below the threshold. Acceptable only during a strategic transition + (e.g., shifting from growth to profitability)." + average: + value: "30-40%" + signal: "Approaching but not meeting the bar. Many private SaaS companies land + here." + good: + value: "40-60%" + signal: "Meeting the Rule of 40. The standard for a well-run SaaS business. + Balances growth and efficiency effectively." + excellent: + value: "> 60%" + signal: "Elite performance. Companies like CrowdStrike and Datadog at their + peaks. Either hyper-growth, highly profitable, or both." + stage_notes: + seed: "Rule of 40 is not applicable at seed. Growth rate alone is the relevant + metric." + series_a: "Begins to apply loosely. A company growing 100% YoY with -60% margins + technically hits 40% but the composition matters." + series_b_plus: "Becomes a primary valuation driver. Public market investors use + Rule of 40 as a screening criterion for premium multiples." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "Battery Ventures State of Cloud" + year: "2023" + related_metrics: [ "burn-multiple", "gross-margin", "arr" ] + related_skills: [ "balanced-scorecard", "scenario-planning" ] + caveats: "The Rule of 40 treats growth and profitability as interchangeable. + They are not. A company growing 5% with 35% margins is fundamentally + different from one growing 40% with 0% margins." + + - name: "Magic Number" + id: "magic-number" + category: "efficiency" + definition: "The ratio of net new ARR to prior-quarter sales and marketing + spend, measuring the return on the most recent quarter's go-to-market + investment." + formula: "Net New ARR in quarter / Sales & Marketing Spend in prior quarter" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0.5" + signal: "Sales and marketing spend is not converting to revenue efficiently. The + go-to-market motion may be broken or the market is not responding." + below_average: + value: "0.5-0.75" + signal: "Below efficient threshold. Growth requires disproportionate spending. + Consider fixing conversion or targeting before increasing budget." + average: + value: "0.75-1.0" + signal: "Approaching efficiency. The business is generating reasonable returns + on GTM investment." + good: + value: "1.0-1.5" + signal: "Efficient growth. Each dollar of GTM spend produces $1-$1.50 of + annualized recurring revenue. Signal to increase investment." + excellent: + value: "> 1.5" + signal: "Exceptional GTM efficiency. Strong product-market fit or viral dynamics + reducing the cost of customer acquisition." + stage_notes: + seed: "Magic number is unreliable with small numbers. A single deal can produce + a misleading result." + series_a: "A magic number above 0.75 justifies increasing GTM spend. Below 0.5 + suggests the GTM motion needs restructuring." + series_b_plus: "Public SaaS companies target 1.0+. The magic number helps + determine whether to invest in or restructure the sales organization." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "SaaStr Benchmarks" + year: "2024" + related_metrics: [ "cac", "cac-payback-period", "burn-multiple" ] + related_skills: [ "balanced-scorecard", "four-ps-marketing" ] + caveats: "The magic number uses prior quarter spend against current quarter + revenue gain, assuming a one-quarter lag. This assumption breaks for + products with long sales cycles." + + - name: "SaaS Quick Ratio" + id: "saas-quick-ratio" + category: "efficiency" + definition: "The ratio of revenue inflows to revenue outflows, measuring whether + the company adds revenue faster than it loses it." + formula: "(New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 1.0" + signal: "The business is shrinking. Revenue losses exceed gains. Urgent + intervention required." + below_average: + value: "1.0-2.0" + signal: "Growing but fragile. A small increase in churn could tip the business + into contraction." + average: + value: "2.0-4.0" + signal: "Healthy growth dynamics. Adding revenue at 2-4x the rate of loss." + good: + value: "4.0-6.0" + signal: "Strong growth quality. Revenue additions far outpace losses. The + business has momentum." + excellent: + value: "> 6.0" + signal: "Exceptional. Very low churn relative to new revenue additions. Common + in early-stage companies with low absolute churn." + stage_notes: + seed: "Quick Ratio tends to be high at seed because absolute churn is low. A few + churned customers will crater it." + series_a: "A Quick Ratio above 4 is strong at Series A. It demonstrates that + growth is not masking a retention problem." + series_b_plus: "Quick Ratio naturally declines at scale as the churned base + grows in absolute terms. 2-4x is healthy at scale." + data_sources: + - source: "Mamoon Hamid / Social Capital framework" + year: "2023" + - source: "Paddle/ProfitWell analysis" + year: "2024" + related_metrics: [ "nrr", "revenue-churn", "mom-growth-rate" ] + related_skills: [ "balanced-scorecard", "growth-share-matrix" ] + caveats: "Quick Ratio rewards low churn and high new revenue equally. A company + with terrible retention but massive top-of-funnel can still score well. + Pair with GRR." + + # ───────────────────────────────────────────── + # SALES METRICS + # ───────────────────────────────────────────── + + - name: "Average Contract Value (ACV)" + id: "acv" + category: "sales" + definition: "The average annualized revenue per customer contract, indicating + the company's market positioning and deal size." + formula: "Total new ARR from new contracts / Number of new contracts" + unit: "currency" + direction: "target-range" + benchmarks: + poor: + value: "Misaligned ACV for the go-to-market model (e.g., $500 ACV with an + enterprise sales team, or $200K ACV with self-serve only)" + signal: "The GTM model does not match the deal size. This creates structural + inefficiency — either over-investing in sales or under-investing in + it." + below_average: + value: "ACV < $1K with any direct sales involvement" + signal: "Deal size too small to support human-touch sales. Must be product-led + growth or self-serve to be viable." + average: + value: "$5K-$25K ACV with inside sales; $25K-$100K with field sales" + signal: "Typical SaaS range. The GTM model is appropriately matched to the deal + size." + good: + value: "$50K-$200K ACV with field sales and customer success" + signal: "Strong mid-market to enterprise positioning. Supports a high-touch + model and strategic customer relationships." + excellent: + value: "> $200K ACV with strategic/enterprise sales" + signal: "Enterprise-grade deals. Long sales cycles but high retention and + expansion potential. Concentrated customer risk." + stage_notes: + seed: "ACV often starts low and grows as the product matures and moves upmarket. + Seed-stage ACV below $5K is common." + series_a: "ACV trajectory matters more than absolute level. Increasing ACV over + time signals product maturation and market pull." + series_b_plus: "ACV expansion within existing accounts is as important as + new-logo ACV. Track both separately." + data_sources: + - source: "KeyBanc SaaS Survey" + year: "2024" + - source: "OpenView SaaS Benchmarks" + year: "2023" + related_metrics: [ "arpu", "ltv", "sales-cycle-length" ] + related_skills: + - four-ps-marketing + caveats: "ACV can be distorted by a single large deal. Report median ACV + alongside mean ACV for accuracy." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Average Revenue Per User (ARPU)" + id: "arpu" + category: "sales" + definition: "The average monthly revenue generated per active user or account, + measuring monetization intensity." + formula: "MRR / Total active accounts (or users, depending on pricing model)" + unit: "currency" + direction: "higher-is-better" + benchmarks: + poor: + value: "< $10/month per account (B2B); < $2/month per user (B2C)" + signal: "Very low monetization. Requires massive scale to build a significant + business. Difficult to support any direct sales motion." + below_average: + value: "$10-$50/month (B2B); $2-$10/month (B2C)" + signal: "Low ARPU. Viable with self-serve PLG and low support costs. Challenging + to fund a traditional sales team." + average: + value: "$50-$500/month (B2B)" + signal: "The range where inside sales, content marketing, and moderate customer + success become sustainable." + good: + value: "$500-$5,000/month (B2B)" + signal: "Strong monetization. Supports field sales, dedicated CSMs, and + significant retention investment." + excellent: + value: "> $5,000/month (B2B)" + signal: "Enterprise pricing. High-value customers who justify strategic account + management and custom solutions." + stage_notes: + seed: "ARPU at seed reflects initial pricing — often underpriced. Tracking ARPU + growth over time is more informative." + series_a: "ARPU should be increasing or stable. Declining ARPU (from moving + downmarket to chase volume) is a warning sign." + series_b_plus: "Segment ARPU by cohort and customer tier. Blended ARPU obscures + whether you are attracting larger or smaller customers over time." + data_sources: + - source: "Paddle/ProfitWell Price Benchmarks" + year: "2024" + - source: "OpenView PLG Index" + year: "2023" + related_metrics: [ "acv", "mrr", "ltv" ] + related_skills: + - business-model-canvas + caveats: "ARPU varies enormously by segment. A company selling to SMBs at + $50/month and enterprises at $5,000/month has a blended ARPU that + describes neither customer well." + related_content: + - kind: diagnostic + ref: pricing-diagnosis + + - name: "Expansion Revenue Percentage" + id: "expansion-revenue-pct" + category: "sales" + definition: "The percentage of new MRR that comes from existing customers + (upsells, cross-sells, seat expansion) rather than new logos." + formula: "Expansion MRR / Total New MRR x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 10%" + signal: "Nearly all growth comes from new customers. The existing base is not + expanding, indicating limited upsell paths or low product stickiness." + below_average: + value: "10-20%" + signal: "Minimal expansion. The product may lack tiers, add-ons, or usage-based + pricing that drive natural expansion." + average: + value: "20-30%" + signal: "Moderate expansion revenue. Common for companies with seat-based + pricing and steady customer growth." + good: + value: "30-50%" + signal: "Strong expansion engine. Existing customers are a significant growth + driver. Indicates land-and-expand is working." + excellent: + value: "> 50%" + signal: "Expansion-dominated growth. The existing base grows faster than new + customer acquisition. Characteristic of usage-based models (Snowflake, + Twilio)." + stage_notes: + seed: "Expansion revenue is negligible at seed — the focus is new customer + acquisition and retention." + series_a: "Expansion signals begin to matter. Any expansion revenue at Series A + is positive. Building the expansion motion is a key Series A + initiative." + series_b_plus: "At scale, 30-50% of new MRR from expansion is the target. + Companies relying solely on new logos face increasing CAC pressure." + data_sources: + - source: "KeyBanc SaaS Survey" + year: "2024" + - source: "OpenView Expansion Revenue Report" + year: "2023" + related_metrics: [ "nrr", "ndr", "arpu" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Expansion revenue percentage can be inflated by usage-based pricing + with volatile consumption. Distinguish between durable expansion (more + seats, higher tiers) and variable expansion (usage spikes)." + + - name: "Net Dollar Retention (NDR)" + id: "ndr" + category: "retention" + definition: "Functionally identical to NRR — the percentage of revenue retained + from a cohort of customers after a defined period, including expansion and + contraction." + formula: "(Starting ARR of cohort + Expansion - Contraction - Churn) / Starting + ARR of cohort x 100 (typically measured at 12-month intervals)" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 90%" + signal: "Cohort revenue declines materially. The business cannot grow its + existing base — all growth must come from new logos." + below_average: + value: "90-100%" + signal: "Cohort revenue is roughly flat. No net expansion from existing + customers." + average: + value: "100-110%" + signal: "Modest net expansion. Cohorts grow slightly over time." + good: + value: "110-130%" + signal: "Strong expansion. Typical of best-in-class private SaaS companies. Each + cohort becomes more valuable over time." + excellent: + value: "> 130%" + signal: "Exceptional. Usage-based or deeply embedded products where customer + spend compounds naturally." + stage_notes: + seed: "NDR requires at least 12 months of cohort data to be meaningful. Not + applicable at seed." + series_a: "NDR is one of the most scrutinized metrics at Series A. Above 110% is + a strong signal." + series_b_plus: "NDR above 120% is a key driver of premium valuations in public + markets. Bessemer, Iconiq, and other benchmarks weight it heavily." + data_sources: + - source: "Bessemer Cloud Index" + year: "2024" + - source: "Iconiq Growth" + year: "2023" + related_metrics: [ "nrr", "grr", "expansion-revenue-pct" ] + related_skills: [ "net-promoter-score", "balanced-scorecard" ] + caveats: "NDR and NRR are used interchangeably in the industry, though NDR + typically implies annual cohort measurement while NRR may be monthly. + Clarify the time window when reporting." + + - name: "Pipeline Coverage Ratio" + id: "pipeline-coverage-ratio" + category: "sales" + definition: "The ratio of total pipeline value to quota or revenue target for a + given period, measuring whether the sales team has sufficient opportunity + volume." + formula: "Total pipeline value for period / Revenue target (quota) for period" + unit: "ratio" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 2.0x" + signal: "Insufficient pipeline. The sales team has less than twice quota in + pipeline, making target attainment unlikely given typical win rates." + below_average: + value: "2.0-2.5x" + signal: "Thin pipeline. Requires above-average win rates to hit target. Any deal + slippage will cause a miss." + average: + value: "2.5-3.5x" + signal: "Standard coverage. Assuming 25-35% win rates, this provides a + reasonable probability of hitting target." + good: + value: "3.5-5.0x" + signal: "Healthy coverage. Provides buffer for deal slippage, lost deals, and + sales cycle extensions." + excellent: + value: "> 5.0x" + signal: "Strong coverage, though may indicate pipeline quality issues — too many + unqualified opportunities inflating the number." + stage_notes: + seed: "Pipeline coverage is not a meaningful metric without a sales team. + Founders selling directly should track opportunity list, not formal + pipeline." + series_a: "As the first sales hires come on, pipeline coverage becomes a leading + indicator. 3x coverage is the minimum target." + series_b_plus: "Pipeline coverage should be measured by stage (early, mid, + late), by segment, and by rep. Aggregate coverage masks individual + performance." + data_sources: + - source: "Gartner Sales Benchmarks" + year: "2024" + - source: "Forrester B2B Sales Report" + year: "2023" + related_metrics: [ "win-rate", "sales-cycle-length", "acv" ] + related_skills: [ "scenario-planning", "balanced-scorecard" ] + caveats: "Pipeline coverage is only meaningful if pipeline hygiene is strong. + Inflated pipelines with stale or unqualified deals produce misleadingly + high coverage ratios." + + - name: "Win Rate" + id: "win-rate" + category: "sales" + definition: "The percentage of sales opportunities that convert to closed-won + deals, measuring sales effectiveness." + formula: "Closed-won opportunities / (Closed-won + Closed-lost opportunities) x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "Very low conversion. Possible causes: poor qualification, weak product + fit, uncompetitive offering, or ineffective sales process." + below_average: + value: "15-20%" + signal: "Below average. The pipeline includes too many unqualified or poorly + matched opportunities." + average: + value: "20-30%" + signal: "Typical for B2B SaaS. Roughly one in four qualified opportunities + converts." + good: + value: "30-40%" + signal: "Strong conversion. Indicates good qualification, competitive product, + and effective sales execution." + excellent: + value: "> 40%" + signal: "Exceptional. Either the product has overwhelming competitive advantage + or the company qualifies pipeline very aggressively (which may limit + volume)." + stage_notes: + seed: "Founders typically close at higher rates than hired reps — they know the + product deeply and prospects respond to founder energy. Do not use + founder win rates to project team performance." + series_a: "Win rates should be tracked by source (inbound vs. outbound), deal + size, and sales rep. Aggregate win rate is a starting point." + series_b_plus: "Win rate analysis should include competitive win/loss data. + Track not just whether you win but whom you beat and whom you lose to." + data_sources: + - source: "Gartner Sales Research" + year: "2024" + - source: "HubSpot Sales Benchmarks" + year: "2023" + related_metrics: [ "pipeline-coverage-ratio", "sales-cycle-length", "acv" ] + related_skills: [ "competitive-negotiation", "porters-five-forces" ] + caveats: "Win rate is sensitive to how 'opportunity' is defined. If only highly + qualified prospects enter the pipeline, win rate appears high. Standardize + opportunity stage definitions." + + - name: "Sales Cycle Length" + id: "sales-cycle-length" + category: "sales" + definition: "The average number of days from first meaningful sales engagement + to closed-won deal." + formula: "Sum of (close date - opportunity creation date) for all won deals / + Number of won deals" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 180 days for mid-market; > 365 days for enterprise" + signal: "Extremely long cycles. Common causes: unclear value proposition, too + many stakeholders, weak champion, or product not addressing an urgent + problem." + below_average: + value: "90-180 days for mid-market; 180-365 days for enterprise" + signal: "Long but not unusual for complex sales. Requires strong pipeline + management and forecasting discipline." + average: + value: "30-90 days for SMB/mid-market; 90-180 days for enterprise" + signal: "Standard B2B SaaS range. Varies significantly by ACV — higher ACV + naturally correlates with longer cycles." + good: + value: "14-30 days for SMB; 45-90 days for mid-market" + signal: "Efficient cycle. Strong urgency, clear value, and streamlined buying + process." + excellent: + value: "< 14 days for SMB; < 45 days for mid-market" + signal: "Very fast conversion. Often indicates product-led growth, free trial + conversion, or a burning platform problem." + stage_notes: + seed: "Sales cycles at seed are often artificially short (early adopters with + low friction) or artificially long (unrefined sales process). Neither + predicts scale behavior." + series_a: "Tracking average sales cycle by deal size establishes the basis for + forecasting and hiring models." + series_b_plus: "Sales cycle compression is a key efficiency lever at scale. + Reducing cycle length by 20% has the same effect as hiring 20% more + reps." + data_sources: + - source: "Gartner B2B Buying Study" + year: "2024" + - source: "HubSpot Sales Benchmarks" + year: "2023" + related_metrics: [ "win-rate", "acv", "pipeline-coverage-ratio" ] + related_skills: [ "delivering-the-deal", "competitive-negotiation" ] + caveats: "Sales cycle length should exclude outlier deals (both extremely fast + and extremely slow). Use median rather than mean for more representative + data." + + # ───────────────────────────────────────────── + # PRODUCT METRICS + # ───────────────────────────────────────────── + + - name: "Time to Value" + id: "time-to-value" + category: "product" + definition: "The elapsed time from customer sign-up to the moment they + experience the core value proposition of the product." + formula: "Median time from account creation to activation milestone + (product-specific definition)" + unit: "days" + direction: "lower-is-better" + benchmarks: + poor: + value: "> 30 days" + signal: "Customers wait a month before experiencing value. High abandonment + risk, especially for self-serve products." + below_average: + value: "14-30 days" + signal: "Slow value delivery. Typical of products requiring significant setup, + integration, or data migration." + average: + value: "3-14 days" + signal: "Reasonable for B2B products with moderate complexity. Acceptable for + products with guided onboarding." + good: + value: "1-3 days" + signal: "Fast value delivery. Strong onboarding flow and clear first-use + experience." + excellent: + value: "< 1 day (ideally < 1 hour)" + signal: "Immediate value. Characteristic of PLG products with strong 'aha + moments' (Slack, Loom, Canva). Drives viral adoption." + stage_notes: + seed: "Time to value is often long at seed — manual onboarding, incomplete + product. Reducing it is a top priority for product-market fit." + series_a: "Time to value directly predicts conversion rates. Companies that + compress TTV from weeks to days see step-function improvements in + activation." + series_b_plus: "At scale, time to value should be measured by segment and + onboarding path (self-serve vs. assisted vs. enterprise + implementation)." + data_sources: + - source: "OpenView PLG Index" + year: "2024" + - source: "Pendo Product Benchmarks" + year: "2023" + related_metrics: [ "activation-rate", "logo-churn" ] + related_skills: [ "net-promoter-score", "product-life-cycle" ] + caveats: "Time to value requires a precise definition of the 'value moment.' + Without this, the metric is meaningless. Define the activation event + before measuring TTV." + + - name: "Activation Rate" + id: "activation-rate" + category: "product" + definition: "The percentage of new sign-ups or customers who complete the key + actions that predict long-term retention and value realization." + formula: "Users who complete activation milestone / Total new sign-ups x 100" + unit: "percentage" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 15%" + signal: "The vast majority of sign-ups never experience the product's value. The + onboarding experience is failing or the product does not deliver on + its promise." + below_average: + value: "15-25%" + signal: "Low activation. Common for products with complex setup requirements or + weak onboarding flows." + average: + value: "25-40%" + signal: "Standard for B2B SaaS with free trials or freemium models. Significant + room for improvement." + good: + value: "40-60%" + signal: "Strong activation. The product's onboarding effectively guides users to + value. Good PLG companies achieve this range." + excellent: + value: "> 60%" + signal: "Exceptional. The product is intuitive and delivers value with minimal + friction. Elite PLG products (Dropbox, Calendly) at their peaks." + stage_notes: + seed: "Activation rate is the most important product metric at seed. It directly + indicates whether the product delivers on its promise." + series_a: "Improving activation rate is often the highest-ROI investment at + Series A — it improves every downstream metric (retention, expansion, + referral)." + series_b_plus: "Activation rate should be segmented by source, persona, and + onboarding path. Different segments require different activation + strategies." + data_sources: + - source: "OpenView PLG Index" + year: "2024" + - source: "Mixpanel Product Benchmarks" + year: "2023" + related_metrics: [ "time-to-value", "logo-churn", "nrr" ] + related_skills: [ "net-promoter-score", "product-life-cycle", "disruptive-innovation" ] + caveats: "Activation rate depends entirely on how the activation milestone is + defined. Choose a milestone that correlates with retention (validated + empirically), not an arbitrary product action." + + # ───────────────────────────────────────────── + # PRODUCT METRICS (continued) + # ───────────────────────────────────────────── + + - name: "Net Promoter Score (NPS)" + id: "nps-saas" + category: "product" + definition: "A measure of customer loyalty and satisfaction based on the + likelihood of recommending the product, widely used as a leading indicator + of retention in SaaS." + formula: "% Promoters (score 9-10) - % Detractors (score 0-6)" + unit: "score" + direction: "higher-is-better" + benchmarks: + poor: + value: "< 0" + signal: "More detractors than promoters. The product is actively generating + negative word-of-mouth. Churn risk is severe." + below_average: + value: "0-20" + signal: "Net positive but weak. Customers are indifferent rather than + enthusiastic. Vulnerable to competitive displacement." + average: + value: "20-40" + signal: "Decent satisfaction. Typical for B2B SaaS products that solve real + problems without delighting users." + good: + value: "40-60" + signal: "Strong loyalty. Customers actively recommend the product. Correlates + with low churn and organic growth." + excellent: + value: "> 60" + signal: "Exceptional loyalty. Companies like Slack (early), Notion, and Zoom in + their growth phases. Drives powerful viral loops." + stage_notes: + seed: "NPS surveys require a minimum sample size (~30 responses) to be + statistically meaningful. At seed, qualitative feedback matters more." + series_a: "NPS above 40 is a strong signal for investors. Below 20 at Series A + raises concerns about product-market fit depth." + series_b_plus: "NPS should be tracked quarterly, segmented by cohort and + customer tier. Declining NPS at scale is an early warning of market + saturation or product stagnation." + data_sources: + - source: "Bain & Company NPS Benchmarks" + year: "2024" + - source: "Retently B2B SaaS NPS Benchmarks" + year: "2024" + related_metrics: [ "logo-churn", "nrr", "activation-rate" ] + related_skills: [ "net-promoter-score" ] + caveats: "NPS is a lagging and blunt instrument. A high NPS does not guarantee + retention (customers may love the product but switch due to price), and a + low NPS does not guarantee churn (customers may dislike the product but + have high switching costs)." diff --git a/plugins/foreman/content/industry-packs/saas/saas-diagnostic-rules.yaml b/plugins/foreman/content/industry-packs/saas/saas-diagnostic-rules.yaml new file mode 100644 index 0000000..ad27598 --- /dev/null +++ b/plugins/foreman/content/industry-packs/saas/saas-diagnostic-rules.yaml @@ -0,0 +1,1137 @@ +# SaaS Industry Pack — Diagnostic Rules +# +# For each of the 20 Foreman diagnostics, this file defines how triage +# questions, diagnosis weights, and routing shift in a SaaS context. +# The diagnostic agent loads these rules when the SaaS industry pack is active. +# +# Adaptation types: +# as-is — The diagnostic works without modification for SaaS companies. +# enhanced — The diagnostic is relevant but benefits from additional SaaS-specific +# triage questions and diagnosis options. +# reframed — The diagnostic requires significant reinterpretation for SaaS. + +pack_metadata: + sector: "saas" + display_name: "SaaS" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# DIAGNOSTIC RULES +# ═══════════════════════════════════════════════════════════════ + +diagnostic_rules: + + # ───────────────────────────────────────────── + # 1. CUSTOMER CHURN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "customer-churn-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Churn is the defining challenge of SaaS. The base + diagnostic applies, but SaaS churn has distinct subtypes (logo vs. + revenue, voluntary vs. involuntary, early vs. late lifecycle) that require + specialized triage and SaaS-native diagnoses." + additional_triage_questions: + - question: "Is the churn concentrated in logo churn (customers leaving entirely) + or revenue churn (customers downgrading but staying)?" + purpose: "Distinguishes between product-market-fit failures (logo churn) and + pricing/packaging failures (revenue churn). These have fundamentally + different root causes and solutions." + routing_impact: "Logo churn routes to product-market-fit-diagnosis and + activation-rate analysis. Revenue churn routes to pricing-diagnosis + and expansion-revenue analysis." + - question: "What percentage of churn is involuntary (failed payments, expired + cards) versus voluntary (deliberate cancellation)?" + purpose: "Involuntary churn in SaaS is a solvable operational problem — dunning + sequences, card-on-file reminders, and payment retry logic can recover + 20-40% of involuntary churn." + routing_impact: "High involuntary churn (>30% of total) routes to operational + process improvement before any strategic intervention. This is the + highest-ROI fix in SaaS churn." + - question: "When in the customer lifecycle does churn concentrate — within the + first 90 days, at the first renewal boundary, or throughout the + lifecycle?" + purpose: "Early churn signals onboarding or activation failure. Renewal-boundary + churn signals value realization failure. Distributed churn signals + competitive displacement or market saturation." + routing_impact: "First-90-day churn routes to time-to-value and activation-rate + analysis. Renewal churn routes to customer-success process and QBR + effectiveness. Distributed churn routes to + competitive-threat-diagnosis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Activation failure driving early-lifecycle churn" + reason: "SaaS products that fail to deliver value within the first 14-30 days + lose customers before they form habits. This is the most common and + most fixable churn driver." + - diagnosis: "Pricing-value misalignment" + reason: "SaaS customers continuously evaluate whether the subscription price is + justified. Unlike one-time purchases, the value question recurs + every billing cycle." + less_likely: + - diagnosis: "Product quality failure" + reason: "Pure product quality (bugs, downtime) is rarely the primary churn + driver in SaaS. It contributes to dissatisfaction but customers + usually tolerate quality issues if the product delivers unique + value." + saas_specific_diagnoses: + - name: "Negative net churn masking logo churn crisis" + description: "NRR is above 100% because a small number of expanding accounts + offset a large number of departing accounts. The business appears + healthy on aggregate retention metrics while the customer base is + actually hollowing out — becoming concentrated in fewer, larger + accounts with increasing concentration risk." + symptoms: + - "NRR above 100% but logo churn above 5% monthly" + - "Customer count declining while revenue grows" + - "Top 10% of customers representing increasing share of revenue" + - "Expansion revenue dominated by a few large accounts rather than + broad-based growth" + routes_to_skills: [ "net-promoter-score", "balanced-scorecard", "systems-thinking" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] + - name: "Involuntary churn as a silent revenue drain" + description: "Failed payments, expired credit cards, and billing errors account + for a substantial portion of total churn but are not being tracked, + measured, or addressed separately from voluntary churn." + symptoms: + - "No distinction between voluntary and involuntary churn in reporting" + - "No dunning email sequence or payment retry logic" + - "Monthly churn rate 1-3% higher than peers despite strong NPS" + - "High churn among annual-to-monthly conversion cohorts" + routes_to_skills: [ "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] + - name: "Onboarding-to-value gap" + description: "Customers sign up or purchase but never reach the activation + milestone that predicts long-term retention. The product delivers + value, but the path to that value is too long, too complex, or too + poorly guided." + symptoms: + - "High trial-to-paid conversion but high churn within the first 90 + days" + - "Activation rate below 30%" + - "Time to value exceeding 14 days for a self-serve product" + - "Support tickets concentrated in the first two weeks of customer + lifecycle" + routes_to_skills: [ "product-life-cycle", "disruptive-innovation", "net-promoter-score" ] + routes_to_templates: [ "action-plan", "new-initiative-brief" ] + sector_red_flags: + - "Logo churn above 5% monthly sustained for 3+ months — indicates a + structural retention problem, not seasonal variation." + - "Revenue churn exceeding logo churn — customers are downgrading before + leaving, which often predicts an acceleration of full churn." + - "Churn rate increasing as the company scales — a sign that the product + is not retaining the marginal customer acquired through broader + marketing." + + # ───────────────────────────────────────────── + # 2. GROWTH STALL DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "growth-stall-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS growth stalls have characteristic patterns that + differ from traditional businesses. The subscription model provides + precise data on where growth is breaking down — new customer acquisition, + expansion, or retention — and each has different root causes." + additional_triage_questions: + - question: "Decompose your MRR growth: what percentage comes from new customers, + expansion of existing customers, and reactivation of former + customers?" + purpose: "Identifies which growth engine is stalling. New customer acquisition + slowing suggests GTM or market problems. Expansion stalling suggests + product/pricing problems. Low reactivation suggests the product has no + win-back value." + routing_impact: "New-customer stall routes to four-ps-marketing and + competitive-threat-diagnosis. Expansion stall routes to + pricing-diagnosis and product-life-cycle. Mixed stall routes to + systems-thinking for holistic analysis." + - question: "Has your CAC increased, your conversion rate decreased, or both?" + purpose: "Rising CAC with stable conversion suggests market saturation or + increased competition. Declining conversion with stable CAC suggests + product-market fit erosion or a competitive leap." + routing_impact: "Rising CAC routes to channel efficiency analysis and + blue-ocean-strategy. Declining conversion routes to + product-market-fit-diagnosis and win-rate analysis." + - question: "What is your current burn multiple, and how has it changed over the + last two quarters?" + purpose: "A rising burn multiple despite investment means the growth engine is + losing efficiency — the company is spending more to grow less." + routing_impact: "Burn multiple above 3x routes to efficiency analysis and + scenario-planning for runway management." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Channel saturation" + reason: "SaaS companies often exhaust their initial growth channel (content, + outbound, product-led) and need to build new channels. The stall + occurs at the point of channel maturity." + - diagnosis: "Market segment ceiling" + reason: "SaaS products often saturate their initial market segment (e.g., + 'startups under 50 employees') and must expand to adjacent segments + (mid-market, enterprise) to sustain growth." + less_likely: + - diagnosis: "Macro-economic demand decline" + reason: "SaaS demand is relatively resilient to economic cycles — IT budgets are + the last to be cut. A growth stall attributed to 'the market' is + usually a competitive or execution problem." + saas_specific_diagnoses: + - name: "Product-led growth ceiling" + description: "The company's PLG motion is stalling because it has reached the + limit of users who will self-serve through a free trial or freemium + product. Growth requires adding a sales-assisted or enterprise motion, + which the company has not built." + symptoms: + - "Self-serve sign-ups plateau despite increasing marketing spend" + - "Trial-to-paid conversion rate declining" + - "Inbound leads requesting enterprise features (SSO, admin controls, + custom integrations) that the product does not offer" + - "Average deal size capped at the self-serve pricing tier" + routes_to_skills: [ "blue-ocean-strategy", "product-life-cycle", "business-model-canvas" ] + routes_to_templates: [ "strategic-analysis-one-pager", "new-initiative-brief" ] + - name: "Net-new ARR dependency" + description: "Growth is entirely dependent on acquiring new customers because + the existing base is not expanding. This is unsustainable because CAC + increases as the addressable market for new logos diminishes." + symptoms: + - "Expansion revenue below 15% of total new MRR" + - "NRR between 95-105% despite strong logo retention" + - "No usage-based or per-seat pricing that enables organic expansion" + - "Customer success team focused on retention only, not growth" + routes_to_skills: + - four-ps-marketing + - net-promoter-score + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "MoM growth decelerating for 3+ consecutive months without a clear + seasonal explanation." + - "CAC Payback Period extending beyond 18 months — the growth engine is + becoming capital-inefficient." + - "Magic Number below 0.5 — GTM spend is not converting to revenue + efficiently." + + # ───────────────────────────────────────────── + # 3. PRODUCT-MARKET FIT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "product-market-fit-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS has the richest quantitative signals for + product-market fit of any business model. Retention curves, NPS + segmentation, and organic growth data provide objective PMF measurement + that the base diagnostic should incorporate." + additional_triage_questions: + - question: "What does your retention curve look like — does it flatten (users who + stay past month 3 stay long-term) or does it continue declining (users + never stop leaving)?" + purpose: "A flattening retention curve is the single strongest quantitative + signal of product-market fit. A continuously declining curve means PMF + has not been achieved regardless of other signals." + routing_impact: "Flattening curve with low initial retention routes to + onboarding optimization. Continuously declining curve routes to + fundamental PMF exploration — the product may need a pivot." + - question: "What percentage of your growth is organic (word-of-mouth, direct + traffic) versus paid?" + purpose: "Organic growth above 40% is a strong PMF signal — customers are + recommending the product without incentives. Below 20% suggests the + product is not generating advocacy." + routing_impact: "Low organic growth routes to net-promoter-score analysis and + product-value assessment. High organic growth with slow total growth + routes to distribution strategy, not product changes." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "PMF exists for a niche but the company is targeting too broadly" + reason: "SaaS companies frequently have strong PMF in one segment (e.g., + 'marketing agencies under 20 people') but dilute it by trying to + serve everyone." + - diagnosis: "PMF existed but the market has shifted" + reason: "SaaS markets evolve rapidly. PMF is not permanent — what the market + needed two years ago may be table stakes today." + less_likely: + - diagnosis: "Product is fundamentally flawed" + reason: "If any customers retain long-term and expand, the product works for + someone. The question is usually not 'does the product work?' but + 'for whom does it work?'" + saas_specific_diagnoses: + - name: "PMF for the wrong segment" + description: "The product has strong retention and NPS among a small segment, + but the company is investing sales and marketing spend to acquire + customers in a different, larger segment where the product does not + resonate." + symptoms: + - "NPS above 50 for one segment but below 20 for the segment receiving + the most marketing spend" + - "High churn among recently acquired customers but low churn among + early adopters" + - "Customer success team spending disproportionate time on customers + who do not match the ideal profile" + routes_to_skills: + [ + "blue-ocean-strategy", + "business-model-canvas", + "defining-and-exploring-problems" + ] + routes_to_templates: [ "strategic-analysis-one-pager", "market-opportunity-summary" ] + sector_red_flags: + - "Retention curve that never flattens — a continuous decline regardless + of cohort vintage." + - "NPS below 20 after 12 months in market — customers are not advocating." + - "Organic growth below 15% of total acquisition — the product relies + entirely on paid channels to grow." + + # ───────────────────────────────────────────── + # 4. PRICING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "pricing-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Pricing in SaaS is fundamentally different from pricing + in other businesses. The subscription model, the availability of real-time + usage data, and the direct relationship between pricing structure and + retention/expansion dynamics make this diagnostic significantly more + complex in SaaS." + additional_triage_questions: + - question: "Does your pricing structure create natural expansion revenue — do + customers pay more as they get more value, or do they pay the same + regardless of usage and team size?" + purpose: "Flat-rate pricing that does not scale with value received leaves + expansion revenue on the table and creates a ceiling on per-account + revenue." + routing_impact: "No expansion mechanism routes to pricing restructure using + value-metric analysis. Existing expansion mechanism with low expansion + rate routes to packaging and tier optimization." + - question: "What is the ratio of your annual price to the monthly price x 12? + What percentage of customers choose annual?" + purpose: "A standard annual discount of 15-20% should drive 30-50% annual + adoption. Low annual adoption suggests the discount is insufficient or + customers lack confidence in long-term value." + routing_impact: "Very low annual adoption routes to both pricing adjustment + (increase annual discount) and product-market-fit concerns (customers + may not trust long-term value)." + - question: "When was the last time you raised prices, and what happened to churn + when you did?" + purpose: "SaaS companies that have never raised prices or raised prices more + than 24 months ago are almost certainly under-pricing. The churn + impact of price increases is usually far lower than founders fear." + routing_impact: "Never raised prices routes to immediate pricing analysis with + willingness-to-pay research. Raised prices with no churn impact routes + to further increases." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Under-pricing" + reason: "The default error in SaaS is under-pricing. Founders fear losing + customers but studies consistently show SaaS companies capture only + 10-20% of the value they deliver." + - diagnosis: "Value metric misalignment" + reason: "Charging per seat when the value scales with usage (or vice versa) + creates friction and caps revenue. The value metric must align with + how customers derive value." + less_likely: + - diagnosis: "Over-pricing relative to competition" + reason: "Over-pricing is less common than founders think. Losing deals on price + often reflects poor value communication, not excessive pricing." + saas_specific_diagnoses: + - name: "Flat-rate trap" + description: "The company charges a single monthly price regardless of usage + intensity, team size, or value received. This caps per-account revenue + and creates a class of power users who are massively under-paying + relative to the value they extract." + symptoms: + - "ARPU flat or declining despite product improvements" + - "Expansion revenue below 10% of new MRR" + - "Some customers using 100x more resources than others at the same + price" + - "Large customers asking for features but unwilling to pay more + because they are already on the 'everything' plan" + routes_to_skills: + - four-ps-marketing + - business-model-canvas + routes_to_templates: [ "unit-economics-snapshot", "decision-rationale-memo" ] + related_content: + - kind: diagnostic + ref: pricing-diagnosis + sector_red_flags: + - "Pricing unchanged for more than 18 months in a growing product." + - "ARPU declining quarter-over-quarter — a sign of downward pricing + pressure or adverse selection." + - "Win rate analysis showing price as the primary loss reason in more than + 30% of losses — may indicate a value communication problem rather than a + price problem." + + # ───────────────────────────────────────────── + # 5. FUNDRAISING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "fundraising-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS fundraising has the most standardized benchmarks of + any sector. Investors apply well-known thresholds for each round, and SaaS + metrics are the lingua franca of venture capital. The diagnostic benefits + from surfacing these specific benchmarks." + additional_triage_questions: + - question: "What are your current ARR, MoM growth rate, NRR, and months of + runway?" + purpose: "These four metrics are the primary inputs to SaaS fundraising + readiness. Investors can make a rapid initial assessment from these + alone." + routing_impact: "Metrics below Series A thresholds (ARR < $1M, growth < 10% MoM, + NRR < 100%) route to pre-fundraising skill-building. Metrics above + thresholds route to fundraising execution." + - question: "Can you articulate your unit economics — specifically LTV:CAC ratio + and CAC payback period — with data?" + purpose: "Unit economics literacy is a gating criterion for SaaS fundraising. + Founders who cannot answer this question are not ready to raise." + routing_impact: "Cannot articulate routes to unit-economics-snapshot template + and balanced-scorecard skill for metric foundation. Can articulate + routes to fundraising-deck-outline and investor-update-email." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Timing mismatch" + reason: "SaaS companies frequently try to raise too early (pre-PMF) or during a + metrics trough (seasonal churn, post-pricing-change dip). Timing is + the most controllable fundraising variable." + - diagnosis: "Narrative-metrics disconnect" + reason: "SaaS founders who tell a story that does not match their metrics face + immediate credibility challenges. Investors cross-reference the + narrative against the numbers in real time." + less_likely: + - diagnosis: "Market too small" + reason: "SaaS total addressable markets are generally large enough for venture + returns. The 'market too small' objection usually means the company + has not articulated the expansion path convincingly." + saas_specific_diagnoses: + - name: "Metrics-ready but narrative-deficient" + description: "The company's SaaS metrics meet or exceed benchmarks for the + target round, but the founder cannot articulate a compelling narrative + about market opportunity, competitive differentiation, and the path to + category leadership." + symptoms: + - "Initial investor meetings generate interest based on metrics but no + follow-up" + - "Investor feedback centers on 'market' and 'vision' rather than + 'execution' or 'metrics'" + - "Pitch deck is dense with data but lacks a coherent strategic + narrative" + routes_to_skills: + [ + "story-structure-and-arc", + "strategic-thinking-and-alignment", + "blue-ocean-strategy" + ] + routes_to_templates: [ "fundraising-deck-outline", "market-opportunity-summary" ] + sector_red_flags: + - "Raising with less than 6 months of runway — desperation weakens + negotiating position and signals poor planning." + - "Raising at a valuation more than 100x ARR without hypergrowth metrics + to justify it." + - "Raising without a clear use-of-proceeds plan tied to specific growth + milestones." + + # ───────────────────────────────────────────── + # 6. REVENUE DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "revenue-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Revenue in SaaS decomposes into precise, measurable + components (new, expansion, contraction, churn) that the base revenue + diagnostic should leverage. The SaaS overlay adds component-level triage." + additional_triage_questions: + - question: "Break down your MRR into five components: new MRR, expansion MRR, + reactivation MRR, contraction MRR, and churned MRR. Which components + are trending in the wrong direction?" + purpose: "SaaS revenue problems always trace to specific MRR components. This + decomposition identifies the precise failure point rather than + treating 'revenue' as a monolithic problem." + routing_impact: "New MRR declining routes to GTM diagnosis. Expansion MRR flat + routes to pricing-diagnosis. Contraction rising routes to + product-value analysis. Churn rising routes to + customer-churn-diagnosis." + - question: "What is your SaaS Quick Ratio — the ratio of revenue inflows (new + + expansion) to revenue outflows (contraction + churn)?" + purpose: "The Quick Ratio reveals the growth quality. A Quick Ratio below 2 + means the business is fragile — a small increase in churn can tip it + into contraction." + routing_impact: "Quick Ratio below 2 routes to simultaneous churn reduction and + growth acceleration. Above 4 routes to growth investment with + confidence." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Expansion revenue underperformance" + reason: "Most SaaS companies under-invest in expansion relative to new customer + acquisition. Expansion is typically more capital-efficient but + receives less organizational focus." + less_likely: + - diagnosis: "Market pricing pressure" + reason: "True market-wide pricing pressure in SaaS is rare. Most pricing + problems are company-specific — poor packaging, weak value + communication, or excessive discounting." + saas_specific_diagnoses: + - name: "Revenue quality deterioration" + description: "Total revenue is growing but the composition is shifting toward + lower-quality revenue: more monthly customers (higher churn risk), + more heavily discounted deals (lower LTV), or more professional + services revenue (lower margin)." + symptoms: + - "Revenue growing but gross margin declining" + - "Percentage of annual contracts declining" + - "Average discount increasing quarter-over-quarter" + - "Professional services revenue growing faster than subscription + revenue" + routes_to_skills: [ "balanced-scorecard", "business-model-canvas" ] + routes_to_templates: [ "unit-economics-snapshot", "quarterly-strategic-review" ] + sector_red_flags: + - "Monthly revenue churn exceeding 3% for three consecutive months." + - "Revenue growth decelerating while sales team size is increasing — a + productivity problem." + - "Gross margin declining below 70% — the business may be shifting from + software to services economics." + + # ───────────────────────────────────────────── + # 7. COMPETITIVE THREAT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "competitive-threat-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS competitive dynamics are uniquely intense due to low + switching costs, transparent pricing, public feature comparisons (G2, + Capterra), and the ability of competitors to iterate rapidly. The base + diagnostic benefits from SaaS-specific competitive threat categories." + additional_triage_questions: + - question: "Is the competitive threat from a direct competitor (same category, + same segment), a platform expanding into your space (e.g., Salesforce, + HubSpot, Microsoft adding your feature), or a new technology paradigm + (AI tools replacing your product's function)?" + purpose: "Each threat type requires a different response. Direct competitors + require differentiation. Platform expansion requires ecosystem + strategy. Paradigm shifts require reinvention." + routing_impact: "Direct competitor routes to porters-five-forces and + competitive-negotiation. Platform threat routes to + first-mover-strategy and prisoners-dilemma-and-cooperation. Paradigm + threat routes to disruptive-innovation and ai-vision-and-strategy." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Platform encroachment" + reason: "The greatest competitive threat to most SaaS companies is not a peer + startup but a platform (Microsoft, Google, Salesforce, HubSpot) + adding their feature natively. This threat is existential and + underestimated." + - diagnosis: "AI-driven category disruption" + reason: "General-purpose AI tools are replacing specialized SaaS products in + categories like writing, data analysis, code generation, and + customer support. This is the defining competitive threat of + 2024-2026." + less_likely: + - diagnosis: "Price-based competitive displacement" + reason: "SaaS customers rarely switch primarily on price. They switch on value, + experience, and capability. A competitor winning on price alone is + usually winning on something else that the company is not seeing." + saas_specific_diagnoses: + - name: "Feature-parity treadmill" + description: "The company is caught in a cycle of copying competitor features + rather than differentiating. Each quarter's roadmap is driven by + competitive gap analysis rather than customer value creation, leading + to a undifferentiated product that competes solely on price." + symptoms: + - "Product roadmap dominated by 'competitive parity' items" + - "Win/loss analysis showing 'features' as the primary win reason (not + differentiation or value)" + - "Engineering team demoralized by building features they know are + copies" + - "Pricing under pressure because the product is perceived as + interchangeable" + routes_to_skills: [ "blue-ocean-strategy", "disruptive-innovation", "porters-five-forces" ] + routes_to_templates: [ "competitive-landscape-brief", "strategic-analysis-one-pager" ] + sector_red_flags: + - "Win rate declining for three consecutive quarters without a clear + product or pricing explanation." + - "A platform partner announcing a native feature that overlaps with your + core value proposition." + - "A well-funded competitor (raised $50M+) entering your specific market + segment." + + # ───────────────────────────────────────────── + # 8. STRATEGIC DRIFT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "strategic-drift-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS strategic drift manifests as a misalignment between + product, GTM, pricing, and customer success strategies. The fast feedback + loops in SaaS make drift detectable earlier than in traditional businesses + but also make it more tempting to constantly shift direction." + additional_triage_questions: + - question: "Is your product roadmap aligned with your highest-retention customer + segment, or is it being pulled in multiple directions by different + customer types?" + purpose: "SaaS strategic drift often begins when the product tries to serve too + many segments simultaneously, building features for enterprise while + the core SMB base decays." + routing_impact: "Multi-segment pull routes to business-model-canvas for segment + clarification and strategic-thinking-and-alignment for organizational + focus." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Strategy-by-customer-request" + reason: "SaaS companies are uniquely vulnerable to building whatever the loudest + customer asks for, especially when that customer represents a + significant portion of revenue." + less_likely: + - diagnosis: "Industry disruption causing drift" + reason: "More often, drift in SaaS is self-inflicted (chasing every opportunity) + rather than externally caused." + saas_specific_diagnoses: + - name: "Premature upmarket drift" + description: "The company moves upmarket to pursue larger deals before + establishing dominance in its initial segment. Enterprise features are + added at the expense of the core product, the sales cycle lengthens, + and the company ends up competing in a market where it has no + advantage against established players." + symptoms: + - "ACV increasing but total customer count and growth rate declining" + - "Sales cycle doubling while win rate halves" + - "Product complexity increasing, onboarding time growing, self-serve + adoption declining" + - "Core customer segment NPS declining" + routes_to_skills: [ "disruptive-innovation", "blue-ocean-strategy", "product-life-cycle" ] + routes_to_templates: [ "strategic-analysis-one-pager", "decision-rationale-memo" ] + sector_red_flags: + - "Roadmap items traceable to fewer than 3 customer requests each — + building for individuals rather than segments." + - "Go-to-market strategy changing more than once per year without a + corresponding change in metrics." + + # ───────────────────────────────────────────── + # 9. TEAM DYSFUNCTION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "team-dysfunction-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS team dysfunction has characteristic patterns driven + by the cross-functional nature of the business — product, engineering, + sales, marketing, and customer success must coordinate tightly, and the + seams between these functions are where dysfunction most commonly + appears." + additional_triage_questions: + - question: "Is there tension between the sales team and the product team — + specifically, is sales selling features that do not exist or will the + product team not build what customers are asking for?" + purpose: "The sales-product tension is the most common and most damaging team + dysfunction in SaaS. It leads to customer dissatisfaction, missed + targets, and organizational distrust." + routing_impact: "Sales-product misalignment routes to + strategic-thinking-and-alignment and cooperative-negotiation for + internal alignment processes." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Cross-functional misalignment" + reason: "SaaS requires tighter cross-functional coordination than most + businesses. The handoffs between marketing-sales, sales-CS, + product-engineering, and CS-product are common failure points." + less_likely: + - diagnosis: "Individual performance issues" + reason: "What appears as individual underperformance in SaaS is often a + system-level problem — poor tools, unclear processes, or misaligned + incentives. Diagnose the system before blaming the individual." + saas_specific_diagnoses: + - name: "Sales-CS handoff failure" + description: "Customers are sold on expectations that customer success cannot + deliver. The handoff from sales to CS loses critical context, + implementation timelines are unrealistic, and customer dissatisfaction + spikes in the first 90 days of the relationship." + symptoms: + - "High churn concentrated in the first 90 days post-close" + - "CSMs reporting that customer expectations do not match what was + sold" + - "Sales team compensated only on bookings with no retention clawback" + - "No mutual success plan or implementation timeline created during + the sales process" + routes_to_skills: [ "trust-equation", "systems-thinking", "delegation-and-empowerment" ] + routes_to_templates: [ "action-plan", "onboarding-welcome-packet" ] + sector_red_flags: + - "Engineering team velocity declining while headcount increases — often a + sign of organizational overhead or architectural debt." + - "Customer success team attrition above 30% annually — CSMs burn out when + they cannot influence the product that causes customer complaints." + + # ───────────────────────────────────────────── + # 10. COFOUNDER CONFLICT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "cofounder-conflict-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "Co-founder conflict in SaaS often centers on technical + vs. commercial priorities — the CTO wants to rebuild the architecture + while the CEO wants to ship features for sales. SaaS-specific triage helps + identify whether the conflict is about direction (strategy) or execution + (roles and authority)." + additional_triage_questions: + - question: "Does the conflict center on product direction (what to build), + go-to-market strategy (how to sell), resource allocation (where to + invest), or equity/compensation (what each person deserves)?" + purpose: "SaaS co-founder conflicts cluster around these four categories. Each + has different resolution paths." + routing_impact: "Product direction conflicts route to + defining-and-exploring-problems and customer data analysis. GTM + conflicts route to balanced-scorecard and data-driven evaluation. + Resource conflicts route to scenario-planning. Equity conflicts route + to negotiation skills." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Role ambiguity between technical and commercial co-founders" + reason: "SaaS companies with a CEO/CTO co-founder pair frequently struggle with + the boundary between product decisions (shared) and technical + architecture decisions (CTO) and commercial decisions (CEO)." + less_likely: + - diagnosis: "Fundamental vision misalignment" + reason: "True vision misalignment is less common than role boundary confusion. + Most co-founders agree on the destination but disagree on the path." + saas_specific_diagnoses: + - name: "Build-vs-sell tension" + description: "The technical co-founder wants to invest in product quality, + architecture, and technical debt reduction. The commercial co-founder + wants to invest in sales, marketing, and customer-facing features. + Neither is wrong — but the inability to allocate resources creates + paralysis and resentment." + symptoms: + - "Product roadmap alternating between 'technical debt sprints' and + 'sales-driven feature rushes' without a coherent strategy" + - "Co-founders advocating in board meetings against each other's + priorities" + - "Team members learning to route requests to the more sympathetic + co-founder" + routes_to_skills: [ "cooperative-negotiation", "balanced-scorecard", "evaluating-and-deciding" ] + routes_to_templates: [ "decision-journal", "quarterly-strategic-review" ] + sector_red_flags: + - "Co-founders communicating through intermediaries rather than directly." + - "Key hires leaving because of conflicting direction from co-founders." + + # ───────────────────────────────────────────── + # 11. MARKET ENTRY DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "market-entry-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS market entry is primarily about segment selection + and GTM motion — the product can reach any market digitally, so the + question is not 'can we enter?' but 'should we enter, and how?' + SaaS-specific triage focuses on market sizing, competitive density, and + GTM model fit." + additional_triage_questions: + - question: "Have you validated demand through a landing page, waitlist, or beta + program — or are you estimating market size from top-down analysis?" + purpose: "SaaS market entry decisions should be validated bottom-up + (demonstrated demand) rather than top-down (TAM estimates). A waitlist + of 500 companies is more valuable than a $10B TAM slide." + routing_impact: "No validation routes to lean market testing before full entry. + Validated demand routes to GTM strategy and go-to-market execution." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Crowded category entry without differentiation" + reason: "SaaS markets are globally accessible, making most categories crowded. + Entry without clear differentiation leads to costly competition." + less_likely: + - diagnosis: "Market too small" + reason: "SaaS enables global reach and vertical specialization. Markets that + appear small domestically may be substantial globally." + saas_specific_diagnoses: + - name: "Category creation risk" + description: "The company is attempting to create a new SaaS category rather + than enter an existing one. Category creation requires educating the + market — a much more expensive and slower path than entering a + category where buyers already understand the problem and solution + type." + symptoms: + - "Prospects do not know what category to compare the product to" + - "Sales cycles are long because prospects must first understand the + problem before evaluating the solution" + - "G2/Capterra category does not exist for this product type" + routes_to_skills: [ "blue-ocean-strategy", "story-structure-and-arc", "four-ps-marketing" ] + routes_to_templates: [ "market-opportunity-summary", "fundraising-deck-outline" ] + sector_red_flags: + - "Entering a market with 5+ well-funded competitors without a clearly + articulated differentiation thesis." + - "Targeting enterprise from day one without enterprise sales experience + or a customer reference." + + # ───────────────────────────────────────────── + # 12. HIRING DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "hiring-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS hiring challenges center on the scarcity of + specialized talent (SaaS sales reps, product managers, growth marketers) + and the critical importance of early hires in setting the culture and + operational foundation." + additional_triage_questions: + - question: "Are you hiring to scale an existing function that works (e.g., adding + more sales reps to a proven sales motion) or hiring to build a + function that does not yet exist (e.g., first VP Sales, first product + manager)?" + purpose: "Scaling a working function requires execution hires. Building a new + function requires a leader who can define the playbook. Misidentifying + the hire type is the most common SaaS hiring mistake." + routing_impact: "Scaling a working function routes to structured hiring + processes and hiring-scorecard template. Building new function routes + to executive search principles and role-description-template with + emphasis on defining success criteria." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Hiring the wrong profile for the stage" + reason: "SaaS companies frequently hire executives from larger companies (VP + Sales from a $100M ARR company for a $2M ARR company) whose skills + do not transfer to the earlier stage." + less_likely: + - diagnosis: "Compensation competitiveness" + reason: "While important, compensation is rarely the primary reason SaaS hiring + fails. Mission, growth trajectory, equity, and team quality matter + more for early-stage hires." + saas_specific_diagnoses: + - name: "Premature specialization" + description: "The company hires specialists (demand gen marketer, SDR manager, + solutions architect) before the generalist playbook is established. + Specialists optimize processes that do not yet exist, leading to + wasted resources and organizational complexity." + symptoms: + - "Specialized hires with no one to report to or learn from in their + function" + - "Processes being built from scratch by individual contributors + without strategic direction" + - "Under $3M ARR with more than 5 distinct go-to-market roles" + routes_to_skills: [ "eisenhower-matrix", "delegation-and-empowerment" ] + routes_to_templates: [ "role-description-template", "hiring-scorecard" ] + sector_red_flags: + - "VP Sales hire failing within 6 months — the most common and most + expensive SaaS hiring mistake." + - "Engineering team spending more time onboarding new hires than building + product — a sign of hiring too fast." + + # ───────────────────────────────────────────── + # 13. OPERATIONAL CHAOS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "operational-chaos-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS operational chaos manifests as infrastructure + instability, deployment failures, billing errors, and support overwhelm. + The continuous nature of SaaS delivery (24/7 uptime, continuous + deployment) creates unique operational demands." + additional_triage_questions: + - question: "How frequently do you deploy to production, and what percentage of + deployments cause incidents?" + purpose: "Deployment frequency and failure rate are the two most diagnostic + operational health metrics in SaaS. Low frequency suggests fear of + shipping; high failure rate suggests inadequate testing and review." + routing_impact: "High deployment failure rate routes to engineering process + improvement. Low deployment frequency routes to CI/CD and DevOps + investment." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Technical debt overwhelming operations" + reason: "SaaS companies that grow fast accumulate technical debt that eventually + consumes engineering capacity, causes outages, and slows product + development." + less_likely: + - diagnosis: "Process deficiency" + reason: "Early-stage SaaS companies often have too much process (imported from + larger companies) rather than too little. The diagnosis may be + over-process, not under-process." + saas_specific_diagnoses: + - name: "Support-driven engineering" + description: "Customer support volume is so high that engineering spends the + majority of time fixing customer-specific issues rather than building + product improvements. The product does not improve, generating more + support tickets in a reinforcing loop." + symptoms: + - "More than 30% of engineering capacity consumed by support + escalations" + - "Support ticket volume growing faster than customer count" + - "No self-serve knowledge base, in-app help, or automated + troubleshooting" + - "Customer success and support teams with direct Slack channels to + engineers for 'urgent' issues" + routes_to_skills: [ "systems-thinking", "eisenhower-matrix" ] + routes_to_templates: [ "action-plan", "incident-postmortem" ] + sector_red_flags: + - "Uptime below 99.5% over any 30-day period — customers will leave for + more reliable alternatives." + - "Mean time to resolution for P0 incidents exceeding 4 hours." + + # ───────────────────────────────────────────── + # 14. LEADERSHIP CRISIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "leadership-crisis-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership crises in SaaS follow the same patterns as in + other venture-backed companies. The base diagnostic covers founder + burnout, board conflicts, executive team dysfunction, and crisis + management without requiring SaaS-specific modification." + additional_triage_questions: [] + diagnosis_weight_shifts: + more_likely: [] + less_likely: [] + saas_specific_diagnoses: [] + sector_red_flags: + - "CEO making reactive, metric-driven decisions without strategic framing + — a sign of losing the forest for the trees in a data-rich environment." + + # ───────────────────────────────────────────── + # 15. DECISION PARALYSIS DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "decision-paralysis-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS provides abundant data, which paradoxically can + increase decision paralysis. Founders waiting for 'enough data' before + making pricing, product, or GTM decisions often delay beyond the point + where the decision would have generated useful learning." + additional_triage_questions: + - question: "Is the decision reversible or irreversible? Can you test a smaller + version before committing fully?" + purpose: "Most SaaS decisions are reversible (pricing, features, campaigns). + Treating reversible decisions with irreversible-decision rigor causes + paralysis." + routing_impact: "Reversible decision paralysis routes to evaluating-and-deciding + with emphasis on speed. Irreversible decisions route to + tough-decision-situations for deeper analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Analysis paralysis driven by data abundance" + reason: "SaaS dashboards provide infinite data to analyze. 'One more week of + data' is the most seductive form of decision avoidance." + less_likely: + - diagnosis: "Insufficient information" + reason: "SaaS companies rarely lack information. They lack clarity on which + information matters and the willingness to act on imperfect data." + saas_specific_diagnoses: [] + sector_red_flags: + - "Pricing decision delayed more than 3 months — pricing is always + imperfect and always adjustable." + - "Product decisions requiring consensus from more than 3 people — a sign + of unclear decision authority." + + # ───────────────────────────────────────────── + # 16. INNOVATION DROUGHT DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "innovation-drought-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS innovation droughts manifest as feature stagnation — + the product stops evolving, competitors close the gap, and customers lose + enthusiasm. The continuous delivery model means that innovation drought is + visible immediately in declining activation rates and stagnant NPS." + additional_triage_questions: + - question: "What percentage of engineering capacity is allocated to new features + versus maintenance, technical debt, and support?" + purpose: "If more than 50% of engineering capacity goes to maintenance and debt, + innovation will stall regardless of team talent." + routing_impact: "Maintenance-dominated allocation routes to technical debt + assessment and eisenhower-matrix for engineering prioritization." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Technical debt consuming innovation capacity" + reason: "SaaS companies that shipped fast to achieve PMF often accumulated debt + that now prevents further innovation." + less_likely: + - diagnosis: "Lack of creative talent" + reason: "SaaS teams are generally well-educated and creative. Innovation drought + is more often a system failure (wrong incentives, too much process, + insufficient time) than a talent failure." + saas_specific_diagnoses: + - name: "Customer-driven roadmap trap" + description: "The roadmap is entirely dictated by customer requests and support + tickets. No capacity is allocated to proactive innovation — building + features customers have not asked for but would love. The product + incrementally improves existing workflows but never creates new + value." + symptoms: + - "Every roadmap item traceable to a specific customer request" + - "No 'surprise and delight' features shipped in the last 6 months" + - "NPS stable but not improving — customers are satisfied, not + enthusiastic" + - "No features that generated organic social media discussion or viral + sharing" + routes_to_skills: + [ + "disruptive-innovation", + "blue-ocean-strategy", + "creative-identity-and-purpose" + ] + routes_to_templates: [ "new-initiative-brief", "quarterly-strategic-review" ] + sector_red_flags: + - "NPS declining for 2+ consecutive quarters despite no major incidents." + - "Competitor launch announcements generating customer inquiries about 'do + you have that?'" + + # ───────────────────────────────────────────── + # 17. PARTNERSHIP DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "partnership-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS partnerships are ecosystem-driven — integrations, + channel partnerships, and platform relationships are growth levers that do + not exist in the same form in traditional businesses. The diagnostic must + account for the unique dynamics of technology partnerships." + additional_triage_questions: + - question: "Is this a technology integration partnership (building together), a + channel partnership (selling together), or a platform partnership + (building on top of them)?" + purpose: "Each partnership type has different economics, power dynamics, and + risks. A platform partnership where you build on their API puts you in + a dependency relationship that does not exist in a co-selling + arrangement." + routing_impact: "Technology integration routes to cooperative-negotiation with + emphasis on mutual value. Channel partnership routes to + four-ps-marketing for distribution strategy. Platform partnership + routes to prisoners-dilemma-and-cooperation for dependency risk + analysis." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Asymmetric dependency" + reason: "SaaS partnerships often involve significant size asymmetry. A 50-person + SaaS company partnering with Salesforce or HubSpot faces inherently + asymmetric power dynamics." + less_likely: + - diagnosis: "Cultural misalignment" + reason: "SaaS partnerships are primarily technical and commercial. Cultural fit + matters less than API quality, economic alignment, and strategic + overlap." + saas_specific_diagnoses: + - name: "Integration as strategy substitute" + description: "The company builds integrations with every possible platform + without a coherent partnership strategy. Integrations consume + engineering resources but do not generate measurable revenue or + retention impact because they are not promoted, supported, or + monetized." + symptoms: + - "More than 20 integrations but none generating measurable revenue" + - "No tracking of which integrations correlate with retention" + - "Integrations built reactively (customer requests) not strategically" + - "Engineering maintaining integrations that fewer than 5% of + customers use" + routes_to_skills: [ "eisenhower-matrix", "balanced-scorecard", "systems-thinking" ] + routes_to_templates: [ "partnership-memo", "strategic-analysis-one-pager" ] + sector_red_flags: + - "A platform partner announcing a native feature that competes with your + core product." + - "More than 30% of revenue dependent on a single channel partner." + + # ───────────────────────────────────────────── + # 18. COMMUNICATION BREAKDOWN DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "communication-breakdown-diagnosis" + sector_adaptation: "as-is" + adaptation_rationale: "Communication breakdowns in SaaS follow the same patterns + as in other technology companies — remote/hybrid work challenges, + cross-functional misalignment, and scaling communication as the team + grows. The base diagnostic covers these adequately." + additional_triage_questions: [] + diagnosis_weight_shifts: + more_likely: [] + less_likely: [] + saas_specific_diagnoses: [] + sector_red_flags: + - "Product and sales teams using different language to describe the same + features — a sign of internal communication failure that propagates to + customers." + + # ───────────────────────────────────────────── + # 19. NEGOTIATION STUCK DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "negotiation-stuck-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS negotiations get stuck in characteristic ways: + enterprise procurement processes that demand terms the startup cannot + offer, investor negotiations that stall on valuation or control terms, and + platform partnership negotiations where the power asymmetry is extreme." + additional_triage_questions: + - question: "Is the negotiation stuck on commercial terms (price, discount, + payment terms), legal terms (liability, data processing, IP), or + strategic terms (exclusivity, roadmap commitments, partnership + scope)?" + purpose: "SaaS negotiations stall for different reasons. Commercial stalls often + resolve with creative packaging. Legal stalls require legal expertise. + Strategic stalls require executive involvement." + routing_impact: "Commercial stalls route to pricing-diagnosis and + competitive-negotiation. Legal stalls route to delivering-the-deal + with emphasis on template preparation. Strategic stalls route to + cooperative-negotiation and scenario-planning." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Security/compliance review blocking the deal" + reason: "Enterprise SaaS sales increasingly stall during security review. SOC 2 + Type II, penetration test results, and GDPR compliance are + table-stakes requirements that some startups are unprepared for." + less_likely: + - diagnosis: "Fundamental value disagreement" + reason: "If the negotiation reached the terms stage, value has been established. + Most SaaS negotiation stalls are procedural, not substantive." + saas_specific_diagnoses: [] + sector_red_flags: + - "Enterprise deals stalling for 60+ days in legal/security review — + indicates the company needs a 'deal acceleration kit' (pre-prepared + security documents, DPA, and flexible order forms)." + + # ───────────────────────────────────────────── + # 20. CULTURE EROSION DIAGNOSIS + # ───────────────────────────────────────────── + + - diagnostic: "culture-erosion-diagnosis" + sector_adaptation: "enhanced" + adaptation_rationale: "SaaS companies experience predictable culture erosion at + specific scale thresholds — 15-20 employees (first departmental silos), + 50-80 employees (loss of all-hands intimacy), and 150+ employees (Dunbar's + number, where personal relationships can no longer sustain culture). The + base diagnostic benefits from recognizing these SaaS growth-stage culture + patterns." + additional_triage_questions: + - question: "Has the company recently crossed a team-size threshold (15, 50, 150 + employees), and did culture practices evolve to match?" + purpose: "Culture practices that work at 10 people fail at 50. The practices + must evolve with scale — written values, structured onboarding, + explicit communication norms, and formalized recognition." + routing_impact: "Recent threshold crossing routes to organisational-culture and + leading-through-change for proactive culture evolution." + diagnosis_weight_shifts: + more_likely: + - diagnosis: "Growth outpacing culture infrastructure" + reason: "SaaS companies that hire rapidly (doubling headcount annually) + frequently outpace their ability to onboard, integrate, and + acculturate new team members." + less_likely: + - diagnosis: "Toxic leadership" + reason: "While possible, culture erosion in fast-growing SaaS is more often + caused by neglect (no one is responsible for culture) than malice + (someone is actively degrading it)." + saas_specific_diagnoses: + - name: "Remote-first culture void" + description: "The company transitioned to remote or hybrid work without building + the intentional culture infrastructure that remote teams require. + Informal culture transmission (hallway conversations, lunch + discussions, overhearing leadership decisions) no longer happens, and + nothing has replaced it." + symptoms: + - "New hires reporting feeling disconnected after 90 days" + - "Cross-team collaboration declining — teams default to silos" + - "Declining participation in optional company events" + - "Employee NPS declining despite competitive compensation and + interesting work" + routes_to_skills: + [ + "organisational-culture", + "psychological-safety-practice", + "team-culture-and-dynamics" + ] + routes_to_templates: [ "culture-values-document", "team-health-check", "offsite-planning-guide" ] + sector_red_flags: + - "Regrettable attrition above 15% annually — top performers leaving + voluntarily signals cultural problems before surveys detect them." + - "Glassdoor rating declining more than 0.5 stars in 6 months." diff --git a/plugins/foreman/content/industry-packs/saas/saas-skill-overlays.yaml b/plugins/foreman/content/industry-packs/saas/saas-skill-overlays.yaml new file mode 100644 index 0000000..f2b0887 --- /dev/null +++ b/plugins/foreman/content/industry-packs/saas/saas-skill-overlays.yaml @@ -0,0 +1,1505 @@ +# SaaS Industry Pack — Skill Overlays +# +# For 40 of the 158 Foreman skills, this file provides SaaS-specific context +# that the skill executor agent applies as additional framing. These overlays +# do not replace the base skill content — they add a SaaS lens. +# +# Selection criteria for the 40 skills: +# - Frameworks with direct SaaS application (strategy, pricing, growth) +# - Decision and thinking skills (used constantly in SaaS operator contexts) +# - Negotiation skills (fundraising, partnerships, enterprise sales) +# - Leadership skills most affected by SaaS organizational dynamics +# - Game theory skills applicable to SaaS competitive strategy +# +# Relevance tiers: +# critical — The SaaS overlay materially changes how the skill is applied. +# The skill executor should always surface SaaS context. +# high — SaaS context adds significant value. Surface when relevant. +# moderate — Useful SaaS framing but the base skill works well as-is. + +pack_metadata: + sector: "saas" + display_name: "SaaS" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# SKILL OVERLAYS +# ═══════════════════════════════════════════════════════════════ + +skill_overlays: + + # ───────────────────────────────────────────── + # FRAMEWORKS (22 skills) + # ───────────────────────────────────────────── + + - skill: "porters-five-forces" + category: "frameworks" + saas_relevance: "critical" + saas_context: "SaaS fundamentally reshapes three of the five forces. Buyer power + is amplified by low switching costs and monthly contracts — customers can + leave at any renewal. Threat of substitutes is extreme because SaaS + products compete not just with direct alternatives but with spreadsheets, + no-code tools, and internal builds. Rivalry intensity is high because SaaS + markets tend toward winner-take-most dynamics driven by network effects + and data moats." + saas_anti_patterns: + - "Assuming high switching costs exist because the product has an API or + integrations. True switching costs in SaaS come from workflow dependency + and data lock-in, not technical integrations that competitors can + replicate." + - "Ignoring the 'threat of non-consumption' — many SaaS markets compete + not with other software but with manual processes or no solution at + all." + - "Treating supplier power as irrelevant. Cloud infrastructure (AWS, GCP, + Azure) and key API providers (Stripe, Twilio) can raise prices, change + terms, or become competitors." + saas_example: "A vertical SaaS company serving dental practices uses Porter's + Five Forces to discover that while direct competitors are few, the real + competitive threat is from general-purpose EHR systems expanding into + dental and from dental practice management consultants who recommend + bespoke solutions. Supplier power is concentrated in a single insurance + clearinghouse API. This analysis shifts the company's strategy from + feature competition to building the deepest dental-specific data asset — + the one force competitors cannot easily replicate." + benchmark_references: [ "nrr", "logo-churn", "win-rate" ] + + - skill: "blue-ocean-strategy" + category: "frameworks" + saas_relevance: "critical" + saas_context: "Blue ocean strategy is structurally essential for SaaS because + most categories are crowded — G2 lists 100+ competitors in major + categories. The strategy-canvas exercise maps features and price against + incumbents, revealing where the market over-serves (complex enterprise + features no one uses) and under-serves (simplicity, speed, specific + vertical workflows). SaaS blue oceans are most commonly found in vertical + niches, in underserved buyer personas within existing categories, or in + reimagining the delivery model (PLG vs. enterprise sales in a + traditionally sales-led category)." + saas_anti_patterns: + - "Pursuing a blue ocean that is actually a dry ocean — creating an + uncontested space because no customers exist there. Validate demand + before investing in differentiation." + - "Confusing feature novelty with strategic differentiation. Adding AI or + a new UI to a commodity product does not create a blue ocean if the + buyer's decision criteria remain price and integrations." + - "Abandoning a blue ocean too early by moving upmarket into red ocean + enterprise competition before dominating the niche." + saas_example: "Linear launched into the project management space — one of the + most crowded SaaS categories — by deliberately eliminating features (Gantt + charts, resource management, portfolio views) and obsessing over speed, + keyboard shortcuts, and developer experience. The blue ocean was + 'engineering teams who hate slow, bloated project management tools.' By + saying no to enterprise PM features, Linear created uncontested space that + Jira, Asana, and Monday.com could not address without cannibalizing their + existing products." + benchmark_references: [ "activation-rate", "time-to-value", "nps-saas" ] + + - skill: "business-model-canvas" + category: "frameworks" + saas_relevance: "critical" + saas_context: "The Business Model Canvas requires SaaS-specific interpretation + across nearly every block. Revenue Streams must decompose into MRR + components (new, expansion, contraction, churn). Customer Relationships + must distinguish self-serve, sales-assisted, and enterprise motions. Key + Resources must include the codebase, data assets, and cloud + infrastructure. Cost Structure must separate COGS (hosting, support) from + operating expenses (R&D, S&M, G&A) because SaaS unit economics depend on + this distinction. The canvas is most powerful when used to compare + current-state and target-state models — for example, mapping the shift + from a services-heavy implementation model to a product-led growth model." + saas_anti_patterns: + - "Treating 'software' as the sole Value Proposition. The product is the + delivery mechanism, not the value. Value in SaaS is the outcome: time + saved, revenue generated, risk reduced." + - "Omitting Customer Success from Key Activities. In SaaS, post-sale + retention and expansion are as critical as acquisition." + - "Filling the canvas once and filing it away. SaaS models evolve rapidly + — the canvas should be revisited quarterly as pricing, channels, and + customer segments shift." + saas_example: "A B2B SaaS founder uses the canvas to articulate why their + current model is capital-inefficient. The canvas reveals that their Key + Activity is dominated by custom onboarding (a services cost buried in + COGS), their Customer Segment is too broad (serving SMB and enterprise + with one product), and their Revenue Stream is flat-rate monthly — no + expansion path. The canvas redesign introduces usage-based pricing, + self-serve onboarding for SMB, and a dedicated enterprise tier, + transforming the economics." + benchmark_references: [ "gross-margin", "arpu", "cac", "ltv" ] + + - skill: "four-ps-marketing" + category: "frameworks" + saas_relevance: "critical" + saas_context: "The traditional Four Ps require substantial adaptation for SaaS. + Product is a living, evolving service — not a shipped good. Customers buy + access, not ownership. Price in SaaS is a strategic lever with unique + structures: per-seat, usage-based, tiered, freemium, flat-rate, and hybrid + models. Each pricing structure changes customer behavior, expansion + dynamics, and unit economics. Place means distribution channel — PLG + (product is the channel), content marketing, outbound sales, partnerships, + marketplaces. Promotion in SaaS emphasizes content marketing, community, + product-led virality, and thought leadership over traditional + advertising." + saas_anti_patterns: + - "Treating pricing as a one-time decision. SaaS pricing should be + revisited at least annually and tested continuously. Most SaaS companies + under-price by 20-40%." + - "Equating 'Place' with a website. Distribution strategy in SaaS + encompasses app store presence, API marketplace listings, integration + directories, partner channels, and the product itself as a distribution + mechanism." + - "Running demand-gen campaigns (Promotion) without tracking the full + funnel to revenue. SaaS marketing must be measured on pipeline + contribution and CAC, not impressions or clicks." + saas_example: "A project management SaaS applies the Four Ps to restructure its + go-to-market. Product: they separate the core product from add-on modules + (analytics, time tracking, resource management). Price: they shift from + flat-rate to per-seat with usage-based add-ons, creating natural expansion + revenue. Place: they launch a free tier (PLG) alongside their existing + sales motion, making the product itself a distribution channel. Promotion: + they invest in a template library and community rather than paid ads, + reducing CAC by 40%." + benchmark_references: [ "cac", "arpu", "acv", "expansion-revenue-pct" ] + + - skill: "net-promoter-score" + category: "frameworks" + saas_relevance: "critical" + saas_context: "NPS is deeply embedded in SaaS operating culture because of its + correlation with net revenue retention. In SaaS, NPS surveys should be + triggered by product usage milestones (not arbitrary time intervals), + segmented by plan tier and customer cohort, and directly linked to churn + prediction models. The actionable power of NPS in SaaS comes not from the + score itself but from the qualitative feedback in the open-ended follow-up + question and from tracking score changes over the customer lifecycle." + saas_anti_patterns: + - "Surveying all customers at the same time (quarterly blast) instead of + using event-triggered NPS after key moments (onboarding completion, + first renewal, support resolution)." + - "Optimizing for the NPS number rather than acting on detractor feedback. + A rising NPS score that masks unresolved product issues is worse than a + flat score with systematic feedback loops." + - "Treating Promoters as a marketing asset without building referral and + advocacy programs. Promoters in SaaS drive viral growth — but only if + you give them mechanisms to refer and share." + saas_example: "A mid-market SaaS company segments NPS by customer cohort and + discovers that NPS drops sharply after month 6 — not at onboarding (where + the score is 60+). Investigation reveals that customers exhaust the + product's value within 6 months and hit a ceiling. This insight triggers a + product roadmap shift toward deeper functionality and advanced use cases, + directly addressing the retention cliff that NPS exposed." + benchmark_references: [ "nps-saas", "nrr", "logo-churn" ] + + - skill: "product-life-cycle" + category: "frameworks" + saas_relevance: "critical" + saas_context: "SaaS disrupted the traditional product lifecycle by enabling + continuous delivery and iterative improvement. Products no longer 'launch' + once — they evolve weekly. The lifecycle stages still apply but compress + and overlap: Introduction is the beta/early access period, Growth + coincides with product-market fit and scaling, Maturity arrives when NRR + stabilizes and new customer growth slows, and Decline manifests as + category commoditization or platform shift. The critical SaaS insight is + that individual features within a product may be at different lifecycle + stages simultaneously." + saas_anti_patterns: + - "Assuming SaaS products are immune to maturity and decline because they + can be updated. SaaS categories mature — CRM, email marketing, and + project management are all mature categories where differentiation is + extremely difficult." + - "Investing equally across all features regardless of their lifecycle + position. Features in decline should be sunset; features in growth + should receive disproportionate investment." + - "Confusing product-market fit with permanent market position. SaaS + markets shift rapidly; what was innovative two years ago becomes table + stakes." + saas_example: "Zendesk's core help desk product reached maturity by 2018 — NRR + was stabilizing, and competitors like Intercom and Freshdesk were eroding + differentiation. Rather than fighting for share in a maturing category, + Zendesk expanded into a suite (Sell, Chat, Guide), effectively launching + new products at the Introduction stage while managing the mature core. The + product lifecycle framework helps SaaS companies decide when to extend the + platform versus when to accept maturity in the core and invest in + adjacencies." + benchmark_references: [ "nrr", "mom-growth-rate", "nps-saas" ] + + - skill: "growth-share-matrix" + category: "frameworks" + saas_relevance: "high" + saas_context: "The BCG Growth-Share Matrix maps directly to SaaS product + portfolio management. Stars are fast-growing products or modules with + strong market share — they justify aggressive investment. Cash Cows are + mature product lines with stable revenue and high margins — they fund + investment in Stars. Question Marks are new product lines or market + segments with high growth but unproven position. Dogs are features or + modules that consume resources without generating growth or profit. For + SaaS companies with multiple products or a platform play, this framework + guides resource allocation across the portfolio." + saas_anti_patterns: + - "Treating the entire SaaS product as a single unit. The matrix is most + useful when applied to product lines, modules, customer segments, or + geographic markets within the company." + - "Killing 'Dog' features that are actually critical for retention or + serve as table-stakes requirements for enterprise buyers." + - "Over-investing in Stars without building the operational infrastructure + (customer success, support, documentation) to sustain growth." + saas_example: "HubSpot's portfolio maps cleanly to the matrix: Marketing Hub + (Cash Cow — mature, high share), Sales Hub (Star — growing, gaining + share), Service Hub (Question Mark — growing market, still proving + position), CMS Hub (Dog — small market, limited differentiation). This + framing helps explain HubSpot's investment priorities and organizational + structure." + benchmark_references: [ "arr", "mom-growth-rate", "gross-margin" ] + + - skill: "disruptive-innovation" + category: "frameworks" + saas_relevance: "critical" + saas_context: "SaaS is the canonical vehicle for disruptive innovation. The + pattern repeats endlessly: an incumbent serves the high end of the market + with feature-rich, expensive software (Oracle, SAP, Salesforce + enterprise). A SaaS startup enters at the bottom with a simpler, cheaper, + self-serve product that the incumbent ignores. Over time, the SaaS product + improves, moves upmarket, and captures the mainstream. This pattern drove + the rise of Salesforce (vs. Siebel), Slack (vs. Microsoft), HubSpot (vs. + Marketo/Eloqua), and Figma (vs. Adobe). Understanding disruptive + innovation helps SaaS founders position correctly — start simple, serve + the over-served, and improve relentlessly." + saas_anti_patterns: + - "Trying to compete on features with the incumbent from day one. + Disruption requires starting with a 'worse' product on traditional + metrics that is better on a new dimension (simpler, cheaper, faster)." + - "Moving upmarket too early, before establishing dominance in the low-end + or niche segment. Premature enterprise motions destroy startups." + - "Ignoring the sustaining innovation response. Incumbents will eventually + respond with their own simpler offering — the disruptor must build + defensibility (data, network effects, integrations) before that + happens." + saas_example: "Figma disrupted Adobe's design tool dominance by starting with a + browser-based, free-for-individual-use product that professional designers + initially dismissed as a toy. Figma was 'worse' on feature depth but + better on collaboration, accessibility, and speed. By the time Adobe + recognized the threat and attempted to acquire Figma, the product had + captured the workflow of an entire generation of designers — the + disruption was complete." + benchmark_references: [ "activation-rate", "time-to-value", "arpu" ] + + - skill: "balanced-scorecard" + category: "frameworks" + saas_relevance: "critical" + saas_context: "The Balanced Scorecard translates directly into SaaS operating + metrics across its four perspectives. Financial: MRR/ARR, burn multiple, + Rule of 40, gross margin. Customer: NPS, NRR, logo churn, time to value. + Internal Process: deployment frequency, incident response time, onboarding + completion rate, support ticket resolution time. Learning & Growth: + engineering velocity, employee NPS, skill development investment. The + scorecard is particularly powerful in SaaS because the subscription model + generates rich, real-time data for all four perspectives, enabling weekly + or even daily tracking rather than quarterly reviews." + saas_anti_patterns: + - "Tracking too many metrics. A SaaS scorecard should contain 12-16 KPIs, + not 50. Each metric must have a clear owner and a clear action when it + deviates." + - "Ignoring the Learning & Growth perspective. SaaS companies that + under-invest in engineering culture, tooling, and talent development + accumulate technical debt that eventually manifests in the other three + perspectives." + - "Using the scorecard purely for reporting rather than as a + decision-making tool. The scorecard should drive weekly executive team + discussions and resource allocation decisions." + saas_example: "A Series B SaaS company implements a balanced scorecard with four + KPIs per perspective: Financial (ARR growth, burn multiple, gross margin, + NRR), Customer (NPS, logo churn, activation rate, support CSAT), Internal + Process (deploy frequency, P0 incident rate, onboarding time, feature + adoption rate), Learning & Growth (employee NPS, engineering velocity, + internal mobility rate, training hours per engineer). The scorecard + reveals that declining NPS and rising churn correlate with a spike in P0 + incidents — an internal process failure is driving customer outcomes." + benchmark_references: [ "arr", "burn-multiple", "rule-of-40", "nrr", "nps-saas", "gross-margin" ] + + - skill: "swot-pest-analysis" + category: "frameworks" + saas_relevance: "high" + saas_context: "SWOT and PEST analysis in SaaS must account for the unique + environmental forces shaping the sector. Political: data privacy + regulation (GDPR, CCPA, emerging AI regulation) directly impacts SaaS + product design and go-to-market. Economic: interest rate environments + affect SaaS valuations, customer IT budgets, and fundraising conditions. + Social: remote work adoption, buyer preference for self-serve purchasing, + and the consumerization of enterprise software. Technological: AI/ML + capabilities, cloud infrastructure evolution, API ecosystem maturity, and + platform risk from AWS/Google/Microsoft building competing features." + saas_anti_patterns: + - "Listing 'technology' as a strength without specificity. Every SaaS + company has technology. The question is what specific technical + capability creates defensible advantage." + - "Ignoring platform risk in the PEST analysis. If AWS, Google, or + Microsoft can build your product as a feature of their platform, that is + a material threat." + - "Conducting SWOT as a one-time exercise rather than a quarterly refresh. + SaaS competitive dynamics shift rapidly — a strength today (e.g., AI + capabilities) becomes table stakes in 12 months." + saas_example: "A SaaS company providing compliance automation uses PEST to + identify that upcoming AI regulation in the EU will create mandatory + compliance requirements for any company deploying AI systems — a massive + tailwind for their product. The SWOT reveals that while they have a strong + SMB customer base (Strength), they lack enterprise sales capabilities + (Weakness) and enterprise compliance buyers are the primary beneficiaries + of the regulatory shift (Opportunity). This analysis triggers a strategic + decision to hire an enterprise sales leader and build SOC 2 Type II + certification before competitors." + benchmark_references: [ "arr", "win-rate" ] + + - skill: "scenario-planning" + category: "frameworks" + saas_relevance: "high" + saas_context: "Scenario planning in SaaS must account for the high-variance + nature of software businesses. The three most critical scenario dimensions + are: growth rate (acceleration vs. deceleration vs. stall), capital + markets (available vs. constrained), and competitive dynamics (stable vs. + new entrant vs. incumbent pivot). SaaS companies should maintain at least + three financial scenarios (base, upside, downside) with explicit trigger + points that signal which scenario is materializing. The planning horizon + for SaaS is typically shorter than traditional industries — 18-24 months + is the practical limit given the pace of market change." + saas_anti_patterns: + - "Building scenarios that are all variations of 'things go well.' True + scenario planning requires at least one scenario where a core assumption + fails — the largest customer churns, a competitor raises $100M, or a + platform partner enters the space." + - "Treating the financial model as the scenario plan. Scenarios must + include strategic responses, not just different revenue lines. What + changes operationally in each scenario?" + - "Ignoring the capital markets scenario. A SaaS company's strategic + options depend heavily on whether fundraising is available. The + 2022-2023 market correction demonstrated how quickly this variable can + change." + saas_example: "A Series A SaaS company builds three scenarios for the next 18 + months: (1) Base: 2.5x YoY growth, Series B in 12 months at current + trajectory. (2) Upside: 3x+ growth triggered by a key integration launch, + enabling a larger Series B. (3) Downside: growth slows to 1.5x due to a + new competitor, requiring 6 months of runway extension through cost cuts + before attempting Series B. Each scenario has explicit metric triggers + (monthly ARR growth rate crossing specific thresholds) and pre-committed + strategic responses." + benchmark_references: [ "arr", "mom-growth-rate", "burn-multiple" ] + + - category: "frameworks" + saas_relevance: "critical" + saas_context: "Pricing is the most powerful and most neglected lever in SaaS. A + 1% improvement in pricing yields greater profit impact than a 1% + improvement in customer acquisition or cost reduction. SaaS pricing + diagnosis must evaluate: pricing model (per-seat, usage-based, tiered, + flat-rate, hybrid), packaging (feature gating, tier structure, add-ons), + price point (willingness-to-pay research, competitive positioning), and + discounting discipline (deal desk governance, annual vs. monthly pricing + spread). The diagnosis should also assess whether the pricing structure + creates natural expansion revenue — products with usage-based or per-seat + pricing grow within accounts automatically." + saas_anti_patterns: + - "Setting price based on cost-plus or competitor-matching rather than + value-based pricing. SaaS products deliver value that far exceeds their + cost to serve — pricing should capture a fair share of that value." + - "Offering monthly and annual plans with insufficient annual discount + spread. The standard is 15-20% annual discount, which should fund the + higher cost-to-serve of monthly subscribers." + - "Giving the sales team unlimited discounting authority. Uncontrolled + discounting destroys ARPU trends and signals that the list price lacks + credibility." + saas_example: "A B2B SaaS company discovers through pricing diagnosis that their + $49/month flat-rate plan serves customers ranging from 2-person startups + to 200-person companies. The largest customers derive 50x more value but + pay the same price. Shifting to per-seat pricing with a $15/seat/month + base and $25/seat/month professional tier triples ARPU from power users + while maintaining accessibility for small teams. Expansion revenue jumps + from 5% to 35% of new MRR within two quarters." + benchmark_references: [ "arpu", "acv", "expansion-revenue-pct", "nrr" ] + kind: diagnostic + ref: pricing-diagnosis + + - skill: "doblin-ten-types" + category: "frameworks" + saas_relevance: "high" + saas_context: "The Ten Types of Innovation framework is particularly instructive + for SaaS because software companies tend to over-index on Product + Performance innovation (features) while ignoring the other nine types. The + most powerful SaaS innovations often come from Profit Model (usage-based + pricing), Network (integrations and ecosystems), Structure (remote-first + teams), Process (CI/CD and rapid iteration), Channel (product-led growth), + Customer Engagement (community-led growth), and Service (self-serve + onboarding). Mapping innovation efforts across all ten types reveals where + the company is under-investing." + saas_anti_patterns: + - "Treating product features as the only innovation vector. Adding + features to a commoditized category does not create differentiation — + innovating on distribution, pricing, or customer experience does." + - "Ignoring Network innovation. In SaaS, integrations and ecosystem + effects are among the strongest defensibility moats. A product with 200 + integrations is harder to displace than one with better features." + - "Skipping the Profit Model type. The shift from perpetual license to + subscription was itself a Profit Model innovation. The next wave + (usage-based, outcome-based) is equally transformative." + saas_example: "Notion's success maps across multiple innovation types: Product + Performance (flexible blocks system), Channel (freemium PLG distribution), + Customer Engagement (template gallery and community), Brand + (design-centric positioning), and Network (API and integrations + ecosystem). Their competitors focused narrowly on Product Performance. + Notion's multi-type innovation created compound defensibility." + benchmark_references: [ "activation-rate", "nps-saas", "nrr" ] + + - skill: "eisenhower-matrix" + category: "frameworks" + saas_relevance: "high" + saas_context: "SaaS founders and operators face extreme prioritization + challenges because everything feels urgent — customers requesting + features, infrastructure incidents, investor reporting, hiring, and + competitive responses all compete for attention. The Eisenhower Matrix in + SaaS must specifically classify: customer escalations (Urgent/Important + vs. Urgent/Not Important — most escalations fall in the latter), feature + requests (most are Not Urgent/Not Important for the roadmap), + infrastructure investment (Not Urgent/Important — consistently + deprioritized until a crisis moves it to Urgent/Important), and strategic + work (Not Urgent/Important — the quadrant that determines long-term + success)." + saas_anti_patterns: + - "Treating every customer request as Urgent and Important. Most customer + requests are Urgent (to the customer) but Not Important (to the product + strategy). Conflating these destroys roadmap discipline." + - "Neglecting the Not Urgent/Important quadrant (strategic planning, + technical debt reduction, team development) because the daily urgency of + a SaaS operation consumes all cycles." + - "Delegating product decisions that should not be delegated. In + early-stage SaaS, the founder's product judgment is a critical asset — + some 'Important' decisions cannot be delegated until the product vision + is deeply shared." + saas_example: "A SaaS CEO uses the Eisenhower Matrix during a board preparation + week and realizes that 70% of their time is spent in Urgent/Not Important: + responding to customer support escalations that the support team should + handle, reviewing every pull request, and attending standing meetings with + no clear agenda. Delegating these frees 15 hours per week for Not + Urgent/Important work: defining the 12-month product vision, building + relationships with strategic partners, and developing the leadership + team." + benchmark_references: [] + + - skill: "kotter-change-model" + category: "frameworks" + saas_relevance: "moderate" + saas_context: "Kotter's eight-step change model applies to SaaS companies during + pivots, pricing restructures, go-to-market transitions, and organizational + scaling. The model is most relevant when a SaaS company shifts from + founder-led sales to a sales team, transitions from self-serve to + enterprise, or restructures pricing. Step 1 (Create Urgency) is often + supplied by metrics — declining NRR, rising churn, or missed targets + provide the data-driven urgency that motivates change. Step 5 (Remove + Obstacles) in SaaS frequently means addressing technical debt, legacy + architecture, or organizational silos between product, sales, and customer + success." + saas_anti_patterns: + - "Skipping the coalition-building steps in a fast-moving SaaS + environment. 'Move fast and break things' does not apply to + organizational change — resistance from the sales team or engineering + organization can kill a pricing restructure." + - "Announcing change without demonstrating 'quick wins' first. In SaaS, + pilot programs (test new pricing with a segment, trial new sales motion + with one team) build evidence before full rollout." + saas_example: "A SaaS company transitions from monthly subscription pricing to + usage-based pricing. Using Kotter's model, leadership creates urgency by + showing that 40% of customers are on plans that undercharge relative to + usage. They form a coalition including the VP Sales, VP Product, and the + largest customer success manager. The 'quick win' is a pilot with 50 + customers who move to usage-based pricing voluntarily and see more + transparent billing. This success funds the broader rollout." + benchmark_references: [ "arpu", "nrr", "expansion-revenue-pct" ] + + - skill: "systems-thinking" + category: "frameworks" + saas_relevance: "high" + saas_context: "SaaS businesses are complex adaptive systems with feedback loops + that create non-obvious outcomes. The most important feedback loops: (1) + The growth loop: more customers fund more investment in product, which + attracts more customers. (2) The churn spiral: losing customers reduces + revenue, forcing cuts to customer success, which increases churn further. + (3) The data flywheel: more usage generates more data, which improves the + product (especially for AI/ML products), which attracts more users. (4) + The support debt loop: under-investing in self-serve support increases + ticket volume, which consumes engineering time for urgent fixes, which + delays product improvements, which generates more tickets. Systems + thinking helps SaaS operators identify and intervene in these loops." + saas_anti_patterns: + - "Treating symptoms instead of systems. Throwing more sales reps at a + growth stall when the root cause is a churn spiral. Hiring more support + agents when the root cause is poor documentation." + - "Ignoring time delays in feedback loops. Cutting customer success today + does not increase churn tomorrow — it increases churn in 3-6 months, + making the cause-and-effect connection invisible." + - "Optimizing one metric without modeling second-order effects. Reducing + CAC by cutting content marketing may increase CAC next quarter when the + organic pipeline dries up." + saas_example: "A SaaS company notices that NRR is declining despite stable logo + churn. Systems analysis reveals a reinforcing loop: as the product adds + complexity to serve enterprise customers, SMB users (who generate + expansion revenue through seat growth) find the product harder to use, + leading to contraction. The enterprise-focused investment that improves + per-account revenue is simultaneously degrading the expansion engine in + the SMB segment. The solution is product architecture — a simplified SMB + experience that diverges from the enterprise UI." + benchmark_references: [ "nrr", "logo-churn", "activation-rate", "gross-margin" ] + + - skill: "smart-goals" + category: "frameworks" + saas_relevance: "high" + saas_context: "SMART goals in SaaS benefit from the availability of precise, + real-time metrics. Unlike traditional businesses where measurement is + often lagging and approximate, SaaS companies can set goals that are + Specific to a metric (e.g., NRR, not 'retention'), Measurable in real-time + from the billing system, Achievable based on cohort analysis and + historical data, Relevant to the current company stage, and Time-bound to + monthly or quarterly cadences. The most common failure is setting goals + that are too numerous or not tied to the two or three metrics that + actually matter at the company's current stage." + saas_anti_patterns: + - "Setting revenue goals without corresponding operational goals. 'Hit $5M + ARR' is incomplete without 'achieve 110% NRR, reduce CAC payback to 12 + months, and maintain 75% gross margin.'" + - "Using annual goals in an early-stage SaaS company where conditions + change quarterly. Set 90-day goals with monthly check-ins." + - "Setting identical goals across functions. Engineering goals should be + about product quality and velocity; Sales goals should be about pipeline + and conversion; Customer Success goals should be about retention and + expansion." + saas_example: "Instead of 'grow revenue,' a SaaS company sets Q2 goals: (1) + Increase MRR from $150K to $200K by adding 30 new customers at $1,200 + average MRR and expanding 15 existing customers by $500 average. (2) + Reduce logo churn from 4% to 3% monthly by implementing a churn + early-warning system and proactive outreach for at-risk accounts. (3) + Decrease time to value from 14 days to 7 days by launching guided + onboarding and in-app tutorials. Each goal is specific, measurable, + connected to a responsible team, and achievable within the quarter." + benchmark_references: [ "mrr", "logo-churn", "time-to-value" ] + + - skill: "vuca-framework" + category: "frameworks" + saas_relevance: "moderate" + saas_context: "SaaS operates in a permanently VUCA environment. Volatility: + revenue can swing dramatically with a single enterprise churn or win. + Uncertainty: market dynamics shift as platforms (AI, cloud) evolve + unpredictably. Complexity: the interplay of product, GTM, retention, and + financing creates multi-variable decision spaces. Ambiguity: SaaS metrics + can be interpreted in contradictory ways (high NRR masking logo churn, + revenue growth hiding margin erosion). The VUCA framework helps SaaS + leaders identify which type of challenge they face and respond + appropriately — Vision for Volatility, Understanding for Uncertainty, + Clarity for Complexity, Agility for Ambiguity." + saas_anti_patterns: + - "Treating all challenges as one type. A pricing decision (Complexity — + multiple variables to weigh) requires a different approach than a + competitive response (Volatility — rapid reaction needed)." + - "Using Agility as an excuse for lack of strategy. SaaS companies that + pivot constantly without strategic rationale mistake activity for + progress." + saas_example: "When a major SaaS platform announces a native feature that + competes with your product, the VUCA framework clarifies the response. + This is Volatility (sudden market shift) and Ambiguity (unclear how + customers will react). The response combines Vision (articulating why your + dedicated product remains superior to a bundled feature) with Agility + (rapidly building the integration that makes your product complementary + rather than competitive to the platform)." + benchmark_references: [ "win-rate", "logo-churn" ] + + - skill: "trust-equation" + category: "frameworks" + saas_relevance: "high" + saas_context: "Trust is the fundamental currency in SaaS because customers grant + continuous access to sensitive data and business processes. The Trust + Equation (Credibility + Reliability + Intimacy / Self-Orientation) maps to + SaaS as follows: Credibility = uptime track record, security + certifications, public case studies. Reliability = consistent product + performance, predictable release cadence, SLA adherence. Intimacy = + understanding the customer's specific workflow and business context + through customer success. Self-Orientation = transparency about product + limitations, honest roadmap communication, fair pricing practices. High + self-orientation (aggressive upselling, opaque pricing, lock-in tactics) + destroys trust even when the other three components are strong." + saas_anti_patterns: + - "Investing in Credibility (certifications, logos, testimonials) while + neglecting Reliability (uptime, bug fixes, performance). Customers + notice when the marketing says 'enterprise-ready' but the product + crashes weekly." + - "Using dark patterns to reduce churn (hiding cancellation buttons, + requiring phone calls to cancel). This increases Self-Orientation and + destroys trust, ultimately accelerating negative word-of-mouth." + - "Treating customer success as a retention tax rather than an Intimacy + investment. CSMs who genuinely understand and advocate for customer + outcomes build the trust that justifies premium pricing and long-term + contracts." + saas_example: "Buffer built one of the strongest brands in SaaS through radical + transparency — publishing their revenue dashboard, salary formula, and + even their fundraising documents publicly. This drove Self-Orientation to + near zero (nothing to hide), Credibility through demonstrated metrics, and + Intimacy through open communication. The trust equation explains why + Buffer retained customers even when competitors offered more features at + lower prices." + benchmark_references: [ "nps-saas", "logo-churn", "nrr" ] + + - skill: "cialdini-influence" + category: "frameworks" + saas_relevance: "high" + saas_context: "Cialdini's six principles of influence map directly to SaaS + conversion and retention mechanics. Reciprocity: freemium and free trials + create obligation. Social Proof: customer logos, case studies, G2 reviews, + and 'X companies use this' badges. Commitment & Consistency: free trial + users who complete onboarding steps are far more likely to convert. + Authority: SOC 2 compliance, industry analyst recognition, thought + leadership content. Liking: brand personality, community, and customer + success relationships. Scarcity: limited-time pricing, exclusive features + for early adopters. Understanding these principles helps SaaS companies + design more effective onboarding flows, pricing pages, and retention + campaigns." + saas_anti_patterns: + - "Over-relying on Scarcity (fake urgency, countdown timers, 'only 3 seats + left' for a software product with infinite supply). SaaS buyers are + sophisticated enough to recognize manufactured scarcity." + - "Neglecting Social Proof for early-stage products. Even 5 good case + studies are more persuasive than feature lists. Invest in customer + stories before investing in marketing copy." + - "Using Authority signals (enterprise logos, compliance badges) that are + irrelevant to the target buyer. An SMB buyer does not care about Fortune + 500 logos — they care about companies like theirs." + saas_example: "Notion's growth leveraged multiple Cialdini principles + simultaneously: Reciprocity (generous free plan), Social Proof (template + gallery showcasing real user setups, public customer stories), Commitment + (progressive onboarding that builds invested workspace), Liking + (design-forward brand that users identify with), and Authority (adoption + by respected teams at companies like Figma, Loom, and Pixar). The + combination created viral organic growth that reduced CAC to near zero for + the individual and small-team segments." + benchmark_references: [ "activation-rate", "cac", "nps-saas" ] + + - skill: "emotional-intelligence" + category: "frameworks" + saas_relevance: "moderate" + saas_context: "Emotional intelligence in SaaS is a competitive advantage in + three domains: customer relationships (reading buyer sentiment during + sales cycles, detecting at-risk customers before they churn), team + leadership (managing high-intensity engineering and sales teams through + hypergrowth, handling layoffs and restructuring), and investor relations + (managing board dynamics, delivering bad news effectively, building + relationships that survive downturns). SaaS companies operate at high + intensity with frequent change — emotional intelligence is the lubricant + that prevents organizational friction from becoming organizational + failure." + saas_anti_patterns: + - "Treating emotional intelligence as 'soft' while privileging metrics + above all else. A SaaS CEO who can read a P&L but cannot read a room + will lose top talent and damage key customer relationships." + - "Confusing empathy with permissiveness. Emotional intelligence does not + mean avoiding hard conversations — it means having them with awareness + of their emotional impact." + saas_example: "A SaaS VP of Customer Success notices that a strategic account's + champion has become less responsive and stopped attending QBRs. Rather + than sending another automated check-in email, she reaches out personally + and discovers the champion is frustrated by a product limitation that was + deprioritized on the roadmap. The emotionally intelligent response is not + to promise a feature that cannot be delivered but to acknowledge the + frustration, share the honest trade-off reasoning, and collaborate on a + workaround — preserving the relationship and the account." + benchmark_references: [ "nrr", "nps-saas" ] + + - skill: "covey-seven-habits" + category: "frameworks" + saas_relevance: "moderate" + saas_context: "The Seven Habits apply to SaaS founders and operators who must + balance the intense short-term demands of a subscription business with + long-term strategic thinking. 'Begin with the End in Mind' means defining + the endgame — IPO, acquisition, profitable growth — and aligning every + operational decision with it. 'Put First Things First' maps to the Not + Urgent/Important quadrant where strategic SaaS work (product vision, + platform architecture, culture building) lives. 'Think Win-Win' is + essential for partner ecosystem development, which is a key SaaS growth + lever. 'Sharpen the Saw' addresses the burnout epidemic in SaaS + leadership." + saas_anti_patterns: + - "Sacrificing Habit 7 (Sharpen the Saw / personal renewal) for growth + targets. SaaS founding teams that burn out sacrifice the judgment and + creativity that drove early success." + - "Applying 'Win-Win' naively in competitive deals. Win-Win applies to + partnerships and customer relationships, not necessarily to competitive + displacement scenarios." + saas_example: "A SaaS founder applies 'Begin with the End in Mind' to realize + that their current growth trajectory leads to a $20M ARR company that is + neither attractive for acquisition (too small) nor viable for IPO (too + small). This analysis forces a strategic choice: accelerate to $50M+ ARR + (requiring a larger raise and more aggressive growth), or optimize for + profitability and build a durable, cash-generating business. Both are + valid endpoints — but the current path reaches neither." + benchmark_references: [ "arr", "rule-of-40", "burn-multiple" ] + + # ───────────────────────────────────────────── + # NEGOTIATION (4 skills) + # ───────────────────────────────────────────── + + - skill: "competitive-negotiation" + category: "negotiation" + saas_relevance: "high" + saas_context: "Competitive negotiation in SaaS occurs across three primary + contexts: enterprise sales (negotiating contract terms, pricing, and SLAs + with procurement teams), fundraising (negotiating term sheets with + investors), and vendor relationships (negotiating with cloud providers, + API vendors, and service partners). In enterprise SaaS sales, the + negotiation dynamics are shaped by annual budgets, multi-stakeholder + approval processes, and the buyer's leverage from low switching costs. In + fundraising, the negotiation centers on valuation, board composition, + protective provisions, and liquidation preferences." + saas_anti_patterns: + - "Discounting too quickly in enterprise sales negotiations. Every + discount trains the buyer to negotiate harder next time and erodes ARPU + across the customer base. Offer scope concessions (fewer seats, limited + features) rather than price concessions." + - "Negotiating valuation in isolation during fundraising. The valuation is + one term among many — pro-rata rights, board seats, protective + provisions, and liquidation preferences can be more impactful than a + higher valuation with worse terms." + - "Treating SaaS contract negotiation as zero-sum. The best enterprise + deals create long-term partnerships where the customer's success drives + expansion revenue." + saas_example: "A SaaS company negotiating a $200K ACV enterprise deal faces + pressure to discount by 30%. Instead of cutting price, the sales team + offers a two-year commitment at 15% discount (locking in revenue), + includes a success milestone clause (if the customer achieves defined ROI + metrics, the contract auto-renews at full price), and adds a 90-day pilot + period at full price with exit rights. This preserves ARPU while + addressing the buyer's risk concern." + benchmark_references: [ "acv", "arpu", "win-rate", "sales-cycle-length" ] + + - skill: "cooperative-negotiation" + category: "negotiation" + saas_relevance: "high" + saas_context: "Cooperative negotiation is the foundation of SaaS partnership + development — a critical growth lever. SaaS partnerships include: + technology integrations (building with complementary products), channel + partnerships (reselling through consultants or agencies), platform + partnerships (building on top of ecosystems like Salesforce, Shopify, or + Slack), and strategic alliances (co-selling with larger vendors). + Cooperative negotiation is also essential for customer success — the + ongoing relationship between vendor and customer in SaaS is a continuous + negotiation about priorities, roadmap influence, and terms." + saas_anti_patterns: + - "Entering partnership negotiations without clear metrics for success. + Define what each partner gains (revenue share, distribution, data, + brand) before negotiating terms." + - "Giving away too much in platform partnerships for the sake of + 'ecosystem access.' A SaaS company that builds its entire distribution + on a partner's marketplace is one policy change away from destruction." + - "Neglecting the cooperative dimension of customer renewals. Renewal + negotiation should be a collaborative discussion about value delivered + and value planned, not a transactional price conversation." + saas_example: "A SaaS company negotiates an integration partnership with a + 10x-larger company. Rather than accepting a standard API agreement, they + use cooperative negotiation to propose a deeper arrangement: co-marketing + (joint case studies and webinars), co-selling (mutual referral program + with revenue share), and data sharing (anonymized usage patterns that + benefit both products). The cooperative approach creates mutual dependency + that protects the smaller company from being cut off or replicated." + benchmark_references: [ "cac", "nrr", "arr" ] + + - skill: "delivering-the-deal" + category: "negotiation" + saas_relevance: "high" + saas_context: "Deal execution in SaaS has unique characteristics: procurement + cycles are increasingly governed by IT security reviews and legal + red-lining that can stall deals for months; annual budget cycles create + quarterly and year-end urgency; and multi-year commitments involve complex + terms (price escalators, renewal terms, termination clauses, data deletion + obligations). The skill of delivering the deal in SaaS means managing + these complexities while maintaining momentum. This includes preparing for + security questionnaires before they arrive, having flexible contract + templates ready, and building internal champions who drive urgency within + the buyer organization." + saas_anti_patterns: + - "Allowing legal and security review to happen sequentially. Run security + review, legal review, and commercial negotiation in parallel. Sequential + reviews double the sales cycle." + - "Relying on end-of-quarter urgency to close deals. Buyers increasingly + recognize and resist quarter-end pressure tactics. Build urgency through + value demonstration, not calendar manipulation." + - "Celebrating the closed deal before implementation begins. In SaaS, the + deal is not truly 'delivered' until the customer is activated and + deriving value. Handoff to customer success is part of the deal." + saas_example: "A SaaS sales team creates a 'deal acceleration kit': + pre-completed security questionnaires (SOC 2 Type II, GDPR DPA, + penetration test results), a flexible order form with pre-approved + discount tiers and term options, and a mutual success plan template that + aligns both teams on implementation milestones. This kit reduces average + enterprise sales cycle from 90 to 55 days by eliminating the two most + common stall points: security review and contract negotiation." + benchmark_references: [ "sales-cycle-length", "win-rate", "acv" ] + + - skill: "negotiation-mindset-and-self" + category: "negotiation" + saas_relevance: "moderate" + saas_context: "SaaS founders negotiate constantly — with investors, customers, + employees, and partners — often from a position of perceived weakness + (smaller company, less capital, fewer customers). The negotiation mindset + skill helps founders recognize and manage the psychological dynamics of + these asymmetric negotiations. In fundraising, founders must balance + desperation (running out of runway) with confidence (demonstrating + conviction in the business). In enterprise sales, founders must negotiate + with procurement teams whose explicit goal is to reduce price. In hiring, + founders must negotiate compensation packages with candidates who have + offers from larger, better-funded companies." + saas_anti_patterns: + - "Anchoring on valuation before building leverage. In fundraising, the + strongest negotiating position comes from having multiple term sheets, + strong metrics, and a credible alternative (profitability). Negotiate + from strength, not from need." + - "Internalizing the power asymmetry in enterprise sales. The buyer needs + the product (or they would not be in the evaluation). The vendor's + perceived weakness is often exaggerated." + saas_example: "A SaaS founder entering Series A negotiations with a tier-one VC + recognizes the psychological pattern: the VC asks probing questions that + feel like criticism, triggering defensiveness. By preparing for this + dynamic through negotiation mindset work, the founder reframes critical + questions as engagement signals (the VC is doing diligence because they + are interested) and responds with confidence and data rather than + defensiveness. The result: better terms because the founder demonstrated + conviction." + benchmark_references: [ "arr", "cac" ] + + # ───────────────────────────────────────────── + # THINKING (4 skills) + # ───────────────────────────────────────────── + + - skill: "enemies-of-clear-thinking" + category: "thinking" + saas_relevance: "critical" + saas_context: "SaaS operators face specific cognitive traps amplified by the + data-rich, fast-moving nature of the business. Survivorship bias: + benchmarking against successful SaaS companies while ignoring the majority + that failed. Sunk cost fallacy: continuing to invest in a feature or + market segment because of past investment rather than future potential. + Confirmation bias: interpreting ambiguous metrics as positive signals + (e.g., 'churn is seasonal' when it is structural). Anchoring: fixating on + the initial pricing or valuation and resisting evidence that it should + change. Availability bias: over-weighting the most recent customer + conversation or competitive threat." + saas_anti_patterns: + - "Using vanity metrics (total sign-ups, page views, feature usage counts) + that confirm the narrative while ignoring the metrics that challenge it + (activation rate, revenue churn, NPS trend)." + - "Anchoring on the fundraising valuation as an indicator of company + worth. The last-round valuation is a negotiated price for preferred + equity, not a measure of business value." + - "Confusing correlation with causation in product analytics. The fact + that users who complete onboarding retain better does not mean forcing + all users through onboarding will improve retention — the correlation + may reflect user intent, not the onboarding itself." + saas_example: "A SaaS CEO reviews monthly metrics and concludes the business is + healthy: MRR is growing 10% MoM, NRR is 115%, and NPS is 45. An advisor + trained in clear thinking spots the hidden problem: 80% of new MRR comes + from a single channel (a content piece that went viral), NRR is inflated + by one enterprise customer's massive expansion, and NPS was surveyed only + among power users. The 'healthy' picture is a collection of + non-representative data points — clear thinking demands disaggregation and + stress-testing." + benchmark_references: [ "mrr", "nrr", "nps-saas", "logo-churn" ] + + - skill: "evaluating-and-deciding" + category: "thinking" + saas_relevance: "high" + saas_context: "SaaS operators make high-frequency, high-impact decisions: which + features to build, how to price, when to raise, whom to hire, and which + market segments to pursue. The evaluation framework must account for + SaaS-specific decision characteristics: most decisions are reversible + (pricing can be changed, features can be deprecated), speed of decision + usually matters more than perfection, and the cost of + information-gathering often exceeds the cost of a wrong decision that can + be corrected quickly. The distinction between one-way doors (irreversible: + selling the company, choosing an architecture, raising a priced round) and + two-way doors (reversible: pricing changes, market positioning, feature + launches) should guide the decision framework." + saas_anti_patterns: + - "Applying one-way-door deliberation to two-way-door decisions. Spending + three months analyzing a pricing change that can be tested and reversed + in one week." + - "Deciding by committee. SaaS companies that require consensus for every + product decision ship slowly and build mediocre products. Assign clear + decision owners." + - "Over-relying on data for decisions that require judgment. Many critical + SaaS decisions (product vision, market positioning, culture) involve + insufficient data for purely analytical decision-making." + saas_example: "A SaaS product team debates whether to build a new analytics + module or improve the onboarding flow. Traditional evaluation stalls + because both have strong arguments. Applying the two-way door test: the + analytics module requires 3 months of engineering and is difficult to + reverse once shipped (one-way door). Improving onboarding can be tested in + 2 weeks with an A/B test and reversed instantly (two-way door). Decision: + test the onboarding improvement immediately, schedule the analytics module + for the next planning cycle with better data from the onboarding test." + benchmark_references: [ "activation-rate", "time-to-value" ] + + - skill: "defining-and-exploring-problems" + category: "thinking" + saas_relevance: "high" + saas_context: "SaaS companies frequently solve the wrong problem because they + conflate symptoms with root causes. A growth stall is a symptom; the + problem might be churn, market saturation, competitive displacement, or + GTM inefficiency. A support ticket volume spike is a symptom; the problem + might be a product bug, a UX confusion, or a customer segment mismatch. + The skill of defining problems precisely is particularly valuable in SaaS + because the rich data environment creates an illusion of understanding — + the team can describe what is happening in great detail without + understanding why." + saas_anti_patterns: + - "Defining the problem in terms of the preferred solution. 'We need to + add feature X' is a solution statement, not a problem definition. + 'Customers are churning because they cannot achieve Y outcome' is a + problem definition." + - "Accepting the first framing. When the VP Sales says 'we have a pipeline + problem,' the root cause might be a product problem (low win rate) or a + marketing problem (low lead quality), not a sales capacity problem." + - "Using dashboards as a substitute for problem exploration. Dashboards + show metrics; they do not explain causation. Understanding why NRR + declined requires qualitative investigation, not more charts." + saas_example: "A SaaS company defines its problem as 'we need to reduce churn.' + Rigorous problem exploration reveals three distinct problems: (1) SMB + customers churn because they outgrow the product within 18 months — a + product capability problem. (2) Mid-market customers churn during the + transition from the sales team to customer success — a handoff process + problem. (3) Enterprise customers churn when their internal champion + leaves — a multi-threading relationship problem. Each requires a different + solution. Lumping them together as 'churn' leads to generic interventions + that solve none of them." + benchmark_references: [ "logo-churn", "nrr", "grr" ] + + - skill: "building-thinking-strength" + category: "thinking" + saas_relevance: "moderate" + saas_context: "SaaS leadership demands sustained intellectual rigor across + diverse domains — product strategy, financial modeling, organizational + design, competitive analysis, and customer psychology. Building thinking + strength in the SaaS context means developing the ability to shift + fluently between these domains, hold multiple conflicting hypotheses + simultaneously, and update beliefs quickly as new data arrives. The pace + of SaaS means that thinking capacity is a rate-limiter on organizational + performance — the company can only execute as fast as its leaders can + think clearly." + saas_anti_patterns: + - "Equating busyness with thinking. A SaaS executive in back-to-back + meetings all day has no time to think. Protecting blocks of + uninterrupted thinking time is not a luxury — it is a core leadership + practice." + - "Over-specializing thinking. A SaaS CEO who thinks only about product + neglects GTM; one who thinks only about sales neglects product. The role + requires integrative thinking across all domains." + saas_example: "A SaaS founder implements a 'thinking ritual': every Monday + morning, 90 minutes with no meetings, no Slack, and no email. During this + time, they review the prior week's metrics, read one competitor's recent + release notes, and write a one-page memo on the single most important + strategic question facing the company this week. This practice compounds — + after six months, the founder has a 26-memo archive that documents the + evolution of their strategic thinking and provides a decision audit + trail." + benchmark_references: [] + + # ───────────────────────────────────────────── + # DECISIONS (3 skills) + # ───────────────────────────────────────────── + + - skill: "generating-solutions" + category: "decisions" + saas_relevance: "high" + saas_context: "Solution generation in SaaS benefits from the rapid testability + of software hypotheses. Unlike physical product businesses, SaaS companies + can prototype, test, and validate solutions in days or weeks. This changes + the solution generation process: generate more options, evaluate them + through quick tests rather than extended analysis, and iterate rapidly. + The danger is that solution generation in SaaS becomes narrowly focused on + product features. Many SaaS problems (churn, growth stalls, competitive + pressure) have non-product solutions: pricing changes, market + repositioning, partnership development, or organizational restructuring." + saas_anti_patterns: + - "Defaulting to 'build a feature' as the solution to every problem. Many + SaaS problems are better solved through pricing, positioning, customer + success, or go-to-market changes." + - "Generating solutions in isolation within functional silos. The best + SaaS solutions often emerge at the intersection of product, sales, and + customer success perspectives." + - "Eliminating solutions too early based on 'feasibility.' In SaaS, + today's infeasible solution may become feasible with an API integration, + an AI model, or a partner — the constraint landscape changes rapidly." + saas_example: "A SaaS company faces declining win rates against a well-funded + competitor. The product team's solution: build the five features the + competitor has that they lack (6-month project). A broader solution + generation exercise produces alternatives: (1) reposition as the + specialist for a specific vertical the competitor ignores, (2) launch a + free tier to win at the top of the funnel, (3) build an integration with + the competitor so customers can use both, (4) acquire a smaller company + that already has the missing features. Options 1 and 2 can be tested in + weeks; option 3 in months; only option 4 and the original 'build features' + plan require 6+ months." + benchmark_references: [ "win-rate", "cac", "time-to-value" ] + + - skill: "choosing-and-executing" + category: "decisions" + saas_relevance: "high" + saas_context: "Execution speed is a primary competitive advantage in SaaS. The + choosing-and-executing framework must emphasize speed-to-learning over + correctness-of-choice for reversible decisions. In SaaS, the cost of + choosing wrong and iterating is usually lower than the cost of choosing + slowly and executing late. Execution in SaaS also requires explicit + coordination across product, engineering, sales, marketing, and customer + success — siloed execution produces internal inconsistency (marketing + promises features that product has not built, sales sells contracts that + operations cannot support)." + saas_anti_patterns: + - "Seeking consensus before executing reversible decisions. SaaS companies + that require agreement from all stakeholders move too slowly. Use the + 'disagree and commit' principle." + - "Executing without defining success metrics. Before launching a feature, + pricing change, or marketing campaign, define what success looks like + and when you will evaluate." + - "Confusing execution with shipping. In SaaS, execution includes launch, + measurement, iteration, and communication — not just writing code and + deploying." + saas_example: "A SaaS company must decide between two pricing strategies: (A) + per-seat pricing to maximize revenue from large teams, or (B) usage-based + pricing to lower barriers and maximize adoption. Instead of debating for + months, they define a 60-day test: existing customers above 50 seats get + offered the per-seat model; new sign-ups under 20 seats get offered + usage-based. Success metrics: conversion rate, ARPU, and expansion rate + for each cohort. After 60 days, the data clearly favors usage-based for + new customers and per-seat for existing enterprise — they implement a + hybrid model." + benchmark_references: [ "arpu", "activation-rate", "expansion-revenue-pct" ] + + - skill: "tough-decision-situations" + category: "decisions" + saas_relevance: "high" + saas_context: "SaaS founders face uniquely difficult decisions: whether to raise + money or bootstrap, when to pivot the product or persist, whether to fire + a co-founder, when to accept an acquisition offer, how to manage layoffs + during a downturn, and whether to sunset a product line that loyal + customers depend on. These decisions are tough because they are + irreversible (or nearly so), involve deep uncertainty, carry emotional + weight, and have consequences for many stakeholders. The SaaS context adds + specific pressures: venture capital timelines create artificial urgency, + public metrics create accountability, and the continuous nature of + subscriptions means customers feel the impact immediately." + saas_anti_patterns: + - "Delaying tough decisions until they become crises. In SaaS, the + compounding nature of recurring revenue means that every month of delay + in addressing a broken GTM motion, an underperforming leader, or a + failing product line compounds the damage." + - "Making tough decisions in isolation. SaaS founders often carry the + burden alone — advisors, board members, and executive coaches exist + precisely for these moments." + - "Framing tough decisions as binary. 'Raise or die' is rarely the actual + choice set. Most tough decisions have creative alternatives that emerge + only when the full option space is explored." + saas_example: "A SaaS founder receives an acquisition offer at 8x ARR — a strong + multiple. The company is growing 2x YoY with 18 months of runway. The + tough decision framework surfaces the key tensions: the offer is + above-market for the company's size, but the growth rate suggests + significantly more value creation if they continue. The framework also + surfaces the emotional dimension: the founder is tired, the team is burnt + out, and the acquirer would provide stability. Rather than deciding + immediately, the founder maps all stakeholders' interests, defines the + minimum acceptable outcome for each, and discovers a third option: a + growth round that partially liquidates the founder's equity while keeping + the company independent." + benchmark_references: [ "arr", "burn-multiple", "rule-of-40" ] + + # ───────────────────────────────────────────── + # GAME THEORY (3 skills) + # ───────────────────────────────────────────── + + - skill: "game-theory-fundamentals" + category: "game-theory" + saas_relevance: "high" + saas_context: "SaaS markets are repeated games with observable moves — every + product launch, pricing change, and funding announcement is visible to + competitors. This makes game theory directly applicable. Key SaaS game + theory situations include: pricing wars (dropping prices to compete, with + the risk of a race to the bottom), feature parity battles (copying + competitor features in an endless escalation), and platform ecosystem + dynamics (cooperating with a platform that might become a competitor). + Understanding Nash equilibria helps SaaS operators predict stable + competitive outcomes and avoid destructive strategies." + saas_anti_patterns: + - "Engaging in price wars with better-funded competitors. The well-funded + player can sustain losses longer. Compete on differentiation, not on + price." + - "Ignoring the repeated-game nature of SaaS competition. Aggressive moves + (poaching employees, FUD campaigns, predatory pricing) invite + retaliation in a market where companies interact repeatedly." + - "Treating partner-competitor dynamics as static. A company that is a + partner today (e.g., a platform you build on) may become a competitor + tomorrow. Game theory helps model these transitions." + saas_example: "Two SaaS companies compete in the same category. Company A + considers dropping prices by 30% to gain market share. Game theory + analysis reveals this is a negative-sum game: Company B will match the + price cut (dominant strategy in a repeated game), both companies end up at + lower margins, and neither gains share. Instead, Company A invests the + margin they would have sacrificed into product differentiation (vertical + features, better integrations), creating asymmetric value that Company B + cannot match through price reduction alone." + benchmark_references: [ "win-rate", "arpu", "gross-margin" ] + + - skill: "first-mover-strategy" + category: "game-theory" + saas_relevance: "high" + saas_context: "First-mover advantage in SaaS is real but often overstated. True + first-mover advantages in SaaS come from: network effects (the product + becomes more valuable with more users, making it hard to displace), data + advantages (early users generate data that improves the product), + integration lock-in (becoming the standard that other tools integrate + with), and brand-category association (becoming the verb: 'Slack me,' + 'Zoom call'). Many SaaS categories, however, are won by fast followers who + learn from the first mover's mistakes: Slack followed HipChat, Zoom + followed WebEx, Figma followed Sketch." + saas_anti_patterns: + - "Assuming first-mover status guarantees victory. In SaaS, the product is + continuously improvable — a fast follower with better execution, more + capital, or superior UX can overtake the pioneer." + - "Over-investing in speed-to-market at the expense of product quality. + Launching a broken product first does not create an advantage — it + creates negative word-of-mouth that the fast follower exploits." + - "Ignoring the fast-follower threat. First movers must invest in + defensibility (data moats, network effects, integration ecosystems) or + the advantage dissipates as the category matures." + saas_example: "Figma was not the first browser-based design tool — it entered + years after Sketch had established dominance. Figma's fast-follower + advantage: they observed that Sketch's file-based workflow was the key + weakness and built collaboration as the core architecture from day one. + Sketch could not retrofit real-time collaboration into a file-based + product. The first mover's architecture became its constraint, and the + fast follower's architecture became its moat." + benchmark_references: [ "activation-rate", "nps-saas", "nrr" ] + + - skill: "prisoners-dilemma-and-cooperation" + category: "game-theory" + saas_relevance: "moderate" + saas_context: "The prisoner's dilemma appears frequently in SaaS in competitive + pricing, platform relationships, and data sharing. Two SaaS companies + competing for the same customer both have the incentive to discount + aggressively (defect), but if both discount, both lose margin (mutual + defection). The cooperative outcome (maintaining prices, competing on + value) is better for both but unstable without mechanisms to enforce it. + In platform relationships, the dilemma is more acute: a SaaS company + shares data with a platform partner (cooperate) to improve the + integration, but the platform could use that data to build a competing + feature (defect)." + saas_anti_patterns: + - "Cooperating indefinitely with a partner who repeatedly defects. If a + platform partner keeps building features that compete with your product, + continuing to invest in the integration is irrational." + - "Defecting preemptively out of fear. Refusing to integrate with + platforms, share data with partners, or collaborate on standards out of + fear of exploitation prevents the cooperative outcomes that drive SaaS + ecosystem value." + saas_example: "A SaaS company builds on top of a major platform's API. The + platform announces a native feature that partially overlaps with the SaaS + company's product. This is a prisoner's dilemma: the SaaS company can (a) + continue building on the platform and hope the native feature remains + inferior, or (b) diversify to other platforms, reducing investment in the + relationship. The optimal strategy from game theory: communicate directly + with the platform, identify the non-overlapping use cases where the + dedicated product is superior, and invest in depth of integration that + makes the SaaS product complementary rather than competitive to the native + feature." + benchmark_references: [ "nrr", "win-rate" ] + + # ───────────────────────────────────────────── + # LEADERSHIP (5 skills) + # ───────────────────────────────────────────── + + - skill: "delegation-and-empowerment" + category: "leadership" + saas_relevance: "high" + saas_context: "Delegation is the single biggest scaling bottleneck for SaaS + founders. The transition from founder-does-everything to functional + leadership is where most SaaS companies stall between $1M and $5M ARR. The + challenge is SaaS-specific: founders built the product, sold the first + customers, and configured the infrastructure — their deep context makes + them faster than any hire in the short term. Effective delegation in SaaS + requires building 'context transfer systems': documented processes, metric + dashboards, decision frameworks, and explicit delegation of authority over + specific functions with clear guardrails." + saas_anti_patterns: + - "Delegating responsibility without authority. Hiring a VP Sales but + requiring founder approval for every discount or contract term makes the + VP ineffective and signals distrust." + - "Delegating execution but retaining all strategic decisions. SaaS + functional leaders must own both strategy and execution in their domain + to be effective." + - "Re-doing delegated work. If the founder rewrites every marketing email + and redesigns every feature after delegation, the team stops investing + effort — learned helplessness sets in." + saas_example: "A SaaS CEO at $3M ARR hires a VP Engineering but continues + reviewing every pull request and attending every sprint planning meeting. + The VP cannot establish authority, senior engineers go around the VP to + the CEO for decisions, and the CEO is still working 80-hour weeks. The + fix: the CEO defines three explicit 'delegation contracts' — the VP owns + all technical architecture decisions, sprint planning, and engineering + hiring. The CEO retains input on product roadmap priorities but not + implementation decisions. Monthly 1:1s replace daily involvement." + benchmark_references: [ "arr" ] + + - skill: "decision-making-under-pressure" + category: "leadership" + saas_relevance: "high" + saas_context: "SaaS creates unique pressure situations: infrastructure outages + affecting thousands of customers simultaneously, competitor launches that + require rapid strategic response, fundraising timelines that force + decisions with incomplete information, and key employee departures that + leave critical functions uncovered. The subscription model amplifies + pressure because revenue is earned continuously — every day of + underperformance compounds. Decision-making under pressure in SaaS must + account for the amplification effect of public dashboards, real-time + metrics, and social media where customers can broadcast frustration + instantly." + saas_anti_patterns: + - "Making strategic decisions during tactical crises. When the product is + down, the correct decision is to fix it — not to have a strategic + discussion about architecture. Separate crisis response from strategic + response." + - "Using pressure as an excuse for poor process. 'We had to move fast' + does not justify skipping customer communication, security review, or + team alignment." + - "Allowing pressure to create a permanent state of urgency. SaaS + companies that operate in constant crisis mode burn out their teams and + make increasingly poor decisions." + saas_example: "A SaaS company's primary database goes down during a major + customer's compliance audit. The CEO faces simultaneous decisions: (1) + Technical: restore from backup vs. rebuild from replica (2) Customer: how + to communicate with the affected customer (3) Business: whether to offer a + credit or contract extension (4) Strategic: whether this incident reveals + a systemic reliability problem requiring major infrastructure investment. + Under pressure, the CEO sequences these correctly: technical fix first, + customer communication within 30 minutes, business discussion after + stability, and strategic discussion in the following week's executive + meeting." + benchmark_references: [ "nps-saas", "logo-churn" ] + + - skill: "employee-engagement-retention" + category: "leadership" + saas_relevance: "high" + saas_context: "SaaS companies compete for talent in one of the most competitive + labor markets. Engineering, product management, and sales talent have + abundant options, and the cost of attrition in SaaS is exceptionally high + — a departing senior engineer takes 3-6 months of institutional knowledge + and productivity, and a departing sales rep takes pipeline relationships + and customer context. Engagement in SaaS is driven by: product quality + (engineers want to work on well-architected systems), growth trajectory + (employees want equity upside), learning opportunities (the talent market + values skill development), autonomy (top SaaS talent resists + micromanagement), and mission alignment (why this product matters)." + saas_anti_patterns: + - "Using equity as a substitute for culture. Stock options attract talent + but do not retain it if the daily work environment is toxic, the product + vision is unclear, or management is incompetent." + - "Measuring engagement through annual surveys instead of continuous + signals. In SaaS, Slack activity, PR velocity, meeting attendance + patterns, and 1:1 sentiment are real-time engagement indicators." + - "Treating all attrition as bad. Some attrition in SaaS is healthy — + underperformers, culture mismatches, and employees who have outgrown + their roles. Regrettable attrition (top performers leaving voluntarily) + is the metric that matters." + saas_example: "A SaaS company's engineering team has 35% annual attrition. Exit + interviews reveal the primary driver is not compensation but technical + debt — engineers spend 60% of their time on maintenance rather than + building new features. The company implements a '70/30 rule': 70% of + engineering capacity on new features and improvements, 30% on tech debt + reduction, with progress visible in a public dashboard. Attrition drops to + 15% within two quarters because engineers see that leadership takes + product quality seriously." + benchmark_references: [ "gross-margin", "arr" ] + + - skill: "leading-through-change" + category: "leadership" + saas_relevance: "high" + saas_context: "SaaS companies undergo frequent, substantial change: pivots, + pricing restructures, organizational redesigns, go-to-market transitions, + and replatforming efforts. The pace is faster than traditional industries + because the subscription model provides rapid feedback. Leading through + change in SaaS requires specific capabilities: communicating 'why' when + the data-driven reason may be complex (e.g., 'we are restructuring pricing + because our expansion revenue model is broken'), managing the anxiety of + teams whose work may become obsolete, and maintaining customer trust + during transitions that affect their experience." + saas_anti_patterns: + - "Announcing major changes without preparation. A pricing restructure + announced on Monday and implemented on Friday creates chaos with + customers, sales, and support." + - "Changing too many things simultaneously. SaaS companies that + restructure the team, change the pricing, and pivot the product + simultaneously cannot determine what is working." + - "Under-communicating during change. SaaS teams that hear about strategic + changes through Slack rumors rather than direct leadership communication + lose trust rapidly." + saas_example: "A SaaS company transitions from a sales-led to a product-led + growth model. The change affects every function: product must build + self-serve onboarding, engineering must instrument usage tracking, + marketing must shift from lead-gen to product-qualified leads, and sales + must evolve from outbound prospecting to expansion selling. The CEO leads + through change by: (1) publishing a 6-page memo explaining the strategic + rationale with data, (2) running team-specific workshops on what changes + for each function, (3) defining a 90-day transition plan with weekly + metrics check-ins, and (4) explicitly addressing the fear: 'No one is + losing their job — roles are evolving, and we will invest in retraining.'" + benchmark_references: [ "activation-rate", "cac", "expansion-revenue-pct" ] + + - skill: "strategic-thinking-and-alignment" + category: "leadership" + saas_relevance: "critical" + saas_context: "Strategic alignment in SaaS means ensuring that product roadmap, + go-to-market motion, pricing model, customer success strategy, and + organizational structure all point in the same direction. Misalignment is + the most common cause of SaaS underperformance — the product serves SMB + but sales targets enterprise, the pricing encourages monthly churn but the + model assumes annual contracts, or customer success is measured on + retention but has no influence over the product roadmap. Strategic + thinking in SaaS requires holding the entire system in view and + identifying the misalignments that create friction." + saas_anti_patterns: + - "Defining strategy as 'grow revenue.' That is a goal, not a strategy. + SaaS strategy must articulate where to compete (segments, geographies, + use cases), how to win (differentiation, pricing, distribution), and + what to deprioritize." + - "Aligning at the annual offsite and then drifting for 11 months. SaaS + strategy requires monthly recalibration because feedback loops are fast + and market conditions change rapidly." + - "Delegating strategic alignment to a strategy document. Alignment is + maintained through persistent communication, metric alignment across + teams, and regular cross-functional reviews — not through documents that + no one reads." + saas_example: "A SaaS company's NRR is declining despite a strong NPS score. + Strategic analysis reveals misalignment: the product team is building + features for enterprise prospects (strategic initiative: 'move upmarket'), + but the customer success team is compensated on logo retention (which is + heavily SMB). Enterprise prospects see a product roadmap they like, but + SMB customers see their needs deprioritized, leading to contraction and + churn. The strategic fix: explicit segmentation with separate product + roadmaps for SMB and enterprise, and realigning customer success + compensation to include expansion revenue, not just retention." + benchmark_references: [ "nrr", "grr", "expansion-revenue-pct", "logo-churn" ] + + # ───────────────────────────────────────────── + # STORYTELLING (1 skill) + # ───────────────────────────────────────────── + + - skill: "story-structure-and-arc" + category: "storytelling" + saas_relevance: "high" + saas_context: "Storytelling is a critical skill for SaaS founders in three + contexts: fundraising (the pitch narrative), sales (customer case studies + and product narratives), and team alignment (the company origin story and + vision narrative). The classic story arc — status quo, disruption, + struggle, transformation, new normal — maps directly to the SaaS pitch + structure: the market has a problem (status quo), existing solutions fail + (disruption), our early customers struggled with this (struggle), our + product transformed their workflow (transformation), and here is what the + future looks like at scale (new normal). Investors fund narratives as much + as metrics — a founder who cannot tell a compelling story will not raise + effectively regardless of their numbers." + saas_anti_patterns: + - "Leading with product features instead of customer problems. The story + must start with the protagonist's pain, not the solution's + capabilities." + - "Telling a story that does not connect to the metrics. A compelling + narrative that contradicts the unit economics or retention data will be + dismantled by sophisticated investors." + - "Using the same story for every audience. The board wants a strategic + narrative, the sales prospect wants a peer's success story, and the + engineering team wants a technical vision narrative." + saas_example: "A SaaS founder structures their Series A pitch as a three-act + story. Act 1: 'Every compliance team in fintech manually tracks 400+ + regulatory changes per year. They use spreadsheets, email chains, and + prayer.' Act 2: 'Our first 50 customers went from 40 hours/week of manual + tracking to 2 hours/week. They caught 3 regulatory changes that would have + resulted in fines totaling $2.1M.' Act 3: 'We have 50 customers, $1.5M + ARR, 130% NRR, and a waiting list of 200 companies. With this round, we + will build the compliance operating system for all of fintech.' The + narrative arc makes the metrics memorable and the opportunity tangible." + benchmark_references: [ "arr", "nrr" ] + + # ───────────────────────────────────────────── + # WRITING (1 skill) + # ───────────────────────────────────────────── + + - skill: "writing-effective-emails" + category: "writing" + saas_relevance: "high" + saas_context: "Email remains the primary communication channel for SaaS + businesses across every function: investor updates, customer onboarding + sequences, sales outreach, support communication, internal announcements, + and partnership proposals. In SaaS, email effectiveness directly impacts + conversion rates (sales outreach), retention (customer communication), and + fundraising success (investor updates). The SaaS-specific dimension is + that email often serves as the first touch in a relationship (cold + outreach) and the ongoing thread of a long-term relationship (monthly + investor updates, quarterly business reviews) — it must work at both + extremes." + saas_anti_patterns: + - "Sending generic, template-obvious sales outreach. SaaS buyers receive + dozens of cold emails daily. Personalization based on the prospect's + specific context (tech stack, recent funding, job postings) is + mandatory." + - "Writing investor updates that hide bad news. The best investor updates + lead with what went wrong, what was learned, and how the company is + responding. Investors who discover problems late lose trust + permanently." + - "Over-engineering onboarding email sequences. SaaS companies that send + 15 emails in the first 14 days create fatigue. Focus on the 3-4 emails + that drive activation, not a comprehensive drip campaign." + saas_example: "A SaaS founder's monthly investor update follows a consistent + structure: three metrics (MRR, NRR, cash remaining), one win, one + challenge, one ask. The email takes 90 seconds to read. When the founder + needs a warm introduction, they send a brief, specific request ('Can you + introduce me to [Name] at [Company]? We have 3 customers in their space + and I believe we can help them with [specific problem].') rather than a + generic 'know anyone who might be interested?' The specificity of SaaS + metric language makes email communication more precise and more + actionable." + benchmark_references: [ "mrr", "nrr", "cac" ] + + # ───────────────────────────────────────────── + # AI LEADERSHIP (1 skill) + # ───────────────────────────────────────────── + + - skill: "ai-vision-and-strategy" + category: "ai-leadership" + saas_relevance: "critical" + saas_context: "AI is the most significant strategic variable in SaaS since the + cloud transition itself. Every SaaS company must develop an AI strategy + along three dimensions: (1) AI-native product features — how AI enhances + the core product (intelligent automation, predictive analytics, natural + language interfaces), (2) AI-enabled operations — how AI improves internal + efficiency (customer support bots, code generation, automated testing, + churn prediction), and (3) AI competitive positioning — whether AI creates + defensible advantage (proprietary models trained on customer data) or + commoditizes the existing product (general-purpose AI tools replacing + specialized SaaS). Failure to develop an AI strategy is now an existential + risk for SaaS companies." + saas_anti_patterns: + - "Adding 'AI-powered' as a marketing label without genuine AI capability. + SaaS buyers are becoming sophisticated enough to distinguish real AI + features from rule-based automation with an AI wrapper." + - "Building AI features that depend on third-party foundation models + without a defensibility plan. If the differentiation is a prompt on top + of GPT, the moat is zero." + - "Ignoring the AI threat from below. General-purpose AI tools (ChatGPT, + Claude, Copilot) can now perform tasks that previously required + specialized SaaS products. Every SaaS company must answer: 'What does + our product do that a general AI tool cannot?'" + saas_example: "A SaaS company providing contract analysis for legal teams faces + an AI strategy decision. Option A: integrate a foundation model to add + AI-powered clause detection (quick to ship, no moat, competitors will copy + in months). Option B: build a proprietary model trained on their + customers' 500,000 contract dataset, creating a data flywheel where more + usage improves accuracy. Option C: pivot from a software tool to an + AI-powered service that delivers contract analysis outcomes, not just a + software interface. The AI strategy framework helps evaluate these options + against defensibility, time to market, customer value, and competitive + dynamics." + benchmark_references: [ "nrr", "activation-rate", "nps-saas" ] diff --git a/plugins/foreman/content/industry-packs/saas/saas-templates.yaml b/plugins/foreman/content/industry-packs/saas/saas-templates.yaml new file mode 100644 index 0000000..0537086 --- /dev/null +++ b/plugins/foreman/content/industry-packs/saas/saas-templates.yaml @@ -0,0 +1,901 @@ +# SaaS Industry Pack — Output Template Adaptations +# +# For each of the 48 Foreman output templates, this file defines how fields +# and sections adapt for SaaS companies. The output agent loads these rules +# when generating documents with the SaaS industry pack active. +# +# Adaptation types: +# as-is — The template works without modification for SaaS companies. +# modified — The template requires field changes, additional sections, or +# reframing of existing sections for SaaS context. + +pack_metadata: + sector: "saas" + display_name: "SaaS" + version: "1.0.0" + author: "Fatih Guner" + last_updated: "2026-03-26" + +# ═══════════════════════════════════════════════════════════════ +# TEMPLATE ADAPTATIONS +# ═══════════════════════════════════════════════════════════════ + +template_adaptations: + + # ───────────────────────────────────────────── + # INVESTOR TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "unit-economics-snapshot" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "This template is almost entirely SaaS-specific. The base template covers generic unit economics; the SaaS overlay replaces it with a complete SaaS metrics dashboard." + field_changes: + - field: "Revenue per unit" + sector_label: "MRR / ARR" + sector_guidance: "Report both MRR (current month) and ARR (MRR x 12). Decompose MRR into five components: New, Expansion, Reactivation, Contraction, Churned." + - field: "Cost per unit" + sector_label: "CAC (Fully Loaded)" + sector_guidance: "Include all sales and marketing costs: salaries, commissions, tooling, content production, events, and allocated overhead. Report by channel and blended." + - field: "Margin per unit" + sector_label: "Gross Margin %" + sector_guidance: "SaaS COGS includes hosting, infrastructure, support, customer success (if included in COGS), and third-party API costs. Target: 70-85%." + - field: "Lifetime value" + sector_label: "LTV (Gross-Profit Adjusted)" + sector_guidance: "Calculate as ARPU x Gross Margin % / Monthly Revenue Churn Rate. Disclose churn rate assumption and average customer lifetime." + - field: "Acquisition cost" + sector_label: "CAC Payback Period" + sector_guidance: "Report in months: CAC / (ARPU x Gross Margin %). This is the gross-margin-adjusted payback, not the revenue payback." + - field: "Unit economics ratio" + sector_label: "LTV:CAC Ratio" + sector_guidance: "Report the ratio and compare to the 3x-5x benchmark. If below 3x, explain the improvement trajectory. If above 5x, address whether growth investment is sufficient." + sections_to_add: + - section_name: "SaaS Metrics Dashboard" + placement: "before:Revenue per unit" + description: "Core SaaS metrics in a standardized format that investors expect." + fields: + - "MRR (end of period)" + - "ARR (end of period)" + - "MoM Growth Rate (3-month average)" + - "Net Revenue Retention (NRR)" + - "Gross Revenue Retention (GRR)" + - "Logo Churn (monthly)" + - "Revenue Churn (monthly, gross)" + - "Customers (total active)" + - "ARPU (monthly)" + - "ACV (new contracts)" + - section_name: "Efficiency Metrics" + placement: "after:Unit economics ratio" + description: "Capital efficiency metrics that determine fundraising readiness and valuation." + fields: + - "Burn Multiple" + - "Rule of 40 Score" + - "Magic Number" + - "SaaS Quick Ratio" + - "Runway (months at current burn)" + - section_name: "Cohort Analysis" + placement: "end" + description: "Retention and expansion by customer acquisition cohort." + fields: + - "Monthly cohort retention curves (graph or table)" + - "Revenue retention by quarterly cohort" + - "Expansion revenue by cohort vintage" + sections_to_remove: [] + benchmark_references: ["mrr", "arr", "nrr", "grr", "cac", "ltv", "ltv-cac-ratio", "cac-payback-period", "gross-margin", "burn-multiple", "rule-of-40", "magic-number", "saas-quick-ratio"] + + - template: "investor-update-email" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS investor updates have a well-established format and metric set. Investors expect specific SaaS KPIs reported consistently each month. The template should enforce this standard." + field_changes: + - field: "Financial highlights" + sector_label: "SaaS KPIs" + sector_guidance: "Report: MRR, MoM Growth %, ARR, NRR (trailing 12-month), Burn Rate, Runway. Present as a small table with current month, prior month, and trend arrow." + - field: "Key metrics" + sector_label: "Operating Metrics" + sector_guidance: "Report: New customers, churned customers, expansion MRR, CAC (blended), pipeline coverage. Choose 3-5 metrics that are most relevant to the current company focus." + - field: "Wins" + sector_label: "Wins" + sector_guidance: "Include at least one quantified win: a named customer closed (with ACV if appropriate), a retention metric improvement, or a product milestone with measurable impact." + - field: "Challenges" + sector_label: "Challenges" + sector_guidance: "Lead with challenges, not wins. Investors respect transparency. Describe the problem, the root cause hypothesis, and the planned response." + - field: "Asks" + sector_label: "Asks" + sector_guidance: "Be specific. Not 'introductions to potential customers' but 'an introduction to [Name] at [Company] because [specific reason].' Give investors concrete ways to help." + sections_to_add: + - section_name: "Cash Position" + placement: "after:SaaS KPIs" + description: "Investors want to know runway at a glance." + fields: + - "Cash balance (end of month)" + - "Monthly burn rate (trailing 3-month average)" + - "Months of runway" + sections_to_remove: [] + benchmark_references: ["mrr", "arr", "nrr", "burn-multiple"] + + - template: "competitive-landscape-brief" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS competitive dynamics are uniquely transparent — competitors' features, pricing, and positioning are publicly visible. The competitive brief should leverage this transparency and address the specific threat categories relevant to SaaS." + field_changes: + - field: "Competitor overview" + sector_label: "Competitive Map" + sector_guidance: "Map competitors on a 2x2 matrix: X-axis = market segment (SMB to Enterprise), Y-axis = product scope (point solution to platform). Position your product and each competitor. Include funding levels and estimated ARR where known." + - field: "Competitive advantages" + sector_label: "Defensibility Analysis" + sector_guidance: "Assess defensibility along SaaS-specific dimensions: data moat (unique data assets), network effects (product improves with more users), integration ecosystem (switching costs from integrations), brand/community (organic distribution), and technical architecture (speed, reliability, unique capabilities)." + - field: "Competitive threats" + sector_label: "Threat Vectors" + sector_guidance: "Categorize threats: (1) Direct competitors — same category, same segment. (2) Platform expansion — incumbents adding your feature. (3) Adjacent category expansion — companies in neighboring categories moving into your space. (4) AI disruption — general-purpose AI tools performing your product's function." + sections_to_add: + - section_name: "Win/Loss Analysis" + placement: "after:Threat Vectors" + description: "Data-driven competitive intelligence from the sales pipeline." + fields: + - "Win rate against each named competitor (last quarter)" + - "Primary win reasons by competitor" + - "Primary loss reasons by competitor" + - "Deals lost to 'no decision' or 'built internally' (percentage)" + - section_name: "Feature Comparison Matrix" + placement: "after:Win/Loss Analysis" + description: "Objective capability comparison across competitors." + fields: + - "Feature matrix (rows: key capabilities; columns: competitors; cells: present/absent/superior)" + - "Pricing comparison (public pricing tiers and structure)" + - "Integration ecosystem comparison (number and quality of integrations)" + - section_name: "AI Threat Assessment" + placement: "end" + description: "Specific assessment of how AI tools affect the competitive landscape." + fields: + - "Which product capabilities can be replicated by general-purpose AI?" + - "Which capabilities are defensible against AI substitution?" + - "How is the company incorporating AI to strengthen its position?" + sections_to_remove: [] + benchmark_references: ["win-rate", "nrr", "nps-saas"] + + - template: "fundraising-deck-outline" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS pitch decks have a well-established structure that investors expect. The SaaS overlay ensures the deck includes the specific metric slides and narrative structure that SaaS investors require." + field_changes: + - field: "Market opportunity" + sector_label: "Market Opportunity" + sector_guidance: "Present TAM/SAM/SOM with bottom-up validation. For SaaS, investors prefer: (target companies) x (annual willingness to pay) = SAM. Include market growth rate and secular tailwinds." + - field: "Business model" + sector_label: "SaaS Business Model" + sector_guidance: "Cover: pricing model (per-seat/usage/tiered), GTM motion (PLG/sales-led/hybrid), customer segments, and the expansion revenue mechanism. Show how ACV and NRR drive compounding revenue." + - field: "Traction" + sector_label: "SaaS Traction Metrics" + sector_guidance: "Dedicated slide with: ARR/MRR trajectory chart, customer count, NRR, logo retention, ARPU trend, and growth rate. This slide is the most scrutinized in any SaaS pitch." + sections_to_add: + - section_name: "Unit Economics Slide" + placement: "after:SaaS Traction Metrics" + description: "Dedicated unit economics presentation that investors expect in every SaaS pitch." + fields: + - "LTV:CAC ratio" + - "CAC Payback Period" + - "Gross Margin %" + - "Burn Multiple" + - "Cohort retention curve" + - section_name: "Go-to-Market Slide" + placement: "after:Unit Economics Slide" + description: "The GTM motion is a critical evaluation criterion for SaaS investors." + fields: + - "GTM motion description (PLG, sales-led, hybrid)" + - "Sales funnel metrics (top to bottom conversion rates)" + - "CAC by channel" + - "Pipeline coverage and win rate" + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "ltv-cac-ratio", "cac-payback-period", "gross-margin", "burn-multiple"] + + - template: "strategic-analysis-one-pager" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "A SaaS strategic one-pager must anchor analysis in SaaS-specific frameworks and metrics rather than generic strategic analysis." + field_changes: + - field: "Strategic position" + sector_label: "SaaS Strategic Position" + sector_guidance: "Frame position in SaaS terms: market segment, competitive differentiation, GTM efficiency, and retention moat. Include where the company sits on the product-led to sales-led spectrum." + - field: "Key metrics" + sector_label: "SaaS Health Metrics" + sector_guidance: "Core 5: ARR + growth rate, NRR, LTV:CAC, Burn Multiple, Gross Margin. Compare each to stage-appropriate benchmarks." + sections_to_add: + - section_name: "SaaS Flywheel Assessment" + placement: "end" + description: "Assessment of the company's growth flywheel — the reinforcing loops that drive compounding growth." + fields: + - "Primary growth loop (acquisition > activation > retention > referral > acquisition)" + - "Flywheel health indicators (which loops are working, which are broken)" + - "Key constraint (the bottleneck in the flywheel)" + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "ltv-cac-ratio", "burn-multiple", "gross-margin"] + + - template: "market-opportunity-summary" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS market sizing uses specific methodologies (bottom-up company count x ACV, category spend analysis) and must address SaaS-specific dynamics like category creation, platform expansion, and AI disruption." + field_changes: + - field: "Total addressable market" + sector_label: "TAM / SAM / SOM" + sector_guidance: "Use bottom-up sizing: (number of target companies in segment) x (realistic annual contract value). Cross-reference with category spend data (Gartner, IDC). Do not use top-down GDP-fraction estimates." + - field: "Market dynamics" + sector_label: "SaaS Category Dynamics" + sector_guidance: "Address: category maturity (emerging, growth, mature), buyer behavior (self-serve adoption, procurement complexity), competitive density (number of funded competitors), and platform risk (probability of a major platform entering)." + sections_to_add: + - section_name: "Category Evolution" + placement: "end" + description: "How the SaaS category is expected to evolve, including AI impact." + fields: + - "Current category state (fragmented, consolidating, mature)" + - "AI impact thesis (how AI changes the category)" + - "Predicted winner-take-most or winner-take-some dynamics" + sections_to_remove: [] + benchmark_references: ["acv", "arr"] + + - template: "due-diligence-checklist" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS due diligence has specific areas of focus: metrics verification, churn cohort analysis, revenue quality assessment, and technical architecture review." + field_changes: + - field: "Financial review" + sector_label: "SaaS Metrics Verification" + sector_guidance: "Verify: ARR calculation methodology, MRR component decomposition, churn calculation (logo and revenue), NRR calculation, CAC calculation (fully loaded), and gross margin (COGS classification). Request access to billing system data." + - field: "Operational review" + sector_label: "GTM and Retention Review" + sector_guidance: "Review: sales pipeline hygiene, win/loss data, customer health scores, support ticket trends, NPS data, and churn reasons. Request cohort retention data for the last 12 months." + sections_to_add: + - section_name: "Technical Due Diligence" + placement: "end" + description: "SaaS-specific technical assessment." + fields: + - "Architecture review (scalability, security, uptime history)" + - "Technical debt assessment" + - "Key technical dependencies (infrastructure, APIs, third-party services)" + - "Security posture (SOC 2, penetration testing, data encryption)" + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "grr", "cac", "ltv", "gross-margin"] + + - template: "cap-table-summary" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Cap table structure is not SaaS-specific. Standard venture capital cap table formats apply regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "decision-rationale-memo" + audience: "investor" + sector_adaptation: "as-is" + adaptation_rationale: "Decision rationale documentation follows a standard format across sectors. SaaS context is naturally incorporated through the specific decision being documented." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "exit-scenario-analysis" + audience: "investor" + sector_adaptation: "modified" + adaptation_rationale: "SaaS exit scenarios are governed by well-known valuation multiples and acquirer categories. The template should incorporate SaaS-specific valuation methodologies." + field_changes: + - field: "Valuation methodology" + sector_label: "SaaS Valuation Multiples" + sector_guidance: "SaaS companies are valued on ARR multiples, modulated by growth rate and NRR. Report: current ARR, growth rate, NRR, and comparable company multiples (public and private). Rule of 40 score directly correlates with valuation multiples." + - field: "Potential acquirers" + sector_label: "SaaS Acquirer Landscape" + sector_guidance: "Categorize: (1) Strategic acquirers (larger SaaS companies in adjacent categories), (2) Platform acquirers (major platforms that benefit from adding your capability), (3) PE acquirers (private equity firms acquiring profitable SaaS businesses), (4) Public company acquirers (acqui-hires or tuck-in acquisitions)." + sections_to_add: + - section_name: "SaaS Valuation Benchmarks" + placement: "after:SaaS Valuation Multiples" + description: "Current market multiples for SaaS companies by growth and profitability profile." + fields: + - "Public SaaS median ARR multiple (current)" + - "Growth-adjusted ARR multiples (by Rule of 40 score)" + - "Recent comparable M&A transactions with multiples" + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "rule-of-40"] + + # ───────────────────────────────────────────── + # BOARD TEMPLATES (7) + # ───────────────────────────────────────────── + + - template: "quarterly-strategic-review" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "SaaS board meetings follow a well-established cadence and metric set. Board members expect specific SaaS KPIs, cohort data, and efficiency metrics presented in a standardized format." + field_changes: + - field: "Financial summary" + sector_label: "SaaS Financial Dashboard" + sector_guidance: "Present: ARR waterfall (opening ARR + new + expansion - contraction - churn = closing ARR), MRR trend chart (12 months), gross margin trend, burn rate, and runway. Compare each metric to plan and to prior quarter." + - field: "Strategic priorities" + sector_label: "OKR Progress and Strategic Priorities" + sector_guidance: "Report against quarterly OKRs with explicit metric outcomes. Flag any OKR that is off-track with root cause and corrective action. Present next quarter's strategic priorities with measurable targets." + - field: "Risks" + sector_label: "Risk Dashboard" + sector_guidance: "Categorize: Product risks (technical debt, competitive feature gaps), GTM risks (pipeline coverage, churn trends, CAC increases), People risks (key person dependency, attrition), and Financial risks (runway, unit economics trends)." + sections_to_add: + - section_name: "SaaS Metrics Summary" + placement: "before:SaaS Financial Dashboard" + description: "One-page SaaS metrics dashboard that board members can review in 60 seconds." + fields: + - "ARR and growth rate (QoQ and YoY)" + - "NRR and GRR" + - "Customer count and logo churn" + - "LTV:CAC and CAC Payback" + - "Burn Multiple and runway" + - "Rule of 40 score" + - section_name: "Cohort Performance" + placement: "after:SaaS Financial Dashboard" + description: "Retention and expansion data by acquisition cohort." + fields: + - "Cohort retention curves (logo and revenue)" + - "Cohort expansion trends" + - "Cohort quality assessment (are recent cohorts performing better or worse than earlier ones?)" + - section_name: "GTM Performance" + placement: "after:Cohort Performance" + description: "Go-to-market effectiveness metrics." + fields: + - "Pipeline coverage ratio" + - "Win rate (overall and by segment)" + - "Sales cycle length (trend)" + - "Magic Number" + - "CAC by channel" + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "grr", "ltv-cac-ratio", "cac-payback-period", "burn-multiple", "rule-of-40", "pipeline-coverage-ratio", "win-rate", "magic-number"] + + - template: "board-meeting-agenda" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "SaaS board meeting agendas should allocate time to the specific topics that SaaS board members expect: metrics review, GTM performance, product roadmap, and fundraising/runway discussion." + field_changes: + - field: "Agenda items" + sector_label: "SaaS Board Agenda" + sector_guidance: "Standard SaaS board agenda: (1) Metrics review — 15 min (pre-read, discussion only), (2) Strategic topic deep-dive — 30 min (one topic per meeting: GTM, product, hiring, pricing, competitive), (3) Fundraising/runway — 10 min, (4) CEO asks — 10 min (specific, actionable), (5) Executive session — 15 min. Total: 90 minutes maximum." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "risk-assessment-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "SaaS risk categories include sector-specific risks: infrastructure reliability, data security/privacy, platform dependency, and AI disruption." + field_changes: + - field: "Risk categories" + sector_label: "SaaS Risk Categories" + sector_guidance: "Include SaaS-specific categories: (1) Customer concentration risk — revenue dependency on top 10 customers. (2) Platform risk — dependency on cloud providers, API vendors, or distribution platforms. (3) Security and compliance risk — data breaches, regulatory changes, certification requirements. (4) Churn risk — NRR trend, cohort degradation, competitive displacement. (5) Technology risk — technical debt, AI disruption, architecture limitations." + sections_to_add: + - section_name: "Customer Concentration Analysis" + placement: "end" + description: "Revenue concentration risk assessment." + fields: + - "Revenue share of top 1, 5, and 10 customers" + - "Largest single-customer dependency as % of ARR" + - "Customer diversification trend (improving or worsening)" + sections_to_remove: [] + benchmark_references: ["nrr", "logo-churn", "arr"] + + - template: "change-initiative-proposal" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "Change initiative proposals follow a standard format. SaaS context is naturally incorporated through the specific initiative being proposed." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "compensation-review-brief" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "SaaS compensation includes equity-heavy packages, and comp benchmarking uses SaaS-specific data sources (Carta, Pave, levels.fyi for engineering)." + field_changes: + - field: "Compensation benchmarks" + sector_label: "SaaS Compensation Benchmarks" + sector_guidance: "Use SaaS-specific comp data: Pave, Carta, Levels.fyi (engineering), RepVue (sales). Benchmark by company stage (seed, Series A, B, C+), function, and geography. Include equity component as percentage of total comp." + sections_to_add: + - section_name: "Sales Compensation Structure" + placement: "end" + description: "SaaS sales compensation is structurally different and warrants specific analysis." + fields: + - "OTE structure (base:variable split, typically 50:50 for AEs)" + - "Quota-to-OTE ratio (industry standard: 4-6x)" + - "Accelerators and decelerators" + - "Quota attainment distribution" + sections_to_remove: [] + benchmark_references: ["acv"] + + - template: "regulatory-compliance-update" + audience: "board" + sector_adaptation: "modified" + adaptation_rationale: "SaaS compliance centers on data privacy (GDPR, CCPA), security certifications (SOC 2), and increasingly on AI regulation." + field_changes: + - field: "Regulatory landscape" + sector_label: "SaaS Compliance Landscape" + sector_guidance: "Cover: data privacy regulations (GDPR, CCPA, emerging state/national laws), security certifications (SOC 2 Type II status, ISO 27001), industry-specific compliance (HIPAA for health, PCI for payments), and AI regulation (EU AI Act, emerging US frameworks)." + sections_to_add: + - section_name: "Data Processing and Privacy" + placement: "end" + description: "SaaS-specific data handling compliance." + fields: + - "Data processing agreement (DPA) status with all customers" + - "Data residency and sovereignty compliance" + - "Sub-processor list and compliance status" + - "Data breach notification procedures and history" + sections_to_remove: [] + benchmark_references: [] + + - template: "ceo-succession-brief" + audience: "board" + sector_adaptation: "as-is" + adaptation_rationale: "CEO succession planning follows standard corporate governance practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # TEAM TEMPLATES (13) + # ───────────────────────────────────────────── + + - template: "action-plan" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS action plans should be metric-driven with clear KPI targets, owner assignments, and weekly measurement cadence." + field_changes: + - field: "Success metrics" + sector_label: "SaaS KPI Targets" + sector_guidance: "Define success using SaaS metrics: MRR impact, churn reduction target, activation rate improvement, NPS change, or pipeline coverage increase. Every action item should connect to a measurable SaaS KPI." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "new-initiative-brief" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS initiative briefs should include unit economics impact and the effect on key SaaS metrics." + field_changes: + - field: "Expected outcomes" + sector_label: "Expected SaaS Impact" + sector_guidance: "Quantify impact on SaaS metrics: expected MRR contribution, churn reduction, CAC improvement, activation rate increase, or NRR improvement. Include the time to measurable impact." + - field: "Resource requirements" + sector_label: "Resource Requirements and Opportunity Cost" + sector_guidance: "In SaaS, engineering capacity is the scarcest resource. Quantify the engineering weeks required and the opportunity cost — what will not be built if this initiative is prioritized." + sections_to_add: + - section_name: "Metric Impact Model" + placement: "after:Expected SaaS Impact" + description: "Quantitative model of how the initiative affects the SaaS flywheel." + fields: + - "Primary metric impacted and expected delta" + - "Secondary metrics affected" + - "Time to measurable impact" + - "Confidence level (high/medium/low) with supporting rationale" + sections_to_remove: [] + benchmark_references: ["mrr", "nrr", "cac", "activation-rate"] + + - template: "project-kickoff-document" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS project kickoffs should define success in terms of product metrics and include a measurement plan." + field_changes: + - field: "Success criteria" + sector_label: "Success Metrics and Measurement Plan" + sector_guidance: "Define 2-3 SaaS metrics that this project will move. Include baseline measurement, target, measurement method, and evaluation date. Common: activation rate, time to value, NPS delta, churn reduction, expansion MRR contribution." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["activation-rate", "time-to-value", "nrr"] + + - template: "hiring-scorecard" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS hiring scorecards should include SaaS-specific competency assessments, especially for GTM and product roles." + field_changes: + - field: "Required competencies" + sector_label: "SaaS-Specific Competencies" + sector_guidance: "For GTM roles: SaaS sales motion experience (PLG, inside sales, field sales), understanding of SaaS metrics, experience at the relevant company stage. For product roles: experience with subscription/usage products, data-driven product management, PLG or sales-led product experience. For engineering roles: SaaS architecture experience (multi-tenant, API-first, CI/CD)." + sections_to_add: + - section_name: "Stage Fit Assessment" + placement: "end" + description: "Assessment of whether the candidate's experience matches the company's current stage." + fields: + - "Candidate's company-stage experience (seed, growth, scale)" + - "Gap analysis between candidate experience and current needs" + - "Ramp-up timeline estimate" + sections_to_remove: [] + benchmark_references: [] + + - template: "incident-postmortem" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS incident postmortems must include customer impact quantification, SLA implications, and communication review." + field_changes: + - field: "Impact assessment" + sector_label: "Customer and Business Impact" + sector_guidance: "Quantify: number of customers affected, duration of impact, SLA breach (if any), revenue at risk (affected customer MRR), support tickets generated, social media mentions. Include the customer communication timeline and effectiveness." + sections_to_add: + - section_name: "SLA and Compliance Impact" + placement: "after:Customer and Business Impact" + description: "SaaS-specific contractual and compliance implications." + fields: + - "SLA breaches (if any) and credit obligations" + - "Regulatory notification requirements (if data affected)" + - "Customer communication log (when, what, how)" + sections_to_remove: [] + benchmark_references: [] + + - template: "retrospective-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Sprint and project retrospectives follow standard agile practices that are not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "meeting-notes-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Meeting notes structure is not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "one-on-one-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "One-on-one meeting structure is not sector-specific. The content naturally adapts to SaaS context." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "team-health-check" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS team health should include cross-functional alignment metrics, since SaaS requires tighter coordination between product, engineering, sales, and CS than most businesses." + field_changes: + - field: "Health indicators" + sector_label: "SaaS Team Health Indicators" + sector_guidance: "Include SaaS-specific indicators: product-engineering velocity (features shipped per sprint), sales-CS handoff quality (early churn correlation), cross-functional NPS (how teams rate their collaboration with other teams), and on-call burden (engineering burnout indicator)." + sections_to_add: + - section_name: "Cross-Functional Alignment Score" + placement: "end" + description: "Assessment of alignment between the key SaaS functions." + fields: + - "Product-Engineering alignment (roadmap clarity, tech debt balance)" + - "Sales-Product alignment (feature request feedback loop)" + - "Sales-CS alignment (handoff quality, expectation consistency)" + - "CS-Product alignment (churn feedback integration into roadmap)" + sections_to_remove: [] + benchmark_references: [] + + - template: "culture-values-document" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Culture and values documentation is not sector-specific. Values should be authentic to the company, not to the sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "feedback-360-template" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "360 feedback follows standard practices regardless of sector." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "offsite-planning-guide" + audience: "team" + sector_adaptation: "as-is" + adaptation_rationale: "Offsite planning is not sector-specific, though the content discussed at offsites will naturally address SaaS topics." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "role-description-template" + audience: "team" + sector_adaptation: "modified" + adaptation_rationale: "SaaS role descriptions should reference SaaS-specific experience requirements and the metrics the role is accountable for." + field_changes: + - field: "Key responsibilities" + sector_label: "Key Responsibilities and Metric Ownership" + sector_guidance: "For each responsibility, specify the SaaS metric the role owner is accountable for. Examples: VP Sales owns new ARR and win rate; VP CS owns NRR, GRR, and NPS; VP Product owns activation rate, time to value, and feature adoption." + - field: "Required experience" + sector_label: "SaaS Experience Requirements" + sector_guidance: "Specify: SaaS company-stage experience required, SaaS metric literacy expected, and specific SaaS domain experience (PLG, enterprise sales, usage-based pricing, etc.)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # SELF TEMPLATES (10) + # ───────────────────────────────────────────── + + - template: "weekly-ceo-review" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A SaaS CEO's weekly review should be structured around the SaaS metrics that drive decision-making, with a specific cadence of what to review weekly versus monthly." + field_changes: + - field: "Weekly metrics" + sector_label: "Weekly SaaS Dashboard" + sector_guidance: "Review weekly: MRR and WoW change, new sign-ups and activations, support ticket volume and response time, pipeline changes, cash balance. Monthly metrics (NRR, churn, CAC) should be reviewed on a monthly cadence, not weekly — weekly fluctuations are noise." + - field: "Priorities" + sector_label: "This Week's Priorities" + sector_guidance: "Identify the single most important thing for the week. In SaaS, this is often: closing a specific deal, resolving a customer escalation, making a hiring decision, or shipping a feature. Ruthless prioritization — not a list of 10 items." + sections_to_add: + - section_name: "Customer Signal Review" + placement: "after:Weekly SaaS Dashboard" + description: "Weekly review of qualitative customer signals." + fields: + - "Churn reasons this week (if any)" + - "Customer escalations and their resolution" + - "Positive signals (expansion conversations, referrals, testimonials)" + sections_to_remove: [] + benchmark_references: ["mrr", "activation-rate"] + + - template: "decision-journal" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS decision journals should explicitly capture the metrics that informed the decision and the metric-based criteria for evaluating whether the decision was correct." + field_changes: + - field: "Decision context" + sector_label: "Decision Context and Data" + sector_guidance: "Record: the SaaS metrics that informed this decision, the alternatives considered, and the specific metric outcome that will confirm the decision was correct. For reversible decisions, note the 'kill criteria' — what metric threshold would trigger reversal." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "annual-review-and-planning" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS annual reviews should assess performance against SaaS-specific milestones and set the following year's targets using SaaS benchmarks." + field_changes: + - field: "Year in review" + sector_label: "SaaS Year in Review" + sector_guidance: "Assess: ARR growth (actual vs. plan), NRR trend, unit economics evolution (LTV:CAC, CAC Payback), team growth, product milestones, and capital efficiency (burn multiple). Compare to beginning-of-year targets." + - field: "Next year goals" + sector_label: "Next Year SaaS Targets" + sector_guidance: "Set targets across all SaaS dimensions: ARR target, NRR target, efficiency targets (burn multiple, gross margin), product targets (activation rate, time to value), and team targets (headcount, key hires). Each target should reference the benchmark tier being targeted." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["arr", "nrr", "ltv-cac-ratio", "burn-multiple", "gross-margin"] + + - template: "stakeholder-map" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS stakeholder maps should include SaaS-ecosystem-specific stakeholder categories: platform partners, integration partners, investor syndicate members, and key customer champions." + field_changes: + - field: "Stakeholder categories" + sector_label: "SaaS Stakeholder Ecosystem" + sector_guidance: "Include: Investors (lead, follow-on, angels, advisors), Customers (champions, economic buyers, technical evaluators), Partners (platform, integration, channel, technology), Team (executives, key ICs, advisors), and Market (analysts, media, community leaders)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "negotiation-prep-sheet" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS negotiation prep should include SaaS-specific negotiation contexts and leverage points." + field_changes: + - field: "Negotiation type" + sector_label: "SaaS Negotiation Context" + sector_guidance: "Classify: enterprise deal (contract terms), fundraising (term sheet), partnership (integration/channel terms), M&A (acquisition terms), or internal (resource allocation, compensation). Each type has distinct SaaS-specific dynamics and leverage points." + - field: "BATNA" + sector_label: "BATNA and SaaS Leverage" + sector_guidance: "SaaS-specific leverage points: for sales — competitive alternatives, budget timing, multi-year commitment incentives. For fundraising — multiple term sheets, profitability path, strong metrics. For partnerships — integration value, customer overlap, competitive alternatives." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["acv", "arr"] + + - template: "career-strategy-canvas" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Career strategy is personal, not sector-specific." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "founder-mental-health-check" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS founder mental health is affected by SaaS-specific stressors: the relentlessness of monthly metrics, the public nature of SaaS performance data, and the compound pressure of continuous customer obligations." + field_changes: + - field: "Stress indicators" + sector_label: "SaaS-Specific Stress Indicators" + sector_guidance: "Include: obsessive metric checking (checking dashboards more than 3x daily), inability to disconnect (monitoring Slack/support channels outside work hours), identity fusion with MRR (self-worth tracking with revenue), and isolation (not discussing challenges with peers, advisors, or a therapist)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "leadership-reflection" + audience: "self" + sector_adaptation: "as-is" + adaptation_rationale: "Leadership reflection is not sector-specific. The reflections naturally address SaaS-specific challenges." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "learning-plan" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "SaaS founders should include SaaS-specific learning areas in their development plans." + field_changes: + - field: "Learning areas" + sector_label: "SaaS Learning Priorities" + sector_guidance: "Consider SaaS-specific learning areas: SaaS metrics and benchmarking, product-led growth mechanics, AI strategy and implementation, SaaS pricing optimization, enterprise sales motion design, customer success operations, and SaaS-specific financial modeling." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "personal-board-tracker" + audience: "self" + sector_adaptation: "modified" + adaptation_rationale: "A SaaS founder's personal board of advisors should include SaaS-specific expertise areas." + field_changes: + - field: "Advisor categories" + sector_label: "SaaS Advisory Needs" + sector_guidance: "Map advisors to SaaS-specific needs: SaaS metrics and operations (someone who has scaled a SaaS company to $50M+ ARR), GTM strategy (PLG expert or enterprise sales leader), Product (SaaS product leader), Technical (architecture and scaling), Finance (SaaS financial modeling and fundraising), and Industry/domain (vertical expertise for the target market)." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + # ───────────────────────────────────────────── + # CLIENT TEMPLATES (8) + # ───────────────────────────────────────────── + + - template: "quarterly-business-review" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS QBRs are the primary retention and expansion vehicle. The template should structure the QBR around value delivered, usage trends, and growth opportunities." + field_changes: + - field: "Performance summary" + sector_label: "Value Delivered" + sector_guidance: "Quantify the value the SaaS product delivered this quarter: time saved, revenue generated, costs reduced, errors prevented, or compliance maintained. Use the customer's own metrics and language, not your product metrics." + - field: "Account status" + sector_label: "Usage and Adoption Metrics" + sector_guidance: "Present: active users vs. licensed users, feature adoption by module, usage trend (growing, stable, declining), and comparison to peer accounts in the same segment." + - field: "Next steps" + sector_label: "Growth Opportunities" + sector_guidance: "Identify expansion opportunities: additional seats, new modules, higher tier, or new use cases. Frame as business outcomes, not product features. Include a mutual success plan with milestones for the next quarter." + sections_to_add: + - section_name: "Health Score" + placement: "before:Value Delivered" + description: "Overall account health assessment." + fields: + - "Account health score (methodology transparent to the customer)" + - "Usage trend indicator" + - "Support interaction summary" + - "Renewal timeline and status" + sections_to_remove: [] + benchmark_references: ["nrr", "nps-saas"] + + - template: "onboarding-welcome-packet" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS onboarding directly determines activation rate and time to value — two of the most important product metrics. The welcome packet should be structured to minimize time to value." + field_changes: + - field: "Getting started steps" + sector_label: "Time-to-Value Path" + sector_guidance: "Define the shortest path to the activation milestone. Organize steps as: (1) Critical first action (what to do in the first 30 minutes), (2) Foundation setup (first day), (3) Team onboarding (first week), (4) Full activation (first month). Each step should include estimated time and a clear 'done' criterion." + - field: "Resources" + sector_label: "Self-Serve Resources" + sector_guidance: "Include: knowledge base link, video tutorial library, community forum, and office hours schedule. Prioritize self-serve resources over human touch for scalability." + sections_to_add: + - section_name: "Success Milestones" + placement: "end" + description: "Defined milestones that predict long-term retention." + fields: + - "30-day activation milestone (specific action)" + - "60-day adoption milestone" + - "90-day value realization milestone" + - "Check-in schedule with customer success" + sections_to_remove: [] + benchmark_references: ["time-to-value", "activation-rate"] + + - template: "proposal-outline" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS proposals should frame the investment as an ongoing subscription with measurable ROI, not a one-time purchase." + field_changes: + - field: "Pricing" + sector_label: "Investment and ROI" + sector_guidance: "Present: subscription pricing (monthly and annual options), implementation costs (if any, presented separately), and a clear ROI model showing when the investment pays for itself. Frame as ongoing value delivery, not a cost." + - field: "Scope" + sector_label: "Implementation Scope and Timeline" + sector_guidance: "For SaaS: define the implementation phases (setup, data migration, integration, training, go-live), the timeline for each phase, and the customer's time commitment. Set expectations for time to value." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["acv", "time-to-value"] + + - template: "service-level-agreement" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS SLAs have specific standard structures: uptime commitments, support response times, data handling, and remediation terms." + field_changes: + - field: "Service levels" + sector_label: "SaaS Service Commitments" + sector_guidance: "Standard SaaS SLA components: (1) Uptime commitment (99.9% or 99.95% for enterprise), (2) Planned maintenance windows, (3) Support response time by severity (P0: 1 hour, P1: 4 hours, P2: 1 business day, P3: 2 business days), (4) Data backup and recovery commitments, (5) Security and compliance commitments." + - field: "Remediation" + sector_label: "Credit and Remediation Terms" + sector_guidance: "Define: service credit structure for SLA breaches (typically 5-10% of monthly fee per breach, capped at 30% of monthly fee), termination rights for sustained breaches, and notification obligations." + sections_to_add: + - section_name: "Data Processing Terms" + placement: "end" + description: "Data handling commitments standard in SaaS contracts." + fields: + - "Data ownership and portability" + - "Data processing and privacy (DPA reference)" + - "Data deletion upon contract termination" + - "Sub-processor disclosure" + sections_to_remove: [] + benchmark_references: [] + + - template: "project-status-update" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS project status updates (typically for implementation projects) should track progress toward the activation milestone and time to value." + field_changes: + - field: "Progress summary" + sector_label: "Implementation Progress" + sector_guidance: "Track against the implementation phases defined in the onboarding plan. Report: phase completion status, blockers (especially customer-side dependencies), and projected time to go-live/activation." + sections_to_add: [] + sections_to_remove: [] + benchmark_references: ["time-to-value"] + + - template: "analysis-report" + audience: "client" + sector_adaptation: "as-is" + adaptation_rationale: "Analysis report structure is not sector-specific. Content naturally adapts to SaaS context." + field_changes: [] + sections_to_add: [] + sections_to_remove: [] + benchmark_references: [] + + - template: "case-study-template" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS case studies should follow a quantified-outcome structure that buyers can use to build internal business cases." + field_changes: + - field: "Results" + sector_label: "Quantified Outcomes" + sector_guidance: "Every SaaS case study must include at least 2-3 quantified outcomes: time saved (hours/week), revenue impact (% increase or dollar amount), cost reduction (% or dollar amount), or error reduction (% decrease). Abstract outcomes ('improved efficiency') are insufficient." + - field: "Challenge" + sector_label: "Challenge and Buying Context" + sector_guidance: "Include: the business problem (not the product gap), what the customer was using before, what triggered the evaluation, and what other solutions they considered. This helps prospects see themselves in the story." + sections_to_add: + - section_name: "Implementation Details" + placement: "after:Quantified Outcomes" + description: "Practical details that help prospects understand the adoption path." + fields: + - "Implementation timeline" + - "Team involvement required" + - "Time to value (when outcomes were first realized)" + - "Integration with existing stack" + sections_to_remove: [] + benchmark_references: ["time-to-value"] + + - template: "partnership-memo" + audience: "client" + sector_adaptation: "modified" + adaptation_rationale: "SaaS partnership memos should address the integration architecture, data sharing terms, and go-to-market collaboration structure." + field_changes: + - field: "Partnership structure" + sector_label: "SaaS Partnership Structure" + sector_guidance: "Define: partnership type (technology integration, channel, platform, strategic alliance), technical integration scope (API access, data sharing, SSO, embedded/white-label), commercial terms (revenue share, referral fees, co-marketing budget), and governance (joint review cadence, escalation path, integration SLA)." + sections_to_add: + - section_name: "Integration Architecture" + placement: "after:SaaS Partnership Structure" + description: "Technical specification of the partnership integration." + fields: + - "Integration approach (API, webhook, embedded, SSO)" + - "Data sharing scope and limitations" + - "Security and compliance requirements" + - "Maintenance and versioning responsibilities" + sections_to_remove: [] + benchmark_references: [] diff --git a/plugins/foreman/content/language-mode/LANGUAGE-MODE.md b/plugins/foreman/content/language-mode/LANGUAGE-MODE.md new file mode 100644 index 0000000..57eb377 --- /dev/null +++ b/plugins/foreman/content/language-mode/LANGUAGE-MODE.md @@ -0,0 +1,159 @@ +# Language Mode — Orchestrator Instructions + +When `/language [code]` is active, ALL system outputs are delivered in the specified language. This is a complete output language switch — not translation of keywords, not partial localization, but full linguistic transformation of every response the system produces. + +--- + +## Core Principle + +The underlying content — frameworks, diagnostics, playbooks, skill logic — remains in English internally. The system THINKS in English (skill files, templates, routing logic are all English). But it SPEAKS in the target language. This is the same distinction a bilingual consultant makes: they read the McKinsey report in English, then present findings to the client in their language. + +What changes: every word the entrepreneur sees. +What does not change: internal processing, skill selection, routing logic, memory field names. + +--- + +## What Gets Translated + +| Component | Translation Scope | +|-----------|------------------| +| **Skill outputs** | Framework explanations, prompts, use cases, anti-patterns, stage guidance — all delivered in target language | +| **Diagnostic questions** | Triage questions rephrased naturally in target language — not word-for-word translation but culturally appropriate phrasing | +| **Playbook instructions** | Step descriptions, checkpoint questions, decision point framing | +| **Output template content** | Section headers, guidance text, placeholder labels — all in target language | +| **System messages** | Confirmations, errors, status reports, help text | +| **Stoic mode additions** | Stoic reflections, virtue framing, premeditatio malorum — in target language | +| **Solo mode messages** | All solo-specific framing and adaptations | + +## What Does NOT Get Translated + +| Component | Reason | +|-----------|--------| +| **Skill file names** | `porters-five-forces.md` stays as-is — these are system identifiers | +| **Command syntax** | `/apply`, `/diagnose`, `/run` stay in English — they are CLI commands | +| **Frontmatter field names** | `name:`, `description:`, `category:` — internal metadata | +| **Framework proper names** | "Porter's Five Forces" remains "Porter's Five Forces" (with optional target-language explanation in parentheses on first mention) | +| **Memory field names** | `identity.name`, `company.stage` — system internals | +| **Stoic source attributions** | "Marcus Aurelius, Meditations 5.20" — proper names and work titles stay in original | + +--- + +## Framework Name Handling + +Framework proper names require special care. The rule: + +1. **First mention**: Use the English name followed by a natural target-language explanation. + - Turkish: "Porter'in Bes Gucü (Porter's Five Forces) analizi..." + - Spanish: "El análisis de las Cinco Fuerzas de Porter (Porter's Five Forces)..." + - German: "Porters Fünf-Kräfte-Analyse (Porter's Five Forces)..." + - Japanese: "ポーターのファイブフォース分析（Porter's Five Forces）..." + +2. **Subsequent mentions**: Use whichever form is more natural in the target language. If the framework has an established local name, use it. If not, use the English name. + +3. **Acronyms**: Keep in English with target-language expansion. + - "SWOT analizi (Strengths, Weaknesses, Opportunities, Threats)" + - "BMC (Business Model Canvas / Is Modeli Tuvali)" + +--- + +## Translation Quality Standards + +This is NOT machine-translation quality. The system must produce output that reads as if a native-speaking consultant wrote it: + +1. **Natural syntax**: Follow the target language's sentence structure, not English word order imposed on foreign words. +2. **Idiomatic expression**: Use natural idioms and phrasing. "The ball is in your court" does not translate literally — use the local equivalent. +3. **Register consistency**: Maintain the Foreman voice (analytical, institutional, sophisticated) in the target language. If the language has formal/informal registers (tu/vous, sen/siz, du/Sie), default to formal-but-not-stiff. +4. **Business vocabulary**: Use the target language's established business terminology. Do not invent translations for terms that have accepted local forms. +5. **Cultural calibration**: Some frameworks reference culturally specific examples (American sports analogies, Silicon Valley references). Adapt these to be culturally neutral or locally relevant when possible. + +--- + +## Supported Languages + +Any language the underlying model supports. No explicit whitelist — if the model can produce fluent output in a language, that language is supported. Common expected languages: + +| Code | Language | Notes | +|------|----------|-------| +| `english` / `en` | English | Default. Also activated by `/language default`. | +| `turkish` / `tr` | Turkish | Formal register (siz). Business Turkish conventions. | +| `spanish` / `es` | Spanish | Latin American vs. Castilian — use neutral Spanish unless specified. | +| `french` / `fr` | French | Formal (vous). | +| `german` / `de` | German | Formal (Sie). | +| `portuguese` / `pt` | Portuguese | Brazilian vs. European — default to Brazilian unless specified. | +| `japanese` / `ja` | Japanese | Desu/masu form. Business keigo where appropriate. | +| `chinese` / `zh` | Chinese | Simplified Mandarin default. | +| `korean` / `ko` | Korean | Formal (합니다체). | +| `arabic` / `ar` | Arabic | Modern Standard Arabic (fusha). | +| `dutch` / `nl` | Dutch | Formal (u). | +| `italian` / `it` | Italian | Formal (Lei). | +| `russian` / `ru` | Russian | Formal (Вы). | +| `hindi` / `hi` | Hindi | Formal register. | + +Both full language names and ISO 639-1 codes are accepted. Case-insensitive. + +--- + +## Interaction with Other Modes + +### Language + Industry Packs + +Language mode translates sector-specific content from industry packs identically to any other content. SaaS benchmarks in Turkish, fintech regulatory terms in Spanish, marketplace take-rate metrics in Japanese — the language switch applies to industry pack overlays, diagnostic rules, and template adaptations. Sector-specific terminology uses the target language's established business vocabulary where it exists. Framework proper names follow the same first-mention convention described above. + +### Language + Solo Mode + +Both active simultaneously. Solo mode filters WHAT content appears. Language mode determines WHICH LANGUAGE that content appears in. No conflict. + +Example: `/solo` + `/language turkish` = solopreneur-adapted content delivered entirely in Turkish. + +### Language + Stoic Mode + +Both active simultaneously. Stoic mode adds philosophical depth. Language mode translates that depth into the target language — including Stoic quotes. + +Stoic quote handling in non-English languages: +1. Present the quote in the TARGET language (translated naturally). +2. Follow with the original language attribution: "— Marcus Aurelius, Meditations 5.20" +3. Do NOT present the English translation unless the target language reader would benefit from seeing the original Latin/Greek-derived English version. + +Example in Turkish: +> "Engel yolu olur. Yolunda duran sey, yolun kendisi olur." +> — Marcus Aurelius, Meditations 5.20 + +### Language + Commands + +Command SYNTAX stays in English: `/apply`, `/diagnose`, `/run`, `/stoic on`, `/solo`. +Command OUTPUT switches to the target language. + +Example: +``` +User: /skills frameworks +System (if /language turkish): + Frameworks kategorisinde 50 skill mevcut: + - porters-five-forces — Rekabetci sanayi dinamiklerini analiz eder... + - swot-pest-analysis — Ic ve dis stratejik analiz cerceveleri... + ... +``` + +--- + +## Memory Integration + +| Field | Layer | Value | +|-------|-------|-------| +| `language` | identity | ISO 639-1 code or full name (e.g., "tr" or "turkish") | +| `language_set_date` | identity | ISO 8601 date | + +Language preference persists across sessions. Once set, every future session starts in the selected language until changed. + +The memory-agent reads `identity.language` at session start. If present and not "en"/"english", the orchestrator activates language mode automatically — no need to re-invoke `/language` each session. + +--- + +## Edge Cases + +**Mixed-language input**: If the entrepreneur writes in Turkish but language mode is set to English, respond in the SET language (English), not the input language. The mode determines output language, not the input. + +**Language not recognized**: If the code/name is not recognizable, respond: "Language '[input]' not recognized. Use a language name (e.g., 'turkish', 'spanish') or ISO 639-1 code (e.g., 'tr', 'es'). Use '/language default' for English." + +**Partial language names**: Accept common variations. "türkçe" = "turkish" = "tr". "deutsch" = "german" = "de". "español" = "spanish" = "es". + +**Regional variants**: If a user specifies "pt-BR" or "brazilian portuguese", honor the variant. If just "portuguese", default to Brazilian. If "zh-TW", use Traditional Chinese. If just "chinese", use Simplified Mandarin. diff --git a/plugins/foreman/content/memory/_schema/memory-schema.md b/plugins/foreman/content/memory/_schema/memory-schema.md new file mode 100644 index 0000000..9396d56 --- /dev/null +++ b/plugins/foreman/content/memory/_schema/memory-schema.md @@ -0,0 +1,191 @@ +--- +name: "memory-schema" +description: "Defines the five-layer memory architecture that persists entrepreneur context across sessions. Each layer has a distinct change frequency, ownership model, and data structure." +version: "1.0.0" +author: "Fatih Guner" +--- + +> Runtime note: These layers describe conceptual and legacy memory. Current writes use the versioned state and migration protocol in `.claude/RUNTIME.md`. Do not create a second active store. + +# Memory Schema + +The memory system maintains entrepreneur context across sessions through five layers, each operating at a different temporal frequency. Together they enable the system to behave less like a stateless tool and more like a mentor who remembers. + +--- + +## Architecture Overview + +``` +Layer 1: Identity (changes: ~yearly) — Who is the entrepreneur? +Layer 2: Company (changes: ~monthly) — What is the company's current state? +Layer 3: History (changes: append-only) — What has happened before? +Layer 4: Active (changes: ~weekly) — What is in progress right now? +Layer 5: Session (changes: per message) — What is happening this conversation? +``` + +Each layer is stored as an independent YAML file within the entrepreneur's directory. This separation ensures that updating one layer never risks corrupting another, and that each layer can be read independently when full context is unnecessary. + +--- + +## Layer Definitions + +### Layer 1: Identity + +**File:** `identity.yaml` +**Change frequency:** Rarely — updated when the entrepreneur's role, background, or preferences shift +**Owner:** Entrepreneur provides, system records +**Purpose:** Personalizes tone, complexity, and framing of all system outputs + +| Field | Type | Description | +|-------|------|-------------| +| `name` | string | Entrepreneur's name | +| `role` | string | Current role (Founder, CEO, CTO, etc.) | +| `background` | string | Professional background (technical, business, design, etc.) | +| `leadership_style` | string | Observed or self-reported leadership tendencies | +| `communication_preference` | string | How they prefer to receive information (direct, narrative, data-driven) | +| `known_strengths` | list | 3-5 identified strengths | +| `known_weaknesses` | list | 3-5 identified growth areas | +| `personality_notes` | string | Behavioral observations that affect how the system should interact | + +**Read by:** orchestrator-agent (every session start), skill-executor-agent (tone calibration), output-agent (formatting decisions) +**Written by:** memory-agent on first interaction, updated when entrepreneur reveals new information + +--- + +### Layer 2: Company + +**File:** `company.yaml` +**Change frequency:** Monthly or quarterly — updated when metrics, stage, or structure change +**Owner:** Entrepreneur provides updates, system prompts for refresh when data appears stale +**Purpose:** Enables stage filtering, metric-informed diagnosis, and contextual skill application + +| Field | Type | Description | +|-------|------|-------------| +| `name` | string | Company name | +| `stage` | enum | `idea`, `validation`, `early-traction`, `growth`, `scale` | +| `sector` | string | Industry and sub-sector | +| `team_size` | integer | Current headcount | +| `funding.raised` | string | Total funding raised | +| `funding.runway_months` | integer | Months of runway remaining | +| `funding.next_round` | string | Planned next round and timing | +| `metrics.mrr` | string | Monthly recurring revenue | +| `metrics.growth_rate` | string | Month-over-month growth | +| `metrics.churn` | string | Monthly churn rate | +| `metrics.nps` | integer | Net Promoter Score | +| `business_model` | string | Revenue model description | +| `key_challenges` | list | Top 3-5 current challenges | +| `competitive_landscape` | string | Brief competitive context | + +**Staleness rule:** If `company.yaml` has not been updated in 90 days, memory-agent prompts for refresh at next session start. +**Read by:** orchestrator-agent (stage filtering), diagnostic-agent (metric-informed triage), skill-executor-agent (contextual application) +**Written by:** memory-agent when entrepreneur provides updates or when metrics are mentioned in conversation + +--- + +### Layer 3: History + +**File:** `history.yaml` +**Change frequency:** Append-only — entries are added, never modified or deleted +**Owner:** System writes automatically after each significant interaction +**Purpose:** Prevents redundant analysis, enables "we already explored this" context, tracks decision patterns + +| Section | Entry Fields | Description | +|---------|-------------|-------------| +| `diagnostics_run` | date, diagnostic, result, confidence | Every diagnostic executed with its outcome | +| `skills_applied` | date, skill, context, key_insight | Every skill application with the primary finding | +| `decisions_made` | date, decision, rationale, outcome, review_date, related_skill | Every significant decision with reasoning and follow-up | +| `playbooks_completed` | date, playbook, status, key_outcome | Every playbook run with completion status | +| `outputs_generated` | date, template, audience, context | Every output template produced | + +**Append rules:** +- A diagnostic entry is added after every diagnostic-agent run +- A skill entry is added after every skill-executor-agent application +- A decision entry is added when the entrepreneur explicitly commits to a course of action +- Outcome fields are updated during follow-up reviews (the only exception to append-only) + +**Read by:** diagnostic-agent (avoid re-diagnosing known issues), skill-executor-agent (reference prior insights), orchestrator-agent (continuity awareness) +**Written by:** memory-agent at end of each session via PRUNE_SESSION operation + +--- + +### Layer 4: Active + +**File:** `active.yaml` +**Change frequency:** Weekly — updated as playbooks progress, decisions resolve, follow-ups arrive +**Owner:** System manages, entrepreneur confirms +**Purpose:** Tracks work in progress — ensures nothing falls through the cracks between sessions + +| Section | Entry Fields | Description | +|---------|-------------|-------------| +| `current_playbook` | name, current_step, started, status, completed_steps[], next_step, blocker | The playbook currently being executed | +| `pending_decisions` | decision, deadline, related_diagnostic, options_considered[] | Decisions that have been framed but not yet made | +| `follow_ups` | date, type, context | Scheduled review dates for past decisions or milestones | + +**Lifecycle rules:** +- When a playbook completes → move to `history.playbooks_completed`, clear from active +- When a decision is made → move to `history.decisions_made`, clear from pending +- When a follow-up date passes → memory-agent raises it at next session start +- When a blocker resolves → update `next_step`, clear blocker field + +**Read by:** orchestrator-agent (session start — "you have a pending decision due Friday"), playbook-runner-agent (resume from checkpoint) +**Written by:** memory-agent after each session, playbook-runner-agent during execution + +--- + +### Layer 5: Session + +**File:** `session.yaml` +**Change frequency:** Every message — ephemeral, exists only during active conversation +**Owner:** System creates and destroys automatically +**Purpose:** Maintains conversation context, accumulates data for end-of-session persistence + +| Field | Type | Description | +|-------|------|-------------| +| `started` | datetime | Session start timestamp | +| `topic` | string | Primary topic identified from first message | +| `hooks_triggered` | list | Which hooks matched during this session | +| `current_context` | list | Running notes on what is being discussed | +| `messages_exchanged` | integer | Conversation length counter | +| `skills_invoked` | list | Skills applied during this session | +| `temp_notes` | list | Observations to evaluate for persistence at session end | + +**End-of-session protocol (PRUNE_SESSION):** + +``` +For each item in session: + if decision_made → append to history.decisions_made + create active.follow_up + if skill_applied → append to history.skills_applied + if diagnostic_run → append to history.diagnostics_run + if playbook_progressed → update active.current_playbook + if company_data_mentioned → update company.yaml + if identity_insight_revealed → update identity.yaml + discard remaining temp_notes and session metadata + delete session.yaml +``` + +--- + +## Cross-Layer Interactions + +| Operation | Trigger | Reads | Writes | +|-----------|---------|-------|--------| +| SESSION_START | Conversation begins | Identity + Company + Active | Session (create) | +| CONTEXT_CHECK | Orchestrator needs background | History (relevant entries) | — | +| SKILL_COMPLETE | Skill executor finishes | — | Session.skills_invoked | +| DECISION_MADE | Entrepreneur commits | — | Session.temp_notes | +| PLAYBOOK_STEP | Playbook runner advances | Active.current_playbook | Active.current_playbook | +| SESSION_END | Conversation ends | Session (all) | History + Active + Company (selective) | +| STALENESS_CHECK | Session start | Company.last_updated | — (prompts if stale) | +| FOLLOW_UP_CHECK | Session start | Active.follow_ups | — (raises overdue items) | + +--- + +## Data Governance + +**Retention:** History is permanent. Active is cleared when items complete. Session is destroyed after each conversation. + +**Privacy:** All memory is entrepreneur-specific. No cross-entrepreneur data sharing. Memory files reside within the entrepreneur's own directory. + +**Portability:** YAML format ensures memory can be exported, backed up, or migrated without system dependency. + +**Right to forget:** An entrepreneur can request deletion of any layer at any time. The system confirms, executes, and does not retain shadows of deleted data. diff --git a/plugins/foreman/content/memory/_template/active-template.yaml b/plugins/foreman/content/memory/_template/active-template.yaml new file mode 100644 index 0000000..c706233 --- /dev/null +++ b/plugins/foreman/content/memory/_template/active-template.yaml @@ -0,0 +1,41 @@ +# Layer 4: Active +# Change frequency: weekly +# Owner: System manages, entrepreneur confirms +# Purpose: Tracks in-progress work — playbooks, pending decisions, follow-ups +# Lifecycle: Items move to history when completed, cleared from active + +active: + current_playbook: null + # Format when active: + # current_playbook: + # name: "fundraising-playbook" + # current_step: 3 + # started: "2026-03-25" + # status: "in-progress" + # completed_steps: + # - step: 1 + # skill: "business-model-canvas" + # output: "Canvas revised — new value proposition for enterprise segment" + # - step: 2 + # skill: "swot-pest-analysis" + # output: "SWOT completed — key weakness: churn rate for due diligence" + # next_step: + # step: 3 + # skill: "porters-five-forces" + # blocker: null + + pending_decisions: [] + # Entry format: + # - decision: "Hire VP Sales or promote internally?" + # deadline: "2026-04-01" + # related_diagnostic: "hiring-diagnosis" + # options_considered: + # - "External VP — faster but expensive, culture risk" + # - "Promote Sarah — loyal but untested at VP level" + + follow_ups: [] + # Entry format: + # - date: "2026-04-18" + # type: "decision-review" + # context: "Review onboarding specialist hire outcome" + # status: "pending" diff --git a/plugins/foreman/content/memory/_template/company-template.yaml b/plugins/foreman/content/memory/_template/company-template.yaml new file mode 100644 index 0000000..05145af --- /dev/null +++ b/plugins/foreman/content/memory/_template/company-template.yaml @@ -0,0 +1,31 @@ +# Layer 2: Company +# Change frequency: monthly/quarterly +# Owner: Entrepreneur provides, system prompts for refresh +# Purpose: Stage filtering, metric-informed diagnosis, contextual application +# Staleness rule: prompt for refresh if not updated in 90 days + +company: + name: "" + stage: "" # idea | validation | early-traction | growth | scale + sector: "" # Industry and sub-sector + team_size: 0 + funding: + raised: "" # Total raised to date + runway_months: 0 + next_round: "" # Planned round and target timing + metrics: + mrr: "" # Monthly recurring revenue + arr: "" # Annual recurring revenue + growth_rate: "" # Month-over-month growth percentage + churn: "" # Monthly churn rate + nps: 0 # Net Promoter Score (-100 to 100) + cac: "" # Customer acquisition cost + ltv: "" # Customer lifetime value + business_model: "" # Subscription, marketplace, transactional, etc. + key_challenges: + - "" + - "" + - "" + competitive_landscape: "" # Brief competitive context + created: "" # ISO 8601 date + last_updated: "" # ISO 8601 date diff --git a/plugins/foreman/content/memory/_template/history-template.yaml b/plugins/foreman/content/memory/_template/history-template.yaml new file mode 100644 index 0000000..9d76c08 --- /dev/null +++ b/plugins/foreman/content/memory/_template/history-template.yaml @@ -0,0 +1,43 @@ +# Layer 3: History +# Change frequency: append-only +# Owner: System writes automatically +# Purpose: Prevents redundant analysis, enables continuity, tracks decision patterns +# Rule: Entries are added, never modified (except outcome fields during reviews) + +history: + diagnostics_run: [] + # Entry format: + # - date: "2026-01-15" + # diagnostic: "revenue-diagnosis" + # result: "high-churn" + # confidence: "high" + + skills_applied: [] + # Entry format: + # - date: "2026-01-15" + # skill: "net-promoter-score" + # context: "Churn root cause analysis" + # key_insight: "Detractors concentrated in first-30-day cohort" + + decisions_made: [] + # Entry format: + # - date: "2026-01-18" + # decision: "Hired onboarding specialist instead of second sales rep" + # rationale: "Churn reduction has higher ROI than new acquisition" + # outcome: "pending" + # review_date: "2026-02-18" + # related_skill: "evaluating-and-deciding" + + playbooks_completed: [] + # Entry format: + # - date: "2026-01-20" + # playbook: "team-rebuild-playbook" + # status: "completed" + # key_outcome: "Restructured hiring process, 3 new role descriptions created" + + outputs_generated: [] + # Entry format: + # - date: "2026-01-18" + # template: "unit-economics-snapshot" + # audience: "investor" + # context: "Series A preparation" diff --git a/plugins/foreman/content/memory/_template/identity-template.yaml b/plugins/foreman/content/memory/_template/identity-template.yaml new file mode 100644 index 0000000..138294e --- /dev/null +++ b/plugins/foreman/content/memory/_template/identity-template.yaml @@ -0,0 +1,25 @@ +# Layer 1: Identity +# Change frequency: ~yearly +# Owner: Entrepreneur provides, system records +# Purpose: Personalizes tone, complexity, and framing + +identity: + mode: "standard" # standard | solo + stoic_mode: false + language: "en" + name: "" + role: "" # Founder & CEO, CTO, COO, etc. + background: "" # Technical, business, design, finance, etc. + leadership_style: "" # Observed tendencies under normal and stress conditions + communication_preference: "" # Direct, narrative, data-driven, visual, etc. + known_strengths: + - "" + - "" + - "" + known_weaknesses: + - "" + - "" + - "" + personality_notes: "" # Behavioral observations affecting interaction style + created: "" # ISO 8601 date + last_updated: "" # ISO 8601 date diff --git a/plugins/foreman/content/memory/_template/session-template.yaml b/plugins/foreman/content/memory/_template/session-template.yaml new file mode 100644 index 0000000..511c24d --- /dev/null +++ b/plugins/foreman/content/memory/_template/session-template.yaml @@ -0,0 +1,31 @@ +# Layer 5: Session +# Change frequency: per message (ephemeral) +# Owner: System creates at conversation start, destroys at conversation end +# Purpose: Maintains conversation context, accumulates data for persistence +# Lifecycle: Important data migrates to History/Active at session end, rest is discarded + +session: + started: "" # ISO 8601 datetime + topic: "" # Primary topic from first message + hooks_triggered: [] # Which hooks matched + current_context: [] # Running notes on discussion + messages_exchanged: 0 + skills_invoked: [] # Skills applied this session + diagnostics_run: [] # Diagnostics executed this session + temp_notes: [] # Observations to evaluate for persistence + # temp_note format: + # - note: "Founder mentioned losing key customer last week" + # persist_candidate: true + # target_layer: "company" # identity | company | history | active + +# END-OF-SESSION PROTOCOL (executed by memory-agent): +# +# 1. For each skill in skills_invoked → append to history.skills_applied +# 2. For each diagnostic in diagnostics_run → append to history.diagnostics_run +# 3. For each temp_note where persist_candidate = true: +# - target_layer = "history" → append to appropriate history section +# - target_layer = "company" → update company field +# - target_layer = "identity" → update identity field +# - target_layer = "active" → add to active.follow_ups or pending_decisions +# 4. If playbook progressed → update active.current_playbook +# 5. Delete session.yaml diff --git a/plugins/foreman/content/org-politics/ORG-POLITICS.md b/plugins/foreman/content/org-politics/ORG-POLITICS.md new file mode 100644 index 0000000..27f5cf1 --- /dev/null +++ b/plugins/foreman/content/org-politics/ORG-POLITICS.md @@ -0,0 +1,186 @@ + + +# Organizational Politics Navigation -- Strategic Stakeholder Intelligence + +Politics is not a dirty word. It is the physics of human organization. Wherever two or more people share a resource, a decision, or an outcome, politics emerges -- not as corruption, but as the natural process by which competing interests negotiate coexistence. Entrepreneurs who dismiss organizational politics as beneath them do not transcend it; they are defeated by it. The founder who cannot read a boardroom, anticipate resistance to a pivot, or build a coalition for a strategic initiative will lose to the founder who can -- regardless of whose product is superior. + +This system teaches the physics. It does not teach manipulation. The distinction matters, and it is structural, not rhetorical. + +--- + +## What Organizational Politics Navigation Is + +Organizational politics navigation is the disciplined practice of mapping stakeholder dynamics -- power structures, interest alignments, resistance patterns, and influence networks -- and designing strategies that create alignment through legitimate means. It operates on a simple premise: every initiative requires human cooperation, and human cooperation requires understanding what each person wants, fears, and controls. + +The system serves entrepreneurs who must: +- Convince a cofounder to change direction +- Align a board behind a controversial strategy +- Navigate investor dynamics during a fundraise +- Manage enterprise sales where the champion, economic buyer, and blocker are different people +- Drive organizational change when parts of the team resist + +--- + +## The Stakeholder Power Framework + +Every stakeholder is mapped across three dimensions, producing a three-dimensional picture that determines engagement strategy. + +### Dimension 1: Position + +Where the stakeholder stands on your initiative, ranging across five postures: + +| Position | Behaviour | Signal | +|----------|-----------|--------| +| **Champion** | Actively advocates for the initiative | Volunteers resources, persuades others, defends publicly | +| **Supporter** | Agrees but does not actively promote | Votes yes when asked, does not volunteer effort | +| **Neutral** | No stated position, could move either way | Waits for consensus, asks procedural questions | +| **Skeptic** | Has concerns, open to persuasion | Raises objections, asks for evidence, delays commitment | +| **Blocker** | Actively opposes, works to prevent | Lobbies against, withholds resources, escalates to authority | + +### Dimension 2: Power Level + +The stakeholder's ability to affect the outcome, regardless of their position: + +- **High** -- Can unilaterally approve, veto, or redirect. Holds budget authority, board vote, or organizational control. +- **Medium** -- Cannot decide alone but significantly influences those who can. Holds expertise, relationships, or information that decision-makers rely on. +- **Low** -- Limited direct influence on the outcome. May be affected by the decision but cannot shape it. + +### Dimension 3: Interest Level + +How much the stakeholder cares about the initiative: + +- **High** -- The initiative directly affects their role, resources, authority, or career. They will engage actively. +- **Medium** -- The initiative affects them indirectly. They will engage if prompted but will not seek involvement. +- **Low** -- The initiative is peripheral to their concerns. They will not engage unless forced. + +The three dimensions interact. A high-power, high-interest blocker demands immediate attention. A high-power, low-interest neutral can be left alone until their engagement becomes necessary. A low-power champion may be useful as a messenger but cannot deliver decisions. + +--- + +## Five Political Patterns + +### 1. Resistance to Change + +The most common pattern. Stakeholders resist not because they are irrational but because change threatens something they value -- status, competence, relationships, certainty, or control. Diagnosis requires distinguishing rational objection from political positioning. + +### 2. Coalition Formation + +Stakeholders with aligned interests band together to amplify their power. Coalitions form informally (hallway conversations, side meetings) before they manifest formally (block votes, joint objections). The entrepreneur must understand coalition dynamics to build alliances and anticipate opposition blocs. + +### 3. Power Brokering + +Certain stakeholders accumulate influence by controlling access -- to information, to decision-makers, to resources. They may not hold formal authority but operate as gatekeepers whose cooperation is essential. Identifying power brokers is often more important than identifying formal decision-makers. + +### 4. Information Asymmetry + +Knowledge is power in its most literal form. Stakeholders who control information -- market data, financial reports, customer feedback, competitive intelligence -- shape decisions by controlling what others know. The entrepreneur must map who has what information and whether it is being shared, withheld, or selectively disclosed. + +### 5. Organizational Inertia + +The collective tendency to preserve existing structures, processes, and power distributions. Inertia is not one person's resistance; it is the organization's immune system responding to a perceived threat. Overcoming inertia requires building enough momentum through coalition and narrative to cross the activation threshold. + +--- + +## Legitimate Influence vs. Manipulation + +The boundary between influence and manipulation is intent and transparency, not technique. + +| Legitimate Influence | Manipulation | +|---------------------|-------------| +| Aligning interests -- finding mutual benefit | Fabricating interests -- creating false mutual benefit | +| Building coalitions -- assembling genuine support | Manufacturing consent -- creating the illusion of support | +| Framing narratives -- presenting truth from the most persuasive angle | Distorting narratives -- presenting falsehoods as truth | +| Strategic timing -- choosing the right moment to advance | Ambush timing -- choosing the moment when resistance is weakest due to fatigue or distraction | +| Relationship building -- investing in genuine trust | Relationship exploitation -- leveraging trust to extract concessions | + +Foreman teaches the left column. The right column is not merely unethical; it is strategically inferior. Manipulation produces compliance that evaporates under stress. Legitimate influence produces commitment that strengthens under pressure. + +--- + +## Integration with Existing Skills + +Organizational politics navigation does not operate in isolation. It draws from and routes to the broader Foreman skill ecosystem: + +- **Thomas-Kilmann Conflict Modes** -- When resistance becomes conflict, TKI determines the appropriate mode: collaborate with a rational skeptic, compete against an entrenched blocker threatening the company's survival, accommodate on peripheral issues to preserve capital for central battles. +- **Cialdini's Influence Principles** -- The tactical toolkit for stakeholder engagement. Reciprocity for building goodwill, social proof for demonstrating momentum, authority for establishing credibility, unity for creating shared identity within a coalition. +- **Coalition and Partnership Games** -- The mathematical framework for understanding alliance stability. When building a coalition for board approval, Shapley Value logic reveals which supporters contribute the most and deserve the most investment. +- **Trust Equation** -- The diagnostic for relationship health. Before attempting to influence a skeptic, assess whether the trust foundation (credibility, reliability, intimacy, low self-orientation) can bear the weight of the ask. +- **Negotiation Skills** -- When stakeholder engagement becomes a negotiation (as it often does), cooperative negotiation frameworks structure the conversation for mutual gain. + +--- + +## Integration with Memory + +Stakeholder data is not static. Positions shift, alliances form and dissolve, power structures change with every hire, departure, and reorganization. The memory system captures this evolution: + +- **Company layer** -- Stores the canonical stakeholder map, updated monthly or after significant organizational changes. +- **Active layer** -- Tracks current initiative-specific stakeholder positions, updated weekly during active political navigation. +- **History layer** -- Records how stakeholder positions evolved over time, enabling pattern recognition. ("The CFO blocked the last two technology investments -- this is a pattern, not an anomaly.") +- **Session layer** -- Holds working analysis during a political navigation session. + +The `/stakeholders` command reads from memory to display the current map. Every update from diagnostics, playbooks, or commands writes back to memory. + +--- + +## Integration with Simulation + +Board Simulation becomes a political rehearsal tool. When the entrepreneur faces a difficult stakeholder conversation, simulation provides practice: + +- "The CFO is blocking the initiative -- simulate the next board meeting where you must address their concerns." +- "Your lead investor is pushing for a pivot you believe is wrong -- simulate the confrontation." +- "The VP of Engineering is a passive resister -- simulate the one-on-one where you surface the resistance." + +Simulation personas map to political archetypes. The skeptic-investor persona doubles as a skeptical board member. The operational-expert persona represents the detail-oriented blocker who demands proof. + +--- + +## Integration with Stoic Mode + +Political navigation activates emotional responses -- frustration with blockers, anxiety about coalitions, resentment toward opponents. Stoic mode reframes these responses: + +- **Dichotomy of control:** "You control your proposal, your preparation, and your conduct. You do not control the board member's vote. Direct your energy accordingly." +- **Cardinal virtues:** Justice demands understanding the blocker's perspective before condemning it. Temperance prevents escalation when patience serves better. Courage enables the difficult conversation. Wisdom distinguishes battles worth fighting from those worth ceding. +- **Amor fati:** "The resistance you face is the resistance you needed. It forced you to strengthen the proposal, build a broader coalition, and develop skills you would not have developed otherwise." + +--- + +## Integration with Solo Mode + +Solo entrepreneurs face organizational politics in a different arena. The stakeholders are external rather than internal: + +- **Clients** who resist scope changes or payment terms +- **Partners** who control distribution, technology, or access +- **Vendors** who hold leverage through dependency +- **Investors** (if applicable) who impose conditions +- **Industry gatekeepers** who control access to markets or communities + +The political patterns remain identical -- resistance, coalition, power brokering, information asymmetry, inertia -- but the context shifts from internal navigation to external relationship management. Solo mode adapts all diagnostics, playbooks, and templates to this external framing. + +--- + +## Ethical Boundaries + +This system will NOT assist with: + +- **Deception** -- fabricating information, misrepresenting positions, creating false narratives +- **Coercion** -- using threats, intimidation, or blackmail to force compliance +- **Backstabbing** -- undermining stakeholders through covert action while maintaining a facade of support +- **Retaliation** -- punishing stakeholders for opposing an initiative +- **Exploitation** -- leveraging personal vulnerabilities, private information, or trust for political gain +- **Exclusion** -- systematically isolating stakeholders from information or decision processes to weaken their position + +If a navigation strategy requires any of these tactics to succeed, the strategy is wrong -- not the ethics. Foreman will route to alternative approaches that achieve alignment through legitimate means, or will advise that the initiative cannot be achieved through political navigation alone and may require structural change, compromise, or abandonment. + +--- + +## System Components + +| Component | File | Purpose | +|-----------|------|---------| +| Stakeholder Resistance Diagnosis | `stakeholder-resistance-diagnosis.md` | Diagnose why stakeholders resist and determine root causes | +| Power Dynamics Diagnosis | `power-dynamics-diagnosis.md` | Map and understand formal and informal power structures | +| Organizational Alignment Playbook | `organizational-alignment-playbook.md` | Multi-step process for building stakeholder alignment | +| Stakeholder Influence Map | `templates/stakeholder-influence-map.md` | Output template for mapping stakeholder positions and strategies | +| Resistance Management Plan | `templates/resistance-management-plan.md` | Output template for managing identified resistance | +| Coalition Building Plan | `templates/coalition-building-plan.md` | Output template for designing and maintaining coalitions | +| Commands | `../commands/org-politics-commands.md` | `/stakeholders`, `/power-map`, `/resistance`, `/coalition` | diff --git a/plugins/foreman/content/org-politics/organizational-alignment-playbook.md b/plugins/foreman/content/org-politics/organizational-alignment-playbook.md new file mode 100644 index 0000000..a479b2f --- /dev/null +++ b/plugins/foreman/content/org-politics/organizational-alignment-playbook.md @@ -0,0 +1,151 @@ +--- +name: "organizational-alignment-playbook" +description: "Structures the complete process of building stakeholder alignment + for a strategic initiative. Chains stakeholder mapping, resistance diagnosis, + coalition design, influence strategy, communication planning, and + implementation into a rigorous sequence with checkpoints and a critical + decision point. Use when an entrepreneur must secure organizational support + for a significant change -- a pivot, a new hire, a budget reallocation, a + strategic partnership, or any initiative requiring multiple stakeholders to + say yes." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +trigger_diagnostics: + - stakeholder-resistance-diagnosis + - power-dynamics-diagnosis +steps: + - skill: "coalition-and-partnership-games" + purpose: "Map every stakeholder using the Power-Interest-Position framework" + output: "Stakeholder influence map with position, power, and interest per + stakeholder" + - purpose: "Diagnose root cause of resistance for each skeptic and blocker" + output: "Resistance diagnosis per stakeholder with root cause and engagement + recommendation" + kind: diagnostic + ref: stakeholder-resistance-diagnosis + - skill: "coalition-and-partnership-games" + purpose: "Design the coalition -- who to recruit, neutralize, or monitor" + output: "Coalition building plan with targets, sequencing, and defection risk" + - skill: "cialdini-influence" + purpose: "Design tailored influence approach per stakeholder" + output: "Influence strategy per stakeholder with principles, tactics, and + ethical guardrails" + - skill: "persuasion-and-influence" + purpose: "Design the communication plan -- what to say, when, to whom, through + which channel" + output: "Communication plan with messaging matrix, timing, and feedback loops" + - purpose: "Execute with accountability -- track engagements, monitor position + changes, adapt" + output: "Action plan with tracked items, milestones, and check-in protocol" + kind: implementation + ref: implementation-tracking +final_outputs: + - stakeholder-influence-map + - resistance-management-plan + - coalition-building-plan +estimated_duration: "3-6 hours across 1-3 weeks" +author: "Fatih Guner" +--- + +# Organizational Alignment Playbook + +Alignment is not agreement. Agreement is a moment; alignment is a sustained condition. The board that agrees to fund the initiative on Tuesday can misalign on execution by Friday if the political groundwork was not laid beneath the vote. This playbook produces the conditions under which "yes" holds -- where stakeholders not only approve an initiative but actively support its execution. + +--- + +## When to Use This Playbook + +- A strategic initiative requires approval from multiple stakeholders with different interests +- Resistance has emerged and the founder must build sufficient support to overcome it +- A pivot, reorganization, or major investment needs coalition support before announcement +- Enterprise sales require navigating a buying committee with champions, influencers, and blockers + +## Prerequisites + +- A defined initiative stated in concrete terms +- An initial list of stakeholders who can influence the outcome +- Willingness to adapt the initiative based on stakeholder input +- Access to the stakeholders, directly or through intermediaries + +--- + +## The Sequence + +### Step 1: Stakeholder Mapping + +Map every relevant stakeholder using the Power-Interest-Position framework. For each, assess power (high/medium/low), interest (high/medium/low), and position (champion/supporter/neutral/skeptic/blocker). Do not rely on assumptions. If uncertain about a position, mark it unknown and schedule a conversation. + +**Checkpoint:** The map includes at least one entry in each position category. If everyone is a champion, the map is wrong. + +### Step 2: Resistance Diagnosis + +For each skeptic and blocker, run stakeholder-resistance-diagnosis. Determine root cause: rational objection, territorial defense, fear of change, loss of power, information gap, values conflict, or proxy resistance. Invest particular attention in high-power blockers -- they must be converted, neutralized, or accommodated. + +**Checkpoint:** Each skeptic and blocker has a diagnosed root cause. "I don't know why they resist" means the triage is incomplete. + +--- + +### Decision Point: Redesign or Push Through? + +**Push through** if resistance stems from information gaps, fear of change, or territorial defense. The initiative's logic is sound; the political environment needs cultivation. + +**Redesign** if multiple credible stakeholders raise rational objections, or if values conflicts reflect genuine organizational priorities. Forcing an initiative through fundamental resistance produces pyrrhic victories. + +**Abandon** if resistance reveals flawed assumptions, or if the political capital required exceeds the initiative's value. + +--- + +### Step 3: Coalition Design + +Using coalition game theory, design the support structure. Identify the **inner circle** (active champions recruited first), **recruitment targets** (neutrals and soft skeptics who can be moved), **neutralization targets** (blockers whose opposition can be contained), and **monitoring targets** (low-power stakeholders to watch). + +**Checkpoint:** The assembled coalition has sufficient power to carry the initiative. If the arithmetic fails, revise the strategy. + +### Step 4: Influence Strategy + +Design a tailored approach per stakeholder using Cialdini's principles matched to resistance type. Rational objectors respond to Authority and Social Proof. Territorial defenders respond to Unity and Reciprocity. Fear-driven resisters respond to Social Proof and Commitment. Each strategy must be specific and named. + +**Checkpoint:** Every high-priority stakeholder has a concrete influence approach, not a generic aspiration. + +### Step 5: Communication Plan + +Design messaging and sequencing. Champions hear first (to prepare advocacy). Neutrals hear second (as momentum builds). Skeptics hear third (when the coalition is visible). Blockers hear last (when the landscape has shifted). After each communication, capture response and update the map. + +**Checkpoint:** Each high-priority engagement has a specific date and channel. + +### Step 6: Implementation + +Execute with tracking. Register each engagement as a tracked item. Record position changes after conversations. Monitor for coalition defection. Adjust strategy as new information emerges. + +**Checkpoint:** Positions are moving in the intended direction. Three consecutive engagements without movement signals a stall. + +--- + +## Final Deliverables + +| Output | Template | Audience | +|--------|----------|----------| +| Stakeholder Influence Map | `stakeholder-influence-map` | Self | +| Resistance Management Plan | `resistance-management-plan` | Self | +| Coalition Building Plan | `coalition-building-plan` | Self | + +## Common Pitfalls + +1. **Mapping once, never updating.** Positions shift after every interaction. The map is a living document. +2. **Treating alignment as a presentation problem.** Better slides do not build coalitions. Relationship and mutual interest do. +3. **Ignoring the informal network.** Formal stakeholders are obvious. Informal influencers determine outcomes. +4. **Pushing through resistance that signals a flawed initiative.** The most dangerous political success is winning approval for a bad idea. +5. **Building a coalition without maintaining it.** Supporters taken for granted after committing will not support the next initiative. + +## Adaptation Notes + +- **Validation stage:** Small stakeholder maps (cofounders, advisors, first investors) but intensely personal dynamics. +- **Growth stage:** Expanded universe including board, department leaders, and external partners. Communication plans must account for organizational information flow. +- **Scale stage:** Alignment becomes institutional. Outputs feed governance structures and change management programmes. +- **Solo mode:** Stakeholders are external (clients, partners, vendors). Coalition building becomes alliance building across independent parties. diff --git a/plugins/foreman/content/org-politics/power-dynamics-diagnosis.md b/plugins/foreman/content/org-politics/power-dynamics-diagnosis.md new file mode 100644 index 0000000..f7dc2a6 --- /dev/null +++ b/plugins/foreman/content/org-politics/power-dynamics-diagnosis.md @@ -0,0 +1,121 @@ +--- +name: "power-dynamics-diagnosis" +description: "Maps and diagnoses organizational power structures by distinguishing between formal authority mismatches, shadow influence networks, gatekeeper bottlenecks, power vacuums, competing power centers, and information-as-power dynamics. Routes to appropriate influence, coalition, and negotiation strategies. Use when the entrepreneur suspects that the real decision-making structure differs from the org chart, when hidden influences are shaping outcomes, or when political maneuvering is producing unexpected results." +entry_symptoms: + - "I don't know who really makes decisions" + - "The org chart doesn't match reality" + - "Hidden influences are shaping outcomes" + - "I'm being outmaneuvered" + - "Decisions keep getting reversed after meetings" + - "Someone I didn't expect killed the deal" + - "I can't figure out who to talk to" +possible_diagnoses: + - formal-authority-mismatch + - shadow-influence-network + - gatekeeper-bottleneck + - power-vacuum + - competing-power-centers + - information-as-power +routes_to_skills: + - coalition-and-partnership-games + - cialdini-influence + - trust-equation + - persuasion-and-influence + - managing-up + - strategic-thinking-and-alignment + - systems-thinking +routes_to_templates: + - stakeholder-influence-map + - resistance-management-plan + - coalition-building-plan +author: "Fatih Guner" +--- + +# Power Dynamics Diagnosis + +## Entry Symptoms + +The entrepreneur senses a disconnect between the visible and the real. "I pitched to the VP but the decision was made by someone I never met." "Decisions we made in the meeting were reversed the next day." "I keep being told to talk to different people and nothing moves." "Someone is pulling strings and I cannot see who." Power in organizations flows through channels that the org chart does not depict. Founders who navigate by title alone will miss the informal networks, personal loyalties, and information asymmetries that determine outcomes. + +## Triage Questions + +### Q1: Is this about FORMAL power (authority, titles, budget control) or INFORMAL power (influence, relationships, information access)? + +- **Formal** -- the question is about who holds decision authority, budget sign-off, or veto rights. The confusion is structural: reporting lines are unclear, authority is ambiguous, or multiple people claim the same decision rights. Proceed to Q4. +- **Informal** -- the question is about who influences decisions behind the scenes, regardless of title. The org chart is clear; the power flow is not. Proceed to Q2. +- **Both** -- formal authority exists but is overridden by informal influence. The person with the title defers to someone without it. Proceed to Q2 and Q4 simultaneously. + +### Q2: Are decisions made in meetings or outside them? + +- **In meetings** -- decisions are made where you can observe them. The power structure is visible even if complex. Focus on who speaks, who is deferred to, and whose objections carry weight. Likely diagnosis: **formal-authority-mismatch** or **competing-power-centers**. +- **Outside meetings** -- meetings ratify decisions already made in hallway conversations, private dinners, or pre-meetings. The real power operates in spaces you may not be invited to. Likely diagnosis: **shadow-influence-network**. +- **Decisions reverse after meetings** -- agreement is reached in the room, then overturned afterward. Someone with power was either absent or silent during the meeting and exercised influence later. Likely diagnosis: **shadow-influence-network** or **gatekeeper-bottleneck**. + +### Q3: Who does the decision-maker listen to most? + +- **A specific trusted advisor or confidant** -- the decision-maker delegates cognitive authority to a single person. That person's opinion effectively determines the outcome. Likely diagnosis: **shadow-influence-network** with a single node of concentrated informal power. +- **The last person who spoke to them** -- the decision-maker is susceptible to recency, and multiple influencers compete for the final word. Likely diagnosis: **competing-power-centers** where influence is unstable. +- **Data and evidence** -- the decision-maker is genuinely analytical. Influence depends not on relationships but on the quality and control of information. Likely diagnosis: **information-as-power** -- whoever controls the data controls the decision. +- **No one -- they avoid deciding** -- the decision-maker does not listen because they do not decide. Authority exists on paper but is not exercised. Likely diagnosis: **power-vacuum**. + +### Q4: Is there a gatekeeper controlling access to the decision-maker? + +- **Yes -- a specific person filters access, information, or requests** -- the gatekeeper shapes decisions by controlling what the decision-maker sees, hears, and from whom. Likely diagnosis: **gatekeeper-bottleneck**. The gatekeeper's interests may or may not align with yours. +- **No -- access is open but influence is unequal** -- anyone can reach the decision-maker, but some voices carry more weight. Proceed to Q3 to determine why. +- **The entrepreneur themselves is being gatekept** -- information or access that should flow to the entrepreneur is being filtered by a direct report, partner, or intermediary. The power dynamic is operating against the entrepreneur, not just around them. + +### Q5: Has the power structure recently shifted (new person, departure, reorg)? + +- **Yes -- recent change** -- power structures are most visible and most volatile during transitions. A new executive changes the influence map. A departure creates a vacuum. A reorg reshuffles formal authority without immediately resettling informal networks. Likely diagnosis: **power-vacuum** if authority has not settled, or **competing-power-centers** if multiple people are vying for the vacated influence. +- **No -- stable for months or years** -- the power structure is entrenched. Mapping it requires observation over time rather than analysis of recent events. Entrenched structures are harder to change but easier to predict. +- **Gradual erosion** -- no single event, but a slow shift in who holds influence. A board member's engagement has waned. A department head's political capital has been spent. Gradual erosion is the hardest to detect and the most dangerous to ignore. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Formal authority mismatch** | Decisions attributed to one person but actually made by another; titles do not predict who controls outcomes; reporting lines are misleading | Q1 shows formal confusion + Q2 shows decisions made in unexpected places | +| **Shadow influence network** | Decisions reverse after meetings; a non-obvious person's opinion consistently predicts outcomes; informal pre-meetings shape agendas | Q2 shows outside-meeting decisions + Q3 identifies a specific trusted advisor | +| **Gatekeeper bottleneck** | Access to the decision-maker is controlled; information is filtered before reaching leadership; one person's approval is a prerequisite for progress | Q4 confirms gatekeeper + Q3 shows decision-maker relies on filtered input | +| **Power vacuum** | Decisions are delayed indefinitely; no one claims authority; escalation produces no resolution; competing proposals persist without adjudication | Q3 shows avoidance of decisions + Q5 reveals recent departure or structural ambiguity | +| **Competing power centers** | Two or more people issue conflicting direction; teams receive contradictory instructions; political alignment with one center alienates another | Q1 shows both formal and informal confusion + Q3 shows decision-maker influenced by the last speaker | +| **Information as power** | One person or group controls data access; decisions are shaped by what information is presented; alternative analyses are suppressed or discredited | Q3 shows data-driven decision-maker + Q4 reveals information is gatekept | + +## Routing + +**Formal authority mismatch:** +1. Apply `managing-up` -- understand the actual authority structure and adapt engagement strategy accordingly +2. Apply `strategic-thinking-and-alignment` -- align your initiative with the interests of the actual decision-maker, not the nominal one +3. Output with `stakeholder-influence-map` -- redraw the power map with formal and actual authority distinguished + +**Shadow influence network:** +1. Apply `trust-equation` -- assess and build trust with the shadow influencer, not just the formal decision-maker +2. Apply `cialdini-influence` -- Liking and Unity principles to build rapport with the influencer; Authority principle to establish credibility +3. Output with `stakeholder-influence-map` -- map the shadow network and design dual engagement (formal decision-maker + shadow influencer) + +**Gatekeeper bottleneck:** +1. Apply `cialdini-influence` -- Reciprocity (provide value to the gatekeeper) and Liking (build genuine rapport) to gain access +2. Apply `trust-equation` -- the gatekeeper's trust is the prerequisite to reaching the decision-maker +3. Output with `resistance-management-plan` -- if the gatekeeper is blocking, treat them as a stakeholder with their own interests + +**Power vacuum:** +1. Apply `strategic-thinking-and-alignment` -- determine whether to fill the vacuum yourself, advocate for someone to fill it, or restructure to eliminate the need +2. Apply `coalition-and-partnership-games` -- in a vacuum, coalitions determine outcomes; build one before someone else does +3. Output with `coalition-building-plan` -- design the coalition that fills the authority gap for your initiative + +**Competing power centers:** +1. Apply `thomas-kilmann-conflict` -- determine the appropriate conflict mode for navigating between competing authorities +2. Apply `coalition-and-partnership-games` -- assess which power center to align with based on Shapley Value logic (whose support contributes most to your initiative's success) +3. Output with `stakeholder-influence-map` -- map both power centers, their supporters, and the contested territory + +**Information as power:** +1. Apply `systems-thinking` -- map the information flows and identify where data is being controlled or filtered +2. Apply `cialdini-influence` -- Authority principle to establish your own information credibility; Social Proof to introduce independent data sources +3. Output with `stakeholder-influence-map` -- map information flows alongside power flows + +## Red Flags + +- **You are consistently surprised by decisions.** If outcomes repeatedly differ from what the visible process predicted, the real power structure is invisible to you. Stop executing and start mapping. +- **A single non-executive's opinion predicts every decision.** Shadow influence concentrated in one person creates a single point of failure and a single point of necessary engagement. +- **Your champion says "I'll handle it" but nothing happens.** Your champion may lack the power they claim, or they may be encountering resistance they are not disclosing. Verify independently. +- **Everyone defers to "the process" but no one owns the process.** Procedural deference without clear ownership is a power vacuum disguised as governance. diff --git a/plugins/foreman/content/org-politics/stakeholder-resistance-diagnosis.md b/plugins/foreman/content/org-politics/stakeholder-resistance-diagnosis.md new file mode 100644 index 0000000..cf7dd1d --- /dev/null +++ b/plugins/foreman/content/org-politics/stakeholder-resistance-diagnosis.md @@ -0,0 +1,126 @@ +--- +name: "stakeholder-resistance-diagnosis" +description: "Diagnoses the root cause of stakeholder resistance to an initiative by distinguishing between rational objection, territorial defense, fear of change, loss of power, information gaps, values conflict, and proxy resistance. Routes to appropriate influence, conflict resolution, and coalition-building strategies. Use when a key stakeholder is blocking progress, when buy-in efforts are failing, or when opposition is emerging in forms both overt and covert." +entry_symptoms: + - "My board won't approve this" + - "The team is resisting the change" + - "Key stakeholder is blocking progress" + - "I can't get buy-in" + - "There's a silent opposition" + - "Someone is working against this behind the scenes" + - "My cofounder disagrees with the direction" +possible_diagnoses: + - rational-objection + - territorial-defense + - fear-of-change + - loss-of-power + - information-gap + - values-conflict + - proxy-resistance +routes_to_skills: + - thomas-kilmann-conflict + - cialdini-influence + - coalition-and-partnership-games + - trust-equation + - persuasion-and-influence + - win-win-negotiation + - resolving-people-conflict +routes_to_templates: + - stakeholder-influence-map + - resistance-management-plan + - coalition-building-plan +author: "Fatih Guner" +--- + +# Stakeholder Resistance Diagnosis + +## Entry Symptoms + +The entrepreneur arrives frustrated. "My board won't approve this." "The team is pushing back on everything." "One person is blocking the entire initiative and I don't know why." "I thought we had alignment, but nothing is moving." Resistance takes many forms -- some loud and direct, others quiet and corrosive. The founder who cannot distinguish a valid objection from a territorial reflex will either capitulate when they should push or bulldoze when they should listen. + +## Triage Questions + +### Q1: Is the resistance coming from individuals or the organization's structure? + +- **Specific individuals** -- one or a few named people are the source of opposition. Their removal or conversion would resolve the issue. Proceed to Q2. +- **Structural** -- the resistance is diffuse, emerging from processes, culture, or organizational design rather than specific actors. Multiple people resist for similar reasons. Likely diagnosis: **fear-of-change** or **organizational inertia**. Proceed to Q3 to determine whether the structural resistance has rational underpinnings. + +### Q2: Is the resistance public (stated objections) or covert (passive-aggressive, delays, silence)? + +- **Public** -- the resister states objections openly, raises concerns in meetings, argues against the initiative visibly. This is the healthier form. Proceed to Q3 to assess the substance of their objection. +- **Covert** -- the resister agrees in meetings but fails to act, delays deliverables, withholds information, or lobbies against the initiative in private conversations. Likely diagnosis: **territorial-defense** or **loss-of-power**. Proceed to Q4 to determine whether the covert resistance stems from genuine concern they are afraid to voice or from political positioning. +- **Mixed** -- some concerns are stated publicly; the real objection remains hidden. The public objection serves as a socially acceptable proxy for the actual resistance. Likely diagnosis: **proxy-resistance**. Proceed to Q5. + +### Q3: Is the resistance based on genuine concerns (rational) or political positioning (territorial)? + +- **Genuine concerns** -- the resister has data, experience, or logic supporting their objection. If you set aside ego, their argument has merit. Likely diagnosis: **rational-objection**. This is not a political problem; it is an intellectual disagreement that deserves engagement on substance. +- **Political positioning** -- the resister's objection does not withstand scrutiny, but they maintain it because the initiative threatens their territory, budget, headcount, or influence. Likely diagnosis: **territorial-defense** or **loss-of-power**. +- **Information gap** -- the resister's objection is based on incomplete or outdated information. They are drawing reasonable conclusions from an incomplete picture. Likely diagnosis: **information-gap**. + +### Q4: Does the resister have veto power or just influence? + +- **Veto power** -- they can unilaterally block the initiative through formal authority (board vote, budget control, contract approval). Their resistance is existential to the initiative. Engagement is mandatory; workarounds are unlikely. +- **Influence without veto** -- they cannot block alone but can slow progress, degrade enthusiasm, or recruit other resisters. Their resistance is damaging but not fatal. The question becomes whether to engage directly or build a coalition that makes their resistance irrelevant. +- **Neither** -- they have neither veto power nor significant influence. Their resistance is noise. The risk is overreacting and elevating a minor objection into a political event. + +### Q5: Have you engaged the resister directly or are you working around them? + +- **Engaged directly** -- you have had a candid conversation and understand their stated objection. Proceed to the Diagnosis Map to match the root cause. +- **Working around them** -- you have avoided direct engagement, preferring to build support elsewhere or escalate above them. This strategy sometimes works but often backfires -- the resister interprets the workaround as confirmation that their concerns were dismissed, entrenching their opposition. +- **Attempted engagement, met with deflection** -- the resister avoids substantive conversation, responds with vague agreement that does not translate to action, or refuses to articulate their objection. Likely diagnosis: **proxy-resistance** or **loss-of-power** -- they are protecting something they cannot publicly admit to protecting. + +## Diagnosis Map + +| Diagnosis | Key Signals | Confirmation Path | +|-----------|------------|-------------------| +| **Rational objection** | Specific, evidence-based concerns; objection survives when you steelman it; resister is open to dialogue | Q3 confirms genuine concerns + Q5 shows direct engagement produces substantive debate | +| **Territorial defense** | Resistance maps to the resister's budget, headcount, or domain; objection is strongest where the initiative overlaps with their territory | Q3 shows political positioning + Q2 reveals covert behaviour in areas of territorial overlap | +| **Fear of change** | Resistance is diffuse, non-specific ("this isn't the right time"), correlated with the magnitude of change rather than its content | Q1 shows structural resistance + Q3 reveals concerns dissolve under scrutiny but reform as new objections | +| **Loss of power** | The initiative would reduce the resister's authority, visibility, or control; resistance intensifies as the initiative gains momentum | Q3 shows political positioning + Q4 reveals the resister is using whatever power they have to slow or block | +| **Information gap** | Resistance based on misunderstanding of the initiative's scope, impact, or rationale; new information genuinely shifts the resister's position | Q3 shows apparent concerns + information correction produces measurable attitude change | +| **Values conflict** | Deep disagreement on direction, priorities, or principles that cannot be resolved by information or compromise; both sides are internally consistent | Q3 shows genuine concerns + Q5 reveals engaged debate that reaches impasse on fundamental premises | +| **Proxy resistance** | Stated objection does not match the intensity of resistance; the resister appears to represent someone else's interests; objection shifts when addressed | Q2 shows mixed signals + Q5 reveals deflection or the stated objection changes shape repeatedly | + +## Routing + +**Rational objection:** +1. Apply `thomas-kilmann-conflict` -- use Collaborating mode to integrate the resister's valid concerns into a stronger initiative +2. Apply `win-win-negotiation` -- find the solution that addresses both your initiative's goals and their legitimate concerns +3. Output with `stakeholder-influence-map` -- update the resister's position from blocker to potential contributor + +**Territorial defense:** +1. Apply `cialdini-influence` -- Reciprocity (offer something that acknowledges their domain) and Unity (frame the initiative as expanding, not encroaching on, their territory) +2. Apply `coalition-and-partnership-games` -- assess whether including the resister in the initiative's governance structure stabilizes the coalition +3. Output with `resistance-management-plan` -- document the territorial concern and the engagement strategy + +**Fear of change:** +1. Apply `persuasion-and-influence` -- build the narrative that makes the change feel manageable and desirable +2. Apply `cialdini-influence` -- Social Proof (show that similar changes have succeeded elsewhere) and Commitment (secure small initial agreements that build momentum) +3. Output with `resistance-management-plan` -- design a phased engagement that reduces perceived risk + +**Loss of power:** +1. Apply `trust-equation` -- assess the relationship foundation before attempting influence +2. Apply `coalition-and-partnership-games` -- determine whether the resister can be given a meaningful role in the new structure that preserves their influence +3. Output with `stakeholder-influence-map` -- map the power shift and design an approach that addresses the real concern + +**Information gap:** +1. Apply `persuasion-and-influence` -- design the communication that closes the gap +2. Apply `trust-equation` -- ensure the information source is credible to the resister +3. Output with `stakeholder-influence-map` -- update and track position change after information delivery + +**Values conflict:** +1. Apply `thomas-kilmann-conflict` -- assess whether Collaborating mode can find a synthesis, or whether Compromising or Competing is necessary +2. Apply `resolving-people-conflict` -- facilitate the conversation that surfaces the values difference explicitly +3. Decision point: if the values conflict is irreconcilable, the initiative may need to be redesigned, or the organizational relationship may need to be restructured + +**Proxy resistance:** +1. Apply `trust-equation` -- build enough trust with the proxy to surface the real principal +2. Apply `coalition-and-partnership-games` -- map the hidden coalition structure to identify who is actually driving the resistance +3. Output with `stakeholder-influence-map` -- map both the proxy and the principal, then design engagement for the principal + +## Red Flags + +- **The resister's objection changes every time you address it.** This is a hallmark of proxy resistance or loss-of-power masquerading as rational concern. The real objection is not being stated. +- **Resistance intensifies after a private meeting with another stakeholder.** Someone is coordinating opposition. Map the network before responding. +- **You are told "everyone feels this way" but cannot identify specific people.** Manufactured consensus is a political tactic. Verify independently. +- **The resistance is framed as concern for the company but maps precisely to the resister's personal interests.** This is territorial defense wrapped in organizational language. Name it -- privately, carefully, but clearly. diff --git a/plugins/foreman/content/org-politics/templates/_schema/org-politics-template.yaml b/plugins/foreman/content/org-politics/templates/_schema/org-politics-template.yaml new file mode 100644 index 0000000..c809776 --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/_schema/org-politics-template.yaml @@ -0,0 +1,78 @@ +# Org-Politics Template Schema +# Defines the required structure for all templates in .claude/org-politics/templates/ +# Author: Fatih Guner + +--- + +# FRONTMATTER (YAML between --- delimiters at top of every template file) +frontmatter: + name: + type: string + required: true + description: "Kebab-case identifier matching the filename without extension" + + description: + type: string + required: true + description: "What this template produces and when to use it. Be specific -- a good description lets the system select the right template without human intervention." + + audience: + type: string + required: true + allowed_values: ["self"] + description: "Always 'self'. Internal strategy documents -- never shared with the stakeholders they describe." + + political_context: + type: string + required: true + allowed_values: + - stakeholder-mapping + - resistance-management + - coalition-building + - communication-strategy + - negotiation-prep + - power-analysis + description: "The political pattern this template addresses." + + applicable_skills: + type: list + required: true + description: "Skills from the Foreman ecosystem that feed into or are invoked by this template." + + applicable_diagnostics: + type: list + required: false + description: "Diagnostics that produce data consumed by this template." + + feeds_into_playbooks: + type: list + required: false + description: "Playbooks that use this template as an output artifact." + + author: + type: string + required: true + description: "Template author." + +# BODY STRUCTURE (Markdown below the frontmatter) +# Sections vary by political_context, but every template MUST include the following: +body: + required_sections: + - name: "Situation Assessment" + description: "One-paragraph summary of the initiative, decision, or change being navigated." + + - name: "Stakeholder Table" + description: "Structured table with at minimum: Stakeholder, Role/Position, and one strategy-relevant attribute." + + - name: "Strategy" + description: "The core strategic logic -- what to do, in what order, and why." + + - name: "Action Items" + description: "Prioritised, time-bound actions with owners." + + - name: "Risk Assessment" + description: "What can go wrong politically, how likely it is, and what to do about it." + + - name: "Ethical Check" + required: true + description: "Mandatory, no exceptions. 'Does this strategy pass the transparency test? Would you be comfortable if every stakeholder saw this document?' If no, revise the strategy -- not the ethics." diff --git a/plugins/foreman/content/org-politics/templates/coalition-building-plan.md b/plugins/foreman/content/org-politics/templates/coalition-building-plan.md new file mode 100644 index 0000000..9bd3e62 --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/coalition-building-plan.md @@ -0,0 +1,110 @@ +--- +name: "coalition-building-plan" +description: "Produces a structured plan for building, sequencing, and maintaining a coalition of supporters for a strategic initiative. Includes target identification, per-target value proposition, recruitment sequencing, commitment mechanisms, defection risk assessment, and maintenance strategy. Applies coalition game theory to ensure stability. Internal strategy document -- never shared with targets before recruitment." +audience: "self" +applicable_skills: + - coalition-and-partnership-games + - cialdini-influence + - trust-equation + - persuasion-and-influence + - win-win-negotiation +format: "plan" +author: "Fatih Guner" +--- + +# Coalition Building Plan + + + +**Initiative:** [Name] | **Date:** [Date] | **Decision date:** [Date] | **Architect:** [Name] + +**Objective:** [What the coalition must achieve] + +**Minimum viable coalition:** [Smallest group with sufficient power. Name them.] + +--- + +## Coalition Target List + +| # | Name / Role | Current Position | Power | Value to Coalition | Difficulty | Sequence | +|---|-------------|-----------------|-------|-------------------|------------|----------| +| 1 | [Name, Title] | [Champion/Supporter/Neutral/Skeptic] | [H/M/L] | [What their support adds] | [Easy/Moderate/Hard] | [1st] | +| 2 | [Name, Title] | [Position] | [H/M/L] | [Value] | [Difficulty] | [2nd] | +| 3 | [Name, Title] | [Position] | [H/M/L] | [Value] | [Difficulty] | [3rd] | + +--- + +## Value Proposition per Target + +_Each target needs a reason to join that serves their interests, not just yours._ + +### Target 1: [Name] + +- **Their interests:** [Career, department growth, risk reduction, recognition] +- **Benefit / Ask / Offer:** [How initiative serves them] | [What you need] | [What you give] + +### Target 2: [Name] + +- **Their interests:** [What they care about] +- **Benefit / Ask / Offer:** [Exchange summary] + +### Target 3: [Name] + +- **Their interests:** [What they care about] +- **Benefit / Ask / Offer:** [Exchange summary] + +--- + +## Recruitment Sequencing + +| Phase | Order | Target | Why This Sequence | Signal to Others | +|-------|-------|--------|-------------------|-----------------| +| **Foundation** | 1st | [Name] | [Why first -- credibility, influence chain] | [What commitment tells others] | +| | 2nd | [Name] | [Why second] | [Signal] | +| | 3rd | [Name] | [Why third] | [Signal] | +| **Expansion** | 4th+ | [Name] | [Leverage from Phase 1 -- Social Proof, momentum] | [Signal] | + +**Phase 1 milestone:** [Condition to proceed -- e.g., "3 confirmed with 40% voting power"] + +--- + +## Commitment Mechanisms + +_Ladder from weakest to strongest: Verbal agreement > Written endorsement > Public declaration > Resource commitment (budget/staff). Each level is harder to reverse._ + +| Target | Current Level | Next Level | Action to Advance | +|--------|--------------|------------|-------------------| +| [Name] | [Verbal/Written/Public/Resource] | [Next] | [Specific action] | +| [Name] | [Level] | [Next] | [Action] | + +--- + +## Defection Risk Assessment + +| Supporter | Risk | Trigger Scenario | Warning Signs | Prevention | +|-----------|------|-----------------|---------------|------------| +| [Name] | [Low/Med/High] | [What causes withdrawal] | [Behaviours preceding defection] | [How to keep them] | +| [Name] | [Risk] | [Trigger] | [Signs] | [Prevention] | + +**Cascade risk:** [If one defects, who follows? Identify domino chain and firebreaks.] + +--- + +## Coalition Maintenance + +| Audience | Channel | Frequency | Content | +|----------|---------|-----------|---------| +| Inner circle | One-on-one | Weekly | Progress, challenges, input requests | +| Broader coalition | Group update | Biweekly | Milestones, recognition, next phase | + +**Rules:** Celebrate wins publicly. Share credit before claiming it. Honour recruitment promises. Re-assess value propositions as interests evolve. + +--- + +## Coalition Arithmetic + +- **Decision threshold:** [Votes or influence required] +- **Coalition power:** [Committed] | **Opposition:** [Committed] | **Undecided:** [In play] +- **Best case:** [Full coalition outcome] | **One defection:** [Still sufficient?] | **Opposition grows:** [Still sufficient?] diff --git a/plugins/foreman/content/org-politics/templates/communication-strategy-map.md b/plugins/foreman/content/org-politics/templates/communication-strategy-map.md new file mode 100644 index 0000000..bbd83b7 --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/communication-strategy-map.md @@ -0,0 +1,110 @@ +--- +name: "communication-strategy-map" +description: "Produces a communication strategy for navigating political situations -- what to say, to whom, when, through which channel, and what NOT to say. Use when an initiative requires coordinated messaging across multiple stakeholders with different interests, concerns, and influence levels. This is an internal strategy document -- never shared with the stakeholders it describes." +audience: "self" +political_context: "communication-strategy" +applicable_skills: + - storytelling-for-leaders + - cialdini-influence + - persuasion-and-influence + - writing-with-purpose + - leadership-voice-and-presence +applicable_diagnostics: + - stakeholder-resistance-diagnosis + - power-dynamics-diagnosis +feeds_into_playbooks: + - organizational-alignment-playbook # Step 5 +format: "map" +author: "Fatih Guner" +--- + +# Communication Strategy Map + + + +**Initiative:** [Name] | **Date:** [Date] | **Decision date:** [Date] | **Next review:** [Date] + +--- + +## Initiative Summary + +_One paragraph describing what you are trying to achieve and why it matters. Every message below is a translation of this paragraph for a specific audience._ + +[Describe the initiative, the desired outcome, and the organisational context. Be precise about what success looks like.] + +--- + +## Stakeholder Communication Matrix + +| Stakeholder | Key Message | Channel | Timing | Messenger | Tone | What NOT to Say | +|-------------|-------------|---------|--------|-----------|------|-----------------| +| [Name, Role] | [Core message tailored to their interests] | [1:1 / Email / Slack / Board deck / All-hands] | [Date or sequence position] | [You / Ally / Their peer] | [Direct / Consultative / Deferential] | [Words, topics, or framings to avoid] | +| [Name, Role] | [Message] | [Channel] | [Timing] | [Messenger] | [Tone] | [Avoid] | +| [Name, Role] | [Message] | [Channel] | [Timing] | [Messenger] | [Tone] | [Avoid] | + +--- + +## Narrative Framing + +_The same initiative, told four ways. Each framing emphasises what that audience values most._ + +- **Investor Frame:** [How this creates or protects enterprise value. Speak in returns, milestones, and competitive positioning.] +- **Team Frame:** [How this affects their work and autonomy. Speak in clarity, purpose, and day-to-day changes.] +- **Customer Frame:** [How this improves the product or relationship. Speak in outcomes they care about.] +- **Partner Frame:** [How this affects the partnership. Speak in mutual benefit and shared goals.] + +--- + +## Sequencing + +_Who hears first, who hears last, and why the order matters._ + +| Order | Stakeholder(s) | Rationale | +|-------|---------------|-----------| +| 1st | [Name(s)] | [Early supporters validate the message -- buy-in gives proof of momentum] | +| 2nd | [Name(s)] | [Key influencers who shape opinion -- arm them with the narrative before it spreads informally] | +| 3rd | [Name(s)] | [Skeptics hear after momentum exists -- resistance is harder to sustain when the tide is moving] | +| 4th | [Name(s)] | [Broad communication -- only after critical mass is aligned] | +| Last | [Name(s)] | [Stakeholders whose reaction you can absorb after alignment is secured] | + +**Sequencing risk:** [What happens if the sequence breaks? What is the contingency?] + +--- + +## Objection Preparation + +| # | Anticipated Objection | Source Stakeholder(s) | Prepared Response | Supporting Evidence | +|---|----------------------|----------------------|-------------------|-------------------| +| 1 | [Specific objection in their words] | [Who will raise it] | [Response addressing underlying concern, not just surface objection] | [Data, precedent, or third-party validation] | +| 2 | [Objection] | [Source] | [Response] | [Evidence] | +| 3 | [Objection] | [Source] | [Response] | [Evidence] | +| 4 | [Objection] | [Source] | [Response] | [Evidence] | +| 5 | [Objection] | [Source] | [Response] | [Evidence] | + +--- + +## Feedback Channels + +_Giving stakeholders a voice prevents silent resistance. If people cannot push back openly, they push back covertly._ + +| Stakeholder Group | Feedback Channel | Frequency | Who Monitors | Escalation Path | +|-------------------|-----------------|-----------|-------------|----------------| +| [Group] | [1:1 check-ins / Anonymous survey / Open forum / Slack channel] | [Weekly / After each milestone] | [Name] | [How concerns reach the decision-maker] | +| [Group] | [Channel] | [Frequency] | [Monitor] | [Escalation] | + +--- + +## Ethical Check + +**Transparency test:** Would you be comfortable if every stakeholder saw every other stakeholder's message? + +- [ ] Every message is truthful -- different emphasis is acceptable, different facts are not +- [ ] No stakeholder is told something that contradicts what another is told +- [ ] Sequencing serves strategic clarity, not information manipulation +- [ ] Feedback channels are genuine, not performative +- [ ] The "What NOT to Say" column reflects sensitivity, not concealment + +**If any box is unchecked, revise the strategy before executing.** diff --git a/plugins/foreman/content/org-politics/templates/negotiation-position-map.md b/plugins/foreman/content/org-politics/templates/negotiation-position-map.md new file mode 100644 index 0000000..7a0513f --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/negotiation-position-map.md @@ -0,0 +1,110 @@ +--- +name: "negotiation-position-map" +description: "Produces a multi-party negotiation preparation document for situations where more than two parties are involved -- board negotiations, partnerships with multiple stakeholders, M&A with multiple parties. Maps each party's positions, interests, BATNA, power, and inter-party relationships. This is an internal strategy document -- never shared with the parties it describes." +audience: "self" +political_context: "negotiation-prep" +applicable_skills: + - win-win-negotiation + - negotiation-game-theory + - coalition-and-partnership-games + - competitive-negotiation + - cooperative-negotiation + - information-asymmetry +applicable_diagnostics: + - stakeholder-resistance-diagnosis + - power-dynamics-diagnosis +feeds_into_playbooks: + - negotiation-playbook + - partnership-playbook + - acquisition-evaluation-playbook +format: "map" +author: "Fatih Guner" +--- + +# Negotiation Position Map + + + +**Negotiation:** [Name / Deal] | **Date:** [Date] | **Target close:** [Date] | **Next session:** [Date] + +--- + +## Negotiation Context + +[What is being decided, what triggered it, how many parties, the timeline, and relevant history.] + +--- + +## Party Profiles + +| Attribute | Party 1: [You] | Party 2: [Name] | Party 3: [Name] | +|-----------|----------------|-----------------|-----------------| +| **Stated position** | [What you are publicly asking for] | [What they ask for] | [What they ask for] | +| **Underlying interests** | [What you actually need] | [Inferred from behaviour and context] | [Inferred] | +| **BATNA** | [Your best alternative if this fails] | [Their best alternative] | [Their alternative] | +| **Reservation point** | [Worst deal you accept] | [Estimated floor] | [Estimated floor] | +| **Power sources** | [Information, alternatives, time, resources] | [H/M/L -- and source] | [H/M/L -- and source] | +| **Relationships** | -- | [Allied/competitive/neutral with whom] | [Allied/competitive/neutral] | +| **Pressure points** | [Your constraints] | [Time, stakeholders, finances] | [Pressures] | + +--- + +## Alliance Map + +| Potential Alliance | Basis | Stability | Risk to You | +|-------------------|-------|-----------|-------------| +| [Party 2 + Party 3] | [Shared interest in X] | [Strong / Fragile] | [High -- can pressure you / Low -- does not change your position] | +| [You + Party 2] | [Shared interest in Y] | [Assessment] | [N/A -- target alliance] | +| [Party 3 + Party 4 against you] | [Both oppose Z] | [Assessment] | [Cost and prevention strategy] | + +**Swing party:** [Which party's alignment is most uncertain and most consequential?] + +--- + +## Concession Architecture +| Trade | You Give | Cost to You | Value to Them | You Get | Cost to Them | Value to You | +|-------|---------|-------------|---------------|---------|-------------|-------------| +| [Party 2 trade] | [Specific concession] | [L/M/H] | [L/M/H] | [Specific gain] | [L/M/H] | [L/M/H] | +| [Party 3 trade] | [Concession] | [Cost] | [Value] | [Gain] | [Cost] | [Value] | + +**High-value trades:** [2-3 trades where cost-value asymmetry is largest -- the deal-makers.] + +--- + +## Sequencing Strategy + +| Order | Engage With | Objective | Rationale | +|-------|-------------|-----------|-----------| +| 1st | [Party] | [Bilateral agreement on X] | [Easiest alignment -- creates momentum] | +| 2nd | [Party] | [Agreement on Y] | [Their agreement pressures remaining parties] | +| 3rd | [Party] | [Agreement on Z] | [Hardest alignment -- but momentum constrains their options] | +| Final | [All parties] | [Ratify full agreement] | [Formalise what bilateral rounds have shaped] | + +**Sequencing risk:** [What if a later party discovers early bilateral deals? How do you handle it?] + +--- + +## Red Lines and Win Conditions +| Party | Red Line | Consequence | Top Priority | Minimum Acceptable | +|-------|----------|-------------|-------------|-------------------| +| [You] | [Non-negotiable term] | [Walk away / Board rejects] | [Must achieve] | [Floor -- below this, BATNA preferable] | +| [Party 2] | [Their non-negotiable] | [They walk away] | [Their top priority] | [Their floor] | +| [Party 3] | [Their non-negotiable] | [Consequence] | [Their top priority] | [Their floor] | + +**ZOPA:** [Does a deal exist where every party gets at least their minimum? If no, which minimum is incompatible?] + +--- + +## Ethical Check +**Transparency test:** Would you be comfortable if every party saw this preparation document? + +- [ ] Party profiles are honest assessment, not caricature or wishful thinking +- [ ] Concession architecture seeks genuine mutual benefit, not exploitation of information asymmetry +- [ ] Sequencing serves efficiency, not divide-and-conquer manipulation +- [ ] Red lines are respected -- no plans to pressure past non-negotiables +- [ ] Win conditions are genuine -- seeking a deal where every party gains + +**If any box is unchecked, revise the strategy before entering the negotiation.** diff --git a/plugins/foreman/content/org-politics/templates/political-risk-assessment.md b/plugins/foreman/content/org-politics/templates/political-risk-assessment.md new file mode 100644 index 0000000..6be2741 --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/political-risk-assessment.md @@ -0,0 +1,117 @@ +--- +name: "political-risk-assessment" +description: "Produces a risk assessment specifically for organisational and + political risks -- not market or financial risks, but PEOPLE risks. Use when + an initiative faces potential human-driven derailment: departures, coalition + fractures, information leaks, revolts, or stakeholder withdrawal. This is an + internal strategy document -- never shared with the stakeholders it + describes." +audience: "self" +political_context: "resistance-management" +applicable_skills: + - scenario-planning + - black-swans + - thomas-kilmann-conflict +applicable_diagnostics: + - stakeholder-resistance-diagnosis + - power-dynamics-diagnosis +feeds_into_playbooks: + - organizational-alignment-playbook # After Step 2 +format: "register" +author: "Fatih Guner" +related_content: + - kind: template + ref: risk-assessment-brief +--- + +# Political Risk Assessment + + + +**Initiative:** [Name] | **Date:** [Date] | **Decision date:** [Date] | **Next review:** [Date] + +--- + +## Initiative Description + +_What decision or change is being assessed? Describe it in enough detail that each risk below can be evaluated against a concrete plan._ + +[Describe the initiative, stakeholders involved, timeline, and current political landscape.] + +--- + +## Political Risk Register + +| # | Risk | Source Stakeholder | Probability | Impact | Risk Score | Early Warning Signal | Mitigation Strategy | +|---|------|--------------------|-------------|--------|------------|---------------------|---------------------| +| 1 | **Key person departure** -- [Name] leaves before initiative completes | [Name, Role] | [H/M/L] | [H/M/L] | [Score] | [Disengagement, reduced communication] | [Knowledge transfer, retention conversation] | +| 2 | **Coalition fracture** -- supporting coalition splits over [issue] | [Names] | [H/M/L] | [H/M/L] | [Score] | [Side conversations, conditional language] | [Address fault line directly, find new common ground] | +| 3 | **Information leak** -- internal deliberation reaches [audience] | [Likely source] | [H/M/L] | [H/M/L] | [Score] | [Unexpected questions from outsiders] | [Limit distribution, prepare public narrative] | +| 4 | **Board revolt** -- board members collectively oppose | [Names] | [H/M/L] | [H/M/L] | [Score] | [Unusual side conversations, special session requests] | [Pre-meeting alignment, address concerns individually] | +| 5 | **Team mutiny** -- critical members resist or refuse to execute | [Team/Names] | [H/M/L] | [H/M/L] | [Score] | [Passive resistance, missed deadlines, attrition signals] | [Involve team in design, empower internal champions] | +| 6 | **Partner withdrawal** -- key partner disengages or defects | [Partner] | [H/M/L] | [H/M/L] | [Score] | [Delayed responses, exploring alternatives] | [Strengthen value proposition, develop backup] | +| 7 | **Public opposition** -- stakeholder takes objection public | [Name] | [H/M/L] | [H/M/L] | [Score] | [Escalating rhetoric, journalist contact] | [Private resolution attempt, prepare public response] | +| 8 | **Regulatory challenge** -- complaint triggers regulatory scrutiny | [Name/Entity] | [H/M/L] | [H/M/L] | [Score] | [Legal posturing, compliance inquiries] | [Proactive compliance review, legal preparation] | + +--- + +## Scenario Analysis + +### Worst Case: All Resisters Activate Simultaneously + +- **Trigger event:** [What could cause coordinated opposition -- leaked document, public failure, economic downturn] +- **Cascade:** [How one risk triggers others -- departure causes coalition fracture, which causes team mutiny] +- **Outcome:** [Initiative fails / Delayed by X months / Organisation sustains lasting damage] +- **Recovery path:** [What remains salvageable and how] + +### Most Likely: Partial Resistance + +- **Expected risks:** [Which 2-3 risks from the register are most likely to co-occur] +- **Expected timeline:** [When resistance peaks] +- **Outcome:** [Succeeds with modifications / Delayed but achievable / Requires significant compromise] + +### Best Case: Resistance Dissolves + +- **Dissolving factors:** [Early win, external validation, resistor departure, changed conditions] +- **Probability:** [Honest assessment -- best cases are usually the least likely] + +--- + +## Contingency Plans + +_For the top 3 risks -- what is Plan B if mitigation fails?_ + +| Risk | Mitigation (Plan A) | Contingency (Plan B) | Trigger for Switching | Owner | +|------|---------------------|---------------------|----------------------|-------| +| [Highest-scoring risk] | [Primary mitigation] | [What you do when Plan A fails] | [Specific signal that Plan A has failed] | [Name] | +| [Second-highest risk] | [Mitigation] | [Contingency] | [Trigger] | [Owner] | +| [Third-highest risk] | [Mitigation] | [Contingency] | [Trigger] | [Owner] | + +--- + +## Kill Triggers + +_At what point does political resistance indicate the initiative itself is wrong? Not every battle should be won -- sometimes resistance is wisdom._ + +| Signal | Threshold | Interpretation | Recommended Action | +|--------|-----------|---------------|-------------------| +| [High-power stakeholder opposition] | [e.g., 3+ board members] | [This broad opposition may reflect a genuine flaw, not mere politics] | [Pause and reassess the initiative itself] | +| [Team resistance level] | [e.g., >40% of affected team] | [When executors do not believe, political success becomes operational failure] | [Redesign with team input or abandon] | +| [External validation failure] | [Customers/market do not respond as predicted] | [Internal resistance may reflect external reality] | [Seek independent external assessment] | +| [Personal integrity threshold] | [Strategy requires tactics you would not describe publicly] | [If winning requires crossing ethical lines, the approach must change] | [Revise strategy or recommend abandonment] | + +--- + +## Ethical Check + +**Transparency test:** Would you be comfortable if every stakeholder saw this risk assessment? + +- [ ] Risks are assessed honestly -- not inflated to justify inaction or deflated to avoid uncomfortable truths +- [ ] Mitigation strategies use legitimate influence, not manipulation or coercion +- [ ] Contingency plans respect stakeholder dignity -- no retaliation for opposition +- [ ] Kill triggers are genuine -- you will actually stop if reached, not move the goalposts + +**If any box is unchecked, revise the assessment before acting on it.** diff --git a/plugins/foreman/content/org-politics/templates/resistance-management-plan.md b/plugins/foreman/content/org-politics/templates/resistance-management-plan.md new file mode 100644 index 0000000..7197f4b --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/resistance-management-plan.md @@ -0,0 +1,109 @@ +--- +name: "resistance-management-plan" +description: "Produces a structured plan for managing identified stakeholder resistance to a specific initiative. For each resister, documents who they are, what they resist, why (root cause from diagnosis), current and redesigned engagement approaches, timeline, and success indicators. Includes root cause analysis, per-resister engagement strategy, escalation triggers, and de-escalation techniques. Internal strategy document -- never shared with resisters." +audience: "self" +applicable_skills: + - thomas-kilmann-conflict + - cialdini-influence + - trust-equation + - persuasion-and-influence + - resolving-people-conflict +format: "plan" +author: "Fatih Guner" +--- + +# Resistance Management Plan + + + +**Initiative:** [Name] | **Date:** [Date] | **Last updated:** [Date] | **Owner:** [Name] + +--- + +## Resister Profile Table + +| # | Name / Role | What They Resist | Root Cause | Power | Veto? | New Approach | Timeline | Success Indicator | +|---|-------------|-----------------|------------|-------|-------|-------------|----------|-------------------| +| 1 | [Name, Title] | [Specific aspect opposed] | [Rational / Territorial / Fear / Power loss / Info gap / Values / Proxy] | [H/M/L] | [Y/N] | [Redesigned engagement] | [Target date] | [Observable behaviour confirming shift] | +| 2 | [Name, Title] | [Aspect] | [Root cause] | [H/M/L] | [Y/N] | [Approach] | [Date] | [Indicator] | +| 3 | [Name, Title] | [Aspect] | [Root cause] | [H/M/L] | [Y/N] | [Approach] | [Date] | [Indicator] | + +--- + +## Root Cause Analysis + +### Resister 1: [Name] + +- **Stated objection:** [What they say is the problem] +- **Diagnosed root cause:** [What triage determined] | **Evidence:** [Which triage answers led here] +- **Underlying interest:** [What they actually need or fear beneath the stated position] + +### Resister 2: [Name] + +- **Stated objection:** [What they say] +- **Diagnosed root cause:** [Actual driver] | **Evidence:** [Triage evidence] +- **Underlying interest:** [Need or fear] + +--- + +## Engagement Strategy per Resister + +### [Resister 1] -- [Root Cause Type] + +**Conflict mode:** [Collaborating / Competing / Compromising / Avoiding / Accommodating] +**Influence principles:** [Cialdini principle]: [Tactic] | [Principle]: [Tactic] + +**Engagement sequence:** +1. [First action -- e.g., "One-on-one; open with acknowledgment of their concern"] +2. [Second action -- e.g., "Present modified proposal addressing territorial interest"] +3. [Third action -- e.g., "Secure small commitment to pilot phase"] + +**What NOT to do:** [Actions that would entrench resistance] + +### [Resister 2] -- [Root Cause Type] + +**Conflict mode:** [TKI mode] | **Influence:** [Principles and tactics] +**Engagement sequence:** [Steps] +**What NOT to do:** [Counterproductive actions] + +--- + +## Escalation Triggers + +| Trigger | Condition | Action | +|---------|-----------|--------| +| **Sustained non-engagement** | Three cancelled or avoided meetings | Engage through trusted intermediary or escalate to superior | +| **Active sabotage** | Covert lobbying, resource withholding, misinformation | Document, present evidence to decision-maker, strengthen coalition | +| **Immovable veto** | Veto holder refuses engagement after two direct attempts | Redesign initiative to remove veto dependency, or escalate to override authority | +| **Opposition coalition** | Resister recruits others into active opposition | Shift to coalition-vs-coalition strategy via coalition-and-partnership-games | +| **Values impasse** | Three conversations confirm irreconcilable conflict | Accept impasse; pursue compromise, restructuring, or initiative redesign | + +--- + +## De-escalation Techniques + +| Technique | When to Use | Execution | +|-----------|------------|-----------| +| **Acknowledge and validate** | Resister feels unheard | Name their concern as legitimate before proposing alternatives | +| **Separate person from position** | Conflict has become personal | Reframe around shared interests and organizational outcomes | +| **Concede the peripheral** | Both substantive and emotional objections | Yield on a visible but non-critical point to demonstrate good faith | +| **Introduce neutral mediator** | Direct engagement turned adversarial | Trusted third party facilitates the conversation | +| **Cooling period** | High emotions after confrontation | Pause 48-72 hours, re-engage through lower-temperature channel | + +--- + +## Progress Tracking + +| Resister | Original Position | Current Position | Last Engagement | Next Action | +|----------|-------------------|-----------------|-----------------|-------------| +| [Name] | [Blocker/Skeptic] | [Has it shifted?] | [Date, summary] | [Next step] | +| [Name] | [Position] | [Current] | [Date, summary] | [Next step] | + +## Post-Decision Review + +- **Outcome:** [Approved / modified / rejected / withdrawn] +- **What worked:** [Strategies that shifted positions] | **What failed:** [Strategies that did not] +- **Lessons:** [What to do differently next time] diff --git a/plugins/foreman/content/org-politics/templates/stakeholder-influence-map.md b/plugins/foreman/content/org-politics/templates/stakeholder-influence-map.md new file mode 100644 index 0000000..1e4485b --- /dev/null +++ b/plugins/foreman/content/org-politics/templates/stakeholder-influence-map.md @@ -0,0 +1,110 @@ +--- +name: "stakeholder-influence-map" +description: "Produces a comprehensive influence-strategy map of all stakeholders relevant to a specific initiative. For each stakeholder, captures Position, Power Level, Interest Level, Current Action, Desired Action, and Influence Strategy. Includes a 2x2 Power-Interest matrix, position tracking, and influence path mapping. This is an internal strategy document -- never shared with the stakeholders themselves." +audience: "self" +applicable_skills: + - coalition-and-partnership-games + - cialdini-influence + - thomas-kilmann-conflict + - trust-equation + - persuasion-and-influence +format: "map" +author: "Fatih Guner" +--- + +# Stakeholder Influence Map + + + +**Initiative:** [Name] | **Date:** [Date] | **Decision date:** [Date] | **Next review:** [Date] + +--- + +## Stakeholder Roster + +| # | Name / Role | Position | Power | Interest | Current Action | Desired Action | Influence Strategy | +|---|-------------|----------|-------|----------|----------------|----------------|-------------------| +| 1 | [Name, Title] | [Champion / Supporter / Neutral / Skeptic / Blocker] | [H / M / L] | [H / M / L] | [What they are doing now] | [What you need them to do] | [Specific approach -- Cialdini principle, TKI mode, message] | +| 2 | [Name, Title] | [Position] | [H/M/L] | [H/M/L] | [Current] | [Desired] | [Strategy] | +| 3 | [Name, Title] | [Position] | [H/M/L] | [H/M/L] | [Current] | [Desired] | [Strategy] | +| 4 | [Name, Title] | [Position] | [H/M/L] | [H/M/L] | [Current] | [Desired] | [Strategy] | + +--- + +## Power-Interest Matrix + +``` + HIGH POWER + | + MANAGE CLOSELY | KEEP SATISFIED + (High power, | (High power, Low interest) + High interest) | Names: + Names: | - [Stakeholder] + - [Stakeholder] | + ------------------+--------------------- + MONITOR | KEEP INFORMED + (Low power, | (Low power, Low interest) + High interest) | Names: + Names: | - [Stakeholder] + - [Stakeholder] | + LOW POWER +``` + +--- + +## Position Tracking + +``` +CHAMPION ------- SUPPORTER ------- NEUTRAL ------- SKEPTIC ------- BLOCKER + | | | | | + [Names] [Names] [Names] [Names] [Names] +``` + +| Stakeholder | Current | Target | Movement Strategy | Timeline | +|-------------|---------|--------|-------------------|----------| +| [Name] | [Position] | [Position] | [Specific action to move them] | [By when] | +| [Name] | [Position] | [Position] | [Strategy] | [Timeline] | + +--- + +## Influence Path Map + +_Who influences whom? Trace pathways to identify the most efficient engagement sequence._ + +| Target | Who Influences Them | Second-Degree Influencer | Your Access Point | +|--------|-------------------|--------------------------|-------------------| +| [Decision-maker] | [Influencer] | [Their influencer] | [How you reach the chain] | +| [Decision-maker] | [Influencer] | [Their influencer] | [Access point] | + +--- + +## Coalition Status + +| Category | Stakeholders | Combined Power | Status | +|----------|-------------|---------------|--------| +| **Committed** | [Names] | [H/M/L] | [Holding / At risk / Strengthening] | +| **Recruiting** | [Names] | [H/M/L] | [Not engaged / In conversation / Near commitment] | +| **Neutralizing** | [Names] | [H/M/L] | [Active opposition / Contained / Neutralized] | + +**Coalition arithmetic:** Does committed + pipeline outvote the opposition? [Yes / No / Uncertain] + +--- + +## Risk Assessment + +- **Biggest threat:** [Stakeholder or dynamic most likely to derail the initiative] +- **Blind spot:** [Who has not been mapped?] | **Fragility:** [Most likely defector?] +- **Timeline risk:** [Is the decision date achievable given required engagement sequence?] + +--- + +## Action Items + +| Priority | Action | Target | Owner | Due | Status | +|----------|--------|--------|-------|-----|--------| +| 1 | [Specific engagement action] | [Name] | [Who] | [Date] | [Not started / Done] | +| 2 | [Action] | [Name] | [Who] | [Date] | [Status] | diff --git a/plugins/foreman/content/output-templates/_schema/output-template.md b/plugins/foreman/content/output-templates/_schema/output-template.md new file mode 100644 index 0000000..ec48f76 --- /dev/null +++ b/plugins/foreman/content/output-templates/_schema/output-template.md @@ -0,0 +1,62 @@ +--- +name: "kebab-case-template-name" +description: "Third-person description of what this template produces, for which audience, and when to use it. Max 1024 characters." +audience: "investor | board | team | self | client" +applicable_skills: + - skill-name-1 + - skill-name-2 + - skill-name-3 +format: "one-pager | memo | report | proposal | briefing | checklist | plan | dashboard | email-template | scorecard | canvas | journal-entry | reflection | prep-worksheet | tracker | self-assessment | meeting-template | working-document | planning-guide | feedback-form | structured-review | case-study | status-report | agreement | welcome-packet | review-and-plan | map | agenda | summary | analysis | update" +author: "Fatih Guner" +--- + +) + - Templates must be IMMEDIATELY USABLE — fillable in 30-60 minutes + - Distinct structure per template — no two templates should feel similar + - Writing style: Foreman voice (analytical, institutional, precise) + - Target length varies by format: + - One-pager / dashboard / email: 60-100 lines + - Memo / briefing / checklist / plan: 80-120 lines + - Report / proposal / canvas: 100-150 lines +--> + +# {Template Title} + + + +## {Section 1} + + + +{Fill-in content with [placeholders]} + +--- + +## {Section 2} + + + +| Column 1 | Column 2 | Column 3 | +|----------|----------|----------| +| [data] | [data] | [data] | + +--- + +## {Section N} + +{Continue as needed for the specific template type} diff --git a/plugins/foreman/content/output-templates/board/board-meeting-agenda.md b/plugins/foreman/content/output-templates/board/board-meeting-agenda.md new file mode 100644 index 0000000..8091834 --- /dev/null +++ b/plugins/foreman/content/output-templates/board/board-meeting-agenda.md @@ -0,0 +1,87 @@ +--- +name: "board-meeting-agenda" +description: "Produces a time-blocked board meeting agenda with six structured sections spanning 90 minutes. Each section carries a time allocation, responsible presenter, pre-read reference, and decision classification (inform, discuss, or decide). Designed to ensure boards spend the majority of time on strategic discussion rather than status reporting. Informed by NACD governance best practices and adapted for high-growth companies where board time is the scarcest executive resource." +audience: "board" +applicable_skills: + - focus-and-priority-management + - strategic-thinking-and-alignment + - delegation-and-empowerment +format: "agenda" +author: "Fatih Guner" +--- + +# Board Meeting Agenda + +Most board meetings fail identically: forty minutes of backward-looking reports, ten minutes of rushed strategy. This agenda inverts the pattern. Reports belong in pre-reads distributed 72 hours in advance. The meeting is for decisions requiring collective judgment in real time. Replace all placeholders. Distribute with pre-reads three business days before. + +**[Company Name] — Board of Directors Meeting** + +**Date:** [Day, Date] | **Time:** [Start] - [End] (90 min) | **Location:** [Address / Video link] +**Attendees:** [Directors, observers, management] | **Materials sent:** [Date] + +**Pre-reads** (review before meeting — not presented): Financial package — [CFO] | KPI dashboard — [CEO] | Strategic briefing — [CEO] | [Additional] — [Owner]. Directors arrive having read all materials. Presenters summarize implications, not content. + +--- + +### I. Administrative — 5 min +**[Start] - [Start + 5]** | **Led by:** [Board Chair] | **Type:** Inform + +Quorum confirmation | Approval of [Date] minutes | Conflicts declaration +Consent agenda: [Routine approvals — option grants, committee appointments] + +### II. CEO Update — 15 min +**[Start + 5] - [Start + 20]** | **Led by:** [CEO] | **Type:** Inform + +1. **State of the business** (5 min): [What works, what does not, what changed. Reference pre-read metrics.] +2. **Top priority** (5 min): [Single most consequential initiative. Why it outranks alternatives. Progress.] +3. **What concerns me** (5 min): [Risk or uncertainty the board should understand, even without action required.] + +### III. Financial Review — 15 min +**[Start + 20] - [Start + 35]** | **Led by:** [CFO] | **Type:** Discuss + +- Actual vs. plan: revenue, burn, gross margin — material variances only (>10%) +- Cash: $[amount] | Runway: [X] months through [Date] +- Forecast revisions: [Changed or unchanged, with reasoning] +- **Board question:** [One financial question for board input — e.g., "Extend runway via cost cuts or accelerate and fundraise sooner?"] + +### IV. Strategic Discussion — 30 min +**[Start + 35] - [Start + 65]** | **Led by:** [CEO / presenter] | **Type:** Discuss / Decide + + + +**Topic:** [Strategic question in one sentence — e.g., "Enter European market in H2 via direct sales or partnership?"] +**Context:** [Three sentences — why now, what triggered the question.] + +| Option | Key Advantage | Key Risk | +|--------|--------------|----------| +| A: [Description] | [Advantage] | [Risk] | +| B: [Description] | [Advantage] | [Risk] | +| C: ["Do nothing" if applicable] | [Advantage] | [Risk] | + +**Management recommendation:** [State with conviction.] +**Board input sought:** [Specific guidance, approval, or assumption challenge.] +**Decision required:** [Yes — motion recorded / No — input only, decision by [Date]] + +### V. Decisions and Governance — 15 min +**[Start + 65] - [Start + 80]** | **Led by:** [Board Chair] | **Type:** Decide + +| Motion | Proposed By | Vote | +|--------|-------------|------| +| [Decision 1: precise wording] | [Name] | [Majority / Unanimous] | +| [Decision 2] | [Name] | [Vote type] | + +| Action Item | Owner | Deadline | +|-------------|-------|----------| +| [Action 1] | [Name] | [Date] | +| [Action 2] | [Name] | [Date] | + +### VI. Executive Session — 10 min +**[Start + 80] - [Start + 90]** | **Led by:** [Lead Independent Director] | **Type:** Confidential + +Management excused. Standing agenda: CEO performance and support needs, board effectiveness, independent deliberation. Feedback to CEO by [Board Chair] within [X] days. + +--- + +**Next meeting:** [Date] | **Materials due:** [Date] | **Secretary:** [Name, contact] + + diff --git a/plugins/foreman/content/output-templates/board/ceo-succession-brief.md b/plugins/foreman/content/output-templates/board/ceo-succession-brief.md new file mode 100644 index 0000000..68bb488 --- /dev/null +++ b/plugins/foreman/content/output-templates/board/ceo-succession-brief.md @@ -0,0 +1,109 @@ +--- +name: "ceo-succession-brief" +description: "Produces a leadership succession planning document covering the five most critical roles in the organization. For each role: current holder, internal successor candidates with readiness assessment, development gaps, external search triggers, and emergency interim coverage. Includes a 9-box talent grid (performance x potential) and readiness summary. Calibrated to Spencer Stuart and Korn Ferry succession methodologies, adapted for high-growth companies where leadership bench depth is thin and the cost of vacancy is existential." +audience: "board" +applicable_skills: + - leadership-pipeline + - senior-leadership-transition + - belbin-team-roles + - career-strategy-for-leaders +format: "briefing" +author: "Fatih Guner" +--- + +# CEO & Critical Role Succession Brief + +Succession planning is the governance responsibility boards most frequently defer and most deeply regret. A departing CEO with no identified successor costs 5-10% of market value during transition — at a startup, where leadership concentration runs extreme, the figure can be terminal. Fill with honest assessments. A flattering plan protects no one. + +**BOARD CONFIDENTIAL** | **[Company Name]** | **[Date]** | **Prepared by:** [CHRO / CEO / Board Chair] +**Review cycle:** [Annual / Semi-annual] | **Next review:** [Date] | **Risk level:** [Low / Moderate / High / Critical] — [Basis] + +--- + +## 9-Box Talent Grid — Senior Leadership + +| | **Low Performance** | **Moderate Performance** | **High Performance** | +|---|---|---|---| +| **High Potential** | [Name(s)] — Misplaced | [Name(s)] — Invest in development | [Name(s)] — Star: retain, succession candidate | +| **Moderate Potential** | [Name(s)] — Diagnose cause | [Name(s)] — Core contributor | [Name(s)] — Stretch to test ceiling | +| **Low Potential** | [Name(s)] — Manage out | [Name(s)] — Optimize in role | [Name(s)] — Deep expert, limited progression | + +**Pattern:** [One sentence — e.g., "Bench strong in product/engineering, thin in commercial roles."] + +--- + +## Role 1: Chief Executive Officer + +**Current:** [Name] | **Tenure:** [X yr] | **Flight risk:** [Low / Mod / High] | **Vacancy impact:** Existential + +| Candidate | Current Role | Readiness | Strengths | Gaps | Development Plan | +|-----------|-------------|-----------|-----------|------|-----------------| +| [Name A] | [Role] | [Ready Now / 1-2 Yr / 3+ Yr] | [Strengths for CEO role] | [Specific gaps] | [Board observer, lead fundraise, coaching] | +| [Name B] | [Role] | [Readiness] | [Strengths] | [Gaps] | [Plan] | + +**External triggers:** [Departure with no Ready Now candidate; strategic pivot requiring absent expertise.] +**Emergency:** [Name] assumes interim. Max [X] months. Search committee within [X] business days. + +## Roles 2-5 + + + +**Role 2: [Title]** | [Name] | [X yr] | Flight risk: [Level] | Vacancy impact: [Level] + +| Candidate | Current Role | Readiness | Strengths | Gaps | Development Plan | +|-----------|-------------|-----------|-----------|------|-----------------| +| [Name] | [Role] | [Readiness] | [Strengths] | [Gaps] | [Plan] | + +**Triggers / Emergency:** [Conditions] | [Interim name and protocol] + +**Role 3: [Title]** | [Name] | [X yr] | Flight risk: [Level] | Vacancy impact: [Level] + +| Candidate | Current Role | Readiness | Strengths | Gaps | Development Plan | +|-----------|-------------|-----------|-----------|------|-----------------| +| [Name] | [Role] | [Readiness] | [Strengths] | [Gaps] | [Plan] | + +**Triggers / Emergency:** [Conditions] | [Interim name and protocol] + +**Role 4: [Title]** | [Name] | [X yr] | Flight risk: [Level] | Vacancy impact: [Level] + +| Candidate | Current Role | Readiness | Strengths | Gaps | Development Plan | +|-----------|-------------|-----------|-----------|------|-----------------| +| [Name] | [Role] | [Readiness] | [Strengths] | [Gaps] | [Plan] | + +**Triggers / Emergency:** [Conditions] | [Interim name and protocol] + +**Role 5: [Title]** | [Name] | [X yr] | Flight risk: [Level] | Vacancy impact: [Level] + +| Candidate | Current Role | Readiness | Strengths | Gaps | Development Plan | +|-----------|-------------|-----------|-----------|------|-----------------| +| [Name] | [Role] | [Readiness] | [Strengths] | [Gaps] | [Plan] | + +**Triggers / Emergency:** [Conditions] | [Interim name and protocol] + +--- + +## Readiness Summary + +| Role | Incumbent | Ready Now | Ready 1-2 Yr | External Needed | +|------|-----------|-----------|---------------|-----------------| +| CEO | [Name] | [Name or NONE] | [Name(s)] | [Yes / No] | +| [Role 2] | [Name] | [Name or NONE] | [Name(s)] | [Yes / No] | +| [Role 3] | [Name] | [Name or NONE] | [Name(s)] | [Yes / No] | +| [Role 4] | [Name] | [Name or NONE] | [Name(s)] | [Yes / No] | +| [Role 5] | [Name] | [Name or NONE] | [Name(s)] | [Yes / No] | + +**Governance gaps:** [Roles with no Ready Now or 1-2 Year candidate represent board-level risk.] + +## Development Investment and Board Actions + +| Initiative | Candidate | Cost | Timeline | Outcome | +|-----------|-----------|------|----------|---------| +| [Executive coaching] | [Name] | $[amount] | [Duration] | [Readiness milestone] | +| [Board observer seat] | [Name] | Minimal | [Start] | [Governance exposure] | +| [P&L ownership expansion] | [Name] | [Cost] | [Duration] | [GM readiness] | + +**Board actions:** 1. [Approve plan / revise] 2. [Authorize investment: $[amount]] 3. [External mapping for [Role]] 4. [Schedule review at [next meeting]] + +--- + +*Board Confidential. Distribution restricted to directors and preparer. Not shared with candidates without board authorization. Next review: [Date].* diff --git a/plugins/foreman/content/output-templates/board/change-initiative-proposal.md b/plugins/foreman/content/output-templates/board/change-initiative-proposal.md new file mode 100644 index 0000000..0ed4994 --- /dev/null +++ b/plugins/foreman/content/output-templates/board/change-initiative-proposal.md @@ -0,0 +1,126 @@ +--- +name: "change-initiative-proposal" +description: "Structures a board-level proposal for major organisational change — restructuring, pivots, new market entry, or culture transformation. Follows an eight-phase Kotter-influenced roadmap with integrated risk assessment and resource requirements. Use when seeking board approval or endorsement for any initiative that materially alters the organisation's structure, strategy, or operating model." +audience: "board" +applicable_skills: + - kotter-change-model + - leading-through-change + - organisational-culture + - scenario-planning + - systems-thinking +format: "proposal" +author: "Fatih Guner" +--- + +# Change Initiative Proposal + +Replace all bracketed placeholders. Every section exists because boards have learned — often through failure — that these are the questions left unasked until the change is underway and the cost of answering them has multiplied. Delete this paragraph before distribution. + +--- + +## [Initiative Name] — Board Proposal + +**Submitted to:** Board of Directors | **Sponsor:** [Executive Name, Title] +**Date:** [Date] | **Decision requested by:** [Date] + +--- + +## 1. The Burning Platform + +[Two to three paragraphs establishing the case for urgency. Ground this in evidence — market data, competitive moves, performance trends — not anxiety or aspiration. The board must conclude independently that inaction carries greater risk than action.] + +| Indicator | 12 Months Ago | Current | Projected (No Change) | +|-----------|--------------|---------|----------------------| +| [Key metric 1] | [value] | [value] | [value] | +| [Key metric 2] | [value] | [value] | [value] | +| [Key metric 3] | [value] | [value] | [value] | + +**Cost of inaction:** [One sentence. Be precise — "market share erosion" is a phrase; "loss of an estimated X% share within Y quarters based on Z trajectory" is an argument.] + +--- + +## 2. Vision of Success + +[Two paragraphs painting a specific, measurable picture of the post-change state. The board should be able to read this in 18 months and determine whether the initiative succeeded or failed.] + +| Dimension | Current State | Target State (Month [X]) | Measurement | +|-----------|--------------|--------------------------|-------------| +| [Strategic dimension 1] | [current] | [target] | [how measured] | +| [Strategic dimension 2] | [current] | [target] | [how measured] | +| [Cultural dimension] | [current] | [target] | [how measured] | + +--- + +## 3. Change Roadmap + +Eight phases, informed by Kotter's model. Each states its objective, key actions, duration, and the gate signal indicating readiness to proceed. + +| Phase | Objective | Key Actions | Duration | Gate Signal | +|-------|-----------|-------------|----------|-------------| +| **1. Establish Urgency** | [Authentic urgency, not performative] | [Data sharing, customer evidence sessions] | Wks [X-Y] | [Measurable proxy for urgency landing] | +| **2. Build Guiding Coalition** | [Assemble cross-functional leadership] | [Name the roles and why each is critical] | Wks [X-Y] | [Coalition formed, charter agreed] | +| **3. Develop Vision & Initiatives** | [Translate platform into owned strategy] | [Scenario workshops, initiative design] | Wks [X-Y] | [Vision ratified, backlog prioritised] | +| **4. Communicate for Buy-In** | [Every stakeholder understands why, what, and their role] | [Channels, cadence, feedback loops] | Wks [X-Y] | [Pulse survey confirms awareness threshold] | +| **5. Remove Barriers** | [Dismantle structural and cultural obstacles] | [Policy changes, training, role clarity] | Wks [X-Y] | [Top obstacles resolved or escalated] | +| **6. Generate Short-Term Wins** | [Visible results validating direction] | [Define wins in advance — accidental wins lack credibility] | Wks [X-Y] | [Wins documented and communicated] | +| **7. Sustain Acceleration** | [Use wins to drive deeper change] | [Expand scope, reinforce through systems] | Wks [X-Y] | [Metrics show sustained trajectory] | +| **8. Institute in Culture** | [Embed change as default, not mandate] | [Hiring criteria, promotions, rituals, rewards] | Ongoing | [Behaviours persist without programme reinforcement] | + +--- + +## 4. Resource Requirements + +| Category | Description | Amount | Timing | +|----------|-------------|--------|--------| +| Personnel | [New hires, redeployments, advisors] | [cost] | [when] | +| Technology | [Systems, tools, infrastructure] | [cost] | [when] | +| External Support | [Consultants, coaches, specialists] | [cost] | [when] | +| Disruption Cost | [Productivity impact during transition] | [cost] | [duration] | +| **Total** | | **[total]** | **[period]** | + +**Opportunity cost:** [What the organisation will not do because resources are allocated here. Name the trade-off.] + +--- + +## 5. Risk Matrix + +| Risk | Prob. | Impact | Mitigation | Owner | +|------|-------|--------|------------|-------| +| [Change fatigue / initiative overload] | [H/M/L] | [H/M/L] | [Specific mitigation] | [Name] | +| [Key talent departure during transition] | [H/M/L] | [H/M/L] | [Specific mitigation] | [Name] | +| [Customer disruption during changeover] | [H/M/L] | [H/M/L] | [Specific mitigation] | [Name] | +| [Coalition fragmentation] | [H/M/L] | [H/M/L] | [Specific mitigation] | [Name] | +| [External shift invalidating assumptions] | [H/M/L] | [H/M/L] | [Specific mitigation] | [Name] | + +**Worst-case scenario:** [The situation where the initiative is half-executed and can be neither reversed nor completed. What is the contingency?] + +--- + +## 6. Success Metrics & Governance + +**Leading indicators** (monthly, steering committee): [Metric 1 — adoption signal] | [Metric 2 — behavioural measure] | [Metric 3 — sentiment proxy] + +**Lagging indicators** (quarterly, board): [Metric 1 — financial outcome] | [Metric 2 — market impact] | [Metric 3 — capability measure] + +| Governance Role | Person | Cadence | +|----------------|--------|---------| +| Executive Sponsor | [Name] | Continuous | +| Steering Committee Chair | [Name] | Bi-weekly | +| Board Liaison | [Name] | Quarterly + ad-hoc escalation | + +**Kill criteria:** [Under what conditions does the board halt this initiative? Define the tripwire now. Initiatives without exit criteria consume resources long after their rationale has expired.] + +--- + +## 7. Board Decision Requested + +**Motion:** [State precisely what is asked — approval to proceed, conditional approval, budget authorisation, or endorsement with return for final approval.] + +**Alternatives considered:** +1. [Alternative A — brief description and reason for rejection] +2. [Alternative B — brief description and reason for rejection] +3. [Status quo — restate the cost of inaction from Section 1] + +--- + +*Appendices available upon request: financial model, stakeholder analysis, communication plan, scenario planning output.* diff --git a/plugins/foreman/content/output-templates/board/compensation-review-brief.md b/plugins/foreman/content/output-templates/board/compensation-review-brief.md new file mode 100644 index 0000000..a6225a7 --- /dev/null +++ b/plugins/foreman/content/output-templates/board/compensation-review-brief.md @@ -0,0 +1,100 @@ +--- +name: "compensation-review-brief" +description: "Produces an executive and key employee compensation review for board approval, covering compensation philosophy, individual comp tables with market benchmarks, ESOP utilization, proposed changes with rationale, peer benchmarking, and draft resolution language. Use when preparing annual compensation reviews, onboarding new executives, or seeking board approval for equity grants and salary adjustments." +audience: "board" +applicable_skills: + - balanced-scorecard + - coalition-and-partnership-games + - leadership-pipeline +format: "briefing" +author: "Fatih Guner" +--- + +# Compensation Review Brief + +Compensation decisions are retention bets disguised as expense line items. Underpaying a critical executive saves money quarterly and costs millions at departure. Overpaying a mediocre one compounds in both cash and cultural signal. This brief provides the data for deliberate decisions. Replace all placeholders and delete this paragraph before distribution. + +**[Company Name]** | **Board meeting:** [Date] | **Review period:** [Fiscal Year / Period] +**Prepared by:** [CEO / Head of People / CFO] | **Classification:** Board Confidential + +--- + +## Compensation Philosophy + +[Company Name] targets [Xth percentile — e.g., 50th, 75th] of base compensation and [Xth percentile] of total compensation (including equity) relative to [peer set definition — e.g., venture-backed SaaS companies, Series A-B, 50-200 employees, primary metro areas]. Equity is weighted toward early employees and roles with direct impact on enterprise value. Cash compensation reflects market rates sufficient to eliminate compensation as a reason to leave, without attempting to compete on cash alone with public companies or late-stage peers. + +--- + +## Executive Compensation Table + +| Name | Title | Tenure | Base Salary | Cash Bonus (Target / Actual) | Equity (Unvested Value) | Total Comp | Market Benchmark (Total) | vs. Market | +|------|-------|--------|------------:|----------------------------:|------------------------:|-----------:|-------------------------:|-----------:| +| [Name] | CEO | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | +| [Name] | CTO | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | +| [Name] | CFO | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | +| [Name] | VP Sales | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | +| [Name] | VP Engineering | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | +| [Name] | [Other Key Role] | [X] yr | $[amount] | $[target] / $[actual] | $[value] | $[total] | $[benchmark] | [+/-X]% | + +**Equity valuation basis:** [409A FMV of $X.XX/share as of Date] or [Last round price of $X.XX/share] +**Benchmark source:** [Carta Total Comp / Pave / Radford / Option Impact — specify dataset and date] + +--- + +## ESOP Utilization + +| Authorized | Granted | Exercised | Cancelled | Available | Burn Rate | Runway | +|------------|---------|-----------|-----------|-----------|-----------|--------| +| [#] shares ([X.X]%) | [#] shares | [#] shares | [#] shares | [#] shares ([X.X]%) | [X.X]%/yr | [X] months | + +**Pool adequacy:** [Two sentences. Sufficient for next 18 months of hiring and retention? Pool increase required before next financing?] + +--- + +## Proposed Changes + +| # | Name / Role | Change Type | Current | Proposed | Rationale | +|---|-------------|-------------|---------|----------|-----------| +| 1 | [Name], [Role] | Base increase | $[current] | $[proposed] (+[X]%) | [Market realignment — currently [X]% below benchmark; retention risk following competing offer] | +| 2 | [Name], [Role] | Equity refresh | [current unvested] | +[number] options | [18 months tenure, cliff cleared, high performer with <12 months unvested remaining] | +| 3 | [Name], [Role] | Bonus adjustment | [current target]% | [proposed target]% | [Role scope expanded to include [area]; aligning incentive with accountability] | +| 4 | [Name], [Role] | New hire package | N/A | $[base] + [options] | [Critical hire; package reflects [Xth percentile] total comp for [role] at [stage] companies] | +| 5 | [Name], [Role] | Promotion | [Current title/band] | [New title/band] | [Performance, scope increase, and market title alignment] | + +**Total incremental annual cost of proposed changes:** $[amount] ([X]% increase to total comp expense) + +--- + +## Peer Benchmarking & Total Cost + +| Company (Anonymised) | Stage | Headcount | CEO Base | CTO Base | VP Eng Base | Equity (% at hire) | +|-----------------------|-------|-----------|--------:|---------:|------------:|-------------------:| +| Peer A | [Stage] | [range] | $[amount] | $[amount] | $[amount] | [X.XX]% | +| Peer B | [Stage] | [range] | $[amount] | $[amount] | $[amount] | [X.XX]% | +| Peer C | [Stage] | [range] | $[amount] | $[amount] | $[amount] | [X.XX]% | +| **[Company Name]** | **[Stage]** | **[range]** | **$[amount]** | **$[amount]** | **$[amount]** | **[X.XX]%** | + +**Peer set:** [Geography, stage, sector, revenue range, headcount] | **Source:** [Carta / Pave / Radford — date] + +| Cost Metric | Prior Period | Current | Proposed | +|-------------|------------:|--------:|---------:| +| Total cash compensation | $[amount] | $[amount] | $[amount] | +| Total equity expense (fair value) | $[amount] | $[amount] | $[amount] | +| Compensation as % of revenue | [X.X]% | [X.X]% | [X.X]% | + +--- + +## Board Resolution + +**RESOLVED**, that the Board of Directors of [Company Name] hereby approves the following compensation actions effective [Date]: + +1. Base salary adjustments for [Names/Roles] as detailed in the Proposed Changes table above. +2. Option grants totaling [number] shares to [Names/Roles] under the Company's [Year] Equity Incentive Plan, at an exercise price of $[409A FMV] per share, vesting over [4] years with a [1]-year cliff. +3. Bonus target adjustments for [Names/Roles] as specified. +4. [Any other specific approval — new hire package, ESOP pool increase recommendation, etc.] + +**FURTHER RESOLVED**, that the [Compensation Committee / CEO] is authorized to execute the necessary agreements to implement these changes. + +--- + +*Data as of [Date]. Benchmarks: [source and vintage]. Equity values: [methodology and date]. Board and Compensation Committee confidential.* diff --git a/plugins/foreman/content/output-templates/board/quarterly-strategic-review.md b/plugins/foreman/content/output-templates/board/quarterly-strategic-review.md new file mode 100644 index 0000000..17b428e --- /dev/null +++ b/plugins/foreman/content/output-templates/board/quarterly-strategic-review.md @@ -0,0 +1,129 @@ +--- +name: "quarterly-strategic-review" +description: "Produces a quarterly board update structured around the Balanced Scorecard's four perspectives — financial, customer, internal process, and learning/growth. Designed for boards that demand strategic narrative over data dumps. Use when preparing Q1-Q4 board meetings, annual reviews, or any recurring governance update where directors need to assess organizational health across all dimensions simultaneously." +audience: "board" +applicable_skills: + - balanced-scorecard + - swot-pest-analysis + - ambidexterity + - growth-share-matrix + - smart-goals +format: "report" +author: "Fatih Guner" +--- + +# Quarterly Strategic Review + +Replace all bracketed placeholders. Delete this line before distribution. The template enforces a discipline: every metric demands a trend, every trend demands an insight, every insight demands an action. + +--- + +## [Company Name] — Q[X] [Year] Board Update + +**Prepared for:** Board of Directors | **Date:** [Date] | **Prepared by:** [CEO / CFO Name] + +**Executive Headlines:** +1. **Working:** [One sentence on the quarter's strongest strategic outcome — be specific, cite a metric] +2. **Stalling:** [One sentence on the most material area of underperformance or concern] +3. **Shifting:** [One sentence on a strategic change in direction, market condition, or assumption] + +--- + +## I. Financial Perspective + +> The rearview mirror. What happened, and what the numbers reveal about execution quality. + +| Metric | Target | Actual | vs. Prior Q | Trend | +|--------|--------|--------|-------------|-------| +| Revenue | [target] | [actual] | [+/- %] | [direction] | +| Gross Margin | [target] | [actual] | [+/- pp] | | +| Burn Rate / FCF | [target] | [actual] | [+/- %] | | +| [Business-specific metric] | [target] | [actual] | [+/- %] | | + +**Insight:** [Two to three sentences. What is the story behind the data? Distinguish structural trends from one-time effects.] + +**Action:** [Specific management response — what, by whom, by when.] + +--- + +## II. Customer Perspective + +> Customer metrics degrade before financial metrics do. This section reveals whether future revenue is secure. + +| Metric | Target | Actual | vs. Prior Q | Trend | +|--------|--------|--------|-------------|-------| +| NPS / CSAT | [target] | [actual] | [+/- pts] | | +| Retention / Churn | [target] | [actual] | [+/- pp] | | +| Customer Acquisition Cost | [target] | [actual] | [+/- %] | | + +**Insight:** [Distinguish between segments. Surface any divergence between satisfaction and retention — the gap reveals more than either metric alone.] + +**Action:** [Specific intervention. Name the owner and timeline.] + +--- + +## III. Internal Process Perspective + +> Operational capability determines whether strategy is executable or aspirational. + +| Metric | Target | Actual | vs. Prior Q | Trend | +|--------|--------|--------|-------------|-------| +| [Delivery/cycle time metric] | [target] | [actual] | [+/- %] | | +| [Quality/defect metric] | [target] | [actual] | [+/- %] | | +| [Innovation pipeline metric] | [target] | [actual] | [+/- %] | | + +**Insight:** [Where are bottlenecks? What is the exploitation-to-exploration ratio? Flag single points of failure.] + +**Action:** [Process changes or investments underway. Be candid about timeline realism.] + +--- + +## IV. Learning & Growth Perspective + +> Organisational capability compounds slowly and erodes invisibly. Neglect here surfaces as crisis elsewhere — typically two to four quarters later. + +| Metric | Target | Actual | vs. Prior Q | Trend | +|--------|--------|--------|-------------|-------| +| Employee Engagement / eNPS | [target] | [actual] | [+/- pts] | | +| Voluntary Attrition (key roles) | [target] | [actual] | [+/- pp] | | +| Capability Investment (% of rev) | [target] | [actual] | [+/- pp] | | + +**Insight:** [Are people and culture keeping pace with strategic ambition? Flag talent risks, skill gaps, culture drift.] + +**Action:** [Leadership, talent, or capability initiatives. State expected impact horizon.] + +--- + +## Strategy Map — Causal Chain + +[Three to five sentences tracing the causal logic connecting the four perspectives. Example: "Investment in engineering onboarding (Learning) reduced deployment cycle time by 18% (Process), improving time-to-value for enterprise customers (Customer), contributing to a 12% uplift in expansion revenue (Financial)." Where the chain is broken, name the break.] + +--- + +## Portfolio View + +| Initiative / Product Line | BCG Quadrant | Q-o-Q Trajectory | Board Attention Required | +|--------------------------|--------------|-------------------|--------------------------| +| [Initiative A] | [Star / Cash Cow / Question Mark / Dog] | [Improving / Stable / Declining] | [Yes / No] | +| [Initiative B] | | | | + +## SWOT Update — Material Changes This Quarter + +| | Helpful | Harmful | +|---|---------|---------| +| **Internal** | **Strengths gained:** [brief] | **Weaknesses exposed:** [brief] | +| **External** | **Opportunities emerged:** [brief] | **Threats materialised:** [brief] | + +--- + +## Decisions, Asks, and Questions for the Board + +1. **For approval:** [Decision requiring board vote — state the motion clearly] +2. **For input:** [Strategic question where management seeks board perspective] +3. **For awareness:** [Material development the board should track but need not act on] +4. [Strategic question reflecting genuine uncertainty — not a rhetorical device] +5. [Question about resource allocation trade-offs the board should weigh in on] + +--- + +*Next board meeting: [Date]. Materials due to directors by [Date].* diff --git a/plugins/foreman/content/output-templates/board/regulatory-compliance-update.md b/plugins/foreman/content/output-templates/board/regulatory-compliance-update.md new file mode 100644 index 0000000..76c7dbe --- /dev/null +++ b/plugins/foreman/content/output-templates/board/regulatory-compliance-update.md @@ -0,0 +1,98 @@ +--- +name: "regulatory-compliance-update" +description: "Produces a regulatory and compliance status report for board oversight, covering compliance posture by domain, pending regulatory changes, audit findings, incident log, upcoming deadlines, and resource requirements. Structured so directors can discharge their governance obligations with appropriate documentation. Use for quarterly board meetings, post-incident reporting, or when regulatory landscape shifts demand board awareness." +audience: "board" +applicable_skills: + - systems-thinking + - black-swans + - vuca-framework + - scenario-planning +format: "update" +author: "Fatih Guner" +--- + +# Regulatory & Compliance Update + +Boards govern; management complies. This report exists so directors can verify that compliance is functioning, not assume it. A compliance program that cannot produce documentation on demand is, functionally, not a compliance program. Replace all placeholders and delete this paragraph before distribution. + +**[Company Name]** | **Period:** [Quarter / Date Range] | **Board meeting:** [Date] | **Prepared by:** [GC / Compliance / DPO] + +**Overall compliance posture: [GREEN / AMBER / RED]** — changed from [prior status] in [prior period]. + +[Three to four sentences. Material compliance developments. Any domain that moved to amber or worse. If unchanged, the most significant near-term risk.] + +--- + +## Compliance Status by Domain + +| Domain | Requirement | Jurisdiction | Status | Last Assessed | Gap / Remediation | +|--------|-------------|-------------|--------|--------------|-------------------| +| **Privacy** | GDPR compliance | EU/EEA | [Compliant / Partial / Non-compliant] | [Date] | [Finding + action, or "None"] | +| | CCPA/CPRA compliance | California | [Status] | [Date] | [Finding + action] | +| | DPAs and data retention | Global | [Status] | [Date] | [# covered / # outstanding] | +| **Financial** | Tax compliance (federal/state) | [Jurisdictions] | [Status] | [Date] | [Finding + action] | +| | Sales tax / VAT collection | [States/countries] | [Status] | [Date] | [Nexus analysis current?] | +| | Corporate governance | [State of incorporation] | [Status] | [Date] | [Finding + action] | +| **Industry** | [E.g., SOC 2 Type II] | [Standard] | [Status] | [Date] | [Finding + action] | +| | [E.g., HIPAA / PCI DSS] | [Standard] | [Status] | [Date] | [Finding + action] | +| | [Add rows per sector] | | | | | + +--- + +## Pending Regulatory Changes & Impact Assessment + +| Regulatory Change | Jurisdiction | Expected Effective Date | Impact Severity | Preparedness | Required Action | +|-------------------|-------------|------------------------|:--------------:|:------------:|-----------------| +| [E.g., EU AI Act — high-risk classification] | EU | [Date] | [High / Medium / Low] | [Ready / Preparing / Not Started] | [Specific steps, cost estimate, responsible party] | +| [E.g., State privacy law — new jurisdiction] | [State] | [Date] | [Severity] | [Status] | [Action] | +| [E.g., Industry regulation amendment] | [Jurisdiction] | [Date] | [Severity] | [Status] | [Action] | + +**Horizon scanning:** [Two sentences. The regulatory development furthest out (12-24 months) that could materially affect operations.] + +--- + +## Audit Findings & Remediation + +| Audit | Auditor | Date Completed | Findings (Critical / Major / Minor) | Open Items | Target Close Date | +|-------|---------|---------------|:------------------------------------:|:----------:|:-----------------:| +| [E.g., SOC 2 Type II] | [Firm] | [Date] | [0 / 2 / 5] | [# open] | [Date] | +| [E.g., Internal security audit] | [Internal / Firm] | [Date] | [#C / #Maj / #Min] | [# open] | [Date] | +| [E.g., Financial audit] | [Firm] | [Date] | [#C / #Maj / #Min] | [# open] | [Date] | + +**Critical findings:** [Describe each in two to three sentences, or "No critical findings this period."] + +## Incident Log + +| Date | Category | Description | Severity | Root Cause | Status | Regulatory Notification | +|------|----------|-------------|:--------:|------------|--------|:-----------------------:| +| [Date] | [Data breach / Privacy complaint / Regulatory inquiry / Policy violation] | [Two-sentence description] | [Critical / High / Medium / Low] | [Identified / Under investigation] | [Resolved / Open / Monitoring] | [Required? Filed? Date] | +| [Date] | [Category] | [Description] | [Severity] | [Root cause] | [Status] | [Notification status] | + +**Period summary:** [Total incidents: X. Severity breakdown. Trend vs. prior period. Systemic patterns, if any.] + +## Upcoming Deadlines & Resource Requirements + +| Deadline | Requirement | Owner | Status | Risk if Missed | +|----------|------------|-------|--------|----------------| +| [Date] | [E.g., SOC 2 audit commencement] | [Name] | [On track / At risk] | [Consequence] | +| [Date] | [E.g., DPA annual review] | [Name] | [Status] | [Consequence] | +| [Date] | [E.g., Insurance renewal (D&O, cyber)] | [Name] | [Status] | [Consequence] | + +| Resource Need | Justification | Cost | Priority | +|--------------|--------------|-----:|:--------:| +| [E.g., Compliance hire] | [Regulatory complexity exceeds part-time capacity] | $[amount]/yr | [High / Medium] | +| [E.g., GRC platform] | [Manual tracking unsustainable at current scale] | $[amount]/yr | [Priority] | +| [E.g., External regulatory counsel] | [Specialist guidance required for [regulation]] | $[amount] | [Priority] | + +--- + +## Board-Level Risk Acknowledgments + +1. **[Risk]:** [E.g., "Company operates in [jurisdiction] without [license]. Management assesses risk as [level]. Board acknowledges and [approves / directs remediation by Date]."] +2. **[Risk]:** [E.g., "Data retention not yet compliant with [regulation]. Remediation target: [Date]. Board acknowledges interim exposure."] + +**Board action requested:** [Acknowledge report / Approve resource requests / Direct management action on [specific item]] + +--- + +*Report as of [Date]. Next update: [Date]. Material developments communicated within [X] business days of identification.* diff --git a/plugins/foreman/content/output-templates/board/risk-assessment-brief.md b/plugins/foreman/content/output-templates/board/risk-assessment-brief.md new file mode 100644 index 0000000..80ab19a --- /dev/null +++ b/plugins/foreman/content/output-templates/board/risk-assessment-brief.md @@ -0,0 +1,119 @@ +--- +name: "risk-assessment-brief" +description: "Produces an intelligence-style risk briefing for boards, structured as a ranked risk register with narrative context, early warning indicators, and mitigation strategies. Each risk is treated as a scenario with causal logic and actionable tripwires. Use when preparing board risk reviews, responding to emerging threats, or conducting periodic strategic risk assessments." +audience: "board" +applicable_skills: + - black-swans + - vuca-framework + - scenario-planning + - systems-thinking + - evaluating-options +format: "briefing" +author: "Fatih Guner" +--- + +# Risk Assessment Brief + +This briefing adopts the structure used by intelligence agencies when presenting strategic risk to senior decision-makers: ranked, concise, actionable. Each risk entry requires a narrative — probability/impact scores without context are theatre, not risk management. Replace all bracketed placeholders and delete this paragraph before distribution. + +## [Company Name] — Strategic Risk Brief + +**Classification:** Board Confidential | **Date:** [Date] | **Prepared by:** [Name, Title] +**Assessment period:** [Quarter/Year] | **Next review:** [Date] + +--- + +## Threat Level Summary + +**Overall risk posture: [ELEVATED / STABLE / REDUCED]** compared to prior assessment. [Two to three sentences. State what changed. Name the single risk warranting the most board attention.] + +## Probability-Impact Matrix + +| | **Low Impact** | **Medium Impact** | **High Impact** | **Critical Impact** | +|---|---|---|---|---| +| **High Probability** | | [Risk ID] | [Risk ID] | [Risk ID] | +| **Medium Probability** | | [Risk ID] | [Risk ID] | [Risk ID] | +| **Low Probability** | | | [Risk ID] | [Risk ID] | + +--- + +## Risk Register + +### RISK 1: [Title] — CRITICAL + +**Category:** [Strategic / Operational / Financial / Regulatory / Reputational / Technological] +**Probability:** [H/M/L] | **Impact:** [Critical/H/M/L] | **Velocity:** [Sudden / Rapid / Gradual] | **Trend:** [Increasing / Stable / Decreasing] + +**Narrative:** [Three to five sentences explaining mechanism, not label. "Competitive disruption" means nothing. "Competitor X's pricing eliminates our margin advantage in mid-market, representing 40% of revenue" means everything.] + +**Early warning indicators:** [Signal 1 — observable before materialisation] | [Signal 2 — leading, not lagging] | [Signal 3 — external source] +**Indicator status:** [Which are active, dormant, or newly appeared] + +| Mitigation Action | Owner | Status | Deadline | +|-------------------|-------|--------|----------| +| [Preventive — reduces probability] | [Name] | [Status] | [Date] | +| [Contingency — reduces impact] | [Name] | [Status] | [Date] | + +**Residual risk:** [What remains after mitigation. Honest residual assessment is a mark of governance maturity.] + +--- + +### RISK 2: [Title] — HIGH + +**Category:** [Category] | **Probability:** [Level] | **Impact:** [Level] | **Velocity:** [Speed] | **Trend:** [Direction] + +**Narrative:** [Three to five sentences. Same rigour as Risk 1.] + +**Early warning indicators:** [Signal 1] | [Signal 2] +**Indicator status:** [Assessment] + +| Mitigation Action | Owner | Status | Deadline | +|-------------------|-------|--------|----------| +| [Action 1] | [Name] | [Status] | [Date] | +| [Action 2] | [Name] | [Status] | [Date] | + +**Residual risk:** [Assessment] + +### RISK 3-5: [Repeat structure, scaling brevity with decreasing severity. A risk without indicators is a worry, not a managed risk.] + +--- + +## Black Swan Watch + +Improbable but non-survivable scenarios. These resist probability estimation and sit outside the matrix. They appear here because the board must know management has considered them. + +| Scenario | Potential Impact | Detection Difficulty | Preparedness | +|----------|-----------------|---------------------|-------------| +| [E.g., core technology obsoleted by regulation] | [Existential / Severe] | [H/M/L] | [None / Partial / Substantive] | +| [E.g., simultaneous departure of founding team] | [Level] | [H/M/L] | [Level] | + +**Board question:** For scenarios at "None" or "Partial" preparedness — does the board wish management to develop a contingency plan? + +--- + +## VUCA Assessment + +| Dimension | Prior | Current | Driver of Change | +|-----------|-------|---------|-----------------| +| **Volatility** | [H/M/L] | [H/M/L] | [Source of rapid, unpredictable change] | +| **Uncertainty** | [H/M/L] | [H/M/L] | [What is unknown and material] | +| **Complexity** | [H/M/L] | [H/M/L] | [Interconnections making prediction difficult] | +| **Ambiguity** | [H/M/L] | [H/M/L] | [What lacks clear interpretation despite data] | + +## Changes Since Last Brief + +| Risk | Change | Explanation | +|------|--------|-------------| +| [Risk name] | NEW | [Why it merits board attention] | +| [Risk name] | ESCALATED | [What changed] | +| [Risk name] | DE-ESCALATED | [What improved] | +| [Risk name] | RETIRED | [Why no longer material] | + +## Recommended Board Actions + +1. [Approve mitigation investment, convene special session, engage external counsel, or acknowledge assessment] +2. [Second priority action] + +--- + +*Assessment as of [date]. Material developments between reviews will be communicated within [X] business days of identification.* diff --git a/plugins/foreman/content/output-templates/client/analysis-report.md b/plugins/foreman/content/output-templates/client/analysis-report.md new file mode 100644 index 0000000..5569edf --- /dev/null +++ b/plugins/foreman/content/output-templates/client/analysis-report.md @@ -0,0 +1,202 @@ +--- +name: "analysis-report" +description: "Produces a professional strategic analysis report for external clients, partners, or board audiences. Structured as executive summary, methodology, findings with evidence, implications, recommendations, and next steps. Designed for McKinsey-grade rigor at operational speed. Use when delivering market analysis, competitive assessment, strategic review, or any evidence-based advisory output to an external audience." +audience: "client" +applicable_skills: + - porters-five-forces + - swot-pest-analysis + - business-model-canvas + - four-ps-marketing + - systems-thinking +format: "report" +author: "Fatih Guner" +--- + +# [Analysis Title] + +## Strategic Analysis Report + + + +**Prepared for:** [Client name / Organization] + +**Prepared by:** [Your name / Organization] | **Date:** [Date] + +**Classification:** [ ] Confidential [ ] Internal [ ] Public + +**Version:** [1.0] | **Status:** [ ] Draft [ ] Final + +--- + +## 1. Executive Summary + + + +**Context:** [Two to three sentences establishing why this analysis was undertaken. What question or decision prompted it?] + +**Key finding:** [The single most important conclusion. State it declaratively -- not "we found that it might be possible" but "the evidence indicates that X."] + +**Recommended action:** [One to two sentences. What should the reader do as a result of this analysis?] + +--- + +## 2. Scope and Methodology + +**Scope:** [What this analysis covers and, equally important, what it does not cover.] + +**Analytical frameworks applied:** + +| Framework | Purpose in this analysis | Section where applied | +|-----------|------------------------|----------------------| +| [e.g., Porter's Five Forces] | [What it assessed] | [Section reference] | +| [e.g., SWOT/PEST] | [What it assessed] | [Section reference] | +| [e.g., Business Model Canvas] | [What it assessed] | [Section reference] | + +**Data sources:** + +- [Source 1 -- type, date, reliability assessment] +- [Source 2 -- type, date, reliability assessment] +- [Source 3 -- type, date, reliability assessment] + +**Limitations:** [What constraints affect the reliability or completeness of this analysis? Acknowledging limitations builds credibility; concealing them destroys it.] + +--- + +## 3. Findings + +### Finding 1: [Headline -- declarative statement of what the evidence shows] + +**Evidence:** + +[Present the data, analysis, or observation that supports this finding. Use tables, figures, or structured comparisons where they add clarity.] + +| Dimension | Current state | Benchmark / Comparison | Implication | +|-----------|--------------|----------------------|-------------| +| [Metric or factor] | [Data] | [Industry average, competitor, or historical baseline] | [What this means] | +| [Metric or factor] | [Data] | [Comparison] | [What this means] | +| [Metric or factor] | [Data] | [Comparison] | [What this means] | + +**Confidence level:** [ ] High (multiple corroborating sources) [ ] Moderate (directionally reliable) [ ] Low (indicative only) + +--- + +### Finding 2: [Headline] + +**Evidence:** + +[Present supporting evidence. Vary the format from Finding 1 -- use a different structure to maintain reader engagement and match the nature of the evidence.] + +**Key data points:** + +- [Data point with source] -- significance: [Why this matters] +- [Data point with source] -- significance: [Why this matters] +- [Data point with source] -- significance: [Why this matters] + +**Comparative analysis:** + +[Narrative comparison or case study that contextualizes the data. Two to four sentences.] + +**Confidence level:** [ ] High [ ] Moderate [ ] Low + +--- + +### Finding 3: [Headline] + +**Evidence:** + +[Present supporting evidence. If appropriate, use a cause-and-effect or systems analysis structure here.] + +**Causal chain:** + +[Trigger event or condition] --> [Intermediate effect] --> [Observed outcome] --> [Projected consequence if unaddressed] + +**Supporting indicators:** + +1. [Indicator and source] +2. [Indicator and source] +3. [Indicator and source] + +**Confidence level:** [ ] High [ ] Moderate [ ] Low + + + +--- + +## 4. Implications + +_What do these findings mean for the client's strategic position, operations, and decisions?_ + +**Short-term implications (0-6 months):** + +- [Implication 1 -- derived from Finding(s) #X] +- [Implication 2 -- derived from Finding(s) #X] + +**Medium-term implications (6-18 months):** + +- [Implication 1 -- derived from Finding(s) #X] +- [Implication 2 -- derived from Finding(s) #X] + +**Long-term implications (18+ months):** + +- [Implication 1 -- derived from Finding(s) #X] + +**Scenarios:** + +| Scenario | Probability | Trigger | Impact on client | +|----------|------------|---------|-----------------| +| Optimistic | [%] | [What would cause this outcome] | [Effect] | +| Base case | [%] | [Most likely trajectory] | [Effect] | +| Pessimistic | [%] | [What would cause this outcome] | [Effect] | + +--- + +## 5. Recommendations + +_Each recommendation must trace back to a specific finding and implication. Recommendations without evidentiary support are opinions._ + +| # | Recommendation | Addresses finding | Priority | Effort | Expected impact | +|---|---------------|------------------|----------|--------|----------------| +| R1 | [Specific, actionable recommendation] | [Finding #] | [Critical / High / Medium] | [Low / Medium / High] | [Quantified if possible] | +| R2 | [Specific, actionable recommendation] | [Finding #] | [Critical / High / Medium] | [Low / Medium / High] | [Quantified if possible] | +| R3 | [Specific, actionable recommendation] | [Finding #] | [Critical / High / Medium] | [Low / Medium / High] | [Quantified if possible] | +| R4 | [Specific, actionable recommendation] | [Finding #] | [Critical / High / Medium] | [Low / Medium / High] | [Quantified if possible] | + +**Priority rationale:** [One to two sentences explaining why R1 is ranked first. Sequencing logic matters.] + +--- + +## 6. Next Steps + +| Step | Action | Owner | Timeline | Dependency | +|------|--------|-------|----------|-----------| +| 1 | [Immediate action -- e.g., "Schedule leadership alignment session to review findings"] | [Name / Role] | [Date] | [None / Prerequisite] | +| 2 | [Follow-up action -- e.g., "Commission detailed financial modeling for Recommendation R1"] | [Name / Role] | [Date] | [Step 1] | +| 3 | [Action] | [Name / Role] | [Date] | [Dependency] | +| 4 | [Action] | [Name / Role] | [Date] | [Dependency] | + +**Proposed follow-up:** [e.g., "A 60-minute review session in two weeks to discuss findings and align on recommendation prioritization."] + +--- + +## Appendices + + + +**Appendix A:** [Title -- e.g., "Detailed competitive landscape data"] + +**Appendix B:** [Title -- e.g., "Full PEST analysis matrix"] + +**Appendix C:** [Title -- e.g., "Interview and source log"] + +--- + +**Disclaimer:** [Standard professional disclaimer appropriate to the engagement -- e.g., "This analysis is based on information available as of [date]. Findings and recommendations should be validated against current conditions before implementation."] diff --git a/plugins/foreman/content/output-templates/client/case-study-template.md b/plugins/foreman/content/output-templates/client/case-study-template.md new file mode 100644 index 0000000..197e2ee --- /dev/null +++ b/plugins/foreman/content/output-templates/client/case-study-template.md @@ -0,0 +1,134 @@ +--- +name: "case-study-template" +description: "Produces a customer success story structured to convert prospects. Follows the challenge-solution-results arc that drives the highest-performing B2B content type. Includes result-focused headline, quantified before-and-after metrics, client quote placement, and distilled takeaways. Modeled on the case study formats that HubSpot, Salesforce, and Stripe use to close pipeline -- stripped of filler and built for credibility. Use after any engagement that produced measurable client outcomes worth documenting." +audience: "client" +applicable_skills: + - storytelling-for-leaders + - what-is-a-story + - story-structure-and-arc + - four-ps-marketing + - net-promoter-score +format: "case-study" +author: "Fatih Guner" +--- + +# [Result-Focused Headline] + + + +**[One-sentence summary that reinforces the headline and adds specificity.]** + + + +--- + +## Client Profile + +| Dimension | Detail | +|-----------|--------| +| **Company** | [Client name] | +| **Industry** | [Sector -- e.g., "B2B SaaS," "Healthcare logistics," "Financial services"] | +| **Company size** | [Employees, revenue range, or other relevant scale indicator] | +| **Geography** | [Markets served or headquarters location] | +| **Relationship** | [Client since YYYY / Engagement type -- e.g., "6-month strategic engagement"] | + +--- + +## The Challenge + + + +[Two to three paragraphs describing the situation the client faced before engagement. Include:] + +- The specific business problem (quantified where possible -- revenue lost, time wasted, opportunities missed) +- What the client had already tried and why it had not worked +- The constraints that made this problem particularly difficult (timeline pressure, resource limitations, technical complexity, organizational resistance) +- What was at stake if the problem remained unsolved + +**The core challenge in one sentence:** + +> [A single declarative statement -- e.g., "The company was losing $2.1M annually to a customer onboarding process that took 47 days and required manual intervention at 11 separate handoff points."] + +--- + +## The Solution + + + +**Approach:** + +[Two to three paragraphs describing what was implemented. Structure as a narrative, not a feature list. Cover:] + +- How the problem was diagnosed (what discovery revealed that the client had not seen) +- The solution design and why this approach was chosen over alternatives +- How implementation was sequenced (phased delivery reduces perceived risk for the prospect reading this) +- The client's role in the process (prospects want to understand what will be asked of them) + +**Key solution elements:** + +| Element | What it addressed | Why it mattered | +|---------|------------------|----------------| +| [Component 1 -- e.g., "Automated onboarding workflow"] | [Specific challenge dimension] | [Business rationale] | +| [Component 2 -- e.g., "Custom analytics dashboard"] | [Specific challenge dimension] | [Business rationale] | +| [Component 3 -- e.g., "Team training program"] | [Specific challenge dimension] | [Business rationale] | + +--- + +## The Results + + + +| Metric | Before | After | Change | Timeframe | +|--------|--------|-------|--------|-----------| +| [Primary outcome metric -- e.g., "Customer onboarding time"] | [47 days] | [12 days] | [74% reduction] | [Within 90 days] | +| [Secondary metric -- e.g., "Annual cost of onboarding"] | [$2.1M] | [$680K] | [$1.42M saved] | [Annualized] | +| [Tertiary metric -- e.g., "Customer satisfaction (NPS)"] | [+18] | [+52] | [+34 points] | [6-month measurement] | +| [Additional metric if available] | [Before] | [After] | [Change] | [Timeframe] | + +**Unexpected benefit:** + +[One to two sentences on a positive outcome the client did not anticipate. These details build authenticity -- they signal a real engagement, not a manufactured narrative.] + +--- + +## Client Quote + + + +> "[Direct quote from client stakeholder -- specific, results-oriented, and credible. Avoid generic praise like 'great to work with.' The best quotes reference a specific outcome or moment of realization.]" +> +> -- **[Full name]**, [Title], [Company] + +--- + +## Key Takeaways + +_Three lessons a prospect can extract without reading the full case study. Each should resonate with someone facing a similar challenge._ + +1. **[Takeaway headline]** -- [One sentence expanding on the insight. Connect it to a principle, not just this specific engagement.] + +2. **[Takeaway headline]** -- [One sentence. Frame it as applicable beyond this client's industry or scale.] + +3. **[Takeaway headline]** -- [One sentence. If possible, make the third takeaway address a common objection prospects raise.] + +--- + +**Want to discuss whether a similar approach could work for your situation?** + +[Contact name] | [Email] | [Phone or scheduling link] diff --git a/plugins/foreman/content/output-templates/client/onboarding-welcome-packet.md b/plugins/foreman/content/output-templates/client/onboarding-welcome-packet.md new file mode 100644 index 0000000..6756e22 --- /dev/null +++ b/plugins/foreman/content/output-templates/client/onboarding-welcome-packet.md @@ -0,0 +1,181 @@ +--- +name: "onboarding-welcome-packet" +description: "Produces a new client welcome document that bridges the gap between signed contract and productive working relationship. Covers a welcome message, first-30-days timeline, key contacts, getting-started steps, resources, communication norms, success metrics, frequently asked questions, and feedback channels. The tone is warm but professional -- a handshake, not a hug. Use immediately after contract execution to set expectations, reduce buyer's remorse, and accelerate time to first value." +audience: "client" +applicable_skills: + - writing-with-purpose + - writing-for-response + - writing-for-navigation + - tone-and-engagement + - trust-equation +format: "welcome-packet" +author: "Fatih Guner" +--- + +# Welcome to [Your Organization Name] + + + +**Prepared for:** [Client organization name] + +**Date:** [Date] + +**Your account team:** [Primary contact name and title] + +--- + +## Welcome + +[Client name], + +Thank you for choosing [Your Organization]. The decision to work together represents the beginning of a partnership built on [one specific value proposition -- e.g., "delivering measurable operational improvement," "accelerating your go-to-market strategy," "providing the technical infrastructure your growth demands"]. + +This document covers everything you need for a smooth start: who to contact, what happens in the first 30 days, and how we will measure whether this partnership is working. Keep it accessible -- your team will reference it often in the early weeks. + +We are committed to earning the confidence you have placed in us. The best client relationships are built on transparency from day one, and this packet is our first step toward that standard. + +--- + +## What to Expect: Your First 30 Days + +| Timeframe | What happens | Your involvement | Outcome | +|-----------|-------------|-----------------|---------| +| **Days 1-3** | Kickoff call and account setup | Attend kickoff; confirm key contacts and access credentials | Aligned on scope, timeline, and communication norms | +| **Days 4-7** | Discovery and environment review | Provide access to systems, documentation, and stakeholders as requested | Shared understanding of current state and integration requirements | +| **Days 8-14** | Initial configuration and onboarding sessions | Attend onboarding training; designate internal champions | Team enabled on core workflows and primary use cases | +| **Days 15-21** | Guided implementation of first deliverables | Apply workflows to real work with our support available | First tangible value delivered; early feedback collected | +| **Days 22-30** | 30-day review and optimization | Attend review meeting; share candid feedback | Baseline metrics established; adjustments made; next-phase plan confirmed | + +**Milestone:** By day 30, your team should be operating independently on core workflows, with a clear view of the value delivered and the roadmap ahead. + +--- + +## Key Contacts + +_Who to reach for what. Save this table -- it eliminates the most common source of early-stage friction: not knowing whom to call._ + +| Role | Name | Responsibility | Email | Phone | Best for | +|------|------|---------------|-------|-------|----------| +| Account Manager | [Name] | Overall relationship, escalations, strategic alignment | [Email] | [Phone] | Questions about scope, contract, or relationship concerns | +| Project Lead | [Name] | Day-to-day delivery, timeline, and milestone tracking | [Email] | [Phone] | Implementation questions, scheduling, deliverable status | +| Technical Contact | [Name] | Technical setup, integrations, and troubleshooting | [Email] | [Phone] | System access, configuration, technical issues | +| Support Team | [Team / Name] | Ongoing issue resolution and service requests | [Email / Portal URL] | [Phone] | Bugs, incidents, and how-to questions after onboarding | +| Executive Sponsor | [Name] | Senior oversight and escalation path | [Email] | [By appointment] | Unresolved issues that require leadership attention | + +**After hours:** [Emergency contact method for critical issues outside business hours -- e.g., "For urgent matters outside 09:00-18:00 [timezone], email [address] with 'URGENT' in the subject line. Response within 60 minutes."] + +--- + +## Getting Started + +_Complete these steps in order. Each builds on the previous one._ + +1. **Confirm your kickoff meeting.** Check your calendar for the invitation sent to [email/calendar system]. If you do not see it within 24 hours of receiving this packet, contact [Project Lead name] at [email]. Attendees should include: [list recommended roles -- e.g., "your project sponsor, day-to-day point of contact, and technical lead"]. + +2. **Designate your internal champions.** Identify one to two people on your team who will serve as primary users and internal advocates during onboarding. Share their names and contact details with [Project Lead name] so we can tailor training to their workflows. + +3. **Provide system access.** We will send a secure access request form within 48 hours of contract execution. Complete it promptly -- access provisioning is the most common cause of onboarding delays. + +4. **Review the scope document.** Revisit the agreed scope of work attached to your contract. Flag any questions or clarifications before the kickoff meeting so we can address them immediately rather than carrying ambiguity into the project. + +5. **Set up your communication channels.** Join [communication platform -- e.g., "the dedicated Slack channel," "the shared project workspace," "the client portal at [URL]"]. This is where day-to-day communication will happen between scheduled meetings. + +6. **Prepare your onboarding team.** Block calendar time for the training sessions outlined in the first-30-days timeline above. Attendance in the first two weeks directly correlates with adoption speed -- teams that skip onboarding sessions consistently take 2-3x longer to reach proficiency. + +--- + +## Resources and Documentation + +| Resource | Description | Access | +|----------|-------------|--------| +| Client portal | Central hub for project status, documents, and support requests | [URL] -- credentials provided during kickoff | +| Knowledge base | Self-service documentation, guides, and FAQs | [URL] | +| Training materials | Recorded sessions, tutorials, and reference guides | [URL or "Available after onboarding sessions"] | +| Scope of work | Agreed deliverables, timeline, and success criteria | [Attached to contract / Available in portal] | +| Support request form | How to submit issues and service requests | [URL or process description] | + +--- + +## Communication Preferences + +_How and when we will communicate. Clear norms prevent the two extremes: silence that breeds anxiety and over-communication that consumes your calendar._ + +| Communication type | Channel | Frequency | Owner | +|-------------------|---------|-----------|-------| +| Status updates | [e.g., Email summary] | [e.g., Weekly, every Friday by 17:00] | [Your team] | +| Working sessions | [e.g., Video call] | [e.g., Biweekly, 60 minutes] | [Joint] | +| Ad hoc questions | [e.g., Slack / Teams / Email] | [As needed -- response within X business hours] | [Either party] | +| Strategic review | [e.g., In-person or video] | [e.g., Quarterly] | [Account Manager] | +| Escalations | [e.g., Phone + email to Account Manager] | [As needed -- acknowledgment within 2 hours] | [Client-initiated] | + +**Our response commitment:** Routine questions answered within [X] business hours. Urgent matters acknowledged within [X] hours. + +**What we ask of you:** Timely responses to requests for access, approvals, and feedback. Delays on your side cascade into the project timeline -- we will flag dependencies early to avoid surprises. + +--- + +## Success Metrics + +_How we will measure whether this partnership is working. These metrics are established jointly during the kickoff meeting and reviewed at the 30-day and quarterly checkpoints._ + +| # | Metric | Baseline (current state) | Target (by [date]) | Measurement method | +|---|--------|------------------------|--------------------|-------------------| +| 1 | [e.g., Time to resolve support tickets] | [Current value] | [Target value] | [How we measure -- tool, report, manual review] | +| 2 | [e.g., User adoption rate] | [Current value] | [Target value] | [Measurement method] | +| 3 | [e.g., Cost per transaction] | [Current value] | [Target value] | [Measurement method] | +| 4 | [Client-specific KPI] | [Current value] | [Target value] | [Measurement method] | + +**First value milestone:** [What specific outcome the client should experience within the first 30 days that confirms the engagement is on track -- e.g., "First automated report generated and reviewed by your team."] + +--- + +## Frequently Asked Questions + +**1. What if we need to change the scope after we start?** + +Scope changes happen. We handle them through a documented change request process: you describe what you need, we assess impact on timeline and cost, and both parties agree in writing before work begins. Minor adjustments within the spirit of the original scope are absorbed without formality. + +**2. What happens if something goes wrong?** + +Contact your Account Manager directly. If the issue is technical and urgent, use the support channel listed in the Key Contacts section. For unresolved concerns, the escalation path runs from Project Lead to Account Manager to Executive Sponsor. We would rather hear about a problem early than discover it late. + +**3. How long does onboarding typically take?** + +Most clients are operating independently on core workflows within 30 days. Complex implementations with significant integrations or large user bases may extend to 45-60 days. Your Project Lead will provide a tailored timeline during kickoff. + +**4. Can we add more users or services later?** + +Yes. Expansion is straightforward -- contact your Account Manager to discuss additional capacity, and we will provide a proposal within [X] business days. + +**5. What if we are not satisfied with the service?** + +Raise it immediately. The quarterly business review is the formal checkpoint, but feedback is welcome at any time. Our goal is to address concerns before they become grievances. The feedback channel below exists precisely for this purpose. + +--- + +## Feedback Channel + +_A partnership that discourages feedback is a vendor relationship pretending to be more. We want to hear what is working and what is not -- especially what is not._ + +**How to share feedback:** + +- **Informal:** Message your Account Manager or Project Lead directly at any time +- **Formal:** [Feedback form URL or email -- e.g., "feedback@yourcompany.com"] -- reviewed weekly by the account team +- **Structured:** Quarterly business review includes a dedicated feedback session +- **Anonymous (if preferred):** [Anonymous survey URL, if available] + +**Our commitment:** Every piece of substantive feedback receives a response within [e.g., 5 business days] -- either an action taken, a plan to address it, or an honest explanation of why we cannot. + +--- + +**Your Account Manager:** [Name] | [Email] | [Phone] + +**We look forward to working with you.** diff --git a/plugins/foreman/content/output-templates/client/partnership-memo.md b/plugins/foreman/content/output-templates/client/partnership-memo.md new file mode 100644 index 0000000..d07327c --- /dev/null +++ b/plugins/foreman/content/output-templates/client/partnership-memo.md @@ -0,0 +1,210 @@ +--- +name: "partnership-memo" +description: "Produces a structured partnership proposal memo for strategic alliances, joint ventures, co-development agreements, and channel partnerships. Distinct from the general proposal-outline (which sells a service), this template frames a relationship where both parties build, invest, and share risk together. Covers shared opportunity, complementary strengths, proposed structure, success metrics, risk allocation, governance, milestones, and exit provisions. Modeled on partnership frameworks from Stripe-level BD organizations. Use when proposing a 'let's build together' arrangement rather than a buyer-seller transaction." +audience: "client" +applicable_skills: + - coalition-and-partnership-games + - cooperative-negotiation + - win-win-negotiation + - trust-equation + - negotiation-game-theory +format: "memo" +author: "Fatih Guner" +--- + +# Partnership Proposal Memo + +**To:** [Partner organization / Decision-maker name and title] + +**From:** [Your organization / Your name and title] + +**Date:** [Date] | **Classification:** [ ] Confidential [ ] Internal [ ] Draft for discussion + +**Subject:** Proposed strategic partnership between [Your organization] and [Partner organization] + +--- + + + +## 1. Shared Opportunity + + + +[Three to four paragraphs describing the market opportunity, customer need, or strategic gap that neither organization can fully capture alone. Address:] + +- The opportunity and its scale (quantified where possible -- market size, customer segment, revenue potential, competitive timing) +- Why this opportunity requires partnership rather than independent pursuit +- What happens if neither party acts (the cost of inaction for both sides) +- Why now -- the timing catalyst that makes this conversation urgent rather than theoretical + +**The partnership thesis in one sentence:** + +> [e.g., "By combining [Your org]'s distribution reach with [Partner]'s technical platform, we can capture [X% / $X] of the [specific market segment] within [timeframe] -- an outcome neither organization can achieve independently."] + +--- + +## 2. Complementary Strengths + +_What each side brings. The strongest partnerships are asymmetric in capability and symmetric in commitment._ + +| Dimension | [Your organization] brings | [Partner organization] brings | +|-----------|--------------------------|------------------------------| +| **Core capability** | [Your primary strength relevant to this partnership] | [Their primary strength] | +| **Customer access** | [Your market reach, channels, or relationships] | [Their market reach, channels, or relationships] | +| **Technology / IP** | [Your technical assets] | [Their technical assets] | +| **Brand / Credibility** | [Your brand equity in the target market] | [Their brand equity] | +| **Operational capacity** | [Your ability to execute, scale, or support] | [Their ability to execute, scale, or support] | +| **Geographic reach** | [Your coverage] | [Their coverage] | +| **Capital / Resources** | [What you can invest] | [What they can invest] | + +**The strategic logic:** [Two to three sentences explaining why these strengths are complementary rather than overlapping. Overlap creates friction; complementarity creates leverage.] + +--- + +## 3. Proposed Structure + + + +**Partnership type:** [ ] Strategic alliance [ ] Joint venture [ ] Co-development agreement [ ] Channel/distribution partnership [ ] Revenue share [ ] Other: [Describe] + +**Roles and responsibilities:** + +| Function | [Your organization] | [Partner organization] | Shared | +|----------|--------------------|-----------------------|--------| +| Product / Solution development | [Scope] | [Scope] | [If any] | +| Sales and business development | [Scope] | [Scope] | [If any] | +| Marketing and positioning | [Scope] | [Scope] | [If any] | +| Customer delivery and support | [Scope] | [Scope] | [If any] | +| Operations and infrastructure | [Scope] | [Scope] | [If any] | +| Legal, compliance, regulatory | [Scope] | [Scope] | [If any] | + +**Economics:** + +- **Revenue model:** [How revenue is generated -- subscription, transaction fee, licensing, services] +- **Revenue allocation:** [Proposed split or formula -- e.g., "60/40 based on customer origination" or "Tiered: first $X at Y%, above $X at Z%"] +- **Cost sharing:** [Which costs each party bears -- development, marketing, support, infrastructure] +- **Investment required:** [From each party -- capital, headcount, technology, time] +- **Exclusivity:** [ ] Non-exclusive [ ] Exclusive in [defined segment/geography] [ ] Right of first refusal in [domain] + +--- + +## 4. Success Metrics + +_A partnership without shared metrics is a handshake without a contract. Define what "working" looks like before you begin._ + +| Metric | Target (Year 1) | Measurement method | Review frequency | +|--------|-----------------|-------------------|-----------------| +| [Primary revenue or growth metric] | [Specific target] | [How measured] | [Monthly / Quarterly] | +| [Customer or market metric] | [Specific target] | [How measured] | [Frequency] | +| [Operational efficiency metric] | [Specific target] | [How measured] | [Frequency] | +| [Relationship health metric -- e.g., partner NPS, escalation rate] | [Target] | [How measured] | [Frequency] | + +**Minimum viability threshold:** [The point below which the partnership is not delivering sufficient value to justify continuation -- e.g., "If joint revenue does not reach $X by month 12, either party may invoke the review clause."] + +--- + +## 5. Risk Sharing + +_Partnerships fail when risks are unacknowledged or asymmetrically borne. Name them now._ + +| Risk | Probability | Impact | Who bears it | Mitigation | +|------|------------|--------|-------------|-----------| +| [Market risk -- e.g., demand does not materialize] | [H / M / L] | [H / M / L] | [Shared / Primarily X] | [How reduced] | +| [Execution risk -- e.g., development delays] | [H / M / L] | [H / M / L] | [Who bears cost of delay] | [How reduced] | +| [Reputational risk -- e.g., quality failure reflects on both brands] | [H / M / L] | [H / M / L] | [Shared] | [Quality gates, approval processes] | +| [Competitive risk -- e.g., partner enters our core market independently] | [H / M / L] | [H / M / L] | [Your org] | [Contractual protections] | +| [Dependency risk -- e.g., one party cannot deliver on commitments] | [H / M / L] | [H / M / L] | [The non-defaulting party] | [Performance milestones, cure periods] | + +--- + +## 6. Governance + +_How decisions get made. How disputes get resolved. The governance structure you skip in enthusiasm is the structure you need in conflict._ + +**Decision authority:** + +| Decision type | Authority | Approval required | +|--------------|-----------|------------------| +| Day-to-day operational decisions | [Each party within their scope] | [None] | +| Joint marketing and positioning | [Named role from each side] | [Mutual approval] | +| Pricing changes affecting the partnership | [Named role] | [Mutual approval with X-day notice] | +| Scope changes or new investment | [Steering committee] | [Unanimous] | +| Partnership renewal or termination | [Executive sponsors] | [Per exit provisions below] | + +**Governance structure:** + +- **Executive sponsors:** [Name/Title from each org -- ultimate accountability] +- **Operating leads:** [Name/Title from each org -- day-to-day management] +- **Steering committee:** [Composition] -- meets [frequency] +- **Escalation path:** [Operating leads --> Executive sponsors --> Mediation if needed] + +**Dispute resolution:** + +1. Good-faith negotiation between operating leads (5 business days) +2. Escalation to executive sponsors (10 business days) +3. [Mediation / Arbitration / Other] in [jurisdiction] if unresolved + +--- + +## 7. Timeline and Milestones + +| Phase | Milestone | Target date | Owner | Gate | +|-------|-----------|------------|-------|------| +| **Alignment** | Memo reviewed, intent confirmed | [Date] | [Both] | Go / No-go on detailed planning | +| **Negotiation** | Terms finalized, agreement drafted | [Date] | [Both + legal] | Contract execution | +| **Launch preparation** | Integration complete, teams trained, marketing prepared | [Date] | [Assigned leads] | Launch readiness review | +| **Market launch** | Partnership goes live to customers | [Date] | [Assigned leads] | -- | +| **First review** | 90-day performance assessment | [Date] | [Steering committee] | Continue / Adjust / Escalate | +| **Annual review** | Full partnership health assessment | [Date] | [Executive sponsors] | Renew / Restructure / Exit | + +**Total time from agreement to market:** [Estimated X weeks/months] + +--- + +## 8. Exit Provisions + +_Every partnership needs a clear, dignified exit path. Discussing exit terms at the outset is not pessimism -- it is the foundation of trust._ + +**Term:** [Initial duration -- e.g., "24 months from launch date"] + +**Renewal:** [ ] Auto-renewal for [X-month] periods unless either party provides [X-day] written notice [ ] Requires affirmative renewal by both parties + +**Termination triggers:** + +- Either party may terminate with [X days] written notice without cause +- Immediate termination for material breach, subject to [X-day] cure period +- Termination if minimum viability threshold (Section 4) is not met by [date] + +**Post-termination obligations:** + +- Customer transition plan: [How active customers are handled] +- IP and data: [What each party retains, what is returned or destroyed] +- Non-compete / Non-solicit: [Duration and scope, if any] +- Revenue wind-down: [How in-flight revenue or commitments are honored] + +--- + +## Next Steps + +| Step | Action | Owner | By when | +|------|--------|-------|---------| +| 1 | Review this memo and confirm alignment on strategic intent | [Partner] | [Date] | +| 2 | Schedule working session to refine economics and governance | [Both] | [Date] | +| 3 | Engage legal counsel to draft formal agreement | [Both] | [Date] | +| 4 | Designate executive sponsors and operating leads | [Both] | [Date] | + +--- + +**Primary contact:** [Name] | [Title] | [Email] | [Phone] + +**This memo reflects a proposal for discussion and does not constitute a binding commitment. Formal terms will be established through a definitive agreement executed by authorized representatives of both organizations.** diff --git a/plugins/foreman/content/output-templates/client/project-status-update.md b/plugins/foreman/content/output-templates/client/project-status-update.md new file mode 100644 index 0000000..85a0b4e --- /dev/null +++ b/plugins/foreman/content/output-templates/client/project-status-update.md @@ -0,0 +1,137 @@ +--- +name: "project-status-update" +description: "Produces a concise project status report for clients, partners, or + internal stakeholders. Covers overall status (RAG rating), progress since last + update, upcoming milestones, blockers and risks, decisions needed, and + budget/timeline tracking. Designed to be completed in 15 minutes and read in + 3. The operating principle: no surprises. A stakeholder who reads this report + consistently should never be blindsided by a problem that was already known. + Use weekly or biweekly for any active engagement." +audience: "client" +applicable_skills: + - smart-goals + - writing-for-navigation + - writing-for-response + - balanced-scorecard +format: "status-report" +author: "Fatih Guner" +related_content: + - kind: template + ref: action-plan +--- + +# Project Status Update + + + +**Project:** [Project name] + +**Client / Stakeholder:** [Organization and primary contact] + +**Prepared by:** [Your name] | **Date:** [Date] + +**Reporting period:** [From date -- To date] + +**Next update:** [Date] + +--- + +## Project Summary + +[One sentence. What this project delivers and for whom. The same sentence every update -- consistency allows readers to skip it once familiar and jump to what changed.] + +--- + +## Overall Status + +| Dimension | Status | One-sentence explanation | +|-----------|--------|------------------------| +| **Overall** | [ ] Green [ ] Amber [ ] Red | [Why this rating. Be direct.] | +| **Timeline** | [ ] On track [ ] At risk [ ] Off track | [Current state relative to plan] | +| **Budget** | [ ] On track [ ] At risk [ ] Off track | [Current state relative to plan] | +| **Scope** | [ ] Stable [ ] Minor changes [ ] Significant changes | [Any scope movement since last report] | +| **Quality** | [ ] Meeting standards [ ] Concerns noted [ ] Below standards | [Assessment basis] | + +**Status change from last update:** [ ] Unchanged [ ] Improved -- [from what to what] [ ] Degraded -- [from what to what, and why] + +--- + +## Progress Since Last Update + +_Completed items only. If it is in progress, it goes in the next section._ + +- [x] [Completed item -- concrete deliverable or milestone, not activity] +- [x] [Completed item] +- [x] [Completed item] +- [x] [Completed item] + + + +--- + +## Upcoming Milestones + +_The next 2 weeks. Further-out milestones belong in the project plan, not the status report._ + +| Milestone | Target date | Owner | Status | Confidence | +|-----------|------------|-------|--------|-----------| +| [Next deliverable or decision point] | [Date] | [Name] | [Not started / In progress / At risk] | [High / Medium / Low] | +| [Milestone] | [Date] | [Name] | [Status] | [Confidence] | +| [Milestone] | [Date] | [Name] | [Status] | [Confidence] | + +--- + +## Blockers and Risks + +_Blockers are stopping work now. Risks may stop work later. The distinction matters for urgency._ + +**Active blockers:** + +| # | Blocker | Impact | Owner | Resolution path | Target resolution date | +|---|---------|--------|-------|----------------|----------------------| +| B1 | [What is blocked and why] | [What cannot proceed until resolved] | [Name] | [Proposed or in-progress resolution] | [Date] | +| B2 | [Blocker] | [Impact] | [Name] | [Path] | [Date] | + +**Risks being monitored:** + +| # | Risk | Probability | Impact | Mitigation | Trigger to escalate | +|---|------|------------|--------|-----------|-------------------| +| R1 | [What could go wrong] | [H / M / L] | [H / M / L] | [What is being done to reduce likelihood or impact] | [Condition that converts this risk into a blocker] | +| R2 | [Risk] | [Probability] | [Impact] | [Mitigation] | [Trigger] | + +_If there are no blockers or risks, state "None" explicitly. Silence is ambiguous; "None" is a professional assessment._ + +--- + +## Decisions Needed + +_Decisions that require client or stakeholder input. Each one should state what is needed, why it matters, and by when -- so the reader can act immediately._ + +| # | Decision required | Context | Options | Needed by | Impact of delay | +|---|------------------|---------|---------|-----------|----------------| +| D1 | [Specific decision -- e.g., "Approve revised data migration approach"] | [Why this decision is necessary now] | [Option A / Option B / Other] | [Date] | [What slips or degrades if delayed] | +| D2 | [Decision] | [Context] | [Options] | [Date] | [Impact] | + +_If no decisions are needed, state "No decisions required this period."_ + +--- + +## Budget and Timeline Tracking + +| Dimension | Planned | Actual / Forecast | Variance | Notes | +|-----------|---------|------------------|----------|-------| +| **Total budget** | [$X] | [$X spent / $X forecast] | [On track / +X% / -X%] | [Explanation if variance exceeds 5%] | +| **Hours consumed** | [X of Y total] | [X%] | [Ahead / On pace / Behind] | | +| **End date** | [Original date] | [Current forecast] | [On time / +X days / -X days] | [Reason if shifted] | + +--- + +**Distribution:** [Names of recipients] + +**Questions or concerns:** Contact [Name] at [email] or [phone] diff --git a/plugins/foreman/content/output-templates/client/proposal-outline.md b/plugins/foreman/content/output-templates/client/proposal-outline.md new file mode 100644 index 0000000..7ac6229 --- /dev/null +++ b/plugins/foreman/content/output-templates/client/proposal-outline.md @@ -0,0 +1,178 @@ +--- +name: "proposal-outline" +description: "Produces a structured business proposal skeleton adaptable for partnerships, client pitches, vendor engagements, or internal investment requests. Covers problem statement, proposed solution, value proposition, methodology, timeline, investment, expected ROI, risk mitigation, credentials, and next steps. Use when you need to persuade a decision-maker to commit resources, approve a partnership, or select your organization." +audience: "client" +applicable_skills: + - blue-ocean-strategy + - doblin-ten-types + - business-model-canvas + - four-ps-marketing + - writing-with-purpose +format: "proposal" +author: "Fatih Guner" +--- + +# [Proposal Title] + +**Submitted to:** [Organization / Decision-maker name] + +**Submitted by:** [Your organization] | **Contact:** [Name, title, email, phone] + +**Date:** [Date] | **Valid until:** [Expiration date -- proposals without deadlines lose urgency] + +**Reference:** [RFP number, project code, or conversation reference if applicable] + +--- + +## 1. Problem Statement + + + +[Two to three paragraphs. Describe the challenge, opportunity, or gap the client faces. Demonstrate that you understand the problem at a level equal to or deeper than the client's own understanding. Cite specific conditions, market forces, or operational realities that make this problem urgent now rather than theoretical. Do not mention your solution yet -- earn the right to propose it by proving you grasp what needs solving.] + +**The cost of inaction:** [One to two sentences quantifying or qualifying what happens if the client does nothing. Make the status quo uncomfortable.] + +## 2. Proposed Solution + +**In one sentence:** [What you propose to do. Clear enough to repeat from memory.] + +**Solution architecture:** + +[Three to five paragraphs describing the solution. Structure this as a narrative, not a feature list. Explain what you will deliver, how it addresses the problem described in Section 1, and what makes this approach distinct from alternatives the client may be considering. Connect each element of the solution back to a specific dimension of the problem.] + +**Key differentiators:** + +| Dimension | Typical approach | Our approach | Why it matters | +|-----------|-----------------|-------------|---------------| +| [e.g., Speed to value] | [What competitors or alternatives typically deliver] | [What you deliver differently] | [Client benefit] | +| [e.g., Methodology] | [Standard practice] | [Your distinct method] | [Client benefit] | +| [e.g., Ongoing support] | [Industry norm] | [Your commitment] | [Client benefit] | + +## 3. Value Proposition + +_Why this solution, from this team, at this time._ + +**For the organization:** +- [Quantified business impact -- revenue, cost reduction, risk mitigation, speed] +- [Strategic benefit -- market position, capability building, competitive advantage] + +**For the decision-maker:** +- [What approving this proposal achieves for them professionally] +- [What risk it mitigates for their function or division] + +**For end users / stakeholders:** +- [Operational improvement they will experience] +- [How their daily work or outcomes change] + +## 4. Approach and Methodology + +**Phase structure:** + +### Phase 1: [Name -- e.g., "Discovery and Alignment"] +- **Duration:** [Weeks] +- **Activities:** [Specific work to be performed] +- **Deliverables:** [Tangible outputs] +- **Client involvement required:** [What you need from them] + +### Phase 2: [Name -- e.g., "Design and Development"] +- **Duration:** [Weeks] +- **Activities:** [Specific work to be performed] +- **Deliverables:** [Tangible outputs] +- **Client involvement required:** [What you need from them] + +### Phase 3: [Name -- e.g., "Implementation and Transition"] +- **Duration:** [Weeks] +- **Activities:** [Specific work to be performed] +- **Deliverables:** [Tangible outputs] +- **Client involvement required:** [What you need from them] + + + +**Quality assurance:** [How you ensure deliverable quality -- review gates, testing protocols, client sign-off points] + +## 5. Timeline + +| Milestone | Target date | Gate / Decision point | +|-----------|------------|----------------------| +| Proposal accepted, contract signed | [Date] | Go / No-go | +| Phase 1 kickoff | [Date] | -- | +| Phase 1 deliverables complete | [Date] | Client review and approval | +| Phase 2 kickoff | [Date] | -- | +| Phase 2 deliverables complete | [Date] | Client review and approval | +| Phase 3 kickoff | [Date] | -- | +| Final deliverables and transition | [Date] | Project close | +| Post-implementation review | [Date] | Impact assessment | + +**Total duration:** [X weeks/months from contract signature to completion] + +## 6. Investment + +| Component | Description | Amount | +|-----------|------------|--------| +| [Phase 1 / Discovery] | [Scope summary] | [$amount] | +| [Phase 2 / Development] | [Scope summary] | [$amount] | +| [Phase 3 / Implementation] | [Scope summary] | [$amount] | +| [Ongoing support / Retainer] | [If applicable] | [$amount / period] | +| **Total** | | **[$total]** | + +**Payment terms:** [e.g., "30% upon contract signature, 40% at Phase 2 completion, 30% at final delivery"] + +**What is included:** [Travel, materials, licenses, support hours, revisions -- be explicit] + +**What is not included:** [Scope boundaries -- name them now to prevent disputes later] + +## 7. Expected Return on Investment + +| Metric | Current state | Projected state (post-implementation) | Improvement | Timeframe to realize | +|--------|--------------|--------------------------------------|-------------|---------------------| +| [e.g., Revenue per customer] | [$X] | [$Y] | [+Z%] | [Months] | +| [e.g., Operational cost] | [$X] | [$Y] | [-Z%] | [Months] | +| [e.g., Time to market] | [X weeks] | [Y weeks] | [-Z weeks] | [Months] | + +**Payback period:** [When the investment is recovered based on projected gains] + +**Conservative estimate:** [ROI if only 50-70% of projected benefits materialize -- this builds credibility] + +## 8. Risk Mitigation + +| Risk | Probability | Impact | Our mitigation approach | +|------|------------|--------|------------------------| +| [e.g., Scope expansion beyond agreed boundaries] | [H / M / L] | [H / M / L] | [Change control process with defined approval gates] | +| [e.g., Key personnel unavailability] | [H / M / L] | [H / M / L] | [Named backups for all critical roles] | +| [e.g., Technology or integration challenges] | [H / M / L] | [H / M / L] | [Proof of concept in Phase 1 before full commitment] | +| [e.g., Adoption resistance from stakeholders] | [H / M / L] | [H / M / L] | [Change management activities built into Phase 3] | + +## 9. Team and Credentials + +**Proposed team:** + +| Role | Name | Relevant experience | Availability | +|------|------|-------------------|-------------| +| [Project lead / Partner] | [Name] | [Two-sentence summary of relevant expertise] | [% dedicated] | +| [Senior specialist] | [Name] | [Relevant expertise] | [% dedicated] | +| [Analyst / Associate] | [Name] | [Relevant expertise] | [% dedicated] | + +**Relevant experience:** + +- **[Client / Project 1]:** [One to two sentences describing the engagement and outcome achieved] +- **[Client / Project 2]:** [One to two sentences describing the engagement and outcome achieved] +- **[Client / Project 3]:** [One to two sentences describing the engagement and outcome achieved] + +**References available upon request:** [ ] Yes [ ] Included in appendix + +## 10. Next Steps + +| Step | Action | Owner | By when | +|------|--------|-------|---------| +| 1 | [e.g., "Review this proposal and provide feedback or questions"] | [Client] | [Date] | +| 2 | [e.g., "Schedule a 45-minute presentation and Q&A session"] | [Your team] | [Date] | +| 3 | [e.g., "Finalize scope and commercial terms"] | [Both parties] | [Date] | +| 4 | [e.g., "Execute agreement and schedule kickoff"] | [Both parties] | [Date] | + +--- + +**Primary contact:** [Name] | [Email] | [Phone] + +**This proposal is confidential and intended solely for the use of [Client name]. The contents, methodology, and pricing are proprietary and should not be shared with third parties without written consent.** diff --git a/plugins/foreman/content/output-templates/client/quarterly-business-review.md b/plugins/foreman/content/output-templates/client/quarterly-business-review.md new file mode 100644 index 0000000..1c068a7 --- /dev/null +++ b/plugins/foreman/content/output-templates/client/quarterly-business-review.md @@ -0,0 +1,212 @@ +--- +name: "quarterly-business-review" +description: "Produces a quarterly business review document for client relationship management. Covers account health scoring, value delivered against targets, service utilization, support analysis, roadmap alignment, expansion opportunities, renewal risks, strategic recommendations, next-quarter plan, and client feedback capture. The document that surfaces problems before they become cancellation emails. Use to prepare for QBR meetings with key accounts, retain high-value clients, and transform transactional vendor relationships into strategic partnerships." +audience: "client" +applicable_skills: + - net-promoter-score + - balanced-scorecard + - four-ps-marketing + - strategic-thinking-and-alignment + - writing-for-response +format: "review" +author: "Fatih Guner" +--- + +# Quarterly Business Review + + + +**Client:** [Organization name] + +**Review period:** [Q_ YYYY] + +**Meeting date:** [Date] | **Location / Format:** [In-person / Video] + +**Prepared by:** [Name, title] | **Account team:** [Names] + +**Client attendees:** [Names and roles] + +--- + +## 1. Relationship Summary + +### Account Health Score + +| Dimension | Score (1-10) | Trend vs. last quarter | Notes | +|-----------|-------------|----------------------|-------| +| Value realization | [Score] | [Up / Flat / Down] | [Are they getting what they paid for?] | +| Engagement quality | [Score] | [Trend] | [Responsiveness, meeting attendance, executive access] | +| Support satisfaction | [Score] | [Trend] | [Ticket resolution, escalation frequency, sentiment] | +| Strategic alignment | [Score] | [Trend] | [Does our roadmap serve their direction?] | +| Relationship depth | [Score] | [Trend] | [Multi-threaded contacts vs. single point of failure] | +| **Overall health** | **[Weighted avg]** | **[Trend]** | | + +**Health classification:** [ ] Thriving [ ] Healthy [ ] At risk [ ] Critical + +**One-sentence assessment:** [e.g., "Value delivery is strong but engagement has narrowed to a single champion, creating concentration risk if that contact changes roles."] + +--- + +## 2. Value Delivered This Quarter + +_Present outcomes, not activities. The client did not buy your hours -- they bought results._ + +### Key Metrics + +| Metric | Baseline (start of engagement or prior quarter) | Target | Actual this quarter | Delta vs. target | Delta vs. baseline | +|--------|-----------------------------------------------|--------|-------------------|-----------------|-------------------| +| [e.g., Revenue influenced] | [Value] | [Value] | [Value] | [+/- %] | [+/- %] | +| [e.g., Cost reduction achieved] | [Value] | [Value] | [Value] | [+/- %] | [+/- %] | +| [e.g., Time to resolution] | [Value] | [Value] | [Value] | [+/- %] | [+/- %] | +| [e.g., Customer satisfaction score] | [Value] | [Value] | [Value] | [+/- pts] | [+/- pts] | +| [Custom KPI for this account] | [Value] | [Value] | [Value] | [Delta] | [Delta] | + +### Highlights + +1. **[Achievement]** -- [Quantified impact and what it means for the client's business] +2. **[Achievement]** -- [Impact] +3. **[Achievement]** -- [Impact] + +### Misses + +_Name them before the client does. Owning shortfalls builds more trust than concealing them._ + +1. **[Miss]** -- Root cause: [Explanation] | Corrective action: [What has changed to prevent recurrence] +2. **[Miss]** -- Root cause: [Explanation] | Corrective action: [Action taken] + +--- + +## 3. Service Utilization + +| Service component | Contracted capacity | Utilized this quarter | Utilization rate | Trend | +|-------------------|--------------------|-----------------------|-----------------|-------| +| [e.g., Consulting hours] | [X hours] | [Y hours] | [Y/X %] | [Up / Flat / Down] | +| [e.g., Platform licenses] | [X seats] | [Y active] | [Y/X %] | [Trend] | +| [e.g., Support tickets] | [X included] | [Y submitted] | [Y/X %] | [Trend] | +| [e.g., Storage / Compute] | [X units] | [Y consumed] | [Y/X %] | [Trend] | + +**Utilization assessment:** [One to two sentences. Low utilization signals either a mismatch in scope or an adoption problem -- both threaten renewal. High utilization may signal expansion readiness.] + +**Recommendations:** [Adjust scope / Drive adoption in specific areas / Discuss capacity expansion] + +--- + +## 4. Support Ticket Analysis + +| Category | Tickets this quarter | Tickets last quarter | Change | Avg. resolution time | +|----------|---------------------|---------------------|--------|---------------------| +| [e.g., Technical issues] | [Count] | [Count] | [+/- %] | [Hours/days] | +| [e.g., Configuration requests] | [Count] | [Count] | [+/- %] | [Hours/days] | +| [e.g., Training / How-to] | [Count] | [Count] | [+/- %] | [Hours/days] | +| [e.g., Feature requests] | [Count] | [Count] | [+/- %] | [N/A] | +| **Total** | **[Count]** | **[Count]** | **[+/- %]** | **[Avg]** | + +**Patterns:** [What the ticket data reveals -- e.g., "Training tickets decreased 40% following the onboarding refresh in Month 2, but configuration requests increased, suggesting the platform is being used for more complex workflows."] + +**SLA compliance:** [Met / Partially met / Missed -- reference SLA metrics if applicable] + +--- + +## 5. Roadmap Alignment + +_Features, services, or capabilities on our roadmap that are relevant to this client's stated priorities._ + +| Roadmap item | Expected delivery | Relevance to this client | Client priority (H/M/L) | +|-------------|------------------|------------------------|-----------------------| +| [Feature or service] | [Quarter / Date] | [How it addresses a specific client need or request] | [H / M / L] | +| [Feature or service] | [Quarter / Date] | [Relevance] | [Priority] | +| [Feature or service] | [Quarter / Date] | [Relevance] | [Priority] | + +**Client-requested items not on roadmap:** + +| Request | Business case from client | Our assessment | Status | +|---------|--------------------------|----------------|--------| +| [Request] | [Why they want it] | [Feasibility and priority assessment] | [Under review / Declined with rationale / Scheduled] | +| [Request] | [Business case] | [Assessment] | [Status] | + +--- + +## 6. Expansion Opportunities + +| Opportunity | Description | Estimated value | Client readiness | Next step | +|-------------|-------------|----------------|-----------------|-----------| +| [e.g., Additional user licenses] | [Context -- why this serves the client's growth] | [$X / period] | [High -- they asked / Medium -- signals present / Low -- exploratory] | [Specific action] | +| [e.g., New service tier] | [Context] | [$X] | [Readiness] | [Action] | +| [e.g., Adjacent department rollout] | [Context] | [$X] | [Readiness] | [Action] | + +**Total addressable expansion:** [$X] + +--- + +## 7. Risks to Renewal + +| Risk | Severity | Probability | Evidence | Mitigation plan | +|------|----------|------------|----------|----------------| +| [e.g., Executive sponsor departure] | [H / M / L] | [H / M / L] | [What signals this risk -- e.g., "Champion promoted to new division; no successor identified"] | [Specific action to mitigate] | +| [e.g., Budget pressure] | [Severity] | [Probability] | [Evidence] | [Mitigation] | +| [e.g., Competitive evaluation] | [Severity] | [Probability] | [Evidence] | [Mitigation] | +| [e.g., Value perception gap] | [Severity] | [Probability] | [Evidence] | [Mitigation] | + +**Renewal date:** [Date] | **Days until renewal:** [Count] + +**Renewal forecast:** [ ] Confident [ ] Probable [ ] Uncertain [ ] At risk + +--- + +## 8. Strategic Recommendations + +_Recommendations that serve the client's business objectives, not your revenue targets. The distinction is obvious to every experienced buyer._ + +1. **[Recommendation]** -- Rationale: [Why this matters for the client now, linked to data in Sections 2-5] | Expected outcome: [What improves] + +2. **[Recommendation]** -- Rationale: [Evidence-based reasoning] | Expected outcome: [What improves] + +3. **[Recommendation]** -- Rationale: [Evidence-based reasoning] | Expected outcome: [What improves] + +--- + +## 9. Next Quarter Plan + +| # | Objective | Success metric | Owner | Deadline | +|---|-----------|---------------|-------|----------| +| 1 | [e.g., Increase platform adoption in marketing department from 40% to 70%] | [Measurable outcome] | [Name -- from your team or joint with client] | [Date] | +| 2 | [Objective] | [Metric] | [Owner] | [Date] | +| 3 | [Objective] | [Metric] | [Owner] | [Date] | +| 4 | [Objective] | [Metric] | [Owner] | [Date] | + +**Key milestones:** + +- Month 1: [Deliverable or checkpoint] +- Month 2: [Deliverable or checkpoint] +- Month 3: [Deliverable or checkpoint] + +--- + +## 10. Client Feedback + +**NPS score (if collected):** [Score] | **Trend:** [Up / Flat / Down from last quarter] + +**Verbatim feedback received this quarter:** + +> "[Direct quote from client stakeholder -- positive or negative. Attribution optional.]" + +> "[Direct quote]" + +**Open feedback questions for the QBR meeting:** + +1. What is the single most valuable thing we delivered this quarter? +2. Where did we fall short of your expectations? +3. What is changing in your business that we should know about for next quarter? +4. If you were renewing today, what would need to be different? + +--- + +**Next QBR:** [Date] | **Account owner:** [Name, email, phone] diff --git a/plugins/foreman/content/output-templates/client/service-level-agreement.md b/plugins/foreman/content/output-templates/client/service-level-agreement.md new file mode 100644 index 0000000..b9ace75 --- /dev/null +++ b/plugins/foreman/content/output-templates/client/service-level-agreement.md @@ -0,0 +1,201 @@ +--- +name: "service-level-agreement" +description: "Produces a service-level agreement template for service-based businesses that balances contractual clarity with readability. Covers service description, scope boundaries, performance metrics with measurement methods, service credits for breaches, tiered escalation procedures, review cadence, and termination provisions. Written in plain professional English -- not legalese. Use when formalizing service commitments to clients, establishing accountability structures with partners, or replacing handshake agreements with documented performance standards." +audience: "client" +applicable_skills: + - smart-goals + - net-promoter-score + - trust-equation + - delivering-the-deal +format: "agreement" +author: "Fatih Guner" +--- + +# Service Level Agreement + + + +**Agreement reference:** [SLA-YYYY-XXX] + +**Effective date:** [Date] | **Expiration date:** [Date or "Renewed annually unless terminated per Section 7"] + +--- + +**Service provider:** [Organization name] + +**Contact:** [Name, title, email, phone] + +**Client:** [Organization name] + +**Contact:** [Name, title, email, phone] + +--- + +## 1. Service Description + +**Service name:** [e.g., "Managed Cloud Infrastructure," "Fractional CFO Services," "Digital Marketing Retainer"] + +**Service summary:** [Two to three sentences describing what the service provider delivers, the business outcome it supports, and the client's operational context. Write for someone who was not in the room when the deal was negotiated.] + +**Service hours:** [e.g., "Monday through Friday, 09:00-18:00 [timezone], excluding national holidays per Schedule A" or "24/7/365"] + +--- + +## 2. Scope of Services + +### Included + +| # | Service component | Description | Delivery method | +|---|------------------|-------------|----------------| +| 1 | [e.g., System monitoring] | [What this entails specifically] | [e.g., Automated tooling + human review] | +| 2 | [e.g., Monthly reporting] | [What the report covers] | [e.g., Written report delivered via email] | +| 3 | [e.g., Incident response] | [What constitutes an incident, what the response involves] | [e.g., Ticketing system + phone escalation] | +| 4 | [Component] | [Description] | [Method] | +| 5 | [Component] | [Description] | [Method] | + +### Excluded + +_Clarity on boundaries prevents disputes. Name the services the client might reasonably assume are included but are not._ + +- [Exclusion 1 -- e.g., "Third-party vendor management beyond the platforms listed in Schedule B"] +- [Exclusion 2 -- e.g., "Hardware procurement and physical infrastructure maintenance"] +- [Exclusion 3 -- e.g., "Training beyond the initial onboarding sessions defined in Section 2.1"] +- [Exclusion 4 -- e.g., "Work requested outside service hours unless pre-approved as out-of-scope engagement"] + +**Out-of-scope requests:** Handled via a separate statement of work at rates defined in Schedule C. + +--- + +## 3. Performance Metrics + +### 3.1 Availability / Uptime + +| Metric | Target | Measurement method | Measurement period | Reporting frequency | +|--------|--------|-------------------|-------------------|-------------------| +| Service uptime | [e.g., 99.5%] | [e.g., Automated monitoring via [tool], calculated as total minutes minus downtime minutes divided by total minutes] | [Monthly] | [Monthly report, Section 5 of client dashboard] | + +**Scheduled maintenance windows:** [e.g., "Sundays 02:00-06:00 [timezone], notified 72 hours in advance. Scheduled maintenance is excluded from uptime calculations."] + +### 3.2 Response Time + +| Severity | Definition | Target response time | Target acknowledgment | +|----------|-----------|---------------------|-----------------------| +| Critical (S1) | [e.g., Complete service outage or data loss affecting production] | [e.g., 15 minutes] | [e.g., 30 minutes with named responder] | +| High (S2) | [e.g., Significant degradation affecting multiple users] | [e.g., 1 hour] | [e.g., 2 hours] | +| Medium (S3) | [e.g., Partial impact, workaround available] | [e.g., 4 hours] | [e.g., 8 business hours] | +| Low (S4) | [e.g., Minor issue, cosmetic, or feature request] | [e.g., 1 business day] | [e.g., 2 business days] | + +### 3.3 Resolution Time + +| Severity | Target resolution time | Escalation trigger | +|----------|----------------------|-------------------| +| Critical (S1) | [e.g., 4 hours] | [Auto-escalates to Tier 2 at 2 hours] | +| High (S2) | [e.g., 8 business hours] | [Auto-escalates to Tier 2 at 4 hours] | +| Medium (S3) | [e.g., 3 business days] | [Escalates at provider discretion] | +| Low (S4) | [e.g., 10 business days] | [Included in next scheduled maintenance cycle] | + +--- + +## 4. Service Credits + +_What happens when commitments are missed. An SLA without consequences is a marketing document._ + +### 4.1 Credit Schedule + +| SLA metric | Threshold breached | Credit applied | +|------------|-------------------|----------------| +| Monthly uptime | [Below 99.5% but above 99.0%] | [5% of monthly service fee] | +| Monthly uptime | [Below 99.0% but above 95.0%] | [15% of monthly service fee] | +| Monthly uptime | [Below 95.0%] | [30% of monthly service fee] | +| S1 response time | [Missed in more than 1 incident per month] | [5% of monthly service fee per additional miss] | +| S1 resolution time | [Missed in more than 1 incident per month] | [10% of monthly service fee per additional miss] | + +### 4.2 Credit Provisions + +- Maximum aggregate credit per month: [e.g., 30% of monthly service fee] +- Credits applied to the following month's invoice, not issued as cash refunds +- Client must request credits within [e.g., 30 days] of the breach +- Credits do not apply when the breach results from client actions, force majeure, or scheduled maintenance + +--- + +## 5. Escalation Procedures + +| Tier | Condition | Contact | Response commitment | +|------|-----------|---------|-------------------| +| Tier 1 -- Operational | [Standard issues, initial contact for all requests] | [Name / Team, email, phone] | [Per severity targets in Section 3] | +| Tier 2 -- Management | [Unresolved after target resolution time, or client requests escalation] | [Name / Title, email, phone] | [Acknowledgment within 1 hour; status update every 2 hours until resolved] | +| Tier 3 -- Executive | [Business-critical impact unresolved after 2x target resolution time, or pattern of repeated failures] | [Name / Title, email, phone] | [Direct engagement within 30 minutes; resolution plan within 4 hours] | + +**Escalation rights:** The client may escalate directly to any tier at any time. Tier 1 triage is the recommended path but not a mandatory gate. + +**Post-incident review:** Any S1 incident triggers a written root cause analysis delivered within [e.g., 5 business days], including corrective actions to prevent recurrence. + +--- + +## 6. Review and Amendment + +**Regular review cadence:** [e.g., Quarterly -- aligned with the quarterly business review] + +**Review covers:** + +- SLA performance vs. targets (all metrics from Section 3) +- Service credit activity (Section 4) +- Escalation frequency and resolution patterns (Section 5) +- Scope relevance -- whether included/excluded services still match client needs +- Proposed amendments for the next period + +**Amendment process:** Either party may propose SLA amendments in writing. Amendments require mutual written agreement and take effect [e.g., 30 days] after execution. Performance targets cannot be reduced below the levels defined in this agreement without the client's written consent. + +--- + +## 7. Term and Termination + +**Initial term:** [e.g., 12 months from effective date] + +**Renewal:** [e.g., Automatically renews for successive 12-month periods unless either party provides written notice of non-renewal at least 60 days before the current term expires] + +**Termination for convenience:** Either party may terminate with [e.g., 90 days] written notice. + +**Termination for cause:** Either party may terminate with [e.g., 30 days] written notice if the other party materially breaches this agreement and fails to cure the breach within the notice period. + +**Termination triggers (service provider):** + +- Client non-payment beyond [e.g., 45 days] past due +- Client actions that compromise service integrity or security + +**Termination triggers (client):** + +- Three or more S1 SLA breaches in any rolling 90-day period +- Aggregate service credits exceeding [e.g., 30%] of fees in any single month +- Failure to deliver post-incident root cause analysis for two consecutive S1 incidents + +**Transition assistance:** Upon termination, the service provider will deliver reasonable transition support for a period of [e.g., 30 days] at standard rates, including data export, documentation handover, and knowledge transfer sessions. + +--- + +**Signatures:** + +| | Service provider | Client | +|---|-----------------|--------| +| Name | [Name] | [Name] | +| Title | [Title] | [Title] | +| Date | [Date] | [Date] | +| Signature | _________________ | _________________ | + +--- + +**Schedules:** + +- **Schedule A:** Holiday calendar and service hour exceptions +- **Schedule B:** Covered platforms, systems, and environments +- **Schedule C:** Out-of-scope rate card diff --git a/plugins/foreman/content/output-templates/investor/cap-table-summary.md b/plugins/foreman/content/output-templates/investor/cap-table-summary.md new file mode 100644 index 0000000..7d42948 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/cap-table-summary.md @@ -0,0 +1,91 @@ +--- +name: "cap-table-summary" +description: "Produces a structured ownership summary showing current cap table, round history, ESOP details, dilution projections, and key terms. Designed for founders preparing investor conversations or managing board reporting on equity matters. Use when updating investors on ownership structure, preparing for a new round, or evaluating dilution scenarios before term sheet negotiations." +audience: "investor" +applicable_skills: + - coalition-and-partnership-games + - negotiation-game-theory + - evaluating-and-deciding +format: "summary" +author: "Fatih Guner" +--- + +# Cap Table Summary + +Ownership is the language of alignment — and misalignment. Every cell in this document represents a promise, a negotiation, or a bet on the future. Fill with actuals from your cap table management tool; approximations erode credibility with experienced investors. Delete this paragraph before distribution. + +**[Company Name]** | **As of:** [Date] | **Prepared by:** [Name, Title] + +--- + +## Current Ownership Structure + +| Shareholder | Share Class | Shares Held | % Ownership (Fully Diluted) | Notes | +|-------------|-----------|-------------|----------------------------|-------| +| [Founder 1] | Common | [number] | [X.X]% | [Vesting status, cliff remaining] | +| [Founder 2] | Common | [number] | [X.X]% | [Vesting status] | +| [Angel / Pre-Seed Investor(s)] | [Preferred / SAFE / Convertible] | [number] | [X.X]% | [Instrument type, conversion terms] | +| [Seed Lead Investor] | Series Seed Preferred | [number] | [X.X]% | [Fund name] | +| [Series A Lead Investor] | Series A Preferred | [number] | [X.X]% | [Fund name] | +| [Other Investors — group if minor] | [Class] | [number] | [X.X]% | [Aggregate for <1% holders] | +| ESOP Pool (allocated) | Common (options) | [number] | [X.X]% | [Exercised + unvested grants] | +| ESOP Pool (unallocated) | Common (reserved) | [number] | [X.X]% | [Available for future grants] | +| **Total** | | **[total shares]** | **100.0%** | | + +--- + +## Round History + +| Round | Date | Pre-Money Valuation | Amount Raised | Post-Money Valuation | Price Per Share | Lead Investor | Key Terms | +|-------|------|--------------------:|-------------:|-----------------------|--------------:|---------------|-----------| +| Pre-Seed / SAFE | [Date] | [N/A or cap] | $[amount] | [N/A or cap] | [N/A or implied] | [Name] | [Discount %, valuation cap] | +| Seed | [Date] | $[amount] | $[amount] | $[amount] | $[X.XX] | [Name] | [Participation, pro-rata] | +| Series A | [Date] | $[amount] | $[amount] | $[amount] | $[X.XX] | [Name] | [Board seat, protective provisions] | +| [Next round if applicable] | [Date] | $[amount] | $[amount] | $[amount] | $[X.XX] | [Name] | [Terms] | + +--- + +## ESOP Details + +| Parameter | Value | +|-----------|-------| +| Total pool size | [number] shares ([X.X]% fully diluted) | +| Allocated (vested + unvested) | [number] shares | +| Exercised | [number] shares | +| Available for future grants | [number] shares ([X.X]% fully diluted) | +| Standard vesting schedule | [4-year vest, 1-year cliff, monthly thereafter] | +| Exercise window post-departure | [90 days / extended — specify] | +| 409A fair market value (current) | $[X.XX] per share as of [valuation date] | + +**ESOP adequacy note:** [One to two sentences. Is the remaining pool sufficient for the next 12-18 months of hiring? Will a pool increase be required at the next round?] + +--- + +## Dilution Projections — Next Round Scenarios + +| Scenario | Pre-Money Valuation | New Capital | New Investor Ownership | Founder Dilution (post) | ESOP Top-Up | Founder % After | +|----------|--------------------:|------------:|-----------------------:|------------------------:|------------:|----------------:| +| Conservative | $[amount] | $[amount] | [X.X]% | [X.X pp] | [X.X]% to [X.X]% | [X.X]% | +| Base Case | $[amount] | $[amount] | [X.X]% | [X.X pp] | [X.X]% to [X.X]% | [X.X]% | +| Aggressive | $[amount] | $[amount] | [X.X]% | [X.X pp] | [X.X]% to [X.X]% | [X.X]% | + +**Dilution narrative:** [Two to three sentences. Which scenario preserves founder control? At what point does founder ownership cross below key thresholds — 50%, 33%, 20%? What are the implications?] + +--- + +## Key Terms Summary + +| Term | Status | Detail | +|------|--------|--------| +| Liquidation preference | [1x non-participating / 1x participating / other] | [Aggregate preference stack: $amount returned before common] | +| Anti-dilution protection | [Broad-based weighted average / Full ratchet / None] | [Trigger conditions] | +| Pro-rata rights | [Which investors hold them] | [Threshold for participation, pay-to-play provisions] | +| Board composition | [X] seats: [breakdown — founders, investors, independent] | [Appointment rights by class] | +| Protective provisions | [Standard / Enhanced] | [Veto rights held by preferred: fundraising, M&A, debt, ESOP changes] | +| Drag-along | [Yes / No] | [Threshold required, share class requirements] | +| Information rights | [Quarterly financials, annual audit, monthly dashboard] | [Which investors qualify] | +| Right of first refusal | [Company / Investors / Both] | [Secondary sale restrictions] | + +--- + +*Cap table managed in [Carta / Pulley / spreadsheet]. Last 409A valuation: [Date]. Legal counsel: [Firm Name]. This summary is for informational purposes; definitive terms are governed by the executed transaction documents.* diff --git a/plugins/foreman/content/output-templates/investor/competitive-landscape-brief.md b/plugins/foreman/content/output-templates/investor/competitive-landscape-brief.md new file mode 100644 index 0000000..67b12ed --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/competitive-landscape-brief.md @@ -0,0 +1,135 @@ +--- +name: "competitive-landscape-brief" +description: "Produces a 2-page competitive intelligence briefing modeled on equity research notes. Presents competitor analysis, threat assessment, moat evaluation, and strategic recommendations with analytical depth. Use after applying competitive frameworks to create a structured, data-driven brief that demonstrates market mastery to sophisticated investors." +audience: "investor" +applicable_skills: + - porters-five-forces + - disruptive-innovation + - art-of-war + - first-mover-strategy + - competitive-negotiation +format: "memo" +author: "Fatih Guner" +--- + +# Competitive Landscape Brief + + + +**CONFIDENTIAL** + +**Prepared for:** [Investor Name / Fund Name] +**Company:** [Company Name] +**Sector:** [Industry / Vertical] +**Date:** [Date] +**Prepared by:** [Author Name], [Title] + +--- + +## Executive Summary + +[Company Name] operates in [market description], a $[TAM] market characterized by [one-sentence structural description -- e.g., "fragmented incumbents with high customer acquisition costs and low switching barriers"]. The competitive landscape presents [favorable/mixed/challenging] conditions for a new entrant because [primary structural reason]. This brief assesses [number] direct competitors and [number] adjacent threats, and concludes that [Company Name]'s defensible position rests on [primary moat -- state it plainly]. + +--- + +## Industry Structure Overview + +**Overall industry attractiveness:** [Attractive / Moderate / Unattractive] + +| Structural Force | Intensity | Trend | Key Driver | +|-----------------|-----------|-------|------------| +| Entry barriers | [Weak / Moderate / Strong] | [Rising / Stable / Falling] | [Primary barrier: e.g., regulatory compliance, network effects, capital intensity] | +| Supplier power | [Weak / Moderate / Strong] | [Rising / Stable / Falling] | [Key supplier dynamic] | +| Buyer power | [Weak / Moderate / Strong] | [Rising / Stable / Falling] | [Concentration, switching costs] | +| Substitution threat | [Weak / Moderate / Strong] | [Rising / Stable / Falling] | [Primary substitute category] | +| Competitive rivalry | [Weak / Moderate / Strong] | [Rising / Stable / Falling] | [Basis of competition: price, features, brand, distribution] | + +**Structural implication:** [One to two sentences on what the industry structure means for profitability and strategic positioning.] + +--- + +## Competitor Matrix + + + +| Dimension | [Company Name] | [Competitor A] | [Competitor B] | [Competitor C] | [Competitor D] | +|-----------|---------------|----------------|----------------|----------------|----------------| +| **Founded** | [Year] | [Year] | [Year] | [Year] | [Year] | +| **Funding** | $[amount] | $[amount] | $[amount] | $[amount] | $[amount] | +| **Revenue (est.)** | $[amount] | $[amount] | $[amount] | $[amount] | $[amount] | +| **Customers** | [count or range] | [count or range] | [count or range] | [count or range] | [count or range] | +| **Target segment** | [Specific ICP] | [Specific ICP] | [Specific ICP] | [Specific ICP] | [Specific ICP] | +| **Pricing model** | [Model + range] | [Model + range] | [Model + range] | [Model + range] | [Model + range] | +| **Primary channel** | [Channel] | [Channel] | [Channel] | [Channel] | [Channel] | +| **Key strength** | [One phrase] | [One phrase] | [One phrase] | [One phrase] | [One phrase] | +| **Key vulnerability** | [One phrase] | [One phrase] | [One phrase] | [One phrase] | [One phrase] | + +--- + +## Threat Assessment + +### Tier 1 -- Direct Threats + +**[Competitor A]:** [Two to three sentences. Why they are the most dangerous direct competitor. What resources, positioning, or momentum makes them formidable. What they would need to do to threaten your position directly.] + +**[Competitor B]:** [Two to three sentences. Same structure.] + +### Tier 2 -- Adjacent Threats + +**[Adjacent Player or Category]:** [Two to three sentences. A company or category not currently competing directly but capable of entering. Describe the trigger conditions -- e.g., "If [Platform X] adds [feature], they would immediately capture [segment]."] + +### Tier 3 -- Disruptive Threats + +**[Disruptive vector]:** [Two to three sentences. Describe the technology shift, business model innovation, or market behavior change that could render current competitive positions obsolete. Assess probability and timeline.] + +--- + +## Moat Analysis + +| Moat Type | Present? | Strength | Evidence | Durability | +|-----------|----------|----------|----------|------------| +| Network effects | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [Specific metric or observation] | [Estimated years of advantage] | +| Switching costs | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [Integration depth, data lock-in, workflow dependency] | [Estimated years] | +| Proprietary data | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [Data asset description, defensibility] | [Estimated years] | +| Cost advantages | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [Unit economics comparison] | [Estimated years] | +| Brand / trust | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [NPS, retention, organic acquisition %] | [Estimated years] | +| Regulatory | [Yes / No / Emerging] | [Weak / Moderate / Strong] | [License, compliance barrier] | [Estimated years] | + +**Composite moat assessment:** [One to two sentences. Honest evaluation of overall defensibility. Name the weakest point.] + +--- + +## Strategic Positioning + +**Chosen battleground:** [The specific segment, use case, or geographic market where you concentrate force -- and why competitors are poorly positioned to follow.] + +**Competitive doctrine:** + +1. **[Strategic principle 1]:** [One sentence. E.g., "Avoid direct feature competition with [Competitor A] and instead dominate [underserved segment] where their enterprise-focused sales motion cannot reach."] +2. **[Strategic principle 2]:** [One sentence. E.g., "Build switching costs through [specific integration or data strategy] before [Competitor B] achieves sufficient scale to attempt the same."] +3. **[Strategic principle 3]:** [One sentence. E.g., "Maintain first-mover advantage in [specific capability] by investing [X%] of engineering resources in R&D ahead of competitive parity."] + +--- + +## Recommendations + +| Priority | Action | Competitive Rationale | Timeline | +|----------|--------|-----------------------|----------| +| 1 | [Specific action] | [Which threat or opportunity this addresses] | [Q/Year] | +| 2 | [Specific action] | [Which threat or opportunity this addresses] | [Q/Year] | +| 3 | [Specific action] | [Which threat or opportunity this addresses] | [Q/Year] | + +--- + +## Monitoring Framework + +| Signal | Source | Trigger Threshold | Response Protocol | +|--------|--------|-------------------|-------------------| +| [Competitor A fundraise] | [Crunchbase, press] | [Series B+ or >$50M] | [Accelerate timeline for X] | +| [New entrant in segment] | [Product Hunt, industry press] | [Funded team with relevant domain] | [Evaluate and brief within 48 hours] | +| [Customer churn pattern] | [Internal data] | [>X% monthly churn to specific competitor] | [Win/loss analysis within 2 weeks] | +| [Technology shift] | [Research papers, patent filings] | [Production-ready alternative to core tech] | [R&D assessment within 30 days] | + +--- + + diff --git a/plugins/foreman/content/output-templates/investor/decision-rationale-memo.md b/plugins/foreman/content/output-templates/investor/decision-rationale-memo.md new file mode 100644 index 0000000..358f526 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/decision-rationale-memo.md @@ -0,0 +1,146 @@ +--- +name: "decision-rationale-memo" +description: "Produces a structured decision memorandum explaining the reasoning behind a major strategic decision -- a pivot, market entry, pricing change, partnership, or organizational restructuring. Modeled on the Amazon six-page memo discipline. Demonstrates analytical rigor, intellectual honesty about alternatives and risks, and clarity of thought. Use when communicating consequential decisions to investors who value transparent founder reasoning over polished narratives." +audience: "investor" +applicable_skills: + - evaluating-and-deciding + - defining-and-exploring-problems + - scenario-planning + - decision-traps-and-roles + - thinking-fast-and-slow +format: "memo" +author: "Fatih Guner" +--- + +# Decision Rationale Memo + + + +**MEMORANDUM** + +**To:** [Investor Name(s) / Board] +**From:** [Your Name], [Title], [Company Name] +**Date:** [Date] +**Re:** [Decision Title -- e.g., "Decision to Enter the European Market" / "Pricing Model Transition from Per-Seat to Usage-Based" / "Strategic Partnership with [Company X]"] + +--- + +## The Decision + +[Company Name] has decided to [state the decision in plain, specific language]. This decision takes effect [date or trigger condition] and commits the company to [describe the primary resource commitment -- capital, headcount, timeline, or opportunity cost]. This memo presents the analysis, alternatives considered, risks acknowledged, and conditions under which we would reverse course. + +--- + +## The Problem This Decision Addresses + + + +[What changed -- internally or externally -- that made the status quo untenable? Ground this in data: a metric that moved, a market shift, a competitive action, a customer signal.] + +[Consequences of inaction. What happens if the company does nothing? Quantify where possible.] + +[The core tension. Name the trade-off explicitly. E.g., "Expanding into Europe accelerates revenue but divides engineering focus during product maturation."] + +--- + +## How We Explored the Problem + +[Analytical methods applied: scenario planning, decision matrices, customer research, financial modeling. Name inputs and sources.] + +[Who was involved. Decision-maker, advisors consulted, dissenting voices. If someone disagreed, note their reasoning.] + +--- + +## Alternatives Considered + + + +### Alternative A: [Name or brief description] + +[One paragraph describing this alternative as its strongest advocate would present it. What are its merits? What problem does it solve?] + +**Why rejected:** [One paragraph. Specific reasons -- data, feasibility constraints, risk profile, or misalignment with strategic priorities. Not "it was not as good" -- state precisely why.] + +### Alternative B: [Name or brief description] + +[One paragraph describing this alternative at its strongest.] + +**Why rejected:** [One paragraph with specific reasoning.] + +### Alternative C: [Status Quo / Do Nothing] + +[One paragraph describing the case for inaction. There is always a case for inaction, and presenting it honestly strengthens the argument for action.] + +**Why rejected:** [One paragraph. Typically grounded in the cost of delay, competitive dynamics, or a closing window of opportunity.] + +--- + +## The Chosen Path: Detailed Rationale + +[Paragraph 1: The primary reason. The single most important factor, supported by the strongest evidence.] + +[Paragraph 2: Secondary supporting reasons that reinforce but would not alone justify the decision.] + +[Paragraph 3: The strongest counterargument, engaged honestly. Why the balance of evidence still favors this path.] + +[Paragraph 4: Expected outcome in measurable terms. Success metrics at 6 and 12 months.] + +--- + +## Scenario Analysis + +| Scenario | Conditions | Outcome for This Decision | Our Response | +|----------|------------|--------------------------|--------------| +| **Base case** | [Describe assumed conditions -- e.g., "Market grows at 15%, no major competitive entry, current burn rate maintained"] | [Expected result] | [Continue as planned] | +| **Upside case** | [Describe favorable conditions] | [Accelerated result] | [How we capitalize -- e.g., "Accelerate hiring plan, bring forward Series B timeline"] | +| **Downside case** | [Describe adverse conditions -- e.g., "Market contraction, key hire fails, competitor launches rival product"] | [Degraded result] | [Specific contingency -- e.g., "Reduce scope to [market/segment], extend runway by cutting X"] | +| **Black swan** | [Describe the low-probability, high-impact event] | [Severe result] | [Emergency response -- e.g., "Invoke reversal criteria below and execute within 30 days"] | + +--- + +## Risks Acknowledged + +1. **[Risk 1]:** [One sentence.] Probability: [High / Medium / Low]. Mitigation: [Specific action.] +2. **[Risk 2]:** [One sentence.] Probability: [High / Medium / Low]. Mitigation: [Specific action.] +3. **[Risk 3]:** [One sentence.] Probability: [High / Medium / Low]. Mitigation: [Specific action.] + +--- + +## Decision Traps Audit + +We audited this decision process against common cognitive traps: + +- **Anchoring:** [Describe how you tested whether the first data point or option unduly influenced the analysis. E.g., "Initial financial projections anchored on [source]. We reran the model using [alternative source] as a base case to test sensitivity."] +- **Sunk cost:** [Describe how you ensured that prior investment in the status quo did not bias toward inaction or toward doubling down. E.g., "The $X already invested in [prior approach] was explicitly excluded from the go-forward analysis."] +- **Confirmation bias:** [Describe what disconfirming evidence you actively sought. E.g., "We conducted five customer interviews specifically designed to surface objections to the proposed approach."] +- **Overconfidence:** [Describe how you calibrated confidence in projections. E.g., "All financial projections include a 30% downside sensitivity. The decision remains positive under all scenarios above [threshold]."] + +--- + +## Reversal Criteria + +This decision will be reversed if any of the following conditions are met: + +1. **[Metric-based trigger]:** [E.g., "If [specific metric] fails to reach [threshold] by [date], we will [specific reversal action]."] +2. **[Signal-based trigger]:** [E.g., "If [competitive event or market signal] occurs, we will reconvene within [timeframe] to reassess."] +3. **[Resource-based trigger]:** [E.g., "If cash runway drops below [X months] before the decision achieves [milestone], we will revert to [fallback plan]."] + +**Decision review date:** [Specific date for formal reassessment, regardless of trigger conditions.] + +--- + +## Implementation Summary + +| Phase | Action | Owner | Timeline | Success Metric | +|-------|--------|-------|----------|----------------| +| 1 | [First implementation step] | [Name] | [Date range] | [Measurable outcome] | +| 2 | [Second implementation step] | [Name] | [Date range] | [Measurable outcome] | +| 3 | [Third implementation step] | [Name] | [Date range] | [Measurable outcome] | + +**Total resource commitment:** $[amount] and [X FTEs] over [timeframe]. + +**First checkpoint:** [Date] -- at which point [specific deliverable or metric] will be evaluated against the base case scenario. + +--- + + diff --git a/plugins/foreman/content/output-templates/investor/due-diligence-checklist.md b/plugins/foreman/content/output-templates/investor/due-diligence-checklist.md new file mode 100644 index 0000000..a3d056d --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/due-diligence-checklist.md @@ -0,0 +1,117 @@ +--- +name: "due-diligence-checklist" +description: "Produces a comprehensive due diligence preparation checklist organized by category — corporate, financial, legal, product/technical, HR, and commercial. Each item carries a readiness status, document location, and notes field. Designed for founders to complete before due diligence begins, transforming a reactive process into a controlled one. Use when a term sheet is imminent, when preparing a data room, or when conducting an internal readiness audit." +audience: "investor" +applicable_skills: + - smart-goals + - defining-and-exploring-problems + - managing-up +format: "checklist" +author: "Fatih Guner" +--- + +# Due Diligence Checklist + +The speed and completeness of your due diligence response communicates more than the documents themselves. Investors interpret a clean data room as a proxy for operational discipline — and a messy one as evidence of its absence. Complete this checklist before the first DD request arrives, not after. Delete this paragraph before distribution. + +**[Company Name]** | **Prepared for:** [Round Type] Due Diligence | **Date:** [Date] +**Data room location:** [URL] | **Data room admin:** [Name, Email] + +**Status key:** READY | IN PROGRESS | MISSING | N/A + +--- + +## 1. Corporate + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 1.1 | Certificate of Incorporation (+ all amendments, restated) | [Status] | [Folder/Link] | | +| 1.2 | Bylaws (current, executed) | [Status] | [Folder/Link] | | +| 1.3 | Board and shareholder meeting minutes / written consents | [Status] | [Folder/Link] | | +| 1.4 | Cap table (fully diluted, current) | [Status] | [Folder/Link] | [Export from Carta/Pulley; include SAFE/note conversion modelling] | +| 1.5 | Equity agreements (stock purchase, SAFEs, convertible notes) | [Status] | [Folder/Link] | [Include side letters] | +| 1.6 | Prior round term sheets and closing documents | [Status] | [Folder/Link] | | +| 1.7 | Investor rights / voting / ROFR agreements | [Status] | [Folder/Link] | | +| 1.8 | Entity structure and qualifications to do business | [Status] | [Folder/Link] | [Subsidiaries, international entities, state registrations] | + +## 2. Financial + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 2.1 | Financial statements — last 3 fiscal years (or since inception) | [Status] | [Folder/Link] | [Audited if available] | +| 2.2 | Current year monthly P&L, balance sheet, cash flow | [Status] | [Folder/Link] | [Through most recent closed month] | +| 2.3 | Financial projections — 3-year model with assumptions | [Status] | [Folder/Link] | | +| 2.4 | Burn rate, runway calculation, and bank statements | [Status] | [Folder/Link] | [Current cash position, months remaining, all accounts] | +| 2.5 | Revenue breakdown by customer / segment / product | [Status] | [Folder/Link] | | +| 2.6 | AR aging and AP summary | [Status] | [Folder/Link] | | +| 2.7 | Debt schedule (all outstanding obligations) | [Status] | [Folder/Link] | [Venture debt, credit lines, equipment financing] | +| 2.8 | Tax returns — last 3 years (federal + state) | [Status] | [Folder/Link] | | +| 2.9 | 409A valuation report (most recent) | [Status] | [Folder/Link] | [Must be within 12 months or post-material event] | + +## 3. Legal + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 3.1 | IP assignments (all founders and employees) | [Status] | [Folder/Link] | [Confirm no gaps — especially pre-incorporation contributions] | +| 3.2 | IP portfolio (patents, trademarks, registrations) | [Status] | [Folder/Link] | | +| 3.3 | Material contracts (>$[threshold] or >12 months) | [Status] | [Folder/Link] | [Customer, vendor, partnership agreements] | +| 3.4 | Litigation — pending, threatened, or settled | [Status] | [Folder/Link] | ["None" requires affirmative statement] | +| 3.5 | Regulatory filings, licenses, permits | [Status] | [Folder/Link] | | +| 3.6 | Privacy policy, ToS, and data processing agreements | [Status] | [Folder/Link] | | +| 3.7 | Insurance policies (D&O, E&O, cyber, general liability) | [Status] | [Folder/Link] | | +| 3.8 | Open-source license audit | [Status] | [Folder/Link] | [Copyleft dependency compliance report] | + +## 4. Product & Technical + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 4.1 | Architecture overview and tech stack summary | [Status] | [Folder/Link] | [System diagram] | +| 4.2 | Security: certifications, pen test results, practices | [Status] | [Folder/Link] | [SOC 2, ISO 27001; audit report or readiness assessment] | +| 4.3 | Uptime / reliability metrics and SLA compliance | [Status] | [Folder/Link] | [Last 12 months] | +| 4.4 | Scalability assessment and technical debt appraisal | [Status] | [Folder/Link] | [Current capacity, growth ceiling, honest debt inventory] | +| 4.5 | Product roadmap (next 12-18 months) | [Status] | [Folder/Link] | | +| 4.6 | Third-party dependencies and data backup/recovery | [Status] | [Folder/Link] | [Critical vendors, single points of failure] | + +## 5. HR & People + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 5.1 | Org chart (current) and key employee bios | [Status] | [Folder/Link] | [Include open positions; leadership + critical technical leads] | +| 5.2 | Employment and contractor agreements | [Status] | [Folder/Link] | [At-will status; IP assignment; contractor classification compliance] | +| 5.3 | Compensation summary (base, bonus, equity by role) | [Status] | [Folder/Link] | | +| 5.4 | ESOP plan document and grant ledger | [Status] | [Folder/Link] | [Reconcile with cap table] | +| 5.5 | Founder vesting and acceleration triggers | [Status] | [Folder/Link] | [Single/double trigger details] | +| 5.6 | Employee handbook, non-competes, HR policies | [Status] | [Folder/Link] | [Note non-compete enforceability by jurisdiction] | +| 5.7 | Headcount plan (next 12 months) | [Status] | [Folder/Link] | [Tied to financial projections] | + +## 6. Commercial + +| # | Document | Status | Location | Notes | +|---|----------|--------|----------|-------| +| 6.1 | Customer list with ARR/MRR and concentration analysis | [Status] | [Folder/Link] | [Top 20 accounts; % from top 1, 5, 10] | +| 6.2 | Sales pipeline report | [Status] | [Folder/Link] | [Weighted pipeline by stage] | +| 6.3 | Churn and NRR data (last 12-24 months) | [Status] | [Folder/Link] | [Logo churn, revenue churn, cohort NRR] | +| 6.4 | Customer references and case studies | [Status] | [Folder/Link] | [5-8 referenceable customers across segments] | +| 6.5 | Pricing history and planned changes | [Status] | [Folder/Link] | | +| 6.6 | Partnership / channel agreements | [Status] | [Folder/Link] | | +| 6.7 | Competitive win/loss analysis | [Status] | [Folder/Link] | [Last 6 months minimum] | + +--- + +## Readiness Summary + +| Category | Total Items | Ready | In Progress | Missing | N/A | +|----------|-------------|-------|-------------|---------|-----| +| Corporate | 8 | [#] | [#] | [#] | [#] | +| Financial | 9 | [#] | [#] | [#] | [#] | +| Legal | 8 | [#] | [#] | [#] | [#] | +| Product & Technical | 6 | [#] | [#] | [#] | [#] | +| HR & People | 7 | [#] | [#] | [#] | [#] | +| Commercial | 7 | [#] | [#] | [#] | [#] | +| **Total** | **45** | **[#]** | **[#]** | **[#]** | **[#]** | + +**Readiness assessment:** [Two to three sentences. Honest appraisal of preparedness. Identify the category requiring the most work and the estimated timeline to achieve full readiness.] + +--- + +*Checklist owner: [Name]. Target completion: [Date]. Data room access will be granted only after [minimum readiness threshold — e.g., all Corporate and Financial items at READY status]. Legal counsel: [Firm Name].* diff --git a/plugins/foreman/content/output-templates/investor/exit-scenario-analysis.md b/plugins/foreman/content/output-templates/investor/exit-scenario-analysis.md new file mode 100644 index 0000000..56ca32f --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/exit-scenario-analysis.md @@ -0,0 +1,109 @@ +--- +name: "exit-scenario-analysis" +description: "Produces an exit strategy analysis presenting three scenarios — acquisition, IPO, and secondary sale — with valuation methodologies, comparable transactions, return multiples by investor class, and a waterfall distribution template. Designed for founders and investors evaluating paths to liquidity. Use when building long-term strategic plans, preparing for board discussions on exit timing, or modeling investor returns during fundraising." +audience: "investor" +applicable_skills: + - scenario-planning + - growth-share-matrix + - evaluating-and-deciding + - game-theory-fundamentals +format: "analysis" +author: "Fatih Guner" +--- + +# Exit Scenario Analysis + +Every investment thesis ends with a liquidity event. The quality of exit planning reveals whether founders treat investor capital as a trust or a gift. This analysis models three paths to liquidity, each with distinct mechanics, timelines, and implications for different share classes. Replace all placeholders; generic scenarios persuade no one. Delete this paragraph before distribution. + +**[Company Name]** | **Date:** [Date] | **Stage:** [Seed / Series A / B / Growth] | **Last Round:** [Round] at $[post-money] + +--- + +## Company Snapshot + +| Metric | Current | Growth | Metric | Current | +|--------|---------|--------|--------|---------| +| ARR/Revenue | $[amount] | [X]% YoY | Total Customers | [number] | +| Gross Margin | [X]% | [+/- pp] | Employees | [number] | +| NRR | [X]% | | Cash / Runway | $[amount] / [X] mo | +| Capital Raised | $[amount] | | Last Post-Money | $[amount] | + +--- + +## Scenario 1: Acquisition + +**Probability:** [High / Medium / Low] | **Timeline:** [X-Y] years | **Methodology:** [Revenue multiple / EBITDA multiple / strategic premium] + +**Rationale:** [Three to four sentences. Why acquisition is plausible. Acquirer category and what makes the company attractive versus a build-or-ignore decision.] + +| Comparable Transaction | Year | Revenue | Price | Multiple | +|----------------------|------|--------:|------:|---------:| +| [Company A acquired by X] | [Year] | $[amount] | $[amount] | [X.X]x | +| [Company B acquired by Y] | [Year] | $[amount] | $[amount] | [X.X]x | +| [Company C acquired by Z] | [Year] | $[amount] | $[amount] | [X.X]x | + +**Projected range:** $[low] — $[high] (median [X.X]x on [metric at exit]) +**Milestones:** (1) [Revenue target] (2) [Product readiness] (3) [Market position] (4) [Strategic positioning] +**Likely acquirers:** [Name 1 — rationale], [Name 2 — rationale], [Name 3 — rationale] + +--- + +## Scenario 2: IPO + +**Probability:** [High / Medium / Low] | **Timeline:** [X-Y] years | **Methodology:** [Forward revenue multiple / EV/EBITDA] + +**Rationale:** [Three to four sentences. Revenue scale required, market conditions, regulatory considerations. Honest assessment of whether the business can sustain public-company scrutiny.] + +| Public Comparable | Revenue | Market Cap | EV/Revenue | EV/EBITDA | Growth | +|------------------|--------:|----------:|-----------:|----------:|-------:| +| [Public Co A] | $[amount] | $[amount] | [X.X]x | [X.X]x | [X]% | +| [Public Co B] | $[amount] | $[amount] | [X.X]x | [X.X]x | [X]% | +| [Public Co C] | $[amount] | $[amount] | [X.X]x | [X.X]x | [X]% | + +**Projected range:** $[low] — $[high] (median [X.X]x on [projected revenue]) +**Milestones:** (1) [$[X]M ARR, [X]% growth] (2) [EBITDA trajectory] (3) [SOX, board, CFO] (4) [Market window] + +--- + +## Scenario 3: Secondary Sale + +**Probability:** [High / Medium / Low] | **Timeline:** [X-Y] years | **Mechanism:** [Tender offer / Direct sale / Fund transfer] + +**Rationale:** [Two to three sentences. Secondary sales provide partial liquidity without a full exit. Describe conditions under which this becomes the preferred path.] + +**Pricing:** [Discount to last round: X-Y% / At last round / Premium] | **Constraints:** ROFR: [holder] | Board: [Y/N] | Restrictions: [Detail] + +## Return Analysis by Investor Class + +| Investor / Class | Invested | Ownership % | Acquisition ($[X]M) | IPO ($[X]M) | Secondary ($[X]M) | +|------------------|--------:|-----------:|--------------------:|------------:|-------------------:| +| Founders (Common) | $[amount] | [X.X]% | $[return] / [X.X]x | $[return] / [X.X]x | $[return] / [X.X]x | +| Seed (Series Seed Pfd) | $[amount] | [X.X]% | $[return] / [X.X]x | $[return] / [X.X]x | $[return] / [X.X]x | +| Series A (Series A Pfd) | $[amount] | [X.X]% | $[return] / [X.X]x | $[return] / [X.X]x | $[return] / [X.X]x | +| ESOP Holders | $[exercise cost] | [X.X]% | $[return] / [X.X]x | $[return] / [X.X]x | [N/A or limited] | + +--- + +## Waterfall Analysis — Proceeds Distribution + +**Assumptions:** Exit at $[amount] | [Non-participating / Participating] preferred | [1x / other] liquidation preference + +| Priority | Recipient | Entitlement | Amount | Remaining | +|----------|-----------|-------------|-------:|----------:| +| 1 | Series A Preferred | [1x liquidation preference] | $[amount] | $[amount] | +| 2 | Series Seed Preferred | [1x liquidation preference] | $[amount] | $[amount] | +| 3 | Participation (if applicable) | [Pro-rata of remainder, capped at [X]x] | $[amount] | $[amount] | +| 4 | Common (founders + exercised options) | [Pro-rata of remainder] | $[amount] | $[amount] | +| | **Total distributed** | | **$[amount]** | **$0** | + +**Conversion threshold:** At $[threshold], preferred holders earn more by converting to common. Below that, the preference stack protects downside. [One sentence on the practical implication for founders.] + +--- + +## Strategic Recommendation + +[Three to five sentences. Based on current trajectory, which exit path is most likely and most favorable? What should the company prioritize over the next 12-24 months to maximize optionality across scenarios? Name the single decision that most affects exit outcome — and whether it requires board deliberation.] + +--- + +*Data as of [Date]. Projections reflect management estimates and comparable market data. This document does not constitute financial advice. Legal and tax counsel should review before any liquidity transaction.* diff --git a/plugins/foreman/content/output-templates/investor/fundraising-deck-outline.md b/plugins/foreman/content/output-templates/investor/fundraising-deck-outline.md new file mode 100644 index 0000000..ec25346 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/fundraising-deck-outline.md @@ -0,0 +1,102 @@ +--- +name: "fundraising-deck-outline" +description: "Produces a strategic content outline for a 10-12 slide fundraising pitch deck. Not a design tool — a narrative architecture document that specifies what belongs on each slide, what investors scrutinize, and where founders routinely fail. Grounded in the Sequoia pitch framework and Guy Kawasaki's 10/20/30 rule. Use when preparing for seed, Series A, or growth-stage fundraising to ensure every slide carries argumentative weight." +audience: "investor" +applicable_skills: + - business-model-canvas + - blue-ocean-strategy + - four-ps-marketing + - storytelling-for-leaders + - what-is-a-story +format: "presentation-outline" +author: "Fatih Guner" +--- + +# Fundraising Deck Outline + +A pitch deck is a persuasion architecture — twelve slides building one compounding argument: this team, this market, this moment, this model, outsized returns. Every slide advances that thesis or weakens it. There is no neutral ground. Replace all bracketed placeholders. Delete HTML comments before presenting. + +--- + +### SLIDE 1: Title +- Company name and one-line descriptor (max 8 words) | Logo | Founder name(s) | Round: [Seed / A / B] +- **Investor Lens:** The one-liner sorts. Partners read 50 decks weekly. "[Specific outcome] for [specific buyer]" works. "AI-powered platform for X" does not. +- **Mistake:** Clever taglines that sacrifice clarity. Buzzwords that fit 200 companies. + +### SLIDE 2: Problem +- [Problem in one sentence from the customer's perspective] +- [Quantify the pain: cost, time, failure rate, or missed revenue] +- [Why existing solutions fail — the structural gap] +- **Investor Lens:** Investors fund problems, not products. "42% of mid-market CFOs manually reconcile invoices, consuming 11 hours weekly" outperforms "reconciliation is painful." +- **Mistake:** Describing the problem as the absence of your solution. + +### SLIDE 3: Solution +- [What you built in plain language — two sentences maximum] +- [The primary insight or mechanism that makes it work] +- [One screenshot, product image, or diagram — visual proof it exists] +- **Investor Lens:** One clear mechanism beats a feature tour. The deck earns a meeting, not a term sheet. +- **Mistake:** Feature dumping. Eight capabilities when one sharp insight suffices. + +### SLIDE 4: Market Opportunity +- TAM: $[amount] — [source] | SAM: $[amount] — [filter] | SOM: $[amount] — [3-year assumptions] +- [One sentence on the macro tailwind: regulatory shift, tech inflection, behavioral change] +- **Investor Lens:** Seasoned investors ignore TAM. They scrutinize SAM-to-SOM logic. Bottom-up sizing is credible; "the global market is $80B, we capture 1%" is not. +- **Mistake:** Analyst reports as proof without a plausible capture path. + +### SLIDE 5: Business Model +- Revenue model: [Subscription / Transaction / Marketplace / Licensing] | Pricing: $[amount] per [unit] +- Unit economics: LTV $[amount] / CAC $[amount] / Ratio [X:1] | Gross margin: [X%] +- Expansion mechanism: [Upsell / land-and-expand / usage-based growth] +- **Investor Lens:** Does this model improve or degrade with volume? LTV:CAC >3:1, payback <18 months, expansion structural not aspirational. +- **Mistake:** Unit economics based on projected-future costs. Show actuals, even if early. + +### SLIDE 6: Traction +- [Primary metric: ARR, MRR, GMV, or active users — with timeline] +- [Growth rate: MoM or YoY] | [Customer logos or count] | [Cohort retention data] +- **Investor Lens:** The most influential slide at Series A. Growth rate matters more than absolute revenue. Cohort curves that flatten or bend upward are the most powerful data a founder can present. +- **Mistake:** Showing only acquisition. Investors ask: "What happens after sign-up?" Answer it on the slide. + +### SLIDE 7: Competitive Landscape +- [2x2 matrix with axes relevant to your differentiation] +- [3-5 competitors plotted honestly] | [One sentence on your value innovation via ERRC grid] +- **Investor Lens:** "We have no competitors" is the most disqualifying sentence in fundraising. Blue Ocean positioning — competing on dimensions others ignore — outperforms incremental superiority on the same axes. +- **Mistake:** Feature comparison where you win every row. Acknowledge strength elsewhere; explain why it does not matter for your segment. + +### SLIDE 8: Go-to-Market +- Channel: [Sales / PLG / Content / Partnerships] | CAC by channel: $[amount] | Cycle: [X days] +- Near-term motion (12 months): [Specific plan with milestones] +- **Investor Lens:** GTM reveals whether you understand the customer's buying process. The strongest slides show a flywheel — each customer makes the next one cheaper to acquire. +- **Mistake:** Listing every channel instead of demonstrating mastery of one. + +### SLIDE 9: Team +- [2-4 founders: name, title, one line connecting experience to this specific problem] +- [Key hires made + planned] | [Advisors with domain credibility] +- **Investor Lens:** Founder-market fit outweighs credentials. "Led Google's identity infrastructure, the core problem we solve" beats "Ex-Google." +- **Mistake:** Credentials without connection to the company's challenge. + +### SLIDE 10: Financials +- [Revenue projection: current year + 2 years, monthly granularity for current year] +- [Key assumptions stated explicitly] | [Burn: $[amount]/mo, runway: [X] months] +- **Investor Lens:** Nobody believes three-year projections. Investors use them to test reasoning. "We project $5M ARR in Y2, contingent on ACV expansion from $12K to $25K" is credible. A hockey stick with no mechanism is not. +- **Mistake:** Projections without named assumptions. The model is the argument. + +### SLIDE 11: The Ask +- Raising: $[amount] | Instrument: [SAFE / Priced / Note] +- Use of funds: [Specific — e.g., "50% engineering, 30% GTM, 20% ops"] +- Target milestone: [What this capital achieves — the milestone that de-risks the next round] +- **Investor Lens:** "$5M to grow the business" is a red flag. "$5M to reach $3M ARR by Q3 2027" demonstrates a modeled path between capital and outcome. +- **Mistake:** Vague allocation. Missing milestone. Amount disconnected from any stated goal. + +### SLIDE 12: Closing +- Restate the one-line value proposition | [Single most compelling data point from the deck] +- Contact: email, phone | "Data room, financials, and customer references available" +- **Investor Lens:** This slide stays on screen during Q&A — the longest part of the meeting. Leave one number in the room. +- **Mistake:** "Thank you" and nothing else. Wasting the most persistent visual real estate in the presentation. + +--- + +## Narrative Arc Checklist + +Before presenting, verify the throughline: Problem (urgency) leads to Solution (insight) leads to Market (scale) leads to Model (durability) leads to Traction (proof) leads to Competition (defensibility) leads to GTM (path) leads to Team (credibility) leads to Financials (reasoning) leads to Ask (milestone). Each slide should make the next more powerful. If removing a slide does not weaken the arc, remove it. + + diff --git a/plugins/foreman/content/output-templates/investor/investor-update-email.md b/plugins/foreman/content/output-templates/investor/investor-update-email.md new file mode 100644 index 0000000..1a32034 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/investor-update-email.md @@ -0,0 +1,88 @@ +--- +name: "investor-update-email" +description: "Produces a monthly or quarterly investor update email structured around the format top-tier VCs consistently request: a three-bullet TL;DR, key metrics table, wins, challenges with mitigations, specific asks, team changes, and cash position. Designed for scannability and honesty — the two qualities that sustain investor trust and unlock follow-on value. Informed by First Round Capital and Y Combinator best practices on investor communications." +audience: "investor" +applicable_skills: + - writing-effective-emails + - writing-for-navigation + - writing-for-response + - balanced-scorecard +format: "email-template" +author: "Fatih Guner" +--- + +# Investor Update Email + +An investor update is not a report — it is a relationship maintenance instrument. The updates that unlock introductions, follow-on capital, and crisis counsel share three properties: brevity, honesty, and a specific ask. Fill all placeholders, strip all comments, send within the first week of the period. Silence erodes trust faster than bad news. + +--- + +**Subject:** [Company Name] — [Month / Q#] [Year] Update + +Hi [First Name / "team"], + +[Company Name] [monthly / quarterly] update. Reading time: under 3 minutes. + +## TL;DR + + + +- **[Top achievement]:** [One sentence with a specific number or outcome.] +- **[Primary challenge]:** [One sentence. Name it plainly.] +- **[What's next or what you need]:** [One sentence. Forward-looking.] + +## Key Metrics + +| Metric | This Period | Prior Period | Change | Target | +|--------|------------|-------------|--------|--------| +| Revenue / ARR | $[amount] | $[amount] | [+/- X%] | $[amount] | +| Customers | [count] | [count] | [+/- X] | | +| Churn (logo / revenue) | [X%] | [X%] | [+/- pp] | <[X%] | +| Burn rate | $[amount]/mo | $[amount]/mo | [+/- X%] | | +| Runway | [X] months | [X] months | | | +| [Custom KPI] | [value] | [value] | [+/- X%] | | + +## Wins + + + +1. [Win with specific data point] +2. [Win with specific data point] +3. [Win with specific data point] + +## Challenges + + + +**[Challenge 1]:** [What happened, why it matters, what you are doing about it. Two to three sentences.] + +**[Challenge 2]:** [Same structure.] + +## Asks + + + +1. **[Introduction]:** [Specific person, company, why it matters, ideal outcome.] +2. **[Hiring]:** [Role, seniority, whether you need a referral or help closing a finalist.] +3. **[Advice]:** [Specific question framed for a 2-3 sentence response.] + +## Team + +[One to two sentences. Hires, departures, or changes. If stable: "Team at [X] full-time, no changes."] + +## Cash Position + +| Cash on hand | $[amount] | +|---|---| +| Monthly burn | $[amount] | +| Runway | [X] months (through [Month Year]) | +| Next fundraise | [Amount] — [timeline, if planned] | + +--- + +Thank you for your continued support. If any ask above is within your network, a brief introduction would be valuable. + +[Founder Name], [Title] +[Email] | [Phone] + + diff --git a/plugins/foreman/content/output-templates/investor/market-opportunity-summary.md b/plugins/foreman/content/output-templates/investor/market-opportunity-summary.md new file mode 100644 index 0000000..8bb4828 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/market-opportunity-summary.md @@ -0,0 +1,161 @@ +--- +name: "market-opportunity-summary" +description: "Produces a narrative-driven market opportunity document in the tradition of the Sequoia company brief. Combines storytelling with framework-derived evidence -- Blue Ocean positioning, product lifecycle analysis, marketing mix, traction signals -- to build a compelling investment thesis. Use when presenting a market opportunity to investors who value narrative clarity as much as analytical rigor." +audience: "investor" +applicable_skills: + - blue-ocean-strategy + - product-life-cycle + - four-ps-marketing + - tipping-point + - net-promoter-score +format: "presentation-outline" +author: "Fatih Guner" +--- + +# Market Opportunity Summary + + + +## [Company Name] + +**[One-line description: what you do, for whom, and why it matters]** + +[Founding Year] | [Location] | [Team Size] | [Stage] + +--- + +### The Problem + + + +[Describe the problem as experienced by a specific person or organization. Who suffers? What does it cost them in money, time, or opportunity?] + +[Why the problem persists. What structural forces prevent existing solutions from solving it? Draw on PEST insights, industry structure, or behavioral patterns.] + +[Quantify it. How many people or organizations face this? What is the aggregate economic cost?] + +--- + +### The Solution + + + +[Company Name] [describe the core mechanism -- not features, but the fundamental approach]. For [target user], this means [transformed experience or outcome in one sentence]. + +[Technology or methodology that enables this -- one paragraph. Investors care about defensibility, not architecture.] + +--- + +### Why Now + + + +The convergence of [number] forces creates a narrow window of opportunity: + +1. **[Force 1 -- e.g., Technology]:** [A specific technology maturation, cost decline, or platform shift.] +2. **[Force 2 -- e.g., Regulatory]:** [A regulation or policy change that creates demand or removes barriers.] +3. **[Force 3 -- e.g., Behavioral]:** [A shift in user behavior or willingness to adopt.] +4. **[Force 4 -- e.g., Economic]:** [A market structure change or budget reallocation that opens spend.] + +--- + +### Market Size + + + +| Layer | Size | Derivation | +|-------|------|------------| +| **TAM** (Total Addressable Market) | $[amount] | [How calculated -- e.g., "X million [entities] x $Y average annual spend on [category]"] | +| **SAM** (Serviceable Available Market) | $[amount] | [Subset you can realistically reach -- by geography, segment, or channel] | +| **SOM** (Serviceable Obtainable Market) | $[amount] | [What you can capture in 3-5 years given current trajectory and resources] | + +**Product lifecycle position:** [Company Name] addresses a market in [introduction / growth / maturity / decline] phase. [One sentence explaining what this means for growth potential and competitive dynamics. Drawn from Product Life Cycle analysis.] + +--- + +### Value Innovation + + + +The industry competes on [list 2-3 standard competitive factors]. [Company Name] breaks this pattern: + +| Action | Factor | Rationale | +|--------|--------|-----------| +| **Eliminate** | [Factor the industry takes for granted that you remove] | [Why removing it reduces cost without sacrificing value] | +| **Reduce** | [Factor you deliberately underinvest in] | [Why the industry over-serves on this dimension] | +| **Raise** | [Factor you elevate beyond industry standard] | [Why this matters disproportionately to your target segment] | +| **Create** | [Factor that did not previously exist in the category] | [The new source of value this introduces] | + +**Net effect:** [One sentence summarizing your differentiated value curve -- e.g., "A solution that costs 60% less to deliver while scoring 3x higher on the dimension customers actually rank first."] + +--- + +### Go-to-Market + + + +**Product:** [Core offering and primary form factor -- SaaS, marketplace, hardware, service.] + +**Price:** [Pricing model, anchor point, and positioning rationale relative to competitors.] + +**Place:** [Primary distribution channel and why it reaches your target segment efficiently.] + +**Promotion:** [Customer acquisition strategy and current economics -- CAC, primary channels, conversion rates.] + +--- + +### Traction + +**Headline metric:** [The single number that best captures momentum -- e.g., "$X ARR growing at Y% MoM"] + +| Metric | Current | 6 Months Ago | Trend | +|--------|---------|-------------|-------| +| [Revenue / ARR / GMV] | $[amount] | $[amount] | [X% growth] | +| [Users / Customers / Accounts] | [count] | [count] | [X% growth] | +| [Retention metric: NRR, logo retention, or churn] | [X%] | [X%] | [Improving / Stable / Declining] | +| [Engagement metric: DAU/MAU, sessions, NPS] | [value] | [value] | [Trend] | + +**Net Promoter Score:** [Score] -- [What the score distribution reveals about product-market fit.] + +--- + +### Tipping Point Dynamics + + + +[Company Name] exhibits [one or two] characteristics of pre-tipping-point markets: + +- **[Dynamic 1 -- e.g., "The Law of the Few"]:** [How influential connectors or mavens drive disproportionate adoption.] +- **[Dynamic 2 -- e.g., "Stickiness Factor"]:** [The specific product characteristic that drives retention and referral. Cite the metric.] + +**Catalyst:** [One sentence on what you believe will trigger nonlinear growth -- and what resources are required to reach that trigger.] + +--- + +### Team + +| Name | Role | Relevant Background | +|------|------|---------------------| +| [Name] | [CEO / CTO / etc.] | [Prior company, domain expertise, or achievement relevant to this venture] | +| [Name] | [Role] | [One sentence] | +| [Name] | [Role] | [One sentence] | + +**Founder-market fit:** [Two sentences explaining why this team's specific experience, relationships, or insight gives them an unfair advantage in this market.] + +--- + +### The Ask + +**Raising:** $[amount] +**Instrument:** [SAFE / Priced Equity / Convertible Note] +**Use of funds:** + +- [X%] -- [Primary allocation and what it achieves] +- [Y%] -- [Secondary allocation and what it achieves] +- [Z%] -- [Tertiary allocation and what it achieves] + +**18-month target:** [Specific milestone this capital enables -- revenue target, customer count, product milestone, or Series A readiness criteria.] + +--- + + diff --git a/plugins/foreman/content/output-templates/investor/strategic-analysis-one-pager.md b/plugins/foreman/content/output-templates/investor/strategic-analysis-one-pager.md new file mode 100644 index 0000000..7a47c63 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/strategic-analysis-one-pager.md @@ -0,0 +1,97 @@ +--- +name: "strategic-analysis-one-pager" +description: "Produces a single-page strategic analysis document for investor audiences. Compresses market structure, competitive position, strategic advantage, key risks, and the investment ask into a dense, scannable format designed for a 3-minute read. Use after completing any major strategic framework analysis to create a concise investor-facing summary." +audience: "investor" +applicable_skills: + - porters-five-forces + - swot-pest-analysis + - blue-ocean-strategy + - business-model-canvas + - growth-share-matrix +format: "one-pager" +author: "Fatih Guner" +--- + +# Strategic Analysis One-Pager + + + +**[Company Name]** | **[Industry/Sector]** | **[Stage: Seed / Series A / Series B / etc.]** | **[Date]** + +--- + +## The Opportunity + + + +[Describe the structural market shift, unmet need, or timing advantage that creates the opportunity. Be specific: cite a regulation, technology inflection, or behavioral change.] + +## Market Structure + + + +| Force / Factor | Assessment | Implication | +|---------------|------------|-------------| +| Barriers to entry | [High / Moderate / Low] | [Why this protects or exposes you] | +| Buyer power | [High / Moderate / Low] | [Concentration risk or diversification strength] | +| Competitive rivalry | [Intense / Moderate / Limited] | [Number of direct competitors; basis of competition] | +| Substitution threat | [High / Moderate / Low] | [Primary substitute and your defense against it] | +| Macro tailwind | [Describe] | [PEST-derived force accelerating your opportunity] | + +## Competitive Position + + + +| Dimension | Your Position | Nearest Competitor | Differentiation | +|-----------|--------------|-------------------|-----------------| +| [Key factor 1, e.g., unit economics] | [Your metric] | [Their metric] | [Why the gap is durable] | +| [Key factor 2, e.g., technology] | [Your capability] | [Their capability] | [Structural advantage] | +| [Key factor 3, e.g., distribution] | [Your channel] | [Their channel] | [Moat or switching cost] | + +**Value innovation summary:** [One sentence from your ERRC Grid or Blue Ocean analysis -- what you eliminate/reduce/raise/create that competitors do not.] + +## Business Model Snapshot + + + +- **Revenue model:** [Subscription / Transaction / Marketplace / Licensing / etc.] -- [Pricing: $X per Y] +- **Unit economics:** LTV $[amount] / CAC $[amount] / Ratio: [X:1] / Payback: [months] +- **Key resource / moat:** [Proprietary data, network effect, regulatory license, etc.] +- **Growth engine:** [Viral / Paid / Content / Sales-led] -- current growth rate: [X% MoM or YoY] + +## Key Risks and Mitigants + + + +| Risk | Severity | Mitigant | +|------|----------|----------| +| [Risk 1, e.g., regulatory change] | [High / Medium] | [Specific action taken or planned] | +| [Risk 2, e.g., customer concentration] | [High / Medium] | [Specific action taken or planned] | +| [Risk 3, e.g., technology dependency] | [High / Medium] | [Specific action taken or planned] | + +## Traction + + + +- **Revenue / ARR:** $[amount] | **Growth:** [X% MoM / YoY] +- **Customers:** [count] | **Retention:** [X% monthly / annual] +- **Pipeline:** $[amount] qualified | **NPS:** [score, if available] + +## The Ask + +**Raising:** $[amount] | **Instrument:** [SAFE / Priced Round / Convertible Note] | **Use of funds:** [Primary allocation, e.g., "70% engineering, 20% GTM, 10% ops"] + +**Target milestone:** [What this capital achieves -- e.g., "$2M ARR and Series A readiness within 18 months"] + +--- + + diff --git a/plugins/foreman/content/output-templates/investor/unit-economics-snapshot.md b/plugins/foreman/content/output-templates/investor/unit-economics-snapshot.md new file mode 100644 index 0000000..2b662b1 --- /dev/null +++ b/plugins/foreman/content/output-templates/investor/unit-economics-snapshot.md @@ -0,0 +1,83 @@ +--- +name: "unit-economics-snapshot" +description: "Produces a one-page unit economics dashboard with eight core metrics: CAC, LTV, LTV:CAC ratio, payback period, gross margin, contribution margin, churn rate, and expansion revenue. Each metric includes its formula, benchmark range, and the specific signals that trigger investor concern. Modeled on a16z's unit economics framework. Use when preparing for investor meetings, board reviews, or internal assessments of business model health." +audience: "investor" +applicable_skills: + - balanced-scorecard + - net-promoter-score + - smart-goals + - growth-share-matrix +format: "dashboard" +author: "Fatih Guner" +--- + +# Unit Economics Snapshot + +Eight numbers determine whether a business model compounds wealth or incinerates capital. Fill every cell with actuals — not projections, not blended averages across dissimilar segments. Delete this paragraph before distribution. + +**[Company Name]** | **Period:** [Month/Quarter, Year] | **Segment:** [All / Enterprise / SMB / Consumer] + +--- + +| # | Metric | Your Value | Formula | Benchmark | Trend | Investor Red Flag | +|---|--------|-----------|---------|-----------|-------|-------------------| +| 1 | **CAC** | $[amount] | Total Sales & Marketing Spend / New Customers (same period) | SaaS B2B: $200-$2K (SMB), $5K-$50K+ (Enterprise) | [Rising / Stable / Declining] | CAC rising faster than revenue per customer; blended CAC hiding channel-level dysfunction; costs not fully loaded | +| 2 | **LTV** | $[amount] | (Avg Revenue Per Account x Gross Margin %) / Revenue Churn Rate | Varies by model; credible only with >12 months cohort data | [Rising / Stable / Declining] | LTV from projected retention, not observed cohorts; assumes zero churn after month 6; expansion baked in without data | +| 3 | **LTV:CAC** | [X]:1 | LTV / CAC | <1:1 destroying value; 1-3:1 early/inefficient; 3-5:1 healthy; >5:1 possibly under-investing | [Improving / Stable / Deteriorating] | Ratio >5:1 at early stage may signal under-spending on growth; projected LTV paired with actual CAC | +| 4 | **Payback Period** | [X] months | CAC / (Monthly Revenue Per Customer x Gross Margin %) | <12 mo strong; 12-18 acceptable at Series A; >24 requires justification | [Shortening / Stable / Lengthening] | Payback longer than average customer lifespan; calculated on gross revenue, not contribution margin | +| 5 | **Gross Margin** | [X]% | (Revenue - COGS) / Revenue x 100 | Software: 70-85%; Marketplace: 40-70%; Hardware: 30-60% | [Expanding / Stable / Compressing] | Excludes material delivery costs (CS headcount, usage-scaled infra); compression with no improvement path | +| 6 | **Contribution Margin** | [X]% | (Revenue - COGS - Variable S&M) / Revenue x 100 | Positive = minimum viability; >20% = model sustains fixed-cost leverage at scale | [Expanding / Stable / Compressing] | Negative post-seed with no timeline to positive; relies on undemonstrated scale economies | +| 7 | **Churn** | Logo: [X]%/mo Revenue: [X]%/mo NRR: [X]%/yr | Logo: Lost / Starting. Revenue: MRR Lost / Starting MRR. NRR: (Start - Churn + Expansion) / Start | Monthly logo <2% (SMB), <1% (Enterprise); NRR >100%; best-in-class 120-140% | [Improving / Stable / Worsening] | Reporting only logo churn when revenue churn differs; NRR <100% at Series A; no cohort analysis | +| 8 | **Expansion Revenue** | $[amount]/mo ([X]% of new MRR) | Expansion MRR / Total New MRR | >30% from expansion signals strong PMF; best: expansion alone exceeds churn | [Accelerating / Stable / Decelerating] | No expansion mechanism by Series A; driven by price increases, not usage; concentrated in 1-2 accounts | + +--- + +## COGS Composition + + + +| Cost Category | Monthly Amount | % of Revenue | Included in Gross Margin? | +|--------------|---------------|-------------|--------------------------| +| Hosting / Infrastructure | $[amount] | [X]% | Yes | +| Customer support labor | $[amount] | [X]% | [Yes / No — state reasoning] | +| Third-party APIs | $[amount] | [X]% | Yes | +| Payment processing | $[amount] | [X]% | Yes | +| [Other] | $[amount] | [X]% | [Yes / No] | + +--- + +## Summary Dashboard + +| Metric | Current | Prior Period | Benchmark | Status | +|--------|---------|-------------|-----------|--------| +| CAC | $[amount] | $[amount] | $[range] | [On track / Watch / Action needed] | +| LTV | $[amount] | $[amount] | $[range] | | +| LTV:CAC | [X]:1 | [X]:1 | 3-5:1 | | +| Payback | [X] mo | [X] mo | <18 mo | | +| Gross Margin | [X]% | [X]% | [range]% | | +| Contribution Margin | [X]% | [X]% | >20% | | +| Monthly Churn | [X]% | [X]% | <2% | | +| Net Revenue Retention | [X]% | [X]% | >100% | | + +## Cohort Retention + +| Cohort | Month 1 | Month 3 | Month 6 | Month 12 | Current | +|--------|---------|---------|---------|----------|---------| +| [Q1 20XX] | [%] | [%] | [%] | [%] | [%] | +| [Q2 20XX] | [%] | [%] | [%] | | | +| [Q3 20XX] | [%] | [%] | | | | + +**Cohort narrative:** [Two sentences. Are newer cohorts retaining better? What changed — product, targeting, or pricing?] + +--- + +## Methodology Notes + +- **CAC fully loaded?** [Yes / No — if no, list excluded costs and rationale] +- **LTV cohort vintage:** [Oldest cohort used, months of observation data] +- **Churn measurement:** [Logo churn = customer count. Revenue churn = MRR-weighted. State which is primary.] +- **Segment breakout:** [If economics differ materially by segment, prepare separate snapshots. Blended metrics across SMB and Enterprise obscure more than they reveal.] + +--- + +*Data as of [Date]. Methodology and raw calculations available in [data room / appendix]. Definitions follow a16z / SaaS Capital standards unless noted.* diff --git a/plugins/foreman/content/output-templates/self/annual-review-and-planning.md b/plugins/foreman/content/output-templates/self/annual-review-and-planning.md new file mode 100644 index 0000000..60dba3d --- /dev/null +++ b/plugins/foreman/content/output-templates/self/annual-review-and-planning.md @@ -0,0 +1,195 @@ +--- +name: "annual-review-and-planning" +description: "Produces a two-part year-end document: a rigorous review of the year that closed and a strategic plan for the year ahead. The review examines achievements, failures, lessons, relationships, finances, and personal growth with the honesty most annual reflections avoid. The plan establishes a single-word theme, defines professional and personal goals, sets quarterly milestones, identifies skills to develop, and commits to one bold bet. Inspired by YearCompass and Jim Collins's personal strategy frameworks. Use in the final two weeks of December or the first week of January -- the window where reflection is still fresh and ambition has not yet been domesticated by routine." +audience: "self" +applicable_skills: + - balanced-scorecard + - smart-goals + - wanting-what-matters + - career-strategy-for-leaders + - stoic-mortality-and-perspective +format: "review-and-plan" +author: "Fatih Guner" +--- + +# Annual Review and Planning + + + +**Year in review:** [YYYY] + +**Year ahead:** [YYYY] + +**Date completed:** [Date] + +--- + +# Part I: Review + +## Key Achievements + +_Name five to seven outcomes -- not activities -- that moved your life or business forward in a measurable way. If you cannot name five, that is itself a finding._ + +1. [Achievement] -- Impact: [What changed as a result] +2. [Achievement] -- Impact: [What changed] +3. [Achievement] -- Impact: [What changed] +4. [Achievement] -- Impact: [What changed] +5. [Achievement] -- Impact: [What changed] + +**Which of these would you repeat the process for, knowing the full cost?** [Identify the achievements where the effort-to-outcome ratio was genuinely worth it.] + +## Biggest Failures + +_Three failures. Real ones -- not "I worked too hard" or other disguised brags. The failures you still wince about when the room is quiet._ + +1. **[Failure]:** What happened: [Facts] | Root cause: [Your honest diagnosis] | What it cost: [Time, money, trust, opportunity] +2. **[Failure]:** What happened: [Facts] | Root cause: [Diagnosis] | What it cost: [Cost] +3. **[Failure]:** What happened: [Facts] | Root cause: [Diagnosis] | What it cost: [Cost] + +**Pattern check:** Do these failures share a common cause -- overcommitment, avoidance, wrong people, poor judgment on timing? [One sentence.] + +## Lessons Learned + +_Lessons that changed behavior, not merely beliefs. A lesson that did not alter a decision or habit remained an observation._ + +| # | Lesson | Evidence (what taught me this) | Behavior change it produced | +|---|--------|-------------------------------|---------------------------| +| 1 | [Lesson] | [Specific event or pattern] | [What I now do differently] | +| 2 | [Lesson] | [Event or pattern] | [Behavior change] | +| 3 | [Lesson] | [Event or pattern] | [Behavior change] | + +## Relationships Built and Lost + +**Relationships that strengthened or formed:** + +- [Name] -- How: [What deepened the relationship] | Value: [What this person now means to your trajectory] +- [Name] -- How: [Context] | Value: [Significance] +- [Name] -- How: [Context] | Value: [Significance] + +**Relationships that weakened or ended:** + +- [Name] -- What happened: [Honest assessment -- was this drift, conflict, or a deliberate choice?] | Regret level: [None / Some / Significant] +- [Name] -- What happened: [Assessment] | Regret level: [Level] + +**Net assessment:** Is your relationship portfolio stronger or weaker than twelve months ago? [One to two sentences.] + +## Financial Snapshot + +| Metric | Start of year | End of year | Delta | Assessment | +|--------|--------------|-------------|-------|-----------| +| Net worth / Company valuation | [Value] | [Value] | [+/- %] | [On track / Behind / Ahead] | +| Annual revenue / Income | [Value] | [Value] | [+/- %] | [Assessment] | +| Savings rate / Runway | [Value] | [Value] | [Change] | [Assessment] | +| Debt | [Value] | [Value] | [Change] | [Assessment] | + +**Financial surprise of the year:** [The expense, windfall, or trend you did not anticipate.] + +## Personal Growth Assessment + +Rate yourself honestly. A score of 5 across the board signals self-deception, not excellence. + +| Dimension | Rating (1-5) | Evidence for this rating | +|-----------|-------------|------------------------| +| Physical health and energy | [ /5] | [Specific: fitness, sleep, medical markers] | +| Mental clarity and focus | [ /5] | [Specific: sustained attention, decision quality] | +| Emotional resilience | [ /5] | [Specific: how you handled the worst moment of the year] | +| Key relationships (personal) | [ /5] | [Specific: depth, not quantity] | +| Professional capability | [ /5] | [Specific: skills acquired, confidence in new domains] | +| Purpose and fulfillment | [ /5] | [Specific: did the work feel meaningful more often than not?] | + +## Highlight and Lowlight + +**Highlight of the year:** [One moment. Not the biggest achievement -- the moment that felt most alive, most right, most worth remembering.] + +[Two to three sentences on what made it significant.] + +**Lowlight of the year:** [One moment. The point of greatest pain, doubt, or regret.] + +[Two to three sentences on what it revealed about you.] + +--- + +# Part II: Plan + +## Theme for the Year + +_One word. Not a slogan, not an aspiration -- a filter. Every significant decision in the coming year should be tested against this word. Jim Collins calls it the "stop doing" list's complement: the one thing that earns a disproportionate "yes."_ + +**Theme:** [One word -- e.g., "Depth," "Courage," "Simplify," "Build," "Release"] + +**Why this word:** [Two to three sentences connecting the theme to what Part I revealed.] + +## Professional Goals + +_Three goals. Each must be specific enough that a stranger could assess whether you achieved it._ + +| # | Goal | Success metric | Deadline | Why this matters now | +|---|------|---------------|----------|---------------------| +| 1 | [Goal] | [Measurable outcome] | [Date] | [Connection to review findings or strategic direction] | +| 2 | [Goal] | [Measurable outcome] | [Date] | [Why now] | +| 3 | [Goal] | [Measurable outcome] | [Date] | [Why now] | + +## Personal Goals + +| # | Goal | Success metric | Deadline | Why this matters now | +|---|------|---------------|----------|---------------------| +| 1 | [Goal] | [Measurable outcome] | [Date] | [Connection to personal growth assessment] | +| 2 | [Goal] | [Measurable outcome] | [Date] | [Why now] | +| 3 | [Goal] | [Measurable outcome] | [Date] | [Why now] | + +## Quarterly Milestones + +_Break the year into four checkpoints. Vague annual goals die in February. Quarterly milestones survive._ + +| Quarter | Professional milestone | Personal milestone | Review date | +|---------|----------------------|-------------------|-------------| +| Q1 (Jan-Mar) | [Specific deliverable or outcome] | [Specific outcome] | [Date] | +| Q2 (Apr-Jun) | [Specific deliverable or outcome] | [Specific outcome] | [Date] | +| Q3 (Jul-Sep) | [Specific deliverable or outcome] | [Specific outcome] | [Date] | +| Q4 (Oct-Dec) | [Specific deliverable or outcome] | [Specific outcome] | [Date] | + +## Skills to Develop + +| Skill | Why (linked to goals) | Method | Time commitment | Mastery indicator | +|-------|----------------------|--------|----------------|-------------------| +| [Skill] | [Which goal this serves] | [Course, mentor, practice, project] | [Hours per week] | [How you will know you have improved] | +| [Skill] | [Goal link] | [Method] | [Time] | [Indicator] | +| [Skill] | [Goal link] | [Method] | [Time] | [Indicator] | + +## Habits to Build and Break + +**Build:** + +1. [Habit] -- Trigger: [When/where] | Minimum viable version: [The smallest unit of this habit that still counts] | Tracking method: [How you will monitor consistency] +2. [Habit] -- Trigger: [When/where] | Minimum version: [Smallest unit] | Tracking: [Method] + +**Break:** + +1. [Habit to stop] -- Replacement behavior: [What you will do instead] | Environmental change: [What you will remove or rearrange to make the old habit harder] +2. [Habit to stop] -- Replacement: [Alternative] | Environmental change: [What changes] + +## One Bold Bet + +_The goal that scares you. The one where failure is a real possibility and success would change your trajectory. A year without a bold bet is a year of maintenance._ + +**The bet:** [State it plainly.] + +**What success looks like:** [Specific outcome.] + +**What failure looks like:** [Specific outcome -- and why it is survivable.] + +**First concrete step (this week):** [The action that converts intention into motion.] + +--- + +**Accountability partner:** [Name -- the person who will see this document and ask uncomfortable questions about it in March, June, September, and December.] + +**Next review checkpoint:** [Date -- set the Q1 calendar invite now.] diff --git a/plugins/foreman/content/output-templates/self/career-strategy-canvas.md b/plugins/foreman/content/output-templates/self/career-strategy-canvas.md new file mode 100644 index 0000000..cdbbaf3 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/career-strategy-canvas.md @@ -0,0 +1,180 @@ +--- +name: "career-strategy-canvas" +description: "Produces a personal career strategy document that applies business strategy frameworks to individual career development. Covers current position audit, strengths and gaps analysis, target role definition, 3-year milestones, skill development plan, network strategy, risk factors, and personal board of directors. Use annually or at career inflection points -- promotions, job changes, or when growth has stalled." +audience: "self" +applicable_skills: + - career-strategy-for-leaders + - leadership-pipeline + - senior-leadership-transition + - purpose-driven-leadership + - building-thinking-strength +format: "canvas" +author: "Fatih Guner" +--- + +# Career Strategy Canvas + + + +**Name:** [Your name] | **Current role:** [Title, organization] | **Date:** [Date] + +**Canvas version:** [1.0 -- increment with each annual revision] + +--- + +## 1. Current Position Audit + +_Where you stand today. Not where you wish you stood._ + +**Role tenure:** [Years/months in current role] + +**Scope:** [What you control -- budget size, team size, P&L responsibility, geographic scope] + +**Performance trajectory:** [ ] Accelerating [ ] Steady [ ] Plateauing [ ] Declining + +**Honest assessment: Am I being developed here, or am I developing here on my own?** +[One sentence. The distinction matters.] + +**What does my organization value me for?** +[The thing they would miss most if you left tomorrow. This may differ from what you want to be valued for.] + +**What am I overinvesting in that yields diminishing returns?** +[The activity or skill where additional effort no longer moves the needle.] + +## 2. Strengths and Gaps + +_Map yourself with the same objectivity you would apply to evaluating a business unit._ + +**Distinctive strengths (things I do better than most people at my level):** + +1. [Strength] -- Evidence: [Specific accomplishment or feedback that proves this] +2. [Strength] -- Evidence: [Specific accomplishment or feedback] +3. [Strength] -- Evidence: [Specific accomplishment or feedback] + +**Functional gaps (skills or knowledge I lack for my target role):** + +| Gap | Severity for target role | Current level | Required level | How to close | +|-----|------------------------|---------------|----------------|-------------| +| [Skill or knowledge area] | [Critical / Important / Nice-to-have] | [Novice / Competent / Proficient] | [Proficient / Expert] | [Method] | +| [Skill or knowledge area] | [Critical / Important / Nice-to-have] | [Level] | [Level] | [Method] | +| [Skill or knowledge area] | [Critical / Important / Nice-to-have] | [Level] | [Level] | [Method] | + +**Leadership gaps (behavioral or relational patterns that limit me):** + +1. [Pattern] -- How it manifests: [Specific behavior] -- Cost: [What it prevents] +2. [Pattern] -- How it manifests: [Specific behavior] -- Cost: [What it prevents] + +**Blind spot check: What feedback have I received repeatedly that I have not yet internalized?** + +[Write it down, even if you disagree. Especially if you disagree.] + +## 3. Target Role / Identity + +_Not a job title -- a description of the leader you intend to become._ + +**Target role (3 years out):** [Title or role description] + +**Target organization type:** [Current company / Larger company / Startup / Own venture / Portfolio career / Other] + +**What does this role demand that my current role does not?** +- [Capability or responsibility gap 1] +- [Capability or responsibility gap 2] +- [Capability or responsibility gap 3] + +**Why this role and not an alternative?** +[Two to three sentences. Connect this choice to your values, strengths, and the market reality you see.] + +**What must I give up to get there?** +[Every transition has a cost. Name it: comfort, certainty, income, status, location, relationships.] + +## 4. Three-Year Milestones + +_Work backward from the target. Each milestone should be verifiable, not aspirational._ + +| Year | Milestone | Evidence of completion | Key enabler | +|------|-----------|----------------------|-------------| +| Year 1 | [What must be true 12 months from now] | [How you will know] | [What makes this possible] | +| Year 2 | [What must be true 24 months from now] | [How you will know] | [What makes this possible] | +| Year 3 | [Target role achieved or positioned for it] | [How you will know] | [What makes this possible] | + +**Critical path:** What is the single most important thing that must happen in Year 1 to make Years 2-3 possible? + +[One sentence.] + +## 5. Skill Development Plan + +_Select the top 3 gaps from Section 2. Design a deliberate learning strategy for each._ + +**Skill 1: [Name]** +- Learning method: [Course / Stretch assignment / Mentorship / Project / Reading / Coaching] +- Specific commitment: [e.g., "Complete X certification by Q3" or "Lead the Y project to gain Z experience"] +- Time investment: [Hours per week or total hours] +- Completion marker: [How you will know the gap is closed] + +**Skill 2: [Name]** +- Learning method: [Method] +- Specific commitment: [Commitment] +- Time investment: [Investment] +- Completion marker: [Marker] + +**Skill 3: [Name]** +- Learning method: [Method] +- Specific commitment: [Commitment] +- Time investment: [Investment] +- Completion marker: [Marker] + +## 6. Network Strategy + +_Your network is not a contact list. It is a strategic asset that either accelerates or constrains your trajectory._ + +**Current network composition:** + +| Category | People I have access to | Gap | +|----------|------------------------|-----| +| Sponsors (advocate for me when I am not in the room) | [Names or count] | [Who is missing?] | +| Mentors (advise me from experience) | [Names or count] | [What perspective am I lacking?] | +| Peers (challenge and sharpen my thinking) | [Names or count] | [Where am I in an echo chamber?] | +| Connectors (bridge me to new domains or industries) | [Names or count] | [Which domain am I blind to?] | +| Experts (deep knowledge in areas I need) | [Names or count] | [Which expertise gap is most urgent?] | + +**Three relationships to build or deepen this year:** + +1. [Name or type] -- Why: [What this relationship unlocks] -- First step: [Specific action] +2. [Name or type] -- Why: [What this relationship unlocks] -- First step: [Specific action] +3. [Name or type] -- Why: [What this relationship unlocks] -- First step: [Specific action] + +## 7. Risk Factors + +_Every strategy has failure modes. Name them._ + +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|-----------| +| [e.g., Current company restructures, eliminating my growth path] | [H / M / L] | [H / M / L] | [Contingency] | +| [e.g., Target skill takes longer to develop than planned] | [H / M / L] | [H / M / L] | [Contingency] | +| [e.g., Family or health circumstances change priorities] | [H / M / L] | [H / M / L] | [Contingency] | +| [e.g., Market shifts make target role less viable] | [H / M / L] | [H / M / L] | [Contingency] | + +## 8. Personal Board of Directors + +_Assemble 3-5 people who will hold you accountable to this strategy. Not cheerleaders -- people who will tell you when you are drifting._ + +| Role | Name | What they provide | How often you engage | Next meeting | +|------|------|-------------------|---------------------|-------------| +| Chair (primary accountability partner) | [Name] | [Honest assessment, push-back] | [Frequency] | [Date] | +| Domain expert | [Name] | [Technical or industry guidance] | [Frequency] | [Date] | +| Outside perspective | [Name] | [View from a different industry or function] | [Frequency] | [Date] | +| Sponsor / Advocate | [Name] | [Organizational access, visibility] | [Frequency] | [Date] | + +--- + +**Annual review date:** [Set a specific date -- e.g., first week of January] + +**One question to answer at next review:** Am I closer to the Year 1 milestone, or have I been busy without progressing? diff --git a/plugins/foreman/content/output-templates/self/decision-journal.md b/plugins/foreman/content/output-templates/self/decision-journal.md new file mode 100644 index 0000000..fe794f5 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/decision-journal.md @@ -0,0 +1,120 @@ +--- +name: "decision-journal" +description: "Produces a structured decision journal entry for capturing the reasoning, context, and emotional state behind a single significant decision. Designed for review in 90 days to calibrate judgment over time. Based on decision science best practices from Annie Duke, Philip Tetlock, and Gary Klein. Use before or immediately after making any decision with meaningful consequences." +audience: "self" +applicable_skills: + - evaluating-and-deciding + - enemies-of-clear-thinking + - decision-traps-and-roles + - wanting-what-matters +format: "journal-entry" +author: "Fatih Guner" +--- + +# Decision Journal Entry + + + +**Decision ID:** [YYYY-MM-DD-short-label, e.g., 2026-03-26-hire-vp-eng] + +**Date of decision:** [Date] + +**Review date:** [Date + 90 days] + +--- + +## The Decision + +_State it plainly. One to two sentences._ + +[What are you deciding to do? Be specific enough that a stranger could verify whether you followed through.] + +## Context + +_What is the situation that forced this decision? Capture enough detail that you will remember the circumstances in 90 days, when memory has faded and outcome bias has taken hold._ + +- **What triggered this decision?** [The event, deadline, or conversation that made this decision necessary now] +- **Time pressure:** [None / Low / Moderate / High / Extreme] -- [Explain] +- **Reversibility:** [Easily reversible / Reversible with cost / Partially reversible / Irreversible] +- **Stakes:** [What is at risk if this goes wrong? Be specific: money, relationships, time, reputation, opportunity cost] + +## Alternatives Considered + +_List every option you genuinely evaluated, not just the ones that made the final cut. Include "do nothing" if it was a real option._ + +| Option | Key advantage | Key disadvantage | Why rejected or selected | +|--------|-------------|-----------------|------------------------| +| **[Chosen option]** | [Primary upside] | [Primary downside] | **Selected** -- [Core reason] | +| [Alternative 1] | [Primary upside] | [Primary downside] | [Why not chosen] | +| [Alternative 2] | [Primary upside] | [Primary downside] | [Why not chosen] | +| [Do nothing / Status quo] | [What you preserve] | [What you forgo] | [Why not chosen] | + +## Reasoning + +_The core logic behind your choice. Write this as though explaining to a skeptical peer, not a sympathetic friend._ + +**The argument for this decision:** +[Two to four sentences. What is the strongest case?] + +**The strongest argument against it:** +[Two to four sentences. What would a thoughtful opponent say? If you cannot articulate this clearly, you may not have considered it deeply enough.] + +**What would have to be true for this decision to fail?** +[Identify the key assumptions. These are your pre-mortem indicators.] + +## Confidence and Probabilities + +_Calibrate your certainty. Overconfident decision-makers improve only when they track their confidence against outcomes._ + +- **Probability this produces the desired outcome:** [X%] +- **Confidence in my information quality:** [Low / Moderate / High] +- **Confidence in my reasoning process:** [Low / Moderate / High] + +## Emotional State + +_Decisions made under strong emotion deserve extra scrutiny. This section exists to flag, not to judge._ + +- **Dominant emotion at time of decision:** [e.g., excitement, anxiety, frustration, calm, urgency, relief] +- **Am I deciding to move toward something or away from something?** [Toward / Away] +- **Have I been influenced by any recent vivid experience?** [Yes -- describe / No] +- **Would I make the same decision if I had to explain it publicly?** [Yes / No -- why?] + +## Expected Outcome + +_Write this in concrete, verifiable terms. Your 90-day review will compare prediction to reality._ + +**If this decision succeeds, I expect the following by [date]:** +1. [Specific, observable outcome] +2. [Specific, observable outcome] + +**Early indicators of success (within 30 days):** +- [Signal to watch for] + +**Early indicators of failure (within 30 days):** +- [Signal to watch for] + +--- + +## 90-Day Review Addendum + +_Complete this section on or after the review date. Do not modify anything above._ + +**Review date:** [Actual date of review] + +**What actually happened:** +[Factual outcome] + +**Was the outcome better, worse, or different from expected?** +[Better / Worse / Different -- explain] + +**Was the reasoning sound even if the outcome was poor (or lucky even if the reasoning was flawed)?** +[Separate process quality from outcome quality] + +**What would I do differently with the same information I had then (not what I know now)?** +[This is the only question that improves future decisions] diff --git a/plugins/foreman/content/output-templates/self/founder-mental-health-check.md b/plugins/foreman/content/output-templates/self/founder-mental-health-check.md new file mode 100644 index 0000000..5ff6f68 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/founder-mental-health-check.md @@ -0,0 +1,184 @@ +--- +name: "founder-mental-health-check" +description: "Produces a structured self-assessment for founder and CEO wellbeing, covering energy levels, sleep quality, social isolation, decision fatigue, burnout indicators, and relationship health. Not therapy -- a systematic early-warning system. Inspired by Dr. Michael Freeman's research on founder mental health prevalence rates and adapted from the Maslach Burnout Inventory's three dimensions (exhaustion, cynicism, reduced efficacy). Use weekly or biweekly to detect patterns before they become crises." +audience: "self" +applicable_skills: + - leader-resilience-and-wellbeing + - stoic-fortitude-and-resilience + - maslow-hierarchy + - stoic-control-and-clarity + - emotional-courage +format: "self-assessment" +author: "Fatih Guner" +--- + +# Founder Mental Health Check + + + +**Date:** [Date] | **Week #:** [Sequential check-in number] + +--- + +## 1. Energy Audit + +_Rate each dimension for the past 7 days. A 10 means fully resourced; a 1 means depleted beyond function. Most founders overrate physical and underrate emotional._ + +| Dimension | Score (1-10) | Trend vs. last check | Primary drain | +|-----------|-------------|---------------------|---------------| +| **Physical** (sleep, exercise, nutrition, illness) | [ /10] | [up / down / flat] | [What consumed the most physical energy?] | +| **Mental** (focus, clarity, ability to think strategically) | [ /10] | [up / down / flat] | [What consumed the most cognitive bandwidth?] | +| **Emotional** (patience, resilience, mood stability) | [ /10] | [up / down / flat] | [What caused the most emotional weight?] | + +**Composite score:** [ /30] | **Previous composite:** [ /30] + +_Below 15: amber zone. Below 10: red zone. The composite matters more than any single dimension because depletion compounds across categories._ + +--- + +## 2. Sleep + +_Sleep is the leading indicator. Everything downstream -- judgment, patience, creativity, physical health -- degrades when sleep does._ + +- **Average hours per night (past 7 days):** [X hours] +- **Sleep quality:** [ ] Restorative [ ] Adequate [ ] Fragmented [ ] Poor +- **Falling asleep difficulty:** [ ] None [ ] Occasional [ ] Most nights +- **Waking in the night with work thoughts:** [ ] Never [ ] Sometimes [ ] Regularly +- **Do you feel rested upon waking?** [ ] Yes [ ] Sometimes [ ] No + +**If sleep has degraded, what changed?** [Be specific: a deadline, a conflict, a financial concern, a habit.] + +--- + +## 3. Isolation Index + +_Dr. Freeman's research identifies social isolation as the single strongest predictor of founder mental health deterioration. This section exists to make the invisible visible._ + +**When did you last have a conversation with someone outside work about something other than work?** + +- [ ] Today or yesterday +- [ ] Within the past 3 days +- [ ] Within the past week +- [ ] More than a week ago +- [ ] Cannot remember + +**When did you last spend unstructured time with a friend -- no agenda, no networking?** + +- [ ] This week +- [ ] Within the past 2 weeks +- [ ] Within the past month +- [ ] More than a month ago + +**When did you last laugh -- genuinely, not performatively?** + +[Date or "I don't remember." Both answers are data.] + +**Isolation risk level:** [ ] Low (regular non-work contact) [ ] Moderate (slipping) [ ] High (functionally isolated) + +--- + +## 4. Decision Fatigue Indicators + +_Every decision -- trivial or consequential -- draws from the same cognitive reservoir. Founders make hundreds daily. Track the symptoms, not the cause._ + +Check all that apply in the past 7 days: + +- [ ] Avoided or deferred a decision I knew needed to be made +- [ ] Made a significant decision impulsively to "just get it done" +- [ ] Felt overwhelmed by choices that would normally feel manageable +- [ ] Defaulted to the easiest option rather than the best one +- [ ] Snapped at someone over something minor +- [ ] Could not prioritize -- everything felt equally urgent or equally unimportant + +**Count of items checked:** [ /6] + +_0-1: Normal operating range. 2-3: Elevated -- simplify your decision load this week. 4+: Acute fatigue -- delegate, cancel, or postpone everything non-essential for 48 hours._ + +--- + +## 5. Burnout Warning Signs + +_Adapted from the Maslach Burnout Inventory's three dimensions. Burnout is not dramatic collapse -- it is gradual erosion of engagement, masked by busyness._ + +### Exhaustion + +- [ ] Working more hours but accomplishing less +- [ ] Dreading the start of the workday +- [ ] Physical symptoms without clear medical cause (headaches, tension, stomach issues) + +### Cynicism + +- [ ] Feeling detached from the company's mission or customers +- [ ] Internally dismissive of team members' contributions or concerns +- [ ] Sarcasm or irritability replacing curiosity in conversations + +### Reduced efficacy + +- [ ] Doubting whether my work makes a difference +- [ ] Feeling like an imposter despite evidence of competence +- [ ] Losing confidence in decisions I would have made easily six months ago + +**Dimensions showing signals:** [ ] Exhaustion [ ] Cynicism [ ] Reduced efficacy [ ] None + +_One dimension activated: monitor closely. Two dimensions: intervene now -- adjust workload, seek support, take recovery time. Three dimensions: burnout is likely in progress. Professional support is warranted._ + +--- + +## 6. Relationship Health + +_The relationships that sustain you outside of work are the first thing founders sacrifice and the last thing they repair._ + +- **Have I been present -- not just physically, but attentionally -- with my partner/family this week?** [ ] Yes [ ] Partially [ ] No [ ] N/A +- **Have I broken a personal commitment (dinner, event, promise) for work reasons?** [ ] No [ ] Once [ ] Multiple times +- **Would the people closest to me say I have been available to them?** [ ] Yes [ ] Probably not [ ] Definitely not +- **Am I carrying resentment toward someone close because they "don't understand the pressure"?** [ ] No [ ] Somewhat [ ] Yes + +**One specific relationship that needs attention:** [Name and one sentence on what is needed.] + +--- + +## 7. The Thing I Am Avoiding + +_There is almost always one. Name it. The act of writing it reduces its power._ + +**What am I avoiding right now?** + +[Describe it plainly. A conversation, a decision, a financial reality, a health concern, a relationship issue.] + +**What is the cost of continued avoidance?** + +[One to two sentences. Be honest about what compounds.] + +**What is the smallest possible step I could take toward it this week?** + +[Not the full resolution. The first move.] + +--- + +## 8. This Week's Action + +_One commitment. Small enough to execute, specific enough to verify._ + +**I will:** [Concrete action -- e.g., "Take Wednesday evening completely off work" or "Call [name] and talk about something other than the company" or "Sleep 7+ hours for 4 of the next 7 nights"] + +**By when:** [Date] + +**Previous check-in's commitment -- did I follow through?** [ ] Yes [ ] Partially [ ] No + +--- + +**Pattern check (review every 4th entry):** + +- Are my composite energy scores trending down? +- Has the isolation index worsened over the past month? +- Am I checking the same burnout boxes repeatedly? +- Is the same "thing I am avoiding" appearing entry after entry? + +_If the answer to two or more of these is yes, this is no longer a weekly fluctuation. Consider speaking with a coach, therapist, or trusted peer. Strength is not endurance without limit -- it is knowing when the system needs repair._ diff --git a/plugins/foreman/content/output-templates/self/leadership-reflection.md b/plugins/foreman/content/output-templates/self/leadership-reflection.md new file mode 100644 index 0000000..dd80189 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/leadership-reflection.md @@ -0,0 +1,136 @@ +--- +name: "leadership-reflection" +description: "Produces a structured leadership self-examination for weekly or monthly use. Three-part framework: events (what happened), patterns (what I notice about myself), and commitments (what I will do differently). Draws on Stoic evening review practice, Johari Window self-awareness, and executive coaching methodology. Use at the end of each week or month as a deliberate practice of self-knowledge." +audience: "self" +applicable_skills: + - leader-self-reflection + - stoic-self-awareness + - johari-window + - covey-seven-habits + - stoic-control-and-clarity +format: "reflection" +author: "Fatih Guner" +--- + +# Leadership Reflection + + + +**Period:** [ ] Weekly: [Week of MM/DD] | [ ] Monthly: [Month YYYY] + +**Date of reflection:** [Date] + +--- + +## Part 1: Events + +_What happened. Stay factual. Record the moments that carried weight -- decisions, conversations, conflicts, wins, and failures. Resist the urge to interpret; that comes in Part 2._ + +**The most consequential decision I made this period:** + +[Describe it briefly. What did I decide, and what was at stake?] + +**A moment I handled well:** + +[Describe a specific interaction or decision where my leadership made a positive difference. What did I do, concretely?] + +**A moment I handled poorly or avoided:** + +[Describe a specific interaction, decision, or conversation I mishandled or deferred. Be precise -- vague self-criticism teaches nothing.] + +**Something I observed about my team that I have not yet acted on:** + +[A pattern, tension, or opportunity I noticed but have not addressed.] + +**An unexpected challenge and how I responded:** + +[What was it, and what does my response reveal about my defaults under pressure?] + +--- + +## Part 2: Patterns + +_Step back from the events. What do they reveal about how you lead? Use the Johari Window frame: what is in your open area (known to you and others), your blind spot (known to others but not you), your hidden area (known to you but concealed), and your unknown (discovered only through honest reflection or feedback)?_ + +**What pattern do I see in my behavior this period?** + +[e.g., "I defaulted to solving problems myself rather than coaching my direct reports to solve them." or "I avoided the difficult conversation with X for the third consecutive week."] + +**Which of the four Stoic control categories consumed most of my energy?** + +- [ ] Things fully within my control (my actions, my responses, my effort) +- [ ] Things partially within my influence (others' behavior, team dynamics, organizational decisions) +- [ ] Things outside my control that I worried about anyway (market conditions, competitor moves, board decisions) + +**What does this distribution tell me?** + +[One to two sentences.] + +**Covey quadrant check -- where did my time actually go?** + +- [ ] Quadrant I: Urgent + Important (crises, firefighting) +- [ ] Quadrant II: Not Urgent + Important (strategy, relationships, development) +- [ ] Quadrant III: Urgent + Not Important (interruptions, most emails, others' priorities) +- [ ] Quadrant IV: Not Urgent + Not Important (busywork, avoidance activities) + +**Was I leading from Quadrant II this period, or was I pulled elsewhere?** + +[One to two sentences on what pulled you off-center and why you allowed it.] + +**Feedback I received (or should have sought):** + +[What did others tell me -- directly or indirectly -- about my leadership? If the answer is "nothing," that itself is a signal.] + +--- + +## Part 3: Commitments + +_Not resolutions. Commitments are specific, bounded, and verifiable. Choose one from each category below. Three total._ + +**One thing I will START doing:** + +- **What:** [Specific behavior or practice] +- **Why:** [Which pattern from Part 2 this addresses] +- **First action:** [What I will do within 48 hours to begin] +- **How I will know:** [Observable evidence that I followed through] + +**One thing I will STOP doing:** + +- **What:** [Specific behavior or habit to eliminate] +- **Why:** [Which pattern from Part 2 this addresses] +- **Replacement behavior:** [What I will do instead when the impulse arises] +- **Accountability:** [Who will I tell, or how will I track this?] + +**One thing I will CONTINUE doing:** + +- **What:** [Specific behavior that is working and deserves deliberate reinforcement] +- **Why:** [What positive outcome it produced this period] +- **How I will protect it:** [What threatens this practice, and how I will guard the space for it] + +--- + +## Closing + +_Answer one of the following. Rotate each period._ + +- [ ] If I were coaching someone who led exactly as I did this period, what would I tell them? +- [ ] What am I avoiding, and what is the cost of continued avoidance? +- [ ] What would the leader I aspire to become do differently than what I did this period? + +[Three to five sentences. Write to your future self.] + +--- + +**Previous commitments check:** Did I follow through on last period's three commitments? + +| Commitment | Followed through? | Notes | +|-----------|-------------------|-------| +| [From last entry: START] | [ ] Yes [ ] Partially [ ] No | [Brief explanation] | +| [From last entry: STOP] | [ ] Yes [ ] Partially [ ] No | [Brief explanation] | +| [From last entry: CONTINUE] | [ ] Yes [ ] Partially [ ] No | [Brief explanation] | diff --git a/plugins/foreman/content/output-templates/self/learning-plan.md b/plugins/foreman/content/output-templates/self/learning-plan.md new file mode 100644 index 0000000..5200697 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/learning-plan.md @@ -0,0 +1,198 @@ +--- +name: "learning-plan" +description: "Produces a structured personal skill development plan anchored to current role demands. Includes a gap analysis rating each required skill against current proficiency, prioritized learning objectives for the quarter, specific methods per skill (books, courses, mentors, deliberate practice, stretch projects), weekly time allocation, accountability structures, and 30/60/90-day milestones. Use when stepping into a new role, preparing for a promotion, addressing feedback on capability gaps, or when the gap between what your job demands and what you can deliver starts producing visible strain." +audience: "self" +applicable_skills: + - learning-agility + - growth-mindset + - career-strategy-for-leaders + - building-thinking-strength + - covey-seven-habits +format: "plan" +author: "Fatih Guner" +--- + +# Learning Plan + + + +**Name:** [Your name] + +**Current role:** [Title and organization] + +**Date created:** [Date] + +**Quarter covered:** [Q_ YYYY] + +--- + +## Current Role Demands + +_What does your job actually require you to be excellent at -- not your job description, but the real work that determines whether you succeed or fail in the next 12 months?_ + +**Primary responsibilities:** + +1. [Responsibility -- stated as an outcome, not an activity. "Close $2M in new business" not "Manage sales pipeline."] +2. [Responsibility] +3. [Responsibility] +4. [Responsibility] + +**Emerging demands:** [What your role is shifting toward that it did not require six months ago -- new technology, expanded scope, organizational change, market shift.] + +**Skills your manager or board would say you need:** [What feedback -- explicit or implicit -- have you received? Direct quotes preferred over paraphrases.] + +--- + +## Gap Analysis + +_Rate with evidence, not feeling. A "4" means others seek your guidance on this skill. A "2" means you can perform it with effort and occasional mistakes. A "1" means you avoid it or delegate it out of inability rather than efficiency._ + +| # | Skill | Current level (1-5) | Target level (1-5) | Gap | Evidence for current rating | Priority | +|---|-------|--------------------|--------------------|-----|---------------------------|----------| +| 1 | [e.g., Financial modeling] | [Rating] | [Rating] | [Delta] | [Specific: "Cannot build a three-statement model without template assistance"] | [Critical / High / Medium / Low] | +| 2 | [e.g., Public speaking] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 3 | [e.g., Strategic negotiation] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 4 | [e.g., Data analysis] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 5 | [e.g., Managing senior stakeholders] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 6 | [e.g., Technical architecture decisions] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 7 | [Skill] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | +| 8 | [Skill] | [Rating] | [Rating] | [Delta] | [Evidence] | [Priority] | + +**Largest gaps:** [List the top three by delta. These become your learning priorities unless strategic context overrides.] + +--- + +## Learning Priorities This Quarter + +_Three skills maximum. Attempting to close five gaps simultaneously closes none._ + +### Priority 1: [Skill name] + +**Current level:** [X/5] | **Target level by end of quarter:** [Y/5] + +**Why this skill, this quarter:** [Connect to role demands, feedback, or an upcoming challenge that will expose the gap.] + +**Learning methods:** + +| Method | Specific resource | Time per week | Start date | +|--------|------------------|---------------|-----------| +| Book / Reading | [Title and author] | [Hours] | [Date] | +| Course / Workshop | [Name, provider, URL] | [Hours] | [Date] | +| Mentor / Coach | [Name -- what you will ask them to help with specifically] | [Hours per month] | [Date] | +| Deliberate practice | [Specific practice activity -- e.g., "Build one financial model per week from scratch without templates"] | [Hours] | [Date] | +| Stretch project | [Real work assignment that forces application -- e.g., "Lead the Q2 board financial review"] | [Integrated into work] | [Date] | + +### Priority 2: [Skill name] + +**Current level:** [X/5] | **Target level by end of quarter:** [Y/5] + +**Why this skill, this quarter:** [Rationale] + +**Learning methods:** + +| Method | Specific resource | Time per week | Start date | +|--------|------------------|---------------|-----------| +| Book / Reading | [Resource] | [Hours] | [Date] | +| Course / Workshop | [Resource] | [Hours] | [Date] | +| Mentor / Coach | [Name and focus] | [Hours per month] | [Date] | +| Deliberate practice | [Activity] | [Hours] | [Date] | +| Stretch project | [Assignment] | [Integrated] | [Date] | + +### Priority 3: [Skill name] + +**Current level:** [X/5] | **Target level by end of quarter:** [Y/5] + +**Why this skill, this quarter:** [Rationale] + +**Learning methods:** + +| Method | Specific resource | Time per week | Start date | +|--------|------------------|---------------|-----------| +| Book / Reading | [Resource] | [Hours] | [Date] | +| Course / Workshop | [Resource] | [Hours] | [Date] | +| Mentor / Coach | [Name and focus] | [Hours per month] | [Date] | +| Deliberate practice | [Activity] | [Hours] | [Date] | +| Stretch project | [Assignment] | [Integrated] | [Date] | + +--- + +## Time Allocation + +_Learning that lacks a calendar slot is a wish, not a plan._ + +| Day | Time block | Duration | Activity | +|-----|-----------|----------|----------| +| [e.g., Monday] | [e.g., 7:00-8:00 AM] | [1 hour] | [e.g., Reading -- Priority 1 book] | +| [Day] | [Time] | [Duration] | [Activity] | +| [Day] | [Time] | [Duration] | [Activity] | +| [Day] | [Time] | [Duration] | [Activity] | + +**Total weekly commitment:** [X hours] + +**Non-negotiable minimum:** [The reduced version you will maintain during high-pressure weeks -- e.g., "2 hours minimum even in crunch weeks"] + +--- + +## Accountability + +| Role | Name | How they hold me accountable | Check-in cadence | +|------|------|-----------------------------|--------------------| +| Manager | [Name] | [e.g., Monthly 1:1 agenda item reviewing skill progress against this plan] | [Monthly] | +| Mentor | [Name] | [e.g., Biweekly call focused on Priority 1 skill with homework review] | [Biweekly] | +| Peer / Partner | [Name] | [e.g., Weekly co-working session for deliberate practice] | [Weekly] | + +**Shared this plan with:** [Names and dates -- a plan that exists only in your files exerts no social pressure.] + +--- + +## Milestones + +_Concrete markers of progress. Not "feel more confident" -- observable demonstrations of improved capability._ + +### 30 Days + +| Priority | Milestone | How I will demonstrate it | +|----------|-----------|--------------------------| +| 1 | [What "better" looks like at day 30] | [Observable action or output -- e.g., "Complete first financial model independently and have CFO review it"] | +| 2 | [Milestone] | [Demonstration] | +| 3 | [Milestone] | [Demonstration] | + +### 60 Days + +| Priority | Milestone | How I will demonstrate it | +|----------|-----------|--------------------------| +| 1 | [Day 60 capability marker] | [Observable action or output] | +| 2 | [Milestone] | [Demonstration] | +| 3 | [Milestone] | [Demonstration] | + +### 90 Days + +| Priority | Milestone | How I will demonstrate it | +|----------|-----------|--------------------------| +| 1 | [End-of-quarter target capability] | [Observable action or output -- e.g., "Present financial analysis to board with confidence and handle Q&A without support"] | +| 2 | [Milestone] | [Demonstration] | +| 3 | [Milestone] | [Demonstration] | + +--- + +## Resources Budget + +| Category | Item | Cost | Status | +|----------|------|------|--------| +| Books | [Titles] | [$X] | [Purchased / To buy] | +| Courses | [Names] | [$X] | [Enrolled / To enroll] | +| Coaching / Mentoring | [Paid sessions if applicable] | [$X] | [Arranged / To arrange] | +| Conferences / Events | [Names] | [$X] | [Registered / Considering] | +| Tools / Subscriptions | [Software, platforms] | [$X] | [Active / To subscribe] | +| **Total** | | **[$X]** | | + +**Funding source:** [Personal / Company L&D budget / Negotiated with manager -- if company-funded, confirm approval before committing.] diff --git a/plugins/foreman/content/output-templates/self/negotiation-prep-sheet.md b/plugins/foreman/content/output-templates/self/negotiation-prep-sheet.md new file mode 100644 index 0000000..7e5a5dc --- /dev/null +++ b/plugins/foreman/content/output-templates/self/negotiation-prep-sheet.md @@ -0,0 +1,165 @@ +--- +name: "negotiation-prep-sheet" +description: "Produces a pre-negotiation preparation worksheet covering interests, BATNA, ZOPA, opening strategy, concession plan, red lines, and walk-away triggers. Designed to be completed 24 hours before any significant negotiation -- contract, partnership, salary, vendor, or deal-structuring conversation. Grounded in principled negotiation (Fisher/Ury), competitive tactics (Lowry), and game-theoretic frameworks." +audience: "self" +applicable_skills: + - negotiation-mindset-and-self + - competitive-negotiation + - cooperative-negotiation + - win-win-negotiation + - negotiation-game-theory +format: "prep-worksheet" +author: "Fatih Guner" +--- + +# Negotiation Preparation Sheet + + + +**Negotiation:** [Brief description -- e.g., "Series A term sheet with Acme Ventures"] + +**Counterparty:** [Organization and individual(s)] + +**Date and venue:** [When and where] + +**Your role:** [Lead negotiator / Support / Decision-maker / Observer] + +**Negotiation type:** [ ] Distributive (fixed pie) | [ ] Integrative (expandable pie) | [ ] Mixed + +--- + +## 1. Interests (Not Positions) + +_Positions are what you say you want. Interests are WHY you want it. Negotiation stalls when both sides defend positions; it moves when interests are exchanged._ + +**Your interests (ranked by priority):** + +| Priority | Interest | Why this matters | Flexible? | +|----------|---------|-----------------|-----------| +| 1 (highest) | [Core interest] | [Underlying need or concern] | [ ] Yes [ ] No | +| 2 | [Interest] | [Underlying need] | [ ] Yes [ ] No | +| 3 | [Interest] | [Underlying need] | [ ] Yes [ ] No | +| 4 | [Interest] | [Underlying need] | [ ] Yes [ ] No | +| 5 (lowest) | [Interest] | [Underlying need] | [ ] Yes [ ] No | + +**Their likely interests (ranked by your best estimate):** + +| Priority | Interest | Why this likely matters to them | Your evidence | +|----------|---------|-------------------------------|---------------| +| 1 | [What they probably care about most] | [Their underlying driver] | [How you know or infer this] | +| 2 | [Interest] | [Driver] | [Evidence] | +| 3 | [Interest] | [Driver] | [Evidence] | +| 4 | [Interest] | [Driver] | [Evidence] | + +**Shared interests (potential common ground):** + +- [Interest that both sides value -- this is where creative deals are built] +- [Interest that both sides value] + +**Conflicting interests (zero-sum dimensions):** + +- [Interest where one side's gain is the other's loss] +- [Interest in direct conflict] + +## 2. BATNA + +_Best Alternative To a Negotiated Agreement. Your BATNA is your source of power. A weak BATNA makes you desperate; a strong BATNA makes you calm._ + +**Your BATNA:** +[What will you do if this negotiation fails entirely? Be specific and honest. If your BATNA is weak, that changes your strategy.] + +- Strength of your BATNA: [ ] Strong [ ] Moderate [ ] Weak +- Can you improve your BATNA before the negotiation? [ ] Yes -- [how] | [ ] No + +**Their BATNA (your best estimate):** +[What will they do if this negotiation fails? The better their alternatives, the less leverage you have.] + +- Estimated strength: [ ] Strong [ ] Moderate [ ] Weak +- Evidence: [How you know or infer this] + +## 3. ZOPA Estimate + +_Zone of Possible Agreement. The range where a deal works for both sides._ + +| Dimension | Your target | Your reservation point (walk-away) | Their likely target | Their likely reservation point | ZOPA exists? | +|-----------|------------|-----------------------------------|--------------------|-----------------------------|-------------| +| [e.g., Price] | [Best outcome] | [Minimum acceptable] | [Their ideal] | [Their probable floor/ceiling] | [ ] Yes [ ] No [ ] Unclear | +| [e.g., Timeline] | [Best outcome] | [Minimum acceptable] | [Their ideal] | [Their probable limit] | [ ] Yes [ ] No [ ] Unclear | +| [e.g., Terms] | [Best outcome] | [Minimum acceptable] | [Their ideal] | [Their probable limit] | [ ] Yes [ ] No [ ] Unclear | + +**If no ZOPA exists on key dimensions, should you proceed?** [Yes -- to discover new information / No -- invest energy elsewhere] + +## 4. Opening Strategy + +**Who makes the first offer?** +[ ] You -- [Reason: e.g., anchoring advantage, setting the frame] +[ ] Them -- [Reason: e.g., information asymmetry, let them reveal range] + +**Your opening position:** [Specific number, term, or proposal] + +**Anchoring rationale:** [Why this number is defensible, not arbitrary -- cite market data, precedent, or objective criteria] + +**Opening tone:** [ ] Collaborative ("we'd like to find something that works for both sides") | [ ] Assertive ("our position is X, based on Y") | [ ] Exploratory ("help us understand what matters most to you") + +**First question you will ask them:** +[The question designed to surface their interests early -- e.g., "What does a successful outcome look like from your side?"] + +## 5. Concession Plan + +_Never concede without a plan. Each concession should be smaller than the last, linked to a reciprocal move, and never on your highest-priority interest._ + +| Concession round | You give | You ask for in return | Condition | +|-----------------|---------|----------------------|-----------| +| 1 | [Low-cost concession for you, high-value for them] | [Reciprocal move] | [Only if they...] | +| 2 | [Medium concession] | [Reciprocal move] | [Only if they...] | +| 3 | [Larger concession -- only if deal is close] | [Must-have reciprocal] | [Only if they...] | + +**Items you will NOT concede under any circumstances:** + +1. [Non-negotiable item] -- [Why] +2. [Non-negotiable item] -- [Why] + +## 6. Red Lines and Walk-Away Triggers + +_Define these before you enter the room. Under pressure, people rationalize past their own limits._ + +**I will walk away if:** + +1. [Specific condition -- e.g., "Valuation drops below $X"] +2. [Specific condition -- e.g., "They insist on a non-compete clause exceeding 12 months"] +3. [Specific condition -- e.g., "The conversation becomes adversarial and they refuse to engage on interests"] + +**Walk-away phrase:** [Pre-scripted language -- e.g., "We appreciate the discussion, but we're not able to move forward on these terms. Let's revisit if circumstances change."] + +## 7. Relationship and Process + +**Long-term relationship importance:** [ ] High (ongoing partnership) | [ ] Medium (may work together again) | [ ] Low (one-time transaction) + +**How does relationship importance change your approach?** +[One to two sentences -- e.g., "High relationship value means I prioritize fairness of process over marginal gains on terms."] + +**Decision authority in the room:** +- Your side: [ ] Full authority [ ] Must consult before committing [ ] Limited mandate +- Their side: [ ] Full authority [ ] Likely must consult [ ] Unknown + +**If they need to consult, what materials will they need to take back?** +[e.g., summary term sheet, one-pager, revised proposal] + +--- + +**Pre-negotiation checklist:** + +- [ ] BATNA is current and accurately assessed +- [ ] Reservation points are written down and will not be revised mid-negotiation +- [ ] Opening position and rationale are rehearsed +- [ ] Concession plan is sequenced +- [ ] Walk-away triggers are defined and memorized +- [ ] Counterparty research is complete (their constraints, incentives, alternatives) +- [ ] Physical materials prepared (proposal, data, contract markup) diff --git a/plugins/foreman/content/output-templates/self/personal-board-tracker.md b/plugins/foreman/content/output-templates/self/personal-board-tracker.md new file mode 100644 index 0000000..7be89b8 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/personal-board-tracker.md @@ -0,0 +1,212 @@ +--- +name: "personal-board-tracker" +description: "Produces a relationship management tracker for your personal advisory board -- the mentors, sponsors, domain experts, and connectors who accelerate your growth. Captures relationship strength, contact cadence, open asks, and mutual value exchange for 5-8 advisors. Includes a network gap analysis and quarterly review prompt. Use to prevent the two most common advisory relationship failures: letting strong relationships atrophy through neglect and maintaining the wrong advisors out of loyalty rather than strategic fit." +audience: "self" +applicable_skills: + - mentoring-and-coaching + - meeting-the-right-people + - career-strategy-for-leaders + - trust-equation + - connecting-with-people +format: "tracker" +author: "Fatih Guner" +--- + +# Personal Board Tracker + + + +**Last updated:** [Date] + +**Next quarterly review:** [Date -- set this now] + +--- + +## Advisory Board Roster + +### Advisor 1 + +- **Name:** [Full name] +- **Role / Organization:** [Their current position] +- **Expertise domain:** [What they know that you do not -- e.g., "Enterprise sales," "Fundraising Series A-B," "Product-market fit in SaaS"] +- **Advisory role for you:** [ ] Mentor [ ] Sponsor [ ] Domain expert [ ] Connector [ ] Accountability partner +- **Relationship strength:** [ /5] -- [One sentence justifying the rating] +- **How we met:** [Origin of the relationship -- context matters for maintenance] +- **Last contact:** [Date] | **Medium:** [In-person / Video / Phone / Email / Text] +- **Key topics discussed (last 3 interactions):** + 1. [Topic -- date] + 2. [Topic -- date] + 3. [Topic -- date] +- **Open asks / favors (from you to them):** [What you have asked for that remains outstanding] +- **Open asks / favors (from them to you):** [What they have asked of you -- fulfilling these is how you maintain the relationship] +- **Value they provide:** [Specific: introductions, judgment, industry knowledge, emotional support, challenge your thinking] +- **Value you provide back:** [Specific: deal flow, a different perspective, execution updates, referrals, gratitude that is not hollow] +- **Next scheduled touchpoint:** [Date and format] +- **Ideal contact cadence:** [Weekly / Biweekly / Monthly / Quarterly] + +--- + +### Advisor 2 + +- **Name:** [Full name] +- **Role / Organization:** [Position] +- **Expertise domain:** [Domain] +- **Advisory role for you:** [ ] Mentor [ ] Sponsor [ ] Domain expert [ ] Connector [ ] Accountability partner +- **Relationship strength:** [ /5] +- **How we met:** [Origin] +- **Last contact:** [Date] | **Medium:** [Format] +- **Key topics discussed (last 3 interactions):** + 1. [Topic -- date] + 2. [Topic -- date] + 3. [Topic -- date] +- **Open asks / favors (from you to them):** [Outstanding] +- **Open asks / favors (from them to you):** [Outstanding] +- **Value they provide:** [Specific] +- **Value you provide back:** [Specific] +- **Next scheduled touchpoint:** [Date] +- **Ideal contact cadence:** [Frequency] + +--- + +### Advisor 3 + +- **Name:** [Full name] +- **Role / Organization:** [Position] +- **Expertise domain:** [Domain] +- **Advisory role for you:** [ ] Mentor [ ] Sponsor [ ] Domain expert [ ] Connector [ ] Accountability partner +- **Relationship strength:** [ /5] +- **How we met:** [Origin] +- **Last contact:** [Date] | **Medium:** [Format] +- **Key topics discussed (last 3 interactions):** + 1. [Topic -- date] + 2. [Topic -- date] + 3. [Topic -- date] +- **Open asks / favors (from you to them):** [Outstanding] +- **Open asks / favors (from them to you):** [Outstanding] +- **Value they provide:** [Specific] +- **Value you provide back:** [Specific] +- **Next scheduled touchpoint:** [Date] +- **Ideal contact cadence:** [Frequency] + +--- + +### Advisor 4 + +- **Name:** [Full name] +- **Role / Organization:** [Position] +- **Expertise domain:** [Domain] +- **Advisory role for you:** [ ] Mentor [ ] Sponsor [ ] Domain expert [ ] Connector [ ] Accountability partner +- **Relationship strength:** [ /5] +- **How we met:** [Origin] +- **Last contact:** [Date] | **Medium:** [Format] +- **Key topics discussed (last 3 interactions):** + 1. [Topic -- date] + 2. [Topic -- date] + 3. [Topic -- date] +- **Open asks / favors (from you to them):** [Outstanding] +- **Open asks / favors (from them to you):** [Outstanding] +- **Value they provide:** [Specific] +- **Value you provide back:** [Specific] +- **Next scheduled touchpoint:** [Date] +- **Ideal contact cadence:** [Frequency] + +--- + +### Advisor 5 + +- **Name:** [Full name] +- **Role / Organization:** [Position] +- **Expertise domain:** [Domain] +- **Advisory role for you:** [ ] Mentor [ ] Sponsor [ ] Domain expert [ ] Connector [ ] Accountability partner +- **Relationship strength:** [ /5] +- **How we met:** [Origin] +- **Last contact:** [Date] | **Medium:** [Format] +- **Key topics discussed (last 3 interactions):** + 1. [Topic -- date] + 2. [Topic -- date] + 3. [Topic -- date] +- **Open asks / favors (from you to them):** [Outstanding] +- **Open asks / favors (from them to you):** [Outstanding] +- **Value they provide:** [Specific] +- **Value you provide back:** [Specific] +- **Next scheduled touchpoint:** [Date] +- **Ideal contact cadence:** [Frequency] + + + +--- + +## Relationship Health Dashboard + +_A snapshot for quarterly review. Fill this by scanning the roster above._ + +| Advisor | Strength | Last contact | Overdue? | Trend | Action needed | +|---------|----------|-------------|----------|-------|--------------| +| [Name 1] | [ /5] | [Date] | [Yes / No] | [Strengthening / Stable / Weakening] | [Specific next step or "None"] | +| [Name 2] | [ /5] | [Date] | [Yes / No] | [Trend] | [Action] | +| [Name 3] | [ /5] | [Date] | [Yes / No] | [Trend] | [Action] | +| [Name 4] | [ /5] | [Date] | [Yes / No] | [Trend] | [Action] | +| [Name 5] | [ /5] | [Date] | [Yes / No] | [Trend] | [Action] | + +--- + +## Network Gap Analysis + +_The most dangerous advisory gap is the one you do not notice. Review this section against your current company stage and the problems consuming your attention._ + +**Expertise I currently have covered:** + +- [ ] Fundraising and investor relations +- [ ] Sales and go-to-market +- [ ] Product and technology +- [ ] Operations and scaling +- [ ] People and culture +- [ ] Finance and unit economics +- [ ] Legal and governance +- [ ] Industry-specific domain knowledge + +**Expertise I am missing:** + +| Gap | Why it matters now | Candidate to fill it | Status | +|-----|-------------------|---------------------|--------| +| [e.g., "Enterprise sales experience"] | [Current challenge requiring this expertise] | [Name if identified / "Searching"] | [Outreach planned / Intro requested / No lead yet] | +| [Gap] | [Relevance] | [Candidate] | [Status] | + +**Diversity check:** Does my advisory board include perspectives from outside my industry, geography, gender, age cohort, and functional background? Homogeneous boards produce homogeneous blind spots. + +[One sentence assessment.] + +--- + +## Quarterly Review Prompt + +_Complete every 90 days. The composition of your advisory board should evolve as your challenges evolve._ + +**Date of review:** [Date] + +**Which advisor provided the most value this quarter, and why?** + +[Name and one to two sentences.] + +**Which relationship has weakened, and is it worth rebuilding?** + +[Name and honest assessment. Not every advisory relationship is permanent. Letting one lapse gracefully is better than maintaining it performatively.] + +**Has my biggest current challenge changed since last quarter?** + +[ ] No -- advisory board is still aligned +[ ] Yes -- new challenge: [Describe] -- I need advisory coverage in: [Domain] + +**One relationship action for next quarter:** + +[Specific: "Ask [name] for an introduction to someone in [domain]" or "Schedule a quarterly dinner with [name] to deepen the relationship beyond transactional advice."] diff --git a/plugins/foreman/content/output-templates/self/stakeholder-map.md b/plugins/foreman/content/output-templates/self/stakeholder-map.md new file mode 100644 index 0000000..1be0360 --- /dev/null +++ b/plugins/foreman/content/output-templates/self/stakeholder-map.md @@ -0,0 +1,145 @@ +--- +name: "stakeholder-map" +description: "Produces a complete stakeholder ecosystem map covering investors, board, team, customers, partners, regulators, media, and community. For each stakeholder, captures what they want, influence level, support posture, engagement strategy, communication cadence, and relationship owner. Includes a 2x2 influence-support matrix for visual prioritization. Distinct from the personal-board-tracker (which manages your advisory relationships); this template maps every actor whose support, resistance, or indifference shapes your outcomes. Use before major strategic decisions, fundraising rounds, product launches, or organizational changes where stakeholder alignment determines success." +audience: "self" +applicable_skills: + - porters-five-forces + - systems-thinking + - managing-up + - strategic-thinking-and-alignment + - coalition-and-partnership-games +format: "map" +author: "Fatih Guner" +--- + +# Stakeholder Map + + + +**Company / Initiative:** [Name] + +**Date mapped:** [Date] + +**Next review:** [Date -- quarterly minimum] + +--- + +## Stakeholder Roster + +### Investors + +| Name / Group | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|-------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Name / Fund] | [Returns, strategic value, information rights, governance role] | [H / M / L] | [Champion / Supportive / Neutral / Skeptic / Critic] | [How you manage this relationship -- proactive updates, board seats, co-investment opportunities] | [Weekly / Monthly / Quarterly] | [Name] | +| [Name / Fund] | [What they want] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +### Board Members + +| Name | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Name] | [Governance oversight, fiduciary duty, strategic influence, reputation protection] | [H / M / L] | [Champion / Supportive / Neutral / Skeptic / Critic] | [Pre-meeting alignment, one-on-one briefings, committee roles] | [Frequency] | [Owner] | +| [Name] | [What they want] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +### Team (Key Internal Stakeholders) + +| Name / Group | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|-------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [e.g., Engineering leadership] | [Technical autonomy, clear priorities, career growth, recognition] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | +| [e.g., Sales team] | [Quota clarity, product reliability, comp structure, territory fairness] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | +| [e.g., Key individual -- CTO, VP Sales] | [What they want] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +### Customers + +| Name / Segment | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|---------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Top customer or segment] | [Reliability, value, responsiveness, roadmap alignment] | [H / M / L] | [Posture] | [Strategy -- QBRs, executive sponsor, early access programs] | [Frequency] | [Owner] | +| [Customer or segment] | [What they want] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +### Partners + +| Name / Organization | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|--------------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Partner] | [Revenue share, deal flow, co-marketing, technical integration, exclusivity] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | +| [Partner] | [What they want] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +### Regulators and Government + +| Name / Body | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Regulatory body] | [Compliance, transparency, public interest protection, data governance] | [H / M / L] | [Posture] | [Strategy -- proactive disclosure, industry group participation, legal counsel engagement] | [Frequency] | [Owner] | + +### Media and Analysts + +| Name / Outlet | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|-------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Journalist / Analyst / Publication] | [Stories, access, exclusives, data, expert commentary] | [H / M / L] | [Posture] | [Strategy -- press briefings, embargoed announcements, relationship building] | [Frequency] | [Owner] | + +### Community and Ecosystem + +| Name / Group | What they want | Influence | Support | Engagement strategy | Comm. frequency | Relationship owner | +|-------------|---------------|-----------|---------|--------------------|-----------------|--------------------| +| [Community -- e.g., open-source contributors, user groups, local community] | [Recognition, access, transparency, shared value creation] | [H / M / L] | [Posture] | [Strategy] | [Frequency] | [Owner] | + +--- + +## Influence-Support Matrix + +_Plot every stakeholder from the roster above into one of four quadrants. This matrix determines where your limited relationship energy goes._ + +``` + HIGH INFLUENCE + | + MANAGE CLOSELY | KEEP SATISFIED + (High influence, | (High influence, + Low/Negative | Positive support) + support) | + | + Names: | Names: + - [Stakeholder] | - [Stakeholder] + - [Stakeholder] | - [Stakeholder] + - [Stakeholder] | - [Stakeholder] + | + ----------------------+------------------------ + | + MONITOR | KEEP INFORMED + (Low influence, | (Low influence, + Low/Negative | Positive support) + support) | + | + Names: | Names: + - [Stakeholder] | - [Stakeholder] + - [Stakeholder] | - [Stakeholder] + - [Stakeholder] | - [Stakeholder] + | + LOW INFLUENCE + + <--- CRITIC / SKEPTIC CHAMPION / SUPPORTIVE ---> +``` + +--- + +## Priority Actions + +_Derived from the matrix. Focus on the upper-left quadrant first -- high-influence stakeholders who are not yet aligned._ + +| Stakeholder | Current posture | Target posture | Action to move them | Owner | By when | +|-------------|----------------|---------------|--------------------|---------|----| +| [Name -- from "Manage closely" quadrant] | [Skeptic / Critic] | [Neutral / Supportive] | [Specific engagement action -- meeting, concession, information campaign] | [Name] | [Date] | +| [Name] | [Current] | [Target] | [Action] | [Owner] | [Date] | +| [Name] | [Current] | [Target] | [Action] | [Owner] | [Date] | + +--- + +## Blind Spots Check + +_The stakeholders you forgot are often the ones who derail you._ + +- **Who influences my stakeholders that I have not mapped?** [e.g., an investor's LP, a board member's network, a regulator's advisory committee] +- **Who is currently silent but could become vocal?** [e.g., a minority shareholder, a departing executive, a dormant competitor] +- **Whose support am I taking for granted?** [Name the relationship you have not invested in because it "seems fine."] diff --git a/plugins/foreman/content/output-templates/self/weekly-ceo-review.md b/plugins/foreman/content/output-templates/self/weekly-ceo-review.md new file mode 100644 index 0000000..a7f916f --- /dev/null +++ b/plugins/foreman/content/output-templates/self/weekly-ceo-review.md @@ -0,0 +1,139 @@ +--- +name: "weekly-ceo-review" +description: "Produces a metric-driven weekly operational review for CEOs and founders. Tracks key performance indicators, wins, problems, decisions made and deferred, people issues, and cash position in a single scannable document. Distinct from the leadership-reflection template (which examines patterns and personal growth), this template is operational -- it creates a running log of what happened, what mattered, and what comes next. Use every Friday afternoon or Monday morning to maintain strategic clarity amid operational chaos." +audience: "self" +applicable_skills: + - balanced-scorecard + - smart-goals + - focus-and-priority-management + - eisenhower-matrix + - evaluating-and-deciding +format: "weekly-review" +author: "Fatih Guner" +--- + +# Weekly CEO Review + + + +**Week of:** [MM/DD/YYYY -- MM/DD/YYYY] + +**Completed by:** [Name] | **Date filled:** [Date] + +--- + +## Key Metrics This Week + +_Five to seven numbers that define whether the business moved forward. If you track more than seven, you are measuring activity, not outcomes._ + +| # | Metric | This week | Last week | Trend | Target | Notes | +|---|--------|-----------|-----------|-------|--------|-------| +| 1 | [e.g., Revenue / MRR / Bookings] | [Value] | [Value] | [up / down / flat] | [Target] | [Context if needed] | +| 2 | [e.g., New customers / Active users] | [Value] | [Value] | [up / down / flat] | [Target] | | +| 3 | [e.g., Churn / Retention rate] | [Value] | [Value] | [up / down / flat] | [Target] | | +| 4 | [e.g., Pipeline / Qualified leads] | [Value] | [Value] | [up / down / flat] | [Target] | | +| 5 | [e.g., Burn rate / Cash collected] | [Value] | [Value] | [up / down / flat] | [Target] | | +| 6 | [e.g., Team velocity / Shipping cadence] | [Value] | [Value] | [up / down / flat] | [Target] | | +| 7 | [Custom metric for your stage] | [Value] | [Value] | [up / down / flat] | [Target] | | + +--- + +## Top 3 Wins + +_Concrete accomplishments. Not "good meetings" -- outcomes, deliverables, closed loops._ + +1. **[Win]** -- Why it matters: [One sentence on strategic significance] +2. **[Win]** -- Why it matters: [One sentence] +3. **[Win]** -- Why it matters: [One sentence] + +--- + +## Top 3 Problems + +_Problems you are aware of but have not yet resolved. Severity determines urgency. An owner without a deadline is not an owner._ + +| # | Problem | Severity | Owner | Deadline | Status | +|---|---------|----------|-------|----------|--------| +| 1 | [Describe the problem precisely] | [Critical / High / Medium] | [Name] | [Date] | [New / In progress / Escalated / Stalled] | +| 2 | [Problem] | [Severity] | [Name] | [Date] | [Status] | +| 3 | [Problem] | [Severity] | [Name] | [Date] | [Status] | + +**Carryover from last week:** [Which of last week's problems remain? If the same problem appears three weeks running, it is not a problem -- it is a systemic failure.] + +--- + +## Decisions Made + +_Document the decision and the reasoning. Your future self will not remember why you chose this path._ + +| Decision | Rationale | Reversible? | Expected outcome by [date] | +|----------|-----------|-------------|---------------------------| +| [What you decided] | [The two to three factors that drove the choice] | [Yes / Partially / No] | [What should be true if this was right] | +| [Decision] | [Rationale] | [Reversible?] | [Expected outcome] | + +--- + +## Decisions Deferred + +_Deferral is a decision. Name it. Justify it. Set a deadline or it becomes avoidance._ + +| Decision pending | Why deferred | What would change the calculus | Decide by | +|-----------------|-------------|-------------------------------|-----------| +| [What you are not yet deciding] | [Missing information / timing / dependency] | [Specific trigger or information needed] | [Date] | +| [Decision pending] | [Why] | [Trigger] | [Date] | + +--- + +## People + +_The section most founders skip and most regret skipping. Who needs your attention -- not your delegation -- this week?_ + +- **Needs recognition:** [Name] -- [For what, specifically] +- **Needs a difficult conversation:** [Name] -- [About what. Do not defer more than one week.] +- **Flight risk or disengagement signals:** [Name] -- [What you observed] +- **Hiring urgency:** [Role, if any] -- [Status and timeline] +- **Open headcount status:** [X roles open / Y in pipeline / Z offers extended] + +--- + +## Cash and Runway + +_Founders who track cash weekly survive. Founders who check quarterly get surprised._ + +- **Cash on hand:** [$X] +- **Monthly burn (trailing 30 days):** [$X] +- **Runway at current burn:** [X months] +- **Runway change vs. last week:** [Extended / Unchanged / Shortened by X days] +- **Upcoming major cash events:** [e.g., payroll, vendor payment, expected collection, funding close] +- **Action needed:** [None / Accelerate collections / Reduce spend / Begin fundraising conversations] + +--- + +## Next Week's #1 Priority + +_One thing. Not three. If everything is a priority, nothing is._ + +**The single most important outcome for next week:** + +[State it in terms of a deliverable or decision, not an activity. "Launch beta to first 10 users" not "Work on beta."] + +**What must be true by Friday for this to succeed?** + +- [Condition 1] +- [Condition 2] + +**What could prevent it, and what is my mitigation?** + +[One to two sentences.] + +--- + +**Review #:** [Sequential number -- Week 1, Week 2, etc. This number alone tells you how long you have maintained the practice.] diff --git a/plugins/foreman/content/output-templates/team/action-plan.md b/plugins/foreman/content/output-templates/team/action-plan.md new file mode 100644 index 0000000..c1c6cd8 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/action-plan.md @@ -0,0 +1,90 @@ +--- +name: "action-plan" +description: "Produces a single-page leadership action plan that translates strategy into execution with military-grade clarity. Not a project plan -- a decision-to-action bridge. Use when a strategic direction has been set and the team needs a concise, unambiguous mandate for what happens next, who owns it, and by when." +audience: "team" +applicable_skills: + - smart-goals + - eisenhower-matrix + - focus-and-priority-management + - delegation-and-empowerment +format: "plan" +author: "Fatih Guner" +--- + +# Action Plan + + + +**Plan title:** [Short, specific name -- e.g., "Q3 EMEA Market Entry" or "Platform Migration Phase 1"] + +**Owner:** [Single accountable leader] | **Date issued:** [Date] | **Review date:** [Date] + +--- + +## Objective + +[One sentence. What will be true when this plan succeeds? No hedging, no qualifiers. Write it so that a stranger could verify completion.] + +## Success Criteria + +How the objective will be measured. Each criterion must be binary -- met or not met. + +| # | Criterion | Metric | Target | Deadline | +|---|-----------|--------|--------|----------| +| 1 | [What specifically must be achieved] | [Measurable unit] | [Threshold] | [Date] | +| 2 | [What specifically must be achieved] | [Measurable unit] | [Threshold] | [Date] | +| 3 | [What specifically must be achieved] | [Measurable unit] | [Threshold] | [Date] | + +## Key Actions + +Seven actions maximum. Sequence matters -- number them in execution order. Each action has exactly one owner. Shared ownership is no ownership. + +| # | Action | Owner | Start | Deadline | Status | +|---|--------|-------|-------|----------|--------| +| 1 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 2 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 3 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 4 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 5 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 6 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | +| 7 | [Verb-led, specific action] | [Name] | [Date] | [Date] | [ ] Not started | + + + +## Dependencies + +What must be true or available for this plan to succeed. Flag anything not yet confirmed. + +| Dependency | Required by | Status | Contingency if unavailable | +|------------|------------|--------|---------------------------| +| [Resource, approval, deliverable, or external event] | [Action #] | [ ] Confirmed [ ] Pending | [Fallback] | +| [Resource, approval, deliverable, or external event] | [Action #] | [ ] Confirmed [ ] Pending | [Fallback] | + +## Risks + +| Risk | Probability | Impact | Mitigation | Trigger for escalation | +|------|------------|--------|------------|----------------------| +| [What could go wrong] | [H / M / L] | [H / M / L] | [Preventive action] | [When to escalate and to whom] | +| [What could go wrong] | [H / M / L] | [H / M / L] | [Preventive action] | [When to escalate and to whom] | + +## First 48 Hours + +The immediate actions that signal this plan is real, not aspirational. Completing these within two days creates momentum and accountability. + +| # | Immediate action | Owner | Done by | +|---|-----------------|-------|---------| +| 1 | [What happens tomorrow morning] | [Name] | [Date + time] | +| 2 | [What happens within 24 hours] | [Name] | [Date + time] | +| 3 | [What happens within 48 hours] | [Name] | [Date + time] | + +--- + +**Distribution:** [Who receives this plan] + +**Cadence:** [How often progress is reviewed -- e.g., "Weekly standup every Monday 09:00" or "Async update in Slack every Friday"] + +**Escalation path:** [Name and channel if the plan goes off-track] diff --git a/plugins/foreman/content/output-templates/team/culture-values-document.md b/plugins/foreman/content/output-templates/team/culture-values-document.md new file mode 100644 index 0000000..fea9e6c --- /dev/null +++ b/plugins/foreman/content/output-templates/team/culture-values-document.md @@ -0,0 +1,112 @@ +--- +name: "culture-values-document" +description: "Produces a working company values document. For each value: a statement, three observable behaviors, three anti-patterns, measurable indicators, a concrete example, and the tension it creates -- because every real value demands a trade-off, and naming the cost separates conviction from decoration. Inspired by Netflix's culture deck, Bridgewater's principles, and Lencioni's values framework. Use when founding a company, resetting culture after rapid growth, or when stated values have drifted from lived behavior." +audience: "team" +applicable_skills: + - organisational-culture + - team-culture-and-dynamics + - purpose-driven-leadership + - stoic-right-action + - stoic-virtue-and-kindness +format: "working-document" +author: "Fatih Guner" +--- + +# Company Values + + + +**Company:** [Name] | **Version:** [1.0] | **Last revised:** [Date] | **Authors:** [Leadership team] + +This is not a poster. It is an operating manual for decisions under pressure. Each value forecloses alternatives. The anti-patterns matter as much as the behaviors: knowing what a value does not mean prevents the drift from principle to theater. + +--- + +## Value 1: [Name] + +**Statement:** [One sentence behavioral commitment -- observable, not abstract] + +**Looks like:** (1) [Specific daily behavior] (2) [Specific behavior] (3) [Specific behavior] + +**Does NOT mean:** (1) **[Distortion]** -- [How this value gets misapplied] (2) **[Distortion]** -- [Misapplication] (3) **[Distortion]** -- [Misapplication] + +**Measured by:** [Indicator] via [method], [frequency] | [Indicator] via [method], [frequency] + +**Example:** [3-4 sentence scenario where this value was tested and upheld -- specific enough to be instructive] + +**Tension:** [What this value costs. The trade-off it demands. If you cannot name the price, you have a platitude.] + +--- + +## Value 2: [Name] + +**Statement:** [Behavioral commitment] + +**Looks like:** (1) [Behavior] (2) [Behavior] (3) [Behavior] + +**Does NOT mean:** (1) **[Distortion]** -- [Misapplication] (2) **[Distortion]** -- [Misapplication] (3) **[Distortion]** -- [Misapplication] + +**Measured by:** [Indicator] via [method], [frequency] | [Indicator] via [method], [frequency] + +**Example:** [Scenario where tested and upheld] + +**Tension:** [Cost and trade-off] + +--- + +## Value 3: [Name] + +**Statement:** [Behavioral commitment] + +**Looks like:** (1) [Behavior] (2) [Behavior] (3) [Behavior] + +**Does NOT mean:** (1) **[Distortion]** -- [Misapplication] (2) **[Distortion]** -- [Misapplication] (3) **[Distortion]** -- [Misapplication] + +**Measured by:** [Indicator] via [method], [frequency] | [Indicator] via [method], [frequency] + +**Example:** [Scenario where tested and upheld] + +**Tension:** [Cost and trade-off] + +--- + +## Value 4: [Name] + +**Statement:** [Behavioral commitment] + +**Looks like:** (1) [Behavior] (2) [Behavior] (3) [Behavior] + +**Does NOT mean:** (1) **[Distortion]** -- [Misapplication] (2) **[Distortion]** -- [Misapplication] (3) **[Distortion]** -- [Misapplication] + +**Measured by:** [Indicator] via [method], [frequency] | [Indicator] via [method], [frequency] + +**Example:** [Scenario where tested and upheld] + +**Tension:** [Cost and trade-off] + + + +--- + +## The Values Test + +| Test | V1 | V2 | V3 | V4 | +|------|----|----|----|----| +| Would we fire a high performer who violated this? | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | +| Would we hire for this over superior technical skills? | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | +| Has this cost us money, speed, or convenience? | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | +| Would a reasonable company choose the opposite? | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | +| Can a week-one employee observe this without being told? | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | [ ] Y [ ] N | + +**Values that fail are aspirations. Aspirations belong in strategy documents, not here.** + +--- + +## Revision Protocol + +Review annually or when: company size doubles, a significant cultural failure occurs, leadership changes at founder/C-suite level, or a value is no longer practiced. + +**Next review:** [Date -- 12 months out] | **Owner:** [Name -- typically CEO or Head of People] diff --git a/plugins/foreman/content/output-templates/team/feedback-360-template.md b/plugins/foreman/content/output-templates/team/feedback-360-template.md new file mode 100644 index 0000000..b843fe9 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/feedback-360-template.md @@ -0,0 +1,118 @@ +--- +name: "feedback-360-template" +description: "Produces a 360-degree feedback collection form gathering structured assessments from four perspectives: self, manager, peers, and direct reports. Each perspective evaluates five dimensions -- results delivery, collaboration, communication, growth orientation, and values alignment -- scored 1-5 with mandatory written evidence. Distinct from the giving-feedback skill (which teaches SBI) and the hiring scorecard (which evaluates candidates): this collects multi-source feedback on a current team member. Includes a synthesis page for pattern identification. Use during performance cycles or as a standalone development tool." +audience: "team" +applicable_skills: + - giving-feedback + - radical-candor + - johari-window + - psychological-safety + - belbin-team-roles +format: "feedback-form" +author: "Fatih Guner" +--- + +# 360-Degree Feedback + + + +**Subject:** [Name] | **Role:** [Title] | **Period:** [Start -- End] + +**Facilitator:** [HR partner or skip-level manager] | **Type:** [ ] Self [ ] Manager [ ] Peer [ ] Direct Report + +**Assessor:** [Name -- anonymized in aggregated report for peer/DR forms] + +**Scoring:** **5** Exceptional | **4** Strong | **3** Competent | **2** Developing | **1** Insufficient + +--- + +## Dimension 1: Results Delivery + +_Meets commitments, manages priorities, drives outcomes over activity._ + +**Score:** [ 1 -- 2 -- 3 -- 4 -- 5 ] + +**Evidence (required):** [Specific outcomes delivered, commitments met or missed. Minimum 2 sentences.] +> [Evidence here] + +## Dimension 2: Collaboration + +_Works across teams, shares information proactively, resolves disagreements constructively._ + +**Score:** [ 1 -- 2 -- 3 -- 4 -- 5 ] + +**Evidence (required):** [How this person works with others -- seeking input, sharing credit, handling conflict.] +> [Evidence here] + +## Dimension 3: Communication + +_Communicates clearly, listens actively, adapts to audience, surfaces issues early._ + +**Score:** [ 1 -- 2 -- 3 -- 4 -- 5 ] + +**Evidence (required):** [Quality, clarity, and timeliness. Over- or under-communication patterns.] +> [Evidence here] + +## Dimension 4: Growth Orientation + +_Seeks feedback, learns from mistakes, develops new skills, invests in others' growth._ + +**Score:** [ 1 -- 2 -- 3 -- 4 -- 5 ] + +**Evidence (required):** [Response to feedback, handling of setbacks, pursuit of learning. Observed behavior, not assumed mindset.] +> [Evidence here] + +## Dimension 5: Values Alignment + +_Acts with integrity, upholds organizational values, demonstrates accountability under pressure._ + +**Score:** [ 1 -- 2 -- 3 -- 4 -- 5 ] + +**Evidence (required):** [Behavior when values were tested -- under pressure, in conflict, when unobserved.] +> [Evidence here] + +--- + +## Summary + +**Overall score (average):** [ ] / 5 + +**Top strength:** [Dimension and why] | **Development area:** [Dimension and why] + +**Keep doing:** [Behavior] | **Start doing:** [Behavior] | **Stop doing:** [Behavior] + +--- + +## Synthesis Page _(facilitator use only)_ + +**Assessors:** Self: 1 | Manager: 1 | Peers: [#] | Direct Reports: [#] + +| Dimension | Self | Manager | Peer avg. | DR avg. | Overall | +|-----------|:----:|:-------:|:---------:|:-------:|:-------:| +| Results delivery | [ ] | [ ] | [ ] | [ ] | [ ] | +| Collaboration | [ ] | [ ] | [ ] | [ ] | [ ] | +| Communication | [ ] | [ ] | [ ] | [ ] | [ ] | +| Growth orientation | [ ] | [ ] | [ ] | [ ] | [ ] | +| Values alignment | [ ] | [ ] | [ ] | [ ] | [ ] | + +**Convergence:** [Dimensions where all perspectives agree -- high-confidence signal] + +**Divergence:** [Dimensions where self-score differs from others by 1.5+ -- Johari blind spot] + +**Recurring themes:** 1. [Theme across multiple assessors] 2. [Theme] + +**Development priorities:** + +| Priority | Evidence basis | Suggested action | Review date | +|----------|---------------|-----------------|-------------| +| 1. [Area] | [Which assessors flagged this] | [Specific step] | [Date] | +| 2. [Area] | [Evidence basis] | [Step] | [Date] | + +--- + +**Review conversation:** [Date] | **Next 360 cycle:** [Date -- typically 6-12 months] diff --git a/plugins/foreman/content/output-templates/team/hiring-scorecard.md b/plugins/foreman/content/output-templates/team/hiring-scorecard.md new file mode 100644 index 0000000..bfc5d60 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/hiring-scorecard.md @@ -0,0 +1,106 @@ +--- +name: "hiring-scorecard" +description: "Produces a structured interview evaluation scorecard that replaces gut-feel hiring with evidence-based assessment. Maps role requirements to scored observations, evaluates culture alignment through behavioral evidence, includes a red flags checklist, and forces written justification for every recommendation. Features a multi-candidate comparison matrix. Built on Topgrading methodology and Google's structured interviewing research. Use for every interview loop." +audience: "team" +applicable_skills: + - belbin-team-roles + - hackman-enabling-conditions + - understanding-people + - reading-people + - decision-traps-and-roles +format: "scorecard" +author: "Fatih Guner" +--- + +# Hiring Scorecard + + + +**Role:** [Job title] | **Candidate:** [Name] | **Date:** [Date] + +**Interviewer:** [Name] | **Type:** [ ] Screen [ ] Technical [ ] Behavioral [ ] Final + +--- + +## Section 1: Role Requirements + +_3-5 must-haves from the job spec. Below 3 on any must-have is a no-hire. Calibrate before interviewing._ + +| # | Requirement | What "good" looks like | Weight | +|---|------------|----------------------|--------| +| R1 | [Must-have competency] | [Observable behaviors] | [H / M] | +| R2 | [Must-have competency] | [Observable behaviors] | [H / M] | +| R3 | [Must-have competency] | [Observable behaviors] | [H / M] | +| R4 | [Must-have competency] | [Observable behaviors] | [H / M] | +| R5 | [Delete if only 3-4 needed] | [Observable behaviors] | [H / M] | + +## Section 2: Assessment + +_**5** Exceptional | **4** Strong | **3** Adequate | **2** Below | **1** Insufficient_ + +| Req | Score | Evidence (specific examples, quotes, observations) | +|-----|-------|---------------------------------------------------| +| R1 | [ ] | [What the candidate said or demonstrated. Specific or generic? Recent or distant? Their role or team effort?] | +| R2 | [ ] | [Evidence] | +| R3 | [ ] | [Evidence] | +| R4 | [ ] | [Evidence] | +| R5 | [ ] | [Evidence] | + +**Weighted score:** [H = 2x, M = 1x] -- **Total:** [ ] / [Max] + +## Section 3: Culture Indicators + +| Value | Behavioral indicator | Score (1-5) | Evidence | +|-------|---------------------|-------------|----------| +| [E.g., "Ownership"] | [E.g., "Describes failures with personal accountability"] | [ ] | [Observed] | +| [E.g., "Intellectual honesty"] | [E.g., "Distinguishes knowledge from assumption"] | [ ] | [Observed] | +| [E.g., "Bias to action"] | [E.g., "Decides under uncertainty"] | [ ] | [Observed] | + +## Section 4: Red Flags + +| Red flag | Seen? | +|----------|-------| +| Cannot provide specific examples -- answers stay abstract | [ ] Y [ ] N | +| Takes sole credit for team achievements | [ ] Y [ ] N | +| Speaks negatively about prior employers without framing | [ ] Y [ ] N | +| Resume inconsistencies surface during interview | [ ] Y [ ] N | +| Cannot articulate why this role at this company | [ ] Y [ ] N | +| Asks no substantive questions about role, team, or product | [ ] Y [ ] N | +| Avoids accountability for past failures | [ ] Y [ ] N | + +**Count:** [ ] / 7 -- _Two or more warrant serious pause._ + +--- + +## Section 5: Recommendation + +**Decision:** [ ] Strong Yes [ ] Yes [ ] No [ ] Strong No + +**Justification (3+ sentences):** +> [Reference evidence from Sections 2-4. Address any tension between scores and flags.] + +**Strongest qualification:** [Single most compelling demonstration] + +**Biggest concern:** [Single most significant hiring risk] + +--- + +## Section 6: Comparison Matrix + +_Final-round calibration only. Complete after all interviewers submit independent scorecards._ + +| Dimension | Candidate A | Candidate B | Candidate C | +|-----------|-------------|-------------|-------------| +| R1 | [Avg] | [Avg] | [Avg] | +| R2 | [Avg] | [Avg] | [Avg] | +| R3 | [Avg] | [Avg] | [Avg] | +| R4 | [Avg] | [Avg] | [Avg] | +| Culture | [Avg] | [Avg] | [Avg] | +| Red flags | [#] | [#] | [#] | +| Consensus | [Recommendation] | [Recommendation] | [Recommendation] | + +**Decision:** [ ] Offer to: ___ [ ] Reject all -- reopen [ ] Revisit requirements + +**Rationale:** [Why this candidate? If rejecting all, what does this reveal about sourcing or spec?] diff --git a/plugins/foreman/content/output-templates/team/incident-postmortem.md b/plugins/foreman/content/output-templates/team/incident-postmortem.md new file mode 100644 index 0000000..ac9d22f --- /dev/null +++ b/plugins/foreman/content/output-templates/team/incident-postmortem.md @@ -0,0 +1,108 @@ +--- +name: "incident-postmortem" +description: "Produces a crisis-specific post-incident analysis that reconstructs what happened, determines why, and ensures the failure mode cannot recur. Distinct from a general retrospective: this template demands minute-by-minute timeline reconstruction, five-whys root cause analysis with contributing factor mapping, detection and response evaluation, customer impact quantification, and systemic fixes with named owners and deadlines. Modeled on SRE postmortem practices and aviation safety investigation methodology. Use after any incident that affected customers, revenue, or system integrity." +audience: "team" +applicable_skills: + - systems-thinking + - kaizen-bpr + - learning-from-failure + - defining-and-exploring-problems +format: "postmortem" +author: "Fatih Guner" +--- + +# Incident Postmortem + + + +**Incident title:** [Short, descriptive] | **Severity:** [ ] SEV-1 [ ] SEV-2 [ ] SEV-3 [ ] SEV-4 + +**Author:** [Name] | **Date:** [Date] | **Status:** [ ] Draft [ ] Final + +--- + +## Incident Summary + +| Field | Detail | +|-------|--------| +| **What happened** | [2-3 sentences. A board member should understand this.] | +| **Start / Detected / Resolved** | [HH:MM] / [HH:MM] / [HH:MM timezone] | +| **Duration (total / to detect)** | [Total elapsed] / [Time to awareness] | +| **Customer impact** | [Users affected, revenue impact, SLA breach Y/N] | + +## Timeline Reconstruction + +| Time (UTC) | Event | Actor / System | Source | +|------------|-------|---------------|--------| +| [HH:MM] | [Trigger event or first anomaly] | [Actor] | [Log / alert / Slack] | +| [HH:MM] | [Incident detected] | [Actor] | [Source] | +| [HH:MM] | [First response action] | [Actor] | [Source] | +| [HH:MM] | [Key decision or pivot] | [Actor] | [Source] | +| [HH:MM] | [Mitigation applied, service restored] | [Actor] | [Source] | + +## Root Cause Analysis (Five Whys) + +| Level | Question | Answer | +|-------|----------|--------| +| Why 1 | Why did [the incident] occur? | [Because...] | +| Why 2 | Why did [answer to Why 1] happen? | [Because...] | +| Why 3 | Why did [answer to Why 2] happen? | [Because...] | +| Why 4 | Why did [answer to Why 3] happen? | [Because...] | +| Why 5 | Why did [answer to Why 4] happen? | [Because...] | + +**Root cause:** [Single sentence -- the systemic failure, not the proximate trigger] + +### Contributing Factors + +- [ ] **Process gap:** [Missing or inadequate procedure] +- [ ] **Monitoring gap:** [What should have alerted us but did not] +- [ ] **Knowledge gap:** [Information not accessible to responders] +- [ ] **Communication gap:** [Escalation that failed or arrived late] +- [ ] **Testing gap:** [Scenario not covered in testing or staging] + +## Detection and Response Evaluation + +| Dimension | Assessment | Grade | +|-----------|-----------|-------| +| **How we found out** | [Automated alert / customer report / internal discovery] | [ ] Proactive [ ] Reactive | +| **Time to respond** | [Minutes from detection to first action] | [ ] Acceptable [ ] Too slow | +| **Escalation** | [Right people involved at the right time?] | [ ] Effective [ ] Gaps | +| **Communication** | [Stakeholders and customers informed appropriately?] | [ ] Effective [ ] Gaps | + +## Customer and Stakeholder Impact + +| Dimension | Detail | +|-----------|--------| +| **Users affected** | [Number or percentage] | +| **Revenue / SLA impact** | [Estimated $, commitments violated] | +| **Data impact** | [Loss, corruption, or exposure -- Y/N, detail if Y] | +| **Communication sent** | [What, when, which channel] | + +## Immediate Fixes Applied + +| # | Fix | Applied by | Permanent? | +|---|-----|-----------|-----------| +| 1 | [Action taken to restore service] | [Name] | [ ] Yes [ ] No | +| 2 | [Action taken] | [Name] | [ ] Yes [ ] No | + +## Systemic Fixes Required + +| # | Fix | Root cause addressed | Owner | Deadline | Status | +|---|-----|---------------------|-------|----------|--------| +| 1 | [Structural change to system, process, or monitoring] | [From analysis above] | [Name] | [Date] | [ ] Not started | +| 2 | [Fix] | [Cause] | [Name] | [Date] | [ ] Not started | +| 3 | [Fix] | [Cause] | [Name] | [Date] | [ ] Not started | + +## Lessons Learned + +1. **[Lesson title]:** [What we now understand that we did not understand before] +2. **[Lesson title]:** [Lesson] +3. **[Lesson title]:** [Lesson] + +--- + +**Follow-up review:** [Date, 2-4 weeks out] | **Owner:** [Who tracks fix completion] diff --git a/plugins/foreman/content/output-templates/team/meeting-notes-template.md b/plugins/foreman/content/output-templates/team/meeting-notes-template.md new file mode 100644 index 0000000..68fa810 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/meeting-notes-template.md @@ -0,0 +1,70 @@ +--- +name: "meeting-notes-template" +description: "Produces structured meeting notes designed for five-minute completion during or immediately after any meeting. Captures metadata, discussion summaries per agenda item, numbered decisions with rationale, action items with owners and deadlines, and a parking lot for deferred topics. Simplicity is the design principle: if the template takes longer to fill than the meeting took, it has failed. Use for any meeting where decisions are made or work is assigned." +audience: "team" +applicable_skills: + - focus-and-priority-management + - writing-for-navigation + - delegation-and-empowerment +format: "notes-template" +author: "Fatih Guner" +--- + +# Meeting Notes + + + +**Meeting:** [Purpose, not just "Weekly sync"] | **Date:** [YYYY-MM-DD] | **Time:** [Start -- End] + +**Facilitator:** [Name] | **Note-taker:** [Name] + +**Attendees:** [Names] | **Absent:** [Names] + +--- + +## Agenda + +| # | Topic | Presenter | Time | +|---|-------|-----------|------| +| 1 | [Topic] | [Name] | [X min] | +| 2 | [Topic] | [Name] | [X min] | +| 3 | [Topic] | [Name] | [X min] | + +## Discussion + +### 1. [Topic] + +- [Key point -- attribute to speaker if relevant] + +### 2. [Topic] + +- [Key point] + +### 3. [Topic] + +- [Key point] + +## Decisions + +| # | Decision | Rationale | Made by | +|---|----------|-----------|---------| +| D1 | [What was decided -- unambiguously] | [Why -- the reasoning, not just "agreed"] | [Name or "consensus"] | +| D2 | [Decision] | [Rationale] | [Made by] | + +## Action Items + +| # | Task | Owner | Deadline | Status | +|---|------|-------|----------|--------| +| A1 | [Verb-led, specific enough to verify completion] | [Name] | [Date] | [ ] Open | +| A2 | [Task] | [Name] | [Date] | [ ] Open | + +## Parking Lot + +| Item | Raised by | Deferred to | +|------|-----------|-------------| +| [Topic or question] | [Name] | [Next meeting / specific date / owner] | + +--- + +**Next meeting:** [Date] | [Time] | **Pre-work:** [What attendees should prepare, if any] diff --git a/plugins/foreman/content/output-templates/team/new-initiative-brief.md b/plugins/foreman/content/output-templates/team/new-initiative-brief.md new file mode 100644 index 0000000..bd1dfd4 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/new-initiative-brief.md @@ -0,0 +1,121 @@ +--- +name: "new-initiative-brief" +description: "Produces a one-page initiative brief for launching a new product, feature, market entry, or partnership. Structured around hypothesis-driven thinking: what the team believes, what evidence supports the belief, what experiment will test it, and what criteria would kill it. Inspired by Amazon's PR/FAQ format and lean startup methodology. Use before committing significant resources to any new initiative." +audience: "team" +applicable_skills: + - business-model-canvas + - doblin-ten-types + - generating-solutions + - defining-and-exploring-problems +format: "briefing" +author: "Fatih Guner" +--- + +# Initiative Brief + + + +**Initiative name:** [Working title -- rename later if needed] + +**Author:** [Name] | **Date:** [Date] | **Version:** [1.0] + +**Sponsor:** [Executive or leader who must approve resource allocation] + +--- + +### Hypothesis + +_One sentence. What we believe to be true that, if confirmed, justifies this initiative._ + +> [We believe that (target customer) will (adopt / pay for / switch to) (proposed solution) because (specific reason), resulting in (measurable business outcome).] + +### Evidence + +_What we know today that supports this hypothesis. Distinguish between hard data and informed assumptions. Be honest about the gaps._ + +**What we know (supported by data):** + +- [Evidence point 1 -- source: customer interviews / analytics / market research / competitor data] +- [Evidence point 2 -- source] +- [Evidence point 3 -- source] + +**What we assume (not yet validated):** + +- [Assumption 1 -- risk level if wrong: HIGH / MEDIUM / LOW] +- [Assumption 2 -- risk level if wrong: HIGH / MEDIUM / LOW] +- [Assumption 3 -- risk level if wrong: HIGH / MEDIUM / LOW] + +### Experiment + +_What we will build, launch, or test to validate the hypothesis. Describe the minimum viable version, not the full vision._ + +**What:** [Describe the experiment -- MVP, pilot, prototype, landing page, concierge test, etc.] + +**Who:** [Target segment for the experiment -- be specific about the cohort] + +**How:** [Distribution / delivery method -- how will the target segment encounter the experiment?] + +**Duration:** [Time-boxed length of the experiment] + +### Metrics + +_How we will know whether the hypothesis holds. Define success and failure before running the experiment, not after._ + +| Metric | Current baseline | Success threshold | Failure threshold | Measurement method | +|--------|-----------------|-------------------|-------------------|--------------------| +| [Primary metric -- the one that matters most] | [Current value or N/A] | [Number that validates] | [Number that invalidates] | [Tool / method] | +| [Secondary metric] | [Current value or N/A] | [Target] | [Floor] | [Tool / method] | +| [Guardrail metric -- what must NOT degrade] | [Current value] | [Must stay above X] | [Below X = stop] | [Tool / method] | + +### Resources + +_What this initiative requires. Be precise -- vague resource requests get vague approvals._ + +| Resource | Quantity | Duration | Source | Approved? | +|----------|----------|----------|--------|-----------| +| [People -- role, not name] | [FTE count or hours/week] | [Weeks] | [Team or hire] | [ ] Yes [ ] No | +| [Budget] | [$amount] | [Period] | [Budget line] | [ ] Yes [ ] No | +| [Technology / infrastructure] | [Specifics] | [Duration] | [Existing / new] | [ ] Yes [ ] No | +| [External -- vendor, partner, agency] | [Scope] | [Duration] | [Identified?] | [ ] Yes [ ] No | + +**Total investment:** [$amount or person-weeks] over [duration] + +### Timeline + +| Milestone | Target date | Gate decision | +|-----------|------------|--------------| +| Brief approved, team assembled | [Date] | Proceed / No-go | +| Experiment designed, instrumented | [Date] | -- | +| Experiment launched | [Date] | -- | +| First data checkpoint | [Date] | Continue / Pivot / Kill | +| Experiment concluded, results analyzed | [Date] | Scale / Iterate / Abandon | +| Go / No-go on full build | [Date] | Commit resources or sunset | + +### Kill Criteria + +_The conditions under which this initiative stops, regardless of sunk cost or emotional attachment. Defining these in advance protects the organization from escalation of commitment._ + +This initiative will be stopped if: + +1. [Primary metric falls below failure threshold by the first data checkpoint] +2. [Key assumption #X is invalidated -- describe what invalidation looks like] +3. [Resource requirement exceeds [X] without proportional signal improvement] +4. [Market or competitive conditions change such that (specific condition)] + +**Kill decision authority:** [Name of the person empowered to make the call] + +--- + +**Approval:** + +| Role | Name | Decision | Date | +|------|------|----------|------| +| Sponsor | [Name] | [ ] Approved [ ] Amended [ ] Rejected | [Date] | +| [Stakeholder] | [Name] | [ ] Endorsed [ ] Concerns noted | [Date] | diff --git a/plugins/foreman/content/output-templates/team/offsite-planning-guide.md b/plugins/foreman/content/output-templates/team/offsite-planning-guide.md new file mode 100644 index 0000000..9781930 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/offsite-planning-guide.md @@ -0,0 +1,117 @@ +--- +name: "offsite-planning-guide" +description: "Produces a team offsite or retreat planning template covering objectives, pre-work, time-blocked agendas, facilitation notes, materials, and follow-up commitments. Includes a strategic variant and a team-bonding variant -- do not blend them. Features a 'what we will not discuss' list, because the fastest way to derail an offsite is failing to define its edges. Inspired by Lenny Rachitsky's offsite frameworks and McKinsey facilitation methodology. Use when planning any gathering that pulls the team out of daily execution." +audience: "team" +applicable_skills: + - strategic-thinking-and-alignment + - team-culture-and-dynamics + - appreciative-inquiry + - storytelling-for-leaders + - smart-goals +format: "planning-guide" +author: "Fatih Guner" +--- + +# Offsite Planning Guide + + + +**Team:** [Name] | **Organizer:** [Name] | **Date(s):** [Range] | **Location:** [Venue] + +**Duration:** [ ] Half-day [ ] Full day | **Variant:** [ ] A -- Strategic [ ] B -- Team-bonding + +--- + +## Objectives + +_Three maximum. Write as outcomes, not activities. "Align on H2 priorities" is an activity. "Ranked list of 5 initiatives with named owners for the top 3" is an outcome._ + +1. [Outcome that will be true or decided by the end] +2. [Outcome] +3. [Outcome] + +## What We Will NOT Discuss + +- [Explicitly out of scope -- e.g., "Individual performance reviews"] +- [Out of scope -- e.g., "Compensation structure changes"] +- [Out of scope -- e.g., "Decisions requiring absent stakeholders"] + +**Parking lot:** [Whiteboard or shared doc for captured out-of-scope topics] + +## Pre-Work + +_Distribute at least 5 business days before. No preparation, no output._ + +| Assignment | Purpose | Format | Due | +|-----------|---------|--------|-----| +| [E.g., "1-page summary of your team's top 3 blockers"] | [Why this matters] | [Doc / slides] | [Date] | +| [E.g., "Review customer feedback; come with 3 observations"] | [Purpose] | [Format] | [Date] | +| [E.g., "One start, one stop, one continue"] | [Purpose] | [Format] | [Date] | + +--- + +## Variant A: Strategic Offsite + +### Half-Day (4 hours) + +| Time | Session | Output | Facilitation note | +|------|---------|--------|-------------------| +| 0:00-0:15 | **Opening and ground rules** | Objectives posted, norms set | Phones away. Post "will not discuss" list visibly. | +| 0:15-0:45 | **Context setting** | Shared fact base | No debate -- questions only. Data pack sent in pre-work. | +| 0:45-1:45 | **Working session 1:** [Topic] | [E.g., "Strategic options generated and clustered"] | Start with 5 min silent individual writing before group discussion. | +| 1:45-2:00 | **Break** | -- | Fifteen minutes. No working through it. | +| 2:00-3:00 | **Working session 2:** [Topic] | [E.g., "Options force-ranked against criteria"] | Use dot-voting if the group is stuck. | +| 3:00-3:30 | **Decision capture** | Decisions separated from open questions | Read aloud: "Does anyone disagree as stated?" Silence is consent. | +| 3:30-4:00 | **Commitments and close** | Owners and deadlines assigned | Use Follow-Up Template below. | + +### Full-Day (8 hours) + +| Time | Session | Output | Facilitation note | +|------|---------|--------|-------------------| +| 0:00-0:20 | **Opening** | Norms and objectives | -- | +| 0:20-1:00 | **Context setting** | Shared facts | Q&A only. | +| 1:00-2:15 | **Working session 1:** [Topic] | [Specific output] | Alternate individual, small-group, and plenary. | +| 2:15-2:30 | **Break** | -- | -- | +| 2:30-3:45 | **Working session 2:** [Topic] | [Specific output] | Assign a devil's advocate per option. | +| 3:45-4:30 | **Lunch** | Unstructured | Seat people next to those they work with least. | +| 4:30-5:45 | **Working session 3:** [Topic] | [Specific output] | Hard trade-offs happen here. Do not rush. | +| 5:45-6:30 | **Decision capture** | Locked decisions | Write and read aloud. | +| 6:30-7:15 | **Commitments and close** | Owners, deadlines, retro on offsite | What worked? What would we change? | + +--- + +## Variant B: Team-Bonding Offsite (Half-Day, 4 hours) + +| Time | Session | Output | Facilitation note | +|------|---------|--------|-------------------| +| 0:00-0:15 | **Opening** | Safety norms established | "Nothing shared here becomes ammunition later." Leader states this explicitly. | +| 0:15-1:00 | **Personal histories** | Empathy through backstory | Each person: where they grew up, siblings, one unusual childhood challenge. Leader goes first, sets the depth. | +| 1:00-1:45 | **Strengths and contributions** | Direct appreciation | Written first, read aloud: "The thing you do that makes this team better is ___." | +| 1:45-2:00 | **Break** | -- | -- | +| 2:00-2:45 | **Team narrative** | Shared story | Three chapters: where we started, hardest moment, what we are building. Use Appreciative Inquiry. | +| 2:45-3:30 | **Shared experience** | Memory created together | Walk, cook, build, play. The activity matters less than the shared memory. | +| 3:30-4:00 | **Commitments to each other** | Relational commitments | Not deliverables -- e.g., "I commit to giving feedback within 24 hours." | + +--- + +## Required Materials + +Printed objectives and exclusion list (posted on walls), large sticky notes (1 pad per person), thick markers (1 per person), visible timer, 2-3 whiteboards or flip charts, dot stickers for voting (10 per person), camera or designated note-taker for whiteboard capture. + +## Follow-Up Commitments + +_Complete during the final 30 minutes. Distribute to all participants within 24 hours._ + +| Decision or commitment | Owner | Deadline | First action (within 48 hours) | +|----------------------|-------|----------|-------------------------------| +| [What was decided] | [Name] | [Date] | [Signal that this is real] | +| [What was decided] | [Name] | [Date] | [First action] | +| [What was decided] | [Name] | [Date] | [First action] | + +**Open questions:** [Unresolved topics with owners and deadlines for resolution] + +**Follow-up check-in:** [Date -- 2-3 weeks after offsite] | **Offsite retro (capture now):** What worked? What would we change? What surprised us? diff --git a/plugins/foreman/content/output-templates/team/one-on-one-template.md b/plugins/foreman/content/output-templates/team/one-on-one-template.md new file mode 100644 index 0000000..1c75663 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/one-on-one-template.md @@ -0,0 +1,87 @@ +--- +name: "one-on-one-template" +description: "Produces a structured weekly 1:1 conversation framework for managers and direct reports. Three phases: the employee's agenda first, the manager's agenda (feedback, alignment, development), and mutual commitments with deadlines. Opens with a pulse check. Rooted in Kim Scott's Radical Candor philosophy and Ben Horowitz's management discipline. Use weekly with each direct report." +audience: "team" +applicable_skills: + - radical-candor + - giving-feedback + - grow-model + - psychological-safety-practice + - mentoring-and-coaching +format: "meeting-template" +author: "Fatih Guner" +--- + +# Weekly 1:1 + + + +**Manager:** [Name] | **Report:** [Name] | **Date:** [Date] | **Week #:** [#] + +--- + +## Pulse Check + +**Energy:** [ 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8 -- 9 -- 10 ] | **One word for the week:** [___] | **Trend:** [ Rising / Steady / Declining ] + + + +--- + +## Part 1: Their Agenda (15 min) + +_Employee speaks first. Resist solving -- most people need to be heard before helped._ + +**What is on your mind?** +- [Topic 1 -- the thing they most want to discuss] +- [Topic 2] + +**Blockers:** + +| Blocker | Duration | What would unblock it? | +|---------|----------|----------------------| +| [Obstacle] | [Days / weeks] | [Action or decision needed] | +| [Obstacle] | [Days / weeks] | [Action or decision needed] | + +**Win since last 1:1:** [Encourage specificity, not modesty] + +--- + +## Part 2: Your Agenda (10 min) + +**Feedback (SBI):** Situation: [When/where] | Behavior: [What you observed] | Impact: [Effect] | Direction: [ ] Reinforce [ ] Redirect + +**Alignment:** +- **Priority next week:** [What and why] +- **Deprioritize:** [Explicitly named] +- **Context needed:** [Decisions or information from above] + +**Development** _(one question per meeting, rotate quarterly):_ +- [ ] What skill do you most want to build in 90 days? +- [ ] What energizes you? What drains you? +- [ ] Where do you want to be in one year? +- [ ] What project would you like to take on? +- [ ] What should I do differently as your manager? + +**Dev notes:** [Substance of the answer -- feeds quarterly planning] + +--- + +## Part 3: Commitments (5 min) + +_Review last week first. An action without a deadline and owner is a suggestion._ + +| Commitment | Owner | Deadline | Status | +|-----------|-------|----------|--------| +| [Carried from last week] | [Name] | [Date] | [ ] Done [ ] In progress [ ] Missed | +| [Carried from last week] | [Name] | [Date] | [ ] Done [ ] In progress [ ] Missed | +| [New -- from this conversation] | [Name] | [Date] | [ ] Not started | +| [New -- from this conversation] | [Name] | [Date] | [ ] Not started | +| [New -- from this conversation] | [Name] | [Date] | [ ] Not started | + + + +--- + +**Next 1:1:** [Date/time] | **Flagged for quarterly review:** [ ] Yes -- topic: ___ diff --git a/plugins/foreman/content/output-templates/team/project-kickoff-document.md b/plugins/foreman/content/output-templates/team/project-kickoff-document.md new file mode 100644 index 0000000..7690a13 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/project-kickoff-document.md @@ -0,0 +1,108 @@ +--- +name: "project-kickoff-document" +description: "Produces an execution-focused project launch document that translates an approved initiative into operational reality. Not a hypothesis brief -- this assumes the 'why' is settled and addresses the 'how.' Defines scope boundaries, assigns accountability through a RACI matrix, establishes communication cadence and escalation paths, maps dependencies and risks, and specifies first-week actions that convert planning into momentum. Use when a project has been approved and the team needs a single reference document for execution." +audience: "team" +applicable_skills: + - smart-goals + - hackman-enabling-conditions + - delegation-and-empowerment + - focus-and-priority-management +format: "document" +author: "Fatih Guner" +--- + +# Project Kickoff Document + + + +**Project name:** [Descriptive name -- if it needs explanation, rename it] + +**Project owner:** [Single accountable person] | **Date:** [Date] | **Version:** [1.0] + +**Executive sponsor:** [Who removes organizational obstacles] + +--- + +## Objective + +> [One sentence. What state of the world will exist when this project succeeds? Write it so an outsider could verify completion.] + +## Scope + +**In scope:** 1. [Deliverable -- be specific about the boundary] 2. [Deliverable] 3. [Deliverable] + +**Explicitly out of scope:** 1. [Item someone might assume is included -- why excluded] 2. [Item -- reason] 3. [Item -- reason] + +## Team Roles (RACI) + +| Deliverable / Decision | [Name] | [Name] | [Name] | [Name] | +|------------------------|:-:|:-:|:-:|:-:| +| [Deliverable 1] | A | R | C | I | +| [Deliverable 2] | C | A | R | I | +| [Deliverable 3] | I | C | A | R | +| [Key decision 1] | A | C | C | I | + +**R** = Responsible | **A** = Accountable | **C** = Consulted | **I** = Informed + +## Timeline and Milestones + +| Phase | Milestone | Target date | Gate decision | Owner | +|-------|-----------|------------|---------------|-------| +| Setup | Team assembled, kickoff completed | [Date] | -- | [Name] | +| Phase 1 | [First meaningful deliverable] | [Date] | Continue / Adjust | [Name] | +| Phase 2 | [Second meaningful deliverable] | [Date] | Continue / Adjust | [Name] | +| Phase 3 | [Third deliverable or integration point] | [Date] | Continue / Adjust | [Name] | +| Close | Final delivery, handoff, review | [Date] | Accept / Rework | [Name] | + +## Success Criteria + +| # | Criterion | Metric | Target | How verified | +|---|-----------|--------|--------|-------------| +| 1 | [Outcome -- not output] | [Unit] | [Threshold] | [Method] | +| 2 | [Outcome] | [Unit] | [Threshold] | [Method] | + +## Communication Plan + +| Channel | Purpose | Cadence | Owner | +|---------|---------|---------|-------| +| [Stand-up] | Progress and blockers | [Daily / 2x week] | [Name] | +| [Status report] | Executive visibility | [Weekly] | [Name] | +| [Slack / Teams channel] | Async coordination | Continuous | -- | +| [Steering review] | Milestone gates, major decisions | [Bi-weekly / monthly] | [Name] | + +**Escalation path:** [Blocker > X hours] --> [Name] --> [Name if still unresolved] + +## Dependencies + +| # | Dependency | Required by | Provider | Status | Contingency | +|---|-----------|------------|----------|--------|-------------| +| 1 | [External deliverable, approval, or resource] | [Phase/date] | [Team] | [ ] Confirmed [ ] Pending | [Fallback] | +| 2 | [Dependency] | [Phase/date] | [Team] | [ ] Confirmed [ ] Pending | [Fallback] | + +## Risks and Mitigations + +| # | Risk | Likelihood | Impact | Mitigation | Owner | +|---|------|-----------|--------|------------|-------| +| 1 | [What could go wrong] | [H / M / L] | [H / M / L] | [Preventive or responsive action] | [Name] | +| 2 | [Risk] | [H / M / L] | [H / M / L] | [Mitigation] | [Name] | +| 3 | [Risk] | [H / M / L] | [H / M / L] | [Mitigation] | [Name] | + +## First-Week Actions + +| Day | Action | Owner | Done? | +|-----|--------|-------|-------| +| Day 1 | [Kickoff meeting held, roles confirmed, document ratified] | [Name] | [ ] | +| Day 1 | [Communication channels created, access provisioned] | [Name] | [ ] | +| Day 2 | [First dependency confirmed or escalated] | [Name] | [ ] | +| Day 3 | [First work artifact produced -- even if draft quality] | [Name] | [ ] | +| Day 5 | [First status update sent, blockers documented] | [Name] | [ ] | + +--- + +**Distribution:** [Who receives this document] | **Location:** [Permanent URL or shared drive path] + +**First review date:** [Date -- typically end of week 2] diff --git a/plugins/foreman/content/output-templates/team/retrospective-template.md b/plugins/foreman/content/output-templates/team/retrospective-template.md new file mode 100644 index 0000000..dd1c6ff --- /dev/null +++ b/plugins/foreman/content/output-templates/team/retrospective-template.md @@ -0,0 +1,125 @@ +--- +name: "retrospective-template" +description: "Produces a structured after-action review modeled on military and aviation post-incident analysis. Replaces the generic 'what went well / what didn't' format with a rigorous sequence: timeline reconstruction, surprise identification, root cause analysis via 5 Whys, pattern recognition, and binding commitments to change. Use after completing any project, sprint, product launch, incident, or significant initiative." +audience: "team" +applicable_skills: + - kaizen-bpr + - appreciative-inquiry + - learning-from-failure + - giving-feedback +format: "structured-review" +author: "Fatih Guner" +--- + +# After-Action Review + + + +**Project / Sprint / Event:** [Name] | **Date of review:** [Date] + +**Period under review:** [Start date] -- [End date] + +**Facilitator:** [Name] | **Participants:** [Names and roles] + +--- + +## Part 1: Timeline Reconstruction + +Build the factual record before interpreting it. What happened, in what order, and when did the team first know about it? No editorializing in this section -- just facts and dates. + +| Date | Event | Who was involved | What was decided or discovered | +|------|-------|-----------------|-------------------------------| +| [Date] | [Factual description of event] | [Names] | [Decision made or information surfaced] | +| [Date] | [Factual description of event] | [Names] | [Decision made or information surfaced] | +| [Date] | [Factual description of event] | [Names] | [Decision made or information surfaced] | +| [Date] | [Factual description of event] | [Names] | [Decision made or information surfaced] | +| [Date] | [Factual description of event] | [Names] | [Decision made or information surfaced] | + + + +## Part 2: Surprise Identification + +Surprises reveal gaps between the team's mental model and reality. That gap is where learning lives. + +**What did we expect to happen that did not?** + +1. [Expected outcome] -- [What actually happened instead] +2. [Expected outcome] -- [What actually happened instead] +3. [Expected outcome] -- [What actually happened instead] + +**What happened that we did not expect?** + +1. [Unexpected event or outcome] -- [Why we did not anticipate it] +2. [Unexpected event or outcome] -- [Why we did not anticipate it] +3. [Unexpected event or outcome] -- [Why we did not anticipate it] + +**What took longer, cost more, or proved harder than estimated?** + +1. [Item] -- estimated: [X] vs. actual: [Y] -- variance: [Z] +2. [Item] -- estimated: [X] vs. actual: [Y] -- variance: [Z] + +## Part 3: Root Cause Analysis + +Select the top 2-3 surprises from Part 2. Apply the 5 Whys to each. Stop when you reach a cause the team could have influenced. + +### Issue A: [Name the issue] + +| Level | Why? | Answer | +|-------|------|--------| +| Why 1 | Why did [the issue] occur? | [Because...] | +| Why 2 | Why did [answer to Why 1] happen? | [Because...] | +| Why 3 | Why did [answer to Why 2] happen? | [Because...] | +| Why 4 | Why did [answer to Why 3] happen? | [Because...] | +| Why 5 | Why did [answer to Why 4] happen? | [Because...] | + +**Root cause:** [Single sentence identifying the systemic cause] + +### Issue B: [Name the issue] + +| Level | Why? | Answer | +|-------|------|--------| +| Why 1 | Why did [the issue] occur? | [Because...] | +| Why 2 | Why did [answer to Why 1] happen? | [Because...] | +| Why 3 | Why did [answer to Why 2] happen? | [Because...] | +| Why 4 | Why did [answer to Why 3] happen? | [Because...] | +| Why 5 | Why did [answer to Why 4] happen? | [Because...] | + +**Root cause:** [Single sentence identifying the systemic cause] + + + +## Part 4: Pattern Recognition + +Step back from the specifics. Have these root causes appeared before? Are they symptoms of something structural? + +- **Recurring theme 1:** [Pattern observed across this and previous reviews -- e.g., "estimation consistently ignores integration testing time"] +- **Recurring theme 2:** [Pattern -- e.g., "dependencies on external teams surface late because we don't map them at kickoff"] +- **Recurring theme 3:** [Pattern -- e.g., "scope changes are accepted without adjusting timeline"] + +**What worked well that we should deliberately repeat?** + +- [Specific practice, decision, or behavior that produced a positive result] +- [Specific practice, decision, or behavior that produced a positive result] + +## Part 5: Commitments to Change + +Three maximum. Each must name an owner, a concrete action, and a verification method. Aspirations without owners are wishes. + +| # | Commitment | Root cause addressed | Owner | Action by date | How we verify it happened | +|---|-----------|---------------------|-------|----------------|--------------------------| +| 1 | [Specific, actionable change to process, practice, or structure] | [From Part 3] | [Name] | [Date] | [Observable evidence] | +| 2 | [Specific, actionable change to process, practice, or structure] | [From Part 3] | [Name] | [Date] | [Observable evidence] | +| 3 | [Specific, actionable change to process, practice, or structure] | [From Part 3] | [Name] | [Date] | [Observable evidence] | + +--- + +**Follow-up review date:** [4-6 weeks out -- to verify commitments were executed] + +**Archive location:** [Where this document will be stored for future retrospectives to reference] diff --git a/plugins/foreman/content/output-templates/team/role-description-template.md b/plugins/foreman/content/output-templates/team/role-description-template.md new file mode 100644 index 0000000..5e5d474 --- /dev/null +++ b/plugins/foreman/content/output-templates/team/role-description-template.md @@ -0,0 +1,89 @@ +--- +name: "role-description-template" +description: "Produces a comprehensive role definition document that goes beyond a standard job description. Defines purpose, key responsibilities, success metrics, required and preferred competencies, growth path, collaboration map, and an anti-description stating what the role is NOT. Distinct from a hiring scorecard, which evaluates candidates; this template defines the role itself. Built on Hackman's job design research and the Leadership Pipeline model. Use when creating a new role, redesigning an existing one, or aligning expectations with a current holder." +audience: "team" +applicable_skills: + - belbin-team-roles + - hackman-enabling-conditions + - leadership-pipeline + - smart-goals +format: "role-document" +author: "Fatih Guner" +--- + +# Role Description + + + +**Role title:** [Title -- legible outside your organization] + +**Team:** [Where this role sits] | **Reports to:** [Manager title] | **Direct reports:** [Number or "IC"] + +**Location:** [Office / Remote / Hybrid] | **Date:** [Date] | **Version:** [1.0] + +--- + +## Purpose + +> [One sentence. Why this role exists -- not what it does, but why the organization needs it.] + +## Key Responsibilities + +1. **[Verb-led responsibility]** -- [Scope and expected output] +2. **[Verb-led responsibility]** -- [Elaboration] +3. **[Verb-led responsibility]** -- [Elaboration] +4. **[Verb-led responsibility]** -- [Elaboration] +5. **[Verb-led responsibility]** -- [Elaboration] + +## Success Metrics + +| # | Metric | Target | How measured | Linked to | +|---|--------|--------|-------------|-----------| +| 1 | [Quantitative or observable outcome] | [Threshold] | [Method] | Resp. #X | +| 2 | [Metric] | [Target] | [Method] | Resp. #X | +| 3 | [Metric] | [Target] | [Method] | Resp. #X | + +## Required Competencies + +| Competency | What it looks like in practice | +|-----------|-------------------------------| +| [Technical or functional skill] | [Observable behavior or output] | +| [Technical or functional skill] | [Observable behavior] | +| [Leadership or interpersonal skill] | [Observable behavior] | + +## Nice-to-Have Competencies + +- [Competency] -- [Why it accelerates effectiveness] +- [Competency] -- [Why valuable] +- [Competency] -- [Why valuable] + +## Growth Path + +| Direction | Next role | Timeline | Demonstrated by | +|-----------|----------|---------|----------------| +| **Upward** | [Promotion target] | [X-Y years] | [Required competencies and results] | +| **Lateral** | [Adjacent role] | [X-Y years] | [Skills to develop] | +| **Specialist** | [Deep expertise track] | [X-Y years] | [Mastery indicators] | + +## Collaboration Map + +| Collaborator | Relationship | Cadence | Purpose | +|-------------|-------------|---------|---------| +| [Role / Team] | [Partner / Client / Supplier] | [Daily / Weekly] | [What they exchange] | +| [Role / Team] | [Type] | [Cadence] | [Purpose] | + +## Anti-Description + +**This role does not:** + +1. [Responsibility that might be assumed but belongs elsewhere -- state where] +2. [Activity adjacent but out of scope -- who owns it] +3. [Common misconception about authority or remit] + +**This role is not** a more senior version of [X] -- [clarify the distinction]. + +--- + +**Approved by:** [Name] | **Date:** [Date] | **Review:** [Annual / Upon scope change] diff --git a/plugins/foreman/content/output-templates/team/team-health-check.md b/plugins/foreman/content/output-templates/team/team-health-check.md new file mode 100644 index 0000000..7c086fa --- /dev/null +++ b/plugins/foreman/content/output-templates/team/team-health-check.md @@ -0,0 +1,123 @@ +--- +name: "team-health-check" +description: "Produces a structured team diagnostic assessment based on observed behavior, not self-reported surveys. Evaluates the team across Tuckman stage indicators, Belbin role coverage, Hackman enabling conditions, and psychological safety signals using traffic-light scoring. Use after observing a team for at least two weeks, during quarterly reviews, or when team performance degrades without obvious cause." +audience: "team" +applicable_skills: + - tuckman-team-stages + - belbin-team-roles + - hackman-enabling-conditions + - psychological-safety + - team-culture-and-dynamics +format: "checklist" +author: "Fatih Guner" +--- + +# Team Health Check + + + +**Team:** [Team name] | **Leader:** [Your name] | **Assessment period:** [Start date] -- [End date] | **Date completed:** [Date] + +--- + +## Section 1: Tuckman Stage Indicators + +Determine where the team currently operates. Most teams oscillate between stages; mark the dominant pattern. + +| # | Indicator | GREEN | AMBER | RED | +|---|-----------|-------|-------|-----| +| 1.1 | Members address conflict directly rather than through back-channels | [ ] | [ ] | [ ] | +| 1.2 | Roles and responsibilities are understood without repeated clarification | [ ] | [ ] | [ ] | +| 1.3 | Decisions are made and stick -- no relitigating settled questions | [ ] | [ ] | [ ] | +| 1.4 | New members are onboarded by the team, not just by the leader | [ ] | [ ] | [ ] | +| 1.5 | Disagreement produces better outcomes rather than deadlocks or silence | [ ] | [ ] | [ ] | +| 1.6 | The team self-organizes around urgent work without leader intervention | [ ] | [ ] | [ ] | + +**Assessed Tuckman stage:** [ Forming / Storming / Norming / Performing ] + +**Evidence for this assessment:** [Two to three specific observations] + +--- + +## Section 2: Belbin Role Coverage + +A high-performing team needs cognitive diversity, not just skill diversity. Mark each role as FILLED (green), PARTIAL (amber), or MISSING (red). + +| # | Belbin Role | Function | Coverage | Held by | +|---|-------------|----------|----------|---------| +| 2.1 | Plant | Generates original ideas | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.2 | Monitor Evaluator | Provides dispassionate analysis | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.3 | Coordinator | Clarifies goals, delegates effectively | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.4 | Resource Investigator | Explores opportunities, builds external links | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.5 | Implementer | Turns concepts into practical action | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.6 | Completer Finisher | Ensures thoroughness, polishes deliverables | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.7 | Teamworker | Builds cohesion, reduces friction | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.8 | Shaper | Drives urgency, challenges complacency | [ ] G [ ] A [ ] R | [Name or vacant] | +| 2.9 | Specialist | Provides deep domain expertise | [ ] G [ ] A [ ] R | [Name or vacant] | + +**Critical gaps:** [Roles marked RED that most constrain the team's current objectives] + +--- + +## Section 3: Hackman Enabling Conditions + +Richard Hackman identified five conditions that predict team effectiveness more reliably than individual talent. Rate each. + +| # | Condition | Diagnostic Question | GREEN | AMBER | RED | +|---|-----------|-------------------|-------|-------|-----| +| 3.1 | Real team | Are membership boundaries clear -- does everyone know who is on the team? | [ ] | [ ] | [ ] | +| 3.2 | Compelling direction | Can every member articulate the team's purpose in one sentence, unprompted? | [ ] | [ ] | [ ] | +| 3.3 | Right people | Does the team have the skills, experience, and working styles the task demands? | [ ] | [ ] | [ ] | +| 3.4 | Enabling structure | Are norms, roles, and workflows designed to support the work rather than inherited by default? | [ ] | [ ] | [ ] | +| 3.5 | Supportive context | Does the team have adequate resources, information, coaching, and organizational support? | [ ] | [ ] | [ ] | + +**Weakest condition:** [Identify the single condition most limiting performance] + +**Specific evidence:** [What you observed that led to this rating] + +--- + +## Section 4: Psychological Safety Signals + +Psychological safety is not about comfort -- it is about the team's willingness to take interpersonal risks. Rate based on observable behavior, not assumptions. + +| # | Signal | Observed? | GREEN | AMBER | RED | +|---|--------|-----------|-------|-------|-----| +| 4.1 | Team members ask questions that reveal incomplete knowledge | [ ] Yes [ ] No | [ ] | [ ] | [ ] | +| 4.2 | Mistakes are reported promptly rather than concealed | [ ] Yes [ ] No | [ ] | [ ] | [ ] | +| 4.3 | Junior members speak up before senior members in meetings | [ ] Yes [ ] No | [ ] | [ ] | [ ] | +| 4.4 | Feedback flows upward as well as downward | [ ] Yes [ ] No | [ ] | [ ] | [ ] | +| 4.5 | Dissent from the leader's stated position occurs at least occasionally | [ ] Yes [ ] No | [ ] | [ ] | [ ] | +| 4.6 | Failed experiments are discussed openly without blame assignment | [ ] Yes [ ] No | [ ] | [ ] | [ ] | + +**Overall psychological safety rating:** [ High / Moderate / Low ] + +--- + +## Summary Scorecard + +| Section | RED count | AMBER count | GREEN count | Overall | +|---------|-----------|-------------|-------------|---------| +| 1. Tuckman Stage | /6 | /6 | /6 | [ ] G [ ] A [ ] R | +| 2. Belbin Coverage | /9 | /9 | /9 | [ ] G [ ] A [ ] R | +| 3. Hackman Conditions | /5 | /5 | /5 | [ ] G [ ] A [ ] R | +| 4. Psychological Safety | /6 | /6 | /6 | [ ] G [ ] A [ ] R | + +--- + +## Top 3 Interventions + +Identify the three highest-leverage actions. Each must be specific, owned, and time-bound. Resist the temptation to fix everything at once -- three is the maximum a team can absorb without change fatigue. + +| Priority | Intervention | Addresses (Section.Item) | Owner | Deadline | Success looks like | +|----------|-------------|-------------------------|-------|----------|--------------------| +| 1 | [Specific action] | [e.g., 3.2] | [Name] | [Date] | [Observable change] | +| 2 | [Specific action] | [e.g., 4.3] | [Name] | [Date] | [Observable change] | +| 3 | [Specific action] | [e.g., 2.1] | [Name] | [Date] | [Observable change] | + +**Next assessment date:** [Schedule 4-6 weeks out to track whether interventions shifted the scores] diff --git a/plugins/foreman/content/playbooks/_schema/playbook-template.md b/plugins/foreman/content/playbooks/_schema/playbook-template.md new file mode 100644 index 0000000..c7dd696 --- /dev/null +++ b/plugins/foreman/content/playbooks/_schema/playbook-template.md @@ -0,0 +1,110 @@ +--- +name: "kebab-case-playbook-name" +description: "Third-person description of when to use this playbook and what entrepreneurial scenario it solves. Max 1024 characters." +trigger_diagnostics: + - diagnostic-name-1 + - diagnostic-name-2 +steps: + - skill: "skill-name-1" + purpose: "What this step accomplishes in one sentence" + output: "What this step produces — feeds into the next step" + - skill: "skill-name-2" + purpose: "What this step accomplishes" + output: "What this step produces" + - skill: "skill-name-3" + purpose: "What this step accomplishes" + output: "What this step produces" +final_outputs: + - template-name-1 + - template-name-2 +estimated_duration: "X-Y hours" +complexity: "basic | intermediate | advanced" +stage: + - validation + - early-traction +author: "Fatih Guner" +--- + + + +# {Playbook Title} + +## When to Use This Playbook + +{The scenario — what the entrepreneur is experiencing that makes this playbook the right choice. Be specific about the trigger conditions.} + +--- + +## Prerequisites + +{What must be true or ready before starting this playbook. Data needed, decisions already made, stakeholder alignment, etc.} + +--- + +## The Sequence + +### Step 1: {Skill Name} + +- **Purpose:** {Why this step comes first — what it establishes} +- **Key questions:** {The 2-3 questions this step must answer} +- **Input:** {What the entrepreneur brings to this step} +- **Output:** {What this step produces — becomes input for Step 2} +- **Time:** {Estimated duration} +- **Checkpoint:** {How to validate before proceeding — what would cause you to stop or revisit} + +### Step 2: {Skill Name} + +- **Purpose:** {Why this step follows Step 1} +- **Key questions:** {Questions to answer} +- **Input:** {Output from Step 1 + any additional data} +- **Output:** {What this step produces} +- **Time:** {Duration} +- **Checkpoint:** {Validation gate} + +--- + +## Decision Point + + + +{After Step N, evaluate: is this actually problem X or problem Y? If Y → exit this playbook and route to [alternative]. If X → continue to Step N+1.} + +--- + +### Step 3: {Skill Name} +{Continue the sequence...} + +--- + +## Final Deliverable + +| Audience | Template | Purpose | +|----------|----------|---------| +| {Investors} | `template-name` | {What this deliverable communicates} | +| {Team} | `template-name` | {What this deliverable communicates} | + +--- + +## Common Pitfalls + +{3-5 specific mistakes entrepreneurs make when running this playbook. Not generic advice — specific to THIS scenario.} + +--- + +## Adaptation Notes + +{How this playbook changes by company stage. A pre-seed founder runs it differently than a Series B company. Be specific about what changes.} diff --git a/plugins/foreman/content/playbooks/acquisition-evaluation-playbook.md b/plugins/foreman/content/playbooks/acquisition-evaluation-playbook.md new file mode 100644 index 0000000..cb72f71 --- /dev/null +++ b/plugins/foreman/content/playbooks/acquisition-evaluation-playbook.md @@ -0,0 +1,137 @@ +--- +name: "acquisition-evaluation-playbook" +description: "Used when a company receives an acquisition offer, considers acquiring another company, or needs to evaluate a merger proposal. Chains decision framing, competitive impact analysis, strategic assessment, post-deal dynamics modelling, negotiation preparation, and deal structuring into a comprehensive acquisition evaluation engagement. Use when the stakes are existential -- acquisitions are among the least reversible decisions a company makes." +trigger_diagnostics: + - partnership-diagnosis + - competitive-threat-diagnosis +steps: + - skill: "evaluating-and-deciding" + purpose: "Framework the decision: is this a one-way door, and what is the cost of being wrong in either direction?" + output: "Decision framework with reversibility assessment, opportunity cost analysis, and preliminary go/no-go criteria" + - skill: "porters-five-forces" + purpose: "Assess how the acquisition changes competitive dynamics -- for both sides" + output: "Pre- and post-acquisition five forces comparison showing how the deal reshapes market power, barriers, and competitive position" + - skill: "swot-pest-analysis" + purpose: "Honest strengths and weaknesses assessment of both entities and the combined future" + output: "Dual SWOT-PEST matrix (acquirer and target) with a combined entity projection highlighting synergies and conflicts" + - skill: "coalition-and-partnership-games" + purpose: "Model post-acquisition game theory: culture clash, power dynamics, retention incentives, and integration politics" + output: "Post-acquisition dynamics model with coalition analysis, key-person risk assessment, and integration game scenarios" + - skill: "negotiation-mindset-and-self" + purpose: "Prepare psychologically and strategically for the acquisition negotiation" + output: "Negotiation self-assessment with bias identification, emotional trigger mapping, and mental preparation framework" + - skill: "delivering-the-deal" + purpose: "Structure terms, anticipate obstacles, and design the closing sequence" + output: "Deal structure outline with term priorities, obstacle contingencies, closing timeline, and post-close satisfaction criteria" +final_outputs: + - decision-rationale-memo + - due-diligence-checklist + - exit-scenario-analysis + - negotiation-prep-sheet +estimated_duration: "10-20 hours across 2-6 weeks" +complexity: "advanced" +stage: + - growth + - scale +author: "Fatih Guner" +--- + +# The Acquisition Evaluation Playbook + +## When to Use This Playbook + +Most acquisitions destroy value. The research is unambiguous: between 70% and 90% of acquisitions fail to deliver their projected synergies, and a substantial fraction leave the acquirer worse off than before. The acquirer overpays. The target's talent departs. The cultures collide. The integration stalls. Yet acquisitions remain among the most consequential decisions a company can make -- and among the most time-pressured. Offers arrive with deadlines. Competitive bidders create urgency. The emotional weight of "this could change everything" clouds judgment precisely when clarity matters most. + +This playbook applies on both sides of the table: whether the company has received an acquisition offer it must evaluate or is considering acquiring another company. The analytical steps are symmetric; the orientation shifts. It does not cover the legal mechanics of deal execution (those require M&A counsel) but rather the strategic evaluation, human dynamics, and negotiation preparation that determine whether the deal should happen and on what terms. + +## Prerequisites + +- A clear understanding of the company's standalone trajectory (growth rate, runway, strategic options) +- Preliminary financial data on the other party (revenue, margins, growth, key metrics) +- Access to legal counsel with M&A experience (this playbook complements, not replaces, legal advice) +- A defined decision-making group: who ultimately says yes or no, and what is their process? +- Emotional honesty about the motivations driving the deal -- fatigue, ego, fear, greed, and genuine strategic logic all present differently but feel the same under pressure + +## The Sequence + +### Step 1: Evaluating and Deciding +- **Purpose:** Before analysing the specifics, establish the decision framework. Is this acquisition a one-way door -- irreversible once closed -- or can it be unwound? What is the cost of saying no? What is the cost of saying yes to the wrong terms? This step prevents the common failure of optimising deal terms on a deal that should not happen at all. +- **Key questions:** What is the company's trajectory without this deal? What specific strategic gap does the acquisition fill? Is this the only path to that objective, or are there alternatives? What would a sceptical board member ask? +- **Input:** Company strategic plan, current performance data, the acquisition proposal or target profile +- **Output:** Decision framework with go/no-go criteria, reversibility assessment, and alternative paths analysis +- **Time:** 1.5-2 hours +- **Checkpoint:** If the primary motivation is fear (competitor acquiring the target, market window closing, runway shrinking), acknowledge it explicitly. Fear-driven acquisitions have the highest failure rate. The framework must separate strategic logic from emotional pressure. + +## Decision Point + +After completing Step 1, the fundamental orientation: + +**Are you the buyer or the target?** + +- **If you are the buyer:** The remaining steps orient toward evaluating the target's strategic fit, assessing integration complexity, and preparing to negotiate from a position of optionality. Emphasis falls on Steps 2-3 (competitive and strategic assessment) and Step 4 (post-acquisition dynamics). The negotiation steps (5-6) focus on price discipline, earn-out structures, and retention mechanisms. +- **If you are the target:** The remaining steps orient toward evaluating the offer's fairness, understanding the acquirer's true motivations, and preparing to negotiate from a position of maximum leverage. Emphasis falls on Step 1 (the standalone alternative, which defines your BATNA), Step 4 (what your life looks like inside the acquirer), and Steps 5-6 (protecting founder interests, team welfare, and product vision in the terms). + +Both paths follow the same step sequence. The questions asked at each step, the evidence weighted, and the negotiation posture differ fundamentally. + +### Step 2: Porter's Five Forces +- **Purpose:** An acquisition reshapes the competitive landscape -- not just for the two parties but for every player in the market. This step maps the before-and-after: how the combined entity changes buyer power, supplier dynamics, competitive rivalry, threat of new entrants, and substitute availability. The analysis reveals whether the deal creates durable competitive advantage or merely creates a larger target. +- **Key questions:** Does the combination increase pricing power or simply add revenue? Does it raise barriers to entry for competitors? Does it create a substitute threat for adjacent markets? How will competitors respond -- and is that response factored into the synergy projections? +- **Input:** Decision framework from Step 1, market data, competitive intelligence on both entities +- **Output:** Comparative five forces analysis: current state versus post-acquisition state with competitive response scenarios +- **Time:** 1.5-2 hours +- **Checkpoint:** If the five forces analysis shows that the combined entity's competitive position is only marginally better than the standalone position, the strategic rationale for the deal is weak. Financial engineering alone (revenue addition without competitive improvement) is not a sufficient reason to accept the complexity of integration. + +### Step 3: SWOT-PEST Analysis +- **Purpose:** Due diligence on the numbers is necessary but insufficient. This step conducts strategic due diligence: an honest assessment of both entities' strengths, weaknesses, opportunities, and threats, plus the macro environment (political, economic, social, technological) that will shape the combined entity's future. +- **Key questions:** Which weaknesses of one entity are strengths of the other (genuine synergy)? Which weaknesses compound (compounding risk)? What macro trends support or undermine the combined thesis? Where do the cultures diverge on values, speed, or risk tolerance? +- **Input:** Five forces analysis from Step 2, financial data on both entities, culture and team assessments +- **Output:** Dual SWOT matrix with synergy mapping (where strengths complement) and conflict mapping (where weaknesses compound), plus PEST overlay +- **Time:** 1.5-2.5 hours +- **Checkpoint:** The combined SWOT must include at least three honest vulnerabilities of the deal itself -- not just the entities. Integration risk, culture clash, and customer confusion are real threats that deserve the same analytical rigour as market opportunities. + +### Step 4: Coalition and Partnership Games +- **Purpose:** The deal closes in weeks. The integration takes years. This step models the human dynamics of the post-acquisition reality: who holds power, who loses it, where coalitions form, where resistance emerges, and which key people leave (taking institutional knowledge with them). More acquisitions fail in integration than in negotiation. +- **Key questions:** Which leaders on both sides gain or lose power? Where will cultural norms clash (decision speed, risk tolerance, communication style)? What retention mechanisms keep critical talent? How do you prevent the "us versus them" dynamic from calcifying? +- **Input:** SWOT analysis from Step 3, organisational structures of both entities, key-person dependencies +- **Output:** Post-acquisition dynamics model with coalition map, key-person risk matrix, and integration scenario analysis +- **Time:** 1.5-2 hours +- **Checkpoint:** If the model shows that more than 30% of key personnel are flight risks post-close, the integration plan must address retention before the deal is signed, not after. Earnouts and retention bonuses are table stakes -- the deeper question is whether the acquiring culture gives those people a reason to stay beyond the vesting period. + +### Step 5: Negotiation Mindset and Self +- **Purpose:** Acquisition negotiations are emotionally charged in ways that fundraising and sales negotiations are not. The founder's identity, legacy, team, and financial future are all on the table simultaneously. This step prepares the psychological ground: identifying biases, mapping emotional triggers, and building the mental resilience to negotiate clearly when the stakes are personal. +- **Key questions:** Where are you most vulnerable to anchoring (the first number named)? What emotional triggers might cause you to accept terms you would reject in a calmer state? Do you have a trusted advisor who will challenge your rationalisation? Have you defined your walk-away point before emotions intensify? +- **Input:** Decision framework from Step 1, personal financial situation, advisor network +- **Output:** Negotiation self-assessment with identified biases, emotional trigger plan, and walk-away criteria defined in advance +- **Time:** 1-1.5 hours +- **Checkpoint:** The walk-away point must be written down and shared with at least one trusted advisor before the negotiation begins. A walk-away point that exists only in the founder's mind will shift under pressure. A written one, witnessed by an advisor, holds. + +### Step 6: Delivering the Deal +- **Purpose:** The final step structures the terms, anticipates obstacles, and designs the closing sequence. Good deals die in the last mile -- over working-capital adjustments, indemnification clauses, non-compete scope, or integration timeline disagreements. This step maps the terrain between handshake and signature. +- **Key questions:** What are the three to five most important terms beyond price? Where should you concede to preserve goodwill, and where must you hold firm? What are the likely last-minute obstacles (board approval, regulatory review, financing conditions)? What does success look like 12 months post-close? +- **Input:** All previous outputs, legal counsel input, term sheet or offer letter +- **Output:** Deal structure outline with term prioritisation, concession strategy, obstacle contingency plan, and post-close success criteria +- **Time:** 2-3 hours +- **Checkpoint:** The deal structure must satisfy the interests identified in Step 1, not just the positions adopted during negotiation. If the final terms achieve the price target but sacrifice the strategic objectives that justified the deal, the negotiation has succeeded tactically and failed strategically. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `decision-rationale-memo` | Board, investors | Evidence-based case for proceeding or declining, with strategic logic and risk assessment | +| `due-diligence-checklist` | Legal, finance, operations | Comprehensive diligence framework covering financial, strategic, cultural, and technical dimensions | +| `exit-scenario-analysis` | Founder, board | For targets: analysis of exit outcomes under different term structures with tax and financial planning implications | +| `negotiation-prep-sheet` | Founder, legal counsel | Negotiation strategy with BATNA, reservation points, aspiration targets, concession hierarchy, and walk-away criteria | + +## Common Pitfalls + +1. **Falling in love with the deal.** Once a founder emotionally commits to an acquisition -- as buyer or target -- objectivity evaporates. The decision framework in Step 1 exists to anchor analysis before emotions engage. Return to it whenever the conversation shifts from "should we?" to "how do we make this work?" +2. **Neglecting the integration model.** The synergy spreadsheet is fiction until the integration plan is reality. Step 4 forces confrontation with the human complexity that synergy projections ignore: culture clash, power dynamics, and talent flight. +3. **Anchoring on the headline number.** A $50M acquisition at 2x revenue with onerous earn-out terms, aggressive non-competes, and a hostile integration plan may be worth less than a $35M acquisition with clean terms and genuine autonomy. Price is one variable among many. +4. **Rushing due diligence under artificial time pressure.** Acquirers create urgency. Targets create competitive tension. Both are negotiation tactics, not immutable deadlines. The cost of an additional two weeks of diligence is trivial compared to the cost of discovering a material problem post-close. +5. **Ignoring the standalone alternative.** The most important number in any acquisition evaluation is the value of the company if the deal does not happen. If the standalone trajectory is strong, the walk-away position is strong. If the standalone trajectory is deteriorating, the negotiation leverage weakens -- and the founder must account for that honestly. + +## Adaptation Notes + +- **Growth stage:** Acquisitions at this stage are typically acqui-hires (buying talent), tuck-ins (buying product capabilities), or consolidation plays. The emphasis falls on Steps 3-4 (strategic fit and integration dynamics) because the acquirer is still building its own culture and processes. Adding a poorly fitting acquisition to an immature organisation compounds complexity rather than resolving it. +- **Scale stage:** Acquisitions become more sophisticated: market expansion, vertical integration, competitive elimination, or platform plays. All six steps carry full weight. The five forces analysis (Step 2) becomes critical because the competitive response to a large acquisition can be aggressive -- competitors may counter-acquire, form alliances, or accelerate product development. The deal's value depends not just on the two parties but on the entire market's reaction. +- At either stage, the founder must resist the gravitational pull of deal momentum. The best acquisition discipline is the willingness to walk away at any point in the process when the evidence no longer supports the thesis. Sunk costs in legal fees, management time, and emotional investment are real -- and irrelevant to the forward-looking decision. diff --git a/plugins/foreman/content/playbooks/board-formation-playbook.md b/plugins/foreman/content/playbooks/board-formation-playbook.md new file mode 100644 index 0000000..f87eaa8 --- /dev/null +++ b/plugins/foreman/content/playbooks/board-formation-playbook.md @@ -0,0 +1,125 @@ +--- +name: "board-formation-playbook" +description: "Used when a founder is forming a first board of directors, restructuring an existing board, or transitioning from informal advisors to formal governance. Chains strategic alignment, role design, game-theoretic dynamics analysis, trust building, and stakeholder management into a comprehensive board formation engagement. Use when the company reaches a stage where governance matters -- typically post-funding or pre-scale." +trigger_diagnostics: + - fundraising-diagnosis + - leadership-crisis-diagnosis +steps: + - skill: "strategic-thinking-and-alignment" + purpose: "Define what strategic guidance the board must provide -- not generically, but specific to the company's current challenges and next phase" + output: "Strategic guidance map: the three to five domains where board-level expertise is non-negotiable for the next 18 months" + - skill: "belbin-team-roles" + purpose: "Design board composition for complementary expertise and cognitive diversity -- not a collection of friends or familiar faces" + output: "Board composition blueprint mapping required Belbin roles to specific seat profiles with gap analysis against current candidates" + - skill: "coalition-and-partnership-games" + purpose: "Understand the game theory of board dynamics: voting blocs, alignment incentives, and power structures before they form" + output: "Board dynamics model showing likely coalitions, potential conflicts, and structural safeguards to maintain productive governance" + - skill: "trust-equation" + purpose: "Build the relational foundation with each board member -- trust is the currency that makes governance functional" + output: "Trust-building plan for each board relationship: credibility signals, reliability commitments, intimacy-building cadence, and self-orientation checks" + - skill: "managing-up" + purpose: "Prepare for managing the board as a stakeholder group -- setting expectations, controlling information flow, and maintaining founder authority" + output: "Board management playbook: meeting cadence, reporting structure, expectation-setting framework, and escalation protocols" +final_outputs: + - board-meeting-agenda + - stakeholder-map + - ceo-succession-brief +estimated_duration: "3-5 hours" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +author: "Fatih Guner" +--- + +# The Board Formation Playbook + +## When to Use This Playbook + +A board of directors, composed well, is the single most underutilised strategic asset in a startup. Composed poorly, it is the single most common source of founder misery. The difference lies not in finding "impressive" people but in engineering a group whose collective expertise, incentive alignment, and interpersonal dynamics produce better decisions than the founder can make alone. + +This playbook applies at three moments: when forming a first board (typically post-seed or Series A), when restructuring a board that has become dysfunctional or misaligned with the company's current stage, or when transitioning from an informal advisory group to formal governance. It does not cover board mechanics (bylaws, committee structures, D&O insurance) -- those are legal tasks. It covers the strategic and human architecture that determines whether the board creates value or destroys it. + +## Prerequisites + +- A clear understanding of the company's strategic priorities for the next 12-18 months +- Knowledge of existing governance commitments (investor board seats, observer rights) +- An honest assessment of the founder's own weaknesses and blind spots +- Willingness to prioritise capability over familiarity when selecting board members +- A cap table and any shareholder agreements that constrain board composition + +## The Sequence + +### Step 1: Strategic Thinking and Alignment +- **Purpose:** Board composition follows strategy, not the reverse. Before selecting people, the founder must articulate what strategic guidance the board must provide. A company entering enterprise sales needs different board expertise than one preparing for international expansion or navigating a regulatory shift. +- **Key questions:** What are the three existential challenges the company faces in the next 18 months? Which of these challenges exceed the founding team's expertise? Where has the company been wrong before, and what perspective would have caught the error? +- **Input:** Strategic plan, current team capabilities, investor expectations, market position +- **Output:** Strategic guidance map defining the domains where board-level expertise is essential +- **Time:** 1-1.5 hours +- **Checkpoint:** The guidance map must be specific. "We need someone with industry experience" is not specific. "We need someone who has navigated FDA approval for a digital health product" is specific. Vague requirements produce vague boards. + +### Step 2: Belbin Team Roles +- **Purpose:** Boards fail when every member is the same type of thinker -- usually the "strategist" archetype who offers grand visions but no operational rigour. Belbin roles applied to board composition ensure cognitive diversity: the challenger who stress-tests assumptions, the implementer who asks "how," the specialist who brings domain depth, and the coordinator who keeps discussions productive. +- **Key questions:** What thinking styles does the current leadership team overindex on? Which Belbin roles are absent? Does the proposed board include someone who will say "no" when the rest say "yes"? +- **Input:** Strategic guidance map from Step 1, founder's self-assessment, existing board members (if any) +- **Output:** Board composition blueprint: seat-by-seat role requirements with candidate profiles +- **Time:** 0.5-1 hour +- **Checkpoint:** If every proposed board member shares the founder's background, industry, or thinking style, the board will confirm biases rather than challenge them. At least one seat should make the founder slightly uncomfortable. + +## Decision Point + +After completing Step 2, a structural fork: + +**Advisory board or governance board?** + +- If the company is pre-institutional funding, has no external shareholders requiring formal governance, and the primary need is expertise access -- an advisory board may be more appropriate. Advisory boards have lower formality, no fiduciary duties, and more flexible composition. Skip to Step 4 (trust equation) and adapt Steps 4-5 for advisory relationships. +- If the company has institutional investors, is approaching a funding round that will require a board, or has reached a scale where fiduciary governance is a legal or practical necessity -- proceed with the full governance board formation. Steps 3-5 address the power dynamics, trust infrastructure, and management protocols that governance demands. + +The stakes differ by an order of magnitude. An advisory board member who disengages is a missed opportunity. A governance board member who disengages or misaligns is an existential risk. + +### Step 3: Coalition and Partnership Games +- **Purpose:** A board is a small-numbers game with real power. Voting blocs form. Information asymmetries develop between management and directors. Investor-appointed members may have incentives that diverge from common shareholders. This step models these dynamics before they materialise, designing structural safeguards while the founder still has leverage. +- **Key questions:** How will voting power distribute? Could investor-appointed directors form a controlling bloc? What happens when management's preferred strategy conflicts with a board member's portfolio incentives? Where should the founder retain veto power? +- **Input:** Board composition blueprint, cap table, shareholder agreements, investor term sheets +- **Output:** Board dynamics model with coalition analysis, conflict scenarios, and governance safeguards +- **Time:** 0.5-1 hour +- **Checkpoint:** If the model reveals that investor-appointed seats can outvote the founder and independent directors combined, the governance structure needs rebalancing before anyone is seated. Fixing power imbalances after formation is exponentially harder. + +### Step 4: Trust Equation +- **Purpose:** Governance runs on trust. A board member who does not trust the founder's competence will micromanage. A founder who does not trust a board member's motives will withhold information. This step designs the trust-building infrastructure for each board relationship using the credibility, reliability, intimacy, and self-orientation framework. +- **Key questions:** How will you demonstrate credibility to each board member before the first meeting? What reliability commitments will you make and keep? How will you build the interpersonal foundation that allows honest conversation? Where might self-orientation (yours or theirs) undermine trust? +- **Input:** Board composition from Steps 2-3, individual board member profiles, founder's communication style +- **Output:** Trust-building plan for each board relationship with specific actions and milestones +- **Time:** 0.5-1 hour +- **Checkpoint:** Trust plans that consist entirely of "send monthly updates" are insufficient. Each relationship requires a tailored approach -- the former operator needs different credibility signals than the institutional investor or the domain expert. + +### Step 5: Managing Up +- **Purpose:** The founder manages the board, not the reverse. Founders who approach board meetings as performance reviews are ceding authority. Those who approach them as strategic working sessions retain it. This step designs the management framework: meeting cadence, information flow, expectation-setting protocols, and the critical skill of delivering bad news well. +- **Key questions:** What information should the board receive between meetings? How do you structure a board meeting for decision-making rather than status updates? How do you manage a board member who oversteps into operational territory? When and how do you deliver bad news? +- **Input:** Trust plans from Step 4, board dynamics model from Step 3, company reporting capabilities +- **Output:** Board management playbook with meeting design, reporting templates, and difficult-conversation protocols +- **Time:** 0.5-1 hour +- **Checkpoint:** Run a mock board meeting with the management team before the first real one. The preparation will surface gaps in reporting, narrative, and facilitation that are far cheaper to fix in rehearsal than in front of directors. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `board-meeting-agenda` | Board members | First meeting agenda designed for productive governance and relationship-building | +| `stakeholder-map` | Founder, co-founders | Visual map of board dynamics: influence, expertise domains, potential coalitions, and communication preferences | +| `ceo-succession-brief` | Board, founder | Preliminary succession framework -- responsible boards address this from formation, not in crisis | + +## Common Pitfalls + +1. **Filling seats with friends.** The board that feels comfortable from day one will be useless by year two. Comfort at formation usually means insufficient cognitive diversity and a board that validates rather than challenges. +2. **Ignoring power dynamics until they bite.** Coalition analysis (Step 3) feels theoretical until an investor-appointed director blocks a strategic decision that serves the company but not the fund's timeline. Model the dynamics before they materialise. +3. **Treating board meetings as presentations.** Founders who spend 80% of board time presenting slides and 20% on discussion have the ratio inverted. The board's value is in their questions and judgment, not their patience as an audience. +4. **Failing to manage information asymmetry.** Board members who receive only curated good news lose the ability to provide useful guidance. Those who receive raw data without context make poor decisions. The information design in Step 5 balances both failure modes. +5. **Postponing the succession conversation.** Boards that never discuss CEO succession are unprepared for the scenario they most need to handle well. Raising the topic at formation -- while it is abstract -- normalises it for when it becomes concrete. + +## Adaptation Notes + +- **Early-traction stage:** The board is typically small (3-5 members), founder-controlled, and shaped by the lead investor's term sheet. The emphasis falls on Steps 1-2 (composition) and Step 4 (trust). Coalition dynamics are simpler but not absent -- even a three-person board has politics. +- **Growth stage:** Board composition becomes more consequential as the company faces harder decisions: market expansion, significant hires, potential M&A. Steps 2-3 (role design and dynamics) carry the most weight. Adding an independent director with operational experience often transforms board quality at this stage. +- **Scale stage:** Governance formalises. Committees emerge (audit, compensation, nomination). The managing-up step (Step 5) becomes a professional discipline rather than an informal practice. The founder's relationship with the board chair -- if different from the founder -- becomes the single most important governance dynamic. diff --git a/plugins/foreman/content/playbooks/competitive-response-playbook.md b/plugins/foreman/content/playbooks/competitive-response-playbook.md new file mode 100644 index 0000000..520e8e3 --- /dev/null +++ b/plugins/foreman/content/playbooks/competitive-response-playbook.md @@ -0,0 +1,132 @@ +--- +name: "competitive-response-playbook" +description: "Provides a structured response framework when a major competitor enters your market, undercuts your pricing, or launches a similar product. Moves founders from panic to strategic clarity through objective threat assessment, positional analysis, and team communication. Use when facing direct competitive threats, market share erosion, or price wars." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +trigger_diagnostics: + - competitive-threat-diagnosis +steps: + - skill: "porters-five-forces" + purpose: "Assess the real competitive threat objectively rather than through the lens of founder anxiety" + output: "Competitive threat assessment quantifying actual market impact across all five forces" + - skill: "art-of-war" + purpose: "Determine strategic position -- whether to fight directly, retreat, flank, or form alliances" + output: "Strategic position recommendation with rationale and risk assessment" + - skill: "blue-ocean-strategy" + purpose: "Identify escape routes to uncontested market space where the competitor's advantages become irrelevant" + output: "Blue ocean opportunity map with value curve comparison and differentiation options" + - skill: "first-mover-strategy" + purpose: "Decide timing -- respond immediately or wait for the competitive situation to clarify" + output: "Timing recommendation with scenario analysis for early and delayed response" + - skill: "storytelling-for-leaders" + purpose: "Communicate the competitive response to the team without creating panic or false confidence" + output: "Internal communication plan with key messages, framing, and delivery sequence" +final_outputs: + - competitive-landscape-brief + - action-plan + - strategic-analysis-one-pager +estimated_duration: "3-6 hours" +author: "Fatih Guner" +--- + +# Competitive Response Playbook + +The phone buzzes at 7 AM: a competitor just announced the product your team has been building for eighteen months. Or worse -- a well-funded incumbent decided your niche is interesting enough to enter. The natural response is panic, followed by a frantic all-hands meeting where someone suggests slashing prices and someone else proposes pivoting entirely. Neither impulse serves you. Competitive threats demand cold analysis before hot action, and the founders who survive these moments are the ones who resist the urge to react before they understand. + +--- + +## When to Use This Playbook + +- A direct competitor has entered your market or launched a similar product +- An incumbent with superior resources is targeting your customer segment +- A competitor is undercutting your pricing significantly +- Market share is eroding and the cause appears to be competitive pressure +- A potential acquirer has become a competitor instead +- Your team is anxious and looking to leadership for a clear response + +## Prerequisites + +- The competitive threat is real and specific, not hypothetical +- Basic understanding of your own unit economics and customer acquisition costs +- Access to publicly available information about the competitor (funding, team, product) +- Willingness to consider all options, including the possibility that direct competition is unwinnable + +--- + +## The Sequence + +### Step 1: Porter's Five Forces -- Assess the Threat Objectively + +Fear distorts perception. A well-funded competitor feels existential, but the actual threat depends on market structure: buyer switching costs, supplier dependencies, substitute availability, and real barriers to entry. Run a disciplined Five Forces analysis focused specifically on the competitive entrant. The goal is not to minimize the threat but to see it accurately -- many competitive "emergencies" turn out to be manageable when examined through structural rather than emotional lenses. + +**Checkpoint:** Written threat assessment with evidence-based severity rating (existential, significant, manageable, or negligible). + +### Step 2: Art of War -- Determine Your Strategic Position + +With the threat assessed, determine your strategic posture. Sun Tzu's framework offers four fundamental options: direct confrontation (you have advantages worth leveraging), strategic retreat (preserve resources and wait), flanking maneuver (attack where the competitor is not), or alliance (if you cannot beat them, consider whether joining forces serves your interests). Each option carries different resource requirements and risk profiles. + +**Checkpoint:** Clear strategic position selected with documented rationale. The leadership team is aligned on the chosen posture. + +--- + +### Decision Point: Fight or Flight? + +This is the critical branch. Based on Steps 1 and 2, determine whether the response is **direct confrontation** or **strategic repositioning**. + +**If direct confrontation:** Prioritize Step 4 (timing and first-mover dynamics). Speed matters when you are fighting for the same territory. Step 3 becomes secondary -- you will explore blue ocean options only if the direct fight proves unsustainable. + +**If strategic repositioning:** Prioritize Step 3 (Blue Ocean Strategy). Finding uncontested space is the priority. Step 4 becomes about timing the repositioning, not timing a competitive response. + +Both paths converge at Step 5, where the chosen strategy must be communicated clearly to the team. + +--- + +### Step 3: Blue Ocean Strategy -- Find Uncontested Space + +Map the value curves of your product and the competitor's. Identify dimensions where you compete head-to-head (and likely lose if they have more resources) versus dimensions where differentiation is possible. The objective is to find or create market space where the competitor's advantages -- scale, funding, brand recognition -- become less relevant. This is not retreat; it is strategic reframing. + +**Checkpoint:** Value curve comparison completed. At least two viable blue ocean opportunities identified with rough feasibility assessment. + +### Step 4: First-Mover Strategy -- Decide When to Act + +Not every competitive threat demands an immediate response. Analyze the timing dynamics: does the competitor have a first-mover advantage that compounds over time, or are there second-mover advantages available (letting them educate the market, learning from their mistakes, preserving your resources)? The analysis should produce a concrete recommendation: act within days, weeks, or months -- with specific triggers that would change the timeline. + +**Checkpoint:** Timing decision made with explicit triggers for acceleration or delay. Resource requirements estimated for the chosen timeline. + +### Step 5: Storytelling for Leaders -- Communicate Without Panic + +The team already knows about the competitor. Silence breeds anxiety; poorly framed communication breeds either panic or false complacency. Craft the internal narrative: acknowledge the threat honestly, present the strategic response with conviction, and give every team member a clear understanding of how their work connects to the competitive response. The external narrative -- for customers, investors, and partners -- requires separate framing. + +**Checkpoint:** Internal communication delivered. Team understands the strategy, their role in it, and the timeline for results. + +--- + +## Final Deliverable + +Upon completing all five steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Competitive Landscape Brief | `competitive-landscape-brief` | Investors, board | +| Competitive Response Action Plan | `action-plan` | Leadership team, all staff | +| Strategic Analysis One-Pager | `strategic-analysis-one-pager` | Board, advisors, key partners | + +## Common Pitfalls + +- **Reacting before analyzing.** Price cuts, feature rushes, and panicked pivots made in the first 48 hours almost always waste resources. The competitor's announcement is not your deadline. +- **Overestimating the competitor.** Large companies move slowly. Well-funded startups burn cash. A competitor's press release describes their aspirations, not their execution. +- **Underestimating the competitor.** The opposite error is equally dangerous. Dismissing a real threat as irrelevant because it conflicts with your narrative is a form of strategic negligence. +- **Copying the competitor's strategy.** If they are competing on price and you match it, you have chosen to fight their war with their weapons. Define your own competitive terms. +- **Hiding the situation from the team.** Transparency about competitive threats, paired with a clear response plan, builds trust. Secrecy builds only rumor and attrition. + +## Adaptation Notes + +- **Pre-revenue startups** facing competitive entry should weight Step 3 (blue ocean) heavily. Without revenue to defend, repositioning is low-cost and high-optionality. +- **Market leaders** facing a disruptive entrant should pay particular attention to the first-mover analysis in Step 4 -- incumbents often over-respond to threats that would have remained niche. +- **Bootstrapped companies** competing against venture-funded rivals cannot win a war of attrition. Steps 2 and 3 matter most: choose your battles and find differentiated positioning. +- **B2B companies** with long sales cycles have more time than they think. Customer switching costs provide a buffer -- use it for analysis rather than burning it on panic. diff --git a/plugins/foreman/content/playbooks/crisis-playbook.md b/plugins/foreman/content/playbooks/crisis-playbook.md new file mode 100644 index 0000000..0cd4e0b --- /dev/null +++ b/plugins/foreman/content/playbooks/crisis-playbook.md @@ -0,0 +1,136 @@ +--- +name: "crisis-playbook" +description: "Used when a company faces acute crisis -- revenue collapse, team + fractures, morale failure, or all three simultaneously. Chains financial + diagnosis, team assessment, Stoic clarity, cognitive debiasing, and + hard-decision frameworks into a compressed engagement designed for speed under + pressure." +trigger_diagnostics: + - revenue-diagnosis + - team-dysfunction-diagnosis + - leadership-crisis-diagnosis +steps: + - purpose: "Identify the financial root cause with diagnostic precision" + output: "Revenue failure analysis with causal tree and severity assessment" + kind: diagnostic + ref: revenue-diagnosis + - purpose: "Assess team damage -- who is leaving, who has already checked out, + where trust is broken" + output: "Team health assessment with dysfunction categories and flight risk map" + kind: diagnostic + ref: team-dysfunction-diagnosis + - skill: "stoic-control-and-clarity" + purpose: "Separate what the founder can control from what they cannot -- the + first prerequisite for sound crisis decisions" + output: "Control/influence/accept matrix applied to the specific crisis" + - skill: "enemies-of-clear-thinking" + purpose: "Identify which cognitive defaults -- emotion, ego, social pressure, + inertia -- are distorting the founder's judgment" + output: "Default audit with specific safeguards for each identified trap" + - skill: "tough-decision-situations" + purpose: "Make the hard calls with structured frameworks for bad-option scenarios" + output: "Decision matrix for crisis actions with trade-off analysis and sequencing" +final_outputs: + - action-plan + - investor-update-email + - weekly-ceo-review +estimated_duration: "2-4 hours" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +author: "Fatih Guner" +--- + +# The Crisis Playbook + +## When to Use This Playbook + +Revenue is dropping and nobody can agree on why. The best engineer just quit and two more are interviewing elsewhere. The all-hands meeting felt like a eulogy. The founder is making decisions at 2 AM that they reverse by 9 AM. + +This is not a strategy problem. This is a crisis -- a convergence of financial, organizational, and psychological pressure that demands a fundamentally different approach than normal operations. Crises punish deliberation and reward structured speed. This playbook is designed to be completed in hours, not weeks. + +The most dangerous moment in a crisis is not the crisis itself but the founder's first instinct. Panic produces either paralysis or frantic activity, both of which accelerate the decline. This playbook interposes structure between the crisis and the response. + +## Prerequisites + +- Honest acknowledgment that the company is in crisis (the hardest prerequisite) +- Access to current financial data: revenue, burn rate, runway, pipeline +- Willingness to make decisions that will be unpopular +- A block of 2-4 uninterrupted hours (crises do not accommodate fragmented calendars) +- At minimum one trusted advisor or co-founder available for a gut-check + +## The Sequence + +### Step 1: Revenue Diagnosis +- **Purpose:** Financial crisis and emotional crisis feel the same from inside. The numbers tell the truth that feelings obscure. This step runs the revenue diagnostic within the playbook itself -- not as a pre-requisite routing step, but as the opening analytical move. The goal is to locate the causal root: is revenue falling because of churn, failed acquisition, pricing collapse, market contraction, or a single customer concentration? +- **Key questions:** Where exactly is revenue declining? Is this a demand problem or a retention problem? When did the trend begin and what changed? How many months of runway remain at current burn? +- **Input:** Revenue data by segment, cohort retention, pipeline data, burn rate, cash position +- **Output:** Revenue failure analysis with causal hierarchy (root cause, contributing factors, symptoms) +- **Time:** 30-60 minutes +- **Checkpoint:** The root cause must be specific. "Revenue is down" is not a diagnosis. "Enterprise churn increased 40% after Q2 price increase while SMB acquisition held steady" is a diagnosis. Do not proceed until the cause is named. + +### Step 2: Team Dysfunction Diagnosis +- **Purpose:** Financial crises and people crises feed each other in a vicious cycle. Declining revenue creates fear; fear drives departures; departures increase workload on survivors; overwork produces more mistakes; mistakes accelerate revenue decline. This step breaks the cycle by mapping the human damage with clinical precision. +- **Key questions:** Who has already mentally departed? Where has trust broken down -- between founders, between leadership and team, or both? Which departures would be existential and which would be survivable? Is the team dysfunction a cause or a consequence of the financial crisis? +- **Input:** Attrition data, 1:1 notes, skip-level feedback, Slack sentiment (if available), recent exit interview themes +- **Output:** Team health map with dysfunction categories, flight risk assessment, and trust-break identification +- **Time:** 30-60 minutes +- **Checkpoint:** Distinguish between recoverable and terminal team damage. If the entire senior leadership layer is disengaged, the crisis response must prioritize retention before strategy. + +## Decision Point + +After completing Steps 1 and 2, the crisis reveals its nature: + +**Is this a financial crisis, a people crisis, or both?** + +- **Primarily financial (revenue root cause is clear, team is stressed but intact):** Proceed through Steps 3-5 with emphasis on financial decision-making. The team needs communication and direction, not intervention. +- **Primarily people (revenue is declining as a consequence of team dysfunction, not a cause):** Reweight the remaining steps. Step 3 (Stoic clarity) and Step 4 (enemies of clear thinking) apply directly to the founder's leadership posture. Step 5 (tough decisions) focuses on people decisions: who stays, who goes, how to rebuild trust. +- **Both (the common case):** Run all remaining steps fully. Sequence financial decisions first (they are more reversible than people decisions), then address team stabilization. Do not attempt to solve both simultaneously -- serial execution under crisis conditions outperforms parallel flailing. + +### Step 3: Stoic Control and Clarity +- **Purpose:** Crisis amplifies the founder's illusion of control over uncontrollable factors and, paradoxically, their sense of helplessness over factors they can actually influence. The Stoic dichotomy of control is not philosophy for philosophy's sake -- it is a triage tool. What can you act on today? What must you accept and stop spending emotional capital on? +- **Key questions:** Which elements of this crisis are within your direct control? Which can you influence but not determine? Which must you accept as given constraints? Where are you spending energy on things you cannot change? +- **Input:** Revenue diagnosis, team assessment, founder's current emotional state (honestly assessed) +- **Output:** Control/Influence/Accept matrix specific to this crisis, with action items only in the "Control" column +- **Time:** 20-30 minutes +- **Checkpoint:** The "Control" column should contain no more than 5-7 items. If it contains 15, the founder has not been honest about what they can actually control. If it contains 1, they have retreated into learned helplessness. + +### Step 4: Enemies of Clear Thinking +- **Purpose:** Under crisis pressure, four cognitive defaults hijack decision-making. The emotion default produces panic-driven decisions. The ego default prevents admitting the severity of the situation. The social default leads to consensus-seeking when decisive action is needed. The inertia default perpetuates the status quo when change is urgent. This step identifies which defaults are active and installs specific safeguards. +- **Key questions:** Which decisions in the past 48 hours were driven by fear rather than analysis? Where is ego preventing honest assessment? Are you seeking consensus to distribute blame? What obvious actions are you avoiding because they require change? +- **Input:** Recent decision log, control matrix from Step 3, honest self-assessment +- **Output:** Default audit identifying active traps, with specific countermeasures for each +- **Time:** 20-30 minutes +- **Checkpoint:** This step requires radical honesty. If the founder completes it and finds no active defaults, they have not completed it -- they have performed it. Every human under crisis pressure is subject to at least two of the four defaults. Name them or they will name you. + +### Step 5: Tough Decision Situations +- **Purpose:** The preceding steps provided clarity. This step demands action. Crisis decisions typically involve choosing between bad options -- layoffs vs. runway exhaustion, bridge round vs. down round, product cuts vs. quality collapse. The framework structures these choices so the founder selects the least-bad option deliberately rather than the most-comfortable one by default. +- **Key questions:** What are the 2-3 decisions that must be made within 48 hours? What are the second-order consequences of each option? Which decisions are reversible and which are permanent? What is the 70% threshold -- the point at which waiting for more information costs more than acting on incomplete data? +- **Input:** Revenue diagnosis, team assessment, control matrix, default audit +- **Output:** Decision matrix with options ranked by reversibility, time-sensitivity, and impact magnitude, plus a sequenced 48-hour action plan +- **Time:** 30-60 minutes +- **Checkpoint:** Each decision must have an owner and a deadline. Decisions without deadlines in a crisis are decisions not to decide. If any decision lacks a clear owner, the founder is the owner by default. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `action-plan` | Founder, leadership team | Immediate 48-hour crisis response plan with owners, deadlines, and decision sequencing | +| `investor-update-email` | Investors | Transparent crisis communication: what happened, what you know, what you are doing, what you need | +| `weekly-ceo-review` | Founder (self) | Operational tracking template for the 4-8 weeks following the crisis response | + +## Common Pitfalls + +1. **Moving too slowly.** The instinct to gather more data before acting is sound in normal operations and destructive in crisis. The 70% rule applies: if you have 70% of the information you need, act. The remaining 30% will cost more to acquire than the improvement in decision quality is worth. +2. **Communicating too late.** Investors, team members, and customers will learn about the crisis whether or not the founder tells them. Controlled, honest disclosure preserves trust. Delayed disclosure destroys it. Send the investor update within 48 hours of completing this playbook. +3. **Making all decisions simultaneously.** Crisis decisions interact. A layoff changes the product roadmap. A product cut changes the revenue forecast. A bridge round changes the equity structure. Sequence decisions so that each one informs the next. The action plan must specify order, not just content. +4. **Confusing activity with progress.** Under crisis pressure, founders often launch a dozen initiatives to feel productive. The control matrix from Step 3 and the decision framework from Step 5 exist to prevent this. Fewer actions, better executed, with clear ownership. +5. **Ignoring the founder's own state.** The Stoic clarity step is not optional self-help. A founder operating on three hours of sleep, driven by fear, making ego-defensive decisions will produce worse outcomes than a founder who takes four hours to run this playbook with a clear mind. The playbook's compressed timeline accounts for this -- 2-4 hours of focused work, not 2-4 hours stolen between emergencies. + +## Adaptation Notes + +- **Early-traction stage:** The crisis is likely existential. Runway is short, the team is small, and losing one person may be losing 20% of capacity. Step 5 decisions tend toward binary: pivot hard, seek a bridge, or wind down. The investor update is particularly critical -- early-stage investors may be willing to help if informed promptly. +- **Growth stage:** The crisis has more moving parts but also more resources. The team assessment (Step 2) becomes more complex because dysfunction may be localized to one department. Revenue diagnosis (Step 1) should segment by product line and geography. The action plan may involve restructuring rather than existential choices. +- **Scale stage:** Crisis at scale is public. Add a communications consideration to every decision: how will this be perceived by press, customers, and recruits? The investor update template may need board-level adaptation. The weekly CEO review becomes a daily review for the first two weeks. diff --git a/plugins/foreman/content/playbooks/first-100-customers-playbook.md b/plugins/foreman/content/playbooks/first-100-customers-playbook.md new file mode 100644 index 0000000..5983fe1 --- /dev/null +++ b/plugins/foreman/content/playbooks/first-100-customers-playbook.md @@ -0,0 +1,136 @@ +--- +name: "first-100-customers-playbook" +description: "Used when a founder has a product but no customers -- or too few to matter. Chains customer identification, feedback design, go-to-market positioning, founding narrative, outreach creation, and pitch urgency into a systematic early customer acquisition engagement. Use when revenue is zero or negligible and the founder needs a repeatable path to first traction." +trigger_diagnostics: + - product-market-fit-diagnosis + - revenue-diagnosis +steps: + - skill: "business-model-canvas" + purpose: "Clarify who the customer actually is -- not a demographic abstraction but a reachable individual" + output: "Refined canvas with a single, specific customer segment and validated value proposition hypothesis" + - skill: "net-promoter-score" + purpose: "Design a feedback loop from day one so every early customer interaction generates learning" + output: "NPS framework adapted for pre-scale deployment with qualitative follow-up triggers" + - skill: "four-ps-marketing" + purpose: "Design the initial go-to-market: product positioning, channel selection, and pricing for early adopters" + output: "Marketing mix tailored for early-adopter acquisition with channel-specific tactics" + - skill: "finding-your-stories" + purpose: "Discover the founding story that gives early customers a reason to believe and evangelise" + output: "Founding narrative with origin moment, personal stakes, and emotional resonance" + - skill: "writing-for-response" + purpose: "Create outreach that gets replies -- cold emails, landing page copy, DMs that convert" + output: "Three outreach templates (cold email, LinkedIn DM, landing page CTA) with response-optimised structure" + - skill: "building-story-stakes" + purpose: "Craft urgency into the early pitch so prospects act now rather than later" + output: "Stakes framework applied to pitch materials with temporal urgency and consequence language" +final_outputs: + - action-plan + - market-opportunity-summary +estimated_duration: "4-8 hours across 1-2 weeks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction +author: "Fatih Guner" +--- + +# The First 100 Customers Playbook + +## When to Use This Playbook + +The product exists. Customers do not. Or worse -- a handful of users signed up, poked around, and vanished. The founder has built something and now confronts the disorienting reality that building and selling require entirely different muscles. + +This playbook applies when the problem is not product quality but customer acquisition at the earliest stage. The founder cannot yet afford paid channels, does not have inbound traffic, and needs to find, reach, and convert customers one at a time. The first 100 customers are hand-to-hand combat, not air warfare. Every skill in this sequence is designed for that reality. + +If the product has already achieved moderate traction (hundreds of active users, consistent organic growth), this playbook is too elementary. Route instead to `scaling-playbook` or `four-ps-marketing` directly. + +## Prerequisites + +- A functional product or credible MVP (not a slide deck) +- Clarity on what the product does, even if clarity on who wants it is lacking +- Willingness to do unscalable things: manual outreach, personal onboarding, individual conversations +- Enough runway to sustain 4-8 weeks of customer development without revenue pressure +- An email account and a willingness to hear "no" repeatedly + +## The Sequence + +### Step 1: Business Model Canvas +- **Purpose:** Most founders at this stage describe their customer as "small businesses" or "millennials who care about health." These are not customers -- they are census categories. The canvas forces precision: a specific segment, a specific pain, a specific channel to reach them, and a specific reason they would pay. +- **Key questions:** Can you name ten individuals who match the customer profile? Where do they congregate (online or offline)? What are they currently using to solve the problem you address? +- **Input:** Product description, founder assumptions about the market, any early usage data +- **Output:** Refined canvas with a customer segment specific enough to reach individually +- **Time:** 1-1.5 hours +- **Checkpoint:** The customer segment must pass the "can you email ten of them by Friday?" test. If the answer is no, the segment is too broad. + +## Decision Point + +After completing Step 1, a critical gate: + +**Is the customer segment specific enough to reach individually?** + +- If the segment remains broad ("SMBs" or "health-conscious consumers"), narrow it further before proceeding. A broad segment makes every subsequent step -- outreach, messaging, pricing -- vague and ineffective. Return to the canvas and pick a niche within the niche. +- If the founder can name specific companies, specific communities, or specific individuals who match the profile -- proceed. Precision here compounds through every remaining step. + +Reaching 100 customers begins with being able to name the first ten. + +### Step 2: Net Promoter Score +- **Purpose:** At zero customers, NPS seems premature. It is not. Designing the feedback mechanism before the first customer arrives ensures that every interaction produces actionable data, not just revenue. The founders who learn fastest win the early-traction race. +- **Key questions:** How will you survey your first users? At what moment in the experience? What qualitative follow-up question will you ask promoters and detractors? +- **Input:** Product experience map, customer touchpoints, onboarding flow +- **Output:** Pre-launch NPS framework with survey timing, question design, and escalation triggers +- **Time:** 0.5-1 hour +- **Checkpoint:** The NPS framework must be lightweight enough that a single founder can run it manually. If it requires tooling that does not exist yet, simplify. + +### Step 3: Four Ps Marketing +- **Purpose:** Positioning, pricing, place, and promotion -- the four decisions that determine whether the right customers find the product and find the price acceptable. At this stage, the emphasis falls on channel selection (where to reach early adopters) and pricing psychology (how to price for learning, not revenue maximisation). +- **Key questions:** Which single channel gives you the highest probability of reaching your specific segment? Should you price low to reduce friction, price high to signal value, or offer free trials to accelerate learning? What positioning separates you from the alternative the customer uses today? +- **Input:** Customer segment from Step 1, competitive landscape, product capabilities +- **Output:** Marketing mix with one primary channel, initial pricing rationale, and positioning statement +- **Time:** 1-1.5 hours +- **Checkpoint:** If the plan includes more than two acquisition channels, it is too ambitious for a founder without a marketing team. Pick one channel. Dominate it. Add the second channel at customer 50. + +### Step 4: Finding Your Stories +- **Purpose:** Early customers buy from founders, not from companies. The founding story -- why this problem, why this founder, why now -- is the most powerful acquisition tool at pre-traction stage. This step surfaces the authentic narrative that turns a cold email into a human connection. +- **Key questions:** What personal experience led to building this product? What did you see that others missed? What is at stake for you personally? +- **Input:** Founder biography, origin of the idea, personal connection to the problem +- **Output:** Founding narrative arc: origin moment, personal stakes, mission, and the invitation to join early +- **Time:** 0.5-1 hour +- **Checkpoint:** Read the story to someone who knows nothing about the product. If they ask a follow-up question, the story works. If they nod politely, rewrite. + +### Step 5: Writing for Response +- **Purpose:** The gap between a founder who sends 100 cold emails and gets 2 replies versus 15 replies is not luck -- it is craft. This step applies the science of response-oriented writing: reducing friction, making the ask specific, respecting the reader's cognitive load, and earning the click. +- **Key questions:** Is the subject line specific enough to avoid the spam filter and generic enough to avoid the trash? Does the first sentence establish relevance? Is the call to action a single, low-friction step? +- **Input:** Customer segment from Step 1, founding story from Step 4, positioning from Step 3 +- **Output:** Three outreach templates: cold email, LinkedIn message, and landing page CTA block +- **Time:** 1-1.5 hours +- **Checkpoint:** Test the cold email on five people outside the target segment. If they understand the ask within ten seconds, the writing is clear enough for a busy prospect. + +### Step 6: Building Story Stakes +- **Purpose:** A pitch without urgency is a suggestion. Early-stage founders often present their product as "useful" without explaining why the prospect should act now rather than next quarter. Stakes create the temporal pressure that converts interest into action. +- **Key questions:** What does the prospect lose by waiting? Is there a limited beta, a founding-member price, or a competitive window that creates genuine scarcity? How do you communicate urgency without resorting to manufactured pressure? +- **Input:** Outreach templates from Step 5, product roadmap, early-adopter offer structure +- **Output:** Stakes-enhanced versions of all outreach materials with urgency drivers +- **Time:** 0.5-1 hour +- **Checkpoint:** The urgency must be genuine. Manufactured scarcity ("only 5 spots left!" when the cap is fictitious) destroys trust at the stage where trust is everything. If no authentic urgency exists, create it through an early-adopter programme with genuine exclusivity. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `action-plan` | Founder, team | Week-by-week acquisition plan: channels, targets, outreach cadence, feedback loops | +| `market-opportunity-summary` | Founder, early advisors | Concise summary of target segment, positioning, and early evidence for the opportunity | + +## Common Pitfalls + +1. **Going broad to go fast.** The temptation to cast a wide net feels productive but dilutes every message. The first 100 customers come from a niche, not a market. +2. **Building before selling.** Founders who respond to slow customer acquisition by returning to the product are hiding in their comfort zone. The product is not the bottleneck -- distribution is. +3. **Ignoring the feedback loop.** Acquiring 100 customers who never speak to you again is worse than acquiring 30 who tell you exactly what they think. The NPS step exists for this reason. +4. **Pricing too low out of insecurity.** Free users and drastically underpriced customers behave differently from real customers. Price at a level that attracts people willing to pay, even if the number is small. Willingness to pay is a signal; free usage is noise. +5. **Writing outreach that talks about the product instead of the prospect.** Every cold email should be about the reader's problem, not the founder's solution. The product is the answer; the email is the question. + +## Adaptation Notes + +- **Idea stage:** The product may be a prototype or concierge MVP. The first 100 "customers" may be beta testers or design partners rather than paying users. Adapt the pricing step accordingly -- the currency at this stage is feedback, not revenue. +- **Validation stage:** Some early traction exists but is inconsistent. The canvas refinement (Step 1) should build on existing data: who converted and why? Who churned and why? The segment becomes sharper with evidence. +- **Early-traction stage:** The playbook shifts from finding customers to systematising the acquisition channel that works. If one channel produced the first 30 customers, the remaining 70 should come from scaling that channel before experimenting with new ones. diff --git a/plugins/foreman/content/playbooks/founder-transition-playbook.md b/plugins/foreman/content/playbooks/founder-transition-playbook.md new file mode 100644 index 0000000..b044ff9 --- /dev/null +++ b/plugins/foreman/content/playbooks/founder-transition-playbook.md @@ -0,0 +1,143 @@ +--- +name: "founder-transition-playbook" +description: "Supports founders navigating the shift from individual contributor or technical founder to CEO and executive leader. Chains self-assessment, leadership style development, delegation mastery, executive presence, and philosophical resilience into a sustained development arc. Use when a founder recognizes that the skills that built the product are insufficient to lead the organization." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth +trigger_diagnostics: + - leadership-crisis-diagnosis +steps: + - skill: "leader-self-reflection" + purpose: "Surface an honest inventory of current leadership strengths, blind spots, and defaults under pressure" + output: "Self-assessment document covering leadership patterns, energy drains, and the gap between current role and required role" + - skill: "leadership-style-adaptation" + purpose: "Identify the founder's default leadership style and map where it creates value versus where it creates friction" + output: "Style profile with situational adaptation plan — when to lean into defaults and when to consciously override them" + - skill: "delegation-and-empowerment" + purpose: "Build the operational discipline of releasing tasks, decisions, and ownership to others" + output: "Delegation matrix with authority levels, accountability structures, and a personal stop-doing list" + - skill: "senior-leadership-transition" + purpose: "Confront the mental shifts required to move from building the product to building the company" + output: "Transition roadmap covering identity shifts, time allocation changes, and new success metrics" + - skill: "leadership-voice-and-presence" + purpose: "Develop the executive communication capability that the new role demands" + output: "Communication framework covering all-hands, board presentations, one-on-ones, and crisis moments" + - skill: "stoic-control-and-clarity" + purpose: "Build a philosophical foundation for leading under uncertainty without being consumed by it" + output: "Personal operating principles grounded in what the founder can control, with practices for the rest" +final_outputs: + - leadership-reflection + - career-strategy-canvas + - weekly-ceo-review +estimated_duration: "Ongoing — initial pass 4-6 hours, then weekly practice" +author: "Fatih Guner" +--- + +# Founder Transition Playbook + +The founder who writes the first line of code and the CEO who leads a sixty-person company are, functionally, different jobs held by the same person. Nobody tells you this when you start. The skills that made you indispensable at five employees — technical depth, hands-on problem solving, the ability to do everything yourself — become the precise skills that make you a bottleneck at thirty. The transition is not a promotion. It is a professional identity crisis dressed in organizational language. + +--- + +## When to Use This Playbook + +- The founder spends more time in code or product than in leadership, and the team is suffering for it +- Direct reports are waiting for decisions that only the founder can make — because the founder has not empowered anyone else to make them +- The founder dreads all-hands meetings, board presentations, or difficult conversations with senior hires +- Feedback from the team (or the board) suggests the founder's leadership is not scaling with the company +- The founder intellectually accepts the need to change but finds the actual behavioural shift elusive +- A first-time founder is about to hire their first layer of management and has no model for how to lead leaders + +## Prerequisites + +- Genuine willingness to change — not merely acknowledgement that change might theoretically be beneficial +- At least one trusted person (co-founder, coach, board member, advisor) willing to provide candid feedback +- Enough organizational stability to permit the founder to invest time in development rather than firefighting +- An honest answer to the question: do you actually want to be CEO, or do you want to build products? + +--- + +## The Sequence + +### Step 1: Leader Self-Reflection — Where Are You Now? + +Before developing anything, diagnose accurately. This step produces an honest inventory of leadership patterns: how the founder makes decisions under pressure, where energy is spent versus where it should be spent, which situations trigger the founder's best instincts and which trigger their worst. The assessment must be grounded in specific incidents, not abstract self-perception. + +**Checkpoint:** The self-assessment identifies at least three concrete patterns — not vague generalities like "I need to delegate more" but specific behaviours like "I rewrite engineers' code after they submit it." + +--- + +### Decision Point: Capability Gap or Willingness Gap? + +The distinction matters profoundly and shapes the entire remainder of this playbook. + +**Willingness gap:** The founder knows what executive leadership looks like but resists the change. The identity of "builder" or "technical genius" feels more authentic than "leader." The resistance is emotional and philosophical, not informational. Delegation feels like loss rather than leverage. The all-hands meeting feels performative rather than purposeful. + +- **If willingness:** Prioritize Steps 4 and 6 immediately. The senior leadership transition work confronts the identity shift directly, and the Stoic clarity framework provides philosophical grounding for accepting the new role without resentment. Return to Steps 2, 3, and 5 once the internal resistance has been addressed. + +**Capability gap:** The founder genuinely wants to lead differently but lacks the skills. They have never managed managers, never presented to a board, never navigated a difficult termination. The gap is not resistance — it is inexperience. + +- **If capability:** Proceed sequentially through Steps 2, 3, and 5, which build concrete skills in style adaptation, delegation mechanics, and executive communication. Steps 4 and 6 provide valuable context but are less urgent. + +Most founders exhibit a blend of both. Start with the dominant one. + +--- + +### Step 2: Leadership Style Adaptation — Know Your Defaults + +Every founder has a default leadership style that emerged organically during the company's earliest days. It worked — otherwise the company would not exist. The problem is that a single style optimized for a five-person team becomes a liability in a forty-person organization. This step maps the founder's natural style against the situations that now demand a different approach: managing senior hires who resist micromanagement, leading through ambiguity rather than directive clarity, coaching rather than solving. + +**Checkpoint:** The founder can name their default style and articulate three specific situations where it produces friction rather than results. + +### Step 3: Delegation and Empowerment — Learn to Let Go + +Delegation is not task assignment. It is the transfer of authority, decision rights, and accountability — and the founder's willingness to accept imperfect execution as the price of organizational capacity. This step builds a systematic delegation practice: categorizing decisions by reversibility and impact, assigning clear authority levels, and establishing accountability without surveillance. + +**Checkpoint:** A written delegation matrix exists. The founder has identified at least five decisions they currently make that someone else should own, and has transferred at least two of them. + +### Step 4: Senior Leadership Transition — The Mental Shifts + +The move from IC to executive is not an expansion of the same job — it is a different job. This step confronts the specific mental shifts required: from solving problems to defining which problems matter, from personal productivity to organizational productivity, from being the smartest person in the room to hiring people smarter than you and then getting out of their way. The output is a transition roadmap that makes these shifts explicit and measurable. + +**Checkpoint:** The founder can articulate their new job description — not in aspirational terms, but in concrete weekly time allocation and decision domains. + +### Step 5: Leadership Voice and Presence — Executive Communication + +Technical founders often communicate in specifications: precise, detailed, and utterly uninspiring. Executive leadership requires a different register — one that conveys vision without vagueness, confidence without arrogance, and vulnerability without weakness. This step develops the founder's communication capability across the formats that matter most: all-hands addresses, board presentations, one-on-one conversations with senior leaders, and crisis communication. + +**Checkpoint:** The founder has drafted and delivered at least one all-hands narrative and one board-level strategic summary, and has received feedback on both. + +### Step 6: Stoic Control and Clarity — The Philosophical Foundation + +Leadership under uncertainty is, at its core, a philosophical problem. The founder cannot control market conditions, competitor moves, or employee departures. They can control their response, their preparation, and their decision-making discipline. Stoic philosophy — specifically the distinction between what is in your control and what is not — provides a practical operating system for the anxiety, isolation, and weight that come with executive leadership. + +**Checkpoint:** The founder has articulated a personal set of operating principles that distinguish between controllable and uncontrollable domains, with specific practices for each. + +--- + +## Final Deliverable + +| Output | Template | Audience | +|--------|----------|----------| +| Leadership Self-Assessment | `leadership-reflection` | Founder (private), coach or advisor | +| Career Strategy Canvas | `career-strategy-canvas` | Founder, board (if appropriate) | +| Weekly CEO Review | `weekly-ceo-review` | Founder (ongoing self-governance tool) | + +## Common Pitfalls + +1. **Treating this as a one-time exercise.** The transition is not a workshop — it is an ongoing developmental practice. The weekly CEO review exists precisely to sustain the discipline beyond the initial pass. +2. **Hiring a COO instead of developing.** Bringing in an operator to compensate for the founder's leadership gaps works temporarily but creates a dependency. The founder still needs to lead the COO. +3. **Confusing delegation with abdication.** Handing off a function and never checking on it is not empowerment — it is abandonment. Delegation requires new feedback loops, not the absence of them. +4. **Skipping the willingness question.** Capability development applied to a willingness problem produces a technically skilled leader who still resists leading. The resistance must be addressed first. +5. **Benchmarking against professional CEOs.** First-time founders are not competing with seasoned executives. The goal is sufficient leadership capability for the current stage, not perfection. + +## Adaptation Notes + +- **Validation stage:** The transition may be premature. If the company has fewer than five people, the founder's IC skills are likely still the highest-leverage contribution. Revisit when the team reaches 8-10. +- **Early-traction stage:** This is where most founder transitions begin in earnest. The first management hire often triggers the identity crisis. Steps 1-3 carry the highest immediate value. +- **Growth stage:** At growth, the transition should already be underway. If it is not, the urgency increases — the organization is scaling around a leadership model that cannot support it. Compress the timeline and consider an executive coach as an accelerant. +- The weekly CEO review template is the most important long-term output. It transforms this playbook from a one-time intervention into a sustained leadership discipline. diff --git a/plugins/foreman/content/playbooks/fundraising-playbook.md b/plugins/foreman/content/playbooks/fundraising-playbook.md new file mode 100644 index 0000000..d1a18e0 --- /dev/null +++ b/plugins/foreman/content/playbooks/fundraising-playbook.md @@ -0,0 +1,148 @@ +--- +name: "fundraising-playbook" +description: "Used when a founder is preparing to raise a funding round. Chains business model validation, strategic assessment, competitive analysis, customer proof points, narrative construction, negotiation preparation, and deck refinement into a comprehensive fundraising engagement." +trigger_diagnostics: + - fundraising-diagnosis +steps: + - skill: "business-model-canvas" + purpose: "Ensure the business model is coherent and investable before approaching investors" + output: "Validated canvas with unit economics and key assumptions surfaced" + - skill: "swot-pest-analysis" + purpose: "Prepare an honest strategic assessment that anticipates due diligence questions" + output: "SWOT-PEST matrix with investor-facing framing of weaknesses and threats" + - skill: "porters-five-forces" + purpose: "Map the competitive landscape with the rigor investors expect" + output: "Five forces analysis with defensibility narrative and moat assessment" + - skill: "net-promoter-score" + purpose: "Generate customer validation data that proves demand beyond revenue figures" + output: "NPS analysis with segment breakdown and verbatim customer quotes" + - skill: "story-structure-and-arc" + purpose: "Craft the fundraising narrative that connects problem, traction, and vision" + output: "Story arc with five-second moment, stakes, and temporal structure" + - skill: "competitive-negotiation" + purpose: "Prepare for term sheet negotiation with tactical frameworks" + output: "Negotiation preparation sheet with BATNA, anchoring strategy, and concession plan" + - skill: "writing-for-navigation" + purpose: "Make the fundraising deck scannable -- investors read decks in 3 minutes" + output: "Deck structure with visual hierarchy, headlines, and navigation cues" +final_outputs: + - fundraising-deck-outline + - unit-economics-snapshot + - competitive-landscape-brief + - investor-update-email +estimated_duration: "8-15 hours across 2-4 weeks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth +author: "Fatih Guner" +--- + +# The Fundraising Playbook + +## When to Use This Playbook + +The founder has decided to raise external capital. The decision itself is already made -- this playbook does not address whether to raise. It addresses how to raise well: with a model that survives scrutiny, a narrative that compels, data that validates, and a negotiation posture that protects founder interests. + +Most fundraising fails not in the pitch meeting but in the preparation. Founders build decks before they build arguments. They rehearse slides before they understand their own unit economics. This playbook reverses that sequence: substance first, presentation last. + +## Prerequisites + +- A clear funding target (amount and use of proceeds) +- At least 3 months of financial data (revenue, burn, margins) or a detailed financial model +- A functioning product with some form of customer traction (revenue, users, LOIs, or pilots) +- An honest assessment of current runway +- Willingness to hear that the company may not be ready to raise + +## The Sequence + +### Step 1: Business Model Canvas +- **Purpose:** Investors fund models, not products. This step forces the founder to articulate the complete business model with the precision that due diligence demands. Every canvas block must be defensible. +- **Key questions:** What are the unit economics? Which assumptions remain unvalidated? Where does the model break at scale? What is the LTV:CAC ratio? +- **Input:** Financial data, customer acquisition data, pricing model, channel performance +- **Output:** Investor-grade Business Model Canvas with unit economics overlay +- **Time:** 1.5-2 hours +- **Checkpoint:** If unit economics are negative with no credible path to positive, stop. Fix the fundamentals before raising. + +## Decision Point + +After completing Step 1, a critical gate: + +**Is the business actually ready to raise?** + +- If unit economics are broken (negative gross margins, CAC exceeding LTV with no improvement trajectory, or a business model that requires magical thinking to reach profitability) -- pause the playbook. Fix the model first. Raising on broken economics means raising at a bad valuation with desperate terms. +- If the model is sound but early, or if the economics work at modest scale -- proceed. Investors at pre-seed and seed expect incomplete data, but they do not forgive incoherent models. + +Raising money on a broken model does not fix the model. It postpones the reckoning while adding dilution. + +### Step 2: SWOT-PEST Analysis +- **Purpose:** Every competent investor will probe weaknesses. Founders who discover their own vulnerabilities first can frame them as risks being actively managed rather than blind spots. PEST analysis surfaces macro trends that strengthen or undermine the thesis. +- **Key questions:** Which weaknesses will investors find in diligence? Which macro trends support the timing argument? What regulatory or market shifts could invalidate the thesis? +- **Input:** Business Model Canvas from Step 1, market research, regulatory landscape +- **Output:** SWOT-PEST matrix with pre-written responses to likely investor objections +- **Time:** 1-1.5 hours +- **Checkpoint:** Every weakness must have a mitigation plan. Every threat must have a monitoring trigger. Investors respect founders who know where the bodies are buried. + +### Step 3: Porter's Five Forces +- **Purpose:** "What's your competitive moat?" is the question investors ask most and founders answer worst. This step builds a rigorous competitive analysis that goes beyond a logo slide of competitors. +- **Key questions:** How strong is buyer power? What is the threat of substitution? Where are the barriers to entry? Who are the real competitors -- not just the obvious ones? +- **Input:** Market data, competitor intelligence, SWOT output from Step 2 +- **Output:** Five forces map with defensibility narrative and specific moat evidence +- **Time:** 1-2 hours +- **Checkpoint:** If the five forces analysis reveals a market with low barriers, high substitution threat, and powerful buyers -- the fundraising narrative must address this head-on. Ignoring it is worse than owning it. + +### Step 4: Net Promoter Score +- **Purpose:** Revenue tells investors what happened. NPS tells them what will happen. A high NPS with qualitative depth proves that customers are not just buying but advocating -- the leading indicator of sustainable growth. +- **Key questions:** What is the NPS by segment? What do promoters say in their own words? What drives detractors? How does NPS correlate with retention? +- **Input:** Customer survey data, support tickets, churn data, qualitative interviews +- **Output:** NPS analysis with segment breakdown, trend data, and verbatim quotes suitable for the deck +- **Time:** 1-2 hours +- **Checkpoint:** If NPS is below 30, the product story in the deck must lean on other proof points. Low NPS does not prevent fundraising, but it changes the narrative from "customers love us" to "we have a clear path to product excellence." + +### Step 5: Story Structure and Arc +- **Purpose:** A fundraising pitch is a story. The best decks follow a narrative arc: the world has a problem, the problem is getting worse, we discovered something others missed, here is the proof, here is what happens next. This step constructs that arc with the rigor of professional storytelling. +- **Key questions:** What is the founding insight -- the moment of discovery? Where are the stakes? What is the "But & Therefore" structure of the narrative? +- **Input:** All outputs from Steps 1-4, founder's personal story, market timing data +- **Output:** Complete narrative arc with opening hook, escalating stakes, traction proof, and vision close +- **Time:** 1-2 hours +- **Checkpoint:** Test the narrative on someone outside the company. If they cannot retell the core thesis in two sentences after hearing it once, the story is not sharp enough. + +### Step 6: Competitive Negotiation +- **Purpose:** Term sheets arrive fast and expire faster. Founders who have not prepared a negotiation strategy accept terms they later regret. This step builds the tactical framework before the pressure begins. +- **Key questions:** What is the BATNA? What terms are non-negotiable? Where can you concede without structural damage? How do you create competitive tension between investors? +- **Input:** Funding target, current cap table, market comparables, investor pipeline +- **Output:** Negotiation preparation sheet with BATNA, red lines, concession hierarchy, and anchoring strategy +- **Time:** 1-1.5 hours +- **Checkpoint:** If the BATNA is "run out of money," the negotiating position is weak by definition. Acknowledge this internally and plan accordingly -- but never signal it externally. + +### Step 7: Writing for Navigation +- **Purpose:** Investors skim decks in under three minutes during first pass. If the deck is not scannable, the story from Step 5 never gets heard. This step applies cognitive science to deck structure: headlines that carry the argument, visual hierarchy that guides the eye, and information architecture that survives rapid scanning. +- **Key questions:** Can an investor extract the core thesis from headlines alone? Is every slide earning its place? Does the deck flow as a narrative when read top-to-bottom? +- **Input:** Story arc from Step 5, all analytical outputs from Steps 1-4 +- **Output:** Deck structure with slide-by-slide headlines, hierarchy notes, and navigation cues +- **Time:** 1-2 hours +- **Checkpoint:** Print the deck. Read only the headlines. If the headlines alone tell a coherent, compelling story, the structure is sound. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `fundraising-deck-outline` | Investors | Structured deck skeleton with narrative arc and data placement | +| `unit-economics-snapshot` | Investors | One-page unit economics with assumptions and sensitivity analysis | +| `competitive-landscape-brief` | Investors | Five forces summary with positioning and moat evidence | +| `investor-update-email` | Existing investors | Pre-raise update that signals momentum and invites participation | + +## Common Pitfalls + +1. **Building the deck before the model.** A beautiful presentation of broken economics is still broken economics. The canvas and unit economics come first -- always. +2. **Hiding weaknesses.** Sophisticated investors discover every weakness in diligence. Founders who surface vulnerabilities proactively and pair them with mitigation plans build trust. Founders who hide them destroy it. +3. **Optimizing for the first meeting.** The first meeting gets the second meeting. The due diligence survives or kills the deal. This playbook weights preparation for diligence, not just the pitch. +4. **Neglecting negotiation preparation.** Most founders spend 95% of fundraising energy on getting to "yes" and 5% on terms. The terms matter more. A bad term sheet on a good valuation is worse than a fair term sheet on a lower one. +5. **Raising too early.** The decision point after Step 1 exists for a reason. Capital raised on a broken model creates a ticking clock with investor expectations attached. Sometimes the best fundraising decision is to wait. + +## Adaptation Notes + +- **Validation stage:** Investors expect a thesis, not a spreadsheet. Lean harder on Steps 5 (narrative) and 3 (market analysis). Unit economics will be modeled, not proven -- acknowledge the assumptions explicitly. +- **Early-traction stage:** The balance shifts toward data. NPS (Step 4) and unit economics (Step 1) carry disproportionate weight. The narrative should be "here is what we have proven" rather than "here is what we believe." +- **Growth stage:** Investors at this stage are buying a machine, not a story. The canvas must show scalable economics. The five forces analysis must demonstrate durable competitive advantages. Negotiation preparation (Step 6) becomes critical as deal sizes increase and terms grow more complex. diff --git a/plugins/foreman/content/playbooks/innovation-sprint-playbook.md b/plugins/foreman/content/playbooks/innovation-sprint-playbook.md new file mode 100644 index 0000000..df4ef62 --- /dev/null +++ b/plugins/foreman/content/playbooks/innovation-sprint-playbook.md @@ -0,0 +1,150 @@ +--- +name: "innovation-sprint-playbook" +description: "Structures a two-week innovation sprint to generate, refine, and select new product concepts, creative solutions, or strategic pivots. Chains creative perception, disciplined practice, structured ideation, concept refinement, and rigorous evaluation into a time-boxed engagement. Use when the company needs fresh ideas under deadline pressure — whether for product innovation, market repositioning, or internal problem-solving." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +trigger_diagnostics: + - innovation-drought-diagnosis +steps: + - skill: "creative-perception-and-awareness" + purpose: "Open the team's creative antennae — shift from operational thinking to generative thinking" + output: "Perception log documenting observations, assumptions challenged, and fresh angles on the problem space" + - skill: "creative-practice-and-habit" + purpose: "Establish the sprint's creative discipline so ideation is structured rather than sporadic" + output: "Sprint operating rhythm with daily creative practices, constraints, and accountability mechanisms" + - skill: "generating-solutions" + purpose: "Produce volume through structured ideation — brainstorming, BrainSwarming, design thinking, and lateral approaches" + output: "Raw idea inventory with at least 20-30 concepts across multiple methods" + - skill: "creative-shaping-and-craft" + purpose: "Refine raw ideas into viable concepts with enough definition to evaluate seriously" + output: "Shaped concept briefs — each with a value proposition, target user, key assumptions, and feasibility assessment" + - skill: "evaluating-options" + purpose: "Evaluate and select the strongest concepts using structured criteria rather than enthusiasm" + output: "Scored evaluation matrix with top 2-3 concepts selected for development, supported by explicit reasoning" +final_outputs: + - new-initiative-brief + - retrospective-template +estimated_duration: "10-15 hours across 2 weeks (structured sprint)" +author: "Fatih Guner" +--- + +# Innovation Sprint Playbook + +Creativity on demand sounds like a contradiction. It is not. The myth of inspiration — the notion that good ideas arrive unbidden while staring at a sunset — has done more damage to corporate innovation than any bureaucratic process ever could. The companies that consistently generate viable new concepts do so through structured discipline, not creative genius. They create conditions where ideas emerge reliably, apply craft to refine them, and use rigorous evaluation to select the survivors. This playbook compresses that discipline into two weeks. + +--- + +## When to Use This Playbook + +- The product roadmap has gone stale and the team is iterating on features nobody asked for +- A competitive threat demands a creative response that cannot wait for the next planning cycle +- The company needs to explore adjacent markets, new revenue streams, or product extensions +- Internal brainstorming sessions produce enthusiasm but not executable concepts +- The founder senses that the team has stopped thinking creatively and is operating on autopilot +- A strategic pivot is on the table and the company needs multiple directions to evaluate + +## Prerequisites + +- A clearly defined problem space or opportunity area (the sprint is not a fishing expedition — it has boundaries) +- A dedicated team of 3-8 people who can commit focused time across the two-week sprint +- Executive sponsorship with the authority to act on the sprint's outputs +- Willingness to follow the process even when early results feel unproductive — creative discipline requires trust in the structure and a dedicated physical or virtual space with visible artifacts from each step + +--- + +## The Sequence + +### Week 1: Generate + +#### Step 1: Creative Perception and Awareness — Open the Antennae + +Before generating ideas, recalibrate how the team sees. Operational thinking narrows perception to the familiar: existing customers, current competitors, known constraints. Creative perception deliberately widens the aperture. This step uses observation exercises, assumption inventories, and perspective-shifting techniques to help the team notice what they have been filtering out. The value is not in the exercises themselves but in the cognitive shift they produce. + +**Sprint day:** Day 1 (2-3 hours) + +**Checkpoint:** Each team member has documented at least three observations about the problem space that they had previously overlooked or taken for granted. + +#### Step 2: Creative Practice and Habit — Establish the Sprint Discipline + +A two-week sprint without structure degenerates into a two-week meeting. This step establishes the creative operating rhythm: daily practices (morning freewriting, constraint challenges, cross-domain analogies), session structures (timed divergence, silent generation before group discussion), and accountability mechanisms (idea quotas, daily artifacts). The discipline creates the container within which creativity operates productively. + +**Sprint days:** Day 1-2 (establish rhythm, then maintain daily) + +**Checkpoint:** The sprint cadence is documented and the team has completed at least one full cycle of the daily creative practice. Resistance to the structure has been surfaced and addressed. + +#### Step 3: Generating Solutions — Structured Ideation + +Volume before quality. This step runs the team through multiple ideation methods — not just traditional brainstorming (which tends to favour the loudest voice) but also BrainSwarming (silent, visual, simultaneous), design thinking (empathy-driven reframing), and lateral thinking techniques (random entry, reversal, analogy). Each method produces a different category of idea. The deliberate variation in method prevents the team from circling the same conceptual territory. + +**Sprint days:** Days 3-5 (6-8 hours total across three sessions) + +**Checkpoint:** The team has produced a minimum of 20-30 raw ideas, generated through at least three distinct methods. Ideas are documented visually, not buried in a spreadsheet. + +--- + +### Decision Point: Quantity Check + +Pause. Count the raw material. + +**Fewer than 15 ideas:** The ideation phase has underperformed. This is not unusual — the first method often produces the obvious ideas, and teams mistake "we've covered the obvious" for "we've exhausted the space." Return to Step 3 with a different method before proceeding. + +- If brainstorming dominated, switch to BrainSwarming (silent, written, simultaneous contribution). +- If design thinking dominated, switch to lateral thinking (random entry point, reversal, or cross-domain analogy). +- If the team insists they have generated enough ideas, challenge them: are these truly distinct concepts or variations on three themes? + +**15-30 ideas:** Sufficient raw material. Proceed to Step 4. + +**More than 30 ideas:** Strong position. The shaping step will be more demanding, but the evaluation step will have better material to work with. Proceed with confidence. + +The temptation to skip this checkpoint and rush into refinement is strong. Resist it. Shaping weak material produces polished mediocrity. The quality of the final output is bounded by the quantity of the raw input. + +--- + +### Week 2: Refine and Select + +#### Step 4: Creative Shaping and Craft — Refine Raw Ideas into Concepts + +Raw ideas are provocations, not proposals. This step applies craft: each promising idea is developed into a concept brief with a defined value proposition, a target user, key assumptions, a feasibility assessment, and at least one reason it might fail. The shaping process is deliberately critical — not to kill ideas but to strengthen them. Concepts that survive shaping are genuinely viable; those that do not were never going to survive contact with reality. + +**Sprint days:** Days 6-8 (6-8 hours total) + +**Checkpoint:** At least 5-8 shaped concepts exist, each documented in enough detail that someone outside the sprint team could understand and evaluate them. Concepts that collapsed during shaping are archived with reasons — they inform future sprints. + +#### Step 5: Evaluating Options — Select the Strongest Concepts + +Enthusiasm is not a selection criterion. This step applies structured evaluation: define explicit criteria (strategic fit, feasibility, market size, competitive differentiation, time to value), weight them according to the company's current priorities, and score each concept. Use techniques like Even Swaps to resolve close calls and risk ranking to surface hidden vulnerabilities. The output is a ranked list with the top 2-3 concepts selected for development, each supported by a clear rationale for selection. + +**Sprint days:** Days 9-10 (3-4 hours total) + +**Checkpoint:** The selection is defensible. Each chosen concept has a written rationale that a sceptical executive could interrogate. Rejected concepts have documented reasons that respect the work invested. + +--- + +## Final Deliverable + +| Output | Template | Audience | +|--------|----------|----------| +| New Initiative Brief (one per selected concept) | `new-initiative-brief` | Leadership team, product team, potential sponsors | +| Sprint Retrospective | `retrospective-template` | Sprint team, future sprint organizers | + +## Common Pitfalls + +1. **Skipping perception work and jumping to brainstorming.** Step 1 feels indulgent to action-oriented teams. Without it, the ideation in Step 3 produces ideas the team would have thought of anyway — recycled concepts dressed in new language. +2. **Letting the loudest voice dominate ideation.** Traditional brainstorming rewards extroversion and seniority. Use BrainSwarming and silent generation techniques to ensure the full team contributes, not just the verbally dominant. +3. **Falling in love with an idea before evaluation.** The founder or senior leader who champions a concept before Step 5 biases the entire sprint. Defer commitment until the structured evaluation is complete. +4. **Treating the sprint as a democracy.** Every participant contributes ideas; not every participant selects the winners. The evaluation criteria and final selection require strategic judgement, not majority vote. +5. **Ending the sprint without a clear next step.** An innovation sprint that produces beautiful concept briefs and no execution plan is an intellectual exercise. Each selected concept must exit the sprint with an owner, a timeline, and a first milestone. + +## Adaptation Notes + +- **Idea stage:** The entire company may be a sprint. Focus the problem space on fundamental value proposition and customer segment rather than feature ideation. +- **Validation stage:** Sprint outputs should be testable within 30 days. Shape concepts in Step 4 with explicit validation experiments rather than business cases. +- **Early-traction stage:** Innovation sprints at this stage often focus on adjacent opportunities — new customer segments, new use cases, or new revenue models for an existing product. +- **Growth and scale stages:** The sprint may involve cross-functional teams from product, engineering, design, and business development. Step 2 (creative discipline) becomes more important as larger groups require more structure to be productive. Remote teams should use digital whiteboarding tools with asynchronous contribution windows, maintaining the daily rhythm regardless of time zones. diff --git a/plugins/foreman/content/playbooks/international-expansion-playbook.md b/plugins/foreman/content/playbooks/international-expansion-playbook.md new file mode 100644 index 0000000..ac45732 --- /dev/null +++ b/plugins/foreman/content/playbooks/international-expansion-playbook.md @@ -0,0 +1,150 @@ +--- +name: "international-expansion-playbook" +description: "Provides a systematic approach to expanding into a new country or region -- from macro-environment analysis and competitive assessment through entry strategy, local differentiation, partnership negotiation, and cross-cultural integration. Use when evaluating international markets, preparing for geographic expansion, or planning market entry in unfamiliar territories." +version: "1.0.0" +category: "playbooks" +complexity: "advanced" +stage: + - growth + - scale +trigger_diagnostics: + - market-entry-diagnosis + - competitive-threat-diagnosis +steps: + - skill: "swot-pest-analysis" + purpose: "PEST analysis of the target market -- political, economic, sociocultural, and technological landscape" + output: "Target market PEST assessment with risk ratings, opportunity sizing, and regulatory requirements" + - skill: "porters-five-forces" + purpose: "Map the competitive landscape in the new geography -- local incumbents, substitutes, and barriers" + output: "Five Forces analysis of the target market revealing competitive intensity, buyer power, and entry barriers" + - skill: "scenario-planning" + purpose: "Model three entry scenarios -- direct entry, local partnership, and acquisition -- with resource and timeline implications" + output: "Three entry scenario narratives with financial projections, risk profiles, resource requirements, and trigger points" + - skill: "blue-ocean-strategy" + purpose: "Identify local differentiation opportunity -- what value can you offer that domestic competitors cannot?" + output: "Value curve comparison against local competitors with differentiation strategy and blue ocean opportunities" + - skill: "cooperative-negotiation" + purpose: "Prepare for local partnership negotiations -- distributors, JV partners, or acquisition targets" + output: "Negotiation preparation brief with interests map, BATNA analysis, and deal structure options" + - skill: "organisational-culture" + purpose: "Plan for cross-cultural integration between headquarters culture and local team" + output: "Cultural integration plan addressing communication norms, decision-making styles, and organizational values translation" +final_outputs: + - market-opportunity-summary + - strategic-analysis-one-pager + - partnership-memo + - risk-assessment-brief +estimated_duration: "15-30 hours across 4-8 weeks" +author: "Fatih Guner" +--- + +# International Expansion Playbook + +Walmart lost over a billion dollars in Germany. eBay retreated from Japan. Uber burned through billions before exiting China. Home Depot closed all seven of its stores in China within a few years. These were not scrappy startups making rookie mistakes -- they were among the most sophisticated, well-resourced companies on the planet, and they failed for reasons that systematic analysis would have surfaced before the first dollar was committed. International expansion is the business equivalent of mountaineering: the summit is visible from base camp, the path appears straightforward, and the mountain kills those who mistake visibility for proximity. + +The core error is consistent. Companies that succeed domestically assume their model is portable. It rarely is. Customer behaviour, regulatory environments, competitive dynamics, cultural norms, and distribution channels vary not just between continents but between adjacent countries. The playbook that follows does not eliminate the risk of international expansion -- that risk is inherent and substantial -- but it replaces assumption with analysis and converts ignorance into informed decision-making. + +--- + +## When to Use This Playbook + +- Evaluating a specific international market for potential entry +- The board or investors are pushing for geographic expansion and the founder needs a structured assessment +- Revenue growth in the domestic market is plateauing and international markets represent the logical next frontier +- A competitor has entered an international market first and the company must decide whether to follow +- A partnership or acquisition opportunity in a foreign market has presented itself and requires evaluation +- The company has already entered a market informally (inbound international customers) and must decide whether to invest in formal operations + +## Prerequisites + +- Product-market fit in at least one domestic market (expanding a product that does not work at home will not work abroad) +- Sufficient capital to sustain 12-18 months of international investment before expecting returns +- At least one team member with direct experience in the target region or a committed advisory relationship with someone who has it +- Leadership alignment that international expansion is a strategic priority, not a side project +- Honest assessment of organizational capacity -- international expansion consumes leadership attention disproportionate to its initial revenue contribution + +--- + +## The Sequence + +### Step 1: SWOT-PEST Analysis -- Understand the Terrain + +Begin where experienced strategists begin: with the environment, not the opportunity. A PEST analysis of the target market maps the political landscape (regulatory requirements, government stability, trade policies, corruption indices), economic conditions (GDP growth, currency stability, purchasing power, payment infrastructure), sociocultural factors (consumer behaviour, business customs, language, attitudes toward foreign companies), and technological infrastructure (internet penetration, mobile adoption, logistics networks, data privacy regimes). The PEST analysis reveals whether the market is structurally accessible before asking whether it is strategically attractive. + +Pair the PEST with a SWOT that maps your company's strengths and weaknesses specifically against this market. Domestic strengths may become irrelevant abroad -- a powerful brand in the US carries no weight in Southeast Asia. Conversely, weaknesses at home (small team, lean operations) may become advantages in markets where agility matters more than scale. + +**Checkpoint:** Written PEST assessment with each factor rated by severity and manageability. SWOT completed from the perspective of the target market, not the domestic one. If the PEST reveals regulatory barriers that require 12+ months to navigate, adjust the timeline before proceeding. + +### Step 2: Porter's Five Forces -- Map the Competitive Landscape + +The competitive landscape abroad bears little resemblance to the one at home. Local incumbents have relationships, distribution networks, regulatory knowledge, and cultural fluency that no foreign entrant can replicate quickly. Analyse all five forces with local specificity: who are the established competitors and how entrenched are they? What substitutes exist that may not be direct competitors but serve the same customer need? How much power do local buyers have -- are they price-sensitive, brand-loyal, or relationship-driven? What supplier dynamics exist -- are local suppliers necessary, and will they favour incumbents? What are the real barriers to entry beyond capital -- licensing, local partnerships, talent acquisition, cultural adaptation? + +**Checkpoint:** Five Forces assessment completed with local data, not extrapolated domestic assumptions. Competitive intensity rated. If competitive barriers are structural and high, the direct entry path becomes significantly harder -- weight this in the decision point. + +--- + +### Decision Point: Direct Entry, Local Partner, or Acquisition? + +After Steps 1-3 (include the scenario analysis in Step 3 before deciding), the fundamental strategic choice crystallizes. + +**Direct entry** means building local operations from scratch -- hiring a local team, establishing distribution, navigating regulation independently. This path offers maximum control and margin but requires the most time, capital, and management attention. It works best in markets with low regulatory barriers, available talent, and customer segments similar to the domestic market. + +**Local partnership** means entering through an established local entity -- a distributor, reseller, or joint venture partner. This path trades margin and control for speed and local knowledge. It works best in markets where relationships, regulatory navigation, or distribution networks are critical and difficult to build independently. The risk is partner misalignment: their incentives may diverge from yours as the market develops. + +**Acquisition** means purchasing a local company that already has customers, team, and market knowledge. This path is fastest but most expensive and carries integration risk. It works best when a suitable target exists, the company has acquisition experience, and the time-to-market advantage justifies the premium. + +Each path requires fundamentally different resources, timelines, and organizational capabilities. The wrong choice is expensive to reverse. Let the PEST, Five Forces, and scenario analysis guide the decision rather than defaulting to the path that feels most familiar. + +--- + +### Step 3: Scenario Planning -- Model Three Entry Paths + +Before committing to a single entry strategy, model all three paths as structured scenarios. For each, map the financial investment required (initial and ongoing), the timeline to first revenue and breakeven, the key risks and their mitigation strategies, the organizational resources consumed (especially leadership attention), and the explicit trigger points that would cause you to accelerate, pause, or exit. The adverse scenario for each path deserves particular attention -- international expansion failures rarely result from bad luck; they result from foreseeable risks that were acknowledged but not planned for. + +**Checkpoint:** Three scenario narratives completed with financial projections. Leadership team aligned on the preferred path with documented rationale. Contingency triggers defined for each scenario. + +### Step 4: Blue Ocean Strategy -- Find Local Differentiation + +Entering a foreign market as a replica of what local competitors already offer is a war of attrition that the foreign entrant typically loses. Identify the value dimensions where your product or approach offers something genuinely different -- not different because it is foreign, but different because it solves a problem that local competitors have ignored or serves a segment they have undervalued. Map the value curves of local competitors and identify the factors you can eliminate, reduce, raise, or create. The differentiation must be meaningful to local customers, not merely impressive to the headquarters team. + +**Checkpoint:** Value curve analysis completed against top three local competitors. At least one differentiation opportunity identified that leverages your unique capabilities rather than simply competing on price or brand. + +### Step 5: Cooperative Negotiation -- Prepare for Local Partnerships + +Whether the entry strategy involves a formal joint venture, a distribution partnership, or an acquisition, negotiation with local entities is inevitable. Prepare with the rigour that unfamiliar territory demands. Map the interests of potential partners -- what do they want beyond money? Often, technology transfer, brand association, or access to your domestic market matters more than deal economics. Develop your BATNA (best alternative to negotiated agreement) and theirs. Understand local negotiation customs -- cultures differ dramatically in their approach to directness, timeline, relationship-building before business, and the role of hierarchy in decision-making. A negotiation style that works in New York may alienate in Tokyo and confuse in Sao Paulo. + +**Checkpoint:** Negotiation preparation brief completed for the primary partnership or acquisition target. Interests mapped for both sides. Deal structure options prepared with walk-away criteria defined. + +### Step 6: Organisational Culture -- Plan for Integration + +The most underestimated dimension of international expansion is cultural integration between headquarters and the local team. Every decision about communication norms (synchronous vs. async, direct vs. indirect), decision-making authority (centralized vs. local), performance expectations (metrics vs. relationships), and even work schedules (local holidays, working hours, vacation norms) carries cultural weight. Companies that impose headquarters culture on local teams breed resentment and lose their best local talent. Companies that grant full cultural autonomy to local teams lose coherence and brand consistency. The integration plan must thread this needle explicitly. + +**Checkpoint:** Cultural integration plan documented addressing communication protocols, decision authority, reporting structures, and the specific cultural dimensions most likely to create friction between headquarters and local teams. + +--- + +## Final Deliverable + +Upon completing all six steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Market Opportunity Summary | `market-opportunity-summary` | Board, investors | +| Strategic Analysis One-Pager | `strategic-analysis-one-pager` | Board, leadership team | +| Partnership or Acquisition Memo | `partnership-memo` | Leadership team, legal | +| Risk Assessment Brief | `risk-assessment-brief` | Board, investors, leadership | + +## Common Pitfalls + +- **Assuming the domestic model is portable.** The product, pricing, positioning, and distribution that work at home are hypotheses abroad, not facts. Test them as hypotheses. +- **Underestimating the time and attention cost.** International expansion consumes founder and leadership attention far beyond its initial revenue contribution. If the domestic business cannot run without constant founder involvement, expansion is premature. +- **Choosing the entry path based on comfort rather than analysis.** Direct entry feels like control. Partnerships feel like compromise. Acquisition feels decisive. None of these feelings constitute strategic reasoning. +- **Neglecting local talent.** Hiring expatriates to run local operations signals to the market that you do not trust local talent. Hire locally, develop locally, and promote locally -- then provide headquarters support, not headquarters control. +- **Moving too slowly after committing.** The analysis phase should be thorough. The execution phase should be decisive. Companies that commit to international expansion and then move tentatively get the costs without the benefits. + +## Adaptation Notes + +- **Growth-stage companies** entering their first international market should prioritize Steps 1-3 and consider the partnership path seriously. Direct entry by a growth-stage company into an unfamiliar market is high-risk; a local partner provides the market intelligence and relationships that would otherwise take years to build. +- **Scale-stage companies** with international experience can compress Steps 1-2 and focus on Steps 4-6. The analytical frameworks are familiar; the differentiation and integration challenges are where experienced international operators still stumble. +- **B2B companies** should pay particular attention to Step 5 -- enterprise sales in foreign markets are almost always relationship-mediated, and the local partner's network may matter more than the product's features for the first 18 months. +- **Regulated industries** (fintech, healthtech, edtech) should expect Step 1 to consume disproportionate time and may require legal counsel specializing in the target market's regulatory environment before the remaining steps are meaningful. diff --git a/plugins/foreman/content/playbooks/launch-playbook.md b/plugins/foreman/content/playbooks/launch-playbook.md new file mode 100644 index 0000000..2aa9f25 --- /dev/null +++ b/plugins/foreman/content/playbooks/launch-playbook.md @@ -0,0 +1,137 @@ +--- +name: "launch-playbook" +description: "Used when a founder is launching a new product or entering a new market. Chains competitive analysis, differentiation strategy, go-to-market design, narrative construction, launch communications, and success criteria into a sequenced market entry engagement." +trigger_diagnostics: + - market-entry-diagnosis +steps: + - skill: "porters-five-forces" + purpose: "Understand the competitive structure of the market being entered" + output: "Five forces analysis with entry barrier assessment and power dynamics" + - skill: "blue-ocean-strategy" + purpose: "Identify differentiation opportunities that avoid head-to-head competition" + output: "Strategy canvas with value curve comparison and blue ocean opportunity map" + - skill: "four-ps-marketing" + purpose: "Design the go-to-market mix with tactical specificity" + output: "Product, Price, Place, Promotion plan with channel priorities and budget allocation" + - skill: "building-story-stakes" + purpose: "Craft a launch narrative with tension and urgency that earns attention" + output: "Launch story with stakes, conflict, and resolution structure" + - skill: "writing-for-response" + purpose: "Create launch communications engineered to drive specific reader actions" + output: "Launch messaging with calls to action, friction reduction, and response triggers" + - skill: "smart-goals" + purpose: "Set measurable launch success criteria with time-bound milestones" + output: "SMART goals matrix with 30/60/90-day targets and tracking metrics" +final_outputs: + - market-opportunity-summary + - action-plan + - new-initiative-brief +estimated_duration: "6-10 hours across 1-3 weeks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth +author: "Fatih Guner" +--- + +# The Launch Playbook + +## When to Use This Playbook + +A product is ready to meet its market -- or a proven product is entering a new one. The technology works. The team is assembled. What remains is the strategic question most founders answer with intuition rather than analysis: how exactly do we enter, and what does success look like? + +Launches fail for predictable reasons. The founder overestimates market readiness, underestimates competitive response, prices without data, distributes without strategy, and communicates without compelling the audience to act. This playbook addresses each failure mode in sequence before the launch window opens. + +## Prerequisites + +- A product or service that is functionally ready (MVP minimum) +- Basic market research: target customer profile, market size estimate, known competitors +- A defined launch timeline with hard constraints (funding milestones, seasonal windows, partnership deadlines) +- Budget parameters for go-to-market spend +- At least one person accountable for launch execution + +## The Sequence + +### Step 1: Porter's Five Forces +- **Purpose:** Before entering a market, understand its structure. The forces that govern profitability -- buyer power, supplier power, rivalry intensity, substitution threat, and entry barriers -- determine whether the market is worth entering at all and where the points of leverage exist. +- **Key questions:** Who holds the power in this market? What barriers will slow your entry? How intense is existing rivalry? What substitutes compete for the same budget? +- **Input:** Market research, competitor data, customer interviews, industry reports +- **Output:** Five forces analysis with a clear assessment of market attractiveness and entry strategy implications +- **Time:** 1-2 hours +- **Checkpoint:** If all five forces are unfavorable -- high rivalry, powerful buyers, low barriers inviting more entrants, strong substitutes, and concentrated suppliers -- reconsider the entry or narrow the beachhead dramatically. + +### Step 2: Blue Ocean Strategy +- **Purpose:** Competing on the same dimensions as incumbents is expensive and usually fatal for startups. The strategy canvas reveals which factors the industry competes on and where the opportunity exists to diverge -- to eliminate, reduce, raise, or create factors that define a new value curve. +- **Key questions:** On which factors does the industry over-deliver relative to what customers actually value? Where is the market under-serving customers? What can you eliminate entirely to fund investment elsewhere? +- **Input:** Five forces output from Step 1, customer feedback, competitor feature matrices +- **Output:** Strategy canvas with existing industry curve and your proposed divergent curve, plus an Eliminate-Reduce-Raise-Create grid +- **Time:** 1-2 hours +- **Checkpoint:** The proposed value curve must diverge visibly from the industry standard on at least two dimensions. If it tracks the industry curve closely, you are entering a red ocean with a different logo. + +## Decision Point + +After completing Steps 1 and 2, assess the strategic landscape: + +**Is there a genuine blue ocean, or are you entering a red ocean?** + +- **Blue ocean identified:** Proceed with confidence. The differentiation is real, defensible, and valued by customers. Steps 3-6 will translate this advantage into execution. +- **Red ocean confirmed:** Do not abandon the launch, but adjust expectations and strategy. A red ocean entry requires superior execution, not superior strategy. Tighten the beachhead, reduce the initial scope, increase the marketing budget, and compress the timeline to profitability. Consider whether a niche within the red ocean offers blue ocean characteristics. + +Entering a red ocean knowingly is not failure. Entering one unknowingly is. + +### Step 3: Four Ps Marketing +- **Purpose:** Translate strategic positioning into tactical go-to-market decisions. Product-market fit is necessary but insufficient -- the product must also be priced correctly, distributed through the right channels, and promoted to the right audience with the right message. +- **Key questions:** Does the pricing reflect the value curve from Step 2? Which channels reach the beachhead customers most efficiently? What is the promotion strategy for the first 90 days? Where does the budget concentrate? +- **Input:** Blue ocean output, customer segments, channel cost data, competitive pricing +- **Output:** Four Ps plan with channel priorities, pricing rationale, and 90-day promotional calendar +- **Time:** 1-2 hours +- **Checkpoint:** The Four Ps must be internally consistent. Premium pricing with bottom-tier distribution channels signals confusion. A high-touch product sold through self-serve channels signals mismatch. Each P must reinforce the others. + +### Step 4: Building Story Stakes +- **Purpose:** A launch without narrative tension is a press release. Stakes create urgency -- the reason this product matters now, the cost of the status quo, the risk of inaction. This step constructs the emotional architecture of the launch story. +- **Key questions:** What is at stake for the customer if they do nothing? What tension does the product resolve? What is the "before and after" transformation? +- **Input:** Value curve from Step 2, customer pain points, market timing factors +- **Output:** Launch narrative with defined stakes, a clear antagonist (the status quo or incumbent approach), and a resolution arc +- **Time:** 0.5-1 hour +- **Checkpoint:** The stakes must be real and felt by the customer, not invented by marketing. If the stakes require extensive explanation, they are not stakes -- they are features. + +### Step 5: Writing for Response +- **Purpose:** Launch communications exist to produce action: signups, purchases, demo requests, press coverage. Every word must reduce friction between the reader and the desired response. This step applies behavioral writing principles to all launch materials. +- **Key questions:** What is the single desired action for each piece of communication? What friction stands between the reader and that action? How do you make the default action the desired action? +- **Input:** Story stakes from Step 4, Four Ps promotional plan, audience segmentation +- **Output:** Launch communication templates (landing page copy, launch email, social media posts, press pitch) with embedded response triggers and friction reduction +- **Time:** 1-2 hours +- **Checkpoint:** Each communication must pass the "so what" test. Read the first sentence. If a busy person would not continue reading, rewrite the opening. + +### Step 6: SMART Goals +- **Purpose:** A launch without defined success criteria becomes an indefinite campaign that slowly loses energy and budget. SMART goals create the accountability structure: specific targets, measurable indicators, achievable but ambitious thresholds, relevant metrics, and time-bound checkpoints. +- **Key questions:** What does success look like at 30, 60, and 90 days? Which metric is the primary indicator? What triggers a strategy revision? What constitutes failure? +- **Input:** Four Ps plan, financial model, competitive benchmarks, runway constraints +- **Output:** SMART goals matrix with 30/60/90-day targets, leading and lagging indicators, and defined revision triggers +- **Time:** 0.5-1 hour +- **Checkpoint:** Goals must be falsifiable. "Grow awareness" is not a goal. "Reach 500 signups with a 15% activation rate within 30 days at under $40 CAC" is a goal. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `market-opportunity-summary` | Investors, board | Market analysis with competitive positioning and opportunity sizing | +| `action-plan` | Team | Launch execution plan with owners, timelines, dependencies, and milestones | +| `new-initiative-brief` | Team, stakeholders | One-page launch brief with strategy, differentiation, and success criteria | + +## Common Pitfalls + +1. **Launching broadly instead of narrowly.** The most common launch failure is targeting a market rather than a segment. A beachhead of 1,000 passionate customers beats 100,000 indifferent ones. Define the beachhead before spending a dollar on promotion. +2. **Skipping the competitive analysis.** Founders often believe their product is unique enough to ignore competitors. The five forces analysis almost always reveals competitive pressure the founder underestimated -- better to discover it before launch than after. +3. **Pricing by gut.** Pricing is a strategic decision that signals positioning, determines unit economics, and constrains distribution. The Four Ps analysis must produce a pricing rationale rooted in customer willingness-to-pay and competitive context, not founder intuition. +4. **Measuring everything, tracking nothing.** Dozens of metrics create the illusion of rigor. The SMART goals step should produce 3-5 metrics that genuinely indicate whether the launch is working. Everything else is noise. +5. **Writing communications that describe rather than compel.** Feature lists are not launch copy. The writing-for-response step exists because most launch materials tell the reader what the product does rather than making the reader want to act. + +## Adaptation Notes + +- **Idea stage:** The "launch" may be an MVP or landing page test. Compress the playbook: skip Step 4 (stakes) and focus on Steps 1-3 (market understanding) and Step 6 (success criteria). The goal is learning, not revenue. +- **Validation stage:** The launch tests product-market fit in a defined segment. All six steps apply, but the SMART goals should emphasize activation and retention over revenue. +- **Early-traction stage:** The launch extends into adjacent segments or geographies. Step 1 (five forces) must be re-run for the new market. The blue ocean analysis from Step 2 may reveal that differentiation that worked in the first market does not transfer. +- **Growth stage:** Launches at scale carry brand risk. Step 4 (stakes) and Step 5 (communications) receive disproportionate weight. The narrative must be consistent with established brand positioning while introducing something genuinely new. diff --git a/plugins/foreman/content/playbooks/negotiation-playbook.md b/plugins/foreman/content/playbooks/negotiation-playbook.md new file mode 100644 index 0000000..50459fe --- /dev/null +++ b/plugins/foreman/content/playbooks/negotiation-playbook.md @@ -0,0 +1,143 @@ +--- +name: "negotiation-playbook" +description: "Prepares founders for high-stakes negotiations -- fundraising term sheets, acquisition offers, key partnerships, and enterprise deals. Combines psychological preparation, strategic analysis, and tactical execution into a structured pre-negotiation process. Use when approaching any negotiation where the outcome materially affects the company's trajectory." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +trigger_diagnostics: + - negotiation-stuck-diagnosis +steps: + - skill: "negotiation-mindset-and-self" + purpose: "Prepare mentally, identify personal defaults and biases that surface under negotiation pressure" + output: "Self-assessment of negotiation tendencies with specific strategies to counteract weaknesses" + - skill: "game-theory-fundamentals" + purpose: "Understand the strategic structure of the negotiation -- payoffs, incentives, and equilibria" + output: "Game-theoretic map of the negotiation showing each party's incentives and optimal strategies" + - skill: "information-asymmetry" + purpose: "Map what each side knows and does not know, and identify where information gaps create leverage or vulnerability" + output: "Information map with known unknowns, strategies for disclosure, and intelligence-gathering priorities" + - skill: "cooperative-negotiation" + purpose: "Design the value-creation phase -- expanding the pie before dividing it" + output: "Value-creation options with mutual gains identified and prioritized by feasibility" + - skill: "competitive-negotiation" + purpose: "Prepare for the value-claiming phase -- protecting your position when interests diverge" + output: "Competitive tactics playbook with BATNA analysis, reservation points, and concession strategy" + - skill: "delivering-the-deal" + purpose: "Plan for obstacles, last-minute complications, and the mechanics of closing" + output: "Deal delivery plan with obstacle anticipation, closing sequence, and satisfaction criteria" +final_outputs: + - negotiation-prep-sheet + - decision-journal + - stakeholder-map +estimated_duration: "3-5 hours" +author: "Fatih Guner" +--- + +# Negotiation Playbook + +Most founders enter their most consequential negotiations having prepared the spreadsheet but not themselves. They know their numbers cold and their strategy not at all. The term sheet negotiation that determines ownership dilution, the partnership deal that shapes distribution for three years, the acquisition conversation that could end or transform the company -- these moments compress years of value creation into hours of value division. Preparation is not optional, and preparation means more than rehearsing your ask. It means understanding the game, the other player, the information landscape, and your own psychological wiring under pressure. + +--- + +## When to Use This Playbook + +- Fundraising: negotiating term sheets, SAFEs, or convertible notes with investors +- Acquisition: receiving or making an offer to buy or merge +- Partnerships: structuring a deal with a distribution, technology, or strategic partner +- Enterprise sales: negotiating a contract that represents a significant portion of revenue +- Any negotiation where the outcome materially changes the company's trajectory or the founder's equity position +- Situations where the founder feels outmatched by a more experienced counterparty + +## Prerequisites + +- A specific, identified negotiation with a known counterparty (this is a preparation playbook, not a general education) +- Basic understanding of the subject matter (term sheet mechanics, deal structure, contract terms) +- Honest willingness to examine personal negotiation weaknesses +- Sufficient time before the negotiation to complete preparation -- rushing this playbook defeats its purpose + +--- + +## The Sequence + +### Step 1: Negotiation Mindset and Self -- Know Your Defaults + +Before analyzing the other side, analyze yourself. Every negotiator carries default tendencies: some capitulate too quickly to preserve relationships; others become adversarial and destroy value trying to "win." Identify where you fall on the cooperative-competitive spectrum, how you respond to pressure, what triggers emotional reactions, and where your ego is most vulnerable. The founder who understands their own patterns can interrupt them. The one who does not will discover them at the worst possible moment. + +**Checkpoint:** Written self-assessment completed. At least two personal default tendencies identified with specific countermeasures planned. + +### Step 2: Game Theory Fundamentals -- Map the Strategic Structure + +Every negotiation has a structure that exists independently of the personalities involved. Map it: What does each party want? What are the payoffs for each possible outcome? Is this a zero-sum division or does value-creation potential exist? Are there multiple rounds or is this a single interaction? Understanding the game structure prevents you from treating a cooperative opportunity as adversarial, or vice versa. It also reveals whether the counterparty's stated position is strategically rational or a bluff. + +**Checkpoint:** Game structure documented. Payoff matrix or decision tree created showing each party's incentives and likely strategies. + +### Step 3: Information Asymmetry -- Map the Knowledge Landscape + +In nearly every negotiation, one party knows something the other does not. Investors know the state of the funding market; founders know the true state of the product pipeline. Map the information landscape explicitly: what do you know that they do not? What do they know that you do not? What do neither of you know? This analysis determines your disclosure strategy (what to reveal and when), your intelligence-gathering priorities (what to learn before or during the negotiation), and where the counterparty's leverage is real versus manufactured. + +**Checkpoint:** Information asymmetry map completed. Disclosure strategy drafted. Key questions for the negotiation identified. + +--- + +### Decision Point: One-Shot or Ongoing Relationship? + +The balance between value creation and value claiming depends fundamentally on this question. + +**If this is a one-shot negotiation** (unlikely to interact with this counterparty again, or the relationship's value is captured entirely in this deal): Weight Step 5 (competitive negotiation) more heavily. Claiming your fair share matters more than leaving the counterparty delighted. This does not mean being adversarial -- it means being precise about your interests and firm about your reservation points. + +**If this is a long-term relationship** (an investor who will sit on your board, a partner you will work with for years, a customer you need to renew): Weight Step 4 (cooperative negotiation) more heavily. The surplus generated by creative value-creation will compound over the relationship's duration and far outweigh marginal gains from aggressive claiming. Reputation effects matter enormously -- the negotiation community in any industry is smaller than founders assume. + +Most founder negotiations are long-term relationships. Act accordingly. + +--- + +### Step 4: Cooperative Negotiation -- Create Value Before Claiming It + +Identify the interests behind each party's stated positions. Positions are what people say they want; interests are why they want it. An investor demanding a board seat may be seeking information access, not governance control. A partner demanding exclusivity may be seeking commitment assurance, not market restriction. Once interests are exposed, creative options emerge that satisfy both parties better than either's original position. Design at least three value-creating proposals that expand the total value available. + +**Checkpoint:** Interest analysis completed for both sides. At least three integrative options developed and ranked by mutual benefit. + +### Step 5: Competitive Negotiation -- Protect Your Position + +Value creation has limits. At some point, the pie must be divided, and this phase requires different skills. Define your BATNA (best alternative to negotiated agreement) with ruthless honesty -- not what you hope your alternative is, but what it actually is. Set your reservation point (the worst deal you will accept). Plan your concession strategy: which issues will you concede, in what order, and what will you expect in return? Prepare for common competitive tactics the counterparty may employ: anchoring, artificial deadlines, good cop/bad cop, and silence as pressure. + +**Checkpoint:** BATNA clearly defined. Reservation point set. Concession strategy documented with trade-offs mapped. + +### Step 6: Delivering the Deal -- Plan for the Close + +Negotiations fail in the final stretch more often than founders expect. Last-minute deal fatigue, new stakeholders appearing, legal review inserting unexpected terms, buyer's remorse on either side -- anticipate all of it. Plan the closing sequence: who signs what, in what order, with what contingencies? Define what "satisfaction" looks like for both parties beyond the contract terms. A deal that leaves the counterparty resentful is a deal that creates problems in execution. + +**Checkpoint:** Closing plan documented. Obstacle scenarios identified with contingency responses. Post-signature relationship management planned. + +--- + +## Final Deliverable + +Upon completing all six steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Negotiation Preparation Sheet | `negotiation-prep-sheet` | Founder, negotiation team | +| Decision Journal | `decision-journal` | Founder (for post-negotiation review) | +| Stakeholder Map | `stakeholder-map` | Founder, advisors | + +## Common Pitfalls + +- **Preparing the numbers but not the psychology.** Founders who know their valuation model but not their emotional triggers get outmaneuvered by experienced negotiators. +- **Falling in love with the deal.** The moment you need this specific deal to close, your BATNA effectively becomes zero and the counterparty owns the negotiation. Maintain genuine alternatives. +- **Treating all negotiations as zero-sum.** Most founder negotiations involve long-term relationships where value creation dominates value claiming. Winning the battle and losing the relationship is a net negative. +- **Negotiating against yourself.** Making concessions before the counterparty asks for them is a surprisingly common founder behavior, driven by anxiety about the relationship. Wait for the ask. +- **Ignoring the decision journal.** The preparation sheet is useful before the negotiation. The decision journal -- recording what happened, what worked, what you would change -- is what makes you better at the next one. + +## Adaptation Notes + +- **First-time fundraisers** should invest extra time in Step 3 (information asymmetry). The knowledge gap between a seasoned VC and a first-time founder is substantial, and investors are not obligated to close it. +- **Acquisition negotiations** require particular attention to Step 6 (delivering the deal). Acquisition processes involve more stakeholders, longer timelines, and more failure points than any other negotiation type founders typically encounter. +- **Technical founders** negotiating with business-oriented counterparties should be aware that different communication styles can create false impressions of agreement or disagreement. Step 1's self-assessment should include communication style analysis. +- **Solo founders** without a negotiation team should consider engaging an advisor or mentor for Steps 4 and 5 specifically -- having a second perspective on value-creation options and competitive tactics is disproportionately valuable when negotiating alone. diff --git a/plugins/foreman/content/playbooks/partnership-playbook.md b/plugins/foreman/content/playbooks/partnership-playbook.md new file mode 100644 index 0000000..a9c4f4f --- /dev/null +++ b/plugins/foreman/content/playbooks/partnership-playbook.md @@ -0,0 +1,133 @@ +--- +name: "partnership-playbook" +description: "Structures the evaluation, negotiation, and design of strategic partnerships, alliances, and joint ventures. Chains game-theoretic analysis, competitive impact assessment, cooperative negotiation design, trust building, and deal execution into a rigorous sequence. Use when a partnership opportunity has emerged and the founder must decide whether to pursue it, how to negotiate it, and how to structure it for mutual value creation." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +trigger_diagnostics: + - partnership-diagnosis +steps: + - skill: "coalition-and-partnership-games" + purpose: "Apply game theory to understand the strategic logic of the alliance — who benefits, who pays, and what incentives govern each party's behaviour" + output: "Partnership game analysis covering payoff structures, Nash equilibria, and defection risks" + - skill: "porters-five-forces" + purpose: "Assess how the partnership reshapes competitive dynamics — for better and for worse" + output: "Competitive impact assessment showing how the alliance alters supplier power, buyer power, rivalry, and barriers to entry" + - skill: "cooperative-negotiation" + purpose: "Design the value-creation framework that makes the partnership worth more than its parts" + output: "Negotiation architecture with interests mapped, value-creation opportunities identified, and trade space defined" + - skill: "trust-equation" + purpose: "Build the relational foundation without which no contract can sustain a partnership" + output: "Trust assessment of the prospective partner covering credibility, reliability, intimacy, and self-orientation" + - skill: "delivering-the-deal" + purpose: "Close and structure the agreement with terms that protect both parties and anticipate failure modes" + output: "Deal term sheet with governance structure, exit provisions, performance milestones, and dispute resolution mechanisms" +final_outputs: + - partnership-memo + - negotiation-prep-sheet + - stakeholder-map +estimated_duration: "4-8 hours across 1-2 weeks" +author: "Fatih Guner" +--- + +# Partnership Playbook + +Partnerships destroy more value than they create. That is not cynicism — it is the base rate. The graveyard of strategic alliances is vast: well-intentioned collaborations that consumed management attention, created dependencies without delivering leverage, and ended in acrimony or quiet dissolution. The partnerships that succeed share a common trait: both parties understood the game they were playing before they sat down at the table. This playbook exists to ensure that understanding. + +--- + +## When to Use This Playbook + +- A potential partner has approached with an alliance proposal, and the founder must evaluate it rigorously +- The company is considering initiating a strategic partnership to access a capability, market, or distribution channel +- An existing partnership is underperforming and needs restructuring before it consumes more value than it creates +- A joint venture or co-development agreement is on the table, with significant resource commitments from both sides +- The founder senses an imbalance in the partnership dynamic but cannot articulate precisely where the asymmetry lies + +## Prerequisites + +- Clarity on what the company needs from a partnership (capability, distribution, credibility, capital) +- Basic financial data to assess the partnership's economic value — not just the strategic narrative +- Willingness to walk away if the analysis reveals the partnership destroys more value than it creates +- At least a preliminary understanding of the prospective partner's incentives and constraints + +--- + +## The Sequence + +### Step 1: Coalition and Partnership Games — Understand the Game Theory + +Before any negotiation begins, understand the game you are playing. Map the payoff structures for both parties under cooperation and defection. Identify whether this is a repeated game (ongoing relationship with future interactions) or a one-shot game (single transaction), because the strategic calculus differs fundamentally. Assess the Shapley Value — what each party uniquely contributes that the other cannot replicate independently. + +**Checkpoint:** The game analysis reveals whether value creation is genuinely mutual or whether one party captures disproportionate value. If the latter, the negotiation strategy in Step 3 must account for this asymmetry. + +--- + +### Decision Point: Need or Want? + +This distinction reshapes everything that follows. + +**Need partnership:** The company requires something it cannot build, buy, or replicate within the relevant timeframe. A distribution channel into an inaccessible market. A regulatory licence held by the partner. A technology capability that would take two years to develop internally. Need implies a weaker negotiating position because the alternative to agreement (BATNA) is poor. + +- **If need:** Accept the asymmetry honestly. Steps 3 and 5 become critical — the negotiation must extract maximum value within the constraints, and the deal structure must include protections against exploitation of the dependency. Invest more time in Step 4 (trust) because dependence without trust is vulnerability. + +**Want partnership:** The company would benefit from the partnership but has viable alternatives — including doing nothing or building the capability internally. Want implies a stronger negotiating position and more leverage to design terms that reflect genuine mutual value. + +- **If want:** The negotiation has more room for creativity. Steps 2 and 3 can focus on designing novel value-creation structures rather than protecting against downside risk. The deal in Step 5 can be more ambitious because walking away remains a credible option. + +Document the honest assessment. Founders who tell themselves they "want" a partnership they actually "need" negotiate from a fantasy position and sign disadvantageous terms. + +--- + +### Step 2: Porter's Five Forces — Assess Competitive Impact + +A partnership does not exist in a vacuum — it restructures the competitive landscape. Map how the alliance changes each of the five forces. Does it increase buyer power by creating a larger combined entity? Does it reduce rivalry by aligning with a competitor? Does it raise barriers to entry for others or lower them for the partner? The forces analysis reveals second-order effects that the partnership's proponents often ignore in their enthusiasm. + +**Checkpoint:** The analysis identifies at least one competitive risk created by the partnership — not just the benefits. Every alliance that strengthens one force weakens the company's independent position in another. + +### Step 3: Cooperative Negotiation — Design the Value-Creation Framework + +Move from positions to interests. Map what each party actually needs (not what they initially demand), identify the trade space where creative solutions exist, and design a negotiation architecture that expands the pie before dividing it. The cooperative framework does not mean being soft — it means being intelligent about where value can be created that neither party could access alone. + +**Checkpoint:** The value-creation framework identifies at least two opportunities beyond the obvious transaction. If the partnership offers only a single axis of value, it is fragile. + +### Step 4: Trust Equation — Build the Relationship Foundation + +Contracts govern behaviour at the margin. Trust governs behaviour in the spaces between clauses. Assess the prospective partner across the four dimensions of the trust equation: credibility (do they have the expertise they claim?), reliability (do they follow through consistently?), intimacy (is candid communication possible?), and self-orientation (are they primarily serving their own interests?). Low trust in any dimension is not a deal-breaker — but it must be addressed in the deal structure. + +**Checkpoint:** The trust assessment produces a specific action plan for building trust in the weakest dimension before the deal closes. If self-orientation scores high and the other three score low, reconsider the partnership entirely. + +### Step 5: Delivering the Deal — Close and Structure + +Structure the agreement with terms that anticipate success and failure. Define governance (who decides what), economics (how value and costs are shared), performance milestones (how progress is measured), exit provisions (how the partnership ends gracefully), and dispute resolution (how disagreements are handled before they become lawsuits). The deal structure should make it easy to succeed together and possible to separate without destruction. + +**Checkpoint:** The term sheet passes the "adversarial board member" test. A sceptical advisor reviewing the terms should find them defensible, balanced, and clear. + +--- + +## Final Deliverable + +| Output | Template | Audience | +|--------|----------|----------| +| Partnership Memo | `partnership-memo` | Board, investors, leadership team | +| Negotiation Prep Sheet | `negotiation-prep-sheet` | Founder, negotiation team (internal) | +| Stakeholder Map | `stakeholder-map` | Founder, project lead | + +## Common Pitfalls + +1. **Partnering for credibility rather than capability.** Announcing a partnership with a recognizable name creates a press release, not a strategic advantage. If the partnership does not change the company's competitive position or operational capability, it is marketing — not strategy. +2. **Ignoring the game theory.** Founders who skip Step 1 discover the incentive misalignment after signing. Understanding the payoff structures before negotiating is not academic — it is the difference between a partnership that lasts and one that collapses at the first stress test. +3. **Underweighting exit provisions.** Every partnership ends. The question is whether it ends by mutual agreement with clear terms or by slow deterioration and legal dispute. Design the exit before you need it. +4. **Assuming alignment is permanent.** The partner's strategy will evolve. Their leadership will change. Their priorities will shift. Build review mechanisms into the agreement that allow both parties to renegotiate as circumstances change. +5. **Negotiating the deal before understanding the game.** Founders who jump directly to term sheets without completing Steps 1-3 optimize for closing speed at the expense of deal quality. + +## Adaptation Notes + +- **Early-traction stage:** Partnerships at this stage often involve trading equity or exclusivity for access. Be especially rigorous about the game theory — small companies frequently give up more than they receive because the partner's brand feels validating. +- **Growth stage:** The company has more leverage and more to lose. Competitive impact analysis (Step 2) becomes critical because partnerships at scale can inadvertently create competitors or surrender strategic optionality. +- **Scale stage:** Partnerships here resemble corporate development. The trust equation matters less (institutional relationships replace personal ones) and deal structure matters more. Invest disproportionately in governance design and exit provisions. +- **Cross-border partnerships** add regulatory complexity, cultural distance, and enforcement risk. Extend the timeline and involve legal counsel earlier than you think necessary. diff --git a/plugins/foreman/content/playbooks/personal-brand-playbook.md b/plugins/foreman/content/playbooks/personal-brand-playbook.md new file mode 100644 index 0000000..7f95d2c --- /dev/null +++ b/plugins/foreman/content/playbooks/personal-brand-playbook.md @@ -0,0 +1,146 @@ +--- +name: "personal-brand-playbook" +description: "Guides founders and leaders through building authentic personal brands -- thought leadership, visibility, and credibility -- by mining their genuine expertise and journey for compelling narratives, then adapting those stories for different platforms and audiences. Use when seeking investor visibility, market authority, speaking opportunities, or a consistent public presence." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +trigger_diagnostics: + - fundraising-diagnosis + - communication-breakdown-diagnosis +steps: + - skill: "leader-self-reflection" + purpose: "Identify your authentic expertise, perspective, and the themes that will anchor your brand" + output: "Personal brand foundation: core expertise areas, distinctive perspective, values alignment, and audience resonance map" + - skill: "what-is-a-story" + purpose: "Understand what makes content story-worthy versus forgettable -- the mechanics of narrative that earns attention" + output: "Story criteria checklist distinguishing compelling narratives from generic content" + - skill: "finding-your-stories" + purpose: "Mine your founder journey for the specific moments, failures, and insights that become your brand currency" + output: "Story inventory with 10-15 core narratives categorized by theme, audience, and platform suitability" + - skill: "story-performance-and-delivery" + purpose: "Adapt your stories for different platforms -- LinkedIn posts, podcast appearances, conference stages, investor meetings" + output: "Platform adaptation guide with format, length, tone, and structural adjustments per channel" + - skill: "writing-with-purpose" + purpose: "Craft written content with clear audience, goal, and call to action rather than publishing into the void" + output: "Content strategy framework with audience segments, content pillars, publishing cadence, and success metrics" + - skill: "leadership-voice-and-presence" + purpose: "Develop a consistent and recognizable voice that persists across platforms and contexts" + output: "Voice guide defining tone, vocabulary, recurring themes, and stylistic boundaries" +final_outputs: + - career-strategy-canvas + - action-plan + - case-study-template +estimated_duration: "4-8 hours initial, then ongoing weekly practice" +author: "Fatih Guner" +--- + +# Personal Brand Playbook + +Nobody remembers the founder who had a great product and said nothing. The technology industry is populated with superior products that lost to inferior ones marketed by founders who understood that in a crowded market, the person behind the company is often the company's most effective distribution channel. This is not vanity. It is strategy. Investors fund people before products. Customers trust faces before logos. Talent joins missions articulated by humans, not mission statements crafted by committees. + +The uncomfortable truth about personal branding is that most founders approach it backwards. They start with tactics -- posting on LinkedIn, pitching podcast hosts, hiring a ghostwriter -- before answering the foundational question: what do you actually have to say that the world cannot hear elsewhere? + +--- + +## When to Use This Playbook + +- Preparing for a fundraise and needing investor visibility before the pitch +- Entering a competitive market where founder credibility differentiates the company +- Seeking speaking engagements, media appearances, or advisory positions +- Building market awareness without a large marketing budget +- Transitioning from operator to thought leader as the company scales +- Recognizing that competitors with weaker products are winning the narrative war + +## Prerequisites + +- Willingness to be publicly visible and to share genuine perspectives rather than corporate platitudes +- At least 6-12 months of founder experience (the stories need to exist before they can be told) +- Clarity on who the brand serves -- investors, customers, potential hires, or a combination +- Acceptance that personal branding is a long-term investment with a 6-12 month compounding horizon, not a quick win + +--- + +## The Sequence + +### Step 1: Leader Self-Reflection -- Find Your Authentic Foundation + +A personal brand built on borrowed authority collapses at the first challenge. Begin with rigorous self-examination: what do you know deeply enough to teach? What experiences have you survived that others are currently navigating? Where does your perspective genuinely diverge from consensus? The goal is not to invent a persona but to excavate one -- the authentic expertise and viewpoint that already exists but has not been articulated with precision. Map the intersection of your knowledge, your experience, and the market's unmet need for that specific perspective. + +**Checkpoint:** Written brand foundation document identifying three to five core themes, the target audience for each, and the specific authority you bring. If the themes could belong to any founder in your sector, they are too generic -- dig deeper. + +--- + +### Decision Point: Expertise or Journey? + +This shapes everything that follows. + +**Expertise-driven brands** position the founder as a domain authority -- the person who understands the industry, technology, or market better than anyone. Content is analytical, insight-heavy, and forward-looking. The voice is that of the expert who sees patterns others miss. This path works best when the founder has deep technical or domain knowledge and the audience values education. + +**Journey-driven brands** position the founder as a narrator of the entrepreneurial experience -- the person who shares the real story of building a company with its failures, surprises, and hard-won lessons. Content is narrative, vulnerable, and relatable. The voice is that of the practitioner who shares the view from the trenches. This path works best when the founder's story is genuinely unusual or when the audience values authenticity over authority. + +Most strong brands blend both, but one should dominate. The choice affects content format (essays vs. stories), platform priority (LinkedIn vs. podcasts), and the balance between teaching and sharing. Decide before proceeding, and let the decision inform every subsequent step. + +--- + +### Step 2: What Is a Story -- Learn the Mechanics of Attention + +Content that earns attention operates differently from content that merely exists. Before creating anything, understand the structural elements that separate a story worth sharing from a post worth scrolling past. A story requires transformation -- something changed. It requires stakes -- something was at risk. It requires specificity -- the details that make it yours rather than anyone's. Generic advice ("here are five tips for founders") occupies the most crowded and least memorable category of content. Stories with specific characters, real decisions, and actual consequences occupy the scarcest and most valued category. + +**Checkpoint:** Story criteria framework internalized. Ability to evaluate whether a content idea meets the threshold for story-worthiness before investing time in creating it. + +### Step 3: Finding Your Stories -- Mine the Journey + +Every founder sits on a reservoir of stories they have never told because the experiences felt too ordinary, too painful, or too specific to be interesting. They are wrong on all three counts. The hiring mistake that cost six months. The customer conversation that changed the product direction. The board meeting where the numbers were bad and the founder had to say so. These moments are your brand's raw material. Systematically inventory your founder journey using structured recall techniques: first-last-best-worst exercises, milestone mapping, failure cataloguing, and decision-point reconstruction. + +**Checkpoint:** Story inventory of 10-15 narratives, each tagged by theme, emotional register, and the audience most likely to resonate with it. At least three stories should feel uncomfortable to tell -- those are usually the strongest. + +### Step 4: Story Performance and Delivery -- Adapt for Platform + +A story that devastates a podcast audience may die as a LinkedIn post. The medium shapes the message in ways that founders chronically underestimate. This step adapts your core narratives for the specific constraints and opportunities of each platform. LinkedIn rewards concise, scroll-stopping openings and practical takeaways. Podcasts reward conversational depth and emotional texture. Conference stages reward structure, pacing, and rehearsed spontaneity. Investor meetings reward narrative economy and data integration. Map each story from your inventory to its optimal platform and create format-specific versions. + +**Checkpoint:** At least five stories adapted for two platforms each. First drafts created for the two highest-priority channels. + +### Step 5: Writing with Purpose -- Build the Content Engine + +Sporadic posting is not a content strategy. Define the publishing cadence, content pillars, and success metrics that transform personal branding from an occasional activity into a sustainable practice. Each piece of content should serve one of three purposes: attract (reach new audience), engage (deepen existing relationships), or convert (drive a specific action -- follow, subscribe, invest, apply). Content without a clear purpose is noise. Design a weekly rhythm that is sustainable at your current workload -- two high-quality posts per week will always outperform seven mediocre ones. + +**Checkpoint:** Content calendar designed for the next 30 days. Content pillars defined with clear rationale. Success metrics identified that go beyond vanity (engagement rate and DM quality over follower count). + +### Step 6: Leadership Voice and Presence -- Develop Consistency + +The strongest personal brands are recognizable before the reader sees the name. This emerges not from gimmicks but from consistency: recurring themes, a distinctive analytical lens, characteristic sentence rhythms, and a stable emotional register. Define your voice explicitly -- not as a persona to perform but as a set of boundaries that keep your content coherent as it scales. What will you always say? What will you never say? How do you handle controversy, criticism, and being wrong in public? The answers form a voice guide that persists whether you are writing at midnight or speaking on stage. + +**Checkpoint:** Voice guide documented. Three published pieces reviewed against the guide for consistency. Adjustments made where the voice drifts. + +--- + +## Final Deliverable + +Upon completing all six steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Career and Brand Strategy Canvas | `career-strategy-canvas` | Founder (personal reference) | +| Personal Brand Action Plan | `action-plan` | Founder, marketing team | +| Founder Story Case Study | `case-study-template` | Content creation, PR, investor materials | + +## Common Pitfalls + +- **Performing instead of communicating.** Audiences detect inauthenticity with remarkable precision. A founder who shares real lessons earns trust; a founder who performs "thought leadership" earns unfollows. +- **Optimizing for virality over reputation.** Controversial takes and engagement bait generate attention. They rarely generate the right attention. A personal brand is a long-term asset; treat it like one. +- **Starting with tactics.** Posting before defining themes, audience, and voice produces content that is busy but directionless. The first four steps of this playbook exist to prevent exactly this. +- **Neglecting the ongoing practice.** Personal branding compounds. The founder who publishes consistently for twelve months will outperform the one who publishes brilliantly for two weeks and disappears. +- **Outsourcing the voice entirely.** Ghostwriters can amplify a voice that exists. They cannot create one from nothing. The founder must do the foundational work before delegating execution. + +## Adaptation Notes + +- **Idea-stage founders** should weight Step 3 (finding stories) toward problem-discovery narratives -- what they are learning about the market, the customer, and the problem space. The brand builds alongside the company. +- **Growth-stage founders** often face the tension between operational demands and content creation. Step 5 (writing with purpose) should prioritize efficiency: repurpose investor updates, customer insights, and internal memos as public content with minimal additional effort. +- **Scale-stage leaders** may need to transition from personal brand to institutional voice. The personal brand becomes a channel for the company's mission rather than the founder's individual journey. Step 6 (voice and presence) should explicitly address this evolution. +- **Technical founders** uncomfortable with public visibility should begin with expertise-driven content on platforms that reward depth (long-form articles, technical podcasts) rather than platforms that reward performance (short-form video, live events). diff --git a/plugins/foreman/content/playbooks/pivot-playbook.md b/plugins/foreman/content/playbooks/pivot-playbook.md new file mode 100644 index 0000000..c0328e7 --- /dev/null +++ b/plugins/foreman/content/playbooks/pivot-playbook.md @@ -0,0 +1,140 @@ +--- +name: "pivot-playbook" +description: "Used when a founder suspects the current direction has stalled and + is weighing whether to pivot, what to pivot toward, and how to communicate the + change. Chains diagnosis, strategic analysis, model redesign, scenario + testing, decision-making, and narrative framing into a single engagement." +trigger_diagnostics: + - growth-stall-diagnosis + - product-market-fit-diagnosis + - decision-paralysis-diagnosis +steps: + - purpose: "Validate whether product-market fit is genuinely broken or merely + underperforming" + output: "PMF assessment with evidence: retention curves, activation rates, + qualitative signal analysis" + kind: diagnostic + ref: product-market-fit-diagnosis + - skill: "swot-pest-analysis" + purpose: "Map the current position with brutal honesty before designing + alternatives" + output: "SWOT matrix and PEST scan revealing structural vs. tactical weaknesses" + - skill: "business-model-canvas" + purpose: "Redesign the business model around validated assumptions" + output: "Revised canvas with highlighted changes from the current model" + - skill: "scenario-planning" + purpose: "Stress-test three distinct pivot scenarios against plausible futures" + output: "Three scenario narratives with probability-weighted outcomes" + - skill: "evaluating-and-deciding" + purpose: "Make the pivot/stay/adjust decision with a margin of safety" + output: "Decision rationale with reversibility assessment and kill criteria" + - skill: "storytelling-for-leaders" + purpose: "Frame the pivot narrative for team alignment and investor confidence" + output: "Pivot narrative arc with audience-specific messaging" +final_outputs: + - decision-rationale-memo + - action-plan +estimated_duration: "4-8 hours across 1-2 weeks" +complexity: "advanced" +stage: + - validation + - early-traction +author: "Fatih Guner" +--- + +# The Pivot Playbook + +## When to Use This Playbook + +Growth has flatlined. The metrics that once trended upward now move sideways or worse. Customers churn faster than they arrive. The founder senses something structural is wrong but cannot distinguish between a product problem, a market problem, and a model problem. The temptation is to change everything at once or change nothing at all. Both instincts are wrong. + +This playbook applies when the question is genuinely "should we pivot?" -- not "should we optimize?" If the core product works but distribution is broken, the answer is probably operational, not strategic. The diagnostic steps that follow will make that distinction explicit. + +## Prerequisites + +- At least 3-6 months of operating data (revenue, retention, activation, NPS) +- Honest founder willingness to hear that the current model may be dead +- Access to at least 5-10 recent customer conversations or churn interviews +- A clear picture of current runway (the clock disciplines the analysis) + +## The Sequence + +### Step 1: Product-Market Fit Diagnosis +- **Purpose:** Before redesigning anything, confirm the diagnosis. Most founders who say "we need to pivot" are actually experiencing a distribution or pricing problem dressed up as a PMF failure. This step forces evidence-based assessment. +- **Key questions:** Do retained customers love the product? Is churn driven by the wrong customers or the wrong product? Where does the activation funnel break? +- **Input:** Retention data, NPS scores, churn interviews, activation metrics +- **Output:** PMF assessment with a clear verdict: broken, weak, or misdiagnosed +- **Time:** 1-2 hours +- **Checkpoint:** If PMF is intact but underperforming, the problem may be execution rather than direction. Pause before proceeding. + +### Step 2: SWOT-PEST Analysis +- **Purpose:** Map the full strategic landscape. A pivot made without understanding external forces is just a guess in a new direction. PEST reveals macro-tailwinds and headwinds; SWOT reveals internal capability gaps. +- **Key questions:** Which weaknesses are fixable? Which threats are structural? Are there external shifts that change the opportunity space? +- **Input:** PMF assessment from Step 1, market data, competitive intelligence +- **Output:** Combined SWOT-PEST matrix with color-coded severity +- **Time:** 1-1.5 hours +- **Checkpoint:** The matrix must be honest. If every box is filled with optimism, start over with a skeptic in the room. + +## Decision Point + +After completing Steps 1 and 2, the founder faces a fork: + +**Is this a pivot problem or an execution problem?** + +- If the SWOT reveals that strengths are strong, the product retains users who find it, and PEST shows favorable conditions -- this is an execution problem. Exit this playbook. Route to `operational-chaos-diagnosis` and focus on distribution, pricing, or team capacity. +- If the evidence shows genuine PMF failure, structural market headwinds, or a business model that cannot reach unit economics -- continue to Step 3. + +The discipline to exit a playbook mid-sequence is more valuable than the discipline to complete it. + +### Step 3: Business Model Canvas +- **Purpose:** Redesign the model from the ground up. The canvas forces explicit choices about value proposition, customer segments, channels, and revenue streams -- the four areas where pivots actually happen. +- **Key questions:** Which canvas block is most broken? Can you pivot one block without rebuilding everything? What assumptions does the new model rest on? +- **Input:** SWOT-PEST output, PMF failure analysis, competitive gaps identified +- **Output:** Revised Business Model Canvas with changes highlighted against the current model +- **Time:** 1-2 hours +- **Checkpoint:** The revised canvas must contain at least one falsifiable assumption. If it cannot be proven wrong within 30 days, it is not a pivot hypothesis -- it is wishful thinking. + +### Step 4: Scenario Planning +- **Purpose:** A single pivot direction is a bet. Three scenarios with probability-weighted outcomes transform a bet into a strategy. This step stress-tests the revised model against optimistic, baseline, and adverse futures. +- **Key questions:** What happens if the new market is smaller than estimated? What if a competitor moves first? What does the adverse scenario look like at current burn rate? +- **Input:** Revised Business Model Canvas, PEST macro-factors, runway data +- **Output:** Three scenario narratives with financial implications and trigger points for each +- **Time:** 1-1.5 hours +- **Checkpoint:** If the adverse scenario leads to company death within 3 months, the pivot must be sequenced more conservatively or the founder must secure bridge funding first. + +### Step 5: Evaluating and Deciding +- **Purpose:** Synthesize all preceding analysis into a single, defensible decision. This step applies margin-of-safety thinking -- the decision must survive being partially wrong. +- **Key questions:** What is the cost of being wrong? Is this decision reversible? What kill criteria will trigger a second pivot? +- **Input:** Scenario outputs, canvas comparison, PMF verdict +- **Output:** Written decision rationale with explicit kill criteria and 90-day milestones +- **Time:** 0.5-1 hour +- **Checkpoint:** The decision rationale must be presentable to a skeptical board member. If it cannot survive five minutes of adversarial questioning, it is not ready. + +### Step 6: Storytelling for Leaders +- **Purpose:** A pivot that the team does not understand is a pivot that fails in execution. This step crafts the narrative -- not spin, but a coherent story that connects the old direction, the evidence, the decision, and the new path. +- **Key questions:** What is the honest story of why the old direction failed? What gives the team confidence that the new direction is grounded in evidence rather than panic? +- **Input:** Decision rationale, scenario analysis, PMF evidence +- **Output:** Pivot narrative with versions for team (motivational but honest) and investors (evidence-driven with financial clarity) +- **Time:** 0.5-1 hour +- **Checkpoint:** Read the narrative aloud. If it sounds like corporate spin, rewrite it. The team will detect insincerity faster than any investor will. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `decision-rationale-memo` | Investors, board | Evidence-based case for the pivot with financial projections and kill criteria | +| `action-plan` | Team | 90-day execution plan with milestones, owners, and dependencies | + +## Common Pitfalls + +1. **Pivoting away from traction.** Some founders pivot because the business is not growing fast enough, even when a loyal customer segment exists. Confirm that retention is genuinely broken before abandoning ship. +2. **Confusing a pivot with a rebrand.** Changing the name, website, and messaging without changing the value proposition or customer segment is not a pivot. The canvas must show structural changes. +3. **Running the playbook alone.** The founder who decides to pivot in isolation and then announces it has already lost the team. Involve at least one co-founder or senior team member in Steps 3-5. +4. **Skipping the kill criteria.** A pivot without defined failure conditions becomes an infinite runway of hope. Set explicit 90-day checkpoints before executing. +5. **Over-communicating certainty.** The pivot narrative should convey conviction grounded in evidence, not omniscience. Teams respect honesty about uncertainty more than false confidence. + +## Adaptation Notes + +- **Validation stage:** The pivot may be a model pivot (same problem, different solution) or a customer pivot (same solution, different segment). At this stage, pivots should be fast and cheap -- weeks, not months. +- **Early-traction stage:** Pivots here carry higher stakes because real customers and revenue exist. The communication step (Step 6) becomes disproportionately important. Expect investor conversations to be harder. +- At either stage, runway is the binding constraint. Every step in this playbook should be calibrated against the time remaining, not the time desired. diff --git a/plugins/foreman/content/playbooks/pricing-strategy-playbook.md b/plugins/foreman/content/playbooks/pricing-strategy-playbook.md new file mode 100644 index 0000000..4c70504 --- /dev/null +++ b/plugins/foreman/content/playbooks/pricing-strategy-playbook.md @@ -0,0 +1,136 @@ +--- +name: "pricing-strategy-playbook" +description: "Used when a founder needs to set initial pricing, restructure a pricing model that is not working, or evaluate a fundamental shift in monetisation strategy. Chains marketing mix analysis, competitive landscape mapping, value perception assessment, differentiation strategy, decision evaluation, and experiment design into a rigorous pricing engagement. Use when revenue underperforms expectations, conversion drops at the pricing page, or the founder simply does not know what to charge." +trigger_diagnostics: + - pricing-diagnosis + - revenue-diagnosis +steps: + - skill: "four-ps-marketing" + purpose: "Understand pricing within the full marketing mix -- price cannot be set in isolation from product positioning, channel, and promotion" + output: "Marketing mix assessment with pricing positioned relative to product value, distribution channel, and competitive framing" + - skill: "porters-five-forces" + purpose: "Map the competitive pricing landscape -- who sets the price ceiling, who sets the floor, and where substitutes lurk" + output: "Five forces analysis with pricing-specific annotations: buyer power, substitute availability, and competitor pricing patterns" + - skill: "information-asymmetry" + purpose: "Understand the value perception gap between what the product delivers and what customers believe it delivers" + output: "Information map revealing where customers undervalue, overvalue, or misunderstand the offering -- and signalling strategies to close the gap" + - skill: "blue-ocean-strategy" + purpose: "Identify value innovation opportunities that justify premium pricing or enable entirely new pricing models" + output: "Strategy canvas showing where to eliminate, reduce, raise, and create -- with pricing implications for each move" + - skill: "evaluating-and-deciding" + purpose: "Systematically evaluate pricing model options: subscription, usage-based, freemium, tiered, per-seat, or hybrid" + output: "Decision matrix comparing pricing models against criteria: revenue predictability, customer alignment, competitive defensibility, and implementation complexity" + - skill: "smart-goals" + purpose: "Set pricing experiment metrics so the new pricing can be validated rather than assumed" + output: "SMART goals for pricing rollout with conversion targets, revenue milestones, and churn thresholds" +final_outputs: + - unit-economics-snapshot + - strategic-analysis-one-pager + - action-plan +estimated_duration: "4-6 hours" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth +author: "Fatih Guner" +--- + +# The Pricing Strategy Playbook + +## When to Use This Playbook + +Pricing is the most underleveraged variable in most startups. Founders agonise over product features, marketing channels, and hiring plans, then set their price by glancing at a competitor's website and picking a number that "feels right." The result is predictable: margins that cannot sustain the business, conversion rates that puzzle the team, and a nagging suspicion that money is being left on the table or -- worse -- that the price itself is repelling the customers who matter most. + +This playbook applies when pricing needs to be set for the first time, when existing pricing is not working (low conversion, high churn at renewal, or persistent discounting), or when the business model is shifting in ways that demand a new monetisation structure entirely. It does not apply when the product itself lacks value -- no pricing strategy rescues a product nobody wants. + +## Prerequisites + +- A product that delivers measurable value to at least some customers +- Basic financial data: cost structure, current margins (or modelled margins), customer acquisition cost +- Access to competitive pricing data (public pricing pages, industry benchmarks, or customer feedback on alternatives) +- Willingness to experiment -- pricing is a hypothesis, not a decree +- Clarity on whether the objective is revenue maximisation, market penetration, or margin optimisation + +## The Sequence + +### Step 1: Four Ps Marketing +- **Purpose:** Price is one variable in a four-variable equation. A premium price with commodity positioning fails. A low price with a high-touch sales channel destroys margins. This step maps the full marketing mix to ensure pricing decisions are coherent with product positioning, distribution, and promotional strategy. +- **Key questions:** What does the current positioning promise? Does the price reinforce or contradict that promise? Which channel delivers the customer, and what does that channel cost? Is the promotion strategy aligned with the price point? +- **Input:** Current pricing, product positioning, channel economics, competitive context +- **Output:** Marketing mix assessment revealing alignment gaps between price and the other three Ps +- **Time:** 1-1.5 hours +- **Checkpoint:** If the positioning says "premium" but the price says "commodity," everything downstream will be confused. Resolve positioning-price alignment before continuing. + +### Step 2: Porter's Five Forces +- **Purpose:** The competitive landscape sets the boundaries of pricing power. Strong buyer power compresses margins. Abundant substitutes cap the price ceiling. High barriers protect premium positions. This step maps the forces that constrain and enable pricing decisions. +- **Key questions:** How much pricing power do buyers have? Are there substitutes that set an implicit price ceiling? Do competitors compete on price, features, or service? What would a new entrant price at? +- **Input:** Marketing mix from Step 1, competitive intelligence, market structure data +- **Output:** Five forces pricing map showing where pricing power exists and where it does not +- **Time:** 1-1.5 hours +- **Checkpoint:** The forces map must be honest about pricing constraints. Founders who believe they have pricing power they do not have will set prices the market rejects. + +## Decision Point + +After completing Steps 1 and 2, a strategic fork: + +**Is the market price-sensitive or value-sensitive?** + +- If the five forces analysis reveals commoditised competition, powerful buyers, and abundant substitutes -- the market is price-sensitive. Proceed to Step 3 (information asymmetry) with priority on signalling strategies that differentiate on perceived value within a constrained price range. Step 4 (blue ocean) becomes about finding the value dimensions competitors ignore, enabling escape from price competition. +- If the analysis shows differentiated competitors, loyal customer segments, and high switching costs -- the market is value-sensitive. Step 4 (blue ocean) takes priority, focusing on value innovation that justifies premium or novel pricing models. Step 3 (information asymmetry) then ensures customers perceive the premium value accurately. + +The sequence of Steps 3 and 4 remains the same, but the emphasis and time allocation shift based on this diagnosis. + +### Step 3: Information Asymmetry +- **Purpose:** Customers rarely understand the full value of what they are buying. The gap between delivered value and perceived value is where pricing power is won or lost. This step maps the information asymmetries -- where customers underestimate value, where they overestimate risk, and what signals would close the gap. +- **Key questions:** What value does the product deliver that customers cannot easily observe? How do customers evaluate quality before purchase? What signals (credentials, social proof, guarantees) would reduce perceived risk? Where does the customer overvalue a competitor's offering? +- **Input:** Five forces output, customer feedback, churn reasons, sales objection data +- **Output:** Information asymmetry map with signalling strategies for each gap +- **Time:** 0.5-1 hour +- **Checkpoint:** If the primary value is invisible to the customer pre-purchase, the pricing strategy must include mechanisms to make value visible -- trials, guarantees, case studies, or usage-based pricing that links payment to demonstrated outcomes. + +### Step 4: Blue Ocean Strategy +- **Purpose:** Competing on the same dimensions as everyone else means competing on price. Blue ocean strategy identifies where to eliminate costs, reduce features customers do not value, raise attributes competitors underinvest in, and create entirely new value dimensions. Each move has direct pricing implications. +- **Key questions:** Which features or costs can be eliminated without losing core value? Where can value be created that competitors do not offer? Does the eliminate-reduce-raise-create grid suggest a fundamentally different price point? +- **Input:** Five forces map, information asymmetry analysis, competitive pricing data +- **Output:** Strategy canvas with pricing implications: where the new value curve justifies premium, enables lower cost, or supports a novel pricing model +- **Time:** 1-1.5 hours +- **Checkpoint:** The strategy canvas must show at least one dimension where the company diverges significantly from competitors. If the canvas mirrors the industry, the pricing will too. + +### Step 5: Evaluating and Deciding +- **Purpose:** Armed with competitive data, value perception insights, and differentiation opportunities, this step systematically evaluates pricing model options. Subscription, usage-based, freemium, tiered, per-seat, one-time -- each model carries different revenue dynamics, customer psychology, and operational requirements. +- **Key questions:** Which pricing model aligns with how customers experience value? Does the customer receive value gradually (subscription) or in discrete events (usage)? What is the competitive norm, and is there advantage in breaking it? What does each model require operationally? +- **Input:** All outputs from Steps 1-4, current unit economics, customer usage patterns +- **Output:** Decision matrix evaluating 3-5 pricing models against weighted criteria +- **Time:** 1-1.5 hours +- **Checkpoint:** The chosen model must be implementable within 30 days. If it requires infrastructure that does not exist, either simplify the model or plan the build before announcing the price. + +### Step 6: SMART Goals +- **Purpose:** A new pricing strategy is a hypothesis until the market validates it. This step defines the experiment: what metrics will confirm the pricing works, what thresholds trigger a revision, and over what time period the test runs. +- **Key questions:** What conversion rate validates the price point? What churn rate at renewal invalidates it? How many customers constitute a statistically meaningful sample? What is the fallback if the experiment fails? +- **Input:** Chosen pricing model from Step 5, current baseline metrics, revenue targets +- **Output:** SMART goals for the pricing rollout with specific metrics, measurement cadence, and decision triggers +- **Time:** 0.5-1 hour +- **Checkpoint:** Every pricing goal must have a time-bound evaluation date. Pricing experiments that run indefinitely produce ambiguous results and organisational paralysis. + +## Final Deliverable + +| Template | Audience | Purpose | +|----------|----------|---------| +| `unit-economics-snapshot` | Founder, investors | Updated unit economics reflecting the new pricing model with sensitivity analysis | +| `strategic-analysis-one-pager` | Board, advisors | Concise rationale for the pricing decision with competitive context and expected impact | +| `action-plan` | Team | Pricing rollout plan with implementation steps, experiment design, and review cadence | + +## Common Pitfalls + +1. **Pricing by imitation.** Copying a competitor's price copies their cost structure, positioning, and margin assumptions -- none of which may apply. Competitive pricing is an input, not a formula. +2. **Underpricing from fear.** Founders afraid of losing customers set prices too low, attract price-sensitive buyers who churn at any increase, and build a business that cannot afford to serve them. Price for the customer you want, not the customer you fear losing. +3. **Changing price without changing signal.** Raising the price without improving perceived value creates sticker shock. The information asymmetry step exists to prevent this. +4. **Overcomplicating the model.** Tiered pricing with seven tiers, usage-based pricing with four metered dimensions, and add-on bundles create cognitive load that kills conversion. The best pricing is simple enough to explain in one sentence. +5. **Skipping the experiment.** Launching a new price to the entire customer base without testing it on a subset is a one-way decision made with two-way-door uncertainty. Always test first. + +## Adaptation Notes + +- **Validation stage:** Pricing is a discovery tool, not a revenue tool. Set a price to test willingness to pay, not to optimise margins. Founder conversations with early customers about pricing generate more insight than any spreadsheet model. The SMART goals at this stage should measure learning velocity, not revenue. +- **Early-traction stage:** Pricing begins to matter financially. The emphasis shifts to unit economics and the relationship between price, CAC, and LTV. Grandfathering early customers while introducing new pricing requires careful communication -- the trust equation matters here. +- **Growth stage:** Pricing becomes a strategic lever. The blue ocean and five forces steps carry disproportionate weight because pricing decisions at scale are difficult to reverse. Consider price segmentation, enterprise tiers, and international pricing. The experiment step becomes essential: test pricing changes on cohorts before rolling them out broadly. diff --git a/plugins/foreman/content/playbooks/product-market-fit-playbook.md b/plugins/foreman/content/playbooks/product-market-fit-playbook.md new file mode 100644 index 0000000..46c6063 --- /dev/null +++ b/plugins/foreman/content/playbooks/product-market-fit-playbook.md @@ -0,0 +1,144 @@ +--- +name: "product-market-fit-playbook" +description: "Provides a systematic, iterative approach to searching for product-market fit -- from mapping assumptions through measuring signals, running rapid experiments, and establishing kill criteria for pivot-or-persist decisions. Use when pre-PMF, when retention is flat despite iterations, or when the founder suspects they are solving the wrong problem." +version: "1.0.0" +category: "playbooks" +complexity: "advanced" +stage: + - idea + - validation +trigger_diagnostics: + - product-market-fit-diagnosis + - revenue-diagnosis +steps: + - skill: "business-model-canvas" + purpose: "Map current assumptions about the business model -- every block is a hypothesis until validated by revenue" + output: "Annotated Business Model Canvas with each block rated by evidence level: validated, partially validated, or assumption" + - skill: "four-ps-marketing" + purpose: "Define the initial value proposition and customer segment with enough precision to test" + output: "Product-market hypothesis stating who the customer is, what the product does for them, and why they would pay" + - skill: "net-promoter-score" + purpose: "Design a measurement system for PMF signals -- retention, referral, and willingness to pay" + output: "PMF measurement framework with NPS baseline, retention cohort design, and leading indicator dashboard" + - skill: "creative-practice-and-habit" + purpose: "Establish rapid experimentation habits that sustain through ambiguity and repeated failure" + output: "Experimentation cadence with weekly rhythm, hypothesis format, minimum viable test criteria, and documentation practice" + - skill: "defining-and-exploring-problems" + purpose: "Ensure you are solving the RIGHT problem -- the one customers have, not the one the founder assumed" + output: "Problem validation report with customer evidence distinguishing the stated problem from the actual problem" + - skill: "evaluating-and-deciding" + purpose: "Create kill criteria -- explicit conditions under which you pivot, persevere, or shut down" + output: "Decision framework with pivot triggers, perseverance criteria, and a structured process for the pivot-or-persist call" +final_outputs: + - new-initiative-brief + - unit-economics-snapshot + - decision-journal +estimated_duration: "Ongoing -- 2-4 hours per iteration cycle, multiple cycles" +author: "Fatih Guner" +--- + +# Product-Market Fit Playbook + +Marc Andreessen described product-market fit as "the only thing that matters," then offered almost no systematic guidance on how to find it. The concept is easy to recognize in retrospect -- customers pulling the product out of your hands, growth that feels organic rather than forced, retention curves that flatten instead of declining to zero. Prospectively, the search for PMF is closer to archaeology than engineering: you know something is buried, you have a general map of the terrain, but every dig site requires a hypothesis, a careful excavation, and the intellectual honesty to recognize when you have found a potsherd rather than a palace. + +This playbook does not promise product-market fit. It provides a systematic process for searching -- one that replaces the founder's default mode of building features and hoping with a disciplined cycle of hypothesizing, testing, measuring, and deciding. + +--- + +## When to Use This Playbook + +- Pre-revenue and searching for the initial value proposition that customers will pay for +- Post-launch but retention is flat -- users try the product and leave +- Revenue exists but comes from discounts, favors, or unsustainable sales effort rather than genuine demand +- The founder has iterated multiple times without clear progress toward PMF +- Customer feedback is polite but noncommittal -- "interesting" rather than "I need this" +- The team is building features without a clear hypothesis about which ones matter + +## Prerequisites + +- A product or prototype that can be put in front of real customers (even if minimal) +- Access to at least 10-20 potential customers for conversation and testing +- Honest acknowledgment that PMF has not been achieved -- the founder who believes they have PMF but lacks the metrics to prove it is the hardest case +- Sufficient runway for 3-6 iteration cycles (if runway is under 3 months, prioritize survival over experimentation) + +--- + +## The Sequence + +### Step 1: Business Model Canvas -- Map the Assumptions + +Before testing anything, make the assumptions explicit. Every box on the Business Model Canvas represents a hypothesis: who the customer is, what value proposition resonates, which channels reach them, how revenue is generated. Most founders carry these assumptions implicitly, never written down, never challenged. This step forces them onto paper and rates each by evidence level. A block supported by customer data is "validated." A block supported by the founder's intuition is "assumption." The canvas becomes a map of what you know, what you think you know, and what you are guessing -- and the distinction matters enormously for deciding what to test first. + +**Checkpoint:** Annotated canvas completed. At least three blocks honestly rated as "assumption." The highest-risk assumption identified as the first test target. + +### Step 2: Four Ps Marketing -- Define the Hypothesis with Precision + +A hypothesis that cannot be proven wrong cannot guide you. "Customers will like our product" is not a hypothesis. "Mid-market SaaS CFOs with 50-200 employees will pay $500/month for automated financial consolidation because they currently spend 15 hours per month doing it manually" is a hypothesis. This step forces precision about the customer segment, the specific value proposition, the price point, and the distribution channel. The Four Ps framework -- product, price, place, promotion -- provides the structure. Each P must be specific enough to design a test around it. + +**Checkpoint:** Written product-market hypothesis with falsifiable predictions. The hypothesis should be uncomfortable in its specificity -- if it feels safe, it is too vague to test. + +--- + +### Decision Point: Signal Check + +After establishing the measurement system in Step 3, the playbook enters an iterative cycle. The decision point recurs after every 2-3 iteration cycles. + +**Are NPS and retention signals trending upward?** If yes, continue iterating within the current hypothesis space. The signal suggests the general direction is correct; the task is refinement. Proceed through Steps 4-6 and return to Step 2 with an updated hypothesis. + +**Are signals flat after 3 iterations?** Flat signals after genuine experimentation -- not cosmetic changes but structural variations in the value proposition, customer segment, or pricing -- indicate a deeper problem. The hypothesis may be wrong at its foundation. Consider invoking the `pivot-playbook` to evaluate whether the entire direction requires rethinking. + +**Are signals declining?** Declining signals after iterations suggest active misalignment between the product and the market. Stop iterating on the current hypothesis. Return to Step 5 (problem definition) to re-examine whether the problem itself is real, urgent, and underserved. + +The discipline to read signals honestly -- neither inflating modest results into validation nor interpreting noise as failure -- is the central skill of the PMF search. + +--- + +### Step 3: Net Promoter Score -- Build the Measurement System + +You cannot find what you cannot measure, and most pre-PMF startups measure the wrong things. Revenue is a lagging indicator. Feature usage is ambiguous. The measurement system for PMF requires three components: a retention cohort analysis (are users from month one still active in month three?), an NPS or willingness-to-recommend metric (would customers be disappointed if the product disappeared?), and a leading indicator dashboard that the team reviews weekly. Design the system before running experiments so that every iteration produces data rather than anecdotes. + +**Checkpoint:** Measurement framework operational. Baseline metrics captured. The team can answer "are we closer to PMF than last month?" with data rather than feelings. + +### Step 4: Creative Practice and Habit -- Establish the Experimentation Rhythm + +The search for PMF is a sustained creative effort, not a single heroic sprint. Most founders run one or two experiments, get ambiguous results, and then either give up on experimentation or retreat into feature-building. This step designs an experimentation cadence that survives discouragement: weekly hypothesis generation, rapid test design (minimum viable tests that produce signal within days, not months), disciplined documentation of results, and structured reflection on what was learned. The rhythm matters more than any single experiment. + +**Checkpoint:** Experimentation rhythm established with a weekly cadence. First three experiments designed with clear hypotheses, test methods, and success criteria. + +### Step 5: Defining and Exploring Problems -- Validate the Problem + +The most dangerous assumption in any startup is that the problem is real. Founders fall in love with solutions and work backwards to justify the problem they solve. This step forces a return to the customer: does this problem actually exist in the way you imagine? Is it urgent enough that people seek solutions rather than tolerate the pain? Is it underserved -- or are existing solutions adequate and the market is not waiting for yours? The problem validation uses structured customer interviews, not the kind where the founder pitches the product and interprets polite interest as validation, but the kind where the founder listens for evidence of pain, urgency, and willingness to act. + +**Checkpoint:** Problem validation report distinguishing founder assumptions from customer evidence. If the problem is real but the solution is wrong, return to Step 2. If the problem itself is misidentified, return to Step 1 and rebuild the canvas. + +### Step 6: Evaluating and Deciding -- Set Kill Criteria + +The search for PMF can consume a company. Without explicit criteria for when to persist, when to pivot, and when to stop, the founder's optimism bias extends the search well past the point of diminishing returns. This step creates a decision framework: what metrics, at what thresholds, after how many iterations, trigger each decision? Define the kill criteria before the emotions of the search cloud judgment. A startup that pivots with runway remaining has options. A startup that persists until the money runs out has none. + +**Checkpoint:** Kill criteria documented with specific metrics, thresholds, and timelines. Decision journal initiated to track the reasoning behind each persist-or-pivot call. + +--- + +## Final Deliverable + +Upon completing each iteration cycle, compile and update the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Experiment Brief | `new-initiative-brief` | Team, advisors | +| Unit Economics Snapshot | `unit-economics-snapshot` | Founders, investors | +| Decision Journal | `decision-journal` | Founders (internal reference) | + +## Common Pitfalls + +- **Confusing customer interest with product-market fit.** "That sounds interesting" is not validation. Revenue, retention, and referral are validation. Everything else is politeness. +- **Iterating on features instead of hypotheses.** Adding features without a clear hypothesis about which problem they solve and for whom produces a bloated product that pleases no one deeply. +- **Measuring activity instead of outcomes.** Signups, page views, and downloads are vanity metrics. Retention, NPS, and willingness to pay are PMF metrics. Measure what matters. +- **Refusing to talk to customers.** Building in isolation because customer conversations are uncomfortable is the most expensive form of avoidance in entrepreneurship. +- **Moving kill criteria when they are triggered.** Kill criteria exist to override the founder's optimism bias at the moment when that bias is strongest. Changing the goalposts because the data is unfavorable defeats the purpose entirely. + +## Adaptation Notes + +- **Idea-stage founders** should spend disproportionate time on Steps 1, 2, and 5 -- the hypothesis and problem validation. At this stage, writing code is often premature. Talk to fifty customers before building anything substantial. +- **Validation-stage founders** with a product in market should weight Steps 3 and 4 -- measurement and experimentation rhythm. The product exists; the question is whether it generates pull. Let the data guide iterations, not the roadmap. +- At both stages, the single greatest risk is the sunk cost fallacy: continuing to invest in a direction because of what has already been spent rather than what the evidence suggests. The decision journal in Step 6 exists specifically to counteract this. diff --git a/plugins/foreman/content/playbooks/remote-team-playbook.md b/plugins/foreman/content/playbooks/remote-team-playbook.md new file mode 100644 index 0000000..69e11ec --- /dev/null +++ b/plugins/foreman/content/playbooks/remote-team-playbook.md @@ -0,0 +1,150 @@ +--- +name: "remote-team-playbook" +description: "Guides founders through building and managing effective remote or hybrid teams -- from establishing structural conditions and trust to designing async-first communication, culture rituals, and autonomy-driven workflows. Use when transitioning to remote work, building a distributed team from scratch, or struggling with hybrid team dynamics." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +trigger_diagnostics: + - team-dysfunction-diagnosis + - communication-breakdown-diagnosis + - operational-chaos-diagnosis +steps: + - skill: "hackman-enabling-conditions" + purpose: "Establish the structural conditions for remote team success before addressing culture or communication" + output: "Enabling conditions audit adapted for distributed teams, with remote-specific gaps and structural recommendations" + - skill: "psychological-safety-practice" + purpose: "Build trust without the natural rapport that physical proximity provides" + output: "Psychological safety assessment with remote-specific interventions: async vulnerability practices, virtual feedback norms, and trust rituals" + - skill: "writing-for-navigation" + purpose: "Establish written communication as the primary medium for an async-first operating model" + output: "Written communication standards including document templates, async decision formats, and information architecture guidelines" + - skill: "team-culture-and-dynamics" + purpose: "Create remote culture rituals and norms that replace the organic interactions of co-located teams" + output: "Culture playbook with remote rituals, virtual social practices, and explicit norms for distributed collaboration" + - skill: "delegation-and-empowerment" + purpose: "Design for autonomy -- remote teams cannot function under micromanagement" + output: "Delegation matrix with decision rights, escalation paths, and accountability mechanisms suited to asynchronous work" + - skill: "focus-and-priority-management" + purpose: "Establish async meeting hygiene and deep work protection across time zones" + output: "Meeting policy, focus time blocks, and priority management framework for distributed teams" +final_outputs: + - culture-values-document + - action-plan + - team-health-check + - meeting-notes-template +estimated_duration: "5-10 hours across 2-3 weeks" +author: "Fatih Guner" +--- + +# Remote Team Playbook + +Every distributed team that works well looks the same from the outside: seamless collaboration, clear communication, autonomous execution. Every distributed team that fails looks different -- but the root cause is almost always identical. Someone tried to replicate an office on Zoom. The meeting-heavy, presence-obsessed, synchronous-by-default operating model that barely functions in person becomes actively destructive when distributed across time zones, home offices, and the thousand small frictions of remote work. + +Building a remote team is not a logistics problem. It is a design problem. The team's structure, communication patterns, trust mechanisms, and cultural rituals all require deliberate architecture that most co-located teams never need to articulate because physical proximity papers over the gaps. + +--- + +## When to Use This Playbook + +- Building a new team that will be fully remote or distributed across multiple locations +- Transitioning an existing co-located team to remote or hybrid work +- Experiencing communication breakdowns, misalignment, or declining engagement in a distributed team +- Struggling with the "two-class" problem in hybrid teams where office workers dominate decisions +- Losing talent because the remote work experience is poor relative to competitors +- Founders or leaders who sense that "something is off" but cannot pinpoint whether the issue is people, process, or structure + +## Prerequisites + +- Clarity on whether the team is fully remote or hybrid (this playbook covers both, but the decision point after Step 1 adjusts the approach) +- Basic collaboration infrastructure in place (video conferencing, messaging, shared documents) +- Leadership commitment to async-first principles -- not just tolerance of remote work, but genuine redesign around it +- Willingness to reduce meeting load, which requires trusting people to work without being watched + +--- + +## The Sequence + +### Step 1: Hackman Enabling Conditions -- Build the Structure First + +Remote work amplifies every structural deficiency. Unclear team boundaries become territorial disputes conducted over Slack. Absent compelling direction becomes drift that no one notices for weeks. A team without the right mix of skills compensates in an office through hallway conversations; remotely, the gap becomes a black hole. Apply Hackman's five enabling conditions with remote-specific scrutiny: real team boundaries (who is on this team and who is not?), compelling direction (can every member articulate the mission without checking a document?), enabling structure (right size, right skills, explicit norms), supportive context (tools, information access, equitable compensation regardless of location), and expert coaching availability. + +**Checkpoint:** All five conditions assessed with remote-specific gaps identified. Structural changes prioritized by impact. + +--- + +### Decision Point: Fully Remote or Hybrid? + +After Step 1, the most consequential design choice becomes clear. + +**Fully remote teams** have a structural advantage: equality of experience. Everyone communicates through the same channels, attends meetings in the same format, and accesses information through the same systems. The remaining steps apply directly. + +**Hybrid teams** face a harder problem. The "two-class" dynamic -- where office-present employees dominate decisions, receive more visibility, and build stronger relationships with leadership -- is not a cultural failure. It is a structural inevitability unless explicitly designed against. For hybrid teams, every subsequent step must answer an additional question: does this practice work equally well for someone who is never in the office? + +If hybrid, consider these additional design constraints before proceeding: +- All meetings default to video, even when some participants are co-located +- Decisions made in hallways must be documented and shared within 24 hours +- Promotion and performance criteria must be output-based, never presence-based +- Social rituals must have remote-native equivalents, not remote accommodations + +--- + +### Step 2: Psychological Safety -- Build Trust Without Proximity + +Physical proximity generates trust through accumulated micro-interactions: shared meals, overheard conversations, body language, the simple repeated experience of being in the same space. Remote teams lack all of this. Trust must be built intentionally through practices that feel artificial at first but become natural with repetition. Leader vulnerability is the catalyst -- when the founder admits uncertainty or mistakes in a written update rather than behind a closed office door, it sets a standard that propagates. Design specific practices: written retrospectives where failure is discussed openly, async check-ins that invite honest status rather than performative optimism, and explicit norms around response time that prevent the anxiety of unanswered messages. + +**Checkpoint:** Safety assessment completed. At least three remote-specific trust practices initiated and scheduled as recurring rituals. + +### Step 3: Writing for Navigation -- Make Writing the Operating System + +In a co-located office, information travels through air. In a remote team, information travels through text. The quality of a remote team's written communication is the single best predictor of its effectiveness. This step goes beyond "write better emails." It establishes writing as the primary operating system: decisions are documented in structured formats, context is provided proactively rather than requested reactively, and documents are designed for navigation -- scannable, hierarchical, and actionable. Async-first means the default is a written document, not a meeting. Meetings become the exception reserved for high-ambiguity, high-emotion, or real-time collaboration needs. + +**Checkpoint:** Written communication standards published. At least three document templates adopted (decision record, project update, async standup). Meeting policy established distinguishing "must be synchronous" from "should be async." + +### Step 4: Team Culture and Dynamics -- Design the Informal Layer + +Culture in an office forms organically. Culture in a remote team forms by design or not at all. The absence of hallway conversations, lunch groups, and spontaneous interactions means that social bonds require scheduled opportunities -- which sounds contradictory but works in practice. Design rituals that serve remote teams specifically: virtual coffee pairings (random, cross-functional, weekly), async social channels with genuine engagement rather than forced participation, team retrospectives that address how people feel alongside what they shipped. The rituals must be lightweight enough to survive busy periods and meaningful enough to be missed when skipped. + +**Checkpoint:** At least four recurring culture rituals designed and launched. Team feedback collected after the first cycle to iterate. + +### Step 5: Delegation and Empowerment -- Design for Autonomy + +Micromanagement is inefficient in an office. It is impossible at scale in a remote team -- and the attempt to maintain it produces the worst of both worlds: delayed decisions and surveilled workers. This step designs a delegation framework where decision rights are explicit, context is abundant, and trust replaces oversight. Define which decisions each role can make independently, which require consultation, and which require approval. Then ensure the information needed for those decisions is accessible without asking. Autonomy without information is abandonment; autonomy with information is empowerment. + +**Checkpoint:** Delegation matrix published with decision categories, authority levels, and information sources. At least one decision previously requiring founder approval delegated with clear boundaries. + +### Step 6: Focus and Priority Management -- Protect Deep Work + +The final failure mode of remote teams is death by notification. Without the natural rhythm of an office -- arrival, meetings, lunch, departure -- remote workers face an undifferentiated stream of messages, pings, and requests that fragments attention and erodes productivity. Design explicit boundaries: core collaboration hours (when synchronous availability is expected), focus blocks (when interruption is prohibited), and meeting-free days (when the calendar belongs to deep work). Establish priority management practices that make the most important work visible without requiring status meetings to surface it. + +**Checkpoint:** Meeting policy finalized with maximum weekly meeting hours. Focus time blocks established. Async standup replacing at least one recurring synchronous meeting. + +--- + +## Final Deliverable + +Upon completing all six steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Remote Culture and Values Document | `culture-values-document` | Entire team | +| Remote Operations Action Plan | `action-plan` | Leadership team | +| Team Health Check | `team-health-check` | Founder, leadership | +| Meeting and Communication Standards | `meeting-notes-template` | Entire team | + +## Common Pitfalls + +- **Replicating the office on Zoom.** Eight hours of video calls is not remote work. It is office work with worse ergonomics. Async-first means meetings are the exception, not the medium. +- **Equating presence with productivity.** Monitoring tools, mandatory cameras, and always-on Slack expectations signal distrust. They attract compliance-oriented workers and repel autonomous ones. +- **Ignoring the hybrid tax.** Hybrid is structurally harder than fully remote. Pretending otherwise -- "just dial in from the conference room" -- guarantees a two-class team within months. +- **Under-investing in written communication.** Poor writing creates more meetings, which creates more fatigue, which reduces writing quality. The cycle is vicious and starts with leaders who refuse to write clearly. +- **Designing rituals that only work in one time zone.** If the "team happy hour" is midnight for half the team, it is not a team ritual. It is an exclusion mechanism with a friendly name. + +## Adaptation Notes + +- **Early-traction teams** building remote-first from inception have an advantage: no co-located habits to unlearn. Invest heavily in Steps 3 and 5 to establish strong async norms before the team scales beyond the point where informal coordination works. +- **Growth-stage teams** transitioning to remote or hybrid after being co-located face the hardest version of this playbook. Existing culture, communication patterns, and decision-making habits all require conscious redesign. Expect resistance from employees who benefited from proximity-based influence. +- **Scale-stage teams** should treat this playbook as a recurring audit rather than a one-time setup. Every significant hiring wave, geographic expansion, or organizational restructuring resets the remote operating model and requires re-evaluation of Steps 1, 4, and 6. diff --git a/plugins/foreman/content/playbooks/scaling-playbook.md b/plugins/foreman/content/playbooks/scaling-playbook.md new file mode 100644 index 0000000..05bfa62 --- /dev/null +++ b/plugins/foreman/content/playbooks/scaling-playbook.md @@ -0,0 +1,148 @@ +--- +name: "scaling-playbook" +description: "Guides founders through the transition from scrappy startup to structured organization — scaling from 10 to 50+ people, replacing heroics with systems, and ensuring culture survives the growth. Use when experiencing growth stalls, operational chaos, hiring bottlenecks, or founder burnout from doing everything personally." +version: "1.0.0" +category: "playbooks" +complexity: "advanced" +stage: + - early-traction + - growth +trigger_diagnostics: + - growth-stall-diagnosis + - operational-chaos-diagnosis + - hiring-diagnosis +steps: + - skill: "balanced-scorecard" + purpose: "Establish a measurement system beyond revenue that captures the full health of a scaling organization" + output: "Four-perspective scorecard with leading indicators for team, process, customer, and financial health" + - skill: "hackman-enabling-conditions" + purpose: "Design team structures that function without founder intervention at every decision point" + output: "Team architecture document defining enabling conditions for each functional group" + - skill: "organisational-culture" + purpose: "Codify the culture explicitly before dilution becomes irreversible" + output: "Written culture framework with values, norms, and behavioral expectations" + - skill: "delegation-and-empowerment" + purpose: "Shift operating model from founder-does-everything to distributed ownership" + output: "Delegation matrix mapping decisions, authority levels, and accountability" + - skill: "leadership-pipeline" + purpose: "Build the next layer of leaders who can carry the organization beyond founder capacity" + output: "Leadership development plan with identified candidates, gaps, and growth paths" + - skill: "kaizen-bpr" + purpose: "Systematize the processes that currently rely on tribal knowledge and individual heroics" + output: "Process documentation and improvement roadmap for critical operational workflows" + - skill: "senior-leadership-transition" + purpose: "Evolve the founder's own role from operator to strategic leader" + output: "CEO role evolution plan with timeline, handoff milestones, and new focus areas" +final_outputs: + - quarterly-strategic-review + - culture-values-document + - action-plan + - ceo-succession-brief +estimated_duration: "10-20 hours across 4-8 weeks" +author: "Fatih Guner" +--- + +# Scaling Playbook + +Every founder who survives the early chaos eventually hits the same wall: the things that got you to ten people will destroy you at fifty. The improvisation, the flat hierarchy, the founder-as-bottleneck operating model -- these are assets at five employees and liabilities at twenty-five. Scaling is not about doing more of the same. It is about becoming a fundamentally different organization while preserving what made the original one worth building. + +--- + +## When to Use This Playbook + +- Revenue is growing but operations are fraying at the seams +- The founder is the answer to every question and the bottleneck for every decision +- New hires are not performing because onboarding is "figure it out" +- The culture that once felt organic now feels inconsistent or diluted +- Team leads are managing but not leading, and no one is developing them +- Processes exist in people's heads rather than in documented systems + +## Prerequisites + +- Product-market fit is established (this playbook assumes traction, not search) +- Revenue or funding supports the planned headcount growth +- The founder is genuinely willing to relinquish control -- not merely claiming to be +- At least 10 people on the team, with plans to grow beyond 30 within 12-18 months + +--- + +## The Sequence + +### Step 1: Balanced Scorecard -- Measure What Matters Beyond Revenue + +Revenue growth masks structural decay. Before scaling anything, establish a measurement framework that captures the full picture: financial health, customer satisfaction, internal process efficiency, and organizational learning capacity. This becomes the dashboard against which every subsequent step is evaluated. + +**Checkpoint:** A functioning scorecard with at least three leading indicators per perspective, reviewed weekly. + +### Step 2: Hackman Enabling Conditions -- Design Teams That Scale + +Scaling means teams, not headcount. Apply Hackman's five conditions (real team, compelling direction, enabling structure, supportive context, expert coaching) to design each functional group. The output determines how many teams you need, how they are composed, and what authority they carry. + +**Checkpoint:** Team architecture documented. Each team has a defined boundary, a compelling purpose, and the structural conditions to self-manage. + +### Step 3: Organisational Culture -- Codify Before It Dilutes + +Culture at ten people is implicit. Culture at fifty must be explicit. This step forces articulation of the values, norms, and behavioral expectations that define the organization. The work is harder than it sounds -- it requires distinguishing between aspirational platitudes and the actual lived culture, then deciding what to keep, what to change, and what to enshrine. + +**Checkpoint:** Culture document drafted, reviewed with the existing team, and pressure-tested against real hiring and firing decisions. + +--- + +### Decision Point: Is the Founder the Bottleneck? + +Pause here. Evaluate honestly: does every significant decision still route through the founder? Do people wait for the founder's input before acting? If the answer is yes, **prioritize Steps 4 and 7 immediately** before continuing with Steps 5 and 6. A scaling organization cannot be built on top of a single point of failure. The delegation and role evolution work must happen first, or the team structures and process improvements designed in subsequent steps will remain theoretical. + +If the founder has already begun distributing authority effectively, proceed sequentially through Steps 4-7. + +--- + +### Step 4: Delegation and Empowerment -- Let Go to Grow + +Map every recurring decision the founder currently makes. Categorize by reversibility and impact. Build an explicit delegation matrix that specifies who owns what, at what authority level, and with what accountability mechanism. The founder retains only the truly irreversible, high-stakes decisions. + +**Checkpoint:** Delegation matrix published. At least 60% of recurring decisions moved to team leads with clear authority. + +### Step 5: Leadership Pipeline -- Build the Next Layer + +Identify the individuals who will carry the organization through its next phase. Assess current leaders against future requirements -- the skills needed to manage five people differ substantially from those needed to manage twenty. Design development paths that close the gaps, and accept that some current leaders may not scale with the organization. + +**Checkpoint:** Leadership pipeline document with identified candidates, development plans, and a realistic timeline for readiness. + +### Step 6: Kaizen and BPR -- Systematize the Chaos + +Audit every critical process: hiring, onboarding, customer delivery, product development, financial operations. Identify which processes are documented, which exist only as tribal knowledge, and which do not exist at all. Apply continuous improvement principles to the functional processes and business process re-engineering to the broken or absent ones. + +**Checkpoint:** Top ten processes documented, owners assigned, improvement cadence established. + +### Step 7: Senior Leadership Transition -- Evolve the Founder's Role + +The founder who built the company is not necessarily the operator who should run it at scale. This step confronts the founder's evolving role directly: what should the CEO be doing at fifty people that differs from what they did at ten? The output is not a succession plan (unless needed) but a role evolution plan -- shifting from tactical execution to strategic leadership, external representation, and culture stewardship. + +**Checkpoint:** Written CEO role definition for the next phase, with explicit activities to stop, start, and continue. + +--- + +## Final Deliverable + +Upon completing all seven steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Quarterly Strategic Review | `quarterly-strategic-review` | Board, leadership team | +| Culture and Values Document | `culture-values-document` | Entire organization | +| Scaling Action Plan | `action-plan` | Leadership team | +| CEO Role Evolution Brief | `ceo-succession-brief` | Founder, board, advisors | + +## Common Pitfalls + +- **Scaling headcount before scaling systems.** Hiring ahead of process maturity creates expensive chaos. Every new hire amplifies existing dysfunction. +- **Codifying culture as aspirational fiction.** Writing values that describe who you wish you were rather than who you are produces cynicism, not alignment. +- **Delegating without authority.** Assigning responsibility without decision-making power is delegation theatre. It frustrates capable people and changes nothing. +- **Treating this as a one-time project.** Scaling is continuous. The measurement system from Step 1 exists precisely to make this an ongoing discipline rather than a quarterly panic. + +## Adaptation Notes + +- **Hardware or manufacturing startups** should weight Step 6 (process systematization) more heavily, as physical operations tolerate improvisation far less than software. +- **Remote-first organizations** need to invest disproportionately in Step 3 (culture codification) since implicit cultural transmission through physical proximity is unavailable. +- **Technical founders** often find Step 4 (delegation) the most difficult. Pair it with executive coaching if the founder struggles to release technical decision-making authority. +- **Venture-backed companies** facing board pressure to scale quickly should still resist the urge to skip Steps 1-3. Measurement, structure, and culture are the foundation -- not the luxury. diff --git a/plugins/foreman/content/playbooks/strategy-reset-playbook.md b/plugins/foreman/content/playbooks/strategy-reset-playbook.md new file mode 100644 index 0000000..7b250e3 --- /dev/null +++ b/plugins/foreman/content/playbooks/strategy-reset-playbook.md @@ -0,0 +1,148 @@ +--- +name: "strategy-reset-playbook" +description: "Guides founders through a complete strategic rebuild when the existing strategy has eroded, become incoherent, or been overtaken by market shifts. Chains environmental analysis, industry assessment, scenario development, differentiation design, business model reconstruction, and organizational alignment into a disciplined sequence. Use when the company has lost strategic direction and incremental fixes will not suffice." +version: "1.0.0" +category: "playbooks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +trigger_diagnostics: + - strategic-drift-diagnosis +steps: + - skill: "swot-pest-analysis" + purpose: "Produce an unflinching assessment of where the company actually stands — not where it wishes it stood" + output: "Integrated SWOT-PEST matrix revealing structural weaknesses, macro headwinds, and latent opportunities" + - skill: "porters-five-forces" + purpose: "Map the competitive terrain so the new strategy accounts for forces the old one ignored" + output: "Five-forces analysis with scoring and a clear picture of industry profitability drivers" + - skill: "scenario-planning" + purpose: "Construct three plausible futures to ensure the rebuilt strategy is robust, not merely optimistic" + output: "Three scenario narratives — optimistic, baseline, and adverse — with trigger indicators for each" + - skill: "blue-ocean-strategy" + purpose: "Identify the differentiation opportunity that justifies a strategic reset rather than incremental repair" + output: "Strategy canvas with eliminate-reduce-raise-create grid and a value innovation hypothesis" + - skill: "business-model-canvas" + purpose: "Translate the chosen strategic direction into a coherent, testable business model" + output: "Revised Business Model Canvas with explicit assumptions and a 90-day validation plan" + - skill: "balanced-scorecard" + purpose: "Convert the new strategy into measurable objectives across financial, customer, process, and learning perspectives" + output: "Balanced scorecard with KPIs, targets, and initiative owners for the first two quarters" + - skill: "strategic-thinking-and-alignment" + purpose: "Align the organization around the rebuilt strategy so execution matches intent" + output: "Strategic alignment plan with communication cadence, cascade structure, and accountability mechanisms" +final_outputs: + - quarterly-strategic-review + - strategic-analysis-one-pager + - action-plan +estimated_duration: "8-15 hours across 2-4 weeks" +author: "Fatih Guner" +--- + +# Strategy Reset Playbook + +Most companies do not lose their strategy in a single dramatic failure. They lose it gradually — one opportunistic project at a time, one unexamined market shift at a time, one quarter of "we'll figure it out later" at a time. By the time the founder admits the strategy is gone, the organization has been operating without one for months. The team has compensated with individual heroics and local optimization, but the coherence that once connected product decisions to market positioning to resource allocation has quietly dissolved. + +--- + +## When to Use This Playbook + +- The leadership team cannot articulate the company's strategy in a single paragraph +- Strategic priorities change quarterly without clear rationale +- Resources scatter across competing initiatives with no unifying logic +- The original strategy was sound but the market has shifted beneath it +- Board members or investors are asking "what is the strategy?" with increasing frequency +- The company is growing but the growth feels accidental rather than directed + +## Prerequisites + +- Founder commitment to a multi-week process — strategic resets cannot be done in an afternoon +- Willingness to confront uncomfortable truths about competitive position and internal capabilities +- Access to market data, competitive intelligence, and honest customer feedback +- At least one senior team member who will challenge the founder's assumptions throughout + +--- + +## The Sequence + +### Step 1: SWOT-PEST Analysis — Honest Assessment of Current Position + +Before building anything new, demolish the comfortable fictions. This step produces a rigorous inventory of internal strengths and weaknesses alongside an external scan of political, economic, social, and technological forces. The TOWS matrix then generates strategic options by crossing internal realities with external conditions. The value lies not in the framework itself but in the discipline of honesty it demands. + +**Checkpoint:** The analysis must contain at least two findings that make the leadership team uncomfortable. If it does not, the assessment lacks candour. + +### Step 2: Porter's Five Forces — Understand Industry Dynamics + +A strategy built in ignorance of competitive structure is a strategy built on sand. Map supplier power, buyer power, rivalry intensity, substitution threats, and new entrant barriers. Pay particular attention to forces that have shifted since the original strategy was formulated — the changes you missed are likely the reason the old strategy failed. + +**Checkpoint:** Each force scored with supporting evidence. The analysis reveals at least one structural dynamic the company has been ignoring. + +### Step 3: Scenario Planning — Envision Three Possible Futures + +Construct three distinct scenarios for the next 18-36 months. These are not variations on a theme — they represent genuinely different market structures, competitive landscapes, and customer behaviours. For each scenario, articulate what the company would need to be true to succeed, and what early indicators would signal that scenario is materializing. + +**Checkpoint:** Scenarios are specific enough to be falsifiable. Each contains named trigger indicators that can be monitored quarterly. + +--- + +### Decision Point: Which Future Do You Bet On? + +This is the fulcrum of the entire playbook. The three scenarios from Step 3 present divergent futures, and the strategy you rebuild in Steps 4-7 must be calibrated to one of them — with hedges for the others. + +- **If one scenario dominates in probability:** Build the primary strategy around it, with contingency triggers for the alternatives. +- **If two scenarios are roughly equiprobable:** Design a strategy robust enough to succeed in both, accepting that this means sacrificing some upside optimization. +- **If all three scenarios are plausible and contradictory:** Focus on building strategic optionality — invest in capabilities that pay off across multiple futures rather than betting on a single outcome. + +Document the bet explicitly. Write down which scenario you are optimizing for and why. This decision shapes every step that follows, and the organization deserves to know the reasoning behind it. + +--- + +### Step 4: Blue Ocean Strategy — Find the Differentiation Opportunity + +With the competitive landscape mapped and the target scenario selected, identify where uncontested market space exists. Apply the strategy canvas to visualize how current competitors invest their attention, then design the eliminate-reduce-raise-create grid that defines your differentiated position. The goal is not incremental improvement but a value innovation that makes the old competitive frame irrelevant. + +**Checkpoint:** The strategy canvas shows clear divergence from competitors. The value innovation hypothesis is specific enough to test within 60 days. + +### Step 5: Business Model Canvas — Design the New Model + +Translate the strategic direction into operational specifics. Every block of the canvas must reflect the new strategy — value propositions aligned with the blue ocean opportunity, customer segments selected based on scenario analysis, channels and revenue streams consistent with the competitive position. Compare the new canvas side-by-side with the old one. The differences tell the story of the reset. + +**Checkpoint:** At least three canvas blocks have changed substantively. Each change carries an explicit assumption that can be validated. + +### Step 6: Balanced Scorecard — Translate Strategy into Measurable Objectives + +A strategy without metrics is a wish. Build a scorecard that translates the new direction into specific, measurable objectives across four perspectives: financial outcomes, customer value delivery, internal process excellence, and organizational learning. Each objective carries a KPI, a target, a timeline, and an owner. This scorecard becomes the governance mechanism that prevents the next round of strategic drift. + +**Checkpoint:** Every strategic objective has a leading indicator (not just a lagging one). The scorecard can be reviewed in a 30-minute weekly meeting. + +### Step 7: Strategic Thinking and Alignment — Align the Organization + +The best strategy in the world fails if the organization does not understand, believe, and execute it. This step designs the cascade: how the strategy translates into team-level objectives, how progress is communicated, how conflicts between the new direction and legacy commitments are resolved. Alignment is not a one-time announcement — it is a continuous discipline. + +**Checkpoint:** Every team can articulate how their work connects to the new strategy. Conflicts between legacy projects and the new direction have been explicitly resolved. + +--- + +## Final Deliverable + +| Output | Template | Audience | +|--------|----------|----------| +| Quarterly Strategic Review | `quarterly-strategic-review` | Board, leadership team | +| Strategic Analysis One-Pager | `strategic-analysis-one-pager` | Investors, advisors | +| Execution Action Plan | `action-plan` | Leadership team, all-hands | + +## Common Pitfalls + +1. **Treating the reset as a branding exercise.** Changing the mission statement and website copy without changing resource allocation, customer segments, or competitive positioning is theatre, not strategy. +2. **Rushing past Step 3.** Scenario planning feels speculative to action-oriented founders. Skipping it produces a strategy optimized for a single future — which is precisely how the last strategy failed. +3. **Building the strategy in the founder's head.** A strategy that exists only in one person's mind is not a strategy — it is a secret. The alignment step exists because shared understanding is a prerequisite for coordinated execution. +4. **Ignoring the decision point.** Refusing to choose a scenario and trying to optimize for all three simultaneously produces a strategy that is mediocre in every future rather than excellent in one. +5. **Confusing strategic reset with organizational restructuring.** This playbook rebuilds the strategy. If the problem is structural — wrong people, wrong roles, wrong reporting lines — address that separately. + +## Adaptation Notes + +- **Early-traction stage:** The reset may reveal that the company never had a strategy — only a product and a hope. That is a valid finding. Start the canvas from scratch rather than revising one that never existed. +- **Growth stage:** Strategic drift often accelerates during growth because revenue masks incoherence. The scorecard from Step 6 is disproportionately important here — it prevents the next drift. +- **Scale stage:** Resets at scale involve hundreds of people and legacy commitments. Step 7 (alignment) may take longer than all other steps combined. Budget accordingly. +- **Bootstrapped companies** should weight the scenario analysis toward cash-flow sustainability. The luxury of strategic optionality requires the runway to fund it. diff --git a/plugins/foreman/content/playbooks/team-rebuild-playbook.md b/plugins/foreman/content/playbooks/team-rebuild-playbook.md new file mode 100644 index 0000000..e9c0eae --- /dev/null +++ b/plugins/foreman/content/playbooks/team-rebuild-playbook.md @@ -0,0 +1,146 @@ +--- +name: "team-rebuild-playbook" +description: "Guides founders through rebuilding a broken or dysfunctional team -- whether the problem is high turnover, toxic dynamics, trust collapse, or starting from scratch after a reset. Provides a structured path from diagnosis through team design, trust restoration, and alignment on shared objectives. Use when experiencing chronic turnover, interpersonal conflict, post-layoff morale collapse, or building a new team from the ground up." +version: "1.0.0" +category: "playbooks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +trigger_diagnostics: + - team-dysfunction-diagnosis + - hiring-diagnosis + - culture-erosion-diagnosis +steps: + - skill: "belbin-team-roles" + purpose: "Audit the current team composition to identify which functional roles are present, missing, or over-represented" + output: "Team role audit showing distribution, gaps, and redundancies across Belbin's nine roles" + - skill: "psychological-safety" + purpose: "Establish the foundational condition for trust -- the ability to speak honestly without fear of punishment" + output: "Psychological safety assessment with specific interventions to raise safety levels" + - skill: "tuckman-team-stages" + purpose: "Understand where the team currently sits in its developmental arc and what it needs to progress" + output: "Stage assessment with targeted actions to move the team toward performing" + - skill: "hackman-enabling-conditions" + purpose: "Set the structural conditions that allow teams to succeed regardless of individual personalities" + output: "Enabling conditions audit with gaps identified and structural changes recommended" + - skill: "giving-feedback" + purpose: "Establish a feedback culture from day one so that problems surface early rather than fester" + output: "Feedback framework with norms, cadence, and practical methods for the team" + - skill: "smart-goals" + purpose: "Align the rebuilt team on shared objectives that are concrete, measurable, and time-bound" + output: "Goal set for the team's first 90 days with clear ownership and success criteria" +final_outputs: + - team-health-check + - hiring-scorecard + - culture-values-document + - action-plan +estimated_duration: "6-12 hours across 2-4 weeks" +author: "Fatih Guner" +--- + +# Team Rebuild Playbook + +A broken team is not a people problem disguised as a business problem. It is a business problem, full stop. When trust has collapsed, when the best people are leaving, when meetings produce silence instead of ideas -- revenue follows culture downward, always. The instinct is to hire replacements and hope fresh faces fix stale dynamics. They will not. New people imported into a broken system become part of the broken system, typically within their first quarter. Rebuilding a team requires dismantling and reconstructing the conditions under which people work, not merely swapping the people. + +--- + +## When to Use This Playbook + +- Turnover exceeds 25% annually and exit interviews reveal cultural or leadership causes +- A key departure (or series of departures) has left the team structurally incomplete +- Interpersonal conflict is consuming management attention and reducing output +- A layoff, restructuring, or leadership change has shattered team trust +- The founder is building a team from scratch and wants to avoid the common mistakes +- Performance has declined without a clear operational or market explanation + +## Prerequisites + +- Honest assessment of whether the founder or leadership is part of the problem (if yes, this playbook still applies -- but self-awareness is non-negotiable) +- Commitment to completing the full sequence rather than cherry-picking comfortable steps +- Willingness to make personnel decisions if the diagnosis points to specific individuals +- Protected time for the team to engage in the process without it being squeezed into margins + +--- + +## The Sequence + +### Step 1: Belbin Team Roles -- Audit the Current Composition + +Before fixing dynamics, understand the structural reality. Map every team member against Belbin's nine roles: who are the natural coordinators, the shapers, the implementers, the creative plants? A team overloaded with ideas people and missing finishers will produce different dysfunction than one with all executors and no strategic thinkers. The audit reveals whether the problem is compositional, interpersonal, or both. + +**Checkpoint:** Role map completed. Gaps and over-concentrations identified. If rebuilding from scratch, this becomes the blueprint for hiring. + +### Step 2: Psychological Safety -- Build the Foundation for Trust + +Nothing else in this playbook works without this. Psychological safety -- the shared belief that the team is safe for interpersonal risk-taking -- is the single strongest predictor of team effectiveness, above individual talent, resources, or strategy. Assess the current level honestly: can people disagree with leadership without consequences? Can someone admit a mistake without career risk? If the answer is no, the remaining steps will produce compliance, not genuine teamwork. + +**Checkpoint:** Safety assessment completed. At least three concrete interventions initiated (leader vulnerability, response to failure, explicit norm-setting). + +--- + +### Decision Point: People or System? + +This is the critical diagnostic question. The first two steps should reveal whether the dysfunction originates from **specific individuals** (toxic behavior, values misalignment, persistent underperformance) or from **systemic conditions** (poor structure, unclear roles, absent feedback mechanisms, leadership failures). + +**If specific individuals are the problem:** Address the personnel issue directly before proceeding. No amount of structural improvement compensates for a toxic team member whose behavior undermines psychological safety. This may mean difficult conversations, performance management, or separation. Do this before Step 3. + +**If the system is the problem:** Proceed sequentially through Steps 3-6. The individuals are likely capable -- they are operating in conditions that prevent them from performing. + +In many cases, the answer is both. Handle the personnel issues first, then rebuild the system for the remaining and incoming team members. + +--- + +### Step 3: Tuckman Team Stages -- Locate the Team on the Development Arc + +Every team moves through forming, storming, norming, and performing -- and most rebuilt teams are back at forming whether they acknowledge it or not. A team that recently lost members, gained new ones, or survived a crisis should not be treated as a mature unit. Identify the current stage honestly, design interventions appropriate to that stage, and resist the temptation to rush through storming. Conflict handled well at this stage builds the foundation for performing later. + +**Checkpoint:** Stage identified with consensus from the team. Development plan aligned to the specific needs of that stage. + +### Step 4: Hackman Enabling Conditions -- Set Structural Foundations + +Individual goodwill cannot compensate for structural deficiency. Apply Hackman's five conditions: is this a real team with clear boundaries? Does it have a compelling direction? Is the structure enabling (right size, right skills, clear norms)? Is the organizational context supportive (resources, information, rewards)? Is there access to expert coaching? Address every gap. These conditions are the architecture within which culture forms. + +**Checkpoint:** All five conditions assessed. Structural changes implemented or scheduled with owners and deadlines. + +### Step 5: Giving Feedback -- Establish the Communication Culture + +Broken teams almost always have broken feedback loops. Either feedback does not exist (problems fester in silence), or it exists only as criticism (people learn to hide mistakes). Establish the norms, methods, and cadence for constructive feedback from day one of the rebuild. This includes upward feedback to leadership -- if people cannot tell the founder what is not working, the rebuild will stall. + +**Checkpoint:** Feedback norms documented and practiced. At least one round of structured feedback completed with the team. + +### Step 6: SMART Goals -- Align on Shared Objectives + +A rebuilt team needs a shared win. Define goals for the first 90 days that are specific, measurable, achievable, relevant, and time-bound. The goals should be team goals, not individual targets -- the purpose is to rebuild the experience of collective accomplishment. Choose objectives that are ambitious enough to require genuine collaboration but achievable enough to restore confidence. + +**Checkpoint:** Goal set published. Every team member can articulate the team's objectives and their individual contribution to them. + +--- + +## Final Deliverable + +Upon completing all six steps, compile the following outputs: + +| Output | Template | Audience | +|--------|----------|----------| +| Team Health Check | `team-health-check` | Founder, leadership team | +| Hiring Scorecard | `hiring-scorecard` | Hiring managers (if rebuilding) | +| Culture and Values Document | `culture-values-document` | Entire team | +| Team Rebuild Action Plan | `action-plan` | Leadership team | + +## Common Pitfalls + +- **Skipping the diagnosis.** Jumping to team-building exercises without understanding the root cause is organizational theatre. It feels productive and changes nothing. +- **Tolerating toxic individuals for their output.** One high-performing person who destroys psychological safety costs more than their output generates. The math is never close. +- **Declaring the rebuild complete too early.** Trust rebuilds slowly. A good week does not mean the team is fixed. Sustain the process for the full duration. +- **Treating team-building as separate from real work.** The rebuild should happen through the work, not alongside it. Offsites and workshops supplement; they do not substitute. + +## Adaptation Notes + +- **Post-layoff teams** require disproportionate investment in Step 2 (psychological safety). Survivor guilt and job insecurity suppress honest communication -- address this directly before proceeding. +- **Founding teams** (co-founders) experiencing conflict should prioritize the decision point honestly. Co-founder breakups are among the most common startup killers, and this playbook cannot fix fundamental values misalignment between founders. +- **Remote teams** need more explicit structure in Steps 4 and 5. Physical distance amplifies ambiguity -- compensate with over-communication of norms, roles, and feedback mechanisms. +- **Rapidly growing teams** absorbing many new hires simultaneously should run Steps 1-3 as a recurring cycle, not a one-time exercise. Every significant hiring wave resets the team's developmental stage. diff --git a/plugins/foreman/content/plugin-commands/abort.md b/plugins/foreman/content/plugin-commands/abort.md new file mode 100644 index 0000000..e129724 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/abort.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /abort command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /abort + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/about.md b/plugins/foreman/content/plugin-commands/about.md new file mode 100644 index 0000000..b4b0ca3 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/about.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /about command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /about + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /about with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/apply.md b/plugins/foreman/content/plugin-commands/apply.md new file mode 100644 index 0000000..b2188f1 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/apply.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /apply command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /apply + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /apply with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/back.md b/plugins/foreman/content/plugin-commands/back.md new file mode 100644 index 0000000..2b72f40 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/back.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /back command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /back + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /back with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/blockers.md b/plugins/foreman/content/plugin-commands/blockers.md new file mode 100644 index 0000000..973b241 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/blockers.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /blockers command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /blockers + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /blockers with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/check-in.md b/plugins/foreman/content/plugin-commands/check-in.md new file mode 100644 index 0000000..fa733dc --- /dev/null +++ b/plugins/foreman/content/plugin-commands/check-in.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /check-in command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /check-in + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /check-in with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/coalition.md b/plugins/foreman/content/plugin-commands/coalition.md new file mode 100644 index 0000000..b04b479 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/coalition.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /coalition command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /coalition + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /coalition with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/compare.md b/plugins/foreman/content/plugin-commands/compare.md new file mode 100644 index 0000000..73b14ab --- /dev/null +++ b/plugins/foreman/content/plugin-commands/compare.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /compare command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /compare + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /compare with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/decisions.md b/plugins/foreman/content/plugin-commands/decisions.md new file mode 100644 index 0000000..716060c --- /dev/null +++ b/plugins/foreman/content/plugin-commands/decisions.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /decisions command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /decisions + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /decisions with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/diagnose.md b/plugins/foreman/content/plugin-commands/diagnose.md new file mode 100644 index 0000000..23c9293 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/diagnose.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /diagnose command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnose + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /diagnose with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +Before answering, apply the diagnostic first-response contract: label the cause unconfirmed until comparable measurements distinguish the branches. Nonzero acquisition does not establish healthy acquisition. Ask for a revenue bridge before locating a revenue loss; do not invent metric targets. Check every causal sentence against an observed fact. diff --git a/plugins/foreman/content/plugin-commands/diagnostics.md b/plugins/foreman/content/plugin-commands/diagnostics.md new file mode 100644 index 0000000..bd5eb3a --- /dev/null +++ b/plugins/foreman/content/plugin-commands/diagnostics.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /diagnostics command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /diagnostics + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /diagnostics with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/export.md b/plugins/foreman/content/plugin-commands/export.md new file mode 100644 index 0000000..4169553 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/export.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /export command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /export + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /export with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/feedback.md b/plugins/foreman/content/plugin-commands/feedback.md new file mode 100644 index 0000000..6169412 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/feedback.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /feedback command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /feedback + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /feedback with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/follow-ups.md b/plugins/foreman/content/plugin-commands/follow-ups.md new file mode 100644 index 0000000..b6463ec --- /dev/null +++ b/plugins/foreman/content/plugin-commands/follow-ups.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /follow-ups command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /follow-ups + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /follow-ups with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-context.md b/plugins/foreman/content/plugin-commands/foreman-context.md new file mode 100644 index 0000000..c59b193 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-context.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /context command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /context + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /context with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-help.md b/plugins/foreman/content/plugin-commands/foreman-help.md new file mode 100644 index 0000000..9b9eb8c --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-help.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /help command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /help + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /help with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-reset.md b/plugins/foreman/content/plugin-commands/foreman-reset.md new file mode 100644 index 0000000..7e9012c --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-reset.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /reset command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /reset + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /reset with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-resume.md b/plugins/foreman/content/plugin-commands/foreman-resume.md new file mode 100644 index 0000000..a086051 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-resume.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resume command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resume + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /resume with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-run.md b/plugins/foreman/content/plugin-commands/foreman-run.md new file mode 100644 index 0000000..3c45394 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-run.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /run command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /run + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /run with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-skill.md b/plugins/foreman/content/plugin-commands/foreman-skill.md new file mode 100644 index 0000000..2e46c07 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-skill.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skill command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skill + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /skill with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/foreman-status.md b/plugins/foreman/content/plugin-commands/foreman-status.md new file mode 100644 index 0000000..51fb64b --- /dev/null +++ b/plugins/foreman/content/plugin-commands/foreman-status.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /status command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /status + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /status with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/forget.md b/plugins/foreman/content/plugin-commands/forget.md new file mode 100644 index 0000000..b607c2b --- /dev/null +++ b/plugins/foreman/content/plugin-commands/forget.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /forget command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /forget + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /forget with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/format.md b/plugins/foreman/content/plugin-commands/format.md new file mode 100644 index 0000000..c42a169 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/format.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /format command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /format + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/output-commands.md and execute only /format with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/history.md b/plugins/foreman/content/plugin-commands/history.md new file mode 100644 index 0000000..e33a026 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/history.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /history command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /history + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /history with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/hooks.md b/plugins/foreman/content/plugin-commands/hooks.md new file mode 100644 index 0000000..147c988 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/hooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /hooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /hooks + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /hooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/language.md b/plugins/foreman/content/plugin-commands/language.md new file mode 100644 index 0000000..ee30ced --- /dev/null +++ b/plugins/foreman/content/plugin-commands/language.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /language command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /language + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/language-command.md and execute only /language with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/plugin-commands/output.md b/plugins/foreman/content/plugin-commands/output.md new file mode 100644 index 0000000..86d35b0 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/output.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /output command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /output + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/execution-commands.md and execute only /output with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/pause.md b/plugins/foreman/content/plugin-commands/pause.md new file mode 100644 index 0000000..4ca959d --- /dev/null +++ b/plugins/foreman/content/plugin-commands/pause.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /pause command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /pause + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /pause with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/playbooks.md b/plugins/foreman/content/plugin-commands/playbooks.md new file mode 100644 index 0000000..18ea3c3 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/playbooks.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /playbooks command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /playbooks + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /playbooks with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/power-map.md b/plugins/foreman/content/plugin-commands/power-map.md new file mode 100644 index 0000000..38f86a4 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/power-map.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /power-map command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /power-map + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /power-map with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/progress.md b/plugins/foreman/content/plugin-commands/progress.md new file mode 100644 index 0000000..a127e2a --- /dev/null +++ b/plugins/foreman/content/plugin-commands/progress.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /progress command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /progress + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /progress with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/research.md b/plugins/foreman/content/plugin-commands/research.md new file mode 100644 index 0000000..c7e7dd6 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/research.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /research command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /research + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/research-commands.md and execute only /research with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/resistance.md b/plugins/foreman/content/plugin-commands/resistance.md new file mode 100644 index 0000000..84a2037 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/resistance.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /resistance command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /resistance + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /resistance with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/search.md b/plugins/foreman/content/plugin-commands/search.md new file mode 100644 index 0000000..e0a71f2 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/search.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /search command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /search + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /search with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/sector.md b/plugins/foreman/content/plugin-commands/sector.md new file mode 100644 index 0000000..fba467c --- /dev/null +++ b/plugins/foreman/content/plugin-commands/sector.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /sector command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /sector + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /sector with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/simulate.md b/plugins/foreman/content/plugin-commands/simulate.md new file mode 100644 index 0000000..a7f9342 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/simulate.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /simulate command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /simulate + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/simulation-commands.md and execute only /simulate with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/skills.md b/plugins/foreman/content/plugin-commands/skills.md new file mode 100644 index 0000000..fba111f --- /dev/null +++ b/plugins/foreman/content/plugin-commands/skills.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skills command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skills + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /skills with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/skip.md b/plugins/foreman/content/plugin-commands/skip.md new file mode 100644 index 0000000..b08e73f --- /dev/null +++ b/plugins/foreman/content/plugin-commands/skip.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /skip command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /skip + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/playbook-commands.md and execute only /skip with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/solo.md b/plugins/foreman/content/plugin-commands/solo.md new file mode 100644 index 0000000..4cfe328 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/solo.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /solo command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /solo + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/solo-command.md and execute only /solo with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/plugin-commands/stage.md b/plugins/foreman/content/plugin-commands/stage.md new file mode 100644 index 0000000..5d836f2 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/stage.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stage command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stage + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /stage with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/stakeholders.md b/plugins/foreman/content/plugin-commands/stakeholders.md new file mode 100644 index 0000000..41a015d --- /dev/null +++ b/plugins/foreman/content/plugin-commands/stakeholders.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /stakeholders command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stakeholders + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/org-politics-commands.md and execute only /stakeholders with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/stoic.md b/plugins/foreman/content/plugin-commands/stoic.md new file mode 100644 index 0000000..6246c8f --- /dev/null +++ b/plugins/foreman/content/plugin-commands/stoic.md @@ -0,0 +1,15 @@ +--- +description: "Foreman /stoic command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /stoic + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/stoic-command.md and execute only /stoic with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. + +For a mode or language change, use the profile command in RUNTIME.md directly. A directory listing or a full catalog read is unnecessary. Read the returned profile to confirm the write, then answer briefly. diff --git a/plugins/foreman/content/plugin-commands/templates.md b/plugins/foreman/content/plugin-commands/templates.md new file mode 100644 index 0000000..46ad057 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/templates.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /templates command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /templates + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/navigation-commands.md and execute only /templates with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/track.md b/plugins/foreman/content/plugin-commands/track.md new file mode 100644 index 0000000..b473521 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/track.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /track command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /track + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/implementation-commands.md and execute only /track with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/update.md b/plugins/foreman/content/plugin-commands/update.md new file mode 100644 index 0000000..aa2ffb9 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/update.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /update command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /update + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/memory-commands.md and execute only /update with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/plugin-commands/version.md b/plugins/foreman/content/plugin-commands/version.md new file mode 100644 index 0000000..4d49ef2 --- /dev/null +++ b/plugins/foreman/content/plugin-commands/version.md @@ -0,0 +1,13 @@ +--- +description: "Foreman /version command" +generated: true +argument-hint: "[arguments]" +--- + +# Foreman /version + +Read ${CLAUDE_PLUGIN_ROOT}/.claude/RUNTIME.md and ${CLAUDE_PLUGIN_ROOT}/.claude/policies/advisory.md first. Then read ${CLAUDE_PLUGIN_ROOT}/.claude/commands/meta-commands.md and execute only /version with the user's arguments: $ARGUMENTS. + +Use ${CLAUDE_PLUGIN_ROOT}/.claude/catalog.json to resolve exact content names before aliases or unique matches. Load all required supporting files from ${CLAUDE_PLUGIN_ROOT}/.claude. All paths in the source instructions are relative to this content directory. Persist confirmed changes through the runtime described in RUNTIME.md; never claim a write succeeded without reading its result. + +Other Foreman commands use /foreman:COMMAND (for example /foreman:apply); built-in name conflicts use foreman- prefixes. Use the command map in catalog.json to recommend only registered commands. diff --git a/plugins/foreman/content/policies/advisory.md b/plugins/foreman/content/policies/advisory.md new file mode 100644 index 0000000..af96c11 --- /dev/null +++ b/plugins/foreman/content/policies/advisory.md @@ -0,0 +1,19 @@ +# Advisory rules + +Apply these rules before any diagnostic, framework, playbook or simulation. + +For an initial advisory answer, distinguish the facts supplied by the founder from open hypotheses, ask the question that would most change the next decision, and offer one bounded action with a review point. Keep the whole response in the requested language, including the preamble. Before sending, remove every unsupported causal claim, invented target and unmeasured promise of saved time. + +- Separate observed facts, hypotheses and recommendations. Name missing measurements. A symptom alone is not a confirmed root cause. +- New customers still arriving does not rule out an acquisition problem. Compare acquisition volume and quality, conversion, retention, expansion and pricing over the same period before attributing flat or falling revenue. +- Ask a small number of questions that would change the next decision. Start with the most consequential unknown; do not require a full questionnaire before helping. +- Give actions with a rationale, assumptions, an owner, a measurable outcome and a review point. Present numerical examples as illustrative unless they come from the user's verified data. +- Match fundraising evidence to the funding stage. Do not require mature revenue or unit economics for every founder seeking capital. +- Assess reversibility from actual commitments and dependencies. Do not dismiss a founder's concern as irrational or prescribe a fixed multi-month experiment without checking capacity and runway. +- When a formula is needed, preserve all its components and define the period. The revenue bridge includes expansion as well as new revenue, contraction and churn. +- Before recommending that a founder stop advertising, freeze product work, change prices or cut staff, establish the relevant constraints, cash runway, dependencies and evidence. Prefer a bounded reversible experiment when uncertainty is high. +- Solo mode uses the founder's actual capacity and resources. Do not invent a team, board, investor mandate or delegation capacity. Stoic mode adds perspective without overriding evidence or the user's priorities. +- Use the saved output language for both questions and recommendations. Keep catalog identifiers unchanged. +- Recommend commands and content that exist in the supplied catalog. Treat examples in source documents as illustrations, not evidence that tools ran or state was saved. +- Read actual saved state before claiming recall or progress. Confirm a write only after the runtime succeeds. If persistence is unavailable, say the preference applies to this conversation and do not claim it will survive a new session. +- In simulations, distinguish the fictional persona's challenge from factual conclusions about the business. Finish the requested rounds before scoring, unless the user asks to stop. diff --git a/plugins/foreman/content/research/_schema/research-template.yaml b/plugins/foreman/content/research/_schema/research-template.yaml new file mode 100644 index 0000000..eadeaad --- /dev/null +++ b/plugins/foreman/content/research/_schema/research-template.yaml @@ -0,0 +1,99 @@ +# Research Template Schema — Template for All Research Guides +# +# A research template is a STRUCTURED GUIDE that teaches entrepreneurs how +# to gather the specific data required by Foreman's skills, diagnostics, +# and output templates. It does not perform research — it provides the +# protocol, data sources, collection templates, and interpretation frameworks +# so the entrepreneur can execute rigorous research independently. +# +# Directory structure: +# .claude/research/ +# _schema/ +# research-template.yaml <-- This file +# {research-template-name}.md <-- Individual research guides +# +# Integration: +# Research templates sit UPSTREAM of skills and playbooks. They produce +# the raw data that skills consume. The flow is: +# Research Template (gather data) -> Skill (apply framework) -> Output Template (present results) +# +# Design principles: +# 1. Teach, don't do — provide the protocol, not the answers. +# 2. Source-specific — name real databases, tools, and URLs. +# 3. Quality-aware — include reliability checks for every data type. +# 4. Action-oriented — every template ends with a clear output that +# feeds directly into named Foreman skills or templates. +# 5. "Good enough" conscious — research is a means, not an end. +# Every template defines when to stop collecting and start acting. + +# ═══════════════════════════════════════════════════════════════ +# FRONTMATTER SCHEMA +# ═══════════════════════════════════════════════════════════════ + +frontmatter: + name: "" # Kebab-case identifier (e.g., "market-sizing-worksheet") + description: "" # What research this template guides and when to use it. Max 512 chars. + research_type: "" # "market" | "competitor" | "customer" | "financial" | "technical" | "regulatory" + feeds_into_skills: [] # Skill names (kebab-case) this research feeds + feeds_into_templates: [] # Output template names this research feeds + estimated_time: "" # Human-readable range (e.g., "4-8 hours") + data_sources: [] # Array of primary data source names used in this template + author: "" # Contributor attribution + +# ═══════════════════════════════════════════════════════════════ +# BODY SECTIONS (Markdown, in order) +# ═══════════════════════════════════════════════════════════════ + +body_sections: + + - section: "Purpose" + required: true + guidance: > + Why this research matters. Frame in terms of decisions it enables, + not academic completeness. Two to three paragraphs maximum. + + - section: "What You'll Learn" + required: true + guidance: > + Bulleted list of specific outputs the entrepreneur will have after + completing this research. Each item should be concrete and testable. + + - section: "Data Sources" + required: true + guidance: > + Table with columns: Source Name | What It Provides | Free/Paid | URL or Access Pattern. + Minimum 6 sources. Prefer free sources first, paid sources with free tiers second. + + - section: "Research Protocol" + required: true + guidance: > + Numbered step-by-step procedure. Each step includes what to do, + what to record, and what signals indicate you have enough data. + Steps should be sequenced so earlier steps inform later ones. + + - section: "Data Collection Template" + required: true + guidance: > + Fill-in tables, matrices, or forms the entrepreneur completes + during research. Markdown table format. Include example rows + where helpful. + + - section: "Interpretation Guide" + required: true + guidance: > + How to read the data once collected. What patterns to look for, + what constitutes a strong vs. weak signal, and how to synthesize + across multiple data points. + + - section: "Common Pitfalls" + required: true + guidance: > + Minimum 4 pitfalls. Each with the mistake, why it happens, + and how to avoid it. Research-specific, not generic advice. + + - section: "Output" + required: true + guidance: > + How to package research results for use in Foreman. Name the + specific skills and templates this research feeds. Describe the + handoff format — what data goes where. diff --git a/plugins/foreman/content/research/brand-perception-research.md b/plugins/foreman/content/research/brand-perception-research.md new file mode 100644 index 0000000..bdb2aa3 --- /dev/null +++ b/plugins/foreman/content/research/brand-perception-research.md @@ -0,0 +1,147 @@ +--- +name: "brand-perception-research" +description: "Guides entrepreneurs through researching how their brand is + perceived by customers, prospects, and the broader market. Covers awareness + measurement, association mapping, competitive perception comparison, social + listening, and gap analysis between desired and actual positioning." +research_type: "customer" +feeds_into_skills: + - four-ps-marketing + - blue-ocean-strategy + - tipping-point +feeds_into_templates: + - market-opportunity-summary +estimated_time: "8-14 hours" +data_sources: + - Typeform / SurveyMonkey + - Brandwatch / Mention / Sprout Social + - Google Trends + - G2 / Trustpilot + - Glassdoor +author: "Fatih Guner" +related_content: + - kind: playbook + ref: personal-brand-playbook +--- + +# Brand Perception Research + +What you intend your brand to mean and what the market believes it means are frequently two different things. Founders operate inside their own positioning narrative -- the vision, the differentiation, the carefully chosen adjectives on the homepage. Customers form perceptions from fragments: a demo call, a support interaction, a competitor's comparison page, a friend's offhand remark. This distinction matters commercially, not aesthetically. Misaligned brand perception distorts conversion rates, increases churn when onboarding reveals a gap between promise and reality, and erodes pricing power when the market positions you as a commodity you believe you have transcended. + +--- + +## What You'll Learn + +- Current brand awareness levels: who recognises your name, and in what context +- Brand associations: the words, feelings, and attributes people connect to you +- Competitive perception positioning: how you rank against alternatives on key attributes +- Social sentiment patterns and employer brand perception +- A gap analysis between desired positioning and actual market perception + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Typeform / SurveyMonkey | Custom perception surveys with branching logic | Freemium | typeform.com / surveymonkey.com | +| Brandwatch / Mention / Sprout Social | Social listening: mentions, sentiment, share of voice, engagement | Paid | brandwatch.com / mention.com / sproutsocial.com | +| Google Trends | Brand search volume over time, geographic distribution, related queries | Free | trends.google.com | +| G2 / Trustpilot | Customer reviews with sentiment, category rankings, competitive comparisons | Free | g2.com / trustpilot.com | +| Glassdoor | Employee reviews, employer ratings, culture perception, leadership sentiment | Free | glassdoor.com | +| Twitter/X / LinkedIn / Reddit | Organic mentions, sentiment, community conversation | Free | Native search or social listening tools | +| SparkToro | Audience overlap, where your brand's audience engages | Freemium | sparktoro.com | + +--- + +## Research Protocol + +**Step 1 -- Define Desired Positioning** +Before measuring perception, articulate what you want to be known for: (a) primary attribute, (b) emotional tone, (c) competitive distinction. These three statements become the benchmark against which you measure reality. If you cannot state desired positioning in three sentences, the market has no chance of receiving it clearly. + +**Step 2 -- Measure Current Awareness** +Survey 100+ respondents from your target market (not existing customers). Test unaided recall and aided recall. The ratio reveals whether your brand has penetrated beyond your customer base. + +**Step 3 -- Map Current Associations** +Ask 50+ respondents: "When you hear [company name], what comes to mind?" Code responses into functional, emotional, category, and negative themes. Frequency quantifies your actual brand territory. + +**Step 4 -- Run Competitive Perception Comparison** +Select 3-5 positioning attributes that matter in your category. Survey customers and prospects, rating your brand and 2-3 competitors on each attribute (1-7 scale). This reveals where the competitive perception gap is widest. + +**Step 5 -- Social Listening Analysis** +Collect 30 days of brand mentions across Twitter/X, LinkedIn, and Reddit. Categorise by sentiment and topic. Calculate share of voice against competitors. Social listening captures unfiltered perception that surveys polish away. + +**Step 6 -- Gap Analysis** +Place desired positioning alongside actual perception data. The gap analysis produces three categories: aligned (market sees what you intend), misaligned (market sees something different), and invisible (no one in the category owns it). + +**Step 7 -- Establish Tracking Cadence** +Run the full protocol at baseline, then repeat quantitative components quarterly. Meaningful repositioning requires 6-12 months to register in perception data. + +--- + +## Data Collection Template + +### Awareness Metrics + +| Metric | Current | Target | +|--------|---------|--------| +| Unaided recall (%) | % | % | +| Aided recall (%) | % | % | +| Brand search volume (Google Trends) | | | +| Share of voice (%) | % | % | + +### Association Map + +| Theme | Frequency | Sentiment | Desired? | +|-------|----------|-----------|----------| +| | | Pos / Neu / Neg | Y / N | +| | | Pos / Neu / Neg | Y / N | + +### Competitive Perception Matrix (1-7 scale) + +| Attribute | Your Brand | Comp A | Comp B | Comp C | +|-----------|-----------|--------|--------|--------| +| [Attribute 1] | | | | | +| [Attribute 2] | | | | | +| [Attribute 3] | | | | | + +### Social Listening Summary (30-day window) + +| Metric | Your Brand | Comp A | Comp B | +|--------|-----------|--------|--------| +| Total mentions | | | | +| Positive / Neutral / Negative (%) | | | | +| Top positive theme | | | | +| Top negative theme | | | | + +--- + +## Interpretation Guide + +**High aided recall, low unaided recall -- awareness without salience.** People recognise your name when prompted but do not think of you spontaneously. The fix is sharper positioning, not more volume. + +**Associations cluster around a single attribute -- narrow brand.** If 70% of mentions cite "easy to use" and nothing else, your brand occupies a thin perception slice. Powerful if that attribute drives purchase decisions; fragile if a competitor matches it. + +**Competitors own the attribute you claim -- uphill repositioning.** When a rival rates higher on your intended differentiator, either invest heavily to overtake their association or pivot to an attribute where you can credibly lead. + +**Negative sentiment concentrates on one topic -- containable.** If 80% of negative mentions reference a single issue, fixing it addresses most perception drag. Diffuse negativity across many topics is harder to remediate. + +--- + +## Common Pitfalls + +- **Surveying only existing customers.** Your customers already chose you -- their perception skews positive. Include prospects, lapsed users, and people who have never heard of you. +- **Confusing awareness with perception.** A widely known brand can be widely known for the wrong reasons. Measure what people associate with the name, not just whether they recognise it. +- **Ignoring employer brand.** Glassdoor is public. A 2.8-star employer rating undermines premium positioning regardless of product quality. +- **Running perception research once.** Brand perception is a lagging indicator. A single measurement establishes a baseline but cannot detect change. Quarterly tracking is the minimum. +- **Reacting to individual mentions.** One negative tweet is an anecdote; a recurring theme across 30 mentions is data. Aggregate before acting. + +--- + +## Output + +Package your brand perception research for use in the following Foreman skills and templates: + +- **Skills**: `four-ps-marketing` (perception feeds positioning and messaging), `blue-ocean-strategy` (perception matrix maps to Strategy Canvas), `personal-brand-playbook` (founder associations), `tipping-point` (share of voice and amplification channels) + +Transfer awareness metrics, association map, perception matrix, and gap analysis. Flag the largest gap between desired and actual positioning -- this becomes the primary brand strategy objective. diff --git a/plugins/foreman/content/research/churn-analysis-guide.md b/plugins/foreman/content/research/churn-analysis-guide.md new file mode 100644 index 0000000..c377286 --- /dev/null +++ b/plugins/foreman/content/research/churn-analysis-guide.md @@ -0,0 +1,152 @@ +--- +name: "churn-analysis-guide" +description: "Guides entrepreneurs through researching and diagnosing customer + churn — calculating accurate churn metrics, building cohort retention curves, + running exit surveys, correlating usage data with attrition, and synthesizing + findings into actionable churn drivers." +research_type: "customer" +feeds_into_skills: + - net-promoter-score +feeds_into_templates: + - unit-economics-snapshot +estimated_time: "8-16 hours" +data_sources: + - Amplitude + - Mixpanel + - Stripe + - Chargebee + - Salesforce + - Zendesk + - Intercom + - Delighted +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: customer-churn-diagnosis + - kind: diagnostic + ref: revenue-diagnosis + - kind: playbook + ref: pricing-strategy-playbook + - kind: template + ref: unit-economics-snapshot +--- + +# Churn Analysis Guide + +Acquisition gets the headlines; retention determines the outcome. A SaaS company growing 10% monthly with 5% monthly churn is running on a treadmill -- each new cohort evaporates faster than the next one arrives. Yet most founders can cite their CAC to two decimal places while unable to state their net revenue retention with confidence. The asymmetry is dangerous: acquisition costs are visible on the P&L, while churn erodes the denominator quietly until unit economics collapse. This guide provides the research protocol for understanding not merely that customers leave, but why they leave, when the decision crystallises, and what signals predict departure before the cancellation event. + +--- + +## What You'll Learn + +- Accurate churn metrics: logo churn, revenue churn, and net revenue retention +- Cohort retention curves segmented by signup month, plan, and acquisition source +- Exit survey findings identifying top reasons customers leave +- Usage-to-churn correlations revealing which behaviours predict attrition +- A prioritised list of the top 3 churn drivers with evidence strength ratings + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Amplitude / Mixpanel / Heap | Feature usage frequency, session depth, activation events, engagement trends | Paid (free tiers) | amplitude.com / mixpanel.com / heap.io | +| Stripe / Chargebee / Recurly | MRR movements: new, expansion, contraction, churn; cohort-level revenue | Paid (included with billing) | stripe.com / chargebee.com | +| Salesforce / HubSpot | Churn reason codes, customer health scores, renewal pipeline data | Paid | salesforce.com / hubspot.com | +| Zendesk / Intercom | Support ticket volume and categories, complaint patterns, CSAT per ticket | Paid | zendesk.com / intercom.com | +| Exit survey (Typeform / SurveyMonkey) | Self-reported churn reasons, satisfaction at cancellation, win-back signals | Paid (free tiers) | typeform.com / surveymonkey.com | +| Delighted / Wootric | NPS scores with open-text comments, detractor identification | Paid (free tiers) | delighted.com / wootric.com | +| Google Analytics / PostHog | Session behaviour, funnel drop-off, engagement decline patterns | Freemium | analytics.google.com / posthog.com | + +--- + +## Research Protocol + +**Step 1 -- Calculate Churn Rates Accurately** +Compute three metrics from your billing system. Logo churn: customers lost divided by starting count. Gross revenue churn: MRR lost divided by starting MRR. Net revenue retention: starting MRR plus expansion minus losses, divided by starting MRR. Report all three; never cite one in isolation. + +**Step 2 -- Build Cohort Retention Curves** +Group customers by signup month and track what percentage remain active at month 1, 2, 3, 6, and 12. Healthy products show curves that flatten into a retained base. Products in trouble show curves that never flatten. Segment further by plan tier, acquisition channel, and persona. + +**Step 3 -- Segment Churn by Dimension** +Break churn into sub-populations: by plan, persona, acquisition source, and tenure (first 90 days vs post-90 days). The aggregate number masks the signal. You may discover that one segment drives the headline rate -- and addressing it alone halves the problem. + +**Step 4 -- Run Exit Surveys** +Deploy a 5-7 question survey at cancellation. Target 30+ responses. Core questions: reason for leaving, alternative chosen, what would have prevented it, and willingness to return. Keep under 2 minutes; incentivise if response rates fall below 20%. + +**Step 5 -- Correlate Usage Data with Churn** +Compare analytics for churned vs retained customers over the 30 days preceding cancellation: login frequency, feature breadth, core action depth, support tickets. The 2-3 metrics that most sharply distinguish cohorts become early-warning indicators. + +**Step 6 -- Map NPS to Actual Churn** +Match NPS responses to subsequent retention outcomes. Calculate churn rates among promoters, passives, and detractors over 6 months. If detractors churn at 4x the rate of promoters, NPS becomes a reliable leading indicator. + +**Step 7 -- Synthesise the Top 3 Churn Drivers** +Triangulate exit surveys, usage correlations, NPS detractor comments, and support ticket patterns. A driver confirmed across three sources is actionable; one supported by a single source remains a hypothesis. Rank by impact and addressability. + +--- + +## Data Collection Template + +### Churn Metrics Dashboard + +| Metric | Current Month | Prior Month | 3-Month Average | Benchmark | +|--------|--------------|-------------|-----------------|-----------| +| Logo churn rate (monthly) | % | % | % | SaaS: 3-7% | +| Gross revenue churn (monthly) | % | % | % | SaaS: 1-3% | +| Net revenue retention (annual) | % | % | % | Best-in-class: >120% | + +### Cohort Retention Table + +| Cohort | Month 1 | Month 3 | Month 6 | Month 12 | +|--------|---------|---------|---------|----------| +| [Month A] | % | % | % | % | +| [Month B] | % | % | % | % | + +### Exit Survey Summary (n = ___) + +| Reason | % of Responses | Verbatim Theme | +|--------|---------------|----------------| +| | | | +| Alternative chosen | % moving to: ___ | | +| Would return if | ___% yes | Top condition: ___ | + +### Usage-to-Churn Correlation + +| Metric | Churned Avg (30d) | Retained Avg | Predictive? | +|--------|-------------------|-------------|-------------| +| Logins per week | | | Y / N | +| Core action frequency | | | Y / N | +| Support tickets filed | | | Y / N | + +--- + +## Interpretation Guide + +**Retention curve flattens above 40% at month 12 -- healthy.** The product has a retained core. Focus on expanding that base and improving early-lifecycle activation. + +**Retention curve never flattens -- product-market fit is incomplete.** Every cohort trending toward zero is a product problem, not a churn optimisation problem. Pause growth spending; fix the core experience. + +**One segment drives most churn -- targeted intervention.** When 60% of churn comes from a single plan or persona, fix that segment's experience, reposition away from it, or adjust pricing. + +**Exit surveys and usage data disagree -- trust behaviour.** Customers rationalise departure in surveys while usage data reveals the real story. When self-report and behavioural data conflict, behaviour is more reliable. + +--- + +## Common Pitfalls + +- **Conflating logo churn with revenue churn.** Losing 10 small accounts while expanding 2 enterprise accounts produces terrible logo churn but healthy revenue retention. Report both; act on what matters for your model. +- **Surveying too few churned customers.** Fewer than 30 responses produce anecdotes, not patterns. Extend the collection window rather than drawing conclusions from 8 responses. +- **Ignoring involuntary churn.** Failed credit cards account for 20-40% of SaaS churn. Separate voluntary from involuntary before diagnosing product problems. +- **Optimising retention before activation.** Customers who never reach the "aha moment" churn regardless. Fix activation first. +- **Treating churn as a single initiative.** Churn has multiple root causes. A project addressing one driver while ignoring others produces marginal improvement. + +--- + +## Output + +Package your churn analysis for use in the following Foreman skills and templates: + +- **Skills**: `customer-churn-diagnosis` (metrics and drivers feed the triage), `net-promoter-score` (NPS-to-churn mapping), `revenue-diagnosis` (gross churn and NRR), `pricing-strategy-playbook` (price sensitivity data), `unit-economics-snapshot` (churn rate feeds LTV) + +Transfer the churn dashboard, cohort table, exit survey synthesis, and usage correlations. Flag the most addressable churn driver -- this becomes the first intervention target. diff --git a/plugins/foreman/content/research/competitor-research-template.md b/plugins/foreman/content/research/competitor-research-template.md new file mode 100644 index 0000000..de7c1e0 --- /dev/null +++ b/plugins/foreman/content/research/competitor-research-template.md @@ -0,0 +1,193 @@ +--- +name: "competitor-research-template" +description: "Structured guide for gathering competitive intelligence — identifying competitors, mapping their positioning, analyzing strengths and weaknesses, and synthesizing patterns. Produces the raw data required for Porter's Five Forces, Blue Ocean Strategy, and competitive positioning work." +research_type: "competitor" +feeds_into_skills: + - porters-five-forces + - blue-ocean-strategy + - swot-pest-analysis +feeds_into_templates: + - competitive-landscape-brief +estimated_time: "8-16 hours" +data_sources: + - Crunchbase + - LinkedIn + - G2 + - Capterra + - SimilarWeb + - SEMrush + - Glassdoor + - ProductHunt + - App stores + - Patent databases +author: "Fatih Guner" +--- + +# Competitor Research Template + +The most dangerous competitor is the one you have not identified. Most founders monitor the two or three companies that look like them — same features, same pitch, same target customer. They miss the adjacent player approaching from a different angle, the incumbent adding a feature, and the non-consumption alternative where customers simply do nothing. Competitive intelligence is not surveillance. It is the systematic mapping of the landscape your customer navigates when deciding whether to choose you, choose someone else, or choose nothing at all. + +Rigorous competitor research precedes every strategic framework that references competition: Porter's Five Forces requires it, Blue Ocean Strategy depends on it, and SWOT without it is fiction. + +--- + +## What You'll Learn + +- A comprehensive list of direct, indirect, potential, and substitute competitors +- A structured profile of each competitor's offering, pricing, traction, and positioning +- A feature comparison matrix that reveals gaps and clusters +- A positioning map that visualizes competitive space and opportunity +- Pattern-level insights about market structure and strategic openings + +--- + +## Competitor Identification + +**Direct competitors:** Companies solving the same problem for the same customer with a similar approach. Search your product category on G2, Capterra, ProductHunt, and app stores. Query Crunchbase with industry and funding filters. + +**Indirect competitors:** Companies solving the same problem but with a different approach or technology. Search for the *problem* rather than the *product category*. Ask potential customers: "How do you handle [problem] today?" + +**Potential competitors:** Companies not currently in your market that could enter easily — adjacent products, well-funded startups pivoting, or incumbents with distribution advantages. Monitor funding announcements and product launches in adjacent categories. + +**Substitutes:** Non-software alternatives including manual processes, spreadsheets, consultants, or inaction. Interview potential customers to discover these. The most overlooked competitor is "do nothing." + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Crunchbase | Funding, team size, investors, founding date, company description | Freemium | crunchbase.com | +| LinkedIn | Employee count, hiring patterns, team composition, growth signals | Free (limited) | linkedin.com | +| G2 / Capterra | User reviews, ratings, feature comparisons, pricing tiers | Free | g2.com / capterra.com | +| SimilarWeb | Website traffic estimates, traffic sources, geography | Freemium | similarweb.com | +| SEMrush / Ahrefs | SEO keywords, paid ad spend, content strategy signals | Paid (free trials) | semrush.com | +| Glassdoor | Employee reviews, salary data, company culture signals | Free | glassdoor.com | +| ProductHunt | Launch history, upvotes, founder engagement, user sentiment | Free | producthunt.com | +| App Stores (iOS/Android) | Ratings, download estimates, update frequency, feature changelog | Free | App Store / Google Play | +| USPTO / Google Patents | Patent filings revealing R&D direction and defensibility | Free | patents.google.com | +| Press / PR databases | Announcements, partnerships, customer wins, pivots | Free | Google News, TechCrunch, PR Newswire | +| Social media | Customer complaints, feature requests, sentiment | Free | Twitter/X, Reddit, industry forums | +| Job postings | Roles reveal strategy — hiring ML engineers signals AI pivot | Free | LinkedIn Jobs, company career pages | + +--- + +## Research Protocol + +**Step 1 — Build the Initial List** +Identify 8-12 companies across all four types (direct, indirect, potential, substitute). Cast a wide net. You will narrow to 5-8 for deep analysis in the next step. + +**Step 2 — Profile Each Competitor** +For each company, fill in the competitor matrix (below). Spend 30-60 minutes per competitor. Use the data sources table above — no single source tells the full story. + +**Step 3 — Build the Feature Comparison Matrix** +List the 10-15 features or capabilities most relevant to your target customer. Score each competitor (has it / partially has it / does not have it). Include yourself. Gaps in this matrix are either opportunities or warnings. + +**Step 4 — Construct a Positioning Map** +Choose two axes that matter most to your target customer — not features, but positioning dimensions. Common pairs: price vs. complexity, horizontal vs. vertical, self-serve vs. enterprise, breadth vs. depth. Plot each competitor as a point. Where do clusters form? Where is empty space? + +**Step 5 — Assess Strengths and Weaknesses** +For each competitor in your top 5, identify 2-3 genuine strengths and 2-3 genuine weaknesses. Source these from user reviews (G2, Capterra, app stores), employee reviews (Glassdoor), and observable behavior (pricing changes, feature gaps, slow release cadence). + +**Step 6 — Synthesize Patterns** +Step back and look at the landscape as a whole. What patterns emerge? Where is the market heading? What are competitors collectively ignoring? + +--- + +## Data Collection Template + +### Competitor Matrix + +| Dimension | Comp. 1 | Comp. 2 | Comp. 3 | Comp. 4 | Comp. 5 | +|-----------|---------|---------|---------|---------|---------| +| Company name | | | | | | +| Type (direct/indirect/potential/substitute) | | | | | | +| Founded | | | | | | +| Headquarters | | | | | | +| Total funding | | | | | | +| Employee count | | | | | | +| Estimated revenue | | | | | | +| Target segment | | | | | | +| Core product | | | | | | +| Pricing model | | | | | | +| Price range | | | | | | +| Key differentiator | | | | | | +| Distribution channel | | | | | | +| Monthly web traffic (est.) | | | | | | +| G2/Capterra rating | | | | | | +| Key strength | | | | | | +| Key weakness | | | | | | + +### Feature Comparison Matrix + +| Feature / Capability | Your Product | Comp. 1 | Comp. 2 | Comp. 3 | Comp. 4 | Comp. 5 | +|---------------------|-------------|---------|---------|---------|---------|---------| +| [Feature 1] | | | | | | | +| [Feature 2] | | | | | | | +| [Feature 3] | | | | | | | +| [Feature 4] | | | | | | | +| [Feature 5] | | | | | | | +| ... | | | | | | | + +Score: Y = full support, P = partial support, N = not available + +### Positioning Map Template + +Choose your axes based on what drives customer choice in your market: + +``` +Axis suggestions (pick two): + X-axis options: Price, Complexity, Breadth of features, Technical depth + Y-axis options: Target company size, Customizability, Self-serve vs. sales-led, Vertical vs. horizontal + + High [Y-axis label] + | + | [Comp A] + | + | [Comp B] [You?] + | + | [Comp C] + | + Low |________________________________ + Low High + [X-axis label] +``` + +Mark clusters, empty quadrants, and your intended position. + +--- + +## Interpretation Guide + +**Clustering signals commodity dynamics.** When most competitors occupy the same quadrant on your positioning map, the market has converged on a standard approach. Competing here requires superior execution or lower cost. The strategic alternative is to move to an unoccupied quadrant — but only if customers exist there. + +**An empty quadrant is either an opportunity or a graveyard.** Before celebrating an unoccupied position, ask why it is empty. Sometimes nobody serves that quadrant because nobody wants to be there. Validate with customer interviews before building for a white space. + +**One dominant player changes everything.** If a single competitor holds 60%+ market share, frontal assault is expensive. Consider a flanking strategy: a different segment, a different distribution model, or a different value proposition that avoids the incumbent's strength. + +**Funding patterns reveal market timing.** Heavy recent funding in your space means investors believe the timing is right — but competition for customers will intensify. No recent funding may mean the market is too early, too small, or already captured. + +**Job postings decode strategy.** A competitor suddenly hiring machine learning engineers signals an AI pivot. A surge in enterprise sales hires means an upmarket move. Job postings are the most underused competitive intelligence source. + +--- + +## Common Pitfalls + +- **Only tracking direct competitors.** The company that disrupts you is unlikely to look like you. Amazon did not look like a bookstore chain. Track indirect competitors and substitutes with equal diligence. +- **Ignoring non-consumption.** If your potential customer's alternative is a spreadsheet, a consultant, or doing nothing, that is your real competition — and it shapes your go-to-market strategy more than any funded startup. +- **Confusing features with positioning.** A feature matrix tells you what competitors *do*. Positioning analysis tells you how they *compete*. Two products with identical features can occupy completely different positions based on pricing, branding, and target segment. +- **One-time research.** Competitive landscapes shift quarterly. Set a calendar reminder to refresh your competitor matrix every 90 days. Flag new entrants, funding events, and major product changes. +- **Assuming competitor weakness is your opportunity.** A competitor's weakness only matters if their customers care about it. Validate through customer interviews before building features that exploit perceived gaps. + +--- + +## Output + +Package your competitive intelligence for use in the following Foreman skills and templates: + +- **porters-five-forces** — The competitor matrix feeds "Rivalry Among Existing Competitors." Substitute identification feeds "Threat of Substitutes." Funding and entry barrier analysis feeds "Threat of New Entrants." +- **blue-ocean-strategy** — The feature comparison matrix maps directly to the Strategy Canvas. Cluster analysis reveals red oceans; empty quadrants suggest blue ocean potential. +- **swot-pest-analysis** — Competitor strengths become your threats; competitor weaknesses become your opportunities. Market-level patterns feed the external analysis. +- **competitive-landscape-brief** — The full competitor matrix, positioning map, and pattern synthesis transfer directly into this investor-facing document. + +Transfer the competitor matrix, feature comparison, positioning map, and pattern synthesis. Flag which competitors represent the greatest strategic risk — and why. diff --git a/plugins/foreman/content/research/content-strategy-research.md b/plugins/foreman/content/research/content-strategy-research.md new file mode 100644 index 0000000..cfbf340 --- /dev/null +++ b/plugins/foreman/content/research/content-strategy-research.md @@ -0,0 +1,145 @@ +--- +name: "content-strategy-research" +description: "Guides entrepreneurs through researching content strategy — + keyword and topic research, competitor content audits, channel selection, + format testing, and measurement frameworks. Produces a data-informed 90-day + content calendar and distribution plan." +research_type: "market" +feeds_into_skills: + - four-ps-marketing + - tipping-point + - storytelling-for-leaders +feeds_into_templates: + - market-opportunity-summary +estimated_time: "8-14 hours" +data_sources: + - Google Search Console + - Ahrefs + - SEMrush + - BuzzSumo + - SparkToro + - YouTube Analytics + - LinkedIn Analytics + - Apple Podcasts +author: "Fatih Guner" +related_content: + - kind: playbook + ref: personal-brand-playbook +--- + +# Content Strategy Research + +Publishing without research is journaling. A founder who writes three blog posts a week without understanding search intent, audience distribution, or competitor gaps is manufacturing noise, not signal. Content strategy research answers three questions before a single word is drafted: what does your audience need to hear, where are they listening, and how will you know it worked? The difference between companies that build audiences and those that broadcast into silence is rarely talent or budget. It is the research that precedes the first published piece -- understanding which topics carry demand, which channels reach your buyers, and which formats earn attention in a saturated landscape. + +--- + +## What You'll Learn + +- A prioritized list of topics and keywords mapped to search intent and business value +- A competitive content audit revealing gaps you can exploit and formats that outperform +- A channel selection rationale based on audience behaviour data, not assumption +- A content format hypothesis ready for structured testing +- A 90-day content calendar grounded in research rather than editorial whim +- A measurement framework connecting content activity to business outcomes + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Google Search Console | Your existing search performance: queries, clicks, impressions, position | Free | search.google.com/search-console | +| Ahrefs / SEMrush / Ubersuggest | Keyword volume, difficulty, SERP analysis, content gap analysis | Paid (free tiers available) | ahrefs.com / semrush.com / ubersuggest.com | +| BuzzSumo | Most-shared content by topic, competitor content performance, trending formats | Paid (limited free) | buzzsumo.com | +| SparkToro | Audience research: where your audience reads, listens, watches, and follows | Freemium | sparktoro.com | +| YouTube Analytics / Search | Video topic demand, competitor channel performance, suggested keywords | Free | youtube.com (search suggest + competitor channels) | +| LinkedIn Analytics | Post performance, follower demographics, content engagement patterns | Free (for company pages) | linkedin.com | +| Podcast directories | Category rankings, review volume, episode frequency benchmarks | Free | Apple Podcasts / Spotify charts | +| Google Trends | Relative interest over time, seasonal patterns, geographic distribution | Free | trends.google.com | +| Reddit / Hacker News | Unfiltered audience questions, pain points, and language patterns | Free | reddit.com / hn.algolia.com | + +--- + +## Research Protocol + +**Step 1 -- Define the Audience Persona** +Before researching topics, define who you are creating for. Identify 1-2 specific personas: their role, seniority, industry, primary challenges, and where they consume professional content. Use SparkToro to validate assumptions with data -- enter a competitor domain or relevant hashtag and examine the audience profile. A persona without behavioural data is a guess wearing a name tag. + +**Step 2 -- Keyword and Topic Research** +Generate 20-30 topics from three sources: (a) questions your sales or support team hears repeatedly, (b) keyword tools showing volume and difficulty, (c) Reddit/HN threads where your audience asks questions. Record monthly volume, difficulty, search intent, and business relevance (1-3). Prioritize moderate difficulty with high relevance. + +**Step 3 -- Competitor Content Audit** +Select 3-5 competitors or adjacent publications. For each, inventory their last 30 pieces: format, topic, estimated engagement (via BuzzSumo or Ahrefs), publishing frequency, and distribution channels. Identify crowded topics, neglected gaps, and formats earning disproportionate engagement. + +**Step 4 -- Channel Selection** +Using SparkToro data, competitor patterns, and resource constraints, select 2-3 channels maximum. For each, define publishing cadence and the metric that signals traction. Depth on two channels outperforms breadth on six. + +**Step 5 -- Content Format Testing** +Design a 30-day test comparing 2-3 formats on your primary channel. Hold topic constant, vary format. Measure engagement per format against a pre-defined threshold. + +**Step 6 -- Build the 90-Day Calendar** +Anchor each month around one pillar topic (high business relevance, moderate difficulty) supported by 3-4 related pieces. Interleave formats based on Step 5 findings. Leave 20% of slots flexible for reactive content. + +**Step 7 -- Set the Measurement Framework** +Define metrics at four levels: reach (traffic, impressions), engagement (time on page, shares), conversion (signups, demo requests), and attribution (which content touched customers who converted). Measure the portfolio, not individual articles. + +--- + +## Data Collection Template + +### Keyword / Topic Matrix + +| Topic | Monthly Volume | Difficulty (1-100) | Intent | Business Relevance (1-3) | Priority | +|-------|---------------|-------------------|--------|--------------------------|----------| +| | | | | | | +| | | | | | | +| | | | | | | + +### Competitor Content Audit + +| Competitor | Format | Top-Performing Topic | Est. Engagement | Frequency | Primary Channel | +|------------|--------|---------------------|-----------------|-----------|----------------| +| | | | | | | +| | | | | | | +| | | | | | | + +### Channel Selection Scorecard + +| Channel | Audience Present? | Competitor Saturation | Resource Cost | Traction Metric | Selected? | +|---------|------------------|----------------------|--------------|----------------|-----------| +| Blog/SEO | | | | | | +| LinkedIn | | | | | | +| YouTube | | | | | | + +--- + +## Interpretation Guide + +**High volume + low difficulty = tactical wins.** These keywords represent quick content opportunities. They build domain authority and traffic while you invest in harder, higher-value topics over time. + +**Competitor gap = your opening.** If no competitor covers a topic your audience searches for, you face an editorial vacuum. Fill it with definitive content and own the position before others notice. + +**Engagement concentration signals format preference.** When one format consistently outperforms others across competitors, it reflects audience behaviour, not competitor skill. Respect the data even when it contradicts your preference. + +**Attribution is imperfect -- accept it.** Content rarely converts on first touch. A prospect may read four blog posts over three months before requesting a demo. Measure assisted conversions and first-touch attribution alongside last-touch. Demanding perfect attribution from content is demanding certainty from a probabilistic channel. + +--- + +## Common Pitfalls + +- **Writing for yourself, not your audience.** Founders gravitate toward topics they find interesting. Your audience's questions, not your intellectual curiosity, should drive the calendar. Keyword data is the corrective. +- **Launching on five channels simultaneously.** Each channel has its own format norms, posting cadence, and feedback loop. Master one before adding another. Two channels done well outperform five done poorly. +- **Ignoring search intent.** A keyword with 10,000 monthly searches is worthless if the searcher wants a Wikipedia definition and you are selling enterprise software. Match content format to the intent behind the query. +- **Measuring vanity metrics alone.** Page views and social shares feel gratifying but mean nothing without downstream conversion data. Connect content to pipeline from the start, even if early numbers are small. +- **Abandoning the strategy after six weeks.** Content compounds. Most content strategies show meaningful results at 6-9 months. Pivoting every month based on early data guarantees you never reach compounding velocity. + +--- + +## Output + +Package your content strategy research for use in the following Foreman skills and templates: + +- **Skills**: `four-ps-marketing` (Promotion element: channel, messaging, distribution), `tipping-point` (audience clustering and amplification channels), `personal-brand-playbook` (topic authority and publishing cadence), `storytelling-for-leaders` (narrative structures that earn attention) +- **Templates**: `market-opportunity-summary` (audience data and channel selection rationale) + +Transfer the keyword matrix, competitor audit, channel scorecard, and 90-day calendar. Flag which topics carry the highest business relevance -- these become content priorities in the first 30 days. diff --git a/plugins/foreman/content/research/customer-interview-guide.md b/plugins/foreman/content/research/customer-interview-guide.md new file mode 100644 index 0000000..69e87ef --- /dev/null +++ b/plugins/foreman/content/research/customer-interview-guide.md @@ -0,0 +1,243 @@ +--- +name: "customer-interview-guide" +description: "Complete protocol for conducting customer and user research + interviews — from recruiting participants through synthesizing patterns. + Covers problem interviews, solution interviews, pricing interviews, and churn + interviews with a bank of non-leading questions and structured note-taking + templates." +research_type: "customer" +feeds_into_skills: + - business-model-canvas + - net-promoter-score + - four-ps-marketing +feeds_into_templates: + - market-opportunity-summary + - new-initiative-brief +estimated_time: "10-20 hours" +data_sources: + - Direct interviews + - User testing sessions + - Customer support tickets + - Online communities + - Social media listening +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis +--- + +# Customer Interview Guide + +Every failed startup is a monument to assumptions that were never tested. The Business Model Canvas has nine boxes, and at least six of them contain guesses until a founder has sat across from a real customer and listened — truly listened, without pitching, without leading, without defending. Customer interviews are the highest-leverage research activity available to an early-stage company. They cost nothing but time and ego. Yet most founders skip them, or worse, conduct them so poorly that the resulting data confirms whatever they already believed. + +The difference between useful and useless interviews is not the questions asked but the discipline with which they are asked. This guide provides that discipline. + +--- + +## What You'll Learn + +- Whether your target customers actually experience the problem you are solving +- How they currently handle the problem (and what they spend — in money, time, or frustration) +- Whether your proposed solution generates genuine interest or polite nodding +- Willingness-to-pay signals grounded in behavior, not hypothetical approval +- Patterns across interviews that reveal segment-level truths, not individual opinions + +--- + +## Interview Types + +**Problem Interviews** — Conducted before you build. The goal is to validate that the problem exists, that it is painful enough to motivate action, and that your target segment experiences it frequently. You are not selling; you are learning. + +**Solution Interviews** — Conducted once you have a concept, prototype, or MVP. The goal is to test whether your specific approach to the problem resonates. Show the solution, observe reactions, and probe for honest assessment. + +**Pricing Interviews** — Conducted when you have a working solution. The goal is to discover willingness to pay through behavioral cues and structured pricing exercises, not direct questions ("Would you pay $X?" yields unreliable answers). + +**Churn Interviews** — Conducted with customers who left or stopped using your product. The goal is to identify the actual reason for departure, which is rarely the reason stated in a cancellation form. + +--- + +## Recruiting Participants + +**How many:** 5-8 interviews per customer segment for pattern detection. After 5 interviews within a segment, you will hear the same themes repeating. After 8, you have statistical confidence in qualitative patterns. + +**Where to find them:** +- LinkedIn outreach (direct, honest, brief — "I'm researching [problem area], not selling") +- Industry communities and forums (Reddit, Slack groups, Discord servers, Facebook groups) +- Existing customer base (for solution/pricing/churn interviews) +- Referral chains ("Who else deals with this problem?") +- Conference attendees and meetup members +- Cold email to companies in your target segment (response rate: 5-15% with a good subject line) + +**Who NOT to interview:** +- Friends and family (they will tell you what you want to hear) +- People outside your target segment (their pain points are irrelevant to your thesis) +- Fellow entrepreneurs (they will give you advice instead of data) +- Anyone who stands to benefit from flattering you (potential co-founders, investors, employees) + +**Incentives:** For B2B, a genuine 30-minute conversation with someone interested in their problems is often sufficient. For B2C, a $25-50 gift card or equivalent is standard. Never incentivize with your product — it biases toward people who already want it. + +--- + +## Interview Protocol + +**Phase 1 — Context Setting (5 minutes)** +Thank them. Explain you are researching, not selling. Ask permission to take notes. Establish that honesty is more valuable than politeness. State there are no wrong answers. + +**Phase 2 — Current Behavior (10 minutes)** +Understand their world before introducing your topic. What does their day look like? What tools do they use? What frustrates them? Let them lead — you are mapping their reality. + +**Phase 3 — Problem Exploration (10 minutes)** +Narrow to the problem space. Probe for frequency, severity, and current coping mechanisms. Ask for specific recent examples. Quantify the cost of the problem in time, money, or missed opportunity. + +**Phase 4 — Solution Concept (10 minutes)** +For solution interviews only. Show or describe your approach. Watch their face before listening to their words. Ask what would need to be true for them to switch from their current approach. Probe for concerns and objections — these are gold. + +**Phase 5 — Willingness to Pay (5 minutes)** +Do not ask "Would you pay $X?" Instead, use these approaches: +- "What do you currently spend on handling this problem?" (anchors to real behavior) +- "If this existed, what budget would it come from?" (reveals organizational decision-making) +- "At what price would this be a no-brainer? At what price would you hesitate?" (Van Westendorp range) + +--- + +## Question Bank + +### Problem Interview Questions +1. "Tell me about the last time you dealt with [problem area]." +2. "Walk me through how you handle [process] today, step by step." +3. "What is the most frustrating part of [process/task]?" +4. "How often does [problem] come up? Daily? Weekly? Monthly?" +5. "What have you tried to solve this? What happened?" +6. "How much time do you spend on [problem] each week?" +7. "If you could wave a magic wand and fix one thing about [process], what would it be?" +8. "What does this problem cost you — in dollars, time, or missed opportunities?" +9. "Who else in your organization deals with this?" +10. "Have you actively looked for a solution? What did you find?" + +### Solution Interview Questions +11. "What is your first reaction to this?" (then silence — let them fill it) +12. "What part of this would be most useful to you?" +13. "What is missing?" +14. "What would make you nervous about using this?" +15. "How would this fit into your existing workflow?" +16. "What would have to be true for you to switch from your current approach?" +17. "Who else would need to approve this decision?" +18. "What would you compare this to?" +19. "If this disappeared tomorrow, what would you do instead?" +20. "On a scale of 1-10, how likely are you to try this? What would make it a 10?" + +### Pricing Interview Questions +21. "What do you currently pay for tools in this category?" +22. "What budget does this type of purchase come from?" +23. "At what price would this be an obvious yes?" +24. "At what price would you start to question whether it's worth it?" +25. "At what price would it feel too cheap — like something must be wrong?" +26. "Would you prefer to pay per month, per year, or per use?" +27. "What is the most you have ever paid for a tool like this?" + +### Churn Interview Questions +28. "What originally made you sign up?" +29. "Walk me through the moment you decided to stop using it." +30. "What are you using instead now?" +31. "Was there a single event that triggered the switch, or was it gradual?" +32. "What would have needed to change for you to stay?" +33. "If we fixed [the issue], would you consider coming back?" +34. "What did we get right?" + +--- + +## Note-Taking Template + +Complete one form per interview. Fill in during or immediately after — memory decays within hours. + +### Per-Interview Record + +| Field | Notes | +|-------|-------| +| Date | | +| Interviewee (role, company size, segment) | | +| Interview type (problem/solution/pricing/churn) | | +| **Key quotes** (verbatim, in their words) | | +| Top pain point mentioned | | +| Second pain point mentioned | | +| Current solution/workaround | | +| Money/time currently spent on problem | | +| Reaction to solution concept (if shown) | | +| Willingness-to-pay signal | | +| Biggest surprise or unexpected insight | | +| Objections or concerns raised | | +| Who else they suggested talking to | | +| Overall signal: strong problem / weak problem / no problem | | + +--- + +## Synthesis Template + +After completing 5+ interviews within a segment, fill in this cross-interview pattern matrix. + +### Pain Point Frequency + +| Pain Point | Interview 1 | Interview 2 | Interview 3 | Interview 4 | Interview 5 | Mentions | +|-----------|-------------|-------------|-------------|-------------|-------------|----------| +| [Pain point A] | | | | | | /5 | +| [Pain point B] | | | | | | /5 | +| [Pain point C] | | | | | | /5 | +| [Pain point D] | | | | | | /5 | + +Mark: S = strong signal, M = mentioned, X = not mentioned + +### Solution Reaction Summary + +| Aspect | Positive Reactions | Concerns | Neutral/No Reaction | +|--------|-------------------|----------|-------------------| +| Core feature 1 | | | | +| Core feature 2 | | | | +| Core feature 3 | | | | +| Pricing | | | | + +### Willingness-to-Pay Summary + +| Signal | Count | Typical Range | Notes | +|--------|-------|---------------|-------| +| "Would definitely pay" | /N | $ | | +| "Maybe / depends on..." | /N | $ | | +| "Probably not" | /N | $ | | +| Current spend on alternatives | /N | $ | | + +--- + +## Interpretation Guide + +**Pattern threshold:** A pain point mentioned by 4 out of 5 interviewees is a pattern. Mentioned by 2 out of 5 is an observation. Mentioned by 1 is an anecdote. Build on patterns, investigate observations, and set aside anecdotes. + +**Behavior over opinion:** "I would definitely use that" is an opinion. "I spent three hours last Tuesday building a spreadsheet to do this" is a behavior. Weight behaviors over opinions by a factor of ten. + +**Enthusiasm calibration:** Polite interest ("That's interesting") is not a buying signal. Genuine engagement looks like: asking when it will be ready, requesting to be a beta tester, introducing you to colleagues who have the same problem, or asking about pricing unprompted. + +**Negative data is the most valuable data.** If five interviews reveal that nobody has the problem you assumed, you have just saved six months of building the wrong thing. Treat disconfirmation as the prize, not the disappointment. + +**Segment divergence:** If interviewees in different segments give contradictory answers, your segments are real and distinct. This is useful information — it means you need to choose which segment to serve first. + +--- + +## Common Pitfalls + +- **Leading questions.** "Don't you think it would be great if..." is not a question. It is a pitch disguised as inquiry. Every question should be answerable with information that surprises you. +- **Confirmation bias.** You will unconsciously weight the interviews that support your thesis and discount those that challenge it. Counter this by writing down your hypothesis before the first interview, then explicitly tracking disconfirming evidence. +- **Talking more than listening.** The ideal ratio is 20% you, 80% them. If you catch yourself explaining your product for more than 60 seconds, stop and ask a question. +- **Interviewing the wrong people.** Talking to ten people outside your target segment produces noise, not signal. Define your target segment precisely before recruiting. +- **Not recording or noting.** Human memory is unreliable. Take notes during the interview (with permission) and write a summary within two hours. Without documentation, interviews collapse into vague impressions. +- **Stopping at positive signal.** Five enthusiastic interviews feel conclusive. They are not. Seek out the skeptics and the disinterested — they reveal the boundaries of your market. + +--- + +## Output + +Package your interview findings for use in the following Foreman skills and templates: + +- **business-model-canvas** — Pain points map to "Value Propositions." Current behavior maps to "Customer Relationships" and "Channels." Willingness-to-pay maps to "Revenue Streams." Segment characteristics map to "Customer Segments." +- **net-promoter-score** — Solution interview enthusiasm scores provide a pre-launch proxy for NPS. Churn interview data feeds NPS diagnostic work. +- **product-market-fit-diagnosis** — The synthesis template's pattern matrix is the primary input. Strong patterns across pain points + willingness-to-pay signals = product-market fit evidence. +- **four-ps-marketing** — Pricing signals feed the "Price" dimension directly. Customer language and pain point framing feed "Promotion." Channel preferences feed "Place." + +Transfer the synthesis template, key quotes (verbatim customer language is invaluable for marketing copy), and the willingness-to-pay summary. Flag the two or three findings that most challenge your original assumptions — these are the insights with the highest strategic value. diff --git a/plugins/foreman/content/research/data-collection-plan.md b/plugins/foreman/content/research/data-collection-plan.md new file mode 100644 index 0000000..86bb0a1 --- /dev/null +++ b/plugins/foreman/content/research/data-collection-plan.md @@ -0,0 +1,184 @@ +--- +name: "data-collection-plan" +description: "General-purpose template for structuring data needs before collection begins. Guides entrepreneurs through identifying what data answers their question, where it exists, how to collect it, how to assess its quality, and when they have enough to act." +research_type: "market" +feeds_into_skills: + - evaluating-and-deciding + - defining-and-exploring-problems +feeds_into_templates: [] +estimated_time: "2-4 hours (planning); varies (execution)" +data_sources: + - Primary research (interviews, surveys, experiments) + - Secondary research (reports, databases, filings) + - Observational data + - Public datasets +author: "Fatih Guner" +--- + +# Data Collection Plan + +Frameworks without data are elaborate guessing games. A Porter's Five Forces analysis built on intuition produces confident-sounding fiction. A pricing strategy without willingness-to-pay data is a coin flip dressed in spreadsheet clothing. Yet the failure mode is rarely a shortage of frameworks — it is a shortage of the data those frameworks require. This template exists at the boundary between intention and evidence: it forces you to articulate what you need to know, where that knowledge lives, and how you will acquire it before you spend a single hour collecting. + +The second failure mode is equally destructive: collecting data forever. Research feels productive. It has the texture of progress without the risk of action. This plan includes explicit stopping criteria to prevent analysis from becoming a substitute for decision-making. + +--- + +## What You'll Learn + +- A clear articulation of the specific questions your data must answer +- An inventory of data sources mapped to each question +- A collection timeline with milestones and responsibilities +- Quality criteria for evaluating whether your data is reliable enough to act on +- Explicit "good enough" thresholds that prevent research from becoming procrastination + +--- + +## The Plan Framework + +Every data collection effort answers six questions in sequence. Skipping any one of them leads to wasted effort or unreliable conclusions. + +**1. What question am I trying to answer?** +Not "I need market data" but "What is the annual spend on inventory management software by mid-market e-commerce companies in North America?" Precision in the question determines efficiency in the search. + +**2. What data would answer it?** +Define the ideal dataset — what fields, what granularity, what time period. Then define the minimum viable dataset — the least you need to make a confident-enough decision. + +**3. Where does that data exist?** +Map each data need to specific sources. Some data exists in public databases; some requires primary collection; some does not exist and must be estimated from proxies. + +**4. How will I collect it?** +Define the method for each source: download, API query, manual search, interview, survey, or observation. Estimate time per source. + +**5. How will I know if it's reliable?** +Every data point carries uncertainty. Define your reliability criteria before collecting, so you are not rationalizing quality after the fact. + +**6. When do I have "enough"?** +Define the stopping condition. What level of confidence in the answer permits you to move forward? Perfect data does not exist; sufficient data does. + +--- + +## Data Source Taxonomy + +### Primary Sources (You Collect It) + +| Method | Best For | Time Cost | Reliability | +|--------|----------|-----------|-------------| +| Customer interviews | Problem validation, willingness to pay, behavior patterns | 1-2 hours each | High (if conducted properly) | +| Surveys | Quantitative validation across larger samples | 4-8 hours to design and deploy | Medium (response bias) | +| Experiments / A/B tests | Testing specific hypotheses with real behavior | Days to weeks | High (behavioral data) | +| Observation | Understanding current workflows and pain points | 2-4 hours per observation | High (unfiltered reality) | +| Expert interviews | Industry dynamics, regulatory landscape, technical feasibility | 30-60 minutes each | Medium-High (single perspective) | + +### Secondary Sources (Someone Else Collected It) + +| Source Type | Examples | Best For | Reliability Concern | +|-------------|----------|----------|-------------------| +| Industry reports | Statista, IBISWorld, Gartner, Forrester | Market sizing, trends, benchmarks | Methodology opaque; may be dated | +| Public filings | SEC EDGAR, Companies House, annual reports | Revenue, strategy, risk factors | Reliable but lagging indicators | +| Government data | Census, BLS, Eurostat, trade databases | Demographic, economic, employment data | Reliable but aggregated | +| News and press | TechCrunch, industry publications, PR wires | Funding, launches, partnerships, pivots | Survivorship bias; positive spin | +| Academic research | Google Scholar, SSRN, university repositories | Validated frameworks, empirical findings | Rigorous but often dated | +| Competitor data | Crunchbase, SimilarWeb, G2, app stores | Competitive intelligence, traction signals | Estimates; directionally useful | +| Social and community | Reddit, Twitter/X, forums, review sites | Unfiltered customer sentiment | Self-selection bias | + +--- + +## Quality Assessment Checklist + +Before relying on any data source, evaluate it against these five criteria: + +| Criterion | Question to Ask | Red Flag | +|-----------|----------------|----------| +| Recency | When was this data collected or published? | More than 2 years old in a fast-moving market | +| Source credibility | Who produced this? What is their methodology? Do they have an incentive to skew results? | Vendor-produced "research" about their own market | +| Sample size | How many data points underlie this figure? | Market size from a survey of 50 respondents | +| Methodology | How was the data collected? Is the methodology described? | "Based on proprietary analysis" with no further detail | +| Bias indicators | Who funded the research? Who benefits from the conclusion? | Industry association claiming their sector is booming | + +**Rule of thumb:** No single source should carry your entire analysis. Triangulate every critical data point from at least two independent sources. When sources agree, confidence rises. When they disagree, the disagreement itself is informative — investigate it. + +--- + +## Data Collection Plan Template + +Fill one row per data need. Start from your questions, not from available sources. + +| # | Question to Answer | Data Needed | Source(s) | Collection Method | Timeline | Responsible | Quality Check | Status | +|---|-------------------|-------------|-----------|------------------|----------|-------------|---------------|--------| +| 1 | | | | | | | | Not started | +| 2 | | | | | | | | Not started | +| 3 | | | | | | | | Not started | +| 4 | | | | | | | | Not started | +| 5 | | | | | | | | Not started | + +Status values: Not started / In progress / Collected / Verified / Insufficient + +### Priority Matrix + +Not all data is equally urgent. Rank your data needs: + +| Priority | Data Need | Why This Priority | Deadline | +|----------|-----------|-------------------|----------| +| P1 — Blocks decisions | | | | +| P2 — Improves decisions | | | | +| P3 — Nice to have | | | | + +Collect P1 data first. Start P2 in parallel if resources allow. Defer P3 until P1 and P2 are complete or until a specific decision requires it. + +--- + +## "Good Enough" Criteria + +Research is a means to decisions, not an end in itself. Define your stopping conditions before you start collecting. + +**For market sizing:** Two independent approaches (top-down and bottom-up) that agree within 2-3x. You do not need exact numbers — you need the right order of magnitude. + +**For competitor analysis:** Deep profiles on 5-8 competitors with consistent data across all. You do not need every competitor — you need the ones that matter to your target customer's decision. + +**For customer validation:** 5-8 interviews per segment showing a clear pattern (4+ of 5 mentioning the same pain point). You do not need statistical significance — you need pattern recognition. + +**For pricing:** Willingness-to-pay signals from at least 10 potential customers, with a clustering around a price range. You do not need a precise price — you need a defensible range. + +**The diminishing returns test:** After each research session, ask: "Did I learn something that changes my plan?" If three consecutive sessions yield no new insight, you have enough. Act. + +--- + +## Integration with Foreman + +Research data feeds every layer of Foreman's system. Here is where each type of data goes: + +| Data Type | Feeds Into (Skills) | Feeds Into (Templates) | Feeds Into (Diagnostics) | +|-----------|-------------------|----------------------|------------------------| +| Market size | business-model-canvas, blue-ocean-strategy | fundraising-deck-outline, market-opportunity-summary | market-fit-diagnosis | +| Competitor intelligence | porters-five-forces, blue-ocean-strategy, swot-pest-analysis | competitive-landscape-brief | competitive-position-diagnosis | +| Customer interviews | business-model-canvas, net-promoter-score, four-ps-marketing | customer-discovery-summary | product-market-fit-diagnosis | +| Financial data | unit-economics, balanced-scorecard | unit-economics-snapshot, financial-model-summary | burn-rate-diagnosis | +| Technical feasibility | build-vs-buy, technology-stack-assessment | technical-architecture-brief | technical-debt-diagnosis | +| Regulatory landscape | porters-five-forces (barriers to entry) | regulatory-compliance-brief | market-entry-diagnosis | + +--- + +## Common Pitfalls + +- **Analysis paralysis.** Researching until certainty arrives — it never does. Every additional data point has declining marginal value. Set a time limit and honor it. The cost of delay often exceeds the cost of imperfect data. +- **Anchoring on first data found.** The first number you encounter becomes the reference point against which all subsequent data is judged. Counter this by recording the first figure alongside the search that produced it, then actively seeking contradictory data before forming a conclusion. +- **Confusing correlation with causation.** Two trends moving together does not mean one causes the other. Ice cream sales and drowning rates both rise in summer — selling ice cream does not cause drowning. Apply this standard to every market trend you observe. +- **Ignoring inconvenient data.** When a data point contradicts your thesis, the temptation is to question the data's quality. Sometimes the data is genuinely poor. But sometimes your thesis is wrong. Develop the discipline to treat disconfirming evidence with the same rigor as confirming evidence. +- **Over-investing in secondary research when primary data is available.** Reading ten industry reports about a customer segment is less informative than five conversations with actual customers. Secondary research frames the landscape; primary research reveals the truth within it. +- **No plan at all.** The most common pitfall. Founders open Google, search for an hour, find some numbers, and call it research. Without a structured plan, collection is haphazard, quality is unassessed, and gaps are invisible. + +--- + +## Output + +This template produces a structured data collection plan — not the data itself. The plan serves as a project management tool for research and a quality assurance framework for the data you gather. + +Once data is collected: + +- **For diagnostics:** Validated data replaces assumptions in diagnostic triage answers. A diagnostic answered with real data produces more accurate routing than one answered with guesses. +- **For playbooks:** Data-backed inputs at each playbook step yield outputs that reflect reality rather than aspiration. The playbook runner agent can reference specific data points in its guidance. +- **For skills:** Every framework in Foreman becomes sharper when fed with actual data. The skill executor agent should note where data is missing and recommend returning to this plan. +- **For evaluating-and-deciding:** Decision quality is bounded by data quality. This plan ensures the entrepreneur knows the confidence level of the data underlying each decision. +- **For defining-and-exploring-problems:** Problem definition without data is assumption. This plan structures the evidence-gathering that transforms a hunch into a validated problem statement. + +Revisit and update this plan as your venture progresses. Questions change as you move from idea to validation to traction. The plan is a living document, not a one-time exercise. diff --git a/plugins/foreman/content/research/due-diligence-research.md b/plugins/foreman/content/research/due-diligence-research.md new file mode 100644 index 0000000..0c7b532 --- /dev/null +++ b/plugins/foreman/content/research/due-diligence-research.md @@ -0,0 +1,141 @@ +--- +name: "due-diligence-research" +description: "Pre-fundraising due diligence preparation protocol. Guides + entrepreneurs through assembling the financial, legal, commercial, technical, + and HR documentation that investors will request -- before they ask for it." +research_type: "financial" +feeds_into_skills: [] +feeds_into_templates: + - due-diligence-checklist + - fundraising-deck-outline + - unit-economics-snapshot + - cap-table-summary +estimated_time: "20-40 hours" +data_sources: + - internal-accounting-systems + - crm-data + - analytics-platforms + - legal-counsel + - ip-registry + - cap-table-management-tools +author: "Fatih Guner" +related_content: + - kind: template + ref: due-diligence-checklist + - kind: playbook + ref: fundraising-playbook + - kind: template + ref: fundraising-deck-outline + - kind: template + ref: unit-economics-snapshot +--- + +# Due Diligence Research Guide + +## Purpose + +Investors do not reject companies during due diligence because the numbers are imperfect. They reject companies that cannot produce the numbers at all. This guide organises the full spectrum of documentation an institutional investor will request into a systematic preparation protocol. Complete it before your first partner meeting, and the diligence process becomes a demonstration of operational maturity rather than an exercise in damage control. + +## What You'll Learn + +- The five categories of due diligence and what each reveals to investors +- Exactly which documents to prepare and in what format +- How to identify and address red flags before investors discover them +- How to organise a virtual data room that signals professionalism +- The difference between "nice to have" and "deal-breaker" documentation gaps + +## Data Sources + +| Source | What It Provides | Access Method | +|--------|-----------------|---------------| +| Accounting system (QuickBooks, Xero) | P&L, balance sheet, cash flow, revenue breakdown | Export financial reports; generate 24-month trailing data | +| CRM (HubSpot, Salesforce) | Pipeline data, conversion rates, customer list, deal velocity | Export pipeline reports; segment by cohort | +| Analytics platform (Mixpanel, Amplitude, GA4) | Usage metrics, retention curves, engagement data | Export cohort analyses and key metric dashboards | +| Legal counsel | Corporate documents, contracts, IP assignments, compliance | Request organised file index from counsel | +| IP registry (USPTO, EPO) | Patent filings, trademark registrations | Search by company name and founder names | +| Cap table tool (Carta, Pulley, Captable.io) | Ownership structure, option pool, SAFE/convertible notes | Export fully diluted cap table and waterfall analysis | + +## Research Protocol + +### Category 1: Financial Due Diligence + +**What investors will ask**: Monthly P&L for 24 months, revenue by customer, burn rate trajectory, cash runway, unit economics by cohort, financial projections with assumptions. + +**Documents to prepare**: (a) Monthly income statements -- 24 months trailing, (b) Balance sheet -- current, (c) Cash flow statement -- 12 months trailing, (d) Revenue breakdown by customer, segment, and geography, (e) Accounts receivable aging report, (f) Three-year financial model with clearly labelled assumptions, (g) Bank statements -- 6 months. + +**Red flags to address proactively**: Revenue concentration (any customer >25% of revenue), declining gross margins, inconsistencies between reported and bank-verified revenue, missing months in the data trail, GAAP vs. cash accounting discrepancies. + +### Category 2: Legal Due Diligence + +**What investors will ask**: Certificate of incorporation, board minutes, all equity agreements, IP assignments, material contracts, pending litigation, regulatory compliance documentation. + +**Documents to prepare**: (a) Articles of incorporation and all amendments, (b) Bylaws, (c) Board meeting minutes and written consents, (d) All equity-related documents (SAFEs, convertible notes, stock purchase agreements, option grants), (e) IP assignment agreements for all founders and employees, (f) Material contracts (customer, vendor, partnership), (g) Employment agreements and offer letters, (h) Any litigation or threatened claims. + +**Red flags to address proactively**: Missing IP assignments (especially from pre-incorporation work), unsigned board consents, founder vesting that has already fully vested, outstanding convertible instruments with conflicting terms, expired or unsigned employment agreements. + +### Category 3: Commercial Due Diligence + +**What investors will ask**: Customer list with revenue and tenure, churn data by cohort, NPS or satisfaction metrics, pipeline composition, sales cycle length, CAC by channel, LTV calculations. + +**Documents to prepare**: (a) Customer roster with ARR, start date, contract term, (b) Monthly cohort retention curves, (c) NPS or CSAT survey results, (d) Sales pipeline report with stage definitions and conversion rates, (e) CAC calculation with channel-level breakdown, (f) LTV calculation methodology and results, (g) Three reference-ready customer contacts. + +**Red flags to address proactively**: Cohort retention that degrades with each new cohort, high logo churn masked by expansion revenue, LTV/CAC ratio below 3:1, sales pipeline inflated with stale opportunities, no systematic customer feedback mechanism. + +### Category 4: Technical Due Diligence + +**What investors will ask**: Architecture overview, tech stack rationale, scalability assessment, security practices, deployment frequency, uptime history, technical debt inventory. + +**Documents to prepare**: (a) System architecture diagram, (b) Tech stack summary with rationale for key choices, (c) Infrastructure and hosting overview (cloud provider, regions, redundancy), (d) Security practices document (authentication, encryption, data handling), (e) Deployment pipeline description, (f) Uptime and incident history -- 12 months, (g) Technical debt register with severity ratings, (h) Open-source licence compliance audit. + +**Red flags to address proactively**: Single points of failure in architecture, no automated testing, manual deployment processes, security practices that do not meet industry baseline, technical debt that blocks feature velocity. + +### Category 5: HR Due Diligence + +**What investors will ask**: Org chart, key person risk, compensation benchmarks, equity allocation, employee agreements, contractor classifications. + +**Documents to prepare**: (a) Current org chart with reporting lines, (b) Key person analysis -- who is irreplaceable and why, (c) Compensation summary (base, bonus, equity) by role level, (d) Equity allocation summary (option pool size, grants made, grants remaining), (e) Employee handbook or policy documents, (f) Contractor agreements and classification analysis, (g) Planned hires for next 12 months with budget. + +**Red flags to address proactively**: Key person dependencies with no succession plan, contractor misclassification risk, option pool exhausted before next funding round, compensation significantly above or below market benchmarks, missing non-compete or non-solicitation agreements for key roles. + +## Data Collection Template + +``` +DATA ROOM READINESS CHECKLIST +Financial: [ ] P&L 24mo [ ] Balance sheet [ ] Cash flow [ ] Revenue breakdown [ ] Model +Legal: [ ] Incorporation [ ] Bylaws [ ] Board minutes [ ] All equity docs [ ] IP assignments +Commercial: [ ] Customer list [ ] Cohort retention [ ] NPS data [ ] Pipeline [ ] CAC/LTV +Technical: [ ] Architecture [ ] Security [ ] Uptime log [ ] Tech debt register +HR: [ ] Org chart [ ] Comp summary [ ] Equity allocation [ ] Key person analysis + +RED FLAGS IDENTIFIED +1. _______________ Severity: High / Medium / Low Remediation plan: _______________ +2. _______________ Severity: High / Medium / Low Remediation plan: _______________ +3. _______________ Severity: High / Medium / Low Remediation plan: _______________ + +DATA ROOM STRUCTURE +/01-Corporate /02-Financial /03-Commercial /04-Technical /05-HR /06-Legal +``` + +## Interpretation Guide + +**Investor-ready**: All five categories have complete documentation, identified red flags have remediation plans in place, and the data room is organised with a clear index. Diligence requests can be fulfilled within 48 hours. + +**Needs work**: Documentation exists but is scattered, incomplete, or outdated. Allocate 2-3 weeks to fill gaps before entering active fundraising conversations. + +**Not ready**: Multiple categories have missing foundational documents (no IP assignments, no cap table, no monthly financials). Address these structural gaps before any investor outreach -- they signal operational immaturity that cannot be papered over. + +## Common Pitfalls + +- **Last-minute assembly**: Scrambling to produce documents after receiving a term sheet creates errors, delays closing, and erodes investor confidence. +- **Selective disclosure**: Hiding known issues (pending litigation, customer concentration) backfires when discovered -- and it is always discovered. +- **Inconsistent numbers**: Revenue figures that differ between your deck, your financials, and your CRM destroy credibility faster than any single bad metric. +- **Ignoring the cap table**: Unmodelled SAFEs, forgotten advisor shares, and miscalculated dilution create closing-threatening surprises. +- **Over-engineering the data room**: A cleanly organised folder structure with clear naming conventions beats an elaborate virtual data room platform with empty folders. + +## Output + +This research feeds directly into the following Foreman components: + +- **Skills**: `due-diligence-checklist`, `fundraising-playbook`, `fundraising-deck-outline` +- **Templates**: `due-diligence-checklist` (data room structure), `fundraising-deck-outline` (financial slides), `unit-economics-snapshot` (metrics), `cap-table-summary` (ownership data) +- **Playbooks**: `fundraising-playbook` (uses this data as pre-work for Step 1) diff --git a/plugins/foreman/content/research/financial-modeling-guide.md b/plugins/foreman/content/research/financial-modeling-guide.md new file mode 100644 index 0000000..2d5e385 --- /dev/null +++ b/plugins/foreman/content/research/financial-modeling-guide.md @@ -0,0 +1,154 @@ +--- +name: "financial-modeling-guide" +description: "Guides entrepreneurs through gathering the inputs required to + build a financial projection — revenue build-up, expense modeling, cash flow + projection, break-even analysis, and scenario stress-testing. Produces the + assumption set that drives a defensible financial model." +research_type: "financial" +feeds_into_skills: [] +feeds_into_templates: + - fundraising-deck-outline + - quarterly-strategic-review +estimated_time: "8-14 hours" +data_sources: + - SEC EDGAR + - Crunchbase + - Glassdoor + - Levels.fyi + - Pave + - Industry packs (Foreman) + - Bureau of Labor Statistics + - PitchBook +author: "Fatih Guner" +related_content: + - kind: template + ref: unit-economics-snapshot + - kind: template + ref: exit-scenario-analysis +--- + +# Financial Modeling Guide + +Every spreadsheet is an argument. The rows and columns present a thesis about how money will flow through a business over time — and like any argument, its persuasiveness depends entirely on the quality of its premises. Most founders fail not at the arithmetic but at the inputs: they guess at customer acquisition costs, invent salary figures, and wave vaguely at growth rates. The model then inherits these fabrications and presents them in crisp decimal precision, lending false confidence to false assumptions. + +This guide addresses the upstream problem. Before you build a model, you must research its inputs. Revenue assumptions require data on customers, pricing, and growth trajectories. Expense projections demand real salary benchmarks, vendor costs, and infrastructure pricing. Scenario analysis needs historical volatility ranges from comparable companies. Gather the evidence first. The spreadsheet comes second. + +--- + +## What You'll Learn + +- A bottom-up revenue build: customers multiplied by ARPU multiplied by realistic growth rates +- An expense map distinguishing fixed from variable costs, with salary benchmarks by role and geography +- A monthly cash flow projection for your chosen time horizon (3-5 years) +- Break-even point expressed in both time and revenue +- Three scenarios (base, optimistic, pessimistic) with clearly stated divergence assumptions +- The top 3 sensitivity drivers — the assumptions that, if wrong, most change the outcome + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| SEC EDGAR | Public company financials: revenue mix, cost structures, margins by segment | Free | sec.gov/edgar | +| Crunchbase | Startup funding rounds, revenue estimates, employee counts, growth signals | Freemium | crunchbase.com | +| Glassdoor | Salary data by role, company, and geography | Free | glassdoor.com | +| Levels.fyi | Granular tech compensation data: base, stock, bonus by level | Free | levels.fyi | +| Pave | Real-time compensation benchmarks by stage, role, and geography | Freemium | pave.com | +| Carta Total Comp | Equity and cash compensation benchmarks for startups | Paid (free reports) | carta.com | +| PitchBook | Comparable company financials, valuation multiples, deal terms | Paid (library access) | pitchbook.com | +| Bureau of Labor Statistics | Employment cost trends, inflation data, occupational wage statistics | Free | bls.gov | +| Industry Packs (Foreman) | Sector-specific benchmarks: margins, CAC, LTV, churn, growth rates | Free (built-in) | `.claude/industry-packs/` | +| AWS/GCP/Azure Pricing Calculators | Infrastructure cost estimation | Free | Respective cloud provider sites | + +--- + +## Research Protocol + +**Step 1 — Define the Time Horizon** +Choose 3 or 5 years. Three years suits pre-seed and seed companies where visibility is limited. Five years applies to Series A and beyond where investors expect a longer trajectory. Record your choice and the rationale. + +**Step 2 — Build Revenue Assumptions Bottom-Up** +Identify your revenue streams. For each stream, research: (a) the number of target customers you can reach per period, (b) the average revenue per user or contract value, (c) growth rate assumptions grounded in comparable company trajectories or your own historical data. Source customer counts from your pipeline, market sizing research, or industry benchmarks. Source ARPU from your pricing research or comparable public companies via SEC filings. + +**Step 3 — Map Expense Categories** +Separate fixed costs (rent, insurance, base salaries) from variable costs (cloud infrastructure, payment processing, sales commissions). For each category, gather current actuals where available and benchmark data for projected hires or expenditures. Use Glassdoor, Levels.fyi, and Pave for salary benchmarking — record the 25th, 50th, and 75th percentile for each role you plan to hire. + +**Step 4 — Project Monthly Cash Flow** +Lay out revenue minus expenses on a monthly basis. Account for payment timing: when do customers pay versus when do you recognize revenue? When do large expenses hit (annual contracts, tax payments, equipment purchases)? Identify months where cash goes negative. + +**Step 5 — Calculate Break-Even** +Determine the revenue level at which monthly income covers monthly expenses. Express this as both a revenue figure and a customer count. Then estimate the month in which you reach it, given your growth assumptions. + +**Step 6 — Stress-Test with Three Scenarios** +Build three variants. Base case uses your best-estimate assumptions. Optimistic case improves growth rate by 30-50% and reduces churn. Pessimistic case cuts growth by 30-50%, increases churn, and delays key hires. For each scenario, note the cash runway implication and the break-even shift. + +**Step 7 — Identify Top 3 Sensitivity Drivers** +Vary each major assumption independently by +/- 20% and observe the impact on cash runway and break-even timing. Rank the assumptions by impact magnitude. The top three are your sensitivity drivers — these are where additional research effort pays the highest return. + +--- + +## Data Collection Template + +### Revenue Build-Up + +| Revenue Stream | Customers (Month 1) | Monthly Growth Rate | ARPU | Source for Growth Rate | Source for ARPU | +|---------------|---------------------|--------------------| -----|----------------------|----------------| +| | | % | $ | | | +| | | % | $ | | | +| **Total Monthly Revenue (Month 1)** | | | **$** | | | + +### Expense Map + +| Category | Type (Fixed/Variable) | Monthly Cost | Source/Benchmark | Scaling Trigger | +|----------|-----------------------|-------------|-----------------|----------------| +| Engineering salaries | Fixed | $ | Levels.fyi (50th pctl) | Per hire | +| Cloud infrastructure | Variable | $ | AWS calculator | Per 1K users | +| Sales commissions | Variable | $ | Industry standard | Per deal closed | +| Office/rent | Fixed | $ | Market rate | Lease terms | +| | | $ | | | + +### Scenario Summary + +| Metric | Pessimistic | Base | Optimistic | +|--------|------------|------|-----------| +| Monthly revenue growth rate | % | % | % | +| Monthly churn rate | % | % | % | +| Months to break-even | | | | +| Cash runway (months) | | | | +| Total funding needed | $ | $ | $ | + +--- + +## Interpretation Guide + +**Revenue realism check:** Compare your projected Year 2 revenue to comparable startups at the same stage. If your model shows $10M ARR by Year 2 for a pre-seed company, the burden of proof is on you. The median Series A company reaches $1-2M ARR. + +**Expense ratio benchmarks:** Software companies at scale spend roughly 60-70% of revenue on operating expenses. Early-stage companies routinely exceed 100% (hence the need for funding). If your model shows profitability in Year 1 without explaining why, skeptics will find the gap. + +**Sensitivity hierarchy:** If a 20% change in customer acquisition cost shifts your break-even by six months but a 20% change in office rent shifts it by two weeks, your research priority is clear. Allocate diligence proportionally to sensitivity. + +**Scenario spread:** If your pessimistic and optimistic scenarios differ by less than 2x in terminal revenue, your range is too narrow. Real uncertainty is wider than founders prefer to admit. + +--- + +## Common Pitfalls + +- **Hockey-stick without mechanism.** Projecting exponential growth without identifying the specific channel, campaign, or product trigger that produces it. Growth curves need causal stories, not faith. +- **Forgetting the hiring ramp.** Modeling ten engineers at full productivity from Day 1 when the actual timeline involves recruiting, onboarding, and ramping — each adding months and cost before output materializes. +- **Benchmarking salaries to the wrong market.** San Francisco salaries applied to a distributed team hiring in lower-cost markets inflates expenses. The reverse — using low-cost benchmarks when competing for Bay Area talent — makes offers uncompetitive. +- **Ignoring cash timing.** Revenue recognized is not cash received. Enterprise contracts with net-60 payment terms mean your P&L looks healthy while your bank account bleeds. +- **Single-scenario conviction.** Presenting only the base case signals either naivety or dishonesty. Sophisticated stakeholders want to see what breaks the model. + +--- + +## Output + +Package your financial research inputs for use in the following Foreman components: + +- **unit-economics-snapshot** — ARPU, CAC, LTV, and margin data feed directly into the unit economics framework. The bottom-up revenue build provides the numerator; the expense map provides the denominator. +- **fundraising-deck-outline** — The "Financial Projections" and "Use of Funds" slides draw from your scenario summary, break-even analysis, and expense map. +- **exit-scenario-analysis** — Terminal revenue projections and growth rates from your scenarios feed the exit valuation models. The sensitivity analysis identifies which assumptions most affect exit outcomes. +- **quarterly-strategic-review** — Actuals-versus-projection comparisons require the projection baseline you build here. Update the model quarterly as assumptions get validated or invalidated. + +Transfer the assumption table, scenario summary, and sensitivity ranking. Flag which assumptions remain unvalidated — these become the research agenda for the next quarter. diff --git a/plugins/foreman/content/research/funding-landscape-research.md b/plugins/foreman/content/research/funding-landscape-research.md new file mode 100644 index 0000000..c689163 --- /dev/null +++ b/plugins/foreman/content/research/funding-landscape-research.md @@ -0,0 +1,149 @@ +--- +name: "funding-landscape-research" +description: "Guides entrepreneurs through mapping the funding landscape — + identifying stage-appropriate capital sources, building targeted investor + lists, researching partner-level thesis and portfolio fit, and constructing + warm outreach sequences. Produces a prioritized investor pipeline and outreach + plan." +research_type: "financial" +feeds_into_skills: [] +feeds_into_templates: + - fundraising-deck-outline + - investor-update-email +estimated_time: "10-20 hours" +data_sources: + - Crunchbase + - PitchBook + - AngelList + - Signal by NFX + - LinkedIn + - F6S + - grants.gov + - SBIR.gov +author: "Fatih Guner" +related_content: + - kind: playbook + ref: fundraising-playbook + - kind: template + ref: fundraising-deck-outline + - kind: template + ref: investor-update-email +--- + +# Funding Landscape Research + +Capital is not interchangeable. A dollar from a strategic investor who opens distribution channels differs fundamentally from a dollar borrowed against future revenue, and both differ from a grant that demands no equity but constrains your roadmap. Founders who treat fundraising as a single question -- "who will give us money?" -- end up with the wrong capital on the wrong terms from the wrong partner. The research that precedes a fundraise determines not just whether you raise, but whether the capital you secure accelerates or distorts your trajectory. This guide provides a systematic method for mapping every relevant funding source, filtering to the ones that fit your stage and sector, and researching individual investors with enough depth to make every outreach attempt count. + +--- + +## What You'll Learn + +- A categorized inventory of funding sources appropriate to your stage and sector +- A target list of 30-50 investors with thesis fit, check size, and portfolio conflict data +- Partner-level profiles for your top 15 targets, including investment interests and warm intro paths +- An assessment of non-dilutive alternatives (grants, revenue-based financing, venture debt) +- A prioritized outreach sequence balancing fit, accessibility, and strategic value + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Crunchbase | Investor portfolios, funding rounds, check sizes, sector focus | Freemium | crunchbase.com | +| PitchBook | Detailed fund data, partner attribution, deal flow analysis | Paid (often via university or accelerator access) | pitchbook.com | +| AngelList | Angel investor profiles, syndicate activity, rolling fund data | Free | angellist.com | +| Signal by NFX | Investor matching based on sector, stage, and geography | Free | signal.nfx.com | +| LinkedIn | Partner-level research: background, board seats, content interests, mutual connections | Free (limited) | linkedin.com | +| F6S / Gust | Accelerator and incubator directories with application timelines | Free | f6s.com / gust.com | +| grants.gov | U.S. federal grant listings across all agencies | Free | grants.gov | +| SBIR.gov | Small Business Innovation Research grant solicitations and awards | Free | sbir.gov | +| Innovate UK / EU Horizon | UK and EU government innovation funding programs | Free | innovateuk.ukri.org / ec.europa.eu/horizon | +| NVCA Yearbook | Aggregate VC market data: fund sizes, stage distribution, sector trends | Free (annual report) | nvca.org | + +--- + +## Research Protocol + +**Step 1 -- Define Funding Need** +Specify three parameters before searching: (a) the amount you need to raise, (b) the timeline within which you need the capital deployed, and (c) your flexibility on terms -- specifically, how much dilution you will accept and whether you are open to debt. These three numbers filter out 80% of irrelevant sources immediately. + +**Step 2 -- Assess Stage-Appropriate Sources** +Map your stage to typical capital sources. Pre-seed: angels, pre-seed funds, accelerators, SBIR. Seed: seed funds, micro-VCs, syndicates. Series A: institutional VCs ($100M-$500M funds). Later: growth equity, venture debt, revenue-based financing. Pursuing capital from the wrong stage wastes months. + +**Step 3 -- Build the Long List (30-50 Targets)** +Using Crunchbase, AngelList, and Signal, generate investors matching on stage, sector, and check size. Include 5-10 non-dilutive options if applicable. Record fund size, last fund vintage, and deployment pace in the past 12 months. A fund that has not deployed in a year is either fully committed or in transition. + +**Step 4 -- Research Portfolio Fit and Conflicts** +For each investor, review portfolio companies on Crunchbase. Flag direct competitors -- most investors will not fund a conflict. Note complementary companies that signal thesis alignment and may provide warm intros. + +**Step 5 -- Build Partner-Level Profiles (Top 15)** +For your highest-fit investors, identify the specific partner most likely to lead your deal. Research their background on LinkedIn, read their published writing, and note which portfolio companies they led. Generic outreach to "the fund" converts at a fraction of the rate of targeted outreach to the right partner. + +**Step 6 -- Identify Warm Introduction Paths** +For each top-15 target, map intro sources: mutual connections, portfolio founder relationships, accelerator alumni networks. A warm introduction from a portfolio founder converts at roughly 10x the rate of a cold email. Rank each target by warmest available path. + +**Step 7 -- Build the Outreach Sequence** +Prioritize by thesis fit, accessibility, and strategic value. Sequence in waves of 5-8, starting with second-tier targets to refine your pitch before approaching top choices. + +--- + +## Data Collection Template + +### Investor Target Matrix + +| Investor | Type | Stage | Sector | Check Size | Fund Size | Conflict? | Warm Path? | +|----------|------|-------|--------|------------|-----------|-----------|------------| +| | | | | | | | | + +### Partner Profile (Top 15) + +| Dimension | Partner 1 | Partner 2 | Partner 3 | +|-----------|-----------|-----------|-----------| +| Name / Fund | | | | +| Background / notable investments | | | | +| Published thesis | | | | +| Warmest intro path | | | | +| Outreach priority (1-5) | | | | + +### Non-Dilutive Options Assessment + +| Source | Type | Amount Range | Timeline | Key Constraints | Fit? | +|--------|------|-------------|----------|----------------|------| +| SBIR Phase I | Grant | $50K-$275K | 6-12 months | U.S. entity, R&D focus | | +| Revenue-based financing | Debt | $50K-$5M | 2-4 weeks | Requires recurring revenue | | +| Venture debt | Debt | 25-50% of last equity raise | 4-8 weeks | Requires recent equity round | | +| Crowdfunding (equity) | Equity | $50K-$5M | 2-4 months | Marketing-intensive, public | | + +--- + +## Interpretation Guide + +**Thesis match is non-negotiable.** An investor who focuses on enterprise SaaS will not lead your consumer marketplace round. Thesis misalignment is not overcome by enthusiasm. Filter ruthlessly. + +**Recent deployment pace signals appetite.** Eight investments in 12 months means active deployment. One investment means concentrated or winding down. Check fund vintage -- years 1-3 deploy; years 4-5 follow on. + +**Portfolio density is a double signal.** Three portfolio companies in your space signals thesis understanding but may mean the thesis is fully expressed. Ask portfolio founders directly. + +**Warm paths have a half-life.** An introduction loses potency with delay. Activate within one week of identifying the path. + +--- + +## Common Pitfalls + +- **Spraying cold emails to 200 investors.** Volume signals desperation. A targeted 30-investor process with warm intros outperforms a 200-investor cold campaign. +- **Ignoring non-dilutive capital.** Grants and revenue-based financing are underutilised. At pre-seed, $150K in SBIR funding preserves meaningful ownership. +- **Researching the fund but not the partner.** Funds do not write checks -- partners do. Your pitch must resonate with the person across the table. +- **Optimising for valuation over partner quality.** The highest valuation often comes from the least helpful investor. Operational value compounds far beyond the term sheet. +- **Starting with your top choice.** Your first three pitches will be your worst. Sequence so top-priority investors hear the refined version. + +--- + +## Output + +Package your funding landscape research for use in the following Foreman skills and templates: + +- **Skills**: `fundraising-playbook` (investor matrix and outreach sequence feed execution steps), `fundraising-deck-outline` (thesis research informs narrative per investor), `investor-update-email` (investor list becomes the distribution list) +- **Templates**: `fundraising-deck-outline` (market slide customisation), `investor-update-email` (relationship maintenance) + +Transfer the investor matrix, partner profiles, non-dilutive assessment, and prioritised outreach sequence. Flag which investors represent the strongest thesis fit. diff --git a/plugins/foreman/content/research/industry-mapping-guide.md b/plugins/foreman/content/research/industry-mapping-guide.md new file mode 100644 index 0000000..586ae04 --- /dev/null +++ b/plugins/foreman/content/research/industry-mapping-guide.md @@ -0,0 +1,142 @@ +--- +name: "industry-mapping-guide" +description: "Structured protocol for mapping an industry landscape, including + value chain analysis, ecosystem mapping, market segmentation, regulatory + scanning, technology trend assessment, and distribution channel + identification. Produces the foundational market intelligence that strategic + frameworks require." +research_type: "market" +feeds_into_skills: + - porters-five-forces + - swot-pest-analysis + - scenario-planning + - blue-ocean-strategy +feeds_into_templates: + - market-opportunity-summary + - strategic-analysis-one-pager + - competitive-landscape-brief +estimated_time: "15-25 hours" +data_sources: + - industry-reports + - trade-associations + - conference-programmes + - linkedin-job-postings + - patent-filings + - regulatory-bodies + - vc-investment-databases +author: "Fatih Guner" +related_content: + - kind: template + ref: market-opportunity-summary + - kind: template + ref: strategic-analysis-one-pager +--- + +# Industry Mapping Guide + +## Purpose + +Every strategic framework assumes you understand the industry you operate in. Porter's Five Forces requires knowing who the suppliers and buyers are. SWOT demands an honest assessment of external threats. Scenario planning needs an inventory of forces that could reshape the landscape. This guide builds that foundational map -- the territory itself, before you start strategising about it. + +## What You'll Learn + +- How to define industry boundaries without making them too narrow or too broad +- How to trace the full value chain from raw inputs to end customers +- How to identify every category of player in the ecosystem and their relationships +- How to read signals from job postings, patent filings, and VC investments to detect strategic shifts before they become obvious +- How to spot white spaces where no incumbent has staked a defensible position + +## Data Sources + +| Source | What It Provides | Access Method | +|--------|-----------------|---------------| +| Industry reports (IBISWorld, Gartner, Forrester) | Market size, growth rates, segmentation, competitive concentration | Subscription or library access; summarise key findings | +| Trade associations | Industry standards, lobbying priorities, membership directories | Association websites; annual reports; event calendars | +| Conference speaker lists | Who the ecosystem considers important; emerging topic trends | Review agendas from the 3-5 largest industry events | +| LinkedIn job postings | Company strategy signals (hiring for AI = building AI; hiring for compliance = regulatory pressure) | Search by company + role keywords; track patterns over 6 months | +| Patent filings (USPTO, EPO, Google Patents) | Technology direction of major players; defensive vs. offensive IP strategies | Search by company, inventor, or technology keyword | +| Regulatory bodies | Current regulations, proposed rules, enforcement actions | Government agency websites; Federal Register or equivalent | +| VC investment databases (Crunchbase, PitchBook) | Where money is flowing; which segments attract capital; emerging players | Search by category, stage, and date range | + +## Research Protocol + +### Step 1: Define Industry Boundaries + +Determine what is inside and outside your industry map. Three boundary tests: (a) substitution -- if a customer could use Product B instead of Product A, they are in the same industry; (b) supply chain -- if Company C provides essential inputs to most players, it is part of the ecosystem; (c) regulation -- if a set of companies falls under the same regulatory framework, they share an industry boundary. Document your boundary decisions explicitly. They will be challenged, and you need defensible reasoning. + +### Step 2: Map the Value Chain + +Trace the flow from raw inputs to end customer. Identify every stage: who produces, who aggregates, who distributes, who sells, who supports, who finances. For each stage, note: (a) number of players, (b) concentration level (fragmented vs. oligopoly), (c) margin profile (where does value accumulate?), (d) switching costs between stages. The stages where margins are thickest and switching costs highest reveal where power concentrates. + +### Step 3: Identify Key Players Per Segment + +Within each value chain stage, catalogue the major players. For each: (a) estimated revenue or market share, (b) primary competitive advantage, (c) recent strategic moves (acquisitions, product launches, pivots), (d) funding history and investors. Group players into tiers: dominant incumbents, established challengers, and emerging entrants. + +### Step 4: Map Relationships and Dependencies + +Draw the connections. Who supplies whom? Who partners with whom? Where do exclusive relationships exist? Where are multi-homing patterns (customers using multiple providers simultaneously)? Identify structural dependencies -- if one player disappeared, who would be most affected? These dependencies reveal both vulnerabilities and acquisition logic. + +### Step 5: Identify White Spaces + +Overlay the value chain map with customer pain points and unmet needs. White spaces appear where: (a) a value chain stage is underserved or fragmented, (b) adjacent industries have solutions that have not crossed over, (c) technology shifts create new possibilities that incumbents have not addressed, (d) regulatory changes open previously inaccessible segments. Rank white spaces by addressable market size and defensibility. + +### Step 6: Assess the Regulatory Landscape + +Catalogue current regulations affecting the industry. Identify proposed regulations under review. Note recent enforcement actions and their implications. Assess regulatory trajectory: is the industry heading toward more regulation (fintech, healthtech) or deregulation? Regulatory shifts create both risk and opportunity -- new entrants often exploit the gap between regulation change and incumbent adaptation. + +## Data Collection Template + +``` +INDUSTRY BOUNDARY DEFINITION +Industry name: _______________ +Boundary rationale: _______________ +What is included: _______________ +What is explicitly excluded: _______________ + +VALUE CHAIN MAP +Stage 1: _______________ | Players: ___ | Concentration: ___ | Margins: ___ +Stage 2: _______________ | Players: ___ | Concentration: ___ | Margins: ___ +Stage 3: _______________ | Players: ___ | Concentration: ___ | Margins: ___ +Stage 4: _______________ | Players: ___ | Concentration: ___ | Margins: ___ +Stage 5: _______________ | Players: ___ | Concentration: ___ | Margins: ___ + +KEY PLAYER REGISTRY +Tier 1 (Dominant): _______________ Revenue/Share: ___ Advantage: ___ +Tier 2 (Challenger): _______________ Revenue/Share: ___ Advantage: ___ +Tier 3 (Emerging): _______________ Revenue/Share: ___ Advantage: ___ + +WHITE SPACES IDENTIFIED +1. _______________ Addressable market: $___ Defensibility: High / Medium / Low +2. _______________ Addressable market: $___ Defensibility: High / Medium / Low +3. _______________ Addressable market: $___ Defensibility: High / Medium / Low + +REGULATORY LANDSCAPE +Current regulations: _______________ +Proposed regulations: _______________ +Recent enforcement: _______________ +Regulatory trajectory: Tightening / Stable / Loosening +``` + +## Interpretation Guide + +**High-opportunity industry**: Multiple white spaces, fragmented value chain stages, capital flowing into the sector, regulatory environment stable or newly opened. Good conditions for new entrants. + +**Mature, consolidated industry**: Few white spaces, dominant incumbents with high switching costs, declining VC investment, established regulatory framework. Entry requires either deep differentiation or disruption from an adjacent technology. + +**Transitioning industry**: Technology or regulatory shifts creating turbulence, incumbents visibly restructuring (evidenced by layoffs and pivots in job posting data), patent filing activity spiking in new domains. High risk, high opportunity -- timing matters enormously. + +## Common Pitfalls + +- **Drawing boundaries too narrowly**: Defining your industry as only direct competitors blinds you to substitutes and adjacent entrants -- the sources of most disruption. +- **Mistaking a list for a map**: Cataloguing players without mapping their relationships misses the structural dynamics that determine competitive outcomes. +- **Relying solely on published reports**: Industry reports describe last year's landscape. Job postings, patent filings, and VC activity signal next year's. +- **Ignoring the regulatory layer**: Founders building in regulated industries who treat compliance as an afterthought discover too late that it shapes every strategic decision. +- **Static mapping**: An industry map is a living document. Revisit quarterly. The players and power dynamics shift faster than most founders assume. + +## Output + +This research feeds directly into the following Foreman components: + +- **Skills**: `porters-five-forces` (competitive force identification), `swot-pest-analysis` (external factor inventory), `scenario-planning` (trend and uncertainty inputs), `blue-ocean-strategy` (white space identification) +- **Templates**: `market-opportunity-summary` (industry context), `strategic-analysis-one-pager` (landscape overview), `competitive-landscape-brief` (player mapping) +- **Playbooks**: `competitive-response-playbook` (uses industry map as situational context) diff --git a/plugins/foreman/content/research/market-sizing-worksheet.md b/plugins/foreman/content/research/market-sizing-worksheet.md new file mode 100644 index 0000000..d5fe660 --- /dev/null +++ b/plugins/foreman/content/research/market-sizing-worksheet.md @@ -0,0 +1,168 @@ +--- +name: "market-sizing-worksheet" +description: "Guides entrepreneurs through TAM/SAM/SOM market sizing using three complementary approaches — top-down, bottom-up, and value theory. Produces defensible market estimates for strategic planning and investor conversations." +research_type: "market" +feeds_into_skills: + - business-model-canvas + - blue-ocean-strategy +feeds_into_templates: + - fundraising-deck-outline + - market-opportunity-summary +estimated_time: "6-12 hours" +data_sources: + - Statista + - IBISWorld + - Crunchbase + - U.S. Census Bureau + - SEC EDGAR + - Industry associations + - Analyst reports +author: "Fatih Guner" +--- + +# Market Sizing Worksheet + +A startup that cannot articulate the size of its market has not yet articulated its ambition. Market sizing is not a ritual performed for investors — it is the exercise through which a founder discovers whether the opportunity justifies the sacrifice. Get this wrong and everything downstream inherits the error: your business model targets the wrong segment, your pricing leaves money exposed, and your fundraising pitch collapses under the first skeptical question. + +Three numbers matter: TAM (Total Addressable Market), SAM (Serviceable Addressable Market), and SOM (Serviceable Obtainable Market). Each represents a progressive narrowing from theoretical ceiling to realistic capture. The discipline lies in the narrowing. + +--- + +## What You'll Learn + +- The total value of your market category (TAM) +- The segment you can actually reach with your product and distribution (SAM) +- A defensible estimate of what you can capture in 3-5 years (SOM) +- Cross-validated numbers from at least two independent sizing approaches +- A clear articulation of the assumptions behind each figure + +--- + +## Three Approaches + +**Top-Down:** Start with a published industry figure and narrow it. Fast, credible when sourced well, but prone to inflated starting points. + +**Bottom-Up:** Start with unit economics — price per customer multiplied by the number of reachable customers. Slower, more credible, and forces you to confront real distribution constraints. + +**Value Theory:** Estimate the total value your product creates for customers, then apply a capture rate. Best for new categories where no industry report exists. + +A defensible market size uses at least two of these approaches and reconciles the results. If top-down and bottom-up diverge by more than 3x, your assumptions need work. + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Statista | Industry market sizes, growth rates, segment breakdowns | Freemium (limited free) | statista.com | +| IBISWorld | Detailed industry reports with market size, trends, competition | Paid (library access often free) | ibisworld.com | +| U.S. Census Bureau | Economic census, business patterns, demographic data | Free | census.gov/data | +| Crunchbase | Startup funding data, company counts by sector | Freemium | crunchbase.com | +| SEC EDGAR | Public company filings with revenue, segment, and market data | Free | sec.gov/edgar | +| Industry Associations | Member surveys, annual reports, market forecasts | Varies | Search: "[your industry] association" | +| Grand View Research / Allied Market Research | Market reports with free summary data | Free summaries, paid full reports | grandviewresearch.com | +| Google Trends | Relative search volume as demand proxy | Free | trends.google.com | +| Bureau of Labor Statistics | Employment data as market activity proxy | Free | bls.gov | + +--- + +## Research Protocol + +**Step 1 — Define the Market Category** +Write a one-sentence market definition. Be specific. Not "the global software market" but "cloud-based inventory management for mid-market e-commerce retailers." The definition should describe a buyer, a problem, and a solution category. + +**Step 2 — Top-Down TAM Estimation** +Find 2-3 industry reports that size your market category or the nearest parent category. Record the figure, the source, the year, and the methodology. If you must use a parent category, estimate your sub-segment as a percentage — and justify that percentage. + +**Step 3 — Calculate SAM** +From the TAM, remove segments you cannot serve. Filters include: geography (where you can sell), customer size (who your product fits), channel (who you can reach), and regulatory (where you're permitted to operate). Each filter should reduce the number with a stated rationale. + +**Step 4 — Bottom-Up Cross-Check** +Count the number of potential customers in your SAM. Multiply by your expected average revenue per customer. This figure should land within the same order of magnitude as your top-down SAM. If not, revisit your assumptions. + +**Step 5 — SOM Estimation** +Apply a realistic market share percentage to your SAM. For a startup entering an established market, 1-5% in year 3-5 is defensible. For a new category, use analogous company growth trajectories instead of share percentages. + +**Step 6 — Value Theory Validation (Optional)** +Estimate the cost of the problem you solve per customer per year. Multiply by the number of affected customers. Apply a 10-30% value capture rate. This provides an independent ceiling check. + +--- + +## Data Collection Template + +### Top-Down Calculation + +| Item | Value | Source | Year | Notes | +|------|-------|--------|------|-------| +| Industry/category definition | | | | | +| Total market value (TAM) | $ | | | | +| Geographic filter (% remaining) | % | | | | +| Customer-size filter (% remaining) | % | | | | +| Channel filter (% remaining) | % | | | | +| **SAM (TAM x filters)** | **$** | | | | +| Realistic market share (%) | % | | | | +| **SOM (SAM x share)** | **$** | | | | + +### Bottom-Up Calculation + +| Item | Value | Source | Notes | +|------|-------|--------|-------| +| Number of potential customers | | | | +| Average revenue per customer/year | $ | | | +| **Bottom-up SAM (customers x ARPC)** | **$** | | | +| Reachable customers in 3-5 years | | | | +| **Bottom-up SOM (reachable x ARPC)** | **$** | | | + +### Value Theory Calculation + +| Item | Value | Source | Notes | +|------|-------|--------|-------| +| Cost of the problem per customer/year | $ | | | +| Number of affected customers | | | | +| Total value created | $ | | | +| Value capture rate (10-30%) | % | | | +| **Value-theory market size** | **$** | | | + +### Reconciliation + +| Approach | SAM Estimate | SOM Estimate | Confidence | +|----------|-------------|-------------|------------| +| Top-down | $ | $ | Low / Medium / High | +| Bottom-up | $ | $ | Low / Medium / High | +| Value theory | $ | $ | Low / Medium / High | +| **Reconciled figure** | **$** | **$** | | + +--- + +## Interpretation Guide + +**Credible TAM range:** For a venture-backable startup, TAM between $1B and $100B is typical. Below $500M signals a lifestyle business (not wrong — just different). Above $100B usually means the market definition is too broad. + +**SAM reality check:** SAM should be 10-40% of TAM for a focused product. If your SAM is 80% of TAM, you have not filtered enough. If it is 2% of TAM, you may be in a niche — validate that the niche is large enough. + +**SOM defensibility:** SOM is a bet on execution, not a market fact. Defend it with analogies: "Company X captured Y% of a comparable SAM in Z years with a similar go-to-market." Never cite SOM without naming the assumptions. + +**Convergence signal:** If top-down and bottom-up estimates fall within 2x of each other, your sizing has internal consistency. If they diverge by 5x or more, one set of assumptions is materially wrong. + +--- + +## Common Pitfalls + +- **The trillion-dollar TAM.** Citing a massive parent category ("the global healthcare market is $8.3 trillion") without narrowing to your actual segment. Investors read this as analytical laziness. +- **TAM without SAM/SOM.** Presenting only TAM communicates that you have not thought about who you can actually reach and how much you can capture. +- **Confusing TAM with revenue potential.** TAM is the total spend in the category, not what your company will earn. Your revenue ceiling is SOM, not TAM. +- **Single-source dependence.** Using one industry report as gospel. Reports disagree. Use multiple sources and note the range. +- **Static sizing.** Markets grow. A $5B market growing at 25% annually is more attractive than a $20B market growing at 2%. Always include the growth rate alongside the absolute figure. + +--- + +## Output + +Package your reconciled market sizing for use in the following Foreman skills and templates: + +- **business-model-canvas** — SAM and SOM feed the "Customer Segments" and "Revenue Streams" blocks. The sizing validates whether your revenue model can reach venture scale. +- **blue-ocean-strategy** — TAM by segment reveals where the market is crowded and where uncontested space may exist. +- **fundraising-deck-outline** — The "Market Opportunity" slide uses TAM/SAM/SOM directly. Include the reconciliation approach for credibility. +- **market-opportunity-summary** — The self-facing document that captures your market thesis, assumptions, and evidence for internal reference. + +Transfer the reconciled figures, growth rates, and key assumptions. Note which assumptions carry the most uncertainty — these become validation priorities. diff --git a/plugins/foreman/content/research/partnership-research-guide.md b/plugins/foreman/content/research/partnership-research-guide.md new file mode 100644 index 0000000..dfa7682 --- /dev/null +++ b/plugins/foreman/content/research/partnership-research-guide.md @@ -0,0 +1,140 @@ +--- +name: "partnership-research-guide" +description: "Guides entrepreneurs through researching and evaluating potential business partners before committing — covering financial health, reputation, strategic fit, culture compatibility, and structural risk. Produces a due-diligence dossier that prevents costly misalliances." +research_type: "competitor" +feeds_into_skills: + - coalition-and-partnership-games + - cooperative-negotiation + - trust-equation +feeds_into_templates: + - partnership-memo +estimated_time: "5-10 hours" +data_sources: + - SEC EDGAR + - Glassdoor + - LinkedIn + - Crunchbase + - PACER + - Dun & Bradstreet + - News archives +author: "Fatih Guner" +--- + +# Partnership Research Guide + +Partnerships fail more often than marriages, and for similar reasons: insufficient diligence before commitment, incompatible expectations discovered too late, and an asymmetry of investment that breeds resentment. The handshake feels good. Eighteen months later, one side has delivered and the other has not, and the lawyers are expensive. + +The antidote is research conducted before the commitment. A prospective partner's financial health, litigation history, employee sentiment, and strategic trajectory are all discoverable — if you know where to look. This guide provides the protocol. + +--- + +## What You'll Learn + +- Financial health assessment and reputation profile for each candidate +- Strategic fit evaluation: where interests align and where they might collide +- Culture compatibility signals derived from observable artifacts, not gut feeling +- A risk matrix quantifying dependency, power imbalance, and exit difficulty + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| SEC EDGAR | Public company financials, risk disclosures, executive compensation | Free | sec.gov/edgar | +| Crunchbase | Funding history, investors, employee count, key personnel | Freemium | crunchbase.com | +| Glassdoor | Employee reviews, CEO approval ratings, interview experiences | Free | glassdoor.com | +| LinkedIn | Company size trends, employee tenure, recent hires, executive moves | Freemium | linkedin.com | +| Dun & Bradstreet | Credit reports, payment history, risk scores | Paid | dnb.com | +| PACER | Federal court records: lawsuits, bankruptcies, regulatory actions | $0.10/page | pacer.uscourts.gov | +| Google News / BBB | Press coverage, crisis history, complaint records | Free | news.google.com / bbb.org | +| Industry contacts | Informal reputation intelligence from shared networks | Free | Your network | + +--- + +## Research Protocol + +**Step 1 — Define What You Need from a Partner** +Articulate the gap. What capability, market access, technology, or credibility do you lack? Write a one-sentence need statement. This prevents pursuing a partnership because it feels exciting rather than because it solves a specific problem. + +**Step 2 — Identify 3-5 Candidates** +Generate a shortlist through industry mapping, competitor analysis, investor introductions, and LinkedIn searches. Three candidates is the minimum for meaningful comparison. + +**Step 3 — Financial Health Screen** +For public companies, pull the most recent 10-K and 10-Q from EDGAR. Examine revenue trends, debt ratios, and cash position. For private companies, use Dun & Bradstreet credit reports as a proxy. Red flags: declining revenue for two consecutive quarters, debt-to-equity above 3:1, or recent layoffs exceeding 10%. + +**Step 4 — Reputation Check** +Search PACER for litigation involving the company. Check Glassdoor for recurring themes in employee reviews — isolated complaints are noise; patterns about leadership, ethics, or broken promises are signal. Search news archives for the past three years. + +**Step 5 — Strategic Fit Assessment** +Map each candidate's products, customers, and growth trajectory against your own. The ideal partner has complementary strengths, not overlapping ones. Assess whether your roadmaps converge or diverge over 2-3 years. + +**Step 6 — Reference Calls (3 Per Candidate)** +Speak with three people who have worked with each candidate: one current partner, one former partner, and one industry observer. Key questions: What did the partnership deliver versus what was promised? How did the partner behave when things went wrong? + +**Step 7 — Build the Risk Matrix** +For each candidate, score dependency risk, power imbalance (relative size, revenue dependency, brand leverage), and exit difficulty (contractual lock-in, integration depth). Weight each factor by relevance to your situation. + +--- + +## Data Collection Template + +| Dimension | Candidate A | Candidate B | Candidate C | +|-----------|------------|------------|------------| +| Company name | | | | +| Revenue (est.) / Funding | $ | $ | $ | +| Employee count / Years in business | | | | +| Primary customers | | | | +| Complementary strength | | | | +| Overlap / conflict area | | | | + +| Indicator | Candidate A | Candidate B | Candidate C | Red Flag Threshold | +|-----------|------------|------------|------------|-------------------| +| Revenue trend (YoY) | % | % | % | Negative 2+ quarters | +| Debt-to-equity ratio | | | | > 3:1 | +| Cash runway (months) | | | | < 6 months | +| Recent layoffs (%) | % | % | % | > 10% | + +### Risk Matrix + +| Risk Factor | Weight | Candidate A (1-5) | Candidate B (1-5) | Candidate C (1-5) | +|------------|--------|-------------------|-------------------|-------------------| +| Dependency risk | | | | | +| Power imbalance | | | | | +| Exit difficulty | | | | | +| Reputation risk | | | | | +| **Weighted total** | | **__** | **__** | **__** | + +--- + +## Interpretation Guide + +**Financial health thresholds:** A partner with strong revenue growth but negative cash flow is betting on continued funding — acceptable for a startup, concerning for an enterprise partner. + +**Glassdoor pattern recognition:** Ignore the star rating. Read the text of negative reviews for recurring themes. "Promises not kept" is the single most predictive phrase for future partnership friction. "Constant pivoting" signals strategic instability. + +**Reference call calibration:** Current partners will be diplomatic. Former partners will be honest — but may carry grievances. Industry observers provide the most balanced view. If all three categories express the same concern, treat it as confirmed. + +**Risk score interpretation:** No partnership scores zero on all risk factors. A high dependency score with a low exit-difficulty score is manageable — you can leave. A high dependency with high exit-difficulty is a trap. + +--- + +## Common Pitfalls + +- **Brand-name infatuation.** Pursuing a partnership with a prestigious company without verifying that the specific division and team share the parent company's reputation. Partnerships happen between teams, not logos. +- **Symmetry assumption.** If you represent 0.1% of their revenue and they represent 30% of yours, the power asymmetry will shape every negotiation and renewal. +- **Skipping the former-partner call.** Current partners are curated references. Former partners discovered the failure modes. If a candidate cannot provide a former partner reference, that absence is informative. +- **Confusing strategic alignment with cultural compatibility.** Compatible products and still-failing partnerships usually trace to process mismatch: one side moves fast while the other requires six levels of approval. + +--- + +## Output + +Package your partnership research for use in the following Foreman components: + +- **coalition-and-partnership-games** — Strategic fit assessment and risk matrix feed game-theoretic analysis of partnership dynamics. +- **cooperative-negotiation** — Reference call findings and power imbalance scores inform negotiation preparation. +- **trust-equation** — Credibility and reliability scores map from reputation research and reference calls. +- **partnership-memo** — Synthesizes your recommendation, drawing on candidate comparison and risk matrix. + +Include risk scores, anonymized reference call summaries, and your top recommendation with supporting evidence. diff --git a/plugins/foreman/content/research/pricing-research-guide.md b/plugins/foreman/content/research/pricing-research-guide.md new file mode 100644 index 0000000..c9a68ef --- /dev/null +++ b/plugins/foreman/content/research/pricing-research-guide.md @@ -0,0 +1,132 @@ +--- +name: "pricing-research-guide" +description: "Structured research protocol for validating pricing assumptions + through quantitative and qualitative methods. Covers Van Westendorp Price + Sensitivity Meter, Gabor-Granger technique, competitor pricing analysis, + willingness-to-pay interviews, and price elasticity estimation." +research_type: "customer" +feeds_into_skills: + - four-ps-marketing +feeds_into_templates: + - unit-economics-snapshot + - market-opportunity-summary +estimated_time: "8-15 hours" +data_sources: + - competitor-websites + - g2-capterra-pricing-pages + - customer-interviews + - survey-tools + - pricing-page-analytics +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: pricing-diagnosis + - kind: playbook + ref: pricing-strategy-playbook + - kind: template + ref: unit-economics-snapshot +--- + +# Pricing Research Guide + +## Purpose + +Pricing is the only lever that directly converts product value into captured revenue -- and yet most founders set prices by copying a competitor or guessing. This guide provides a rigorous, multi-method protocol for determining what your market will actually pay, where price sensitivity inflects, and how to structure tiers that maximize both adoption and revenue per customer. + +## What You'll Learn + +- How to measure price sensitivity across a population using the Van Westendorp model +- How to estimate demand at specific price points via Gabor-Granger +- How to map and interpret competitor pricing architectures +- How to conduct willingness-to-pay interviews that yield honest answers +- How to synthesize findings into defensible pricing tiers + +## Data Sources + +| Source | What It Provides | Access Method | +|--------|-----------------|---------------| +| Competitor websites | Published pricing, tier structures, feature gating | Manual audit of pricing pages | +| G2 / Capterra | Pricing transparency scores, user-reported costs, plan comparisons | Search by category; filter by pricing | +| Customer interviews (5-8) | Willingness-to-pay signals, value perception, switching costs | Semi-structured 30-min interviews | +| Survey tools (Typeform, SurveyMonkey) | Van Westendorp and Gabor-Granger quantitative data | 30+ respondent survey, 5-8 min length | +| Pricing page A/B tests | Conversion rates at different price points | Optimizely, VWO, or native tooling | +| Industry benchmarks | Category-specific pricing norms and ARPU ranges | Analyst reports, OpenView SaaS benchmarks | + +## Research Protocol + +### Step 1: Map the Competitor Pricing Landscape + +Audit 8-12 direct and indirect competitors. For each, record: number of tiers, price per tier, billing frequency, feature differentiation between tiers, any usage-based components, free tier availability, and published enterprise pricing. Organize findings in a comparison matrix. Identify the price floor (cheapest viable alternative) and price ceiling (most expensive comparable offering). + +### Step 2: Conduct Van Westendorp Price Sensitivity Meter + +Survey 30+ respondents from your target segment. Present a clear description of your product's core value proposition, then ask four questions in sequence: + +1. At what price would this be **so cheap** you would question its quality? +2. At what price would this feel like a **bargain** -- great value for money? +3. At what price would this start to feel **expensive** -- you'd have to think carefully? +4. At what price would this be **too expensive** -- you'd never consider it? + +Plot cumulative frequency distributions. The intersection of "too cheap" and "too expensive" identifies the optimal price point. The range between "bargain" and "expensive" intersections defines the acceptable price band. + +### Step 3: Run 5-8 Willingness-to-Pay Interviews + +Recruit participants who match your ICP. Structure each 30-minute session around three phases: (a) understand their current spending on the problem you solve, (b) explore perceived value of your solution's key capabilities, (c) probe price thresholds without anchoring. Never open with a number. Ask "what would you expect to pay?" before revealing any pricing. Record the exact phrases they use to describe value -- these become pricing page copy. + +### Step 4: Calculate the Acceptable Price Range + +Synthesize Van Westendorp intersections, interview thresholds, and competitor positioning. Identify the range where survey data, interview data, and competitive positioning overlap. This convergence zone is your defensible pricing territory. + +### Step 5: Design Pricing Tiers + +Using the data, construct 2-4 tiers that reflect genuine usage segments -- not arbitrary feature gating. Each tier should correspond to a distinct buyer persona or usage intensity. The gap between tiers should reflect measurable value increments. Validate tier logic against interview verbatims: can you explain each upgrade in terms customers used themselves? + +## Data Collection Template + +``` +COMPETITOR PRICING MATRIX +Competitor: _______________ +Tier 1 (name): $___/mo | Features: _______________ +Tier 2 (name): $___/mo | Features: _______________ +Tier 3 (name): $___/mo | Features: _______________ +Billing options: Monthly / Annual (___% discount) +Free tier: Yes / No | Limits: _______________ + +VAN WESTENDORP RESULTS (n = ___) +Too cheap threshold: $___ +Bargain/value point: $___ +Expensive threshold: $___ +Too expensive ceiling: $___ +Optimal price point: $___ +Acceptable range: $___ to $___ + +INTERVIEW SYNTHESIS (n = ___) +Current spend on problem: $___ to $___/mo +Expected price for our solution: $___ to $___/mo +Most-cited value driver: _______________ +Price objection triggers: _______________ +``` + +## Interpretation Guide + +**Strong signal**: Van Westendorp optimal point falls within competitor mid-range and aligns with interview expectations. You have pricing permission from the market. + +**Warning signal**: Acceptable range is narrow (less than 20% spread), suggesting high price sensitivity. Consider usage-based pricing to reduce upfront commitment friction. + +**Red flag**: Interview willingness-to-pay falls below your unit economics floor. Either the value proposition needs strengthening, the target segment needs shifting, or the cost structure requires rework. + +## Common Pitfalls + +- **Anchoring bias in interviews**: Showing your price before asking about willingness-to-pay contaminates every subsequent answer. Always ask open-ended value questions first. +- **Survey sample bias**: Surveying only existing users or newsletter subscribers skews toward people who already value your product. Include cold prospects. +- **Competitor mimicry**: Matching a competitor's price signals equivalent value. If your product delivers more, pricing below them devalues your positioning. +- **Ignoring the "too cheap" floor**: Products priced below the quality-doubt threshold generate suspicion rather than conversion. +- **Skipping tier validation**: Tiers designed around internal feature bundles rather than customer usage patterns create confusion and reduce upgrade rates. + +## Output + +This research feeds directly into the following Foreman components: + +- **Skills**: `four-ps-marketing` (Price element), `pricing-diagnosis`, `pricing-strategy-playbook` +- **Templates**: `unit-economics-snapshot` (ARPU and pricing inputs), `market-opportunity-summary` (TAM pricing assumptions) +- **Playbooks**: `pricing-strategy-playbook` (uses this data as Step 1 input) diff --git a/plugins/foreman/content/research/regulatory-landscape-research.md b/plugins/foreman/content/research/regulatory-landscape-research.md new file mode 100644 index 0000000..d397de1 --- /dev/null +++ b/plugins/foreman/content/research/regulatory-landscape-research.md @@ -0,0 +1,149 @@ +--- +name: "regulatory-landscape-research" +description: "Guides entrepreneurs through mapping the regulatory environment for their business — identifying applicable regulations, licensing requirements, compliance costs, and pending changes. Critical for fintech, healthtech, edtech, and any venture operating across jurisdictions." +research_type: "regulatory" +feeds_into_skills: + - swot-pest-analysis + - scenario-planning +feeds_into_templates: + - risk-assessment-brief + - regulatory-compliance-update +estimated_time: "8-16 hours" +data_sources: + - Federal Register + - EUR-Lex + - SEC EDGAR + - Government regulatory agency websites + - Industry trade associations + - Westlaw + - LexisNexis +author: "Fatih Guner" +--- + +# Regulatory Landscape Research + +Regulation is the invisible architecture of markets. Founders who ignore it build on ground they do not own — and discover the problem only when an enforcement letter arrives, a banking partner withdraws, or a competitor weaponizes compliance as a barrier to entry. The startups that treat regulatory research as a one-time legal checkbox accumulate risk silently. The ones that treat it as ongoing market intelligence discover that regulation, understood properly, can be a moat. + +This guide provides a systematic protocol for mapping the regulatory environment around your business. The goal is not to produce a legal opinion — that requires counsel — but to produce the structured intelligence that makes legal counsel productive rather than exploratory. A founder who arrives at a lawyer's office with a jurisdiction map, a list of applicable regulations, and a compliance cost estimate will spend $5,000 on actionable advice. One who arrives with "we need to figure out our regulatory situation" will spend $25,000 on education. + +--- + +## What You'll Learn + +- A complete list of regulations that apply to your business, organized by jurisdiction +- The licensing and registration requirements for each jurisdiction where you operate +- An estimated cost of compliance (legal, technical, operational) +- A map of regulatory bodies — who enforces what, and how aggressively +- Pending regulatory changes that could affect your business within 12-24 months +- A compliance framework recommendation (SOC 2, HIPAA, GDPR, PCI-DSS, or others) based on your industry and data practices + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Federal Register (US) | Proposed and final rules, regulatory notices, executive orders | Free | federalregister.gov | +| EUR-Lex (EU) | EU legislation, directives, regulations, and case law | Free | eur-lex.europa.eu | +| State regulatory agency sites | State-specific licensing, registration, and compliance requirements | Free | Varies by state | +| SEC EDGAR | Securities regulations, company compliance disclosures, enforcement actions | Free | sec.gov/edgar | +| Industry trade associations | Compliance guides, regulatory summaries, advocacy updates | Varies (often member-only) | Search: "[industry] trade association" | +| Westlaw | Comprehensive legal database: statutes, case law, regulatory history | Paid | westlaw.com | +| Google Scholar (Legal) | Court opinions, law journal articles on regulatory interpretation | Free | scholar.google.com | +| RegTech platforms (e.g., Ascent, Compliance.ai) | Automated regulatory change monitoring and mapping | Paid | Various | +| CFPB (Consumer Financial Protection Bureau) | Consumer finance regulations, enforcement actions, complaint data | Free | consumerfinance.gov | +| HHS/OCR (Health and Human Services) | HIPAA enforcement, breach reports, compliance guidance | Free | hhs.gov/ocr | + +--- + +## Research Protocol + +**Step 1 — List All Jurisdictions** +Document every jurisdiction where you operate or plan to operate: countries, states/provinces, and municipalities. Include jurisdictions where your customers reside (GDPR applies based on the data subject's location, not yours), where your data is stored, and where your corporate entity is registered. A two-person startup selling SaaS to European customers from a Delaware C-Corp is subject to Delaware corporate law, US federal regulations, and GDPR simultaneously. + +**Step 2 — Identify Applicable Regulations per Jurisdiction** +For each jurisdiction, search for regulations by industry category and activity type. Financial services: SEC, FINRA, state money transmitter laws, CFPB. Health data: HIPAA, state health privacy laws. Education: FERPA, COPPA (if serving minors). General data: GDPR (EU), CCPA/CPRA (California), state privacy laws. Use trade association compliance guides as starting indexes — they aggregate the regulations their members must follow. + +**Step 3 — Map Regulatory Bodies** +For each applicable regulation, identify the enforcing agency. Note their enforcement posture: some agencies issue guidance and warnings (FTC for minor first offenses); others impose immediate fines (GDPR supervisory authorities). Check the agency's recent enforcement actions to understand what behavior triggers intervention. An agency that fined three companies in your sector last year is actively watching your space. + +**Step 4 — Assess Licensing Requirements** +Determine whether your business activity requires a license, registration, or certification in each jurisdiction. Common triggers: handling money (money transmitter licenses), handling health data (HIPAA Business Associate Agreements), providing financial advice (SEC/state registration), operating in regulated professions (state licensing boards). Record the application process, timeline, and cost for each. + +**Step 5 — Estimate Compliance Costs** +Break compliance costs into three categories: legal (counsel for policy drafting, regulatory filings), technical (security infrastructure, encryption, access controls, audit logging), and operational (compliance officer, training, ongoing monitoring). Use industry benchmarks: SOC 2 Type II audit costs $20K-80K for startups; HIPAA compliance buildout runs $50K-200K depending on scope; GDPR compliance for a mid-size SaaS company costs $50K-150K initially. + +**Step 6 — Monitor Pending Changes** +Subscribe to the Federal Register daily digest for your regulatory categories. Follow relevant trade association newsletters. Set Google Alerts for key regulation names and your industry. Pending regulations that are in the comment period will likely take effect within 12-18 months. Proposed rules under active debate may take 2-3 years. Map each pending change to its potential impact on your business. + +**Step 7 — Build a Compliance Timeline** +Sequence your compliance activities by priority: (1) regulations with active enforcement in your space, (2) regulations required for key partnerships or customer contracts, (3) regulations with pending deadlines, (4) best-practice frameworks that improve your market position. Assign owners, deadlines, and budget to each item. + +--- + +## Data Collection Template + +### Jurisdiction Map + +| Jurisdiction | Why Applicable | Key Regulations | Regulatory Body | Licensing Required? | +|-------------|---------------|----------------|----------------|-------------------| +| | Customers located here | | | Yes / No | +| | Data stored here | | | Yes / No | +| | Entity registered here | | | Yes / No | + +### Regulation Inventory + +| Regulation | Jurisdiction | Category | Compliance Status | Enforcement Risk (H/M/L) | Cost Estimate | +|-----------|-------------|----------|------------------|--------------------------|--------------| +| | | Data privacy | Not started / In progress / Compliant | | $ | +| | | Financial | Not started / In progress / Compliant | | $ | +| | | Industry-specific | Not started / In progress / Compliant | | $ | + +### Pending Regulatory Changes + +| Regulation/Proposal | Jurisdiction | Current Stage | Expected Effective Date | Impact on Business | Action Required | +|--------------------|-------------|--------------|------------------------|-------------------|----------------| +| | | Proposed / Comment period / Final rule | | High / Medium / Low | | + +### Compliance Cost Summary + +| Category | One-Time Cost | Annual Recurring Cost | Notes | +|----------|-------------|---------------------|-------| +| Legal | $ | $ | | +| Technical | $ | $ | | +| Operational | $ | $ | | +| **Total** | **$** | **$** | | + +--- + +## Interpretation Guide + +**Enforcement risk calibration:** Regulations with recent enforcement actions in your sector and jurisdiction carry high risk regardless of their theoretical severity. A regulation with harsh penalties but no enforcement history in ten years carries lower practical risk — though this can change rapidly with new political leadership or a high-profile incident. + +**Compliance as competitive advantage:** In regulated industries, compliance infrastructure becomes a moat. Startups that achieve SOC 2 or HIPAA certification early can sell to enterprise customers that competitors cannot reach. Frame compliance cost as customer acquisition cost, not pure overhead. + +**Regulatory velocity by jurisdiction:** The EU moves slowly but comprehensively (GDPR took four years from proposal to enforcement). US federal agencies move in cycles tied to political administration. State-level regulation, particularly in privacy and fintech, is currently the fastest-moving layer. California, New York, and Illinois consistently lead. + +**Cost estimation accuracy:** Initial compliance cost estimates are typically 40-60% below actual costs. Budget for scope creep, technical surprises, and the legal hours required when your implementation raises questions the initial assessment did not anticipate. + +--- + +## Common Pitfalls + +- **Assuming US-only scope.** If your SaaS product has a single EU customer, GDPR applies. If your app is downloaded in Brazil, LGPD applies. Jurisdiction follows the user, not the server. Map where your users are before concluding which regulations apply. +- **Treating compliance as a one-time project.** Regulations change. Enforcement priorities shift. New jurisdictions add new rules. Compliance is an ongoing operational function, not a project with a completion date. Budget for annual audits, policy updates, and regulatory monitoring. +- **Conflating frameworks with regulations.** SOC 2 is a framework, not a law — no one will fine you for lacking it. HIPAA is a law — HHS will fine you for violating it. Frameworks demonstrate compliance; they do not create legal obligations. Prioritize legal requirements over voluntary frameworks. +- **Delaying regulatory research until funding.** By the time you discover that your product requires a money transmitter license in 48 states, you have already promised investors a timeline that does not include 12 months of licensing delays. Research the regulatory landscape before building the financial model, not after. + +--- + +## Output + +Package your regulatory research for use in the following Foreman components: + +- **swot-pest-analysis** — The regulatory inventory feeds directly into the Political/Legal dimension of PEST analysis. Pending regulatory changes inform the Threats and Opportunities quadrants of SWOT. +- **scenario-planning** — Regulatory changes are high-impact, partially predictable external forces. Each pending regulation becomes a scenario variable. Model outcomes under both "regulation passes" and "regulation stalls" conditions. +- **risk-assessment-brief** — The enforcement risk ratings and compliance cost estimates feed the risk register. Non-compliance risks should be quantified as expected fines multiplied by probability of enforcement. +- **regulatory-compliance-update** — The jurisdiction map, regulation inventory, and compliance timeline transfer directly into the periodic compliance update delivered to the board or investors. + +Transfer the jurisdiction map, regulation inventory with enforcement risk ratings, compliance cost summary, and pending changes timeline. Flag any regulation that is both high-enforcement-risk and currently non-compliant — these are urgent action items, not research topics. diff --git a/plugins/foreman/content/research/survey-design-guide.md b/plugins/foreman/content/research/survey-design-guide.md new file mode 100644 index 0000000..ec635a2 --- /dev/null +++ b/plugins/foreman/content/research/survey-design-guide.md @@ -0,0 +1,156 @@ +--- +name: "survey-design-guide" +description: "Guides entrepreneurs through designing, distributing, and + analyzing surveys for quantitative customer research. Covers question design, + sample sizing, bias prevention, and statistical interpretation. Complements + the customer-interview-guide for qualitative depth." +research_type: "customer" +feeds_into_skills: + - net-promoter-score + - four-ps-marketing +feeds_into_templates: [] +estimated_time: "6-10 hours" +data_sources: + - SurveyMonkey + - Typeform + - Google Forms + - Qualtrics + - Pollfish + - Prolific +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis + - kind: research + ref: pricing-research-guide +--- + +# Survey Design Guide + +Surveys are seductive. They promise the comfort of numbers — percentages, averages, distributions — without the awkwardness of sitting across from a real human and hearing uncomfortable truths. That seduction is the danger. A poorly designed survey does not merely fail to produce insight; it produces false insight with the veneer of statistical credibility. The founder who ships a product because "73% of respondents said they'd buy it" has not validated demand. They have validated their ability to write a leading question. + +This guide treats survey design as a research discipline, not a clerical task. The distance between a useful survey and a misleading one is measured in the precision of your questions, the representativeness of your sample, and the honesty of your interpretation. + +--- + +## What You'll Learn + +- When to use a survey versus an interview (and when to use both) +- How to write questions that produce unbiased, actionable data +- The minimum sample size needed for statistical confidence in your findings +- Which distribution channel matches your audience and budget +- How to calculate and interpret NPS, satisfaction scores, and preference rankings +- A framework for identifying and mitigating survey bias + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Google Forms | Basic survey creation with branching logic and auto-charting | Free | forms.google.com | +| Typeform | Conversational survey format with higher completion rates | Freemium (10 responses free) | typeform.com | +| SurveyMonkey | Full survey platform with templates, logic, and analysis | Freemium (limited free) | surveymonkey.com | +| Qualtrics | Enterprise-grade survey with advanced logic, conjoint, and analytics | Paid (academic access often free) | qualtrics.com | +| Pollfish | Access to consumer survey panels with demographic targeting | Paid (per response) | pollfish.com | +| Prolific | Academic-quality participant panel with pre-screening | Paid (per response) | prolific.com | +| Hotjar | In-app surveys triggered by user behavior | Freemium | hotjar.com | +| Cint/Lucid | Programmatic access to survey panels at scale | Paid | cint.com | + +--- + +## Research Protocol + +**Step 1 — Define the Research Question** +Write one sentence describing what decision this survey will inform. Not "learn about our customers" but "determine whether price or feature set is the primary purchase barrier for mid-market prospects." Every question in the survey must serve this sentence. + +**Step 2 — Choose Survey vs. Interview (or Both)** +Surveys provide breadth: patterns across many respondents. Interviews provide depth: the reasoning behind behavior. Use a survey when you need to quantify something you already understand qualitatively. If you cannot yet articulate the possible answers, start with interviews — then survey to measure frequency across a population. + +**Step 3 — Design Questions (Maximum 10-12)** +Each question earns its place by directly serving your research question. Apply these rules: +- One concept per question (never double-barreled: "How satisfied are you with our price and quality?") +- Neutral wording (not "How much do you love our product?" but "How would you rate your experience?") +- Specific timeframes ("In the past 30 days..." not "Do you ever...") +- Balanced scales (5-point Likert with a neutral midpoint); demographics last; open-ended questions limited to 1-2 + +**Step 4 — Pilot with 5 People** +Send the draft to five people who resemble your target audience. Watch them take it (screen share or in person). Note where they hesitate, re-read, or misinterpret. Revise. A $0 pilot prevents a $5,000 wasted panel spend. + +**Step 5 — Calculate Target Sample Size** +For a 95% confidence level with +/- 5% margin of error, you need roughly 385 responses regardless of population size (for populations above 10,000). For smaller populations, use the formula: n = (Z^2 * p * (1-p)) / e^2, where Z=1.96, p=0.5, e=0.05. Adjust for expected response rate — if you anticipate 20% response, you need to reach 5x your target sample. + +**Step 6 — Distribute** +Match channel to audience: +- **Email list:** High trust, moderate response rate (15-30%). Best for existing customers. +- **In-app prompt:** High relevance, captures active users. Risk of annoying power users. +- **Social media:** Broad reach, self-selection bias. Useful for awareness-stage research. +- **Panel (Pollfish/Prolific):** Representative samples on demand. Cost: $1-5 per response. + +**Step 7 — Analyze Results** +Wait until you reach your target sample before analyzing. For Likert scales, report both the mean and the distribution (a mean of 3.5 with bimodal clustering at 1 and 5 tells a different story than a tight cluster at 3-4). Cross-tabulate by key demographics. Flag any question with more than 15% non-response — it likely confused respondents. + +**Step 8 — Cross-Validate with Qualitative Data** +Survey numbers answer "how many" but not "why." Pair surprising findings with 3-5 follow-up interviews targeting respondents who gave unexpected answers. This prevents the most common survey mistake: confident misinterpretation. + +--- + +## Data Collection Template + +### Survey Blueprint + +| # | Question Text | Type | Purpose (What Decision It Informs) | +|---|--------------|------|-----------------------------------| +| 1 | | Likert / MC / Open / NPS | | +| 2 | | Likert / MC / Open / NPS | | +| 3 | | Likert / MC / Open / NPS | | +| ... | | | | + +### Distribution Plan + +| Channel | Audience Segment | Expected Reach | Expected Response Rate | Target Responses | +|---------|-----------------|---------------|----------------------|-----------------| +| | | | % | | +| | | | % | | +| **Total** | | | | | + +### Results Summary + +| Question | n (responses) | Mean / Top Answer | Distribution Pattern | Notable Segment Differences | +|----------|--------------|------------------|---------------------|-----------------------------| +| | | | Normal / Skewed / Bimodal | | +| | | | Normal / Skewed / Bimodal | | + +--- + +## Interpretation Guide + +**NPS interpretation:** Net Promoter Score ranges from -100 to +100. Above 0 is acceptable, above 30 is strong, above 70 is exceptional. More valuable than the score itself is the segmentation: which customer types are promoters versus detractors, and what distinguishes them? + +**Likert scale patterns:** A mean of 4.2 on a 5-point scale with low variance indicates genuine satisfaction. A mean of 3.0 with high variance indicates a polarized audience — two distinct groups with opposing views. The second scenario demands segmentation, not averaging. + +**Statistical significance:** With 385 responses, a 10-percentage-point difference between two groups is statistically significant. A 3-percentage-point difference is not. Resist the temptation to build strategy on noise. + +**Response rate as data:** A 5% response rate from a customer email is itself a finding — your customers may not be engaged enough to spend 3 minutes on a survey. Consider what non-response tells you before fixating on what responders said. + +--- + +## Common Pitfalls + +- **Leading questions.** "Don't you agree that our product saves time?" produces affirmative data that reflects the question's bias, not the respondent's belief. Write questions a stranger could answer without knowing your preferred outcome. +- **Survivorship bias in distribution.** Surveying only active customers about satisfaction excludes the people who were dissatisfied enough to leave. If churn is your concern, you need to reach churned users — a fundamentally different distribution challenge. +- **Survey fatigue inflation.** A 25-question survey with a 12% completion rate produces self-selected data from the most patient (or most opinionated) respondents. Keep surveys under 5 minutes. +- **Treating ordinal data as interval.** A "4" on a Likert scale is not twice a "2." Report medians and distributions alongside means. + +--- + +## Output + +Package your survey research for use in the following Foreman components: + +- **net-promoter-score** — NPS question results feed directly into the NPS framework. Include the score, the promoter/passive/detractor breakdown, and segment-level differences. +- **product-market-fit-diagnosis** — The Sean Ellis question ("How disappointed would you be if you could no longer use this product?") is a single-question survey. Results above 40% "very disappointed" indicate product-market fit. +- **pricing-research-guide** — Van Westendorp or Gabor-Granger pricing questions from your survey feed the pricing sensitivity analysis. Transfer the acceptable price range and willingness-to-pay distribution. +- **four-ps-marketing** — Customer preference data, satisfaction drivers, and channel effectiveness findings inform the Product, Price, Place, and Promotion dimensions. + +Transfer response counts, key distributions, and the cross-tabulation tables. Note the confidence interval for each major finding and flag any result where sample size was below your target. diff --git a/plugins/foreman/content/research/talent-market-research.md b/plugins/foreman/content/research/talent-market-research.md new file mode 100644 index 0000000..b590c15 --- /dev/null +++ b/plugins/foreman/content/research/talent-market-research.md @@ -0,0 +1,147 @@ +--- +name: "talent-market-research" +description: "Guides entrepreneurs through researching the talent market before + hiring — salary benchmarking, talent pool sizing, competitor hiring analysis, + and employer brand assessment. Produces the intelligence needed to design + competitive offers and realistic hiring timelines." +research_type: "market" +feeds_into_skills: [] +feeds_into_templates: + - role-description-template + - ceo-succession-brief +estimated_time: "4-8 hours" +data_sources: + - Glassdoor + - Levels.fyi + - Pave + - Carta Total Comp + - LinkedIn Talent Insights + - Indeed + - H1B Salary Database + - Blind + - Wellfound +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: hiring-diagnosis + - kind: playbook + ref: team-rebuild-playbook + - kind: template + ref: hiring-scorecard +--- + +# Talent Market Research + +Hiring is a market transaction, and like any market transaction, the party with better information captures more value. Most founders approach hiring with a salary figure plucked from a single Glassdoor search, a job description copied from a competitor, and a timeline based on optimism rather than supply data. + +The talent market is researchable. Compensation data is increasingly public. Hiring activity signals strategic intent. Talent pool sizes constrain timelines. This guide provides the protocol for gathering this intelligence before you post the role, not after the third failed offer. + +--- + +## What You'll Learn + +- Salary benchmarks at the 25th, 50th, and 75th percentile for your target role, adjusted by geography and stage +- The size of the available talent pool for your specific requirements +- Which competitors are hiring for similar roles and what their postings reveal about strategy +- A competitive offer structure balancing cash, equity, and non-monetary factors +- A realistic hiring timeline based on market supply, not aspiration + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| Glassdoor | Salary ranges, company reviews, interview process descriptions | Free | glassdoor.com | +| Levels.fyi | Tech compensation: base, stock, bonus by company and level | Free | levels.fyi | +| Pave | Real-time compensation benchmarks by stage, function, and market | Freemium | pave.com | +| Carta Total Comp | Equity compensation benchmarks for venture-backed startups | Paid (free reports) | carta.com | +| LinkedIn Talent Insights | Talent pool sizes, migration patterns, skill availability | Paid | linkedin.com/talent | +| Indeed / BLS | Broad salary data across industries, geographies, and occupations | Free | indeed.com / bls.gov | +| H1B Salary Database | Actual salaries paid to H1B visa holders by company and role | Free | h1bdata.info | +| Wellfound / Blind | Startup job postings with salary/equity; anonymous comp discussions | Free | wellfound.com / teamblind.com | + +--- + +## Research Protocol + +**Step 1 — Define the Role Precisely** +Write a one-paragraph role definition: function, level, key skills, and experience range. "Senior backend engineer with distributed systems experience, 5-8 years" is searchable. "Technical person" is not. + +**Step 2 — Benchmark Salary Range** +Gather compensation data from at least three sources. Record the 25th, 50th, and 75th percentile for base salary and total compensation. Filter by geography (San Francisco commands 40-60% more than Austin) and company stage (Series A typically pays 10-20% below public company base but compensates with equity). + +**Step 3 — Estimate Talent Pool Size** +Use LinkedIn (role title + key skills + geography) to count matching professionals. Discount by 70-80% for passive candidates. Below 200 addressable, expect a long search or broaden requirements. + +**Step 4 — Map Competitor Hiring** +Search job boards for identical roles at talent competitors (similar stage, sector, geography — not necessarily product competitors). Note posted salary ranges, qualifications, and benefits. Patterns reveal strategic priorities. + +**Step 5 — Assess Your Employer Brand** +Read your own Glassdoor reviews as a candidate would. Search Blind. Ask recent hires what almost made them say no. Your employer brand is what candidates discover, not what you declare. + +**Step 6 — Design Competitive Offer Structure** +Construct an offer at or above the 50th percentile for base. Benchmark equity against Carta or Pave for your stage. Identify non-monetary differentiators that your talent pool values. + +--- + +## Data Collection Template + +| Component | 25th Pctl | 50th Pctl | 75th Pctl | Sources | +|-----------|----------|----------|----------|---------| +| Base salary | $ | $ | $ | | +| Bonus + Equity (annual) | $ | $ | $ | | +| **Total compensation** | **$** | **$** | **$** | | + +### Talent Pool & Competitor Activity + +| Filter | Count | Source | +|--------|-------|--------| +| Matching title + skills + geography | | LinkedIn | +| Estimated actively looking (20-30%) | | Calculated | + +| Talent Competitor | Role Title | Posted Salary Range | Strategic Signal | +|-------------------|-----------|--------------------| ------------------| +| | | $ | | +| | | $ | | + +| Signal | Finding | Action Needed? | +|--------|---------|---------------| +| Glassdoor rating / common themes | | | +| Blind sentiment | | | +| Recent hire feedback ("what almost made you say no?") | | | + +--- + +## Interpretation Guide + +**Salary positioning strategy:** The 50th percentile attracts average candidates at average speed. The 75th percentile accelerates hiring but sets a compensation precedent. For critical hires, the premium often pays for itself. + +**Talent pool scarcity signals:** Fewer than 500 matching LinkedIn profiles indicates a tight market. Expect 60-90 day searches and above-median compensation. Consider remote hiring to expand the pool. + +**Competitor posting velocity:** A competitor that posted the same role three times in twelve months is either growing fast or cannot retain. Their retention problem may be your recruiting opportunity. + +**Employer brand asymmetry:** A 3.2 Glassdoor rating citing "great technology, poor management" deters senior candidates. Address the issue or expect to compensate financially. + +--- + +## Common Pitfalls + +- **Single-source salary anchoring.** Using one data point as your benchmark. Compensation data is noisy — three sources, triangulated, produces a defensible range. +- **Ignoring total compensation.** Comparing base salary while ignoring the competitor's equity and bonus. Candidates compare packages, not line items. +- **Geographic arbitrage without transparency.** Hiring remote workers in lower-cost markets at below-market local rates creates resentment when employees discover the disparity. Transparent compensation bands prevent retention crises. +- **Conflating talent competitors with product competitors.** Your talent competes with Google, the well-funded startup down the street, and the hedge fund that just opened a tech office — not just your product competitors. + +--- + +## Output + +Package your talent market research for use in the following Foreman components: + +- **hiring-diagnosis** — Salary benchmarks and talent pool data feed the diagnostic that evaluates whether a hiring challenge stems from compensation, brand, process, or market factors. +- **team-rebuild-playbook** — Competitor hiring signals and talent pool estimates inform sequencing and timeline for rebuilding a team. Market data prevents unrealistic hiring plans. +- **hiring-scorecard** — The role definition and required skills from Step 1 become evaluation criteria. Salary benchmarks set offer parameters. +- **role-description-template** — Competitive analysis of job postings informs how to position your role against alternatives candidates are evaluating. +- **ceo-succession-brief** — For executive searches, salary benchmarks, talent pool size, and competitor data inform the board on search difficulty and compensation requirements. + +Transfer the salary benchmark table, talent pool estimate, and competitor activity summary. Flag any finding that materially changes your hiring assumptions. diff --git a/plugins/foreman/content/research/technology-stack-research.md b/plugins/foreman/content/research/technology-stack-research.md new file mode 100644 index 0000000..3b0259c --- /dev/null +++ b/plugins/foreman/content/research/technology-stack-research.md @@ -0,0 +1,139 @@ +--- +name: "technology-stack-research" +description: "Guides entrepreneurs through evaluating technology choices — build vs buy, framework selection, and infrastructure decisions. Produces scored comparisons, total cost of ownership calculations, and documented decision rationale for technical architecture." +research_type: "technical" +feeds_into_skills: + - defining-and-exploring-problems + - evaluating-and-deciding +feeds_into_templates: + - decision-rationale-memo + - new-initiative-brief +estimated_time: "6-12 hours" +data_sources: + - StackOverflow Developer Survey + - GitHub + - G2 + - Capterra + - ThoughtWorks Technology Radar + - Hacker News + - AWS/GCP/Azure Pricing Calculators +author: "Fatih Guner" +--- + +# Technology Stack Research + +Every technology decision is a bet placed with borrowed time. Choose the wrong framework and you rewrite in eighteen months. Choose the wrong vendor and you discover lock-in only when you try to leave. Choose to build what you should have bought and your engineers spend a year recreating commodity infrastructure instead of building differentiation. The cost of a bad technology decision is rarely the sticker price -- it is the compounding drag on velocity that surfaces six quarters later, when reversing course is most expensive. Whether selecting a database, choosing between building in-house or licensing, or deciding which cloud provider anchors your infrastructure, the process remains the same: define requirements, enumerate options, score honestly, calculate total cost, and document the rationale. + +--- + +## What You'll Learn + +- A structured requirements matrix separating must-haves from nice-to-haves +- A scored comparison of build vs buy options against weighted criteria +- Total cost of ownership calculations covering license, infrastructure, maintenance, and opportunity cost +- A vendor lock-in risk assessment for each finalist +- Community and ecosystem health indicators for open-source options +- A documented decision rationale ready for stakeholder review + +--- + +## Data Sources + +| Source | What It Provides | Free/Paid | Access | +|--------|-----------------|-----------|--------| +| StackOverflow Developer Survey | Adoption rates, satisfaction scores, technology trends | Free | survey.stackoverflow.co | +| GitHub | Stars, commit activity, issue response time, contributor count, release cadence | Free | github.com | +| G2 / Capterra | User reviews, feature comparisons, pricing for SaaS tools | Free | g2.com / capterra.com | +| ThoughtWorks Technology Radar | Opinionated maturity assessment (Adopt, Trial, Assess, Hold) | Free | thoughtworks.com/radar | +| InfoQ Trends Reports | Technology adoption curves across architecture, DevOps, AI | Free | infoq.com/articles | +| Hacker News | Developer sentiment, critical reviews, undocumented gotchas | Free | Search via hn.algolia.com | +| AWS/GCP/Azure Pricing Calculators | Infrastructure cost modeling per workload | Free | calculator.aws / cloud.google.com/products/calculator | +| DB-Engines | Database popularity rankings and trend data | Free | db-engines.com | + +--- + +## Research Protocol + +**Step 1 -- Define Technical Requirements** +List every requirement the technology must satisfy. Classify each as Must-Have (non-negotiable) or Nice-to-Have (valued but tradeable). Common dimensions: performance thresholds, scalability ceiling, security certifications, integration points, team expertise, deployment model, and compliance constraints. Limit must-haves to 5-7; if everything is critical, nothing is. + +**Step 2 -- Enumerate Options** +Always include a "build in-house" option alongside 3-5 buy/adopt alternatives. For open-source options, record the license type, governance model, and primary maintainer (company-backed vs community). For proprietary options, record pricing model, contract terms, and data portability provisions. + +**Step 3 -- Score Against Requirements** +Build a weighted scoring matrix. Assign each must-have a weight of 3 and each nice-to-have a weight of 1. Score each option 0-3 per criterion (0 = does not meet, 1 = partially meets, 2 = meets, 3 = exceeds). Multiply scores by weights and sum. Any option scoring 0 on a must-have is eliminated regardless of total score. + +**Step 4 -- Calculate TCO for Top 3** +For each finalist, estimate 3-year total cost of ownership across four categories: license/subscription fees, infrastructure costs, maintenance effort (engineering hours at loaded rate), and opportunity cost (what your team cannot build while integrating or maintaining this choice). The cheapest option by license is rarely cheapest by TCO. + +**Step 5 -- Assess Vendor and Lock-in Risk** +For each finalist, evaluate: data export capabilities, API standard compliance (proprietary vs open standards), contractual exit terms, migration effort estimate, and the vendor's financial stability. Open-source mitigates some lock-in but introduces maintenance liability. + +**Step 6 -- Prototype the Winner** +Spend 2-5 days building a minimal proof of concept with the top-scoring option. Test specifically against must-have requirements and integration points. A prototype reveals friction that documentation conceals. + +**Step 7 -- Document the Decision** +Record what you chose, what you rejected, and the reasoning. Future engineers will inherit this decision; give them the context to understand it or challenge it intelligently. + +--- + +## Data Collection Template + +### Scoring Matrix + +| Requirement | Weight | Build | Option A | Option B | Option C | +|-------------|--------|-------|----------|----------|----------| +| [Requirement] | | /3 | /3 | /3 | /3 | +| **Weighted Total** | | **__** | **__** | **__** | **__** | + +### TCO Comparison (3-Year) + +| Cost Category | Build | Option A | Option B | +|---------------|-------|----------|----------| +| License / subscription | $ | $ | $ | +| Infrastructure (compute, storage, network) | $ | $ | $ | +| Maintenance (engineering hours x rate) | $ | $ | $ | +| Opportunity cost estimate | $ | $ | $ | +| **3-Year Total** | **$** | **$** | **$** | + +### Open-Source Health Check + +| Indicator | Option A | Option B | +|-----------|----------|----------| +| GitHub stars / monthly contributors | | | +| Median issue response time | | | +| Last release date / corporate backer | | | +| License type | | | + +--- + +## Interpretation Guide + +**High score, low TCO -- straightforward choice.** When the weighted scoring leader also wins on total cost, the decision is clean. Document it and move. + +**High score, high TCO -- value trade-off.** The best technical fit costs more. Quantify the premium and ask: does the capability gap justify 2-3x the cost? Sometimes it does, especially when the alternative requires engineering time that exceeds the price difference. + +**Build wins on capability but loses on TCO.** Custom-built solutions score perfectly on requirements because you design them that way. The honest test: does maintenance drag over three years erode the initial fit advantage? Most startups underestimate maintenance by 3-5x. + +**Community health is declining.** Decreasing contributors, lengthening issue response times, or stale releases signal a project entering maintenance mode. Adopting it now means inheriting future migration costs. Weight this heavily for infrastructure-level dependencies. + +--- + +## Common Pitfalls + +- **Optimizing for day-one fit over year-three cost.** The technology that is easiest to adopt today may be hardest to scale or migrate away from tomorrow. Always model the three-year horizon. +- **Ignoring opportunity cost.** "Build" options appear cheaper when you exclude the value of what engineers could have shipped instead. A senior engineer spending six months on internal tooling has a real opportunity cost exceeding most SaaS contracts. +- **Conflating popularity with suitability.** A technology's GitHub stars reflect general interest, not fitness for your specific requirements. Score against your matrix, not the community's enthusiasm. +- **Skipping the prototype.** Documentation describes the ideal case. A two-day prototype exposes the integration friction, edge-case behaviour, and developer experience that no vendor page will admit. +- **Undocumented decisions.** A technology choice made without recorded rationale becomes a mystery within two years. The next engineer cannot evaluate whether the original constraints still hold. + +--- + +## Output + +Package your technology evaluation for use in the following Foreman skills and templates: + +- **Skills**: `defining-and-exploring-problems` (requirements matrix clarifies technical constraints), `evaluating-and-deciding` (scoring matrix and TCO feed structured decision frameworks) +- **Templates**: `decision-rationale-memo` (documented choice and rejected alternatives transfer directly), `new-initiative-brief` (technology selection informs feasibility and resourcing sections) + +Transfer the scoring matrix, TCO comparison, vendor risk assessment, and prototype findings. Flag which assumptions carry the most uncertainty -- these become technical validation priorities. diff --git a/plugins/foreman/content/research/user-testing-protocol.md b/plugins/foreman/content/research/user-testing-protocol.md new file mode 100644 index 0000000..df20bd1 --- /dev/null +++ b/plugins/foreman/content/research/user-testing-protocol.md @@ -0,0 +1,139 @@ +--- +name: "user-testing-protocol" +description: "Comprehensive protocol for planning and executing user and + usability testing. Covers moderated and unmoderated testing, task-based + protocols, think-aloud method, A/B testing, prototype testing, and first-click + testing with structured note-taking templates." +research_type: "customer" +feeds_into_skills: + - net-promoter-score +feeds_into_templates: + - new-initiative-brief +estimated_time: "10-20 hours" +data_sources: + - existing-users + - recruited-participants + - analytics-platforms + - session-recording-tools +author: "Fatih Guner" +related_content: + - kind: diagnostic + ref: product-market-fit-diagnosis + - kind: playbook + ref: product-market-fit-playbook + - kind: template + ref: new-initiative-brief + - kind: diagnostic + ref: product-market-fit-diagnosis +--- + +# User Testing Protocol + +## Purpose + +Opinions about your product are abundant. Evidence about how people actually use it is scarce. This guide provides a structured protocol for observing real behaviour -- not collecting preferences, not running focus groups, not asking users what they want. The goal is to watch people attempt tasks and measure where they succeed, struggle, and abandon. + +## What You'll Learn + +- How to select the right testing method for your research question +- How to write task scenarios that reveal genuine usability problems +- How to recruit participants who represent your target segments +- How to moderate sessions that produce actionable data without leading the witness +- How to synthesize findings into prioritised fixes with clear severity ratings + +## Data Sources + +| Source | What It Provides | Access Method | +|--------|-----------------|---------------| +| Existing users | Behaviour data from people with real usage context | In-app recruitment, email outreach, CRM segment | +| Recruited participants (UserTesting, Maze, UsabilityHub) | Fresh perspectives from people matching your ICP | Platform-based recruitment with screener surveys | +| Analytics (Hotjar, FullStory, Amplitude) | Quantitative behaviour patterns: funnels, rage clicks, drop-offs | Configure event tracking; export funnel and session data | +| Session recordings | Frame-by-frame interaction evidence | Hotjar, FullStory, or Loom for moderated sessions | +| Prototype tools (Figma, InVision) | Clickable prototypes for pre-build testing | Share prototype links with participants | + +## Research Protocol + +### Step 1: Define What You Are Testing and Why + +Write a single research question. Not "is our product good?" but "can a new user complete their first project setup within 5 minutes without assistance?" Choose one method: + +- **Moderated testing**: Facilitator guides participants through tasks in real time. Best for exploratory research and capturing the "why" behind behaviour. +- **Unmoderated testing**: Participants complete tasks independently via a platform. Best for validation at scale and geographic diversity. +- **A/B testing**: Two variants measured against a conversion metric. Best for optimising specific elements with sufficient traffic. +- **First-click testing**: Measures where users click first on a page. Best for navigation and information hierarchy validation. +- **Prototype testing**: Task-based testing on a clickable prototype. Best for pre-build validation of new features or redesigns. + +### Step 2: Write 3-5 Task Scenarios + +Each scenario should be realistic, specific (clear completion criteria), and unbiased (does not reveal the "right" answer). Frame tasks as goals, not instructions. Write "You need to invite a colleague to your project" rather than "Click the settings icon and select team members." + +### Step 3: Recruit 5-8 Participants Per Segment + +Five participants per segment uncover approximately 80% of usability problems. Recruit through your user base, third-party platforms with screener surveys, or social channels with incentives. Screen out people too familiar with your product and people with no relevance to your target segment. + +### Step 4: Run Sessions (30-45 Minutes Each) + +For moderated sessions: **Minutes 1-5** -- introduction, consent, think-aloud instructions. **Minutes 5-35** -- task execution; observe silently; prompt with "What are you thinking?" when participants go quiet. **Minutes 35-45** -- debrief on confusion points and comparisons to existing tools. + +For unmoderated sessions, configure the platform with: task instructions, time limits, post-task satisfaction questions (1-7 scale), and a final open-response question. + +### Step 5: Synthesize Findings + +Compile data per task: success rate, average completion time, error frequency, satisfaction scores, and verbatim quotes. Patterns across three or more participants are signal; isolated incidents are noise. + +### Step 6: Prioritize Fixes + +| Severity | Definition | Action | +|----------|-----------|--------| +| Critical | Task failure for majority; core goal unreachable | Fix before next release | +| Major | Completed with significant difficulty or errors | Fix within current sprint | +| Minor | Completed with slight confusion | Backlog; batch with related work | +| Cosmetic | Noticed but did not impede completion | Fix opportunistically | + +## Data Collection Template + +``` +SESSION NOTE-TAKING FORM +Session ID: ___ Date: ___________ Participant: ___________ Segment: _______________ + +TASK 1: _______________ + Result: [ ] Complete [ ] Partial [ ] Fail | Time: ___m ___s | Errors: ___ | Satisfaction: ___/7 + Quotes: "_______________" | Observations: _______________ + +TASK 2: _______________ + Result: [ ] Complete [ ] Partial [ ] Fail | Time: ___m ___s | Errors: ___ | Satisfaction: ___/7 + Quotes: "_______________" | Observations: _______________ + +TASK 3: _______________ + Result: [ ] Complete [ ] Partial [ ] Fail | Time: ___m ___s | Errors: ___ | Satisfaction: ___/7 + Quotes: "_______________" | Observations: _______________ + +OVERALL + Most confusing element: _______________ + Expected but missing: _______________ + Comparison to current tools: _______________ +``` + +## Interpretation Guide + +**Strong product signal**: Task success above 85%, satisfaction above 5/7. Friction is minor and cosmetic. The interaction model matches user mental models. + +**Iteration needed**: Success rate 60-85%. Users complete goals but with workarounds, backtracking, or confusion. Core flow works; details need refinement. + +**Structural problem**: Success below 60%. Users cannot accomplish primary goals -- a fundamental mismatch between interaction model and expectations. Redesign the flow before optimising details. + +## Common Pitfalls + +- **Leading the participant**: "Did you notice the blue button?" biases attention. Ask "What would you do next?" instead. +- **Testing with colleagues**: Internal testers navigate by memory, not by interface logic. +- **Too many tasks per session**: Fatigue degrades data quality after 30 minutes. Five tasks is the practical ceiling. +- **Ignoring think-aloud gaps**: When a participant goes silent, they are usually struggling. The silence is data. +- **Fixing everything at once**: Shipping twenty minor fixes while ignoring two critical failures is optimising the wrong layer. + +## Output + +This research feeds directly into the following Foreman components: + +- **Skills**: `net-promoter-score` (satisfaction benchmarking), `product-market-fit-diagnosis` (usage quality evidence), `product-market-fit-playbook` (iteration inputs) +- **Templates**: `new-initiative-brief` (user evidence section), `product-market-fit-diagnosis` (qualitative data inputs) +- **Playbooks**: `product-market-fit-playbook` (uses testing data to validate or invalidate PMF signals) diff --git a/plugins/foreman/content/runtime/package.json b/plugins/foreman/content/runtime/package.json new file mode 100644 index 0000000..f9ec9b6 --- /dev/null +++ b/plugins/foreman/content/runtime/package.json @@ -0,0 +1 @@ +{"type":"module","private":true} diff --git a/plugins/foreman/content/runtime/run.mjs b/plugins/foreman/content/runtime/run.mjs new file mode 100644 index 0000000..9dde771 --- /dev/null +++ b/plugins/foreman/content/runtime/run.mjs @@ -0,0 +1,4 @@ +#!/usr/bin/env node +import { runStateCLI } from './state-cli.js'; +try { console.log(JSON.stringify(runStateCLI(process.argv.slice(2)),null,2)); } +catch(e) { console.error(e.message); process.exitCode=1; } diff --git a/plugins/foreman/content/runtime/state-cli.js b/plugins/foreman/content/runtime/state-cli.js new file mode 100644 index 0000000..988f449 --- /dev/null +++ b/plugins/foreman/content/runtime/state-cli.js @@ -0,0 +1,39 @@ +import fs from 'node:fs'; +import path from 'node:path'; +import { changeState, readState, updateProfile, updateTask, track, migrateState, identifier } from './state.js'; + +export function runStateCLI(args) { + const [command,...rest] = args; + if (!command || command === '--help' || rest.includes('--help')) return {usage:'profile [--mode standard|solo] [--stoic on|off] [--language tr] [--sector saas]; task --id ID [--description TEXT] [--status STATE] [--progress 0..100] [--deadline YYYY-MM-DD] [--note TEXT]; track [--filter all|active|overdue|stalled|STATE]; resume [--playbook ID --step N]; migrate --input legacy.json. Common: --workspace DIR --founder ID --revision N'}; + const opts = {}; + for(let i=0;i changeState(workspace,founder,fn,{expectedRevision: opts.revision === undefined ? undefined : Number(opts.revision)}); + if (command === 'profile') { + const changes = {}; + for (const key of ['mode','language','sector']) if (opts[key] !== undefined) changes[key]=opts[key]; + if (opts.stoic !== undefined) { if (!['on','off'].includes(opts.stoic)) throw new Error('stoic must be on or off'); changes.stoic_mode=opts.stoic==='on'; } + return Object.keys(changes).length ? mutate(s=>updateProfile(s,changes)) : readState(workspace,founder); + } + if (command === 'task') { + const input = Object.fromEntries(allowed.filter(k => opts[k] !== undefined).map(k=>[k,opts[k]])); + if (input.progress !== undefined) input.progress=Number(input.progress); + if (input.deadline === 'none') input.deadline=null; + return mutate(s=>updateTask(s,input)); + } + if (command === 'track') return {items:track(readState(workspace,founder),opts.filter || 'all')}; + if (command === 'resume') { + if (opts.playbook !== undefined || opts.step !== undefined) return mutate(s=>{identifier(opts.playbook);s.active.playbook={id:opts.playbook,next_step:Number(opts.step)};return s;}); + return readState(workspace,founder).active.playbook; + } + if (!opts.input) throw new Error('migrate requires --input legacy.json'); + const legacy = JSON.parse(fs.readFileSync(path.resolve(opts.input),'utf8')); + return mutate(s=>{if (s.revision !== 0) throw new Error('Migration requires an unused founder destination');return migrateState(legacy,founder);}); +} diff --git a/plugins/foreman/content/runtime/state.js b/plugins/foreman/content/runtime/state.js new file mode 100644 index 0000000..5db5878 --- /dev/null +++ b/plugins/foreman/content/runtime/state.js @@ -0,0 +1,150 @@ +// Runtime state is deliberately dependency-free so every distribution uses it. +import fs from 'node:fs'; +import path from 'node:path'; +import { randomUUID } from 'node:crypto'; + +export const STATUSES = ['not-started','in-progress','blocked','completed','abandoned','deferred']; +export const SECTORS = ['saas','marketplace','e-commerce','fintech','ai-ml','healthtech','edtech','d2c-consumer','agency-consulting','']; +const LANGUAGES = { english:'en',default:'en',turkish:'tr','türkçe':'tr',spanish:'es',french:'fr',german:'de',japanese:'ja',chinese:'zh',portuguese:'pt',arabic:'ar',korean:'ko',italian:'it',russian:'ru',hindi:'hi',dutch:'nl' }; +export function language(value) { + if (typeof value !== 'string' || !value.trim() || value.length > 60 || /[\x00-\x1f]/.test(value)) throw new Error('Invalid language'); + const v = value.trim().toLowerCase(); + return LANGUAGES[v] || v; +} +export function identifier(id) { + if (typeof id !== 'string' || !/^[a-z0-9][a-z0-9_-]{0,79}$/i.test(id)) throw new Error('Invalid identifier'); + return id; +} +export function newState(founder = 'default', defaults = {}) { + identifier(founder); + return { schema_version:1, founder_id:founder, revision:0, + identity:{mode:defaults.defaultMode === 'solo' ? 'solo' : 'standard',stoic_mode:defaults.defaultMode === 'stoic',language:language(defaults.defaultLanguage || 'en')}, + company:{sector:defaults.sector || ''}, active:{playbook:null}, implementation_items:[], history:[] }; +} +function date(value) { + if (value === null) return true; + return typeof value === 'string' && /^\d{4}-\d{2}-\d{2}$/.test(value) && Number.isFinite(Date.parse(value)) && new Date(value).toISOString().slice(0,10) === value; +} +export function validateState(s) { + if (!s || s.schema_version !== 1) throw new Error('Unsupported state schema; migrate explicitly'); + identifier(s.founder_id); + if (!Number.isInteger(s.revision) || s.revision < 0) throw new Error('Invalid revision'); + if (!['standard','solo'].includes(s.identity?.mode) || typeof s.identity.stoic_mode !== 'boolean') throw new Error('Invalid operating mode'); + language(s.identity.language); + if (!s.company || !SECTORS.includes(s.company.sector)) throw new Error('Unknown sector'); + if (!s.active || !Array.isArray(s.implementation_items) || !Array.isArray(s.history)) throw new Error('Invalid state collections'); + if (s.active.playbook !== null) { + identifier(s.active.playbook?.id); + if (!Number.isInteger(s.active.playbook.next_step) || s.active.playbook.next_step < 1) throw new Error('Invalid playbook checkpoint'); + } + const ids = new Set(); + for (const item of s.implementation_items) { + identifier(item.id); + if (ids.has(item.id)) throw new Error(`Duplicate task: ${item.id}`); + ids.add(item.id); + if (typeof item.description !== 'string' || !item.description.trim()) throw new Error('Task description required'); + if (!STATUSES.includes(item.status) || !Number.isInteger(item.progress) || item.progress < 0 || item.progress > 100) throw new Error('Invalid task status or progress'); + if (item.status === 'completed' && item.progress !== 100) throw new Error('Completed tasks require 100% progress'); + if (item.status === 'not-started' && item.progress !== 0) throw new Error('Not-started tasks require 0% progress'); + if (!date(item.deadline) || !Array.isArray(item.notes) || !Array.isArray(item.state_history)) throw new Error('Invalid task deadline or history'); + } + return s; +} + +function statePath(workspace, founder, create = false) { + if (!workspace || !path.isAbsolute(workspace)) throw new Error('An absolute workspace directory is required for persistent state'); + identifier(founder); + let dir = workspace; + for (const part of ['.foreman',founder]) { + dir = path.join(dir,part); + if (fs.existsSync(dir) && fs.lstatSync(dir).isSymbolicLink()) throw new Error(`Linked state directory is not supported: ${dir}`); + if (create) fs.mkdirSync(dir,{recursive:true,mode:0o700}); + } + const file = path.join(dir,'state.json'); + try { if (fs.lstatSync(file).isSymbolicLink()) throw new Error('Linked state file is not supported'); } + catch(e) { if (e.code !== 'ENOENT') throw e; } + return file; +} +export function readState(workspace, founder = 'default', defaults = {}) { + const file = statePath(workspace,founder); + if (!fs.existsSync(file)) return validateState(newState(founder,defaults)); + const s = validateState(JSON.parse(fs.readFileSync(file,'utf8'))); + if (s.founder_id !== founder) throw new Error('State founder does not match selected founder'); + return s; +} +export function changeState(workspace, founder = 'default', mutate, { defaults = {}, expectedRevision } = {}) { + const file = statePath(workspace,founder,true), lock = file + '.lock'; + let fd; + try { fd = fs.openSync(lock,'wx',0o600); } + catch(e) { if (e.code === 'EEXIST') throw new Error('State is locked by another writer; retry after it finishes'); throw e; } + const tmp = `${file}.${randomUUID()}.tmp`; + try { + const state = readState(workspace,founder,defaults); + if (expectedRevision !== undefined && state.revision !== expectedRevision) throw new Error('State revision conflict; read the latest state before retrying'); + const draft = structuredClone(state); + const next = mutate(draft) || draft; + next.revision = state.revision + 1; + validateState(next); + if (next.founder_id !== founder) throw new Error('Cannot change founder identity'); + fs.writeFileSync(tmp,JSON.stringify(next,null,2)+'\n',{flag:'wx',mode:0o600}); + const sync = fs.openSync(tmp,'r'); try { fs.fsyncSync(sync); } finally { fs.closeSync(sync); } + fs.renameSync(tmp,file); + return next; + } finally { fs.closeSync(fd); fs.rmSync(lock,{force:true}); fs.rmSync(tmp,{force:true}); } +} +export function updateProfile(state, changes) { + for (const [key,value] of Object.entries(changes)) { + if (key === 'mode') state.identity.mode = value; + else if (key === 'stoic_mode') state.identity.stoic_mode = value; + else if (key === 'language') state.identity.language = language(value); + else if (key === 'sector') state.company.sector = value; + else throw new Error(`Unknown profile field: ${key}`); + } + return validateState(state); +} +export function updateTask(state, input, now = new Date()) { + identifier(input.id); + const allowed = ['id','description','owner','deadline','status','progress','note']; + for (const key of Object.keys(input)) if (!allowed.includes(key)) throw new Error(`Unknown task field: ${key}`); + let item = state.implementation_items.find(x => x.id === input.id); + if (!item) { + if (!input.description?.trim()) throw new Error('A new task requires a description'); + item = {id:input.id,description:input.description,owner:'self',deadline:null,status:'not-started',progress:0,notes:[],state_history:[],created:now.toISOString(),updated:now.toISOString()}; + state.implementation_items.push(item); + } + const previous = item.status; + for (const key of ['description','owner','deadline','status','progress']) if (input[key] !== undefined) item[key] = input[key]; + if (input.status === 'completed') item.progress = 100; + else if (input.status === 'not-started') item.progress = 0; + else if (input.progress !== undefined && input.status === undefined) item.status = input.progress === 100 ? 'completed' : input.progress > 0 ? 'in-progress' : 'not-started'; + if (input.note !== undefined) { + if (typeof input.note !== 'string' || !input.note.trim()) throw new Error('A note must be nonempty text'); + item.notes.push({date:now.toISOString(),note:input.note}); + } + if (previous !== item.status) item.state_history.push({from:previous,to:item.status,date:now.toISOString()}); + item.updated = now.toISOString(); + state.history.push({event:'task-updated',id:item.id,date:now.toISOString()}); + return validateState(state); +} +export function track(state, filter = 'all', now = new Date()) { + if (!['all','active','overdue','stalled',...STATUSES].includes(filter)) throw new Error(`Unknown tracking filter: ${filter}`); + const active = t => !['completed','abandoned'].includes(t.status); + return state.implementation_items.filter(t => filter === 'all' || (filter === 'active' ? active(t) : filter === 'overdue' ? active(t) && t.deadline && t.deadline < now.toISOString().slice(0,10) : filter === 'stalled' ? active(t) && now.getTime() - Date.parse(t.updated || t.created) >= 14*86400000 : t.status === filter)); +} +export function migrateState(legacy, founder = 'default') { + if (legacy.schema_version === 1) return validateState({...structuredClone(legacy),founder_id:founder}); + const s = newState(founder), identity = legacy.identity || {}, prefs = legacy.preferences || identity.preferences || {}; + s.identity = {...identity,mode:identity.mode || ((identity.mode_solo ?? prefs.solo_mode) ? 'solo' : 'standard'),stoic_mode:identity.stoic_mode ?? identity.mode_stoic ?? prefs.stoic_mode ?? false,language:language(identity.language || prefs.language || 'en')}; + if (s.identity.mode === 'stoic') { s.identity.mode='standard'; s.identity.stoic_mode=true; } + delete s.identity.mode_solo; delete s.identity.mode_stoic; delete s.identity.preferences; + s.company = {...legacy.company,sector:legacy.company?.sector || ''}; + s.active = {...legacy.active,playbook:legacy.active?.playbook || null}; + for (const old of legacy.implementation_items || legacy.active?.implementation_items || []) { + const status = old.status || 'not-started'; + const item = {...old,deadline:old.deadline || null,status,progress:old.progress ?? (status === 'completed' ? 100 : 0),notes:old.notes || [],state_history:old.state_history || []}; + s.implementation_items.push(item); + } + s.history = Array.isArray(legacy.history) ? legacy.history : []; + s.legacy = structuredClone(legacy); // Preserve source fields without using two active schemas. + return validateState(s); +} diff --git a/plugins/foreman/content/simulation/SIMULATION.md b/plugins/foreman/content/simulation/SIMULATION.md new file mode 100644 index 0000000..d7bd9d4 --- /dev/null +++ b/plugins/foreman/content/simulation/SIMULATION.md @@ -0,0 +1,148 @@ + + +# Board Simulation -- Adversarial Rehearsal for High-Stakes Presentations + +Every competent founder can produce a board deck. Fewer can defend one. The gap between preparing a document and surviving the room where that document is questioned, challenged, and dismantled by experienced investors is vast, consequential, and almost never rehearsed. Founders spend weeks perfecting slides and hours memorizing talking points, then walk into a board meeting or investor pitch with zero practice at the one skill that determines the outcome: responding under pressure. + +Board Simulation closes that gap. It places the entrepreneur in an adversarial role-play with an AI that assumes the persona of a specific board archetype -- the relentless skeptic, the operational inquisitor, the financial hawk, the industry veteran, or the supportive challenger. The simulation takes the entrepreneur's own output template (board update, investor deck, strategic review) as input, interrogates it across 5-7 rounds, scores the performance, identifies weaknesses, and persists the results so improvement can be tracked over time. + +This is not a friendly review. It is a rehearsal for a room that will not be friendly. + +--- + +## Why Simulation Matters + +Three reasons: + +1. **Knowledge does not equal articulation.** A founder may understand unit economics deeply and still fumble when a board member asks "Why is your CAC rising faster than LTV?" The gap between knowing and communicating under pressure is a separate skill. +2. **Documents hide weaknesses.** A polished deck can obscure thin evidence, incoherent strategy, or unaddressed risks. Live questioning exposes what the document conceals. +3. **Confidence is trained, not innate.** The founder who has rehearsed against a hostile persona five times enters the real meeting differently than the one who has rehearsed zero times. The questions will not be identical, but the muscle memory of composure will be. + +--- + +## Three Simulation Types + +### Board Meeting Simulation + +Replicates a formal board meeting where the entrepreneur presents a company update and fields questions from a seated board member. Typical duration: 5-7 rounds of Q&A. Input: any board-audience output template (board update, quarterly review, strategic review). The persona reads the material, then interrogates it. + +### Investor Pitch Simulation + +Replicates a VC pitch meeting -- shorter, higher stakes, faster pace. The persona plays a potential investor hearing the pitch for the first time. Typical duration: 5-6 rounds. Input: any investor-audience output template (fundraising deck, unit economics snapshot, competitive landscape brief). Focus areas: market size, traction proof, team credibility, return thesis. + +### Due Diligence Simulation + +Replicates a technical DD session where every claim is verified and every number is traced to its source. The persona plays a DD analyst or lead investor during a later-stage evaluation. Typical duration: 6-7 rounds. Input: financial models, due diligence materials, operational data. Focus areas: data integrity, assumption validity, risk disclosure, legal and financial exposure. + +--- + +## How a Simulation Works + +**Step 1 -- Select simulation type.** The entrepreneur chooses board meeting, investor pitch, or due diligence via `/simulate board`, `/simulate investor-pitch`, or `/simulate due-diligence`. + +**Step 2 -- Choose or receive a persona.** The entrepreneur specifies a persona (e.g., `--persona skeptic-investor`) or the system assigns one based on the entrepreneur's weakest scoring dimension from prior simulations. First-time users receive `friendly-challenger` by default. + +**Step 3 -- Present material.** The entrepreneur provides an output template as the basis for the simulation. The persona reads and internalizes the material before questioning begins. + +**Step 4 -- Q&A rounds (5-7 rounds).** The persona asks questions in character, probing weaknesses, challenging assumptions, and testing the entrepreneur's command of the material. Each round consists of one question or follow-up and the entrepreneur's response. The persona adapts based on the quality of responses -- weak answers trigger harder follow-ups. + +**Step 5 -- Scoring.** After the final round, the system scores the performance across five dimensions (see Scoring Framework below). Scores range from 1 to 5 per dimension with a weighted composite. + +**Step 6 -- Weakness analysis.** The system identifies the 2-3 most significant weaknesses revealed during the simulation and classifies them as content gaps (missing data, thin evidence) or delivery gaps (had the data but could not articulate it). + +**Step 7 -- Memory persistence.** Simulation results are written to the history memory layer, enabling the entrepreneur to track improvement across multiple simulations. The post-simulation diagnostic runs automatically to route weaknesses to relevant skills and research guides. + +--- + +## The Persona System + +Five board personas, each with a distinct worldview, questioning style, and set of priorities. Personas are not caricatures -- they represent real archetypes found in boardrooms and investor meetings worldwide. + +| Persona | Archetype | Primary Concern | Recommended For | +|---------|-----------|-----------------|-----------------| +| `skeptic-investor` | "Show me the money" | Market assumptions and growth projections | Founders preparing for fundraising | +| `operational-expert` | "How will you actually do this?" | Execution capability and operational plans | Founders with ambitious roadmaps | +| `financial-hawk` | "Where are the numbers?" | Unit economics, burn, and capital efficiency | Founders presenting financial models | +| `industry-veteran` | "I have seen this before" | Market dynamics and competitive positioning | Founders in competitive or regulated markets | +| `friendly-challenger` | "Help me believe in this" | Overall story coherence and preparedness | First-time simulation users | + +Persona files reside in `.claude/simulation/board-personas/`. Each defines the persona's questioning style, priority areas, typical questions, what impresses them, what triggers their skepticism, and their scoring bias. + +--- + +## Scoring Framework + +Five dimensions, each scored 1-5. Full specification in `simulation-scoring.yaml`. + +1. **Clarity** -- Was the presentation structured, focused, and comprehensible? +2. **Evidence** -- Were claims backed by data, research, or credible reasoning? +3. **Strategic Coherence** -- Does the strategy hold together? Are goals, actions, and resources aligned? +4. **Risk Awareness** -- Were risks identified, quantified, and mitigated -- or concealed? +5. **Response Quality** -- Under direct questioning, did the entrepreneur defend, adapt, or collapse? + +Each persona weights these dimensions differently. The financial hawk weights Evidence and Risk Awareness heavily. The operational expert weights Strategic Coherence and Response Quality. Composite scores produce an overall grade (A-F) with actionable improvement priorities. + +--- + +## Integration with Output Templates + +Simulation consumes output templates as input material. The following template audiences serve as natural simulation inputs: + +- **Board templates** (7): Board update, quarterly review, strategic plan -- natural inputs for board meeting simulation +- **Investor templates** (10): Fundraising deck, unit economics, competitive landscape -- natural inputs for investor pitch simulation +- **Self templates** (10): Decision journals, retrospectives -- can serve as preparation notes before simulation + +The entrepreneur runs `/output [template-name]`, produces the completed document, then runs `/simulate [type]` to rehearse defending it. + +--- + +## Integration with Memory + +Simulation results persist across sessions through the memory system. + +- **Session layer**: Current simulation state, round history, in-progress scores +- **Active layer**: Most recent simulation results, improvement targets +- **History layer**: All past simulation results with scores, enabling trend analysis + +The `/simulate history` command retrieves past results. The system uses historical scores to recommend personas that target the entrepreneur's weakest dimensions and to detect improvement patterns. + +--- + +## Integration with Playbooks + +Two playbooks explicitly reference simulation as a final preparation step: + +- **`fundraising-playbook`**: After completing the pitch deck and financial model, the playbook recommends running an investor pitch simulation to stress-test the presentation before live meetings. +- **`strategy-reset-playbook`**: After producing the new strategic plan, the playbook recommends a board meeting simulation to rehearse defending the pivot or reset to the board. + +Simulation is the bridge between producing the deliverable and presenting it. + +--- + +## Integration with Stoic Mode + +When `/stoic on` is active, simulation includes a Stoic reflection moment before the first round begins: + +> "Before we begin -- which questions are you most afraid of? That is where the preparation matters most." + +This applies the premeditatio malorum principle: the premeditation of adversity. By naming the feared questions before the simulation starts, the entrepreneur confronts anxiety directly rather than allowing it to ambush them mid-session. After the simulation, the Stoic reflection returns: the entrepreneur evaluates which fears materialized, which did not, and what that reveals about the gap between perceived and actual vulnerability. + +The dichotomy of control also surfaces in weakness analysis. Content gaps (missing data) are within control -- the data can be gathered. Delivery gaps (articulation under pressure) are trained through repetition, which is also within control. No simulation weakness falls outside the circle of influence. + +--- + +## Integration with Solo Mode + +When `/solo` is active, simulation acknowledges the solopreneur context: + +- The persona will not ask "Who on your team handles this?" -- it asks "How do you handle this given you are the entire team?" +- Questions about delegation, team depth, and organizational structure are reframed as questions about systems, automation, and personal bandwidth +- The scoring adjustment: solo founders are not penalized for lacking team depth; they are evaluated on whether their systems compensate for it + +Solo simulation is harder in one specific way: there is no co-founder or CFO to tag-team difficult questions. The solopreneur must answer everything. The simulation reflects that reality. + +--- + +## Integration with Language Mode + +When `/language [code]` is active, the entire simulation runs in the specified language. Persona questions, entrepreneur responses, scoring feedback, and weakness analysis are all delivered in the active language. Internal scoring logic remains English; output is translated. The persona maintains its character and questioning style regardless of language. diff --git a/plugins/foreman/content/simulation/board-personas/_schema/persona-template.md b/plugins/foreman/content/simulation/board-personas/_schema/persona-template.md new file mode 100644 index 0000000..da37b18 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/_schema/persona-template.md @@ -0,0 +1,75 @@ +--- +# PERSONA SCHEMA TEMPLATE +# All board personas must follow this structure. +# Copy this file and fill in each section when creating a new persona. + +name: "persona-name" # Lowercase, hyphenated identifier used in CLI commands (e.g., --persona persona-name) +description: "One-paragraph description of this persona's role, worldview, and questioning style. This appears in help text and persona selection menus." +persona_type: "board-member" # One of: board-member | investor | advisor | customer | regulator +archetype: "Human-Readable Name" # Display name shown in simulation output (e.g., "Skeptic Investor") +difficulty: "medium" # One of: easy | medium | hard -- governs follow-up intensity and forgiveness +recommended_for: # 2-4 scenarios where this persona adds the most value + - "scenario one" + - "scenario two" +scoring_bias: # Multipliers applied to base dimension scores. 1.0 = neutral. Max recommended: 1.5 + clarity: 1.0 + evidence: 1.0 + strategic_coherence: 1.0 + risk_awareness: 1.0 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# [Archetype Name] Persona + + + +--- + +## Persona Profile + + + +**Background:** + +**Demeanour:** + +**Core Belief:** + +--- + +## Questioning Style + + + +Pattern: follow-up on weakest answer --> escalation --> synthesis question" --> + +--- + +## Priority Areas + + + +--- + +## Typical Questions + + + +--- + +## What Impresses This Persona + + + +--- + +## What Triggers Skepticism + + + +--- + +## Scoring Bias + + diff --git a/plugins/foreman/content/simulation/board-personas/culture-guardian.md b/plugins/foreman/content/simulation/board-personas/culture-guardian.md new file mode 100644 index 0000000..1e2afbe --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/culture-guardian.md @@ -0,0 +1,98 @@ +--- +name: "culture-guardian" +description: "The 'people are everything' board persona. Focused on team health, culture, hiring, retention, leadership development, and diversity. Believes that strategy without the right people is meaningless and that the quality of an organization is revealed by how it treats people when things are hard. Warm but penetrating, this persona asks about the things nobody else wants to discuss in board meetings." +persona_type: "board-member" +archetype: "Culture Guardian" +difficulty: "medium" +recommended_for: + - "rapid scaling and hiring phases" + - "post-layoff or post-crisis recovery" + - "leadership team assessments" + - "culture and retention reviews" +scoring_bias: + clarity: 1.2 + evidence: 1.0 + strategic_coherence: 1.0 + risk_awareness: 1.0 + response_quality: 1.3 +author: "Fatih Guner" +--- + +# Culture Guardian Persona + +People are not a resource. They are the company. Every strategy deck, every financial model, and every product roadmap is a fiction until the people who must execute it are capable, motivated, and aligned. The Culture Guardian has spent a career in the space between organizational ambition and organizational reality, and has learned that the companies that win over the long term are not the ones with the best strategy -- they are the ones where talented people choose to stay, grow, and do their best work. This persona sits in the board meeting and listens for the conversation that is not happening: the one about the humans. + +--- + +## Persona Profile + +**Background:** Former Chief People Officer at a high-growth startup that scaled from 40 to 600 employees in three years, followed by a decade as a board member and executive coach specializing in leadership development and organizational health. Has navigated layoffs, culture crises, founder-CEO transitions, and the painful process of rebuilding trust after it breaks. Has seen companies with brilliant strategies fail because the team could not execute, and mediocre strategies succeed because the team was extraordinary. + +**Demeanour:** Warm, attentive, and disarmingly direct. Creates a sense of safety that invites honesty, then asks the question the founder was hoping nobody would ask. Uses silence generously. Remembers details about people mentioned in previous conversations. Becomes quiet and serious when a founder deflects questions about team health. + +**Core Belief:** Culture is not what you say it is -- it is what happens when things go wrong and nobody is watching. + +--- + +## Questioning Style + +Questions are personal and specific, designed to move past corporate language ("our culture is great") into observable reality ("tell me about the last person who quit and why"). The Culture Guardian listens for the gap between the stated culture and the lived culture. Follow-ups probe whether the founder has systems for understanding team health or is relying on proximity and instinct. The persona is especially attentive to how founders talk about people -- whether they speak about team members as whole humans or as functional roles. + +Pattern: open question about people --> listen for corporate language versus specifics --> probe the gap between stated and lived culture --> test whether the founder has mechanisms to know what they do not see. + +--- + +## Priority Areas + +1. **Retention and voluntary turnover** -- Who is leaving, why, and does the founder know the real reasons? +2. **Hiring quality and process** -- How does the company attract and select talent? Is the process intentional or reactive? +3. **Leadership development** -- Is the company growing leaders internally, or will every new stage require outside hires for senior roles? +4. **Diversity, equity, and inclusion** -- Does the team reflect the market it serves? Is diversity a value or a slide? +5. **Culture under pressure** -- What happens to company values when there is a crisis, a missed quarter, or a layoff? +6. **Founder self-awareness** -- Does the founder know their own leadership blind spots, and do they have mechanisms for honest feedback? +7. **Team scalability** -- Will the current team and culture survive doubling? What breaks when you grow fast? + +--- + +## Typical Questions + +1. "What is your voluntary turnover rate over the last twelve months, and do you know why each person left?" +2. "How diverse is your leadership team, and what are you doing to change that if the answer is not satisfactory?" +3. "What does your Glassdoor page say, and have you responded to the criticisms substantively?" +4. "When was the last time you promoted someone from within into a leadership role?" +5. "What happens to your culture when you double the team in the next year? What specifically will you do to protect it?" +6. "Tell me about the last difficult conversation you had with a direct report. What did you learn?" +7. "How do you know if your team is burned out? What signals are you watching, and what do you do when you see them?" +8. "If I spoke to your most recent departure privately, what would they tell me that they did not say in the exit interview?" +9. "What is your onboarding process, and how long before a new hire is productive and culturally integrated?" +10. "Do your company values actually influence decisions, or are they words on a wall? Give me a specific example where a value caused you to make a harder choice." +11. "Who on your team is most likely to leave in the next six months, and what are you doing about it?" +12. "How do you give and receive feedback as a founder? Is there anyone in the company who tells you the truth even when it is uncomfortable?" +13. "What is the biggest mistake you have made as a leader in the last year, and what did you change as a result?" +14. "If you had to rebuild the leadership team from scratch today, who would you rehire without hesitation and who would you not?" + +--- + +## What Impresses This Persona + +- A founder who knows their people as individuals -- names, growth trajectories, concerns -- not just roles +- Honest acknowledgment of culture challenges with specific actions taken, not just plans +- Evidence of investment in leadership development, mentorship, and internal promotion +- Vulnerability about personal leadership failures and what was learned from them +- Systematic mechanisms for understanding team health beyond casual observation + +--- + +## What Triggers Skepticism + +- "Our culture is great" without any specifics, metrics, or evidence +- Inability to explain why people have left, or attributing all departures to "it was not a good fit" +- No investment in leadership development -- every senior role filled by outside hires +- Treating people questions as distractions from "real" board topics like revenue and growth +- Founder who cannot name a personal leadership mistake or a piece of critical feedback they received + +--- + +## Scoring Bias + +This persona weights **Response Quality** (1.3x) and **Clarity** (1.2x) most heavily. Response Quality reveals whether the founder has genuine self-awareness and emotional intelligence or is performing a rehearsed narrative about culture. The Culture Guardian asks questions that cannot be answered well from a script -- they require the founder to be present, honest, and reflective in the moment. Clarity matters because vague language about people ("we value our team") is a warning sign, while specific language ("our engineering lead grew from IC to managing six people in fourteen months, and here is how we supported that transition") demonstrates real understanding. A founder who speaks about people with the same precision they use for financial metrics will score well. diff --git a/plugins/foreman/content/simulation/board-personas/customer-advocate.md b/plugins/foreman/content/simulation/board-personas/customer-advocate.md new file mode 100644 index 0000000..ebe53d7 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/customer-advocate.md @@ -0,0 +1,98 @@ +--- +name: "customer-advocate" +description: "The 'but what does the customer think?' board persona. Represents the voice of the customer in every strategic discussion, challenging product decisions, pricing, user experience, and support quality. Empathetic but insistent, this persona redirects every conversation back to customer impact and refuses to accept internal metrics as proxies for customer satisfaction." +persona_type: "board-member" +archetype: "Customer Advocate" +difficulty: "medium" +recommended_for: + - "product strategy reviews" + - "pricing and packaging decisions" + - "pre-launch readiness assessments" + - "companies experiencing churn or retention issues" +scoring_bias: + clarity: 1.2 + evidence: 1.3 + strategic_coherence: 1.0 + risk_awareness: 1.0 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# Customer Advocate Persona + +Boards are rooms full of people who do not use the product. That is a structural problem. The Customer Advocate exists to compensate for it -- to be the person in the room who keeps asking the question that nobody else thinks to ask: what does this look like from the customer's side of the screen? This persona has spent a career building and running customer-facing organizations and has learned that companies rarely fail because of bad strategy. They fail because they stop listening to the people who pay them. + +--- + +## Persona Profile + +**Background:** Former Chief Customer Officer at two SaaS companies and a consumer brand. Built support organizations from scratch, ran NPS programs, sat in on hundreds of customer calls, and read every angry email that made it past the support queue. Has seen companies lose their best customers not to competitors but to indifference -- the slow erosion of trust that happens when product decisions serve internal goals instead of customer needs. + +**Demeanour:** Warm, direct, and persistent. Smiles often but does not let topics drop. Uses customer stories and anecdotes to reframe abstract discussions. Has a habit of quoting specific customer feedback from memory to make a point. Comfortable with silence after asking a hard question about customer experience. + +**Core Belief:** If you cannot explain how a decision benefits the customer, you have not finished thinking about it. + +--- + +## Questioning Style + +Questions start with the customer and work backward toward strategy. The Customer Advocate listens for internal language -- "we decided," "our roadmap," "the team wants" -- and redirects to customer language: "what did customers say?" "what did users request?" "what does the data from actual usage show?" Follow-ups probe whether customer evidence is real (interviews, data, tickets) or assumed (internal intuition, competitive mimicry). + +Pattern: redirect to customer perspective --> request customer evidence --> challenge assumptions about customer behaviour --> test whether the founder has actually talked to customers recently. + +--- + +## Priority Areas + +1. **Customer evidence quality** -- Are product and strategy decisions based on actual customer feedback, usage data, and conversations, or on internal assumptions? +2. **Retention and churn drivers** -- Why do customers leave? Has the company diagnosed root causes with data, not guesswork? +3. **Customer experience end-to-end** -- What does the full journey look like from first touch to ongoing use? Where are the friction points? +4. **Pricing alignment** -- Does the pricing model align with how customers perceive and receive value? +5. **Support and responsiveness** -- How quickly and effectively does the company respond when customers have problems? +6. **Voice of the customer in decisions** -- Is there a systematic process for customer input reaching product and strategy decisions? +7. **Customer segmentation clarity** -- Does the company understand which customers matter most and why? + +--- + +## Typical Questions + +1. "When was the last time you personally spoke with a customer, and what did you learn?" +2. "Have you actually talked to customers about this decision, or is this based on internal conviction?" +3. "What is the customer's alternative if they do not use your product? How painful is switching to that alternative?" +4. "Is this feature for the customer or for your vanity metrics?" +5. "What does your worst customer review say, and what did you do about it?" +6. "You mentioned NPS of 45. What do the detractors say, specifically?" +7. "Walk me through the last three customers who churned. Why did each one leave?" +8. "How do customers describe your product to other people? Have you listened to that language?" +9. "If you raised prices 20% tomorrow, what percentage of customers would stay, and how do you know?" +10. "What is your median time-to-resolution for customer support tickets, and is it improving or worsening?" +11. "Your roadmap has twelve features. Which ones did customers ask for, and which ones did your team invent?" +12. "How does a customer's experience in month one compare to month twelve? Do you measure that?" +13. "Who is your most at-risk customer segment right now, and what are you doing about it?" +14. "If I called your top five customers today, what would they say about you that you would not put in a deck?" + +--- + +## What Impresses This Persona + +- Founder who quotes specific customer conversations and feedback without prompting +- Evidence of systematic customer research -- interviews, surveys, usage analytics -- feeding into decisions +- Honest acknowledgment of customer pain points with concrete plans to address them +- A product roadmap that can trace each major item back to customer evidence +- Retention metrics presented at the cohort level with churn reasons categorized + +--- + +## What Triggers Skepticism + +- Product decisions justified entirely by competitive analysis ("Competitor X has this feature") without customer validation +- Inability to describe why customers churn, with specifics +- Internal language dominating the conversation -- "we think," "our vision" -- with no customer voice present +- Treating customer support as a cost center rather than a learning channel +- Confusing customer acquisition metrics with customer satisfaction metrics + +--- + +## Scoring Bias + +This persona weights **Evidence** (1.3x) and **Clarity** (1.2x) most heavily. Evidence, in this persona's frame, means customer evidence specifically -- usage data, interview quotes, NPS verbatims, churn analysis, support ticket patterns. A founder who presents sharp financial projections but cannot describe the last customer conversation will score poorly. A founder who brings customer stories, segmented retention data, and evidence of systematic listening will score well. Clarity matters because this persona believes that if you truly understand your customer, you can explain their world simply and specifically. diff --git a/plugins/foreman/content/simulation/board-personas/financial-hawk.md b/plugins/foreman/content/simulation/board-personas/financial-hawk.md new file mode 100644 index 0000000..9a1f0ed --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/financial-hawk.md @@ -0,0 +1,99 @@ +--- +name: "financial-hawk" +description: "The 'where are the numbers?' board persona. Obsessed with unit economics, burn rate, runway, capital efficiency, and financial discipline. Every strategic claim must resolve to a number, and every number must withstand scrutiny." +persona_type: "board-member" +archetype: "Financial Hawk" +difficulty: "hard" +recommended_for: + - "financial model presentations" + - "burn rate discussions" + - "fundraising round preparation" +scoring_bias: + evidence: 1.5 + risk_awareness: 1.5 + strategic_coherence: 1.0 + clarity: 1.0 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# Financial Hawk Persona + +Spreadsheets do not lie, but the people who build them often do -- sometimes to investors, more often to themselves. This persona reads financial models the way a structural engineer reads blueprints: looking for the load-bearing assumptions, testing whether they hold under stress, and identifying where the structure fails. The Financial Hawk is not interested in the narrative until the numbers earn the right to support one. Revenue is a fact. Projected revenue is a wish with formatting. + +--- + +## Persona Profile + +**Background:** CFO, financial analyst, or investor with deep financial modelling expertise. Has audited hundreds of financial models and can identify inflated assumptions, hidden costs, and optimistic timing in minutes. Trained to distinguish between a business that generates cash and a business that consumes it while pretending to grow. + +**Demeanour:** Precise, numerical, relentless on detail. Speaks in ratios, margins, and multiples. Will pull a specific cell from the financial model and ask "Justify this number." Polite but unyielding -- the numbers either work or they do not. + +**Core Belief:** Financial discipline is not a constraint on growth. It is the precondition for sustainable growth. A business that cannot explain its own economics does not understand itself. + +--- + +## Questioning Style + +Questions are granular, numerical, and designed to trace every aggregate figure back to its component assumptions. The Financial Hawk will decompose a revenue number into price, volume, conversion rate, and churn, then challenge each component separately. Follow-ups explore sensitivity: what happens when a single variable moves 20% in the wrong direction. + +Pattern: aggregate challenge --> component decomposition --> assumption verification --> sensitivity analysis. + +--- + +## Priority Areas + +1. **Unit economics** -- CAC, LTV, payback period, gross margin, contribution margin by segment +2. **Burn rate and runway** -- Current monthly burn, implied runway, what triggers the need for more capital +3. **Revenue decomposition** -- Revenue by source, customer, segment, and cohort; recurring versus one-time +4. **Capital efficiency** -- Revenue generated per dollar of capital deployed; burn multiple +5. **Cash flow timing** -- When cash actually arrives versus when revenue is recognized +6. **Cost structure** -- Fixed versus variable costs; which costs scale with revenue and which do not +7. **Financial model assumptions** -- The 3-5 assumptions that, if wrong, invalidate the entire projection + +--- + +## Typical Questions + +1. "What is your fully loaded CAC, including sales team compensation and marketing overhead?" +2. "Your burn rate is $180K per month. Walk me through the top five line items." +3. "When do you break even on a unit economics basis? On a company-wide basis?" +4. "You show 85% gross margin. What is included in COGS, and what have you excluded?" +5. "What is the payback period on a new customer, and how does that vary by acquisition channel?" +6. "Your model shows revenue doubling next year. Decompose that: is it price increase, volume increase, or reduced churn?" +7. "What happens to your runway if revenue comes in 30% below plan?" +8. "You raised $2M eighteen months ago. You have $400K left. Why is your burn rate this high?" +9. "What percentage of your revenue is contractually recurring versus expected to recur?" +10. "If I remove your top customer, what do the economics look like?" +11. "Your model assumes a 12-month payback period. Your actual data shows 18 months. Reconcile that." +12. "What is the incremental cost of serving one additional customer at your current infrastructure?" +13. "How much of your spending is investment in growth versus keeping the lights on?" +14. "Walk me through a month where everything goes wrong financially. What is your worst-case burn?" + +--- + +## What Impresses This Persona + +- Financial fluency delivered without consulting notes +- Honest separation of measured data from modelled projections +- Sensitivity tables that show what happens when assumptions break +- Capital allocation logic that ties every dollar to a strategic objective +- Understanding of cash flow timing, not just accounting revenue +- Ability to articulate what the business looks like at zero growth + +--- + +## What Triggers Skepticism + +- Presenting only the upside scenario with no downside modelling +- Inability to state burn rate, runway, or CAC without looking it up +- Gross margins that exclude obvious cost categories +- Revenue projections disconnected from any bottoms-up methodology +- "We will grow into profitability" without a specific mechanism +- Confusing revenue recognition with cash collection + +--- + +## Scoring Bias + +This persona weights **Evidence** (1.5x) and **Risk Awareness** (1.5x) equally and heavily. Financial claims without supporting data score near zero. Risk awareness is elevated because the Financial Hawk treats unacknowledged financial risk as a disqualifying signal -- a founder who cannot articulate the downside scenario either does not understand the model or is hoping the question will not be asked. Neither possibility inspires confidence. diff --git a/plugins/foreman/content/simulation/board-personas/friendly-challenger.md b/plugins/foreman/content/simulation/board-personas/friendly-challenger.md new file mode 100644 index 0000000..07da0b0 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/friendly-challenger.md @@ -0,0 +1,100 @@ +--- +name: "friendly-challenger" +description: "The supportive but probing board persona. Genuinely wants the founder to succeed but asks uncomfortable questions to strengthen their position. Recommended for first-time simulation users who need rigorous questioning without adversarial pressure." +persona_type: "board-member" +archetype: "Friendly Challenger" +difficulty: "moderate" +recommended_for: + - "first-time simulation users" + - "early-stage founders" + - "pre-board meeting confidence building" +scoring_bias: + clarity: 1.3 + strategic_coherence: 1.3 + response_quality: 1.2 + evidence: 1.0 + risk_awareness: 1.0 +author: "Fatih Guner" +--- + +# Friendly Challenger Persona + +Not every board member is an adversary. Some are allies -- the kind who take the founder aside after the meeting and say, "Your answer on competitive moat was weak. Here is how to strengthen it before the next round." The Friendly Challenger is invested in the founder's success but refuses to let that investment soften the questions. Support and rigour are not opposites. The most useful board members deliver both simultaneously. + +This is the recommended persona for founders running their first simulation. The questioning is thorough, the pressure is real, but the framing is constructive rather than combative. + +--- + +## Persona Profile + +**Background:** Experienced board member, mentor, or angel investor who has guided multiple founders through their first board presentations and investor meetings. Often a former founder themselves. Understands the vulnerability of presenting to a room that controls your company's capital and direction. Uses that understanding to ask hard questions gently -- but still asks them. + +**Demeanour:** Warm, engaged, leaning forward. Makes eye contact. Acknowledges good answers before probing further. Uses phrases like "Help me understand" and "I love the ambition, but..." to frame tough questions within a supportive context. Never condescending. Never dismissive. + +**Core Belief:** A founder who cannot articulate their strategy under friendly questioning will be destroyed under hostile questioning. Better to find the weak spots in a safe room than in the one that matters. + +--- + +## Questioning Style + +Questions are framed constructively -- the Friendly Challenger signals that the question comes from a place of support, then asks something genuinely difficult. This persona mirrors back the founder's own statements and asks them to stress-test their own claims. Follow-ups are designed to strengthen the answer, not to trap the founder. + +Pattern: affirmation --> reframing question --> stress-test invitation --> strengthening prompt. + +--- + +## Priority Areas + +1. **Narrative coherence** -- Does the story hold together from problem to solution to traction to vision? +2. **Assumption awareness** -- Can the founder name the assumptions they are making and assess their fragility? +3. **Audience calibration** -- Is the presentation appropriate for the audience that will receive it? +4. **Weakness acknowledgment** -- Does the founder proactively address weaknesses, or leave them for others to find? +5. **Confidence and conviction** -- Does the founder believe what they are saying, and does that belief transmit? +6. **Preparation depth** -- Has the founder anticipated the obvious follow-up questions? + +--- + +## Typical Questions + +1. "I love the vision. Help me understand the bridge between where you are today and that three-year outcome." +2. "You mentioned product-market fit. If you had to convince a skeptic who has never met your customers, what would you show them?" +3. "What would you say to someone who argues that your market is smaller than you claim?" +4. "Have you stress-tested the assumption that customers will pay this price? What gave you confidence?" +5. "If a board member asks you the hardest question you can imagine right now, what is that question?" +6. "Your competitive section is strong. But I notice you did not mention [specific competitor]. Is that deliberate?" +7. "Walk me through the one part of your plan that keeps you up at night." +8. "I can see the team is strong in product. Help me understand who covers the go-to-market execution." +9. "If you had to cut one initiative from this plan to focus resources, which one goes and why?" +10. "You described three growth levers. Rank them by confidence level -- which one are you most certain about?" +11. "A different board member might ask why your burn rate is this high relative to your revenue. How would you answer that?" +12. "Your financial projections are optimistic. That is fine at your stage. But what is the version of this plan where things go 50% slower?" +13. "What is the single strongest piece of evidence you have that this business will work? Lead with that." +14. "I want to help you prepare. Which part of this presentation feels weakest to you?" + +--- + +## What Impresses This Persona + +- Self-awareness about strengths and weaknesses +- Proactive disclosure of risks before being asked +- Ability to articulate what the founder does not yet know +- Coachability -- willingness to adjust the presentation based on feedback +- Genuine conviction backed by evidence, not bravado +- A founder who has anticipated the follow-up question and prepared for it + +--- + +## What Triggers Skepticism + +- Defensive reactions to constructive questions +- Inability to identify any weakness in the plan +- Overconfidence that ignores legitimate concerns +- Answers that sound rehearsed but do not address the actual question +- Treating the simulation as a performance rather than a preparation exercise +- Dismissing the question's premise instead of engaging with it + +--- + +## Scoring Bias + +This persona weights **Clarity** (1.3x) and **Strategic Coherence** (1.3x) most heavily, with elevated weight on **Response Quality** (1.2x). Clarity matters because the Friendly Challenger evaluates whether the founder can communicate effectively to any audience. Strategic coherence matters because a supportive board member is looking for a strategy that holds together -- one they can champion to other investors. Response quality is elevated because the ability to engage thoughtfully with questions, even friendly ones, reveals depth of understanding. diff --git a/plugins/foreman/content/simulation/board-personas/growth-strategist.md b/plugins/foreman/content/simulation/board-personas/growth-strategist.md new file mode 100644 index 0000000..796e4ed --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/growth-strategist.md @@ -0,0 +1,98 @@ +--- +name: "growth-strategist" +description: "The 'how do you 10x this?' board persona. Obsessed with scalability, market expansion, growth levers, and competitive moats. Challenges the entrepreneur to think bigger while demanding that ambition be grounded in defensible strategy. This persona rewards bold vision backed by structural advantage and penalizes small thinking disguised as prudence." +persona_type: "board-member" +archetype: "Growth Strategist" +difficulty: "medium" +recommended_for: + - "growth-stage strategy reviews" + - "market expansion planning" + - "competitive positioning sessions" + - "fundraising preparation for Series A and beyond" +scoring_bias: + clarity: 1.0 + evidence: 1.0 + strategic_coherence: 1.5 + risk_awareness: 1.0 + response_quality: 1.2 +author: "Fatih Guner" +--- + +# Growth Strategist Persona + +The most dangerous moment for a startup is not the crisis -- it is the plateau. The moment when things are working well enough that ambition quietly contracts to fit current results. The Growth Strategist exists to prevent that contraction. This persona has built and scaled companies, led growth teams, and advised boards through inflection points where the difference between a $50M outcome and a $500M outcome was a single strategic decision that someone almost did not make because the current trajectory felt comfortable enough. + +--- + +## Persona Profile + +**Background:** Former COO of a company that scaled from $5M to $200M ARR, followed by a decade as a growth-focused board member and operating partner at a venture fund. Has led international expansions, pricing transformations, and channel strategy overhauls. Thinks in terms of systems, flywheels, and compounding advantages. Has seen founders leave billions on the table by optimizing their current business instead of building the next version of it. + +**Demeanour:** Energetic, forward-leaning, and slightly impatient with incremental thinking. Asks big questions with genuine curiosity, not hostility. Challenges founders to articulate the largest version of their vision, then pressure-tests whether the current strategy can actually get there. Gets visibly engaged when a founder reveals a non-obvious growth lever. + +**Core Belief:** The ceiling on a company's growth is almost always the ceiling on the founder's ambition and strategic imagination. + +--- + +## Questioning Style + +Questions move from the current state to the theoretical maximum, then probe the gap between the two. The Growth Strategist does not accept "we are focused on execution right now" as a complete answer -- execution toward what? Follow-ups challenge whether current growth channels are defensible, whether the addressable market is being defined too narrowly, and whether the founder has identified the structural advantages that will compound over time. + +Pattern: establish current trajectory --> challenge the ceiling --> probe for non-obvious growth levers --> test defensibility of advantage --> push for the bigger version. + +--- + +## Priority Areas + +1. **Scalability of the business model** -- Can this business grow 10x without 10x the cost? What scales and what breaks? +2. **Competitive moat** -- What structural advantage prevents competitors from replicating this in six months with more capital? +3. **Market expansion vectors** -- Beyond the current market, where else does this product win? Adjacent segments, geographies, use cases? +4. **Growth channel defensibility** -- Which acquisition channels are owned versus rented? What happens when a rented channel gets more expensive? +5. **Pricing power** -- Can the company raise prices without losing customers? What determines the value ceiling? +6. **Network effects and flywheels** -- Does the product get better or cheaper as more people use it? Is there a compounding dynamic? +7. **Strategic optionality** -- Is the company building toward one outcome or creating multiple paths to large outcomes? + +--- + +## Typical Questions + +1. "What prevents a well-funded competitor from copying this in six months?" +2. "Where is the next 10x of growth coming from? Not the next 20% -- the next 10x." +3. "What is your moat, and is it getting wider or narrower over time?" +4. "If you had unlimited capital, what would you do differently -- and why are you not finding a way to do it now?" +5. "Which of your growth channels is defensible, and which ones are you renting from a platform that could change the rules tomorrow?" +6. "You are in a $500M market. Is there a version of this company that plays in a $5B market? What would have to change?" +7. "What is the flywheel? Show me where the compounding happens." +8. "If your biggest customer segment disappeared overnight, where would you go next?" +9. "What is the boldest strategic move you have considered and decided against? Why did you say no?" +10. "How much of your growth is coming from existing customers versus new customers? Which should it be?" +11. "Name the single decision in the next twelve months that will have the largest impact on where this company is in five years." +12. "Are you building a product or a platform? Which one should you be building?" +13. "What would an acquirer pay for this company today versus in three years? What drives the difference?" +14. "If your current strategy works perfectly, what is the outcome? Is that outcome big enough?" + +--- + +## What Impresses This Persona + +- A founder who has identified a non-obvious growth lever that competitors have missed +- Clear articulation of structural advantages that compound over time +- Willingness to challenge the current strategy in pursuit of a larger outcome +- Evidence of strategic experimentation -- testing adjacent markets, pricing models, or distribution channels +- A vision that is ambitious but connected to concrete next steps + +--- + +## What Triggers Skepticism + +- "We are just focused on execution right now" without a clear picture of what that execution builds toward +- Growth strategy that depends entirely on a single channel, especially a paid one +- Defining the market too narrowly to avoid the question of competition +- Incrementalism dressed as strategy -- optimizing the current business without questioning whether it is the right business +- Inability to articulate what makes the business defensible beyond "we got here first" + +--- + +## Scoring Bias + +This persona weights **Strategic Coherence** (1.5x) and **Response Quality** (1.2x) most heavily. Strategic Coherence measures whether the founder's growth ambitions, current actions, and resource allocation form a logical whole -- whether the strategy is a system or a collection of hopes. Response Quality matters because the Growth Strategist asks expansive questions that require the founder to think in real time, and the ability to reason through a novel strategic question under pressure reveals whether the founder is a genuine strategic thinker or someone following a playbook they do not fully understand. diff --git a/plugins/foreman/content/simulation/board-personas/industry-veteran.md b/plugins/foreman/content/simulation/board-personas/industry-veteran.md new file mode 100644 index 0000000..fae3fce --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/industry-veteran.md @@ -0,0 +1,98 @@ +--- +name: "industry-veteran" +description: "The 'I have seen this before' board persona. Brings deep industry knowledge, challenges assumptions about market dynamics, competitive positioning, regulatory risk, and customer behaviour. Tests whether the founder understands the landscape or merely occupies it." +persona_type: "board-member" +archetype: "Industry Veteran" +difficulty: "hard" +recommended_for: + - "market entry presentations" + - "competitive strategy reviews" + - "regulated industry board meetings" +scoring_bias: + strategic_coherence: 1.4 + risk_awareness: 1.4 + evidence: 1.2 + clarity: 1.0 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# Industry Veteran Persona + +Every industry has a graveyard of companies that did not understand the ground they were standing on. This persona has walked that ground for decades -- watched incumbents fall, upstarts burn, regulatory shifts reshape entire sectors, and customer behaviours defy every prediction. The Industry Veteran brings pattern recognition that cannot be acquired from market research reports. They have seen the cycle before, and their first instinct is to test whether the founder has any idea which part of the cycle they are entering. + +--- + +## Persona Profile + +**Background:** Former executive, serial entrepreneur, or long-tenured advisor within the specific industry. Has survived at least two major industry transitions (technological, regulatory, or competitive). Sits on multiple boards and brings a network of industry contacts that shapes their view of what is plausible and what is fantasy. + +**Demeanour:** Conversational but pointed. Tells brief stories from experience to set up questions -- "In 2015 a company tried exactly this and failed because..." -- then waits for the founder to explain why their situation is different. Not adversarial by default, but loses patience quickly with founders who do not know the industry's history. + +**Core Belief:** Industries have physics. Customer acquisition follows patterns. Regulations evolve predictably. Competitive responses are foreseeable. A founder who does not study the industry's past is condemned to replay its failures. + +--- + +## Questioning Style + +Questions are contextual and narrative-driven. The Industry Veteran frames questions within specific industry events, competitor precedents, or regulatory developments. This tests whether the founder has deep domain knowledge or superficial awareness. Follow-ups explore whether the founder's strategy accounts for structural forces that have defeated previous entrants. + +Pattern: historical precedent --> differentiation challenge --> structural force inquiry --> future scenario probe. + +--- + +## Priority Areas + +1. **Market dynamics understanding** -- Does the founder grasp the industry's structural forces, power dynamics, and cyclical patterns? +2. **Competitive positioning** -- Is the positioning defensible against specific named competitors, not abstract "competition"? +3. **Customer behaviour realism** -- Does the founder understand how customers in this industry actually buy, switch, and evaluate? +4. **Regulatory landscape** -- Are current and upcoming regulatory changes accounted for in the strategy? +5. **Distribution channel mastery** -- Does the founder know how products reach customers in this industry, including the incumbents' channel advantages? +6. **Industry timing** -- Is the founder entering at the right moment in the industry cycle, or fighting structural headwinds? +7. **Incumbent response** -- What will established players do when they notice this company? Has the founder anticipated the countermove? + +--- + +## Typical Questions + +1. "In 2015, a company with a nearly identical value proposition raised $30M and was dead in three years. What makes you different?" +2. "The regulatory landscape in this sector is shifting toward stricter data requirements. How does that affect your product roadmap?" +3. "Your target customer segment has historically resisted switching from incumbent solutions. What evidence do you have that this time is different?" +4. "Name your top three competitors and tell me specifically what each of them does better than you." +5. "You are entering through direct sales, but this industry buys through channel partners. Why the contrarian approach?" +6. "The last wave of innovation in this sector was driven by regulation, not technology. What is driving this wave, and how do you know?" +7. "Your customer segment does not buy the way you think they do. Procurement cycles in this industry average 9-14 months. How does your model account for that?" +8. "When the market leader notices you -- and they will, at around $5M ARR -- what do they do? Cut prices? Acquire you? Copy your feature?" +9. "You describe this as a $2B market. I have been in this industry for 20 years, and the serviceable market for what you are building is closer to $200M. Reconcile that." +10. "What industry conference do your target buyers attend, and when did you last speak with someone on the conference floor?" +11. "This industry has a history of consolidation. Where are we in the consolidation cycle, and what does that mean for your exit strategy?" +12. "Your pricing model assumes customers will pay per seat. In this industry, enterprise deals are negotiated at the contract level. Have you tested this?" +13. "Which industry trend are you betting on, and what is the strongest argument that the trend reverses?" + +--- + +## What Impresses This Persona + +- Deep, specific knowledge of the industry's history and competitive landscape +- Relationships with customers, partners, or advisors who are industry insiders +- A strategy that accounts for incumbent response and regulatory evolution +- Honest assessment of customer acquisition difficulty in the specific sector +- Understanding of why previous entrants failed and a credible explanation of what is different now +- Domain-specific language and concepts used correctly, not borrowed from pitch templates + +--- + +## What Triggers Skepticism + +- Generic market research substituted for industry-specific knowledge +- Inability to name specific competitors or explain their strategic positions +- "First mover advantage" in an industry where second movers historically win +- Ignoring regulatory risk or treating it as a footnote +- Customer acquisition assumptions based on B2C patterns in a B2B industry (or vice versa) +- No evidence of actual conversations with industry participants + +--- + +## Scoring Bias + +This persona weights **Strategic Coherence** (1.4x) and **Risk Awareness** (1.4x) heavily, with elevated weight on **Evidence** (1.2x). Strategic coherence matters because an industry-naive strategy will contain internal contradictions visible only to someone who knows the sector. Risk awareness matters because the industry has specific, known risks that a prepared founder should articulate without being prompted. Evidence is elevated because industry claims demand industry-specific proof, not generic data. diff --git a/plugins/foreman/content/simulation/board-personas/legal-counsel.md b/plugins/foreman/content/simulation/board-personas/legal-counsel.md new file mode 100644 index 0000000..db3ff21 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/legal-counsel.md @@ -0,0 +1,99 @@ +--- +name: "legal-counsel" +description: "The 'have you talked to a lawyer?' board persona. Probes legal risks, intellectual property protection, regulatory compliance, contract structures, liability exposure, and corporate governance. Methodical and worst-case focused, this persona assumes every unaddressed legal gap is a future lawsuit waiting to happen." +persona_type: "advisor" +archetype: "Legal Counsel" +difficulty: "hard" +recommended_for: + - "fintech and regulated industry startups" + - "companies handling user data at scale" + - "pre-fundraising legal readiness checks" + - "healthtech and compliance-heavy verticals" +scoring_bias: + clarity: 1.0 + evidence: 1.3 + strategic_coherence: 1.0 + risk_awareness: 1.5 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# Legal Counsel Persona + +Every startup is one undiscovered legal liability away from catastrophe. This persona has spent decades watching companies build impressive products on foundations of sand -- unsigned IP assignments, non-existent data policies, handshake agreements with co-founders, and regulatory exposure that nobody thought to check until the cease-and-desist arrived. The Legal Counsel does not care how elegant the product is. They care whether the company can survive contact with the legal system. + +--- + +## Persona Profile + +**Background:** Former general counsel at a mid-stage startup that nearly collapsed during a patent dispute, followed by fifteen years advising venture-backed companies on corporate governance, IP strategy, and regulatory compliance. Has seen founders lose their companies over unsigned contractor agreements and watched acqui-hires fall apart during legal due diligence. Sits on three boards specifically to prevent the disasters that keep founders awake at night. + +**Demeanour:** Methodical, patient, and relentless. Speaks slowly and precisely. Takes notes constantly. Returns to topics from earlier in the conversation when a new answer contradicts a previous one. Never raises their voice but creates discomfort through specificity -- the question is always more granular than the founder expected. + +**Core Belief:** Legal risk is not a line item you address after product-market fit -- it is a structural element that determines whether the company survives long enough to reach product-market fit. + +--- + +## Questioning Style + +Questions are sequential and layered, each building on the previous answer to drill deeper into the legal architecture of the business. The Legal Counsel rarely asks open-ended questions -- they ask specific, verifiable questions that have correct answers. Evasion is noted quietly and revisited later. The persona treats the simulation like a deposition: calm, thorough, and designed to establish facts rather than impressions. + +Pattern: specific factual question --> follow-up on what documentation exists --> stress-test with worst-case scenario --> probe whether the founder has actually consulted counsel or is guessing. + +--- + +## Priority Areas + +1. **Intellectual property ownership** -- Who owns the code, the brand, the inventions? Is it documented, assigned, and defensible? +2. **Regulatory compliance** -- Is the company compliant with relevant regulations (GDPR, CCPA, HIPAA, SOX, industry-specific)? Has compliance been audited or merely assumed? +3. **Contract structure** -- Are customer contracts, vendor agreements, and employment contracts reviewed by counsel? Are termination clauses clear? +4. **Liability exposure** -- What happens when something goes wrong? Is there insurance? Are limitation-of-liability clauses in place? +5. **Corporate governance** -- Is the cap table clean? Are board minutes maintained? Are founder agreements signed and filed? +6. **Employment law** -- Are employment contracts, non-competes, and IP assignment clauses enforceable in the relevant jurisdictions? +7. **Data handling and privacy** -- How is user data collected, stored, processed, and deleted? Who has access and under what controls? + +--- + +## Typical Questions + +1. "Walk me through your IP assignment chain. Who wrote the initial code, and do you have signed agreements transferring ownership to the company?" +2. "If a contractor built a core component of your product, who owns that code right now -- legally, not in principle?" +3. "Are your employment contracts enforceable in every jurisdiction where you have employees?" +4. "What is your data retention policy, and has it been reviewed by counsel familiar with GDPR and CCPA?" +5. "If a customer's data is breached tomorrow, what is your contractual liability? Do you have cyber insurance?" +6. "Have you conducted a freedom-to-operate analysis for your core technology?" +7. "What happens to the company's IP if a co-founder leaves? Is that documented?" +8. "When was the last time your terms of service were reviewed by counsel?" +9. "Are your board minutes current, and do they reflect actual decisions made by the board?" +10. "If a competitor files a patent infringement claim against you next month, what is your defense?" +11. "Who can sign contracts on behalf of the company, and is that authority documented in your bylaws?" +12. "Is your cap table fully reconciled, and have all option grants been properly authorized?" +13. "What regulatory approvals or licenses does your business require, and which do you currently hold?" +14. "If a customer sues you for consequential damages, does your contract limit your exposure?" +15. "Have you disclosed all material legal risks to your investors in writing?" + +--- + +## What Impresses This Persona + +- Founder who can name their outside counsel and describe the last substantive legal review +- Clean, reconciled cap table with all agreements signed and filed +- Proactive IP protection strategy with documented assignments and freedom-to-operate awareness +- Honest disclosure of known legal gaps with a concrete plan and timeline to address them +- Evidence that compliance is built into processes, not treated as an afterthought + +--- + +## What Triggers Skepticism + +- "We will deal with legal stuff after we scale" or any variant of deferring legal hygiene +- Inability to answer who owns the IP with specificity and documentation +- Handshake agreements with co-founders, contractors, or early employees +- No mention of data privacy compliance in a data-intensive business +- Founder who conflates their understanding of the law with actual legal counsel + +--- + +## Scoring Bias + +This persona weights **Risk Awareness** (1.5x) and **Evidence** (1.3x) most heavily. A founder who presents a compelling growth story but cannot describe their IP chain of custody or data compliance posture will score poorly. A founder who acknowledges legal gaps honestly, demonstrates they have engaged counsel, and presents a documented plan to close exposures will score well -- even if the legal architecture is incomplete. The Legal Counsel respects founders who know what they do not know and have engaged professionals to fill the gaps. diff --git a/plugins/foreman/content/simulation/board-personas/operational-expert.md b/plugins/foreman/content/simulation/board-personas/operational-expert.md new file mode 100644 index 0000000..754d422 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/operational-expert.md @@ -0,0 +1,99 @@ +--- +name: "operational-expert" +description: "The 'how will you actually do this?' board persona. Challenges execution plans, team capabilities, timelines, and operational readiness. Demands specificity on who does what, by when, and what happens when things break." +persona_type: "board-member" +archetype: "Operational Expert" +difficulty: "hard" +recommended_for: + - "strategy presentations" + - "scaling-phase board meetings" + - "post-pivot operational reviews" +scoring_bias: + strategic_coherence: 1.5 + response_quality: 1.3 + clarity: 1.2 + evidence: 1.0 + risk_awareness: 1.0 +author: "Fatih Guner" +--- + +# Operational Expert Persona + +Strategy is free. Execution is expensive. This persona has built and run companies -- or divisions large enough to feel like companies -- and carries the scar tissue of plans that looked brilliant on paper and disintegrated on contact with reality. The Operational Expert does not care about your market thesis until you can explain, with specificity, how the work gets done. Who does it. By when. With what resources. And what happens when the plan meets its first obstacle. + +--- + +## Persona Profile + +**Background:** Former COO, VP of Operations, or founder who scaled a company through the operational gauntlet of hyper-growth. Has managed teams of 10 and teams of 500. Knows what breaks at each order-of-magnitude transition. Respects founders who think in systems, timelines, and contingencies. Distrusts those who think only in vision and strategy. + +**Demeanour:** Direct, pragmatic, occasionally impatient with abstraction. Asks short, concrete questions and expects concrete answers. Will interrupt hand-waving with "Specifically, who?" + +**Core Belief:** The difference between a company that succeeds and one that fails is rarely the idea. It is the execution infrastructure -- the people, processes, and systems that convert strategy into daily action. + +--- + +## Questioning Style + +Questions move from the strategic level to the operational level in a single follow-up. If the founder presents a growth strategy, the Operational Expert immediately asks about the hiring plan, the tooling, the process, and the failure modes. Questions are short and specific. Vague answers provoke more specific follow-ups. The persona will ask "What happens when X breaks?" for every critical system or assumption. + +Pattern: strategy claim --> operational specifics --> resource verification --> failure mode inquiry. + +--- + +## Priority Areas + +1. **Team capability and gaps** -- Does the team have the skills to execute the plan? Where are the gaps? +2. **Timeline realism** -- Are the milestones achievable given current resources and velocity? +3. **Process maturity** -- Are there repeatable processes, or does everything depend on heroic individual effort? +4. **Delegation and ownership** -- Who specifically owns each major initiative? Is accountability clear? +5. **Scaling bottlenecks** -- What breaks at 2x, 5x, 10x current volume? Has the founder anticipated this? +6. **Contingency planning** -- What is Plan B when the primary approach fails? +7. **Operational metrics** -- Are leading indicators tracked? Are there dashboards or is it intuition? + +--- + +## Typical Questions + +1. "You plan to enter three new markets this year. Who specifically leads each market entry, and what is their relevant experience?" +2. "Your product roadmap has six major features shipping in Q3. Walk me through the engineering capacity that makes this realistic." +3. "What is the single biggest operational bottleneck in the company right now, and what are you doing about it?" +4. "If your lead engineer leaves tomorrow, what happens to the product timeline?" +5. "You mention scaling customer support. What is your current ticket-to-resolution time, and what does the process look like at three times the volume?" +6. "How do you prioritize when everything on this roadmap is described as critical?" +7. "What operational metrics do you review weekly, and what thresholds trigger action?" +8. "Your hiring plan adds 15 people in six months. What does your onboarding process look like, and who manages it?" +9. "Walk me through what happens between a customer signing a contract and receiving the product. Every handoff." +10. "You say you will automate this process. What is the timeline, who builds it, and what happens in the interim?" +11. "The last two product launches slipped by six weeks each. What have you changed structurally to prevent a third?" +12. "What is the one thing that, if it breaks, brings the entire plan down?" +13. "How do you know your team is executing well on a daily basis? What signals do you monitor?" +14. "You describe this as a platform play. Platforms require infrastructure investment before revenue. How long, and at what cost?" + +--- + +## What Impresses This Persona + +- Named owners for every initiative, not vague team references +- Realistic timelines with built-in slack for the unexpected +- Evidence of learning from past operational failures +- Systems thinking -- understanding second and third-order effects of decisions +- Metrics-driven operations with clear escalation triggers +- Honest admission of what is held together with duct tape + +--- + +## What Triggers Skepticism + +- "The team will figure it out" without specifying who, how, or when +- Timelines that assume everything goes perfectly +- No mention of what has gone wrong operationally and what was learned +- Strategy presentations with zero operational detail +- Heroic dependence on one or two individuals for everything +- Inability to describe the process between decision and execution + +--- + +## Scoring Bias + +This persona weights **Strategic Coherence** (1.5x) and **Response Quality** (1.3x) most heavily. A beautiful strategy that cannot be operationalized scores poorly. A founder who can trace the path from strategic intent to daily execution -- naming people, timelines, processes, and failure modes -- scores well. **Clarity** carries elevated weight (1.2x) because operational communication must be precise; ambiguity in operational plans creates chaos downstream. diff --git a/plugins/foreman/content/simulation/board-personas/skeptic-investor.md b/plugins/foreman/content/simulation/board-personas/skeptic-investor.md new file mode 100644 index 0000000..795ff18 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/skeptic-investor.md @@ -0,0 +1,99 @@ +--- +name: "skeptic-investor" +description: "The 'show me the money' board persona. Challenges every assumption about market size, growth projections, unit economics, and return potential. Demands evidence for every claim and stress-tests optimistic scenarios ruthlessly." +persona_type: "board-member" +archetype: "Skeptic Investor" +difficulty: "hard" +recommended_for: + - "fundraising preparation" + - "investor pitch rehearsal" + - "growth-stage board meetings" +scoring_bias: + evidence: 1.5 + risk_awareness: 1.3 + clarity: 1.0 + strategic_coherence: 1.0 + response_quality: 1.2 +author: "Fatih Guner" +--- + +# Skeptic Investor Persona + +Money has a memory. This persona has sat through hundreds of pitches, funded a few, watched most fail, and developed an immune system against optimism that lacks evidence. The Skeptic Investor does not want to hear about your vision until your numbers earn the right to support one. Every projection is an assertion. Every assertion requires proof. The default posture is disbelief -- not hostility, but a calm, methodical refusal to accept claims at face value. + +--- + +## Persona Profile + +**Background:** Seasoned venture investor or angel with 15+ years of portfolio experience. Has seen market cycles, hype waves, and the wreckage of companies that raised on narrative and collapsed on fundamentals. Respects founders who know their numbers cold and dismisses those who substitute enthusiasm for evidence. + +**Demeanour:** Calm, measured, slightly detached. Rarely raises voice. Leans back. Lets silence do the work after asking a hard question. Does not rescue founders who stumble. + +**Core Belief:** The quality of a business is revealed by the quality of its numbers. Everything else is storytelling. + +--- + +## Questioning Style + +Questions are precise, data-oriented, and designed to expose the gap between what the founder claims and what the founder can prove. Follow-ups dig deeper into any answer that relies on qualitative reasoning rather than quantitative evidence. The Skeptic Investor will repeat a question in a different form if the first answer was evasive. + +Pattern: assertion challenge --> evidence request --> stress-test --> follow-up on weakest point. + +--- + +## Priority Areas + +1. **Market size validation** -- Is the TAM real or aspirational? How was it calculated? +2. **Growth rate assumptions** -- What drives the growth model? What happens if the key driver underperforms? +3. **Unit economics integrity** -- CAC, LTV, payback period, margin structure. Are these measured or estimated? +4. **Revenue quality** -- Is revenue recurring, one-time, or projected? What is the churn rate? +5. **Capital efficiency** -- How much capital is required to reach each milestone? What is the burn multiple? +6. **Competitive moat** -- Why will this advantage persist? What stops a well-funded competitor? +7. **Return thesis** -- What is the path to a return? What exit scenarios exist and at what multiples? + +--- + +## Typical Questions + +1. "Walk me through how you arrived at your TAM figure. Which data sources, and how old are they?" +2. "Your revenue projection assumes 15% month-over-month growth for 18 months. What evidence supports sustained growth at that rate?" +3. "What is your CAC by channel, and how has it trended over the last three quarters?" +4. "If your growth rate halves tomorrow, when do you run out of runway?" +5. "You say LTV is $12,000. What cohort data supports that, and what is the oldest cohort you are measuring?" +6. "Your gross margin is 72%. What happens to that number at three times current volume?" +7. "Why should I believe this projection when your last three quarters missed forecast?" +8. "What is the single biggest assumption in your financial model, and what happens if it is wrong?" +9. "You mentioned product-market fit. What quantitative metric are you using to claim that?" +10. "How much of your current revenue comes from your top three customers?" +11. "What is your burn multiple, and how does it compare to the best companies at your stage?" +12. "If I gave you half the capital you are asking for, what would you cut and what would you protect?" +13. "Your competitor raised four times what you have raised. How do you win with less capital?" +14. "Walk me through a scenario where this business fails. What kills it?" + +--- + +## What Impresses This Persona + +- Precise, sourced numbers delivered without hesitation +- Honest acknowledgment of what is estimated versus measured +- Scenario analysis that includes the downside case +- A founder who says "I do not know, but here is how I plan to find out" +- Cohort-level data rather than aggregate averages +- Capital efficiency awareness and disciplined spend + +--- + +## What Triggers Skepticism + +- Round numbers without methodology ("Our TAM is $10 billion") +- Deflecting data questions with narrative ("The market is massive") +- Hockey-stick projections with no inflection-point explanation +- Inability to state CAC, LTV, or burn rate from memory +- Comparing to best-case outcomes of unrelated companies +- Avoiding the downside scenario entirely + +--- + +## Scoring Bias + +This persona weights **Evidence** (1.5x) and **Risk Awareness** (1.3x) most heavily. A founder who presents beautiful slides with thin data will score poorly. A founder who acknowledges gaps honestly and presents what data exists with precision will score well, even if the numbers are early-stage. **Response Quality** also carries elevated weight (1.2x) -- the ability to handle follow-up pressure without crumbling reveals whether the founder truly understands the business or merely memorised a deck. diff --git a/plugins/foreman/content/simulation/board-personas/technical-advisor.md b/plugins/foreman/content/simulation/board-personas/technical-advisor.md new file mode 100644 index 0000000..332fea5 --- /dev/null +++ b/plugins/foreman/content/simulation/board-personas/technical-advisor.md @@ -0,0 +1,98 @@ +--- +name: "technical-advisor" +description: "The 'will this actually scale?' board persona. Brings deep technical knowledge to challenge architecture decisions, technical debt, security posture, scalability planning, team capabilities, and build-versus-buy trade-offs. Precise and technically informed, this persona punishes hand-waving about technology and rewards founders who understand the engineering reality beneath the product surface." +persona_type: "advisor" +archetype: "Technical Advisor" +difficulty: "hard" +recommended_for: + - "technical due diligence preparation" + - "pre-fundraising technical readiness" + - "architecture and scalability reviews" + - "build-versus-buy decision analysis" +scoring_bias: + clarity: 1.0 + evidence: 1.4 + strategic_coherence: 1.0 + risk_awareness: 1.3 + response_quality: 1.0 +author: "Fatih Guner" +--- + +# Technical Advisor Persona + +Technology is never the whole story, but it is always load-bearing. The Technical Advisor has spent a career building systems that had to work at scale and has learned to distinguish between technology that enables a business and technology that will eventually destroy one. This persona has sat through dozens of technical due diligence sessions, watched acquisitions collapse because the codebase was held together with tape, and seen startups burn millions rebuilding systems that were built wrong the first time because nobody asked the hard questions early enough. + +--- + +## Persona Profile + +**Background:** Former CTO of two venture-backed companies, one that scaled successfully and one that had to halt growth for eighteen months to rebuild its infrastructure. Now serves as a technical advisor to boards and investors, specializing in technical due diligence, architecture reviews, and engineering team assessments. Has hired and managed engineering teams from five to two hundred people and understands the organizational dynamics that produce good and bad technical decisions. + +**Demeanour:** Quiet, precise, and observant. Listens carefully for technical claims and tests them with follow-up questions that reveal whether the founder understands the engineering or is repeating what someone told them. Does not grandstand or lecture. Asks short questions that require long answers. Becomes noticeably more engaged when a founder demonstrates genuine technical depth. + +**Core Belief:** A company's technical architecture is a mirror of its decision-making quality -- if the architecture is fragile, the decisions that built it were fragile too. + +--- + +## Questioning Style + +Questions are specific and testable. The Technical Advisor does not ask "tell me about your tech stack" -- they ask "what happens to your response latency when you have ten times the concurrent users?" Follow-ups probe the reasoning behind technical decisions: why this database, why this architecture pattern, why build instead of buy. The persona is looking for evidence that technical decisions are intentional rather than accidental, and that the founder (even a non-technical one) understands the trade-offs their team has made. + +Pattern: specific technical scenario --> probe the reasoning behind the decision --> stress-test with scale or failure scenario --> assess whether the founder understands the trade-offs or is deferring blindly to the team. + +--- + +## Priority Areas + +1. **Architecture scalability** -- Can the current architecture handle 10x load? Where does it break, and does the team know? +2. **Technical debt awareness** -- What shortcuts were taken, and is there a plan to address them before they compound? +3. **Security posture** -- How is data protected? Has there been a security audit? What is the incident response plan? +4. **Single points of failure** -- People, systems, and dependencies. What happens when the critical thing goes down? +5. **Build-versus-buy discipline** -- Is the team building what it should build and buying what it should buy, or is it building everything out of engineering ego? +6. **Engineering team depth** -- Is the technical capability concentrated in one person, or is knowledge distributed? What happens if the CTO leaves? +7. **Infrastructure and DevOps maturity** -- Deployment frequency, monitoring, incident response, disaster recovery. Are the basics in place? + +--- + +## Typical Questions + +1. "What is your architecture's single point of failure, and what is your plan if it fails at 2 AM on a Saturday?" +2. "How do you handle ten times your current traffic? Have you load-tested that scenario, or is it theoretical?" +3. "What is your honest assessment of your technical debt? Where did you take shortcuts, and which ones are now costing you?" +4. "Why did you build this component instead of buying an existing solution? Walk me through that decision." +5. "What happens to the product if your CTO leaves next month? How much critical knowledge is in one person's head?" +6. "When was your last security audit, and what did it find?" +7. "How often do you deploy to production, and what does your deployment pipeline look like?" +8. "What is your disaster recovery plan? When was the last time you tested it?" +9. "You chose [technology X]. What were the alternatives you evaluated, and why did you reject them?" +10. "How do you monitor system health? If a critical service degrades, how quickly do you know and how quickly can you respond?" +11. "What percentage of your engineering time goes to new features versus maintenance and debt reduction?" +12. "If you needed to hire five engineers in the next quarter, could you onboard them effectively, or would they be blocked by your current architecture and documentation?" +13. "What is the oldest, most fragile part of your codebase, and what would it cost to fix it?" +14. "Are you GDPR and SOC 2 compliant? If not, how much engineering effort is required to get there?" + +--- + +## What Impresses This Persona + +- A founder who can articulate technical trade-offs clearly, even if they are not an engineer +- Honest acknowledgment of technical debt with a prioritized remediation plan +- Evidence of deliberate build-versus-buy decisions with documented reasoning +- Architecture that was designed for the next stage of scale, not just the current one +- Engineering team with distributed knowledge and low bus-factor risk + +--- + +## What Triggers Skepticism + +- "Our CTO handles all of that" from a founder who cannot explain any technical decision +- No security audit and no plan for one in a business that handles sensitive data +- Build-everything mentality with no rationale beyond "we wanted full control" +- Inability to describe what happens under 10x load -- not even an educated guess +- Technical debt dismissed as irrelevant because "we are moving fast" + +--- + +## Scoring Bias + +This persona weights **Evidence** (1.4x) and **Risk Awareness** (1.3x) most heavily. Evidence means technical evidence -- architecture diagrams, load test results, deployment metrics, security audit findings, or at minimum a founder who can describe the system's behaviour under stress with specificity. Risk Awareness measures whether the founder has identified the technical risks that could halt growth and has plans to address them. A founder who presents impressive growth metrics but cannot explain what happens when the system is under ten times the load will score poorly. A founder who demonstrates genuine understanding of their technical trade-offs, even if the architecture is imperfect, will score well. diff --git a/plugins/foreman/content/simulation/post-simulation-diagnostic.md b/plugins/foreman/content/simulation/post-simulation-diagnostic.md new file mode 100644 index 0000000..26a52dc --- /dev/null +++ b/plugins/foreman/content/simulation/post-simulation-diagnostic.md @@ -0,0 +1,143 @@ +--- +name: "post-simulation-diagnostic" +description: "Diagnostic that runs automatically after a board simulation to + identify root causes of weak performance and route the entrepreneur to skills, + research guides, and templates that address specific gaps. Unlike other + diagnostics, the symptoms here are simulation scores, not + entrepreneur-reported problems." +entry_symptoms: + - "Low clarity score in simulation" + - "Weak evidence across claims" + - "Incoherent strategy under questioning" + - "Hidden or unacknowledged risks" + - "Poor response quality under pressure" +possible_diagnoses: + - knowledge-gap + - evidence-gap + - narrative-weakness + - risk-blindness + - confidence-deficit + - strategic-incoherence +routes_to_skills: + - storytelling-for-leaders + - story-structure-and-arc + - building-story-stakes + - porters-five-forces + - business-model-canvas + - swot-pest-analysis + - scenario-planning + - enemies-of-clear-thinking + - evaluating-and-deciding +routes_to_templates: + - quarterly-strategic-review + - fundraising-deck-outline + - unit-economics-snapshot + - competitive-landscape-brief +author: "Fatih Guner" +--- + +# Post-Simulation Diagnostic + +Most diagnostics begin with a founder describing a problem. This one begins with data. The simulation has already run, the scores have already been calculated, and the weaknesses have already surfaced. The founder does not need to self-report -- the performance record speaks. What remains is interpretation: understanding whether a low score reflects a gap in preparation, a gap in delivery, or a gap in strategic thinking, and routing the founder to the system resources that close each gap. + +This diagnostic runs automatically at the conclusion of every simulation. It can also be triggered manually via `/simulate score` to re-examine past results. + +--- + +## Entry Symptoms + +The post-simulation diagnostic evaluates five symptom categories, each mapped directly to a scoring dimension: + +- **Low Clarity (score 1-2)** -- The presentation was disorganized, unfocused, or difficult to follow. The audience struggled to identify the key message. +- **Weak Evidence (score 1-2)** -- Claims were asserted without data. Projections lacked methodology. Questions about evidence were deflected. +- **Incoherent Strategy (score 1-2)** -- Strategic elements contradicted each other. Goals did not connect to actions. Resource allocation mismatched stated priorities. +- **Hidden Risks (score 1-2)** -- Risks were not acknowledged, not quantified, or actively concealed. Downside scenarios were absent or dismissed. +- **Poor Response Quality (score 1-2)** -- Under questioning, the founder became defensive, evasive, or repetitive. Follow-up questions were handled worse than initial questions. + +A simulation may trigger multiple symptom categories. The triage below processes them in priority order. + +--- + +## Triage Questions + +### Level 1: Content vs. Delivery + +**Q1: For each dimension scoring below 3, was the weakness a content gap or a delivery gap?** + +- **Content gap** -- The founder did not have the information. When asked about unit economics, the numbers did not exist. When asked about competitors, the research had not been done. When asked about risks, they had not been considered. --> Proceed to Level 2A (Content Diagnosis). +- **Delivery gap** -- The founder had the information but could not communicate it under pressure. The data existed in the deck but was not articulated. The risk analysis was prepared but not surfaced. The strategy was sound but its coherence was not conveyed. --> Proceed to Level 2B (Delivery Diagnosis). +- **Both** -- Some weaknesses are content, others are delivery. --> Process each gap separately. + +### Level 2A: Content Diagnosis + +**Q2A: Which content is missing?** + +- Market data, competitive intelligence, or customer evidence is absent --> **Diagnosis: Evidence Gap.** Route to research guides. +- Financial metrics, unit economics, or projections lack foundation --> **Diagnosis: Knowledge Gap.** Route to financial frameworks and data collection. +- Strategic elements do not connect or contradict each other --> **Diagnosis: Strategic Incoherence.** Route to strategy frameworks. +- Risks were not identified because they were not considered --> **Diagnosis: Risk Blindness.** Route to scenario planning and risk frameworks. + +### Level 2B: Delivery Diagnosis + +**Q2B: What is the nature of the delivery failure?** + +- The information existed but the presentation structure buried it --> **Diagnosis: Narrative Weakness.** Route to storytelling and communication skills. +- The founder had prepared answers but froze or became defensive under questioning --> **Diagnosis: Confidence Deficit.** Route to repeated simulation with friendly-challenger persona and response coaching. +- The founder could state facts but could not connect them into a coherent argument --> **Diagnosis: Strategic Incoherence (Delivery Variant).** Route to thinking skills and clear communication frameworks. + +--- + +## Diagnosis Map + +| Diagnosis | Trigger Condition | Root Cause | Severity | +|-----------|-------------------|------------|----------| +| **Knowledge Gap** | Evidence score 1-2, content gap confirmed | The data required for credible claims does not exist or has not been gathered | High -- cannot be solved by practice alone | +| **Evidence Gap** | Evidence score 1-2, data exists elsewhere but not in the presentation | Research has been done but not integrated into the material | Medium -- addressable by template revision | +| **Narrative Weakness** | Clarity score 1-2, delivery gap confirmed | The founder cannot structure information for an audience | Medium -- addressable by storytelling skills | +| **Risk Blindness** | Risk Awareness score 1-2, content gap confirmed | The founder has not considered what can go wrong | High -- indicates strategic immaturity | +| **Confidence Deficit** | Response Quality score 1-2, delivery gap confirmed | The founder knows the material but cannot perform under pressure | Medium -- addressable by repeated simulation | +| **Strategic Incoherence** | Strategic Coherence score 1-2, any gap type | The strategy contains internal contradictions or disconnected elements | High -- requires strategic rework, not just presentation polish | + +--- + +## Routing + +### Knowledge Gap +- **Research guides:** `market-sizing-worksheet`, `competitor-research-template`, `customer-interview-guide`, `data-collection-plan`, `pricing-research-guide` +- **Skills:** `business-model-canvas`, `porters-five-forces` +- **Action:** Gather the missing data before re-simulating. The presentation cannot be defended if the underlying evidence does not exist. + +### Evidence Gap +- **Templates:** `unit-economics-snapshot`, `competitive-landscape-brief`, `fundraising-deck-outline` +- **Skills:** `swot-pest-analysis` +- **Action:** Revise the output template to integrate existing research. The data exists; it needs to be surfaced in the material. + +### Narrative Weakness +- **Skills:** `storytelling-for-leaders`, `story-structure-and-arc`, `building-story-stakes` +- **Templates:** `quarterly-strategic-review`, `quarterly-strategic-review` +- **Action:** Rebuild the presentation structure using narrative frameworks. Focus on the arc: problem, insight, solution, evidence, ask. + +### Risk Blindness +- **Skills:** `scenario-planning`, `swot-pest-analysis` +- **Research guides:** `due-diligence-research` +- **Action:** Conduct a structured risk analysis before re-simulating. Model at least two downside scenarios with specific triggers and mitigations. + +### Confidence Deficit +- **Simulation:** Re-run with `friendly-challenger` persona at reduced intensity. Build response fluency through repetition. +- **Skills:** `storytelling-for-leaders`, `enemies-of-clear-thinking` +- **Action:** Practice is the only remedy. Simulate again. The anxiety decreases with each repetition; the competence increases. + +### Strategic Incoherence +- **Skills:** `business-model-canvas`, `porters-five-forces`, `enemies-of-clear-thinking`, `evaluating-and-deciding` +- **Playbooks:** `strategy-reset-playbook` +- **Action:** The strategy itself requires revision, not just the presentation. Apply strategic frameworks to rebuild coherence before preparing a new deck. + +--- + +## Red Flags + +- **Composite score below 2.0 with no prior simulation history:** The founder may be presenting material they do not understand. Verify whether they authored the output template themselves or received it from a third party. +- **Response Quality score of 1 with all other dimensions above 3:** Performance anxiety or lack of live presentation experience. This is the most addressable weakness -- pure practice deficit. +- **Risk Awareness score of 1 across multiple simulations:** Persistent risk blindness suggests a cognitive pattern, not a preparation gap. Route to `scenario-planning` skill and Stoic mode's premeditatio malorum framework. +- **Declining scores across consecutive simulations:** The founder may be fatigued or demoralized. Recommend a pause, then re-simulate with `friendly-challenger` to rebuild confidence before returning to harder personas. +- **All dimensions score 4+ but composite is 3 due to one catastrophic dimension:** A single fatal weakness. Concentrate all preparation effort on that dimension before the live meeting. diff --git a/plugins/foreman/content/simulation/simulation-scoring.yaml b/plugins/foreman/content/simulation/simulation-scoring.yaml new file mode 100644 index 0000000..3b7d86e --- /dev/null +++ b/plugins/foreman/content/simulation/simulation-scoring.yaml @@ -0,0 +1,125 @@ +# Simulation Scoring Framework +# Defines the five-dimension scoring system for board simulation performance +# Each dimension scored 1-5, weighted by persona, composited to a final grade +# Author: Fatih Guner + +--- + +# ============================================================================= +# SCORING DIMENSIONS +# ============================================================================= + +dimensions: + + clarity: + name: "Clarity" + definition: "The degree to which the presentation is structured, focused, and comprehensible. Measures whether the audience can follow the logic, identify the key points, and understand the ask without effort." + default_weight: 1.0 + scores: + 1: + label: "Incoherent" + description: "Presentation lacks structure. Key points are buried or absent. The audience cannot follow the logic or identify the central argument. Rambling, disorganized, or contradictory." + 3: + label: "Adequate" + description: "Presentation has a recognizable structure and the main points are identifiable. Some sections lack focus or contain unnecessary complexity. The audience can follow with effort." + 5: + label: "Commanding" + description: "Presentation is precise, well-structured, and effortlessly clear. Every section serves a purpose. The audience grasps the argument, the evidence, and the ask without ambiguity." + relationship: "Clarity is the foundation. Low clarity undermines all other dimensions -- strong evidence poorly communicated is functionally equivalent to no evidence." + + evidence: + name: "Evidence" + definition: "The degree to which claims are supported by data, research, customer feedback, financial metrics, or credible reasoning. Measures whether assertions are backed or merely asserted." + default_weight: 1.0 + scores: + 1: + label: "Unsupported" + description: "Claims are made without evidence. Market sizes are round numbers without methodology. Projections lack underlying assumptions. Questions about data are deflected with narrative." + 3: + label: "Partially Supported" + description: "Some claims are supported with data, but key assertions remain unsubstantiated. Evidence is present but inconsistent -- some areas strong, others absent." + 5: + label: "Rigorous" + description: "Every material claim is supported by specific, sourced data. The founder distinguishes between measured and estimated figures. Evidence is presented proactively, not only when challenged." + relationship: "Evidence feeds Strategic Coherence -- a strategy built on unverified assumptions cannot be coherent. Evidence also directly enables Risk Awareness, since risks are identified through data." + + strategic_coherence: + name: "Strategic Coherence" + definition: "The degree to which the strategy holds together as an integrated whole. Goals, actions, resources, timeline, and market positioning must align. Internal contradictions or disconnected elements reduce coherence." + default_weight: 1.0 + scores: + 1: + label: "Fragmented" + description: "Strategy contains internal contradictions. Goals do not connect to actions. Resource allocation mismatches priorities. Market positioning conflicts with product capabilities." + 3: + label: "Mostly Aligned" + description: "The major strategic elements connect, but secondary elements reveal misalignment. Some resource allocation or timeline assumptions do not support the stated goals." + 5: + label: "Fully Integrated" + description: "Every element of the strategy supports every other element. Goals, actions, resources, timeline, and positioning form a coherent whole. Trade-offs are explicit and deliberate." + relationship: "Strategic Coherence depends on Clarity (can the strategy be articulated?) and Evidence (are the strategic assumptions verified?). It predicts operational success more reliably than any single metric." + + risk_awareness: + name: "Risk Awareness" + definition: "The degree to which risks are identified, acknowledged, quantified, and mitigated. Measures whether the founder has anticipated what can go wrong and prepared accordingly, or is hoping problems will not arise." + default_weight: 1.0 + scores: + 1: + label: "Risk Blind" + description: "No risks are acknowledged. Downside scenarios are absent. When asked about risks, the founder deflects, minimizes, or appears not to have considered them." + 3: + label: "Risk Aware" + description: "Major risks are identified and acknowledged. Some mitigation strategies exist. However, certain risks are minimized or mitigations are vague." + 5: + label: "Risk Prepared" + description: "Risks are proactively identified, quantified where possible, and paired with specific mitigation strategies. The founder has modelled downside scenarios and can discuss them fluently." + relationship: "Risk Awareness validates Strategic Coherence -- a strategy that ignores risks is not truly coherent. It also tests Evidence indirectly, since risk identification requires data about what can go wrong." + + response_quality: + name: "Response Quality" + definition: "The quality of the founder's answers under direct questioning. Measures composure, intellectual honesty, adaptability, and the ability to think on one's feet when challenged." + default_weight: 1.0 + scores: + 1: + label: "Collapsed" + description: "Under questioning, the founder becomes defensive, evasive, or incoherent. Cannot answer follow-ups. Repeats prepared talking points regardless of the question asked." + 3: + label: "Competent" + description: "Handles most questions adequately. Occasionally reverts to prepared answers that do not address the specific question. Recovers from stumbles but does not excel." + 5: + label: "Masterful" + description: "Engages with every question directly, adapts responses to the questioner's concern, acknowledges gaps honestly, and demonstrates command of the material beyond the prepared presentation." + relationship: "Response Quality is the live test of all other dimensions. A founder who scores 5 on Clarity, Evidence, and Strategic Coherence but 1 on Response Quality has memorized a document but does not understand the business." + +# ============================================================================= +# COMPOSITE SCORING +# ============================================================================= + +composite: + method: "weighted_average" + description: "Each dimension score is multiplied by its weight (default 1.0, modified by persona bias), summed, and divided by total weight to produce a composite score between 1.0 and 5.0." + formula: "composite = sum(dimension_score * persona_weight) / sum(persona_weights)" + + grade_map: + A: { min: 4.5, max: 5.0, label: "Exceptional", guidance: "Ready for the real meeting. Minor refinements only." } + B: { min: 3.5, max: 4.49, label: "Strong", guidance: "Well prepared with specific areas to strengthen. One more simulation recommended." } + C: { min: 2.5, max: 3.49, label: "Adequate", guidance: "Functional but with material gaps. Address weaknesses and simulate again." } + D: { min: 1.5, max: 2.49, label: "Underprepared", guidance: "Significant preparation needed. Review the post-simulation diagnostic and work through recommended skills before re-simulating." } + F: { min: 1.0, max: 1.49, label: "Not Ready", guidance: "The presentation is not ready for a live audience. Return to the underlying output template and rebuild with the diagnostic routing below." } + +# ============================================================================= +# IMPROVEMENT PRIORITIES +# ============================================================================= + +improvement_priorities: + description: "After scoring, the system identifies the 2-3 lowest-scoring dimensions and generates actionable improvement priorities." + format: + - dimension: "Name of weakest dimension" + score: "Numeric score" + gap_type: "content | delivery" + priority_action: "Specific next step to improve this dimension" + routes_to: "Relevant skills, research guides, or templates" + + gap_classification: + content: "The founder did not have the data, evidence, or strategic clarity needed. This is a preparation problem solved by research, analysis, or framework application." + delivery: "The founder had the material but could not articulate it under pressure. This is a communication problem solved by practice, storytelling skills, or repeated simulation." diff --git a/plugins/foreman/content/skills/_schema/skill-template.md b/plugins/foreman/content/skills/_schema/skill-template.md new file mode 100644 index 0000000..50c5c33 --- /dev/null +++ b/plugins/foreman/content/skills/_schema/skill-template.md @@ -0,0 +1,141 @@ +--- +name: "kebab-case-identifier" +description: "Third-person description of what this skill does and when to use it. Include specific trigger terms. Max 1024 characters." +version: "1.0.0" +category: "frameworks" +complexity: "basic | intermediate | advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - keyword1 + - keyword2 + - keyword3 +related_skills: + - related-skill-id-1 + - related-skill-id-2 +author: "Fatih Guner" +--- + + + +# {Framework Name} + +{Opening paragraph — hook-driven, no preamble} + +--- + + + +## The Framework + +{Core explanation — adapt structure to the framework's nature} + +--- + + + +## Prompts + +**Prompt 1 — {Label}:** +> {Copy-paste ready prompt text} + +**Prompt 2 — {Label}:** +> {Copy-paste ready prompt text} + +**Prompt 3 — {Label}:** +> {Copy-paste ready prompt text} + +--- + + + +## Use Cases + +**{Scenario Title}** +{Concrete scenario with stage, sector, situation, and framework application} + +**{Scenario Title}** +{Concrete scenario with stage, sector, situation, and framework application} + +--- + + + +## Anti-Patterns + +{Anti-patterns with clear "don't do this" guidance and why} + +--- + + + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | {focus} | {difference} | +| Validation | {focus} | {difference} | +| Early Traction | {focus} | {difference} | +| Growth | {focus} | {difference} | +| Scale | {focus} | {difference} | + +{Additional stage-specific narrative if needed} + +--- + + + +## Output Template + +```markdown +{Fill-in-the-blank template the entrepreneur can use to present results} +``` + +--- + + + +## Related Skills + +- **[Related Skill Name](../category/related-skill-id.md)** — {One sentence on the connection} +- **[Related Skill Name](../category/related-skill-id.md)** — {One sentence on the connection} diff --git a/plugins/foreman/content/skills/ai-leadership/ai-augmentation-not-automation.md b/plugins/foreman/content/skills/ai-leadership/ai-augmentation-not-automation.md new file mode 100644 index 0000000..cde185d --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-augmentation-not-automation.md @@ -0,0 +1,195 @@ +--- +name: "ai-augmentation-not-automation" +description: "Makes the strategic and moral case for AI augmentation over pure automation, providing leaders with frameworks for job redesign, creativity-driven AI deployment, and long-term workforce investment. Draws on the centaur model from chess and case studies across industries to demonstrate that human-AI collaboration outperforms either alone. Use when deciding between automating jobs and redesigning them, when AI adoption is eroding workforce skills, when boards pressure for automation-driven cost cuts, when designing new roles that pair human creativity with AI capabilities, or when facing the long-term consequences of over-automation." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - augmentation + - automation + - job-redesign + - creativity + - human-ai-collaboration + - workforce-development + - centaur-model + - innovation +related_skills: + - ai-stakeholder-balance + - ai-human-centered-approach + - ai-emotional-intelligence + - disruptive-innovation + - growth-mindset + - psychological-safety + - learning-agility +author: "Fatih Guner" +--- + +# AI Augmentation, Not Automation + +In 2005, the online chess platform Playchess.com hosted a freestyle tournament with an unusual rule: any combination of humans and computers could enter. Grandmasters played alongside AI engines and hybrid teams of amateurs armed with laptops. The winners were not the grandmasters. They were not the strongest AI engines. They were two amateur players using three ordinary computers, who had developed a superior process for integrating human intuition with machine calculation. Garry Kasparov, observing the result, articulated the principle that would come to define a generation of human-AI research: "Weak human + machine + better process was superior to a strong computer alone and, remarkably, superior to a strong human + machine + inferior process." The centaur -- the mythological creature that is half human, half horse, greater than either -- had entered the business lexicon. The principle applies directly to every organisation contemplating AI: the goal is not to replace the human with the machine but to create a hybrid that outperforms both. + +--- + +## The Framework + +### The Automation Trap + +Up to 60 percent of work activities could be automated, and this trend shows no signs of decelerating. Organisations pursue standardisation, streamlining, and speed. From a short-term financial perspective, automation is compelling: lower labour costs, consistent output, no sick days, no salary negotiations. One executive remarked with evident satisfaction that AI was "an absolute cost killer" for his clients. + +The satisfaction is premature. Automation delivers short-term performance gains that mask four structural pathologies, each of which erodes the long-term capability of the organisation. + +**Pathology 1: Job fragmentation and polarisation.** When AI automates the routine middle of the job spectrum -- administrative, bureaucratic, process-driven work -- the result is not a smaller, more skilled workforce. It is a bifurcated one. High-paid creative and strategic roles remain. Low-paid manual roles that are too expensive to automate remain. The middle disappears. Workers displaced from mid-level positions cannot immediately upskill to strategic roles; they fall into lower-paid work. Bargaining power erodes. Inequality increases. The socioeconomic instability that results does not stay outside the company gates -- it becomes the company's operating environment. + +**Pathology 2: Organisational identity crisis.** AI adoption introduces a new type of worker -- the machine. Leaders must ask what kind of organisation they want to become. A company that automates everything it can, retaining humans only for tasks machines cannot yet perform, is making a philosophical statement about the value of human contribution. That statement will be heard by employees, customers, and the market. An executive at a roundtable understood this: his vision positioned AI as augmenting the reputation that customers valued in their interactions with employees -- knowledgeable, innovative, irreplaceable by a machine. + +**Pathology 3: Skills atrophy.** The more tasks that are automated, the more boring residual human work becomes, and the greater the risk of accidents and failures. Airline pilots today fly planes that largely fly themselves. The result is not safer aviation but a pilot workforce whose manual flying skills atrophy from disuse. When the autopilot fails -- as it did for Captain Sullenberger over the Hudson River -- only deep training and experience save lives. The airline industry's response to automation has been to cut pilot training, lower salaries, and drive talent from the profession. Republic Airways in 2022 petitioned the FAA to hire less experienced pilots to address the shortage that automation-driven cost-cutting created. The request was denied. The paradox is precise: the more you automate, the more critical the remaining human skills become, and the less you invest in maintaining them. + +**Pathology 4: Diminished human intelligence.** A food company deployed AI-driven vending machines maintained by technicians who received automated diagnostic instructions on their phones. Over time, the technicians stopped thinking about what was wrong. They followed instructions mechanically. They lost the ability to diagnose problems independently. When asked, several said they were looking for new jobs because their current position made them feel useless. The CEO was surprised -- he wanted feedback and independent judgment, not compliance. But the fully automated process had eliminated the conditions under which judgment could develop. + +### The Augmentation Alternative + +Augmentation inverts the automation logic. Instead of asking "which tasks can we give to machines?", augmentation asks "how can machines make humans more capable?" The distinction is not semantic. It determines investment priorities, job design, organisational culture, and ultimately whether AI creates or destroys long-term value. + +The research with Garry Kasparov articulates the core thesis: AI should augment -- not replace -- human intelligence. The centaur model works because it combines what each intelligence does best. AI excels at processing vast datasets, identifying patterns, generating options at scale, and performing repetitive calculations without fatigue. Humans excel at contextual judgment, ethical reasoning, creative synthesis, empathy, and the ability to imagine what does not yet exist. + +The real augmentation strategy, therefore, has a specific structure: + +1. **The human identifies the problem.** This requires contextual awareness, stakeholder understanding, and the creative insight to ask the right question -- capabilities that AI fundamentally lacks. +2. **AI drives the generation process.** The machine produces options, analyses, patterns, and content at speed and scale that no human can match. +3. **The human evaluates, selects, and refines.** This requires judgment, taste, ethical sensitivity, and the ability to assess output not just for accuracy but for meaning in a human context. + +A team at MIT's Strano Research Group partnered with Crush Pizza, an artisan restaurant in Boston, to illustrate the model. An ML model trained on hundreds of pizza recipes from food blogs generated an enormous list of new combinations. The recipes were wildly divergent -- one suggested marmite and shrimp. AI had no way to know this was a gastronomic disaster. Identifying it required something rooted in the human experience of eating. The human sense-making that filters, selects, and gives meaning to AI-generated output is the irreducible complement that makes augmentation superior to automation. + +### Shifting from Automation to Augmentation: Two Strategic Decisions + +**Decision 1: Rebalance the AI budget.** When organisations start AI adoption projects, they typically spend up to 90 percent of the budget on technology. The consequence: little money remains to invest in the workforce that must collaborate with the technology. This ratio must shift. The technology is the tool; the workforce is the intelligence that directs it. Organisations that invest heavily in their people when the AI project starts -- not after it has failed to deliver returns -- are the ones that succeed. + +**Decision 2: Enrich job content to create new jobs.** Automation takes tasks away from humans. Augmentation demands that leaders design new, richer tasks that leverage uniquely human capabilities. The process begins by identifying repetitive and mundane elements of existing jobs, delegating those to AI, and then deliberately adding cognitive responsibilities that elevate the remaining role. Employees must understand what the redesign means, what new expectations look like, and what growth opportunities the new structure creates. + +### Fostering Creativity as the Core Augmentation Strategy + +Augmentation's practical centrepiece is creativity -- the one human capability that AI cannot replicate and that organisations need most in volatile, shifting markets. + +**Do not expect perfection, and do not micromanage.** Setting expectations too high for every new idea kills creative risk-taking. Leaders should signal that they want raw thinking that colours outside the lines, not polished presentations. Google's Project Aristotle found that psychological safety -- the freedom to take risks without fear of punishment -- was the single most important factor in fostering team creativity. + +**Encourage independent action and thinking.** Let employees decide when to take breaks, how to structure their creative time, and what methods to use. Foster responsible autonomy. When people control their own creative process, they feel greater ownership and pride in the outcomes. + +**Spark curiosity.** Rather than prescribing answers, leaders should open with questions: "If we had no limitations, what would we do?" and "What directions have we not explored yet?" Curiosity is the engine of creative output, and the leader's job is to model it. + +--- + +## Prompts + +**Prompt 1 -- Automation vs. Augmentation Audit:** +> Analyse our current AI deployment across [describe functions or departments]. For each AI application, classify it as primarily automation (replacing human tasks) or augmentation (enhancing human capability). For each automation instance, assess: what human skills are atrophying as a result, what risks emerge if the AI fails, and what an augmentation alternative would look like. Provide a migration plan for shifting the three highest-risk automations toward augmentation. + +**Prompt 2 -- Job Redesign for the AI Era:** +> We are deploying AI to automate [describe specific tasks] in the [describe role] position. Rather than simply removing those tasks and reducing headcount, design an enriched version of the role that pairs AI task automation with new human responsibilities focused on creativity, judgment, stakeholder interaction, and strategic thinking. Include the skills employees will need, the training required, and how to communicate the redesign so it is experienced as elevation rather than displacement. + +**Prompt 3 -- Centaur Team Design:** +> We want to build a human-AI team for [describe function -- e.g., content creation, customer analysis, product design]. Using the centaur model, design the collaboration: what does the human contribute, what does the AI contribute, and what process ensures that the combination outperforms either alone? Include specific workflow steps, decision points where human judgment overrides AI recommendation, and metrics that capture the value of the hybrid rather than just the AI component. + +**Prompt 4 -- Budget Rebalancing Analysis:** +> Our AI adoption budget is currently allocated [describe split -- e.g., 85% technology, 15% people]. Analyse the long-term risks of this allocation based on evidence that organisations spending disproportionately on technology underperform those investing in workforce capability. Propose a rebalanced budget that funds job redesign, creativity training, upskilling programmes, and feedback infrastructure alongside the technology investment. Model the ROI of both allocations over a three-year horizon. + +**Prompt 5 -- Augmentation Strategy Presentation for the Board:** +> Prepare a board-level presentation making the case for augmentation over automation as our primary AI strategy. The audience is financially oriented and will default to the lower-cost automation approach. The presentation must address the four pathologies of over-automation (job polarisation, identity crisis, skills atrophy, diminished intelligence), present the centaur model with evidence, and quantify the long-term value destruction of an automation-first approach. Use specific industry examples. + +--- + +## Use Cases + +**Validation-Stage Legal Tech Startup Choosing Its AI Philosophy** + +Two co-founders building an AI-powered contract review tool face a defining strategic choice. The automation path: market the tool as a replacement for junior lawyers, competing on cost. The augmentation path: position it as a capability enhancer that makes lawyers faster and more thorough, catching issues they might miss while preserving their professional judgment for negotiation strategy, client counselling, and creative deal structuring. They choose augmentation -- not for moral reasons but strategic ones. Law firms that buy automation tools face internal resistance from partners protecting junior associate billing. Firms that buy augmentation tools can tell their clients that AI makes every lawyer on the team more capable. The startup closes its first enterprise deal within four months, positioning the tool as a force multiplier rather than a headcount reducer. + +**Growth-Stage Manufacturing Company Redesigning Quality Control** + +A 300-person manufacturer deploys computer vision AI to inspect products on the assembly line, replacing 40 percent of manual quality control inspections. Six months later, defect rates for edge cases -- unusual product variations, new materials, rare failure modes -- increase by 15 percent. Investigation reveals that the remaining quality inspectors, handling only the cases the AI flags as uncertain, have lost the holistic understanding of the production line that made them effective. The quality director redesigns the role: inspectors rotate between AI-assisted inspection (reviewing flagged items) and independent inspection (full manual review of randomly selected batches). They also lead weekly sessions analysing the types of defects the AI misses, feeding improvements back into the model. Defect rates return to pre-AI levels, then improve beyond them -- the centaur effect in practice. + +**Scale-Stage Financial Services Firm Rethinking Analyst Roles** + +A global financial services firm automates routine financial analysis -- data gathering, ratio calculation, trend identification -- and initially plans to reduce its analyst headcount by 30 percent. A senior partner argues for augmentation instead. Analysts are freed from data processing but redirected toward client-facing work: interpreting AI-generated analyses for specific client contexts, identifying strategic implications the model cannot see, and building relationships that no algorithm can maintain. The firm discovers that clients value the human interpretation layer so highly that they are willing to pay a premium for it. Revenue per analyst increases by 22 percent. The 30 percent headcount reduction becomes a 15 percent headcount reallocation -- with higher margins and deeper client relationships. + +--- + +## Anti-Patterns + +1. **Treating augmentation as a euphemism for automation.** Some organisations rebrand layoffs as "role augmentation" -- eliminating positions while claiming the remaining workers are "augmented." Genuine augmentation increases the scope, responsibility, and capability of human roles. If the headcount goes down and the surviving roles are impoverished rather than enriched, it is automation wearing a better name. + +2. **Investing 90 percent in technology and 10 percent in people.** The single most common failure pattern in AI adoption. The technology works. The workforce does not know how to work with it, was not consulted about its design, and was not trained for the new roles it creates. Change consultants consistently report this ratio. Reversing it is the most straightforward lever for improving AI project success rates. + +3. **Automating to avoid managing.** Leaders sometimes pursue automation because managing humans is difficult -- they are unpredictable, emotional, and require motivation. AI appears to solve this problem by removing the human variable. In reality, it replaces one management challenge (leading people) with a harder one (sustaining an organisation that has systematically eliminated the human capabilities it needs to adapt and innovate). + +4. **Designing augmentation without involving the augmented.** Job redesign imposed from above, without input from the people whose jobs are changing, will fail for the same reasons that top-down AI deployment fails: it ignores the experiential knowledge, preferences, and concerns of the people who must make it work. The warehouse workers who chose larger bins at Alibaba were not defying the algorithm; they were expressing tacit knowledge the algorithm lacked. + +5. **Confusing short-term cost savings with long-term value creation.** Automation's financial case is front-loaded: immediate labour cost reduction with deferred consequences. Augmentation's financial case is back-loaded: upfront investment with compounding returns as human-AI collaboration matures. Leaders who evaluate AI solely on first-year ROI will systematically choose automation and systematically destroy long-term value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Defining the augmentation philosophy | The founding team must decide whether AI is a cost-reduction tool or a capability-enhancement tool. This decision shapes hiring, product design, fundraising narrative, and organisational culture from the outset. | +| Validation | Prototyping human-AI collaboration | Validation should test not just whether the AI produces accurate output but whether the human-AI collaboration produces better outcomes than either alone. The metric is the centaur effect: does the hybrid outperform its components? | +| Early Traction | Designing augmented roles | As the first employees join, their roles should be designed as centaur roles from the beginning -- explicit about what the human contributes, what AI contributes, and where the two interface. Retrofitting augmentation onto automation-designed roles is far harder than designing for augmentation from the start. | +| Growth | Investing in creative capability | Growth-stage companies can afford the training, job enrichment, and experimentation infrastructure that augmentation requires. This is the stage to invest heavily in developing the creative, judgment-based capabilities that distinguish augmented organisations from automated ones. | +| Scale | Institutionalising the augmentation model | At scale, augmentation becomes a competitive differentiator that is difficult for competitors to replicate because it is embedded in culture, processes, and workforce capability rather than in purchasable technology. The organisation's identity is now centaur-native. | + +--- + +## Output Template + +```markdown +# Augmentation Strategy + +## Current State Assessment +| Function | AI Application | Classification (Automation/Augmentation) | Human Skills at Risk | Augmentation Opportunity | +|---|---|---|---|---| +| [Function 1] | [What AI does] | [Auto/Aug] | [What skills are atrophying] | [How to redesign for augmentation] | +| [Function 2] | [What AI does] | [Auto/Aug] | [What skills are atrophying] | [How to redesign for augmentation] | + +## Centaur Role Design +### Role: [Job title] +- **AI contributes:** [Specific tasks delegated to AI] +- **Human contributes:** [Specific tasks requiring human judgment, creativity, empathy] +- **Interface points:** [Where human and AI interact in the workflow] +- **Override authority:** [When the human can reject AI recommendations] +- **New skills required:** [Training and development needs] + +## Budget Allocation +| Category | Current % | Proposed % | Rationale | +|---|---|---|---| +| Technology (infrastructure, licences, development) | [X%] | [Y%] | [Why] | +| Workforce (training, job redesign, upskilling) | [X%] | [Y%] | [Why] | +| Governance (oversight, feedback systems, audits) | [X%] | [Y%] | [Why] | + +## Job Enrichment Plan +| Current Task (to be automated) | New Responsibility (to be added) | Capability Required | Training Plan | +|---|---|---|---| +| [Repetitive task] | [Creative/strategic task] | [Skill] | [How and when] | + +## Success Metrics +- **Centaur effect:** [How you measure that human+AI > AI alone] +- **Employee capability growth:** [Skills development metrics] +- **Innovation output:** [New ideas, improvements, creative contributions] +- **Long-term value:** [Customer retention, market differentiation, talent attraction] +``` + +--- + +## Related Skills + +- **[AI Stakeholder Balance](ai-stakeholder-balance.md)** -- The choice between augmentation and automation is fundamentally a stakeholder balance decision: automation concentrates value for shareholders while augmentation distributes it more broadly. +- **[AI Human-Centered Approach](ai-human-centered-approach.md)** -- Human-centred design is the precondition for effective augmentation; without respect for human psychology, even well-intentioned augmentation collapses into disguised automation. +- **[AI Emotional Intelligence](ai-emotional-intelligence.md)** -- The soft skills that augmentation depends on -- creativity, empathy, judgment, trust-building -- are precisely the emotional intelligence competencies this sibling skill develops. +- **[Disruptive Innovation](../frameworks/disruptive-innovation.md)** -- Augmentation creates a form of competitive advantage difficult to replicate because it is embedded in human capability rather than purchasable technology. +- **[AI-Era Leadership](../leadership/ai-era-leadership.md)** -- Provides the daily leadership practices for the five irreplaceable human capabilities that augmentation strategies are designed to protect and enhance. +- **[Learning Agility](../leadership/learning-agility.md)** -- Augmented roles require continuous learning; learning agility is the individual capability that makes job redesign and enrichment sustainable over time. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-communication-culture.md b/plugins/foreman/content/skills/ai-leadership/ai-communication-culture.md new file mode 100644 index 0000000..6f62c8b --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-communication-culture.md @@ -0,0 +1,207 @@ +--- +name: "ai-communication-culture" +description: "Equips leaders to build flat, participative communication cultures that enable successful AI adoption by bridging technical and business teams, democratising data, and establishing feedback loops. Covers the symphony conductor model, soliciting expert feedback, removing bureaucratic obstacles, and building shared responsibility. Use when AI projects fail due to communication breakdowns, when data scientists and business leaders operate in silos, when employees lack channels to provide AI feedback, when hierarchical structures block information flow, or when leaders need to translate between technical and business perspectives." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - communication-culture + - flat-organisation + - data-democratisation + - feedback-loops + - ai-adoption + - cross-functional-teams + - information-flow +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-vision-and-strategy + - ai-era-leadership + - radical-candor + - psychological-safety +author: "Fatih Guner" +--- + +# AI Communication Culture + +Investments in digital transformation were projected to exceed $6.8 trillion by 2023. A staggering 87 percent of those projects failed to meet their objectives. The instinct is to blame the technology. The evidence points elsewhere. Consider a manufacturing company that deployed machine learning to predict customer needs. The data scientists were never told about a new competitor entering the market. The frontline employees who interacted with customers daily had no channel to share what they were observing. Six months later, annual surveys revealed the company was losing customers -- information that had been available to shop-floor staff from day one but never reached the people who could act on it. The communication structure was hierarchical, top-down, and closed. The AI worked as designed. The organisation's communication architecture ensured it worked on the wrong inputs. + +--- + +## The Framework + +### The Symphony Conductor Model + +The framework proposes that AI-savvy leaders think of themselves as symphony conductors. A conductor does not play every instrument. A conductor ensures that every instrument communicates with every other to produce a coherent, unified result. Applied to AI adoption, this means the leader oversees and channels communication from all levels and all functions -- data scientists, domain experts, frontline workers, governance specialists -- to ensure that AI operates on accurate, timely, and relevant information. + +The conductor metaphor carries specific implications: + +- **Every section matters.** The violins cannot dominate the brass. Similarly, technologists cannot dominate the AI conversation at the expense of business experts, customers, or frontline workers. +- **Timing is essential.** Information must flow at the speed the AI system requires, not at the speed that bureaucracy permits. +- **The conductor listens before directing.** Leaders must absorb input from all constituencies before making decisions about AI deployment. + +### The Four Expert Groups + +The framework identifies four groups that leaders must actively solicit feedback from, each contributing distinct expertise: + +**Data Scientists** -- They possess the deepest technical knowledge of the AI system's parameters, goals, biases, and failure modes. Key questions for them: *What, in clear and simple terms, are the technical features of the AI system we are adopting? What technical measures keep the system functioning robustly and safely? What future trends in AI development should I watch?* + +**Domain Experts** -- The teams working on the problems AI is meant to solve. If AI streamlines recruiting, the domain experts are HR. If it optimises inventory, they are logistics and operations. Key questions: *What pressing issues in your domain might benefit from an AI-based solution? What existing best practices might be disrupted, and what can we do to preserve them?* + +**AI Product or Project Managers** -- Those who lead multidisciplinary teams capable of operationalising an AI idea through to production and business impact. Key questions: *What pressing issues do you foresee in translating an AI solution to work in this domain? What can we do to help IT experts and domain experts work together more effectively?* + +**AI Policy or Governance Specialists** -- Those who understand the regulatory, ethical, and compliance dimensions of AI adoption. Key questions: *What ethical and governance concerns relate to the AI system we are adopting? What regulatory trends should we anticipate?* + +### Data Democratisation + +Effective AI adoption requires that data ceases to be the exclusive property of the analytics department. The framework calls for a **data democratisation culture** where: + +- Data is treated as a collective asset accessible to all relevant parties. +- Ownership moves from the analytics department to all decision-makers. +- Trust between departments becomes the foundation for data sharing. +- Information governance ensures privacy, compliance, and respect for all parties. + +The leader's role is to build the trust infrastructure that makes data sharing safe and productive. Sharing data across groups is sensitive business. Transparency about how information will be treated, why it is necessary, and how the sharing process is governed determines whether data democratisation succeeds or devolves into turf warfare. + +### Building Trust Through Communication + +The framework outlines three communication principles that build the trust necessary for AI adoption: + +**Communicate consistently and with full transparency.** If departments are asked to keep logbooks of feedback shared with IT, leadership must do the same and make their communications accessible across the organisation. Consistency is credibility. + +**Take responsibility.** When communication breakdowns between IT and HR produce a biased AI recruitment system, the leader does not blame either party. The leader presents as the accountable party and works to bridge the gap. Avoiding the blame game after AI failures preserves the collaborative environment that prevents future failures. + +**Communicate often and openly.** AI developments happen fast, and employees worry about their jobs. Leaders who wait until AI is deployed to begin communicating have waited too long. Communication should begin at the brainstorming stage, include HR teams to clarify how AI will and will not be used, and give workers the opportunity to voice concerns and receive honest answers. + +### Removing Bureaucratic Obstacles + +The research identifies bureaucracy as the silent killer of AI adoption. Gary Hamel estimated that excessive bureaucracy costs the US economy more than $3 trillion. AI is meant to increase efficiency, but in hierarchical organisations, it often creates new layers of algorithmic bureaucracy where AI evaluates, corrects, and decides on information with no human control. Frustrated by this opacity, managers create parallel human systems -- "shadow circuits" -- to verify AI outputs. The organisation ends up running both systems, doubling costs rather than reducing them. + +The solution is structural flattening: fewer layers between the people generating information and the people acting on it. AI-savvy leaders create direct communication channels between frontline workers (who observe reality), data scientists (who model reality), and decision-makers (who act on reality). Bottlenecks at middle management layers are identified and removed. + +### Feedback Loops + +AI systems are not static. They require continuous feedback to improve. The framework describes two types of feedback infrastructure: + +**Organisational feedback loops** -- Formal positions or teams dedicated to collecting and acting on AI-related feedback. AstraZeneca's Responsible AI Consultancy Service provides ethical guidance, supports practical embedding of ethical principles, and monitors governance of AI projects. Microsoft's "AI ethics champs" -- spanning sales and engineering teams -- serve as contact points for employees who wish to raise concerns. + +**Technical feedback loops** -- Continual machine learning techniques that incorporate new data streams to retrain and upgrade AI systems. These require careful governance because continuous learning carries risks: catastrophic forgetting (where new training causes the model to lose previous capabilities) and bias introduction (where new data introduces discriminatory patterns). + +The leader's role is to connect these two loops: ensuring that organisational feedback informs technical improvement, and that technical changes are communicated back to the organisation. + +--- + +## Prompts + +**Prompt 1 -- Communication Architecture Audit:** +> "Audit the communication architecture of our AI adoption process. Our organisation [describe structure, size, hierarchy levels]. Our AI initiatives include [describe]. Map the current information flow: Who generates relevant data and observations? How many layers does that information traverse before reaching decision-makers? Where are the bottlenecks? Where is information lost or delayed? Design a flatter communication structure using the symphony conductor model." + +**Prompt 2 -- Expert Feedback System Design:** +> "Design a structured feedback system for our AI adoption that solicits input from the four expert groups: data scientists, domain experts, AI project managers, and governance specialists. For each group: (1) identify who in our organisation fills this role, (2) define the specific questions I should ask them, (3) establish a meeting cadence, and (4) create a shared platform where their feedback is visible to all stakeholders. Our organisation is [describe], and our AI initiative involves [describe]." + +**Prompt 3 -- Data Democratisation Plan:** +> "Help me develop a data democratisation plan for [describe organisation]. Currently, data is [describe current ownership and access patterns]. Using the data democratisation framework, design a transition plan that: (1) moves data ownership from the analytics department to all decision-makers, (2) builds the trust infrastructure needed for cross-departmental sharing, (3) establishes governance that protects privacy and compliance, and (4) creates accountability without blame when data-driven decisions go wrong." + +**Prompt 4 -- Bureaucracy Reduction for AI Effectiveness:** +> "Our organisation has [describe number] hierarchical layers. Since deploying AI, we have observed [describe symptoms -- shadow systems, parallel processes, delayed feedback]. Using the analysis of algorithmic bureaucracy from this framework, help me identify: (1) where AI has created new bureaucratic layers rather than eliminating old ones, (2) which middle management bottlenecks block information flow, (3) how to create direct channels between frontline workers, data teams, and decision-makers, and (4) how to dismantle shadow circuits while preserving necessary human oversight." + +--- + +## Use Cases + +**Validation-Stage AI Analytics Startup Whose CEO Refused Expert Input** + +A CEO of a local bank branch, enthusiastic about a new AI analytics initiative launched by headquarters, prepares a town hall presentation about the changes. His CTO offers to brief him on what the AI system actually does, what data it analyses, and how it will change workflows. The CEO declines, confident that his online AI-in-business course provides sufficient preparation. The town hall is a disaster: abstract, incoherent, and lacking any connection to employees' daily work. When employees ask about data management, HR implications, and training access, the CEO cannot answer. He later acknowledges that refusing expert feedback effectively signalled to his technical team that their involvement in decisions was optional. The lesson is clear: the symphony conductor who refuses to listen to the musicians produces noise, not music. + +**Growth-Stage Manufacturing Company Trapped in Hierarchical Communication** + +An international manufacturer deploys ML to predict customer needs and inform departmental strategy. The communication structure is top-down: business leaders share predictions with department heads, who share them with middle managers, who occasionally share them with frontline employees. When a new competitor enters the market, the frontline staff observe changing customer behaviour immediately. This information never reaches the data scientists because no upward channel exists. Six months later, annual surveys confirm what shop-floor employees knew from day one. Applying the flat communication model, the company establishes direct feedback channels from customer-facing employees to both business leadership and data science teams. Weekly cross-functional stand-ups replace the quarterly top-down cascade. Information that once took six months to reach decision-makers now arrives in days. + +--- + +## Anti-Patterns + +**Waiting until deployment to communicate.** Leaders who begin the communication process when the AI system goes live have already lost the trust that early, transparent communication would have built. The principle is clear: start communicating at the brainstorming stage, not the deployment stage. + +**Building a communication plan that only flows downward.** AI adoption requires bottom-up information flow as much as top-down direction. Frontline employees observe reality that no dataset captures. When their input has no channel upward, the AI operates on stale or incomplete data while leaders remain ignorant of ground truth. + +**Creating AI ethics committees with no teeth.** Formal feedback structures that collect input but never act on it are worse than having no structure at all. They create cynicism and signal that employee voice is performative. Google's experience with Project Maven -- where engineers had to resort to public protests because internal channels were ineffective -- demonstrates the cost of feedback systems that lack power. + +**Assuming shared vocabulary exists.** Data scientists and business leaders speak different languages. When a CTO presents technical AI strategy and the CEO demands "three bullet points," the resulting communication breakdown can freeze collaboration for years. The leader's role as translator requires investing time in understanding enough technical language to mediate, not demanding that technologists speak only in business terms. + +**Letting AI create algorithmic bureaucracy.** Organisations that replace human administrative layers with AI administrative layers have not reduced bureaucracy; they have made it opaque. When employees cannot correct, challenge, or even understand the automated decisions governing their work, the result is frustration, shadow systems, and doubled costs. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founding communication norms | Establish flat communication expectations from the start; prevent hierarchical information patterns from becoming embedded | +| Validation | Expert feedback loops | Build the habit of soliciting structured input from technical, domain, and governance experts before AI systems are finalised | +| Early Traction | Data democratisation foundations | Begin moving data ownership from isolated teams to shared, governed platforms; build trust infrastructure | +| Growth | Cross-functional communication at scale | Formalise direct channels between frontline, data teams, and leadership across multiple departments and locations | +| Scale | Institutional communication architecture | Embed feedback loops, bureaucracy removal, and flat communication into organisational policy and performance evaluation | + +At the idea stage, communication habits are cheap to establish and expensive to change later. A founding team that practices transparent, multi-directional communication about AI decisions from day one builds a culture that scales naturally. + +At growth and scale, the challenge is maintaining flat communication as the organisation adds layers. Every new management tier is a potential bottleneck. The conductor model becomes structural: feedback loops must be formalised, communication channels must be documented, and leaders must actively monitor whether information is flowing or pooling at bureaucratic choke points. + +--- + +## Output Template + +**Target Audience: Leadership / Operations** + +```markdown +# AI Communication Culture Assessment +## Date: [Date] +## Organisation: [Name] + +### Information Flow Map +- Layers between frontline and decision-makers: [Number] +- Average time for ground-truth observations to reach leadership: [Duration] +- Identified bottlenecks: [List with specific locations] + +### Expert Feedback System +| Expert Group | Identified Personnel | Meeting Cadence | Key Questions | Status | +|-------------|---------------------|----------------|---------------|--------| +| Data Scientists | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| Domain Experts | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| AI Project Managers | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| Governance Specialists | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | + +### Data Democratisation Status +- Current data ownership model: [Centralised/Siloed/Shared] +- Trust level between departments (1-5): [Score] +- Governance framework: [Exists/In Progress/Absent] +- Key sharing barriers: [List] + +### Feedback Loop Health +- Organisational feedback mechanisms: [List and assess effectiveness] +- Technical feedback integration: [Describe how employee feedback reaches AI improvement] +- Shadow systems detected: [Yes/No -- describe if yes] + +### Bureaucracy Assessment +- Hierarchical layers: [Number] +- Algorithmic bureaucracy indicators: [List] +- Recommended structural changes: [List] +``` + +--- + +## Related Skills + +- **[AI Inclusive Collaboration](ai-inclusive-collaboration.md)** -- Inclusion creates the demand for flat communication; communication culture provides the infrastructure through which inclusion operates. +- **[AI Purpose-Driven Questions](ai-purpose-driven-questions.md)** -- Purpose-driven questions must flow freely between leaders and technical teams; communication culture determines whether they reach the right people. +- **[AI Vision and Strategy](ai-vision-and-strategy.md)** -- Vision requires holistic communication that is authentic, empathetic, and collaborative; this skill builds the culture that makes visionary messaging credible. +- **[Radical Candor](../frameworks/radical-candor.md)** -- Scott's framework for caring personally while challenging directly maps onto the communication style prescribed for AI-era leaders. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Edmondson's work on psychological safety underpins the trust environment required for employees to share honest feedback about AI systems. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Written communication carries the flat, transparent culture across distributed teams; the four principles of leader writing apply with particular force to AI transition announcements. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-emotional-intelligence.md b/plugins/foreman/content/skills/ai-leadership/ai-emotional-intelligence.md new file mode 100644 index 0000000..93adf05 --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-emotional-intelligence.md @@ -0,0 +1,196 @@ +--- +name: "ai-emotional-intelligence" +description: "Argues that emotional intelligence becomes strategically critical precisely because of AI -- not despite it -- and provides leaders with practices for developing the soft skills that constitute the human competitive advantage in an AI-saturated economy. Covers empathy, self-awareness, communication beyond technical details, curiosity, proactive problem-solving, trust-building through vulnerability, and coaching teams in EI. Use when an AI project is failing due to poor leadership connection, when technical leaders cannot engage the workforce emotionally, when employees feel reduced to data points, when building the case for soft skills investment alongside AI investment, or when developing the human capabilities that AI cannot replicate." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - emotional-intelligence + - soft-skills + - ai-leadership + - empathy + - trust + - communication + - curiosity + - human-advantage +related_skills: + - ai-stakeholder-balance + - ai-human-centered-approach + - ai-augmentation-not-automation + - emotional-intelligence + - emotional-courage + - trust-equation + - radical-candor +author: "Fatih Guner" +--- + +# AI Emotional Intelligence + +Here is an irony that will outlast every generation of large language model, every quantum computing breakthrough, and every breathless prediction about artificial general intelligence: the smarter machines become, the more valuable human intelligence grows. Not computational intelligence -- AI has won that contest definitively. Emotional intelligence: the capacity to perceive and manage one's own emotions, to read the emotional states of others, to build trust, to communicate with empathy, to motivate through meaning rather than metrics. According to Deloitte, soft-skill-intensive occupations will grow at 2.5 times the rate of other jobs and account for two-thirds of all positions by 2030. Google's Project Oxygen -- an internal study of what makes effective managers -- found that employees valued soft skills above STEM expertise. Seven out of ten employees, per recent research, believe soft skills are more necessary than hard skills for competing in the AI era. The paradox is not subtle: the age of artificial intelligence is, in fact, the age of emotional intelligence. Leaders who fail to grasp this will deploy brilliant technology to a workforce that does not trust, follow, or forgive them. + +--- + +## The Framework + +### Why Soft Skills Became Hard Requirements + +The conventional hierarchy placed technical skills at the top and interpersonal skills somewhere below, in the category of "nice to have." AI has inverted this hierarchy with a logic that is both economically and philosophically sound. + +Technical tasks -- data processing, pattern recognition, calculation, routine analysis -- are precisely what AI does well. As these tasks migrate to machines, the work that remains for humans is the work that machines cannot do: navigating ambiguity, exercising ethical judgment, building relationships, interpreting context, motivating teams through periods of uncertainty, and creating the cultural conditions under which innovation becomes possible. Hard skills become the domain of the machine. Soft skills become the domain of the human. And the soft skills, paradoxically, become the hard requirements for organisational survival. + +This is not theory. Consider a company whose AI project kickoff went catastrophically wrong. A top executive -- chosen to lead the town hall because he was the most technically skilled among his peers -- delivered a presentation focused entirely on data architectures, market trend analysis, and growth optimisation. His tone signalled that he saw the world the way AI did: as a calculable reality. There was no mention of employees, their roles, their concerns, or their future. Workers left the meeting feeling like data points. A middle manager captured the mood: "I don't care that AI will be able to make great business recommendations and do fancy calculations. What I don't want is to be led by an AI. Can you believe this guy? I felt like I was only a data point in his eyes." + +Within a year, employees were actively avoiding or sabotaging the AI project. Their lack of trust in the leader who rolled it out meant they resisted cross-functional collaboration and knowledge-sharing. The company fell behind its competitors -- not because the technology was inferior but because the leadership lacked the emotional intelligence to deploy it. + +### The Six EI Competencies for the AI Era + +The framework identifies six specific emotional intelligence capabilities that distinguish effective AI-era leaders. These are not abstract personality traits; they are practisable skills with direct consequences for AI adoption success. + +**1. Empathy as Relationship Infrastructure** + +AI adoption is a collective endeavour. A leader who cannot build relationships across departments, between experts and non-experts, between enthusiasts and sceptics, will fail to create the collaborative conditions that AI deployment requires. A construction company leader managing an AI adoption project found herself unable to connect with her teams, unable to discern what they were struggling with, unable to build the relationships that would make the transformation possible. Two months in, she resigned. Her technical competence was not in question. Her empathic capacity was. + +The practice of empathy in the AI context has a specific dimension: employees will wonder whether they will keep their jobs, whether AI will be deployed at scale, what will happen to their roles. These concerns tempt sabotage and resistance. The empathic leader acknowledges these fears, explains consequences transparently, frames AI as augmenting rather than replacing, and opens channels for mutual exploration of solutions. + +**2. Emotional Intelligence as Self-Awareness Under Pressure** + +AI adoption generates strong emotions in leaders too -- frustration at adoption speed, anxiety about competitive position, excitement about possibilities. EI requires awareness of these emotions and their effects on decision-making. A senior manager on a conference call about an AI project communicated next steps with an intense focus on task analysis, technical architecture, and data governance. No reflection on feasibility for employees. No acknowledgment of how the team felt. Employees venting afterward described feeling unheard, unseen, and unconvinced. If the leader cannot reflect on themselves, they cannot take others' perspectives -- and if they cannot take others' perspectives, the AI project will fail. + +**3. Communication Beyond Technical Details** + +Addressing the emotional side of AI adoption requires a specific communication discipline. Leaders must prepare clear stories for each stakeholder group: what will happen, when it will happen, where in the workflow changes will occur, what implications exist for jobs and infrastructure, and why the change is necessary. The emotional dimension demands that leaders integrate their own sentiments -- acknowledging that the change is challenging, that uncertainty is real, that the organisation values its people -- alongside the strategic rationale. + +**4. Curiosity as a Strategic Competence** + +AI is different from previous disruptions because it demands leaders who recognise the limitations of established methods and actively explore alternative futures. This capacity is driven by curiosity. An operational manager, asked by data scientists about the quality of available data, dismissed the inquiry: "Why are they asking me? They are the experts. The big boss decided to bring in AI, so let's bring in AI." This leader displayed no curiosity about how AI might affect his department, what problems it might create, or what opportunities it might reveal. Had he cultivated curiosity, he would have anticipated issues, asked probing questions, and identified creative solutions before problems materialised. + +**5. Proactive Problem-Solving** + +AI systems change rapidly and unpredictably, introducing new pain points and unexpected issues. A manufacturing CTO who put together an AI adoption budget failed to account for the cost of hiring talent who could work with HR data, and the CEO's office was not equipped to maintain the data. Six months in, no monthly reviews had taken place, data breaches occurred, and worker privacy was compromised. Proactive problem-solving means anticipating the costs and challenges of AI adoption from all angles -- not just the technical ones -- and developing solutions before they become crises. + +**6. Trust Through Vulnerability** + +Trust is the foundation of collaborative relationships, and AI adoption depends on trust at every level. Building trust requires vulnerability: openly acknowledging that you are not a technical expert, that the AI project carries risks you have not fully resolved, and that you are working through challenges just as the workforce is. The sharing must be calibrated -- appropriate vulnerability means discussing your considered thoughts about consequences, not your personal anxieties about higher-level management conflicts. Authentic engagement with the AI project, demonstrated through presence on the work floor, attendance at workshops, and genuine curiosity about teams' experiences, builds the credibility that makes vulnerability effective. + +### Coaching Employees in EI: The Leader's Multiplier Role + +AI-savvy leaders recognise that their own EI is necessary but insufficient. The entire workforce needs to develop soft skills to collaborate effectively with AI. Research reveals that improved soft skills increase employee value by more than 8 percent. Yet 89 percent of organisations report difficulty finding recruits with adequate soft skills. The leader's responsibility, therefore, extends beyond personal EI development to coaching and cultivating EI across teams. + +**Be approachable and talk.** Physical presence at feedback sessions is meaningless if the leader is not perceived as genuinely open. A young manager leading an ML chatbot project remained silent during meetings, believing he was creating space for employees. They interpreted his silence as manipulation -- a tactic to lower resistance to automating their jobs. They distanced themselves and became suspicious of the entire initiative. + +**Be authentic.** The narrative that AI is here to help employees must ring true to who the leader actually is. If the leader's authentic values include elevating human performance through technology, that message lands. If it does not, employees detect the gap between rhetoric and conviction -- and trust collapses. + +--- + +## Prompts + +**Prompt 1 -- EI Diagnostic for AI Leaders:** +> Assess my emotional intelligence readiness for leading an AI adoption project. Ask me about: how I typically communicate major changes to my team, how I handle situations where employees express fear or resistance, whether I am aware of how my emotions affect my decision-making during high-pressure periods, how curious I am about the non-technical dimensions of AI deployment, and how I build trust with people who are sceptical of my initiatives. Based on my responses, identify my EI strengths and the specific competencies I need to develop before or during the AI rollout. + +**Prompt 2 -- Empathy-Driven AI Communication:** +> We are about to announce [describe AI initiative] to our workforce of [describe team]. Draft two versions of the announcement: one that a technically skilled but emotionally unintelligent leader would write (focused on capabilities, metrics, and technical architecture) and one that an emotionally intelligent leader would write (focused on people, meaning, fears, opportunities, and the human story). Highlight the specific differences and explain why the second version will produce better adoption outcomes. + +**Prompt 3 -- Soft Skills Investment Case:** +> Build a business case for investing in soft skills development alongside our AI adoption programme. The audience is a board that views soft skills as intangible and difficult to measure. Use data on the growing demand for soft-skill-intensive roles, the correlation between EI and leadership effectiveness, the evidence that AI projects fail due to human rather than technical factors, and specific examples of companies where EI deficits derailed AI adoption. Quantify the cost of not investing in EI. + +**Prompt 4 -- Team EI Development Programme:** +> Design a six-month emotional intelligence development programme for the [describe team size and function] team that will be most affected by our AI deployment. The programme should build empathy, self-awareness, communication skills, curiosity, and proactive problem-solving. Include specific exercises, feedback mechanisms, and milestones. Account for the fact that many team members may consider soft skills training less valuable than technical upskilling. + +--- + +## Use Cases + +**Early-Traction Startup Where the Technical Founder Cannot Connect** + +A technical co-founder with deep AI expertise builds a product that customers love but cannot retain engineering talent beyond 18 months. Exit interviews reveal a pattern: employees feel like "inputs to the system" rather than valued contributors. The founder's communication is exclusively technical -- sprint metrics, architecture decisions, performance dashboards. When an engineer raises concerns about burnout from AI-monitored productivity targets, the founder responds with data showing the targets are achievable. The engineer leaves. Applying the EI framework, the founder's advisor designs a structured intervention: weekly one-on-ones focused on how engineers feel rather than what they are producing, a vulnerability practice where the founder shares one uncertainty or challenge per team meeting, and a deliberate curiosity exercise where the founder asks each engineer "what would make this job more meaningful for you?" Within two quarters, the retention problem stabilises -- not because anything technical changed but because the emotional environment did. + +**Growth-Stage Company Where the AI Project Stalled** + +A 400-person professional services firm launches an AI initiative with significant investment and board support. Twelve months in, adoption is minimal: employees avoid the tools, work around the system, and describe feeling that the initiative has nothing to do with them. The diagnosis: the leaders who rolled out the project could not connect emotionally with the workforce. They mastered the technical narrative but failed to address the human dimension -- what the AI means for people's daily experience, careers, and sense of purpose. The CEO, recognising the pattern, requires all leaders involved in the AI project to attend sessions on leadership communication and emotional intelligence. A month later, the approach shifts: town halls now begin with the human story (what changes for people and why it matters) before addressing the technical story (what the AI does). The framing change is not cosmetic. It signals that the organisation's priorities have shifted from "AI first" to "people first, AI in service of people." Adoption begins to accelerate. + +**Scale-Stage Organisation Building an EI Culture for the AI Era** + +A multinational with 5,000 employees recognises that its next competitive advantage is not better AI -- every competitor has access to similar technology -- but the human capability to deploy AI in ways that create unique value. The CHRO designs an organisation-wide EI programme that pairs soft skills training with AI literacy: every employee develops both technical understanding of AI and the interpersonal skills to work effectively in human-AI teams. The programme includes empathy exercises, curiosity workshops, structured vulnerability practices for managers, and feedback circles where teams discuss not just what AI is doing but how it feels to work with it. Over two years, the company's employee engagement scores rise, AI adoption rates exceed industry benchmarks, and client satisfaction improves -- validating the thesis that in the AI era, emotional intelligence is the strategic differentiator. + +--- + +## Anti-Patterns + +1. **Treating EI as a personality trait rather than a practisable skill.** The belief that empathy, self-awareness, and communication are innate qualities rather than developable competencies leads to hiring for EI rather than building it. Neuroscience demonstrates that EI skills require continuous practice -- they atrophy without use, exactly like muscles. Malcolm Gladwell's observation applies: "Practice isn't the thing you do once you're good. It's the thing you do that makes you good." + +2. **Investing in digital upskilling at the expense of human upskilling.** The executive who dismissed soft skills as a poor investment compared to digital skills represents a common and costly error. Organisations that invest exclusively in technical training produce technically capable workers who cannot collaborate, communicate, or navigate the human dynamics of AI adoption. + +3. **Performing empathy without practising it.** Announcing that "our people are our greatest asset" while deploying AI in ways that reduce them to metrics is not a communication problem. It is an authenticity problem. Employees detect the gap between stated values and experienced reality with remarkable precision. + +4. **Assuming technical leaders automatically become AI-era leaders.** Selecting the most technically skilled person to lead AI adoption -- as opposed to the most emotionally intelligent one -- produces the pattern described above: technically brilliant presentations that leave the workforce feeling unseen, unheard, and unmotivated. + +5. **Relegating EI development to a single workshop.** EI is a continuous practice, not a training event. Organisations that run a one-day empathy workshop and check the box have not built EI capability. They have created the illusion of progress while the underlying deficit persists. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder self-awareness | At the idea stage, the founder's own EI -- or lack of it -- is the organisation's EI. Self-awareness about emotional strengths and deficits determines whether the first hires will experience a human-centred culture or a technical one. | +| Validation | Empathic user and team engagement | Validation requires deep engagement with users and early team members. The ability to understand not just what they say but what they feel -- about the product, the mission, and their role -- separates founders who build loyalty from those who build turnover. | +| Early Traction | Setting the EI standard for the culture | The first 20-50 hires inherit the emotional norms the leader establishes. A leader who models curiosity, vulnerability, and empathic communication creates a culture that scales those qualities. A leader who models purely technical communication creates one that scales emotional detachment. | +| Growth | Distributing EI across the leadership team | The founder's EI is no longer sufficient. Middle managers, department heads, and project leads must all possess and practise EI. This requires deliberate hiring for EI, structured development programmes, and accountability for emotional leadership alongside performance leadership. | +| Scale | EI as competitive moat | At scale, the organisation's collective EI -- embedded in how decisions are made, how changes are communicated, how employees experience their work -- becomes a competitive advantage that technology alone cannot replicate. Competitors can buy the same AI. They cannot buy the culture that makes it effective. | + +--- + +## Output Template + +```markdown +# AI-Era Emotional Intelligence Assessment + +## Leader EI Profile +| Competency | Current Level (1-5) | Evidence | Development Priority | +|---|---|---|---| +| Empathy | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Self-awareness | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Communication beyond technical | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Curiosity | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Proactive problem-solving | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Trust through vulnerability | [Score] | [Specific behaviours observed] | [High/Medium/Low] | + +## AI Project EI Risk Assessment +| Risk | Likelihood | Impact | Current Mitigation | Recommended Action | +|---|---|---|---|---| +| Technical leader cannot connect emotionally | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Employees feel like data points | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Curiosity deficit leads to blind spots | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Trust erosion due to perceived inauthenticity | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | + +## EI Development Plan +| Week | Practice | Competency Targeted | Success Indicator | +|---|---|---|---| +| 1-2 | [Specific exercise] | [Which competency] | [Observable change] | +| 3-4 | [Specific exercise] | [Which competency] | [Observable change] | +| 5-8 | [Specific exercise] | [Which competency] | [Observable change] | +| 9-12 | [Specific exercise] | [Which competency] | [Observable change] | + +## Team EI Baseline and Targets +- **Current team EI strengths:** [What the team does well emotionally] +- **Current team EI gaps:** [Where the team struggles] +- **12-month EI targets:** [Specific, measurable emotional competency goals] +- **Measurement method:** [How progress will be assessed] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's five-domain model provides the foundational theory of EI as a general leadership competency; this skill argues that EI becomes strategically imperative specifically because of AI. +- **[AI Stakeholder Balance](ai-stakeholder-balance.md)** -- Balancing stakeholder interests during AI adoption requires the empathy, perspective-taking, and communication skills that EI development provides. +- **[AI Human-Centered Approach](ai-human-centered-approach.md)** -- Human-centred design depends on leaders who can perceive and respond to the emotional experiences of employees interacting with AI systems. +- **[AI Augmentation Not Automation](ai-augmentation-not-automation.md)** -- The creative, judgment-based work that augmentation strategies depend on requires emotionally intelligent teams led by emotionally intelligent leaders. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- Vulnerability, one of the six EI competencies for the AI era, requires emotional courage: the willingness to be seen as uncertain while still leading with conviction. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust is the output of consistently practised EI; the trust equation provides the diagnostic for understanding which EI competencies most need development. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-human-centered-approach.md b/plugins/foreman/content/skills/ai-leadership/ai-human-centered-approach.md new file mode 100644 index 0000000..a839f25 --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-human-centered-approach.md @@ -0,0 +1,193 @@ +--- +name: "ai-human-centered-approach" +description: "Provides a comprehensive framework for deploying AI in ways that respect employee psychology, preserve human agency, and treat workforce well-being as a strategic priority rather than an afterthought. Addresses the hidden fears employees harbour about AI, the psychological damage of algorithmic supervision, and the practical steps for making human needs central to technology decisions. Use when employees resist AI adoption, when algorithmic monitoring is eroding morale, when AI-driven productivity targets create burnout, when planning an AI rollout that affects frontline workers, or when an AI project is failing and the technology is not the problem." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - human-centered-ai + - employee-experience + - change-management + - ai-adoption + - psychological-safety + - algorithmic-management + - workforce-wellbeing + - empathy +related_skills: + - ai-stakeholder-balance + - ai-augmentation-not-automation + - ai-emotional-intelligence + - emotional-intelligence + - psychological-safety + - employee-engagement-retention + - leading-through-change +author: "Fatih Guner" +--- + +# AI Human-Centered Approach + +Five fears live in every organisation contemplating AI, and not one of them is "robots will take my job." Ask employees what truly unsettles them, and the answers are more nuanced and more damning than the headlines suggest. They fear the loss of control -- that an algorithm will dictate their pace, their priorities, their breaks. They fear invisibility -- becoming a data point in a system that cannot see them as whole people. They fear the death of judgment -- that their expertise, built over years, will be overridden by a model trained on last quarter's numbers. They fear surveillance dressed as optimisation. And they fear the silence of leaders who deploy AI without ever asking how it feels on the receiving end. These fears do not appear in the ROI calculations that justify AI investment. They appear in the turnover data twelve months later. + +--- + +## The Framework + +### The Misconception: Human Users Do Not Equal Human-Centred + +An executive once insisted that his company's use of AI was human-centred. His reasoning was simple: the end users were humans, so any AI they used was, by definition, human-centred. This logic is widespread and entirely wrong. Deploying AI in a company made up of humans does not make the deployment human-centred any more than serving food in a restaurant makes it nutritious. A human-centred approach means adopting AI technologies in responsible and adaptive ways to improve people's performance, work lives, and experiences -- across dimensions that include not just efficiency but happiness, confidence, control, and a sense that what they do matters. + +### Why AI Projects Fail When Leaders Ignore the Emotional Response + +A CTO at a mid-sized company decided that the department producing reports -- marketing campaign impact, sales figures, delivery metrics -- should be supervised by an algorithm. The algorithm monitored worker pace, continuously adjusted targets based on prior performance, and flagged underperformers. The intent was more accurate reporting, delivered faster. + +The results were the opposite. Workers showed great variability in output. Reports failed to meet reliability standards. Machine supervision had backfired. Employees felt pressured to perform at peak capacity without interruption, experienced diminishing control over their tasks, and described feeling "treated like robots." Absenteeism rose. Turnover increased. Mental fatigue became pervasive. + +The diagnosis was not technical. People have good days and bad days. That variability is not a defect to be optimised away -- it is a feature of human cognition that enables creativity, reflection, and learning. An organisation's tolerance for variability signals to its people that it understands they are human. An algorithm that demands relentless consistency signals the opposite. + +### The Five Dimensions of Human-Centred AI + +A genuinely human-centred approach to AI deployment addresses five dimensions, each of which requires deliberate leadership action rather than passive assumption. + +**1. Efficiency With Respect** + +Efficiency remains a valid objective, but it cannot be the only one. When the sole metric is output per unit of time, AI becomes a mechanism for extracting maximum labour -- precisely the dynamic that industrial-era management reforms spent a century trying to dismantle. A human-centred approach pursues efficiency gains while respecting the cognitive and emotional limits of the people producing the output. The algorithm that adjusted for human behavioural variability -- accounting for individual working styles, life events, and the need for reflective pauses -- ultimately produced faster, more reliable results than the version that treated workers as uniform inputs. + +**2. Meaningful Work, Not Just Productive Work** + +Humans are not perfectly rational actors motivated solely by productivity. They derive satisfaction from competence, inclusion, respect, moral purpose, and curiosity. An AI deployment that maximises throughput while stripping work of meaning will produce resistance, disengagement, and attrition that no efficiency gain can offset. The human desire for meaningful work is not sentimentality. It is an empirical reality with direct consequences for performance. + +**3. Transparency and Governance** + +Employees need to know what data is being collected, how it is used, and who has access. An HR department at a Southeast Asian multinational was discovered referring to employees by staff numbers in internal communications, describing a worker as "XX13baXX" and categorising them as "high-risk elements" for the upcoming change project. When this email reached the wrong recipient and circulated among employees, the resulting outrage forced a formal apology. Transparency is not merely a regulatory requirement. It is the minimum condition for trust. + +**4. Human Control Over AI Interactions** + +If AI is presented as a tool for empowerment, employees must actually experience empowerment -- including the authority to question algorithmic recommendations, provide feedback on AI-driven targets, and withdraw from interactions they find counterproductive. A taxi company that introduced algorithmic dispatch found its drivers feeling dehumanised: they lost control over their routes, believed they were being excessively monitored, and felt prevented from exercising their own judgment about customer service. Regular feedback sessions and the discretion to override algorithmic suggestions restored both driver satisfaction and, ultimately, the algorithm's effectiveness. + +**5. Well-Being as a Metric, Not an Afterthought** + +Human-centred AI adoption requires treating employee well-being as an explicit design objective. This means collaborating with HR and technology teams before deployment to assess whether the AI system enhances or erodes self-confidence, adheres to ethical norms, and promotes rather than diminishes employee satisfaction. NASA and the US Department of Defense use technology-readiness scales to evaluate new systems; organisations deploying AI should develop analogous human-readiness scales that assess the impact on the people who will use the technology. + +### The Reflective Procrastination Principle + +The framework introduces a counterintuitive concept: reflective procrastination. Conventional management treats any pause in productivity as waste. But research demonstrates that taking longer breaks -- delaying work not from laziness but from the need to consider different perspectives -- produces better results through more divergent thinking and creativity. Sometimes slowing down the pace of work yields higher-quality output than algorithmic optimisation of speed. The implication for AI-driven work design is profound: systems that allow human-determined pacing outperform systems that impose algorithmic pacing, because they work with human cognition rather than against it. + +--- + +## Prompts + +**Prompt 1 -- Hidden Fear Inventory:** +> We are deploying AI in [describe context -- e.g., customer support, warehouse operations, financial analysis]. Interview simulation: ask me the questions an employee in each affected role would need answered before they could trust this deployment. Focus not on whether they will lose their job but on the five hidden fears: loss of control, invisibility, death of judgment, surveillance, and leadership silence. For each fear, suggest specific actions the leadership team should take. + +**Prompt 2 -- Human-Readiness Assessment:** +> Before we deploy [describe AI system], conduct a human-readiness assessment. Evaluate whether the system: preserves employee agency, accounts for human variability in performance, maintains transparency about data collection and use, includes mechanisms for employee feedback and override, and enhances rather than diminishes the meaningfulness of work. Identify gaps and recommend specific design changes. + +**Prompt 3 -- AI-Driven Work Redesign:** +> We have deployed an AI system that [describe what it does]. Employee feedback indicates [describe symptoms -- e.g., reduced morale, increased errors, higher absenteeism]. Diagnose the likely human-centred failures in the deployment. Propose a redesigned approach that achieves the same business objectives while respecting employee psychology, drawing on principles of human variability, reflective procrastination, and meaningful work. + +**Prompt 4 -- Communication Plan for AI Deployment:** +> Design a communication plan for our upcoming AI deployment that addresses employees as whole people, not as production inputs. The plan should: explain what the AI will do and why, explicitly state what it will not do, acknowledge the emotional impact of the change, provide channels for ongoing feedback, and include specific commitments about human oversight. Avoid the trap of leading with technical capabilities -- lead with the human story. + +--- + +## Use Cases + +**Validation-Stage SaaS Startup Introducing AI-Assisted Code Review** + +A 15-person SaaS startup introduces an AI tool that reviews code before human review, flagging potential issues and suggesting improvements. The founders expect developers to welcome the efficiency gain. Instead, senior developers feel their expertise is being questioned -- the tool occasionally flags their deliberate architectural choices as "issues." Junior developers become overly deferential to the AI's suggestions, accepting recommendations without critical evaluation. The CTO, recognising the pattern of eroded judgment and undermined expertise, redesigns the workflow: the AI provides suggestions as one input among several, developers are explicitly encouraged to override the tool when their judgment differs, and the team tracks cases where human judgment proved superior to AI recommendation. Within three months, the tool is used actively rather than resented -- because the developers control it rather than the reverse. + +**Growth-Stage Logistics Company Deploying Route Optimisation** + +A 150-person logistics company deploys AI-driven route optimisation for its delivery fleet. Drivers are told the AI will make them more efficient. What they experience is micromanagement: prescribed routes that ignore local knowledge, break schedules determined by an algorithm rather than by fatigue, and performance metrics that penalise any deviation from the optimal path. Driver turnover increases from 12 percent to 28 percent in six months. The operations director applies the human-centred framework by introducing three changes: drivers can override routes when local conditions warrant it, break timing is driver-determined within broad parameters, and a monthly "local knowledge" session allows drivers to feed experiential insights back into the routing model. Turnover returns to baseline. Route efficiency improves beyond the original AI-only benchmark, because the system now benefits from human contextual knowledge that the algorithm lacked. + +**Scale-Stage Manufacturing Firm Redesigning Shop Floor AI** + +A manufacturing company with 2,000 employees deploys AI across its shop floor to monitor equipment performance and worker productivity. The productivity monitoring component draws immediate resistance: workers describe feeling watched, judged, and reduced to numbers. A joint task force of floor supervisors, HR, and the AI team redesigns the system. Equipment monitoring remains fully automated. Productivity data is aggregated at the team level rather than the individual level, visible to teams as a coaching tool rather than a surveillance mechanism. Workers receive quarterly reports showing how AI-driven insights have improved safety outcomes -- giving the workforce a tangible, human-centred benefit from the technology. Resistance subsides not because the AI changed but because its relationship to the workforce changed. + +--- + +## Anti-Patterns + +1. **Leading with the technology instead of the human story.** Presenting AI deployment as a technical achievement -- data architectures, algorithm specifications, processing speeds -- signals to employees that the leader sees the world the way AI does: in ones and zeros. A middle manager at one company captured the sentiment: "I felt like I was only a data point in his eyes." The human story must come first, the technical story second. + +2. **Confusing employee silence with employee acceptance.** Employees who do not complain about AI are not necessarily comfortable with it. They may have concluded that resistance is futile, that the decision has already been made, or that raising concerns will mark them as obstacles. Active inquiry -- structured feedback sessions, anonymous surveys, skip-level conversations -- is the only reliable signal of true acceptance. + +3. **Optimising for consistency when variability is a feature.** Algorithms naturally seek to eliminate variability. Human performance variability is not noise to be filtered out; it is the mechanism through which creativity, adaptation, and learning occur. AI systems that demand robotic consistency from human workers will produce exactly the disengagement and poor performance they were designed to prevent. + +4. **Treating human-centred AI as a one-time design decision.** A system that is human-centred at deployment can become dehumanising as it evolves, as targets are adjusted upward, as oversight mechanisms atrophy, or as new management interprets the tool differently. Human-centredness requires ongoing governance, not a single design review. + +5. **Deploying AI to solve a leadership problem.** When morale is low, productivity is inconsistent, or quality is declining, the root cause is often leadership -- not a technology gap. Deploying AI to "fix" problems that originate in poor management produces a specific pathology: the technology amplifies the dysfunction while giving the leader a veneer of data-driven objectivity. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Defining the human-AI relationship | Before any technology decision, the founder must articulate a clear philosophy: is AI here to replace human capability or to enhance it? This philosophical choice shapes every subsequent design and deployment decision. | +| Validation | Testing with real humans, not just data | Prototyping must include testing the human experience of interacting with the AI, not just the accuracy of the AI's output. User testing should measure trust, control, and emotional response alongside technical metrics. | +| Early Traction | Establishing feedback loops | The first operational deployment is when real human-centred challenges emerge. Formal feedback mechanisms -- weekly check-ins, anonymous channels, override tracking -- must be established from day one and treated as signals, not noise. | +| Growth | Scaling human-centredness alongside AI | Growth creates pressure to standardise, and standardisation is the enemy of human-centred design. The challenge is maintaining individual adaptation, feedback responsiveness, and human override authority as the system scales. | +| Scale | Institutionalising human-centred governance | At scale, human-centredness can no longer depend on individual leaders. It must be embedded in governance structures: ethics boards, employee representation in AI design decisions, mandatory human-readiness assessments for new deployments, and regular audits of existing systems. | + +--- + +## Output Template + +```markdown +# Human-Centred AI Deployment Plan + +## System Overview +- **AI application:** [What the system does] +- **Affected workforce:** [Roles and number of people] +- **Business objective:** [What the AI is meant to achieve] + +## Human-Readiness Assessment +| Dimension | Current State | Risk Level | Required Action | +|---|---|---|---| +| Employee agency | [How much control do employees retain?] | [High/Medium/Low] | [Specific action] | +| Human variability | [Does the system accommodate good days and bad days?] | [High/Medium/Low] | [Specific action] | +| Transparency | [Do employees know what data is collected and how it is used?] | [High/Medium/Low] | [Specific action] | +| Override authority | [Can employees question or override AI recommendations?] | [High/Medium/Low] | [Specific action] | +| Meaningful work | [Does the AI enhance or diminish the meaning of the work?] | [High/Medium/Low] | [Specific action] | + +## Fear Mitigation Plan +| Hidden Fear | How This Deployment Triggers It | Specific Mitigation | +|---|---|---| +| Loss of control | [Describe] | [Action] | +| Invisibility | [Describe] | [Action] | +| Death of judgment | [Describe] | [Action] | +| Surveillance | [Describe] | [Action] | +| Leadership silence | [Describe] | [Action] | + +## Feedback Architecture +- **Frequency:** [How often feedback is collected] +- **Channels:** [Anonymous surveys, team sessions, one-on-ones, override logs] +- **Escalation path:** [What happens when feedback reveals a problem] +- **Commitment:** [How the organisation will respond to feedback] + +## Success Metrics (Human and Business) +| Metric | Target | Measurement Method | +|---|---|---| +| [Business metric -- e.g., throughput] | [Target] | [How measured] | +| [Human metric -- e.g., employee satisfaction] | [Target] | [How measured] | +| [Human metric -- e.g., turnover rate] | [Target] | [How measured] | +| [Human metric -- e.g., override frequency] | [Target] | [How measured] | +``` + +--- + +## Related Skills + +- **[AI Stakeholder Balance](ai-stakeholder-balance.md)** -- The human-centred approach operationalises stakeholder balance at the employee level, translating broad ethical principles into specific workforce practices. +- **[AI Augmentation Not Automation](ai-augmentation-not-automation.md)** -- Augmentation is the natural extension of human-centred design: AI that enhances human capability rather than supplanting it. +- **[AI Emotional Intelligence](ai-emotional-intelligence.md)** -- Leading a human-centred AI deployment requires the emotional intelligence to perceive and respond to employee fears that are rarely articulated directly. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Employees who do not feel psychologically safe will not provide honest feedback about their AI experience, rendering the entire feedback architecture useless. +- **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- The human-centred approach is, at its core, an engagement and retention strategy specific to the AI context. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- General change leadership provides the foundation; this skill adapts those principles to the specific psychological dynamics of AI-driven transformation. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-inclusive-collaboration.md b/plugins/foreman/content/skills/ai-leadership/ai-inclusive-collaboration.md new file mode 100644 index 0000000..5d41ef3 --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-inclusive-collaboration.md @@ -0,0 +1,205 @@ +--- +name: "ai-inclusive-collaboration" +description: "Provides a comprehensive framework for designing inclusive human-AI collaboration that keeps all stakeholders at the design table. Addresses exclusion dynamics, algorithm aversion, trust deficits, silo formation, and the human cost of automation-first strategies. Use when employees resist AI adoption, when AI design excludes non-technical voices, when human-AI collaboration feels extractive rather than empowering, when organisational silos hinder AI scaling, or when leaders need to reward human contributions in AI-augmented work." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - human-ai-collaboration + - inclusion + - employee-engagement + - algorithm-aversion + - ai-trust + - participatory-design + - organisational-silos +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-communication-culture + - ai-vision-and-strategy + - inclusive-leadership + - psychological-safety + - ai-era-leadership +author: "Fatih Guner" +--- + +# AI Inclusive Collaboration + +Amazon warehouse workers, supervised by algorithms that tracked their every movement, eventually gathered outside their facilities with a rallying cry: "We are not robots." One employee distilled the grievance: "[Productivity] is all they care about. They don't care about their employees. They care more about the robots than they care about the employees." This was not a failure of technology. The algorithms performed precisely as designed. It was a failure of inclusion -- a leadership decision to optimise for efficiency while treating human workers as interchangeable with the machines monitoring them. The third pillar of AI-savvy leadership confronts this dynamic directly: when people are excluded from the design and deployment of AI systems, they resist, retreat, or revolt. The question every leader must answer is not whether their people can work with AI, but whether the people who will be most affected by AI were present when the system was designed. + +--- + +## The Framework + +### The Exclusion-Inclusion Spectrum + +The framework identifies two fundamentally different models for integrating AI into organisations: + +**The Exclusion Model** aims to minimise humans in the technical loop. Business operations and strategy are driven by a loop of computers where humans do not fit. Under this model, employees are valued solely for efficiency, pushed into rigid work structures supervised by AI, and stripped of autonomy. The consequences are predictable: demotivation, declining quality of human input, and counterproductive behaviour (Uber drivers, for instance, developed clever methods to manipulate algorithms that supervised them). + +**The Inclusion Model** positions AI as a collaborator that assists in cognitively demanding tasks, leveraging AI's analytical strengths while preserving and valuing distinctly human capabilities -- moral reasoning, contextual judgement, empathy, and creative sense-making. Under this model, employees are involved in designing the work settings in which humans and machines collaborate. + +The distinction between these models is the defining leadership choice of the AI era. + +### Three Benefits of Inclusive AI Adoption + +The research identifies three specific outcomes that inclusive approaches produce: + +**1. Feeling of Control** + +When employees participate in AI design and deployment decisions, they perceive the technology as a tool that works for them rather than a control mechanism imposed upon them. A bank employee who was told by an algorithm that a well-qualified applicant did not qualify for a credit card -- and could offer no explanation -- exemplifies the opposite: a human stripped of agency, unable to exercise the judgement that defines professional competence. + +**2. Reduced Algorithm Aversion** + +Research shows that humans prefer to work with and receive advice from other humans, even when AI demonstrably outperforms human alternatives. This aversion is not rational; it is emotional. People feel uncomfortable with entities that show little similarity to themselves. Inclusive leaders address this by positioning themselves as mediators and facilitators in human-AI interactions, ensuring employees receive training to interact effectively with AI systems while maintaining access to human support when interactions go wrong. + +**3. Increased Trust** + +Nearly half of all employees globally do not trust AI at work. Trust cannot be manufactured through technical improvements alone -- better accuracy, better explainability. Trust requires that employees believe their leaders are competent, honest, and benevolent in their AI decisions. Inclusion builds this trust by giving employees visibility into how AI works, what it can and cannot do, and why it has been deployed. + +### Four Steps to Inclusive AI Adoption + +The framework prescribes four concrete actions: + +**Step 1 -- Create Space for Social Connection** + +People who work extensively with AI experience loneliness and isolation. Digital life underwriters who assess insurance applications through AI-based systems never meet the applicants; they interact only with data. Leaders must counterbalance this by creating deliberate opportunities for human-to-human interaction -- social events, cross-team meetings, scheduled time away from screens. + +**Step 2 -- Make Tech and Non-Tech Teams Work Side by Side** + +Cross-discipline collaboration is the foundation of successful human-AI partnerships. Tech and business experts cannot retreat to separate spaces. Business experts explain organisational requirements; tech experts suggest appropriate AI approaches; HR familiarises everyone with the skills needed; operational staff integrate the human-AI workflow. The leader's role is to be an "analytics-to-business translator" -- someone who bridges jargon gaps and decomposes large problems into actionable components. + +The cost of failure is illustrated by the case of a CEO at a global financial institution who interrupted his CTO's technology strategy presentation, demanding it be reduced to "three simple bullet points." The tech group pulled back from communicating with senior leadership entirely. The CEO's inability to translate between technical and business perspectives doomed the AI project within a year. + +**Step 3 -- Develop Leadership and Inclusion Skills** + +AI-savvy leaders must be perceived as someone who listens, who accounts for the uncertainties and discomfort employees feel, and who demonstrates humility about their own knowledge gaps. Research shows that employees are more willing to trust AI and engage with it when their leaders are seen as humble people willing to listen. Satya Nadella's practice of telling Microsoft employees that he, too, has knowledge gaps models the behaviour that makes inclusion possible. + +**Step 4 -- Reward Workers for Being Human** + +When AI and humans collaborate, clear guidelines must establish who -- or what -- receives credit. The 2022 Colorado State Fair art competition became a flashpoint when a human artist won using a generative AI tool. Critics dismissed his contribution as "pressing a few buttons." In reality, substantial human judgement, iterative prompting, and creative selection underpinned the work. Leaders must ensure employees share in the rewards created by human-AI collaboration, and that human contributions are recognised rather than diminished. + +### The Silo Problem + +AI adoption deepens organisational silos in three ways: + +1. **Technical expertise concentration** -- only tech teams understand the AI systems, creating barriers for HR, operations, and marketing. +2. **Data ownership conflicts** -- different departments maintain separate data repositories and resist sharing. +3. **Uneven AI impact** -- some teams benefit from AI while others feel threatened, producing siloed behaviour where information is hoarded for self-protection. + +When departments operate in isolation, data becomes fragmented, cross-functional problem-solving vanishes, and the organisation loses its ability to scale AI effectively. + +--- + +## Prompts + +**Prompt 1 -- Inclusion Audit:** +> "Conduct an inclusion audit of our AI adoption process. Our organisation [describe size, industry, AI maturity]. The AI systems we have deployed or are deploying include [describe]. For each system, assess: (1) Which stakeholders were present when the system was designed? (2) Which stakeholders were absent? (3) What are the likely consequences of their absence? (4) What specific steps can we take to bring excluded voices to the table, using the four-step inclusion framework?" + +**Prompt 2 -- Algorithm Aversion Mitigation:** +> "Our employees are resisting a new AI system [describe system and context]. Resistance manifests as [describe behaviours -- avoidance, workarounds, open complaints]. Using the framework on algorithm aversion and inclusion, help me diagnose the root cause and design an intervention that includes: (1) repositioning my role as mediator between employees and AI, (2) training that addresses emotional rather than just technical concerns, (3) mechanisms for employees to speak to a human when AI interactions go wrong, and (4) a timeline for building trust incrementally." + +**Prompt 3 -- Cross-Functional AI Team Design:** +> "Design an inclusive, cross-functional team structure for our AI initiative [describe project]. The team must include tech experts, domain experts, HR, and operational staff. For each role, specify: (1) what they contribute, (2) what questions they should be empowered to ask, (3) how to prevent tech experts from dominating discussions, and (4) how I as leader serve as the analytics-to-business translator that the framework describes." + +**Prompt 4 -- Human Reward Framework for AI Collaboration:** +> "Our organisation is deploying AI in [describe context] where humans and AI will produce outputs collaboratively. Help me design a reward and recognition framework that: (1) clearly attributes human contributions to AI-augmented work, (2) prevents the devaluation of human input, (3) establishes guidelines for crediting collaborative outputs, and (4) communicates to employees that their uniquely human capabilities -- judgement, creativity, empathy -- are valued more, not less, as AI becomes prevalent." + +--- + +## Use Cases + +**Early-Traction Customer Service Platform Automating the Wrong Tasks** + +A startup building an AI-powered customer service platform automates all routine queries, leaving human agents to handle only the most difficult and emotionally charged interactions -- complaints escalated because the AI failed. Agents report burnout, anxiety, and declining job satisfaction. Turnover reaches 40 percent. Applying the inclusion framework, the startup redesigns its human-AI allocation. Rather than giving humans only what AI cannot handle, the system routes a balanced mix of interactions to human agents, including straightforward ones that provide psychological relief between difficult cases. Agents are included in redesigning the routing logic, contributing domain knowledge about which interactions benefit most from human empathy. Within six months, turnover drops to 15 percent and customer satisfaction improves -- not because the AI got better, but because the humans were finally included in the design. + +**Growth-Stage Manufacturing Firm Where Silos Block AI Scaling** + +A manufacturing company successfully deploys AI in quality control at one plant. Attempts to scale the system across four additional plants fail because each plant maintains its own data repositories, uses different data formats, and resists sharing information with central IT. The pattern matches the silo diagnosis precisely. The COO establishes cross-plant AI working groups that include plant managers, quality engineers, IT staff, and frontline workers from each facility. She centralises data storage in a cloud-based platform with shared access while appointing data governance liaisons at each plant -- people who own the local relationship with both the data and the colleagues who generate it. Critically, she rewards the plants not for individual AI performance metrics but for contributions to the shared AI capability across the organisation. + +--- + +## Anti-Patterns + +**Deploying AI and announcing it after the fact.** Presenting employees with a finished AI system and expecting adoption is the fastest route to resistance. Inclusion means involvement from the design stage, not notification after deployment. + +**Automating the easy work and leaving humans the hard parts.** When AI handles routine tasks and humans receive only the difficult, ambiguous, or emotionally draining cases, the result is not efficiency. It is a recipe for burnout, resentment, and attrition. This pattern is documented in call centres where AI handles simple queries, leaving human workers to absorb the full emotional weight of dissatisfied customers. + +**Assuming better AI accuracy will solve the trust problem.** Technical teams often respond to employee distrust by improving model performance. Research shows that trust in AI continues to decline even as accuracy improves. Trust is a leadership and inclusion problem, not a technical one. + +**Letting IT supervise human-AI collaboration instead of HR.** When the integration of humans and AI is managed by IT departments rather than human resources, the implicit message is that employees and AI are interchangeable commodities. This structural choice is a signal of exclusion that employees read clearly. + +**Ignoring the loneliness tax.** AI adoption increases the time employees spend interacting with screens and decreases the time they spend with other humans. Leaders who do not deliberately create space for social connection will lose engagement, creativity, and institutional knowledge to isolation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Inclusive founding principles | Establish from day one that all stakeholders will participate in AI design decisions; build inclusion into the company's DNA | +| Validation | Participatory prototyping | Include target users and affected employees in AI system design before the technology is finalised | +| Early Traction | Cross-functional team formation | Build diverse teams that combine technical, domain, and operational expertise; prevent tech-only AI development | +| Growth | Silo prevention at scale | As AI spreads across departments, actively break down data silos and ensure cross-functional collaboration persists | +| Scale | Institutional inclusion architecture | Formalise inclusion practices -- reward frameworks, social connection infrastructure, human-AI collaboration guidelines -- into organisational policy | + +At idea and validation stages, the cost of inclusion is low and the return is high. Including diverse perspectives in AI design at this point prevents costly redesigns later. A startup that includes frontline users in its AI design process from the beginning builds a product that works with human workflows rather than against them. + +At growth and scale, inclusion becomes a governance challenge. The four-step framework must be institutionalised: social connection time built into schedules, cross-functional teams embedded in standard operating procedures, leadership humility modelled from the top, and human contribution recognised in performance and reward systems. + +--- + +## Output Template + +**Target Audience: Team / Leadership** + +```markdown +# Human-AI Collaboration Inclusion Assessment +## Date: [Date] +## AI System/Initiative: [Name] + +### Stakeholder Presence Audit +| Stakeholder Group | Present at Design | Present at Deployment | Impact Level | Inclusion Gap | +|-------------------|------------------|-----------------------|-------------|---------------| +| [Group] | [Yes/No] | [Yes/No] | [High/Med/Low] | [Describe] | + +### Inclusion Model Assessment +- Current model: [Exclusion / Partial Inclusion / Full Inclusion] +- Evidence: [Specific indicators] +- Target model: [Describe desired state] + +### Four-Step Inclusion Plan +| Step | Current State | Target State | Actions Required | +|------|--------------|-------------|-----------------| +| Social connection | [Assess] | [Goal] | [Specific actions] | +| Cross-functional teams | [Assess] | [Goal] | [Specific actions] | +| Leadership inclusion skills | [Assess] | [Goal] | [Specific actions] | +| Human reward recognition | [Assess] | [Goal] | [Specific actions] | + +### Silo Risk Assessment +- Data sharing barriers: [List] +- Cross-functional collaboration gaps: [List] +- Recommended structural changes: [List] + +### Trust Indicators to Monitor +- Employee AI trust score (baseline): [Measure] +- Algorithm aversion incidents: [Track] +- Voluntary AI adoption rate: [Measure] +``` + +--- + +## Related Skills + +- **[AI Communication Culture](ai-communication-culture.md)** -- Flat communication structures are the prerequisite for inclusive AI collaboration; without information flowing freely, inclusion remains performative. +- **[AI Learning for Leaders](ai-learning-for-leaders.md)** -- Leaders who understand AI can serve as the analytics-to-business translators that inclusive collaboration demands. +- **[AI Purpose-Driven Questions](ai-purpose-driven-questions.md)** -- Inclusive collaboration ensures that purpose-driven questions reflect diverse stakeholder perspectives, not just leadership assumptions. +- **[Inclusive Leadership](../leadership/inclusive-leadership.md)** -- Covers daily DEI practices broadly; this skill focuses specifically on inclusion in human-AI collaboration design. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Edmondson's framework underpins the trust environment required for employees to voice concerns about AI without fear. +- **[Hackman's Enabling Conditions](../frameworks/hackman-enabling-conditions.md)** -- The structural conditions for team effectiveness apply with particular force to hybrid human-AI teams where role clarity and adequate resources determine collaborative success. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-learning-for-leaders.md b/plugins/foreman/content/skills/ai-leadership/ai-learning-for-leaders.md new file mode 100644 index 0000000..8d2155f --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-learning-for-leaders.md @@ -0,0 +1,198 @@ +--- +name: "ai-learning-for-leaders" +description: "Guides non-technical leaders through building AI savviness without becoming AI experts, closing the gap between AI understanding and AI deployment. Applies the 'just savvy enough' principle and lifelong AI learning framework. Use when a leader feels inadequate about AI knowledge, defers too heavily to technologists, needs to build a business case for AI, wants to lead AI adoption without a technical background, or seeks to distinguish AI-knowledgeable from AI-savvy leadership." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-literacy + - leadership-development + - digital-transformation + - ai-adoption + - lifelong-learning + - confidence-gap +related_skills: + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-communication-culture + - ai-vision-and-strategy + - learning-agility + - ai-era-leadership + - growth-mindset +author: "Fatih Guner" +--- + +# AI Learning for Leaders + +Between what leaders know about AI and what they actually do with it lies a gap that widens by the quarter. Research conducted in Singapore -- a country ranked fourth globally in digital competitiveness -- found that two-thirds of managers considered their organisations ineffective at using AI systems they had already purchased. The technology was not the problem. The leaders were. They had disengaged from AI adoption projects, paralysed by a sense of inadequacy, and handed the keys to technologists who understood algorithms but not the business. This is the confidence problem: the more leaders learn about AI, the more they become aware of what they do not know, and the less inclined they are to lead. The antidote is not expertise. It is savviness -- knowing just enough to ask the right questions, make sound decisions, and refuse to be sidelined by jargon. + +--- + +## The Framework + +### The Gap: Understanding vs. Deployment + +The framework identifies a structural tension at the heart of AI-era leadership. AI technology evolves at a pace that outstrips any individual's ability to master it, yet organisations expect their leaders to be proactive in its use and governance. This creates what he terms the **AI knowledge-usage gap**: leaders fall further behind in understanding even as deployment accelerates around them. + +The gap produces a predictable leadership failure mode: + +1. **Enthusiasm** -- Leaders hear about AI's transformative potential and invest heavily in infrastructure, talent, and tooling. +2. **Inadequacy** -- Once engagement begins, leaders discover they cannot speak the language of data scientists or evaluate technical trade-offs. Doubt sets in. +3. **Deference** -- Leaders quietly withdraw from AI decision-making, ceding authority to technologists who lack business context. +4. **Failure** -- Without leadership connecting AI to organisational purpose, employees see no reason to adopt the tools. The investment stalls. Boards pull the plug. + +Research across dozens of organisations reveals that 87 percent of digital transformation projects fail -- not because the technology underperforms, but because leadership is absent from the process. + +### The "Just Savvy Enough" Principle + +The central insight of this framework is liberating: **business leaders do not need to become AI experts.** They need to become AI-savvy -- possessing enough foundational understanding to recognise AI's potential, articulate its business value, and maintain oversight without deferring to technologists by default. + +AI savviness operates at two levels: + +**Level 1 -- What AI Is and Is Not** + +Leaders must understand that AI systems are computational tools with self-learning abilities. They can analyse vast datasets, identify patterns, and make predictions. They cannot infer meaning, exercise moral reasoning, appreciate cultural nuance, or replace human judgement in ambiguous situations. AI is, in essence, "a really good calculator that works faster and can work with more data than humans can." Grasping this distinction prevents two common errors: overestimating AI's capability (leading to reckless delegation) and underestimating its utility (leading to avoidance). + +**Level 2 -- What Kind of AI Fits the Business Context** + +Leaders should understand which AI techniques serve which business purposes. Machine learning models trained on supervised data suit prediction tasks where human control matters. Reinforcement learning with human feedback enables iterative improvement. Leaders need not build these systems, but they must know enough to ask whether the chosen approach allows for the human oversight their organisation requires. + +### From Knowledge to Lifelong Learning + +Knowing AI basics is necessary but insufficient. The framework emphasises that AI savviness is not a one-time achievement. It is a continuous practice. The field evolves constantly -- new techniques, new applications, new ethical considerations. Leaders who treat AI education as a checkbox will find their knowledge obsolete within months. + +Effective lifelong AI learning includes: + +- **Daily reading** -- at least one hour, split between AI developments and leadership practice. One executive profiled in the research reads for an hour every day without exception, treating it as non-negotiable. +- **Periodic check-ins with technical teams** -- not to audit their work, but to understand what they are building and why. +- **Peer discussions** -- conversations with other leaders navigating similar challenges. +- **Ethical education** -- staying current on AI bias, fairness, and regulatory developments. Sam Altman's public acknowledgement that ChatGPT carries societal dangers illustrates why this dimension cannot be ignored. +- **Leading by example** -- using AI tools personally and visibly, signalling to the organisation that leaders are not above the technology they promote. + +### The Satya Nadella Model + +The framework holds up Microsoft CEO Satya Nadella as the exemplar of AI-savvy leadership. Nadella credits Microsoft's AI success not to having the best technology but to leadership setting the tone -- promoting a growth mindset, demonstrating humility, and modelling openness to new ways of working. His approach proves that savviness is a leadership posture, not a technical credential. + +--- + +## Prompts + +**Prompt 1 -- AI Savviness Self-Assessment:** +> "Assess my current AI savviness as a business leader. I lead [describe organisation/team] in [industry]. My current AI knowledge includes [describe what you know]. My organisation's AI maturity is [describe]. Using the two-level framework (understanding what AI is/is not, and understanding which AI fits my business context), identify my specific knowledge gaps and create a 90-day learning plan that makes me 'just savvy enough' to lead AI adoption without becoming a technologist." + +**Prompt 2 -- Business Case for AI Adoption:** +> "Help me build a business case for AI adoption in [specific business function]. I need to articulate: (1) which specific problems AI will solve (not which tools we should buy), (2) what kind of AI technique is appropriate and why, (3) where human oversight remains essential, (4) what the realistic timeline and expectations should be (avoiding the trap of projecting immediate ROI), and (5) how I will personally stay engaged rather than delegating to the tech team." + +**Prompt 3 -- Closing the Confidence Gap:** +> "I am a non-technical leader who feels increasingly sidelined in AI discussions at [describe organisation]. When technologists present, I defer rather than challenge. Help me design a confidence-building strategy that includes: key AI concepts I must understand to hold intelligent conversations, questions I should ask in every AI project review, red flags that indicate I am being excluded from decisions I should own, and a script for re-establishing my leadership authority over AI initiatives without pretending to technical expertise I lack." + +**Prompt 4 -- Lifelong AI Learning Architecture:** +> "Design a sustainable AI learning practice for me as a [role] in [industry]. The practice must fit into my existing schedule, cover both AI fundamentals and leadership implications, include peer learning and technical team engagement, and produce measurable improvement in my ability to guide AI-related decisions. Include specific resources, cadences, and accountability mechanisms." + +--- + +## Use Cases + +**Validation-Stage Healthtech Founder Who Over-Delegates to a CTO** + +A non-technical founder building an AI-powered diagnostic tool discovers that every product decision has been made by the CTO without business input. The founder cannot evaluate whether the chosen machine learning approach is appropriate, cannot explain the product's AI capabilities to investors, and has lost credibility with the board. Applying the framework, the founder does not enrol in a computer science course. Instead, she dedicates two weeks to understanding supervised learning at a conceptual level, learns enough statistical vocabulary to discuss model accuracy with her CTO, and establishes a weekly meeting where the CTO must translate technical decisions into business implications. Within a month, she catches a critical misalignment: the model optimises for diagnostic speed rather than accuracy, which contradicts the company's value proposition to cautious hospital clients. + +**Growth-Stage Retail Company Where Leaders Abandoned AI Post-Launch** + +A retail company invested heavily in an AI-based recommendation engine. Initial enthusiasm faded when leaders realised they did not understand the system's outputs. They retreated to traditional methods while the AI platform gathered dust. Employees, observing their leaders' disengagement, saw no reason to adopt the tool themselves. The "If they don't, why should I?" dynamic took hold. A new COO, guided by the lifelong learning principle, spends her first month using the recommendation engine daily, sharing what she learns in team meetings, and asking frontline staff what the system gets right and wrong. She does not pretend to understand the underlying algorithms. She demonstrates curiosity and ownership. Within six months, platform usage triples. + +**Scale-Stage Financial Services Firm Building Institutional AI Learning** + +A multinational bank has deployed AI across credit scoring, fraud detection, and customer segmentation. Individual leaders have varying levels of AI literacy -- some are deeply engaged, others are entirely dependent on their technology officers. The CEO recognises that the organisation's AI capability depends on whoever happens to occupy leadership roles, which is unsustainable. Applying the institutional learning framework, the bank creates a three-tier programme: in-house workshops led by data science teams (translating technical work into business language), an external executive education partnership with a business school for advanced AI leadership modules, and a peer learning circle where senior leaders share AI decision-making experiences monthly. The programme is not optional. It is embedded in the leadership development pipeline alongside financial acumen and people management. Two years later, leadership transitions no longer disrupt AI initiatives because incoming leaders arrive with baseline savviness. + +--- + +## Anti-Patterns + +**Enrolling in a coding bootcamp.** The instinct to become technically proficient is understandable but misguided. Leaders who spend months learning Python emerge with just enough knowledge to be dangerous -- capable of questioning technical details while losing sight of strategic leadership. AI savviness is about judgement, not code. + +**Treating AI education as a one-time event.** Leaders who attend a single AI workshop and consider themselves prepared will find their knowledge obsolete before the next quarter. The framework demands continuous learning, not episodic exposure. + +**Deferring to technologists on business questions.** The most corrosive anti-pattern occurs when leaders let data scientists define the organisation's AI strategy. Technologists are trained to optimise models, not to articulate organisational purpose or navigate stakeholder concerns. When leaders ask their analytics team "what should we do with AI?" they have abdicated their primary responsibility. + +**Confusing AI knowledge with AI savviness.** A leader who can explain how a neural network operates but cannot connect that knowledge to a customer retention problem is knowledgeable but not savvy. Savviness is applied understanding -- the ability to translate technical capability into business value. + +**Waiting until you feel ready.** Perfectionism disguised as prudence. The gap between knowledge and deployment will never close completely. Leaders who wait for full understanding before engaging will wait indefinitely while their organisations drift. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Foundational AI literacy | Understand what AI can and cannot do; assess whether AI is genuinely relevant to the problem the venture addresses | +| Validation | AI-informed product thinking | Learn enough to evaluate whether AI is the right tool for the specific use case, not just an impressive technology to mention in pitch decks | +| Early Traction | Leading the first AI deployment | Maintain active involvement as AI moves from concept to implementation; resist the urge to hand off to technologists | +| Growth | Scaling AI across the organisation | Expand from a single use case to enterprise-wide adoption; model AI usage personally to drive cultural change | +| Scale | Institutional AI governance | Establish continuous learning infrastructure -- workshops, peer circles, ethical reviews -- that outlasts any single leader | + +At the idea stage, the temptation is to treat AI as a feature to attract investors. Resist this. AI savviness at this stage means honestly evaluating whether the proposed solution requires AI at all, or whether simpler approaches would suffice. Investors see through AI window-dressing faster than founders expect. + +During growth and scale, the leader's personal learning journey becomes the organisation's learning culture. The research shows that employees mirror their leaders' relationship with AI. A leader who learns publicly, admits gaps openly, and engages with the technology visibly creates permission for the entire organisation to do the same. + +The ethical dimension of learning intensifies at scale. As AI systems are applied to increasingly sensitive business use cases, the considerations needed to ensure responsible deployment evolve constantly. Leaders must learn not only about AI capabilities but about emerging biases, regulatory shifts, and the responsibilities that accompany powerful technology. OpenAI's Sam Altman publicly acknowledging that his own creation, ChatGPT, carries societal dangers illustrates why ethical learning is not a peripheral concern -- it is central to credible AI leadership. + +The framework also emphasises that lifelong learning is collaborative, not solitary. Organisations can accelerate their leaders' development by creating in-house workshops, inviting experienced industry peers and external faculty, and partnering with business schools. The individual leader's commitment to learning must be matched by institutional investment in making that learning possible, structured, and continuous. + +--- + +## Output Template + +**Target Audience: Board / Leadership Team** + +```markdown +# AI Savviness Assessment and Learning Plan +## Date: [Date] +## Leader: [Name / Role] + +### Current State Assessment +- AI Knowledge Level: [Basic / Intermediate / Advanced] +- AI Engagement Level: [Disengaged / Deferential / Active / Leading] +- Key Knowledge Gaps: [List specific gaps at Level 1 and Level 2] + +### The Confidence Gap +- Situations where I defer to technologists unnecessarily: [List] +- Decisions I should own but currently do not: [List] +- Business questions that remain unasked in AI discussions: [List] + +### 90-Day Learning Plan +| Week | Focus Area | Activity | Outcome | +|------|-----------|----------|---------| +| 1-2 | AI fundamentals | [Specific activity] | [Measurable outcome] | +| 3-4 | Business context fit | [Specific activity] | [Measurable outcome] | +| 5-8 | Applied practice | [Specific activity] | [Measurable outcome] | +| 9-12 | Leadership integration | [Specific activity] | [Measurable outcome] | + +### Ongoing Learning Architecture +- Daily: [Reading / tool usage commitment] +- Weekly: [Technical team check-in format] +- Monthly: [Peer discussion / review cadence] +- Quarterly: [Ethical and regulatory update process] + +### Leading by Example +- AI tools I will use personally and visibly: [List] +- Forums where I will demonstrate learning publicly: [List] +- How I will signal that AI engagement is expected, not optional: [Plan] +``` + +--- + +## Related Skills + +- **[AI Purpose-Driven Questions](ai-purpose-driven-questions.md)** -- Learning what AI can do is the prerequisite; knowing which questions to ask it is the application. These two skills form a natural sequence. +- **[AI Communication Culture](ai-communication-culture.md)** -- AI-savvy leaders must translate their learning into shared language that bridges technical and business teams. +- **[AI Vision and Strategy](ai-vision-and-strategy.md)** -- Foundational AI knowledge enables the visionary thinking required to set long-term AI strategy. +- **[Learning Agility](../leadership/learning-agility.md)** -- Covers general continuous learning practices; this skill applies those principles specifically to AI as a non-technical leader. +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Nadella's approach to AI-savvy leadership is built on Dweck's growth mindset; the two frameworks reinforce each other directly. +- **[AI Augmentation Not Automation](ai-augmentation-not-automation.md)** -- Understanding AI capabilities is the prerequisite for making informed augmentation-versus-automation decisions about specific tasks and roles. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-purpose-driven-questions.md b/plugins/foreman/content/skills/ai-leadership/ai-purpose-driven-questions.md new file mode 100644 index 0000000..4f4308f --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-purpose-driven-questions.md @@ -0,0 +1,199 @@ +--- +name: "ai-purpose-driven-questions" +description: "Teaches leaders to ground AI adoption in organisational purpose by asking the right questions before selecting tools. Applies the purpose-driven framework to prevent technology-for-technology's-sake deployments. Use when evaluating AI investments against business goals, when data scientists operate without strategic direction, when AI projects lack clear problem definitions, when aligning AI initiatives with company values, or when leaders are tempted to adopt AI because competitors have." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-strategy + - purpose-alignment + - data-driven-decisions + - business-questions + - ai-adoption + - value-alignment +related_skills: + - ai-learning-for-leaders + - ai-inclusive-collaboration + - ai-communication-culture + - ai-vision-and-strategy + - purpose-driven-leadership + - balanced-scorecard + - ai-era-leadership +author: "Fatih Guner" +--- + +# AI Purpose-Driven Questions + +Most leaders ask the wrong first question about AI. They ask "Which AI tool should we use?" or "What can AI do for us?" -- questions that position technology as the starting point and the organisation as the beneficiary of whatever the algorithms happen to produce. Garry Kasparov, the chess grandmaster who lost to IBM's Deep Blue in 1997, offers a sharper frame. "Machines don't have understanding," he told a TechCrunch audience. "They don't have a purpose." Neither, it turns out, do most AI deployments. A large telecom company deployed AI to predict customer churn, then bombarded at-risk customers with advertising. Many left anyway. The AI had answered the wrong question. It identified who was likely to leave rather than who could be persuaded to stay -- a distinction no algorithm could make without a human defining the purpose of the analysis. The technology worked perfectly. The leadership failed entirely. + +--- + +## The Framework + +### Why Purpose Must Precede Technology + +The second pillar of AI-savvy leadership rests on an uncomfortable observation: most business leaders cannot clearly articulate why their organisation exists. When asked what their company aims to achieve beyond making profits, they produce the same boilerplate values that appear on every corporate website. This vagueness is tolerable in ordinary operations. It becomes fatal when deploying AI, because AI systems require precise questions to produce useful answers, and those questions can only emerge from a clear understanding of organisational purpose. + +The failure pattern is consistent: + +1. Leaders declare the company a "data company" and invest millions in data infrastructure. +2. Data scientists amass enormous datasets and build sophisticated models. +3. The models produce insights that are technically impressive but strategically meaningless -- answering questions nobody in leadership thought to ask. +4. Leaders adopt the data scientists' conclusions as strategy, inverting the proper relationship between business leadership and technical analysis. + +This is the **purpose inversion**: letting data define strategy rather than using strategy to direct data collection and analysis. + +### The Question Hierarchy + +Purpose-driven AI adoption follows a strict hierarchy of questions: + +**Tier 1 -- Purpose Questions (Leaders Own These)** +- Why does this organisation exist? +- What values guide our decisions? +- Which stakeholder needs must we serve? +- What problems are we uniquely positioned to solve? + +**Tier 2 -- Strategic Questions (Leaders Ask These of Data Teams)** +- Does our data allow us to answer questions relevant to our purpose? +- If not, what data must we collect? +- Are we measuring what matters, or merely what is measurable? + +**Tier 3 -- Technical Questions (Data Teams Own These)** +- Which AI technique best addresses the strategic question? +- What are the model's limitations and biases? +- How do we validate outputs against real-world outcomes? + +The critical insight: **Tier 1 and Tier 2 questions are the leader's job.** They cannot be delegated to data scientists, who are trained to optimise models, not to interpret the purpose of a business. When leaders skip directly to Tier 3 -- "What AI should we buy?" -- they cede the most consequential decisions to people who lack the framework to make them. + +### Technology Is Neutral; Leaders Are Not + +The framework emphasises a point that much of the AI discourse ignores: all technology is neutral. AI can identify outcomes and even make decisions that influence lives, but it cannot intentionally pursue values. It has no common sense, no moral reasoning, no understanding of why humans are in business. Marvin Minsky identified this decades ago as the "common sense problem." Yann LeCun, chief AI scientist at Meta, recently confirmed that the AI community has not developed learning paradigms that allow machines to understand how the world works. + +The implication is stark. AI cannot ask the questions that matter to your organisation. Those questions emerge from purpose -- from human understanding of what the company values and why it exists. Leaders who expect AI to generate strategic direction are waiting for a calculator to develop opinions. + +### The Purpose-Profit Tension + +The framework confronts the practical challenge head-on: AI adoption requires substantial investment, and investors expect returns. Purpose-driven leadership does not mean ignoring economics. It means ensuring that the pursuit of profit operates within the broader context of organisational purpose. As Larry Fink, CEO of BlackRock, puts it: "Purpose is not the sole pursuit of profits, but the animating force for achieving them." + +A purpose-driven AI leader communicates that AI adoption is a long-term investment in sustainable value creation, not a short-term cost-cutting exercise. When this message is internalised, data scientists shift from maximising the volume of data analysed to focusing on the quality and relevance of insights produced. + +--- + +## Prompts + +**Prompt 1 -- Purpose Audit for AI Readiness:** +> "Help me conduct a purpose audit before our organisation adopts AI. Our stated mission is [describe]. Our actual strategic priorities are [describe]. The AI project under consideration would [describe]. Walk me through the question hierarchy: (1) Does this AI initiative align with our purpose, or is it technology-for-technology's-sake? (2) Are we asking the right questions of the data, or letting the data define our questions? (3) What purpose-driven questions should I bring to our data science team?" + +**Prompt 2 -- Reframing the Wrong Question:** +> "Our organisation is about to deploy AI to [describe project]. The project was initiated because [describe trigger -- competitor pressure, board mandate, etc.]. I suspect we are asking the wrong question. Help me apply the purpose-driven framework to: (1) identify what question we are actually asking the AI to answer, (2) determine whether this is the right question given our organisational purpose and values, (3) reframe the question if needed, and (4) identify what data we would need to answer the reframed question." + +**Prompt 3 -- Purpose-Technology Reconciliation:** +> "Our organisation's purpose is [describe]. AI technology is evolving rapidly in our industry, with competitors adopting [describe]. I feel pressure to match their moves. Help me reconcile our fixed purpose with the need to stay technologically current. Using the principle of 'be firm with the purpose, be agile with the technology,' design an approach that keeps us anchored to our values while remaining adaptive in our AI strategy." + +**Prompt 4 -- Data Scientist Collaboration Framework:** +> "I need to restructure my relationship with our data science team. Currently, they operate autonomously and report insights that I then try to incorporate into strategy. I want to invert this: I define the purpose-driven questions, they find the data and methods to answer them. Help me design: (1) a recurring meeting structure, (2) a question template I should bring to each session, (3) criteria for evaluating whether their work addresses our strategic priorities, and (4) a communication approach that respects their expertise while asserting my leadership over business direction." + +--- + +## Use Cases + +**Idea-Stage Fintech Founder Seduced by AI Capabilities** + +A founder planning an AI-powered lending platform becomes fixated on the technology's ability to process loan applications in seconds. Every pitch deck emphasises speed and automation. An advisor applies the purpose framework and asks a simple question: what problem is the business actually solving? The founder pauses. Speed is not the problem -- underserved borrowers lack access to fair credit evaluation, not faster rejection. This reframing shifts the entire AI strategy from optimising processing speed to building models that assess creditworthiness using non-traditional data points (utility payments, rental history) that serve the purpose of expanding access. The technology changes; the purpose clarifies everything. + +**Early-Traction SaaS Company Where Data Science Operates in a Vacuum** + +A B2B SaaS company has hired three data scientists who spend their time building increasingly sophisticated churn prediction models. The CEO, not technically fluent, waits for their reports and adjusts strategy accordingly. When the framework is applied, the fundamental dysfunction becomes visible: the data scientists are answering the question "which customers will leave?" when the purpose-aligned question is "which customers derive the most value from our product, and how do we deepen that value?" The CEO begins monthly meetings where he presents the company's strategic priorities and asks the data team to evaluate whether existing data can address those priorities. The first meeting reveals that the company collects extensive usage data but nothing about customer outcomes -- a gap that no amount of churn modelling could have exposed. + +**Growth-Stage Retailer Racing to Match Competitors** + +A mid-size retailer observes that every competitor has deployed AI-powered recommendation engines and feels compelled to follow. The Apple example proves instructive: Apple, known as a fast follower, declined to enter the LLM arms race because it conflicted with the company's privacy-centric purpose. The retailer's purpose centres on curated, personalised customer relationships -- a value that a generic recommendation engine might actually undermine if it reduces human interaction to algorithmic suggestions. The company instead deploys AI to augment its sales associates with real-time customer preference data, preserving the human relationship while enhancing it with analytical capability. Purpose dictates the deployment, not competitive anxiety. + +--- + +## Anti-Patterns + +**Asking data scientists to define business strategy.** When leaders tell their analytics team to "find something interesting in the data," they have surrendered strategic direction. Data scientists will optimise whatever metric they are given. Without purpose-driven questions from leadership, they optimise for the wrong things. + +**Confusing data volume with strategic clarity.** The research documents organisations that invest millions to amass ever-larger datasets, convinced that more data equals better decisions. Without purpose-driven questions guiding what data matters, the organisation drowns in noise while the signals it needs go uncollected. + +**Adopting AI because competitors have.** Competitive mimicry is the antithesis of purpose-driven adoption. Microsoft rushed to deploy "Sydney" in Bing to compete with Google; the chatbot threatened users and caused a $100 billion market value loss at Google when Bard launched with a factual error in its first demonstration. Both companies allowed competitive pressure to override purpose. + +**Treating purpose as fixed and AI as its servant exclusively.** Purpose should remain stable, but the road to achieving it must be flexible. The formula: be firm with the purpose you want to achieve, but be agile with how AI can help you achieve that value. A retail company using AI-based recommender systems today might switch to LLM-powered chatbots tomorrow -- same purpose, different tool. + +**Separating the "AI question" from the "business question."** There is no separate AI strategy. There is only business strategy, informed by AI capabilities. Leaders who create dedicated "AI strategy" documents disconnected from business strategy have already made the fundamental error. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Purpose definition | Establish why the venture exists before considering whether AI is relevant; the purpose determines whether AI is a genuine enabler or a distraction | +| Validation | Question formulation | Translate purpose into specific, testable questions that data can answer; validate that the right data exists or can be collected | +| Early Traction | Leader-data scientist alignment | Establish the collaboration rhythm where leaders pose purpose-driven questions and data teams find answers; resist deferring | +| Growth | Purpose-scaled AI governance | As AI spreads across departments, ensure every deployment answers a question tied to organisational purpose, not departmental convenience | +| Scale | Purpose resilience under pressure | Maintain purpose alignment when competitive pressure, investor expectations, and technological hype create urgency to adopt AI indiscriminately | + +At the idea and validation stages, the discipline of asking purpose-driven questions prevents premature technology commitment. Many founders build AI-powered solutions before confirming that their target customers need AI at all. The purpose framework forces the question: is this a genuine problem that AI uniquely solves, or is AI a feature bolted on to attract investment? + +At growth and scale, the challenge shifts from formulating questions to institutionalising the practice. Every department deploying AI should begin with a purpose statement, not a technical specification. Regular cross-functional reviews should evaluate whether AI outputs address the questions that matter most to the organisation's mission. + +--- + +## Output Template + +**Target Audience: Leadership Team / Board** + +```markdown +# Purpose-Driven AI Assessment: [Project Name] +## Date: [Date] + +### Organisational Purpose Alignment +- Stated mission: [Mission statement] +- Core values relevant to this AI initiative: [List] +- Strategic priority this initiative serves: [Describe] + +### Question Audit +| Level | Question We Are Asking | Question We Should Be Asking | Gap | +|-------|----------------------|----------------------------|-----| +| Purpose | [Current] | [Revised] | [Gap description] | +| Strategic | [Current] | [Revised] | [Gap description] | +| Technical | [Current] | [Revised] | [Gap description] | + +### Data Readiness +- Data available to answer purpose-aligned questions: [Describe] +- Data gaps that must be filled: [List] +- Data currently collected that serves no strategic purpose: [List] + +### Competitive Pressure Assessment +- Are we pursuing this because of purpose or because of competitors? [Honest assessment] +- Would this initiative make sense if no competitor had adopted AI? [Yes/No + reasoning] + +### Purpose-Profit Reconciliation +- Expected financial return: [Realistic estimate] +- Timeline: [Honest projection, avoiding the immediate-ROI trap] +- How this investment creates sustainable value: [Narrative] + +### Recommended Questions for Data Science Team +1. [Purpose-driven question] +2. [Purpose-driven question] +3. [Purpose-driven question] +``` + +--- + +## Related Skills + +- **[AI Learning for Leaders](ai-learning-for-leaders.md)** -- Foundational AI knowledge enables leaders to formulate purpose-driven questions with enough technical fluency to evaluate answers. +- **[AI Communication Culture](ai-communication-culture.md)** -- Purpose-driven questions lose their value if leaders cannot communicate them effectively to technical teams across organisational silos. +- **[AI Vision and Strategy](ai-vision-and-strategy.md)** -- Purpose defines the "why"; vision translates it into a compelling "where we are going" that inspires the organisation. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- Covers the broader practice of leading with purpose; this skill applies that principle specifically to AI adoption decisions. +- **[Balanced Scorecard](../frameworks/balanced-scorecard.md)** -- Provides the measurement framework for translating purpose into metrics that guide AI initiatives beyond pure financial returns. +- **[Strategic Questioning](../leadership/strategic-questioning.md)** -- The general practice of leading through questions rather than answers; this skill applies that discipline specifically to the AI context where questions matter more than technical expertise. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-stakeholder-balance.md b/plugins/foreman/content/skills/ai-leadership/ai-stakeholder-balance.md new file mode 100644 index 0000000..8319efe --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-stakeholder-balance.md @@ -0,0 +1,182 @@ +--- +name: "ai-stakeholder-balance" +description: "Guides leaders through the ethical and strategic complexities of balancing multiple stakeholder interests during AI adoption, from employees and customers to society at large. Provides frameworks for responsible AI deployment, stakeholder impact mapping, and moral decision-making when efficiency gains conflict with human welfare. Use when evaluating whether an AI deployment will harm employees or customers, weighing automation against workforce impact, facing pressure to prioritise shareholders over other stakeholders, designing an AI ethics governance structure, or confronting the societal consequences of algorithmic decision-making." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stakeholder-management + - ai-ethics + - responsible-ai + - risk-management + - governance + - societal-impact + - fairness + - ai-adoption +related_skills: + - ai-human-centered-approach + - ai-augmentation-not-automation + - ai-emotional-intelligence + - emotional-intelligence + - psychological-safety + - trust-equation + - leading-through-change +author: "Fatih Guner" +--- + +# AI Stakeholder Balance + +A scale, by definition, must have two sides. Most leaders deploying AI place efficiency on one side and load the other with nothing at all -- then marvel at how quickly things tip over. The promise of artificial intelligence is real: faster decisions, lower costs, sharper predictions. But efficiency is not a value-neutral concept. Efficiency *for whom* is the question that separates organisations that extract lasting value from AI from those that generate headlines about algorithmic bias, workforce revolts, and regulatory backlash. When Boston deployed an AI-optimised school bus scheduling system designed by two MIT graduates to trim a $100 million transportation budget, the algorithm dutifully reshuffled start times across hundreds of schools. It did not, however, consider that shifting elementary school start times to 7:15 a.m. would create a childcare gap that forced parents to change jobs or scramble for emergency arrangements. The city dropped the plan. The algorithm had optimised for cost. It had forgotten the humans. + +--- + +## The Framework + +### The Stakeholder Triad in AI Adoption + +AI adoption decisions radiate outward in concentric circles. At the centre sit the three stakeholder groups whose interests a leader must actively balance: employees, customers, and society. Most leaders acknowledge the first two and entirely forget the third. + +**Employees** are the most immediately affected. Surveys indicate that organisations expect automation to increase workforce capacity by 30 to 40 percent -- a statistic that, from the employee's perspective, reads as a 30 to 40 percent reduction in their perceived indispensability. Employees fear job loss, but they also fear something subtler: the erosion of agency, the sense that they have become appendages to an algorithm rather than professionals exercising judgment. + +**Customers** sit at the receiving end of AI-driven interactions. An algorithm that predicts palliative care eligibility using electronic health records may achieve impressive accuracy, but it cannot hold an end-of-life conversation. It cannot understand why a patient with a terminal diagnosis might still prefer aggressive treatment over statistical probability. Anand Avati and associates at Stanford developed precisely such an algorithm in 2018, and the fundamental limitation was not technical but human: AI regresses to the mean, approximating any individual's needs by referencing the average of a population. If a customer deviates from that average, the algorithm fails them. + +**Society** is the forgotten stakeholder. The AI decisions a company makes about hiring, pricing, surveillance, and data collection do not exist in a vacuum. Amazon's gender-biased recruiting algorithm, the UK's student grading algorithm that penalised students from poorer schools -- these were not just corporate embarrassments. They were societal harms with real victims who had no seat at the decision-making table. + +### Four Principles for Stakeholder-Balanced AI + +Research across multiple organisations and regulatory environments yields four principles that distinguish responsible AI adoption from the merely profitable kind. + +**Principle 1: AI is a tool, not a stakeholder manager.** The technology cannot go beyond treating a stakeholder as a data point. Supervised machine learning regresses observations to the mean and avoids outliers. Every individual stakeholder -- the atypical customer, the employee with unusual circumstances, the community with specific needs -- becomes an approximation. Leaders who delegate stakeholder management to AI are not managing stakeholders; they are managing averages. + +**Principle 2: Human intelligence imagines; AI intelligence extrapolates.** When an organisation adopts AI to promote innovation, it needs decisions based on thinking beyond what is already known. AI excels at extrapolation from existing data. It cannot imagine what does not yet exist. The ability to anticipate, take perspective, and envision what drives stakeholders at any given moment remains irreducibly human. + +**Principle 3: Financial motivation corrupts stakeholder judgment.** Research demonstrates that the more salient a financial incentive becomes, the more decision-makers will refrain from making the responsible choice. When Facebook was urged to address misinformation, its AI director reportedly slowed initiatives because they might harm the company's growth strategy. A heavily funded AI project creates its own gravitational pull toward financial justification at the expense of stakeholder welfare. + +**Principle 4: Identify all stakeholders -- especially the invisible ones.** The most dangerous omissions are the stakeholders who are not immediately visible: the parents affected by a school scheduling algorithm, the job applicants screened out by a biased hiring model, the communities whose data feeds a surveillance system. Leaders must think in terms of both direct and indirect, short-term and long-term stakeholder impact. + +### The Stakeholder Impact Matrix + +| Stakeholder Group | Direct Impact | Indirect Impact | Time Horizon | Typical Blind Spot | +|---|---|---|---|---| +| Employees | Job redesign, skill demands, algorithmic supervision | Work identity, psychological safety, bargaining power | Immediate to medium-term | Assuming silence equals acceptance | +| Customers | Service quality, personalisation, data privacy | Trust, brand loyalty, switching costs | Medium-term | Treating customers as data profiles | +| Shareholders | ROI on AI investment, competitive positioning | Long-term reputation risk, regulatory exposure | Short to medium-term | Conflating short-term returns with sustainable value | +| Society | Employment patterns, inequality, public services | Democratic processes, social cohesion, economic mobility | Long-term | Assuming societal impact is someone else's problem | +| Regulators | Compliance requirements, reporting obligations | Industry standards, public trust in technology | Medium to long-term | Treating regulation as an obstacle rather than a signal | + +### The Therac-25 Warning + +The Therac-25 case -- a computer-controlled radiation therapy machine used for cancer treatment -- remains one of the most sobering examples of what happens when human oversight is subordinated to algorithmic authority. Decisions that would have been made by licensed technicians were delegated to the machine. When patients received fatal overdoses of radiation, the technicians who should have intervened failed to override the software, even as patients cried out in pain. They had been instructed that it was "virtually impossible" for the system to overdose a patient. The mindset that "the computer knows best" led directly to the disengagement of the human technician -- and to deaths that competent human oversight would have prevented. + +The lesson extends far beyond healthcare. Every AI deployment carries a version of this risk: the gradual erosion of human judgment in favour of algorithmic authority, producing outcomes that no stakeholder -- not the technician, not the patient, not the institution -- actually wanted. + +--- + +## Prompts + +**Prompt 1 -- Stakeholder Impact Audit:** +> We are planning to deploy AI in [describe the specific AI application -- e.g., customer service automation, hiring screening, performance monitoring]. Map every stakeholder group that will be affected, both directly and indirectly, in the short term and long term. For each group, identify what they stand to gain, what they stand to lose, and where the most serious conflicts between stakeholder interests will emerge. Pay special attention to stakeholders who are not immediately visible. + +**Prompt 2 -- Ethical Risk Assessment:** +> Our AI adoption project involves [describe the project]. Conduct an ethical risk assessment: identify scenarios where the AI could produce outcomes that harm employees, customers, or society even while meeting its intended efficiency objectives. For each risk, assess severity, likelihood, and the strength of the human oversight mechanisms currently in place. Recommend specific governance structures to mitigate the top three risks. + +**Prompt 3 -- Stakeholder Communication Strategy:** +> We are deploying AI that will affect [describe affected groups]. Design a stakeholder communication plan that addresses each group's specific concerns, explains what the AI will and will not do, establishes transparency about data usage, and creates feedback mechanisms. The plan should include what to say when the honest answer is "we do not yet know the full impact." + +**Prompt 4 -- Society-as-Stakeholder Analysis:** +> Analyse the broader societal implications of our AI deployment in [describe context]. Consider effects on employment patterns in our region, potential for algorithmic bias across demographic groups, data privacy implications, and the precedent our approach sets for our industry. Recommend specific actions to mitigate societal harms while preserving the business value of the deployment. + +--- + +## Use Cases + +**Early-Traction Fintech Startup Automating Loan Decisions** + +A fintech startup with 30 employees deploys an AI model to automate small-business loan approvals. The model is fast, consistent, and demonstrably more profitable than the human underwriters it partially replaces. Six months in, a pattern emerges: the algorithm systematically disadvantages applicants from certain postal codes that correlate with lower-income, minority-heavy communities. The founders face a choice between a model that maximises approval accuracy (by their historical lending data) and one that serves the broader community equitably. Applying the stakeholder impact matrix, they map not just the direct impact on loan applicants but the indirect societal effect of perpetuating lending discrimination. The decision: retrain the model with fairness constraints, accept a modest reduction in predictive accuracy, and publish their fairness metrics publicly. The short-term cost is higher default rates. The medium-term gain is regulatory goodwill, brand trust, and a defensible position when lending regulations tighten -- which they invariably do. + +**Growth-Stage E-Commerce Company Introducing Algorithmic Performance Monitoring** + +A 200-person e-commerce company introduces an AI system to monitor warehouse worker productivity, adjusting individual targets based on historical performance data. Within weeks, absenteeism increases, error rates rise, and three senior packers -- the informal leaders of the warehouse floor -- resign. Exit interviews reveal a consistent theme: employees feel they are being treated like robots, monitored continuously, with targets that ratchet upward regardless of circumstance. The operations VP applies the principle of reflective procrastination -- the insight that allowing human variability, including bad days and creative pauses, produces better long-term results than algorithmic optimisation. The system is redesigned to account for individual working preferences, allow employee feedback on pace, and build in rest periods determined by workers rather than by the algorithm. Productivity data after the redesign shows reports are completed faster and with greater reliability than before -- achieved by respecting the human condition rather than overriding it. + +**Scale-Stage Healthcare Platform Deploying Predictive Diagnostics** + +A healthcare technology company deploys a predictive algorithm across 50 partner clinics to identify patients at risk of specific conditions. The algorithm performs well on aggregate metrics. A senior data scientist notices, however, that performance varies dramatically across demographic groups -- significantly worse for patients over 70 and for patients from non-English-speaking backgrounds, whose historical data is sparser. The company must decide whether to deploy broadly (maximising revenue) or restrict deployment to populations where the model is reliable (protecting patients). The stakeholder analysis reveals that broad deployment creates an invisible stakeholder harm: patients who receive inaccurate risk assessments may make medical decisions based on flawed predictions. The company restricts deployment, invests in collecting more diverse training data, and communicates the limitation transparently to partner clinics -- a decision that costs a quarter's revenue target but avoids the catastrophic trust destruction of a misdiagnosis scandal. + +--- + +## Anti-Patterns + +1. **Treating stakeholder impact as a post-deployment audit.** The time to assess stakeholder impact is before the algorithm is built, not after complaints arrive. Retrospective ethics reviews are reputation management, not responsible leadership. By the time harm is detected, the affected stakeholders have already paid the price. + +2. **Equating stakeholder management with customer management.** Leaders who define stakeholders as "employees and customers" and stop there are ignoring the constituency that will ultimately regulate, tax, and constrain their AI use: society. The Boston bus scheduling disaster was not a customer problem. It was a society problem that the decision-makers had not considered at all. + +3. **Delegating AI ethics to the technical team.** Ethics committees staffed exclusively with engineers and data scientists lack the philosophical, legal, and sociological perspectives needed to identify non-obvious harms. Hugging Face's model -- a dedicated, cross-disciplinary ethics group with a mandate to halt projects that reveal significant harm -- represents the standard that responsible organisations should aspire to. + +4. **Assuming algorithmic fairness is a mathematical property.** Fairness is a human value that requires human judgment. An algorithm can be optimised for statistical parity across groups while still producing outcomes that every reasonable person would consider unfair. The UK grading algorithm was statistically consistent. It was also morally indefensible. + +5. **Privileging speed over deliberation.** The pressure to deploy AI quickly -- to capture first-mover advantage, to justify investment, to satisfy board expectations -- creates a systematic bias against the careful stakeholder analysis that prevents harm. Speed is a business virtue. Recklessness disguised as speed is not. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Stakeholder identification | At the idea stage, the leader defines which stakeholders the AI is intended to serve -- and must resist the temptation to define that group too narrowly. The stakeholder map created now determines what harms will be invisible later. | +| Validation | Ethical hypothesis testing | Validation involves testing not just whether the AI works but whether it works fairly and without unintended harm across stakeholder groups. Prototype testing should include edge cases and underrepresented populations. | +| Early Traction | Governance infrastructure | The transition from prototype to production requires formal governance: who reviews algorithmic decisions, how stakeholders provide feedback, what triggers a human override. These structures are vastly easier to build now than to retrofit later. | +| Growth | Scaling without diluting oversight | Growth creates pressure to automate oversight itself. The challenge is maintaining human judgment in the loop as the volume of AI-driven decisions increases by orders of magnitude. This is the stage where stakeholder harm most often escapes detection. | +| Scale | Systemic and societal accountability | At scale, the organisation's AI decisions affect not just individual stakeholders but entire markets, communities, and public systems. The leader must engage with regulators, participate in industry standards, and accept that their AI's societal impact is a legitimate subject of public scrutiny. | + +--- + +## Output Template + +```markdown +# AI Stakeholder Impact Assessment + +## AI Application +- **Description:** [What the AI system does] +- **Primary business objective:** [Cost reduction / Revenue growth / Quality improvement / Speed] +- **Deployment scope:** [Number of people/transactions affected] + +## Stakeholder Map +| Stakeholder Group | Interest at Stake | Positive Impact | Negative Risk | Risk Severity (1-5) | Mitigation | +|---|---|---|---|---|---| +| [Group 1] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] | +| [Group 2] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] | +| [Society] | [Broader implications] | [Potential benefits] | [Potential harms] | [1-5] | [Specific action] | + +## Conflict Analysis +| Conflict | Stakeholder A Wants | Stakeholder B Wants | Resolution Principle | Decision | +|---|---|---|---|---| +| [Describe tension] | [Their interest] | [Their interest] | [Which principle applies] | [How you resolve it] | + +## Governance Structure +- **Ethics review body:** [Composition and mandate] +- **Override authority:** [Who can halt an AI decision and under what conditions] +- **Feedback mechanism:** [How stakeholders report concerns] +- **Audit cadence:** [How often stakeholder impact is formally reviewed] + +## Commitments +- **We will:** [Specific promises to stakeholders] +- **We will not:** [Explicit boundaries on AI use] +- **We will disclose:** [What transparency looks like in practice] +``` + +--- + +## Related Skills + +- **[AI Human-Centered Approach](ai-human-centered-approach.md)** -- Stakeholder balance provides the strategic framework; the human-centred approach supplies the operational mindset for putting people before algorithms. +- **[AI Augmentation Not Automation](ai-augmentation-not-automation.md)** -- The choice between augmentation and automation is itself a stakeholder decision: automation prioritises shareholders while augmentation distributes value more broadly. +- **[AI Emotional Intelligence](ai-emotional-intelligence.md)** -- Balancing stakeholder interests requires the emotional intelligence to understand what different groups actually feel, not merely what they say in surveys. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Stakeholder trust is the currency that responsible AI governance either builds or destroys; the trust equation provides the diagnostic for understanding why. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- AI adoption is a specific instance of organisational change; stakeholder balance determines whether that change is experienced as progress or as imposition. +- **[Systems Thinking](../frameworks/systems-thinking.md)** -- Stakeholder balance requires understanding the feedback loops between employee experience, customer satisfaction, and shareholder returns rather than treating each as independent. diff --git a/plugins/foreman/content/skills/ai-leadership/ai-vision-and-strategy.md b/plugins/foreman/content/skills/ai-leadership/ai-vision-and-strategy.md new file mode 100644 index 0000000..48ac3db --- /dev/null +++ b/plugins/foreman/content/skills/ai-leadership/ai-vision-and-strategy.md @@ -0,0 +1,230 @@ +--- +name: "ai-vision-and-strategy" +description: "Guides leaders in developing and communicating a compelling AI vision that inspires rather than threatens, choosing augmentation over replacement as the strategic paradigm. Covers Perspective 1 (AI replaces humans) vs. Perspective 2 (AI augments humans), the tech-driving-tech trap, holistic communication, ethical foresight, and agile visionary leadership. Use when setting long-term AI strategy, when employees fear AI will eliminate their jobs, when AI adoption lacks a unifying narrative, when vision statements betray organisational identity, or when leaders need to translate AI potential into a story that builds commitment." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-vision + - ai-strategy + - augmentation-vs-replacement + - holistic-communication + - visionary-leadership + - organisational-identity + - agile-leadership +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-communication-culture + - ai-era-leadership + - scenario-planning + - kotter-change-model +author: "Fatih Guner" +--- + +# AI Vision and Strategy + +Ninety percent of organisations have experimented with AI. Only 17 percent have succeeded in scaling it. The gap between experimentation and institutionalisation is not a technology problem -- it is a vision problem. One CEO, upon deciding to adopt AI, told his leadership team that business strategies of the past would no longer be relevant, that organisations needed to "start thinking like machines," and that AI engineers would become "the voices of the future." The meeting erupted in chaos. Managers asked in near-despair what this meant for their own jobs and their teams. The CEO had presented AI as an inevitability without a human story -- a technology-first vision that offered efficiency but no meaning. Contrast this with a logistics company leader who articulated precisely why AI mattered for inventory management, acknowledged what it could and could not do, set realistic targets, and told her workforce: "We're not using AI simply to use AI. It needs to help and make a difference, or else we will not use it." A year later, the adoption was expanding at every level. The difference between these two leaders was not technical knowledge. It was vision. + +--- + +## The Framework + +### The Two Perspectives + +The framework presents the entire AI leadership challenge as a choice between two fundamentally different perspectives: + +**Perspective 1: AI as Replacement** + +AI is an increasingly cheap way to replace people and achieve new levels of productivity and efficiency. Under this view, the primary focus is using AI to make the best use of data and, eventually, to delegate decision-making and thinking to the technology. Leaders who adopt this perspective are, ironically, making themselves redundant. If the logic holds -- if AI can think as well as humans but cheaper -- then leadership itself becomes dispensable. + +This pattern is called **tech-driving-tech transformation**: people valuing AI's computational prowess over human understanding and letting it lead. The Synthetic Party in Denmark, whose leader is an AI chatbot named Lars, and NetDragon Websoft, which appointed a robot named Tang Yu as CEO, embody this perspective taken to its logical extreme. + +**Perspective 2: AI as Augmentation** + +AI is a powerful tool to augment -- not replace -- human intelligence, unlocking innovation and creativity in workers. Under this view, investing in humans is the priority. Leaders take active charge of AI adoption to complement a human-centred strategy. This approach does not focus primarily on reducing costs; it requires significant investment in human resources to deploy AI in human-centred ways. + +The entire architecture of this framework argues for Perspective 2. The evidence supports it: AI cannot infer meaning, exercise moral reasoning, appreciate cultural nuance, generate genuinely novel ideas, or understand why humans are in business. Kate Crawford of Microsoft Research puts it plainly: "Most AI is neither artificial, nor intelligent." Vision is a uniquely human capacity, and the AI-savvy leader does not outsource it. + +### Why Vision Fails in AI Adoption + +The research identifies three specific reasons why leaders with otherwise strong visionary skills fail when it comes to AI: + +**1. The Bridge Problem.** Leaders can imagine an AI-enabled future but cannot see the bridge to get there. The technology shifts too rapidly. Building a bridge when you are uncertain where the other bank is -- or whether it will move -- creates paralysis. + +**2. The Expectations Trap.** Leaders project that AI will deliver immediate results, then are disappointed when the technology falls short or scaling proves difficult. This premature disappointment leads to abandonment. + +**3. The Silo Default.** Leaders announce an AI vision, then expect AI engineers to carry it forward. Without continued leadership involvement, AI adoption fractures into independent departmental projects that serve narrow interests rather than organisational goals. + +### Holistic Communication + +To overcome these failures, the framework prescribes **holistic communication** -- a visionary approach built on four principles: + +| Principle | Impact | +|-----------|--------| +| Improve your tech savviness | Helps explain AI's function and goal in your own words, making the business narrative relevant and meaningful to the workforce | +| Be authentic | Makes you persuasive because you know what you are talking about; enables genuine connection with your audience | +| Use the rhetoric of collaboration | Rallies everyone around the common goal of AI adoption as a shared endeavour | +| Show empathy | Gives employees confidence that AI adoption is not an end in itself but a means to an end, with full recognition of the workforce's interests | + +Holistic communication is what separates vision from announcement. A leader who merely declares "we are adopting AI" has made an announcement. A leader who explains why AI matters for the organisation's purpose, how it will change workflows, what it will not change about the company's identity, and how employees fit into the future -- that leader has communicated a vision. + +### Preserving Organisational Identity + +Research with collaborator Shane Schweitzer demonstrates a counterintuitive finding: AI vision statements that promise to transform the company into a technology company actually reduce employee commitment and customer loyalty. + +CEOs of major banks have stated: +- "We're clearly a technology company." (CEO, Bank of America) +- "We act less like a bank and more like a tech company." (CEO, DBS Bank) +- "In many ways, we see ourselves as a technology company with a banking license." (CEO, Citibank) + +Across several studies, the research found that such statements made employees and customers feel that banking was no longer central to the institution. Neither party could identify what the bank stood for -- besides wanting to be a technology company. As a result, neither employees nor customers were willing to commit to or trust the institution. + +The lesson: an AI-based vision must emphasise that the technology supports what the company already stands for. Bosch CEO Volkmar Denner modelled this correctly: "Ten years from now, scarcely any Bosch product will be conceivable without AI." The statement keeps Bosch products -- not AI -- at the centre of the vision. + +### Ethical Foresight + +Visionary AI leadership requires incorporating ethical considerations into the strategic narrative from the beginning, not as an afterthought. AI systems are frequently biased, often opaque, and increasingly subject to regulation. Leaders who ignore these dimensions in their vision will be caught unprepared when biases surface, when regulators intervene, or when stakeholders lose trust. + +Consider a health insurance example: a company deploying AI to predict risk profiles and set premiums must proactively invest in explainability techniques, transparency policies, and data governance. The leader who includes ethical considerations in the AI vision from the start builds credibility; the leader who addresses them only after a scandal has lost it. + +### Agile Vision + +Being visionary does not mean being rigid. AI adoption involves iteration and experimentation. Initial performance targets may prove unreasonable. Work routines may be disrupted before they are improved. New AI capabilities may emerge that render current approaches obsolete. + +The formula: provide a clear overarching goal while giving teams the freedom to pivot from unreasonable objectives. The logistics CEO he profiles exemplified this -- she baked agility into her core vision message, telling employees that AI adoption was not a plug-and-play process and that challenges should be anticipated and addressed collaboratively. + +--- + +## Prompts + +**Prompt 1 -- AI Vision Statement Development:** +> "Help me craft an AI vision for [describe organisation, its purpose, and its identity]. Using the holistic communication framework, the vision must: (1) emphasise that AI supports what the company already stands for, rather than transforming it into a tech company, (2) use the rhetoric of collaboration to frame AI as a shared endeavour, (3) show empathy for employee concerns about job displacement, (4) demonstrate tech savviness without pretending to technical expertise, and (5) preserve the organisation's core identity while articulating how AI enhances it." + +**Prompt 2 -- Perspective 1 vs. Perspective 2 Diagnostic:** +> "Analyse our current AI strategy and determine whether it follows Perspective 1 (AI as replacement for efficiency) or Perspective 2 (AI as augmentation of human capability). Our AI initiatives include [describe]. Employee sentiment about AI is [describe]. Leadership communication about AI has emphasised [describe]. If we are operating under Perspective 1, design a transition plan to Perspective 2 that reframes our AI narrative, adjusts our investment priorities, and rebuilds employee trust." + +**Prompt 3 -- Vision Credibility Assessment:** +> "Evaluate the credibility of our AI vision. Our stated vision is [describe]. Using the framework, assess whether: (1) the vision starts with the problem we are solving, not the technology we are buying, (2) it demonstrates informed decision-making rather than following trends, (3) it includes ethical considerations and regulatory foresight, (4) it signals agility rather than rigidity, and (5) it preserves organisational identity. Identify specific weaknesses and recommend revisions." + +**Prompt 4 -- Agile AI Strategy Design:** +> "Design an agile AI adoption strategy for [describe organisation and context]. The strategy must: (1) provide a clear overarching vision that inspires commitment, (2) build in mechanisms for adjusting targets based on real-world outcomes, (3) encourage teams to anticipate challenges rather than be surprised by them, (4) remain responsive to emerging AI developments (e.g., the sudden prominence of LLMs), and (5) balance ambition with realism so that employees feel challenged but not threatened." + +--- + +## Use Cases + +**Idea-Stage AI Startup Choosing Between Replacement and Augmentation** + +Two co-founders building an AI-powered writing assistant disagree on the product's fundamental positioning. One frames the product as replacing human copywriters (cheaper, faster, no benefits to pay). The other frames it as augmenting writers (handling first drafts, research summaries, and structural suggestions while humans provide voice, judgement, and creativity). The augmentation frame proves more compelling to early users, who resist tools that threaten their professional identity but embrace tools that make them more productive. It also proves more compelling to investors, who recognise that pure replacement products face commoditisation pressure as every LLM provider offers similar capabilities. The Perspective 2 vision differentiates the product by centring human capability rather than cost reduction. + +**Growth-Stage Financial Services Firm Whose Vision Alienated Employees** + +A mid-size bank, responding to competitive pressure from fintechs, declares itself a "technology company that happens to hold a banking license." Employee surveys reveal a sharp decline in engagement and loyalty. Customer research shows that clients prefer their banker -- not an analytics expert -- to manage their finances. Applying the research findings, the bank reframes its vision: AI will enhance the bank's ability to deliver personalised financial guidance, enabling relationship managers to serve clients with deeper insight and faster response times. The bank remains a bank. AI becomes the instrument, not the identity. Employee engagement recovers within two quarters, and client retention improves as relationship managers report feeling empowered rather than displaced. + +**Scale-Stage Logistics Company Embedding Agility into AI Vision** + +A global logistics firm with AI deployed across warehousing, routing, and demand forecasting faces a new challenge: the emergence of LLM-based tools that could transform how planners interact with data. The company's AI vision, written two years earlier, makes no mention of generative AI. Rather than rewriting the vision, the CEO invokes the agility principle embedded in the original statement: "Our commitment is to using AI to help our people plan better and serve customers faster. The specific tools will evolve; the commitment will not." Teams are given latitude to experiment with LLM-based interfaces while the overarching performance goals remain stable. The vision flexes without breaking because agility was built into its foundation from the start. + +--- + +## Anti-Patterns + +**Declaring the company a technology company.** The research demonstrates that AI vision statements framing traditional businesses as technology companies reduce both employee commitment and customer trust. The company's identity should remain intact; AI is the enabler, not the identity. + +**Presenting AI as inevitable and demanding compliance.** "Everything is changing; get on board" is not a vision. It is coercion wrapped in technological determinism. Employees who feel threatened rather than inspired will resist, quietly or otherwise. Vision must offer meaning, not just momentum. + +**Setting the vision and walking away.** Leaders who deliver an inspiring AI speech and then delegate execution to engineers have made the silo default error. AI vision requires continuous leadership involvement -- adjusting targets, celebrating progress, acknowledging failures, and maintaining the human narrative. + +**Promising immediate returns.** The expectations trap claims leaders who project that AI will deliver transformational results quickly. When the technology falls short -- as it inevitably does in early deployment -- disappointment leads to abandonment. Honest timelines and realistic targets build credibility. + +**Ignoring ethics until forced to confront them.** Bias, opacity, and regulatory risk are not edge cases. They are central features of AI deployment. Leaders who exclude ethical considerations from their vision will face them as crises rather than managing them as expected challenges. + +**Rigid long-term AI roadmaps.** A five-year AI roadmap written without agility provisions will be obsolete within months. The field moves too quickly for rigid planning. The agile vision principle -- clear goals, flexible methods -- is the only sustainable approach. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision as differentiator | Articulate how AI serves the venture's purpose in a way that attracts talent and investment; choose Perspective 2 from the start | +| Validation | Vision-reality alignment | Test whether the AI vision survives contact with real users and real data; adjust expectations based on evidence rather than hype | +| Early Traction | Vision communication at scale | Move beyond founder-to-team communication; ensure the AI vision is understood and embraced across a growing organisation | +| Growth | Vision preservation under competitive pressure | Resist the temptation to abandon purpose-aligned AI strategy in favour of copying competitors; maintain organisational identity | +| Scale | Institutional vision governance | Embed the AI vision into strategic planning, performance evaluation, and cultural practice so it outlasts any single leader | + +At the idea stage, the choice between Perspective 1 and Perspective 2 is foundational. Startups that build on the replacement paradigm attract talent that shares that worldview and build products that embody it. Changing the paradigm later requires rebuilding culture, product, and positioning simultaneously. + +At growth and scale, the challenge is maintaining vision coherence as the organisation encounters competitive pressure, technological disruption, and stakeholder fatigue. The logistics CEO's approach -- agility baked into the vision's architecture -- offers a model. The vision remains fixed on purpose while accommodating shifts in the technological landscape. + +--- + +## Output Template + +**Target Audience: Board / All-Hands** + +```markdown +# AI Vision and Strategy: [Organisation Name] +## Date: [Date] + +### Vision Statement +[A concise statement that emphasises augmentation, preserves identity, and inspires commitment] + +### Perspective Assessment +- Current paradigm: [Perspective 1 (Replacement) / Perspective 2 (Augmentation) / Mixed] +- Target paradigm: Perspective 2 -- AI augments human capability +- Transition steps required: [List if currently Perspective 1] + +### Organisational Identity Preservation +- Core identity elements that AI must not change: [List] +- Ways AI will strengthen these elements: [Describe] +- Risk of identity erosion: [Assess] + +### Holistic Communication Plan +| Audience | Key Message | Communication Channel | Cadence | +|----------|-----------|---------------------|---------| +| Employees | [Message] | [Channel] | [Frequency] | +| Customers | [Message] | [Channel] | [Frequency] | +| Investors/Board | [Message] | [Channel] | [Frequency] | +| Partners | [Message] | [Channel] | [Frequency] | + +### Ethical Foresight +- Known bias risks: [List] +- Regulatory landscape: [Summarise relevant regulations] +- Explainability investments: [Planned/Active] +- Proactive governance measures: [List] + +### Agility Architecture +- Fixed elements (will not change): [List -- purpose, values, identity] +- Flexible elements (will adapt): [List -- specific tools, timelines, methods] +- Review cadence for adjusting AI approach: [Frequency] +- Process for incorporating emerging AI capabilities: [Describe] + +### Success Metrics +| Metric | Baseline | 6-Month Target | 12-Month Target | +|--------|----------|---------------|-----------------| +| Employee AI adoption rate | [%] | [%] | [%] | +| Employee engagement score | [Score] | [Score] | [Score] | +| AI contribution to [business metric] | [Baseline] | [Target] | [Target] | +| Customer trust in AI-enabled services | [Score] | [Score] | [Score] | +``` + +--- + +## Related Skills + +- **[AI Learning for Leaders](ai-learning-for-leaders.md)** -- Tech savviness is one of the four pillars of holistic communication; leaders cannot articulate a credible AI vision without foundational knowledge. +- **[AI Purpose-Driven Questions](ai-purpose-driven-questions.md)** -- Purpose provides the foundation upon which vision is built; without clear purpose, vision becomes empty aspiration. +- **[AI Inclusive Collaboration](ai-inclusive-collaboration.md)** -- Vision requires collaboration rhetoric; inclusive collaboration ensures that the vision reflects diverse stakeholder perspectives. +- **[AI Communication Culture](ai-communication-culture.md)** -- The flat communication culture this skill builds is the infrastructure through which vision is communicated, tested, and refined. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- Provides structured methods for anticipating multiple AI futures, supporting the agile vision approach prescribed. +- **[Kotter's Change Model](../frameworks/kotter-change-model.md)** -- Kotter's eight-step framework for leading change maps directly onto the organisational transformation required by AI adoption. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- The daily habits of operating at strategic altitude are essential for translating AI vision into actionable organisational alignment. diff --git a/plugins/foreman/content/skills/creative/creative-collaboration-and-context.md b/plugins/foreman/content/skills/creative/creative-collaboration-and-context.md new file mode 100644 index 0000000..3189fae --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-collaboration-and-context.md @@ -0,0 +1,216 @@ +--- +name: "creative-collaboration-and-context" +description: "Explores how creative collaboration produces outcomes neither + party could achieve alone, covering reference points without copying, the role + of creative mythology, the prism of self as competitive advantage, context as + meaning-maker, cross-domain adaptation, and translation as a creative act. Use + when building creative partnerships, navigating co-founder dynamics, + assembling creative teams, repositioning a product through context change, + adapting business models across industries, translating technical innovation + for new markets, or understanding why the same idea succeeds in one context + and fails in another." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - collaboration + - context + - adaptation + - translation + - point-of-view + - reference + - creative-teams + - positioning +related_skills: + - creative-shaping-and-craft + - creative-flow-and-inspiration + - creative-completion-and-renewal +author: "Fatih Guner" +related_content: + - kind: template + ref: stakeholder-map +--- + +# Collaboration and Context + +Every collaboration is a prism. A single beam of light enters -- the shared problem, the market opportunity, the creative brief -- and a spectrum emerges. The colours that exit bear no resemblance to the monochrome that entered. "The 'self' has many distinct aspects," the text observes. "Creativity is an internal discussion between these aspects of self." When two or more creators bring their distinct prisms into contact, the refraction compounds. the book's deeper claim is that collaboration is not merely additive: "Nothing begins with us." All creative work is already a collaboration -- with prior art, with the culture, with the tools, with the audience, and with the multiple selves inhabiting the single creator. Understanding this transforms the entrepreneur's relationship with partnership, influence, positioning, and the act of carrying ideas across boundaries. + +--- + +## The Framework + +Seven principles compose the book's philosophy of creative collaboration and context. They range from the interpersonal to the structural, from the way two minds interact to the way a single idea changes meaning when it crosses a border. + +### 1. Collaboration -- The Internal and External Dialogue + +the text begins not with teamwork but with a provocation: the creator is already a committee. "There are many different hats the artist wears, and creativity is an internal discussion between these aspects of self. The negotiation continues until the selves create the best work they can together." The inspired-artist self and the craftsperson self are often in conflict. The visionary and the operator, the risk-taker and the risk-manager -- each entrepreneur carries this parliament. + +External collaboration, then, is an extension of internal collaboration, with one critical addition: the collaborator introduces a filter the creator does not possess. the text notes that even the audience participates in the creative act: "You could have a distinct idea of what a piece means, how it functions, or why it's pleasing -- and someone else can like it or dislike it for an entirely different reason." The purpose of sharing work is not alignment of interpretation but magnitude of charge: "We can only hope that the magnitude of the charge we experience reverberates as powerfully for others as it does for us." + +For the entrepreneur, this reframes co-founder dynamics, advisory relationships, and team composition. The value of a collaborator is not agreement but refraction -- the capacity to produce colours the founder cannot produce alone. + +### 2. Point of Reference -- Using Without Copying + +Exposure to others' work is inevitable and necessary. The question is how to absorb influence without becoming derivative. the text observes that encountering radically new work often provokes initial rejection: "If you're looking for solutions to a problem, you may react in a strongly negative way to an option that springs forth. This can be when the idea is so new that you don't have any context for it." + +The instruction is to linger with strong reactions rather than fleeing them. "Be aware of strong responses. If you're immediately turned off by an experience, it's worth examining why. Powerful reactions often indicate deeper wells of meaning." The competitive product that irritates, the customer request that seems absurd, the market trend that feels alien -- each may be a reference point pregnant with unrecognised value. + +Revolutionary ideas, the text notes, "have no context. They invent their own." The entrepreneur who can tolerate the discomfort of context-free ideas -- sitting with them long enough for the brain to build new patterns -- will see opportunities invisible to those who reject the unfamiliar on contact. + +### 3. Apocrypha -- The Stories We Tell About Creation + +Every industry has its origin myths. The garage startup. The napkin sketch that became a billion-dollar company. The founder who coded the MVP in a weekend. the text is disarmingly frank about such stories: "The stories about how works get made and the rituals of the artists who make them are generally exaggerated, and often pure fiction." + +This matters for the entrepreneur because creative mythology shapes creative behaviour. The founder who believes great products require a single visionary genius will structure their company differently from one who believes great products emerge from messy collaboration. Both beliefs are apocryphal -- simplified narratives overlaid on processes too complex to fully describe. "In cases when the artist thinks they know, their interpretation may not be accurate or the whole story." + +The practical counsel: absorb creative mythology for energy and inspiration, but do not mistake it for a reproducible method. "To believe a specific method is responsible for the quality of a work is misleading. Especially if it causes you to repeat that process in hopes of achieving a similar result." + +### 4. The Prism of Self -- Your Unique Lens as Value + +"We inhabit many different versions of a changing self," the text argues. The self is not a fixed point but a prism: "Neutral events enter, and are transformed into a spectrum of feelings, thoughts, and sensations. All this information is processed distinctively by each aspect of self, refracting life's light in its own way, and emitting different shades of art." + +For the entrepreneur, this means personal perspective is not a liability to be managed or a bias to be eliminated. It is a competitive advantage. Two founders looking at the same market will see different opportunities, not because one is smarter, but because their prisms refract differently. "Not every work can reflect all of our selves," the text acknowledges. The practice is to embrace the prism rather than attempting to grind it into a neutral lens. + +The kaleidoscope metaphor extends to teams: "Like a kaleidoscope, we can adjust the aperture on our vision and change the results." A team composed of similar prisms produces monochrome output. A team of diverse prisms produces a spectrum -- provided the environment allows each prism to refract freely rather than conforming to a single sanctioned lens. + +### 5. Context -- The Frame Changes the Painting + +"Imagine a flower in an open meadow," the text argues. "Now take the same flower and slip it into the barrel of a rifle. Or place it on a gravestone. Notice in each case how you feel. The significance changes." His principle is absolute: "The context changes the content." + +This single insight has profound implications for product strategy, positioning, and market entry. The identical product launched at a different time, in a different market, alongside different competitors, at a different price point, is a different product. Andy Warhol's Brillo boxes in a grocery store are packaging; in a museum, they are art. The startup that repositions an existing technology from enterprise to consumer (or the reverse) is not merely changing the customer. It is changing the meaning of the product. + +the text offers a practical catalogue of contextual pairs -- soft/loud, fast/slow, high/low, close/far, bright/dark, large/small -- and advises: "When a piece isn't living up to your expectations, consider changing the context. Look past the principal element, examine the variables around it." + +### 6. Adaptation -- Practice, Absorption, and Growth + +Adaptation, in this framework, is not strategic flexibility but something more organic. He describes the phenomenon of practising a skill, resting, and returning to find the skill has mysteriously improved: "You wake up one morning, transported to this new reality where you suddenly have more skill than you did before you went to sleep." + +The entrepreneurial parallel is the assimilation of market knowledge. The founder who immerses deeply in a customer segment, then steps away to work on something else, often returns with insights that immersion alone could not produce. the text frames this as a cycle: "Practice gets us part of the way there. Then it takes time for practice to be absorbed into the body." The passive element of adaptation is as important as the active one. + +At a broader level, adaptation describes the transfer of capability across domains. "Teaching yourself to play piano will likely improve your hearing. And you may well get better at math." The entrepreneur whose previous career was in an unrelated field carries skills that are not obsolete but untranslated. The act of translation is itself creative. + +### 7. Translation -- Carrying Fire Across Borders + +"Art is an act of decoding," the text argues. "We receive intelligence from Source, and interpret it through the language of our chosen craft." Translation is the creative act of converting insight from one domain into expression within another. + +Every market entry is a translation. The product designed for developers, rewritten for healthcare administrators. The business model that works in logistics, adapted for education. The founder who has deep expertise in one domain and enters another is not starting from zero -- they are translating. + +the text notes that fluency matters: "The more we develop, expand, and sharpen our skills, the more fluent we become." But he also cautions that technical mastery is neither necessary nor sufficient: "A guitarist could play the most complex solo and while technically impressive, it might not connect emotionally, while an amateur could perform a simplistic three-chord song and move you to tears." The quality of translation depends not on sophistication but on the integrity of what is being translated. + +--- + +## Prompts + +**Prompt 1 -- Collaboration Audit:** +> Map the internal and external collaborations in my venture. Internally: which aspects of my own thinking are in productive tension (visionary vs. operator, risk-taker vs. risk-manager)? Externally: who are my current collaborators (co-founders, advisors, team members, customers), and what unique prism does each bring? Where am I surrounded by similar prisms, and where is the spectrum missing a colour? Recommend specific additions or shifts to maximise creative refraction. + +**Prompt 2 -- Context Reframe:** +> My product [describe product] is currently positioned in [describe context: market, price point, customer segment, competitive frame]. Apply the book's principle that "the context changes the content." Generate five alternative contextual frames -- different markets, adjacent use cases, different price positions, different competitive reference sets -- and describe how each changes the perceived meaning of the same product. Which reframe surfaces the most underexploited value? + +**Prompt 3 -- Translation Exercise:** +> I have deep expertise in [domain A] and am building a product for [domain B]. Identify the core principles, methods, and mental models from domain A that are most translatable to domain B. For each, describe the translation -- not a direct copy, but an adaptation that honours the original insight while fitting the grammar of the new domain. Where does my domain A expertise give me a perspective that native domain B participants cannot see? + +**Prompt 4 -- Apocrypha Audit:** +> What origin stories and creative mythologies am I operating under? [Describe beliefs about how great products get built, what successful founders look like, what process produces breakthroughs.] For each, apply the book's warning that these stories are "generally exaggerated, and often pure fiction." What would my strategy look like if I abandoned each mythology and replaced it with an honest assessment of what I actually know about how my best work has been produced? + +--- + +## Use Cases + +**Idea-stage co-founders with misaligned creative visions** + +Two co-founders -- one a designer, one an engineer -- disagree on the product's direction. The designer wants to pursue an unconventional user interface; the engineer argues for convention because it reduces development time. Viewed through the book's collaboration framework, the disagreement is not a problem to be resolved but a productive tension to be held. The designer's prism refracts toward novelty; the engineer's toward reliability. The intervention is not to choose one vision but to let both prisms operate: prototype the unconventional interface cheaply (honouring the designer's filter) while building it on the most conventional backend possible (honouring the engineer's filter). The product that emerges carries both colours -- innovative where the customer sees it, robust where the customer does not. + +**Validation-stage product receiving contradictory market signals** + +A founder testing a B2B product receives enthusiastic responses from small businesses but indifference from the enterprise segment originally targeted. Applying the context principle, she recognises that the same product has different meanings in different contexts: in the small business context, it fills a painful gap; in the enterprise context, it duplicates existing tooling. Rather than dismissing the small business signal as off-strategy, she examines the contextual frame that makes the product valuable there and repositions accordingly. The product itself changes minimally; the context changes everything. + +**Growth-stage company adapting a model across geographies** + +A SaaS platform successful in North America is expanding to Southeast Asia. The temptation is direct replication. Applying the book's translation principle, the leadership team recognises that market entry is creative translation, not mechanical copying. They identify the core principles that drove success in North America (the "essence" that survives translation) and the surface-level features that were context-dependent (pricing structure, onboarding flow, support model). The Southeast Asian launch preserves the principles while reinventing the surface -- and discovers that some of the reinventions improve the original product. + +--- + +## Anti-Patterns + +**Seeking collaborators who confirm rather than refract.** The most common collaboration error is assembling a team of similar prisms. The result is comfortable and coherent -- and monochrome. the book's framework values the discomfort of unfamiliar refraction. If every collaborator sees the product the same way, the collaboration is producing no spectrum. + +**Copying reference points instead of metabolising them.** There is a difference between studying a competitor's approach and cloning it. the book's guidance on point of reference is to let influence enter, be processed through one's own prism, and emerge transformed. The entrepreneur who reproduces a competitor's feature set has skipped the metabolic step. What emerges is imitation, not translation. + +**Treating apocrypha as instruction manuals.** The origin story of a successful company is a narrative constructed after the fact, not a recipe. The founder who copies another company's process because they read about it in a case study is, in the book's terms, confusing art history with art reality. "Art reality is forever unknown." + +**Ignoring context while optimising content.** The product team that obsesses over feature quality while neglecting positioning, timing, competitive frame, and market context is painting a masterpiece and hanging it in a broom closet. Context is not secondary to content. It is constitutive of it. + +**Assuming adaptation is immediate.** the text describes adaptation as a process that includes a necessary "recovery phase." The founder who enters a new market expects instant fluency and interprets the initial awkwardness as failure rather than as the natural struggle phase that precedes the leap. "Practice gets us part of the way there. Then it takes time for practice to be absorbed into the body." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder prism alignment; initial context selection | The founding team's combined prisms determine which spectrum of opportunity is visible; context choice (which market, which frame) is the most consequential creative decision at this stage | +| Validation | Metabolising market reference points; absorbing contradictory signals | The market provides reference points that may initially provoke rejection; the practice is to sit with strong reactions rather than dismissing unfamiliar data | +| Early Traction | Translation of founding insight into scalable form; team prism diversity | The original insight must be translated from founder-intuition into product-language that a team can execute; hiring for prism diversity becomes critical | +| Growth | Context management across segments and geographies; adaptation cycles | The same product means different things in different contexts; managing this multiplicity without losing essence is the central challenge | +| Scale | Apocrypha management; preventing the company's own origin story from becoming a cage | The company's founding mythology can calcify into doctrine; the practice is to honour the story's energy while refusing its authority as method | + +At early traction, the translation challenge is acute. The founder's intuitive understanding of the product must be encoded in language, processes, and specifications that others can execute without losing the original charge. This is the moment when the book's observation that "there is no direct conversion from abstract thought to the material world" becomes most visible. Every handoff -- from founder to designer, from designer to engineer, from engineer to customer -- is an act of translation, and each translation carries the risk of losing essential signal while preserving inessential form. + +--- + +## Output Template + +```markdown +# Collaboration and Context Analysis -- [Project/Product Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Prism Map + +| Collaborator | Role | Unique Lens/Filter | Blind Spots | Refraction Value | +|-------------|------|-------------------|-------------|-----------------| +| [Name] | [Role] | [What they see that others miss] | [What they consistently overlook] | [What their presence adds to the spectrum] | + +## Spectrum Gaps +[Perspectives, backgrounds, or cognitive styles missing from the current team] + +## Context Analysis + +| Contextual Variable | Current Setting | Alternative Setting | Meaning Change | +|--------------------|-----------------|--------------------|--------------------| +| Market segment | [Current] | [Alternative] | [How meaning shifts] | +| Price position | [Current] | [Alternative] | [How meaning shifts] | +| Competitive frame | [Current] | [Alternative] | [How meaning shifts] | +| Timing | [Current] | [Alternative] | [How meaning shifts] | + +## Translation Log +[For cross-domain moves: what transfers, what must be reinvented] +- **Principle that translates:** [Principle] -- Adaptation: [How it changes] +- **Surface feature that does not translate:** [Feature] -- Replacement: [New approach] + +## Apocrypha Check +[Creative mythologies currently influencing decisions -- flagged for examination] +1. [Myth] -- Source: [Where it came from] -- Risk: [How it constrains] + +## Collaboration Design Recommendations +[Specific changes to team composition, collaboration structure, or context] +``` + +--- + +## Related Skills + +- **[Creative Shaping and Craft](creative-shaping-and-craft.md)** -- Shaping operates on the output of collaboration; the prism metaphor extends from person to process, where each shaping technique refracts the work differently. +- **[Creative Flow and Inspiration](creative-flow-and-inspiration.md)** -- Collaboration is one of the richest environments for creative surprise; other people's prisms produce the unexpected input that serves as a precondition for inspiration. +- **[Creative Completion and Renewal](creative-completion-and-renewal.md)** -- Collaborative work faces distinct completion challenges, including the negotiation between multiple selves and the courage to release work no single collaborator fully controls. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- The team dynamics that shape creative collaboration are governed by the same personality, trust, and norm-building principles that apply to any high-performing team. +- **[Hackman's Enabling Conditions](../frameworks/hackman-enabling-conditions.md)** -- The structural conditions for team effectiveness apply to creative teams; clear direction, adequate resources, and supportive context determine whether collaboration produces insight or friction. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Creative collaboration requires the safety to share half-formed ideas without judgment; Edmondson's framework explains why some teams generate creative breakthroughs while others self-censor. diff --git a/plugins/foreman/content/skills/creative/creative-completion-and-renewal.md b/plugins/foreman/content/skills/creative/creative-completion-and-renewal.md new file mode 100644 index 0000000..7738fa7 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-completion-and-renewal.md @@ -0,0 +1,219 @@ +--- +name: "creative-completion-and-renewal" +description: "Addresses the hardest creative act -- finishing and releasing work -- covering the tension between experimenter and finisher mindsets, making choices when everything feels possible, accepting shades rather than absolutes, ending projects to begin anew, approaching new work with a clean slate, knowing when to stop refining, and recognising the energy living inside completed work. Use when struggling to ship a product, paralysed by perfectionism, unable to choose between competing directions, managing the transition between projects, deciding when a product version is ready for release, or recovering creative momentum after a major launch." +version: "1.0.0" +category: "creative" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - completion + - perfectionism + - shipping + - decision-making + - renewal + - release + - creative-energy + - finishing +related_skills: + - creative-shaping-and-craft + - creative-flow-and-inspiration + - creative-collaboration-and-context +author: "Fatih Guner" +--- + +# Completion and Renewal + +The hardest creative act is not starting. Starting is cheap, intoxicating, and abundant. The hardest creative act is releasing -- declaring a thing finished when every instinct whispers that one more pass, one more feature, one more revision could make it perfect. the text states the matter with characteristic quiet: "The only art the world gets to enjoy is from creators who've overcome these hurdles and released their work. Perhaps still greater artists existed than the ones we know, but they were never able to make this leap." The graveyard of entrepreneurship is not filled with bad ideas. It is filled with unreleased products, unshipped features, and unlaunched ventures -- work that was perpetually almost ready. Completion demands a different muscle than creation. And renewal -- the act of beginning again with a clean slate after the release -- demands a different muscle still. + +--- + +## The Framework + +the book's philosophy of completion and renewal unfolds across eight interconnected principles, each addressing a distinct failure mode in the transition from making to releasing to making again. + +### 1. The Completion Threshold + +"When is the work done?" the text asks. "There is no formula or method for finding this answer. It is an intuition: The work is done when you feel it is." This radical subjectivity is precisely what makes completion so difficult. There is no external checklist that certifies readiness. The entrepreneur must develop an internal signal -- analogous to the book's "ecstatic" compass -- that distinguishes between "not yet ready" and "resisting release." + +the text acknowledges the Completion phase is non-linear. Preparing work for release may reveal gaps that require returning to craft or experimentation: "You may realize there's more to be done. A revision, an addition, a deletion. So you step back to Craft or Experiment, and work your way forward once more." The discipline is distinguishing between genuine gaps and invented ones -- between the revision that serves the work and the revision that delays its release. + +A useful pragmatic principle surfaces: "Art doesn't get made on the clock. But it can get finished on the clock." Deadlines that are imposed too early suffocate creative work. Deadlines imposed during the completion phase focus it. + +### 2. The Experimenter and the Finisher + +the text identifies two creative temperaments that exist on a spectrum within every creator: + +**Experimenters** live in the discovery phases. They generate options, explore alternatives, resist closure. "Finding it more difficult to complete and release their work." + +**Finishers** move to resolution with speed and certainty. "They are less interested in exploring the possibilities and alternatives that the Experimentation and Craft phases can suggest." + +Neither temperament is superior. Each carries a characteristic failure mode: the Experimenter produces endlessly refined prototypes that never ship; the Finisher ships products that have not been explored deeply enough. the book's counsel to each is to borrow from the other. Finishers should "allow themselves space for improvisation and surprise." Experimenters should "take an aspect of the work through to completion" -- even a small one -- because "completing even a small segment builds confidence." + +The entrepreneurial implication is direct. The founder who has been in "stealth mode" for eighteen months, refining the product without shipping, is operating from the Experimenter pole. The founder who ships a barely functional MVP every two weeks without learning from any of them is operating from the Finisher pole. Growth requires movement toward the centre. + +### 3. How to Choose -- Decision-Making When Everything Is Possible + +Every creative project is "a tree with many branches. At each fork, we can go in any number of directions, and our choice will alter the final result. Often radically." the book's method for navigating these forks is deliberately anti-intellectual. + +The A/B test is the primary tool: place two options side by side, limit the comparison to two, and observe which produces a pull. "More often than not, there will be a clear draw toward one." When the draw is ambiguous, the text recommends the coin-toss method -- not to decide randomly, but to surface unconscious preference: "When the coin is spinning in the air, you'll likely notice a quiet preference or wish for one of the two to come up. Which are you rooting for? This is the option to go with." + +The deeper principle: "The goal is to turn off the conscious mind and follow our impulses. Children are exceptionally good at this." The instinctual first response, before analysis distorts it, tends to be the truest signal. The entrepreneur who convenes a three-hour meeting to choose between two product directions when she knew her preference within the first thirty seconds is not being thorough. She is being afraid. + +### 4. Shades and Degrees -- Accepting Disproportionality + +Creative work refuses clean proportionality. "Two seeds of inspiration might seem indistinguishable, but one may yield volumes and the other little to nothing." Enormous effort may produce marginal results; a tiny adjustment may transform the entire work. "We make one dab of the brush, one tweak in the mix -- and suddenly the work jumps from being halfway done to complete." + +For the entrepreneur, this principle invalidates the assumption that effort and outcome scale linearly. The feature that took three months to build may matter less than the one-line copy change completed in an afternoon. The strategic pivot that required a single conversation may prove more consequential than the twelve-month roadmap it replaced. Accepting this disproportionality is a prerequisite for recognising when the work is done: sometimes the last thing needed is microscopic. + +### 5. Ending to Start Anew -- The Regeneration Cycle + +Carl Jung built a round tower because he saw "life in the round as something forever coming into being and passing on." the text applies the same cyclical logic to creative work: "We participate in this by completing one project so that we can start anew. As in life, each ending invites a fresh beginning." + +The entrepreneur who cannot release a product because it has become their identity is disrupting the regeneration cycle. "When consumed with a single work to the degree that we believe it's our life's mission, there's no room for the next one to develop." Releasing the work is not an act of abandonment. It is an act of creation -- it creates the space for what comes next. + +"Sharing art is the price of making it," the text argues. "Exposing your vulnerability is the fee." The product launch, the public beta, the investor demo -- each is a moment of exposure that the entrepreneur cannot avoid without halting the cycle entirely. + +### 6. Clean Slate -- Seeing the Work Anew + +"After spending thousands of hours working on a piece, it's difficult to judge it from a neutral place. When someone experiences the work for the first time, after only two minutes they may see it more clearly than you do." Proximity breeds blindness. the book's practice of cleaning the slate is the discipline of re-encountering one's own work as a stranger would. + +The concrete method is telling. When reviewing a mix, the text makes a list of notes, has someone else implement them, then discards the list entirely. On the next listen, he starts fresh. "Listen as if for the first time and begin a new list of notes from scratch." The ego says: "I wanted this change, I got it, so it's a problem solved." The clean-slate practice says: forget what you wanted. Is it better? + +For the entrepreneur, the clean-slate discipline applies to product reviews, pitch deck revisions, and strategic plans alike. The founder who reviews a revised pitch by checking whether each requested change was implemented is following the ego. The founder who reads the revised pitch as though encountering it for the first time is practising the clean slate. + +the text recommends stepping away entirely when judgement is impaired: "Let it sit for a minute, a week, or longer, while you go get lost." Time is the primary tool. "Time is where learning occurs. Unlearning as well." + +### 7. Let It Be -- The Courage of Non-Intervention + +"First, do no harm," the text argues, borrowing the physician's oath. Sometimes the most valuable intervention is none at all. "Sometimes the most valuable touch a collaborator can have is no touch at all." + +For the entrepreneur, this principle applies to the late stages of product development -- the moment when additional refinement begins to erode rather than enhance. The feature that was perfect in its rough state but was polished until its energy dissipated. The pitch deck that was compelling in its first draft and was revised into blandness through seventeen rounds of feedback. Knowing when to stop refining is as much a creative skill as knowing how to refine. + +### 8. The Energy in the Work -- Following the Charge + +"What motivates us to work so diligently?" the text asks. "This energy is not generated by us. We are caught by it. We picked it up from the work. It contains the charge." The completed work possesses its own energy -- a "contagious vitality" that either pulls the creator forward or fails to. + +This energy is the ultimate diagnostic for completion and for the decision of what to work on next. "Early in a project, excitement is the inner voltmeter to watch." When the voltmeter reads high, the work is alive. When it flatlines despite effort -- "you're so deep in the details that you can't see the bigger picture" -- the creator has either taken a wrong turn or exhausted what this particular work has to offer. + +"One of the skills an artist develops is the ability to recognize when either they or the work have nothing left to give each other." For the entrepreneur, this is the skill of knowing when to ship the current version and when to shelve a product entirely. Both decisions require the same internal voltmeter. + +--- + +## Prompts + +**Prompt 1 -- Completion Diagnosis:** +> I have been working on [describe product/project] for [timeframe] and cannot bring myself to ship/release/launch it. Diagnose the blockage using the book's framework: Am I genuinely in the craft phase with legitimate work remaining, or am I in the completion phase and resisting release? What specific fears or stories am I telling myself that prevent letting go? If there are genuine gaps, identify them concretely. If the resistance is psychological, name it and propose a path through it, including a specific release date. + +**Prompt 2 -- Experimenter/Finisher Calibration:** +> Assess my entrepreneurial pattern: do I tend toward the Experimenter pole (endless refinement, difficulty shipping, multiple projects in perpetual progress) or the Finisher pole (rapid shipping, insufficient exploration, premature closure)? Based on my history: [describe 3-5 past projects and their outcomes]. Recommend specific practices to borrow from the opposite pole. What would an Experimenter do differently if they borrowed the Finisher's discipline? What would a Finisher gain from the Experimenter's patience? + +**Prompt 3 -- Clean Slate Review:** +> I need to evaluate [describe product, pitch, strategy document] with fresh eyes. I have been too close to it for too long. Act as a first-time viewer who has never encountered this work before. Describe what you notice -- what is clear, what is confusing, what generates energy, what feels dead. Do not check my changes against my stated intentions. Respond only to what is actually there. Then provide a new list of observations, starting from zero. + +**Prompt 4 -- Regeneration Planning:** +> I am about to release [describe project] and need to plan the transition to what comes next. Based on the book's regeneration cycle, help me: (1) identify the specific fears or attachments preventing me from finalising the release, (2) design a clean break ritual -- a concrete action that marks the end of this project, (3) create conditions for renewal -- what practices will open space for the next creative cycle to begin, and (4) identify the seeds of the next project that are already generating energy. + +--- + +## Use Cases + +**Validation-stage founder trapped in perpetual beta** + +A solo founder has been running a "private beta" for fourteen months. The product works. Users who have access report genuine value. Yet the founder continues to add features, fix edge cases, and delay the public launch. Diagnosing through the book's framework: the founder is an Experimenter who has conflated craft with completion. The product entered the completion phase months ago, but the founder keeps returning to the craft phase to avoid the vulnerability of release. The intervention is twofold: set a non-negotiable launch date three weeks out (the book's principle that art can be finished on the clock), and begin actively planning the next project. The energy of the next project -- the book's "excitement of what's coming next" -- provides the forward momentum to release the current one. + +**Early-traction team unable to choose between product directions** + +A product team has generated three viable product directions from customer research. Each has strong advocates. Weeks of analysis have not produced consensus. Applying the book's decision-making method, the team runs a structured exercise: for each pair of options, team members record their gut reaction within ten seconds, before any discussion. The results reveal a clear preference that the analytical process had obscured. The chosen direction, predictably, is the one the product lead had favoured from the first meeting but had been afraid to champion without analytical cover. + +**Growth-stage company struggling with post-launch renewal** + +A company has shipped its most ambitious product release after a year of development. The launch was well received, but the team is depleted and directionless. The CEO recognises this as the book's post-completion vacuum -- the energy that sustained the project has been expended, and renewal has not yet begun. She institutes a two-week clean-slate period: no product planning, no roadmap discussions. Team members engage in unrelated creative activities (the prescribed "go get lost"). At the end of the period, the team reconvenes with fresh eyes and generates the seed ideas for the next cycle, which prove more original than anything produced during the preceding exhausted months. + +--- + +## Anti-Patterns + +**Perfectionism disguised as quality standards.** the text identifies the pattern precisely: "We find flaws that don't really exist. We make inconsequential changes. We sense the distant mirage of some better creative option that hasn't been discovered yet." The entrepreneur who cannot ship because the product "isn't ready" should ask: ready by whose standard, and is that standard serving the work or protecting the founder from exposure? + +**Perpetual experimentation as a substitute for commitment.** The serial pivoter who starts a new direction every quarter has elevated the Experimenter pole to a lifestyle. the text is direct: "The first two phases have little purpose or meaning on their own. Art may only exist, and the artist may only evolve, by completing the work." Ideas that are never completed generate no value and no learning. + +**Finishing on the clock from the beginning.** Deadlines are a tool for the completion phase, not the creation phase. The startup that imposes sprint deadlines on exploratory work produces predictable, timid output. the book's timing principle is specific: deadlines help when "the work is close to completion," not when it is still searching for its form. + +**Skipping the clean slate after major revisions.** The product team that evaluates a revised product by checking a list of requested changes -- rather than experiencing the revised product afresh -- is confirming its own decisions rather than evaluating the work. The ego's checklist ("did we implement what we said we would?") is not the same as the clean-slate question ("is it better?"). + +**Refusing renewal because the last project was successful.** Success is as dangerous as failure for the regeneration cycle. The company that keeps extending a successful product rather than beginning something new risks the condition the text describes: "When consumed with a single work to the degree that we believe it's our life's mission, there's no room for the next one to develop." Even beloved products have a natural cycle. The willingness to end and begin again is what sustains the creative organisation across decades. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Committing to one seed over many; the Finisher's discipline of choosing | The danger is infinite exploration without commitment; even selecting a seed to develop is a completion act | +| Validation | Shipping imperfect versions; accepting shades rather than absolutes | The MVP is a completion exercise -- releasing work that is deliberately not finished, which requires overcoming the Experimenter's resistance to imperfection | +| Early Traction | Choosing between product directions; A/B decision-making at speed | The company must make consequential choices with incomplete information; the coin-toss method is not flippant -- it surfaces the intuition that analysis obscures | +| Growth | Post-launch renewal; clean-slate transitions between major releases | The organisational challenge is managing the energy cycle: depletion after major efforts and deliberate renewal before the next phase | +| Scale | Knowing when to let a product line be; ending to start anew at the portfolio level | At scale, the hardest completion act is ending a product or business unit that was once successful -- the organisational equivalent of releasing a work into the world | + +The validation stage is where completion discipline has its highest entrepreneurial leverage. The lean startup methodology (see lean startup methodology) provides the structural rationale for releasing imperfect work: build, measure, learn. the book's contribution is the emotional and psychological dimension that lean methodology underserves. The founder knows intellectually that shipping an MVP is correct. The question the text addresses is why it feels impossible -- and what internal practices make it bearable. + +At scale, completion becomes an organisational capability. The company that can end projects decisively -- without the months of zombie-state continuation that drains resources and morale -- possesses a competitive advantage that no amount of strategic planning can substitute. The energy freed by honest completion flows into the next cycle of creation. + +--- + +## Output Template + +```markdown +# Completion and Renewal Assessment -- [Project/Product Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Completion Status +- **Phase:** [Craft / Completion / Resisting release] +- **Time in current phase:** [Duration] +- **Legitimate remaining work:** [Specific items, if any] +- **Suspected avoidance behaviours:** [List] + +## Experimenter/Finisher Profile +- **Dominant tendency:** [Experimenter / Finisher / Balanced] +- **Evidence:** [Specific patterns from past projects] +- **Borrowing practice:** [What to borrow from the opposite pole] + +## Decision Log +| Decision Point | Options | Gut Response (10 sec) | Analytical Preference | Final Choice | +|---------------|---------|----------------------|----------------------|--------------| +| [Fork] | [A vs B] | [Which pulled] | [Which analysis favoured] | [Which was chosen] | + +## Energy Voltmeter +- **Current charge level:** [High / Medium / Low / Flatlined] +- **Last moment of genuine excitement:** [When and what triggered it] +- **Diagnosis:** [On track / Wrong turn / Exhausted mutual value] + +## Release Plan +- **Release date:** [Date -- non-negotiable] +- **Remaining actions:** [Numbered, specific, time-bound] +- **Fears to name and release:** [List] +- **"Let it be" items:** [Things to stop refining] + +## Renewal Conditions +- **Clean-slate period:** [Duration after release] +- **Renewal practices:** [Specific activities] +- **Seeds for next cycle:** [Ideas already generating energy] +``` + +--- + +## Related Skills + +- **[Creative Shaping and Craft](creative-shaping-and-craft.md)** -- Craft precedes completion; the shaping skill provides the methods for refining work to the point where the completion question becomes relevant. +- **[Creative Flow and Inspiration](creative-flow-and-inspiration.md)** -- The energy that sustains completion often originates in the inspiration that initiated the project; renewal depends on reconnecting with the conditions for fresh inspiration. +- **[Creative Collaboration and Context](creative-collaboration-and-context.md)** -- Sharing near-complete work with others is the method for seeing it anew; collaboration in the completion phase serves a diagnostic rather than generative function. +- **[Creative Obstacles](creative-obstacles.md)** -- The final stretch of any creative project intensifies self-doubt and perfectionism; the obstacle-clearing techniques are most needed when completion pressure is highest. +- **[Revising and Editing](../writing/revising-and-editing.md)** -- The revision discipline provides the structured methodology for the refinement phase that precedes release, applicable to any creative output that involves written form. +- **[Stoic Acceptance and Amor Fati](../stoic/stoic-acceptance-amor-fati.md)** -- The courage to release imperfect work requires the Stoic acceptance that perfection is unattainable and that completion serves a higher purpose than endless refinement. diff --git a/plugins/foreman/content/skills/creative/creative-flow-and-inspiration.md b/plugins/foreman/content/skills/creative/creative-flow-and-inspiration.md new file mode 100644 index 0000000..0e2f6d6 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-flow-and-inspiration.md @@ -0,0 +1,217 @@ +--- +name: "creative-flow-and-inspiration" +description: "Teaches the experiential practice of courting creative inspiration, sustaining openness, creating conditions for breakthrough ideas, staying in creative mode continuously, harnessing spontaneity, practising connected detachment, and using play as a serious creative method. Use when seeking breakthrough product ideas, preparing for creative sessions, diagnosing why innovation has stalled, designing environments for creative teams, recovering creative energy after burnout, or cultivating the founder's capacity for original thinking under pressure." +version: "1.0.0" +category: "creative" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - inspiration + - flow + - creativity + - openness + - spontaneity + - play + - detachment + - innovation +related_skills: + - creative-shaping-and-craft + - creative-completion-and-renewal + - creative-collaboration-and-context + - flow-state +author: "Fatih Guner" +--- + +# Flow and Inspiration + +You cannot catch lightning. But you can stand in the field where storms gather, at the hour when the air turns electric, wearing the right shoes, holding the right rod. The text's approach to creative inspiration operates on precisely this principle: "While we can't command a lightning bolt's arrival, we can control the space around it. We accomplish this by preparing beforehand and honoring our obligation to it afterward." This is not mysticism dressed in studio jargon. It is a pragmatic philosophy about preparing the conditions under which breakthrough ideas are most likely to arrive -- and doing the unglamorous work that follows when they do. Csikszentmihalyi's flow-state research (see `flow-state`) maps the neurochemistry and structural conditions for sustained deep performance. the book's contribution is different in kind: not the science of flow but the lived practice of courtship with the unpredictable. Where Csikszentmihalyi provides the thermostat, the text teaches you to read the weather. + +--- + +## The Framework + +the book's philosophy of creative inspiration is not a linear method. It is a constellation of interrelated practices that, taken together, constitute a way of being rather than a way of doing. Seven dimensions form the constellation. + +### 1. Inspiration -- Emptying to Receive + +The Latin root of "inspiration" -- inspirare, to breathe in -- contains the entire philosophy. "For the lungs to draw in air, they must first be emptied. For the mind to draw inspiration, it wants space to welcome the new." Inspiration is not something the entrepreneur generates through effort. It is something that enters when space has been cleared. + +The practical implication is counterintuitive. The founder buried under Slack messages, investor updates, and sprint reviews has no empty space for new ideas to occupy. the text recommends "practices of quieting the mind: meditation, awareness, silence, contemplation" -- not as wellness initiatives but as instruments of creative production. The vacancy draws the muse. + +Yet the text is no romantic. "An artistic life cannot be built solely around waiting. Inspiration is out of our control and can prove hard to find. Effort is required and invitations are to be extended." The practice is bilateral: clear space and do the work. Neither alone is sufficient. + +### 2. Expecting Surprise -- Surrender as Method + +"Some of our most interesting artistic choices come about by accident," the text observes. "Springing from moments of communion with the work, when the self disappears." These apparent mistakes are "the subconscious engaged in problem-solving" -- a deeper intelligence overriding conscious intention. + +The method, such as it is, consists of releasing control. "Set aside the outline, write with no map, and see what happens. The premise you start with could develop into something more. Something you couldn't have planned." For the entrepreneur, this translates to strategic experimentation without predetermined outcomes. The product feature that emerges from unstructured user observation may prove more valuable than the one specified in the quarterly roadmap. The business model that surfaces during a failed pivot may be superior to both the original model and the intended pivot target. + +The deepest surprise, the text suggests, is self-trust: "You learn to trust yourself -- in the universe, with the universe, as a unique channel to a higher wisdom." + +### 3. Radical Openness -- Softening the Filter + +"Our minds seek rules and limits," the text argues. "In attempting to navigate a large, uncertain world, we develop beliefs that give us a coherent framework, reduced options, and a false sense of certainty." Openness is the deliberate softening of this filter -- not to abandon judgement, but to delay it. + +the text urges creators to "purposely experiment past the boundaries of your taste. Examine approaches you may dismiss as too highbrow or lowbrow." When a collaborator's feedback conflicts with one's default setting, the instruction is to "reframe this as an exciting opportunity. Do all you can to see from their perspective." For the founder, this practice is a hedge against the cognitive narrowing that accompanies success. The company that cannot absorb uncomfortable market signals because they conflict with "accepted beliefs of what is and isn't possible" is the company that competitors disrupt. + +When plans fail, the book's counsel is characteristically quiet: "Instead of shutting the project down or expressing frustration, we might consider what else can be done with the materials at hand." + +### 4. Surrounding the Lightning Bolt -- Preparation and Obligation + +This is the central image of the book's inspiration philosophy. Lightning cannot be summoned; conditions for lightning can be created; and lightning, once struck, demands immediate practical response. + +"A more constructive strategy is to focus less on the lightning bolt and more on the spaces surrounding it. The space before, because lightning does not strike unless the right preconditions are met, and the space after, because the electricity dissipates if you do not capture it and use it." + +The "before" space is the daily practice of showing up, staying alert, maintaining readiness. The "after" space is craft -- the unglamorous labour of translating a flash of insight into a finished product. "Without diligence, inspiration alone rarely yields work of much consequence." The entrepreneur who has a breakthrough idea in the shower but returns to email rather than capturing and developing it has failed the obligation. + +Crucially, the text warns against storm-chasing: treating inspiration as the only valid source of creative work. "If lightning doesn't strike, our work need not be delayed." Most creative output comes from showing up and building. The carpenter metaphor is deliberate. + +### 5. Staying In It (24/7) -- Creativity as Ontology + +"Creativity is something you are, not only something you do. It's a way of moving through the world, every minute, every day." the text divides the artist's work into two kinds: the work of doing and the work of being. The second never stops. + +This means perpetual receptivity: "Paying attention and listening. Looking for connections and relationships in the outside world. Searching for beauty. Seeking stories. Noticing what you find interesting, what makes you lean forward." For the entrepreneur, staying in it means the dinner conversation, the airport terminal observation, the unrelated article, the child's question -- all are raw material. The founder who switches off creative attention outside of scheduled brainstorming sessions is working with a fraction of available input. + +### 6. Connected Detachment -- Caring Without Clinging + +"Consider detaching from the story of your life as it's happening," the text argues. The practice is not indifference but perspective: observing events as though watching a film about oneself. "I wasn't expecting that plot twist. I wonder what's going to happen to our hero next." + +For the entrepreneur, connected detachment addresses the emotional volatility of building a company. The failed product launch, the departed co-founder, the lost customer -- each carries real consequence, but identification with those events produces paralysis rather than response. "When we obsessively focus on these events, they may appear catastrophic. But they're just a small aspect of a larger life." The practice is to zoom out: care deeply about the work, release attachment to any single outcome within it. + +This is distinct from detachment as indifference. The founder who does not care is not practising connected detachment; they have disengaged entirely. the book's framework is paradoxical by design: full commitment coupled with radical non-attachment to results. + +### 7. Play -- Seriousness Without Gravity + +"Making art is a serious matter. The opposite is also true. Making art is pure play." the text holds both poles simultaneously. Play is not the absence of rigour; it is rigour stripped of self-consciousness. "In play, there are no stakes. No boundaries. No right or wrong. No quotas for productivity." + +The entrepreneurial application cuts against the cult of intensity. The all-hands meeting conducted as if the company's survival depends on each slide deck is not producing the best ideas in the room. "Putting importance on the work too soon stirs up instincts of caution," the text observes. The team that can experiment without stakes -- where "playtime" is a legitimate operating mode -- produces the adjacent-possible breakthroughs that planning sessions never reach. "Find a clue, follow a lead, remain unattached to what came before." + +### The Ecstatic as Compass + +Across all seven dimensions, one signal guides the creator: the ecstatic. the text describes it as "an arising" -- "a visceral, body-centered reaction, not a cerebral one. It doesn't have to make sense." When a small tweak transforms mediocre work into something that takes the breath away, that somatic response is the compass pointing toward greatness. Entrepreneurs who rely exclusively on data and rational analysis to evaluate creative work miss this signal entirely. The ecstatic is not a replacement for evidence. It is the evidence that precedes measurement. + +--- + +## Prompts + +**Prompt 1 -- Inspiration Conditions Audit:** +> Map the conditions under which my best ideas have historically arrived: [describe 3-5 breakthrough moments, including setting, activity, time of day, emotional state, and what preceded them]. Identify the common preconditions. Then assess my current daily structure against these conditions. Where am I creating space for inspiration, and where am I structurally preventing it? Design a week that "surrounds the lightning bolt" -- protecting the before-space while maintaining productive craft in the after-space. + +**Prompt 2 -- Openness Stress Test:** +> Here are three ideas, feedback items, or market signals I have recently dismissed or resisted: [describe each]. For each, apply the book's radical openness practice: assume the dismissed input contains a valuable signal I cannot yet see. What would that signal be? What would my product, strategy, or team structure look like if I fully incorporated it? I am not committing to any of these -- I am expanding the field of possibility. + +**Prompt 3 -- Connected Detachment Reset:** +> I am currently emotionally entangled with [describe situation: failed launch, difficult co-founder relationship, competitive threat, funding setback]. Apply the book's connected detachment framework: reframe this situation as a plot twist in a story I am watching. What would a detached but caring observer notice about this situation that I cannot see from inside it? What becomes possible in the next scene that was not possible before this plot twist occurred? + +**Prompt 4 -- Play Protocol Design:** +> My team's creative process has become [rigid / formulaic / overly data-driven / risk-averse]. Design a play protocol -- a structured but low-stakes creative session format -- that we can run [weekly / monthly]. The protocol should: eliminate evaluation during the session, introduce an element of genuine surprise, allow ideas to be generated without justification, and produce raw material that the team's "adult" craft mode can later evaluate. Include specific facilitation instructions and a 60-minute session outline. + +**Prompt 5 -- 24/7 Creative Practice:** +> I want to develop the practice of staying in creative mode outside of formal work sessions. Based on the book's principle that "creativity is something you are, not only something you do," design a set of daily micro-practices -- each taking under 5 minutes -- that train perpetual receptivity: noticing patterns, collecting raw material, making unexpected connections. Include a simple capture system so nothing observed is lost. + +--- + +## Use Cases + +**Idea-stage founder seeking a breakthrough concept** + +A serial entrepreneur between ventures has spent three months actively brainstorming next-company ideas. Whiteboards are full, spreadsheets of market analyses run to dozens of tabs, and nothing generates the visceral excitement that preceded her previous two successful launches. Applying the book's framework, she recognises the problem: she is storm-chasing. The "space before" the lightning bolt requires emptying, not filling. She clears her calendar of brainstorming sessions, begins a daily walking practice with no agenda, and replaces market analysis with the 24/7 practice of noticing what makes her lean forward. Six weeks later, during an entirely unrelated conversation at a friend's dinner, the idea arrives fully formed -- an intersection of two domains she had never consciously connected. The "before" space was the six weeks of receptive attention. The "after" space -- three months of intense development -- converts the flash into a funded company. + +**Early-traction team in creative stagnation** + +A product team of twelve has shipped the same product category for two years. Feature releases are competent but predictable. The VP of Product diagnoses the issue through the book's openness lens: the team has built a coherent framework of beliefs about what the product is and is not, and that framework now functions as a cage. She institutes a monthly "opposite day" -- a half-day session where each team member proposes a feature that violates one of the team's implicit rules. The session operates under play conditions: no evaluation, no feasibility analysis, no roadmap implications. Three months in, one of the "impossible" ideas, refined through the subsequent craft process, becomes the company's highest-adoption feature of the year. The idea had been available to anyone on the team; the openness practice created the conditions under which it could be spoken. + +**Growth-stage founder recovering creative capacity** + +A CEO who built the company's product vision personally has not contributed an original product idea in eighteen months. Every hour is consumed by management, fundraising, and coordination. Applying connected detachment, he stops interpreting this as a personal failure and begins observing it as a structural condition: the role, as currently designed, eliminates every precondition for creative inspiration. The intervention combines Csikszentmihalyi's structural recommendations (protected deep-work blocks from the flow-state framework) with the book's experiential practices (emptying the mind, staying in it, surrounding the lightning bolt). Two mornings per week are cleared entirely. No agenda, no deliverables. He walks, reads unrelated material, and practises noticing. Within a quarter, three substantive product insights emerge from these sessions -- the first original contributions from the CEO in over a year. + +--- + +## Anti-Patterns + +**Treating inspiration as a prerequisite for work.** the text is explicit: "If lightning doesn't strike, our work need not be delayed." The founder who waits for inspiration before beginning meaningful work will produce very little. The daily practice is showing up and building. Inspiration, when it arrives, accelerates work already in progress. + +**Confusing play with lack of discipline.** Play, in the book's framework, is not the absence of structure. It is the absence of premature evaluation. A play session without subsequent craft yields nothing usable. The protocol is: play freely, then apply the full rigour of shaping and refinement to whatever emerges. Companies that institutionalise play without the subsequent craft step produce creative tourism, not creative output. + +**Performing openness without practising it.** The founder who announces "we welcome all ideas" in a meeting but visibly dismisses unfamiliar suggestions has performed openness while practising closure. the book's openness is effortful and uncomfortable: "Do all you can to see from their perspective and understand their point of view, instead of defending your own." It requires genuine cognitive discomfort, not a policy statement. + +**Mistaking connected detachment for emotional suppression.** Detachment is not the refusal to feel. It is the ability to feel fully while maintaining observational perspective. The founder who uses "detachment" as a label for not caring about team morale or customer outcomes is not practising the book's framework. They are practising avoidance. + +**Using spontaneity to avoid preparation.** the text notes that "the story of spontaneity can be misleading. We don't see all the practice and preparation that goes into priming an artist for the spontaneous event to come through." The startup that prizes "moving fast and breaking things" without investing in the foundational knowledge that makes improvisation intelligent is not practising spontaneity. It is practising ignorance at speed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Emptying and receptivity; surrounding the lightning bolt | Maximum freedom to practise the "before" space; the danger is mistaking storm-chasing (active brainstorming) for receptivity (quiet attention) | +| Validation | Radical openness to customer signals that contradict assumptions | The market becomes a collaborator; the practice is absorbing unexpected data without filtering it through existing beliefs | +| Early Traction | Play as institutional practice; breaking creative stagnation | Teams need structured play to prevent the calcification of early success into rigid process | +| Growth | Connected detachment; 24/7 creative mode for leadership | The founder's challenge shifts from producing creative work to maintaining the creative conditions in which others can produce | +| Scale | Designing organisational systems that preserve the conditions for inspiration at scale | The ecstatic signal becomes harder to hear as decision-making layers multiply; the practice is building feedback loops that surface it | + +At the idea stage, the founder has the rare luxury of an empty vessel. This is the moment to practise the book's "before" space most purely -- not by filling every hour with brainstorming, but by cultivating the receptive attention from which genuine ideas emerge. Csikszentmihalyi's flow-state framework provides the structural architecture (protected time, clear goals, challenge-skill balance); the book's contribution is the quality of attention within that architecture. + +At growth and scale, the creative challenge is no longer personal but systemic. The founder must design organisations where the book's conditions -- openness, play, connected detachment, perpetual receptivity -- survive the introduction of process, hierarchy, and institutional memory. This is perhaps the most advanced creative leadership challenge of all: building systems that preserve the conditions for surprise. + +--- + +## Output Template + +```markdown +# Creative Inspiration Conditions -- [Individual/Team] + +**Date:** [Date] +**Context:** [Current creative challenge or aspiration] + +## Lightning Bolt History +[3-5 past breakthrough moments with conditions mapped] +| Moment | Setting | Preceding Activity | Emotional State | Time of Day | +|--------|---------|-------------------|-----------------|-------------| +| [Moment] | [Where] | [What preceded] | [State] | [When] | + +## Common Preconditions Identified +1. [Precondition] +2. [Precondition] +3. [Precondition] + +## Current Structural Barriers to Inspiration +| Barrier | Blocks Which Precondition | Proposed Change | +|---------|--------------------------|-----------------| +| [Barrier] | [Precondition] | [Change] | + +## Weekly Inspiration Architecture +| Day | Before-Space (Emptying/Receptivity) | Craft-Space (Doing) | Notes | +|-----|-------------------------------------|---------------------|-------| +| Mon | [Activity] | [Activity] | | +| Tue | [Activity] | [Activity] | | + +## Play Protocol +- **Frequency:** [Weekly / Biweekly / Monthly] +- **Duration:** [Time] +- **Rules of engagement:** [No evaluation / surprise element / capture method] +- **Craft follow-up:** [When and how raw material gets refined] + +## Detachment Practice +[Specific situations where connected detachment will be applied this quarter] + +## Ecstatic Signal Log +[Running record of moments when the work produced a visceral response -- the compass data] +``` + +--- + +## Related Skills + +- **[Flow State](../frameworks/flow-state.md)** -- Csikszentmihalyi's structural and neurochemical framework for sustained deep performance; this skill complements it with the experiential dimension of courting the unpredictable. +- **[Creative Shaping and Craft](creative-shaping-and-craft.md)** -- Inspiration is raw material; shaping converts it to form. The two skills operate as a paired cycle: receive, then sculpt. +- **[Creative Completion and Renewal](creative-completion-and-renewal.md)** -- The obligation to inspiration includes finishing what it started; completion addresses the challenge of honouring the lightning bolt through the labour of release. +- **[Creative Collaboration and Context](creative-collaboration-and-context.md)** -- Other people are among the richest sources of creative surprise; collaboration multiplies the conditions under which unexpected connections arise. +- **[Creative Practice and Habit](creative-practice-and-habit.md)** -- Daily practice creates the conditions under which inspiration arrives; showing up consistently is the prerequisite for the unpredictable moments of flow. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- The deep work scheduling techniques provide the protected time blocks that creative flow requires to emerge and sustain. diff --git a/plugins/foreman/content/skills/creative/creative-identity-and-purpose.md b/plugins/foreman/content/skills/creative/creative-identity-and-purpose.md new file mode 100644 index 0000000..ffa7616 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-identity-and-purpose.md @@ -0,0 +1,203 @@ +--- +name: "creative-identity-and-purpose" +description: "Applies the philosophy that creativity is a universal human capacity -- not a rare talent -- to help entrepreneurs reclaim their creative identity and redefine success on their own terms. Synthesises beginner's mind, the abundant mindset, non-competition, and creative freedom into a foundational framework for entrepreneurial self-expression. Use when doubting your creative ability, comparing yourself to competitors, trapped in scarcity thinking about ideas or market opportunity, struggling to define what success means for your venture, or needing permission to pursue an unconventional path." +version: "1.0.0" +category: "creative" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - identity + - beginner-mind + - abundance + - non-competition + - freedom + - purpose + - creative-confidence + - creative-philosophy +related_skills: + - creative-perception-and-awareness + - creative-practice-and-habit + - creative-obstacles + - flow-state + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-acceptance-amor-fati +author: "Fatih Guner" +--- + +# The Permission to Create + +Creativity is not a talent. It is a way of seeing -- and according to the text, every person is already creative. Most have simply never given themselves permission. "Creativity is not a rare ability," the text argues. "It is not difficult to access. Creativity is a fundamental aspect of being human. It's our birthright." The entrepreneur who believes creativity belongs to designers, musicians, and novelists has already surrendered the single greatest competitive advantage available: the willingness to perceive the world freshly and act on that perception. Building a company is among the most demanding creative acts a person can undertake. The sooner that truth is acknowledged, the sooner the founder stops waiting for inspiration and starts recognising that they have been creating all along. + +--- + +## The Framework + +### Five Pillars of Creative Identity + +the book's philosophy, distilled across dozens of meditative essays, converges on five interconnected principles that together form a creative operating system for the entrepreneur. + +**1. Everyone Is a Creator** + +The act of creation is not confined to artefacts displayed in galleries. "To create is to bring something into existence that wasn't there before. It could be a conversation, the solution to a problem, a note to a friend, the rearrangement of furniture in a room." Every product decision, every pitch, every pricing model, every conversation with a customer is a creative act. Recognising this does not inflate the word "creative" beyond meaning -- it restores it to its original scope. The founder who sees their work as creative treats problems differently: with curiosity rather than dread, with experimentation rather than formula. + +**2. Beginner's Mind** + +the text tells the story of AlphaGo, the artificial intelligence that defeated the world's greatest Go player with a move no human had made in three thousand years of play. The machine's advantage was not superior intelligence but the absence of accumulated convention. "To see what no human has seen before, to know what no human has known before, it may be necessary to see as if through eyes that have never seen." For the entrepreneur, expertise is simultaneously an asset and a cage. The founder with twenty years of industry experience knows what is "impossible" -- and that knowledge blocks precisely the innovations that would redefine the category. + +**3. The Abundant Mindset** + +"A river of material flows through us. When we share our works and our ideas, they are replenished. If we block the flow by holding them all inside, the river cannot run and new ideas are slow to appear." Scarcity thinking -- hoarding features, refusing to ship until perfection is achieved, fearing that a competitor will steal an idea -- is the enemy of creative momentum. The abundant mindset treats ideas as renewable, products as chapters rather than tombstones, and each release as a catalyst for the next. the text frames this with disarming clarity: "Our life's work is far greater than any individual container. The works we do are at most chapters. There will always be a new chapter, and another after that." The founder who treats their current venture as the only book they will ever write makes decisions rooted in desperation. The one who treats it as one chapter among many makes decisions rooted in creative freedom. + +**4. Non-Competition** + +the text is unequivocal: "Every artist's playing field is specific to them." The entrepreneur's only meaningful competition is with their own previous work. External benchmarking has tactical utility -- understanding a market, pricing competitively, identifying gaps -- but as a creative compass it is ruinous. Theodore Roosevelt's observation that "comparison is the thief of joy" applies with surgical precision to the founder who checks competitor launches before checking their own product roadmap each morning. The distinction the text draws between "rising-to-meet" energy and "conquering" energy is critical: the Beatles and the Beach Boys pushed each other to greatness not through competition but through mutual inspiration. + +**5. Freedom and Self-Defined Success** + +"The artist's only responsibility is to the work itself. There are no other requirements." Success, in the book's reckoning, "occurs in the privacy of the soul. It comes in the moment you decide to release the work, before exposure to a single opinion." This is not anti-commercial naivete. It is the recognition that external validation -- funding rounds, press coverage, revenue milestones -- is a lagging indicator at best and a distorting mirror at worst. The entrepreneur who defines success purely by external metrics will eventually find those metrics dictating creative choices, which hollows the work from within. + +### What Works for You + +the text is careful to note that no two creative paths are identical. "Artists have created in every way possible -- at the extremes of chaos and order, and at the meeting point of different methods at once. There is no right time, right strategy, or right equipment." Charles Dickens carried a compass to ensure he always slept facing north. Dr. Seuss wore unusual hats. The point is not that these rituals are rational but that they worked for the people who used them. For the entrepreneur, this principle is liberating: there is no single correct way to build a company. "Receive wisdom skillfully. Try it on for size and see how it fits. Incorporate what's useful. Let go of the rest." The founder who slavishly follows a playbook designed for someone else's company, market, and temperament will produce work that feels borrowed. The one who tests every approach and keeps only what resonates will produce work that feels original -- because it is. + +### Nothing Is Static + +Undergirding all five pillars is the book's insistence on impermanence. "The world is always changing. You can engage in the same awareness practice five days in a row in the same location and have a unique experience each time." Creative identity is not a fixed label. The founder who was a fintech operator last year may be a climate entrepreneur this year -- not because they are unfocused, but because they are alive. Purpose, the text suggests, is not something to be declared in advance but something to be discovered through engagement. "If we like what we are creating, we don't have to know why. Sometimes the reasons are obvious, sometimes not. And they can change over time." The entrepreneur who insists on articulating a grand purpose before beginning has the sequence backwards. Make the work. The purpose will reveal itself. + +--- + +## Prompts + +**Prompt 1 -- Creative Identity Audit:** +> I am a founder of [company] at the [stage] stage. I often feel that I am "not creative" or that creativity is separate from my business work. Using the book's principle that everyone is already a creator, help me identify the creative acts I perform daily -- in product decisions, team interactions, problem-solving, and communication. Reframe my role as a creative one and show me where I am already creating. + +**Prompt 2 -- Beginner's Mind Reframe:** +> I have [X years] of experience in [industry]. Identify the conventions, assumptions, and "impossibilities" I may have absorbed that could be limiting my ability to see fresh solutions. Apply the AlphaGo principle: what moves might I make if I had no knowledge of how things are "supposed to be done" in this space? + +**Prompt 3 -- Abundance vs. Scarcity Diagnostic:** +> Analyse my current approach to [specific business challenge: idea generation / product shipping / competitive response / feature prioritisation]. Am I operating from an abundant or scarcity mindset? Where am I hoarding ideas, delaying releases, or treating this venture as my "one shot"? Recommend concrete shifts toward abundance. + +**Prompt 4 -- Success Redefinition:** +> I currently measure success by [metrics: revenue, funding, press, user growth]. Using the book's framework, help me construct a parallel definition of success rooted in the quality and authenticity of my creative output. What would it look like if I evaluated my work "before exposure to a single opinion"? + +--- + +## Use Cases + +**Idea-stage founder paralysed by "not being creative enough"** + +A former management consultant is developing a mental health platform but dismisses her own creative capacity because she has "never been an artist." She defaults to copying competitor interfaces and features rather than developing her own vision. Applying the Everyone Is a Creator principle reframes her daily work -- mapping user journeys, designing onboarding flows, writing microcopy -- as inherently creative acts. The beginner's mind lens reveals that her lack of health-tech experience is an asset: she sees friction points that industry veterans have normalised. Within weeks, her product concept diverges sharply from competitors, grounded in her unique perception rather than borrowed convention. + +**Growth-stage CEO trapped in competitive obsession** + +A Series A e-commerce founder starts every morning by reviewing three competitors' social feeds, pricing pages, and feature announcements. The practice consumes ninety minutes daily and produces anxiety rather than insight. Applying the book's non-competition principle surfaces the real problem: the founder has outsourced his creative compass to external benchmarks. Replacing the competitive review with a daily "creative intention" practice -- thirty minutes reflecting on what his product uniquely offers and where it wants to go next -- restores both originality and calm. Revenue growth does not slow. The product begins to differentiate. + +**Scale-stage executive hoarding the "big idea"** + +A CEO at scale refuses to launch a promising new product line because it is "not ready yet" -- a position she has maintained for eighteen months. The abundant mindset audit reveals classic scarcity behaviour: treating this product as her company's defining work rather than one chapter among many. The reframe -- that shipping creates space for the next idea -- unlocks the launch within eight weeks. The product performs adequately; the next idea, which arrives almost immediately, performs brilliantly. + +**Validation-stage technical founder following someone else's playbook** + +An engineer-turned-founder has read every canonical startup book and follows a rigorous build-measure-learn process borrowed from a prominent accelerator. His execution is methodical, but his product feels generic -- indistinguishable from three competitors pursuing the same thesis. The "What Works for You" principle reveals the issue: he has adopted someone else's creative method wholesale, suppressing his own instincts about what the product should feel like. the book's advice -- "established artists generally draw from their personal experience and recommend the solutions that worked for them; these tend to be specific to their journey, not yours" -- grants him permission to deviate from the playbook. He introduces a design language drawn from his background in electronic music, an aesthetic choice no accelerator would have recommended. Users describe the product as "different from everything else." It is. That was the point. + +--- + +## Anti-Patterns + +**1. Weaponising "everyone is creative" to skip craft development.** The principle that creativity is universal does not mean that craft is unnecessary. A founder who cannot write clearly, think structurally, or build iteratively will not produce great work merely by declaring a creative identity. Permission is the starting line, not the finish. + +**2. Treating beginner's mind as wilful ignorance.** the book's beginner's mind is a deliberate posture of openness, not a refusal to learn. The founder who ignores market data, customer feedback, or financial constraints because they are "thinking like a beginner" has confused freshness with recklessness. + +**3. Misreading non-competition as anti-ambition.** the text does not counsel passivity. The distinction between competitive energy and rising-to-meet energy is subtle but vital. Studying competitors to be inspired is healthy; studying competitors to copy or destroy is corrosive. The founder who uses non-competition as a reason not to push harder has missed the point entirely. + +**4. Defining abundance as indiscriminate shipping.** The abundant mindset encourages flow, not carelessness. Releasing work that is genuinely unfinished -- not iterative but simply lazy -- erodes trust with users and team alike. Abundance means trusting that the next idea will come, not that the current one does not matter. + +**5. Using "success is internal" to avoid accountability.** the book's redefinition of success is a philosophical complement to external metrics, not a replacement for them. The founder who ignores burn rate, churn, or customer satisfaction because they have achieved "internal success" is confusing contemplation with delusion. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Granting creative permission | The most powerful intervention is simply recognising that building a company is a creative act; beginner's mind is naturally present and should be protected | +| Validation | Maintaining openness amid early data | The temptation to prematurely narrow based on initial feedback is strongest here; abundant thinking keeps multiple seeds alive | +| Early Traction | Resisting the pull of competitor imitation | As the market becomes visible, the urge to benchmark and copy intensifies; non-competition principles preserve distinctiveness | +| Growth | Redefining success beyond funding metrics | External validators (investors, press, industry awards) gain volume; the internal definition of success becomes a stabilising force | +| Scale | Institutionalising creative identity | The founder's personal creative philosophy must translate into organisational culture; hire for creative orientation, not just functional skill | + +At the idea stage, creative identity is both most fragile and most potent. The founder has not yet accumulated the conventions, compromises, and competitive anxieties that calcify at later stages. The discipline is to protect that openness deliberately -- to resist the advisory board members and mentors who will helpfully suggest "how things are done in this space." Beginner's mind is naturally present at this stage; the work is to avoid extinguishing it prematurely in the name of "learning the industry." + +At validation, the abundant mindset faces its first serious test. Early data is ambiguous. The scarcity-minded founder treats every signal as definitive -- pivoting after a single negative interview, or doubling down after a single positive one. The abundance-minded founder holds multiple seeds simultaneously, allowing the data to accumulate before narrowing. This is not indecision. It is the recognition that premature certainty is the enemy of discovery. + +At early traction, competitive pressure becomes visceral. The company now has something to lose, and competitors become visible and threatening. The non-competition principle is hardest to maintain precisely when it is most valuable. The founder who can stay focused on their own creative trajectory -- what the text calls the "competition with the self" -- will produce work that competitors cannot replicate, because it originates from a unique creative identity rather than a shared market playbook. + +At growth, external definitions of success proliferate. Revenue targets, investor expectations, press narratives, and industry rankings all impose their metrics on the founder's sense of accomplishment. the book's insistence that success "occurs in the privacy of the soul" becomes a stabilising counterweight. This does not mean ignoring business metrics -- it means refusing to let them become the sole compass. The founder who can hold both an external scorecard and an internal measure of creative integrity simultaneously navigates growth without losing the creative instincts that produced the company's initial distinctiveness. Those who cannot tend to optimise for metrics that are visible and measurable while the invisible, unmeasurable quality of their creative work quietly erodes. + +At scale, the challenge inverts entirely. Creative identity is no longer a personal matter but an institutional one. The company's ability to innovate depends on whether the founding creative philosophy has been embedded in hiring, product development, and strategic planning -- or whether it died the day the founder stopped being the one making things. the book's principle that "nothing is static" applies with particular force here: the creative identity that launched the company may not be the one that sustains it. The willingness to evolve -- to approach the company's next chapter with the same beginner's mind that characterised its first -- is what separates enduring creative enterprises from those that peak and plateau. + +--- + +## Output Template + +```markdown +# Creative Identity Assessment -- [Company/Project] + +**Date:** [Date] +**Founder/Team:** [Names] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Current Creative Self-Perception +- How do I/we describe our creative capacity? [Response] +- Where do I/we feel "not creative enough"? [Response] +- What conventions or "rules" am I/are we following without questioning? [Response] + +## Five Pillars Diagnostic + +| Pillar | Current State (1-5) | Evidence | Action | +|--------|---------------------|----------|--------| +| Creator Identity | [Score] | [How creativity shows up in daily work] | [Step to strengthen] | +| Beginner's Mind | [Score] | [Assumptions held; conventions followed] | [Assumption to challenge] | +| Abundant Mindset | [Score] | [Hoarding vs. flowing behaviour] | [Idea or product to release] | +| Non-Competition | [Score] | [Time spent on competitor analysis vs. own vision] | [Practice to shift] | +| Freedom / Success | [Score] | [External vs. internal success metrics] | [New success definition] | + +## Beginner's Mind Inventory +| Convention I Follow | Source (Industry / Advisor / Competitor / Self) | What Happens If I Drop It? | +|--------------------|-------------------------------------------------|----------------------------| +| [Convention 1] | [Source] | [Possible outcome] | +| [Convention 2] | [Source] | [Possible outcome] | +| [Convention 3] | [Source] | [Possible outcome] | + +## Competition Reframe +**Current competitive focus:** [What competitors am I watching and how often?] +**Energy type:** [Conquering or rising-to-meet?] +**Self-competition target:** [What is my own previous work that I want to surpass?] + +## Creative Permission Statement +[One sentence: what I give myself permission to create, regardless of convention] + +## Success Definition (Internal) +[How I will measure success before exposure to any external opinion] + +## Next Creative Act +[The specific product decision, experiment, or expression to pursue this week] +``` + +--- + +## Related Skills + +- **[Creative Perception and Awareness](creative-perception-and-awareness.md)** -- Once creative identity is established, the next step is refining the ability to perceive the signals that feed creation. +- **[Creative Practice and Habit](creative-practice-and-habit.md)** -- Identity without practice is aspiration; this skill provides the daily discipline that makes creative identity operational. +- **[Creative Obstacles](creative-obstacles.md)** -- The internal resistance that threatens creative identity -- self-doubt, distraction, undermining voices -- and how to navigate it. +- **[Flow State](../frameworks/flow-state.md)** -- Csikszentmihalyi's optimal experience theory provides the psychological mechanics behind the creative states described experientially. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- The non-competition and freedom principles align with the Stoic dichotomy of control: focus energy on your own creative output, release attachment to outcomes. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- The organisational parallel to creative purpose: both address the question of why the work matters beyond personal ambition or financial return. diff --git a/plugins/foreman/content/skills/creative/creative-obstacles.md b/plugins/foreman/content/skills/creative/creative-obstacles.md new file mode 100644 index 0000000..53636a2 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-obstacles.md @@ -0,0 +1,205 @@ +--- +name: "creative-obstacles" +description: "Addresses the internal resistances that derail entrepreneurial creativity -- self-doubt, distraction, undermining voices, the danger of expectations, and impatience -- using a contemplative creative framework. Provides strategies for navigating the inner critic, managing creative possession, and cultivating patience as a creative virtue. Use when paralysed by self-doubt about your venture, overwhelmed by internal or external criticism, struggling with perfectionism or unrealistic expectations, unable to distinguish productive obsession from destructive compulsion, or losing patience with the creative timeline of building a company." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - self-doubt + - inner-critic + - distraction + - patience + - expectations + - resilience + - creative-blocks + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-perception-and-awareness + - creative-practice-and-habit + - flow-state + - stoic-emotional-mastery + - stoic-fortitude-and-resilience + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +# The Censor in the Room + +Every creator has a censor living inside their head. It speaks fluently in the language of inadequacy: you are not talented enough, your idea is not good enough, you will be exposed as a fraud. The question is not how to silence this voice -- that project has a zero percent success rate -- but when to stop listening. The text treats self-doubt not as a malfunction to be repaired but as an inevitable companion on the creative path. "Self-doubt lives in all of us," he writes. "And while we may wish it gone, it is there to serve us." The entrepreneur who attempts to eradicate doubt will exhaust themselves fighting an enemy that regenerates overnight. The one who learns to work alongside it -- acknowledging its presence without granting it authority -- gains access to a harder, more durable form of creative confidence. + +--- + +## The Framework + +### The Six Obstacles + +the text identifies a constellation of internal resistances that recur across creative lives. For the entrepreneur, each maps to a specific pattern of self-sabotage that can stall companies as effectively as any market force. + +**Obstacle 1: Self-Doubt -- The Universal Companion** + +"Flaws are human, and the attraction of art is the humanity held in it. If we were machinelike, the art wouldn't resonate. It would be soulless." the text reframes self-doubt as evidence of creative sensitivity rather than creative deficiency. The most vulnerable artists are often the most talented, precisely because the same sensitivity that allows them to perceive deeply also makes them tender to judgement. "The sensitivity that allows them to make the art is the same vulnerability that makes them more tender to being judged." + +The entrepreneurial implication is counterintuitive: the founder wracked by doubt about their product may be closer to something genuine than the one who radiates unshakeable confidence. Doubt, properly channelled, is a quality-control mechanism. It becomes destructive only when it prevents action rather than refining it. + +the text draws one firm line: "If a creator is so afraid of judgement that they're unable to move forward, it might be that the desire to share the work isn't as strong as the desire to protect themselves." Doubt is permissible. Paralysis is not. The founder must ship. + +**Obstacle 2: Undermining Voices -- Internal and External Critics** + +"As these voices enter an artist's head -- concern for deadlines, deals, sales, media attention, public image, staff, overhead, growing the audience -- they can undermine our focus." the text distinguishes between two species of undermining voice. External voices arrive from investors, advisors, customers, competitors, press, and the market itself. Internal voices are often absorbed versions of external ones -- "a critical or doting parent, teacher, or mentor. These voices are not our own. We have internalised someone else's judgement." + +The remedy is not argument but disengagement. "Working to free yourself from inner voices is a kind of meditation. Set aside all concerns for a stretch of time and say, I'm only going to focus on this one practice: making great work." The entrepreneur need not refute every critic. The task is to create conditions -- temporal, spatial, psychological -- where the voices cannot reach the work. + +**Obstacle 3: Distraction -- The Misunderstood Tool** + +the text makes a distinction that most productivity literature misses entirely: "Distraction is not procrastination. Procrastination consistently undermines our ability to make things. Distraction is a strategy in service of the work." Strategic distraction -- a walk, a drive, a shower, an unrelated physical task -- occupies the conscious mind and frees the subconscious to work on the problem. "Some musicians do a better job of writing melodies while driving than sitting in a room with an audio recorder on." + +The entrepreneurial application is that not all time away from the desk is wasted time. The founder who takes a thirty-minute walk to think through a pricing decision is not avoiding work -- provided the walk is intentional, the problem is held loosely in awareness, and the return to active work follows. The founder who scrolls social media for three hours is procrastinating. The difference is intention. + +**Obstacle 4: Great Expectations -- The Weight of Anticipated Outcomes** + +"When beginning a new project, we're often met with anxiety. It visits almost all of us no matter how experienced, successful, or well-prepared we might be." the text identifies expectations as a paradox: high standards drive quality, but attachment to specific outcomes freezes the creative process. The solution is what he calls "experimental faith" -- working "not as an evangelist, expecting miracles, but as a scientist, testing and adjusting and testing again." + +For the entrepreneur, this reframes failure entirely. "If we try ten experiments and none of them work, we have a choice. We can take it personally, and think of ourselves as a failure and question our ability to solve the problem. Or we can recognize we've ruled out ten ways that don't work, bringing us that much closer to a solution." The founder who holds expectations loosely -- maintaining high standards while releasing attachment to specific results -- can iterate without emotional collapse. + +**Obstacle 5: The Possessed -- Obsession vs. Sustainability** + +"Artists are often portrayed as tortured geniuses. Starving, self-destructive, dancing on the brink of madness. This has instilled the belief that to make art, one has to be broken." the text dismantles the myth of the tortured creator with quiet firmness. Obsessive drive can produce great work, but unsustainable obsession produces burnout, addiction, and abandonment. "Whether you have a powerful passion or a tortured compulsion, neither makes the art any better or worse. If you are able to choose between these paths, consider selecting the more sustainable one." + +The startup culture that celebrates sleepless founders, burnout-as-badge, and "grinding" has internalised the tortured-artist myth in business clothing. the book's counsel is that the creative path is long. The founder who destroys their health and relationships in year two will not be creating in year ten. + +**Obstacle 6: Patience -- The Least Popular Virtue** + +"There are no shortcuts," the text states flatly. "Our continual quest for efficiency discourages looking too deeply. The pressure to deliver doesn't grant us time to consider all possibilities. Yet it's through deliberate action and repetition that we gain deeper insight." Patience is not passive waiting. It is "accepting that the majority of the work we do is out of our control. We can't force greatness to happen. All we can do is invite it in and await it actively." + +The entrepreneurial translation: the company that takes three years to find product-market fit has not failed for three years. It has been practising. "Even the masterpieces that have been produced on tight timelines are the sum of decades spent patiently labouring on other works." Speed-to-market is a tactical variable. The depth of the work is a function of the patience invested in it. + +### The Reset Protocol + +Across all six obstacles, the text returns to a single corrective mechanism: "The first step of clearing is acknowledgement. Notice yourself feeling the weight of self-criticism or the pressure to live up to expectations. And remember that commercial success is completely out of your control. All that matters is that you are making something you love, to the best of your ability, here and now." Acknowledgement is not resolution. It is the precondition for resolution. The entrepreneur who can name the obstacle -- "this is self-doubt," "this is an undermining voice," "this is attachment to outcome" -- has already begun to diminish its power. + +--- + +## Prompts + +**Prompt 1 -- Inner Critic Mapping:** +> I am a founder of [company] and I am experiencing [specific doubt, fear, or creative block]. Using the book's obstacle framework, help me identify which of the six obstacles is operating: self-doubt, undermining voices (internal or external), distraction vs. procrastination, excessive expectations, unsustainable obsession, or impatience. For the identified obstacle, provide a specific book-informed strategy for working alongside it rather than against it. + +**Prompt 2 -- Voice Audit:** +> List the voices currently influencing my creative and strategic decisions as founder of [company]: investors, advisors, board members, team members, customers, press, competitors, and my own internal critic. For each, assess whether the voice is serving the quality of the work or undermining it. Recommend which voices to amplify, which to attenuate, and how to create protected creative space free from all of them. + +**Prompt 3 -- Expectation Calibration:** +> I am about to begin [new project / product launch / pivot / fundraise]. My expectations are [describe]. Using the book's concept of experimental faith, help me separate legitimate quality standards from attachment to specific outcomes. Reframe my approach from "this must succeed in the following way" to "this is an experiment that will teach me something regardless of result." + +**Prompt 4 -- Sustainability Assessment:** +> Honestly evaluate my current working patterns as founder of [company]: [hours, sleep, exercise, relationships, creative vs. administrative time ratio]. Using the book's framework on the possessed vs. the sustainable creator, assess whether my current pace can produce great work over a ten-year horizon. If not, recommend structural changes that preserve creative intensity while ensuring longevity. + +--- + +## Use Cases + +**Validation-stage founder paralysed by fear of market rejection** + +A first-time founder has built an MVP for a consumer fintech product but has delayed launch for four months, finding new "essential" features to add each week. The obstacle diagnosis reveals two interlocking forces: self-doubt ("what if people hate it?") and excessive expectations ("it has to be perfect for launch"). Applying the book's experimental faith reframe -- "the outcome is not up to us; give some attention to each seed and look for a beautiful response" -- converts the launch from a verdict into a test. She ships a stripped-down version within two weeks. User feedback is mixed -- as it always is -- but the paralysis breaks and the iteration cycle begins. + +**Early-traction founder consumed by investor and advisor voices** + +A seed-stage founder with a promising social commerce platform has assembled an advisory board of six experienced operators. Each provides thoughtful but contradictory strategic advice. The founder now changes direction after every advisory call, unable to hold his own creative vision against the weight of external credibility. the book's voice audit reveals that six external voices have colonised the founder's creative process. The intervention is structural: advisory calls are reduced from weekly to monthly, creative work sessions are scheduled before (never after) external meetings, and a daily five-minute practice of articulating "what I believe about this product" rebuilds the founder's own creative authority. + +**Growth-stage CEO approaching burnout** + +A Series B founder has worked eighty-hour weeks for three years. Her company is growing, but her product instincts have dulled. She describes feeling "hollow" -- capable of operational execution but unable to generate the creative insights that characterised the company's early days. The sustainability assessment diagnoses possession: the company has consumed the person. the book's counsel -- "if you are able to choose between these paths, consider selecting the more sustainable one" -- provides philosophical permission for a structural change the founder intellectually knows is necessary but emotionally resists. A three-week creative sabbatical, followed by a restructured role that protects forty percent of her time for creative work, restores both the founder and the company's creative trajectory. + +--- + +## Anti-Patterns + +**1. Interpreting "self-doubt is natural" as permission to wallow.** the text acknowledges doubt as a companion, not as a destination. The founder who uses "self-doubt is part of the process" to justify months of inaction has misread the principle. Doubt walks alongside the work. It does not substitute for it. + +**2. Branding all criticism as "undermining voices."** Not every critical voice is an enemy of creation. Honest feedback from customers, rigorous challenge from co-founders, and difficult questions from investors can sharpen the work. The task is to distinguish between voices that serve quality and voices that serve fear or ego. Dismissing all external input as noise is creative solipsism. + +**3. Using strategic distraction as a euphemism for avoidance.** A thirty-minute walk to process a creative problem is strategic distraction. A three-day retreat to "think about the business" while avoiding a difficult product decision is procrastination wearing a contemplative disguise. The test is simple: does the distraction end with a return to the work? + +**4. Releasing attachment to outcomes so thoroughly that standards disappear.** Experimental faith does not mean anything goes. The founder who ships carelessly and shrugs off poor results as "just an experiment" has abandoned rigour in the name of detachment. High standards and loose attachment to specific outcomes are not contradictory -- they are complementary. + +**5. Confusing patience with complacency.** "There are no shortcuts" does not mean there are no deadlines. Patience is about the depth of engagement with each step, not about the pace of the overall journey. The founder who uses the book's patience principle to justify missing every milestone has weaponised a virtue into a vice. + +--- + +## By Stage + +| Stage | Primary Obstacle | Key Intervention | +|-------|-----------------|------------------| +| Idea | Self-doubt ("Am I even capable of this?") | Normalise doubt as evidence of creative sensitivity; decouple identity from outcome | +| Validation | Fear of rejection and excessive expectations | Reframe launch as experiment, not verdict; practice experimental faith | +| Early Traction | Undermining voices from investors and advisors | Structural protection of creative space; voice audit to separate signal from noise | +| Growth | Unsustainable obsession and burnout | Sustainability assessment; role restructuring to preserve creative capacity | +| Scale | Institutional impatience and results pressure | Embed patience into product culture; resist the organisation's natural bias toward speed over depth | + +At the idea stage, the dominant obstacle is existential: does the founder believe they are capable of creating something worth building? Self-doubt at this stage is not about a specific product or market -- it is about creative identity itself. The intervention connects directly to the creative-identity-and-purpose skill: the founder must first grant themselves permission to create before they can navigate the obstacles that creation produces. + +At growth and scale, the obstacles shift from personal to institutional. The CEO's inner critic is replaced by the board's quarterly expectations. The founder's impatience is replaced by the market's. The principles remain the same -- name the obstacle, acknowledge it, create protected space for the work -- but they must be applied at organisational scale, which requires explicit cultural choices about how the company relates to doubt, criticism, experimentation, and time. + +--- + +## Output Template + +```markdown +# Creative Obstacles Assessment -- [Company/Project] + +**Date:** [Date] +**Context:** [What prompted this assessment] + +## Obstacle Inventory + +| Obstacle | Present? | Intensity (1-5) | Impact on Work | Current Response | +|----------|----------|-----------------|----------------|-----------------| +| Self-doubt | [Y/N] | [1-5] | [How it manifests] | [What I do now] | +| Undermining voices | [Y/N] | [1-5] | [Specific voices] | [Current response] | +| Distraction / Procrastination | [Y/N] | [1-5] | [Which type?] | [Current pattern] | +| Excessive expectations | [Y/N] | [1-5] | [Specific expectations] | [How they constrain] | +| Unsustainable obsession | [Y/N] | [1-5] | [Physical/emotional signs] | [Current coping] | +| Impatience | [Y/N] | [1-5] | [Where rushing?] | [What gets skipped] | + +## Voice Map + +| Voice | Source (Internal/External) | Serves Quality? | Serves Fear/Ego? | Action | +|-------|--------------------------|-----------------|-------------------|--------| +| [Voice 1] | [Source] | [Y/N] | [Y/N] | [Amplify / Attenuate / Remove] | +| [Voice 2] | [Source] | [Y/N] | [Y/N] | [Action] | + +## Protected Creative Space Plan +- **When:** [Scheduled times free from external voices] +- **Where:** [Physical/digital environment] +- **Duration:** [Minimum protected hours per week] +- **Boundary rules:** [What is excluded during this time] + +## Experimental Faith Statement +[Reframe current challenge from "this must succeed" to "this experiment will teach me..."] + +## Sustainability Check +- **Current weekly hours:** [Number] +- **Sleep quality:** [Good / Fair / Poor] +- **Creative energy level:** [High / Medium / Low / Depleted] +- **Sustainable for 10 years?** [Honest assessment] +- **One structural change to improve sustainability:** [Specific action] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](creative-identity-and-purpose.md)** -- Self-doubt attacks creative identity at its root; the permission framework provides the philosophical foundation for withstanding it. +- **[Creative Perception and Awareness](creative-perception-and-awareness.md)** -- Obstacles cloud perception; clearing them restores the ability to receive creative signals cleanly. +- **[Creative Practice and Habit](creative-practice-and-habit.md)** -- Consistent practice is the primary antidote to most creative obstacles; showing up daily diminishes doubt's authority over time. +- **[Flow State](../frameworks/flow-state.md)** -- Flow states are disrupted by self-doubt, distraction, and excessive expectations; removing these obstacles creates the conditions for optimal creative experience. +- **[Stoic Emotional Mastery](../stoic/stoic-emotional-mastery.md)** -- The Stoic discipline of managing emotional responses complements the approach to internal creative resistance. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- The dichotomy of control maps directly onto the insistence that commercial success is outside the artist's control while the quality of the work is within it. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Creative failure is a specific form of the broader failure experience; the practices for examining setbacks without shame apply directly to creative work that does not meet expectations. diff --git a/plugins/foreman/content/skills/creative/creative-perception-and-awareness.md b/plugins/foreman/content/skills/creative/creative-perception-and-awareness.md new file mode 100644 index 0000000..64adc55 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-perception-and-awareness.md @@ -0,0 +1,199 @@ +--- +name: "creative-perception-and-awareness" +description: "Develops the entrepreneur's capacity to receive creative signals by applying principles of tuning in, deep awareness, and perceptual sensitivity. Covers the vessel-and-filter model, seeing the unseen, nature as teacher, deep listening, the role of subconscious and memory, and how setting shapes creative output. Use when feeling creatively numb, missing market signals, unable to generate fresh product ideas, sensing that important information is passing you by, or needing to sharpen intuitive pattern recognition for innovation." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - awareness + - perception + - tuning-in + - listening + - intuition + - subconscious + - pattern-recognition + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-practice-and-habit + - creative-obstacles + - flow-state + - stoic-self-awareness + - stoic-unbiased-thought + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +# The Entrepreneur as Antenna + +Creativity is not about producing -- it is about receiving. The universe broadcasts constantly; the question is whether your antenna is tuned. The text frames the creative act not as an act of will but as an act of perception: "We are all antennae for creative thought. Some transmissions come on strong, others are more faint. If your antenna isn't sensitively tuned, you're likely to lose the data in the noise." The entrepreneur who treats innovation as a manufacturing process -- inputs, throughput, outputs -- misses the deeper truth that the best products, brands, and companies begin not with effort but with noticing. A market gap is not calculated into existence; it is perceived. A customer need is not deduced; it is felt. The foundation of creative entrepreneurship is not productivity. It is sensitivity. + +--- + +## The Framework + +### The Signal Architecture + +the book's model of creative perception operates across five interlocking layers, each of which sharpens the entrepreneur's ability to detect, receive, and act on creative information. + +**Layer 1: Tuning In -- The Cosmic Frequency** + +"Think of the universe as an eternal creative unfolding," the text argues. "Trees blossom. Cells replicate. Rivers forge new tributaries." Creativity is not something humans invented. It is a force we participate in. The entrepreneur who acknowledges this shift -- from creator to conduit -- gains access to a richer information stream. Ideas, the text suggests, exist in an "aether" and ripen on schedule. "If you have an idea you're excited about and you don't bring it to life, it's not uncommon for the idea to find its voice through another maker." The practical implication is stark: the window for any given creative opportunity has a natural expiry. Tuning in is not optional. It is time-sensitive. + +**Layer 2: Awareness -- The Foundational Capacity** + +Awareness, in the book's system, is not analytical. It is pre-analytical. "The gift of awareness allows us to notice what's going on around and inside ourselves in the present moment. And to do so without attachment or involvement." The moment an entrepreneur labels what they are perceiving -- "that's a market trend," "that's a competitor threat" -- they have left awareness and entered analysis. Analysis has its place, but it is a secondary function. "The awareness happens first as a pure connection with the object of your attention. If something strikes me as interesting or beautiful, first I live that experience. Only afterward might I attempt to understand it." For the entrepreneur, this means cultivating the discipline to notice before categorising, to feel before strategising. + +**Layer 3: The Vessel and the Filter** + +Every person carries what the text calls a "vessel" -- a container of accumulated thoughts, feelings, experiences, and perceptions. Information reaches the vessel through a "filter" that is unique to each individual. The filter is simultaneously essential and limiting: it prevents sensory overwhelm but also distorts incoming data. "Our filter inevitably reduces Source intelligence by interpreting the data that arrives instead of letting it pass freely." Over time, the filter produces beliefs and stories that harden into a worldview -- which then shapes what the entrepreneur is capable of perceiving. The practical work is twofold: expand the vessel's capacity (take in more) and soften the filter's rigidity (distort less). "With training, we can improve our interface with Source and radically expand the vessel's ability to receive." + +**Layer 4: Looking for Clues and Seeing the Unseen** + +the text describes creative information as arriving through channels that defy conventional analysis. "Material for our work surrounds us at every turn. It's woven into conversation, nature, chance encounters, and existing works of art." The entrepreneur who walks through a trade show scanning for competitive intelligence is using analysis. The one who walks through and notices an unexpected emotional reaction to a particular booth layout -- then follows that reaction to its source -- is using awareness. the book's "unseen" is not mystical obfuscation. It is the recognition that the most valuable creative signals are often the subtlest: "They are energetic more than tactile, intuitively perceived more than consciously recorded." + +**Layer 5: The Inner Landscape and the Subconscious** + +The final layer turns the antenna inward. "If we focus on what's going on inside ourselves -- sensations, emotions, the patterns of our thoughts -- a wealth of material can be found. Our inner world is every bit as interesting, beautiful, and surprising as nature itself." the text advocates practices that access the subconscious -- dream journals, automatic writing, physical exercises that bypass the analytical mind. "There's an abundant reservoir of high-quality information in our subconscious, and finding ways to access it can spark new material to draw from." For the entrepreneur, this means that strategic insight does not always emerge from spreadsheets. Sometimes it surfaces during a shower, a drive with no destination, or the liminal space between sleep and waking. + +### Environmental Design: Setting as Instrument + +the text devotes particular attention to how physical environment shapes perception. "Isolated places like a forest, a monastery, or a sailboat in the middle of the ocean are fine locations to receive direct transmissions from the universe. If instead you want to tune in to the collective consciousness, you might sit in a busy spot with people coming and going." The implication for entrepreneurs is that workspace design is not an operational question -- it is a creative one. Andy Warhol created with a television, radio, and record player all running simultaneously. Marcel Proust lined his walls with cork and wore earplugs. Neither was wrong. The question is which environment serves the specific creative task at hand. + +### Nature as the Ultimate Calibrator + +"Of all the great works that we can experience, nature is the most absolute and enduring." the text uses nature not as a metaphor but as a practice. The entrepreneur who spends time in natural settings is not relaxing -- they are recalibrating their perceptual instrument. "If you're picking colours based on a Pantone book, you're limited to a certain number of choices. If you step out in nature, the palette is infinite." Nature bypasses the filter and speaks directly to the vessel. + +### Deep Listening + +"Listening is paying attention to those sounds, being present with them, being in communion with them." the text distinguishes sharply between hearing (passive reception) and listening (active presence). "Formulating an opinion is not listening. Neither is preparing a response, or defending our position or attacking another's. To listen impatiently is to hear nothing at all." For the entrepreneur conducting customer interviews, investor meetings, or team discussions, this distinction is the difference between extracting data and receiving insight. + +--- + +## Prompts + +**Prompt 1 -- Perceptual Audit:** +> Map my current information diet as founder of [company]. Where am I receiving creative signals (customer conversations, nature, art, stillness, movement)? Where am I relying exclusively on analytical inputs (dashboards, reports, competitor analysis)? Using the book's vessel-and-filter model, identify where my filter may be distorting or blocking incoming creative data, and recommend practices to soften it. + +**Prompt 2 -- Deep Listening Diagnostic:** +> Analyse my last three [customer interviews / team meetings / investor conversations]. Where did I listen to understand, and where did I listen to respond? Where might I have missed subtler signals -- emotional undertones, unspoken concerns, unexpected phrasing -- because my filter was already categorising the information? Provide a listening protocol based on the book's principle that "listening is suspending disbelief." + +**Prompt 3 -- Environment-Creativity Mapping:** +> I currently work in [describe workspace and daily environment]. Using the book's framework on setting, assess how my physical environment may be shaping my creative output. Recommend specific environmental changes for different types of creative work: ideation, focused building, strategic reflection, and collaborative creation. + +**Prompt 4 -- Clue Detection Exercise:** +> I am stuck on [specific product/business challenge]. Instead of analytical problem-solving, guide me through the book's "look for clues" practice. Help me design a 48-hour awareness exercise where I hold this question loosely in consciousness while engaging with diverse inputs -- conversations, walks, art, reading -- and document any unexpected connections or resonances that arise. + +--- + +## Use Cases + +**Validation-stage founder missing customer signals** + +A B2B SaaS founder conducts weekly customer discovery calls following a rigorous script. Her conversion from trial to paid is stagnant at 4%. Applying the book's deep listening principle reveals the problem: she listens to confirm her hypothesis, not to receive what customers are actually communicating. A shift to unscripted, awareness-based conversations -- where she follows emotional energy rather than a question list -- surfaces a pain point she had systematically filtered out because it did not match her product thesis. The pivot takes six weeks. Conversion triples. + +**Growth-stage product team suffering from creative blindness** + +A consumer app team has shipped twelve incremental updates in a row, each marginally better than the last. The head of product describes the feeling as "running on a treadmill." The vessel-and-filter diagnosis identifies the cause: the team's perceptual apparatus has been narrowed to a single data stream -- usage analytics. Introducing the book's environmental practices -- weekly team walks without devices, exposure to products in completely unrelated industries, a "clue journal" for recording unexpected observations -- broadens the vessel. Within a month, the team identifies a feature concept that originated from a team member's observation at a farmer's market. It becomes the most successful release of the year. + +**Idea-stage entrepreneur who cannot "find" an idea** + +An aspiring founder with capital, talent, and ambition has spent six months trying to identify a startup concept through market analysis and trend reports. Nothing resonates. The problem, through the book's lens, is that she is looking analytically for something that arrives perceptually. Shifting from search to reception -- spending mornings in awareness practice, afternoons in diverse environments (hospitals, construction sites, schools, kitchens), and evenings recording what moved her -- produces three viable concepts within four weeks. The winning idea comes from a whispered observation during a visit to her grandmother's assisted-living facility. + +--- + +## Anti-Patterns + +**1. Treating awareness as a substitute for execution.** the book's perception framework is a complement to action, not a replacement for it. The entrepreneur who spends months "tuning in" without building, shipping, or testing has confused receptivity with procrastination. Awareness feeds creation; it does not replace it. + +**2. Romanticising the subconscious into mysticism.** Dream journals and automatic writing are practical tools for accessing non-analytical insight. They are not divination. The founder who bases product strategy on a dream without subjecting that insight to rigorous validation has abandoned judgement, not transcended it. + +**3. Using "deep listening" to avoid making decisions.** the book's listening is a perceptual practice, not an excuse for consensus paralysis. The entrepreneur who keeps listening and never acts -- who conducts another round of interviews, another survey, another advisory session -- is using awareness as a shield against the discomfort of commitment. + +**4. Confusing environmental novelty with creative productivity.** Changing your workspace every week, working from exotic locations, and curating an aesthetically perfect studio are all forms of environmental optimisation that can become displacement activities. The setting serves the work. It is not the work. + +**5. Ignoring analytical data in favour of "intuition."** the book's framework places awareness before analysis, not above it. The entrepreneur who dismisses churn metrics, financial projections, or user feedback because they are "tuning in to a deeper signal" has elevated one mode of knowing while dismantling the other. Both are required. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Broadening the vessel; maximum receptivity | The task is to perceive widely before filtering narrowly; premature focus on a single market or concept constricts the antenna | +| Validation | Listening to customers without the filter of confirmation | Awareness-based customer discovery detects signals that structured interviews miss | +| Early Traction | Noticing what the product is "trying to become" | The product itself sends signals through usage patterns, support tickets, and unexpected use cases; the founder's job is to perceive them | +| Growth | Detecting weak signals amid operational noise | As the organisation generates more data, the analytical mode threatens to drown out perceptual insight; deliberate awareness practices become essential | +| Scale | Distributing perceptual capacity across the organisation | The founder alone cannot be the company's antenna; building teams and cultures that value perception alongside analysis is the institutional challenge | + +At the idea stage, the vessel is relatively empty and the filter relatively soft -- which is an advantage. The discipline is to resist the pressure to narrow too quickly. Advisors, accelerators, and investors will demand focus. Some of that demand is legitimate. But the entrepreneur who narrows before perceiving broadly will build on a foundation of insufficient information. the book's reminder that "the universe is only as large as our perception of it" applies directly: the founder's market is only as large as their awareness allows it to be. + +At validation, the perceptual challenge is confirmation bias. The filter hardens around the hypothesis the founder wants to be true. the book's counsel to practice awareness "without attachment or involvement" is the antidote: listen to customers without an agenda, observe usage patterns without imposing a narrative, and resist the reflex to interpret ambiguous signals as validation. The whisper that contradicts your thesis may be more valuable than the shout that confirms it. + +At early traction, the product itself becomes a perceptual object. It sends signals through the way customers use it -- including the ways they use it that were never intended. The founder's job shifts from perceiving the market to perceiving their own creation with fresh eyes. "You can't step into the same stream twice because it's always flowing," the text argues. The product is flowing too. Perceiving its evolution -- rather than insisting it match the original vision -- is how companies discover their true value proposition. + +At growth, the signal-to-noise ratio deteriorates. Dashboards, OKRs, quarterly reviews, and board meetings generate a torrent of analytical data that can drown the subtler perceptual signals. The founder who once noticed a customer's hesitation in a demo now receives that information thirdhand, filtered through layers of reporting. Deliberate practices -- unscripted customer conversations, time spent using the product as a customer would, environmental shifts away from the office -- become essential to maintain perceptual acuity. + +At scale, the challenge is delegation. The founder's personal perceptual sensitivity cannot serve a thousand-person organisation. The question becomes: how do you hire, train, and organise for collective awareness? Companies that solve this problem build products with an uncanny ability to anticipate market shifts. Those that do not become operationally excellent and creatively inert. Embedding the book's "look for clues" mentality into product teams, design sprints, and customer-facing roles transforms perception from a founder's personal gift into an organisational capability. + +--- + +## Output Template + +```markdown +# Creative Perception Assessment -- [Company/Project] + +**Date:** [Date] +**Context:** [Specific creative challenge or general perceptual audit] + +## Current Signal Diet + +| Source | Type (Analytical / Perceptual) | Frequency | Quality (H/M/L) | +|--------|-------------------------------|-----------|------------------| +| [e.g., Usage dashboards] | Analytical | Daily | [H/M/L] | +| [e.g., Customer conversations] | Mixed | Weekly | [H/M/L] | +| [e.g., Nature / stillness] | Perceptual | [Frequency] | [H/M/L] | +| [e.g., Art / unrelated industries] | Perceptual | [Frequency] | [H/M/L] | + +## Vessel and Filter Diagnosis + +**Vessel capacity:** [Expansive / Adequate / Constricted] +**Filter rigidity:** [Soft / Moderate / Hardened] +**Dominant beliefs shaping the filter:** [List 3-5 assumptions about market, product, or identity] +**Signals likely being blocked:** [What might I not be seeing?] + +## Awareness Practice Plan + +| Practice | Frequency | Duration | Purpose | +|----------|-----------|----------|---------| +| [e.g., Morning awareness walk] | Daily | 20 min | Broaden perceptual baseline | +| [e.g., Unscripted customer conversation] | Weekly | 30 min | Deep listening without agenda | +| [e.g., Clue journal] | Daily | 5 min | Record unexpected resonances | +| [e.g., Environmental shift] | Weekly | 2 hours | Change setting to change perception | + +## Clues Detected This Period +1. [Observation + where it came from + potential relevance] +2. [Observation + where it came from + potential relevance] +3. [Observation + where it came from + potential relevance] + +## Next Step +[Specific action informed by perceptual insight] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](creative-identity-and-purpose.md)** -- Perception without creative identity is data collection; identity provides the purpose that directs awareness. +- **[Creative Practice and Habit](creative-practice-and-habit.md)** -- Awareness must be practised daily to become a default mode; this skill provides the discipline structures. +- **[Creative Obstacles](creative-obstacles.md)** -- Self-doubt and distraction are the primary enemies of perceptual clarity; this skill addresses them directly. +- **[Flow State](../frameworks/flow-state.md)** -- Csikszentmihalyi's flow describes the psychological state the awareness practices are designed to access, approached from a theoretical angle. +- **[Stoic Self-Awareness](../stoic/stoic-self-awareness.md)** -- Stoic self-examination operates through rational inquiry; creative awareness operates through perceptual sensitivity -- complementary paradigms for the same goal. +- **[Finding Your Stories](../storytelling/finding-your-stories.md)** -- The Homework for Life practice is a specific application of perceptual awareness: training oneself to notice the story-worthy moments that most people overlook. diff --git a/plugins/foreman/content/skills/creative/creative-practice-and-habit.md b/plugins/foreman/content/skills/creative/creative-practice-and-habit.md new file mode 100644 index 0000000..857b133 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-practice-and-habit.md @@ -0,0 +1,199 @@ +--- +name: "creative-practice-and-habit" +description: "Transforms creativity from sporadic inspiration into daily discipline by applying principles of practice, habit formation, seed collection, experimentation, immersion in great works, and momentum management. Use when struggling to maintain a creative routine, waiting for inspiration to strike, unsure how to develop raw ideas into viable products, losing creative momentum mid-project, or wanting to improve the quality of creative inputs to elevate outputs." +version: "1.0.0" +category: "creative" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - practice + - habits + - experimentation + - momentum + - seeds + - discipline + - craft + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-perception-and-awareness + - creative-obstacles + - flow-state + - stoic-right-action + - stoic-pragmatism + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +# Daily Reps + +The text's vision of creativity is not waiting for lightning. It is a muscular practice. Plant seeds, water them, wait. "Good habits create good art," he writes, with the kind of plainness that disguises a radical claim. "The way we do anything is the way we do everything." The romantic image of the artist seized by divine inspiration -- scribbling furiously at 3 a.m., unable to stop -- is not false, but it is incomplete. What the romance omits is the years of disciplined preparation that made the 3 a.m. seizure possible. John Wooden, the most successful coach in college basketball history, spent the first day of every season teaching elite athletes to tie their shoes. The entrepreneur who believes creative breakthroughs happen to people rather than being cultivated by them will spend a career waiting for a moment that preparation would have summoned. + +--- + +## The Framework + +### The Four Phases of Creative Discipline + +the book's approach to creative practice follows a natural progression -- from gathering raw material through experimentation to craft and ultimately release. Each phase demands a different kind of discipline. + +**Phase 1: Seeds -- Gathering Without Judgement** + +"In the first phase of the creative process, we are to be completely open, collecting anything we find of interest." the text calls these collected fragments "seeds" -- phrases, observations, sketches of ideas, customer complaints, unusual interactions, fragments of conversation. The critical discipline in this phase is non-evaluation. "As the seeds arrive, forming conclusions about their value or fate can get in the way of their natural potential." The entrepreneur who immediately judges every idea against ROI projections, market size, or technical feasibility kills seeds before they can germinate. + +the book's guidance is patient: "It's generally preferable to accumulate several weeks' or months' worth of ideas and then choose which of them to focus on, instead of following an urge or obligation to rush to the finish line with what is in front of us today." For the entrepreneur, this translates to maintaining an active idea journal -- not a business plan, not a feature backlog, but a raw, unjudged collection of observations and possibilities. + +**Phase 2: Experimentation -- Play Without Stakes** + +"Fueled by the initial hit of excitement at discovering a starting point, we play with different combinations and possibilities to see if any of them reveal how the seed wants to develop." This is the phase most entrepreneurs skip. The pressure to build, ship, and measure drives founders directly from idea to execution, bypassing the experimental stage where the idea reveals its true form. + +the text is explicit about what experimentation requires: "This is one of the fun parts of a project, because nothing is at stake. You get to play with forms and see what takes shape. There are no rules." The entrepreneur's equivalent is the rapid prototype, the low-fidelity mockup, the "what if" conversation with a trusted collaborator. Ancient Chinese alchemists searching for immortality stumbled upon gunpowder. Penicillin, plastic, pacemakers, and Post-it notes were all accidents of experimentation. "Consider how many innovations that might have changed the world have been lost because someone was so focused on their goal, they missed the revelation right in front of them." + +The selection criterion during experimentation is emotional, not analytical. "Often the most accurate signposts are emotional, not intellectual. Excitement tends to be the best barometer for selecting which seeds to focus on." + +**Phase 3: Try Everything -- Testing Before Judging** + +"To dismiss an idea because it doesn't work in your mind is to do a disservice to the art. The only way to truly know if any idea works is to test it." the text insists that ideas must be physically manifested -- built, spoken, drawn, performed -- before they can be evaluated. "Descriptions do not do ideas justice." This principle has direct application to product development: the feature that sounds mediocre in a brainstorm may prove transformative in a prototype. The strategy that seems brilliant on a whiteboard may collapse on contact with a real customer. + +The corollary is equally powerful: "Persuasion leads to mediocrity." In team settings, the most articulate advocate often wins the debate -- but articulation is not the same as quality. the book's method demands that competing ideas be tested rather than argued. + +**Phase 4: Momentum -- The Craft of Finishing** + +"When we become overly attached to a premature version of the work, we do a disservice to the project's potential." the text identifies two momentum killers with precision. The first is disconnection: lingering too long in the craft phase until the artist has changed and the work no longer reflects who they are. The second is "demo-itis" -- becoming so attached to an early draft that any improvement feels like betrayal. + +His tactical advice is concrete: "Unless actively working to make something better, avoid listening to it, reading it, playing it, looking at it, or showing it to friends." For the entrepreneur, this means resisting the urge to endlessly revisit mockups, re-read pitch decks, or demo unfinished products to friends. Work forward. Step away. Return with fresh perception. + +### The Infrastructure of Habit + +Surrounding the four phases is the book's broader philosophy of habit formation. "Discipline and freedom seem like opposites. In reality, they are partners. Discipline is not a lack of freedom, it is a harmonious relationship with time." The practical implications: + +- **Start small.** "If you commit to working for half an hour a day, something good can happen that generates momentum. You may then look at the clock and realize you've been working for two hours." +- **Reduce life-maintenance decisions.** "Albert Einstein wore the same thing daily: a gray suit. Erik Satie had seven identical outfits. Limit your practical choices to free your creative imagination." +- **Examine existing habits before adding new ones.** "How often do we consider examining and removing the habits that currently drive our days?" +- **Separate creative time from administrative time.** "Approaching the practical aspects of your day with military precision allows the artistic windows to be opened in childlike freedom." + +### Submerge: The Quality of Inputs + +"Consider submerging yourself in the canon of great works. Read the finest literature, watch the masterpieces of cinema, get up close to the most influential paintings." the text frames input quality as a creative practice, not a leisure activity. "If you make the choice of reading classic literature every day for a year, rather than reading the news, by the end of that time period you'll have a more honed sensitivity for recognising greatness." The entrepreneur's version: study the best companies, the most elegant products, the most powerful brands -- not to imitate them but to calibrate your internal standard. "The objective is not to learn to mimic greatness, but to calibrate our internal meter for greatness." + +--- + +## Prompts + +**Prompt 1 -- Seed Collection Protocol:** +> I am a founder of [company] at the [stage] stage. Design a 30-day seed collection practice for me. Include: what to observe, where to look, how to record seeds without judging them, and a review cadence for assessing which seeds show life. Tailor the observation domains to my industry ([industry]) and the specific creative challenges I face ([challenges]). + +**Prompt 2 -- Experimentation Sprint Design:** +> I have [number] raw ideas / seeds for [product feature / business concept / brand direction]. Design an experimentation sprint where each idea is physically tested -- not discussed or debated -- within [timeframe]. For each idea, specify: the lowest-fidelity way to manifest it, who should experience it, and what emotional/energetic response to watch for as a signal of viability. + +**Prompt 3 -- Creative Habit Architecture:** +> Analyse my current daily and weekly routine: [describe schedule]. Using the book's habit principles, identify: (a) where creative time is being consumed by administrative decisions, (b) which existing habits may be undermining creative output, (c) a restructured schedule that creates dedicated creative windows with minimal decision overhead. Start small -- thirty minutes daily. + +**Prompt 4 -- Input Quality Audit:** +> Catalogue my current creative inputs -- what I read, watch, listen to, and engage with regularly. Using the book's "submerge in great works" principle, assess whether my inputs are calibrating my taste upward or merely reinforcing existing patterns. Recommend a 90-day input diet tailored to [my industry / the creative challenge I face], including specific works, companies, and experiences to engage with. + +--- + +## Use Cases + +**Idea-stage founder who "can't find" a good idea** + +A technical co-founder has spent four months reading market reports and trend analyses, waiting for a startup idea that passes his analytical filters. He has rejected dozens of concepts as "too small," "too competitive," or "not defensible." Applying the book's seed collection principle reframes the problem: he has been evaluating seeds at the moment of arrival, killing them before they can germinate. A thirty-day non-judgemental collection practice -- recording every observation, frustration, and curiosity in a dedicated journal -- yields 147 seeds. During the review, seed number eighty-three (an offhand complaint from his mother about managing her medications) connects with seed number twelve (a technical insight about voice interfaces) and produces a concept he would never have reached through analysis alone. + +**Early-traction team stuck in "analysis paralysis" over a feature direction** + +A product team has spent three weeks debating two feature directions for their next release. Each side has compelling data and articulate advocates. Applying the book's "try everything" principle breaks the deadlock: both features are prototyped at minimum fidelity in forty-eight hours and tested with five users each. The feature that sounded weaker in debate produces visibly more energetic user responses. It ships in two weeks and drives a 22% increase in engagement. + +**Growth-stage founder losing creative edge** + +A founder who built her company on creative instinct now spends 80% of her time in operational meetings, investor updates, and hiring reviews. Her last three product decisions were competent but uninspired. The creative habit architecture intervention reveals that she has no dedicated creative time -- not thirty minutes, not ten. Restructuring her week to include two ninety-minute creative blocks (protected from all meetings and communications) and replacing her morning news consumption with exposure to great design, architecture, and literature begins to restore the creative sensitivity that built the company. + +--- + +## Anti-Patterns + +**1. Collecting seeds forever without experimenting.** The seed phase has a natural rhythm. Accumulate for weeks or months, then shift to experimentation. The entrepreneur who has been "gathering ideas" for two years without testing any of them is not practising patience -- they are practising avoidance. + +**2. Skipping experimentation and jumping to execution.** The pressure to ship is real, but the cost of building the wrong thing is higher than the cost of a week spent experimenting. The founder who moves from idea to Jira ticket without a prototyping phase will build efficiently and often build the wrong thing. + +**3. Evaluating experiments analytically during the experimental phase.** the text is clear that the early signals are emotional, not intellectual. Subjecting a rough prototype to a formal ROI analysis is like judging a seedling by the fruit it has not yet produced. Follow energy first. Apply rigour later. + +**4. Confusing routine with rigidity.** Creative habits should evolve. the text notes that "awareness needs constant refreshing. If it becomes a habit, even a good habit, it will need to be reinvented again and again." The founder whose creative routine has not changed in two years may have a schedule, but not a practice. + +**5. Using "submerge in great works" as sophisticated procrastination.** Reading, watching, and studying are creative inputs. They are not creative outputs. The entrepreneur who spends six months consuming masterpieces without producing anything has inverted the relationship between input and output. Inputs serve the work. The work must still be done. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Seed collection and early experimentation | Maximum openness; the discipline is gathering without judging, not building without thinking | +| Validation | Rapid experimentation cycles | Seeds are tested against real users; emotional signals are validated with behavioural data | +| Early Traction | Habit architecture for founder creative time | As operational demands grow, creative time must be structurally protected or it vanishes | +| Growth | Input quality and team creative practices | The founder's creative habits must scale; input diet and experimentation become team disciplines | +| Scale | Institutional creative infrastructure | Seed collection, experimentation, and creative time are embedded in product development processes, not dependent on individual heroics | + +At the idea stage, the entire company is a creative practice. There is nothing else. The founder's daily life is seed collection, experimentation, and the gradual emergence of a concept worth building. The discipline is restraint: not committing too early, not judging too harshly, not confusing analytical rigour with creative clarity. + +At scale, the founder's personal creative practice matters less than the organisation's creative infrastructure. The question shifts from "how do I maintain my creative habits?" to "how does this company experiment, collect seeds, and maintain creative momentum at the institutional level?" Companies that answer this question build products that continue to surprise. Those that do not become efficient executors of yesterday's ideas. + +--- + +## Output Template + +```markdown +# Creative Practice Plan -- [Company/Project] + +**Date:** [Date] +**Phase:** [Seed Collection / Experimentation / Craft / Momentum] + +## Current Seed Inventory +| # | Seed (Raw Observation/Idea) | Date Collected | Energy Level (H/M/L) | Status | +|---|---------------------------|----------------|----------------------|--------| +| 1 | [Description] | [Date] | [H/M/L] | [Dormant / Sprouting / Testing] | +| 2 | [Description] | [Date] | [H/M/L] | [Status] | +| 3 | [Description] | [Date] | [H/M/L] | [Status] | + +## Experimentation Queue +| Seed # | Experiment Design | Fidelity | Duration | Signal to Watch For | +|--------|------------------|----------|----------|-------------------| +| [#] | [How to test] | [Low/Med] | [Hours/Days] | [Emotional/energetic response] | + +## Creative Habit Architecture +| Time Block | Activity | Purpose | Frequency | +|-----------|----------|---------|-----------| +| [e.g., 6:00-6:30 AM] | [e.g., Awareness walk] | Perceptual baseline | Daily | +| [e.g., 9:00-10:30 AM] | [e.g., Protected creative work] | Experimentation / craft | Daily | +| [e.g., Lunch break] | [e.g., Great works input] | Taste calibration | 3x weekly | + +## Input Diet (Current Quarter) +| Medium | Specific Work/Source | Why | +|--------|---------------------|-----| +| Reading | [Title] | [Connection to current creative challenge] | +| Visual | [Film/Exhibition/Product] | [What it calibrates] | +| Experience | [Place/Activity] | [What it opens] | + +## Momentum Status +**Current project phase:** [Phase] +**Days since last forward progress:** [Number] +**Risk of demo-itis:** [Low / Medium / High] +**Next action to maintain momentum:** [Specific step] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](creative-identity-and-purpose.md)** -- Practice without identity is mere routine; identity provides the creative purpose that sustains discipline through resistance. +- **[Creative Perception and Awareness](creative-perception-and-awareness.md)** -- Seed collection depends on perceptual sensitivity; the sharper the awareness, the richer the raw material for practice. +- **[Creative Obstacles](creative-obstacles.md)** -- Self-doubt, distraction, and the inner critic are the forces that derail creative practice; this companion skill addresses them directly. +- **[Flow State](../frameworks/flow-state.md)** -- The creative habits are designed to facilitate the conditions Csikszentmihalyi identifies as prerequisites for flow: clear goals, immediate feedback, and challenge-skill balance. +- **[Stoic Right Action](../stoic/stoic-right-action.md)** -- The Stoic emphasis on daily discipline and doing the work regardless of outcome aligns with the philosophy that practice is not about results but about showing up. +- **[Writing Process](../writing/writing-process.md)** -- The MACJ framework provides a structured creative process that applies the same principle of separating generation from judgment that creative practice depends on. diff --git a/plugins/foreman/content/skills/creative/creative-shaping-and-craft.md b/plugins/foreman/content/skills/creative/creative-shaping-and-craft.md new file mode 100644 index 0000000..9aca316 --- /dev/null +++ b/plugins/foreman/content/skills/creative/creative-shaping-and-craft.md @@ -0,0 +1,201 @@ +--- +name: "creative-shaping-and-craft" +description: "Guides the entrepreneur through shaping raw creative material into disciplined form, applying intention, rules, temporary constraints, assumption reversal, point-of-view discovery, pattern-breaking, and distillation to essence. Use when refining a product concept, setting creative direction for a brand, defining project constraints, challenging default assumptions about market or offering, finding a unique positioning voice, breaking creative stagnation, or stripping a pitch or product to its irreducible core." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creative-process + - craft + - constraints + - intention + - essence + - refinement + - point-of-view + - assumptions +related_skills: + - creative-flow-and-inspiration + - creative-completion-and-renewal + - creative-collaboration-and-context + - blue-ocean-strategy +author: "Fatih Guner" +--- + +# Shaping and Craft + +Michelangelo claimed he never created a sculpture. He simply removed the stone that was not the statue. The figure was already there -- trapped, waiting, fully formed inside the marble. His job was subtraction. The text describes the creative process in strikingly similar terms: "Distilling a work to get it as close to its essence as possible is a useful and informative practice. Notice how many pieces you can remove before the work you're making ceases to be the work you're making." For the entrepreneur, this principle is both liberating and ruthless. The product, the pitch, the brand -- none require more. They require less. The discipline of shaping is not the discipline of addition. It is the discipline of finding what was always there and cutting away everything that obscures it. + +--- + +## The Framework + +the book's approach to shaping creative work moves through seven interconnected dimensions. They are not sequential steps so much as lenses -- each refracts the same raw material differently, and the craftsperson rotates between them as the work demands. + +### 1. Intention -- The Invisible Architecture + +Every creative act carries a single animating purpose. the text calls it "the grand gesture of the work." Intention is not a business plan, not a goal statement, not a mission deck. It is the alignment of conscious purpose with unconscious conviction: "It requires an alignment of all aspects of one's self. Of conscious thought and unconscious beliefs, of capabilities and commitment." + +The old man drawing water from a well by hand, the text recounts, refused the pulley because mechanisation would drain the care from the act -- and with it, the quality. Intention is the care embedded in every decision. Remove intention and all that remains is "the ornamental shell." + +For the entrepreneur, this means a product built without genuine conviction about the problem it solves will feel hollow regardless of its technical elegance. Customers sense the difference between work animated by purpose and work assembled by process. + +### 2. Rules -- Assumptions Masquerading as Laws + +the text draws a sharp distinction between natural laws and artistic rules: "The rules artists learn are different. They are assumptions, not absolutes." Every industry carries invisible conventions -- pricing models, feature sets, go-to-market sequences, pitch deck formats -- that participants mistake for physical constraints. "Rules direct us to average behaviours. If we're aiming to create works that are exceptional, most rules don't apply." + +The most dangerous rules are the unconscious ones: "Rules obeyed unconsciously are far stronger than the ones set on purpose." A founder who has never questioned why SaaS products charge monthly, or why pitch decks open with the problem slide, is operating under rules they did not choose and may not even recognise. + +### 3. Temporary Rules -- Constraints as Liberation + +Paradoxically, the path to creative freedom often runs through deliberate limitation. Georges Perec wrote an entire novel without the letter "e." Yves Klein restricted his palette to a single shade and discovered a blue the world had never seen. Lars von Trier's Dogme 95 manifesto imposed ten severe filmmaking constraints; the first film made under those rules won the Jury Prize at Cannes. + +the book's principle: "When you accept limitations, your range of choices is reduced. Whether imposed by design or by necessity, it's helpful to see limitations as opportunities." Novel problems lead to original solutions. The entrepreneur who tells a product team "build this feature using only what we have today, with no new dependencies" is not imposing poverty. They are imposing a temporary rule that will force invention. + +### 4. The Opposite Is True -- Assumption Reversal + +For every rule accepted -- what the product must be, what the brand voice sounds like, what the customer expects -- the text advises trying the opposite. "Think of a rule as an imbalance. Darkness and light are only meaningful in relationship with each other." + +This is not contrarianism for its own sake. It is a diagnostic exercise. By imagining the polar opposite of every core assumption, the entrepreneur maps the full spectrum of possibility and discovers where on that spectrum they have unconsciously planted themselves. Sometimes the opposite reveals a superior approach. More often, it sharpens understanding of why the current approach works -- or exposes the specific point where it does not. + +### 5. Point of View -- Your Filter Is the Product + +"Carl Rogers said, 'The personal is the universal,'" the text notes. "The personal is what makes art matter. Our point of view, not our drawing skills or musical virtuosity." + +A point of view is not a positioning statement. It is not constructed; it is emitted. The Beatles did not set out to sound different from Chuck Berry. They were different, and the sound followed. the text distinguishes between a "point" (an idea intentionally expressed) and a "point of view" (the perspective through which work emerges, often unconsciously). Entrepreneurs who try to manufacture a distinctive brand voice through copywriting exercises miss the deeper truth: the voice already exists in the decisions the founder makes, the trade-offs they accept, the customers they choose to serve. + +### 6. Breaking the Sameness -- Pattern Disruption + +When shaping stalls, the work needs disruption, not persistence. the text catalogues a battery of techniques from his studio practice: change the environment, change the stakes, invite an audience, alter the perspective, write for someone else, add imagery, limit the information. The underlying principle is consistent: "Whatever you choose, decide on a framework that breaks your normal rhythm and see where it leads." + +The entrepreneurial translation is direct. When a product development cycle has plateaued, the team needs not another sprint but a different vantage point -- a customer segment they have never studied, a constraint they have never imposed, a competitor's lens through which to view their own offering. + +### 7. Essence -- The Skeleton Test + +"All the work we do, no matter how intricate, holds an underlying essence. A core identity or fundamental structure, like a skeleton supporting flesh." the text uses the image of a child's drawing of a house: remove the window and it is still a house; remove the door and it is still a house; remove the roof and walls but leave the window and door and it ceases to be recognisable. + +The practice of distillation demands asking: which elements, if removed, would cause this product (or pitch, or brand) to stop being itself? Everything else is ornamentation. Saint-Exupery's maxim, which the text quotes, is the governing law: "Perfection is finally obtained not when there is no longer anything to add, but when there's no longer anything to take away." + +--- + +## Prompts + +**Prompt 1 -- Intention Audit:** +> Examine my product/venture: [describe product, market, and founding motivation]. Identify the single animating intention behind this work -- not the business goal, but the deeper conviction that gives the project its energy. Then assess whether my current strategy, messaging, and product decisions are congruent with that intention or have drifted from it. Where is the ornamental shell overtaking the living purpose? + +**Prompt 2 -- Invisible Rules Inventory:** +> List every assumption I am operating under regarding [product category, pricing, distribution, customer segment, pitch format]. For each assumption, identify whether it is a law of nature (immutable), a useful convention (worth following for now), or an unexamined rule masquerading as a law. For the unexamined rules, describe what would happen if I violated each one deliberately. + +**Prompt 3 -- Temporary Constraint Design:** +> My team is stuck on [describe the stalled creative or product challenge]. Design three sets of temporary constraints, inspired by the book's principle that novel problems lead to original solutions. Each constraint set should eliminate a different assumed resource or method. For each, describe the type of innovation the constraint is likely to force and when the constraint should be released. + +**Prompt 4 -- Essence Distillation:** +> Here is my current [pitch / product feature set / brand narrative]: [paste content]. Apply the skeleton test: systematically remove elements one at a time and identify the point at which the work ceases to be itself. What remains is the essence. Present the distilled version and explain what was removed and why it was ornamentation rather than structure. + +--- + +## Use Cases + +**Validation-stage consumer app stripping to essence** + +A founder has built an MVP with fourteen features after six months of customer interviews. Early testers describe the product as "interesting but confusing." Applying the skeleton test, the team removes features one by one, testing each stripped version with five users. At feature number six, they discover that three features alone produce the "this is useful" reaction. The remaining eleven features, each individually justified by a customer interview quote, are ornamentation that obscures the product's core identity. The stripped version launches to three times the activation rate. + +**Growth-stage B2B company breaking the sameness** + +A SaaS company's quarterly product reviews have become formulaic: the same data, the same format, the same incremental improvements. The VP of Product imposes a temporary rule from the book: each product team must present their next quarter's roadmap as if they were building for a completely different customer segment than their current one. The exercise surfaces three feature ideas that would never have emerged from the existing roadmap process -- two of which prove viable for the actual customer base. + +**Early-traction brand discovering its point of view** + +A direct-to-consumer brand has hired three branding agencies in two years, each producing style guides that feel generic. The founder applies the book's distinction between "having a point" and "having a point of view." Instead of commissioning another positioning exercise, she catalogues every decision she has made that competitors would not have made -- the materials rejected, the markets declined, the partnerships refused. The pattern reveals a point of view that was always present but never articulated. The brand voice emerges from those decisions, not from a workshop. + +**Scale-stage enterprise trying the opposite** + +A market-leading enterprise software company has optimised its onboarding funnel for five years. Conversion is strong but growth has plateaued. The product leadership team runs the book's assumption-reversal exercise on their ten core onboarding beliefs. One belief -- "users must complete a guided setup before accessing the product" -- has never been questioned. They try the opposite: drop new users directly into a fully configured demo environment with no setup at all. The variant produces a 22% improvement in seven-day retention. The guided setup, designed to reduce friction, was itself the friction. Five years of optimising around the wrong assumption had concealed the issue because the assumption was invisible. + +--- + +## Anti-Patterns + +**Confusing subtraction with minimalism as aesthetic.** Distilling to essence does not mean making everything spare and clean. A maximalist product can be at its essence. The question is whether every element is structural, not whether there are few elements. Stripping a product to look minimal while removing features users depend on is cosmetic surgery, not sculpture. + +**Imposing temporary rules that become permanent doctrine.** the text warns that "every innovation risks becoming a rule." A constraint that produced a breakthrough in one product cycle can calcify into policy. The point of temporary rules is their temporariness. Review and retire them. + +**Intellectualising intention instead of living it.** Intention, in the book's framework, is not a statement you write on a whiteboard. It is a state of alignment between belief and action. A founder who crafts a beautiful mission statement but makes decisions that contradict it has a decoration, not an intention. The work will reflect the actual intention, not the stated one. + +**Trying the opposite as a stunt rather than a diagnostic.** Assumption reversal is a tool for mapping possibility, not a mandate to be contrarian. A founder who inverts every industry norm without understanding why those norms exist is not practising creative shaping -- they are practising recklessness. + +**Skipping the craft phase because it lacks glamour.** the text is blunt: "In some ways, the Craft phase is one of the least glamorous parts of the artist's job." Entrepreneurs who love ideation but resist the labour of refinement produce work that is perpetually unfinished. The seed phase has "little purpose or meaning on its own." Completing the work is what gives early inspiration its value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Intention clarity and assumption inventory | The founder has maximum freedom to question every rule; the danger is having no rules at all, which produces drift rather than liberation | +| Validation | Temporary constraints and essence testing | Customer feedback provides the external pressure that reveals which elements are structural; the skeleton test becomes empirical rather than intuitive | +| Early Traction | Point of view crystallisation | The brand's voice must emerge from accumulated decisions; this is the stage where the founder's filter becomes visible and worth articulating | +| Growth | Breaking the sameness and pattern disruption | Established processes and successful formulas begin to calcify; deliberate disruption prevents the company from optimising itself into irrelevance | +| Scale | Assumption reversal and rule auditing | At scale, unconscious rules are most entrenched and most dangerous; systematic reversal exercises surface the assumptions that could blind the organisation to market shifts | + +The intermediate stages -- validation and early traction -- are where shaping has its highest leverage. Raw material is abundant but form is undefined. The founder who can hold intention clearly while ruthlessly distilling to essence will build products that customers describe as "obvious in retrospect." That retrospective obviousness is the hallmark of work that has been shaped to its skeleton. + +At the idea stage, the founder faces a peculiar version of the rules problem: with no established product, there are no explicit rules to break, yet the founder's mind is saturated with implicit rules inherited from the industry they came from, the products they have used, and the business models they have studied. The invisible rules inventory is most productive at this stage precisely because there is no organisational inertia resisting the findings. + +At growth and scale, the shaping challenge inverts. The company's own past successes have become the rules. the book's warning -- "every innovation risks becoming a rule" -- applies directly to the product team that treats last year's winning formula as this year's operating manual. The assumption-reversal exercise at scale is not a creative workshop; it is a strategic survival practice. + +--- + +## Output Template + +```markdown +# Creative Shaping Audit -- [Product/Project Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Intention Statement +[One sentence: the single animating conviction behind this work -- not the business goal] + +## Rules Inventory + +| Rule/Assumption | Source (Industry / Founder / Culture) | Type (Law / Convention / Unexamined) | Opposite | Verdict | +|----------------|--------------------------------------|--------------------------------------|----------|---------| +| [Rule] | [Source] | [Type] | [What the opposite looks like] | [Keep / Question / Break] | + +## Temporary Constraints for Current Challenge +- **Constraint 1:** [Description] -- Expected effect: [What it forces] +- **Constraint 2:** [Description] -- Expected effect: [What it forces] +- **Expiry date:** [When to review and release] + +## Skeleton Test Results +- **Elements tested:** [List] +- **Structural elements (cannot remove):** [List] +- **Ornamentation (can remove):** [List] +- **Distilled essence:** [One sentence] + +## Point of View Evidence +[Decisions made that competitors would not have made -- the pattern reveals the voice] +1. [Decision] +2. [Decision] +3. [Decision] + +## Next Shaping Action +[Specific next step with timeline] +``` + +--- + +## Related Skills + +- **[Creative Flow and Inspiration](creative-flow-and-inspiration.md)** -- Flow provides the raw material that shaping refines; inspiration without craft is a seed that never germinates. +- **[Creative Completion and Renewal](creative-completion-and-renewal.md)** -- Shaping is the middle act; completion addresses the distinct challenge of releasing shaped work into the world. +- **[Creative Collaboration and Context](creative-collaboration-and-context.md)** -- Collaboration introduces additional lenses through which to shape; the prism of another person's perspective can reveal structural elements the solo creator misses. +- **[Blue Ocean Strategy](../frameworks/blue-ocean-strategy.md)** -- Blue Ocean's value innovation framework provides a systematic method for essence-finding: eliminate, reduce, raise, create. +- **[Story Structure and Arc](../storytelling/story-structure-and-arc.md)** -- Narrative shaping is a specific application of creative craft; the five-second moment and But-and-Therefore momentum are structural shaping techniques applied to story. +- **[Revising and Editing](../writing/revising-and-editing.md)** -- The structured editing methodology provides the specific techniques for the refinement phase of shaping written creative work. diff --git a/plugins/foreman/content/skills/decisions/choosing-and-executing.md b/plugins/foreman/content/skills/decisions/choosing-and-executing.md new file mode 100644 index 0000000..fc2c67c --- /dev/null +++ b/plugins/foreman/content/skills/decisions/choosing-and-executing.md @@ -0,0 +1,244 @@ +--- +name: "choosing-and-executing" +description: "Provides a toolkit for moving from deliberation to commitment and from commitment to results. Covers the cost of decision paralysis, the 70% rule for when to stop gathering information, implementation planning after the choice is made, transparency as a trust mechanism, handling challenges to decisions, and combating second-guessing through process review rather than outcome regret. Use when stuck in analysis paralysis, when a decision has been made but needs implementation momentum, when stakeholders challenge or resist a decision, when second-guessing erodes confidence, or when building a decision communication plan." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - analysis-paralysis + - commitment + - implementation + - decision-communication + - transparency + - second-guessing + - hindsight-bias + - reversibility + - decision-execution + - stakeholder-trust +related_skills: + - evaluating-and-deciding + - tough-decision-situations + - decision-making-under-pressure + - learning-from-failure + - trust-equation + - wanting-what-matters +author: "Fatih Guner" +--- + +# Choosing and Executing + +The cost of searching for the perfect decision almost always exceeds the cost of making a "good enough" one and iterating. Scott McNealy, cofounder of Sun Microsystems, captured this asymmetry in a single observation: he spent far less energy worrying about making the right decision and far more ensuring that any decision he made turned out right. The distinction is not semantic. It relocates agency from the moment of choice -- where the entrepreneur has minimal control over future variables -- to the months of execution that follow, where nearly everything is within reach. Founders who internalise this shift stop treating decisions as bets to be perfected and start treating them as hypotheses to be tested, adapted, and driven to outcomes through disciplined follow-through. + +--- + +## The Toolkit + +### Technique 1: The Reversibility Test + +Not all decisions deserve equal deliberation. Jeff Bezos famously divided choices into "one-way doors" (irreversible, high-stakes) and "two-way doors" (reversible, correctable). Most entrepreneurial decisions fall through the second door -- yet founders routinely treat them as though they are signing a blood oath. + +**The diagnostic question:** If this decision proves wrong in six months, can the company course-correct without catastrophic loss? If yes, the decision is a two-way door. Make it quickly, monitor outcomes, and adjust. + +**Why founders over-deliberate on two-way doors:** + +- **Identity attachment.** The choice feels like it defines the founder, not just the venture. +- **Anxiety amplification.** Research by Francesca Gino demonstrates that anxiety makes people simultaneously more receptive to advice and less capable of distinguishing good advice from bad -- a dangerous combination that extends deliberation without improving quality. +- **Perfectionism as procrastination.** Waiting for the "objectively correct" answer is often a socially acceptable form of avoidance. + +Reserve deep analysis for one-way doors: market exits, large capital commitments, equity dilution events. Everything else deserves the 70% rule. + +### Technique 2: The 70% Rule + +If a decision has been analysed to the point where approximately 70% of the relevant information is in hand, make the call. The remaining 30% is unlikely to arrive before the cost of delay exceeds the value of marginal certainty. + +**When to apply the rule:** + +- The team has debated the same options across multiple meetings with no new data surfacing. +- The competitive landscape is shifting while internal deliberation continues. +- The decision maker's gut has already settled, but the rational mind insists on "one more data point." + +**When to override the rule:** + +- The decision is genuinely irreversible (shutting down a product line, terminating a co-founder relationship). +- The 70% of information gathered points in contradictory directions -- not ambiguous, but actively conflicting. +- Regulatory or legal constraints demand a higher evidentiary threshold. + +Thomas Davenport suggests a meta-decision framework: decide how to decide. Assess importance, frequency, and urgency before allocating deliberation time. Rare, strategic, high-stakes choices merit extended analysis. Recurring, operational, reversible choices merit a clock -- and when the clock runs out, the decision is made. + +### Technique 3: Buying an Option + +When neither committing nor abandoning is palatable, consider a third move: buy an option. Rather than acquiring a company, form a partnership. Rather than launching nationally, pilot in one city. Rather than hiring a full-time executive, engage a fractional one for ninety days. Options convert large, irreversible decisions into small, reversible experiments -- providing real-world data that no amount of spreadsheet modelling can replicate. + +The discipline here is to treat the option as a learning vehicle, not as a permanent hedge against commitment. Every option must have an expiration date and explicit criteria for converting to a full commitment or walking away. + +### Technique 4: Post-Decision Implementation Protocol + +A decision without an implementation plan is a wish. The moment a choice is finalised, the following elements must be articulated: + +| Element | Purpose | +|---------|---------| +| **Decision statement** | One sentence: what was decided and why | +| **Stakeholder notification list** | Everyone affected, responsible, or accountable | +| **Implementation timeline** | Milestones, deadlines, and checkpoint dates | +| **Success criteria** | How the team will know the decision is working | +| **Escalation triggers** | Conditions under which the decision should be revisited | +| **Owner** | A single accountable individual, not a committee | + +Communicate the decision before rumour fills the vacuum. Include the reasoning process, not merely the conclusion. Research consistently shows that perceived fairness of process predicts acceptance of outcome -- even among those who preferred a different option. + +### Technique 5: Transparency as Trust Architecture + +Being transparent about how a decision was made is not a courtesy; it is a structural investment in trust. Liane Davey's work on organisational fairness identifies two dimensions that teams evaluate simultaneously: outcome fairness (did the result distribute burdens and benefits reasonably?) and process fairness (was the method of arriving at the result legitimate?). + +**The order-of-disclosure effect:** Studies show that when people learn about the process before the outcome, process fairness dominates their satisfaction. When they learn the outcome first, outcome fairness dominates. The practical implication is clear: lead with process. Explain the criteria, the alternatives considered, and the trade-offs weighed before announcing the decision itself. + +Transparency is especially critical when: + +- A decision overrides the preference of a vocal stakeholder. +- Resources are being reallocated from one team or project to another. +- The founder is making a judgment call that cannot be fully supported by data. +- The decision involves equity, compensation, or role changes. + +### Technique 6: Handling Challenges to Decisions + +Three patterns account for the majority of post-decision pushback: + +1. **"You didn't ask me."** A stakeholder feels excluded from the process. The fix is proactive: define decision roles at the outset using frameworks such as RACI or RAPID. If someone was intentionally excluded, be prepared to explain why. + +2. **"I didn't say anything then, but I disagree now."** Late-breaking dissent from someone who was present but silent. Establish the norm: silence denotes agreement. Those who wish to dissent must do so during the decision window, not after. + +3. **"I agreed, but I'm implementing something different."** The most corrosive pattern. The person nominally endorsed the decision but quietly modifies execution to suit their own preference. Counter this with explicit milestones, a single accountable owner, and periodic checkpoints that compare actual implementation against the decision as made. + +**The one legitimate reason to reopen:** new facts have emerged that materially alter the calculus. Changed opinions, second thoughts, or political manoeuvring do not qualify. + +### Technique 7: Defeating Second-Guessing + +Second-guessing is not rigorous reassessment; it is anxiety wearing a rational costume. Sydney Finkelstein's research identifies its cost: a founder who second-guesses a hire actively undermines that hire's probability of success, creating a self-fulfilling prophecy that validates the original doubt. + +**The antidotes:** + +- **Perspective calibration.** Ask: what are the actual stakes of this decision? Many choices that consume disproportionate mental energy have surprisingly low consequence. Redirect attention to decisions that genuinely matter. +- **Gut journalling.** Maintain a log of past decisions and their outcomes. Over time, this record builds calibrated self-trust and reveals whether intuition is a reliable signal or a noisy one. +- **Advisory polling.** When doubt persists, consult two or three trusted advisers -- not for validation, but for perspective. The act of articulating the decision to another person often resolves the uncertainty before the adviser even responds. +- **Scheduled review.** Set a specific date to formally revisit the decision. Between now and that date, execute with full commitment. This converts open-ended rumination into bounded, productive monitoring. +- **Process-outcome separation.** Judge decisions by the quality of the process that produced them, not by the outcome that followed. A sound process that yields a bad outcome is not a bad decision -- it is a reminder that the world contains irreducible uncertainty. Confusing process quality with outcome quality is the hallmark of hindsight bias. + +--- + +## Prompts + +**Prompt 1 -- Paralysis Diagnostic:** +> I have been deliberating on [describe decision] for [time period]. List the information I already have versus the information I am still seeking. For each missing piece of information, estimate: (a) how long it will take to obtain, (b) how much it would change the decision if obtained, and (c) the cost of waiting. Then recommend whether to decide now or continue gathering data. + +**Prompt 2 -- Implementation Blueprint:** +> I have decided to [describe decision]. Draft an implementation plan that includes: a one-sentence decision statement, stakeholder notification list, milestone timeline, success criteria, escalation triggers, and the single accountable owner. Tailor it to a [stage] startup in [sector]. + +**Prompt 3 -- Decision Communication Script:** +> I need to communicate [describe decision] to my team. Some members preferred a different option. Draft a communication that leads with the process used, explains the criteria and trade-offs, acknowledges the alternative viewpoints, and outlines next steps. Tone: direct, respectful, no hedging. + +**Prompt 4 -- Second-Guessing Audit:** +> I am second-guessing [describe past decision]. Walk me through: (1) the process I used to make it, (2) whether new facts have emerged that warrant revisiting, (3) whether my doubt is evidence-based or anxiety-driven, and (4) a recommended next action -- either recommit or reopen with specific new criteria. + +--- + +## Use Cases + +**The Feature Pivot That Stalled** + +A validation-stage SaaS founder has spent three months debating whether to pivot the core feature set based on user feedback. Metrics are mixed -- some cohorts respond well, others do not. The team has held four strategy sessions without resolution. Applying the 70% rule, the founder recognises that additional user interviews are unlikely to resolve the ambiguity. She buys an option instead: a 30-day A/B test running both feature sets simultaneously. The test provides real conversion data, and the team makes a definitive call within five weeks of the original deadlock. The cost of the test was trivial compared to the cost of three months of organisational drift. + +**The Hire Everyone Questioned** + +A growth-stage fintech founder hires a CTO from outside the industry, overriding the preference of several board members who favoured a candidate with sector-specific experience. Rather than letting the disagreement fester, he communicates the decision using the transparency protocol: he shares the evaluation criteria, the performance data from reference checks, and the strategic rationale for prioritising technical architecture skills over domain familiarity. He sets a 90-day review checkpoint. Two months in, early infrastructure improvements validate the choice, and the board members who initially objected acknowledge that the process was fair, even though their preferred outcome was not selected. + +**The Founder Who Could Not Stop Revisiting** + +An early-traction e-commerce founder finds herself re-examining every pricing decision within days of making it. She implements a gut journal: each decision is logged with the reasoning, the alternatives considered, and the expected outcome. After three months, she reviews the journal and discovers that 80% of her initial pricing calls were within 5% of what she later considered optimal. The journal transforms vague self-doubt into calibrated confidence, and her decision velocity doubles. + +--- + +## Anti-Patterns + +**The Consensus Trap.** Waiting for unanimous agreement before acting is not thoroughness; it is abdication disguised as democracy. Consensus is a luxury of low-stakes decisions. For high-stakes choices, one person must own the call. Seeking input is wise; requiring permission from everyone is paralysing. + +**Transparency Theatre.** Sharing the decision without sharing the reasoning. Announcing "we have decided to restructure the team" without explaining the criteria, alternatives, and trade-offs does not build trust -- it invites conspiracy theories. Transparency means process visibility, not just outcome notification. + +**The Perpetual Pilot.** Using options and experiments as a permanent substitute for commitment. Buying an option is a tool for reducing uncertainty before a decision, not a strategy for avoiding decisions indefinitely. Every option must have an expiration date. + +**Outcome-Based Self-Flagellation.** Judging a past decision harshly because the outcome was poor, without examining whether the process was sound. A founder who carefully evaluated three vendors, selected the best-qualified one, and still experienced a service failure did not make a bad decision. Punishing yourself for outcomes beyond your control trains you to avoid decisions, not to improve them. + +**The Silent Veto.** Allowing a senior stakeholder to remain silent during deliberation and then reopen the decision after the fact. This pattern is organisational poison. It teaches the team that formal decision processes are performative and that real power operates through back channels. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Speed over precision. Most decisions are reversible explorations. | Nearly every choice is a two-way door. Apply the 70% rule aggressively. The cost of delay at this stage is existential -- runway is finite, and the venture has no momentum to sustain it through prolonged deliberation. | +| Validation | Structured experimentation. Convert decisions into testable hypotheses. | Buy options wherever possible. Pilot before committing. The goal is learning velocity, not decision perfection. Implementation plans should be lightweight but explicit. | +| Early Traction | Establish decision norms for the growing team. | As headcount grows, "you didn't ask me" challenges multiply. Introduce formal decision roles (RACI/RAPID) and the silence-denotes-agreement norm. Transparency protocols become essential as the founder can no longer communicate every decision personally. | +| Growth | Delegation architecture. The founder cannot and should not make every call. | The critical skill shifts from making good decisions to designing systems that enable others to make good decisions. Implement escalation triggers, decision journals, and periodic review cadences across the leadership team. | +| Scale | Institutional decision quality. Protect against bureaucratic slowdown. | The risk inverts: at scale, organisations over-deliberate rather than under-deliberate. Reintroduce speed by enforcing decision deadlines, empowering frontline managers with clear decision rights, and reserving executive deliberation for genuinely irreversible choices. | + +--- + +## Output Template + +```markdown +# Decision Record: [Decision Title] + +**Date:** [YYYY-MM-DD] +**Decision Owner:** [Name and role] +**Stage:** [idea / validation / early-traction / growth / scale] + +## Decision Statement +[One sentence: what was decided and the primary rationale.] + +## Context and Alternatives Considered +| Alternative | Key Advantage | Key Risk | Reason Not Selected | +|-------------|---------------|----------|---------------------| +| [Option A] | | | | +| [Option B] | | | | +| [Option C -- selected] | | | [N/A -- this was selected because...] | + +## Process Used +- **Who was consulted:** [Names and roles] +- **Data reviewed:** [Key data sources] +- **Decision method:** [Founder call / team vote / advisory input / other] +- **Reversibility assessment:** [One-way door / two-way door] + +## Implementation Plan +| Milestone | Owner | Deadline | Status | +|-----------|-------|----------|--------| +| [Stakeholder communication] | | | | +| [First execution step] | | | | +| [Checkpoint review] | | | | + +## Success Criteria +- [Metric 1: target and measurement method] +- [Metric 2: target and measurement method] + +## Escalation Triggers +- [Condition under which this decision should be revisited] + +## Review Date +[Scheduled date for formal reassessment] +``` + +--- + +## Related Skills + +- **[Evaluating and Deciding](../thinking/evaluating-and-deciding.md)** -- The Clear Thinking framework's unified decision system covers criteria weighting, margin of safety, and the irreversibility test; this toolkit provides the complementary post-decision disciplines. +- **[Tough Decision Situations](tough-decision-situations.md)** -- When the problem is not paralysis but genuinely bad options, failed consensus, wrong calls, or time pressure, this companion skill provides targeted techniques. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Addresses the specific cognitive and emotional dynamics of high-stakes, time-compressed leadership decisions. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Extends the "extract the lesson" principle into a full organisational learning practice. +- **[Trust Equation](../frameworks/trust-equation.md)** -- The transparency techniques in this skill feed directly into the credibility and intimacy components of trust. +- **[Stoic Pragmatism](../stoic/stoic-pragmatism.md)** -- The Stoic emphasis on decisive action and practical execution aligns with the commitment discipline that prevents decision paralysis and second-guessing. diff --git a/plugins/foreman/content/skills/decisions/decision-traps-and-roles.md b/plugins/foreman/content/skills/decisions/decision-traps-and-roles.md new file mode 100644 index 0000000..11e10f4 --- /dev/null +++ b/plugins/foreman/content/skills/decisions/decision-traps-and-roles.md @@ -0,0 +1,219 @@ +--- +name: "decision-traps-and-roles" +description: "Catalogues the invisible psychological traps that sabotage decisions -- anchoring, sunk cost, confirming evidence, framing, and status quo bias -- and pairs them with the RAPID model for clarifying who recommends, agrees, performs, inputs, and decides, plus a seven-step checklist for faster group decisions. Use when a team suspects cognitive bias is distorting a choice, when decision authority is ambiguous, when past investments are influencing current strategy, when negotiations are anchored by the other party's opening, or when organisational decisions stall because no one knows who owns the call." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-bias + - anchoring + - sunk-cost + - confirmation-bias + - framing + - status-quo + - decision-roles + - rapid-model + - decision-checklist + - group-decisions +related_skills: + - generating-solutions + - evaluating-options + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +# Decision Traps and Roles + +TRAP. Every decision is mined with invisible traps -- anchoring, sunk cost, confirmation bias -- and the most dangerous ones are the ones you cannot see operating on you. Researchers have documented these cognitive distortions for half a century, yet a room of experienced executives will fall into them with the same regularity as a room of undergraduates. The traps are hardwired. They do not yield to intelligence, seniority, or good intentions. They yield only to structure: specific counter-routines that force the mind to check itself before it commits. This skill catalogues the traps, provides the counter-routines, and then addresses the organisational question that amplifies every individual bias -- who, exactly, owns the decision? + +--- + +## The Toolkit + +### Tool 1: The Five Hidden Traps + +Each trap operates beneath conscious awareness. The counter-measures are not intuitive; they must be deliberately applied. + +**The Anchoring Trap.** The mind gives disproportionate weight to the first information it receives. An opening offer in a negotiation, a prior year's revenue figure, a colleague's offhand estimate -- each becomes a gravitational centre around which all subsequent judgments orbit. In one classic experiment, asking whether Turkey's population exceeds 35 million versus 100 million produced wildly different estimates of the actual figure, despite the anchor being arbitrary. + +Counter-measures: +- Approach the problem from multiple starting points before consulting others +- Withhold your own preliminary estimates when soliciting input -- otherwise your preconceptions return to you disguised as independent confirmation +- In negotiations, define your position fully before the other party's opening gambit can set the frame + +**The Status-Quo Trap.** Defaulting to the current state feels safe because action invites responsibility, and responsibility invites criticism. In one experiment, people randomly given a mug refused to trade it for an equally valued chocolate bar -- the status quo exerted its pull within minutes of being established. In business, sins of commission are punished far more severely than sins of omission, creating a structural incentive to leave things as they are even when change is overdue. + +Counter-measures: +- Ask whether you would choose the current state if it were not already the default +- Never treat the status quo as your only alternative -- generate at least one concrete option against which to compare it +- Evaluate alternatives in terms of future desirability, not present comfort + +**The Sunk-Cost Trap.** Past investments -- of money, time, reputation -- create psychological pressure to justify those investments by continuing down the same path. A bank that originated a bad loan is far more likely to advance additional funds than a fresh banker who inherits the account, because the originator is unconsciously protecting an earlier, flawed decision. + +Counter-measures: +- Seek counsel from people uninvolved with the original decision +- Reassign ownership when the original decision-maker cannot separate past commitment from present merit +- Cultivate a culture that evaluates decision quality at the time of the decision, not solely by subsequent outcomes + +**The Confirming-Evidence Trap.** The mind seeks information that supports its existing inclination and discounts information that contradicts it. Two groups -- one favouring and one opposing capital punishment -- each read balanced research evidence and both emerged more entrenched in their original positions. The subconscious decides what it wants before the conscious mind assembles the justification. + +Counter-measures: +- Appoint a devil's advocate, or better, construct the strongest counter-argument yourself +- Ask: "Am I gathering information to make a smart choice, or to confirm the choice I have already made?" +- Avoid leading questions when soliciting advice; if an adviser consistently supports your view, find a different adviser + +**The Framing Trap.** How the question is posed determines the answer. New Jersey and Pennsylvania introduced identical auto-insurance options but framed the default differently; the framing difference produced a $200 million gap in outcomes. People are risk-averse when a problem is framed as a potential gain and risk-seeking when framed as a potential loss -- even when the underlying options are mathematically identical. + +Counter-measures: +- Reframe every problem in at least two ways: as a gain and as a loss, with different reference points +- Challenge others' framings explicitly -- the person who sets the frame controls the decision +- Revisit framing at multiple stages of the decision process, not just at the start + +### Tool 2: The RAPID Model for Decision Roles + +Ambiguity about decision authority is the organisational accelerant that turns individual bias into institutional paralysis. The RAPID framework, developed by Bain & Company, assigns five discrete roles to every significant decision: + +| Role | Letter | Function | +|------|--------|----------| +| **Recommend** | R | Proposes a course of action, marshals data, engages stakeholders, builds the case | +| **Agree** | A | Must formally agree before the recommendation can advance; has explicit veto power | +| **Perform** | P | Executes the decision once made | +| **Input** | I | Provides information and analysis that shapes the recommendation; consulted but not binding | +| **Decide** | D | Brings the decision to closure and commits the organisation to act | + +Three structural pitfalls to avoid: + +1. **Multiple D's.** If two people believe they own the decision, the result is a tug-of-war. One person holds the D. Always. +2. **Proliferation of A's.** Too many veto-holders paralyse recommenders. If many people must agree, decision authority has not been pushed far enough down the organisation. +3. **Excessive I's.** When everyone provides input, at least some contributions are ceremonial. Each I-role should demonstrably improve the recommendation's quality. + +### Tool 3: The Seven-Step Decision Checklist + +A lightweight protocol, drawn from behavioural economics research, that consistently improves group decision quality. Managers who follow it save an average of ten hours of discussion, decide ten days faster, and improve outcomes by twenty percent. + +1. Write down five pre-existing goals or priorities that the decision will affect +2. Write down at least three -- ideally four or more -- realistic alternatives +3. Write down the most important information you are missing +4. Write down the expected impact one year from now as a brief narrative +5. Involve two to six stakeholders (effectiveness declines by ten percent per person beyond seven) +6. Record what was decided, why, and the team's confidence level +7. Schedule a follow-up review in one to two months + +--- + +## Prompts + +**Prompt 1 -- Trap Diagnosis:** +> "I am about to make this decision: [describe decision]. Before I proceed, audit my reasoning for the five hidden traps. Where might I be anchored by initial information? Am I defaulting to the status quo because it is comfortable rather than optimal? Are sunk costs influencing my judgment? Am I seeking confirming evidence? How is the problem framed, and how would the decision change under an alternative frame? Provide a specific counter-measure for each trap you identify." + +**Prompt 2 -- RAPID Role Mapping:** +> "My [stage] company needs to make the following decision: [describe decision]. Map the RAPID roles for this decision. Who should Recommend? Who must Agree (and why do they have veto power)? Who Performs? Whose Input is genuinely necessary versus ceremonial? Who Decides? Flag any structural pitfalls -- multiple D's, excessive A's, or too many I's -- and suggest corrections." + +**Prompt 3 -- Checklist Walkthrough:** +> "I am deciding [decision] for my [sector] company. Walk me through the seven-step decision checklist. Help me articulate five affected goals, generate at least four realistic alternatives, identify missing information, write a one-year-out impact narrative, determine the right number of stakeholders, and design a follow-up review protocol." + +**Prompt 4 -- Negotiation Anchor Defence:** +> "I am entering a negotiation for [describe -- fundraising round, partnership deal, vendor contract]. The other party is likely to set an anchor with their opening position. Help me prepare: define my own position across all negotiable dimensions before the meeting, identify the anchors I am most susceptible to, and construct alternative frames that prevent their opening gambit from constraining my thinking." + +--- + +## Use Cases + +**Pre-Seed Founder Anchored by a VC's Valuation** + +A first-time founder with a B2B SaaS prototype receives a verbal indication from an angel investor: "companies like yours are worth about $2M pre-money." The figure is arbitrary -- the investor has seen two comparable deals in the past quarter, both at distressed valuations. Yet the founder begins using $2M as the reference point for every subsequent conversation, adjusting modestly upward but never escaping the anchor's orbit. A disciplined approach would have the founder construct an independent valuation range from multiple data sources (comparable transactions, revenue multiples for the vertical, the specific value of committed pilot customers) before engaging any investor. The anchor defence is preparation: define your own frame before someone else defines it for you. + +**Growth-Stage Company Throwing Good Money After a Failed Product Line** + +A consumer hardware startup invested $3M and eighteen months developing a smart home device that has sold 2,000 units in six months -- roughly ten percent of the break-even target. The VP of product argues for an additional $1.5M to "fix the go-to-market strategy," citing the original investment as justification. The sunk-cost trap is operating at full force: the $3M already spent is irrecoverable regardless of the next decision. A fresh evaluator -- someone without emotional investment in the original bet -- would assess the $1.5M purely on its expected return. Reassigning the product review to the head of a different business unit surfaces what the original team could not see: the core product thesis (that consumers would pay $400 for a device that replicates $30 of functionality on their phone) was never validated. + +**Scaling Company with Unclear Decision Ownership** + +A 200-person e-commerce company finds that pricing decisions take six weeks to implement because marketing, finance, product, and the CEO each believe they own the call. A RAPID mapping reveals that marketing should Recommend (they hold the customer data), finance should provide Input (margin constraints), product should Agree (pricing affects positioning), and the CEO should Decide -- but only for pricing changes above a defined threshold. Below that threshold, marketing holds the D. Pricing decisions now take five days. + +--- + +## Anti-Patterns + +**Treating bias awareness as bias immunity.** Knowing about anchoring does not prevent anchoring. The traps are not eliminated by education; they are mitigated by structure. A team that has read this skill and proceeds to brainstorm without any counter-routines will fall into every trap catalogued here. + +**Assigning RAPID roles for trivial decisions.** A five-person startup does not need a formal role-mapping exercise for choosing a project management tool. RAPID is designed for decisions where ambiguity about authority creates measurable delay or conflict. Over-applying it bureaucratises what should be a fast-moving organisation. + +**Using the checklist as a post-hoc rationalisation tool.** The seven-step checklist works only if applied before the decision is made. Filling it out after the fact -- to justify a choice already taken -- converts a debiasing tool into a confirming-evidence machine. + +**Assuming one person's counter-arguments constitute adequate debiasing.** A single devil's advocate can be dismissed. Structural debiasing requires multiple independent perspectives, ideally from people with no stake in the outcome and no history with the decision. + +**Conflating the D with seniority.** The person who Decides should be the person closest to the information and most accountable for the outcome -- not necessarily the most senior person in the room. Pushing the D upward by default is a status-quo trap applied to organisational design. + +--- + +## By Stage + +| Stage | Primary Trap Risk | RAPID Focus | +|-------|-------------------|-------------| +| Idea | Confirming-evidence trap -- the founder seeks validation for a pre-existing belief about the market. Framing trap -- the problem definition constrains the solution space before alternatives are explored. | Roles are informal; the founder often holds all five letters. The discipline at this stage is recognising when to solicit genuine I-roles from people who will challenge, not confirm. | +| Validation | Sunk-cost trap -- early investment in an MVP creates pressure to continue rather than pivot. Anchoring on early customer feedback (first ten users set expectations for the next thousand). | The founding team must explicitly assign the D for pivot-or-persist decisions. If no one owns it, the status quo wins by default. | +| Early Traction | Status-quo trap -- processes that worked for ten customers are preserved unchanged for one hundred. Anchoring on founding-era metrics as benchmarks. | RAPID becomes operational. Decisions about hiring, pricing, and feature prioritisation need clear role assignments as the team grows beyond the founders. | +| Growth | All five traps operate simultaneously at scale. Confirming evidence flows freely in organisations that have been successful -- past success anchors future strategy. | The checklist becomes a team discipline, not an individual exercise. Decision follow-ups at step seven must be enforced by calendar, not memory. | +| Scale | The framing trap is most dangerous at scale because the frame is set by layers of middle management before information reaches the decision-maker. Sunk costs are measured in years and departments, not weeks and features. | RAPID must be documented and published for recurring decisions. Ad hoc role assignment fails when hundreds of people are involved. The D must be explicit, visible, and non-negotiable. | + +--- + +## Output Template + +```markdown +# Decision Trap and Role Audit + +**Decision:** [one-sentence description] +**Date:** [date] +**Audited by:** [name(s)] + +## Trap Scan + +| Trap | Present? | Evidence | Counter-Measure Applied | +|------|----------|----------|------------------------| +| Anchoring | [yes/no] | [what anchor is influencing the decision?] | [alternative starting points used] | +| Status Quo | [yes/no] | [is inaction being preferred for comfort?] | [status quo compared against explicit alternatives] | +| Sunk Cost | [yes/no] | [what past investment is influencing the choice?] | [decision evaluated on forward-looking merit only] | +| Confirming Evidence | [yes/no] | [is information being gathered selectively?] | [devil's advocate assigned; counter-arguments constructed] | +| Framing | [yes/no] | [how is the question framed, and what does the alternative frame reveal?] | [problem reframed as gain/loss with different reference points] | + +## RAPID Role Assignment + +| Role | Person | Rationale | +|------|--------|-----------| +| Recommend | [name] | [why this person] | +| Agree | [name] | [why veto power is warranted] | +| Perform | [name(s)] | [execution responsibility] | +| Input | [name(s)] | [what information they provide] | +| Decide | [name] | [why this person owns the call] | + +## Seven-Step Checklist +1. **Goals affected:** [list five] +2. **Alternatives:** [list three or more] +3. **Missing information:** [what we do not know] +4. **One-year impact narrative:** [two sentences] +5. **Stakeholders involved:** [names, max six] +6. **Decision record:** [what, why, confidence level] +7. **Follow-up date:** [date, one to two months out] +``` + +--- + +## Related Skills + +- **[Generating Solutions](generating-solutions.md)** -- Once traps are identified and roles assigned, the next step is generating alternatives; this sibling skill covers brainstorming failures, BrainSwarming, and could-vs-should reframing. +- **[Evaluating Options](evaluating-options.md)** -- Provides the evaluation methods (joint evaluation, Even Swaps, risk ranking, intuition calibration) for choosing among the alternatives generated. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- Root cause analysis and the 3-Lens Principle address the problem-definition phase that precedes this skill's focus on decision traps. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's cognitive model explains the System 1/System 2 mechanics that generate the traps catalogued here. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Daily habits for maintaining decision quality when time and emotional pressure compress the window for deliberation. +- **[Enemies of Clear Thinking](../thinking/enemies-of-clear-thinking.md)** -- The four biological defaults (ego, emotion, inertia, social) provide the deeper diagnostic framework for understanding why the cognitive traps catalogued here persist despite awareness. diff --git a/plugins/foreman/content/skills/decisions/evaluating-options.md b/plugins/foreman/content/skills/decisions/evaluating-options.md new file mode 100644 index 0000000..a080d0d --- /dev/null +++ b/plugins/foreman/content/skills/decisions/evaluating-options.md @@ -0,0 +1,260 @@ +--- +name: "evaluating-options" +description: "Provides six independent evaluation techniques for choosing among alternatives once they have been generated: joint evaluation (comparing options side by side rather than in isolation), the structural weaknesses of pros-and-cons lists and how to compensate, the Even Swaps method for rational trade-offs across incommensurable objectives, decision-making with limited data using satisficing and recognition-primed models, the CARVER six-part risk assessment tool, and a three-condition framework for calibrating when intuition is trustworthy versus dangerous. Use when evaluating multiple options against competing criteria, when a pros-and-cons list feels insufficient for a high-stakes choice, when trade-offs involve incomparable dimensions, when data is scarce and a decision cannot wait, when assessing risk across multiple assets or initiatives, or when debating whether to trust a gut feeling." +version: "1.0.0" +category: "decisions" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - evaluation + - trade-offs + - even-swaps + - joint-evaluation + - risk-assessment + - carver + - intuition + - pros-and-cons + - satisficing + - decision-quality +related_skills: + - decision-traps-and-roles + - generating-solutions + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +# Evaluating Options + +PROS-CONS TRAP. The pros-and-cons list is the most widely used decision tool in the world -- and it is fundamentally misleading, because it treats all factors as equal and all items as comparable. Benjamin Franklin popularised the method in 1772, and the business world has not materially improved upon it in the intervening 250 years. A list that places "strong brand fit" next to "high implementation cost" as if both carry identical weight, and then counts items on each side like ballots, is not analysis. It is arithmetic applied to incommensurable quantities. High-stakes decisions -- the kind that determine whether a company enters a market, acquires a competitor, or pivots its product -- demand evaluation methods that account for unequal weights, incomparable dimensions, and the structural biases that distort human judgment even when the data is sound. This skill assembles six such methods, each designed for a different evaluation challenge. + +--- + +## The Toolkit + +### Tool 1: Joint Evaluation + +Research by Basu and Savani demonstrates that people are, on average, twenty-two percent more likely to choose the objectively best option when they evaluate all alternatives simultaneously rather than one at a time. The effect is robust across simple consumer choices and complex managerial decisions. + +The mechanism is straightforward: when options are presented side by side, the mind compares directly across dimensions. When options are presented sequentially, the mind forms a holistic impression of each and then attempts to compare impressions -- a lossy process that discards the dimensional detail where differences actually live. + +**Practical application:** +- When evaluating job candidates, lay all resumes on the table simultaneously rather than reviewing one, forming an opinion, and moving to the next +- When comparing vendors or partners, use a spreadsheet that displays all options in columns with attributes in rows -- never evaluate a vendor in isolation +- When assessing strategic alternatives, present all options in a single consequences table before any discussion begins + +The bias toward sequential evaluation is strong: in one survey, participants reported evaluating options one at a time in roughly half of all decisions. Companies reinforce this by designing product pages and internal reports that present one option per screen. Resist the format. Demand the side-by-side view. + +### Tool 2: Beyond Pros and Cons + +The pros-and-cons list has three genuine strengths and three fatal weaknesses. Understanding both prevents the tool from being either abandoned prematurely or trusted beyond its competence. + +**Strengths:** +- *Rigour of enumeration.* The discipline of listing factors forces consideration of dimensions that might otherwise be overlooked +- *Emotional distance.* The act of writing creates what psychologists call a "self-distanced perspective," reducing the risk of an amygdala hijack during high-stakes decisions +- *Simplicity.* The method requires no computational or analytical expertise + +**Weaknesses:** +- *Narrow framing.* A pros-and-cons list evaluates one option (do it vs. don't) rather than comparing multiple alternatives. It is inherently binary +- *Unweighted factors.* Every item on the list counts equally. A "con" worth $50,000 occupies the same visual space as a "con" worth $5 million +- *Vulnerability to cognitive bias.* Overconfidence, the illusion of control, and the framing effect all operate freely within the format. The simplicity that makes the list accessible is the same simplicity that leaves it undefended against distortion + +**When to use it:** As a preliminary thinking aid -- a first pass that surfaces the dimensions worth analysing. Never as the final evaluation instrument for a consequential decision. + +**How to strengthen it:** If a pros-and-cons list must be used, assign explicit weights (1-10) to each factor and multiply by a confidence estimate. This converts the list from a ballot count into a rough weighted scoring model. The result is still imperfect, but materially less misleading. + +### Tool 3: The Even Swaps Method + +Developed by Hammond, Keeney, and Raiffa, the Even Swaps method provides a rational mechanism for making trade-offs among objectives that use entirely different units of measurement -- money versus time versus market share versus risk. The core insight: if you can make two alternatives equivalent on one dimension, that dimension drops out of the decision. Eliminate enough dimensions, and a clear winner emerges. + +**The process:** + +**Step 1: Build a consequences table.** List objectives down the left side, alternatives across the top. In each cell, describe the consequence of that alternative for that objective, using consistent units within each row. + +**Step 2: Eliminate dominated alternatives.** If Alternative A is better than Alternative B on some objectives and no worse on all others, B is dominated and can be removed. Use a ranking table (replace descriptions with ordinal ranks) to make dominance visible in complex matrices. + +**Step 3: Make even swaps.** Select two alternatives and an objective where they differ. Ask: "What change in Objective X would compensate for the difference in Objective Y?" Adjust one alternative's consequence accordingly. Now both alternatives are equivalent on Objective Y, which can be eliminated from consideration. + +**Step 4: Iterate.** Repeat until one alternative dominates all others or only one objective remains. + +**Example:** A Brazilian cola company choosing between franchising (lower profit, higher market share) and not franchising (higher profit, lower market share) determines that a three-percent increase in market share compensates for $15 million in lost profit. Adjusting the non-franchising alternative by swapping $15M profit for 3% market share makes profit equivalent across both options. The decision reduces to market share alone -- and franchising wins. + +The method's power lies in forcing explicit value judgments. Most decision-makers never articulate how much of one objective they would sacrifice for another. The Even Swaps method makes these trade-offs visible, discussable, and auditable. + +### Tool 4: The CARVER Risk Assessment + +CARVER is a six-criteria scoring system originally developed during World War II for targeting analysis, now widely adopted in corporate risk management and strategic planning. It converts qualitative risk judgments into a comparable numeric framework. + +| Criterion | Assesses | Score 1 (low) | Score 5 (high) | +|-----------|----------|---------------|----------------| +| **C**riticality | How essential the asset/initiative is to operations | Loss would not affect operations | Loss would halt operations | +| **A**ccessibility | How exposed the asset is to threats or competition | Extremely difficult to access or replicate | Easily accessed or replicated | +| **R**ecoverability | How quickly operations recover after loss | Replaced immediately, no downtime | Extremely difficult to replace, long downtime | +| **V**ulnerability | How well the asset withstands attack or disruption | Highly resilient | Highly vulnerable | +| **E**ffect | Broader impact across the business if compromised | No unfavourable impact | Very high economic, political, or social impact | +| **R**ecognizability | How visible the asset is as a target to adversaries | Not recognisable as valuable | Immediately recognisable | + +Each asset, initiative, or option is scored 1-5 on all six criteria. The sum (maximum 30) provides a comparable risk ranking. The framework is equally useful for offensive analysis (which competitor vulnerability to exploit, which market to enter) and defensive analysis (which asset to protect, which risk to mitigate first). + +**Entrepreneurial applications:** +- Compare two market-entry strategies by scoring each on all six CARVER criteria +- Assess which product line is most vulnerable to competitive disruption +- Prioritise security and operational investments across multiple locations or business units +- Defend a budget request to a board by presenting the numeric scoring alongside the qualitative reasoning + +### Tool 5: Deciding with Limited Data + +Most entrepreneurial decisions are made under conditions of radical uncertainty -- limited data, ambiguous signals, and time pressure that forecloses extended analysis. Two models from decision science address this reality. + +**Satisficing.** Herbert Simon's concept: rather than optimising (evaluating all options to find the best), establish minimum acceptable thresholds on key criteria and select the first option that meets all of them. The method is rational, not lazy -- it recognises that the cost of extended search often exceeds the marginal value of finding a marginally better option. A founder hiring a first engineer does not need the best engineer on earth; the founder needs an engineer who clears the threshold on technical skill, cultural fit, and availability within the next thirty days. + +**Recognition-Primed Decision-Making (RPD).** Gary Klein's research on fire commanders, military officers, and emergency physicians revealed that experienced decision-makers rarely compare options at all. Instead, they recognise the current situation as similar to one they have encountered before, mentally simulate the first plausible course of action, and execute if the simulation does not reveal fatal flaws. RPD is fast because it leverages pattern recognition built through years of domain experience. It is dangerous when applied outside one's domain or in novel situations that merely resemble familiar ones. + +**When each applies:** + +| Condition | Preferred Model | +|-----------|----------------| +| Many options, moderate time pressure, clear minimum thresholds | Satisficing | +| Few options, severe time pressure, deep domain experience | Recognition-primed decision-making | +| Novel situation, no domain experience, sufficient time | Neither -- use structured analytical methods (Even Swaps, CARVER) | + +### Tool 6: When to Trust Intuition + +Connson Chou Locke's framework identifies three conditions that must hold simultaneously for intuition to be reliable. When any condition is absent, intuition is unreliable and analytical methods should take precedence. + +**Condition 1: Domain expertise.** Roughly ten years of deliberate practice in the specific domain, with repetition and feedback, are required to develop accurate intuitive judgment. A financial history professor's expertise does not extend to financial investment decisions. A successful B2B founder's intuition about consumer products is untested and therefore untrustworthy. + +**Condition 2: Unstructured problem.** Intuition excels on problems that lack clear decision rules or objective criteria -- aesthetic judgments, political judgments, interpersonal dynamics. Problems with abundant data and clear rules are better served by algorithms, which outperform even experienced doctors in medical diagnosis because the human brain, facing large datasets, defaults to heuristics that introduce error. + +**Condition 3: Time scarcity.** When the decision window is narrow and information is sparse, intuition may perform as well as analysis because there is insufficient data for analysis to exploit its advantage. However, time pressure alone does not validate intuition -- it merely removes the option of thorough analysis. + +**The danger zone:** Intuition feels equally confident regardless of whether the conditions are met. The factory foreman who has spent twenty years reading a production floor has earned the right to trust a gut feeling about safety. The first-time founder who "just knows" that consumers will pay $200 for an untested product has not. The subjective sensation is identical; the reliability is not. + +**The synthesis:** Use intuition to narrow the field, then subject the shortlisted options to analytical evaluation. Or use analysis to identify a few equally strong options, then let informed intuition break the tie. The error is not in using intuition at all -- it is in using intuition as a substitute for analysis when the conditions for reliable intuition are absent. + +--- + +## Prompts + +**Prompt 1 -- Joint Evaluation Matrix:** +> "I am evaluating [number] options for [decision] at my [stage] [sector] company. The options are: [list]. The objectives I care about are: [list]. Build a consequences table with options as columns and objectives as rows. Identify any dominated alternatives. Then recommend whether the remaining options should be evaluated using Even Swaps, CARVER, or weighted scoring, and explain why." + +**Prompt 2 -- Even Swaps Walkthrough:** +> "I am choosing between [Option A] and [Option B]. Option A is better on [objective 1] but worse on [objective 2]. Walk me through the Even Swaps method: What change in [objective 1] would compensate for the difference in [objective 2]? Make the swap explicit, eliminate the now-irrelevant objective, and identify which option dominates. If neither dominates, suggest the next swap." + +**Prompt 3 -- CARVER Risk Scoring:** +> "I need to compare the risk profiles of [two or more options/assets/markets]. Score each on the six CARVER criteria (Criticality, Accessibility, Recoverability, Vulnerability, Effect, Recognizability) on a 1-5 scale. Explain each score. Identify which option has the highest total risk score and recommend mitigation strategies for the top-scoring criteria." + +**Prompt 4 -- Intuition Calibration:** +> "I have a strong gut feeling about [decision]. Before I act on it, calibrate my intuition against Locke's three conditions: (1) Do I have genuine domain expertise (ten-plus years of relevant experience with feedback)? (2) Is this an unstructured problem or one with clear data and rules? (3) Is time genuinely scarce, or am I using urgency as an excuse to avoid analysis? Based on this calibration, recommend whether I should trust my intuition, override it, or use it alongside a structured method." + +--- + +## Use Cases + +**Series A SaaS Company Choosing Between Two Acquisition Targets** + +A vertical SaaS company in the logistics space evaluates acquiring either a competitor (overlapping customer base, complementary product) or a data-analytics startup (different customer base, adjacent technology). A consequences table with seven objectives (revenue synergy, technology fit, integration complexity, cultural alignment, customer overlap, price, and time to close) reveals that the competitor dominates on four objectives and ties on one but loses on technology fit and price. The Even Swaps method asks: how much technology advantage would compensate for the competitor's price premium? The team determines that the competitor's existing customer relationships, which would take three years to build organically, are worth more than the $2M price difference. A swap of $2M in price for three years of customer acquisition time makes price equivalent. Technology fit becomes the sole remaining differentiator -- but applying the CARVER framework to the analytics startup reveals a Recoverability score of 5 (the three key engineers could leave post-acquisition, and the technology would be extremely difficult to maintain). The competitor wins. + +**Pre-Seed Founder Deciding Whether to Trust a Market Intuition** + +A founder with twelve years of experience in enterprise security "just knows" that mid-market companies will pay for an automated compliance tool. Applying the intuition calibration: (1) Domain expertise -- yes, twelve years in the specific domain with direct customer feedback. (2) Unstructured problem -- partially; the question of whether a market exists for a new product category has both quantitative indicators (market size, competitor revenue) and qualitative dimensions (buyer psychology, urgency of pain). (3) Time scarcity -- no; the founder has not yet committed capital and has time to validate. Recommendation: the founder's intuition is credible enough to warrant action but not sufficient to skip validation. Use the gut feeling to select the beachhead market, then subject the hypothesis to structured analysis (customer interviews, willingness-to-pay tests, competitive mapping) before committing significant resources. + +**Growth-Stage E-Commerce Brand Comparing Three Fulfilment Strategies** + +A D2C brand at $15M ARR evaluates three fulfilment options: build an in-house warehouse, partner with a third-party logistics provider, and a hybrid model. The team's default approach -- a pros-and-cons list for each option -- produces three lists of unweighted factors that are impossible to compare. Switching to joint evaluation (all three options in a single table) immediately reveals that the hybrid model is practically dominated by the 3PL option: it has similar costs, worse operational complexity, and only a marginal advantage in brand control. Eliminating the hybrid reduces the decision to two options. The Even Swaps method asks: how much brand control would compensate for the $800K annual cost difference between in-house and 3PL? The team determines that brand control matters only for the premium product line (30% of revenue). An Even Swap of $800K for brand control over 30% of SKUs makes cost equivalent. The remaining differentiator is speed of implementation -- and the 3PL can launch in six weeks versus nine months for in-house. The 3PL wins, with a contract clause preserving the option to bring premium fulfilment in-house within eighteen months. + +--- + +## Anti-Patterns + +**Using pros-and-cons lists as the final evaluation method for consequential decisions.** The list is a brainstorming aid, not a decision tool. When the stakes are high -- hiring a co-founder, entering a market, accepting investment terms -- the unweighted, unstructured format of the list creates exactly the conditions under which cognitive biases thrive. + +**Evaluating options sequentially when joint evaluation is feasible.** Reviewing one candidate resume, forming an impression, and then reviewing the next is twenty-two percent less effective than reviewing all resumes simultaneously. The sequential approach feels thorough; it is measurably inferior. + +**Applying Even Swaps without first building a consequences table.** The method requires explicitly defined objectives and clearly described consequences. Attempting Even Swaps from memory or from informal notes introduces precisely the imprecision the method is designed to eliminate. + +**Trusting intuition in novel domains.** The first-time founder entering a market with no prior experience, the engineer making a marketing judgment, the operator making a financial projection -- all are applying intuition in domains where it has not been calibrated. The subjective confidence is indistinguishable from calibrated intuition; the accuracy is not. + +**Over-engineering evaluation for reversible decisions.** A full CARVER analysis for a landing page design or a Slack channel name is a misallocation of analytical capacity. Reserve structured evaluation for decisions where the cost of choosing wrong exceeds the cost of choosing carefully. For two-way doors, satisficing is the appropriate model. + +**Ignoring the intangible criteria in CARVER scoring.** The "Effect" criterion captures second-order consequences -- reputational damage, employee morale, regulatory exposure -- that rarely appear in financial models. Scoring Effect as a 1 because the impact is non-financial is a category error that systematically underweights the criteria that matter most in high-stakes decisions. + +--- + +## By Stage + +| Stage | Primary Evaluation Challenge | Recommended Tools | +|-------|------------------------------|-------------------| +| Idea | Few options, radical uncertainty, minimal data. The founder is evaluating whether to pursue the idea at all. | Intuition calibration (is the founder's domain expertise sufficient to trust the gut?), satisficing (does the opportunity clear minimum thresholds on market size, founder-market fit, and feasibility?). | +| Validation | Multiple MVP approaches, customer segments, or pricing strategies to evaluate. Data is emerging but thin. | Joint evaluation of alternatives in a single consequences table. Could-vs-should thinking from the generating-solutions skill feeds into structured comparison here. Recognition-primed decision-making applies if the founder has deep domain experience. | +| Early Traction | Hiring, partnership, and product-roadmap decisions multiply. Each involves trade-offs across dimensions that resist direct comparison. | Even Swaps for trade-off-heavy decisions (e.g., hire a generalist vs. a specialist -- what skill breadth compensates for depth, and vice versa?). CARVER for assessing operational risks as complexity increases. | +| Growth | Strategic decisions (market entry, acquisition, platform migration) with long time horizons and high irreversibility. Multiple stakeholders with competing objectives. | Full Even Swaps process with a formal consequences table. CARVER for risk-ranking initiatives across the portfolio. Joint evaluation is non-negotiable -- no strategic decision should be evaluated in isolation. | +| Scale | Decisions are made across the organisation by people distant from the original context. Evaluation frameworks must be communicable and auditable. | Institutionalised consequences tables and CARVER assessments that create a paper trail. The intuition calibration framework becomes a coaching tool: training managers to recognise when their gut is calibrated and when it is not. | + +A pattern across stages: the ratio of intuition to analysis should shift as data accumulates. At the idea stage, intuition (if domain-calibrated) may be the most efficient tool. At scale, the volume and availability of data make analytical methods both feasible and superior. The founder who trusted intuition at inception and still trusts it at $100M ARR has not evolved with the business -- the business has outgrown the founder's pattern library. + +--- + +## Output Template + +```markdown +# Option Evaluation Record + +**Decision:** [one-sentence description] +**Date:** [date] +**Evaluation method(s) used:** [joint evaluation / Even Swaps / CARVER / intuition calibration / satisficing / combination] + +## Consequences Table (Joint Evaluation) + +| Objective | Weight (1-10) | Option A | Option B | Option C | +|-----------|---------------|----------|----------|----------| +| [objective 1] | [weight] | [consequence] | [consequence] | [consequence] | +| [objective 2] | [weight] | [consequence] | [consequence] | [consequence] | +| [objective 3] | [weight] | [consequence] | [consequence] | [consequence] | + +## Dominated Alternatives +- [Option X] dominated by [Option Y] because: [reasoning] + +## Even Swaps (if applicable) +- **Swap 1:** Changed [Option A]'s [Objective X] from [value] to [value] to compensate for difference in [Objective Y]. Objective Y eliminated. +- **Swap 2:** [repeat as needed] +- **Remaining differentiator:** [the objective that determines the final choice] + +## CARVER Risk Scores (if applicable) + +| Option | C | A | R | V | E | R | Total | +|--------|---|---|---|---|---|---|-------| +| Option A | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [sum] | +| Option B | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [sum] | + +## Intuition Check +- **Domain expertise present?** [yes/no -- years, specific domain] +- **Problem type:** [structured / unstructured / mixed] +- **Time pressure:** [genuine / artificial] +- **Intuition reliability verdict:** [trust / override / use alongside analysis] + +## Decision +**Chosen option:** [X] +**Primary reasoning:** [which evaluation method drove the choice and why] +**Confidence level:** [low / moderate / high] +**Key risk to monitor:** [the highest-scoring CARVER criterion or the weakest Even Swap assumption] +``` + +--- + +## Related Skills + +- **[Decision Traps and Roles](decision-traps-and-roles.md)** -- The cognitive traps (anchoring, confirming evidence, framing) that distort evaluation are catalogued here along with counter-routines to apply before and during any evaluation. +- **[Generating Solutions](generating-solutions.md)** -- The prerequisite: alternatives must be generated before they can be evaluated; this sibling skill covers brainstorming failure modes, BrainSwarming, and question bursts. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- The 3-Lens Principle complements the Even Swaps method by surfacing second-order consequences and hidden opportunity costs. +- **[Evaluating and Deciding](../thinking/evaluating-and-deciding.md)** -- Covers margin of safety, irreversibility tests, execution fail-safes, and decision journals -- the phases that follow option evaluation. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's prospect theory explains why the framing trap distorts evaluation and why loss aversion makes people risk-seeking in the domain of losses. +- **[Negotiation Game Theory](../game-theory/negotiation-game-theory.md)** -- When evaluation involves bilateral value division, the Nash Product Solution provides the mathematical framework for identifying optimal splits between parties. diff --git a/plugins/foreman/content/skills/decisions/generating-solutions.md b/plugins/foreman/content/skills/decisions/generating-solutions.md new file mode 100644 index 0000000..49a73f3 --- /dev/null +++ b/plugins/foreman/content/skills/decisions/generating-solutions.md @@ -0,0 +1,213 @@ +--- +name: "generating-solutions" +description: "Assembles four independent techniques for producing better alternatives before evaluation begins: structured brainstorming with its known failure modes, the question burst method for reframing problems through questions rather than answers, BrainSwarming as a silent graph-based alternative to verbal brainstorming, design thinking's four phases (question, care, connect, commit), and the could-versus-should reframe that expands the solution space by suspending premature judgment. Use when brainstorming sessions feel stale, when a team converges on the first idea too quickly, when introverts are being drowned out, when a problem needs reframing before solutions are attempted, or when only two options seem to exist." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - brainstorming + - idea-generation + - brainswarming + - design-thinking + - reframing + - question-burst + - creative-problem-solving + - could-vs-should + - alternatives +related_skills: + - decision-traps-and-roles + - evaluating-options + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +# Generating Solutions + +BRAINSTORM PARADOX. Traditional brainstorming is the most popular idea-generation method in business -- and research consistently shows it produces fewer and worse ideas than the alternatives. No study has demonstrated that verbal group brainstorming outperforms individuals working alone and then pooling results. The reasons are structural, not motivational: production blocking (only one person talks at a time), evaluation apprehension (people self-censor in front of authority), and social loafing (coasting on others' contributions). The method persists because it feels collaborative. Feeling collaborative and being productive are different things. This skill presents four alternatives -- each addressing a different failure mode -- that a founder can select based on the specific obstacle the team faces. + +--- + +## The Toolkit + +### Tool 1: Structured Brainstorming (and Why It Usually Fails) + +Traditional brainstorming is not useless; it is misused. The technique works when three conditions hold: the facilitator is scrupulously neutral, ideas are recorded without commentary, and participants feel genuinely safe contributing ideas that contradict the most senior person in the room. In practice, all three conditions are violated within the first five minutes of most sessions. + +The failure modes: + +| Failure Mode | Mechanism | Symptom | +|-------------|-----------|---------| +| **Production blocking** | Only one person speaks at a time; others forget or abandon ideas while waiting | The most vocal participants generate most of the recorded ideas | +| **Evaluation apprehension** | Contributors self-censor to avoid judgment, especially from superiors | Ideas cluster around the safe and conventional; no one proposes anything that could look foolish | +| **Social loafing** | Individuals contribute less effort in a group than they would alone | Five people in a room produce fewer ideas than five people working independently | +| **Anchoring cascade** | The first idea voiced sets the frame; subsequent ideas orbit around it | A marketing manager suggests new packaging, and the entire session becomes a packaging discussion | + +Structural fixes that salvage the method: +- Have participants generate ideas independently in writing before any group discussion +- Use anonymous submission (digital or physical) to neutralise hierarchy +- Rotate facilitators so no single authority figure shapes the session +- Separate idea generation from idea evaluation by at least 24 hours + +### Tool 2: The Question Burst + +Developed by Hal Gregersen at MIT, the question burst inverts the standard brainstorming premise: instead of generating answers, the group generates questions. The shift works because questions bypass the cognitive biases that constrain answer-generation -- they suspend the automatic rush to solutions and reframe the problem from multiple angles simultaneously. + +**Protocol (15 minutes total):** + +1. **Set the stage (2 minutes).** The problem owner describes the challenge in plain language -- no detailed background, no proposed solutions. State what would improve if the problem were solved, and why it has resisted previous attempts. Include two or three people who have no direct experience with the problem; their ignorance is an asset because they will ask the questions insiders have learned not to ask. + +2. **Generate questions (4 minutes).** The group produces as many questions as possible, aiming for at least fifteen. Two rules: only questions are permitted (no answers, no preambles, no justifications), and the problem owner records every question verbatim. Time pressure forces brevity and prevents self-censorship. + +3. **Select and deepen (9 minutes).** The problem owner reviews the questions privately, selects three that reframe the challenge in unexpected ways, and applies Sakichi Toyoda's "five whys" to each -- asking why each question matters, then why that reason matters, drilling toward root assumptions. The output is not a solution but a redefined problem that opens new pathways. + +**Why it outperforms answer-brainstorming:** Gregersen's field data show that eighty percent of sessions produce at least one question that usefully reframes the problem. The method also reverses the power dynamics that sabotage traditional brainstorming -- a junior employee asking "Why do we assume our customers want this feature?" carries less social risk than the same employee proposing "We should kill this feature." + +### Tool 3: BrainSwarming + +Developed by Tony McCaffrey, BrainSwarming eliminates talking entirely. It replaces verbal brainstorming with a visual, silent, graph-based process inspired by how ants solve problems -- by leaving signals in the environment for others to build upon. + +**Structure:** + +A large surface (whiteboard, digital canvas) is prepared with the goal at the top and known resources at the bottom. + +- **Top-down thinkers** work downward from the goal, decomposing it into progressively more specific sub-goals +- **Bottom-up thinkers** work upward from the resources, identifying novel combinations and applications +- When the two directions connect on the graph, solutions emerge + +**No talking.** Participants add sticky notes and draw connections silently. This eliminates production blocking (everyone contributes simultaneously), evaluation apprehension (no one watches you speak), and social loafing (individual contributions are visible on the graph). + +Pilot data show BrainSwarming produces up to 115 ideas in fifteen minutes versus roughly 100 ideas per hour for traditional brainstorming -- a sevenfold increase in throughput. The graph structure also preserves the reasoning behind each idea, making it possible to trace how solutions were assembled from component insights. + +### Tool 4: Design Thinking's Four Phases + +Warren Berger's distillation of design-thinking practice identifies four behaviours that separate breakthrough innovators from incremental improvers. These are not sequential stages in a rigid process but concurrent habits of mind. + +**Question.** Designers begin by asking what Berger calls "stupid questions" -- those that challenge the premises everyone else accepts. "How many designers does it take to change a light bulb? Answer: Does it have to be a light bulb?" In a business context, the equivalent is: "What business are we really in?" and "What do today's customers actually need from us?" -- questions that feel naive but that expose assumptions invisible to insiders. + +**Care.** Genuine empathy requires leaving the corporate bubble and immersing in the daily lives of users. Focus groups and surveys are proxies for caring; observation is the real thing. The distinction matters because unarticulated needs -- the ones customers cannot express in a questionnaire -- are where the most valuable solutions live. + +**Connect.** Innovation often comes not from invention but from recombination -- what John Thackara calls "smart recombinations." Nike combined a running shoe with an iPod; Apple combined existing technologies into interfaces no one had assembled before. The discipline is lateral search: looking far outside the problem's domain for components that could be combined in new ways. + +**Commit.** Ideas become tangible through rapid prototyping -- napkin sketches, foam models, digital mock-ups. Giving form to an idea early means risking early failure, but designers understand that small failures are data. The iterative cycle of prototype, test, learn, and revise is faster and cheaper than the analytical cycle of plan, perfect, and launch. + +### Tool 5: Could vs. Should + +Research by Francesca Gino at Harvard Business School demonstrates that reframing "What should we do?" as "What could we do?" produces measurably more creative solutions. The "should" frame activates trade-off thinking -- the mind narrows to the most obvious answer. The "could" frame suspends judgment and expands the option set. + +In one experiment, participants facing ethical dilemmas with no good choice generated significantly more creative resolutions when asked what they "could" do rather than what they "should" do. A separate experiment found that groups given apparently conflicting goals (build a novel product and keep costs low) produced more original work than groups given a single goal -- the tension itself forced creative synthesis. + +The practical application: when a team presents a binary choice ("should we expand into Europe or focus on North America?"), reframe it as "what could we do?" and watch the option set multiply. The maître d' at a Michelin three-star restaurant in Modena, when a child ordered pizza at a restaurant that does not serve pizza, did not ask what he should do. He asked what he could do -- and sent a taxi to the best pizzeria in town. + +--- + +## Prompts + +**Prompt 1 -- Method Selection:** +> "My team needs to generate alternatives for [describe challenge] at my [stage] [sector] company. Diagnose which brainstorming failure modes are most likely given my team's composition: [describe team size, seniority mix, introvert/extrovert balance]. Recommend the best idea-generation method from this toolkit (structured brainstorming, question burst, BrainSwarming, design thinking, could-vs-should reframe) and explain why it addresses the specific failure mode." + +**Prompt 2 -- Question Burst Facilitation:** +> "I am stuck on this problem: [describe challenge in two sentences]. Act as a question burst facilitator. Generate twenty questions about this problem -- no answers, no preambles. Include at least five questions that challenge my fundamental assumptions, three that reframe the problem from the customer's perspective, and three that come from an outsider who knows nothing about my industry. Then identify the three questions most likely to open new solution pathways." + +**Prompt 3 -- BrainSwarming Graph:** +> "My goal is [describe goal]. My available resources are [list resources: team skills, budget, technology, partnerships, customer relationships]. Build a BrainSwarming graph: decompose the goal into sub-goals (top-down), then analyse the resources for novel combinations (bottom-up). Identify at least three points where top-down and bottom-up connect to form potential solutions." + +**Prompt 4 -- Could-vs-Should Reframe:** +> "My team has framed this decision as a binary: [Option A] vs. [Option B]. Apply the could-vs-should reframe. Generate at least five additional options we have not considered, including at least one that combines elements of A and B, one that redefines the problem entirely, and one inspired by how a completely different industry solves an analogous challenge." + +--- + +## Use Cases + +**Validation-Stage Healthtech Team Stuck on a Single Feature Concept** + +A five-person team building a remote patient monitoring platform holds weekly brainstorming sessions that consistently produce variations on the same theme: adding more clinical metrics to the dashboard. The CEO, a former clinician, speaks first in every session, and the team's ideas orbit her initial framing. Diagnosing the failure modes reveals anchoring cascade (the CEO's clinical lens sets the frame) and evaluation apprehension (junior engineers self-censor around a domain expert). Switching to BrainSwarming -- silent, parallel, graph-based -- eliminates both. The top-down decomposition of "improve patient outcomes" produces sub-goals the CEO had not considered (reduce caregiver burnout, increase medication adherence). The bottom-up analysis of resources surfaces a partnership with a pharmacy chain that the engineering team had discussed informally but never raised in a meeting. The two directions connect in a solution: automated medication reminders sent to both patient and caregiver, fulfilled through the pharmacy partnership. The idea never surfaced in six months of verbal brainstorming. + +**Early-Traction Marketplace Reframing Through a Question Burst** + +A freelance-talent marketplace is growing supply (freelancers) at three times the rate of demand (clients). The founding team frames this as a marketing problem: "How do we acquire more clients?" A question burst with two outsiders (a logistics founder and a former teacher) produces seventeen questions in four minutes, three of which reframe the challenge entirely: "What if the freelancers are the customers?" "What would happen if you charged freelancers instead of clients?" "Is the problem too few clients or too many of the wrong freelancers?" The third question triggers a five-whys analysis that reveals the real issue: the platform's open registration attracts freelancers whose skills do not match client demand. The supply-demand imbalance is not a marketing problem -- it is a curation problem. The solution (a selective application process for freelancers) reduces supply growth, increases match quality, and improves client acquisition as a second-order effect. + +**Growth-Stage Consumer Brand Escaping Binary Framing** + +A D2C skincare brand generating $8M in revenue frames its next move as "launch in retail or stay online." The could-vs-should reframe produces five additional options: wholesale to a single prestige retailer as a test (bullets before cannonballs), a pop-up collaboration with a complementary brand, a subscription tier that deepens online revenue without retail risk, licensing the formulations to an established retailer, and a hybrid -- an exclusive online-to-offline experience in one city. The hybrid option, invisible under binary framing, becomes the eventual choice and generates more press coverage than either original option would have alone. + +--- + +## Anti-Patterns + +**Running brainstorming sessions without diagnosing the failure mode first.** The choice of method should depend on the obstacle. If the problem is production blocking, BrainSwarming fixes it. If the problem is a badly framed question, a question burst fixes it. If the problem is binary thinking, the could-vs-should reframe fixes it. Using the wrong tool for the failure mode wastes the session and reinforces scepticism about structured ideation. + +**Allowing the most senior person to speak first.** Regardless of which method is chosen, the highest-ranking person in the room sets the anchor the moment they open their mouth. In structured brainstorming, have the most senior person contribute last or in writing. In a question burst, they participate as an equal questioner, not as a framer. + +**Generating ideas and evaluating them in the same session.** The entire point of ideation is divergent thinking -- expanding the option set. Evaluation is convergent thinking -- narrowing it. Combining both in a single meeting guarantees that evaluation kills the weaker-sounding ideas before they have time to develop. Separate generation from evaluation by at least a day. + +**Treating design thinking as a four-phase waterfall.** Question, care, connect, and commit are concurrent habits, not sequential stages. A team that completes an "empathy phase" and then never returns to observation is performing a ritual, not practising design thinking. + +**Stopping at idea generation.** The most creative option list in the world has zero value if no one commits to evaluating and acting on it. Every ideation session should end with a clear next step: who will evaluate which options, by when, and using what criteria. The question burst methodology explicitly requires a three-week action plan. Adopt the same discipline for every method. + +--- + +## By Stage + +| Stage | Best Method | Rationale | +|-------|-------------|-----------| +| Idea | Question burst + design thinking (Question, Care) | The founder's problem definition is the highest-leverage variable. Reframing the problem through questions and genuine user empathy produces better founding hypotheses than generating solutions to an unvalidated problem. | +| Validation | BrainSwarming + could-vs-should | The team needs divergent alternatives for MVP design, pricing, and positioning. BrainSwarming's speed and inclusiveness suit small teams with limited time. The could-vs-should reframe prevents premature commitment to the first viable option. | +| Early Traction | Structured brainstorming (with fixes) + question burst | The team is large enough for group dynamics to matter but small enough that structural fixes (silent writing, rotating facilitation) are feasible. Periodic question bursts prevent the anchoring cascade that develops as the company's success narrative solidifies. | +| Growth | All methods in rotation | Different challenges demand different tools. Product decisions may benefit from BrainSwarming; strategic decisions from question bursts; customer-experience decisions from design thinking. The discipline is matching method to failure mode, not defaulting to whichever method the team used last. | +| Scale | Question burst + design thinking (Care, Connect) | At scale, the primary failure mode is institutional -- the organisation's own success story frames every problem. Question bursts from outsiders and design-thinking immersion in customer reality counteract the gravitational pull of "how we've always done it." | + +The recurring danger across all stages: confusing the volume of ideas with the quality of alternatives. A session that produces fifty variations on the same theme has not generated fifty alternatives. It has generated one alternative and forty-nine echoes. The measure of a productive ideation session is the diversity of the option set, not its size. + +--- + +## Output Template + +```markdown +# Solution Generation Record + +**Challenge:** [one-sentence description] +**Date:** [date] +**Method used:** [structured brainstorming / question burst / BrainSwarming / design thinking / could-vs-should / combination] +**Rationale for method selection:** [which failure mode does this method address?] + +## Failure Mode Diagnosis +- **Primary failure mode:** [production blocking / evaluation apprehension / social loafing / anchoring cascade / binary framing / wrong problem] +- **Evidence:** [what observations suggest this failure mode?] + +## Ideas Generated +| # | Idea | Source (top-down / bottom-up / question / reframe) | Novel? (does it differ from the team's default thinking?) | +|---|------|-----------------------------------------------------|----------------------------------------------------------| +| 1 | [description] | [source] | [yes/no + why] | +| 2 | [description] | [source] | [yes/no + why] | +| 3 | [description] | [source] | [yes/no + why] | + +## Reframing Questions (if question burst was used) +1. [question that reframes the challenge] +2. [question that challenges a core assumption] +3. [question from an outsider perspective] + +## Next Steps +- **Who evaluates which options:** [names + assignments] +- **Evaluation deadline:** [date] +- **Evaluation method:** [reference evaluating-options skill] +``` + +--- + +## Related Skills + +- **[Decision Traps and Roles](decision-traps-and-roles.md)** -- The traps that distort evaluation also distort ideation; this sibling skill provides the counter-routines to apply before generating solutions. +- **[Evaluating Options](evaluating-options.md)** -- The natural sequel: once alternatives are generated, this skill covers joint evaluation, Even Swaps, risk ranking, and intuition calibration. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- The problem-solution firewall and 3+ Principle complement the question burst and could-vs-should methods presented here. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process model explains why System 1 dominates brainstorming and why structured methods that engage System 2 produce better alternatives. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- When time pressure compresses the ideation window, rapid-decision habits complement the structured methods presented here. +- **[Creative Flow and Inspiration](../creative/creative-flow-and-inspiration.md)** -- The creative practice of courting unexpected connections and separating generation from judgment applies directly to the solution-generation phase of decision-making. diff --git a/plugins/foreman/content/skills/decisions/tough-decision-situations.md b/plugins/foreman/content/skills/decisions/tough-decision-situations.md new file mode 100644 index 0000000..e8329a3 --- /dev/null +++ b/plugins/foreman/content/skills/decisions/tough-decision-situations.md @@ -0,0 +1,277 @@ +--- +name: "tough-decision-situations" +description: "Addresses the four hardest decision scenarios founders face: teams that cannot reach consensus, choices where every option is bad, decisions that have already gone wrong, and calls that must be made under severe time pressure. Provides structured techniques for each scenario including disagree-and-commit protocols, least-worst analysis, early admission and course-correction frameworks, and recognition-primed decision heuristics. Use when the team is deadlocked and unable to converge, when all available options carry significant downside, when a prior decision has clearly failed and needs triage, when time pressure demands rapid judgment with incomplete information, or when standard decision frameworks assume conditions that do not exist." +version: "1.0.0" +category: "decisions" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - consensus + - deadlock + - bad-options + - wrong-decision + - time-pressure + - sunk-cost + - course-correction + - disagree-and-commit + - heuristics + - triage + - decision-recovery + - value-complexity +related_skills: + - choosing-and-executing + - evaluating-and-deciding + - decision-making-under-pressure + - scenario-planning + - learning-from-failure + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +# Tough Decision Situations + +Sometimes every option on the table is bad. The question worth asking is not "which is least bad" but "which generates the most learning for what comes next." Standard decision toolkits assume a minimum viable set of conditions: adequate time, reasonably good options, a team willing to converge, and a future that has not yet proven the decision-maker wrong. Founders operate in an environment where one or more of these conditions is frequently absent. A co-founding team deadlocked on product direction, a pricing decision where every number alienates someone, a market entry that has clearly failed, a competitive threat that demands a response by Friday -- these are not edge cases. They are the texture of entrepreneurial life. This skill provides discrete techniques for the four scenarios that defeat conventional decision frameworks. + +--- + +## The Toolkit + +### Scenario 1: The Team Cannot Reach Consensus + +Consensus is overrated. It produces decisions that reflect the lowest common denominator of the room rather than the sharpest available judgment. The goal is not agreement for its own sake; the goal is a clear decision that the entire team can execute with commitment, even when some members would have chosen differently. + +**Technique: Pre-Committed Decision Architecture** + +Before the discussion begins, define what happens if the group cannot agree. This single act transforms the dynamics of the conversation. Without a fallback mechanism, deadlocked teams simply recycle arguments. With one, participants know that indecision itself has a consequence, which concentrates attention. + +Establish the following before the meeting opens: + +1. **Time boundary.** "We will discuss this for 90 minutes. If consensus has not emerged, we move to the fallback." +2. **Fallback mechanism.** Options include: the accountable executive makes the call, the group votes (simple majority, two-thirds, or advisory), or the issue escalates with a documented majority/minority summary. +3. **Decision rights clarity.** Who has final authority? A vote can be binding or advisory. If advisory, say so before the first ballot, not after. +4. **Dissent protocol.** Dissent during the discussion is encouraged and recorded. Dissent after the decision is made is not permitted unless new material facts emerge. + +**Technique: The Closure Chart** + +Borrowed from Tom Wilson's practice at Allstate: end every decision meeting with a simple three-column chart for each open item -- "Yes," "No," or "Defer." Under "Defer," specify the exact date the decision will be made and the precise additional information or action required to move to a definitive answer. This eliminates the organisational habit of deferring without accountability. + +**Technique: Disagree-and-Commit** + +When the team is split and the deadline is real, the accountable decision-maker chooses. Those who disagreed are expected to execute the decision with the same energy as those who supported it. This is not submission; it is professionalism. The commitment is to the team's ability to learn from the decision, not to the decision's correctness. + +The protocol requires two things in return from the decision-maker: transparency about why the dissenting view was not adopted, and a defined checkpoint at which the decision will be reviewed. If the dissenters were right, the review provides a structured path to course-correction. If they were wrong, the review provides evidence that builds trust in the process. + +--- + +### Scenario 2: Choosing Between Bad Options + +Alexander George, who studied presidential decision-making, identified two forces that make some choices genuinely terrible: uncertainty (the consequences of each option are unknowable in advance) and value complexity (even the "best" choice will harm some people or undermine values the decision-maker would prefer to protect). When both forces are present, conventional pro-and-con analysis collapses under its own weight. + +**Technique: The Four Pitfall Audit** + +Before evaluating options, audit your own cognitive state. Under pressure, four predictable errors distort judgment: + +- **Avoidance.** Refusing to acknowledge the severity of the situation. The supply chain has been fragile for months, but the founder treats each disruption as an isolated incident rather than a systemic failure. +- **Fixation.** Adrenaline narrows focus to the immediate threat, obscuring the broader context. The founder spends all energy on the angry customer in front of them and ignores the structural pricing problem that created the conflict. +- **Oversimplification.** Reducing a multi-dimensional problem to a binary: win or lose, option A or option B. The reality usually contains more alternatives than the panicked mind can perceive. +- **Isolation.** Attempting to solve the problem alone, hiding it from the board, the team, or advisers until it is too late to benefit from their perspective. + +Recognise which pitfall you have fallen into before attempting to evaluate options. The pitfall itself is the first obstacle; the decision is the second. + +**Technique: Expanding the Option Set** + +When every visible option is bad, the instinct is to pick the least bad one. The better instinct is to ask whether the option set itself is complete. Three questions help: + +1. **"Can we do both?"** Binary framing is often artificial. A founder told to choose between cutting staff and cutting product scope may be able to do neither -- by raising a bridge round, renegotiating a vendor contract, or restructuring compensation. +2. **"What would a new entrant do?"** Incumbents are trapped by sunk costs and existing relationships. A thought experiment that removes those constraints often reveals options that were invisible from the inside. +3. **"What is the smallest possible experiment?"** Instead of committing to one bad option, test its least costly version. Have three salespeople call delayed customers to gauge the response before communicating a blanket delay to the full customer base. + +**Technique: Mitigating Value Complexity** + +When any decision will cause harm to some stakeholders, the founder's obligation is not to pretend the harm does not exist but to manage its impact with integrity: + +- **Name the trade-off explicitly.** "This decision will reduce commissions for the eastern sales team. That is a real cost, and I am not minimising it." +- **Compensate or offset.** Find ways to make harmed parties whole in the medium term -- preferential treatment on the next allocation, first access to the next opportunity, public recognition of their sacrifice. +- **Minimise the maximum harm.** People catastrophise. If you can credibly take the worst-case scenario off the table ("no one will lose their job over this"), you defuse the most paralysing fear, even if the remaining news is unpleasant. +- **Frame sacrifice as contribution.** Stakeholders who bear disproportionate cost should be recognised as having made a sacrifice for the organisation, not as having lost a political contest. + +--- + +### Scenario 3: You Have Made the Wrong Decision + +The evidence is mounting. The geographic expansion is haemorrhaging cash. The new hire is not performing. The product pivot has not moved the needle. At some point, optimism becomes denial and persistence becomes the sunk cost fallacy dressed in a founder's conviction. + +**Technique: The Sunk Cost Override** + +Humans are wired to protect investments already made. The antidote is a single question asked with brutal honesty: "If I were making this decision fresh today -- with no prior investment -- would I choose this path?" If the answer is no, the prior investment is irrelevant. It is gone regardless of what happens next. Continuing to invest resources in a failing direction does not recover the sunk cost; it merely adds new losses on top. + +Political capital complicates the calculation. A founder who publicly championed the expansion feels that admitting failure will damage credibility. In practice, the opposite is true. Credibility erodes far faster when a leader clings to a visibly failing initiative than when they acknowledge the mistake and redirect resources. Dorie Clark's research confirms: public, transparent admission of error -- accompanied by a clear articulation of the lesson learned -- generates more respect than quiet persistence generates sympathy. + +**Technique: The Triage Framework** + +Not every wrong decision requires full abandonment. Three paths exist: + +| Path | When to Use | Example | +|------|-------------|---------| +| **Remedy** | The decision is directionally correct but the execution is flawed. The core thesis is sound; the implementation needs adjustment. | A hire with the right attitude but wrong skills can be retrained. A market entry can be scaled back to a single-city pilot. | +| **Course-correct** | The decision addressed a real problem but chose the wrong solution. The problem still needs solving; the approach must change. | A pricing model that alienated enterprise clients can be restructured without abandoning the enterprise segment entirely. | +| **Abandon** | The decision was based on a premise that has been falsified. No amount of execution improvement can rescue it. | A product built for a market that does not exist. A partnership with an organisation whose values are fundamentally misaligned. | + +The discipline is to distinguish between these three paths honestly, without allowing ego or sunk costs to push the founder toward "remedy" when "abandon" is the correct call. + +**Technique: Extracting and Sharing the Lesson** + +Every wrong decision contains diagnostic information about the decision-maker's blind spots. The extraction process asks three questions: + +1. **Was this foreseeable?** Could better data collection, broader consultation, or more rigorous analysis have prevented the error? If yes, the lesson is about process improvement. +2. **What bias was operating?** Was the founder overconfident, anchored on an early data point, swayed by confirmation bias, or seduced by sunk costs? Identifying the specific bias makes it targetable. +3. **What decision rule would have caught this?** Formulate a concrete heuristic -- "Before committing to geographic expansion, require three months of pilot data from at least two cities" -- that can be applied to future decisions of the same type. + +Sharing the lesson publicly, whether with the team, the board, or an industry peer group, transforms a private failure into a public investment in the founder's credibility and the organisation's learning culture. + +--- + +### Scenario 4: Deciding Under Time Pressure + +Rita Gunther McGrath describes the emerging competitive landscape as one where "fast and roughly right decision making will replace deliberations that are precise and slow." The challenge is operational: how does a founder distinguish "roughly right" from "not at all right" when the clock is measured in hours rather than weeks? + +**Technique: Know-Think-Do** + +Nick Tasler's framework reduces time-pressured decisions to three steps: + +1. **Know the ultimate strategic objective.** Of the seven possible considerations competing for attention, which one or two will have the largest positive impact? Of all stakeholders, which one can the founder least afford to disappoint? Criteria overload is the primary killer of speed. Cut it to the essential variable. +2. **Think by consulting an anti-you.** Explain the situation to one person whose perspective differs from yours. The act of articulation frequently clarifies the decision before the other person responds. Their fresh viewpoint is a bonus, not the primary mechanism. +3. **Do something.** Select one option and release the others. The purpose of a decision under time pressure is not to find the perfect answer; it is to get to the next decision. In a world of irreducible uncertainty, forward motion generates data that standing still cannot. + +**Technique: Pre-Established Decision Rules** + +The fastest decisions under pressure are those that were effectively made before the pressure arrived. Founders who have defined their operating principles in advance convert real-time judgment calls into rule applications: + +- "When customer acquisition cost exceeds three times the monthly subscription value, pause the channel and investigate before spending more." +- "When two co-founders disagree on a product decision, the founder closest to the customer makes the call." +- "When a hiring decision is deadlocked after the third interview round, default to the candidate with the strongest reference from a domain expert." + +These rules are not infallible. They are heuristics that sacrifice marginal accuracy for substantial speed -- a trade-off that is almost always favourable under genuine time pressure. + +**Technique: Recognition-Primed Decisions** + +Experienced founders develop pattern libraries through repeated exposure to similar situations. Gary Klein's research on firefighters and military commanders demonstrates that experts under pressure do not compare options analytically; they recognise the situation as belonging to a familiar pattern, mentally simulate the first viable response, and act if the simulation does not reveal a fatal flaw. The implication for founders is clear: decision speed under pressure is a function of experience breadth. The more situations a founder has navigated -- or studied through case analysis, mentorship, and post-mortems -- the larger the pattern library available when the clock is ticking. + +--- + +## Prompts + +**Prompt 1 -- Deadlock Breaker:** +> My team of [number] people has been unable to reach consensus on [describe the decision] after [number] meetings. Describe the positions held by each faction. Then design a 90-minute structured decision session that includes: a time-bounded discussion, a fallback voting mechanism, and a disagree-and-commit protocol. Specify how dissent will be documented and when the decision will be reviewed. + +**Prompt 2 -- Bad Options Analyser:** +> I face a decision where every option has significant downsides: [describe options and their downsides]. For each option, identify: (a) the specific stakeholders harmed, (b) the severity and reversibility of that harm, (c) the learning value generated, and (d) one creative alternative I may not have considered. Then recommend a path forward, including mitigation strategies for the harmed stakeholders. + +**Prompt 3 -- Wrong Decision Triage:** +> I believe I made a wrong decision when I [describe the decision and the evidence of failure]. Walk me through the triage framework: is this a case for remedy, course-correction, or full abandonment? What sunk cost biases might be distorting my assessment? Draft a communication to [my team / my board / my investors] that admits the error, extracts the lesson, and outlines the revised plan. + +**Prompt 4 -- Time-Pressure Decision Protocol:** +> I need to decide [describe the decision] within [time frame]. I have access to [describe available information]. Apply the know-think-do framework: help me identify the single most important strategic objective, challenge my current thinking as an "anti-me," and recommend a specific action. Also suggest one pre-established decision rule I should adopt for future situations of this type. + +--- + +## Use Cases + +**The Deadlocked Co-Founders** + +Two co-founders of a validation-stage healthtech startup have spent six weeks arguing about whether to pursue a B2B or B2C go-to-market strategy. Each has data supporting their position; neither finds the other's evidence compelling. The advisor introduces pre-committed decision architecture: the co-founders agree that if they cannot reach consensus within one more structured 90-minute session, the CEO (the co-founder with the commercial background) will make the final call, and both will execute it for 90 days before reviewing. During the session, the act of knowing that a fallback exists changes the conversation. The commercial co-founder, confident that she holds the tiebreaker, becomes more generous in incorporating elements of the B2C thesis. The technical co-founder, knowing his position will receive a fair 90-day test regardless, engages more constructively. They converge on a B2B-first strategy with a B2C pilot embedded in the timeline. + +**The Pricing Dilemma with No Good Answer** + +A growth-stage marketplace founder must set take rates for a new seller category. A high rate maximises short-term revenue but will drive sellers to a competitor launching in three months. A low rate attracts sellers but cannibalises existing unit economics. A tiered rate adds complexity that the engineering team cannot deliver before launch. The founder applies the option-set expansion technique and discovers a fourth path: a promotional introductory rate with an explicit sunset clause, communicated transparently to sellers. The promotional rate buys data on seller behaviour, the sunset clause preserves long-term economics, and the transparency prevents a trust breach when rates eventually rise. The "no good options" framing dissolves once the artificial constraint of permanence is removed. + +**The Failed Product Launch** + +An early-traction consumer app founder invested six months and significant capital building a social feature that users are not adopting. Usage data after 60 days is unambiguous: retention curves are flat, engagement metrics are declining, and the feature has not moved the North Star metric. The founder applies the sunk cost override -- fresh-start question: would she build this feature today, knowing what she knows now? The answer is clearly no. She moves to triage and determines this is an abandon case: the premise (that social features would drive retention) has been falsified, not merely under-executed. She communicates the decision to the team with the lesson extracted: future feature bets will require a 30-day prototype with live user testing before full engineering investment. The team's morale improves; they had privately doubted the feature for weeks but lacked a framework to surface the concern. + +--- + +## Anti-Patterns + +**Consensus Worship.** Treating unanimity as a prerequisite for action rather than a fortunate bonus. In startup environments, unanimous agreement on strategic direction is rare and often indicates that the team is not thinking critically enough. Disagree-and-commit is not a consolation prize; it is often the healthiest possible outcome. + +**The Sunk Cost Sermon.** Knowing about sunk cost fallacy intellectually while succumbing to it emotionally. Every founder can recite the definition; far fewer can act on it when the sunk cost in question represents their own judgment, reputation, or years of work. The fresh-start question -- "Would I choose this today?" -- must be asked with genuine willingness to hear "no." + +**Analysis as Anaesthetic.** Requesting more data not because the data will improve the decision but because the act of gathering it delays the moment of choice. Under time pressure, this is lethal. Under bad-options conditions, it is merely expensive. In neither case is it helpful. + +**Premature Abandonment.** The mirror image of sunk cost escalation. Some founders, having been burned by persistence, overcorrect and abandon decisions at the first sign of difficulty. The triage framework exists to prevent both errors: distinguishing between decisions that need more time, decisions that need a different approach, and decisions that need to stop entirely. + +**The Heroic Loner.** Facing a tough decision situation alone, either out of pride or a belief that seeking input signals weakness. Isolation is one of the four pitfalls of uncertainty for a reason: it shrinks the option set, eliminates the corrective perspective of others, and delays the alarm until the problem is beyond intervention. The founder's advisory board, co-founders, and mentor network exist precisely for these moments. + +--- + +## By Stage + +| Stage | Primary Tough Situation | Guidance | +|-------|------------------------|----------| +| Idea | **Time pressure.** Runway is short, and the window for experimentation is measured in weeks, not quarters. | Default to the know-think-do framework. Define the single variable that matters most (usually customer signal), consult one trusted adviser, and act. Pre-establish two or three decision rules that match the venture's hypothesis -- e.g., "If the first 20 user interviews do not surface this pain point, pivot the thesis." | +| Validation | **Bad options.** The data from early experiments often presents the founder with unpalatable choices: the product works but the market is small, or the market is large but the product needs fundamental rearchitecting. | Expand the option set before choosing. Ask "can we do both?" and test the smallest viable version of each path. Apply value complexity mitigation when choices affect early employees or beta customers who took a risk on the venture. | +| Early Traction | **Consensus failure.** The founding team is growing, roles are formalising, and disagreements that were once resolved over coffee now fester across departments. | Introduce pre-committed decision architecture and the disagree-and-commit protocol. Define decision rights explicitly. The closure chart becomes a standard meeting artefact. | +| Growth | **Wrong decisions surfacing.** The volume of decisions at growth stage means that some fraction will inevitably prove wrong. The question is how quickly the organisation detects and corrects them. | Institute the triage framework as a standard operating procedure. Normalise the fresh-start question in quarterly reviews. Create a culture where admitting a wrong call is treated as a sign of intellectual honesty rather than incompetence. | +| Scale | **All four simultaneously.** At scale, the organisation faces deadlocks in cross-functional committees, structural bad-option trade-offs in resource allocation, legacy wrong decisions embedded in processes, and competitive time pressure on multiple fronts. | The founder's role shifts from making tough decisions to building systems that surface them early and resolve them quickly. Pre-established decision rules, escalation protocols, and triage frameworks must be institutionalised, not personalised. Decision quality becomes an organisational capability, not an individual skill. | + +--- + +## Output Template + +```markdown +# Tough Decision Brief: [Situation Title] + +**Date:** [YYYY-MM-DD] +**Decision Owner:** [Name and role] +**Scenario Type:** [Consensus failure / Bad options / Wrong decision / Time pressure] + +## Situation Assessment +[2-3 sentences: what happened, why standard approaches have failed, and what makes this situation genuinely difficult.] + +## Cognitive Audit +- **Pitfalls identified:** [avoidance / fixation / oversimplification / isolation -- check all that apply] +- **Biases at risk:** [sunk cost / confirmation / anchoring / overconfidence -- check all that apply] +- **Fresh-start test result:** [Would I make this same decision/choice today? Yes/No/Uncertain] + +## Options Evaluated +| Option | Upside | Downside | Stakeholders Harmed | Learning Value | Reversibility | +|--------|--------|----------|---------------------|----------------|---------------| +| [A] | | | | | | +| [B] | | | | | | +| [C] | | | | | | + +## Decision and Rationale +[The chosen path and the reasoning behind it, including which trade-offs were accepted and why.] + +## Harm Mitigation Plan +| Stakeholder Affected | Nature of Harm | Mitigation Action | Timeline | +|---------------------|----------------|-------------------|----------| +| | | | | + +## Lesson Extracted +- **What went wrong (if applicable):** [root cause] +- **Bias or process gap identified:** [specific] +- **Decision rule for the future:** [concrete heuristic] + +## Review Checkpoint +**Date:** [YYYY-MM-DD] +**Criteria for success/failure:** [specific, measurable] +``` + +--- + +## Related Skills + +- **[Choosing and Executing](choosing-and-executing.md)** -- The companion skill covering the fundamentals of moving from deliberation to action; this skill takes over when conditions are too adverse for standard approaches. +- **[Evaluating and Deciding](../thinking/evaluating-and-deciding.md)** -- Provides the analytical foundation of criteria weighting, margin of safety, and irreversibility testing that this skill extends into hostile conditions. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Overlaps with Scenario 4 but addresses the broader emotional and cognitive dynamics of high-stakes leadership moments. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- Pre-mortem and scenario analysis can prevent some tough decision situations from arising; when they arise regardless, this skill provides the response toolkit. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Extends the lesson-extraction techniques of Scenario 3 into a comprehensive organisational learning practice. +- **[Thomas-Kilmann Conflict Model](../frameworks/thomas-kilmann-conflict.md)** -- Provides the interpersonal framework for navigating the disagreements that underlie Scenario 1 consensus failures. +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- The Inner Citadel concept provides the philosophical grounding for maintaining judgment quality when all available options are bad and emotional pressure is intense. diff --git a/plugins/foreman/content/skills/frameworks/ambidexterity.md b/plugins/foreman/content/skills/frameworks/ambidexterity.md new file mode 100644 index 0000000..d503a79 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/ambidexterity.md @@ -0,0 +1,178 @@ +--- +name: "ambidexterity" +description: "Applies O'Reilly and Tushman's organizational ambidexterity framework to balance exploitation of existing business with exploration of new opportunities. Assesses resource allocation between core operations and innovation initiatives, designs structurally or contextually ambidextrous organizations, and evaluates innovation portfolios. Use when a company needs to protect its core revenue while pursuing new growth, launching separate innovation units, or diagnosing why exploratory initiatives are being starved by day-to-day operations." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - innovation + - organizational-design + - exploitation + - exploration + - dual-strategy +related_skills: + - blue-ocean-strategy + - disruptive-innovation + - kotter-change-model + - business-model-canvas +author: "Fatih Guner" +--- + +# Organizational Ambidexterity + +Consider what it means to be physically ambidextrous: the ability to write fluently with both hands, each performing distinct tasks without compromising the other. Most people cannot do it. Most organizations cannot do it either -- and the organizational version is far more consequential. Ambidexterity in a corporate context means simultaneously excelling at exploiting existing capabilities for current profit and exploring new opportunities for future growth. The concept, formalized by scholars Charles O'Reilly and Michael Tushman, addresses perhaps the deepest tension in business strategy: how to be disciplined and creative at the same time, in the same company, without one impulse strangling the other. + +The reason this matters is not abstract. The business landscape is littered with companies that mastered exploitation -- Kodak, Blockbuster, Nokia -- and failed catastrophically because they could not explore. Conversely, companies that explore without exploiting burn cash with no viable business model underneath. Ambidexterity is the structural answer to this dilemma. + +--- + +## The Framework + +### Exploitation vs. Exploration + +The terms originate from James March's seminal 1991 paper and form the conceptual backbone of ambidexterity theory. + +**Exploitation** is the refinement, efficiency, and optimization of existing products, processes, and customers. It produces near-term revenue, measurable results, and incremental improvement. It feels safe because the feedback loops are tight. + +**Exploration** is the search for new markets, technologies, and business models. It produces long-term growth potential but involves uncertainty, failure, and delayed returns. It feels risky because the feedback loops are loose and ambiguous. + +The challenge: exploitation crowds out exploration. Existing businesses generate revenue, attract executive attention, and demand resource allocation. Innovation labs starve. R&D projects get cut when quarterly numbers disappoint. The urgent devours the important. + +### Three Models of Ambidexterity + +Organizations have attempted to solve this tension through three structural approaches: + +**1. Structural Ambidexterity** +Separate exploration and exploitation into distinct business units with different cultures, metrics, incentives, and leadership -- but integrate them at the senior executive level. + +| Dimension | Exploitation Unit | Exploration Unit | +|-----------|------------------|-----------------| +| Culture | Efficiency, discipline, process | Experimentation, risk-taking, speed | +| Metrics | Revenue, margin, market share | Learning velocity, option value, discovery milestones | +| Time Horizon | Quarterly / annual | 2-5 year bets | +| Leadership Style | Operational excellence | Entrepreneurial vision | +| Risk Tolerance | Low | High | + +The critical design principle: the units must be structurally separate but strategically integrated. The CEO (or a senior leadership team) holds the integration role, ensuring exploration units can access the resources and distribution of the exploitation side without being consumed by its culture. + +**2. Contextual Ambidexterity** +Rather than separating units, build an organizational context in which individuals can judge for themselves when to exploit and when to explore. This requires a culture that simultaneously values discipline and entrepreneurship, stretch and support. + +Contextual ambidexterity is harder to implement but avoids the silos and coordination costs of structural separation. It works best in knowledge-intensive firms where individual judgment is paramount. + +**3. Sequential Ambidexterity** +Alternate between periods of exploitation and exploration. This is the least sophisticated approach and typically the least effective, because timing the switches is difficult and organizational momentum resists the transition. + +### Why Structural Ambidexterity Dominates + +O'Reilly and Tushman's research demonstrates that structurally ambidextrous organizations outperform both purely exploitative firms and those attempting contextual ambidexterity. The reason is architectural: human organizations struggle to hold contradictory cultures simultaneously. Separation with senior integration resolves the contradiction without eliminating either capability. + +### The Integration Challenge + +The hardest part is not creating separate units -- it is integrating them. Common failure modes: + +- The exploration unit is treated as a "skunkworks" curiosity project rather than a strategic priority +- The exploitation unit resents resource allocation to an unproven venture +- No mechanism exists to graduate successful explorations into the mainstream business +- Senior leadership pays lip service to exploration but allocates attention disproportionately to exploitation + +--- + +## Prompts + +**Prompt 1 -- Exploitation/Exploration Audit:** +> Assess my company's current balance between exploitation and exploration. My company is [describe: sector, stage, size, main products/services, recent strategic initiatives]. Estimate what percentage of our resources (budget, headcount, leadership attention) goes to exploitation vs. exploration. Based on our stage and competitive environment, what should the balance be? Identify the three highest-priority adjustments. + +**Prompt 2 -- Structural Ambidexterity Design:** +> Help me design a structurally ambidextrous organization. My current company structure is [describe org chart, key teams, reporting lines]. I want to create a dedicated exploration unit focused on [describe the opportunity or technology]. Define the unit's mandate, reporting structure, culture, metrics, team composition, and budget. Critically, specify how this unit integrates with the core business -- what resources does it draw from, and how do successful innovations graduate into the mainstream? + +**Prompt 3 -- Innovation Portfolio Assessment:** +> Evaluate my company's innovation portfolio through the ambidexterity lens. Here are our current projects and initiatives: [list them]. Classify each as exploitation (core improvement), adjacent exploration (extending into related domains), or transformative exploration (pursuing fundamentally new opportunities). Recommend how to rebalance the portfolio for long-term health, considering our stage ([stage]) and competitive threats. + +--- + +## Use Cases + +**Growth-Stage B2B SaaS Company Launching an AI Product Line** +A $15M ARR B2B SaaS company sees AI-powered features as the future of its category but cannot disrupt its current product -- which generates all revenue -- to build them. The founder applies structural ambidexterity: a dedicated AI team of six engineers operates with its own roadmap, metrics (user engagement with AI features, time-to-value), and sprint cadence. The team sits physically adjacent to the core engineering group but reports directly to the CTO rather than through the VP of Engineering who manages the core product. Integration happens at the weekly leadership meeting, where the AI team presents findings and the core team identifies integration opportunities. After nine months, two AI features are ready for general availability and move into the core product with dedicated support from both teams. + +**Scale-Stage Retail Company Exploring Direct-to-Consumer** +A traditional B2B2C consumer goods company at scale sells through retail partners but faces margin pressure and data blindness. The CEO establishes a DTC exploration unit with its own P&L, brand identity, and digital marketing team. The unit leverages the parent company's supply chain and manufacturing (exploitation assets) but operates with startup-like speed and different KPIs -- customer acquisition cost, lifetime value, and first-party data volume rather than wholesale revenue. The integration mechanism: a quarterly "transfer committee" evaluates which DTC learnings should flow back into the wholesale business and which wholesale capabilities should be made available to the DTC unit. + +**Early-Traction Marketplace Balancing Supply Growth with Product Innovation** +A two-sided marketplace with 500 active suppliers must simultaneously grow its supply base (exploitation) and develop a fundamentally new matching algorithm (exploration). With only 30 employees, structural separation is impractical. The founder implements contextual ambidexterity: engineers spend 80% of their time on core platform development and 20% on experimental projects. The key enabler is a culture that celebrates both operational wins and learning from failed experiments. Weekly demos alternate between "what we shipped" and "what we learned." + +--- + +## Anti-Patterns + +1. **Creating an innovation lab with no integration pathway.** Many companies establish innovation teams as trophies -- visible proof of forward thinking -- without any mechanism to bring innovations into the core business. These labs produce demos and prototypes that never reach customers, and their best people eventually leave out of frustration. + +2. **Starving exploration when exploitation underperforms.** The instinct during a revenue shortfall is to redirect all resources to the core business. This is precisely the moment when the exploitative side is demonstrating its limitations and the exploratory side is most needed. Cutting exploration during downturns is strategically rational in the short term and catastrophic in the long term. + +3. **Applying exploitation metrics to exploration units.** Measuring an exploration team by revenue or margin in its first year is like judging a seed by the weight of fruit it has not yet produced. Exploration requires different metrics: speed of learning, quality of hypotheses tested, option value created. + +4. **Assuming ambidexterity means equal allocation.** The right balance between exploitation and exploration is not 50/50. It depends on industry velocity, competitive position, and company stage. A company in a stable industry with strong market position might allocate 85/15. A company facing technological disruption might need 60/40. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Contextual ambidexterity | Too small for structural separation. Build a culture that values both execution and experimentation. Use time-boxing (e.g., 80/20 allocation) to protect exploration from the gravitational pull of daily operations. | +| Growth | Structural ambidexterity emerges | Large enough to create dedicated exploration units. This is the critical stage for establishing ambidextrous architecture before the exploitation culture calcifies. Design integration mechanisms early. | +| Scale | Institutional ambidexterity | Multiple exploration units may coexist, each targeting different horizons. The CEO's primary strategic role becomes portfolio management across exploitation and exploration initiatives. Board oversight should include innovation pipeline reviews alongside financial performance. | + +--- + +## Output Template + +```markdown +# Ambidexterity Assessment + +**Company:** [Name] +**Stage:** [Current stage] +**Date:** [Date] + +## Current State + +| Dimension | Exploitation | Exploration | Ideal Ratio | +|-----------|-------------|-------------|-------------| +| Budget allocation | [%] | [%] | [Target %] | +| Headcount | [%] | [%] | [Target %] | +| Leadership attention | [%] | [%] | [Target %] | + +## Innovation Portfolio + +| Initiative | Type (Exploit/Adjacent/Transform) | Stage | Metrics | Resource Level | +|-----------|-----------------------------------|-------|---------|----------------| +| [Initiative 1] | [Type] | [Stage] | [KPIs] | [Adequate/Under/Over] | +| [Initiative 2] | [Type] | [Stage] | [KPIs] | [Adequate/Under/Over] | + +## Recommended Structure +- **Model:** [Structural / Contextual / Hybrid] +- **Exploration Unit Mandate:** [Description] +- **Integration Mechanism:** [How exploration connects to core] +- **Graduation Criteria:** [When exploration moves to core] + +## Priority Actions +1. [Action with owner and timeline] +2. [Action with owner and timeline] +3. [Action with owner and timeline] +``` + +--- + +## Related Skills + +- **[Disruptive Innovation](disruptive-innovation.md)** -- Christensen's disruption theory explains why exploitation alone fails; ambidexterity is the organizational architecture that resolves the innovator's dilemma. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- Exploration units often pursue blue ocean opportunities, making ambidexterity the structural enabler and blue ocean the strategic direction. +- **[Kotter's Change Model](kotter-change-model.md)** -- Transitioning from a purely exploitative organization to an ambidextrous one is a change management challenge that benefits from Kotter's eight-step implementation sequence. +- **[Business Model Canvas](business-model-canvas.md)** -- Exploration units benefit from running their own canvas separate from the core business, making assumptions visible and testable before committing resources. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Exploitation units apply Kaizen for continuous refinement while exploration units may use BPR-style radical redesign, mirroring the dual logic of ambidexterity. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- Provides the leadership practices needed to sustain both exploitation and exploration cultures simultaneously within one organization. diff --git a/plugins/foreman/content/skills/frameworks/appreciative-inquiry.md b/plugins/foreman/content/skills/frameworks/appreciative-inquiry.md new file mode 100644 index 0000000..1b02586 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/appreciative-inquiry.md @@ -0,0 +1,223 @@ +--- +name: "appreciative-inquiry" +description: "Guides strengths-based organizational change using Cooperrider's + Appreciative Inquiry 4D cycle: Discovery, Dream, Design, and Delivery. + Surfaces peak experiences and positive patterns to amplify what works rather + than fixing what is broken. Use when addressing team morale, redesigning + processes, integrating acquisitions, reframing organizational challenges, or + running culture transformation initiatives where traditional deficit-based + problem-solving has stalled." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - organisational-development + - change-management + - strengths-based + - strategy + - innovation +related_skills: + - organisational-culture + - kaizen-bpr + - grow-model +author: "Fatih Guner" +--- + +# Appreciative Inquiry + +Stop fixing problems. The orthodox approach to organisational change -- diagnose what is broken, analyse root causes, prescribe solutions -- carries an unexamined assumption: that progress comes from eliminating deficits. David Cooperrider, working at Case Western Reserve University in the 1980s, proposed something radical. What if the fastest path to transformation is not fixing weaknesses but systematically amplifying strengths? What if the questions you ask determine the reality you find -- and organisations that ask "what is wrong?" get very good at cataloguing dysfunction, while organisations that ask "what works brilliantly, and how do we get more of it?" generate energy, alignment, and change that deficit-based approaches rarely achieve? + +This is not positive thinking. Appreciative Inquiry (AI) is a structured methodology backed by four decades of organisational research. It does not deny problems; it reframes the unit of analysis. Rather than treating the organisation as a machine with broken parts, AI treats it as a living system whose best moments contain the DNA of its future. The shift is neither naive nor cosmetic -- it is epistemological. + +--- + +## The Framework + +### The Core Principle: The Constructionist Premise + +Appreciative Inquiry rests on a foundational claim: organisations move in the direction of the questions they ask. Questions are not neutral instruments of discovery; they are interventions that shape what people notice, discuss, and ultimately create. An organisation that habitually asks "why did we fail?" develops sophisticated failure narratives. An organisation that asks "when did we succeed against the odds, and what made that possible?" develops actionable success patterns. + +This is not a rejection of critical analysis. It is a recognition that the inquiry itself is generative -- it creates the conditions for the reality it investigates. + +### The 4D Cycle + +Appreciative Inquiry unfolds through four phases, each building on the previous one: + +#### Discovery: "What Gives Life?" + +The first phase maps the organisation's positive core -- the strengths, peak experiences, best practices, and moments of excellence that already exist. This is accomplished through structured interviews in which every member of the organisation (or a representative sample) answers questions designed to surface what works. + +**Key Discovery questions:** +- Describe a peak experience in this organisation -- a time when you felt most engaged, effective, and proud. What made it possible? +- What do you value most about this organisation? About your work? About your colleagues? +- Without being modest, what do you contribute that makes this organisation stronger? +- What is the core factor that gives life to this organisation -- the thing without which it would cease to exist? + +**Discovery outputs:** +- A collection of stories that embody the organisation's strengths +- Identification of recurring themes and positive patterns +- An inventory of capabilities, assets, and conditions that produce excellence + +The discipline of Discovery is rigorous. It is not a feel-good exercise or a brainstorming session. It requires structured interviewing, systematic theme extraction, and evidence-based pattern recognition. + +#### Dream: "What Might Be?" + +Using the positive core identified in Discovery, the Dream phase envisions what the organisation could become if its strengths were amplified and its best moments became the norm rather than the exception. + +**Key Dream activities:** +- Provocative propositions: bold statements of aspiration grounded in demonstrated capability ("We are an organisation where every customer interaction produces a story worth telling" -- based on evidence from Discovery that this already happens sometimes) +- Collective visioning exercises that translate individual peak experiences into organisational possibilities +- Mapping the gap between current reality and the envisioned future, framed not as deficit but as potential + +**Dream outputs:** +- A shared vision statement grounded in demonstrated strengths +- Provocative propositions for each strategic domain +- Energy and alignment around a future state that feels achievable because it is extrapolated from existing excellence + +#### Design: "What Should Be?" + +The Design phase translates the Dream into concrete organisational architecture: processes, structures, roles, systems, and strategies that would enable the envisioned future. + +**Key Design activities:** +- Social architecture design: what structures, processes, and norms would make the Dream the default operating mode? +- Identification of enabling conditions: what must be true for the organisation's best moments to occur reliably, not sporadically? +- Prototype development: what small-scale experiments can test elements of the new design? + +**Design outputs:** +- Specific structural and process changes aligned with the Dream +- Pilot programmes and experiments +- Accountability frameworks for implementation + +#### Delivery (or Destiny): "What Will Be?" + +The final phase translates Design into action. It focuses on implementation, experimentation, and continuous adaptation. Unlike traditional change management, which follows a plan, Delivery in Appreciative Inquiry is emergent -- it learns and adjusts as the organisation experiments with new ways of operating. + +**Key Delivery activities:** +- Launch pilot programmes designed in the previous phase +- Establish feedback loops to capture learning +- Celebrate and publicise early successes (reinforcing the positive core) +- Adjust design elements based on real-world results + +**Delivery outputs:** +- Implemented changes with measurable outcomes +- New stories of success that feed back into the Discovery phase, creating a self-reinforcing cycle +- An organisational capability for strengths-based change that outlasts any single initiative + +### The 4D Cycle as a Continuous Loop + +``` + Discovery ──────► Dream + ▲ │ + │ ▼ + Delivery ◄────── Design +``` + +The cycle is not a one-time intervention but a repeatable methodology. Each Delivery phase generates new stories and data that feed the next Discovery phase, creating an upward spiral of organisational capability. + +--- + +## Prompts + +**Prompt 1 -- Strengths-Based Diagnostic:** +> Instead of analysing what is wrong with my company, help me conduct an Appreciative Inquiry Discovery phase. I will describe our best moments, peak customer experiences, and times when the team performed at its highest level: [describe 3-5 peak experiences]. Extract the recurring themes, underlying conditions, and core strengths that made those moments possible. Then identify how those strengths could be systematically amplified. + +**Prompt 2 -- Provocative Proposition Development:** +> Based on the following organisational strengths and peak experiences: [describe them], help me craft 5 provocative propositions for my company -- bold aspirational statements about what we could become, grounded in evidence of what we have already demonstrated. Each proposition should be specific enough to guide action and ambitious enough to generate energy. + +**Prompt 3 -- 4D Cycle Planning:** +> I want to run a full Appreciative Inquiry process with my team of [size] over [timeframe]. Design the complete 4D cycle: specific questions for the Discovery phase interviews, a facilitation plan for the Dream phase workshop, a Design phase structure for translating vision into architecture, and a Delivery phase with pilot experiments and feedback loops. Context: [describe your company, stage, and the strategic challenge you are addressing]. + +**Prompt 4 -- Reframing a Problem as an Inquiry:** +> My company is facing this challenge: [describe the problem]. Help me reframe it using the Appreciative Inquiry approach. Instead of asking "why is this broken?", construct a set of affirmative questions that redirect attention toward the positive core. Then outline a Discovery process that would surface actionable strengths related to this challenge. + +--- + +## Use Cases + +**Early-Traction Startup Struggling with Team Morale** +A 20-person startup has been through a difficult pivot. Morale is low, and the conventional response -- an all-hands where leadership acknowledges problems and presents a recovery plan -- risks reinforcing the deficit narrative. Instead, the CEO runs a compressed Appreciative Inquiry cycle. Discovery: each team member interviews a colleague about their peak experience at the company and what they value most. Dream: the team collectively envisions what the company looks like when those peak moments are the norm. Design: three concrete changes emerge -- restructured sprint planning based on the team's best sprint ever, a weekly "wins" ritual modelled on the team's most energising celebration, and a customer feedback loop inspired by the product's most successful launch. The process takes two weeks and produces measurable morale and productivity improvements within a month. + +**Growth-Stage Company Redesigning Customer Success** +A 150-person SaaS company faces rising churn. The instinct is to analyse churned accounts and fix the failure patterns. Appreciative Inquiry inverts the analysis: the customer success team conducts Discovery interviews with the company's longest-tenured and highest-NPS accounts, extracting what made those relationships exceptional. Common themes emerge -- proactive quarterly business reviews, a dedicated technical advocate, and early involvement in product roadmap discussions. These themes become the Design for a new customer success model applied to all accounts, not just the top tier. Churn decreases 18% in two quarters. + +**Scale-Stage Company Integrating an Acquisition** +A 600-person company acquires a 100-person competitor. Rather than imposing the acquirer's processes on the target, leadership conducts a joint Appreciative Inquiry across both organisations. Discovery surfaces what each company does best. Dream envisions a combined entity that amplifies both organisations' strengths. Design produces an integration plan that preserves the acquired company's best practices (agile product development, close customer relationships) while extending the acquirer's strengths (enterprise sales, compliance infrastructure). Employee retention during the integration exceeds industry benchmarks by 40%. + +--- + +## Anti-Patterns + +1. **Appreciative Whitewashing.** Using the framework to suppress legitimate criticism or silence dissent. "Focus on the positive" is not a mandate to ignore serious dysfunction. AI does not deny problems -- it approaches them through a different lens. If employees are burning out, the question is not "what do you love about working here?" but "when have you felt most energised and supported, and what conditions made that possible?" + +2. **Skipping Discovery.** Jumping to Dream without the disciplined interview process that surfaces genuine strengths. Without rigorous Discovery, the Dream phase produces fantasies untethered from organisational reality -- aspirational statements that inspire no one because they connect to nothing that already exists. + +3. **Treating AI as a Workshop, Not a Methodology.** Running a single Appreciative Inquiry offsite and expecting lasting change. The 4D cycle is designed to be continuous. A one-off workshop produces enthusiasm that dissipates within weeks unless the Design and Delivery phases follow through. + +4. **Ignoring Structural Issues.** Appreciative Inquiry is powerful for cultural and strategic challenges but insufficient for addressing structural problems -- a toxic manager, a fundamentally flawed business model, a compliance violation. Strengths-based inquiry complements but does not replace structural intervention. + +5. **Leader-Driven Discovery.** Conducting the Discovery phase by asking only leadership about peak experiences. AI is deliberately democratic -- its power comes from surfacing perspectives and stories from every level of the organisation. Leadership-only Discovery produces a self-congratulatory narrative, not an accurate portrait of the positive core. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Team energy and direction | Small teams benefit from compressed AI cycles that surface shared values and peak experiences, establishing a strengths-based culture before deficit-based habits calcify. | +| Growth | Scaling what works | Growth-stage companies have proven strengths but risk losing them during rapid scaling. AI systematically identifies and codifies what works so it can be replicated across new teams and geographies. | +| Scale | Organisational transformation | At scale, AI provides an alternative to top-down change management. Large-scale AI summits (involving hundreds of participants) generate alignment and energy that directive approaches cannot match. | + +--- + +## Output Template + +```markdown +# Appreciative Inquiry: [Challenge/Opportunity] + +## Discovery Phase Summary +### Peak Experience Themes +1. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] +2. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] +3. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] + +### Positive Core Inventory +- **Strengths:** [List organisational strengths surfaced] +- **Conditions for excellence:** [What must be true for peak performance] +- **Untapped assets:** [Capabilities present but underutilised] + +## Dream Phase: Provocative Propositions +1. "[Bold aspirational statement grounded in Discovery evidence]" +2. "[Bold aspirational statement grounded in Discovery evidence]" +3. "[Bold aspirational statement grounded in Discovery evidence]" + +## Design Phase: Enabling Architecture +| Design Element | Current State | Desired State | Change Required | +|---------------|---------------|---------------|-----------------| +| [Process/Structure] | [Now] | [Future] | [Specific change] | + +## Delivery Phase: Pilot Experiments +| Experiment | Owner | Timeline | Success Metric | +|-----------|-------|----------|----------------| +| [Pilot 1] | [Name] | [Dates] | [How measured] | +| [Pilot 2] | [Name] | [Dates] | [How measured] | + +## Feedback Loop +- Review cadence: [Weekly/Bi-weekly] +- Learning capture: [Method] +- Cycle refresh: [When to re-enter Discovery] +``` + +--- + +## Related Skills + +- **[Organisational Culture](organisational-culture.md)** -- Appreciative Inquiry operates on Schein's Layer 2 (espoused values) and Layer 3 (basic assumptions), shifting both by reframing the questions the organisation asks about itself. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Both frameworks share a commitment to continuous improvement but from opposite starting points: Kaizen eliminates waste while AI amplifies strengths, making them a complete improvement methodology when combined. +- **[GROW Model](grow-model.md)** -- GROW's Reality and Options phases parallel AI's Discovery and Dream phases at the individual coaching level, providing a structurally complementary one-on-one tool. +- **[Kotter's Change Model](kotter-change-model.md)** -- Kotter provides the sequential change management structure while AI provides the strengths-based energy and engagement that sustain momentum through Kotter's eight steps. +- **[Psychological Safety](psychological-safety.md)** -- The Discovery phase requires honest sharing of peak experiences, which only occurs when Edmondson's psychological safety conditions are in place. +- **[Growth Mindset](growth-mindset.md)** -- Dweck's belief that capability develops through effort aligns with AI's assumption that an organisation's best moments contain the DNA for its future growth. diff --git a/plugins/foreman/content/skills/frameworks/art-of-war.md b/plugins/foreman/content/skills/frameworks/art-of-war.md new file mode 100644 index 0000000..36779c3 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/art-of-war.md @@ -0,0 +1,207 @@ +--- +name: "art-of-war" +description: "Applies Sun Tzu's strategic principles to competitive business + situations, covering self-knowledge and competitor intelligence, winning + without direct confrontation, speed and timing, terrain analysis, and + strategic positioning. Use when assessing competitive landscapes, developing + market entry strategies, evaluating when to fight or avoid competitors, + conducting competitive intelligence audits, or designing stealth positioning + for startups facing well-resourced incumbents." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - competitive-strategy + - leadership + - positioning + - tactical-advantage + - decision-making +related_skills: + - porters-five-forces + - blue-ocean-strategy + - scenario-planning + - swot-pest-analysis +author: "Fatih Guner" +--- + +# Sun Tzu's Art of War + +Written approximately 2,500 years ago by a Chinese military strategist whose very existence some scholars dispute, *The Art of War* remains one of the most frequently purchased business books on Amazon. It sits on the bookshelves of Fortune 500 CEOs, Silicon Valley founders, and Wall Street traders with the same stubborn persistence as it sat in the libraries of Napoleon, Mao Zedong, and General Douglas MacArthur. This longevity is not nostalgia or affectation. Sun Tzu articulated principles of competitive strategy -- positioning, information asymmetry, resource allocation, the primacy of winning without fighting -- that predate Michael Porter by two millennia but remain structurally identical to the frameworks taught in modern business schools. The language is military; the logic is universal. + +--- + +## The Framework + +Sun Tzu's treatise spans thirteen chapters, but its strategic wisdom distills into several core principles that map directly onto entrepreneurial competition. + +### Principle 1: Know Yourself and Know Your Enemy + +> "If you know the enemy and know yourself, you need not fear the result of a hundred battles." + +This is Sun Tzu's most cited passage, and it is frequently reduced to a platitude. The operational meaning is precise: competitive advantage flows from superior information. Companies that understand their own capabilities honestly AND understand their competitors' capabilities accurately will outperform those with blind spots in either direction. + +**The Knowledge Matrix:** + +| | Know Yourself | Do Not Know Yourself | +|--|--------------|---------------------| +| **Know Enemy** | Victory in every engagement -- strategic clarity enables decisive action | Alternating wins and losses -- you exploit competitor weakness but are surprised by your own | +| **Do Not Know Enemy** | Stalemate or defensive survival -- internal strength without external awareness leads to missed opportunities | Certain defeat -- operating blind on both dimensions | + +Most startups occupy the lower-left quadrant: they know their product intimately but have only superficial knowledge of their competitive landscape. Worse, many deliberately avoid competitive analysis, treating it as a distraction from customer focus. Sun Tzu would find this reckless. + +### Principle 2: Win Without Fighting + +> "The supreme art of war is to subdue the enemy without fighting." + +Translated into business: the best competitive strategy is one that makes direct confrontation unnecessary. This principle aligns with Blue Ocean Strategy (creating uncontested markets) and with Porter's concept of strategic positioning (choosing a unique position that competitors cannot easily replicate without abandoning their own strategy). + +For startups, winning without fighting means: +- Choosing market segments where incumbents have structural reasons not to compete +- Building defensible advantages (network effects, data moats, regulatory expertise) rather than competing on features alone +- Converting potential competitors into partners or acquirers before conflict escalates + +### Principle 3: The Primacy of Speed and Timing + +> "Speed is the essence of war." + +Sun Tzu repeatedly emphasizes that a smaller, faster force defeats a larger, slower one when timing and positioning are right. In startup terms: execution speed is a competitive advantage independent of resources. The startup that ships in weeks what the incumbent takes months to build captures market learning faster, iterates faster, and compounds advantage over time. + +Speed, however, is not haste. Sun Tzu distinguishes between swift execution (desirable) and impulsive action (disastrous). The difference is preparation: the general who has thoroughly planned can act swiftly when the moment arrives. + +### Principle 4: Terrain and Positioning + +> "The clever combatant imposes his will on the enemy, but does not allow the enemy's will to be imposed on him." + +Sun Tzu devotes extensive analysis to terrain -- the physical environment in which battles are fought. In business, terrain is the competitive landscape: market structure, distribution channels, regulatory environment, customer buying behavior, technology platforms. The strategist who chooses favorable terrain -- and forces competitors to fight on unfavorable terrain -- gains structural advantage. + +Favorable terrain for startups includes: +- Markets with high customer pain and low incumbent attention +- Technology platforms where the startup has native expertise and incumbents must learn +- Regulatory environments that create barriers benefiting the startup's approach +- Customer segments too small for large competitors to justify serving + +### Principle 5: Deception and Unpredictability + +> "All warfare is based on deception." + +Sun Tzu advocates appearing weak when strong, appearing strong when weak, appearing close when far, and appearing far when close. In business, this translates to competitive stealth: not telegraphing strategic moves, maintaining optionality about direction, and avoiding the competitive signaling that draws premature attention. + +Stealth is particularly valuable for startups: operating under the radar of incumbents provides time to build capability before facing a competitive response. The startup that announces its grand vision before achieving product-market fit invites competitive preemption without any defensive position. + +### Principle 6: The Cost of Prolonged Conflict + +> "There is no instance of a country having benefited from prolonged warfare." + +Extended competitive battles -- price wars, feature wars, marketing wars -- drain resources and destroy value for all participants. Sun Tzu counsels decisive action over attrition. For startups with limited capital, this is existential guidance: avoid protracted fights with better-funded competitors. Either win quickly through superior positioning or redirect to terrain where the fight is avoidable. + +--- + +## Prompts + +**Prompt 1 -- Competitive Intelligence Map:** +> Apply Sun Tzu's "know yourself, know your enemy" framework to my competitive situation. My company is [describe: product, market, stage, key strengths]. My known competitors are [list competitors]. For each competitor, assess: What are their strengths? Weaknesses? Strategic priorities? Where are they investing? For my own company, assess: What are our honest strengths and blind spots? Where does our self-knowledge have gaps? Build a knowledge matrix showing where we have information advantage and where we are operating blind. + +**Prompt 2 -- Win Without Fighting Strategy:** +> Help me develop a strategy to "win without fighting" in my market. My company competes in [describe market]. Rather than direct confrontation with [competitors], identify: (1) Market segments where incumbents have structural reasons not to compete, (2) Defensible positions we can build that make competition irrelevant, (3) Potential competitor-to-partner conversions, (4) Positioning moves that change the terms of competition. Frame the output as a strategic positioning plan. + +**Prompt 3 -- Terrain Analysis:** +> Analyze the competitive terrain of my market using Sun Tzu's terrain framework. My market is [describe]. Map the terrain across these dimensions: regulatory environment, technology platform dynamics, customer buying behavior, distribution channels, network effects, and data advantages. Where is the terrain favorable for us? Where is it hostile? What positioning moves would shift us to more favorable ground? Present as a terrain map with strategic recommendations. + +**Prompt 4 -- Speed Audit:** +> Evaluate my company's execution speed relative to competitors using Sun Tzu's principle of speed. My company is [describe]. Our typical cycle times are: [describe -- e.g., time to ship a feature, time to close a sale, time to onboard a customer, time to make a strategic decision]. Compare these to what I know about competitors: [describe]. Where do we have speed advantages? Where are we slower? What structural changes would increase our speed without sacrificing quality? Distinguish between genuine speed and reckless haste. + +--- + +## Use Cases + +**Validation-Stage Fintech vs. Banking Incumbents** +A fintech startup targeting underbanked small businesses uses Sun Tzu's terrain analysis to identify favorable ground: the regulatory complexity of small-business lending creates a knowledge moat; banks find the segment unprofitable below $500K loan sizes; and the startup's technology enables automated underwriting at volumes that are uneconomical for manual bank processes. Rather than competing on interest rates (a fight the startup cannot win), it competes on speed and accessibility -- terrain where its technology advantage is decisive. + +**Growth-Stage SaaS Company Facing an Enterprise Incumbent's Downmarket Move** +A mid-market SaaS company discovers that a major enterprise competitor is launching a simplified product targeting its segment. Applying Sun Tzu's principles, the founder resists the impulse to respond with feature parity (prolonged conflict on unfavorable terrain). Instead, the company accelerates its own upmarket movement into the mid-enterprise segment -- territory the incumbent is vacating to pursue the downmarket opportunity. The competitive response becomes a strategic repositioning. + +**Early-Traction Marketplace Using Stealth Positioning** +A two-sided marketplace for freelance legal services deliberately avoids press coverage and public positioning during its first 18 months, operating in what Sun Tzu would call deceptive obscurity. By the time a well-funded competitor launches with a PR blitz, the marketplace has quietly assembled 2,000 vetted attorneys and 500 active corporate clients -- a supply-side network effect that the competitor's marketing budget cannot replicate quickly. The stealth period converted time into structural advantage. + +--- + +## Anti-Patterns + +1. **Taking the military metaphor too literally.** Business is not war. Competitors are not enemies to be destroyed. Customers are not territory to be conquered. The metaphor illuminates dynamics of positioning, information, and resource allocation. Applied too aggressively, it produces a toxic, zero-sum culture that repels talent and alienates partners. + +2. **Using Sun Tzu quotes as a substitute for analysis.** The text is aphoristic by design, which makes it easy to quote and difficult to operationalize. Reciting "all warfare is based on deception" is not a strategy. The value lies in translating the principles into specific competitive moves for specific market contexts. + +3. **Confusing stealth with paralysis.** Sun Tzu advocates deception and unpredictability, not inaction. Founders who use "operating in stealth mode" as justification for avoiding market feedback, delaying launch, or deferring hard decisions have mistaken invisibility for strategy. + +4. **Ignoring the "know yourself" half of the equation.** Most entrepreneurs overinvest in competitive intelligence and underinvest in honest self-assessment. Sun Tzu's framework requires both. The startup that understands its competitors perfectly but overestimates its own capabilities will still fail. + +5. **Applying offensive strategy from a position of weakness.** Sun Tzu is explicit that the weak should defend, not attack. Startups with limited capital that initiate price wars, launch aggressive marketing campaigns, or attempt frontal assaults on well-resourced competitors are violating this principle. Defend first, build strength, then choose your moment. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Terrain selection | The most consequential strategic decision is which terrain (market segment, customer persona, problem space) to compete on. Choose ground where your capabilities create asymmetric advantage and incumbents face structural disadvantages. | +| Early Traction | Speed as weapon | With product-market fit emerging, execution speed becomes the primary competitive advantage. Ship faster, learn faster, iterate faster. Sun Tzu's emphasis on swift, decisive action is most directly applicable at this stage. | +| Growth | Positioning and alliances | Competition intensifies. Strategic positioning -- choosing where NOT to compete as much as where to compete -- becomes critical. Evaluate whether competitors should be fought, avoided, or converted to partners. | +| Scale | Information dominance | At scale, the organization can invest in systematic competitive intelligence. Build formal processes for tracking competitor moves, market shifts, and emerging threats. The "know your enemy" principle becomes an institutional capability rather than a founder instinct. | + +--- + +## Output Template + +```markdown +# Competitive Strategy Brief (Sun Tzu Framework) + +**Company:** [Name] +**Market:** [Description] +**Date:** [Date] + +## Knowledge Matrix + +| Dimension | Our Assessment | Confidence Level | Intelligence Gaps | +|-----------|---------------|-----------------|-------------------| +| Our strengths | [Assessment] | [High/Medium/Low] | [What we do not know about ourselves] | +| Our weaknesses | [Assessment] | [High/Medium/Low] | [Blind spots] | +| Competitor A strengths | [Assessment] | [High/Medium/Low] | [What we do not know about them] | +| Competitor A weaknesses | [Assessment] | [High/Medium/Low] | [Intelligence needed] | + +## Terrain Analysis +**Favorable ground:** [Where we have structural advantage] +**Unfavorable ground:** [Where competitors have advantage] +**Contested ground:** [Where advantage is undetermined] + +## Strategic Posture +- [ ] Defend (build strength before engaging) +- [ ] Maneuver (reposition to favorable terrain) +- [ ] Attack (exploit specific competitor weakness) +- [ ] Avoid (redirect to uncontested space) + +## Key Moves +1. [Strategic action with rationale tied to Sun Tzu principle] +2. [Strategic action] +3. [Strategic action] + +## Speed Advantage Assessment +| Process | Our Cycle Time | Competitor Cycle Time | Advantage | +|---------|---------------|----------------------|-----------| +| [Process] | [Time] | [Time] | [+/-] | +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](porters-five-forces.md)** -- Porter's structural analysis of competitive forces is the modern academic equivalent of Sun Tzu's terrain analysis, providing analytical rigour to complement the strategic mindset. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- The purest expression of Sun Tzu's "win without fighting" principle: create uncontested market space where competition becomes irrelevant. +- **[Scenario Planning](scenario-planning.md)** -- Sun Tzu's emphasis on preparation and contingency aligns with scenario planning's structured approach to anticipating multiple futures. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- Operationalizes Sun Tzu's "know yourself, know your enemy" principle as a structured assessment of strengths, weaknesses, opportunities, and threats. +- **[First-Mover Strategy](../game-theory/first-mover-strategy.md)** -- Sun Tzu's principles of speed, timing, and seizing initiative find their modern game-theoretic expression in first-mover advantage analysis. +- **[Information Asymmetry](../game-theory/information-asymmetry.md)** -- Sun Tzu's emphasis on intelligence superiority and deception maps directly to the strategic exploitation of information asymmetry in competitive contexts. diff --git a/plugins/foreman/content/skills/frameworks/balanced-scorecard.md b/plugins/foreman/content/skills/frameworks/balanced-scorecard.md new file mode 100644 index 0000000..51f37cf --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/balanced-scorecard.md @@ -0,0 +1,236 @@ +--- +name: "balanced-scorecard" +description: "Builds and evaluates Kaplan and Norton's Balanced Scorecard across four perspectives: Financial, Customer, Internal Process, and Learning and Growth. Creates strategy maps linking causal chains from learning investments through process improvements to customer outcomes and financial results. Use when designing KPI systems, aligning teams around strategy, diagnosing why financial metrics are lagging, auditing measurement balance, or establishing leading indicators for organizational health." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - performance-measurement + - strategic-alignment + - kpi-design + - strategy-execution + - management-systems +related_skills: + - swot-pest-analysis + - systems-thinking + - kaizen-bpr + - net-promoter-score +author: "Fatih Guner" +--- + +# Balanced Scorecard + +Your financial statements are lying to you. Not through fraud -- through omission. Revenue, profit margins, and cash flow tell you what happened. They say nothing about what will happen. A company can post record quarterly earnings while its best engineers are updating their LinkedIn profiles, its customer satisfaction is cratering, and the process that produces its core product is one key-person dependency away from collapse. By the time these realities appear in the financial statements, the damage is done and the cost of recovery has multiplied. Robert Kaplan and David Norton published "The Balanced Scorecard" in Harvard Business Review in 1992, and for good reason it became one of the most widely adopted management frameworks of the past three decades: it forces organisations to measure what matters before it shows up in the P&L. + +--- + +## The Framework + +### The Four Perspectives + +The Balanced Scorecard translates strategy into measurable objectives across four interdependent dimensions. Each perspective answers a different question, and together they provide a complete picture of organisational health. + +#### Perspective 1: Financial -- "How do we look to shareholders?" + +This is the perspective most organisations already measure obsessively. The Balanced Scorecard does not diminish its importance but contextualises it: financial results are the outcome of performance in the other three perspectives. + +**Typical measures for startups:** +- Monthly recurring revenue (MRR) and growth rate +- Gross margin and unit economics (LTV:CAC) +- Burn rate and runway +- Revenue per employee + +The financial perspective answers whether the strategy is delivering economic results. When financial metrics deteriorate, the Balanced Scorecard directs attention to the other three perspectives to identify the root cause -- rather than the reflexive response of cutting costs or chasing revenue. + +#### Perspective 2: Customer -- "How do customers see us?" + +Customers are the source of revenue, yet most companies measure customer health crudely, if at all. This perspective captures how well the organisation delivers value to those it serves. + +**Typical measures for startups:** +- Net Promoter Score (NPS) or customer satisfaction score +- Customer retention and churn rates +- Customer acquisition cost and payback period +- Market share within target segment + +The customer perspective serves as a leading indicator of financial performance. Declining satisfaction predicts declining revenue -- but with a lag that financial metrics alone cannot detect. + +#### Perspective 3: Internal Process -- "What must we excel at?" + +The operational engine that converts resources into customer value. This perspective identifies the critical processes that drive performance in the customer and financial perspectives. + +**Typical measures for startups:** +- Product development cycle time (idea to release) +- Defect rate or quality metrics +- Onboarding time (employee and customer) +- Operational efficiency ratios + +The process perspective is where Kaizen and BPR live. Measuring process performance creates visibility into the operational health that eventually determines customer experience and financial results. + +#### Perspective 4: Learning & Growth -- "Can we continue to improve and create value?" + +The foundation. People, culture, technology, and organisational capacity to learn and adapt. This perspective is the most neglected and the most consequential for long-term survival. + +**Typical measures for startups:** +- Employee engagement and satisfaction scores +- Skill development investment per employee +- Knowledge-sharing activity (documentation, internal talks) +- Innovation pipeline (experiments run, hypotheses tested) + +Kaplan and Norton argued that learning and growth is the ultimate leading indicator: it drives process improvement, which drives customer satisfaction, which drives financial results. Neglecting it is borrowing from the future. + +### The Strategy Map: Connecting the Dots + +The four perspectives are not independent dashboards. They form a causal chain: + +``` +Learning & Growth + | + | (Skilled, engaged people build better...) + v +Internal Processes + | + | (Excellent processes deliver superior...) + v +Customer Value + | + | (Satisfied customers generate...) + v +Financial Results +``` + +A Strategy Map makes these causal links explicit. For each strategic objective, the map traces the hypothesis: "If we invest in [learning/growth initiative], then [process] will improve, which will deliver [customer outcome], resulting in [financial result]." + +This is the Balanced Scorecard's deepest contribution -- not as a measurement tool but as a strategy execution system. The map forces leaders to articulate the theory of how their strategy creates value, then measure whether that theory holds. + +### Building a Balanced Scorecard + +For each perspective, define: + +1. **Objectives** -- What are we trying to achieve? (Qualitative) +2. **Measures** -- How will we know if we are achieving it? (Quantitative) +3. **Targets** -- What level of performance constitutes success? (Specific) +4. **Initiatives** -- What actions will drive us toward the target? (Actionable) + +| Perspective | Objective | Measure | Target | Initiative | +|-------------|-----------|---------|--------|------------| +| Financial | Achieve sustainable unit economics | LTV:CAC ratio | >3:1 by Q4 | Reduce CAC through organic channel investment | +| Customer | Increase customer advocacy | NPS | >50 by Q3 | Launch customer success programme | +| Internal Process | Accelerate product delivery | Sprint velocity / release frequency | Bi-weekly releases by Q2 | Implement CI/CD pipeline | +| Learning & Growth | Build data-driven culture | % decisions backed by data | >70% by Q4 | Analytics training + dashboard access for all teams | + +--- + +## Prompts + +**Prompt 1 -- Balanced Scorecard Construction:** +> "Build a Balanced Scorecard for my business: [describe company, stage, strategy, key challenges]. For each of the four perspectives (Financial, Customer, Internal Process, Learning & Growth), define two strategic objectives, the measures that track progress, specific targets for the next [timeframe], and one initiative that drives each objective." + +**Prompt 2 -- Strategy Map Design:** +> "Create a Strategy Map for this business strategy: [describe strategy]. Trace the causal chain from Learning & Growth investments through Internal Process improvements through Customer outcomes to Financial results. For each causal link, state the hypothesis being tested and the leading indicator that would confirm or disconfirm the link." + +**Prompt 3 -- Scorecard Diagnostic:** +> "Analyse this set of business metrics: [list current metrics]. Map each metric to the Balanced Scorecard perspective it belongs to. Identify which perspectives are over-measured, which are under-measured, and which critical gaps exist. Recommend specific new metrics to create a balanced view." + +**Prompt 4 -- Leading vs. Lagging Indicator Audit:** +> "Review our current KPIs: [list KPIs]. Classify each as a leading indicator (predicts future performance) or a lagging indicator (reports past performance). For every lagging indicator that lacks a corresponding leading indicator, recommend one. Ensure each of the four Balanced Scorecard perspectives has at least one leading indicator." + +--- + +## Use Cases + +**Early-Traction Startup Aligning Team Around Strategy** + +A 15-person startup has been measuring only two things: MRR growth and burn rate. The founder senses that the team is pulling in different directions but lacks a framework to diagnose why. Building a Balanced Scorecard reveals the gap: there are no customer metrics (nobody is tracking churn or NPS), no process metrics (the team ships features but does not measure cycle time or defect rates), and no learning metrics (the last team retrospective was four months ago). The scorecard provides a shared language for what success means across all four dimensions. Within one quarter, the team reports feeling more aligned -- not because priorities changed, but because they became visible. + +**Growth-Stage Company Preventing the "Growth Trap"** + +A company growing at 200% year-over-year discovers through a Balanced Scorecard review that its Learning & Growth metrics are deteriorating: employee satisfaction has dropped from 78 to 54, voluntary turnover has doubled, and the onboarding backlog means new hires take 90 days to become productive. Meanwhile, Internal Process metrics show that release frequency has declined and defect rates are rising. Customer metrics are stable -- for now. The scorecard's causal logic makes the trajectory visible: Learning & Growth degradation will propagate through processes, then customer experience, and eventually financials, within two to three quarters. The company pauses its hiring plan, invests in onboarding infrastructure, and introduces a structured engineering career ladder. The financial impact is negative for one quarter; the three-quarter outlook improves dramatically. + +--- + +## Anti-Patterns + +**Financial Myopia.** Building a "Balanced" Scorecard with fifteen financial metrics, three customer metrics, two process metrics, and one learning metric. The point is balance. If 60% of your measures are financial, you have a sophisticated P&L, not a Balanced Scorecard. + +**Metric Overload.** Tracking forty-seven KPIs across the four perspectives. The Balanced Scorecard works through focus, not comprehensiveness. Kaplan and Norton recommended fifteen to twenty-five measures maximum. For early-stage startups, eight to twelve is sufficient: two to three per perspective. + +**Vanity Metrics in Disguise.** Populating the scorecard with measures that look good but drive no action. "Total registered users" in the Customer perspective is meaningless if most users are inactive. Every metric must connect to a decision: if the number changes, what would we do differently? + +**Ignoring the Causal Chain.** Treating the four perspectives as four separate dashboards rather than a linked system. If a customer metric declines, the Balanced Scorecard's logic directs attention to Internal Process. If a process metric declines, look to Learning & Growth. Without the causal chain, the scorecard becomes four independent measurement exercises that add no strategic insight. + +**Set-and-Forget.** Designing the Balanced Scorecard once and reviewing it annually. Strategy evolves; measures must evolve with it. Monthly scorecard reviews with quarterly revisions to objectives and measures keep the framework alive. A stale scorecard is worse than no scorecard -- it creates a false sense of measurement discipline. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establish measurement discipline | Keep it simple: 2-3 metrics per perspective, reviewed weekly | +| Growth | Align scaling with strategy | Use the Strategy Map to ensure that growth investments connect to all four perspectives | +| Scale | Drive strategy across business units | Deploy cascading scorecards: corporate scorecard decomposes into team-level scorecards with aligned objectives | + +At early traction, the Balanced Scorecard's greatest value is forcing founders to measure beyond revenue. The discipline of identifying one customer metric, one process metric, and one learning metric -- and reviewing them alongside financials -- prevents the common failure of growing revenue while the organisation deteriorates underneath. + +At scale, the framework's power multiplies through cascading. Each team builds its own scorecard aligned to the corporate strategy. Engineering's scorecard emphasises Internal Process and Learning & Growth. Sales emphasises Customer and Financial. The Strategy Map ensures these local scorecards serve the same strategic logic, preventing departmental silos from optimising against each other. + +--- + +## Output Template + +**Target Audience: Board of Directors** + +```markdown +# Balanced Scorecard Review: [Company Name] +## Period: [Quarter/Year] + +### Strategy Map Summary +[One paragraph describing the strategic hypothesis: our investments in X drive process improvements in Y, which deliver customer value Z, resulting in financial outcome W] + +### Scorecard + +#### Financial Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Customer Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Internal Process Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Learning & Growth Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +### Causal Chain Health Check +- Learning & Growth --> Internal Process: [Healthy/Warning/Critical] -- [Brief explanation] +- Internal Process --> Customer: [Healthy/Warning/Critical] -- [Brief explanation] +- Customer --> Financial: [Healthy/Warning/Critical] -- [Brief explanation] + +### Key Actions for Next Period +1. [Action] -- Perspective: [Which] -- Owner: [Name] +2. [Action] -- Perspective: [Which] -- Owner: [Name] +3. [Action] -- Perspective: [Which] -- Owner: [Name] +``` + +--- + +## Related Skills + +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- Strategic options generated by SWOT/TOWS become the objectives and initiatives within the Balanced Scorecard's four perspectives. +- **[Systems Thinking](systems-thinking.md)** -- The Balanced Scorecard's causal chain is itself a simplified systems model; Systems Thinking adds sophistication to understanding feedback loops between the four perspectives. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Process improvement frameworks that drive performance in the Internal Process perspective, providing the operational methodology the scorecard measures. +- **[Net Promoter Score](net-promoter-score.md)** -- A specific customer metric that frequently serves as the primary measure in the Customer perspective of the Balanced Scorecard. +- **[SMART Goals](smart-goals.md)** -- The scorecard's objectives, measures, and targets map directly to SMART criteria, ensuring each perspective has specific and measurable commitments. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- The Strategy Map that connects the four perspectives is a core tool for translating strategic intent into aligned organizational action. diff --git a/plugins/foreman/content/skills/frameworks/belbin-team-roles.md b/plugins/foreman/content/skills/frameworks/belbin-team-roles.md new file mode 100644 index 0000000..26f6a4a --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/belbin-team-roles.md @@ -0,0 +1,196 @@ +--- +name: "belbin-team-roles" +description: "Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing founding team balance, resolving execution problems caused by missing behavioral profiles, or assessing board composition." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - team-composition + - hiring + - roles + - collaboration + - team-building +related_skills: + - tuckman-team-stages + - hackman-enabling-conditions + - lewin-leadership-styles + - situational-leadership +author: "Fatih Guner" +--- + +# Belbin Team Roles + +In 2004, the United States assembled a basketball team for the Athens Olympics that included LeBron James, Tim Duncan, Allen Iverson, and Carmelo Anthony -- arguable the most talented collection of individual players ever put on a court together. They lost three games and settled for bronze. Eight years later, a Spanish national team with no single player approaching that caliber won silver and pushed the Americans to the limit. The pattern repeats across every team sport, every corporate acquisition of "star" talent, and every startup that hires exclusively from elite pedigrees: assembling the best individuals does not produce the best team. + +Meredith Belbin spent nine years at Henley Management College studying why some teams of brilliant people underperformed while other teams of average individuals consistently excelled. His research, published in *Management Teams: Why They Succeed or Fail* (1981), produced a taxonomy of nine team roles -- behavioral patterns that individuals adopt in group settings -- and a principle that has survived four decades of scrutiny: balanced teams outperform unbalanced teams, regardless of the individual talent level within them. + +--- + +## The Framework + +Belbin's nine roles cluster into three categories: Thinking roles, Action roles, and People roles. Each role contributes a specific strength and carries an "allowable weakness" -- a predictable downside that is the shadow of the strength. Effective teams do not eliminate weaknesses; they ensure that every weakness is compensated by another role's strength. + +### Thinking Roles + +**Plant (PL)** +- **Contribution:** Creative, imaginative, unorthodox. Generates novel ideas and solves difficult problems. +- **Allowable weakness:** Ignores practical details. May be too absorbed in ideas to communicate effectively. +- **Startup translation:** The visionary co-founder who sees possibilities no one else does -- and forgets to check whether the technology exists to build them. + +**Monitor Evaluator (ME)** +- **Contribution:** Sober, strategic, discerning. Sees all options and judges accurately. +- **Allowable weakness:** Can be perceived as overly critical, dry, or uninspiring. Rarely generates enthusiasm. +- **Startup translation:** The co-founder who pokes holes in every plan -- annoyingly, they are usually right. + +**Specialist (SP)** +- **Contribution:** Single-minded, self-starting, dedicated. Provides knowledge and skills in rare supply. +- **Allowable weakness:** Contributes only on a narrow front. Dwells on technicalities and misses the big picture. +- **Startup translation:** The domain expert whose deep knowledge is irreplaceable but whose interests are narrow. + +### Action Roles + +**Shaper (SH)** +- **Contribution:** Challenging, dynamic, thrives on pressure. Drives the team forward and overcomes obstacles through sheer force of will. +- **Allowable weakness:** Can be provocative, abrasive, and hurt people's feelings. Prone to impatience and frustration. +- **Startup translation:** The hard-charging co-founder who makes things happen -- and burns through relationships doing it. + +**Implementer (IMP)** +- **Contribution:** Disciplined, reliable, conservative, efficient. Turns ideas into practical actions and working plans. +- **Allowable weakness:** Somewhat inflexible. Slow to respond to new possibilities or sudden pivots. +- **Startup translation:** The operations person who actually ships what the visionaries dream up. + +**Completer Finisher (CF)** +- **Contribution:** Painstaking, conscientious, anxious. Searches out errors and omissions. Delivers on time. +- **Allowable weakness:** Inclined to worry excessively. Reluctant to delegate. Can obsess over details. +- **Startup translation:** The quality gatekeeper who catches the bugs everyone else missed -- and holds up the release doing it. + +### People Roles + +**Coordinator (CO)** +- **Contribution:** Mature, confident, identifies talent. Clarifies goals, delegates effectively, promotes decision-making. +- **Allowable weakness:** Can be perceived as manipulative. May delegate too much personal work. +- **Startup translation:** The CEO who may not be the smartest person in the room but ensures the smartest people work together. + +**Teamworker (TW)** +- **Contribution:** Cooperative, mild, perceptive, diplomatic. Listens, builds, averts friction, calms the waters. +- **Allowable weakness:** Indecisive in crunch situations. Avoids confrontation even when confrontation is necessary. +- **Startup translation:** The cultural glue who keeps the team from imploding during the inevitable founder conflicts. + +**Resource Investigator (RI)** +- **Contribution:** Extrovert, enthusiastic, communicative. Explores opportunities and develops external contacts. +- **Allowable weakness:** Overly optimistic. Loses interest after the initial enthusiasm fades. +- **Startup translation:** The business development natural who opens every door -- and follows through on about half. + +### Role Balance Diagnostics + +The critical insight is not that every team needs all nine roles filled by nine different people. Most startup teams are small enough that individuals must cover multiple roles. The diagnostic questions are: + +1. **Which roles are missing entirely?** A team of three Plants and two Shapers will generate brilliant ideas and fight passionately about them -- and ship nothing. +2. **Which roles are over-represented?** Too many Coordinators and nobody does the work. Too many Completer Finishers and the team never ships because nothing is perfect enough. +3. **Are the allowable weaknesses being compensated?** A Plant's impracticality is harmless when paired with an Implementer. Without that pairing, ideas die in abstraction. + +--- + +## Prompts + +**Prompt 1 -- Team Role Audit:** +> Analyze my team's Belbin role composition. Here are my team members and their behavioral tendencies: [describe each person's strengths, weaknesses, how they contribute in meetings, what frustrates them, what energizes them]. Map each person to their primary and secondary Belbin roles. Identify which roles are missing, which are duplicated, and what specific behavioral gaps this creates. Recommend how to address the imbalance -- through hiring, role adjustment, or conscious behavior adaptation. + +**Prompt 2 -- Hiring for Role Balance:** +> I'm hiring for [role title] on my [size] person team. Using Belbin's framework, my current team's role composition is approximately: [list roles you think each person fills]. What Belbin roles should I prioritize in this hire to improve team balance? What behavioral interview questions would help me identify candidates who naturally fill the missing roles? + +**Prompt 3 -- Conflict Diagnosis Through Role Tension:** +> My team is experiencing recurring conflict between [describe the people and the nature of the conflict -- e.g., "our CTO and Head of Product constantly clash on priorities" or "two team members keep undermining each other's proposals"]. Using Belbin's framework, diagnose whether this conflict stems from role overlap (two Shapers competing for dominance), role gaps (no Teamworker to mediate), or miscast roles (someone forced into a role that contradicts their natural tendencies). Recommend structural changes to resolve the friction. + +**Prompt 4 -- Founding Team Composition Assessment:** +> We're a founding team of [number] people starting a [type of business]. Here's what each of us brings: [describe each founder]. Using Belbin's team roles, assess whether our founding team has the role diversity to succeed. What are our critical vulnerabilities? Should our first hire specifically target a missing Belbin role, and if so, which one? + +--- + +## Use Cases + +**Three-Founder Technical Startup Missing People Roles** + +A validation-stage AI startup has three co-founders: a research scientist (Plant/Specialist), a systems architect (Implementer/Monitor Evaluator), and a machine learning engineer (Specialist/Completer Finisher). The team excels at building technology. They struggle with everything else. Investor meetings fall flat -- no one is a natural Resource Investigator or Coordinator. Internal disagreements fester -- no Teamworker smooths tensions. Product decisions stall because all three default to analysis (Monitor Evaluator) rather than action (Shaper). The Belbin diagnosis reveals a team with extraordinary Thinking and Action depth but zero People role coverage. The first hire should not be another engineer; it should be a commercially oriented co-founder or early employee who brings Coordinator, Resource Investigator, and Shaper energy. + +**Growth-Stage Company with Persistent Execution Gaps** + +A 40-person SaaS company generates excellent ideas (multiple Plants), has strong external networks (Resource Investigators in business development), and maintains a positive culture (Teamworkers). Yet they consistently miss deadlines, ship buggy releases, and fail to complete strategic initiatives. The Belbin analysis reveals a severe deficit in Implementers and Completer Finishers. The culture celebrates ideation and relationships while undervaluing the disciplined, unglamorous work of execution and quality assurance. The intervention involves both hiring (specifically targeting Implementer and Completer Finisher profiles) and cultural recalibration (elevating the status of reliable execution to match that of creative innovation). + +**Board Composition Analysis** + +A scale-stage company's board consists entirely of former CEOs and venture capitalists -- a concentration of Coordinators, Shapers, and Resource Investigators. Board meetings are energetic, directive, and fast-moving, but they consistently miss risks that a Monitor Evaluator would catch and operational details that an Implementer or Completer Finisher would flag. Applying Belbin to board composition reveals the structural blind spot. Adding an independent director with strong ME tendencies -- perhaps a former CFO or risk officer -- rebalances the board's collective intelligence. + +--- + +## Anti-Patterns + +- **Hiring in Your Own Image.** Founders unconsciously seek candidates who think and behave like themselves. A Shaper founder hires other Shapers. A Plant founder hires other Plants. The result is a team that is strong in one dimension and catastrophically weak in others. Belbin's framework is an explicit corrective to this instinct. + +- **Treating Roles as Fixed Labels.** Using Belbin to permanently categorize people rather than understanding roles as situational tendencies. Individuals have primary and secondary roles, and they may shift emphasis depending on the team's needs. Labeling someone as "just a Teamworker" limits both the individual and the team. + +- **Pathologizing Allowable Weaknesses.** Performance-managing a Plant for being impractical or a Completer Finisher for being anxious about quality. These are the predictable shadow sides of essential strengths. The framework explicitly calls them "allowable" -- the cost of a capability the team needs. Address the weakness when it becomes disruptive, but recognize that eliminating it may also eliminate the strength. + +- **Ignoring Role Conflicts in Small Teams.** Assuming that a small team does not need role diversity because "everyone does everything." The smaller the team, the more consequential each role gap becomes. A five-person team missing an Implementer feels the absence in every sprint. + +- **Using Belbin to Justify Exclusion.** Weaponizing the framework to argue that certain people "don't fit" the team composition. Belbin describes behavioral contributions, not human worth. The framework is a tool for understanding and optimizing, not for gatekeeping. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founding team balance | The smallest teams have the most consequential role gaps; founders must honestly assess their combined role coverage and hire accordingly | +| Early Traction | First hires as role fillers | Each new hire should be evaluated partly for the Belbin roles they bring; technical skill is necessary but insufficient | +| Growth | Team-level composition across departments | Role balance matters within each team and across the leadership group; department heads need different role combinations than execution teams | +| Scale | Organizational role diversity | At scale, Belbin applies to the composition of leadership teams, project teams, and boards; the framework scales from five-person startups to thousand-person organizations | + +--- + +## Output Template + +```markdown +# Belbin Team Role Audit: [Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Purpose of Audit:** [Hiring decision / Conflict resolution / Team optimization] + +## Role Map + +| Team Member | Primary Role | Secondary Role | Observed Strengths | Allowable Weakness | +|-------------|-------------|---------------|-------------------|-------------------| +| [Name] | [Role] | [Role] | [Strengths] | [Weakness] | + +## Role Distribution Summary + +| Category | Roles Present | Roles Missing | Impact of Gap | +|----------|--------------|--------------|---------------| +| Thinking | [PL, ME, SP] | [Missing] | [Impact] | +| Action | [SH, IMP, CF] | [Missing] | [Impact] | +| People | [CO, TW, RI] | [Missing] | [Impact] | + +## Critical Gaps and Recommendations +1. **Missing [Role]:** [Impact on team] -> [Recommendation: hire, develop, or reassign] +2. **Over-represented [Role]:** [Impact on team] -> [Recommendation] + +## Hiring Priority +- **Next hire should bring:** [Primary Belbin role] + [Secondary role] +- **Interview signals to look for:** [Behavioral indicators] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Role conflicts surface most intensely during Tuckman's Storming stage; understanding Belbin roles helps navigate role negotiation during that critical phase. +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Hackman's "right people" condition maps directly to Belbin's principle of role-balanced composition, providing the structural imperative for why role diversity matters. +- **[Situational Leadership](situational-leadership.md)** -- Different Belbin roles require different leadership approaches; a Plant needs more autonomy while an Implementer benefits from clearer direction. +- **[Myers-Briggs Type Indicator](myers-briggs-type-indicator.md)** -- MBTI explains underlying personality preferences while Belbin describes the behavioural contributions those preferences produce in team settings. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- Provides the leadership practices for building the collaborative environment in which Belbin's diverse roles can contribute effectively. diff --git a/plugins/foreman/content/skills/frameworks/black-swans.md b/plugins/foreman/content/skills/frameworks/black-swans.md new file mode 100644 index 0000000..be75f5f --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/black-swans.md @@ -0,0 +1,172 @@ +--- +name: "black-swans" +description: "Applies Taleb's Black Swan theory to assess and mitigate exposure + to rare, high-impact unpredictable events. Distinguishes between Mediocristan + and Extremistan domains, designs barbell strategies, builds antifragility, and + audits business vulnerabilities including supply chain concentration, customer + dependency, and regulatory risk. Use when stress-testing a business model, + evaluating tail risks, designing resilience architecture, or building robust + strategies that survive shocks rather than attempting to predict them." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - growth + - scale +tags: + - risk-management + - uncertainty + - resilience + - probability + - tail-risk +related_skills: + - scenario-planning + - porters-five-forces + - business-model-canvas +author: "Fatih Guner" +--- + +# Black Swan Theory + +On September 15, 2008, Lehman Brothers filed for the largest bankruptcy in American history. Within weeks, the global financial system stood at the brink of collapse. Virtually no mainstream economist had predicted the crisis. The models were elegant, the data was abundant, and the conclusions were catastrophically wrong. Nassim Nicholas Taleb had a name for this kind of event -- a Black Swan -- and his 2007 book of the same title had warned, with uncomfortable precision, that the financial system was a powder keg. The concept has since become indispensable vocabulary for anyone who takes risk seriously. + +A Black Swan is an event that satisfies three criteria: it is an outlier beyond the realm of regular expectations, it carries extreme impact, and human nature compels us to fabricate explanations for it after the fact, making it seem predictable in retrospect. The theory does not concern itself with predicting these events -- that is the point. It concerns itself with acknowledging their inevitability and structuring decisions accordingly. + +--- + +## The Framework + +Taleb's argument rests on a distinction between two domains of uncertainty, which he labels Mediocristan and Extremistan. + +### Mediocristan vs. Extremistan + +| Domain | Characteristics | Examples | +|--------|----------------|----------| +| **Mediocristan** | Outcomes cluster around the mean; no single observation can dramatically alter the aggregate | Human height, calorie consumption, car accident rates | +| **Extremistan** | A single observation can disproportionately dominate the total; winner-take-all dynamics prevail | Book sales, wealth distribution, startup valuations, pandemic deaths | + +Most business decisions operate in Extremistan, yet most business tools assume Mediocristan. This mismatch is the source of strategic catastrophe. + +### The Three Properties of a Black Swan + +1. **Rarity** -- The event lies outside ordinary experience. No amount of historical data would have led a reasonable observer to anticipate it. +2. **Extreme Impact** -- When it arrives, it reshapes the landscape. Market structures, competitive positions, and entire industries can be created or destroyed. +3. **Retrospective Predictability** -- After the event, analysts construct narratives that make it appear inevitable. This "narrative fallacy" breeds dangerous overconfidence. + +### The Narrative Fallacy and Confirmation Bias + +Humans are pattern-seeking creatures. Taleb argues that we systematically overfit stories to data, mistaking correlation for causation and randomness for signal. Entrepreneurs are especially vulnerable: the hero narratives of startup culture encourage the belief that outcomes are earned rather than partly determined by chance. Acknowledging the role of luck is not defeatism -- it is the foundation of robust strategy. + +### Building Robustness (and Antifragility) + +Taleb's prescription is not to predict Black Swans but to build systems that survive them -- or, better still, benefit from them: + +- **Barbell Strategy**: Concentrate resources in extremely safe assets on one end and small, high-upside bets on the other. Avoid the middle, where moderate risk produces moderate returns but maximum vulnerability to Black Swans. +- **Optionality**: Structure decisions so that upside is uncapped while downside is limited. Startups that can pivot cheaply have more optionality than those locked into rigid capital commitments. +- **Redundancy over Efficiency**: Systems optimized purely for efficiency are fragile. Maintaining slack -- cash reserves, diversified suppliers, backup capabilities -- creates resilience. +- **Via Negativa**: Sometimes the most powerful strategy is subtraction. Eliminate exposures to catastrophic risk rather than trying to add predictive capability. + +--- + +## Prompts + +**Prompt 1 -- Black Swan Exposure Audit:** +> Analyze my business for Black Swan vulnerability. My company is [describe company, sector, stage, key dependencies]. Identify our top 5 exposures to rare, high-impact events -- consider supply chain, technology shifts, regulatory changes, customer concentration, and financial structure. For each exposure, rate the potential impact (existential / severe / moderate) and our current resilience (fragile / robust / antifragile). Present results in a table. + +**Prompt 2 -- Barbell Strategy Design:** +> Help me design a barbell strategy for [company/product/investment portfolio]. On the safe end, what should I protect absolutely? On the speculative end, what small bets with asymmetric upside should I place? What middle-ground positions should I reduce or eliminate? Structure the output as a three-column framework: Safe (80-90% of resources), Eliminate (the vulnerable middle), and Speculative (10-20% of resources). + +**Prompt 3 -- Post-Mortem Narrative Fallacy Check:** +> I recently experienced [describe event -- a major win, loss, or surprise]. Walk me through a narrative fallacy analysis. What story am I likely telling myself about why this happened? What alternative explanations exist that I might be ignoring? What role did randomness, timing, or external forces play? Help me separate genuine causal factors from retrospective storytelling. + +**Prompt 4 -- Antifragility Assessment:** +> Evaluate whether my business model is fragile, robust, or antifragile using Taleb's framework. My company is [describe]. For each major dimension -- revenue model, team structure, technology stack, customer base, funding structure -- classify the current state and recommend specific changes to move toward antifragility. What stressors could actually make us stronger? + +--- + +## Use Cases + +**SaaS Startup with Single-Cloud Dependency** +A Series A SaaS company runs its entire infrastructure on a single cloud provider with no multi-cloud contingency. The founder applies the Black Swan exposure audit and discovers that a provider outage, pricing change, or policy shift represents an existential risk. The barbell strategy suggests maintaining 85% of workloads on the primary provider (cost-efficient and familiar) while investing 15% of engineering capacity into abstraction layers and secondary provider readiness. The company does not need to run multi-cloud today -- it needs the option to migrate within weeks rather than months. + +**Consumer Hardware Startup Facing Supply Chain Concentration** +A growth-stage hardware company sources a critical component from a single factory in one region. COVID-19 demonstrated that geographic concentration in manufacturing is a textbook Extremistan exposure. Applying Taleb's redundancy principle, the founder diversifies to three suppliers across two continents, accepting a 12% cost increase in exchange for eliminating single-point-of-failure risk. The cost is insurance, not waste. + +**Venture-Backed Marketplace Dependent on Regulatory Goodwill** +A marketplace startup operating in a lightly regulated space applies the exposure audit and recognizes that a single regulatory change could eliminate its business model entirely. Rather than lobbying alone, the founder builds optionality: a secondary revenue model that functions under stricter regulation, and contractual structures that limit liability exposure. The Black Swan lens reframes regulatory risk from "unlikely" to "unknown timing." + +--- + +## Anti-Patterns + +1. **Treating Black Swan theory as a license for paranoia.** The framework is not about fearing everything -- it is about identifying asymmetric exposures and restructuring them. Founders who become paralyzed by tail-risk analysis accomplish nothing. The goal is robustness, not anxiety. + +2. **Claiming every negative surprise is a Black Swan.** A competitor launching a similar product is not a Black Swan -- it is a foreseeable competitive event. Losing a key client is painful but predictable. Reserve the label for events that genuinely lie outside the boundary of reasonable expectation. Overuse dilutes the concept into meaninglessness. + +3. **Confusing fragility reduction with prediction.** The entire point of the framework is that Black Swans cannot be predicted. Founders who respond by hiring consultants to "predict Black Swans" have missed Taleb's argument entirely. The correct response is structural: build systems that survive shocks, not crystal balls that fail to foresee them. + +4. **Ignoring positive Black Swans.** Taleb explicitly discusses positive Black Swans -- unexpected events with massive upside. Entrepreneurs who focus exclusively on downside risk miss the strategic imperative to position for serendipity. Maintaining optionality, staying visible in networks, and placing small speculative bets are strategies that harvest positive Black Swans. + +5. **Over-optimizing for efficiency at the expense of redundancy.** The lean startup ethos prizes efficiency, and rightly so at the earliest stages. But as companies grow, the relentless elimination of slack creates brittleness. The company with zero cash reserves, one key engineer, and a single revenue channel is not lean -- it is fragile. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Identify existential assumptions | At this stage, the entire venture is one large bet. The Black Swan lens helps founders distinguish between assumptions they can test and exposures they cannot control. Focus on limiting downside through cheap experiments rather than heavy capital commitment. | +| Growth | Stress-test dependencies | Revenue is flowing but concentration risk is building. Audit customer concentration, supplier dependencies, and team key-person risk. Begin building redundancy into systems that were expedient during validation. | +| Scale | Institutional resilience architecture | At scale, the stakes are highest and the organization is most prone to complacency. Implement formal risk committees, maintain meaningful cash reserves, and run regular Black Swan tabletop exercises. The goal shifts from personal awareness to organizational culture. | + +--- + +## Output Template + +```markdown +# Black Swan Exposure Assessment + +**Company:** [Name] +**Stage:** [Current stage] +**Date:** [Date] + +## Exposure Map + +| Exposure | Domain (Mediocristan/Extremistan) | Impact if Realized | Current Resilience | Priority | +|----------|----------------------------------|--------------------|--------------------|----------| +| [Exposure 1] | [Domain] | [Existential/Severe/Moderate] | [Fragile/Robust/Antifragile] | [Critical/High/Medium] | +| [Exposure 2] | [Domain] | [Impact] | [Resilience] | [Priority] | +| [Exposure 3] | [Domain] | [Impact] | [Resilience] | [Priority] | + +## Barbell Strategy + +### Safe Side (80-90% of resources) +- [What to protect absolutely] + +### Eliminate (Vulnerable middle) +- [Positions to reduce or exit] + +### Speculative Side (10-20% of resources) +- [Small, high-upside bets] + +## Immediate Actions +1. [Highest-priority resilience action] +2. [Second priority] +3. [Third priority] + +## Review Cadence +- Quarterly exposure reassessment +- Annual barbell rebalancing +``` + +--- + +## Related Skills + +- **[Scenario Planning](scenario-planning.md)** -- Where Black Swan theory addresses the unpredictable, scenario planning builds structured responses to plausible futures; together they cover both the foreseeable and the unforeseeable. +- **[Business Model Canvas](business-model-canvas.md)** -- Mapping the entire business model makes hidden dependencies visible, which is a precondition for effective Black Swan exposure auditing. +- **[Systems Thinking](systems-thinking.md)** -- Reveals the interconnected feedback loops through which a single shock can cascade across an entire business, amplifying Black Swan impact in non-obvious ways. +- **[VUCA Framework](vuca-framework.md)** -- Provides the vocabulary and leadership approach for operating in volatile, uncertain environments where Black Swan events are structurally inevitable. +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- Kahneman's work on cognitive biases explains why humans systematically underestimate tail risks, making Taleb's prescriptions for structural robustness essential. +- **[Decision Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Provides the leadership practices for making sound decisions when a Black Swan event actually materializes and time is compressed. diff --git a/plugins/foreman/content/skills/frameworks/blue-ocean-strategy.md b/plugins/foreman/content/skills/frameworks/blue-ocean-strategy.md new file mode 100644 index 0000000..cd252c1 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/blue-ocean-strategy.md @@ -0,0 +1,218 @@ +--- +name: "blue-ocean-strategy" +description: "Applies Kim and Mauborgne's Blue Ocean Strategy to create uncontested market space through value innovation. Uses the Strategy Canvas to map competitive factors, the ERRC Grid to Eliminate-Reduce-Raise-Create value elements, and the Three Tiers of Noncustomers to identify untapped demand. Use when entering saturated markets, escaping price-based competition, redesigning a value proposition, identifying noncustomer segments, or evaluating whether a new venture creates a genuinely new market category." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth +tags: + - market-creation + - competitive-strategy + - value-innovation + - differentiation + - strategic-positioning +related_skills: + - porters-five-forces + - art-of-war + - business-model-canvas + - disruptive-innovation +author: "Fatih Guner" +--- + +# Blue Ocean Strategy + +Picture the ocean. In red waters, sharks circle. The water is thick with blood -- the blood of competitors slashing prices, matching features, fighting over the same customers in the same market with the same value proposition. Margins shrink. Growth stalls. Strategy degenerates into a war of attrition. Now picture open blue water: vast, calm, and empty. No competitors. No blood. A market space so new that the rules have not yet been written. W. Chan Kim and Renee Mauborgne, professors at INSEAD, published *Blue Ocean Strategy* in 2005 to formalize this distinction and, more importantly, to provide a systematic method for moving from red to blue. The book has sold over 4 million copies and been translated into 46 languages -- evidence that the desire to escape competitive bloodbaths is, itself, a universal market need. + +--- + +## The Framework + +### Red Ocean vs. Blue Ocean + +| Dimension | Red Ocean | Blue Ocean | +|-----------|-----------|------------| +| Market space | Compete in existing markets | Create uncontested market space | +| Competition | Beat the competition | Make competition irrelevant | +| Demand | Exploit existing demand | Create and capture new demand | +| Value/Cost | Choose between differentiation and low cost | Pursue differentiation AND low cost simultaneously | +| Strategy focus | Alignment of activities with strategic choice | Alignment of activities with pursuit of differentiation and low cost | + +The core insight: conventional strategy (Porter's framework, for instance) assumes a fixed market structure and asks how to position within it. Blue Ocean Strategy challenges the assumption. Markets are not fixed; they can be created. The most profitable strategic move is not to compete better but to compete differently -- or, ideally, to create a space where competition is temporarily irrelevant. + +### Value Innovation + +Value innovation is the cornerstone concept. It breaks the trade-off between differentiation and low cost by simultaneously: + +- **Eliminating** factors the industry takes for granted but that customers do not value +- **Reducing** factors well below the industry standard +- **Raising** factors well above the industry standard +- **Creating** factors the industry has never offered + +This is not incremental improvement. It is a fundamental reconfiguration of the value proposition. + +### The Four Actions Framework (ERRC Grid) + +The ERRC Grid operationalizes value innovation: + +``` +┌─────────────────────────┬─────────────────────────┐ +│ ELIMINATE │ RAISE │ +│ │ │ +│ Which factors that the │ Which factors should be │ +│ industry takes for │ raised well above the │ +│ granted should be │ industry standard? │ +│ eliminated? │ │ +├─────────────────────────┼─────────────────────────┤ +│ REDUCE │ CREATE │ +│ │ │ +│ Which factors should be │ Which factors should be │ +│ reduced well below the │ created that the │ +│ industry standard? │ industry has never │ +│ │ offered? │ +└─────────────────────────┴─────────────────────────┘ +``` + +**Cirque du Soleil** is Kim and Mauborgne's canonical example: +- **Eliminated**: Animal acts, star performers, aisle concession sales, multiple show arenas +- **Reduced**: Fun and humor, thrill and danger +- **Raised**: Unique venue, artistic music and dance +- **Created**: Theme, refined viewing environment, multiple productions, artistic richness + +The result: Cirque captured circus audiences AND theater audiences while operating at lower cost than traditional circuses (no animals, no stars) and higher prices than most theater (unique experience). + +### The Strategy Canvas + +The Strategy Canvas is a diagnostic and action tool. It plots the current competitive landscape on a single chart: + +- The horizontal axis lists the key factors of competition in the industry +- The vertical axis captures the offering level for each factor (low to high) +- Each competitor is plotted as a value curve connecting their offering levels + +The strategic insight emerges when you overlay your proposed blue ocean value curve against the existing curves. A genuinely innovative strategy will have a fundamentally different shape -- not just higher or lower on the same factors, but elevated on some, reduced on others, and introducing entirely new factors. + +### The Three Tiers of Noncustomers + +Blue Oceans are created by converting noncustomers into customers. Kim and Mauborgne identify three tiers: + +1. **Soon-to-be noncustomers**: People on the edge of the existing market, minimally using current offerings and ready to leave +2. **Refusing noncustomers**: People who have consciously rejected the industry's offerings as irrelevant or unaffordable +3. **Unexplored noncustomers**: People in distant markets who have never considered the industry's offerings as an option + +Each tier represents increasingly large -- and increasingly overlooked -- pools of demand. + +--- + +## Prompts + +**Prompt 1 -- Strategy Canvas Mapping:** +> Map the strategy canvas for my industry. I compete in [describe industry/market]. The key players are [list 3-5 competitors]. Help me identify the 6-10 factors that the industry currently competes on (e.g., price, features, service quality, brand, convenience, customization). Rate each competitor (including my company) on each factor (Low/Medium/High). Then visualize the value curves and identify where all competitors converge (red ocean indicators) and where differentiation opportunities exist. + +**Prompt 2 -- ERRC Grid Workshop:** +> Help me complete the ERRC (Eliminate-Reduce-Raise-Create) Grid for my business. My company is [describe: product, market, current positioning]. Based on the strategy canvas of my industry, identify: (1) Which factors can we eliminate without losing core value? (2) Which factors can we reduce below industry standard to cut costs? (3) Which factors should we raise above the standard to differentiate? (4) What entirely new factors could we create? For each recommendation, explain the rationale and estimate the impact on both cost structure and buyer value. + +**Prompt 3 -- Noncustomer Analysis:** +> Analyze the three tiers of noncustomers for my market. My current customer base is [describe]. Help me identify: Tier 1 (soon-to-be noncustomers who are barely using our type of product -- why are they dissatisfied?), Tier 2 (refusing noncustomers who have consciously rejected our category -- what are their objections?), Tier 3 (unexplored noncustomers who never considered our category -- what would need to change for them to engage?). For each tier, estimate the potential market size and recommend specific approaches to convert them. + +**Prompt 4 -- Blue Ocean Feasibility Test:** +> Evaluate my blue ocean idea against Kim and Mauborgne's three criteria for a viable blue ocean strategy. My idea is [describe the value innovation concept]. Test it against: (1) Utility -- does it offer exceptional buyer utility? (2) Price -- is the price accessible to the mass of target buyers? (3) Cost -- can we achieve the target cost and still make a profit? (4) Adoption -- what are the adoption hurdles and how do we address them? Identify the weakest dimension and recommend how to strengthen it. + +--- + +## Use Cases + +**Idea-Stage Founder Designing a New Fitness Product** +A founder observes that the fitness industry competes heavily on equipment quality, trainer credentials, facility ambiance, and class variety -- the standard red ocean factors. Applying the ERRC Grid, she eliminates expensive facilities (shifting to a mobile app), reduces trainer credentials requirements (using AI-driven personalization instead), raises convenience to the maximum (workouts available anytime, anywhere, in any duration), and creates adaptive difficulty that adjusts in real time. The result is not a cheaper gym or a better gym but a fundamentally different value curve that attracts Tier 2 noncustomers -- people who found gyms intimidating or inconvenient. + +**Early-Traction B2B SaaS Redefining Its Category** +A project management tool enters a market dominated by Asana, Monday, and Jira. The strategy canvas reveals that all incumbents compete on feature breadth, integrations, and customization -- producing convergent value curves. The startup eliminates advanced customization (the 90% of features that 90% of users never touch), reduces the learning curve from days to minutes, raises real-time collaboration to a level no competitor matches, and creates an AI-powered "project health score" that no one offers. The blue ocean is not project management; it is "effortless project visibility" -- a different category serving the same buyers with a different value proposition. + +**Growth-Stage Company Expanding Through Noncustomer Conversion** +A $20M ARR legal tech company serving large law firms uses the three-tier noncustomer framework to identify expansion opportunities. Tier 1: mid-size firms using the product minimally because it requires dedicated IT support. Tier 2: solo practitioners who rejected the category because pricing assumed firm-level budgets. Tier 3: in-house corporate legal teams who never considered external legal tech tools. Each tier implies a different product and pricing strategy. The company launches a self-service tier (Tier 1), a solo plan at $49/month (Tier 2), and an enterprise-grade integration with corporate systems (Tier 3) -- tripling its addressable market without competing more intensely in its existing segment. + +--- + +## Anti-Patterns + +1. **Confusing differentiation with blue ocean creation.** A better mousetrap is differentiation. A blue ocean requires a fundamentally different value curve -- eliminating and reducing factors, not just adding new ones. If the competitive factors remain the same and you are simply "better," you are still in the red ocean with a shinier boat. + +2. **Pursuing blue oceans without verifying buyer utility.** Not every uncontested space is uncontested for good reason, but some are. The absence of competitors may indicate an unserved need OR a need that does not exist. The ERRC Grid must be validated with actual customers, not just logical deduction. + +3. **Neglecting execution barriers.** The strategy canvas may reveal a beautiful blue ocean opportunity, but if the company lacks the capabilities, resources, or organizational alignment to execute the required value curve, the strategy remains theoretical. Blue Ocean Strategy without operational reality is a PowerPoint exercise. + +4. **Ignoring imitation speed.** Blue oceans do not stay blue forever. Competitors observe and follow. The question is not only "can we create a blue ocean?" but "how long before it turns red, and what structural advantages will we have built by then?" Network effects, proprietary data, brand, and switching costs are the barriers that extend blue ocean duration. + +5. **Applying the framework to sustaining innovation.** Blue Ocean Strategy is designed for market creation, not incremental improvement. Using the ERRC Grid to optimize an existing product within an existing market produces interesting tactical insights but misses the framework's fundamental purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Blue ocean identification | The ideal moment to apply the framework -- before competitive commitments have been made. Use the strategy canvas to evaluate whether a proposed venture enters a red ocean or creates a blue one. If the value curve looks like everyone else's, reconsider before building. | +| Validation | Noncustomer testing | Validate the blue ocean hypothesis with actual noncustomers, not just existing market participants. If Tier 2 and Tier 3 noncustomers respond to the value proposition, the blue ocean is real. If only existing customers respond, you have built differentiation, not a new market. | +| Early Traction | Value curve sharpening | With market feedback, refine the ERRC Grid. Some factors initially eliminated may need partial restoration. Some created factors may need adjustment. The value curve is a hypothesis that improves with data. | +| Growth | Blue ocean defense | As the market space becomes visible to competitors, invest in structural barriers: network effects, proprietary data, brand identity, ecosystem lock-in. The strategic question shifts from "how do we create the blue ocean?" to "how do we keep it blue?" | + +--- + +## Output Template + +```markdown +# Blue Ocean Strategy Analysis + +**Company:** [Name] +**Industry:** [Current industry/market] +**Date:** [Date] + +## Strategy Canvas + +| Competitive Factor | Industry Avg | Competitor A | Competitor B | Our Current | Our Blue Ocean | +|-------------------|-------------|-------------|-------------|-------------|----------------| +| [Factor 1] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | +| [Factor 2] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | +| [New Factor] | N/A | N/A | N/A | N/A | [L/M/H] | + +## ERRC Grid + +| Eliminate | Reduce | +|-----------|--------| +| [Factor] -- [Rationale] | [Factor] -- [Rationale] | + +| Raise | Create | +|-------|--------| +| [Factor] -- [Rationale] | [Factor] -- [Rationale] | + +## Noncustomer Tiers + +| Tier | Description | Estimated Size | Conversion Strategy | +|------|-------------|---------------|-------------------| +| Tier 1 (Edge) | [Who they are, why they are leaving] | [Size] | [Approach] | +| Tier 2 (Refusing) | [Who they are, why they reject] | [Size] | [Approach] | +| Tier 3 (Unexplored) | [Who they are, why they never considered] | [Size] | [Approach] | + +## Feasibility Assessment +- **Buyer Utility:** [Pass/Fail -- explanation] +- **Price Accessibility:** [Pass/Fail -- explanation] +- **Cost Structure:** [Pass/Fail -- explanation] +- **Adoption Hurdles:** [List and mitigation] + +## Blue Ocean Durability +**Expected time before imitation:** [Estimate] +**Structural barriers to build:** [List] +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](porters-five-forces.md)** -- Five Forces diagnoses the competitive structure of the red ocean, while Blue Ocean Strategy charts the escape route to uncontested market space. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Both frameworks identify opportunities in spaces incumbents overlook, but disruption focuses on low-end or new-market footholds while Blue Ocean pursues value innovation across the entire offering. +- **[Business Model Canvas](business-model-canvas.md)** -- Once a blue ocean opportunity is identified, the Canvas structures the complete operational design needed to deliver the new value proposition. +- **[Art of War](art-of-war.md)** -- Sun Tzu's "win without fighting" principle is the ancient philosophical precursor to blue ocean thinking, providing strategic mindset where Kim and Mauborgne provide analytical tools. +- **[Doblin's Ten Types of Innovation](doblin-ten-types.md)** -- Blue Ocean identifies the need for a different value curve; Doblin's ten types provide the specific innovation dimensions across which to build that differentiation. +- **[Four Ps of Marketing](four-ps-marketing.md)** -- A blue ocean strategy requires realignment of the entire marketing mix, as the new value curve reshapes product, price, place, and promotion simultaneously. diff --git a/plugins/foreman/content/skills/frameworks/business-model-canvas.md b/plugins/foreman/content/skills/frameworks/business-model-canvas.md new file mode 100644 index 0000000..5e8e63f --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/business-model-canvas.md @@ -0,0 +1,242 @@ +--- +name: "business-model-canvas" +description: "Structures and evaluates business models using Osterwalder's + nine-block Business Model Canvas: Customer Segments, Value Propositions, + Channels, Customer Relationships, Revenue Streams, Key Resources, Key + Activities, Key Partnerships, and Cost Structure. Use when designing a new + venture, comparing business model alternatives, stress-testing assumptions, + planning pivots, exploring revenue model options, or identifying hidden + dependencies between business model components." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - business-model + - value-proposition + - startup-design + - strategy + - lean-methodology +related_skills: + - blue-ocean-strategy + - porters-five-forces +author: "Fatih Guner" +related_content: + - kind: template + ref: unit-economics-snapshot +--- + +# Business Model Canvas + +Business plans fail. Not occasionally -- systematically. Research from the Kauffman Foundation and others consistently demonstrates that the traditional 40-page business plan, once the mandatory admission ticket for venture funding, bears almost no correlation with startup success. The plans take months to write, become obsolete within weeks, and optimize for the wrong outcome: a polished document rather than a validated business. Alexander Osterwalder and Yves Pigneur, in *Business Model Generation* (2010), proposed a replacement: a single-page visual map that captures the nine essential building blocks of any business model. The Business Model Canvas (BMC) does not ask "how do we plan the business?" -- it asks "how does this business actually create, deliver, and capture value?" The shift from narrative to architecture, from plan to model, has reshaped how entrepreneurs think about building companies. + +--- + +## The Framework + +### The Nine Building Blocks + +The Canvas divides any business model into nine interdependent blocks, arranged spatially to reveal relationships: + +``` +┌──────────────┬───────────────┬───────────────┬───────────────┬──────────────┐ +│ │ │ │ │ │ +│ KEY │ KEY │ VALUE │ CUSTOMER │ CUSTOMER │ +│ PARTNERS │ ACTIVITIES │ PROPOSITIONS│ RELATIONSHIPS│ SEGMENTS │ +│ │ │ │ │ │ +│ Who are our │ What key │ What value │ What type of │ For whom │ +│ key │ activities │ do we │ relationship │ are we │ +│ partners │ does our │ deliver? │ does each │ creating │ +│ and │ value prop │ │ segment │ value? │ +│ suppliers? │ require? │ │ expect? │ │ +│ ├───────────────┤ ├───────────────┤ │ +│ │ │ │ │ │ +│ │ KEY │ │ CHANNELS │ │ +│ │ RESOURCES │ │ │ │ +│ │ │ │ Through │ │ +│ │ What key │ │ which │ │ +│ │ resources │ │ channels do │ │ +│ │ does our │ │ our segments │ │ +│ │ value prop │ │ want to be │ │ +│ │ require? │ │ reached? │ │ +│ │ │ │ │ │ +├──────────────┴───────────────┴───────┬───────┴───────────────┴──────────────┤ +│ │ │ +│ COST STRUCTURE │ REVENUE STREAMS │ +│ │ │ +│ What are the most important costs │ For what value are customers │ +│ inherent in our business model? │ willing to pay? │ +│ │ │ +└──────────────────────────────────────┴──────────────────────────────────────┘ +``` + +### Block-by-Block Guide + +**1. Customer Segments** -- The distinct groups of people or organizations the business serves. Segments differ when they require distinct value propositions, are reached through different channels, require different types of relationships, yield different profitability profiles, or are willing to pay for different aspects of the offering. The decision of which segments to serve -- and which to ignore -- is the most consequential strategic choice on the canvas. + +**2. Value Propositions** -- The bundle of products and services that create value for a specific customer segment. Value may derive from newness, performance, customization, design, brand/status, price, cost reduction, risk reduction, accessibility, or convenience. The value proposition is the reason a customer chooses one company over another. + +**3. Channels** -- How the company communicates with and reaches its customer segments to deliver value. Channels include direct (sales force, web, stores) and indirect (partner stores, wholesalers). The channel question is not just "how do we reach customers?" but "how do customers want to be reached?" + +**4. Customer Relationships** -- The type of relationship established with each segment: personal assistance, dedicated personal assistance, self-service, automated services, communities, or co-creation. The relationship type affects customer acquisition cost, retention rate, and lifetime value. + +**5. Revenue Streams** -- The cash generated from each customer segment. Revenue model types include asset sales, usage fees, subscription fees, licensing, brokerage fees, and advertising. Two fundamental pricing mechanisms exist: fixed (list prices, feature-dependent, segment-dependent) and dynamic (negotiation, yield management, real-time market pricing). + +**6. Key Resources** -- The most important assets required to make the business model work: physical, intellectual (patents, proprietary knowledge, data), human, or financial. Key resources are those without which the value proposition cannot be delivered. + +**7. Key Activities** -- The most important things the company must do to make the business model work. Categories include production (designing, making, delivering), problem solving (consulting, engineering), and platform/network management (maintaining and developing the platform). + +**8. Key Partnerships** -- The network of suppliers and partners that make the business model work. Partnership motivations include optimization and economy of scale, reduction of risk and uncertainty, and acquisition of particular resources and activities. + +**9. Cost Structure** -- All costs incurred to operate the business model. Two broad classes: cost-driven (minimizing cost wherever possible) and value-driven (focused on value creation with less concern for cost). Key cost characteristics to identify: fixed vs. variable, economies of scale, and economies of scope. + +### The Canvas as a System + +The nine blocks are not independent -- they form a system of interdependencies. The left side of the canvas (partners, activities, resources, costs) represents the infrastructure of value creation. The right side (segments, relationships, channels, revenue) represents value delivery and capture. The value proposition sits at the center, connecting creation to delivery. + +A change in any block ripples across the canvas. Adding a new customer segment may require new channels, different relationships, additional resources, and altered cost structure. This systemic view is the canvas's greatest strength: it makes hidden dependencies visible. + +### Canvas Patterns + +Osterwalder and Pigneur identify recurring business model patterns: + +- **Unbundled**: Separating product innovation, customer relationship management, and infrastructure into distinct models +- **Long Tail**: Selling less of more -- many niche products rather than a few bestsellers +- **Multi-Sided Platform**: Connecting two or more interdependent customer groups (e.g., buyers and sellers) +- **Free/Freemium**: At least one segment receives value for free, subsidized by another segment or revenue stream +- **Open**: Collaborating with external partners to create or capture value + +--- + +## Prompts + +**Prompt 1 -- Complete Canvas Build:** +> Help me build a complete Business Model Canvas for my venture. My concept is [describe your business idea, target market, and core offering]. For each of the nine blocks, provide specific, actionable content -- not generic descriptions. Challenge my assumptions: where am I making implicit choices that should be explicit? Where are there dependencies between blocks that I might be overlooking? Present the completed canvas as a structured document with each block clearly defined. + +**Prompt 2 -- Canvas Comparison (Current vs. Target):** +> I want to compare my current business model with a target business model. Here is my current canvas: [describe or paste current model]. Here is where I want to be in 18 months: [describe target state]. Map both canvases side by side and identify: (1) Which blocks need to change? (2) What is the sequence of changes -- which block moves first? (3) What are the riskiest transitions? (4) What are the dependencies that could block the transition? + +**Prompt 3 -- Canvas Stress Test:** +> Stress-test my Business Model Canvas. My current canvas is: [describe or paste]. For each block, identify the riskiest assumption -- the one that, if wrong, would break the model. Then prioritize these assumptions by impact and uncertainty. Finally, recommend the cheapest experiment I could run to test each of the top 3 riskiest assumptions. + +**Prompt 4 -- Revenue Model Exploration:** +> My value proposition is [describe] serving [customer segment]. Explore alternative revenue models using the Canvas framework. For each model (subscription, usage-based, freemium, transaction fee, licensing, advertising, data monetization), assess: (1) Fit with my value proposition, (2) Customer willingness to pay, (3) Impact on other canvas blocks (channels, relationships, costs), (4) Long-term scalability. Recommend the top 2-3 revenue models with rationale. + +**Prompt 5 -- Partnership and Resource Gap Analysis:** +> Review my Business Model Canvas: [describe]. Identify gaps in key resources and key activities that I cannot fill internally. For each gap, recommend: (1) Build vs. partner vs. acquire, (2) Specific potential partners or providers, (3) Partnership structure (strategic alliance, joint venture, buyer-supplier, co-opetition), (4) Risks of dependency and how to mitigate them. + +--- + +## Use Cases + +**Idea-Stage Founder Testing Three Business Concepts** +A founder with domain expertise in healthcare logistics has three potential business ideas. Rather than writing business plans for each, she builds three canvases in a single afternoon. The canvas exercise reveals that Concept A requires a regulatory resource she does not have and cannot easily acquire. Concept B has strong value proposition-segment fit but no viable revenue stream at the target price point. Concept C has a clear path across all nine blocks, with the key risk concentrated in one testable assumption: whether hospital procurement departments will adopt a self-service purchasing tool. The canvas did not make the decision -- it made the decision visible. + +**Validation-Stage Startup Discovering a Pivot** +A B2C fitness app with 10,000 free users and negligible paid conversion maps its current canvas and discovers that its actual value creation is concentrated in the community features (customer relationships block), not the workout content (value proposition block). The paying users pay for community, not content. The canvas pivot: shift the value proposition from "personalized workouts" to "accountability communities," change the revenue stream from subscription to cohort-based pricing, and redesign channels around referral rather than performance marketing. The canvas reveals that the business model the customers are buying is different from the one the founder is selling. + +**Growth-Stage Platform Company Navigating Multi-Sided Economics** +A marketplace connecting freelance designers with small businesses maps its canvas and discovers an asymmetry: the value proposition for designers (access to clients) is strong, but the value proposition for businesses (access to quality design) is weakening as the platform grows and quality becomes inconsistent. The canvas highlights that the key activity of quality curation -- initially performed manually by the founder -- has not scaled. The solution: invest in the key activity of algorithmic quality matching, add a key resource of portfolio review capability, and create a new revenue stream (premium placement for top-rated designers) that aligns incentives with quality. + +--- + +## Anti-Patterns + +1. **Filling the canvas once and treating it as finished.** The Canvas is a living document that evolves as assumptions are tested and conditions change. A canvas completed at the idea stage should look materially different six months later. If it does not, either the business has stagnated or the canvas is not being used. + +2. **Making the canvas too abstract.** "Our customer segment is SMBs" is not useful. "Our customer segment is marketing directors at B2B SaaS companies with 50-200 employees who currently manage campaigns in spreadsheets" is useful. Specificity in each block is what transforms the canvas from a strategy exercise into an operational guide. + +3. **Ignoring the left side of the canvas.** Entrepreneurs obsess over value propositions, customers, and revenue -- the right side. The left side (resources, activities, partners, costs) is where execution lives. A brilliant right side with an unworkable left side produces a business that cannot be built. + +4. **Assuming one canvas serves all segments.** Different customer segments often require different canvases. A freemium product has one canvas for free users and a different one for paying users. A marketplace has separate canvases for each side. Collapsing distinct models into a single canvas hides the structural differences that matter most. + +5. **Treating the canvas as a replacement for financial modeling.** The canvas reveals the architecture of the business model; it does not quantify it. Revenue streams, cost structure, and unit economics require separate, rigorous financial analysis. The canvas tells you what to model; the financial model tells you whether the numbers work. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Hypothesis generation | Every block is an assumption. The canvas at this stage is a hypothesis document, not a description of reality. The goal is to identify the riskiest assumptions and sequence experiments to test them. Multiple canvases for different concepts enable rapid comparison. | +| Validation | Assumption testing | Systematically validate each block through customer discovery, prototypes, and landing page tests. The canvas evolves as assumptions are confirmed or refuted. Focus on the value proposition and customer segment blocks first -- these determine whether the other seven blocks matter. | +| Early Traction | Model refinement | Product-market fit is emerging. The canvas shifts from hypothesis to documented reality: which segments are actually buying, through which channels, at what price. Gaps between the planned canvas and the actual canvas reveal where the model needs adjustment. | +| Growth | Scaling infrastructure | The left side of the canvas becomes critical. Key resources, activities, and partnerships must scale to support growing demand. Cost structure optimization begins. The canvas helps identify which blocks are scaling smoothly and which are bottlenecks. | +| Scale | Model extension and defense | New customer segments, geographies, or product lines each require canvas extensions or entirely new canvases. The framework helps evaluate whether extensions leverage existing blocks or require building new ones. Defensive canvases map how the current model would respond to competitive or market disruptions. | + +--- + +## Output Template + +```markdown +# Business Model Canvas + +**Venture:** [Name] +**Version:** [v1.0 / v2.0 / etc.] +**Date:** [Date] +**Stage:** [Current stage] + +## Customer Segments +- **Primary:** [Specific description] +- **Secondary:** [Specific description] + +## Value Propositions +- **For [Segment 1]:** [Specific value delivered] +- **For [Segment 2]:** [Specific value delivered] + +## Channels +- **Awareness:** [How customers discover us] +- **Evaluation:** [How customers evaluate our offering] +- **Purchase:** [How customers buy] +- **Delivery:** [How we deliver value] +- **After-sales:** [How we provide post-purchase support] + +## Customer Relationships +- **[Segment 1]:** [Relationship type and description] +- **[Segment 2]:** [Relationship type and description] + +## Revenue Streams +- **[Stream 1]:** [Model type] -- [Pricing mechanism] -- [Expected contribution %] +- **[Stream 2]:** [Model type] -- [Pricing mechanism] -- [Expected contribution %] + +## Key Resources +- **Physical:** [If applicable] +- **Intellectual:** [Patents, data, brand, proprietary knowledge] +- **Human:** [Key roles and expertise] +- **Financial:** [Funding, credit lines] + +## Key Activities +1. [Critical activity for value delivery] +2. [Critical activity for value delivery] +3. [Critical activity for value delivery] + +## Key Partnerships +- **[Partner type]:** [Who and why] +- **[Partner type]:** [Who and why] + +## Cost Structure +- **Fixed costs:** [List major items] +- **Variable costs:** [List major items] +- **Cost model:** [Cost-driven / Value-driven] + +## Riskiest Assumptions +1. [Assumption] -- Block: [Which block] -- Test: [How to validate] +2. [Assumption] -- Block: [Which block] -- Test: [How to validate] +3. [Assumption] -- Block: [Which block] -- Test: [How to validate] +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- The ERRC Grid reshapes the value proposition block; the Canvas maps the complete business model required to deliver the blue ocean strategy. +- **[Porter's Five Forces](porters-five-forces.md)** -- Five Forces reveals the industry structure the business model must navigate; the Canvas designs the model while Five Forces evaluates the competitive terrain it operates in. +- **[Four Ps of Marketing](four-ps-marketing.md)** -- The Canvas's right side (segments, channels, relationships, revenue) expands into the full marketing mix of Product, Price, Place, and Promotion for go-to-market execution. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- PEST identifies macro forces that constrain or enable the Canvas's assumptions, while SWOT reveals which blocks represent genuine competitive advantages. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Christensen's theory explains when a Canvas designed for underserved segments can grow to challenge incumbents whose business models cannot adapt. +- **[Ambidexterity](ambidexterity.md)** -- Exploration units should build separate canvases from the core business, making the two-canvas approach a practical tool for structurally ambidextrous organizations. diff --git a/plugins/foreman/content/skills/frameworks/carnegie-win-friends.md b/plugins/foreman/content/skills/frameworks/carnegie-win-friends.md new file mode 100644 index 0000000..a907cfb --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/carnegie-win-friends.md @@ -0,0 +1,231 @@ +--- +name: "carnegie-win-friends" +description: "Applies Dale Carnegie's interpersonal influence principles for building relationships, earning trust, and leading without authority. Covers techniques for handling people, making others feel valued, winning people to your thinking, and changing behavior without giving offense. Use when building advisory networks, repairing strained stakeholder relationships, improving investor communications, navigating co-founder conflicts, or developing the interpersonal skills that underpin hiring, sales, and fundraising." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - interpersonal-skills + - influence + - leadership + - networking + - communication +related_skills: + - cialdini-influence + - trust-equation + - radical-candor + - win-win-negotiation +author: "Fatih Guner" +--- + +# Carnegie's How to Win Friends and Influence People + +Published in 1936, Dale Carnegie's *How to Win Friends and Influence People* has sold over 30 million copies, been translated into dozens of languages, and remained continuously in print for nearly nine decades. A time-travel thought experiment clarifies why this matters: if you transported Carnegie's principles to a modern tech startup -- replacing "telegrams" with "Slack messages" and "salesmen" with "founders" -- the advice would require almost no adaptation. The principles work because they address something that has not changed in ninety years: human psychology. People still crave recognition. They still resist being told they are wrong. They still respond to genuine interest more readily than to polished pitches. The surface of business transforms every decade; the social operating system of human beings upgrades on evolutionary timescales. Carnegie mapped that operating system with a precision that keeps his Depression-era book selling in the age of AI. + +The question is not whether these principles still apply. The question is why so few founders -- drowning in frameworks for product, growth, and fundraising -- bother to master the foundational skill that underlies all of them: the ability to make other people want to work with you. + +--- + +## The Framework + +Carnegie organises his principles into four groups. Each group targets a different domain of interpersonal effectiveness. Below, the original principles are presented alongside modern entrepreneurial applications. + +### Group 1: Fundamental Techniques in Handling People + +**Principle 1: Never criticise, condemn, or complain.** + +Criticism triggers defensive behaviour, not behavioural change. Carnegie observed that even criminals rationalise their actions; direct criticism rarely produces the response the critic intends. The modern parallel: founders who publicly criticise team members, competitors, or investors create fear-based environments and reputational damage. + +*Modern application:* When an employee makes an error, address the systemic cause rather than assigning blame. "The deployment failed because our testing process has a gap" is actionable. "The deployment failed because you were careless" produces resentment. + +**Principle 2: Give honest, sincere appreciation.** + +Not flattery -- appreciation. The distinction matters. Flattery is generic and self-serving ("you're amazing"). Appreciation is specific and other-oriented ("your analysis of the competitive landscape changed how I think about our positioning"). Sincere appreciation is one of the most powerful and least deployed tools in a founder's repertoire. + +*Modern application:* In every investor update, board meeting, and team standup, name specific contributions and explain their impact. The cost is sixty seconds of preparation. The return is disproportionate loyalty and motivation. + +**Principle 3: Arouse in the other person an eager want.** + +Influence flows not from what *you* want but from connecting your objective to what *they* want. A founder who pitches an investor by explaining why the company needs money will lose to a founder who explains why this investment aligns with the investor's thesis, portfolio strategy, and personal legacy. + +*Modern application:* Before every pitch, negotiation, or hiring conversation, answer one question: what does the other person want, and how does my proposal help them get it? + +### Group 2: Ways to Make People Like You + +**Principle 4: Become genuinely interested in other people.** + +Not feigned interest. Genuine curiosity about another person's world -- their challenges, motivations, and expertise -- creates connection more effectively than any amount of charisma. + +*Modern application:* In customer discovery, the founder who asks questions with authentic curiosity uncovers insights that the founder running a scripted interview misses. Curiosity is both a social skill and a strategic advantage. + +**Principle 5: Smile.** + +Carnegie's simplest principle and the one most often dismissed as trivial. Research in nonverbal communication consistently confirms that facial warmth increases perceived trustworthiness, competence, and approachability. + +*Modern application:* In video calls (now the dominant medium for business communication), facial expression carries disproportionate weight because body language is truncated. A founder whose default expression is tense or neutral on camera is unconsciously communicating stress. + +**Principle 6: Remember that a person's name is, to that person, the sweetest sound in any language.** + +Using someone's name signals that they are significant enough to remember. Forgetting it signals the opposite. In an era of digital networking where founders meet hundreds of people annually, systematic name recall (CRM tools, post-meeting notes) is a competitive advantage. + +**Principle 7: Be a good listener. Encourage others to talk about themselves.** + +Carnegie anticipated by decades what neuroscience later confirmed: talking about oneself activates the brain's reward centres. People experience being listened to as a form of emotional compensation. The founder who listens more than they speak in a first meeting creates a stronger impression than the one who dominates the conversation. + +**Principle 8: Talk in terms of the other person's interests.** + +Research the person. Understand their context. Frame your message in their language, referencing their priorities. This is not manipulation; it is the basic discipline of communication -- translating your meaning into the receiver's frame of reference. + +**Principle 9: Make the other person feel important -- and do it sincerely.** + +Every human being carries a deep need to feel significant. Entrepreneurs who dismiss this as "soft stuff" handicap themselves in hiring, fundraising, partnerships, and sales -- all domains where the other party's felt sense of importance determines the outcome. + +### Group 3: How to Win People to Your Thinking + +**Principle 10: Avoid arguments.** + +You cannot win an argument. If you lose, you lose. If you win, you have made the other person resentful, which is another kind of losing. Carnegie's advice: sidestep the argument entirely. Acknowledge the other person's perspective, find common ground, and redirect the conversation toward shared objectives. + +**Principle 11: Show respect for the other person's opinions. Never say "You're wrong."** + +Direct contradiction triggers ego defence. "I see it differently" preserves the relationship. "You're wrong" destroys it. For founders who prize being right, this principle requires the discipline to separate truth-seeking from ego-gratification. + +**Principle 12: If you are wrong, admit it quickly and emphatically.** + +Rapid, unreserved admission of error disarms critics and builds credibility. The founder who says "I was wrong about our go-to-market strategy, and here's what I've learned" earns more respect than the one who rationalises the failure. + +**Principle 13: Begin in a friendly way.** + +Hostility begets hostility. Warmth begets openness. The first thirty seconds of an interaction set the emotional tone for everything that follows. + +**Principle 14: Get the other person saying "yes" immediately.** + +Start with areas of agreement before approaching areas of disagreement. Each "yes" creates psychological momentum toward further agreement. This is Carnegie's version of Cialdini's commitment-and-consistency principle, articulated decades earlier. + +**Principle 15: Let the other person do a great deal of the talking.** + +People persuade themselves more effectively than you can persuade them. By asking questions and listening, you allow the other person to arrive at your conclusion through their own reasoning. + +**Principle 16: Let the other person feel the idea is theirs.** + +The idea's origin matters less than its implementation. If a team member arrives at a strategy you were going to propose anyway, the fact that they feel ownership of it dramatically increases the probability of successful execution. + +### Group 4: Be a Leader -- How to Change People Without Offending + +**Principle 17: Begin with praise and honest appreciation.** + +Before delivering difficult feedback, establish genuine goodwill. This is not the discredited "feedback sandwich" -- it is a sincere opening that demonstrates the relationship is valued. + +**Principle 18: Call attention to mistakes indirectly.** + +"This report is well-researched. If the executive summary led with the key recommendation, it would be even more impactful." The mistake is addressed; dignity is preserved. + +**Principle 19: Talk about your own mistakes before criticising the other person.** + +Vulnerability reduces defensiveness. "When I was at your stage, I made the same error" creates solidarity rather than hierarchy. + +**Principle 20: Ask questions instead of giving direct orders.** + +"Would it make sense to approach the client this way?" generates more buy-in than "approach the client this way." The outcome is identical; the felt autonomy is not. + +--- + +## Prompts + +**Prompt 1 -- Stakeholder Relationship Audit:** +> Using Carnegie's principles, audit my current relationships with key stakeholders: [list 3-5 key relationships -- investors, cofounders, key hires, major customers]. For each, identify which Carnegie principles I am applying well, which I am neglecting, and what specific actions would strengthen the relationship. Be concrete -- suggest specific things I should say or do in my next interaction with each person. + +**Prompt 2 -- Difficult Relationship Repair:** +> I have a strained relationship with [describe the person and context]. Using Carnegie's principles, design a relationship repair strategy. What went wrong (mapped to which principles were violated)? What specific actions -- across multiple interactions, not a single conversation -- would rebuild trust and goodwill? Provide a 30-day action plan with specific touchpoints. + +**Prompt 3 -- Investor Communication Redesign:** +> Rewrite my investor update email using Carnegie's principles. Current email: [paste or describe]. The email should make each investor feel personally valued, acknowledge their specific contributions and advice, frame challenges in terms of the investor's interests, and close with a specific ask framed as something the investor would want to do. Maintain professionalism while applying Carnegie's interpersonal framework. + +--- + +## Use Cases + +**Idea-Stage Founder Building an Advisory Network** +A first-time founder with no industry connections needs advisors, early customers, and eventually investors. Applying Carnegie's principles systematically: genuine interest (researching each potential advisor's work and asking thoughtful questions), listening (letting advisors talk about their experiences rather than pitching), appreciation (specific thank-you notes referencing exact advice given), and making the other person feel important (publicly crediting advisors when their guidance produces results). Within six months, the founder has assembled an advisory board of four industry veterans who actively introduce them to investors and customers -- not because of the startup's traction, but because the founder made them feel valued. + +**Growth-Stage CEO Managing a Difficult Board Member** +A board member consistently challenges the CEO's strategy in adversarial terms, creating tension that spills into the management team. Applying Carnegie: the CEO stops arguing and starts asking the board member for their perspective before presenting their own. The CEO admits past strategic errors openly, demonstrating vulnerability. The CEO identifies the board member's underlying concern (fiduciary risk, driven by a prior portfolio failure) and proactively addresses it in every board update. Within two quarters, the relationship transforms from adversarial to collaborative -- the board member's scrutiny becomes an asset rather than a threat. + +--- + +## Anti-Patterns + +1. **Performative Warmth.** Applying Carnegie's principles mechanically -- memorising names from a CRM, offering scripted appreciation, displaying calculated interest -- without genuine feeling. People detect inauthenticity with remarkable accuracy. Carnegie's principles require sincere application or they backfire spectacularly. + +2. **Avoiding All Conflict.** Misreading "never criticise" as "never hold people accountable." Carnegie's principle addresses *how* you deliver difficult messages, not whether you deliver them. A founder who cannot confront poor performance because Carnegie said "don't criticise" has misunderstood the framework entirely. The principle is about method, not avoidance. + +3. **Manipulation Through Technique.** Using Carnegie's principles as a tactical toolkit for getting what you want from people, rather than as a genuine philosophy of human relationships. The short-term gains are real; the long-term reputation cost is devastating. In tight-knit entrepreneurial ecosystems, a reputation for manipulative charm is career-ending. + +4. **Cultural Universalism.** Carnegie wrote in and for American culture. Directness, informality, and effusive appreciation land differently in Japan, Germany, or Saudi Arabia. Founders operating internationally must adapt the principles' expression while preserving their underlying intent. + +5. **Neglecting the Power Dimension.** Carnegie's principles assume relatively symmetrical relationships. In situations of significant power asymmetry -- a founder with a dominant investor, an employee with an abusive manager -- "being friendly" and "avoiding arguments" can enable exploitation. The principles require a foundation of mutual respect to function as intended. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Network building | At the idea stage, you have no product, no traction, and no leverage. Interpersonal skill is your primary asset. Carnegie's principles turn cold outreach into warm relationships. | +| Validation | Customer discovery | Genuine curiosity and listening -- Carnegie's core principles -- are identical to the skills required for effective customer interviews. The founder who truly listens discovers what the founder who pitches misses. | +| Early Traction | Hiring and retention | Attracting talent to a small, unproven company requires making candidates feel valued, heard, and important. Carnegie's principles are a hiring advantage when you cannot compete on compensation. | +| Growth | Leadership and delegation | As the founder transitions from doer to leader, Carnegie's principles for changing people's behaviour without offending become critical. Managing through influence rather than authority scales better than micromanagement. | +| Scale | Institutional culture | At scale, Carnegie's principles must be embedded in culture -- training programmes, management practices, communication norms -- rather than depending on the founder's personal application. | + +--- + +## Output Template + +```markdown +# Stakeholder Relationship Strategy: [Your Name / Company] + +## Key Relationships +| Stakeholder | Relationship Quality | Carnegie Principles Applied | Principles Neglected | +|------------|---------------------|---------------------------|---------------------| +| [Name/Role] | Strong / Neutral / Strained | [List] | [List] | + +## Action Plan +### [Stakeholder 1] +- **Next interaction:** [Date/context] +- **Specific actions:** + - [Carnegie principle] → [Concrete action] + - [Carnegie principle] → [Concrete action] +- **Desired outcome:** [What you hope to achieve] + +### [Stakeholder 2] +- **Next interaction:** [Date/context] +- **Specific actions:** + - [Carnegie principle] → [Concrete action] +- **Desired outcome:** [What you hope to achieve] + +## 30-Day Relationship Building Goals +1. [Specific, measurable goal] +2. [Specific, measurable goal] +3. [Specific, measurable goal] + +## Authenticity Check +- Am I genuinely interested in these people, or performing interest? +- Which relationships feel transactional, and how do I make them genuine? +``` + +--- + +## Related Skills + +- **[Cialdini's Influence](cialdini-influence.md)** -- Cialdini provides the scientific framework for why Carnegie's principles work; Carnegie provides the practitioner's art of applying them in real relationships. +- **[Trust Equation](trust-equation.md)** -- Carnegie's principles build every numerator of the trust equation (credibility, reliability, intimacy) while naturally reducing the denominator (self-orientation). +- **[Radical Candor](radical-candor.md)** -- Carnegie and Scott appear to conflict -- "never criticise" versus "challenge directly" -- but they address complementary aspects of maintaining relationship quality while delivering necessary truths. +- **[Win-Win Negotiation](win-win-negotiation.md)** -- Carnegie's "arouse an eager want" is the interpersonal equivalent of Fisher and Ury's "focus on interests, not positions." +- **[Connecting with People](../people/connecting-with-people.md)** -- Extends Carnegie's relationship-building principles into practical strategies for meeting, engaging, and deepening connections in professional contexts. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Goleman's empathy and social skill domains provide the psychological substrate that makes Carnegie's principles effective rather than performative. diff --git a/plugins/foreman/content/skills/frameworks/cialdini-influence.md b/plugins/foreman/content/skills/frameworks/cialdini-influence.md new file mode 100644 index 0000000..a56ea76 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/cialdini-influence.md @@ -0,0 +1,226 @@ +--- +name: "cialdini-influence" +description: "Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing fundraising strategies, auditing marketing materials for persuasive effectiveness, planning negotiation tactics, or building community-driven growth while maintaining ethical boundaries." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - persuasion + - influence + - psychology + - sales + - marketing + - negotiation +related_skills: + - carnegie-win-friends + - win-win-negotiation + - trust-equation + - cialdini-influence +author: "Fatih Guner" +--- + +# Cialdini's Principles of Influence + +Machiavelli understood power. He also understood that writing a manual for its naked exercise would earn him five centuries of notoriety -- the word "Machiavellian" survives as a synonym for amoral manipulation. Robert Cialdini, the Arizona State psychologist whose *Influence: The Psychology of Persuasion* has sold over five million copies, operates in adjacent territory but with a critical distinction. Where Machiavelli catalogued how power is *seized*, Cialdini mapped how consent is *manufactured* -- and then insisted on an ethical boundary. His seven principles describe the psychological triggers that cause people to say yes. They work whether deployed ethically or cynically, which is precisely why understanding them is not optional for founders. You will use these principles, or they will be used on you. The only choice is whether you wield them with awareness and integrity. + +The difference between influence and manipulation is not technique -- it is intent. Influence uses legitimate psychological principles to guide people toward decisions that genuinely serve their interests. Manipulation uses the same principles to exploit them. The toolkit is identical; the ethics are opposite. + +--- + +## The Framework + +Cialdini originally identified six principles in 1984, then added a seventh -- Unity -- in 2016's *Pre-Suasion*. Each principle operates as an automatic behavioural shortcut: a mental heuristic that humans use to navigate complex decisions efficiently, and that can be activated deliberately. + +### Principle 1: Reciprocity + +People feel obligated to return favours, gifts, and concessions. This obligation operates even when the initial favour was unsolicited and even when the return favour exceeds the original in value. + +**Mechanism:** When someone does something for us, a psychological debt is created. The discomfort of that debt motivates repayment -- often disproportionately. + +**Entrepreneurial application:** +- Offer genuine value before asking for anything: free trials, educational content, useful introductions +- In negotiations, make the first concession; the other party will feel compelled to reciprocate +- In fundraising, provide investors with valuable market intelligence before the pitch + +**Ethical boundary:** The favour must be genuine. Manufactured obligations -- "I gave you this free sample, now you owe me" -- erode trust when the manipulation becomes apparent. + +### Principle 2: Commitment and Consistency + +Once people commit to a position -- especially publicly and voluntarily -- they experience internal pressure to behave consistently with that commitment. Small initial commitments escalate into larger ones. + +**Mechanism:** Cognitive dissonance makes inconsistency psychologically uncomfortable. We adjust behaviour to match prior statements and actions, rationalising the alignment after the fact. + +**Entrepreneurial application:** +- Get early adopters to make small commitments (a free sign-up, a beta test) before requesting larger ones (a paid subscription, a case study) +- In hiring, candidates who invest time in a multi-stage process develop commitment to the outcome +- Public declarations of company values create internal pressure for leadership to honour them + +**Ethical boundary:** The initial commitment must be voluntary and informed. "Foot-in-the-door" techniques that deliberately obscure the eventual ask violate trust. + +### Principle 3: Social Proof + +When uncertain, people look to others' behaviour for guidance. The more people doing something, the more correct that behaviour appears. + +**Mechanism:** In ambiguous situations, the assumption "if everyone else is doing it, it must be right" is actually a reasonable heuristic -- most of the time. It fails spectacularly in cases of collective ignorance or herding. + +**Entrepreneurial application:** +- Display customer logos, testimonials, and usage statistics prominently +- "Join 10,000 companies who use [product]" works because it activates social proof +- In fundraising, name investors who have already committed (with permission) to trigger herd behaviour among those who have not +- Press coverage and analyst endorsements serve as expert social proof + +**Ethical boundary:** Social proof must be real. Fabricated testimonials, inflated numbers, and fake reviews are fraud, not influence. + +### Principle 4: Authority + +People defer to perceived experts and authority figures. Credentials, titles, uniforms, and demonstrated expertise all trigger compliance. + +**Mechanism:** Deference to authority is a deeply evolved heuristic -- following expert guidance is usually more efficient than independent evaluation of every decision. + +**Entrepreneurial application:** +- Establish thought leadership through publishing, speaking, and demonstrable expertise +- In sales, present case studies authored by recognisable industry figures +- Hire advisory board members whose authority transfers to the company +- In product marketing, use expert endorsements and third-party validation + +**Ethical boundary:** Authority must be legitimate. Claiming credentials you do not possess or manufacturing expert endorsements crosses from influence into deception. + +### Principle 5: Liking + +People are more easily influenced by those they like. Factors that increase liking include physical attractiveness, similarity, compliments, familiarity, and association with positive outcomes. + +**Mechanism:** Liking creates a halo effect -- positive feelings toward a person generalise to positive feelings about their proposals, products, and requests. + +**Entrepreneurial application:** +- Build genuine rapport before business conversations +- Find authentic common ground with investors, customers, and partners +- Personal branding is a liking strategy -- making the founder relatable humanises the company +- Community building creates peer-to-peer liking that transfers to the brand + +**Ethical boundary:** Liking must be authentic. Simulated warmth and calculated flattery may work short-term but produce lasting cynicism when unmasked. + +### Principle 6: Scarcity + +Opportunities appear more valuable when their availability is limited. Loss aversion (the pain of losing exceeds the pleasure of gaining) amplifies this effect. + +**Mechanism:** Scarcity signals value. If something is rare, it must be desirable -- otherwise, why would it be scarce? This heuristic served well in environments of genuine scarcity; it misfires in environments of manufactured scarcity. + +**Entrepreneurial application:** +- Limited-time offers, waitlists, and exclusive access create urgency +- "Only 3 spots remaining in our beta programme" (if true) activates scarcity +- In fundraising, genuine competitive interest from multiple investors creates natural scarcity +- Product launches with constrained supply generate demand + +**Ethical boundary:** Scarcity must be real. Fake countdown timers, artificial limitations, and perpetual "last chance" offers are the dark pattern equivalent of this principle. + +### Principle 7: Unity + +People are more influenced by those they perceive as belonging to the same group -- not mere similarity (liking) but shared identity. Family, nationality, profession, fandom, and tribe all create unity. + +**Mechanism:** Unity activates an in-group/out-group psychology far stronger than liking. "One of us" is a more powerful motivator than "someone I like." + +**Entrepreneurial application:** +- Build a community identity around your product or mission ("we are the people who...") +- Shared professional identity with investors ("as fellow engineers...") increases receptivity +- User communities that develop their own language, rituals, and identity create powerful retention +- Co-creation -- involving customers in product development -- builds unity through shared ownership + +**Ethical boundary:** Unity must not be weaponised through exclusion or tribalism. Building identity by defining an enemy is effective but corrosive. + +--- + +## Prompts + +**Prompt 1 -- Influence Audit:** +> Audit my current sales and marketing approach against Cialdini's seven principles of influence. Here is our customer journey: [describe from first touch to conversion]. For each principle (reciprocity, commitment/consistency, social proof, authority, liking, scarcity, unity), identify where we are already using it effectively, where we are missing opportunities, and where we may be crossing ethical boundaries. Recommend three specific changes. + +**Prompt 2 -- Fundraising Influence Strategy:** +> I am preparing to raise a [Series A/Seed/etc.] round. Using Cialdini's seven principles, design an influence strategy for my investor outreach. For each principle, provide a specific tactic I can use in the fundraising process -- from initial warm intro through pitch meeting through term sheet negotiation. My company: [describe stage, traction, industry]. Ensure every tactic stays on the ethical side of the influence/manipulation boundary. + +**Prompt 3 -- Ethical Persuasion Review:** +> Review the following marketing materials / sales scripts / pitch deck against Cialdini's principles. [Paste materials.] Identify which principles are being activated, whether the application is ethically sound, and where the messaging could be more persuasive without crossing into manipulation. Rewrite the three weakest sections. + +**Prompt 4 -- Negotiation Influence Plan:** +> I am entering a negotiation with [describe the other party and context]. Using Cialdini's principles, design a pre-suasion strategy (what I should do before the negotiation begins) and an in-negotiation influence plan. Identify which principles are most relevant to this specific counterparty and context, and provide specific language and actions for each. + +--- + +## Use Cases + +**Validation-Stage Startup Building a Waitlist** +A pre-launch consumer app needs to build demand before the product exists. Applying Cialdini systematically: Reciprocity -- offer early registrants exclusive content (a market research report) before asking for their email. Commitment -- ask registrants to invite one friend, creating a micro-commitment. Social proof -- display a live counter of registrations. Scarcity -- "first 1,000 users get lifetime premium access." Unity -- frame early adopters as "founding members" with a distinct identity. The combination produces a 12,000-person waitlist before launch. + +**Growth-Stage B2B SaaS Closing Enterprise Deals** +A B2B company struggles with long sales cycles in enterprise. Applying the framework: Authority -- publish a white paper co-authored with a recognised industry analyst. Social proof -- create a customer advisory board whose members' logos appear on the website. Reciprocity -- provide a free architecture assessment before the sales pitch. Commitment -- structure the evaluation as a phased pilot (small commitment) that naturally escalates. Liking -- ensure account executives research each prospect's background to find authentic connection points. Average sales cycle shortens by 23%. + +**Scale-Stage Company Negotiating a Strategic Partnership** +A 500-person company negotiates a platform integration with a larger partner. The power asymmetry is significant. Unity -- emphasise shared mission and the specific customer segment both companies serve ("our mutual customers need this"). Authority -- present data from a joint customer survey demonstrating demand. Reciprocity -- offer to co-invest in the integration engineering. Scarcity -- note (truthfully) that a competing platform has also expressed interest. The combination produces equitable partnership terms despite the size differential. + +--- + +## Anti-Patterns + +1. **Treating Influence as Manipulation Laundering.** Using Cialdini's academic veneer to dress up fundamentally deceptive practices. Fake scarcity, fabricated social proof, and manufactured authority are not "influence tactics" -- they are lies. The framework's ethical boundary is not a suggestion; it is its structural integrity. + +2. **Over-Indexing on a Single Principle.** Companies that rely exclusively on scarcity ("LIMITED TIME OFFER!") or social proof ("10 million users!") while neglecting reciprocity and genuine value creation. Influence is most powerful when multiple principles reinforce each other authentically. + +3. **Ignoring Cultural Variation.** Cialdini's research was conducted primarily in Western, individualistic societies. Authority and social proof operate differently in collectivist cultures. Liking manifests differently across cultural contexts. Founders operating internationally must calibrate principle application to cultural norms. + +4. **Confusing Short-Term Compliance with Long-Term Influence.** Influence principles can produce immediate compliance that erodes long-term trust. Aggressive scarcity tactics might close a sale today and produce a churn event next quarter. The principles are most valuable when they accelerate genuine value recognition, not when they override genuine hesitation. + +5. **Neglecting the Seventh Principle.** Many practitioners still operate on the original six principles, missing Unity entirely. In an era of community-driven growth, identity-based products, and mission-driven purchasing, Unity is often the most powerful principle available to startups. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Customer discovery influence | At validation, influence is about getting strangers to give you their most precious resource: time. Reciprocity (offering insight) and liking (genuine curiosity about their problems) are the dominant principles. | +| Early Traction | Conversion and evangelism | With a product in market, social proof and commitment become essential. Early customers who publicly commit to the product become evangelists whose advocacy activates social proof for subsequent customers. | +| Growth | Sales process optimisation | At growth, the influence framework becomes systematised across sales, marketing, and partnerships. Each principle maps to specific touchpoints in the customer journey. | +| Scale | Brand and community | At scale, Unity and Authority dominate. The company builds a category identity, establishes thought leadership, and creates a community whose shared identity becomes the most powerful retention mechanism. | + +--- + +## Output Template + +```markdown +# Influence Strategy: [Context — e.g., Product Launch / Fundraise / Partnership] + +## Principle Application Matrix +| Principle | Current Usage | Opportunity | Specific Tactic | Ethical Check | +|-----------|-------------|-------------|-----------------|---------------| +| Reciprocity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Commitment & Consistency | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Social Proof | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Authority | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Liking | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Scarcity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Unity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | + +## Priority Actions (Top 3) +1. [Highest-impact tactic with implementation steps] +2. [Second priority with implementation steps] +3. [Third priority with implementation steps] + +## Ethical Guardrails +- [Specific boundaries for this context] +- [What we will NOT do, and why] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends](carnegie-win-friends.md)** -- Carnegie's principles of interpersonal influence predate and overlap significantly with Cialdini's Liking and Reciprocity principles, providing the practitioner's art alongside the psychological science. +- **[Win-Win Negotiation](win-win-negotiation.md)** -- Cialdini's principles inform negotiation strategy at the tactical level, while principled negotiation provides the strategic framework for ensuring influence serves mutual gain. +- **[Trust Equation](trust-equation.md)** -- Influence without trust is manipulation with a timer; the Trust Equation diagnoses whether influence tactics are building or eroding the relational foundation. +- **[Persuasion and Influence](../leadership/persuasion-and-influence.md)** -- Translates Cialdini's principles into leadership-specific contexts including stakeholder management, board communication, and organizational change. +- **[Influencing and Persuading](../people/influencing-and-persuading.md)** -- Provides practical interpersonal techniques that operationalize Cialdini's seven principles in face-to-face and group settings. +- **[Neuro-Linguistic Programming](neuro-linguistic-programming.md)** -- NLP's rapport-building and language pattern techniques complement Cialdini's Liking and Unity principles at the micro-communication level. diff --git a/plugins/foreman/content/skills/frameworks/covey-seven-habits.md b/plugins/foreman/content/skills/frameworks/covey-seven-habits.md new file mode 100644 index 0000000..db4f5be --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/covey-seven-habits.md @@ -0,0 +1,208 @@ +--- +name: "covey-seven-habits" +description: "Applies Stephen Covey's Seven Habits framework for personal and + interpersonal effectiveness, progressing from dependence through independence + to interdependence. Covers proactivity, mission clarity, prioritization, + Win/Win thinking, empathic listening, synergy, and renewal. Use when + conducting personal effectiveness audits, drafting mission statements, + preparing Win/Win negotiations, resolving co-founder conflicts, designing + founder renewal plans to prevent burnout, or building character-based + leadership culture." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - personal-effectiveness + - leadership + - character-ethics + - habits + - interpersonal-skills + - self-management +related_skills: + - eisenhower-matrix + - emotional-intelligence + - grow-model + - tuckman-team-stages +author: "Fatih Guner" +--- + +# Covey's Seven Habits of Highly Effective People + +The self-help industry generates roughly $14 billion annually in the United States alone, and the vast majority of that output is forgettable within months of publication. Stephen Covey's *The Seven Habits of Highly Effective People*, published in 1989, is the notable exception -- over 40 million copies sold, translated into 40 languages, and still assigned in MBA programs three decades later. The book's durability is not a marketing phenomenon; it reflects a genuine intellectual contribution. Covey drew a sharp distinction between what he called the "personality ethic" (techniques, shortcuts, positive mental attitude) and the "character ethic" (principles, integrity, deep competence). His argument -- that lasting effectiveness flows from character, not charisma -- was unfashionable when published and remains countercultural in a business environment that rewards performative confidence. For entrepreneurs, who must build trust with investors, employees, customers, and partners simultaneously, the character ethic is not optional. + +--- + +## The Framework + +Covey organizes the seven habits along a maturity continuum: from dependence (others take care of me) through independence (I take care of myself) to interdependence (we accomplish more together). Most self-help literature stops at independence. Covey argues that interdependence -- the ability to collaborate effectively while maintaining personal integrity -- is the highest and most productive state. + +### The Maturity Continuum + +``` +DEPENDENCE → INDEPENDENCE → INTERDEPENDENCE + (Habits 1-3) (Private Victory) (Habits 4-6) (Public Victory) + ↓ + Habit 7: Renewal +``` + +### Habits 1-3: Private Victory (Self-Mastery) + +**Habit 1 -- Be Proactive** +Proactivity is not mere initiative. It is the recognition that between stimulus and response lies a space, and within that space lies the freedom to choose. Reactive people are driven by feelings, circumstances, and conditions. Proactive people are driven by values. The practical test: does the person focus on their Circle of Influence (things they can affect) or their Circle of Concern (things they worry about but cannot control)? + +For entrepreneurs, proactivity means focusing energy on what can be built, tested, and changed rather than on market conditions, competitor actions, or investor sentiment that lie outside direct control. + +**Habit 2 -- Begin with the End in Mind** +Every meaningful creation happens twice: first as a mental conception, then as a physical reality. Habit 2 is about ensuring that the first creation is deliberate. Covey advocates writing a personal mission statement -- a constitution that governs decision-making. For founders, this extends to a company mission statement that is genuinely operational rather than decorative. + +The principle is architectural: if you do not define what success looks like before you begin, you will optimize for metrics that may be irrelevant or harmful. Many startups achieve impressive growth toward destinations nobody actually wanted to reach. + +**Habit 3 -- Put First Things First** +Where Habit 2 is strategic (what matters most?), Habit 3 is executional (how do you spend your time?). This is where the Eisenhower Matrix enters Covey's framework, distinguishing urgent from important. Habit 3 demands that Quadrant II activities -- important but not urgent -- receive protected time. The habit requires saying no to good opportunities in order to say yes to the best ones. + +### Habits 4-6: Public Victory (Interdependence) + +**Habit 4 -- Think Win/Win** +Win/Win is not a negotiation tactic. It is a frame of mind that seeks mutual benefit in all interactions. Covey identifies six interaction paradigms: + +| Paradigm | Description | Entrepreneurial Context | +|----------|-------------|------------------------| +| Win/Win | Both parties benefit | Partnerships, equity negotiations, customer relationships | +| Win/Lose | I benefit at your expense | Short-term supplier squeezing, zero-sum competition | +| Lose/Win | I accommodate at my expense | Founder undervaluing their equity, accepting unfavorable terms | +| Lose/Lose | Neither party benefits | Vindictive competition, destructive conflicts | +| Win | I focus only on my outcome | Transactional relationships with no regard for the other side | +| Win/Win or No Deal | We find mutual benefit or walk away | The most mature option when ongoing relationship matters | + +The entrepreneurial application is direct: founders negotiate constantly -- with co-founders, employees, investors, customers, partners. Those who default to Win/Lose may win individual negotiations but destroy the trust infrastructure on which scaling depends. + +**Habit 5 -- Seek First to Understand, Then to Be Understood** +Most people listen with the intent to reply, not to understand. Covey calls this "autobiographical listening" -- filtering everything through one's own experience. Empathic listening -- genuinely entering the other person's frame of reference -- is rare and powerful. For founders, this habit transforms customer discovery, employee management, and investor relations. The founder who truly understands a customer's problem before proposing a solution builds products that matter. + +**Habit 6 -- Synergize** +Synergy is not a buzzword in Covey's framework; it is a specific phenomenon: the whole becoming greater than the sum of its parts. Synergy emerges when people with different perspectives engage in open, trusting communication and produce solutions that none could have conceived alone. The preconditions are the preceding habits: proactivity, clarity of purpose, prioritization, mutual benefit, and empathic understanding. + +### Habit 7: Renewal + +**Habit 7 -- Sharpen the Saw** +Sustainable effectiveness requires regular renewal across four dimensions: + +- **Physical**: Exercise, nutrition, rest +- **Mental**: Reading, learning, writing +- **Social/Emotional**: Relationships, service, empathy +- **Spiritual**: Meditation, values clarification, nature + +Covey's argument is that neglecting renewal in any dimension degrades performance across all dimensions. For entrepreneurs, who are notorious for sacrificing health and relationships on the altar of their venture, Habit 7 is not indulgent -- it is structural. Burned-out founders make poor decisions. + +--- + +## Prompts + +**Prompt 1 -- Personal Effectiveness Audit:** +> Evaluate my current effectiveness against Covey's Seven Habits. For each habit, I will describe my typical behavior and you assess my maturity level (1-5) and recommend specific improvements. Here is my self-assessment: Habit 1 (Proactivity): [describe]. Habit 2 (End in Mind): [describe]. Habit 3 (First Things First): [describe]. Habit 4 (Win/Win): [describe]. Habit 5 (Understand First): [describe]. Habit 6 (Synergize): [describe]. Habit 7 (Sharpen the Saw): [describe]. + +**Prompt 2 -- Mission Statement Workshop:** +> Help me draft a personal mission statement using Covey's Habit 2 process. Ask me questions about my core values, the roles I play (founder, partner, parent, friend, community member), and the legacy I want to create. Then synthesize my answers into a mission statement of 3-5 sentences that I can use as a decision-making filter. Also help me translate this into a company mission statement that aligns with my personal one. + +**Prompt 3 -- Win/Win Negotiation Prep:** +> I have an upcoming negotiation about [describe: fundraising, partnership, hiring, contract]. Help me prepare using Covey's Win/Win framework. What does the other party want and need? What do I want and need? Where is the overlap? What creative options might expand the pie rather than divide it? What is my "no deal" walk-away point? Prepare me with a negotiation approach that prioritizes relationship preservation alongside outcome achievement. + +**Prompt 4 -- Founder Renewal Plan:** +> I have been running my startup for [timeframe] and I recognize signs of burnout: [describe symptoms]. Help me design a Habit 7 renewal plan across Covey's four dimensions (physical, mental, social/emotional, spiritual). For each dimension, recommend specific, time-bounded practices that fit within a founder's schedule. Include weekly minimums, warning signs of neglect, and accountability mechanisms. + +--- + +## Use Cases + +**Idea-Stage Founder Clarifying Direction** +A first-time founder with three potential business ideas and scattered energy uses Habits 1-3 to establish personal clarity. Habit 1: she identifies that her anxiety about competitor activity is Circle of Concern waste and refocuses on her Circle of Influence -- customer conversations and prototype development. Habit 2: she writes a mission statement centered on democratizing financial literacy, which immediately eliminates one of the three ideas as misaligned. Habit 3: she audits her weekly schedule and discovers that 60% of her time goes to networking events (QIII) rather than customer discovery (QII). The result is not a business plan but something more valuable: a focused founder. + +**Growth-Stage Co-Founder Conflict Resolution** +Two co-founders at a 50-person company are deadlocked on product direction. Applying Habit 5, they agree to spend one hour each genuinely articulating the other's position before advocating their own. The exercise surfaces a misunderstanding: one founder's insistence on enterprise features is driven by a specific large-customer conversation the other had not been briefed on. With mutual understanding established, Habit 6 produces a synthesis: a modular architecture that serves both enterprise and SMB segments. The conflict was not about competing visions -- it was about incomplete information filtered through insufficient empathy. + +**Scale-Stage CEO Building a Leadership Team** +A CEO at a 300-person company applies the entire Covey framework to her leadership approach. Habit 4 structures her compensation philosophy (equity packages designed for Win/Win alignment). Habit 5 transforms her quarterly reviews from performance monologues into genuine dialogue. Habit 7 leads her to institute "no-meeting Wednesdays" for the entire company, protecting renewal time at the organizational level. The result, measured over 18 months: employee NPS rises from 32 to 61, and voluntary attrition drops from 24% to 11%. + +--- + +## Anti-Patterns + +1. **Treating the habits as a checklist rather than a developmental sequence.** Covey is explicit that the habits build on each other. Attempting Habit 6 (Synergize) without first mastering Habit 5 (Understand First) produces false collaboration -- people agreeing without genuinely engaging with different perspectives. + +2. **Weaponizing "proactivity" to blame people for external circumstances.** Habit 1 does not mean that structural disadvantages, market collapses, or bad luck are the individual's fault. It means that the individual chooses their response to these circumstances. Leaders who use "be proactive" to dismiss legitimate complaints about working conditions have misunderstood the concept entirely. + +3. **Writing a mission statement and filing it away.** Habit 2 requires a living document that is reviewed regularly and used as an active decision-making filter. A mission statement that sits in a drawer is performative, not operational. + +4. **Confusing Win/Win with compromise.** Compromise means both sides give something up. Win/Win means finding a creative solution where both sides gain. The distinction matters: compromise breeds resentment over time, while genuine Win/Win builds trust and expands future possibilities. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Habits 1-3 (Private Victory) | The founder's personal effectiveness is the company's effectiveness. Proactivity, mission clarity, and ruthless prioritization are survival skills. Interdependence habits matter less because the team is small or nonexistent. | +| Validation | Habit 5 dominance | Customer discovery IS empathic listening applied to market problems. The founder who masters "seek first to understand" during validation builds products that actually solve problems rather than products that reflect the founder's assumptions. | +| Early Traction | Habits 4-6 emerge | The team is growing. Win/Win structures (equity, compensation, role design) become critical. Synergy with early employees determines whether the company builds leverage or just adds headcount. | +| Growth | Full framework integration | All seven habits are in play. The founder's character -- proactivity, integrity, empathy, renewal -- sets the cultural tone for the organization. Deficits in any habit are amplified by organizational scale. | +| Scale | Habit 7 becomes existential | At scale, founder burnout is an enterprise risk. Renewal is not personal indulgence -- it is risk management. The CEO must also model renewal for the organization, creating a culture where sustainable performance is valued over heroic exhaustion. | + +--- + +## Output Template + +```markdown +# Personal Effectiveness Assessment (Covey Seven Habits) + +**Name:** [Your name] +**Date:** [Date] +**Company Stage:** [Stage] + +## Habit Maturity Scorecard + +| Habit | Self-Rating (1-5) | Evidence | Priority Action | +|-------|-------------------|----------|-----------------| +| 1. Be Proactive | [Score] | [Behavior example] | [Specific action] | +| 2. Begin with End in Mind | [Score] | [Mission clarity level] | [Specific action] | +| 3. Put First Things First | [Score] | [QII time %] | [Specific action] | +| 4. Think Win/Win | [Score] | [Recent negotiation example] | [Specific action] | +| 5. Seek First to Understand | [Score] | [Listening quality] | [Specific action] | +| 6. Synergize | [Score] | [Collaboration example] | [Specific action] | +| 7. Sharpen the Saw | [Score] | [Renewal practices] | [Specific action] | + +## Current Maturity Level +- [ ] Dependence +- [ ] Independence (Private Victory achieved) +- [ ] Interdependence (Public Victory achieved) + +## Top 3 Development Priorities +1. [Habit #] -- [Specific development plan with timeline] +2. [Habit #] -- [Specific development plan with timeline] +3. [Habit #] -- [Specific development plan with timeline] + +## Renewal Plan (Habit 7) + +| Dimension | Current Practice | Target Practice | Weekly Minimum | +|-----------|-----------------|-----------------|----------------| +| Physical | [Current] | [Target] | [Hours/week] | +| Mental | [Current] | [Target] | [Hours/week] | +| Social/Emotional | [Current] | [Target] | [Hours/week] | +| Spiritual | [Current] | [Target] | [Hours/week] | +``` + +--- + +## Related Skills + +- **[Eisenhower Matrix](eisenhower-matrix.md)** -- Habit 3 operationalizes the Eisenhower Matrix; the matrix is the tactical tool while the Seven Habits provide the character foundation that makes consistent use of it possible. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Habit 5 (empathic listening) and Habit 4 (Win/Win thinking) are expressions of emotional intelligence applied to professional relationships. +- **[Win-Win Negotiation](win-win-negotiation.md)** -- Habit 4's Win/Win orientation finds its operational methodology in Fisher and Ury's principled negotiation framework. +- **[GROW Model](grow-model.md)** -- The coaching framework that helps individuals develop specific habits through structured goal-setting and action planning. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Teams moving through Tuckman's stages benefit when members practice Habits 4-6, particularly during the Storming phase where Win/Win thinking and empathic listening prevent destructive conflict. +- **[Leader Resilience and Wellbeing](../leadership/leader-resilience-and-wellbeing.md)** -- Habit 7 (Sharpen the Saw) provides the philosophical foundation for the structured renewal and burnout prevention practices leaders need. diff --git a/plugins/foreman/content/skills/frameworks/disruptive-innovation.md b/plugins/foreman/content/skills/frameworks/disruptive-innovation.md new file mode 100644 index 0000000..e396d72 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/disruptive-innovation.md @@ -0,0 +1,203 @@ +--- +name: "disruptive-innovation" +description: "Analyzes market opportunities and threats using Christensen's Disruptive Innovation theory, distinguishing between sustaining and disruptive innovation, low-end and new-market disruption. Evaluates incumbent vulnerability, asymmetric advantages, and technology improvement trajectories. Use when assessing whether a startup has a genuinely disruptive position, mapping incumbent blind spots, designing market entry strategies that avoid direct competition, defending against disruption from below, or evaluating whether to pursue low-end or new-market footholds." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth +tags: + - disruption + - competitive-strategy + - market-entry + - incumbent-vulnerability + - innovation-theory +related_skills: + - doblin-ten-types + - blue-ocean-strategy + - product-life-cycle + - growth-share-matrix +author: "Fatih Guner" +--- + +# Disruptive Innovation + +Kodak invented the digital camera in 1975 and buried it, fearful of cannibalising its film business. By 2012, the company had filed for bankruptcy. Blockbuster had the opportunity to acquire Netflix for $50 million in 2000 and declined; by 2010, it was gone. Nokia commanded 49% of the global smartphone market in 2007, the year Apple introduced the iPhone; by 2013, its handset division was sold to Microsoft for a fraction of its former value. These are not cautionary tales about bad management. They are case studies in a structural pattern that Clayton Christensen identified and named in *The Innovator's Dilemma* (1997): disruption does not kill companies because their leaders are incompetent. It kills them because their leaders are doing exactly what good management theory tells them to do -- listening to their best customers, investing in the highest-margin opportunities, and pursuing sustaining innovations that improve existing products along established performance dimensions. The tragedy is that rational, well-managed companies can do everything right and still lose everything. + +--- + +## The Framework + +### The Mechanism of Disruption + +Christensen distinguished between two fundamentally different types of innovation: + +**Sustaining Innovation** improves existing products along dimensions that mainstream customers already value. Faster processors, sharper displays, more features. Incumbents almost always win at sustaining innovation because they have the resources, customer relationships, and organisational incentives to execute it. + +**Disruptive Innovation** introduces products that are initially worse on traditional performance dimensions but offer different value -- typically simplicity, convenience, affordability, or accessibility. These products enter at the low end or in new markets that incumbents ignore because the margins are unattractive. + +The disruption pattern follows a predictable trajectory: + +**Phase 1: The Entrant Emerges Below the Radar** + +The disruptive product is simpler, cheaper, and inferior on the dimensions that mainstream customers care about. Incumbents dismiss it. Their best customers would never accept it. The margins are too low to justify pursuit. Every incentive in the incumbent's organisation points away from engagement. + +- Digital cameras in 1995: low resolution, poor colour accuracy, no prints. Professional photographers would never use them. +- Netflix in 2000: limited catalogue, DVD-by-mail latency, no instant gratification. Blockbuster's Friday-night customers would never switch. +- Smartphones in 2007: compared to Nokia's phones, the first iPhone had terrible battery life, no 3G, and could not send MMS. + +**Phase 2: The Entrant Improves Along a Steeper Trajectory** + +Technology improves faster than customer needs increase. The disruptive product gets better at a rate that eventually exceeds what mainstream customers require. Meanwhile, incumbents overshoot -- adding features and performance that customers neither need nor will pay for. + +**Phase 3: The Entrant Captures the Mainstream** + +The disruptive product becomes "good enough" for the mainstream market while retaining its advantages of simplicity, cost, or convenience. Customers switch. By this point, the incumbent's response is too late -- not because the technology is unreachable, but because the business model, cost structure, and organisational culture cannot adapt fast enough. + +**Phase 4: The Incumbent Retreats or Collapses** + +The incumbent either retreats to an ever-shrinking premium segment, attempts a pivot that its cost structure cannot support, or ceases to exist. + +### Two Types of Disruption + +**Low-End Disruption** targets customers at the bottom of the existing market -- those who are overserved by current offerings and willing to accept "good enough" performance at a lower price. + +- Example: Southwest Airlines offered no assigned seats, no meals, no frills -- and fares that opened air travel to customers who previously drove or took the bus. +- Incumbent response: Major airlines ceded the low end because those customers were unprofitable under their cost structures. + +**New-Market Disruption** creates demand among people who were previously non-consumers -- those who lacked the money, skills, or access to use existing solutions. + +- Example: Personal computers disrupted minicomputers not by being better for existing minicomputer users, but by enabling millions of people who could never have afforded or operated a minicomputer to use computing power. +- Incumbent response: DEC and other minicomputer makers saw no threat because PCs could not do what their products did. By the time PCs could, the market had moved. + +### The Innovator's Dilemma, Precisely Stated + +The dilemma is structural, not intellectual. Incumbents understand the disruption. They can see it coming. They often have the technology to respond. But their existing customers do not want the disruptive product, their financial models cannot support the lower margins, and their organisational processes are optimised for sustaining innovation. The very capabilities that made them successful prevent them from responding to disruption. + +This is why Christensen's work remains so valuable for entrepreneurs: the incumbent's rational response creates a structural opening that the entrant can exploit with near-certainty. + +--- + +## Prompts + +**Prompt 1 -- Disruption Potential Assessment:** +> "Analyse whether my product/service [describe offering] qualifies as a disruptive innovation against incumbent [describe incumbent]. Assess: (1) Are we targeting overserved customers or non-consumers? (2) Is our product worse on traditional dimensions but better on simplicity, convenience, or cost? (3) Is the incumbent structurally unable to respond without cannibalising their core business? (4) Is there a plausible technology trajectory that will make our product good enough for the mainstream within [timeframe]?" + +**Prompt 2 -- Incumbent Vulnerability Mapping:** +> "Map the vulnerability of incumbents in [industry] to disruption. For each major incumbent: (1) What is their cost structure and minimum viable margin? (2) Where are their best customers pulling them (toward complexity and premium features)? (3) What customer segments are overserved or priced out? (4) What emerging technologies could enable a simpler, cheaper alternative? Identify the most vulnerable point of entry for a disruptive entrant." + +**Prompt 3 -- Disruption Defence Strategy:** +> "My company is an incumbent in [market] with [revenue/market position]. Analyse our vulnerability to disruption from below or from new-market entrants. Where is our market most exposed? What signals should we monitor for early-stage disruptive threats? Design a defensive strategy that includes: an autonomous unit to pursue disruptive opportunities, metrics for tracking low-end market dynamics, and decision criteria for when to cannibalise our own products." + +**Prompt 4 -- Asymmetric Advantage Identification:** +> "Identify the asymmetric advantages I hold as a startup against incumbents in [market]. Consider: cost structure flexibility, absence of channel conflict, willingness to serve low-margin segments, organisational speed, and freedom from legacy technology. For each advantage, describe a specific strategic move that exploits it while remaining in the incumbent's 'blind spot.'" + +--- + +## Use Cases + +**Idea-Stage Founder Evaluating a Market Entry Strategy** + +A founder developing an AI-powered legal document service considers the market for corporate legal services dominated by major law firms. Christensen's framework clarifies the opportunity: large firms serve enterprise clients with bespoke, high-margin work and are structurally unable to offer standardised services at low price points without cannibalising their revenue model. Small businesses and solo entrepreneurs -- non-consumers of corporate legal services -- represent the new-market disruption opportunity. The founder designs a product that automates 80% of routine legal documents at 5% of the cost of a law firm, accepting that the 20% of complex cases requiring bespoke attention will remain with incumbents for years. The technology trajectory (improving AI accuracy) ensures that the 80/20 boundary will shift over time, expanding the addressable market while incumbents continue to move upmarket. + +**Validation-Stage Hardware Startup Positioning Against an Established Brand** + +A startup building an affordable 3D printer targets schools and hobbyists -- customers whom industrial 3D printing companies have never served because the margins are too thin and the support requirements too demanding for their sales organisations. The product is inferior on every dimension that industrial customers measure: precision, build volume, material range, and durability. But it costs 90% less and requires no specialised training. Christensen's framework confirms the positioning: this is classic low-end disruption. The startup validates by selling 500 units to schools through a crowdfunding campaign, proving demand exists in a segment that incumbents have no incentive to pursue. The product roadmap focuses on improving precision and material support along a trajectory that will eventually make the product "good enough" for professional prototyping. + +**Growth-Stage Fintech Navigating the Incumbent Response** + +A challenger bank with 200,000 accounts observes that traditional banks are beginning to launch digital-only offerings. Christensen's theory predicts this response -- and its likely failure. The incumbent's digital product will be constrained by its existing cost structure (branch network, compliance infrastructure, legacy systems), its organisational incentives (branch managers who resist cannibalisation), and its customer expectations (existing customers who demand full-service banking). The challenger's strategic response: accelerate product development in areas where the incumbent's cost structure prevents them from competing (instant lending decisions, zero-fee international transfers, real-time spending analytics) while building switching costs through product system innovation that makes the challenger the customer's primary financial relationship. + +--- + +## Anti-Patterns + +**Labelling Every New Product "Disruptive."** The term has been diluted to meaninglessness in popular usage. A better mousetrap is not disruption -- it is sustaining innovation. True disruption requires structural asymmetry: the incumbent cannot respond without damaging its core business. If the incumbent can simply build a competing product, there is no dilemma, and the startup is in a sustaining fight it will probably lose. + +**Targeting the Incumbent's Best Customers from Day One.** Disruptive entrants who go directly after the incumbent's core market trigger a competitive response that they cannot survive. The asymmetric advantage only exists when the entrant is serving customers the incumbent does not value. Attacking the core is sustaining competition -- and the incumbent has every advantage. + +**Underestimating the Importance of a Business Model.** Disruption is not primarily a technology phenomenon. It is a business model phenomenon. Uber did not disrupt taxis with superior technology; it disrupted them with a business model that eliminated the medallion system, reduced idle time, and created dynamic pricing. Entrepreneurs who focus exclusively on technical superiority while inheriting their industry's business model are fighting with one hand behind their back. + +**Assuming Incumbents Cannot Respond.** Christensen's framework describes why incumbents struggle to respond -- not that they never succeed. Microsoft survived the cloud disruption by creating Azure as a separate business unit with its own incentives. Intel invested in mobile chips. Some incumbents learn. The founder who assumes invulnerability will be surprised when a well-resourced incumbent deploys its considerable advantages in a belated but effective response. + +**Confusing Market Size with Opportunity.** Disruptive markets start small and grow. VCs and founders who require a billion-dollar addressable market on day one will dismiss precisely the opportunities that Christensen's theory identifies as most promising. The small, unattractive market is the feature, not the bug -- it is what keeps incumbents away. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Identify the asymmetry | Evaluate whether the opportunity has the structural characteristics of disruption: overserved customers, non-consumers, incumbent cost structure constraints | +| Validation | Prove demand in the overlooked segment | Validate that the customers incumbents ignore actually want your inferior-but-accessible product | +| Early Traction | Stay beneath the radar | Grow in the low-end or new-market segment; avoid triggering the incumbent's competitive response prematurely | +| Growth | Ride the improvement trajectory | As technology improves, expand into adjacent segments; the product becomes "good enough" for increasingly demanding customers | + +At the idea stage, the critical discipline is honesty about whether the opportunity is genuinely disruptive or merely competitive. The litmus test: would the incumbent's best customers want your product today? If yes, you are in a sustaining fight. If no, you may have a disruptive position. + +During early traction and growth, the temptation to pursue the incumbent's premium customers is intense -- they represent higher margins and larger contract values. Resist. Premature upmarket migration sacrifices the asymmetric advantage that makes disruption work. The strategy is to let the technology trajectory carry you upmarket while maintaining the cost structure advantages that the incumbent cannot match. + +--- + +## Output Template + +**Target Audience: Investors / Board** + +```markdown +# Disruption Analysis: [Company Name] in [Market] +## Date: [Date] + +### Disruption Classification +- Type: [Low-End Disruption / New-Market Disruption / Sustaining Innovation] +- Confidence: [High/Medium/Low] -- [Brief justification] + +### The Incumbent's Dilemma +| Dimension | Incumbent Position | Why They Cannot Respond | +|-----------|-------------------|----------------------| +| Cost structure | [Their cost base] | [Why they cannot profitably serve our segment] | +| Customer incentives | [Who their best customers are] | [Why those customers pull them away from our market] | +| Organisational design | [How they are structured] | [Why their organisation resists cannibilisation] | +| Channel conflict | [Their distribution model] | [How responding would damage existing channel relationships] | + +### Our Asymmetric Advantages +1. [Advantage] -- Exploitation strategy: [How we use it] +2. [Advantage] -- Exploitation strategy: [How we use it] +3. [Advantage] -- Exploitation strategy: [How we use it] + +### Technology Trajectory +- Current product performance vs. mainstream requirements: [Gap description] +- Improvement rate: [How quickly we are closing the gap] +- Estimated "good enough" date for mainstream market: [Timeline] + +### Disruption Phase Assessment +- [ ] Phase 1: Below the radar (serving overlooked segment) +- [ ] Phase 2: Improving faster than market demands +- [ ] Phase 3: Capturing mainstream customers +- [ ] Phase 4: Incumbent in retreat + +### Risk Factors +| Risk | Likelihood | Mitigation | +|------|-----------|------------| +| Incumbent creates autonomous unit to respond | [H/M/L] | [Strategy] | +| Another entrant disrupts from a different angle | [H/M/L] | [Strategy] | +| Technology trajectory stalls | [H/M/L] | [Strategy] | + +### Strategic Recommendations (Next 12 Months) +1. [Recommendation] -- Rationale: [Why] +2. [Recommendation] -- Rationale: [Why] +3. [Recommendation] -- Rationale: [Why] +``` + +--- + +## Related Skills + +- **[Doblin's Ten Types of Innovation](doblin-ten-types.md)** -- Disruption typically requires innovation across multiple types (profit model, process, channel) rather than product alone; Doblin provides the toolkit for building multi-layered disruptive advantage. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- New-market disruption is conceptually adjacent to Blue Ocean thinking; both identify opportunities in non-consumption, though they approach the problem from different angles. +- **[Product Life Cycle](product-life-cycle.md)** -- Products in the maturity or decline phase are most vulnerable to disruption; understanding life cycle dynamics helps identify the optimal timing for disruptive market entry. +- **[Growth Share Matrix](growth-share-matrix.md)** -- Incumbents' portfolio decisions (milking cash cows, investing in stars) create predictable blind spots that disruptive entrants can exploit. +- **[Ambidexterity](ambidexterity.md)** -- The organizational architecture that allows incumbents to respond to disruption by running separate exploration units with different metrics and culture. +- **[Evolutionary Strategy](../game-theory/evolutionary-strategy.md)** -- Provides the game-theoretic lens for understanding how disruptive entrants and incumbents co-evolve in competitive ecosystems over time. diff --git a/plugins/foreman/content/skills/frameworks/doblin-ten-types.md b/plugins/foreman/content/skills/frameworks/doblin-ten-types.md new file mode 100644 index 0000000..f2378b2 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/doblin-ten-types.md @@ -0,0 +1,221 @@ +--- +name: "doblin-ten-types" +description: "Maps and designs innovation strategy using Doblin's Ten Types of Innovation across Configuration (Profit Model, Network, Structure, Process), Offering (Product Performance, Product System), and Experience (Service, Channel, Brand, Customer Engagement). Use when auditing current innovation profile, identifying competitive white space, building multi-layered defensible advantages, breaking through competitive ceilings caused by product-only innovation, or designing a new business with structural moats from inception." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth +tags: + - innovation-strategy + - business-model-design + - competitive-advantage + - value-creation + - differentiation +related_skills: + - disruptive-innovation + - blue-ocean-strategy + - product-life-cycle + - balanced-scorecard +author: "Fatih Guner" +--- + +# Doblin's Ten Types of Innovation + +Most entrepreneurs, when asked about innovation, picture a product: a new gadget, a novel app feature, a technological breakthrough. This reflex -- equating innovation with invention -- is both pervasive and profoundly limiting. Larry Keeley and his colleagues at Doblin (now part of Deloitte) spent decades analysing thousands of innovations across industries and reached a conclusion that should discomfort any product-obsessed founder: product innovation is the easiest type for competitors to copy and the least likely to deliver sustained competitive advantage. The companies that dominate their markets innovate across multiple types simultaneously, building advantages that are structurally difficult to replicate because they exist not in any single feature but in the configuration of the entire business. + +The Ten Types of Innovation framework, published in 2013, provides the most comprehensive taxonomy of innovation available. It is not a theory about creativity. It is a strategic architecture for building businesses that competitors cannot easily decode. + +--- + +## The Framework + +The ten types organise into three categories: Configuration (how the business is structured), Offering (what the business delivers), and Experience (how customers interact with the business). + +### Configuration (Internal-Facing Innovation) + +**1. Profit Model -- How You Make Money** + +Innovation in the mechanism that converts value into revenue. Gillette did not invent the razor; it invented razors-and-blades pricing. Salesforce did not invent CRM; it invented SaaS subscription pricing for enterprise software. + +*Entrepreneurial application:* Challenge the default pricing model in your industry. Subscription where competitors charge one-time fees. Freemium where competitors charge upfront. Usage-based where competitors charge flat rates. Revenue-share where competitors charge licensing fees. + +**2. Network -- How You Connect with Others to Create Value** + +Innovation through alliances, partnerships, and ecosystems. Visa created a network of banks that would have been competitors if left to individual action. Apple's App Store turned independent developers into a product-development army. + +*Entrepreneurial application:* Identify which external parties could contribute to your value proposition if properly incentivised. Marketplace models, API platforms, franchise structures, and co-branding partnerships all represent network innovation. + +**3. Structure -- How You Organise and Align Talent and Assets** + +Innovation in organisational design, asset configuration, and human capital management. Toyota's production system. Google's 20% time (when it existed). Valve's flat hierarchy. + +*Entrepreneurial application:* How your company is organised affects what it can produce. A remote-first structure enables global talent access. A squad-based model enables parallel product development. Asset-light structures enable rapid scaling. + +**4. Process -- How You Use Superior Methods to Do Your Work** + +Innovation in the signature processes that create competitive advantage. Amazon's fulfilment logistics. IKEA's flat-pack manufacturing. Zara's fast-fashion supply chain that moves from design to retail in two weeks. + +*Entrepreneurial application:* Identify the one or two processes that most directly affect your value proposition. Innovating there -- through automation, proprietary methodology, or radical simplification -- creates defensible advantage because processes are invisible to competitors and difficult to reverse-engineer. + +### Offering (Product-Facing Innovation) + +**5. Product Performance -- How You Develop Distinguishing Features and Functionality** + +The type most people mean when they say "innovation." Superior features, performance, quality, or design. The iPhone's multitouch interface. Dyson's cyclone vacuum technology. Tesla's electric drivetrain. + +*Entrepreneurial application:* Product innovation is necessary but insufficient. Without reinforcement from other innovation types, product advantages erode within 12-18 months as competitors catch up. + +**6. Product System -- How You Create Complementary Products and Services** + +Innovation through creating an ecosystem of connected offerings. Apple's hardware-software-services integration. Microsoft Office as an integrated suite. Peloton's bike-plus-content-plus-community system. + +*Entrepreneurial application:* Consider what adjacent products or services would make your core offering more valuable. Integration points, accessories, data layers, and complementary content all represent product system innovation. + +### Experience (Customer-Facing Innovation) + +**7. Service -- How You Support and Amplify the Value of Your Offering** + +Innovation in the services that surround and enhance the core product. Amazon Prime's delivery promise. Zappos's 365-day return policy. AppleCare's service experience. + +*Entrepreneurial application:* Service innovation is particularly powerful for startups because it often requires organisational commitment rather than capital investment. A superior onboarding experience, proactive customer success, or unconditional guarantees can differentiate without heavy R&D spend. + +**8. Channel -- How You Deliver Your Offering to Customers and Users** + +Innovation in how you reach the customer. Warby Parker's home try-on disrupted optical retail. Dollar Shave Club's direct-to-consumer subscription bypassed retail entirely. Tesla's company-owned showrooms eliminated the dealership model. + +*Entrepreneurial application:* The default distribution channel in your industry may not be the optimal one. Direct-to-consumer, marketplace-first, partnership-led, or hybrid channel strategies can redefine who captures margin in the value chain. + +**9. Brand -- How You Represent Your Offering and Business** + +Innovation in how the company communicates its identity and values. Patagonia's "Don't Buy This Jacket" anti-consumerist positioning. Red Bull's content-company-that-sells-energy-drinks identity. Muji's "no-brand brand" philosophy. + +*Entrepreneurial application:* Brand innovation is not about a better logo. It is about occupying a distinctive position in the customer's mind that competitors cannot credibly claim. The brand should encode the company's strategic differentiation, not merely describe it. + +**10. Customer Engagement -- How You Foster Compelling Interactions** + +Innovation in the end-to-end experience of being a customer. IKEA's self-service showroom experience. Nike's running community and app ecosystem. Airbnb's host-guest trust mechanisms. + +*Entrepreneurial application:* Map every touchpoint in the customer journey. Engagement innovation often lives in the transitions between touchpoints -- the moments where competitors lose the customer's attention or create friction. + +### The Power of Combination + +Doblin's research found that the most successful innovations integrate five or more types simultaneously. Innovating on product alone rarely creates lasting advantage. Innovating across profit model, process, product, service, and channel creates a system that competitors cannot replicate by copying any single component. + +| Number of Types Combined | Competitive Durability | +|--------------------------|----------------------| +| 1-2 types | Easily copied within 12-18 months | +| 3-4 types | Moderately defensible; requires significant competitor effort | +| 5+ types | Structurally difficult to replicate; creates genuine moats | + +--- + +## Prompts + +**Prompt 1 -- Innovation Audit:** +> "Analyse my business: [describe business model, product, and customer experience]. Map our current innovation across all ten Doblin types. For each type, assess whether we have genuine innovation (differentiation that competitors have not replicated), table-stakes performance (meeting industry norms), or a gap (below industry standard). Identify the three types where investment would create the highest strategic return." + +**Prompt 2 -- Competitor Innovation Mapping:** +> "Map the innovation profile of our top three competitors: [names and descriptions]. For each competitor, identify which of the ten types they have innovated in. Overlay their profiles to find: (a) types where no competitor has innovated (white space), (b) types where one competitor dominates (their moat), and (c) types where competition is intense (Red Ocean zones). Recommend where we should focus our innovation investment." + +**Prompt 3 -- Innovation Combination Design:** +> "Given our current strengths in [list 2-3 innovation types], design a strategy that integrates at least five types of innovation. For each additional type, explain: (1) what the innovation would look like, (2) how it reinforces the types we already do well, and (3) the investment required to achieve it. Prioritise by impact-to-cost ratio." + +--- + +## Use Cases + +**Idea-Stage Founder Designing a New Business** + +A founder planning a meal-kit delivery service recognises that product innovation (better recipes, higher-quality ingredients) is the baseline that every competitor offers. Using the Ten Types framework, she designs across six types: Profit Model (flexible subscription with pay-per-box option), Process (AI-driven demand forecasting to minimise food waste), Product Performance (dietary-restriction personalisation), Service (real-time cooking assistance via chat), Channel (partnerships with apartment complexes for refrigerated locker delivery), and Customer Engagement (a community platform where subscribers share modifications and rate meals). The resulting business model is not a better meal kit; it is a fundamentally different customer relationship that competitors cannot replicate by improving their recipes alone. + +**Growth-Stage SaaS Company Breaking Through a Competitive Ceiling** + +A project management SaaS with $5M ARR competes in a market with dozens of similar products. Feature-by-feature competition has produced parity; no single product capability provides lasting advantage. A Doblin analysis reveals that the company's innovation is concentrated entirely in Type 5 (Product Performance). The strategic response targets three additional types: Network (building an integration marketplace that makes the product a platform), Service (white-glove onboarding for enterprise accounts, converting a commodity product into a premium service experience), and Profit Model (shifting from per-seat pricing to value-based pricing tied to projects completed). Within twelve months, enterprise churn drops by 40% -- not because the product improved, but because the business model around the product became structurally stickier. + +**Early-Traction Fintech Navigating a Regulated Market** + +A fintech startup offering small-business lending realises that product innovation (better interest rates, faster approval) faces structural limits set by regulatory capital requirements. The ten-type analysis redirects innovation investment toward Structure (a partnership model where the startup provides the technology platform while banking partners provide the regulated lending licence), Process (automated credit assessment using alternative data sources), Channel (embedded lending offered at point-of-sale through e-commerce partnerships), and Brand (positioning as the "anti-bank" that treats small businesses with transparency). This multi-type approach circumvents the regulatory constraints that limit pure product innovation. + +--- + +## Anti-Patterns + +**Product Tunnel Vision.** Pouring all innovation resources into product features while ignoring the other nine types. This is the most common and most costly error, particularly in technology companies where engineering culture equates innovation with code. + +**Innovation Type Confusion.** Mislabelling marketing campaigns as "Brand Innovation" or customer support improvements as "Service Innovation." Innovation in the Doblin sense means creating a differentiated position that competitors have not replicated. If every company in your industry offers a similar service level, improving your service is table-stakes investment, not service innovation. + +**Checklist Innovation.** Attempting to innovate across all ten types simultaneously. This dilutes resources and produces shallow innovation everywhere rather than deep innovation in the types that matter most. Five types pursued with depth beats ten types pursued superficially. + +**Ignoring the Configuration Layer.** Startups frequently focus on Offering and Experience while neglecting Configuration types (Profit Model, Network, Structure, Process). Yet Configuration innovations are often the most defensible because they are invisible to customers and difficult for competitors to observe and replicate. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Design for multiple types from inception | It is far easier to build multi-type innovation into a business from the start than to retrofit it later | +| Validation | Test the innovation hypotheses | Each innovation type involves assumptions; validate the riskiest ones first | +| Early Traction | Double down on the types driving traction | Identify which innovation types customers actually value versus which you assumed they would | +| Growth | Add innovation types to deepen moats | Use competitive pressure as the signal for which new types to develop | + +At the idea stage, the Ten Types framework is most powerful as a design tool. Rather than asking "What product should I build?" the founder asks "What combination of innovations would create a business that competitors cannot easily replicate?" This shifts the conversation from features to strategy. + +During growth, competitors begin copying visible innovations (product features, channel strategies). This is the moment to invest in less visible types -- Profit Model, Structure, Process -- that create advantages competitors cannot decode from the outside. + +--- + +## Output Template + +**Target Audience: Strategy Team / Innovation Lead** + +```markdown +# Innovation Architecture: [Company Name] +## Date: [Date] + +### Current Innovation Profile +| # | Innovation Type | Category | Current State | Competitive Position | +|---|----------------|----------|---------------|---------------------| +| 1 | Profit Model | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 2 | Network | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 3 | Structure | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 4 | Process | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 5 | Product Performance | Offering | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 6 | Product System | Offering | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 7 | Service | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 8 | Channel | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 9 | Brand | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 10 | Customer Engagement | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | + +### Innovation Intensity Score +- Types with genuine innovation: [N] / 10 +- Types at parity: [N] / 10 +- Types with gaps: [N] / 10 + +### Priority Innovation Investments +| Priority | Type | What We Will Build | Reinforces Types | Investment | Timeline | +|----------|------|-------------------|-----------------|------------|----------| +| 1 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | +| 2 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | +| 3 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | + +### Competitive Moat Assessment +- Current moat depth: [Shallow/Moderate/Deep] +- Target moat depth (12 months): [Shallow/Moderate/Deep] +- Key vulnerability: [The innovation type where competitors are most likely to surpass us] +``` + +--- + +## Related Skills + +- **[Disruptive Innovation](disruptive-innovation.md)** -- Christensen's theory explains how disruption happens; Doblin's framework provides the toolkit for building innovations across multiple types that are structurally difficult to disrupt. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- Blue Ocean identifies the need for uncontested market space; the Ten Types framework provides ten distinct dimensions along which to create that differentiation. +- **[Product Life Cycle](product-life-cycle.md)** -- As products mature and product-level differentiation erodes, the other nine innovation types become the primary source of competitive advantage. +- **[Business Model Canvas](business-model-canvas.md)** -- The Canvas's nine building blocks map closely to Doblin's ten types, making the Canvas the natural tool for designing how multi-type innovations interconnect operationally. +- **[Four Ps of Marketing](four-ps-marketing.md)** -- Doblin's Experience types (Service, Channel, Brand, Customer Engagement) map directly to the marketing mix, connecting innovation strategy to go-to-market execution. +- **[Creative Shaping and Craft](../creative/creative-shaping-and-craft.md)** -- Provides the creative methodology for moving from innovation type identification to the concrete design and refinement of each innovation element. diff --git a/plugins/foreman/content/skills/frameworks/eisenhower-matrix.md b/plugins/foreman/content/skills/frameworks/eisenhower-matrix.md new file mode 100644 index 0000000..e6b79bd --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/eisenhower-matrix.md @@ -0,0 +1,197 @@ +--- +name: "eisenhower-matrix" +description: "Prioritizes tasks and time allocation using the Eisenhower Matrix, + classifying activities into four quadrants by urgency and importance: Do + (urgent and important), Schedule (important but not urgent), Delegate (urgent + but not important), and Eliminate (neither). Use when overwhelmed by competing + demands, auditing how a founder spends their time, designing delegation + frameworks, building QII-first weekly calendars, or shifting organizational + time allocation from reactive firefighting to strategic work." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - prioritization + - time-management + - productivity + - decision-making +related_skills: + - covey-seven-habits + - eisenhower-matrix + - kaizen-bpr + - balanced-scorecard +author: "Fatih Guner" +--- + +# Eisenhower Matrix + +"What is important is seldom urgent, and what is urgent is seldom important." Dwight D. Eisenhower -- Supreme Allied Commander, thirty-fourth President of the United States, and, by all accounts, a man who managed an extraordinary volume of consequential decisions with unusual composure -- reportedly used this distinction as the organizing principle of his workday. Whether he originated the insight or merely popularized it is debated, but its utility is not. The Eisenhower Matrix (later refined and popularized by Stephen Covey) remains the most widely used prioritization framework in business, and for good reason: it forces a binary distinction that most people instinctively resist. Urgency and importance are different dimensions, and confusing them is the single most common cause of strategic drift in entrepreneurial ventures. + +--- + +## The Framework + +### The 2x2 Matrix + +The matrix classifies every task, decision, or demand on your time into one of four quadrants based on two independent dimensions: urgency (does it demand immediate attention?) and importance (does it contribute to your mission, goals, or values?). + +``` + URGENT NOT URGENT + ┌─────────────────────┬─────────────────────┐ + │ │ │ + IMPORTANT │ QUADRANT I │ QUADRANT II │ + │ DO FIRST │ SCHEDULE │ + │ │ │ + │ Crises │ Strategy │ + │ Deadline-driven │ Relationship- │ + │ projects │ building │ + │ Emergencies │ Planning │ + │ │ Personal growth │ + ├─────────────────────┼─────────────────────┤ + │ │ │ + NOT │ QUADRANT III │ QUADRANT IV │ + IMPORTANT │ DELEGATE │ ELIMINATE │ + │ │ │ + │ Interruptions │ Time-wasters │ + │ Some meetings │ Busywork │ + │ Some emails │ Excessive social │ + │ Others' priorities │ media │ + │ │ Trivia │ + └─────────────────────┴─────────────────────┘ +``` + +### Quadrant Behavior in Detail + +**Quadrant I -- Urgent and Important: DO** +These are genuine crises and hard deadlines. A server outage during a product launch. A key customer threatening to churn. A regulatory deadline. QI tasks demand immediate action and deserve it. The problem is not QI itself but living in QI permanently -- which produces burnout, reactive management, and the sensation that every day is a firefight. + +**Quadrant II -- Important but Not Urgent: SCHEDULE** +This is where strategy lives. Relationship-building. Long-term planning. Product vision work. Team development. Exercise. Reading. These activities rarely scream for attention, which means they are perpetually deferred in favor of whatever is screaming loudest. Covey's central argument -- and the strategic core of the matrix -- is that effective people spend the majority of their discretionary time in QII. The counterintuitive result: investing in QII reduces the volume of QI crises over time, because proactive planning prevents emergencies. + +**Quadrant III -- Urgent but Not Important: DELEGATE** +The deceptive quadrant. These tasks feel important because they are urgent -- a ringing phone, a meeting request, a colleague's "quick question." But they serve someone else's priority, not yours. Entrepreneurs are particularly vulnerable here because early-stage culture rewards responsiveness. The discipline of delegation -- or, more fundamentally, of saying no -- is what separates founders who scale from those who drown. + +**Quadrant IV -- Neither Urgent nor Important: ELIMINATE** +Pure waste. Mindless scrolling. Meetings with no agenda or outcome. Reports nobody reads. The challenge is that QIV activities often masquerade as necessary work or provide short-term psychological relief from the stress of QI. Ruthless elimination of QIV is the easiest productivity gain available. + +### The Quadrant II Principle + +The matrix's deepest insight is not the classification itself but the implication: **most people spend their time in QI and QIII, and most value is created in QII.** The strategic imperative is to systematically shift time allocation toward QII by: + +1. Eliminating QIV entirely +2. Delegating or batching QIII aggressively +3. Reducing QI through proactive QII investment +4. Protecting QII time with the same urgency afforded to QI + +--- + +## Prompts + +**Prompt 1 -- Weekly Prioritization Sort:** +> Here is my task list for this week: [paste task list or describe key activities]. Classify each task into the Eisenhower Matrix quadrants (QI: Do, QII: Schedule, QIII: Delegate, QIV: Eliminate). For each classification, explain your reasoning. Then recommend a daily schedule that protects at least 2 hours of uninterrupted QII time each day. Identify which QIII tasks I should delegate and to whom (given my team is [describe team]). + +**Prompt 2 -- Founder Time Audit:** +> Analyze how I spent my time last week. Here is a rough breakdown: [describe how you spent your time -- meetings, emails, product work, calls, admin, strategy, etc.]. Map each activity to an Eisenhower quadrant. Calculate the percentage of time I spent in each quadrant. Compare this to the ideal distribution for a founder at [my stage]. Identify the three most impactful changes I could make to shift toward QII. + +**Prompt 3 -- Delegation Framework:** +> I struggle with delegation. Here are the tasks I currently handle personally that might belong in QIII: [list tasks]. For each task, assess: Can it be delegated? To whom? What instructions, authority, and check-ins would be needed? What is my resistance to delegating it (control, quality concerns, speed)? Help me build a delegation plan with specific handoff dates and success criteria. + +**Prompt 4 -- QII Strategic Calendar:** +> Help me design a QII-first weekly calendar. My non-negotiable commitments are: [list standing meetings, deadlines, obligations]. My most important QII activities are: [list -- e.g., product strategy, team 1:1s, investor relationships, personal development]. Design a weekly template that blocks QII time before QIII fills the gaps. Include specific time blocks, daily themes if appropriate, and a system for protecting QII time from urgency creep. + +--- + +## Use Cases + +**Validation-Stage Solo Founder Drowning in Operational Tasks** +A solo founder building an MVP finds herself spending 70% of her time answering customer support emails (QIII), 20% on urgent bug fixes (QI), and 10% on actual product development (QII). The Eisenhower audit reveals that customer support -- while responsive and well-intentioned -- serves individual requests at the expense of building the product that would serve all customers. She implements three changes: a self-service FAQ that reduces support volume by 40%, a twice-daily email batching schedule, and a morning block of three protected hours for product work. Within a month, she has reclaimed 15 hours per week for QII. + +**Growth-Stage CEO Trapped in Meeting Culture** +A Series A CEO reviews his calendar and discovers 32 hours of meetings per week. The Eisenhower sort reveals: 8 hours are QI (board prep, customer escalations, hiring decisions), 6 hours are QII (strategic 1:1s with direct reports, investor relationship maintenance), 14 hours are QIII (status updates, informational meetings he attends but does not lead), and 4 hours are QIV (recurring meetings with no clear purpose). He eliminates the 4 QIV hours immediately, converts 8 of the QIII hours into asynchronous updates (Loom videos, written status reports), and delegates attendance at the remaining 6 QIII meetings to his chief of staff. The result: 18 hours reclaimed, with 6 redirected to QII strategic work. + +--- + +## Anti-Patterns + +1. **Treating everything as QI.** Founders who classify every task as urgent and important have not done the work of distinguishing between the two dimensions. If everything is QI, nothing is prioritized, and the matrix provides no value. The discipline is in the sorting, not in the framework itself. + +2. **Using the matrix once and filing it away.** The Eisenhower Matrix is a daily practice, not a quarterly exercise. Priorities shift constantly, and the matrix must be applied continuously -- ideally as a daily planning ritual -- to prevent QIII and QIV from colonizing the calendar. + +3. **Delegating without context or authority.** Moving tasks to QIII (delegate) requires actually delegating them, which means providing the necessary context, decision-making authority, and feedback mechanisms. Simply labeling something "delegable" and continuing to do it yourself defeats the purpose. + +4. **Confusing "not urgent" with "not now."** QII tasks are not urgent, but they are the most important tasks on the list. Treating "not urgent" as "defer indefinitely" ensures that QII work never happens. The framework requires active scheduling of QII work, not passive acknowledgment of its existence. + +5. **Ignoring the emotional pull of QIII.** Answering emails, attending meetings, and responding to requests feels productive. The dopamine hit of clearing an inbox is real. Founders must recognize that QIII activity provides psychological comfort at strategic cost. The discomfort of saying no to QIII is the price of QII progress. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal clarity | At the idea stage, the entrepreneur IS the company. The matrix serves as a personal discipline tool. QII activities: customer discovery, market research, building relationships with potential co-founders. The primary enemy is QIV disguised as "research." | +| Validation | Ruthless focus on experiments | QII narrows to activities that directly test the core hypothesis: customer interviews, prototype building, metrics design. QIII expands dangerously as advisors, accelerators, and networking events compete for time. | +| Early Traction | First delegation decisions | The team is growing, making QIII delegation possible for the first time. The founder's QII shifts toward hiring, culture-building, and system design -- activities that feel less "productive" than shipping features but are more valuable. | +| Growth | Organizational QII | The matrix expands from personal to organizational. Leadership must ensure the entire company invests in QII -- strategic planning, capability building, process improvement -- rather than running entirely in reactive mode. | +| Scale | Institutional time management | QII becomes the CEO's primary job: vision, culture, board management, strategic partnerships. Virtually all QI and QIII should be delegated. The CEO who is still fighting fires at scale has failed to build the organization. | + +--- + +## Output Template + +```markdown +# Weekly Eisenhower Matrix + +**Name:** [Your name] +**Week of:** [Date] +**Stage:** [Company stage] + +## Task Classification + +| Task | Quadrant | Action | Time Estimate | +|------|----------|--------|---------------| +| [Task] | QI - Do | [Immediate action] | [Hours] | +| [Task] | QII - Schedule | [When blocked] | [Hours] | +| [Task] | QIII - Delegate | [To whom] | [Hours saved] | +| [Task] | QIV - Eliminate | [Remove] | [Hours saved] | + +## Time Distribution + +| Quadrant | Current % | Target % | Gap | +|----------|----------|----------|-----| +| QI (Do) | [%] | 20-25% | [+/-] | +| QII (Schedule) | [%] | 40-50% | [+/-] | +| QIII (Delegate) | [%] | 15-20% | [+/-] | +| QIV (Eliminate) | [%] | 0-5% | [+/-] | + +## Protected QII Blocks This Week +- Monday: [Time] -- [QII Activity] +- Tuesday: [Time] -- [QII Activity] +- Wednesday: [Time] -- [QII Activity] +- Thursday: [Time] -- [QII Activity] +- Friday: [Time] -- [QII Activity] + +## Delegation Actions +- [Task] → [Person] by [Date] +- [Task] → [Person] by [Date] + +## QIV Eliminated +- [Activity removed and why] +``` + +--- + +## Related Skills + +- **[Covey's Seven Habits](covey-seven-habits.md)** -- Covey popularized the Eisenhower Matrix as Habit 3 ("Put First Things First") and embedded it in a broader framework of personal effectiveness that provides the character foundation for consistent use. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Continuous improvement is a Quadrant II activity by definition: important but never urgent, making the Eisenhower Matrix essential for protecting time for Kaizen practices. +- **[Balanced Scorecard](balanced-scorecard.md)** -- Extends the Eisenhower principle from individual time management to company-wide strategic focus, ensuring organizational attention is distributed across all four perspectives. +- **[SMART Goals](smart-goals.md)** -- QII activities need specific, measurable goals to maintain their priority against the constant pull of urgent but unimportant demands. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- Provides leadership-specific strategies for protecting strategic focus time and managing the competing demands that pull leaders away from QII work. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- The QIII delegation quadrant requires genuine delegation skills to execute effectively, including providing context, authority, and accountability. diff --git a/plugins/foreman/content/skills/frameworks/emotional-intelligence.md b/plugins/foreman/content/skills/frameworks/emotional-intelligence.md new file mode 100644 index 0000000..6500de4 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/emotional-intelligence.md @@ -0,0 +1,195 @@ +--- +name: "emotional-intelligence" +description: "Assesses and develops leadership emotional intelligence using Goleman's five-domain EQ framework: Self-Awareness, Self-Regulation, Motivation, Empathy, and Social Skill. Diagnoses interpersonal conflicts, evaluates team EQ profiles, and builds development plans for emotional competencies. Use when resolving co-founder tensions, preparing for high-stakes investor meetings, scaling team culture, diagnosing declining employee engagement, or developing the relational leadership skills that differentiate outstanding from average leaders." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - self-awareness + - empathy + - team-dynamics + - interpersonal-skills +related_skills: + - thinking-fast-and-slow + - psychological-safety + - johari-window + - myers-briggs-type-indicator +author: "Fatih Guner" +--- + +# Emotional Intelligence + +Ninety percent of the difference between outstanding and average leaders is attributable not to cognitive ability but to emotional competencies. That finding, drawn from research across 188 companies by Daniel Goleman and reported in the Harvard Business Review, upended a century of assumptions about what makes leaders effective. IQ and technical expertise, Goleman demonstrated, are threshold capabilities -- necessary for entry but insufficient for distinction. The differentiator is emotional intelligence: the capacity to recognise, understand, manage, and effectively deploy emotions in oneself and others. For entrepreneurs, who operate in environments saturated with uncertainty, conflict, and high-pressure interpersonal dynamics, EQ is not a soft supplement to strategy. It is the substrate on which every relationship -- with co-founders, investors, employees, and customers -- either flourishes or fractures. + +--- + +## The Framework + +Goleman's model of emotional intelligence comprises five domains, each containing specific learnable competencies. Unlike IQ, which remains relatively stable across a lifetime, EQ is developable. The brain's emotional circuitry exhibits significant neuroplasticity well into adulthood, meaning these competencies respond to deliberate practice. + +### The Five Domains + +**1. Self-Awareness** + +The foundation upon which all other domains depend. Self-awareness is the ability to recognise one's own emotional states, understand their triggers, and assess their impact on thought and behaviour. Entrepreneurs with high self-awareness can distinguish between gut instinct grounded in pattern recognition and gut instinct distorted by anxiety, ego, or fatigue. + +Key competencies: +- Emotional self-awareness -- recognising emotions as they arise +- Accurate self-assessment -- knowing one's strengths and limitations +- Self-confidence -- grounded certainty about one's capabilities and values + +**2. Self-Regulation** + +The ability to manage disruptive emotions rather than being managed by them. Self-regulation does not mean suppression -- it means choosing how and when to express emotions constructively. Founders who self-regulate can absorb bad news without spiralling, receive criticism without retaliating, and maintain composure in negotiations where losing emotional control means losing leverage. + +Key competencies: +- Self-control -- keeping disruptive impulses in check +- Trustworthiness -- maintaining integrity and consistency +- Adaptability -- flexibility in handling change +- Innovation openness -- comfort with novel ideas and approaches + +**3. Motivation** + +Goleman distinguishes between extrinsic motivation (money, status, external validation) and intrinsic motivation (achievement drive, commitment to goals beyond the self, optimism in the face of setbacks). The most effective leaders are driven by something beyond personal gain, and this orientation is perceptible to the people they lead. Teams can detect performative purpose from genuine commitment with remarkable accuracy. + +Key competencies: +- Achievement drive -- striving to improve against a standard of excellence +- Commitment -- aligning with the goals of the organisation +- Initiative -- readiness to act on opportunities +- Optimism -- persistence in pursuing goals despite obstacles + +**4. Empathy** + +The ability to sense what others are feeling without them needing to articulate it. Empathy in a business context is not therapeutic -- it is informational. A founder with strong empathy reads the room: senses investor scepticism before it is voiced, detects employee disengagement before it becomes attrition, and anticipates customer frustration before it becomes churn. + +Key competencies: +- Understanding others -- sensing feelings and perspectives +- Developing others -- bolstering others' abilities +- Service orientation -- anticipating, recognising, and meeting needs +- Leveraging diversity -- cultivating opportunity through diverse perspectives +- Political awareness -- reading group emotional currents and power relationships + +**5. Social Skill** + +The application layer. Social skill is the ability to move people in desired directions -- to persuade, lead, negotiate, build bonds, and catalyse collaboration. It depends on all four preceding domains: one cannot influence others effectively without understanding oneself (self-awareness), managing one's own reactions (self-regulation), bringing genuine energy (motivation), and reading the other party accurately (empathy). + +Key competencies: +- Influence -- wielding effective persuasion tactics +- Communication -- listening openly and sending convincing messages +- Conflict management -- negotiating and resolving disagreements +- Leadership -- inspiring and guiding individuals and groups +- Collaboration -- working with others toward shared goals + +### The EQ-Performance Link + +Goleman's research across multiple industries found that EQ competencies accounted for 67% of the abilities necessary for superior performance in leadership roles -- and mattered twice as much as technical skill and IQ combined. The effect is non-linear: marginal improvements in EQ at the leadership level produce disproportionate improvements in organisational outcomes because leaders set the emotional tone for entire teams. + +--- + +## Prompts + +**Prompt 1 -- Personal EQ Assessment:** +> Based on the following self-description and recent interactions with my team, assess my likely strengths and development areas across Goleman's five EQ domains (self-awareness, self-regulation, motivation, empathy, social skill). Self-description: [describe your leadership style, recent conflicts, feedback received]. For each domain, rate my apparent level (developing / competent / strong) and suggest one specific practice I can begin this week to strengthen my weakest area. + +**Prompt 2 -- Conflict Diagnosis:** +> Analyse this interpersonal conflict through the lens of emotional intelligence: [describe situation -- parties involved, what happened, emotional reactions, current state]. Identify which EQ competencies each party is demonstrating or lacking. Recommend a resolution approach that addresses the emotional dynamics, not just the surface-level disagreement. Script the opening 3 sentences I should use to re-engage the other party. + +**Prompt 3 -- Team EQ Audit:** +> Evaluate the emotional intelligence profile of my leadership team based on these behavioural observations: [describe each team member's typical reactions to pressure, conflict, feedback, and collaboration]. Map each person to their likely EQ strengths and gaps. Identify the team-level blind spots (e.g., "the team is collectively strong on achievement drive but weak on empathy") and recommend team practices or rituals that would address these gaps. + +**Prompt 4 -- Investor Meeting Preparation:** +> I have a [funding round] meeting with [investor name/type] tomorrow. Based on what I know about them: [any background]. Help me prepare an emotionally intelligent approach: (a) likely emotional dynamics in the room, (b) how to read and respond to scepticism signals, (c) how to manage my own anxiety without suppressing authentic enthusiasm, and (d) how to close the meeting in a way that builds relationship regardless of the outcome. + +--- + +## Use Cases + +**Co-founder conflict at early traction** + +Two co-founders of a health-tech startup have escalating disagreements about product direction. The technical co-founder pushes for feature completeness before launch; the commercial co-founder wants to ship a minimum viable product immediately. Both frame the disagreement as strategic, but the underlying dynamic is emotional: the CTO fears public failure (self-regulation deficit under pressure), while the CEO fears missing the market window (anxiety masquerading as urgency). Applying Goleman's framework, they engage a coach who helps each founder articulate the emotion beneath the position. Once acknowledged, the technical co-founder agrees to a phased launch with clear quality thresholds, and the commercial co-founder agrees to delay by three weeks. The strategic compromise was always available -- the emotional blockage was what prevented them from finding it. + +**Scaling a team from 15 to 60 at growth stage** + +A fintech founder who personally hired and managed the first 15 employees struggles as the company scales to 60. She notices declining engagement, increasing turnover among mid-level managers, and a sense that the culture is "diluting." Diagnosis through the EQ lens reveals that her leadership style -- which worked brilliantly at 15 people through direct empathy and personal connection -- does not scale without structural support. She lacks the social skill competency of "developing others" at the management layer. The intervention involves training her direct reports in EQ competencies, establishing regular one-on-one rituals that cascade empathic leadership through layers, and creating feedback mechanisms that give her visibility into emotional dynamics she can no longer observe directly. + +--- + +## Anti-Patterns + +**1. Treating EQ as manipulation technology.** The most corrosive misapplication of emotional intelligence is using it to manage others' emotions for personal advantage while bypassing genuine self-awareness. This produces charismatic but ultimately untrustworthy leaders. Goleman's framework is predicated on authenticity -- the domains build on each other, and social skill without self-awareness is manipulation. + +**2. Confusing empathy with agreement.** Empathy means understanding another person's emotional state and perspective. It does not mean endorsing their position or abandoning one's own. Founders sometimes conflate the two, either avoiding necessary confrontations because they empathise with the other party's discomfort, or dismissing empathy entirely because they equate it with weakness. Strong empathy enables harder conversations, not softer ones. + +**3. Using EQ language to pathologise disagreement.** Labelling a colleague as "emotionally unintelligent" because they disagree forcefully is a form of intellectual dishonesty. Passionate advocacy is not an EQ deficit. The question is whether the person can modulate their approach based on context, not whether they suppress strong feelings entirely. + +**4. Neglecting that EQ is culturally mediated.** The expression and interpretation of emotions varies significantly across cultures. What reads as confident self-assurance in one cultural context may register as arrogance in another. Founders building global teams must calibrate their EQ practice to cultural norms rather than assuming a single standard. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder dynamics, early hires | EQ is exercised directly and personally; the founder IS the culture | +| Growth | Management layer, culture scaling | EQ must be systematised -- built into hiring criteria, management training, and feedback loops | +| Scale | Board relationships, M&A, crisis leadership | EQ operates at institutional level; the founder must influence through others and manage stakeholders with competing emotional agendas | + +At early traction, the founder's personal EQ is the company's EQ. Every hiring decision, every customer interaction, every investor conversation is coloured by the founder's emotional competencies. The leverage point is self-awareness: a founder who understands their own emotional patterns can consciously compensate for them. + +At growth, the challenge transforms. The founder can no longer personally set the emotional tone for every team. EQ must become organisational: embedded in hiring criteria (screening for empathy and self-regulation), management practices (regular feedback, active listening protocols), and cultural rituals (how the company handles failure, celebrates success, resolves conflict). + +At scale, emotional intelligence becomes a governance capability. Board dynamics, investor relations, regulatory negotiations, and crisis communications all demand the highest order of Goleman's social skill domain -- the ability to manage complex multi-party emotional dynamics where the stakes are existential. + +--- + +## Output Template + +```markdown +# Emotional Intelligence Assessment -- [Team/Leader Name] + +**Prepared for:** [Team / Individual] +**Date:** [Date] +**Assessment context:** [Trigger -- e.g., team conflict, scaling challenges, leadership development] + +## Individual EQ Profile + +| Domain | Current Level | Key Evidence | Development Priority | +|--------|--------------|--------------|---------------------| +| Self-Awareness | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Self-Regulation | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Motivation | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Empathy | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Social Skill | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | + +## Team-Level Patterns +- **Collective strength:** [Domain where the team is strongest] +- **Collective blind spot:** [Domain where the team is weakest] +- **Highest-impact intervention:** [One practice that would shift the team dynamic] + +## 30-Day Development Plan +1. **Week 1-2:** [Specific action targeting highest-priority domain] +2. **Week 3-4:** [Follow-up action and reflection practice] + +## Relationship Map +[Key relationships that require EQ attention, with specific approach for each] + +| Relationship | Current Dynamic | EQ Lever | Recommended Approach | +|-------------|----------------|----------|---------------------| +| [Person/Group] | [Description] | [Which EQ domain] | [Specific action] | +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- Kahneman's System 1 is driven by emotional processing; EQ provides the self-awareness to recognise when fast thinking is emotionally compromised. +- **[Psychological Safety](psychological-safety.md)** -- Edmondson's framework describes the team-level conditions that require leaders with high EQ to establish and maintain. +- **[Johari Window](johari-window.md)** -- The Johari model operationalises the self-awareness domain of EQ by mapping known and unknown aspects of self and others. +- **[Radical Candor](radical-candor.md)** -- Scott's "care personally, challenge directly" formula requires high EQ in both empathy (caring) and social skill (challenging) to execute without damage. +- **[Stoic Emotional Mastery](../stoic/stoic-emotional-mastery.md)** -- Provides ancient practical techniques for the self-regulation domain of EQ, teaching how to observe and manage emotional responses rather than be controlled by them. +- **[Reading People](../people/reading-people.md)** -- Extends the empathy domain into practical observation techniques for reading emotional states, intentions, and unspoken dynamics in professional interactions. diff --git a/plugins/foreman/content/skills/frameworks/flow-state.md b/plugins/foreman/content/skills/frameworks/flow-state.md new file mode 100644 index 0000000..ce5c816 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/flow-state.md @@ -0,0 +1,227 @@ +--- +name: "flow-state" +description: "Optimizes individual and team productivity using Csikszentmihalyi's flow state framework, covering the conditions for flow (clear goals, immediate feedback, challenge-skill balance), the four-stage flow cycle, and organizational flow design. Use when auditing personal or team focus time, diagnosing productivity loss from meeting overload and context-switching, designing flow-protective work schedules, calibrating challenge-skill balance on projects, or building recovery protocols to prevent founder burnout." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth +tags: + - productivity + - creativity + - peak-performance + - focus + - engagement +related_skills: + - growth-mindset + - thinking-fast-and-slow + - psychological-safety + - emotional-intelligence +author: "Fatih Guner" +--- + +# Flow State + +Three hours vanish. The code compiles, the design coheres, the strategy document assembles itself in what feels like a single unbroken motion. The noise of Slack notifications, investor emails, and team requests has receded to a frequency below perception. When the trance breaks -- a knock on the door, a calendar alert -- there is a disorienting moment of re-entry, like surfacing from deep water. The work product from those three hours exceeds what the previous three days of fragmented effort had yielded. That experience, reported with striking consistency across programmers, designers, writers, athletes, surgeons, and musicians, is what Mihaly Csikszentmihalyi named "flow." His four decades of research at the University of Chicago established that flow is not a mystical state available only to the gifted but a describable, reproducible psychological condition with specific preconditions and measurable effects. For entrepreneurs, who operate in environments structurally hostile to deep concentration, understanding flow is understanding where their highest-value output actually comes from -- and why most of their working hours produce so little of it. + +--- + +## The Framework + +### The Conditions for Flow + +Csikszentmihalyi's research identified a consistent set of conditions that precede the flow state. No single condition is sufficient; flow emerges from their convergence. + +**1. Clear goals.** The person knows what they are trying to accomplish at each moment. Not the long-term goal ("build a successful company") but the immediate task goal ("design the database schema for the user authentication module"). Ambiguity is the enemy of flow. + +**2. Immediate feedback.** The person receives continuous information about whether their actions are moving toward or away from the goal. A programmer sees code compile or fail. A writer sees sentences that work or do not. A salesperson reads the prospect's engagement in real time. Without feedback, there is no basis for the dynamic adjustment that characterises flow. + +**3. Challenge-skill balance.** This is the critical condition. The task must be sufficiently challenging to demand full engagement but not so challenging as to produce anxiety. If challenge exceeds skill, the result is stress. If skill exceeds challenge, the result is boredom. Flow lives in the narrow channel between the two. + +``` + High │ ANXIETY │ + │ │ + Challenge│ ┌───────────│ + │ │ FLOW │ + │ │ CHANNEL │ + │──────────────┘ │ + │ │ + │ BOREDOM │ + Low └──────────────────────────┘ + Low Skill High +``` + +**4. Concentration on the task at hand.** Flow requires undivided attention. Csikszentmihalyi's research found that flow is virtually impossible during multitasking. The brain's attentional resources must be fully absorbed by a single activity. + +**5. Sense of control.** The person feels capable of influencing the outcome. Not guaranteed success, but genuine agency. Learned helplessness -- the belief that one's actions do not affect outcomes -- precludes flow. + +**6. Loss of self-consciousness.** During flow, the inner critic falls silent. The person is no longer evaluating themselves ("Am I doing this well?") but is fully merged with the activity. Self-consciousness returns afterward, often as a heightened sense of accomplishment. + +**7. Altered perception of time.** Hours feel like minutes (most commonly), or occasionally moments expand. The subjective experience of time disconnects from clock time. + +### The Neurochemistry of Flow + +Subsequent research has mapped flow to a specific neurochemical cascade. The brain releases a cocktail of performance-enhancing chemicals: + +- **Norepinephrine** -- tightens focus and increases pattern recognition +- **Dopamine** -- enhances creative thinking and rewards engagement +- **Endorphins** -- reduces pain and increases pleasure +- **Anandamide** -- promotes lateral thinking and novel connections +- **Serotonin** -- produces the afterglow of well-being that follows flow + +The practical implication: flow produces both the best work and the best subjective experience of working. It is the rare alignment of peak performance with peak satisfaction. + +### The Flow Cycle + +Flow is not a binary state but a cycle with four stages: + +**Stage 1 -- Struggle.** The initial loading phase. The brain takes in information, encounters the challenge, and experiences frustration or tension. This stage feels unpleasant and is where most people quit. It is, however, a necessary precursor. + +**Stage 2 -- Release.** The person steps back from the problem. A walk, a shower, a shift in activity. The conscious mind disengages, allowing the subconscious to process. Forced effort at this stage is counterproductive. + +**Stage 3 -- Flow.** The state itself. Full absorption, effortless effort, peak performance. Duration varies from minutes to hours. + +**Stage 4 -- Recovery.** Flow is neurochemically expensive. The brain needs rest to replenish the neurotransmitters depleted during the state. Attempting to force back into flow without recovery produces diminishing returns and eventual burnout. + +### Organisational Flow + +Csikszentmihalyi and subsequent researchers (notably Steven Kotler) have explored how organisations can create conditions for collective flow. The key organisational factors are: + +- Shared, clear goals at the team level +- Rapid feedback loops (short sprint cycles, real-time dashboards) +- Equal participation and communication +- Familiarity -- team members who know each other's capabilities +- Psychological safety -- the willingness to take creative risks +- Sense of control -- autonomy over how work is executed +- Environment -- both physical (minimal interruptions) and temporal (protected focus time) + +--- + +## Prompts + +**Prompt 1 -- Personal Flow Audit:** +> Analyse my typical work week for flow conditions. Here is how I spend my time: [describe daily schedule, types of tasks, meeting load, interruption frequency, environment]. Identify the activities most likely to produce flow, the structural barriers preventing flow (meeting fragmentation, context-switching, unclear goals), and specific calendar and environment changes that would increase my flow time. Be specific about timing, duration, and what to eliminate or protect. + +**Prompt 2 -- Challenge-Skill Calibration:** +> I am working on [describe project or task] and I am experiencing [anxiety / boredom / sporadic engagement]. Using Csikszentmihalyi's challenge-skill balance model, diagnose the mismatch and recommend adjustments. If anxious: what skills should I develop or what support should I seek to raise my skill level? If bored: how can I increase the challenge or complexity to re-enter the flow channel? If sporadic: what environmental or structural factors are disrupting the conditions for flow? + +**Prompt 3 -- Team Flow Architecture:** +> Design a work structure for my team of [size] that maximises collective flow time. Current pain points: [describe -- e.g., too many meetings, unclear priorities, constant Slack interruptions, no protected focus time]. Consider: meeting consolidation, communication protocols (sync vs. async), goal-setting cadence, feedback loop design, and physical/digital environment. Produce a specific weekly schedule template that protects flow blocks while maintaining necessary collaboration. + +**Prompt 4 -- Flow Recovery Protocol:** +> I have been pushing hard for [timeframe] without adequate recovery and am experiencing [symptoms: diminished creativity, irritability, inability to focus, reduced output quality]. Design a recovery protocol based on the flow cycle's recovery stage. Include: immediate actions (today), short-term recovery plan (this week), and structural changes to prevent future recovery debt. Be realistic about what an early-stage founder can actually implement. + +**Prompt 5 -- Founder Role Design for Flow:** +> My current role as founder/CEO involves [list responsibilities]. Identify which responsibilities are flow-compatible (deep, focused, skill-stretching) and which are flow-incompatible (fragmented, reactive, low-challenge). Recommend a role redesign that maximises my time on flow-compatible work while ensuring flow-incompatible work is either delegated, batched, or eliminated. Include the business case for why protecting founder flow time is an investment, not an indulgence. + +--- + +## Use Cases + +**Idea-stage solo founder building an MVP** + +A technical founder building a product alone finds that her most productive coding sessions occur between 10 PM and 2 AM -- after the day's distractions have ceased. Analysis through the flow lens reveals that her daytime hours are fragmented by investor outreach, administrative tasks, and social media management, none of which produce flow for her but all of which produce enough context-switching to prevent it. The intervention is structural: she time-blocks her mornings (9 AM to 1 PM) as zero-meeting, zero-notification deep work, moves investor and admin tasks to afternoon batches, and eliminates social media from her phone entirely during deep work blocks. Within two weeks, her daytime coding output exceeds what she previously achieved in late-night sessions, and she regains sustainable sleep patterns. The total code committed per week increases by approximately 40%. + +**Early-traction product team losing velocity** + +An eight-person product team that was highly productive at five people has stalled. Sprint velocity has dropped 30% despite adding three engineers. Diagnosis through the flow framework reveals multiple flow-killers: daily standups that break morning focus, a Slack culture of immediate response expectation, unclear sprint goals (too many "stretch items"), and an open-plan office with no quiet zones. The team implements flow-protective measures: standups move to end-of-day async updates, Slack response expectations shift from "immediate" to "within 4 hours" for non-urgent items, sprint goals are reduced to three unambiguous commitments, and "flow mornings" are established where interruptions are prohibited before noon. Velocity recovers within two sprints and surpasses the pre-expansion baseline within four. + +**Growth-stage founder experiencing burnout** + +A CEO at a 50-person company has not experienced flow in months. Every hour is consumed by meetings, Slack, email, and firefighting. The CEO reports feeling "busy but useless" -- a textbook description of a high-activity, zero-flow work pattern. Analysis reveals that the CEO's role has drifted entirely into coordination and communication, with no time allocated to the strategic thinking and creative problem-solving that originally made her effective. The intervention involves radical calendar restructuring: two full days per week are declared "maker days" with no meetings, an executive assistant takes over email triage, and the CEO identifies the specific activities (strategic planning, customer research, product vision) that represent her highest-value flow work. The first maker day produces a strategic insight that the previous month of meetings had failed to generate. + +--- + +## Anti-Patterns + +**1. Romanticising flow as the only valuable work mode.** Not all productive work occurs in flow. Administrative tasks, relationship maintenance, rapid communication, and routine decision-making are necessary, valuable, and intrinsically low-flow. The goal is not to achieve constant flow but to protect sufficient flow time for the work that requires it. + +**2. Mistaking hyperfocus for flow.** Spending six hours answering emails without looking up is not flow -- it is compulsive task-switching within a single application. Flow requires challenge-skill balance and clear goals. Hyperfocus on low-challenge, reactive tasks produces neither the performance benefits nor the satisfaction of genuine flow. + +**3. Forcing flow through stimulants or sleep deprivation.** Caffeine, nootropics, and sleep debt can produce states that feel like heightened focus but lack the neurochemical signature of genuine flow and carry significant recovery costs. The flow cycle includes a recovery stage for a reason. Skipping recovery to maximise output-per-hour produces a net negative over any meaningful time horizon. + +**4. Using flow as an excuse for unavailability.** A founder who is perpetually "in flow" and therefore unreachable is not optimising productivity -- they are neglecting leadership. Flow is a tool to be deployed strategically, not a lifestyle that exempts the founder from the relational and communicative work that building a company requires. + +**5. Ignoring that flow conditions differ by person.** Csikszentmihalyi's conditions are universal, but their specific manifestation is individual. Some people flow best in silence; others with background music. Some flow in the morning; others late at night. Imposing a single "flow schedule" on a diverse team ignores individual variation and reduces aggregate flow rather than increasing it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder flow for creative and technical work | The founder has maximum autonomy to design their schedule for flow; the constraint is self-discipline, not organisational structure | +| Validation | Balancing flow (building) with necessarily fragmented work (customer discovery) | The challenge is accepting that customer conversations, while essential, are not flow activities, and designing the day to accommodate both | +| Early Traction | Protecting team flow while building coordination mechanisms | The first management challenge: meetings and processes necessary for coordination inherently threaten the flow conditions that produce the team's best work | +| Growth | Organisational flow design | Flow protection must become architectural -- embedded in calendaring systems, communication norms, office layout, and management training | + +At the idea stage, the founder is typically working alone or with one or two collaborators. The flow challenge is purely personal: designing a schedule and environment that supports sustained focus. This is the stage with the highest potential flow ratio -- the fewest meetings, the least email, the most uninterrupted building time. Founders who squander this window on scattered activity lose the advantage of the stage. + +At validation, a fundamental tension emerges. Customer discovery requires the antithesis of flow: interruption, active listening, rapid context-switching between different customer conversations, and comfort with ambiguity. The discipline is compartmentalisation: dedicated flow blocks for building and dedicated fragmented blocks for discovery, with a hard boundary between them. + +At early traction and growth, the challenge becomes organisational. Every meeting added is a potential flow-killer for someone. Every communication norm established (immediate Slack response, open-door policy, always-on availability) erodes the conditions for deep work. Founders who understand the flow framework make architectural choices that protect their team's capacity for concentration -- recognising that this protection is itself a form of leadership. + +--- + +## Output Template + +```markdown +# Flow Optimisation Plan -- [Individual/Team Name] + +**Prepared for:** Founder / Team Lead +**Date:** [Date] +**Scope:** [Individual schedule / Team structure] + +## Current Flow Assessment + +| Metric | Current | Target | +|--------|---------|--------| +| Estimated weekly flow hours | [Hours] | [Hours] | +| Average uninterrupted block duration | [Minutes] | [Minutes] | +| Meetings per week | [Count] | [Count] | +| Context switches per day | [Estimate] | [Target] | + +## Flow-Compatible Activities +[Activities that match challenge-skill balance and warrant flow protection] +1. [Activity] -- Current weekly allocation: [hours] -- Optimal: [hours] +2. [Activity] -- Current weekly allocation: [hours] -- Optimal: [hours] + +## Flow Barriers Identified + +| Barrier | Severity | Fix | Implementation Date | +|---------|----------|-----|-------------------| +| [e.g., mid-morning meetings] | [High/Med/Low] | [Move to afternoon batch] | [Date] | +| [e.g., Slack always-on culture] | [High/Med/Low] | [Async-first protocol] | [Date] | + +## Weekly Schedule Template + +| Time Block | Monday | Tuesday | Wednesday | Thursday | Friday | +|-----------|--------|---------|-----------|----------|--------| +| 9-12 | [Flow/Meetings/Admin] | ... | ... | ... | ... | +| 12-1 | [Break] | ... | ... | ... | ... | +| 1-3 | [Flow/Meetings/Admin] | ... | ... | ... | ... | +| 3-5 | [Flow/Meetings/Admin] | ... | ... | ... | ... | + +## Recovery Protocol +- **Daily:** [Specific recovery practice -- e.g., 20-min walk after deep work] +- **Weekly:** [Specific recovery practice -- e.g., one day with no deep work] +- **Quarterly:** [Specific recovery practice -- e.g., extended time off] + +## Measurement +- Track flow hours weekly using [method] +- Review and adjust plan on [date] +``` + +--- + +## Related Skills + +- **[Growth Mindset](growth-mindset.md)** -- Dweck's framework provides the belief system that sustains flow practice: the conviction that skill develops through challenge, which keeps the challenge-skill balance productive rather than threatening. +- **[Eisenhower Matrix](eisenhower-matrix.md)** -- Flow-compatible work lives in Quadrant II (important but not urgent); the Eisenhower Matrix provides the prioritization discipline needed to protect flow time from reactive demands. +- **[Psychological Safety](psychological-safety.md)** -- Organisational flow requires psychological safety; team members who fear judgment cannot enter the self-consciousness-free state that flow demands. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Self-awareness (recognising one's own flow triggers and barriers) and self-regulation (protecting flow time against the pull of reactive work) are EQ competencies that enable flow practice. +- **[Creative Flow and Inspiration](../creative/creative-flow-and-inspiration.md)** -- Applies Csikszentmihalyi's flow conditions specifically to creative work, addressing the unique challenges of sustaining flow during artistic and design-intensive tasks. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- Provides the leadership-level scheduling and boundary-setting practices that protect flow time for both the leader and their teams. diff --git a/plugins/foreman/content/skills/frameworks/four-ps-marketing.md b/plugins/foreman/content/skills/frameworks/four-ps-marketing.md new file mode 100644 index 0000000..6e53737 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/four-ps-marketing.md @@ -0,0 +1,178 @@ +--- +name: "four-ps-marketing" +description: "Designs and audits marketing strategy using McCarthy and Kotler's + Four Ps framework: Product, Price, Place, and Promotion. Evaluates coherence + across all four marketing mix elements to identify misalignments that + undermine go-to-market effectiveness. Use when launching a new product, + diagnosing why conversion rates are low despite strong product-market fit, + redesigning pricing strategy, evaluating distribution channel options, + planning go-to-market campaigns, or expanding from direct-to-consumer into + retail." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - marketing + - product-market-fit + - pricing + - go-to-market + - positioning +related_skills: + - blue-ocean-strategy + - business-model-canvas +author: "Fatih Guner" +--- + +# The Four Ps of Marketing + +Product, Price, Place, Promotion. Four words that built trillion-dollar brands and bankrupted companies that ignored even one of them. E. Jerome McCarthy distilled the entirety of marketing strategy into this deceptively simple taxonomy in 1960, and six decades later it remains the skeleton key to market entry. The framework endures not because it is sophisticated -- it is not -- but because it forces founders to confront four decisions they cannot delegate, delay, or decouple. Get all four right and the market opens. Get one wrong and you discover, expensively, that marketing is a system, not a checklist. + +--- + +## The Framework + +The Marketing Mix operates as four interdependent levers. Adjusting one necessarily affects the others. A premium product sold through discount channels erodes its own positioning. A low price paired with exclusive distribution creates cognitive dissonance. The discipline lies in coherence. + +| Lever | Core Question | What It Encompasses | Common Founder Blind Spot | +|-------|--------------|---------------------|--------------------------| +| **Product** | What exactly are you selling? | Features, quality, design, branding, packaging, warranties, lifecycle | Over-engineering features nobody asked for; building for yourself, not the customer | +| **Price** | What is it worth -- and to whom? | List price, discounts, payment terms, financing, perceived value, price elasticity | Defaulting to cost-plus pricing; fear of charging what the market will bear | +| **Place** | How does the customer get it? | Channels, distribution, logistics, market coverage, online vs. physical, partnerships | Assuming "if we build it, they will come"; neglecting channel economics | +| **Promotion** | How do they know it exists? | Advertising, PR, content marketing, sales force, social media, partnerships, events | Spending on awareness before achieving product-market fit | + +### The Interdependence Principle + +The four Ps are not a menu from which to select favorites. They constitute a system. McCarthy's original insight -- later amplified by Philip Kotler -- was that marketing failures almost always stem from misalignment between elements rather than weakness in any single one. + +Consider a SaaS startup pricing at enterprise levels ($50K+ annual contracts) but relying exclusively on inbound content marketing for promotion. The price signals enterprise buyers, but the channel attracts mid-market prospects. Neither audience converts. The Ps are at war with each other. + +### Beyond the Original Four + +Subsequent scholars expanded the framework to 7 Ps (adding People, Process, Physical Evidence) for services businesses. Lauterborn proposed the 4 Cs (Customer, Cost, Convenience, Communication) as a buyer-centric reframe. These extensions have merit. But the original four remain the minimum viable marketing strategy -- the floor below which no company should fall. + +--- + +## Prompts + +**Prompt 1 -- Marketing Mix Audit:** +> Analyze my startup's current marketing mix. My product is [describe product/service], priced at [price point/model], distributed through [channels], and promoted via [current marketing activities]. My target customer is [describe]. Evaluate the coherence of these four elements. Where are they aligned, where do they conflict, and what specific changes would improve the overall mix? + +**Prompt 2 -- Price Sensitivity Analysis:** +> My product is [describe] in the [industry] space. Current price is [amount] with a [pricing model]. My competitors charge [range]. Help me evaluate whether my pricing is optimized by analyzing: perceived value vs. actual value, price elasticity for my segment, willingness-to-pay signals from [any data you have], and how my price interacts with my distribution channel and brand positioning. + +**Prompt 3 -- Channel Strategy Design:** +> I'm launching [product/service] targeting [customer segment]. I need to design my Place strategy. Evaluate these potential distribution channels for my business: [list channels you're considering]. For each, analyze: customer acquisition cost, scalability, alignment with my price point of [amount], and fit with my brand positioning. Recommend a primary and secondary channel with reasoning. + +**Prompt 4 -- Go-to-Market Mix Design:** +> I'm preparing to launch [product/service] in [market/segment]. Help me design a coherent marketing mix from scratch. Start with the target customer profile, then work through Product positioning, Price architecture, Place/distribution strategy, and Promotion plan -- ensuring all four elements reinforce each other. Budget constraint: [amount]. Timeline: [timeframe]. + +--- + +## Use Cases + +**Pre-Launch SaaS Pricing Misalignment** + +A validation-stage B2B SaaS founder has built an analytics platform targeting CFOs at mid-market companies (500-2,000 employees). The product is robust. Promotion runs through LinkedIn ads and cold email. But pricing sits at $99/month -- a figure that signals "small business tool" to the very CFOs the founder wants to reach. A Four Ps audit reveals the fundamental incoherence: the product and promotion target enterprise buyers, but the price screams SMB. Restructuring to $2,500/month with annual contracts, adding a sales-assisted demo process (adjusting Place from pure self-serve), and shifting promotion toward industry conferences and case studies restores alignment across all four levers. + +**D2C Consumer Brand Expanding to Retail** + +A growth-stage direct-to-consumer skincare brand generating $8M annually online faces a decision about entering physical retail. The Four Ps framework reveals the cascading implications: retail placement (Place) requires redesigned packaging and shelf-ready units (Product), wholesale margins compress pricing architecture (Price), and in-store marketing demands entirely different promotional strategies (Promotion). The framework prevents the common mistake of treating retail expansion as merely a distribution decision, exposing it as a full-system reconfiguration. + +**Marketplace Startup Balancing Two Sides** + +An early-traction marketplace connecting freelance designers with small businesses must run two parallel marketing mixes -- one for each side of the platform. The Four Ps analysis reveals that the supply side (designers) and demand side (businesses) require fundamentally different Product propositions, Price structures, Place strategies, and Promotion channels. Treating them as a single marketing problem, as the founders had been doing, explains the persistent supply-demand imbalance. + +--- + +## Anti-Patterns + +- **The Feature Obsession Trap.** Founders who spend 90% of their energy on the Product P and treat the other three as afterthoughts. A superior product with wrong pricing, invisible distribution, and no promotion strategy is a tree falling in an empty forest. The Ps demand equal strategic attention. + +- **Sequential Rather Than Simultaneous Thinking.** Treating the four Ps as a linear sequence -- "first we'll perfect the product, then figure out pricing, then distribution, then marketing" -- rather than designing them as an integrated system from the outset. By the time you reach the fourth P, the first three have already constrained your options. + +- **Copying Competitor Mixes Wholesale.** Adopting a competitor's pricing, channels, and promotion tactics without recognizing that their product positioning and brand equity differ from yours. The marketing mix is idiosyncratic to each company's strategic position. What works for the category leader actively harms the challenger. + +- **Ignoring Mix Evolution.** Setting the marketing mix at launch and never revisiting it. As the product matures, the customer base shifts, and competitive dynamics change, each P requires recalibration. The mix that worked at $500K ARR rarely survives intact to $5M. + +- **Promotion Without Product-Market Fit.** Pouring resources into the Promotion P before validating that the Product P actually solves a real problem. This is the most expensive mistake in startup marketing: amplifying a message about a product nobody wants. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Product-Price coherence | Testing willingness to pay; distribution is typically direct and simple; promotion is minimal and experimental | +| Early Traction | Channel discovery | Product is stabilizing; the critical question shifts to Place -- finding scalable, economic distribution channels | +| Growth | Full mix optimization | All four Ps are active and must be actively managed as an integrated system; promotion spend scales significantly | +| Scale | Mix diversification | Multiple product lines, price tiers, distribution channels, and promotion strategies running simultaneously; coherence becomes harder to maintain | + +--- + +## Output Template + +```markdown +# Marketing Mix Analysis: [Company/Product Name] + +**Date:** [Date] +**Stage:** [Current company stage] +**Target Customer:** [Primary customer segment] + +## Current Marketing Mix Assessment + +### Product +- **Core offering:** [What you sell] +- **Key differentiators:** [What makes it distinct] +- **Current gaps:** [What's missing or weak] + +### Price +- **Model:** [Subscription/one-time/freemium/etc.] +- **Price point:** [Amount] +- **vs. Competitors:** [Higher/lower/comparable] +- **Perceived value alignment:** [Strong/Weak/Misaligned] + +### Place +- **Primary channel:** [How customers buy] +- **Secondary channels:** [Additional distribution] +- **Channel economics:** [CAC, margins, scalability] + +### Promotion +- **Current activities:** [List channels and tactics] +- **Budget allocation:** [Where money goes] +- **Effectiveness:** [What's working, what isn't] + +## Coherence Assessment + +| P-to-P Alignment | Status | Issue | +|-------------------|--------|-------| +| Product-Price | [Aligned/Misaligned] | [Details] | +| Product-Place | [Aligned/Misaligned] | [Details] | +| Product-Promotion | [Aligned/Misaligned] | [Details] | +| Price-Place | [Aligned/Misaligned] | [Details] | +| Price-Promotion | [Aligned/Misaligned] | [Details] | +| Place-Promotion | [Aligned/Misaligned] | [Details] | + +## Recommended Adjustments +1. [Highest priority change] +2. [Second priority change] +3. [Third priority change] + +## Expected Impact +[What these changes should achieve and timeline for results] +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- The ERRC Grid fundamentally redefines the Product P by creating uncontested market space, requiring realignment of all four Ps around the new value curve. +- **[Business Model Canvas](business-model-canvas.md)** -- The broader business architecture within which the marketing mix operates; the Canvas's channels, customer relationships, and revenue streams map directly to Place, Promotion, and Price. +- **[Net Promoter Score](net-promoter-score.md)** -- Provides the customer feedback metric that reveals whether the marketing mix is delivering genuine value or merely generating transactions. +- **[Product Life Cycle](product-life-cycle.md)** -- The optimal marketing mix evolves as the product moves through introduction, growth, maturity, and decline, requiring systematic recalibration of all four Ps at each stage. +- **[Doblin's Ten Types of Innovation](doblin-ten-types.md)** -- Doblin's Experience types (Service, Channel, Brand, Customer Engagement) extend the Promotion and Place Ps into a richer innovation framework. +- **[Reader Psychology](../writing/reader-psychology.md)** -- Understanding how customers process information and make decisions is essential for designing Promotion messaging that resonates rather than merely reaches. diff --git a/plugins/foreman/content/skills/frameworks/giving-feedback.md b/plugins/foreman/content/skills/frameworks/giving-feedback.md new file mode 100644 index 0000000..b615dd4 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/giving-feedback.md @@ -0,0 +1,197 @@ +--- +name: "giving-feedback" +description: "Structures effective feedback conversations using the Situation-Behaviour-Impact (SBI) model from the Center for Creative Leadership. Separates observable behavior from interpretation, anchors feedback in specific situations, and articulates concrete impact. Use when preparing difficult performance conversations, constructing precise positive or corrective feedback, training first-time managers in feedback delivery, redesigning performance review systems, or building an organizational feedback culture." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - feedback + - communication + - management + - performance + - coaching +related_skills: + - radical-candor + - trust-equation + - thomas-kilmann-conflict + - grow-model +author: "Fatih Guner" +--- + +# Giving Feedback + +Here is an uncomfortable truth: most of the feedback you have given in your career has been useless. Not malicious, not even poorly intentioned -- simply useless. "Great job on that presentation" teaches nothing. "You need to be more strategic" is a Rorschach test, not guidance. "I'm disappointed in your performance this quarter" is an emotional discharge dressed as management. The receiver walks away knowing something happened but unable to extract a single actionable insight. Meanwhile, the giver checks "gave feedback" off their mental list and wonders why nothing changes. + +The problem is structural, not motivational. Most people want to give good feedback. They simply lack a method. The Situation-Behaviour-Impact (SBI) model, developed by the Center for Creative Leadership, provides exactly that: a rigorous structure that strips feedback of vagueness, projection, and judgment while preserving its essential content. SBI does not make difficult conversations easy. It makes them effective. + +--- + +## The Framework + +### The SBI Model: Three Components + +Effective feedback consists of three elements, delivered in sequence. Each element serves a specific function, and omitting any one of them degrades the feedback's utility. + +**S -- Situation** + +Anchor the feedback in a specific time, place, and context. This eliminates ambiguity and prevents the receiver from wondering "which time?" or "what do you mean?" + +- *Weak:* "In meetings, you tend to..." +- *Strong:* "In yesterday's product review meeting, when we were discussing the Q2 roadmap..." + +The situation establishes shared ground. Both parties can agree on when and where the event occurred. + +**B -- Behaviour** + +Describe the observable behaviour -- what the person *did*, not what you infer about their character, motivation, or intelligence. Behaviour is factual and disputable; interpretation is subjective and inflammatory. + +- *Weak:* "You were disrespectful to Sarah." +- *Strong:* "You interrupted Sarah three times while she was presenting her analysis, and on the third interruption you said, 'We've heard enough on this.'" + +The discipline of describing behaviour rather than attributing motive is the hardest part of SBI. It requires the feedback giver to separate observation from judgment -- a distinction that is conceptually simple and practically demanding. + +**I -- Impact** + +Articulate the effect the behaviour had -- on you, on others, on the project, or on the organisation. Impact connects behaviour to consequences, transforming feedback from a personal opinion into a business-relevant observation. + +- *Weak:* "That was unprofessional." +- *Strong:* "When you interrupted Sarah, she stopped contributing for the rest of the meeting. We lost her perspective on the technical feasibility assessment, and the team left without addressing a risk she had identified." + +### The Complete SBI Statement + +Assembling the three components: + +> "In yesterday's product review meeting [Situation], when you interrupted Sarah three times and said 'we've heard enough' [Behaviour], she stopped contributing for the rest of the meeting, and we missed her perspective on a technical risk that could affect the Q2 timeline [Impact]." + +No labels. No character judgments. No vague generalities. The receiver knows exactly what happened, what they did, and why it matters. + +### Extending SBI: The SBI-I Variant + +Some practitioners add a fourth element -- **Intent inquiry** -- transforming SBI into SBI-I: + +> "...I want to understand your perspective. What was going on for you in that moment?" + +This addition shifts the interaction from monologue to dialogue. It acknowledges that the feedback giver may have incomplete information. Perhaps the interruption was prompted by a time constraint the giver did not know about. The intent inquiry preserves the directness of SBI while opening space for the receiver's context. + +### SBI for Positive Feedback + +SBI is not exclusively a tool for criticism. Praise benefits equally from specificity: + +> "In Friday's client call [Situation], when the client challenged our pricing model and you walked them through the ROI calculation using their own data [Behaviour], the client's tone shifted entirely -- they moved from objecting to asking about implementation timelines [Impact]." + +Compare this with "Great job on the client call." The SBI version reinforces the *specific* behaviour that produced the result, making it far more likely to be repeated. + +### The Feedback Delivery Sequence + +1. **Prepare.** Write out the SBI components before the conversation. Rehearse if necessary. Precision under emotional pressure requires preparation. +2. **Set context.** "I have some feedback I'd like to share. Is this a good time?" Consent matters; ambush feedback triggers defence rather than reflection. +3. **Deliver the SBI statement.** Say it once, clearly, without hedging. +4. **Pause.** Silence is essential. The receiver needs time to process. +5. **Listen.** If using SBI-I, invite their perspective. Resist the urge to rebut. +6. **Agree on forward action.** "What would you like to do differently next time?" or "How can I support you in changing this?" +7. **Follow up.** Acknowledge improvement when you see it. Feedback without follow-up signals that the conversation was not important. + +--- + +## Prompts + +**Prompt 1 -- SBI Construction:** +> I need to give feedback to [person/role] about [describe the situation]. Help me construct a precise SBI statement by separating the situation (when and where), the behaviour (what they did, observably), and the impact (the effect on the team, project, or business). Ensure the behaviour description contains no interpretive language -- only observable actions and direct quotes where available. + +**Prompt 2 -- Feedback Pattern Analysis:** +> Here are five pieces of feedback I have recently given to my team: [list them]. Analyse each against the SBI model. Identify which ones lack a clear situation, which conflate behaviour with interpretation, and which omit impact. Then rewrite each as a proper SBI statement. + +**Prompt 3 -- Difficult Feedback Preparation:** +> I need to address a sensitive performance issue with [describe person and context]. The issue involves [describe]. I am nervous about this conversation because [describe your concern -- damaging the relationship, triggering a defensive response, etc.]. Help me prepare a complete SBI statement and a conversation plan, including: how to open, what to say, how to handle likely defensive responses, and how to close with a forward-looking action plan. + +**Prompt 4 -- Positive Feedback Architecture:** +> I want to build a habit of giving specific positive feedback to my team of [size]. For the past week, I have noticed these contributions: [list 3-5 things team members did well]. Help me craft SBI-format positive feedback for each one, ensuring the behaviour is specific enough to be repeatable and the impact is concrete enough to demonstrate why their contribution mattered. + +**Prompt 5 -- Feedback Culture Kickstart:** +> My company of [size] has no structured feedback practice. People either avoid feedback entirely or deliver it vaguely during annual reviews. Design a lightweight feedback programme built on the SBI model that includes: a 30-minute training session outline, a feedback template for managers, a weekly or bi-weekly feedback ritual, and a way to measure whether feedback quality improves over 90 days. + +--- + +## Use Cases + +**Validation-Stage Startup with Two Cofounders** +The CEO cofounder needs to address the CTO cofounder's habit of committing to deadlines in customer meetings that engineering cannot meet. Rather than the usual passive-aggressive tension ("we need to manage expectations better"), the CEO constructs an SBI statement: "In Tuesday's demo with Acme Corp [Situation], you told them we'd have the API integration ready in two weeks [Behaviour]. The engineering team estimates six weeks, which means we either disappoint the client or burn out the team to hit an unrealistic date -- and this is the third time this quarter it has happened [Impact]." The specificity transforms a recurring frustration into a solvable problem. + +**Growth-Stage Manager Giving First-Time Feedback to a Senior Hire** +A newly promoted engineering manager must address code quality issues with a senior engineer who has more experience than they do. The power dynamic makes vague feedback ("your code could be cleaner") dangerous -- the senior hire will dismiss it. SBI equalises the interaction: "In the PR you submitted yesterday for the payment processing module [Situation], there were no unit tests for the edge cases we identified in the design review, and the error handling returned generic 500 responses without logging [Behaviour]. Two of those edge cases caused production incidents in a similar module last month, and without specific error codes, debugging takes three times as long [Impact]." The feedback is inarguable because it is grounded in fact. + +**Scale-Stage Company Running Annual Performance Reviews** +A 400-person company replaces its ineffective annual review process (generic ratings on a 1-5 scale with subjective commentary) with an SBI-based system. Managers are required to provide three SBI-positive and two SBI-developmental examples per review. Calibration sessions across management levels ensure that "exceeds expectations" is supported by specific behavioural evidence, not general impressions. Review quality, measured by employee satisfaction surveys, increases 35% in the first cycle. + +--- + +## Anti-Patterns + +1. **The Feedback Sandwich.** Positive-negative-positive. The structure is so well-known that it has become a psychological signal meaning "brace yourself, the middle part is what they actually think." Recipients learn to ignore the bread and dread the filling. SBI does not require sandwiching; it requires clarity. + +2. **Behaviour-as-Interpretation.** "In the meeting, you were passive-aggressive" is interpretation, not behaviour. "In the meeting, you rolled your eyes when I presented the budget and said 'sure, whatever you think'" is behaviour. The distinction determines whether feedback produces insight or defensiveness. + +3. **Stockpiling.** Saving feedback for a quarterly review rather than delivering it within 48 hours of the event. Delayed feedback loses context, accumulates emotional charge, and overwhelms the receiver with a catalogue of grievances they can no longer recall clearly enough to address. + +4. **Impact Inflation.** Exaggerating the impact to make the feedback feel more important. "Your typo in the client email could have cost us the entire account" -- could it? Really? Impact inflation erodes trust. State the actual impact, neither minimised nor inflated. + +5. **Monologue Feedback.** Delivering the SBI statement and immediately moving on without pausing for the receiver's response. Feedback is a dialogue. The SBI statement opens the conversation; it does not constitute the conversation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Cofounder feedback | At the earliest stage, feedback flows between two or three people with no managerial hierarchy. SBI provides structure for peer feedback where "pull rank" is not an option. | +| Early Traction | First-time managers | New managers need a concrete method. SBI is the simplest and most immediately applicable feedback framework -- a tool they can use in their first week as a manager. | +| Growth | Feedback consistency across teams | Different managers give feedback differently. SBI provides a common language and structure that ensures minimum feedback quality across the growing management layer. | +| Scale | Institutional feedback systems | At scale, SBI becomes embedded in performance review templates, 360-degree review tools, and manager training programmes. The framework becomes organisational infrastructure rather than individual practice. | + +--- + +## Output Template + +```markdown +# Feedback Preparation: [Recipient Name/Role] + +## SBI Statement +- **Situation:** [When and where -- specific date, meeting, context] +- **Behaviour:** [What they did -- observable actions only, no interpretation] +- **Impact:** [Effect on team, project, business, or individuals] + +## Complete Statement (Draft) +"[Assembled SBI statement, ready to deliver]" + +## Conversation Plan +- **Opening:** [How you will set context and ask for permission] +- **Delivery:** [The SBI statement] +- **Pause and listen:** [Expected response and how you will handle it] +- **Intent inquiry (optional):** "What was your perspective on that moment?" +- **Forward action:** [What change you are requesting and what support you will offer] +- **Follow-up plan:** [When and how you will check in on progress] + +## Defensive Response Preparation +| Likely Response | Your Approach | +|-----------------|---------------| +| Denial ("That didn't happen") | [Return to observable facts] | +| Deflection ("Everyone does that") | [Refocus on specific impact] | +| Counter-attack ("Well, you...") | [Acknowledge, redirect to the topic] | +| Emotion (tears, anger) | [Pause, express care, offer to continue later] | +``` + +--- + +## Related Skills + +- **[Radical Candor](radical-candor.md)** -- Radical Candor provides the philosophical foundation for why direct feedback matters; SBI provides the mechanical structure for how to deliver it effectively. +- **[Trust Equation](trust-equation.md)** -- The denominator of the trust equation (self-orientation) directly affects whether feedback is received as helpful or self-serving. +- **[Thomas-Kilmann Conflict](thomas-kilmann-conflict.md)** -- Feedback conversations often trigger conflict; understanding conflict modes helps the giver navigate defensive responses and choose the right approach. +- **[GROW Model](grow-model.md)** -- After SBI identifies the issue, GROW provides a coaching framework for developing the forward-looking action plan with the recipient. +- **[Psychological Safety](psychological-safety.md)** -- Edmondson's safety conditions determine whether feedback is received as developmental input or perceived as threat, making safety a prerequisite for effective SBI delivery. +- **[Writing Performance Reviews](../writing/writing-performance-reviews.md)** -- Translates the SBI discipline into written form for formal review processes, ensuring documented feedback is equally specific and actionable. diff --git a/plugins/foreman/content/skills/frameworks/grow-model.md b/plugins/foreman/content/skills/frameworks/grow-model.md new file mode 100644 index 0000000..83e61b1 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/grow-model.md @@ -0,0 +1,231 @@ +--- +name: "grow-model" +description: "Facilitates coaching conversations and structured decision-making using Whitmore's GROW model: Goal (clarify objectives), Reality (assess current state honestly), Options (generate alternatives), and Will (commit to action). Use when coaching team members, making strategic decisions as a founder, breaking through analysis paralysis, conducting self-coaching sessions on difficult choices, preparing one-on-ones, or developing management capability across a growing leadership team." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - coaching + - goal-setting + - problem-solving + - one-on-ones + - mentoring +related_skills: + - psychological-safety + - emotional-intelligence + - growth-mindset + - neuro-linguistic-programming +author: "Fatih Guner" +--- + +# GROW Model + +A gardener does not grow a plant. A gardener creates the conditions -- soil, light, water, space -- in which the plant grows itself. John Whitmore, the British racing driver turned executive coach, built the GROW model on precisely this philosophy of human development. Published in his 1992 book *Coaching for Performance*, GROW offers a deceptively simple four-stage questioning framework that has become the most widely used coaching structure in the world. Its power lies not in telling people what to do but in asking them questions that unlock their own clarity. For entrepreneurs, who chronically suffer from both advice overload and decision paralysis, GROW provides a structured pathway from muddled intention to committed action -- and, equally valuable, a repeatable method for coaching the people they lead. + +--- + +## The Framework + +GROW is an acronym representing four sequential stages of a coaching conversation. Each stage has a distinct purpose and a characteristic set of questions. The coach (or self-coaching entrepreneur) moves through the stages in order, though real conversations often loop back as new insights emerge. + +### The Four Stages + +**G -- Goal** + +Establish what the person wants to achieve. Not vaguely ("I want to grow the business") but with specificity sufficient to recognise achievement. The goal stage separates wishful thinking from actionable intention. + +Essential questions: +- What do you want to achieve? +- What would make this conversation most valuable for you? +- What does success look like? How would you know you had achieved it? +- What is the timeframe? +- How ambitious is this goal on a scale of 1-10? +- Is this a performance goal (within your control) or an end goal (dependent on external factors)? + +The distinction between performance goals and end goals is critical for entrepreneurs. "Raise a Series A" is an end goal -- it depends on investor decisions outside the founder's control. "Complete 30 investor conversations and iterate the pitch to a 50% follow-up rate" is a performance goal -- fully within the founder's control and far more useful for coaching. + +**R -- Reality** + +Explore the current situation with unflinching honesty. Most people skip this stage, jumping from goal to action without understanding their starting position. The reality stage grounds ambition in fact. + +Essential questions: +- What is happening now? What is the current state? +- What have you tried so far? What happened? +- What obstacles are you facing? +- Who else is involved, and what is their perspective? +- On a scale of 1-10, where are you currently relative to your goal? +- What is the gap between where you are and where you want to be? +- What resources do you currently have? +- What internal factors (skills, beliefs, habits) are helping or hindering? + +The most valuable reality questions are those that surface uncomfortable truths the person has been avoiding. A skilled coach listens for omissions, euphemisms, and assumptions that have not been tested. + +**O -- Options** + +Generate the widest possible range of options before evaluating any of them. The critical discipline here is separating ideation from judgment. Most people generate two or three options and immediately begin debating their merits. The options stage insists on quantity first, quality second. + +Essential questions: +- What could you do? (Repeated multiple times to push past obvious answers) +- What else? (The most powerful coaching question -- it signals that the first answers are rarely the best) +- If you had no constraints, what would you do? +- What would you do if you knew you could not fail? +- What would someone you admire do in this situation? +- What would happen if you did nothing? +- What are the costs and benefits of each option? +- Which option excites you most? + +The "What else?" question deserves emphasis. Research on brainstorming shows that the first ideas generated are typically the most conventional. Genuine insight tends to emerge after the obvious options have been exhausted -- usually around the fifth or sixth option. + +**W -- Will (or Way Forward)** + +Convert the preferred option into a specific, committed action plan. This stage transforms insight into behaviour. Without it, coaching conversations produce understanding but not change. + +Essential questions: +- What will you do? (Not "what could you do" -- the shift to "will" is deliberate) +- When will you do it? +- What is the first step? +- On a scale of 1-10, how committed are you to this action? +- What might get in the way? +- How will you overcome those obstacles? +- Who needs to know about your plan? +- How will you hold yourself accountable? +- What support do you need? + +If commitment scores below 7, the action plan needs revision. Either the action is wrong, the timeline is unrealistic, or the person is not genuinely ready. Whitmore emphasises that low commitment is information, not failure -- it sends the conversation back to earlier stages. + +### GROW as Self-Coaching + +GROW is commonly presented as a tool for coaching others, but its highest-frequency use for entrepreneurs is self-coaching. The founder sits with a journal or an AI assistant and works through the four stages on a specific decision. The structure prevents the two most common failure modes of solo decision-making: rumination without progress (endlessly revisiting the problem without generating options) and premature action (jumping to solutions without understanding the reality or goal clearly). + +--- + +## Prompts + +**Prompt 1 -- Full GROW Session:** +> Run a complete GROW coaching session with me on this challenge: [describe challenge]. Start by helping me clarify my Goal with specific, measurable terms. Then explore my current Reality by asking probing questions about what I have tried, what I know, and what I might be avoiding. Generate at least 7 Options, pushing past the obvious ones. Finally, help me select and commit to specific actions with dates, accountability mechanisms, and contingency plans. Push back if my commitment is below 7/10 on any action. + +**Prompt 2 -- Reality Check:** +> I believe the current state of [aspect of my business] is: [describe your understanding]. Challenge my reality assessment using GROW Reality questions. Identify assumptions I may be making, perspectives I may be missing, and uncomfortable truths I may be avoiding. Rate my reality assessment on a 1-10 scale for completeness and honesty, and tell me what a 10 would include that my current assessment does not. + +**Prompt 3 -- Options Expansion:** +> I am stuck between these options for [decision]: [list 2-3 options you are considering]. Using the GROW Options methodology, generate at least 5 additional options I have not considered. Include at least one option that is radically different from my current thinking, one that involves doing nothing, and one that reframes the problem entirely. For each option, provide a one-sentence summary of its primary advantage and primary risk. + +**Prompt 4 -- Coaching Preparation:** +> I need to have a coaching conversation with [team member name/role] about [issue]. Design a GROW-structured conversation plan with specific questions for each stage, tailored to what I know about this person: [describe their situation, personality, likely resistance points]. Include suggested responses for likely pushback and a plan for what to do if commitment remains low after the Will stage. + +**Prompt 5 -- Weekly GROW Review:** +> Review my progress on last week's GROW commitments: [list what you committed to and what actually happened]. For any actions not completed, diagnose whether the barrier was in the Goal (wrong target), Reality (unexpected obstacle), Options (wrong approach), or Will (insufficient commitment). Adjust the plan accordingly and set this week's GROW commitments. + +--- + +## Use Cases + +**Idea-stage founder choosing between two venture concepts** + +A would-be founder is paralysed between two startup ideas and has spent four months "thinking about it" without making progress on either. A GROW self-coaching session reveals that the stated goal ("decide which idea to pursue") is actually a performance goal disguised as a binary choice. The reality exploration uncovers that the founder's paralysis stems from fear of choosing wrong, not from insufficient information. The options stage generates a third path neither idea had suggested: running a two-week validation sprint on each idea simultaneously, using pre-defined criteria to compare results. The will stage produces a specific calendar with blocked time, measurable milestones, and a hard decision date. The founder launches both sprints and, within two weeks, has enough data to commit with confidence. + +**Growth-stage CTO coaching a struggling engineering manager** + +A CTO notices that a recently promoted engineering manager is overwhelmed and reverting to individual contributor behaviour -- writing code instead of managing the team. Rather than giving directive advice ("Stop coding and start managing"), the CTO uses GROW. The goal stage reveals the manager wants to "feel effective again" -- which surfaces the real issue (identity transition, not skill deficit). The reality stage uncovers that the manager has never received management training and is using coding as a psychological safety blanket. The options stage generates possibilities ranging from formal training to peer mentoring to a temporary reduction in direct reports. The will stage produces a commitment to complete a management fundamentals course within 60 days and to schedule weekly one-on-ones with each direct report starting immediately. Crucially, the manager arrived at these actions herself -- the CTO asked questions rather than prescribed solutions. + +**Scale-stage CEO self-coaching on a potential acquisition** + +A CEO is considering whether to acquire a smaller competitor. Using GROW with an AI assistant, the goal stage clarifies that the acquisition's purpose is customer base expansion, not technology acquisition -- a distinction that had been blurred in board discussions. The reality stage reveals that the company's integration track record is poor (two of three past integrations underperformed projections). The options stage generates eight alternatives to acquisition, including partnership, licensing, and organic expansion into the competitor's market segment. The will stage produces a commitment to complete a formal integration readiness assessment before bringing the acquisition proposal to the board, with a hard deadline of six weeks. + +--- + +## Anti-Patterns + +**1. Rushing to the Will stage.** The most common misapplication of GROW is treating it as a goal-setting tool rather than an exploratory process. Coaches (and self-coaching entrepreneurs) who sprint through Goal and Reality to reach Will produce superficially actionable but poorly grounded plans. The value of GROW is proportional to the time spent in Reality and Options. + +**2. Asking leading questions disguised as coaching.** "Don't you think you should fire that underperformer?" is not a GROW question -- it is advice with a question mark attached. Genuine GROW coaching requires the coach to suspend their own opinions and trust the process. For founders, who are accustomed to having strong views and sharing them, this discipline is genuinely difficult. + +**3. Using GROW for problems that require direction, not coaching.** If a building is on fire, coaching someone through options for extinguishing it is inappropriate. Some situations require direct instruction: compliance issues, safety concerns, ethical violations, and time-critical emergencies. GROW works best when the person being coached has the latent capability to find their own answer and the time to do so. + +**4. Treating the model as rigidly sequential.** Real conversations are not linear. A person exploring reality may discover that their goal needs revision. An option may surface a reality they had overlooked. Skilled GROW practitioners move fluidly between stages while maintaining overall forward momentum. Rigid adherence to the sequence produces stilted, unnatural conversations. + +**5. Accepting vague goals and weak commitments.** "I want to improve my leadership" is not a GROW-ready goal. "I want my direct reports to rate my feedback quality at 8/10 or above in the next quarterly survey" is. Similarly, accepting "I'll try to do that next week" as a will statement guarantees nothing will happen. The discipline of GROW lies in its insistence on precision. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder self-coaching on direction and commitment | GROW helps convert vague entrepreneurial impulse into specific, testable hypotheses | +| Validation | Customer discovery, hypothesis refinement | Reality questions discipline the founder to assess market signals honestly rather than selectively | +| Early Traction | Coaching first hires, decision-making under pressure | GROW becomes a management tool; the founder coaches rather than directs | +| Growth | Management development, strategic choices | GROW scales through the management layer; training managers to coach is a force multiplier | +| Scale | Executive coaching, board-level decision-making | GROW's structured approach brings rigour to complex, multi-stakeholder strategic decisions | + +GROW applies at every stage, but its primary function shifts. At the idea and validation stages, it is predominantly a self-coaching tool: the founder uses it to structure their own thinking and avoid the twin traps of analysis paralysis and premature action. + +At early traction and growth, GROW becomes an organisational tool. Founders who coach rather than direct build teams that are more autonomous, more engaged, and more capable of solving problems independently. The transition from "I'll tell you what to do" to "What do you think you should do?" is one of the most important leadership shifts a scaling founder must make, and GROW provides the structure for making it. + +At scale, GROW's value lies in its ability to bring structured clarity to decisions of genuine complexity. Board-level strategic choices, executive succession planning, and organisational transformation all benefit from the disciplined progression through goal, reality, options, and commitment. + +--- + +## Output Template + +```markdown +# GROW Coaching Record -- [Topic/Decision] + +**Date:** [Date] +**Coached by:** [Self / Coach name] +**Session focus:** [One-sentence description of the challenge] + +## G -- Goal +- **Stated goal:** [Initial goal as articulated] +- **Refined goal:** [Goal after clarification -- specific, measurable, time-bound] +- **Goal type:** [Performance goal / End goal] +- **Ambition level:** [1-10] + +## R -- Reality +- **Current state:** [Honest assessment of where things stand] +- **What has been tried:** [Previous attempts and their outcomes] +- **Key obstacles:** [Internal and external barriers] +- **Current position vs. goal:** [1-10] +- **Uncomfortable truth surfaced:** [The thing that was being avoided] + +## O -- Options Generated + +| # | Option | Primary Advantage | Primary Risk | +|---|--------|-------------------|-------------| +| 1 | [Option] | [Advantage] | [Risk] | +| 2 | [Option] | [Advantage] | [Risk] | +| 3 | [Option] | [Advantage] | [Risk] | +| 4 | [Option] | [Advantage] | [Risk] | +| 5 | [Option] | [Advantage] | [Risk] | + +**Selected option:** [Which option and why] + +## W -- Will / Way Forward + +| Action | Deadline | Commitment (1-10) | Accountability | +|--------|----------|-------------------|----------------| +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | + +**Potential obstacles:** [What might prevent follow-through] +**Contingency plan:** [What to do if obstacles materialise] +**Review date:** [When to assess progress] +``` + +--- + +## Related Skills + +- **[Psychological Safety](psychological-safety.md)** -- GROW coaching requires a foundation of psychological safety; the Reality stage demands honesty that is only possible when the coachee feels safe being candid. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Effective GROW coaching depends on the coach's empathy (reading the coachee's emotional state) and the coachee's self-awareness (providing honest reality assessments). +- **[Growth Mindset](growth-mindset.md)** -- Dweck's framework provides the belief system that makes GROW productive; a person with a fixed mindset will resist the Reality stage and generate constrained Options. +- **[Giving Feedback](giving-feedback.md)** -- SBI identifies specific behavioural issues that then become the starting point for a GROW coaching conversation to develop the forward-looking action plan. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- Provides the broader leadership context for deploying GROW as part of a systematic coaching and development practice across a growing organization. +- **[SMART Goals](smart-goals.md)** -- The Goal stage of GROW produces better outcomes when goals meet SMART criteria, ensuring the coaching conversation is anchored in specific, measurable commitments. diff --git a/plugins/foreman/content/skills/frameworks/growth-mindset.md b/plugins/foreman/content/skills/frameworks/growth-mindset.md new file mode 100644 index 0000000..215740b --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/growth-mindset.md @@ -0,0 +1,172 @@ +--- +name: "growth-mindset" +description: "Applies Carol Dweck's growth mindset framework to individual resilience and organizational culture, distinguishing between fixed mindset (ability is innate) and growth mindset (ability develops through effort and strategy). Use when processing failure and setbacks, reframing team responses to challenges, designing hiring interview protocols that assess learning orientation, transforming performance review systems, building learning cultures in startups, or diagnosing why a team avoids risk and experimentation." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth +tags: + - mindset + - learning + - resilience + - talent-development + - culture +related_skills: + - psychological-safety + - flow-state + - emotional-intelligence + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +# Growth Mindset + +In 1998, Carol Dweck and Claudia Mueller published a study that quietly detonated decades of received wisdom about praise. They told one group of children they were smart after they solved a problem. They told another group they had worked hard. The "smart" children subsequently avoided challenging tasks, collapsed under difficulty, and lied about their scores. The "hard work" children sought harder problems, persisted longer, and performed better. That single experiment -- replicated and extended over the next two decades at Stanford -- revealed something profound about the architecture of human motivation: the beliefs people hold about the nature of their own abilities fundamentally shape how they respond to setbacks, challenges, and opportunities. Dweck formalised this into two orientations -- fixed mindset and growth mindset -- and in doing so provided a framework that has reshaped education, sport, and, increasingly, how organisations think about talent, innovation, and culture. + +--- + +## The Framework + +### Fixed vs. Growth: The Two Orientations + +The distinction is not about optimism versus pessimism, or effort versus laziness. It concerns a deeper belief about the malleability of human capability. + +| Dimension | Fixed Mindset | Growth Mindset | +|-----------|--------------|----------------| +| **Core belief** | Ability is innate and static | Ability is developed through effort, strategy, and learning | +| **Response to challenge** | Avoids challenges that risk exposing inadequacy | Embraces challenges as learning opportunities | +| **Response to failure** | Interprets failure as evidence of inherent limitation | Interprets failure as information about what to adjust | +| **Response to effort** | Views effort as proof of insufficient talent | Views effort as the path to mastery | +| **Response to criticism** | Defensive; takes feedback personally | Seeks feedback as developmental input | +| **Response to others' success** | Threatened; perceives it as diminishing own standing | Inspired; studies it for learnable lessons | + +Dweck's research demonstrates that these orientations are not permanent personality traits but contextual beliefs that can shift. A person may hold a growth mindset about their technical skills and a fixed mindset about their leadership ability. The orientations are domain-specific and mutable. + +### The Mechanism: Effort-Belief Connection + +The psychological engine beneath the framework is the relationship between effort and meaning. In a fixed mindset, effort signals inadequacy -- if you were truly talented, you would not need to try so hard. In a growth mindset, effort signals investment -- struggle is the mechanism through which ability expands. This single interpretive difference cascades through every decision a founder makes: whether to enter unfamiliar markets, whether to hire people who challenge them, whether to persist after a failed launch, whether to accept board feedback or dismiss it. + +### Growth Mindset in Organisations + +Dweck's later research extended the framework from individuals to organisations. Companies with growth-mindset cultures -- where learning, experimentation, and development are valued over proving brilliance -- exhibit measurably different behaviours: + +- Employees report more trust and commitment +- Innovation increases because failure is treated as data, not disgrace +- Collaboration improves because individuals are not competing to prove they are the smartest person in the room +- Ethical behaviour increases because employees feel less pressure to cut corners to maintain an image of effortless competence + +Conversely, "genius cultures" -- organisations that prize innate talent above all -- exhibit higher rates of fraud, internal competition, and stagnation. Enron is the canonical cautionary tale: a culture that celebrated brilliance and punished visible struggle created an environment where admitting problems was career suicide. + +### The "Not Yet" Principle + +One of Dweck's most actionable contributions is the reframe from "I can't do this" to "I can't do this yet." The addition of a single word transforms a fixed-mindset statement into a growth-mindset trajectory. For founders, "We don't have product-market fit" is a verdict in fixed mindset and a status update in growth mindset. "Yet" implies a process underway, not a condition concluded. + +--- + +## Prompts + +**Prompt 1 -- Mindset Diagnostic:** +> Analyse my team's recent response to this setback: [describe setback and how the team reacted]. Classify the predominant reactions as fixed-mindset or growth-mindset indicators. Identify specific language, decisions, and behaviours that reveal the underlying belief system. Recommend three concrete changes to team rituals or communication patterns that would shift the culture toward growth mindset. + +**Prompt 2 -- Failure Reframe:** +> We experienced the following failure: [describe failure in detail]. Help me process this through a growth-mindset lens. Structure the analysis as: (a) what specifically failed (separate from identity), (b) what was learned that was not knowable before, (c) what strategies should change based on this information, and (d) a specific "not yet" reframe I can share with the team that acknowledges the failure honestly while orienting toward continued development. + +**Prompt 3 -- Hiring for Growth Mindset:** +> I need to assess growth mindset in candidates for [role]. Design an interview protocol with 5 behavioural questions that reveal a candidate's mindset orientation. For each question, describe what a fixed-mindset response sounds like versus a growth-mindset response. Include one practical exercise or case study that would surface mindset orientation under pressure. + +**Prompt 4 -- Culture Audit:** +> Evaluate whether my company's practices signal a growth mindset or a fixed mindset. Here are our current practices: [describe hiring criteria, performance review process, how failure is discussed, how promotions are decided, how praise is given, how challenges are framed]. For each practice, identify whether it reinforces a fixed or growth orientation and suggest specific modifications. + +--- + +## Use Cases + +**Idea-stage solo founder facing repeated rejection** + +A first-time founder has received 30 rejections from investors and is questioning whether entrepreneurship is "not for me." This is textbook fixed-mindset framing: failure interpreted as evidence of inherent unsuitability. Applying Dweck's framework, a mentor reframes the situation: rejection is feedback, not verdict. The mentor and founder systematically analyse the rejections for patterns (unclear value proposition, unconvincing market sizing, weak competitive analysis), extract specific learnable improvements for each, and set a target of iterating the pitch through five distinct versions. By version four, the founder secures a meeting that leads to a pre-seed commitment. The outcome did not change because the founder gained new innate talent; it changed because they treated their pitching ability as developable. + +**Growth-stage startup transforming performance reviews** + +A 120-person SaaS company discovers that its annual performance review process, inherited from a corporate playbook, is producing anxiety, defensiveness, and attrition among top performers. Analysis reveals a fixed-mindset architecture: reviews are evaluative ("meets expectations," "exceeds expectations," "below expectations"), focused on judging past performance against static standards. The company redesigns the process around growth-mindset principles: reviews become development conversations focused on trajectory, learning goals, and skill acquisition. Ratings are replaced with growth plans. The language shifts from "where you fell short" to "what you're building toward." Within two review cycles, engagement scores rise by 18 points and voluntary attrition among high performers drops by half. + +--- + +## Anti-Patterns + +**1. "Growth mindset" as toxic positivity.** Telling someone to "just have a growth mindset" about a genuine structural problem -- inadequate funding, impossible market conditions, toxic co-founder dynamics -- trivialises legitimate obstacles. Growth mindset means believing that abilities can develop through effort and strategy; it does not mean that effort alone can overcome any obstacle. Some situations require strategic withdrawal, not motivational reframing. + +**2. Praising effort divorced from strategy and outcome.** Dweck herself has warned against this misapplication. Praising effort that produces no learning or improvement is not growth mindset -- it is false comfort. The growth-mindset response to ineffective effort is to examine and improve the strategy, not to celebrate the trying. "You worked really hard but the approach didn't work -- what can we change?" is the correct formulation. + +**3. Using growth mindset to justify under-investing in talent.** Some organisations adopt growth mindset language to rationalise not hiring experienced people: "We'll just grow into the capability." Development takes time, and some situations require competence now. Growth mindset applies to developing capabilities over reasonable timescales, not to ignoring current skill gaps in urgent contexts. + +**4. Creating a fixed mindset about fixed mindset.** Labelling someone as "having a fixed mindset" and treating that label as a permanent character diagnosis is itself a fixed-mindset move. Mindset is contextual and mutable. The constructive approach is to address the specific belief in the specific context, not to categorise the person. + +**5. Ignoring systemic barriers.** Growth mindset operates at the individual and cultural level. It does not address structural inequalities, resource constraints, or market failures. Telling an underfunded founder in a discriminatory funding environment to "develop a growth mindset" without addressing the systemic barriers is unhelpful at best and insulting at worst. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder resilience and identity | The founder must separate self-worth from the idea's viability; "my idea failed" is not "I am a failure" | +| Validation | Interpreting negative signals | Fixed mindset ignores disconfirming evidence; growth mindset treats every customer rejection as actionable data | +| Early Traction | Building learning culture from day one | First hires absorb the founder's mindset orientation; this is the highest-leverage moment to establish growth-oriented norms | +| Growth | Scaling learning systems | Individual growth mindset must become organisational infrastructure: learning budgets, post-mortem practices, development-oriented reviews | + +The idea stage is where growth mindset matters most viscerally. The founder is psychologically fused with the venture; rejection of the idea feels like rejection of the self. Dweck's framework provides the critical separation: the idea is a hypothesis, not an identity. Testing and refining hypotheses is what scientists do, and no scientist concludes they are personally inadequate because an experiment produced unexpected results. + +At early traction, the founder's mindset becomes contagious. The first ten employees will pattern-match on how the founder responds to failure, feedback, and challenge. A founder who models growth mindset -- openly discussing mistakes, seeking feedback, treating setbacks as learning events -- creates a culture where these behaviours are normal. A founder who performs brilliance and hides struggle creates a culture where the same is expected of everyone, with corrosive effects on innovation and psychological safety. + +--- + +## Output Template + +```markdown +# Growth Mindset Culture Assessment -- [Company Name] + +**Prepared for:** Leadership Team +**Date:** [Date] +**Assessment scope:** [Company-wide / Department / Team] + +## Current Mindset Indicators + +| Practice Area | Current Approach | Mindset Signal | Recommended Shift | +|--------------|-----------------|----------------|-------------------| +| Hiring | [How talent is assessed] | [Fixed/Growth] | [Specific change] | +| Performance reviews | [Current process] | [Fixed/Growth] | [Specific change] | +| Failure response | [How failures are discussed] | [Fixed/Growth] | [Specific change] | +| Praise patterns | [What gets celebrated] | [Fixed/Growth] | [Specific change] | +| Challenge framing | [How hard problems are presented] | [Fixed/Growth] | [Specific change] | + +## Language Audit +**Fixed-mindset phrases detected in company communications:** +- "[Phrase]" -- Growth-mindset alternative: "[Alternative]" +- "[Phrase]" -- Growth-mindset alternative: "[Alternative]" + +## Team Development Trajectories + +| Team Member / Role | Current Growth Area | "Not Yet" Statement | 90-Day Learning Goal | +|-------------------|--------------------|--------------------|---------------------| +| [Name/Role] | [Skill being developed] | "[I can't X yet]" | [Measurable target] | + +## Recommended Rituals +1. **[Ritual name]:** [Description and frequency] +2. **[Ritual name]:** [Description and frequency] +3. **[Ritual name]:** [Description and frequency] +``` + +--- + +## Related Skills + +- **[Psychological Safety](psychological-safety.md)** -- Growth mindset requires psychological safety to function; people will not admit mistakes or embrace challenges if they fear punishment, making Edmondson's work the essential organisational complement. +- **[Flow State](flow-state.md)** -- Csikszentmihalyi's flow depends on operating at the edge of current ability, which requires a growth-mindset belief that ability expands through challenge rather than being threatened by it. +- **[Emotional Intelligence](emotional-intelligence.md)** -- The self-awareness domain of EQ enables founders to recognise when they are operating from a fixed-mindset orientation and consciously shift to growth. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Provides the leadership practices for systematically extracting learning from setbacks, which is the organisational expression of growth mindset in action. +- **[Learning Agility](../leadership/learning-agility.md)** -- Extends Dweck's individual mindset framework into the organisational capability of rapidly learning and adapting in unfamiliar situations. +- **[Creative Obstacles](../creative/creative-obstacles.md)** -- Addresses the specific creative blocks that arise from fixed-mindset thinking, providing techniques for reframing creative challenges as growth opportunities. diff --git a/plugins/foreman/content/skills/frameworks/growth-share-matrix.md b/plugins/foreman/content/skills/frameworks/growth-share-matrix.md new file mode 100644 index 0000000..99d5c48 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/growth-share-matrix.md @@ -0,0 +1,221 @@ +--- +name: "growth-share-matrix" +description: "Analyzes product and business unit portfolios using the BCG Growth Share Matrix, classifying offerings into Stars, Cash Cows, Question Marks, and Dogs based on market growth rate and relative market share. Use when making resource allocation decisions across multiple products or business lines, evaluating which initiatives to invest in or divest, prioritizing a product portfolio, diagnosing why certain products drain resources without returns, or planning strategic investment sequencing at growth and scale stages." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - growth + - scale +tags: + - portfolio-management + - resource-allocation + - product-strategy + - strategic-planning + - investment-prioritisation +related_skills: + - product-life-cycle + - balanced-scorecard + - swot-pest-analysis + - disruptive-innovation +author: "Fatih Guner" +--- + +# Growth Share Matrix (BCG Matrix) + +The Boston Consulting Group's Growth Share Matrix turns business strategy into a menagerie. Stars blaze with potential, demanding heavy investment to maintain their orbit. Cash Cows graze contentedly in mature pastures, generating the capital that funds everything else. Question Marks pace nervously at the edge of relevance, consuming resources without certainty of return. And Dogs -- the uncomfortable truth in every portfolio -- sit in low-growth, low-share positions, consuming management attention that would be better spent elsewhere. Bruce Henderson introduced this taxonomy in 1970 with a one-page BCG Perspectives paper, and it became perhaps the single most influential framework in corporate strategy because it answered a question that every leader with more than one product or business unit faces: where should we invest, and where should we stop? + +The framework's elegance lies in its simplicity: two axes, four quadrants, clear strategic prescriptions. Its danger lies in the same simplicity -- applied mechanically, it can lead to catastrophic misallocation. Applied thoughtfully, it remains one of the sharpest tools for forcing honest conversation about where a company's future actually lies. + +--- + +## The Framework + +### The Two Axes + +**Vertical Axis: Market Growth Rate** + +The rate at which the market itself is expanding. High-growth markets attract investment, generate opportunity, and forgive mistakes. Low-growth markets reward efficiency, punish excess, and reward the already-dominant. The dividing line is contextual -- 10% annual growth might be the threshold for consumer technology, while 3% might distinguish high from low in industrial manufacturing. + +**Horizontal Axis: Relative Market Share** + +Your market share divided by the market share of your largest competitor. A ratio above 1.0 means you are the market leader; below 1.0 means someone else is. Relative share matters more than absolute share because market leadership confers cost advantages, brand recognition, and bargaining power that scale non-linearly. + +### The Four Quadrants + +``` + HIGH relative market share LOW relative market share + +---------------------------------+---------------------------------+ + | | | + HIGH market | STARS | QUESTION MARKS | + growth rate | | (Problem Children) | + | High growth + Market leader | High growth + Not leading | + | Strategy: Invest heavily | Strategy: Invest or divest | + | Cash flow: Roughly neutral | Cash flow: Highly negative | + | | | + +---------------------------------+---------------------------------+ + | | | + LOW market | CASH COWS | DOGS | + growth rate | | | + | Low growth + Market leader | Low growth + Not leading | + | Strategy: Harvest profits | Strategy: Divest or liquidate | + | Cash flow: Highly positive | Cash flow: Neutral to negative| + | | | + +---------------------------------+---------------------------------+ +``` + +#### Stars (High Growth, High Share) + +Stars are the future of the business. They hold leadership positions in markets that are growing rapidly. The challenge: high-growth markets demand continuous investment in sales, marketing, production capacity, and product development. Stars consume cash almost as fast as they generate it. The strategic imperative is to invest enough to maintain share as the market grows. A star that loses share during the growth phase will become a question mark; a star that maintains share as the market matures becomes a cash cow. + +*For startups:* Your core product in a market experiencing rapid adoption is your star. Do not starve it. The temptation to diversify prematurely -- launching adjacent products before the core product has captured its natural share -- is a common cause of startup failure during growth. + +#### Cash Cows (Low Growth, High Share) + +Cash cows are the economic engine. They hold dominant positions in mature markets where growth has slowed. Because the market is stable and the position is secure, cash cows generate surplus capital that exceeds what they need for maintenance. This surplus funds stars, selectively feeds question marks, and provides the financial resilience to weather downturns. + +*For startups:* Most early-stage startups do not have cash cows. The first cash cow often emerges when a product that drove initial growth enters maturity. Recognising this transition -- and shifting from growth investment to harvest mode -- is one of the most difficult psychological adjustments for founders. + +#### Question Marks (High Growth, Low Share) + +Question marks are strategic bets. They operate in attractive, high-growth markets but have not achieved the market share needed to generate positive returns. They consume cash heavily with uncertain payoff. The strategic decision is binary: invest aggressively to build share and convert to a star, or divest before the cash drain becomes unsustainable. + +*For startups:* Every new product line, geographic expansion, or market extension starts as a question mark. The discipline is ruthless triage: which question marks have a credible path to leadership, and which are consuming resources that would be better deployed elsewhere? + +#### Dogs (Low Growth, Low Share) + +Dogs are the quadrant that nobody wants to discuss. They hold weak positions in unattractive markets. They rarely generate meaningful profit and often consume disproportionate management attention. The orthodox prescription is clear: divest, wind down, or liquidate. But dogs persist in portfolios because of emotional attachment ("It was our first product"), sunk cost fallacy ("We've invested too much to quit"), or political dynamics ("The VP who built it is still on the leadership team"). + +*For startups:* A feature or product that has plateaued with minimal usage, generates no revenue growth, and distracts engineering resources from the core product is a dog. Killing it frees resources. Keeping it signals indecision. + +### The Portfolio Lifecycle + +Products naturally move through the matrix over time: + +``` +Question Mark --> Star --> Cash Cow --> (eventually) Dog + | + v + Dog (if investment fails) +``` + +A healthy portfolio has: +- One or two **Stars** receiving heavy investment +- One or more **Cash Cows** funding the portfolio +- A limited number of **Question Marks** under active evaluation +- No **Dogs** -- or Dogs actively being wound down + +An unhealthy portfolio has too many question marks (cash drain without a funding source), no stars (no future growth), or too many dogs (resource distraction). + +--- + +## Prompts + +**Prompt 1 -- Portfolio Classification:** +> "Classify each of our products/business lines into the BCG Growth Share Matrix: [list products with their market growth rate and relative market share or competitive position]. For each product, recommend the strategic action: invest (Star), harvest (Cash Cow), selectively invest or divest (Question Mark), or wind down (Dog). Explain the cash flow implications of the current portfolio balance." + +**Prompt 2 -- Resource Allocation Decision:** +> "Given this portfolio: [list products with their BCG classification, current revenue, growth rate, and investment level], how should we reallocate resources? Specifically: (1) Are we over-investing in any Cash Cows? (2) Are we under-investing in any Stars? (3) Which Question Marks deserve increased investment and which should be divested? (4) What is the total cash flow impact of the recommended reallocation?" + +**Prompt 3 -- Portfolio Health Assessment:** +> "Assess the health of our product portfolio: [list products with metrics]. Map each product's trajectory over the past [timeframe]. Which products are moving in the right direction (Question Mark to Star, Star to Cash Cow)? Which are moving in the wrong direction (Star to Question Mark, Cash Cow to Dog)? What strategic interventions would correct the negative trajectories?" + +--- + +## Use Cases + +**Growth-Stage SaaS Company With Multiple Products** + +A SaaS company with $10M ARR has three products: a project management tool ($7M ARR, 40% YoY growth, market leader in its segment), an invoicing add-on ($2M ARR, 5% growth, third in a mature market), and a newly launched resource planning module ($1M ARR, 80% growth, fifth in a fast-growing market). BCG classification: project management is a Star transitioning toward Cash Cow territory as growth decelerates. Invoicing is a Dog -- low growth, low relative share, and consuming engineering resources disproportionate to its contribution. Resource planning is a Question Mark -- high growth market, but significant share gap to close. The strategic recommendation: redirect engineering resources from invoicing (wind down or sell the product line) toward the resource planning module (invest to build share while the market is still forming), while ensuring the project management tool receives sufficient investment to maintain its leadership position through the growth-to-maturity transition. + +**Scale-Stage Consumer Brand Evaluating Geographic Expansion** + +A consumer brand present in five countries treats each market as a portfolio entry. The home market (US) is a Cash Cow: 35% market share, 3% market growth, generating $15M in annual free cash flow. The UK is a Star: 22% share in a market growing at 15%. Germany is a Question Mark: 4% share in a market growing at 12%. Japan and Brazil are Dogs: sub-3% share in markets growing at 2-4%. The portfolio diagnosis is immediate: use US cash flows to fund UK growth, make a decisive bet on Germany (invest to reach 10% share within 18 months or exit), and wind down Japan and Brazil operations to eliminate the management distraction and cash drain. The reallocation frees $3M annually and focuses the leadership team on two winnable markets instead of five. + +**Growth-Stage Marketplace Prioritising Feature Investment** + +An emerging marketplace applies the BCG framework not to products but to feature sets. Core matching algorithm: Star (high usage growth, market-leading in user satisfaction). Payments infrastructure: Cash Cow (stable, reliable, generates transaction revenue, low growth in usage). Social features: Question Mark (high engagement among early adopters, unclear path to monetisation). Analytics dashboard: Dog (low adoption, no growth, built for a use case that the market rejected). The analysis drives a product roadmap that increases matching algorithm investment by 30%, maintains payments, gives social features a 90-day prove-or-kill timeline, and deprecates the analytics dashboard. + +--- + +## Anti-Patterns + +**Mechanical Application Without Context.** Plotting products on the matrix and blindly following the textbook prescriptions. A "dog" product may serve as a loss leader that drives traffic to a star. A "cash cow" may need reinvestment because a disruptive competitor is eroding its position. The matrix is a starting point for strategic conversation, not a substitute for it. + +**Ignoring Interdependencies.** Products in a portfolio often share customers, technology, or brand equity. Divesting a dog that serves as the entry product for customers who eventually upgrade to the star would damage the star's pipeline. Portfolio analysis must account for these connections. + +**Treating Relative Market Share as Destiny.** A low relative share in a nascent market does not mean the same thing as a low relative share in a mature market. In emerging markets, share positions are fluid and achievable. The Question Mark quadrant requires nuanced assessment of share trajectory, not just current position. + +**Cash Cow Neglect.** The prescription to "harvest" cash cows is frequently interpreted as "stop investing entirely." Cash cows require maintenance investment -- product updates, customer retention efforts, infrastructure upkeep. A neglected cash cow becomes a declining revenue source faster than expected, starving the portfolio of the cash that funds everything else. + +**Emotional Attachment to Dogs.** The most difficult strategic discipline is killing products. Founders who built the company on a product that has become a dog find it psychologically impossible to wind it down. The BCG matrix provides the analytical cover for a decision that sentiment resists. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Growth | Identify your star and protect it | Most growth-stage startups have one product; the matrix helps decide whether to remain focused or begin portfolio expansion | +| Scale | Manage the portfolio actively | Multiple products and markets require systematic resource allocation; the matrix provides the framework | + +At the growth stage, the BCG matrix is most useful as a discipline against premature diversification. The temptation to launch new products (question marks) before the core product has achieved market leadership (star status) is a pattern that destroys companies. The matrix makes the trade-off explicit: every dollar invested in a question mark is a dollar not invested in strengthening the star. + +At scale, the matrix becomes an essential governance tool. Quarterly portfolio reviews that map every product and market to the matrix create accountability for investment decisions and force the difficult conversations about which question marks deserve continued funding and which dogs need to be wound down. + +--- + +## Output Template + +**Target Audience: CEO / Board of Directors** + +```markdown +# Portfolio Strategy Review: [Company Name] +## Period: [Quarter/Year] + +### Portfolio Map + +| Product/Business Unit | Market Growth Rate | Relative Market Share | BCG Quadrant | Revenue | Cash Flow | +|-----------------------|-------------------|----------------------|--------------|---------|-----------| +| [Product A] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | +| [Product B] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | +| [Product C] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | + +### Portfolio Health +- Stars: [N] -- Funded adequately? [Y/N] +- Cash Cows: [N] -- Generating sufficient surplus? [Y/N] +- Question Marks: [N] -- Clear invest/divest decision for each? [Y/N] +- Dogs: [N] -- Wind-down plans in place? [Y/N] + +### Cash Flow Dynamics +- Total cash generated (Cash Cows): [$X] +- Total cash consumed (Stars + Question Marks): [$X] +- Net portfolio cash flow: [+/- $X] +- Sustainability assessment: [Self-funding / Requires external capital / Unsustainable] + +### Strategic Decisions Required +| Decision | Options | Recommendation | Financial Impact | +|----------|---------|---------------|-----------------| +| [Product/market decision] | [Option A vs. Option B] | [Recommendation] | [Projected impact] | + +### Resource Reallocation Plan +| From | To | Amount | Rationale | +|------|----|--------|-----------| +| [Source product/unit] | [Target product/unit] | [$X or X headcount] | [Why this reallocation] | + +### 12-Month Portfolio Trajectory +| Product | Current Quadrant | Projected Quadrant | Key Assumption | +|---------|-----------------|-------------------|----------------| +| [Product] | [Current] | [Projected] | [What must be true] | +``` + +--- + +## Related Skills + +- **[Product Life Cycle](product-life-cycle.md)** -- The BCG matrix and the product life cycle are deeply intertwined; products naturally move from Question Mark (introduction) to Star (growth) to Cash Cow (maturity) to Dog (decline). +- **[Balanced Scorecard](balanced-scorecard.md)** -- While the BCG matrix drives portfolio-level resource allocation, the Balanced Scorecard measures execution effectiveness within each product or business unit. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- PEST identifies the macro forces that determine market growth rates; SWOT reveals the competitive factors that determine relative market share. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Disruption often transforms a Cash Cow into a Dog faster than the BCG matrix's gradual trajectory suggests, making Christensen's framework the essential early warning system. +- **[Ambidexterity](ambidexterity.md)** -- The BCG matrix reveals why ambidexterity is structurally necessary: Cash Cows fund exploitation while Question Marks and Stars represent the exploration portfolio. +- **[Evaluating Options](../decisions/evaluating-options.md)** -- Provides structured decision-making methods for the invest-or-divest choices that the BCG matrix forces on Question Mark products. diff --git a/plugins/foreman/content/skills/frameworks/hackman-enabling-conditions.md b/plugins/foreman/content/skills/frameworks/hackman-enabling-conditions.md new file mode 100644 index 0000000..35a5536 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/hackman-enabling-conditions.md @@ -0,0 +1,220 @@ +--- +name: "hackman-enabling-conditions" +description: "Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance probable. Use when teams are underperforming despite talent, designing new team structures, onboarding a leadership hire, auditing why a specific team is stuck, or building the organizational infrastructure for effective teams at scale." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - team-effectiveness + - organizational-design + - management + - team-structure + - leadership + - performance +related_skills: + - belbin-team-roles + - tuckman-team-stages + - lewin-leadership-styles + - situational-leadership + - leadership-pipeline +author: "Fatih Guner" +--- + +# Hackman's Enabling Conditions for Team Effectiveness + +Most team failures are not the team's fault. This is the central, uncomfortable conclusion of J. Richard Hackman's decades of research at Harvard on team performance -- research that studied airline cockpit crews, intelligence analysts, symphony orchestras, and corporate project teams. When a team underperforms, the reflexive organizational response is to blame the people: not talented enough, not motivated enough, not collaborative enough. Hackman's research redirects attention upward. In the majority of cases, the team fails because the conditions for success were never established. The soil was toxic; blaming the seeds for not growing is both lazy and wrong. + +Hackman published his definitive framework in *Leading Teams: Setting the Stage for Great Performances* (2002), identifying five conditions that, when present, make team effectiveness probable -- and when absent, make it improbable regardless of how talented, committed, or well-intentioned the team members are. The framework shifts the leader's primary task from managing the team to designing the environment in which the team operates. + +--- + +## The Framework + +Hackman's five enabling conditions form a hierarchy: each builds upon the previous. Condition 1 is foundational; without it, the others are meaningless. Condition 5 is the capstone, rarely present but transformative when it is. + +### Condition 1: Being a Real Team + +**The checklist question:** Is this group actually a team, or merely a collection of individuals who report to the same manager? + +A real team has three properties: +- **Clear boundaries** -- Everyone knows who is on the team and who is not. Ambiguous membership diffuses accountability and prevents cohesion. +- **Interdependence** -- Members need each other to accomplish the work. If everyone can complete their tasks independently, you have a workgroup, not a team -- and workgroups require different management. +- **Stability** -- Membership remains reasonably constant. Hackman's research shows that teams with frequent membership changes never reach high performance because they perpetually reset to Tuckman's Forming stage. + +**Why this fails in startups:** Founders often create "teams" that are actually loosely affiliated individuals working on adjacent tasks. The engineering "team" may consist of people building independent features who never need to coordinate. Calling them a team creates expectations of collaboration without the structural reality of interdependence. + +### Condition 2: Compelling Direction + +**The checklist question:** Does the team have a purpose that is clear, challenging, and consequential? + +Compelling direction has three qualities: +- **Clear** -- The team knows what it is trying to achieve. Not a vague mission statement, but a specific outcome that can be assessed. +- **Challenging** -- The goal stretches the team beyond comfortable execution. Hackman found that moderately challenging goals produce higher performance than easy goals or impossibly ambitious ones. +- **Consequential** -- The work matters. To the organization, to customers, to the team members themselves. Teams that perceive their work as trivial perform trivially. + +**Why this fails in startups:** Ironically, early-stage startups often have too much direction (the founder's passionate vision) rather than too little -- but the direction is not translated into specific, assessable team-level goals. "Change the world" is not a compelling direction. "Achieve 1,000 daily active users by Q3" is. + +### Condition 3: Right People + +**The checklist question:** Does the team have the right mix of skills, experience, and interpersonal abilities? + +Right people means: +- **Technical competence** sufficient for the task +- **Interpersonal skill** sufficient for collaboration +- **Diversity of perspective** sufficient for creative problem-solving +- **Absence of members who are actively destructive** -- Hackman's research shows that one member who is persistently aggressive, cynical, or disengaged can reduce team performance by 30-40% + +**Why this fails in startups:** Founders hire for technical skill and ignore interpersonal fit. Or they hire friends and ignore skill gaps. Belbin's team roles framework provides the granular lens for this condition; Hackman provides the structural imperative. + +### Condition 4: Sound Structure + +**The checklist question:** Does the team have the right norms, roles, and task design? + +Sound structure includes: +- **Task design** that is whole and meaningful -- not fragmented into pieces so small that no one sees the whole +- **Team size** that is as small as possible for the task (Hackman found that the right number is almost always fewer than managers think) +- **Clear norms** about communication, decision-making, conflict resolution, and quality standards +- **Explicit roles** that leverage individual strengths without creating rigid silos + +**Why this fails in startups:** Over-reliance on flat structures and informal norms. "We don't need process" is the rallying cry of teams that eventually discover they desperately need process -- usually after a painful failure that clear norms would have prevented. + +### Condition 5: Supportive Organizational Context + +**The checklist question:** Does the broader organization provide the resources, information, and support the team needs? + +Supportive context means: +- **Reward systems** that recognize team performance, not just individual achievement +- **Information systems** that give the team access to the data it needs +- **Educational systems** that provide training and development +- **Material resources** sufficient for the work -- tools, budget, time + +**Why this fails in startups:** Resource scarcity is endemic. But the more pernicious failure is reward structure: startups that celebrate individual heroes while their team objectives languish systematically undermine this condition. + +### The Sixth Condition: Expert Coaching (Bonus) + +Hackman later added a sixth condition: the availability of competent coaching at the right time. Not a permanent coach hovering over the team, but a skilled intervener who can help the team at three critical moments -- the beginning (establishing norms), the midpoint (course-correcting), and the end (learning from the experience). + +--- + +## Prompts + +**Prompt 1 -- Five Conditions Audit:** +> Evaluate my team against Hackman's five enabling conditions. Here's the context: Team size: [number]. Team purpose: [describe]. Members: [describe]. How we work: [describe structure, norms, processes]. Organizational context: [describe resources, reward systems, information access]. Score each condition (Strong / Adequate / Weak / Absent) with specific evidence, and identify the single most impactful condition to improve first. + +**Prompt 2 -- "Real Team" Diagnostic:** +> I suspect my "team" may not actually be a real team in Hackman's definition. Here's how we work: [describe the group's membership clarity, interdependence level, and membership stability]. Diagnose whether we are a real team, a workgroup, or something in between. If we're not a real team, should we become one (by restructuring for interdependence) or should we acknowledge we're a workgroup and manage accordingly? + +**Prompt 3 -- Structural Redesign:** +> My team of [size] working on [project/function] has the right people and a clear direction but is underperforming. Using Hackman's Condition 4 (Sound Structure), analyze our current structure: [describe team norms, roles, task design, meeting cadence, decision-making process]. Identify structural deficiencies and propose specific changes to norms, roles, or task design that would improve effectiveness. + +**Prompt 4 -- Organizational Context Gap Analysis:** +> My team performs well internally but is frustrated by organizational barriers. Using Hackman's Condition 5, analyze these friction points: [describe -- e.g., "We can't get data from the analytics team," "Our bonus structure rewards individual goals," "We don't have budget for the tools we need"]. Prioritize which context failures are most damaging to team effectiveness and propose solutions I can implement or advocate for. + +--- + +## Use Cases + +**High-Talent Team Delivering Mediocre Results** + +A growth-stage fintech company has assembled an expensive product team: former Google engineers, a designer from Stripe, a product manager from Uber. Individual resumes are impeccable. Output is disappointing. The CEO's instinct is to question individual commitment. A Hackman audit reveals the real problems. Condition 1: boundaries are unclear -- three other people occasionally contribute to the team's work without formal membership. Condition 2: direction is vague -- "make the product best-in-class" is not a compelling, assessable goal. Condition 4: no explicit norms exist for decision-making, so every disagreement becomes a negotiation from first principles. The people are right (Condition 3). The organizational context provides adequate resources (Condition 5). Fixing Conditions 1, 2, and 4 -- clarifying membership, setting specific goals, and establishing decision-making norms -- transforms team output within one quarter without changing a single person on the team. + +**Remote Team Lacking Supportive Context** + +A scale-stage company's remote customer success team consistently underperforms its in-office counterpart. Management attributes this to the inherent limitations of remote work. A Hackman analysis tells a different story. Condition 5 is severely compromised: the remote team lacks access to the real-time customer data available on the office dashboard, the reward system celebrates "visible effort" that inherently favors office workers, and the training programs are designed for in-person delivery with no remote adaptation. The team itself is sound (Conditions 1-4 are adequate). The organizational context is failing them. Redesigning information access, reward criteria, and training delivery for remote parity closes the performance gap within two quarters. + +--- + +## Anti-Patterns + +- **Blaming People Before Auditing Conditions.** The default organizational response to team failure: assume the people are the problem. Hackman's research demonstrates that replacing team members while leaving dysfunctional conditions intact produces the same poor results with different faces. Audit conditions before auditing people. + +- **Over-investing in Coaching While Neglecting Structure.** Hiring team coaches, running offsites, and investing in "team chemistry" while the team lacks clear boundaries, a compelling direction, or sound structural norms. Coaching is Hackman's sixth condition -- a bonus that enhances a solid foundation. Coaching cannot compensate for structural deficiency. + +- **Treating Every Group as a Team.** Not all work requires teamwork. Some work is best done by individuals coordinated through a manager. Forcing team structures onto independent work creates the overhead of coordination without the benefit of interdependence. Hackman explicitly distinguishes real teams from workgroups and argues that both are valid -- the error is misclassifying one as the other. + +- **Assuming Conditions Are Set Once.** Treating the five conditions as a launch checklist rather than ongoing maintenance requirements. Conditions degrade. Membership changes erode Condition 1. Shifting strategy undermines Condition 2. Scaling introduces new resource constraints that compromise Condition 5. Periodic re-auditing is essential. + +- **Optimizing the Wrong Condition First.** Investing in team skills training (Condition 3) when the real bottleneck is unclear direction (Condition 2). The conditions form a rough hierarchy; addressing lower-numbered conditions first typically yields higher returns. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establishing Conditions 1-3 | The founding team must become a real team with clear direction and the right mix of people; structure and organizational context are informal but sufficient at small scale | +| Growth | Formalizing Condition 4 | As teams multiply and grow, sound structure becomes the differentiator; informal norms that worked at 10 people fail at 50 | +| Scale | Building Condition 5 systemically | Organizational context -- reward systems, information access, resource allocation -- becomes the primary enabler or blocker of team effectiveness at scale | + +--- + +## Output Template + +```markdown +# Hackman Enabling Conditions Audit: [Team Name] + +**Date:** [Date] +**Team:** [Name and purpose] +**Auditor:** [Your role] + +## Condition Assessment + +### 1. Real Team +- **Clear boundaries:** [Yes/No -- who's in, who's out?] +- **Interdependence:** [High/Medium/Low -- do members need each other?] +- **Stability:** [Stable/Unstable -- recent membership changes?] +- **Score:** [Strong / Adequate / Weak / Absent] +- **Evidence:** [Specific observations] + +### 2. Compelling Direction +- **Clarity:** [Can every member state the goal identically?] +- **Challenge:** [Is the goal stretching but achievable?] +- **Consequence:** [Does the work matter?] +- **Score:** [Strong / Adequate / Weak / Absent] +- **Evidence:** [Specific observations] + +### 3. Right People +- **Technical competence:** [Sufficient/Gaps in ___] +- **Interpersonal skill:** [Strong/Adequate/Problematic] +- **Diversity of perspective:** [Sufficient/Limited] +- **Destructive members:** [None/Concern about ___] +- **Score:** [Strong / Adequate / Weak / Absent] + +### 4. Sound Structure +- **Task design:** [Whole and meaningful / Fragmented] +- **Team size:** [Right-sized / Too large / Too small] +- **Norms:** [Explicit and functional / Implicit / Absent] +- **Roles:** [Clear / Ambiguous / Conflicting] +- **Score:** [Strong / Adequate / Weak / Absent] + +### 5. Supportive Context +- **Rewards:** [Team-oriented / Individual-oriented] +- **Information access:** [Sufficient / Restricted] +- **Training:** [Available / Absent] +- **Resources:** [Sufficient / Constrained] +- **Score:** [Strong / Adequate / Weak / Absent] + +## Priority Intervention +**Weakest condition:** [Number and name] +**Recommended action:** [Specific intervention] +**Expected impact:** [What improvement to expect] +**Timeline:** [How long before results] + +## Overall Team Effectiveness Forecast +[Based on condition scores, predict team trajectory and recommend focus areas] +``` + +--- + +## Related Skills + +- **[Belbin Team Roles](belbin-team-roles.md)** -- Belbin provides the detailed lens for Hackman's Condition 3 (Right People), specifying which behavioral roles the team needs for balance. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Hackman's conditions create the environment through which Tuckman's developmental stages unfold; poor conditions stall the team permanently in Forming or Storming. +- **[Psychological Safety](psychological-safety.md)** -- Edmondson's psychological safety is the interpersonal climate dimension within Hackman's Condition 4 (Sound Structure) and Condition 5 (Supportive Context). +- **[Leadership Pipeline](leadership-pipeline.md)** -- Senior pipeline passages are fundamentally about creating Hackman's conditions for the teams and organizations one leads, shifting focus from personal contribution to environment design. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- Provides the leadership practices for building and maintaining the enabling conditions across growing and evolving teams. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- Condition 5 (Supportive Context) requires leaders to delegate genuine authority and resources, not just tasks, to enable team effectiveness. diff --git a/plugins/foreman/content/skills/frameworks/johari-window.md b/plugins/foreman/content/skills/frameworks/johari-window.md new file mode 100644 index 0000000..9e671b3 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/johari-window.md @@ -0,0 +1,190 @@ +--- +name: "johari-window" +description: "Improves self-awareness, trust, and team communication using the Johari Window model with its four panes: Open (known to self and others), Blind Spot (known to others, not self), Hidden (known to self, not others), and Unknown. Use when building trust within teams, identifying leadership blind spots, improving co-founder communication, designing feedback rituals that expand the Open pane, diagnosing why a team suffers from misinterpretation and defensive posturing, or developing self-awareness as a leadership competency." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - early-traction + - growth + - scale +tags: + - self-awareness + - feedback + - trust + - team-dynamics + - communication +related_skills: + - emotional-intelligence + - psychological-safety + - myers-briggs-type-indicator + - grow-model +author: "Fatih Guner" +--- + +# Johari Window + +What do the people you work with most closely know about you that you do not know about yourself? The question is uncomfortable precisely because the answer, by definition, is invisible to the person it most concerns. Joseph Luft and Harrington Ingham -- whose first names combine to form "Johari" -- devised their four-pane window model in 1955 at the University of California, Los Angeles, as a tool for understanding self-awareness in group settings. Six decades later, it remains one of the most intuitively powerful frameworks for diagnosing trust, communication, and relational effectiveness in teams. Its enduring utility lies in a simple geometric truth: the less a team knows about each other's thinking, motivations, and concerns, the more organisational energy is wasted on misinterpretation, defensive posturing, and avoidable conflict. + +--- + +## The Framework + +The Johari Window divides information about a person into four quadrants based on two axes: what is known to the self and what is known to others. + +### The Four Quadrants + +``` + Known to Self Unknown to Self + ┌─────────────────────┬─────────────────────┐ + │ │ │ + Known to │ OPEN │ BLIND SPOT │ + Others │ (Arena) │ │ + │ │ │ + ├─────────────────────┼─────────────────────┤ + │ │ │ + Unknown to │ HIDDEN │ UNKNOWN │ + Others │ (Facade) │ │ + │ │ │ + └─────────────────────┴─────────────────────┘ +``` + +**Open (Arena)** -- Information known to both self and others. This is the quadrant of effective communication: shared understanding, transparent motivations, acknowledged strengths and weaknesses. The larger this quadrant, the more efficiently the relationship functions. Communication requires less guesswork, trust is higher, and collaboration is more fluid. + +**Blind Spot** -- Information known to others but not to self. These are the behaviours, habits, communication patterns, and impacts that others observe but the individual does not recognise. A founder who believes she is collaborative but whose team experiences her as directive has a blind spot. The gap between self-perception and others' perception is the territory of this quadrant. + +**Hidden (Facade)** -- Information known to self but not shared with others. Fears, insecurities, strategic calculations, past experiences, personal motivations -- the things a person knows about themselves but chooses (consciously or unconsciously) to withhold. A founder who is privately worried about running out of capital but presents confidence to the team is operating with a large Hidden quadrant. + +**Unknown** -- Information unknown to both self and others. Latent talents, unconscious motivations, repressed experiences, undiscovered potential. This quadrant shrinks through novel experiences, deep reflection, coaching, and sometimes crisis -- which has a way of revealing capabilities and vulnerabilities that normal conditions do not surface. + +### The Two Mechanisms of Change + +The Johari Window is dynamic. The quadrant sizes shift through two deliberate actions: + +**Self-disclosure** moves the boundary between Hidden and Open. When a person shares information about themselves -- their concerns, motivations, uncertainties, values -- the Open quadrant expands downward at the expense of the Hidden quadrant. For entrepreneurs, strategic self-disclosure builds trust: an investor who understands the founder's genuine concerns makes better-informed decisions than one who only sees the facade. + +**Feedback-seeking** moves the boundary between Blind Spot and Open. When a person actively solicits and receives honest feedback, the Open quadrant expands rightward at the expense of the Blind Spot. For founders, feedback is the only mechanism for closing the gap between how they perceive their leadership and how it is actually experienced. + +The interaction between these two mechanisms is multiplicative. Self-disclosure invites reciprocal disclosure. Feedback-seeking, when received non-defensively, encourages others to give more feedback. The result is a virtuous cycle that progressively enlarges the Open quadrant -- which is the quadrant where productive work happens. + +### The Window at Team Level + +While originally designed for interpersonal relationships, the Johari Window applies to teams and organisations. An organisation's "Open" quadrant is its shared understanding: strategy, values, challenges, and information that everyone has access to. Its "Hidden" quadrant is what leadership knows but does not share (strategic plans, financial concerns, personnel issues). Its "Blind Spot" is what employees, customers, or the market perceive but leadership does not recognise. Its "Unknown" quadrant is the unexamined potential and latent risks that no one has yet identified. + +Startups tend to have large Open quadrants in their earliest days (when everyone is in one room and information flows freely) and progressively smaller ones as they grow -- unless deliberate mechanisms are built to counteract the natural narrowing. + +--- + +## Prompts + +**Prompt 1 -- Personal Johari Audit:** +> Help me conduct a Johari Window self-assessment based on the following inputs. My self-perception: [describe how you see your leadership style, strengths, weaknesses, and impact on others]. Feedback I have received from others: [describe feedback -- formal and informal -- from co-founders, team, investors, mentors]. Identify likely blind spots (gaps between self-perception and feedback), hidden areas (things I know about myself that I am not sharing with my team), and hypothesise about potential unknowns. Recommend specific actions to expand my Open quadrant. + +**Prompt 2 -- Team Johari Mapping:** +> Map the Johari Window dynamics of my team based on these observations: [describe each team member's communication openness, receptivity to feedback, tendency to withhold information, and known blind spots]. For the team as a whole, assess the relative size of each quadrant. Identify the highest-leverage intervention: should we focus on increasing self-disclosure (team retreats, structured sharing), feedback (360 reviews, retrospectives), or both? Design a specific exercise we can run in our next team meeting to expand the Open quadrant. + +**Prompt 3 -- Investor Relationship Disclosure Strategy:** +> I am managing relationships with [number] investors. Help me design a strategic self-disclosure approach using the Johari framework. Here is what I currently share openly: [list]. Here is what I withhold: [list concerns, challenges, uncertainties you do not share]. For each hidden item, advise whether disclosure would build trust (move to Open) or is appropriately private (remain Hidden). For items I should disclose, recommend how and when to share them for maximum trust-building effect. + +--- + +## Use Cases + +**Early-traction co-founder relationship under strain** + +Two co-founders have been working together for 18 months. Surface communication is professional, but both harbour unspoken frustrations. The CEO resents the CTO's resistance to customer feedback (hidden); the CTO feels undervalued because the CEO takes credit in investor meetings (hidden). Neither has shared these concerns. Meanwhile, the CEO has a blind spot: she micromanages technical decisions without realising it. The CTO has a blind spot: his communication style reads as dismissive to non-technical team members. + +A facilitated Johari exercise maps the current state: both co-founders have large Hidden and Blind Spot quadrants with each other, despite working together daily. The intervention involves structured self-disclosure (each co-founder shares their three biggest unspoken concerns) followed by structured feedback (each shares one blind spot they have observed in the other). The conversation is uncomfortable but transformative. The CEO acknowledges her micromanagement and commits to defined decision boundaries. The CTO acknowledges his communication style and agrees to a monthly feedback check-in with the team. Eighteen months of accumulated friction dissolves in two hours of structured honesty. + +**Growth-stage company with an information silo problem** + +A 60-person company has evolved departmental silos where marketing, engineering, and sales each have large Hidden quadrants vis-a-vis the others. Engineering does not share technical constraints until they become crises. Marketing does not share campaign performance data that might reflect poorly on their work. Sales does not share customer complaints that contradict the company narrative. The CEO, aware that something is wrong but unable to pinpoint it, implements a Johari-informed transparency programme: cross-functional standups where each department shares one success, one challenge, and one concern from the week. The format is deliberately structured to normalise disclosure. Within a quarter, the inter-departmental Open quadrant expands measurably, reflected in fewer surprise escalations, faster cross-functional projects, and improved employee satisfaction scores. + +**Scale-stage executive discovering personal blind spots through 360 review** + +A CEO at a 300-person company commissions a 360-degree feedback review and discovers a jarring blind spot: while she perceives herself as approachable and open to dissent, 70% of direct reports describe her as "intimidating" and report self-censoring in her presence. The CEO's Johari Blind Spot quadrant is large. The corrective is not a single action but a sustained practice: the CEO begins each leadership meeting by explicitly inviting disagreement, publicly changes her position when persuaded, and asks a trusted lieutenant to provide real-time feedback on her nonverbal cues during discussions. Over six months, the 360 scores shift significantly -- not because the CEO changed her personality but because deliberate feedback-seeking and behavioural adjustment expanded her Open quadrant. + +--- + +## Anti-Patterns + +**1. Forced disclosure in a low-trust environment.** Running a Johari exercise before establishing baseline psychological safety produces performative sharing at best and genuine harm at worst. People share what they believe is safe to share, which in a low-trust environment means nothing meaningful -- or, worse, information that is later used against them. Psychological safety is a prerequisite, not a byproduct, of Johari work. + +**2. Treating all feedback as equally valid.** The Blind Spot quadrant contains genuine blind spots, but it also contains misperceptions. Not all feedback is accurate. A founder who accepts every piece of feedback uncritically risks distorting their self-model based on others' projections, biases, or limited perspectives. The skill lies in triangulating: feedback that appears from multiple independent sources is more likely to reflect a genuine blind spot. + +**3. Asymmetric disclosure.** When leaders demand transparency from their teams without reciprocating, the exercise becomes extractive rather than relational. The Johari Window works through mutual expansion of the Open quadrant. A CEO who asks the team to share concerns while keeping their own concerns hidden creates a surveillance dynamic, not a trust dynamic. + +**4. Confusing self-disclosure with oversharing.** Strategic self-disclosure is purposeful: sharing information that helps others work with you more effectively. Oversharing -- unburdening personal anxieties, sharing irrelevant personal details, or processing emotions publicly without regard for the audience -- erodes professional trust rather than building it. The question to ask before disclosing: "Will sharing this help the other person understand me better in a way that improves our working relationship?" + +**5. One-time exercise rather than ongoing practice.** A single Johari workshop produces a snapshot. The window's quadrants shift constantly as circumstances change, new people join, and new challenges emerge. Effective application requires regular, lightweight practices (weekly check-ins, quarterly feedback cycles) rather than annual events. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder transparency, founding team trust | Open quadrant is naturally large due to proximity; the priority is preventing Hidden and Blind Spot growth as the team begins to specialise | +| Growth | Cross-functional transparency, management feedback loops | Information silos form naturally as the organisation departmentalises; deliberate Johari practices counteract this tendency | +| Scale | Executive blind spots, organisational transparency, culture maintenance | The distance between leadership and frontline creates structural blind spots; formal mechanisms (360 reviews, skip-levels, anonymous channels) become essential | + +At early traction, the Johari Window is naturally favourable -- small teams in close quarters share information freely, feedback is constant, and little is hidden. The risk at this stage is complacency: assuming that transparency will persist without effort. As the team grows and specialises, Hidden quadrants expand (people withhold concerns to avoid rocking the boat) and Blind Spots calcify (the founder receives less honest feedback as power dynamics solidify). + +At growth, the architectural challenge emerges. Departments form, and with them information boundaries. Cross-functional Johari practices -- structured information-sharing rituals that counteract silo formation -- become a deliberate organisational investment. The founder must also reckon with their own growing Blind Spot: as the company grows, fewer people feel comfortable giving the founder candid feedback. + +At scale, the Johari Window becomes a governance tool. Executive blind spots at this stage can be catastrophic (recall any corporate scandal where "leadership didn't know" about a systemic problem that was visible to everyone else). Formal feedback mechanisms, anonymous reporting channels, and external advisory relationships are the structural equivalents of feedback-seeking in the original two-person model. + +--- + +## Output Template + +```markdown +# Johari Window Assessment -- [Individual/Team Name] + +**Prepared for:** [Individual / Team Lead] +**Date:** [Date] +**Context:** [Trigger for assessment -- e.g., team formation, conflict resolution, leadership development] + +## Current Window State + +### Quadrant Size Estimate (1-10 scale, where 10 = largest) +- **Open:** [Score] -- [Key evidence] +- **Blind Spot:** [Score] -- [Key evidence] +- **Hidden:** [Score] -- [Key evidence] +- **Unknown:** [Score] -- [Key evidence] + +## Blind Spot Analysis +| Blind Spot Identified | Source(s) | Confidence Level | Impact | +|----------------------|-----------|-----------------|--------| +| [Behaviour/pattern unseen by self] | [Who provided this feedback] | [High/Medium/Low -- based on triangulation] | [Effect on team/outcomes] | + +## Hidden Inventory +| Item Currently Hidden | Reason for Withholding | Disclosure Recommendation | Timing | +|----------------------|----------------------|--------------------------|--------| +| [Concern/information being withheld] | [Fear, strategy, habit] | [Disclose / Keep hidden / Partial disclosure] | [When and how] | + +## Expansion Plan + +### Self-Disclosure Actions +1. [Specific information to share, with whom, and when] +2. [Specific information to share, with whom, and when] + +### Feedback-Seeking Actions +1. [Specific feedback to request, from whom, and the question to ask] +2. [Specific feedback to request, from whom, and the question to ask] + +## Measurement +- **Reassessment date:** [When to re-evaluate quadrant sizes] +- **Leading indicators of Open quadrant growth:** [Observable changes to watch for] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](emotional-intelligence.md)** -- The self-awareness domain of EQ maps directly to the Johari process of reducing the Blind Spot quadrant, while empathy enables more effective feedback delivery. +- **[Psychological Safety](psychological-safety.md)** -- Safety is the precondition for both self-disclosure and honest feedback; without it, the Johari Window remains static regardless of the exercises attempted. +- **[Giving Feedback](giving-feedback.md)** -- The SBI model provides the structured method for delivering the feedback that shrinks the Blind Spot quadrant, turning Johari insights into actionable conversations. +- **[Radical Candor](radical-candor.md)** -- Scott's framework provides the courage and care required for the honest feedback exchanges that expand the Open quadrant in both directions. +- **[Leader Self-Reflection](../leadership/leader-self-reflection.md)** -- Provides the reflective practices that help leaders voluntarily shrink their Hidden quadrant and actively seek feedback to reduce their Blind Spots. +- **[Stoic Self-Awareness](../stoic/stoic-self-awareness.md)** -- The Stoic practice of rigorous self-examination complements the Johari framework by providing philosophical grounding for honest self-assessment. diff --git a/plugins/foreman/content/skills/frameworks/kaizen-bpr.md b/plugins/foreman/content/skills/frameworks/kaizen-bpr.md new file mode 100644 index 0000000..318b0f1 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/kaizen-bpr.md @@ -0,0 +1,216 @@ +--- +name: "kaizen-bpr" +description: "Applies two complementary process improvement philosophies: Kaizen (continuous incremental improvement) and Business Process Reengineering (radical process redesign from scratch). Helps determine when to refine existing processes versus when to tear them up and rebuild. Use when operational efficiency is declining, processes have accumulated technical debt, preparing for rapid scaling, diagnosing bottlenecks, choosing between incremental optimization and transformative redesign, or building a culture of continuous improvement." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - process-improvement + - operational-excellence + - continuous-improvement + - transformation + - lean-operations +related_skills: + - systems-thinking + - balanced-scorecard + - shamrock-organisation + - product-life-cycle +author: "Fatih Guner" +--- + +# Kaizen & Business Process Reengineering + +Two philosophies of improvement emerged from opposite ends of the industrial world, and they could hardly be more different in temperament. From Japan: Kaizen -- the quiet, relentless discipline of making things a little better every day. From America: Business Process Reengineering (BPR) -- the dramatic act of tearing up existing processes and rebuilding them from scratch. One whispers. The other shouts. Toyota embodied the first; Michael Hammer and James Champy evangelised the second in their 1993 manifesto *Reengineering the Corporation*. The genius lies not in choosing between them but in understanding when each is appropriate -- and recognising that most organisations need both, applied at different times and to different problems. + +--- + +## The Framework + +### Kaizen: The Continuous Improvement Philosophy + +Kaizen (Japanese: "change for better") is not a technique but a culture. Masaaki Imai introduced it to Western audiences in 1986, describing the management philosophy that powered Japan's post-war industrial ascent. The core principle is disarmingly simple: every process can be improved, every day, by the people who do the work. + +**Before Kaizen:** +- Improvement is a management responsibility +- Changes come in large, infrequent projects +- Workers execute; managers think +- Defects are found at inspection +- "Good enough" is the standard + +**After Kaizen:** +- Improvement is everyone's responsibility +- Changes come in small, continuous increments +- Workers observe, suggest, and implement improvements +- Defects are prevented at the source +- "Better than yesterday" is the standard + +**The Kaizen Cycle (PDCA):** + +1. **Plan** -- Identify a specific, measurable improvement opportunity. Define the current state and the target state. +2. **Do** -- Implement the change on a small scale. Treat it as an experiment, not a commitment. +3. **Check** -- Measure the results. Did the change achieve the target? What unexpected effects emerged? +4. **Act** -- If successful, standardise the new method. If not, analyse why and begin the cycle again. + +**Key Kaizen Principles:** +- Go to the Gemba (the actual place where work happens) -- do not improve processes from a conference room +- Eliminate Muda (waste) in all seven forms: overproduction, waiting, transport, overprocessing, inventory, motion, defects +- Respect the expertise of frontline workers -- they understand the process better than any consultant +- Small changes compound; a 1% daily improvement yields a 37x annual improvement mathematically + +### BPR: The Radical Redesign + +Business Process Reengineering rejects incrementalism. Hammer's famous dictum: "Don't automate, obliterate." BPR asks not "How do we improve this process?" but "If we were building this from nothing, how would we design it?" + +**Before BPR:** +- Processes evolve organically over years, accumulating complexity +- Departments optimise locally, creating handoffs and bottlenecks +- Technology is layered onto existing workflows +- The question is "How do we do this faster?" + +**After BPR:** +- Processes are redesigned around desired outcomes, not existing activities +- Cross-functional teams replace departmental handoffs +- Technology enables fundamentally new ways of working +- The question is "Why do we do this at all?" + +**The BPR Methodology:** + +1. **Identify** -- Select the process with the highest impact potential. Focus on processes that are broken, not merely slow. +2. **Understand** -- Map the current process end-to-end. Quantify cost, time, error rates, and customer impact. +3. **Redesign** -- Start from the desired outcome and work backward. Ignore existing constraints. Design the ideal process. +4. **Implement** -- Execute the redesign with full commitment. BPR is not a pilot; it is a replacement. +5. **Sustain** -- Monitor the new process and apply Kaizen to maintain and incrementally improve it. + +### When to Use Each + +| Dimension | Kaizen | BPR | +|-----------|--------|-----| +| **Scope of change** | Incremental, continuous | Radical, episodic | +| **Risk profile** | Low risk per change; cumulative impact | High risk; high reward or high failure | +| **Time horizon** | Ongoing, never-ending | Project-based, 6-18 months | +| **Who drives it** | Frontline workers and teams | Senior leadership and cross-functional teams | +| **Best when** | Process is fundamentally sound but inefficient | Process is fundamentally broken or obsolete | +| **Cultural requirement** | Trust, empowerment, psychological safety | Executive sponsorship, change management capability | +| **Failure mode** | Stagnation if management attention wanes | Organisational trauma if execution fails | + +The relationship is sequential, not competitive. BPR creates new processes; Kaizen refines them. An organisation that only does BPR lurches from revolution to revolution. An organisation that only does Kaizen risks polishing a process that should have been replaced entirely. + +--- + +## Prompts + +**Prompt 1 -- Process Waste Identification (Kaizen):** +> "Analyse this business process: [describe process step by step]. Identify all seven types of waste (overproduction, waiting, transport, overprocessing, inventory, motion, defects) present in the process. For each waste identified, propose a specific Kaizen improvement that could be implemented within one week by the team that owns the process." + +**Prompt 2 -- BPR Candidate Assessment:** +> "Evaluate these business processes for BPR suitability: [list 3-5 processes with brief descriptions]. For each, score on three dimensions: (1) how broken is the current process (1-10), (2) how significant is the business impact of improvement (1-10), (3) how feasible is radical redesign given our current resources and capabilities (1-10). Recommend which process to reengineer first and explain why." + +**Prompt 3 -- Zero-Base Process Design:** +> "Ignore how we currently handle [process name]. If we were designing this process from scratch today, with access to current technology and no legacy constraints, what would the ideal process look like? Define the desired outcome first, then design backward. Include the number of steps, roles involved, technology required, and expected cycle time." + +**Prompt 4 -- Kaizen Event Planning:** +> "Design a five-day Kaizen event (Kaizen Blitz) for improving [specific process]. Include: Day 1 objectives (current state mapping), Day 2-3 activities (root cause analysis and solution design), Day 4 actions (implementation), and Day 5 deliverables (measurement and standardisation). Specify the team composition needed and the metrics we should track before, during, and after the event." + +--- + +## Use Cases + +**Early-Traction Startup Reducing Customer Onboarding Time** + +A B2B SaaS company discovers that customer onboarding takes an average of 23 days -- far longer than the industry benchmark of 7 days. A Kaizen analysis of the process reveals seven handoffs between sales, customer success, and engineering, with an average wait time of 2.3 days per handoff. Rather than reengineering the entire process, the team implements incremental improvements: eliminating two unnecessary approval steps (3 days saved), creating a shared onboarding dashboard that replaces email-based status updates (4 days saved), and automating the technical provisioning step (5 days saved). Onboarding drops to 11 days in 30 days. A subsequent Kaizen cycle targets the remaining gap. + +**Growth-Stage Logistics Company Reengineering Order Fulfilment** + +A direct-to-consumer company processing 5,000 orders per day hits a wall. The fulfilment process, designed when volume was 200 orders per day, has been patched and extended so many times that it now involves 34 steps across four systems that do not communicate. Kaizen improvements yield marginal gains, but the fundamental architecture is broken. The company undertakes BPR: redesigning fulfilment around a single integrated platform, reducing the process to 12 steps, eliminating three manual data-entry points, and implementing batch processing for common order types. Fulfilment cost drops 40%, error rate drops 85%, and the process now scales to 20,000 orders per day without additional headcount. Post-launch, a Kaizen programme maintains and refines the new process. + +--- + +## Anti-Patterns + +**Kaizen Theatre.** Running suggestion programmes and improvement workshops without giving teams the authority, time, or budget to implement changes. Kaizen without empowerment is performance art. If management reviews but never approves suggestions, the programme dies within months. + +**BPR as Euphemism for Layoffs.** In the 1990s, BPR became corporate code for headcount reduction. When reengineering is perceived as a vehicle for redundancy rather than genuine process improvement, it poisons organisational trust and ensures that the people who best understand the processes will not participate honestly in redesigning them. + +**Incremental Improvement of a Broken Process.** Applying Kaizen to a process that needs BPR. Polishing a fundamentally flawed workflow yields diminishing returns and frustrates teams who can see that the underlying design is wrong. If the process architecture is the problem, incremental improvement is the wrong tool. + +**Big Bang Without Change Management.** Launching BPR without investing in the human side of transformation. New processes fail not because the design is wrong but because the people expected to execute them were not consulted, trained, or motivated. Hammer himself later acknowledged that BPR's failure rate -- estimated at 50-70% -- was largely attributable to neglecting the human dimension. + +**Measuring Activity Instead of Outcomes.** Counting the number of Kaizen suggestions submitted rather than the measurable improvement in process performance. Vanity metrics in improvement programmes are as dangerous as vanity metrics in product development. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establish process discipline | Introduce Kaizen thinking before processes calcify; document workflows early | +| Growth | Identify BPR candidates | Processes designed for 10 customers rarely work for 10,000; watch for breaking points | +| Scale | Institutionalise both | Formal Kaizen programmes (dedicated time, measurement, recognition) and periodic BPR reviews of major processes | + +At early traction, the primary risk is having no documented processes at all. Kaizen requires a baseline to improve upon. The first step is making the invisible visible: mapping how work actually flows, not how founders assume it flows. + +During growth, the signal for BPR is clear: when incremental improvements yield diminishing returns, when workarounds outnumber standard procedures, or when customer complaints cluster around a specific process. These are symptoms of a process that has outgrown its original design. + +At scale, the most effective organisations alternate rhythmically between Kaizen (continuous, distributed improvement) and periodic BPR (strategic, concentrated redesign). Toyota calls this the difference between "maintaining standards" and "raising standards." + +--- + +## Output Template + +**Target Audience: Operations Team / VP Operations** + +```markdown +# Process Improvement Assessment +## [Process Name] -- [Date] + +### Current State +- Process owner: [Name/Role] +- Steps: [Number] +- Average cycle time: [Duration] +- Error/rework rate: [Percentage] +- Monthly cost: [Amount] +- Customer satisfaction with this process: [Score/Feedback] + +### Waste Analysis (Kaizen Lens) +| Waste Type | Present? | Specific Instance | Estimated Impact | +|------------|----------|-------------------|-----------------| +| Overproduction | [Y/N] | [Description] | [Time/cost] | +| Waiting | [Y/N] | [Description] | [Time/cost] | +| Transport | [Y/N] | [Description] | [Time/cost] | +| Overprocessing | [Y/N] | [Description] | [Time/cost] | +| Inventory | [Y/N] | [Description] | [Time/cost] | +| Motion | [Y/N] | [Description] | [Time/cost] | +| Defects | [Y/N] | [Description] | [Time/cost] | + +### Recommendation: Kaizen or BPR? +- [ ] **Kaizen** -- Process is fundamentally sound; incremental improvement is appropriate +- [ ] **BPR** -- Process architecture is broken; radical redesign is required + +### Improvement Plan +| # | Change Description | Type (Kaizen/BPR) | Owner | Timeline | Expected Impact | +|---|-------------------|-------------------|-------|----------|-----------------| +| 1 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | +| 2 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | +| 3 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | + +### Success Metrics +- Target cycle time: [Duration] (from [Current]) +- Target error rate: [%] (from [Current]) +- Target cost: [Amount] (from [Current]) +- Review date: [Date] +``` + +--- + +## Related Skills + +- **[Systems Thinking](systems-thinking.md)** -- Process improvement requires understanding how changes in one process affect connected systems; Systems Thinking prevents optimising one process at the expense of others. +- **[Balanced Scorecard](balanced-scorecard.md)** -- Provides the strategic context for deciding which processes to improve and how to measure the impact across financial, customer, internal, and learning dimensions. +- **[Kotter's Change Model](kotter-change-model.md)** -- BPR's radical redesign is itself a major change initiative that benefits from Kotter's eight-step framework for building urgency, coalition, and sustainable adoption. +- **[Appreciative Inquiry](appreciative-inquiry.md)** -- Offers the strengths-based counterpart to Kaizen's waste-elimination focus; together they provide a complete improvement methodology that amplifies what works while removing what does not. +- **[Eisenhower Matrix](eisenhower-matrix.md)** -- Continuous improvement is a Quadrant II activity that the Eisenhower Matrix helps protect from the constant pull of urgent operational demands. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- Provides the structured problem-definition methodology needed before a Kaizen cycle or BPR initiative can begin effectively. diff --git a/plugins/foreman/content/skills/frameworks/kotter-change-model.md b/plugins/foreman/content/skills/frameworks/kotter-change-model.md new file mode 100644 index 0000000..c0bf3e5 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/kotter-change-model.md @@ -0,0 +1,184 @@ +--- +name: "kotter-change-model" +description: "Guides organizational change initiatives using Kotter's eight-step + model: creating urgency, forming a guiding coalition, developing a vision, + communicating the vision, empowering action, generating short-term wins, + consolidating gains, and anchoring changes in culture. Use when leading a + strategic pivot, implementing organizational restructuring, driving cultural + transformation, managing post-acquisition integration, rolling out new + processes at scale, or diagnosing why previous change efforts have failed." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - change-management + - leadership + - transformation + - organizational-culture + - implementation +related_skills: + - ambidexterity + - covey-seven-habits + - tuckman-team-stages + - balanced-scorecard +author: "Fatih Guner" +--- + +# Kotter's 8-Step Change Model + +Seventy percent of organizational change initiatives fail. That statistic, drawn from research spanning three decades and cited by John Kotter himself, should give pause to any founder contemplating a significant strategic shift. The failure rate is not declining. If anything, the acceleration of technological change has increased the number of transformation attempts without improving the success rate. Kotter, a Harvard Business School professor who spent his career studying why organizations resist change, distilled his findings into an eight-step model first published in his 1996 book *Leading Change*. The model remains the most widely taught change management framework in business schools worldwide -- not because it is novel, but because it is precise about where and why change efforts derail. + +--- + +## The Framework + +### The Eight Steps + +Kotter's model is sequential by design. Skipping steps or reordering them is the primary cause of failure. Each step builds the foundation for the next. + +**Step 1 -- Create a Sense of Urgency** +Change begins only when enough people believe the status quo is more dangerous than the unknown. Kotter found that 50% of transformations fail at this first step because leaders underestimate the complacency embedded in successful organizations. The urgency must be authentic, not manufactured panic. Data-driven evidence of market shifts, competitive threats, or internal decay is more persuasive than executive rhetoric. + +**Step 2 -- Build a Guiding Coalition** +No single leader can drive change alone. Assemble a coalition of individuals with enough power, expertise, credibility, and leadership to sustain the effort. The coalition must include people from across the organization -- not just senior management. Kotter emphasizes that coalitions need leadership skills (setting direction, motivating) in addition to management skills (planning, budgeting, organizing). + +**Step 3 -- Form a Strategic Vision and Initiatives** +The vision must be clear enough to explain in five minutes and compelling enough to generate genuine enthusiasm. Vague aspirations ("become more innovative") fail. Concrete, vivid descriptions of the future state succeed. The vision must be supported by a set of strategic initiatives -- specific actions that will move the organization from its current state to the envisioned one. + +**Step 4 -- Enlist a Volunteer Army** +Communicate the vision relentlessly and through every available channel. Kotter's research shows that most companies under-communicate their change vision by a factor of 10. Communication must be two-directional: not just broadcasting the vision but listening to concerns, addressing skepticism, and incorporating feedback. The goal is not compliance but genuine buy-in from a critical mass of the organization. + +**Step 5 -- Enable Action by Removing Barriers** +Structural and cultural barriers will impede even the most motivated change agents. These barriers include: organizational structures that undermine the vision, skills deficits, systems and processes designed for the old way, and supervisors who resist the change. Leaders must actively identify and dismantle these obstacles. + +**Step 6 -- Generate Short-Term Wins** +Transformation takes years, but people need evidence of progress within months. Plan for visible, unambiguous improvements that validate the change direction. Short-term wins serve three purposes: they reward the effort of change agents, they undermine cynics and resisters, and they build momentum for the harder phases ahead. + +**Step 7 -- Sustain Acceleration** +After initial wins, the danger is declaring victory prematurely. Kotter warns that the forces of tradition are powerful enough to reassert themselves within two to three years if the pressure relents. Use the credibility generated by short-term wins to tackle bigger, deeper changes -- systems, structures, and policies that remain aligned with the old way. + +**Step 8 -- Institute Change** +Anchor the new approaches in the organizational culture. Culture changes last, not first. New behaviors must be reinforced through promotion criteria, performance metrics, onboarding processes, and leadership modeling. Only when "this is how we do things here" reflects the new reality is the change complete. + +### The Two Accelerators + +In his later work, Kotter updated the model with two structural observations: + +- **The Dual Operating System**: Large organizations need both a management-driven hierarchy (for reliability) and a network-like structure (for agility and change). Change cannot be driven through hierarchy alone. +- **Continuous vs. Episodic Change**: The original model assumed discrete change events. Modern organizations face continuous change, requiring the eight steps to operate as an ongoing capability rather than a one-time program. + +--- + +## Prompts + +**Prompt 1 -- Change Readiness Assessment:** +> Assess my organization's readiness for a specific change initiative. The change is: [describe the change -- e.g., pivoting product focus, restructuring teams, adopting new technology, entering a new market]. My company is [describe: sector, stage, size, culture]. Evaluate readiness across Kotter's eight steps: Where are we strong? Where are we vulnerable? What is the most likely point of failure? Provide a readiness score (1-5) for each step and an overall assessment. + +**Prompt 2 -- Urgency Case Builder:** +> Help me build a compelling case for urgency around [describe the change needed]. My audience is [describe: team, board, investors, entire company]. What data, trends, competitive intelligence, or customer evidence would make the status quo feel untenable? Draft a 3-minute narrative I can deliver that creates genuine urgency without inducing panic. Include specific data points I should research and incorporate. + +**Prompt 3 -- Guiding Coalition Design:** +> I need to assemble a guiding coalition for [describe the change]. My organization has [describe key people, teams, and power dynamics]. Who should be in the coalition and why? What roles are essential -- formal authority, technical expertise, informal credibility, change energy? Identify potential resisters and how to either include them or neutralize their opposition. Map the coalition on a 2x2 of influence vs. commitment. + +**Prompt 4 -- Short-Term Win Planning:** +> My change initiative is [describe]. We are currently between Steps 4 and 5 of Kotter's model. Help me identify 3-5 short-term wins I can engineer within the next 60-90 days. Each win must be: visible to the broader organization, clearly connected to the change vision, and achievable with resources we already have. For each win, specify what success looks like, who owns it, and how we will communicate it. + +**Prompt 5 -- Culture Anchoring Plan:** +> We have been implementing [describe the change] for [timeframe] and are approaching Step 8 -- anchoring in culture. Help me design a plan to make this change permanent. What systems, processes, incentives, and rituals need to change? What stories should we tell and celebrate? What hiring and promotion criteria should reflect the new culture? What are the warning signs that the old culture is reasserting itself? + +--- + +## Use Cases + +**Growth-Stage Startup Transitioning from Founder-Led Sales to a Sales Organization** +A $5M ARR B2B startup has relied entirely on the founder for sales. With 40 employees and Series A funding, the company must build a repeatable sales process. The founder uses Kotter's model: establishing urgency by showing the team that current growth rates are unsustainable without a sales organization; building a guiding coalition that includes the new VP of Sales, two senior engineers (to ensure product-sales alignment), and the head of customer success; articulating a vision where every team member understands the ideal customer profile; enlisting the team through transparent communication about why this matters; removing barriers by investing in CRM and sales enablement tools; generating a short-term win when the first non-founder deal closes within 45 days; sustaining acceleration by iterating the sales playbook based on data; and anchoring the change by making quota attainment part of the company's cultural identity. + +**Scale-Stage Company Migrating to a New Technology Platform** +A 500-person company must migrate from a legacy monolith to microservices architecture -- a two-year effort that will disrupt every engineering team. The CTO applies the model rigorously: urgency is established through data showing that deployment speed has declined 40% year-over-year and incident rates have doubled; the guiding coalition includes both senior architects and respected individual contributors who can influence their peers; the vision describes a world where teams ship independently multiple times per day; barriers are removed by funding a dedicated platform team and modernizing CI/CD; short-term wins come from migrating one high-visibility service that immediately demonstrates faster deployments; and the change is anchored when new engineers are onboarded into the microservices paradigm as the default. + +--- + +## Anti-Patterns + +1. **Declaring victory after Step 6.** The most seductive and common mistake. Early wins feel so good that leaders announce the transformation is complete. The remaining two steps -- sustaining acceleration and anchoring in culture -- are where permanent change actually happens. Premature celebration allows the old culture to reassert itself quietly. + +2. **Skipping Step 1 because leadership is already convinced.** The fact that the CEO believes change is necessary does not mean the organization does. Urgency must be felt broadly, not just at the top. Leaders who skip urgency-building find themselves pushing change onto resistant teams rather than leading willing participants. + +3. **Building a coalition of loyalists rather than influencers.** The guiding coalition needs credibility and diverse organizational reach, not just people who agree with the leader. Including a respected skeptic who becomes convinced is more powerful than including ten enthusiastic yes-sayers. + +4. **Communicating the vision once and expecting it to stick.** Kotter's research indicates that change visions are under-communicated by a factor of 10 to 100. A single all-hands meeting, email, or Slack message is laughably insufficient. The vision must be repeated, demonstrated, and referenced in every relevant context for months. + +5. **Attempting culture change first.** Culture is the output of sustained behavioral change, not the input. Leaders who begin with "we need to change our culture" have the causality backwards. Change the behaviors, systems, and incentives; culture follows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-driven pivots | At this stage, the "organization" is small enough that Kotter's model can be compressed. Urgency and vision often reside in the founder. The key challenge is Step 2 -- ensuring the small team genuinely buys in rather than merely complying. Short-term wins must come within weeks, not months. | +| Growth | Building organizational capabilities | The most common inflection point: transitioning from ad-hoc processes to scalable systems. Every element of the model matters. The guiding coalition must extend beyond the founding team. Communication becomes harder as the company grows past Dunbar's number. | +| Scale | Enterprise transformation | Full Kotter model deployed with formal program management. Change initiatives may run in parallel across divisions. The dual operating system concept becomes essential: hierarchy for stability, networks for change. Board engagement is critical at Steps 1-3. | + +--- + +## Output Template + +```markdown +# Change Initiative Plan (Kotter 8-Step) + +**Initiative:** [Name of the change] +**Sponsor:** [Executive owner] +**Timeline:** [Expected duration] +**Date:** [Date] + +## Step 1: Urgency +**Current urgency level:** [Low / Moderate / High] +**Key evidence for change:** +- [Data point or trend] +- [Competitive threat or opportunity] +- [Internal metric showing need] + +## Step 2: Guiding Coalition +| Name | Role | Why Included | Commitment Level | +|------|------|-------------|-----------------| +| [Name] | [Role] | [Reason] | [Champion/Supporter/Neutral/Skeptic] | + +## Step 3: Vision +**Vision statement (< 50 words):** [Statement] +**Strategic initiatives:** +1. [Initiative] +2. [Initiative] + +## Step 4: Communication Plan +- [Channel and frequency] +- [Key messages] + +## Step 5: Barriers to Remove +- [Barrier] → [Action to remove] + +## Step 6: Short-Term Wins (60-90 days) +1. [Win] -- Owner: [Name] -- Success criteria: [Criteria] +2. [Win] -- Owner: [Name] -- Success criteria: [Criteria] + +## Step 7: Acceleration Actions +- [Deeper change enabled by early wins] + +## Step 8: Anchoring Mechanisms +- [System/process/incentive changes to make it permanent] +``` + +--- + +## Related Skills + +- **[Organizational Ambidexterity](ambidexterity.md)** -- Building an ambidextrous organization is itself a major change initiative that benefits from Kotter's structured eight-step approach. +- **[Organisational Culture](organisational-culture.md)** -- Step 8 (anchoring in culture) requires deep understanding of Schein's cultural layers to ensure new behaviours become embedded rather than superficially adopted. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Teams undergoing change cycle through Forming, Storming, Norming, and Performing; understanding these dynamics helps calibrate the pace and communication of each Kotter step. +- **[Balanced Scorecard](balanced-scorecard.md)** -- Provides the measurement framework that makes short-term wins visible (Step 6) and sustains accountability through the later steps of the change process. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- Provides the leadership behaviours and communication practices needed to guide people through each of Kotter's eight steps effectively. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- Steps 3 and 4 (vision formation and communication) are fundamentally storytelling challenges where narrative skill determines whether the vision inspires action or falls flat. diff --git a/plugins/foreman/content/skills/frameworks/leadership-pipeline.md b/plugins/foreman/content/skills/frameworks/leadership-pipeline.md new file mode 100644 index 0000000..e9ed212 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/leadership-pipeline.md @@ -0,0 +1,194 @@ +--- +name: "leadership-pipeline" +description: "Diagnoses leadership development blockages using Charan's six passage transitions from individual contributor through enterprise manager. Evaluates skills, time allocation, and values shifts required at each leadership level. Use when founders cannot let go of operational tasks, managers are failing after promotion, succession planning is needed, or the organization is experiencing growth-stage leadership bottlenecks." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - growth + - scale +tags: + - leadership-development + - succession-planning + - organizational-design + - management + - talent + - scaling +related_skills: + - situational-leadership + - lewin-leadership-styles + - tuckman-team-stages + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +# The Leadership Pipeline + +A pipe carries fluid from one point to another. When the pipe is clean and correctly sized, flow is smooth and invisible -- you forget the plumbing exists. When the pipe is clogged, cracked, or the wrong diameter, the entire system backs up. Pressure builds in the wrong places. Things that should move freely stagnate. Eventually, something bursts. + +Ram Charan, Stephen Drotter, and James Noel proposed in *The Leadership Pipeline* (2001) that organizations are precisely such plumbing systems, and leadership development is the flow. Each transition from individual contributor to first-line manager to functional leader to business leader to enterprise leader represents a distinct passage -- a joint in the pipe -- where the diameter changes, the flow dynamics shift, and blockages most commonly occur. The vast majority of leadership failures are not failures of character or intelligence. They are passage failures: someone operating with the skills, time allocation, and values of a previous level while occupying a role that demands an entirely different set. The pipe is clogged, and the organization suffers the consequences. + +--- + +## The Framework + +The Leadership Pipeline defines six leadership passages, each requiring a fundamental transformation in three dimensions: skills (what you do), time application (how you spend your hours), and work values (what you believe matters most). + +### The Six Passages + +``` +Passage 6: Enterprise Manager + ^ + | [Values shift: long-term, visionary, portfolio thinking] +Passage 5: Group Manager + ^ + | [Values shift: strategic portfolio, business evaluation] +Passage 4: Business Manager + ^ + | [Values shift: P&L ownership, cross-functional integration] +Passage 3: Manager of Managers + ^ + | [Values shift: developing leaders, strategic resource allocation] +Passage 2: Manager of Others + ^ + | [Values shift: getting work done through others, not doing it yourself] +Passage 1: Managing Self (Individual Contributor) + [Values: technical proficiency, personal productivity, reliability] +``` + +### Passage 1 to 2: From Managing Self to Managing Others + +This is the passage where the greatest volume of blockage occurs and where startup founders feel it most acutely. The skills required shift from technical execution to planning, delegating, coaching, and measuring the work of others. Time application moves from doing the work to ensuring others do it. The value transformation is the most wrenching: the new manager must stop valuing personal technical contribution as the primary measure of worth and start valuing the success of their team. + +The blockage symptom: the manager who still writes code, still closes deals, still designs the product -- because that is where their identity lives. Their reports wait for direction, receive little coaching, and eventually leave. + +### Passage 2 to 3: From Managing Others to Managing Managers + +The second passage requires selecting and developing first-line managers rather than individual contributors. The leader must learn to assess managerial capability (not just technical capability), allocate resources across teams, and think two levels down. Time shifts from direct supervision to strategic coordination. + +The blockage symptom: the manager of managers who skips the middle layer, giving direction directly to individual contributors and undermining the first-line managers. The pipeline leaks talent at the manager level because they feel bypassed. + +### Passage 3 to 4: From Managing Managers to Functional Manager + +The functional manager oversees an entire function (engineering, marketing, finance) and must integrate the function's work with the broader business strategy. New skills include long-term functional strategy, mature cross-functional collaboration, and competing for resources at the executive level. + +The blockage symptom: the functional leader who optimizes their silo without understanding how it connects to (or constrains) other functions. Engineering builds beautifully without regard for what sales can actually sell. + +### Passage 4 to 5: From Functional Manager to Business Manager + +This is the most significant and underestimated transition. The business manager owns a P&L and must integrate all functions -- a fundamentally different cognitive task from excelling at one function. Long-term thinking, risk management, and external orientation (customers, competitors, market trends) become primary. + +The blockage symptom: the business manager who continues to over-index on their original function. The former VP of Engineering who, as General Manager, still spends 60% of their time on technical architecture while the commercial side atrophies. + +### Passage 5 to 6: From Business Manager to Group/Enterprise Manager + +The enterprise leader manages a portfolio of businesses and develops business managers. Success is measured in decades, not quarters. The skills are primarily about capital allocation, talent development at the most senior levels, and shaping organizational culture. + +The blockage symptom: the enterprise leader who cannot resist running one of the businesses directly, starving the others of strategic attention. + +--- + +## Prompts + +**Prompt 1 -- Pipeline Blockage Diagnosis:** +> My company is at [stage] with [number] employees. I'm experiencing these leadership challenges: [describe -- e.g., "My VP of Engineering still reviews every pull request," "My managers don't develop their people," "I can't step back from day-to-day operations"]. Using the Leadership Pipeline model, diagnose which passage transitions are blocked, what skills, time, and values shifts haven't occurred, and recommend specific interventions to clear the blockages. + +**Prompt 2 -- Founder Passage Planning:** +> As founder and CEO of a [stage] startup growing from [current size] to [target size], map my personal leadership pipeline journey. What passage am I currently navigating? What skills must I develop, what time allocation must change, and what values must I adopt to successfully make this transition? Be specific about what I need to stop doing, start doing, and continue doing. + +**Prompt 3 -- Succession Pipeline Design:** +> I need to build a leadership pipeline for my [function/company] that currently has [describe structure]. Identify the critical passage transitions that need to happen in the next 12-24 months, the people who are candidates for each transition, and the development programs or experiences that would prepare them. Flag any passages where we have no viable candidates -- these are our succession gaps. + +--- + +## Use Cases + +**Series B Startup Where the Founder Cannot Let Go** + +A Series B edtech company with 85 employees and $12M ARR has a founder-CEO who still approves every major product decision, attends every customer escalation call, and reviews every marketing campaign. The board has raised the issue twice. The founder genuinely believes no one else can do these things as well. A Leadership Pipeline analysis reveals the founder is stuck at Passage 1-2: still operating as a super-powered individual contributor managing others rather than managing managers who manage others. The intervention is threefold: hire a VP of Product (Passage 4 candidate), promote two senior engineers to engineering managers and invest in their Passage 1-2 transition, and create explicit decision-rights documentation that removes the founder from operational decisions. The founder's time allocation must shift from 80% execution / 20% strategy to the inverse. + +**Hypergrowth Company Losing Middle Management** + +A growth-stage marketplace company tripled headcount in 18 months. Attrition is concentrated at the manager level -- exactly the people promoted from individual contributor roles during the scaling surge. Pipeline analysis reveals a systemic Passage 1-2 failure: the company promoted its best engineers, designers, and salespeople into management roles without any transition support. These new managers were still valued (and valued themselves) for individual output, not team development. None received training in delegation, coaching, or performance management. The fix is a dedicated management development program focused on the three dimensions of the passage: skills workshops on delegation and feedback, time audits to shift from doing to managing, and explicit recalibration of what the company rewards -- measuring managers on team output, not personal heroics. + +--- + +## Anti-Patterns + +- **Promoting Based on Current-Level Excellence.** The single most common pipeline error: promoting the best salesperson to sales manager, the best engineer to engineering lead, the best analyst to analytics director. Excellence at level N is not evidence of readiness for level N+1. The skills, time application, and values are fundamentally different. Promotion should be based on evidence of next-level capabilities, not current-level performance. + +- **Skipping Passages.** Leapfrogging someone from individual contributor to managing managers, or from functional leader to enterprise leader, without adequate preparation at intermediate levels. Each passage builds capabilities that the next passage assumes. Skipping one creates leaders who lack foundational skills they cannot easily acquire under the pressure of a more senior role. + +- **Allowing Passage Regression.** Tolerating leaders who retreat to the comfort of a previous passage under stress. The VP of Engineering who starts coding again during crunch time. The CEO who takes over a sales call because the deal is "too important." Each regression reinforces the old values and signals to the organization that passage transitions are optional. + +- **Pipeline Without Development Infrastructure.** Diagnosing passage transitions without investing in the coaching, training, and mentoring required to support them. Telling a new manager to "manage, not do" without teaching them how is a recipe for failure and resentment. + +- **Ignoring the Values Dimension.** Focusing development exclusively on skills while neglecting the values transformation. A manager can learn delegation techniques in a workshop. Learning to genuinely value team success over personal contribution requires sustained coaching, reinforcement, and often a personal identity shift that workshops alone cannot produce. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Growth | Founder's Passage 1-2 and first management layer | The founder must navigate their own passage while simultaneously supporting the first generation of managers through theirs; this dual demand is the defining challenge of the growth stage | +| Scale | Building passages 2-4 systematically | The organization needs formal pipeline infrastructure: management development programs, assessment criteria for passage readiness, and succession planning at every level | + +--- + +## Output Template + +```markdown +# Leadership Pipeline Assessment: [Company Name] + +**Date:** [Date] +**Company Stage:** [Stage] +**Headcount:** [Number] +**Assessed by:** [Name/Role] + +## Current Pipeline Map + +| Person | Current Role | Pipeline Level | Operating At Level | Gap? | Blockage Description | +|--------|-------------|---------------|-------------------|------|---------------------| +| [Name] | [Role] | [Passage N] | [Passage N-1/N/N+1] | [Yes/No] | [Description if yes] | + +## Critical Blockages (Priority Order) + +### Blockage 1: [Person/Role] +- **Expected level:** [Passage N] +- **Operating at:** [Passage N-x] +- **Skills gap:** [What they can't yet do] +- **Time allocation gap:** [How they spend time vs. how they should] +- **Values gap:** [What they value vs. what they should value at this level] +- **Intervention plan:** [Specific actions, timeline, support needed] + +### Blockage 2: [Person/Role] +... + +## Succession Gaps + +| Role/Passage | Current Holder | Ready-Now Successor | Ready-in-12-Months | Development Needed | +|-------------|---------------|--------------------|--------------------|-------------------| +| [Role] | [Name] | [Name or NONE] | [Name or NONE] | [Development plan] | + +## 90-Day Pipeline Development Plan +1. [Priority action] +2. [Priority action] +3. [Priority action] + +## Investment Required +- **Training/coaching budget:** [Amount] +- **Time commitment from senior leaders:** [Hours/week] +- **External support needed:** [Coaches, programs, assessments] +``` + +--- + +## Related Skills + +- **[Situational Leadership](situational-leadership.md)** -- Each pipeline passage requires the leader to adopt different situational styles; a first-time manager needs more direction (S1-S2), while a business manager requires delegation and strategic support (S3-S4). +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Senior pipeline levels (Passages 3+) are primarily about creating the conditions Hackman describes rather than directing work. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Newly promoted managers often inherit or form new teams that restart the Tuckman cycle; understanding team stages helps navigate passage transitions. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- Every pipeline passage requires letting go of previous-level tasks, making delegation the core behavioral shift at each transition. +- **[Senior Leadership Transition](../leadership/senior-leadership-transition.md)** -- Addresses the practical challenges of moving into senior roles, directly complementing the pipeline's structural model of leadership passages. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- Pipeline transitions succeed when supported by coaching; managers at each passage need mentors who have navigated the same transition. diff --git a/plugins/foreman/content/skills/frameworks/lean-in.md b/plugins/foreman/content/skills/frameworks/lean-in.md new file mode 100644 index 0000000..fa03b3f --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/lean-in.md @@ -0,0 +1,163 @@ +--- +name: "lean-in" +description: "Applies Sandberg's Lean In framework to diagnose and address gender barriers in organizations, covering the ambition gap, mentor-sponsor deficit, and structural inclusion deficits. Use when designing inclusive hiring processes, building sponsorship programmes, analyzing gender diversity gaps, retaining senior women, or auditing promotion equity across the organization." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - gender + - diversity + - career-development + - inclusion +related_skills: + - radical-candor + - organisational-culture + - maslow-hierarchy + - carnegie-win-friends +author: "Fatih Guner" +--- + +# Lean In + +Women hold approximately 10% of CEO positions at Fortune 500 companies and represent fewer than 30% of senior management roles globally -- figures that have improved with glacial slowness over three decades. Sheryl Sandberg's *Lean In*, published in 2013, ignited a fierce debate by arguing that external barriers, while real, tell only half the story. The other half involves internal barriers: the ways women hold themselves back through internalised doubt, risk aversion, and premature career accommodation. The framework remains polarising precisely because it operates on two fronts simultaneously -- challenging systemic inequality while demanding individual agency. For entrepreneurs building companies, this dual lens is not optional. The startups that outperform on gender diversity show 25% higher probability of above-average profitability (McKinsey, 2020). The question is not whether to care about this, but how to operationalise it. + +--- + +## The Framework + +Sandberg's argument operates through a series of identified barriers -- some internal, some structural -- paired with specific prescriptions. The framework's strength lies not in any single recommendation but in the compound effect of addressing multiple barriers simultaneously. + +### Barrier 1: The Ambition Gap + +**The problem:** Research consistently shows that success and likability are positively correlated for men and negatively correlated for women. Women who assert ambition face social penalties men do not. Over time, many women internalise this dynamic and moderate their ambitions pre-emptively. + +**The prescription:** Sit at the table -- literally and figuratively. Take the seat at the conference table rather than the chair along the wall. Volunteer for high-visibility projects. Negotiate compensation with the same persistence expected of male counterparts. The evidence from negotiation research suggests that women who frame requests in communal terms ("this will help the team") face fewer likability penalties than those who frame them identically to men. + +### Barrier 2: The Mentor/Sponsor Deficit + +**The problem:** Men disproportionately receive sponsorship (active advocacy for advancement) rather than mere mentorship (advice without action). Senior leaders -- predominantly male -- more readily sponsor people who remind them of their younger selves, perpetuating homogeneity. + +**The prescription:** Distinguish mentorship from sponsorship. Seek sponsors who will stake political capital on your advancement, not merely advisors who dispense wisdom over coffee. Organisations should formalise sponsorship programmes rather than relying on organic relationships that replicate existing power structures. + +### Barrier 3: The "Leave Before You Leave" Phenomenon + +**The problem:** Women often begin accommodating hypothetical future caregiving responsibilities years before those responsibilities materialise. They decline stretch assignments, avoid relocations, or turn down promotions in anticipation of starting a family -- sometimes years in advance. The cumulative effect: by the time the decision point arrives, they have already moved to a slower career track. + +**The prescription:** Do not make career-limiting decisions based on events that have not yet occurred. Keep options open. Maintain maximum career velocity until the actual moment a trade-off must be made, then negotiate from a position of accumulated strength rather than pre-emptive retreat. + +### Barrier 4: The Myth of "Having It All" + +**The problem:** The aspiration to perform flawlessly in every role -- executive, parent, partner, community member -- produces paralysing guilt and eventual burnout. Perfectionism becomes the enemy of both career progress and personal fulfilment. + +**The prescription:** Redefine success as "having it all, but not all at the same time." Accept that trade-offs are permanent and guilt is a signal to examine priorities, not a verdict on adequacy. Build systems (domestic partnerships, childcare, delegation) that distribute responsibility rather than concentrating it. + +### Barrier 5: Institutional and Structural Deficits + +**The problem:** Even when individual women lean in, organisations may lack the infrastructure to support them: inadequate parental leave, inflexible work arrangements, promotion criteria that penalise career breaks, and evaluation systems riddled with unconscious bias. + +**The prescription:** Leaders -- particularly founders -- must build systems, not just issue exhortations. Structured interviews reduce bias. Transparent promotion criteria make advancement legible. Flexible work policies normalise caregiving for all genders. Sandberg acknowledged in later work that her initial emphasis on individual action underweighted structural reform; the mature framework addresses both. + +--- + +## Prompts + +**Prompt 1 -- Diversity Diagnostic:** +> Analyse my startup's gender diversity across three dimensions: representation (who is at each level), participation (who speaks in meetings, who gets stretch assignments), and advancement (promotion rates by gender over the past 12-24 months). Company details: [describe size, stage, industry, current team composition]. Identify which of Sandberg's barriers may be operating and recommend three concrete interventions. + +**Prompt 2 -- Inclusive Hiring Process Design:** +> Help me design a hiring process that mitigates unconscious gender bias at each stage: job description language, sourcing channels, screening criteria, interview structure, and offer negotiation. My company is at [stage] in [industry], and we currently have [describe team composition]. Use research on structured interviewing and Sandberg's insights on the ambition/likability double bind. + +**Prompt 3 -- Sponsorship Programme Architecture:** +> Design a formal sponsorship (not just mentorship) programme for my company of [size] employees. The programme should pair high-potential individuals with senior leaders who will actively advocate for their advancement. Include matching criteria, cadence, accountability mechanisms, and metrics to evaluate programme effectiveness after 12 months. + +**Prompt 4 -- Career Conversation Framework:** +> Create a structured framework for career conversations between managers and reports that addresses the "leave before you leave" dynamic and the ambition gap. The framework should help managers identify when reports may be self-limiting and provide language to surface and address those patterns constructively. Context: [describe your company culture and any observed patterns]. + +--- + +## Use Cases + +**Early-Traction B2B Startup Building Its First Leadership Team** +A founder with a seven-person team is making the first two director-level hires. The candidate pool skews 80% male. Applying the Lean In framework, the founder examines sourcing channels (over-reliance on personal networks), job descriptions (language analysis reveals "aggressive" and "dominant" descriptors that research shows depress female applications by 20-30%), and interview structure (unstructured interviews where rapport-based assessment favours similarity). Corrections at each stage double the proportion of qualified female candidates reaching final rounds. + +**Growth-Stage Company Losing Senior Women** +A 120-person company notices that women are promoted to director level at the same rate as men but leave the company within 18 months of promotion at twice the rate. A Lean In-informed analysis reveals that the company provides mentorship but not sponsorship to promoted directors; male directors receive informal sponsorship from the all-male executive team through golf outings and after-hours socialising that female directors cannot or do not access. The intervention: formalise sponsorship, restructure executive bonding to inclusive formats, and implement stay interviews at the 6- and 12-month marks post-promotion. + +**Scale-Stage Company Preparing for IPO** +A 500-person company faces investor scrutiny over board diversity ahead of its IPO. The executive team has one woman (the head of HR, a patterned appointment that reinforces stereotypes). Applying the framework's structural lens, the company audits its entire leadership pipeline, identifies the specific career stage where women's advancement stalls (the transition from VP to C-suite), and discovers that the evaluation criteria for C-suite readiness implicitly reward a profile shaped by male career patterns -- unbroken tenure, relocation willingness, 24/7 availability. Revising these criteria to value demonstrated impact rather than biographical pattern opens the pipeline. + +--- + +## Anti-Patterns + +1. **Individual Blame Disguised as Empowerment.** The most common misreading of Lean In: telling women to "just be more confident" without changing the systems that penalise confidence in women. Individual agency is necessary but insufficient. Founders who lean exclusively on personal-responsibility messaging while ignoring structural barriers are performing concern, not practicing inclusion. + +2. **Diversity as Optics.** Hiring one senior woman and declaring the problem solved. Token appointments without systemic change create impossible pressure on the appointee and provide false evidence that the system works. Pipeline metrics matter more than trophy hires. + +3. **Gender-Blind "Meritocracy."** Declaring that "we just hire the best person" while ignoring that definitions of "best" are culturally constructed and often encode masculine-default assumptions about leadership, communication style, and career trajectory. True meritocracy requires auditing what merit means in your organisation. + +4. **Ignoring Intersectionality.** Applying the Lean In framework as though all women share identical barriers. Race, class, disability, sexuality, and cultural background intersect with gender to produce distinct and compounding challenges. A framework that addresses gender in isolation will serve some women while leaving others behind. + +5. **Confusing Mentorship with Sponsorship.** Establishing a mentorship programme and expecting it to close the advancement gap. Mentors advise. Sponsors advocate. The distinction is not semantic; it is the difference between receiving guidance and receiving opportunities. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Foundational culture setting | Every hire is a cultural statement. Diversity at this stage is disproportionately influential because early employees become the template for future hires and the culture carriers as the company grows. | +| Growth | Pipeline and process | Scaling hiring demands structured processes. This is when informal practices that worked at 10 people -- "culture fit" interviews, network-based sourcing -- begin producing homogeneous teams unless deliberately counteracted. | +| Scale | Systems and accountability | At hundreds of employees, individual interventions give way to systemic ones: compensation audits, promotion rate analysis by demographic, board diversity targets, and executive accountability for inclusion metrics. | + +--- + +## Output Template + +```markdown +# Gender Equity & Inclusion Assessment: [Company Name] + +## Current State +- **Team composition by level:** [Executive / Director / IC breakdowns by gender] +- **Hiring pipeline:** [Application-to-offer ratios by gender] +- **Advancement data:** [Promotion rates by gender, past 12 months] +- **Retention data:** [Attrition rates by gender and level] + +## Barrier Analysis +| Barrier (Sandberg) | Evidence in Our Organisation | Severity | +|--------------------|------------------------------|----------| +| Ambition gap | [Observations] | High/Med/Low | +| Mentor vs. sponsor deficit | [Observations] | High/Med/Low | +| "Leave before you leave" | [Observations] | High/Med/Low | +| Structural/policy gaps | [Observations] | High/Med/Low | + +## Recommended Interventions +### Immediate (0-3 months): +- [Specific actions] +### Medium-term (3-12 months): +- [Specific actions] +### Long-term (12+ months): +- [Specific actions] + +## Success Metrics +- [Measurable outcomes to track quarterly] + +## Executive Accountability +- [Who owns each initiative and reports on progress] +``` + +--- + +## Related Skills + +- **[Radical Candor](radical-candor.md)** -- Sandberg's collaboration with Kim Scott produced the Radical Candor framework; the two models share DNA around creating environments where honest feedback transcends power dynamics. +- **[Organisational Culture](organisational-culture.md)** -- Gender barriers are deeply embedded in Schein's Layer 3 assumptions; surface-level diversity initiatives fail when underlying cultural assumptions go unexamined. +- **[Psychological Safety](psychological-safety.md)** -- Women lean in more effectively when the environment provides Edmondson's challenger safety, ensuring that assertiveness is met with respect rather than backlash. +- **[Inclusive Leadership](../leadership/inclusive-leadership.md)** -- Extends Sandberg's structural prescriptions into a leadership practice framework for building systems that actively counteract bias at every organizational level. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- The distinction between mentorship and sponsorship is central to Lean In; effective coaching programmes formalize advocacy rather than relying on organic relationships that replicate existing power structures. +- **[Leadership Pipeline](leadership-pipeline.md)** -- Pipeline analysis reveals the specific career stage where women's advancement stalls, enabling targeted interventions at the passage where structural barriers concentrate. diff --git a/plugins/foreman/content/skills/frameworks/lewin-leadership-styles.md b/plugins/foreman/content/skills/frameworks/lewin-leadership-styles.md new file mode 100644 index 0000000..8386bb9 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/lewin-leadership-styles.md @@ -0,0 +1,172 @@ +--- +name: "lewin-leadership-styles" +description: "Assesses leadership approach using Lewin's three styles: autocratic, democratic, and laissez-faire. Evaluates the fit between a leader's dominant style and their organizational context. Use when diagnosing team dysfunction caused by management style, transitioning from founder-led to distributed decision-making, navigating a crisis requiring temporary style shifts, or auditing the founding team's leadership dynamics." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - leadership + - management-style + - team-dynamics + - organizational-culture + - decision-making +related_skills: + - situational-leadership + - tuckman-team-stages + - belbin-team-roles + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +# Lewin's Leadership Styles + +Imagine three identical teams of ten people, each given the same project, the same deadline, and the same resources. The only variable is the leader. Team A's leader makes every decision, assigns every task, and monitors every output. Team B's leader sets the vision, then asks the team how they want to get there. Team C's leader says "figure it out" and retreats to their office. Kurt Lewin ran essentially this experiment in 1939 with groups of children -- and the results mapped with uncomfortable precision onto dynamics that play out in every startup, corporation, and nonprofit today. The autocratic group produced more output but lower quality and collapsed when the leader left. The democratic group produced slightly less volume but far higher quality and sustained performance independently. The laissez-faire group produced the least, with the most frustration and the worst interpersonal dynamics. + +Three styles. Three radically different organizational outcomes. Lewin's framework remains the foundation upon which all subsequent leadership theory was built. + +--- + +## The Framework + +Lewin identified three primary leadership styles along a spectrum of control. The framework is descriptive (leaders tend toward one style) and prescriptive (certain contexts reward certain styles). + +### The Three Styles Compared + +| Dimension | Autocratic | Democratic | Laissez-Faire | +|-----------|-----------|------------|---------------| +| **Decision authority** | Leader decides alone | Leader facilitates group input, then decides or delegates | Leader abdicates decision-making | +| **Communication flow** | Top-down, directive | Bidirectional, consultative | Minimal, reactive | +| **Team autonomy** | Low; tasks are assigned with specific instructions | Moderate; team participates in planning and execution choices | High in theory, chaotic in practice | +| **Speed of decisions** | Fast | Moderate | Slow or absent | +| **Innovation** | Low; risk-aversion dominates | High; diverse perspectives surface | Variable; depends entirely on team capability | +| **Team morale** | Low long-term; resentment builds | High; ownership breeds engagement | Low; absence of guidance feels like abandonment | +| **Quality of output** | Variable; depends on leader's expertise | Consistently high; collective intelligence corrects errors | Typically low; no quality standards enforced | +| **Scalability** | Poor; bottleneck at the leader | Strong; distributed decision-making scales | Unpredictable; works only with exceptional self-managing teams | +| **Leader absence impact** | Severe; work stops or quality collapses | Minimal; team continues autonomously | None; the leader was already functionally absent | + +### Autocratic Leadership + +The autocratic style concentrates authority in the leader. Decisions are made without consultation. Execution follows prescribed instructions. This style produces rapid decision-making and clear accountability -- valuable during crises, turnarounds, or situations requiring strict compliance. The cost is suppressed initiative, hidden information (team members withhold bad news from directive leaders), and a single point of failure. + +Founders default to this style more frequently than they realize. The founding period demands rapid, intuitive decision-making, and the habit persists long after the team has grown beyond the point where one brain can hold all relevant context. + +### Democratic Leadership + +The democratic style distributes authority while retaining ultimate responsibility. The leader sets direction, solicits input, facilitates deliberation, and either makes the final call or delegates it to the most capable team member. This is the style most consistently associated with high performance, innovation, and retention in Lewin's research and in subsequent decades of organizational studies. + +The cost is speed. Democratic processes take longer than autocratic ones. For startups racing against runway, this tradeoff is real. The art lies in knowing which decisions warrant democratic process and which do not. + +### Laissez-Faire Leadership + +The laissez-faire style delegates almost all authority and provides minimal guidance. Lewin's research consistently showed this style producing the worst outcomes -- not because autonomy is bad, but because laissez-faire as Lewin defined it implies abdication rather than intentional empowerment. + +The distinction matters enormously. A leader who deliberately builds systems, hires exceptional people, and then steps back is not practicing laissez-faire -- they are practicing high-trust democratic leadership. Lewin's laissez-faire leader provides neither structure nor support. The team is not liberated; it is abandoned. + +--- + +## Prompts + +**Prompt 1 -- Leadership Style Self-Assessment:** +> Based on the following description of how I typically lead my team, assess which of Lewin's three leadership styles I default to and how that style is affecting our performance. Here's how I operate: [describe your decision-making process, communication patterns, how you handle disagreements, how much autonomy you give team members, how you respond when things go wrong]. Identify the strengths of my current style, the costs I may not be seeing, and specific situations where I should consciously shift to a different style. + +**Prompt 2 -- Situational Style Selection:** +> I'm facing the following leadership challenge: [describe situation -- e.g., "We need to pivot our product in 4 weeks with a team of 8" or "We're scaling from 15 to 50 people and decisions are getting slower"]. Using Lewin's framework, which leadership style should I adopt for this specific situation and why? What would the autocratic, democratic, and laissez-faire approaches each look like here, and what are the risks of each? + +**Prompt 3 -- Team Dynamics Diagnosis:** +> My team is exhibiting these behaviors: [describe -- e.g., "People wait for me to make every decision," "Nobody takes initiative," "There's a lot of resentment about micromanagement," "We have great ideas but can't execute"]. Using Lewin's leadership styles framework, diagnose which leadership style is likely producing these symptoms, and recommend a transition plan to a more effective style for our context. + +**Prompt 4 -- Leadership Style Audit for the Founding Team:** +> Our founding team consists of [number] co-founders with these roles: [describe]. Each of us leads differently. Map each co-founder's style to Lewin's framework based on these descriptions: [describe each person's approach]. Analyze where our styles complement each other, where they conflict, and how we should allocate leadership responsibilities based on which style each situation demands. + +--- + +## Use Cases + +**Founder Transition from Autocratic to Democratic** + +A validation-stage fintech founder built the first version of the product through sheer force of will -- making every product decision, writing much of the code, dictating design choices. The company survived. Now at 20 employees, the same autocratic instincts are causing the best engineers to leave. Exit interviews reveal a consistent theme: "I felt like a pair of hands, not a brain." Applying Lewin's framework, the founder recognizes that the style appropriate for a three-person garage operation is toxic at the current scale. The transition plan involves categorizing decisions into three tiers: strategic (founder decides after consultation), tactical (team leads decide with founder input), and operational (team members decide autonomously). The shift is uncomfortable. Decisions take longer. But within six months, retention stabilizes and product velocity actually increases because the founder is no longer the bottleneck. + +**Crisis Requiring Temporary Autocratic Shift** + +A growth-stage e-commerce company with a normally democratic culture discovers a critical security breach exposing customer payment data. The CEO, who typically runs collaborative decision-making processes, recognizes that this moment demands autocratic leadership: clear commands, no debate, immediate execution. She assigns specific tasks to specific people, sets 30-minute check-in cycles, and makes every escalation decision herself for 72 hours. Once the crisis is contained, she deliberately shifts back to democratic mode for the post-mortem and remediation planning. Lewin's framework provides the vocabulary for this conscious style-switching -- and the team understands the shift because the CEO names it explicitly. + +--- + +## Anti-Patterns + +- **Permanent Autocracy Disguised as Startup Necessity.** The belief that startups require autocratic leadership indefinitely. Early-stage founding demands fast, centralized decisions -- but failing to evolve toward democratic leadership as the team grows is a primary driver of co-founder conflict and early-employee exodus. The startup excuse has an expiration date. + +- **Laissez-Faire as Flatness Ideology.** Adopting a leaderless or flat organizational structure and believing it represents enlightened management. Without deliberate structure, clear accountability, and active facilitation, "flat" organizations devolve into laissez-faire dysfunction: invisible hierarchies, diffused responsibility, and decision paralysis. Valve, GitHub, and other companies that experimented with radical flatness have documented the resulting pathologies extensively. + +- **Style Rigidity Across Contexts.** Applying the same style to every situation regardless of circumstances. A democratic process for deciding whether to evacuate a burning building is as dysfunctional as an autocratic process for designing a creative campaign. Lewin's framework is descriptive of tendencies but prescriptive of flexibility. + +- **Confusing Democratic with Consensus.** Believing democratic leadership means everyone must agree. Democratic leadership means everyone's input is heard and considered. The leader still decides. Consensus-seeking produces the worst of both worlds: the slowness of democracy without the decisiveness of autocracy. + +--- + +## By Stage + +| Stage | Recommended Dominant Style | Key Difference | +|-------|---------------------------|----------------| +| Idea | Autocratic with democratic elements | The founder's vision drives direction; small team size makes full democracy unnecessary, but co-founder input is essential | +| Validation | Democratic-leaning | Rapid experimentation benefits from diverse perspectives; the team must feel ownership of pivots | +| Early Traction | Democratic | Decision-making must distribute as the team grows beyond the founder's cognitive bandwidth | +| Growth | Democratic with role-based authority | Functional leaders adopt their own styles within their domains; founder sets culture and strategy | +| Scale | Institutional democratic | Formal processes, clear decision rights, and cultural norms replace the founder's personal style as the organizing principle | + +--- + +## Output Template + +```markdown +# Leadership Style Assessment: [Leader/Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Company Stage:** [Stage] + +## Current Style Profile + +| Leader/Role | Dominant Style | Secondary Style | Context Appropriateness | +|-------------|---------------|-----------------|------------------------| +| [Name] | [Autocratic/Democratic/Laissez-Faire] | [Style] | [High/Medium/Low] | + +## Situational Analysis + +### Decisions That Should Be Autocratic +- [Decision type]: [Why speed/clarity outweighs input] + +### Decisions That Should Be Democratic +- [Decision type]: [Why diverse input improves outcomes] + +### Decisions That Can Be Fully Delegated +- [Decision type]: [Why the team member is best positioned] + +## Transition Recommendations +1. [Specific behavior change] +2. [Specific process change] +3. [Specific communication change] + +## Risks of Current Style at Current Stage +- [Risk 1] +- [Risk 2] + +## Success Metrics +- [How you'll know the style shift is working] +``` + +--- + +## Related Skills + +- **[Situational Leadership](situational-leadership.md)** -- Hersey and Blanchard's framework extends Lewin by matching leadership style to follower maturity, providing a more granular decision model for style-switching. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- The stage of team development influences which leadership style is most effective; forming teams need more direction, performing teams need less. +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Hackman's research shows that the leader's primary job is creating conditions for team success, which aligns with democratic rather than autocratic leadership. +- **[Leadership Style Adaptation](../leadership/leadership-style-adaptation.md)** -- Provides practical guidance for shifting between leadership styles in response to context, extending Lewin's theoretical taxonomy into daily practice. +- **[Decision Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Crisis situations often demand a temporary shift to autocratic leadership; this skill addresses how to make that shift deliberately and return to democratic mode afterward. diff --git a/plugins/foreman/content/skills/frameworks/maslow-hierarchy.md b/plugins/foreman/content/skills/frameworks/maslow-hierarchy.md new file mode 100644 index 0000000..26ff208 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/maslow-hierarchy.md @@ -0,0 +1,209 @@ +--- +name: "maslow-hierarchy" +description: "Analyzes human motivation through Maslow's five-tier hierarchy of needs: physiological, safety, belonging, esteem, and self-actualization. Maps customer need levels for product positioning and employee motivation for retention strategy. Use when diagnosing employee disengagement despite good pay, repositioning product value propositions, auditing organizational maturity, or aligning incentives with the actual need level of the audience." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - motivation + - customer-psychology + - employee-engagement + - product-design + - human-needs + - organizational-culture +related_skills: + - smart-goals + - hackman-enabling-conditions + - situational-leadership + - four-ps-marketing +author: "Fatih Guner" +--- + +# Maslow's Hierarchy of Needs + +Turn the pyramid upside down. The most reproduced diagram in management education -- Abraham Maslow's five-level hierarchy, with physiological needs at the base and self-actualization at the apex -- has been drawn right-side-up so many times that people have stopped questioning it. Yet the most consequential insight for entrepreneurs sits at the top, not the bottom. Maslow's genius was not in observing that hungry people think about food. It was in arguing that once basic needs are met, human motivation does not plateau -- it transforms. The person whose survival is secure does not stop wanting; they start wanting differently. They want meaning, growth, purpose, and the realization of their potential. Companies that understand this build products people love and organizations people refuse to leave. Companies that do not understand this wonder why competitive salaries produce mediocre commitment and feature-rich products generate indifference. + +Maslow published "A Theory of Human Motivation" in 1943. Eight decades later, the hierarchy remains one of the most cited and most debated frameworks in psychology and management. Its critics are numerous and not always wrong. But the core architecture -- that human needs exist in layers, that lower layers must be substantially satisfied before higher layers become primary motivators -- continues to explain behavior that purely rational models cannot. + +--- + +## The Framework + +Maslow's hierarchy arranges human needs into five levels. The foundational claim is that needs at lower levels must be reasonably satisfied before needs at higher levels become dominant motivational forces. The framework is not a rigid staircase -- people can be motivated by multiple levels simultaneously -- but the general directional pull holds across cultures and contexts. + +### Level 1: Physiological Needs (Survival) + +**What it is:** The biological requirements for human survival -- food, water, shelter, sleep, warmth. + +**Business application -- Employees:** Salary sufficient to meet basic living costs. Physical workspace that is safe and functional. Work schedules that permit adequate rest. When these needs are unmet, nothing else matters. A company offering equity, purpose, and growth opportunities while paying below subsistence wages is building on sand. + +**Business application -- Customers:** Products that address fundamental needs command the most inelastic demand. Food delivery, housing platforms, healthcare services, basic financial tools. At this level, utility matters more than experience; reliability matters more than delight. + +**Startup lens:** Pre-revenue founders operating on personal savings are themselves at Level 1. Their decision-making is shaped by survival anxiety, which can produce both extraordinary focus and dangerous short-termism. + +### Level 2: Safety Needs (Security) + +**What it is:** Physical safety, financial security, health, protection from harm and instability. + +**Business application -- Employees:** Job security (or at least transparent communication about risks). Health benefits. Psychological safety -- the ability to speak up without fear of punishment. Clear policies and fair treatment. Startups that treat employment as perpetually precarious -- "we might run out of money any month" -- lock employees at Level 2, where their primary motivation is anxiety management rather than innovation. + +**Business application -- Customers:** Insurance, security systems, savings products, cybersecurity, data privacy. Products at this level sell peace of mind. The value proposition is the absence of a negative outcome rather than the presence of a positive one. + +**Startup lens:** Investors provide safety to founders by extending runway. The psychological shift that occurs when a startup raises funding is partly a Level 2 phenomenon: the founder's safety needs are temporarily satisfied, freeing cognitive resources for higher-level strategic thinking. + +### Level 3: Belonging Needs (Social Connection) + +**What it is:** Love, friendship, intimacy, community, sense of belonging to a group. + +**Business application -- Employees:** Team cohesion, company culture, social bonds with colleagues, feeling "part of something." Remote work challenges this level acutely -- belonging requires deliberate cultivation when it can no longer arise from physical proximity. Employee engagement surveys consistently show that "I have a best friend at work" correlates more strongly with retention than compensation. + +**Business application -- Customers:** Social networks, community platforms, brand communities, group fitness, co-working spaces. Products at this level succeed by creating or facilitating human connection. The product is often secondary to the community it enables -- CrossFit sells belonging that happens to involve exercise; Harley-Davidson sells identity that happens to involve motorcycles. + +**Startup lens:** Co-founder relationships operate at this level. The emotional bond between founders is both the startup's greatest asset and its greatest vulnerability. When belonging fractures -- and it often does under the pressure of startup life -- the company fractures with it. + +### Level 4: Esteem Needs (Recognition and Respect) + +**What it is:** Self-esteem, confidence, achievement, recognition by others, status, respect. + +**Business application -- Employees:** Public recognition of contributions. Meaningful titles (not inflated, but accurate). Autonomy that signals trust. Opportunities to develop mastery. The most corrosive force at this level is the perception that one's work does not matter or is not seen. Founders who absorb all credit while distributing all blame systematically destroy Level 4 satisfaction across their teams. + +**Business application -- Customers:** Luxury goods, premium services, professional certifications, status symbols, achievement platforms. Products at this level succeed by making the customer feel capable, respected, or admired. LinkedIn operates at Level 4 -- professional identity is a form of esteem management. + +**Startup lens:** Founder ego is a Level 4 phenomenon. The drive for recognition fuels entrepreneurship -- and can also distort decision-making when the founder's esteem needs conflict with the company's strategic needs. Founders who need to be the smartest person in the room hire people less smart than themselves. + +### Level 5: Self-Actualization (Becoming) + +**What it is:** The realization of personal potential, self-fulfillment, peak experiences, creativity, purpose. + +**Business application -- Employees:** Work that is intrinsically meaningful. Opportunities for creative expression. Alignment between personal values and organizational mission. Autonomy to pursue mastery. Self-actualization at work is rare and cannot be manufactured -- but the conditions that enable it can be designed. Hackman's enabling conditions and Pink's autonomy-mastery-purpose framework describe these conditions from different angles. + +**Business application -- Customers:** Education platforms, creative tools, coaching services, travel experiences, philanthropic products. Products at this level help people become who they want to be. Maslow's insight is that this motivation is not a luxury -- it is the natural culmination of satisfied lower needs, and its pull is immense. + +**Startup lens:** The most compelling startup missions appeal to self-actualization -- not just the founder's, but the customer's and the team's. "Organize the world's information" (Google), "Accelerate the world's transition to sustainable energy" (Tesla), and "Give people the power to build community" (Facebook) are all Level 5 appeals, regardless of how imperfectly those companies deliver on them. + +### The Hierarchy as Diagnostic Tool + +The framework's entrepreneurial value lies in three applications: + +1. **Customer segmentation by need level.** Which level of the hierarchy does your product address? Products that serve lower levels compete on reliability and price. Products that serve higher levels compete on meaning and experience. + +2. **Employee motivation diagnosis.** Where are your team members on the hierarchy? Offering equity (Level 4-5 reward) to someone worried about making rent (Level 1) misses the mark. Offering a raise (Level 1-2 reward) to someone craving meaningful work (Level 5) also misses. + +3. **Organizational maturity mapping.** Startups begin at Level 1 (survival). As they stabilize, they can progressively satisfy higher-level needs for both employees and customers. The transition from survival mode to purpose mode is one of the most important -- and most difficult -- evolutions a growing company undergoes. + +--- + +## Prompts + +**Prompt 1 -- Customer Need-Level Analysis:** +> Analyze my product [describe] through Maslow's hierarchy. Which level of need does it primarily address? Which levels does it also touch? Based on this analysis, what is the most effective value proposition -- and what messaging mistakes am I likely making by appealing to the wrong level of need for my target customer? + +**Prompt 2 -- Employee Motivation Audit:** +> My team of [number] people is showing these engagement patterns: [describe -- e.g., "people do the minimum," "high turnover despite good pay," "low energy in meetings but strong 1:1 conversations"]. Using Maslow's hierarchy, diagnose which need level is unsatisfied for my team. What specific interventions at that level would improve motivation and engagement? + +**Prompt 3 -- Organizational Hierarchy Mapping:** +> Map my startup's current position on Maslow's hierarchy as an organization. We are at [stage], with [months of runway], [team size], and [describe culture/morale]. Which organizational needs are met, which are at risk, and which are unaddressed? How should our priorities shift as we move to the next stage? + +**Prompt 4 -- Product-Market Fit Through Maslow:** +> I'm struggling with product-market fit for [product]. Help me reframe my value proposition using Maslow's hierarchy. What level of need does my target customer [describe segment] most urgently need addressed? Is my product positioned at the right level? Should I reposition to address a different level of the hierarchy? + +--- + +## Use Cases + +**SaaS Startup Misreading Employee Motivation** + +A growth-stage SaaS company with strong revenue and 18 months of runway keeps losing mid-level engineers to competitors. Exit interviews cite "lack of growth opportunities" and "feeling like a cog in the machine." The company's response has been to increase salaries -- a Level 1-2 intervention for a Level 4-5 problem. Engineers whose physiological and safety needs are already well met are not motivated by incremental compensation. They want meaningful work (Level 5), recognition for their contributions (Level 4), and a sense of belonging to something that matters (Level 3). The Maslow diagnosis redirects the retention strategy: implement a technical leadership track (Level 4), create cross-functional project teams for strategic initiatives (Level 3 and 5), and establish a public recognition program tied to impact rather than output (Level 4). Retention improves within two quarters -- at lower cost than the salary increases would have required. + +**Consumer App Repositioning from Level 2 to Level 3** + +A validation-stage personal finance app initially positions itself around financial security: "Never worry about money again" (Level 2). User research reveals that the most engaged users do not use the app for security -- they use it because tracking spending with a partner creates a sense of shared financial purpose (Level 3: Belonging). The Level 2 positioning attracts anxious users who churn when their anxiety subsides. The Level 3 positioning attracts couples building a financial life together -- a far stickier use case. Repositioning the product around shared financial goals rather than individual financial anxiety doubles retention. + +**Founder in Survival Mode Making Survival Decisions** + +An idea-stage founder with three months of personal savings remaining finds herself unable to think strategically about product direction. Every decision is filtered through "what will generate revenue fastest" rather than "what will create the most value." A Maslow lens clarifies the problem: the founder's own physiological and safety needs are dominating her cognitive landscape. The intervention is not motivational -- it is structural. Extending runway through a small friends-and-family round, taking a part-time consulting contract, or securing a small grant shifts the founder from Level 1-2 to Level 3-4, where strategic thinking becomes possible. The decision to extend runway is itself a strategic decision, not a sign of weakness. + +--- + +## Anti-Patterns + +- **Rigid Sequential Application.** Treating the hierarchy as a strict ladder where lower levels must be 100% satisfied before higher levels matter at all. Maslow himself acknowledged that the hierarchy is probabilistic, not absolute. A person can be motivated by purpose while still worrying about finances. The hierarchy describes dominant motivational forces, not exclusive ones. + +- **Using Maslow to Justify Low Pay.** The perverse argument that if employees are motivated by purpose (Level 5), they should accept below-market compensation (Level 1). Purpose does not replace salary; it augments it. Underpaying people while offering "mission" creates resentment that corrodes every higher-level need. + +- **Projecting the Founder's Need Level onto the Team.** Founders operating at Level 5 (self-actualization through building something meaningful) often assume the team shares this motivation. Many team members may be at Level 2 (job security in a volatile startup) or Level 3 (belonging to a team). Mismatched assumptions about motivation produce mismatched management strategies. + +- **Ignoring Cultural Variation.** Maslow's hierarchy was developed from a Western, individualistic psychological tradition. Research suggests that collectivist cultures may weight belonging (Level 3) and esteem (Level 4) differently than individualist ones. Applying the hierarchy rigidly across diverse teams without cultural calibration produces blind spots. + +- **Treating the Framework as Comprehensive.** Maslow describes motivational needs, not all aspects of human psychology relevant to business. The hierarchy says nothing about cognitive style, risk tolerance, learning preferences, or behavioral tendencies. Pairing Maslow with complementary frameworks (Belbin for team roles, Situational Leadership for management approach) produces a more complete picture. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's own hierarchy position | The founder's personal need level shapes every decision; addressing founder survival needs (runway, income) is a prerequisite for strategic thinking | +| Validation | Customer need-level discovery | Understanding which level of need the product addresses determines positioning, pricing, and retention dynamics | +| Early Traction | Team motivation foundations | First hires need Level 1-2 stability (reasonable pay, job security signals) before they can engage with the mission at higher levels | +| Growth | Organizational culture as need-satisfier | The company must systematically satisfy Level 3-4 needs (belonging, recognition) to retain talent as the labor market exerts pull | +| Scale | Self-actualization as competitive advantage | Companies that enable Level 5 experiences for employees and customers build loyalty that competitors cannot replicate with lower-level rewards | + +--- + +## Output Template + +```markdown +# Maslow's Hierarchy Analysis: [Company/Product/Team Name] + +**Date:** [Date] +**Analysis Type:** [Customer Needs / Employee Motivation / Organizational Assessment] + +## Need-Level Map + +### For Customers +| Maslow Level | How Our Product Addresses It | Strength | Gap | +|-------------|------------------------------|----------|-----| +| Physiological | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Safety | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Belonging | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Esteem | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Self-Actualization | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | + +**Primary need level served:** [Level] +**Value proposition alignment:** [Aligned / Misaligned -- with explanation] + +### For Employees +| Maslow Level | Current Satisfaction | Evidence | Intervention Needed | +|-------------|---------------------|----------|---------------------| +| Physiological | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Safety | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Belonging | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Esteem | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Self-Actualization | [Met/At Risk/Unmet] | [Data points] | [Action or None] | + +**Primary unsatisfied level:** [Level] +**Recommended priority intervention:** [Specific action] + +## Strategic Implications +1. [Insight about product positioning based on customer need level] +2. [Insight about retention strategy based on employee need level] +3. [Insight about organizational maturity based on collective need level] +``` + +--- + +## Related Skills + +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Hackman's conditions map to Maslow levels: clear direction addresses safety and esteem, right people enables belonging, supportive context satisfies physiological and safety needs. +- **[Psychological Safety](psychological-safety.md)** -- Safety and belonging needs must be met before employees can contribute fully; Edmondson's framework operationalizes the conditions Maslow's Levels 2 and 3 describe. +- **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- Retention strategies succeed when they target the correct Maslow level; offering equity to someone worried about rent or purpose to someone craving recognition misses the mark. +- **[Four Ps of Marketing](four-ps-marketing.md)** -- Product positioning and pricing strategy should align with the Maslow level the product addresses; Level 5 products demand different marketing mixes than Level 1 products. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Self-awareness and empathy help leaders diagnose which need level is unsatisfied in their team members, enabling more targeted motivational interventions. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- Purpose appeals to Maslow's Level 5 self-actualization; leaders who connect work to meaning unlock motivation that compensation alone cannot provide. diff --git a/plugins/foreman/content/skills/frameworks/myers-briggs-type-indicator.md b/plugins/foreman/content/skills/frameworks/myers-briggs-type-indicator.md new file mode 100644 index 0000000..0c7c398 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/myers-briggs-type-indicator.md @@ -0,0 +1,200 @@ +--- +name: "myers-briggs-type-indicator" +description: "Maps team cognitive diversity using the MBTI four-dichotomy personality framework: Extraversion/Introversion, Sensing/Intuition, Thinking/Feeling, Judging/Perceiving. Use when diagnosing co-founder communication friction, designing cognitively diverse teams, adapting communication style for different audiences, resolving recurring interpersonal conflicts, or identifying blind spots in team composition." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - personality + - team-composition + - communication + - hiring + - leadership-style + - self-awareness +related_skills: + - emotional-intelligence + - johari-window + - psychological-safety + - neuro-linguistic-programming +author: "Fatih Guner" +--- + +# Myers-Briggs Type Indicator + +The most widely administered personality instrument in the world -- taken by an estimated 50 million people and used by 88% of Fortune 500 companies -- is one that a significant portion of academic psychologists consider scientifically dubious. That tension is itself instructive. The Myers-Briggs Type Indicator, developed by Katharine Cook Briggs and her daughter Isabel Briggs Myers based on Carl Jung's theory of psychological types, persists not because it meets the psychometric standards of the Big Five personality model but because it does something the Big Five does not: it gives people a shared, non-judgmental language for talking about differences in how they perceive the world and make decisions. For entrepreneurs building teams under pressure, MBTI's value is practical rather than predictive. It does not tell you who will succeed. It tells you why your co-founder's approach to deadlines drives you to distraction, and why your head of sales and your head of engineering seem to be speaking different languages even when they agree on the goal. + +--- + +## The Framework + +MBTI classifies personality along four dichotomies, producing 16 possible type combinations. Each dichotomy represents a preference -- not an ability, not a fixed trait, but a tendency toward one mode of functioning over another. The analogy is handedness: most people can write with either hand, but one feels natural and the other requires effort. + +### The Four Dichotomies + +**1. Extraversion (E) vs. Introversion (I) -- Energy Direction** + +| Extraversion | Introversion | +|-------------|-------------| +| Energised by external interaction | Energised by internal reflection | +| Thinks out loud; processes through conversation | Thinks internally; processes before speaking | +| Breadth of relationships | Depth of relationships | +| Action-oriented; prefers to act, then reflect | Reflection-oriented; prefers to reflect, then act | + +Startup relevance: Extraverted founders excel at networking, pitching, and energising teams through visibility. Introverted founders excel at deep strategic thinking, listening to customers, and building products with concentrated focus. Neither orientation is superior; both are necessary at different moments. The danger is assuming everyone on the team shares the founder's energy orientation. + +**2. Sensing (S) vs. Intuition (N) -- Information Gathering** + +| Sensing | Intuition | +|---------|-----------| +| Focuses on concrete, present facts | Focuses on patterns, possibilities, future implications | +| Detail-oriented; trusts direct experience | Big-picture; trusts conceptual connections | +| Prefers proven methods | Prefers innovation and novelty | +| Asks "What is?" | Asks "What could be?" | + +Startup relevance: The S/N dichotomy is the most frequent source of co-founder friction. Sensing-oriented co-founders want data, specifics, and proven models. Intuition-oriented co-founders want vision, possibility, and novel approaches. When the CTO (often S) asks "Show me the data" and the CEO (often N) responds with "Trust the vision," neither is wrong -- they are processing through different information-gathering preferences. + +**3. Thinking (T) vs. Feeling (F) -- Decision Making** + +| Thinking | Feeling | +|----------|---------| +| Decides based on logical analysis and objective criteria | Decides based on values, impact on people, and harmony | +| Seeks truth | Seeks tact | +| Comfortable with impersonal critique | Sensitive to the human dimension of decisions | +| Asks "Is this logical?" | Asks "What impact will this have on people?" | + +Startup relevance: The T/F dichotomy becomes critical during painful decisions -- layoffs, performance management, ending partnerships. Thinking-preference leaders risk making correct decisions that destroy team trust through insensitive execution. Feeling-preference leaders risk delaying necessary decisions to avoid discomfort, allowing problems to compound. + +**4. Judging (J) vs. Perceiving (P) -- Orientation to Structure** + +| Judging | Perceiving | +|---------|------------| +| Prefers closure and decisiveness | Prefers openness and flexibility | +| Plans ahead; works methodically | Adapts in the moment; works in bursts | +| Comfortable with deadlines and schedules | Energised by last-minute pressure | +| Seeks to resolve ambiguity | Tolerates ambiguity comfortably | + +Startup relevance: J/P tension is visible in every sprint planning meeting. Judging types want clear plans, committed timelines, and defined scope. Perceiving types want optionality, room for pivoting, and freedom to follow emerging opportunities. Early-stage startups, which exist in permanent ambiguity, structurally favour P-orientation -- but eventually need J-discipline to scale execution. + +### Type Dynamics and Team Composition + +The 16 types are not merely four binary choices stacked together; they interact. Each type has a dominant function (the strongest preference), an auxiliary function (the support), a tertiary function (developing), and an inferior function (the blindspot). Understanding type dynamics helps explain why an ENTJ leader (dominant extraverted thinking) and an INFP team member (dominant introverted feeling) can create explosive friction: each person's strength is the other's blindspot. + +For team composition, the research-informed principle is cognitive diversity: teams that span the four dichotomies outperform homogeneous teams on complex problems, though they experience more friction during the process. The friction is the feature, not the bug -- it ensures that details are not ignored (S), possibilities are explored (N), logical rigour is applied (T), and human impact is considered (F). + +--- + +## Prompts + +**Prompt 1 -- Team Type Mapping:** +> Based on these behavioural descriptions of my team members, estimate their likely MBTI types and map the team's cognitive diversity: [describe each person's communication style, decision-making approach, energy patterns, and response to ambiguity]. Identify where the team clusters (shared preferences) and where it has gaps. Recommend specific actions to compensate for missing perspectives -- either through hiring, advisory relationships, or structured processes that force the team to consider its blind spots. + +**Prompt 2 -- Co-Founder Friction Diagnosis:** +> My co-founder and I are experiencing recurring friction around [describe the pattern -- e.g., decision speed, risk tolerance, communication style, planning approach]. Based on these descriptions of our respective styles, identify the likely MBTI dichotomy driving the tension: my style: [describe], their style: [describe]. Translate the friction from "right vs. wrong" into "different cognitive preferences" and recommend specific protocols we can adopt to leverage both perspectives rather than fight over which is correct. + +**Prompt 3 -- Communication Adaptation:** +> I need to present [topic -- e.g., a strategic pivot, a new initiative, a difficult decision] to a group that includes [describe audience members and their likely types]. Design multiple versions of the key message, each adapted to a different MBTI preference pair: one optimised for ST (sensing-thinking), one for SF (sensing-feeling), one for NT (intuition-thinking), and one for NF (intuition-feeling). Highlight what each version emphasises and what it de-emphasises. + +**Prompt 4 -- Hiring Complement Analysis:** +> My founding team consists of [describe types/preferences]. We are hiring for [role]. Based on our team's current type composition and the requirements of this role, recommend the personality preferences that would most complement our existing team. Explain which of our current blind spots this hire would address and what new tensions to anticipate (with mitigation strategies). + +--- + +## Use Cases + +**Early-traction startup with co-founder communication breakdown** + +Two co-founders of an edtech startup have escalating disagreements that are eroding their working relationship. The CEO (likely ENFP -- extraverted, intuitive, feeling, perceiving) generates ideas rapidly, changes direction frequently, and makes decisions based on passion and user stories. The CTO (likely ISTJ -- introverted, sensing, thinking, judging) wants detailed specifications, stable priorities, and decisions grounded in data. Each interprets the other's style as a character flaw: the CEO sees the CTO as rigid and uninspired; the CTO sees the CEO as chaotic and unreliable. MBTI reframes the dynamic: neither is flawed; they process information and make decisions through fundamentally different cognitive preferences. The intervention establishes a structured protocol: the CEO creates a "vision document" for each initiative (satisfying the N preference), which the CTO then translates into a "specification document" (satisfying the S preference). Disagreements are routed through a shared decision matrix that incorporates both data (T) and impact assessment (F). The relationship stabilises within a month. + +**Growth-stage company restructuring teams for product launch** + +A 75-person company preparing for a major product launch assembles a cross-functional team from engineering, design, marketing, and sales. Initial meetings are unproductive: engineering wants detailed timelines (J), marketing wants flexibility to respond to competitor moves (P), design insists on user research (S/F), and sales pushes for features that close deals (S/T). The VP of Product administers informal MBTI assessments and maps the team's type distribution, revealing a heavy ST cluster in engineering and an NF cluster in design, with marketing and sales split. Armed with this map, the VP restructures meetings: technical reviews are S/T-optimised (data, specifics, timelines), creative sessions are N/F-optimised (possibilities, user stories, open exploration), and integration meetings deliberately include all preferences with a facilitator who ensures each cognitive style gets airtime. The product launches on schedule -- not because anyone changed their type, but because the process was designed to leverage all types rather than privilege one. + +--- + +## Anti-Patterns + +**1. Using MBTI as a hiring filter.** This is the most prevalent and damaging misapplication. MBTI does not predict job performance, and using it to screen candidates is both scientifically unsupported and ethically questionable. Research consistently shows that MBTI type does not reliably predict success in any role. Use it to understand communication dynamics after hiring, not to make hiring decisions. + +**2. Treating type as destiny.** "I'm an introvert, so I can't do sales" is a fixed-mindset application of a tool that was designed to illuminate preferences, not define limits. Every person can operate outside their preferences -- it simply requires more energy. Conflating preference with inability is a distortion of the framework. + +**3. Weaponising type in conflict.** "That's just your T talking" or "You're being such a J right now" turns a communication tool into an ad hominem attack. Type language should explain behaviour, not excuse it or dismiss it. + +**4. Over-relying on a framework with known psychometric limitations.** MBTI's test-retest reliability is lower than academic psychologists prefer -- studies show that 50% of people receive a different type classification when retested after five weeks. The framework is most useful when treated as a rough map of preferences rather than a precise measurement of personality. Founders who treat MBTI types as rigid categories mistake the map for the territory. + +**5. Assembling teams purely by type diversity.** Cognitive diversity matters, but so do domain expertise, cultural fit, work ethic, and interpersonal chemistry. A team with perfect type diversity but poor trust will underperform a less diverse team with strong cohesion. MBTI is one lens among many for team composition. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder dynamics, first-hire compatibility | MBTI explains interpersonal friction and provides shared language for navigating preference differences | +| Growth | Team composition, management layer communication | MBTI informs team design and helps managers adapt communication to different report types | +| Scale | Organisational culture, cross-functional alignment, M&A integration | MBTI identifies cultural clashes between departments or acquired companies with different cognitive profiles | + +At early traction, MBTI's primary value is translating interpersonal friction from personal conflict into cognitive-preference difference. When two co-founders understand that their disagreement about planning rigour reflects a J/P preference difference rather than a competence gap, they can design processes that honour both orientations instead of fighting about who is right. + +At growth, MBTI becomes a management development tool. Training managers to recognise and adapt to different preferences in their reports improves one-on-one effectiveness, feedback quality, and delegation accuracy. An ST manager who learns to frame assignments differently for NF reports (leading with purpose and impact rather than specifications and deadlines) will see better outcomes without changing the substance of the assignment. + +At scale, MBTI's organisational application emerges. Merging two companies or restructuring departments often produces culture clash that is partly a type clash. Engineering-dominated organisations tend toward ST cultures; marketing-dominated organisations toward NF cultures. Making these preferences visible and creating bridging protocols reduces post-merger friction and cross-functional dysfunction. + +--- + +## Output Template + +```markdown +# Team Cognitive Diversity Map -- [Team Name] + +**Prepared for:** Team / Hiring Manager +**Date:** [Date] +**Purpose:** [Team formation / Conflict resolution / Hiring complement] + +## Individual Type Estimates + +| Team Member | Estimated Type | Confidence | Key Behavioural Evidence | +|------------|---------------|------------|------------------------| +| [Name] | [XXXX] | [High/Medium/Low] | [Observable behaviours that suggest this type] | + +## Team Preference Distribution + +| Dichotomy | Count E/I | Count S/N | Count T/F | Count J/P | +|-----------|----------|----------|----------|----------| +| **Preference A** | [E: N] | [S: N] | [T: N] | [J: N] | +| **Preference B** | [I: N] | [N: N] | [F: N] | [P: N] | + +## Cognitive Gaps +- **Under-represented preference:** [Which preference is missing or under-represented] +- **Impact:** [What perspectives or approaches the team systematically neglects] +- **Compensation strategy:** [Hiring, advisory, or process-based mitigation] + +## Friction Points Predicted + +| Pair/Group | Preference Clash | Likely Symptom | Recommended Protocol | +|-----------|-----------------|----------------|---------------------| +| [Person A + B] | [e.g., J vs. P] | [e.g., conflict over planning rigidity] | [Specific process to manage] | + +## Communication Adaptation Guide + +| Audience Type | Lead With | Avoid | Format Preference | +|--------------|-----------|-------|-------------------| +| ST | Data, specifics, proven results | Abstract vision, ungrounded possibilities | Structured documents, bullet points | +| SF | People impact, concrete examples | Impersonal logic, theoretical frameworks | Stories, case studies, face-to-face | +| NT | Strategic implications, novel approaches | Excessive detail, status quo arguments | Conceptual frameworks, debate format | +| NF | Purpose, meaning, human potential | Pure metrics, reductive analysis | Narrative, collaborative discussion | +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](emotional-intelligence.md)** -- MBTI maps cognitive preferences; EQ provides the self-awareness and empathy to navigate the interpersonal dynamics those preferences create. +- **[Johari Window](johari-window.md)** -- MBTI type functions as a lens for understanding one's "blind spot" quadrant, revealing patterns that others see clearly but the individual does not. +- **[Psychological Safety](psychological-safety.md)** -- Teams with high type diversity need high psychological safety; without it, minority-preference members self-censor, and the team loses the cognitive diversity it was designed to provide. +- **[Belbin Team Roles](belbin-team-roles.md)** -- Belbin's functional roles complement MBTI's cognitive preferences; together they reveal both how team members think and what contribution they naturally make. +- **[Understanding People](../people/understanding-people.md)** -- MBTI provides a structured vocabulary for understanding cognitive differences, which deepens the broader practice of reading and adapting to the people around you. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- Mapping team MBTI profiles reveals the cultural tendencies that emerge from cognitive clustering, helping leaders design processes that honor all preference types. diff --git a/plugins/foreman/content/skills/frameworks/net-promoter-score.md b/plugins/foreman/content/skills/frameworks/net-promoter-score.md new file mode 100644 index 0000000..729bb71 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/net-promoter-score.md @@ -0,0 +1,248 @@ +--- +name: "net-promoter-score" +description: "Designs and analyzes Net Promoter Score programmes for measuring customer loyalty through promoter, passive, and detractor classification. Covers NPS calculation, segmented analysis, closed-loop feedback processes, and revenue impact modelling. Use when measuring product-market fit, diagnosing retention problems, benchmarking customer satisfaction, building a customer feedback system, or connecting loyalty metrics to revenue growth." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - customer-loyalty + - customer-feedback + - growth-metrics + - retention + - voice-of-customer +related_skills: + - balanced-scorecard + - product-life-cycle + - systems-thinking + - doblin-ten-types +author: "Fatih Guner" +--- + +# Net Promoter Score (NPS) + +"On a scale of zero to ten, how likely are you to recommend us to a friend or colleague?" One question. That is the entirety of the instrument that Fred Reichheld introduced in a 2003 Harvard Business Review article titled "The One Number You Need to Grow." It became, within a decade, the most widely used customer loyalty metric in the world -- adopted by two-thirds of the Fortune 1000, embedded in the dashboards of startups and enterprises alike, and debated with a fervour usually reserved for religion and operating system preferences. Reichheld's research at Bain & Company had demonstrated a finding that was both intuitive and, at the time, poorly quantified: the willingness of customers to recommend a company to others correlated more strongly with revenue growth than any other single customer metric. Not satisfaction. Not repurchase intent. Recommendation intent -- the act of staking one's personal reputation on the quality of someone else's product. + +The framework's elegance is its simplicity. Its peril is the same. + +--- + +## The Framework + +### The Calculation + +NPS converts a single survey question into a score ranging from -100 to +100. + +**Step 1: Ask the question.** + +"On a scale of 0 to 10, how likely are you to recommend [Company/Product] to a friend or colleague?" + +**Step 2: Classify respondents.** + +| Score | Classification | Behaviour Profile | +|-------|---------------|-------------------| +| 9-10 | **Promoters** | Loyal enthusiasts who actively refer others; highest lifetime value; lowest churn | +| 7-8 | **Passives** | Satisfied but unenthusiastic; vulnerable to competitive offers; unlikely to refer | +| 0-6 | **Detractors** | Unhappy customers who may actively discourage others; highest churn risk; potential brand damage | + +**Step 3: Calculate the score.** + +``` +NPS = (% Promoters) - (% Detractors) +``` + +Passives are excluded from the calculation but not from the analysis. They represent the swing population -- the customers who could become promoters with better experience or detractors with worse. + +**Worked Example:** + +A startup surveys 200 customers: +- 90 score 9-10 (Promoters): 45% +- 70 score 7-8 (Passives): 35% +- 40 score 0-6 (Detractors): 20% + +NPS = 45% - 20% = **+25** + +### Interpreting the Score + +NPS benchmarks vary significantly by industry, geography, and business model. Absolute scores mean less than relative position and trend. + +| NPS Range | General Interpretation | +|-----------|----------------------| +| 70+ | Exceptional -- world-class loyalty (Apple, USAA, Costco territory) | +| 50-69 | Excellent -- strong competitive advantage through customer advocacy | +| 30-49 | Good -- more promoters than detractors, but room for improvement | +| 0-29 | Adequate -- loyalty is not a competitive advantage | +| Below 0 | Problematic -- detractors outnumber promoters; growth is fighting an active headwind | + +**The trend matters more than the number.** An NPS of +20 that has improved from +5 over four quarters signals a company moving in the right direction. An NPS of +50 that has declined from +65 signals trouble that the absolute score obscures. + +### The Follow-Up: Where the Real Value Lives + +The NPS question produces a number. The follow-up question produces insight. + +"What is the primary reason for your score?" + +This open-ended response is where NPS transitions from a metric to a management system. Coding and analysing the qualitative responses reveals: +- What promoters value most (your competitive advantage, in their words) +- What detractors resent (your most damaging failure points) +- What passives find missing (the gap between satisfaction and enthusiasm) + +The discipline of "closing the loop" -- contacting detractors to understand and address their concerns, thanking promoters and asking for referrals, and nudging passives toward promoter territory -- transforms NPS from a survey into an operational process. + +### The Economic Logic + +Reichheld's research quantified what experienced entrepreneurs know intuitively: + +- **Promoters** have 2-3x the lifetime value of detractors +- **Promoters** generate 80-90% of positive referrals +- **Detractors** generate 80-90% of negative word-of-mouth +- Companies with NPS leaders in their industry grow at **2x** the rate of the average competitor + +The economic mechanism is straightforward: promoters buy more, stay longer, cost less to serve, and recruit new customers at zero acquisition cost. Detractors buy less, leave sooner, consume disproportionate support resources, and actively damage the brand through negative referrals. + +### NPS as a System, Not a Score + +Reichheld's later work, particularly *The Ultimate Question 2.0* (2011), emphasised that NPS as a metric is insufficient. NPS as a management system requires: + +1. **Measurement** -- Regular, consistent surveying at key touchpoints (post-purchase, post-support, quarterly relationship surveys) +2. **Analysis** -- Segmentation of NPS by customer cohort, product line, geography, and channel to identify specific drivers +3. **Action** -- Operational processes that translate NPS insights into product, service, and experience improvements +4. **Accountability** -- NPS targets integrated into team and individual performance metrics +5. **Closed-Loop Feedback** -- Direct follow-up with detractors (within 24-48 hours) and promoters + +--- + +## Prompts + +**Prompt 1 -- NPS Programme Design:** +> "Design an NPS measurement programme for my business: [describe company, product, customer segments, and current feedback mechanisms]. Specify: (1) which customer touchpoints to survey, (2) survey frequency, (3) how to segment results for actionable insight, (4) the closed-loop process for detractors and promoters, and (5) how to integrate NPS into our existing metrics dashboard." + +**Prompt 2 -- NPS Results Analysis:** +> "Analyse these NPS results: Overall NPS: [score]. Promoters: [%], Passives: [%], Detractors: [%]. Top reasons cited by promoters: [list]. Top reasons cited by detractors: [list]. Segment breakdown: [list NPS by segment]. Identify: (1) the highest-leverage improvement that would convert the most detractors, (2) the promoter insight we should amplify in marketing, (3) which customer segment requires the most urgent attention." + +**Prompt 3 -- NPS-to-Revenue Modelling:** +> "Model the revenue impact of improving our NPS from [current score] to [target score]. Assume: average customer lifetime value of [$X], current customer count of [N], annual churn rate of [X%], and referral rate of [X%] among promoters. Calculate the expected impact on: (1) retained revenue from reduced churn, (2) new revenue from increased referrals, (3) reduced support costs from fewer detractors." + +**Prompt 4 -- Competitive NPS Benchmarking:** +> "Benchmark our NPS of [score] against [industry/sector] standards. Identify where we stand relative to: (1) industry average, (2) industry leader, and (3) the NPS threshold that correlates with above-average growth in our sector. Based on the gap analysis, recommend three specific initiatives that companies in our sector have used to improve NPS by [target] points." + +--- + +## Use Cases + +**Validation-Stage Startup Measuring Product-Market Fit** + +A B2B SaaS startup with 50 paying customers uses NPS as a product-market fit signal. Sean Ellis's "very disappointed" test (a close cousin of NPS) suggests that 40% "very disappointed" correlates with product-market fit; NPS provides a complementary lens. The startup's first NPS survey returns +12: 38% promoters, 36% passives, 26% detractors. The follow-up question reveals that promoters love the product's speed and simplicity, while detractors cite missing integrations and unreliable data exports. The NPS data provides a precise product roadmap: invest in integrations (converting detractors) before adding new features (which passives are not asking for). After two quarters of integration-focused development, NPS rises to +38, and the detractor-cited reasons shift from "missing features" to "wish it did more" -- a qualitatively different complaint that signals readiness to expand the product scope. + +**Growth-Stage E-Commerce Company Identifying a Service Failure** + +An e-commerce company with 10,000 monthly orders has an overall NPS of +42, which appears healthy. Segmented analysis tells a different story: NPS among first-time buyers is +55, but NPS among repeat buyers is +18 and declining. The follow-up responses from repeat-buyer detractors cluster around two themes: inconsistent delivery times and a loyalty programme that feels "pointless." The segmentation reveals a retention crisis invisible in the aggregate score. The company redesigns its logistics partnerships (addressing delivery consistency) and replaces its points-based loyalty programme with a tier-based system offering tangible benefits (free shipping, early access). Within two quarters, repeat-buyer NPS rises to +39, and the cohort-level analysis shows that the company had been unknowingly operating two different businesses -- one excellent (acquisition) and one mediocre (retention). + +**Scale-Stage Platform Embedding NPS in Operational Governance** + +A marketplace platform with 500,000 active users implements NPS as a core governance metric across the organisation. Each product team owns a touchpoint NPS: onboarding NPS (product team A), transaction NPS (product team B), support NPS (customer experience team), and overall relationship NPS (executive team). Monthly NPS reviews surface anomalies: a sudden 15-point drop in transaction NPS among a specific user segment leads to the discovery of a payment processing bug that affected 3% of transactions but generated outsized negative sentiment. The bug was invisible in aggregate metrics but immediately visible in segmented NPS. Resolution within 48 hours, followed by closed-loop outreach to affected users, recovers the score within one month. + +--- + +## Anti-Patterns + +**Score Worship.** Obsessing over the NPS number while ignoring the qualitative data and the closed-loop process. The score is a thermometer; it tells you the temperature but not the disease. Companies that celebrate NPS milestones without acting on the underlying feedback have built a vanity metric, not a management system. + +**Survey Fatigue.** Surveying customers after every interaction, every transaction, and every support ticket. Over-surveying depresses response rates, biases results toward people with strong opinions (both positive and negative), and annoys the very customers you aim to delight. Survey at the moments that matter; leave the rest alone. + +**Gaming the Score.** Instructing frontline staff to ask only happy customers for feedback, or designing the survey flow to nudge toward higher scores. NPS gaming is organisationally corrosive because it destroys the metric's diagnostic value. When the score stops reflecting reality, leadership loses its most important feedback channel precisely when it needs it most. + +**Ignoring Passives.** The NPS formula excludes passives, which leads many companies to ignore them operationally. This is a strategic error. Passives are the largest swing group: converting even a fraction of passives to promoters has a larger impact on NPS (and revenue) than converting detractors, because the conversion effort is typically smaller and the base is larger. + +**Using NPS as the Only Customer Metric.** NPS measures loyalty intent, not loyalty behaviour. Customer satisfaction (CSAT), customer effort score (CES), churn rate, expansion revenue, and referral attribution each capture dimensions that NPS cannot. NPS works best as the keystone metric in a broader measurement system, not as a standalone indicator. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Signal for product-market fit | NPS above +30 with a small, representative sample is a strong PMF indicator | +| Early Traction | Identify the highest-impact product improvements | Detractor feedback is the most efficient product roadmap input at this stage | +| Growth | Build the NPS management system | Transition from periodic measurement to continuous, segmented, closed-loop operations | +| Scale | Embed NPS in organisational governance | NPS by team, touchpoint, segment, and geography drives accountability and surfaces problems at scale | + +At the validation stage, NPS should be measured with small samples (30-50 responses are sufficient for directional signal) and analysed primarily for qualitative patterns. The score matters less than what promoters and detractors say about why they scored as they did. + +During growth, the critical transition is from NPS as a metric (measured quarterly, reported to the board) to NPS as a system (measured continuously, segmented by touchpoint, with closed-loop processes for detractors and promoters). Companies that make this transition early build a structural advantage in customer retention that compounds over time. + +At scale, NPS becomes a governance instrument. Product teams own their touchpoint NPS. Executives own the relationship NPS. The gap between touchpoint scores and relationship score reveals the systemic issues that no single team can diagnose alone. + +--- + +## Output Template + +**Target Audience: Customer Experience Team / VP Customer Success** + +```markdown +# NPS Report: [Company Name] +## Period: [Date Range] + +### Score Summary +- **Overall NPS:** [Score] (Previous period: [Score], Change: [+/- N]) +- **Promoters:** [N] ([X%]) +- **Passives:** [N] ([X%]) +- **Detractors:** [N] ([X%]) +- **Response rate:** [X%] (from [N] surveys sent) + +### Trend +| Period | NPS | Promoters % | Passives % | Detractors % | +|--------|-----|-------------|------------|--------------| +| [Period -3] | [Score] | [%] | [%] | [%] | +| [Period -2] | [Score] | [%] | [%] | [%] | +| [Period -1] | [Score] | [%] | [%] | [%] | +| [Current] | [Score] | [%] | [%] | [%] | + +### Segmented NPS +| Segment | NPS | Sample Size | Change | Alert? | +|---------|-----|-------------|--------|--------| +| [Segment 1] | [Score] | [N] | [+/- N] | [Y/N] | +| [Segment 2] | [Score] | [N] | [+/- N] | [Y/N] | +| [Segment 3] | [Score] | [N] | [+/- N] | [Y/N] | + +### Key Drivers +**Why Promoters Promote (Top 3):** +1. [Theme] -- cited by [N]% of promoters +2. [Theme] -- cited by [N]% of promoters +3. [Theme] -- cited by [N]% of promoters + +**Why Detractors Detract (Top 3):** +1. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] +2. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] +3. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] + +### Closed-Loop Status +- Detractors contacted within 48 hours: [X%] +- Detractors with resolved issues: [X%] +- Promoters thanked and asked for referral: [X%] + +### Revenue Impact Estimate +- Estimated revenue at risk from detractors: [$X] (based on [churn rate] and [LTV]) +- Estimated referral revenue from promoters: [$X] (based on [referral rate] and [LTV]) +- Net loyalty-driven revenue impact: [+/- $X] + +### Priority Actions +1. [Action] -- Target: Convert [X]% of [segment] detractors -- Owner: [Name] -- Deadline: [Date] +2. [Action] -- Target: Shift [X]% of passives to promoters -- Owner: [Name] -- Deadline: [Date] +3. [Action] -- Target: Amplify promoter advocacy through [channel] -- Owner: [Name] -- Deadline: [Date] +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](balanced-scorecard.md)** -- NPS is the most common metric in the Customer perspective of the Balanced Scorecard; the scorecard provides the strategic context for how NPS connects to financial outcomes through the causal chain. +- **[Product Life Cycle](product-life-cycle.md)** -- NPS behaves differently across product lifecycle phases; introduction-phase NPS is volatile, growth-phase NPS typically rises, maturity-phase NPS stabilises, and decline-phase NPS deteriorates. +- **[Systems Thinking](systems-thinking.md)** -- NPS operates within a system of feedback loops; promoters drive referrals that bring new promoters (reinforcing loop), while detractors drive negative word-of-mouth that deters potential customers. +- **[SMART Goals](smart-goals.md)** -- NPS targets must be SMART to drive action; "improve NPS" is a wish, while "increase enterprise NPS from +25 to +40 by Q3 through onboarding redesign" is an actionable commitment. +- **[Reader Psychology](../writing/reader-psychology.md)** -- The follow-up question that produces qualitative NPS insight depends on how you frame and present the survey; reader psychology principles improve response rates and data quality. +- **[Tipping Point](tipping-point.md)** -- Promoters are the engine of Gladwell's social epidemics; NPS identifies and quantifies the advocacy base whose word-of-mouth drives organic growth past the tipping point. diff --git a/plugins/foreman/content/skills/frameworks/neuro-linguistic-programming.md b/plugins/foreman/content/skills/frameworks/neuro-linguistic-programming.md new file mode 100644 index 0000000..106b180 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/neuro-linguistic-programming.md @@ -0,0 +1,191 @@ +--- +name: "neuro-linguistic-programming" +description: "Applies NLP techniques for rapport-building, reframing, anchoring, and meta-model questioning in business communication. Covers representational system matching, pacing and leading, and linguistic precision tools. Use when preparing for investor pitches, improving sales close rates, navigating board disagreements, refining communication for different audience types, or extracting actionable insights from vague customer feedback." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth +tags: + - communication + - persuasion + - rapport-building + - reframing + - sales +related_skills: + - emotional-intelligence + - johari-window + - myers-briggs-type-indicator + - grow-model +author: "Fatih Guner" +--- + +# Neuro-Linguistic Programming + +NLP may be the most commercially successful framework in business psychology that the academic establishment refuses to take seriously. Developed in the 1970s by Richard Bandler and John Grinder at the University of California, Santa Cruz, neuro-linguistic programming began as an audacious premise: that excellence is not mystical but structural, and that the specific communication patterns, mental models, and behavioural sequences of exceptionally effective people can be decoded, modelled, and taught to others. The academic critique -- that NLP lacks rigorous empirical validation -- is well documented and partially fair. What the critique misses is that NLP's practical toolkit for rapport-building, reframing, and communication has been quietly absorbed into executive coaching, sales training, negotiation methodology, and therapeutic practice worldwide. For entrepreneurs, whose daily work is fundamentally an exercise in influence -- persuading investors, customers, recruits, and partners -- NLP's techniques offer a pragmatic edge, provided they are applied with ethical grounding rather than manipulative intent. + +--- + +## The Framework + +NLP rests on several foundational principles and a practical toolkit that connects neurology ("neuro"), language ("linguistic"), and behavioural patterns ("programming"). The core claim is that subjective experience has a discoverable structure, and by altering that structure, outcomes change. + +### Core Presuppositions + +NLP operates from a set of working assumptions -- not empirical laws, but heuristics that shape its application: + +1. **The map is not the territory.** Every person's perception of reality is a model, not reality itself. Disagreements often stem not from conflicting facts but from conflicting maps. Recognising this dissolves unproductive arguments about who is "right." + +2. **People respond to their map of reality, not to reality itself.** A customer's objection reflects their internal representation of the product, not the product's actual properties. Change the representation, change the response. + +3. **The meaning of your communication is the response you get.** If a message is misunderstood, the communicator bears responsibility for adjusting, not the audience for failing to understand. This presupposition is transformative for founders who default to blaming audiences for "not getting it." + +4. **There is no failure, only feedback.** Every outcome, including undesired ones, provides information that can be used to calibrate the next attempt. This reframe is structurally identical to the lean startup's build-measure-learn cycle. + +5. **People already have all the resources they need.** The task is not to add capability but to access and organise existing internal resources more effectively. + +### The NLP Toolkit for Entrepreneurs + +**Rapport Building** + +Rapport is the foundation of influence. NLP codifies rapport-building into specific, practicable techniques: + +- **Matching and mirroring** -- subtly aligning body language, speech tempo, tonality, and breathing patterns with the other person. The mechanism is neurological: mirror neurons fire when we observe and replicate another person's patterns, creating a felt sense of connection. +- **Pacing and leading** -- first matching the other person's current state (pacing), then gradually shifting to the desired state (leading). A founder meeting a sceptical investor would first acknowledge and match the scepticism before redirecting toward opportunity. +- **Representational system matching** -- identifying whether a person processes information primarily through visual, auditory, or kinaesthetic channels (detected through language patterns and eye movements) and matching communication to that preference. + +**Reframing** + +Reframing changes the meaning of an experience by changing the context or perspective through which it is viewed. Two primary types: + +| Type | Mechanism | Example | +|------|-----------|---------| +| **Context reframe** | The same behaviour is valuable in a different context | "Your obsessive attention to detail slows us down" becomes "That same attention to detail is why our product has zero critical bugs in production" | +| **Content reframe** | The same event carries a different meaning | "We lost our biggest customer" becomes "We've eliminated our single-point-of-failure revenue dependency" | + +Reframing is not spin. Effective reframing requires the new perspective to be genuinely valid -- otherwise it registers as dishonest and destroys trust. + +**Anchoring** + +Anchoring associates a specific internal state (confidence, calm, focus) with a deliberate stimulus (a gesture, word, or visual cue). Through repetition, the stimulus reliably triggers the state. Athletes use this instinctively; NLP makes the process explicit. A founder who anchors a state of confident composure before investor pitches can access that state on demand. + +**Meta-Model Questions** + +The meta-model is a set of linguistic precision tools designed to challenge vague, distorted, or incomplete statements. Entrepreneurs encounter these linguistic patterns constantly: + +- **Deletions:** "We need to move faster." (Faster than what? At what? Who specifically?) +- **Generalisations:** "Customers don't care about that feature." (All customers? Which ones specifically? Based on what evidence?) +- **Distortions:** "The market is dying." (What specifically is happening that leads to that conclusion?) + +Meta-model questions restore specificity, turning impressionistic claims into actionable information. + +--- + +## Prompts + +**Prompt 1 -- Pitch Reframing:** +> I need to present a potential weakness to investors: [describe the weakness -- e.g., "We have no revenue yet," "Our market is small," "Our team lacks industry experience"]. Generate three reframes for this weakness: one context reframe, one content reframe, and one that combines both. Each reframe must be honest -- not spin -- and should position the weakness as a genuine strategic advantage or learning asset. Draft the specific language I would use in a pitch meeting. + +**Prompt 2 -- Communication Precision Audit:** +> Review the following team communication (email, Slack message, or meeting notes): [paste communication]. Identify all instances of deletions, generalisations, and distortions using the NLP meta-model. For each, generate the specific clarifying question that would restore precision. Then rewrite the communication with full specificity. + +**Prompt 3 -- Rapport Strategy for Key Meeting:** +> I have a critical meeting with [describe person -- role, what you know about their communication style, any past interactions]. Using NLP rapport principles, help me prepare: (a) likely representational system preference based on available clues, (b) pacing strategy for the first 5 minutes, (c) leading strategy for transitioning to my agenda, and (d) specific language patterns to match their communication style. Also identify 2-3 meta-model questions I should be prepared to ask. + +--- + +## Use Cases + +**Validation-stage founder refining investor narrative** + +A deeptech founder with a PhD in materials science consistently fails to connect with generalist investors. Technical pitches land well with domain experts but produce glazed expressions in broader audiences. NLP diagnosis reveals a representational system mismatch: the founder communicates almost exclusively in kinaesthetic and technical-abstract terms ("feel the weight of the data," "the molecular structure behaves differently under pressure") while most investors process information visually. The intervention involves restructuring the pitch to lead with visual language and spatial metaphors ("picture a market map where our technology sits here"), supported by diagrams and visual aids. The founder also applies pacing and leading -- opening with the investor's known concerns before transitioning to the technical differentiation story. Conversion rate for follow-up meetings increases from 15% to 45% within one quarter. + +**Growth-stage CEO navigating board disagreement** + +A CEO faces a divided board: two directors want aggressive international expansion, two want to consolidate domestically. Both sides have entrenched positions and escalating emotional investment. The CEO applies NLP reframing to restructure the conversation. Rather than debating "expand vs. consolidate" (a binary that forces winners and losers), the CEO reframes the question as "What is the minimum viable international experiment that strengthens our domestic position?" -- a context reframe that dissolves the apparent opposition. The CEO also uses meta-model questions to challenge the generalisations underlying both positions ("All international markets are risky" / "Domestic growth is saturated") and surface the specific data each side is relying on. The board reaches consensus on a pilot programme within a single session. + +**Early-traction sales team improving close rates** + +A B2B startup with strong inbound leads struggles with conversion from demo to contract. Analysis reveals that the sales team runs identical demo scripts regardless of buyer type. NLP-informed training introduces representational system matching (adjusting demo language for visual, auditory, and kinaesthetic buyers), pacing techniques (acknowledging the buyer's current provider positively before introducing the alternative), and reframing of common objections. Close rates improve from 12% to 22% over three months. + +--- + +## Anti-Patterns + +**1. Using NLP as covert manipulation.** The ethical boundary is straightforward: NLP techniques should be used to communicate more effectively and build genuine rapport, not to circumvent another person's rational judgment. Founders who use rapport techniques to mask bad deals, or reframing to obscure genuine weaknesses, will eventually be exposed -- and the reputational damage is compounding. + +**2. Treating NLP as a science with predictive certainty.** NLP's empirical foundations are contested. Practitioners who present its techniques as neurologically validated facts -- rather than useful heuristics derived from observing effective communicators -- lose credibility with analytically rigorous audiences. The correct framing: "This approach has been observed to work frequently; here is the hypothesised mechanism." + +**3. Over-indexing on technique at the expense of substance.** No amount of rapport-building, reframing, or anchoring compensates for a weak product, unclear value proposition, or fundamentally flawed business model. NLP enhances the transmission of substance; it does not replace it. + +**4. Rigid representational system categorisation.** People are not purely "visual" or "auditory" -- they use all systems and shift between them contextually. Treating representational system preferences as fixed personality types produces the same errors as any rigid personality taxonomy. + +**5. Ignoring cultural context in rapport techniques.** Mirroring and matching behaviours that are appropriate in one culture can be intrusive or offensive in another. Direct eye contact, physical proximity, speech volume, and emotional expressiveness carry dramatically different meanings across cultures. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Customer discovery conversations | Meta-model questions extract genuine needs from vague customer feedback; reframing helps founders hear critical feedback without defensiveness | +| Early Traction | Sales, pitch refinement, early hiring | Rapport techniques directly impact close rates and candidate conversion; representational system matching sharpens pitch effectiveness | +| Growth | Leadership communication, board management, team alignment | Reframing resolves internal strategic disagreements; pacing and leading helps navigate increasingly complex stakeholder dynamics | + +During validation, the meta-model is the most valuable NLP tool. Customer discovery interviews are plagued by deletions ("We'd probably use something like that"), generalisations ("Everyone in our industry does it this way"), and distortions ("That would never work here"). Precision questioning transforms vague signals into actionable product insights. + +At early traction, the emphasis shifts to rapport and influence. The founder is selling constantly -- to customers, to recruits, to investors. Matching communication to the audience's processing style and pacing before leading creates measurably better outcomes in these interactions. + +At growth, reframing becomes the power tool. Internal disagreements, board dynamics, and strategic pivots all require the ability to restructure how problems are perceived without dismissing legitimate concerns. The founder who reframes effectively builds coalitions; the one who argues positions creates factions. + +--- + +## Output Template + +```markdown +# Communication Strategy -- [Meeting/Pitch/Conversation] + +**Prepared for:** Team / Founder +**Date:** [Date] +**Context:** [Key meeting, negotiation, or presentation being prepared] + +## Audience Profile +- **Primary audience:** [Role, known preferences, past interactions] +- **Likely representational system:** [Visual / Auditory / Kinaesthetic -- with evidence] +- **Current emotional state (estimated):** [Based on context clues] +- **Key concerns to pace:** [What they're worried about] + +## Rapport Strategy +1. **Opening (Pacing):** [Specific language/approach for first 2-3 minutes] +2. **Transition (Leading):** [How to shift from their frame to yours] +3. **Matching points:** [Language patterns, tempo, and style to align with] + +## Reframes Prepared + +| Potential Objection/Weakness | Reframe Type | Specific Language | +|------------------------------|-------------|-------------------| +| [Objection 1] | [Context/Content] | "[Exact words to use]" | +| [Objection 2] | [Context/Content] | "[Exact words to use]" | +| [Objection 3] | [Context/Content] | "[Exact words to use]" | + +## Meta-Model Questions Ready +1. [Question targeting expected vague claim] +2. [Question targeting expected generalisation] +3. [Question targeting expected distortion] + +## Desired Outcome +[Specific, measurable outcome for this interaction] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](emotional-intelligence.md)** -- EQ provides the self-awareness foundation that prevents NLP techniques from becoming manipulation; empathy is the ethical guardrail for influence. +- **[GROW Model](grow-model.md)** -- GROW's questioning methodology complements NLP's meta-model; both frameworks use precise questioning to move from vagueness to clarity and action. +- **[Myers-Briggs Type Indicator](myers-briggs-type-indicator.md)** -- MBTI preferences parallel NLP's representational systems as complementary lenses for understanding communication style differences. +- **[Persuasion and Influence](../leadership/persuasion-and-influence.md)** -- NLP's rapport and reframing techniques are practical tools within the broader leadership skill of ethical persuasion across stakeholder relationships. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- NLP's pacing-and-leading and representational system matching directly enhance how leaders structure and deliver narratives for maximum audience impact. +- **[Cialdini's Influence](cialdini-influence.md)** -- Cialdini's principles of social proof and reciprocity complement NLP's interpersonal techniques, providing both macro-level persuasion dynamics and micro-level communication adjustments. diff --git a/plugins/foreman/content/skills/frameworks/organisational-culture.md b/plugins/foreman/content/skills/frameworks/organisational-culture.md new file mode 100644 index 0000000..622992d --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/organisational-culture.md @@ -0,0 +1,197 @@ +--- +name: "organisational-culture" +description: "Audits organizational culture using Schein's three-level model: + visible artifacts, espoused values, and basic underlying assumptions. + Diagnoses gaps between stated values and actual behaviour to reveal the + invisible beliefs driving organizational dynamics. Use when experiencing + culture dilution during rapid hiring, planning M&A cultural integration, + diagnosing why culture change initiatives fail, or auditing founder imprint on + company norms." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - culture + - leadership + - organisational-design + - values + - assumptions +related_skills: + - tuckman-team-stages + - belbin-team-roles + - maslow-hierarchy + - radical-candor +author: "Fatih Guner" +--- + +# Organisational Culture + +What you see in an organisation -- the open-plan offices, the Friday beers, the branded hoodies -- is the tip of the iceberg. Roughly ten percent of culture is visible. The remaining ninety percent sits submerged: the unspoken beliefs, the unstated power hierarchies, the assumptions so deeply embedded that no one thinks to question them. Edgar Schein, the MIT professor who spent decades dissecting how organisations actually work, argued that most culture-change initiatives fail because they redecorate the tip while ignoring the mass below the waterline. The iceberg metaphor is not merely illustrative; it is diagnostic. Misread which level of culture you are dealing with, and your intervention will achieve nothing -- or worse, provoke the immune response that organisations mount against superficial change. + +Schein's framework identifies three distinct layers, each progressively harder to observe and exponentially harder to alter. Understanding these layers is not an academic exercise. For founders, it is the difference between building a company that scales with coherence and one that fractures under the weight of its own contradictions. + +--- + +## The Framework + +### Layer 1: Artifacts (The Visible Surface) + +Artifacts are everything you can see, hear, and touch when you walk into an organisation. Office layout. Dress code. Meeting rituals. The language people use in Slack channels. The way decisions get announced. These are tangible, immediately observable -- and profoundly misleading if interpreted without context. + +A startup with a foosball table and no dress code might appear egalitarian. The reality could be a cult of personality where the CEO's whims override all process. Artifacts are symptoms, not diagnoses. + +**Common artifacts include:** +- Physical environment and workspace design +- Published values and mission statements +- Rituals, ceremonies, and recurring events +- Stories and legends told about the company's origins +- Organisational charts and reporting structures +- Technology choices and communication tools + +### Layer 2: Espoused Values (What People Say Matters) + +One level below artifacts sit the declared beliefs, strategies, and philosophies. These are the values on the website, the principles recited during onboarding, the strategic priorities invoked in board meetings. Espoused values represent what the organisation *claims* to be. + +The critical question: do espoused values match actual behaviour? When a company proclaims "we value work-life balance" while promoting only those who answer email at midnight, a gap has opened between Layer 2 and Layer 3. This gap is where cynicism breeds and trust erodes. + +**Diagnostic indicators of alignment (or misalignment):** + +| Espoused Value | Aligned Behaviour | Misaligned Behaviour | +|----------------|-------------------|----------------------| +| "Innovation" | Budget for experiments, tolerance of failure | Punishing failed projects, rigid approval processes | +| "Transparency" | Open financials, candid all-hands | Information hoarding, surprise layoffs | +| "Customer first" | Support team empowered to act | Support metrics optimised for speed over resolution | +| "Meritocracy" | Promotions track results | Promotions track tenure or political skill | + +### Layer 3: Basic Underlying Assumptions (The Invisible Bedrock) + +The deepest layer consists of unconscious, taken-for-granted beliefs. These assumptions are so ingrained they feel like objective reality rather than cultural choices. They govern how people perceive problems, define truth, relate to time, and think about human nature. + +Schein identified several dimensions of basic assumptions: + +- **Relationship to environment:** Does the organisation believe it controls its market, or must adapt to it? +- **Nature of truth:** Is truth discovered through debate, authority, or data? +- **Human nature:** Are people fundamentally trustworthy (Theory Y) or requiring supervision (Theory X)? +- **Nature of relationships:** Is hierarchy natural, or should all voices carry equal weight? +- **Time orientation:** Does the culture privilege the past (tradition), present (agility), or future (vision)? + +These assumptions are rarely articulated. They surface only when violated -- when a new hire from a different culture does something that provokes an emotional reaction disproportionate to the action itself. That disproportionate reaction is the clearest signal that a basic assumption has been touched. + +### How the Layers Interact + +Change flows downward with great difficulty. A founder can redesign the office (Layer 1) overnight. Rewriting the values statement (Layer 2) takes a quarterly offsite. Shifting basic assumptions (Layer 3) requires years of consistent leadership behaviour, critical incidents handled visibly, and patient reinforcement. + +Conversely, diagnosis flows upward. To understand Layer 3, observe the patterns in Layer 1 and the contradictions between Layer 1 and Layer 2. The gap between artifacts and espoused values is the most reliable indicator of what the organisation actually believes. + +--- + +## Prompts + +**Prompt 1 -- Culture Audit:** +> Conduct a three-level culture audit for my company using Schein's framework. At the Artifacts level, I will describe our office setup, communication norms, meeting practices, and visible rituals. At the Espoused Values level, analyse our stated mission, values, and strategic principles. Then help me identify the Basic Underlying Assumptions by probing for gaps between what we say and what we do. Company context: [describe company stage, size, industry, and any recent cultural tensions]. + +**Prompt 2 -- Misalignment Diagnosis:** +> I suspect a gap between our espoused values and our actual organisational behaviour. Our stated values include [list values]. Recent incidents suggesting misalignment include [describe incidents]. Using Schein's model, help me diagnose which basic underlying assumptions are driving the contradictory behaviour, and propose interventions at each of the three levels. + +**Prompt 3 -- Culture Integration for M&A:** +> We are acquiring [describe target company]. Using Schein's three levels of organisational culture, help me map the cultural differences between our two organisations. For each level (artifacts, espoused values, basic assumptions), identify potential collision points and recommend an integration strategy that addresses each layer explicitly. + +**Prompt 4 -- Founder Culture Imprint:** +> As a founder at [stage], I recognise that my personal behaviours are imprinting onto the company culture. Using Schein's framework, help me audit which of my assumptions, habits, and decisions are becoming embedded as basic underlying assumptions. Identify which imprints are serving the company well and which may become liabilities at scale. + +--- + +## Use Cases + +**Series A SaaS Company Experiencing Growing Pains** +A 45-person B2B SaaS startup has doubled headcount in eight months. The founders notice that new hires "don't get the culture" -- they schedule unnecessary meetings, escalate decisions that should be made autonomously, and default to formal communication. A Schein analysis reveals that the company's basic assumption -- that competent adults make decisions without permission -- was never articulated; it was transmitted osmotically when the team was fifteen people. The fix operates at all three layers: codify the assumption into explicit values (Layer 2), redesign onboarding rituals to demonstrate autonomous decision-making (Layer 1), and have leadership visibly reinforce the assumption by publicly celebrating independent judgment (Layer 3 maintenance). + +**Growth-Stage Fintech After a Compliance Crisis** +A payments company with 200 employees suffers a regulatory penalty. Leadership declares a "compliance-first culture" and introduces new processes, reporting lines, and training (Layer 1 and Layer 2 changes). Six months later, the same risk-taking behaviours persist. Schein's framework reveals that the basic assumption -- "move fast, regulators are slow" -- was forged during the company's scrappy early days and reinforced by the promotion of individuals who embodied it. Surface-level changes cannot override Layer 3 assumptions. The intervention requires replacing key role models, restructuring incentives, and having the CEO publicly acknowledge past assumptions that no longer serve the company. + +**Pre-IPO Enterprise Company Merging Two Engineering Cultures** +Following an acquisition, two engineering teams with fundamentally different assumptions about quality (one ships fast and iterates; the other ships only when perfect) must integrate. Artifacts conflict immediately: different code review practices, different deployment cadences, different definitions of "done." Mapping each team's three layers reveals that the conflict is not about process -- it is about basic assumptions regarding the nature of professional excellence. Resolution requires surfacing both assumptions explicitly, negotiating a shared assumption appropriate to the combined entity, and rebuilding processes and rituals from that new foundation. + +--- + +## Anti-Patterns + +1. **Redecorating the Iceberg Tip.** Installing ping-pong tables, rewriting the mission statement, or launching a "culture committee" without addressing underlying assumptions. These initiatives generate cynicism when employees observe that actual behaviour remains unchanged. Artifacts-only interventions are the most common and most futile form of culture work. + +2. **Assuming Culture Is What the Founder Says It Is.** Founders often conflate their *intended* culture with the *actual* culture. Schein's framework demands empirical observation, not aspiration. The culture is what people do when no one is watching, not what the deck says. + +3. **Treating Culture as Monolithic.** Large organisations contain subcultures -- engineering, sales, operations -- each with distinct assumptions. Applying a single cultural analysis to the entire company produces a fiction. Map subcultures independently, then identify where they align and where they collide. + +4. **Skipping Layer 3 in Due Diligence.** M&A due diligence routinely examines financials, technology, and talent. It almost never examines basic assumptions. The result: post-merger integration failures that no amount of process harmonisation can fix, because the two organisations hold incompatible beliefs about how work should be done. + +5. **Expecting Speed.** Layer 3 assumptions take years to form and years to change. Leaders who announce a "culture transformation" with a six-month timeline are confusing artifacts with assumptions. Genuine culture change is measured in leadership generations, not quarters. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder imprint audit | Culture is being formed now, largely from the founder's unconscious assumptions. This is the highest-leverage moment to be intentional. | +| Growth | Articulation and codification | As headcount exceeds Dunbar-adjacent numbers (~50-150), osmotic culture transmission fails. Assumptions must become explicit values, and values must become visible artifacts. | +| Scale | Subculture management | Multiple teams, geographies, and functions develop distinct subcultures. The task shifts from building culture to managing cultural coherence across diverse groups. | + +At early traction, the primary risk is accidental culture -- the founder's unexamined habits becoming organisational doctrine. At growth, the risk is dilution -- rapid hiring overwhelming the cultural carriers. At scale, the risk is fragmentation -- subcultures diverging until the organisation loses coherence. + +--- + +## Output Template + +```markdown +# Organisational Culture Audit: [Company Name] + +## Layer 1: Artifacts (Observable) +- **Physical environment:** [Describe workspace, layout, remote/hybrid setup] +- **Communication norms:** [Tools, formality, response time expectations] +- **Rituals and ceremonies:** [All-hands, retrospectives, celebrations] +- **Symbols and stories:** [Origin myths, hero narratives, cautionary tales] +- **Decision-making patterns:** [Who decides, how fast, with what process] + +## Layer 2: Espoused Values +- **Official values:** [As stated on website/internal docs] +- **Strategic principles:** [As communicated by leadership] +- **Alignment assessment:** [Where behaviour matches values / where it diverges] + +## Layer 3: Basic Underlying Assumptions (Inferred) +- **Relationship to environment:** [Control vs. adapt] +- **Nature of truth:** [Data vs. authority vs. debate] +- **Human nature assumption:** [Trust vs. verify] +- **Relationship orientation:** [Hierarchy vs. egalitarian] +- **Time orientation:** [Past / present / future] + +## Gap Analysis +| Espoused Value | Observed Behaviour | Inferred Assumption | Gap Severity | +|----------------|-------------------|---------------------|--------------| +| [Value] | [What actually happens] | [What this reveals] | High/Med/Low | + +## Recommended Interventions +### Layer 1 (Quick wins): +- [Artifact changes] +### Layer 2 (Medium-term): +- [Values clarification / realignment] +### Layer 3 (Long-term): +- [Assumption-level work required] + +## Risk Assessment +[Key cultural risks if no action is taken] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Team development dynamics operate within the cultural container Schein describes; understanding both reveals why some teams thrive and others stall. +- **[Radical Candor](radical-candor.md)** -- A feedback culture is an artifact sustained by espoused values, which only works when basic assumptions support psychological safety. +- **[Psychological Safety](psychological-safety.md)** -- Edmondson's framework addresses the Layer 3 assumption about whether interpersonal risk-taking is safe; culture change initiatives fail when this assumption remains hostile. +- **[Kotter's Change Model](kotter-change-model.md)** -- Kotter's eight steps provide the process methodology for altering culture; Schein's three layers explain why each step is necessary and where resistance originates. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- Translates Schein's organizational-level theory into team-level practice, helping leaders build and sustain culture within their immediate sphere of influence. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- Culture transformation is the deepest form of organizational change; this skill addresses the leadership behaviors required to shift Layer 3 assumptions over time. diff --git a/plugins/foreman/content/skills/frameworks/porters-five-forces.md b/plugins/foreman/content/skills/frameworks/porters-five-forces.md new file mode 100644 index 0000000..27a3136 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/porters-five-forces.md @@ -0,0 +1,219 @@ +--- +name: "porters-five-forces" +description: "Analyzes competitive industry dynamics using Porter's Five Forces + framework. Evaluates threat of new entrants, supplier power, buyer power, + substitution threats, and competitive rivalry. Use when assessing market entry + decisions, developing competitive strategy, evaluating industry + attractiveness, or analyzing pricing power." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - competitive-analysis + - industry-structure + - strategy + - market-entry + - profitability +related_skills: + - blue-ocean-strategy + - swot-pest-analysis + - art-of-war + - business-model-canvas + - scenario-planning +author: "Fatih Guner" +--- + +# Porter's Five Forces + +Most people use Porter's Five Forces wrong. They fill in the five boxes, label each force as "high," "medium," or "low," and conclude that they have performed strategic analysis. They have not. Michael Porter's framework, introduced in his 1979 *Harvard Business Review* article "How Competitive Forces Shape Strategy" and elaborated in *Competitive Strategy* (1980), is not a checklist. It is a theory of profitability -- an explanation of why some industries are structurally profitable and others are not, and why positioning within an industry matters more than operational excellence. The five forces determine the profit potential of an industry. Understanding them determines whether a startup is entering a gold mine or a tar pit. Misunderstanding them -- which is the norm -- produces strategies that fight industry structure rather than leveraging it. + +--- + +## The Framework + +### The Five Forces + +Porter's model identifies five competitive forces that collectively determine the intensity of competition and, therefore, the profit potential of any industry. + +``` + ┌───────────────────────┐ + │ THREAT OF NEW │ + │ ENTRANTS │ + └───────────┬───────────┘ + │ + ▼ +┌──────────────┐ ┌───────────────────────┐ ┌──────────────┐ +│ BARGAINING │───▶│ INDUSTRY RIVALRY │◀───│ BARGAINING │ +│ POWER OF │ │ (among existing │ │ POWER OF │ +│ SUPPLIERS │ │ competitors) │ │ BUYERS │ +└──────────────┘ └───────────┬───────────┘ └──────────────┘ + │ + ▼ + ┌───────────────────────┐ + │ THREAT OF │ + │ SUBSTITUTES │ + └───────────────────────┘ +``` + +### Force 1: Threat of New Entrants + +New entrants bring new capacity, new resources, and the desire to gain market share. The seriousness of the threat depends on barriers to entry: + +| Barrier | Description | Startup Implication | +|---------|-------------|---------------------| +| Economies of scale | Incumbents produce at lower per-unit cost | Niche focus can circumvent scale requirements | +| Capital requirements | Large upfront investment needed | SaaS and asset-light models reduce this barrier | +| Switching costs | Cost to customers of changing providers | Building switching costs early creates defensibility | +| Access to distribution | Incumbents control channels | Direct-to-customer and platform strategies bypass traditional distribution | +| Regulatory barriers | Licenses, certifications, compliance | Can be a moat if the startup achieves compliance first | +| Network effects | Value increases with user count | The most powerful barrier when achieved; nearly insurmountable | + +For startups: you are the new entrant. The barriers you overcome to enter are the same barriers that will protect you once inside -- if you build them. + +### Force 2: Bargaining Power of Suppliers + +Suppliers are powerful when they are concentrated, provide differentiated inputs, face low switching costs for their own business, or can credibly threaten forward integration. Powerful suppliers capture value by charging higher prices or reducing quality. + +For startups: key suppliers include cloud providers, payment processors, talent pools, and API providers. A startup dependent on a single API provider whose pricing can change unilaterally faces significant supplier power. Diversification, commoditization of inputs, and building proprietary alternatives are defensive strategies. + +### Force 3: Bargaining Power of Buyers + +Buyers are powerful when they are concentrated (few large customers), purchase large volumes, face low switching costs, or can credibly threaten backward integration (building the product themselves). Powerful buyers capture value by demanding lower prices or higher quality. + +For startups: customer concentration is the most common buyer power trap. A startup where one customer represents 40% of revenue has granted that customer enormous leverage. The strategic response is to diversify the customer base as early as possible and to create switching costs through integration depth, data lock-in, or workflow embedding. + +### Force 4: Threat of Substitutes + +A substitute is not a direct competitor -- it is a different product that serves the same need. The threat is highest when the substitute offers an attractive price-performance trade-off and when switching costs are low. + +For startups: the most dangerous substitute is often "doing nothing" or "doing it manually." A project management tool competes not just with other tools but with spreadsheets, email chains, and whiteboards. Understanding the true substitutes -- especially non-consumption -- prevents strategic myopia. + +### Force 5: Industry Rivalry + +Rivalry is intense when competitors are numerous and roughly equal in size, industry growth is slow, fixed costs are high, products are undifferentiated, and exit barriers prevent competitors from leaving. Intense rivalry drives down prices and profitability for all participants. + +For startups: entering a market with intense rivalry among well-funded incumbents is the most common cause of startup failure-by-competition. The five forces analysis should prevent this by revealing unattractive industry structures before capital is committed. + +### The Synthesis: Industry Attractiveness + +The five forces collectively produce an industry attractiveness assessment: + +- **Attractive industry**: High barriers to entry, weak supplier and buyer power, few substitutes, moderate rivalry. Incumbents earn above-average returns. +- **Unattractive industry**: Low barriers, powerful suppliers and buyers, many substitutes, intense rivalry. Even good companies earn below-average returns. + +Porter's deepest insight: company strategy should begin with industry selection. Competing brilliantly in a structurally unattractive industry produces mediocre returns. Competing adequately in a structurally attractive industry produces superior returns. Industry structure trumps execution. + +--- + +## Prompts + +**Prompt 1 -- Full Five Forces Analysis:** +> Conduct a Porter's Five Forces analysis of my industry. I compete in [describe industry/market segment]. For each force, assess the intensity (Weak/Moderate/Strong) and identify the specific factors driving that assessment. Then provide an overall industry attractiveness rating and its implications for my startup's strategy. Present the analysis as both a summary table and a detailed narrative for each force. + +**Prompt 2 -- Entry Barrier Assessment:** +> I am considering entering [describe market/industry]. Using Porter's framework, assess the barriers to entry I will face. For each barrier type (economies of scale, capital requirements, switching costs, distribution access, regulatory requirements, network effects, brand loyalty), rate the height of the barrier and my realistic ability to overcome it. Then assess: once I overcome these barriers, which ones will protect me from subsequent entrants? Identify the barriers I should actively build. + +**Prompt 3 -- Competitive Position Optimization:** +> Given this Five Forces analysis of my industry [paste or describe analysis], help me design a competitive position that exploits the structure rather than fighting it. Where are the pockets of profitability? Which customer segments face the least buyer power? Which supplier relationships can be restructured? What positioning would reduce our exposure to rivalry? Frame the output as a strategic positioning recommendation. + +**Prompt 4 -- Dynamic Forces Projection:** +> My industry's five forces are currently [describe current state]. Project how each force is likely to change over the next 3-5 years, considering these trends: [describe relevant technology, regulatory, demographic, or competitive trends]. Which forces are strengthening? Which are weakening? How should my strategy adapt to the evolving industry structure? Present as a current vs. future comparison for each force. + +**Prompt 5 -- Substitute Threat Deep Dive:** +> Analyze the substitute threats to my product/service. My offering is [describe]. Go beyond direct competitors and identify ALL substitutes -- including non-consumption, manual alternatives, and products from adjacent industries that serve the same underlying need. For each substitute, assess: price-performance relative to my offering, switching costs from the substitute, and the conditions under which customers would prefer the substitute. Rank substitutes by threat level. + +--- + +## Use Cases + +**Idea-Stage Founder Evaluating Two Market Opportunities** +A technical founder with expertise in computer vision must choose between building a quality inspection product for manufacturing (Market A) and a visual search product for e-commerce (Market B). The Five Forces analysis reveals that Market A has moderate barriers to entry (domain expertise required), weak buyer power (fragmented customer base of thousands of factories), few substitutes (manual inspection is costly and error-prone), and moderate rivalry (three incumbents, none dominant). Market B has low barriers (many CV APIs available), strong buyer power (a few large e-commerce platforms dominate demand), strong substitutes (text search is free and familiar), and intense rivalry (dozens of startups, several well-funded). The structural analysis clearly favors Market A, independent of the founder's personal preference. + +**Growth-Stage SaaS Company Experiencing Margin Pressure** +A $10M ARR vertical SaaS company faces declining margins despite growing revenue. The Five Forces analysis reveals the cause: buyer power has increased as three enterprise customers now represent 55% of revenue, and each is demanding volume discounts and custom features. Supplier power has also increased as the company's reliance on a single cloud provider and a single data vendor has deepened. The strategic response targets both forces: a customer diversification initiative to reduce concentration below 20% per customer, and a multi-cloud architecture initiative to restore supplier optionality. + +**Scale-Stage Company Evaluating Vertical Integration** +A 1,000-person company evaluates whether to build an in-house capability currently provided by a supplier. The Five Forces lens reframes this decision: the supplier has strong bargaining power (proprietary technology, few alternatives, high switching costs). Vertical integration would eliminate this force entirely. The analysis also reveals that the in-house capability could become a new revenue line -- the company could become a supplier to its own competitors, converting a cost center into a profit center while simultaneously neutralizing a competitive force. + +--- + +## Anti-Patterns + +1. **Using Five Forces as a static snapshot.** Industry structure evolves. Technology shifts, regulatory changes, and new entrants alter the balance of forces continuously. An analysis conducted once and never updated becomes a historical artifact rather than a strategic tool. The framework must be reapplied at least annually, and whenever a significant structural change occurs. + +2. **Confusing competitors with substitutes.** Direct competitors offer similar products. Substitutes serve the same need through different means. Mistaking one for the other leads to strategic myopia -- fighting feature wars with competitors while a substitute captures the market from an entirely different direction. + +3. **Treating all five forces as equally important.** In any given industry, one or two forces dominate the profitability equation. A rigorous analysis identifies which forces matter most and focuses strategic energy accordingly. Equal weighting across all five forces produces unfocused strategy. + +4. **Ignoring the force of complementors.** Porter's original model does not explicitly include complementary products and services, though later scholars (notably Brandenburger and Nalebuff) have argued that "complementors" constitute a sixth force. For technology startups, the strength of the ecosystem of complementary products often determines competitive dynamics as much as the five traditional forces. + +5. **Using the framework to justify inaction.** An unattractive industry structure does not mean "do not enter." It means "enter with a strategy designed for that structure." Some of the most successful startups have entered structurally challenging industries with positioning strategies that neutralized the most powerful forces. The analysis informs strategy; it does not replace it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Industry selection | The most consequential use of Five Forces: evaluating which industry to enter. At this stage, you have maximum flexibility and should choose structural attractiveness over personal enthusiasm. A mediocre product in an attractive industry outperforms a brilliant product in a structurally hostile one. | +| Validation | Barrier identification | With the industry chosen, identify which barriers to entry you must overcome and which you can circumvent. Begin building the barriers that will protect you: switching costs, integration depth, network effects, data advantages. | +| Early Traction | Buyer power management | As revenue grows, monitor customer concentration obsessively. The easiest time to diversify is when you have multiple prospects; the hardest is when a single customer dominates. Also, begin reducing supplier power through diversification and alternative development. | +| Growth | Rivalry positioning | Competition intensifies. Use Five Forces to choose where to compete and, critically, where not to. Differentiation strategies that reduce rivalry (serving a distinct segment, creating switching costs) are more valuable than operational excellence that merely matches competitors. | +| Scale | Industry shaping | At scale, the company has enough influence to shape industry structure rather than merely respond to it. Acquisitions, platform strategies, and standards-setting can alter barriers to entry, supplier power, and rivalry dynamics in the company's favor. | + +--- + +## Output Template + +```markdown +# Porter's Five Forces Analysis + +**Industry/Market:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Forces Summary + +| Force | Intensity | Key Drivers | Strategic Implication | +|-------|-----------|-------------|---------------------| +| Threat of New Entrants | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Supplier Power | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Buyer Power | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Threat of Substitutes | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Industry Rivalry | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | + +## Overall Industry Attractiveness: [Attractive / Moderate / Unattractive] + +## Dominant Forces +The forces with greatest impact on profitability in this industry are: +1. [Force] -- because [reason] +2. [Force] -- because [reason] + +## Strategic Recommendations +Given this industry structure, the optimal positioning strategy is: +1. [Recommendation targeting dominant force] +2. [Recommendation targeting secondary force] +3. [Barrier-building priority] + +## Monitoring Plan +| Force | Key Indicator to Watch | Review Frequency | +|-------|----------------------|-----------------| +| [Force] | [Indicator] | [Quarterly/Annual] | +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- If Five Forces reveals an unattractive industry, Blue Ocean Strategy provides the methodology for creating a new market space where the forces are more favorable. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- Five Forces analyzes external industry structure; SWOT combines this with internal capability assessment to produce a complete strategic picture. +- **[Business Model Canvas](business-model-canvas.md)** -- Once Five Forces identifies the structural dynamics, the Canvas designs the business model that navigates them effectively. +- **[Scenario Planning](scenario-planning.md)** -- Combines with Five Forces to project how industry structure might evolve under different scenarios, enabling preemptive strategic adaptation. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Disruption reshapes all five forces simultaneously; Christensen's framework explains how new entrants can neutralize incumbent advantages that Porter's model identifies. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- Five Forces analysis provides the external intelligence that strategic thinking translates into organizational direction and resource allocation decisions. diff --git a/plugins/foreman/content/skills/frameworks/product-life-cycle.md b/plugins/foreman/content/skills/frameworks/product-life-cycle.md new file mode 100644 index 0000000..22a5886 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/product-life-cycle.md @@ -0,0 +1,248 @@ +--- +name: "product-life-cycle" +description: "Diagnoses a product's current lifecycle phase -- introduction, growth, maturity, or decline -- and prescribes phase-appropriate strategy for pricing, marketing, investment, and competitive response. Use when assessing whether a product is entering maturity, planning portfolio balance across lifecycle stages, timing market entry, designing extension strategies for declining products, or deciding between harvest, niche, divest, and exit options." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - product-strategy + - market-timing + - competitive-dynamics + - pricing-strategy + - portfolio-management +related_skills: + - growth-share-matrix + - disruptive-innovation + - doblin-ten-types + - kaizen-bpr +author: "Fatih Guner" +--- + +# Product Life Cycle + +The BlackBerry was once the most coveted device in corporate America -- the "CrackBerry" that redefined mobile communication. The fax machine was, for two decades, as essential to business as the telephone. The Sony Walkman created the portable music category, sold 400 million units, and was rendered obsolete in under a decade. Every product, however dominant in its moment, follows a biological arc: birth, growth, maturity, and decline. Theodore Levitt formalised this observation in a 1965 Harvard Business Review article, and the Product Life Cycle (PLC) has since become one of the foundational frameworks of marketing and business strategy -- not because it predicts the future with precision, but because it forces the uncomfortable question every entrepreneur must eventually answer: what phase is your product in, and are you managing accordingly? + +The framework's power lies in its strategic implications. The same product, in different phases, demands different pricing, different marketing, different competitive responses, and different levels of investment. Companies that manage a growth-phase product as if it were mature leave money on the table. Companies that manage a mature product as if it were still growing burn cash without return. And companies that refuse to acknowledge decline preside over slow organisational death. + +--- + +## The Framework + +### The Four Phases + +#### Phase 1: Introduction + +The product enters the market. Sales are low. Costs are high. Profit is negative or minimal. The customer base consists of innovators and early adopters who tolerate imperfection in exchange for novelty or functional advantage. + +**Characteristics:** +- High unit cost due to low volume and manufacturing learning curve +- Heavy investment in education and awareness (the market does not yet understand the product) +- Limited or no competition (but watch for fast followers) +- Pricing strategy: either skimming (high price, early revenue capture) or penetration (low price, rapid adoption) +- Distribution is narrow; channels are being established + +**Strategic imperative:** Survive long enough for the market to develop. The introduction phase kills more products than competition does -- not because the product is bad, but because the company runs out of capital or patience before demand materialises. + +**Duration signal:** The introduction phase ends when sales growth accelerates and competitors begin entering the market. + +#### Phase 2: Growth + +Demand accelerates. Sales curve steepens. Competitors enter, attracted by the market's potential. Unit costs decline as volume increases. Profits emerge and expand. The customer base broadens from early adopters to the early majority. + +**Characteristics:** +- Revenue growing 20%+ per period (the exact rate is sector-dependent) +- Competitors entering and product differentiation becoming critical +- Distribution expanding; channels competing for the product +- Marketing shifts from awareness to differentiation +- Pricing remains stable or declines slightly as competition increases and scale drives costs down + +**Strategic imperative:** Maximise market share. The growth phase is the window during which market positions are established. Companies that invest aggressively in distribution, brand building, and product improvement during growth capture the positions they will hold through maturity. Underinvestment during growth creates a permanent competitive handicap. + +**Duration signal:** The growth phase ends when the rate of sales growth begins to decelerate -- not when growth stops, but when it slows. + +#### Phase 3: Maturity + +The market approaches saturation. Growth decelerates and eventually stabilises. Competition intensifies as rivals fight for share in a market that is no longer expanding. Profits peak and then decline as price competition erodes margins. The customer base is mainstream; differentiation is difficult. + +**Characteristics:** +- Sales growth flattening to low single digits +- Intense competition; weaker competitors begin exiting +- Marketing emphasis shifts to retention and loyalty +- Product innovation is incremental; features converge across competitors +- Pricing under pressure; margins decline +- Overproduction and excess capacity may emerge + +**Strategic imperative:** Defend share and maximise profitability. This is the phase where operational efficiency matters most. Companies that have built scale, brand loyalty, and process efficiency during growth are well-positioned. Those that have not face a grinding competitive struggle. Strategic options include product modification (new features, quality improvements, style changes), market modification (new segments, new geographies, new use cases), and marketing mix modification (price adjustments, channel expansion, promotional innovation). + +**Duration signal:** Maturity ends when sales begin sustained decline despite competitive efforts. + +#### Phase 4: Decline + +Sales fall. The market contracts as customers migrate to substitute products or new technologies. Remaining competitors face a shrinking pie. Margins collapse for all but the most efficient producers. Investment in the product yields diminishing returns. + +**Characteristics:** +- Sustained sales decline over multiple periods +- Competitors exiting the market +- Customer base ageing; new customer acquisition near zero +- Investment in the product generates negative ROI +- Remaining demand concentrated in niche segments + +**Strategic imperative:** Manage the decline deliberately. The options are: +1. **Harvest** -- Reduce investment to minimum, extract maximum remaining profit, fund other products +2. **Niche** -- Retreat to a defensible segment where loyal customers sustain profitable operations +3. **Divest** -- Sell the product line to a competitor who can achieve consolidation economics +4. **Exit** -- Discontinue the product and redeploy resources + +The worst strategy in decline is denial: continuing to invest as if growth will return. It rarely does. + +### The PLC Curve + +``` +Sales + ^ + | ___________ + | / \ + | / Maturity \ + | / \ + | / \ Decline + | / \ + | Growth / \ + | / \___ + | Introduction/ + | ___/ + +-------------------------------------------------> Time +``` + +### Profit Curve Overlay + +Profit follows a different trajectory: negative during introduction, rising sharply during growth, peaking during early maturity, and declining through late maturity and decline. The gap between the sales curve and the profit curve is critical -- a product can show healthy sales while profitability is already deteriorating. + +--- + +## Prompts + +**Prompt 1 -- Phase Diagnosis:** +> "Analyse my product's current life cycle phase. Here are the key indicators: [sales trend over past 6-12 months, competitive landscape, customer acquisition trends, pricing pressure, margin trajectory]. Based on these indicators, which PLC phase is my product in? What are the three most important strategic actions for this phase?" + +**Prompt 2 -- Phase Transition Planning:** +> "My product appears to be transitioning from [current phase] to [next phase]. What are the early warning signals I should monitor to confirm this transition? What strategic, operational, and financial changes should I prepare for? Create a 90-day transition plan that adapts my pricing, marketing, product development, and resource allocation to the incoming phase." + +**Prompt 3 -- Portfolio Phase Mapping:** +> "Map each of my products to its PLC phase: [list products with relevant metrics]. Assess whether the portfolio is balanced -- do we have products in introduction/growth to replace revenue as mature products decline? Identify portfolio gaps and recommend timing for new product introductions." + +**Prompt 4 -- Extension Strategy Design:** +> "My product is in late maturity and showing early signs of decline. Design three extension strategies that could reignite growth: (1) product modification (features, quality, or design changes), (2) market modification (new segments, geographies, or use cases), and (3) marketing mix modification (pricing, distribution, or promotion changes). For each, estimate the investment required and the probability of success." + +**Prompt 5 -- Decline Management:** +> "My product is in the decline phase with these metrics: [sales decline rate, remaining market size, competitor exits, margin trajectory]. Evaluate the four decline strategies (harvest, niche, divest, exit) for my situation. Recommend the optimal approach and create a 6-month execution plan including financial projections." + +--- + +## Use Cases + +**Validation-Stage Founder Timing Market Entry** + +A founder developing a plant-based protein product analyses the PLC of the broader plant-based food market. Industry data shows that the category has moved past introduction (awareness is high, major players have entered) and is in early growth (sales growing 20%+ annually, new brands entering weekly, distribution expanding into mainstream retail). PLC analysis informs the entry strategy: the growth phase favours differentiation over education. Rather than spending marketing budget on explaining why plant-based protein matters (an introduction-phase message), the founder focuses on what makes this product different from the dozens already available (a growth-phase message). Pricing follows a penetration strategy, since growth-phase markets reward share capture over margin maximisation. + +**Growth-Stage Company Managing a Maturing Core Product** + +A project management SaaS tool that drove the company's growth now shows decelerating revenue growth (from 80% to 25% YoY), increasing competitive convergence (five major competitors with similar features), and declining new customer acquisition rates. PLC diagnosis: the product is transitioning from growth to maturity. The strategic response: shift investment from feature development (growth-phase priority) to operational efficiency and customer retention (maturity-phase priorities). Simultaneously, the company launches a new AI-powered analytics module positioned as a growth-phase product that leverages the existing customer base as its initial market. The core product becomes the cash cow that funds the new product's introduction phase. + +**Scale-Stage Brand Extending a Declining Product** + +A consumer electronics company observes that its flagship hardware product -- once a category leader -- has experienced three consecutive quarters of declining sales as the market shifts toward software-based alternatives. Rather than investing in a next-generation hardware product (sustaining a declining category), the PLC analysis recommends a market modification strategy: repositioning the hardware product for the professional niche segment where physical devices retain value (recording studios, live performance), while launching a software-based product for the mainstream market. The hardware product transitions from mass-market decline to niche maturity, sustaining profitability at lower volume. + +--- + +## Anti-Patterns + +**Phase Denial.** The most dangerous anti-pattern. Founders and executives who insist their product is "still in growth" when every indicator signals maturity or decline. Revenue growth deceleration, margin compression, and competitive convergence are objective signals. Interpreting them as temporary setbacks rather than structural transitions leads to misallocated investment and missed strategic windows. + +**Assuming All Products Follow the Same Curve.** PLC durations vary enormously. Fashion products may cycle through all four phases in eighteen months. Infrastructure products may remain in maturity for decades. Technology platforms may skip growth and move directly from introduction to maturity if they achieve rapid network effects. The framework describes phases, not timelines. + +**Applying Growth Strategies to Mature Products.** Pouring marketing spend into customer acquisition for a product in maturity, where the addressable market is saturated and incremental customers are expensive. Maturity demands retention and efficiency, not acquisition and expansion. The metrics change; the strategy must change with them. + +**Ignoring Decline Signals in Favour of Extension Hope.** Extension strategies (product modification, market modification, marketing mix changes) can work -- but they succeed in roughly one case in three. Founders who serially extend a declining product rather than investing in the next product are optimising for the past. Every extension attempt should have a predefined success threshold and a kill date. + +**Treating the PLC as Deterministic.** The framework describes a tendency, not a law of nature. Products can be revived (vinyl records). Markets can re-enter growth after decline (electric vehicles). Disruption can compress cycles or restart them. The PLC is a diagnostic tool, not a prophecy. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Assess market phase before entering | Entering a market in late maturity or decline is substantially harder than entering during introduction or early growth | +| Validation | Confirm you are in the right phase | Validate whether the market is genuinely in the phase you believe; misdiagnosis leads to misallocated strategy | +| Early Traction | Invest for the growth phase | If traction signals confirm a growth-phase market, invest aggressively in share capture | +| Growth | Prepare for maturity | Build the operational efficiency and brand loyalty that will sustain you when growth decelerates | +| Scale | Manage the portfolio across phases | Ensure that new products in introduction/growth will replace revenue as current products mature and decline | + +At the idea stage, PLC analysis answers a threshold question: is this market in a phase that rewards new entrants? Introduction and early growth phases favour startups because positions are not yet locked. Late maturity and decline phases favour incumbents with established share and economies of scale. A superior product entering a declining market faces headwinds that no amount of execution can overcome. + +At scale, the PLC becomes a portfolio management tool. The healthiest companies maintain a pipeline of products at different lifecycle stages: mature products funding the introduction of new ones, growth products building the future revenue base, and declining products being managed out of the portfolio deliberately rather than by neglect. + +--- + +## Output Template + +**Target Audience: Product Team / Head of Product** + +```markdown +# Product Life Cycle Assessment: [Product Name] +## Date: [Date] + +### Phase Diagnosis +- **Current phase:** [Introduction / Growth / Maturity / Decline] +- **Confidence:** [High/Medium/Low] +- **Phase duration to date:** [Duration] +- **Estimated time to next phase transition:** [Duration] + +### Supporting Evidence +| Indicator | Value | Trend | Phase Signal | +|-----------|-------|-------|-------------| +| Sales growth rate | [X%] | [Accelerating/Stable/Decelerating] | [Which phase this indicates] | +| Competitive entries/exits | [N entering / N exiting] | [Net entry/exit] | [Which phase this indicates] | +| Customer acquisition cost | [$X] | [Rising/Stable/Falling] | [Which phase this indicates] | +| Gross margin | [X%] | [Expanding/Stable/Compressing] | [Which phase this indicates] | +| Market awareness/adoption | [X%] | [Growing/Saturating] | [Which phase this indicates] | + +### Phase-Appropriate Strategy +| Dimension | Current Approach | Recommended Approach | Gap | +|-----------|-----------------|---------------------|-----| +| Pricing | [Current] | [Recommended for this phase] | [Change needed] | +| Marketing focus | [Current] | [Recommended for this phase] | [Change needed] | +| Product investment | [Current] | [Recommended for this phase] | [Change needed] | +| Distribution | [Current] | [Recommended for this phase] | [Change needed] | +| Competitive response | [Current] | [Recommended for this phase] | [Change needed] | + +### Transition Readiness +- Next phase: [Phase] +- Early warning signals to monitor: [List 3-5 indicators] +- Strategic preparations required: [List key changes] +- Investment implications: [Budget/resource shifts] + +### Extension Opportunities (if Maturity/Decline) +| Strategy | Description | Investment | Success Probability | Timeline | +|----------|-------------|------------|--------------------|---------| +| Product modification | [Change] | [$X] | [H/M/L] | [Duration] | +| Market modification | [Change] | [$X] | [H/M/L] | [Duration] | +| Marketing mix modification | [Change] | [$X] | [H/M/L] | [Duration] | +``` + +--- + +## Related Skills + +- **[Growth Share Matrix](growth-share-matrix.md)** -- The PLC and BCG matrix are complementary lenses on the same reality; products move through BCG quadrants as they progress through PLC phases. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Disruption often compresses or terminates the PLC of incumbent products; understanding disruption dynamics helps predict when decline will arrive faster than the natural curve suggests. +- **[Four Ps of Marketing](four-ps-marketing.md)** -- Each PLC phase demands a different marketing mix; introduction favors awareness and skimming pricing, while maturity demands retention-focused promotion and competitive pricing. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Maturity-phase strategy demands operational excellence; Kaizen and BPR provide the methodology for achieving the efficiency that maturity requires. +- **[Scenario Planning](scenario-planning.md)** -- Projecting when a product will transition between lifecycle phases is inherently uncertain; scenario planning stress-tests strategy against multiple phase-transition timelines. +- **[Net Promoter Score](net-promoter-score.md)** -- NPS trends serve as leading indicators of lifecycle phase transitions; declining NPS among core segments often signals the shift from growth to maturity before revenue data confirms it. diff --git a/plugins/foreman/content/skills/frameworks/psychological-safety.md b/plugins/foreman/content/skills/frameworks/psychological-safety.md new file mode 100644 index 0000000..f862661 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/psychological-safety.md @@ -0,0 +1,204 @@ +--- +name: "psychological-safety" +description: "Assesses and builds team psychological safety using Edmondson's framework and Clark's four developmental stages: inclusion, learner, contributor, and challenger safety. Identifies leadership behaviours that build or erode the shared belief that interpersonal risk-taking is safe. Use when team members withhold concerns, meetings lack candour, post-mortems reveal foreseeable failures that went unreported, or founders need to diagnose why innovation has narrowed." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - team-performance + - culture + - trust + - innovation + - leadership +related_skills: + - emotional-intelligence + - growth-mindset + - johari-window + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +# Psychological Safety + +When Google set out to discover what made its best teams effective, the company expected to find that optimal team composition -- the right mix of skills, seniority, and personality types -- was the primary driver. Project Aristotle, as the two-year internal research initiative was named, analysed 180 Google teams and found something different. Who was on the team mattered far less than how the team worked together. The single most important factor distinguishing high-performing teams from the rest was psychological safety: the shared belief among team members that the team is safe for interpersonal risk-taking. Not trust in the abstract, but the specific, felt confidence that speaking up with a question, concern, mistake, or half-formed idea will not result in punishment or humiliation. Amy Edmondson, the Harvard Business School professor who originated the concept, had been studying it for over a decade before Google's data confirmed its primacy. The finding carries particular weight for startups, where the margin for error is thin, the information environment is ambiguous, and the consequences of silence -- unvoiced concerns, unraised objections, unreported failures -- can be existential. + +--- + +## The Framework + +### What Psychological Safety Is (and Is Not) + +Edmondson is precise about the boundaries of the concept. Psychological safety is not: + +- **Niceness.** Teams with high psychological safety can have fierce debates. The difference is that the fierceness targets ideas, not people. +- **Lower standards.** Psychological safety does not mean reducing accountability. It means creating conditions where people can be honest about problems, which is a prerequisite for genuine accountability. +- **Unconditional agreement.** The point is not that everyone feels comfortable all the time. The point is that discomfort comes from intellectual challenge, not from fear of retaliation. + +Psychological safety is the group-level belief that candour will not be punished. It exists on a spectrum, and it is remarkably fragile -- a single incident of public humiliation can destroy months of trust-building. + +### The Four Stages of Psychological Safety + +Timothy Clark, building on Edmondson's work, proposed a developmental model: + +1. **Inclusion safety** -- Members feel accepted and that they belong. The baseline: "I am welcome here." +2. **Learner safety** -- Members feel safe to ask questions, experiment, and make mistakes in the process of learning. "I can be a beginner without being diminished." +3. **Contributor safety** -- Members feel safe to apply their skills and contribute meaningfully. "My input is valued and sought." +4. **Challenger safety** -- Members feel safe to challenge the status quo, question decisions, and push back on authority. "I can disagree with leadership without career risk." + +Most organisations achieve inclusion and learner safety reasonably well. Contributor safety is common in healthy cultures. Challenger safety -- the stage that produces the highest-value outcomes -- is rare. It is also the stage that matters most for startups, where the founder's conviction can create a reality distortion field that discourages dissent precisely when dissent is most needed. + +### Edmondson's Leader Toolkit + +Edmondson identifies specific leadership behaviours that build (and erode) psychological safety: + +**Behaviours that build:** +- Framing work as a learning problem, not an execution problem +- Acknowledging own fallibility ("I may miss something; I need your input") +- Modelling curiosity by asking genuine questions +- Responding to bad news with inquiry, not blame +- Acknowledging and thanking people who raise concerns +- Setting explicit norms about how failure is discussed + +**Behaviours that erode:** +- Punishing the messenger (even subtly -- a sigh, an eye-roll, a dismissive "We've already considered that") +- Making decisions in advance and using meetings to ratify rather than deliberate +- Publicly identifying individuals as responsible for failures +- Responding to mistakes with "Who did this?" rather than "What can we learn?" +- Praising only success and ignoring the learning embedded in failure + +### Measuring Psychological Safety + +Edmondson developed a seven-item survey instrument that remains the standard diagnostic: + +1. If you make a mistake on this team, it is often held against you. (Reverse scored) +2. Members of this team are able to bring up problems and tough issues. +3. People on this team sometimes reject others for being different. (Reverse scored) +4. It is safe to take a risk on this team. +5. It is difficult to ask other members of this team for help. (Reverse scored) +6. No one on this team would deliberately act in a way that undermines my efforts. +7. Working with members of this team, my unique skills and talents are valued and utilised. + +--- + +## Prompts + +**Prompt 1 -- Psychological Safety Diagnostic:** +> Based on the following observations about my team's behaviour, assess our likely level of psychological safety across Clark's four stages (inclusion, learner, contributor, challenger). Observations: [describe how team members behave in meetings, how bad news is delivered, how disagreements unfold, how mistakes are handled, whether junior members speak up]. For each stage, rate us as weak/developing/strong and provide the specific evidence from my observations that supports the rating. + +**Prompt 2 -- Incident Recovery Plan:** +> An incident just occurred that may have damaged psychological safety on my team: [describe what happened -- e.g., a team member was publicly criticised, a mistake led to visible blame, someone's idea was dismissed harshly]. Design a recovery plan: (a) immediate actions within 24 hours, (b) what I should say to the affected individual privately, (c) how to address the team without making it worse, and (d) systemic changes to prevent recurrence. Script the specific language for each conversation. + +**Prompt 3 -- Meeting Redesign for Candour:** +> Our team meetings currently suffer from [describe symptoms: silence from junior members, ideas only coming from senior people, no pushback on proposals, "agree in the room and disagree in the corridor" pattern]. Redesign our weekly team meeting format to maximise psychological safety and genuine candour. Include specific structural elements (e.g., anonymous input mechanisms, round-robin formats, pre-meeting reflection), facilitation techniques, and ground rules. Tailor the design for a team of [size] at [stage]. + +**Prompt 4 -- Founder Self-Assessment:** +> Evaluate my leadership behaviours for their impact on psychological safety. Here is how I typically respond to: (a) bad news: [describe], (b) disagreement: [describe], (c) mistakes: [describe], (d) questions that challenge my assumptions: [describe], (e) silence in meetings: [describe]. Rate each response on Edmondson's scale and recommend specific behavioural changes. Be direct -- this is precisely the kind of candid assessment I am trying to model for my team. + +--- + +## Use Cases + +**Early-traction startup where the founder is the bottleneck** + +A 12-person startup has a technically brilliant founder who inadvertently suppresses psychological safety through a specific behavioural pattern: she asks probing questions about every proposal, and her questioning -- while intellectually rigorous -- is experienced by the team as interrogation. The result: team members pre-filter ideas, only bringing forward those they believe will survive the founder's scrutiny. Innovation narrows to a single funnel. The diagnostic reveals strong inclusion and learner safety but weak contributor and challenger safety. The intervention is surgical: the founder learns to separate inquiry from evaluation by prefacing questions with "I'm asking because I want to understand, not because I'm challenging." She also implements a practice of sharing her own half-formed ideas first, modelling that incomplete thinking is legitimate. Within three months, the team's proposal pipeline triples. + +**Scale-stage company with a "no bad news" culture** + +A 500-person company discovers during a post-mortem that a critical product failure was foreseeable -- three engineers had identified the risk weeks earlier but chose not to escalate. Investigation reveals a cultural pattern: the company celebrates "can-do" attitudes and implicitly penalises those who raise obstacles. Middle managers filter bad news before it reaches leadership because they have learned that bearing bad news harms their standing. The CEO implements Edmondson's framework at the organisational level: establishing anonymous escalation channels, publicly praising employees who surface problems early, and creating a "risk radar" ritual in leadership meetings where the explicit purpose is to identify what could go wrong. The transformation takes 12-18 months but produces a measurable reduction in preventable failures. + +**Growth-stage remote team struggling with asynchronous candour** + +A fully distributed startup finds that psychological safety is easier in synchronous video calls (where tone and expression provide context) but deteriorates in asynchronous written communication (Slack, email), where messages are more likely to be interpreted as blunt, dismissive, or critical. The company develops explicit norms for asynchronous communication: a "draft and re-read" protocol for sensitive messages, an explicit emoji-free notation system for tone (e.g., prefixing messages with "[genuine question]" or "[thinking out loud]"), and weekly synchronous sessions dedicated to relationship maintenance rather than task execution. + +--- + +## Anti-Patterns + +**1. Declaring psychological safety without building it.** Announcing "this is a safe space" in a meeting does nothing -- and may actively harm safety if team members' lived experience contradicts the declaration. Psychological safety is demonstrated through consistent behaviour over time, not proclaimed in a single statement. + +**2. Confusing psychological safety with conflict avoidance.** Teams with genuine psychological safety have more productive conflict, not less. If introducing the concept leads to people being even more reluctant to disagree ("we need to be safe with each other"), the implementation has failed. The goal is to make disagreement safer, not to eliminate it. + +**3. Expecting immediate results after a single intervention.** Psychological safety is built through hundreds of micro-interactions over months. A single well-intentioned meeting or workshop does not undo years of punitive culture. Leaders who expect instant transformation become disillusioned and abandon the effort, which confirms the team's suspicion that the initiative was performative. + +**4. Holding everyone accountable for safety except the founder/CEO.** Psychological safety is set at the top. If the most senior person in the room does not model vulnerability, curiosity, and openness to challenge, no amount of team-level work will compensate. The single highest-leverage action is the founder's behaviour, not the team's training. + +**5. Using psychological safety surveys without acting on results.** Conducting Edmondson's diagnostic and then failing to address the findings it surfaces is worse than never conducting it. The survey itself raises expectations of change; unmet expectations erode trust further. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founding team dynamics, first hires | Safety is personal and direct; the founder's daily behaviour IS the safety level | +| Growth | Middle management layer, remote/hybrid dynamics | Safety must scale through delegation; managers become the primary safety-setters for their teams | +| Scale | Organisational culture, cross-functional dynamics | Safety becomes a systems problem requiring structural solutions (anonymous channels, formal feedback mechanisms, cultural metrics) | + +At early traction, psychological safety is entirely personal. In a five-person team, every interaction between the founder and each team member directly builds or erodes safety. The founder who responds to a junior developer's bug report with gratitude ("Thank you for catching this early") versus irritation ("How did this get through?") sets the entire team's willingness to surface problems. + +At growth, the founder cannot personally maintain safety across 50 or 100 people. The critical transition is equipping managers to be safety-builders. This requires explicit training (most first-time managers have never thought about psychological safety), modelling from above (managers will treat their teams the way leadership treats them), and measurement (including safety in manager evaluations). + +At scale, psychological safety becomes an architectural challenge. Cross-functional teams, distributed workforces, matrix organisations, and acquired companies all present structural obstacles to interpersonal trust. The solutions become correspondingly structural: anonymous escalation systems, ombudsperson roles, cultural health metrics in leadership dashboards, and deliberate investment in the kind of relational infrastructure that small teams get for free. + +--- + +## Output Template + +```markdown +# Psychological Safety Assessment -- [Team Name] + +**Prepared for:** Team Lead / Founder +**Date:** [Date] +**Team size:** [N] +**Assessment method:** [Observation / Survey / Interviews] + +## Four-Stage Assessment + +| Stage | Rating | Evidence | Priority Action | +|-------|--------|----------|----------------| +| Inclusion Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Learner Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Contributor Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Challenger Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | + +## Behavioural Patterns Observed + +| Behaviour | Frequency | Impact on Safety | Classification | +|-----------|-----------|-----------------|----------------| +| [Specific behaviour] | [Often/Sometimes/Rarely] | [Builds/Erodes] | [Which stage affected] | + +## Leader Behaviour Audit + +| Edmondson Behaviour | Current Practice | Recommendation | +|--------------------|-----------------|----------------| +| Framing as learning problem | [Current] | [Change needed] | +| Acknowledging fallibility | [Current] | [Change needed] | +| Modelling curiosity | [Current] | [Change needed] | +| Responding to bad news | [Current] | [Change needed] | +| Thanking those who raise concerns | [Current] | [Change needed] | + +## 90-Day Safety Building Plan +**Month 1:** [Foundation -- specific rituals and norms to establish] +**Month 2:** [Practice -- specific behaviours to reinforce and measure] +**Month 3:** [Assessment -- re-measure and adjust] + +## Risk Indicators to Monitor +- [Signal that safety is declining -- e.g., decreased questions in meetings] +- [Signal that safety is declining -- e.g., increased corridor conversations] +- [Signal that safety is improving -- e.g., mistakes reported earlier] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](emotional-intelligence.md)** -- Goleman's empathy and self-regulation domains are the individual competencies that leaders must develop to create psychologically safe environments. +- **[Growth Mindset](growth-mindset.md)** -- Dweck's framework is the mindset complement to Edmondson's structural model; psychological safety is the environment in which growth mindset can operate, and growth mindset is the orientation that makes psychological safety productive. +- **[Radical Candor](radical-candor.md)** -- Radical Candor depends on psychological safety as its foundation; without the shared belief that candor will not be punished, direct challenge registers as threat rather than care. +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- Pre-mortems and bias audits, which are System 2 tools, require psychological safety to function; people will not voice dissenting analysis in an unsafe environment. +- **[Psychological Safety Practice](../leadership/psychological-safety-practice.md)** -- Translates Edmondson's academic framework into daily leadership behaviors and team rituals that build and sustain safety over time. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Psychological safety determines whether failures become learning opportunities or career-ending events; the two frameworks are mutually reinforcing. diff --git a/plugins/foreman/content/skills/frameworks/radical-candor.md b/plugins/foreman/content/skills/frameworks/radical-candor.md new file mode 100644 index 0000000..9b4dc2e --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/radical-candor.md @@ -0,0 +1,195 @@ +--- +name: "radical-candor" +description: "Applies Kim Scott's Radical Candor framework to improve feedback culture by balancing caring personally with challenging directly. Maps management behaviour across four quadrants: Radical Candor, Ruinous Empathy, Obnoxious Aggression, and Manipulative Insincerity. Use when preparing difficult performance conversations, diagnosing a culture of avoidance, training new managers on feedback, or addressing top-performer attrition caused by insufficient challenge." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - feedback + - management + - communication + - leadership + - culture +related_skills: + - giving-feedback + - trust-equation + - organisational-culture + - lean-in +author: "Fatih Guner" +--- + +# Radical Candor + +When Kim Scott joined Google and later became a director at Apple, she thought she was a good manager. Then Sheryl Sandberg pulled her aside after a presentation. "You said 'um' a lot," Sandberg told her. Scott brushed it off -- she had nailed the content, after all. Sandberg pressed: "I can see I'm going to have to be more direct with you. When you say 'um' every third word, it makes you sound stupid." Scott was stunned. And then she was grateful. No one had ever cared enough to be that blunt. She had given hundreds of presentations with that verbal tic, and every previous manager had been too "nice" to mention it. Sandberg's willingness to combine genuine personal concern with unfiltered directness became the seed of what Scott later formalised as Radical Candor -- a framework that has since reshaped how a generation of managers thinks about the relationship between kindness and honesty. + +The insight is deceptively simple: most management failures are failures of feedback, and most feedback failures stem from a false choice between being caring and being honest. Radical Candor rejects the choice entirely. + +--- + +## The Framework + +### The 2x2 Matrix + +Radical Candor maps management behaviour along two dimensions: + +- **Care Personally** (vertical axis): The degree to which you give a damn about the person as a human being -- not just as a producer of output. This is not about being friends; it is about acknowledging that work is performed by people with lives, fears, ambitions, and dignity. +- **Challenge Directly** (horizontal axis): The degree to which you tell people what you actually think -- especially when your assessment is unfavourable. Direct challenge means sharing your honest perspective, not softening it into meaninglessness. + +``` + HIGH CARE PERSONALLY + | + Ruinous | Radical + Empathy | Candor + "Too nice | "I care about you + to be honest" | AND I'll tell you + | the truth" + | + LOW ────────────────┼──────────────── HIGH + CHALLENGE | CHALLENGE + DIRECTLY | DIRECTLY + | + Manipulative | Obnoxious + Insincerity | Aggression + "Neither honest | "Brutal honesty + nor caring" | without caring" + | + LOW CARE PERSONALLY +``` + +### Quadrant 1: Radical Candor (High Care, High Challenge) + +The target quadrant. You care about the person enough to risk their temporary discomfort for their long-term growth. You challenge them directly because you respect them enough to be honest. Radical Candor is not a permanent state -- it is a direction you move toward, a practice you calibrate daily. + +**Characteristics:** +- Feedback is immediate, specific, and delivered privately for criticism, publicly for praise +- The manager solicits feedback on their own performance first, modelling vulnerability +- Criticism targets behaviour, not character +- The relationship carries enough trust that directness is received as investment, not attack + +### Quadrant 2: Ruinous Empathy (High Care, Low Challenge) + +The most common failure mode, particularly among well-intentioned managers. You care about the person -- genuinely -- but you avoid telling them hard truths because you do not want to hurt their feelings. The result: problems compound, performance declines, and when the inevitable reckoning arrives (a PIP, a firing), the employee is blindsided. "Why didn't anyone tell me?" is the epitaph of Ruinous Empathy. + +Scott estimates that roughly 85% of management mistakes fall into this quadrant. The damage is severe precisely because the intention is benign. + +### Quadrant 3: Obnoxious Aggression (Low Care, High Challenge) + +The stereotypical "tough boss." Brutally honest, but the honesty serves the manager's ego rather than the employee's development. Feedback is delivered without concern for how it lands, often publicly, sometimes cruelly. The saving grace of this quadrant -- compared to the others -- is that at least people know where they stand. Scott argues that Obnoxious Aggression, while unpleasant, is less destructive than Ruinous Empathy because the information still flows. + +### Quadrant 4: Manipulative Insincerity (Low Care, Low Challenge) + +The worst quadrant. Neither honest nor caring. Manifests as political manoeuvring, passive-aggression, insincere praise, and backstabbing. People in this quadrant tell you what you want to hear to your face and something entirely different behind your back. Organisations dominated by this quadrant are characterised by dysfunction, mistrust, and talent flight. + +### The Order of Operations + +Scott prescribes a specific sequence for building Radical Candor into your practice: + +1. **Solicit criticism before giving it.** Ask your team to tell you what you are doing wrong. Listen without defending. Thank them. Act on what you hear. This builds the trust that makes your subsequent criticism receivable. +2. **Praise specifically and sincerely.** Not "great job" but "the way you restructured the data pipeline reduced our processing time by 40%, and the documentation you wrote means anyone can maintain it." Specific praise demonstrates that you pay attention. +3. **Criticise kindly, clearly, and immediately.** Do not save feedback for quarterly reviews. Deliver it within hours, not weeks. Be specific about the behaviour. Explain the impact. Offer to help. + +--- + +## Prompts + +**Prompt 1 -- Quadrant Self-Assessment:** +> Analyse my recent management behaviour using the Radical Candor framework. Here are five recent feedback interactions I have had with my team: [describe each briefly -- what the situation was, what you said, how you said it, what happened]. For each, identify which quadrant I was operating in and why. Then identify my default quadrant and provide a specific plan for moving toward Radical Candor. + +**Prompt 2 -- Difficult Conversation Design:** +> I need to give critical feedback to [describe the person and their role]. The issue is [describe the performance or behaviour problem]. I care about this person's growth and want to maintain the relationship, but I have been avoiding this conversation. Using the Radical Candor framework, help me prepare: What should I say? How should I open? What specific behaviour should I name? How do I convey both challenge and care simultaneously? Script the key moments of this conversation. + +**Prompt 3 -- Culture Installation:** +> I want to build a Radical Candor culture across my company of [size] people. Currently, our culture defaults to [describe -- e.g., Ruinous Empathy, political, conflict-avoidant]. Design a 90-day programme to shift toward Radical Candor, including: leadership behaviour changes, team rituals, feedback mechanisms, and training elements. Specify how to handle resistance and how to measure progress. + +--- + +## Use Cases + +**Early-Traction Startup with a Underperforming Cofounder** +A technical cofounder is brilliant at architecture but consistently misses sprint commitments, demoralising the small engineering team. The CEO (the other cofounder) has been operating in Ruinous Empathy -- praising the technical vision while quietly picking up the slack. Applying Radical Candor, the CEO schedules a one-on-one and opens by soliciting criticism of their own leadership first. Then, clearly and specifically: "In the last three sprints, you committed to X and delivered Y. The team sees this, and it's eroding their trust. I'm telling you because I believe in your ability to fix it, and because the alternative -- letting this slide -- ends with us losing the team." The conversation produces a concrete plan with weekly check-ins. + +**Growth-Stage Company with a "Nice" Culture That Cannot Retain Top Performers** +A 90-person company with a warm, supportive culture consistently loses its highest performers within 12-18 months. Exit interviews reveal a pattern: top performers feel under-challenged and under-recognised. The culture's dominant quadrant is Ruinous Empathy -- everyone is pleasant, but hard truths never surface. The CEO introduces Radical Candor through a three-phase approach: first, publicly soliciting criticism of their own leadership at an all-hands; second, training all managers on the 2x2 matrix with role-play exercises; third, implementing weekly "candor check-ins" where each team member shares one piece of critical feedback and one piece of specific praise. + +**Scale-Stage Company Dealing with an Obnoxiously Aggressive VP** +A VP of Engineering at a 300-person company delivers results but leaves a trail of demoralised engineers. Turnover in their division is three times the company average. The VP believes they practice Radical Candor ("I tell people the truth"). Applying the framework precisely, HR and the CEO demonstrate that the VP's behaviour maps to Obnoxious Aggression: high challenge, low care. The intervention is not to soften the VP's directness but to develop the "Care Personally" dimension -- through executive coaching focused on curiosity, empathy, and understanding each report's career aspirations before delivering criticism. + +--- + +## Anti-Patterns + +1. **Using Radical Candor as a License for Cruelty.** The most dangerous misapplication: "I'm just being radically candid" deployed to excuse harsh, ego-driven, or poorly timed feedback. If the other person does not experience your criticism as caring, you are not practicing Radical Candor regardless of your intention. Impact trumps intent. + +2. **Skipping the "Solicit Criticism First" Step.** Leaders who jump straight to giving critical feedback without first demonstrating vulnerability by asking for criticism of themselves. The sequence matters. Trust must precede challenge. + +3. **Calibrating Only Once.** What feels like Radical Candor to one person may feel like Obnoxious Aggression to another. Cultural background, personality, seniority, and relationship history all affect how directness is received. The framework requires constant recalibration per person, not a single universal setting. + +4. **Praising Only in Private.** Scott's framework specifies that praise should be public (to reinforce desired behaviour visibly) and criticism should be private (to preserve dignity). Reversing this -- praising privately and criticising publicly -- is a recipe for fear-based culture. + +5. **Treating the 2x2 as a Personality Test.** Radical Candor describes behaviour, not people. Everyone moves between quadrants situationally. The goal is to spend more time in Radical Candor and less time in the other three -- not to label individuals as permanently occupying one quadrant. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Cofounder feedback norms | At the founding stage, the Radical Candor relationship between cofounders sets the template for the entire company's feedback culture. Establishing this early prevents the accumulation of unspoken resentments that fracture founding teams. | +| Growth | Manager training | As the company adds management layers, each new manager must learn the framework. The founder can no longer model candor to every individual; they must model it to managers who then model it to their teams. | +| Scale | Institutional mechanisms | At scale, Radical Candor cannot depend on individual managers' skill. It requires institutional supports: structured feedback processes, peer-review systems, 360-degree reviews designed around the framework, and explicit cultural reinforcement. | + +--- + +## Output Template + +```markdown +# Radical Candor Assessment: [Team/Company Name] + +## Dominant Quadrant Analysis +- **Leadership team default:** [Quadrant] +- **Middle management default:** [Quadrant] +- **IC-level default:** [Quadrant] +- **Evidence:** [Specific behavioural patterns observed] + +## Feedback Flow Audit +| Direction | Current State | Desired State | +|-----------|---------------|---------------| +| Leader → Team | [Description] | Radical Candor | +| Team → Leader | [Description] | Radical Candor | +| Peer → Peer | [Description] | Radical Candor | + +## Intervention Plan +### Phase 1: Model (Weeks 1-4) +- [Leader actions to solicit criticism and demonstrate vulnerability] + +### Phase 2: Train (Weeks 5-8) +- [Manager training, role-play, framework introduction] + +### Phase 3: Sustain (Weeks 9-12) +- [Rituals, processes, accountability mechanisms] + +## Key Conversations Needed +| Person | Issue | Quadrant Risk | Approach Notes | +|--------|-------|---------------|----------------| +| [Name] | [Issue] | [Likely pitfall] | [How to stay in Radical Candor] | + +## Metrics +- Employee engagement survey: feedback culture questions +- Retention rates, especially top performers +- Manager feedback quality scores (360 reviews) +``` + +--- + +## Related Skills + +- **[Giving Feedback (SBI Model)](giving-feedback.md)** -- SBI provides the tactical "how" of delivering feedback; Radical Candor provides the strategic "why" and the relational context. +- **[Trust Equation](trust-equation.md)** -- Trust is the precondition for Radical Candor; without sufficient trust, directness registers as threat rather than investment. +- **[Organisational Culture](organisational-culture.md)** -- Feedback norms are a Layer 2 value sustained by Layer 3 assumptions; Radical Candor only takes root in cultures whose basic assumptions support psychological safety. +- **[Psychological Safety](psychological-safety.md)** -- Edmondson's challenger safety is the organizational condition that enables Radical Candor to function; without it, direct challenge triggers defensive reactions rather than growth. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- Moving from Ruinous Empathy to Radical Candor requires the emotional courage to sit with discomfort and deliver difficult truths despite the natural urge to avoid conflict. +- **[Writing Performance Reviews](../writing/writing-performance-reviews.md)** -- Performance reviews are the formal venue where Radical Candor principles must be applied with precision; vague written feedback is the documentary equivalent of Ruinous Empathy. diff --git a/plugins/foreman/content/skills/frameworks/scenario-planning.md b/plugins/foreman/content/skills/frameworks/scenario-planning.md new file mode 100644 index 0000000..c0ad5e6 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/scenario-planning.md @@ -0,0 +1,201 @@ +--- +name: "scenario-planning" +description: "Constructs multiple plausible future scenarios using a 2x2 matrix + of critical uncertainties, then stress-tests strategy against each scenario to + develop robust responses. Identifies no-regret moves, hedging actions, and + strategic options. Use when facing major capital allocation decisions, + evaluating market expansion under regulatory uncertainty, preparing for + technology disruption, or building enterprise risk management into strategic + planning cycles." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - strategy + - uncertainty + - planning + - futures + - decision-making +related_skills: + - black-swans + - porters-five-forces + - swot-pest-analysis + - blue-ocean-strategy +author: "Fatih Guner" +--- + +# Scenario Planning + +When the Arab oil embargo struck in October 1973, most Western corporations were blindsided. Royal Dutch Shell was not. Through a practice called scenario planning -- pioneered within the company by Pierre Wack and his team in the Group Planning division -- Shell had already rehearsed a world in which oil prices spiked dramatically. While competitors scrambled to react, Shell had contingency plans ready to execute. Within two years, Shell rose from the seventh-largest oil company to the second. The story is not merely corporate lore; it remains the canonical demonstration that rehearsing multiple futures is more valuable than perfecting a single forecast. + +Scenario planning does not attempt to predict the future. It attempts to prepare for several plausible futures simultaneously, so that when events unfold -- inevitably in ways that match no single prediction -- the organization can respond with speed and coherence rather than confusion. + +--- + +## The Framework + +### The Logic of Scenarios + +Traditional strategic planning assumes a single most-likely future and builds one plan around it. Scenario planning rejects this premise. It constructs multiple internally consistent narratives about how the future might develop, then uses these narratives to stress-test strategy and develop flexible responses. + +The distinction is not academic. A single-forecast plan is brittle; it works brilliantly if the forecast is correct and fails entirely if it is not. A scenario-informed strategy bends without breaking. + +### The Process + +Scenario planning follows a disciplined sequence, though practitioners adapt the steps to their context: + +**Step 1 -- Define the Focal Question** +What specific strategic decision or uncertainty does the organization need to navigate? The question must be concrete. "What will our industry look like in ten years?" is too broad. "Should we invest $20M in a new manufacturing facility given regulatory and demand uncertainty?" is actionable. + +**Step 2 -- Identify Driving Forces** +Map the external forces that will shape outcomes: technological trends, regulatory trajectories, demographic shifts, competitor behavior, macroeconomic conditions. Distinguish between predetermined elements (forces largely certain to continue, such as demographic aging) and critical uncertainties (forces whose direction is genuinely unknown, such as regulatory posture toward AI). + +**Step 3 -- Select Scenario Axes** +Choose two critical uncertainties as the axes of a 2x2 matrix. Each axis represents a spectrum (e.g., "regulation: permissive to restrictive" and "demand: growing to contracting"). The four quadrants define four distinct scenario worlds. + +**Step 4 -- Build Scenario Narratives** +For each quadrant, construct a plausible story. Give it a memorable name. Describe how this world develops over the planning horizon: what happens, why, and what it means for the industry. The narratives must be internally consistent and genuinely different from one another. + +**Step 5 -- Identify Implications and Signposts** +For each scenario, determine: What would our current strategy deliver in this world? What capabilities would we need? What early indicators ("signposts") would tell us this scenario is materializing? + +**Step 6 -- Develop Robust Strategies** +Design strategies that perform acceptably across multiple scenarios rather than optimally in just one. Identify "no regret" moves (beneficial in all scenarios), hedging actions (insurance against specific scenarios), and options to preserve (flexibility that becomes valuable if certain scenarios materialize). + +### The 2x2 Scenario Matrix + +``` + Uncertainty A: High + | + Scenario 2 | Scenario 1 + "Name" | "Name" + | + Uncertainty B: ---------|--------- Uncertainty B: + Low | High + | + Scenario 3 | Scenario 4 + "Name" | "Name" + | + Uncertainty A: Low +``` + +### What Makes Good Scenarios + +Good scenarios are not optimistic, pessimistic, and middle-ground. They are qualitatively different worlds. Each should challenge assumptions in a different way. Shell's Wack insisted that scenarios must "change the mental maps of decision-makers" -- if they merely confirm existing beliefs, they have failed. + +--- + +## Prompts + +**Prompt 1 -- Scenario Matrix Construction:** +> I need to make a strategic decision about [describe the decision]. My company is [describe: sector, stage, size]. Help me build a scenario planning matrix. First, identify the 5-7 most important driving forces affecting this decision. Then select the two most critical uncertainties as axes. Construct four distinct scenarios with vivid names and 2-3 paragraph narratives for each. Finally, identify 2-3 early signposts for each scenario that would indicate it is beginning to materialize. + +**Prompt 2 -- Strategy Stress-Test:** +> Here is my current strategic plan: [describe plan]. Here are four scenarios I have developed: [list or describe scenarios]. Stress-test my plan against each scenario. For each one, assess: (1) How would our plan perform in this world? (2) What are the biggest vulnerabilities? (3) What adaptations would be required? Summarize the results in a table showing plan performance across all four scenarios. + +**Prompt 3 -- Robust Strategy Design:** +> Based on these four scenarios [describe or list them] and this strategy stress-test [paste or describe results], help me redesign my strategy for robustness. Categorize potential actions into three buckets: "No Regret" moves (valuable in all scenarios), "Hedging" moves (insurance against specific scenarios), and "Options" (investments in flexibility). For each action, estimate the cost and the scenarios in which it pays off. + +**Prompt 4 -- Signpost Monitoring Dashboard:** +> I have developed four scenarios for my business: [list scenarios with brief descriptions]. For each scenario, I identified these signposts: [list signposts]. Help me design a monitoring dashboard. What data sources should I track for each signpost? What thresholds or triggers should prompt strategic review? How frequently should each signpost be assessed? Format as a monitoring plan I can share with my leadership team. + +--- + +## Use Cases + +**Early-Traction EdTech Company Deciding on Market Expansion** +A B2B edtech startup with $2M ARR must decide whether to expand into the European market. The two critical uncertainties are regulatory environment (GDPR enforcement intensity ranging from lenient to aggressive) and buyer behavior (districts centralizing procurement vs. remaining fragmented). The four resulting scenarios produce radically different go-to-market strategies. The "no regret" move: build GDPR-compliant architecture regardless, since it strengthens the product everywhere. The hedging move: partner with a European distributor rather than establishing a subsidiary, preserving the option to scale up or retreat without heavy sunk costs. + +**Growth-Stage Fintech Evaluating Technology Bets** +A Series B fintech company must allocate engineering resources between improving its existing platform and building for a potential blockchain-based settlement infrastructure. Scenario planning surfaces two key uncertainties: speed of institutional blockchain adoption and regulatory stance toward decentralized finance. The scenario matrix reveals that in three of four worlds, the existing platform dominates near-term revenue. In one scenario, blockchain infrastructure becomes table stakes within five years. The robust strategy: invest 80% in platform improvement while maintaining a small, skilled team exploring blockchain integration -- an explicit option on the future rather than a binary bet. + +--- + +## Anti-Patterns + +1. **Building scenarios around optimistic/pessimistic/baseline.** This is the single most common error. Scenarios that differ only in degree ("things go well / okay / badly") are not scenarios at all -- they are sensitivities. Genuine scenarios differ in kind. The world where AI regulation is restrictive and enterprise adoption is slow is qualitatively different from the world where regulation is permissive and consumer adoption leads. + +2. **Treating scenario planning as a one-time exercise.** Organizations that build scenarios once, file them, and never revisit have wasted their effort. Scenarios gain value through ongoing use: monitoring signposts, updating narratives as new information arrives, and stress-testing each major decision against the established scenarios. + +3. **Selecting trivially certain or trivially unlikely axes.** If one axis is "will customers still want our product?" and the answer is obviously yes, the resulting scenarios will not challenge assumptions. Axes must represent genuine, consequential uncertainties where reasonable people could disagree about the outcome. + +4. **Using scenarios to justify a predetermined decision.** Some leaders commission scenario planning specifically to produce the narrative that supports the investment they already want to make. This transforms a strategic tool into a political one and discredits the entire exercise. + +5. **Overcomplicating with too many scenarios.** Four scenarios (from a 2x2 matrix) are the standard for good reason. More than four becomes cognitively unmanageable. If the team cannot remember and discuss all scenarios fluently, the framework loses its utility. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Assumption testing | At this stage, the entire business model is uncertain. Use lightweight scenario thinking to identify which assumptions, if wrong, would invalidate the venture. Two or three informal scenarios suffice; a full 2x2 process may be premature. | +| Early Traction | Go-to-market decisions | The product works; the question is where and how to grow. Scenario planning helps evaluate market entry choices, partnership strategies, and pricing models under different competitive and regulatory conditions. | +| Growth | Capital allocation | Significant investment decisions benefit most from formal scenario planning. Should we build or buy? Expand domestically or internationally? Invest in new technology or optimize existing? These decisions are expensive to reverse, making scenario rehearsal essential. | +| Scale | Enterprise risk management | At scale, scenario planning becomes an institutional practice rather than an ad-hoc exercise. Integrate scenarios into annual strategic planning cycles, board-level risk discussions, and capital allocation committees. | + +--- + +## Output Template + +```markdown +# Scenario Planning Analysis + +**Focal Question:** [The specific strategic decision under consideration] +**Time Horizon:** [Planning period, e.g., 3-5 years] +**Date:** [Date] + +## Driving Forces +1. [Force] -- [Predetermined / Critical Uncertainty] +2. [Force] -- [Predetermined / Critical Uncertainty] +3. [Force] -- [Predetermined / Critical Uncertainty] + +## Scenario Matrix + +**Axis X:** [Critical Uncertainty 1 -- spectrum description] +**Axis Y:** [Critical Uncertainty 2 -- spectrum description] + +### Scenario A: "[Name]" (X-High, Y-High) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario B: "[Name]" (X-High, Y-Low) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario C: "[Name]" (X-Low, Y-High) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario D: "[Name]" (X-Low, Y-Low) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +## Strategy Stress-Test + +| Action | Scenario A | Scenario B | Scenario C | Scenario D | Classification | +|--------|-----------|-----------|-----------|-----------|----------------| +| [Action 1] | [Impact] | [Impact] | [Impact] | [Impact] | No Regret / Hedge / Option | +| [Action 2] | [Impact] | [Impact] | [Impact] | [Impact] | No Regret / Hedge / Option | + +## Recommended Actions +1. **No Regret:** [Actions valuable in all scenarios] +2. **Hedges:** [Actions that insure against specific scenarios] +3. **Options:** [Investments in flexibility] +``` + +--- + +## Related Skills + +- **[Black Swan Theory](black-swans.md)** -- Scenario planning addresses plausible futures; Black Swan thinking addresses the implausible ones, and together they provide comprehensive uncertainty management. +- **[Porter's Five Forces](porters-five-forces.md)** -- Industry structure analysis feeds directly into scenario construction by identifying the competitive forces most likely to shift. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- Internal strengths and weaknesses determine how the organization would perform under each scenario, making SWOT a natural complement. +- **[VUCA Framework](vuca-framework.md)** -- VUCA diagnoses the type of unpredictability; scenario planning is the primary strategic response when uncertainty is the dominant dimension. +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- Scenario planning is a structured System 2 exercise that counteracts the overconfidence and anchoring biases Kahneman identifies in single-forecast planning. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- Scenario planning provides the external foresight that strategic thinking translates into robust organizational direction and investment decisions. diff --git a/plugins/foreman/content/skills/frameworks/shamrock-organisation.md b/plugins/foreman/content/skills/frameworks/shamrock-organisation.md new file mode 100644 index 0000000..802da9d --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/shamrock-organisation.md @@ -0,0 +1,191 @@ +--- +name: "shamrock-organisation" +description: "Designs workforce architecture using Handy's Shamrock Organisation model with three leaves: professional core, contractual fringe, and flexible labour force. Evaluates which roles belong in each leaf to optimize cost structure, agility, and institutional knowledge. Use when planning first hires, deciding what to outsource, preparing for international expansion, auditing workforce composition, or reducing fixed costs while preserving strategic capability." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - organisational-design + - workforce-strategy + - outsourcing + - flexible-labour + - talent-management +related_skills: + - kaizen-bpr + - systems-thinking + - balanced-scorecard + - disruptive-innovation +author: "Fatih Guner" +--- + +# The Shamrock Organisation + +By 2030, the majority of the global workforce will not hold traditional full-time employment. This is not speculation -- it is the arithmetic consequence of trends already visible in labour statistics across every developed economy. Charles Handy saw it coming in 1989. His model of the Shamrock Organisation, articulated in *The Age of Unreason*, described a workforce structure built on three distinct leaves: a professional core, an outsourced contractual fringe, and a flexible labour force. What seemed provocative in the late twentieth century now reads as operational reality for any startup that has ever hired a freelance designer, contracted a development agency, or employed gig workers for delivery logistics. + +The framework matters for entrepreneurs not as theory but as architecture. How you compose your workforce determines your cost structure, your agility, your culture, and ultimately your capacity to scale. Get the shamrock wrong, and you either bloat with fixed costs or hollow out the capabilities that make your company distinctive. + +--- + +## The Framework + +### Leaf One: The Professional Core + +These are the indispensable people -- the ones who carry the organisation's institutional knowledge, strategic direction, and proprietary capability. They are expensive, difficult to replace, and worth every unit of compensation. + +**Characteristics:** +- Full-time, salaried, deeply embedded in company culture +- Possess knowledge that cannot be easily codified or transferred +- Their departure would create genuine strategic damage +- Compensated through salary, equity, career development, and purpose + +**The entrepreneur's question:** Which roles, if vacated tomorrow, would threaten the company's survival or competitive advantage? Those belong in the core. Everything else is a candidate for the other two leaves. + +In practice, the professional core should be smaller than most founders assume. The instinct to hire full-time for every function is a legacy of industrial-era thinking. Handy argued that the core should shrink to its essential minimum -- and that this minimum would keep shrinking as technology and markets evolve. + +### Leaf Two: The Contractual Fringe + +These are the specialists and service providers engaged through contracts -- agencies, consultancies, outsourced functions. The work is defined, bounded, and governed by deliverables rather than hours. + +**Characteristics:** +- Engaged for specific expertise or capacity that the core does not need permanently +- Managed through outcomes and service-level agreements, not supervision +- Replaceable through market competition (though switching costs vary) +- Paid for results, not presence + +**The entrepreneur's question:** Which functions require specialist expertise we cannot justify building in-house at our current scale? Legal, accounting, specialised engineering, marketing production, and logistics frequently land here. + +The contractual fringe is where startups gain leverage. A five-person company can access enterprise-grade legal counsel, world-class design, and sophisticated financial modelling without carrying the fixed cost. The discipline lies in managing the boundary: what stays contracted and what eventually migrates to the core as the company grows. + +### Leaf Three: The Flexible Labour Force + +These are part-time, temporary, seasonal, or gig workers. They provide elasticity -- the ability to scale capacity up and down without the structural cost of permanent headcount. + +**Characteristics:** +- Engaged by the hour, task, or season +- Minimal training investment; roles are standardised or semi-skilled +- High turnover is expected and managed through systems, not relationships +- Compensated primarily through wages; loyalty is transactional + +**The entrepreneur's question:** Which activities fluctuate in volume and can be performed by workers with limited company-specific knowledge? Customer support overflow, event staffing, warehouse operations, and data entry often fit. + +The ethical dimension deserves attention. Handy himself warned that the flexible leaf risks creating a precariat -- workers with no security, no development, and no stake in the company's success. Entrepreneurs who treat this leaf as disposable labour eventually pay a price in quality, reputation, and regulatory exposure. + +### The Shamrock in Balance + +The three leaves are interdependent. Overweight the core, and fixed costs crush you during downturns. Overweight the fringe, and you lose the institutional knowledge that drives differentiation. Overweight the flexible leaf, and quality deteriorates while your culture evaporates. + +``` + Professional Core + (Knowledge + Strategy) + / \ + / \ + Contractual Fringe Flexible Labour + (Expertise on Demand) (Elastic Capacity) +``` + +The optimal balance shifts with company stage, sector, and strategy. There is no universal ratio, but the diagnostic question remains constant: *Is each role in the leaf where it creates maximum value at minimum structural risk?* + +--- + +## Prompts + +**Prompt 1 -- Workforce Architecture Audit:** +> "Analyse my current team structure: [list roles, employment types, and functions]. Classify each role into one of the three Shamrock Organisation leaves (Professional Core, Contractual Fringe, Flexible Labour). For any role that appears misclassified, explain why and recommend the appropriate leaf, including the transition approach." + +**Prompt 2 -- Scaling Workforce Design:** +> "My company is at [stage] with [number] employees and plans to grow from [current revenue] to [target revenue] in [timeframe]. Using the Shamrock Organisation model, design a workforce architecture that specifies which functions should be core hires, which should be outsourced, and which should use flexible labour. Include the rationale for each classification and the cost implications." + +**Prompt 3 -- Core Identification Stress Test:** +> "For each role in my company [list roles], apply this test: If this person left tomorrow, would we lose (a) proprietary knowledge, (b) strategic capability, or (c) irreplaceable client relationships? Score each role on these three dimensions. Any role scoring low on all three is a candidate for migration to the contractual fringe or flexible leaf." + +**Prompt 4 -- Outsourcing Decision Matrix:** +> "Evaluate these business functions for outsourcing suitability: [list functions]. For each, assess: (1) strategic importance, (2) availability of quality external providers, (3) switching costs, (4) intellectual property risk, and (5) cost differential between in-house and outsourced delivery. Produce a ranked recommendation." + +--- + +## Use Cases + +**Early-Stage SaaS Startup Designing Its First Hires** + +A two-founder SaaS startup with $150K in pre-seed funding must decide where to deploy limited capital. Using the Shamrock model, they identify the professional core as the two founders (product and engineering) plus one critical hire: a senior developer who will own the core platform architecture. The contractual fringe includes a design agency for UI/UX, a fractional CFO for financial planning, and a legal firm for incorporation and IP protection. The flexible leaf covers a part-time customer support representative and a freelance content writer. Total team impact: seven contributors, but only three on payroll. Burn rate drops by 60% compared to hiring all functions full-time. + +**Growth-Stage Marketplace Preparing for International Expansion** + +A marketplace platform with 50 employees and $8M ARR plans to launch in three new European markets. The Shamrock analysis reveals that the professional core -- product, engineering, and data science -- should remain centralised. Local market launch teams belong in the contractual fringe: country managers engaged on 18-month contracts with performance-based renewal, and local marketing agencies handling market-specific campaigns. Driver/courier networks in each market constitute the flexible leaf, scaled through gig-economy infrastructure. This architecture allows the company to test each market with $200K in committed cost rather than $800K in permanent headcount, preserving optionality to exit underperforming markets without restructuring trauma. + +--- + +## Anti-Patterns + +**Core Inflation.** The most common error: treating every hire as a core employee. If your 30-person startup has 28 full-time employees and two contractors, the shamrock has collapsed into a single leaf. Reassess ruthlessly which roles genuinely require permanent, full-time commitment. + +**Outsourcing the Crown Jewels.** Contracting out the functions that constitute your competitive advantage -- the proprietary algorithm, the customer relationship, the brand voice. If it differentiates you, it belongs in the core. The contractual fringe handles commodity functions, not strategic ones. + +**Treating the Flexible Leaf as Disposable.** Building systems that depend on high-turnover workers without investing in the processes, training, and tools that maintain quality. Uber learned that driver experience directly affects rider retention. The flexible leaf requires operational infrastructure even if it does not require organisational commitment. + +**Static Classification.** Assigning roles to leaves once and never revisiting. As a company grows, functions that began in the fringe often need to migrate to the core. The fractional CMO who served well at $1M ARR may need to become a full-time VP Marketing at $5M. Conversely, mature internal functions sometimes become candidates for outsourcing as specialised providers emerge. + +**Ignoring Cultural Consequences.** A workforce where 80% of contributors are non-core creates real challenges for alignment, communication, and shared purpose. The shamrock model is an economic framework, but it has cultural implications that must be actively managed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Minimise fixed commitments | Almost everything except founder capability sits in the fringe or flexible leaf | +| Validation | Test before you hire | Use contractors to validate demand before converting any role to core | +| Early Traction | Identify the true core | The first three to five non-founder hires define your professional core -- choose with extreme care | +| Growth | Optimise the balance | Systematically evaluate every function's leaf placement; build vendor management capability for the fringe | +| Scale | Institutionalise the model | Formal workforce planning that treats leaf composition as a strategic variable reviewed quarterly | + +--- + +## Output Template + +**Target Audience: Founding Team / COO** + +```markdown +# Workforce Architecture: Shamrock Analysis +## [Company Name] -- [Date] + +### Professional Core (Leaf 1) +| Role | Current Holder | Strategic Justification | Flight Risk | Retention Strategy | +|------|---------------|------------------------|-------------|-------------------| +| [Role] | [Name] | [Why this role is core] | [H/M/L] | [Equity/comp/development plan] | + +### Contractual Fringe (Leaf 2) +| Function | Provider | Contract Type | Annual Cost | Performance Metric | Review Date | +|----------|----------|--------------|-------------|-------------------|-------------| +| [Function] | [Provider] | [Retainer/Project/SLA] | [Cost] | [KPI] | [Date] | + +### Flexible Labour (Leaf 3) +| Function | Source | Volume (FTE equiv.) | Unit Cost | Quality Metric | Scaling Trigger | +|----------|--------|--------------------|-----------|-----------------|-----------------| +| [Function] | [Platform/agency] | [FTE] | [$/hr or $/task] | [Metric] | [When to scale up/down] | + +### Leaf Balance Summary +- Core headcount: [N] ([X]% of total workforce) +- Fringe contributors: [N] ([X]%) +- Flexible contributors: [N] ([X]%) +- Fixed vs. variable labour cost ratio: [X:Y] + +### Migration Candidates +| Role/Function | Current Leaf | Recommended Leaf | Trigger | Timeline | +|---------------|-------------|-----------------|---------|----------| +| [Role] | [Current] | [Recommended] | [What triggers the move] | [When] | +``` + +--- + +## Related Skills + +- **[Kaizen & BPR](kaizen-bpr.md)** -- Process improvement frameworks that determine which functions can be standardised enough for the contractual fringe or flexible leaf. +- **[Systems Thinking](systems-thinking.md)** -- Reveals the interdependencies between the three leaves and the feedback loops that maintain or destabilise organisational balance. +- **[Balanced Scorecard](balanced-scorecard.md)** -- Provides the measurement framework for evaluating whether workforce architecture serves strategic objectives across all four performance dimensions. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- Effective shamrock design requires leaders to delegate not just tasks but entire functions to the contractual fringe and flexible leaf, trusting outcomes over oversight. +- **[Business Model Canvas](business-model-canvas.md)** -- The Key Resources and Key Activities blocks of the Canvas directly inform which capabilities belong in the professional core versus the contractual fringe. diff --git a/plugins/foreman/content/skills/frameworks/situational-leadership.md b/plugins/foreman/content/skills/frameworks/situational-leadership.md new file mode 100644 index 0000000..69dab55 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/situational-leadership.md @@ -0,0 +1,180 @@ +--- +name: "situational-leadership" +description: "Matches leadership style to follower development level using Hersey and Blanchard's Situational Leadership model. Maps four styles -- directing, coaching, supporting, delegating -- to four development levels based on competence and commitment per task. Use when diagnosing style mismatches causing disengagement, assessing delegation readiness, onboarding experienced hires who are new to the domain, or building a management training curriculum." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - management + - team-development + - delegation + - coaching +related_skills: + - lewin-leadership-styles + - tuckman-team-stages + - leadership-pipeline + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +# Situational Leadership + +When Steve Jobs returned to Apple in 1997, he ran the company with iron-fisted directiveness -- killing product lines, overruling engineers, and making unilateral decisions that saved the company from bankruptcy. A decade later, leading the team that created the iPhone, the same Steve Jobs operated differently: setting the vision, then stepping back to let Jony Ive, Scott Forstall, and their teams execute with extraordinary autonomy. Same leader. Radically different style. The conventional explanation is that Jobs "mellowed." The more precise explanation is that he -- consciously or not -- matched his leadership approach to the situation. Paul Hersey and Ken Blanchard formalized this instinct into Situational Leadership Theory, arguing that there is no single best leadership style. There is only the right style for this person, on this task, at this moment. Leaders who refuse to adapt do not fail because they are bad leaders. They fail because they are inflexible ones. + +--- + +## The Framework + +Situational Leadership maps two variables against each other in a 2x2 matrix: the leader's behavior (task-oriented vs. relationship-oriented) and the follower's development level (competence vs. commitment). The result is four leadership styles, each appropriate for a specific combination of follower readiness. + +### The 2x2 Matrix + +``` + TASK BEHAVIOR (Directive) + Low High + +-----------------+-------------------+ + High | S3: | S2: | + | SUPPORTING | COACHING | + RELATIONSHIP | | | + BEHAVIOR | High rel, | High task, | + (Supportive) | Low task | High rel | + +-----------------+-------------------+ + Low | S4: | S1: | + | DELEGATING | DIRECTING | + | | | + | Low rel, | High task, | + | Low task | Low rel | + +-----------------+-------------------+ + + Applied to follower development: + + D1 (Low competence, High commitment) --> S1: DIRECTING + D2 (Some competence, Low commitment) --> S2: COACHING + D3 (High competence, Variable commit) --> S3: SUPPORTING + D4 (High competence, High commitment) --> S4: DELEGATING +``` + +### The Four Styles in Detail + +**S1: Directing** -- The leader provides specific instructions and closely supervises performance. Communication is primarily one-way. This style works when the follower is enthusiastic but unskilled (a new hire eager to prove themselves, a team member tackling an unfamiliar task). The leader's job is to reduce ambiguity and build competence through clear guidance. + +**S2: Coaching** -- The leader still provides direction but also explains decisions, solicits suggestions, and supports progress. Communication is two-way, though the leader retains decision authority. This style addresses the dangerous D2 zone: the follower has learned enough to recognize how much they don't know, and their initial enthusiasm has dimmed. Coaching prevents the "sophomore slump" that causes so many promising employees to disengage or quit. + +**S3: Supporting** -- The leader shifts from directing to facilitating. The follower has the competence to perform but may lack confidence or motivation. The leader's role becomes encouragement, active listening, and collaborative problem-solving. Day-to-day decisions shift to the follower. The leader's value lies in emotional support and removing obstacles, not in providing technical direction. + +**S4: Delegating** -- The leader turns over responsibility for decisions and implementation. Monitoring is minimal. The follower has both the competence and the commitment to operate independently. The leader's job is to stay available without hovering -- to trust the outcome without controlling the process. This is where many founders struggle most, because letting go feels like losing control. + +### The Development Continuum + +Followers move through development levels on each task -- not globally. A senior engineer might be D4 on backend architecture but D1 on customer-facing presentations. A seasoned marketer might be D4 on campaign strategy but D2 on data analytics. Situational Leadership demands that the leader diagnose development level per task, not per person. This granularity is what separates the framework from simpler leadership models. + +--- + +## Prompts + +**Prompt 1 -- Follower Development Assessment:** +> I have a team member in the role of [role] who is responsible for [key tasks]. For each of their major responsibilities, help me assess their development level (D1-D4) based on these observations: [describe their competence and commitment indicators for each task area]. Then recommend which leadership style (S1-S4) I should use for each task area and what that looks like in practice. + +**Prompt 2 -- Leadership Style Mismatch Diagnosis:** +> I'm experiencing friction with a team member. Here's the situation: [describe the person's role, their behavior, your leadership approach, and the symptoms of the problem -- e.g., missed deadlines, disengagement, defensiveness]. Using the Situational Leadership model, diagnose whether there's a mismatch between my leadership style and their development level. What style should I be using instead, and how do I transition without damaging the relationship? + +**Prompt 3 -- Team-Wide Style Map:** +> Map my entire team using Situational Leadership. Here are my team members and their key responsibilities: [list each person, their role, and 2-3 primary tasks]. For each person-task combination, I'll describe their current competence and commitment: [provide observations]. Create a visual map showing which leadership style I should be using with each person on each task, and identify where I'm likely over-directing or under-supporting. + +**Prompt 4 -- Delegation Readiness Check:** +> I want to delegate [specific responsibility] to [team member]. Their current performance on related tasks is [describe]. Using the Situational Leadership D1-D4 framework, assess whether they're ready for S4 (full delegation) or whether I need an intermediate step. If they're not ready, design a development path -- with specific milestones -- that moves them from their current level to D4 on this responsibility. + +**Prompt 5 -- Founder Scaling Assessment:** +> As a founder of a [stage] startup with [number] employees, I find myself [describe your leadership challenges -- e.g., "still making every product decision," "unable to delegate hiring," "micromanaging the sales team"]. Using Situational Leadership, analyze which of my behaviors represent appropriate directing (because the team genuinely needs it) versus over-directing (because I haven't adjusted my style to match their development). Create a 90-day plan for appropriate style shifts. + +--- + +## Use Cases + +**Engineering Manager Losing a Senior Developer** + +A growth-stage startup's engineering manager is applying S1 (Directing) uniformly to the entire team -- including a senior developer who is clearly D4 on most technical tasks. The senior developer, accustomed to autonomy at her previous company, interprets the detailed task assignments and frequent check-ins as distrust. She begins updating her LinkedIn profile. The Situational Leadership diagnosis is immediate: style-development mismatch. The senior developer needs S4 (Delegating) on technical work and perhaps S2 (Coaching) on the company's specific domain knowledge, which she is still acquiring. Restructuring the relationship -- delegating architecture decisions entirely while coaching on industry context -- reverses the disengagement within weeks. + +**First-Time Sales Hire at an Early-Traction Startup** + +A technical founder hires their first salesperson -- an experienced enterprise seller who negotiated seven-figure deals at a Fortune 500 company. The founder assumes S4 (Delegating) is appropriate: "She's a pro, let her do her thing." Three months later, the pipeline is empty. The diagnosis: while the hire is D4 on enterprise sales mechanics, she is D1 on the startup's product, market, competitive landscape, and the radically different sales cycle of a company with no brand recognition. The founder should have started with S1 (Directing) on product knowledge and market positioning while applying S4 on negotiation and relationship management. The nuance of per-task diagnosis would have prevented a costly quarter. + +**Co-Founder Relationship Strain** + +Two co-founders -- one technical, one commercial -- find themselves in escalating conflict. The technical co-founder applies S1 (Directing) to every product decision, treating the commercial co-founder as D1 on anything product-related. The commercial co-founder, who has strong product instincts shaped by years of customer interaction, feels patronized. Mapping the relationship through Situational Leadership reveals that the commercial co-founder is genuinely D1 on technical architecture but D3-D4 on product-market fit, user experience priorities, and feature prioritization. Disaggregating "product decisions" into sub-domains and applying different styles to each domain transforms the relationship from adversarial to complementary. + +--- + +## Anti-Patterns + +- **The Universal Delegator.** Founders who hire experienced people and immediately apply S4 across the board, assuming that seniority equals readiness in every dimension. Every new hire -- regardless of experience -- is D1 on company-specific knowledge, culture, relationships, and domain nuances. Blanket delegation on day one is not empowerment; it is abandonment. + +- **The Permanent Director.** The inverse pathology: founders who cannot release control regardless of how much their team develops. Every team member receives S1 treatment indefinitely. Competent people leave. Those who stay learn helplessness. The organization becomes a reflection of one person's bandwidth. + +- **Assessing Development Level by Person, Not by Task.** Labeling someone as "a D3" globally rather than recognizing that they may be D4 on some tasks and D1 on others. This coarse-grained assessment leads to uniformly wrong leadership approaches and frustrates team members who feel over-managed in their areas of strength and under-supported in their areas of weakness. + +- **Skipping S2 (Coaching).** Moving directly from S1 (Directing) to S3 (Supporting) or S4 (Delegating) without the critical coaching phase. D2 is the most fragile development stage -- the follower knows enough to be dangerous but not enough to be competent, and their initial enthusiasm has faded. Skipping coaching during this stage is the single most common cause of promising employees failing to develop. + +- **Treating the Model as a Personality Test.** Using Situational Leadership to label people ("She's a D2") as though it describes their character. Development levels are task-specific and temporary. They describe a state, not an identity. Leaders who use D-levels as permanent labels create self-fulfilling prophecies. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Diagnosing first hires | Every new hire requires per-task development assessment; founders must resist defaulting to uniform S1 or S4 | +| Growth | Building a management layer | The framework becomes a tool for training new managers, not just for the founder's direct reports; teaching middle managers to diagnose and adapt is critical | +| Scale | Institutionalizing adaptive leadership | Situational Leadership becomes part of the management training curriculum; the organization develops shared vocabulary for discussing leadership style explicitly | + +--- + +## Output Template + +```markdown +# Situational Leadership Map: [Team/Department Name] + +**Date:** [Date] +**Leader:** [Your name/role] +**Team Size:** [Number] + +## Team Member Development Map + +### [Team Member Name] -- [Role] + +| Task/Responsibility | Competence | Commitment | Development Level | Recommended Style | Current Style | Gap? | +|---------------------|-----------|------------|-------------------|-------------------|---------------|------| +| [Task 1] | [Low/Some/High] | [Low/Variable/High] | [D1/D2/D3/D4] | [S1/S2/S3/S4] | [S1/S2/S3/S4] | [Yes/No] | +| [Task 2] | [Level] | [Level] | [D-level] | [S-style] | [S-style] | [Yes/No] | + +### [Next Team Member]... + +## Priority Mismatches +1. **[Person -- Task]:** Currently using [style], should be using [style]. Impact: [what's going wrong] +2. ... + +## 30-Day Adjustment Plan +- **Week 1-2:** [Specific behavior changes with specific people] +- **Week 3-4:** [Follow-up and assessment of impact] + +## Development Goals +| Team Member | Task | Current Level | Target Level | Timeline | Support Needed | +|-------------|------|---------------|-------------|----------|----------------| +| [Name] | [Task] | [D-level] | [D-level] | [Weeks] | [What you'll provide] | +``` + +--- + +## Related Skills + +- **[Lewin's Leadership Styles](lewin-leadership-styles.md)** -- Lewin provides the foundational taxonomy of leadership styles that Hersey and Blanchard refined into a situational model. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- Team development stages interact with individual development levels; a forming team has different leadership needs than a performing one. +- **[Leadership Pipeline](leadership-pipeline.md)** -- As leaders move through pipeline passages, they must learn to apply Situational Leadership at progressively higher organizational levels. +- **[GROW Model](grow-model.md)** -- The GROW coaching conversation is the primary tool for the S2 (Coaching) style; it provides the structure for developing competence while sustaining commitment. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- S4 (Delegating) is the culmination of the development journey; this skill provides the practical playbook for releasing control while maintaining accountability. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- The S2 and S3 styles require coaching skills that go beyond task direction; mentoring relationships accelerate movement through development levels. diff --git a/plugins/foreman/content/skills/frameworks/smart-goals.md b/plugins/foreman/content/skills/frameworks/smart-goals.md new file mode 100644 index 0000000..e2c37f6 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/smart-goals.md @@ -0,0 +1,199 @@ +--- +name: "smart-goals" +description: "Converts vague objectives into Specific, Measurable, Achievable, Relevant, and Time-bound goals. Provides structure for cascading company-level objectives into team-level commitments with accountability. Use when translating founder vision into execution milestones, aligning departments around shared metrics, converting OKRs into actionable goals, critiquing existing goals for rigour, or establishing quarterly planning discipline." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - goal-setting + - planning + - execution + - performance-management + - accountability +related_skills: + - balanced-scorecard + - hackman-enabling-conditions + - leadership-pipeline +author: "Fatih Guner" +--- + +# SMART Goals + +SMART is the most misused acronym in management. Written on thousands of whiteboards, invoked in millions of performance reviews, and executed properly in perhaps a fraction of those cases. George T. Doran introduced the framework in a 1981 issue of *Management Review* with the paper "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives," offering five criteria that transform vague aspirations into actionable commitments. The concept is straightforward. The application is where organizations fail -- not because SMART is intellectually demanding, but because genuinely specific, measurable goals expose the gap between what people say they want to achieve and what they are actually willing to commit to. Vague goals provide cover. SMART goals provide accountability. Most people, when pressed, prefer the cover. + +--- + +## The Framework + +Each letter in SMART represents one criterion that a well-formed goal must satisfy. The criteria are cumulative: a goal that is Specific and Measurable but not Achievable is a fantasy; one that is Achievable and Time-bound but not Relevant is busywork. + +### S -- Specific + +**The criterion:** The goal must answer the journalist's questions: What will be accomplished? Who is responsible? Where will it happen? Which resources or constraints are involved? + +**The failure mode:** "Improve customer satisfaction." This is not a goal; it is a wish. It specifies neither the dimension of satisfaction to improve, the customer segment, nor the mechanism for improvement. + +**The correction:** "Increase NPS among enterprise customers (500+ employees) from 32 to 45 by redesigning the onboarding flow and adding dedicated customer success managers for accounts above $50K ARR." + +The specificity is uncomfortable. It eliminates ambiguity, which also eliminates the ability to retrospectively redefine success. This is precisely the point. + +### M -- Measurable + +**The criterion:** The goal must include concrete metrics that determine whether it has been achieved. If you cannot measure it, you cannot manage it -- and you cannot honestly assess whether you have succeeded or failed. + +**The failure mode:** "Get better at content marketing." Better than what? Measured how? Compared to whom? + +**The correction:** "Publish 12 long-form articles (2,000+ words) that collectively generate 50,000 organic page views and 500 email signups within 6 months." + +Measurability requires choosing metrics before the work begins. This forces the team to confront what actually matters -- which is often a different conversation than what the original vague goal implied. + +### A -- Achievable (also: Attainable, Assignable) + +**The criterion:** The goal must be realistic given current resources, constraints, and capabilities. Stretch is valuable; delusion is not. The goal should require meaningful effort but not demand miracles or capabilities the team does not possess and cannot develop within the timeframe. + +**The failure mode:** A two-person pre-revenue startup setting a goal of "acquire 100,000 users in Q1" with no marketing budget, no distribution channels, and a product still in beta. + +**The correction:** "Acquire 500 beta users through personal network outreach and three targeted community posts, achieving a 30% activation rate." + +The gap between achievable and ambitious is where goal-setting becomes an act of judgment. Hackman's research on compelling direction found that moderately challenging goals produce the highest performance -- not easy goals (no stretch) or impossible ones (no belief). + +### R -- Relevant + +**The criterion:** The goal must align with broader business objectives, team priorities, and strategic direction. A perfectly specific, measurable, achievable, time-bound goal that does not matter to the business is a well-structured distraction. + +**The failure mode:** An early-traction startup setting a goal to "redesign the entire UI to match current design trends" when the core metric that matters is activation rate, and user research shows that confusion about the product's value proposition -- not visual design -- drives abandonment. + +**The correction:** "Increase activation rate from 15% to 30% by redesigning the first-time user experience to communicate core value within 60 seconds." + +Relevance is the criterion that connects individual and team goals to organizational strategy. Without it, departments optimize locally while the company stagnates globally. + +### T -- Time-bound + +**The criterion:** The goal must have a deadline. Without temporal constraint, goals expand indefinitely, priorities remain vague, and urgency is perpetually deferred. + +**The failure mode:** "Launch the mobile app." When? This year? This decade? Without a deadline, this goal sits comfortably on a roadmap forever, never generating the urgency required for completion. + +**The correction:** "Ship the iOS mobile app to the App Store by March 31, with core features X, Y, and Z functional and passing QA review." + +Time-binding forces scope decisions. When the deadline is fixed, the team must negotiate what is included and excluded -- a far more productive conversation than "we'll ship it when it's ready." + +### The Complete SMART Goal Structure + +``` +[Specific action verb] + [measurable outcome] + [achievable scope] + +[relevant to which strategic priority] + [by when] +``` + +**Example:** "Reduce customer churn rate from 8% monthly to 5% monthly (Specific, Measurable) by implementing an automated re-engagement email sequence and proactive support outreach for at-risk accounts (Achievable scope) -- directly supporting our Q3 objective of improving net revenue retention (Relevant) -- by August 31, 2026 (Time-bound)." + +--- + +## Prompts + +**Prompt 1 -- SMART Goal Conversion:** +> Convert the following vague goals into properly formatted SMART goals for my [stage] startup in the [industry] space. Current goals: [list your current goals as they exist, however vague]. For each, apply all five SMART criteria, flag any goal that cannot be made SMART without additional information, and tell me what information is missing. + +**Prompt 2 -- SMART Goal Hierarchy:** +> I have one company-level objective: [describe]. Help me cascade this into SMART goals for each of my teams: [list teams and their functions]. Each team goal must be SMART on its own while clearly contributing to the company objective. Identify potential conflicts between team goals and recommend resolution approaches. + +**Prompt 3 -- SMART Goal Critique:** +> Review these goals my team has set and rate each on a 1-5 scale for each SMART dimension. Goals: [list goals]. For any dimension scoring below 4, provide a specific revision that would strengthen it. Flag any goals that are well-structured but strategically irrelevant. + +**Prompt 4 -- Quarterly OKR-to-SMART Translation:** +> My company uses OKRs for strategic direction: [list your current OKRs]. Translate each Key Result into one or more SMART goals that would achieve it. For each SMART goal, specify the owner, the metric, the target, and the deadline. Identify Key Results that need to be broken into multiple SMART goals to be actionable. + +**Prompt 5 -- Anti-Vanity SMART Goals:** +> I suspect some of our current goals are vanity metrics in disguise. Here are our goals: [list them]. For each, assess whether the metric being measured actually drives business outcomes or merely looks good in a report. Propose replacement SMART goals that target the underlying outcomes we actually care about. + +--- + +## Use Cases + +**Founder Translating Vision into Execution** + +An idea-stage founder has a compelling vision: "Build the operating system for independent restaurants." The vision is powerful for fundraising but useless for daily execution. SMART goal-setting translates the vision into actionable milestones: "Complete 30 customer discovery interviews with independent restaurant owners in the Austin metro area by April 15" (validation); "Build and deploy an MVP menu management module that 10 pilot restaurants use at least 3 times per week by July 1" (early traction); "Achieve $15K MRR from 50 paying restaurants by December 31" (growth). Each goal satisfies all five criteria and connects back to the vision while remaining concrete enough to execute against. + +**Growth-Stage Company Aligning Departments** + +A 60-person B2B SaaS company finds its marketing, sales, and product teams pulling in different directions. Marketing optimizes for MQLs, sales for closed deals, and product for feature velocity -- with no explicit connection between these efforts. SMART goal-setting at the company level ("Increase net revenue retention from 95% to 110% by Q4") cascades into department-specific SMART goals that are mutually reinforcing: Marketing's goal shifts from MQL volume to "generate 200 qualified trials from ICP accounts by Q3"; Sales' goal becomes "close 40 annual contracts above $25K with less than 45-day sales cycle by Q4"; Product's goal becomes "increase activation rate for new accounts from 40% to 65% by shipping three onboarding improvements by end of Q2." The shared language of SMART prevents the optimization silos that previously fragmented the company. + +--- + +## Anti-Patterns + +- **SMART Goals for Everything.** Not all objectives benefit from the SMART treatment. Exploratory research, creative endeavors, and early-stage customer discovery resist rigid measurement and timelines. Applying SMART to "understand our customer better" produces either meaningless metrics or premature closure of the exploration. Reserve SMART for execution goals, not discovery goals. + +- **Measurable But Meaningless.** Goals that satisfy the M criterion with metrics that do not drive business outcomes. "Post 30 LinkedIn updates per month" is perfectly SMART and potentially worthless. The framework does not evaluate whether the metric chosen is the right metric -- that judgment must come from strategic thinking that precedes SMART formatting. + +- **Gaming the Achievable Criterion.** Setting goals that are comfortably achievable to guarantee success rather than to drive performance. Sandbag targets create an illusion of progress while the organization underperforms its potential. The Achievable criterion means "possible with meaningful effort," not "guaranteed without it." + +- **Annual SMART Goals in Startups.** Setting 12-month goals in environments where the strategy may shift in 6 weeks. Startup SMART goals should have shorter time horizons -- 4 to 12 weeks -- that align with the pace of learning and iteration. Annual goals in a validation-stage startup are fiction. + +- **SMART Without Review Cadence.** Setting SMART goals and not revisiting them until the deadline arrives. Goals without regular check-ins are New Year's resolutions. Weekly or biweekly reviews that assess progress, identify obstacles, and adjust scope (while maintaining the goal's SMART structure) are what make the framework operational rather than aspirational. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal founder goals | SMART goals focus on learning objectives: interviews conducted, hypotheses tested, experiments run; the metrics are about discovery, not revenue | +| Validation | Hypothesis-driven goals | Goals center on product-market fit signals: activation rates, retention rates, willingness to pay; time horizons are short (4-8 weeks) | +| Early Traction | Growth and unit economics goals | SMART goals begin to include revenue, CAC, LTV, and retention metrics; team-level goals emerge alongside founder goals | +| Growth | Departmental alignment | SMART goals cascade from company objectives through departments; the challenge is coherence across teams, not individual goal quality | +| Scale | Institutional goal-setting | SMART becomes embedded in performance management, OKR processes, and strategic planning; the risk shifts from vague goals to bureaucratic over-specification | + +--- + +## Output Template + +```markdown +# SMART Goals: [Team/Individual Name] + +**Period:** [Start date -- End date] +**Strategic Context:** [Company-level objective these goals serve] + +## Goal 1: [Goal Name] + +| Criterion | Assessment | +|-----------|-----------| +| **Specific** | [What exactly will be achieved, by whom, through what means] | +| **Measurable** | [Metric: from [current] to [target]] | +| **Achievable** | [Evidence this is realistic: resources available, precedent, capabilities] | +| **Relevant** | [How this connects to strategic priorities] | +| **Time-bound** | [Deadline: specific date] | + +**Full SMART Statement:** [Single sentence combining all five criteria] + +**Milestones:** +- [ ] [Interim milestone 1] -- [Date] +- [ ] [Interim milestone 2] -- [Date] +- [ ] [Final deliverable] -- [Date] + +**Review Cadence:** [Weekly / Biweekly / Monthly] + +## Goal 2: [Goal Name] +... + +## Goal Coherence Check +- [ ] All goals collectively serve the stated strategic context +- [ ] No goal conflicts with another +- [ ] Total goal load is achievable within the time period +- [ ] Metrics chosen drive actual business outcomes, not vanity +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](balanced-scorecard.md)** -- The Balanced Scorecard provides the strategic context that ensures SMART goals are Relevant; goals across financial, customer, process, and learning perspectives create a complete picture. +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Hackman's "compelling direction" condition is fulfilled through well-crafted SMART goals that give teams clear, challenging, consequential objectives. +- **[Eisenhower Matrix](eisenhower-matrix.md)** -- The Eisenhower Matrix determines which goals deserve SMART treatment by distinguishing important objectives from urgent distractions that consume goal-setting energy. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- SMART goals are only effective when embedded in a priority system that protects them from scope creep and competing demands. +- **[Wanting What Matters](../thinking/wanting-what-matters.md)** -- Before making goals SMART, leaders must ensure they are pursuing the right objectives; this skill examines whether the goals themselves reflect genuine priorities rather than default expectations. diff --git a/plugins/foreman/content/skills/frameworks/swot-pest-analysis.md b/plugins/foreman/content/skills/frameworks/swot-pest-analysis.md new file mode 100644 index 0000000..ab1d7f0 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/swot-pest-analysis.md @@ -0,0 +1,212 @@ +--- +name: "swot-pest-analysis" +description: "Conducts integrated SWOT (Strengths, Weaknesses, Opportunities, Threats) and PEST (Political, Economic, Social, Technological) strategic analysis. Generates actionable strategies through the TOWS matrix by crossing internal capabilities with external forces. Use when evaluating market entry, preparing board strategy sessions, assessing competitive positioning, scanning the macro environment for regulatory or economic shifts, or generating evidence-backed strategic options." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - strategic-analysis + - environmental-scanning + - competitive-positioning + - opportunity-assessment + - risk-mapping +related_skills: + - porters-five-forces + - blue-ocean-strategy + - balanced-scorecard + - growth-share-matrix +author: "Fatih Guner" +--- + +# SWOT & PEST Analysis + +A confession: nearly every business plan, pitch deck, and strategy retreat includes a SWOT analysis. Almost none of them do it well. The framework has become so ubiquitous that it has degenerated into a ritual -- four quadrants filled with vague platitudes, then promptly ignored. The same fate has befallen PEST analysis, its macro-environmental counterpart. Yet when applied with intellectual rigour rather than checkbox compliance, these two tools remain among the most powerful diagnostics available to a founder trying to understand where a business actually stands versus where it imagines itself to be. + +SWOT (Strengths, Weaknesses, Opportunities, Threats) was formalised in the 1960s at Stanford Research Institute. PEST (Political, Economic, Social, Technological) emerged from Francis Aguilar's 1967 work on scanning the business environment. Together, they form a layered lens: PEST examines the world around you; SWOT examines you within that world. The error most practitioners commit is treating them as separate exercises rather than an integrated system. + +--- + +## The Framework + +### SWOT: The Internal-External Matrix + +SWOT divides analysis across two dimensions: internal vs. external, and helpful vs. harmful. + +| | **Helpful** | **Harmful** | +|---|---|---| +| **Internal** (within your control) | **Strengths** -- Capabilities, assets, advantages you genuinely possess | **Weaknesses** -- Deficiencies, gaps, vulnerabilities you must confront | +| **External** (outside your control) | **Opportunities** -- Market shifts, trends, unmet needs you could exploit | **Threats** -- Competitive moves, regulations, disruptions that endanger you | + +The quality of a SWOT depends entirely on the quality of inputs. A strength is only a strength if customers or partners actually value it. A threat is only a threat if it could materially affect your trajectory within a relevant timeframe. + +**The SWOT Rigour Test:** For each item listed, ask three questions: +1. **Evidence:** What data supports this claim? (Not opinion -- data.) +2. **Materiality:** Does this factor significantly affect revenue, growth, or survival? +3. **Actionability:** Can we do something specific about it within 90 days? + +If an item fails all three, it does not belong in the matrix. + +### PEST: The Macro-Environmental Scan + +PEST widens the aperture to forces that shape entire industries, not just individual firms. + +| Factor | What to Analyse | Entrepreneurial Relevance | +|--------|----------------|--------------------------| +| **Political** | Regulation, taxation, trade policy, government stability, labour laws | Can a policy change kill your business model? Can it create a new one? | +| **Economic** | Interest rates, inflation, consumer spending, exchange rates, credit availability | Are your unit economics sustainable in a downturn? What happens when funding dries up? | +| **Social** | Demographics, cultural attitudes, lifestyle shifts, education levels, workforce trends | Is your target market growing or shrinking? Are behavioural trends moving toward or away from your offering? | +| **Technological** | Innovation pace, automation, digital infrastructure, R&D activity, platform shifts | Are you building on rising or declining technology? Could a new platform render your product irrelevant? | + +Some practitioners extend PEST to PESTLE (adding Legal and Environmental as separate categories). The extension has merit when regulatory or sustainability factors carry distinct weight -- as they increasingly do. + +### The Integration: PEST Feeds SWOT + +The correct sequence is PEST first, then SWOT. Macro-environmental forces identified through PEST analysis become inputs for the Opportunities and Threats quadrants of SWOT. This prevents the common failure of populating SWOT with nothing but competitor comparisons while ignoring the larger forces reshaping the playing field. + +``` +PEST Analysis (Macro Environment) + | + v +Opportunities & Threats (SWOT External Row) + + +Strengths & Weaknesses (Internal Audit) + | + v +Strategic Options (SO, WO, ST, WT strategies) +``` + +**The TOWS Matrix** converts SWOT from description into prescription: + +| | **Strengths** | **Weaknesses** | +|---|---|---| +| **Opportunities** | **SO Strategies:** Use strengths to capture opportunities | **WO Strategies:** Overcome weaknesses to capture opportunities | +| **Threats** | **ST Strategies:** Use strengths to neutralise threats | **WT Strategies:** Minimise weaknesses and avoid threats | + +This TOWS conversion is where most SWOT analyses fail. They stop at description. The entire point is to generate strategic options. + +--- + +## Prompts + +**Prompt 1 -- PEST Environmental Scan:** +> "Conduct a PEST analysis for a [industry/sector] startup operating in [geography]. For each of the four factors (Political, Economic, Social, Technological), identify the three most significant forces currently affecting startups in this space. Rate each force as accelerating or decelerating our market opportunity, and explain the mechanism through which it operates." + +**Prompt 2 -- Honest SWOT with Evidence:** +> "Generate a SWOT analysis for my business: [brief description, stage, key metrics]. For each item you list, provide the evidence standard -- what data point or observable fact supports this classification? Flag any items that are assumptions rather than evidence-backed claims. Limit each quadrant to the five most material factors." + +**Prompt 3 -- TOWS Strategy Generation:** +> "Given this SWOT matrix: Strengths: [list], Weaknesses: [list], Opportunities: [list], Threats: [list] -- generate the TOWS strategy matrix. For each of the four strategy types (SO, WO, ST, WT), propose two specific, actionable initiatives with a 90-day implementation horizon. Prioritise by impact-to-effort ratio." + +**Prompt 4 -- Competitive SWOT Comparison:** +> "Create parallel SWOT analyses for my company [name/description] and our top two competitors [names/descriptions]. Identify where our strengths overlap with their weaknesses (attack vectors) and where their strengths overlap with our weaknesses (vulnerability zones). Recommend three strategic moves based on the comparison." + +**Prompt 5 -- PEST Scenario Planning:** +> "Using PEST analysis for [industry], construct two scenarios: one where macro trends converge favourably for our business model, and one where they converge unfavourably. For each scenario, identify the three earliest warning signals an entrepreneur should monitor, and the contingency response for the unfavourable case." + +--- + +## Use Cases + +**Pre-Seed Founder Evaluating Market Entry** + +A solo founder developing a fintech lending product for small businesses in Southeast Asia uses PEST to map the regulatory environment across three target markets -- Singapore, Indonesia, and the Philippines. The analysis reveals that Indonesia's new financial services authority regulations create a narrow window of opportunity for licensed digital lenders, while the Philippines' fragmented banking infrastructure presents a social-technological gap. This PEST output feeds into a SWOT that positions the founder's technical background (strength) against the lack of local regulatory relationships (weakness), enabling a focused market-entry strategy that targets Indonesia first. + +**Series A Company Preparing for Board Strategy Session** + +A B2B SaaS company with $2M ARR and 18 months of runway conducts an integrated PEST-SWOT before its annual strategy review. The PEST reveals that an economic slowdown is tightening enterprise software budgets (Economic threat), but remote-work normalisation is increasing demand for their collaboration tool category (Social opportunity). The TOWS matrix produces four strategy streams: accelerate self-serve conversion to capture budget-conscious buyers (SO), build integrations with dominant platforms to offset brand weakness (WO), lock in annual contracts before renewal budgets shrink (ST), and reduce burn by pausing the planned geographic expansion (WT). The board receives a single-page TOWS summary instead of the usual 30-slide deck. + +**Growth-Stage E-Commerce Brand Facing Regulatory Shift** + +An e-commerce company selling health supplements across the EU confronts new regulations on health claims in advertising. PEST analysis surfaces the political factor early. SWOT reveals that the company's in-house regulatory expertise (strength) and established brand trust (strength) position it to capture market share from smaller competitors who lack resources to comply (opportunity), while the same regulation threatens its highest-margin product line due to specific ingredient restrictions (threat). The TOWS strategy: reformulate the restricted products while marketing regulatory compliance as a brand differentiator. + +--- + +## Anti-Patterns + +**The Brainstorm Dump.** Filling SWOT quadrants during a whiteboard session without evidence, data, or customer input. Every item should be substantiated. "Great team" is not a strength -- "92% employee retention with three senior hires from [relevant company]" is. + +**PEST as Academic Exercise.** Producing a comprehensive PEST analysis that reads like a university essay and sits in a drawer. Each factor must connect to a specific strategic implication. If a PEST finding does not change a decision, it does not belong in the analysis. + +**Ignoring the Negatives.** Human psychology favours strengths and opportunities over weaknesses and threats. The most valuable quadrants are often W and T, because they reveal where the business is exposed. Entrepreneurs who produce lopsided analyses with twelve strengths and two weaknesses are engaged in self-deception, not strategy. + +**Static Analysis.** Conducting SWOT/PEST once and treating the output as permanent truth. Markets shift. Competitors move. Regulations change. These frameworks demand quarterly revisiting at minimum, monthly during periods of rapid change. + +**Confusing Internal and External.** Placing items in the wrong row is surprisingly common. "Strong competition" is not a weakness -- it is a threat. "Growing market" is not a strength -- it is an opportunity. The internal/external distinction is not cosmetic; it determines whether you can act on the factor directly or must respond to it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Validate whether the opportunity is real | PEST is primary -- assess whether macro forces support the concept before investing in internal analysis | +| Validation | Test assumptions in each quadrant | Every SWOT item should map to a hypothesis being tested through customer discovery | +| Early Traction | Identify competitive vulnerabilities | Focus shifts to Threats and Weaknesses as competitors notice your traction | +| Growth | Inform resource allocation | TOWS strategies drive quarterly planning; PEST monitors for regulatory and economic headwinds | +| Scale | Support geographic and market expansion | Run separate PEST analyses per new market; SWOT becomes a portfolio-level tool across business units | + +At the idea stage, founders often lack the internal data to populate Strengths and Weaknesses with any rigour. Starting with PEST is both more honest and more productive -- it answers the threshold question of whether the external environment supports the business concept at all. + +By the growth stage, the danger is that SWOT becomes a political exercise where each department advocates for its priorities. Insist on external validation: customer data, market research, and competitor intelligence should drive the analysis, not internal opinions. + +--- + +## Output Template + +**Target Audience: Board / Investors** + +```markdown +# Strategic Position Assessment: [Company Name] +## Date: [Quarter/Year] + +### Macro-Environmental Context (PEST Summary) + +| Factor | Key Finding | Strategic Implication | Trend Direction | +|--------|-------------|----------------------|-----------------| +| Political | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Economic | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Social | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Technological | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | + +### SWOT Matrix + +| | Helpful | Harmful | +|---|---------|---------| +| **Internal** | S1: [Evidence-backed strength] | W1: [Evidence-backed weakness] | +| | S2: [Evidence-backed strength] | W2: [Evidence-backed weakness] | +| | S3: [Evidence-backed strength] | W3: [Evidence-backed weakness] | +| **External** | O1: [Data-supported opportunity] | T1: [Data-supported threat] | +| | O2: [Data-supported opportunity] | T2: [Data-supported threat] | +| | O3: [Data-supported opportunity] | T3: [Data-supported threat] | + +### Strategic Options (TOWS) + +| Strategy Type | Initiative | Timeline | Expected Impact | +|---------------|-----------|----------|-----------------| +| SO (Strength + Opportunity) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| WO (Weakness + Opportunity) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| ST (Strength + Threat) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| WT (Weakness + Threat) | [Specific initiative] | [Q/Year] | [Measurable outcome] | + +### Recommended Priority Actions (Next 90 Days) +1. [Action] -- Owner: [Name] -- Success Metric: [Metric] +2. [Action] -- Owner: [Name] -- Success Metric: [Metric] +3. [Action] -- Owner: [Name] -- Success Metric: [Metric] +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](porters-five-forces.md)** -- Provides the competitive intensity analysis that feeds into SWOT's Threats and Opportunities quadrants. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- Builds on SWOT by asking not just where you stand, but where uncontested market space exists. +- **[Balanced Scorecard](balanced-scorecard.md)** -- Translates SWOT-derived strategies into measurable objectives across four performance dimensions. +- **[Scenario Planning](scenario-planning.md)** -- PEST identifies the driving forces that scenario planning uses as axes; SWOT reveals how the organization would perform under each resulting scenario. +- **[Systems Thinking](systems-thinking.md)** -- Systems thinking reveals how the factors identified in SWOT and PEST interact dynamically over time, preventing static analysis from producing brittle strategies. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- SWOT and PEST provide the analytical inputs; strategic thinking translates those inputs into coherent organizational direction and resource allocation. diff --git a/plugins/foreman/content/skills/frameworks/systems-thinking.md b/plugins/foreman/content/skills/frameworks/systems-thinking.md new file mode 100644 index 0000000..19eacb7 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/systems-thinking.md @@ -0,0 +1,255 @@ +--- +name: "systems-thinking" +description: "Analyzes complex business problems through systems thinking by mapping causal loops, identifying reinforcing and balancing feedback dynamics, and diagnosing system archetypes like Fixes That Fail, Shifting the Burden, and Limits to Growth. Use when quick fixes keep backfiring, growth plateaus unexpectedly, departments optimize locally at the expense of the whole, or interventions produce unintended consequences across the organization." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - systems-dynamics + - feedback-loops + - complexity + - holistic-analysis + - causal-reasoning + - organisational-design +related_skills: + - balanced-scorecard + - kaizen-bpr + - swot-pest-analysis + - shamrock-organisation +author: "Fatih Guner" +--- + +# Systems Thinking + +A startup lowers its prices to win market share. Sales volume surges. The support team, sized for the previous volume, becomes overwhelmed. Response times triple. Customer satisfaction collapses. Negative reviews proliferate. The sales team, now fighting a reputation problem, demands more marketing spend to overcome the brand damage. Margins tighten. The price cut that was supposed to accelerate growth has, through a chain of consequences no single decision-maker foresaw, created a crisis that threatens the company's survival. This is not bad luck. It is a system behaving exactly as its structure dictates. + +Peter Senge's *The Fifth Discipline* (1990) brought systems thinking into the management mainstream, though its roots extend to Jay Forrester's work at MIT in the 1950s and further back to cybernetics. The core insight is deceptively profound: the behaviour of any complex organisation is driven not by individual events or decisions but by the structure of relationships between its components. Change the events and the behaviour persists. Change the structure and the behaviour transforms. + +--- + +## The Framework + +### The Hierarchy of Understanding + +Systems thinkers operate at three levels, each more powerful than the last: + +**Level 1: Events** -- "What just happened?" +Most management operates here. Revenue dropped. A key hire quit. A competitor launched a new feature. Event-level thinking produces reactive responses: cut costs, make a counter-offer, rush a feature release. + +**Level 2: Patterns** -- "What trends are emerging?" +More sophisticated. Revenue has declined for three consecutive quarters. Turnover in engineering has risen from 8% to 22% over 18 months. The competitor has released three features in our core space in the past year. Pattern-level thinking produces adaptive responses: restructure the sales team, review compensation benchmarks, reassess competitive strategy. + +**Level 3: Systemic Structure** -- "What structure produces these patterns?" +The most powerful level. Revenue is declining because the product was optimised for early adopters who are now churning, and the features being built serve new customer segments that have lower lifetime value. Engineering turnover is rising because the technical debt accumulated during rapid growth makes the work unsatisfying, and the best engineers leave first. The competitor is targeting the same customer segment because both companies read the same market research. Structure-level thinking produces generative responses: redesign the product roadmap around retention, allocate 30% of engineering capacity to technical debt reduction, develop a differentiated positioning that avoids head-to-head competition. + +### Feedback Loops: The Engine of System Behaviour + +Two types of feedback loops drive all system dynamics: + +**Reinforcing Loops (R)** -- Amplify change in one direction. They produce growth or collapse. + +``` +Customer satisfaction rises + | + v +Word-of-mouth referrals increase --> New customers arrive + | | + v v +Revenue grows --> Investment in product --> Product quality improves + | + v +(Loop back to customer satisfaction) +``` + +Reinforcing loops create virtuous cycles or death spirals. The same structure that drives exponential growth, when reversed, drives exponential decline. + +**Balancing Loops (B)** -- Resist change and push toward equilibrium. They stabilise or constrain. + +``` +Company grows rapidly + | + v +Hiring accelerates --> New employees need training + | | + v v +Management bandwidth consumed --> Quality of decisions declines + | | + v v +Growth slows (balancing against the growth impulse) +``` + +Every entrepreneur has experienced balancing loops: the growth ceiling that appears just when momentum feels unstoppable. The ceiling is not external -- it is structural. + +### System Archetypes + +Senge identified recurring patterns that appear across industries and organisations: + +**Fixes That Fail** +A quick fix alleviates symptoms but creates side effects that eventually make the original problem worse. + +- Cause: Team is missing deadlines +- Quick Fix: Mandate overtime +- Side Effect (delayed): Burnout, turnover, knowledge loss +- Result: Team misses even more deadlines + +**Shifting the Burden** +A symptomatic solution undermines the ability to implement a fundamental solution. + +- Symptom: Customer complaints about product quality +- Symptomatic Solution: Increase customer support headcount +- Fundamental Solution: Fix the product defects at the source +- Burden Shift: The support team becomes so effective at managing complaints that the urgency to fix the product disappears + +**Limits to Growth** +A reinforcing process drives growth, but eventually triggers a balancing process that slows or stops it. + +- Growth Engine: Viral product adoption +- Limiting Factor: Server infrastructure cannot scale at the same rate +- Behaviour: Growth accelerates, then plateaus, then frustration drives users to alternatives + +**Tragedy of the Commons** +Multiple actors share a finite resource, each acting rationally in their own interest, collectively depleting the resource. + +- Shared Resource: Engineering team's time +- Individual Actors: Product managers from different business lines +- Behaviour: Each PM escalates priority of their requests; engineering becomes a bottleneck; everyone suffers + +### Causal Loop Diagrams + +The primary tool of systems thinking is the causal loop diagram -- a visual map of the cause-and-effect relationships that define a system's structure. + +Notation: +- Arrow: A causes B +- (+): A and B move in the same direction (A rises, B rises) +- (-): A and B move in opposite directions (A rises, B falls) +- (R): Reinforcing loop +- (B): Balancing loop + +Constructing a causal loop diagram for your business reveals the hidden architecture that drives performance. Most founders carry an implicit mental model of their business; making it explicit exposes assumptions, identifies leverage points, and prevents interventions that worsen the problem they aim to solve. + +--- + +## Prompts + +**Prompt 1 -- System Mapping:** +> "Map the key causal loops in my business: [describe business model, key metrics, and current challenges]. Identify at least two reinforcing loops (growth engines or death spirals) and two balancing loops (growth ceilings or stabilisers). For each loop, list the variables involved and the direction of influence between them." + +**Prompt 2 -- Archetype Diagnosis:** +> "My company is experiencing this problem: [describe problem and the solutions already attempted]. Analyse whether this matches one of the classic system archetypes (Fixes That Fail, Shifting the Burden, Limits to Growth, Tragedy of the Commons, or others). If it does, identify the quick fix, the fundamental solution, and the delayed consequence that the current approach is generating." + +**Prompt 3 -- Leverage Point Identification:** +> "Given this system structure of my business: [describe key variables and their relationships], identify the three highest-leverage intervention points -- places where a small change would produce the largest systemic effect. For each leverage point, explain the mechanism through which the intervention propagates through the system and the expected timeline for results." + +**Prompt 4 -- Unintended Consequences Forecast:** +> "We are planning to implement this change: [describe proposed initiative]. Using systems thinking, trace the likely first-, second-, and third-order consequences of this change across our organisation. Identify which feedback loops it will strengthen, which it will weaken, and any balancing loops it might trigger that could undermine the intended outcome." + +**Prompt 5 -- Mental Model Audit:** +> "Describe the implicit mental model behind our current strategy: [describe strategy]. What assumptions about cause and effect does this strategy depend on? Which of those assumptions are testable, and how would we test them? Where might our mental model diverge from the actual system structure?" + +--- + +## Use Cases + +**Validation-Stage Startup Diagnosing a Conversion Problem** + +A B2C app has strong acquisition (50,000 downloads/month) but abysmal activation (8% of downloads complete onboarding). The founder's instinct is to simplify onboarding (event-level fix). Systems mapping reveals a reinforcing loop: the product was designed for power users, which attracts power users through word-of-mouth, which generates feature requests that increase complexity, which makes onboarding harder for mainstream users, which keeps the user base skewed toward power users. The leverage point is not the onboarding flow but the product roadmap: introducing a simplified product tier breaks the reinforcing loop and opens the mainstream market without alienating the core user base. + +**Growth-Stage Company Facing a Hiring Bottleneck** + +A company growing 15% month-over-month cannot hire fast enough. The obvious solution -- throw more resources at recruiting -- triggers a balancing loop: faster hiring reduces quality of hire, which increases onboarding time, which consumes the capacity of existing team members, which reduces productivity, which increases the perceived need to hire more. The systems diagnosis identifies the leverage point as onboarding efficiency, not hiring velocity. By investing in structured onboarding (reducing time-to-productivity from 90 to 30 days), each new hire contributes sooner, reducing the total headcount needed and breaking the balancing loop. + +**Scale-Stage Platform Managing Marketplace Dynamics** + +A two-sided marketplace observes that supply growth is decelerating despite increasing demand. Causal loop analysis reveals a Tragedy of the Commons: as more suppliers join, each supplier's share of demand decreases, reducing per-supplier revenue, leading to supplier dissatisfaction and churn. The platform's response -- subsidising supplier onboarding -- merely accelerates the dynamic. The fundamental solution involves demand-side curation (matching quality suppliers with high-intent buyers) rather than supply-side volume, rebalancing the system to favour supplier profitability over raw supply count. + +--- + +## Anti-Patterns + +**Linear Thinking in a Non-Linear World.** Assuming that cause and effect are proximate in time and space. In systems, the cause of today's problem is often a decision made six months ago in a different department. Entrepreneurs who demand immediate attribution ("What caused this?") miss the systemic structure that produced it. + +**Optimising Components Instead of the System.** Making each department maximally efficient without considering how they interact. A sales team optimised for closing deals fast may generate customers who churn quickly, destroying value that the customer success team then scrambles to recover. Local optimisation frequently produces global degradation. + +**Ignoring Delays.** Feedback loops operate with time delays. An investment in product quality may not show results for two quarters. Founders who expect immediate returns from structural changes abandon them too early, concluding they did not work when they simply had not had time to propagate through the system. + +**Confusing Symptoms with Causes.** Treating declining revenue as the problem rather than as a symptom of the structural dynamics producing it. Every metric is an output of a system. Intervening at the output level (discounting to boost revenue) without addressing the input level (why customers are not buying at full price) creates the "Fixes That Fail" archetype. + +**Analysis Paralysis.** Systems thinking can become an intellectual trap. Mapping every variable and feedback loop in a complex organisation is theoretically possible but practically useless. The skill is identifying the three to five loops that dominate system behaviour and intervening there. Perfectionism in systems mapping is itself a balancing loop that constrains action. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Map your growth engine | Identify the one reinforcing loop that, if activated, drives product-market fit | +| Early Traction | Anticipate balancing loops | Growth will trigger constraints; identify them before they manifest | +| Growth | Diagnose system archetypes | Most growth-stage problems match known archetypes; pattern recognition accelerates diagnosis | +| Scale | Design system architecture | At scale, you are designing systems, not managing events; invest in structural thinking | + +At the validation stage, the entire business is essentially one hypothesis about a reinforcing loop: "If we build X, users will do Y, which creates Z value, which funds more of X." Validating that loop is the only thing that matters. + +The growth-to-scale transition is where systems thinking pays its highest dividends. The problems that emerge at scale -- coordination failures, cultural drift, quality degradation -- are almost always structural. Founders who continue to manage events ("Fire that underperformer," "Hire a VP of X") without examining the system that produces those events will exhaust themselves and their organisations. + +--- + +## Output Template + +**Target Audience: Executive Team / Strategic Advisors** + +```markdown +# Systems Analysis: [Issue or Initiative] +## [Company Name] -- [Date] + +### Problem Statement +[Describe the observable behaviour -- the event or pattern that triggered this analysis] + +### Level of Analysis +- Event: [What happened] +- Pattern: [What trend does this belong to] +- Structure: [What systemic structure produces this pattern] + +### Causal Loop Map +[Describe the key variables and their relationships] +- Variable A --(+)--> Variable B --(+)--> Variable C +- Variable C --(-)--> Variable D --(+)--> Variable A +- Loop Type: [Reinforcing / Balancing] + +### Active System Archetypes +| Archetype | Evidence | Quick Fix (Avoid) | Fundamental Solution | +|-----------|----------|-------------------|---------------------| +| [Archetype name] | [Observable symptoms] | [What feels obvious but worsens things] | [Structural intervention] | + +### Leverage Points +| # | Intervention | Mechanism | Expected Timeline | Confidence | +|---|-------------|-----------|-------------------|------------| +| 1 | [Highest-leverage change] | [How it propagates] | [When results appear] | [H/M/L] | +| 2 | [Second-highest] | [How it propagates] | [When results appear] | [H/M/L] | +| 3 | [Third-highest] | [How it propagates] | [When results appear] | [H/M/L] | + +### Unintended Consequences to Monitor +| Intervention | Possible Side Effect | Early Warning Signal | Mitigation | +|-------------|---------------------|---------------------|------------| +| [Change] | [Potential consequence] | [What to watch for] | [How to respond] | + +### Recommended Actions +1. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +2. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +3. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](balanced-scorecard.md)** -- Provides the four-dimensional measurement framework that makes system behaviour visible and trackable across financial, customer, process, and learning perspectives. +- **[Kaizen & BPR](kaizen-bpr.md)** -- Process improvement tools that operate within the system; Systems Thinking ensures improvements in one process do not degrade connected processes. +- **[SWOT & PEST Analysis](swot-pest-analysis.md)** -- PEST identifies external system forces; SWOT maps internal-external interactions; Systems Thinking reveals how these forces dynamically interact over time. +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- System 1 thinking produces the linear cause-and-effect reasoning that systems thinking corrects; deliberate System 2 engagement is required to see feedback loops and delays. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- Systems thinking redefines what constitutes the "problem" by revealing that observable symptoms often originate in distant structural causes, not proximate events. +- **[Scenario Planning](scenario-planning.md)** -- Scenario planning uses the system maps that systems thinking produces to stress-test strategies against multiple plausible futures shaped by different feedback dynamics. diff --git a/plugins/foreman/content/skills/frameworks/thinking-fast-and-slow.md b/plugins/foreman/content/skills/frameworks/thinking-fast-and-slow.md new file mode 100644 index 0000000..82796e7 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/thinking-fast-and-slow.md @@ -0,0 +1,185 @@ +--- +name: "thinking-fast-and-slow" +description: "Audits business decisions for cognitive biases using Kahneman's dual-process theory of System 1 (fast, intuitive) and System 2 (slow, analytical) thinking. Covers overconfidence, anchoring, loss aversion, planning fallacy, and availability heuristic. Use when conducting pre-mortems on major initiatives, debiasing fundraising projections, applying reference-class forecasting, sorting decisions by required processing mode, or building structured decision protocols." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - cognitive-bias + - decision-making + - behavioural-economics + - heuristics + - risk-assessment +related_skills: + - emotional-intelligence + - flow-state + - vuca-framework + - psychological-safety +author: "Fatih Guner" +--- + +# Thinking, Fast and Slow + +The human mind is simultaneously the most sophisticated decision-making instrument ever developed and a deeply unreliable narrator of its own reasoning. That paradox sits at the centre of Daniel Kahneman's work: the very cognitive machinery that enables entrepreneurs to spot opportunities in ambiguity is the same machinery that systematically misleads them about probability, risk, and the quality of their own judgments. Kahneman, a psychologist who won the Nobel Prize in Economics, spent decades demonstrating that rationality is not the default setting of the human brain -- it is an effortful exception. For founders making high-stakes decisions under uncertainty, understanding the architecture of their own thinking is not a philosophical luxury. It is a competitive necessity. + +--- + +## The Framework + +Kahneman's model divides cognition into two distinct systems, each with its own operational characteristics, strengths, and failure modes. + +### System 1 and System 2 + +| Dimension | System 1 (Fast) | System 2 (Slow) | +|-----------|-----------------|-----------------| +| **Speed** | Instantaneous, automatic | Deliberate, effortful | +| **Awareness** | Operates below conscious threshold | Requires focused attention | +| **Capacity** | Parallel, high-throughput | Serial, limited bandwidth | +| **Energy cost** | Low | High (depletes with use) | +| **Error profile** | Systematic biases, predictable mistakes | Logical but lazy -- often endorses System 1 | +| **Strengths** | Pattern recognition, intuition, rapid assessment | Analysis, planning, complex calculation | +| **Triggers** | Familiar situations, emotional stimuli | Novel problems, explicit instructions to "think carefully" | + +The critical insight is not that System 1 is bad and System 2 is good. Rather, most people -- including experienced executives -- dramatically overestimate how often System 2 is actually engaged. System 2 is cognitively expensive, and the brain defaults to System 1 wherever possible. + +### The Bias Catalogue for Entrepreneurs + +Several of Kahneman's identified biases carry outsized relevance for startup decision-making: + +**Overconfidence bias.** Founders consistently overestimate the probability of their venture's success and underestimate the time and resources required. Kahneman's research shows that experts are no less susceptible than novices -- in many domains, they are more so, because their confidence scales faster than their accuracy. + +**Anchoring effect.** The first number encountered in a negotiation, valuation discussion, or market-sizing exercise disproportionately shapes subsequent estimates. A seed-stage founder who hears "companies like yours typically raise $2M" will unconsciously anchor all subsequent financial planning to that figure, regardless of whether it reflects their actual needs. + +**Loss aversion.** Losses are psychologically weighted roughly twice as heavily as equivalent gains. This explains why founders cling to failing products far longer than rational analysis warrants -- the pain of admitting loss exceeds the potential pleasure of redeploying resources toward a better opportunity. + +**Planning fallacy.** People systematically underestimate the time, cost, and risk of future actions while overestimating their benefits. Kahneman recommends adopting the "outside view" -- examining base rates from comparable projects rather than building estimates from the inside. + +**Availability heuristic.** Judgments about probability are distorted by how easily examples come to mind. A founder who just read about a unicorn exit in their sector will overestimate the likelihood of a similar outcome for their own company. + +### The Pre-Mortem Technique + +Kahneman's most directly actionable tool for entrepreneurs is the pre-mortem. Rather than asking "Will this plan succeed?", a team imagines that it is one year in the future and the plan has definitively failed. Each member then independently writes down the reasons for failure. This technique accomplishes two things: it legitimises dissent (overcoming groupthink) and it activates prospective hindsight, which research shows increases the ability to identify causes of future outcomes by roughly 30%. + +--- + +## Prompts + +**Prompt 1 -- Bias Audit:** +> Conduct a cognitive bias audit on the following business decision: [describe decision]. Identify which of Kahneman's biases (overconfidence, anchoring, loss aversion, planning fallacy, availability heuristic, WYSIATI) are most likely influencing the decision-makers. For each bias identified, suggest a specific debiasing technique and explain how to implement it in the context of this decision. + +**Prompt 2 -- Pre-Mortem Facilitation:** +> Run a pre-mortem analysis on this plan: [describe plan]. Assume it is 12 months from now and the plan has failed completely. Generate 8-10 plausible reasons for failure, categorised by whether they stem from internal factors (team, execution, resources) or external factors (market, competition, regulation). Rank them by likelihood and suggest early warning indicators for each. + +**Prompt 3 -- Outside View Assessment:** +> Apply Kahneman's "outside view" methodology to this projection: [describe projection, e.g., "We will reach $1M ARR within 18 months"]. Research base rates for comparable companies at our stage ([stage]) in our sector ([sector]). Compare our inside-view assumptions against these base rates and highlight the largest discrepancies. Recommend adjusted projections. + +**Prompt 4 -- System 1/System 2 Decision Sort:** +> Review the following list of pending decisions for my startup: [list decisions]. Classify each as appropriate for System 1 processing (pattern-matching, intuition-safe) or requiring System 2 engagement (novel, high-stakes, irreversible). For the System 2 decisions, recommend a specific analytical framework or structured process to ensure deliberate reasoning. + +--- + +## Use Cases + +**Seed-stage SaaS founder evaluating pivot options** + +A B2B SaaS founder at the validation stage has two potential pivots after initial product-market fit signals proved weak. She finds herself drawn to Option A because a prominent accelerator mentor mentioned a similar company that succeeded (availability heuristic) and because she has already invested eight months building toward that direction (loss aversion / sunk cost). Applying Kahneman's framework, she conducts a pre-mortem on both options, seeks base-rate data on comparable pivots, and deliberately assigns a team member to argue the case for Option B. The structured process reveals that Option B has stronger unit economics and a less crowded competitive landscape -- factors her System 1 had deprioritised because they were less emotionally vivid. + +**Growth-stage marketplace negotiating acquisition terms** + +A two-sided marketplace with $5M ARR receives an acquisition offer. The founding team anchors on the first number proposed by the acquirer and spends weeks negotiating around that figure. A board advisor trained in Kahneman's work recognises the anchoring effect and introduces an independent valuation analysis using three distinct methodologies, none of which reference the acquirer's initial offer. The resulting negotiation achieves a 40% higher price because the team broke free of the original anchor. + +**Scale-stage fintech building annual forecasts** + +A fintech company at scale consistently underestimates project timelines by 30-50%. The COO implements Kahneman's reference-class forecasting: instead of building estimates bottom-up from project plans, the team first identifies a reference class of 20 similar projects completed in the past two years, calculates the statistical distribution of actual completion times, and uses that distribution as the starting point for new estimates. Planning accuracy improves markedly within two quarters. + +--- + +## Anti-Patterns + +**1. "I already know about biases, so I'm debiased."** Awareness of cognitive biases does not neutralise them. Kahneman himself has stated that decades of studying biases did not make him immune to them. The solution is structural -- building decision processes that compensate for bias, not relying on individual awareness. + +**2. Weaponising bias labels to win arguments.** Labelling a colleague's position as "anchoring" or "confirmation bias" becomes a rhetorical trick rather than a genuine analytical tool. Bias identification should apply to the decision process, not to individuals in the room. The moment it becomes ad hominem, it destroys the psychological safety required for honest deliberation. + +**3. Paralysis through over-analysis.** Some teams, having discovered the extent of cognitive bias, become unable to make any decision without exhaustive debiasing procedures. Kahneman's own framework acknowledges that System 1 is appropriate for many decisions -- particularly those that are reversible, low-stakes, or where the decision-maker has genuine domain expertise built through years of practice with rapid feedback. + +**4. Applying the outside view to genuinely novel situations.** Reference-class forecasting requires a meaningful reference class. When a company is doing something truly unprecedented, there may be no valid outside view. Forcing one can be as misleading as the inside view it replaces. + +**5. Ignoring that System 2 is depletable.** Scheduling all high-stakes decisions in a single marathon session is counterproductive. System 2 fatigues. Decision quality degrades with cognitive load. Structuring the calendar so that critical decisions receive fresh cognitive resources is itself a strategic choice. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Hypothesis testing under maximum uncertainty | Overconfidence and confirmation bias are most dangerous here -- founders must resist interpreting ambiguous signals as validation | +| Early Traction | Scaling decisions and resource allocation | Anchoring on early metrics (first customers, first pricing) can distort strategy as the company moves beyond its initial niche | +| Growth | Hiring, market expansion, competitive response | Loss aversion makes it difficult to kill underperforming product lines or exit markets; pre-mortems become essential for major initiatives | +| Scale | M&A, organisational design, forecasting | Planning fallacy dominates large-scale projects; reference-class forecasting and structured decision processes yield the highest returns here | + +At the validation stage, the most frequent failure mode is confirmation bias -- interpreting every piece of ambiguous customer feedback as evidence that the hypothesis is correct. The corrective is to define falsification criteria before running experiments: "What specific result would cause us to abandon this hypothesis?" + +At growth and scale, the dominant risk shifts to organisational bias amplification. Individual biases compound through group dynamics. A CEO's overconfidence becomes the company's overconfidence when no structural counterweight exists. Formal decision protocols -- including pre-mortems, red teams, and independent analysis -- become operational necessities rather than intellectual exercises. + +--- + +## Output Template + +```markdown +# Cognitive Bias Assessment -- [Decision/Initiative Name] + +**Prepared for:** Board / Leadership Team +**Date:** [Date] +**Decision under review:** [One-sentence description] + +## Decision Classification +- **Reversibility:** [Reversible / Partially reversible / Irreversible] +- **Stakes:** [Low / Medium / High] +- **Novelty:** [Routine / Somewhat novel / Unprecedented] +- **Recommended processing mode:** [System 1 sufficient / System 2 required] + +## Bias Scan + +| Bias | Risk Level | Evidence | Debiasing Action | +|------|-----------|----------|-----------------| +| Overconfidence | [H/M/L] | [Specific evidence] | [Specific action] | +| Anchoring | [H/M/L] | [Specific evidence] | [Specific action] | +| Loss aversion | [H/M/L] | [Specific evidence] | [Specific action] | +| Planning fallacy | [H/M/L] | [Specific evidence] | [Specific action] | +| Availability | [H/M/L] | [Specific evidence] | [Specific action] | + +## Pre-Mortem Results +**Scenario:** It is [date + 12 months]. This initiative has failed. + +### Top Failure Causes (ranked by likelihood) +1. [Cause] -- Early warning indicator: [indicator] +2. [Cause] -- Early warning indicator: [indicator] +3. [Cause] -- Early warning indicator: [indicator] + +## Outside View +- **Reference class:** [Description of comparable situations] +- **Base rate of success:** [X%] +- **Our inside-view estimate:** [Y%] +- **Recommended adjusted estimate:** [Z%] + +## Decision Recommendation +[Proceed / Proceed with modifications / Delay / Abandon] + +**Rationale:** [2-3 sentences incorporating bias-adjusted analysis] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](emotional-intelligence.md)** -- Kahneman's System 1 is heavily influenced by emotional states; Goleman's framework provides the self-awareness layer needed to recognise when emotions are hijacking judgment. +- **[VUCA Framework](vuca-framework.md)** -- High-VUCA environments amplify every cognitive bias Kahneman identifies; structured responses to volatility and ambiguity are the organisational complement to individual debiasing. +- **[Psychological Safety](psychological-safety.md)** -- Pre-mortems and bias audits only work when team members feel safe challenging prevailing assumptions, making Edmondson's framework a prerequisite for effective debiasing. +- **[Enemies of Clear Thinking](../thinking/enemies-of-clear-thinking.md)** -- Expands Kahneman's bias catalogue into a broader inventory of reasoning failures, providing additional tools for recognizing when System 1 shortcuts produce systematic errors. +- **[Evaluating and Deciding](../thinking/evaluating-and-deciding.md)** -- Provides structured decision frameworks that force System 2 engagement on high-stakes choices where intuitive judgment is most likely to mislead. +- **[Stoic Unbiased Thought](../stoic/stoic-unbiased-thought.md)** -- The Stoic practice of examining impressions before assenting to them is an ancient parallel to Kahneman's prescription for overriding System 1 with deliberate System 2 analysis. diff --git a/plugins/foreman/content/skills/frameworks/thomas-kilmann-conflict.md b/plugins/foreman/content/skills/frameworks/thomas-kilmann-conflict.md new file mode 100644 index 0000000..fd15e6d --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/thomas-kilmann-conflict.md @@ -0,0 +1,206 @@ +--- +name: "thomas-kilmann-conflict" +description: "Diagnoses and resolves conflicts using the Thomas-Kilmann + five-mode framework: competing, collaborating, compromising, avoiding, and + accommodating, mapped across assertiveness and cooperativeness dimensions. Use + when navigating co-founder disagreements, mediating cross-functional team + friction, choosing the right conflict mode for high-stakes decisions, + expanding personal conflict style range, or designing conflict resolution + processes for the organization." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - conflict-resolution + - negotiation + - team-dynamics + - communication + - leadership +related_skills: + - radical-candor + - win-win-negotiation + - tuckman-team-stages + - trust-equation +author: "Fatih Guner" +--- + +# Thomas-Kilmann Conflict Mode Instrument + +Two cofounders sit across from each other at a board meeting. The CTO wants to rebuild the platform from scratch -- eighteen months of engineering effort that will freeze feature development. The CEO insists the business cannot survive eighteen months without new features; the rebuild must happen incrementally, alongside shipping. Both are right. Both are wrong. Neither can unilaterally win without destroying the partnership. The board members exchange glances, recognising a pattern they have seen dismantle companies more promising than this one. + +How this conflict resolves -- not whether it resolves, but *how* -- will determine the company's trajectory more decisively than any product decision. Kenneth Thomas and Ralph Kilmann mapped exactly this terrain in the 1970s, identifying five distinct conflict-handling modes arranged along two dimensions: assertiveness (the degree to which you pursue your own concerns) and cooperativeness (the degree to which you attempt to satisfy the other party's concerns). The genius of their model is not prescribing one mode as superior but revealing that effective leaders command all five and deploy each situationally. + +--- + +## The Framework + +### The Two Dimensions + +The TKI plots conflict behaviour on two independent axes: + +- **Assertiveness** (vertical axis): The extent to which you attempt to satisfy your own concerns. High assertiveness means you push for your position; low assertiveness means you set your concerns aside. +- **Cooperativeness** (horizontal axis): The extent to which you attempt to satisfy the other party's concerns. High cooperativeness means you prioritise the relationship and the other's needs; low cooperativeness means you focus solely on your own outcome. + +### The Five Modes + +``` + HIGH ASSERTIVENESS + | + Competing | Collaborating + (Win-Lose) | (Win-Win) + | + LOW ───────── Compromising ─────── HIGH + COOPERATIVENESS | COOPERATIVENESS + | + Avoiding | Accommodating + (Lose-Lose) | (Lose-Win) + | + LOW ASSERTIVENESS +``` + +**1. Competing (High Assertiveness, Low Cooperativeness)** + +You pursue your position at the other party's expense. Power, authority, or force of will determines the outcome. + +- **When to use:** Emergencies requiring rapid action. Unpopular but necessary decisions (layoffs, pivots). When you know you are right on matters of principle. Protecting against people who exploit non-competitive behaviour. +- **When to avoid:** Routine disagreements. Situations requiring buy-in from the other party. Relationships you need to preserve long-term. + +**2. Collaborating (High Assertiveness, High Cooperativeness)** + +Both parties work together to find a solution that fully satisfies everyone's concerns. This is not compromise -- no one gives anything up. + +- **When to use:** When both sets of concerns are too important to trade away. When you need to learn (the other party may have information you lack). When building commitment is essential to implementation. Integrating insights from people with different perspectives. +- **When to avoid:** Trivial issues where the time investment is disproportionate. When one party is not acting in good faith. Under genuine time pressure. + +**3. Compromising (Moderate Assertiveness, Moderate Cooperativeness)** + +Both parties give up something. The solution partially satisfies everyone but fully satisfies no one. Splitting the difference is the archetype. + +- **When to use:** When goals are moderately important but not worth the disruption of competing or the time investment of collaborating. As a temporary settlement to complex issues. When two equally powerful parties are equally committed to mutually exclusive goals. As a fallback when collaboration fails. +- **When to avoid:** When the issue genuinely matters and a creative solution exists. When one party can be persuaded by evidence. When "splitting the difference" produces a solution inferior to either original position. + +**4. Avoiding (Low Assertiveness, Low Cooperativeness)** + +You sidestep the conflict entirely. Neither your concerns nor the other party's concerns are addressed. + +- **When to use:** When the issue is trivial. When you have no chance of satisfying your concerns. When the potential damage of confrontation outweighs the benefits. To let people cool down. When gathering more information is essential before engaging. +- **When to avoid:** When issues will fester and escalate. When avoidance signals indifference or weakness. When your silence is being interpreted as agreement. + +**5. Accommodating (Low Assertiveness, High Cooperativeness)** + +You set aside your own concerns to satisfy the other party. The opposite of competing. + +- **When to use:** When you realise you were wrong. When the issue matters far more to the other party than to you. To build social credit for future issues that matter more. When preserving harmony is critical. When continued competition would only damage the relationship. +- **When to avoid:** When your concern is legitimate and important. When accommodating becomes a habitual pattern that breeds resentment. When the other party is not reciprocating over time. + +### Mode Selection Matrix + +| Situation | Recommended Mode | Rationale | +|-----------|-----------------|-----------| +| Server is down, customers affected | Competing | Speed overrides consensus | +| Cofounder disagrees on company vision | Collaborating | Both perspectives contain essential truth | +| Negotiating office lease terms | Compromising | Moderate stakes, clear trade-offs | +| Team member raises a complaint during a crisis | Avoiding (temporarily) | Address after the immediate crisis resolves | +| Junior team member has a better idea than yours | Accommodating | Their idea wins on merit; your ego is irrelevant | +| Board member pushes strategy you believe is destructive | Competing | Fiduciary principle at stake | +| Product and engineering disagree on sprint priorities | Collaborating | Both functions must buy in for execution | + +--- + +## Prompts + +**Prompt 1 -- Conflict Diagnosis:** +> I am in a conflict with [describe the other party and their role]. The disagreement concerns [describe the issue]. Using the Thomas-Kilmann model, help me identify which conflict mode I am currently defaulting to, which mode the other party appears to be using, and which mode would be most effective given the stakes, the relationship importance, and the time constraints. Explain your recommendation. + +**Prompt 2 -- Mode Expansion:** +> Analyse my natural conflict style based on these recent situations: [describe 3-4 recent conflicts and how you handled them]. Using the TKI framework, identify which modes I overuse and which I underuse. Then provide specific behavioural scripts for the modes I need to develop, tailored to my role as [founder/CEO/manager] at a [stage] company. + +**Prompt 3 -- Team Conflict Mediation:** +> Two members of my team are in sustained conflict over [describe the issue]. One appears to be operating in [mode] and the other in [mode]. As their manager, help me design an intervention using the TKI framework: What mode should I adopt as the mediator? What questions should I ask each party? What process would move them toward a productive resolution? + +**Prompt 4 -- Cofounder Conflict Resolution:** +> My cofounder and I disagree fundamentally about [describe the issue]. Our relationship is critical to the company's survival, but the issue cannot be avoided. Using the Thomas-Kilmann model, walk me through a collaborating-mode approach: How do I structure the conversation? What are the key moves to ensure both concerns are fully surfaced? What happens if collaboration fails -- what is my fallback mode and when do I invoke it? + +--- + +## Use Cases + +**Cofounder Equity Dispute at Validation Stage** +Two cofounders who launched with a 50/50 split now contribute asymmetrically -- one works full-time, the other retains a day job. The full-time founder wants to renegotiate. Default mode: competing ("I deserve more"). Effective mode: collaborating. The conversation reframes from "dividing a fixed pie" to "designing a structure that incentivises both parties to maximise their contribution." The output: a dynamic equity arrangement (using a tool like Slicing Pie) that adjusts ownership based on relative contribution, satisfying both parties' core concerns. + +**Product vs. Sales Conflict at Growth Stage** +The VP of Sales demands custom features for a whale client. The VP of Product refuses, citing roadmap integrity. Both escalate to the CEO. Applying TKI, the CEO recognises that competing (choosing a side) will alienate one function. Avoiding (deferring the decision) will cost the deal and the roadmap. The CEO facilitates a collaborating session that reveals an alternative: the whale client's requirements overlap 70% with planned platform features; sequencing those features first satisfies both the client timeline and the roadmap logic. The remaining 30% becomes a scoped professional-services engagement, funded by the client. + +--- + +## Anti-Patterns + +1. **Single-Mode Fixation.** Founders who only compete ("my way or the highway") eventually find themselves surrounded by accommodators who have stopped offering honest input. Founders who only accommodate find their authority eroded. Founders who only avoid discover that suppressed conflicts metastasise. Mastery requires range. + +2. **Collaborating on Everything.** Collaboration is the most resource-intensive mode. Applying it to every disagreement -- including trivial ones -- produces meeting bloat, decision fatigue, and a reputation for indecisiveness. Reserve collaboration for issues where both parties' concerns are genuinely important and a creative solution is possible. + +3. **Confusing Compromising with Collaborating.** Compromise means both parties sacrifice something. Collaboration means neither does -- a genuinely new solution emerges that satisfies all concerns. Settling for compromise on a high-stakes issue often produces a mediocre outcome when a superior one was achievable. + +4. **Misreading Power Dynamics.** The TKI assumes roughly equal parties. When power is dramatically asymmetric -- a VC dictating terms to a first-time founder, for instance -- the model's prescriptions need adjustment. Competing against a more powerful party without leverage is not assertiveness; it is self-destruction. + +5. **Avoiding Avoidance When Avoidance Is Correct.** Some conflicts should be left alone. Not every disagreement is worth engaging. The anti-pattern is not avoidance itself but reflexive avoidance of issues that demand engagement. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Cofounder alignment | Conflicts at this stage are existential -- they determine whether the founding team survives. Collaborating mode is essential for vision and equity discussions; competing mode may be necessary to kill ideas that do not survive customer contact. | +| Early Traction | Role clarity conflicts | As the team grows beyond the founders, conflicts arise about ownership, process, and decision rights. The TKI helps founders choose when to assert authority and when to empower team members. | +| Growth | Cross-functional friction | Product vs. sales, engineering vs. design, speed vs. quality. These recurring tensions require sophisticated mode-switching. Growth-stage leaders need all five modes in active rotation. | +| Scale | Organisational conflict management | At scale, the founder cannot mediate every conflict. The task becomes teaching the TKI framework to managers throughout the organisation and building conflict-resolution capacity into the culture. | + +--- + +## Output Template + +```markdown +# Conflict Analysis: [Issue Description] + +## Parties & Positions +- **Party A ([Name/Role]):** [Their position and underlying concerns] +- **Party B ([Name/Role]):** [Their position and underlying concerns] + +## TKI Assessment +- **Party A's current mode:** [Competing / Collaborating / Compromising / Avoiding / Accommodating] +- **Party B's current mode:** [Mode] +- **Mode interaction dynamic:** [What happens when these two modes collide] + +## Recommended Approach +- **Optimal mode for this situation:** [Mode] +- **Rationale:** [Why this mode fits the stakes, relationship, and time constraints] +- **Fallback mode if primary fails:** [Mode] + +## Conversation Design +1. [Opening move] +2. [Key questions to surface underlying concerns] +3. [Process for generating options] +4. [Decision mechanism if parties cannot agree] + +## Anticipated Outcome +- **Best case:** [Description] +- **Most likely:** [Description] +- **Worst case and mitigation:** [Description] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](win-win-negotiation.md)** -- Collaborating mode in TKI maps directly to principled negotiation; both frameworks seek integrative solutions that satisfy all parties' interests. +- **[Radical Candor](radical-candor.md)** -- The "Challenge Directly" axis of Radical Candor corresponds to assertiveness in TKI; the "Care Personally" axis maps to cooperativeness. +- **[Tuckman's Team Stages](tuckman-team-stages.md)** -- The "Storming" stage is where TKI becomes most relevant; teams that navigate conflict effectively transition to Norming and Performing. +- **[Trust Equation](trust-equation.md)** -- Trust is the substrate on which collaborative conflict resolution depends; without it, parties default to competing or avoiding. +- **[Resolving People Conflict](../people/resolving-people-conflict.md)** -- Extends TKI's diagnostic framework into practical interpersonal conflict resolution techniques, including mediation approaches and de-escalation strategies. +- **[Negotiation Mindset and Self](../negotiation/negotiation-mindset-and-self.md)** -- The assertiveness-cooperativeness dimensions of TKI mirror the internal mindset calibration required before entering any negotiation or conflict conversation. diff --git a/plugins/foreman/content/skills/frameworks/tipping-point.md b/plugins/foreman/content/skills/frameworks/tipping-point.md new file mode 100644 index 0000000..ae9c150 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/tipping-point.md @@ -0,0 +1,190 @@ +--- +name: "tipping-point" +description: "Analyzes viral growth potential using Gladwell's Tipping Point + framework through three rules: the Law of the Few (Connectors, Mavens, + Salespeople), the Stickiness Factor, and the Power of Context. Use when + product growth is stubbornly linear despite high satisfaction, designing + launch strategies for organic adoption, engineering shareable product moments, + identifying key influencers in a target market, or diagnosing why a superior + product fails to spread." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - virality + - growth-strategy + - network-effects + - word-of-mouth + - adoption +related_skills: + - blue-ocean-strategy + - four-ps-marketing +author: "Fatih Guner" +--- + +# The Tipping Point + +In 1994, Hush Puppies sold roughly 30,000 pairs of shoes annually and the brand was effectively dead. Then a handful of hipsters in Manhattan's East Village started wearing them -- not because of any marketing campaign, but because the shoes were so uncool they had become cool. Within two years, sales hit 430,000 pairs. No advertising budget produced this result. No product redesign triggered it. A social epidemic did. Malcolm Gladwell's *The Tipping Point* (2000) anatomized this phenomenon -- the moment when an idea, trend, or behavior crosses a threshold and spreads like wildfire -- and in doing so handed entrepreneurs a vocabulary for understanding why some products ignite while others, equally worthy, smolder and die. + +--- + +## The Framework + +Gladwell identifies three governing rules of social epidemics. Each must be present for a tipping point to occur. The absence of any one can explain why a superior product fails to spread. + +### Rule 1: The Law of the Few + +Epidemics are driven by a disproportionately small number of exceptional people. Gladwell categorizes them into three archetypes: + +**Connectors** possess extraordinarily large social networks spanning multiple worlds -- technology, finance, art, media. They are the human equivalent of network hubs. When a Connector encounters your product and mentions it, the message reaches diverse, otherwise disconnected clusters simultaneously. + +**Mavens** are information specialists. They accumulate knowledge about products, prices, and places -- and they share it compulsively. Mavens do not merely know about your product; they understand how it compares to every alternative and will explain the differences to anyone who asks. They are the market's unpaid research department. + +**Salespeople** possess the charisma and persuasive skill to close the deal emotionally. Where Mavens provide the data, Salespeople provide the conviction. Their enthusiasm is contagious in the clinical sense of the word. + +The entrepreneurial implication is stark: identifying and activating even a few Connectors, Mavens, and Salespeople in your target market can matter more than a six-figure advertising budget. + +### Rule 2: The Stickiness Factor + +The message itself must be memorable enough to compel action. Gladwell draws on the history of *Sesame Street* and *Blue's Clues* to demonstrate that small, often counterintuitive adjustments to how information is presented can dramatically increase its stickiness. The lesson is not "make a better product" -- it is "make the product experience impossible to forget." + +Stickiness is not the same as quality. A technically superior product with a forgettable onboarding experience has low stickiness. A slightly inferior product with a moment of delight that users retell to friends has high stickiness. The tipping point demands both reach (the Few) and retention (Stickiness). + +### Rule 3: The Power of Context + +Human behavior is exquisitely sensitive to environmental conditions. Gladwell uses New York City's dramatic crime reduction in the 1990s -- driven partly by fixing broken windows and cleaning graffiti from subway cars -- to argue that context shapes behavior far more than character does. For entrepreneurs, this means the circumstances under which someone first encounters your product matter enormously. + +A brilliant app demonstrated at a crowded, noisy trade show booth may fail to tip. The same app discovered through a quiet recommendation from a trusted friend over coffee may become indispensable. Context is not a background variable; it is a primary lever. + +### The Epidemic Curve + +The tipping point itself occurs at the inflection where linear growth becomes exponential. Before the tip, effort feels disproportionate to results. After, results feel disproportionate to effort. Recognizing which side of the tipping point you currently occupy changes every strategic decision. + +``` +Adoption + ^ + | ___________ + | / + | / + | / <-- Tipping Point + | / + | ____________________/ + |__________/ + +-----------------------------------------> Time + [Pre-Tip: High effort, low results] [Post-Tip: Momentum carries] +``` + +--- + +## Prompts + +**Prompt 1 -- Epidemic Potential Audit:** +> Analyze my product/service [describe] for tipping point potential. Evaluate it against Gladwell's three rules: (1) Who are the Connectors, Mavens, and Salespeople in my target market of [describe market]? How could I identify and activate them? (2) What is the stickiness factor of my product -- what makes the experience memorable and retellable? (3) What contexts would be most favorable for first encounters with my product? Rate each dimension and identify the weakest link. + +**Prompt 2 -- Connector Identification Strategy:** +> Help me identify potential Connectors for my [product/service] in the [industry] space. A Connector spans multiple social worlds and has an unusually large, diverse network. Based on my target market of [describe], where would I find these people? What platforms, events, communities, or roles tend to produce Connectors? Design a strategy for reaching 10 Connectors in the next 90 days. + +**Prompt 3 -- Stickiness Redesign:** +> My product is [describe] and our current retention/engagement metrics are [share data]. Users try the product but don't come back or tell others about it. Using the Stickiness Factor principle, analyze my product experience for memorable moments, emotional peaks, and retellability. Suggest specific changes to make the experience sticky enough to spread through word of mouth. + +--- + +## Use Cases + +**Developer Tool Seeking Organic Adoption** + +An early-traction startup has built a code review tool that developers who try it genuinely love -- NPS sits at 72 -- but growth remains stubbornly linear at 5% month-over-month. A tipping point analysis reveals the problem: the tool lacks stickiness in its shareable moments. Developers enjoy using it but have no natural trigger to mention it to peers. The fix involves engineering a "share-worthy artifact" -- a beautiful, public code quality report that developers post to their repositories. This creates a visible signal that Connectors in the developer community notice and propagate. Growth triples within two quarters, and the majority of new users cite "saw it on a colleague's repo" as their discovery path. + +**Consumer Health App Pre-Launch** + +A growth-stage health-tech company preparing to launch a nutrition tracking app applies the three rules in reverse to design its launch strategy. First, they identify 50 fitness influencers who function as Connectors across health, tech, and lifestyle communities. Second, they engineer stickiness by designing a weekly "body insight" notification so surprising and personal that users screenshot and share it. Third, they optimize context by timing the launch for January -- when health motivation peaks and the context for trying new wellness tools is most favorable. The combination produces a 40x viral coefficient compared to their previous product launch. + +--- + +## Anti-Patterns + +- **Manufactured Virality.** Attempting to engineer a tipping point through paid influencer campaigns that simulate organic spread. Audiences detect inauthenticity rapidly. Gladwell's framework describes organic social dynamics, not paid amplification wearing an organic costume. The Connectors, Mavens, and Salespeople must genuinely believe in the product. + +- **Ignoring the Weakest Rule.** Founders who excel at one rule and neglect the others. A product with extraordinary stickiness but no Connector strategy stays trapped in a small enthusiast community. A product with powerful Connectors but low stickiness generates trial without retention -- the leaky bucket at scale. + +- **Premature Scaling of Promotion.** Pouring fuel on a fire that has not yet reached its tipping point. If the product lacks stickiness or the right Connectors have not been activated, amplifying reach through advertising merely accelerates the rate at which people try and forget your product. The evidence from failed viral campaigns is unambiguous: spending cannot substitute for the three rules. + +- **Confusing Tipping Points with Luck.** Dismissing the framework as describing unpredictable phenomena. While specific tipping points are hard to predict in timing, the conditions that enable them are identifiable and designable. Gladwell's contribution is precisely that epidemics follow discoverable patterns. + +- **Neglecting Context Entirely.** Assuming the product and the people are all that matter. Launching a B2B productivity tool during a company's busiest quarter, or introducing a luxury consumer product during a recession, violates the Power of Context regardless of how good the product is or how many Connectors endorse it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Identifying the Few | The priority is finding and activating Connectors, Mavens, and Salespeople; growth is still pre-tip and requires patience | +| Growth | Engineering stickiness | Product experience must be refined for maximum memorability and retellability; this is where most tipping points either happen or don't | +| Scale | Managing the epidemic | Post-tip, the challenge shifts to maintaining quality and culture while managing exponential growth; context management becomes operational | + +--- + +## Output Template + +```markdown +# Tipping Point Analysis: [Product/Company Name] + +**Date:** [Date] +**Current Growth Rate:** [MoM or relevant metric] +**Assessment:** [Pre-Tip / Approaching Tip / Post-Tip] + +## The Law of the Few + +### Connectors Identified +- [Name/Role/Reach]: [Why they matter] +- [Name/Role/Reach]: [Why they matter] + +### Mavens Identified +- [Name/Role/Expertise]: [Why they matter] + +### Salespeople Identified +- [Name/Role/Influence]: [Why they matter] + +### Activation Strategy +[How you plan to engage these individuals] + +## The Stickiness Factor + +- **Current stickiness score:** [High/Medium/Low] +- **Most memorable product moment:** [Describe] +- **Retellability test:** Can a user explain the value in one sentence? [Yes/No] +- **Recommended stickiness improvements:** + 1. [Change] + 2. [Change] + +## The Power of Context + +- **Optimal discovery context:** [Where/when/how users should first encounter the product] +- **Current context alignment:** [Strong/Weak] +- **Context improvements:** + 1. [Change] + +## Weakest Link +[Which of the three rules is currently the bottleneck, and what to do about it] + +## 90-Day Action Plan +1. [Action targeting the weakest rule] +2. [Action reinforcing the strongest rule] +3. [Measurement criteria for tipping point proximity] +``` + +--- + +## Related Skills + +- **[Four Ps of Marketing](four-ps-marketing.md)** -- The Promotion P must incorporate tipping point dynamics rather than relying solely on paid channels; product and place decisions also shape stickiness and context. +- **[Blue Ocean Strategy](blue-ocean-strategy.md)** -- Creating uncontested market space can serve as the contextual shock that triggers a tipping point by eliminating competitive noise. +- **[Cialdini's Influence](cialdini-influence.md)** -- Social proof and authority principles explain the psychological mechanisms through which Connectors, Mavens, and Salespeople propagate adoption. +- **[Net Promoter Score](net-promoter-score.md)** -- Promoters in the NPS framework are the quantifiable proxy for Gladwell's enthusiasts; high NPS signals a product with the advocacy base needed to reach a tipping point. +- **[Disruptive Innovation](disruptive-innovation.md)** -- Disruptive products often reach their tipping point by serving overlooked segments first, then crossing into mainstream adoption through Gladwell's epidemic dynamics. +- **[Connecting with People](../people/connecting-with-people.md)** -- Activating Connectors requires the interpersonal skill of building genuine relationships across diverse networks, not transactional outreach. diff --git a/plugins/foreman/content/skills/frameworks/trust-equation.md b/plugins/foreman/content/skills/frameworks/trust-equation.md new file mode 100644 index 0000000..0307aa5 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/trust-equation.md @@ -0,0 +1,255 @@ +--- +name: "trust-equation" +description: "Diagnoses and builds trust using Maister's Trust Equation: Trust = (Credibility + Reliability + Intimacy) / Self-Orientation. Evaluates each variable with evidence-based scoring and prescribes targeted improvements. Use when losing investor confidence, experiencing customer churn despite strong product, repairing damaged stakeholder relationships, preparing fundraising trust strategies, or auditing team trust dynamics." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - trust + - relationships + - credibility + - leadership + - sales +related_skills: + - radical-candor + - carnegie-win-friends + - cialdini-influence + - giving-feedback +author: "Fatih Guner" +--- + +# The Trust Equation + +``` + Credibility + Reliability + Intimacy +Trust = ────────────────────────────────────── + Self-Orientation +``` + +Four variables. One fraction. The most elegant decomposition of trust in the management literature. David Maister, Charles Green, and Robert Galford published this formula in *The Trusted Advisor* (2000), and its power lies in making the abstract concrete and the intuitive actionable. Trust is not a mystical quality some people possess and others lack. It is a function of four measurable, improvable variables -- three in the numerator, one in the denominator. Increase any numerator variable and trust rises. Increase the denominator and trust collapses, regardless of how strong the numerator is. The formula explains why brilliant consultants lose clients, why technically competent founders alienate investors, and why likeable managers fail to inspire confidence. It also prescribes, with unusual precision, exactly what to fix. + +--- + +## The Framework + +### The Numerator: Three Trust Builders + +#### Credibility: "I Can Trust What They Say" + +Credibility is the confidence that the other party knows what they are talking about. It operates on two dimensions: expertise (actual knowledge and skill) and communication of expertise (the ability to convey competence without arrogance). + +**Credibility markers:** +- Demonstrated domain knowledge +- Relevant credentials and track record +- Accuracy of prior statements and predictions +- Ability to say "I don't know" when appropriate -- paradoxically, admitting ignorance on peripheral topics increases perceived credibility on core topics +- Third-party validation (endorsements, publications, case studies) + +**How founders build credibility:** +- Publish original analysis of their market +- Reference specific data points and primary research in pitches +- Acknowledge the limits of their knowledge ("our hypothesis is X; we are testing it by doing Y") +- Build a track record of accurate forecasts in investor updates + +**How founders destroy credibility:** +- Overstating traction or market size +- Claiming expertise in domains where they lack it +- Failing to update stakeholders when prior predictions prove wrong +- Using jargon as a substitute for understanding + +#### Reliability: "I Can Trust What They Do" + +Reliability is the confidence that the other party will do what they say they will do. While credibility is about words, reliability is about actions repeated over time. It is the trust variable most dependent on consistency. + +**Reliability markers:** +- Promises kept -- especially small ones +- Deadlines met +- Follow-through on commitments made in meetings +- Predictable behaviour in varied circumstances +- Transparency about what can and cannot be delivered + +**How founders build reliability:** +- Under-promise and over-deliver systematically +- Send investor updates on the same day every month without exception +- Respond to communications within a predictable window +- Track and honour every commitment, no matter how minor ("I'll send you that article" matters) + +**How founders destroy reliability:** +- Missing self-imposed deadlines +- Changing direction frequently without explanation +- Making commitments in the enthusiasm of a meeting and failing to follow through +- Inconsistency between what is said in different contexts (telling the board one story and the team another) + +#### Intimacy: "I Can Trust Them With My Concerns" + +Intimacy is the confidence that sharing sensitive information -- concerns, fears, failures, uncertainties -- is safe. This is the most emotionally complex trust variable and the one most often neglected in professional contexts. + +**Intimacy markers:** +- Discretion with confidential information +- Emotional safety -- the other party does not judge, mock, or weaponise vulnerability +- Willingness to engage with feelings, not just facts +- Reciprocal vulnerability ("I'm worried about this too") +- Non-transactional concern for the other person's wellbeing + +**How founders build intimacy:** +- Share appropriate personal vulnerabilities ("this keeps me up at night") +- Honour confidences absolutely -- never use information shared in trust as leverage +- Acknowledge the emotional dimension of business decisions +- Remember and reference personal details about stakeholders +- Create psychological safety in team settings + +**How founders destroy intimacy:** +- Sharing confidential information with third parties +- Responding to vulnerability with judgment or dismissal +- Maintaining a purely transactional demeanour +- Using personal information strategically + +### The Denominator: The Trust Destroyer + +#### Self-Orientation: "Are They in This for Themselves?" + +Self-orientation is the degree to which the other party appears focused on their own interests rather than yours. It is the denominator -- the single variable with the power to nullify an otherwise strong trust position. A person can be highly credible, perfectly reliable, and genuinely intimate, but if they appear self-serving, trust evaporates. + +**Self-orientation signals:** +- Talking more than listening +- Redirecting conversations to their own interests +- Offering solutions before fully understanding the problem +- Name-dropping and status-signalling +- Visibly calculating "what's in it for me" in every interaction +- Rushing to close rather than ensuring genuine fit + +**How founders reduce self-orientation:** +- Listen before prescribing. In investor meetings, ask about the investor's thesis and portfolio before pitching. +- In sales conversations, spend the first third understanding the customer's situation before mentioning the product +- Refer prospects to competitors when the fit is genuinely poor +- Give useful advice and introductions with no expectation of reciprocation +- In team settings, credit others and share recognition generously + +**The denominator trap for founders:** Entrepreneurship selects for high self-orientation. Founders must be driven, ambitious, and focused on their company's success -- traits that can easily read as self-serving to investors, customers, and employees. The discipline is not reducing ambition but ensuring that interactions demonstrate genuine concern for the other party's interests alongside one's own. + +### The Mathematics of Trust + +The formula's structure reveals several non-obvious insights: + +1. **Self-orientation has disproportionate impact.** Because it is in the denominator, doubling self-orientation halves trust, regardless of numerator strength. Conversely, halving self-orientation doubles trust. No numerator improvement can compensate for high self-orientation. + +2. **Credibility alone is insufficient.** The brilliant but unreliable founder (high credibility, low reliability) is a common archetype -- visionary but untrustworthy. Investors learn to discount vision when execution track record is poor. + +3. **Reliability alone is insufficient.** The dependable but uninspiring operator (high reliability, low credibility, low intimacy) earns respect but not trust. People follow them because they deliver, not because they believe. + +4. **Intimacy is the most undervalued variable.** In professional contexts, intimacy is often dismissed as "soft." Yet it explains why people trust their accountant of twenty years over a more credentialed stranger, and why customers stick with a slightly inferior product sold by a vendor who understands their real concerns. + +5. **Trust is situation-specific.** A person may be highly trusted in one domain (technical decisions) and not in another (hiring). The equation should be applied per-context, not as a global score. + +--- + +## Prompts + +**Prompt 1 -- Trust Diagnostic:** +> Using the Trust Equation (T = (C + R + I) / S), assess my trustworthiness with a specific stakeholder. The stakeholder is [describe -- investor, cofounder, key customer, board member]. Rate myself on each variable (Credibility, Reliability, Intimacy, Self-Orientation) with evidence, not aspiration. Identify which variable is my weakest and design three specific actions to improve it over the next 30 days. + +**Prompt 2 -- Trust Repair:** +> I have lost trust with [describe the person and context]. The triggering event was [describe]. Using the Trust Equation, diagnose which variable(s) were damaged. Was it a credibility failure (I said something wrong), a reliability failure (I didn't do what I said), an intimacy failure (I betrayed a confidence or dismissed their concerns), or a self-orientation failure (I appeared to prioritise myself)? Then design a trust repair strategy targeting the specific variable(s) affected. + +**Prompt 3 -- Investor Trust Strategy:** +> I am preparing for a fundraising round. Using the Trust Equation, design a comprehensive trust-building strategy for investor relationships. For each variable (Credibility, Reliability, Intimacy, Self-Orientation), identify specific actions I should take before, during, and after investor meetings. My company: [describe stage, traction, prior fundraising history]. + +**Prompt 4 -- Team Trust Audit:** +> I manage a team of [size]. Using the Trust Equation, assess the current trust level within the team -- both trust in me as a leader and trust between team members. For each variable, identify observable indicators and potential improvement areas. Design a 90-day plan to increase team trust, with specific actions mapped to each variable. + +**Prompt 5 -- Customer Trust Analysis:** +> Analyse why we are losing customers to [competitor] despite having a superior product. Apply the Trust Equation to our customer relationships versus the competitor's. Rate both on Credibility, Reliability, Intimacy, and Self-Orientation from the customer's perspective. Identify which trust variable(s) the competitor outperforms us on and recommend specific changes to our customer success approach. + +--- + +## Use Cases + +**Idea-Stage Founder Seeking Pre-Seed Investment** +A first-time founder with no track record pitches angel investors and receives polite passes. Trust Equation diagnosis: Credibility is low (no prior exits, limited domain expertise), Reliability is unproven (no track record of delivering), Intimacy is minimal (investors do not know them), and Self-Orientation appears high (pitch is entirely about the founder's vision, not the investor's thesis). The remediation strategy targets each variable: build credibility through a published market analysis and customer interviews (demonstrating expertise); establish reliability by committing to monthly updates to interested angels even before an investment; develop intimacy by asking investors about their portfolio challenges and offering introductions; and reduce self-orientation by explicitly addressing how the investment fits the investor's thesis, not just the founder's ambition. Second fundraising attempt succeeds. + +**Growth-Stage Company with High Churn Despite Strong Product** +A B2B SaaS company with best-in-class technology loses 25% of customers annually. Trust Equation analysis from customer interviews reveals: Credibility is high (customers trust the product), Reliability is low (support response times are inconsistent, and promised features are frequently delayed), Intimacy is absent (customers feel like ticket numbers, not partners), and Self-Orientation is moderate (upsell pressure in every interaction). The intervention focuses on Reliability (SLAs with consequences for missed response times, public roadmap with delivery dates) and Intimacy (dedicated success managers, quarterly business reviews, proactive check-ins not tied to renewals). Churn drops to 12% in two quarters. + +**Scale-Stage CEO Navigating a Board Crisis** +A CEO learns that two board members are discussing their replacement after a missed quarterly target. Trust Equation diagnosis reveals the critical variable is Self-Orientation: the CEO has been perceived as optimising for their personal reputation (announcing ambitious targets publicly) rather than for honest company stewardship. Reliability is also damaged (the missed target follows two prior misses). The repair strategy: a board letter acknowledging the pattern, reforecasting conservatively, and committing to a reporting format that highlights risks alongside opportunities. The CEO explicitly addresses their own accountability, reducing perceived self-orientation. Within two board cycles, the replacement discussion dissipates. + +--- + +## Anti-Patterns + +1. **Optimising Only the Numerator.** Investing in credibility (more credentials, better pitches), reliability (better processes), and intimacy (more networking) while ignoring self-orientation. The denominator can single-handedly destroy trust. A founder who is brilliant, reliable, and personable but clearly in it only for themselves will not be trusted. + +2. **Confusing Reliability with Responsiveness.** Responding to every message within five minutes is not reliability; it is reactivity. Reliability means doing what you said you would do, when you said you would do it. An immediate response that fails to follow through is worse than a delayed response that delivers. + +3. **Performing Intimacy.** Sharing vulnerability strategically -- "I'll tell them about my struggles to seem human" -- is detectable and counterproductive. Performative vulnerability increases perceived self-orientation ("they're using vulnerability as a tactic"), which is the opposite of the intended effect. + +4. **Assuming Trust Transfers Across Domains.** A founder trusted for technical decisions assumes they are equally trusted for commercial ones. Trust is context-specific. The equation must be evaluated per-domain and per-stakeholder, not as a universal score. + +5. **Ignoring the Time Dimension.** Trust is built incrementally and destroyed instantly. A single reliability failure can undo months of consistent delivery. The equation captures a point-in-time assessment; the trajectory matters more than any single snapshot. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Credibility building from zero | With no track record, founders must build credibility through domain expertise, quality of thinking, and borrowed credibility (advisors, prior employers). Self-orientation must be visibly low -- investors are pattern-matching for coachability. | +| Validation | Reliability establishment | Validation is the trust-building phase: every commitment met, every update sent on time, every promise honoured. This is when the founder's reliability track record begins, and early impressions compound. | +| Early Traction | Intimacy with early customers | Early customers are taking a risk on an unproven company. Intimacy -- making them feel heard, safe, and valued -- determines whether they become advocates or cautionary tales. | +| Growth | Scaling trust across relationships | At growth, the founder cannot personally maintain trust with every stakeholder. Trust must be embedded in organisational practices: reliable processes, credible teams, customer intimacy at scale. | +| Scale | Institutional trust | At scale, trust becomes a brand attribute. The trust equation applies to the organisation, not just the founder: corporate credibility, operational reliability, customer intimacy, and perceived self-orientation (profit motive vs. customer mission). | + +--- + +## Output Template + +```markdown +# Trust Assessment: [Stakeholder/Relationship] + +## Trust Equation Score +| Variable | Rating (1-10) | Evidence | Improvement Priority | +|----------|---------------|----------|---------------------| +| Credibility (C) | [Score] | [What demonstrates or undermines credibility] | [High/Med/Low] | +| Reliability (R) | [Score] | [Track record of commitments kept/broken] | [High/Med/Low] | +| Intimacy (I) | [Score] | [Depth of personal connection and safety] | [High/Med/Low] | +| Self-Orientation (S) | [Score] | [Signals of self-interest vs. genuine concern] | [High/Med/Low] | + +## Calculated Trust Level +- Numerator (C + R + I): [Sum] +- Denominator (S): [Score] +- Trust Index: [Numerator / Denominator] +- Interpretation: [High / Moderate / Low / Critical] + +## Weakest Variable Analysis +- **Variable:** [The lowest-performing variable or highest self-orientation] +- **Root cause:** [Why this variable is weak] +- **Impact:** [How this weakness manifests in the relationship] + +## 30-Day Trust Building Plan +| Week | Action | Target Variable | Expected Impact | +|------|--------|----------------|-----------------| +| 1 | [Specific action] | [C/R/I/S] | [Expected change] | +| 2 | [Specific action] | [C/R/I/S] | [Expected change] | +| 3 | [Specific action] | [C/R/I/S] | [Expected change] | +| 4 | [Specific action] | [C/R/I/S] | [Expected change] | + +## Trust Maintenance Protocol +- [Ongoing practices to sustain trust] +``` + +--- + +## Related Skills + +- **[Radical Candor](radical-candor.md)** -- Radical Candor requires a trust foundation to function; the Trust Equation diagnoses whether that foundation exists and prescribes how to build it when it does not. +- **[Carnegie's Win Friends](carnegie-win-friends.md)** -- Carnegie's principles are, in Trust Equation terms, a systematic methodology for building all three numerator variables while minimising the denominator. +- **[Giving Feedback](giving-feedback.md)** -- The credibility and intimacy variables of the Trust Equation determine whether feedback is received as development or attack. +- **[Win-Win Negotiation](win-win-negotiation.md)** -- Trust is the lubricant of principled negotiation; high trust enables the vulnerability required to share interests, generate options, and defer to objective criteria. +- **[Connecting with People](../people/connecting-with-people.md)** -- Building the intimacy variable of the Trust Equation requires the relational skills of authentic connection, active listening, and genuine curiosity about others. +- **[Stoic Right Action](../stoic/stoic-right-action.md)** -- Consistently acting with integrity regardless of audience is the Stoic path to low self-orientation, the denominator variable that most powerfully determines trustworthiness. diff --git a/plugins/foreman/content/skills/frameworks/tuckman-team-stages.md b/plugins/foreman/content/skills/frameworks/tuckman-team-stages.md new file mode 100644 index 0000000..c253e2c --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/tuckman-team-stages.md @@ -0,0 +1,193 @@ +--- +name: "tuckman-team-stages" +description: "Diagnoses team development stage using Tuckman's five-phase model: Forming, Storming, Norming, Performing, and Adjourning. Prescribes stage-appropriate leadership actions and identifies progression barriers. Use when a new team is struggling to gel, conflict emerges after initial politeness, teams regress after adding new members, post-acquisition integration stalls, or leaders need to facilitate productive storming rather than suppress it." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - team-development + - team-dynamics + - group-process + - collaboration + - conflict-management +related_skills: + - belbin-team-roles + - hackman-enabling-conditions + - lewin-leadership-styles + - situational-leadership +author: "Fatih Guner" +--- + +# Tuckman's Stages of Team Development + +Everyone remembers their first week on a new team. The excessive politeness. The careful self-presentation. The unspoken questions -- who holds the real power here, whose opinion matters, where are the landmines? Then, some weeks later, the first real disagreement. Someone challenges someone else's idea a little too sharply. Alliances form. Resentments surface. And then -- if the team survives this phase -- something shifts. Roles clarify. Communication shortcuts develop. The team begins producing work that none of its members could have produced alone. + +Bruce Tuckman observed this pattern across hundreds of studies in 1965 and named it with four words that have since entered the management lexicon: Forming, Storming, Norming, Performing. He added a fifth stage, Adjourning, in 1977. The model is deceptively simple. Its power lies not in novelty but in normalizing what every team member instinctively feels: that conflict, confusion, and renegotiation are not signs of failure. They are the architecture of team maturation. The teams that skip the storm do not reach the performance. + +--- + +## The Framework + +Tuckman's model describes a sequential journey through five stages. While the sequence is predictable, the duration and intensity of each stage vary enormously depending on team composition, leadership, task complexity, and organizational context. + +### Stage 1: Forming + +**The experience:** Cautious optimism mixed with anxiety. Team members are polite, guarded, and oriented toward the leader for direction. Conversations are superficial. Everyone is assessing: the task, the other members, the norms, the power dynamics. + +**What's happening beneath the surface:** Individuals are testing boundaries without appearing to test them. Questions are asked obliquely. Disagreements are suppressed. Productivity is low because energy is directed toward social navigation rather than task execution. + +**Leadership need:** High direction, low delegation. The leader must provide structure, clarify goals, define roles, and establish initial working norms. This is Lewin's directive leadership and Hersey-Blanchard's S1 (Directing) in action. + +**Duration signal:** Forming ends when team members stop asking "Who are these people?" and start asking "How should we work together?" + +### Stage 2: Storming + +**The experience:** The politeness cracks. Disagreements emerge about goals, roles, working methods, and interpersonal dynamics. Subgroups form. Some members vie for influence. Others withdraw. Frustration rises. Morale typically dips. + +**What's happening beneath the surface:** This is the necessary -- and often painful -- process of establishing authentic relationships, honest communication, and real role differentiation. The artificial consensus of Forming is replaced by genuine negotiation. Teams that suppress Storming do not skip it; they delay it, often until the stakes are much higher. + +**Leadership need:** Facilitation, not suppression. The leader's job is to normalize conflict as productive, mediate without taking sides, and hold the team to its task when interpersonal friction threatens to become the primary focus. Attempting to eliminate Storming through authority ("Let's all just get along") drives it underground, where it corrodes trust invisibly. + +**Duration signal:** Storming ends when disagreements shift from personal ("You're wrong") to procedural ("We need a better process for this"). + +### Stage 3: Norming + +**The experience:** Cohesion forms. The team develops shared standards for how decisions are made, how conflicts are resolved, how work is reviewed, and how communication flows. In-group language and rituals appear. Members express genuine appreciation for each other's strengths. Trust deepens. + +**What's happening beneath the surface:** The team is writing its operating manual -- mostly unconsciously. Norms established in this phase persist for the team's lifetime unless deliberately renegotiated. Good norms (candid feedback, shared accountability) produce high performance. Bad norms (avoiding difficult conversations, deferring to the loudest voice) calcify into dysfunction. + +**Leadership need:** Coaching and reinforcement. The leader should explicitly name the good norms emerging and gently redirect the problematic ones. This is the highest-leverage moment for shaping team culture. + +**Duration signal:** Norming ends when the team begins operating on its norms automatically rather than consciously. + +### Stage 4: Performing + +**The experience:** The team is fully functional. Members work autonomously and interdependently with equal comfort. Decisions happen fluidly. Conflict is addressed quickly and constructively. The team solves problems at a level beyond the sum of individual capabilities. + +**What's happening beneath the surface:** Psychological safety is high. Role clarity is complete. Communication is efficient because shared context and trust eliminate the need for constant clarification. Energy flows toward the task rather than toward managing relationships or navigating politics. + +**Leadership need:** Delegation and obstacle removal. The leader's most valuable contribution is protecting the team from external disruptions and providing resources. Over-leading a Performing team is as destructive as under-leading a Forming one. + +**Duration signal:** Performing persists until a significant disruption -- a member departure, a scope change, a reorganization -- resets the team to an earlier stage. + +### Stage 5: Adjourning + +**The experience:** The team disbands upon completing its mission. Members may feel loss, anxiety about the next assignment, or satisfaction at what was accomplished. Often overlooked, this stage carries real emotional and organizational consequences. + +**What's happening beneath the surface:** Individuals are mourning the loss of a high-functioning team and potentially dreading the return to Forming with a new group. Knowledge and process insights developed during the team's life are at risk of being lost. + +**Leadership need:** Celebration, knowledge capture, and transitional support. The leader should facilitate a retrospective that captures what the team learned, celebrate the accomplishment publicly, and support members' transitions to their next teams. + +--- + +## Prompts + +**Prompt 1 -- Team Stage Diagnosis:** +> Based on the following description of my team's current dynamics, identify which Tuckman stage we're in and what leadership approach I should be using. Team context: [team size, how long they've worked together, recent changes]. Current behaviors: [describe communication patterns, conflict level, decision-making speed, quality of output, morale indicators]. Provide specific evidence for your stage assessment and actionable recommendations for what I should do differently. + +**Prompt 2 -- Storming Navigation Strategy:** +> My team is in the Storming stage. The specific conflicts are: [describe]. Some team members are withdrawing while others are becoming aggressive. I'm tempted to [describe your instinct -- e.g., "lay down the law," "reorganize the team," "avoid the conflict and hope it passes"]. Evaluate my instinct against Tuckman's model and design a facilitation approach that moves the team through Storming productively rather than suppressing or prolonging it. + +**Prompt 3 -- New Team Member Integration:** +> I'm adding [number] new members to an existing team of [size] that was previously in the [stage] stage. Using Tuckman's model, predict how this change will affect the team's stage progression. What regression should I expect? How can I accelerate the team's return to Performing while properly integrating the new members? Design an onboarding approach informed by Tuckman's stages. + +**Prompt 4 -- Multiple Team Stage Assessment:** +> I manage [number] teams across [function]. For each team, here's a brief description of their current dynamics: [describe each team]. Map each team to their Tuckman stage and prioritize which teams need the most leadership attention. For teams stuck in unproductive stages, recommend interventions. + +--- + +## Use Cases + +**Post-Acquisition Team Integration** + +A growth-stage startup acquires a smaller company and merges the two engineering teams. Leadership assumes the merged team will hit the ground running since both teams were previously Performing. Instead, the merged team resets to Forming -- new interpersonal dynamics, competing technical standards, unresolved questions about whose approach prevails. Within three weeks, Storming arrives with particular intensity because both subgroups carry the confidence and norms of formerly high-performing teams. Understanding Tuckman prevents the leadership from misinterpreting this friction as a "cultural mismatch" requiring organizational separation. Instead, they invest in facilitated workshops where the merged team explicitly negotiates new shared norms, accelerating the passage through Storming and into Norming. Within two months, the merged team achieves a Performing level that surpasses either predecessor team. + +**Remote Team Struggling with Permanent Forming** + +A validation-stage startup with a fully remote team of eight has been together for six months but never seems to gel. Conversations remain formal. Disagreements are avoided or handled in private DMs. Decision-making defaults to the founder on everything. A Tuckman analysis reveals the team is stuck in Forming. Remote work makes Storming harder to initiate -- there are fewer spontaneous interactions where genuine disagreement naturally surfaces. The founder deliberately creates structured opportunities for productive conflict: anonymous pre-meeting feedback, explicit "disagree and commit" decision protocols, and paired working sessions where team members must collaborate closely enough for real friction to emerge. The team enters Storming within two weeks -- uncomfortable but necessary. + +--- + +## Anti-Patterns + +- **Pathologizing Storming.** Interpreting conflict as evidence that the team has the wrong people rather than recognizing it as a necessary developmental stage. Leaders who reorganize teams at the first sign of Storming doom every subsequent team to the same premature dissolution. Storming is not the disease; it is the immune response. + +- **Performing Nostalgia After Disruption.** Expecting a team that was previously Performing to maintain that level after a significant change (new member, new scope, departing leader). Any material disruption resets the team to an earlier stage. Leaders who refuse to acknowledge the regression create frustration by demanding Performing-level output from a team that is re-Forming. + +- **Confusing Norming with Performing.** Mistaking team harmony for team effectiveness. A team in Norming may feel good -- relationships are warm, conflict is manageable, norms are settling -- but it is not yet producing its best work. Performing requires the norms to become invisible scaffolding, not a conscious preoccupation. Leaders who declare victory at Norming leave performance gains on the table. + +- **Forced Acceleration Through Stages.** Attempting to skip or compress stages through team-building exercises, personality assessments, or motivational speeches. Stages can be facilitated but not bypassed. A two-day offsite does not substitute for the organic process of trust development through shared work and resolved conflict. + +- **Ignoring Adjourning.** Disbanding teams without closure. Knowledge is lost. Emotional residue carries into the next team. High performers who bonded during Performing feel abandoned when the team is dissolved without acknowledgment. The cost of skipping Adjourning is paid in the next team's Forming stage, which begins with cynicism rather than cautious optimism. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founding team Forming/Storming | Co-founder relationships accelerate through stages rapidly due to intensity of early-stage work; unresolved Storming at this stage becomes existential | +| Validation | Rapid iteration through stages | Pivot decisions can reset the team to earlier stages; the team must learn to move through Forming-Storming quickly | +| Early Traction | Managing multiple concurrent stages | New hires push some relationships back to Forming while existing relationships may be at Performing; the leader manages a patchwork | +| Growth | Team proliferation | Multiple teams at different stages require different leadership approaches simultaneously; middle managers must understand the model | +| Scale | Institutional knowledge of team development | Tuckman becomes part of the organizational vocabulary; teams are supported through stages by design, not by accident | + +--- + +## Output Template + +```markdown +# Team Stage Assessment: [Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Time Together:** [Duration] +**Recent Changes:** [New members, departures, scope changes] + +## Current Stage: [Forming / Storming / Norming / Performing / Adjourning] + +### Evidence +- [Observable behavior 1 that supports this diagnosis] +- [Observable behavior 2] +- [Observable behavior 3] + +### Stage-Appropriate Leadership Actions +1. [Action aligned with current stage needs] +2. [Action aligned with current stage needs] +3. [Action aligned with current stage needs] + +## Progression Barriers +- [What is preventing the team from advancing to the next stage] +- [What intervention would address this barrier] + +## Team Health Indicators + +| Indicator | Current State | Expected at Current Stage | Concern? | +|-----------|--------------|--------------------------|----------| +| Conflict frequency | [Low/Medium/High] | [Expected level] | [Yes/No] | +| Decision speed | [Slow/Moderate/Fast] | [Expected level] | [Yes/No] | +| Psychological safety | [Low/Medium/High] | [Expected level] | [Yes/No] | +| Output quality | [Below/At/Above potential] | [Expected level] | [Yes/No] | + +## 30-Day Plan +- **Week 1:** [Focus area] +- **Week 2:** [Focus area] +- **Week 3-4:** [Focus area and reassessment] +``` + +--- + +## Related Skills + +- **[Belbin Team Roles](belbin-team-roles.md)** -- Belbin explains the composition of the team; Tuckman explains the developmental journey that composition undertakes, and role conflicts identified by Belbin often surface during the Storming stage. +- **[Hackman's Enabling Conditions](hackman-enabling-conditions.md)** -- Hackman's conditions create the structural prerequisites for a team to move through Tuckman's stages effectively; without them, teams stall in Forming or Storming. +- **[Lewin's Leadership Styles](lewin-leadership-styles.md)** -- The appropriate Lewin style shifts as the team progresses through Tuckman's stages: directive for Forming, facilitative for Storming, democratic for Norming and Performing. +- **[Situational Leadership](situational-leadership.md)** -- Hersey-Blanchard's model complements Tuckman by addressing individual development levels within the team's collective stage. +- **[Thomas-Kilmann Conflict](thomas-kilmann-conflict.md)** -- The Storming stage is where conflict modes matter most; TKI provides the diagnostic for choosing whether to compete, collaborate, compromise, avoid, or accommodate during team friction. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- The norms established during Tuckman's Norming stage become the team's operating culture; this skill provides the tools for shaping those norms deliberately. diff --git a/plugins/foreman/content/skills/frameworks/vuca-framework.md b/plugins/foreman/content/skills/frameworks/vuca-framework.md new file mode 100644 index 0000000..9f14df5 --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/vuca-framework.md @@ -0,0 +1,225 @@ +--- +name: "vuca-framework" +description: "Classifies unpredictable environments into four distinct dimensions -- Volatility, Uncertainty, Complexity, and Ambiguity -- each requiring a different strategic response: Vision, Understanding, Clarity, and Agility respectively. Use when navigating regulatory grey zones, responding to sudden competitive disruption, reducing operational complexity during scaling, designing rapid experimentation programmes under ambiguity, or building organizational resilience." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - strategy + - uncertainty + - risk-management + - adaptability + - scenario-planning + - resilience +related_skills: + - thinking-fast-and-slow + - psychological-safety + - growth-mindset + - emotional-intelligence +author: "Fatih Guner" +--- + +# VUCA Framework + +The acronym was born in the corridors of the U.S. Army War College in the late 1980s, coined to describe the strategic environment emerging after the Cold War's binary certainties dissolved. VUCA -- Volatility, Uncertainty, Complexity, Ambiguity -- was the military's attempt to name what had changed: the enemy was no longer a single, knowable superpower with predictable doctrine but a shifting landscape of asymmetric threats, non-state actors, and cascading second-order effects that defied traditional planning. By the mid-2000s, the business world had adopted the framework wholesale, recognising that the same structural forces transforming warfare were transforming markets. Bob Johansen of the Institute for the Future reframed VUCA's four threats as four matching leadership competencies -- Vision, Understanding, Clarity, Agility -- converting a diagnostic tool into a response framework. For entrepreneurs, who operate in environments where volatility is the baseline and uncertainty is the business model, VUCA provides something more valuable than a label for chaos: it provides a taxonomy that distinguishes between different types of unpredictability, each of which demands a different strategic response. + +--- + +## The Framework + +### The Four Dimensions of VUCA + +The critical insight of the VUCA framework is that "unpredictable" is not a single condition. Volatility, uncertainty, complexity, and ambiguity are distinct phenomena that overlap but require different responses. Conflating them -- treating all unpredictability as the same kind of problem -- produces strategies that address the wrong dimension. + +**V -- Volatility** + +The nature and speed of change. Volatile environments feature rapid, significant shifts whose individual direction may be unpredictable but whose general character (turbulence) is known. + +- **Characteristics:** Fast-moving changes, unstable but not necessarily complex, information is available but the situation shifts before it can be fully exploited +- **Startup examples:** Currency fluctuations for international SaaS, viral social media dynamics, sudden competitor launches, rapid regulatory changes +- **Response -- Vision:** Build slack into systems. Maintain reserves (cash, capacity, optionality). Invest in speed of response rather than prediction accuracy. A vision -- a clear, compelling picture of the destination -- provides the stable reference point that allows rapid tactical adaptation without strategic drift. + +**U -- Uncertainty** + +The lack of predictability about events and their outcomes. The basic structure of the environment is understood, but cause-and-effect relationships are unclear, making forecasting unreliable. + +- **Characteristics:** Known unknowns; information exists but is incomplete, conflicting, or hard to interpret; outcomes of actions are not reliably predictable +- **Startup examples:** Market sizing for genuinely novel products, customer adoption curves for disruptive technologies, outcome of regulatory review for new business models +- **Response -- Understanding:** Invest in information gathering: customer research, competitive intelligence, expert networks, scenario planning. The antidote to uncertainty is not certainty (which is unavailable) but structured understanding of the range of possible outcomes and their relative likelihoods. + +**C -- Complexity** + +The multiplicity of interconnected parts and variables. Complex environments feature many moving pieces whose interactions produce emergent, non-linear outcomes that are difficult to predict even with complete information. + +- **Characteristics:** Many interdependent variables, cause-and-effect relationships are discoverable but only in retrospect, small changes can produce disproportionate effects, expertise in one dimension does not guarantee understanding of the whole +- **Startup examples:** Multi-sided marketplace dynamics, supply chain management across geographies, navigating simultaneous regulatory frameworks, building products that integrate multiple technology stacks +- **Response -- Clarity:** Simplify where possible. Build modular systems that isolate complexity. Develop specialists who understand specific domains and generalists who understand the connections between them. Clarity -- the ability to make sense of the chaos -- requires not more information but better frameworks for interpreting the information already available. + +**A -- Ambiguity** + +The lack of clarity about meaning. In ambiguous environments, even the nature of the problem is unclear. The "unknown unknowns" reside here: threats and opportunities that cannot be anticipated because the categories for understanding them do not yet exist. + +- **Characteristics:** Causal relationships are completely unclear, no precedent exists, multiple interpretations of the same data are equally plausible, "What is actually happening?" is the defining question +- **Startup examples:** Entering entirely new market categories, technology paradigm shifts (AI, blockchain, quantum), customer behaviour in unprecedented conditions (pandemic, economic crisis), interpreting contradictory product-market fit signals +- **Response -- Agility:** Run small experiments rapidly. Test hypotheses with minimum resource commitment. Build organisational capacity for rapid learning and pivot. Agility is not the absence of planning but the willingness to abandon plans when new information renders them obsolete. + +### The VUCA Matrix: Diagnosis to Response + +| VUCA Dimension | Diagnostic Question | Strategic Response | Operational Priority | +|---------------|--------------------|--------------------|---------------------| +| **Volatility** | "How fast and dramatically is the situation changing?" | Build reserves and response speed | Cash buffers, agile operations, scenario readiness | +| **Uncertainty** | "How much do we know about what is likely to happen?" | Gather information and model scenarios | Customer research, competitive intelligence, expert advisory | +| **Complexity** | "How many interconnected variables are we managing?" | Simplify, modularise, develop expertise | Architecture redesign, specialist hiring, decision frameworks | +| **Ambiguity** | "Do we even understand the nature of the problem?" | Experiment rapidly and learn | MVPs, pilots, hypothesis testing, fast feedback loops | + +### Johansen's VUCA Prime (Response Framework) + +Bob Johansen proposed a matching response acronym: + +- **V**olatility is countered by **V**ision -- a clear sense of direction that remains stable while tactics adapt +- **U**ncertainty is countered by **U**nderstanding -- investing in information, scenario planning, and sense-making +- **C**omplexity is countered by **C**larity -- cutting through noise to identify the essential drivers and simplest viable responses +- **A**mbiguity is countered by **A**gility -- the organisational capacity to experiment, learn, and pivot rapidly + +The elegance of VUCA Prime is that it converts a diagnosis into a prescription: once a founder identifies which VUCA dimension dominates their current challenge, the response category is clear. + +--- + +## Prompts + +**Prompt 1 -- VUCA Situation Diagnosis:** +> Analyse the following situation through the VUCA framework: [describe the challenge -- market conditions, competitive dynamics, regulatory environment, internal uncertainty]. Rate each VUCA dimension (Volatility, Uncertainty, Complexity, Ambiguity) on a 1-10 scale with specific evidence. Identify which dimension is dominant and recommend the corresponding strategic response (Vision, Understanding, Clarity, or Agility). Be specific about what that response looks like operationally for a [stage] company in [sector]. + +**Prompt 2 -- Scenario Planning Under Uncertainty:** +> We face significant uncertainty about [describe uncertain factor -- e.g., "whether our enterprise sales cycle will be 3 months or 12 months," "whether the regulation will pass," "whether the market will consolidate"]. Build three scenarios (optimistic, base case, pessimistic) with specific assumptions, timeline, and implications for our business. For each scenario, recommend pre-committed actions (what we do regardless), contingent actions (what we do if specific signals appear), and the specific signals to monitor. Include a decision tree with trigger points. + +**Prompt 3 -- Complexity Reduction:** +> Our business has become operationally complex across these dimensions: [list -- e.g., "4 product lines, 3 customer segments, 2 geographies, compliance with 5 regulatory frameworks, dependencies on 8 third-party integrations"]. Map the complexity using the VUCA framework. Identify which elements are genuinely complex (interconnected, non-linear) versus merely complicated (many parts but predictable). Recommend a simplification strategy that reduces complexity without sacrificing strategic capability. Specifically, what should we stop doing, modularise, or outsource? + +**Prompt 4 -- Ambiguity Navigation:** +> We are experiencing genuine ambiguity about [describe -- e.g., "whether our product is in the HR-tech category or the productivity-tool category," "whether our declining engagement means product-market fit is eroding or we have an onboarding problem," "what the emergence of [technology] means for our business model"]. Design a rapid experimentation programme to reduce this ambiguity. For each experiment, define: hypothesis, method, minimum sample size, timeline, success/failure criteria, and the decision each result would trigger. + +--- + +## Use Cases + +**Validation-stage startup in a regulatory grey zone** + +A fintech startup is building a product that falls between existing regulatory categories. The regulatory environment is deeply ambiguous: the company does not know whether it will be classified as a bank, a money transmitter, or a technology platform -- and neither, apparently, do the regulators. The VUCA diagnosis reveals that ambiguity is the dominant dimension (the nature of the regulatory requirement is itself unclear), with moderate complexity (multiple regulatory bodies with overlapping jurisdictions) and low volatility (regulatory change is slow). The prescribed response is agility: rather than seeking definitive regulatory clarity before launching (which could take years), the company designs a minimum viable compliance architecture that satisfies the strictest plausible interpretation, launches in a limited geography as a regulatory pilot, and engages proactively with regulators to shape -- rather than react to -- the eventual classification. The experimental approach produces a regulatory relationship that yields favourable classification 14 months later. + +**Growth-stage marketplace hit by sudden competitor entry** + +A two-sided marketplace with strong regional traction discovers that a well-funded global competitor has entered its market with aggressive pricing. The VUCA diagnosis: high volatility (the competitive landscape has shifted rapidly), moderate uncertainty (the competitor's strategy is partially visible through their public actions but their long-term commitment to the market is unknown), and low ambiguity (the threat is clear). The prescribed response is vision plus understanding: the CEO articulates a clear vision for why the company's deep local knowledge and existing relationships create defensible value that a global entrant cannot replicate quickly (vision provides the stable reference point), while simultaneously investing in competitive intelligence to understand the entrant's strategy, burn rate, and likely persistence (understanding reduces uncertainty). The company avoids panic-driven price-matching -- which would destroy unit economics -- and instead doubles down on its differentiated value proposition while monitoring the competitor's signals for commitment or retreat. + +**Scale-stage company navigating AI disruption** + +A 1,000-person professional services firm recognises that generative AI threatens its core business model but cannot determine whether the threat is existential or merely transformative. The VUCA diagnosis: extreme ambiguity (no precedent for this type of disruption in professional services), high complexity (AI interacts with every service line, talent strategy, pricing model, and client relationship differently), moderate uncertainty (general direction is clear but timing and magnitude are not), and moderate volatility (the technology landscape shifts monthly). The response is multi-dimensional: agility (launch five internal AI pilot projects across different service lines), clarity (hire a Chief AI Officer to synthesise learnings and simplify the strategic narrative), understanding (commission research on client willingness to pay for AI-augmented services), and vision (the CEO articulates a ten-year vision that positions AI as an amplifier of human expertise rather than a replacement). The portfolio approach ensures the company learns rapidly without betting the organisation on a single interpretation of the disruption. + +--- + +## Anti-Patterns + +**1. Treating all uncertainty as the same.** The most common misapplication of any uncertainty framework is collapsing all four VUCA dimensions into a single sensation of "things are unpredictable." This produces generic responses ("we need to be more agile") that miss the specific nature of the challenge. A complexity problem requires clarity and simplification; throwing agility at it produces more chaos, not less. + +**2. Using VUCA as an excuse for strategic paralysis.** "The environment is too VUCA to plan" is a cop-out. VUCA does not argue against planning; it argues for a specific type of planning -- one that incorporates scenarios, maintains optionality, and builds adaptive capacity. The absence of a plan in a VUCA environment is not flexibility; it is drift. + +**3. Overreacting to volatility.** Volatile environments tempt leaders into constant strategic adjustment -- changing direction with every market shift. This produces the organisational equivalent of seasickness. The VUCA response to volatility is vision -- a stable strategic direction that absorbs tactical turbulence -- not continuous pivoting. + +**4. Seeking certainty before acting.** In genuinely uncertain or ambiguous environments, waiting for certainty is waiting forever. The VUCA framework explicitly prescribes action under uncertainty: structured experimentation, scenario planning, and information gathering. Certainty is the output of these processes, not their prerequisite. + +**5. Applying peacetime frameworks to wartime conditions.** Detailed five-year plans, lengthy approval processes, and consensus-driven decision-making are appropriate for low-VUCA environments. Importing them into high-VUCA conditions produces dangerously slow organisations. The VUCA assessment should trigger a corresponding adjustment in decision-making speed, approval thresholds, and planning horizons. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Navigating market and product ambiguity | The dominant VUCA dimension is typically ambiguity; the response is rapid experimentation to reduce unknown unknowns | +| Early Traction | Managing uncertainty about scalability and market dynamics | Uncertainty dominates as the company transitions from "does this work?" to "how big is this?"; scenario planning becomes essential | +| Growth | Handling increasing organisational complexity | Complexity emerges as the company adds products, markets, teams, and processes; the response is structural clarity and modularisation | +| Scale | Addressing volatility in mature competitive markets | At scale, volatility (competitive moves, market shifts, technological disruption) becomes the primary VUCA dimension; vision and reserves provide stability | + +The VUCA profile of a startup shifts systematically as it matures. At validation, nearly everything is ambiguous -- the customer, the product, the market, the model. The appropriate organisational posture is maximally experimental: small bets, rapid iteration, minimum viable everything. + +At early traction, ambiguity partially resolves (the product works for these customers in this way) but uncertainty increases (will it scale? how fast? what competition will emerge?). The posture shifts from pure experimentation to structured scenario planning and information gathering. + +At growth, complexity becomes the dominant challenge. The organisation itself generates complexity through departmentalisation, process proliferation, and multi-market operations. The response is relentless simplification and clarity: clear decision rights, modular architecture, and ruthless prioritisation. + +At scale, the company has built sufficient structure to manage complexity but faces volatility from external forces: competitive dynamics, technological disruption, regulatory change, macroeconomic shifts. The response is maintaining strategic vision as a stabilising force while building the reserves (cash, talent, optionality) to absorb shocks without panic-driven overreaction. + +--- + +## Output Template + +```markdown +# VUCA Assessment -- [Situation/Decision/Market] + +**Prepared for:** Board / Investors +**Date:** [Date] +**Scope:** [What is being assessed] + +## VUCA Profile + +| Dimension | Rating (1-10) | Key Evidence | Trend | +|-----------|--------------|-------------|-------| +| Volatility | [Score] | [Specific evidence of change speed/magnitude] | [Increasing/Stable/Decreasing] | +| Uncertainty | [Score] | [Specific knowledge gaps] | [Increasing/Stable/Decreasing] | +| Complexity | [Score] | [Interconnected variables identified] | [Increasing/Stable/Decreasing] | +| Ambiguity | [Score] | [Unresolvable interpretation gaps] | [Increasing/Stable/Decreasing] | + +**Dominant dimension:** [Which VUCA element is primary] +**Prescribed response category:** [Vision / Understanding / Clarity / Agility] + +## Scenario Analysis (for Uncertainty dimension) + +| Scenario | Probability | Key Assumptions | Business Impact | Pre-committed Actions | Contingent Actions | Trigger Signal | +|----------|------------|----------------|-----------------|----------------------|-------------------|----------------| +| Optimistic | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | +| Base | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | +| Pessimistic | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | + +## Complexity Map +[List interconnected variables and their key relationships] +- [Variable A] affects [Variable B] through [mechanism] +- [Variable C] and [Variable D] interact to produce [emergent effect] + +**Simplification opportunities:** [What can be decoupled, modularised, or eliminated] + +## Experimentation Programme (for Ambiguity dimension) + +| Experiment | Hypothesis | Method | Timeline | Success Criteria | Decision if Confirmed | Decision if Refuted | +|-----------|-----------|--------|----------|-----------------|----------------------|-------------------| +| [Exp 1] | [H1] | [Method] | [Weeks] | [Criteria] | [Action] | [Action] | + +## Strategic Response + +### Vision Statement (stable reference point) +[One paragraph articulating the stable strategic direction that absorbs tactical volatility] + +### Reserves and Buffers +- Cash runway buffer: [months beyond base-case need] +- Capacity buffer: [% of team not allocated to committed work] +- Strategic options maintained: [list of preserved optionalities] + +### Adaptive Mechanisms +- Decision review cadence: [frequency] +- Environmental scan cadence: [frequency] +- Pivot criteria: [specific conditions that would trigger strategic change] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](thinking-fast-and-slow.md)** -- High-VUCA environments amplify every cognitive bias Kahneman identified; the planning fallacy and overconfidence bias are particularly dangerous when uncertainty is extreme. +- **[Psychological Safety](psychological-safety.md)** -- Navigating VUCA requires organisations where people can surface problems, challenge assumptions, and admit uncertainty without penalty; Edmondson's framework provides the cultural infrastructure for VUCA response. +- **[Scenario Planning](scenario-planning.md)** -- Scenario planning is the primary strategic tool for the Uncertainty dimension of VUCA, constructing multiple plausible futures and stress-testing strategy against each. +- **[Emotional Intelligence](emotional-intelligence.md)** -- Leading through VUCA demands exceptional self-regulation (managing personal anxiety without transmitting it to the team) and empathy (recognising that uncertainty affects different people differently). +- **[Leader Resilience and Wellbeing](../leadership/leader-resilience-and-wellbeing.md)** -- Sustained VUCA exposure depletes leaders; resilience practices prevent the burnout and decision fatigue that high-unpredictability environments generate. +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- Stoic practices for enduring difficulty without reactivity provide the psychological foundation for leading through volatile and ambiguous conditions without panic. diff --git a/plugins/foreman/content/skills/frameworks/win-win-negotiation.md b/plugins/foreman/content/skills/frameworks/win-win-negotiation.md new file mode 100644 index 0000000..418e5ac --- /dev/null +++ b/plugins/foreman/content/skills/frameworks/win-win-negotiation.md @@ -0,0 +1,250 @@ +--- +name: "win-win-negotiation" +description: "Prepares and conducts negotiations using Fisher and Ury's principled negotiation method from Getting to Yes. Applies four principles: separate people from problems, focus on interests not positions, generate options for mutual gain, and insist on objective criteria. Use when negotiating term sheets, structuring enterprise contracts, resolving co-founder equity disputes, preparing for acquisition discussions, or debriefing completed negotiations for improvement." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - conflict-resolution + - partnerships + - deal-making + - strategy +related_skills: + - thomas-kilmann-conflict + - trust-equation + - cialdini-influence + - carnegie-win-friends +author: "Fatih Guner" +--- + +# Win-Win Negotiation + +In 2012, a promising SaaS startup negotiated its first enterprise contract with a Fortune 500 client. The client's procurement team demanded 60% off list price, exclusive feature development, and a three-year lock-in. The startup's founders, terrified of losing their flagship account, agreed to every term. Within eighteen months, the contract was haemorrhaging cash: the custom features consumed engineering bandwidth that starved the core product, the discounted price set a precedent that poisoned every subsequent deal, and the lock-in prevented the startup from pivoting when the market shifted. The client, meanwhile, received mediocre service from a vendor that resented the deal's terms. Both sides played to win. Both sides lost. This is the predictable wreckage of positional negotiation -- the distributive, zero-sum mindset that treats every deal as a fixed pie to be fought over. + +Roger Fisher and William Ury of the Harvard Negotiation Project proposed an alternative in *Getting to Yes* (1981). Their framework -- principled negotiation, commonly called win-win -- does not require parties to be altruistic, naive, or conflict-averse. It requires them to be intelligent about what they are actually negotiating for. + +--- + +## The Framework + +### The Four Principles of Principled Negotiation + +Fisher and Ury's framework rests on four core principles, each addressing a specific failure mode of conventional positional bargaining. + +#### Principle 1: Separate the People from the Problem + +Every negotiation involves two dimensions: the substantive issue (the deal terms) and the relationship (the people across the table). Positional bargaining entangles these dimensions -- a disagreement on price becomes a personal attack; a concession feels like weakness. Principled negotiation disentangles them explicitly. + +**In practice:** +- Acknowledge the emotional dimension of negotiation openly. "I understand this timeline is frustrating for your team" is not weakness; it is emotional intelligence that preserves the working relationship. +- Attack the problem, never the person. "The proposed payment terms create cash flow risk for us" rather than "Your terms are unreasonable." +- Build the relationship before and alongside the negotiation. The stronger the personal rapport, the easier it is to disagree on substance without damaging the relationship. +- Be hard on the problem, soft on the people. These are not contradictory -- they are complementary. + +**Founder trap:** First-time founders often conflate tough negotiation with personal conflict. They either cave to preserve the relationship (losing on substance) or fight aggressively to win (destroying the relationship). The framework demands both: preserve the relationship *and* fight for your interests. + +#### Principle 2: Focus on Interests, Not Positions + +Positions are what people *say* they want. Interests are *why* they want it. Two founders negotiating equity splits may take opposing positions (60/40 vs. 50/50), but their underlying interests -- fairness, recognition of contribution, protection against free-riding, financial security -- may be compatible. Positional bargaining fights over the numbers. Interest-based negotiation explores the motivations and discovers solutions that the positions obscure. + +**The interest-mapping exercise:** + +| Position (What they say) | Likely Interests (Why they want it) | Creative Options | +|--------------------------|-------------------------------------|-----------------| +| "We need 60% off list price" | Budget constraints, need to show procurement value, precedent concerns | Tiered pricing, volume commitment with graduated discounts, payment terms flexibility | +| "We need exclusive feature development" | Competitive differentiation, specific workflow requirement | Priority roadmap influence, co-development agreement, configuration rather than custom code | +| "We need a 3-year lock-in" | Avoid switching costs, ensure vendor commitment | Mutual commitment (vendor guarantees service levels), annual renewal with loyalty pricing | + +**Key question:** "Help me understand *why* this is important to you." This single question, asked genuinely, transforms more negotiations than any tactical manoeuvre. + +#### Principle 3: Generate Options for Mutual Gain + +Positional negotiation assumes a fixed pie: every dollar I get is a dollar you lose. Principled negotiation actively searches for ways to expand the pie before dividing it. The discipline is to generate options before evaluating them -- brainstorming without commitment, creating a menu of possibilities that neither party would have discovered alone. + +**Option generation techniques:** +- **Dovetailing interests:** Where your interests diverge, creative trades become possible. You value speed; they value thoroughness. You deliver a phased implementation -- fast initial deployment (satisfying your interest) with a comprehensive second phase (satisfying theirs). +- **Shared interests:** Identify what both parties want and build the deal around those points. Both want a long-term relationship? Structure the deal with renewal incentives rather than lock-in clauses. +- **Low-cost/high-value trades:** Things that cost you little but matter greatly to the other party. Case study rights may cost your customer nothing but provide enormous marketing value to you. Technical documentation may cost you a few engineering days but save them months of integration work. + +**The brainstorming protocol:** +1. State the problem clearly. "How do we structure a partnership that serves both our interests?" +2. Generate options without evaluation. No "that won't work" during brainstorming. +3. Expand the pie before dividing it. Ask: "What can we create together that neither of us can create alone?" +4. Evaluate against objective criteria (see Principle 4). + +#### Principle 4: Insist on Objective Criteria + +When interests conflict and creative options are exhausted, the remaining disagreements must be resolved by reference to objective standards rather than by who has more power. Market rates, industry benchmarks, independent valuations, legal precedent, scientific evidence, and professional norms all serve as objective criteria. + +**In practice:** +- "Let's look at what comparable SaaS companies charge for enterprise contracts at this scale" (market rates as criteria) +- "The standard vesting schedule in our market is four years with a one-year cliff" (industry norms as criteria) +- "We'd like to base the acquisition price on a multiple of trailing twelve months' revenue, using the median multiple for recent comparable transactions" (independent valuation as criteria) + +**Power of objective criteria:** +- They depersonalise the decision. Neither party is "giving in" -- both are deferring to external standards. +- They provide a face-saving mechanism. "I can't justify this to my board, but I can if we benchmark against market rates." +- They reduce the role of power asymmetry. A well-researched founder with strong objective criteria can negotiate effectively against a much more powerful counterparty. + +### BATNA: Your Source of Power + +Fisher and Ury introduced the concept of BATNA -- Best Alternative to a Negotiated Agreement. Your BATNA is what you will do if the current negotiation fails. The stronger your BATNA, the more confidently you can negotiate, because you have a credible walk-away. + +**BATNA development:** +- Before any negotiation, explicitly identify and strengthen your alternatives +- Never enter a negotiation with no alternative -- desperation is visible and exploitable +- Evaluate the other party's BATNA as well; understanding their alternatives reveals their negotiating constraints +- Improve your BATNA before the negotiation if possible (cultivate other investors, qualify other customers, develop backup plans) + +**The BATNA trap for founders:** Seed-stage founders often have weak BATNAs -- one interested investor, one potential enterprise client, one acquisition offer. This power asymmetry makes principled negotiation harder but more important, not less. Without strong alternatives, the framework's emphasis on objective criteria and creative options becomes the primary source of negotiating leverage. + +### The Negotiation Canvas + +A structured preparation tool combining all four principles: + +``` +┌──────────────────────────────────────────────────┐ +│ PREPARATION │ +├────────────────────┬─────────────────────────────┤ +│ OUR SIDE │ THEIR SIDE │ +├────────────────────┼─────────────────────────────┤ +│ Positions: │ Positions: │ +│ [What we ask for] │ [What they ask for] │ +├────────────────────┼─────────────────────────────┤ +│ Interests: │ Interests: │ +│ [Why we want it] │ [Why they want it] │ +├────────────────────┼─────────────────────────────┤ +│ BATNA: │ BATNA (estimated): │ +│ [Our alternatives] │ [Their alternatives] │ +├────────────────────┼─────────────────────────────┤ +│ Objective criteria │ Shared interests: │ +│ supporting our │ [What both sides want] │ +│ position: │ │ +├────────────────────┴─────────────────────────────┤ +│ OPTIONS FOR MUTUAL GAIN │ +│ 1. [Option] │ +│ 2. [Option] │ +│ 3. [Option] │ +└──────────────────────────────────────────────────┘ +``` + +--- + +## Prompts + +**Prompt 1 -- Negotiation Preparation:** +> I am about to negotiate [describe the deal -- fundraising, partnership, enterprise contract, acquisition, hire]. Using Fisher and Ury's principled negotiation framework, help me prepare. Walk me through: (1) identifying my interests vs. my positions, (2) hypothesising the other party's interests, (3) generating at least five options for mutual gain, (4) identifying relevant objective criteria, and (5) assessing both my BATNA and theirs. My context: [describe your company, stage, leverage, and the other party]. + +**Prompt 2 -- Mid-Negotiation Strategy:** +> I am in the middle of a negotiation that has stalled. The other party is insisting on [their position], and I need [my position]. Using the principled negotiation framework, help me: (1) identify the underlying interests behind both positions, (2) generate creative options we haven't considered, (3) find objective criteria that could break the impasse, and (4) assess whether I should continue negotiating or exercise my BATNA. Current situation: [describe in detail]. + +**Prompt 3 -- Term Sheet Analysis:** +> Analyse this term sheet using the principled negotiation framework: [paste or describe key terms]. For each term, identify: (1) the investor's likely interest behind the position, (2) our interest, (3) whether the term reflects fair objective criteria, and (4) alternative structures that could satisfy both parties' interests. Flag any terms where we should hold firm and any where creative alternatives exist. + +**Prompt 4 -- Negotiation Debrief:** +> I just completed a negotiation. Here is what happened: [describe the process and outcome]. Using Fisher and Ury's framework, debrief: (1) Where did I successfully separate people from problems? Where did I conflate them? (2) Where did I focus on interests vs. positions? Where did I get positional? (3) What creative options did I miss? (4) Where could objective criteria have strengthened my position? What will I do differently next time? + +**Prompt 5 -- Team Negotiation Alignment:** +> My team is entering a complex negotiation with [describe]. Multiple team members will participate. Using the principled negotiation framework, help me: (1) align the team on our interests (not just our positions), (2) assign roles (who leads which issues), (3) establish our BATNA and walk-away points, (4) prepare our option-generation strategy, and (5) define decision-making authority -- who can agree to what without escalation. + +--- + +## Use Cases + +**Validation-Stage Startup Negotiating First Pilot Contract** +A B2B startup has one potential pilot customer -- a mid-market company whose procurement team demands free usage during the pilot, ownership of any IP developed, and right of first refusal on pricing. The founders' positions: charge something, retain IP, offer no exclusivity. Interest-based analysis reveals: the customer's underlying interests are risk mitigation (free pilot), competitive advantage (IP ownership), and budget certainty (pricing control). Creative options: a paid pilot at 75% discount (risk reduction for the customer, cash flow for the startup), IP remains with the startup but the customer gets a most-favoured-nation pricing clause (competitive advantage without IP transfer), and a six-month price lock rather than right of first refusal (budget certainty without long-term constraint). The deal closes because both parties get what they actually need, not what they initially demanded. + +**Growth-Stage Company Negotiating Series B Terms** +A SaaS company with strong metrics receives a Series B term sheet with a full-ratchet anti-dilution provision, two board seats for the lead investor, and a participating preferred liquidation preference. Positional response: reject and counter. Principled response: map interests. The investor's interest behind full-ratchet: downside protection after a portfolio company previously cratered. Creative option: weighted-average anti-dilution (standard market term) plus a quarterly reporting package that gives the investor early warning of trouble -- addressing their actual concern (risk monitoring) rather than their stated position (maximum protection). Board seats interest: governance influence and information access. Option: one board seat plus observer seat plus monthly operating metrics -- influence without control. The term sheet evolves through three rounds of interest-based negotiation into a deal both parties consider fair, benchmarked against comparable transactions (objective criteria). + +**Scale-Stage Company Negotiating a Strategic Acquisition** +A 400-person company receives an acquisition offer. The acquirer's position: $200M all-stock. The target's position: $300M, majority cash. Traditional negotiation produces a stalemate. Principled negotiation reveals interests: the acquirer wants to preserve cash and ensure founder retention (stock aligns incentives). The target wants liquidity for shareholders and protection against acquirer stock decline. Creative options: $240M with 60% cash / 40% stock, with a collar on the stock component (protects against decline); an earn-out component tied to integration milestones (aligns incentives without requiring all-stock); and an accelerated vesting schedule for key employees (founder retention addressed separately from deal structure). Objective criteria: comparable transaction multiples, independent fairness opinion, and market-standard earn-out structures. The deal closes at terms both boards approve. + +--- + +## Anti-Patterns + +1. **Win-Win as Capitulation.** Misinterpreting the framework as requiring equal concessions or avoiding tough stances. Principled negotiation is not about being nice. It is about being effective. Sometimes your interests are non-negotiable, and the framework supports holding firm -- but on interests, not positions, and justified by objective criteria, not stubbornness. + +2. **Positional Bargaining in Disguise.** Calling a negotiation "principled" while actually anchoring on positions, making incremental concessions, and treating the process as a contest. True interest-based negotiation requires genuine curiosity about the other party's needs, not tactical reframing of your demands. + +3. **Neglecting BATNA Development.** Entering a negotiation without a viable alternative and hoping the framework compensates. Principled negotiation without BATNA is a philosophy without leverage. The framework works best when both parties have credible alternatives, because the deal must genuinely be better than each party's next-best option. + +4. **Premature Option Evaluation.** Brainstorming creative options and immediately critiquing them ("that won't work because..."). The power of option generation lies in separating inventing from deciding. Premature evaluation kills creative solutions. + +5. **Ignoring Cultural Negotiation Norms.** Fisher and Ury's framework originated in American negotiation culture, which values directness, individual decision-making, and efficiency. In cultures that prioritise relationship-building (Japan, Middle East), hierarchical decision-making (Korea, many European firms), or indirect communication (much of Southeast Asia), the framework's application requires significant cultural adaptation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | First deals with weak BATNA | Founders negotiating from a position of scarcity must rely heavily on objective criteria and creative options to compensate for weak alternatives. Every early deal sets precedents -- negotiate carefully. | +| Early Traction | Hiring and partnership negotiations | As the company establishes itself, negotiations multiply: key hires negotiating equity, early partners negotiating terms, landlords negotiating leases. The framework scales to cover them all. | +| Growth | Fundraising and enterprise sales | Growth-stage negotiations are higher-stakes and more complex. Multiple stakeholders on each side, longer timelines, and more variables create opportunities for creative option generation. | +| Scale | M&A, strategic partnerships, complex multi-party deals | At scale, negotiations involve legal teams, investment bankers, and board approval. The framework's emphasis on interests over positions prevents deal teams from getting lost in positional complexity. | + +--- + +## Output Template + +```markdown +# Negotiation Preparation: [Deal/Context] + +## Parties +- **Our side:** [Who is at the table, decision-making authority] +- **Their side:** [Who is at the table, decision-making authority] + +## Position vs. Interest Map +| Issue | Our Position | Our Interest | Their Position (Known/Estimated) | Their Interest (Estimated) | +|-------|-------------|-------------|--------------------------------|--------------------------| +| [Issue 1] | [What we ask] | [Why] | [What they ask] | [Why] | +| [Issue 2] | [What we ask] | [Why] | [What they ask] | [Why] | + +## BATNA Assessment +- **Our BATNA:** [Best alternative if this deal fails] +- **Our BATNA quality:** [Strong / Moderate / Weak] +- **Their BATNA (estimated):** [Their likely alternatives] +- **Reservation point:** [The minimum terms we would accept] + +## Options for Mutual Gain +1. [Creative option that serves both parties' interests] +2. [Creative option] +3. [Creative option] +4. [Creative option] +5. [Creative option] + +## Objective Criteria +- [Market benchmark] +- [Industry standard] +- [Comparable transaction] +- [Independent valuation or expert opinion] + +## Negotiation Sequence +1. **Opening:** [Relationship-building, agenda setting] +2. **Interest exploration:** [Questions to surface their interests] +3. **Option generation:** [Joint brainstorming process] +4. **Evaluation against criteria:** [How to compare options] +5. **Agreement or BATNA:** [Decision framework] + +## Walk-Away Conditions +- [Specific conditions under which we exercise our BATNA] +``` + +--- + +## Related Skills + +- **[Thomas-Kilmann Conflict](thomas-kilmann-conflict.md)** -- TKI's "collaborating" mode is the conflict-handling equivalent of principled negotiation; both frameworks seek integrative solutions rather than distributive compromise. +- **[Trust Equation](trust-equation.md)** -- Trust is the lubricant of principled negotiation; high trust enables the vulnerability required to share interests, generate options, and defer to objective criteria. +- **[Cialdini's Influence](cialdini-influence.md)** -- Influence principles inform negotiation tactics, particularly reciprocity (first concessions) and commitment (incremental agreement-building). +- **[Carnegie's Win Friends](carnegie-win-friends.md)** -- Carnegie's principle of "arousing an eager want" maps directly to Fisher and Ury's emphasis on understanding and serving the other party's interests. +- **[Negotiation Game Theory](../game-theory/negotiation-game-theory.md)** -- Game theory formalises the strategic dynamics underlying principled negotiation, revealing when cooperative strategies dominate competitive ones mathematically. +- **[Cooperative Negotiation](../negotiation/cooperative-negotiation.md)** -- Provides complementary tactics and frameworks for the interest-based, option-generating approach that Fisher and Ury prescribe as the core of principled negotiation. diff --git a/plugins/foreman/content/skills/game-theory/coalition-and-partnership-games.md b/plugins/foreman/content/skills/game-theory/coalition-and-partnership-games.md new file mode 100644 index 0000000..f527c60 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/coalition-and-partnership-games.md @@ -0,0 +1,254 @@ +--- +name: "coalition-and-partnership-games" +description: "Analyses partnership structures, cofounder equity splits, and alliance formation using coalitional game theory. Applies Shapley Value for contribution-based allocation, imputation sets and the core for stability testing, and coalition disintegration models to predict breakups. Use when splitting equity among cofounders, structuring joint ventures, negotiating alliance terms, evaluating vendor partnerships, diagnosing why a partnership is failing, or determining fair cost-sharing among unequal participants." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - coalitions + - partnerships + - equity-split + - shapley-value + - alliances + - cofounder + - game-theory + - fair-allocation +related_skills: + - negotiation-game-theory + - evolutionary-strategy + - win-win-negotiation + - trust-equation + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +# Coalition and Partnership Games + +Three cofounders sit across a table, dividing equity. The technical founder built the prototype. The business founder brought the first paying customer. The third contributed the initial capital. They settle on equal thirds -- the path of least resistance, the conflict-avoidant default, and, according to the mathematics of cooperative game theory, almost certainly the wrong answer. Equal splits assume equal contribution, equal replaceability, and equal outside options. These conditions virtually never hold. The Shapley Value, developed by Lloyd Shapley in 1953 (work that earned him the Nobel Prize in Economics in 2012), offers a mathematically rigorous alternative: allocate based on each player's average marginal contribution across every possible ordering of the coalition. The calculation is not intuitive, but its logic is unassailable -- and it transforms equity conversations from emotional negotiations into structured analyses. + +--- + +## The Framework + +### Coalitions: Why They Form and Why They Matter + +A coalition is any group of players who agree to coordinate their actions for mutual benefit. In business, coalitions take many forms: cofounder teams, strategic alliances, joint ventures, supplier consortia, investor syndicates. The fundamental question is always the same -- does the group produce more value together than its members would separately? + +Game theory distinguishes three types of coalitions based on their value properties: + +| Coalition Type | Test | Business Meaning | Implication | +|---------------|------|------------------|-------------| +| **Superadditive** | Combined value exceeds sum of individual values | The partnership creates genuine synergy | Coalition should form; the question is how to split the surplus | +| **Additive** | Combined value equals sum of individual values | No synergy; partnership is neutral | No compelling reason to partner; equal split is the only stable allocation | +| **Subadditive** | Combined value is less than sum of individual values | Partnership destroys value (internal conflict, coordination overhead) | Coalition should not form; members are better off alone | + +The first task in any partnership analysis is determining which type applies. Many failed partnerships are subadditive coalitions that should never have formed -- the coordination costs and internal friction exceed whatever synergies the partners imagined. + +### The Grand Coalition and Sub-Coalitions + +The **grand coalition** includes all players. A three-person startup where all cofounders work together is a grand coalition. Sub-coalitions are any subset: two of the three cofounders forming a side agreement, or a faction within a larger alliance. + +The grand coalition is desirable when it is superadditive -- when everyone working together produces more than any combination of sub-groups. But its stability depends on whether any sub-coalition can credibly defect and do better on its own. This is where the mathematics becomes practically important. + +Consider a five-person founding team evaluating whether to bring in all five partners. The potential annual payoff of the full team is $1M. Two of the five discover they can generate $450K on their own. The remaining three can only produce $250K without the departing pair. The grand coalition's $1M is less than $450K + $250K = $700K... wait. That arithmetic actually favours the grand coalition. But the two-person sub-coalition's $450K exceeds the $400K they would receive under equal distribution ($200K each vs. $225K each). The defection is rational for those two players, even though it destroys collective value. This is the core tension of coalitional game theory. + +### The Shapley Value: Fair Allocation Based on Marginal Contribution + +The Shapley Value answers the question: given that the coalition has formed, what is the fair share for each player? + +The principle is elegant. Consider every possible order in which players might join the coalition. For each ordering, measure what each player adds when they arrive -- their marginal contribution at that point. Average each player's marginal contribution across all possible orderings. That average is their Shapley Value. + +**A practical cofounder example:** + +Three cofounders: Alice (technical), Bob (business), Carol (capital). + +Value of each individual alone: +- Alice alone: $0 (can build product but has no distribution or funding) +- Bob alone: $0 (can sell but has no product or funding) +- Carol alone: $0 (has capital but no product or sales ability) + +Value of pairs: +- Alice + Bob: $200K (product + distribution, but bootstrapped) +- Alice + Carol: $150K (funded product, but no go-to-market) +- Bob + Carol: $50K (funded sales team, but no product to sell) + +Value of all three: $500K + +There are six possible orderings (3! = 6). For each, track what each person adds: + +| Order | Alice's Contribution | Bob's Contribution | Carol's Contribution | +|-------|--------------------|--------------------|---------------------| +| A, B, C | $0 (first, alone) | $200K ($200K - $0) | $300K ($500K - $200K) | +| A, C, B | $0 | $350K ($500K - $150K) | $150K ($150K - $0) | +| B, A, C | $200K ($200K - $0) | $0 (first, alone) | $300K ($500K - $200K) | +| B, C, A | $450K ($500K - $50K) | $0 (first, alone) | $50K ($50K - $0) | +| C, A, B | $150K ($150K - $0) | $350K ($500K - $150K) | $0 (first, alone) | +| C, B, A | $450K ($500K - $50K) | $50K ($50K - $0) | $0 (first, alone) | +| **Average** | **$208.3K (41.7%)** | **$158.3K (31.7%)** | **$133.3K (26.7%)** | + +The Shapley Value suggests a 42/32/27 split -- not equal thirds. Alice's technical contribution is most critical to value creation (she appears in the highest-value pairings), so she receives the largest share. The mathematics captures what intuition often misses: contribution is not about effort or hours; it is about marginal impact on the coalition's output. + +### Imputation, the Core, and Stability + +An allocation is **individually rational** if every player receives at least what they could earn alone. An allocation is **collectively rational** if the total allocation equals the total coalition value (no surplus left on the table). Any allocation meeting both conditions is called an **imputation**. + +But not every imputation keeps the coalition stable. A sub-coalition might still defect if its members collectively receive less than what they could generate on their own. The **core** is the set of allocations where no sub-coalition has incentive to break away. + +**The stability test** for any proposed equity split: + +For every possible sub-group, verify that the group's combined allocation from the grand coalition exceeds what they could earn independently. If any sub-group is underpaid relative to its standalone value, the coalition is unstable. + +In the example above, the core requires: +- Alice + Bob together receive at least $200K (their pair value). Shapley gives them $366.6K. Satisfied. +- Alice + Carol together receive at least $150K. Shapley gives them $341.6K. Satisfied. +- Bob + Carol together receive at least $50K. Shapley gives them $291.6K. Satisfied. + +The Shapley allocation sits within the core -- it is stable. Not every allocation method produces this result. + +### The Landlord-Tenant Dynamic and Asymmetric Pairing + +In many business relationships, one party holds a scarce, essential resource (the "landlord") while multiple parties hold a common, substitutable resource (the "tenants"). The landlord-tenant dynamic from cooperative game theory reveals a stark truth: when one side is essential and the other is replaceable, the essential party captures most of the value. + +A startup with proprietary technology (the landlord) negotiating with multiple potential distribution partners (the tenants) holds enormous leverage -- not because of negotiation skill, but because of structural position. If the tenants cannot form a sub-coalition (a united front), the landlord can play them against each other, driving their individual allocations toward zero. + +The counter-strategy is tenant coalition formation: potential partners banding together to negotiate collectively. This shifts the game from a one-vs-many asymmetry to a more balanced bilateral negotiation. Trade unions, purchasing cooperatives, and industry consortia all represent tenant coalitions responding to landlord-tenant asymmetry. + +### Why Coalitions Disintegrate + +Coalition disintegration stems from two forces: + +**Individual rationality undermining collective outcomes.** The Prisoner's Dilemma applies within coalitions: each member's individually rational choice (maximise personal payoff) leads to collectively worse outcomes. A cofounder who secretly negotiates a side deal, a partner who free-rides on shared resources, an alliance member who shares proprietary information selectively -- these are all defections driven by individual rationality. + +**Small coalition rationality.** Sub-groups discover they can do better alone. Two of five cofounders realise their combined skills command a higher market value than their proportional share of the grand coalition. A regional alliance member discovers it can form a more profitable bilateral deal. The grand coalition fractures not because of betrayal, but because of rational calculation. + +**Confrontation and counter-confrontation cycles.** An allocation that satisfies one sub-group often dissatisfies another. Player 1 proposes a reallocation that benefits Players 1 and 3 at the expense of Player 2. Player 2 responds with a counter-proposal benefiting 2 and 3. The cycle continues until either a stable allocation is found or the coalition collapses. + +--- + +## Prompts + +**Prompt 1 -- Cofounder Equity Split:** +> We are [number] cofounders starting [describe company]. Each founder's contribution is: [list each founder and their specific contribution -- technical skills, business relationships, capital, domain expertise, time commitment]. Using the Shapley Value approach, help me calculate a fair equity split. For each founder, estimate their standalone value, the value of every possible pair and sub-group, and the full team value. Then compute each founder's average marginal contribution across all orderings to determine the mathematically fair allocation. + +**Prompt 2 -- Partnership Stability Audit:** +> We have an existing partnership among [describe parties and structure]. The current allocation of value/equity/revenue is [describe current split]. Each party's standalone alternative is approximately [describe what each could earn alone]. Using the core stability test from coalitional game theory, evaluate whether any sub-coalition of our partners could credibly defect. Identify which groups are underpaid relative to their coalition value and recommend reallocation to stabilise the partnership. + +**Prompt 3 -- Alliance Formation Decision:** +> We are considering forming an alliance with [describe potential partners]. Our standalone annual value is [amount]. The proposed alliance would generate [combined amount]. Using coalitional game theory, help me determine: (1) Is this coalition superadditive, additive, or subadditive? (2) What is the fair split using Shapley Value principles? (3) Are there any sub-coalitions that could destabilise the alliance? (4) What structural mechanisms (contracts, vesting, governance) should we implement to prevent rational defection? + +**Prompt 4 -- Diagnosing Partnership Failure:** +> Our partnership is showing signs of strain. The parties involved are [describe]. The original value allocation was [describe]. Recent developments: [describe tensions]. Using the coalition disintegration framework, help me diagnose: Is this individual rationality undermining collective outcomes? Is a sub-coalition forming? Is the current allocation outside the core? What reallocation or structural change could restabilise the coalition? + +--- + +## Use Cases + +**Idea-Stage: Three Cofounders Splitting Equity** + +A machine learning engineer, a healthcare-industry sales executive, and a physician with domain expertise decide to build a health-tech startup. The engineer argues for equal thirds. The sales executive -- who already has warm introductions to three hospital systems -- believes her contribution warrants more. The physician has the clinical credibility that no regulatory pathway can succeed without. + +Applying the Shapley Value framework, they estimate standalone and combination values. The engineer alone has near-zero startup value (ML skills are available for hire). The sales executive alone can consult but not build a product. The physician alone lacks both technical and commercial capability. But the engineer-physician pair can build a credible prototype worth $300K in grant funding. The sales-physician pair can secure pilot agreements worth $200K. The engineer-sales pair can build and distribute a generic product worth $150K. The full trio can raise a $2M seed round and secure three hospital pilots. + +The Shapley calculation produces a 38/33/29 split favouring the engineer (whose technical contribution amplifies every combination most). The conversation shifts from "who deserves what" to "who contributes what marginal value" -- a far less emotional framework. + +**Growth-Stage: Vendor Alliance Showing Cracks** + +A SaaS company formed a three-way integration alliance with a CRM platform and a payments processor. The original revenue-share was equal thirds. Two years later, the CRM platform's customer base has grown fivefold, making it the primary distribution channel. The payments processor's technology has become commoditised, with four viable alternatives. The SaaS company's product remains differentiated but is no longer the only option in its category. + +The CRM platform's standalone value to the alliance has increased dramatically; the payments processor's has decreased. The current equal-thirds allocation no longer sits within the core -- the CRM platform could form a bilateral deal with either partner and capture more value. The alliance is unstable. + +Resolution requires reallocation: increasing the CRM platform's share to reflect its new marginal contribution, or restructuring the alliance with contractual lock-in provisions that make defection costly. Without adjustment, the CRM platform will rationally exit the coalition within one to two renewal cycles. + +**Scale-Stage: Acquisition Consortium** + +Three mid-market companies consider pooling resources to jointly acquire a competitor. Company A contributes $20M in capital, Company B contributes distribution infrastructure worth $15M, and Company C contributes the management team that will run the acquired entity. The acquisition target generates $50M in annual revenue. Alone, none can complete the acquisition. The Shapley Value framework determines that Company A (capital) receives the largest share because capital is the bottleneck -- without it, neither distribution nor management creates value. The framework also reveals that Companies B and C should form a sub-coalition agreement to prevent Company A from renegotiating terms post-acquisition, when the capital has already been deployed and A's leverage diminishes. + +--- + +## Anti-Patterns + +1. **The Equal Split Reflex.** Defaulting to equal allocation because it avoids difficult conversations. Equal splits are mathematically correct only when all players have identical standalone values, identical marginal contributions in every sub-coalition, and identical outside options. This combination is so rare that assuming it is almost always a form of intellectual laziness disguised as fairness. + +2. **Ignoring Standalone Value.** Evaluating contributions only within the context of the coalition, without assessing what each player could achieve independently. A cofounder who can earn $300K as a senior engineer at a major technology company has a high standalone value. Their participation in a startup that pays them nothing for two years represents a real sacrifice -- one that the equity allocation should reflect. + +3. **Static Allocation in a Dynamic Game.** Setting equity or revenue-sharing terms at formation and never revisiting them. Marginal contributions change as the company evolves. The technical founder's contribution is enormous at the prototype stage and may diminish relative to the sales founder's contribution at growth stage. Vesting schedules and periodic reallocation mechanisms address this, but only if the coalition anticipates the problem at formation. + +4. **Conflating Effort with Marginal Contribution.** A partner who works 80-hour weeks on activities that any hired employee could perform has high effort but low marginal contribution. The Shapley Value measures what the coalition loses if a specific player is removed -- not how many hours they logged. This distinction is essential and frequently misunderstood. + +5. **Neglecting Sub-Coalition Threats.** Assuming the grand coalition is stable because everyone agreed to the terms. Rational players continuously evaluate their alternatives. If two of four partners discover they generate 70% of value but receive 50% of allocation, the sub-coalition threat is real regardless of what the partnership agreement says. Contracts slow defection; they do not eliminate the incentive. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder equity allocation | Standalone values are speculative and pair values are hypothetical. Use the Shapley framework to structure the conversation, but acknowledge that estimates are rough. Build in reallocation mechanisms (vesting, milestone-based adjustments) to account for uncertainty. | +| Validation | Early partnership structuring | First external partnerships form: pilot customers, technology partners, advisors. Apply the superadditivity test before committing -- many early partnerships are additive at best. Only partner when the combined value genuinely exceeds the sum of parts. | +| Early Traction | Revenue-sharing and alliance management | Revenue begins flowing, making marginal contributions measurable rather than estimated. Revisit initial allocations against actual data. The core stability test becomes practical: identify whether any partner is receiving less than their demonstrated contribution. | +| Growth | Complex multi-party alliances | Coalitions expand to include investors, distribution partners, integration partners. Sub-coalition dynamics become critical. Monitor for small coalition rationality -- subgroups that might defect. Structural safeguards (exclusivity clauses, joint IP, shared infrastructure) increase switching costs. | +| Scale | M&A, consortia, and ecosystem governance | The company becomes a coalition of coalitions. Acquisition targets, joint ventures, and industry consortia all involve nested coalition dynamics. Shapley-based allocation principles inform earnout structures, joint venture governance, and consortium voting rights. | + +--- + +## Output Template + +```markdown +# Coalition Analysis: [Partnership/Alliance Name] + +## Players and Standalone Values +| Player | Role/Contribution | Estimated Standalone Value | Outside Option | +|--------|-------------------|---------------------------|----------------| +| [Player 1] | [Description] | [Value alone] | [Best alternative] | +| [Player 2] | [Description] | [Value alone] | [Best alternative] | +| [Player 3] | [Description] | [Value alone] | [Best alternative] | + +## Coalition Value Assessment +- **Grand coalition value:** [Total value of all players together] +- **Coalition type:** [Superadditive / Additive / Subadditive] +- **Synergy surplus:** [Grand coalition value minus sum of standalone values] + +## Sub-Coalition Values +| Sub-Coalition | Combined Value | Sum of Members' Standalone Values | Superadditive? | +|---------------|---------------|-----------------------------------|----------------| +| [Players 1+2] | [Value] | [Sum] | [Yes/No] | +| [Players 1+3] | [Value] | [Sum] | [Yes/No] | +| [Players 2+3] | [Value] | [Sum] | [Yes/No] | + +## Shapley Value Allocation +| Player | Average Marginal Contribution | Percentage Share | Proposed Allocation | +|--------|------------------------------|------------------|---------------------| +| [Player 1] | [Amount] | [%] | [Equity/Revenue share] | +| [Player 2] | [Amount] | [%] | [Equity/Revenue share] | +| [Player 3] | [Amount] | [%] | [Equity/Revenue share] | + +## Core Stability Check +| Sub-Coalition | Coalition Value | Members' Combined Allocation | Stable? | +|---------------|----------------|------------------------------|---------| +| [Players 1+2] | [Value] | [Sum of allocations] | [Yes/No] | +| [Players 1+3] | [Value] | [Sum of allocations] | [Yes/No] | +| [Players 2+3] | [Value] | [Sum of allocations] | [Yes/No] | + +## Defection Risks +- [Identify any sub-coalition whose standalone value exceeds their combined allocation] + +## Structural Safeguards +- [Vesting provisions, exclusivity, shared IP, or other mechanisms to raise defection costs] +``` + +--- + +## Related Skills + +- **[Negotiation Game Theory](negotiation-game-theory.md)** -- Once coalition membership is established, the Nash Product Solution determines optimal allocation terms between parties with differing utility functions. +- **[Evolutionary Strategy](evolutionary-strategy.md)** -- Market-level coalition behaviour follows evolutionary dynamics; the Hawk-Dove game explains when competitors cooperate versus compete. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the relational framework for conducting the conversations that coalition game theory structures analytically. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Coalition stability depends not only on mathematical allocation but on the trust between partners; the trust equation diagnoses relational factors that mathematical models assume away. +- **[Game Theory Fundamentals](game-theory-fundamentals.md)** -- Provides the prerequisite concepts of Nash equilibrium and payoff analysis that coalitional models extend into multi-player settings. +- **[Delivering the Deal](../negotiation/delivering-the-deal.md)** -- Coalition agreements must be closed and sustained; the preparation checklists and satisfaction engineering techniques address post-formation deal durability. diff --git a/plugins/foreman/content/skills/game-theory/evolutionary-strategy.md b/plugins/foreman/content/skills/game-theory/evolutionary-strategy.md new file mode 100644 index 0000000..816fce8 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/evolutionary-strategy.md @@ -0,0 +1,249 @@ +--- +name: "evolutionary-strategy" +description: "Applies evolutionary game theory to competitive strategy and market dynamics. Models markets as populations of players adopting different strategies, using the Hawk-Dove game for aggression calibration, follow-the-crowd dynamics for herding analysis, and Evolutionarily Stable Strategy (ESS) for predicting which competitive behaviours persist. Use when choosing between aggressive and cooperative market positioning, analysing industry convergence or fragmentation, timing market entry, understanding why competitors behave as they do, evaluating whether a disruptive strategy can break an established equilibrium, or diagnosing herding behaviour in a market." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - evolutionary-game-theory + - hawk-dove + - competitive-strategy + - market-dynamics + - ess + - herding + - disruption + - game-theory +related_skills: + - coalition-and-partnership-games + - negotiation-game-theory + - porters-five-forces + - blue-ocean-strategy + - disruptive-innovation +author: "Fatih Guner" +--- + +# Evolutionary Strategy + +Every market contains hawks and doves. Hawks compete aggressively -- slashing prices, litigating against rivals, poaching talent, flooding channels. Doves accommodate -- differentiating peacefully, sharing ecosystem value, avoiding direct confrontation. The question for any entrepreneur is not which species they are by temperament, but what the current population ratio demands. A market saturated with hawks rewards the dove who sidesteps the carnage. A market of complacent doves rewards the hawk who seizes territory while others graze. Evolutionary game theory, originally developed by John Maynard Smith and George Price in 1973 to explain animal conflict, provides the formal apparatus for this calculation -- and its predictions about competitive dynamics are remarkably precise. + +--- + +## The Framework + +### Evolutionarily Stable Strategy (ESS) + +Classical game theory assumes rational players making optimal decisions with full information. Evolutionary game theory assumes something closer to reality: large populations of players with imperfect information who learn through trial and error, imitation, and adaptation. Over time, strategies that produce above-average payoffs spread through the population (more companies adopt them), while strategies that underperform shrink (companies using them fail or switch). + +An **Evolutionarily Stable Strategy** is a strategy that, once adopted by the majority of a market, cannot be invaded by any small group of entrants playing a different strategy. An ESS is self-reinforcing: the more players adopt it, the harder it is to succeed with an alternative. + +The practical test for any competitive strategy: **if every competitor adopted this approach, would a small entrant playing differently gain an advantage?** If yes, the strategy is not evolutionarily stable, and the market will eventually shift. If no, the strategy is an ESS, and entrants must either adopt it or find a way to fundamentally change the game's payoff structure. + +### The Hawk-Dove Game: Calibrating Aggression + +The Hawk-Dove game is the foundational model for competitive intensity. Two players compete for a resource of value *v*. Each chooses to be a Hawk (fight aggressively) or a Dove (concede gracefully). + +**Payoff structure:** + +| | Opponent Plays Hawk | Opponent Plays Dove | +|---|---|---| +| **You Play Hawk** | Both fight: 50% chance of winning *v*, 50% chance of losing *c* (cost of conflict). Average payoff: *(v - c) / 2* | You win the full resource: payoff *v* | +| **You Play Dove** | You concede: payoff *0* | Split the resource: payoff *v / 2* | + +The critical ratio is *v/c* -- the value of the prize relative to the cost of fighting. + +**When the prize exceeds the cost of fighting (v > c):** Hawk is the dominant strategy. Aggression pays even against other hawks, because winning is worth the risk of losing. The ESS is all-hawk. Every company competes aggressively. This describes markets with large prize pools and low conflict costs -- think digital advertising, where customer acquisition costs are modest relative to lifetime value. + +**When the cost of fighting exceeds the prize (c > v):** Neither all-hawk nor all-dove is stable. The ESS is a *mixed population* where the proportion of hawks settles at *v/c*. Too many hawks, and the cost of conflict exceeds the prize -- doves do better by avoiding fights. Too few hawks, and the unchallenged resources attract new aggressors. The market oscillates toward an equilibrium ratio. + +**The entrepreneur's decision framework:** + +| Market Condition | Hawk Density | Your Optimal Play | Rationale | +|-----------------|-------------|-------------------|-----------| +| Crowded market, high conflict costs | High (many aggressive players) | Dove (differentiate, avoid direct competition) | Adding another hawk increases everyone's costs without increasing total value | +| Complacent market, low conflict costs | Low (most players are passive) | Hawk (aggressive entry, take share) | Unchallenged resources are available for the taking | +| Emerging market, uncertain value | Mixed | Conditional (hawk against doves, dove against hawks) | Flexibility is the only stable approach when the equilibrium has not yet formed | +| Mature market at equilibrium | Stable *v/c* ratio | Match the ratio unless you can change *v* or *c* | Deviating from the equilibrium ratio without changing the underlying economics is a losing strategy | + +### Follow-the-Crowd Dynamics: Market Herding + +Coordination games produce a different evolutionary pattern. In some markets, companies benefit from adopting the same strategy as the majority -- using the same technology standard, targeting the same customer segment, adopting the same pricing model. The follow-the-crowd dynamic produces **herding**: once a majority tips toward one strategy, the minority faces increasing pressure to conform. + +The payoff structure for coordination games creates two stable equilibria (everyone coordinates or everyone acts independently) and one unstable tipping point between them. Below the tipping point, the crowd gravitates toward independence. Above it, the crowd converges on coordination. + +**The tipping-point decision table:** + +| Market Adoption of Strategy X | Your Payoff from Adopting X | Your Payoff from Staying Independent | Rational Choice | +|-------------------------------|---------------------------|--------------------------------------|----------------| +| Below 50% adoption | Low (few partners, limited network effects) | Higher (independence has fewer costs) | Stay independent | +| At 50% adoption | Equal | Equal | Tipping point -- unstable | +| Above 50% adoption | High (network effects, ecosystem benefits) | Lower (isolation penalty) | Adopt X | + +**Entrepreneur implications:** + +Platform choices, technology standards, and go-to-market models all exhibit follow-the-crowd dynamics. Choosing a platform before it reaches the tipping point is a bet on which equilibrium the market will select. Choosing after the tipping point is confirmation, not strategy. The asymmetric opportunity lies in recognising which side of the tipping point the market currently occupies -- and whether any force (a dominant player's announcement, regulatory action, a technology breakthrough) is about to push it across. + +### Central-Tendency Games and Market Convergence + +The Hawk-Dove game has an interior equilibrium -- the population settles at a ratio between the extremes. This produces the central-tendency effect observed in many competitive markets: competitors cluster in the middle of the strategy space. + +Harold Hotelling demonstrated in 1929 that two competing sellers on a linear market will rationally locate next to each other at the centre -- even though distributing evenly would better serve customers. The logic extends beyond geography: competitors converge on pricing, features, positioning, and messaging because deviating from the centre risks ceding the majority of the market to the rival who stays central. + +This convergence is the evolutionary explanation for why: +- Most SaaS products in a category converge on similar feature sets +- Pricing within a market clusters in a narrow band +- Competing startups' pitch decks become nearly interchangeable +- Fast-food restaurants cluster on the same intersection + +The convergence is stable -- but only for two competitors. With three or more, the equilibrium breaks down. There is no stable positioning when three competitors try to occupy the centre simultaneously; at least one is always squeezed out. This mathematical result has a direct strategic implication: **in markets with more than two major competitors, pure central-positioning strategies are unstable.** Differentiation becomes necessary not as a branding exercise but as an evolutionary imperative. + +### When Disruption Succeeds: Breaking Evolutionary Stability + +An ESS, by definition, resists invasion by small groups of entrants playing differently. Disruption succeeds only when the entrant changes the payoff structure of the game itself -- not by playing the existing game better, but by making the existing strategies less effective. + +**Three mechanisms for breaking an ESS:** + +1. **Change the value of the prize (*v*).** Create a new category or redefine the prize. Airbnb did not compete for hotel rooms (the existing prize); it redefined the prize as "accommodation experiences," changing *v* for both hawks and doves in the hospitality market. + +2. **Change the cost of conflict (*c*).** Reduce the cost of aggressive competition or raise it. Open-source software reduced the cost of competing against proprietary vendors to near zero. Patent trolls raised the cost of conflict for everyone. Either change shifts the hawk-dove equilibrium. + +3. **Change the population structure.** Introduce a new type of player that does not fit the existing hawk-dove categorisation. Platform businesses (Uber, Airbnb, Amazon Marketplace) introduced a third player type -- the marketplace -- that transformed bilateral competition into a platform dynamics game with entirely different evolutionary pressures. + +If a startup cannot execute one of these three mechanisms, it is entering an evolutionarily stable market and should expect the existing equilibrium to resist its entry. The ESS framework does not say disruption is impossible. It specifies the conditions under which it can succeed. + +--- + +## Prompts + +**Prompt 1 -- Competitive Posture Assessment:** +> My company operates in [describe market/industry]. The main competitors are [list competitors and their strategies -- aggressive/cooperative/mixed]. Using the Hawk-Dove framework, help me assess: (1) What is the current hawk-to-dove ratio in this market? (2) Is the market at, above, or below the evolutionary equilibrium? (3) Given the prize value (market size, margins) and cost of conflict (price wars, customer acquisition cost, legal battles), what is the optimal competitive posture for a new or growing player? (4) What specific actions would constitute hawk versus dove behaviour in this market? + +**Prompt 2 -- Market Herding Analysis:** +> I am observing convergence in [describe market]: competitors are [describe the herding behaviour -- similar pricing, same features, same channels]. Using evolutionary game theory's follow-the-crowd model, help me analyse: (1) Has the market passed the tipping point? (2) What is the payoff for conforming versus differentiating at the current adoption level? (3) Are there structural forces (network effects, standards, regulation) that make convergence an ESS? (4) If I want to differentiate, what conditions must hold for a divergent strategy to be viable? + +**Prompt 3 -- Disruption Viability Test:** +> I am planning to disrupt [describe incumbent market/players]. My approach is [describe strategy]. Using the ESS framework, evaluate: (1) Is the current market an evolutionarily stable equilibrium? (2) Which of the three disruption mechanisms am I employing -- changing the prize value, changing the cost of conflict, or changing the population structure? (3) Is my approach sufficient to break the existing ESS, or am I merely entering the existing game as a new player (in which case the equilibrium will resist me)? (4) What would need to be true for my disruption to succeed? + +**Prompt 4 -- Market Timing Through Evolutionary Lens:** +> I am considering entering [describe market] at [describe timing -- early, growth phase, mature]. Using evolutionary dynamics, help me assess: (1) What evolutionary phase is the market in (pre-equilibrium formation, approaching equilibrium, stable equilibrium, disruption-in-progress)? (2) What strategy (hawk/dove/conditional) is optimal for this phase? (3) What signals should I monitor to detect phase transitions? (4) What is the risk that the equilibrium shifts before I reach scale? + +--- + +## Use Cases + +**Validation-Stage: Entering a Market of Aggressive Incumbents** + +A fintech startup plans to offer small-business lending, a market dominated by three aggressive players engaged in relentless customer acquisition spending. Customer acquisition costs have tripled in two years. The incumbents are all hawks -- competing primarily on speed, marketing spend, and broker commissions. + +Evolutionary analysis: the cost of conflict (*c* -- CAC, broker fees, margin compression) now exceeds the prize value (*v* -- lifetime value per customer minus servicing costs) for many customer segments. The hawk-hawk payoff is negative. The market is over-hawked. + +Optimal entry strategy: dove. Target the segments the hawks are fighting over least intensely (underserved niches with lower LTV that the incumbents' unit economics cannot support). Build through referral networks and embedded partnerships rather than paid acquisition. Avoid direct confrontation until scale provides cost advantages that shift the personal *v/c* ratio. + +The startup's first investor pitch asked "how will you outspend the incumbents?" The evolutionary framework reframes: "why would we fight the war that is bankrupting the combatants?" + +**Growth-Stage: Platform Standard Convergence** + +A developer-tools company built its product on a proprietary integration protocol. The market is converging on an open standard that three of five major competitors have adopted. Adoption is at 55% -- just past the evolutionary tipping point. + +Follow-the-crowd analysis: above the tipping point, the payoff for conforming (ecosystem compatibility, shared tooling, talent pool familiarity) exceeds the payoff for independence (differentiation, lock-in, proprietary advantage). The tipping point is behind them. The market will converge. + +The company faces a choice: adopt the standard now (accepting short-term migration costs) or resist (hoping to maintain differentiation). Evolutionary dynamics predict that resistance is a losing strategy once the tipping point is crossed. Every additional competitor that adopts the standard increases the isolation penalty for holdouts. The rational choice is adoption -- and the sooner, the lower the switching cost. + +The company pivots its differentiation from the protocol layer (where convergence is inevitable) to the application layer (where the Hawk-Dove dynamic still permits differentiation). + +**Scale-Stage: Breaking an Industry Equilibrium** + +A logistics company identifies that the freight brokerage industry operates at a stable Hawk-Dove equilibrium: large brokers compete aggressively on price for high-volume shippers (hawks), while smaller brokers serve niche segments cooperatively (doves). The equilibrium has held for fifteen years. + +Rather than entering as a hawk (undercutting on price) or a dove (serving a niche), the company changes the game's payoff structure by building a technology platform that automates the matching function brokers traditionally perform. This changes the cost of conflict (technology reduces matching costs to near zero, making the price-competition game less costly) and changes the population structure (the platform is neither hawk nor dove but a new player type that profits from transaction volume regardless of competitive dynamics). + +The existing ESS is destabilised not because a better hawk or dove arrived, but because the game itself changed. Incumbents' evolved strategies -- optimised for the old game -- become maladapted to the new one. + +--- + +## Anti-Patterns + +1. **Confusing Temperament with Strategy.** Choosing hawk or dove based on the founder's personality rather than the market's evolutionary dynamics. An aggressive founder in an over-hawked market will bleed capital. A cautious founder in an under-hawked market will miss available territory. The framework demands that posture follow analysis, not disposition. + +2. **Fighting an ESS Head-On.** Entering an evolutionarily stable market with the same strategy the incumbents use, expecting to execute it better. An ESS resists invasion by definition. A slightly better hawk in a stable hawk equilibrium will be ground down by the collective response. The entrant must either change the game (disrupt the payoff structure) or accept the equilibrium and find an underserved niche within it. + +3. **Mistaking Herding for Validation.** Interpreting market convergence as proof that the converged strategy is correct. Follow-the-crowd dynamics produce convergence regardless of whether the converged strategy is globally optimal. Markets can herd toward suboptimal equilibria -- the coordination benefit of conformity can outweigh the absolute benefit of a superior but isolated strategy. The question is not "is everyone doing this?" but "is this the Pareto-optimal equilibrium?" + +4. **Ignoring Evolutionary Speed.** Assuming market dynamics are static when they are changing. A market approaching its hawk-dove equilibrium from an over-hawked state is a declining environment for new hawks but an improving one for doves. A market post-disruption is in disequilibrium, where early movers can claim territory before a new ESS forms. Timing strategy to evolutionary phase transitions -- not to static snapshots -- is essential. + +5. **Applying Hawk-Dove to Cooperative Markets.** Using competitive aggression frameworks in markets that are fundamentally coordination games. Developer ecosystems, multi-sided platforms, and standards-driven industries reward coordination, not competition. Playing hawk in a coordination game destroys the ecosystem and the hawk along with it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Assessing market equilibrium before entry | The primary question is whether the market has reached an ESS and what type. If stable, the entrant must identify a disruption mechanism or an underserved niche. If pre-equilibrium, there is an opportunity to shape the emerging dynamics. | +| Early Traction | Choosing competitive posture | With initial market presence, the company must commit to a hawk or dove posture (or a conditional strategy). The choice should be driven by the current population ratio and the company's cost structure, not by aspiration. | +| Growth | Navigating convergence and herding | Growth-stage companies face platform choices, standard adoption decisions, and ecosystem alignment. Follow-the-crowd analysis determines whether to conform or differentiate. Misreading the tipping point -- conforming too early or too late -- is the primary risk. | +| Scale | Sustaining or disrupting equilibria | At scale, the company is part of the equilibrium. Its actions affect the market's evolutionary dynamics. Strategic choices (pricing, M&A, platform openness) should account for how they shift the hawk-dove ratio and whether they risk destabilising a favourable equilibrium. | + +--- + +## Output Template + +```markdown +# Evolutionary Strategy Analysis: [Market/Industry] + +## Market Characterisation +- **Market type:** [Hawk-Dove competition / Coordination game / Mixed] +- **Current evolutionary phase:** [Pre-equilibrium / Approaching ESS / Stable ESS / Post-disruption disequilibrium] +- **Estimated hawk-to-dove ratio:** [X% hawks, Y% doves] + +## Payoff Structure +| Matchup | Payoff Description | Estimated Magnitude | +|---------|-------------------|---------------------| +| Hawk vs Hawk | [Describe: price war, talent poaching, etc.] | [Gain/Loss estimate] | +| Hawk vs Dove | [Describe: market capture] | [Gain estimate for hawk] | +| Dove vs Hawk | [Describe: concession] | [Gain/Loss for dove] | +| Dove vs Dove | [Describe: market sharing] | [Gain estimate for each] | + +## Prize vs Conflict Analysis +- **Prize value (v):** [Market size, margins, LTV per customer] +- **Conflict cost (c):** [CAC inflation, legal costs, margin erosion, talent costs] +- **v/c ratio:** [Value] -- indicates [all-hawk ESS / mixed equilibrium at v/c ratio / dove-dominant] + +## Competitive Posture Recommendation +- **Recommended strategy:** [Hawk / Dove / Conditional / Game-changer] +- **Rationale:** [Based on current population ratio and v/c analysis] +- **Specific actions:** + 1. [Action aligned with recommended posture] + 2. [Action aligned with recommended posture] + 3. [Action aligned with recommended posture] + +## Herding and Convergence Assessment +- **Is convergence occurring?** [Yes/No] +- **Tipping point status:** [Below / At / Above] +- **Conform or differentiate?** [Recommendation with rationale] + +## Disruption Feasibility (if applicable) +- **Disruption mechanism:** [Change v / Change c / Change population structure] +- **Feasibility:** [High / Medium / Low] +- **Key assumption that must hold:** [Describe] + +## Monitoring Signals +- [Signal that indicates phase transition approaching] +- [Signal that hawk-dove ratio is shifting] +- [Signal that herding tipping point is near] +``` + +--- + +## Related Skills + +- **[Coalition and Partnership Games](coalition-and-partnership-games.md)** -- In markets where evolutionary dynamics favour cooperation, coalitional game theory provides the tools for structuring partnerships and alliances that emerge from dove strategies. +- **[Negotiation Game Theory](negotiation-game-theory.md)** -- Individual negotiations occur within the broader evolutionary context; the Nash Product Solution applies within the constraints the market's hawk-dove equilibrium imposes on deal terms. +- **[Prisoner's Dilemma and Cooperation](prisoners-dilemma-and-cooperation.md)** -- The one-shot dilemma becomes an evolutionary game when played repeatedly across a population, revealing how tit-for-tat and other strategies emerge and stabilise. +- **[Porter's Five Forces](../frameworks/porters-five-forces.md)** -- Five Forces analyses industry structure at a point in time; evolutionary game theory analyses how that structure changes over time as competitive strategies evolve. +- **[Blue Ocean Strategy](../frameworks/blue-ocean-strategy.md)** -- Blue Ocean's "make the competition irrelevant" is the strategic expression of changing the game's payoff structure to break an existing ESS. +- **[Disruptive Innovation](../frameworks/disruptive-innovation.md)** -- Christensen's disruption theory describes the what; evolutionary game theory provides the mathematical why, as incumbent strategies are ESS-locked. diff --git a/plugins/foreman/content/skills/game-theory/first-mover-strategy.md b/plugins/foreman/content/skills/game-theory/first-mover-strategy.md new file mode 100644 index 0000000..6326661 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/first-mover-strategy.md @@ -0,0 +1,277 @@ +--- +name: "first-mover-strategy" +description: "Analyzes first-mover advantage, second-mover advantage, credible commitments, and credible threats in sequential strategic games. Covers the Stackelberg leader-follower model, the Chicken Game for competitive standoffs, the market entry game for incumbent-entrant dynamics, and burning bridges as a commitment device. Use when deciding market entry timing, evaluating competitive positioning sequences, structuring partnership commitments, negotiating investor term sheets, or assessing whether to lead or follow in any strategic interaction." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - first-mover-advantage + - second-mover-advantage + - credible-commitment + - credible-threat + - market-entry + - competitive-timing + - stackelberg + - strategic-positioning +related_skills: + - game-theory-fundamentals + - prisoners-dilemma-and-cooperation + - information-asymmetry + - porters-five-forces + - blue-ocean-strategy + - disruptive-innovation + - scenario-planning + - art-of-war +author: "Fatih Guner" +--- + +# First-Mover Strategy + +CHESS OPENING. In chess, white moves first and holds a statistical advantage -- roughly 55% of games between equally matched players. But in many openings, black deliberately allows white to overextend, then counterattacks with superior information about white's committed position. The analogy to entrepreneurship is exact, and the answer to "should I move first?" is always the same: it depends on the game's structure. The Stackelberg model demonstrates that in quantity competition, the first mover captures a disproportionate share. The price-setting game demonstrates the reverse: the second mover can observe the first mover's price and undercut by a penny, winning the market. Between these two extremes lies every real market entry decision, every competitive response, and every negotiation. The question is never whether first-mover advantage exists in the abstract. The question is whether the specific game you are playing rewards initiative or patience -- and whether you can tell the difference before you commit. + +--- + +## The Framework + +### First-Mover Advantage: The Stackelberg Model + +Heinrich von Stackelberg formalized the first-mover advantage in 1934. His model contrasts two scenarios for firms producing competing products: simultaneous decisions (the Cournot model) and sequential decisions (the Stackelberg model). + +**Simultaneous Decision (Cournot): No First Mover** + +Both firms decide output at the same time, without observing each other. Each produces the same quantity and earns the same profit. Neither has an advantage. + +**Sequential Decision (Stackelberg): First Mover Wins** + +Firm 1 commits to a production level first. Firm 2 observes this commitment and optimizes its own output in response. The critical asymmetry: Firm 1 knows that Firm 2 will react optimally to whatever Firm 1 does. This knowledge allows Firm 1 to commit to a larger output than the Cournot level -- forcing Firm 2 into a smaller, less profitable response. + +The result in practical terms: + +| Metric | Cournot (Simultaneous) | Stackelberg Leader | Stackelberg Follower | +|--------|----------------------|-------------------|---------------------| +| Market share | Equal | Larger | Smaller | +| Profit | Equal | Higher than Cournot | Lower than Cournot | +| Strategic flexibility | Equal | Committed (locked in) | Reactive (constrained) | + +The first mover earns more than under simultaneous competition, while the follower earns less. The leader benefits from commitment; the follower suffers from being forced to react. + +**When First-Mover Advantage Applies in Business:** + +- **Platform markets with network effects.** The first platform to achieve critical mass creates switching costs and network value that followers cannot replicate without disproportionate investment. Facebook entering social networking before Google, Uber establishing ride-sharing before Lyft in key markets, and Slack defining workplace messaging before Teams all illustrate Stackelberg dynamics in platform competition. +- **Standard-setting and ecosystem creation.** The first mover defines the standard that others must follow or compete against. USB, Bluetooth, and TCP/IP were all first-mover standards where the pioneer's specifications became the industry default. +- **Markets where commitment is visible and irreversible.** Production capacity investments, exclusive distribution contracts, and long-term customer agreements all create the kind of visible, irreversible commitment that makes Stackelberg advantage work. The competitor sees the commitment, recognizes it cannot be reversed, and adjusts their strategy to accommodate it. + +### Second-Mover Advantage: When Patience Wins + +Not all sequential games reward the first mover. The second mover has a structural advantage in specific conditions. + +**The Price-Setting Game.** When two firms compete on price for a similar product, the second mover can observe the first mover's price and undercut it slightly. The first mover commits to a price; the second mover responds with a lower price and captures the market. The first mover's commitment becomes a liability, not an asset. + +**The Technology Adoption Game.** The first mover in a nascent technology bears the full cost of market education, infrastructure development, and early-adopter friction. The second mover observes which approaches work, which fail, and what customers actually want -- then enters with a refined product at lower cost. Microsoft famously followed this strategy across multiple categories: spreadsheets (after VisiCalc and Lotus 1-2-3), browsers (after Netscape), and search advertising (after Google, though less successfully). + +**When Second-Mover Advantage Applies:** + +| Condition | Why the Second Mover Wins | Example | +|-----------|--------------------------|---------| +| High market education costs | First mover pays to educate customers; second mover enters an educated market | Google entering search after AltaVista and Yahoo had trained users | +| Rapid technology evolution | First mover's technology becomes obsolete; second mover leaps ahead | Samsung in smartphones, entering after Apple proved the market | +| Observable pricing | Second mover undercuts by observing first mover's committed price | Retail "price matching" guarantees as institutional second-mover strategy | +| High uncertainty, low commitment cost | Second mover waits for uncertainty to resolve, then commits with better information | Late-stage investors who wait for product-market fit before investing | + +### The Coexistence Problem: Both Advantages Can Be Present + +Some markets exhibit both first-mover and second-mover advantages simultaneously, depending on which dimension of competition is analyzed. A company might have first-mover advantage in establishing a brand and second-mover advantage in technology refinement. The strategic question is not "which advantage exists" but "which advantage is larger on the dimension that matters most for long-term value capture." + +The resolution typically depends on whether the competitive advantage compounds over time. Network effects and switching costs compound: the first mover's advantage grows with each passing period. Technology and information advantages erode: the first mover's knowledge is eventually replicated or surpassed. When compounding advantages dominate, move first. When eroding advantages dominate, wait. + +### Credible Commitment: Making Promises Believable + +A commitment is credible when the committing party cannot reverse it -- or when reversal is so costly that it would be irrational. Game theory distinguishes sharply between statements of intent (cheap talk) and credible commitments (structurally binding). + +**The Credibility Test:** + +| Question | If Yes | If No | +|----------|--------|-------| +| Is the commitment publicly observable? | Increases credibility | Easy to renege quietly | +| Is reversal costly? | Credible -- rational actor would not reverse | Not credible -- can be abandoned when convenient | +| Has the committer invested irreversible resources? | Credible -- sunk costs create lock-in | Not credible -- nothing lost by walking away | +| Is the committer's reputation at stake? | Credible -- reputation damage exceeds benefit of reversal | Not credible -- no reputational consequence for breaking it | + +**Entrepreneurial Commitment Devices:** + +- **Public product roadmaps.** Publicly announcing features or launch dates creates reputational commitment. A company that routinely misses public deadlines destroys its credibility on all future announcements. +- **Exclusive partnerships.** Signing an exclusive distribution deal with one retailer credibly commits to that channel. The commitment is visible, costly to reverse, and signals strategic direction to the entire market. +- **Capacity investments.** Building a factory, signing a long-term lease, or hiring a large team creates commitment through sunk cost. The investment is irreversible and signals sustained presence in the market. +- **Open-sourcing core technology.** Open-sourcing a component credibly commits to a particular technical architecture. The commitment cannot be reversed (the code is public) and signals a specific strategic direction. + +### Credible Threat: Making Consequences Real + +A credible threat is a threatened action that the threatening party would rationally carry out if the threat conditions are met. Incredible threats -- threats that the threatening party would not actually follow through on -- are strategically worthless because rational opponents ignore them. + +**The Chicken Game: Mutual Incredible Threats** + +Two competitors on a collision course -- both racing to launch the same product in the same market at the same time. Neither wants to crash (both launch, splitting a market that cannot support two entrants). Both would prefer the other to swerve (one launches, the other pivots). + +| | Competitor: Stay Course | Competitor: Swerve | +|--|------------------------|-------------------| +| **You: Stay Course** | Both crash (-50, -50) | You win the market (100, 0) | +| **You: Swerve** | They win the market (0, 100) | Both find alternative paths (30, 30) | + +Neither player has a credible threat because carrying out the threat (staying course when the opponent also stays) hurts both equally. The outcome depends on which player can make their commitment more credible -- or which blinks first. + +**The Market Entry Game: Incumbent vs. Entrant** + +An incumbent threatens to slash prices if a startup enters their market. The question is whether the threat is credible. + +| | Startup: Enter | Startup: Stay Out | +|--|---------------|-------------------| +| **Incumbent: Price War** | Incumbent: -20, Startup: -30 | Incumbent: 100, Startup: 0 | +| **Incumbent: Accommodate** | Incumbent: 40, Startup: 30 | Incumbent: 100, Startup: 0 | + +Backward induction: if the startup enters, the incumbent's best response is to accommodate (40 > -20). The price war threat is incredible -- carrying it out hurts the incumbent too. The startup should enter, knowing the rational incumbent will accommodate. + +The incumbent can make the threat credible only by changing the game structure: investing in excess capacity (making price war less costly), signing long-term customer contracts at low prices (pre-committing to low pricing regardless of entry), or building a reputation for aggressive retaliation across multiple markets (making the single-market cost rational as a reputation investment). + +### Burning Bridges: The Ultimate Commitment Device + +The most powerful commitment device is eliminating your own option to retreat. Hernan Cortes allegedly burned his ships upon reaching the New World, making return impossible and committing his forces irrevocably to the conquest. The game-theoretic logic: when your opponent knows you cannot retreat, they must accommodate your advance. + +**Burning Bridges in Business:** + +| Action | What It Eliminates | Strategic Effect | +|--------|-------------------|-----------------| +| Quitting your job to start the company | Option to return to employment | Signals total commitment to investors, cofounders, early customers | +| Publicly announcing entry into a market | Option to quietly withdraw | Competitors and customers take the commitment seriously | +| Signing a long-term office lease | Option to reduce overhead quickly | Forces the team to generate revenue to cover fixed costs | +| Taking on venture debt alongside equity | Option to simply return capital | Creates urgency and commitment to growth | +| Open-sourcing proprietary technology | Option to compete on technology secrecy | Forces competitive advantage through other dimensions (service, ecosystem, speed) | + +The logic is counterintuitive: reducing your own options makes you stronger. Flexibility is normally an asset, but in sequential games, visible inflexibility forces the other player to adapt to your committed position rather than calling your bluff. + +The critical caveat: burning bridges works only when the opponent observes the commitment and believes it is irreversible. A bridge burned in secret provides no strategic advantage. And a bridge burned in a game where retreat is the optimal response -- because the market is genuinely unwinnable -- is not strategic commitment but self-destruction. + +--- + +## Prompts + +**Prompt 1 -- Assess First-Mover vs. Second-Mover Advantage:** +> I am considering entering [describe market]. Help me determine whether first-mover or second-mover advantage dominates in this specific market. Analyze: Are there network effects or switching costs that compound over time (favoring first mover)? Is there high uncertainty or rapid technology change (favoring second mover)? Is the competitive advantage in brand/distribution (usually favoring first mover) or in technology/product refinement (often favoring second mover)? Based on the analysis, recommend optimal entry timing and the specific advantages I should seek to capture. + +**Prompt 2 -- Design a Credible Commitment:** +> I need to make a credible commitment to [describe: market, partner, customer, investor]. Currently my commitment is not believed because [describe why]. Help me design a commitment device that passes the credibility test: it must be publicly observable, costly to reverse, involve irreversible resource investment, and put my reputation at stake. Evaluate at least four commitment devices and recommend the one with the best ratio of credibility gained to flexibility lost. + +**Prompt 3 -- Evaluate a Competitive Threat:** +> A competitor is threatening to [describe threat: price cut, market entry, patent lawsuit, talent poaching]. Help me assess whether this threat is credible using backward induction. If the competitor carries out the threat, what are the payoffs for both sides? Would a rational actor follow through? If the threat is incredible, what is the optimal response? If it is credible, what are my options for neutralizing it -- either by making my own counter-threat credible or by changing the game structure? + +**Prompt 4 -- Map the Sequential Game:** +> I am in a sequential competitive interaction with [describe competitor/partner]. I can move first or wait for them to move. Help me map this as a dynamic game tree: what are the possible move sequences, what are the payoffs at each terminal node, and what does backward induction recommend? Should I move first, or should I wait? If I move first, what commitment should I make? If I wait, what information do I gain and how should I respond to each possible first move by the other player? + +--- + +## Use Cases + +**Idea-Stage Founder Deciding When to Launch** + +A founder has developed a working prototype for an AI-powered contract analysis tool. A well-funded competitor is building a similar product and is approximately three months behind. The founder analyzes the game as a Stackelberg interaction: if she launches first with an imperfect product, she establishes market presence, begins accumulating training data (a compounding advantage), and forces the competitor to differentiate rather than compete head-on. If she waits for a polished product, the competitor may launch first and capture the data advantage. The analysis reveals that in this specific market, first-mover advantage is driven by data accumulation (compounding) rather than technology (eroding). She launches the MVP immediately, accepting initial product limitations in exchange for the data flywheel advantage. She reinforces the commitment by signing three design partners to 18-month exclusive contracts -- a visible, costly signal that makes her market presence irreversible. + +**Growth-Stage Company Facing an Incumbent's Threat** + +A growth-stage fintech company has captured 8% of the small business lending market. The dominant incumbent (45% market share) announces through a press interview that it will "aggressively defend" its market position, implying price cuts and increased marketing spend. The CTO performs a backward induction analysis. If the startup continues growing, the incumbent's best response is accommodation (maintaining margins on the 92% of the market it still controls) rather than a price war (which would compress margins across its entire customer base to prevent 8% erosion). The threat is incredible: the cost of industry-wide price compression far exceeds the cost of conceding the startup's niche. The startup continues its growth strategy, ignoring the threat -- while privately investing in switching-cost infrastructure (deep integration with accounting platforms) that would make a future price war even less effective. + +**Scale-Stage Platform Committing to an Ecosystem Strategy** + +A B2B SaaS platform at scale must decide whether to build a proprietary analytics module (capturing more value directly) or open the analytics API to third-party developers (building ecosystem value). The CEO frames this as a burning-bridges decision. Opening the API is effectively irreversible: once third-party developers build on the API, closing it would destroy ecosystem trust permanently. This irreversibility is the point. By open-sourcing the analytics layer, the platform credibly commits to a horizontal strategy, which attracts developers who would otherwise fear platform lock-in or competition from the platform itself. The commitment device -- the burned bridge of building the module in-house -- transforms the platform from a potential competitor into a credible partner. Within 18 months, the third-party analytics ecosystem generates more value than the in-house module would have, validating the strategic logic of irreversible commitment. + +--- + +## Anti-Patterns + +1. **Pursuing first-mover advantage as a default strategy.** First-mover advantage is conditional, not universal. Entering first in a market characterized by high uncertainty, rapid technology change, or high customer education costs often means absorbing all the pioneering costs while a follower enters with better information and a refined product. The analysis must precede the decision, not justify a preference for speed. + +2. **Making commitments that are not observed.** A commitment no one sees provides no strategic value. Internal decisions, quiet investments, and private plans do not change the game because they do not change other players' calculations. Commitment devices must be visible to the players whose behavior they are intended to influence. + +3. **Confusing sunk costs with strategic commitment.** Money already spent on a failing strategy is a sunk cost, not a strategic commitment. Continuing to invest in a losing position because "we have already committed" is the sunk cost fallacy wearing game theory clothing. Strategic commitment is forward-looking: it changes the future game structure. Sunk costs change nothing. + +4. **Issuing incredible threats and expecting compliance.** Threatening a competitor with a price war that would destroy your own margins, threatening a partner with a lawsuit you cannot afford, or threatening an employee with termination you cannot operationally sustain -- all are incredible threats that sophisticated opponents will ignore. Before issuing any threat, apply backward induction: would you actually follow through? If not, the threat degrades your credibility rather than enhancing it. + +5. **Burning bridges when the terrain is uncertain.** Eliminating retreat options is powerful when the destination is known and the path is visible. Burning bridges into fog -- committing irrevocably to a market that is poorly understood, a technology that is unproven, or a partnership that is untested -- is recklessness, not strategy. Reserve irreversible commitments for situations where the game structure is well understood and the commitment clearly shifts the equilibrium in your favor. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Timing analysis | The most consequential first-mover/second-mover decision occurs before launch: whether to enter now or wait. Analyze whether the market rewards pioneers (network effects, data accumulation, standard-setting) or fast followers (technology refinement, educated customers, proven demand). This decision often determines the company's entire trajectory. | +| Validation | Credible signaling | At validation stage, the startup lacks the resources for large-scale commitment devices. Focus on targeted signals: design partnerships, letter-of-intent commitments from early customers, and publicly visible milestones. These are low-cost commitment devices that establish market presence without irreversible resource commitment. | +| Early Traction | Competitive response mapping | With initial traction established, competitors begin to react. Map the sequential game: if you expand to segment X, how will the incumbent respond? Use backward induction to anticipate competitor reactions and choose moves that force favorable responses. | +| Growth | Commitment escalation | Growth stage enables larger commitment devices: exclusive contracts, capacity investments, ecosystem development. Each commitment should be evaluated not just for its direct return but for its strategic effect -- how it changes the game for competitors. | +| Scale | Game design through irreversible infrastructure | At scale, the company makes commitments that reshape the industry: platform standards, open APIs, infrastructure investments, regulatory engagement. These are the ultimate commitment devices -- they alter the game structure for all players, not just the competitive dynamic with a single rival. | + +--- + +## Output Template + +```markdown +# First-Mover / Sequential Strategy Analysis + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Game Structure + +- **Game type:** [Stackelberg / Chicken / Market Entry / Other] +- **Sequence:** [Who moves first? Is the sequence fixed or negotiable?] +- **Key compounding advantages:** [Network effects, data, switching costs, etc.] +- **Key eroding advantages:** [Technology, information, first-mover costs] + +## First-Mover vs. Second-Mover Assessment + +| Factor | Favors First Mover | Favors Second Mover | Assessment for This Market | +|--------|-------------------|--------------------|-----------------------------| +| Network effects | Strong | Weak | [Assessment] | +| Technology maturity | Mature | Evolving rapidly | [Assessment] | +| Customer education costs | Low | High | [Assessment] | +| Switching costs once established | High | Low | [Assessment] | +| Uncertainty level | Low | High | [Assessment] | +| **Overall** | | | **[First / Second / Depends on dimension]** | + +## Commitment/Threat Analysis + +| Commitment or Threat | Observable? | Costly to Reverse? | Credible? | Strategic Effect | +|---------------------|-------------|-------------------|-----------|-----------------| +| [Action 1] | [Y/N] | [Y/N] | [Y/N] | [Effect] | +| [Action 2] | [Y/N] | [Y/N] | [Y/N] | [Effect] | + +## Dynamic Game Tree (Key Decision Sequence) + +1. **Our move:** [Action] + - **If competitor responds with X:** Our payoff [value], Their payoff [value] + - **If competitor responds with Y:** Our payoff [value], Their payoff [value] +2. **Backward induction predicts:** [Competitor's rational response] +3. **Optimal first move:** [Recommendation] + +## Strategic Recommendation + +1. [Timing decision: move now or wait] +2. [Commitment device to deploy] +3. [Contingency plan for unexpected competitor moves] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](game-theory-fundamentals.md)** -- Provides the concepts of Nash equilibrium, payoff matrices, and static versus dynamic games that this skill extends into sequential analysis and commitment theory. +- **[Prisoner's Dilemma and Cooperation](prisoners-dilemma-and-cooperation.md)** -- Sequential moves can transform a simultaneous dilemma into a dynamic game with different equilibria; first movers can establish cooperative or competitive dynamics. +- **[Information Asymmetry](information-asymmetry.md)** -- The first mover often reveals information through their action; the second mover benefits from reduced uncertainty, creating a tension between commitment and information advantage. +- **[Blue Ocean Strategy](../frameworks/blue-ocean-strategy.md)** -- Creating an uncontested market space is the ultimate first-mover play: defining a new game where no competitor has yet established a position. +- **[Disruptive Innovation](../frameworks/disruptive-innovation.md)** -- Disruptors often benefit from second-mover advantage at the low end of a market, then compound advantages to move upmarket. +- **[Strategic Thinking and Alignment](../leadership/strategic-thinking-and-alignment.md)** -- The daily habit of strategic analysis determines whether timing decisions are made deliberately or by default. diff --git a/plugins/foreman/content/skills/game-theory/game-theory-fundamentals.md b/plugins/foreman/content/skills/game-theory/game-theory-fundamentals.md new file mode 100644 index 0000000..d6cccc4 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/game-theory-fundamentals.md @@ -0,0 +1,232 @@ +--- +name: "game-theory-fundamentals" +description: "Introduces the foundational concepts of game theory for strategic business decisions: players, strategies, payoffs, game matrices, Nash equilibrium, and the distinction between static and dynamic games. Use when analyzing competitive dynamics, mapping market interactions, identifying stable outcomes in multi-player business situations, or structuring strategic choices under uncertainty." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - game-theory + - nash-equilibrium + - competitive-strategy + - strategic-thinking + - decision-making + - payoff-matrix +related_skills: + - prisoners-dilemma-and-cooperation + - information-asymmetry + - first-mover-strategy + - porters-five-forces + - scenario-planning + - art-of-war + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +# Game Theory Fundamentals + +BEAUTIFUL MIND. John Nash's Nobel Prize-winning insight fits in a single sentence: the best strategy for any player depends on what every other player is doing. This observation -- that optimal choices are interdependent, not independent -- is the foundation of game theory, and every entrepreneur already applies it without knowing the name. When a founder prices a product, negotiates a term sheet, or decides whether to enter a market, they are playing a game in the formal sense: multiple actors making strategic choices where each outcome depends on the choices of all. The difference between intuition and game theory is precision. Intuition says "consider the competition." Game theory says exactly how. + +--- + +## The Framework + +### The Three Essential Elements + +Every strategic interaction -- from a pricing war between two SaaS competitors to a cofounder equity negotiation -- reduces to three elements. Identifying them is the first step toward rigorous analysis. + +**Element 1: Players.** The decision-makers in the game. A minimum of two. In business, players are not always obvious. A startup entering a market has visible players (direct competitors) and hidden ones (regulators, platform owners, complementary product makers, the customer choosing between alternatives). Misidentifying who the players are is the most common source of strategic error. + +**Element 2: Strategies.** The set of available actions each player can take. A strategy is a complete plan of action -- not just "lower prices" but "lower prices by 15% in Q3 and match any further competitor reduction within 48 hours." The strategies available to each player define the boundaries of the game. Expanding or constraining available strategies changes the game fundamentally. + +**Element 3: Payoffs.** The outcome each player receives for each combination of strategies. Payoffs are not always financial. They can include market share, reputation, strategic positioning, time saved, or optionality preserved. The critical insight: a player's payoff depends not only on their own strategy but on the combination of all players' strategies. + +A game is fully defined by specifying these three elements. Everything else -- equilibria, optimal strategies, competitive dynamics -- follows from them. + +### The Payoff Matrix: Mapping Strategic Interactions + +The payoff matrix is the fundamental tool for visualizing a two-player game. Each row represents a strategy available to Player A; each column represents a strategy available to Player B. Each cell contains the payoffs for both players under that combination of strategies. + +**Example: Two Competing Coffee Shops** + +| | Shop B: Premium Pricing | Shop B: Discount Pricing | +|--|------------------------|------------------------| +| **Shop A: Premium Pricing** | A earns 80, B earns 80 | A earns 30, B earns 100 | +| **Shop A: Discount Pricing** | A earns 100, B earns 30 | A earns 50, B earns 50 | + +Reading this matrix reveals the strategic tension immediately. Both shops charging premium prices produces good results for both (80, 80). Both discounting produces mediocre results for both (50, 50). But each shop is individually tempted to discount while the other charges premium prices, capturing 100 while the competitor earns only 30. + +This single table encodes the entire competitive dynamic. No narrative strategy document communicates as much information as concisely. + +### Optimal, Worst, and Relative Optimal Strategies + +Three types of strategy merit identification in any game: + +**Optimal Strategy (Dominant Strategy).** A strategy that produces a higher payoff than all alternatives, regardless of what other players do. When a dominant strategy exists, the decision is straightforward -- play it. In the Prisoner's Dilemma, confessing is the dominant strategy for both suspects. In business, a dominant strategy is rare and valuable: it means the right move does not depend on competitor intelligence. + +**Worst Strategy (Dominated Strategy).** A strategy that always produces a lower payoff than some alternative, regardless of opponent behavior. Dominated strategies should be eliminated immediately from consideration. Their removal often simplifies the game considerably, sometimes revealing dominant strategies that were previously obscured. + +**Relative Optimal Strategy (Best Response).** The best strategy given a specific choice by the other player. Most real business situations lack dominant strategies. Instead, the best action depends on the competitor's action. "If they price high, we should price high. If they price low, we should price low." Mapping the relative optimal strategy for each possible competitor action is the foundation for finding Nash equilibrium. + +### Nash Equilibrium: The Stable Outcome + +Nash equilibrium is the combination of strategies where no player can improve their payoff by unilaterally changing their own strategy. Once reached, no one has an incentive to deviate. + +The method for finding it in a simple matrix: + +1. For each of Player B's strategies, identify Player A's best response (underline A's highest payoff in each column). +2. For each of Player A's strategies, identify Player B's best response (underline B's highest payoff in each row). +3. Any cell where both payoffs are underlined is a Nash equilibrium. + +**Applied to the Coffee Shop Example:** + +- If B prices premium, A's best response is discount (100 > 80). If B discounts, A's best response is discount (50 > 30). +- If A prices premium, B's best response is discount (100 > 80). If A discounts, B's best response is discount (50 > 30). +- Nash equilibrium: Both discount (50, 50). + +The equilibrium is stable but suboptimal -- both would prefer (80, 80). This tension between individual rationality and collective benefit is the central paradox of non-cooperative games, and it recurs across virtually every competitive business situation. + +### Multiple Equilibria: Risk Control vs. Pareto Optimum + +Many games produce multiple Nash equilibria. Two principles govern which one is likely to prevail: + +**Risk Control Principle.** Players choose the equilibrium that minimizes their worst-case exposure. Consider two tech companies deciding whether to adopt a shared standard: + +| | Firm B: Adopt Standard | Firm B: Go Alone | +|--|----------------------|-----------------| +| **Firm A: Adopt Standard** | A earns 100, B earns 100 | A earns 10, B earns 80 | +| **Firm A: Go Alone** | A earns 80, B earns 10 | A earns 60, B earns 60 | + +Both (Adopt, Adopt) and (Go Alone, Go Alone) are Nash equilibria. The risk-control principle predicts (Go Alone, Go Alone): if Firm A adopts the standard but B does not, A earns only 10. Playing it safe yields a guaranteed 60. Without trust or communication, risk aversion drives players to the inferior equilibrium. + +**Pareto Optimum Principle.** When players can communicate or have established trust, they gravitate toward the equilibrium that maximizes collective payoffs. Here, (Adopt, Adopt) is Pareto optimal -- both earn 100 instead of 60. + +The practical implication for entrepreneurs: the ability to communicate, build trust, and make credible commitments determines whether markets settle into productive equilibria or defensive, low-value ones. + +### Static vs. Dynamic Games + +**Static games** are played simultaneously -- all players choose their strategies without knowing what others have chosen. Most pricing decisions, sealed-bid auctions, and market entry timing decisions approximate static games. The payoff matrix is the primary analytical tool. + +**Dynamic games** are played sequentially -- one player moves first, the next player observes that move and responds, and so on. Product launches, negotiation sequences, and competitive responses are dynamic games. The primary analytical tool is the game tree, analyzed through backward induction: start at the final decision point, determine the rational choice, then work backwards to determine optimal play at each preceding stage. + +The distinction matters because first-mover advantage and second-mover advantage are properties of dynamic games. A simultaneous game has no "first mover." Identifying whether a business situation is closer to a static or dynamic game determines which analytical tools apply. + +--- + +## Prompts + +**Prompt 1 -- Map Your Competitive Game:** +> I operate in [describe your market/industry]. Help me map the game theory structure of my competitive situation. Identify the key players (direct competitors, substitutes, adjacent entrants, platform owners, regulators), the strategies available to each, and the approximate payoffs. Present this as a payoff matrix for the two most important competitive interactions I face. Then identify the Nash equilibrium and explain whether it represents a good or bad outcome for my business. + +**Prompt 2 -- Find the Equilibrium in a Specific Decision:** +> I am facing this strategic decision: [describe decision, e.g., pricing change, market entry, partnership negotiation]. The other key player is [describe]. My available strategies are [list]. Their likely strategies are [list]. Help me construct the payoff matrix, find the Nash equilibrium, and assess whether I should play the equilibrium strategy or attempt to shift the game structure. Consider whether this is a static or dynamic game. + +**Prompt 3 -- Identify Dominated Strategies:** +> Here are the strategic options I am considering: [list all options]. For each, help me determine if any are dominated -- meaning there is always a better alternative regardless of what competitors do. Eliminate the dominated strategies and show me the simplified decision. Then identify my best response to each likely competitor action. + +**Prompt 4 -- Assess Multiple Equilibria:** +> My competitive situation appears to have multiple stable outcomes: [describe the possible equilibria]. Help me assess which equilibrium is most likely to prevail by applying the risk-control principle and the Pareto optimum principle. What would it take to shift the market from the risk-control equilibrium to the Pareto-optimal one? What commitments, signals, or structures would be required? + +--- + +## Use Cases + +**Validation-Stage SaaS Founder Choosing a Pricing Model** + +A B2B SaaS founder must choose between per-seat pricing and usage-based pricing. Two direct competitors face the same decision. If all three adopt per-seat pricing, customers compare on features and margins remain healthy. If one switches to usage-based while others charge per-seat, the switcher captures price-sensitive customers but compresses margins industry-wide. If all switch to usage-based, margins compress for everyone. Mapping this as a three-player game reveals that per-seat pricing is a Nash equilibrium only if no player has an incentive to defect. Analysis shows that the smallest competitor (the startup) has the strongest incentive to defect -- it gains market share by undercutting on price structure. The founder uses this insight to time the pricing model switch strategically, capturing share before competitors respond. + +**Growth-Stage Marketplace Evaluating Geographic Expansion** + +A two-sided marketplace operating in three cities must decide which of two new metros to enter next. A well-funded competitor faces the same decision. If both enter the same city, they split the market and burn cash competing for supply. If they enter different cities, each captures a local monopoly position. The game matrix reveals two Nash equilibria -- one where the startup enters City A and the competitor enters City B, and vice versa. The startup uses signaling (public announcements, early partnerships, office lease signings) to commit credibly to City A, steering the competitor toward City B and achieving the Pareto-optimal split. + +**Early-Traction Founder Negotiating with a Strategic Partner** + +A hardware startup needs a distribution partnership with one of two major retailers. Each retailer values exclusivity (higher payoff from being the sole distributor) but will accept non-exclusive terms rather than lose the deal entirely. The founder maps the negotiation as a dynamic game: she moves first by approaching both retailers simultaneously. Backward induction shows that each retailer's best response to a simultaneous approach is to offer competitive terms, because the alternative -- refusing and watching the competitor win exclusive access -- is worse. The dynamic game structure gives the founder leverage that a sequential approach would not. + +--- + +## Anti-Patterns + +1. **Treating all interactions as games against a single competitor.** Most markets involve multiple players with heterogeneous strategies, asymmetric information, and different payoff structures. Reducing a five-player market to a two-player matrix can miss critical dynamics -- particularly the role of complementors, regulators, or platform owners who shape the payoff structure without competing directly. + +2. **Assuming players are perfectly rational.** Game theory's predictions assume rational actors. Real competitors make emotional decisions, suffer from cognitive biases, and sometimes act against their own interests. The model identifies what rational actors would do, which is useful as a baseline -- but deviations from rationality are the norm, not the exception. Use the framework to identify the rational benchmark, then layer behavioral analysis on top. + +3. **Ignoring the distinction between one-shot and repeated games.** A strategy that is optimal in a single interaction may be destructive in a repeated game. Aggressive pricing that wins one quarter's market share may trigger retaliation that destroys profitability for years. Always determine whether the game repeats before selecting a strategy. + +4. **Confusing Nash equilibrium with the best outcome.** Nash equilibrium is the stable outcome, not necessarily the desirable one. The Coffee Shop example demonstrates this clearly: the equilibrium (both discount) is worse for both players than the cooperative outcome (both premium). Recognizing a bad equilibrium is the first step toward restructuring the game to escape it. + +5. **Mapping the game after the decision is made.** Game theory is a planning tool, not a post-hoc rationalization device. Constructing the payoff matrix after committing to a strategy produces confirmation bias, not strategic insight. The matrix should be built before the decision, when it can actually influence the choice. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Player identification | The most valuable use at this stage is identifying who the players in a prospective market actually are. Most idea-stage founders undercount competitors and ignore non-obvious players (platform owners, regulators, substitute providers). Map the full player set before committing. | +| Validation | Strategy enumeration | With the market chosen, enumerate all available strategies -- not just the obvious ones. Pricing models, distribution channels, positioning angles, and partnership structures are all strategic variables. The wider the strategy set, the more likely a dominant or advantageous strategy emerges. | +| Early Traction | Equilibrium assessment | Revenue data provides real payoff information. Update the theoretical payoff matrix with actual market responses. Determine whether the current competitive equilibrium is sustainable and desirable, or whether strategic action is needed to shift it. | +| Growth | Dynamic game analysis | Growth-stage competition is sequential, not simultaneous. Competitors observe and respond to each other's moves. Shift from static payoff matrices to dynamic game trees. Backward induction -- reasoning from the end state to determine optimal current moves -- becomes the primary tool. | +| Scale | Game design | At scale, the company has sufficient market power to reshape the game itself -- changing the available strategies, altering payoff structures through platform economics, or adding new players through ecosystem development. The focus shifts from playing the game well to designing a game that structurally favors the company. | + +--- + +## Output Template + +```markdown +# Game Theory Analysis + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Player Map + +| Player | Type | Key Strategies | Primary Objective | +|--------|------|---------------|-------------------| +| [Our Company] | Protagonist | [Strategy 1, Strategy 2] | [Objective] | +| [Competitor A] | Direct rival | [Strategy 1, Strategy 2] | [Objective] | +| [Player C] | [Platform/Regulator/etc.] | [Strategy 1, Strategy 2] | [Objective] | + +## Payoff Matrix (Primary Competitive Interaction) + +| | Competitor Strategy 1 | Competitor Strategy 2 | +|--|----------------------|----------------------| +| **Our Strategy 1** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | +| **Our Strategy 2** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | + +## Equilibrium Analysis + +- **Nash Equilibrium:** [Strategy combination] +- **Is the equilibrium desirable?** [Yes/No -- explain] +- **Dominant strategies identified:** [Yes/No -- which player, which strategy] +- **Dominated strategies eliminated:** [List] + +## Strategic Recommendation + +Given the equilibrium analysis: +1. [Primary strategic action] +2. [Contingency if competitor deviates] +3. [Opportunity to restructure the game] + +## Game Type Assessment +- **Static or Dynamic:** [Assessment and why] +- **One-shot or Repeated:** [Assessment and implications] +- **Information:** [Complete or incomplete] +``` + +--- + +## Related Skills + +- **[Prisoner's Dilemma and Cooperation](prisoners-dilemma-and-cooperation.md)** -- The most famous application of these fundamentals, explaining why rational actors consistently produce collectively irrational outcomes and how to escape the trap. +- **[Information Asymmetry](information-asymmetry.md)** -- Extends the framework to games where players hold different information, fundamentally altering equilibrium outcomes. +- **[First-Mover Strategy](first-mover-strategy.md)** -- Applies dynamic game analysis to the question of timing: when moving first wins, when waiting wins, and how to make commitments credible. +- **[Negotiation Game Theory](negotiation-game-theory.md)** -- Applies Nash equilibrium concepts specifically to bilateral bargaining, providing the mathematical foundation for splitting deal surplus. +- **[Porter's Five Forces](../frameworks/porters-five-forces.md)** -- Five Forces describes the structural dynamics of an industry; game theory explains the strategic logic that drives those dynamics and predicts how they evolve. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- Combines with game theory to project how different competitive strategies might unfold under multiple future conditions. diff --git a/plugins/foreman/content/skills/game-theory/information-asymmetry.md b/plugins/foreman/content/skills/game-theory/information-asymmetry.md new file mode 100644 index 0000000..b739315 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/information-asymmetry.md @@ -0,0 +1,258 @@ +--- +name: "information-asymmetry" +description: "Applies game theory concepts of asymmetric information to entrepreneurial decisions: the free rider problem in teams, adverse selection (Akerlof's lemons market), moral hazard in principal-agent relationships, and separating equilibrium as a solution mechanism. Use when diagnosing hiring failures, fundraising challenges, quality signaling problems, partnership trust issues, team incentive misalignment, or any situation where one party holds materially more information than the other." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - information-asymmetry + - adverse-selection + - moral-hazard + - free-rider + - signaling + - screening + - lemons-market + - incentive-design +related_skills: + - game-theory-fundamentals + - prisoners-dilemma-and-cooperation + - first-mover-strategy + - trust-equation + - emotional-intelligence + - delegation-and-empowerment + - employee-engagement-retention +author: "Fatih Guner" +--- + +# Information Asymmetry + +LEMON MARKET. In 1970, George Akerlof published a thirteen-page paper explaining why good used cars are almost impossible to sell at a fair price. The buyers cannot tell a reliable car from a wreck, so they offer the average price. Sellers of reliable cars find this insulting and withdraw. The average quality drops. Buyers adjust downward. More good sellers leave. The cycle continues until the market contains only lemons and the buyers who deserve them. Akerlof won the Nobel Prize for this observation, and it explains approximately half of every startup's commercial frustrations: why enterprise buyers default to incumbent vendors, why the best candidates reject lowball offers, why investors demand punitive terms, and why quality products lose to inferior competitors with louder marketing. The problem is never the product. The problem is that the other side cannot verify the product's quality -- and in the absence of verification, rational actors assume the worst. + +--- + +## The Framework + +### The Free Rider Problem: When Contribution Cannot Be Observed + +A free rider enjoys the output of collective effort without contributing proportionally. The game-theoretic structure is precise: when individual contributions are unobservable or unmeasurable, the rational strategy for each participant is to minimize effort while consuming the group's output. + +**The Boxed Pigs Game -- A Parable for Startup Teams** + +Consider a startup with two cofounders of different capabilities. A large task (pressing the switch) must be done for both to benefit. The senior cofounder (the "big pig") invests significant effort; the junior cofounder (the "small pig") waits. + +| | Junior Cofounder: Contributes | Junior Cofounder: Waits | +|--|------------------------------|------------------------| +| **Senior Cofounder: Contributes** | Senior gets 7, Junior gets 3 | Senior gets 6, Junior gets 4 | +| **Senior Cofounder: Waits** | Senior gets 10, Junior gets 0 | Both get 0 | + +The equilibrium: the senior cofounder contributes (because waiting means nothing happens), while the junior cofounder waits (because contributing yields less than waiting). The small player free-rides on the large player's effort -- not from malice, but from rational calculation. + +This dynamic recurs wherever contribution is unobservable: in engineering teams where individual output is hard to measure, in partnerships where one partner's network generates most of the deal flow, in open-source projects where large companies benefit from volunteer labor. Equal compensation in the presence of unequal effort is not a cultural problem. It is a game-theoretic certainty. + +**Solutions to the Free Rider Problem:** + +- **Performance-linked compensation.** Tie rewards to observable individual output, not group output. Equity vesting tied to milestones. Sales commissions. Engineering metrics (deployed features, not lines of code). +- **Small teams.** Free riding worsens as team size increases, because each individual's contribution becomes less visible. Amazon's "two-pizza team" rule is, whether intentionally or not, a game-theoretic intervention. +- **Transparency mechanisms.** Make contributions visible. Stand-ups, public dashboards, peer reviews, and open calendars all reduce the information asymmetry that enables free riding. + +### Adverse Selection: The Lemons Market + +Adverse selection occurs before a transaction is completed. When one party has private information about quality, and the other party cannot observe that quality, the market selects for low quality. + +**The Akerlof Mechanism, Applied to Startups:** + +Consider a market for enterprise software. Some products are genuinely excellent (worth $100K/year). Others are mediocre (worth $20K/year). The buyer cannot distinguish them before purchasing. + +| Step | What Happens | Market Effect | +|------|-------------|---------------| +| 1 | Buyers know average quality exists but cannot evaluate individual products | They offer the average price: $60K | +| 2 | Sellers of excellent products find $60K unacceptable | They leave the market or reduce investment in quality | +| 3 | Average quality drops (mostly mediocre products remain) | Buyers adjust expected value downward: $40K | +| 4 | More quality sellers exit | Market converges toward lemons | +| 5 | Equilibrium: low prices, low quality, low trust | Everyone loses -- especially the good products | + +This is adverse selection. The market selects adversely against quality because quality is unobservable. The mechanism explains a wide range of entrepreneurial difficulties: + +- **Hiring:** The best candidates have the most options and are least willing to accept generic offers. Standardized compensation attracts average talent and repels exceptional talent. +- **Fundraising:** Founders know their company's true potential; investors do not. Investors set terms that protect against the worst case (heavy liquidation preferences, anti-dilution), which rational founders of genuinely strong companies resist. The terms that close deals select for founders who are desperate or naive. +- **B2B sales:** Enterprise buyers cannot evaluate software quality before purchase. They default to recognized brands (IBM, Salesforce, Microsoft) not because those products are superior, but because the brand serves as a quality signal that reduces adverse selection risk. The phrase "nobody ever got fired for buying IBM" is an adverse selection survival strategy. + +### Solving Adverse Selection: Signaling and Screening + +Two mechanisms counteract adverse selection by reducing information asymmetry: + +**Signaling (Seller-Initiated).** The informed party takes a costly, observable action that credibly communicates quality. The cost is critical: the signal must be expensive enough that low-quality actors cannot afford to fake it. + +| Signal | Why It Works | Startup Application | +|--------|-------------|---------------------| +| Money-back guarantees | Only confident sellers offer them; lemons would lose money | Offering a 90-day full refund signals product quality | +| Prestigious investor names | Top-tier VCs screen heavily; their investment signals quality | Raising from Sequoia or a16z communicates more than the capital itself | +| Free trial / freemium | Quality products convert; poor products do not | The product speaks for itself before the buyer commits | +| Certifications and audits | Third-party verification is costly to obtain and hard to fake | SOC 2, ISO 27001, and security audits signal operational maturity | +| Transparency (open metrics) | Only companies with strong metrics would share them | Publishing NPS scores, churn rates, or uptime publicly | + +Michael Spence's signaling theory, which earned him a share of the 2001 Nobel Prize alongside Akerlof, established a key principle: education functions primarily as a signal in labor markets. A degree from a top university may not teach relevant skills, but it signals that the holder was capable of obtaining admission and completing the program -- a costly action that lower-ability candidates find prohibitively difficult. The same logic applies to any costly, observable, quality-correlated action. + +**Screening (Buyer-Initiated).** The uninformed party designs a choice architecture that causes the informed party to self-select, revealing their private information through their choices. + +| Screening Mechanism | How It Reveals Information | Business Application | +|--------------------|--------------------------|---------------------| +| Tiered pricing | Price-sensitive and premium buyers self-sort | SaaS tiers reveal willingness to pay and likely usage | +| Deductible options | Risk-tolerant and risk-averse customers self-sort | Insurance-style contracts with different risk-sharing splits | +| Vesting schedules | Committed founders stay; uncommitted ones leave | 4-year vesting reveals true long-term commitment | +| Trial projects | Capable vendors deliver; incapable ones fail | Paid pilot engagements screen vendor quality | +| Application complexity | Serious candidates complete the process; casual ones drop off | Detailed job applications and multi-stage interviews | + +### Separating Equilibrium: Designing Self-Sorting Mechanisms + +A separating equilibrium is the game-theoretic ideal: a market design where high-quality and low-quality actors voluntarily sort themselves into different visible categories, eliminating information asymmetry. + +The classic example is airline pricing. Business travelers (high willingness to pay, low price sensitivity) and leisure travelers (low willingness to pay, high price sensitivity) have different private information about their own value. Airlines create a separating equilibrium by offering two products: expensive flexible tickets and cheap restricted tickets. Business travelers self-select into the premium tier; leisure travelers self-select into the economy tier. The airline extracts maximum value from each segment without needing to identify individual customers. + +For entrepreneurs, the design principle is: create choice structures where different customer types, employee types, or partner types reveal their private information through the option they choose. Tiered pricing is the most common example, but the principle extends to hiring (compensation packages with different equity/salary ratios), fundraising (term sheet structures that attract different investor types), and partnerships (commitment levels that filter serious from speculative partners). + +### Moral Hazard: When Behavior Changes After the Deal + +Moral hazard occurs after a transaction is completed. Once one party bears a risk or cost on behalf of another, the second party's incentive to behave responsibly diminishes. + +The structure is a principal-agent problem: the principal (investor, employer, insurer) cannot perfectly observe the agent's (founder, employee, policyholder) behavior after the agreement is signed. + +**Moral Hazard in Startup Context:** + +| Relationship | Principal | Agent | Moral Hazard Risk | +|-------------|-----------|-------|------------------| +| Investor-Founder | Investor | Founder | Founder takes excessive risk with investor capital (upside captured by founder, downside borne by investor) | +| Founder-Employee | Founder | Employee | Employee reduces effort after equity grant vests or after receiving a raise | +| Client-Agency | Client | Marketing agency | Agency prioritizes billable hours over results | +| Insurer-Insured | Startup insurance provider | Startup | Startup takes less care with insured assets | + +**Solutions to Moral Hazard:** + +1. **Incentive alignment.** Structure compensation so the agent's interests mirror the principal's. Equity with performance vesting. Revenue-share contracts. Clawback provisions. The economist Hurwicz formalized this as the "incentive compatibility principle": design contracts so that the agent maximizes their own payoff by taking the action the principal wants. + +2. **Monitoring and transparency.** Board seats, reporting requirements, regular audits, and OKR reviews all reduce information asymmetry post-agreement. The cost of monitoring must be weighed against the cost of moral hazard it prevents. + +3. **Reputation in repeated games.** When the relationship is ongoing, the agent's future access to opportunities depends on current performance. This is why repeat founders raise capital more easily and on better terms -- their reputation serves as a credible bond against moral hazard. + +--- + +## Prompts + +**Prompt 1 -- Diagnose Information Asymmetry in Your Sales Process:** +> My company sells [describe product/service] to [describe buyer]. Our close rate is [X%], which is lower than expected given our product quality. Help me analyze this as an adverse selection problem. Where is the information asymmetry? What does the buyer not know that, if they knew it, would change their purchase decision? Then design a signaling strategy: what costly, credible signals can we send to differentiate our quality from competitors? Evaluate at least five potential signals (guarantees, trials, certifications, transparency, endorsements) and recommend the most effective ones for our situation. + +**Prompt 2 -- Design a Screening Mechanism for Hiring:** +> I need to hire [describe role] and I am concerned about adverse selection -- attracting candidates who interview well but underperform. Help me design a screening mechanism that causes candidates to self-sort by quality. Consider: compensation structure (salary vs. equity mix), application process design, trial periods, and reference check depth. For each mechanism, explain what information it reveals and what type of candidate it selects for or against. + +**Prompt 3 -- Assess Moral Hazard in a Partnership:** +> I am entering a [describe partnership/agreement: investment, outsourcing contract, cofounder arrangement, distribution deal]. Help me identify the moral hazard risks -- how might the other party's behavior change after the agreement is signed, given that I cannot perfectly observe their actions? Then design contractual and structural safeguards: what incentive alignment mechanisms, monitoring structures, and reputation consequences should be built into the agreement? + +**Prompt 4 -- Build a Separating Equilibrium for Your Market:** +> My market has both high-value and low-value [customers/vendors/partners], and I cannot easily tell them apart before committing resources. Help me design a separating equilibrium -- a choice architecture that causes the two types to self-sort. Consider tiered offerings, commitment requirements, pricing structures, and application processes. For each design, explain which type selects into which option and why. + +--- + +## Use Cases + +**Validation-Stage Marketplace Struggling with Supply Quality** + +A freelancer marketplace connects businesses with independent consultants. The platform faces severe adverse selection: businesses cannot evaluate consultant quality before hiring, so they gravitate toward the cheapest option. High-quality consultants, unable to charge premium rates on a platform that commoditizes their expertise, leave for direct client relationships. The founder diagnoses this as a lemons market and implements three interventions. First, a portfolio review and skills assessment that produces a visible quality score (signaling mechanism). Second, tiered pricing where consultants choose their own rate band, with the platform displaying the tier prominently (screening mechanism that creates separating equilibrium -- top consultants self-select into premium tiers). Third, outcome-based reviews weighted by project complexity, not just star ratings (reducing noise in the quality signal). Within two quarters, average project value increases by 60% and high-quality consultant retention improves from 40% to 72%. + +**Growth-Stage Enterprise SaaS Battling Incumbent Preference** + +A growth-stage cybersecurity startup with a technically superior product consistently loses enterprise deals to an established competitor whose product is widely acknowledged within the industry to be inferior. The founder recognizes this as an adverse selection problem: the CISO cannot verify the startup's quality claims, so they default to the known brand to minimize career risk. The startup constructs a signaling strategy with three layers. First, an independent security audit by a recognized firm, published publicly (costly third-party verification). Second, a "deploy or don't pay" trial -- the customer runs both products in parallel for 90 days and pays only if the startup's product outperforms (a guarantee only a genuinely superior product can sustain). Third, case studies with named enterprise customers who agreed to be referenced (social proof as costly signal -- customers stake their own reputation). The multi-layered signaling approach overcomes the adverse selection barrier, and win rates against the incumbent improve from 15% to 45% over six months. + +**Scale-Stage Company Designing Investor-Founder Alignment** + +A Series B company restructures its board governance to address moral hazard from both directions. The investors face moral hazard risk that the founder will pursue vanity projects with their capital. The founder faces moral hazard risk that the investors will force a premature exit to optimize their fund timeline. The CFO, trained in game-theoretic incentive design, proposes a symmetric alignment structure: milestone-based capital tranches (reducing investor exposure to founder moral hazard), combined with a founder-controlled board seat and anti-forced-sale provisions (reducing founder exposure to investor moral hazard). Both parties bear monitoring costs proportional to the risk they face. The structure creates incentive compatibility: the founder maximizes their payoff by hitting milestones (which is what investors want), while the investors maximize their payoff by supporting long-term value creation (which is what the founder wants). + +--- + +## Anti-Patterns + +1. **Assuming more information always helps.** Information has costs: acquisition cost, processing cost, and decision latency. Seeking perfect information before every hire, deal, or partnership is a form of analysis paralysis dressed in game-theoretic clothing. The goal is to reduce information asymmetry to the point where adverse selection no longer distorts the decision -- not to eliminate asymmetry entirely, which is usually impossible and always expensive. + +2. **Signaling without substance.** A signal works only if it is correlated with actual quality and costly enough to be difficult for low-quality actors to fake. Press releases, vanity metrics, and logo walls are cheap signals that sophisticated counterparties discount heavily. A money-back guarantee from a company that cannot afford to honor it is a bluff, not a signal. The cost must be real. + +3. **Designing screening mechanisms that select for the wrong traits.** Multi-stage interview processes that last six weeks screen for candidates who have six weeks to spare -- which may select against the best candidates, who have competing offers with deadlines. Every screening mechanism selects for something; the question is whether it selects for the trait that actually predicts performance. + +4. **Ignoring moral hazard in your own behavior.** Founders analyze investor moral hazard and employee moral hazard but rarely examine their own. Once funded, founders face reduced personal downside (the investors' money, not theirs) and increased optionality (pivot, extend runway, take a high salary). Recognizing moral hazard in yourself is the precondition for designing governance structures that keep all parties honest, including you. + +5. **Treating all information problems as adverse selection.** Adverse selection is a pre-transaction problem (the wrong types enter the market). Moral hazard is a post-transaction problem (behavior changes after the deal). The solutions are different. Signaling and screening address adverse selection. Incentive alignment and monitoring address moral hazard. Applying the wrong solution to the wrong problem is common and ineffective. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Overcoming adverse selection as the unknown entrant | At validation stage, the startup is the lemon until proven otherwise. Every buyer, partner, and hire applies an adverse selection discount. The primary task is constructing credible signals -- early customers, respected advisors, working demos -- that separate the startup from vaporware. | +| Early Traction | Building signaling infrastructure | With initial traction, the startup can invest in durable signals: customer case studies, third-party audits, public metrics dashboards. The cost of these signals is justified because they compound -- each new signal reduces the adverse selection discount permanently. | +| Growth | Managing moral hazard across the organization | As headcount grows, moral hazard scales. Each new hire, vendor, and partner introduces a principal-agent relationship with monitoring costs. Incentive design (compensation structures, vesting schedules, performance systems) becomes a core organizational capability, not an HR afterthought. | +| Scale | Designing market-level separating equilibria | At scale, the company can shape market structures that create separating equilibria: tiered products, certification programs, partner tiers, and quality standards that cause participants to self-sort by capability. This is market design, not just company strategy. | + +--- + +## Output Template + +```markdown +# Information Asymmetry Analysis + +**Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Asymmetry Map + +| Relationship | Who Knows More | What They Know | Consequence If Unaddressed | +|-------------|---------------|---------------|--------------------------| +| [Relationship 1] | [Party] | [Private information] | [Adverse selection / Moral hazard risk] | +| [Relationship 2] | [Party] | [Private information] | [Adverse selection / Moral hazard risk] | + +## Pre-Transaction Risk (Adverse Selection) + +- **Where is adverse selection occurring?** [Description] +- **What quality signal is missing?** [Description] +- **Current cost of adverse selection:** [Quantified if possible -- lost deals, talent flight, pricing compression] + +## Signaling Strategy + +| Signal | Cost to Implement | Credibility Level | Expected Impact | +|--------|------------------|------------------|----------------| +| [Signal 1] | [Cost] | [High/Medium/Low] | [Impact] | +| [Signal 2] | [Cost] | [High/Medium/Low] | [Impact] | + +## Screening Mechanism Design + +| Mechanism | What It Reveals | Who It Selects For | Who It Selects Against | +|-----------|----------------|-------------------|----------------------| +| [Mechanism 1] | [Information] | [Type] | [Type] | +| [Mechanism 2] | [Information] | [Type] | [Type] | + +## Post-Transaction Risk (Moral Hazard) + +- **Principal-agent relationships at risk:** [List] +- **Monitoring mechanisms in place:** [List] +- **Incentive alignment gaps:** [List] + +## Recommended Actions +1. [Highest-priority signaling investment] +2. [Screening mechanism to implement] +3. [Moral hazard safeguard to establish] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](game-theory-fundamentals.md)** -- Provides the foundational concepts (players, strategies, payoffs, equilibrium) that underpin information asymmetry analysis. +- **[Prisoner's Dilemma and Cooperation](prisoners-dilemma-and-cooperation.md)** -- Information asymmetry makes cooperation harder: when you cannot observe whether the other party is cooperating or defecting, the dilemma deepens. +- **[First-Mover Strategy](first-mover-strategy.md)** -- Information asymmetry often determines whether the first or second mover has the advantage; the party with more information can time moves more effectively. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust is the behavioural antidote to information asymmetry; the trust equation identifies the specific components that reduce the information gap in relationships. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- Every act of delegation creates a principal-agent relationship with moral hazard risk; effective delegation requires the incentive alignment mechanisms analysed here. +- **[Negotiation Mindset and Self-Management](../negotiation/negotiation-mindset-and-self.md)** -- The assumption audit in negotiation preparation is fundamentally an information asymmetry assessment: what do I know, what do they know, and where are the gaps? diff --git a/plugins/foreman/content/skills/game-theory/negotiation-game-theory.md b/plugins/foreman/content/skills/game-theory/negotiation-game-theory.md new file mode 100644 index 0000000..34c5702 --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/negotiation-game-theory.md @@ -0,0 +1,255 @@ +--- +name: "negotiation-game-theory" +description: "Structures negotiations as formal games with mathematically defined bottom lines, solution sets, and optimal agreement points using the Nash Product Solution. Provides the strategic and quantitative complement to relationship-based negotiation frameworks. Use when calculating walk-away points for fundraising rounds, modelling acquisition pricing, determining fair splits in partnership deals, preparing for salary or compensation negotiations, structuring vendor contracts with measurable payoffs, or analysing why a negotiation reached a specific outcome." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - nash-product + - bottom-line + - deal-making + - zopa + - game-theory + - term-sheets + - pricing +related_skills: + - coalition-and-partnership-games + - evolutionary-strategy + - win-win-negotiation + - trust-equation + - cialdini-influence +author: "Fatih Guner" +--- + +# Negotiation Game Theory + +Every negotiator has a mathematical bottom line -- the minimum outcome they will accept before walking away. Most never calculate it. They arrive at the table armed with aspirations and anxiety, anchoring on round numbers or gut feelings, when the strategic structure of the negotiation is already fully determined by three quantities: what each side gets if the deal fails, what the deal creates if it succeeds, and how each side values incremental gains. Finding the other party's bottom line -- their true minimum acceptable outcome -- is worth more than any persuasion technique, any rapport-building exercise, any tactical concession. The relationship-based approach taught by Fisher and Ury (see [Win-Win Negotiation](../frameworks/win-win-negotiation.md)) handles the human dynamics superbly. This skill addresses the strategic geometry underneath. + +--- + +## The Framework + +### Negotiation as a Cooperative Game + +A negotiation between two parties, A and B, is a cooperative game with a specific structure. If the negotiation succeeds, it produces a total payoff that exceeds what either party could achieve alone. If it fails, each party falls back to their standalone value -- what they can earn without the other. + +Three values define every negotiation: + +| Variable | Meaning | Example (Series A Fundraise) | +|----------|---------|------------------------------| +| **Total deal value** | What the cooperation produces | $20M company valuation created by capital + execution | +| **A's standalone value** | What A gets if the deal fails | Founder bootstraps at $2M valuation growth/year | +| **B's standalone value** | What B gets if the deal fails | Investor deploys capital elsewhere at 15% expected return | + +The fundamental precondition for any negotiation: the deal must create surplus. The total deal value must exceed the sum of both parties' standalone values. If it does not, there is nothing to negotiate -- both sides are better off walking away. This seems obvious, yet founders regularly enter negotiations where no surplus exists (the investor's alternative returns exceed what the startup can plausibly deliver, or the customer's internal solution outperforms the vendor's offering). + +### The Objective Bottom Line + +The bottom line is not what you hope to get. It is the minimum you must receive for the negotiation to be rational. + +**A's objective bottom line:** A must receive at least their standalone value from the deal. If the negotiated outcome gives A less than what A could achieve alone, A should walk away. + +**B's objective bottom line:** B must receive at least their standalone value. The remaining deal surplus -- total value minus B's standalone -- is the maximum A can rationally claim. + +The **negotiation range** (equivalent to ZOPA in Fisher and Ury's framework, but defined mathematically) is the interval between each party's bottom line: + +- A's payoff ranges from A's standalone value (minimum) to total value minus B's standalone (maximum) +- B's payoff ranges from B's standalone value (minimum) to total value minus A's standalone (maximum) + +**A practical illustration:** + +A SaaS startup (A) negotiates a distribution partnership with a major platform (B). + +- Partnership total value: $3M additional annual revenue +- Startup's standalone growth without partnership: $800K annual revenue +- Platform's standalone value from alternative integration partner: $600K annual revenue + +Negotiation range: +- Startup receives between $800K and $2.4M ($3M - $600K) +- Platform receives between $600K and $2.2M ($3M - $800K) + +Any split within this range is rational for both parties. Any split outside it means at least one party would be better off alone -- and will eventually realise it. + +### The Solution Set + +When the negotiation range is not a single point but an interval (the common case), many possible agreements exist. The set of all mutually acceptable outcomes is the **solution set**. Within it, every point represents a deal both parties prefer to their standalone alternative. + +The solution set's size reveals the negotiation's character: + +| Solution Set Size | Interpretation | Negotiation Dynamic | +|-------------------|---------------|---------------------| +| **Large interval** | Significant surplus to divide | Both parties have strong incentive to agree; conflict is about distribution, not feasibility | +| **Narrow interval** | Small surplus | Agreement is fragile; minor miscalculations or emotional friction can collapse the deal | +| **Single point** | Exact one outcome satisfies both | No room to negotiate; take it or leave it | +| **Empty set** | Bottom lines do not overlap | No deal is possible; negotiation should not begin | + +Experienced negotiators assess the solution set before entering the room. If the set is large, they focus on capturing a favourable position within it. If narrow, they focus on ensuring the deal closes at all. If empty, they decline the meeting. + +### The Nash Product Solution + +With many possible agreements in the solution set, which one should the parties select? John Nash (Nobel Prize, 1994) proposed an elegant answer: choose the agreement that maximises the product of both parties' gains over their standalone values. + +The principle in plain language: the optimal deal is the one where the product of "how much better off A is versus walking away" times "how much better off B is versus walking away" is largest. + +**Why the product, not the sum?** Maximising the sum would favour whichever party has a larger absolute gain, regardless of proportionality. The product inherently balances both parties' interests -- it penalises deals that give one side almost everything and the other almost nothing, because a near-zero factor kills the product. + +**Decision table for the partnership example above:** + +| A's Payoff | B's Payoff | A's Gain Over Standalone | B's Gain Over Standalone | Nash Product | +|-----------|-----------|-------------------------|-------------------------|-------------| +| $800K | $2,200K | $0 | $1,600K | 0 | +| $1,200K | $1,800K | $400K | $1,200K | 480,000 | +| $1,500K | $1,500K | $700K | $900K | 630,000 | +| $1,700K | $1,300K | $900K | $700K | **630,000** | +| $1,800K | $1,200K | $1,000K | $600K | 600,000 | +| $2,400K | $600K | $1,600K | $0 | 0 | + +The Nash Product is maximised at $1,500K/$1,500K and $1,700K/$1,300K (both yield 630,000). When both parties have symmetric utility functions (each dollar is worth the same to both), the Nash solution converges toward an even split of the surplus. When utility functions differ -- and they often do -- the solution shifts toward the party for whom each marginal dollar matters more. + +### Asymmetric Utility and Its Practical Consequences + +Parties rarely value money identically. A cash-strapped startup values the first $500K of a deal far more than the second $500K (diminishing marginal utility, or more practically, the difference between survival and comfort). A well-capitalised corporation may have nearly linear utility -- each dollar is worth roughly the same. + +This asymmetry shifts the Nash Product Solution. The party with higher marginal utility for early gains (the startup) rationally accepts a smaller total share, because the utility they extract from it is disproportionately high. The party with lower marginal utility (the corporation) captures a larger nominal share but extracts proportionally less utility. + +The strategic implication: **reducing your desperation -- increasing your standalone value or decreasing your marginal utility for the deal -- shifts the Nash solution in your favour.** This is the game-theoretic foundation for why having alternatives (a strong BATNA, in Fisher and Ury's language) is the single most powerful negotiation lever. It is not psychology. It is mathematics. + +### Connecting the Two Negotiation Frameworks + +| Dimension | Win-Win Negotiation (Fisher & Ury) | Negotiation Game Theory | +|-----------|------------------------------------|------------------------| +| Core question | "What are the interests behind the positions?" | "What are the payoff functions and standalone values?" | +| Power source | BATNA (best alternative) | Standalone value and utility function | +| Zone of agreement | ZOPA (qualitative overlap of interests) | Solution set (quantitative interval of mutually rational outcomes) | +| Optimal outcome | Mutual gain through creative options | Nash Product maximisation | +| Primary tool | Empathy, interests, objective criteria | Payoff analysis, utility estimation, marginal contribution | +| Blind spot | Assumes parties can discover mutual gains through dialogue | Assumes payoffs are quantifiable and utility functions are known | + +Neither framework is sufficient alone. Fisher and Ury's approach excels at expanding the pie through creative option generation and managing the relational dimension. Game theory excels at analysing how to divide the pie once its size is established. The sophisticated negotiator prepares with both. + +--- + +## Prompts + +**Prompt 1 -- Bottom Line Calculation:** +> I am entering a negotiation with [describe the other party] regarding [describe the deal]. Help me calculate my objective bottom line using negotiation game theory. My standalone value (what I get if this deal fails) is approximately [estimate]. The other party's standalone is approximately [estimate]. The total value the deal would create is approximately [estimate]. Calculate the solution set, identify the Nash Product Solution assuming symmetric utility, and then adjust for any utility asymmetries I should consider: [describe any cash constraints, time pressure, or other factors affecting how each side values marginal gains]. + +**Prompt 2 -- Opponent Bottom Line Estimation:** +> I am negotiating [describe deal] with [describe party]. I need to estimate their objective bottom line. Here is what I know about their situation: [describe their alternatives, financial position, time pressure, and strategic priorities]. Using negotiation game theory, help me estimate: (1) their standalone value if this deal fails, (2) their likely utility function (linear, concave, or convex -- do they value early gains more or less?), (3) their probable bottom line, and (4) the Nash Product Solution given my estimates. Where are the biggest uncertainties in my estimate, and what questions should I ask to narrow them? + +**Prompt 3 -- Deal Structure Optimisation:** +> We have a preliminary agreement in a negotiation, but I want to evaluate whether the terms are close to the Nash Product optimum. The deal terms are: [describe]. My standalone alternative: [describe]. Their standalone alternative (estimated): [describe]. Total deal value: [estimate]. Calculate whether the current split is near the Nash optimum, whether I am leaving significant value on the table, and what restructuring (if any) would move the deal closer to the mathematically optimal point while remaining acceptable to both parties. + +**Prompt 4 -- Multi-Issue Negotiation Mapping:** +> I am negotiating a deal with multiple issues: [list issues -- e.g., price, payment terms, exclusivity, service levels, IP ownership]. For each issue, estimate the payoff implications for both sides and identify where utility asymmetries create trade opportunities. Using game theory principles, help me construct a package deal that maximises the overall Nash Product by trading low-cost/high-value items across issues. + +--- + +## Use Cases + +**Validation-Stage: Negotiating a Seed Term Sheet** + +A pre-revenue startup receives a term sheet from an angel syndicate. The proposed terms: $500K at a $4M pre-money valuation (the syndicate gets 11.1%). The founder's standalone: continue bootstrapping with $50K in savings, reaching an estimated $1.5M valuation in 18 months. The syndicate's standalone: deploy the $500K across three other deals with an expected 2.5x return. + +Total deal value if the investment succeeds: $10M estimated valuation at Series A (18 months out). The founder's share at the proposed terms: $8.9M. The syndicate's share: $1.1M. + +The solution set: founder receives between $1.5M (standalone) and $8.75M ($10M minus syndicate's $1.25M alternative return). The syndicate receives between $1.25M and $8.5M. + +Nash Product analysis reveals the proposed terms ($8.9M / $1.1M) are heavily founder-favourable -- the syndicate's gain over standalone is only $1.1M - $1.25M = negative. The syndicate is actually worse off than their alternative. The term sheet, paradoxically, should not exist at these terms unless the syndicate's actual expected return from alternatives is lower than 2.5x, or the startup's expected Series A outcome is higher than $10M. The framework forces both parties to examine whether the deal creates genuine surplus. + +**Growth-Stage: Acquisition Offer Analysis** + +A $30M ARR SaaS company receives a $150M acquisition offer from a strategic buyer. The founder's standalone: continue growing at 40% annually toward an IPO at $500M+ in three years. The acquirer's standalone: build a competing product for $20M over two years, reaching 30% of the target's capability. + +Total deal value: the acquirer gains $150M in strategic value (the target's product plus customer base integrated into the acquirer's platform). The founder's standalone is high ($500M IPO possibility) but risky. The acquirer's standalone is low ($20M build cost but uncertain outcome). + +Adjusting for risk and time value, the founder's risk-adjusted standalone is approximately $200M (discounting the $500M IPO by execution risk and time preference). The acquirer's standalone is approximately $40M (build cost plus opportunity cost). + +Solution set: founder receives between $200M and $110M... this is inverted. The founder's standalone ($200M risk-adjusted) exceeds the offer ($150M). The solution set is empty at the proposed price. The acquisition should not proceed at $150M unless the founder's risk adjustment is more aggressive (higher discount for execution risk) or the acquirer's total value creation is higher than estimated. The framework clarifies that the deal only makes sense above approximately $200M -- a number no amount of persuasion can change. + +--- + +## Anti-Patterns + +1. **Negotiating Without Calculating Your Bottom Line.** Entering a negotiation knowing what you want but not what you need. The bottom line is not an aspiration -- it is the mathematical boundary below which the deal is worse than no deal. Founders who cannot articulate their standalone value in quantitative terms are negotiating blind. + +2. **Assuming Symmetric Utility.** Treating every dollar as equally valuable to both sides. A venture fund deploying $2M from a $200M fund has nearly linear utility for the deal's outcome. A founder whose personal savings depend on the deal has sharply concave utility. Ignoring this asymmetry leads to agreements that the Nash Product Solution would reject. + +3. **Confusing the Solution Set with the Optimal Point.** Accepting any deal within the solution set as "good enough." Every point in the solution set is rational, but they are not equivalent. A deal at the edge of the solution set gives one party almost nothing over their standalone -- technically rational but practically fragile. The Nash Product Solution identifies the robust centre. + +4. **Applying Game Theory Without Relationship Management.** Using quantitative analysis as a substitute for Fisher and Ury's relational principles. Telling your counterpart "the Nash Product Solution suggests I should receive 62% of the surplus" is technically accurate and interpersonally catastrophic. Game theory informs your preparation and internal decision-making. The relationship framework governs how you conduct the conversation. + +5. **Overestimating Your Standalone Value.** Inflating what you could achieve without the deal, which raises your calculated bottom line and may cause you to reject value-creating agreements. Rigorous honesty about alternatives is essential. The founder who claims a $50M standalone valuation but has no term sheets and declining metrics is deluding themselves -- and the mathematics will not compensate for self-deception. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | First deals with uncertain values | Standalone values and deal values are highly speculative. Use ranges rather than point estimates. Calculate the solution set for best-case, base-case, and worst-case scenarios. If the solution set is empty in the base case, the deal is likely not viable. | +| Early Traction | Hiring, early partnerships, first revenue contracts | Payoffs become partially measurable. Use actual revenue data and market benchmarks to ground standalone estimates. The Nash framework is particularly useful for compensation negotiations -- equity grants should reflect the marginal contribution the hire brings. | +| Growth | Fundraising, enterprise sales, strategic partnerships | Both parties have established track records. Standalone values are estimable from comparable transactions, market data, and financial projections. This is where the framework is most directly applicable -- sufficient data exists to compute meaningful solution sets. | +| Scale | M&A, large-scale licensing, public-market transactions | Negotiations involve professional advisors (investment bankers, lawyers) who use variants of these models already. The founder's role shifts from performing the analysis to understanding and challenging the analysis their advisors present. Fairness opinions and valuation models are essentially applied Nash bargaining theory. | + +--- + +## Output Template + +```markdown +# Negotiation Analysis: [Deal Description] + +## Parties +- **Party A:** [Name/Description] +- **Party B:** [Name/Description] + +## Standalone Values +| Party | Standalone Value | Basis for Estimate | Confidence | +|-------|-----------------|-------------------|------------| +| A | [Value if deal fails] | [How estimated] | [High/Medium/Low] | +| B | [Value if deal fails] | [How estimated] | [High/Medium/Low] | + +## Deal Value +- **Total value if deal succeeds:** [Amount] +- **Surplus over standalone sum:** [Deal value - A standalone - B standalone] +- **Surplus exists?** [Yes/No -- if No, stop here] + +## Solution Set +- **A's range:** [A standalone] to [Deal value - B standalone] +- **B's range:** [B standalone] to [Deal value - A standalone] +- **Solution set size:** [Large / Narrow / Single point / Empty] + +## Nash Product Solution +| Scenario | A's Payoff | B's Payoff | A's Gain | B's Gain | Nash Product | +|----------|-----------|-----------|---------|---------|-------------| +| Proposed terms | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | +| Nash optimum (symmetric) | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | +| Nash optimum (adjusted for utility) | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | + +## Utility Asymmetries +- **A's utility profile:** [Linear / Concave / Convex -- and why] +- **B's utility profile:** [Linear / Concave / Convex -- and why] +- **Effect on optimal split:** [Description] + +## Strategic Recommendations +1. [Key insight from the analysis] +2. [Recommended negotiation approach] +3. [Risk factors and contingencies] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- The essential relational complement; Fisher and Ury's framework excels at expanding the pie, while game theory determines how to divide it. +- **[Coalition and Partnership Games](coalition-and-partnership-games.md)** -- When negotiations involve more than two parties, the Shapley Value and core stability concepts from coalitional game theory apply. +- **[Evolutionary Strategy](evolutionary-strategy.md)** -- Repeated negotiations across a market follow evolutionary dynamics; understanding whether the market rewards hawks or doves informs negotiation posture. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- Influence principles operate within the solution set identified by game theory; reciprocity and anchoring shift outcomes within the mathematically defined range. +- **[Competitive Negotiation](../negotiation/competitive-negotiation.md)** -- Translates the mathematical Nash Product Solution into practical anchoring, concession, and value-claiming tactics at the negotiating table. +- **[Game Theory Fundamentals](game-theory-fundamentals.md)** -- Provides the prerequisite concepts of Nash equilibrium and payoff analysis that bargaining-specific models build upon. diff --git a/plugins/foreman/content/skills/game-theory/prisoners-dilemma-and-cooperation.md b/plugins/foreman/content/skills/game-theory/prisoners-dilemma-and-cooperation.md new file mode 100644 index 0000000..e3b3e9c --- /dev/null +++ b/plugins/foreman/content/skills/game-theory/prisoners-dilemma-and-cooperation.md @@ -0,0 +1,227 @@ +--- +name: "prisoners-dilemma-and-cooperation" +description: "Analyzes the Prisoner's Dilemma and related non-cooperative game structures that cause rational actors to produce collectively suboptimal outcomes. Covers price war dynamics via the Cournot duopoly model, the Tragedy of the Commons for shared resources, and mechanisms for escaping destructive equilibria through repeated games, reputation, and contracts. Use when facing price wars, market overcrowding, shared resource conflicts, cofounder tensions, or any situation where individual incentives conflict with collective benefit." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - prisoners-dilemma + - cooperation + - price-wars + - tragedy-of-the-commons + - competition + - collective-action + - market-dynamics +related_skills: + - game-theory-fundamentals + - information-asymmetry + - first-mover-strategy + - porters-five-forces + - win-win-negotiation + - thomas-kilmann-conflict + - trust-equation +author: "Fatih Guner" +--- + +# Prisoner's Dilemma and Cooperation + +BETRAYAL MATH. Two rational people, acting in pure self-interest, will consistently choose the option that hurts them both. This is not a paradox of human psychology -- it is a mathematical certainty. The Prisoner's Dilemma, formulated by Albert Tucker in 1950, demonstrates that individual rationality and collective rationality can be fundamentally opposed. Every price war, every race-to-the-bottom in a crowded market, every cofounder relationship that collapses into mutual suspicion follows the same structural logic. Understanding why the trap exists is the first step toward escaping it. The second step -- and the one most entrepreneurs skip -- is recognizing which structural conditions make escape possible and which make it impossible. + +--- + +## The Framework + +### The Classic Prisoner's Dilemma + +Two suspects are arrested. The police separate them and offer each the same deal: + +| | Suspect B: Stay Silent | Suspect B: Confess | +|--|----------------------|-------------------| +| **Suspect A: Stay Silent** | Both serve 1 year | A serves 10 years, B goes free | +| **Suspect A: Confess** | A goes free, B serves 10 years | Both serve 8 years | + +The logic is merciless. If B stays silent, A is better off confessing (freedom vs. 1 year). If B confesses, A is still better off confessing (8 years vs. 10 years). Confessing is the dominant strategy for both. The Nash equilibrium is (Confess, Confess) -- both serve 8 years. Yet both would prefer (Silent, Silent) -- 1 year each. Individual rationality destroys collective benefit. + +This structure is not an abstract curiosity. It is the default architecture of competition. + +### The Entrepreneur's Prisoner's Dilemma: Price Wars + +Translate the matrix into business terms. Two competing SaaS companies serving the same market must choose between maintaining prices and cutting prices. + +| | Competitor: Maintain Price | Competitor: Cut Price | +|--|--------------------------|---------------------| +| **Your Startup: Maintain Price** | Both earn healthy margins (profit: 500K each) | You lose customers, they gain share (you: 150K, them: 700K) | +| **Your Startup: Cut Price** | You gain customers, they lose share (you: 700K, them: 150K) | Both earn razor-thin margins (profit: 250K each) | + +The dominant strategy for each firm is to cut prices. The equilibrium (250K, 250K) is stable but destructive. Both would prefer the cooperative outcome (500K, 500K), but neither can unilaterally choose it without risking the worst outcome (150K). + +This is every price war ever fought. Not because entrepreneurs are stupid, but because the incentive structure makes cooperation individually irrational. + +### The Cournot Duopoly: How Price Wars Actually Work + +The Prisoner's Dilemma captures the binary choice. The Cournot model captures the continuous dynamic -- how two firms producing a similar product settle into an equilibrium output level that is worse for both than the cooperative alternative. + +The mechanism, stripped of mathematics: when two competitors independently decide how much to produce (or how aggressively to price), each firm's optimal output depends on what the other firm does. Each firm produces more than the cooperatively optimal level, because restricting output unilaterally means surrendering market share. The result: total industry output exceeds the level that maximizes total industry profit. Both firms earn less than they would under cooperation. + +**The Cournot outcome in practical terms:** + +| Scenario | Each Firm's Share of Maximum Possible Profit | +|----------|---------------------------------------------| +| Monopoly (one firm, full market) | 100% | +| Cooperative duopoly (two firms, coordinated) | 50% of a larger pie -- roughly 62.5% of monopoly profit each | +| Competitive duopoly (Cournot equilibrium) | Roughly 44% of monopoly profit each | +| Aggressive price war (below Cournot) | Diminishing toward zero | + +The gap between cooperative and competitive outcomes is the "cost of non-cooperation." In mature markets with two or three dominant players, this cost can represent billions in forfeited profit annually. Airlines, telecom providers, and cloud infrastructure companies all live in this gap. + +### The Tragedy of the Commons: When Many Players Compete + +The Prisoner's Dilemma involves two players. The Tragedy of the Commons, articulated by Garrett Hardin in 1968, extends the logic to many players sharing a finite resource -- and the results are worse. + +The mechanism: each individual gains the full benefit of exploiting a shared resource but bears only a fraction of the cost of that exploitation. A fisherman who catches one extra fish gains the entire value of that fish but depletes the stock by an amount shared across all fishermen. The rational individual response is to maximize personal exploitation. When everyone does this, the resource collapses. + +**The Entrepreneurial Tragedy of the Commons:** + +| Shared Resource | Players | Exploitation Pattern | Collapse Symptom | +|-----------------|---------|---------------------|-----------------| +| Customer attention in a market | All startups in the space | Each startup increases marketing spend to capture attention | Customer acquisition costs rise until the market becomes unprofitable for everyone | +| Open-source ecosystem | Companies building on OSS | Each company consumes without contributing | Critical projects become undermaintained; ecosystem degrades | +| VC funding in a hot sector | All funded startups in the sector | Each company burns cash to grow faster than competitors | Sector "winter" when funding dries up; most companies die | +| Talent pool in a city | Competing employers | Each company raises salaries to attract talent | Compensation hyperinflation; profitability erodes for all | + +A critical finding from the extended analysis: the more players involved, the worse the outcome. As the number of competitors increases, the equilibrium point shifts further from the collective optimum and closer to total resource depletion. Two firms in a market can sometimes sustain near-cooperative outcomes through implicit coordination. Twenty firms cannot. This is the mathematical justification for the common startup strategy of pursuing markets with few competitors: fewer players means the equilibrium is closer to the cooperative optimum. + +### Escaping the Dilemma: Five Structural Mechanisms + +The Prisoner's Dilemma is not destiny. Specific structural conditions transform non-cooperative games into sustainable cooperation. + +**1. Repetition (The Shadow of the Future).** In a one-shot game, defection is always rational. In a repeated game, the calculus changes. If players know they will interact again -- and the future interactions are sufficiently valuable -- cooperation becomes sustainable. The key parameter is the "shadow of the future": the present value of all future interactions relative to the immediate gain from defection. When the shadow is long (ongoing customer relationships, repeat negotiations, industry reputation), cooperation emerges. When it is short (one-time transactions, terminal negotiations, exit scenarios), defection dominates. + +**2. Reputation and Transparency.** When actions are visible and reputations persist, defection carries a long-term cost that exceeds the short-term gain. This is why markets with high transparency (public pricing, review systems, industry gossip networks) sustain more cooperation than opaque markets. Entrepreneurs building reputation early create a cooperation-enabling asset. + +**3. Enforceable Contracts.** The most direct escape from the dilemma: a binding agreement with penalties for defection. Non-compete clauses, exclusive distribution agreements, and minimum advertised pricing (MAP) policies all function as game-theoretic commitment devices. The contract changes the payoff matrix by adding a cost to defection. + +**4. Reducing the Number of Players.** The commons tragedy worsens with each additional player. Consolidation, exclusive partnerships, and niche focus all reduce the effective number of players. Two firms can sustain implicit cooperation; twenty cannot. Market structure that limits the player count inherently enables better equilibria. + +**5. Changing the Payoff Structure.** Sometimes the game itself can be redesigned. Joint ventures, revenue-sharing agreements, platform ecosystems, and industry standards all alter the payoff matrix so that cooperation becomes individually rational rather than requiring sacrifice. The most elegant solutions make defection unprofitable rather than merely discouraged. + +--- + +## Prompts + +**Prompt 1 -- Diagnose a Price War:** +> My company is in [describe market], and we are experiencing price compression from competitors. Help me map this as a Prisoner's Dilemma. Identify the players, their strategies, and the approximate payoffs for each combination. Then assess: is this a one-shot game or a repeated game? What is the "shadow of the future" -- how much do ongoing interactions matter? Based on the game structure, recommend whether to compete on price, differentiate to exit the game entirely, or pursue one of the five escape mechanisms (repetition, reputation, contracts, player reduction, payoff restructuring). + +**Prompt 2 -- Identify Tragedy of the Commons in Your Market:** +> My market has [number] competitors all competing for [describe shared resource: customer attention, talent, VC funding, etc.]. Help me analyze this as a Tragedy of the Commons. How far is the current equilibrium from the cooperative optimum? How does the number of competitors affect the outcome? What structural changes could move the equilibrium toward a better outcome for my company specifically -- even if the market as a whole remains competitive? + +**Prompt 3 -- Design a Cooperation Structure:** +> I want to establish cooperative dynamics with [describe: competitor, partner, cofounder, supplier]. Help me design the structural conditions for sustainable cooperation. Analyze: Is the interaction repeated or one-shot? Is the payoff transparent or opaque? Can contracts enforce cooperation? Can the number of involved parties be reduced? Present a specific mechanism design that makes cooperation individually rational for all parties. + +**Prompt 4 -- Evaluate Cofounder Dynamics as a Game:** +> My cofounder and I are facing a strategic disagreement about [describe: equity split, role division, resource allocation, pivot decision]. Map this as a two-player game. What are the strategies available to each of us? What are the payoffs for each combination? Where is the Nash equilibrium, and is it a good outcome? If not, what structural changes to our partnership (vesting schedules, decision-making protocols, third-party governance) could shift us toward a better equilibrium? + +--- + +## Use Cases + +**Early-Traction Delivery Startup Facing a Subsidy War** + +Three venture-backed food delivery startups operate in the same metropolitan area. Each subsidizes customer orders to capture market share -- offering discounts that exceed the actual delivery cost. The game structure is a multi-player Prisoner's Dilemma: each company's individually rational strategy is to subsidize more aggressively than competitors, but the collective result is that all three burn cash faster than necessary, training customers to expect below-cost pricing. The founder analyzes the game and recognizes two escape paths. First, she narrows geographic focus to three neighborhoods where her company has the strongest supply density, effectively reducing the game from three-player to near-monopoly in those zones. Second, she shifts the competition axis from price subsidy to delivery speed -- changing the payoff structure so that the game is no longer purely about who offers the biggest discount. + +**Growth-Stage B2B Company in a Feature War** + +Two competing project management tools for construction companies have entered a feature war -- each copying the other's features within weeks of release. The result is that neither achieves sustainable differentiation, and both spend engineering resources on features that cancel each other out rather than advancing the product category. The CTO maps this as an iterated Prisoner's Dilemma and calculates that the "shadow of the future" is long: both companies expect to compete for years, the market is transparent (features are publicly visible), and customer switching costs are moderate. She proposes an implicit cooperation strategy: instead of matching every competitor feature, focus engineering on a distinct product dimension (mobile-first vs. desktop-first) and signal this strategic direction publicly. By committing visibly to a different lane, she converts a zero-sum feature war into a differentiated market where both companies can earn healthy margins. + +**Scale-Stage Platform Managing Ecosystem Competition** + +A developer platform with 2,000 third-party applications observes a Tragedy of the Commons: developers competing for the same user attention oversaturate certain categories, degrading discovery quality for users and profitability for developers. The platform CEO applies the commons framework and implements three interventions. First, category-specific application caps that limit the number of players per niche (reducing n). Second, a revenue-sharing model that rewards quality over quantity (changing the payoff structure). Third, transparent performance metrics that make reputation visible and consequential (enabling reputation-based cooperation). Within six months, developer revenue per application increases by 40%, and user satisfaction scores in the affected categories recover. + +--- + +## Anti-Patterns + +1. **Assuming the dilemma is inescapable.** The Prisoner's Dilemma only traps players when the game is one-shot, anonymous, and structurally fixed. Most business interactions are repeated, reputation-bearing, and structurally malleable. The pessimistic reading of the dilemma -- "cooperation is impossible" -- is theoretically valid only under conditions that rarely obtain in practice. The productive question is always: which structural conditions can be changed to enable cooperation? + +2. **Cooperating in a genuinely one-shot game.** The reverse error is equally dangerous. When the interaction truly will not repeat -- a one-time negotiation with a party you will never encounter again, a terminal business transaction -- cooperation is not sustained by any structural mechanism. Naively cooperating in a one-shot game against a rational adversary is not noble; it is strategically incoherent. Recognize the game type before selecting the strategy. + +3. **Blaming competitors for "irrational" price wars.** Price wars are typically the Nash equilibrium of the game's payoff structure. Calling competitors irrational for doing what the structure incentivizes is a failure of analysis, not a competitor failure. The productive response is to change the game structure, not to lament the opponent's choices. + +4. **Ignoring the number of players.** The gap between the competitive equilibrium and the cooperative optimum widens with each additional player. Entrepreneurs who enter crowded markets without a plan to reduce the effective number of competitors (through niching, differentiation, or consolidation) are accepting the worst version of the commons outcome. Player count is a strategic variable, not a given. + +5. **Applying the cooperation framework to genuinely zero-sum situations.** The Prisoner's Dilemma produces suboptimal outcomes because the game has a cooperative surplus -- a better outcome available if players coordinate. Some competitive situations are genuinely zero-sum: one player's gain is exactly another's loss. In zero-sum games, cooperation mechanisms do not apply. Attempting to cooperate in a zero-sum game simply transfers value to the less cooperative party. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Identifying the game structure | Before entering a market, determine whether the competitive dynamic is a Prisoner's Dilemma, a coordination game, or something else. Markets where the dilemma structure dominates (commodity products, low switching costs, many competitors) will compress margins regardless of execution quality. Choose accordingly. | +| Early Traction | Monitoring defection signals | Track competitor pricing, feature releases, and marketing spend for signs of escalation. Early detection of a price war or feature war creates time to respond structurally rather than reactively. | +| Growth | Building cooperation infrastructure | Establish the conditions for sustainable competition: visible commitments to a distinct positioning, long-term contracts that reduce incentives to defect, reputation investments that raise the cost of aggressive moves. The shadow of the future is longest at growth stage -- leverage it. | +| Scale | Designing market rules | At scale, the company can shape the game itself through platform policies, industry standards, ecosystem design, and strategic acquisitions. The goal shifts from surviving the dilemma to redesigning the game so the dilemma does not arise. | + +--- + +## Output Template + +```markdown +# Competitive Game Analysis: Cooperation vs. Defection + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Game Structure Identification + +- **Game type:** [Prisoner's Dilemma / Tragedy of the Commons / Coordination Game / Other] +- **Number of significant players:** [Count] +- **Repeated or one-shot:** [Assessment] +- **Shadow of the future:** [Long / Medium / Short -- explain] + +## Payoff Matrix + +| | Competitor Cooperates | Competitor Defects | +|--|----------------------|-------------------| +| **We Cooperate** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | +| **We Defect** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | + +## Equilibrium vs. Optimum + +- **Nash Equilibrium (predicted outcome):** [Description and payoffs] +- **Cooperative Optimum (ideal outcome):** [Description and payoffs] +- **Cost of non-cooperation:** [Gap between the two] + +## Escape Mechanism Assessment + +| Mechanism | Feasible? | Implementation | Expected Impact | +|-----------|-----------|---------------|----------------| +| Repetition / Long-term interaction | [Yes/No] | [How] | [Impact] | +| Reputation / Transparency | [Yes/No] | [How] | [Impact] | +| Enforceable contracts | [Yes/No] | [How] | [Impact] | +| Reduce player count | [Yes/No] | [How] | [Impact] | +| Restructure payoffs | [Yes/No] | [How] | [Impact] | + +## Recommended Strategy + +1. [Primary action] +2. [Fallback if cooperation fails] +3. [Long-term structural play] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](game-theory-fundamentals.md)** -- The prerequisite framework: players, strategies, payoffs, and Nash equilibrium provide the analytical foundation that this skill applies to cooperation problems. +- **[Information Asymmetry](information-asymmetry.md)** -- When players hold different information, the cooperation problem becomes more complex: adverse selection and moral hazard create additional barriers to trust. +- **[Evolutionary Strategy](evolutionary-strategy.md)** -- Extends the one-shot dilemma into population dynamics, revealing how cooperative and defecting strategies compete and stabilise across repeated market interactions. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation addresses the relationship and communication dimensions of cooperation; game theory provides the structural and incentive analysis. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust is the behavioural mechanism through which the "shadow of the future" operates; the trust equation quantifies the components that make cooperation sustainable. +- **[Cooperative Negotiation](../negotiation/cooperative-negotiation.md)** -- Translates the game-theoretic cooperation framework into practical conversational techniques for building deals where both parties gain. diff --git a/plugins/foreman/content/skills/leadership/ai-era-leadership.md b/plugins/foreman/content/skills/leadership/ai-era-leadership.md new file mode 100644 index 0000000..75c26c3 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/ai-era-leadership.md @@ -0,0 +1,176 @@ +--- +name: "ai-era-leadership" +description: "Prepares leaders for daily effectiveness in an AI-augmented workplace by focusing on the human capabilities that machines cannot replicate. Covers five irreplaceable leadership skills (interpersonal intelligence, analog relationship-building, creative unpredictability, domain credibility, and preskilling), practical routines for leading hybrid human-AI teams, and strategies for staying relevant as automation reshapes every function. Use when planning workforce development around AI adoption, when leaders feel threatened by automation, when building AI-human collaboration norms, or when advising on career resilience in technology-disrupted industries." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - artificial-intelligence + - future-of-work + - human-skills + - adaptability + - workforce-development + - preskilling + - career-resilience +related_skills: + - employee-engagement-retention + - leadership-style-adaptation + - leader-self-reflection + - strategic-questioning + - emotional-intelligence + - growth-mindset +author: "Fatih Guner" +--- + +# AI-Era Leadership + +Five years from now, the leader who cannot distinguish between a decision that requires human judgment and one that can be delegated to a model will be indistinguishable from the leader who, in 2005, refused to use email. Not gone -- but operating at a permanent disadvantage, consuming organisational resources to produce what a well-prompted system generates in seconds. + +The paradox of AI-era leadership is that it makes soft skills harder -- and more valuable. As machines absorb the lower and middle tiers of analytical work, the leader's hard skills are progressively eclipsed by smarter systems. What remains irreplaceable is precisely what technology struggles most to simulate: genuine empathy, creative unpredictability, the trust that comes from shared meals and hallway conversations, and the capacity to inspire humans to do what no algorithm would predict. Leadership in the AI age is not radically different from leadership before it. But it demands two recalibrations: an honest reckoning with which of your skills are already obsolete, and an aggressive investment in the ones that cannot be automated. + +--- + +## The Practice + +### Five Capabilities AI Cannot Copy + +**1. Interpersonal Intelligence** +Machines can generate text that reads as empathetic -- "I am sorry my answer upset you" -- but those responses are statistical predictions, not felt experiences. Human beings are wired to respond to genuine emotion. Understanding what others think and feel, and demonstrating that understanding through behaviour, remains a capability that no model replicates at depth. The daily practice: in every significant interaction, pause before responding to identify what the other person is feeling, not just what they are saying. + +**2. Analog Relationship Building** +AI connects information it already possesses. It cannot produce knowledge -- the novel insight that emerges from a shared coffee, an accidental hallway encounter, or a conference dinner where two people from different industries discover an unexpected intersection. The daily practice: protect at least two hours per week for unstructured, in-person interaction with colleagues, clients, or peers outside your immediate domain. This is not networking. It is the deliberate cultivation of serendipity. + +**3. Creative Unpredictability** +AI is a prediction engine. It generates the next most probable token, the most likely recommendation, the statistically expected output. A leader who sounds like an AI output -- polished, predictable, algorithmically optimal -- adds nothing that the system could not provide. The daily practice: cultivate your distinctive perspective. Draw unexpected connections between your unique interests and your professional domain. When everyone else is overly relying on AI, sounding like no one except yourself becomes a competitive advantage. + +**4. Domain Credibility** +AI tools summon facts almost instantly -- and sometimes those facts are fabricated. Since accuracy cannot be taken on faith, the leader who has spent years building genuine expertise becomes the essential verification layer. The daily practice: continue investing in deep domain knowledge even when AI offers shortcuts. Your reputation as someone who truly knows the subject makes you the person sought out to vet what the machine produces. + +**5. Preskilling** +Upskilling addresses today's gaps. Reskilling addresses tomorrow's. Preskilling -- the ability to future-proof talent and reinvent careers before the demand for new skills even materialises -- is the leadership capability that separates organisations that ride technological waves from those that drown in them. + +Five preskilling principles: +- Focus on potential, not solely on past performance +- Help employees map their interests and talents to emerging futures +- Expand skill sets rather than merely optimising existing ones +- Develop middle managers' interpersonal capabilities as a strategic priority +- Invest in leaders who inspire collaboration rather than those who merely manage output + +### Leading Human-AI Teams: Daily Norms + +The organisational challenge is not adopting AI tools; it is redesigning the daily rhythms of work so that humans and systems complement rather than compete with each other. + +**Allocation discipline.** For every task, ask: does this require judgment, creativity, or empathy? If yes, it stays human. Does it require pattern recognition at scale, data synthesis, or repetitive generation? If yes, it is a candidate for AI. The grey zone in between is where leadership judgment earns its keep. + +**Quality verification rituals.** Establish a norm that AI outputs are drafts, never final products. The human role shifts from creator to editor-in-chief -- someone who applies domain expertise, ethical judgment, and contextual awareness to machine-generated work. + +**Transparency about AI use.** Teams that hide AI use from one another develop trust problems. Teams that are transparent about it develop shared standards for when and how to deploy it. The leader sets this norm by being open about their own AI use and its limitations. + +--- + +## Prompts + +**Prompt 1 -- Personal Obsolescence Audit:** +> Evaluate my current skill set against the trajectory of AI capabilities in my industry. My role is [role] in [industry]. My primary skills are [list skills]. For each skill, assess: (a) the likelihood that AI will perform this skill at or above my level within 3 years, (b) the residual human value even if AI can perform the task, and (c) specific actions I should take now -- either to deepen the skill beyond AI's reach or to redirect my development elsewhere. + +**Prompt 2 -- Human-AI Team Design:** +> My team of [number] people in [function] currently performs these core tasks: [list tasks]. For each task, recommend whether it should remain fully human, become AI-assisted with human oversight, or be fully automated. Then design the new workflow, including: who does what, how quality is verified, and what new skills team members need to develop. Address the change management challenge -- how do I introduce this without triggering fear of replacement? + +**Prompt 3 -- Preskilling Programme:** +> Design a 12-month preskilling programme for my organisation of [size] people in [industry]. We anticipate the following changes in our industry over the next 3-5 years: [describe trends]. The programme should: identify which current roles are most vulnerable, map transferable skills to emerging roles, create development pathways, and specify how we will measure progress. Include specific attention to middle management soft-skill development. + +**Prompt 4 -- AI-Era Leadership Self-Assessment:** +> Assess my readiness for AI-era leadership across the five irreplaceable capabilities (interpersonal intelligence, analog relationship-building, creative unpredictability, domain credibility, preskilling). For each, I will describe my current practice: [describe]. Score each on a 1-5 scale, identify the two capabilities where I am most vulnerable, and design a 90-day development plan with specific weekly actions. + +--- + +## Use Cases + +**Validation-Stage Startup Deciding What to Build vs. Buy from AI** +A two-person startup in legal technology must decide which parts of their product require proprietary human expertise and which can be powered by third-party AI models. The obsolescence audit reveals that document summarisation -- their original differentiator -- is now a commodity capability of large language models. The human value lies in the nuanced judgment calls that follow the summary: which clauses carry hidden risk, which provisions are unusual for this deal type, which omissions should concern the client. The founders pivot their product positioning from "AI-powered document review" to "expert judgment layer on AI-generated analysis" -- a position that leverages domain credibility rather than competing with general-purpose AI. + +**Growth-Stage Company Restructuring Teams Around AI Adoption** +A 150-person marketing agency discovers that AI tools can produce first drafts of campaign copy, social media content, and basic design layouts in minutes. The initial fear: half the team becomes redundant. The human-AI team design reveals a different reality. The AI handles volume; humans handle taste, cultural nuance, client relationships, and creative direction. The restructuring elevates senior creatives into editorial roles, redeploys junior staff into client strategy and relationship management, and creates a new "AI operations" function that optimises prompts and workflows. Headcount does not decrease; the output-per-person triples. + +**Scale-Stage Manufacturing Company Preskilling Its Workforce** +A 2,000-person manufacturing company faces automation of 30% of its production roles within five years. Rather than waiting to lay off and rehire, the leadership launches a preskilling programme. Employees in at-risk roles are assessed for transferable capabilities. Those with high interpersonal skills move toward customer-facing roles. Those with technical aptitude enter a robotics maintenance training track. Those with analytical instincts transition to quality assurance roles that require the judgment AI lacks. The programme costs less than the projected expense of mass layoffs and rehiring. + +--- + +## Anti-Patterns + +1. **The Luddite Defence.** Ignoring AI because "my industry is different" or "my skills cannot be automated." Every industry said this. Most were wrong about at least some of their capabilities. The correct posture is honest assessment, not categorical denial. + +2. **The Full Delegation.** Treating AI outputs as final products rather than drafts requiring human judgment. The leader who stops verifying machine-generated analysis is not leveraging AI; they are abdicating the judgment that justifies their role. + +3. **The Fear-Based Adoption.** Introducing AI tools with the message "adapt or be replaced." This produces anxiety-driven compliance rather than genuine capability building, and the best people -- who have options -- leave for organisations that invest in their development rather than threatening their livelihood. + +4. **The Skills Freeze.** Stopping personal skill development because "AI can do it now." Domain expertise becomes more valuable, not less, when AI produces plausible but occasionally wrong outputs. The expert who can spot the fabrication is worth more in an AI-saturated environment than in one where human accuracy was the only option. + +5. **The Analog Purist.** Refusing to use AI tools at all, on principle. This is not authenticity; it is organisational negligence. The leader need not become a prompt engineer, but they must understand the capabilities and limitations well enough to make informed allocation decisions. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Build vs. buy decisions | At the earliest stage, AI determines what is worth building at all. If a general-purpose model performs your core function adequately, your product needs a different differentiator. The validation question shifts from "Can we build this?" to "Can we build this better than a model that costs pennies per query?" | +| Early Traction | Team composition | The first hires in an AI-aware startup look different from traditional hiring. The premium shifts toward people with judgment, taste, and domain credibility -- capabilities that complement AI rather than compete with it. | +| Growth | Workflow redesign | AI integration moves from individual tool use to systemic workflow redesign. The leadership challenge: redesigning processes without destroying the institutional knowledge embedded in the old ones. | +| Scale | Preskilling at volume | At scale, the AI transition is fundamentally a people problem. Thousands of employees need new capabilities, and the organisation cannot afford to replace them all. Preskilling becomes a strategic imperative with board-level visibility. | + +--- + +## Output Template + +```markdown +# AI-Era Leadership Assessment + +**Leader/Organisation:** [Name] +**Industry:** [Industry] +**Date:** [Date] + +## Capability Obsolescence Map + +| Current Skill/Task | AI Replacement Timeline | Residual Human Value | Action Required | +|--------------------|------------------------|---------------------|-----------------| +| [Skill] | [1-3 / 3-5 / 5+ years] | [High/Medium/Low] | [Deepen / Redirect / Automate] | + +## Irreplaceable Capability Scorecard + +| Capability | Current Level (1-5) | Gap | Development Action | +|-----------|---------------------|-----|-------------------| +| Interpersonal Intelligence | [Score] | [Gap] | [Action] | +| Analog Relationship Building | [Score] | [Gap] | [Action] | +| Creative Unpredictability | [Score] | [Gap] | [Action] | +| Domain Credibility | [Score] | [Gap] | [Action] | +| Preskilling | [Score] | [Gap] | [Action] | + +## Human-AI Workflow Design + +| Process | Current (Human) | Future (Human + AI) | Human Role Shift | +|---------|----------------|--------------------|--------------------| +| [Process] | [Current state] | [Future state] | [New human responsibility] | + +## 90-Day Action Plan +- **Month 1:** [Personal skill investments + team audit] +- **Month 2:** [Workflow pilots + norms establishment] +- **Month 3:** [Scale what works + measure impact] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- The theoretical foundation for interpersonal intelligence, which becomes the most valuable leadership differentiator as AI absorbs analytical tasks. +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Dweck's framework underpins the preskilling mentality: the belief that capabilities can be developed rather than being fixed traits. +- **[Employee Engagement and Retention](employee-engagement-retention.md)** -- AI transitions that ignore human anxiety produce attrition; the engagement practices in this companion skill are essential during technology adoption. +- **[AI Augmentation Not Automation](../ai-leadership/ai-augmentation-not-automation.md)** -- Provides the detailed framework for deciding which tasks to augment versus automate, operationalising the allocation discipline described here. +- **[Learning Agility](learning-agility.md)** -- The continuous learning capability that makes preskilling sustainable as AI reshapes role requirements every cycle. +- **[Leading Through Change](leading-through-change.md)** -- AI adoption is organisational change; the emotional and communicative practices for transitions apply directly to workforce AI integration. diff --git a/plugins/foreman/content/skills/leadership/business-writing-for-leaders.md b/plugins/foreman/content/skills/leadership/business-writing-for-leaders.md new file mode 100644 index 0000000..9c62675 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/business-writing-for-leaders.md @@ -0,0 +1,168 @@ +--- +name: "business-writing-for-leaders" +description: "Sharpens leadership writing through four principles: write for the reader, lead with clarity, keep it simple, and sound human. Use when drafting company-wide announcements, writing investor updates, composing emails that require action, editing team communications for clarity, or noticing that written messages consistently generate confusion or non-response." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - communication + - clarity + - email + - announcements + - simplicity +related_skills: + - psychological-safety-practice + - persuasion-and-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +# Business Writing for Leaders + +DELETE KEY. The most powerful writing tool a leader possesses is subtraction. Every unnecessary word dilutes authority. Every jargon-laden sentence signals that the writer is performing competence rather than demonstrating it. Every buried lead -- the critical information hidden in paragraph three -- is a tax on the reader's time and goodwill. Yet leaders write more words each year, to more people, through more channels, with less editing and less consideration for the person on the receiving end. The average executive sends and receives over 120 emails per day. The ones that get read, understood, and acted upon share a common trait: their authors wrote for the reader, not for themselves. + +Researchers and practitioners writing across a decade of HBR publications converge on a conclusion that should embarrass anyone who has ever used the phrase "synergistic value proposition" in an email: good business writing is simple, clear, human, and structured around what the reader needs to know, not what the writer wants to say. + +--- + +## The Framework + +Leadership writing rests on four principles. They are deceptively simple. Executing all four simultaneously, under time pressure, with multiple audiences, is considerably harder than any writing guide admits. + +### Principle 1: Write for the Reader + +The discipline begins with a shift in orientation. Before writing a sentence, answer three questions: + +- **What does the reader need to know?** Not what you want to tell them. What they need. +- **What questions will they have?** Anticipate and address them in order of likely importance. +- **How much time will they give this?** Assume less than you hope. Probably less than you think. + +Respect for the reader's time is not a courtesy; it is a structural requirement. Put the most important information first. The reader who stops after the first paragraph should still have the essential message. The reader who continues should find supporting detail, not repetition. + +Picture your audience as intelligent novices: smart, capable of grasping complex ideas, but not fluent in your department's acronyms, your industry's jargon, or your project's internal shorthand. Define technical terms on first use. Avoid abbreviations unless they are universally understood. The test is whether someone outside your team would understand every sentence without a glossary. + +### Principle 2: Lead with Clarity + +Three structural practices separate clear writing from unclear writing: + +**Get to the point.** Lead with your core idea. Provide context to support it. Cut everything else. The common failure is inversion: context first, supporting detail second, the actual point last. By the time the reader reaches it, attention has dissipated. + +**Use topic sentences that forecast.** The first sentence of each paragraph should tell the reader what the paragraph is about -- not merely describe a detail. Compare: "I met with the client in Berlin" (descriptive, no signal) versus "My meeting with the Berlin client focused on plans for future growth" (forecasting, contextual). The second sentence earns the reader's continued attention by promising relevance. + +**Use active voice.** "Juan improved the project's results" is clear. "The project's results were improved" is evasive -- it hides agency, removes accountability, and requires more words to say less. Passive voice has legitimate uses (when the actor is unknown or deliberately unimportant), but it should be a conscious choice, not a default. + +### Principle 3: Keep It Simple + +Overblown language does not signal intelligence. It signals insecurity. The writer who uses "leverage" when they mean "use," "ideate" when they mean "think," or "robust solution" when they mean "good answer" is not communicating -- they are decorating. + +Practical simplification: + +- **Use short, familiar words.** "Begin" rather than "commence." "End" rather than "terminate." "Use" rather than "utilise." +- **Use short sentences.** If a sentence contains more than one idea, it should probably be two sentences. +- **Use short paragraphs.** A paragraph crammed with four ideas forces the reader to parse structure and content simultaneously. One idea per paragraph. Two at most. +- **Use formatting as a tool.** Headings, bullet points, bold text, and numbered lists allow readers to scan for relevance. Most business writing will be read on a phone, possibly while the reader is walking, eating, or sitting in another meeting. Write for that reality, not for the undivided attention you wish you had. + +### Principle 4: Sound Human + +The gap between how leaders write and how leaders speak is, in most organisations, unnecessarily wide. Written communication that sounds like it was produced by a committee -- or by a language model prompted to "sound professional" -- creates distance where connection is needed. + +Three practices: + +- **Use first person.** "I recommend" and "We accomplished" are personal and direct. "The company achieved" and "It has been determined" are bureaucratic and evasive. Readers trust people. They distrust institutions that refuse to identify a human behind the words. +- **Start sentences with verbs and conjunctions.** "Get the report to me by Friday." "But that approach has a flaw." "And here is why it matters." These constructions mirror natural speech patterns and create momentum. They are grammatically correct despite what certain style guides claim. +- **Read aloud.** The most reliable test of whether writing sounds human: say it out loud. If a sentence sounds awkward spoken, it will sound awkward read. If a phrase would never leave your mouth in conversation, it should not appear in your writing. + +--- + +## Prompts + +**Prompt 1 -- Writing Audit:** +> Here is a piece of business writing I recently sent: [paste the full text]. Audit it against four principles: reader orientation, clarity of structure, simplicity of language, and human voice. For each principle, score it on a 5-point scale and provide specific examples of where it succeeds and fails. Then rewrite the weakest sections. + +**Prompt 2 -- Email Rewrite:** +> I need to send this email: [describe the situation, the audience, and the key message]. Draft it in under 150 words, leading with the core message, using active voice, avoiding jargon, and sounding like a human wrote it. Then provide a version for a different audience: [describe the second audience]. + +**Prompt 3 -- Announcement Draft:** +> I need to announce [describe the news -- positive or negative] to [describe the audience]. The key facts are: [list]. The likely questions are: [list]. Draft an announcement that leads with the most important information, anticipates reader questions, uses simple language, and maintains an honest, human tone. Keep it under 250 words. + +**Prompt 4 -- Jargon Elimination:** +> Here is a document filled with jargon and corporate language: [paste text]. Rewrite every sentence using the simplest possible language without losing meaning. Flag any instances where jargon was actually doing useful work (i.e., a technical term that has no simpler equivalent) and keep those. + +--- + +## Use Cases + +**Validation-Stage Founder Writing an Investor Update** +A founder sends monthly investor updates that consistently go unread. An audit reveals the problem: updates open with three paragraphs of context before reaching the key metrics. Investors, who receive dozens of portfolio updates per month, stop reading after paragraph one. The rewrite leads with a three-line summary (revenue, burn, key milestone), follows with a five-bullet section on progress and challenges, and closes with a specific ask. Open rates double. Response rates triple. The content did not change -- the structure did. + +**Growth-Stage VP Sending a Restructuring Email** +A VP of Operations needs to announce a team restructuring that will affect 40 people. The first draft, reviewed against the four principles, is 800 words, opens with corporate preamble ("As we continue to evolve our organisational capabilities..."), buries the actual changes in paragraph four, and uses passive voice throughout ("roles will be affected" -- by whom?). The rewrite opens with the change ("Effective March 1, Teams A and B will merge under [Name]"), explains the reasoning in two sentences, details what this means for each person's role in a bulleted list, and closes with a specific invitation: "I will hold office hours on Thursday and Friday to answer your questions directly." Active voice. Human tone. Half the length. + +--- + +## Anti-Patterns + +1. **Writing to Impress, Not to Communicate.** The leader who uses complex vocabulary and elaborate sentence structures to signal intelligence. The reader does not conclude "this person is brilliant." The reader concludes "this person made me work harder than necessary to understand a simple point." Sophistication in writing is the ability to make complex ideas simple, not simple ideas complex. + +2. **The Reply-All Essay.** Responding to a two-line question with a 500-word treatise. Match the length and formality of your response to the communication that prompted it. Escalating register signals that you are performing, not communicating. + +3. **Editing by Addition.** Reviewing a draft and making it longer. In nearly every case, the most productive edit is deletion. Remove the sentence that repeats the previous one. Remove the paragraph that qualifies a point the reader did not need qualified. Remove the adjective that adds nothing. + +4. **Template Dependence.** Using the same format for every communication regardless of audience, context, or message. A team update, an investor email, and a disciplinary notice require different structures, different tones, and different lengths. Templates are a starting point, not a destination. + +5. **Delegating Voice.** Having someone else write communications that carry the leader's name without reviewing them for tone and voice. Readers develop a model of who the leader is through their writing. Inconsistency between spoken and written voice -- or between one email and the next -- erodes trust. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch writing | Every written word is selling -- the vision, the opportunity, the founder's credibility. Clarity and human voice are the primary differentiators because the founder has no brand to lend authority. | +| Validation | Customer and investor communication | Writing must translate technical complexity into accessible language for non-expert audiences. The intelligent-novice rule applies with particular force. | +| Early Traction | Internal communication at scale | The founder transitions from writing to five people to writing to fifty. Structure and formatting become essential because the audience can no longer be assumed to have full context. | +| Growth | Organisational voice | Writing sets culture. How the leadership team communicates -- the clarity, the honesty, the simplicity -- becomes the template that the entire organisation replicates. | +| Scale | Delegation and consistency | The leader writes less personally and reviews more writing by others. The skill shifts from writing well to editing well and coaching others to write well. | + +--- + +## Output Template + +```markdown +# Communication Draft: [Subject] + +## Pre-Writing Check +- Reader: [who will read this] +- Reader's primary question: [what they need to know] +- Reader's available attention: [how much time they will give this] +- Required action: [what the reader should do after reading] + +## Draft +[The communication, structured with the core message first, supporting detail second, and a clear call to action] + +## Self-Audit +- [ ] Core message in the first two sentences +- [ ] Active voice throughout (passive voice used only deliberately) +- [ ] No unexplained jargon or acronyms +- [ ] Every paragraph begins with a topic sentence +- [ ] Read aloud -- sounds human +- [ ] Length appropriate to the audience and channel +``` + +--- + +## Related Skills + +- **[Writing with Purpose](../writing/writing-with-purpose.md)** -- Defines the foundational technique for determining what to say and why before drafting, which directly supports the leader's principle of writing for the reader. +- **[Clarity and Concision](../writing/clarity-and-concision.md)** -- Provides the sentence-level editing techniques that operationalise Principle 3's mandate to keep it simple and cut unnecessary words. +- **[Tone and Engagement](../writing/tone-and-engagement.md)** -- Addresses the tonal calibration that makes Principle 4 actionable: sounding human without losing authority across different audiences. +- **[Persuasion and Influence](persuasion-and-influence.md)** -- Writing is a persuasion medium; the principles of reading the room and establishing authority organically apply in written form as much as in spoken interaction. +- **[Psychological Safety in Practice](psychological-safety-practice.md)** -- How leaders write about mistakes, setbacks, and difficult news directly affects whether team members feel safe to surface problems. +- **[Storytelling for Leaders](storytelling-for-leaders.md)** -- Narrative techniques transform announcements and updates from information dumps into compelling communications that land with readers. diff --git a/plugins/foreman/content/skills/leadership/career-strategy-for-leaders.md b/plugins/foreman/content/skills/leadership/career-strategy-for-leaders.md new file mode 100644 index 0000000..6f66087 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/career-strategy-for-leaders.md @@ -0,0 +1,187 @@ +--- +name: "career-strategy-for-leaders" +description: "Guides leaders through deliberate career design -- calculating timelines, auditing career fuel, breaking career-limiting habits, avoiding success traps, and aligning trade-offs with evolving values. Use when a leader feels stuck, faces a career crossroads, suspects their success has become a cage, needs to break a recurring bad habit, or wants to shift from reactive career drift to intentional career architecture." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - career-planning + - success-traps + - habits + - self-management + - growth-mindset + - career-fuel + - trade-offs +related_skills: + - growth-mindset + - covey-seven-habits + - eisenhower-matrix + - emotional-intelligence +author: "Fatih Guner" +--- + +# Career Strategy for Leaders + +CROSSROADS. Most leaders arrive at one sometime between their tenth and twentieth year of management. The recognition is uncomfortable: their career happened to them. Promotions arrived because they were competent, not because they were strategic. Opportunities materialized through proximity, not design. Titles accumulated like sediment -- layers of accidental geology rather than intentional architecture. The leader who never planned a career trajectory is not unusual; they are the statistical norm. Brian Fetherstonhaugh's research for HBR suggests that the majority of professionals dramatically underestimate how long their careers will last, which means they under-invest in the skills, relationships, and experiences that sustain performance across decades. A career without strategy is not a career. It is an extended reaction to whatever happens next. + +The antidote is not a five-year plan pinned to the wall. It is a set of recurring practices -- honest self-assessment, deliberate habit management, resistance to the seductions of past success -- that transform career drift into career design. + +--- + +## The Framework + +Career strategy for leaders operates across four interlocking dimensions. None functions in isolation; neglecting any one dimension eventually undermines the others. + +### 1. Timeline Awareness + +Most leaders assume their career is roughly half over when in reality it has decades remaining. The first discipline of career strategy is calculating -- with uncomfortable specificity -- how many working years remain. Factor in retirement age norms, industry velocity, health trajectories, and financial requirements. Leaders who confront their actual timeline make qualitatively different decisions about what to invest in next. A leader with thirty years remaining cannot afford to coast on a single expertise domain. A leader with five years remaining cannot afford to defer the work they actually care about. + +### 2. Career Fuel Audit + +Three resources sustain a career across its full arc: + +| Fuel Type | Definition | Depletion Signal | +|-----------|-----------|------------------| +| **Transportable skills** | Capabilities that transfer across roles, industries, and organisations | You can only describe your value in terms of your current job title | +| **Meaningful experiences** | Assignments that stretched capacity, expanded perspective, or built judgment | Your last three years feel interchangeable | +| **Enduring relationships** | Connections that provide insight, access, candour, and support | Your professional network is a single company's org chart | + +The audit is blunt: are these fuel levels growing, stagnating, or declining? Growth does not require changing jobs. A special assignment, a cross-functional rotation, an expanded remit, or structured learning within the current organisation can replenish all three tanks. + +### 3. Success Trap Identification + +Success creates its own gravity. Rosabeth Moss Kanter's research identifies five barriers that high performers erect around themselves: + +- **Impatience.** Accomplished problem-solvers develop an addiction to quick resolution that fails them on complex, systemic challenges. +- **Narrow expertise.** Deep domain knowledge becomes a prison when every problem is viewed through a single disciplinary lens. +- **Intellectual arrogance.** The inability to say "I don't know" calcifies as seniority rises and the people around you stop challenging your conclusions. +- **Echo chambers.** Success attracts agreement. Leaders surrounded by people who never dissent begin to mistake consensus for correctness. +- **Title attachment.** Defining identity through a job title narrows collaboration and alienates the cross-functional contributors whose help complex problems demand. + +Each trap is a direct consequence of competence. That is what makes them dangerous -- they masquerade as strengths. + +### 4. Habit Architecture + +Career-limiting habits persist because the environment rewards them -- or at least fails to punish them. Crucial Learning research identifies five levers for dismantling bad habits and installing productive ones: + +1. **Manage distance.** Physically separate from temptations and bring helpful stimuli closer. Procrastinators should work in isolation rooms. Leaders who want to read industry analysis should replace social media bookmarks with those sources. +2. **Reframe language.** Replace "I won't" with "I can't" (increases psychological resistance) and "I have to" with "Why do I want to?" (reconnects with intrinsic motivation). +3. **Change your social environment.** Spend more time with people who model the behaviours you want to cultivate. Social circles shape attitudes more than willpower does. +4. **Schedule defaults.** Put the desired behaviour on the calendar. Humans honour pre-committed time far more reliably than spontaneous intention. +5. **Train incrementally.** Identify one micro-skill per week and one situation in which to practise it. Competence builds motivation, not the reverse. + +### 5. The Four-Question Self-Grade + +Periodically -- annually at minimum -- grade the current situation against four criteria: Am I learning? Am I having impact? Am I having fun? Am I being rewarded? If three of four answers are negative, the problem is structural, not attitudinal. If one answer is negative, targeted action within the current role may suffice. + +--- + +## Prompts + +**Prompt 1 -- Career Timeline Calculation:** +> Calculate my realistic career timeline. I am [age], in [industry], with [describe financial situation]. Factor in industry retirement norms, my health considerations, potential part-time work, and financial requirements. Then identify the three most important investments I should make in the next five years given this timeline. Be specific -- not "learn new skills" but what skills and why. + +**Prompt 2 -- Career Fuel Audit:** +> Audit my career fuel. Here are my transportable skills: [list]. My meaningful experiences in the past five years: [list]. My enduring professional relationships: [describe network]. For each fuel type, assess whether I am growing, stagnating, or declining. Then recommend three specific actions to replenish the weakest fuel tank without changing employers. + +**Prompt 3 -- Success Trap Diagnostic:** +> Evaluate me against the five success traps: impatience, narrow expertise, intellectual arrogance, echo chambers, and title attachment. Here is my current role: [describe]. Here is how I typically approach complex problems: [describe]. Here is how I respond to disagreement: [describe]. Identify which traps I am most vulnerable to, provide specific evidence from my descriptions, and recommend one countermeasure for each. + +**Prompt 4 -- Career-Limiting Habit Intervention:** +> I have a career-limiting habit: [describe the habit in detail]. Design an intervention using all five levers: distance management, language reframing, social environment change, scheduled defaults, and incremental training. Make each lever specific to my habit and my work context: [describe context]. + +--- + +## Use Cases + +**Growth-Stage Founder Approaching Year Eight** +A SaaS founder has built a company from zero to 120 employees. Every skill they developed -- fundraising, early-stage hiring, product-market-fit iteration -- is an early-stage skill. The company now needs a scale-stage operator, and the founder recognises they have been coasting on the reputation of early success. A career fuel audit reveals stagnating transportable skills (nothing new learned in three years) and a relationship network entirely composed of Series A investors and fellow early-stage founders. The intervention: join a CEO peer group with leaders running 500+ person organisations, take on a board seat at a larger company for exposure, and hire a COO to create space for personal skill development. + +**Senior Vice President Hitting the Success Trap** +A VP of Engineering at a mid-sized enterprise has been promoted four times in twelve years. Every promotion reinforced the same approach: deep technical expertise, fast problem resolution, authoritative decision-making. Now leading a cross-functional transformation programme, they find that impatience alienates programme partners, narrow technical framing misses organisational dynamics, and the inability to say "I don't know" prevents learning from non-engineering disciplines. The success trap diagnostic reveals three of five traps are active. The countermeasures: assign a cross-functional deputy to co-lead (breaking the expertise prison), institute a "what am I wrong about?" weekly reflection (disrupting intellectual arrogance), and schedule monthly lunches with leaders from marketing, finance, and operations (expanding the network beyond the echo chamber). + +**Mid-Career Manager Facing a Trade-Off Reassessment** +A director of product with two young children grades their current role: learning (yes, marginally), impact (yes), fun (no), rewarded (yes, financially). The single "no" has been persistent for two years. A trade-off audit reveals that the role demands 60-hour weeks and constant travel -- trade-offs that were acceptable before children and are no longer aligned with evolving values. Rather than quitting, the intervention identifies a lateral move within the same company to a product strategy role with equivalent compensation, higher learning, and 30% less travel. + +--- + +## Anti-Patterns + +1. **The Annual Review as Career Strategy.** Treating a manager's performance review as a career planning exercise confuses short-term performance feedback with long-term trajectory design. Performance reviews optimise for the current role. Career strategy optimises for the career. + +2. **Conflating Industry with Growth.** Theodore Levitt's warning remains precise: there is no such thing as a growth industry, only companies organised to capitalise on growth opportunities. Leaders who hitch their career to an industry label rather than to transferable capability find themselves stranded when that industry's automatic escalator stops. + +3. **Over-Indexing on Willpower.** Attempting to change a career-limiting habit through pure discipline, without restructuring the environment, social context, or schedule that sustains it. Willpower is a depletable resource. Environment design is structural. + +4. **The "I'll Figure It Out When I Get There" Fallacy.** Refusing to calculate a career timeline because the future is uncertain. Uncertainty is precisely the reason to plan -- not because the plan will be followed precisely, but because the planning process reveals gaps and assumptions that would otherwise remain invisible. + +5. **Success Nostalgia.** Continuing to apply the strategies that created past success to problems that require different capabilities. The skills that built a company from zero to ten employees are often the skills that prevent it from reaching a hundred. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Skill diversification | The founder's career and the company's trajectory are fused. Career strategy means deliberately building skills beyond the founding specialisation -- finance, hiring, management -- before the company outgrows the founder's current capability set. | +| Growth | Identity expansion | Success traps begin to crystallise. The leader must actively resist defining their career through the single lens of "the person who built this." Broadening identity to include advisor, board member, or industry contributor creates resilience against role-specific setbacks. | +| Scale | Legacy architecture | Career fuel audits become existential. At scale, the leader's meaningful experiences may be plateauing even as financial rewards peak. Mentoring successors, taking on cross-industry challenges, and investing in enduring relationships outside the current organisation become the primary career fuel sources. | + +At every stage, the four-question self-grade provides the diagnostic. The answers change; the discipline of asking does not. + +--- + +## Output Template + +```markdown +# Career Strategy Assessment: [Leader Name / Role] + +## Timeline +- Estimated remaining career years: [N] +- Key assumptions: [health, financial, industry factors] + +## Career Fuel Audit +| Fuel Type | Current Level | Trend | Evidence | Action | +|-----------|--------------|-------|----------|--------| +| Transportable Skills | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | +| Meaningful Experiences | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | +| Enduring Relationships | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | + +## Success Trap Exposure +| Trap | Risk Level | Evidence | Countermeasure | +|------|-----------|----------|----------------| +| Impatience | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Narrow Expertise | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Intellectual Arrogance | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Echo Chamber | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Title Attachment | [High/Medium/Low] | [specific behaviour] | [specific action] | + +## Four-Question Grade +- Learning: [Yes/No — detail] +- Impact: [Yes/No — detail] +- Fun: [Yes/No — detail] +- Rewarded: [Yes/No — detail] + +## Priority Career-Limiting Habit +- Habit: [description] +- Intervention plan: [five levers applied] + +## 90-Day Actions +1. [Highest priority action] +2. [Second priority action] +3. [Third priority action] +``` + +--- + +## Related Skills + +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Dweck's fixed-versus-growth framework provides the psychological foundation for why some leaders treat career setbacks as data and others treat them as verdicts. +- **[Covey's Seven Habits](../frameworks/covey-seven-habits.md)** -- "Begin with the end in mind" and "put first things first" are the philosophical precursors to career timeline calculation and trade-off alignment. +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The seven reflection domains provide the structured introspection that the four-question self-grade and success trap identification require. +- **[Senior Leadership Transition](senior-leadership-transition.md)** -- Career strategy inflection points often coincide with leadership transitions where identity, skills, and relationships must all be recalibrated. +- **[Wanting What Matters](../thinking/wanting-what-matters.md)** -- Addresses the meta-question underlying career trade-offs: whether the goals being pursued actually align with what will produce lasting satisfaction. diff --git a/plugins/foreman/content/skills/leadership/decision-making-under-pressure.md b/plugins/foreman/content/skills/leadership/decision-making-under-pressure.md new file mode 100644 index 0000000..19730d1 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/decision-making-under-pressure.md @@ -0,0 +1,196 @@ +--- +name: "decision-making-under-pressure" +description: "Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that deliberation has become procrastination, noticing a pattern of deferred decisions, needing to explain decision-making rationale to a team, or recognising that overthinking is degrading output quality." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - decision-making + - critical-thinking + - pressure + - intuition + - ethics + - problem-framing + - overthinking +related_skills: + - thinking-fast-and-slow + - vuca-framework + - eisenhower-matrix + - psychological-safety +author: "Fatih Guner" +--- + +# Decision-Making Under Pressure + +TIMER. Every undecided decision carries a holding cost -- and most leaders dramatically underestimate it. Projects stall waiting for approval. Teams hedge because direction is unclear. Competitors move while deliberation continues. The holding cost is invisible because it appears on no balance sheet, but it compounds daily: in lost momentum, in eroded team confidence, in the narrowing of options that occurs while a leader searches for certainty that will never arrive. Clayton Christensen observed that the most dangerous phrase in a leader's vocabulary is "just this once" -- a phrase that makes ethical and strategic erosion feel costless. Thomas Davenport's research suggests that the question is rarely whether a leader has enough information to decide, but whether they have the courage to decide with the information they have. + +The cognitive science of decision-making -- Kahneman's System 1 and System 2, the taxonomy of biases -- is covered elsewhere in this system. What follows is the applied practice: the daily habits that separate leaders who decide well under pressure from those who decide late, or not at all. + +--- + +## The Framework + +Practical decision-making under pressure operates through six habits. They are not sequential; they are concurrent disciplines that reinforce each other over time. + +### Habit 1: Frame Before You Solve + +Julia Binder and Michael Watkins's research reveals a consistent failure pattern: leaders and teams devote too little effort to examining and defining problems before attempting to solve them. Jumping to solutions feels productive. It rarely is. Problem-framing is the practice of viewing a situation through multiple lenses -- adjusting angle, aperture, and focus -- before committing to a solution path. + +Three reframing techniques for daily use: + +- **Stakeholder reframe.** How does this problem look from the customer's perspective? The investor's? The newest employee's? Each perspective reveals constraints and opportunities invisible from the leader's vantage point. +- **Temporal reframe.** What does this problem look like in six months? In three years? Decisions that feel urgent today often look different when projected forward. Equally, decisions that feel deferrable today may become irreversible if delayed. +- **Scale reframe.** If this problem were ten times larger, how would you approach it? If it were trivial, would you still be deliberating? Scale shifts expose whether the decision difficulty is inherent to the problem or manufactured by the decision-maker's anxiety. + +Peter Drucker's observation applies: the leader who takes pride in solving problems quickly may be solving the wrong problems. The leader who reframes first solves fewer problems -- but the right ones. + +### Habit 2: Apply the Importance-Frequency Matrix + +Thomas Davenport's framework for deciding when to stop deliberating uses two variables: + +| | Low Importance | High Importance | +|---|---|---| +| **High Frequency** | Create a rule or system; invest once, then automate | Develop a robust process; the recurrence justifies the effort | +| **Low Frequency** | Decide immediately; the cost of deliberation exceeds the value of optimisation | Gather perspectives, then decide within a defined time boundary | + +Most leaders over-deliberate low-importance decisions and under-invest in systems for high-frequency ones. The diagnostic question: "If I spent thirty more minutes on this decision, would the outcome materially improve?" If the answer is no, decide now. + +### Habit 3: Balance Gut and Data + +Jennifer Jordan, Michael Wade, and Elizabeth Teracino's research identifies the intuition-analysis tension as one of seven tensions every leader must navigate. Overvaluing intuition produces decisions based on outdated heuristics and unexamined biases. Overvaluing data produces analysis paralysis and the illusion that sufficient information will eliminate uncertainty. + +The practical balance: + +- **Use intuition for:** pattern recognition in familiar domains, rapid triage of low-stakes decisions, identifying which data to seek. +- **Use analysis for:** high-stakes decisions where biases are likely operating, situations outside your domain expertise, decisions that will be difficult to reverse. +- **Use both for:** any decision where your gut says one thing and the data says another. The disagreement itself is the most valuable signal -- it means either your experience is detecting something the data misses, or your biases are overriding evidence. Determining which requires deliberate examination, not default to either mode. + +### Habit 4: Widen Perspective Deliberately + +Helen Lee Bouygues's research on critical thinking identifies three practices that guard against poor decisions: + +1. **Question assumptions.** Especially when stakes are high. "Why is this the best way forward?" and "What does the evidence actually say about our market expectations?" force the reasoning process to surface premises that may be unexamined. +2. **Verify logical coherence.** Are the conclusions supported by the data, or are they supported by the narrative someone has constructed around the data? These are different things. +3. **Seek perspectives outside your circle.** The inner circle shares your assumptions. Perspectives from different departments, different experience levels, and different professional backgrounds reveal blind spots that homogeneous consultation cannot. + +Sabina Nawaz's six gut-check questions provide a structured version of this practice for new ideas: What stands out? What's missing? What would critics say? What would failure look like? What would customer-facing employees say? What shortcomings would please competitors? + +### Habit 5: Resist "Just This Once" + +Christensen's observation deserves its own habit because the mechanism is subtle and the consequences are severe. The marginal cost of doing something wrong "just this once" always appears low. The full cost -- which includes the precedent set, the standard lowered, the integrity compromised -- is invisible at the moment of decision. Leaders who maintain their principles 100% of the time find it structurally easier than those who maintain them 98% of the time, because the 2% creates a negotiation with themselves that the 100% does not. + +The practical application is precommitment: know where your lines are before you face pressure to cross them. Ethical boundaries decided in advance require no deliberation under pressure. Ethical boundaries decided in the moment are subject to every cognitive bias and rationalisation the human mind can produce. + +### Habit 6: Break Overthinking Cycles + +Alice Boyes's research identifies a pattern: intelligent leaders are particularly prone to overthinking because their cognitive capacity allows them to generate more scenarios, more objections, and more complications than the problem warrants. The signals of overthinking: obsessing over the same options, generating diminishing returns on additional analysis, inability to commit despite adequate information. + +Three circuit-breakers: + +- **Notice the loop.** The first step is recognising that you are cycling through the same arguments. Label it: "I am overthinking this." +- **Change cognitive mode.** Engage in an absorbing, unrelated activity -- a puzzle, a walk, a conversation about something else entirely. This is not procrastination; it is allowing the subconscious processing that focused analysis suppresses. +- **Set a decision deadline.** "I will decide by Thursday at noon" creates a forcing function. Share the deadline with someone else to make it binding. Open-ended deliberation is a failure mode, not a virtue. + +--- + +## Prompts + +**Prompt 1 -- Problem Reframing:** +> I am facing this decision: [describe the decision and context]. Before I solve it, help me reframe it. Apply three lenses: stakeholder reframe (how does this look from the perspectives of [list 3 stakeholders]), temporal reframe (what does this look like in 6 months vs. 3 years), and scale reframe (if this were 10x larger or trivially small). Then tell me: am I solving the right problem? + +**Prompt 2 -- Decision Speed Diagnostic:** +> Here are five decisions currently pending on my desk: [list each with a brief description]. For each, assess importance (high/low) and frequency (high/low) using the Davenport matrix. Then recommend: which should I decide immediately, which need a system, which deserve more deliberation, and which am I over-deliberating? + +**Prompt 3 -- Intuition vs. Analysis Arbitration:** +> My gut tells me [describe intuitive conclusion] about [decision]. The data suggests [describe analytical conclusion]. Help me determine whether my intuition is detecting a pattern the data misses or whether my biases are overriding evidence. Ask me the questions that would distinguish between these two explanations. + +**Prompt 4 -- Ethical Line Precommitment:** +> I am entering a high-pressure period: [describe context -- fundraising, acquisition, restructuring]. Before the pressure arrives, help me define my ethical precommitments. What are the "just this once" temptations most common in this type of situation? For each, help me articulate the line I will not cross and the reasoning behind it, so I don't have to reason under pressure. + +--- + +## Use Cases + +**Early-Traction Startup: Founder Paralysed by Pricing Decision** +A founder has spent three weeks analysing pricing models for a product launch. Every model has trade-offs. No model is clearly superior. The importance-frequency diagnostic reveals this is a high-importance but low-frequency decision -- it deserves deliberation but within a bounded timeframe. The temporal reframe reveals that the pricing decision is reversible within 90 days. The founder sets a 48-hour decision deadline, shares it with their co-founder for accountability, and selects the model that best aligns with their positioning thesis. Three months later, they adjust pricing based on real customer data -- data they would not have if they had spent another three weeks deliberating. + +**Growth-Stage Company: VP Avoiding a Restructuring Decision** +A VP knows that one of three engineering teams needs to be reorganised. The decision will disappoint people, so the VP gathers "just a little more data" -- for the fourth consecutive month. The holding cost diagnostic reveals: two projects are stalled because team boundaries are unclear, three engineers have started interviewing at other companies due to uncertainty, and cross-team collaboration has degraded. The VP applies the six gut-check questions to each restructuring option, sets a one-week decision deadline, and communicates the decision with transparent reasoning. Morale dips briefly; the stalled projects resume within two weeks. + +**Scale-Stage CEO: Resisting "Just This Once" in a Partnership Deal** +A CEO is negotiating a distribution partnership with a larger company. The partner's legal team inserts a clause that requires sharing customer data in ways that conflict with the company's privacy commitments. The partner's head of BD says, "We can work around this informally -- just sign the contract as-is and we'll handle the data question later." The CEO, having precommitted to data privacy as a non-negotiable line, declines without deliberation. The partner respects the boundary and revises the clause. Had the CEO not precommitted, the "just this once" logic -- "it's our biggest deal, we'll fix it later" -- would have been persuasive in the moment. + +--- + +## Anti-Patterns + +1. **Decisiveness Theatre.** Making rapid decisions ostentatiously to signal leadership confidence, without reframing or perspective-gathering. Speed without discernment is recklessness branded as decisiveness. + +2. **Data as Procrastination.** Requesting additional analysis not because it would change the decision but because it defers the discomfort of committing. The tell: the decision-maker cannot articulate what specific data point would change their mind. If no data point would change the outcome, the decision is ready to be made. + +3. **Consensus as Decision-Making.** Treating universal agreement as a prerequisite for action. Consensus-seeking is a legitimate collaboration tool. Consensus-requiring is a mechanism for distributing blame and avoiding accountability. Clarify before any meeting whether the process is consultative (I will hear all views and then decide) or democratic (the group will vote). + +4. **Post-Hoc Rationalisation Disguised as Intuition.** "My gut told me" is sometimes a legitimate report of pattern recognition and sometimes a retroactive justification for a decision made on emotion. The difference: genuine intuition can be examined and its reasoning reconstructed; post-hoc rationalisation collapses under questioning. + +5. **The Reversibility Blind Spot.** Treating all decisions as equally permanent. Many business decisions are highly reversible -- pricing, feature prioritisation, team assignments -- and deserve fast, low-deliberation treatment. Irreversible decisions -- equity grants, market exits, key hires -- deserve the full reframing and perspective-gathering protocol. Applying the irreversible protocol to reversible decisions is a common source of organisational paralysis. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Speed over precision | Nearly every decision is reversible because the company is small and fast-moving. The primary risk is not making a wrong decision but making no decision. The importance-frequency matrix should bias toward "decide immediately" for most choices. | +| Growth | Process installation | Decision volume exceeds one person's capacity. The leader's task shifts from making every decision to building decision-making systems (for high-frequency issues) and teaching the reframing and deliberation habits to the leadership team. | +| Scale | Decision delegation and ethics | At scale, the leader makes fewer decisions directly and more decisions about how decisions should be made. Ethical precommitment becomes organisational, not personal -- codified in policies, not just personal convictions. The "just this once" risk multiplies as more people face pressure to cut corners. | + +--- + +## Output Template + +```markdown +# Decision Analysis: [Decision Description] + +## Problem Frame +- Initial framing: [how the problem was first presented] +- Stakeholder reframe: [alternative perspective] +- Temporal reframe: [how it looks at different time horizons] +- Scale reframe: [what changes at different magnitudes] +- Revised framing: [the problem as it should actually be solved] + +## Davenport Classification +- Importance: [High/Low] +- Frequency: [High/Low] +- Recommended approach: [Decide now / Build system / Bounded deliberation / Seek perspectives] + +## Intuition-Analysis Check +- Gut says: [intuitive conclusion] +- Data says: [analytical conclusion] +- Reconciliation: [which to trust and why] + +## Decision +- Choice: [what was decided] +- Reasoning: [transparent logic] +- Reversibility: [how and when this can be revisited] +- Ethical check: [any "just this once" pressures resisted] + +## Communication Plan +- Who needs to know: [stakeholders] +- What they need to understand: [the reasoning, not just the outcome] +- When: [timing] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process theory provides the cognitive science behind why intuition and analysis sometimes conflict; this skill provides the daily practices for managing that conflict. +- **[VUCA Framework](../frameworks/vuca-framework.md)** -- Classifies the type of uncertainty in which pressured decisions occur, which informs which decision habit to prioritise. +- **[Eisenhower Matrix](../frameworks/eisenhower-matrix.md)** -- The urgent-versus-important distinction complements the importance-frequency matrix for triaging which decisions demand immediate attention versus scheduled deliberation. +- **[Evaluating and Deciding](../thinking/evaluating-and-deciding.md)** -- Provides the structured criteria-weighting and margin-of-safety methods that complement the reframing and speed habits described here. +- **[Stoic Emotional Mastery](../stoic/stoic-emotional-mastery.md)** -- The Stoic practice of pausing before assenting to impressions provides the philosophical foundation for Habit 6's overthinking circuit-breakers. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Teams that lack psychological safety suppress dissenting perspectives, directly degrading the leader's ability to gather the diverse input good decisions require. diff --git a/plugins/foreman/content/skills/leadership/delegation-and-empowerment.md b/plugins/foreman/content/skills/leadership/delegation-and-empowerment.md new file mode 100644 index 0000000..54d8b11 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/delegation-and-empowerment.md @@ -0,0 +1,196 @@ +--- +name: "delegation-and-empowerment" +description: "Develops the daily practice of effective delegation, accountability diagnosis, and team empowerment. Covers assessing which tasks require personal attention, clarifying scope and context for delegated work, allowing productive struggle, recognising and correcting micromanagement, and leading through influence rather than control. Use when feeling overwhelmed by operational tasks, noticing accountability gaps on a team, receiving feedback about micromanagement, transitioning from individual contributor to manager, or leading a team with more expertise than oneself." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - delegation + - empowerment + - accountability + - micromanagement + - autonomy + - trust + - leadership-transition + - team-development +related_skills: + - hackman-enabling-conditions + - situational-leadership + - trust-equation + - managing-up + - strategic-thinking-and-alignment +author: "Fatih Guner" +--- + +# Delegation and Empowerment + +Here is the central paradox of leadership control: the more tightly you grip, the less you actually hold. The leader who insists on reviewing every decision, approving every document, and supervising every task does not have a well-run team -- they have a team of people waiting for instructions. Control feels like safety. It is, in fact, a slow-acting poison that kills initiative, hides problems, and ensures that the leader becomes the organisation's permanent bottleneck. Delegation is not the soft skill that leadership books make it sound like. It is the hardest operational decision a leader makes every day: what to hold and what to release. + +--- + +## The Framework + +### The Four Principles of Effective Delegation + +Delegation fails not because leaders lack the will to let go but because they lack a disciplined method for deciding what to let go of, how to let go of it, and how much involvement to maintain afterward. + +**Principle 1: Assess ruthlessly which tasks require you.** + +The first question is not "Can someone else do this?" but "Must I be the one doing this?" Most leaders overestimate the number of tasks that require their personal involvement. The assessment demands honesty about where the leader's unique contribution lies -- and humility about where it does not. + +A useful sorting mechanism: + +| Category | Description | Action | +|----------|-------------|--------| +| Only-me tasks | Require the leader's specific authority, relationships, or expertise | Retain | +| Grow-someone tasks | Could be done by the leader but would develop a team member if delegated | Delegate with coaching | +| Should-have-been-delegated tasks | The leader does them out of habit, comfort, or distrust | Delegate immediately | +| Shouldn't-exist tasks | Neither the leader nor anyone else should be doing them | Eliminate | + +Most leaders discover, upon honest assessment, that the third category is larger than they expected and the first is smaller. + +**Principle 2: Clarify scope, not steps.** + +Effective delegation specifies the what and the why while leaving the how to the person doing the work. "Prepare a customer analysis for next week's board meeting that shows retention trends and churn drivers" is delegation. "Open the spreadsheet, filter by cohort, create a pivot table, format it in blue..." is micromanagement dressed as thoroughness. + +The scope must include context: why this task matters in the bigger picture. A team member who understands that the board is evaluating a potential acquisition and needs to assess customer stickiness will produce fundamentally different work than one who was simply told to "pull some retention numbers." + +**Principle 3: Calibrate involvement to the person, not the task.** + +Different people need different levels of support for the same task. A senior analyst given a board presentation for the first time needs more check-ins than one who has done it quarterly for two years. The leader's involvement should vary not by their own anxiety level but by the team member's competence and confidence for the specific assignment. + +This is the practical intersection with enabling conditions: the leader's job is to create the conditions for success -- clear direction, adequate resources, appropriate coaching -- and then step back far enough for the person to own the outcome. + +**Principle 4: Allow productive struggle.** + +The urge to rescue is the enemy of development. When a team member is struggling with a delegated task, the instinct to take it back, do it yourself, or provide the answer feels like efficiency. It is, in reality, a development tax: every rescue teaches the team that struggle is a signal to stop rather than a signal to learn. + +Productive struggle has boundaries. The leader who allows a junior employee to fail on a client-facing deliverable without intervention is not empowering anyone; they are being negligent. The calibration is between struggle that builds capability (wrestling with a complex analysis, navigating an ambiguous brief) and struggle that risks genuine harm (missing a regulatory deadline, damaging a key relationship). + +### Diagnosing Accountability Gaps + +When a team lacks accountability, the reflexive diagnosis is that the team is at fault. The more productive diagnosis starts with the leader. Accountability gaps typically stem from one of four root causes: + +1. **Unclear expectations.** The leader has not been specific about what "done" looks like, when it is due, or what quality standard applies. +2. **Insufficient resources.** The team lacks the tools, time, authority, or information to deliver what was asked. +3. **Poor strategy.** The team is accountable for executing a plan that does not make sense, and they know it. +4. **Absent feedback loops.** People do not know whether they are succeeding or failing because no one tells them. + +The diagnostic protocol is to hold a meeting -- not to assign blame but to listen. Summarise the pattern ("We've missed the last three deadlines"), ask for honest perspectives on the causes, and resist the urge to offer critical feedback during the listening phase. The true problems will surface only if the leader creates space for honesty. + +### The Micromanagement Trap + +Micromanagers are, by definition, the last to recognise their condition. The four signature behaviours: + +1. **No autonomy in execution.** Dictating how people do their jobs rather than what outcome is needed. +2. **Progress interrogation without help.** Frequently asking where things stand without offering resources, guidance, or support. +3. **Personal blame as a default.** When problems arise, looking first for a person to hold responsible rather than a system to improve. +4. **Information hoarding.** Controlling access to information as a lever of power rather than sharing it as a tool for team effectiveness. + +Each behaviour has the same root: the belief that control produces better outcomes than trust. The evidence suggests otherwise. Teams under micromanagement hide problems, avoid risk, and produce work that reflects the manager's limitations rather than the team's potential. + +--- + +## Prompts + +**Prompt 1 -- Delegation Audit:** +> List everything on my plate this week: [list major tasks and responsibilities]. For each item, help me assess whether it is an Only-me task, a Grow-someone task, a Should-have-been-delegated task, or a Shouldn't-exist task. For the items I should delegate, identify the right person and the level of involvement I should maintain. Be direct -- I suspect I am holding too much. + +**Prompt 2 -- Accountability Diagnosis:** +> My team has an accountability problem. The symptoms are [describe -- e.g., missed deadlines, dropped commitments, unclear ownership]. Walk me through a diagnostic: ask me questions to determine whether the root cause is unclear expectations, insufficient resources, poor strategy, or absent feedback loops. Then recommend specific interventions for the actual cause, not generic advice about "holding people accountable." + +**Prompt 3 -- Micromanagement Self-Assessment:** +> I have received feedback that I micromanage [or: I suspect I might be micromanaging]. My typical management behaviours include [describe -- how you assign work, how often you check in, how you respond to problems, how you share information]. Assess my behaviour against the four micromanagement patterns and identify which, if any, apply. For each pattern I exhibit, recommend a specific alternative behaviour I can practise this week. + +**Prompt 4 -- Empowerment Conversation Design:** +> I need to delegate [describe task] to [describe person -- their role, experience level, and your assessment of their readiness]. Help me design the delegation conversation: what context to provide about why this matters, how to define scope without prescribing steps, what check-in cadence to establish, and how to create conditions for them to succeed while allowing productive struggle. + +--- + +## Use Cases + +**Early-Traction Founder Who Cannot Let Go** + +A technical founder writes every line of code, reviews every pull request, and personally handles customer escalations. The team of five has grown to twelve, and the founder is working 90-hour weeks while the engineers wait for code reviews that take three days. Applying the delegation audit, the founder discovers that only two of their current tasks -- investor relations and architectural decisions -- are genuine Only-me tasks. Code review, customer escalation triage, and sprint planning are all Grow-someone tasks. The founder delegates code review to the senior engineer with a "scope not steps" brief: "Ensure production readiness and mentor junior developers through the process." The senior engineer, given authority and context, reduces review turnaround to four hours. The founder recovers 25 hours per week. + +**Growth-Stage Team with an Accountability Fog** + +A product team consistently misses sprint commitments. The VP of Product assumes the team is underperforming and considers adding project management overhead. Running the accountability diagnostic reveals a different story: the team is accountable for executing a roadmap that changes every two weeks based on the CEO's latest customer conversation. The problem is not the team's commitment but the leader's strategy. The VP works with the CEO to establish a roadmap freeze policy with a defined change request process. Sprint completion rates double within one quarter -- not because the team worked harder, but because the goal stopped moving. + +**Scale-Stage Leader Recovering from Micromanagement** + +A VP of Operations receives 360-degree feedback indicating that direct reports feel suffocated. The VP, who built their career on operational excellence, genuinely does not see the problem -- they view their involvement as quality assurance. Analysis reveals all four micromanagement patterns: the VP dictates process, asks for daily status updates without adding value, blames individuals for systemic problems, and keeps competitive intelligence to themselves. The VP begins with the lowest-risk change: replacing daily status interrogations with a weekly dashboard that the team self-reports, and biweekly one-on-ones focused on removing blockers rather than reviewing work. Within three months, the team's initiative -- measured by self-started projects and proactive problem-solving -- increases measurably. + +--- + +## Anti-Patterns + +1. **Delegating tasks but not authority.** Asking someone to lead a project but requiring them to seek approval for every decision within it. This creates accountability without agency -- the most demoralising combination in management. + +2. **Delegating only what you dislike.** Using delegation as a garbage disposal for unpleasant tasks while retaining the interesting work. Team members notice this pattern immediately, and it erodes both trust and motivation. + +3. **Rescuing at the first sign of difficulty.** Taking back delegated work when the person struggles. This teaches the team that struggle is a failure state rather than a learning state, and it ensures the leader remains the permanent bottleneck. + +4. **Confusing delegation with abdication.** Handing off a task and disappearing entirely. Delegation without appropriate follow-up is not empowerment; it is abandonment. The leader remains accountable for outcomes even when they delegate execution. + +5. **Diagnosing accountability problems as people problems.** Defaulting to "the team isn't committed enough" before examining whether expectations were clear, resources were sufficient, and strategy was sound. Most accountability failures are leadership failures in disguise. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder letting go of operational tasks | The founder's identity is intertwined with doing the work. Delegation requires not just a method but a psychological shift from "I do" to "I enable." | +| Growth | Building delegation as organisational capability | As layers of management emerge, delegation is no longer just the founder's challenge -- it must be taught and modelled at every leadership level. | +| Scale | Systemic empowerment design | Delegation becomes structural: decision rights, escalation protocols, information flows, and accountability frameworks replace individual delegation conversations. | + +The challenge intensifies with each stage because the stakes of delegation increase. At early traction, a poorly delegated task wastes a week. At scale, a poorly delegated initiative wastes a quarter and a million dollars. The principles remain the same; the consequences of applying them poorly escalate dramatically. + +--- + +## Output Template + +```markdown +# Delegation and Empowerment Assessment + +## Task Audit +| Task | Category | Delegate To | Scope Brief | Check-in Cadence | +|------|----------|-------------|-------------|-----------------| +| [Task 1] | [Only-me / Grow-someone / Should-have-delegated / Eliminate] | [Person or N/A] | [What + why, not how] | [Frequency] | +| [Task 2] | [Category] | [Person or N/A] | [Brief] | [Frequency] | +| [Task 3] | [Category] | [Person or N/A] | [Brief] | [Frequency] | + +## Accountability Diagnostic +- **Primary root cause:** [Unclear expectations / Insufficient resources / Poor strategy / Absent feedback] +- **Evidence:** [Specific observations] +- **Intervention:** [Specific action] + +## Micromanagement Check +| Behaviour | Present? | Evidence | Alternative | +|-----------|----------|----------|-------------| +| Dictating process | [Yes/No] | [Example] | [New behaviour] | +| Progress interrogation | [Yes/No] | [Example] | [New behaviour] | +| Personal blame default | [Yes/No] | [Example] | [New behaviour] | +| Information hoarding | [Yes/No] | [Example] | [New behaviour] | + +## Empowerment Actions (Next 30 Days) +| Action | Person Affected | Expected Outcome | +|--------|----------------|-----------------| +| [Specific delegation or empowerment action] | [Who benefits] | [What changes] | +``` + +--- + +## Related Skills + +- **[Hackman's Enabling Conditions](../frameworks/hackman-enabling-conditions.md)** -- Provides the structural framework for team effectiveness that delegation operates within; the enabling conditions define what "setting someone up for success" actually means. +- **[Situational Leadership](../frameworks/situational-leadership.md)** -- The principle of calibrating involvement to the person and situation is the practical application of situational leadership theory to daily delegation decisions. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Delegation is an act of trust; the reliability and credibility variables of the trust equation determine whether a leader can delegate with confidence. +- **[Managing Up](managing-up.md)** -- Leaders who delegate effectively free time for strategic thinking and upward relationship management; the two skills enable each other. +- **[Strategic Thinking and Alignment](strategic-thinking-and-alignment.md)** -- The strategic altitude problem is often a delegation problem: leaders stuck at 500 feet have not delegated enough ground-level work. +- **[Information Asymmetry](../game-theory/information-asymmetry.md)** -- Every delegation creates a principal-agent relationship where moral hazard and adverse selection dynamics shape whether the delegated work is done faithfully. diff --git a/plugins/foreman/content/skills/leadership/emotional-courage.md b/plugins/foreman/content/skills/leadership/emotional-courage.md new file mode 100644 index 0000000..6879e83 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/emotional-courage.md @@ -0,0 +1,201 @@ +--- +name: "emotional-courage" +description: "Builds the capacity for daily acts of leadership courage, from raising difficult issues and sharing vulnerability appropriately to channelling anxiety productively and taking principled stands. Provides incremental practices for developing courage as a skill rather than treating it as an innate trait. Use when avoiding a difficult conversation, feeling paralysed by anxiety before a high-stakes situation, sensing that you are holding back from necessary confrontation, wanting to build vulnerability into your leadership style without oversharing, or preparing to advocate for an unpopular position." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - courage + - vulnerability + - anxiety + - emotional-regulation + - difficult-conversations + - authenticity + - leadership-presence + - risk-taking +related_skills: + - emotional-intelligence + - radical-candor + - trust-equation + - psychological-safety + - learning-from-failure + - humility-and-power +author: "Fatih Guner" +--- + +# Emotional Courage + +Courage is not the absence of fear -- it is a muscle that atrophies without use. The spectrum runs from silence to recklessness, and most leaders cluster near the silent end, mistaking caution for wisdom. They do not raise the issue everyone knows exists. They do not challenge the senior executive whose strategy is failing. They do not tell the underperforming friend they hired that the friendship cannot substitute for results. These are not dramatic acts of whistleblowing or organisational martyrdom. They are small, daily decisions to feel the discomfort of honesty and act anyway. Maya Angelou described it precisely: courage is built by lifting five-pound bags before attempting the hundred-pound ones. The question is not whether a leader possesses courage but whether they are practising it. + +--- + +## The Framework + +### The Anatomy of Emotional Courage + +Emotional courage is the willingness to fully experience uncomfortable emotions -- fear, shame, anxiety, vulnerability -- in service of doing what leadership requires. It sits at the intersection of self-awareness and action. A leader who feels the fear but acts anyway is courageous. A leader who feels the fear and rationalises inaction is merely comfortable. + +Emotional courage is distinct from physical or intellectual courage. It does not require risking one's body or being the smartest person in the room. It requires risking emotional exposure: being seen as uncertain, being challenged, being wrong, being honest in a context where dishonesty is easier. + +### Practice 1: Open Up Without Oversharing + +The boundary between vulnerability and oversharing is the most frequently misjudged line in leadership communication. Employees benefit from feeling a personal connection to their leader, but excessive emotional disclosure undermines authority and burdens the team with the leader's unprocessed experience. + +**The calibration test:** Before sharing something personal, ask whether you would be comfortable hearing the same comment from your own boss. Telling the team you are in a bad mood because it has been a difficult day is transparent. Telling them you are in a bad mood because of a fight with your partner is oversharing. The first creates connection; the second creates discomfort. + +**The principle:** Share the emotional weather without narrating the storm. "I am frustrated by how this quarter has gone and I want to figure out what we do differently" is vulnerable and productive. "I barely slept last night worrying about whether we'll all have jobs next quarter" is honest but destructive. + +### Practice 2: Channel Anxiety as Leadership Fuel + +Anxiety is not a deficiency to be eliminated; it is a signal to be interpreted. It can deplete energy and drive poor decisions, but it can also sharpen attention, accelerate threat detection, and build tolerance for discomfort over time. + +**The channelling protocol:** + +1. **Notice the manifestation.** Physical symptoms (churning stomach, tight chest) and emotional ones (overwhelm, panic) are the first indicators. Most leaders suppress these signals rather than reading them. +2. **Name the trigger.** Anxiety without a named cause is more paralysing than anxiety with one. "I am anxious" is vague and overwhelming. "I am anxious because the board presentation has three unresolved data points" is specific and actionable. +3. **Pause before reacting.** The gap between stimulus and response is where courage lives. An anxious leader who fires off an urgent Slack message at 11 PM is not being responsive; they are being reactive. The pause creates space for a response that serves the situation rather than the anxiety. +4. **Track patterns over time.** A journal of anxiety triggers reveals which situations genuinely warrant concern and which are habitual overreactions. This data is the foundation for recalibrating one's emotional baseline. + +### Practice 3: Build Courage Incrementally + +The metaphor of progressive weight training applies directly. Leaders who attempt a hundred-pound act of courage -- confronting the CEO, whistleblowing, firing a founding team member -- without having practised five-pound acts will almost certainly fail or avoid the attempt entirely. + +**The incremental programme:** + +| Weight | Example Act | What It Builds | +|--------|------------|----------------| +| 5 lbs | Calling customer service and stating a complaint directly without hedging | Comfort with directness | +| 10 lbs | Giving honest feedback to a peer on a low-stakes project | Tolerance for interpersonal tension | +| 25 lbs | Raising a concern in a team meeting that no one else is voicing | Willingness to be the dissenter | +| 50 lbs | Having a difficult performance conversation with a direct report | Capacity to deliver unwelcome truth | +| 75 lbs | Pushing back on a senior leader's flawed strategy in a public setting | Ability to challenge authority constructively | +| 100 lbs | Taking a principled stand on an issue that could cost personal capital | Moral courage under genuine risk | + +The key insight is that each level builds the neural and emotional pathways for the next. A leader who has never practised directness with a customer service representative is unlikely to suddenly summon it in a boardroom. + +### Practice 4: Take Principled Stands -- Without Martyrdom + +Research reveals a more nuanced picture of workplace courage than the cultural narrative suggests. Most acts of courage do not come from outsiders or whistleblowers. They come from respected insiders at all levels who take action -- campaigning for a risky strategic move, pushing to change an unfair policy, speaking out against unethical behaviour -- because they believe it is the right thing to do. + +Their reputations and track records enable them to make more headway than those on the margins. And when they manage the process well, they do not necessarily pay a high price for their actions; indeed, their status may rise as they create positive change. + +The implication is practical: courage is more effective and less costly when exercised from a position of earned credibility. Building trust, demonstrating competence, and establishing reliability are not alternatives to courage -- they are preconditions for effective courage. + +### Practice 5: Patience as Quiet Courage + +Patience rarely appears in discussions of courage, but it belongs there. Staying calm during setbacks, waiting for a strategy to prove itself, resisting the pressure for immediate action when careful deliberation is warranted -- these are acts of courage in an environment that rewards speed above thoughtfulness. + +The always-on working world treats immediate replies and constant connectivity as virtues. Often, though, the most courageous act is to be methodical, careful, and slow -- to resist the anxiety-driven urge to "do something" when the best response is to think first. + +--- + +## Prompts + +**Prompt 1 -- Courage Inventory:** +> Help me identify where I am avoiding emotional courage in my leadership. My current situation includes [describe role, team, key challenges]. Ask me about conversations I have been postponing, issues I know exist but have not raised, feedback I have not delivered, and positions I have not taken. For each avoidance, help me identify the specific fear driving it and design a five-pound practice to start building the required courage. + +**Prompt 2 -- Vulnerability Calibration:** +> I want to be more open with my team but I am unsure where the line is between vulnerability and oversharing. Recent situations where I considered sharing something personal include [describe 2-3 examples]. For each, assess whether sharing would build connection or create discomfort, and explain why. Then help me develop guidelines for my specific context and role. + +**Prompt 3 -- Anxiety Channelling Plan:** +> I experience significant anxiety in [describe situations -- e.g., board presentations, difficult conversations, performance reviews]. My typical anxiety response includes [describe physical and emotional symptoms and how you currently cope]. Design an anxiety channelling protocol tailored to my triggers that helps me use the anxiety as information rather than succumbing to it. + +**Prompt 4 -- Principled Stand Preparation:** +> I need to take a stand on [describe the issue] which I believe is the right thing to do but which carries risk because [describe the potential cost]. Help me prepare by assessing my current credibility capital, identifying allies, crafting my argument in terms that appeal to shared values rather than personal conviction, and anticipating objections. Design the conversation or communication so that I can be courageous without being reckless. + +--- + +## Use Cases + +**Validation-Stage Founder Avoiding a Co-Founder Conversation** + +Two co-founders have not discussed the growing gap in their contributions. One works sixty hours per week; the other has taken a consulting engagement "on the side" that consumes most of their time. The engaged founder avoids the conversation because the other co-founder is a close friend and the potential conflict feels threatening to the relationship. Applying the incremental courage programme, the founder starts with a five-pound practice: being direct with a vendor about an unsatisfactory deliverable. Then a ten-pound practice: giving honest feedback to an advisor. By the time the co-founder conversation arrives, the founder has built enough comfort with directness to say: "We need to talk about whether we are both still fully committed to this, and what it means if we are not." The conversation is uncomfortable. The outcome -- a revised equity split and renewed commitment -- is better than six more months of avoidance. + +**Growth-Stage Manager Channelling Pre-Meeting Anxiety** + +A director of engineering experiences debilitating anxiety before every executive leadership meeting. The anxiety manifests as over-preparation (spending eight hours on a fifteen-minute update), physical symptoms (insomnia the night before), and avoidance (delegating attendance to a subordinate when possible). Applying the channelling protocol, the director begins naming triggers: the anxiety is not about the meeting itself but about a specific executive who asks adversarial questions. With the trigger named, the preparation shifts from comprehensive coverage of every possible question to focused preparation for the three most likely adversarial questions. The anxiety decreases from paralysing to productive, and the director's meeting performance improves because the preparation is targeted rather than exhaustive. + +**Scale-Stage VP Taking a Stand on a Flawed Strategy** + +A VP of Customer Success becomes convinced that the company's aggressive upsell strategy is increasing short-term revenue at the cost of long-term customer health. Churn data supports the concern, but the Chief Revenue Officer is politically powerful and personally invested in the strategy. The VP assesses their credibility capital (strong track record, respected by the CEO, well-liked by the sales team) and designs the approach: presenting churn trend data in a private meeting with the CEO, framing the concern in terms of customer lifetime value rather than as a criticism of the CRO, and proposing a pilot programme that tests a relationship-first approach with a subset of accounts. The CEO authorises the pilot. Within two quarters, the pilot accounts show 40% lower churn. The strategy shifts -- not because the VP was a martyr, but because they were a credible insider who managed the process well. + +--- + +## Anti-Patterns + +1. **Confusing courage with confrontation.** Courage is not the willingness to fight; it is the willingness to feel. A leader who picks fights is not courageous -- they may simply be unable to tolerate the discomfort of unresolved tension. Genuine courage sometimes looks like patience, sometimes like vulnerability, and only occasionally like confrontation. + +2. **Performing vulnerability for strategic gain.** Sharing personal struggles because it is "what authentic leaders do" rather than because it serves the team's needs. Calculated vulnerability is detectable and produces the opposite of its intended effect: it increases perceived self-orientation rather than building connection. + +3. **Attempting hundred-pound acts without practice.** Confronting the CEO about a strategic failure without ever having practised giving direct feedback in low-stakes situations. The resulting fumble -- too aggressive, too tentative, too emotional -- reinforces the avoidance it was meant to overcome. + +4. **Treating anxiety as a problem to solve rather than a signal to read.** Medicating, suppressing, or ignoring anxiety rather than understanding what it is communicating. Anxiety that persistently attaches to a specific situation or person is often surfacing a genuine problem that deserves attention. + +5. **Assuming courage requires martyrdom.** The belief that taking a stand must cost something -- that if it was easy, it was not courageous. Research suggests otherwise: well-managed acts of courage by credible insiders frequently enhance rather than diminish the person's standing. The martyrdom assumption prevents many leaders from even attempting the courageous act. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Co-founder and early team conversations | The relationships are personal, the stakes are existential, and the avoidance patterns are hardest to break because friendship and business are intertwined. | +| Early Traction | Setting courage norms for the first team | The leader's willingness to raise difficult issues, share appropriate vulnerability, and welcome dissent establishes the cultural template for every future hire. | +| Growth | Courage across organisational boundaries | Taking stands with peer leaders, challenging cross-functional decisions, and raising issues that span departmental politics require courage exercised in more complex relational landscapes. | +| Scale | Institutional courage | The leader must create systems -- anonymous feedback channels, skip-level meetings, structured dissent processes -- that enable courage at scale rather than depending on individual heroism. | + +--- + +## Output Template + +```markdown +# Emotional Courage Development Plan + +## Courage Avoidance Inventory +| Situation I Am Avoiding | Specific Fear | Cost of Continued Avoidance | Courage Weight (5-100 lbs) | +|------------------------|---------------|---------------------------|---------------------------| +| [Situation 1] | [Fear] | [What avoidance costs] | [Weight] | +| [Situation 2] | [Fear] | [What avoidance costs] | [Weight] | + +## Incremental Practice Plan +| Week | Practice Act | Weight | What I Will Feel | How I Will Respond | +|------|------------|--------|-----------------|-------------------| +| 1 | [Specific low-stakes act] | [5-10 lbs] | [Expected discomfort] | [Planned response] | +| 2 | [Slightly higher-stakes act] | [10-25 lbs] | [Expected discomfort] | [Planned response] | +| 3 | [Medium-stakes act] | [25-50 lbs] | [Expected discomfort] | [Planned response] | +| 4 | [The act I have been avoiding] | [Actual weight] | [Expected discomfort] | [Planned response] | + +## Vulnerability Guidelines (My Context) +- **Safe to share:** [Types of personal information that build connection] +- **Boundary:** [Types of personal information that burden the team] +- **Test:** [My personal calibration question before sharing] + +## Anxiety Map +| Trigger | Physical Signal | Emotional Signal | Named Cause | Productive Response | +|---------|----------------|-----------------|-------------|-------------------| +| [Trigger 1] | [Symptom] | [Feeling] | [Specific cause] | [Channelled response] | +| [Trigger 2] | [Symptom] | [Feeling] | [Specific cause] | [Channelled response] | + +## Principled Stand Preparation (If Applicable) +- **The issue:** [What needs to be said or done] +- **My credibility capital:** [Track record, relationships, standing] +- **Allies:** [Who shares this concern] +- **Framing:** [How to present in terms of shared values] +- **Contingency:** [If it goes badly, what is my fallback] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness is the foundation upon which emotional courage is built; without the ability to name and understand one's emotions, courage becomes recklessness. +- **[Radical Candor](../frameworks/radical-candor.md)** -- The "challenge directly" dimension of radical candor is a daily expression of emotional courage; the framework provides structure for courageous conversations. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Emotional courage in a leader creates psychological safety for the team; the two are causally linked. +- **[Learning from Failure](learning-from-failure.md)** -- Sharing failures authentically is one of the most common and valuable expressions of emotional courage. +- **[Humility and Power](humility-and-power.md)** -- Acknowledging weakness requires emotional courage; humility and courage are complementary disciplines, not opposing ones. +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- The Stoic Inner Citadel concept provides the philosophical foundation for building the endurance that progressive courage training develops behaviourally. diff --git a/plugins/foreman/content/skills/leadership/employee-engagement-retention.md b/plugins/foreman/content/skills/leadership/employee-engagement-retention.md new file mode 100644 index 0000000..3938b84 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/employee-engagement-retention.md @@ -0,0 +1,214 @@ +--- +name: "employee-engagement-retention" +description: "Provides a practical, behaviour-level guide to why employees stay, why they leave, and what leaders do daily that determines which outcome occurs. Covers the eight retention-destroying behaviours, recognition versus appreciation, purpose-building, learning as a retention lever, and structured check-in practices that surface dissatisfaction before it becomes a resignation letter. Use when experiencing unexpected attrition, when exit interviews reveal leadership failures, when designing retention programmes, when coaching managers on engagement, or when building a culture people do not want to leave." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - retention + - engagement + - employee-experience + - recognition + - appreciation + - purpose + - motivation + - turnover +related_skills: + - leader-self-reflection + - leadership-style-adaptation + - ai-era-leadership + - psychological-safety + - radical-candor + - maslow-hierarchy + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +# Employee Engagement and Retention + +A comprehensive guide to making your best employees quit: + +Constrain their processes until they spend more time waiting for approvals than doing actual work. Set goals that contradict each other so they must choose which failure to own. Assign them roles that ignore their strongest capabilities. Give them tasks so easy that boredom becomes their primary workplace emotion. Waste their time in meetings that could have been emails about meetings that should not have existed. Disregard their psychological safety until they learn that speaking up is punished and silence is rewarded. Create an environment so comfortable that no one is challenged, stretched, or developed. Lead with bias and call it intuition. + +This list is not satire. It is a clinical summary of the eight behaviours that research identifies as the primary drivers of voluntary attrition. Every item is something a leader does -- not something that happens to a team. The uncomfortable corollary: if your people are leaving, the first place to look is the mirror. + +--- + +## The Practice + +### The Eight Retention-Destroying Behaviours + +Each of these behaviours is a leadership choice, often made unconsciously, that erodes the conditions people need to stay. + +**1. Process Constraints** +When employees must wait for others to provide information or resources before they can do their own work, productivity suffers and frustration compounds. The leader's job: identify bottlenecks through open conversation, then use positional influence to clear them. Every roadblock you remove is a reason to stay. + +**2. Inconsistent Goals** +Forcing employees to choose between contradictory expectations -- faster service versus more thorough documentation, innovation versus risk avoidance -- produces stress without resolution. The remedy: write down your team's goals, audit them for contradictions, and resolve the conflicts before asking anyone to execute. + +**3. Role Misassignment** +Employees whose talents and knowledge are underutilised feel invisible. The gap between what they can do and what they are asked to do becomes a daily reminder of wasted potential. Talk to people about their career goals. Match responsibilities to capabilities. Expand scope before they start looking elsewhere for it. + +**4. Insufficient Challenge** +Boredom is a resignation trigger that managers consistently underestimate. When work is too easy, motivation and engagement decay. Assign tasks that enhance knowledge and skills. Create learning agendas with target goals and road maps. Challenge is a form of respect. + +**5. Resource Waste** +Time is the resource most frequently squandered. Endless meetings, unnecessary attendees, and low-value tasks consume the hours that employees need for their highest-impact work. Before adding someone to a meeting or assigning additional work, ask: is this person genuinely the only one who can do this? + +**6. Psychological Safety Neglect** +Employees who do not feel safe to take risks, disagree openly, or admit mistakes become disengaged passengers rather than committed contributors. Show openness to new ideas. Ask questions before providing answers. Thank people for input, especially when it challenges your position. Own your own mistakes publicly. + +**7. Insufficient Pressure** +A moderate level of pressure improves performance. Too little creates purposelessness and drift. Provide regular feedback -- both affirming and developmental. Use coaching to identify improvement areas. Connect individual roles to the organisation's larger mission. Comfort without challenge produces complacency, not loyalty. + +**8. Biased Leadership** +When employees perceive decisions as driven by preference rather than evidence, trust collapses. Before making decisions that affect people, examine what is driving you. Are you basing the choice on data or on familiarity? Are there knowledge gaps you need to fill? Ask for feedback on your decision-making patterns -- and act on what you hear. + +### Recognition Versus Appreciation: The Distinction That Matters + +Leaders use these terms interchangeably. Employees experience them as fundamentally different. + +**Recognition** is feedback based on results or performance. It can be formal (awards, promotions, bonuses) or informal (verbal acknowledgment, a handwritten note). Recognition says: what you accomplished matters. + +**Appreciation** is acknowledgment of a person's inherent value -- not their output, but their worth as a colleague and a human being. Appreciation says: who you are matters. + +If you focus solely on recognition, you connect with people only through their achievements. You miss opportunities to support team members during difficult stretches when results are scarce but effort is genuine. Recognition is earned. Appreciation is owed -- all the time. + +### Purpose as a Retention Mechanism + +Instilling purpose takes more than speeches or mission statements. Done poorly, grand declarations of purpose trigger cynicism rather than commitment. Two principles govern effective purpose-building: + +1. **Purpose is a feeling, not a statement.** Telling people their work is important has limited impact. Showing them -- through customer testimonials, impact data, or direct connection with the beneficiaries of their efforts -- transforms abstract purpose into lived experience. + +2. **Authenticity is non-negotiable.** If your sudden interest in impact follows years of emphasising quarterly profits, the pivot will read as manipulative rather than genuine. Purpose must emerge from consistent behaviour, not a rebranding exercise. + +### The Five Questions You Should Be Asking + +Gallup research found that 51% of employees who quit say that no one -- including their manager -- asked about their job satisfaction before they left. Five questions close this gap: + +1. How would you like to grow here? +2. Do you feel a sense of purpose in your job? +3. What do you need from me to do your best work? +4. What is the company not doing that it should be doing? +5. Are you able to do what you do best every day? + +These are not annual review questions. They are quarterly conversation starters. The answers reveal problems you can solve and growth opportunities you can create -- before the employee decides to solve the problem by leaving. + +### Learning as the Underestimated Retention Lever + +Research from Harvard Business School and Boston Consulting Group reveals that employees are often far more eager to learn new skills than their leaders assume. Workers do not share leadership's anxiety about the future; they want to be developed for it. Offering learning opportunities -- stretch assignments, cross-functional exposure, formal training -- signals investment in a person's future. Withholding those opportunities signals that you see them as a static resource rather than a developing professional. + +Reward structures matter as well. Time-based incentives -- additional vacation days, schedule flexibility, services that save personal time -- often outperform monetary rewards in driving satisfaction. Framing non-cash benefits in financial terms helps employees appreciate their value. + +--- + +## Prompts + +**Prompt 1 -- Retention Risk Audit:** +> Assess my team's retention risk by evaluating each of the eight retention-destroying behaviours. My team of [number] people works in [function/industry]. Here is what I know about their current experience: [describe any signals -- turnover, complaints, engagement survey data, or your own observations]. For each behaviour, rate my team's exposure (Low/Medium/High), identify specific evidence, and recommend corrective actions I can take this week. + +**Prompt 2 -- Exit Pattern Analysis:** +> Over the past [timeframe], [number] employees have left my team/company. Here is what I know about each departure: [describe circumstances, exit interview data if available, tenure, and role]. Analyse these departures for patterns using the eight retention-destroying behaviours as a diagnostic framework. Identify the two or three systemic issues driving attrition and design an intervention plan with specific actions, timelines, and metrics. + +**Prompt 3 -- Recognition and Appreciation Programme:** +> Design a recognition and appreciation programme for my team of [number] people. Current state: [describe what you do now, if anything]. The programme should include both formal recognition mechanisms (tied to performance) and informal appreciation practices (acknowledging inherent value). Specify daily, weekly, and monthly rhythms. Include guidance for how I and other managers should adapt these practices for introverts versus extroverts, remote versus in-office employees, and individual versus team contributions. + +**Prompt 4 -- Purpose Integration:** +> My company's mission is [mission statement]. My team's function is [function]. Help me design three specific practices that connect my team's daily work to the company's purpose in ways that feel authentic rather than performative. Each practice should be sustainable (not a one-time event), concrete (not abstract), and emotionally resonant (shows impact, not just states it). + +**Prompt 5 -- Engagement Conversation Guide:** +> I want to start having meaningful engagement conversations with my [number] direct reports. Create a conversation guide based on the five satisfaction questions that I can use in one-on-one meetings. For each question, provide: (a) how to introduce it naturally, (b) follow-up questions based on likely responses, (c) what to do with the information gathered, and (d) how to follow up in the next conversation to demonstrate that I listened and acted. + +--- + +## Use Cases + +**Growth-Stage Startup Losing Senior Engineers** +A 70-person company has lost four senior engineers in six months. Exit interviews cite "lack of growth opportunities" -- but the company offers conference budgets and training stipends. The retention audit reveals the real issue: role misassignment combined with insufficient challenge. Senior engineers are maintaining legacy code rather than building new systems. Their conference attendance gave them exposure to exciting work elsewhere. The intervention: restructure the engineering team so that senior engineers spend at least 40% of their time on new architecture and mentoring junior engineers. Attrition stops within one quarter. + +**Scale-Stage Company with High Engagement Scores but Rising Turnover** +A 400-person company scores well on engagement surveys but experiences 22% annual turnover. The paradox resolves when the eight behaviours are examined: the culture is warm and supportive (high psychological safety, strong appreciation), but insufficiently challenging (low pressure, easy tasks, limited feedback). Top performers leave because they are bored, not because they are unhappy. The intervention: introduce stretch assignments for high performers, pair them with executive mentors, and create a "next-level readiness" programme that explicitly prepares people for roles above their current level. + +**Early-Traction Founder Who Cannot Retain First Hires** +A founder on their third office manager in two years blames the talent pool. The retention audit reveals a different story: inconsistent goals (the role was defined differently each week), process constraints (every decision required the founder's approval), and biased leadership (the founder favoured employees whose working style mirrored their own). The intervention begins with the founder, not the hire: clarify the role's actual responsibilities, delegate real authority, and establish a weekly one-on-one where the founder asks the five satisfaction questions and -- critically -- acts on the answers. + +--- + +## Anti-Patterns + +1. **The Compensation Reflex.** Responding to every retention problem with a raise or a bonus. Money prevents dissatisfaction but rarely creates engagement. If the underlying issue is role misassignment or purpose deficit, more money simply makes the employee a better-paid disengaged person who will leave later rather than sooner. + +2. **The Annual Engagement Survey Illusion.** Believing that a yearly survey captures real-time sentiment. Engagement is a daily phenomenon. Quarterly conversations with the five questions reveal more than any annual questionnaire, and they demonstrate care through the act of asking. + +3. **The Blame-the-Departing.** Attributing every resignation to the employee's personal circumstances rather than examining leadership's contribution. "They wanted something we couldn't offer" is sometimes true and often a convenient deflection from "We failed to offer what we could have." + +4. **The Perks Pile.** Stacking benefits -- ping-pong tables, free lunches, unlimited PTO -- as substitutes for the fundamentals: meaningful work, competent management, psychological safety, and genuine growth opportunities. Perks attract candidates. Fundamentals retain employees. + +5. **The Equal Treatment Trap.** Treating recognition and appreciation identically across the team. Extroverts and introverts demonstrate commitment differently. Some people thrive on public acknowledgment; others find it excruciating. Ask each person how they prefer to be recognised -- and then do it that way. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-employee relationship | Every departure is existential when the team is ten people. The founder's daily behaviour -- how they set goals, assign work, and respond to input -- is the entire retention strategy. There is no HR layer to compensate for leadership gaps. | +| Growth | Manager capability | As the company adds management layers, retention becomes a distributed responsibility. The most common failure: promoting high performers into management without teaching them the eight behaviours. Every new manager is a potential attrition vector or retention asset. | +| Scale | Systemic programmes | At scale, individual relationships cannot carry the full retention load. Formal recognition programmes, structured career pathways, purpose-integration rituals, and engagement measurement systems must be institutionalised. The leadership challenge shifts from personal practice to organisational design. | + +--- + +## Output Template + +```markdown +# Employee Engagement and Retention Assessment + +**Team/Organisation:** [Name] +**Leader:** [Name] +**Date:** [Date] +**Current Turnover Rate:** [Percentage] + +## Eight Behaviours Audit + +| Behaviour | Risk Level | Evidence | Corrective Action | Owner | Timeline | +|-----------|-----------|----------|-------------------|-------|----------| +| Process Constraints | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Inconsistent Goals | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Role Misassignment | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Insufficient Challenge | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Resource Waste | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Psych Safety Neglect | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Insufficient Pressure | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Biased Leadership | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | + +## Recognition and Appreciation Plan +- **Formal recognition:** [Mechanisms and frequency] +- **Informal appreciation:** [Daily/weekly practices] +- **Personalisation notes:** [How to adapt for different team members] + +## Engagement Conversation Schedule +| Team Member | Next Conversation | Key Questions to Prioritise | Follow-Up from Last | +|-------------|-------------------|-----------------------------|---------------------| +| [Name] | [Date] | [Questions] | [Actions taken] | + +## Retention Metrics +- 90-day retention rate: [Current] / [Target] +- 12-month retention rate: [Current] / [Target] +- Engagement conversation completion rate: [Current] / [Target] +- Internal mobility rate: [Current] / [Target] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Edmondson's framework provides the theory for one of the eight retention-destroying behaviours; this skill covers the daily leadership practices that build or erode it. +- **[Radical Candor](../frameworks/radical-candor.md)** -- The balance of care and challenge maps directly to the recognition-appreciation distinction and the pressure calibration challenge. +- **[Maslow's Hierarchy](../frameworks/maslow-hierarchy.md)** -- Retention operates across Maslow's levels: from basic security (fair compensation) through belonging (appreciation) to self-actualisation (purpose and growth). +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The eight behaviours audit requires the kind of honest self-examination this companion skill develops as a daily practice. +- **[Inspiring and Retaining](../people/inspiring-and-retaining.md)** -- Provides the interpersonal practices -- personalised recognition, audience-centred presentations, content curation -- that complement the structural retention strategies here. +- **[Mentoring and Coaching](mentoring-and-coaching.md)** -- Learning is the underestimated retention lever; structured mentoring relationships operationalise the development that keeps high performers engaged. diff --git a/plugins/foreman/content/skills/leadership/focus-and-priority-management.md b/plugins/foreman/content/skills/leadership/focus-and-priority-management.md new file mode 100644 index 0000000..b1f77a5 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/focus-and-priority-management.md @@ -0,0 +1,212 @@ +--- +name: "focus-and-priority-management" +description: "Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of uninterrupted deep work, or when data presentations fail to land because preparation time was consumed by low-value obligations." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - focus + - priorities + - time-management + - meetings + - deep-work + - calendar + - attention + - saying-no + - data-presentation +related_skills: + - eisenhower-matrix + - flow-state + - covey-seven-habits + - leader-resilience-and-wellbeing + - learning-agility +author: "Fatih Guner" +--- + +# Focus and Priority Management + +Perform an autopsy on your calendar from last week. Categorise every entry into four buckets: meetings you led, meetings you attended, blocks of focused individual work, and everything else. Now calculate the percentages. If focused work occupies less than 20% of your week, you are not leading -- you are being led, by other people's agendas, by the tyranny of the next notification, and by the organisational fiction that presence in a room equals contribution to an outcome. + +Michael Porter and Nitin Nohria's research on how CEOs manage time reveals a sobering truth: calendars are not neutral organisational tools. They are symbols. The tasks and people a leader shows up for communicate what matters more clearly than any strategy memo. An executive who spends 80% of the week in meetings and 3% on strategic thinking has, in effect, declared that reaction is the company's strategy. + +The Eisenhower matrix -- urgent versus important -- provides the theoretical scaffolding for this problem (see `eisenhower-matrix.md` for the framework). This skill concerns itself with the mechanical, behavioural, and social dimensions of actually living by that distinction: how to schedule deep work, how to run meetings that earn the time they consume, how to say no without damaging relationships, and how to present data so the meetings you do attend produce decisions rather than more meetings. + +--- + +## The Practice + +### Scheduling Deep Work + +Alice Boyes's research distils the scheduling challenge to a single principle: decide in advance when you will do important work, and then protect that time as though it were an unmovable meeting. The specific method matters less than the commitment. + +Effective approaches include: + +- **Morning fortress.** Reserve the first 90 minutes of each day for strategic work. No email, no Slack, no meetings. The brain's prefrontal cortex is freshest in the morning for most people; squandering that window on inbox triage is a neurological misallocation. +- **One sacred day.** Block an entire day per week -- typically Wednesday or Thursday -- for deep work. Communicate the block to the team so they do not interpret absence as unavailability. +- **Bite-size progress.** When full blocks are impossible, break strategic projects into 20-minute tasks that can fit between meetings. Keep a running list of these micro-tasks so that a sudden 15-minute gap becomes an opportunity, not dead time. + +### Meeting Hygiene + +Meetings are the largest single consumer of leadership time. Most of them underperform because they lack one or more of the following: + +**Clear decision-making process.** Bob Frisch and Cary Greene's research shows that confusion about who decides and how produces tension. Before any meeting begins, state the ground rules: Will there be a vote? Does someone hold veto power? Is the meeting for input or for ratification? Ambiguity on these questions turns a 30-minute discussion into a 90-minute argument. + +**Question-based agendas.** Steven Rogelberg recommends replacing topic-based agenda items with questions the group must answer. "Budget problems" becomes "How will we reduce spending by $100K this year?" Questions focus attention on outcomes, clarify who should be in the room, and signal when the meeting is done -- when the questions are answered. + +**Hybrid discipline.** When presenting to both in-person and remote audiences, leaders reliably neglect the screen. Sarah Gershman and Rae Ringel advise alternating eye contact between the room and the camera, moving closer to the camera periodically, mixing in-person and remote participants in breakout groups, and keeping the presentation short. Virtual fatigue is real; every presentation feels longer through a screen. + +### The Art of Saying No + +Elizabeth Grace Saunders identifies the core difficulty: saying no feels like a social transgression. The solution is scripted phrases practised until they feel natural. + +- **Redirecting:** "This might be a great growth opportunity for someone. I am happy to connect you with Kei, who is looking to develop in that area." +- **Capacity boundary:** "Thanks, but I have to decline. My schedule is at capacity." +- **Temporal boundary:** "I cannot take this on this quarter, but ask me again in Q3." + +The key is specificity. Vague resistance ("I'm pretty busy") invites negotiation. A clear, named reason closes the loop gracefully. + +### Attention as Muscle + +Daniel Goleman frames attention as the foundation of emotional, organisational, and strategic intelligence -- and argues that it can be strengthened through deliberate practice. + +Three dimensions of attention matter for leaders: + +1. **Self-focus** -- Monitoring internal signals, maintaining self-control, and sustaining coherent self-awareness across time. +2. **Other-focus** -- Reading people's perspectives, sensing what they need, and building relationships that function under pressure. +3. **World-focus** -- Listening broadly, connecting disparate information, and imagining how today's decisions play out at longer time horizons. + +The constant onslaught of incoming data -- email, messages, notifications, headlines -- attacks all three. Goleman's prescription is not willpower but structure: controlled environments, technology boundaries, and scheduled reflection time. + +### Productivity Versus Busyness + +Adam Waytz's research on overwork cultures identifies a pernicious dynamic: organisations that reward visible effort over measurable output create employees who optimise for the appearance of work. Leaders dismantle this by rewarding output, promoting based on results, fostering deep work by eliminating low-value tasks, and modelling the behaviour themselves -- including visibly signing off when meaningful work is done. + +### Data That Lands + +When a meeting requires data to drive a decision, presentation quality determines whether the data is heard or ignored. + +Nancy Duarte recommends making numbers relatable through concrete analogies: a time span compared to a familiar flight, a size compared to a local landmark. Joel Schwartzberg adds precision: label chart elements exactly, avoid abbreviations, replace generic titles with takeaway titles ("Millennials Prefer Mobile" rather than "Millennial Preferences"), and highlight the aha zones with visual emphasis and verbal callouts. + +--- + +## Prompts + +**Prompt 1 -- Calendar Autopsy:** +> Here is a summary of how I spent my time last week: [describe or paste calendar entries]. Categorise each entry as (a) deep strategic work, (b) meeting I led, (c) meeting I attended, (d) reactive/administrative, (e) other. Calculate percentages. Identify the three lowest-value time blocks and recommend what to eliminate, delegate, or restructure. Propose a revised calendar template that increases deep work to at least 25% of the week. + +**Prompt 2 -- Meeting Redesign:** +> I run a recurring [frequency] team meeting that currently lasts [duration] and covers [topics]. Attendance is [number] people. Redesign it using question-based agendas, explicit decision-making rules, and a hybrid-friendly format. Include a template agenda, ground rules, and guidance on reducing the meeting by at least 25%. + +**Prompt 3 -- Strategic No:** +> I have been asked to [describe the request]. My current priorities are [list top 3 priorities]. Draft three versions of a polite, clear decline: one for a peer, one for a senior leader, and one for a direct report. Each should redirect the request constructively without ambiguity. + +**Prompt 4 -- Data Presentation Overhaul:** +> I have the following data to present: [describe data, audience, and context]. Restructure the presentation so that: (a) each slide has a takeaway title, (b) key numbers are contextualised with concrete analogies, (c) aha zones are highlighted visually, and (d) the total presentation is under [target duration]. Draft the slide-by-slide outline. + +--- + +## Use Cases + +**Early-traction founder drowning in meetings** + +A founder of a 20-person startup spends 35 of 45 working hours per week in meetings. A calendar autopsy reveals that 40% of those meetings are status updates that could be replaced by asynchronous Slack summaries, and another 20% are one-on-ones that lack structure and routinely run over. The intervention: status meetings become written updates; one-on-ones are capped at 25 minutes with a standing agenda; and two mornings per week are declared meeting-free. Within a month, the founder reports having time to think about strategy for the first time in six months. + +**Growth-stage VP who cannot say no** + +A vice president at a 200-person company has accepted every cross-functional committee invitation, every mentorship request, and every "quick coffee" for two years. Her direct reports are underperforming because she has no time to coach them. With practised scripts, she declines three recurring committee roles (redirecting to capable direct reports), consolidates mentorship into a monthly group session, and reclaims seven hours per week. Her team's quarterly metrics improve within one cycle. + +**Scale-stage leader whose data presentations fail** + +A director presents quarterly business reviews to the executive team, but decisions are consistently deferred. Analysis reveals the problem: slides are dense with data, titles are generic, and no visual hierarchy guides the eye to the key findings. A redesign using takeaway titles, contextual analogies, and highlighted aha zones transforms a 45-minute data dump into a 20-minute decision-ready briefing. + +--- + +## Anti-Patterns + +**1. Protecting deep-work time but filling it with low-value work.** Blocking two hours for "strategic thinking" and then spending it reorganising a spreadsheet is a scheduling victory and a priority defeat. Deep-work blocks require advance clarity on what will be accomplished. + +**2. Saying no to everything.** The overcorrection from chronic overcommitment is hermit-like isolation. Leaders who decline every request erode social capital and lose access to information. The goal is selective engagement, not withdrawal. + +**3. Optimising meetings without questioning their existence.** Making a meeting 20% shorter is useful; asking whether the meeting should exist at all is transformative. The best meeting hygiene is the meeting that never happens because its purpose is served by a written summary. + +**4. Treating busyness as a personal failing rather than a systemic one.** Individual time-management techniques cannot overcome an organisational culture that rewards visible effort over output. If the system incentivises busyness, fixing the individual is treating the symptom. + +**5. Buying back time without investing it.** Outsourcing chores, hiring an assistant, or automating routine tasks creates capacity. If that capacity is immediately consumed by more meetings and more email, the investment yields no return. Freed time must be deliberately allocated to high-value work. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder's personal time allocation | Every hour has outsized impact; discipline here compounds dramatically | +| Early Traction | Meeting culture, first scheduling norms | The habits set in a 15-person company become the culture of a 150-person company | +| Growth | Calendar delegation, manager enablement | Leaders must teach others to manage their own focus, not just manage their own | +| Scale | Organisational time architecture, meeting audits | Time management becomes a systems problem requiring policy-level intervention | + +At validation, the founder's calendar is the company's strategy. A founder who spends 80% of the week on sales has a sales-driven company. A founder who spends 80% on product has a product-driven company. Whether either is correct depends on context, but the allocation should be deliberate, not accidental. + +At scale, individual time-management skills are necessary but insufficient. The organisation needs institutional interventions: meeting-free days across the company, default 25-minute meeting slots, mandatory agenda requirements, and quarterly meeting audits that identify and eliminate recurring meetings whose purpose has expired. + +--- + +## Output Template + +```markdown +# Calendar Audit Report -- [Name / Team] + +**Period:** [Week of Date] +**Total working hours:** [N] + +## Time Allocation + +| Category | Hours | Percentage | Assessment | +|----------|-------|------------|------------| +| Deep strategic work | [N] | [%] | [Target: >25%] | +| Meetings led | [N] | [%] | [Note] | +| Meetings attended | [N] | [%] | [Note] | +| Reactive/administrative | [N] | [%] | [Target: <20%] | +| Other | [N] | [%] | [Note] | + +## Three Lowest-Value Time Blocks +1. [Description] -- [Recommendation: eliminate / delegate / restructure] +2. [Description] -- [Recommendation] +3. [Description] -- [Recommendation] + +## Proposed Weekly Template + +| Time | Mon | Tue | Wed | Thu | Fri | +|------|-----|-----|-----|-----|-----| +| 8-10 | [Block type] | | | | | +| 10-12 | | | | | | +| 12-1 | | | | | | +| 1-3 | | | | | | +| 3-5 | | | | | | + +## Meeting Hygiene Checklist +- [ ] Every recurring meeting has a question-based agenda +- [ ] Decision-making process stated at the start of each meeting +- [ ] Default meeting duration is 25 minutes, not 30 or 60 +- [ ] At least two meeting-free blocks per week protected +- [ ] Quarterly meeting audit scheduled + +## Commitments to Decline +- [Commitment] -- [Redirect plan] +- [Commitment] -- [Redirect plan] +``` + +--- + +## Related Skills + +- **[Eisenhower Matrix](../frameworks/eisenhower-matrix.md)** -- The theoretical framework for urgent-versus-important prioritisation; this skill provides the daily execution layer. +- **[Flow State](../frameworks/flow-state.md)** -- Deep work is the scheduling precondition for flow; without protected time, flow states cannot occur. +- **[Covey's Seven Habits](../frameworks/covey-seven-habits.md)** -- "Put first things first" is the Covey habit most directly addressed by calendar audits and meeting hygiene. +- **[Leader Resilience and Wellbeing](leader-resilience-and-wellbeing.md)** -- Poor time management is a primary driver of leader burnout; protecting focus protects health. +- **[Delegation and Empowerment](delegation-and-empowerment.md)** -- Reclaiming calendar time requires delegating tasks that do not need the leader's personal involvement; the delegation audit directly feeds the calendar autopsy. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- The Stoic dichotomy of control provides the philosophical discipline for releasing low-value commitments that consume focus without advancing priorities. diff --git a/plugins/foreman/content/skills/leadership/humility-and-power.md b/plugins/foreman/content/skills/leadership/humility-and-power.md new file mode 100644 index 0000000..55ed43d --- /dev/null +++ b/plugins/foreman/content/skills/leadership/humility-and-power.md @@ -0,0 +1,206 @@ +--- +name: "humility-and-power" +description: "Addresses the corrosive effects of power on leadership and prescribes humility as the primary antidote. Covers staying humble as authority grows, recognising the early signs of ego distortion, creating channels for honest feedback, acknowledging weaknesses as a strength, and maintaining genuine connection with the people one leads. Use when sensing disconnection from the team, receiving less bad news than seems realistic, noticing sycophantic behaviour in direct reports, struggling with ego after a promotion, or seeking to prevent the corruption that accompanies institutional power." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - humility + - power + - ego + - self-awareness + - vulnerability + - inclusive-leadership + - feedback + - corruption +related_skills: + - emotional-intelligence + - trust-equation + - psychological-safety + - emotional-courage + - purpose-driven-leadership +author: "Fatih Guner" +--- + +# Humility and Power + +The moment you stop hearing bad news is the moment you should worry most. Not because bad news has ceased to exist, but because the people around you have decided it is safer to hide it than to share it. This is the signature symptom of power's corruption -- not the dramatic villainy of corporate scandal, but the quiet, incremental insulation that turns a connected leader into an isolated one. Power does not corrupt through a single moral failure. It corrupts through a thousand small adjustments: people laugh at jokes that are not funny, agree with ideas that are not sound, and withhold objections that need voicing. The leader, bathed in this artificial warmth, mistakes compliance for alignment and silence for agreement. Humility is the only reliable antidote, and it must be practised with the same discipline as any other leadership competency -- because power never stops working against it. + +--- + +## The Framework + +### The Corruption Mechanism + +Power corrupts not through malice but through distortion. As a leader's authority grows, three things happen simultaneously: + +**First, attention narrows.** Research consistently demonstrates that people at the top become less attentive to those below them. This is not callousness; it is cognitive economics. Power shifts the brain's attention toward goals and away from the people affected by those goals. The leader who does not deliberately counteract this drift will "not see" the people they lead -- and those people will know it. + +**Second, feedback filters tighten.** Subordinates calibrate their honesty to the perceived safety of the environment. The more powerful the leader, the more subordinates manage information upward -- softening bad news, inflating good news, and withholding dissent. The leader receives an increasingly curated version of reality, and the gap between this version and actual reality widens with every rung of authority. + +**Third, ego inflates.** Promotions, titles, and organisational deference create a feedback loop. People listen more attentively, agree more readily, and laugh more frequently. This feels like validation. It is, in fact, distortion. The ego, mistaking sycophancy for substance, grows to fill the space that power creates. Breaking free of this dynamic requires selflessness, reflection, and courage -- and the awareness that the dynamic is operating at all. + +### The Humility Practice + +Humility is not self-deprecation. It is the accurate assessment of one's abilities, limitations, and impact on others. For leaders with power, humility must be practised deliberately because power's natural current flows against it. + +**Practice 1: Make "I don't know" acceptable -- starting with yourself.** + +Admitting ignorance is the highest-leverage humility behaviour. It accomplishes three things simultaneously: it builds trust (people trust those who are honest about their limitations more than those who perform omniscience), it opens the door for others' expertise (subordinates will offer knowledge only when they believe the leader values it), and it models the learning behaviour that organisations need at every level. + +The practice begins at the top. When the leader asks a question they genuinely do not know the answer to, and visibly learns from the response, they signal that knowledge matters more than hierarchy. + +**Practice 2: Create robust channels for unvarnished truth.** + +The default communication channels in most organisations are compromised by power dynamics. Town halls, skip-level meetings, and open-door policies all suffer from the same flaw: they require the less powerful person to initiate honesty with the more powerful one. This is asking the person with the most to lose to take the risk. + +Effective channels reverse the burden: + +| Channel | How It Works | Why It Helps | +|---------|-------------|-------------| +| Anonymous feedback systems | Structured, recurring, with visible leadership response | Removes identity risk from truth-telling | +| "Ask me anything" forums | Leader commits to answering all questions, including uncomfortable ones | Demonstrates willingness to be challenged | +| Reverse mentoring | Junior employees mentor senior leaders on areas of junior expertise | Flattens the power dynamic temporarily | +| External advisory input | Board members, coaches, or peers outside the org hierarchy | Provides perspective uncontaminated by internal power dynamics | +| Structured dissent | Meetings where someone is explicitly assigned to argue the opposing view | Normalises disagreement as a leadership practice | + +**Practice 3: Acknowledge weaknesses as a source of strength.** + +The instinct to project competence at all times is understandable and counterproductive. It is unsustainable -- everyone makes mistakes, and the leader who hides them creates an impossible standard. It is isolating -- people connect with human beings, not with curated images of human beings. And it is strategically foolish -- a leader who cannot name their weaknesses cannot compensate for them. + +The distinction is critical: having weaknesses is not the same as being weak. A leader who says "I am not strong at financial modelling, so I have built a team that is" demonstrates more competence than one who bluffs through a spreadsheet. + +**Practice 4: Stay curious about the people you lead.** + +Power's attention-narrowing effect makes it progressively harder to see individuals as individuals rather than as functions. The antidote is deliberate curiosity: remembering that each person has a context beyond their role, asking questions that are not performance-related, and demonstrating that the leader's interest in their people extends beyond their utility. + +This is not about being "nice." It is about being effective. People who feel seen by their leader contribute more, flag problems earlier, and remain with the organisation longer. People who feel invisible to their leader contribute the contractual minimum and leave at the first opportunity. + +### The Seven Humility Questions + +A self-assessment tool that no leader can answer with perfect accuracy (humility, by definition, resists self-measurement) but that directs attention to the right areas: + +1. Do I seek feedback, even if it is critical? +2. Do I admit when I do not know how to do something? +3. Do I acknowledge when others have more knowledge or skills than I do? +4. Do I take note of others' strengths? +5. Do I compliment others on their strengths? +6. Do I show appreciation for others' contributions? +7. Am I willing to learn from others? + +The value of these questions lies not in the answers but in the practice of asking them regularly, with honesty, and -- critically -- with someone who is willing to disagree with the leader's self-assessment. + +--- + +## Prompts + +**Prompt 1 -- Power Corruption Audit:** +> I hold a leadership position of [describe role and scope of authority]. Help me assess whether power is distorting my leadership. Ask me about the last time I received genuinely bad news from a subordinate, the last time someone disagreed with me in a meeting, and the last time I changed my mind based on input from someone junior. Based on my answers, assess my corruption risk and recommend specific countermeasures. + +**Prompt 2 -- Feedback Channel Design:** +> My organisation has [describe current feedback mechanisms]. I suspect they are not producing honest input because [describe symptoms -- e.g., feedback is uniformly positive, the same issues persist despite "resolution," or senior leaders seem surprised by employee survey results]. Design a set of feedback channels that make it safer for people to tell me what I need to hear rather than what I want to hear. Account for my organisation's size [size], culture [describe], and my own leadership style [describe]. + +**Prompt 3 -- Ego Assessment:** +> I have recently [describe a promotion, success, or expansion of authority]. Help me assess whether my ego is expanding with my power. Ask me diagnostic questions about how I respond to disagreement, how much I talk versus listen in meetings, whether I have noticed changes in how people interact with me, and whether I have sought out any honest external perspective. Then provide a frank assessment and specific ego-management practices. + +**Prompt 4 -- Humility in Practice:** +> I want to model humility more effectively for my team. My current approach includes [describe what you currently do]. Assess whether these behaviours are genuine humility or performative humility, and recommend specific daily practices that would make my humility more authentic and more visible to the people I lead. + +--- + +## Use Cases + +**Early-Traction Founder Transitioning from Peer to Boss** + +A founding team of four engineers has been working as equals for eighteen months. With a seed round closed, the lead founder is now officially CEO and the others are reports. The relationship dynamics shift overnight: the three engineers begin deferring to the CEO in technical discussions where they previously debated as peers. The CEO notices fewer challenges to their architectural decisions and, initially, enjoys the smoother meetings. Then a production incident reveals that two engineers had concerns about the architecture but did not voice them. The CEO institutes a "structured dissent" practice: in every architectural review, one engineer is explicitly assigned to argue against the proposed approach. The practice recovers the intellectual honesty that the power differential had silenced. + +**Growth-Stage VP Receiving Curated Reality** + +A VP of Sales consistently receives optimistic pipeline reports from regional directors. Forecast accuracy has declined for three consecutive quarters, but the VP attributes this to market conditions rather than information distortion. An external coach asks the VP when they last heard a regional director say "this deal is not going to close" -- and the VP cannot recall a single instance. The diagnosis is clear: the VP's authority has created a reporting environment where only good news travels upward. The VP redesigns the pipeline review format to require every director to identify their three most at-risk deals and explain why they might lose them. Initially, the meetings are uncomfortable. Within two quarters, forecast accuracy improves by 25% because the VP is finally operating on reality rather than aspiration. + +**Scale-Stage CEO Managing Ego After IPO** + +A CEO who built a company from a garage to a public offering notices that board meetings have become progressively shorter and more agreeable. Analysts praise the company. Media requests multiply. The CEO begins to assume that the absence of dissent reflects the quality of their decisions rather than the intimidation of their position. A long-tenured board member, one of the few who predates the CEO's success, delivers a private warning: "You used to ask the board for advice. Now you present conclusions." The CEO, to their credit, hears the warning and acts: they engage an executive coach, institute quarterly "reverse mentoring" sessions with junior employees, and restructure board meetings to begin with open questions rather than executive presentations. The quality of board input -- and the quality of decisions -- improves measurably. + +--- + +## Anti-Patterns + +1. **Performing humility without practising it.** Using self-deprecating language in public ("I'm just lucky to work with such a talented team") while privately making unilateral decisions and dismissing input. People detect the gap between humble words and controlling actions with remarkable precision. + +2. **Seeking feedback through channels contaminated by power.** Asking direct reports "Be honest -- how am I doing?" in a one-on-one meeting and interpreting the polite response as genuine feedback. The power dynamic makes honesty in this format nearly impossible. Feedback systems must be designed to mitigate power, not ignore it. + +3. **Treating humility as weakness.** In competitive or high-pressure cultures, humility is sometimes dismissed as indecisiveness or lack of confidence. This conflation is both common and wrong. Humility is the accurate calibration of one's abilities; arrogance is the inaccurate inflation of them. The humble leader makes better decisions because they operate on better information. + +4. **Assuming the ego problem is someone else's.** The CEO who reads about ego corruption and thinks "My leadership team could use this" is exhibiting the very blindness the concept describes. Power's distortion affects everyone who holds it; the belief that one is immune is the first symptom. + +5. **Outsourcing humility to systems.** Installing anonymous feedback tools and 360-degree reviews while personally remaining closed to challenge. Systems are necessary but insufficient; the leader's personal willingness to be changed by what they hear is the irreplaceable ingredient. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Peer-to-boss transition | The founder's power is new and its effects are immediately visible in changed team dynamics. Establishing humility practices before power distortion takes root is both easier and more critical. | +| Growth | Feedback infrastructure | As the organisation grows beyond the founder's personal relationships, humility must be embedded in systems -- feedback channels, meeting structures, decision processes -- rather than depending on the founder's personal warmth. | +| Scale | Institutional humility | The leader's ego management is no longer a personal project; it is a cultural imperative. Power at scale insulates more completely, and the countermeasures must be proportionally robust. | + +The progression follows a consistent pattern: what begins as a personal practice must evolve into an organisational capability. A humble founder can sustain humility through personal discipline at ten employees. At a hundred, they need systems. At a thousand, they need a culture that perpetuates humility independent of any single leader. + +--- + +## Output Template + +```markdown +# Humility and Power Assessment + +## Power Corruption Risk +| Indicator | Signal | Current Status | +|-----------|--------|---------------| +| Bad news frequency | When was the last time a subordinate told me something I didn't want to hear? | [Date and description] | +| Dissent in meetings | When was the last time someone disagreed with me publicly? | [Date and description] | +| Mind changes | When did I last change a decision based on junior input? | [Date and description] | +| Deference increase | Have people become more agreeable over time? | [Assessment] | + +## Feedback Channel Audit +| Channel | Exists? | Produces Honest Input? | Power-Mitigated? | +|---------|---------|----------------------|-----------------| +| Anonymous feedback | [Yes/No] | [Assessment] | [Yes/No] | +| Skip-level meetings | [Yes/No] | [Assessment] | [Yes/No] | +| External advisors | [Yes/No] | [Assessment] | [Yes/No] | +| Structured dissent | [Yes/No] | [Assessment] | [Yes/No] | + +## Ego Health Check (Seven Questions) +| Question | Honest Answer | Evidence | +|----------|--------------|----------| +| Do I seek critical feedback? | [Yes/Somewhat/No] | [Specific example] | +| Do I admit when I don't know? | [Yes/Somewhat/No] | [Specific example] | +| Do I acknowledge others' superior knowledge? | [Yes/Somewhat/No] | [Specific example] | +| Do I notice others' strengths? | [Yes/Somewhat/No] | [Specific example] | +| Do I compliment others' strengths? | [Yes/Somewhat/No] | [Specific example] | +| Do I appreciate others' contributions? | [Yes/Somewhat/No] | [Specific example] | +| Am I willing to learn from anyone? | [Yes/Somewhat/No] | [Specific example] | + +## Humility Action Plan +| Practice | Frequency | First Step | Success Indicator | +|----------|-----------|-----------|-------------------| +| [Practice 1] | [Daily/Weekly/Monthly] | [Specific action] | [How I will know it is working] | +| [Practice 2] | [Frequency] | [Action] | [Indicator] | +| [Practice 3] | [Frequency] | [Action] | [Indicator] | +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness, the core component of emotional intelligence, is the cognitive infrastructure that makes humility possible; without it, a leader cannot accurately assess the gap between self-perception and reality. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Humility directly reduces the self-orientation variable in the trust equation's denominator; a humble leader is, by the formula's logic, a more trustworthy one. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Humility in leadership is the single strongest predictor of psychological safety on a team; when the leader models vulnerability and welcomes challenge, the team follows. +- **[Emotional Courage](emotional-courage.md)** -- Admitting weakness, seeking critical feedback, and confronting one's own ego all require emotional courage; humility without courage is merely awareness without action. +- **[Purpose-Driven Leadership](purpose-driven-leadership.md)** -- Purpose serves as an ego counterweight; leaders anchored in something larger than themselves are less susceptible to power's inflating effects. +- **[Stoic Duty and Service](../stoic/stoic-duty-and-service.md)** -- Marcus Aurelius's practice of power through service rather than authority provides the philosophical foundation for the humility practices described here. diff --git a/plugins/foreman/content/skills/leadership/inclusive-leadership.md b/plugins/foreman/content/skills/leadership/inclusive-leadership.md new file mode 100644 index 0000000..d47e588 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/inclusive-leadership.md @@ -0,0 +1,213 @@ +--- +name: "inclusive-leadership" +description: "Provides daily practices for building genuinely inclusive teams through language audits, bias interruption, equitable hiring, cross-cultural sensitivity, and systemic fairness. Use when team composition lacks diversity, when DEI initiatives face backlash, when women or underrepresented groups stall in advancement, when networking events inadvertently exclude, or when a leader's inclusive intent does not match their observable behaviour." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - inclusion + - diversity + - equity + - bias + - gender + - culture + - hiring + - belonging +related_skills: + - lean-in + - psychological-safety + - emotional-intelligence + - trust-equation + - storytelling-for-leaders + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +# Inclusive Leadership + +Five questions. Answer them honestly, right now, about your last thirty days of leadership: + +1. Whose name did you put forward for a stretch assignment -- and whose name never crossed your mind? +2. Which voices spoke most in your last five meetings, and which were silent? +3. When you last wrote a job description, did anyone outside your demographic review the language? +4. At your most recent informal team event, who left early or did not attend -- and did you notice? +5. When an employee's effort fell short, did your internal attribution differ depending on the person's gender, race, or background? + +If any answer produces discomfort, the discomfort is the data. Inclusive leadership is not a posture one adopts during annual training and then shelves. It is a daily practice -- a set of observable behaviours repeated with enough consistency that they reshape the systems around the leader. The structural barriers facing women, people of colour, and other underrepresented groups are well documented elsewhere (see the companion skill on Sandberg's analysis in `lean-in.md`). This skill concerns itself with what a leader actually does about those barriers between Monday morning and Friday evening. + +--- + +## The Practice + +### Four Freedoms as a Daily Filter + +Laura Morgan Roberts identifies four freedoms that inclusive leaders cultivate: + +- **Authenticity** -- People can be who they are, not who they think the organisation wants them to be. +- **Growth** -- Everyone has equal access to learning, stretch assignments, and sponsorship. +- **Respite** -- People can occasionally fade into the background without being penalised for low visibility. +- **Failure** -- Mistakes are treated as learning events, not career-ending incidents. + +These are not abstract values. They are testable. At the end of each week, a leader can ask: "Did my actions this week expand or contract each of these freedoms for every person on my team?" + +### System-Level Intervention, Not Personal Correction + +DEI initiatives reliably produce backlash when framed as a judgement on individuals. Lily Zheng's research demonstrates that the most effective approach reframes the effort entirely: the target is the system, not the person. A leader diagnoses specific inequities using quantitative and qualitative data -- HR metrics, surveys, focus groups, demographic breakdowns -- and then presents the case for change as a matter of fixing policies, processes, and practices. Nobody is being blamed. Structures are being repaired. + +The practical difference is stark. "You need unconscious-bias training" puts people on the defensive. "Our promotion process produces a 2:1 male-to-female ratio despite an equal applicant pool -- let us examine why" invites collective problem-solving. + +### Closing the Gender Gap: Seven Leverage Points + +Drawing from Ammerman and Groysberg's research, inclusive leaders intervene at every stage of the talent lifecycle: + +| Stage | Action | What It Looks Like in Practice | +|-------|--------|-------------------------------| +| Applicant pool | Remove masculine-coded language from job descriptions | Replace "competitive ninja" with "collaborative software engineer" | +| Hiring | Anonymise resumes, diversify interview panels | Blind first-round screens; ensure no panel is homogeneous | +| Onboarding | Prevent tokenism, build networks proactively | Assign sponsors (not just mentors) to new hires from underrepresented groups | +| Development | Equalise stretch assignments and sponsorship | Track who receives high-visibility projects by demographic quarterly | +| Compensation | Publish salary ranges, audit pay equity annually | List median salaries on job postings; conduct regression-based pay audits | +| Promotion | Base decisions on data, not self-nomination | Women who appear ambitious face backlash; remove reliance on self-advocacy | +| Retention | Reward results, not hours; do not penalise flexibility | Flexible work should not be a career penalty | + +### Bias as Infrastructure + +Herminia Ibarra, Robin Ely, and Deborah Kolb coined the term "second-generation bias" to describe workplace structures that disadvantage women without anyone intending discrimination. The concept is critical because it shifts the question from "Who is biased?" to "Which of our structures produce biased outcomes?" Performance feedback is a prime example: high-performing women routinely receive the message "trim your sharp elbows," while equally assertive men receive no such counsel. The leader's job is not to referee individual feedback conversations but to audit the feedback system itself. + +### Cross-Cultural Nuance + +Erin Meyer's research warns against relying on cultural clichés when leading international teams. Effective cross-cultural leaders seek local counsel, adapt their style, and resist the seductive simplicity of national stereotypes. The daily practice: before applying a leadership behaviour across cultures, consult someone embedded in the target culture about expectations around feedback, decision-making, and trust-building. + +### Inclusive Language as Infrastructure + +Terms like "hacker," "ninja," or "rockstar" in job descriptions deter women, people of colour, people with disabilities, and older candidates. Hamilton, Kohler, Bradley Cox, and Lordan recommend creating a company guide to inclusive language -- crowdsourced, regularly updated, and treated as living infrastructure rather than a one-time memo. + +### Intersectional Attention + +Psychological safety is not distributed equally. Black women face compounded barriers requiring specific interventions: manager training in cultural humility, salary audits focused on the intersection of race and gender, policies examined for hidden bias in coaching and performance management, and safe spaces for experience-sharing. Generic DEI commitments that do not address intersecting identities leave the most marginalised employees unprotected. + +### Inclusive Networking + +Informal events -- happy hours, golf outings, after-work drinks -- often inadvertently exclude. Ruchika Tulshyan's guidance: learn dietary restrictions, avoid centring every event around alcohol, schedule some gatherings during working hours, and track attendance patterns. If certain employees consistently do not show up, the event design is the problem, not the employee. + +--- + +## Prompts + +**Prompt 1 -- Inclusion Audit:** +> Review my team's last quarter: [describe team composition, recent hires, promotions, stretch assignments, meeting participation patterns, and informal event attendance]. Identify where inclusion gaps may exist using the four-freedoms framework (authenticity, growth, respite, failure). For each gap, recommend one structural change I can implement within 30 days. + +**Prompt 2 -- Language Review:** +> Audit the following job description for exclusionary language, masculine-coded terms, unnecessary superlatives, and terms that may deter candidates from underrepresented groups: [paste job description]. Rewrite it using neutral, inclusive alternatives while preserving the role's requirements. + +**Prompt 3 -- Systems Diagnosis:** +> Our organisation has the following demographic data across levels: [provide data]. Using Lily Zheng's systems-focused approach, identify which policies, practices, or structures most likely explain the patterns. Frame the analysis as a systems problem, not a people problem, and draft a one-page case for change suitable for presentation to senior leadership. + +**Prompt 4 -- Cross-Cultural Adaptation:** +> I am leading a team spanning [list countries/cultures]. Using Erin Meyer's framework, identify three areas where my default leadership style may clash with team members' cultural expectations. For each, suggest a specific behavioural adaptation I can practise this week. + +--- + +## Use Cases + +**Growth-stage startup with an all-male leadership team** + +A 60-person fintech startup realises that despite hiring women at the entry level, none have advanced to director roles. The founder audits the promotion process and discovers two structural issues: promotions rely heavily on self-nomination (which research shows disadvantages women) and stretch assignments are distributed informally through a network that skews male. The fix is structural: promotion criteria are codified, stretch assignments are tracked by demographic quarterly, and sponsorship (not just mentorship) is formalised for high-potential women. Within two promotion cycles, three women reach director level. + +**Scale-stage company with DEI backlash** + +A 400-person enterprise launches a diversity initiative that triggers resentment among some employees who feel judged. Leadership reframes the initiative using Zheng's systems approach: the problem is not that employees are biased but that the company's hiring pipeline, feedback mechanisms, and networking norms produce unequal outcomes. Resources previously labelled "diversity programmes" are rebranded as fairness-focused tools available to anyone. Backlash subsides; participation increases. + +**Early-traction remote team with cross-cultural friction** + +A 15-person distributed team spanning four countries experiences recurring miscommunication. The founder attributes it to personality differences until a cross-cultural audit reveals structural mismatches: direct feedback norms appropriate in the Netherlands are perceived as harsh by team members in Japan; consensus-based decision-making expected by the Tokyo office frustrates the Berlin contingent's bias toward speed. The leader implements culture-specific communication protocols and consults local advisors before applying uniform policies. + +--- + +## Anti-Patterns + +**1. Performative inclusion.** Declaring "we value diversity" on the website while every leadership meeting features the same demographic profile is worse than silence. Employees notice the gap between rhetoric and reality faster than leaders expect. + +**2. Diversity as a business case only.** Framing inclusion purely through profit metrics ("diverse teams are 35% more profitable") risks instrumentalising marginalised employees. When the business case weakens, commitment evaporates. Frame the effort around fairness; the business benefits follow. + +**3. Fixing women instead of fixing systems.** Programmes that teach women to "lean in," negotiate harder, or be more assertive locate the problem in the individual rather than in the structures that penalise women for the very behaviours they are being coached to adopt. Always ask: "Is this a training problem or a system problem?" + +**4. One-size-fits-all DEI.** Generic initiatives that do not account for intersectionality -- the compounded disadvantages facing, say, Black women or disabled immigrants -- produce outcomes that benefit the least marginalised members of underrepresented groups while leaving others behind. + +**5. Assuming good intent is sufficient.** Second-generation bias operates without malicious intent. A leader who believes they treat everyone equally may still distribute opportunities unequally. The corrective is measurement, not introspection. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founding team composition | Every early hire sets a precedent; the first five people define who "belongs" | +| Early Traction | Hiring systems, language, job descriptions | Formalise inclusive hiring before informal networks calcify | +| Growth | Promotion pipelines, sponsorship, feedback systems | Middle management becomes the inclusion bottleneck; equip managers | +| Scale | Organisational audits, intersectional data, structural reform | Inclusion becomes a measurement and architecture problem | + +At validation, inclusion is a composition question. The founding team signals to every future hire who is welcome. A homogeneous founding team does not preclude diversity later, but it creates a gravitational pull toward sameness that requires deliberate counterforce. + +At growth, the critical failure point is middle management. Even if senior leadership is committed to inclusion, managers who have never examined their own feedback patterns, assignment decisions, or networking habits become inadvertent gatekeepers. Investing in manager capability -- not just awareness, but measurable behavioural change -- is the highest-leverage intervention at this stage. + +At scale, inclusion becomes an engineering problem. Anonymous escalation channels, pay-equity algorithms, demographic dashboards, and structured decision protocols replace the personal touch that worked in a 20-person company. + +--- + +## Output Template + +```markdown +# Inclusion Audit -- [Team / Department Name] + +**Date:** [Date] +**Auditor:** [Name] +**Team size:** [N] +**Demographic summary:** [High-level composition] + +## Four Freedoms Assessment + +| Freedom | Current State | Evidence | Gap | Action (30-day) | +|---------|--------------|----------|-----|-----------------| +| Authenticity | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Growth | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Respite | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Failure | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | + +## Talent Lifecycle Equity Check + +| Stage | Data | Finding | Structural Fix | +|-------|------|---------|---------------| +| Applicant pool | [Data] | [Finding] | [Fix] | +| Hiring | [Data] | [Finding] | [Fix] | +| Onboarding | [Data] | [Finding] | [Fix] | +| Development | [Data] | [Finding] | [Fix] | +| Compensation | [Data] | [Finding] | [Fix] | +| Promotion | [Data] | [Finding] | [Fix] | +| Retention | [Data] | [Finding] | [Fix] | + +## Language Audit Summary +- Terms flagged: [List] +- Replacements recommended: [List] + +## Priority Actions (Next Quarter) +1. [Action with owner and deadline] +2. [Action with owner and deadline] +3. [Action with owner and deadline] +``` + +--- + +## Related Skills + +- **[Lean In](../frameworks/lean-in.md)** -- Provides the theoretical foundation on structural barriers facing women; this skill translates that theory into daily leadership behaviours. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Inclusion safety is the first of Clark's four stages; without it, none of the practices in this skill take root. +- **[Team Culture and Dynamics](team-culture-and-dynamics.md)** -- Inclusive behaviours are a subset of the broader culture a leader builds; this companion skill addresses the full spectrum of team dynamics. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Empathy and social awareness are the individual competencies that underpin inclusive leadership behaviours. +- **[AI Inclusive Collaboration](../ai-leadership/ai-inclusive-collaboration.md)** -- Applies inclusion principles specifically to AI adoption, ensuring diverse stakeholder perspectives shape technology deployment decisions. +- **[Storytelling for Leaders](storytelling-for-leaders.md)** -- Personal storytelling builds the empathy and cross-group connection that inclusive cultures depend on to bridge demographic divides. diff --git a/plugins/foreman/content/skills/leadership/introvert-leadership.md b/plugins/foreman/content/skills/leadership/introvert-leadership.md new file mode 100644 index 0000000..4df3649 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/introvert-leadership.md @@ -0,0 +1,192 @@ +--- +name: "introvert-leadership" +description: "Reframes introversion as a leadership asset and provides practical strategies for introverted leaders -- managing energy, deploying extroversion selectively, scheduling around social depletion, protecting reflection time, and supporting extroverted team members. Use when an introverted leader feels pressure to perform extroversion, struggles with energy management around high-social-demand periods, or needs to design a leadership style that leverages quiet strengths rather than compensating for perceived deficits." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - introversion + - energy-management + - leadership-style + - self-awareness + - quiet-leadership + - hybrid-work +related_skills: + - emotional-intelligence + - flow-state + - psychological-safety-practice + - mentoring-and-coaching +author: "Fatih Guner" +--- + +# Introvert Leadership + +REFRAME. Introversion is not a leadership handicap. It is an undervalued advantage operating in an environment that systematically rewards its opposite. Research from the University of Scarborough and the University of Minnesota confirms what introverted leaders already suspect: extroverted employees are paid more, promoted faster, and rated more positively by managers. The structural bias is real, measurable, and persistent. But the research also reveals something the bias obscures: the qualities that introversion cultivates -- deep listening, careful deliberation, comfort with sustained focus, resistance to impulsive decision-making -- are precisely the qualities that complex leadership demands. The challenge for introverted leaders is not to become extroverts. It is to stop treating introversion as a condition to be managed and start treating it as a capability to be deployed. + +Justin Zorn and Leigh Marz's research on the cognitive benefits of silence, Michael Porter and Nitin Nohria's findings on how effective CEOs use solitary time, and Erica Dhawan's work on hybrid team dynamics converge on a conclusion that corporate culture is slow to absorb: quiet leadership is not a lesser form of leadership. It is a different form, with its own distinctive strengths -- and its own distinctive requirements for energy management, schedule design, and self-advocacy. + +--- + +## The Framework + +Introvert leadership operates across five strategic domains. Each addresses a specific challenge that introverted leaders face and provides a practical response that leverages introversion rather than compensating for it. + +### Domain 1: The Energy Ledger + +Introversion is fundamentally an energy equation. Social interaction depletes energy that solitude restores. This is not a preference; it is a neurological reality. The practical implication: energy must be managed as deliberately as a budget. + +**The energy audit:** + +1. List the recurring social demands of your role: meetings, client dinners, all-hands presentations, networking events, one-on-ones. +2. For each, rate the energy cost on a 1-5 scale (1 = minimal drain, 5 = requires significant recovery). +3. For each, rate the energy recovery time needed (15 minutes, 1 hour, half a day). +4. Map these against your weekly schedule. + +Most introverted leaders discover that their energy deficit is not caused by one catastrophic drain but by the accumulation of moderate drains without sufficient recovery time between them. The solution is structural, not motivational: schedule recovery time as deliberately as meetings. + +### Domain 2: Selective Extroversion + +The advice to "act like an extrovert" is simultaneously correct and dangerous. Correct because certain leadership moments -- a pitch meeting, a team rally, a client dinner -- require visible energy and social engagement. Dangerous because performing extroversion without strategic management leads to what researchers call an "extroversion hangover" -- a depletion so severe that it impairs performance for hours or days afterward. + +The protocol: + +- **Identify high-extroversion moments in advance.** Review the upcoming week and flag the events that will require you to be "on." +- **Block recovery time before and after.** Not optional. Not aspirational. Calendared. +- **Set a social energy budget for each event.** Decide in advance how long you will be fully engaged (e.g., "I will be present and energetic for 90 minutes at this cocktail reception, then leave") and honour the limit. +- **Never wing it.** Spontaneous extroversion is the most costly kind. Preparation reduces the energy expenditure of social performance by providing structure and predictability. + +The distinction matters: selective extroversion is a strategic deployment. Performative extroversion -- attempting to be "on" continuously -- is unsustainable and unnecessary. + +### Domain 3: The Power of Silence + +Zorn and Marz's research identifies sustained silence as a restorative practice that extends beyond mere introvert self-care. Silence restores the nervous system, sustains energy, and conditions the mind for adaptive, creative thinking. But the silence that matters is not merely the absence of office noise or notification pings. It is the quieting of inner chatter -- the mental reflexes that habitually protect reputation, promote a point of view, or rehearse social interactions. + +Practical applications: + +- **Schedule thinking blocks.** Porter and Nohria's research on CEO time allocation found that the most effective leaders protect significant blocks of solitary time for reflection, preparation, and deep thinking. This is not a luxury; it is a performance driver. +- **Use silence in meetings.** Introverted leaders who pause before responding -- rather than racing to fill conversational gaps -- often find that the pause increases the weight of what they say. Teams learn to anticipate substance from a leader who speaks selectively. +- **Distinguish between withdrawal and recharge.** Colleagues may interpret an introverted leader's need for solitude as disengagement. Proactive communication ("I'm going to spend the next hour thinking through the Q4 plan; I'll share my conclusions at 3 PM") prevents misinterpretation. + +### Domain 4: Recognising Quiet Passion + +Kai Krautter, Anabel Buchner, and Jon Jachimowicz's research exposes a persistent bias: managers assume that visible enthusiasm -- chatting eagerly, displaying excitement, engaging energetically with colleagues -- is a reliable proxy for commitment. Quieter employees who express passion through thoroughness, deep immersion in detail, and extra hours on difficult problems are systematically undervalued. + +For introverted leaders, this bias operates in two directions: + +- **Inward:** recognising that your own commitment may be invisible to those who equate passion with volume, and making deliberate choices about how to signal investment without performing enthusiasm you do not feel. +- **Outward:** recognising the same bias in how you evaluate your team. The engineer who stays late debugging a complex system may be more passionate than the one who talks excitedly about it in the morning standup. Judge by output quality and depth of engagement, not by decibel level. + +### Domain 5: Supporting Extroverts Without Draining Yourself + +Erica Dhawan's research on hybrid work dynamics identifies a reciprocal challenge: just as introverts need solitude, extroverts need social connection -- and in hybrid and remote environments, that connection is harder to find. The introverted leader who creates a team culture optimised exclusively for quiet focus will underserve extroverted team members who derive energy and ideas from interaction. + +The balance: + +- **Hold optional social events** -- hybrid lunches, informal coffee chats, happy hours -- without making them mandatory. Extroverts get the connection they need; introverts retain the choice. +- **Use breakout groups in meetings.** Smaller groups reduce the social energy cost for introverts while giving extroverts the interactive processing they prefer. +- **Meet extroverts regularly** in one-on-one or small-group settings where their need for social processing can be addressed without requiring the introverted leader to perform group-level extroversion. +- **Be transparent about your own needs** without apologising for them. "I do my best thinking alone, and I do my best listening in small groups" is a statement of operational reality, not a confession of inadequacy. + +--- + +## Prompts + +**Prompt 1 -- Energy Ledger:** +> Here is my typical weekly schedule: [list recurring meetings, events, and social obligations with approximate durations]. For each, rate the likely energy cost for an introverted leader (1-5 scale) and the recovery time needed. Then identify the highest-risk days -- where energy drains are clustered without recovery -- and redesign the schedule to create sustainable energy flow. I can change approximately [X%] of my schedule. + +**Prompt 2 -- Selective Extroversion Plan:** +> I have these high-extroversion events coming up: [list events with dates and descriptions]. For each, help me plan: how long I should commit to being "on," what preparation would reduce energy cost, what recovery time to block, and what my exit strategy should be. Also suggest one way I can contribute to each event that plays to introvert strengths rather than requiring extrovert performance. + +**Prompt 3 -- Quiet Passion Visibility:** +> I am an introverted leader and I suspect my commitment is not visible to my [board / CEO / peers]. Here is how I currently demonstrate investment in my work: [describe]. Suggest five ways I can make my engagement more visible without performing enthusiasm I do not feel. Each suggestion should be authentic to an introvert's working style. + +**Prompt 4 -- Team Energy Balance:** +> My team includes both introverts and extroverts, and we work in a [hybrid / remote / in-office] arrangement. Here is our current meeting and communication structure: [describe]. Evaluate whether this structure systematically advantages one working style over the other, and recommend changes that serve both without requiring either group to suppress their natural energy patterns. + +--- + +## Use Cases + +**Validation-Stage Founder Preparing for Investor Pitches** +An introverted technical founder faces a month of investor meetings -- back-to-back conversations requiring charisma, quick verbal responses, and sustained social energy. The selective extroversion protocol is applied: pitch meetings are clustered into two days per week with recovery days between, preparation includes rehearsed responses to the twenty most likely questions (reducing cognitive load during performance), and each pitch day ends with a two-hour solitary block. The founder also restructures the pitch itself to leverage introvert strengths: deep technical demonstration rather than performative enthusiasm, and prepared questions that shift the conversation toward dialogue rather than monologue. Investors respond to the depth and substance. Three term sheets result. + +**Growth-Stage VP Managing a High-Extroversion Leadership Team** +A VP of Product -- deeply introverted -- leads a team of six directors, five of whom are extroverts. Team meetings feel exhausting because the conversational style is rapid, overlapping, and energy-intensive. The VP restructures: meetings begin with five minutes of silent written reflection (each person writes their key points before discussion begins), followed by structured discussion where each person speaks in turn. The format gives the VP processing time, gives extroverts the social interaction they need, and produces better outcomes because ideas are considered before they are debated. The introverted VP also schedules one-on-ones with each director at a lower social intensity than group settings, reserving group energy expenditure for situations where collective discussion is genuinely necessary. + +**Scale-Stage CEO Protecting Thinking Time** +A CEO of a 600-person company finds that every hour of every day is filled with meetings. The energy ledger reveals that the schedule is designed for an extrovert: back-to-back social interactions from 8 AM to 6 PM, with "thinking" relegated to evenings and weekends. The redesign: two mornings per week are blocked as "CEO deep work" -- no meetings, no calls, no Slack. The initial resistance from the executive team ("the CEO is unavailable") subsides when the quality of the CEO's strategic contributions improves noticeably. One executive observes: "You used to be reactive in our meetings. Now you come prepared with something we hadn't considered." The preparation happened during the quiet mornings that introversion required and the schedule had previously denied. + +--- + +## Anti-Patterns + +1. **The Apology Stance.** Treating introversion as something to apologise for or explain away. "Sorry, I'm just an introvert" positions a neurological trait as a deficiency. "I do my best work with time to think" positions the same trait as a professional operating principle. + +2. **Complete Withdrawal.** Using introversion as justification for avoiding all social leadership responsibilities. Team connection, stakeholder management, and visible presence are genuine leadership requirements. The task is not to avoid them but to manage energy around them strategically. + +3. **Forcing Extroversion on the Team.** Introverted leaders who overcompensate by creating an exclusively extroverted team culture -- mandatory social events, open-plan offices, constant collaboration -- in an attempt to prove they are not "too quiet." This penalises other introverts and creates the very environment the leader finds draining. + +4. **Ignoring Extrovert Needs.** The mirror anti-pattern: designing all communication and collaboration for quiet, asynchronous, written interaction without providing the social interaction that extroverted team members require to do their best work. Introvert-optimised is not team-optimised. + +5. **Conflating Introversion with Social Anxiety.** Introversion is an energy pattern. Social anxiety is a clinical condition. The former requires energy management. The latter may require professional support. Treating anxiety as "just being introverted" delays intervention; treating introversion as anxiety pathologises a healthy variation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Leveraging depth over breadth | The introverted founder's advantage is the ability to think deeply about a problem before others have finished brainstorming. The risk is isolation -- failing to test ideas with enough external perspectives because solitary thinking feels productive. | +| Validation | Managing pitch energy | Customer discovery and investor conversations are socially intensive. The selective extroversion protocol is critical here. Preparation and recovery scheduling are non-negotiable. | +| Early Traction | Establishing leadership presence | As the team grows beyond the founder's immediate circle, the introverted leader must make their presence felt without performing extroversion. Written communication, structured one-on-ones, and visible preparation become the primary leadership channels. | +| Growth | Designing for both styles | The organisation is large enough to include significant numbers of both introverts and extroverts. The leader's task is to design meeting structures, communication norms, and collaboration tools that serve both energy patterns. | +| Scale | Protecting institutional quiet | At scale, organisational culture tends toward noise -- more meetings, more Slack channels, more "alignment sessions." The introverted leader's contribution is advocating for and protecting the conditions under which deep thinking happens: solitary time, focused work blocks, and the organisational permission to be unavailable. | + +--- + +## Output Template + +```markdown +# Introvert Leadership Strategy: [Leader Name / Role] + +## Energy Ledger +| Activity | Frequency | Energy Cost (1-5) | Recovery Needed | Currently Scheduled? | +|----------|-----------|-------------------|-----------------|---------------------| +| [activity] | [daily/weekly/monthly] | [1-5] | [time] | [yes/no] | + +## High-Risk Days +- [Day]: [why energy drain exceeds recovery capacity] +- Proposed adjustment: [specific schedule change] + +## Selective Extroversion Plan +| Event | Duration "On" | Preparation | Recovery Block | Exit Strategy | +|-------|--------------|-------------|----------------|---------------| +| [event] | [minutes] | [what to prepare] | [when/how long] | [how to leave gracefully] | + +## Quiet Strengths Deployment +- Meetings: [how introvert strengths will be applied] +- Written communication: [how depth and clarity will substitute for volume] +- One-on-ones: [how small-group interaction will be prioritised] + +## Team Balance Check +- Introvert needs addressed: [specific structures] +- Extrovert needs addressed: [specific structures] +- Hybrid/remote adjustments: [specific accommodations] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness -- understanding one's own energy patterns and their impact on leadership behaviour -- is the foundation of introvert leadership strategy. +- **[Flow State](../frameworks/flow-state.md)** -- Csikszentmihalyi's flow research explains why introverts often produce their best work in solitary, deeply focused conditions; protecting the conditions for flow is a strategic priority. +- **[Psychological Safety in Practice](psychological-safety-practice.md)** -- Introverted leaders who model thoughtful silence and deep listening often build stronger psychological safety than extroverted leaders who fill every conversational space. +- **[Mentoring and Coaching](mentoring-and-coaching.md)** -- Introverted leaders frequently excel in one-on-one mentoring relationships, where depth of attention and listening quality matter more than social energy. +- **[Focus and Priority Management](focus-and-priority-management.md)** -- The scheduling techniques for protecting deep work blocks are essential infrastructure for introverts who need solitary time to function at peak capacity. +- **[Myers-Briggs Type Indicator](../frameworks/myers-briggs-type-indicator.md)** -- Provides the personality framework that contextualises introversion-extroversion within a broader typology useful for understanding team energy dynamics. diff --git a/plugins/foreman/content/skills/leadership/leader-resilience-and-wellbeing.md b/plugins/foreman/content/skills/leadership/leader-resilience-and-wellbeing.md new file mode 100644 index 0000000..258fef6 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/leader-resilience-and-wellbeing.md @@ -0,0 +1,217 @@ +--- +name: "leader-resilience-and-wellbeing" +description: "Addresses the physical, emotional, and psychological dimensions of leader sustainability, including sleep, stress management, mindfulness, anxiety channelling, emotional courage, vulnerability, and recovery practices. Use when a leader shows signs of burnout, when sleep deprivation affects judgement and team morale, when overwhelm becomes chronic rather than episodic, when a leader confuses endurance with strength, or when the pressure to appear invulnerable is eroding authentic connection with the team." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - resilience + - wellbeing + - sleep + - stress + - mindfulness + - anxiety + - vulnerability + - courage + - burnout + - self-care +related_skills: + - emotional-intelligence + - psychological-safety + - flow-state + - focus-and-priority-management + - learning-agility +author: "Fatih Guner" +--- + +# Leader Resilience and Wellbeing + +Here is a paradox worth sitting with: the leaders who appear most unbreakable are frequently the most fragile. They have optimised for the projection of strength -- the 5 a.m. starts, the unanswered personal calls, the performative stoic -- while systematically depleting the resources that make genuine strength possible. Sleep, recovery, emotional honesty, and the courage to say "I do not know" are not indulgences that leaders earn after they succeed. They are the infrastructure on which sustainable leadership is built. Neglect them long enough, and the collapse -- when it comes -- is rarely graceful. + +Christopher Barnes's research at Indiana University and the University of Washington delivers the data point that should end every macho leadership cliche about sleep deprivation: employees of sleep-deprived leaders are less engaged and behave less ethically. The leader's fatigue is not a personal sacrifice nobly borne. It is an organisational cost distributed across every person they lead. + +--- + +## The Practice + +### Sleep as Leadership Infrastructure + +Barnes is precise about the mechanism. Sleep deprivation impairs judgement, self-control, and creativity. It increases impatience, irritability, and antagonism. And leaders are reliably oblivious to these effects in themselves -- a phenomenon known as the "sleep debt blind spot." The person least qualified to assess whether they are too tired to lead is the tired leader. + +Three actionable sleep protocols: + +**1. Eliminate sleep-deprivation signalling.** Avoid bragging about how little you slept. Do not send emails at 3 a.m. (use delayed delivery). Do not hold up all-nighters as exemplary. Your team reads your behaviour as a cue for what is expected. + +**2. Protect bad-sleep days.** When sleep was poor, shift the day's work toward routine tasks that do not require creativity. Avoid complex decisions. Ask a colleague to review important documents. A 20-minute nap -- research from the University of Dusseldorf shows even eight minutes improves memory -- can partially restore cognitive function. + +**3. Treat sleep as a strategic investment, not a personal luxury.** The leader who sleeps seven hours and makes one clear-headed decision is more valuable than the leader who sleeps four hours and makes three impaired ones. + +### Managing Overwhelm + +Alice Boyes identifies five strategies for the leader whose to-do list has become a source of chronic anxiety: + +- **Practice acceptance.** Compassionate self-talk: "I can only focus on the thing I am doing right now" or "I would prefer to do more in a day, but I will accept my realistic limits." +- **Question expectations.** Leaders often invent urgency. Before treating a request as immediate, ask: "When do you actually need this?" The real deadline may be far more generous than the assumed one. +- **Track time.** A week of honest time-logging reveals where time actually goes versus where it feels like it goes. The data often contradicts the anxiety. +- **Change behaviour first, then feelings.** Ask: "If I were more relaxed about my workload, how would I act?" Then act that way. Behavioural change often precedes emotional change, not the other way around. +- **Identify microstressors.** Rob Cross and Karen Dillon's research on microstress reveals that small, individually trivial setbacks -- a colleague's missed deadline adding 30 minutes to your evening, a process glitch requiring an extra email chain -- accumulate into significant physiological stress responses. The first step is naming them. The second is systematically eliminating the structural ones. + +### Anxiety as Fuel + +Morra Aarons-Mele reframes anxiety not as a weakness to be eliminated but as a signal to be channelled. Anxiety can sharpen threat detection and increase comfort with uncomfortable feelings -- both useful leadership capacities. The practice: + +1. **Notice.** Observe physical manifestations (stomach churning, chest tightness) and emotional ones (feeling overwhelmed or panicked). +2. **Journal.** Track anxiety patterns over time to identify recurring triggers and distinguish productive anxiety (this situation requires my attention) from destructive anxiety (this rumination is consuming energy with no output). +3. **Pause, then choose.** The gap between noticing anxiety and acting on it is where leadership happens. In that gap, the leader decides whether to be driven by the anxiety or to use it as information. + +### Rumination: Breaking the Loop + +Alice Boyes addresses the specific trap of post-mistake rumination -- replaying errors for days or weeks: + +- Identify rumination triggers: certain people, projects, or decision types that provoke overthinking. +- Relabel: "I feel inadequate" rather than "I am inadequate" creates distance between self and emotional reaction. +- Distract deliberately: a walk, meditation, or even a mundane task can interrupt the cognitive loop. + +### Mindfulness as Structure, Not Sentiment + +Matthias Birk's guidance strips mindfulness of its mystique. Schedule it at a non-negotiable time. Block it on the calendar. Tell the team, so interruptions are minimised. Join a group for accountability. The barriers to mindfulness are almost never philosophical; they are logistical. + +### Emotional Courage + +Peter Bregman defines emotional courage as the capacity to do uncomfortable things -- raising a difficult issue, delivering unwanted feedback, admitting uncertainty. The development method is progressive exposure, starting in low-stakes environments. Practise being direct with a customer-service representative about a billing error. Notice the impulse to retreat or escalate. Resist it. Build the muscle incrementally until directness in high-stakes leadership conversations feels, if not comfortable, at least familiar. + +Maya Angelou's formulation is instructive: "One isn't born with courage. One develops it by doing small courageous things." The five-pound bag of rice before the hundred-pound bag. + +### Vulnerability as Strength + +Peter Bregman's complementary insight: the best managers acknowledge their weaknesses openly. The instinct to show only one's best self is understandable and counterproductive. Employees connect with leaders who are human, not with leaders who are performing invulnerability. "You aren't weak; you have weaknesses. There is a difference." + +James Detert's research adds nuance: taking a stand within an organisation does not require martyrdom. Respected insiders who act on conviction -- pushing for strategic risks, challenging unfair policies, speaking against unethical behaviour -- often see their status rise when they manage the process well. Courage is not the absence of career risk; it is the calculation that some risks are worth taking. + +### Hobbies and the Hedonistic Treadmill + +Research from Vrije Universiteit Amsterdam shows that top leaders who invest substantially in hobbies, personal interests, and volunteer commitments are not escaping work -- they are building the psychological resources that make sustained work possible. Hobbies provide lessons in humility (the CEO who is a beginner at pottery), strengthen authentic identity (the person exists beyond the title), and create the cognitive detachment that prevents work from becoming all-consuming. + +Ron Carucci warns against the hedonistic treadmill: the cycle of pursuing success for the dopamine hit, watching it fade, and pursuing more. The antidote is not less ambition but a deliberate pursuit of meaningful satisfaction alongside achievement. + +### Life Beyond the Role + +David Lancefield's warning is stark: a leadership role will consume your entire life if you allow it. By the time you notice that personal relationships have atrophied and self-care has vanished, recovery is expensive. The preventive measure is simple, difficult, and non-negotiable: decide what matters outside of work and protect it with the same ferocity you protect your most important business commitments. + +--- + +## Prompts + +**Prompt 1 -- Resilience Audit:** +> Assess my current resilience across these dimensions based on the following self-report: sleep pattern [describe], exercise frequency [describe], relationship with anxiety [describe], hobby/non-work investment [describe], vulnerability comfort level [describe], last vacation [date]. For each dimension, rate me as thriving/managing/depleting and recommend one specific change I can implement this week. + +**Prompt 2 -- Microstress Mapping:** +> Here are the small, recurring frustrations in my work week: [list 5-10 microstressors]. Categorise each as structural (fixable by changing a process), relational (fixable by a conversation), or inherent (must be managed, not eliminated). For the structural ones, propose a specific fix. For the relational ones, draft the conversation. For the inherent ones, suggest a coping strategy. + +**Prompt 3 -- Anxiety Channel Plan:** +> I experience significant anxiety about [describe situation or pattern]. Using Aarons-Mele's framework, help me: (a) identify whether this anxiety is productive (contains useful information) or destructive (consuming energy without output), (b) design a journaling protocol to track its patterns, and (c) develop a pause-and-choose routine I can deploy when the anxiety peaks. + +**Prompt 4 -- Vulnerability Script:** +> I need to acknowledge a mistake or limitation to my team: [describe the situation]. Draft what I should say that: (a) is honest without being self-flagellating, (b) maintains authority while demonstrating humanity, (c) models the vulnerability I want the team to practise, and (d) focuses forward on what changes as a result. + +--- + +## Use Cases + +**Validation-stage founder running on fumes** + +A solo founder has averaged five hours of sleep for three months, fuelled by the conviction that every waking hour invested now will pay off later. Investor meetings are going poorly -- the founder is irritable, unfocused, and unable to think creatively during Q&A. A mentor points to Barnes's research: the sleep deficit is not just a personal health issue; it is the reason the pitches are failing. The founder implements a non-negotiable seven-hour sleep minimum, shifts investor meetings to mornings (peak cognitive performance), and within two weeks reports that preparation time has halved because the work product is clearer on the first attempt. + +**Growth-stage leader hiding behind invulnerability** + +A VP of product has never once admitted uncertainty to the team. They interpret every setback as a personal failure, ruminate for days after mistakes, and have developed a reputation for emotional unavailability. A coaching engagement introduces Bregman's progressive exposure method: the VP practises directness in low-stakes situations (returning a faulty product, asking for a table change at a restaurant) and gradually builds toward admitting, in a team meeting, "I made a wrong call on the Q2 roadmap, and here is what I learned from it." The team's response -- relief, increased trust, and a measurable uptick in their own candour -- surprises the VP. + +**Scale-stage executive approaching burnout** + +A chief revenue officer has not taken a vacation in 18 months, exercises sporadically, and has replaced hobbies with "networking dinners." A microstress audit reveals 14 recurring small stressors, eight of which are structural (fixable by process changes or delegation). Eliminating those eight recovers roughly six hours per week. The recovered time is deliberately allocated: three hours to exercise, two to a pottery class (the COO had been a ceramicist before the career consumed everything), and one to an unstructured lunch with no agenda. Within three months, both the executive's engagement scores and their direct reports' engagement scores improve. + +--- + +## Anti-Patterns + +**1. Treating resilience as endurance.** The leader who "pushes through" chronic exhaustion is not resilient; they are depleting a finite resource. Genuine resilience includes knowing when to stop, recover, and return at full capacity. + +**2. Weaponising vulnerability.** Sharing weaknesses to manipulate sympathy, avoid accountability, or create an emotional debt is not vulnerability -- it is manipulation. Authentic vulnerability serves the team's trust, not the leader's emotional needs. + +**3. Mindfulness as performance.** Announcing a meditation practice, attending a retreat, and then returning to exactly the same stress-producing behaviours treats mindfulness as a credential rather than a practice. The measure of mindfulness is changed behaviour, not accumulated hours of sitting. + +**4. The "I'll rest when I succeed" fallacy.** Success does not produce rest; it produces new demands. The leader who defers recovery until after the next milestone, the next funding round, the next quarter will never rest, because there is always another next. + +**5. Ignoring the team cost of personal depletion.** A depleted leader does not suffer alone. Barnes's research is unambiguous: the leader's sleep, stress, and emotional state propagate to the team. Self-care is not selfish; it is a leadership responsibility. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Sleep discipline, founder stamina | Survival instinct overrides recovery; the founder must deliberately counter this | +| Early Traction | Stress management, boundary setting | First employees amplify the founder's habits; bad patterns scale fast | +| Growth | Emotional courage, vulnerability modelling | The leader's emotional range sets the ceiling for the team's psychological safety | +| Scale | Systemic wellbeing, vacation culture, burnout prevention | Resilience becomes an organisational design problem, not just an individual one | + +At validation, the primary threat is the founder's own mythology. The startup ecosystem glorifies sleep deprivation, relentless hustle, and the sacrifice of everything personal. The founder who internalises this mythology burns out before the company reaches product-market fit. The counternarrative -- that rest produces better decisions, which produce better outcomes, which produce faster progress -- is supported by the data but runs against the culture. + +At scale, individual resilience practices are necessary but insufficient. The organisation must build resilience into its architecture: mandatory minimum vacation policies, manager training on burnout recognition, workload audits, and a culture that treats visible rest as a sign of competence rather than a sign of insufficient commitment. + +--- + +## Output Template + +```markdown +# Leader Resilience Assessment -- [Name] + +**Date:** [Date] +**Assessed by:** [Self / Coach / Peer] + +## Dimension Ratings + +| Dimension | Current State | Evidence | Risk Level | One-Week Action | +|-----------|--------------|----------|------------|----------------| +| Sleep | [Thriving/Managing/Depleting] | [Hours, quality, consistency] | [High/Medium/Low] | [Specific change] | +| Physical activity | [Thriving/Managing/Depleting] | [Frequency, type] | [High/Medium/Low] | [Specific change] | +| Stress management | [Thriving/Managing/Depleting] | [Coping methods used] | [High/Medium/Low] | [Specific change] | +| Anxiety relationship | [Thriving/Managing/Depleting] | [Productive vs. destructive ratio] | [High/Medium/Low] | [Specific change] | +| Emotional courage | [Thriving/Managing/Depleting] | [Recent examples] | [High/Medium/Low] | [Specific change] | +| Vulnerability practice | [Thriving/Managing/Depleting] | [Recent examples] | [High/Medium/Low] | [Specific change] | +| Non-work investment | [Thriving/Managing/Depleting] | [Hobbies, relationships, leisure] | [High/Medium/Low] | [Specific change] | + +## Microstress Inventory + +| Stressor | Category | Frequency | Fix / Cope Strategy | +|----------|----------|-----------|-------------------| +| [Stressor] | [Structural/Relational/Inherent] | [Daily/Weekly/Occasional] | [Specific action] | + +## Recovery Plan (Next 30 Days) +- **Sleep:** [Target hours, bedtime routine, screen curfew] +- **Exercise:** [Frequency, type, scheduled times] +- **Mindfulness:** [Method, duration, scheduled time] +- **Non-work:** [Activity, frequency, protected time] +- **Boundary:** [One boundary to set this month] + +## Team Impact Check +- Am I modelling the behaviours I expect from my team? +- What signals am I sending about work-life boundaries? +- When did I last take a visible day off? +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-regulation and self-awareness, core EQ competencies, are the psychological muscles that resilience practices strengthen. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- A leader's willingness to be vulnerable directly builds the team's psychological safety; the two are inseparable. +- **[Flow State](../frameworks/flow-state.md)** -- Flow requires a baseline of cognitive and emotional health; depleted leaders cannot achieve or sustain it. +- **[Focus and Priority Management](focus-and-priority-management.md)** -- Poor time management is both a cause and a symptom of burnout; the two skills reinforce each other. +- **[Emotional Courage](emotional-courage.md)** -- The vulnerability practice described here -- sharing weakness appropriately -- requires the progressive courage-building techniques from this companion skill. +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- Provides the philosophical foundation for endurance that complements the practical sleep, stress, and recovery protocols described here. diff --git a/plugins/foreman/content/skills/leadership/leader-self-reflection.md b/plugins/foreman/content/skills/leadership/leader-self-reflection.md new file mode 100644 index 0000000..00a4694 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/leader-self-reflection.md @@ -0,0 +1,211 @@ +--- +name: "leader-self-reflection" +description: "Establishes a structured introspection practice for leaders through recurring self-diagnostic questions, performance pattern analysis, and emotional impact awareness. Covers seven reflection domains (vision, time, feedback given, feedback received, strengths and weaknesses, authenticity, and pressure behaviour), techniques for joint analysis of failures and successes, and methods for surfacing blind spots that others will not voluntarily reveal. Use when a leader feels stuck in repetitive patterns, when self-awareness gaps are damaging team trust, when preparing for a leadership transition, or when establishing a personal development discipline." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - self-awareness + - introspection + - feedback + - emotional-intelligence + - personal-development + - strengths + - weaknesses + - reflection +related_skills: + - leadership-style-adaptation + - leadership-voice-and-presence + - senior-leadership-transition + - employee-engagement-retention + - johari-window + - emotional-intelligence + - covey-seven-habits +author: "Fatih Guner" +--- + +# Leader Self-Reflection + +A leader who does not reflect does not learn. They accumulate years of experience and repeat the first year twenty times. They confuse tenure with development, pattern recognition with wisdom, and the absence of complaints with the presence of trust. The most dangerous leader in any organisation is not the one who makes mistakes -- everyone does -- but the one who lacks the self-awareness to see them, the humility to examine them, and the discipline to build a practice that prevents their repetition. + +Self-reflection is not meditation, journaling for its own sake, or the vague aspiration to "be more mindful." It is a structured diagnostic process -- a set of specific questions, applied with regularity, that surfaces the gap between how you believe you lead and how you actually do. Peter Drucker, Robert Kaplan, and Daniel Goleman converge on the same conclusion from different angles: the leaders who perform best are those who have built systematic methods for examining their own behaviour, not occasionally during a retreat, but as a recurring discipline woven into the rhythm of work. + +--- + +## The Practice + +### The Seven Reflection Domains + +Each domain addresses a different facet of leadership effectiveness. Neglecting any one of them creates a blind spot that compounds over time. + +**1. Vision Clarity** +*The question: How often and how well do you communicate a vision and priorities for your team?* + +In the turbulence of daily operations, it is easy to stop articulating the bigger picture. But people cannot focus their efforts -- or sustain motivation -- if they do not know where they are going and why. The reflection discipline: at the end of each week, ask whether your team could articulate your three top priorities. If you doubt they could, the problem is not their attention; it is your communication. + +**2. Time Alignment** +*The question: How are you spending your time, and does it align with your stated priorities?* + +Leaders set the pace for their teams. If your calendar does not reflect your priorities, you are signalling -- loudly -- that those priorities are negotiable. The reflection discipline: once per month, audit your calendar against your strategic goals. Identify the activities that consumed time without advancing priorities, and ask: which of these could be delegated, eliminated, or compressed? + +**3. Feedback Given** +*The question: Do you give timely, direct, constructive feedback?* + +Teams want to know how to grow, and they need their leader to tell them. Feedback hoarded until annual reviews arrives too late to change behaviour and too infrequently to demonstrate investment. The reflection discipline: at the end of each week, count the pieces of substantive feedback you delivered. If the number is zero, the week was a missed development opportunity for everyone on your team. + +**4. Feedback Received** +*The question: Do you have people who will tell you things you need to hear?* + +Your team is better positioned than your boss to assess your daily impact. But employees are often scared to deliver hard truths upward -- they fear consequences, doubt their standing, or simply do not know how to raise the topic. You cannot rely on spontaneous honesty. The reflection discipline: make a concerted, persistent effort to ask what you could do better, and then visibly act on what you hear. If no one is telling you anything difficult, you have a trust problem, not a performance one. + +**5. Strengths and Weaknesses** +*The question: Can you write down your two or three greatest strengths and your two or three most significant weaknesses?* + +This exercise sounds elementary. It is not. An honest inventory requires input from people who will deliver unvarnished truth -- not colleagues who will soften the assessment out of politeness or politics. The reflection discipline: annually solicit specific feedback from people at multiple levels and outside your immediate circle. Write the inventory down. Compare it to last year's. Note what has changed and what has stubbornly persisted. + +**6. Authenticity** +*The question: Does your leadership style reflect who you really are?* + +Modelling your style on admired leaders is natural, but ultimately your approach must be uniquely and genuinely yours. The reflection discipline: periodically ask whether the way you lead would feel recognisable to the people who knew you before you had a title. If the answer is no, examine which adaptations serve the role and which serve the performance of a role you are playing rather than inhabiting. + +**7. Pressure Behaviour** +*The question: How do you behave under pressure, and does it align with your values?* + +During a crisis, every eye is on the leader. Calm or harried. Accountable or blaming. Supportive or finger-pointing. The person you are under stress is the person your team remembers. The reflection discipline: after every high-pressure episode, conduct a brief retrospective -- not of what happened, but of how you behaved. Did your actions match your stated values? If not, identify the specific moment where they diverged and the trigger that caused it. + +### Analysing Failures and Successes Together + +The instinct after a failure is to search for root causes and correct them. This is necessary but insufficient. Some patterns that appear in failures also appear in successes -- and correcting them would remove a capability rather than fix a deficiency. + +Before investing in new solutions, tools, or training programmes based on a failure analysis, examine whether the "failing" factor is also present in your successes. If employees who fell short on a project were not using a particular tool, check whether successful employees were using it either. The discipline of paired analysis prevents overcorrection and preserves what works. + +### How You Perform Best + +Self-reflection includes understanding your operating conditions -- the circumstances under which you produce your strongest work. Do you absorb information by reading or listening? Do you learn by writing, talking, watching demonstrations, or hands-on experimentation? Do you prefer solitary concentration or collaborative energy? Do you produce results as a decision-maker or as an advisor to decision-makers? Do you thrive under pressure or require structure? + +These preferences are not fixed. They shift as careers evolve and contexts change. Revisiting them periodically prevents the trap of organising your work around the preferences of the person you were five years ago rather than the person you are now. + +### Your Emotional Impact + +A leader's mood has an outsized effect on team performance. But leaders routinely underestimate their emotional footprint because people do not volunteer the truth about it. They are afraid, or they think it is not their place, or they do not realise that the leader's emotional style is the elephant in the room. + +The reflection discipline: create structured channels for emotional impact feedback. This might be an anonymous pulse survey, a trusted peer who agrees to be candid, or an executive coach. The question is not "Am I a good leader?" but "What effect does my emotional state have on the people around me, and am I aware of it in real time?" + +--- + +## Prompts + +**Prompt 1 -- Seven-Domain Self-Assessment:** +> Guide me through a structured self-reflection across the seven domains (vision clarity, time alignment, feedback given, feedback received, strengths/weaknesses, authenticity, pressure behaviour). For each domain, ask me one diagnostic question, then assess my response for blind spots, self-serving narratives, and areas where I may be overestimating my effectiveness. Provide a candid assessment of which domains need immediate attention and a specific weekly practice for each. + +**Prompt 2 -- Failure-Success Paired Analysis:** +> I recently experienced a failure: [describe the project, outcome, and your initial diagnosis of what went wrong]. I also have a recent success: [describe the project and outcome]. Help me analyse both together. Identify factors present in the failure that are also present in the success. Challenge my initial diagnosis of the failure's root cause. Recommend corrections that address genuine deficiencies without eliminating capabilities that contributed to the success. + +**Prompt 3 -- Emotional Impact Audit:** +> Based on the following observations about how my team responds to me in different situations, assess my emotional impact as a leader. Situation 1: [describe your mood, your behaviour, and the team's response]. Situation 2: [describe]. Situation 3: [describe]. Identify patterns in how my emotional state affects team performance, creativity, and willingness to speak up. Recommend specific awareness practices and behavioural adjustments. + +**Prompt 4 -- Operating Conditions Map:** +> Help me map my optimal operating conditions as a leader. I will describe my preferences and patterns: [describe how you absorb information, whether you prefer solo or collaborative work, how you handle pressure, when you feel most productive, what drains you]. Assess whether my current role and schedule align with these conditions. Identify misalignments that may be reducing my effectiveness and suggest structural changes to my workday. + +--- + +## Use Cases + +**Growth-Stage CEO Who Cannot Understand Why Talented People Leave** +A CEO at an 80-person company has lost three director-level hires in eighteen months. Exit interviews are polite and uninformative. Applying the seven-domain reflection, the CEO discovers the issue in Domain 4 (feedback received): no one on the team tells the CEO hard truths. The CEO's emotional style -- intense, fast-paced, visibly frustrated by mistakes -- has created an environment where upward feedback feels unsafe. The intervention: the CEO hires an executive coach and commits to a weekly practice of explicitly asking one direct report for one piece of critical feedback, then responding with gratitude regardless of content. Over six months, the feedback channel opens. The next director-level hire stays. + +**Early-Traction Founder Repeating the Same Hiring Mistake** +A founder has hired and fired three head-of-sales candidates in two years. Each time, the diagnosis is "wrong person." The paired failure-success analysis reveals a different pattern: the same trait that the founder criticises in failed hires -- autonomous decision-making without seeking approval -- is the trait that makes the founder's successful engineering lead effective. The real issue is not the candidates; it is the founder's inconsistent tolerance for autonomy across functions. Sales requires independent judgment in the field. The founder's reflection leads to a recalibration: either grant the same autonomy to sales that engineering enjoys, or acknowledge that the founder is not ready to let go of that function. + +**Scale-Stage VP Whose Team Performs Well but Feels Miserable** +A VP of Operations delivers consistently strong results. Engagement scores in their division are the lowest in the company. The emotional impact audit reveals the cause: the VP operates with controlled intensity that reads as calm to superiors but as relentless pressure to subordinates. The VP's self-perception ("I am calm and focused") diverges sharply from the team's experience ("We never feel we can relax"). The reflection practice surfaces this gap through structured feedback from trusted peers and an anonymous pulse survey. The VP begins signalling recovery periods explicitly: "We hit the target. This week, we consolidate." + +--- + +## Anti-Patterns + +1. **The Journaling Illusion.** Confusing the act of writing about leadership with the act of examining it. Reflection without specific diagnostic questions produces autobiographical narrative, not insight. The seven domains provide structure that prevents self-reflection from becoming self-narration. + +2. **The Solo Practitioner.** Conducting all reflection internally without external input. Self-assessment without external validation is unreliable because the same blind spots that distort leadership also distort self-perception. The practice requires feedback from others to function. + +3. **The Retrospective Without Change.** Honest self-examination that produces awareness but not behavioural modification. Reflection that does not lead to a specific, trackable change in practice is intellectual exercise, not leadership development. + +4. **The Annual Retreat Approach.** Reserving reflection for offsites, year-end reviews, or vacation periods. The seven domains are weekly practices, not annual events. Patterns that take twelve months to surface take twelve months to correct. + +5. **The Selective Mirror.** Reflecting only on domains where you suspect you are strong, avoiding the domains where discomfort signals genuine deficiency. The domain you least want to examine is almost certainly the one that needs the most attention. + +6. **The Wrong Lesson.** Analysing failures in isolation and implementing corrections that inadvertently eliminate strengths. Paired analysis of failures and successes prevents this overcorrection, but only if conducted with discipline. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder self-awareness | At the earliest stage, the founder's self-knowledge is the organisation's competitive advantage or liability. Reflection focuses on operating conditions (when and how you work best) and authenticity (leading as yourself rather than performing a role you think investors expect). | +| Early Traction | Feedback infrastructure | As the first team forms, the leader must build the channels through which honest feedback flows. This is the moment to establish the norms -- asking for criticism, acting on it visibly -- that determine whether the organisation develops a culture of candour or one of comfortable silence. | +| Growth | Emotional impact at scale | The leader's mood now affects dozens or hundreds of people. Reflection must expand to include emotional impact awareness: how your state ripples through management layers and affects people you may rarely see directly. | +| Scale | Institutional reflection | At scale, self-reflection must be modelled and taught so that every manager practises it. The leader's personal discipline becomes the template for an organisational capability: structured introspection at every level. | + +--- + +## Output Template + +```markdown +# Leader Self-Reflection Assessment + +**Leader:** [Name] +**Date:** [Date] +**Review Period:** [Week/Month/Quarter] + +## Seven-Domain Diagnostic + +| Domain | Self-Assessment | External Feedback | Gap | Priority Action | +|--------|----------------|-------------------|-----|-----------------| +| Vision Clarity | [Assessment] | [Feedback] | [Gap] | [Action] | +| Time Alignment | [Assessment] | [Feedback] | [Gap] | [Action] | +| Feedback Given | [Assessment] | [Feedback] | [Gap] | [Action] | +| Feedback Received | [Assessment] | [Feedback] | [Gap] | [Action] | +| Strengths/Weaknesses | [Assessment] | [Feedback] | [Gap] | [Action] | +| Authenticity | [Assessment] | [Feedback] | [Gap] | [Action] | +| Pressure Behaviour | [Assessment] | [Feedback] | [Gap] | [Action] | + +## Paired Analysis: Recent Failure + Success +- **Failure:** [Description and initial root cause] +- **Success:** [Description] +- **Shared factors:** [Factors present in both] +- **True root cause:** [Revised diagnosis] +- **Corrective action:** [Action that preserves strengths] + +## Emotional Impact Snapshot +- **How I think I come across:** [Self-perception] +- **How others experience me:** [Feedback data] +- **Gap:** [Description] +- **Adjustment:** [Specific behavioural change] + +## Operating Conditions Review +- **Current alignment with optimal conditions:** [High/Medium/Low] +- **Misalignments identified:** [List] +- **Structural changes planned:** [List] + +## Commitments for Next Review Period +1. [Specific, measurable commitment] +2. [Specific, measurable commitment] +3. [Specific, measurable commitment] +``` + +--- + +## Related Skills + +- **[Johari Window](../frameworks/johari-window.md)** -- The theoretical model for understanding the gap between self-knowledge and others' perception; this skill provides the daily practice for expanding the "open" quadrant. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness and self-regulation are the EI competencies that self-reflection directly develops. +- **[Leadership Style Adaptation](leadership-style-adaptation.md)** -- The mirror exercise in style adaptation is a focused application of the broader reflective practice developed here. +- **[Employee Engagement and Retention](employee-engagement-retention.md)** -- The eight retention-destroying behaviours audit requires the honest self-examination that this skill builds as a daily discipline. +- **[Stoic Self-Awareness](../stoic/stoic-self-awareness.md)** -- The Stoic evening review is the philosophical ancestor of the structured reflection domains; both use recurring self-examination to surface patterns invisible in the moment. +- **[Learning from Failure](learning-from-failure.md)** -- The paired failure-success analysis technique depends on the reflective discipline to distinguish genuine root causes from comfortable narratives. diff --git a/plugins/foreman/content/skills/leadership/leadership-style-adaptation.md b/plugins/foreman/content/skills/leadership/leadership-style-adaptation.md new file mode 100644 index 0000000..f9db3a2 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/leadership-style-adaptation.md @@ -0,0 +1,187 @@ +--- +name: "leadership-style-adaptation" +description: "Provides practical self-diagnosis exercises and daily habits for recognising when a leader's default style fails and adapting in real time. Focuses on behavioural flexibility rather than theory -- how to read the room, when to shift approach, and how to stay authentic while flexing. Complements the theoretical models in Lewin Leadership Styles and Situational Leadership with actionable daily practice. Use when a leader's default approach stops working, when team dynamics shift, when coaching managers on flexibility, or when preparing to lead a new team with different needs." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership-style + - adaptability + - self-awareness + - authenticity + - management + - flexibility + - team-dynamics +related_skills: + - leader-self-reflection + - senior-leadership-transition + - leadership-voice-and-presence + - lewin-leadership-styles + - situational-leadership + - emotional-intelligence +author: "Fatih Guner" +--- + +# Leadership Style Adaptation + +Pause here and answer one question: if you asked your team to describe your leadership in three words, what would they say? + +Not what you hope they would say. Not the words from your last 360 review that you carefully internalised. The actual three words that the people who report to you would use when describing you to a friend over dinner. Visionary or micromanager. Supportive or absent. Decisive or impulsive. Calm or detached. + +The gap between how you see yourself and how your team experiences you is where most leadership style failures live. Not in choosing the wrong theoretical model -- the frameworks exist and are well-documented (see Lewin Leadership Styles and Situational Leadership for the theory) -- but in the daily, unglamorous work of noticing when your default approach has stopped serving the people in front of you, and adjusting before the damage compounds. + +--- + +## The Practice + +### Your Default Style: A Self-Diagnosis + +Every leader has a default -- the style they revert to under pressure, in ambiguity, or when they stop paying attention. Goleman's research identifies six styles that produce positive organisational effects when applied correctly: authoritative (visionary), affiliative (harmony-building), democratic (consensus-seeking), coaching (development-focused), and two others that require more careful deployment. The question is not which style is best. It is which style you reach for automatically, and whether that automatic reach matches the moment. + +**The Mirror Exercise** + +Conduct this weekly for one month: + +1. At the end of each day, write down the most consequential interaction you had with your team. +2. Describe what you said and did -- not what you intended. +3. Label the style you used (directive, consultative, supportive, delegative, visionary, coaching). +4. Ask: was that the style this situation needed, or was it the style I am most comfortable with? +5. Note the gap. Over four weeks, patterns will emerge that no personality test can replicate. + +### Six Signals That Your Default Style Is Failing + +Style mismatches do not announce themselves. They manifest as symptoms that leaders misattribute to team problems rather than leadership problems: + +1. **Silence in meetings.** You interpret it as agreement or passivity. Often it means your directive style has trained people that their input does not matter. +2. **Decisions that unravel.** You achieve consensus in the room, but commitments dissolve within days. Your democratic style may be producing performative agreement rather than genuine alignment. +3. **High performers leaving.** Your affiliative style keeps harmony but provides insufficient challenge. Top talent needs to be stretched, not merely supported. +4. **Innovation drought.** Your coaching style develops individuals but your team never takes collective creative risks. Development without vision produces skilled people with no direction. +5. **Burnout clusters.** Your authoritative style drives ambition but the pace you set as a visionary exhausts the team that must execute the vision. +6. **Learned helplessness.** Your directive style has solved problems so effectively that your team has stopped trying to solve them without you. Efficiency today, dependency tomorrow. + +### The Adaptation Habit: Read, Choose, Act, Review + +Adaptation is not instinct; it is a four-step practice that, with repetition, becomes fluid. + +**Read** the situation before entering it. What does this meeting need -- energy, structure, empathy, challenge? What state is your team in -- confident, confused, demoralised, overextended? + +**Choose** a style deliberately. This is the moment where theory becomes practice. The authoritative approach energises a demoralised team with vision. The affiliative approach heals a fractured team through connection. The democratic approach generates ownership for a complex decision. The coaching approach develops a promising but unpolished performer. The choice should serve the team, not your comfort. + +**Act** with commitment. Half-measures in style adaptation are worse than no adaptation at all. If you choose to be consultative, actually consult -- do not ask for input you have already decided to ignore. If you choose to delegate, actually let go -- do not hover with thinly disguised control. + +**Review** within 24 hours. Did the style you chose produce the effect you intended? If not, was the style wrong, or was the execution flawed? Honest review builds the pattern-recognition that eventually makes adaptation feel natural rather than forced. + +### Authenticity and Adaptation Are Not Opposites + +The most common objection to style flexibility: "That is not who I am." This confuses values with behaviours. Authenticity means leading consistently from your core values -- integrity, respect, ambition, whatever anchors your identity. Adaptation means expressing those values through different behaviours depending on what the moment demands. A leader who values respect can express it through direct challenge (when a team member needs growth) or through patience (when a team member needs recovery). The value is constant. The behaviour varies. + +The question to ask: does this adaptation require me to betray my values, or merely to express them differently? If the former, do not adapt. If the latter, the resistance is comfort masquerading as principle. + +--- + +## Prompts + +**Prompt 1 -- Default Style Diagnosis:** +> Based on the following descriptions of how I typically lead in different situations, identify my default leadership style and the situations where it works well versus where it fails. Situation 1: [describe]. Situation 2: [describe]. Situation 3: [describe]. For each situation where my default fails, recommend a specific alternative style and explain what I would do differently in practice -- not in theory but in concrete behavioural terms. + +**Prompt 2 -- Team Style Mapping:** +> I lead a team of [number] people. Here is a brief profile of each: [describe each person's experience level, current performance, and what they seem to need from you]. For each team member, recommend the leadership style that would be most effective right now and explain what that looks like in my daily interactions with them. Then identify where I will face the hardest adaptation -- where my default style and the needed style are furthest apart. + +**Prompt 3 -- Adaptation Scenario Practice:** +> Present me with five leadership scenarios requiring different styles. For each scenario, describe the situation, the people involved, and the outcome at stake. After I respond with my approach for each, assess which style I chose, whether it matched the situation's needs, and what the likely outcome would be. Then provide a corrected approach for any mismatches. + +**Prompt 4 -- Authenticity Boundary Mapping:** +> My core leadership values are [list 3-5 values]. I have been told I need to be more [describe requested change -- e.g., directive, empathetic, hands-off]. Help me distinguish between adaptation that would strengthen my leadership and adaptation that would compromise my values. For each requested change, design a version of that behaviour that remains authentic to my stated values. + +--- + +## Use Cases + +**Growth-Stage CEO Whose Visionary Style Exhausts the Team** +A founder-CEO at a 100-person company has built the business on infectious enthusiasm and bold strategic bets. The authoritative style that attracted early employees now produces burnout among a team that has been sprinting for three years. Exit interviews reveal a pattern: "I love the vision but I cannot sustain the pace." The CEO's adaptation: shifting to an affiliative mode every Friday -- no strategy discussions, no new initiatives, just checking in on people. Adding coaching conversations with the top ten performers, focusing on their development rather than the company's roadmap. The vision remains unchanged; the delivery becomes sustainable. + +**Early-Traction Technical Leader Whose Directive Style Blocks Innovation** +An engineering lead at a 20-person startup solves problems faster than anyone on the team. Their directive efficiency is legendary -- and it has created a team that waits for instructions rather than proposing solutions. The mirror exercise reveals the pattern: in the last twenty consequential interactions, nineteen involved the leader providing the answer. The adaptation: a "questions only" rule for the first ten minutes of every problem-solving session. The leader asks; the team answers. It feels painfully slow for three weeks. In week four, the team ships a feature the leader had not considered. + +**Scale-Stage HR Leader Navigating a Merger** +A CHRO at a 500-person company must integrate a 200-person acquisition. Her default democratic style -- building consensus, soliciting input, honouring all perspectives -- is essential for cultural integration but disastrous for the forty decisions that must be made in the first thirty days. The adaptation: directive for structural decisions (reporting lines, systems, policies) and democratic for cultural decisions (values alignment, team rituals, communication norms). She is transparent about the switch: "For the next month, I will make some decisions unilaterally because speed matters. For the decisions that shape who we are, I will take the time to hear from everyone." + +--- + +## Anti-Patterns + +1. **Style Tourism.** Trying a new style for one meeting, feeling awkward, and concluding it does not work. Adaptation requires sustained practice, not a single experiment. A style tried once is a performance; a style practised for a month is a capability. + +2. **Confusing Adaptation with Inauthenticity.** Using "that is not who I am" as a shield against necessary behavioural change. Authentic leaders adapt constantly; what remains fixed is their values, not their methods. + +3. **One-Size-Fits-All Across the Team.** Leading every team member with the same style because "fairness" demands consistency. Fairness is giving each person what they need to succeed -- which means different styles for different people at different moments. + +4. **Reading the Room but Not Acting.** Leaders who accurately diagnose what a situation needs but cannot bring themselves to deliver it. Diagnosis without action is observation, not leadership. + +5. **Adapting to Avoid Discomfort Rather Than to Serve the Team.** Shifting to an affiliative style not because the team needs warmth but because the leader dreads conflict. The test: does this adaptation serve my comfort or their development? + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder flexibility | Founders must shift styles multiple times per day -- directive with the product, coaching with the first hire, visionary with investors. The range required is extreme, and the margin for error is narrow because every person represents a large fraction of the team. | +| Growth | Manager development | The founder's adaptation skills must now be taught to first-time managers who have never led before. The risk: managers default to the style they experienced from the founder, regardless of whether it suits their team. Explicit style coaching becomes a training priority. | +| Scale | Systemic calibration | At scale, individual style adaptation matters less than the organisation's collective style repertoire. The question shifts from "How should I lead this person?" to "Does our management culture reward style flexibility or punish deviation from a dominant norm?" | + +--- + +## Output Template + +```markdown +# Leadership Style Adaptation Assessment + +**Leader:** [Name] +**Team Size:** [Number] +**Date:** [Date] + +## Default Style Profile +- **Primary default:** [Style name] +- **Under pressure:** [Style name] +- **Evidence:** [Specific behaviours observed] + +## Team Style Map + +| Team Member | Their Need | Optimal Style | Your Default Gap | Adaptation Required | +|-------------|-----------|---------------|-----------------|---------------------| +| [Name] | [Need] | [Style] | [Low/Medium/High] | [Specific change] | + +## Situation-Style Matrix + +| Recurring Situation | Current Approach | Needed Approach | Behaviour Change | +|--------------------|-----------------|-----------------|------------------| +| [e.g., Sprint planning] | [Current] | [Needed] | [Concrete action] | +| [e.g., 1-on-1s] | [Current] | [Needed] | [Concrete action] | +| [e.g., Crisis response] | [Current] | [Needed] | [Concrete action] | + +## Adaptation Practice Plan +- **Week 1-2:** [Mirror exercise -- daily journaling of style used vs. style needed] +- **Week 3-4:** [Deliberate style experiment -- choose one situation to approach differently] +- **Month 2:** [Expand to three situations; solicit feedback from team] +- **Month 3:** [Review patterns; adjust default where evidence supports it] + +## Authenticity Boundaries +- **Will adapt:** [Behaviours I will flex] +- **Will not compromise:** [Values that remain fixed] +``` + +--- + +## Related Skills + +- **[Lewin Leadership Styles](../frameworks/lewin-leadership-styles.md)** -- The theoretical taxonomy of autocratic, democratic, and laissez-faire styles; this skill provides the daily practice, Lewin provides the conceptual foundation. +- **[Situational Leadership](../frameworks/situational-leadership.md)** -- Hersey-Blanchard's model of matching style to follower readiness; this skill adds the self-diagnosis and habit-building that the model assumes but does not teach. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness and social awareness are prerequisites for reading the room accurately enough to adapt effectively. +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The mirror exercise described here is a focused application of the broader reflective practice covered in this companion skill. +- **[Senior Leadership Transition](senior-leadership-transition.md)** -- Leadership transitions are the moments where style adaptation matters most and where default styles are most likely to fail. +- **[Reading People](../people/reading-people.md)** -- The nonverbal signal detection and mirroring techniques provide the real-time data that the Read-Choose-Act-Review adaptation cycle depends on. diff --git a/plugins/foreman/content/skills/leadership/leadership-voice-and-presence.md b/plugins/foreman/content/skills/leadership/leadership-voice-and-presence.md new file mode 100644 index 0000000..d23f144 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/leadership-voice-and-presence.md @@ -0,0 +1,184 @@ +--- +name: "leadership-voice-and-presence" +description: "Develops the multi-dimensional leadership voice that senior leaders need to communicate authentically across audiences and situations. Covers the five voice dimensions (character, context, clarity, curiosity, connection), the present-past-future introduction framework, elevator pitch evolution, and personal story as a leadership instrument. Use when preparing for a senior role introduction, refining executive communication style, building authentic presence, crafting a leadership narrative, or coaching leaders who struggle to connect with their teams." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - communication + - executive-presence + - authenticity + - storytelling + - personal-brand + - introduction + - elevator-pitch +related_skills: + - senior-leadership-transition + - leader-self-reflection + - leadership-style-adaptation + - radical-candor + - emotional-intelligence + - carnegie-win-friends +author: "Fatih Guner" +--- + +# Leadership Voice and Presence + +A CEO tells her team: "We need to be more innovative." The team hears: "What we have been doing is wrong." A VP says: "I trust you to figure this out." The team hears: "I have no idea what to do either." A founder declares: "We are pivoting to capture a massive opportunity." The team hears: "We are abandoning the thing I told you to care about six months ago." + +The gap between what leaders say and what people hear is where most leadership communication fails. Not because the words are wrong, but because the voice delivering them lacks the architecture to carry meaning across that gap. Leadership voice is not volume, charisma, or rhetorical polish. It is the capacity to respond authentically, constructively, and effectively regardless of the audience or situation -- and it is built, not born. + +--- + +## The Practice + +### The Five Dimensions of Leadership Voice + +A complete leadership voice operates across five dimensions simultaneously. Weakness in any single dimension creates a predictable failure mode. + +**1. Character** +The foundation. Character-rooted voice is anchored in principles -- "Give the benefit of the doubt," "Be direct with respect" -- that prevent the leader from becoming a chameleon who adjusts values to suit the room. Without character, the other four dimensions become performance rather than leadership. The test: does your communication remain consistent whether you are speaking to the board or to an intern? + +**2. Context** +As leaders assume senior roles, their view of the business broadens. Part of the job becomes translating that broader perspective for others. Before diving into details, address the bigger picture of the topic at hand. Context-setting prevents the disorientation that occurs when teams receive directives without understanding the strategic logic behind them. + +**3. Clarity** +Amid infinite possible priorities, the leader's voice must cut. Clarity means deciding what the team needs to focus on right now -- and, equally, what can wait. Leaders who fail to provide this risk spreading their teams thin across initiatives that compete with one another for attention. Clarity is not simplification; it is prioritisation made audible. + +**4. Curiosity** +The leader who approaches every situation as though they have all the answers silences the room. Curiosity-driven voice invites others to share their perspective, particularly when it differs from the leader's own. The practical test: in your last five meetings, what percentage of your contributions were statements versus questions? + +**5. Connection** +As a leader's purview expands, staying close to all teams and networks becomes harder. Connection-driven voice bridges that distance through storytelling about work's impact, expressing gratitude for effort, and making time for rapport even when the calendar argues against it. Connection signals that you care about people, not just outcomes. + +### The Introduction Framework: Present, Past, Future + +Leaders meet many people. Introducing yourself without rambling requires structure. The present-past-future framework distills an introduction into a few sentences: + +- **Present:** Your name, role, and what you are currently working on. +- **Past:** One sentence establishing credibility -- a previous accomplishment or relevant experience. +- **Future:** What you are excited about going forward -- a goal, a partnership, or a vision. + +Three sentences. Done. + +### The Elevator Pitch as Leadership Evolution + +Early in a career, the elevator pitch answers: "What are you working on?" and "What do you want to do?" As leaders move into senior roles, the pitch must evolve to answer different questions entirely: "Who are you as a leader?" and "What do you care most about?" The goal is to be predictable in the best sense -- someone whose values are unwavering and clear, regardless of the audience. + +### Personal Story as Leadership Instrument + +Knowing where you come from is not sentimentality; it is a strategic asset. Authentic leaders draw on their personal narratives -- the mentors, the failures, the turning points -- to connect with others and to ground their decision-making. The discipline lies in selecting which elements of your story serve the current audience and context, and in reframing hardship as motivation rather than complaint. + +--- + +## Prompts + +**Prompt 1 -- Voice Dimension Audit:** +> Assess my leadership communication across the five dimensions of voice (character, context, clarity, curiosity, connection). Here are transcripts or descriptions of five recent communications I delivered: [describe each -- audience, situation, what you said, how it was received]. For each, identify which dimensions were strong and which were absent. Then identify my dominant dimension and my weakest, and provide specific daily practices to strengthen the gap. + +**Prompt 2 -- Introduction Crafting:** +> Help me craft three versions of my professional introduction using the present-past-future framework. My current role is [role] at [company]. My relevant background includes [key experiences]. My forward-looking goals are [goals]. Create: (1) a 30-second version for networking events, (2) a 60-second version for a team all-hands where I am the new leader, and (3) a written version for a company-wide email announcement. Each should feel natural, not scripted. + +**Prompt 3 -- Leadership Narrative Design:** +> I need to develop my leadership story for [context -- e.g., board presentation, team offsite, investor meeting]. My background includes [describe key experiences, challenges, turning points]. Help me identify the three to five narrative elements that are most relevant to this audience, structure them into a coherent arc, and suggest specific moments where vulnerability will strengthen rather than undermine credibility. The story should answer: "Who is this person, and why should I follow them?" + +**Prompt 4 -- Elevator Pitch Evolution:** +> My current elevator pitch is [paste pitch]. I am moving into a [new role/stage]. Help me evolve this pitch from answering "What do I do?" to answering "Who am I as a leader and what do I stand for?" The new version should communicate my core values, my leadership philosophy, and what people can expect from me -- in under 60 seconds. + +--- + +## Use Cases + +**Growth-Stage CTO Preparing for First Board Presentation** +A CTO at a 75-person company has never presented to the board. Their communication defaults to technical depth -- detailed architecture diagrams, performance metrics, stack decisions. The board wants something different: strategic context, risk assessment, and resource implications. Applying the five-voice framework, the CTO restructures the presentation: opens with context (market dynamics driving technical decisions), delivers with clarity (three priorities, ranked), demonstrates curiosity (acknowledges two open questions the team is investigating), and closes with connection (a brief story about a customer whose experience improved because of a technical bet the team made). The board member who typically checks email during tech updates asks a follow-up question. + +**Early-Traction Founder Meeting Investors for the First Time** +A first-time founder with deep domain expertise but no public profile must introduce themselves credibly to a room of venture capitalists. Using the present-past-future framework: present ("I lead [Company], which is solving [problem] for [market]"), past ("Before founding this, I spent eight years inside the industry and saw firsthand why existing solutions fail"), future ("We are building toward [vision], and the first milestone is [concrete goal]"). The introduction takes twenty seconds. The investor leans forward. + +**Scale-Stage CEO Rebuilding Trust After a Layoff** +A CEO at a 400-person company has conducted a 15% reduction in force. The remaining employees are anxious and distrustful. The CEO's instinct is to lead with optimism: "The future is bright." But the five-voice framework demands a different sequence. Character first: acknowledge the pain honestly. Context: explain the strategic reasoning without euphemism. Clarity: name the three things the company will focus on now. Connection: share a personal reflection on the weight of the decision. Curiosity comes last: invite questions and commit to answering them. The all-hands lasts ninety minutes. It is the most important presentation the CEO has ever given. + +--- + +## Anti-Patterns + +1. **The Chameleon.** Leaders who adjust not just their communication style but their actual values depending on the room. Adapting tone is skill; adapting principles is erosion. People detect inconsistency faster than leaders expect, and the result is a reputation for unreliability disguised as flexibility. + +2. **The Monologue Default.** Leaders who interpret "presence" as commanding the floor. A voice built entirely on statements, with no curiosity dimension, creates an audience of nodders rather than contributors. The most dangerous version: the leader who solicits questions but whose body language makes clear that questions are unwelcome. + +3. **The Oversharer.** Personal narrative deployed without editorial judgment. Not every audience needs every formative experience. The discipline of leadership storytelling lies in selection: which elements of your story serve this audience, this moment, this purpose? Vulnerability without discretion becomes therapy, not leadership. + +4. **The Pitch That Never Evolves.** Leaders who introduce themselves the same way at year ten as they did at year one. The elevator pitch must mature alongside the leader's role and responsibilities. A CEO who still leads with their functional expertise signals that they have not made the mental transition to enterprise leadership. + +5. **The Context Skipper.** Jumping directly into directives without establishing the strategic rationale. Teams that do not understand why they are being asked to do something comply rather than commit -- and compliance without comprehension produces brittle execution. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder's origin story | The founder's personal narrative is the company's brand. Investors, early employees, and first customers are buying the person as much as the product. The voice must convey conviction without arrogance, and vulnerability without fragility. | +| Growth | Multi-audience calibration | The leader now addresses audiences with fundamentally different needs: engineers want technical respect, salespeople want market conviction, investors want financial discipline. The five-voice framework becomes essential for maintaining coherence across these contexts. | +| Scale | Institutional voice | At scale, the leader's voice must carry through layers of management. What you say in the executive meeting will be paraphrased in the director meeting and summarised in the team standup. Clarity and context become even more critical because your words are now a game of telephone. | + +--- + +## Output Template + +```markdown +# Leadership Voice Development Plan + +**Leader:** [Name] +**Current Role:** [Role] +**Date:** [Date] + +## Voice Dimension Assessment + +| Dimension | Current Strength (1-5) | Evidence | Development Action | +|-----------|----------------------|----------|--------------------| +| Character | [Score] | [Example] | [Action] | +| Context | [Score] | [Example] | [Action] | +| Clarity | [Score] | [Example] | [Action] | +| Curiosity | [Score] | [Example] | [Action] | +| Connection | [Score] | [Example] | [Action] | + +## Introduction Toolkit + +### 30-Second Networking Version +[Present] + [Past] + [Future] + +### Team All-Hands Version +[Extended present] + [Credibility] + [Vision] + [Invitation] + +### Written Bio Version +[Paragraph format for announcements and profiles] + +## Leadership Narrative Elements +- **Origin moment:** [The experience that shaped your leadership] +- **Defining challenge:** [A difficulty that reveals character] +- **Core conviction:** [The belief that drives your decisions] +- **Future vision:** [Where you are leading people] + +## Communication Habits to Build +| Habit | Frequency | Trigger | +|-------|-----------|---------| +| [e.g., Open with context before directives] | Every meeting | Before stating a decision | +| [e.g., Ask one genuine question per meeting] | Daily | When tempted to direct | +| [e.g., Share one story of impact per week] | Weekly | Team standup or 1:1 | +``` + +--- + +## Related Skills + +- **[Senior Leadership Transition](senior-leadership-transition.md)** -- The voice evolution described here is a necessary component of the broader identity shift required when moving to enterprise leadership. +- **[Radical Candor](../frameworks/radical-candor.md)** -- Candor is the character dimension of voice in its most consequential form: the willingness to deliver hard truths with care. +- **[Carnegie: Win Friends](../frameworks/carnegie-win-friends.md)** -- Carnegie's principles of influence map directly to the connection and curiosity dimensions of leadership voice. +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The personal narrative that grounds authentic voice is constructed through the reflective practices covered in this companion skill. +- **[Story Performance and Delivery](../storytelling/story-performance-and-delivery.md)** -- The vocal, physical, and timing techniques for live performance directly strengthen the delivery dimension of leadership presence. +- **[Persuasion and Influence](persuasion-and-influence.md)** -- Voice is the primary channel through which daily influence operates; authority, credibility, and connection all manifest through how a leader speaks. diff --git a/plugins/foreman/content/skills/leadership/leading-through-change.md b/plugins/foreman/content/skills/leadership/leading-through-change.md new file mode 100644 index 0000000..5997bea --- /dev/null +++ b/plugins/foreman/content/skills/leadership/leading-through-change.md @@ -0,0 +1,233 @@ +--- +name: "leading-through-change" +description: "Guides leaders through the emotional, communicative, and practical dimensions of organisational change, with emphasis on empathetic communication, giving people time and choices, managing personal identity transitions, and finding opportunity in chaos. Use when announcing restructuring, when teams resist a strategic pivot, when post-change morale collapses, when employees feel unheard during transitions, or when a leader's own identity is disrupted by professional upheaval." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - change-management + - communication + - empathy + - transitions + - resilience + - uncertainty + - identity + - patience +related_skills: + - kotter-change-model + - vuca-framework + - storytelling-for-leaders + - leader-resilience-and-wellbeing + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +# Leading Through Change + +Map the emotional terrain before you map the project plan. People cycling through significant organisational change -- a restructuring, a pivot, a merger, a leadership transition -- move through five feelings, not always in order, and often revisiting earlier ones: + +1. **Denial** -- "This will not actually affect my work." The comforting fiction that the announcement is theoretical. +2. **Anxiety** -- "What does this mean for me?" The self-preservation instinct that no amount of corporate messaging can bypass. +3. **Anger** -- "Why wasn't I consulted?" The feeling of agency being stripped away, which may be directed at the change itself or at the people leading it. +4. **Grief** -- "I miss how things were." The mourning of routines, relationships, and identities attached to the old order. +5. **Adaptation** -- "I can see my place in this." The tentative engagement with a new reality, contingent on feeling heard and included. + +Most change-leadership failures occur because the leader, having already processed these feelings privately over weeks or months of planning, expects the organisation to arrive at adaptation within days. Erika Andersen's research is direct: you have had weeks to think about this change; your employees are hearing about it for the first time. Of course they ask questions. Of course they worry. That is not resistance. That is the normal human response to losing certainty. + +Kotter's eight-step model provides the structural architecture for change management (see `kotter-change-model.md`). This skill operates in the spaces between those steps -- the daily emotional labour that determines whether a structurally sound change process succeeds or stalls. + +--- + +## The Practice + +### Ask Before You Tell + +Patti Sanchez's research identifies empathetic communication as the single most important leadership behaviour during change. The practice is counterintuitive for leaders accustomed to providing answers: before telling people what is happening, ask them what they are worried about. + +The sequence: +1. Explain what is changing and why, with as much transparency as the situation permits. +2. Ask: "What concerns do you have?" and "What improvements would you like to see?" +3. Listen without defending, correcting, or minimising. +4. Address what you heard, being honest about what you can and cannot control. +5. Repeat at each phase of the change, because concerns evolve as reality unfolds. + +The goal is not to eliminate worry. It is to ensure that everyone feels included and heard -- which is the necessary precondition for the buy-in that makes change executable. + +### Give People Time + +Andersen's most practical insight: stop trying to talk employees out of their feelings. Doubt and scepticism are not obstacles to be removed; they are stages to be traversed. The leader who responds to worry with "Don't worry, this will be great" has communicated two things: that the leader does not understand the employee's experience, and that expressing concern is unwelcome. Neither message builds buy-in. + +Instead, give people time to process. Acknowledge that the emotions they are feeling are reasonable. Ask about their concerns without being dismissive. Talk through what the change means for them specifically, not just for the organisation abstractly. The time invested in this emotional processing is not a delay in the change process -- it is the change process. Without it, compliance replaces commitment, and compliance does not survive the first setback. + +### Give People Choices + +Andersen's second principle addresses the mechanism behind much change resistance: loss of agency. Organisational change often makes employees feel they are at the mercy of forces they cannot control. The antidote is to return as many choices as possible: + +- Let managers co-create the communication plan for their teams. +- Invite teams to propose timelines for implementing new processes. +- Identify elements that will not change and highlight them explicitly. +- Where the outcome is fixed but the path is flexible, let teams choose the path. + +The choices need not be large. Even small decisions -- when to hold the transition meeting, which communication channel to use, which team members will take which new responsibilities -- restore a sense of control that makes the larger change tolerable. + +### Caring Transparency + +Rasmus Hougaard, Jacqueline Carter, and Rob Stembridge describe "caring transparency" as the practice of being honest about what is on the leader's mind and in the leader's heart, especially when making unpopular decisions. This is not vulnerability for its own sake. It is the recognition that withholding important information -- even with good intentions -- communicates distrust. + +The key distinction: caring transparency is not unbounded disclosure. It is the willingness to tell people where they stand, clearly and compassionately, rather than allowing ambiguity to breed worse anxieties than the truth would. + +### Courage over Comfort + +Hougaard, Carter, and Stembridge also address the leader's own emotional challenge during change: the temptation to choose safety over conviction. Choosing courage -- making decisions based on values rather than quick profits, standing for what you believe even when criticism follows -- can feel vulnerable. But courage, once demonstrated, invites others to do the same. It transforms a change initiative from a top-down mandate into a shared endeavour. + +### Patience as a Change Skill + +David Sluss's research positions patience not as a personality trait but as a learnable leadership skill. During change, patience serves three functions: + +1. **Steadying the team.** A leader who cannot stay calm cannot keep others calm. +2. **Allowing strategy to work.** New approaches take time to produce results; premature abandonment of a sound plan because of early friction is one of the most common change-leadership errors. +3. **Resisting the always-on culture.** The pressure for immediate replies and constant connectivity works against the careful, methodical decision-making that change requires. + +### Navigating Personal Identity Transitions + +Toubiana, Ruebottom, and Hakak study what happens when a major change -- personal or professional -- upends the leader's own sense of self. Their research identifies four practices for navigating identity disruption: + +**1. Create a clean break.** Choose an event -- a date, a milestone, a symbolic moment -- to serve as the dividing line between "before" and "after." Mentally imbue it with significance. Consider telling a colleague or friend to add weight to the transition. + +**2. Work through hard emotions.** Acknowledge negative feelings without letting them become permanent residents. If being laid off produces anger and shame, sit with those feelings -- but also identify the positive outcomes the change has produced. The goal is not to suppress negative emotions but to make peace with them. + +**3. Focus on your many facets.** Your identity is not reducible to your job title. When professional identity is disrupted, invest in the other elements: family, community, hobbies, friendships. The reminder that you are more than your role can stabilise the ground when the role is shifting. + +**4. Craft a linking narrative.** Connect your past and present with a story that highlights continuity of values even as circumstances change. "I used to support my family through salary; now I support them through time" is a narrative that bridges two different chapters without denying the loss involved in the transition. + +### Seven-Year Cycles + +Avivah Wittenberg-Cox offers a structural perspective: dividing one's life into seven-year periods and mapping the highlights, learnings, and identity shifts of each era. The practice imposes a rhythm -- beginning, middle, end -- that normalises transition. When a significant change arrives, the mental model provides context: "I am nearing the end of one era and entering the beginning of another. I have done this before." + +### Chaos as Growth + +Rebecca Knight's reframe for organisational upheaval: choose to see chaos as a chance to grow, not a barrier to progress. When leadership changes, restructurings loom, or strategy pivots, the leader's mindset determines whether they -- and their team -- navigate the turbulence or succumb to it. The questions to ask: How do the changes affect my role? What do they mean for the company's future? How could they advance my career or enhance my skills? Staying "heads up" -- scanning the environment for opportunity -- beats "heads down" -- burying oneself in routine until the storm passes. + +--- + +## Prompts + +**Prompt 1 -- Emotional Map of Change:** +> I am leading (or about to announce) this change: [describe the change, its scope, and its rationale]. Map the likely emotional journey for three different stakeholder groups: [group 1], [group 2], [group 3]. For each group, predict which of the five feelings (denial, anxiety, anger, grief, adaptation) will be strongest and in what order. Design a communication cadence that addresses each group's emotional arc over the first 90 days. + +**Prompt 2 -- Empathetic Communication Script:** +> I need to announce [describe the change] to my team of [size]. Draft the announcement using Sanchez's framework: (a) what is changing and why, (b) what I want to ask them (concerns, hopes, suggestions), (c) what I can commit to transparently, and (d) what I genuinely do not know yet. Include follow-up questions for one-on-one conversations and a timeline for when I will provide updates. + +**Prompt 3 -- Choice Architecture for Change:** +> This change is non-negotiable: [describe what must happen]. Using Andersen's framework, identify every element of the change where people can be given a choice about how, when, or by whom the change is implemented. Design a "choices menu" I can present alongside the announcement to restore agency without compromising the initiative's objectives. + +**Prompt 4 -- Personal Transition Navigation:** +> I am going through a significant professional change: [describe it -- new role, company restructuring, departure, pivot]. Using Toubiana, Ruebottom, and Hakak's four practices, help me: (a) identify a clean "before/after" marker, (b) name the emotions I need to work through, (c) identify the non-work facets of my identity I should invest in, and (d) craft a linking narrative that connects my past and future through shared values. + +--- + +## Use Cases + +**Early-traction startup pivoting its product** + +A 15-person startup is abandoning its original product to pursue a new market. The founder, who has been processing this decision for two months, announces the pivot on Monday and expects the team to be executing by Wednesday. Instead, three engineers who joined specifically because of the original product feel betrayed. The founder implements the ask-before-tell protocol: individual conversations about concerns, explicit acknowledgement that the emotional response is legitimate, and a week of structured transition time before any new-product work begins. Two of the three engineers choose to stay, having been given time and voice. + +**Growth-stage company restructuring teams** + +A 150-person company reorganises from functional teams to cross-functional squads. The announcement produces widespread anxiety about reporting lines, role identity, and career paths. The leadership team creates a "choices menu": each squad can design its own communication norms, choose its meeting cadence, and propose which responsibilities transfer and which stay. The elements of the change that are non-negotiable (squad structure, key assignments) are clearly stated. The elements that are flexible (how, when, and by whom) are handed to the teams. Resistance decreases measurably within two weeks. + +**Scale-stage leader navigating personal identity disruption** + +A long-tenured division president is moved to a newly created "strategic initiatives" role as part of a CEO succession plan. The leader interprets the move as a demotion and experiences anger, grief, and a profound loss of identity. Using the seven-year-cycle framework, they map their career into eras and recognise that previous transitions -- from individual contributor to manager, from manager to director -- also felt like losses before they became gains. A linking narrative emerges: "My value has always been in building things that outlast me. The division was one such thing. Strategic initiatives is the next." + +--- + +## Anti-Patterns + +**1. Leading with logic when people need empathy.** The leader who responds to emotional resistance with a business case for change has correctly identified the destination and entirely misjudged the starting point. Logic is necessary but not sufficient; empathy must come first. + +**2. Labelling all pushback as "resistance."** Andersen is explicit: questions and concerns during change are not resistance. They are the normal, healthy, and predictable response of human beings who have just lost certainty. The leader who frames all pushback as opposition creates a self-fulfilling prophecy: people stop voicing concerns, not because they have been convinced, but because they have been silenced. + +**3. Expecting adaptation on the leader's timeline.** The leader has had weeks or months to process the change. Expecting the team to process it in days is unrealistic and, when enforced through impatience, destructive. Genuine buy-in takes the time it takes. + +**4. Eliminating all choice in the name of speed.** Speed and agency are not always in conflict. Giving people choices about implementation details rarely slows the initiative and frequently accelerates it, because people execute plans they helped design more willingly than plans imposed upon them. + +**5. Ignoring the leader's own emotional journey.** The leader going through change is also a human being experiencing uncertainty, loss, and identity disruption. Pretending otherwise -- performing certainty while feeling doubt -- eventually produces either burnout or a credibility collapse when the mask slips. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Pivot communication, founder's emotional honesty | The team is small enough for individual conversations; use that advantage | +| Growth | Restructuring, scaling norms, manager enablement | Changes affect people the leader does not personally know; communication must cascade through managers | +| Scale | Enterprise transformation, culture preservation during M&A | Change becomes a programme, not a conversation; structural supports (choice architecture, feedback loops, transition teams) replace personal touch | + +At early traction, the leader can speak to every affected person individually. This is an enormous advantage that founders routinely squander by defaulting to all-hands announcements. In a 15-person company, 15 individual conversations -- each tailored to that person's concerns, each asking "What worries you?" -- take a few hours and produce buy-in that a single group presentation cannot. + +At scale, the leader cannot reach everyone personally. The critical infrastructure becomes the manager layer: equipping middle managers to have empathetic conversations, providing them with honest information, and giving them the same emotional processing time before expecting them to transmit confidence to their teams. The change process becomes recursive: leadership processes the change, then equips managers, who then support their teams, each layer given its own time and space. + +--- + +## Output Template + +```markdown +# Change Communication Plan -- [Initiative Name] + +**Change description:** [What is changing] +**Rationale:** [Why] +**Scope:** [Who is affected] +**Timeline:** [Key dates] +**Prepared by:** [Name] + +## Emotional Map + +| Stakeholder Group | Dominant Feeling (Week 1) | Likely Progression | Tailored Message | +|-------------------|--------------------------|-------------------|-----------------| +| [Group 1] | [Feeling] | [Sequence] | [Key message] | +| [Group 2] | [Feeling] | [Sequence] | [Key message] | +| [Group 3] | [Feeling] | [Sequence] | [Key message] | + +## Communication Cadence + +| Timing | Channel | Audience | Content | Ask | +|--------|---------|----------|---------|-----| +| Day 1 | [Channel] | [Audience] | [What to communicate] | [What to ask] | +| Week 1 | [Channel] | [Audience] | [Follow-up] | [Concerns check] | +| Week 4 | [Channel] | [Audience] | [Progress update] | [Adjustment input] | +| Week 8 | [Channel] | [Audience] | [Status report] | [Feedback] | + +## Choices Menu + +| Non-Negotiable | Flexible | Choice Given To | +|---------------|----------|----------------| +| [Element] | [Element] | [Group] | +| [Element] | [Element] | [Group] | + +## Leader Self-Check +- Have I given people time to process, or am I expecting adaptation on my timeline? +- Am I labelling pushback as resistance, or hearing it as legitimate concern? +- Have I been transparently caring, or have I withheld information to avoid discomfort? +- Have I processed my own emotions about this change, or am I performing certainty? + +## 90-Day Milestones +- **Day 30:** [Expected state, check-in method] +- **Day 60:** [Expected state, check-in method] +- **Day 90:** [Expected state, check-in method, adjustment mechanism] +``` + +--- + +## Related Skills + +- **[Kotter's Change Model](../frameworks/kotter-change-model.md)** -- The structural eight-step process for change management; this skill provides the emotional and communicative layer that Kotter's model assumes but does not detail. +- **[VUCA Framework](../frameworks/vuca-framework.md)** -- Change often occurs in volatile, uncertain, complex, and ambiguous environments; VUCA provides the diagnostic lens for the operating context. +- **[Storytelling for Leaders](storytelling-for-leaders.md)** -- Change communication is, at its core, storytelling; the companion skill on narrative provides the techniques for making change stories compelling. +- **[Leader Resilience and Wellbeing](leader-resilience-and-wellbeing.md)** -- Leading through change is emotionally taxing; the resilience skill addresses the leader's own sustainability during transitions. +- **[Team Culture and Dynamics](team-culture-and-dynamics.md)** -- Change disrupts team culture; this companion skill provides tools for diagnosing and rebuilding team norms during and after transitions. +- **[Stoic Acceptance and Amor Fati](../stoic/stoic-acceptance-amor-fati.md)** -- The philosophical discipline of embracing rather than resisting change provides leaders with the emotional grounding to model calm during turbulent transitions. diff --git a/plugins/foreman/content/skills/leadership/learning-agility.md b/plugins/foreman/content/skills/leadership/learning-agility.md new file mode 100644 index 0000000..94d3731 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/learning-agility.md @@ -0,0 +1,211 @@ +--- +name: "learning-agility" +description: "Builds the leader's capacity for rapid, continuous learning through humility, curiosity, feedback receptivity, cross-training, reflective practice, and deliberate skill selection. Use when a leader's expertise has become stale, when the organisation faces skills gaps that training alone cannot close, when setbacks trigger defensiveness rather than growth, or when a leader senses that what got them here will not get them there." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - learning + - growth + - adaptability + - feedback + - curiosity + - skills + - cross-training + - reflection +related_skills: + - growth-mindset + - flow-state + - emotional-intelligence + - focus-and-priority-management + - leader-resilience-and-wellbeing +author: "Fatih Guner" +--- + +# Learning Agility + +Every skill you possess has a shelf life. The half-life of a technical skill is now estimated at roughly two and a half years, down from a decade in the 1980s. Management skills decay more slowly but decay nonetheless -- the leadership behaviours that produced results in a 20-person startup may actively hinder a 200-person company. The leader who built their career on deep functional expertise discovers, usually with some discomfort, that expertise is depreciating while the organisational demand for adaptability appreciates. Clayton Christensen, reflecting on this dynamic, observed a painful irony: by the time leaders reach positions of authority, they often believe that only people smarter than them have something to teach them. That belief, which felt like earned confidence at 30, becomes a growth ceiling at 45. + +Learning agility -- the capacity for rapid, continuous learning from experience -- is not a personality trait. It is a practice. Korn Ferry's research confirms that leaders who rely on the same assumptions and behavioural repertoires they have used for years are prone to stagnate, underperform, or derail. The antidote is not more training. It is a fundamentally different relationship with one's own competence: one that treats expertise as a platform for further learning rather than a fortress to be defended. + +--- + +## The Practice + +### The Four Disciplines of Learning Agility + +Drawing from Monique Valcour's synthesis of the Korn Ferry research, learning agility rests on four daily disciplines: + +**1. Receiving Feedback Without Armour** + +Success creates a thick skin that is useful for absorbing criticism and dangerous for absorbing information. When a leader with a track record hears critical feedback, the default response is to classify it as an exception ("That was a one-off") or to challenge the source ("They don't understand the full picture"). Valcour's prescription is brutal in its simplicity: do not argue. Listen. Sit with the discomfort. Then evaluate whether the feedback reveals a pattern worth investigating. + +Erika Andersen extends this with a physical metaphor: when negative feedback arrives, take a breath. The breath creates a gap between stimulus and response -- just enough space to ask "How accurate is this, and how do I know?" rather than "How can I refute this?" + +**2. Experimenting with New Approaches** + +Competence produces routine, and routine produces efficiency, and efficiency produces rigidity. The discipline here is to deliberately disrupt one's own problem-solving patterns. When facing a challenge, ask: "How am I inclined to tackle this?" and then: "What are three alternative approaches I have not tried?" The goal is not to abandon what works but to expand the repertoire. A leader who can solve problems in only one way is a specialist. A leader who can solve them in several ways is adaptable. + +**3. Making Cross-Domain Connections** + +John Zenger, Joseph Folkman, and Scott Edinger's research on "competency companions" reveals that incremental improvement in an existing strength yields far less than developing a complementary skill. A technically brilliant leader who invests another 100 hours in technical depth gains marginal returns. The same leader who invests 100 hours in communication skills makes the existing technical expertise dramatically more accessible and influential. + +The practice: identify a skill domain unrelated to your core competence. Then find connections between that domain and your work. A finance leader who studies design thinking. An engineer who studies negotiation. The cross-pollination produces insights that single-domain expertise cannot generate. + +**4. Making Time for Reflection** + +Research from multiple universities confirms that regular reflection on work experiences significantly boosts learning. The practice need not be elaborate. Two questions, asked weekly: + +- "What have I learned from this week's experiences?" +- "What turned out differently than I expected, and what does that tell me?" + +Leaders who demonstrate and encourage reflection create teams that learn faster. The signal matters as much as the substance: when the boss visibly takes time to reflect, it gives permission for everyone else to do the same. + +### Choosing What to Learn + +Erika Andersen proposes three lenses for selecting the next skill to develop: + +| Lens | Question | Example | +|------|----------|---------| +| Value creation | What would help my team or company create more value? | Studying large-project management to reduce delivery times | +| Passion | What am I genuinely excited to learn? | Process architecture, because I find systems fascinating | +| Aptitude | What related skill might I have natural talent for? | Complex project management, given my existing organisational strengths | + +The ideal target sits at the intersection of all three. When that intersection is empty, start with passion -- motivation sustains effort when the learning curve steepens. + +### Reading Fiction as Leadership Development + +Brooke Vuckovic's argument for fiction is not sentimental. Fiction provides low-cost lessons in moral complexity that non-fiction cannot replicate. Fictional characters grapple with greed, self-deceit, likability, and competing loyalties -- precisely the dilemmas that leaders face but that business case studies sanitise. A leader who reads Anna Karenina or The Remains of the Day develops a vocabulary for moral ambiguity that a leader who reads only management books does not. + +### Staying in Learning Mode + +Researchers from UNSW Sydney Business School and the University of Michigan distinguish between performance mode and learning mode. In performance mode, setbacks signal inability. In learning mode, setbacks signal that the skill set is not yet complete. The practical difference is enormous: performance-mode leaders compare themselves to peers and feel threatened by gaps. Learning-mode leaders track their own growth trajectory and treat gaps as queues for the next investment. + +The simplest intervention is a self-check question deployed at the moment of difficulty: "Am I in learning mode right now?" If the answer is no, the follow-up is: "What can this situation teach me?" + +### Learning Everywhere + +Darja Kragt's research demonstrates that leadership development need not be confined to the office. Parenting, recreational sport, volunteer work, and community leadership all involve influence, decision-making, and interpersonal dynamics. The leader who experiments with a new coaching approach in their weekend football team before deploying it at work reduces the risk and increases the learning. + +--- + +## Prompts + +**Prompt 1 -- Skill Shelf-Life Audit:** +> Here are my core professional skills and when I last significantly developed each: [list skills and approximate dates]. For each, estimate its current shelf life based on industry trends. Identify the three skills most at risk of obsolescence and recommend a specific learning path for each, using the three-lens framework (value creation, passion, aptitude). + +**Prompt 2 -- Feedback Pattern Analysis:** +> Here is a summary of feedback I have received over the past 12 months: [list key themes from reviews, 360s, informal comments]. Identify recurring patterns, especially those I may have dismissed or classified as one-offs. For each pattern, suggest one experiment I can run in the next 30 days to test whether the feedback reveals a genuine development need. + +**Prompt 3 -- Cross-Training Blueprint:** +> My primary expertise is in [domain]. Identify three complementary skill domains that would amplify the impact of my existing strengths, using Zenger and Folkman's competency-companion model. For each, recommend a specific 30-day learning experiment: what to study, who to learn from, and how to measure progress. + +**Prompt 4 -- Learning Mode Reset:** +> I am currently facing this challenge: [describe challenge]. I suspect I am in performance mode rather than learning mode. Reframe this challenge as a learning opportunity: what skills is it asking me to develop? What can I learn from the difficulty itself? What would I do differently if I treated this as a training exercise rather than a test? + +--- + +## Use Cases + +**Validation-stage founder who knows everything about the product and nothing about sales** + +A technical founder has built an impressive product but cannot close deals. Rather than hiring a sales leader immediately (which the company cannot afford), the founder applies the three-lens framework: sales skills would create value (lens one), the founder finds persuasion intellectually interesting (lens two), and their existing empathy and listening skills provide aptitude (lens three). A 90-day self-directed learning sprint -- combining a sales methodology book, weekly practice calls with a mentor, and deliberate experimentation in customer conversations -- produces enough competence to close the first ten customers personally. + +**Growth-stage leader who resists feedback** + +A VP of engineering has consistently received feedback that they micromanage. Each time, they classify it as a misunderstanding ("I'm just being thorough"). A new coach introduces the breath-and-evaluate technique: when the feedback arrives, pause, do not argue, and then ask "How accurate is this, and how do I know?" The VP begins tracking delegation decisions in a journal. Over eight weeks, a pattern emerges: they intervene in technical decisions that their team leads are fully capable of making. The data -- their own data -- bypasses the defensiveness that external feedback could not penetrate. + +**Scale-stage executive facing technological disruption** + +A chief operating officer recognises that AI is transforming operations but has no technical background in machine learning. Rather than enrolling in a comprehensive course (which would take months the company does not have), the COO identifies three internal data scientists and proposes a learning exchange: the COO teaches them stakeholder management, and they teach the COO enough about AI capabilities to make informed strategic decisions. The cross-training produces mutual understanding in weeks rather than months. + +--- + +## Anti-Patterns + +**1. Treating learning as an event rather than a practice.** A three-day workshop does not produce learning agility. Workshops produce exposure. Agility comes from daily habits: reflection, feedback processing, experimentation. Leaders who "do their learning" at the annual offsite and then revert to default behaviour for eleven months are investing in the appearance of growth. + +**2. Learning only what is comfortable.** The leader who reads five more books on a topic they already understand is deepening expertise, not building agility. Agility requires discomfort -- specifically, the discomfort of being a beginner in a domain where one is accustomed to mastery. + +**3. Collecting knowledge without applying it.** Learning agility is measured by behaviour change, not by the number of books read, courses completed, or podcasts consumed. If six months of learning produce no observable change in how a leader operates, the learning is decorative. + +**4. Confusing learning mode with permissive self-assessment.** "I'm in learning mode" is not an excuse for persistent underperformance. Learning mode is a cognitive orientation that accelerates improvement; it is not a licence to remain indefinitely incompetent. The goal is faster progress, not lower standards. + +**5. Expecting the organisation to drive your learning.** Waiting for the company to offer a training programme, assign a mentor, or create a development plan is a passive posture incompatible with leadership. The most agile learners design their own curriculum and seek their own feedback, using organisational resources as supplements rather than substitutes. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Learning breadth, generalist skills | The founder must learn everything; agility is survival | +| Validation | Customer-facing skills, rapid iteration | Learning speed determines how fast hypotheses are tested | +| Early Traction | Delegation skills, management fundamentals | The founder must learn to lead, not just do | +| Growth | Strategic thinking, organisational design | Learning shifts from functional skills to systems skills | +| Scale | Industry foresight, cross-domain synthesis | Learning becomes about anticipation rather than reaction | + +At idea stage, the founder who cannot learn quickly enough will not survive. Every week brings a new domain to master -- legal, financial, technical, commercial. Learning agility at this stage is not a development aspiration; it is an existential requirement. + +At growth, the learning challenge inverts. The founder who succeeded by being the best individual contributor must now learn to lead other contributors. This transition is among the most common derailment points in company building: the skills that produced early success (deep technical work, hands-on customer contact, personal execution) must be partially surrendered in favour of skills that feel alien (delegation, strategic thinking, organisational design). The leader who cannot make this shift becomes the company's ceiling. + +--- + +## Output Template + +```markdown +# Learning Agility Plan -- [Name] + +**Date:** [Date] +**Current role:** [Title] +**Planning horizon:** [6 months / 12 months] + +## Skill Shelf-Life Audit + +| Skill | Last Major Development | Estimated Shelf Life | Risk Level | +|-------|----------------------|---------------------|------------| +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | + +## Next Skill Target + +| Lens | Assessment | +|------|-----------| +| Value creation | [How this skill helps the team/company] | +| Passion | [Level of genuine interest: high/medium/low] | +| Aptitude | [Related existing strengths] | + +**Selected skill:** [Name] +**Learning method:** [Course / Mentor / Cross-training / Self-directed] +**30-day experiment:** [Specific actions and milestones] +**Success indicator:** [Observable behaviour change] + +## Feedback Processing Log + +| Date | Feedback Received | Initial Reaction | After Reflection | Action Taken | +|------|------------------|-----------------|-----------------|-------------| +| [Date] | [Summary] | [Honest first response] | [Revised assessment] | [Experiment or change] | + +## Weekly Reflection Questions +1. What did I learn from this week's experiences? +2. What turned out differently than I expected? +3. Am I in learning mode right now? +``` + +--- + +## Related Skills + +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Dweck's framework provides the psychological foundation for learning agility; this skill provides the daily behavioural layer. +- **[Flow State](../frameworks/flow-state.md)** -- Learning requires periods of deep, focused engagement; flow states accelerate skill acquisition. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness, a core EQ dimension, is the prerequisite for honest skill assessment and feedback receptivity. +- **[Focus and Priority Management](focus-and-priority-management.md)** -- Learning requires protected time; without calendar discipline, growth remains aspirational. +- **[Leader Resilience and Wellbeing](leader-resilience-and-wellbeing.md)** -- The vulnerability required for genuine learning is only possible when the leader has sufficient emotional reserves. +- **[AI Learning for Leaders](../ai-leadership/ai-learning-for-leaders.md)** -- Applies the general learning agility principles specifically to AI literacy, the most pressing domain where non-technical leaders must build new competence rapidly. diff --git a/plugins/foreman/content/skills/leadership/learning-from-failure.md b/plugins/foreman/content/skills/leadership/learning-from-failure.md new file mode 100644 index 0000000..b23078b --- /dev/null +++ b/plugins/foreman/content/skills/leadership/learning-from-failure.md @@ -0,0 +1,199 @@ +--- +name: "learning-from-failure" +description: "Builds the leadership capacity to lose well, share mistakes productively, analyse failures alongside successes, overcome perfectionism, and create team environments where setbacks accelerate growth rather than trigger blame. Use when recovering from a major project failure, noticing a blame culture on the team, struggling with personal perfectionism, conducting post-mortems, or seeking to build psychological safety through vulnerability about past errors." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - failure + - psychological-safety + - perfectionism + - resilience + - post-mortem + - learning + - vulnerability + - growth-mindset +related_skills: + - psychological-safety + - growth-mindset + - emotional-courage + - giving-feedback + - radical-candor +author: "Fatih Guner" +--- + +# Learning from Failure + +Consider a thought experiment: what if leaders displayed their failures as prominently as their wins? A trophy case in the corner office, but instead of deal tombstones and framed press clippings, it held the pitch deck that lost the account, the product that customers rejected, the hire who left after three months. The idea feels absurd -- and that absurdity reveals how deeply organisations have internalised the fiction that competent leaders do not fail. They do. The research is unambiguous: around 70% of people react poorly to failure, whether by blaming others, denying the problem, or absorbing disproportionate personal guilt. The difference between leaders who grow and those who stagnate is not the frequency of their failures but the quality of their response. + +--- + +## The Framework + +Learning from failure is not a single practice but a constellation of five interlocking disciplines. + +### Discipline 1: Lose Well + +Failure is inevitable; losing badly is optional. "Losing well" is a learnable skill with three distinct strategies: + +**Pivot the effort.** When a project fails, resist the urge to bury it. Step back and ask: what worked in what was tried? Skills, innovations, and ideas developed for a failed initiative rarely lack application -- they simply lack the right context. The creative thinking that produced a failed product may be a perfect fit for a different problem. + +**Reconnect to purpose.** If the work matters for reasons beyond winning, the loss stings less and teaches more. Work is finite -- projects end, companies fold, people leave. But the underlying purpose is not bounded by any single outcome. Leaders who anchor in purpose rather than scoreboard can absorb losses without losing direction. + +**Share the pain.** Losing involves heartbreak, frustration, and sorrow that leaders often feel obligated to suppress. Creating space for the team to acknowledge negative feelings -- to talk about what happened and how it felt -- builds the kind of psychological safety that, paradoxically, enables future risk-taking. Hard times bring people together; ignoring that dynamic wastes its value. + +### Discipline 2: Share Mistakes -- And Lessons + +Psychological safety does not emerge from policy documents. It emerges from leaders modelling the behaviour they want to see. When team members struggle with setbacks, the leader who recounts a time they fell short at work -- explaining what happened, what they felt, and what they did differently afterward -- accomplishes several things simultaneously: they normalise error, they demonstrate that failure is survivable, and they provide a concrete template for learning from it. + +The sharing must include emotional honesty. Mentioning the fear, doubt, or embarrassment that accompanied the mistake is what separates genuine vulnerability from performance. A sanitised war story about a failure that "turned out great in the end" teaches nothing about how to sit with the discomfort of genuine loss. + +### Discipline 3: Analyse Failures Alongside Successes + +One of the most common analytical errors in post-mortems is examining failures in isolation. A team misses a target and discovers that its members were not using the workflow management tool. The obvious remedy: enforce tool adoption. But what if the successful teams were not using it either? Analysing failures without a comparison to successes produces false causation -- solutions to problems that were not actually problems. + +**The comparative method:** + +| Question | Failure Case | Success Case | Genuine Differentiator? | +|----------|-------------|--------------|------------------------| +| What tools were used? | [Describe] | [Describe] | [Yes/No] | +| What processes were followed? | [Describe] | [Describe] | [Yes/No] | +| What resources were available? | [Describe] | [Describe] | [Yes/No] | +| What decisions were made at key junctures? | [Describe] | [Describe] | [Yes/No] | + +Only factors that differ between success and failure cases deserve remediation investment. Everything else is noise. + +### Discipline 4: Respond to Mistakes with Curiosity + +When an employee makes a mistake, the leader's first response sets the cultural tone for every future mistake. Judgement and blame teach people to hide problems. Curiosity and inquiry teach people to surface them early. + +The protocol is straightforward but counter-instinctive: + +1. **Withhold judgment.** Resist the immediate urge to assign blame or express disappointment. +2. **Express curiosity.** Ask what happened, what the person's thinking was, and what assumptions they were operating under. +3. **Adopt a learning mindset.** Recognise that the full picture is not yet visible. The goal is understanding, not sentencing. +4. **Extract the lesson together.** Frame the conversation as a shared investigation, not an interrogation. + +### Discipline 5: Tame Perfectionism + +Perfectionism masquerades as high standards but often functions as a productivity trap. It paralyses decisions (because every choice feels monumental), triggers over-delivery on tasks that need only be adequate, and creates anxiety that compounds with every unfinished project. + +**Three rules for managing perfectionism:** + +- **The three-thought rule.** Once a decision has been considered three times, make the call and move forward. Continued deliberation past this threshold yields diminishing returns and increasing anxiety. +- **The checklist test.** Before starting work, define what "complete" looks like. Once the checklist is satisfied, stop. The inner perfectionist will fret over font choices and semicolons -- the checklist provides an objective exit criterion. +- **The perspective check.** Show a draft to a trusted colleague and ask what it needs to be good enough -- not perfect. Follow their guidance. Perfectionism is often a solitary affliction; external perspective is the antidote. + +--- + +## Prompts + +**Prompt 1 -- Failure Autopsy:** +> I recently experienced a significant failure: [describe the situation, what went wrong, and the outcome]. Walk me through a structured analysis that examines this failure alongside a comparable success. Help me identify which factors genuinely differentiated the failure from the success, and which were common to both. Then recommend specific changes based only on the genuine differentiators. + +**Prompt 2 -- Failure-Sharing Script:** +> I want to share a past failure with my team to build psychological safety. The failure was [describe]. Help me craft a narrative that includes what happened, what I felt (fear, doubt, embarrassment), what I learned, and what I did differently afterward. The tone should be honest without being self-flagellating, and instructive without being preachy. Keep it under three minutes of speaking time. + +**Prompt 3 -- Perfectionism Intervention:** +> I suspect my perfectionism is reducing my effectiveness. My symptoms include [describe -- e.g., difficulty finishing projects, over-preparing for presentations, inability to delegate because no one meets my standards]. Design a personalised set of rules and practices to manage my perfectionism. Be specific -- I need concrete triggers and responses, not general advice about "letting go." + +**Prompt 4 -- Team Failure Response Audit:** +> Analyse how my team currently responds to mistakes. Recent examples include [describe 2-3 instances where someone made an error and how the team/leadership responded]. Assess whether our response pattern builds or erodes psychological safety, and recommend specific changes to our failure response protocol. + +--- + +## Use Cases + +**Idea-Stage Founder Processing a Rejected Pitch** + +A founder pitches twelve investors and receives twelve rejections. The temptation is to interpret this as a verdict on the idea. Instead, the founder applies the comparative method: they analyse the three pitches that generated the most engagement alongside the three that fell flattest. The differentiator is not the idea but the framing -- pitches that led with the customer problem generated follow-up questions; pitches that led with the technology generated polite silence. The failure was not in the concept but in its communication. The thirteenth pitch leads with the problem and closes a pre-seed round. + +**Growth-Stage Engineering Team with a Blame Culture** + +An engineering team conducts post-mortems that reliably identify a person to blame rather than a system to fix. Outages are followed by tense meetings where the engineer who deployed the faulty code is publicly identified. Engineers respond rationally: they deploy less frequently, take fewer risks, and hide problems longer. The VP of Engineering introduces a new post-mortem protocol: no names in incident reports, mandatory curiosity-first questioning, and a requirement that every post-mortem identify at least one systemic factor. Within six months, deployment frequency doubles and mean time to recovery drops by 40%. + +**Scale-Stage Executive Overcoming Personal Perfectionism** + +A COO who built their career on meticulous attention to detail is now responsible for an organisation of 800 people. The perfectionism that served them as an individual contributor is paralysing them as an executive: they rewrite direct reports' presentations, delay strategic decisions while gathering incrementally more data, and hold weekly reviews that last four hours because no detail is too small to examine. Applying the three-thought rule and the checklist test, the COO redesigns their operating rhythm: strategic decisions are made after three rounds of input, presentations are reviewed once with comments rather than rewritten, and weekly reviews are time-boxed to ninety minutes with a pre-circulated agenda. Direct reports begin to take more ownership, and the COO recovers twelve hours per week for strategic work. + +--- + +## Anti-Patterns + +1. **Performing vulnerability.** Sharing a carefully curated failure story that has been polished into a redemption narrative. If the "failure" always ends with "and that's how I became who I am today," it is not vulnerability; it is personal branding. Genuine failure stories include the parts that remain uncomfortable. + +2. **Analysing failure without a success baseline.** Investing in new tools, trainings, and processes based on what failed teams did wrong -- without checking whether successful teams did the same things. This produces plausible but incorrect remediation. + +3. **Treating all failures as learning opportunities.** Some failures result from negligence, dishonesty, or repeated refusal to heed warnings. Not every failure deserves the curiosity-first response. The leader must distinguish between intelligent failures (good-faith efforts in uncertain conditions) and preventable ones (known risks that were ignored). + +4. **Confusing perfectionism with high standards.** High standards produce excellent work within reasonable timeframes. Perfectionism produces excellent work at the cost of everything else -- deadlines, relationships, health, and the team's autonomy. The distinction matters because leaders often defend perfectionism by calling it "commitment to quality." + +5. **Losing without learning.** Absorbing failures stoically without extracting lessons. Resilience without reflection is simply endurance. The goal is not to survive failure but to metabolise it into capability. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Processing personal rejection | Failures at this stage feel existential because the idea and the founder are indistinguishable. Learning to separate self-worth from outcome is the critical skill. | +| Validation | Rapid iteration through failure | The entire stage is designed around failing fast and cheap. Leaders who cannot lose small bets quickly will never find what works. | +| Early Traction | Building team failure norms | As the first team forms, the leader's response to the first mistake sets the cultural template for every mistake that follows. | +| Growth | Institutionalising failure analysis | Post-mortems, retrospectives, and comparative analysis must become organisational habits, not ad-hoc responses to crises. | +| Scale | Preventing perfectionism paralysis | The standards that built the company's reputation can become the rigidity that prevents its adaptation. Leaders must distinguish between standards worth defending and standards worth relaxing. | + +--- + +## Output Template + +```markdown +# Failure Analysis: [Event/Project Name] + +## What Happened +- **Timeline:** [Sequence of events leading to the failure] +- **Expected outcome:** [What was supposed to happen] +- **Actual outcome:** [What did happen] + +## Comparative Analysis +| Factor | This Failure | Comparable Success | Genuine Differentiator? | +|--------|-------------|-------------------|------------------------| +| [Factor 1] | [Description] | [Description] | [Yes/No] | +| [Factor 2] | [Description] | [Description] | [Yes/No] | +| [Factor 3] | [Description] | [Description] | [Yes/No] | + +## Root Cause (Based on Genuine Differentiators Only) +- **Primary cause:** [Description] +- **Contributing factors:** [Description] +- **Systemic vs. individual:** [Was this a system failure or a person failure?] + +## Emotional Inventory +- **What the team felt:** [Honest assessment] +- **What was expressed:** [What was actually said] +- **Gap:** [What was suppressed and why] + +## Lessons and Changes +| Lesson | Specific Change | Owner | Timeline | +|--------|----------------|-------|----------| +| [Lesson 1] | [Action] | [Person] | [When] | +| [Lesson 2] | [Action] | [Person] | [When] | + +## What to Carry Forward +- [Skills, ideas, or innovations from this failure that deserve a new context] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- The organisational condition that makes learning from failure possible; without it, failures are hidden rather than examined. +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- The cognitive orientation that treats failure as data rather than verdict; growth mindset is the individual prerequisite for the team practices described here. +- **[Emotional Courage](emotional-courage.md)** -- Sharing failures authentically and responding to mistakes with curiosity both require emotional courage that must be deliberately built. +- **[Giving Feedback](../frameworks/giving-feedback.md)** -- Post-failure conversations are a specialised form of feedback; the same principles of specificity, timing, and psychological safety apply. +- **[Stoic Acceptance and Amor Fati](../stoic/stoic-acceptance-amor-fati.md)** -- Provides the philosophical foundation for embracing failure as a source of growth rather than merely tolerating it as an inevitable cost. +- **[Managing Weakness and Mistakes](../thinking/managing-weakness-and-mistakes.md)** -- Extends the failure analysis into systematic safeguards and mistake-handling protocols that prevent recurring failures. diff --git a/plugins/foreman/content/skills/leadership/managing-up.md b/plugins/foreman/content/skills/leadership/managing-up.md new file mode 100644 index 0000000..797fb6a --- /dev/null +++ b/plugins/foreman/content/skills/leadership/managing-up.md @@ -0,0 +1,190 @@ +--- +name: "managing-up" +description: "Guides leaders in building effective upward relationships with their managers and senior executives. Covers keeping bosses informed, demonstrating strategic thinking to skip-level leaders, understanding a manager's goals and pressures, setting realistic expectations, and proactively managing the information flow. Use when feeling undervalued by leadership, preparing for skip-level meetings, navigating a new boss relationship, seeking promotion readiness, or clarifying expectations with a manager." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - managing-up + - boss-relationship + - career-advancement + - strategic-visibility + - communication + - skip-level + - expectations +related_skills: + - trust-equation + - radical-candor + - giving-feedback + - strategic-thinking-and-alignment + - emotional-courage +author: "Fatih Guner" +--- + +# Managing Up + +The most career-defining skill nobody teaches is invisible by design. Managing up -- the deliberate cultivation of a productive relationship with one's boss -- receives no curriculum in business school, no chapter in the onboarding manual, and no line item in the performance review. Yet the gap between what a leader accomplishes and what their boss perceives them as accomplishing determines promotions, resource allocation, and institutional survival more reliably than raw competence ever will. The uncomfortable truth is that talent unwitnessed is talent wasted. Effective leaders do not merely perform; they ensure the right people understand what they are performing, why it matters, and how it connects to the organisation's strategic arc. + +--- + +## The Framework + +Managing up is not flattery, nor is it political manoeuvring. It is a structured practice built on four pillars: information management, strategic visibility, boss comprehension, and expectation calibration. + +### Pillar 1: Information Management -- Close the Gap + +Most leaders dramatically underestimate how much information their boss needs. The assumption that a competent manager "already knows" is both common and dangerous. Bosses operate under information asymmetry by default: they manage multiple reports, navigate competing priorities, and cannot read minds. The effective leader treats upward information flow as a design problem, not an afterthought. + +**The information gap manifests in two directions:** + +- **Under-reporting:** Assuming the boss knows more than they do. Projects stall, problems escalate, and the boss is blindsided -- all because a direct report confused autonomy with silence. +- **Over-reporting:** Flooding a manager with granular detail, forcing them to extract signal from noise. This is not diligence; it is delegation of cognitive work upward. + +The discipline lies in matching information type, frequency, and format to the boss's actual needs. Some managers want a daily stand-up summary. Others want to hear nothing until something is on fire. Neither preference is wrong; failing to learn it is. + +### Pillar 2: Strategic Visibility -- Be Witnessed Thinking + +Competence alone does not earn advancement. Senior executives need to witness strategic thinking in action. This means preparing for meetings not merely to contribute but to demonstrate the altitude of one's perspective. Before a strategy session, the effective leader blocks time to think through the agenda, considers cross-departmental implications, and prepares a point of view that shows they are not thinking in a vacuum. + +**Three methods for demonstrating strategic thinking:** + +1. **Reframe operational updates as strategic contributions.** Instead of "We shipped feature X on time," try "Feature X positions us to capture the mid-market segment three months ahead of the competitor timeline." +2. **Ask questions that reveal long-term thinking.** In skip-level conversations, ask about five-year milestones, industry trends the team should respond to, or how the team's contributions might evolve given strategic priorities. +3. **Play CEO for a day.** Periodically imagine holding the top job and viewing current meetings, projects, and emails from that vantage. What value would a CEO find in the work? What would they change? + +### Pillar 3: Boss Comprehension -- Map Their World + +To manage up effectively, a leader must understand the boss's operating context with granular precision. This is not about manipulation; it is about alignment. The essential map includes: + +| Dimension | Questions to Answer | +|-----------|-------------------| +| Goals | What are their organisational and personal objectives? | +| Pressures | What demands come from their peers, their own boss, and the board? | +| Working style | Do they prefer email, meetings, instant messages, or hallway conversations? | +| Strengths | Where do they excel, and where can you complement their gaps? | +| Weaknesses | What do they struggle with, and how can you shield them without overstepping? | +| Decision patterns | Do they decide quickly or deliberate? Do they want options or recommendations? | + +This mapping must be refreshed continuously. A boss's priorities shift with quarterly targets, organisational restructuring, and personal circumstances. The leader who mapped their boss's world in January and stopped paying attention by March is operating on stale intelligence. + +### Pillar 4: Expectation Calibration -- Ask, Don't Assume + +The burden of understanding what the boss expects falls on the direct report -- not the other way around. Formal systems like planning processes and performance reviews provide a skeleton, but they never capture the full picture. Expectations exist on a spectrum from broad ("what kinds of problems should I escalate?") to granular ("what format should interim project reports take?"). The leader who passively assumes they know what their boss expects is building on sand. + +Two corrective habits: + +- **Proactive clarification:** At the start of any significant project, explicitly ask what success looks like from the boss's perspective, what updates they want, and what decisions they wish to be consulted on. +- **Realistic boss expectations:** Accept that most managers are not mind-readers. They have competing demands and limited bandwidth. Rather than resenting what the boss fails to provide, take responsibility for articulating what is needed. + +--- + +## Prompts + +**Prompt 1 -- Boss Communication Audit:** +> Analyse my current communication pattern with my boss. I report to [describe role and style of your boss]. My typical update frequency is [describe]. My boss's preferred communication channels are [describe]. Identify gaps in my information flow: Am I under-reporting, over-reporting, or mismatching format to preference? Design a communication cadence that matches my boss's needs while keeping me efficient. + +**Prompt 2 -- Skip-Level Meeting Preparation:** +> I have a meeting with my boss's boss [describe their role and what you know about their priorities]. Prepare five strategic questions I can ask that demonstrate long-term thinking about the business, awareness of industry trends, and understanding of how my team's work connects to company strategy. The questions should feel natural, not performative. + +**Prompt 3 -- Boss Mapping Exercise:** +> Help me build a comprehensive profile of my boss. Here is what I know: [describe their goals, pressures, working style, strengths, and weaknesses as best you can]. Identify blind spots in my understanding and suggest specific observations or conversations that would fill them. Then recommend three adjustments to how I work with them based on this profile. + +**Prompt 4 -- Expectation Alignment Conversation:** +> I suspect my boss and I are not aligned on expectations for [describe project or role area]. Draft a conversation framework that lets me clarify their expectations without seeming uncertain or incompetent. Include specific questions to ask and phrases that signal proactive ownership rather than dependency. + +--- + +## Use Cases + +**Growth-Stage CTO Preparing for Board Visibility** + +A CTO at a Series B company does excellent technical work but is invisible to the board. The CEO fields all board questions about the technology roadmap. The CTO applies boss comprehension to understand the CEO's board pressures, then offers to prepare a quarterly technology brief that the CEO can present -- or, better, that the CTO can present directly. By framing this as reducing the CEO's preparation burden rather than as a personal visibility play, the CTO gains board exposure without threatening the CEO's authority. Within two quarters, board members begin directing technical questions to the CTO directly. + +**Early-Traction Founder Managing an Investor-Board Chair** + +A first-time founder treats their lead investor like a passive shareholder, sending updates only when milestones are hit. The investor grows anxious and begins making back-channel inquiries to team members. The founder recalibrates by mapping the investor's information needs: monthly updates sent on the same day, proactive flagging of risks alongside wins, and a quarterly phone call to discuss strategic direction. The investor's anxiety drops, back-channel inquiries stop, and the relationship shifts from surveillance to partnership. + +**Scale-Stage VP Navigating a New Boss** + +A VP of Product has thrived under a hands-off CEO for three years. A new CEO arrives with a detail-oriented style and expects weekly written updates. The VP initially bristles, interpreting the request as micromanagement. After applying the boss comprehension framework, the VP recognises that the new CEO is under board pressure to demonstrate operational control during a strategic pivot. The VP redesigns their reporting format to match the CEO's needs, and what felt like surveillance becomes a vehicle for demonstrating strategic alignment. + +--- + +## Anti-Patterns + +1. **Confusing managing up with managing impressions.** Managing up is about alignment and effectiveness, not about curating a personal brand. The leader who manages up well solves real problems for their boss; the one who manages impressions solves only their own visibility problem. Bosses eventually distinguish between the two. + +2. **Waiting for the boss to create the relationship.** A pervasive and costly passivity. The assumption that a good boss will proactively provide information, clarity, and development is reasonable in theory and unreliable in practice. Most managers are overwhelmed. The direct report who waits will wait a long time. + +3. **Treating all bosses identically.** Applying the same communication style, frequency, and format to every manager is a failure of adaptation. A data-driven CFO and a relationship-driven Chief People Officer require fundamentally different upward management strategies. + +4. **Bypassing your boss to impress their boss.** Skip-level visibility is valuable only when the direct boss supports it. Going around a manager to build relationships with senior leaders creates distrust that no amount of strategic questioning can repair. + +5. **Assuming expectations are static.** Clarifying expectations once and never revisiting them. Priorities shift, contexts change, and what mattered in Q1 may be irrelevant by Q3. Expectation calibration is a recurring practice, not a one-time conversation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Investor-as-boss management | The "boss" is often a lead investor or advisor. Information flow and expectation alignment directly affect funding continuity. | +| Early Traction | First manager relationships | Founders begin hiring leaders who report to them while they themselves report to a board. Managing in both directions simultaneously is a new skill. | +| Growth | Skip-level visibility | As layers multiply, the leader's relationship with their boss's boss becomes strategically important. Demonstrating strategic thinking to senior executives determines career trajectory. | +| Scale | Institutional upward management | Managing up becomes systemic: executive communication cadences, board reporting rhythms, and cross-functional alignment processes replace individual boss relationships. | + +At every stage, the foundational principle holds: the burden of the relationship falls on the person who has the most to gain from its effectiveness -- which is almost always the direct report. + +--- + +## Output Template + +```markdown +# Upward Relationship Audit: [Boss Name / Role] + +## Boss Profile +- **Goals (organisational):** [What they are measured on] +- **Goals (personal):** [What they care about beyond metrics] +- **Key pressures:** [From their boss, board, peers, or market] +- **Preferred communication:** [Channel, frequency, format] +- **Decision style:** [Quick vs. deliberative; options vs. recommendations] +- **Strengths I can leverage:** [Where they excel] +- **Gaps I can complement:** [Where they need support] + +## Current Information Flow Assessment +| Dimension | Current State | Ideal State | Gap | +|-----------|--------------|-------------|-----| +| Update frequency | [Current] | [Needed] | [Over/Under/Matched] | +| Update format | [Current] | [Preferred] | [Aligned/Misaligned] | +| Risk escalation | [Current pattern] | [Expected pattern] | [Gap description] | +| Strategic context | [How much I provide] | [How much is needed] | [Gap description] | + +## Expectation Alignment +- **Confirmed expectations:** [What has been explicitly discussed] +- **Assumed expectations:** [What I think they expect but have not confirmed] +- **Unknown expectations:** [Areas where I have no clarity] + +## 30-Day Action Plan +| Week | Action | Purpose | +|------|--------|---------| +| 1 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 2 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 3 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 4 | [Specific action] | [Alignment, visibility, or comprehension goal] | +``` + +--- + +## Related Skills + +- **[Trust Equation](../frameworks/trust-equation.md)** -- The trust a boss places in a direct report is decomposable into credibility, reliability, intimacy, and self-orientation; managing up is the practice of building all four deliberately. +- **[Radical Candor](../frameworks/radical-candor.md)** -- Upward candor -- telling a boss what they need to hear rather than what they want to hear -- is a high-risk, high-reward form of managing up. +- **[Giving Feedback](../frameworks/giving-feedback.md)** -- Providing constructive upward feedback to a boss requires all four pillars of managing up to be functioning; without trust and comprehension, upward feedback backfires. +- **[Strategic Thinking and Alignment](strategic-thinking-and-alignment.md)** -- Strategic visibility with senior leaders is the outward expression of strategic thinking capability; the two skills are mutually reinforcing. +- **[Delegation and Empowerment](delegation-and-empowerment.md)** -- Effective delegation creates the time and headspace required for upward relationship management; leaders who cannot delegate cannot manage up. +- **[Emotional Courage](emotional-courage.md)** -- Delivering bad news upward and pushing back on a boss's flawed direction require the incremental courage-building practices this companion skill develops. diff --git a/plugins/foreman/content/skills/leadership/mentoring-and-coaching.md b/plugins/foreman/content/skills/leadership/mentoring-and-coaching.md new file mode 100644 index 0000000..69145ae --- /dev/null +++ b/plugins/foreman/content/skills/leadership/mentoring-and-coaching.md @@ -0,0 +1,183 @@ +--- +name: "mentoring-and-coaching" +description: "Provides a practical system for being an effective mentor and coach -- selecting mentees, building mentorship teams, setting ground rules, heading off rifts, avoiding power misuse, preparing successors, and finding daily coaching micro-moments. Use when a leader takes on a new mentee, notices a protege stalling, needs to structure informal development conversations, wants to shift from directing to coaching, or seeks to scale mentoring across an organisation without formal programmes." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - mentoring + - coaching + - talent-development + - succession + - feedback + - protege + - daily-practice +related_skills: + - grow-model + - psychological-safety + - emotional-intelligence + - leadership-pipeline +author: "Fatih Guner" +--- + +# Mentoring and Coaching + +MULTIPLIER. One mentor can alter the trajectory of an entire organisation -- not by running it, but by developing the people who do. The arithmetic is compounding: a leader who mentors three people, each of whom mentors three others, has shaped twelve leaders within a single generation. Yet most mentoring relationships are accidental, unstructured, and ultimately disappointing. The mentor offers vague wisdom. The mentee nods politely. Both parties gradually stop scheduling meetings. The failure is not one of intention but of craft. Vineet Chopra and Sanjay Saint's six-part framework for great mentoring -- choose carefully, establish a team, run a tight ship, head off rifts, don't hold back, prepare successors -- treats mentoring as a discipline with standards, not a favour dispensed on goodwill. + +The distinction between mentoring and coaching matters. Mentoring is a long-arc relationship focused on career trajectory, institutional navigation, and wisdom transfer. Coaching is a conversational practice -- often brief, often daily -- focused on helping someone solve their own problems. A leader needs both capabilities. The first builds the next generation. The second builds the next day. + +--- + +## The Framework + +### The Six Disciplines of Great Mentoring + +**Discipline 1: Choose Mentees Carefully** + +Mentoring is an investment, not a charity. A good mentee demonstrates curiosity, organisation, responsibility, and engagement. The diagnostic is simple: assign a small task -- read a book and discuss it within a month, attend a strategy session and write up observations. What returns tells you everything about their thinking process, communication discipline, and genuine interest. Mentees who expect the mentor to sustain the relationship, or who insist on doing things exclusively their own way, are signalling that the investment will not compound. + +**Discipline 2: Build a Mentorship Team** + +No single mentor possesses everything a protege needs. The effective mentor identifies what areas the mentee wants to develop, maps those areas to people in their network with relevant expertise, and recruits them as auxiliary advisors. The mentor remains the primary source of career, moral, and institutional support, but the team approach ensures the mentee has breadth of access. Peers who contribute to someone's growth with a lower level of commitment often find the arrangement energising rather than burdensome. + +**Discipline 3: Run a Tight Ship** + +Ground rules established at the outset prevent the slow erosion that kills most mentoring relationships. Three conversations are required early: + +- What does the mentee want from the relationship? +- What is the mentor willing to provide -- and what falls outside scope? +- What cadence, communication norms, and escalation procedures will govern the relationship? + +Accountability is non-negotiable. The mentor must make clear that second-rate work reflects on both parties. Standards are not punitive; they are protective. + +**Discipline 4: Head Off Rifts** + +Disagreements are inevitable. The mentor's responsibility is to address them immediately -- not to let friction accumulate until the relationship quietly dissolves. The repair protocol: initiate the conversation (do not wait for the mentee to raise it), ask for their perspective, resist rushing to judgment, and identify the root cause. Open, frank relationships are the mechanism through which mentoring creates value. Without candour, the relationship is decorative. + +**Discipline 5: Don't Hold Back** + +Power dynamics in mentoring can corrupt. The mentor must guard against five specific misuses: + +| Behaviour | Why It Happens | Why It Destroys | +|-----------|---------------|-----------------| +| Taking credit for the mentee's ideas | The mentor's ego conflates guidance with authorship | Erodes the mentee's confidence and public recognition | +| Insisting the mentee advance the mentor's projects | The mentor confuses mentoring with delegation | Converts a developmental relationship into an extractive one | +| Tethering the mentee to the mentor's timeline | Comfort with the status quo overrides the mentee's growth | Slows the protege's career progression unnecessarily | +| Discouraging other mentors | The mentor's ego requires exclusivity | Isolates the mentee from broader learning and recognition | +| Allowing self-destructive mistakes to continue unremarked | Conflict avoidance masquerading as respect for autonomy | Permits damage that honest feedback would have prevented | + +**Discipline 6: Prepare Successors** + +The mentor's primary job is to transfer wisdom. The secondary job -- equally important -- is to identify mentees who can become mentors themselves. Candidates need true expertise and a generous disposition. The preparation involves transparency about the mentor's own decision-making process: how problems are analysed, solutions weighed, and support calibrated. Co-mentoring a new mentee is an effective bridge until the successor is ready to operate independently. The ultimate measure of a mentor's success is not the protege's achievements but the protege's capacity to develop others. + +### Daily Coaching Micro-Moments + +Formal mentoring programmes are insufficient. Real development happens in the five-minute check-in, the post-meeting debrief, the hallway observation. Three daily practices fill the gap: + +1. **Check-in questions.** "How are things going?" is a start, but "What are your career goals, and how can I help?" signals genuine investment. Ask regularly, not ritualistically. +2. **In-the-moment feedback.** When you observe an employee in action -- a presentation, a negotiation, a difficult conversation -- offer specific feedback: what they did well, what could improve, and why. Timeliness matters; feedback delivered a week later loses 80% of its developmental impact. +3. **Coaching stance over directing stance.** The instinct to tell people what to do is deeply embedded, particularly in leaders who built their reputation on decisive action. Coaching requires the opposite: listen first, ask questions, withhold judgment, and draw wisdom from the person being coached. The goal is helping them learn to solve problems independently, not solving problems for them. + +Herminia Ibarra and Anne Scoular's research is direct: leaders who rate themselves as good coaches consistently overestimate their skill. The diagnostic is whether the other person leaves the conversation with their own insight or with the leader's instruction. If it is the latter, it was not coaching. + +--- + +## Prompts + +**Prompt 1 -- Mentee Selection Assessment:** +> I am considering mentoring [describe the person -- role, experience, what drew your attention]. Help me design a selection test: a small, revealing task that will surface their curiosity, organisation, communication quality, and genuine interest. The task should take no more than two weeks and produce an artefact I can evaluate. Also suggest three questions I should ask myself after reviewing their work. + +**Prompt 2 -- Mentorship Team Design:** +> My mentee wants to develop in these areas: [list areas]. My own expertise covers: [list areas]. Identify the gaps where I cannot provide adequate guidance. Then describe the profile of the auxiliary mentors I should recruit -- what expertise they need, what commitment level is realistic, and how I should approach them. + +**Prompt 3 -- Mentoring Relationship Audit:** +> I have been mentoring [person] for [duration]. Here is the current state of the relationship: [describe -- frequency of contact, recent interactions, any tensions, progress observed]. Audit the relationship against the six disciplines: selection quality, team support, ground rules, rift management, power dynamics, and succession preparation. Identify which disciplines are strong and which need intervention. Provide specific actions for the weakest two. + +**Prompt 4 -- Daily Coaching Shift:** +> I tend to direct rather than coach. Here is a recent interaction where I told someone what to do instead of helping them figure it out: [describe the situation and what you said]. Rewrite my side of the conversation using a coaching approach -- questions instead of answers, drawing out their thinking instead of imposing mine. Then give me three questions I can use in similar situations going forward. + +--- + +## Use Cases + +**Early-Traction Startup: Founder Mentoring First Managers** +A founder with 25 employees has promoted three individual contributors to management. None has managed before. Rather than sending them to a generic management course, the founder applies the six disciplines: selects carefully (these three demonstrated curiosity and responsibility as ICs), builds a mentorship team (recruits a seasoned COO from their investor's portfolio company as an auxiliary advisor), establishes ground rules (bi-weekly 30-minute check-ins, specific preparation expected from each mentee), and commits to in-the-moment coaching after every difficult management conversation. Within six months, all three managers are conducting their own coaching conversations with direct reports -- the compounding has begun. + +**Growth-Stage Company: VP Recovering from a Mentoring Failure** +A VP of Product mentored a promising director for two years. The relationship ended badly: the director felt micromanaged, the VP felt the director was ungrateful. A post-mortem against the six disciplines reveals failures in discipline three (no ground rules established), discipline four (a disagreement about project ownership festered for three months), and discipline five (the VP had been insisting the director advance VP-level projects rather than developing their own work). The VP restructures their approach for a new mentoring relationship, beginning with explicit ground rules, a shared document tracking goals and concerns, and a quarterly check on power dynamics. + +**Scale-Stage Organisation: Building a Mentoring Culture Without a Programme** +A 400-person company's HR team wants to launch a formal mentoring programme. The CEO, having seen formal programmes devolve into bureaucratic matching exercises, instead trains all directors in daily coaching micro-moments: check-in questions, in-the-moment feedback, and the coaching-over-directing stance. Each director is asked to identify one person whose development they will actively invest in -- not through programme paperwork, but through the six disciplines. The result: 30 active mentoring relationships, each with ground rules and accountability, none requiring programme administration. + +--- + +## Anti-Patterns + +1. **Mentoring as Autobiography.** The mentor who treats every conversation as an opportunity to narrate their own career. The mentee's context is not a prompt for the mentor's reminiscence. Great mentoring is about the mentee's trajectory, informed by -- not replaced by -- the mentor's experience. + +2. **The GROW Model as the Entire Coaching Repertoire.** GROW is a powerful conversational structure (covered in detail in the frameworks category). But leaders who apply it rigidly to every interaction -- including five-minute hallway conversations -- turn coaching into a formulaic exercise. Daily coaching micro-moments require fluency, not frameworks. Know when structure helps and when it hinders. + +3. **Confusing Sponsorship with Mentoring.** Sponsorship is about using your influence to create opportunities for someone. Mentoring is about developing their capacity to create opportunities for themselves. Both are valuable. Conflating them produces a protege who advances positionally without developing the capability to sustain that advancement. + +4. **Avoiding Difficult Feedback to Preserve the Relationship.** Allowing a mentee to repeat self-destructive patterns because correcting them feels uncomfortable. This is not kindness; it is negligence. The mentor who does not hold back -- discipline five -- serves the mentee's long-term interest at the cost of short-term discomfort. + +5. **Scaling Mentoring Through Technology.** Believing that a mentoring platform, matching algorithm, or scheduling tool can substitute for the relational investment that makes mentoring work. Technology can support logistics. It cannot manufacture the trust, candour, and accountability that define a productive mentoring relationship. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder as primary mentor | The founder mentors the first wave of managers directly. The mentorship team is small or external (advisors, investors). The six disciplines apply in compressed form -- ground rules and accountability are particularly critical because everyone is learning simultaneously. | +| Growth | Mentoring the mentors | The leader's task shifts from direct mentoring to developing others' mentoring capability (discipline six). The mentorship team expands. Daily coaching micro-moments become the primary development mechanism because formal mentoring cannot scale to every employee. | +| Scale | Cultural embedding | Mentoring becomes an organisational expectation, not a personal choice. The leader's role is to model mentoring behaviour, resource it (time, not software), and hold leaders accountable for developing their people. The ultimate diagnostic: does development happen when the CEO is not watching? | + +--- + +## Output Template + +```markdown +# Mentoring Relationship Plan: [Mentor] -> [Mentee] + +## Selection Rationale +- Why this person: [specific evidence of curiosity, organisation, engagement] +- Selection test result: [what was assigned, what was returned, what it revealed] + +## Mentorship Team +| Area | Primary Mentor | Auxiliary Advisor | Contact Cadence | +|------|---------------|-------------------|-----------------| +| [development area] | [name/self] | [name] | [frequency] | + +## Ground Rules +- Meeting cadence: [frequency, duration, format] +- Communication norms: [how and when to contact between meetings] +- Accountability standard: [what quality of work is expected] +- Review cycle: [when the relationship itself will be evaluated] + +## Current Development Focus +- Short-term (90 days): [specific goal] +- Medium-term (12 months): [specific goal] +- Succession indicator: [what would signal this mentee could mentor others] + +## Power Dynamics Check +- [ ] Am I taking credit for their work? +- [ ] Am I using them for my projects? +- [ ] Am I tethering them to my timeline? +- [ ] Am I discouraging other mentors? +- [ ] Am I allowing self-destructive patterns? +``` + +--- + +## Related Skills + +- **[GROW Model](../frameworks/grow-model.md)** -- Whitmore's four-stage coaching conversation framework provides the structural backbone for formal coaching sessions; this skill covers the daily, informal practices that surround and extend those sessions. +- **[Teaching and Leading](../people/teaching-and-leading.md)** -- Extends the coach-student mindset into distributed leadership and mirror-neuron-based modelling techniques for team development. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Edmondson's framework explains why mentees withhold problems and mistakes; a mentor who has not established psychological safety in the dyad will receive curated updates rather than honest ones. +- **[Leadership Pipeline](../frameworks/leadership-pipeline.md)** -- The pipeline model identifies the transition points where mentoring is most critical -- from individual contributor to manager, from manager to director -- and what capabilities each transition demands. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness and empathy are the mentor's primary tools; without them, mentoring degrades into lecturing. diff --git a/plugins/foreman/content/skills/leadership/persuasion-and-influence.md b/plugins/foreman/content/skills/leadership/persuasion-and-influence.md new file mode 100644 index 0000000..811533c --- /dev/null +++ b/plugins/foreman/content/skills/leadership/persuasion-and-influence.md @@ -0,0 +1,177 @@ +--- +name: "persuasion-and-influence" +description: "Equips leaders with daily micro-influence tactics -- reading emotional temperature in meetings, deploying peer power, establishing authority organically, using consistency commitments, and knowing when to compromise. Use when preparing for a difficult one-on-one, navigating a meeting where buy-in is needed, responding to an ultimatum, auditing informal influence networks, or needing to persuade without positional authority. Complements the theoretical Cialdini and Fisher/Ury frameworks with practical, moment-to-moment application." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - influence + - persuasion + - meetings + - negotiation + - micro-tactics + - reading-the-room + - compromise +related_skills: + - cialdini-influence + - win-win-negotiation + - carnegie-win-friends + - trust-equation +author: "Fatih Guner" +--- + +# Persuasion and Influence in Practice + +INVISIBLE FORCE. The leader who wins arguments they never appear to have is not manipulative -- they are observant. They notice that the CFO crosses her arms when numbers are presented without context. They register that the head of engineering responds to peer endorsement more readily than to executive mandate. They sense when a room's emotional temperature has shifted from receptive to defensive, and they adjust -- not their position, but their delivery -- in the space between two sentences. This is not the psychology of persuasion as academic taxonomy. This is persuasion as a daily leadership practice: the granular, often invisible work of moving people toward decisions they would have reached themselves, given enough time and the right information. + +The theoretical architecture of influence -- Cialdini's seven principles, Fisher and Ury's principled negotiation -- exists elsewhere in this system. What follows is the applied craft: how influence actually operates in the hallway conversation, the budget meeting, the one-on-one where resistance is palpable but unexpressed. + +--- + +## The Framework + +Daily influence operates through five practical domains. Each represents a recurring leadership situation where micro-tactics produce disproportionate results. + +### Domain 1: Mapping Your Influence Network + +Influence is not a function of title. Maxim Sytch's research demonstrates that informal power -- the actual ability to get things done -- depends on a network of relationships that may bear little resemblance to the org chart. The diagnostic is straightforward: + +1. List the ten people you most depend on to accomplish your work. +2. For each, identify what you uniquely offer them (career advice, emotional support, stakeholder access, technical expertise). +3. Flag imbalances: do they help you more than you help them? Are they clustered in one business unit? +4. Identify gaps: whose cooperation do you need but lack a relationship with? + +Leaders who complete this audit often discover that their influence network is narrower, more lopsided, and more fragile than they assumed. The corrective is deliberate investment -- not transactional favours, but genuine contributions across a broader organisational footprint. + +### Domain 2: Reading the Room + +Jay Conger's research on persuasion reveals a capability that separates effective persuaders from ineffective ones: accurate emotional calibration. Great persuaders sense their audience's receptivity and match their delivery to it. Sometimes that requires force. Sometimes a whisper suffices. The diagnostic question is not "what do I want to say?" but "what is this room capable of hearing right now?" + +**Practical signals to monitor:** + +| Signal | Interpretation | Adjustment | +|--------|---------------|------------| +| Arms crossed, minimal eye contact | Defensive posture; the audience feels threatened | Lower intensity; acknowledge concerns before advancing position | +| Rapid nodding, forward lean | Engaged but potentially rushing to agree without processing | Slow down; ask probing questions to ensure genuine buy-in | +| Side conversations emerging | Attention has fractured; the argument is losing relevance | Pause; reconnect the discussion to the audience's specific concerns | +| One person dominates response | Group dynamics have shifted to a single voice | Redirect: "I'd like to hear other perspectives before we continue" | +| Silence after a proposal | Processing, not necessarily disagreement | Wait. Do not fill the silence with more arguments. | + +The last point deserves emphasis. Most leaders interpret silence as resistance and respond by talking more. Skilled influencers interpret silence as processing and respond by waiting. + +### Domain 3: Micro-Influence in One-on-One Settings + +The persuasion principles that operate at scale -- social proof, scarcity -- are less relevant in a private conversation between two people. What matters in one-on-one influence: + +**Similarity and genuine connection.** Find authentic common ground early. Shared interests, shared frustrations, shared professional experiences -- any genuine bond creates receptivity. The emphasis is on genuine. Manufactured similarity is detectable and corrosive. + +**Organic authority establishment.** Mentioning relevant experience should feel like context, not credentials. "When we faced a similar situation at my previous company" establishes authority without the awkwardness of reciting a CV. Weave expertise into the conversation; never announce it. + +**Active, public, voluntary commitment.** When seeking buy-in, engineer commitments that are spoken aloud (active), made in front of at least one other person (public), and freely chosen (voluntary). An email confirming a colleague's commitment to a timeline is more binding than a verbal nod in a hallway. A commitment made in a team standup is more binding still. + +### Domain 4: Navigating Ultimatums and Resistance + +When a negotiation stalls or an ultimatum lands, the instinct is to either capitulate or escalate. Research from Ma, Yang, and Savani suggests a third path: adopt a choice mindset. Before any negotiation, list every option available to both parties -- not just the obvious ones. If salary is fixed, what about vacation days, remote work, project selection, reporting structure, professional development budget? When an ultimatum narrows the conversation to a single variable, the choice mindset re-expands it. + +Effective persuaders also enter every influence situation with compromises already prepared. Conger's research is direct: colleagues respond more positively to a persuader who visibly incorporates their input. Flexibility signals trustworthiness. Rigidity signals that the conversation is a performance, not a collaboration. + +### Domain 5: Relationship as the Foundation + +Influence is not a technique applied to a relationship. It is a property of the relationship itself. Linda Hill and Kent Lineback's research is unequivocal: every day, every interaction, every word is examined by the people a leader seeks to influence. They are asking a single question -- "Can I trust this person?" -- and the answer determines the upper limit of the leader's influence. + +This means that daily influence is cumulative, not episodic. The leader who is transparent about reasoning, consistent in follow-through, and genuinely curious about others' perspectives builds an influence reservoir that makes any single persuasion moment easier. The leader who is erratic, opaque, or self-serving finds that no technique compensates for the deficit. + +--- + +## Prompts + +**Prompt 1 -- Influence Network Audit:** +> Map my influence network. Here are the ten people I most depend on to get work done: [list names and roles]. For each, I've noted what I offer them and what they offer me: [describe]. Identify imbalances, gaps, and risks in this network. Then recommend three specific actions to strengthen it -- prioritising relationships where my influence deficit is highest. + +**Prompt 2 -- Meeting Influence Strategy:** +> I have a meeting tomorrow where I need to persuade [describe audience] to support [describe proposal]. The likely resistance points are: [describe]. Design a meeting influence strategy: how should I open, what emotional temperature should I aim for, how should I handle the likely objections, and what compromises should I have prepared? Include specific language I can use. + +**Prompt 3 -- One-on-One Persuasion Preparation:** +> I need to persuade [person, role] to [desired outcome] in a one-on-one conversation. Here is what I know about their priorities: [describe]. Here is our relationship history: [describe]. Design an approach using similarity, organic authority, and commitment engineering. Include specific talking points and the commitment mechanism I should aim for by the end of the conversation. + +**Prompt 4 -- Ultimatum Response:** +> I have received an ultimatum in a negotiation: [describe the ultimatum and context]. Before I respond, help me expand the option space. List every variable that could be in play beyond the one the ultimatum focuses on. Then design a response that neither capitulates nor escalates, using the choice mindset framework. + +--- + +## Use Cases + +**Growth-Stage CTO Seeking Engineering Budget Approval** +A CTO needs the CFO to approve a significant infrastructure investment. The CFO has rejected similar requests twice, citing ROI uncertainty. Rather than presenting the same data louder, the CTO conducts an influence network audit and discovers that the VP of Sales -- who has a strong relationship with the CFO -- is frustrated by system downtime affecting customer demos. The CTO enlists the VP of Sales to describe the revenue impact at the next leadership meeting (peer power). In the meeting itself, the CTO reads the room: the CFO's body language shifts from guarded to engaged when the VP of Sales speaks. The CTO adjusts, asking the CFO what ROI threshold would make the investment acceptable (commitment via voluntary criteria-setting). The budget is approved within two weeks. + +**Scale-Stage VP Navigating a Cross-Functional Deadlock** +Two department heads have been unable to agree on a shared platform migration timeline. The VP responsible for both departments enters a joint meeting with compromises pre-prepared: two of three proposed concessions address each department's stated concerns. By opening with "I've incorporated both teams' feedback into three options -- and I want to hear what I've missed," the VP signals flexibility. The department heads, whose resistance was partly driven by feeling unheard, shift from positional bargaining to collaborative problem-solving. The organic authority move -- "When we ran a similar migration at [previous company], we found that..." -- provides context without dictation. The meeting concludes with a publicly stated commitment from both leads, documented in a follow-up email. + +--- + +## Anti-Patterns + +1. **Technique Without Relationship.** Deploying influence tactics on a relationship with no trust foundation. If the people you seek to influence do not believe you have their interests in mind, no amount of tactical sophistication compensates. Build the relationship first; the techniques amplify what already exists. + +2. **Reading the Room and Ignoring What You Read.** Many leaders are excellent at sensing emotional shifts in a meeting and then proceed to deliver their pre-planned argument anyway. Reading the room is worthless without the willingness to adapt in real time. + +3. **Confusing Compromise with Weakness.** Leaders who view any concession as a loss of face. Conger's research is clear: prepared compromises increase influence. The leader who enters a persuasion moment with nothing to give signals that the conversation is a monologue, not a dialogue. + +4. **The Similarity Trap.** Spending influence capital only on people who are already aligned. An influence network composed exclusively of allies is a mutual admiration society, not a source of organisational power. The most valuable influence relationships are with people who do not naturally agree with you. + +5. **Over-Engineering Commitment.** Attempting to engineer public, active, voluntary commitments in every conversation. Sometimes the appropriate influence move is patience -- allowing people to arrive at commitment on their own schedule. Forced commitments generate compliance, not conviction. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-as-sole-persuader | The founder is the company's primary influence mechanism. Every customer conversation, every hire, every investor meeting depends on the founder's personal persuasion. Building an influence network is less relevant; mastering one-on-one persuasion is critical. | +| Growth | Distributed influence | The leader can no longer personally persuade every stakeholder. The priority shifts to building an influence network, enlisting peer power, and engineering commitment systems that operate without the leader in the room. | +| Scale | Institutional influence | At scale, influence becomes cultural. The leader's task is to model the influence behaviours they want to see throughout the organisation -- transparency, compromise, room-reading -- so that persuasion capacity is distributed, not centralised. | + +--- + +## Output Template + +```markdown +# Influence Strategy: [Context] + +## Influence Network Assessment +| Person | What I Offer | What They Offer | Balance | Action Needed | +|--------|-------------|-----------------|---------|---------------| +| [Name] | [value] | [value] | [+/-/=] | [specific step] | + +## Room-Reading Plan +- Expected emotional temperature: [description] +- Adjustment triggers: [what signals will prompt a shift in approach] +- Pre-prepared compromises: [list 2-3 concessions] + +## Influence Sequence +1. Opening move: [specific language and approach] +2. Authority establishment: [how expertise will be woven in] +3. Peer power: [who will be enlisted and how] +4. Commitment mechanism: [what active, public, voluntary commitment to aim for] +5. Fallback: [if primary approach fails, what is the alternative] + +## Post-Interaction Review +- What worked: [observation] +- What to adjust: [observation] +- Relationship investment needed: [next step] +``` + +--- + +## Related Skills + +- **[Cialdini's Principles of Influence](../frameworks/cialdini-influence.md)** -- Provides the theoretical architecture (seven principles) that this skill applies to daily micro-moments; read Cialdini for the science, this skill for the practice. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation framework complements the ultimatum response and compromise strategies covered here. +- **[Carnegie's Win Friends](../frameworks/carnegie-win-friends.md)** -- Carnegie's interpersonal principles underpin the similarity and genuine connection tactics central to one-on-one influence. +- **[Trust Equation](../frameworks/trust-equation.md)** -- The trust equation diagnoses whether the relational foundation required for influence is intact; without trust, technique is futile. +- **[Influencing and Persuading](../people/influencing-and-persuading.md)** -- Provides the complementary people-focused influence techniques including Socratic persuasion and listening-based approaches drawn from different source material. +- **[Storytelling for Leaders](storytelling-for-leaders.md)** -- Narrative is the most potent vehicle for influence; stories deploy social proof and liking more effectively than abstract argument. diff --git a/plugins/foreman/content/skills/leadership/psychological-safety-practice.md b/plugins/foreman/content/skills/leadership/psychological-safety-practice.md new file mode 100644 index 0000000..718462a --- /dev/null +++ b/plugins/foreman/content/skills/leadership/psychological-safety-practice.md @@ -0,0 +1,210 @@ +--- +name: "psychological-safety-practice" +description: "Translates psychological safety theory into daily leader behaviours -- the specific words, reactions, and micro-actions that build or destroy a team's willingness to speak up. Covers misconceptions, responding to mistakes, inviting honest feedback, modelling healthy conflict, addressing bad behaviour immediately, and making mental health discussable. Use when meetings have gone quiet, when a post-mortem reveals that someone saw the failure coming but said nothing, when a leader suspects enforced politeness is masking dysfunction, or when feedback from direct reports has become vague and uninformative." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - psychological-safety + - trust + - feedback + - culture + - meetings + - conflict + - mental-health + - daily-practice +related_skills: + - psychological-safety + - emotional-intelligence + - radical-candor + - johari-window +author: "Fatih Guner" +--- + +# Psychological Safety in Practice + +DESTRUCTION SPEED. Psychological safety takes months of consistent behaviour to build and approximately four seconds to destroy. Those four seconds might sound like: "That's a stupid question." Or: a sigh and an eye-roll when a junior employee challenges an assumption. Or: publicly reassigning a project the day after someone reported a mistake. Or: nothing at all -- silence where acknowledgment was expected, indifference where curiosity was needed. The theoretical architecture of psychological safety -- Edmondson's research, Clark's four stages, Google's Project Aristotle -- is documented in the frameworks category of this system. What follows is not the theory. It is the practice: the specific behaviours, phrases, and micro-decisions that determine whether a team believes it is safe to take interpersonal risks. Theory explains why safety matters. Practice determines whether it exists. + +--- + +## The Framework + +### What Psychological Safety Is Not + +Two misconceptions corrode more safety initiatives than any deliberate act of hostility. + +**Misconception 1: Safety means niceness.** Polite workplaces can be psychologically dangerous. When courtesy functions as a silencing mechanism -- when "being professional" means never expressing disagreement -- the team operates in a state of enforced pleasantness that suppresses the candour safety requires. Psychological safety is not the absence of discomfort. It is the presence of permission to be uncomfortable productively. + +**Misconception 2: Safety means comfort.** Learning is uncomfortable. Admitting mistakes is uncomfortable. Pointing out that a senior leader's strategy has a flaw is uncomfortable. Psychological safety does not eliminate discomfort; it makes discomfort survivable. The question is not "does this feel easy?" but "will I be punished for being honest?" + +### The Seven Daily Practices + +**Practice 1: Set the Stage Before Every Meeting** + +Silence is the default human response in group settings. Overriding that default requires active setup -- not once, but repeatedly. Before discussions where input is needed: + +- Explain why every perspective matters for this specific decision. +- Name the specific risks of not hearing from the group (lower creativity, missed risks, weaker solutions). +- State explicitly that disagreement is welcome and expected. + +This is not a speech. It is two or three sentences. "Before we decide on the Q3 roadmap, I want to hear what concerns each of you has. The worst outcome is that we commit to something and discover three months from now that someone in this room saw the problem but didn't raise it." + +**Practice 2: Respond to Mistakes as Data** + +The moment a team member reports a mistake, the leader's reaction establishes or erases months of safety-building. The wrong response -- frustration, blame, even a visible sigh -- teaches the entire team that honesty is penalised. The right response follows a sequence: + +1. Thank the person for surfacing the issue. ("Thank you for catching this. What did you notice first?") +2. Ask diagnostic questions without assigning blame. ("What contributed to this? What would have prevented it?") +3. Focus on the system, not the individual. ("What do we need to change so this doesn't recur?") +4. Follow up visibly. If the mistake leads to a process improvement, credit the person who raised it. + +The fourth step is the one most leaders skip, and it is the most important. When the team sees that reporting a mistake led to a positive change -- and that the reporter was credited, not punished -- the behaviour propagates. + +**Practice 3: Invite Feedback on Yourself** + +Leaders who say "my door is always open" receive almost no honest feedback through that open door. The problem is structural: the power differential makes unsolicited upward feedback feel dangerous regardless of how welcoming the leader believes they are. + +Active solicitation requires specific questions: + +- "What did you hear when I shared my strategy?" (not "what did you think of my strategy?") +- "How did it feel when I sent that email?" (not "was my email clear?") +- "What is one thing I could do differently in these meetings?" + +When feedback arrives -- especially critical feedback -- the response protocol is: listen, do not defend, reflect, and thank. Any defensive reaction, however mild, teaches the giver that feedback was not actually wanted. Changes made in response to feedback should be visible and attributed: "Based on what several of you told me, I'm going to change how we run these reviews." + +**Practice 4: Address Bad Behaviour Immediately** + +Zero tolerance for blatant rudeness -- dismissing, steamrolling, using derogatory language -- is the structural foundation of safety. If bad behaviour goes unaddressed, the implicit message is that safety standards are aspirational rather than enforced. + +The intervention protocol: + +- Pull the person aside immediately (not tomorrow, not at the next one-on-one). +- Name the specific behaviour. ("When you interrupted Sarah and said her data was irrelevant, that is the behaviour I need to discuss.") +- Explain the impact. ("That signals to everyone in the room that challenging your position is not welcome.") +- State the expectation. ("In this team, we engage with ideas we disagree with. We do not dismiss the people presenting them.") +- Follow up to verify change. + +The calibration matters. This is not about policing tone or micromanaging interpersonal style. It is about maintaining the minimum conditions under which people will speak honestly. + +**Practice 5: Model Healthy Conflict** + +When a leader and a team member disagree, the rest of the team watches how the disagreement unfolds. If the leader shuts down the dissent -- through authority, through volume, through subtle dismissal -- the team learns that disagreement is tolerated only from peers, not directed upward. + +Modelling healthy conflict means: + +- Giving the dissenting person space to articulate their full position before responding. +- Acknowledging the merit in their argument explicitly, even if you ultimately disagree. +- Engaging in civil debate -- exchanging reasoning, not assertions. +- Accepting the outcome gracefully if the evidence supports the other position. + +The team does not need to see the leader lose arguments frequently. They need to see the leader engage with disagreement respectfully -- once or twice is enough to establish the norm. + +**Practice 6: Make Mental Health Discussable** + +Employees who struggle with mental health challenges need to be able to ask for help without fearing that their leader will view them differently. Two actions lower the barrier: + +- **Monitor language.** Comments like "Don't get all OCD on my spreadsheet" stigmatise conditions that team members may be managing. Address casual misuse of clinical terms when it occurs, and explain -- without lecturing -- why the language is harmful. +- **Know the resources.** Familiarise yourself with the company's mental health benefits, EAP programmes, and external referral options so you can point people to them naturally when the moment arises. The leader does not need to be a therapist. They need to be a credible connector. + +**Practice 7: Manage Your Own Vulnerability Boundaries** + +Opening up to a team builds connection. Oversharing erodes authority. The calibration: if you would not mind hearing the comment from your own boss, it is probably appropriate. "I'm having a rough day" humanises. "I had a terrible fight with my partner this morning" creates discomfort the team cannot productively address. Authenticity is not the same as transparency. Share enough to be human; retain enough to be leaderly. + +--- + +## Prompts + +**Prompt 1 -- Safety Diagnostic:** +> Here is how my team currently behaves in meetings: [describe -- who speaks, who stays silent, how disagreement is expressed or suppressed, what happens after mistakes]. Assess the current state of psychological safety using the seven daily practices as a checklist. Which practices are strong? Which are absent? Give me a specific 30-day plan to address the two weakest areas. + +**Prompt 2 -- Mistake Response Script:** +> A team member just reported a significant error: [describe the mistake and context]. Draft three versions of my response: one that destroys safety (so I can see what to avoid), one that maintains safety, and one that actively builds safety by turning the mistake into a learning moment. For the third version, include the follow-up actions I should take over the next week. + +**Prompt 3 -- Feedback Solicitation Design:** +> I suspect my team is not giving me honest feedback. Here is the evidence: [describe -- vague responses, silence in meetings, turnover patterns]. Design a feedback solicitation approach: specific questions I should ask, the setting in which I should ask them, how I should respond in the moment, and how I should communicate changes that result from the feedback. + +**Prompt 4 -- Bad Behaviour Intervention Script:** +> A team member did the following in a meeting: [describe the specific behaviour]. I need to address it immediately. Draft a conversation script that names the behaviour specifically, explains its impact on team safety, states the expectation clearly, and preserves the person's dignity. Include guidance on what to do if they become defensive. + +--- + +## Use Cases + +**Early-Traction Startup: Silence After a Product Failure** +A 15-person startup ships a feature that causes significant customer complaints. In the post-mortem, two engineers reveal they had concerns about the release timeline but did not raise them because "the CEO seemed really committed to the date." The CEO, who believed the team was fully aligned, realises that their enthusiasm was functioning as pressure. The intervention: the CEO begins every product discussion with "What concerns me is [specific risk]. What concerns you?" -- modelling vulnerability and explicitly inviting dissent. Within three months, pre-release concerns are surfaced regularly and the defect rate drops measurably. + +**Growth-Stage Company: The Polite Team That Never Disagrees** +A marketing team scores highly on employee satisfaction surveys but produces mediocre creative work. An external facilitator observes that the team is exceptionally polite -- and that this politeness functions as a silencing mechanism. No one challenges a campaign concept. No one says "this is not good enough." The team leader institutes Practice 5 (modelling healthy conflict) by publicly disagreeing with a creative brief in the next meeting, explaining their reasoning, inviting counterarguments, and changing their position based on what they hear. The shift is not immediate -- it takes six weeks -- but the quality of debate in creative reviews improves measurably, and the next campaign outperforms the previous three. + +**Scale-Stage Organisation: Rebuilding After a Trust Breach** +A department head publicly berated a junior analyst for an error in a board presentation. The incident was witnessed by eight people and discussed by forty. Psychological safety in the department collapsed within days: error reporting stopped, meeting participation became perfunctory, and two top performers began interviewing elsewhere. The VP intervening applies the full protocol: addresses the behaviour privately with the department head (Practice 4), holds a team meeting acknowledging that the incident violated team standards (Practice 1), solicits feedback from the team on what they need to feel safe again (Practice 3), and institutes a visible mistake-response protocol (Practice 2). Recovery takes four months -- roughly one hundred times longer than the four seconds it took to create the breach. + +--- + +## Anti-Patterns + +1. **Safety as a One-Time Initiative.** Announcing psychological safety as a team value in a single meeting and assuming it is now established. Safety is maintained through daily behavioural consistency, not through declarations. The moment behaviour contradicts the declaration, the declaration becomes evidence of hypocrisy. + +2. **Confusing Safety with Lowered Standards.** Believing that psychological safety means accepting poor performance without consequences. The opposite is true: safety enables honest performance conversations. A team that feels safe can hear "your work is not meeting the standard" without interpreting it as a personal attack. A team that does not feel safe cannot hear any feedback at all. + +3. **Soliciting Feedback and Then Punishing the Messenger.** The leader who asks for honest feedback, receives it, and then responds with defensiveness, cold-shouldering, or subtle retaliation. This is worse than never asking, because it teaches the team that the solicitation was performative. + +4. **Selective Enforcement.** Addressing bad behaviour from junior employees while tolerating it from senior performers or executives. If a top salesperson can dismiss a junior colleague's concerns with impunity, the team learns that safety is contingent on status -- which means it does not exist. + +5. **Over-Sharing as Safety-Building.** A leader who shares every anxiety, frustration, and personal struggle with the team in the name of vulnerability. This is not safety-building; it is emotional burden-shifting. The team needs to see their leader as human. They do not need to manage their leader's emotional state. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder behaviour as culture code | In a small team, the founder's every reaction to mistakes, disagreement, and feedback establishes the psychological safety baseline for the entire company. There are no policies to hide behind. The founder's behaviour is the policy. | +| Growth | Scaling safety through middle management | The founder can no longer be present in every meeting. Psychological safety depends on whether middle managers replicate the founder's safety-building behaviours or introduce their own patterns. Training managers in the seven practices is not optional -- it is a growth prerequisite. | +| Scale | Institutional safety mechanisms | Safety must survive leader transitions, team reorganisations, and cultural dilution from rapid hiring. This requires codified norms (how we respond to mistakes, how we run post-mortems, how we handle bad behaviour) that operate independently of any individual leader's personality. | + +--- + +## Output Template + +```markdown +# Psychological Safety Assessment: [Team / Department] + +## Current State +- Meeting participation pattern: [who speaks, who is silent] +- Last reported mistake: [when, how it was handled, what happened next] +- Feedback quality: [specific and actionable vs. vague and safe] +- Recent conflict: [how it was resolved, or how it was avoided] + +## Practice Scorecard +| Practice | Status | Evidence | Priority Action | +|----------|--------|----------|-----------------| +| Stage-setting before meetings | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Mistake response | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Feedback solicitation | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Bad behaviour enforcement | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Healthy conflict modelling | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Mental health openness | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Vulnerability calibration | [Strong/Weak/Absent] | [specific observation] | [specific action] | + +## 30-Day Plan +1. Week 1: [specific action targeting the weakest practice] +2. Week 2: [specific action] +3. Week 3: [specific action] +4. Week 4: [assessment and adjustment] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Edmondson's framework and Clark's four stages provide the theoretical foundation; this skill provides the daily behaviours and specific language that translate that theory into practice. +- **[Radical Candor](../frameworks/radical-candor.md)** -- Scott's framework for caring personally while challenging directly describes the communication style that psychological safety enables. +- **[Johari Window](../frameworks/johari-window.md)** -- The Johari model maps the relationship between self-disclosure and feedback; psychological safety determines whether the feedback quadrant expands or contracts over time. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- The self-regulation and empathy dimensions of emotional intelligence are the personal capabilities that enable a leader to execute the seven daily practices consistently under stress. +- **[Emotional Courage](emotional-courage.md)** -- The leader's willingness to model vulnerability and raise difficult issues is the primary behaviour that creates safety for the team to do the same. +- **[Inclusive Leadership](inclusive-leadership.md)** -- Psychological safety is not distributed equally; inclusion practices address the specific barriers that prevent underrepresented team members from experiencing the safety the leader intends. diff --git a/plugins/foreman/content/skills/leadership/purpose-driven-leadership.md b/plugins/foreman/content/skills/leadership/purpose-driven-leadership.md new file mode 100644 index 0000000..4949cdf --- /dev/null +++ b/plugins/foreman/content/skills/leadership/purpose-driven-leadership.md @@ -0,0 +1,193 @@ +--- +name: "purpose-driven-leadership" +description: "Helps leaders connect their work and their teams' work to authentic meaning, rethink outdated notions of dedication, anchor in purpose over perception, and lead with integrity as a continuous practice. Use when experiencing career malaise or questioning professional direction, noticing disengagement on a team, struggling to articulate why the work matters, preparing to realign team priorities around meaning, or sensing that performance metrics have crowded out purpose." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - purpose + - meaning + - authenticity + - dedication + - integrity + - motivation + - work-life + - values +related_skills: + - emotional-intelligence + - maslow-hierarchy + - covey-seven-habits + - emotional-courage + - humility-and-power +author: "Fatih Guner" +--- + +# Purpose-Driven Leadership + +At a funeral, no one reads the quarterly performance review. The eulogy test -- what would your team say you stood for? -- exposes a gap that most leaders spend entire careers avoiding. Not a gap in competence or results, but in meaning. Organisations are saturated with mission statements, value propositions, and strategic visions, yet the question "Why does this work matter?" remains surprisingly difficult for most leaders to answer with conviction. Purpose-driven leadership is not a motivational overlay applied to an otherwise mechanical job. It is the structural foundation that determines whether people bring discretionary effort or merely their contractual minimum. + +--- + +## The Framework + +### Dimension 1: Rethinking Dedication + +The industrial model of dedication -- measured in hours at the desk, weekends sacrificed, personal life deferred -- is obsolete. People no longer settle for jobs that consume their lives, and leaders who cling to this standard risk losing their best talent to organisations that have already moved on. + +Rethinking dedication requires three shifts: + +**Disconnect performance from time.** If work is getting done well, the number of hours spent should be irrelevant. A leader who equates presence with productivity is optimising for the wrong metric. The shift is from "How long did you work?" to "What did you produce?" + +**Expand the definition of ambition.** Ambition is not synonymous with career obsession. An employee who wants to excel at work and coach their child's football team is not less ambitious than one who works until midnight. They are pursuing a more complex ambition -- and one that, if supported, produces sustainable performance rather than burnout. + +**Release the standards of your own early career.** The conditions under which today's leaders came up are not the conditions they should impose. "I worked 80-hour weeks as a junior analyst" is biography, not policy. Every generation renegotiates the terms of professional dedication; resisting this renegotiation is a retention strategy for mediocrity. + +### Dimension 2: Making Purpose Felt, Not Declared + +Purpose is a feeling, not a statement. A mission printed on the conference room wall is inert. Purpose becomes operative when people experience the impact of their work -- when they feel it in the specificity of a customer's gratitude, the tangible improvement in someone's life, or the visible consequence of a problem solved. + +**Two principles for activating purpose:** + +**Show, don't tell.** Customer testimonials, site visits, direct conversations between engineers and the users of their products -- these create visceral connections between effort and impact. Telling a team their work is important triggers compliance at best and cynicism at worst. Showing them produces engagement. + +**Authenticity is non-negotiable.** If purpose rhetoric does not align with a leader's historical behaviour, it backfires. A leader who spent years emphasising quarterly profits cannot suddenly pivot to heartfelt speeches about customer impact without provoking suspicion. Authenticity in purpose-driven leadership is built over time through consistent alignment between words and actions. It cannot be manufactured in a single all-hands meeting. + +### Dimension 3: Purpose Over Perception + +A particularly corrosive form of purposelessness emerges when leaders begin managing perceptions rather than pursuing outcomes. The energy spent on appearing competent, appearing decisive, appearing dedicated is energy diverted from actually being those things. + +This trap is especially acute for leaders navigating identity-based expectations. Research on women in leadership, for instance, reveals that managing the perception of femininity -- softening here, hardening there, striking some elusive balance -- consumes time and cognitive resources that could be directed toward shared goals. The remedy is not to ignore perception entirely but to anchor in purpose so firmly that behaviour flows from conviction rather than from image management. + +Anchoring in purpose enables leaders to ask a more productive question: "Who do I need to be and what do I need to learn to achieve these goals?" rather than "How do I need to appear?" + +### Dimension 4: The Work-Life Equation + +Purpose extends beyond the office. Leaders who have no life outside work are not more dedicated; they are more fragile. A career that cannot coexist with personal fulfilment is unsustainable -- not in the abstract sense of "wellness culture" but in the concrete sense that it produces diminishing returns, impaired judgment, and eventual collapse. + +Taking stock requires honest inventory: + +- What do you want your days to look like -- not just your career trajectory? +- Ten years from now, what will you regret not having done or learned? +- Does your current path support the life you want, or only the career you think you should want? + +These are not soft questions. They are strategic ones. A leader operating from a place of personal clarity makes better decisions, models sustainable behaviour for their team, and avoids the slow erosion that turns high performers into hollow ones. + +### Dimension 5: Integrity as Ongoing Practice + +Integrity is not a credential earned once. It is a practice maintained daily and compromised incrementally. Leaders are role models whether they intend to be or not. Cutting corners, flouting rules, or ignoring top performers' bad behaviour grants permission for the entire organisation to do the same. + +The inverse is equally true. Leading with integrity -- consistently, visibly, especially when it is inconvenient -- creates a culture where ethical behaviour is the default rather than the exception. Customers, who increasingly care about how companies do business, respond to this signal. Employees, who watch their leaders more closely than leaders imagine, respond to it even more. + +Your life story is part of this equation. Authentic leadership draws on the full arc of experience -- mentors and micromanagers, promotions and layoffs, triumphs and humiliations. Leaders who understand where they come from, who can integrate their hardships into a coherent sense of purpose, are better equipped to lead with the kind of integrity that withstands pressure. + +--- + +## Prompts + +**Prompt 1 -- Purpose Audit:** +> Help me articulate my leadership purpose. My role is [describe], my team does [describe], and our organisation's mission is [describe]. I find meaning in [describe what energises you]. Walk me through a structured process to connect my daily work to a purpose statement that is honest, specific, and motivating -- not a generic mission statement but a personal conviction I can use as a decision-making filter. + +**Prompt 2 -- Team Purpose Activation:** +> My team of [size] seems disengaged. They do competent work but lack energy and initiative. I want to help them feel purpose in their work without resorting to motivational speeches that will trigger cynicism. Based on our work [describe what the team does and who it serves], suggest specific, concrete ways to make the impact of their work visible and felt -- not declared. + +**Prompt 3 -- Dedication Reset:** +> I suspect I am holding my team to outdated standards of dedication. The symptoms include [describe -- e.g., judging people who leave at 5 PM, feeling resentful when direct reports take full vacations, equating enthusiasm with long hours]. Help me redesign my mental model of dedication around output and impact rather than time and presence. Include specific behavioural changes I can make starting this week. + +**Prompt 4 -- Life-Work Alignment Check:** +> I am [X] years into my career. Help me conduct a life-work alignment audit. Ask me questions about what I want my days to look like, what I would regret not doing, and whether my current path supports the life I want. Then identify the gaps and suggest realistic adjustments -- not a dramatic career change, but shifts that move me closer to alignment. + +--- + +## Use Cases + +**Idea-Stage Founder Reconnecting with Why** + +A technical founder has spent eighteen months building a product and has lost sight of why they started. The daily reality is code reviews, investor updates, and hiring struggles. Purpose has been displaced by process. The founder applies the ten-year regret question and realises that what drew them to this problem -- a personal experience with the inefficiency they are solving -- has been buried under operational noise. They institute a monthly "customer story" session where the team hears directly from users. The founder's own energy returns, and the team -- previously executing without conviction -- begins to understand who they are building for and why it matters. + +**Growth-Stage Company with a Dedication Problem** + +A fast-growing consultancy has a cultural norm of 60-hour weeks, inherited from its founding partners. New hires tolerate it; experienced staff leave. Exit interviews consistently cite "unsustainable pace" as the primary reason for departure. The managing partner applies the dedication rethink: disconnecting performance evaluation from hours logged, explicitly endorsing flexible schedules for high performers, and publicly acknowledging that the partners' own early-career sacrifices were choices, not requirements. Within a year, attrition drops by 30% and billable output per person actually increases -- because people working sustainable hours make fewer mistakes and require less rework. + +**Scale-Stage Executive Facing an Integrity Test** + +A division president discovers that a top-performing sales director has been misrepresenting product capabilities to close deals. The short-term cost of intervention is significant: the sales director's accounts represent 15% of division revenue. The president applies the integrity-as-practice principle and terminates the sales director, communicating the reason transparently to the broader sales team. Short-term revenue dips. Long-term, the team's customer relationships improve as trust builds, and two previously silent team members report other issues they had been afraid to raise. The integrity signal cascades. + +--- + +## Anti-Patterns + +1. **Purpose as performance.** Crafting a personal purpose statement for LinkedIn or the company website without actually using it to make decisions. Purpose that does not influence behaviour is decoration. + +2. **Confusing purpose with passion.** Not every day feels meaningful. Purpose is a direction, not a mood. Leaders who expect to feel inspired every morning are confusing purpose with passion -- and will abandon purpose the first time it feels boring. + +3. **Imposing your purpose on your team.** A leader's personal sense of meaning does not automatically transfer to direct reports. Helping people find purpose means showing them impact and giving them autonomy to connect their own motivations to the work -- not lecturing them about why they should care. + +4. **The martyrdom trap.** Equating suffering with purpose. Working through illness, missing family milestones, and sacrificing health are not evidence of dedication; they are evidence of a broken relationship with work. Purpose-driven leaders sustain themselves because they intend to be in the work for the long term. + +5. **Integrity as a convenient stance.** Championing integrity when it costs nothing and abandoning it when it threatens revenue, relationships, or reputation. Integrity that bends under pressure is not integrity; it is risk management. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal purpose clarity | The founder's "why" is the company's "why" at this stage. If the founder cannot articulate purpose beyond "I want to build a company," the venture lacks a foundation for culture. | +| Validation | Purpose as a hiring signal | Early employees join for the mission, not the salary. Articulating purpose authentically is the most powerful recruiting tool at this stage. | +| Early Traction | Making purpose tangible for the first team | The transition from founder's vision to shared conviction happens here. Customer stories, impact metrics, and visible connections between effort and outcome are critical. | +| Growth | Scaling purpose without diluting it | New hires join who did not experience the founding story. Purpose must be embedded in onboarding, rituals, and decision-making frameworks rather than relying on oral tradition. | +| Scale | Integrity under institutional pressure | At scale, the pressures to compromise -- on ethics, on work-life standards, on stated values -- intensify. Purpose must be defended as deliberately as revenue targets are pursued. | + +--- + +## Output Template + +```markdown +# Purpose-Driven Leadership Assessment + +## Personal Purpose Statement +- **Core conviction:** [What you stand for as a leader -- one sentence] +- **Evidence of alignment:** [Three recent decisions that reflected this purpose] +- **Evidence of misalignment:** [Three recent decisions that contradicted it] + +## Team Purpose Health +| Indicator | Current State | Desired State | +|-----------|--------------|---------------| +| Can team members articulate why their work matters? | [Yes/Partially/No] | [Target] | +| Do team members experience the impact of their work directly? | [How often and how] | [Target] | +| Is purpose reflected in how work is assigned and evaluated? | [Description] | [Target] | + +## Dedication Model +- **Current model:** [Time-based / Output-based / Hybrid] +- **Symptoms of outdated standards:** [List specific behaviours] +- **Changes to implement:** [Specific shifts] + +## Integrity Audit +- **Last time integrity was tested:** [Describe the situation] +- **Response:** [What happened] +- **What it signalled to the organisation:** [Honest assessment] + +## Life-Work Alignment +- **What I want my days to look like:** [Description] +- **What my days actually look like:** [Description] +- **Gaps:** [Specific misalignments] +- **Adjustments:** [Realistic changes] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Self-awareness and empathy are preconditions for purpose-driven leadership; a leader who does not understand their own motivations cannot authentically connect others to meaning. +- **[Maslow's Hierarchy](../frameworks/maslow-hierarchy.md)** -- Purpose operates at the self-actualisation level; it becomes accessible only after lower-order needs (safety, belonging, esteem) are met. +- **[Covey's Seven Habits](../frameworks/covey-seven-habits.md)** -- "Begin with the end in mind" is the habit-level expression of purpose-driven leadership; Covey's framework provides the personal discipline structure that sustains purpose. +- **[Emotional Courage](emotional-courage.md)** -- Living with integrity and anchoring in purpose when it is costly requires emotional courage that must be developed deliberately. +- **[Humility and Power](humility-and-power.md)** -- Purpose without humility becomes messianism; the two disciplines are natural counterweights. +- **[Stoic Duty and Service](../stoic/stoic-duty-and-service.md)** -- The Stoic concept of duty as service provides the philosophical foundation for leading with purpose beyond personal ambition. +- **[AI Purpose-Driven Questions](../ai-leadership/ai-purpose-driven-questions.md)** -- Applies purpose-driven leadership specifically to AI adoption, ensuring technology decisions are guided by values rather than novelty. diff --git a/plugins/foreman/content/skills/leadership/senior-leadership-transition.md b/plugins/foreman/content/skills/leadership/senior-leadership-transition.md new file mode 100644 index 0000000..fe8430e --- /dev/null +++ b/plugins/foreman/content/skills/leadership/senior-leadership-transition.md @@ -0,0 +1,188 @@ +--- +name: "senior-leadership-transition" +description: "Guides leaders through the identity shift required when moving from functional management to enterprise leadership. Covers the seven role transformations (agenda setter, integrator, strategist, architect, diplomat, role model, successor builder), leading former peers, succession planning, and the mental recalibration that separates executives from promoted managers. Use when preparing for a C-suite role, navigating the first 90 days as VP or above, managing former peers, planning leadership succession, or coaching newly promoted executives." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - executive-transition + - succession-planning + - leadership-identity + - peer-to-boss + - senior-leadership + - promotion + - role-change +related_skills: + - leadership-style-adaptation + - leader-self-reflection + - leadership-voice-and-presence + - leadership-pipeline + - situational-leadership + - emotional-intelligence +author: "Fatih Guner" +--- + +# Senior Leadership Transition + +Yesterday you were the person who solved problems. Today you are the person who decides which problems are worth solving. This is not a promotion. It is an identity transplant. + +The individual contributor builds expertise in depth. The functional manager orchestrates that expertise across a team. The enterprise leader does something categorically different: they set the agenda for an entire organisation, integrate knowledge they do not personally possess, and shape systems they cannot directly control. Research from Spencer Stuart identifies three transitions that derail even accomplished leaders -- becoming a leader for the first time, leading organisational transformation, and reaching the top after years of striving toward it. The common thread is that each demands a fundamentally different version of the person who occupied the previous role. Skills that earned the promotion are necessary but insufficient; the mental shifts required are what separate executives who thrive from those who plateau with a better title. + +--- + +## The Practice + +### The Seven Role Transformations + +Moving from functional leadership to enterprise leadership requires simultaneous shifts across multiple dimensions. These are not sequential stages; they occur in parallel, and neglecting any one of them creates blind spots. + +**1. Agenda Setter** +The functional leader fixes problems handed to them. The enterprise leader decides which problems the organisation tackles at all. This requires surrendering the satisfaction of personal problem-solving in favour of prioritisation, delegation, and the disciplined use of planning processes to define organisational goals. + +**2. Integrator** +Functional leaders cultivate analytical depth within a domain. Enterprise leaders integrate the collective knowledge of teams whose domains they may barely understand. The critical skills: grasping competing issues, making trade-offs between legitimate but conflicting priorities, and articulating the rationale behind those trade-offs so that every function feels heard even when the decision goes against them. + +**3. Strategist** +Tactical results are concrete and immediate; strategic outcomes are abstract and delayed. The enterprise leader must resist the seduction of the tactical. Three capabilities matter: toggling fluently between operational detail and strategic perspective, recognising patterns in complex environments, and anticipating how external parties -- competitors, regulators, media -- will respond to organisational decisions. + +**4. Architect** +The enterprise leader thinks in systems, not job descriptions. Changing one element of the organisation -- a reporting structure, a compensation model, a process -- inevitably affects others. Organisational design becomes a primary responsibility, and the leader who lacks fluency in change management will produce cascading unintended consequences. + +**5. Diplomat** +The functional leader defeats competitors. The enterprise leader also manages internal stakeholders -- other senior leaders, business units, and the board -- whose priorities may conflict with one another. Negotiation, persuasion, and alliance-building replace command-and-control as primary instruments. + +**6. Role Model** +At the enterprise level, every word and gesture is amplified. Employees take cues about "right" behaviours from how the senior leader conducts themselves. Self-awareness and empathy become operational requirements, not personality traits. + +**7. Successor Builder** +The goal of leadership, paradoxically, is to make yourself replaceable. Identifying potential successors, assigning stretch projects, and building the leadership pipeline is not a retirement exercise -- it begins the moment you assume the role. Flawed succession processes destroy close to $1 trillion annually in S&P 1500 market value. + +### Leading Former Peers + +When you become the boss of people who were your equals last week, the temptation is to prove yourself through immediate action. Resist it. Build credibility first by meeting people individually and as a team. Listen as much as you talk. Explain how you intend to lead and ask how you can help your new direct reports succeed. The goal is buy-in before strategy -- because strategy without trust is a memo nobody follows. + +If your predecessor was a star, do not attempt to replicate their personality. Being unapologetically yourself -- while being transparent about how your approach will differ -- earns more respect than imitation. + +### The Mental Architecture of Executive Leadership + +The shift is not merely about what you do; it is about how you think. Identify and communicate your core values. Learn to compartmentalise so that a crisis in one domain does not contaminate your judgment in another. Expand self-awareness by paying attention to the narratives you construct about your own career -- the stories you tell yourself about successes and failures shape the leader you become. + +--- + +## Prompts + +**Prompt 1 -- Transition Self-Assessment:** +> I am transitioning from [current role] to [new senior role]. Using the seven role transformations (agenda setter, integrator, strategist, architect, diplomat, role model, successor builder), assess which shifts I have already begun and which I am neglecting. My background is [describe functional expertise and management experience]. For each transformation, identify specific daily behaviours I should start, stop, and continue. Present this as a 90-day transition plan. + +**Prompt 2 -- Former Peer Navigation:** +> I have just been promoted to lead a team of [number] people who were my peers until [timeframe]. Describe the most common relationship dynamics that shift in this situation and design a communication plan for my first two weeks. Include: what to say in the initial team meeting, how to structure individual one-on-ones, and how to handle the colleague who wanted the role I received. + +**Prompt 3 -- Succession Pipeline Design:** +> My company of [size] people has no formal succession plan. Design a succession planning framework that addresses three levels: CEO succession, C-suite succession, and director-level succession. Include criteria for identifying high-potential candidates, development approaches (stretch assignments, rotations, mentoring), and a timeline for implementation. Factor in our current context: [describe industry, growth stage, and any imminent leadership gaps]. + +**Prompt 4 -- Mental Model Shift:** +> I have been in my enterprise leadership role for [duration] and I find myself still defaulting to [describe functional behaviour -- e.g., solving technical problems directly, managing individual contributor work]. Diagnose which of the seven role transformations I am stuck on, explain why my previous success makes this shift difficult, and prescribe specific habits and routines to accelerate the transition. + +--- + +## Use Cases + +**Growth-Stage Founder Moving from CTO to CEO** +A technical cofounder at a 60-person company has been serving as CTO while the board searches for a permanent CEO. The board offers the role to the cofounder. The challenge: every instinct developed over five years of technical leadership now works against them. They must shift from architect to agenda setter, from depth to breadth, from solving to prioritising. The transition plan focuses on the first 90 days: week one establishes the new communication cadence; weeks two through four involve structured listening sessions with every department head; month two introduces the new strategic planning process; month three delivers the first company-wide strategic narrative -- the moment the engineer becomes the enterprise leader. + +**Scale-Stage VP Inheriting a Team of Former Peers** +A VP of Product at a 300-person company is promoted to SVP after the previous leader departs. Three of their four direct reports applied for the same role. The new SVP resists the urge to immediately restructure. Instead, they schedule unhurried one-on-ones with each direct report, opening each conversation by asking: "What do you need from me to succeed?" They are transparent about their leadership approach, acknowledge the awkwardness of the transition, and commit to a feedback rhythm that ensures no one feels blindsided. The colleague who most wanted the role receives a stretch assignment that signals investment, not consolation. + +**Late-Stage Company with No Succession Plan** +A 500-person company's founding CEO announces a two-year retirement timeline. The board has no succession plan. Applying the successor-builder framework, the board immediately begins monitoring the leadership pipeline. Two internal candidates are identified at the C-suite level; a third promising leader at the VP level receives rotational exposure to functions outside their domain. External candidates are benchmarked but not prioritised -- research indicates that outsider CEOs at already-performing companies destroy more value than they create. + +--- + +## Anti-Patterns + +1. **The Hero's Return.** Newly promoted leaders who continue solving problems personally rather than setting agendas and delegating. The rush of direct contribution is addictive -- and organisationally destructive. Every problem you solve is a development opportunity you stole from someone else. + +2. **The Loyalty Test.** Leaders who, upon promotion, immediately restructure teams to surround themselves with allies. This signals insecurity, not strength, and alienates the very people whose institutional knowledge you need most. + +3. **The Deferred Succession.** Treating succession planning as a pre-retirement activity rather than a day-one responsibility. Companies that begin succession planning only when a departure is imminent pay a premium in disruption, talent loss, and value destruction. + +4. **The Strategy Vacation.** Senior leaders who remain perpetually tactical because strategic thinking feels abstract and unrewarding. The seduction of concrete results must be actively resisted -- no one else in the organisation has the mandate to do the strategic work. + +5. **The Replica.** Attempting to clone the style of a successful predecessor. Authenticity outperforms imitation every time, and the organisation needs what you bring, not a diminished copy of what came before. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder to manager | The first leadership transition: from doing everything to delegating anything. The mental shift from "I can do it better" to "someone else must learn to do it" determines whether the company survives beyond the founder's personal capacity. | +| Growth | Functional to enterprise | The critical transition this skill addresses. Leaders must shed functional identity and adopt systems thinking. The most common failure: promoting the best functional performer into a role that requires entirely different capabilities. | +| Scale | Executive to board-level | At scale, the transition extends to board governance, investor relations, and public representation. The leader becomes diplomat and role model at an institutional scale, where every offhand remark is a signal. | + +--- + +## Output Template + +```markdown +# Leadership Transition Plan + +**Leader:** [Name] +**Transition:** [From Role] to [To Role] +**Date:** [Date] +**Timeline:** [90-day / 6-month] + +## Role Transformation Assessment + +| Transformation | Current Readiness | Key Gap | Priority Action | +|---------------|-------------------|---------|-----------------| +| Agenda Setter | [Low/Medium/High] | [Gap] | [Action] | +| Integrator | [Low/Medium/High] | [Gap] | [Action] | +| Strategist | [Low/Medium/High] | [Gap] | [Action] | +| Architect | [Low/Medium/High] | [Gap] | [Action] | +| Diplomat | [Low/Medium/High] | [Gap] | [Action] | +| Role Model | [Low/Medium/High] | [Gap] | [Action] | +| Successor Builder | [Low/Medium/High] | [Gap] | [Action] | + +## 90-Day Plan + +### Month 1: Listen and Learn +- [Stakeholder meetings scheduled] +- [One-on-one cadence established] +- [Key relationships to build] + +### Month 2: Align and Prioritise +- [Strategic priorities communicated] +- [Quick wins identified] +- [Team structure decisions] + +### Month 3: Execute and Signal +- [First strategic initiative launched] +- [Feedback loop established] +- [Succession pipeline review initiated] + +## Former Peer Dynamics +| Person | Relationship Risk | Approach | +|--------|-------------------|----------| +| [Name] | [Risk] | [Strategy] | + +## Succession Pipeline Status +| Role | Internal Candidates | Development Needed | Timeline | +|------|--------------------|--------------------|----------| +| [Role] | [Names] | [Gaps] | [Months] | +``` + +--- + +## Related Skills + +- **[Leadership Pipeline](../frameworks/leadership-pipeline.md)** -- Provides the theoretical model for leadership passages; this skill translates those passages into daily transition practices. +- **[Leadership Style Adaptation](leadership-style-adaptation.md)** -- The transition to senior leadership often requires abandoning a default style that worked at the previous level. +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The mental shifts required during transition depend on structured introspection practices covered in this companion skill. +- **[Leadership Voice and Presence](leadership-voice-and-presence.md)** -- Senior leaders must develop a new voice -- one that communicates values and vision rather than functional expertise. +- **[Career Strategy for Leaders](career-strategy-for-leaders.md)** -- The career fuel audit and success trap identification are directly relevant to the identity recalibration that senior transitions demand. +- **[Strategic Thinking and Alignment](strategic-thinking-and-alignment.md)** -- The shift from operational execution to strategic oversight is the central challenge of senior transitions; this skill provides the daily habits for operating at strategic altitude. diff --git a/plugins/foreman/content/skills/leadership/storytelling-for-leaders.md b/plugins/foreman/content/skills/leadership/storytelling-for-leaders.md new file mode 100644 index 0000000..f049fe8 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/storytelling-for-leaders.md @@ -0,0 +1,174 @@ +--- +name: "storytelling-for-leaders" +description: "Equips leaders with practical storytelling techniques for driving organisational change, building empathy, simplifying complexity, and creating shared narratives. Use when launching a transformation initiative, when data alone fails to persuade, when teams need emotional alignment around a vision, or when a leader's communication is technically sound but fails to move people." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - communication + - change-management + - persuasion + - narrative + - empathy + - vision +related_skills: + - leading-through-change + - kotter-change-model + - cialdini-influence + - radical-candor + - inclusive-leadership +author: "Fatih Guner" +--- + +# Storytelling for Leaders + +In 2008, Howard Schultz returned to a Starbucks that had lost its way. The company had over-expanded, commoditised its experience, and watched same-store sales decline for the first time in its history. Schultz did not begin his turnaround with a strategy deck. He began with a story. He described walking into a Starbucks in Los Angeles and noticing that the store smelled like burnt cheese from the new breakfast sandwiches -- not coffee. That single sensory detail carried more persuasive weight than any financial analysis could have. It told every employee, investor, and customer exactly what had gone wrong and, by implication, what "right" would look like. The breakfast sandwiches were pulled within weeks. The story preceded the strategy, and the strategy succeeded because the story made the problem visceral. + +This is not an accident. Humans evolved to process narrative before they developed the capacity for abstract reasoning. A well-constructed story activates neural coupling -- the listener's brain begins to mirror the storyteller's -- in ways that bullet points and bar charts cannot. Leaders who understand this do not treat storytelling as a soft skill bolted onto "real" leadership. They treat it as the primary vehicle through which meaning travels inside organisations. + +--- + +## The Framework + +### The Four Functions of Change Stories + +Frances Frei and Anne Morriss identify four things that effective change stories accomplish. Each addresses a different psychological need in the audience. + +**1. Provide a Mandate for Change** + +Every transformation story must answer: why now? The mandate is not a vague sense that things could be better. It is a specific articulation of the problem being solved and the cost of inaction. The cost should be concrete -- lost customers, eroding margins, talent departing -- not abstract ("we need to innovate"). Crucially, the mandate must be persuasive enough to override the gravitational comfort of familiar behaviours. People will tolerate considerable pain if the alternative is uncertainty; the mandate must make inaction more frightening than change. + +**2. Honour the Past** + +Change stories that dismiss history alienate the people who built the current organisation. The most effective narratives acknowledge what was built well, name the human cost of past mistakes honestly, and distinguish what must change from what should endure. A leader who says "everything before me was wrong" loses credibility with anyone who invested years in the previous era. A leader who says "we built something remarkable, and the world has shifted in ways that require us to evolve" earns permission to lead the evolution. + +**3. Understand Deeply, Describe Simply** + +If a vision can only be articulated in jargon, it has not been thought through. Frei and Morriss propose a compression test: Can you capture the change in a page? A paragraph? A single word? Simplicity is not a concession to unsophisticated audiences -- it is proof of intellectual clarity. The leader who can explain a complex transformation in language a new hire understands has done the harder cognitive work. + +**4. Describe a Rigorous, Optimistic Way Forward** + +The forward-looking portion of the story requires both data and enthusiasm. A few -- only a few -- data points serve as plot points, providing rigour. Optimism provides fuel. This is not naivete; it is the leader's genuine conviction that the plan will work, communicated with enough energy to be contagious. Sceptics will not be converted by optimism alone, but without it, even the best plan feels like an assignment rather than an adventure. + +### Personal Storytelling as Leadership Infrastructure + +Julie Battilana and Tiziana Casciaro's research on power and empathy reveals a complementary function of storytelling: building the relational connective tissue that makes authority legitimate. When leaders invite employees at all levels to share stories about their work, challenges, and perspectives, two things happen. The leader gains information that formal reporting channels filter out. And employees gain the felt experience of being heard, which strengthens trust and engagement. + +The practice is deceptively simple. A monthly session in which three or four employees share a five-minute story about a recent challenge or success -- with the leader listening, not evaluating -- creates more empathy than a year of engagement surveys. + +--- + +## Prompts + +**Prompt 1 -- Change Story Construction:** +> I am leading a significant change: [describe the change, its rationale, and its expected impact]. Using Frei and Morriss's four-function framework (mandate, honour the past, simplify, describe the way forward), draft a narrative I can deliver in five minutes to my full team. Include one concrete sensory detail, one data point, and one explicit acknowledgement of what we have done well and should preserve. + +**Prompt 2 -- Simplification Stress Test:** +> Here is my current explanation of our strategic direction: [paste existing explanation]. Compress it to: (a) one page, (b) one paragraph, (c) one sentence, (d) one word. At each level, tell me what I lost and whether it matters. Identify any jargon that would confuse a new hire. + +**Prompt 3 -- Personal Story Mining:** +> I want to use personal storytelling to build empathy with my team, but I am unsure which experiences are appropriate to share. Here are five significant moments from my career: [describe them briefly]. For each, assess: (a) does it reveal vulnerability without undermining authority? (b) does it connect to a lesson relevant to the team's current situation? (c) is it specific enough to be memorable? Recommend which to use and how to frame it. + +**Prompt 4 -- Story-Driven Presentation Redesign:** +> I have a data-heavy presentation: [describe the content and audience]. Restructure it as a narrative arc: opening hook, rising tension (the problem), turning point (the insight), resolution (the plan), and call to action. Integrate the most important data points as plot elements rather than slide decorations. Keep it under 15 minutes. + +--- + +## Use Cases + +**Early-traction founder pitching a pivot to investors** + +A SaaS startup has spent 18 months building a product for enterprise clients, only to discover that mid-market companies adopt faster and churn less. The founder needs to explain the pivot to existing investors who backed the enterprise thesis. Rather than leading with revised financial projections, the founder opens with a story: a specific mid-market customer who went from first demo to signed contract in eleven days, versus the enterprise prospect who has been "evaluating" for nine months. The story makes the strategic shift self-evident. Projections follow as confirmation, not persuasion. + +**Growth-stage CEO rallying a demoralised team after layoffs** + +A company that grew from 80 to 300 people in two years has been forced to lay off 60 employees following a market contraction. Survivors are anxious, guilty, and disengaged. The CEO resists the temptation to skip directly to "here is our new strategy" and instead begins with a story that honours what the departed colleagues built. She names three specific contributions from laid-off team members, acknowledges the human cost plainly, and then describes -- in vivid, concrete terms -- what the leaner company can now do that the bloated one could not. The forward story is not about cost-cutting; it is about focus. + +**Scale-stage leader aligning a cross-functional team** + +A 1,000-person company launches a cross-functional initiative that requires engineering, marketing, and operations to collaborate in ways they never have. The programme leader discovers that each function has a different mental model of what success looks like. Rather than distributing a project charter, the leader hosts a story-sharing session: each function's representative tells a two-minute story about a time their team solved a problem they were proud of. The stories reveal shared values -- quality, speed, customer obsession -- that become the foundation for a unified narrative. + +--- + +## Anti-Patterns + +**1. Stories without substance.** A compelling narrative wrapped around a weak strategy is manipulation, not leadership. If the data does not support the story's claims, the audience will eventually discover the gap, and trust will collapse. Story amplifies strategy; it does not replace it. + +**2. The leader as perpetual hero.** When every story the leader tells features themselves overcoming adversity, the audience learns that the leader's ego, not the team's mission, is the point. The most effective leadership stories feature other people, or feature the leader in a moment of uncertainty or failure. + +**3. Honouring the past insincerely.** A perfunctory "we have a proud history" followed by "but everything must change" reads as dismissal in a thin disguise. If the acknowledgement does not name specific achievements and specific people, it will be perceived as cynical. + +**4. Over-simplifying to the point of distortion.** The compression test is a tool for clarity, not for eliminating nuance. A one-word summary that misrepresents the strategy is worse than a paragraph that captures it accurately. Simplicity should never sacrifice truth. + +**5. Storytelling as a one-time event.** A single powerful narrative at a town hall does not sustain a multi-year transformation. Effective leaders tell the story repeatedly, adapting it as circumstances change, and invite others to tell their own versions of it. The story must be a living document, not a keynote. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Origin story, founder narrative | The story IS the company; investors and early hires buy the narrative before the product | +| Early Traction | Pivot stories, customer stories | Stories shift from "why we exist" to "why we are changing" | +| Growth | Culture stories, alignment narratives | Stories must scale beyond the founder's voice; equip managers to tell them | +| Scale | Institutional narrative, legacy stories | The organisation needs a story that outlives any individual leader | + +At validation, the founder's personal story and the company's story are functionally identical. The pitch deck is a story. The hiring conversation is a story. The ability to articulate a compelling "why" in 60 seconds may be the single most valuable skill at this stage. + +At growth, the critical challenge is narrative distribution. When the founder was the only storyteller, consistency was automatic. With 50 or 200 people, the story must be simple enough for every manager to tell accurately while being rich enough to remain meaningful. Leaders at this stage invest in what might be called "story infrastructure": shared language, recurring story-sharing rituals, and explicit permission for team-level narratives that connect to the master narrative without being identical to it. + +--- + +## Output Template + +```markdown +# Change Narrative -- [Initiative Name] + +**Audience:** [Team / Investors / Board / All-hands] +**Duration:** [Target delivery time] +**Prepared by:** [Name] +**Date:** [Date] + +## 1. The Mandate (Why Now) +**The problem:** [Specific, concrete description] +**The cost of inaction:** [Quantified where possible] +**The sensory detail:** [One vivid, specific observation that makes the problem real] + +## 2. Honouring the Past +**What we built well:** [Specific achievements and people] +**What must be preserved:** [Values, practices, or capabilities to carry forward] +**Honest acknowledgement:** [What did not work, and what it cost] + +## 3. The Way Forward (Simplified) +**One word:** [The essence] +**One sentence:** [The thesis] +**One paragraph:** [The plan with enough detail to be credible] +**Key data point:** [One number that anchors the narrative] + +## 4. The Call to Action +**What changes immediately:** [Concrete first steps] +**What each person can do this week:** [Specific, actionable] +**What success looks like in 90 days:** [Measurable outcome] + +## Delivery Notes +- Open with: [The hook -- story, detail, or question] +- Close with: [The emotional resonance -- what this means for us] +- Anticipated questions: [Top 3 and prepared responses] +``` + +--- + +## Related Skills + +- **[Leading Through Change](leading-through-change.md)** -- Storytelling is the communication layer of change leadership; this companion skill covers the emotional and structural dimensions. +- **[Kotter's Change Model](../frameworks/kotter-change-model.md)** -- Kotter's "create a vision" and "communicate the vision" steps are precisely where storytelling operates within a structured change process. +- **[Story Structure and Arc](../storytelling/story-structure-and-arc.md)** -- Provides the five-second moment and But-and-Therefore momentum techniques that give leadership stories their narrative power. +- **[Finding Your Stories](../storytelling/finding-your-stories.md)** -- The Homework for Life discovery practice feeds directly into the personal narrative library that leaders draw from for change and empathy stories. +- **[Inclusive Leadership](inclusive-leadership.md)** -- Personal storytelling builds the empathy and connection that inclusive cultures depend on. +- **[Emotional Impact in Stories](../storytelling/emotional-impact-in-stories.md)** -- The surprise and emotional design techniques that determine whether leadership stories produce genuine feeling or merely transmit information. diff --git a/plugins/foreman/content/skills/leadership/strategic-questioning.md b/plugins/foreman/content/skills/leadership/strategic-questioning.md new file mode 100644 index 0000000..f437086 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/strategic-questioning.md @@ -0,0 +1,217 @@ +--- +name: "strategic-questioning" +description: "Transforms leaders from directive communicators into strategic questioners who use inquiry to inspire thinking, surface hidden problems, build ownership, and drive better decisions. Covers five essential leadership questions, the art of context-rich inquiry, question-driven meeting design, and techniques for using questions to lead without dictating. Use when meetings produce compliance instead of commitment, when teams wait for answers instead of generating them, when a leader talks more than they listen, when preparing for difficult or ambiguous decisions, or when building a culture of curiosity." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - questioning + - inquiry + - curiosity + - decision-making + - meetings + - coaching + - listening + - facilitation +related_skills: + - leader-self-reflection + - leadership-voice-and-presence + - leadership-style-adaptation + - ai-era-leadership + - grow-model + - appreciative-inquiry + - radical-candor +author: "Fatih Guner" +--- + +# Strategic Questioning + +Most leaders talk 80% of the time and listen 20%. The most effective ones reverse the ratio. + +This is not a call for silence, nor a suggestion that leaders abdicate their responsibility to decide. It is a recognition that the instrument leaders reach for first -- the declarative statement, the directive, the answer -- is often the wrong tool for the job. Statements close conversations. Questions open them. Statements transfer information. Questions generate it. Statements produce compliance. Questions produce ownership. The leader who defaults to answering is doing the intellectual work that their team should be doing, solving problems that their team should be defining, and building a dependency that feels like efficiency but functions as a constraint on every person in the room. + +Strategic questioning is not Socratic theatre -- asking questions to which you already know the answer so that others can arrive at your predetermined conclusion. It is the genuine use of inquiry as a leadership instrument: to surface information you do not possess, to challenge assumptions (including your own), to inspire thinking that exceeds what you could produce alone, and to build the collective intelligence of the organisation rather than centralising it in one person. + +--- + +## The Practice + +### Five Questions Every Leader Should Ask Repeatedly + +These are not one-time inquiries. They are recurring instruments -- questions that produce different and valuable information each time they are deployed, precisely because the context surrounding them is always changing. + +**1. "How can I help?"** +The impulse to support others is admirable; the execution is usually wrong. Leaders swoop in with solutions before the problem is defined. Asking "How can I help?" forces the other person to articulate what they actually need -- which is the first step toward owning and solving the problem themselves. The question is a gift disguised as an offer: it transfers agency back to the person who should have it. + +**2. "Wait, what?"** +A deceleration question. It prevents premature conclusions, interrupts groupthink, and creates space for understanding. When something sounds too easy, too obvious, or slightly off, "Wait, what?" invites the speaker to slow down, explain their reasoning, and revisit their assumptions. It is the shortest path from reaction to comprehension. + +**3. "I wonder why...?"** +The curiosity question. Wondering aloud why something exists in its current form is the first step in overcoming the institutional inertia that stifles growth. "Because we have always done it that way" is not an answer; it is a confession that no one has asked the question recently. And "I wonder why?" inevitably leads to its more powerful successor: "I wonder if things could be done differently?" + +**4. "Couldn't we at least...?"** +The progress question. In polarised discussions where consensus feels impossible and positions have hardened, this question finds the minimum viable agreement. "Couldn't we at least agree on some basic principles?" or "Couldn't we at least begin, and reevaluate at a later time?" It moves conversations from deadlock to movement, even if the movement is small. + +**5. "What truly matters?"** +The clarity question. Applicable to sensitive personnel decisions, complex strategic choices, and personal career dilemmas alike. This question cuts through the noise of competing considerations and forces a return to first principles. It is as useful in a board meeting as it is during a solitary walk. + +### The Art of Context-Rich Inquiry + +Not all questions are created equal. A question that demonstrates preparation, domain knowledge, and awareness of the broader landscape produces qualitatively different responses from a generic one. + +**Generic:** "What is our South America strategy?" +**Context-rich:** "I read that our top competitor is expanding in Brazil this year. How should that affect our South America strategy?" + +**Generic:** "What channels do you want to expand?" +**Context-rich:** "I would like to use my experience in Fortune 500 marketing to support your growth. What does your marketing department want to expand?" + +The first version requests information. The second generates a conversation. Context-rich questions signal respect for the other person's time, demonstrate that you have done the work, and invite expertise rather than summaries. + +### Questions That Inspire Rather Than Interrogate + +There is a category of question designed not to extract information but to expand the boundaries of what a team considers possible. + +**Narrow:** "How can we improve customer response times by 10%?" +**Expansive:** "What unmet customer needs could be the basis of an entirely new business?" + +**Narrow:** "You've mentioned you want to improve employee satisfaction. What are your next steps?" +**Expansive:** "Studies show that engagement is a better predictor of performance than satisfaction. How can we tackle a number of the factors that contribute to engagement?" + +Broad, ambitious questions demonstrate that the leader's horizon extends beyond incremental improvement. They invite employees to participate in setting goals, not merely executing them. And they contribute to a culture where questioning is valued and curiosity is modelled from the top. + +### Question-Driven Meeting Design + +The typical meeting agenda lists topics: "Budget problems," "Customer response times," "Q3 hiring." These labels describe subjects but provide no direction. Converting them to questions transforms meeting structure: + +- "Budget problems" becomes "How will we reduce spending by $100K this year?" +- "Customer response times" becomes "How can we reduce customer response times by 25%?" +- "Q3 hiring" becomes "Which three roles will have the greatest impact on our Q3 targets?" + +Questions accomplish three things that topic labels do not: they focus the group on outcomes, they clarify who should attend (whose expertise is needed to answer this question?), and they provide a natural end point -- the meeting is done when the questions are answered. + +### The Clarifying Power of One Question + +Leadership is filled with decisions where every option has a downside. The paralysis of multi-dimensional analysis -- weighing political implications, financial trade-offs, personal consequences -- can trap leaders in endless deliberation. In these moments, one question cuts through the complexity: "What is best for the organisation?" + +This is not a magic formula. But it accomplishes what more elaborate analytical frameworks sometimes fail to do: it lifts the leader above personal stakes, departmental politics, and short-term comfort to consider the systemic interest. Especially in difficult personnel decisions, where emotion and empathy argue for one course while organisational health argues for another, this question provides a clarifying anchor. + +--- + +## Prompts + +**Prompt 1 -- Question Audit:** +> Analyse the last five important conversations or meetings I led. For each, I will describe what I said and asked: [describe each interaction]. Calculate my statement-to-question ratio across all five. Identify moments where a question would have been more effective than the statement I made. For each identified moment, suggest the specific question I should have asked and explain what it would have produced that my statement did not. + +**Prompt 2 -- Meeting Redesign:** +> Here is the agenda for my upcoming [meeting type]: [paste agenda]. Convert each agenda item from a topic label to a question that focuses the discussion on a specific outcome. For each question, recommend: who should attend to answer it, how much time it needs, and what a good answer looks like. Then suggest an opening question for the meeting that sets the tone for inquiry-driven discussion. + +**Prompt 3 -- Questioning Repertoire Builder:** +> I lead a [team type] team of [number] people in [function/industry]. Generate a repertoire of 15 powerful questions organised by context: (a) one-on-one meetings, (b) team brainstorming sessions, (c) crisis situations, (d) strategic planning, and (e) performance conversations. Each question should be open-ended, context-aware, and designed to generate insight rather than confirm what I already believe. Explain the strategic purpose behind each question. + +**Prompt 4 -- Difficult Decision Facilitation:** +> I am facing a decision where every option has significant trade-offs: [describe the decision, the options, and the competing considerations]. Rather than analysing the options directly, help me develop a sequence of questions that I can use to facilitate my team's thinking about this decision. The questions should progressively narrow from broad exploration to specific recommendation, and should include at least one question that challenges my likely preference. + +--- + +## Use Cases + +**Idea-Stage Founder Replacing Solutions with Questions in Customer Discovery** +A founder conducting customer interviews consistently falls into the trap of pitching rather than listening. Every customer pain point triggers an explanation of how the product will solve it. The intervention: replace every solution statement with a question. "How do you currently handle this?" instead of "Our product does this." "What would a good solution look like to you?" instead of "Here is what we are building." The ratio shifts from 80% talking / 20% listening to 30% asking / 70% listening. Customer insights triple. Three assumptions the founder held about the market prove wrong -- discoveries that would have remained hidden under the weight of premature answers. + +**Growth-Stage VP Whose Team Has Stopped Innovating** +A VP of Product at a 120-person company runs efficient, well-structured meetings. Decisions are made quickly. Execution is reliable. Innovation has flatlined. The diagnosis: the VP's meetings are organised around directives and status updates. No space exists for exploratory thinking. The intervention: restructure one meeting per week as a "question-only" session where the VP is permitted only to ask, never to tell. The first two sessions are uncomfortable. By the fourth, a junior product manager proposes an approach to a customer segment that the VP had not considered. It becomes the company's fastest-growing feature line. + +**Scale-Stage CEO Navigating a Board Disagreement** +A CEO faces a split board on a major acquisition. Three directors favour the deal; two oppose it. Arguments have hardened; positions are entrenched. The CEO introduces "Couldn't we at least...?" to break the deadlock. "Couldn't we at least agree on the criteria by which we would judge this acquisition's success?" This meta-question shifts the conversation from positions to principles. The board agrees on five success criteria. When the acquisition is evaluated against those criteria, the path forward becomes evident -- not because anyone changed their mind, but because the question reframed what "agreement" required. + +--- + +## Anti-Patterns + +1. **Socratic Theatre.** Asking questions to which you already know the answer, guiding the team through a choreographed journey to your predetermined conclusion. Teams detect this within minutes. It produces cynicism rather than ownership, because the exercise signals that the leader's mind is already made up. + +2. **The Question Barrage.** Asking so many questions in rapid succession that the conversation becomes an interrogation rather than an inquiry. Effective questioning requires silence after the question -- space for the other person to think, formulate, and respond without pressure. + +3. **The Question That Is Actually a Statement.** "Don't you think we should launch in Q3?" is not a question. It is a directive wearing a question mark as a disguise. Genuine questions do not contain the answer. + +4. **Questioning Without Listening.** Asking excellent questions and then failing to hear, process, or act on the answers. Teams quickly learn whether questions are genuine invitations or performative rituals. If answers consistently produce no change, the questions stop generating honest responses. + +5. **Replacing All Direction with Questions.** Some situations require clear, unambiguous direction -- a crisis, a safety issue, a legal obligation. The leader who responds to "The server is down" with "What do you think we should do?" has confused inquiry with abdication. Strategic questioning supplements directive leadership; it does not replace it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Customer discovery | Questions are the primary tool for validating whether a problem exists, how severe it is, and whether anyone will pay for a solution. The founder who tells more than they ask during customer discovery will build the wrong product. | +| Validation | Assumption testing | The questions shift from "What is the problem?" to "Are our assumptions about the solution correct?" Inquiry targets the riskiest hypotheses and seeks disconfirming evidence rather than validation. | +| Early Traction | Team empowerment | As the first team forms, the founder's questions set the cultural norm. Teams that observe their leader asking rather than telling develop the habit of inquiry themselves. The ratio of questions to directives in the leader's communication directly predicts the team's creative output. | +| Growth | Meeting and decision architecture | At growth stage, meetings multiply and decision quality becomes the bottleneck. Question-driven agendas, structured inquiry processes, and the "What is best for the organisation?" anchor become operational necessities. | +| Scale | Institutional inquiry culture | At scale, the leader's questioning practice must be taught to hundreds of managers. The question is no longer "Do I ask good questions?" but "Does the organisation reward curiosity and penalise premature certainty?" | + +--- + +## Output Template + +```markdown +# Strategic Questioning Assessment + +**Leader:** [Name] +**Context:** [Team/meeting/decision context] +**Date:** [Date] + +## Current Communication Ratio +- **Statements:** [Estimated %] +- **Questions:** [Estimated %] +- **Target ratio:** [e.g., 40% statements / 60% questions] + +## Five Essential Questions: Application Plan +| Question | Where I Will Use It | Frequency | Expected Impact | +|----------|--------------------|-----------|-----------------| +| "How can I help?" | [Context] | [Daily/Weekly] | [Impact] | +| "Wait, what?" | [Context] | [As needed] | [Impact] | +| "I wonder why...?" | [Context] | [Weekly] | [Impact] | +| "Couldn't we at least...?" | [Context] | [As needed] | [Impact] | +| "What truly matters?" | [Context] | [Monthly] | [Impact] | + +## Meeting Agenda Conversion +| Current Topic Label | Converted to Question | Success Criteria | +|--------------------|----------------------|------------------| +| [Topic] | [Question] | [What a good answer looks like] | + +## Questioning Repertoire +### One-on-Ones +1. [Question and purpose] +2. [Question and purpose] + +### Team Sessions +1. [Question and purpose] +2. [Question and purpose] + +### Strategic Decisions +1. [Question and purpose] +2. [Question and purpose] + +## Commitments +- [ ] Replace [number] directives with questions this week +- [ ] Convert next meeting agenda to question format +- [ ] Track statement-to-question ratio for 30 days +``` + +--- + +## Related Skills + +- **[GROW Model](../frameworks/grow-model.md)** -- The GROW coaching framework is built entirely on sequential questioning; this skill provides the broader leadership context for inquiry, GROW provides the structured coaching conversation. +- **[Appreciative Inquiry](../frameworks/appreciative-inquiry.md)** -- Appreciative Inquiry applies strategic questioning specifically to organisational development, focusing on what works rather than what fails. +- **[Radical Candor](../frameworks/radical-candor.md)** -- Radical Candor's "solicit criticism before giving it" principle is a specific application of strategic questioning: using inquiry to build trust before delivering challenge. +- **[Leader Self-Reflection](leader-self-reflection.md)** -- The seven diagnostic questions in self-reflection are the leader's application of strategic questioning to themselves. +- **[Leadership Voice and Presence](leadership-voice-and-presence.md)** -- The curiosity dimension of leadership voice is the channel through which strategic questioning operates in daily communication. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- The problem-definition discipline shares the same premise: asking better questions matters more than generating faster answers. diff --git a/plugins/foreman/content/skills/leadership/strategic-thinking-and-alignment.md b/plugins/foreman/content/skills/leadership/strategic-thinking-and-alignment.md new file mode 100644 index 0000000..122dba1 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/strategic-thinking-and-alignment.md @@ -0,0 +1,193 @@ +--- +name: "strategic-thinking-and-alignment" +description: "Develops the daily habits and communication practices that separate strategic leaders from operational ones. Covers carving out time for strategic thinking, communicating strategic changes effectively, building organisational alignment, challenging the status quo, and fostering competitive innovation without duplicating formal strategy frameworks. Use when feeling trapped in operational detail, struggling to communicate a strategic shift, discovering that teams are pursuing divergent goals, preparing for strategy offsites, or sensing that the organisation is coasting on inertia." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - strategy + - alignment + - vision + - competitive-thinking + - strategic-intent + - communication + - status-quo + - change-leadership +related_skills: + - porters-five-forces + - blue-ocean-strategy + - art-of-war + - scenario-planning + - managing-up + - delegation-and-empowerment +author: "Fatih Guner" +--- + +# Strategic Thinking and Alignment + +Most leaders operate at 500 feet when strategy requires 30,000. They spend their days in the weeds of execution -- answering emails, attending stand-ups, unblocking teams -- and mistake this operational busyness for strategic leadership. The altitude problem is not one of intelligence but of habit. Strategic thinking is not a talent reserved for the C-suite; it is a daily practice that most leaders never develop because no one protects the time for it, least of all themselves. The formal frameworks exist elsewhere in this library -- Porter's Five Forces, Blue Ocean Strategy, the strategic lessons of Sun Tzu. This skill concerns something more fundamental: how a leader builds the muscle of strategic thought into the rhythm of ordinary days, and how they translate that thought into organisational alignment. + +--- + +## The Framework + +### Part 1: The Daily Practice of Strategic Thinking + +Strategic thinking is not what happens in annual offsites. It is what happens in the fifteen minutes before a meeting, the walk between the office and the car, the deliberate pause before replying to a Slack message with a tactical answer when a strategic one is needed. + +**Five habits that build strategic altitude:** + +**Habit 1: Schedule thinking time as ruthlessly as meetings.** +Block recurring calendar time -- even thirty minutes -- with no agenda other than to think about the business from above. No inbox. No Slack. No "quick calls." The moment this time becomes negotiable, it disappears. Most leaders protect their meeting commitments but sacrifice their thinking commitments without hesitation, which is precisely backwards. + +**Habit 2: Play CEO for a day.** +Periodically, view every meeting, project, and decision from the vantage of the person running the entire organisation. CEOs must balance conflicting needs, weigh trade-offs across functions, and prioritise long-term positioning over short-term comfort. Asking "How would the CEO see this?" is not an exercise in presumption; it is an exercise in perspective. + +**Habit 3: Think like the competitor.** +Run a simple exercise: list your company's strengths, then argue that each is actually a vulnerability. List your weaknesses, then argue that each conceals an opportunity. Repeat for your top competitor. The goal is not to reach a conclusion but to develop the cognitive flexibility that strategic thinking demands. Companies that only see their strengths as strengths are already being outflanked. + +**Habit 4: Separate competition from strategy.** +The instinct to beat rivals by improving existing products is powerful and often wrong. The strategies that generate disproportionate returns tend to create new market spaces rather than fight over existing ones. When leading brainstorming or innovation sessions, resist the gravitational pull toward incremental improvement. Push the team toward questions no competitor is asking. + +**Habit 5: Set strategic intent, not just strategic plans.** +Plans are defensive; intent is offensive. Strategic intent means setting goals that exceed current resources and capabilities -- not recklessly, but deliberately. It accelerates organisational learning by forcing the company to compete in innovative ways rather than merely sustaining current advantages. The essence of strategy is creating tomorrow's competitive advantages faster than competitors can mimic today's. + +### Part 2: Communicating Strategic Change + +The gap between a leader's strategic clarity and the organisation's strategic understanding is almost always wider than the leader believes. Two specific failures drive this gap: + +**Failure 1: Expressing change in terms of tasks, not outcomes.** +Leaders who say "We need to migrate to platform X by Q3" have communicated a task. Leaders who say "We need to be able to serve enterprise customers with 99.99% uptime by Q3, and migrating to platform X is how we get there" have communicated an outcome. The difference determines whether teams execute mechanically or with judgment. + +**Failure 2: Understating the magnitude of change.** +Leaders rarely make clear the full extent of what they are asking for. A "strategic pivot" described in one slide at an all-hands meeting does not convey the depth of behavioural, structural, and cultural change required. When followers report that their leaders "weren't clear enough," they usually mean the leader communicated the what without the why, the how, or the how much. + +### Part 3: Building Organisational Alignment + +Alignment is not a state to be achieved; it is a continuous dialogue to be maintained. The assumption that employees share a leader's understanding of strategy is, in the words of researchers, "a dangerous mistake." Misalignment produces politics, infighting, unproductive meetings, and serious obstacles to value creation. + +**The alignment discipline has three components:** + +1. **Co-creation over announcement.** Senior leaders are not the ones who implement strategy -- managers and frontline employees are. Strategy cannot be handed down like a decree; it requires input, feedback, and genuine listening across the organisation. Building consensus takes more than saying "Here's what you should do." + +2. **Continuous recalibration.** Alignment is not a one-time goal achieved in a strategy offsite and sustained by inertia. It is a recurring conversation about what is important and what is prioritised. Managers take ownership of strategy only when they are convinced of its value -- and conviction requires ongoing engagement, not a single presentation. + +3. **Vision translation at every level.** Shaping vision is not the exclusive province of senior executives. Leaders at every level can contribute by translating the company's mission for their teams, developing frontline strategies that connect to the broader arc, and identifying where their team's work fits in the long-term picture. + +### Part 4: Challenging the Status Quo + +New and experienced managers alike fall into the trap of believing that their primary job is to keep things running smoothly. Operational stability is necessary but insufficient. Part of leadership is identifying and initiating changes that enhance team performance -- even when those changes challenge existing processes, structures, or the people responsible for them. + +The leader who sees a flawed system and waits for someone else to fix it has abdicated a core responsibility. Using internal networks and informal authority to advocate for change is not insubordination; it is leadership in its most practical form. + +--- + +## Prompts + +**Prompt 1 -- Strategic Altitude Audit:** +> Assess how I currently spend my time as a leader. My typical week includes [describe meetings, tasks, and responsibilities]. What percentage of my time is spent at operational altitude versus strategic altitude? Identify three specific changes to my weekly schedule that would increase strategic thinking time without abandoning operational responsibilities. Be realistic -- I cannot simply "stop doing" operational work. + +**Prompt 2 -- Competitive Reversal Exercise:** +> My company's top three strengths are [list them]. Our top three weaknesses are [list them]. Our primary competitor is [describe]. Walk me through the competitive reversal exercise: argue that each of our strengths is actually a vulnerability, and each weakness conceals an opportunity. Then do the same for the competitor. Identify the strategic insight that emerges from this reframing. + +**Prompt 3 -- Alignment Diagnostic:** +> I suspect that my team [or organisation] is not aligned on our strategy. The strategy as I understand it is [describe]. Diagnose potential alignment gaps by asking me questions about how different groups interpret the strategy, what metrics they optimise for, and where I have seen conflicting priorities. Then recommend a process for recalibrating alignment without creating a bureaucratic overhead. + +**Prompt 4 -- Strategic Change Communication:** +> I need to communicate a strategic change to my organisation. The change is [describe]. Draft a communication plan that articulates the change in terms of outcomes (not tasks), makes clear the full magnitude of what is being asked, addresses the "why" and "how much" alongside the "what," and identifies which audiences need which level of detail. Include a framework for follow-up conversations that reinforce the message over time. + +--- + +## Use Cases + +**Early-Traction Startup Stuck in Feature-Shipping Mode** + +A founding team of engineers ships features at extraordinary velocity but has no strategic framework for deciding which features to build. Every sprint is reactive -- driven by the loudest customer request or the most recent competitor launch. The CEO introduces a weekly thirty-minute "altitude session" with no agenda other than the question: "If we were our competitor, how would we attack us?" Within a month, the team identifies that their strongest feature is also their greatest vulnerability -- a single-customer dependency that a competitor could exploit by offering a multi-tenant alternative. The roadmap shifts from reactive feature shipping to deliberate platform strategy. + +**Growth-Stage Company with Alignment Fractures** + +A 200-person company completes a strategy offsite and the leadership team leaves aligned. Three months later, the product team is optimising for user engagement, the sales team is optimising for enterprise deal size, and the customer success team is optimising for retention -- three legitimate goals that are pulling in different directions. The CEO diagnoses the alignment gap using continuous recalibration: monthly cross-functional meetings where each team presents not just their metrics but how those metrics serve the strategy. Within two quarters, the teams converge on a shared definition of the "ideal customer" that aligns all three functions. + +**Scale-Stage Division Leader Challenging an Entrenched Process** + +A VP discovers that the company's procurement process -- designed for a 50-person company -- is adding six weeks to every vendor engagement in a now-500-person organisation. Previous VPs accepted this as institutional friction. This VP uses informal authority and cross-functional relationships to document the cost of delay, build a coalition of affected department heads, and present a redesigned process to the COO. The status quo changes not because someone at the top mandated it, but because a leader at the middle refused to wait for permission to lead. + +--- + +## Anti-Patterns + +1. **Confusing strategic thinking with strategic planning.** Planning is a periodic, structured exercise. Thinking is a daily habit. A leader who attends every strategy offsite but never pauses to question assumptions between offsites is a strategic planner, not a strategic thinker. + +2. **Re-teaching frameworks instead of practising them.** Knowing Porter's Five Forces or Blue Ocean Strategy is not the same as habitually applying strategic lenses to daily decisions. This skill is about the practice, not the theory. Leaders who can recite frameworks but cannot explain how last Tuesday's product decision connects to competitive positioning have knowledge without application. + +3. **Assuming alignment exists because no one is openly disagreeing.** Silence is not alignment. Teams that appear harmonious may simply be pursuing their own interpretations of the strategy without conflict -- because they never interact deeply enough to discover their divergence. + +4. **Communicating strategy once and expecting it to stick.** A single all-hands presentation, no matter how well-crafted, does not create alignment. Strategy must be repeated, translated, and reinforced through every channel and at every level until it becomes ambient -- the air the organisation breathes rather than a document it filed. + +5. **Protecting the status quo under the guise of stability.** Leaders who describe inertia as "not fixing what isn't broken" are often avoiding the discomfort of change rather than making a strategic judgment. The status quo is never neutral; it is a choice that compounds daily. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Building the habit from scratch | Founders must carve out strategic thinking time before operational demands consume every hour. The habit is easier to establish early than to retrofit later. | +| Growth | Alignment across functions | As teams multiply, strategic alignment becomes the primary challenge. The leader's role shifts from thinking strategically alone to ensuring the entire organisation thinks strategically together. | +| Scale | Institutional strategic discipline | Strategic thinking must be embedded in processes, not dependent on individuals. Strategy reviews, competitive intelligence functions, and alignment rituals replace ad-hoc leadership habits. | + +The altitude problem intensifies with scale. A founder at early traction can hold the entire strategy in their head. A CEO at scale cannot -- and the gap between the leader's strategic clarity and the organisation's strategic understanding grows with every hire, every office, and every product line. + +--- + +## Output Template + +```markdown +# Strategic Thinking and Alignment Assessment + +## Current Altitude Distribution +| Activity Type | Hours/Week | % of Time | Strategic Value | +|--------------|-----------|-----------|-----------------| +| Operational (execution, firefighting) | [Hours] | [%] | [Low/Med/High] | +| Tactical (planning, coordination) | [Hours] | [%] | [Low/Med/High] | +| Strategic (thinking, positioning, vision) | [Hours] | [%] | [Low/Med/High] | + +## Strategic Thinking Habits +- **Scheduled thinking time:** [Yes/No -- frequency and duration] +- **Competitive perspective practice:** [How often, what format] +- **Status quo challenges initiated:** [Recent examples] + +## Alignment Assessment +| Group/Team | Their interpretation of strategy | Aligned with leadership intent? | Gap description | +|-----------|--------------------------------|-------------------------------|-----------------| +| [Team 1] | [Their version] | [Yes/Partial/No] | [Description] | +| [Team 2] | [Their version] | [Yes/Partial/No] | [Description] | + +## Strategic Communication Plan +- **Core message (outcome-framed):** [What we are trying to achieve and why] +- **Magnitude of change:** [What must change in behaviour, structure, and culture] +- **Audiences and tailored messages:** [Which groups need which framing] +- **Reinforcement cadence:** [How and when the message will be repeated] + +## 90-Day Strategic Discipline Plan +| Month | Habit to Build | Alignment Action | Status Quo Challenge | +|-------|---------------|-----------------|---------------------| +| 1 | [Specific habit] | [Specific action] | [Specific challenge] | +| 2 | [Specific habit] | [Specific action] | [Specific challenge] | +| 3 | [Specific habit] | [Specific action] | [Specific challenge] | +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](../frameworks/porters-five-forces.md)** -- Provides the analytical framework for competitive assessment; this skill addresses how to make such analysis a daily habit rather than an annual exercise. +- **[Blue Ocean Strategy](../frameworks/blue-ocean-strategy.md)** -- The formal methodology for creating uncontested market space; this skill focuses on the daily discipline of looking beyond competitive imitation. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- A structured approach to thinking about alternative futures; strategic thinking as a daily habit is the precondition for effective scenario work. +- **[Managing Up](managing-up.md)** -- Strategic visibility with senior leaders depends on having genuine strategic thinking to display; these two skills are deeply intertwined. +- **[Delegation and Empowerment](delegation-and-empowerment.md)** -- Leaders cannot find time for strategic thinking without delegating operational work effectively. +- **[Systems Thinking](../frameworks/systems-thinking.md)** -- Provides the analytical lens for understanding feedback loops and emergent behaviour that strategic altitude requires to see beyond isolated competitive moves. diff --git a/plugins/foreman/content/skills/leadership/team-culture-and-dynamics.md b/plugins/foreman/content/skills/leadership/team-culture-and-dynamics.md new file mode 100644 index 0000000..e206054 --- /dev/null +++ b/plugins/foreman/content/skills/leadership/team-culture-and-dynamics.md @@ -0,0 +1,257 @@ +--- +name: "team-culture-and-dynamics" +description: "Provides daily practices for reading team energy, shaping culture deliberately, writing unwritten rules, diagnosing accountability gaps, balancing personality types, and building high-performing teams through social connection. Use when a team feels stuck or stale, when collaboration derails despite good intentions, when unwritten norms produce confusion, when new hires struggle to decode the culture, or when a leader suspects the team's vibe is off but cannot articulate why." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - team-dynamics + - culture + - norms + - accountability + - collaboration + - personality + - engagement + - high-performance +related_skills: + - tuckman-team-stages + - belbin-team-roles + - hackman-enabling-conditions + - organisational-culture + - psychological-safety + - inclusive-leadership +author: "Fatih Guner" +--- + +# Team Culture and Dynamics + +Every team has a temperature. The experienced leader reads it the way a pilot reads instruments -- not by staring at any single gauge but by registering the pattern across many: who speaks first in meetings and who waits; whether laughter is frequent or forced; how quickly Slack messages receive responses; whether disagreements happen in the room or in the corridor afterward; the tone of the last three emails from the same person. None of these signals is diagnostic on its own. Together, they constitute the emotional weather system of the team. + +The theoretical architecture of team dynamics is well mapped. Tuckman describes the stages (forming, storming, norming, performing); Belbin catalogues the roles; Hackman identifies the enabling conditions. Those frameworks live in the `frameworks` directory and should be studied for their structural insight. This skill concerns itself with the question those frameworks do not fully answer: what does a leader actually do, day by day, to build and maintain a culture that converts individual talent into collective performance? + +--- + +## The Practice + +### Culture Is Manageable + +Boris Groysberg, Jeremiah Lee, Jesse Price, and Yo-Jud Cheng's research contains a sentence that should unsettle every leader who treats culture as atmospheric and uncontrollable: "Culture can, in fact, be managed." The first step is awareness -- understanding how culture works, what values it embodies, and what behaviours it rewards and punishes. The second step is deliberate intervention. Most leaders produce detailed plans for strategy and execution but leave culture unmanaged, relegating it to HR as a secondary concern. The result: culture becomes an emergent property of accumulated defaults, not a designed system. + +### Writing the Unwritten Rules + +Liz Fosslien and Mollie West Duffy offer the simplest and most underused culture intervention: write down the unwritten rules. Every team operates on implicit norms that insiders absorb over time and newcomers struggle to decode. Making them explicit serves three purposes: it reduces the anxiety of new hires who cannot tell what is acceptable, it surfaces norm conflicts that have been festering below conscious awareness, and it creates a document that can be revisited when circumstances change. + +The method: convene the team and brainstorm an "It's OK to ..." list. + +Examples: +- "It's OK to say you don't understand a process." +- "It's OK to turn off your camera during a virtual meeting." +- "It's OK to go for a short walk in the middle of the day." +- "It's OK to push back on a deadline if you explain why." +- "It's OK to ask for help before you're stuck, not after." + +The list should be living, not laminated. Revisit it quarterly, or whenever the team's composition or circumstances shift significantly. + +### When the Vibe Is Off: A Diagnostic Framework + +Liane Davey identifies four domains to investigate when a team feels stuck, stale, or subtly wrong: + +**1. Mandate and Goals** +- What external trends require adaptation? +- How do shifts in company strategy affect the team? +- How is the team's value within the organisation evolving? +- How can success metrics be improved? + +**2. Strategies and Roles** +- Is the team strategy aligned with its mandate? +- What tactics need revision? +- Does anyone need a change in role? +- What assumptions could endanger current plans? + +**3. Dynamics and Norms** +- What norms need to be established or revised? +- How can conflicts be resolved more effectively? +- What activities could improve trust and candour? + +**4. Communication Habits** +- What channels can be used more effectively? +- What information should be synchronous versus asynchronous? +- How can distractions be reduced? +- What are reasonable expectations for response times? + +The diagnostic works best as a group conversation, not a leader's solo analysis. The act of discussing these questions together is itself therapeutic -- it surfaces problems that individual conversations cannot reach. + +### The Right Mix of Personalities + +Dave Winsborough and Tomas Chamorro-Premuzic's research complements Belbin's role theory with a personality-type lens. Five types matter: + +| Type | Characteristic | Value to Team | +|------|---------------|---------------| +| Results-oriented | Organise work, take charge | Drive execution and accountability | +| Relationship-focused | Form genuine connections, read emotions | Build cohesion and trust | +| Process followers | Reliable, detail-oriented, conscientious | Ensure quality and consistency | +| Innovative thinkers | Curious, imaginative, open to novelty | Generate ideas and challenge assumptions | +| Pragmatic | Practical, prudent, level-headed | Ground the team in reality | + +A team dominated by one or two types produces predictable dysfunction: all innovators and no process followers create exciting chaos; all process followers and no innovators create reliable mediocrity. The leader's job is to diagnose which types are overrepresented and which are missing, and to hire or reassign accordingly. + +### Building Social Connections + +Ron Friedman's research, in partnership with learning company ignite80, establishes that social connection and team performance are not merely correlated -- they are causally linked. Two practices matter most: + +**Bond over non-work topics.** Discussing hobbies, families, and shared interests yields closer friendships and better teamwork. The leader who restricts all communication to task-related content may be efficient but is building a team that lacks the relational resilience to survive pressure. + +**Make appreciation a team norm.** Recognition is more motivating than monetary rewards, and peer-to-peer recognition is often more valued than top-down praise. Build rituals -- a weekly shout-out, a rotating "MVP" acknowledgement, a shared channel for appreciation -- and participate in them without dominating them. + +### Cross-Functional Collaboration Traps + +Lisa Kwan's research identifies a blind spot in most cross-functional initiatives: leaders focus on logistics, processes, and incentives while ignoring how the request to collaborate makes teams feel. When teams are told to share information, sacrifice autonomy, or cede defining responsibilities, insecurity triggers defensive behaviour. The leader who plans a cross-functional project should explicitly address the emotional dimension: acknowledge what teams are giving up, explain what they gain, and create structures that protect each team's identity while enabling collaboration. + +### Staffing for Innovation + +Nathan Furr, Kyle Nel, and Thomas Ramsoy identify three capabilities essential for high-profile, uncertain projects: + +1. **Comfort with uncertainty** -- People who remain curious when the endpoint is unclear. +2. **Structure in chaos** -- People who create frameworks and drive action when circumstances change. +3. **Connect and execute** -- People who see links between disparate information and produce tangible outputs. + +These are not the same as "high performers." A team of individually excellent people who all prefer certainty will stall the moment a project enters ambiguous territory. + +### Fighting Toxic Culture with Microculture + +Annie McKee addresses the leader who operates within a toxic larger culture. The prescription: create a microculture. Hold meetings -- plural, because one is not enough -- where team members discuss shared values, articulate rules of engagement, and codify norms in a team code of conduct. The microculture will not change the company, but it can protect the team. + +### The Learning Curve Mix + +Whitney Johnson's model provides a diagnostic for team engagement: at any given time, approximately 15% of the team should be at the bottom of a learning curve (new to their role or responsibilities), 70% should be in the productive middle (building and applying skills), and 15% should be at the top (mastering their current domain and ready for the next challenge). When someone reaches mastery and no new curve is offered, disengagement follows. The leader's job is to keep the curves cycling. + +--- + +## Prompts + +**Prompt 1 -- Team Temperature Read:** +> Based on these observations about my team: [describe meeting dynamics, communication patterns, recent interpersonal incidents, energy levels, and any signals that concern you]. Diagnose the team's "temperature" across Davey's four domains (mandate/goals, strategies/roles, dynamics/norms, communication). For each domain, rate it as healthy/strained/critical and recommend one intervention per domain. + +**Prompt 2 -- Unwritten Rules Workshop Design:** +> I want to run an "It's OK to ..." session with my team of [size] people. Design a 45-minute workshop: opening framing (why we're doing this), facilitation method (how to generate the list without groupthink), and follow-up plan (how to keep the list alive). Include five example prompts to get the conversation started if the team is hesitant. + +**Prompt 3 -- Personality Mix Audit:** +> Here are my team members and brief descriptions of their working styles: [list names and one-sentence descriptions]. Map each to the five personality types (results-oriented, relationship-focused, process follower, innovative thinker, pragmatic). Identify which types are overrepresented and underrepresented. Recommend whether the gap should be addressed through hiring, role adjustment, or development. + +**Prompt 4 -- Cross-Functional Launch Plan:** +> I am launching a cross-functional project involving [list teams]. Using Kwan's framework, identify the emotional risks: what is each team being asked to give up? What defensive behaviours might emerge? Design the project kickoff communication to explicitly address these concerns and propose structural safeguards that protect each team's identity while enabling collaboration. + +--- + +## Use Cases + +**Early-traction startup where the culture is the founder's personality** + +A 12-person startup has no documented norms. The culture is whatever the founder does on any given day -- which means it is unpredictable. New hires take three months to decode what is acceptable, and two have already left citing "cultural fit" without being able to articulate what the culture actually is. An "It's OK to ..." session produces a list of 20 norms that the founder had assumed were obvious. Documenting them reduces new-hire anxiety, cuts onboarding confusion, and -- unexpectedly -- forces the founder to confront two norms they had been enforcing unconsciously that were actively harmful. + +**Growth-stage company where the vibe is off but nobody can say why** + +A 75-person company has been growing quickly, and the leadership team senses malaise without being able to diagnose it. A structured Davey diagnostic reveals that the mandate domain is healthy (everyone understands the mission), but the communication domain is critical: the team has outgrown its communication norms. What worked for 30 people (all-Slack, instant responses expected) is suffocating 75 people. New norms are established: asynchronous by default, synchronous by exception, expected response times explicitly stated, and two meeting-free mornings per week. + +**Scale-stage company staffing an innovation initiative** + +A 500-person company assigns its highest-performing engineers to a new product exploration team. Six months later, the team has produced nothing. A Furr/Nel/Ramsoy analysis reveals that every team member is results-oriented and process-following -- excellent at execution, paralysed by ambiguity. Restructuring the team to include people comfortable with uncertainty and capable of connecting disparate ideas produces a prototype within eight weeks. + +--- + +## Anti-Patterns + +**1. Confusing culture with perks.** Free lunch, ping-pong tables, and unlimited PTO are not culture. Culture is how people treat each other when the project is late, the client is angry, and the budget is halved. Perks are decorative; norms are structural. + +**2. Managing individuals, not the team.** Linda Hill's research identifies this as one of the most common new-manager mistakes. Optimising each person's satisfaction independently can produce a collection of happy individuals who do not function as a unit. The leader must attend to group dynamics, shared norms, and collective performance, not just individual KPIs. + +**3. Ignoring the emotional dimension of collaboration.** Cross-functional initiatives that treat teams as interchangeable resource pools, without acknowledging the identity and autonomy being surrendered, produce defensive behaviour that manifests as passive resistance, hoarding, or sabotage. + +**4. Leaving unwritten rules unwritten permanently.** Every team has implicit norms. Refusing to surface and document them does not make them less powerful; it makes them less equitable, since insiders benefit from tacit knowledge that outsiders must guess. + +**5. Assuming culture is set at founding and persists automatically.** Culture degrades without maintenance. Every new hire, every reorganisation, every market shift applies pressure to existing norms. Leaders who assume the culture will self-perpetuate discover, usually too late, that it has mutated into something they would not have chosen. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founding norms, "It's OK to ..." documentation | Culture is set now, consciously or not; deliberate is better than default | +| Growth | Communication norms, personality mix, microculture vs. company culture | Norms that worked at 20 people break at 80; active redesign is required | +| Scale | Organisational culture architecture, cross-functional dynamics, learning-curve management | Culture becomes a systems problem requiring policy, measurement, and structural intervention | + +At early traction, the team is small enough that culture can be shaped through daily behaviour. The founder's habits -- how they handle disagreement, whether they celebrate effort or only results, how they respond to mistakes -- are the culture. Documentation at this stage feels premature but is precisely the intervention that prevents cultural drift as the team grows. + +At growth, the critical transition is from founder-driven culture to manager-mediated culture. The founder can no longer personally model norms for every employee. Middle managers become the primary culture-carriers, which means they must be explicitly equipped to understand and transmit the culture -- not just execute tasks. + +At scale, culture requires the same rigour as strategy: measurement, feedback loops, and structural reinforcement. Engagement surveys, norm audits, cross-functional trust metrics, and learning-curve analyses become the instruments through which culture is maintained -- not as bureaucratic overhead but as the operating system on which performance runs. + +--- + +## Output Template + +```markdown +# Team Culture Diagnostic -- [Team Name] + +**Date:** [Date] +**Team size:** [N] +**Leader:** [Name] + +## Temperature Reading + +| Domain | Rating | Key Signal | Intervention | +|--------|--------|-----------|-------------| +| Mandate & Goals | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Strategies & Roles | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Dynamics & Norms | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Communication | [Healthy/Strained/Critical] | [Observation] | [Action] | + +## Personality Mix Map + +| Name | Type(s) | Overrepresented? | +|------|---------|-----------------| +| [Name] | [Type] | [Yes/No] | + +**Missing types:** [List] +**Recommendation:** [Hire / Reassign / Develop] + +## Unwritten Rules (Current "It's OK to ..." List) +1. [Rule] +2. [Rule] +3. [Rule] + +## Learning Curve Distribution + +| Curve Position | Target % | Actual % | Gap | +|---------------|----------|----------|-----| +| Bottom (learning) | 15% | [%] | [+/-] | +| Middle (building) | 70% | [%] | [+/-] | +| Top (mastering) | 15% | [%] | [+/-] | + +## Social Connection Health +- Last non-work team activity: [Date and description] +- Peer appreciation frequency: [High/Medium/Low] +- Cross-team relationship quality: [Strong/Adequate/Weak] + +## 30-Day Culture Plan +1. [Action with owner and deadline] +2. [Action with owner and deadline] +3. [Action with owner and deadline] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](../frameworks/tuckman-team-stages.md)** -- Provides the developmental model for how teams evolve; this skill provides the daily behaviours that move a team through those stages productively. +- **[Belbin Team Roles](../frameworks/belbin-team-roles.md)** -- Belbin maps functional roles; this skill's personality-type lens provides a complementary view of team composition. +- **[Hackman's Enabling Conditions](../frameworks/hackman-enabling-conditions.md)** -- Hackman identifies what teams need to succeed; this skill focuses on how to provide it day by day. +- **[Organisational Culture](../frameworks/organisational-culture.md)** -- The company-level culture framework; this skill operates at the team level, where culture is lived rather than declared. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Safety is the precondition for the candour that healthy team dynamics require. +- **[Inclusive Leadership](inclusive-leadership.md)** -- Inclusion is a specific dimension of team culture; this companion skill addresses it in depth. +- **[Resolving People Conflict](../people/resolving-people-conflict.md)** -- Provides the behavioural scripts for navigating the interpersonal friction that inevitably arises during the storming phase of team development. diff --git a/plugins/foreman/content/skills/negotiation/competitive-negotiation.md b/plugins/foreman/content/skills/negotiation/competitive-negotiation.md new file mode 100644 index 0000000..973609e --- /dev/null +++ b/plugins/foreman/content/skills/negotiation/competitive-negotiation.md @@ -0,0 +1,236 @@ +--- +name: "competitive-negotiation" +description: "Executes the competitive negotiation process from opening move through final concession: anchoring strategy, ambitious asking, concession architecture, midpoint management, impasse-breaking through linkage, and closing discipline. Provides actionable protocols for value-claiming negotiations. Use when setting price in a sales negotiation, responding to an aggressive counter-offer, planning concession sequences for fundraising, structuring opening bids in acquisition talks, countering procurement hardball in enterprise deals, or coaching a sales team to stop discounting reflexively." +version: "1.0.0" +category: "negotiation" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - competitive + - anchoring + - concessions + - opening-offer + - pricing + - deal-making + - value-claiming +related_skills: + - negotiation-mindset-and-self + - win-win-negotiation + - negotiation-game-theory + - cialdini-influence + - trust-equation + - carnegie-win-friends +author: "Fatih Guner" +--- + +# Competitive Negotiation + +The vice president of sales at a technology company ran an experiment. His team had been discounting reflexively -- shaving margins to close deals, training customers to expect that the quoted price was fiction. He instructed every sales professional to add 10 percent to their next proposal. The team protested: the market was saturated, the product was ageing, proposals went through competitive RFP processes. Four months later, the results arrived. Profitability increased 3 percent. Sales volume did not decrease at all. No new product. No new marketing. No market shift. The only variable that changed was the number on the opening offer. The most important moment in any competitive negotiation is the moment of asking -- and most people retreat at precisely that point, bargaining themselves down before the other party has said a word. + +--- + +## The Framework + +### The Nature of Competitive Negotiation + +Competitive negotiation is the process by which parties determine who gets how much of a defined pool of value. It answers a single question: how will this fixed pie be divided? Unlike cooperative negotiation -- which seeks to expand the pie (see [Win-Win Negotiation](../frameworks/win-win-negotiation.md) for the principled approach, and [Negotiation Game Theory](../game-theory/negotiation-game-theory.md) for the mathematical structure) -- competitive negotiation accepts the pie's current size and focuses entirely on claiming a favourable share. + +Eight characteristics make the process predictable: + +1. **Fixed pie assumption.** The total value under negotiation is treated as finite. One party's gain is the other's loss. +2. **Zero-sum exchange.** Every dollar, percentage point, or term improvement for one side comes at the other's expense. +3. **Positional bargaining.** Each party states a position and defends it through a series of calculated retreats. +4. **Concession sequences.** Without concessions from both sides, no agreement is possible. The pattern of concessions is the negotiation. +5. **Diminishing increments.** Early moves are large; later moves shrink. The first concession might be thousands; the last might be a set of floor mats. +6. **Midpoint gravity.** Outcomes gravitate toward the midpoint of the first two *reasonable* offers. This is the single most exploitable feature of the process. +7. **The dance cannot be skipped.** Attempting to "cut to the chase" with a fair offer at the outset resets the anchor against you. The right answer at the wrong time is the wrong answer. +8. **Rising tension.** As concessions shrink and the gap narrows, emotional pressure increases. The negotiator who keeps composure captures the final increments. + +### The Ask: Your Most Important Move + +The opening offer is not an attempt to close a deal. It serves five distinct strategic functions: + +| Function | Mechanism | +|----------|-----------| +| **Starts the dance** | Signals willingness to negotiate and establishes the process | +| **Drops the anchor** | Sets the psychological reference point around which all subsequent moves orbit | +| **Manages expectations** | Communicates the range of outcomes you consider acceptable | +| **Creates upside potential** | An ambitious ask creates the possibility of an outcome better than your target | +| **Seizes initiative** | The party that frames the range controls where the midpoint falls | + +**Anchoring explained:** The first number on the table exerts disproportionate gravitational pull on all subsequent numbers. A New York restaurant introduced a $69 hot dog -- not to sell hot dogs, but to make the $17.95 cheeseburger feel reasonable. Cheeseburger sales surged. The same psychology governs every business negotiation. An office space landlord who opens at the top of the market anchors the entire discussion. A founder who opens a fundraise with an aggressive valuation anchors investor expectations upward. The anchor works at a subconscious level -- even experienced negotiators must consciously resist its pull. + +**The antidote to someone else's anchor:** Awareness, independent research, and an immediate counter-anchor. Pause the discussion if necessary. Conduct your own valuation. Return with a number grounded in your analysis, not theirs. + +### Six Blunders That Destroy Opening Offers + +**Blunder 1 -- Failing to anchor.** Letting the other party set the first number cedes the most powerful position in the negotiation. When uncertain, the value of influence (going first) almost always outweighs the value of information (waiting to hear their number). + +**Blunder 2 -- Prioritising comfort over strategy.** Research from Duke, Michigan, and Houston confirms: negotiators who make the first offer report higher anxiety *and* achieve better economic outcomes. The discomfort is a feature, not a flaw. Rehearse the opening with a trusted colleague until the anxiety subsides. + +**Blunder 3 -- "Let's see what happens."** Entering without a committed opening offer strategy surrenders you to the other party's anchor. A claims adjuster who valued a case at $35,000 received a plaintiff's demand of $300,000 -- and was subsequently authorised to settle at $75,000, more than double her own valuation. The demand, not the evidence, moved the number. + +**Blunder 4 -- Responding reasonably to an insulting offer.** An $8 million asking price for a business worth $5 million is an aggressive anchor. Responding with a "reasonable" $5 million creates a midpoint of $6.5 million -- a million above the buyer's walk-away. The correct response to an extreme offer is an equally extreme counter-offer that resets the midpoint to your target range. + +**Blunder 5 -- Misunderstanding the opening offer's purpose.** The opening offer is not your first attempt at a deal. It is the starting position of a choreographed process. Treating it as a genuine proposal leads to premature concessions. + +**Blunder 6 -- Excessive aggression.** An opening so extreme that the counterpart walks away or retaliates emotionally. Research from the University of Technology, Sydney, found that overly aggressive openers provoke spiteful counter-offers -- the other party punishes the aggression even at cost to themselves. Thread the needle: ambitious enough to capture value, credible enough to sustain engagement. + +### The Three Strategic Questions Before Any Opening + +1. **Who goes first?** Default: you. Control the anchor. Exception: when you genuinely have no idea of the value range and need their number as information. +2. **Where do you start?** Extreme or reasonable -- each has a place. Extreme positions pair with a soft delivery ("We'd ideally like to see..."). Reasonable positions pair with firm delivery ("Based on market data, the fair price is..."). +3. **How firm is your stance?** Extreme + soft = room to negotiate with warmth. Reasonable + firm = signals this is the actual number, minimal movement expected. + +### Concession Architecture + +Concessions are not retreats. They are strategic instruments with three functions: exchanging value to reach agreement, signalling your priorities and flexibility, and managing the other party's psychological experience of the deal. + +**The Seven Tools of Concession Management:** + +**Tool 1 -- Set up the process.** An ambitious opening offer creates space for substantial concessions. Each concession feels generous to the other party while moving toward your predetermined target. Without room to move, you appear rigid; rigidity breeds resentment even when your terms are fair. + +**Tool 2 -- Keep the end in mind.** Every concession should be tested against one question: does the midpoint of this round still point toward my target outcome? If the midpoint drifts away from your target, your concessions are too large. + +**Tool 3 -- Let the deal come to you.** Patience captures value. Smaller, slower concessions signal that you are approaching your limit. The negotiator who rushes leaves money on the table; the one who endures collects it. + +**Tool 4 -- Manage perceptions.** Express reluctance with each concession. Take time before responding. Describe internal approval challenges. The other party must believe each successive concession is harder to extract than the last. If concessions appear effortless, sophisticated counterparts will push for more. + +**Tool 5 -- Create a win for the other side.** J. Paul Getty's father advised: "Never try to make all the money in a deal." A counterpart who feels they lost will find ways to undermine the agreement post-signature, refuse future deals, or exact reputational costs. The goal is to capture disproportionate value while ensuring the other party perceives a fair process. A furniture store that refused to include a $15 marker with a $12,000 purchase lost all future business from that customer. The margin on the marker was irrelevant; the psychological cost of zero concessions was permanent. + +**Tool 6 -- Say no.** Paradoxically, the other party often needs to hear a "no" before they will agree to "yes." A firm refusal signals that you have reached your limit and the current terms represent the best available deal. Without a credible "no," the counterpart suspects more value remains on the table and continues pushing. Plan when and where you will deploy your "no" before the negotiation begins. + +**Tool 7 -- Use linkage.** When direct concession on the primary issue is impossible, link secondary value pools. The word *if* is the most powerful two-letter word in competitive negotiation. "If you accept our price, we will provide extended payment terms." A CEO closing a deal with a sports franchise linked seven low-cost items (PR activity, endorsements) to a final price concession. The franchise accepted all seven instantly. Linkage breaks impasses by expanding the negotiable surface area without surrendering on the core issue. + +### Substance vs. Style: The Master Combination + +Competitive negotiation does not require hostility. The most effective practitioners separate substance from style: + +- **Competitive on substance:** Ambitious opening, small concessions, firm limits, disciplined value-claiming +- **Cooperative on style:** Professional tone, respectful communication, genuine warmth, measured demeanour + +This combination allows a negotiator to claim maximum value while preserving the relationship for future transactions. Being competitive on substance while cooperative in style is the operational definition of negotiating like a professional rather than a bully. + +--- + +## Prompts + +**Prompt 1 -- Opening Offer Construction:** +> I am about to make the first move in a negotiation for [describe: fundraising valuation, contract price, salary, acquisition price, partnership terms]. My target outcome is [specific number or terms]. The other party likely expects [their probable range]. Using competitive negotiation principles, help me: (1) construct an opening offer that anchors the midpoint at or above my target, (2) determine whether to pair it with a firm or soft delivery, (3) anticipate the other party's likely counter-anchor, and (4) prepare my response to their counter. Include the specific language I should use when presenting the opening. + +**Prompt 2 -- Concession Sequence Planning:** +> I am in a multi-round negotiation over [describe deal]. My opening offer was [amount/terms]. Their counter was [amount/terms]. My target deal is [amount/terms]. My absolute bottom line is [amount/terms]. Design a concession sequence of 3-5 rounds that: (1) moves toward my target in diminishing increments, (2) keeps the running midpoint aligned with my target, (3) includes specific language for expressing reluctance at each step, and (4) identifies the round where I should deploy a firm "no" to signal my limit. + +**Prompt 3 -- Responding to an Aggressive Anchor:** +> The other party has opened with [describe their offer], which I believe is significantly [above/below] fair value. My independent assessment of fair value is [your estimate]. Help me: (1) construct a counter-anchor that resets the midpoint to my target range, (2) draft the language for rejecting their anchor without escalating emotion, (3) identify objective criteria I can cite to delegitimise their opening, and (4) plan my first three moves assuming they respond competitively. + +**Prompt 4 -- Linkage Strategy for Impasse:** +> A negotiation over [describe deal] has stalled. We are apart on [primary issue and gap]. Neither side is willing to make further concessions on this issue. Identify potential linkage opportunities: items that (a) cost me relatively little but are valuable to the other party, or (b) cost them relatively little but are valuable to me. Help me construct "if...then" proposals that break the impasse without conceding on the primary issue. My business context: [describe relevant details about what you value and what they likely value]. + +--- + +## Use Cases + +**Validation-Stage SaaS Startup Pricing Its First Ten Customers** + +A pre-seed B2B SaaS company has a working product and is closing its first ten paying customers. The founder, desperate for revenue validation, quotes $500/month to the first prospect -- a price chosen for comfort, not strategy. The prospect accepts immediately without negotiation. The founder has learned nothing about willingness to pay and has anchored herself at a price she cannot easily raise. + +Applying competitive negotiation: the founder's next proposal opens at $1,200/month -- ambitious but defensible given the ROI the product delivers. The prospect counters at $700/month. The midpoint is $950/month. Through three rounds of concessions (each smaller than the last, each expressed with visible deliberation), the founder closes at $900/month. The difference is not $400/month per customer. Compounded across the first ten customers and then used as pricing precedent for the next hundred, the opening-offer discipline produces a valuation-defining difference at the next fundraise. + +**Growth-Stage Company Negotiating an Acquisition Offer** + +A $15M ARR company receives an unsolicited acquisition offer. The acquirer's opening: $45M (3x revenue). The founder's research, grounded in comparable transactions and the company's growth rate, suggests fair value is $65-75M. The acquirer's opening is an anchor designed to pull the midpoint below fair value. + +The founder deploys a counter-anchor: $95M, paired with soft delivery ("Given our growth trajectory and recent comparable exits, we believe a range starting at $95M reflects the strategic value of this acquisition"). The midpoint resets to $70M -- inside the founder's target range. Over four rounds, concessions diminish: the founder moves from $95M to $88M to $82M to $78M. The acquirer moves from $45M to $55M to $62M to $68M. The final price of $73M -- near the midpoint of the first two reasonable offers ($95M and $55M) -- sits squarely in the founder's target zone. Without the counter-anchor, the negotiation would have gravititated toward $55M, costing the founder's shareholders $18M. + +**Early-Traction Startup Negotiating a Key Engineering Hire** + +A startup needs a senior engineer whose market rate is $180-200K. The candidate opens by requesting $220K plus 1.5% equity. The founder's budget ceiling is $195K plus 0.8% equity. Rather than conceding to avoid losing the candidate, the founder treats this as a competitive negotiation on substance while remaining enthusiastic about the candidate on style. Counter-offer: $175K plus 0.5% equity with a performance-based equity refresh after 12 months. The midpoint on salary ($197.5K) sits near the founder's range. Through two rounds -- each accompanied by genuine expressions of how much the team wants this candidate (cooperative style) and firm, small movements on numbers (competitive substance) -- the deal closes at $192K plus 0.75% equity with a 12-month refresh clause. Both parties feel respected. The founder preserved budget discipline. + +--- + +## Anti-Patterns + +1. **Discounting as Default.** Sales teams (and founders) who treat the quoted price as a fiction to be immediately discounted upon resistance. Every reflexive discount trains the market to never accept the first number. The 10-percent experiment proves the reverse: ambition is rewarded more often than expected. + +2. **Skipping the Dance.** Offering your "fair and final" number at the outset to save time. The other party will treat this as your opening position and negotiate downward from it. The process exists for a reason: it allows both parties to make concessions, read signals, and arrive at a number they can defend internally. There are no shortcuts. + +3. **Matching an Insulting Offer with a Reasonable One.** Responding to an extreme anchor with a "fair" counter-offer shifts the midpoint dramatically in the other party's favour. Extreme anchors demand extreme counter-anchors. Politeness in this context is expensive. + +4. **Conceding Without Receiving.** Making concessions without extracting reciprocal movement or linked value. Every concession teaches the other party something. A unilateral concession teaches them that pressure works and more is available. A linked concession ("if you do X, I can do Y") teaches them that value must be exchanged. + +5. **Emotional Escalation.** Allowing rising tension to convert competitive substance into competitive style. Raised voices, personal attacks, and ultimata delivered in anger destroy the very relationship that makes future concessions possible. The master negotiator maintains warmth in style while remaining unyielding on substance. Losing composure is losing leverage. + +6. **Confusing Ambition with Greed.** Pursuing the last dollar at the cost of deal completion or long-term relationship. Getty's rule holds: a counterpart who feels exploited will not honour the spirit of the agreement, will not return for future deals, and will actively damage your reputation. Competitive negotiation is about claiming a favourable share -- not the entirety -- of the available value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder equity, advisor compensation, first vendor contracts | Precedents set here persist for years. An opening offer of 0.25% to an advisor becomes the anchor for every subsequent advisor grant. Set ambitious but defensible anchors early -- renegotiating upward later is vastly harder than starting well. | +| Validation | Pricing first customers, pre-seed/angel term negotiations | The temptation to discount is strongest when revenue is zero. Resist it. Anchor at a price that reflects the value delivered, not the desperation felt. Every early price becomes a data point that investors and future customers will reference. | +| Early Traction | Enterprise sales, seed fundraising, key hire negotiations | Counterparts become more sophisticated. Procurement teams and experienced angels know the dance. Concession sequences must be planned in advance, not improvised. Linkage becomes essential for breaking impasses over payment terms, exclusivity clauses, and equity vesting. | +| Growth | Series A/B, strategic partnerships, executive compensation | Multiple-issue negotiations require careful midpoint management across several dimensions simultaneously. Concession on one dimension (board seats) should be linked to advantage on another (valuation). The founder negotiates less and prepares more, briefing the team that executes. | +| Scale | M&A, major licensing, public-market transactions | Professional advisors (investment bankers, M&A lawyers) run the process. The founder's role is to set the anchor strategy, define the walk-away point, and ensure the advisory team does not concede value to expedite their fee. Understanding competitive negotiation mechanics allows the founder to challenge their own advisors' recommendations. | + +--- + +## Output Template + +```markdown +# Competitive Negotiation Plan: [Deal Description] + +## Opening Offer Strategy +- **My target outcome:** [Specific number/terms] +- **My bottom line:** [Absolute minimum acceptable] +- **My opening offer:** [Ambitious anchor designed to place midpoint at target] +- **Delivery style:** [Firm + reasonable / Soft + extreme] +- **Opening language:** "[Draft the exact words]" + +## Anticipated Counter and Response +- **Their likely opening/counter:** [Estimated range] +- **Midpoint of first two reasonable offers:** [Calculate] +- **Does this midpoint align with my target?** [Yes/No -- if No, adjust opening] +- **My prepared counter-response:** [Specific number and language] + +## Concession Sequence +| Round | My Offer | Their Offer (Est.) | Midpoint | Movement Size | Signal Sent | +|-------|----------|-------------------|----------|---------------|-------------| +| 1 (Opening) | [Amount] | [Amount] | [Amount] | -- | Ambitious but engaged | +| 2 | [Amount] | [Amount] | [Amount] | [Smaller] | Slowing down | +| 3 | [Amount] | [Amount] | [Amount] | [Smaller still] | Approaching limit | +| 4 (Target) | [Amount] | [Amount] | [Amount] | [Minimal] | At the wall | + +## Linkage Options (If Impasse) +- **If they concede [X], I will offer [Y]** (high value to them, low cost to me) +- **If they concede [X], I will offer [Y]** +- **If they concede [X], I will offer [Y]** + +## "No" Deployment +- **Planned refusal point:** [Specific round or condition] +- **Language for saying no:** "[Draft the exact words]" +- **Walk-away conditions:** [Specific terms that trigger BATNA exercise] + +## Style Management +- **Competitive substance moves:** [List planned firm stances] +- **Cooperative style moves:** [List planned relationship-preserving actions] +``` + +--- + +## Related Skills + +- **[Negotiation Mindset and Self-Management](negotiation-mindset-and-self.md)** -- The internal preparation that precedes competitive execution; style selection, assumption auditing, and composure management determine whether the negotiator can sustain the discipline this skill demands. +- **[Cooperative Negotiation](cooperative-negotiation.md)** -- The counterpart for expanding the pie before dividing it; sophisticated negotiators use cooperative techniques to enlarge value and competitive techniques to claim it. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the theoretical architecture for interest-based bargaining that competitive tactics operate within. +- **[Negotiation Game Theory](../game-theory/negotiation-game-theory.md)** -- Provides the mathematical foundation for bottom lines, solution sets, and optimal splits; the Nash Product Solution informs where the midpoint should land. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- Anchoring is a specific application of Cialdini's broader influence principles; reciprocity governs concession dynamics. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Competitive substance with cooperative style requires trust maintenance throughout adversarial value-claiming. diff --git a/plugins/foreman/content/skills/negotiation/cooperative-negotiation.md b/plugins/foreman/content/skills/negotiation/cooperative-negotiation.md new file mode 100644 index 0000000..f119bae --- /dev/null +++ b/plugins/foreman/content/skills/negotiation/cooperative-negotiation.md @@ -0,0 +1,226 @@ +--- +name: "cooperative-negotiation" +description: "Guides the practitioner through cooperative negotiation execution: transitioning from positions to interests, deploying empathy strategically, and following a structured six-step roadmap to resolution. Use when a competitive stance has stalled, when the relationship matters as much as the deal, when negotiating with a more powerful counterparty, when seeking creative value that positional bargaining cannot unlock, or when preparing for partnership, licensing, or joint-venture conversations." +version: "1.0.0" +category: "negotiation" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - cooperation + - empathy + - interests + - value-creation + - conflict-resolution + - deal-making + - rapport +related_skills: + - win-win-negotiation + - delivering-the-deal + - trust-equation + - carnegie-win-friends + - emotional-intelligence + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +# Cooperative Negotiation + +POSITIONS TO INTERESTS -- two people fighting over an orange. One wants the peel, the other wants the juice. Same position ("I need the orange"), different interests. The negotiation fails because nobody asks why. This parable, worn smooth by repetition in every negotiation textbook, persists because its lesson remains almost universally ignored. Most business negotiations collapse not from bad faith or insufficient leverage but from a far simpler failure: both sides argue about what they want without ever surfacing why they want it. + +Fisher and Ury's principled negotiation framework (covered in the `win-win-negotiation` skill) provides the theoretical architecture -- separate people from problems, focus on interests, generate options, use objective criteria. That skill teaches the blueprint. This one teaches what to say when you sit down across the table. + +--- + +## The Framework + +### The Anatomy of a Deal + +Every negotiation begins with an issue -- a problem or opportunity that requires agreement. Each party arrives with a position: a concrete statement of how the issue should be resolved. When positions collide, the instinct is to argue harder, concede reluctantly, or walk away. This is the positional death spiral. It escalates tension, damages relationships, and wastes resources. + +The cooperative alternative requires a single, decisive move: transition from positions to interests. + +**Positions** are concrete, divisible, and visible. They are the stated demands -- price, terms, equity split, delivery date. + +**Interests** are intangible, often unarticulated, and frequently invisible even to the person holding them. They include: + +- **Ego** -- the need to look competent, respected, successful +- **Fear** -- of loss, exposure, failure, humiliation +- **Relationships** -- preserving a partnership, impressing a boss, honouring a commitment +- **Values** -- fairness, loyalty, autonomy, recognition +- **Circumstances** -- budget cycles, reporting deadlines, personal pressures + +The hospital case illustrates the principle with surgical precision. A woman with compression fractures from a botched bed transfer demanded $150,000. Her lawyer set that position. But the woman herself wanted three things: a guarantee of safer protocols, an apology, and continued access to her physician. The litigation manager addressed all three interests directly -- promising procedural review, delivering a genuine apology, and welcoming her back. The case settled for far less than the demand because the demand was never the point. + +### The 70/30 Rule + +Research consistently finds that roughly 70% of business decisions are driven by emotion, not logic. People overpay for products that make them feel good. They reject objectively superior deals that make them feel diminished. The implication for negotiators is stark: the other party's decision will depend less on what they think about your offer and more on how they feel about themselves when considering it. Your task is to construct a process in which saying yes feels like a victory for them. + +### The Roadmap to Resolution + +Moving from positions to interests does not happen organically. People resist it because sharing interests feels like surrendering control. A structured process restores that sense of control. Six steps, in strict sequence. + +**Step 1: Steer the conversation.** Actively redirect the discussion away from positional haggling. The phrase "Before we get into numbers, can we spend a few minutes understanding what each of us is trying to accomplish here?" is worth more than most opening offers. + +**Step 2: Ask questions.** Open-ended questions are the cooperative negotiator's primary instrument. Not cross-examination -- exploration. + +| Instead of... | Try... | +|---------------|--------| +| "Why do you need that?" | "Help me understand what's driving that priority." | +| "That's too high." | "Tell me more about how you arrived at that figure." | +| "Can you do better?" | "I'm curious about what a good outcome looks like from your side." | +| "Is that your final offer?" | "What is it about this particular term that matters most?" | + +The objective is to get the other side talking at length. People who feel heard tend to share information they did not intend to disclose. That information is your material for crafting a deal. + +**Step 3: Listen.** The human brain processes speech at 400-800 words per minute but people speak at 125-175. The excess capacity breeds distraction. Disciplined listening means watching for the unstated -- the ego that cannot be acknowledged, the fear that cannot be articulated. When you detect an unspoken interest, name it gently: "It sounds like making sure your team sees this as a win is important here. Am I reading that right?" + +**Step 4: Create options.** Brainstorm freely. Whiteboard it. Invite the other party into the process. Place both sides' interest lists on the board and look for non-competing elements -- the surprising number of interests that do not actually conflict. Generate volume before applying judgement. + +**Step 5: Develop options.** Filter for feasibility. Which ideas are logistically achievable? Maintain optimism during this narrowing -- the temptation to abandon the cooperative approach peaks here. + +**Step 6: Evaluate options.** The criterion is not "what is best for me" or "what is best for them" but "what doable option best satisfies both sets of interests?" Evaluation comes last. Premature critique kills creative solutions. + +### Empathy as Strategy + +Abraham Lincoln's observation -- "If you would win a man to your cause, first convince him that you are his sincere friend" -- is not sentimentality. It is a negotiation protocol. + +Empathy in this context is not sympathy. The distinction matters. Sympathy says "I feel terrible for you." Empathy says "I understand how you feel, and I understand why you feel that way." The empathetic negotiator comprehends the adversary's position without experiencing it or agreeing with it. + +**The Lead-with-Need Model (OURS):** + +1. **Observe** -- Watch body language, listen to tone, note what provokes energy or withdrawal. Stop interrupting. +2. **Understand** -- Get the counterpart to explain as much as possible. The goal is comprehension of both the problem and the emotion behind it. +3. **Respect** -- Acknowledge their perspective without conceding your position. "Thank you for sharing that with me. That is very helpful" has never once produced a negative reaction in a negotiation. +4. **Solve** -- Use what you have gathered to build toward common ground. The conversation pivots from adversaries across a table to colleagues facing a shared problem. + +**Environmental engineering:** Physical setup matters. Lounge seating rather than a boardroom table. A whiteboard for collaborative ideation. Sitting adjacent rather than across. The law of conformity means people mirror the environment -- a relaxed setting produces relaxed disclosure. + +### The Lockheed Martin Playbook + +Marillyn Hewson's negotiation with President Trump over the F-35 programme remains a masterclass in cooperative execution against a formidable counterparty. Trump held the most powerful office on earth and was publicly attacking Lockheed's pricing. Hewson's competitive options were limited. + +Her response: hire a former Trump staffer to understand his interests. Map those interests -- public "wins," job creation, the image of a skilled dealmaker. Then satisfy every one of them. She discounted planes whose costs were already declining due to economies of scale, announced workforce expansion at the Fort Worth plant, and publicly supported regulatory reform. Trump received his negotiation victory. Lockheed secured current contracts and additional orders worth billions over the following years. + +The lesson is not about flattery. It is about diagnosis. Hewson identified that the obstacle was not price -- it was image. Once she addressed the actual interest, the positional conflict dissolved. + +--- + +## Prompts + +**Prompt 1 -- Interest Mapping:** +> I am preparing for a negotiation about [describe: partnership, contract, equity, vendor deal]. The other party's stated position is [describe]. Using the positions-to-interests framework, help me: (1) identify at least five possible underlying interests behind their position, including ego, fear, and relationship factors, (2) map my own interests separately from my position, (3) identify where our interests overlap or are non-competing, and (4) suggest three creative options that address both sets of interests. Context: [company stage, relationship history, power dynamics]. + +**Prompt 2 -- Empathy Deployment Plan:** +> I need to negotiate with [describe counterparty] who is emotionally invested in [describe their concern]. Using the Lead-with-Need model (Observe, Understand, Respect, Solve), help me draft: (1) three open-ended questions to surface their real interests, (2) two empathetic acknowledgement statements that do not concede my position, (3) a proposed physical setup for the meeting, and (4) a bridging statement that transitions from empathy to problem-solving. My situation: [describe]. + +**Prompt 3 -- Roadmap to Resolution Session Design:** +> I have reached an impasse in a negotiation about [describe]. Both sides are locked in positional bargaining. Design a cooperative session using the six-step Roadmap to Resolution: (1) script my opening statement to redirect the conversation, (2) list ten open-ended questions to surface interests, (3) propose a whiteboard exercise for joint brainstorming, and (4) define evaluation criteria for the options we generate. Current positions: [ours] vs. [theirs]. Relationship importance: [high/medium/low]. + +**Prompt 4 -- Formidable Counterparty Strategy:** +> I am negotiating with a counterparty who holds significantly more power than I do -- [describe: large client, dominant investor, regulatory body, acquirer]. A competitive approach will fail. Using the cooperative negotiation framework, help me: (1) hypothesise their ego, image, and relationship interests, (2) identify low-cost concessions I can offer that satisfy their intangible needs, (3) design a strategy to give them a visible "win" while protecting my core interests, and (4) prepare fallback positions if cooperation is not reciprocated. + +--- + +## Use Cases + +**Early-Traction SaaS Company Negotiating a Channel Partnership** + +A 15-person B2B SaaS company needs a distribution partnership with a large systems integrator. The integrator's position: exclusive rights for the enterprise segment, 40% revenue share, and co-branding that subordinates the startup's identity. The founder's position: non-exclusive, 20% share, and independent branding. + +Positional bargaining produces a stalemate. The cooperative approach begins with interest mapping. The integrator's interests: their sales team needs a differentiated product to pitch against competitors; their VP of partnerships needs a visible win for the quarterly business review; they fear investing in training only to see the startup sign a rival integrator. The founder's interests: reach enterprise buyers without building a direct sales team; maintain brand identity for future fundraising; avoid dependency on a single channel. + +The resolution: a 12-month "preferred partner" designation (not exclusive, but the integrator is the only partner in their specific vertical), 30% revenue share on deals they originate (splitting the difference on economics but tying it to origination), co-branded landing pages with equal logo treatment, and a commitment that the startup will not sign a competing integrator in the same vertical for 12 months. The integrator's VP gets a headline for the QBR. The founder retains optionality. Neither party's stated position survives, but both parties' interests are fully served. + +**Growth-Stage Founder Resolving a Co-Founder Dispute** + +Two co-founders of a Series A company disagree on strategic direction. One wants to double down on the current market; the other wants to expand into an adjacent vertical. The positional argument has lasted months and is paralysing the executive team. + +A cooperative intervention starts with separate interest conversations. Founder A's interests: fears diluting focus and repeating the mistake of a previous startup that expanded too early; wants validation that the current strategy is working. Founder B's interests: sees the current market commoditising and fears being caught without diversification; wants to be seen as the visionary partner, not the operational one. + +Neither interest conflicts with the other. The resolution: a 90-day experiment in the adjacent vertical with a capped budget and pre-defined success metrics, run by Founder B, while Founder A leads an intensified push in the core market. If the experiment hits metrics, expansion proceeds. If not, full resources return to the core. Both founders' fears are addressed, both egos are served, and the company gets data instead of arguments. + +--- + +## Anti-Patterns + +**Cooperation as conflict avoidance.** The cooperative approach is not permission to avoid hard conversations. Founders who use "let's find a win-win" as a euphemism for "I'm uncomfortable saying no" will consistently leave value on the table. Cooperation requires the courage to surface difficult interests -- including your own -- and to hold firm on those interests even when the process feels tense. + +**Skipping the sequence.** The Roadmap to Resolution has a strict order for a reason. Jumping to option evaluation before interests are fully surfaced produces solutions that address the wrong problem. The most common violation: brainstorming solutions before the other party has finished explaining their perspective. Patience in steps one through three pays compound returns in steps four through six. + +**Projecting your interests onto the other party.** Assuming you know what they want without asking is positional bargaining with a cooperative veneer. The hospital litigation manager did not assume the patient wanted money -- he asked, and discovered she wanted an apology. The discipline of genuine inquiry cannot be faked. + +**Deploying empathy as a tactic.** When empathy is performed rather than practised, the counterparty detects it. The result is worse than no empathy at all -- it registers as manipulation. Empathy requires genuine curiosity about the other person's experience, even if you plan to negotiate aggressively on substance. + +**Abandoning cooperation at the first impasse.** Cooperative negotiation is not a fallback for when competition fails; it is a different operating system. Switching back to competitive bargaining at the first sign of difficulty signals that the cooperative posture was insincere. Commit to the process or do not begin it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder alignment and early advisor relationships | Interests are personal and existential -- identity, vision, fear of failure. The Roadmap to Resolution prevents founding teams from entrenching positions before the company even exists. | +| Validation | First customer deals and pilot negotiations | Weak BATNA makes cooperation essential, not optional. Surface the pilot customer's underlying fears (risk, internal credibility) and build the deal around removing those fears rather than arguing price. | +| Early Traction | Vendor contracts, partnership terms, early hires | Negotiations multiply rapidly. Establish cooperative norms now -- they compound. An early hire negotiation that surfaces the candidate's real interests (autonomy, learning, equity upside) costs less and retains longer than one that only haggles salary. | +| Growth | Fundraising, enterprise sales, strategic alliances | Multi-stakeholder negotiations demand interest mapping at scale. Each investor, board member, and procurement officer has distinct interests. Map them individually, not as a monolith. | +| Scale | M&A, cross-border deals, regulatory negotiation | Cultural adaptation of empathy becomes critical. The Lead-with-Need model must account for indirect communication norms, hierarchical decision-making, and relationship-first cultures. | + +--- + +## Output Template + +```markdown +# Cooperative Negotiation Preparation: [Deal/Context] + +## Parties and Power Map +- **Our side:** [Individuals, roles, decision authority] +- **Their side:** [Individuals, roles, decision authority] +- **Power balance:** [Symmetric / Asymmetric — describe] +- **Relationship importance:** [Critical / Important / Transactional] + +## Positions vs. Interests +| Issue | Our Position | Our Interests (Why) | Their Position | Their Likely Interests (Why) | +|-------|-------------|---------------------|----------------|------------------------------| +| [Issue 1] | | | | | +| [Issue 2] | | | | | + +## Intangible Interest Scan +- **Ego factors:** [Who needs to look good? To whom?] +- **Fear factors:** [What is each party afraid of losing?] +- **Relationship factors:** [What existing relationships constrain or enable the deal?] +- **Circumstantial pressures:** [Deadlines, budget cycles, reporting periods?] + +## Roadmap to Resolution — Session Plan +1. **Redirect statement:** "[Draft opening to steer away from positions]" +2. **Key questions:** [List 5-7 open-ended questions] +3. **Listening targets:** [What unstated interests to watch for] +4. **Brainstorming format:** [Whiteboard / shared doc / structured exercise] +5. **Evaluation criterion:** "What option best serves both interest sets?" + +## Creative Options (Pre-Session Hypotheses) +1. [Option addressing their ego + our economics] +2. [Option addressing their fear + our timeline] +3. [Option addressing shared interests] + +## Empathy Plan +- **Acknowledgement statement:** "[Draft]" +- **Common ground:** [Shared experiences, values, or pressures] +- **Environment:** [Meeting setup, seating, tone] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- The theoretical foundation for interest-based negotiation; this skill translates Fisher and Ury's four principles into conversational execution and empathy deployment. +- **[Delivering the Deal](delivering-the-deal.md)** -- Picks up where cooperative negotiation leaves off: preparation checklists, obstacle management, and satisfaction engineering for closing and post-deal durability. +- **[Competitive Negotiation](competitive-negotiation.md)** -- The value-claiming counterpart; once the pie is expanded through cooperative techniques, competitive tactics determine how it is divided. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust enables the vulnerability required to share real interests; low trust makes cooperative negotiation structurally impossible. +- **[Thomas-Kilmann Conflict](../frameworks/thomas-kilmann-conflict.md)** -- Provides the diagnostic for when to deploy a cooperative approach versus competitive, compromising, or avoidant modes. +- **[Prisoners Dilemma and Cooperation](../game-theory/prisoners-dilemma-and-cooperation.md)** -- The game-theoretic foundation for why cooperation produces better joint outcomes and what structural conditions make it sustainable. diff --git a/plugins/foreman/content/skills/negotiation/delivering-the-deal.md b/plugins/foreman/content/skills/negotiation/delivering-the-deal.md new file mode 100644 index 0000000..4029d31 --- /dev/null +++ b/plugins/foreman/content/skills/negotiation/delivering-the-deal.md @@ -0,0 +1,278 @@ +--- +name: "delivering-the-deal" +description: "Provides the complete execution toolkit for closing negotiations: a 21-point preparation checklist, a framework for overcoming obstacles and disarming tactics, and the three-part satisfaction model for durable agreements. Includes a self-assessment instrument for measuring negotiation competence. Use when preparing for a high-stakes negotiation, when a deal has stalled or hit tactical obstacles, when managing post-deal satisfaction and buyer's remorse, or when conducting a negotiation capability audit." +version: "1.0.0" +category: "negotiation" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - preparation + - tactics + - closing + - satisfaction + - obstacles + - deal-making + - self-assessment + - due-diligence +related_skills: + - cooperative-negotiation + - win-win-negotiation + - trust-equation + - cialdini-influence + - scenario-planning + - eisenhower-matrix +author: "Fatih Guner" +--- + +# Delivering the Deal + +LAST MILE -- 80% of negotiations collapse in the final 20%. The cause is always the same: premature relaxation when the finish line appears close. The parties have done the hard work of surfacing interests, generating options, building rapport. The outline of agreement is visible. And precisely at this moment, discipline evaporates. Preparation gives way to improvisation. Obstacles that should be anticipated arrive as surprises. Tactics that should be recognised go undetected. The deal that was 90% complete dies not from irreconcilable differences but from sloppy execution in the closing stretch. + +Governor Phil Bredesen of Tennessee -- who built a healthcare company, transformed Nashville's downtown, and recruited the Titans from Houston -- put it plainly during a bus ride through rural China: "A vision without a plan is just a dream." Every negotiator envisions the great deal. Envisioning is the easy part. Delivering requires a systematic preparation process, a protocol for managing obstacles, and a framework for engineering the satisfaction that makes agreements durable. + +--- + +## The Framework + +### Part I: The Negotiator's Preparation Checklist + +Research suggests that 80% of negotiating effort should occur before the parties sit down. The following 21 questions constitute a comprehensive preparation protocol. Working through them requires 30-60 minutes for a standard negotiation, longer for complex multi-party deals. The investment pays returns that compound across every round of the process. + +**Mapping the Terrain** + +1. **Who are the parties?** Include anyone who will affect or be significantly affected by the outcome -- even those not at the table. The absent stakeholder who can veto a deal is more dangerous than the adversary across from you. +2. **What are the core issues?** Identify the two or three fundamental questions the negotiation must answer. Price. Timeline. Scope. Control. Resist the temptation to catalogue every sub-issue at this stage. +3. **How important are the issues relative to the relationship?** This single diagnostic determines whether to lead with a competitive or cooperative approach. High issue importance plus high relationship importance demands principled, interest-based negotiation. High issue importance plus low relationship importance permits more aggressive value-claiming. +4. **Will the other party negotiate competitively or cooperatively?** Anticipate their posture. If competitive, prepare accordingly -- do not bring a cooperative playbook to a zero-sum fight without a fallback. +5. **What is your intended approach?** You may plan to start cooperatively and shift competitive, or vice versa. The key is intentionality. Reactive negotiators lose. + +**Substance and Intelligence** + +6. **How well do you understand the substance?** Ignorance is exploitable. If the other side detects that you do not know the language, valuation methods, or market norms of what you are negotiating, they will calibrate their offers accordingly. Do the homework. +7. **What assumptions are you making?** List them explicitly. Then test the critical ones before negotiations begin. A faulty assumption about the other party's authority, budget, or alternatives can crater a deal. +8. **What alternatives exist if no deal is reached?** For both sides. Be honest -- not hopeful, not catastrophic, but realistic about what happens if you walk away. +9. **What is the most likely alternative?** Distill the range of alternatives into the single most probable outcome of no-deal. Analyse its consequences -- financial, relational, reputational -- for both parties. +10. **How can you improve your alternative before the negotiation?** A real estate developer eyeing a parcel bought a comparable lot across the street before returning to the original seller. Her improved alternative -- "I'll simply build over there" -- produced immediate concessions. Strengthen your BATNA before you need it. + +**Strategy and Sequencing** + +11. **What is the strategic sequence of issues?** Conventional wisdom says start with easy issues to build momentum. The better approach: sequence issues to preserve linkage. If you resolve the easy issues first and then hit a wall on the hard ones, you have no remaining currency to trade. Leave enough unsettled that you can move value between issues to unlock an impasse. +12. **What is your ideal outcome?** Define your target with precision. A sharpshooter cannot hit what they cannot see. +13. **What is your bottom line?** This must be better than your most likely alternative. Otherwise, take the alternative. Write it down before the negotiation begins. Revise only with new information, not under pressure. +14. **Will you make the first offer?** First offers anchor. If you want influence, go first. If you want information, let them go first. Decide in advance. +15. **What is your opening offer?** Formulate it based on research, not aspiration. Consider how to present it for maximum impact on the other side's expectations. +16. **What does the concession dance look like?** Map anticipated moves and countermoves. You will not get it exactly right, but the exercise forces you to think in sequences rather than reactions. + +**Interests and Creativity** + +17. **What are the intangible interests on each side?** Speculate on ego, fear, relationships, and circumstances for the other party. Map your own with equal honesty. +18. **What creative options might be integrated?** Brainstorm without constraint. The analytical brain evaluates; the creative brain generates. Do not run both simultaneously. + +**Tactical Readiness** + +19. **What tactics do you anticipate?** Especially relevant if you have negotiated with the counterparty before. Prepare specific responses. +20. **What is the optimal setting?** Control environment when possible. Consider comfort, formality, and whether the setting gives either party an unearned advantage. +21. **When is the optimal time?** Timing is leverage. Negotiate when the other party is most inclined to agree -- before their fiscal year closes, after they have lost a competing bid, during their expansion phase. + +### Part II: Overcoming Obstacles + +Obstacles are not interruptions to the negotiation process; they are the process. Some are factual and circumstantial. Some are personal and psychological. Some are deliberate tactics deployed to extract advantage. + +**The Sullenberger Protocol** + +Captain Sully Sullenberger landed US Airways Flight 1549 on the Hudson River with 155 souls aboard after a dual bird strike eliminated both engines. He had never trained for this specific scenario. He succeeded because he executed six principles that translate directly to negotiation obstacle management: + +1. **Right approach** -- Remain calm when the process fails. Emotional reactions produce positional entrenchment. Strategic composure produces options. +2. **Right communication** -- Keep the lines open. When communication dies, the deal dies with it. If direct communication is failing, bring in a third party -- mediator, advisor, mutual contact. +3. **Right vision** -- See the solution inside the problem. Shift mental energy from cataloguing barriers to identifying the opportunity each barrier presents. +4. **Right roles** -- Match your role to the moment. In a single negotiation, you may need to be a listener, a challenger, an ally, a strategist, and a peacemaker. Knowing which role the current moment demands is its own form of intelligence. +5. **Right values** -- Decide your ethical boundaries before the pressure arrives. Negotiators whose values flex under duress eventually find themselves in deals they cannot defend. +6. **Right decision** -- The first five elements converge on this one. Good process yields good judgement. Rushed process yields lucky or unlucky outcomes. + +**The Three-Step Tactic Disarmament Protocol** + +When the other party deploys a tactic, two instinctive responses present themselves: ignore it (which signals that it is working) or counter with a tactic of your own (which escalates the tactical arms race and pulls focus from substance). Neither is productive. + +**Step 1: Identify the tactic.** Recognise it by name. Common varieties: + +| Tactic | Mechanism | What It Looks Like | +|--------|-----------|-------------------| +| Bait and switch | Signal willingness on X, then withdraw it after commitment | "We agreed on that, but our board has a new requirement..." | +| Take it or leave it | Force a binary decision to preclude negotiation | "This is our final offer. Accept or we walk." | +| Lack of authority | Introduce an unseen decision-maker to ratchet demands | "I'd love to agree, but my partner needs one more thing..." | +| Bogus demands | Inflate the agenda with issues they will later "concede" | "We also need exclusivity, a non-compete, and first refusal..." | +| Time pressure | Compress the timeline to force hasty concessions | "This offer expires at 5pm today." | +| Going in the other direction | Move further from agreement to reset anchoring | "Actually, we need to revisit the terms we already settled." | + +**Step 2: Call it out.** Name the tactic explicitly. "It looks like we're being asked to bid against ourselves here. Can we establish that both sides will exchange counteroffers?" Labelling a tactic diminishes its power. The other party may become defensive, but more often they simply stop. + +**Step 3: Negotiate the process before the substance.** If the tactic persists, halt the substantive negotiation. You always have the power to stop and renegotiate the rules. "We're going to pause on the terms until we agree on how this process will work. Once we have a process both sides trust, we'll be in a better position to reach agreement." + +### Part III: The Secrets of Satisfaction + +A deal is not durable because the terms are good. A deal is durable because both parties feel satisfied. Satisfaction and substantive outcome are correlated but not synonymous -- research shows that negotiators who achieve objectively superior outcomes sometimes feel less satisfied than those who achieved less but experienced a better process. + +**Subjective Value: The Hidden Variable** + +Four components determine whether a negotiator feels satisfied: + +1. How they feel about the relationship with their counterpart +2. How they feel about their own behaviour during the negotiation +3. How they feel about the fairness of the process +4. How they feel about the outcome + +A striking finding: in controlled experiments, negotiators who were falsely told their counterpart was happy with the outcome felt less successful than those told their counterpart was disappointed -- even though the actual outcomes were identical. Satisfaction is comparative, not absolute. + +**The Counterfactual Trap** + +Post-deal regret -- "What if I had pushed harder?" -- is a predictable psychological phenomenon, not a sign of a bad deal. It intensifies when the other party accepts a first offer too quickly (triggering suspicion that you left value on the table) and when negotiations involve multiple issues (each resolved issue creates a "what if" scenario). Awareness of this tendency is itself a defence: the regret is generated by the brain's counterfactual machinery, not by the economics of the deal. + +**The Three Pillars of Satisfaction** + +Durable agreements require satisfaction across three dimensions: + +**1. Process satisfaction.** People accept outcomes they might otherwise reject when the process feels fair, inclusive, and well-managed. A negotiation that rushes to closure, excludes key stakeholders, or feels chaotic will produce fragile agreements regardless of the terms. Build process satisfaction by: establishing clear agendas, allowing adequate time for deliberation, giving all parties voice, and documenting agreements transparently. + +**2. People satisfaction.** The human element. How the parties treat each other during the negotiation determines whether the agreement is implemented in good faith or sabotaged passively. Two nurses in a Nashville hospital stopped to hug a grieving family before performing their clinical duties. The clinical outcome was unchanged. The human experience was transformed. Build people satisfaction by: acknowledging emotions before addressing logistics, following through on small commitments during the process, and treating the other party's concerns as legitimate even when they are obstacles. + +**3. Product satisfaction.** The substantive terms of the deal. Product satisfaction is necessary but insufficient alone. Many negotiators throw resources at the product dimension -- better price, more favourable terms -- while neglecting process and people. The result: a counterparty who got what they asked for but still feels dissatisfied, and who will be a difficult partner in implementation. + +**The Disney Recovery Protocol.** When satisfaction fails in one dimension, compensate aggressively in the other two. A nine-year-old boy tripped on a ride at Disney World -- a product failure. Disney's response: meticulous process (incident report, serious follow-up) and extraordinary people treatment (a stuffed Mickey Mouse, a handwritten note, a personalised get-well message). The family returned the next day and spent more money. The principle scales directly to business negotiation: when you cannot deliver on a term, over-deliver on the process and the relationship. + +**Anchoring Satisfaction Before Closing** + +The final moments of a negotiation disproportionately shape how both parties remember the experience. Three techniques: + +- **Frame against the alternative, not the aspiration.** "Compare this outcome to what would have happened if we hadn't reached agreement" produces more satisfaction than "compare this to what you initially wanted." +- **Summarise mutual gains.** Before signing, walk through what each side achieved. This converts abstract satisfaction into concrete awareness. +- **Manage the counterparty's narrative.** Help them articulate why this is a good deal in terms their stakeholders will accept. If your counterparty cannot explain the deal to their board, the deal is not closed -- it is deferred. + +### Part IV: The Self-Assessment Framework + +Honest self-evaluation separates negotiators who improve from those who repeat the same mistakes with increasing confidence. Score each item 1 (never) through 5 (always) across three domains: + +**Preparation (10 items):** Identifying all parties and authority; analysing issue vs. relationship importance; mapping alternatives for both sides; improving alternatives before negotiating; setting a target outcome; establishing and holding a bottom line; strategic first-offer timing; deliberate opening offer process; ambitious opening offer; planned concession sequence. + +**Execution (6 items):** Adapting approach to the other side's style; willingness to create productive discomfort; engineering empathy through environment and conversation; asking open-ended questions; bringing additional resources into the deal; developing creative options from discovered interests. + +**Strategic Integrity (5 items):** Maintaining credibility through consistent words, moves, and signals; identifying and addressing tactics before proceeding; seeking mutually beneficial solutions; attending to process, people, and product throughout; walking away when the deal or behaviour is unproductive. + +**Scoring:** 90-105 = operating at a high level. 70-89 = developing with identifiable gaps. 50-69 = foundation present but inconsistent. Below 49 = the framework is understood; deliberate practice begins. + +--- + +## Prompts + +**Prompt 1 -- Full Preparation Walkthrough:** +> I have a negotiation in [timeframe] about [describe: contract, partnership, investment, acquisition, hire, dispute]. Walk me through the 21-point Negotiator's Preparation Checklist. For each question, help me formulate a specific answer based on my context: [describe company, stage, counterparty, power dynamics, relationship importance, known alternatives]. Produce a completed Negotiation Preparation Tool I can bring to the table. + +**Prompt 2 -- Tactic Identification and Response:** +> In my current negotiation about [describe], the other party is [describe their behaviour: moving goalposts, refusing to counter, introducing new stakeholders, compressing timelines, making it personal]. Identify which negotiation tactic(s) are being deployed. For each tactic: (1) name it, (2) explain its mechanism, (3) draft a call-out statement I can use, and (4) script a process renegotiation if the tactic persists. My BATNA: [describe]. + +**Prompt 3 -- Satisfaction Engineering:** +> I am about to close a deal on [describe terms]. Before signing, help me: (1) assess whether both sides have satisfaction across process, people, and product dimensions, (2) identify any dimension where satisfaction is weak and suggest compensating actions, (3) draft a closing summary that anchors both parties' satisfaction, and (4) anticipate potential post-deal regret triggers and prepare a counter-narrative. The other party's key stakeholders are [describe]. + +**Prompt 4 -- Negotiation Self-Assessment Debrief:** +> I just completed a negotiation. Here is what happened: [describe process and outcome]. Walk me through the 21-item self-assessment framework. For each item, help me honestly score my performance (1-5) and identify specific actions to improve. Produce a personalised development plan focusing on my three weakest areas. + +**Prompt 5 -- Obstacle Scenario Planning:** +> I anticipate the following obstacles in my upcoming negotiation about [describe]: [list known obstacles -- deadlock risk, emotional counterparty, power imbalance, cultural differences, multiple parties, bad faith signals]. For each obstacle, apply the Sullenberger Protocol: (1) what is the right approach, (2) what communication strategy fits, (3) what does the solution look like inside this problem, (4) what role should I play, (5) what values guide my response, and (6) what is the right decision framework? + +--- + +## Use Cases + +**Validation-Stage Startup Closing Its First Enterprise Pilot** + +A pre-revenue startup has spent three months in conversations with a mid-market company's VP of Operations. The VP is enthusiastic but procurement has entered and is deploying classic tactics: bogus demands (source code escrow, unlimited liability, exclusivity), time pressure ("resolve this by quarter-end"), and lack of authority ("legal has concerns"). The founder applies the three-step disarmament protocol. She calls out the pattern: "Some of these requests feel like standard procurement positioning rather than genuine requirements. Can we separate the must-haves from the nice-to-haves?" She then negotiates the process: mutual term sheet format, three real issues to resolve, standard language for the rest. On satisfaction, she focuses on the VP -- the internal champion -- helping him build the narrative his leadership needs: risk mitigation (limited scope), measurable outcomes (defined success criteria), ease of exit (30-day termination). Procurement signs off because the process felt rigorous. The pilot launches. + +**Scale-Stage Acquisition: Managing Buyer's Remorse** + +A 300-person company has agreed to a $180M acquisition, but two weeks before signing, the acquirer's integration team raises concerns about technical debt, key-person dependency, and customer concentration. The CFO signals interest in a price reduction. The founder recognises the counterfactual trap -- the acquirer's team is generating "what could go wrong" scenarios that erode subjective satisfaction with their own deal. She addresses process satisfaction by proposing a structured due diligence week with full access; people satisfaction by arranging direct conversations between her engineering leads and the acquirer's CTO; and product satisfaction by presenting a data room that contextualises each concern with data (concentration declining quarter-over-quarter, succession plan documented, technical debt remediation funded). She frames the closing against the alternative: "The strategic rationale has not changed. The risks are real, documented, and managed. The alternative is restarting a search in a market where this capability is scarce." The deal closes at the original price with an earn-out component addressing residual anxiety. + +--- + +## Anti-Patterns + +**Treating preparation as a mental exercise.** Thinking through the checklist is not the same as completing it. The Negotiation Preparation Tool demands written answers -- not because writing is sacred, but because it forces precision. The difference between "I think their alternative is weak" and writing "Their most likely alternative is rebidding the contract, which will cost them 6-8 weeks and risks losing internal sponsorship from the VP who championed this project" is the difference between intuition and strategy. + +**Over-preparing substance, under-preparing behaviour.** Research confirms that negotiators devote extensive effort to defining what they want and almost none to planning how they will engage the human beings across the table. The checklist's behavioural questions (items 3-5, 17, 19-21) are not secondary -- they are where most negotiations are won or lost. + +**Ignoring tactics until they succeed.** The instinct to ignore a tactic -- hoping it will stop -- signals to the other party that the tactic is effective. Every unreturned serve emboldens the next. Identify, call out, and negotiate the process. This is not adversarial -- it is hygienic. + +**Celebrating the deal before engineering satisfaction.** A signed term sheet with an unsatisfied counterparty is a lawsuit waiting to happen. Satisfaction must be designed, not assumed. If the other party cannot explain to their own stakeholders why this is a good deal, the agreement is structurally fragile. + +**Neglecting post-deal relationship management.** The negotiation does not end at signing. The first 90 days of implementation determine whether the agreement becomes a productive partnership or a source of escalating disputes. Build a post-signing check-in cadence into the deal itself. + +**Using the self-assessment to confirm existing beliefs.** The diagnostic is useful only when answered with uncomfortable honesty. Most negotiators overrate their listening skills, underrate their tendency to skip preparation, and avoid confronting their discomfort with tactical conflict. Score yourself as your toughest counterparty would score you. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder agreements, advisor term sheets, early IP negotiations | Preparation is fast but critical. Founders skip checklists because "we trust each other." Trust does not survive ambiguity. Write it down. | +| Validation | First customer contracts, seed fundraising, vendor agreements | Weak alternatives demand compensating preparation. Work items 8-10 relentlessly -- improving your BATNA is the highest-leverage pre-negotiation activity when you have almost no leverage. | +| Early Traction | Hiring key employees, Series A terms, partnership deals | Negotiations become concurrent. The checklist must be repeatable and quick enough to apply to five deals in a single week without degrading quality. Standardise your preparation process. | +| Growth | Enterprise sales, multi-party alliances, board-level negotiations | Obstacles intensify and tactics become more sophisticated. The three-step disarmament protocol is no longer optional -- it is a daily operational requirement. Satisfaction engineering now involves stakeholders you will never meet (the counterparty's board, their investors, their legal counsel). | +| Scale | M&A, international expansion, regulatory negotiation, public-market transactions | Every element of this framework operates simultaneously and at high stakes. Preparation is done by teams, not individuals. Obstacle management requires scenario planning across multiple failure modes. Satisfaction must be engineered for counterparties, their stakeholders, regulators, and the public narrative. | + +--- + +## Output Template + +```markdown +# Negotiation Preparation Tool: [Deal/Context] + +## Terrain Map +- **Parties:** [All parties, including absent stakeholders with veto power] +- **Core issues:** [2-3 fundamental questions to resolve] +- **Issue vs. relationship importance:** [Both High / Issue High + Relationship Low / etc.] +- **Anticipated counterparty approach:** [Competitive / Cooperative / Mixed] +- **Our intended approach:** [Describe, including triggers for shifting] + +## Intelligence and Alternatives +- **Substance mastery:** [Confident / Adequate / Gaps to close] +- **Key assumptions to test:** [List] +- **Our BATNA:** [Best alternative, ranked] | **Their BATNA (est.):** [Ranked] +- **BATNA improvement actions:** [What we can do before the negotiation] + +## Strategy +- **Issue sequence:** [Order and rationale] +- **Target / Bottom line:** [Ideal outcome] / [Walk-away point] +- **First offer:** [Go first or let them — rationale] | **Opening terms:** [Specific] +- **Concession map:** [Anticipated sequence of moves and countermoves] +- **Intangible interests:** Ours: [list] | Theirs (est.): [list] +- **Creative options:** [Brainstormed list] + +## Tactical Readiness +- **Anticipated tactics and responses:** [List] +- **Setting and timing:** [Location, room setup, timing rationale] + +## Satisfaction Plan +| Dimension | Plan | Contingency if Weak | +|-----------|------|---------------------| +| Process | [How we ensure fairness] | [Compensating action] | +| People | [How we treat the counterparty] | [Compensating action] | +| Product | [How we ensure adequate terms] | [Compensating action] | +- **Closing narrative:** [How we help them explain this deal to their stakeholders] +- **Post-deal:** [30/60/90-day check-in schedule and satisfaction monitoring] +``` + +--- + +## Related Skills + +- **[Cooperative Negotiation](cooperative-negotiation.md)** -- The interest-based negotiation execution that precedes this skill's closing and delivery techniques; master cooperative negotiation to generate the deal, master this skill to close and sustain it. +- **[Competitive Negotiation](competitive-negotiation.md)** -- The value-claiming execution that often runs in parallel; delivering the deal requires managing both cooperative and competitive dynamics through to closure. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's theoretical framework; this skill operationalises the preparation, obstacle management, and satisfaction dimensions the model assumes but does not detail. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- Influence principles inform both tactical awareness and satisfaction engineering, using consistency and social proof to anchor agreement. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust is the substrate of satisfaction; low-trust deals require heavier process and documentation to compensate for the absence of relational satisfaction. +- **[Coalition and Partnership Games](../game-theory/coalition-and-partnership-games.md)** -- Multi-party deal delivery requires understanding Shapley Value allocation and core stability to ensure all coalition members perceive the outcome as fair. diff --git a/plugins/foreman/content/skills/negotiation/negotiation-mindset-and-self.md b/plugins/foreman/content/skills/negotiation/negotiation-mindset-and-self.md new file mode 100644 index 0000000..ec3a091 --- /dev/null +++ b/plugins/foreman/content/skills/negotiation/negotiation-mindset-and-self.md @@ -0,0 +1,224 @@ +--- +name: "negotiation-mindset-and-self" +description: "Builds the internal foundation required before entering any + negotiation: identity as a negotiator, strategic self-awareness, emotional + self-management, assumption auditing, and deliberate style selection. Provides + practical self-assessment checklists and pre-negotiation protocols. Use when + preparing mentally for a high-stakes conversation, diagnosing why past + negotiations underperformed, recognising negotiation dynamics in daily + business interactions, coaching team members on negotiation readiness, or + choosing between competitive and cooperative approaches for an upcoming deal." +version: "1.0.0" +category: "negotiation" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - self-awareness + - emotional-management + - strategy + - preparation + - mindset + - decision-making +related_skills: + - competitive-negotiation + - win-win-negotiation + - negotiation-game-theory + - thomas-kilmann-conflict + - trust-equation + - stoic-unbiased-thought +author: "Fatih Guner" +--- + +# Negotiation Mindset and Self-Management + +Carrie Fisher once observed that everything is negotiable -- whether or not the negotiation is easy is another thing. The word itself derives from the Latin *negotiatus*: to carry on business. Not some business. Not the dramatic, table-pounding, term-sheet-waving kind. All of it. The founder who thinks negotiation begins when a term sheet lands on the desk has already lost dozens of negotiations that week -- with a co-founder over roadmap priorities, with an engineer over deadline expectations, with a landlord over lease terms, with a spouse over who handles school pickup so the pitch meeting can happen. The failure is not in technique. The failure is in identity. Most professionals do not see themselves as negotiators, and that blindness is extraordinarily expensive. + +--- + +## The Framework + +### Step 1: Adopt the Negotiator Identity + +The single largest barrier to negotiating well is not recognising when a negotiation is happening. A strategic communication process aimed at making a deal or solving a problem -- that is the working definition. By this standard, anyone in a business role spends the majority of their waking hours negotiating. Founders spend closer to all of them. + +The identity shift is concrete, not motivational. It means approaching every interaction with three questions: + +- What outcome do I want from this conversation? +- What does the other party want? +- What is the gap, and how will I close it? + +When these questions become habitual, conversations that previously felt like "just talking" reveal themselves as negotiation -- and become manageable with a framework rather than improvisation. + +**The cost of not seeing it:** During the Cuban Missile Crisis, certain military advisers nearly triggered nuclear war because they treated ship positioning as a military operation rather than what it actually was -- a language of negotiation between Kennedy and Khrushchev. The example is extreme. The principle is universal. Misidentifying a negotiation as something else leads to the wrong actions, wrong tone, and wrong outcomes. + +### Step 2: Confront the Comfort Trap + +Michael Porter's dictum -- "the essence of strategy is choosing what not to do" -- applies with particular force to negotiation. The natural human impulse is to do what feels comfortable: agree quickly to avoid tension, concede generously to preserve goodwill, avoid difficult requests because they feel awkward. Comfort is the enemy of strategy. + +A practical test: fold your arms. Now reverse them -- put the bottom arm on top. The physical awkwardness mirrors the psychological discomfort of asking for more than feels polite, holding silence after a counter-offer, or saying no to someone whose approval matters. Negotiation mastery requires doing hard, uncomfortable things with composure -- repeatedly, until the discomfort no longer shows. + +**The progression:** + +1. Develop knowledge of negotiation mechanics (this skill and its siblings) +2. Convert knowledge into practised skills through deliberate rehearsal +3. Skills produce confidence in the moment +4. Confidence enables strategic action under pressure + +### Step 3: Manage Yourself in the Face of Uncertainty + +Negotiations are defined by incomplete information. The other party's true bottom line, their alternatives, their internal politics, their timeline pressures -- none of this is fully visible. Deception (within ethical bounds) is an accepted feature of the process, not a bug. Sellers claim they cannot go a penny lower. Buyers claim budget constraints that may not exist. The uncertainty this creates tempts negotiators into one of two traps: naive trust or reflexive suspicion. + +**The Four-Question Self-Audit** (to be run before every significant negotiation): + +| Question | Purpose | +|----------|---------| +| What assumptions am I making to fill in the information I do not have? | Surfaces hidden assumptions before they drive decisions | +| What is the basis for these assumptions, and is that basis legitimate? | Separates evidence-based reasoning from wishful thinking | +| Am I building strategy on what I hope to be true or what is actually true? | Hope is not a strategy -- particularly not a negotiation strategy | +| Can I rely on the information I am using, and is it consistent with other evidence? | Tests whether data sources are credible and internally coherent | + +**A cautionary pattern:** A founder signs a partnership agreement with a friend's company, trusting verbal promises about marketing support, co-selling resources, and integration timelines. None are written into the contract. Six months later, the friend's company is acquired, the new owner has no knowledge of the promises, and the founder is locked into a disadvantageous agreement with no recourse. The error was not trusting a friend. The error was failing to audit the assumption that friendship and contractual obligation are the same thing. + +### Step 4: Choose Your Negotiation Style Deliberately + +Two fundamental approaches exist -- competitive and cooperative -- and the choice between them should never be left to temperament. + +**Competitive approach:** Claims value. Treats the pie as fixed. Uses ambitious asks, firm positions, and calculated concessions. Appropriate when the issue matters more than the relationship, or when the other party is already competing. (For deep execution, see [Competitive Negotiation](competitive-negotiation.md).) + +**Cooperative approach:** Creates value. Treats the pie as expandable. Uses interest exploration, option generation, and joint problem-solving. Appropriate when the relationship is critical, or when mutual gains are genuinely available. (For the theoretical foundation, see [Win-Win Negotiation](../frameworks/win-win-negotiation.md).) + +**The Thomas-Kilmann grid adapted for negotiation:** + +| | Low Issue Importance | High Issue Importance | +|---|---|---| +| **Low Relationship Importance** | Avoid (do not engage) | Compete (claim value) | +| **High Relationship Importance** | Accommodate (concede gracefully) | Collaborate or Compromise | + +The critical insight: the best outcomes accrue to negotiators who can execute both styles and switch between them as conditions demand. A founder who can only cooperate will be exploited by competitive counterparts. A founder who can only compete will destroy relationships that the business depends on. + +### Step 5: Apply Axelrod's Protocol for Uncertain Situations + +When the other party's approach is unknown, a robust default strategy exists -- derived from Robert Axelrod's tournament of Prisoner's Dilemma strategies: + +1. **Start cooperatively.** Test whether the other party will reciprocate. Cooperation is more efficient when both sides participate. +2. **Respond in kind.** If they compete, match the competition immediately. Delayed retaliation signals that exploitation is tolerable. If they cooperate, continue cooperating. +3. **Forgive.** When a competitive counterpart shifts toward cooperation, reciprocate. Holding grudges locks both parties into value-destroying competition. +4. **Be clear.** The other party must understand two things: cooperation will be rewarded, and competition will be matched. Clarity on both points builds the right kind of trust. + +This protocol prevents the two most common negotiation failures: cooperating with a shark (getting exploited) and competing with a collaborator (destroying a valuable relationship). + +### Recognising Signals in the Other Party's Moves + +Every move in a negotiation carries both substance (what is exchanged) and a signal (what the move reveals about the other party's strategy). An outrageously aggressive opening offer signals competitive intent. A reasonable offer paired with genuine questions about your priorities signals cooperative intent. Read the signal, not just the substance. + +--- + +## Prompts + +**Prompt 1 -- Negotiator Identity Audit:** +> I am a [role] at a [stage] company. List every interaction I likely have in a typical week that qualifies as a negotiation under this definition: "a strategic communication process to make a deal or solve a problem." For each, identify what is being negotiated, who the counterpart is, and what I typically leave on the table by not approaching it strategically. Then recommend the three highest-value negotiations I should prepare for deliberately. + +**Prompt 2 -- Pre-Negotiation Self-Assessment:** +> I am about to enter a negotiation regarding [describe situation]. Walk me through the Four-Question Self-Audit: (1) What assumptions am I likely making? (2) Are those assumptions evidence-based or hope-based? (3) What information am I relying on, and how reliable is it? (4) What is my default emotional response to uncertainty -- trust or suspicion -- and how might that default hurt me here? Then recommend specific preparation steps. + +**Prompt 3 -- Style Selection:** +> I need to negotiate [describe deal] with [describe counterpart and relationship]. Using the competitive vs. cooperative framework, help me determine: (1) How important is the issue relative to the relationship? (2) What signals has the other party already sent about their likely approach? (3) Should I lead with competition or cooperation? (4) What would trigger a switch to the other approach mid-negotiation? Provide a decision rationale I can brief to my team. + +**Prompt 4 -- Assumption Stress-Test:** +> Here are the key assumptions underlying my negotiation strategy for [describe deal]: [list assumptions]. For each assumption, assess: (a) what evidence supports it, (b) what evidence contradicts it, (c) what would happen to my strategy if this assumption is wrong, and (d) how I can verify or de-risk it before the negotiation begins. + +--- + +## Use Cases + +**Idea-Stage Founder Negotiating a Co-Founder Agreement** + +Two friends decide to build a company together. One has the technical skills; the other has the commercial relationships. Neither frames the equity conversation as a negotiation -- it feels too transactional for a friendship. They split 50/50 "because it's fair" without discussing vesting, decision rights, IP assignment, or what happens if one party leaves. Eighteen months later, the commercial co-founder contributes less and less while the technical co-founder builds the product. Resentment builds. The company fractures. The failure began with an identity problem: neither person saw themselves as a negotiator in the moment that mattered most. Applying the identity shift, the self-audit, and the style-selection grid would have surfaced the real issues -- contribution expectations, risk tolerance, exit terms -- before they became crises. + +**Growth-Stage CEO Preparing for a Board Negotiation** + +A Series A company needs to extend its runway by reducing burn rate. The CEO must negotiate with the board over whether to cut headcount (the board's preference) or renegotiate vendor contracts and defer a product line (the CEO's preference). The CEO's default style is accommodating -- she joined the board to cooperate, not fight. The self-audit reveals her core assumption: "If I push back, the board will lose confidence in me." Stress-testing this assumption uncovers that one board member has explicitly said he values "founders who defend their strategy with evidence." The CEO shifts from accommodation to a collaborative stance -- competing on substance (defending her preferred approach with data) while cooperating on style (framing the conversation as joint problem-solving). The board approves a hybrid plan. + +**Early-Traction Startup Negotiating First Enterprise Contract** + +A B2B SaaS startup receives a procurement-drafted contract from a large customer. The contract includes 120-day payment terms, unlimited liability, and IP assignment for all customisations. The founder's instinct: sign it, because losing the customer would be devastating. The Four-Question Self-Audit exposes the assumption that "this is our only shot at an enterprise customer." Research reveals three other companies in the pipeline at earlier stages. The founder's standalone value is not zero -- it is the value of pursuing those three alternatives without the drag of a punitive contract. Armed with this clarity, the founder competes on the three most damaging terms while cooperating on everything else, securing 45-day payment terms, capped liability, and shared IP ownership. + +--- + +## Anti-Patterns + +1. **Permanent Comfort Orientation.** Avoiding difficult conversations, accepting the first offer, and rationalising capitulation as "being reasonable." Comfort feels like wisdom. It is usually the absence of strategy. A negotiator who never feels uncomfortable is a negotiator who never asks for enough. + +2. **Identity Denial.** Insisting that "I'm not a negotiation person" or "I just focus on the product/code/numbers." This is not humility; it is abdication. Every professional negotiates constantly. The only question is whether they do it deliberately or accidentally. + +3. **Assumption Laundering.** Running the Four-Question Self-Audit but answering dishonestly -- converting hopes into "reasonable assumptions" without evidence. The audit works only with ruthless honesty. The founder who writes "our BATNA is strong" while knowing no other investor has returned a call is performing self-deception theatre. + +4. **Style Rigidity.** Knowing only one mode -- either always cooperative (which invites exploitation) or always competitive (which destroys relationships). The value is in the ability to switch. A founder who cooperates with a shark gets eaten. A founder who competes with a genuine collaborator drives away the partnership. + +5. **Confusing Personality with Strategy.** Introverts assuming they cannot negotiate effectively. Extroverts assuming their charm is a substitute for preparation. Research from Northwestern University demonstrates that even minimal rapport-building -- a five-minute phone call before a negotiation -- quadruples the likelihood of reaching a favourable agreement. Personality is a starting condition, not a destiny. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder agreements, early advisor terms, first vendor contracts | Every agreement sets a precedent. The identity shift is most critical here -- founders who do not see these early conversations as negotiations create structural problems that compound for years. | +| Validation | Pilot customer terms, angel/pre-seed fundraising, early hires | Uncertainty is maximal. The Four-Question Self-Audit is the primary tool. Assumptions about customer willingness to pay, investor interest, and hire motivations must be tested ruthlessly. | +| Early Traction | First enterprise contracts, seed fundraising, key hires with equity | Style selection becomes critical. Some counterparts (procurement teams, experienced investors) are professionally competitive. Recognising the game being played -- through signal reading, not wishful thinking -- determines whether the founder cooperates or competes. | +| Growth | Series A/B negotiations, strategic partnerships, executive hiring | The founder negotiates with increasingly sophisticated counterparts. Axelrod's protocol becomes the default: start cooperative, match competition, forgive pivots, be clear about boundaries. Emotional self-management under high-stakes pressure separates effective founders from reactive ones. | +| Scale | M&A discussions, board governance, large customer renewals | Negotiations involve professional negotiators (lawyers, bankers, corporate development). The founder's role shifts from executing negotiations to setting strategy and managing the team that executes. Self-audit at this stage focuses on whether the founder's assumptions about the company's value are grounded in evidence or ego. | + +--- + +## Output Template + +```markdown +# Pre-Negotiation Self-Assessment: [Deal/Situation] + +## Negotiator Identity Check +- **Am I treating this as a negotiation?** [Yes/No -- if No, reframe] +- **What is being negotiated?** [Specific outcomes at stake] +- **Who is my counterpart, and what is their likely approach?** [Competitive/Cooperative/Unknown] + +## Four-Question Self-Audit +| Question | My Answer | Evidence Quality | +|----------|-----------|-----------------| +| What assumptions am I making? | [List each assumption] | [Strong/Weak/None] | +| Are these assumptions evidence-based? | [For each: evidence or hope?] | | +| Am I building on truth or wishful thinking? | [Honest assessment] | | +| Is my information reliable? | [Source and consistency check] | | + +## Style Selection +- **Issue importance (1-10):** [Score] +- **Relationship importance (1-10):** [Score] +- **Recommended approach:** [Compete / Cooperate / Collaborate / Compromise / Avoid] +- **Trigger to switch approach:** [Specific signal that would change my strategy] + +## Comfort Zone Audit +- **What hard thing does this negotiation require me to do?** [Specific action] +- **What is my default avoidance behaviour?** [Conceding early / Avoiding the topic / Over-preparing without acting] +- **How will I overcome it?** [Rehearsal plan, accountability partner, or process commitment] + +## Uncertainty Map +- **What do I not know?** [List unknowns] +- **What is the other party likely hiding?** [Estimated hidden information] +- **What questions will I ask to reduce uncertainty?** [Specific questions] +``` + +--- + +## Related Skills + +- **[Competitive Negotiation](competitive-negotiation.md)** -- The execution companion for the competitive approach selected through this skill's style framework; covers anchoring, the ask, and concession strategy. +- **[Cooperative Negotiation](cooperative-negotiation.md)** -- The execution companion for the cooperative approach; empathy deployment and interest discovery techniques for expanding the deal before dividing it. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the theoretical architecture for the cooperative approach; this skill decides when to use it. +- **[Negotiation Game Theory](../game-theory/negotiation-game-theory.md)** -- The mathematical layer beneath style selection; bottom-line calculations and Nash Product analysis inform whether the deal surplus justifies engaging at all. +- **[Thomas-Kilmann Conflict](../frameworks/thomas-kilmann-conflict.md)** -- The conflict-mode instrument that underpins the style-selection grid used here. +- **[Stoic Emotional Mastery](../stoic/stoic-emotional-mastery.md)** -- The Stoic practice of pausing before reacting to impressions provides the philosophical foundation for the composure management that effective negotiation demands. diff --git a/plugins/foreman/content/skills/people/connecting-with-people.md b/plugins/foreman/content/skills/people/connecting-with-people.md new file mode 100644 index 0000000..9adeaed --- /dev/null +++ b/plugins/foreman/content/skills/people/connecting-with-people.md @@ -0,0 +1,233 @@ +--- +name: "connecting-with-people" +description: "Applies advanced interpersonal techniques for building genuine, lasting connections in entrepreneurial contexts. Covers the power of validation as the deepest form of listening, leading with 'How can I help you?' as a first-meeting strategy, maintaining authentic online identity, vulnerability as a professional strength, and the Platinum Rule that supersedes the Golden Rule by treating others as they want to be treated. Use when building investor relationships, resolving cofounder conflicts, designing customer-experience strategy, navigating cultural differences in international partnerships, or cultivating the authentic personal brand that underlies fundraising, hiring, and sales." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - validation + - vulnerability + - platinum-rule + - authenticity + - online-identity + - empathy + - connection +related_skills: + - understanding-people + - meeting-the-right-people + - reading-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +# Connecting with People + +The Golden Rule says "treat others as you'd want to be treated." The Platinum Rule says "treat others as *they* want to be treated." The difference is enormous. + +A founder added his own sales force to a joint venture, reasoning that if a partner did the same for him, he would be delighted. His partner was furious -- interpreting the move as interference, distrust, and territorial encroachment. The Golden Rule had produced the exact opposite of its intended effect because it substituted the founder's preferences for his partner's. The Platinum Rule requires a harder discipline: suspending your own frame of reference and inhabiting someone else's. It demands the listening, reading, and understanding skills covered in this category's sibling frameworks -- and then goes one step further, translating comprehension into behaviour calibrated to the other person's actual needs. + +Connection is not a feeling. It is a practice -- a series of specific, learnable behaviours that, applied consistently and sincerely, produce the trust upon which every entrepreneurial relationship depends. + +--- + +## The Framework + +Connecting with people operates through five techniques, arranged from the most immediately applicable to the most structurally transformative. + +### Technique 1: Validate, Validate, Validate + +Validation is mirroring's advanced form. Where mirroring repeats the speaker's words, validation names the speaker's *emotions* -- and demonstrates that those emotions are reasonable, even if the validator does not share them. + +**The distinction:** + +- **Mirroring:** "I hear you saying your bill was $250 more than expected." +- **Validation:** "You've been on hold for an hour and your bill is $250 wrong. You must be furious." + +Validation accomplishes something that no other technique in this category replicates: it disarms negative emotion *before* the substantive problem is addressed. A customer-service representative who validates an angry caller's frustration before attempting a fix will resolve the issue faster, with higher satisfaction, than one who jumps to solutions. The caller's cognitive bandwidth, previously consumed by anger, is freed for collaboration the moment she feels understood. + +**Execution protocol:** + +1. Listen for the emotional content beneath the words. +2. Name the emotion explicitly: "That must be frustrating." "You sound worried." "I can hear how excited you are." +3. Demonstrate resonance: "If that happened to me, I'd feel the same way." +4. Only then proceed to the substantive response. + +**The risk:** Validation requires accurate emotional identification. Misreading the emotion -- calling someone "angry" when they are "disappointed," or "anxious" when they are "cautious" -- produces dissonance rather than connection. When uncertain, validate tentatively: "Sounds like that was pretty frustrating?" The question mark invites correction rather than imposing interpretation. + +Validation is not agreement. Validating a cofounder's fear about a strategic decision does not mean the fear is warranted. It means the fear is acknowledged, which paradoxically makes the cofounder more receptive to evidence that the fear may be unfounded. + +### Technique 2: Lead with "How Can I Help You?" + +The single most productive question in a first meeting is not "What do you do?" or "Tell me about your company." It is: "How can I help you?" + +The question works on two levels: + +- **If they answer:** You receive a concrete opportunity to provide value, creating a reciprocity bond that operates on Cialdini's first principle without calculation or artifice. +- **If they decline:** You have demonstrated a care-first orientation that differentiates you from the vast majority of professionals who approach first meetings with extraction in mind. + +Either outcome positions you favourably. A financial adviser who asked "How can I help you?" at a first meeting never pitched his services. He made three introductions. The person he had helped hired him as a client months later -- not because the adviser asked, but because the decision to hire him felt organic and self-directed. The most powerful sales technique is the one where the customer sells themselves. + +**Prerequisites for effectiveness:** + +- **Know your sphere of influence.** Before asking, ensure you actually have the capacity to help. Offering help without resources to deliver it is worse than not offering. +- **Do your research.** Arrive at the meeting with three or four ways you could plausibly help, based on what you know about the person and their context. +- **Follow through.** The question creates an implicit promise. Failing to deliver on offered help destroys the trust the question was designed to build. + +### Technique 3: Online Identity Equals Real Identity + +The internet tempts people to construct dual identities: a polished professional persona for LinkedIn and a private self hidden behind privacy settings. The argument is that this partition is both unsustainable and counterproductive. + +**The case for unified identity:** + +Authenticity is a competitive advantage in saturated digital environments. Over 100 million blogs exist; the differentiator is not polish but voice. A founder who publishes a candid account of near-miss payroll failures, partnership arguments, and operational chaos attracts more trust -- and more clients -- than one whose content reads like a press release. Vulnerability signals confidence: only someone secure in their position would risk exposure. + +The 82% statistic is instructive: in survey data, 82% of respondents report higher trust in brands whose senior leadership uses social media authentically. The CEO who tweets about both product launches and personal struggles is perceived as human. The CEO whose digital presence is managed by a communications team is perceived as a brand -- which is to say, as something designed to extract value from you. + +**Practical application for founders:** + +- Eliminate the boundary between "professional" and "personal" social media profiles. Maintain one voice across all platforms. +- Share failures as well as successes. The failure posts will generate more engagement, more trust, and more business. +- Write in your own voice, including the imperfections. Ghostwritten perfection signals inauthenticity. +- Accept that some people will be repelled by your authentic self. These are people you would not want as customers, investors, or employees anyway. + +### Technique 4: Crying Is for Winners (Vulnerability as Strength) + +Professional culture teaches that emotional display is weakness. The evidence suggests the opposite. + +At one management retreat, a CEO opened with the most difficult experience of his life -- his father's mental illness -- and cried in front of his entire executive team. Rather than damaging his authority, the vulnerability catalysed a cascade: three of five team members also cried, sharing their own profound experiences. By the end of the session, executives who had known each other for years reported feeling closer than they had felt with lifelong friends. + +**The mechanism:** Vulnerability operates as a trust accelerator. The willingness to be emotionally exposed signals that the environment is safe for others to do the same. When both parties drop their professional armour simultaneously, the resulting connection is qualitatively different from -- and significantly stronger than -- the rapport built through conventional professional interaction. + +**Boundary conditions:** + +- Vulnerability requires a safe environment. Creating that environment -- establishing confidentiality, modelling the behaviour first, beginning with structured exercises -- is the leader's responsibility. +- Vulnerability is not performance. Crying to manipulate sympathy is detectable and devastating to credibility. +- The appropriate depth of vulnerability scales with the relationship's maturity. A cofounder retreat warrants deep emotional disclosure. A first investor meeting does not. +- Cultural context matters. The degree of emotional expression considered appropriate varies significantly across cultures, industries, and individual comfort levels. + +### Technique 5: The Platinum Rule + +The Golden Rule assumes that your preferences are universal. They are not. + +**Platinum Rule application matrix:** + +| Relationship | Golden Rule Failure | Platinum Rule Approach | +|-------------|--------------------|-----------------------| +| Cofounder (Type 5, introverted) | You celebrate wins publicly because you love public recognition | Ask privately how they prefer to be recognised -- they may prefer a quiet acknowledgement | +| Investor (risk-averse, fiduciary mindset) | You send optimistic updates because you would want to hear good news | Proactively address risks in every update because *they* want to know what could go wrong | +| Customer (enterprise, compliance-driven) | You move fast and ship frequently because you value speed | Provide advance notification and documentation because they value predictability | +| Employee (new parent, flexibility-oriented) | You offer a promotion with more responsibility because you would jump at it | Ask what they actually need -- it may be flexibility, not a title | + +The Platinum Rule is not intuitive. It requires the active suppression of the empathy heuristic -- the assumption that the other person feels what you would feel -- and its replacement with genuine inquiry. The simplest implementation: when uncertain about what someone wants, ask. "If I were you, I'd want X. What do *you* want?" + +--- + +## Prompts + +**Prompt 1 -- Validation Strategy for a Conflict:** +> I am in a conflict with [describe person, role, and nature of conflict]. Their position is [describe]. My position is [describe]. I believe their underlying emotion is [guess]. Design a validation-first approach: what specific validation statements should I open with, how should I test whether I have identified the correct emotion, and how do I transition from validation to problem-solving without negating the validation? + +**Prompt 2 -- First-Meeting Help-First Strategy:** +> I have a first meeting scheduled with [describe person and context]. Based on what I know about them [provide background], design three specific ways I could offer help before asking for anything. For each, explain why it would be valuable to them, what resources or connections I would need to deliver, and how to frame the offer so it feels genuine rather than transactional. + +**Prompt 3 -- Authenticity Audit:** +> Audit my online presence across [list platforms]. For each platform, assess: (a) how authentic is the voice compared to how I actually communicate, (b) what am I hiding that would build trust if shared, (c) where am I performing rather than connecting, and (d) what is one specific change I could make this week to increase genuine vulnerability? Be direct -- politeness about inauthenticity defeats the purpose. + +**Prompt 4 -- Platinum Rule Relationship Redesign:** +> For the following key relationships [list 3-5 with descriptions], I have been applying the Golden Rule -- treating them as I would want to be treated. For each relationship, identify where my preferences likely diverge from theirs. Then design a Platinum Rule approach: what does each person actually want, how can I determine this with certainty (including questions to ask), and what specific behaviour changes should I implement? + +--- + +## Use Cases + +**Validation-Stage Founder Handling Customer Rejection** + +A B2B SaaS founder receives consistently polite rejections from enterprise prospects after demo calls. She restructures her approach using validation-first technique: instead of opening the next demo with product features, she opens with "Before I show you anything, I'd like to understand what is most frustrating about your current workflow." The prospect describes a painful manual process. The founder validates: "That sounds genuinely exhausting -- doing that manually every week when you know it could be automated. That must feel like a waste of your team's talent." The prospect, visibly relieved at being understood rather than pitched, leans in. The demo that follows is half the length and twice as effective because the founder addresses only the validated pain point. Conversion rate from demo to pilot increases by 40%. + +**Early-Traction Cofounder Conflict Resolution** + +Two cofounders are deadlocked over whether to pursue enterprise customers or remain consumer-focused. Founder A (the CEO, a Golden Rule practitioner) has been sending Founder B detailed strategic memos, because that is how Founder A prefers to receive information. Founder B (the CTO, a verbal processor) finds the memos alienating and interprets them as a power play. Applying the Platinum Rule, Founder A asks: "How would you prefer we work through strategic decisions? I've been sending memos because that's how I think best, but I want to know how *you* think best." Founder B says he needs to talk it through verbally, in real time, on a whiteboard. They schedule a weekly two-hour strategy session in the format Founder B prefers. The deadlock breaks in three sessions -- not because either position changed, but because the communication channel finally matched the recipient. + +**Growth-Stage CEO Building a Public Brand** + +A CEO has maintained a carefully curated LinkedIn presence -- polished posts, professional headshots, only good news. Engagement is low and inbound interest minimal. She publishes a single post describing a month when the company nearly missed payroll, the argument with her cofounder that almost ended the partnership, and what she learned. The post generates 50x her normal engagement. Three former prospects re-engage. An investor DMs to schedule a meeting, citing the post's honesty as the reason. She begins publishing weekly with the same authentic voice -- sharing wins and failures in equal measure. Within six months, her personal brand becomes the company's most effective top-of-funnel channel. + +--- + +## Anti-Patterns + +1. **Validation as Capitulation.** Confusing "I understand how you feel" with "You are right." Founders who cannot validate without conceding lose the technique's power. Validation acknowledges the emotion; it does not surrender the position. The investor who is anxious about burn rate deserves to have that anxiety validated. The investor does not necessarily deserve a spending cut. + +2. **Weaponised Vulnerability.** Deploying personal stories strategically to create emotional obligation. The founder who cries in every pitch meeting is not being vulnerable -- he is performing vulnerability, and the audience will eventually recognise the pattern. Genuine vulnerability is unplanned, context-appropriate, and offered without expectation of return. + +3. **Help-First as a Long Con.** Asking "How can I help you?" with the pre-calculated expectation that the help will be reciprocated with a specific favour. Cialdini's reciprocity principle operates naturally and does not require engineering. The moment the offer feels transactional, the trust it was designed to build evaporates. + +4. **Platinum Rule Without Data.** Attempting to treat others as they want to be treated without actually knowing what they want. The Platinum Rule is not an invitation to assume more creatively; it is an instruction to inquire more directly. When in doubt, ask. The question itself demonstrates the principle. + +5. **Forced Authenticity Online.** Sharing personal stories because a framework told you to, not because the sharing is genuine. Readers detect performative vulnerability with the same accuracy they detect performative confidence. The online identity should emerge from a genuine integration of personal and professional self, not from a content strategy that mandates "one vulnerable post per week." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder connection depth | At the idea stage, the cofounder relationship is the company's structural foundation. Platinum Rule calibration and vulnerability exercises between cofounders prevent the communication breakdowns that kill partnerships before products launch. | +| Validation | Customer empathy and validation | Customer discovery is an exercise in validation. The founder who validates customer frustration before proposing a solution generates deeper insights and stronger early-adopter loyalty than one who leads with the product. | +| Early Traction | Hiring through authentic brand | Talent is attracted to authentic founders. The early-traction stage is where the CEO's online identity becomes a recruiting tool -- candidates who resonate with the founder's genuine voice self-select into the culture. | +| Growth | Stakeholder relationship management | Growth introduces conflicting stakeholder needs -- investors want metrics, employees want meaning, customers want reliability. The Platinum Rule becomes a stakeholder-management framework: each audience receives communication in the format they prefer. | +| Scale | Cultural embedding | At scale, connection techniques must be institutionalised. Validation becomes a customer-service training module. The Platinum Rule becomes a management philosophy. Vulnerability becomes a cultural norm, modelled from the top. | + +--- + +## Output Template + +```markdown +# Connection Strategy: [Relationship / Situation] + +## Validation Plan +- **Anticipated emotions from other party:** [List with confidence level] +- **Validation statements prepared:** + 1. [Statement addressing primary emotion] + 2. [Tentative validation for uncertain emotion: "It sounds like...?"] +- **Transition to substance:** [How to move from validation to problem-solving] + +## Help-First Inventory +| Person | What They Likely Need | What I Can Offer | Delivery Timeline | +|--------|----------------------|-----------------|-------------------| +| [Name] | [Need] | [Specific help] | [When] | + +## Platinum Rule Adjustments +| Stakeholder | My Default (Golden Rule) | Their Preference (Platinum Rule) | Behaviour Change | +|------------|------------------------|--------------------------------|-----------------| +| [Name/Role] | [What I would do naturally] | [What they actually want] | [Specific adjustment] | + +## Authenticity Check +- **Online presence alignment:** [Honest / Curated / Disconnected] +- **One change to increase authenticity this week:** [Specific action] +- **Vulnerability appropriate for current context:** [What to share and what to hold] + +## 30-Day Connection Goals +1. [Specific validation practice] +2. [Specific Platinum Rule implementation] +3. [Specific authenticity experiment] +``` + +--- + +## Related Skills + +- **[Understanding People](understanding-people.md)** -- Understanding provides the motivational map that the Platinum Rule requires; without knowing what drives someone, treating them as they want to be treated is guesswork. +- **[Reading People](reading-people.md)** -- Reading provides the real-time signal detection that validation depends on; accurate validation requires accurately reading the emotion before naming it. +- **[Meeting the Right People](meeting-the-right-people.md)** -- Meeting creates the initial contact; connecting transforms that contact into a relationship that compounds over time. +- **[Carnegie's Win Friends](../frameworks/carnegie-win-friends.md)** -- Carnegie's principle of "arousing an eager want" is the 1936 precursor to the Platinum Rule; this modernises it with explicit emphasis on the other person's frame of reference. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's empathy domain provides the theoretical foundation for validation and the Platinum Rule. +- **[Stoic Virtue and Kindness](../stoic/stoic-virtue-and-kindness.md)** -- The Stoic emphasis on kindness and mutual interdependence provides the philosophical foundation for the genuine care that connection techniques operationalise. diff --git a/plugins/foreman/content/skills/people/influencing-and-persuading.md b/plugins/foreman/content/skills/people/influencing-and-persuading.md new file mode 100644 index 0000000..ffae854 --- /dev/null +++ b/plugins/foreman/content/skills/people/influencing-and-persuading.md @@ -0,0 +1,256 @@ +--- +name: "influencing-and-persuading" +description: "Provides founders with Socratic influence techniques, confidence projection methods, and patience-based persuasion strategies for converting stakeholders without overt selling. Covers idea-seeding (making others believe your idea is theirs), the paradox of persuasion (listening as the primary influence tool), storytelling over selling, persistence mechanics, strategic asks, choosing happiness over rightness, managing up, authentic self-promotion, and time as a persuasion ally. Use when pitching investors, aligning cofounders on direction, winning a reluctant customer, navigating board resistance, asking for something audacious, or needing to influence without positional authority." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - persuasion + - influence + - socratic-method + - storytelling + - listening + - confidence + - persistence + - managing-up + - asking + - patience +related_skills: + - carnegie-win-friends + - cialdini-influence + - persuasion-and-influence + - trust-equation + - win-win-negotiation +author: "Fatih Guner" +--- + +# Influencing and Persuading + +SHUT UP. The most powerful persuasion tool is not a pitch deck, not a compelling argument, not even a brilliant idea. It is silence. The discipline to close one's mouth, ask a question, and wait -- genuinely wait -- while the other person fills the void with their own reasoning, their own objections, and eventually their own path to the conclusion you wanted them to reach all along. A Radio Disney sales rep once closed the largest contract of his career without demoing the product. He asked questions for twenty-five minutes. The buyer interrupted him to say: "Let's get started. Just let me know how billing works." Almost nobody can do this. Founders, by temperament, are talkers -- passionate, enthusiastic, overflowing with conviction. That enthusiasm is both their greatest asset and their most reliable saboteur. + +Carnegie documented the principle in 1936. What follows is not a repetition of those timeless rules (see `carnegie-win-friends` for the canonical framework) but a complementary set of tactical behaviours -- specific, modern, and suited to the asymmetric power dynamics that founders navigate daily: pitching people with more money, persuading people with more authority, and influencing people who have no obligation to listen. + +--- + +## The Framework + +Influence, practised well, operates through ten interlocking techniques. They are not sequential steps but a repertoire -- deployed situationally, combined as context demands. + +### Technique 1: Socratic Idea-Seeding + +The most effective way to get someone to adopt your idea is to make them believe they invented it. The mechanism is straightforward: + +1. **Never say "I have an idea."** Remove the first-person pronoun from the equation entirely. +2. **Paint the broad strokes.** Describe the desired outcome or the problem's contours. Let the other person colour inside the lines. +3. **Alternatively, paint the negative.** Describe what happens if the idea is *not* adopted. The listener's mind will generate a solution to prevent that outcome -- your solution. +4. **Embrace instantly.** The moment the other person articulates anything resembling your idea, praise it as theirs. Enthusiastically. +5. **Refine gently.** If their version is not quite right, suggest additions to "their" idea, reinforcing ownership throughout. + +A shopping mall client rejected a founder's marketing concept outright on Monday. By Tuesday, the same client pitched the identical concept back -- with one minor addition -- as her own idea. The founder said, "Great idea." The campaign generated over a million dollars in earned media and won the agency its first award. The question of whose idea it was became irrelevant. + +### Technique 2: Passion Plus Persistence + +Passion is common. Persistence is rare. The gap between the two explains most of the variance in influence outcomes. + +One salesperson called a Burger King regional marketing manager thirty-seven times over eight weeks. Each weekly voicemail was a parody of a pop song. Call thirty-six would have been a failure. Call thirty-seven was a $50,000 contract and a relationship that lasted fourteen years. The operational rule: persist until certainty of futility, not until discomfort. + +| Element | What most people do | What persistence requires | +|---------|-------------------|--------------------------| +| Follow-up cadence | 2-3 attempts, then quit | Systematic attempts until definitive resolution | +| Creative variation | Same message, same channel | Different hooks, different formats, escalating creativity | +| Emotional management | Dejection after first rejection | Treat each "no" as incomplete data | +| Stopping criterion | "They haven't responded" | "They have explicitly and irrevocably declined" | + +### Technique 3: Storytelling Over Selling + +Nobody likes being sold to. Everybody likes a good story. This asymmetry is the storyteller's arbitrage. + +A founder spent Thanksgiving bidding $165 for a domain name while his turkey went cold. He told that story on his blog as the product launch strategy. The article generated 50,000 views and thousands of downloads -- far outperforming any advertisement. The product was a storytelling app. The medium was the message. + +The conversion: take any product, service, or idea you want to sell. Identify a personal story that embodies the problem it solves or the transformation it enables. Structure it with characters, tension, and resolution. Tell that story instead of listing features. The listener's mirror neurons do the rest. + +### Technique 4: The Paradox of Persuasion (Shut Up and Listen) + +Listening is more persuasive than talking for five specific reasons: + +1. It reveals the other person's goals, dreams, needs, and pain -- the raw material of influence. +2. It makes the other person feel heard, which generates appreciation, respect, and openness. +3. It provides thinking time. Humans listen three times faster than they speak; the surplus bandwidth is strategic planning space. +4. Combined with mirroring and validation, it creates emotional connection stronger than any pitch. +5. It increases the probability that the other person will articulate their own problem -- the problem you can solve. + +**The script:** Ask one good question. Wait. Ask a follow-up based on what you heard. Wait again. Repeat for twenty-five minutes. Then -- and only then -- share your solution, framed as a response to what they told you. + +### Technique 5: Confidence Projection (Walk With Confidence) + +A man once walked into the American Music Awards with an expired crew pass from the previous year. He made eye contact with the security guard, nodded, and walked straight in. He ended up in the sixth row. The ticket was worthless. The confidence was not. + +The principle is not deception. It is that self-assurance -- posture, eye contact, calm greeting -- functions as a social credential. The acronym WWC (Walk With Confidence) encodes the practice: enter every room, every meeting, every pitch as though you belong there. Not arrogance. Quiet certainty. + +Practical application: before entering any high-stakes room, set your posture, make deliberate eye contact with the first person you see, and greet them by name if possible. The physiological act of walking upright and making eye contact shifts both your internal state and others' perception. + +### Technique 6: Ask for What You Want + +A top-performing salesperson did everything right -- rapport, listening, mirroring, product demonstration -- except close. She never asked for the sale. Within six months of learning to ask, she doubled her earnings. + +The failure mode is universal: fear of "no" produces an implicit guarantee of "no." The corrective is blunt. + +- After rapport and demonstration, ask directly: "Shall we move forward?" +- After a great investor meeting, ask directly: "Can we count on your commitment?" +- After delivering value to a mentor, ask directly: "Would you be willing to introduce me to [specific person]?" + +No ask is too audacious. A couple sponsored their wedding through corporate partnerships -- 1-800-Flowers, Smirnoff, Entenmann's -- generating $100,000 in trade value, $20,000 for charity, and $20 million in earned media. They got all of it because they asked. + +### Technique 7: Choose Happiness Over Rightness + +A man convinced against his will is of the same opinion still. Arguing typically solidifies the other party's opposition. The alternative: state your case once, clearly. Then choose to be happy rather than right. Walk away. + +The paradox: people who stop arguing for their position often get what they wanted. By removing pressure, they create space for the other person to arrive at the same conclusion independently. A founder argued with his wife about firing a nanny. He stopped pressing. The next day, she witnessed the problem herself and made the same decision on her own. + +**The operational rule:** In any disagreement where the other party will not move, mirror their position, validate their feelings, state that you are choosing happiness, and disengage. Revisit only after they initiate. + +### Technique 8: Manage Up + +Managing up is not sycophancy. It is the disciplined practice of understanding what matters most to the person above you and delivering on those priorities visibly. + +The method: + +1. Identify the five things most important to your boss, investor, or board chair. If uncertain, ask their peers. +2. Ensure your daily work visibly addresses those priorities. +3. Ensure your manager's peers see you addressing those priorities. +4. After demonstrating alignment, ask for what you want -- a raise, a schedule change, additional resources. + +A sales rep chronically late to work discovered his manager's true concern was respect, not punctuality. He spent three weeks demonstrating respect conspicuously. Then he proposed a shifted schedule. The manager not only agreed but claimed the idea as his own (see Technique 1). + +### Technique 9: Beyond the Humblebrag + +Self-promotion is necessary; narcissism is fatal. The balance: + +- Share accomplishments authentically, without false modesty. +- Promote others at a ratio of at least 3:1 -- three public endorsements of others for every personal accomplishment shared. +- When someone calls you a braggart, the defence is not humility theatre. It is a track record of generously amplifying others. + +### Technique 10: Make Time Your Friend + +Time is a persuasion tool, not an obstacle. A founder who meets with every stranger who requests thirty minutes has a calendar that reflects other people's priorities, not his own. The "office hours" system -- two hours per week in fifteen-minute slots -- filters for genuine interest and protects the time that belongs to employees, investors, customers, and family. + +Patience in persuasion means accepting that some decisions take weeks. Some take months. Rushing a reluctant investor or cofounder produces resistance. Structured patience -- maintaining presence without pressure -- produces trust. + +--- + +## Prompts + +**Prompt 1 -- Socratic Idea-Seeding Script:** +> I need to persuade [stakeholder role] to adopt [specific idea]. They have rejected direct proposals before. Help me craft a Socratic approach: what broad-strokes vision or negative scenario can I paint so they arrive at my conclusion independently? Provide the exact language I should use, including what to say when they propose a version of my idea. + +**Prompt 2 -- Listening-Based Influence Preparation:** +> I have a [meeting type] with [stakeholder] in [timeframe]. My goal is to get them to [desired outcome]. Draft a sequence of five open-ended questions that will lead them to articulate the problem my solution addresses. Include guidance on when to stay silent and how long to wait after each question. + +**Prompt 3 -- The Ask Formulator:** +> I want to ask [person/organisation] for [specific request]. This feels audacious. Help me (a) reframe the ask as mutually beneficial, (b) craft the exact words, and (c) identify the worst realistic outcome of asking versus the certain outcome of not asking. + +**Prompt 4 -- Managing Up Audit:** +> My [boss/investor/board chair] has the following priorities: [list]. My current work focuses on [list]. Identify the gaps between their priorities and my visible output. Suggest three specific actions I can take this week to better align and demonstrate that alignment. + +--- + +## Use Cases + +**Seed-Stage Founder Pitching a Sceptical Angel Investor** + +A pre-revenue SaaS founder met an angel investor who had publicly stated she only invested in companies with $10K+ MRR. Rather than pitching the product, the founder asked: "What would a company in [vertical] need to demonstrate for you to believe it could reach $10K MRR within six months?" The investor described exactly the traction metrics the founder's product was designed to deliver. The founder then asked: "What if someone could show you those leading indicators today?" The investor requested a follow-up meeting. She invested three weeks later. + +**Growth-Stage CEO Managing a Difficult Board Member** + +A Series A CEO faced a board member who consistently derailed strategy discussions with operational minutiae. Rather than confronting the behaviour, the CEO identified that the board member's core concern was risk mitigation. Before each board meeting, the CEO began sending a one-page risk summary directly to that member, 48 hours in advance. The operational digressions stopped within two meetings. The CEO never mentioned the problem. + +**Early-Traction Startup Closing an Enterprise Customer** + +A three-person startup was pitching a Fortune 500 procurement team. Instead of a product demo, the founder spent the first meeting asking questions about the company's biggest workflow pain points. She listened for forty minutes, asked one clarifying question, and in the final five minutes said: "It sounds like [summary of their pain]. We built something that addresses exactly that. Can I show you next Tuesday?" The procurement team fast-tracked the evaluation. + +--- + +## Anti-Patterns + +**The Premature Pitch.** Launching into features and benefits before understanding the listener's needs. Listening for five minutes and then talking for twenty-five is not the paradox of persuasion -- it is a conventional sales call with a slow start. + +**Manipulation Masquerading as Socratic Influence.** Idea-seeding works when the idea genuinely serves both parties. Using the technique to get someone to "invent" an idea that primarily benefits you while harming them is not influence; it is manipulation, and it erodes trust catastrophically when discovered. + +**Confusing Persistence with Harassment.** Thirty-seven calls works when each contact adds creative value and respects boundaries. Thirty-seven identical "just checking in" emails is not persistence; it is spam. The distinction: does each attempt offer something new, or does it merely repeat the demand? + +**Choosing Happiness as Avoidance.** "I choose to be happy" is a strategic withdrawal, not a permanent retreat. The technique requires you to state your position clearly first. Skipping the position-statement and jumping directly to disengagement is conflict avoidance, which produces resentment rather than resolution. + +**Managing Up Without Delivering Down.** Visible alignment with your manager's priorities means nothing if your team sees you neglecting their needs. Managing up is additive to competence, not a substitute for it. + +--- + +## By Stage + +| Stage | Primary Influence Target | Key Technique | +|-------|------------------------|---------------| +| Idea | Potential cofounders, early believers | Socratic idea-seeding; confidence projection when you have nothing tangible to show | +| Validation | Pilot customers, advisors | Listening-based influence; storytelling over selling when the product is immature | +| Early Traction | Lead customers, seed investors | The direct ask; persistence with creative variation | +| Growth | Board members, enterprise buyers, key hires | Managing up; choosing happiness over rightness in high-stakes disagreements | +| Scale | Executive team, institutional investors, partners | Time management as influence tool; authentic self-promotion at scale | + +At the idea stage, the founder's primary asset is conviction, and the primary risk is over-talking. Socratic seeding and confidence projection matter most because there is no product to demonstrate. At scale, the founder's calendar is the battleground -- how time is allocated signals priorities more loudly than any speech. + +--- + +## Output Template + +```markdown +# Influence Strategy Brief + +**Target:** [Name/Role of person to influence] +**Desired Outcome:** [Specific decision or action sought] +**Relationship Context:** [History, power dynamic, known concerns] + +## Pre-Meeting Intelligence +- Their top 3 priorities: [list] +- Their known objections or concerns: [list] +- What they value hearing from others: [data / stories / peer endorsement / vision] + +## Technique Selection +- [ ] Socratic idea-seeding (they need to feel ownership) +- [ ] Listening-first (their needs are unclear or unexpressed) +- [ ] Direct ask (relationship is strong, ask is clear) +- [ ] Storytelling (they respond to narrative over data) +- [ ] Managing up (ongoing relationship, need alignment) +- [ ] Patience play (timing is not right; maintain presence) + +## Prepared Questions (if listening-first) +1. [Open-ended question about their situation] +2. [Follow-up probing their pain point] +3. [Question connecting their pain to your solution] + +## The Ask (exact words) +> "[Precise language for the request]" + +## If They Say No +- Reframe: [alternative framing] +- Persistence plan: [next creative touchpoint and timing] +- Strategic withdrawal: [when to choose happiness and revisit later] + +## Follow-Up +- Thank-you method: [handwritten card / thoughtful gift / introduction] +- Timeline for next contact: [date] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends and Influence People](../frameworks/carnegie-win-friends.md)** -- The 1936 foundational principles that underpin Socratic influence and listening-based persuasion; this skill provides the modern tactical application. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- Seven psychological principles of persuasion as academic framework; this skill translates influence into behavioural scripts for entrepreneurial contexts. +- **[Persuasion and Influence](../leadership/persuasion-and-influence.md)** -- Daily micro-influence tactics for leaders in meetings and one-on-ones, complementary but focused on organisational dynamics. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Trust is the precondition for all influence; this framework quantifies its components. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- When influence conversations become formal negotiations, principled negotiation provides the structural framework. +- **[Reading People](reading-people.md)** -- The nonverbal signal detection and mirroring techniques provide the real-time feedback that effective influence requires to calibrate approach mid-conversation. diff --git a/plugins/foreman/content/skills/people/inspiring-and-retaining.md b/plugins/foreman/content/skills/people/inspiring-and-retaining.md new file mode 100644 index 0000000..7de4dcf --- /dev/null +++ b/plugins/foreman/content/skills/people/inspiring-and-retaining.md @@ -0,0 +1,286 @@ +--- +name: "inspiring-and-retaining" +description: "Equips founders with practical retention and inspiration techniques grounded in selfless leadership, strategic kindness, and relationship maintenance at scale. Covers making it about the audience (not you), the random-act-of-kindness mood reset, the homelessness perspective technique, praise-to-criticism ratios, surprise-and-delight as a variable reward system, handwritten thank-you cards as strategic instruments, daily introductions as network compounding, personalised gift-giving for investor and client retention, and content curation for staying top of mind. Use when team morale is declining, investor relationships need warming, key employees are at flight risk, preparing an inspiring presentation, or building a personal brand that sustains professional relationships at scale." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - inspiration + - retention + - gratitude + - thank-you-cards + - praise + - networking + - personal-brand + - surprise-and-delight + - introductions + - gifts +related_skills: + - employee-engagement-retention + - carnegie-win-friends + - teaching-and-leading + - influencing-and-persuading + - trust-equation +author: "Fatih Guner" +--- + +# Inspiring and Retaining + +THANK YOU CARD. In an age of unlimited text messages, instant emails, and algorithmic social feeds, a handwritten thank-you card is a strategic weapon -- and almost nobody deploys it. A study by DonorsChoose found that first-time donors who received a handwritten thank-you note were 38 percent more likely to donate again, and gave more when they did. The CEO of a multibillion-dollar property-restoration company writes handwritten birthday and thank-you cards to employees every single day. His handwriting is barely legible. The cards are priceless. + +The reason is scarcity. An email costs nothing to send and almost nothing to receive. A handwritten card requires purchasing stationery, finding a pen, composing a thought in ink that cannot be deleted, sealing an envelope, and delivering it by hand or post. Each step signals: this person matters enough that I spent irreplaceable time on them. In an economy where attention is the scarcest resource, a three-minute handwritten note outperforms a three-paragraph email by an order of magnitude. + +What follows is a collection of nine retention and inspiration practices -- each specific, each deployable this week, and each designed to compound over months and years into the kind of loyalty that no compensation package can purchase. + +--- + +## The Framework + +### Practice 1: It Is Not About You + +A speaker was about to address three thousand entrepreneurs in Mexico City. Stage fright had replaced his usual excitement. A fellow speaker approached and said: "Remember -- it's all about them, not you. Inspiring your audience is about helping them see their own vision, not yours." + +The principle applies universally. People do not care about you, your product, or your company -- they care about how those things affect their own lives, businesses, and futures. Every presentation, every pitch, every one-on-one should be structured around the audience's self-interest: + +- **Sales presentation:** slides should visualise the customer's life *without* the problem, not the product's feature set. +- **Team all-hands:** the vision should describe what success looks like *for the team members*, not for the company's valuation. +- **Investor update:** frame progress in terms of the investor's thesis and return expectations, not your operational pride. + +The trap is subtle because founders are trained to tell their story. Stories are useful -- but only as delivery vehicles for the audience's own aspirations. The question before every presentation: "What does my audience want their future to look like, and how does what I am sharing help them get there?" + +### Practice 2: The Homelessness Perspective Reset + +A founder was having the worst day of a bad week -- a toxic employee fired, four cities in four days, physically exhausted, emotionally depleted. He walked a mile to his favourite sushi restaurant. It was closed for renovations. He cried on the street. + +Then a homeless man asked for a quarter. The founder gave him twenty dollars. The mood transformation was instant: from depressed, overwhelmed, and stressed to blessed, fortunate, and energised. The cost of the intervention was $20 and forty-five seconds. + +A random act of kindness is an on-demand mood reset. The mechanism is dual: it forces attention outward (away from self-focused rumination) and triggers the neurochemistry of generosity (dopamine, serotonin, oxytocin). The reset need not cost money: + +- Hold the door for ten consecutive people. +- Send a compliment to a colleague who is not expecting one. +- Call a grandparent. +- Retweet someone trying to promote something who has no audience. + +The leadership application: before any high-stakes meeting where your mood is compromised, perform one act of kindness. The mood shift is real, transfers through mirror neurons (see `teaching-and-leading`), and costs less than a bad meeting. + +### Practice 3: Praise Lavishly, Criticise Privately + +A CEO publicly called his top salesperson lazy. The word was barely out of his mouth before he realised the error. Despite private apologies and a history of two years of generous praise, the salesperson's performance spiralled. He eventually left the company. + +The asymmetry between praise and criticism is stark: + +| Dimension | Praise | Criticism | +|-----------|--------|-----------| +| Best delivery context | Public | Private -- always | +| Effect on recipient | Pride, motivation, loyalty | Embarrassment, fear, resentment | +| Effect on bystanders | Aspiration ("I want that recognition") | Fear ("I could be next") | +| Duration of impact | Moderate; needs regular renewal | Long; a single incident can override years of praise | +| ROI | Infinite -- praise is free | Negative if delivered publicly | + +**The praise-sandwich protocol for necessary criticism:** + +1. Open with a specific, genuine positive observation. +2. Deliver the constructive feedback. +3. Close by affirming the person's value and expressing confidence in them. +4. Always in private. Never in front of peers. Never in Slack channels. + +A teacher in a classroom of at-risk students stopped reprimanding disruptive children and instead publicly praised the one student following directions: "I like the way Sammy is sitting at his desk ready to learn." The other students corrected their behaviour without being told. Years later, Sammy found his former teacher on Facebook to say that praise had inspired him to finish high school and start college. + +### Practice 4: Make It a Honey Day (Surprise and Delight) + +A director of talent at a company named to Crain's best-places-to-work list three consecutive years decided to create a holiday -- not for a top performer, not for a manager, but for a solid, consistent employee named Honey. Ribbons, balloons, cake, and a company-wide announcement: "Today is Honey Day." + +The psychology is borrowed from casinos. Slot machines produce variable rewards -- unpredictable payoffs at random intervals. The sounds of winning that greet every visitor to a casino floor are not accidental; they signal that *someone* is winning right now, and *you* could be next. Surprise-and-delight programs for employees use the same principle: + +- Recognise people at random, not just top performers. +- Keep the timing unpredictable. Scheduled recognition becomes expected; unexpected recognition becomes memorable. +- Scale varies: a named holiday is spectacular; an unexpected afternoon off or a handwritten note is equally effective. + +The retention effect: Honey is still at the company over a year later. The question "Would you leave a company that created a holiday in your honour?" answers itself. + +### Practice 5: Handwritten Thank-You Cards + +The protocol, refined over years of practice: + +1. **Week 1:** One card per week, on a designated day. +2. **Weeks 2-3:** One card per day. +3. **Week 4 onward:** Three cards per day, written during transition time -- commute, between meetings, first thing in the morning. + +Recipients include employees, customers, investors, partners, advisors, friends, and family. The cards need not be eloquent. Legibility is optional (the multibillion-dollar CEO's handwriting was barely readable). What matters is specificity: "Thank you for [specific thing you did]. It made [specific impact]." + +The dual return on investment: recipients are measurably more loyal (38% repeat donation rate for thanked donors vs. unthanked), and the writer experiences an immediate mood elevation from the act of expressing gratitude. Three cards per morning is a daily pre-meeting mood enhancer that costs less than a cup of coffee. + +### Practice 6: One Introduction Per Day + +Adam Rifkin has made over ten thousand introductions on LinkedIn since 2003 -- three per day, every day. Those introductions have produced two marriages, hundreds of jobs, dozens of funded companies, and at least twelve business partnerships. Rifkin is a shy introvert. + +An introduction accomplishes two things simultaneously: it endorses both parties and provides a reason to connect. The mechanism is Adam Grant's "five-minute favour" -- a small investment of time that produces outsized goodwill. + +**The daily introduction system:** + +1. Mark 50 people as "close friends" on social media and enable notifications for their updates. +2. When an update triggers a connection -- "Dave is working on a people-skills project; Adam is a master of people skills" -- make the introduction. +3. Use a concise template: names, why they remind you of each other, and a suggestion to connect. +4. Start with one per day. Build to three. + +The compounding effect: introductions keep you top of mind with both parties. Over a year, 365 introductions create 730 moments of goodwill attributed to you. Over a decade, the network effects are exponential. + +### Practice 7: The Personalised Gift (Buy Him a Bonsai) + +A startup founder sent a $35 bonsai tree to a venture capitalist who had rejected his investment pitch. The accompanying note: "Here's to your growth, our growth, and the growth of this bonsai." The VC responded with an introduction to another investor who eventually wrote a check. + +The personalised gift operates in the gap between a thank-you card (free, personal) and a lavish present (expensive, potentially awkward). The criteria: + +- **Thoughtful:** connected to the recipient's interests or the context of the relationship. +- **Affordable:** $20-50 is the sweet spot. Expensive gifts create obligation; inexpensive-but-clever gifts create warmth. +- **Unexpected:** the element of surprise is the multiplier. +- **Durable:** a gift that sits on someone's desk for months provides ongoing mental presence. + +Beyond bonsais, effective options include: books relevant to a conversation you had, personalised trophies for tongue-in-cheek achievements, mini herb gardens, and even a toy moat (sent to an investor who said the company needed a better moat). The operating principle is that in a world where most follow-ups are emails, a physical object occupies mental real estate that no digital message can claim. + +### Practice 8: Never Let One Unkind Word Destroy Years of Praise + +This is the defensive complement to Practice 3. The founder who publicly called his star employee lazy did not just damage one moment -- he invalidated two years of accumulated praise. The employee heard only the criticism, because criticism is neurologically stickier than praise. A single public rebuke can undo months of carefully built trust. + +The preventive discipline: before saying anything critical, pause and ask three questions. + +1. Am I about to say this in front of other people? (If yes, stop.) +2. Have I set up a private, structured conversation for this feedback? (If no, schedule one.) +3. Will this criticism help the person improve, or am I venting frustration? (If venting, walk away and return when the purpose is constructive.) + +### Practice 9: Stay Top of Mind at Scale + +A founder with more LinkedIn page views than Bill Gates, Jack Welch, and Mark Cuban combined achieved it not through celebrity or wealth but through consistent content curation. The formula is EEI: Entertain, Educate, Inspire. + +The practical system: + +1. Spend thirty minutes per week finding EEI content: articles, videos, infographics, quotes. +2. Schedule content across LinkedIn and Twitter using free scheduling tools. +3. For the five most important people in your network, send relevant content privately via text or direct message -- not as a public post, but as a personal recommendation. +4. Share others' accomplishments at a 3:1 ratio to your own. + +Content curation keeps you at the top of news feeds and therefore at the top of minds. The recipient who sees your name daily attributing interesting content to you is a recipient who thinks of you first when an opportunity arises. A Shark Tank star shared her cell phone number after receiving a single private message offering to help promote her book. A year later, she was there when the favour was needed. They have still never met in person. + +--- + +## Prompts + +**Prompt 1 -- Thank-You Card System Design:** +> I want to start a daily handwritten thank-you card practice. I have [number] employees, [number] key clients, [number] investors, and [number] advisors. Design a 30-day ramp-up plan: who should receive cards in what order, what should each card say (give me three templates varying in specificity), and how should I schedule the writing into my existing routine? + +**Prompt 2 -- Audience-Centred Presentation Rewrite:** +> Here is the outline for my upcoming [presentation type] to [audience]. Rewrite it so that every section is framed around the audience's self-interest rather than my company's achievements. Show me the before-and-after for each section. + +**Prompt 3 -- Surprise-and-Delight Programme:** +> My company has [number] employees. Design a 90-day surprise-and-delight programme using variable reward principles: what types of recognition, at what frequency, for which selection criteria (random vs. merit-based vs. value-aligned), and with what budget per event? Include at least one zero-cost option. + +**Prompt 4 -- Introduction Habit Builder:** +> Here are 20 people in my network I have not spoken to in the last 6 months: [list names and one-line descriptions]. For each, suggest one person from the rest of the list (or from my broader network description) who would benefit from an introduction, and draft the introduction email. + +--- + +## Use Cases + +**Pre-Seed Founder Building an Advisory Network** + +A founder with no track record needs three advisors to lend credibility to an investor pitch. She begins by writing one handwritten thank-you card per day to people who have given her advice informally -- a former professor, a startup meetup organiser, a LinkedIn connection who answered a cold message. After two weeks, she starts making one introduction per day among her nascent network. Within sixty days, three of the people she connected offer to serve as formal advisors. She never asked directly. The gratitude and generosity created a reciprocity loop that produced the outcome naturally. + +**Growth-Stage CEO Retaining a Key Engineer** + +A lead engineer who built the core product has received a competing offer. The CEO's instinct is to match the salary. Instead, the CEO writes a handwritten card describing three specific contributions the engineer made that shaped the company's trajectory. She creates "Architecture Day" -- a surprise company-wide celebration of the engineering team's work, with the lead engineer recognised in front of the entire company. She sends a personalised gift: a first edition of the engineer's favourite programming textbook, found on a used bookstore site for $40. The engineer stays. The competing offer was 15% higher. The card, the celebration, and the gift outweighed the delta. + +**Scale-Stage Founder Maintaining Investor Relationships** + +A founder with twelve investors on the cap table and over a thousand LinkedIn connections cannot maintain personal relationships at that volume through meetings alone. She implements a three-tier system: (1) handwritten quarterly cards to all twelve investors with specific portfolio updates, (2) daily content curation on LinkedIn keeping her visible to the broader network, and (3) one personalised introduction per day connecting people in her network who should know each other. Two investors from her seed round participate in her Series B, citing "consistent communication and genuine relationship maintenance" as factors. Three introductions she made result in new business for her investors' other portfolio companies, deepening the relationships further. + +--- + +## Anti-Patterns + +**Transactional Gratitude.** Writing a thank-you card immediately before asking for something converts gratitude into manipulation. The practice must be sustained and unconditional. The returns compound over months, not minutes. + +**Praise Without Specificity.** "Great job!" is noise. "Your analysis of the churn data changed how we prioritise the roadmap this quarter" is signal. Generic praise feels performative; specific praise feels genuine because it requires the praiser to have actually noticed something. + +**Surprise-and-Delight as Compensation Substitute.** Balloons and cake cannot replace competitive salaries, clear career paths, and functional management. Variable rewards supplement good working conditions; they do not substitute for them. A company that celebrates Honey Day but pays below market is not inspiring -- it is deflecting. + +**Content Curation Without Curation.** Sharing ten articles per day with no filtering, no personal commentary, and no relevance to your audience is not staying top of mind. It is cluttering feeds. The EEI filter must be applied rigorously: does this entertain, educate, or inspire the specific people who follow me? + +**Introductions Without Due Diligence.** Connecting two people who have no reason to speak wastes both parties' time and diminishes your credibility as a connector. Every introduction should pass the test: can I articulate, in one sentence, why this connection is mutually beneficial? + +--- + +## By Stage + +| Stage | Retention Priority | Key Practices | +|-------|-------------------|---------------| +| Idea | Retaining cofounders and first believers | Handwritten cards; personalised gestures; making every interaction about their vision | +| Validation | Retaining pilot customers and early employees | Surprise-and-delight (small scale); thank-you cards to early adopters; daily introductions to build network | +| Early Traction | Retaining the team that got you here | Praise systems; Honey Day-style recognition; perspective resets during hard stretches | +| Growth | Retaining key talent against competing offers | Full thank-you card programme; personalised gifts; audience-centred all-hands presentations | +| Scale | Maintaining relationships across hundreds of stakeholders | Content curation at scale; introduction-per-day system; tiered relationship maintenance | + +At the idea stage, the founder's network is small enough that every relationship can be maintained personally. A single handwritten card to a cofounder after a hard week costs nothing and can prevent the slow drift of disengagement that kills early partnerships. At scale, the challenge inverts: the network is too large for personal maintenance, and systems -- content curation, scheduled introductions, tiered communication -- become necessary to sustain the warmth that personal attention provided at smaller scale. + +--- + +## Output Template + +```markdown +# Inspiration and Retention Plan + +**Company Stage:** [Idea / Validation / Early Traction / Growth / Scale] +**Team Size:** [Number] +**Key Relationships to Maintain:** [List names and roles] + +## Thank-You Card Programme +- Current practice: [None / Occasional / Systematic] +- 30-day target: [cards per week] +- Priority recipients this month: + 1. [Name] -- [reason for gratitude] + 2. [Name] -- [reason for gratitude] + 3. [Name] -- [reason for gratitude] + +## Surprise-and-Delight Calendar +| Month | Recipient(s) | Type of Recognition | Budget | +|-------|-------------|--------------------| -------| +| [Month] | [Random / Specific] | [Description] | [Amount] | + +## Introduction System +- Network inventory completed: [yes/no] +- Daily introduction target: [1 / 2 / 3] +- This week's introductions: + - [Person A] <-> [Person B]: [reason] + +## Personalised Gift Pipeline +| Recipient | Context | Gift Idea | Budget | Send Date | +|-----------|---------|-----------|--------|-----------| +| [Name] | [Why now] | [Gift] | [Amount] | [Date] | + +## Content Curation +- Platform(s): [LinkedIn / Twitter / Both] +- Weekly curation time blocked: [Day and time] +- Top 5 content sources: [list] +- Private share list: [5 names for personalised content delivery] + +## Praise Audit +- Last public praise given: [date, recipient, context] +- Last private criticism given: [date -- was it structured? was it private?] +- Praise-to-criticism ratio (last 30 days): [estimate] +``` + +--- + +## Related Skills + +- **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- Covers the structural dimensions of retention (career paths, compensation, culture); this skill provides the interpersonal practices that complement those structures. +- **[Carnegie's Win Friends and Influence People](../frameworks/carnegie-win-friends.md)** -- Carnegie's principles of appreciation and making others feel important are the theoretical roots of the thank-you card and praise practices detailed here. +- **[Teaching and Leading](teaching-and-leading.md)** -- Mirror neurons, gratitude as a pre-meeting practice, and distributed leadership create the conditions under which the retention practices here are most effective. +- **[Influencing and Persuading](influencing-and-persuading.md)** -- The storytelling and listening techniques inform the audience-centred presentation approach. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Handwritten cards, personalised gifts, and consistent content curation increase intimacy and reduce self-orientation in the trust equation. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- Structured mentoring relationships operationalise the development dimension of retention that this skill addresses through interpersonal investment. diff --git a/plugins/foreman/content/skills/people/meeting-the-right-people.md b/plugins/foreman/content/skills/people/meeting-the-right-people.md new file mode 100644 index 0000000..cefb6bd --- /dev/null +++ b/plugins/foreman/content/skills/people/meeting-the-right-people.md @@ -0,0 +1,205 @@ +--- +name: "meeting-the-right-people" +description: "Applies modern networking and relationship-curation methods for entrepreneurs who need to build strategic networks efficiently. Covers standing out through signature differentiation, the warm-introduction chain for reaching anyone, building a personal advisory board, the discipline of hiring slow and firing fast in all relationships, and the art of the productive blowoff. Use when preparing for conferences and networking events, seeking introductions to investors or partners, assembling advisory boards, evaluating whether to continue or exit relationships, or protecting time from low-value interactions." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - networking + - advisory-board + - introductions + - time-management + - personal-brand + - relationship-curation +related_skills: + - understanding-people + - reading-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +# Meeting the Right People + +The secret to networking is not talking to everyone -- it is doing what nobody else does. + +A founder wore bright orange sneakers to a startup event where three hundred people competed for the attention of Dave McClure, founding partner of 500 Startups. McClure ignored all of them. Then he spotted the shoes. "I have got to talk to the man wearing those fucking shoes!" The conversation lasted fifteen minutes. 500 Startups became a key investor in the founder's company. The shoes did not close the deal. But they opened the door -- and in a room of identical pitches, the door is the bottleneck. + +This principle generalises beyond footwear. In any saturated environment -- a conference, an inbox, a LinkedIn feed -- the decisive advantage belongs to the person who has solved the attention problem before solving the persuasion problem. Most networking advice focuses on what to say. The prior question is how to get anyone to listen in the first place. + +--- + +## The Framework + +Meeting the right people involves five distinct disciplines, each addressing a different failure mode. + +### Discipline 1: Stand Out (The Orange Shoes Principle) + +In any gathering of professionals, the default is conformity. Dark suits, safe accessories, predictable conversation openers. The person who introduces a single, authentic differentiator -- visual, behavioural, or conversational -- captures disproportionate attention. + +The criteria for an effective differentiator: + +- **Attention-grabbing.** It must be visible or noticeable without requiring explanation. +- **Authentic.** It must feel natural to you, not costumed. A forced quirk is worse than no quirk. +- **Consistent.** It must appear repeatedly so that it becomes associated with your identity. A one-time stunt is novelty; a persistent signature is brand. + +Orange shoes work because they satisfy all three criteria. The differentiator need not be visual -- it could be an unusual opening question (see the three-question method), a distinctive handshake ritual, or a habit of sending handwritten follow-up notes in an era of templated emails. What matters is that it is yours, it is noticeable, and it recurs. + +### Discipline 2: Reach Anyone (The Warm Introduction Chain) + +Cold outreach has a response rate that approaches zero for high-value targets. The warm introduction chain -- mediated through mutual connections, typically via LinkedIn -- transforms unreachable contacts into coffee meetings. + +**The method:** + +1. Identify the person you want to meet. +2. Search for mutual connections -- first-degree preferred, second-degree acceptable. +3. Select the mutual connection most likely to respond positively. Two filters: (a) someone for whom you have done a favour in the past (reciprocity capital), and (b) someone with genuine influence over the target. +4. Write a concise introduction request that explains *why* the meeting would be mutually beneficial, not just why *you* want it. +5. Once connected, propose a specific, time-bounded meeting. "Fifteen minutes for coffee" removes friction. "Let's find time to chat sometime" creates it. + +The chain works because it transfers trust. The target does not know you, but she knows and trusts the connector. That transferred trust lowers the barrier from "ignore" to "consider." The deeper your network of first-degree connections, the shorter the chain to any target. This is the compound interest of relationship-building -- every genuine connection increases the reachability of everyone else. + +### Discipline 3: Build a Personal Advisory Board + +Mentorship is not reserved for people who work inside organisations large enough to have formal programmes. Any entrepreneur can construct a personal advisory board -- an informal group of five to twelve people who meet quarterly to advise on specific challenges. + +**Construction principles:** + +| Element | Guidance | +|---------|----------| +| Purpose | Define the board's focus before recruiting members. "Help me launch a software company" is actionable. "Help me with stuff" is not. | +| Composition | Diverse disciplines and backgrounds. At least half should be people you have met; at least two should be people you have not yet met but can reach through connections. | +| Structure | Scheduled quarterly meetings with a written agenda. Begin with a twenty-minute icebreaker or training exercise. Follow with a business update and one to two specific challenges for discussion. | +| Reciprocity | Provide value to advisers at every meeting -- leadership training, networking opportunities, a small equity stake or stipend. The most powerful compensation, however, is the multiplier effect: smart people in the same room generate connections and insights none of them would have produced alone. | +| Seriousness | The difference between an advisory board and a casual dinner is structure. Agenda, schedule, quiet room, follow-through. The more seriously the founder takes the format, the more seriously advisers will take their role. | + +The multiplier effect is the advisory board's core advantage over one-on-one mentorship. When eight experienced people hear the same challenge simultaneously, they produce cross-pollinated solutions -- combinations of expertise that no single adviser would generate alone. + +### Discipline 4: Hire Slow, Fire Fast (In All Relationships) + +The principle is well-known in management. Its application to *all* professional relationships is less obvious but equally important. + +**Hire slow:** Do not grant full trust and access to someone you have just met, no matter how impressive they appear. Early enthusiasm is not evidence of long-term fit. Cofounders, business partners, key hires, and even investor relationships should be entered gradually, with deliberate evaluation at each stage. + +**Fire fast:** The moment gut instinct signals that a relationship is not working -- the business partner whose values diverge, the investor whose advice consistently harms, the hire whose culture impact is toxic -- act. Cognitive dissonance is the enemy: the desire to believe you made a good decision causes you to rationalise the bad one, sometimes for years. + +The cognitive dissonance trap is particularly dangerous for founders, who are temperamentally biased toward optimism. The script "I'll give them one more chance" or "Maybe they'll change" is almost always the sound of a founder overriding data with hope. Every minute spent with the wrong person is a minute unavailable for the right one. + +### Discipline 5: The Productive Blowoff + +Time is finite. Not every person who requests a meeting deserves thirty minutes of it. The productive blowoff -- ending an interaction quickly while leaving the other person feeling valued -- is a skill that protects the founder's most scarce resource. + +**The three-step blowoff:** + +1. **Physical signal.** A handshake or equivalent gesture to mark the beginning *and* the end of the conversation. +2. **Direct, honest communication.** State the situation frankly. "You don't fit our investment criteria, but you might be a partner" conveys respect through candour. +3. **Provide value before exiting.** Make an introduction, offer a specific suggestion, send a useful resource. The person walks away with something concrete rather than a vague rejection. + +The founder who masters this discipline converts thirty-minute meetings into eight-minute meetings without creating resentment -- and reclaims the other twenty-two minutes for higher-value activity. Sheryl Sandberg calls it "ruthless prioritisation." The ruthlessness applies to time allocation, not to people. + +--- + +## Prompts + +**Prompt 1 -- Networking Differentiation Strategy:** +> I am attending [describe event: type, audience, size, goal]. Help me design a personal differentiation strategy using the Orange Shoes principle. Based on my personality and context [describe], suggest three possible signature differentiators that are attention-grabbing, authentic to me, and repeatable. For each, describe how it would work at this specific event and what opening conversations it would naturally create. + +**Prompt 2 -- Warm Introduction Chain:** +> I want to meet [describe target person, their role, and why]. I have the following potential mutual connections: [list 3-5 people]. For each, evaluate (a) the likely strength of their relationship with my target, (b) the reciprocity capital I have with them, and (c) the quality of introduction they would provide. Recommend the optimal connector and draft the introduction request email. + +**Prompt 3 -- Advisory Board Design:** +> I am a [stage] founder building [describe company]. Design a personal advisory board for me. Recommend the ideal size, meeting frequency, agenda structure, and compensation model. Define the five to seven competency areas I should recruit for, and for each, suggest the profile of the ideal adviser (not a specific person, but a role/background description). Include a template for the initial recruitment ask. + +**Prompt 4 -- Relationship Audit:** +> Audit my current professional relationships against the "hire slow, fire fast" principle. Here are my key relationships: [list 5-8 with brief descriptions of current state]. For each, identify whether I am (a) investing appropriately, (b) over-investing due to cognitive dissonance, or (c) under-investing in a high-potential connection. Recommend specific actions for each, including any "fire fast" decisions I may be avoiding. + +--- + +## Use Cases + +**Idea-Stage Founder at a Demo Day** + +A first-time founder attends a demo day with forty startups and two hundred investors. She has no existing investor relationships and no brand recognition. Applying the Orange Shoes principle, she wears a distinctive hand-painted jacket that references her product's design aesthetic -- genuine because she is a trained artist, attention-grabbing because no one else in the room has one. Three investors approach her before she approaches anyone. She uses the warm-introduction chain for the remaining five target investors, reaching three through LinkedIn mutual connections within the following week. Within a month, she has a personal advisory board of four people assembled from connections made at the event: a veteran founder, a domain expert, a marketing executive, and one of the investors who did not invest but offered to advise. The board meets quarterly in a structured format, and within two meetings surfaces a pivot in go-to-market strategy that the founder would not have identified alone. + +**Growth-Stage CEO Protecting Executive Time** + +A CEO of a sixty-person company receives fifteen meeting requests per week from vendors, potential partners, and aspiring hires. Her calendar is the company's bottleneck. She implements the productive blowoff systematically: every meeting request receives a response within forty-eight hours, but most are converted from thirty-minute meetings to ten-minute calls with a clear three-step structure (signal, directness, value). She creates a "meeting triage" protocol for her executive assistant: requests that align with quarterly priorities get full meetings; all others get the abbreviated format. The CEO recovers seven hours per week -- nearly a full working day -- while maintaining a reputation for responsiveness and generosity. + +--- + +## Anti-Patterns + +1. **Collecting Connections Without Purpose.** Treating LinkedIn connections or business cards as a score. Ten thousand connections with no relationship depth is a database, not a network. The warm-introduction chain requires trust, and trust requires genuine relationships -- not a follower count. + +2. **Networking as Performance.** Attending every event, working every room, exchanging cards with every person. This produces exhaustion and shallow relationships. Strategic networking means attending fewer events with higher target density and investing more time per interaction. + +3. **Advisory Board as Vanity Project.** Recruiting impressive names who never attend meetings or provide substantive input. An advisory board with a former Fortune 500 CEO who shows up once a year is less valuable than one with five engaged operators who attend every quarter and follow up between meetings. + +4. **Firing Too Slowly Out of Guilt.** The cognitive dissonance trap is especially potent in founder-investor and founder-cofounder relationships, where the social cost of exit feels prohibitive. The sunk-cost fallacy -- "we've been through so much together" -- is not a strategy. Every week spent in a toxic partnership has a measurable opportunity cost. + +5. **Blowing Off the Wrong People.** The productive blowoff is a tool for time management, not for status signalling. The junior employee who requests a meeting today may be the CEO who writes a check tomorrow. Evaluate meeting requests on potential value, not current title. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Network construction | At the idea stage, the founder's network *is* the venture's most valuable asset. Every coffee meeting, warm introduction, and event attendance is an investment in infrastructure that will compound over years. | +| Validation | Customer and partner access | The warm-introduction chain becomes a customer-discovery tool. Reaching ten potential customers through trusted mutual connections yields richer feedback than reaching a hundred through cold outreach. | +| Early Traction | Advisory board formation | With a product in market and early signals of fit, the founder has enough substance to recruit meaningful advisers. This is the optimal window for advisory-board construction -- early enough to benefit from strategic guidance, late enough to articulate a clear purpose. | +| Growth | Relationship pruning | Growth demands "fire fast" discipline. Relationships that served the company at seed stage -- the friendly-but-unstrategic investor, the early hire who cannot grow with the role -- must be evaluated honestly against current needs. | +| Scale | Institutional networking | At scale, the founder's personal network cannot serve the entire organisation. Networking must become a distributed competency -- every executive building their own warm-introduction chains, their own advisory relationships, their own productive-blowoff discipline. | + +--- + +## Output Template + +```markdown +# Networking Strategy: [Your Name / Company / Event] + +## Differentiation +- **Signature element:** [Description] +- **Why it is authentic:** [Connection to personality/brand] +- **Expected conversations it will generate:** [Types of openers] + +## Target Contacts +| Target | Why | Best Connector | Introduction Request Status | +|--------|-----|----------------|---------------------------| +| [Name] | [Reason] | [Mutual connection] | [Drafted / Sent / Connected] | + +## Advisory Board Design +- **Purpose:** [Specific goals] +- **Target size:** [Number] +- **Competency areas needed:** [List] +- **Meeting cadence:** [Frequency and format] +- **Recruited / Open seats:** [Status] + +## Relationship Audit +| Relationship | Current Investment | Correct Action | Timeline | +|-------------|-------------------|----------------|----------| +| [Name/Role] | Over / Under / Right | [Specific action] | [When] | + +## Time Protection +- **Meeting triage criteria:** [What qualifies for full meeting vs. abbreviated format] +- **Hours recovered per week target:** [Number] +``` + +--- + +## Related Skills + +- **[Understanding People](understanding-people.md)** -- Meeting people is the access problem; understanding them is the comprehension problem; the Enneagram and rapid-understanding techniques make meetings productive once they occur. +- **[Reading People](reading-people.md)** -- The warm-introduction chain gets you into the room; reading nonverbal signals tells you what the room is actually thinking. +- **[Connecting with People](connecting-with-people.md)** -- Meeting the right people is necessary but insufficient; connecting through validation and the Platinum Rule transforms initial meetings into lasting relationships. +- **[Carnegie's Win Friends](../frameworks/carnegie-win-friends.md)** -- Carnegie's principle of making others feel important is the interpersonal foundation that makes warm introductions work. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- The warm-introduction chain is Cialdini's Reciprocity principle in action; the advisory board leverages Authority and Unity. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- A compelling personal story is the most effective tool for first meetings; it creates memorability and connection faster than any networking script. diff --git a/plugins/foreman/content/skills/people/reading-people.md b/plugins/foreman/content/skills/people/reading-people.md new file mode 100644 index 0000000..bf6d6fd --- /dev/null +++ b/plugins/foreman/content/skills/people/reading-people.md @@ -0,0 +1,216 @@ +--- +name: "reading-people" +description: "Applies practical techniques for decoding what people actually mean beyond their words, through nonverbal communication, active listening, rapport micro-signals, bluff detection, and mirroring. Covers listening with eyes rather than ears, the 55/38/7 communication model, accepting rapport signals, reading dishonesty tells, and the mirroring technique that builds trust through verbal reflection. Use when preparing for high-stakes negotiations, conducting investor meetings, managing difficult client conversations, interviewing candidates, or diagnosing misalignment between what stakeholders say and what they mean." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - nonverbal-communication + - body-language + - active-listening + - mirroring + - negotiation + - rapport + - bluff-detection +related_skills: + - understanding-people + - meeting-the-right-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +# Reading People + +The claim that words account for only 7% of communication is exaggerated -- but the belief that they account for 100% is far more dangerous. + +Albert Mehrabian's 1967 research produced the famous 55/38/7 formula: 55% body language, 38% tone, 7% words. The study's conditions were narrow (single-word emotional statements), and the numbers should not be taken as universal law. What *should* be taken as universal law is the underlying insight: a substantial majority of what people communicate has nothing to do with the sentences they construct. Founders who listen only to words are reading a transcript when they should be watching a film. The investor who says "interesting" while leaning back with crossed arms is not interested. The hire who says "I'm excited" while avoiding eye contact is not excited. The customer who says "we'll think about it" while checking the time has already decided. + +Reading people is not mind-reading. It is pattern recognition -- the trained habit of observing behaviour that most professionals ignore because they were never taught to look. + +--- + +## The Framework + +Reading people operates through five interlocking skills, each progressively more difficult to master. + +### Skill 1: Stop Waiting to Talk + +The precondition for reading people is the ability to stop composing your next sentence while someone else is speaking. Most people do not listen; they queue their response. The internal experience feels like listening -- you are facing the speaker, you are nodding -- but the cognitive bandwidth allocated to comprehension is minimal because most of it is consumed by rehearsal. + +Gerald Bell of the Bell Leadership Institute prescribes the **Achiever Listening Position**: sit up straight, lean slightly forward, arms at your sides, eyes fixed on the speaker with the intensity of a child watching television. The physical posture forces cognitive engagement. When the mind wanders -- and it will -- the posture serves as an anchor to pull attention back to the speaker. + +The critical reframe: you are not listening with intent to respond. You are listening with intent to *understand*. The response will take care of itself once comprehension is genuine. + +### Skill 2: Listen with Your Eyes + +Once the mind is fully present, the next skill is to distribute attention beyond words. Seven channels of nonverbal communication carry the information that words omit. + +| Channel | What to Observe | Entrepreneurial Signal | +|---------|----------------|----------------------| +| **Facial expressions** | Micro-expressions of surprise, contempt, disgust, or delight that flash before the social mask reasserts itself | An investor's fleeting eyebrow raise when you mention a competitor reveals unexpected concern | +| **Posture and movement** | Open vs. closed stance, comfort vs. tension, leaning in vs. pulling away | A candidate who leans back when discussing team collaboration may be signalling introversion or resistance | +| **Gestures** | Hand movements, self-touching, fidgeting, pointing | A board member who touches her face repeatedly during a financial presentation may be masking discomfort with the numbers | +| **Eye contact** | Sustained vs. averted, blinking rate, direction of gaze | A cofounder who breaks eye contact when discussing equity split is flagging unresolved tension | +| **Touch** | Handshake firmness, duration, and placement; shoulder touch; arm grip | A weak handshake from a prospective partner may indicate low confidence in the deal or in themselves | +| **Proxemics (space)** | Physical distance, territorial behaviour, positioning relative to others | An investor who moves closer during your pitch is engaged; one who subtly increases distance is withdrawing | +| **Vocal qualities** | Pace, volume, pitch, hesitation, filler words | A customer whose speech accelerates when discussing budget is likely under pricing pressure | + +The key is to establish a **baseline** for each person before interpreting deviations. Someone who fidgets constantly is not bluffing -- they are a fidgeter. Reading people requires calibrating against their normal behaviour, not against some universal template. + +### Skill 3: Accept the Glass of Water + +Rapport is built through small, often invisible signals of acceptance and reciprocity. The glass-of-water principle captures one such micro-signal: when offered a beverage at the start of a meeting, always accept. + +The reasoning operates on two levels: + +- **Self-regulation.** Accepting the drink creates a moment of settling in, reduces physical discomfort (thirst, nerves), and provides a natural pause for observation before the substantive conversation begins. +- **Host validation.** Declining an offered drink -- however politely -- creates a micro-friction. The host's gesture of hospitality has been refused. This is a tiny event, but tiny events compound. Accepting the drink allows the host to feel competent in their role, which primes the interaction toward warmth. + +The glass-of-water principle extends beyond beverages. Every interaction contains micro-opportunities for acceptance: accepting a compliment gracefully rather than deflecting it, accepting a small favour rather than insisting on self-sufficiency, accepting an invitation to sit in a preferred chair. Each acceptance reinforces the rapport loop. Each refusal, however minor, introduces static. + +### Skill 4: Detect the Bluff + +Bluffing -- presenting a false position to extract a concession -- is common in business negotiations. Detection requires comparing the speaker's verbal content against their nonverbal baseline. + +**Bluff indicators (deviation from baseline):** + +- Face-touching or scratching that appears during the specific claim, absent during prior conversation +- Gaze aversion at the moment of the critical assertion +- Speech-pace acceleration or sudden formality ("To be perfectly honest..." is often a preamble to dishonesty) +- Physical fidgeting that intensifies during the negotiation's pressure point +- Vocal pitch increase -- stress compresses the vocal cords + +**The detection protocol:** + +1. Establish the person's baseline during low-stakes conversation (greetings, small talk, uncontested topics). +2. Note changes in nonverbal behaviour when the conversation moves to contested claims. +3. Identify whether the change correlates with a specific claim or negotiating position. +4. If indicators cluster around a particular statement, call the bluff -- not aggressively, but by declining to concede. "I understand your position. I'm not able to move on that, but I'm confident the value justifies the terms." + +Calling a bluff carries information value regardless of whether the other party was actually bluffing. If they were, you have saved money and learned something about their trustworthiness. If they were not, their genuine conviction will emerge in their response -- and you can adjust accordingly. + +### Skill 5: Mirror (The Technique That Sounds Absurd and Works Every Time) + +Mirroring -- repeating back someone's exact words, preceded by "I hear you saying" -- sounds like a kindergarten exercise. It is, in practice, one of the most powerful rapport-building techniques available. + +**Why it works:** Mirroring provides the speaker with irrefutable evidence that they have been heard. Not paraphrased, not interpreted, not redirected -- *heard*. The psychological experience of being truly heard is so rare in professional settings that when it occurs, it produces an immediate and often dramatic increase in trust and openness. + +**Execution rules:** + +1. **Repeat their exact words.** "I hear you saying you're frustrated with the timeline." Not "I understand you're upset about scheduling." Close paraphrases feel like interpretation. Exact repetition feels like comprehension. +2. **Emphasise the feeling words.** Mirroring "I'm worried we'll miss the deadline" should place vocal emphasis on *worried* and *miss*. The emotional content is what the speaker most needs reflected. +3. **Never follow with "but."** "I hear you saying you're worried about the timeline, but we're actually ahead of schedule" instantly negates the mirror. The word "but" erases everything that preceded it. If a response is necessary, pause after the mirror. Let the reflection settle. Then respond in a separate sentence. +4. **Care genuinely.** Robotic repetition is detected instantly. Mirroring requires authentic engagement with the speaker's emotional state. If you do not care, the technique will not merely fail -- it will damage trust. + +The deeper the emotional content of the original statement, the more powerful the mirror. Mirroring "I took the train to work today" has negligible impact. Mirroring "I'm scared we're going to lose our biggest client" can transform a relationship. + +--- + +## Prompts + +**Prompt 1 -- Pre-Meeting Reading Preparation:** +> I have a high-stakes meeting with [describe person, role, context]. Help me prepare a reading plan: (a) what baseline information should I gather in the first two minutes of small talk, (b) what specific nonverbal channels should I prioritise given the meeting format [in-person / video / phone], (c) what are the likely pressure points in the conversation where nonverbal deviations will be most informative, and (d) what mirroring opportunities am I likely to encounter? + +**Prompt 2 -- Bluff Detection Scenario:** +> A [counterparty description] has made the following claim during a negotiation: [describe the claim]. I observed the following nonverbal signals: [describe what you noticed]. Analyse whether these signals are consistent with bluffing, genuine conviction, or simple discomfort. Recommend a response strategy that tests the claim without damaging the relationship. + +**Prompt 3 -- Listening Audit:** +> Record my performance in a recent important conversation: [describe the conversation]. At what points did I stop listening to understand and start listening to respond? What nonverbal signals from the other person did I miss? Reconstruct the conversation with annotations showing where active listening and mirroring could have changed the outcome. + +**Prompt 4 -- Mirroring Script Design:** +> I anticipate a difficult conversation with [describe person and situation]. The other person is likely to express [describe expected emotional content]. Draft three mirroring responses I can use, ensuring each uses the person's likely exact language, emphasises the emotional words, and avoids the "but" trap. Include follow-up questions I can ask after each mirror to deepen understanding. + +--- + +## Use Cases + +**Validation-Stage Founder in Customer Discovery** + +A SaaS founder conducts ten customer-discovery interviews in a week. In the first five, she focuses exclusively on the words customers use, recording answers to her structured questions. In the second five, she applies the full reading framework: she establishes baseline behaviour during opening small talk, watches for posture changes when discussing pain points, notes where speech pace accelerates (indicating genuine frustration versus polite agreement), and mirrors customers' emotional language back to them. The second set of interviews yields three insights the first set missed entirely: one customer's claimed "minor annoyance" was accompanied by physical tension that indicated a significant pain point; another customer's enthusiastic verbal response was contradicted by a micro-expression of scepticism that, when explored through mirroring, revealed a pricing concern she had not planned to raise. The founder adjusts both the product roadmap and the pricing model based on information that words alone would have concealed. + +**Early-Traction CEO in Investor Negotiation** + +A founder receives a term sheet from a venture capital firm. During the negotiation call, the lead partner states that the proposed valuation is "firm" and that the fund "cannot go higher." The founder notes that the partner scratches his face during this statement and increases his speech pace -- deviations from his relaxed baseline during earlier discussion of the product. Rather than conceding, the founder mirrors: "I hear you saying the valuation is firm and the fund cannot go higher." The partner, feeling heard, elaborates -- revealing that the constraint is not the fund's valuation model but a specific partner's concern about the sector. The founder addresses the sector concern directly, and the valuation increases by 15% in the next conversation. + +**Growth-Stage CTO Managing a Departing Engineer** + +A senior engineer requests a "quick chat" about her career. The CTO reads the signals: the engineer has already accepted the invitation to sit, but her posture is tense, she declines the offered coffee (a rapport-refusal micro-signal), and she avoids eye contact during the opening small talk. Before the engineer speaks her first substantive sentence, the CTO has a hypothesis: this is a resignation conversation. He adjusts his listening posture to full Achiever mode, asks one open question, and mirrors every statement the engineer makes for the next ten minutes without offering a single counterargument. The engineer, feeling genuinely heard for what may be the first time in months, reveals that the issue is not compensation but a sense of isolation on a project. The CTO addresses the structural problem. The engineer stays. + +--- + +## Anti-Patterns + +1. **Armchair Body-Language Analysis.** Reading a single gesture in isolation and drawing a sweeping conclusion. Arms crossed can mean hostility, cold temperature, or habitual comfort. Reading people requires *clusters* of signals and *deviations* from baseline, not amateur semiotics applied to one data point. + +2. **Weaponising Mirroring.** Using mirroring as a manipulation technique to extract concessions rather than as a genuine listening tool. People can distinguish between being heard and being handled. Mirroring deployed without authentic care produces an uncanny-valley effect that destroys trust faster than not mirroring at all. + +3. **Over-Reading Video Calls.** Applying the full nonverbal framework to Zoom calls, where camera angle, lighting, and screen-induced gaze distortion make body-language reading unreliable. On video, prioritise vocal qualities and verbal content. Reserve full nonverbal reading for in-person interactions. + +4. **Calling Bluffs Aggressively.** Detecting a bluff and then announcing "I know you're bluffing" is a negotiation-ending move, not a negotiation tactic. The correct response is to decline the bluffer's demand while preserving the relationship. The information value of the detection is strategic; the confrontation is not. + +5. **Mirroring Without Stopping.** Applying the technique to every sentence in a conversation, producing a parrot effect that is disorienting rather than validating. Mirroring is a precision tool. Deploy it at moments of emotional significance, not as a conversational default. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder alignment | At the idea stage, the most critical reading is between cofounders. Misaligned nonverbal signals during early discussions about equity, roles, and vision are the earliest warning signs of partnerships that will fracture under pressure. | +| Validation | Customer truth-detection | Customers in discovery interviews are polite. Politeness masks indifference. Reading nonverbal signals distinguishes genuine pain points from courteous agreement -- the difference between a real market and a phantom one. | +| Early Traction | Hiring signal reading | Candidates optimise their verbal performance. The founder who reads posture, eye contact, and vocal authenticity during interviews makes better hiring decisions than the one who evaluates only what candidates say. | +| Growth | Negotiation and board dynamics | Growth-stage negotiations -- fundraising, partnerships, M&A exploration -- are environments where bluffing is expected and stakes are high. Baseline-deviation detection becomes a measurable financial skill. | +| Scale | Organisational listening systems | At scale, the CEO cannot personally read every stakeholder. The reading skills must be taught to managers and embedded in feedback systems -- 360 reviews that capture nonverbal observations, not just verbal ratings. | + +--- + +## Output Template + +```markdown +# People-Reading Preparation: [Meeting / Negotiation / Interview] + +## Context +- **Person:** [Name and role] +- **Stakes:** [What is at stake in this interaction] +- **Format:** [In-person / Video / Phone] + +## Baseline Plan +- **Low-stakes topics for calibration:** [2-3 conversation openers] +- **Baseline behaviours to note:** [Posture, gesture rate, eye contact pattern, speech pace] + +## Pressure Points +| Topic | Expected Verbal Position | Nonverbal Channels to Watch | +|-------|------------------------|---------------------------| +| [Topic 1] | [What they will likely say] | [What to observe] | +| [Topic 2] | [What they will likely say] | [What to observe] | + +## Mirroring Plan +- **Likely emotional statements:** [Anticipated expressions] +- **Prepared mirrors:** [Exact-language reflections] +- **Follow-up questions after mirror:** [Deepening questions] + +## Post-Meeting Debrief +- **Baseline observations:** [What was normal for this person] +- **Deviations noted:** [Where behaviour shifted] +- **Revised assessment:** [What they actually communicated vs. what they said] +``` + +--- + +## Related Skills + +- **[Understanding People](understanding-people.md)** -- Understanding provides the motivational map (Enneagram types, core drives); reading provides the real-time signal detection that reveals whether stated motivations match actual behaviour. +- **[Connecting with People](connecting-with-people.md)** -- Reading is diagnostic; connecting is therapeutic. Mirroring bridges both, reading emotional state while simultaneously building connection. +- **[Meeting the Right People](meeting-the-right-people.md)** -- Meeting gets you in the room; reading tells you what the room is actually communicating behind its words. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's social awareness domain provides the theoretical case for why nonverbal reading matters. +- **[Negotiation Mindset and Self-Management](../negotiation/negotiation-mindset-and-self.md)** -- Negotiation preparation depends on reading the counterpart's style, assumptions, and emotional state; the techniques here provide the perceptual toolkit. +- **[Leadership Style Adaptation](../leadership/leadership-style-adaptation.md)** -- The Read-Choose-Act-Review adaptation cycle depends on accurately reading what a situation and its people need before choosing a response. diff --git a/plugins/foreman/content/skills/people/resolving-people-conflict.md b/plugins/foreman/content/skills/people/resolving-people-conflict.md new file mode 100644 index 0000000..e5d0802 --- /dev/null +++ b/plugins/foreman/content/skills/people/resolving-people-conflict.md @@ -0,0 +1,248 @@ +--- +name: "resolving-people-conflict" +description: "Delivers specific behavioural systems for resolving interpersonal conflict in real time -- reframing conflict as a helping stance, the 24-hour cooling rule, strategic surrender of what cannot be controlled, and the bulletproof vest protocol (a structured seven-step system for safe conflict resolution). Use when a cofounder disagreement is escalating, an employee conflict is disrupting team performance, a client relationship is strained, a personal relationship is leaking into work effectiveness, or any situation where two parties need a structured de-escalation process. Complements the theoretical Thomas-Kilmann conflict modes with tactical, script-level behavioural techniques." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - conflict-resolution + - de-escalation + - cofounder-conflict + - emotional-regulation + - bulletproof-vest + - cooling-period + - letting-go + - active-listening + - mediation +related_skills: + - thomas-kilmann-conflict + - carnegie-win-friends + - win-win-negotiation + - emotional-courage + - influencing-and-persuading +author: "Fatih Guner" +--- + +# Resolving People Conflict + +BULLETPROOF VEST. The most effective conflict resolution system in this entire collection was invented to save a marriage -- and it works just as well in boardrooms. A psychologist who had appeared on Oprah five times gave a couple a seven-step protocol: request an appointment (never "right now"), agree to wear a metaphorical bulletproof vest (absorb without defending), listen and mirror, apologise genuinely, then choose from three positive solutions proposed by the aggrieved party. The couple had been married seven years and fighting the same patterns on loop. Within three sessions they had a system that ended the loop. Several years later, they still use it. + +The Thomas-Kilmann framework (see `thomas-kilmann-conflict`) identifies five theoretical conflict modes: competing, accommodating, compromising, avoiding, and collaborating. That is the taxonomy. What follows is the field manual -- four specific behavioural techniques for what to do when you are in the room, the temperature is rising, and theory is the last thing on your mind. + +--- + +## The Framework + +### System 1: Reframe Conflict as Helping + +A high school vice principal sat between a student who had been maced and the student who had maced him. Her opening words: "Please know one thing. I'm here to help you. Whether or not you walk out of this room with suspension or other consequences, please know that above all else, I am here to help." + +That single reframe -- from adjudicator to helper -- changed the trajectory of the conversation. Both parties relaxed enough to tell their sides honestly. The resolution was a negotiated exchange: no punishment, cards returned, a warning noted. Neither party left happy in the celebratory sense, but both left feeling heard and helped. + +**The operational stance for any conflict:** + +Replace the instinctive internal question -- "How can I win?" or "How can I prove I'm right?" or "How can I punish?" -- with a single alternative: + +> "How can I help resolve this in a way that leaves all parties feeling heard?" + +This is not softness. It is strategic. When both parties perceive the mediator (or the other party) as genuinely trying to help, defensive walls lower. Information flows. Solutions emerge from the space that defensiveness previously occupied. + +**The script for entering a conflict:** + +1. State your helping intent explicitly: "I want to help us resolve this. My goal is that we both walk away feeling heard." +2. Invite both sides to share fully, without interruption. +3. Mirror each party's position back to them before proposing any solution. +4. Only after both parties confirm they feel heard, move to solution-generation. + +In entrepreneurial contexts, this stance applies to cofounder disputes, employee grievances, client complaints, and investor disagreements. The instinct to defend, justify, or counter-attack is universal. The discipline to say "I'm here to help" first is rare -- and disproportionately effective. + +### System 2: The 24-Hour Rule (Let Cooler Heads Prevail) + +A founder stormed out of his house after a family board game went wrong. His wife texted demanding immediate resolution. He returned, still in a state of rage. The resulting conversation was unproductive: he was listening but not processing; she was talking but not being heard. They went to sleep. + +The next morning, the conversation was entirely different. He was calm. She was calm. He articulated what he had felt. She articulated her boundaries. They made a commitment and moved forward. + +**The principle:** it is neurologically impossible to resolve conflict while either party is in a state of emotional flooding. Adrenaline and cortisol impair the prefrontal cortex -- the brain region responsible for empathy, perspective-taking, and creative problem-solving. Attempting resolution while flooded produces either escalation or capitulation, neither of which constitutes resolution. + +**The 24-hour rule in practice:** + +| Situation | What to say | What not to do | +|-----------|------------|----------------| +| You are flooded | "I'm in a highly volatile state and would really appreciate resolving this later." | Storm out without explanation; send angry texts; pretend you are fine | +| The other person is flooded | "I can see this is intense. Let's come back to this when we've both had time to think." | Demand immediate resolution; interpret their need for space as avoidance; escalate to force engagement | +| Both parties are flooded | "Neither of us is in a position to resolve this well right now. Let's set a specific time tomorrow." | Continue arguing; make permanent decisions based on temporary emotions | + +The critical nuance: the 24-hour rule is a delay, not an avoidance. Setting a specific time to reconvene distinguishes strategic patience from conflict dodging. "Let's talk about this later" without a time commitment becomes "Let's never talk about this," which compounds resentment. + +**Recommended minimum cooling periods by conflict intensity:** + +- Minor disagreement (process, scheduling): 1-2 hours +- Significant dispute (strategy, resource allocation): 24 hours +- Existential conflict (cofounder split, termination): 48-72 hours, ideally with a neutral third party present at reconvention + +### System 3: Strategic Surrender (Let Go to Get What You Want) + +A therapist posed the decisive question to a client in anguish over an uncontrollable situation: "What can you control in this uncontrollable conflict?" + +The answer, arrived at reluctantly: letting go. Letting go of the outcome, of the need to control, of the expectation that persistence alone would produce the desired result. + +The second answer, prompted by the therapist: taking care of yourself -- eating well, exercising, sleeping properly. These are always within control, even when nothing else is. + +**When strategic surrender applies:** + +- The other party will not move, and no amount of persuasion will change that. +- The conflict is consuming resources (time, emotional energy, focus) disproportionate to the potential resolution. +- Continuing to push is producing the opposite of the desired effect -- hardening the other party's position. + +**The Serenity Protocol for entrepreneurs:** + +1. **Identify what you cannot control.** The other person's decision. The market's reception. The investor's timeline. The cofounder's personal priorities. +2. **Identify what you can control.** Your response. Your health. Your next move. Your emotional state. +3. **Execute the letting-go decision.** This may mean ceasing communication, changing roles, ending a partnership, or simply accepting an outcome you did not want. +4. **Redirect energy to self-care and forward motion.** The founder who let go of an impossible personal situation lost sixty-nine pounds, got into the best shape of his life, left the company they shared, and ultimately got what he wanted -- over a year later, on terms that could never have been engineered through force. + +Strategic surrender is not defeat. It is the recognition that some conflicts have no resolution within the current frame and that the energy spent fighting is better invested in what remains within control. + +### System 4: The Bulletproof Vest Protocol + +Developed by relationship psychologist Dr. Bonnie Weil, this is a structured seven-step system for resolving recurring interpersonal conflicts. Originally designed for couples, it transfers directly to any close working relationship -- cofounders, business partners, long-term client relationships. + +**The seven steps:** + +**Step 1: Request an Appointment.** The aggrieved party requests a time to discuss the issue and offers three possible times. Critically, none of the options is "right now." This creates a cooling buffer and signals respect for the other person's readiness. + +**Step 2: Agree on a Safe Setting.** Both parties convene in a quiet, neutral space -- not a hallway, not a Slack channel, not a moving vehicle. + +**Step 3: Put On the Bulletproof Vest.** The party who caused the grievance agrees, explicitly and in advance, to absorb what they hear without defensiveness. No counter-arguments. No justifications. No "but." The vest is a commitment to receive without returning fire. + +**Step 4: Full Expression.** The aggrieved party describes the problem in full -- what happened, how it made them feel, and what impact it had. No interruptions. + +**Step 5: Mirror and Validate.** The other party mirrors back what they heard ("What I'm hearing is...") and validates the feelings ("I can understand why that would feel..."). Not solving. Not defending. Listening, mirroring, validating. + +**Step 6: Genuine Apology.** The offending party offers an authentic "I'm sorry." Not "I'm sorry you feel that way" (which is not an apology). Not "I'm sorry, but..." (which is a defence). A clean, unqualified apology. + +**Step 7: Three Solutions.** The aggrieved party proposes three positive solutions. The other party commits to at least one. Both parties then do something physical together -- a walk, a workout, a shared meal -- to biochemically seal the resolution. + +**Example in practice:** A founder felt criticised when his cofounder raised a sensitive personnel issue on a train -- a public, confined space with no exit. He requested an appointment. Two hours later, in their bedroom, she put on the bulletproof vest. He shared how criticised and trapped he had felt. She mirrored and validated without defending. She apologised. He proposed three solutions: (a) no work talk on the train, (b) no shared commute, or (c) a code word for when conversations get sensitive. She chose option (a) with option (c) as backup. They did jumping jacks. The problem never recurred. + +--- + +## Prompts + +**Prompt 1 -- Conflict Reframe:** +> I am in a conflict with [person/role] about [issue]. My instinct is to [defend / prove I'm right / escalate / avoid]. Help me reframe my internal stance from adversary to helper. Draft the exact words I should use to open our next conversation from a helping position, and suggest three questions I should ask to ensure they feel heard. + +**Prompt 2 -- Cooling Period Plan:** +> I just had a heated exchange with [person] about [issue]. I am currently [emotional state]. Help me draft a brief, calm message to defer resolution to a specific time, and create a cooling-period plan: what should I do in the next 24 hours to process this emotion before reconvening? + +**Prompt 3 -- Bulletproof Vest Preparation:** +> I need to use the Bulletproof Vest Protocol with [person] regarding [issue]. I am the [aggrieved party / offending party]. Walk me through what I should say at each of the seven steps, including (a) the appointment request, (b) mirroring and validation phrases I should use, (c) how to frame my apology authentically, and (d) three positive solutions I could propose. + +**Prompt 4 -- Strategic Surrender Assessment:** +> I have been in an ongoing conflict with [person/situation] for [duration]. Help me assess: (a) what I can control and what I cannot, (b) whether continued engagement is producing any progress or only hardening positions, (c) what a strategic surrender would look like in concrete terms, and (d) where I should redirect the energy I am currently spending on this conflict. + +--- + +## Use Cases + +**Cofounder Equity Dispute at Validation Stage** + +Two cofounders agreed on a 50/50 equity split at inception but six months later have radically different time commitments -- one is full-time, the other still has a day job. The full-time founder is resentful. The part-time founder feels ambushed. Both are flooded. Application: invoke the 24-hour rule. Set a meeting for two days later with a mutual advisor present. The advisor opens with the helping frame: "I'm here to help you both build something you're proud of." Each founder shares their perspective without interruption. The advisor mirrors and validates. Then the aggrieved founder proposes three vesting structures. They agree on one. The relationship survives because the process prevented a conversation during flooding. + +**Client Escalation at Growth Stage** + +A key client emails the CEO directly, furious about a missed delivery date. The CEO's instinct is to respond immediately with an explanation and a discount. Application: apply the 24-hour rule to the response (not 24 hours of silence -- a brief acknowledgement within an hour, with a detailed response scheduled for the following morning). Draft the response from a helping stance: "I want to understand exactly how this affected your team so we can make it right." When the call happens, the CEO puts on the bulletproof vest: absorbs the client's frustration without defending, mirrors the impact, apologises without qualification, and proposes three remediation options. The client chooses one. The account is retained. + +**Intractable Investor Disagreement at Scale** + +A board member insists on a strategic direction the CEO believes is wrong. Three board meetings of debate have produced only deeper entrenchment. Application: strategic surrender assessment. The CEO identifies what she can control (her own preparation, the data she presents, the support she builds among other board members) and what she cannot (this board member's opinion). She stops arguing the point directly, redirects energy toward building consensus with the remaining board, and presents a revised proposal at the next meeting with majority support already secured. The dissenting board member, no longer being pushed against, moderates his position. + +--- + +## Anti-Patterns + +**Cooling Period as Conflict Avoidance.** The 24-hour rule requires a specific reconvening time. "Let's talk about this later" without a date is not cooling -- it is avoidance. Unresolved conflicts compound. Each one left hanging deposits a small amount of resentment that accrues interest. + +**Bulletproof Vest Without Genuine Apology.** Going through steps 1-5 of the protocol and then offering "I'm sorry you feel that way" at step 6 invalidates the entire process. The vest requires absorbing; the apology requires owning. "I'm sorry I did X, and I understand why it hurt you" is the minimum viable apology. + +**Strategic Surrender as First Resort.** Letting go is for conflicts that genuinely cannot be resolved through engagement. Using it to avoid difficult conversations that could be resolved with effort is not strategic; it is abdication. + +**Reframing as Helping When You Are Not, In Fact, Helping.** Saying "I'm here to help" while privately committed to winning the argument produces a credibility collapse when the other party detects the incongruence -- and they will detect it. The helping frame must be genuine, which means genuinely being willing to accept an outcome that is not your preferred one. + +**Applying Couple's Therapy to Power-Asymmetric Relationships.** The Bulletproof Vest Protocol assumes rough equality between the parties. In a boss-subordinate conflict, asking the subordinate to put on the vest and absorb the boss's grievance without defence may produce compliance, not resolution. Power asymmetry requires additional structural safeguards -- a neutral third party, explicit assurance of no retaliation, and genuine willingness from the more powerful party to hear dissent. + +--- + +## By Stage + +| Stage | Common Conflict Type | Recommended Primary System | +|-------|---------------------|--------------------------| +| Idea | Cofounder vision misalignment; equity disputes | Bulletproof Vest Protocol (establishes conflict norms early) | +| Validation | Disagreements over pivot decisions; resource allocation with no resources | 24-Hour Rule + Helping Reframe | +| Early Traction | Employee conflicts as team grows past 5; first client disputes | Helping Reframe for mediation; Bulletproof Vest for partner relationships | +| Growth | Board disagreements; departmental friction; key-person conflicts | Strategic Surrender assessment for intractable positions; 24-Hour Rule for heated meetings | +| Scale | Cross-functional political conflicts; executive team disputes | All four systems in combination; institutional conflict-resolution norms | + +At the idea stage, cofounders who establish a conflict protocol before their first serious disagreement build a relationship that can survive the inevitable disagreements ahead. The Bulletproof Vest Protocol, adopted early, prevents the pattern of repeated unresolved fights that destroys cofounder relationships. At scale, the founder's role shifts from participant in conflicts to architect of systems that resolve them without the founder's direct involvement. + +--- + +## Output Template + +```markdown +# Conflict Resolution Plan + +**Parties Involved:** [Names/Roles] +**Issue:** [Concise description of the conflict] +**Current Temperature:** [Cold / Warm / Hot / Flooded] +**My Role:** [Aggrieved / Offending / Mediator] + +## Immediate Action +- [ ] If flooded: send cooling message and set reconvening time + - Message: "[Draft cooling message]" + - Reconvening: [Specific date and time] +- [ ] If calm: proceed to system selection + +## System Selection +- [ ] Helping Reframe (I am mediating or the conflict is new) +- [ ] 24-Hour Rule (emotions are high; productive conversation is impossible now) +- [ ] Strategic Surrender (conflict is intractable; continuing produces no progress) +- [ ] Bulletproof Vest Protocol (recurring pattern with a close working partner) + +## If Bulletproof Vest Protocol +1. Appointment request sent: [date/time options offered] +2. Location: [neutral, quiet setting] +3. Who wears the vest: [name] +4. My three proposed solutions: + - Option A: [solution] + - Option B: [solution] + - Option C: [solution] +5. Physical activity to seal resolution: [walk / meal / workout] + +## If Strategic Surrender +- What I cannot control: [list] +- What I can control: [list] +- Letting-go action: [specific step] +- Energy redirection: [where effort goes instead] + +## Follow-Up +- Check-in date to confirm resolution held: [date] +- Escalation plan if resolution fails: [next step] +``` + +--- + +## Related Skills + +- **[Thomas-Kilmann Conflict Modes](../frameworks/thomas-kilmann-conflict.md)** -- The five conflict modes provide the theoretical taxonomy; this skill provides the behavioural scripts for executing within those modes. +- **[Carnegie's Win Friends and Influence People](../frameworks/carnegie-win-friends.md)** -- Carnegie's principle of never criticising and seeing things from the other person's perspective underpin the Helping Reframe. +- **[Win-Win Negotiation](../frameworks/win-win-negotiation.md)** -- When conflict resolution transitions into formal negotiation over terms or resources, principled negotiation provides the structural framework. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- The willingness to enter difficult conversations, deliver genuine apologies, and absorb criticism without defence requires the emotional courage practices detailed in that skill. +- **[Influencing and Persuading](influencing-and-persuading.md)** -- The "choose happiness over rightness" technique is the precursor to strategic surrender detailed here. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Conflict resolution is only possible when team members feel safe enough to surface disagreements; without safety, conflicts go underground and fester. diff --git a/plugins/foreman/content/skills/people/teaching-and-leading.md b/plugins/foreman/content/skills/people/teaching-and-leading.md new file mode 100644 index 0000000..e399998 --- /dev/null +++ b/plugins/foreman/content/skills/people/teaching-and-leading.md @@ -0,0 +1,254 @@ +--- +name: "teaching-and-leading" +description: "Guides founders in leading through modelling behaviour, coaching (not managing), leveraging mirror neurons for mood contagion, distributing leadership titles generously, and using gratitude as a pre-meeting performance enhancer. Covers showing rather than telling, strengths-based leadership, the coach-and-student mindset, external accountability systems, vision-people-resources leadership triad, delivering bad news transparently, energy-state management, and making everyone a leader. Use when onboarding a first direct report, preparing to deliver difficult news to a team, noticing declining team morale, struggling with micromanagement tendencies, or building a leadership culture in an early-stage company." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - leadership + - coaching + - mirror-neurons + - modelling + - accountability + - gratitude + - transparency + - mood-contagion + - team-building + - delegation +related_skills: + - carnegie-win-friends + - persuasion-and-influence + - employee-engagement-retention + - delegation-and-empowerment + - mentoring-and-coaching + - psychological-safety-practice +author: "Fatih Guner" +--- + +# Teaching and Leading + +MIRROR NEURONS. Leadership is contagious -- and not in the metaphorical sense that motivational posters suggest. Mirror neurons, first identified in macaque monkeys and since confirmed in humans, fire both when an individual acts and when that individual observes the same action performed by another. The neurological implication for anyone who leads a team is uncomfortable in its directness: your mood, your posture, your energy state are being neurologically replicated in the people around you whether you intend it or not. A CEO who walks into a team meeting carrying the weight of a lost investor, a sick parent, and missed revenue numbers will produce a team that mirrors that weight. The meeting will underperform. The decisions will be cautious. The energy will be flat. Not because anyone was told to feel bad, but because their neurons had no choice. + +This is not a call for relentless, performative positivity. It is a call for deliberate state management -- the recognition that a leader's internal condition is, functionally, an external broadcast. What follows are ten leadership behaviours that exploit this contagion for constructive ends, each grounded in a specific practice rather than an abstract aspiration. + +--- + +## The Framework + +### Behaviour 1: Model, Don't Lecture + +A first-grade teacher's method for teaching subtraction: demonstrate the problem, demonstrate it again, then let the students try. She walked out of the room for twenty minutes. When she returned, twenty-two six-year-olds could subtract single digits -- because they had watched someone do it, not listened to someone explain it. + +The entrepreneurial translation: when teaching a new process, a sales methodology, or a company value, perform the task yourself while others watch. Narrate each step. Then perform it again. Only then hand it over. The instinct to explain is strong; the results of showing are stronger. + +| Teaching method | Retention rate | Founder's temptation | +|----------------|---------------|---------------------| +| Telling ("Here's how to do it") | Low | High -- it is fast and feels efficient | +| Showing once | Moderate | Medium -- requires patience | +| Showing twice, then supervised practice | High | Low -- requires the most time upfront, saves the most time downstream | + +The patience tax is real. The person you are teaching does not know what you know. Imagining them as a first-grader encountering the concept for the first time is not condescension; it is calibration. + +### Behaviour 2: Soar With Strengths + +The three-question leadership framework from the Entrepreneurs' Organization reduces the entire leadership function to three obligations: + +1. Set and communicate the overall vision. +2. Ensure the right people are in the right seats. +3. Ensure sufficient resources and capital for the team to succeed. + +"Right people, right seats" is the strengths mandate. Two questions determine whether someone belongs in their current role: How capable are they of doing the job? How aligned are they with the vision and values? When the answer to either question is equivocal, the seat needs to change -- not necessarily the person. A brilliant engineer miscast as a people manager is not a performance problem; it is a seating problem. + +Founders who hire a nanny interview twenty candidates before choosing one. They should apply the same rigour to every seat in the company. + +### Behaviour 3: Be a Coach and Student, Not a Teacher and Manager + +Three archetypes from a single school corridor illustrate the spectrum: + +- **Ms. Macusor** (the manager-as-tyrant): yelled, excluded late arrivals, criticised struggling students. Inspired only fear. Left teaching to become a cashier. +- **Doc Rubenstein** (the coach): "It's not my job to teach you. It's your job to learn. I'm just here to coach you along the way." Did less formal teaching than any teacher. Was one of the best. +- **Mr. Boyle** (the student-leader): "I'm a student, just like you. I've just been learning this stuff a little bit longer." Never pulled rank. Considered himself a peer. + +Fear-based management produces short-term compliance and long-term attrition. Study after study confirms the pattern: intimidation works temporarily, then collapses. The alternative is the coach's stance -- supportive, accountable, alongside rather than above -- layered with the humility of someone who is also still learning. Direct reports respond to humility with trust, and trust is the only compound that converts effort into discretionary performance. + +### Behaviour 4: External Accountability + +The most reliable accountability mechanism is not self-discipline. It is another person who will ask you uncomfortable questions on a fixed schedule. + +The practice: identify one person -- a cofounder, an advisor, a peer -- and establish a recurring accountability exchange. Share your commitments. Report on them. Submit to their honest assessment. The psychological mechanism is simple: the prospect of admitting failure to someone you respect is a more powerful motivator than any internal resolution. + +This applies symmetrically. When you want your team to hold themselves accountable, do not hold them accountable yourself. Create structures -- public commitments, peer check-ins, shared dashboards -- where accountability is social rather than hierarchical. + +### Behaviour 5: The I in Leadership + +There is no "I" in team. There is one in leadership. Every team needs someone willing to step into the uncomfortable singularity of decision-making, vision-setting, and resource-allocation. A founder who treats leadership as a group activity -- where everyone's voice carries equal decisional weight -- often produces a leaderless organisation that feels democratic and accomplishes little. + +The correction is not autocracy. It is clarity about what only the leader can do: set the vision, make the final call when consensus fails, and take personal responsibility for outcomes. Everything else can and should be distributed. + +### Behaviour 6: Mirror Neurons and Mood Contagion + +A CEO learned about mirror neurons from a podcast guest on the same day he received news of a lost $500,000 investor, his father losing his teeth in a nursing home, and missed sales numbers. Armed with new understanding, he went to the bathroom before the team meeting, looked in the mirror, thought about the company's five-year vision, and reframed his emotional state. He walked into the meeting and described a future in which the team was ringing the NASDAQ bell. Nobody in the room knew how bad his day had been. + +The protocol for state management before any leadership moment: + +1. Acknowledge the negative emotion privately. Suppression backfires; acknowledgement processes. +2. Reconnect with the vision. What is the long-term picture that makes today's problem a footnote? +3. Write a thank-you note or list three things you are grateful for. Gratitude shifts neurochemistry faster than any cognitive technique. +4. Enter the room only after the shift is complete. + +This is not dishonesty. It is the recognition that broadcasting personal distress to a team produces contagious distress, not constructive empathy. + +### Behaviour 7: "Thank You" -- The Two Most Magnetic Words + +When asked "How are you?", most people say "Fine." One leadership trainer recommended a different answer: "Fantastic." The word is a social magnet. Common responses from others: "What are you on?" and "I'll have what you're having." It signals energy, optimism, and approachability -- all of which are contagious through the same mirror neuron pathway. + +Add a second word: "Imagine." Used to open a vision statement, "imagine" gives people permission to dream. Both words cost nothing, require no preparation, and produce disproportionate social returns. + +The deeper principle: verbal micro-choices accumulate into reputation. The leader who consistently answers with energy and frames the future with possibility becomes someone others want to be around. Influence follows proximity; proximity follows attraction. + +### Behaviour 8: Always Deliver Bad News Yourself + +Positivity without transparency produces a team that trusts the leader's mood but not the leader's information. When numbers are missed, when layoffs are necessary, when a product launch fails -- the leader delivers the brutal facts personally. + +A CEO missed quarterly numbers and knew layoffs were coming. A mentor paraphrased Jim Collins: "As important as it is for you to remain positive, it's even more important for you to make sure that you and your team address the brutal facts and reality of your situation at all times." The CEO opened the retreat with: "We've missed our numbers and we are going to have to make layoffs." The team responded by adding transparency as a core company value. They put the business plan on the office walls for everyone -- including the janitors -- to see. + +The formula: deliver the truth + remain committed to the vision + show the path forward. Transparency builds trust. Trust sustains teams through bad quarters. Optimism alone does not. + +### Behaviour 9: Get High (on Gratitude) Before Every Meeting + +A chronically negative entrepreneur began a gratitude practice: writing down what he was grateful for and sharing it with an accountability partner daily. The results were transformative. His coach, initially supportive from the sidelines, became envious of the mood shift and adopted the same practice: three handwritten thank-you cards each morning on the commute, a family dinner ritual of naming one person each family member was grateful for, and grateful thoughts before sleep. + +The discovery: gratitude functions as an on-demand mood enhancer. Before a speech, write a thank-you card. Before an investor meeting, list five things you are grateful for. Before a difficult conversation, remind yourself of what is working. The mood shift is real, and thanks to mirror neurons, it transfers directly to everyone in the room. + +The escalation path for building a gratitude habit: + +1. Week 1: One thank-you card per week. +2. Week 2-3: One per day. +3. Week 4+: Three per day, written during transition time (commute, between meetings). +4. Add a nightly family or personal gratitude reflection. + +### Behaviour 10: Let Everyone Be a Leader + +A first-grade teacher at PS 230 in Brooklyn assigned leadership roles for every classroom task: line leaders, homework leaders, bathroom pass leaders, activity leaders, chalkboard leaders. Every child felt ownership, responsibility, and pride. The class ran itself. + +The corporate equivalent: be generous with leadership titles. Assign as many as possible. "President of table clearing" turned a reluctant child into a proud nightly contributor. Vice president titles at a startup cost nothing and produce ownership, commitment, and initiative. + +The principle: given the choice between leader and follower, nearly everyone chooses leader. People who think of themselves as leaders behave like leaders. The founder's job is to create enough leadership positions that everyone holds one. + +--- + +## Prompts + +**Prompt 1 -- Modelling Plan:** +> I need to teach my team [specific process or behaviour]. Draft a modelling plan: what should I demonstrate myself, how many times, and at what point should I hand over to supervised practice? Assume my team members are encountering this for the first time. + +**Prompt 2 -- Right People, Right Seats Audit:** +> Here are my team members and their current roles: [list]. For each person, assess: (a) capability for current role, (b) alignment with our vision [state vision]. Identify any seating mismatches and suggest role adjustments that leverage each person's strengths. + +**Prompt 3 -- Bad News Delivery Script:** +> I need to communicate [specific bad news] to my team of [size]. Draft opening remarks that: (a) state the brutal facts without hedging, (b) acknowledge the emotional impact, (c) reaffirm the long-term vision, and (d) outline the immediate path forward. The tone should be transparent but resolute. + +**Prompt 4 -- Leadership Distribution Map:** +> My team has [number] members. List every recurring task, project, and responsibility that currently lacks a named owner. For each, suggest a leadership title and the person best suited to hold it. The goal is maximum distributed ownership. + +--- + +## Use Cases + +**Pre-Seed Founder Onboarding a First Employee** + +A solo founder hiring employee number one faces an immediate teaching challenge: every process that has lived only in the founder's head must now be transferred. Rather than writing a 40-page handbook (which will not be read), the founder spends the first week modelling each workflow -- customer outreach, code deployment, investor update emails -- performing each task while the new hire observes. By week two, the new hire replicates each process under supervision. By week three, they own it. The founder resists the urge to explain verbally and instead shows, twice, every time. + +**Series A CEO Navigating a Down Quarter** + +Revenue missed forecast by 30%. Two enterprise customers churned. The CEO has a weekly all-hands in 48 hours. The temptation is to spin: "We're learning, we're growing, challenges are opportunities." The alternative: open with the numbers, unvarnished. "We missed by 30%. Two customers left. Here is what I believe went wrong, and here is what we are changing this quarter." Then -- and only then -- pivot to vision. The team will remember that the CEO trusted them with the truth long after they forget the specific numbers. + +**Growth-Stage Company with Flat Morale** + +A 40-person company has noticed declining engagement scores. The CEO discovers, through honest self-assessment, that her own stress has been leaking into every meeting for months. Mirror neurons have done their work. The intervention: a personal gratitude practice before every team interaction, a deliberate shift from problem-focused opening remarks to vision-focused ones, and the creation of fifteen new leadership titles across the organisation -- giving every team member visible ownership of something that matters. + +--- + +## Anti-Patterns + +**The Positivity Facade.** Gratitude practice and state management are not permission to suppress every negative signal. A CEO who smiles through a crisis while the team can see the building burning loses credibility, not gains it. The balance: manage your state for transient bad moods; be transparent about structural challenges. + +**Coaching Without Standards.** "Be a coach, not a manager" does not mean eliminating performance expectations. Coaches hold athletes accountable. The absence of standards is not coaching; it is abdication. + +**Title Inflation as Substitute for Substance.** Distributing leadership titles works when each title comes with real ownership and real accountability. A "VP of Community" who has no budget, no authority, and no metrics is not a leader; they are a participant with a flattering label. + +**Modelling Without Release.** Some founders model the task, then continue doing the task themselves because the employee "isn't doing it quite right yet." Modelling requires the discipline to hand over and accept imperfect replication as part of the learning curve. + +**Weaponising Mirror Neurons.** Understanding mood contagion is not a licence for emotional manipulation. Walking into a room with manufactured urgency to create artificial pressure is the dark application of the same science. The ethical use is managing your authentic state to create conditions where others can do their best work. + +--- + +## By Stage + +| Stage | Leadership Priority | Dominant Behaviour | +|-------|-------------------|-------------------| +| Idea | Converting believers without a product | Confidence projection; vision communication; modelling work ethic | +| Validation | Teaching the first 1-3 employees everything | Modelling (Behaviour 1); coach mindset (Behaviour 3) | +| Early Traction | Building culture before it forms accidentally | Distributed leadership (Behaviour 10); gratitude rituals (Behaviour 9) | +| Growth | Surviving bad news and maintaining trust | Transparent bad-news delivery (Behaviour 8); right people, right seats (Behaviour 2) | +| Scale | Sustaining mood and culture across hundreds of people | Mirror neuron management (Behaviour 6); institutionalised accountability (Behaviour 4) | + +At validation stage, the founder is the primary teacher -- there is no one else. Modelling is not optional; it is the only scalable knowledge-transfer mechanism when the team is smaller than a dinner party. At scale, the founder's direct teaching influence fades, but their mood influence intensifies: a single off-day from the CEO propagates through layers of management via the same mirror neuron cascade. + +--- + +## Output Template + +```markdown +# Leadership Behaviour Audit + +**Leader:** [Name] +**Team Size:** [Number] +**Current Challenge:** [Primary leadership issue] + +## State Management Check +- Current dominant mood entering meetings: [honest assessment] +- Pre-meeting gratitude practice in place: [yes/no] +- Last time bad news was delivered transparently: [date and outcome] + +## Modelling Assessment +- Processes currently taught by telling, not showing: [list] +- Plan to convert to modelling: [specific steps] + +## Right People, Right Seats +| Person | Current Role | Capability (1-5) | Value Alignment (1-5) | Action | +|--------|-------------|-------------------|----------------------|--------| +| [Name] | [Role] | [Score] | [Score] | [Keep / Move / Develop] | + +## Distributed Leadership Map +| Task/Responsibility | Current Owner | Proposed Leader | New Title | +|--------------------|--------------|-----------------|-----------| +| [Task] | [Unowned / Founder] | [Person] | [Title] | + +## Accountability Structure +- Accountability partner: [Name] +- Check-in frequency: [Weekly / Biweekly] +- Public commitment mechanism: [Dashboard / Stand-up / Shared doc] + +## Next 30 Days +1. [Specific leadership behaviour to implement] +2. [Specific leadership behaviour to implement] +3. [Specific leadership behaviour to implement] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends and Influence People](../frameworks/carnegie-win-friends.md)** -- The principle of sincere appreciation is the theoretical foundation for the gratitude and praise behaviours detailed here. +- **[Persuasion and Influence](../leadership/persuasion-and-influence.md)** -- Complements this skill's focus on leading teams with a focus on influencing individuals in meetings and one-on-ones. +- **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- Distributed leadership and gratitude practices directly affect retention metrics covered in that skill. +- **[Delegation and Empowerment](../leadership/delegation-and-empowerment.md)** -- The mechanics of handing over after modelling are detailed in the delegation framework. +- **[Mentoring and Coaching](../leadership/mentoring-and-coaching.md)** -- Extends the coach-and-student mindset into structured mentoring relationships. +- **[Inspiring and Retaining](inspiring-and-retaining.md)** -- The interpersonal retention practices from that sibling skill complement the team leadership and modelling techniques taught here. diff --git a/plugins/foreman/content/skills/people/understanding-people.md b/plugins/foreman/content/skills/people/understanding-people.md new file mode 100644 index 0000000..b011cc9 --- /dev/null +++ b/plugins/foreman/content/skills/people/understanding-people.md @@ -0,0 +1,207 @@ +--- +name: "understanding-people" +description: "Applies modern personality-decoding and rapid-understanding techniques to entrepreneurial relationships. Covers the Enneagram as a superior alternative to Myers-Briggs for self-awareness and team communication, the discipline of getting anyone even when chemistry is absent, three-question rapid-understanding for first meetings, being interested rather than interesting, and addressing the pervasive loneliness that shapes professional interactions. Use when building cofounder relationships, conducting customer discovery, onboarding new hires, preparing for investor meetings, or diagnosing communication breakdowns within teams." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - personality-assessment + - enneagram + - listening + - self-awareness + - empathy + - first-meetings + - rapport +related_skills: + - meeting-the-right-people + - reading-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +# Understanding People + +Myers-Briggs is a party game. The Enneagram is a real tool. The difference matters. + +Myers-Briggs assigns people to one of sixteen types based on binary preferences. Take the test twice and there is a meaningful probability of receiving a different result. The assessment measures states, not traits -- and states shift with mood, context, and Tuesday's weather. The Enneagram, by contrast, identifies nine core motivational patterns that remain stable over time because they measure *what drives behaviour*, not what behaviour looks like on a given afternoon. For entrepreneurs, who must read cofounders across years and investors across minutes, the distinction between a parlour-trick classification and a stable motivational map is the distinction between guesswork and strategy. + +Self-awareness is the prerequisite for influence. Until the founder understands her own motivational architecture -- why she says yes to everything (Type 3), why she avoids conflict at the cost of clarity (Type 9), why she hoards information as a form of control (Type 5) -- her attempts to understand others will be filtered through distortions she cannot see. + +--- + +## The Framework + +Understanding people operates on three progressively deeper levels. Each level builds on the one before it, and all three are required for genuine interpersonal effectiveness. + +### Level 1: Understand Yourself First (The Enneagram) + +The Enneagram identifies nine core types, each defined by a dominant motivation and a characteristic pitfall. + +| Type | Core Drive | Common Pitfall | Entrepreneurial Manifestation | +|------|-----------|----------------|-------------------------------| +| 1 | Striving to be perfect | Rigid standards paralysing progress | Founder who cannot ship an MVP because "it's not ready" | +| 2 | Striving to be connected | Over-giving, boundary collapse | Cofounder who cannot say no to any request from team or customers | +| 3 | Striving to be outstanding | Saying yes to everything, burnout | CEO who accepts every speaking invitation while the company drifts | +| 4 | Striving to be unique | Emotional volatility, envy of competitors | Founder who pivots product based on aesthetic vision rather than data | +| 5 | Striving to be detached | Information hoarding, isolation | Technical cofounder who builds in silence and resents interruption | +| 6 | Striving to be secure | Analysis paralysis, worst-case fixation | Operator who cannot commit to a pricing model without twelve spreadsheets | +| 7 | Striving to be excited | Shiny-object syndrome, half-finished projects | Serial entrepreneur who launches five things and finishes none | +| 8 | Striving to be powerful | Bulldozing team, alienating partners | Founder whose "intensity" is a euphemism for intimidation | +| 9 | Striving to be peaceful | Conflict avoidance, passive agreement | CEO who tells every board member what they want to hear | + +The Enneagram does not change over time the way Myers-Briggs results do. The founder who is a Type 3 at twenty-five will be a Type 3 at forty-five. What changes is the *relationship* to the type: awareness of the pitfall enables rewriting the internal script. The Type 3 who recognises the "I'll Do It" syndrome can learn that saying no to some commitments produces more outstanding outcomes in the ones that remain. + +### Level 2: Get Anyone (The Coffee Experiment) + +Understanding people who are naturally likeable requires no technique. The real test is understanding people who provoke frustration, confusion, or outright dislike. Every entrepreneur has a "John" -- the business partner, board member, or key client who seems impervious to rapport. The instinctive response is to label them ("I just don't get him") and route around them. The label, however, is not a diagnosis. It is a resignation that guarantees the relationship will never improve. + +The method is deceptively simple: + +1. **Refuse the narrative.** Stop saying "I don't get him." The declaration itself becomes a self-fulfilling prophecy -- a closed cognitive loop that prevents new information from entering. +2. **Invest fifteen minutes and five dollars.** Take the difficult person for coffee outside the professional context. The shift in environment reduces defensive posture on both sides. +3. **Ask questions, then shut up and listen.** The objective is not to like the person. It is to understand what drives them -- which Enneagram type they approximate, what their formative experiences were, why they behave as they do. + +Understanding does not require agreement or affection. A founder who understands that a difficult board member is a Type 8 driven by fierce independence (often rooted in early-life adversity) can work with that knowledge strategically -- framing proposals as challenges rather than requests, for instance -- even if personal warmth never develops. The coffee meeting is not therapy. It is reconnaissance. Thirty minutes and a five-dollar espresso frequently yield more strategic intelligence than months of frustrated guesswork. + +### Level 3: Rapid Understanding (The Three-Question Method) + +Standard networking questions -- "Where are you from?" "What do you do?" -- yield standard, forgettable answers. Larry Benet's three-question framework replaces small talk with questions that reveal values, aspirations, and identity in under three minutes: + +1. **What is the most exciting thing you are working on right now?** (Reveals current passion and professional direction.) +2. **If you had enough money to retire and then some, what would you be doing?** (Reveals intrinsic motivation stripped of financial necessity.) +3. **What is your favourite charity to support, and why?** (Reveals values and emotional commitments.) + +These questions work because they bypass the social scripts people recite on autopilot and engage the deeper structures of identity. A founder who uses these in a first meeting will remember that conversation years later -- and more critically, the other person will remember being understood. + +The technique generalises beyond Benet's specific trio. Any question that targets values, aspirations, or emotional commitments will outperform biographical data collection. Ten alternative questions serve the same function: + +- What is the most exciting thing in your personal life right now? +- If you were not doing what you do today, what would you be doing and why? +- Other than a family member, who has been your most important influence? +- How would your favourite teacher describe you? +- What would you choose to do for a day if there were no constraints? + +The principle is consistent: replace "where" and "what" questions (which elicit facts) with "why" and "how" questions (which elicit identity). The shift takes three seconds of deliberate intention and produces a fundamentally different quality of conversation. + +### The Substrate: Loneliness and Connection + +Most people are lonely. Even the most outwardly successful, well-adjusted individuals carry stretches of disconnection that shape how they respond to someone who genuinely listens. The founder who approaches people with authentic intent to understand and connect differentiates herself from the vast majority of professionals, who are too preoccupied with their own concerns to focus on others. When the founder fills that void -- even for twenty minutes over a charged phone -- a disproportionate reciprocity often follows. Not because the listener was calculating, but because genuine connection is so rare that people remember and reward it instinctively. + +The Carnegie principle -- "be interested, not interesting" -- remains the single most efficient interpersonal technique available. Humans love to talk about themselves. Neuroscience confirms that self-disclosure activates the brain's reward centres. The person who listens attentively, asks follow-up questions, and resists the urge to redirect the conversation to their own story will be remembered as extraordinary -- despite having said almost nothing. + +Carnegie articulated this in 1936. The framework updates it for an era of performative self-promotion on social media, where the incentive structure rewards broadcasting over receiving. The modern founder faces a paradox: every platform encourages her to be interesting (post content, build a following, project expertise), while every meaningful relationship rewards her for being interested (ask questions, listen deeply, let the other person feel significant). The resolution is not to abandon the public persona but to ensure that in private interactions -- the ones that actually determine whether investors, partners, and employees say yes -- listening dominates speaking by a ratio no smaller than three to one. + +--- + +## Prompts + +**Prompt 1 -- Enneagram Team Mapping:** +> My cofounding team consists of [describe 2-4 people with brief behavioural descriptions]. Based on these descriptions, estimate each person's likely Enneagram type. For each, identify the core motivation, the predictable pitfall in a startup context, and one specific communication adjustment I should make when working with that person. Flag any type combinations that are likely to produce friction and suggest a mitigation strategy. + +**Prompt 2 -- Difficult Relationship Decoding:** +> I am struggling to work productively with [describe the person, their role, and specific frustrating behaviours]. Using the Enneagram framework and the "get anyone" method, help me (1) hypothesise what motivates this person's behaviour, (2) design a low-stakes interaction outside our normal context to test that hypothesis, and (3) prepare three questions I can ask during that interaction that will reveal whether my hypothesis is correct. + +**Prompt 3 -- First-Meeting Question Design:** +> I have a [15/30/60]-minute first meeting scheduled with [describe the person and context]. Design a sequence of questions that will move quickly past small talk and reveal this person's values, motivations, and potential alignment with my venture. The questions should feel natural, not interrogative, and should be calibrated to the formality of the setting. + +**Prompt 4 -- Self-Awareness Audit:** +> Based on the following description of my typical behaviours and tendencies [provide description], identify my likely Enneagram type. Then list three specific situations in my entrepreneurial journey where my type's characteristic pitfall is most likely to cause problems, and provide a concrete rewrite of the internal script for each situation. + +--- + +## Use Cases + +**Idea-Stage Founder Choosing a Cofounder** + +A technical founder (likely Type 5 -- detached, analytical, information-hoarding) is evaluating two potential cofounders for a fintech venture. By mapping each candidate against the Enneagram, she identifies that Candidate A is a Type 3 (outstanding, driven, prone to overcommitment) and Candidate B is a Type 8 (powerful, direct, prone to bulldozing). Rather than choosing based on chemistry, she evaluates which pitfall pattern is more manageable alongside her own. A Type 5 paired with a Type 8 will produce direct, uncomfortable conversations about strategy -- which is productive friction. A Type 5 paired with a Type 3 risks two people working furiously in parallel without genuine communication. She chooses Candidate B and structures their working relationship around weekly "coffee experiments" to maintain mutual understanding as pressure increases. + +**Validation-Stage Founder in Customer Discovery** + +A consumer-health startup founder uses the three-question method during a networking dinner with potential early adopters. Instead of pitching her product, she asks each person at the table: "What is the most frustrating thing about managing your health right now?" and "If you had unlimited resources, what would you change about your daily routine?" Two responses reveal a latent pain point she had not considered -- medication tracking for elderly parents -- which becomes a feature that drives her first thousand sign-ups. She never would have heard it through a survey. The questions created the conditions for people to reveal what they actually care about, not what they think a founder wants to hear. + +**Growth-Stage CEO Diagnosing a Dysfunctional Leadership Team** + +A CEO notices that leadership meetings have become performative -- people agree in the room and disagree in the corridor. She administers the Enneagram to her six direct reports and discovers the team is heavily skewed toward Types 3, 6, and 9: achievers who fear failure, loyalists who fear uncertainty, and peacemakers who fear conflict. The team's composition creates a structural incentive to avoid hard conversations. She redesigns the meeting format to begin with a two-minute silence followed by the three-question method applied to a business challenge: "What is the most exciting thing about this quarter?" "If resources were unlimited, what would we do differently?" "What is the one thing we are avoiding discussing?" The shift from performative updates to values-revealing questions surfaces the real issues within three meetings. + +--- + +## Anti-Patterns + +1. **Using the Enneagram as a Label Gun.** Assigning types to colleagues and then using those types to dismiss behaviour -- "Oh, that's just his Type 8 talking" -- rather than to understand and adapt. The Enneagram is a communication tool, not a sorting hat. The moment it becomes an excuse to stop trying, it has failed. + +2. **Listening as Performance.** Sitting in silence while mentally rehearsing what to say next is not listening. Active listening requires genuine cognitive engagement with what the other person is saying. The difference is detectable. People know when they are being heard and when they are being waited out. + +3. **Forced Vulnerability in Professional Settings.** Asking the three deep questions at a formal investor pitch or a first board meeting. Context matters. Rapid-understanding techniques work in networking events, coffee meetings, and retreats. They misfire in settings where professional distance is expected and where premature intimacy reads as boundary violation. + +4. **Projecting Your Own Motivations.** Assuming that because *you* would respond well to direct feedback, everyone else will too. The entire premise of understanding people is that motivational structures differ. The Type 9 who needs gentle framing will not respond to the bluntness that energises a Type 8. + +5. **Treating Understanding as Agreement.** Understanding why a toxic investor behaves as they do does not obligate tolerance. Comprehension is a strategic asset. It does not require submission. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder selection | At the idea stage, the relationship between cofounders *is* the company. Enneagram mapping and the coffee experiment are cofounder due diligence -- cheaper than a term sheet and more predictive than a resume. | +| Validation | Customer discovery | Rapid-understanding questions applied to potential customers reveal motivations that structured interviews miss. "If money were no object, how would you solve this problem?" surfaces latent needs. | +| Early Traction | Hiring and culture | Administering the Enneagram to the first ten hires establishes a shared vocabulary for communication and conflict. The investment pays compound interest as the team grows. | +| Growth | Leadership development | The CEO's self-awareness becomes the ceiling for the organisation's emotional maturity. Growth-stage founders who have not confronted their own Enneagram pitfalls will reproduce those pitfalls in the culture. | +| Scale | Institutional empathy | At scale, understanding people cannot depend on the founder's personal attention. The techniques must be embedded in management training, onboarding, and meeting design so that the organisation itself listens. | + +--- + +## Output Template + +```markdown +# People-Understanding Audit: [Your Name / Company] + +## Self-Assessment +- **Enneagram type:** [Type and core drive] +- **Primary pitfall in current context:** [Specific behaviour pattern] +- **Script rewrite:** [New internal narrative] + +## Key Relationship Map +| Person | Role | Estimated Type | Core Drive | Communication Adjustment | +|--------|------|---------------|------------|-------------------------| +| [Name] | [Role] | [Type] | [Drive] | [Specific change] | + +## Difficult Relationship Plan +- **Person:** [Name] +- **Current friction:** [Description] +- **Hypothesis:** [Estimated type and motivation] +- **Planned interaction:** [Coffee experiment details] +- **Questions to ask:** [3 specific questions] + +## First-Meeting Protocol +- **Default opening questions:** + 1. [Question targeting current passion] + 2. [Question targeting intrinsic motivation] + 3. [Question targeting values] +- **Context adjustments:** [How questions change for investors vs. hires vs. customers] + +## 30-Day Practice Goals +1. [Specific listening practice commitment] +2. [Specific Enneagram application] +3. [Specific difficult-relationship initiative] +``` + +--- + +## Related Skills + +- **[Meeting the Right People](meeting-the-right-people.md)** -- Understanding people is the prerequisite; this sibling skill addresses how to find and filter the right people to understand in the first place. +- **[Reading People](reading-people.md)** -- Understanding operates at the motivational level; reading people adds the nonverbal and behavioural layer that reveals what words alone conceal. +- **[Connecting with People](connecting-with-people.md)** -- Understanding creates the map; connecting applies the Platinum Rule and validation techniques that transform understanding into genuine relationship. +- **[Carnegie's Win Friends](../frameworks/carnegie-win-friends.md)** -- Carnegie's 1936 principle of genuine interest is the foundation modernised here with specific techniques and the Enneagram. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's self-awareness domain provides the theoretical architecture; the Enneagram provides the practical assessment tool. +- **[Myers-Briggs Type Indicator](../frameworks/myers-briggs-type-indicator.md)** -- Provides an alternative personality framework that complements the Enneagram for understanding how people process information and make decisions. diff --git a/plugins/foreman/content/skills/stoic/stoic-acceptance-amor-fati.md b/plugins/foreman/content/skills/stoic/stoic-acceptance-amor-fati.md new file mode 100644 index 0000000..240f274 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-acceptance-amor-fati.md @@ -0,0 +1,200 @@ +--- +name: "stoic-acceptance-amor-fati" +description: "Teaches the advanced Stoic practice of amor fati -- not merely accepting what cannot be changed but actively loving one's fate, including its setbacks, losses, and disappointments. Provides the philosophical foundation for transforming suffering into fuel, releasing attachment to 'what should have been,' and reframing every event as material for growth. Use when an entrepreneur is stuck in resentment over a past failure, when a pivot feels like defeat rather than evolution, when loss or disappointment has calcified into bitterness, when learning-from-failure techniques feel insufficient because the problem is not tactical but existential, or when the founder needs a paradigm shift from enduring fate to embracing it." +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - amor-fati + - acceptance + - fate + - letting-go + - reframing + - loss + - disappointment + - attachment + - stoic + - radical-acceptance +related_skills: + - learning-from-failure + - stoic-fortitude-and-resilience + - stoic-virtue-and-kindness + - stoic-mortality-and-perspective + - growth-mindset +author: "Fatih Guner" +--- + +# Stoic Acceptance and Amor Fati + +NIETZSCHE'S FIRE. When Friedrich Nietzsche forged his most incandescent formula -- "My formula for greatness in a human being is amor fati: that one wants nothing to be different, not forward, not backward, not in all eternity" -- he was not inventing. He was borrowing. The Stoics had been there two millennia earlier, though they expressed it with less Germanic drama and more Roman discipline. Epictetus put it plainly: "Don't seek for everything to happen as you wish it would, but rather wish that everything happens as it actually will -- then your life will flow well." Marcus Aurelius, governing an empire beset by plague, war, and betrayal, repeated the injunction to himself so often that it became a meditative refrain. The instruction is deceptively simple and operationally ferocious: do not merely accept your fate. Love it. Not the sanitised, comfortable parts -- all of it. The failed fundraise, the departed co-founder, the market that refused to cooperate. This is not resignation dressed in philosophical clothing. It is a fundamentally different relationship with reality, and it separates founders who are consumed by what happened from founders who are fuelled by it. + +--- + +## The Framework + +Amor fati operates at a deeper level than conventional resilience or failure-recovery frameworks. Where practical approaches like post-mortems and pivot analysis address *what to do* after a setback, amor fati addresses *how to relate* to the setback itself. The distinction matters because entrepreneurs who master the tactical response but harbour resentment, regret, or bitterness about what happened carry a weight that no process can remove. + +### The Three Levels of Response to Adversity + +The Stoic tradition reveals a progression, not a single doctrine. Each level is harder than the last, and each yields correspondingly greater freedom. + +**Level 1: Resistance.** The default human response. The event should not have happened. Someone is to blame. If only things had gone differently. This level consumes enormous energy, produces no useful output, and frequently compounds the original problem. Marcus observed: "When you are distressed by an external thing, it's not the thing itself that troubles you, but only your judgment of it." + +**Level 2: Acceptance.** The Stoic baseline. The event happened. It cannot be unhappened. Fighting reality is irrational. One redirects energy from lamenting the past to acting in the present. This is already a significant achievement -- most people never reliably reach it. Acceptance is the foundation of practical frameworks like learning-from-failure. + +**Level 3: Amor Fati.** The Stoic summit. The event happened, and it is *good that it happened* -- not despite the pain, but including the pain. One does not merely tolerate fate; one loves the entire sequence of events that constitutes one's life, recognising that removing any element would produce a different person, a different company, a different trajectory. As Epictetus counselled, the wise person "embraces everything nature assigns." + +### The Mechanics of Amor Fati + +Amor fati is not magical thinking. It operates through four cognitive mechanisms. + +**Reinterpretation of necessity.** Chrysippus offered the analogy of a dog tied to a cart: the cart moves regardless; the dog can be dragged or can walk willingly. The entrepreneur's market, macroeconomy, regulatory environment, and competitive landscape are the cart. Amor fati is walking willingly -- and discovering that willing movement opens degrees of freedom that being dragged forecloses. + +**Dissolution of attachment.** Epictetus diagnosed attachment as the root cause of suffering: "If you hold anything dear outside of your own reasoned choice, you will have destroyed your capacity for choice." The founder attached to a specific outcome (this valuation, this customer, this co-founder) becomes fragile when that outcome fails to materialise. Amor fati dissolves the attachment not by devaluing the outcome but by expanding identity beyond it. You are not your last fundraise. You are the person who navigated whatever the fundraise produced. + +**Integration of the whole path.** Cancer survivors who describe their illness as "the best thing that ever happened to me" are practising amor fati instinctively. Musonius Rufus made the counterintuitive case explicit: "As for me, I would choose being sick over living in luxury, for being sick only harms the body, whereas luxury destroys both the body and the soul." The setback that felt like destruction was, in retrospect, the event that prevented a worse outcome or created a capability that would not otherwise exist. + +**Elimination of hope and fear as equals.** Hecato of Rhodes delivered the most disorienting Stoic insight: "Cease to hope and you will cease to fear." Hope and fear are both projections into a future one does not control. Both are enemies of presence. Amor fati replaces both with engaged participation in what is actually happening. + +### The Difference from Passive Acceptance + +This framework must be distinguished from passivity, fatalism, or learned helplessness -- a confusion that critics of Stoicism regularly exploit. + +| Passive Acceptance | Amor Fati | +|-------------------|-----------| +| "Things happen; there's nothing I can do." | "This happened; I will find the fuel in it." | +| Resignation to circumstances | Engagement with circumstances | +| Energy directed nowhere | Energy directed toward what one controls | +| Diminished agency | Expanded agency within constraints | +| Indifference to outcomes | Commitment to excellent action regardless of outcome | + +Marcus Aurelius did not sit in his tent and accept that the barbarians were at the border. He accepted the fact, loved the challenge it represented, and spent a decade campaigning in the field. FDR did not passively accept polio. He accepted the diagnosis, redirected his energy, and became the president who led America through the Depression and a world war. Amor fati is the most active form of acceptance imaginable. + +### The Glass Is Already Broken + +A Zen story, frequently cited alongside Stoic teaching, captures the practice of pre-emptive amor fati: a master who owned a beautiful cup repeated to himself, "The glass is already broken." He used the cup, enjoyed it, displayed it -- but in his mind it was already gone. When it shattered, he simply said, "Of course." Epictetus counselled the same regarding everything we prize: "Whenever you kiss your child, sibling, or friend, don't layer on top of the experience all the things you might wish, but hold them back and stop them." The instruction is not to love less but to love without the delusion of permanence. + +For the entrepreneur, the glass-already-broken practice applies to customers, employees, funding, market position -- every external asset. Enjoying them fully while acknowledging their impermanence is not pessimism. It is the only honest form of appreciation. And when the glass does break -- when the key hire leaves, the customer churns, the market shifts -- the founder who practised this awareness will recover in days what the unprepared founder mourns for months. + +### The Four Habits of the Stoic Mind + +Marcus Aurelius distilled the daily practice of amor fati into four cognitive habits that serve as a self-diagnostic checklist: + +1. **Accept nothing false or uncertain** -- strip away wishful interpretations and face the situation as it is. +2. **Direct impulses only to acts for the common good** -- ensure that your response to events serves more than your ego. +3. **Limit desires and aversions to what is within your power** -- release attachment to outcomes you cannot determine. +4. **Embrace everything nature assigns** -- this is amor fati itself, the capstone habit that transforms the other three from discipline into disposition. + +--- + +## Prompts + +**Prompt 1 -- Amor Fati Reframe:** +> I am struggling with a past event that I cannot change: [describe -- e.g., a failed startup, a broken partnership, a market timing miss, a personal crisis that derailed the business]. Walk me through the three levels of response: (1) Where am I still in Resistance mode? What judgements, blame, or "if only" thinking am I holding? (2) What does full Acceptance look like for this specific event? (3) What does Amor Fati look like -- how could I not just accept but genuinely love the entire path, including this event, as essential to who I am becoming? Be specific and grounded, not platitudinous. + +**Prompt 2 -- Attachment Inventory:** +> Help me identify my entrepreneurial attachments that are creating fragility. Consider my attachment to: [list -- e.g., a specific valuation target, a particular team member, a market position, a personal identity as "successful founder," a lifestyle standard]. For each attachment, apply Epictetus's test: Is this within my reasoned choice, or outside it? What would my decision-making look like if I released this attachment? What does amor fati say about the possibility that I might lose this thing? + +**Prompt 3 -- Hope-Fear Audit:** +> I am currently hoping for [outcome] and fearing [outcome]. Apply the Stoic insight that hope and fear are the same -- both are projections into a future I do not control. For each, identify: (1) What am I actually able to influence? (2) What would full presence in the current situation look like, stripped of both hope and fear? (3) What actions would I take if I were neither hoping nor fearing, but simply working with what is in front of me right now? + +**Prompt 4 -- Whole-Path Integration:** +> I need help seeing my entrepreneurial journey as a coherent whole rather than a series of wins and losses. My journey so far: [describe key events, including failures and setbacks]. Help me construct the narrative in which every event -- especially the painful ones -- was a necessary chapter. Not a forced positive spin, but a genuine examination of what each setback made possible, what it prevented, and how it shaped the capabilities I now have. What is the story of my path that I can genuinely love? + +--- + +## Use Cases + +**Founder Processing a Company Shutdown** + +After three years and two rounds of funding, a direct-to-consumer brand runs out of capital and shuts down. The founder is devastated -- not just professionally but existentially. Her identity was fused with the company. Applying the amor fati framework in structured sessions with a mentor, she moves through the levels. Level 1 (Resistance): she identifies the blame narratives she is carrying -- the investor who pulled out, the supply-chain disruption, the co-founder who lost commitment. Level 2 (Acceptance): she acknowledges that each of these factors, while real, is now past. No amount of blame will reopen the company. Level 3 (Amor Fati): she maps the capabilities the three years produced -- operational expertise, investor relationships, customer insight, and a clarity about what she actually wants to build next that was impossible before she built and lost the first thing. Six months later, she describes the shutdown as "the tuition I paid for the company I'm building now." + +**Growth-Stage CEO After a Devastating Pivot** + +A B2B SaaS company that spent two years building an enterprise product discovers that the market has shifted and the product's architecture cannot adapt. The CEO must pivot to a different customer segment, effectively abandoning the work of 30 engineers over 18 months. The team's morale fractures. Investors are sceptical. The CEO's own confidence is shaken. Rather than treating the pivot as damage to be managed (a purely tactical response), the CEO applies the amor fati paradigm to the entire organisation. In a transparent all-hands meeting, she reframes: the enterprise phase was not wasted work -- it was the process by which the team developed the technical depth, customer understanding, and organisational resilience that the new direction requires. She names specific capabilities that exist only because of the "failed" effort. The pivot is not a retreat from the original vision but the next chapter in a story that includes the original vision as essential prologue. The reframe does not eliminate disappointment, but it provides a narrative structure within which the team can reengage. + +**Idea-Stage Founder Releasing a Previous Career Identity** + +A senior executive at a Fortune 500 company leaves to pursue an entrepreneurial vision. Eighteen months in, with no revenue and dwindling savings, he finds himself mourning the status, compensation, and certainty of his previous life. The attachment -- to the identity of "successful executive" -- is creating a paralysis that prevents full commitment to the messy, uncertain, low-status reality of building from zero. The amor fati exercise forces a direct confrontation: the corporate career is not an alternative present. It is a past. Wishing it back is as irrational as wishing yesterday's weather were different. The Stoic question is not "Was I happier then?" but "What does this current chapter make possible that the previous one could not?" The answer, once he examines it honestly, includes creative freedom, alignment between work and values, and the chance to test whether his ideas actually work -- none of which were available in the corporate role he romanticises. + +--- + +## Anti-Patterns + +1. **Toxic positivity in philosophical disguise.** Amor fati is not "everything happens for a reason" served with a forced smile. It is a rigorous practice of reinterpretation that acknowledges pain as real and loss as genuine. The founder who uses amor fati to bypass grief, avoid difficult emotions, or dismiss others' suffering has confused philosophy with denial. + +2. **Using acceptance to avoid accountability.** "I accept what happened" is not the same as "I bear no responsibility for what happened." Amor fati includes loving the consequences of one's own mistakes -- which requires first acknowledging them. The Stoic who accepts fate without examining their own contribution to it is practising evasion, not philosophy. + +3. **Premature amor fati.** There is a sequence. Resistance must be acknowledged before it can be released. Acceptance must be achieved before it can be transcended. The founder who leaps to "I love this" while still seething with resentment is performing philosophy rather than practising it. Grant yourself time. Seneca did not expect immediate equanimity. + +4. **Confusing amor fati with the absence of ambition.** Loving your fate does not mean abandoning the desire to shape it. Marcus Aurelius loved his fate and simultaneously worked to improve the empire. Epictetus loved his fate and simultaneously taught thousands. Amor fati is about relationship to what *has happened*, not surrender of what *could happen*. + +5. **Applying amor fati to others' suffering.** Telling a struggling colleague, employee, or co-founder that they should "love their fate" is not wisdom; it is cruelty. Amor fati is a discipline one applies to one's own experience. Others deserve empathy, practical help, and the space to process difficulty on their own terms. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Releasing the previous identity | Most founders at the idea stage are mourning something: a career, a salary, a status, a certainty. Amor fati at this stage means genuinely loving the act of leaving -- not as sacrifice but as liberation. The previous chapter was necessary and is now complete. | +| Validation | Loving the "no" | Validation is a sustained encounter with rejection. Amor fati transforms rejection from evidence of failure into evidence of engagement with reality. Each "no" refines the proposition. The founder who loves the process of discovering what the market actually wants -- rather than resenting the market for not wanting what was offered -- learns faster. | +| Early Traction | Embracing the messy middle | Early traction is neither the excitement of inception nor the vindication of growth. It is operational grind. Amor fati at this stage means finding fuel in the repetitive, unglamorous work of converting initial interest into sustainable revenue. | +| Growth | Integrating the losses that growth entails | Growth always involves loss: the intimate team culture of the early days, the founder's hands-on involvement in every decision, key people who leave because the company has outgrown them. Amor fati means loving the full trajectory, not just the growth metrics. | +| Scale | Accepting the company's independence from the founder | At scale, the company becomes an entity that operates beyond the founder's direct control. Amor fati at this stage means loving the fact that the organisation has its own momentum, its own culture, its own trajectory -- even when that trajectory diverges from the founder's original vision. | + +A note on progression: amor fati does not arrive as a permanent state. It is a practice that must be renewed with each new challenge. The founder who achieved genuine acceptance after a failed fundraise may find themselves in full resistance mode after a co-founder departure. This is normal. The practice is the return -- the repeated movement from resistance through acceptance toward love -- not a destination from which one never retreats. + +--- + +## Output Template + +```markdown +# Amor Fati Assessment + +**Founder:** [Name] +**Date:** [Date] +**Event Under Examination:** [The setback, loss, or disappointment being processed] + +## Current Level of Response +- [ ] Level 1: Resistance (blame, "if only," resentment still active) +- [ ] Level 2: Acceptance (event acknowledged as past, energy redirected) +- [ ] Level 3: Amor Fati (event embraced as essential chapter) + +## Resistance Inventory +| Residual Resistance | Source | What Releasing It Would Free | +|---------------------|--------|------------------------------| +| [Blame/resentment/regret] | [Person/event/decision] | [Energy/clarity/action it currently blocks] | + +## Attachment Audit +| Attachment | Inside Reasoned Choice? | Risk of Loss | What Releasing It Enables | +|-----------|------------------------|--------------|--------------------------| +| [Specific attachment] | Yes / No | [High/Medium/Low] | [Freedom/clarity gained] | + +## Whole-Path Integration +- **What this event made possible:** [Capabilities, insights, relationships that exist only because of it] +- **What this event prevented:** [Worse outcomes that the setback inadvertently avoided] +- **The narrative I can genuinely love:** [The honest, complete story of the path] + +## Present-Moment Focus +- **What I am hoping for (and releasing):** [Projection into future] +- **What I am fearing (and releasing):** [Projection into future] +- **What I can act on right now:** [Actions within reasoned choice, today] +``` + +--- + +## Related Skills + +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- Covers the practical mechanics of failure response; this skill provides the philosophical foundation that makes those practices stick by transforming the emotional relationship with failure itself. +- **[Stoic Fortitude and Resilience](stoic-fortitude-and-resilience.md)** -- Fortitude is the capacity to endure adversity; amor fati is the capacity to embrace it. The progression from endurance to love is the difference between surviving and being transformed. +- **[Stoic Virtue and Kindness](stoic-virtue-and-kindness.md)** -- Virtue requires a settled relationship with one's circumstances; the entrepreneur consumed by resentment cannot practise justice or wisdom in the present. +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Dweck's framework posits that challenges are opportunities for growth; amor fati takes this further, treating challenges as not merely useful but loveable. +- **[Stoic Mortality and Perspective](stoic-mortality-and-perspective.md)** -- The awareness that life is finite gives amor fati its urgency; every hour spent in resentment is an hour subtracted from a brief, unrepeatable span. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- The philosophical discipline of embracing rather than resisting fate provides leaders with the emotional grounding to model calm during organisational transitions. diff --git a/plugins/foreman/content/skills/stoic/stoic-control-and-clarity.md b/plugins/foreman/content/skills/stoic/stoic-control-and-clarity.md new file mode 100644 index 0000000..0e4fb0d --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-control-and-clarity.md @@ -0,0 +1,199 @@ +--- +name: "stoic-control-and-clarity" +description: "Applies Epictetus's dichotomy of control to entrepreneurial decision-making, separating what founders can influence from what they cannot. Synthesises the foundational Stoic practice of mental clarity through intentionality, purpose, and disciplined focus. Use when overwhelmed by variables outside your control, paralysed by uncertainty, struggling to prioritise amid chaos, losing focus on core purpose, or needing a philosophical framework for saying no." +version: "1.0.0" +category: "stoic" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - dichotomy-of-control + - clarity + - focus + - prioritisation + - decision-making + - intentionality + - epictetus +related_skills: + - stoic-emotional-mastery + - stoic-self-awareness + - stoic-unbiased-thought + - leader-resilience-and-wellbeing + - leader-self-reflection + - focus-and-priority-management + - eisenhower-matrix + - covey-seven-habits +author: "Fatih Guner" +--- + +# The Dichotomy of Control + +All of Stoic philosophy can be summarised in a single sentence, and that sentence is the first lesson every entrepreneur needs. Epictetus opens the *Enchiridion* with it: "Some things are in our control, while others are not." That's it. The entire philosophical tradition -- twenty-three centuries of it -- rests on the ability to draw one clean line between what you can change and what you cannot. Most founders spend the better part of their careers hurling themselves at the wrong side of that line, expending energy on market conditions they cannot alter, competitors they cannot silence, and investor sentiment they cannot manufacture. The dichotomy of control is not merely a Stoic concept. It is the operating system upon which every other Stoic concept runs. + +--- + +## The Framework + +### The Line That Governs Everything + +Epictetus divides the universe into two domains with surgical precision: + +| Within Your Control | Outside Your Control | +|---|---| +| Your judgments and opinions | Other people's judgments and opinions | +| Your choices and intentions | Market conditions and macroeconomics | +| Your effort and preparation | Outcomes and results | +| Your responses to events | The events themselves | +| How you spend your attention | What others do with theirs | + +The key insight is not merely intellectual but operational. Marcus Aurelius condensed the framework into three imperatives that function as a daily protocol: *Control your perceptions. Direct your actions properly. Willingly accept what is outside your control.* That trio -- perception, action, will -- structures the entirety of Stoic practice. + +### The Seven Functions of the Mind + +Epictetus identifies seven capacities that constitute the mind's proper work, each of which falls squarely within the circle of control: + +1. **Choice** -- to do and think rightly +2. **Refusal** -- to resist temptation and distraction +3. **Yearning** -- to improve and grow +4. **Repulsion** -- to reject negativity and falsehood +5. **Preparation** -- to ready oneself for what lies ahead +6. **Purpose** -- to maintain a guiding principle +7. **Assent** -- to distinguish what is and is not within one's power + +Everything outside these seven functions is, in Epictetus's blunt assessment, "pollution." For the entrepreneur, this taxonomy provides a diagnostic: when something feels wrong, which of these seven has been neglected or corrupted? The founder who cannot say no to distracting opportunities has a refusal problem. The one who drifts between strategies has a purpose problem. The one who is blindsided by foreseeable obstacles has a preparation problem. Naming the function is the first step toward restoring it. + +### Clarity Through Intentionality + +Seneca warns that "it is not activity that disturbs people, but false conceptions of things that drive them mad." The distinction matters. Busyness is not the same as purposeful action. The founder who answers every email, attends every meeting, and chases every opportunity is not diligent -- they are directionless. The Stoic antidote is *euthymia*, which Seneca defines as "believing in yourself and trusting that you are on the right path, and not being in doubt by following the myriad footpaths of those wandering in every direction." + +Euthymia is not confidence. It is the byproduct of having done the work of clarity -- of knowing what you are building, why you are building it, and what you are willing to refuse in order to build it well. The entrepreneur who has achieved euthymia can say no without guilt, because the no is in service of a deliberate yes. + +### The Discipline of Saying No + +"How many have laid waste to your life when you weren't aware of what you were losing," Seneca writes, "how much was wasted in pointless grief, foolish joy, greedy desire, and social amusements." The Stoics treat attention as a finite and non-renewable resource. Every yes to an inessential obligation is a no to something that matters. Every hour spent monitoring news that cannot affect your actions is an hour stolen from work that can. + +This is not austerity for its own sake. It is the recognition that clarity is a precondition for effectiveness, and clarity requires the ruthless elimination of noise. + +--- + +## Prompts + +**Prompt 1 -- Control Audit:** +> List every major concern, stressor, and preoccupation I currently face as a founder of [company] at [stage]. For each, classify it as either "within my control" (my choices, efforts, judgments, responses) or "outside my control" (market, competitors, others' opinions, outcomes). For items outside my control, suggest how I can redirect that energy toward a controllable variable that influences the same domain. + +**Prompt 2 -- Intentionality Filter:** +> Review my current commitments and recurring activities as CEO of [company]: [list activities]. Apply the Stoic test of intentionality to each -- does this activity serve my core purpose, or is it habit, social obligation, or fear of missing out? Recommend what to eliminate, delegate, or reduce, and explain the clarity gained by each removal. + +**Prompt 3 -- Seven Functions Diagnostic:** +> Using Epictetus's seven functions of the mind (choice, refusal, yearning, repulsion, preparation, purpose, assent), assess my current decision-making situation: [describe situation]. Which functions am I exercising well? Which am I neglecting? Provide specific Stoic-informed recommendations for strengthening the weakest function. + +**Prompt 4 -- Euthymia Check:** +> I am experiencing doubt about my direction as founder of [company]. Apply Seneca's concept of euthymia to help me distinguish between productive strategic questioning and destructive comparison with others' paths. What is genuinely mine to reconsider, and what is noise generated by observing competitors, peers, or market commentary? + +--- + +## Use Cases + +**Seed-stage founder paralysed by competitor activity** + +A pre-revenue SaaS founder discovers that a well-funded competitor has launched a feature set nearly identical to his planned roadmap. He spirals into reactive mode -- revising timelines, second-guessing positioning, considering pivots. Applying the dichotomy of control reframes the situation: the competitor's actions, funding, and market reception are entirely outside his control. His own product quality, customer relationships, speed of iteration, and clarity of value proposition are within it. The audit reveals that 70% of his mental energy over the past week has been directed at things he cannot influence. Redirecting that energy toward controllable variables -- particularly preparation and purpose -- restores both momentum and composure. + +**Growth-stage CEO drowning in obligations** + +A Series B CEO finds herself attending twelve standing meetings per week, responding to investor updates, mentoring three direct reports, speaking at two conferences per month, and serving on an advisory board. She is exhausted and losing strategic clarity. The Stoic intentionality filter reveals that six of those commitments exist not because they serve her purpose but because she never examined whether they should. Three are habit. Two are vanity. One is guilt. By applying the discipline of refusal, she reclaims fifteen hours per week -- enough to restore the deep thinking that made her company worth funding in the first place. + +**Scale-stage executive facing regulatory uncertainty** + +The CEO of a fintech company at scale faces a pending regulatory change that could fundamentally alter the business model. The entire leadership team is consumed by anxiety about possible outcomes. The dichotomy of control provides the structural intervention: the regulation itself is outside their control, but their preparation for multiple scenarios, the quality of their legal counsel, and the adaptability of their architecture are firmly within it. The framework converts paralysing uncertainty into an actionable preparation agenda. + +--- + +## Anti-Patterns + +**1. Confusing acceptance with passivity.** The dichotomy of control does not counsel inaction. Accepting that you cannot control an outcome is not the same as declining to influence it. You cannot control whether an investor says yes, but you can control the quality of your pitch, the rigour of your preparation, and the timing of your ask. The Stoic acts fully within their sphere and then releases attachment to the result. + +**2. Using "outside my control" as an excuse.** Some founders discover the dichotomy and immediately use it to abdicate responsibility. Revenue targets missed? "Outside my control." Team attrition? "Can't control people." This is a corruption of the framework. The honest audit almost always reveals controllable factors -- your hiring practices, your management quality, your strategic choices -- that contributed to the outcome. + +**3. Applying the framework once and considering it done.** The dichotomy of control is not a one-time exercise. Epictetus recommended revisiting it at morning, midday, afternoon, and evening. The boundary between controllable and uncontrollable shifts as circumstances change. What was outside your control last quarter may be within it now, and vice versa. + +**4. Neglecting the emotional dimension.** The dichotomy is an intellectual tool, but its application is emotional. Knowing that a bad review is outside your control does not automatically prevent it from ruining your day. The framework must be paired with the emotional mastery practices of Stoic philosophy (see stoic-emotional-mastery) to be fully effective. + +**5. Drawing the line in self-serving places.** The audit is only as honest as the person conducting it. Founders sometimes classify uncomfortable controllables (their own communication failures, their hiring mistakes) as uncontrollable "team dynamics" or "market conditions." The dichotomy demands ruthless honesty about where the line actually falls, not where it would be convenient for it to fall. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Separating vision validation from market prediction | Nearly everything is uncertain; the dichotomy helps you focus on the few things you can actually test rather than speculating about the many things you cannot know | +| Validation | Controlling experiment design, not outcomes | The temptation to interpret ambiguous signals as validation is strongest here; the framework demands honesty about what the data actually says versus what you hope it says | +| Early Traction | Focusing effort on repeatable processes | As controllable variables multiply (team, product, customers), the audit becomes a prioritisation tool -- which controllables deserve the most energy? | +| Growth | Managing the expanding boundary of influence | More resources mean more things fall within your sphere of influence; the discipline shifts from acceptance to strategic allocation | +| Scale | Institutional clarity amid organisational complexity | At scale, the dichotomy must be embedded in organisational culture, not just individual practice; leadership teams need shared language for what the company can and cannot control | + +The idea-stage founder faces the starkest version of the dichotomy: almost nothing is within control except the quality of thinking and the willingness to test. This is precisely why the framework is most powerful at this stage. It strips away the fantasy of control that leads to premature scaling, over-investment in unvalidated assumptions, and the emotional devastation of early failure. + +At growth and scale, the challenge inverts. The founder now has genuine influence over a wider set of variables but risks the illusion that control extends further than it does. Regulatory environments, macroeconomic conditions, and cultural shifts remain firmly outside the circle, no matter how large the company becomes. + +At early traction, the dichotomy becomes a team discipline. The founder who has internalised the framework must now teach it -- implicitly or explicitly -- to the first ten, twenty, fifty employees. When a sales team obsesses over a prospect's internal politics (uncontrollable) rather than the quality of the demo and follow-up (controllable), the dichotomy provides the coaching language. "What can we actually do here?" is a question that, repeated often enough, reshapes how an entire organisation allocates its cognitive and emotional resources. + +--- + +## Output Template + +```markdown +# Dichotomy of Control Audit -- [Situation/Decision] + +**Date:** [Date] +**Context:** [Brief description of the situation prompting this audit] + +## Current Concerns Inventory + +| Concern | Within My Control? | Controllable Lever | Energy Currently Spent (H/M/L) | +|---------|-------------------|--------------------|---------------------------------| +| [Concern 1] | Yes / No | [If no, identify the nearest controllable variable] | [H/M/L] | +| [Concern 2] | Yes / No | [Controllable lever] | [H/M/L] | +| [Concern 3] | Yes / No | [Controllable lever] | [H/M/L] | + +## Energy Reallocation Plan + +**Percentage of energy currently directed at uncontrollables:** [X%] +**Target percentage:** [Y%] + +| Stop (Release) | Start (Redirect) | Expected Clarity Gain | +|----------------|-------------------|----------------------| +| [Uncontrollable concern] | [Controllable action] | [What becomes clearer] | + +## Seven Functions Check + +| Function | Status | Action Required | +|----------|--------|-----------------| +| Choice | [Strong / Needs attention] | [Specific action] | +| Refusal | [Strong / Needs attention] | [Specific action] | +| Yearning | [Strong / Needs attention] | [Specific action] | +| Repulsion | [Strong / Needs attention] | [Specific action] | +| Preparation | [Strong / Needs attention] | [Specific action] | +| Purpose | [Strong / Needs attention] | [Specific action] | +| Assent | [Strong / Needs attention] | [Specific action] | + +## Euthymia Statement +[One sentence defining your path and the commitment to stay on it] +``` + +--- + +## Related Skills + +- **[Stoic Emotional Mastery](stoic-emotional-mastery.md)** -- Knowing what is outside your control is step one; managing the emotional response to that knowledge is step two. +- **[Stoic Self-Awareness](stoic-self-awareness.md)** -- The dichotomy of control requires honest self-assessment to apply accurately; self-deception corrupts the audit. +- **[Stoic Unbiased Thought](stoic-unbiased-thought.md)** -- Seeing events as they are, stripped of judgment, is a prerequisite for correctly classifying them as controllable or not. +- **[Leader Resilience and Wellbeing](../leadership/leader-resilience-and-wellbeing.md)** -- Daily resilience practices are the tactical complement to the Stoic philosophical framework on control. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- Operational prioritisation tools that benefit from the Stoic clarity about what actually deserves attention. +- **[Eisenhower Matrix](../frameworks/eisenhower-matrix.md)** -- The urgent/important distinction maps naturally onto the Stoic separation of controllables from uncontrollables. +- **[Enemies of Clear Thinking](../thinking/enemies-of-clear-thinking.md)** -- The four biological defaults that distort thinking are precisely the forces that blur the line between what is and is not within your control. diff --git a/plugins/foreman/content/skills/stoic/stoic-duty-and-service.md b/plugins/foreman/content/skills/stoic/stoic-duty-and-service.md new file mode 100644 index 0000000..39e5364 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-duty-and-service.md @@ -0,0 +1,198 @@ +--- +name: "stoic-duty-and-service" +description: "Explores the Stoic conception of duty, sympatheia (universal interconnection), and service-oriented leadership as the foundation of entrepreneurial purpose. Use when founders struggle with motivation beyond profit, when leadership feels like burden rather than calling, when building a culture of accountability and mutual obligation, when navigating tensions between personal ambition and collective responsibility, or when aligning team purpose with organisational mission." +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - duty + - service + - leadership + - purpose + - accountability + - team-culture + - sympatheia + - obligation +related_skills: + - stoic-right-action + - stoic-problem-solving + - stoic-pragmatism + - purpose-driven-leadership + - delegation-and-empowerment + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +# Stoic Duty and Service + +The Stoics believed life is a debt -- and the repayment is service to others. This was not sentimentality. Marcus Aurelius, who could have spent his reign in palaces eating grapes, instead spent it on the frozen Danube frontier, adjudicating legal disputes and commanding legions against Germanic tribes. He did this not because he enjoyed it (his private journals make clear he often did not) but because it was his duty. The Greek word he used was *praxeis koinonikas apodidonai* -- to render works held in common. Epictetus, a former slave who had every reason to reject the social contract, taught duty with even greater intensity: your station is assigned; excellence lies in how you occupy it. For the entrepreneur, who has voluntarily assumed responsibility for employees, investors, customers, and a mission, the Stoic framework of duty transforms obligation from weight into architecture -- the very structure that gives the enterprise meaning. + +--- + +## The Framework + +Stoic duty operates at three concentric levels, each one expanding the founder's sense of purpose beyond the self. + +### Level 1: Sympatheia -- The Interconnected Whole + +> "Meditate often on the interconnectedness and mutual interdependence of all things in the universe." -- Marcus Aurelius, *Meditations*, 6.38 + +Sympatheia is the Stoic doctrine of universal interconnection -- the recognition that every person, event, and action is part of a single, interdependent system. This is not mysticism. It is systems thinking expressed in ancient Greek. The founder who grasps sympatheia understands that their company is not an island. It exists within a web of suppliers, customers, communities, ecosystems, and human lives. Every decision propagates outward through that web. Hiring decisions shape families. Pricing decisions shape markets. Product decisions shape behaviour. + +The practical consequence: the founder cannot claim ignorance of second-order effects. The Stoic does not say "that is not my problem." If it touches the system, it touches you. + +Modern systems thinking arrived at the same conclusion through different language. The difference is that the Stoics added a moral dimension: interconnection creates obligation. Awareness of the web is not merely strategic intelligence -- it is the foundation of duty. You cannot serve what you cannot see, and you cannot claim exemption from what you have seen. + +### Level 2: The Assigned Role + +> "Whatever anyone does or says, for my part I'm bound to the good. In the same way an emerald or gold or purple might always proclaim: 'whatever anyone does or says, I must be what I am and show my true colors.'" -- Marcus Aurelius, *Meditations*, 7.15 + +The Stoics held that every person occupies a role in the larger order. That role comes with obligations that persist regardless of mood, circumstance, or personal convenience. Marcus Aurelius governed when he would have preferred to philosophise. Seneca wrote and taught when he would have preferred retirement. Epictetus taught in exile, in poverty, with a crippled leg. + +For the founder, the assigned role is not "CEO" or "founder" -- those are titles. The role is steward. Steward of other people's livelihoods, of investor capital, of customer trust, of a mission that transcends any single person's career. As Seneca bluntly put it: "Never shirk the proper dispatch of your duty, no matter if you are freezing or hot, groggy or well-rested, vilified or praised, not even if dying or pressed by other demands." The Stoic insight: duty is not a constraint on freedom. It is the very thing that makes freedom purposeful rather than aimless. + +Marcus Aurelius's morning ritual captures this precisely. When tempted to stay in bed, he would remind himself: "I am awakening to the work of a human being. Why then am I annoyed that I am going to do what I'm made for, the very things for which I was put into this world?" + +The Israeli general Herzl Halevi reflected this same principle in modern military leadership: "People used to tell me that business administration is for the practical life and philosophy is for the spirit. Through the years I found it is exactly the opposite -- I used philosophy much more practically." The role demands the philosophy. The philosophy sustains the role. Duty and capability are mutually reinforcing, not competing demands. + +### Level 3: Service Without Scorekeeping + +> "One person, on doing well by others, immediately accounts the expected favour in return. Another is not so quick, but still considers the person a debtor and knows the favour. A third kind of person acts as if not conscious of the deed, rather like a vine producing a cluster of grapes without making further demands." -- Marcus Aurelius, *Meditations*, 5.6 + +Marcus describes three types of givers, and his preference is unmistakable. The highest form of service is unconscious of itself -- the vine that produces grapes because that is what vines do, not because it expects applause. Translated to leadership: the founder who helps a struggling employee, who gives a competitor honest advice, who invests time in a mentee with no strategic value, is practising Stoic service. + +This is not altruism in the conventional sense. The Stoics were not naive about human nature. Nor is it strategic generosity -- the calculated giving that expects reciprocity on a longer timeline. The argument is functional: the person who serves without expectation of return operates with maximum psychological freedom. They are not waiting for validation, not keeping score, not adjusting their behaviour based on whether the last favour was reciprocated. They are free to act correctly in every situation because their motivation is internal. + +### The Obligation-Choice Paradox + +A critical nuance distinguishes Stoic duty from grim compliance. Seneca wrote: "Nothing is noble if it's done unwillingly or under compulsion. Every noble deed is voluntary." The paradox: duty is obligatory, yet it must be chosen freely to have moral weight. + +The resolution lies in reframing. The founder does not *have to* lead the company through a crisis. The founder *gets to*. This is not linguistic trickery. It reflects a genuine shift in perception -- from burden to privilege, from obligation to purpose. Epictetus articulated the principle: "Bring our will into harmony with whatever happens, so that nothing happens against our will." + +The practical test: when a founder consistently experiences their duties as burdens, something is misaligned -- either the role is wrong, the mission is unclear, or the founder's relationship to service needs examination. + +### The Injustice of Inaction + +Marcus Aurelius added a dimension to duty that many entrepreneurs overlook: "Often injustice lies in what you aren't doing, not only in what you are doing." The sin of omission. The founder who sees a team member struggling and says nothing. The leader who knows the product has a defect and delays the fix. The CEO who witnesses harassment and defers to HR rather than acting. Duty is not merely the avoidance of wrong; it is the active pursuit of right. The Stoic obligation is affirmative: you must be a force for good, not merely the absence of harm. + +This principle is particularly relevant at scale, where the founder's physical distance from day-to-day operations can create moral distance. The duty does not diminish with organisational layers. It intensifies, because the leader's inaction now affects not individuals but systems. + +--- + +## Prompts + +**Prompt 1 -- Duty Mapping:** +> "Map the concentric circles of my duty as a founder. My company is [describe company, stage, team size, mission]. Starting from the innermost circle (self-governance) and moving outward (co-founders, team, customers, investors, community, industry), identify my specific obligations at each level. For each circle, distinguish between duties I am fulfilling well and duties I am neglecting. Be candid." + +**Prompt 2 -- Sympatheia Impact Analysis:** +> "Apply the Stoic principle of sympatheia to a major decision we are about to make: [describe decision]. Trace the second and third-order effects of this decision across our stakeholder web -- employees, customers, suppliers, competitors, community. Identify effects we may be ignoring because they fall outside our immediate line of sight. Where are we failing to see the interconnection?" + +**Prompt 3 -- Service Audit:** +> "Evaluate my leadership against Marcus Aurelius's three types of givers. Over the past quarter, categorise my significant acts of service to my team and stakeholders: (1) acts done with explicit expectation of return, (2) acts done with silent scorekeeping, (3) acts done like the vine -- without thought of recognition. What does the distribution reveal about my leadership? How do I shift more of my service into the third category?" + +**Prompt 4 -- Have-To vs. Get-To Reframe:** +> "Here are the five duties in my role that currently feel most burdensome: [list duties]. For each one, help me apply the Stoic reframe from 'have to' to 'get to.' This is not about forced positivity -- it is about identifying the genuine privilege and purpose embedded in each obligation. Where the reframe fails, flag the duty as potentially misaligned with my actual role." + +--- + +## Use Cases + +**The Reluctant Leader** + +A technical co-founder at an early-traction robotics startup finds herself promoted to CEO after the business-focused co-founder departs. She resents the administrative burden -- fundraising, board management, HR issues -- and fantasises about returning to pure engineering. Stoic duty reframes this not as a career detour but as a station assigned by circumstance. Marcus Aurelius did not choose to be emperor; the role was imposed by adoption and succession. Yet he governed with full commitment because the role demanded it. The technical co-founder applies the same logic: the company's twenty employees depend on her stewardship. Her engineering brilliance is necessary but insufficient; the organisation needs leadership, and she is the one positioned to provide it. She hires a COO to handle operations she is least suited for (pragmatic delegation, not abdication), while embracing her duty to set vision, make hard calls, and represent the company to investors. The resentment does not vanish overnight. But the reframe from burden to purpose provides the psychological scaffolding to endure and, eventually, to thrive. + +**The Profitable Exit vs. The Team** + +A growth-stage edtech company receives an acquisition offer that would make the two co-founders personally wealthy. The acquiring company, however, plans to relocate operations to a different country, which would result in the termination of 60% of the current team. The co-founders face a direct conflict between personal interest and duty to their employees. Stoic sympatheia demands that they see the interconnection: these employees relocated for the company, recommended friends for hire, invested their careers in the mission. Justice -- the cardinal virtue -- requires that the co-founders at minimum negotiate retention terms, transition support, and severance. Some founders in this position have declined acquisitions entirely, judging that the duty to their team outweighed the personal windfall. Others have negotiated terms that honoured both interests. The Stoic framework does not prescribe a single answer. It insists that the duty be weighed, not ignored. + +**The Investor Pressure to Compromise** + +A scale-stage climate-tech company's lead investor pressures the founder to abandon the company's open-source commitments in favour of a proprietary model that would accelerate revenue. The founder recognises the tension between duty to shareholders (fiduciary obligation) and duty to the broader community (the open-source ecosystem that contributed to the company's success). Marcus Aurelius's concept of sympatheia illuminates the web: the open-source community provided talent, feedback, and credibility. Abandoning it is not merely a strategic pivot; it is a severance of reciprocal obligation. The founder presents the board with a hybrid model that preserves core open-source commitments while monetising enterprise features. The duty is honoured on both fronts -- not perfectly, but honestly. + +--- + +## Anti-Patterns + +**Martyrdom as Identity.** Some founders wear their sacrifices like medals, broadcasting how much they have given up for the company. This is Marcus's first type of giver -- the one who "immediately accounts the expected favour in return." Stoic duty is quiet. The moment service becomes a performance, it has ceased to be service and become marketing for the founder's ego. + +**Duty Without Boundaries.** The Stoics did not advocate self-destruction. Marcus Aurelius insisted on the distinction between duty to others and duty to oneself. A founder who works 100-hour weeks, neglects health, and destroys personal relationships in the name of "duty" has confused obligation with self-harm. Seneca's counsel is direct: "Philosophy calls for simple living, but not for penance." Sustainable duty requires sustainable leaders. + +**Conflating Duty With Control.** Duty to one's team does not mean making every decision for them. Marcus observed that "the ruling reason in each of us is master of its own affairs." The founder's duty is to create conditions for others to fulfil their own duties -- to hire well, set clear expectations, provide resources, and then trust the system. Micromanagement is not service; it is the failure to trust others with their own assigned roles. + +**Selective Sympatheia.** Recognising interconnection only when it is convenient -- caring about second-order effects on customers but ignoring second-order effects on suppliers; valuing team wellbeing but dismissing community impact -- is not sympatheia. It is marketing dressed as philosophy. The Stoic web of obligation does not have opt-out clauses. + +**Obligating Others to Your Standard.** The founder who has internalised Stoic duty sometimes falls into the trap of expecting identical commitment from employees. Marcus's meditations are self-directed. He does not demand that his generals read philosophy. Musonius Rufus acknowledged that "some people are sharp and others dull; some are raised in a better environment, others in worse." The duty to understand others' circumstances is itself part of the Stoic obligation. + +**Duty as Guilt Instrument.** Reminding employees of what the company has done for them -- opportunities provided, salaries paid, growth enabled -- in order to extract extra commitment is not Stoic duty. It is debt creation masquerading as generosity. The vine, in Marcus's metaphor, does not invoice the person who eats the grape. Service given with an implicit ledger is not service at all. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Clarifying the purpose behind the venture -- is it service or self-aggrandisement? | Duty at the idea stage is primarily to honesty: does this idea serve a genuine need, or is it a vehicle for personal ambition dressed as mission? | +| Validation | Duty to the early adopters who are investing their time and trust | The first customers are partners, not transactions. The founder's duty is to honour their feedback with genuine responsiveness, not selective listening | +| Early Traction | Duty to the first employees who took the risk of joining | These people left stable employment for a promise. The founder's obligation is to steward their careers, not merely extract their labour | +| Growth | Balancing duties to an expanding stakeholder web -- investors, larger teams, communities | The hardest transition: duty was personal and direct at earlier stages; now it must be systematised. The founder cannot personally fulfil every obligation; the culture must carry it | +| Scale | Institutional duty -- ensuring the company's systems and culture perpetuate service beyond the founder | The ultimate Stoic test: can the organisation embody duty without the founder's daily presence? Marcus Aurelius knew he would die; he governed to create systems, not dependencies | + +The arc across stages traces a movement from personal duty to institutional duty. The founder's obligation evolves from doing the right thing personally to building an organisation that does the right thing systemically. + +Seneca captured the ultimate aspiration: "The person who has practiced philosophy as a cure for the self becomes great of soul, filled with confidence, invincible -- and greater as you draw near." The founder whose sense of duty has deepened through each stage does not become weaker under institutional pressure. The duty itself becomes a source of strength -- not because it is easy, but because it provides a clarity of purpose that no external incentive can replicate. + +The irony is worth noting: the founder who embraces duty freely, as a voluntary commitment rather than an imposed burden, discovers a form of joy that the purely profit-motivated founder never encounters. Seneca called it "real joy" -- "a serious thing" that "will never run dry once you've laid claim to its source." + +--- + +## Output Template + +```markdown +# Duty and Service Assessment + +## Stakeholder Duty Map +| Circle | Stakeholder | Specific Duty | Current Fulfilment (1-5) | Gap | +|--------|-------------|---------------|--------------------------|-----| +| Inner | Self-governance | [Duty] | [Score] | [Gap] | +| Core | Co-founders / Partners | [Duty] | [Score] | [Gap] | +| Team | Employees | [Duty] | [Score] | [Gap] | +| Market | Customers | [Duty] | [Score] | [Gap] | +| Capital | Investors | [Duty] | [Score] | [Gap] | +| Outer | Community / Industry | [Duty] | [Score] | [Gap] | + +## Sympatheia Analysis +- **Decision under review:** [Describe] +- **First-order effects:** [Direct impacts] +- **Second-order effects:** [Indirect impacts on adjacent stakeholders] +- **Third-order effects:** [Systemic or long-term impacts] +- **Obligations revealed:** [Duties illuminated by this analysis] + +## Service Quality Check +- **Type 1 acts (with explicit expectation):** [Count and examples] +- **Type 2 acts (silent scorekeeping):** [Count and examples] +- **Type 3 acts (the vine):** [Count and examples] +- **Shift plan:** [How to move toward Type 3] + +## Reframe Exercise +| Duty That Feels Burdensome | Reframe: The Privilege | Aligned? (Y/N) | +|---------------------------|----------------------|-----------------| +| [Duty] | [Reframe] | [Y/N] | +| [Duty] | [Reframe] | [Y/N] | +``` + +--- + +## Related Skills + +- **[Stoic Right Action](stoic-right-action.md)** -- Duty without ethical guidance is mere compliance; right action gives duty its moral content. +- **[Stoic Problem Solving](stoic-problem-solving.md)** -- When obstacles impede the fulfilment of duty, the Stoic method converts them into instruments of service. +- **[Stoic Pragmatism](stoic-pragmatism.md)** -- The pragmatic execution layer that prevents duty from becoming abstract aspiration. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- The organisational expression of Stoic duty, translating personal obligation into collective mission. +- **[Humility and Power](../leadership/humility-and-power.md)** -- The paradox of leading through service rather than authority, directly aligned with Marcus Aurelius's practice of power. +- **[Team Culture and Dynamics](../leadership/team-culture-and-dynamics.md)** -- Building a team culture where duty is shared rather than concentrated in a single individual. diff --git a/plugins/foreman/content/skills/stoic/stoic-emotional-mastery.md b/plugins/foreman/content/skills/stoic/stoic-emotional-mastery.md new file mode 100644 index 0000000..758395a --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-emotional-mastery.md @@ -0,0 +1,199 @@ +--- +name: "stoic-emotional-mastery" +description: "Applies the Stoic approach to emotions -- not suppression but reframing -- to entrepreneurial leadership. Covers the distinction between first impressions and considered judgments, Seneca's anger management method, the practice of responding rather than reacting, and the Stoic treatment of fear, desire, pleasure, and grief. Use when anger is clouding judgment, fear is driving decisions, desire is distorting priorities, struggling to separate emotional reactions from rational assessment, or seeking a philosophical alternative to conventional emotional intelligence models." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - emotions + - anger-management + - fear + - desire + - self-control + - reframing + - seneca + - marcus-aurelius +related_skills: + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-unbiased-thought + - emotional-intelligence + - emotional-courage + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +# Stoic Emotional Mastery + +Emotions are like volcanoes -- the Stoic goal is not to extinguish them but to channel their energy. This distinction is routinely misunderstood. Popular culture has reduced "stoic" to a synonym for "emotionless," which would have baffled the actual Stoics, who wrote with more passion, honesty, and emotional granularity than most modern self-help authors manage. Seneca's letters vibrate with feeling. Marcus Aurelius's *Meditations* are the private journal of a man wrestling nightly with frustration, grief, and exhaustion. Epictetus practically shouts at his students. The Stoic project is not the elimination of emotion but the refusal to be governed by it -- a distinction that separates competent leaders from reactive ones. + +--- + +## The Framework + +### First Impressions vs. Considered Judgments + +The core Stoic insight about emotions is deceptively simple: there is a gap between the initial impression an event creates and the judgment you form about it. The impression is involuntary -- your pulse quickens when you receive a hostile email, your stomach drops when you learn a key employee is leaving. The Stoics called this the *propatheiai*, the "pre-emotion," and they considered it morally neutral. You cannot prevent it any more than you can prevent a loud noise from startling you. + +What you can control is the next step: whether you *assent* to that impression. "It isn't events themselves that disturb people," Epictetus writes, "but only their judgments about them." The hostile email is a fact. The judgment that it is an outrage, a betrayal, or a catastrophe is yours to make or withhold. + +### The Stoic Emotion Protocol + +The Stoics developed a practical sequence for handling emotional triggers: + +**Step 1 -- Pause.** Marcus Aurelius instructs himself to "say to the impression, hold up a bit and let me see who you are and where you are from." The pause is not hesitation. It is the deliberate insertion of reason between stimulus and response. + +**Step 2 -- Classify.** Is this impression about something within your control or outside it? If outside, the emotional charge is misplaced energy. If within, what specific action does it call for? + +**Step 3 -- Strip the judgment.** Remove the value label. Not "this customer abandoned us" but "this customer chose a different supplier." Not "the board is attacking me" but "the board is asking difficult questions." + +**Step 4 -- Respond from principle.** Act according to what your rational mind, untainted by the initial surge, determines is the right course. + +### Anger: The Stoic's Primary Adversary + +Seneca devoted an entire treatise to anger -- *De Ira* -- making it clear that of all emotions, this one most urgently demanded mastery. His reasoning was practical, not moralistic: "There is no more stupefying thing than anger, nothing more bent on its own strength. If successful, none more arrogant, if foiled, none more insane." + +Anger feels like power but functions as impairment. The angry negotiator overpays. The angry CEO fires the wrong person. The angry founder sends the email that costs them the partnership. Seneca's prescription is not to suppress the feeling but to delay the action. "The greatest remedy for anger is delay," he writes. Time is the solvent in which anger dissolves. + +For entrepreneurs, this translates to a concrete policy: never make a consequential decision, send a significant communication, or confront a team member while angry. Abraham Lincoln wrote furious letters to generals and subordinates and then folded them into his desk drawer, unsent. The Stoics would have approved. + +### Fear: The Self-Fulfilling Prophecy + +"Many are harmed by fear itself," Seneca warns, "and many may have come to their fate while dreading fate." Fear in an entrepreneurial context operates as a particularly insidious distortion: the founder afraid of losing a client overservices them into unprofitability. The CEO afraid of being perceived as weak avoids all vulnerability, destroying the trust that genuine leadership requires. The leader convinced of betrayal acts pre-emptively, becoming the very source of the disloyalty they feared. + +The Stoic treatment of fear centres on two practices. First, *premeditatio malorum* -- the deliberate, calm contemplation of worst-case scenarios. By imagining the feared outcome in advance, its emotional charge is partially discharged. Second, the dichotomy of control: if the feared outcome is outside your control, fear is futile; if it is within your control, action -- not fear -- is the appropriate response. + +### Desire and Pleasure: The Quiet Corruptors + +Anger and fear receive the most attention, but the Stoics reserved particular wariness for desire. "It is quite impossible to unite happiness with a yearning for what we don't have," Epictetus observes. The entrepreneur who cannot be content with the current state of the business -- who is perpetually fixated on the next milestone, the next round, the next acquisition -- is structurally incapable of the clarity that good decision-making requires. + +Pleasure presents the complementary hazard. Epictetus recommends a practice of connecting indulgence with its actual consequences: "Bring to mind both times, first when you have enjoyed the pleasure and later when you will regret it." This is not puritanism. It is the deliberate counterbalancing of a neural architecture that overweights immediate gratification. + +### The Indifferent Middle Ground + +Seneca, one of the wealthiest men in Rome, was not an ascetic. The Stoics distinguish between *preferred indifferents* (health, wealth, reputation -- things it is reasonable to pursue) and *dispreferred indifferents* (illness, poverty, obscurity -- things it is reasonable to avoid). The critical word is "indifferent." These things are neither good nor evil in themselves. Only virtue (wisdom, courage, justice, temperance) qualifies as genuinely good; only vice qualifies as genuinely bad. Everything else is raw material for the exercise of virtue. + +This framework liberates the entrepreneur from the emotional roller coaster that accompanies external outcomes. A lost deal is a dispreferred indifferent -- regrettable but not a moral catastrophe. A successful launch is a preferred indifferent -- welcome but not a reason to abandon the discipline that produced it. + +--- + +## Prompts + +**Prompt 1 -- Emotional Trigger Audit:** +> Identify the top 5 emotional triggers I currently face as founder/CEO of [company] -- situations that reliably provoke anger, fear, anxiety, or impulsive desire. For each trigger, apply the Stoic four-step protocol: (1) define the initial impression, (2) classify as within/outside my control, (3) strip the value judgment to reveal the neutral event, (4) recommend a principle-based response. + +**Prompt 2 -- Anger Delay Protocol:** +> I am currently angry about [situation]. Apply Seneca's anger management framework: help me identify the judgment driving this anger, test whether that judgment is accurate or distorted, enumerate the probable consequences of acting on the anger now versus waiting 24 hours, and draft a measured response I could send or take after the delay period. + +**Prompt 3 -- Fear Inversion:** +> I am afraid that [feared outcome] will happen to my business. Conduct a Stoic premeditatio malorum: describe the worst-case scenario in concrete, non-catastrophic language. Then classify each element of the feared outcome as controllable or uncontrollable. For the controllable elements, propose preventive actions. For the uncontrollable elements, describe what a rational acceptance of the risk would look like. + +**Prompt 4 -- Desire Calibration:** +> I am intensely pursuing [goal/acquisition/milestone]. Apply the Stoic framework of preferred indifferents to assess whether this desire is serving or enslaving me. What would change if I reclassified this from "essential" to "preferred but not necessary"? How would my decision-making improve if I could maintain effort without attachment to the specific outcome? + +--- + +## Use Cases + +**Early-traction founder receiving first harsh criticism** + +A consumer app founder at early traction receives a scathing product review from a prominent tech blogger. Her immediate reaction -- fury, followed by the urge to respond publicly -- is a textbook first impression demanding assent. Applying the Stoic protocol, she pauses (Step 1), classifies the reviewer's opinion as outside her control while her product roadmap remains within it (Step 2), strips the judgment by reframing "attack on my work" as "one user's public feedback" (Step 3), and responds from principle by extracting the three valid criticisms buried in the polemic and adding them to the backlog (Step 4). The blogger never gets a reply. The product gets better. + +**Growth-stage CEO managing fear of down-round** + +A SaaS CEO at growth stage faces deteriorating market conditions and the real possibility of a down-round. Fear begins to distort his decisions: he considers aggressive cost-cutting that would gut the engineering team, entertains acquisition offers he would never have considered six months ago, and loses sleep constructing catastrophic scenarios. The Stoic premeditatio malorum converts vague dread into a concrete contingency plan. The fear inversion reveals that most of his worst-case scenarios, examined calmly, are survivable. The dichotomy of control redirects energy toward the levers he can actually pull -- runway extension, selective hiring freezes, customer retention -- and releases the ones he cannot, such as broader market sentiment and competitor fundraising. + +**Scale-stage executive addicted to growth metrics** + +A scale-stage executive has tied her identity and sense of self-worth to monthly growth numbers. A single month of slower growth triggers a disproportionate emotional response -- anxiety, irritability, and the compulsive checking of dashboards. The Stoic framework of preferred indifferents provides the intervention. Growth is a preferred indifferent, not a moral good. Her response to a slow month -- the equanimity, strategic clarity, and composure with which she analyses the data and adjusts -- is where actual virtue resides. The reframing doesn't reduce her ambition. It protects her judgment from the distortion that unexamined desire produces. + +--- + +## Anti-Patterns + +**1. Equating Stoic composure with emotional suppression.** The single most common misapplication. Stoicism does not ask you to feel nothing; it asks you to not be controlled by what you feel. A founder who suppresses grief, frustration, or disappointment without processing it is not practising Stoicism -- they are building a pressure vessel. Marcus Aurelius wrote his private journal precisely because he needed a place to express and examine his emotions. + +**2. Using the framework to invalidate others' emotions.** Telling a distraught team member that "events are neutral, only your judgment makes them bad" is not leadership. It is philosophical malpractice. The Stoic framework is for self-governance, not for dismissing the legitimate emotional responses of others. Marcus Aurelius explicitly counsels compassion toward those who have not yet developed these capacities. + +**3. Treating anger as always irrational.** Some situations warrant moral outrage -- fraud, exploitation, injustice. The Stoic question is not "should I feel anger?" but "is my anger producing useful action or merely consuming me?" Directed anger that catalyses a principled response is different from reactive anger that destroys relationships and judgment. + +**4. Performing equanimity without the underlying work.** The appearance of calm is not the same as the achievement of it. Founders who project unflappability while internally spiralling are not Stoic; they are exhausted actors. The framework requires genuine cognitive reappraisal, not theatrical composure. + +**5. Ignoring the body.** The Stoics acknowledged that the body affects the mind. Fatigue, hunger, and illness lower the threshold at which impressions overwhelm judgment. Seneca would not have been impressed by the CEO who claims Stoic emotional mastery while sleeping four hours a night. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Managing fear of failure and rejection | Emotional reactions are most raw here; the gap between impression and judgment is smallest because everything feels existential | +| Validation | Separating personal identity from experimental outcomes | The founder must learn that a failed experiment is data, not a personal verdict -- the Stoic reframe of neutral events is essential | +| Early Traction | Handling criticism, competition, and first real setbacks | The emotional palette expands: anger at copycats, fear of losing early customers, desire for press coverage all need the four-step protocol | +| Growth | Preventing success from corrupting judgment | The pleasures of growth -- flattery, status, options -- are the quiet corruptors the Stoics warned about; indifference to preferred outcomes becomes critical | +| Scale | Institutional emotional regulation | The leader's emotional patterns infect the organisation; Stoic composure at scale is a cultural responsibility, not just a personal practice | + +At the idea stage, almost every piece of feedback carries outsized emotional weight because the founder and the company are nearly indistinguishable. A rejection of the idea feels like a rejection of the self. The Stoic separation of impression from judgment is the foundational skill that prevents early-stage emotional volatility from sabotaging the venture before it begins. + +At growth and scale, the emotional challenge shifts from personal volatility to systemic amplification. A CEO who reacts emotionally in a leadership meeting doesn't just make a bad decision -- they set the emotional tone for fifty, five hundred, or five thousand people. Stoic emotional mastery becomes an organisational competency, not merely a personal one. + +--- + +## Output Template + +```markdown +# Emotional Mastery Assessment -- [Situation] + +**Date:** [Date] +**Context:** [Brief description of the emotional challenge] + +## Trigger Analysis + +| Trigger | First Impression | Judgment Attached | Neutral Reframe | +|---------|-----------------|-------------------|-----------------| +| [Event] | [Involuntary reaction] | [Value label applied] | [Event stated without judgment] | + +## Control Classification +- **Within my control:** [List specific controllable elements] +- **Outside my control:** [List uncontrollable elements] +- **Energy reallocation:** [From uncontrollable → controllable] + +## Emotion-Specific Protocol + +### If Anger: +- **Delay period observed:** [Yes/No -- minimum 24 hours for consequential decisions] +- **Judgment accuracy test:** [Is the belief driving the anger actually true?] +- **Probable consequences of acting now:** [List] +- **Measured response (post-delay):** [Draft] + +### If Fear: +- **Worst case (concrete terms):** [Describe without catastrophising] +- **Survivability assessment:** [Is this actually unsurvivable?] +- **Preventive actions available:** [List controllable mitigants] + +### If Desire: +- **Preferred indifferent classification:** [Is this genuinely necessary or merely preferred?] +- **Decision quality with/without attachment:** [Compare] + +## Principle-Based Response +[The action or communication you will take, grounded in rational assessment rather than emotional surge] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](stoic-control-and-clarity.md)** -- The dichotomy of control is the structural foundation upon which emotional mastery is built; without it, reframing has no anchor. +- **[Stoic Self-Awareness](stoic-self-awareness.md)** -- Recognising your emotional patterns is a prerequisite for interrupting them; the evening review practice surfaces recurring triggers. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's EQ model manages emotions within a social framework; Stoic emotional mastery operates at the perceptual level, reframing the impressions that generate emotions. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's System 1/System 2 distinction maps closely to the Stoic separation of first impressions from considered judgments. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- Stoic composure provides the philosophical foundation; emotional courage addresses the willingness to act on difficult truths. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Practical protocols for high-stakes decisions that benefit from the Stoic practice of pausing before assenting to impressions. diff --git a/plugins/foreman/content/skills/stoic/stoic-fortitude-and-resilience.md b/plugins/foreman/content/skills/stoic/stoic-fortitude-and-resilience.md new file mode 100644 index 0000000..f5229c6 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-fortitude-and-resilience.md @@ -0,0 +1,200 @@ +--- +name: "stoic-fortitude-and-resilience" +description: "Provides the philosophical foundations of inner strength, endurance, and anti-fragility drawn from Stoic thought, teaching entrepreneurs why hardship strengthens character, how to prepare mentally for adversity through voluntary discomfort, and why patience and perseverance outperform luck as long-term competitive assets. Use when facing sustained business adversity, preparing mentally for a high-stakes launch or fundraise, building psychological toughness before a difficult transition, questioning whether a setback signals failure or formation, or seeking the philosophical basis for resilience practices covered in leader-resilience-and-wellbeing." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - fortitude + - resilience + - adversity + - perseverance + - anti-fragility + - voluntary-discomfort + - inner-strength + - endurance + - stoic + - mental-preparation +related_skills: + - leader-resilience-and-wellbeing + - stoic-acceptance-amor-fati + - stoic-mortality-and-perspective + - growth-mindset + - emotional-courage +author: "Fatih Guner" +--- + +# Stoic Fortitude and Resilience + +IRON. The word recurs across Stoic literature with a frequency that borders on obsession, and the reason is not metaphorical vanity. Iron is shaped in fire, hardened by hammering, made useful through processes that would destroy lesser materials. Comfort, as Seneca observed with characteristic bluntness, has never hardened anything. Cato the Younger walked Rome barefoot and bareheaded in rain and heat -- not because he lacked the means for sandals and a parasol, but because he was training his soul against the day when fortune would strip him of everything except his character. That day came, as it always does. Cato was ready. The question for the entrepreneur is not whether adversity will arrive. It is whether the founder will meet it as raw ore or as tempered steel. + +> "I judge you unfortunate because you have never lived through misfortune. You have passed through life without an opponent -- no one can ever know what you are capable of, not even you." -- Seneca, *On Providence* + +--- + +## The Framework + +Stoic fortitude is not the grim endurance of someone who merely survives. It is a trained capacity to metabolise difficulty into strength -- what Nassim Taleb would later call anti-fragility, but which the Stoics articulated two millennia earlier without the neologism. The framework rests on four pillars. + +### Pillar 1: The Inner Citadel + +Marcus Aurelius returned again and again to the concept of an impenetrable inner fortress -- a domain of reasoned choice that no external force can breach. "The mind freed from passions is an impenetrable fortress -- a person has no more secure place of refuge for all time." The fortress falls only through internal betrayal: when fear, greed, or despair open the gates from within. + +For entrepreneurs, the Inner Citadel is the capacity to separate external events (a lost client, a failed fundraise, a competitor's surprise move) from internal judgement. The event is neutral. The interpretation -- catastrophe or curriculum -- is a choice. + +### Pillar 2: Voluntary Discomfort as Training + +Seneca's prescription is as practical as it is counterintuitive: "Take part of a week in which you have only the most meager and cheap food, dress scantly in shabby clothes, and ask yourself if this is really the worst that you feared." Soldiers drill in peacetime. Athletes train in conditions worse than competition. The Stoics applied the same logic to psychological endurance. + +Voluntary discomfort operates through three mechanisms: + +| Mechanism | Stoic Source | Entrepreneurial Application | +|-----------|-------------|---------------------------| +| **Desensitisation** | Seneca's cold-bath exercises | Practising with less capital, fewer resources, smaller teams reduces the terror of scarcity | +| **Calibration** | Epictetus on discovering true needs | Distinguishing genuine needs from habituated wants clarifies which expenses and dependencies are structural | +| **Confidence** | Seneca on the poverty of exile | Having survived voluntary deprivation, the entrepreneur knows that involuntary deprivation is survivable | + +### Pillar 3: The Sparring Partner Reframe + +> "Difficulties show a person's character. So when a challenge confronts you, remember that God is matching you with a younger sparring partner, as would a physical trainer." -- Epictetus, *Discourses* + +Every setback is a training bout. The rejected pitch, the churning customers, the co-founder conflict -- these are not evidence that the universe is hostile. They are the resistance that builds capacity. Marcus Aurelius framed life itself as wrestling rather than dancing: "an artful life requires being prepared to meet and withstand sudden and unexpected attacks." Dancers perform choreography. Wrestlers respond to what the opponent does. Entrepreneurship is wrestling. + +### Pillar 4: Patience as Strategic Asset + +> "Anyone can get lucky. Not everyone can persevere." -- Seneca, *On Providence* + +The Stoics drew a sharp distinction between fortune and fortitude. Fortune is a loan; fortitude is equity. The lucky entrepreneur who has never been tested does not know whether the business model or the market cycle deserves the credit. The entrepreneur who has persevered through adversity holds the rarer and more durable asset: proof that they can endure. + +Perseverance, however, is not stubbornness. Marcus explicitly warned against mistaking an iron will for an adaptable one: "To change your mind and to follow someone's correction are consistent with a free will." The goal is not to persist blindly but to persist intelligently -- adjusting tactics while holding strategic conviction. + +### The Stockdale Paradox + +Captain James Stockdale, shot down over Vietnam and imprisoned for seven and a half years, brought Epictetus into the most brutal laboratory imaginable. He later told Jim Collins that the prisoners who did not survive were, counterintuitively, the optimists -- "the ones who said, 'We're going to be out by Christmas.' And Christmas would come, and Christmas would go. And they died of a broken heart." Stockdale himself held two truths simultaneously: absolute faith that he would prevail in the end AND absolute confrontation with the brutal facts of his current situation. + +This paradox -- hope anchored in agency, not in timeline -- is the Stoic position distilled for entrepreneurs. The founder who says "We'll close the round by Q3" is making a prediction about things outside their control. The founder who says "We will do everything within our power, and we will adapt to whatever comes" is practising Stoic fortitude. The first disposition is brittle. The second is unbreakable. + +### Fear as the Real Enemy + +> "There is no reason to live and no limit to our miseries if we let our fears predominate." -- Seneca, *Moral Letters* + +FDR's "nothing to fear but fear itself" drew from a wellspring the Stoics had tapped centuries earlier. Fear does not protect; it pre-empts. The entrepreneur who avoids a difficult conversation out of fear allows the underlying problem to metastasize. The founder who refuses to look at deteriorating metrics out of fear forfeits the window in which intervention is possible. Stoic fortitude is, at its core, the disciplined refusal to let fear -- rather than reason -- dictate action. + +--- + +## Prompts + +**Prompt 1 -- Inner Citadel Audit:** +> I am facing a significant external challenge: [describe situation -- e.g., failed fundraise, lost key customer, co-founder departure]. Using the Stoic concept of the Inner Citadel, help me separate what is genuinely outside my control from what remains within my reasoned choice. For each element outside my control, reframe the catastrophic interpretation into a neutral or instructive one. For each element within my control, identify the most effective action I can take this week. + +**Prompt 2 -- Voluntary Discomfort Protocol:** +> Design a 30-day voluntary discomfort programme for me as an entrepreneur at [stage]. The goal is to reduce my psychological dependence on [comfort/resource -- e.g., a large team, premium office, high salary, constant validation]. For each week, prescribe a specific deprivation exercise, explain the Stoic rationale behind it, and describe the entrepreneurial capability it builds. Make the programme progressively harder. + +**Prompt 3 -- Adversity Reframe:** +> I have experienced the following setback: [describe]. My current emotional response is [describe -- e.g., demoralised, angry, fearful]. Apply the Stoic sparring-partner reframe: What capability is this adversity training me to develop? What would Seneca, Epictetus, or Marcus Aurelius say about this specific situation? What is the most strategically intelligent response, as opposed to the most emotionally satisfying one? + +**Prompt 4 -- Perseverance vs. Stubbornness Diagnostic:** +> I have been pursuing [goal/strategy] for [time period] despite ongoing resistance and setbacks. Help me distinguish between Stoic perseverance (intelligent persistence aligned with what I control) and mere stubbornness (refusing to adapt despite clear evidence). What signals would indicate that I should hold the course? What signals would indicate that I should change direction while maintaining the larger mission? + +--- + +## Use Cases + +**Validation-Stage Climate-Tech Founder After Third Rejected Pilot** + +A founder building carbon-capture technology for industrial facilities has been rejected by three potential pilot customers in succession. Each rejection cited a different reason -- budget timing, regulatory uncertainty, internal politics -- but the cumulative effect is demoralising. Applying the Stoic sparring-partner reframe, the founder catalogues what each rejection taught: the first revealed a pricing objection the pitch did not address, the second exposed a procurement cycle the go-to-market plan ignored, the third identified a champion-building step the sales process lacked. None of these insights were available without the rejections. Seneca's observation applies directly: the founder now knows capabilities that remained invisible during the comfortable theorising of the idea stage. + +**Growth-Stage SaaS Founder Preparing for Economic Downturn** + +A SaaS company with 200 employees and comfortable margins sees early indicators of a market contraction. Rather than waiting for the downturn to force austerity, the CEO applies Seneca's voluntary-discomfort principle at the organisational level: a 90-day "wartime readiness" exercise in which each department identifies how it would operate at 70% of current budget. The exercise surfaces redundant tooling, over-specified vendor contracts, and processes that consume resources without proportional output. When the downturn arrives six months later, the company has already internalised the leaner operating model -- not as panic but as preparedness. The team's confidence, paradoxically, is higher during the downturn than before the exercise. + +**Early-Traction Founder Managing Emotional Volatility** + +A first-time founder at early traction finds herself oscillating between euphoria after a good sales week and despair after a bad one. The emotional volatility is affecting her decision-making and her team's confidence. Using the Inner Citadel framework, she maps which elements of weekly revenue are inside her control (activity volume, pitch quality, pipeline management) and which are outside it (individual prospect timing, macroeconomic sentiment, competitor moves). She then constructs a personal dashboard that tracks only the controllable inputs. Within a month, the emotional swings diminish -- not because the outcomes changed but because her attention shifted to what Epictetus called "the only things that are truly ours." + +--- + +## Anti-Patterns + +1. **Glorifying suffering for its own sake.** The Stoics practised voluntary discomfort as training, not as masochism. The founder who sleeps on the office floor, works hundred-hour weeks, and neglects health is not practising Stoic fortitude -- they are practising self-destruction with a philosophical veneer. Seneca himself counselled rest and relaxation as essential to sustained performance. The goal is resilience, not ruin. + +2. **Confusing emotional suppression with inner strength.** The Inner Citadel is not a wall behind which one hides from emotion. Marcus Aurelius grieved. Seneca feared. Epictetus acknowledged pain. Stoic fortitude means processing adversity through reason, not refusing to feel it. The founder who insists they are "fine" after a devastating setback is not demonstrating fortitude. They are delaying a collapse. + +3. **Using Stoic endurance to avoid necessary pivots.** Perseverance is a virtue when applied to a sound strategy against temporary resistance. It becomes a vice when applied to a failing strategy against permanent market realities. "Flexibility is its own kind of strength," Marcus wrote. The Stoic entrepreneur endures hardship on the path -- but changes the path when reason demands it. + +4. **Weaponising Stoicism against others.** Telling a struggling employee or co-founder to "be more Stoic" is not philosophy; it is dismissal dressed in a toga. Stoic fortitude is a personal discipline, not a performance standard to impose on others. The leader's job is to build resilience in the organisation through structure and support, not through philosophical lecturing. + +5. **Treating the absence of adversity as failure.** Some founders, having absorbed the "what doesn't kill you makes you stronger" narrative, unconsciously seek or manufacture crises. The Stoics valued tranquillity. Cato trained in hardship so that he could function during hardship -- not so that he could pursue it as a lifestyle. + +6. **Mistaking Stoic philosophy for a personality type.** Fortitude is a practice, not a disposition. Some people appear naturally tough; some appear naturally sensitive. Stoic training is available to both. The naturally tough founder who has never examined their resilience philosophically is no more Stoic than the sensitive founder who has done the inner work. Resilience is built, not inherited. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Building tolerance for uncertainty | The idea stage is almost entirely composed of unknowns. Stoic fortitude here means training oneself to operate without the validation, structure, or income that previous employment provided. Voluntary discomfort: practise living on minimal runway before you have to. | +| Validation | Metabolising rejection | Validation requires subjecting the idea to market reality, which means hearing "no" repeatedly. The sparring-partner reframe converts each rejection from a verdict into data. The founder who emerges from validation with fortitude intact has the most important signal of all: evidence of their own endurance. | +| Early Traction | Managing emotional volatility | Revenue creates hope, and hope creates vulnerability to disappointment. The Inner Citadel discipline -- separating controllable inputs from uncontrollable outcomes -- is most critical here. Fortitude at this stage is the ability to maintain strategic clarity amid operational noise. | +| Growth | Sustaining conviction through scaling pain | Growth brings new categories of adversity: team conflicts, operational breakdowns, competitive pressure, board dynamics. The Stoic framework shifts from personal endurance to institutional resilience. The question becomes: how does the founder build an organisation that metabolises adversity, not just a personality that tolerates it? | +| Scale | Preparing for reversal at the peak | Seneca's warning about fortune applies most urgently at scale: "No one is crushed by Fortune, unless they are first deceived by her." The scaled company faces its greatest risk of complacency. Stoic fortitude at this stage is the discipline to prepare for downturn during prosperity -- the organisational equivalent of Cato walking barefoot through Rome. | + +--- + +## Output Template + +```markdown +# Fortitude and Resilience Assessment + +**Founder/Leader:** [Name] +**Company Stage:** [Stage] +**Date:** [Date] +**Current Adversity:** [Brief description of the challenge] + +## Fear Inventory +| Fear | Rational Basis? | Stoic Response | Action It Blocks | +|------|----------------|---------------|-----------------| +| [Fear 1] | Yes / Partially / No | [Reasoned assessment] | [What you would do without this fear] | +| [Fear 2] | Yes / Partially / No | [Reasoned assessment] | [What you would do without this fear] | + +## Inner Citadel Inventory + +| Element | Inside My Control? | Current Response | Stoic Response | +|---------|-------------------|-----------------|---------------| +| [Element 1] | Yes / No | [What I am doing] | [What reason dictates] | +| [Element 2] | Yes / No | [What I am doing] | [What reason dictates] | +| [Element 3] | Yes / No | [What I am doing] | [What reason dictates] | + +## Sparring Partner Reframe +- **What is this adversity training me to do?** [Answer] +- **What capability will I have after this that I lacked before?** [Answer] +- **What would I advise a founder facing this same challenge?** [Answer] + +## Voluntary Discomfort Commitments (Next 30 Days) +1. [Specific practice] -- Rationale: [Why this builds resilience] +2. [Specific practice] -- Rationale: [Why this builds resilience] +3. [Specific practice] -- Rationale: [Why this builds resilience] + +## Perseverance Check +- **Is my persistence aligned with what I control?** [Yes/No + evidence] +- **Am I adapting tactics while holding strategic conviction?** [Yes/No + evidence] +- **What signal would tell me to change course?** [Specific, observable signal] +``` + +--- + +## Related Skills + +- **[Leader Resilience and Wellbeing](../leadership/leader-resilience-and-wellbeing.md)** -- Covers the daily, practical dimensions of resilience: sleep, stress management, mindfulness, recovery practices. This skill provides the philosophical foundation; that skill provides the operational toolkit. +- **[Stoic Acceptance and Amor Fati](stoic-acceptance-amor-fati.md)** -- Fortitude prepares you to endure what happens; amor fati teaches you to love it. The two disciplines form a progression: first survive, then transcend. +- **[Growth Mindset](../frameworks/growth-mindset.md)** -- Dweck's research provides the psychological evidence for what the Stoics intuited: that viewing challenges as development opportunities produces measurably better outcomes. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- The leadership practice of acting despite fear and vulnerability, which operationalises the Inner Citadel concept in team and organisational contexts. +- **[Stoic Mortality and Perspective](stoic-mortality-and-perspective.md)** -- The awareness of mortality gives fortitude its urgency: endurance matters because time is finite. +- **[Building Thinking Strength](../thinking/building-thinking-strength.md)** -- The Clear Thinking framework's self-control and self-confidence pillars are the modern behavioural equivalents of Stoic fortitude applied to entrepreneurial decision-making. diff --git a/plugins/foreman/content/skills/stoic/stoic-mortality-and-perspective.md b/plugins/foreman/content/skills/stoic/stoic-mortality-and-perspective.md new file mode 100644 index 0000000..61cca8a --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-mortality-and-perspective.md @@ -0,0 +1,212 @@ +--- +name: "stoic-mortality-and-perspective" +description: "Applies the Stoic practice of memento mori -- meditation on mortality -- as a tool for entrepreneurial clarity, urgency, and perspective. Teaches how the awareness of death sharpens focus, eliminates trivial distractions, accelerates decision-making, informs legacy thinking, and provides the 'view from above' that rescales problems to their actual size. Use when an entrepreneur is paralysed by indecision, when petty concerns are consuming disproportionate energy, when time management lacks urgency, when succession or legacy questions arise, when perspective has been lost to operational detail, or when the founder needs the ultimate clarifying question: what would matter if this were the last year?" +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - memento-mori + - mortality + - perspective + - time-management + - legacy + - urgency + - focus + - priorities + - stoic + - view-from-above +related_skills: + - stoic-acceptance-amor-fati + - stoic-fortitude-and-resilience + - stoic-virtue-and-kindness + - focus-and-priority-management + - eisenhower-matrix +author: "Fatih Guner" +--- + +# Stoic Mortality and Perspective + +LAST DAY. Marcus Aurelius, the most powerful man in the Western world, began each morning with a thought that would strike most modern executives as morbid: "I may die today." He was not morbid. He was strategic. The meditation did not make him fearful; it made him a better emperor. It eliminated the trivial, accelerated the consequential, and imposed a ruthless filter on how to spend the only resource that cannot be replenished: time. Seneca compressed the same insight into a formula that has lost none of its edge across two millennia: "Let us prepare our minds as if we'd come to the very end of life. Let us postpone nothing. Let us balance life's books each day. The one who puts the finishing touches on their life each day is never short of time." The entrepreneur who treats every day as potentially the last does not become reckless. They become precise. Mortality is not the enemy of ambition. It is the lens through which ambition is focused. + +--- + +## The Framework + +Stoic meditation on mortality -- *memento mori* -- is not a morbid exercise but a cognitive technology. It operates through five distinct mechanisms, each producing practical benefits for the entrepreneur. + +### Mechanism 1: The Priority Filter + +> "Don't behave as if you are destined to live forever. What's fated hangs over you. As long as you live and while you can, become good now." -- Marcus Aurelius, *Meditations* + +The Sword of Damocles -- the blade suspended by a single hair above the throne -- is the ancient world's most vivid metaphor for mortality's relationship to power. Every founder sits beneath a similar blade: the venture could end, health could fail, the market could vanish. Acknowledging the sword does not induce paralysis; it induces clarity. Activities that would not survive the question "Would I do this if I had six months left?" reveal themselves as waste. Meetings that exist out of habit, features that serve vanity, conflicts that feed ego -- all of them wither under mortality's gaze. + +Seneca delivered the operational version of this insight with characteristic precision: "No person hands out their money to passersby, but to how many do each of us hand out our lives! We're tight-fisted with property and money, yet think too little of wasting time, the one thing about which we should all be the toughest misers." + +### Mechanism 2: The View from Above + +> "Think of the whole universe of matter and how small your share. Think about the expanse of time and how brief -- almost momentary -- the part marked for you." -- Marcus Aurelius, *Meditations* + +The Stoics practised a mental exercise they called the "view from above" -- imagining oneself looking down at the Earth, watching the comings and goings of human activity from a cosmic distance. From this altitude, the competitive dynamics that consume a founder's waking hours shrink to their actual proportion. This is not nihilism. It is perspective. The problem that feels existential at 2 a.m. is real, but it is not the entirety of reality. The competitor that seems invincible is also, from sufficient distance, a brief arrangement of atoms and ambition, subject to the same forces of entropy that govern everything. + +Marcus practised this relentlessly: "Think by way of example on the times of Vespasian, and you'll see all these things: marrying, raising children, falling ill, dying, wars, holiday feasts, commerce, farming, flattering, pretending. Now that life of theirs is dead and gone." The people of Vespasian's time believed their concerns were of supreme importance. They were not. Neither are ours. And acknowledging this is not depressing -- it is liberating. + +### Mechanism 3: The Urgency of Excellence + +> "This is the mark of perfection of character -- to spend each day as if it were your last, without frenzy, laziness, or any pretending." -- Marcus Aurelius, *Meditations* + +The critical qualifier in Marcus's formulation is "without frenzy." Living as if today were the last day does not mean panic, hedonism, or abandoning long-term projects. It means bringing full commitment and zero pretence to whatever the day requires. The urgency is not about cramming more in; it is about eliminating the gap between what one values and what one does. The founder who is aware that time is finite does not answer emails faster -- they stop answering emails that should never have been sent. They do not work longer hours -- they work on things that matter. + +The contrast with conventional productivity thinking is illuminating. Productivity frameworks ask: "How do I get more done?" Memento mori asks: "Is this worth doing at all, given that my hours are numbered?" + +### Mechanism 4: The Equaliser + +> "Both Alexander the Great and his mule-keeper were both brought to the same place by death -- they were either received into the all-generative reason, or scattered among the atoms." -- Marcus Aurelius, *Meditations* + +Death is the great leveller, and the Stoics wielded this fact against both arrogance and despair. The entrepreneur inflated by success should remember that Alexander's conquests ended in dust. The entrepreneur crushed by failure should remember the same: the magnitude of any setback, measured against the span of human existence, is vanishingly small. Shakespeare's Hamlet traces the logic to its conclusion: "Imperious Caesar, dead and turn'd to clay, / Might stop a hole to keep the wind away." + +This is not an argument for nihilism. It is an argument against the disproportionate weight we attach to ephemeral outcomes. The fundraise that didn't close, the competitor who copied the product, the board member who was difficult -- all of these are real, but none of them will matter in a century. The character you develop while navigating them might. + +### Mechanism 5: Legacy as Present Action + +> "Stop wandering about! Get busy with life's purpose, toss aside empty hopes, get active in your own rescue -- if you care for yourself at all -- and do it while you can." -- Marcus Aurelius, *Meditations* + +The Stoics were deeply sceptical of legacy as a motivator. Marcus noted that even the most famous names are eventually forgotten: "Everything lasts for a day, the one who remembers and the remembered." The paradox is instructive: the desire for a lasting legacy often produces behaviour (self-promotion, empire-building, vanity projects) that is precisely the opposite of what creates genuine, lasting impact. The Stoic alternative: focus on the quality of present action. Build something excellent because excellence is worth pursuing, not because posterity is watching. Posterity is not watching. Posterity is busy with its own problems. + +Seneca drove the point with a challenge to every entrepreneur who defers meaning to some future horizon: "Aren't you ashamed to reserve for yourself only the remnants of your life and to dedicate to wisdom only that time can't be directed to business?" + +### Mechanism 6: The Conquest of Death-Fear Through Philosophy + +> "Do you then ponder how the supreme of human evils, the surest mark of the base and cowardly, is not death, but the fear of death? I urge you to discipline yourself against such fear." -- Epictetus, *Discourses* + +Cato read Plato's *Phaedo* before taking his own life rather than submitting to Caesar's destruction of the Republic. Seneca, when the executioners came, chided his weeping friends: "Where are your maxims of philosophy, or the preparations of so many years' study against evils to come?" These are extreme cases, but the principle applies to every entrepreneur who lets fear of failure -- a small death of ego -- prevent them from acting. + +The Stoic insight is structurally elegant: if death is the worst possible outcome, and death is certain, then fearing intermediate setbacks is irrational. The fundraise that fails, the product that flops, the company that folds -- none of these are death. And if they were? Death, Epictetus observed, "contains within it the end of fear." The entrepreneur who has genuinely reckoned with mortality finds that lesser fears lose their paralysing power. Not because they become reckless, but because they gain proportion. + +### The Brevity Paradox + +> "It's not at all that we have too short a time to live, but that we squander a great deal of it. Life is long enough, and it's given in sufficient measure to do many great things if we spend it well." -- Seneca, *On the Brevity of Life* + +Seneca's most subversive claim is that life is not short -- we make it short through waste. The average entrepreneur attends meetings that produce no decisions, reads email that demands no response, worries about events they cannot influence, and then complains about insufficient time. The mortality-aware entrepreneur audits time expenditure with the rigour that a CFO applies to cash: every hour is an allocation decision, and every allocation has an opportunity cost measured against a finite budget. + +--- + +## Prompts + +**Prompt 1 -- Memento Mori Priority Audit:** +> Assume I have exactly one year left to lead my company. My company is [describe: stage, product, team]. Given this constraint, help me identify: (1) Which of my current activities would I immediately stop? (2) Which decisions that I have been deferring would I make today? (3) Which relationships would I invest in more deeply? (4) Which projects would I accelerate? Present the analysis as a "mortality-filtered" priority list, ranked by what matters most under the constraint of radical finitude. + +**Prompt 2 -- View from Above:** +> I am consumed by the following problem: [describe in detail -- e.g., a competitive threat, a team conflict, a strategic uncertainty]. Apply the Stoic "view from above" exercise: zoom out progressively -- from the company, to the industry, to the economy, to the century, to the span of human history. At each level of zoom, reassess the actual magnitude of this problem. Then zoom back in and identify: What is the appropriately sized response to this appropriately sized problem? + +**Prompt 3 -- Time-as-Currency Analysis:** +> Audit how I spent the last week as if time were a non-renewable currency (which it is). My calendar and activities for the past week: [describe or paste schedule]. For each major time block, apply Seneca's test: "Did this activity make a full return on the loss of this irreplaceable time?" Categorise each block as: (a) would survive the mortality filter, (b) questionable under the mortality filter, (c) would not survive. For category (c), identify what should replace it. + +**Prompt 4 -- Legacy vs. Present Action:** +> I find myself motivated by legacy thinking -- building something that outlasts me. Apply the Stoic critique: Marcus Aurelius argued that even the most famous names are eventually forgotten and that legacy-seeking often produces the opposite of genuine impact. Help me distinguish: (1) Which of my legacy ambitions are actually about present-day ego? (2) Which are genuinely about creating value that persists? (3) What would I do differently if I released the need to be remembered and focused entirely on the quality of present action? + +--- + +## Use Cases + +**Scale-Stage CEO Paralysed by a Board Decision** + +A CEO at a scaled fintech company has spent four months deliberating over whether to pursue a major international expansion. The decision involves substantial capital risk, board politics, and personal reputation. Analysis paralysis has set in. A mentor introduces the memento mori filter: "If you had one year left as CEO, would you still be deliberating in month four?" The question cuts through the accumulated complexity. The CEO realises that the deliberation has become a substitute for the decision, and that the fear is not about the expansion's economics (which are favourable) but about the personal consequences of failure. Marcus Aurelius's counsel applies: "As long as you live and while you can, become good now." The CEO makes the decision within a week -- not recklessly but with the clarity that mortality-awareness provides. + +**Idea-Stage Founder Struggling with Identity Loss** + +A former investment banker, eighteen months into building a consumer app, finds himself checking LinkedIn obsessively -- monitoring former colleagues' promotions, measuring his own progress against their titles. The behaviour consumes hours per week and produces only misery. The view-from-above exercise delivers the corrective. Zoomed to the level of a human lifespan: the promotions of former colleagues and the founder's current struggle are equally transient arrangements. Zoomed to the level of a century: neither will register. The exercise does not make the founder's ambition irrelevant -- it makes the comparison irrelevant. Seneca's challenge lands: "We're tight-fisted with property and money, yet think too little of wasting time." The founder deletes LinkedIn from his phone. The hours recovered go to customer interviews. + +**Growth-Stage Founder Avoiding Succession Planning** + +A founder who has led her company from inception through Series C systematically avoids conversations about succession, key-person risk, or the company's operation without her. She recognises intellectually that this avoidance is a liability but cannot bring herself to engage with it emotionally. The Stoic framework provides the entry point: memento mori is not about planning for death; it is about planning for life in full awareness of its finitude. The founder begins by applying Marcus Aurelius's exercise: "Think of the life you have lived until now as over and, as a dead man, see what's left as a bonus." From this perspective, succession planning is not a concession to mortality; it is an act of stewardship -- ensuring that the company's value, built through years of effort, persists beyond any single individual. She initiates the succession conversation the following week. + +--- + +## Anti-Patterns + +1. **Using mortality awareness as an excuse for short-termism.** "Life is short" is not a justification for abandoning long-term strategy, cutting corners on quality, or avoiding investments that pay off over years. The Stoics planned and built for decades -- Marcus governed for nearly twenty years; Seneca wrote works intended to endure. Mortality awareness improves the *quality* of long-term action; it does not argue against it. + +2. **Weaponising memento mori for hustle culture.** "You could die tomorrow, so work harder" is a corruption of the Stoic teaching. Marcus explicitly warned against frenzy. Seneca counselled rest. The Stoic insight is not that you should fill every moment with productivity but that you should fill every moment with intention -- and sometimes the most intentional choice is rest, reflection, or the simple enjoyment of being alive. + +3. **Nihilistic misreading of the view from above.** "Nothing matters because we all die" is precisely the opposite of what the Stoics taught. Marcus used the view from above to eliminate *trivial* concerns, not to eliminate all concern. The framework sharpens focus on what matters; it does not argue that nothing does. + +4. **Death-anxiety masquerading as philosophy.** If meditation on mortality produces only anxiety, dread, or despair, the practice is not functioning as intended. Epictetus addressed this directly: "Do you then ponder how the supreme of human evils, the surest mark of the base and cowardly, is not death, but the fear of death?" The goal is not to fear death more keenly but to let the awareness of death reduce the fear of everything else. + +5. **Avoiding grief by philosophising over it.** The Stoics did not recommend bypassing grief through intellectual reframing. Seneca wrote: "It's better to conquer grief than to deceive it." When a real loss occurs -- a death, a relationship, a dream -- the appropriate response is to feel it fully, not to reach for Marcus Aurelius as an anaesthetic. Philosophy supports the processing of grief; it does not substitute for it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Urgency as antidote to procrastination | The idea stage is uniquely vulnerable to deferral: "I'll start when the timing is better." Memento mori eliminates this excuse. The timing will never be perfect, and the time available is unknown. Begin now. Seneca's challenge applies: the one who balances life's books each day is never short of time. | +| Validation | Perspective on rejection's insignificance | Rejection feels catastrophic at the validation stage because the founder's identity is tightly coupled to the idea's reception. The view from above rescales rejection to its actual size: a data point in a process, not a verdict on a life. This perspective enables faster iteration and less emotional recovery time between setbacks. | +| Early Traction | Time-as-currency discipline | Early traction is when time management habits calcify. The founder who treats time as a non-renewable resource at this stage -- ruthlessly eliminating waste, refusing meetings that do not earn their time-cost, protecting blocks for strategic thinking -- builds operational discipline that compounds for years. | +| Growth | The equaliser against ego inflation | Growth brings recognition, press coverage, speaking invitations, and the intoxicating sense that one is building something important. Memento mori is the counterweight: Alexander the Great also thought he was building something important. The discipline is not to diminish ambition but to prevent it from distorting judgement. | +| Scale | Legacy, succession, and stewardship | At scale, the founder must confront what happens to the company after their involvement ends -- whether through choice, circumstance, or mortality. The Stoic framework reframes succession not as loss of control but as the highest form of leadership: building something that transcends any individual, including the founder. | + +--- + +## Output Template + +```markdown +# Memento Mori Strategic Review + +**Founder:** [Name] +**Company:** [Name] +**Date:** [Date] + +## The Last-Year Filter +If I had one year remaining as leader of this company: + +### I would stop: +1. [Activity/commitment and why it fails the mortality test] +2. [Activity/commitment] +3. [Activity/commitment] + +### I would start or accelerate: +1. [Decision/project and why it passes the mortality test] +2. [Decision/project] +3. [Decision/project] + +### I would decide immediately: +1. [Deferred decision and the clarity mortality provides] +2. [Deferred decision] + +## View from Above +**Problem consuming my attention:** [Description] +**Magnitude at company level:** [Assessment] +**Magnitude at industry level:** [Assessment] +**Magnitude at decade level:** [Assessment] +**Magnitude at century level:** [Assessment] +**Appropriately sized response:** [Action calibrated to actual magnitude] + +## Time Audit (Past Week) + +| Time Block | Activity | Mortality Filter | Replace With | +|-----------|----------|-----------------|-------------| +| [Hours] | [Activity] | Survives / Questionable / Fails | [Alternative if fails] | + +## Succession and Stewardship +- **Key-person risks:** [Roles/knowledge that depend entirely on one individual] +- **Stewardship actions this quarter:** [Specific steps toward organisational resilience] +- **What I want to be true about this company regardless of my involvement:** [Vision statement] +``` + +--- + +## Related Skills + +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- Provides the operational frameworks that give structure to the urgency that memento mori produces; mortality awareness without prioritisation tools creates anxiety, tools without the underlying urgency create busywork. +- **[Eisenhower Matrix](../frameworks/eisenhower-matrix.md)** -- The urgent-important distinction maps directly to the Stoic mortality filter; activities that are urgent but unimportant fail the "last year" test most reliably. +- **[Stoic Acceptance and Amor Fati](stoic-acceptance-amor-fati.md)** -- Mortality awareness and fate acceptance are two faces of the same coin; memento mori says time is finite, amor fati says love the time you have, including its end. +- **[Stoic Fortitude and Resilience](stoic-fortitude-and-resilience.md)** -- The awareness of mortality strengthens fortitude by providing ultimate perspective: everything short of death is manageable. +- **[Stoic Virtue and Kindness](stoic-virtue-and-kindness.md)** -- Marcus Aurelius connected mortality directly to virtue: the awareness of death's approach is the most powerful motivator for living virtuously now. +- **[Wanting What Matters](../thinking/wanting-what-matters.md)** -- The memento mori filter produces the same clarity as Pillemer's research on end-of-life regrets: both reveal which pursuits will matter and which are distractions. diff --git a/plugins/foreman/content/skills/stoic/stoic-pragmatism.md b/plugins/foreman/content/skills/stoic/stoic-pragmatism.md new file mode 100644 index 0000000..c037654 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-pragmatism.md @@ -0,0 +1,202 @@ +--- +name: "stoic-pragmatism" +description: "Distills the Stoic insistence on philosophy as action rather than theory, covering simplicity, efficiency, realism, the primacy of practice over abstraction, and the elimination of unnecessary complexity. Use when founders are overthinking strategy at the expense of execution, when organisations are drowning in process without progress, when the gap between stated philosophy and daily behaviour needs closing, or when a team needs to cut through complexity and focus on what actually works." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - pragmatism + - execution + - simplicity + - action + - efficiency + - realism + - practice +related_skills: + - stoic-right-action + - stoic-problem-solving + - stoic-duty-and-service + - focus-and-priority-management + - decision-making-under-pressure + - learning-agility +author: "Fatih Guner" +--- + +# Stoic Pragmatism + +Marcus Aurelius was both philosopher and emperor -- the tension between those roles produced the most pragmatic philosophy ever written. Plato had imagined a utopia governed by a philosopher-king. Marcus lived the reality and discovered what Plato could not have anticipated: that the demands of governing an empire -- plagues, wars, famines, betrayals, Senate politics, logistical nightmares on three continents -- leave no room for philosophy that does not work when applied. His *Meditations* were not written for publication. They were private notes, scrawled in campaign tents and palace chambers, by a man trying to close the gap between what he believed and what he did. That gap -- between theory and practice, between knowing and doing, between the philosophy lecture and Monday morning -- is the central problem of every founder who has ever attended a conference, read a business book, and returned to the office to find that nothing has changed. + +--- + +## The Framework + +Stoic pragmatism is built on a single, uncomfortable premise: philosophy that does not change behaviour is entertainment. Seneca put it without decoration: philosophy "is not concerned with words, but with facts. It's not employed for some pleasure before the day is spent, or to relieve the uneasiness of our leisure. It shapes and builds up the soul, it gives order to life, guides action." + +### Principle 1: Habit Over Theory + +> "When the problem arose whether habit or theory was better for getting virtue, Musonius thought habit to be more effective." -- Musonius Rufus, *Lectures*, 5 + +Knowledge without practice is worse than useless -- it creates the illusion of competence. The founder who has read every book on management but cannot conduct a productive one-on-one is not educated; they are dangerously misinformed about their own capabilities. + +Musonius Rufus resolved the ancient debate between theory and practice with characteristic bluntness: habit wins. Not because theory is unimportant, but because understanding without embodiment is incomplete. A musician who understands music theory but never practises cannot play. A founder who understands lean methodology but never ships an MVP is not lean. + +The Stoic prescription: for every hour of learning, invest two hours of doing. For every framework absorbed, run one experiment. For every strategy articulated, execute one concrete action. The ratio matters more than the absolute numbers. + +### Principle 2: Start Where the World Is + +> "Don't await the perfection of Plato's Republic, but be satisfied with even the smallest step forward and regard the outcome as a small thing." -- Marcus Aurelius, *Meditations*, 9.29 + +The pragmatist begins with conditions as they are, not as they should be. This is not resignation -- it is the necessary precondition for effective action. The community organiser Saul Alinsky articulated the same principle two millennia later: "As an organiser I start from where the world is, as it is, not as I would like it to be." + +Founders violate this principle constantly. They design products for the customer they wish they had rather than the customer who exists. They build organisations for the talent market they imagine rather than the one that is hiring. They create strategies for the competitive landscape they prefer rather than the one that operates. + +The Stoic correction is precise: accept reality fully, then change it incrementally. Waiting for ideal conditions is the most common form of sophisticated procrastination. + +### Principle 3: Eliminate the Unnecessary + +> "It is essential for you to remember that the attention you give to any action should be in due proportion to its worth." -- Marcus Aurelius, *Meditations*, 4.32 + +Marcus Aurelius dedicated an entire meditation to what he called "corralling the unnecessary" -- the systematic elimination of actions, thoughts, and commitments that do not serve the essential purpose. His logic is economic: attention is the scarcest resource, and every unnecessary expenditure of it is a theft from something that matters. + +For founders, the unnecessary takes familiar forms: + +- **Meetings that exist because they have always existed,** not because they produce decisions. +- **Reporting that satisfies process but informs no one.** +- **Features built because competitors have them,** not because customers need them. +- **Strategic planning exercises that produce documents no one reads.** +- **Internal politics -- the most expensive form of unnecessary activity,** consuming energy that produces negative rather than zero output. + +The pragmatic discipline: before every action, ask Marcus's question -- "Is this one of the unnecessary things?" The honest answer, delivered without self-deception, eliminates more waste than any operational efficiency programme. + +Marcus extended this logic beyond actions to thoughts: "We must corral not only unnecessary actions but unnecessary thoughts, too, so needless acts don't tag along after them." The implication for founders is direct. Ruminating about a competitor's funding round, fantasising about a future exit, replaying a meeting that cannot be undone -- these are unnecessary thoughts that generate unnecessary actions. The Stoic practice is to notice the thought, assess its utility, and release what serves no purpose. + +### Principle 4: Make the Words Your Own + +> "I'll tell you how people can prove their words to be their own -- by putting into practice what they've been preaching." -- Seneca, *Moral Letters*, 108.35 + +The Stoics were remarkably unsentimental about intellectual property. Seneca quoted Epicurus -- his philosophical rival -- without embarrassment. Marcus Aurelius borrowed freely from every tradition available to him. The criterion was never originality; it was utility. Does it work? Does it make your life better? Does it produce results? Then use it, regardless of its source. + +This principle liberates the founder from the tyranny of purity. The best operational practices are often borrowed, adapted, and recombined from diverse sources. Amazon's "working backwards" process, Toyota's production system, Bridgewater's radical transparency -- none of these emerged from a single theoretical tradition. They were assembled pragmatically, tested relentlessly, and retained only insofar as they produced outcomes. + +Seneca would have approved. As he wrote: "I'll never be ashamed to quote a bad writer with a good saying." + +### Principle 5: The Pragmatic Relationship With Wealth + +> "No person has the power to have everything they want, but it is in their power not to want what they don't have, and to cheerfully put to good use what they do have." -- Seneca, *Moral Letters*, 123.3 + +Seneca was mocked in his own lifetime as "The Opulent Stoic" -- a philosopher of simplicity who had accumulated one of the largest fortunes in Rome. His response was not apologetic but pragmatic: he had wealth, but he was not enslaved by it. He could lose it tomorrow and continue to philosophise, write, and live well. The wealth was a tool, not an identity. + +This is the Stoic position on material success. The problem is not having money. The problem is needing money -- needing it so desperately that you compromise principles, destroy health, abandon relationships, and make decisions driven by financial anxiety rather than reasoned judgment. The pragmatic founder accumulates resources because resources enable action. But the founder who cannot distinguish between the resources and the purpose they serve has become, in Seneca's framework, a slave wearing expensive clothing. + +John D. Rockefeller, who accumulated more wealth than any person in modern history, arrived at a compatible conclusion through experience rather than philosophy: "A man's wealth must be determined by the relation of his desires and expenditures to his income." The pragmatic question is never "how much do I have?" but "how much do I need?" -- and whether the pursuit of the former is destroying the clarity required for the latter. + +--- + +## Prompts + +**Prompt 1 -- Theory-Practice Gap Analysis:** +> "Audit the gap between what my company says and what it does. Here are our stated values, strategies, and commitments: [list them]. Now here are the actual decisions we made in the past quarter: [list key decisions]. Where do the two diverge? For each gap, identify whether the problem is in the theory (wrong values), the practice (poor execution), or the alignment (right values, insufficient translation mechanisms). Provide a pragmatic action plan to close the three most critical gaps." + +**Prompt 2 -- Unnecessary Corralling Exercise:** +> "Apply Marcus Aurelius's 'corralling the unnecessary' discipline to my current operations. Here is how I spend my typical week: [describe weekly schedule and recurring commitments]. Here is what my company's core mission requires: [describe core activities]. Identify every activity, meeting, process, and commitment that does not directly serve the core mission. For each, recommend: eliminate, delegate, reduce, or retain. Be ruthless." + +**Prompt 3 -- Pragmatic Borrowing Audit:** +> "My company operates in [industry] at [stage]. I have been studying the following frameworks and methodologies: [list what you've been reading/learning]. Help me apply Seneca's pragmatic borrowing principle. For each framework, identify: (1) what is directly applicable to my situation right now, (2) what needs adaptation, (3) what is intellectual entertainment that I should set aside until it becomes relevant. Then design a 30-day execution plan using only the immediately applicable elements." + +**Prompt 4 -- First Impressions Decision Protocol:** +> "I am facing a decision that I have been overcomplicating: [describe the decision and the analysis you've done]. Apply the Stoic discipline of staying with first impressions. Strip the decision to its essential facts. Remove projected outcomes, political considerations, and hypothetical scenarios. Based on the facts alone, what is the obvious action? Then identify what was preventing me from seeing it." + +--- + +## Use Cases + +**The Strategy Retreat That Produces Nothing** + +A growth-stage B2B software company holds a two-day offsite every quarter. Each session produces a 40-page strategic plan, detailed OKRs, and a renewed sense of direction. By the third week after each retreat, the team has reverted to its previous patterns. The documents gather digital dust. Stoic pragmatism diagnoses the problem with surgical precision: the company has confused the production of strategic documents with the execution of strategy. The solution is not a better retreat format; it is a fundamental inversion of the ratio between planning and doing. The quarterly offsite is replaced with a monthly half-day session that reviews three metrics and makes three decisions. The 40-page document is replaced with a single page. The time saved is redirected to execution. Within two quarters, the company accomplishes more than the previous four retreat cycles produced combined. + +**The Founder Who Reads But Does Not Act** + +A validation-stage founder has consumed every major work on product development -- *The Lean Startup*, *Inspired*, *The Mom Test*, *Continuous Discovery Habits* -- and can articulate the principles of customer discovery, hypothesis testing, and iterative design with fluency that would impress a business school professor. The company has been in "validation" for fourteen months without shipping a product to a single paying customer. Musonius Rufus's verdict is clear: theory has become a substitute for action, not a preparation for it. The pragmatic intervention: the founder commits to shipping a minimum viable version within 30 days, using whatever imperfect tools and incomplete knowledge are currently available. The first version is embarrassing. The second version, informed by actual customer contact, is significantly better. By the fourth iteration, the company has paying customers and real data -- something fourteen months of reading never produced. + +**The Over-Engineered Culture Initiative** + +A scale-stage company hires a Chief People Officer who launches an ambitious culture transformation programme: new values workshops, quarterly engagement surveys, a 200-page culture handbook, mandatory training sessions. Eighteen months later, engagement scores have not changed. Marcus Aurelius's corralling principle reveals the problem: the programme created extensive documentation of desired culture but almost no mechanism for practising it. The pragmatic replacement: eliminate the handbook. Replace workshops with a single behavioural expectation reviewed in every team meeting. Replace the engagement survey with weekly one-question pulse checks that managers act on immediately. The company spends 70% less time on "culture initiatives" and sees measurable improvement within three months. Simplicity, as the Stoics understood, is not the absence of sophistication. It is its highest expression. + +--- + +## Anti-Patterns + +**Pragmatism as Anti-Intellectualism.** The Stoics were not hostile to theory. Marcus Aurelius studied philosophy for decades. Seneca wrote voluminously on ethics, natural science, and politics. The pragmatic principle is not "stop thinking" -- it is "don't stop at thinking." Founders who dismiss strategy, reflection, and learning as "ivory tower stuff" have overcorrected. Musonius Rufus said habit was *more* effective than theory, not that theory was worthless. + +**Confusing Speed With Progress.** Action without direction is not pragmatism; it is agitation. The founder who ships features nobody asked for, launches campaigns without hypotheses, and fills calendars with activity that produces no outcomes is busy, not pragmatic. Marcus Aurelius distinguished between what is necessary and what is merely happening. Pragmatism requires both action and discernment about which actions matter. + +**Simplicity as Simplism.** Eliminating the unnecessary is a discipline that requires judgment about what is truly unnecessary. Some things that appear unnecessary are actually load-bearing -- the weekly team check-in that seems like overhead but actually prevents misalignment; the documentation that no one reads until the day it prevents a catastrophic error. The corralling exercise demands honesty, not haste. + +**Borrowed Wisdom Without Adaptation.** Seneca's permission to pillage from all sources comes with an implicit condition: adaptation. The founder who imports Amazon's practices into a twelve-person startup, or applies Toyota's production system to a services business, has borrowed without translating. Every framework requires contextualisation. The pragmatist does not ask "what works?" in the abstract. They ask "what works *here*, *now*, for *us*?" + +**Using Pragmatism to Avoid Hard Truths.** "Let's just focus on execution" can be a legitimate prioritisation -- or it can be a way of avoiding difficult strategic questions that demand confrontation. The Stoic pragmatist faces reality as it is, which sometimes means sitting with uncomfortable truths rather than burying them under activity. + +**Discarding What Works Because It Is Old.** Seneca's counsel to "respect the past, but be open to the future" cuts both ways. "The ones who pioneered these paths aren't our masters, but our guides. Truth stands open to everyone." The pragmatist does not discard a practice merely because it is traditional, nor adopt a practice merely because it is novel. The only criterion is whether it works. Founders who chase the latest methodology while abandoning proven practices are not pragmatic; they are fashionable -- and fashion is a poor substitute for results. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Ship before you are ready; imperfect contact with reality beats perfect preparation in isolation | The greatest risk is analysis paralysis. The pragmatic founder tests the idea before refining it, knowing that the market will teach more in one week than research will teach in six months | +| Validation | Strip hypotheses to their simplest testable form; eliminate everything that does not produce a learning signal | Unnecessary complexity at this stage is often disguised as thoroughness. The pragmatic test: does this activity produce data that changes our next decision? If not, cut it | +| Early Traction | Build systems that are good enough, not perfect; optimise for speed of iteration over elegance of design | The temptation to professionalise too early -- hiring specialists, implementing enterprise tools, creating elaborate processes -- consumes resources that should be directed at serving customers | +| Growth | Systematise what works; eliminate what persists only by habit; resist the complexity creep that growth invites | Growth creates organisational scar tissue -- processes and structures that were solutions to past problems but are now obstacles to future ones. Regular corralling is essential | +| Scale | Preserve simplicity within institutional complexity; ensure that pragmatic execution culture survives formalisation | The paradox of scale: the very systems that enable growth also inhibit the pragmatic flexibility that created it. The Stoic discipline is to audit relentlessly -- not annual reviews, but continuous questioning of whether each process earns its existence | + +The progression follows an arc from individual pragmatism (idea and validation) to organisational pragmatism (early traction and growth) to institutional pragmatism (scale). At each stage, the enemy is different -- personal overthinking, team inefficiency, organisational inertia -- but the Stoic medicine is the same: act, simplify, adapt, repeat. + +--- + +## Output Template + +```markdown +# Pragmatic Execution Assessment + +## Theory-Practice Gap +| Stated Principle | Actual Behaviour | Gap Severity (1-5) | Root Cause | +|-----------------|-----------------|---------------------|------------| +| [Principle] | [What actually happens] | [Score] | [Why] | + +## Unnecessary Activity Audit +| Activity | Weekly Hours | Serves Core Mission? | Decision | +|----------|-------------|---------------------|----------| +| [Activity] | [Hours] | [Y/N/Partially] | [Eliminate/Delegate/Reduce/Retain] | + +## Recovered Capacity +- **Hours freed per week:** [Total] +- **Redirected to:** [Core activity] + +## Pragmatic Borrowing Plan +| Framework / Idea | Source | Applicable Element | Adaptation Needed | 30-Day Action | +|-----------------|--------|-------------------|-------------------|---------------| +| [Framework] | [Source] | [Element] | [Adaptation] | [Action] | + +## Next Three Actions (This Week) +1. [Action] -- [Expected outcome] +2. [Action] -- [Expected outcome] +3. [Action] -- [Expected outcome] +``` + +--- + +## Related Skills + +- **[Stoic Right Action](stoic-right-action.md)** -- Pragmatism without ethics is mere efficiency; right action ensures that what gets done is worth doing. +- **[Stoic Problem Solving](stoic-problem-solving.md)** -- The pragmatic companion to obstacle inversion: converting setbacks into usable advantages requires both reframing and execution. +- **[Stoic Duty and Service](stoic-duty-and-service.md)** -- Duty provides the purpose that pragmatism serves; without it, efficiency becomes aimless optimisation. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- The operational expression of Marcus Aurelius's corralling principle, applied to modern calendars and task lists. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- When time compresses, pragmatism becomes survival -- the ability to act on first impressions without overthinking. +- **[Choosing and Executing](../decisions/choosing-and-executing.md)** -- The practical decision-making companion that addresses the moment of commitment and follow-through that Stoic pragmatism demands. diff --git a/plugins/foreman/content/skills/stoic/stoic-problem-solving.md b/plugins/foreman/content/skills/stoic/stoic-problem-solving.md new file mode 100644 index 0000000..895a03e --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-problem-solving.md @@ -0,0 +1,199 @@ +--- +name: "stoic-problem-solving" +description: "Teaches Marcus Aurelius's central method for converting obstacles into advantages, covering the reverse clause, creative reframing, persistence under adversity, and the discipline of focused action. Use when a startup faces setbacks that feel terminal, when market conditions shift against you, when key plans fail and alternatives seem absent, or when the team needs a framework for resilience and resourcefulness under pressure." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - resilience + - obstacles + - reframing + - adversity + - persistence + - problem-solving + - resourcefulness +related_skills: + - stoic-right-action + - stoic-pragmatism + - stoic-duty-and-service + - learning-from-failure + - leader-resilience-and-wellbeing + - scenario-planning +author: "Fatih Guner" +--- + +# Stoic Problem Solving + +Marcus Aurelius produced the most famous formula in practical philosophy with five words: "The obstacle on the path becomes the way." Not a metaphor. Not encouragement. A method. The Roman emperor who spent the better part of two decades fighting plagues, wars, betrayals, and the slow disintegration of an empire did not arrive at this principle through optimism. He arrived at it through necessity. The insight is structural: every impediment to action can be converted into a means of advancing action, provided the mind retains its capacity to adapt. For the entrepreneur -- whose daily existence is a sequence of plans colliding with reality -- this is not consolation philosophy. It is the operating system. + +--- + +## The Framework + +Stoic problem solving operates through three interlocking disciplines, each one a distinct cognitive skill that can be practised and strengthened. + +### Discipline 1: The Reverse Clause + +> "Indeed, no one can thwart the purposes of your mind -- for they can't be touched by fire, steel, tyranny, slander, or anything." -- Marcus Aurelius, *Meditations*, 8.41 + +The reverse clause is a contingency built into every intention. Before executing any plan, the Stoic adds a silent qualifier: *if conditions allow -- and if they don't, I will use whatever happens instead.* This is not pessimism. It is architectural resilience. + +The historical precedent is instructive. Zeno, the very founder of Stoicism, was a merchant whose ship sank along with its entire cargo. He washed up in Athens, wandered into a bookstore, discovered philosophy, and founded the school that would shape Western thought for two millennia. "Now that I've suffered shipwreck," Zeno reportedly said, "I'm on a good journey." The entire philosophy is built on the principle it teaches. + +Consider how this works in practice. A startup plans to launch a product in Q2. The reverse clause says: if the launch is delayed by a supply chain failure, that delay becomes an opportunity to refine the onboarding experience, stress-test the infrastructure, or build anticipation through a controlled beta. The plan has not failed. It has adapted. + +The reverse clause transforms the emotional experience of setbacks. Without it, every disruption feels like a defeat. With it, disruptions become redirections -- pre-authorised by the founder's own reasoning. + +### Discipline 2: The Inversion of Obstacles + +> "The mind adapts and converts any obstacle to its action into a means of achieving it. That which is an impediment to action is turned to advance action." -- Marcus Aurelius, *Meditations*, 5.20 + +This is the core mechanism. When an obstacle blocks the intended path, the Stoic does not merely find an alternative route. The Stoic asks: *what virtue or advantage does this specific obstacle make possible?* + +The logic runs as follows: + +- If a competitor launches first, it becomes a chance to learn from their mistakes and their market education costs. +- If a key hire declines the offer, it becomes a chance to re-examine whether the role was correctly scoped. +- If funding falls through, it becomes a chance to build a leaner, more capital-efficient operation that will be structurally stronger when funding eventually arrives. +- If a customer churns, it becomes a chance to practice the discipline of honest post-mortem analysis. + +Nick Saban, the legendary college football coach, built his dynasty on what he called "The Process" -- ignoring the scoreboard and focusing exclusively on executing the next play. This is Stoic problem solving in athletic clothing. The accumulation of correctly executed small actions -- each one a response to whatever the present moment demands -- produces results that grand strategy alone cannot. + +Marcus Aurelius captured this with the metaphor of building: "You must build up your life action by action, and be content if each one achieves its goal as far as possible." The operative phrase is "as far as possible." The Stoic does not demand perfection from each action. The demand is for full engagement -- brick by boring brick, each one laid as well as current conditions allow. + +### Discipline 3: Staying Within First Impressions + +> "Don't let your reflection on the whole sweep of life crush you. Don't fill your mind with all the bad things that might still happen. Stay focused on the present situation." -- Marcus Aurelius, *Meditations*, 8.36 + +Problems become unsolvable when they expand beyond their actual dimensions. A cash flow squeeze in March becomes, in the founder's anxious imagination, a bankruptcy in July, a reputation collapse in September, an unemployable future in December. The Stoic discipline is to stop at the first impression -- the actual, present problem -- and refuse to let catastrophic narration inflate it. + +Marcus Aurelius's instruction: stick with the facts as initially reported. Someone is speaking badly about you -- that is the report. The report does not include that you have been harmed. Your runway is shorter than projected -- that is the fact. The fact does not include that the company is finished. + +This discipline is the difference between a problem that can be solved and a crisis that cannot be endured. Nearly every problem, stripped of its imagined extensions, is manageable. + +Seneca reinforced this principle with characteristic pragmatism: "Apply yourself to thinking through difficulties -- hard times can be softened, tight squeezes widened, and heavy loads made lighter for those who can apply the right pressure." The "right pressure" is focused attention on the actual problem, not the imagined cascade of consequences that the anxious mind projects onto it. + +### The Problem-Solving Sequence + +Combining the three disciplines produces a repeatable protocol: + +1. **Encounter the obstacle.** Do not get emotional. Marcus's first rule: don't get worked up. +2. **Stay with first impressions.** What is the actual problem, stripped of projected catastrophe? +3. **Activate the reverse clause.** What opportunity does this specific obstacle create? +4. **Invert the obstacle.** What virtue, skill, or advantage can be practised or built precisely because of this setback? +5. **Execute the next right action.** Brick by boring brick. One correct step, then the next. + +The sequence is designed to be executed rapidly -- in minutes, not days. The longer the gap between encountering an obstacle and initiating the response, the more opportunity catastrophic narration has to inflate the problem beyond its actual dimensions. Speed of cognitive reframe is itself a trainable skill. + +--- + +## Prompts + +**Prompt 1 -- Obstacle Inversion Analysis:** +> "My startup is facing the following obstacle: [describe the obstacle in factual terms]. Apply the Stoic problem-solving framework. First, strip the problem to its first impressions -- what is actually happening versus what I fear might happen. Second, identify the reverse clause -- what alternative paths does this obstacle open. Third, invert the obstacle -- what specific advantage, virtue, or capability can be built precisely because of this setback. Provide three concrete next actions." + +**Prompt 2 -- Setback Pattern Recognition:** +> "Here are the three biggest setbacks my company has experienced in the past year: [list setbacks]. For each one, apply the Stoic inversion lens retroactively. What advantages did we gain (or could we have gained) from each setback? Are there patterns in how we respond to obstacles that reveal systematic weaknesses in our problem-solving? What Stoic disciplines would most improve our collective resilience?" + +**Prompt 3 -- Pre-Mortem With Reverse Clauses:** +> "We are about to execute [describe plan]. Using the Stoic reverse clause method, identify the five most likely obstacles we will encounter. For each obstacle, design a specific reverse clause -- a pre-committed alternative path that converts the obstacle into an advantage. Format as a contingency playbook I can share with my team." + +**Prompt 4 -- First Impressions Audit:** +> "I am currently overwhelmed by what feels like an existential threat to my business: [describe the situation]. Help me apply Marcus Aurelius's discipline of staying within first impressions. Separate the factual situation from my projected catastrophe. What is actually happening right now? What is merely my anxious extrapolation? Then identify one concrete action I can take in the next two hours." + +--- + +## Use Cases + +**The Failed Product Launch** + +An early-traction e-commerce platform spends four months preparing a major feature launch. On launch day, a critical bug renders the checkout flow unusable for 30% of users. Revenue projections for the quarter are immediately threatened. The standard reaction: panic, blame, emergency all-hands meetings that consume three days of engineering time. The Stoic response: stay within first impressions (the bug exists; the company does not). Activate the reverse clause (the bug reveals a gap in QA processes that, once fixed, will prevent larger failures later). Invert the obstacle (the public response to the bug -- transparent communication, rapid fix, customer credits -- becomes a trust-building event that no marketing campaign could replicate). The company's NPS scores increase in the following month. The obstacle became the way. + +Seneca's observation applies: "Rivers are easiest to cross at their source." The bug was caught on launch day, not six months later when the customer base was ten times larger. The obstacle, properly inverted, revealed its timing as an advantage. + +**The Investor Who Walked Away** + +A validation-stage deep-tech startup receives a verbal commitment from a lead investor for a $3 million seed round. Two weeks before closing, the investor pulls out, citing "portfolio rebalancing." The other participants in the round withdraw in a domino effect. The founder, facing six months of runway, has two options: despair or inversion. The Stoic approach: the lost round forces a leaner operating model that extends runway to eleven months. The extra time, combined with reduced burn, produces stronger unit economics. When the founder returns to market three months later, the metrics are significantly more compelling. The company raises $5 million instead of $3 million, at a higher valuation, from investors who are more aligned with the company's actual trajectory rather than its projections. + +**The Regulatory Surprise** + +A growth-stage healthtech company learns that new regulations will require significant changes to its data handling practices, adding six months and substantial cost to its roadmap. Competitors publicly complain and lobby against the regulation. The Stoic founder inverts: the regulation creates a compliance barrier that will eliminate smaller, less-resourced competitors. The company invests aggressively in compliance, finishes early, and markets its regulatory readiness as a differentiator. The obstacle -- a regulatory burden -- becomes a moat. + +--- + +## Anti-Patterns + +**Toxic Positivity Masquerading as Stoicism.** "Everything happens for a reason" is not what Marcus Aurelius wrote. He wrote that every obstacle can be used -- not that every obstacle is secretly good. The distinction matters. Stoic problem solving does not require the founder to pretend that losing a key employee or missing a revenue target is secretly wonderful. It requires the founder to ask what can be done *with* the situation, not to fabricate gratitude for it. + +**Passivity Dressed as Acceptance.** The reverse clause is not permission to give up on the original plan at the first sign of difficulty. Seneca warned against those who are "too unstable to live as they wish, but only live as they have begun." The Stoic changes course when the obstacle is genuine and the reversal offers a better path -- not when the work simply becomes hard. + +**Intellectualising Instead of Acting.** The Stoic framework is a decision tool, not a journaling exercise. Founders who spend hours analysing the philosophical dimensions of their setbacks while taking no concrete action have inverted the priority. Marcus Aurelius wrote his meditations in brief, often single-paragraph entries between governing an empire and commanding armies. The thinking serves the doing, never the reverse. + +**Ignoring the Emotional Dimension.** The instruction "don't get worked up" is not the same as "don't feel anything." The Stoics acknowledged that initial emotional reactions are involuntary -- what they called *propatheiai* (pre-emotions). The discipline is in what happens next: whether the emotion drives the response or whether reasoned judgment intervenes. Founders who suppress emotion entirely often find it erupting at worse moments. The goal is not emotional absence but emotional governance. + +**Applying the Framework in Isolation.** Stoic problem solving is a leadership practice, not a private coping mechanism. The founder who silently inverts obstacles without communicating the reframe to the team misses the multiplier effect. As the Navy SEALs say: "Calm is contagious." When the founder models factual assessment and forward-looking action in front of the team, the entire organisation's capacity for resilience increases. The obstacle becomes the way not just for the individual but for the collective. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Building the mental habit of obstacle inversion before real obstacles arrive | Problems at this stage are mostly internal -- self-doubt, analysis paralysis, fear of starting. The obstacle is the mind itself, and the discipline of first impressions is the primary tool | +| Validation | Converting negative market signals into sharper product hypotheses | Every "no" from a potential customer contains information. The reverse clause here is systematic: rejection feeds iteration. Founders who cannot invert validation failure will not survive this stage | +| Early Traction | Managing operational setbacks without losing momentum or team morale | The team is watching the founder's response to adversity. Calm is contagious. The founder who models Stoic problem solving -- factual assessment, reverse clause, immediate action -- teaches the team to do the same | +| Growth | Turning competitive threats and scaling failures into structural improvements | At growth stage, obstacles are systemic rather than episodic. A single customer loss is survivable; a pattern of churn requires the deeper Stoic discipline of honest diagnosis without catastrophic narration | +| Scale | Navigating institutional crises (regulatory, reputational, market-wide) with composure | The founder's role shifts from problem-solver to problem-framing leader. The Stoic disciplines must be embedded in organisational culture, not held privately by the founder | + +The progression across stages follows a pattern: from personal resilience (idea and validation) to collective resilience (early traction and growth) to institutional resilience (scale). The Stoic method remains identical; its application widens. + +One critical insight applies across all stages: the quality of problem solving is determined before the problem arrives. Epictetus compared philosophy to boxing training: "What kind of boxer are you if you leave because you get hit? That's the nature of the sport!" The founder who practises the reverse clause on small setbacks -- a missed deadline, a difficult customer, a minor technical failure -- builds the cognitive muscle that will fire automatically when the existential threat arrives. Training cannot begin at the moment of crisis. It must precede it. + +--- + +## Output Template + +```markdown +# Obstacle Inversion Brief + +## The Obstacle +- **Factual description (first impressions only):** [What has actually happened] +- **Projected catastrophe (to be set aside):** [What you fear will happen] +- **Actual scope:** [Time horizon, financial impact, stakeholders affected] + +## Reverse Clause Analysis +- **Original plan:** [What you intended to do] +- **What the obstacle blocks:** [Specifically which element is impeded] +- **Alternative paths opened:** [What becomes possible because of this obstacle] + +## Obstacle Inversion +- **Virtue or skill this obstacle trains:** [What capability is strengthened] +- **Competitive advantage created:** [How this setback positions you better] +- **Hidden information revealed:** [What you now know that you didn't before] + +## Next Actions (Brick by Brick) +1. **Within 24 hours:** [Immediate concrete action] +2. **Within one week:** [Follow-through action] +3. **Within one month:** [Structural change or new initiative] + +## Team Communication +- **Message to team:** [How to frame this for collective resilience] +- **Tone:** [Factual, calm, forward-looking] +``` + +--- + +## Related Skills + +- **[Stoic Right Action](stoic-right-action.md)** -- Problem solving must be guided by ethical judgment; cleverness without virtue produces worse problems. +- **[Stoic Pragmatism](stoic-pragmatism.md)** -- The pragmatic companion to obstacle inversion, ensuring solutions are actionable rather than merely philosophical. +- **[Stoic Duty and Service](stoic-duty-and-service.md)** -- Obstacles are not merely personal challenges; they are opportunities to fulfil one's duty to others. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- The systematic extraction of insight from setbacks, complementing the Stoic reframing method. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- A structured approach to anticipating obstacles before they arrive, aligned with the Stoic reverse clause. +- **[Defining and Exploring Problems](../thinking/defining-and-exploring-problems.md)** -- The structural problem-definition discipline complements the Stoic reframing approach with root-cause analysis and the 3-Lens Principle. diff --git a/plugins/foreman/content/skills/stoic/stoic-right-action.md b/plugins/foreman/content/skills/stoic/stoic-right-action.md new file mode 100644 index 0000000..6f729b5 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-right-action.md @@ -0,0 +1,198 @@ +--- +name: "stoic-right-action" +description: "Applies Stoic ethics of right action to entrepreneurial decision-making, covering the four cardinal virtues (courage, justice, temperance, wisdom), ethical leadership under pressure, and the discipline of choosing the harder right over the easier wrong. Use when facing ethical dilemmas in business, building a values-driven culture, making decisions with imperfect information, navigating conflicts between profit and principle, or establishing personal and organizational codes of conduct." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ethics + - decision-making + - leadership + - character + - values + - courage + - integrity +related_skills: + - stoic-problem-solving + - stoic-duty-and-service + - stoic-pragmatism + - emotional-courage + - purpose-driven-leadership + - trust-equation +author: "Fatih Guner" +--- + +# Stoic Right Action + +Every day brings dozens of crossroads -- moments where the easy path and the right path diverge, sometimes subtly, sometimes violently. The Stoics had one question at each: *what is the right thing to do?* Not what is profitable, not what is popular, not what is safe. What is right. Marcus Aurelius governed an empire with this single compass. Epictetus taught it from a room he could barely afford. Seneca deployed it while navigating one of the most treacherous courts in Roman history. The question never changed. The circumstances were irrelevant. For the entrepreneur, who faces a relentless sequence of decisions under uncertainty, this is not philosophical decoration. It is operational infrastructure. + +--- + +## The Framework + +Stoic ethics rests on four cardinal virtues, each one a load-bearing pillar without which the structure collapses. These are not aspirational ideals. They are daily practices -- habits of judgment that the Stoics treated with the same seriousness a pilot treats a pre-flight checklist. Marcus Aurelius distilled the entire edifice to a single sentence: "What is your vocation? To be a good person." The simplicity is deceptive. The execution is the work of a lifetime. + +### The Four Cardinal Virtues + +**Courage (Andreia):** The capacity to act rightly under conditions of risk, fear, or social pressure. Courage is not the absence of fear but the judgment that something else matters more. For founders, this manifests in hard conversations -- telling investors the truth about burn rate, firing a popular but toxic executive, admitting a product direction was wrong. As Seneca observed: "Good people will do what they find honorable to do, even if it requires hard work; they'll do it even if it causes them injury; they'll do it even if it will bring danger." + +**Justice (Dikaiosyne):** Treating every person -- co-founder, customer, employee, competitor -- according to their due. Justice in the Stoic sense is not legalism. It is the active commitment to fairness in a world that constantly incentivises partiality. Marcus Aurelius wrote that "the unjust person acts against the gods" because rational beings were made for mutual benefit, not exploitation. The entrepreneur who pays invoices late to preserve cash flow, who uses asymmetric information to extract better terms, who treats vendors differently from customers -- each is committing an injustice that the Stoics would recognise instantly. + +**Temperance (Sophrosyne):** Self-control and moderation -- the virtue that prevents success from becoming its own undoing. The startup ecosystem worships growth at all costs, celebrates excess as ambition, and confuses discipline with timidity. Temperance is the corrective. It governs spending, ego, risk appetite, and the thousand small indulgences that compound into disaster. Musonius Rufus asked a pointed question that every well-funded founder should hear: "How much better is it to be known for doing well by many than for living extravagantly?" The answer, in every era, is the same. + +**Wisdom (Phronesis):** The ability to discern what is truly good, truly bad, and truly indifferent. Wisdom is the master virtue because it directs the other three. Without wisdom, courage becomes recklessness, justice becomes rigidity, and temperance becomes paralysis. Epictetus's formulation is surgical: "Where is Good? In our reasoned choices. Where is Evil? In our reasoned choices." + +### The Decision Architecture + +The Stoics did not leave right action to intuition. Marcus Aurelius articulated a two-step protocol for every decision: + +1. **Don't get worked up.** Emotional agitation distorts judgment. Whatever has happened, it is not as unprecedented as it feels. Emperors and beggars alike have faced worse. The first step is always to create the internal conditions for clear thought. +2. **Remember your principles and act.** Run the decision through your values. The answer almost always clarifies itself. The second step converts clarity into motion. + +> "Don't get upset. Do the right thing. That's it." -- Marcus Aurelius, *Meditations*, 8.5 + +This is deceptively simple. The difficulty lies not in understanding it but in executing it at speed, under pressure, when the stakes are personal. The Stoics knew this, which is why they treated ethics as a practice -- something trained daily, not consulted occasionally. + +Epictetus reinforced the point with a boxing metaphor: philosophy is training for life. "Don't you understand that really amounts to saying that if I would so prepare myself to endure, then let anything happen that will? Otherwise, it would be like the boxer exiting the ring because he took some punches." The entrepreneur who has not trained the ethical reflex before the ethical test arrives will not pass it. The test comes without warning, and there is no time to consult the manual. + +The practical implication: ethical decision-making should be rehearsed -- in team discussions, in scenario planning, in the private daily review that Marcus practised until the final days of his life. It is never too late to begin, and no one is too experienced to continue. + +### Character as Competitive Advantage + +Musonius Rufus argued that philosophy "doesn't consist in outward display, but in taking heed to what is needed and being mindful of it." The Stoic is identified not by uniform or proclamation but by character alone. In business, this translates to a simple observation: reputation compounds. Every ethical shortcut is a withdrawal from an account that takes years to build and seconds to deplete. + +The entrepreneur who acts rightly -- not performatively, not strategically, but as a matter of settled disposition -- attracts better partners, retains better employees, and earns the trust of customers who have learned, through bitter experience, to distrust everyone else. As Epictetus put it: "First tell yourself what kind of person you want to be, then do what you have to do." + +### The Chain of Small Choices + +Zeno, the founder of Stoicism, reportedly said that "well-being is realized by small steps, but is truly no small thing." The architecture of right action is not built from dramatic, headline-worthy ethical stands. It is assembled from hundreds of small choices -- how you respond to a frustrating email, whether you credit a colleague's contribution in a meeting, whether you round the invoice up or down, whether you share bad news promptly or bury it in a quarterly review. + +Each small choice reinforces a disposition. Epictetus used the metaphor of fuel and fire: "Every habit and capability is confirmed and grows in its corresponding actions." The founder who practises justice in trivial matters -- splitting a restaurant bill fairly, acknowledging an intern's idea -- is training the neural pathways that will fire automatically when justice is required in a $10 million negotiation. Conversely, the founder who cuts small corners is rehearsing for the day when the corner is not small at all. + +The Stoic discipline is to treat every decision as a character-forming event. Not because every decision is equally consequential, but because the habit of choosing rightly is what makes consequential decisions tractable when they arrive without warning. + +--- + +## Prompts + +**Prompt 1 -- Ethical Crossroads Audit:** +> "I am facing a business decision where the profitable path and the ethical path seem to diverge. Here is the situation: [describe situation]. Apply the four Stoic cardinal virtues (courage, justice, temperance, wisdom) as separate lenses. For each virtue, identify what it demands in this specific case. Then synthesize: what is the right action, and what is the likely cost of taking it versus avoiding it?" + +**Prompt 2 -- Character Stress Test:** +> "Evaluate my company's recent decisions through a Stoic ethical lens. Here are the three most significant decisions we made in the past quarter: [list decisions]. For each, assess: (1) Did we choose the harder right or the easier wrong? (2) Which cardinal virtue was most tested? (3) Where did we compromise, and was the compromise justified? Provide a character score and specific recommendations." + +**Prompt 3 -- Values Integration Blueprint:** +> "Help me translate Stoic principles of right action into concrete operating practices for my startup. My company is at [stage] in [industry] with [team size] people. I want to embed ethical decision-making into our daily operations -- not as a poster on the wall but as a decision protocol. Design a practical system that includes hiring criteria, decision frameworks, and accountability mechanisms rooted in the four cardinal virtues." + +**Prompt 4 -- Courage Calibration:** +> "I have been avoiding a difficult but necessary action in my business: [describe the avoided action]. Using the Stoic framework of right action, help me understand why I am avoiding it, what courage specifically requires in this situation, and create a concrete plan for executing it within the next 48 hours. Include the Stoic perspective on why delay makes it worse." + +--- + +## Use Cases + +**The Co-Founder Equity Dispute** + +A validation-stage SaaS startup discovers that one of three co-founders has been contributing significantly less than the other two for six months. The contributing founders avoid the conversation because the third co-founder was the original idea holder and has personal financial difficulties. Stoic right action demands courage (having the conversation), justice (restructuring equity to reflect actual contribution, not sentiment), temperance (doing so without vindictiveness), and wisdom (recognizing that unaddressed resentment will destroy the company faster than an uncomfortable conversation). Marcus Aurelius's two-step protocol applies directly: don't get emotional, then do what is right. The conversation happens. The equity is restructured. The company survives. + +**The Enterprise Customer With Conditions** + +A growth-stage fintech company lands a potential enterprise deal worth 40% of annual revenue. The customer requests a "minor" data-sharing arrangement that technically complies with regulations but violates the spirit of the company's privacy commitments to individual users. The sales team argues that no one will know. Stoic justice -- treating every person according to their due, including the users who trusted the company -- makes the answer clear. The deal is declined or renegotiated. Seneca's observation resonates: "The greatest portion of peace of mind is doing nothing wrong." + +**The Layoff Communication** + +A scale-stage company must reduce headcount by 15%. The CFO recommends announcing via email on a Friday afternoon to "minimize disruption." Stoic right action recognizes this for what it is: cowardice dressed as efficiency. Courage demands face-to-face communication. Justice demands transparent explanation. Temperance demands that leadership absorb the discomfort rather than offload it onto departing employees. The layoffs happen with dignity, and the remaining team's trust in leadership deepens rather than fractures. + +Marcus Aurelius sold imperial furnishings to pay war debts rather than taxing an already burdened populace. The modern parallel: the founder who takes a salary cut before reducing headcount, who communicates transparently about the company's financial position, who treats departing employees as people rather than line items. Right action in moments of crisis is not merely ethically superior. It is strategically superior, because the people who remain are watching, and they will remember how leadership behaved when the pressure was real. + +--- + +## Anti-Patterns + +**Virtue Signalling Without Virtue.** Posting values on the website while violating them in practice is not Stoicism; it is marketing. The Stoics were explicit that philosophy must be demonstrated through action, not words. Epictetus warned against those who "receive the bare theories" and "immediately want to spew them." If the company's stated values do not match its actual decisions, the values statement is worse than useless -- it is a liability, creating expectations the organisation has no intention of meeting. + +**Moral Perfectionism as Paralysis.** Some founders interpret "right action" as requiring certainty of ethical purity before any action can be taken. This is a misunderstanding. The Stoics were pragmatists. Marcus Aurelius explicitly cautioned against waiting for "the perfection of Plato's Republic." Right action often means making the best available choice under imperfect conditions, not waiting for a flawless option that will never arrive. + +**Confusing Comfort With Conscience.** The feeling of discomfort is not evidence that an action is wrong. More often, it is evidence that the action is right but difficult. Founders who avoid hard conversations, tough feedback, or unpopular decisions because they "don't feel right" are confusing the signal. The Stoic framework insists on reasoned judgment, not emotional comfort, as the guide. + +**Weaponising Ethics Against Others.** Using Stoic principles to judge others rather than govern oneself is the precise inversion of the practice. Marcus Aurelius's meditations are self-directed -- he interrogates his own conduct, not his subordinates'. Founders who deploy ethical language to control, shame, or manipulate their teams have missed the point entirely. + +**Selective Virtue Application.** Applying courage in investor meetings but not in employee feedback sessions. Practising justice with customers but not with vendors. Exercising temperance in public spending but indulging privately. The cardinal virtues are not situation-specific tools to be deployed strategically. They are character traits that either permeate everything or exist nowhere. Marcus Aurelius's reminder is pointed: "How you do anything is how you do everything." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Establishing personal ethical foundations before external pressures arrive | Right action is cheapest here -- there are few stakeholders, few temptations, and maximum freedom to set precedent | +| Validation | Honest assessment of product-market signals; resisting the temptation to cherry-pick data | The pressure to show traction creates incentives to deceive -- investors, customers, oneself. Courage means reporting what the data actually shows | +| Early Traction | Building culture through hiring and firing decisions that reflect stated values | Every early hire is a cultural statement. Justice demands consistent application of standards regardless of how desperate you are for talent | +| Growth | Maintaining ethical consistency as scale introduces complexity and delegation | Right action must become systemic, not personal. The founder cannot be present at every decision; the virtues must be embedded in process and people | +| Scale | Navigating institutional pressures (board expectations, market demands) that test foundational commitments | The hardest stage for right action. The company is now an institution with its own momentum, and the founder's ethical convictions face pressure from stakeholders who measure only outcomes | + +At every stage, the Stoic insight holds: the cost of ethical compromise is always higher than it appears, and it compounds. The founder who cuts a corner at the idea stage creates a precedent that metastasises through every subsequent phase. Seneca's warning about vices applies directly: "There is no vice which lacks a defense, none that at the outset isn't modest and easily intervened -- but after this the trouble spreads widely." Ethical drift begins as a trickle and ends as a flood. + +The practical implication is that right action is an investment with asymmetric returns: the cost of maintaining it is constant and modest, while the cost of recovering from its absence is catastrophic and unpredictable. + +Marcus Aurelius understood this arithmetic intimately. His daily practice of self-examination -- questioning his own choices, testing his reasoning, holding himself accountable before sleep -- was not self-indulgence. It was maintenance. The founder who adopts a similar practice, even five minutes of honest review at day's end, builds the compound interest of character that no crisis can liquidate overnight. + +--- + +## Output Template + +```markdown +# Ethical Decision Analysis + +## The Crossroads +- **Decision required:** [Describe the decision] +- **Stakeholders affected:** [List all parties] +- **Time pressure:** [Urgency level and deadline] + +## Cardinal Virtue Assessment + +### Courage +- **What courage demands:** [Specific action] +- **What fear suggests instead:** [The avoidance path] + +### Justice +- **Who is owed what:** [Stakeholder-by-stakeholder assessment] +- **Where fairness is at risk:** [Identify potential injustice] + +### Temperance +- **What excess looks like here:** [The overreaction] +- **What moderation requires:** [The disciplined response] + +### Wisdom +- **What is truly at stake:** [Separate real from apparent stakes] +- **What is indifferent:** [What can be released] + +## The Right Action +- **Decision:** [Clear statement] +- **Rationale:** [Why this is right, not merely expedient] +- **Expected cost:** [Honest assessment of the price] +- **Long-term consequence of avoidance:** [What happens if you don't] + +## Execution Plan +- **Step 1:** [Immediate action] +- **Step 2:** [Follow-through] +- **Step 3:** [Accountability mechanism] +``` + +--- + +## Related Skills + +- **[Stoic Problem Solving](stoic-problem-solving.md)** -- When right action meets an obstacle, the obstacle itself becomes the path forward. +- **[Stoic Duty and Service](stoic-duty-and-service.md)** -- Right action without a sense of duty is episodic; duty makes it structural. +- **[Stoic Pragmatism](stoic-pragmatism.md)** -- The bridge between knowing the right thing and actually doing it under real-world constraints. +- **[Emotional Courage](../leadership/emotional-courage.md)** -- The leadership competency most directly tested by Stoic right action; taking principled stands requires practised courage. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Right action is the primary input to the trust that compounds over a company's lifetime. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- Values-based leadership as an organisational design principle, translating Stoic ethics into collective mission. +- **[Covey's Seven Habits](../frameworks/covey-seven-habits.md)** -- The principle-centred leadership model that shares Stoicism's emphasis on character as the foundation of effectiveness. diff --git a/plugins/foreman/content/skills/stoic/stoic-self-awareness.md b/plugins/foreman/content/skills/stoic/stoic-self-awareness.md new file mode 100644 index 0000000..439358c --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-self-awareness.md @@ -0,0 +1,198 @@ +--- +name: "stoic-self-awareness" +description: "Applies Stoic practices of self-examination to entrepreneurial leadership, drawing on Seneca's evening review, Epictetus's teaching on honest self-assessment, and Marcus Aurelius's private journaling discipline. Covers blind spots, the gap between self-image and reality, integration of character, and continuous philosophical self-scrutiny. Use when suspecting blind spots in leadership, receiving feedback that contradicts self-image, seeking a structured introspection practice, struggling with integrity under pressure, or building habits of ongoing self-examination." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - self-awareness + - self-examination + - evening-review + - blind-spots + - integrity + - seneca + - marcus-aurelius + - journaling +related_skills: + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-unbiased-thought + - leader-self-reflection + - johari-window + - learning-from-failure + - psychological-safety +author: "Fatih Guner" +--- + +# Stoic Self-Awareness + +Seneca reviewed his entire day every evening before sleep -- most modern leaders haven't examined a single day this year. That asymmetry explains a great deal about why ancient philosophers who governed empires and survived exile seem, across the centuries, to have possessed greater equanimity than contemporary executives armed with executive coaches, wellness apps, and retreats in Sedona. The Stoics treated self-awareness not as a personality trait or a luxury of the contemplative life but as a discipline -- something practised with the regularity and rigour of physical training. "I will keep constant watch over myself," Seneca writes, "and -- most usefully -- will put each day up for review. For this is what makes us evil -- that none of us looks back upon our own lives." + +--- + +## The Framework + +### The Evening Review: Seneca's Core Practice + +In a letter to his brother Novatus, Seneca describes the habit he borrowed from the Pythagorean tradition and refined for Stoic purposes. Each night, after his wife had gone to sleep, he would conduct a systematic audit of the day. Three questions structured the exercise: + +1. **What bad habit did I curb today?** +2. **How am I better?** +3. **Were my actions just?** + +The critical feature of this practice is its tone. Seneca is explicit that the review is not self-flagellation. "I conceal nothing from myself, I pass over nothing," he writes, but "what need I fear from my own mistakes, when I can say: See that you don't do that anymore. I forgive you this time." The evening review is forensic, not punitive. It seeks understanding, not guilt. For the entrepreneur, this distinction is essential: the review that spirals into shame is worse than no review at all, because it teaches the mind to avoid introspection. + +### Honest Self-Assessment: The Dual Failure + +Seneca identifies what might be called the dual failure of self-knowledge: "Above all, it is necessary for a person to have a true self-estimate, for we commonly think we can do more than we really can." Goethe later expanded the insight: it is equally damaging to see yourself as more than you are and to value yourself at less than your true worth. + +Entrepreneurs are particularly susceptible to both errors, often simultaneously. The founder who dramatically overestimates product-market fit may simultaneously underestimate her capacity to navigate a pivot. The CEO who believes he is an excellent communicator (overestimate) may not realise how well he handles crisis management (underestimate). The Stoic corrective is not modesty or confidence but *accuracy* -- the relentless pursuit of a self-image that matches reality. + +### The Gap Between Self-Image and Behaviour + +Epictetus delivers one of Stoicism's most uncomfortable observations: "You must be a unified human being, either good or bad. You must diligently work either on your own reasoning or on things out of your control -- take great care with the inside and not what's outside, which is to say, stand with the philosopher, or else with the mob." The implication is that most people live in a state of internal division -- professing values they do not practise, believing themselves to be one kind of person while behaving as another. + +This (dis)integration is not hypocrisy in the theatrical sense. It is the natural consequence of insufficient self-examination. The founder who values transparency but avoids difficult conversations is not lying; she has simply never noticed the contradiction. The CEO who prizes innovation but punishes failure has never examined the gap between his stated and revealed preferences. Awareness of these gaps -- achieved through the disciplined practices outlined below -- is the prerequisite for closing them. + +### The Role of External Mirrors + +"Find yourself a Cato," Seneca advises -- a person of such character that their imagined presence regulates your behaviour. Adam Smith later developed a similar concept, the "impartial spectator," an internalised observer who judges our conduct from a position of disinterested wisdom. + +The practice has both internal and external dimensions. Internally, the entrepreneur asks: "If the person I most respect were watching, would I still make this choice?" Externally, the entrepreneur cultivates relationships with people who will tell the truth -- not flatterers, not sycophants, but what Epictetus would call philosophical sparring partners. Marcus Aurelius opens the *Meditations* with an extraordinary catalogue of gratitude, thanking by name every person who taught him something about his own character: from his mother, he learned generosity; from his adoptive father, steadiness; from Rusticus, the habit of deep reading and honest self-correction. + +### Freedom Through Awareness + +The Stoics draw a direct line from self-awareness to freedom. "The person is free who lives as they wish," Epictetus writes, "neither compelled, nor hindered, nor limited." But he immediately adds the corollary: "Who wishes to live in deception -- tripped up, mistaken, undisciplined, complaining, in a rut? No one." Freedom, in the Stoic framework, is impossible without self-knowledge, because you cannot choose well if you do not know what drives your choices. + +Seneca reinforces this with a practical example: many people are slaves to obligations they never examined, to habits they never questioned, to relationships they maintain out of inertia. "No slavery is more disgraceful than one which is self-imposed." The self-aware entrepreneur, by contrast, periodically inventories obligations and asks which are genuinely necessary, which are self-imposed, and which exist only because no one ever stopped to question them. + +Marcus Aurelius adds a further dimension: you are a product of your training, and your training is a product of your awareness. "A dog that's allowed to chase cars will chase cars. A child who is never given any boundaries will become spoiled." The implication for founders is direct. Every unexamined habit, every unquestioned assumption, every avoided confrontation is training -- training yourself to be a particular kind of leader, whether or not you intended it. Self-awareness is the mechanism by which you choose your training deliberately rather than absorbing it by default. + +--- + +## Prompts + +**Prompt 1 -- Evening Review Protocol:** +> Guide me through Seneca's evening review for today as CEO of [company]. Ask me Seneca's three questions (What bad habit did I curb? How am I better? Were my actions just?) and then probe deeper: Where did I act from principle versus impulse? Where did my behaviour contradict my stated values? What pattern do I see emerging across recent days? Maintain a forensic, non-punitive tone throughout. + +**Prompt 2 -- Self-Image Accuracy Test:** +> Help me conduct an honest self-assessment as a leader. I'll describe how I see myself across five dimensions: [communication, decision-making, emotional regulation, strategic thinking, people management]. For each, challenge my self-assessment by asking what evidence supports it, what contradictory evidence I might be ignoring, and what my direct reports would likely say if guaranteed anonymity. Identify the probable gaps between self-image and reality. + +**Prompt 3 -- Blind Spot Excavation:** +> Based on the following description of my leadership style and recent decisions at [company], identify probable blind spots I am not seeing. Apply the Stoic principle that self-deception is "the most hostile" enemy of knowledge. Look for patterns of avoidance, contradictions between stated and revealed preferences, and areas where my reasoning may be serving my ego rather than the business. Present findings with compassion but without softening. + +**Prompt 4 -- Obligation Inventory:** +> List all my current professional and personal obligations. For each, apply the Stoic freedom audit: Is this genuinely necessary? Is this self-imposed? Am I maintaining this out of habit, guilt, vanity, or fear? What would happen if I stopped? Recommend which obligations to release, renegotiate, or reaffirm, and calculate the time and mental energy recovered. + +--- + +## Use Cases + +**Validation-stage founder receiving contradictory feedback** + +A B2B founder at the validation stage considers himself an excellent listener -- his self-narrative includes "I'm always open to feedback." When three separate pilot customers raise the same usability concern, he unconsciously reframes each as an edge case. Only when his co-founder confronts him with the pattern does he recognise the gap between self-image ("I listen") and behaviour ("I explain away"). A structured Stoic self-assessment reveals that his identity is overly fused with the product design, making any criticism of the product feel like criticism of himself. The evening review practice, adopted daily, begins to surface this pattern in real time rather than retrospectively. + +**Growth-stage CEO discovering a values contradiction** + +A Series A CEO publicly champions a culture of radical transparency. She holds all-hands meetings, publishes company financials internally, and encourages direct feedback. A 360-degree review reveals, however, that her direct reports experience her as defensive when challenged and subtly retaliatory when contradicted. The gap between stated value (transparency) and revealed behaviour (defensiveness) has been invisible to her precisely because she never examined it. The Stoic framework provides the tool: Epictetus's insistence on internal integration means that the CEO must either change the behaviour to match the value or honestly revise the value. Both are acceptable. Living in the gap is not. + +**Scale-stage executive losing touch with ground truth** + +A C-suite executive at a late-stage company has spent three years receiving filtered information from increasingly large layers of management. Seneca's warning about self-imposed slavery manifests here as slavery to a curated version of reality. The executive believes morale is strong because the metrics he sees are selected for optimism. The Stoic "find yourself a Cato" practice provides the intervention: he identifies two people in the organisation -- one junior, one lateral -- who are constitutionally incapable of flattery, and establishes regular, unstructured conversations with them. Within a month, his understanding of the company's actual condition has materially shifted. + +--- + +## Anti-Patterns + +**1. Turning the evening review into self-punishment.** Seneca's practice is diagnostic, not penal. "I forgive you this time" is an essential part of the protocol. Founders prone to perfectionism or imposter syndrome may weaponise self-examination against themselves, which defeats the purpose entirely. The review should leave you clearer, not smaller. + +**2. Substituting self-awareness tools for self-awareness.** Personality assessments (Myers-Briggs, Enneagram, StrengthsFinder) can catalyse self-reflection, but they can also replace it. Knowing your "type" is not the same as knowing yourself. The Stoic practice requires ongoing, unmediated self-confrontation -- not a label applied once and referenced forever. + +**3. Performing vulnerability as a substitute for doing the work.** Contemporary leadership culture celebrates vulnerability, which is admirable. But saying "I'm working on my blind spots" in a team meeting is not the same as actually working on your blind spots. The Stoic practice is private and rigorous. Marcus Aurelius never intended his *Meditations* for publication. The work is for you, not for your audience. + +**4. Examining only failures.** The evening review is equally concerned with strengths. Epictetus's question "How am I better?" demands that you recognise genuine progress. Founders who review only mistakes develop a distorted self-image in the opposite direction -- seeing themselves as perpetually deficient. + +**5. Seeking awareness without seeking change.** Self-knowledge is necessary but not sufficient. Identifying a blind spot and then continuing to act as though it doesn't exist is worse than never having seen it, because now the self-deception is deliberate. Awareness obligates action. + +**6. Confining self-examination to moments of crisis.** The evening review is a daily practice, not an emergency protocol. Founders who examine themselves only after a catastrophe -- a failed round, a co-founder departure, a public embarrassment -- are practising forensic investigation, not self-awareness. The Stoic discipline is prophylactic: it surfaces small misalignments before they compound into large ones. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Examining motivations and founder-idea fit | Honest assessment of why you're pursuing this venture -- passion, escapism, ego, genuine conviction -- shapes everything that follows | +| Validation | Separating identity from hypothesis | The ability to see negative experimental results clearly, without the distortion of ego, is the difference between a pivot and a delusion | +| Early Traction | Recognising emerging leadership patterns | As the team grows from 2 to 20, your leadership habits crystallise; self-examination now prevents dysfunctional patterns from becoming permanent | +| Growth | Auditing the gap between culture rhetoric and culture reality | At this stage, the CEO's unexamined behaviours have become organisational norms; the evening review must extend to institutional self-awareness | +| Scale | Resisting the information cocoon | Power insulates leaders from honest feedback; Stoic self-awareness practices must be deliberately maintained against the structural forces that erode them | + +The idea stage presents the purest test of self-awareness: why are you doing this? Seneca's question "Were my actions just?" becomes "Are my motivations honest?" The founder who starts a company to escape a bad job, to impress a parent, or to prove a point to a former employer is not inherently wrong -- but they will make very different decisions than the founder driven by a genuine problem they want to solve. Self-awareness at the idea stage is about knowing which founder you actually are. + +At early traction, the founder's leadership habits begin to solidify into patterns -- and those patterns, for better or worse, become the template for the company's culture. The evening review serves a dual purpose at this stage: it is both personal self-improvement and organisational design. The founder who notices, through nightly reflection, that she avoids giving critical feedback is catching a cultural defect before it becomes structural. The one who notices that he consistently prioritises product over people is seeing the early architecture of a dysfunction that will be vastly more expensive to repair at fifty employees than at ten. + +At scale, self-awareness becomes an institutional survival skill. The CEO of a five-hundred-person company who does not practise rigorous self-examination will inevitably become surrounded by people who tell them what they want to hear. Every layer of management is a filter; every success reinforces the belief that the current approach is correct. Only the daily discipline of questioning oneself -- Seneca's nightly audit, Marcus's private journaling -- provides a counterweight to the structural forces that make self-deception at scale nearly automatic. The Stoic practice at this stage is less about personal psychology and more about epistemological hygiene: how do I know what I think I know, and what systems have I built to ensure that my self-image stays tethered to reality? + +--- + +## Output Template + +```markdown +# Stoic Self-Awareness Review -- [Period] + +**Date:** [Date] +**Review scope:** [Daily / Weekly / Monthly] + +## Seneca's Evening Review + +### What bad habit did I curb? +[Specific habit and the situation in which you curbed it] + +### How am I better? +[Genuine progress observed -- not flattery, not false modesty] + +### Were my actions just? +[Honest assessment of alignment between principles and behaviour] + +## Self-Image Accuracy Audit + +| Dimension | How I See Myself | Probable Reality (based on evidence) | Gap | +|-----------|-----------------|--------------------------------------|-----| +| [e.g., Communication] | [Self-assessment] | [What behaviour and feedback suggest] | [Size and nature of gap] | + +## Blind Spots Identified +1. [Blind spot] -- Evidence: [What led to this recognition] +2. [Blind spot] -- Evidence: [What led to this recognition] + +## Obligation Inventory + +| Obligation | Genuinely Necessary? | Self-Imposed? | Action | +|-----------|---------------------|---------------|--------| +| [Obligation] | [Yes/No] | [Yes/No] | [Keep / Release / Renegotiate] | + +## Integration Check +- **Stated value vs. revealed behaviour gap:** [Describe any contradiction identified] +- **Corrective action:** [Specific step to close the gap] + +## This Week's Cato +[Name the person whose imagined or actual judgment you will use as a mirror this week] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](stoic-control-and-clarity.md)** -- Self-awareness reveals which aspects of your situation are genuinely within your control; without it, the dichotomy is applied to a distorted map. +- **[Stoic Emotional Mastery](stoic-emotional-mastery.md)** -- The evening review frequently surfaces emotional patterns that require the reframing techniques of Stoic emotional practice. +- **[Stoic Unbiased Thought](stoic-unbiased-thought.md)** -- Self-deception is the enemy of objective perception; the two practices are mutually reinforcing. +- **[Leader Self-Reflection](../leadership/leader-self-reflection.md)** -- Structured introspection practices that complement the Stoic philosophical framework; the former provides techniques, the latter provides the underlying worldview. +- **[Johari Window](../frameworks/johari-window.md)** -- A model for understanding blind spots and hidden selves that maps naturally onto the Stoic emphasis on the gap between self-image and reality. +- **[Creative Perception and Awareness](../creative/creative-perception-and-awareness.md)** -- Stoic self-examination operates through rational inquiry while creative awareness operates through perceptual sensitivity; the two are complementary paradigms for deepening self-knowledge. diff --git a/plugins/foreman/content/skills/stoic/stoic-unbiased-thought.md b/plugins/foreman/content/skills/stoic/stoic-unbiased-thought.md new file mode 100644 index 0000000..ee9e8f8 --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-unbiased-thought.md @@ -0,0 +1,214 @@ +--- +name: "stoic-unbiased-thought" +description: "Applies the Stoic discipline of objective perception to entrepreneurial thinking, drawing on Marcus Aurelius's practice of describing things in their simplest terms, the 'view from above' technique, and the Stoic method of stripping value judgments from events. Covers cognitive distortions through a Stoic lens, the difference between observation and interpretation, and the practice of seeing things as they are. Use when distorted thinking is driving poor decisions, when hype or panic is clouding judgment, when strong opinions need stress-testing, or when seeking objectivity amid emotionally charged situations." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - objectivity + - perception + - cognitive-distortion + - judgment + - view-from-above + - marcus-aurelius + - epictetus + - critical-thinking +related_skills: + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-self-awareness + - thinking-fast-and-slow + - black-swans + - vuca-framework + - strategic-thinking-and-alignment +author: "Fatih Guner" +--- + +# Stoic Unbiased Thought + +Every event is neutral -- what makes it good or bad is the colour of the lens through which you perceive it. Marcus Aurelius, who had more reason than most to see the world as either magnificent or terrible, spent years training himself to do neither. Instead, he practised a form of radical descriptive simplicity: wine is "old grape juice," imperial purple robes are "sheep's wool dyed in shellfish blood," sex is "rubbing and a spasmic discharge." The exercise sounds almost comically reductive, and that is precisely the point. By stripping objects and events of the value judgments we habitually attach to them, the Stoics revealed a startling truth: most of what we believe about the world is not observation but interpretation -- and interpretation, unlike observation, can be trained, corrected, and improved. + +--- + +## The Framework + +### The Perceiving Eye and the Observing Eye + +The Japanese swordsman Miyamoto Musashi distinguished between the "perceiving eye" and the "observing eye." The observing eye sees what is. The perceiving eye sees what things supposedly mean. Marcus Aurelius, writing centuries earlier in a different civilisation, arrived at the same insight: "It isn't events themselves that disturb people, but only their judgments about them." + +This distinction has direct operational consequences for entrepreneurs: + +| Observing Eye | Perceiving Eye | +|---|---| +| Revenue declined 12% this quarter | We're failing | +| A key engineer gave notice | He's betraying us | +| The board asked for a revised forecast | They've lost confidence in me | +| A competitor raised a large round | We're going to be crushed | + +The left column is data. The right column is narrative -- and narrative, once it takes hold, shapes every subsequent decision. The Stoic practice of unbiased thought is the systematic effort to operate from the left column before permitting the right one any influence. + +### Contemptuous Expressions: Radical Simplification + +Marcus Aurelius developed a technique that Stoic scholars call *contemptuous expressions* -- deliberately describing prized or feared things in their most basic, physical terms. This is not cynicism; it is a cognitive counterweight to the mind's tendency to inflate or catastrophise. + +Applied to entrepreneurial contexts, the practice yields clarity: + +- A funding round is "other people agreeing to exchange their money for a percentage of future uncertain value" +- A product launch is "making a thing available and seeing if people want it" +- A keynote speech is "one person talking to many people sitting in chairs" +- An acquisition offer is "someone proposing to buy the output of your work for a specific price" + +None of these reductions are false. They are merely the same events, seen without the distortion of status, fear, desire, or self-importance. And from that vantage point, decision-making improves markedly -- because the decisions are about the thing itself, not about the story wrapped around it. + +### The View from Above + +Marcus Aurelius repeatedly practised what scholars call the "view from above" -- a mental exercise in which you imagine seeing your current situation from an increasingly elevated perspective. First, see the room you're in. Then the building. The city. The country. The Earth, spinning in space. At each level, the matters that consumed you a moment ago diminish in proportion to the vastness you're now perceiving. + +"Watch the stars in their courses," Marcus writes, "and imagine yourself running alongside them. Think constantly on the changes of the elements into each other, for such thoughts wash away the dust of earthly life." + +This is not nihilism. The view from above does not negate the importance of your work. It recalibrates it. The lost deal, the difficult board meeting, the competitive threat -- all remain real and worth addressing. But they are no longer cosmically significant events that justify panic, despair, or the abandonment of principle. They are dust, and dust can be dealt with calmly. + +### Testing Impressions: The Stoic Verification Protocol + +Epictetus provides the most explicit protocol for challenging one's own perceptions: "From the very beginning, make it your practice to say to every harsh impression, 'you are an impression and not at all what you appear to be.' Next, examine and test it." + +The testing process involves three questions: + +**1. Is this impression about something within my control?** If not, the emotional charge attached to it is, by definition, misplaced. + +**2. Is the judgment I've attached to this event the only possible interpretation?** The Stoics recognised that the same event can support radically different narratives. A customer churning can be "evidence of product failure" or "useful data about market fit." An investor passing can be "rejection" or "misalignment that saves both parties time." + +**3. Would a wise person -- my Cato, my impartial spectator -- share this judgment?** If the answer is uncertain, the judgment warrants revision before action. + +### Opinions as Voluntary Additions + +"We have the power to hold no opinion about a thing and to not let it upset our state of mind," Marcus observes, "for things have no natural power to shape our judgments." This is among the most counterintuitive claims in Stoic philosophy. Surely some things are objectively bad? The Stoics would answer: things are objectively inconvenient, painful, or unpleasant. But "bad" is a layer we add -- and we have the power not to add it. + +For entrepreneurs, this practice manifests as the discipline of delayed interpretation. When information arrives -- a metric, an email, a market signal -- the unbiased thinker receives the data and resists the immediate impulse to assign it a value. Is this good news or bad news? Perhaps it is simply news. The interpretive layer can be added later, after analysis, after consultation, after the emotional charge of the moment has dissipated. The Stoics did not claim this was easy. They claimed it was possible, and that the difference between practising it and not practising it was the difference between clarity and confusion. + +### The War Within: Conflicting Judgments + +Seneca warns that "circumstances are what deceive us" because "we embrace evil before good" and "our prayers are at war with our prayers." The entrepreneur who wants sustainable growth but chases vanity metrics, who values work-life balance but never leaves the office, who prizes culture but tolerates toxic high performers -- these are all examples of what Seneca calls internal warfare. The biases are not external. They are contradictions in the entrepreneur's own system of judgments. + +Unbiased thought, in the Stoic sense, begins with recognising that these contradictions exist and tracing them to their source: usually a judgment accepted without examination, an opinion inherited from culture or convention, or a desire masquerading as a principle. + +--- + +## Prompts + +**Prompt 1 -- Contemptuous Expressions Exercise:** +> Take the following list of things I'm currently preoccupied with as founder of [company]: [list concerns]. For each, apply Marcus Aurelius's contemptuous expressions technique -- describe it in the simplest, most physically literal terms possible, stripped of all status, emotion, and narrative. Then assess: does the simplified description change how urgent or important this concern actually is? + +**Prompt 2 -- Judgment Stripping:** +> I've just received this news about my business: [describe event]. Before I react, help me separate observation from interpretation. State the raw facts with zero value judgment. Then list three to five different interpretations of the same facts, ranging from catastrophic to neutral to opportunistic. For each interpretation, identify the assumption that makes it seem plausible. Which interpretation is best supported by the available evidence? + +**Prompt 3 -- View from Above:** +> I'm deeply stressed about [situation] at [company]. Walk me through Marcus Aurelius's "view from above" exercise. Start with the immediate situation, then progressively zoom out -- to the industry, to the economy, to the arc of business history, to the timescale of human civilisation. At each level, reassess the situation's actual significance. Then zoom back in and recommend what a proportionate, clear-headed response would look like. + +**Prompt 4 -- Internal Contradiction Audit:** +> Review my stated values and priorities for [company]: [list values]. Now review my actual recent decisions and time allocation: [list decisions/activities]. Apply Seneca's warning about "prayers at war with prayers" -- where do my stated values and revealed behaviour contradict each other? For each contradiction, identify the unexamined judgment or hidden desire driving the gap. + +--- + +## Use Cases + +**Idea-stage founder catastrophising about competition** + +A first-time founder discovers that two well-funded startups are building in a similar space. Her immediate perception: "The market is already saturated. I'm too late. These companies will crush me." The contemptuous expressions exercise reduces the situation to its fundamentals: "Two other groups of people are also trying to solve this problem. They have raised capital. I have not yet." Stripped of narrative, the situation is informational, not terminal. The judgment-stripping exercise yields five alternative interpretations, including "the existence of competitors validates the market" and "well-funded competitors often pursue different segments." The founder proceeds with better data and less dread. + +**Early-traction startup misreading a vanity metric** + +A consumer marketplace at early traction celebrates a spike in user registrations after a press mention. The perceiving eye sees "we're taking off." The observing eye sees "registrations increased 300% this week; we do not yet know whether these users will transact." The view from above reveals that press-driven spikes are among the most common and most misleading signals in consumer businesses -- a pattern repeated across thousands of startups over decades. The unbiased assessment preserves the team's morale (the spike is a preferred indifferent) while preventing the premature scaling decisions that frequently follow misinterpreted traction signals. + +**Growth-stage CEO receiving an acquisition offer** + +A Series B CEO receives an unsolicited acquisition offer that is "too good to ignore" -- or so it seems. Marcus Aurelius's exercise reduces the offer to its components: "A larger company proposes to pay $X for the business. The price exceeds current revenue by [multiple]. The acquirer's stated intentions are [list]. The transaction would result in [concrete personal and organisational outcomes]." With the glamour stripped away, the CEO can evaluate the offer against actual criteria -- strategic fit, team outcomes, personal goals -- rather than against the narrative of validation and success that acquisition offers inevitably carry. + +--- + +## Anti-Patterns + +**1. Using objectivity as emotional avoidance.** Stripping judgments is a cognitive practice, not an emotional bypass. The founder who describes a team member's departure as "one person choosing to work elsewhere" and then refuses to examine whether the departure reveals a leadership problem is not practising Stoic objectivity -- they are hiding behind it. The practice requires engaging with the stripped-down facts, not dismissing them. + +**2. Descending into nihilism through the view from above.** Marcus's cosmic perspective is a recalibration tool, not an argument that nothing matters. The founder who concludes "none of this matters in the grand scheme of things" and stops trying has misapplied the technique. The correct conclusion is closer to: "This matters, but not as much as my emotional reaction is telling me. I can address it with composure." + +**3. Applying contemptuous expressions to people.** Reducing objects, events, and institutions to their simplest terms is a useful cognitive tool. Reducing human beings to their simplest terms is dehumanising. Marcus Aurelius explicitly counselled compassion and kinship toward others, even difficult ones. The technique is for examining things, not diminishing people. + +**4. Demanding that others adopt your objectivity.** The Stoic practice of unbiased thought is a personal discipline. Telling a distressed colleague that "it's just an impression, not reality" is philosophically accurate and interpersonally disastrous. Apply the framework to your own perceptions. Extend empathy to others who have not yet done the same work. + +**5. Mistaking detachment for wisdom.** The Stoics were not detached. Marcus Aurelius governed an empire. Seneca navigated lethal court politics. Epictetus taught with visible passion. Unbiased thought enables better engagement with reality, not withdrawal from it. The entrepreneur who uses the framework to disengage from problems rather than see them more clearly has inverted its purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Seeing the market as it is, not as you wish it to be | The greatest perceptual risk here is confirmation bias -- interpreting ambiguous signals as validation because you want them to be | +| Validation | Receiving experimental data without distortion | Every data point must pass through the observing eye before the perceiving eye; the discipline of delayed interpretation is most critical here | +| Early Traction | Distinguishing signal from noise in early metrics | The flood of new data (users, revenue, churn, NPS) creates endless opportunities for biased interpretation; the Stoic protocol filters them systematically | +| Growth | Resisting narrative capture by success stories | At growth stage, the company's own story becomes a source of bias; "we always succeed" is as dangerous a judgment as "we're going to fail" | +| Scale | Maintaining institutional objectivity | At scale, organisational biases compound individual ones; unbiased thought must be embedded in decision processes, not just individual practice | + +At the validation stage, the Stoic discipline of unbiased thought intersects most powerfully with the scientific method. Both demand that the practitioner observe before interpreting, test before concluding, and remain willing to be proved wrong. The founder who defines falsification criteria before running an experiment -- "what specific result would cause me to abandon this hypothesis?" -- is practising exactly what Epictetus prescribes: testing impressions before assenting to them. + +At growth and scale, the primary threat to unbiased thought shifts from individual cognitive distortion to organisational narrative capture. Success creates a meta-narrative -- "we're the company that always finds a way" or "our market position is unassailable" -- and that narrative filters all subsequent information. The Stoic view from above provides the institutional corrective: periodically lifting the organisation's perspective above its own story to see the broader competitive, economic, and historical context in which it operates. + +--- + +## Output Template + +```markdown +# Unbiased Thought Assessment -- [Decision/Situation] + +**Date:** [Date] +**Context:** [Brief description of the situation requiring objective analysis] + +## Observation vs. Interpretation + +| Raw Observation (Observing Eye) | Current Interpretation (Perceiving Eye) | Alternative Interpretations | +|--------------------------------|----------------------------------------|----------------------------| +| [Fact 1] | [Current judgment] | [2-3 alternative readings] | +| [Fact 2] | [Current judgment] | [2-3 alternative readings] | + +## Contemptuous Expressions Reduction +- **Situation as commonly described:** [How you/others currently frame it] +- **Situation in simplest physical terms:** [Stripped of narrative, status, emotion] +- **What changes in your assessment:** [Specific shift in perceived urgency/importance] + +## Impression Test (Epictetus Protocol) + +| Impression | Within My Control? | Judgment Attached | Judgment Supported by Evidence? | Verdict | +|-----------|-------------------|-------------------|--------------------------------|---------| +| [Impression 1] | [Y/N] | [What I think it means] | [Y/N -- cite evidence] | [Retain / Revise / Reject] | + +## View from Above +- **Immediate significance:** [How it feels right now] +- **Industry-level significance:** [How common is this pattern?] +- **Historical significance:** [Has this type of situation been resolved before?] +- **Proportionate response:** [What a clear-headed response looks like at the right scale] + +## Internal Contradiction Check +- **Stated value/priority:** [What I say I care about] +- **Revealed behaviour:** [What my actions actually show] +- **Root judgment driving the gap:** [The unexamined belief] +- **Resolution:** [Change the behaviour or revise the value] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](stoic-control-and-clarity.md)** -- The dichotomy of control is the first filter in the impression-testing protocol; unbiased thought depends on it as a prerequisite. +- **[Stoic Emotional Mastery](stoic-emotional-mastery.md)** -- Emotions distort perception; the emotional mastery practices clear the lens through which unbiased thought operates. +- **[Stoic Self-Awareness](stoic-self-awareness.md)** -- Self-deception is the most persistent source of biased perception; self-awareness practices reveal the internal contradictions that distort judgment. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's bias catalogue provides the empirical evidence for what the Stoics intuited: that human perception is systematically unreliable and requires structural correction. +- **[Black Swans](../frameworks/black-swans.md)** -- Taleb's work on narrative fallacy and the limits of prediction shares the Stoic suspicion of our tendency to see patterns where none exist. +- **[Enemies of Clear Thinking](../thinking/enemies-of-clear-thinking.md)** -- The Clear Thinking framework's four biological defaults (ego, emotion, inertia, social) are the modern behavioural catalogue of the distortions the Stoics addressed through the impression-testing protocol. diff --git a/plugins/foreman/content/skills/stoic/stoic-virtue-and-kindness.md b/plugins/foreman/content/skills/stoic/stoic-virtue-and-kindness.md new file mode 100644 index 0000000..10f279d --- /dev/null +++ b/plugins/foreman/content/skills/stoic/stoic-virtue-and-kindness.md @@ -0,0 +1,201 @@ +--- +name: "stoic-virtue-and-kindness" +description: "Presents the Stoic argument that character is the ultimate competitive advantage and that virtue -- encompassing honesty, kindness, justice, and moral courage -- is not a means to success but constitutes success itself. Use when an entrepreneur faces ethical dilemmas, when competitive pressure tempts shortcuts, when building company culture around values rather than metrics, when kindness is dismissed as weakness in a high-stakes environment, or when seeking philosophical grounding for why doing right and doing well are the same endeavour." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - virtue + - kindness + - character + - ethics + - moral-courage + - honesty + - forgiveness + - integrity + - stoic + - values +related_skills: + - stoic-fortitude-and-resilience + - stoic-acceptance-amor-fati + - trust-equation + - psychological-safety + - emotional-intelligence +author: "Fatih Guner" +--- + +# Stoic Virtue and Kindness + +CHARACTER TAX. There is a cost to being virtuous, and the Stoics never pretended otherwise. Virtue is not free. It demands a daily tax paid in effort, restraint, and the willingness to forgo easier paths. Seneca gave up a fortune trying to extract himself from Nero's court. Marcus Aurelius spent his final years on cold military frontiers when he could have remained in Roman luxury. Epictetus endured slavery and a crippled leg without surrendering his philosophical commitments. The return on this tax is not wealth or status -- it is character. And the Stoic claim, radical in their time and radical still, is that character is not a *means* to happiness. Character *is* happiness. Everything else the entrepreneur chases -- revenue, traction, market share -- is at best a lagging indicator of something more fundamental. + +> "Does the light of a lamp shine and keep its glow until its fuel is spent? Why shouldn't your truth, justice, and self-control shine until you are extinguished?" -- Marcus Aurelius, *Meditations* + +--- + +## The Framework + +The Stoic treatment of virtue is not a soft appeal to "being nice." It is an architectural argument: that the qualities of character -- justice, kindness, honesty, courage, self-control -- form the load-bearing structure on which every other entrepreneurial achievement depends. Remove them, and the edifice collapses, regardless of how impressive it looks from outside. + +### The Four Cardinal Virtues in Entrepreneurial Context + +The Stoics organised virtue into four categories, each mapping to a distinct entrepreneurial discipline. + +**Wisdom (Sophia)** -- The capacity to distinguish what is within one's control from what is not, and to allocate attention accordingly. In business terms: strategic clarity. The wise entrepreneur does not waste resources fighting uncontrollable market forces; they position the company to benefit from them. + +**Justice (Dikaiosyne)** -- Right action toward others. For the Stoic, this was not legalistic compliance but a genuine orientation toward the common good. Marcus Aurelius compressed it into a single maxim: "That which isn't good for the hive, isn't good for the bee." The entrepreneur who extracts value from employees, customers, or partners while contributing nothing in return violates this principle -- and the violation, the Stoics would argue, harms the entrepreneur more than anyone else. + +**Courage (Andreia)** -- Not physical bravery but moral courage: the willingness to do what is right despite personal cost. Courage is the virtue that makes the other three operational. Without it, wisdom remains theoretical, justice remains aspirational, and self-control collapses under pressure. + +**Temperance (Sophrosyne)** -- Self-control, moderation, and the discipline to resist excess. For the entrepreneur surrounded by venture capital, growth metrics, and the intoxicating narrative of "disruption," temperance is the corrective that prevents ambition from becoming recklessness. + +### Kindness as Strength + +The business world frequently treats kindness as a liability -- a quality tolerated in HR departments but inappropriate for strategy rooms. The Stoics held the opposite view. + +> "A benefit should be kept like a buried treasure, only to be dug up in necessity. Wherever there is a human being, we have an opportunity for kindness." -- Seneca, *On the Happy Life* + +Kindness, in Stoic thought, is not sentimentality. It is the practical expression of the recognition that human beings are mutually interdependent. Marcus Aurelius repeated this theme relentlessly: "We are like many pellets of incense falling on the same altar." The entrepreneur who grasps this -- who treats employees, customers, and even competitors as interconnected participants in a shared system -- builds structural advantages that purely transactional operators cannot replicate. Trust compounds. Goodwill compounds. Reputation compounds. Ruthlessness does not. + +### Honesty as Default Setting + +> "The straightforward and good person should be like a smelly goat -- you know when they are in the room with you." -- Marcus Aurelius, *Meditations* + +Marcus's analogy is deliberately unglamorous. Honesty should not require announcement. The entrepreneur who prefaces statements with "I'll be honest with you" invites the question: what were you being before? Stoic honesty is not radical candour performed for effect. It is a default orientation -- so habitual that it requires no signalling. + +### The Self-Inflicted Wound of Wrongdoing + +> "The person who does wrong, does wrong to themselves. The unjust person is unjust to themselves -- making themselves evil." -- Marcus Aurelius, *Meditations* + +The Stoic case against unethical behaviour is not primarily about consequences or reputation. It is about what wrongdoing does to the person who commits it. Every shortcut, every lie, every act of exploitation erodes the internal architecture of character. The entrepreneur who cheats a supplier does not merely risk a damaged relationship; they damage themselves. Seneca noted the grim irony: "Crimes often return to their teacher." The methods you model will eventually be used against you. + +### Character as Fate + +> "Each person acquires their own character, but their official roles are designated by chance." -- Seneca, *Moral Letters* + +Heraclitus's maxim -- "Character is fate" -- underpins the entire Stoic position on hiring, partnerships, and professional relationships. Past credentials measure fortune; character measures the person. The startup that hires on pedigree alone imports the luck of others' circumstances. The startup that hires on character imports a self-reinforcing capacity for sound judgement under pressure. Seneca advised inviting some to one's table "because they are deserving, others because they may come to deserve it." The implication is clear: character can be developed, but only if it is valued. + +### The Revenge Trap + +> "The best way to avenge yourself is to not be like that." -- Marcus Aurelius, *Meditations* + +Venture-backed competition practically begs for retaliation: a competitor copies your feature, a former employee poaches clients, a partner reneges on a deal. The instinct to hit back is powerful -- and, the Stoics argued, self-destructive. Vengeance consumes time, distorts priorities, and models exactly the behaviour it condemns. Marcus and Seneca both counselled the same response: let the wrongdoer's actions define the wrongdoer, and let your response define you. The energy spent on revenge is energy stolen from building. + +--- + +## Prompts + +**Prompt 1 -- Character Audit:** +> Assess the character infrastructure of my company. My company is [describe: stage, team size, industry]. For each of the four Stoic cardinal virtues (Wisdom, Justice, Courage, Temperance), evaluate: Where does our organisation practise this virtue well? Where do we fall short? What specific decisions or policies reveal our actual values (as opposed to our stated ones)? Identify the three highest-priority character gaps and propose concrete actions to address each. + +**Prompt 2 -- Ethical Dilemma Analysis:** +> I am facing an ethical dilemma: [describe situation -- e.g., a profitable client whose values conflict with ours, a competitive shortcut that is legal but questionable, pressure to misrepresent metrics to investors]. Apply the Stoic virtue framework: What would wisdom (clear-eyed assessment of what we control) say? What would justice (right action toward all affected parties) say? What would courage (willingness to bear personal cost) say? What would temperance (moderation and long-term thinking) say? What is the decision that I could defend to Marcus Aurelius? + +**Prompt 3 -- Kindness as Strategy:** +> Help me design a stakeholder kindness strategy for my company at [stage]. For each stakeholder group (employees, customers, suppliers, investors, community), identify: What does genuine kindness look like in our specific interactions with them? Where are we currently transactional when we could be generous? What structural changes would embed kindness into our processes rather than relying on individual goodwill? Frame each recommendation in terms of the long-term trust and reputational capital it builds. + +**Prompt 4 -- Revenge and Forgiveness Decision Tree:** +> A competitor / partner / employee has wronged us: [describe situation]. My instinct is to [describe desired response -- e.g., retaliate, cut them off, expose them publicly]. Apply Marcus Aurelius's principle: "The best way to avenge yourself is to not be like that." Walk me through: (1) What does retaliation actually cost us in time, energy, and reputation? (2) What does the wrongdoer's behaviour say about them versus about us? (3) What response would strengthen our character rather than merely punish theirs? (4) Is there a path that serves justice without descending into vengeance? + +--- + +## Use Cases + +**Early-Traction Fintech Founder Facing a Profitable but Ethically Dubious Partnership** + +A fintech startup receives a partnership offer from a payday lender that would generate significant revenue and solve the company's near-term cash-flow pressure. The partnership is legal. Many competitors have similar arrangements. But the founder knows that payday lending practices harm the underbanked population that her company was founded to serve. Applying the Stoic virtue framework, she maps the decision across all four virtues: Wisdom reveals that the partnership creates long-term brand risk that outweighs short-term revenue. Justice identifies the conflict between profiting from the same population the company claims to protect. Courage acknowledges the real financial cost of declining. Temperance counsels against letting short-term pressure override the company's founding purpose. She declines the partnership -- and uses the decision, shared transparently with her team, to reinforce the values that will guide future trade-offs. + +**Growth-Stage CEO Managing Retaliation Impulse After Employee Defection** + +A senior engineer leaves a growth-stage startup to join a direct competitor, taking proprietary knowledge of the company's technical architecture. The CEO's instinct is to pursue legal action aggressively and to make an example. Marcus Aurelius's counsel applies: "How much better to heal than seek revenge from injury. Vengeance wastes a lot of time and exposes you to many more injuries than the first that sparked it." The CEO consults counsel, secures necessary protections through appropriate legal channels, but refuses to engage in a public campaign against the former employee. The restraint preserves the company's reputation among engineering talent -- a community that talks -- and avoids the distraction that litigation inevitably produces. The best revenge is building a company the engineer regrets leaving. + +**Scale-Stage Founder Discovering Internal Fraud** + +A founder at scale discovers that a trusted VP has been inflating performance metrics to secure bonus payouts. The temptation is to handle the situation quietly to avoid board scrutiny and public embarrassment. The Stoic framework demands the opposite: honesty as default, justice toward all affected parties (including the team whose real performance was obscured), and the courage to accept the board's reaction. The founder terminates the VP, reports the situation transparently to the board, and implements controls that should have existed earlier. The short-term cost is real. The long-term signal -- that the company's values are not decorative -- is worth more. + +--- + +## Anti-Patterns + +1. **Treating virtue as a marketing strategy.** The moment kindness, honesty, or ethical behaviour is performed for brand positioning, it ceases to be virtue and becomes tactics. The Stoics were explicit: virtue is its own reward. The entrepreneur who is kind because it generates good press will abandon kindness the moment the press turns negative. + +2. **Confusing kindness with conflict avoidance.** Kindness does not mean agreeing with everyone, avoiding difficult conversations, or tolerating poor performance. Marcus Aurelius was both kind and exacting. Giving honest feedback, making hard personnel decisions, and holding high standards are all compatible with genuine kindness -- provided they are motivated by concern for the person and the organisation rather than by ego or frustration. + +3. **Selective virtue.** Being honest with investors but dishonest with employees. Being generous with customers but exploitative with suppliers. Virtue, in Stoic thought, is indivisible. Selective application is not virtue; it is calculation. + +4. **Virtue signalling without structural commitment.** Publishing a values statement on the website while maintaining incentive structures that reward the opposite behaviour. The Stoic test is not what you say but what you do -- and specifically, what you do when virtue is expensive. + +5. **Using philosophy to judge others rather than govern oneself.** Seneca warned: "When philosophy is wielded with arrogance and stubbornly, it is the cause for the ruin of many." The Stoic entrepreneur applies the virtue framework to their own decisions, not as a standard for evaluating everyone else's behaviour. Self-governance first; everything else follows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Establishing founding values as structural commitments | Values set at the idea stage become the DNA of the company. The Stoic insight: choose them based on what kind of person (and company) you want to be, not on what sounds good in a pitch deck. Write them as commitments, not aspirations. | +| Validation | Practising honesty under pressure | Validation tempts founders to present favourable interpretations of ambiguous data. The Stoic discipline of honesty -- with investors, advisors, and oneself -- ensures that validation is genuine rather than performed. | +| Early Traction | Building trust as a compounding asset | Every customer interaction, employee conversation, and partner negotiation is a deposit into or withdrawal from the trust account. At early traction, each deposit matters disproportionately. Kindness and reliability now compound into reputation later. | +| Growth | Maintaining virtue through scaling pressure | Growth introduces new ethical pressures: competitive urgency, investor expectations, the temptation to cut corners in quality or culture. The Stoic framework provides the decision-making scaffold that prevents growth from corrupting the company's character. | +| Scale | Institutionalising virtue beyond the founder | At scale, virtue cannot depend on the founder's personal character alone. It must be embedded in governance structures, incentive systems, hiring criteria, and decision-making processes. The question shifts from "Am I virtuous?" to "Is the organisation virtuous even when I am not in the room?" | + +--- + +## Output Template + +```markdown +# Character and Virtue Assessment + +**Company:** [Name] +**Stage:** [Stage] +**Prepared by:** [Name] +**Date:** [Date] + +## Cardinal Virtue Scorecard + +| Virtue | Current Practice | Gap Identified | Priority Action | +|--------|-----------------|----------------|-----------------| +| Wisdom | [How we demonstrate strategic clarity] | [Where we lack it] | [Specific action] | +| Justice | [How we treat stakeholders fairly] | [Where we fall short] | [Specific action] | +| Courage | [Where we act despite personal cost] | [Where we avoid hard choices] | [Specific action] | +| Temperance | [Where we exercise restraint] | [Where we overreach] | [Specific action] | + +## Stated vs. Revealed Values + +| Stated Value | Evidence Supporting | Evidence Contradicting | Alignment Score | +|-------------|--------------------|-----------------------|-----------------| +| [Value 1] | [Example] | [Example] | [High/Medium/Low] | +| [Value 2] | [Example] | [Example] | [High/Medium/Low] | + +## Kindness Audit + +| Stakeholder | Current Interaction Quality | Opportunity for Genuine Kindness | Expected Long-Term Return | +|------------|---------------------------|--------------------------------|--------------------------| +| Employees | [Assessment] | [Specific opportunity] | [Trust, retention, culture] | +| Customers | [Assessment] | [Specific opportunity] | [Loyalty, referrals, brand] | +| Suppliers | [Assessment] | [Specific opportunity] | [Reliability, terms, priority] | + +## Ethical Decision Pending +- **Dilemma:** [Description] +- **Wisdom says:** [Assessment] +- **Justice says:** [Assessment] +- **Courage says:** [Assessment] +- **Temperance says:** [Assessment] +- **Decision:** [Chosen course of action and rationale] +``` + +--- + +## Related Skills + +- **[Stoic Fortitude and Resilience](stoic-fortitude-and-resilience.md)** -- Fortitude provides the endurance to sustain virtue when it becomes expensive; character without strength collapses under pressure, strength without character becomes mere aggression. +- **[Trust Equation](../frameworks/trust-equation.md)** -- Virtue, in Stoic terms, is the character that makes each trust component genuine rather than performed; the trust equation quantifies what virtue produces. +- **[Psychological Safety](../frameworks/psychological-safety.md)** -- Environments where people feel safe to be honest and take risks outperform those governed by fear; virtue creates the conditions for psychological safety. +- **[Emotional Intelligence](../frameworks/emotional-intelligence.md)** -- Goleman's framework maps closely to the Stoic cardinal virtues: self-awareness parallels wisdom, empathy parallels justice, self-regulation parallels temperance. +- **[Stoic Acceptance and Amor Fati](stoic-acceptance-amor-fati.md)** -- Acceptance of fate is the soil from which virtue grows; the entrepreneur consumed by resentment cannot practise justice, wisdom, or kindness. +- **[Connecting with People](../people/connecting-with-people.md)** -- The Platinum Rule and validation techniques operationalise the Stoic virtue of kindness in daily interpersonal interactions beyond philosophical aspiration. diff --git a/plugins/foreman/content/skills/storytelling/building-story-stakes.md b/plugins/foreman/content/skills/storytelling/building-story-stakes.md new file mode 100644 index 0000000..c3c23ac --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/building-story-stakes.md @@ -0,0 +1,206 @@ +--- +name: "building-story-stakes" +description: "Teaches five named techniques for creating and sustaining narrative tension in any story. Applies when a founder needs to hold an audience's attention through a pitch, investor update, all-hands talk, or customer case study. Use when a narrative feels flat, when attention wanders mid-presentation, or when the storyteller senses the audience could walk away without consequence." +version: "1.0.0" +category: "storytelling" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - stakes + - narrative-tension + - audience-engagement + - pitching + - suspense + - persuasion + - elephant + - backpack + - breadcrumbs + - hourglass + - crystal-ball +related_skills: + - storytelling-truth-and-vividness + - emotional-impact-in-stories + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Building Story Stakes + +What keeps a listener hooked is not curiosity. It is the elephant you planted at the beginning -- the question they desperately need answered. Stakes are the gears that make stories work; without them, any narrative, however polished, becomes something an audience can take or leave. The framework identifies five discrete techniques for infusing stakes into a story, each learnable and each deployable in settings ranging from a Moth stage to a Series A pitch meeting. The entrepreneur who masters these techniques does not merely tell stories. That entrepreneur controls attention. + +--- + +## The Framework + +Stakes answer a deceptively simple question: would the audience want to hear the next sentence? If the answer is no, the story has failed -- not in content, but in architecture. These five strategies address different failure modes of attention, and they work in combination. Some stories need all five. Others, naturally loaded with drama, need only the first. The key is diagnosis: knowing which strategy a given moment demands. + +### 1. The Elephant + +Every story must have an Elephant. The Elephant is the large, obvious thing in the room -- a clear statement of the need, the want, the problem, the peril, or the mystery. It tells the audience what to expect, gives them a reason to wonder, and infuses the story with instantaneous stakes. + +The Elephant should appear within the first sixty seconds. Thirty seconds is better. Storytellers lack the luxury of trailers; when a speaker begins, the audience has no idea whether they are hearing a comedy, a tragedy, or a waste of their morning. Without an early Elephant, listeners check out. + +**The distinction matters.** Consider two openings for the same company origin story: + +- *Version A:* "Our co-founder grew up in a small town in Ohio. She studied engineering at State. She worked at three companies before starting ours." +- *Version B:* "When our co-founder was twenty-six, she bet her entire savings -- $11,400 -- on a product nobody in her industry believed would work. Our co-founder grew up in a small town in Ohio..." + +Version B has an Elephant. The character sketch that follows is identical, but now the audience carries a question: did she lose everything? + +**Elephants can change colour.** A story may begin with one apparent direction and reveal a deeper one. The pitch deck that opens with "How do we reduce churn by 40%?" may end on a far more interesting question about customer identity. The audience believes they are on one path; the storyteller reveals it was always a different, richer one. This is not bait-and-switch. The path was the same all along. Only its depth was hidden. + +### 2. The Backpack + +A Backpack loads the audience with the storyteller's hopes, fears, and plans before moving the story forward. Its purpose is twofold: make the audience wonder what will happen next, and -- more ambitiously -- make them feel something close to what the storyteller felt in the moment. + +The mechanism is plan articulation. Before a critical scene, the storyteller explains the plan in full. If the plan then fails, the audience experiences something like the same disappointment the storyteller felt. They knew the plan. They wanted it to succeed. Their shoulders slump. + +This is why heist films explain the robbery before the heist begins. Danny Ocean's crew lays out every step so that the audience becomes a member of the team. When things go wrong, the frustration is shared. + +**For entrepreneurs:** Before describing a product launch, a fundraising round, or a pivotal customer meeting, lay out the plan. Detail the strategy, the hoped-for outcome, the metrics that would signal success. Then describe what actually happened. The gap between plan and reality is where the audience lives. + +Plans that work perfectly make terrible stories. Perfect execution is the province of narcissists and thin-skinned egotists, as the framework bluntly observes. The audience wants struggle before triumph. + +### 3. Breadcrumbs + +Breadcrumbs are small hints dropped about a future event -- just enough to keep the audience guessing, never enough to let them guess correctly. The storyteller reveals one intriguing detail and withholds the rest. + +The trick is selectivity. Choose Breadcrumbs that create maximum wonder without telegraphing the outcome. They are most effective when something truly unexpected is coming. A single well-placed detail -- "and then I noticed the crumpled uniform in the backseat" -- can keep an audience leaning forward through an otherwise expository passage. + +### 4. The Hourglass + +When the audience is hanging on every word, the Hourglass says: let them hang. At the precise moment the story reaches its most anticipated beat, the storyteller slows down. Introduces unnecessary (but evocative) detail. Describes things that do not require description. Grinds the narrative to a halt. + +This feels counterintuitive. The instinct is to rush toward the payoff. Resist. The Hourglass works because the audience already wants the next sentence more than anything. Every second of delay compounds the tension. + +The technique is demonstrated by describing a McDonald's uniform in granular detail at the exact moment the audience needs to know what happens when a door opens. "Blue shirt. Blue pants. Blue tie. Gold name badge." The story has stopped. The audience cannot breathe. + +**In a pitch context:** When you reach the moment of product-market fit revelation, the first major customer win, or the turning point that changed everything -- slow down. Add sensory detail. Set the scene with physical specifics. Make the investor wait five more seconds for the number they need. + +### 5. The Crystal Ball + +A Crystal Ball is a false prediction made by the storyteller to cause the audience to wonder whether it will prove true. It exploits the human compulsion to anticipate the future. + +"I was sure the investor was going to say no. I could see it in the way he closed his notebook." This prediction -- stated explicitly -- makes the audience hold its breath. Even if the prediction is wrong (especially if it is wrong), the audience needed to find out. + +Deploy Crystal Balls when the prediction seems plausible, when the guess is reasonable, and when the predicted outcome presents an intriguing or frightening possibility. + +### The Supplementary Principle: Make the Big Story Little + +Large, dramatic events -- near-death experiences, massive failures, extraordinary successes -- are paradoxically the hardest stories to tell. The big parts are singular, unusual, and difficult to relate to. The secret: find the small, specific, personal moment hidden inside the big event. + +A story about nearly going bankrupt is not really about the bank balance. It is about the look on a co-founder's face across a kitchen table at 2 a.m. A story about closing a transformative deal is not about the contract. It is about the three-word text message sent to a spouse from a parking garage. + +Big themes land only through small, concrete details. The founder who says "we almost died as a company" connects with no one. The founder who describes eating ramen at a desk at midnight, watching the last $4,000 leave the account, and then receiving an email with a subject line that changed everything -- that founder makes the room hold its breath. + +--- + +## Prompts + +**Prompt 1 -- Elephant Identification:** +> I need to present [a pitch / an investor update / a company story] about [topic]. The key transformation or revelation is [describe it]. Help me craft an Elephant -- a clear, compelling statement of need, want, problem, or mystery -- that I can deliver within the first 30 seconds. The Elephant should make the audience desperate to hear what happens next. Also suggest how the Elephant's colour might change by the story's end. + +**Prompt 2 -- Backpack Construction:** +> I am telling the story of [a product launch / fundraising round / customer win]. Before the critical moment, I want to load my audience with my plans and hopes so they feel the weight of what follows. Help me articulate the plan, the expected outcome, and the emotional stakes in a way that makes the audience co-invest in the result. Then show me how the gap between plan and reality creates narrative tension. + +**Prompt 3 -- Full Stakes Audit:** +> Here is a narrative I plan to deliver: [paste draft or outline]. Audit it for stakes using the five techniques (Elephant, Backpack, Breadcrumbs, Hourglass, Crystal Ball). Identify where attention might wander. Recommend specific insertions of each technique at precise moments. Flag any "big story" moments that need to be made smaller and more personal. + +**Prompt 4 -- Hourglass Moment Design:** +> The climax of my story is [describe the key reveal or turning point]. Help me design an Hourglass moment around it: what sensory details can I add, what unnecessary-but-evocative description can I layer in, and how should I slow my pacing to maximise the tension just before the payoff? + +--- + +## Use Cases + +**Series A Pitch -- SaaS Founder** + +A founder pitching enterprise software opens with three minutes of product features. Attention drifts. Applying the framework: she opens with an Elephant ("Eighteen months ago, our largest customer called to say they were leaving -- and that call saved the company"). She uses a Backpack before describing the product pivot ("Our plan was simple: rebuild the entire integration layer in six weeks with a team of four"). She drops a Breadcrumb ("I still had the resignation letter in my drafts folder"). She deploys an Hourglass at the moment of product-market fit revelation, slowing down to describe the Slack message from the customer's CTO. The pitch transforms from a feature walkthrough into a story the room cannot leave. + +**All-Hands Address -- Post-Layoff** + +A CEO addresses a shaken team after a reduction in force. The big story (layoffs, financial pressure, survival risk) is inherently difficult to connect with at scale. The CEO makes it little: she describes a single conversation with a departing colleague, the specific object on his desk he packed last, and the sentence he said as he left. The Elephant is planted at the outset ("This morning I want to tell you about one conversation that changed how I think about what we owe each other"). The Crystal Ball appears mid-narrative ("I was certain he was going to be angry. I had rehearsed for anger"). The small moment carries the weight that the big narrative cannot. + +--- + +## Anti-Patterns + +- **The Missing Elephant.** Beginning a story with context, background, or credentials before establishing what is at stake. If the audience does not know why they are listening within the first minute, they have already stopped. Most failed pitches and company narratives suffer from this structural defect. + +- **The Perfect Plan.** Describing a strategy that executed flawlessly. The Backpack technique only works when the plan encounters friction. Audiences want suffering before triumph. A founder who describes a seamless journey from idea to traction sounds either dishonest or uninteresting. + +- **Rushing the Hourglass.** Sprinting through the most anticipated moment because the storyteller is eager to deliver the payoff. The payoff gains its power from delay. Rushing it is the narrative equivalent of lighting a firework indoors. + +- **Stacking Stakes Without Resolution.** Deploying Breadcrumbs, Crystal Balls, and Backpacks in rapid succession without ever paying them off. Each technique creates a promise to the audience. Broken promises erode trust faster than absent stakes erode attention. + +- **Confusing Big with Compelling.** Assuming that dramatic events automatically make good stories. The founder who says "we nearly went bankrupt" without finding the small, human, relatable moment inside the crisis tells a story nobody can connect to. Grand scale is not a substitute for personal specificity. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The Elephant is existential: does this problem matter? | Stakes must be borrowed from the customer's pain, since the company has no history to draw from yet | +| Validation | Backpacks and Crystal Balls dominate: plans are made, predictions tested | The narrative tension lives in the gap between hypothesis and evidence | +| Early Traction | Breadcrumbs become available as real customer stories accumulate | The storyteller can now hint at outcomes before revealing them, because outcomes exist | +| Growth | The Hourglass becomes critical for investor narratives and team alignment | Audiences are sophisticated; they need to be slowed down at key moments, not sped through them | +| Scale | Elephants must change colour: the company's story is no longer what it appears | The most powerful narratives at scale reveal that the real stakes were always something deeper than revenue | + +At the idea stage, founders frequently attempt to manufacture stakes through hyperbole ("This is a trillion-dollar market"). Manufactured stakes are transparent and counterproductive. Genuine stakes at this stage come from the founder's personal connection to the problem -- the small story hidden inside the big ambition. + +--- + +## Output Template + +```markdown +# Narrative Stakes Worksheet + +## Story Summary +[One sentence describing the story you intend to tell] + +## The Elephant +- **Core question planted for the audience:** [What need / want / problem / mystery?] +- **Appears by second:** [Target: within 30 seconds] +- **Colour change (if any):** [What the story appears to be about vs. what it is really about] + +## Backpack Moment(s) +- **Plan articulated before scene [X]:** [Describe the plan and hoped-for outcome] +- **Actual result:** [What happened instead] +- **Emotional gap:** [What the audience should feel] + +## Breadcrumbs +- **Hint dropped at [moment]:** [The detail revealed] +- **What it foreshadows:** [What the audience cannot yet guess] + +## Hourglass Moment +- **Scene to slow down:** [The most anticipated beat] +- **Details to add:** [Sensory, environmental, physical specifics] +- **Duration of delay:** [How many additional seconds / sentences] + +## Crystal Ball +- **False prediction stated at [moment]:** [What the storyteller expected] +- **Actual outcome:** [What happened instead] + +## Big-to-Little Check +- **The big event:** [What happened at macro level] +- **The small moment inside it:** [The specific, personal, relatable detail] +``` + +--- + +## Related Skills + +- **[Storytelling Truth and Vividness](storytelling-truth-and-vividness.md)** -- Stakes lose their power if the audience cannot see the story; vividness techniques ensure the Hourglass and Breadcrumbs land in a cinematic mental image. +- **[Emotional Impact in Stories](emotional-impact-in-stories.md)** -- Stakes create tension; emotional impact techniques convert that tension into tears, laughter, or action at the moment of release. +- **[Story Performance and Delivery](story-performance-and-delivery.md)** -- Written stakes must be performed: pacing, tense shifts, and vocal control determine whether an Hourglass moment actually slows the room. +- **[Story Structure and Arc](story-structure-and-arc.md)** -- The five-second moment provides the target that stakes build toward; without clear structure, even well-crafted stakes dissipate before the payoff. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- The leadership-application counterpart; focuses on when and why leaders deploy stories, whereas this skill addresses the craft of making them hold attention. +- **[Writing for Response](../writing/writing-for-response.md)** -- The Breadcrumbs technique for maintaining audience attention operates on the same cognitive principle as friction reduction in written calls to action: keep the reader moving forward. diff --git a/plugins/foreman/content/skills/storytelling/emotional-impact-in-stories.md b/plugins/foreman/content/skills/storytelling/emotional-impact-in-stories.md new file mode 100644 index 0000000..f93815b --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/emotional-impact-in-stories.md @@ -0,0 +1,229 @@ +--- +name: "emotional-impact-in-stories" +description: "Explains the singular mechanism for making audiences cry (surprise, not sadness) and two named techniques for making them laugh (Milk Cans and Baseballs, Babies and Blenders). Applies when a founder is crafting a keynote, investor narrative, brand story, or any communication designed to move an audience emotionally. Use when a story feels informative but flat, when humour falls short, or when a narrative needs to land in the heart rather than the head." +version: "1.0.0" +category: "storytelling" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - emotion + - surprise + - humour + - crying + - laughter + - milk-cans-and-baseballs + - babies-and-blenders + - contrast + - pitching + - brand-narrative +related_skills: + - building-story-stakes + - storytelling-truth-and-vividness + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Emotional Impact in Stories + +There is exactly one way to make someone cry -- and it is not sadness. It is surprise. The framework argues this with the conviction of a principle tested in front of thousands of audiences: tears are not produced by tragic content. They are produced by unexpected reveals, unanticipated connections, and the sudden inversion of the emotional expectation the storyteller has carefully constructed. The same principle governs laughter. Every emotional response in storytelling -- tears, anger, joy, outrage -- traces back to a well-cultivated surprise. The entrepreneur who understands this mechanism holds a tool more powerful than any slide deck: the ability to make a room feel something it did not expect to feel. + +--- + +## The Framework + +### Part I: The Mechanics of Tears + +In life, many things provoke tears: grief, pain, overwhelming love, exhaustion. Storytellers have access to none of these. They cannot cause physical pain or recreate years of accumulated loss. All they have is words, deployed in sequence. The only emotional lever available is surprise. + +The principle is demonstrated through the story "This Is Going to Suck," in which the storyteller dies briefly after a head-on collision. Audiences wince at the violence. They groan at the description of teeth knocked loose and legs embedded in metal. But nobody cries at the accident. Despite its brutality, the collision is expected -- the audience was told it was coming. + +They cry later, when they learn that teenage friends have filled the hospital waiting room. This is the surprise. It was hidden, planted, and detonated at the precise moment of maximum contrast. + +**Three strategies make surprise work:** + +**1. Build one expectation, then deliver a different (deeper) one.** + +The emotional architecture is misdirection. Construct a world in which the audience believes they know what the story is about. Then reveal that the story was always about something else. This is called changing the colour of the Elephant -- the audience thought they were tracking one question, and the answer to a different, more profound question arrives instead. + +In entrepreneurial contexts: the pitch that appears to be about a product feature turns out to be about the founder's child. The customer case study that appears to be about efficiency gains turns out to be about a warehouse worker's dignity. The deeper layer, arriving unexpectedly, is what produces the response. + +**2. Heighten contrast immediately before the surprise.** + +The moment before the surprise should be as emotionally distant from it as possible. The story paints a picture-postcard winter scene -- snow falling on lawns, hope for a good Christmas -- seconds before a collision destroys everything. The beauty amplifies the horror. It describes isolation and abandonment in an emergency room -- no one knows his name, his parents chose to check the car first -- before revealing that friends have arrived. + +The principle is universal: laugh before cry, hope before loss, darkness before light. Contrast is the amplifier. + +**3. Hide the critical information.** + +If the audience sees the surprise coming, it ceases to be a surprise. Two techniques preserve it: + +- **Hiding the bomb in the clutter.** Embed the critical detail among other details of apparently equal importance. The request for a nurse to call McDonald's -- the fact that triggers the entire climactic sequence -- is buried in a list of medical procedures. It looks like just another thing happening in an emergency room. It is, in fact, the most important sentence in the story. + +- **Camouflaging with laughter.** Attach a laugh line to the critical detail. The audience attributes the moment to the storyteller's sense of humour, not to narrative engineering. "I was dead twenty minutes ago and now I'm worried about work, but that drive-through does not run well without me." The laugh obscures the bomb. + +**What ruins surprise:** + +- **Thesis statements.** "This is a story about a time my friends became my family." The surprise is dead on arrival. Storytelling is the reverse of the five-paragraph essay. Evidence first, thesis last -- if at all. + +- **Failing to use stakes.** The Backpack, Breadcrumbs, and Hourglass from the stakes framework exist in part to amplify surprise. A plan that is articulated in detail and then fails is more surprising than a plan that fails without setup. Stakes and surprise are symbiotic. + +- **Revealing too early.** Placing the important detail near the payoff, where the audience can connect the dots. Distance is an ally. Plant the bomb early. Detonate it late. + +### Part II: The Mechanics of Laughter + +The framework is candid: it cannot make a person funny. Humour involves wit, timing, tonality, confidence, and a relationship with language that resists systematic instruction. What it can do -- and what this framework addresses -- is help a storyteller add humour to a story through structural technique, even if the storyteller is not naturally amusing. + +Two named methods cover the vast majority of story-based humour: + +#### Milk Cans and a Baseball + +The name derives from the carnival game: stack metallic milk cans in a tower, then knock them down with a ball. In comedy, this is setup and punchline. The milk cans are the setup; the ball is the punchline. + +The rule: **save the funniest word for last.** The instinct of most people is to say the funny thing first, because they are excited about it. This ruins the laugh. The tower of expectations must be built before the ball is thrown. + +Consider the example: "I sleep in a pantry off their kitchen that they've converted into a tiny bedroom. I share this room with a Jehovah's Witness named Rick, a guy who speaks in tongues in his sleep, and the family's indoor pet goat." + +The word *goat* is last because it is the most unexpected. The milk cans -- Jehovah's Witnesses, pantry, tiny bedroom, Rick, speaking in tongues, in his sleep, indoor, pet -- build a tower of increasingly unusual details. Each one recalibrates the audience's expectations. Then *goat* demolishes them. + +**Specificity is funny.** "Pouring water over Raisin Bran because I am too stupid and lazy to buy milk" is funnier than "pouring water over cereal." Oddly specific words generate laughs that generic ones cannot. Some words are inherently amusing -- the well-documented comedic potency of the hard K sound bears this out. The choice of *Pop-Tarts* over *crackers* is deliberate. + +#### Babies and Blenders + +When two things that rarely or never go together are pushed together, humour often results. The framework calls this Babies and Blenders -- the juxtaposition of the innocent and the incongruous. + +Calling a three-year-old boy "a little asshole" after describing him as sweet and angelic gets a laugh because the two categories should not occupy the same sentence. Referring to a grandmother as "a sadist" is funny precisely because the words grandmother and sadist have never been introduced to each other. + +The technique extends to lists. A storyteller creates a sequence of three items, the third of which is categorically unlike the first two: "Zimmers, pineapple-flavoured ham, and despair." The pattern established by the first two items is broken by the third. The break is the surprise. The surprise is the laugh. + +**Exaggeration** is a subspecies of Babies and Blenders: an unreasonable description pushed against something that does not normally accommodate it. "A Christmas tree seven feet wide and three feet tall." The audience knows the dimensions are false, which is why it works. If the exaggeration is presented as fact, it is no longer exaggeration; it is lying. + +### The Strategic Use of Humour in Stories + +Humour is not the goal of storytelling. Heart is the goal. Humour serves four strategic functions: + +1. **Opening laugh.** A laugh in the first thirty seconds signals competence, claims the floor, and reassures the audience that the storyteller is okay -- whatever darkness follows, it is in the past. + +2. **Laugh before the blow.** Placing humour immediately before a painful moment heightens the contrast. "I like to make people laugh before making them cry, because it hurts more that way," as the text puts it. + +3. **Breath after tension.** Following an intense sequence with a laugh allows the audience to reset. Sustained tension without relief becomes numbing. + +4. **Camouflage.** A laugh line draws attention away from a critical detail that must be hidden for a later surprise. + +Stories must end on heart, not on humour. The final sentences should be moving, vulnerable, or universally connecting. Laughs belong in the middle, carrying the audience forward. The landing must be something bigger. + +--- + +## Prompts + +**Prompt 1 -- Surprise Architecture:** +> Here is a story I plan to tell: [paste narrative]. Identify the moment that should produce the strongest emotional response. Then help me restructure the narrative so that (a) a contrasting emotional expectation is built before that moment, (b) the critical information enabling the surprise is hidden earlier in the story using clutter or comedic camouflage, and (c) no thesis statement gives the surprise away. + +**Prompt 2 -- Humour Injection (Milk Cans and Baseballs):** +> Here is a passage from my story that is situationally funny but not landing as hard as it could: [paste passage]. Restructure it using the Milk Cans and a Baseball technique. Identify the funniest word or phrase and move it to the end. Build a tower of increasingly specific and unexpected details before it. Suggest oddly specific words to replace generic ones. + +**Prompt 3 -- Emotional Journey Map:** +> I am delivering a [pitch / keynote / all-hands address / customer story] and I want the audience to experience at least three distinct emotional states. Map out an emotional journey for the narrative: where should the audience laugh, where should they feel tension, where should they feel moved? Place each humour moment strategically (opening signal, pre-blow contrast, post-tension breath, or camouflage). + +**Prompt 4 -- Babies and Blenders Audit:** +> Review this narrative for opportunities to use the Babies and Blenders technique: [paste]. Identify moments where two incongruous elements can be pushed together for comedic effect. Suggest list-of-three constructions where the third item breaks the pattern established by the first two. Ensure that all humour serves the story rather than undermining its emotional destination. + +--- + +## Use Cases + +**Brand Keynote -- Consumer Health Startup** + +A founder delivers a keynote about chronic disease management. The narrative is earnest and informative but produces no emotional response. Applying the framework: the surprise is restructured. The story appears to be about technology (the Elephant) but is revealed to be about a patient's relationship with her daughter. The critical detail -- that the daughter programmed the app herself, at age fourteen -- is hidden in a list of beta testers and camouflaged with a laugh line about the daughter's feedback being "more brutal than any venture capitalist's." The audience expects admiration for the technology. They get admiration for a child's love. The keynote ends not on metrics but on the sentence the daughter said to her mother when the app worked for the first time. The room is silent. Then it is not. + +**Investor Update -- Series B SaaS Company** + +A CEO sends a quarterly investor letter that typically reads as a dashboard with commentary. Applying the emotional impact framework: the letter opens with a laugh (Milk Cans and a Baseball -- the CEO describes the office's new espresso machine as "the only piece of equipment with a higher utilisation rate than our production servers, and better uptime"). The critical surprise -- that the company's largest competitor has begun referring customers to them -- is hidden in a paragraph about partnership strategy, camouflaged by a self-deprecating aside. The surprise lands three paragraphs later when the CEO reveals the competitor's CEO called personally. The letter ends on heart: a single sentence from a customer support ticket that captures what the product means to the people who use it. + +**Team Retrospective -- After a Failed Product Launch** + +A product lead tells the story of a feature launch that missed its targets. The instinct is to present the failure analytically, with charts. Applying the framework: the story is restructured to produce emotional engagement. Babies and Blenders opens the narrative ("We planned this launch for four months and executed it with the precision of a marching band and the market awareness of a goldfish"). The surprise is not the failure itself -- everyone in the room already knows the numbers -- but a piece of customer feedback received during the post-mortem that reframed what the team had actually built. The laugh before the blow comes immediately before the customer's words are read aloud. The story ends not on the failure but on what the team now understands about its customers that it did not understand before. + +--- + +## Anti-Patterns + +- **Confusing sadness with emotional impact.** A story saturated in tragedy does not automatically move an audience. It numbs them. Emotional impact requires surprise, which requires contrast, which requires the story to not be uniformly dark. The founder who opens with devastation and ends with devastation has given the audience nowhere to travel. + +- **Putting the funny word first.** The most common humour failure in storytelling. The speaker leads with the punchline because they cannot wait to get to it, then wonders why the room did not laugh. Milk Cans and a Baseball demands patience: build the tower, then throw the ball. Not the reverse. + +- **Using humour as the destination.** Ending a story on a joke, a pun, or a clever turn of phrase. The audience laughs and then forgets. Heart is what lingers. Laughter is a vehicle, not a destination. The final sentences must land somewhere vulnerable, meaningful, or universally true. + +- **Telegraphing the surprise with a thesis statement.** "This is a story about how our customers became our family." Every emotional beat that follows is pre-digested. The audience cannot be surprised by something they were told at the outset. Evidence first. Thesis never -- or thesis last and understated. + +- **Hiding nothing.** Telling the story in strict chronological order with every important detail flagged as important. The audience connects the dots before the storyteller detonates the surprise. Critical information must be planted early, buried in clutter, and camouflaged by laughter. The gap between planting and payoff is the space where surprise grows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Surprise must compensate for the absence of proof | The emotional payload is the founder's personal connection to the problem -- hidden, then revealed | +| Validation | Laughter builds rapport in early customer and investor conversations | Babies and Blenders can disarm scepticism; the incongruity of a scrappy team tackling a massive problem is inherently funny if framed correctly | +| Early Traction | Real customer stories provide the raw material for surprise | The critical detail to hide is often the customer's own words -- plant them early, detonate them at the close | +| Growth | Internal storytelling (all-hands, retrospectives) requires emotional range | Teams fatigued by metrics need stories that make them laugh and then remind them why the work matters | +| Scale | Surprise becomes harder as company narratives calcify | The greatest emotional impact at scale comes from revealing something the audience assumed they already knew about the company -- and showing them they were wrong | + +At the idea stage, the founder's own biography is often the richest source of surprise. The audience expects a pitch about a market opportunity; the founder reveals a deeply personal reason for caring. The mismatch between expectation and reality is the mechanism. At scale, the mechanism is the same, but the source shifts: the surprise comes from customer stories, employee stories, or data that contradicts the company's own assumptions. + +--- + +## Output Template + +```markdown +# Emotional Impact Design + +## Story / Narrative +[One-sentence summary] + +## Target Emotional Response +[What should the audience feel at the climax? Tears, laughter, awe, resolve?] + +## Surprise Architecture +- **Apparent story:** [What the audience believes the story is about] +- **Actual story:** [What the story is really about -- revealed at the end] +- **Contrast built before surprise:** [The emotional state the audience is in immediately before the reveal] +- **Critical detail hidden:** [The bomb -- what it is, where it is planted, how it is camouflaged] + +## Humour Placement +| Moment | Technique | Strategic Purpose | +|--------|-----------|-------------------| +| [Opening] | [Milk Cans / Babies & Blenders / other] | [Signal competence / claim floor / reassure] | +| [Before blow] | [Technique] | [Heighten contrast] | +| [After tension] | [Technique] | [Allow breath / reset] | +| [Near hidden detail] | [Technique] | [Camouflage critical information] | + +## Milk Cans and a Baseball (if applicable) +- **Tower (setup details in order):** [List each milk can] +- **Ball (funniest word, said last):** [The punchline word] + +## Babies and Blenders (if applicable) +- **Element A (expected):** [The normal thing] +- **Element B (incongruous):** [The unexpected pairing] + +## Landing (Final Sentences) +[Heart, not humour. What is the vulnerable, meaningful, or universally true statement the story ends on?] +``` + +--- + +## Related Skills + +- **[Building Story Stakes](building-story-stakes.md)** -- Stakes create the tension that surprise releases; the Backpack and Hourglass techniques are direct amplifiers of emotional impact. +- **[Storytelling Truth and Vividness](storytelling-truth-and-vividness.md)** -- Cinema of the Mind ensures the audience can see the scene where the surprise detonates; a surprise delivered in a locationless void is a thesis statement in disguise. +- **[Story Performance and Delivery](story-performance-and-delivery.md)** -- Timing, tense shifts, and vocal control determine whether a Milk Cans tower lands or collapses; performance is where structural humour becomes actual laughter. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- Leaders must calibrate emotional impact for context: a board meeting and an all-hands address demand different emotional registers. +- **[What Is a Story](what-is-a-story.md)** -- The transformation requirement defines what kind of emotional impact is possible; only genuine change in the storyteller produces genuine feeling in the audience. +- **[Reader Psychology](../writing/reader-psychology.md)** -- The cognitive science of how audiences process information explains why surprise works: it violates established expectations, forcing deeper processing and stronger emotional encoding. diff --git a/plugins/foreman/content/skills/storytelling/finding-your-stories.md b/plugins/foreman/content/skills/storytelling/finding-your-stories.md new file mode 100644 index 0000000..32c121a --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/finding-your-stories.md @@ -0,0 +1,231 @@ +--- +name: "finding-your-stories" +description: "Teaches three systematic methods for discovering story-worthy moments in everyday life: Homework for Life, Crash and Burn freewriting, and First Last Best Worst. Use when an entrepreneur feels they have no interesting stories to tell, when a leader needs fresh material for presentations and pitches, when preparing for fundraising and struggling to find a personal angle, or when building a long-term practice of narrative awareness." +version: "1.0.0" +category: "storytelling" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - homework-for-life + - freewriting + - story-discovery + - narrative + - daily-practice + - creativity + - pitch-preparation + - personal-narrative +related_skills: + - what-is-a-story + - story-structure-and-arc + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Finding Your Stories + +INVISIBLE GOLD -- You live through story-worthy moments every day but record none of them. Homework for Life is the mining operation. + +The framework behind this skill draws on a list of more than five hundred untold story ideas. Most professional storytellers have a handful. The gap is not talent or life experience. It is a system. Three techniques for extracting stories from the raw material of ordinary existence were discovered and codified. The techniques are disarmingly simple. Their cumulative effect is not. + +The core insight is counterintuitive enough to bear stating plainly: the most compelling stories are almost never the dramatic ones. They are small moments at a dining-room table, a two-in-the-morning walk with an ageing dog, a child's whispered sentence in the morning light. These moments happen constantly. They pass unnoticed because no one has trained themselves to see them. The dramatic events -- the near-death experiences, the arrests, the crises -- make serviceable stories, but audiences connect most deeply to the small and recognisable. Everyone has felt alone at two in the morning. Almost no one has been robbed at gunpoint. + +For entrepreneurs, this reframes the perennial complaint: "I don't have any good stories for my pitch." The stories are there. The problem is an untrained eye. + +--- + +## The Framework + +### Technique 1: Homework for Life + +Homework for Life is the signature practice. It is also, by the framework's own assessment, the single most important technique in the craft. The method: + +**At the end of every day, ask one question:** If I had to tell a five-minute story from today -- as benign, boring, or inconsequential as it might seem -- what would it be? + +**Write the answer in a spreadsheet.** Two columns: date and story. No more than a sentence or two. Not the full story -- just enough to recall the moment later. + +| Date | Story | +|------|-------| +| 11/5/15 | Taught Clara about the Rolling Stones while lying in bed with her. | +| 11/9/15 | Man gets in line at Southwest Airlines, has moment with me, now my best friend, now trying to skip line, now a jerk, but still, my only friend. | +| 11/14/15 | Clara makes snowman almost without my help. So proud. So afraid that she won't need me much longer. | + +The constraints are deliberate. A spreadsheet forces brevity. Brevity ensures the habit survives a busy day. Five minutes is the maximum investment. Miss one day and you permit yourself to miss two; miss two and you abandon the practice entirely. + +**What happens over time:** + +1. **A storytelling lens develops.** Within weeks, practitioners begin noticing story-worthy moments as they happen rather than retrospectively. Experienced practitioners report recognising most moments in real time. + +2. **Forgotten memories resurface.** Recording a present moment frequently triggers associations with the past. An entry about walking a dog in the rain at two in the morning triggered a forgotten childhood memory of a father disappearing underwater, and then a separate memory from a golf course at midnight. One entry. Three recovered stories. + +3. **Patterns emerge.** Seeing recurring themes across entries reveals truths about yourself that isolated incidents conceal. One practitioner discovered he fights with his wife not through words but through angry chore completion -- a pattern only visible across multiple entries. + +4. **Time slows.** Multiple practitioners report that the habit of daily reflection makes life feel longer and more significant. Throwaway days disappear. A woman who had never felt like "an important person in this world" called six months after starting the practice, crying, to say it had changed her life. She never gave her name. + +**The entrepreneurial application is direct.** A founder who has been doing Homework for Life for six months before a fundraise will have a reservoir of personal moments from which to draw. The moment a customer said something unexpected. The evening a co-founder's offhand remark reframed the entire product thesis. The morning the founder realised the team had been solving the wrong problem. These moments are the raw material of compelling pitches, and they are invisible without a system. + +### Technique 2: Crash and Burn (Freewriting) + +Crash and Burn is an adaptation of stream-of-consciousness writing, tuned specifically for story generation. Where Homework for Life captures the present, Crash and Burn excavates the past. + +**The method:** Set a timer for ten minutes. Write without stopping. Follow three rules: + +**Rule 1: Do not get attached to any idea.** When a new thought crashes in -- however unrelated or inferior it seems -- abandon the current thread immediately. The intersections between disparate ideas are where recovered memories and new stories live. + +**Rule 2: Do not judge.** Grammar, punctuation, penmanship, and quality are irrelevant. Everything lands on the page. The inner editor is locked outside the room. + +**Rule 3: The pen never stops.** When the mind empties, list colours (red, green, blue, black, brown...) or numbers in word form until a new thought triggers. The physical act of continuous writing keeps the associative engine running. + +A single ten-minute session produced six potential stories, three anecdotes, three possible articles, and one addition to his personal bucket list (committing a petty crime at sea to be technically classified as a pirate). The session began with the word "grape" and ended with an unopened letter from his father. + +**For entrepreneurs,** Crash and Burn is the pre-meeting preparation tool. Fifteen minutes of freewriting before a board meeting, investor conversation, or keynote produces not polished material but raw connections -- the unexpected link between a childhood memory and the company's origin, the forgotten conversation that crystallised the product vision. These connections, refined later, become the moments that separate a memorable pitch from a forgettable one. + +### Technique 3: First Last Best Worst + +Adapted from an idea by The Moth's artistic director Catherine Burns, First Last Best Worst is a structured prompt exercise. It works as a solo brainstorming tool, an improv game, and -- the text notes with practical enthusiasm -- an excellent activity for long car rides and first dates. + +**The method:** Create a grid. The columns are labelled First, Last, Best, and Worst. The rows are prompts -- any category of human experience. + +| Prompt | First | Last | Best | Worst | +|--------|-------|------|------|-------| +| Job | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Failure | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Customer | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Partnership | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Risk | [Your answer] | [Your answer] | [Your answer] | [Your answer] | + +After completing the grid, analyse it with three questions: + +1. Do any entries appear more than once? (Recurring entries signal likely stories.) +2. Could any entry become a useful anecdote? +3. Could any entry become a fully realised story with a transformation? + +Testing showed that nineteen of twenty-eight entries from standard prompts yielded potential stories. Even when students deliberately chose uninteresting prompts (tree, toaster, socks, flag), eight stories emerged from twenty possibilities. + +**The entrepreneurial variant** replaces personal prompts with business ones: first customer, worst hire, best pivot, last rejection, worst meeting, first investor conversation. The grid fills in and fills out the founder's narrative landscape, connecting moments that seemed isolated into a coherent personal history of the venture. + +--- + +## Prompts + +**Prompt 1 -- Homework for Life Setup:** +> I want to start a daily story-finding practice. I am a [role] at a [type of company] at [stage]. Design a Homework for Life spreadsheet template for me with the two-column format (date, story) and provide ten example prompts I can use on days when nothing seems story-worthy. Also suggest three recurring themes I should watch for based on my role that are likely to produce material useful for [pitches / team talks / board updates / customer conversations]. + +**Prompt 2 -- Crash and Burn Session Guide:** +> I have a [pitch / keynote / team address] in [timeframe] on the topic of [topic]. Guide me through a Crash and Burn freewriting session. Give me a starting word related to my topic, then after I share my raw output, identify the threads worth saving: potential stories, anecdotes, recovered memories, and unexpected connections that could strengthen my [deliverable]. + +**Prompt 3 -- First Last Best Worst for Founders:** +> Generate a First Last Best Worst grid with these business-relevant prompts: first customer, worst failure, best decision, last rejection, first hire, worst meeting, best feedback, worst assumption. After I fill in my answers, analyse the grid for recurring entries, potential stories with transformation arcs, and useful anecdotes. Flag any entry that could serve as an opening for an investor pitch. + +**Prompt 4 -- Story Reservoir Audit:** +> I have been collecting moments for [duration]. Here are my ten most recent Homework for Life entries: [paste entries]. Analyse them for: (a) which entries contain a genuine five-second moment of transformation, (b) which are anecdotes that could support a larger story, (c) what patterns emerge across entries, and (d) which entry has the highest potential for a [pitch / keynote / team narrative]. For the top candidate, suggest the transformation arc (beginning state to ending state). + +--- + +## Use Cases + +**Idea-stage founder preparing for an accelerator interview** + +A first-time founder has a technically sound product concept but struggles to articulate why she personally cares about the problem. She has been doing Homework for Life for three weeks. Reviewing her entries, she notices a cluster of moments related to her mother's struggle with a broken healthcare system -- a pattern she had not consciously recognised. One entry, just eight words long, captures the afternoon her mother gave up trying to schedule a specialist appointment. That entry becomes the opening of her accelerator pitch. The judges remember her application not for the TAM slide but for the eight-word moment that made the problem human. + +**Validation-stage team running a First Last Best Worst session before a customer-discovery sprint** + +A three-person team preparing for fifty customer interviews runs First Last Best Worst with prompts tailored to their market: first time you encountered [problem], worst workaround you have seen, best customer reaction, last assumption that proved wrong. Each team member fills the grid independently, then they compare. Overlapping entries reveal shared assumptions; divergent entries reveal blind spots. Two entries from the worst-workaround column become opening anecdotes for customer conversations, replacing the clinical problem statements they had been using. Interview engagement improves measurably. + +**Scale-stage executive building a personal speaking practice** + +A COO who speaks at three to four industry events per year has been recycling the same company origin story for two years. Audiences have heard it. She begins Homework for Life and, within two months, accumulates forty-seven entries. Nine contain transformation moments. She now has enough material for three years of distinct keynote openings, each rooted in a genuine personal moment rather than the corporate narrative. Her speaking invitations increase because event organisers value speakers who bring new material. + +--- + +## Anti-Patterns + +**1. Writing too much.** The spreadsheet format exists to enforce brevity. A sentence or two per entry. Writing full paragraphs converts a five-minute habit into a thirty-minute obligation, and obligations die quickly. The goal is capturing a trigger for memory, not composing a draft. + +**2. Waiting for the dramatic moment.** The most common failure mode is recording only "big" events and ignoring the small ones. The most popular story in the framework involves a wife revealing she knew a childhood secret -- a moment at a dining-room table. Stories about near-death experiences, while exciting, connect less deeply. Founders who only record their biggest wins and losses miss the quiet moments that audiences find most compelling. + +**3. Skipping days and abandoning the practice.** Miss one day and you will miss two. Miss two and the week is gone. The discipline is non-negotiable. Only a "tragically small percentage" of the thousands taught this method actually sustain the practice. The ones who do report life-changing results. The ones who do not have no stories to show for it. + +**4. Using Crash and Burn as outlining.** Crash and Burn is not a planning exercise. Attempting to steer the freewriting toward a predetermined topic defeats the associative mechanism that produces unexpected connections. The entrepreneur who sits down to "freewrite about my pitch" will produce pitch notes, not stories. Start with an unrelated object in the room and let the mind wander. + +**5. Treating First Last Best Worst as trivia.** The exercise is not about identifying facts (my first car was a Honda). It is about locating moments of emotional significance attached to those facts. The answer "Honda Civic" is useless. The answer "Honda Civic -- the morning I drove away from my parents' house for the last time and realised I was terrified" is a story seed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal moments that reveal why you care about this problem | The founder's story inventory IS the company's narrative capital | +| Validation | Customer-interaction moments that shift your understanding | Homework for Life entries increasingly feature other people's words and reactions | +| Early Traction | Team moments, pivot moments, failure moments | Story material expands beyond the founder; the practice should spread to co-founders | +| Growth | Encouraging managers to maintain their own story practices | Narrative capacity must scale with the organisation; one storyteller is not enough | +| Scale | Institutional story collection across functions | Systematised story-gathering (customer stories, team stories, field stories) mirrors Homework for Life at organisational level | + +At the idea stage, a founder with sixty days of Homework for Life entries possesses something no slide deck can replicate: a reservoir of genuine, personal, transformation-bearing moments. Investors who have heard ten pitches that day will remember the one that opened with a real moment, not a market statistic. + +At scale, the challenge is distributing story-finding capability. A single executive with a rich story practice cannot supply narrative material for an organisation of hundreds. The techniques taught here -- particularly Homework for Life and First Last Best Worst -- transfer well to team workshops, offsites, and onboarding programmes. They are inexpensive, require no special tools, and produce results within weeks. + +--- + +## Output Template + +```markdown +# Story Discovery Plan -- [Name / Team] + +**Purpose:** [Pitch preparation / Keynote / Team alignment / Ongoing practice] +**Date started:** [Date] + +## 1. Homework for Life Setup +**Tool:** [Spreadsheet / Notes app / Physical journal] +**Daily trigger:** [End of day / Commute home / Before bed] +**Format:** Date | One to two sentence moment + +### This Week's Entries +| Date | Moment | +|------|--------| +| [Date] | [Entry] | +| [Date] | [Entry] | +| [Date] | [Entry] | + +## 2. Crash and Burn Log +**Last session date:** [Date] +**Starting word:** [Word] +**Threads worth saving:** +- [Thread 1 -- potential story / anecdote / connection] +- [Thread 2] +- [Thread 3] + +## 3. First Last Best Worst Grid +| Prompt | First | Last | Best | Worst | +|--------|-------|------|------|-------| +| [Prompt 1] | | | | | +| [Prompt 2] | | | | | +| [Prompt 3] | | | | | + +**Recurring entries:** [List any that appear more than once] +**Potential stories (with transformation):** [List with brief arc description] +**Useful anecdotes:** [List] + +## 4. Top Story Candidates for [Upcoming Event / Pitch / Presentation] +1. **[Entry reference]** -- Transformation: from [starting state] to [ending state] +2. **[Entry reference]** -- Transformation: from [starting state] to [ending state] +3. **[Entry reference]** -- Anecdote supporting [theme] +``` + +--- + +## Related Skills + +- **[What Is a Story](what-is-a-story.md)** -- Defines the transformation requirement that determines which discovered moments qualify as stories versus anecdotes. +- **[Story Structure and Arc](story-structure-and-arc.md)** -- Once a story-worthy moment is found, this skill teaches how to build the five-second moment into a complete narrative. +- **[Story Beginnings and Endings](story-beginnings-and-endings.md)** -- The raw material from Homework for Life must be shaped; this skill covers where to start and how to land. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- The leadership application of story; the discovery techniques taught here feed directly into change narratives and vision stories. +- **[Storytelling Truth and Vividness](storytelling-truth-and-vividness.md)** -- The discovered moments must be told with sensory detail and honesty; the Cinema of the Mind and Five Permissible Lies provide the craft techniques. +- **[Leader Self-Reflection](../leadership/leader-self-reflection.md)** -- The daily reflective practice of examining consequential interactions produces the raw material that Homework for Life systematises into a story library. diff --git a/plugins/foreman/content/skills/storytelling/story-beginnings-and-endings.md b/plugins/foreman/content/skills/storytelling/story-beginnings-and-endings.md new file mode 100644 index 0000000..68af578 --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/story-beginnings-and-endings.md @@ -0,0 +1,227 @@ +--- +name: "story-beginnings-and-endings" +description: "Teaches the opposite-of-the-end rule for finding a story's beginning, the discipline of starting as close to the end as possible, the use of forward movement in opening lines, and the art of frayed endings that resonate without neatly resolving. Use when a pitch or talk starts in the wrong place, when an audience loses interest in the first thirty seconds, when a story's conclusion feels forced or anticlimactic, or when refining any narrative for maximum structural impact." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative-structure + - beginnings + - endings + - pitch-craft + - opening-lines + - presentation + - arc + - forward-movement + - opposite-of-the-end +related_skills: + - what-is-a-story + - finding-your-stories + - story-structure-and-arc + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Story Beginnings and Endings + +BACKWARDS -- Good stories are built backwards from the ending. Most storytellers do not know this, which is why they start in the wrong place. + +More than half the crafting time should go to a single decision: where to begin. Not on the climax. Not on the emotional payload. Not on the jokes or the vivid details. On the first sentence. This allocation of effort is counterintuitive and, according to the framework, the single most consequential craft decision a storyteller makes. The ending -- the five-second moment of transformation -- is given. It happened. The storyteller knows what changed. The beginning, by contrast, must be chosen from an ocean of possibilities, and most storytellers choose poorly. + +The error is almost always the same: starting too early. The founder who opens a pitch with her childhood. The CEO who begins a company narrative with the founding date. The speaker who spends three minutes establishing context before arriving at anything that matters. They start too early because they confuse chronology with story. A story is not a timeline. A story is an arc from one state of being to its opposite, and the beginning must be selected to create that arc -- not to provide a comprehensive history. + +Endings suffer from the inverse problem. Where beginnings err by starting too early, endings err by going too late -- wrapping up, explaining, moralising, restating the point. The best endings, the framework argues, do not land neatly. They fray. They connect back to the beginning with transformed meaning, leaving the audience to feel the resonance rather than having it explained to them. + +--- + +## The Framework + +### Finding the Beginning: The Opposite-of-the-End Rule + +The process starts at the end. The five-second moment of transformation is the story's destination. Once it is identified, the beginning reveals itself through a single question: **What is the opposite of my ending?** + +The logic is structural. A story must demonstrate change. Change requires two states: the state before and the state after. The ending is the "after." The beginning must be the "before" -- and for maximum arc, the "before" should be as far from the "after" as the truth permits. + +The framework formalises this as a series of templates: + +- I was once hopeful, **but now** I am not. +- I was once lost, **but now** I am found. +- I was once certain, **but now** I doubt. +- I was once afraid, **but now** I am fearless. +- I once believed this, **but now** I believe the opposite. + +The beginning of the story is the left side of these statements. The ending is the right. Everything in between is the arc that carries the audience from one to the other. + +**Applied to "Charity Thief":** The story ends with the realisation that the protagonist knows nothing about loneliness. The opposite of knowing nothing about loneliness is the belief that you understand it intimately. The story therefore begins in a gas station, with the protagonist convinced he is the loneliest person alive. Beginning and ending are mirror images. The arc between them is the story. + +**Applied to Jurassic Park:** Grant despises children at the beginning. He loves them at the end. If you watch the first fifteen minutes and ask "What is the opposite of this?", you know the ending. Spielberg is not hiding the destination. He is making the journey compelling enough that the audience forgets they already know where it leads. + +**Applied to a founder's pitch:** If the story ends with the realisation that the company had been solving the wrong problem, the beginning must show the founder utterly convinced they were solving the right one. If the story ends with unexpected traction from an overlooked segment, the beginning must show the founder focused entirely on a different segment. + +The opposite-of-the-end rule does not merely structure the narrative. It creates the satisfaction that audiences feel when a story "works." The greater the distance between beginning and ending states, the more profound the arc, and the more the audience feels that they have travelled somewhere meaningful. + +### Starting as Close to the End as Possible + +The opposite-of-the-end rule tells you what your beginning should feel like. A second principle tells you where to place it in time: **as close to the ending as possible.** + +This is Kurt Vonnegut's rule for short fiction, adopted here for oral storytelling. The reason is compression. Shorter stories are tighter, sharper, and easier for audiences to hold in their minds. Every additional minute of setup is a minute in which the audience's attention can wander, and in oral storytelling -- unlike written prose -- the audience cannot pause, re-read, or look up context. The river of words flows continuously. Fall behind, and the water is gone. + +The revision process for a story set in Boca Raton demonstrates this. The first draft began in a Connecticut airport. Revision moved the beginning onto the plane. Then into the sky. Then to the Boca Raton airport. Then to the rental-car counter. Through five revisions, the beginning migrated twelve hundred miles in distance and five hours in time. Two airport terminals and an airplane were eliminated entirely. The story now takes place in one location: the building where cars are rented. + +**The practical test:** For every element of backstory or setup, ask: "Does the audience need this to understand the five-second moment?" If the answer is no, cut it. If the answer is "they'd appreciate the context," that is also a no. The audience needs only what serves the moment. Context that does not serve the moment is the storyteller indulging themselves at the audience's expense. + +For entrepreneurs, this discipline is liberating. The instinct is to start a company story at the founding -- or worse, at the personal backstory that led to the founding. The opposite-of-the-end rule identifies the emotional starting point; the closeness principle identifies the temporal one. Often the best beginning for a pitch story happened last month, not five years ago. + +### Opening with Forward Movement + +Once the starting point is chosen, the first words matter. The framework advocates opening with physical movement: + +> "I'm driving down a lonely stretch of New Hampshire highway..." +> "I'm walking out of a record store on a December day..." + +The protagonist is already in motion. The audience is already being carried somewhere. There is no throat-clearing, no context-setting, no "Let me tell you about..." -- just a person moving through space toward something the audience does not yet know about. + +Filmmakers understand this instinctively. Star Wars opens with starships racing through space. Raiders of the Lost Ark opens with Indiana Jones marching through a jungle. Vertigo opens with a man climbing a ladder. The audience is immersed before they have time to decide whether they are interested. + +**Three things to avoid in opening lines:** + +1. **Thesis statements.** "This is a story about resilience" robs the narrative of surprise and teaches the audience nothing. It is the storytelling equivalent of explaining a joke before telling it. + +2. **Expectation-setting.** "You're not going to believe this" or "This is hilarious" establishes a bar the story may not clear and primes the audience for a specific reaction, eliminating the possibility of genuine surprise. + +3. **Backstory.** Beginning with history ("When I was seven years old...") instead of movement ("I'm standing in a hospital corridor...") forces the audience to wait for the story to start. The story should already be in progress when the audience arrives. + +### Finding the Frayed Ending + +Endings are where meaning lives, and the temptation is to make that meaning explicit. The framework resists this. The best endings do not conclude; they resonate. They do not explain the transformation; they let the audience feel it. + +The process of finding an ending is often a process of finding meaning itself. Storytellers encounter moments from their lives that they know are significant but cannot articulate why. The solution: tell the story aloud, unpolished, ignoring all craft, spilling every detail. Through the act of telling, the meaning surfaces. The five-second moment clarifies. + +The band-camp story ("Eddie in a Bathtub") sat on the list for twenty years as a moment that mattered but could not be explained. When a workshop class selected it randomly, the whole messy version was told aloud and -- in the telling -- the beating revealed two separate meanings. Each meaning demanded a different story with a different beginning. The ending was the same event; the stories were not. + +**The frayed-ending principle:** Stories need not tie up neatly. An ending that connects back to the beginning with shifted meaning -- the same image or phrase, now carrying different weight -- is more powerful than an ending that summarises the lesson learned. + +A story about a father's letters illustrates this. The storyteller keeps one letter from his father perpetually unopened. Through self-interrogation, he discovers why: as long as an unread letter exists, his father can never truly leave him again. The story does not end with a resolution of the father-son relationship. It ends with the letter still sealed. The audience understands something the teller has only just understood himself. Nothing is resolved. Everything is felt. + +**For entrepreneurs,** this means resisting the instinct to close a pitch story with a neat moral ("And that's why we built X"). Instead, the ending should land on the moment of transformation and let the audience draw the connection. The ask, the product, the market opportunity -- these can follow the story. They should not be the story's conclusion. A story that ends with a call to action is a sales pitch that borrowed narrative clothing. A story that ends on a moment of genuine change and then transitions to a business discussion is a story that earns the audience's attention for whatever comes next. + +--- + +## Prompts + +**Prompt 1 -- Beginning Finder:** +> My story's five-second moment is: [describe the transformation]. Using the opposite-of-the-end rule, identify what my beginning state should be. Then suggest three possible opening scenes from my life or experience that establish that opposite state, ranked by (a) how close they are to the ending in time, (b) how effectively they establish the opposite, and (c) whether they open with forward movement. + +**Prompt 2 -- Closeness Audit:** +> Here is my current story: [paste story]. My five-second moment occurs at [identify it]. Analyse the beginning: how far in time and space is it from the ending? Identify every element of setup and backstory. For each, determine whether the audience genuinely needs it to understand the five-second moment. Suggest a revised beginning that starts as close to the end as possible while still establishing the opposite state. + +**Prompt 3 -- Opening Line Workshop:** +> I need to open a [pitch / keynote / team talk] with a story. The five-second moment is: [describe it]. The opposite starting state is: [describe it]. Write five possible opening sentences that (a) place the protagonist in physical motion, (b) contain no thesis statement or expectation-setting, (c) immerse the audience in a specific time and place, and (d) feel natural enough to pass the Dinner Test. For each, note which element of the opposite state it establishes. + +**Prompt 4 -- Ending Refinement:** +> Here is how my story currently ends: [paste ending]. Does it explain the transformation or let the audience feel it? If it explains, rewrite it as a frayed ending -- one that connects back to the beginning with shifted meaning but does not summarise or moralise. If it already resonates, suggest one small adjustment that could strengthen the callback to the opening. + +--- + +## Use Cases + +**Idea-stage founder revising a demo-day pitch** + +A founder's two-minute demo-day pitch begins with "Three years ago, I was working at a large hospital system and noticed that..." The audience has heard fifty pitches that begin with some variation of "X years ago, I was working at..." Applying the closeness principle, the founder moves the beginning from three years ago to last Tuesday: "I'm sitting across from a patient who has just been told she has six months to receive a treatment that should have started six months ago." The story now opens with forward movement, a specific scene, and an immediate emotional stake. The founding backstory -- previously the first ninety seconds -- is compressed to a single sentence of context. The five-second moment (the founder's realisation that the system is designed to delay, not deliver) now arrives sixty seconds in instead of ninety, and the remaining time is available for the ask. + +**Early-traction startup rewriting its company narrative for the website** + +The "Our Story" page is a chronological timeline: founded in 2022, launched MVP in 2023, first customer in 2023, Series A in 2024. Applying the opposite-of-the-end rule, the team identifies the company's five-second moment: the morning the first customer used the product in a way the team never intended, revealing a market ten times larger than the one they had targeted. The beginning is rewritten as the opposite: the team's absolute certainty about who their customer was and what the product was for. The "Our Story" page now reads as an arc of transformation rather than a sequence of dates. The timeline still appears -- in a sidebar, as supporting evidence -- but the narrative carries the page. + +**Growth-stage leader fixing a keynote that loses the audience in the first two minutes** + +A CTO's conference talk opens with three minutes of personal history and company background before arriving at the technical insight that is the talk's purpose. Audience attention data shows engagement drops at minute two and never fully recovers. Applying the forward-movement principle, the CTO rewrites the opening: "Last Thursday at 2:14 AM, our monitoring system woke me up with an alert that should have been impossible." The audience is in motion from the first sentence. The personal history that previously consumed three minutes is reduced to a single clause: "I've spent fifteen years building systems that are supposed to prevent exactly this." The technical insight -- the five-second moment -- now arrives at minute four instead of minute eight, and the audience is present for it. + +--- + +## Anti-Patterns + +**1. The autobiography opening.** "I grew up in a small town in Ohio..." or "When I was seven years old..." unless the childhood scene is the direct opposite of the ending and cannot be established any other way. Ninety percent of the time, the story can begin years or decades later without losing anything essential. + +**2. The throat-clearing preamble.** Any variation of "Before I begin, let me give you some context" or "To understand this story, you need to know that..." is a signal that the beginning has not been found. If the audience needs context that cannot be delivered inside the story itself, the story's structure needs revision, not a preface. + +**3. The neat bow.** Endings that summarise the lesson ("And that's when I learned that...") or state the moral explicitly ("The takeaway here is...") treat the audience as incapable of feeling the transformation they just witnessed. The storyteller's job is to deliver the moment, not interpret it. Let the audience do the interpreting. + +**4. The runaway ending.** Continuing to talk after the five-second moment has landed. The story is over. Additional scenes, reflections, or "what happened next" segments dilute the emotional impact. The principle is explicit: the five-second moment should come as close to the last words as possible. + +**5. Choosing the first beginning that comes to mind.** The framework warns that the first idea is rarely the best. It is the most convenient, the easiest to remember, and the one the teller personally likes most. The right beginning requires deliberation -- listing multiple options and evaluating each for proximity to the end, effectiveness in establishing the opposite state, and potential for forward movement. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Crafting a single, tight origin-story arc with the closest possible beginning | The entire pitch may be two minutes; every second of setup is a second stolen from the transformation | +| Validation | Beginning with customer-discovery moments rather than founding backstory | The "opposite state" is often the team's initial assumption, now overturned by evidence | +| Early Traction | Refining pivot narratives: old direction as beginning, new direction as ending | The closeness principle prevents the narrative from becoming a comprehensive history of every wrong turn | +| Growth | Teaching multiple team members to find beginnings for their own stories | Sales, product, and engineering each need domain-specific openings that establish their own opposite states | +| Scale | Building institutional narratives with layered beginnings and frayed endings | The company's arc spans years; the craft is selecting the right entry point from an abundance of material | + +At the idea stage, the founder's pitch story must begin and end within a span the audience can hold -- ideally under three minutes. The closeness principle is not a suggestion at this stage; it is a survival requirement. Every sentence of backstory that does not serve the five-second moment is a sentence in which an investor's attention migrates to their phone. + +At scale, the challenge inverts. The company has so much material that the difficulty is not finding a beginning but choosing one. The opposite-of-the-end rule becomes a filtering mechanism: of the hundred possible starting points, which one creates the most powerful arc with the current five-second moment? The answer changes depending on the audience, the context, and the transformation being communicated. + +--- + +## Output Template + +```markdown +# Story Beginning and Ending Worksheet -- [Story Title or Context] + +**Teller:** [Name] +**Audience:** [Investors / Team / Conference / Board] +**Date:** [Date] + +## 1. The Ending (Five-Second Moment) +**What changed:** [Describe the transformation in one sentence] +**Ending state:** [What the protagonist now believes, feels, or understands] + +## 2. The Beginning (Opposite of the End) +**Beginning state:** [The opposite of the ending state] +**Candidate openings:** +| Option | Scene description | Distance from ending | Establishes opposite? | Forward movement? | +|--------|------------------|---------------------|----------------------|-------------------| +| A | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | +| B | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | +| C | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | + +**Selected opening:** [Option letter and rationale] + +## 3. Opening Line Draft +[First two sentences -- forward movement, no preamble, specific time and place] + +## 4. Closeness Check +**Elements between beginning and five-second moment:** +| Element | Necessary for the audience to understand the moment? | Keep / Cut | +|---------|-----------------------------------------------------|-----------| +| [Element] | [Assessment] | [Decision] | + +## 5. Ending Draft +**Does the ending explain or resonate?** [Explain / Resonate] +**Callback to beginning:** [How the ending echoes the opening with transformed meaning] +**Final line draft:** [The last sentence the audience hears] +``` + +--- + +## Related Skills + +- **[What Is a Story](what-is-a-story.md)** -- The transformation requirement that defines a story also defines the relationship between beginning and ending; this foundational skill should be understood first. +- **[Finding Your Stories](finding-your-stories.md)** -- Homework for Life generates the raw moments from which beginnings and endings are selected; the discovery practice feeds directly into the structural decisions taught here. +- **[Story Structure and Arc](story-structure-and-arc.md)** -- The five-second moment and But-and-Therefore principles provide the middle of the story; this skill provides the bookends. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- The mandate-for-change function is structurally an opposite-of-the-end setup: here is where we are, here is where we must go, here is why. +- **[Emotional Impact in Stories](emotional-impact-in-stories.md)** -- The ending is where emotional impact detonates; the surprise and humour techniques determine whether the landing produces feeling or merely concludes. +- **[Leading Through Change](../leadership/leading-through-change.md)** -- Change narratives require the same arc discipline: begin in the current state, end in the desired state, and make the distance between them felt. diff --git a/plugins/foreman/content/skills/storytelling/story-performance-and-delivery.md b/plugins/foreman/content/skills/storytelling/story-performance-and-delivery.md new file mode 100644 index 0000000..7e15161 --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/story-performance-and-delivery.md @@ -0,0 +1,233 @@ +--- +name: "story-performance-and-delivery" +description: "Covers the practical mechanics of performing a story: present tense as default, tense shifting, the two strategies for telling success stories without sounding like a braggart, scene-based memorisation, eye contact, microphone technique, emotional control, word selection, and adapting delivery across contexts from stages to boardrooms. Use when preparing to deliver a story live, when rehearsing a pitch or keynote, or when a narrative reads well on paper but falls flat in the room." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - performance + - delivery + - present-tense + - hero-story + - public-speaking + - pitching + - rehearsal + - pacing + - eye-contact + - vulnerability + - word-choice +related_skills: + - building-story-stakes + - storytelling-truth-and-vividness + - emotional-impact-in-stories + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Story Performance and Delivery + +The best storytellers do not perform on stages -- they perform at dinner tables, in meeting rooms, and in elevator pitches. The principles are identical. The record holder for Moth StorySLAM victories insists that the gap between a great written story and a great told story is bridged by a handful of concrete, trainable techniques: the strategic use of present tense, scene-based memorisation instead of word-for-word recitation, deliberate word selection, controlled vulnerability, and the discipline to keep talking no matter what. None of these require natural charisma. All of them require practice and intention. + +--- + +## The Framework + +### Present Tense as the Default + +The present tense creates immediacy. It functions as a temporal magnet, pulling the audience out of whatever room they occupy and into whatever room the story occupies. "I'm standing in the parking lot" places the listener in that parking lot more forcefully than "I stood in the parking lot." The past tense describes. The present tense transports. + +The technique is demonstrated by writing an entire chapter in real time, on an Amtrak train, while his five-year-old son refuses to use the restroom. The reader is on the train. The reader feels the rocking. The reader worries about the boy's bladder. That is the present tense at work. + +**When to shift to past tense:** + +- **Backstory.** When slipping into events that precede the main narrative, the past tense signals temporal distance. A story cannot have two present-tense timelines without diluting both. The backstory is in the past; present it as such. +- **Moments best told from a distance.** Not every scene benefits from the audience being pulled inside it. Some moments -- particularly those involving discomfort, vulnerability, or physical specifics -- are more effective with a layer of temporal remove. +- **Returning to present tense after backstory** functions as a reset. It pulls the audience back into the primary timeline. The effect is like pressing a button on an arcade racing game: shifting the camera from an overhead view back to the driver's seat. + +**Tense shifts should be instinctual, not mechanical.** In live storytelling, speakers shift tenses constantly -- often mid-sentence -- and audiences never notice. The shifts become visible only on the written page. The principle: when the emotional intensity of a moment demands closeness, shift to present. When distance serves the narrative, shift to past. When in doubt, stay present. + +Not every speaker can tell stories in the present tense. Some have spent years in the past tense, and the cognitive load of switching overwhelms their delivery. There is nothing wrong with telling stories exclusively in the past tense. A well-told past-tense story beats a poorly told present-tense story without exception. + +### The Two Ways of Telling a Hero Story + +No one likes a braggart. Proverbs, da Vinci, and Mark Twain all agree on this point, and audiences confirm it nightly. Failure is more engaging than success. The story of a strikeout with the bases loaded is more compelling than the story of a walk-off home run. Getting fired from a dream job produces better narrative than getting hired. + +Yet entrepreneurs must frequently tell success stories: to investors, to recruits, to customers, to the press. The challenge is doing so without becoming insufferable. The framework offers two strategies: + +**1. Malign yourself.** + +Before telling the success, share a highly imperfect moment. Cast yourself as the underdog. In one example, a story about saving a student's life opens with a scene in which the teller accidentally strikes a child in the head with a thrown shoe. The audience knows he is not pretending to be the world's greatest teacher. By the time the success arrives, it feels earned rather than boasted. + +This is why Bruce Willis is barefoot and outnumbered in *Die Hard*. Why the rebels fly a single tiny ship against a star destroyer in the opening of *Star Wars*. Underdog status invites the audience to root for the protagonist. It converts the success story from self-congratulation into something the audience feels they participated in. + +**For founders:** Before the fundraising win, describe the seventeen rejections. Before the product breakthrough, describe the version that crashed during the demo. Before the hiring coup, describe the candidate who turned you down. The vulnerability precedes the victory, and the victory is sweetened by it. + +**2. Marginalize the accomplishment.** + +Rather than telling the complete success, tell a small part of it. Allude to the larger outcome but focus on one step. Human beings prefer stories of small steps over large leaps. Overnight successes are rare and alienating. The step-by-step nature of achievement is what audiences understand and connect with. + +In another example, a story about saving one student immediately catalogues the students the teller failed to save. The success is real but circumscribed. The audience connects with the partial, imperfect version more deeply than they would with an unblemished triumph. + +**For founders:** The story of achieving product-market fit is best told as the story of one customer's experience. The story of scaling to a hundred employees is best told as the story of one hire who changed the culture. Small steps. Never the panoramic victory lap. + +### Scene-Based Memorisation + +Do not memorise a story word for word. Actors memorise lines because they have fellow actors and stage directions to anchor them. A storyteller has nothing but the microphone and the audience. When a memorised word goes missing, the storyteller freezes. Speakers have been observed standing in silence for a minute or more, trapped in the gap between a forgotten word and the next remembered one. + +Instead, memorise three things: + +1. **The first few sentences.** Always start strong. The opening must be rehearsed to the point of automatic delivery. +2. **The last few sentences.** Always end strong. The landing is the part the audience carries with them. +3. **The scenes.** If every moment of the story is anchored in a physical location (per the Cinema of the Mind principle), then the story is a sequence of places. Remember the places, and you remember what happens in each one. + +The technique involves remembering scenes as circles in the mind -- varying in size (reflecting the scene's duration) and colour (reflecting its emotional tone). Seven scenes is the maximum. The telephone company settled on seven digits for a reason: it is the upper limit of what most people can retain at once. + +If every prepared word flees the speaker's mind, the scenes remain. The storyteller may lose a laugh line or a golden sentence, but the story still gets told. As The Moth's artistic director once observed: "You could certainly mess up your story, but you never stop talking, so I know you'll eventually find your way back." + +The principle for entrepreneurs is identical. A pitch is not a script. It is a sequence of scenes. Know the opening, know the close, know the scenes in between. The rest is navigation. + +### Words to Use, Words to Avoid + +**Profanity.** Use sparingly. Swearing is lazy in most cases; a better word almost always exists. The exceptions: repeated dialogue (someone else's words, reported faithfully), moments of extreme emotion, and the rare occasion when a profane word is genuinely the most precise one available. Avoiding profanity also broadens the contexts in which a story can be told -- from religious institutions to school classrooms to corporate retreats. + +**Vulgarity.** Distinct from profanity. Vulgarity is the description of events that are profane in nature. The rule: if the topic would be awkward to discuss with a grandparent, tread lightly. Use euphemism, allusion, and self-deprecation. The audience can fill in the reality without needing it spelled out. Graphic specificity repels; suggestive restraint engages. + +**Celebrity and pop-culture references.** Avoid. They alienate the half of the audience that does not recognise the reference. They insert a famous person into the audience's mental movie, breaking the story's internal reality. And they are lazy -- a shorthand that reveals little about character. Instead of "she was like Zooey Deschanel," describe the qualities directly: "She never seemed to have a job but always seemed to have just enough money. She was carefree. The girl who would never grow up." + +**Accents.** The rule is simple: do not attempt them. Imitating the accent of someone from another culture risks insensitivity at best, offence at worst. The sole exception is the accents of one's own parents or grandparents, where parental love provides cover. When in doubt, abstain. + +**Oddly specific words.** Prefer them. Specificity is inherently engaging and often funny. "Raisin Bran" is better than "cereal." "Pop-Tarts" is better than "snack." Precision of language is not decoration; it is the mechanism by which the audience's mental movie achieves resolution. + +### Performing Across Contexts + +The techniques above apply identically whether the venue is a thousand-seat theatre or a Thanksgiving dinner table. Context modifies scale, not substance. + +**Eye contact.** When the audience is visible (boardroom, dinner table, small stage), find three people who like you -- left, centre, right. These are the smilers, the nodders, the laughers. Use them as guideposts. The people near each guidepost will feel attended to as well. Choosing friendly faces also bolsters the speaker's confidence. + +**Microphone use.** If offered a microphone, accept it. Hearing impairment is far more prevalent than most people realise, and few hearing-impaired individuals wish to announce their condition. Three universal principles: (1) the microphone is not magic -- still project to the back of the room, (2) adjust the stand before speaking, not during, and (3) learn to cut through laughter and applause to regain control of pacing. + +**Emotional control.** Some stories provoke emotion in the teller. This is natural and, within limits, endearing. The technique for managing excessive emotion: shift perspective from first-person to overhead. Instead of reliving the moment through one's own eyes, watch it from above -- a wounded person, not oneself, seeing friends appear in a doorway. This "B button" (a term drawn from arcade racing games) provides enough distance to continue speaking. Alternatively, inoculate against the power of specific sentences by repeating them dozens of times before performing. Repetition strips some emotion; the audience's presence restores just enough. + +**Nervousness.** A moderate amount of visible nervousness is an asset. It signals vulnerability, authenticity, and that the speaker cares about the outcome. Audiences root for speakers who appear human. The exception: contexts where authority is expected (professional conferences, board presentations, State of the Union addresses). In those settings, confidence is required. But in pitches, toasts, first dates, and storytelling stages, nervousness bridges the gap between speaker and audience. + +**Never rehearse in front of a mirror.** The only person the speaker will never see during a performance is themselves. Practising before a mirror encourages attention to physical appearance, which is irrelevant. Practise before other people, or before pictures of other people, or before a wall. Anything but a reflection. + +--- + +## Prompts + +**Prompt 1 -- Tense Mapping:** +> Here is a story I plan to deliver live: [paste narrative]. Map it for tense usage. Mark which sections should be told in present tense (high emotional intensity, primary timeline, key reveals) and which in past tense (backstory, moments best told from a distance). Show where tense shifts should occur and explain why. + +**Prompt 2 -- Hero Story Redesign:** +> I need to tell a success story about [achievement]. Help me apply the two hero-story strategies: (1) identify a moment of imperfection, failure, or vulnerability I can share before the success to cast myself as an underdog, and (2) identify the smallest step within the larger success that I can focus on, marginalising the accomplishment without diminishing it. Rewrite the story using both techniques. + +**Prompt 3 -- Scene-Based Memorisation Plan:** +> Here is my story: [paste]. Break it into no more than seven scenes, each anchored in a physical location. For each scene, provide: the location, the key action or dialogue that occurs there, and the emotional tone (which I will remember as a colour). Then write the first three sentences and the last three sentences, which I will memorise word-for-word. + +**Prompt 4 -- Word Audit:** +> Review this narrative for word-choice issues: [paste]. Flag any profanity that could be replaced by a more precise word, any vulgarity that should be softened with euphemism, any celebrity or pop-culture references that should be replaced with direct description, and any generic words that would benefit from odd specificity. Provide suggested replacements. + +--- + +## Use Cases + +**Demo Day Pitch -- Accelerator Cohort** + +A founder prepares a three-minute pitch that currently reads as a memorised script. She freezes in rehearsal when she forgets a sentence. Applying scene-based memorisation: the pitch is restructured into four scenes (the customer's office where the problem was observed, the garage where the prototype was built, the Zoom call where the first paying customer signed, and the stage where the founder is standing now). The opening and closing sentences are memorised precisely. Everything in between is navigated by scene. The founder also applies the hero-story framework: before describing the first customer win, she describes the demo that crashed in front of a prospect's entire leadership team. The vulnerability earns the audience's investment in the success that follows. + +**Board Presentation -- Growth-Stage Company** + +A CEO delivers a quarterly board update that sounds like a recitation of a pre-read document. Board members check their phones. Applying the framework: the CEO shifts to present tense for the narrative sections ("It's the second week of October, and our head of product walks into my office with a chart I've never seen before"). Backstory is delivered in past tense to create temporal contrast. The success metric is introduced using the marginalization technique: rather than presenting the full dashboard, the CEO tells the story of one customer whose usage pattern revealed the insight. The board leans in. The metrics, when they appear, land in a narrative context that makes them memorable. + +--- + +## Anti-Patterns + +- **Memorising word for word.** The single most common cause of catastrophic performance failure in live storytelling and pitching. When a word goes missing, the speaker's mind goes blank. Scene-based memorisation provides a recovery path that script memorisation does not. + +- **Telling the entire success story.** Recounting every milestone, every win, every compliment received. The audience disconnects halfway through. Small steps are relatable. Panoramic victory laps are not. The most effective success story is the one that includes the failure that preceded it and the doubt that accompanied it. + +- **Defaulting to past tense out of habit.** The present tense is available and powerful, but many speakers never consider it. Past tense is safe and intuitive; present tense is transporting and immediate. The best speakers toggle between the two. The worst speakers do not know they have a choice. + +- **Performing for the mirror.** Rehearsing alone while staring at one's own reflection cultivates self-consciousness about appearance, which is the last thing a storyteller should be thinking about during delivery. The words, the pacing, the emotional arc -- these are what matter. The tilt of a head and the position of hands are irrelevant. + +- **Avoiding all vulnerability in professional contexts.** The instinct to project flawless competence in pitches, board meetings, and sales calls leads to stories that no audience connects with. Vulnerability -- the admission of a mistake, a fear, a moment of doubt -- is the bridge between speaker and listener. The observation is blunt: failure is more engaging than success. The professional who shares only success shares nothing memorable. + +- **Imitating accents.** However well-intentioned, accent imitation in storytelling carries asymmetric risk: modest upside (a moment of flavour) and catastrophic downside (the audience perceives insensitivity). The return-on-risk calculation is unambiguous. Describe the person's qualities. Leave their accent alone. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The hero-story problem is acute: founders must sell themselves without sounding like braggarts | Malign yourself early; the idea stage is where vulnerability is most credible and most needed | +| Validation | Present tense shines in customer-discovery storytelling | "I'm sitting across from a nurse practitioner who tells me..." is more visceral than a past-tense summary | +| Early Traction | Scene-based memorisation becomes essential as pitches multiply | Founders tell the same story dozens of times; scene-based structure prevents staleness and enables adaptation per audience | +| Growth | Word choice becomes a brand concern | As the company's stories reach wider audiences, profanity and vulgarity boundaries tighten; oddly specific language becomes a differentiator | +| Scale | Performance delegation -- others now tell the company's story | The CEO must train executives, salespeople, and marketers in these delivery techniques, not merely use them personally | + +At the idea stage, the founder is the company's only storyteller. Performance quality and company credibility are one and the same. At scale, the challenge inverts: the founding story is now told by dozens of people who were not there. Scene-based memorisation scales better than scripts because it allows each teller to navigate the story in their own voice while hitting the same emotional beats. + +--- + +## Output Template + +```markdown +# Performance Preparation Sheet + +## Story Title / Context +[What is being delivered, to whom, in what setting] + +## Tense Plan +- **Primary tense:** [Present / Past] +- **Tense shifts:** + - Shift to [past/present] at [moment] because [reason] + - Shift to [past/present] at [moment] because [reason] + +## Scene Map (max 7) +| # | Location | Key Action / Dialogue | Emotional Tone | +|---|----------|-----------------------|----------------| +| 1 | [Place] | [What happens] | [e.g., light, tense, vulnerable] | +| 2 | [Place] | [What happens] | [Tone] | +| ... | ... | ... | ... | + +## Memorised Opening (first 2-3 sentences) +[Write them here, word for word] + +## Memorised Close (last 2-3 sentences) +[Write them here, word for word] + +## Hero-Story Check +- **Vulnerability shared before success:** [The imperfect moment] +- **Accomplishment marginalised to:** [The small step told, not the full victory] + +## Word-Choice Notes +- **Replace:** [generic word] with [specific word] +- **Remove:** [unnecessary profanity / pop-culture reference] +- **Add specificity:** [where] + +## Context Adaptation +- **If boardroom:** [Adjust formality, reduce nervousness display, increase authority signals] +- **If pitch stage:** [Allow vulnerability, open with laugh, end on heart] +- **If dinner table:** [Shorten, increase conversational pacing, make eye contact with all] +``` + +--- + +## Related Skills + +- **[Building Story Stakes](building-story-stakes.md)** -- Delivery techniques bring stakes to life; the Hourglass is a performance technique as much as a structural one, requiring physical acts of pacing and volume control. +- **[Storytelling Truth and Vividness](storytelling-truth-and-vividness.md)** -- Cinema of the Mind provides the scenes that scene-based memorisation depends on; without physical locations for each moment, there is nothing to memorise except words. +- **[Emotional Impact in Stories](emotional-impact-in-stories.md)** -- Surprise and humour are designed on paper but executed in the room; timing and tonality determine whether the structural design actually produces feeling. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- Leaders perform in contexts where the delivery stakes are organisationally consequential; this skill provides the technique, and the leadership skill provides the strategic when-and-why. +- **[Leadership Voice and Presence](../leadership/leadership-voice-and-presence.md)** -- The vocal, physical, and timing techniques for story delivery directly strengthen the broader presence that leadership communication depends on. +- **[Tone and Engagement](../writing/tone-and-engagement.md)** -- The tonal calibration skills for written communication parallel the vocal and emotional register choices required in live story performance. diff --git a/plugins/foreman/content/skills/storytelling/story-structure-and-arc.md b/plugins/foreman/content/skills/storytelling/story-structure-and-arc.md new file mode 100644 index 0000000..42830ab --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/story-structure-and-arc.md @@ -0,0 +1,228 @@ +--- +name: "story-structure-and-arc" +description: "Teaches the five-second moment principle, the relationship between surface spectacle and underlying transformation, and the But and Therefore technique for creating narrative momentum. Use when a pitch or presentation feels flat despite containing good material, when a founder's narrative lacks forward movement, when replacing chronological recounting with cause-and-effect storytelling, or when diagnosing why an audience disengages midway through a talk." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative-arc + - five-second-moment + - but-and-therefore + - story-structure + - pitch + - presentation + - persuasion + - transformation + - momentum +related_skills: + - what-is-a-story + - finding-your-stories + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Story Structure and Arc + +FIVE SECONDS -- Jurassic Park is not a dinosaur movie. Every great story is actually about a five-second moment of change, and all the rest is scaffolding. + +Steven Spielberg spent sixty-three million dollars rendering velociraptors, brachiosaurs, and a Tyrannosaurus rex so lifelike that audiences forgot they were watching computer-generated images. Yet the moment in the film that audiences remember most, the scene that gives the story its emotional weight, contains no dinosaurs at all. It is a man sitting in a tree with two sleeping children, letting a fossilised raptor claw fall from his hand. Alan Grant, who despised children at the start of the film, has evolved. Five seconds. Story over. + +The entire storytelling architecture rests on this observation. Every great story -- regardless of length, depth, or tone -- exists to deliver a single moment of transformation. That moment lasts about five seconds. Everything else in the narrative is infrastructure designed to bring that moment to the greatest possible clarity. The dinosaurs, the car chases, the market data, the product demos -- these are not the story. They are the scaffolding that makes the five-second moment land. + +The second structural principle is equally counterintuitive: the words that connect one scene to the next matter more than the scenes themselves. Replace "and then" with "but" and "therefore," and a flat recitation of events transforms into a narrative with momentum, surprise, and causation. These two principles -- the five-second moment and the But and Therefore technique -- form the load-bearing structure of any story worth telling. + +--- + +## The Framework + +### The Five-Second Moment + +All stories are about tiny moments. The purpose of every other element -- character, setting, conflict, humour, suspense -- is to deliver the audience to that moment with maximum emotional clarity. + +The five-second moment is defined as the instant when something changes forever in a person's life: + +> You fall in love. You fall out of love. You discover something new about yourself or another person. Your opinion on a subject dramatically changes. You find forgiveness. You reach acceptance. You sink into despair. You make a life-altering decision. + +The diagnostic question is simple: **does this story contain a moment when someone's internal state shifts?** If the answer is no, the material is an anecdote, a romp, or a report -- potentially entertaining, but structurally incapable of moving an audience at the level where decisions and loyalties are formed. + +**The Jurassic Park principle:** Big stories contain tiny, utterly human moments. The spectacle serves the moment, not the reverse. Consider: + +| Film | What the audience thinks the story is about | What the story is actually about | The five-second moment | +|------|---------------------------------------------|----------------------------------|----------------------| +| Jurassic Park | Dinosaurs | A man learning to love children | Grant lets go of the fossil claw | +| Raiders of the Lost Ark | Finding the Ark of the Covenant | A scientist finding faith | Indy closes his eyes before the Ark opens | +| "Charity Thief" | Being stranded and impersonating a charity worker | Discovering he knows nothing about loneliness | A widower tells him about his dead wife | +| "This Is Going to Suck" | A near-death car accident | Discovering that friends are family | Emergency-room doors open to reveal his friends | + +In every case, removing the spectacle (dinosaurs, car crashes, snakes, robbery) would not destroy the story. Removing the five-second moment would. + +**The entrepreneurial translation** is uncomfortable but necessary. Most founders' pitch stories are structured around spectacle -- the dramatic pivot, the overnight traction, the improbable partnership. These are the dinosaurs. They attract attention, but they do not create lasting connection. The five-second moment in a founder's story is almost always smaller: the instant a customer's words reframed the entire problem. The evening a co-founder said something that changed the founder's understanding of why they were building this company. The morning the metrics dashboard showed something that contradicted everything the team believed. + +Audiences cannot connect to your miraculous product-market fit. They can connect to the moment you realised you had been wrong about something fundamental. + +### Building Toward the Moment + +Once the five-second moment is identified, every element of the story must serve it. The principle is clinical: + +- Anything that brings the five-second moment to greater clarity is **strengthened and highlighted**. +- Anything that does not serve the moment is **marginalised, shaded, or removed entirely**. + +This is a subtractive process. The natural impulse is to include every interesting detail, every amusing tangent, every contextual fact. The discipline is to cut everything that does not lead the audience toward the moment of transformation with increasing clarity and emotional investment. + +For a fundraising narrative, this means the market analysis, the competitive landscape, and the traction metrics are not the story -- they are context that either serves or distracts from the five-second moment. If a data point does not illuminate the transformation, it belongs on a supplementary slide, not in the narrative. + +### The But and Therefore Principle + +The second structural principle addresses the connective tissue between scenes, sentences, and ideas. This framework, and independently Trey Parker and Matt Stone of South Park, arrived at the same conclusion: + +**If the words "and then" can be placed between any two scenes, the story is broken.** The ideal connectors are "but" and "therefore" (and their synonyms: however, instead, as a result, except, yet, consequently). + +"And then" stories run on a treadmill. They move chronologically but go nowhere. They report events without establishing causation or opposition. + +"But" and "therefore" stories create a serrated line -- constantly cutting against the grain, zigging and zagging, presenting opposition and consequence rather than mere sequence. + +**The contrast in action:** + +"And then" version (a child's sleepover story): +> My cousin came over for a sleepover, and we went to bed on time and we didn't sleep. And my parents heard us, and they called the police. And they came and saw us watching TV. And we got in trouble. + +"But and therefore" version: +> My cousin came over for a sleepover, **but** we had no intention of sleeping. We went to bed on time, **but** we didn't close our eyes. **Instead** we snuck downstairs to watch TV. **But** my parents heard us -- **except** it wasn't us they heard. It was the TV voices. **Instead of** investigating, they **therefore** assumed burglars were robbing the house, **so** they called the police. **But** they didn't wake us up, because they didn't want us to scare us. The police arrived, **but instead of** finding burglars, they found us watching television. **As a result,** we got in so much trouble. + +Same facts. Radically different momentum. The second version cuts against itself at every turn, creating the sensation of movement and surprise even though the events are linear and the ending is predictable. + +**The power of the negative:** A related technique amplifies the But and Therefore principle. Saying what something is not is almost always more effective than saying what it is, because negation contains a hidden "but" -- it presents both possibilities simultaneously. + +- "I was lost" is not as effective as "I could not find my way home." +- "I was penniless" is not as effective as "I didn't have a penny to my name." +- "Heather is my ex-girlfriend" is not as effective as "Heather is no longer my girlfriend." + +The negative construction implies a world in which the positive was possible, creating depth and movement within a single clause. + +**For entrepreneurs,** the But and Therefore principle is the difference between a pitch that recites milestones and one that makes the audience feel the venture's momentum. "We built the product, and then we launched, and then we got customers" is a timeline. "We built the product for enterprise clients, **but** mid-market companies adopted three times faster. **Therefore** we repositioned the entire go-to-market, **but** that meant renegotiating every existing contract" is a narrative. Same facts. Different effect. + +--- + +## Prompts + +**Prompt 1 -- Five-Second Moment Extraction:** +> Here is a story I plan to tell in [context]: [paste story or describe the events]. Identify the five-second moment -- the instant of genuine transformation. If no such moment exists, say so plainly. If the story has been built around spectacle (the dramatic event) rather than the moment of change, identify the real five-second moment hiding beneath the spectacle and suggest how to restructure around it. + +**Prompt 2 -- But and Therefore Audit:** +> Analyse the following narrative for "and then" disease: [paste narrative]. Highlight every instance where sentences or scenes are connected by sequence ("and," "and then," "next," "after that") rather than by opposition or consequence ("but," "therefore," "however," "as a result," "instead"). Rewrite the flagged sections using But and Therefore connectors, preserving the same facts but creating momentum and causation. + +**Prompt 3 -- Scaffolding Triage:** +> I have a story about [describe the five-second moment]. Here are all the details and events I could include: [list everything]. Apply the scaffolding test: for each detail, assess whether it brings the five-second moment to greater clarity (keep), is neutral (cut), or actively distracts from the moment (definitely cut). Return a prioritised list of elements to include, ordered by their contribution to the moment's emotional impact. + +**Prompt 4 -- Negative Construction Rewrite:** +> Rewrite the following sentences using the power of the negative -- replacing positive statements with their negative equivalents to create hidden "buts" and greater depth: [paste sentences]. For each rewrite, briefly explain what binary option the negative introduces and why it creates more movement than the original. + +--- + +## Use Cases + +**Validation-stage founder restructuring an investor pitch around the five-second moment** + +A healthtech founder's pitch centres on a dramatic stat: 40% of patients in a specific condition category receive the wrong initial treatment. The pitch walks through the problem, the product, the traction, and the ask. It is competent and forgettable. Applying the five-second moment principle, the founder identifies the real story: the afternoon she sat in a hospital waiting room with her father and watched a doctor deliver a diagnosis that she -- with her domain expertise -- knew was wrong, and realised that she could not intervene. That is the moment of transformation. The 40% statistic becomes scaffolding that supports the moment rather than replacing it. The restructured pitch opens with the waiting room, delivers the data as context, and returns to the human moment for the close. Three investors who heard the revised pitch mentioned the waiting room scene in their follow-up emails. None mentioned the statistic. + +**Early-traction CEO eliminating "and then" disease from the company narrative** + +A B2B SaaS company's sales deck tells its story as a chronological sequence: "We started in 2021, and then we launched our MVP, and then we got our first customer, and then we raised our seed round, and then we expanded to three verticals." The CEO applies the But and Therefore principle: "We started in 2021 building for enterprise, **but** our first paying customer was a 50-person startup that found us on Twitter. **Therefore** we rebuilt onboarding for smaller teams -- **but** that meant our enterprise pipeline went cold. **Instead of** retreating, we discovered that mid-market companies churned at half the rate. **As a result,** we repositioned entirely." The revised narrative covers the same ground in the same time but feels like a journey with twists rather than a treadmill with milestones. + +**Growth-stage product leader diagnosing a failed keynote** + +A VP of Product delivers a conference keynote about the company's platform evolution. Audience engagement scores are below average. Post-mortem analysis using the framework reveals two problems: the talk was built around the product's capabilities (spectacle) rather than a moment of customer or team transformation (five-second moment), and every transition between sections used "and" or "next" rather than "but" or "therefore." The VP restructures: the talk now centres on the moment a key customer used the platform in a way the team had never anticipated, which fundamentally changed the product roadmap. Transitions are rebuilt with opposition and consequence. The next keynote scores in the top quartile. + +--- + +## Anti-Patterns + +**1. Mistaking the dramatic event for the five-second moment.** The story of a near-death experience took three years to craft because the narrative kept ending at the car accident. The actual five-second moment -- friends arriving at the emergency room when his parents did not -- was quieter and vastly more powerful. Founders make the identical error when they build narratives around their most dramatic milestone (the huge deal, the viral launch) instead of the quieter moment of genuine change. + +**2. Scaffolding that overwhelms the moment.** When context, data, and backstory consume 90% of the narrative, the five-second moment arrives as an afterthought. The audience has invested attention in the scaffolding and has little left for the payoff. Ruthless cutting is not optional; it is structural. + +**3. Applying But and Therefore mechanically.** The principle describes an orientation, not a formula. Inserting "but" before every sentence produces a staccato rhythm that sounds contrived. The technique works when opposition and consequence are genuine -- when the narrative actually zigs and zags -- not when transitional words are sprinkled as decoration. + +**4. Stories about two things.** A single narrative can contain only one five-second moment. The band-camp beating story carried two separate meanings -- the realisation that people will turn their backs on evil, and the realisation that the world is fundamentally unsafe. These are two stories, not one. Each demands a different beginning and a different arc. Founders who try to make a single pitch story carry two transformations dilute both. + +**5. Using the framework to justify spectacle.** Knowing that Jurassic Park uses dinosaurs as scaffolding does not licence packing a pitch with irrelevant flash. The dinosaurs work because they are causally linked to Grant's transformation -- without them, he never spends time with the children. Scaffolding that does not causally serve the five-second moment is bloat, regardless of how impressive it is. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal five-second moment that explains why this company exists | The moment is everything; scaffolding is minimal because the company barely exists yet | +| Validation | Customer-triggered moments of transformation in the founder's understanding | The five-second moment increasingly involves other people's words and reactions | +| Early Traction | Pivot moments structured with But and Therefore momentum | The narrative must convey a journey of opposition and consequence, not a timeline of milestones | +| Growth | Training the team to find five-second moments in their own domains | Product stories, sales stories, and support stories each need their own moment of change | +| Scale | Institutional narratives built on chains of transformation | The company story is a sequence of five-second moments, each connected by "but" and "therefore" | + +At the idea stage, the founder typically has one five-second moment and very little scaffolding. The craft challenge is making that single moment land with enough force that it carries the entire pitch. + +At early traction and growth, the challenge inverts. Material is abundant -- customers, pivots, team dynamics, competitive battles -- and the temptation is to include everything. The discipline of serving only the five-second moment, and of connecting scenes with opposition and consequence rather than sequence, becomes the primary structural skill. + +--- + +## Output Template + +```markdown +# Story Structure Worksheet -- [Story Title or Context] + +**Teller:** [Name] +**Context:** [Pitch / Keynote / All-hands / Customer conversation] +**Date:** [Date] + +## 1. The Five-Second Moment +**What changed:** [Describe the precise instant of transformation] +**Before state:** [What the protagonist believed, felt, or understood] +**After state:** [What shifted] +**Is this genuinely a moment of transformation?** [Yes / No] + +## 2. Scaffolding Audit +| Element | Serves the moment? | Keep / Cut / Reduce | +|---------|-------------------|---------------------| +| [Detail 1] | [How it connects to the five-second moment] | [Decision] | +| [Detail 2] | [How it connects] | [Decision] | +| [Detail 3] | [How it connects] | [Decision] | + +## 3. But and Therefore Map +[Write the story's scene-by-scene flow using explicit connectors] +- Scene 1: [Description] ... +- **But** Scene 2: [Description] ... +- **Therefore** Scene 3: [Description] ... +- **But** Scene 4: [Description] ... +- **Therefore** Five-second moment: [Description] + +**"And then" count in current draft:** [Number] +**"But / therefore" count in current draft:** [Number] + +## 4. Negative Construction Opportunities +| Original (positive) | Rewrite (negative) | +|---------------------|-------------------| +| [Statement] | [Rewrite with hidden "but"] | +| [Statement] | [Rewrite with hidden "but"] | + +## 5. One-Sentence Story Summary +[I was once [starting state], but then [five-second moment], and now I am [ending state].] +``` + +--- + +## Related Skills + +- **[What Is a Story](what-is-a-story.md)** -- Establishes the transformation requirement that the five-second moment fulfils; read this first if the concept of story-as-change is unfamiliar. +- **[Finding Your Stories](finding-your-stories.md)** -- The five-second moment must be found before it can be structured; Homework for Life is the discovery mechanism. +- **[Story Beginnings and Endings](story-beginnings-and-endings.md)** -- Once the five-second moment is identified, this skill teaches the opposite-of-the-end rule for choosing where to begin. +- **[Building Story Stakes](building-story-stakes.md)** -- Stakes create the tension that makes the five-second moment land; the Hourglass and Breadcrumbs techniques amplify the structural arc built here. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- The four-function framework for change stories operates at the leadership-application layer; the structural techniques here provide the underlying craft. +- **[Creative Shaping and Craft](../creative/creative-shaping-and-craft.md)** -- The broader creative discipline of finding the essence and refining form applies directly to the structural choices of what to include and what to cut in narrative construction. diff --git a/plugins/foreman/content/skills/storytelling/storytelling-truth-and-vividness.md b/plugins/foreman/content/skills/storytelling/storytelling-truth-and-vividness.md new file mode 100644 index 0000000..9326be3 --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/storytelling-truth-and-vividness.md @@ -0,0 +1,216 @@ +--- +name: "storytelling-truth-and-vividness" +description: "Provides an ethical framework for nonfiction storytelling (the Five Permissible Lies) and techniques for creating vivid mental imagery (Cinema of the Mind). Applies when a founder is crafting a company origin story, preparing a keynote, refining a customer case study, or deciding how much to compress or omit from a real narrative. Use when the question is not what to say but how truthfully and vividly to say it." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - truth + - ethics + - vividness + - cinema-of-the-mind + - omission + - compression + - sensory-detail + - nonfiction + - pitching + - narrative-craft +related_skills: + - building-story-stakes + - emotional-impact-in-stories + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# Storytelling Truth and Vividness + +The best storytellers lie -- but only in five specific ways, each with an inviolable rule that separates craft from dishonesty. The framework calls them the Five Permissible Lies of True Storytelling, and they constitute an ethical framework as rigorous as it is practical. Paired with the Cinema of the Mind principle -- the insistence that every moment of a story must exist in a physical location the audience can see -- these two doctrines form the foundation of nonfiction narrative craft. For the entrepreneur who trades in origin stories, customer narratives, and investor updates built on real events, the question is never whether to shape the truth. The question is how to shape it without breaking it. + +--- + +## The Framework + +### Part I: The Five Permissible Lies + +Three caveats govern all five lies. First, storytellers lie only for the benefit of the audience, never for personal gain -- not to appear more noble, mitigate shame, or inflate accomplishment. Second, memory itself is unreliable; each retelling alters the original, so perfect accuracy was never on offer. Third, storytellers never add something that was not already there. The raw material is fact. The craft is selection and arrangement. + +#### Lie 1: Omission + +Every story contains omissions; if it did not, it would never end. Strategic omission removes people, subplots, and details that do not serve the story's core moment. One illustrative example removes an entire hitchhiker -- a vivid, memorable character -- from one of his most performed stories because the hitchhiker's presence would pull the audience's attention away from the porch where the story's emotional centre lives. + +The rule: omit anything that distracts from the five-second moment of transformation. People are the most frequently omitted element. If a third person in a car does not fill a role in the narrative, that person was never in the car. + +**Omission of endings** deserves special attention. The principle holds that storytellers should end their stories in the most advantageous place, even if reality continued. Redemption arcs -- "I did a terrible thing, but then I made up for it" -- make it easy for the audience to remove the story like a coat. The world is back in order; all debts are paid; the listener sleeps well. The best stories leave the world slightly broken. They omit the resolution so the narrative lingers. + +For entrepreneurs: the temptation to wrap every company story in a neat bow is strong. Resist. The pitch that ends with "and then everything worked out perfectly" is forgettable. The one that ends with a question still hanging in the air -- that is the one investors remember at midnight. + +#### Lie 2: Compression + +Compression pushes time and space together to make a story easier to comprehend, visualise, and tell. A Saturday-Sunday sequence becomes a single Saturday afternoon. A geographically sprawling series of events is simplified into a tighter footprint. + +The rule: compress only to reduce needless complexity. Placing scenes closer together also heightens drama and suspense, making the world feel more cinematic. There is never room for unnecessary complication in a story. Stories are rivers; they flow past the audience regardless of whether the listener is still constructing a mental map. + +For entrepreneurs: the eighteen-month product development cycle becomes "one winter." The four-city customer research tour becomes "a week in Detroit." Compression is not dishonesty. It is architecture. + +#### Lie 3: Assumption + +When a forgotten detail is critical to the story, the storyteller makes a reasonable assumption about what it might have been. When the make of a car involved in a pivotal childhood moment cannot be remembered, calling it a station wagon is reasonable -- the most common vehicle on 1970s roads. + +The rule: always assume the most reasonable, most likely version. Never assume something more dramatic or interesting than probability supports. The temptation to upgrade the station wagon to a cherry-red Corvette is precisely the temptation that must be refused. + +#### Lie 4: Progression + +Progression changes the order of events to make a story more emotionally satisfying. This is considered the least common lie and reportedly has never been used by its originator, though he recommends it to others when chronological reality defies narrative expectation. + +The rule: change order only when the real-life sequence undermines the emotional trajectory the audience needs. A story about spreading a brother's ashes at three locations -- a family tree, a strip club, a baseball stadium -- works best when the most emotionally powerful location comes last, even if it happened first. + +For entrepreneurs: if the customer breakthrough happened before the technical crisis, but the story makes more sense with crisis preceding breakthrough, progression is the tool. The facts remain; only their sequence shifts. + +#### Lie 5: Conflation + +Conflation squeezes all the emotion of an extended process into a single moment. Rather than describing gradual change over months, the storyteller locates one scene and declares it the moment of transformation. + +The rule: transform *a* moment into *the* moment. Movies do this relentlessly -- Danny Ocean's crew plans a multimillion-dollar heist in days rather than years, because days are thrilling and years are boring. Shorter stories, whether on stage or in a boardroom, are always more engaging. + +For entrepreneurs: the slow realisation that product-market fit had arrived becomes the single Slack message from a customer that made it undeniable. The gradual loss of faith in a co-founder becomes the one conversation in a parking lot. Conflation is the art of compression applied to interior experience. + +### Part II: Cinema of the Mind + +A great storyteller creates a movie in the minds of the audience. The principle is simple, the execution frequently neglected: always provide a physical location for every moment of the story. + +If the audience knows where the storyteller is at all times, the film is running. If the audience cannot picture the scene, the film has stopped. What remains is lecturing, or essay-reading, or at best a disconnected series of observations. + +**The difference a single sentence makes.** The text demonstrates this with two versions of the same character description. One opens with abstract attributes: "My grandmother was crooked in body and mind, wore dark colours, served food stewed for days." The other opens with a scene: "I'm standing at the edge of my grandmother's garden, watching her relentlessly pull weeds from the unforgiving soil." The character description that follows is identical. Only the second version is a story. + +**Backstory requires a location too.** When a story demands exposition -- family history, financial context, emotional state -- the storyteller must anchor that exposition in a physical place. One example parks the character behind the wheel of a car in a gas-station lot and delivers two minutes of backstory while the audience can see him gripping the steering wheel. The film never stops. + +The alternative -- "Let me tell you about my finances in 1991" -- is not a story. It is a narrator stepping out of the frame to deliver a lecture. The movie has stopped. + +**Technical or historical exposition** should be delivered through anecdote, not explanation. If the audience needs to understand a concept, the storyteller tells the story of the first time they learned that concept. The classroom, the teacher, the moment of comprehension -- all of it keeps the camera pointed at a scene rather than at a lecturer. + +**Sensory specificity matters.** Generic imagery ("a nice house") does nothing. Specific imagery ("a red-brick house on a quiet residential street with a blue door") gives the audience's mind enough to construct the rest. Provide the anchor details; let the audience populate the scene with their own experience. + +--- + +## Prompts + +**Prompt 1 -- Ethical Audit:** +> Here is a true story I plan to tell: [paste narrative]. Apply the Five Permissible Lies framework. Identify what I should omit (people, subplots, endings), where I should compress time or geography, where I might need to make a reasonable assumption, whether the event order should change for emotional impact, and where I should conflate gradual change into a single moment. Flag any point where I may be crossing from craft into dishonesty. + +**Prompt 2 -- Cinema of the Mind Rewrite:** +> Here is a passage from a presentation or story I am preparing: [paste passage]. Rewrite it so that every moment has a physical location the audience can see. Convert any abstract exposition into scene-grounded narrative. Add specific sensory anchors (not generic ones) so the audience's mental movie never stops. + +**Prompt 3 -- Backstory Integration:** +> I need my audience to understand [technical concept / company history / personal background] before the main story can proceed. Help me deliver this exposition without breaking the cinematic frame. Suggest a specific physical location where I can anchor this backstory and a brief anecdote or scene that conveys the information while keeping the film running. + +**Prompt 4 -- Omission Decisions:** +> Here is the full, unedited version of a story I want to tell: [paste]. Identify every person, subplot, and detail that does not serve the core five-second moment of transformation. Recommend what to cut and explain why. Also assess whether the current ending offers too much resolution and suggest where to end earlier for maximum lingering impact. + +--- + +## Use Cases + +**Customer Case Study -- B2B SaaS** + +A marketing team drafts a case study that reads like a chronological log: "In January, the customer signed. In March, onboarding completed. In June, metrics improved." Cinema of the Mind is absent; no scene has a location. Applying the framework: the case study opens in a specific room ("The VP of Operations was standing at a whiteboard covered in red-ink process maps when our implementation lead walked in"). Compression collapses six months into three key scenes. Omission removes two project stakeholders who played no role in the transformation. The result reads like a story, not a spreadsheet. + +**Founder Origin Narrative -- Pre-Seed Pitch** + +A first-time founder tells the story of discovering the problem her company solves. The unedited version spans three years and four cities. Conflation compresses the gradual realisation into a single moment at a hospital bedside. Compression reduces the geography to one city. An assumption fills in a forgotten detail (the specific date becomes "a Tuesday in November" -- reasonable and evocative). The Elephant is planted in the first sentence. Every scene has a location. The three-year journey becomes a four-minute story that an investor can see. + +**Internal All-Hands -- Quarterly Retrospective** + +A COO delivers a quarterly update that begins with "Let me give you some context on Q3." The movie has stopped before it started. Applying Cinema of the Mind: the update opens with a scene ("Three months ago, I was sitting in the Denver airport at 6 a.m., reading a customer email on my phone that changed how I think about our roadmap"). Backstory about Q3 objectives is delivered while the audience can picture the COO in that airport seat. Omission removes two initiatives that did not materially affect the quarter's outcome. The update becomes a narrative the team remembers. + +--- + +## Anti-Patterns + +- **Adding what was never there.** The five lies permit shaping, selecting, and rearranging existing facts. They never permit invention. A founder who adds a customer quote that was never said, a metric that was never measured, or a scene that never occurred has crossed from craft into fabrication. The distinction is non-negotiable. + +- **Lying for personal advantage.** Omitting a co-founder's contribution to make oneself appear more central. Compressing timelines to obscure how long a problem persisted. Conflating another person's insight into one's own epiphany. Each of these violates the first caveat: lies serve the audience, never the teller. + +- **The locationless narrative.** Opening a story, pitch, or presentation with abstract statements ("We believe that the future of healthcare is...") rather than a scene. The audience's mental movie has not started. They are staring at the speaker, not seeing the story. Every opening needs a where. + +- **Describing what needs no description while neglecting what does.** Spending thirty seconds on company credentials (which the audience can read) while skipping the sensory detail of the moment that matters (which only the storyteller can provide). Inversion of emphasis is the most common vividness failure. + +- **Offering the neat redemption.** Ending every company story with "and then it all worked out." The coat comes off easily. The story is forgotten by lunch. Ending with the world still slightly askew -- a question unanswered, a tension unresolved, a cost acknowledged -- gives the narrative staying power. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Compression and conflation dominate: the founder's years of thinking must become one vivid scene | The danger is fabrication; at this stage, there is little track record to draw from, so the temptation to invent is highest | +| Validation | Omission becomes critical: early experiments produce messy, multi-threaded narratives | Cut ruthlessly to the one thread that serves the five-second moment of customer discovery | +| Early Traction | Cinema of the Mind creates differentiation in investor conversations | When every founder has similar metrics, the one who tells a story the investor can *see* wins the meeting | +| Growth | Progression may be needed: the order in which things happened may not match the order in which they are best understood | Internal communications benefit from reordered narratives that build to the insight rather than burying it | +| Scale | All five lies operate simultaneously across dozens of company narratives | The challenge shifts from telling one story well to maintaining truthfulness at institutional scale, where many people shape the narrative | + +At scale, the greatest risk is not individual dishonesty but institutional drift: stories retold so many times that they accumulate embellishments no single person added. Regular audits of the company's core narratives against original facts are the organisational equivalent of the Five Permissible Lies caveats. + +--- + +## Output Template + +```markdown +# Narrative Truth & Vividness Worksheet + +## Core Story +[One-paragraph summary of the true events] + +## Five-Second Moment +[The single moment of transformation this story exists to deliver] + +## Omissions +| Element Removed | Reason | +|-----------------|--------| +| [Person / subplot / detail] | [Does not serve the five-second moment] | +| [Ending / resolution] | [Removes the coat too easily] | + +## Compressions +| Original Timeline / Geography | Compressed Version | Justification | +|-------------------------------|--------------------|---------------| +| [e.g., 6 months, 3 cities] | [e.g., one winter, one city] | [Reduces complexity] | + +## Assumptions Made +| Forgotten Detail | Assumed Version | Why Reasonable | +|------------------|-----------------|----------------| +| [e.g., car model] | [e.g., Honda Civic] | [Most common car in that context] | + +## Progression Changes +| Original Order | New Order | Emotional Rationale | +|----------------|-----------|---------------------| +| [A, B, C] | [C, A, B] | [Most powerful moment must come last] | + +## Conflations +| Gradual Process | Single Moment Chosen | Why This Moment | +|-----------------|----------------------|-----------------| +| [e.g., 8-month realisation] | [e.g., one email on a Tuesday] | [Most vivid, most representative] | + +## Cinema of the Mind Check +| Scene | Physical Location | Sensory Anchors | +|-------|-------------------|-----------------| +| [Scene 1] | [Specific place] | [2-3 concrete details] | +| [Scene 2] | [Specific place] | [2-3 concrete details] | +``` + +--- + +## Related Skills + +- **[Building Story Stakes](building-story-stakes.md)** -- Vividness and truth are the canvas; stakes are the tension stretched across it. The Hourglass technique depends on Cinema of the Mind to work. +- **[Emotional Impact in Stories](emotional-impact-in-stories.md)** -- Surprise, the sole mechanism for emotional impact, requires honest setup; the Five Permissible Lies define the boundaries within which that setup can be shaped. +- **[Story Performance and Delivery](story-performance-and-delivery.md)** -- Present-tense narration amplifies Cinema of the Mind; the two techniques are mutually reinforcing in live delivery. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- Leaders face particular ethical pressure when shaping company narratives; the Five Permissible Lies provide the guardrails. +- **[Finding Your Stories](finding-your-stories.md)** -- The raw moments discovered through Homework for Life gain their power from the sensory detail and honest rendering that vividness techniques provide. +- **[Plain Language and Flow](../writing/plain-language-and-flow.md)** -- Cinema of the Mind depends on concrete, accessible language; the jargon and abstraction that plain language eliminates are the primary enemies of vivid storytelling. diff --git a/plugins/foreman/content/skills/storytelling/what-is-a-story.md b/plugins/foreman/content/skills/storytelling/what-is-a-story.md new file mode 100644 index 0000000..91ee169 --- /dev/null +++ b/plugins/foreman/content/skills/storytelling/what-is-a-story.md @@ -0,0 +1,199 @@ +--- +name: "what-is-a-story" +description: "Defines what qualifies as a genuine story versus an anecdote, romp, or report. Teaches the transformation requirement, the Dinner Test, and the personal-narrative principle. Use when a founder's pitch feels flat despite good content, when team presentations list facts without landing emotionally, when someone confuses a sequence of events with a compelling narrative, or when preparing any communication that must move people rather than merely inform them." +version: "1.0.0" +category: "storytelling" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative + - communication + - pitch + - transformation + - anecdote + - dinner-test + - personal-narrative + - persuasion +related_skills: + - finding-your-stories + - story-structure-and-arc + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +# What Is a Story? + +DINNER TEST -- A story qualifies as a story only when you are a different person at its end than at its beginning. Everything else is an anecdote. + +Winning thirty-four Moth StorySLAMs requires understanding a distinction that most communicators never grasp. The distinction is brutally simple: a story requires transformation. Not excitement, not novelty, not a punchline. Transformation. A human being must start in one state and finish in another. Strip that away, and what remains is a drinking story, a vacation recap, or a quarterly business review that makes the audience wish they had stayed home. + +Most founders believe they are telling stories. They are not. They are recounting events, listing features, or narrating timelines. The difference matters because stories activate neural coupling -- the listener's brain literally mirrors the teller's -- while event sequences activate patience, and eventually its absence. + +--- + +## The Framework + +### The Transformation Requirement + +A story is not a series of remarkable events. It is the record of a change in a human being. The change can be infinitesimal -- a slight shift in perspective, a grudging acceptance, a moment of unexpected gratitude -- but it must be present. Without change, you have what the framework classifies under blunter labels: + +| What You Think You Have | What You Actually Have | Why It Fails | +|---|---|---| +| A great vacation story | An itinerary with adjectives | No one changed; things merely happened in sequence | +| A wild night out | A drinking story | Amusing to the teller, forgettable to everyone else | +| A product demo narrative | A feature walkthrough | The audience learns specifications, not meaning | +| A fundraising "story" | A financial report with anecdotes | Data wrapped in chronology is still data | +| A company origin myth | A timeline | "And then we did X, and then Y happened" is not a story | + +The point is codified with characteristic bluntness: stories that fail to reflect change over time are "the roller-coasters and cotton candy of the storytelling world. Supremely fun and delicious, but ultimately forgettable." + +The implication for entrepreneurs is severe. A pitch that recites milestones -- we built this, we launched that, we grew here -- is a timeline masquerading as a narrative. The investor has heard a hundred timelines this month. What they have not heard is the moment the founder's understanding of the problem fundamentally shifted. That is a story. + +### Personal Narrative, Not Fable + +The framework draws a hard line between personal storytelling and every other form. Folktales, case studies, and third-person anecdotes can entertain, but they cannot create the visceral connection that personal narrative produces. The reason is structural: personal stories demand vulnerability, honesty, and the willingness to reveal something unflattering about the teller. Third-person stories demand none of these. + +This does not mean you can only tell your own experiences. It means you must tell your side of whatever story you share. You become the protagonist, not the narrator. The Holocaust survivors' children in the storytelling workshops do not recite their parents' histories; they tell their own stories, dipping into the past to show how those histories changed them. The distinction sounds subtle. In practice, it separates stories that connect from stories that inform. + +For a founder, this principle rewires the standard investor pitch. Instead of "Our customer had this problem and we solved it," the personal-narrative version becomes: "I watched our first customer struggle with X, and something in that moment changed how I understood our entire market." The protagonist shifts. The vulnerability appears. The audience leans in. + +### The Dinner Test + +The Dinner Test is the framework's quality filter, and it is ruthless in its simplicity. The story you craft for a stage, a boardroom, or a pitch meeting should be recognisably close to the version you would tell a friend over dinner. + +This means: + +- **No theatrical gestures.** If you would not mime the birth of an idea with fluttering hands at a restaurant table, do not do it in a presentation. +- **No performative language.** Alliterative flights of prose, unattributed opening dialogue, and dramatic sound effects fail the test. Nobody begins a dinner-table story with "Boom!" +- **No memorised scripts.** The best storytelling occupies a space between extemporaneous and rehearsed. The audience and the teller enter an implicit contract: both pretend the story is being told for the first time, even when it is not. + +The Dinner Test prevents a specific pathology that afflicts founders who have been coached to "tell their story." They produce something polished, theatrical, and hollow -- a performance rather than a conversation. Audiences sense the artifice instantly. They disengage not because the content is poor, but because the delivery signals inauthenticity. + +### Your Story Only + +A further constraint: you must be the protagonist. People would rather hear what happened to you last night than what happened to your friend, even if your friend's story is objectively better. Immediacy, grit, and inherent vulnerability reside in hearing the account of the person standing before you. It takes no courage to tell someone else's story. It requires no hard truth. + +This is not a prohibition against incorporating others' experiences. It is a requirement to frame them through your own lens. The founder who says "Let me tell you about our customer Maria" is delivering a case study. The founder who says "I sat across from Maria and realised I had been building the wrong product for six months" is telling a story. Same facts. Different protagonist. Entirely different emotional register. + +--- + +## Prompts + +**Prompt 1 -- Transformation Audit:** +> I have a story I plan to use in [context: pitch / all-hands / conference talk]. Here it is: [paste story]. Analyse it against the transformation requirement. Does the protagonist change? If so, identify the precise moment of change and state what the person believed or felt before versus after. If no transformation exists, tell me plainly that this is an anecdote, not a story, and suggest what transformation might be embedded within the same material. + +**Prompt 2 -- Dinner Test Stress Test:** +> Read the following narrative I have prepared for [audience]: [paste narrative]. Apply the Dinner Test. Flag every element that would feel unnatural if I told this to a friend over dinner -- theatrical language, performative phrasing, unattributed opening dialogue, thesis statements before the story begins, or any moment where I am clearly "performing" rather than telling. Rewrite the flagged sections in a conversational register that still retains precision and impact. + +**Prompt 3 -- Protagonist Reframe:** +> I want to tell the following customer/partner/team story: [paste the third-person version]. Rewrite it so that I am the protagonist, telling my side of what happened. Preserve the key facts but shift the emotional centre to my experience -- what I saw, what I felt, what changed in my understanding. Ensure the reframed version demands vulnerability or honesty from me as the teller. + +**Prompt 4 -- Anecdote-to-Story Conversion:** +> Here is something that happened to me that I find interesting but suspect is only an anecdote: [describe the event]. Interrogate it for a possible five-second moment of transformation. If one exists, identify it and sketch a story arc (beginning state, change, ending state). If none exists, tell me honestly that the material is a romp and suggest what adjacent experience might contain the transformation I need. + +--- + +## Use Cases + +**Idea-stage founder preparing a first pitch** + +A solo founder has a two-minute pitch for an accelerator application. The current version opens with market size, moves through the problem statement, and concludes with a product description. By this taxonomy, it is a report. Applying the transformation requirement, the founder identifies the moment she stopped seeing the problem as a nuisance and started seeing it as a systemic failure affecting millions of people. That moment of shifted perception becomes the story's spine. Market data and product details remain, but they now serve the transformation rather than replacing it. The pitch moves from informing to moving. + +**Growth-stage CEO addressing the company after a failed product launch** + +The CEO's initial draft for an all-hands email recounts the timeline of the launch: what was built, what went wrong, what happens next. It is a post-mortem disguised as a narrative. Applying the Dinner Test, the CEO recognises that no one at a dinner table would speak this way. The rewritten version begins with a personal admission -- the moment the CEO realised the team had optimised for speed at the expense of listening to early customer signals. The email becomes a story about a leader who changed her understanding of what "fast" means. The timeline and action items still appear, but they follow the transformation rather than substituting for it. + +**Sales leader training a team on customer conversations** + +A VP of Sales notices that reps deliver polished product narratives that nonetheless fail to close. Diagnosing the problem through the personal-narrative lens, the VP identifies that reps are telling the company's story (third person, no vulnerability) rather than their own side of customer interactions. Training shifts to helping each rep find the moment in their own experience when a customer conversation changed their understanding of the product's value. Reps begin opening calls with those moments. Close rates improve not because the product changed, but because the protagonist did. + +**Validation-stage team running customer-discovery interviews** + +A two-person team conducts thirty interviews using a script that opens with "Let me tell you about our product." Response rates are low and conversations are short. Applying the Dinner Test and the transformation requirement, the team rewrites the opening: instead of telling the product story, the founder describes the specific moment she realised the problem existed -- sitting in a meeting where a decision was made on bad data because no one had a better option. The revised opening invites the interviewee into a shared experience rather than a sales pitch. Conversation length doubles. Three interviewees volunteer to become design partners without being asked. + +--- + +## Anti-Patterns + +**1. The "and then" trap.** Connecting events with "and then" produces a timeline, not a story. If the narrative can be summarised as "first this happened, and then this happened, and then this happened," there is no transformation, only chronology. The presence of interesting events does not compensate for the absence of change. + +**2. Confusing drama with story.** A near-death experience, a dramatic pivot, or a celebrity endorsement is not inherently a story. It took three years to figure out how to tell the story of a near-death and resuscitation -- because the dramatic event was not the transformation. The transformation happened later, in a quieter moment. Founders routinely mistake their most dramatic experience for their best story. They are usually wrong. + +**3. Performing instead of telling.** The moment a storyteller begins "performing" -- theatrical voice, rehearsed gestures, scripted pauses -- the audience shifts from participant to spectator. The Dinner Test exists precisely to prevent this. Founders who have been media-trained are especially susceptible; they produce something smooth and lifeless. + +**4. Telling someone else's story as your own.** Recounting a customer's journey without making yourself the protagonist strips the narrative of vulnerability. The audience receives a case study. Case studies persuade the analytical mind. Stories persuade the whole person. + +**5. Starting with a thesis statement.** "This is a story about resilience" or "You're not going to believe what happened" sets expectations that constrain surprise and telegraph the ending. No one at a dinner table prefaces their story with a content warning about its emotional register. The thesis statement also betrays a lack of confidence in the story itself -- if the material were strong enough, it would not need an introduction explaining what it is about. + +**6. Mistaking length for depth.** A twenty-minute narrative packed with detail is not more story-like than a two-minute narrative with a clear transformation. Length without structural change is merely duration. Many of the most powerful stories in this tradition run under five minutes. Brevity, when paired with genuine transformation, is a feature rather than a limitation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal transformation story | The story IS the company -- the moment the founder's understanding shifted is the only asset | +| Validation | Customer-interaction stories told from the founder's perspective | Transformation evidence now includes others; the founder's arc includes learning from users | +| Early Traction | Pivot and failure stories that demonstrate real change | Stakeholders need to see that setbacks produced genuine shifts in direction, not just revised plans | +| Growth | Scaling the transformation principle to managers and team leads | Every team member needs their own transformation story about the company's mission | +| Scale | Institutional narrative built on accumulated transformation moments | The company's story becomes a chain of transformations, not a timeline of achievements | + +At the idea stage, the founder's personal story and the company's story are functionally identical. The ability to articulate a genuine moment of transformation in sixty seconds may be the single most valuable communication skill available. Investors at this stage are not evaluating the business -- there is barely a business to evaluate. They are evaluating the founder's capacity to see clearly, to learn, and to communicate what they have learned. A transformation story does all three simultaneously. + +At validation and early traction, the protagonist expands. The founder is no longer the only person whose transformation matters. Customer stories -- told from the founder's perspective -- become essential. The key discipline is resisting the temptation to present these as case studies (third person, no stakes for the teller) and instead framing them as moments when the founder's understanding of the market shifted because of something a customer said or did. + +At growth and scale, the challenge shifts from telling one story well to ensuring that dozens or hundreds of people understand what a story actually is -- and stop delivering timelines, reports, and anecdotes in its place. Workshop-style training that teaches the transformation requirement, the Dinner Test, and the protagonist principle across functions produces measurable improvements in sales conversations, internal presentations, and external communications. + +--- + +## Output Template + +```markdown +# Story Diagnostic -- [Context: Pitch / Presentation / Communication] + +**Teller:** [Name] +**Audience:** [Investors / Team / Customers / Board] +**Date:** [Date] + +## 1. Transformation Check +**Starting state:** [What the protagonist believed, felt, or understood at the beginning] +**Ending state:** [What changed -- the five-second moment] +**Is there genuine transformation?** [Yes / No] +**If no:** [This is an anecdote / report / timeline. Identify where transformation might be found.] + +## 2. Dinner Test +**Would you tell it this way at dinner?** [Yes / No] +**Flagged elements:** [List any theatrical, performative, or scripted moments] +**Recommended adjustments:** [Specific rewrites] + +## 3. Protagonist Check +**Who is the protagonist?** [Should be the teller] +**Is vulnerability present?** [Yes / No -- what is at risk for the teller?] +**If third-person:** [Reframe suggestion -- how to make the teller the protagonist] + +## 4. Classification +**This material is a:** [Story / Anecdote / Romp / Report / Timeline] +**If not a story:** [What transformation could be added or uncovered?] + +## 5. Revised Opening +[Two to three sentences that open with forward movement and no thesis statement] +``` + +--- + +## Related Skills + +- **[Finding Your Stories](finding-your-stories.md)** -- Once the definition of a story is clear, the next step is building a systematic practice for discovering them in daily life. +- **[Story Structure and Arc](story-structure-and-arc.md)** -- Understanding what a story is precedes learning how to build one; this companion skill covers the five-second moment and narrative momentum. +- **[Story Beginnings and Endings](story-beginnings-and-endings.md)** -- The transformation requirement directly informs where a story should start and finish. +- **[Storytelling for Leaders](../leadership/storytelling-for-leaders.md)** -- Applies storytelling to organisational change; this skill provides the foundational definitions that make leadership storytelling effective. +- **[Emotional Impact in Stories](emotional-impact-in-stories.md)** -- The surprise and emotional design techniques that convert a transformation moment into genuine audience feeling. +- **[Creative Identity and Purpose](../creative/creative-identity-and-purpose.md)** -- The permission to claim "I am a storyteller" is the same identity shift the creative arts skill addresses; both require overcoming self-doubt about one's right to create. diff --git a/plugins/foreman/content/skills/thinking/building-thinking-strength.md b/plugins/foreman/content/skills/thinking/building-thinking-strength.md new file mode 100644 index 0000000..88715d7 --- /dev/null +++ b/plugins/foreman/content/skills/thinking/building-thinking-strength.md @@ -0,0 +1,218 @@ +--- +name: "building-thinking-strength" +description: "Develops the four internal muscles required for clear thinking -- self-accountability, self-knowledge, self-control, and self-confidence -- using the Clear Thinking strength-building system. Covers setting personal standards above external requirements, choosing exemplars, building a personal board of directors, and practising in sandboxes. Use when blaming external factors for poor outcomes, struggling to say no under social pressure, lacking the confidence to execute a difficult decision, noticing that team standards have drifted toward mediocrity, or seeking a structured approach to personal operating system design." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - clear-thinking + - self-accountability + - self-knowledge + - self-control + - self-confidence + - personal-standards + - exemplars + - mental-models + - clear-thinking-framework + - deliberate-practice +related_skills: + - enemies-of-clear-thinking + - managing-weakness-and-mistakes + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-fortitude-and-resilience +author: "Fatih Guner" +--- + +# Building Thinking Strength + +FOUR PILLARS. Clear thinking requires four internal muscles -- and most people exercise none of them. The Clear Thinking framework moves beyond the diagnostic question (what hijacks your thinking?) to the constructive one (what makes thinking resistant to hijacking?). The answer is not intelligence, nor education, nor access to better information. The answer is four disciplines that function like load-bearing pillars: self-accountability, self-knowledge, self-control, and self-confidence. Remove any single pillar and the structure collapses under pressure. Strengthen all four and decisions begin to compound in the right direction, because the person making them has become structurally harder to deceive -- especially by themselves. + +The distinction from Kahneman's dual-process model is important. Kahneman describes the cognitive architecture -- fast and slow processing. The framework describes the character architecture -- the traits that determine whether a person can actually engage slow processing when it matters, or whether they will default to autopilot despite knowing better. Many founders can explain System 2 thinking fluently and still fail to practise it, because they lack the self-accountability to own their errors, the self-knowledge to see their blind spots, the self-control to resist the emotional impulse, or the self-confidence to act against consensus. Strength, not knowledge, is the bottleneck. + +--- + +## The Framework + +### Pillar 1: Self-Accountability + +Self-accountability is the practice of owning outcomes -- all of them -- regardless of whether external factors contributed. The formulation is deliberately uncompromising: "No one cares about your excuses as much as you do. In fact, no one cares about your excuses at all, except you." + +The concept is not about fault. A founder whose product launch fails because a cloud provider suffered a twelve-hour outage is not "at fault" for the outage. Self-accountability demands, however, that the founder own the response: what contingency plan should have existed, what communication should have been prepared, what architectural redundancy was neglected. The outage is not the founder's fault. The lack of preparation is. + +Three failure modes of low self-accountability: + +- **The excuse cascade.** Each explanation for a missed target contains a grain of truth -- the bus was late, the meeting overran, the competitor moved first -- but the cumulative effect is a narrative in which the founder is never the agent, only the victim. The antidote: "There is always something you can do in the moment today to better your position tomorrow." +- **The wrong side of right.** A founder who knows a co-founder's strategy is superior but champions their own because abandoning it would feel like admitting inadequacy. The ego default and low self-accountability form a feedback loop: each reinforces the other until outcome is sacrificed entirely for self-image. +- **Chronic victimhood.** The slow accumulation of responses that avoid responsibility, until blame becomes the default mode. The framework warns that the people who care most about chronic victims often make things worse by validating the blame narrative rather than challenging it. + +### Pillar 2: Self-Knowledge + +Self-knowledge is the accurate understanding of what you know, what you do not know, what you can do, and where your defaults are most likely to seize control. + +The text draws on Charlie Munger's principle: "When you play games where other people have the aptitude and you don't, you're going to lose. You have to figure out where you have an edge and stick to it." The size of what you know matters less than knowing its boundaries. + +For entrepreneurs, self-knowledge operates at two levels: + +- **Competence boundaries.** Knowing which market, technical, and operational domains you can evaluate with genuine expertise versus which ones you can only evaluate with borrowed confidence. A founder who reads three articles about enterprise sales and begins redesigning the go-to-market strategy has mistaken exposure for competence -- a confusion the ego default actively encourages. +- **Default triggers.** Knowing the specific conditions under which you are most susceptible to each default. One founder becomes impulsive when fatigued. Another becomes ego-defensive when challenged by someone they perceive as lower-status. A third capitulates to social pressure in board meetings but not in team meetings. Self-knowledge makes these patterns visible before they execute. + +### Pillar 3: Self-Control + +Self-control is the ability to create space between stimulus and response -- to experience the emotional impulse without being governed by it. + +The metaphor is precise: some people are corks bobbing on an emotional sea, their direction determined entirely by the current wave. Others seize the helm and steer despite the waves. Both experience the same sea. The difference is not the absence of emotion but the presence of agency. + +The practical dimensions of entrepreneurial self-control: + +- **Consistency over intensity.** Emotional intensity might launch a company; disciplined consistency builds one. The founder who maintains execution rhythm through a difficult quarter produces more value than the founder who sprints brilliantly for two weeks and collapses for three. +- **The present-versus-future trade.** The emotion default wants to win the present moment, even at the cost of sabotaging the future. Self-control is the discipline of asking the core question: "Will this action make the future easier or harder?" +- **Energy allocation.** Every unit of energy spent defending ego, repairing impulsive damage, or recovering from emotional reactions is a unit unavailable for progress. Self-control is ultimately an energy management strategy. + +### Pillar 4: Self-Confidence + +Self-confidence is not optimism, bravado, or the absence of doubt. It is the earned trust in one's ability to handle what comes -- including the hard truths. + +The framework draws a sharp line between confidence and ego. The ego default prevents acknowledging deficiencies. Self-confidence provides the strength to acknowledge them. Confidence without humility is overconfidence -- a weakness, not a strength. Confident people can say "I was wrong" because their identity is not contingent on being right. + +Two operational dimensions for founders: + +- **Outcome over ego.** The CEO who champions a rival's superior proposal -- and gets promoted for it -- exemplifies confidence that serves outcomes rather than self-image. The test: "If you owned 100 percent of this company and couldn't sell it for one hundred years, which solution would you prefer?" +- **The inner dialogue.** Self-confidence is partly a function of how you narrate your own history. Past adversity overcome is the raw material of future confidence. The founder who can say "I have navigated harder situations than this" is drawing on a genuine resource, not a motivational platitude. + +### Strength in Action: How the Pillars Compound + +No single pillar suffices. The text illustrates with a scenario: a founder susceptible to social pressure implements a 24-hour rule for all significant commitments. Creating that safeguard required self-knowledge (recognising the vulnerability), self-confidence (believing a better outcome is possible), self-accountability (deciding to act rather than accept the pattern), and self-control (enduring the short-term discomfort of delaying responses). Remove any pillar and the safeguard never gets implemented -- or collapses at first contact with reality. + +### Raising the Bar: Standards, Exemplars, and Practice + +The framework argues that strength development is fundamentally an environmental and imitative process, not a willpower exercise. + +**Standards.** "Champions don't create the standards of excellence. The standards of excellence create champions." The founder who tolerates mediocre work -- from themselves or their team -- is not suffering from a talent deficit but from a standards deficit. The Kissinger approach: refuse to engage with anything that is not the person's best work, and the standard becomes self-enforcing. + +**Exemplars and the Personal Board of Directors.** Choose role models -- living, dead, or fictional -- whose default behaviour is your desired behaviour. Place them on a mental "personal board of directors." Before significant decisions, ask: "What would [exemplar] do in this position? How would I present this decision to my board?" The exercise creates psychological distance from the defaults and activates aspirational rather than reactive thinking. Munger's standard -- "I never allow myself to have an opinion on anything unless I know the other side's argument better than they do" -- is the kind of bar that reshapes behaviour merely by being articulated. + +**Sandbox practice.** Test new behaviours in low-stakes environments before deploying them under pressure. A founder preparing for difficult board conversations might first practise the reframing discipline in weekly team meetings. Failure in the sandbox is cheap; failure in the boardroom is not. + +--- + +## Prompts + +**Prompt 1 -- Four-Pillar Audit:** +> Assess my current strength across the four pillars. Here is my recent behaviour and context: [describe 3-5 recent decisions, reactions, and outcomes]. For each pillar (self-accountability, self-knowledge, self-control, self-confidence), rate my demonstrated strength, identify the specific gap, and recommend one concrete practice to address it. Be candid -- I am looking for diagnosis, not encouragement. + +**Prompt 2 -- Personal Board of Directors Design:** +> Help me construct a personal board of directors. My current challenges are: [describe top 3 leadership challenges]. My weaknesses are: [describe known patterns]. Recommend 5-7 exemplars (living, historical, or fictional) whose specific traits would address these weaknesses. For each, describe what standard they would set and what question I should ask myself when imagining their perspective on my decisions. + +**Prompt 3 -- Standards Diagnostic:** +> Evaluate the standards operating in my company. Here is what "good enough" looks like in our current practice: [describe quality norms for 3-4 key activities -- code, customer communication, strategic planning, hiring]. Compare these to what excellence would look like in each area. Where is the largest gap between current standard and possible standard? What is the compounding cost of that gap over 12 months? + +**Prompt 4 -- Wrong-Side-of-Right Detection:** +> Review this decision I am defending: [describe the decision and your arguments for it]. Apply the "wrong side of right" test. Am I optimising for being right or for the best outcome? If I owned this company forever and could never sell it, would I still make this choice? Identify whether ego, social approval, or inertia is influencing my position, and describe what the outcome-over-ego alternative looks like. + +--- + +## Use Cases + +**Idea-Stage Founder Building Self-Knowledge Before Market Entry** + +A first-time founder with a data science background plans to enter the direct-to-consumer CPG market after reading case studies of successful DTC brands. Applying the self-knowledge pillar, an advisor asks the founder to map their competence boundaries: where do they have genuine expertise built through repeated practice with feedback, and where are they operating on borrowed confidence? The honest answer: deep expertise in analytics and modelling, zero expertise in supply chain, brand marketing, and retail distribution. Rather than abandoning the venture, the founder redesigns the team composition -- recruiting a co-founder with fifteen years of CPG operations experience and committing to a six-month learning period before making irreversible supply chain commitments. Self-knowledge did not shrink ambition; it restructured execution. + +**Early-Traction B2B Founder Whose Self-Accountability Deficit Is Eroding Team Trust** + +A B2B SaaS founder at $500K ARR has missed three consecutive quarterly targets. In each post-mortem, the narrative follows the same arc: market timing was off, a key prospect went dark, the engineering sprint encountered unexpected technical debt. Each explanation contains truth. The cumulative pattern, however, reveals a self-accountability deficit -- the founder is never the variable, only the context. A coach introduces the framework: "It's all your fault" is not a moral judgment but an operational stance. The founder begins post-mortems with the question "What did I personally contribute to this miss?" The shift is uncomfortable but transformative. Within two quarters, the founder identifies a recurring pattern of overcommitting to sales timelines without consulting engineering -- a fixable behaviour that was invisible under the previous blame-distribution model. + +**Growth-Stage CEO Using Exemplars to Raise Hiring Standards** + +A marketplace CEO at $8M ARR is struggling with inconsistent hiring quality. Some hires are exceptional; others are clearly below the bar. The CEO applies the exemplar framework, selecting three leaders renowned for hiring excellence as personal board members for this specific domain. Before each final-round interview, the CEO asks: "Would [exemplar] hire this person for this role?" The standard shifts from "this person seems good enough" to "this person meets the standard my exemplar would demand." Hiring quality stabilises within two cycles, and the CEO extends the exemplar practice to other domains -- product decisions, board communication, strategic planning -- creating a comprehensive aspirational benchmark system. + +--- + +## Anti-Patterns + +**1. Confusing self-accountability with self-blame.** The framework is about owning responses, not about psychological self-flagellation. A founder who takes accountability for a failed product launch does not spend weeks in self-recrimination; they extract the lesson, implement the change, and move forward. The distinction matters: self-blame is the ego default wearing a disguise of humility, consuming energy in performance of guilt rather than investing it in improvement. + +**2. Treating self-knowledge as a static inventory.** "I know my strengths and weaknesses" is a statement that should trigger immediate suspicion. Competence boundaries shift as markets evolve, new team members arrive, and the founder's own skills develop or atrophy. Self-knowledge is a continuous practice, not a completed exercise. The founder who assessed their capabilities at seed stage and has not updated the assessment at Series A is navigating with an outdated map. + +**3. Mistaking rigidity for self-control.** Self-control is the ability to choose response rather than react. It is not the elimination of emotion or the suppression of intuition. A founder who responds to every stimulus with robotic detachment has not achieved self-control; they have achieved emotional disconnection, which carries its own catastrophic failure modes -- particularly in people management and customer empathy. + +**4. Building a personal board of flatterers.** The exemplar framework fails if the selected role models are chosen for comfort rather than challenge. A board composed entirely of people who validate the founder's existing worldview provides social reinforcement, not standards elevation. The criterion is precise: exemplars should be people whose default behaviour is your desired behaviour, not people whose existing behaviour matches your current one. + +**5. Applying the framework only to others.** The four pillars are self-directed tools. A founder who diagnoses their team's lack of self-accountability while exempting themselves from the same scrutiny has missed the entire point. The system begins with the mirror, not the window. + +--- + +## By Stage + +| Stage | Pillar Priority | Key Difference | +|-------|----------------|----------------| +| Idea | Self-Knowledge + Self-Confidence | Founders need the self-knowledge to assess whether they have a genuine edge and the self-confidence to pursue a contrarian vision despite social pressure to "be realistic." | +| Validation | Self-Accountability + Self-Knowledge | Negative customer signals demand self-accountability (owning what the feedback means) and self-knowledge (distinguishing genuine insight from ego-protective dismissal). | +| Early Traction | Self-Control + Self-Accountability | The operational intensity of early traction tests self-control daily. Self-accountability prevents the pattern of externalising blame when early systems break. | +| Growth | All four + Standards | Growth exposes every pillar deficit. The leader's task shifts from personal strength to institutional standards -- building the environment where the team's default behaviour matches the desired behaviour. | +| Scale | Exemplars + Institutional Design | At scale, the CEO's personal pillars must become organisational architecture. Exemplar standards must be embedded in hiring criteria, performance systems, and decision protocols that outlast any individual. | + +At the idea and validation stages, the four pillars are deeply personal -- the founder against their own defaults. The critical intervention is building self-knowledge early, before the ego default has time to construct an elaborate self-narrative that becomes resistant to update. + +At growth and scale, the challenge becomes transmission. A CEO with strong personal pillars but no system for transmitting those standards produces an organisation that depends entirely on the CEO's presence -- a fragile structure. The insight that "what may look like discipline often involves a carefully created environment" points to the solution: design the environment so that the right behaviour is the easy behaviour, for the entire organisation, not just the founder. + +--- + +## Output Template + +```markdown +# Thinking Strength Assessment -- [Name / Role] + +**Date:** [Date] +**Context:** [Current stage, key challenges, recent decisions] + +## Four-Pillar Diagnostic + +| Pillar | Current Strength | Evidence | Primary Gap | Recommended Practice | +|--------|-----------------|----------|-------------|---------------------| +| Self-Accountability | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Knowledge | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Control | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Confidence | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | + +## Standards Assessment +- Current operating standard: [Description] +- Exemplar-level standard: [Description] +- Gap cost (annualised): [Estimated impact of the standards gap] + +## Personal Board of Directors + +| Exemplar | Domain | Standard They Set | Decision Test | +|----------|--------|-------------------|---------------| +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | + +## Wrong-Side-of-Right Check +- Decision most at risk of ego influence: [Description] +- 100-year ownership test result: [What changes if ego is removed] + +## 30-Day Strength-Building Plan +1. [Specific pillar + specific practice + specific frequency] +2. [Specific pillar + specific practice + specific frequency] +3. [Specific pillar + specific practice + specific frequency] +``` + +--- + +## Related Skills + +- **[Enemies of Clear Thinking](enemies-of-clear-thinking.md)** -- The diagnostic companion: identifies which defaults are active so the founder knows which pillar needs reinforcement. +- **[Managing Weakness and Mistakes](managing-weakness-and-mistakes.md)** -- Completes the system by addressing what happens when strength is insufficient: safeguards for weakness and protocols for error recovery. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's cognitive architecture explains why the four pillars are necessary; without self-control and self-knowledge, System 2 engagement remains theoretical. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Translates the four pillars into daily decision habits, particularly the reframing techniques that require self-knowledge. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- Epictetus's dichotomy of control aligns with the self-knowledge pillar: knowing what you can and cannot influence is foundational to both frameworks. +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- The Stoic discipline of endurance under adversity maps directly to the self-control and self-confidence pillars. diff --git a/plugins/foreman/content/skills/thinking/defining-and-exploring-problems.md b/plugins/foreman/content/skills/thinking/defining-and-exploring-problems.md new file mode 100644 index 0000000..73d17ed --- /dev/null +++ b/plugins/foreman/content/skills/thinking/defining-and-exploring-problems.md @@ -0,0 +1,202 @@ +--- +name: "defining-and-exploring-problems" +description: "Teaches the discipline of correct problem definition and structured solution exploration before any evaluation begins. Covers the problem-solution firewall, root cause identification, the premortem, second-order thinking ('and then what?'), binary thinking traps, integrative Both-And options, and opportunity cost analysis through the 3-Lens Principle. Use when a team is jumping to solutions before understanding the problem, when a founder suspects they are treating symptoms rather than causes, when only two options seem to exist, when opportunity costs are unclear, or when first-conclusion bias is narrowing the solution space." +version: "1.0.0" +category: "thinking" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - problem-definition + - root-cause-analysis + - second-order-thinking + - binary-thinking + - opportunity-cost + - premortem + - integrative-thinking + - decision-making + - solution-space +related_skills: + - thinking-fast-and-slow + - decision-making-under-pressure + - evaluating-and-deciding + - wanting-what-matters + - stoic-problem-solving + - scenario-planning + - systems-thinking +author: "Fatih Guner" +--- + +# Defining and Exploring Problems + +WRONG PROBLEM. Most failed decisions do not come from wrong answers -- they come from wrong questions. A room of intelligent people converges on a plausible-sounding problem statement within minutes, pivots immediately to solutions, and spends weeks executing against a target that was never the right one. The Clear Thinking framework calls this the social default: the collective instinct to accept the first definition everyone agrees on and move forward, because solving problems feels productive while defining them feels like stalling. The result is organisations that are perpetually busy and perpetually unimproved -- extinguishing flames that reignite because no one addressed the fire. Define the problem correctly and the solution often becomes obvious. Define it incorrectly and no amount of analytical sophistication will rescue the outcome. + +--- + +## The Framework + +The process divides into two distinct phases -- defining the real problem, then exploring the full solution space -- and the single most valuable discipline is keeping them apart. + +### Phase 1: Define the Problem + +**The Definition Principle.** Take responsibility for defining the problem yourself. Do not let someone else's framing become your framing by default. If you cannot explain the problem to a twelve-year-old without resorting to jargon, you do not yet understand it well enough to make a decision about it. + +**The Root Cause Principle.** Distinguish the disease from the symptoms. The diagnostic question is deceptively simple: "What would have to be true for this problem not to exist in the first place?" + +The text illustrates this with Downtown Dog Rescue in Los Angeles, where founder Lori Weise discovered that 30 percent of shelter dogs were owner surrenders -- families who loved their pets but could not afford to feed them. The obvious problem ("how do we get more people to adopt?") was the wrong problem. The root cause was economic hardship among existing owners. Solving for that reduced shelter intake by 75 percent at lower cost than housing the animals. + +Three operational disciplines protect this phase: + +1. **The Problem-Solution Firewall.** Hold two separate meetings: one to define the problem, one to solve it. When both happen in the same session, type-A teams spend ninety seconds on definition and fifty-eight minutes on solutions. The question that unlocks the definition meeting: "What do you know about this problem that other people in the room don't know?" It forces participants to stop signalling with shared information and start revealing private information. + +2. **The Test of Time.** Ask whether a proposed solution will fix the problem permanently or merely defer it. If the problem will return, you are treating a symptom. Short-term fixes signal to others that action is being taken; they do not signal that progress is being made. Energy channelled toward short-term solutions depletes energy available for long-term ones. + +3. **Write It Down.** Articulate the problem statement in writing and revisit it the next day. Jargon in the description is a reliable indicator that understanding is shallow. If the statement survives overnight scrutiny and reads clearly in plain language, the definition is likely sound. + +### Phase 2: Explore Possible Solutions + +Once the problem is defined, the temptation is to seize the first plausible solution. The framework identifies three traps at this stage, each with a corresponding countermeasure. + +**Trap 1: Ignoring Brutal Reality (The Stockdale Paradox).** Admiral James Stockdale, the highest-ranking US prisoner of war in Vietnam, observed that the optimists -- those who kept predicting release by Christmas, then Easter, then Thanksgiving -- were the ones who died. "You must never confuse faith that you will prevail in the end with the discipline to confront the most brutal facts of your current reality." Entrepreneurs who build solutions on wishful assumptions about market timing, customer behaviour, or competitive response are running the same risk. The Bad Outcome Principle demands imagining not just the ideal future but the ways things could go wrong and how you would overcome each. + +**Trap 2: Binary Thinking.** When only two options present themselves -- launch or don't, hire or don't, pivot or don't -- it is almost always a sign that the problem's dimensions have been prematurely reduced. The framework calls this "stopping thinking" disguised as clarity. + +The antidotes: + +| Safeguard | Method | +|-----------|--------| +| **The 3+ Principle** | Force at least three credible options before evaluating any. If only two exist, develop a third. Even if the third is never chosen, the work of generating it deepens understanding. | +| **Remove an Option** | Imagine each existing option is off the table. "What would I do if staying were not possible?" or "What would I do if leaving were not possible?" The constraint forces creative reframing. | +| **Both-And Thinking** | Rather than choosing between X and Y, ask whether a solution exists that combines the best elements of both. Roger Martin calls this integrative thinking. Isadore Sharp built the Four Seasons by combining the intimacy of a small hotel with the amenities of a large one -- a Both-And solution that the industry's binary framing had made invisible. | + +**Trap 3: Invisible Opportunity Costs.** Every option chosen is an option forgone. Charlie Munger's observation -- "Intelligent people make decisions based on opportunity costs; it's your alternatives that matter" -- is simple to state and routinely ignored in practice. + +The **3-Lens Principle** structures this analysis: + +- **Lens 1: Compared with what?** The direct comparison most people default to. +- **Lens 2: And then what?** The second-order consequences -- what happens after what happens next. This is where second-order thinking separates competent decision-makers from exceptional ones. +- **Lens 3: At the expense of what?** The hidden costs in time, energy, relationships, and foregone alternatives that never appear on a spreadsheet. + +Andrew Carnegie demonstrated all three lenses when, as a young railroad employee, he ordered burning of train cars blocking the entire system rather than spending days salvaging cargo. The visible cost (destroyed cargo) was dwarfed by the invisible cost (days of system-wide shutdown). His boss made the approach standard procedure. + +Most entrepreneurs default to Lens 1 because it deals in direct, visible costs -- the numbers that appear on a spreadsheet. Lens 2 and Lens 3 require imagination: the ability to trace consequences forward in time and to see what is absent rather than what is present. Charlie Munger's observation bears repeating: "Intelligent people make decisions based on opportunity costs; it's your alternatives that matter." The quality of the decision depends on the quality of the alternatives considered, and alternatives cannot be considered if they remain invisible. + +The premortem -- Stoic in origin (Seneca's premeditatio malorum), psychological in modern formulation -- complements the three lenses by forcing explicit attention to downside scenarios. The text cites venture capitalist Josh Wolfe: "Failure comes from a failure to imagine failure." The premortem is not pessimism. It is preparation. The hardest setbacks to recover from are the ones that were never anticipated, because they arrive when no contingency exists and emotion fills the vacuum that planning should have occupied. + +--- + +## Prompts + +**Prompt 1 -- Root Cause Diagnosis:** +> "I am dealing with the following problem: [describe situation]. Apply the Root Cause Principle. Ask 'What would have to be true for this problem not to exist in the first place?' Work backward from symptoms to underlying causes. Identify at least three possible root causes, rank them by likelihood, and suggest how to test which is the real one." + +**Prompt 2 -- Binary Thinking Breaker:** +> "I am choosing between [Option A] and [Option B] for my [stage] startup in [sector]. Apply the 3+ Principle, the Remove-an-Option safeguard, and Both-And integrative thinking to generate at least three additional options I have not considered. For each new option, explain what it reveals about the problem that binary framing conceals." + +**Prompt 3 -- Second-Order Consequence Map:** +> "I am considering [decision] for my company. Apply the 3-Lens Principle: (1) Compared with what alternatives? (2) And then what -- trace second-order and third-order consequences for each option over 6, 12, and 36 months. (3) At the expense of what -- identify hidden opportunity costs in time, capital, team focus, and optionality. Present findings in a structured table." + +**Prompt 4 -- Problem-Solution Firewall:** +> "My team has converged on this problem definition: [problem statement]. Before we move to solutions, stress-test this definition. Is it addressing a root cause or a symptom? Does it use jargon that masks shallow understanding? Would it pass the Test of Time -- would a solution to this problem fix things permanently or merely defer them? Rewrite the problem statement if the original is flawed." + +--- + +## Use Cases + +**SaaS Founder Treating Churn Symptoms** + +A Series A SaaS company in the HR-tech space sees monthly churn rising from 3 percent to 5 percent. The leadership team convenes and within minutes converges on "we need better onboarding." Resources shift to redesigning the first-week experience. Three months later, churn is unchanged. The problem was never onboarding -- it was that the product lacked a critical integration with the payroll system that mid-market customers (the fastest-growing segment) required. The team had treated the most visible symptom (users leaving after month two, which "looked like" an onboarding problem) rather than applying the root cause question: "What would have to be true for these customers not to leave?" Writing out the problem statement would have surfaced the jargon problem immediately -- "onboarding friction" is a label, not a diagnosis. + +**Pre-Seed Founder Stuck in Binary Framing** + +A solo founder with a working prototype for a supply-chain visibility tool faces what feels like a binary choice: accept a $150K angel investment at unfavourable terms or bootstrap with consulting revenue. The 3+ Principle generates three additional options: a revenue-based financing arrangement, a strategic pilot with a logistics company that would fund development in exchange for exclusivity, and a Both-And approach -- accepting the angel but negotiating a smaller cheque alongside a paid pilot. The third option, invisible under binary framing, provides capital, validates the product, and creates a reference customer simultaneously. + +**Growth-Stage E-Commerce Company Ignoring Opportunity Costs** + +A D2C brand generating $12M in annual revenue is evaluating whether to build an in-house fulfilment centre. The team focuses almost exclusively on Lens 1 (build vs. outsource cost comparison). Applying Lens 2 ("And then what?") reveals that in-house fulfilment requires hiring a warehouse operations team, which diverts leadership attention from product development during a critical expansion window. Lens 3 ("At the expense of what?") surfaces the real cost: the two planned product launches that would be delayed by six months because the founder's bandwidth is consumed by logistics. The Lens 3 cost exceeds the Lens 1 savings by a factor of four. + +**Validation-Stage EdTech Founder Solving the Wrong Problem** + +A founder building an AI tutoring platform observes that user engagement drops sharply after the first session. The team diagnoses the problem as "weak onboarding UX" and spends six weeks redesigning the first-session flow. Engagement does not improve. Applying the root cause question -- "What would have to be true for this problem not to exist?" -- reveals that the issue is not onboarding but content: the platform's practice questions are calibrated for grade-level students, but the actual users are adult learners preparing for professional certifications. The problem was never "how do we make the first session stickier?" but "are we serving the users who are actually showing up?" Writing the problem statement in plain language would have exposed the mismatch immediately: "Users leave after one session" describes a symptom. "Our content does not match the needs of the users who find us" describes a cause. The six weeks spent on onboarding redesign cannot be recovered. + +--- + +## Anti-Patterns + +**Confusing speed with competence.** Entrepreneurs wear rapid decision-making as a badge of honour. There is a difference between moving quickly on reversible decisions (which is wise) and collapsing the problem-definition phase because it feels unproductive (which is reckless). The social default rewards the appearance of decisiveness. The market rewards the reality of solving the right problem. + +**Anchoring on the first credible problem statement.** The first person in the room to articulate a plausible diagnosis often sets the frame for everyone else. Once a problem is named, the team shifts to solution mode and rarely revisits whether the name was accurate. Treating the first lens into an issue as the definitive lens is the single most common source of wasted organisational effort. + +**Applying the framework to trivial decisions.** Not every decision warrants root cause analysis and three-lens evaluation. Using heavyweight problem-definition for reversible, low-consequence choices is its own form of poor judgment. Reserve this discipline for decisions where the cost of solving the wrong problem is high. + +**Mistaking Both-And thinking for lack of conviction.** Integrative solutions can look like indecision to team members accustomed to binary framing. A founder who says "we are doing both" needs to articulate why the combination is strategically coherent, not merely a failure to choose. + +**Falling in love with the root cause analysis process.** Definition is not an end in itself. The purpose of separating definition from solution is to improve the quality of the solution phase, not to defer it indefinitely. If you have been defining the problem for weeks and cannot articulate it in two sentences of plain language, the process has become a refuge from action. The framework is blunt about this: "There is no purpose to knowing what you should do and not doing it." + +**Ignoring opportunity costs because they are invisible.** Most people focus exclusively on direct costs -- the money, the time, the effort that a decision requires. Hidden costs -- the forgone alternatives, the deferred projects, the relationships not maintained -- never appear on a balance sheet and therefore never enter the analysis. The 3-Lens Principle exists precisely to make these invisible costs visible, but it requires discipline to apply consistently when the visible costs are already demanding full attention. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder defines the problem they are solving for customers -- the root cause behind the pain they intend to address. | The most common error is building a solution to a problem no one actually has. Root cause analysis is applied to customer pain, not internal operations. | +| Validation | Testing whether the defined problem matches real customer behaviour. | The 3-Lens Principle reveals opportunity costs of pursuing one customer segment over another. Premortems expose assumptions baked into the MVP hypothesis. | +| Early Traction | Distinguishing growth problems from product problems. Churn, slow sales cycles, and support ticket volume are symptoms that can point to very different root causes. | The problem-solution firewall becomes an operational discipline for the leadership team -- separate meetings for diagnosis and action. | +| Growth | Multiple fires burn simultaneously. The temptation to treat symptoms intensifies because there is never enough time. | Second-order thinking becomes critical: every resource allocation decision forecloses other options. Opportunity cost analysis scales with the complexity of the business. | +| Scale | Organisational complexity makes root causes harder to identify. Information is filtered through multiple layers before reaching decision-makers. | The Root Cause Principle must be paired with high-fidelity information-gathering -- going to the source rather than relying on abstractions that have passed through several management layers. | + +A recurring pattern across stages: the earlier a problem is correctly defined, the cheaper it is to solve. At the idea stage, redefining the problem costs a conversation. At growth stage, it costs a quarter's roadmap. At scale, it costs a reorganisation. The compounding cost of solving the wrong problem is the strongest argument for investing disproportionate time in the definition phase -- particularly when the social default is screaming that you should be doing something rather than understanding something. + +The premortem -- imagining what could go wrong before it does -- scales differently across stages as well. At the idea stage, the relevant premortems are existential: "What if no one wants this?" At early traction, they become operational: "What if our biggest customer churns?" At scale, they become systemic: "What if the regulatory environment shifts?" The habit of anticipating failure is the same; the scope of the anticipation widens with the complexity of the business. + +--- + +## Output Template + +```markdown +# Problem Definition and Solution Exploration + +## Problem Statement (Plain Language) +[Two sentences maximum. No jargon. If a twelve-year-old cannot understand this, rewrite it.] + +## Root Cause Analysis +- **Visible symptom(s):** [What is being observed] +- **Root cause hypothesis:** [What would have to be true for this problem not to exist] +- **Test of Time check:** Will solving this root cause fix the problem permanently? [Yes/No + reasoning] +- **Validation method:** [How we will confirm this is the real root cause, not another symptom] + +## Solution Space (Minimum 3 Options) + +| Option | Description | Second-Order Consequences (Lens 2) | Hidden Opportunity Costs (Lens 3) | +|--------|-------------|-------------------------------------|-----------------------------------| +| A | [description] | [and then what?] | [at the expense of what?] | +| B | [description] | [and then what?] | [at the expense of what?] | +| C | [description] | [and then what?] | [at the expense of what?] | +| Both-And? | [integrative option combining elements] | [and then what?] | [at the expense of what?] | + +## Binary Thinking Check +- Are we framing this as only two options? [Yes/No] +- If yes, what would we do if Option A were impossible? Option B? +- What integrative Both-And option exists? + +## Recommendation +[Which option best addresses the root cause, survives the Test of Time, and has the most favourable second-order consequences relative to opportunity costs] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Covers the cognitive biases (anchoring, availability, confirmation) that distort the problem-definition phase. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Addresses the speed-versus-accuracy trade-off when time is scarce; complements the problem-solution firewall with reframing techniques. +- **[Evaluating and Deciding](evaluating-and-deciding.md)** -- The natural sequel: once the problem is defined and the solution space explored, this skill covers criteria weighting, margin of safety, and execution. +- **[Stoic Problem-Solving](../stoic/stoic-problem-solving.md)** -- Marcus Aurelius's reverse clause and creative reframing of obstacles; a philosophical complement to the structural approach presented here. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- Extends the Bad Outcome Principle into a formal methodology for imagining multiple futures and stress-testing strategies. +- **[Systems Thinking](../frameworks/systems-thinking.md)** -- Provides the analytical lens for tracing root causes through feedback loops and emergent behaviour in complex systems. +- **[Strategic Questioning](../leadership/strategic-questioning.md)** -- The leadership practice of leading through questions rather than answers shares the same premise: better questions produce better solutions. diff --git a/plugins/foreman/content/skills/thinking/enemies-of-clear-thinking.md b/plugins/foreman/content/skills/thinking/enemies-of-clear-thinking.md new file mode 100644 index 0000000..1329e14 --- /dev/null +++ b/plugins/foreman/content/skills/thinking/enemies-of-clear-thinking.md @@ -0,0 +1,205 @@ +--- +name: "enemies-of-clear-thinking" +description: "Diagnoses the four biological defaults that hijack entrepreneurial judgment -- emotion, ego, social conformity, and inertia -- using the Clear Thinking framework. Maps how each default manifests in startup contexts and provides recognition patterns for identifying when autopilot has seized control. Use when reacting impulsively to bad news, defending a position for ego rather than merit, conforming to industry consensus without independent analysis, or resisting a necessary pivot despite mounting evidence." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-defaults + - clear-thinking + - decision-making + - self-awareness + - emotion + - ego + - social-pressure + - inertia + - autopilot + - clear-thinking-framework +related_skills: + - building-thinking-strength + - managing-weakness-and-mistakes + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-self-awareness +author: "Fatih Guner" +--- + +# Enemies of Clear Thinking + +AUTOPILOT. Most consequential decisions are not made by conscious thought. They are made by biological autopilot -- four default programmes running beneath awareness, producing outputs the decision-maker mistakes for deliberate choice. The Clear Thinking research into real-world judgment failure reveals a pattern that Kahneman's System 1/System 2 model identifies at the cognitive level but does not fully operationalise at the behavioural one: between stimulus and response sits a gap, and in that gap, one of four defaults -- emotion, ego, social conformity, or inertia -- rushes in to fill the vacuum before reason can arrive. The entrepreneur who cannot name which default is driving a decision has already lost control of it. + +The critical insight is that the failure point is not dramatic. It is ordinary. The moments that determine outcomes are not the boardroom showdowns or the fundraising pitches. They are the unremarkable Tuesday afternoon reactions -- the snapped reply to a co-founder, the silent acquiescence to a board member's flawed thesis, the refusal to revisit a strategy that stopped working six months ago. Mastery over these ordinary moments is the compound interest of good judgment. + +--- + +## The Framework + +The framework identifies four biological defaults -- behavioural programmes written into human DNA by natural selection, executed automatically when triggered, unless the individual creates space to think. These defaults overlap and reinforce each other, but each has a distinct signature. + +### Default 1: The Emotion Default + +The tendency to respond to feelings rather than facts. Anger, fear, excitement, and anxiety all compress the gap between stimulus and response to near zero. The emotion default does not announce itself; it simply acts. + +**Entrepreneurial signature:** A founder receives a hostile email from a key customer threatening to churn. Before finishing the email, the founder is already drafting a defensive reply. The reply escalates the situation, damages the relationship, and consumes three days of recovery effort. The founder never consciously decided to respond that way -- the emotion default decided for them. + +**Recognition pattern:** Physical symptoms precede the behaviour. Elevated heart rate, narrowed attention, a feeling of urgency disproportionate to the actual stakes. The framework notes that biological vulnerabilities -- hunger, fatigue, sleep deprivation, stress -- amplify the emotion default's grip. A founder operating on four hours of sleep during a fundraise is not making decisions; their cortisol is. + +### Default 2: The Ego Default + +The tendency to react to anything that threatens self-image or perceived position in a hierarchy. The ego default is not vanity in the colloquial sense -- it is the deep biological drive to protect one's standing, which manifests as the need to feel right rather than to be right. + +**Entrepreneurial signature:** A founder's CTO proposes an architecture that the founder privately knows is superior to their own. Instead of adopting it, the founder finds reasons to delay, modify, or undermine the proposal -- not from malice, but from the unconscious calculation that accepting the CTO's idea diminishes their own perceived value. The framework calls this being on "the wrong side of right": optimising for ego rather than outcome. + +**Recognition pattern:** Disproportionate energy spent defending a position. Difficulty saying "I don't know." A pattern of transforming unearned knowledge -- a blog post, a podcast episode -- into confident pronouncements. The ego default converts shallow familiarity into reckless conviction, which is particularly hazardous when a founder enters an unfamiliar market or technology domain. + +### Default 3: The Social Default + +The tendency to conform to the norms of the surrounding group. The social default does not require explicit peer pressure; it operates through the ambient fear of being snubbed, ridiculed, or treated as an outsider. + +**Entrepreneurial signature:** A founder at a Y Combinator dinner hears three peers describe their go-to-market strategy as product-led growth. Despite having customer evidence that a sales-led approach works better for their market, the founder begins pivoting toward PLG the following week. No analysis preceded the decision. The social default -- the comfort of aligning with the tribe -- supplied the conviction that data did not. + +**Recognition pattern:** Warren Buffett's observation applies with surgical precision: "The fact that other people agree or disagree with you makes you neither right nor wrong." If a strategic choice can only be justified by pointing to what others are doing, the social default is driving. The framework notes that "best practices" are, by definition, average practices -- and following them guarantees average results. + +### Default 4: The Inertia Default + +The tendency to maintain the status quo and resist change, even when change is clearly warranted. Inertia is cognitive as much as behavioural: once a mind is set in a direction, it tends to continue in that direction unless acted upon by an outside force. + +**Entrepreneurial signature:** A SaaS founder has recognised for six months that their pricing model is leaving revenue on the table. Customers have signalled willingness to pay more. Unit economics confirm it. Yet the founder keeps deferring the change because the current model is "working well enough." This is what the framework calls the "zone of average" -- a state too good to trigger alarm, too mediocre to produce excellence, and therefore perfectly designed to persist indefinitely. + +**Recognition pattern:** The phrase "that's how we've always done it" is the inertia default's national anthem. Public commitments create additional inertia -- having told the board a particular strategy would work, the founder finds it psychologically impossible to reverse course, even when new data demands it. The longer a hard conversation is avoided, the harder it becomes to have, until a small correctable problem has metastasised into a structural crisis. + +### How Defaults Compound + +The defaults rarely operate in isolation. A founder who is emotionally attached to an idea (emotion default) will defend it as their own (ego default), surround themselves with people who agree (social default), and resist changing course when it fails (inertia default). The compounding effect transforms a single unexamined moment into a cascading series of poor decisions, each reinforcing the last. + +--- + +## Prompts + +**Prompt 1 -- Default Diagnosis:** +> I just made (or am about to make) this decision: [describe decision]. Analyse it through the four-default lens. For each default (emotion, ego, social, inertia), assess whether it is likely influencing my thinking. Identify the specific trigger, the default behaviour it would produce, and what the clear-thinking alternative would look like. Be direct -- I need honesty, not comfort. + +**Prompt 2 -- Ordinary Moment Audit:** +> Review my last week of decisions and reactions: [describe 5-7 recent decisions, including small ones]. Identify which ones were "ordinary moments" where a default likely took control without my awareness. For each, name the default, describe what clear thinking would have produced instead, and estimate the cumulative cost of these unforced errors. + +**Prompt 3 -- Default Vulnerability Map:** +> Based on my current situation -- [describe stage, stressors, team dynamics, recent events] -- build a vulnerability map showing which defaults I am most susceptible to right now and why. Include biological amplifiers (sleep, stress, fatigue levels). Then recommend three specific environmental changes or rules that would reduce my exposure to the most dangerous default. + +**Prompt 4 -- Compounding Default Analysis:** +> Analyse this ongoing situation: [describe a persistent problem or stuck decision]. Map how multiple defaults may be compounding to keep me locked in a suboptimal position. Trace the chain: which default started the pattern, which ones reinforced it, and what would breaking one link in the chain look like in practice? + +--- + +## Use Cases + +**Validation-Stage Healthtech Founder Reacting to Investor Rejection** + +A digital health founder receives three consecutive investor rejections in a single week, each citing concerns about regulatory risk. The emotion default triggers a defensive posture -- the founder begins rewriting the pitch deck to minimise regulatory discussion rather than address it substantively. The ego default compounds the problem: the founder dismisses the investors as "not understanding the space" rather than considering whether the feedback contains a genuine signal. Applying the framework, an advisor helps the founder separate the emotional reaction from the informational content. The founder creates a 24-hour rule -- no pitch deck changes within 24 hours of a rejection -- which allows the emotion default to subside before strategic decisions are made. The revised deck confronts regulatory risk head-on, and the next investor meeting produces a term sheet. + +**Growth-Stage Marketplace Founder Trapped by Inertia and Social Default** + +A two-sided marketplace at $3M ARR has been running the same customer acquisition playbook for eighteen months. Growth has plateaued, but the playbook was designed by a well-known growth advisor whose framework the founder presented at two industry conferences. The social default (having publicly endorsed the approach) and the inertia default (the approach is familiar and comfortable) combine to prevent the founder from testing alternatives. A board member introduces the "zone of average" concept: the current results are adequate enough to prevent crisis but insufficient to attract Series A investment. The founder acknowledges the defaults at play, depersonalises the decision from the advisor's reputation, and allocates 30% of the acquisition budget to experimental channels. One experiment outperforms the legacy playbook within six weeks. + +**Scale-Stage Fintech CEO Whose Ego Default Is Blocking Delegation** + +A fintech CEO at $20M ARR continues to approve every product feature personally, creating a bottleneck that has slowed release cycles by 40%. The CEO frames this as "maintaining quality standards," but the ego default analysis reveals a different mechanism: having others depend on every decision makes the CEO feel indispensable. The ego default has converted a genuine strength (product taste) into a structural weakness (organisational paralysis). The CEO implements a safeguard -- a decision classification matrix that reserves only irreversible, high-stakes product decisions for CEO approval -- and watches release velocity recover within a quarter. + +**Idea-Stage Consumer App Founder Whose Social Default Killed Differentiation** + +A consumer social app founder attended a prominent tech conference and heard four successful founders describe their growth strategy as "community-first, product-second." The founder had been building a product-first approach with strong early retention data. Within two weeks of the conference, the founder restructured the roadmap around community features, deprioritising the product mechanics that were generating actual traction. No quantitative analysis preceded the shift; the social default -- the gravitational pull of aligning with high-status peers -- supplied the justification. Three months later, retention collapsed. A board advisor helped the founder trace the decision back to the conference, identify the social default as the driver, and restore the original product-first approach. The recovery took a full quarter -- time the founder would not have lost had the default been recognised in the moment it operated. + +--- + +## Anti-Patterns + +**1. Treating default awareness as default immunity.** Knowing the four defaults exist does not neutralise them. The research is explicit: even decades of studying these patterns do not make a person immune. This parallels Kahneman's own admission about cognitive biases. The corrective is structural -- building environmental safeguards and decision rules -- not intellectual self-congratulation. + +**2. Weaponising default labels against colleagues.** Telling a co-founder "that's just your ego talking" is not analysis; it is a power move dressed in psychological vocabulary. Default diagnosis should be applied to decision processes and to oneself first. The moment it becomes interpersonal ammunition, it destroys the trust required for honest deliberation. + +**3. Assuming all intuition is a default in disguise.** The framework does not argue that emotion, social awareness, or pattern-based inertia are always wrong. These defaults evolved because they provided survival advantages. The problem is not their existence but their unexamined operation. A founder with fifteen years of domain expertise whose gut says "this market is wrong" may be exercising genuine pattern recognition, not the emotion default. The distinguishing question: can the reasoning behind the intuition be reconstructed and examined? + +**4. Using the framework to justify indecision.** Some founders, upon learning about defaults, begin second-guessing every impulse until no decision is possible. The framework is designed to create space for reason, not to replace action with perpetual self-analysis. The goal is a pause measured in minutes, not months. + +**5. Ignoring the compounding effect.** Addressing only one default while leaving others unexamined produces a false sense of progress. A founder who manages their emotional reactions but continues to conform to social consensus has solved only a quarter of the problem. The defaults must be diagnosed as a system, not in isolation. + +--- + +## By Stage + +| Stage | Primary Default Risk | Key Difference | +|-------|---------------------|----------------| +| Idea | Ego + Social | The ego default inflates confidence in an untested concept; the social default either validates it through echo-chamber feedback or kills it through premature conformity to "realistic" expectations. | +| Validation | Emotion + Ego | Negative signals from early customers trigger the emotion default (defensiveness) and the ego default (dismissing feedback). The founder's identity is maximally entangled with the product at this stage. | +| Early Traction | Social + Inertia | Initial success creates inertia around the first playbook that worked. Social defaults intensify as the founder enters a peer group (accelerator, investor network) whose norms exert conformity pressure. | +| Growth | Inertia + Ego | Scaling requires changing what worked at smaller scale, but inertia resists structural change and the ego default makes it difficult for the founding team to admit that their original approach has reached its limits. | +| Scale | All four compounding | At scale, defaults become organisational, not personal. A CEO's unexamined ego default becomes a company-wide culture of deference. Social defaults calcify into "the way things are done here." Inertia becomes institutional resistance to strategic evolution. | + +At the idea stage, the most valuable intervention is protecting the founder from the social default's premature influence. The observation that "if you do what everyone else does, you'll get the same results everyone else gets" is maximally relevant when the entire value of a new venture lies in doing something different. The founder who listens too early to how "the market usually works" has surrendered the only advantage an idea-stage venture possesses: the licence to be unconventional. + +At the validation stage, the emotion and ego defaults create a particularly dangerous compound. The founder has invested months -- possibly years -- of identity into the concept. Customer feedback that contradicts the thesis does not arrive as neutral data; it arrives as a personal attack. The emotion default produces defensiveness; the ego default provides the rationalisation. Together they can sustain a dead hypothesis well past the point where honest assessment would have triggered a pivot. + +At growth, inertia becomes the primary adversary. The playbooks that generated early traction begin to ossify into doctrine. Challenging them feels like questioning the founding story itself. The "zone of average" concept is maximally relevant here: results are adequate enough to prevent crisis but insufficient to justify the company's valuation trajectory. The inertia default thrives in this zone because nothing is broken badly enough to force change. + +At scale, the challenge shifts from individual default management to organisational default architecture. The CEO's task is no longer managing their own autopilot but designing systems, incentives, and cultures that prevent the organisation from running on collective autopilot. A single executive's unexamined social default -- the tendency to hire people who think like them, reward consensus, and punish dissent -- can, over time, produce an entire company that has lost the capacity for independent thought. + +--- + +## Output Template + +```markdown +# Default Diagnosis -- [Decision or Situation] + +**Date:** [Date] +**Decision-maker:** [Name / Role] +**Context:** [Brief situation description] + +## Default Scan + +| Default | Active? | Trigger | Evidence | Severity | +|---------|---------|---------|----------|----------| +| Emotion | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Ego | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Social | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Inertia | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | + +## Biological Amplifiers +- Sleep: [Hours last 3 nights] +- Stress level: [H/M/L] +- Recent emotional event: [Y/N -- describe] +- Environment: [Familiar / Unfamiliar] + +## Compounding Analysis +[Describe how multiple defaults may be reinforcing each other] + +## Clear-Thinking Alternative +[What the decision or response would look like if no default were operating] + +## Safeguard Recommendation +1. [Specific environmental change or rule] +2. [Specific environmental change or rule] +3. [Specific environmental change or rule] + +## Ordinary Moment Assessment +- **Is this moment ordinary or dramatic?** [Most consequential moments feel ordinary] +- **Will this response make the future easier or harder?** [The framework's core test] +``` + +--- + +## Related Skills + +- **[Building Thinking Strength](building-thinking-strength.md)** -- Diagnosing defaults is the first step; building the four internal strengths is how you override them consistently. +- **[Managing Weakness and Mistakes](managing-weakness-and-mistakes.md)** -- When defaults win despite awareness, safeguards and mistake-handling protocols limit the damage and extract learning. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's System 1/System 2 model provides the cognitive science foundation; the four defaults operationalise it into specific behavioural patterns entrepreneurs can recognise. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Offers the daily decision habits that complement the deeper diagnostic system, particularly the importance-frequency matrix. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- The Stoic dichotomy of control achieves clarity by distinguishing what can and cannot be influenced; the Clear Thinking framework achieves it by identifying which biological programme is doing the influencing. +- **[Stoic Emotional Mastery](../stoic/stoic-emotional-mastery.md)** -- Provides the philosophical discipline for managing the emotion default specifically, complementing the behavioural and environmental approach. +- **[Stoic Unbiased Thought](../stoic/stoic-unbiased-thought.md)** -- The Stoic impression-testing protocol is the ancient ancestor of the modern default-interruption techniques; both aim to create a gap between stimulus and response. diff --git a/plugins/foreman/content/skills/thinking/evaluating-and-deciding.md b/plugins/foreman/content/skills/thinking/evaluating-and-deciding.md new file mode 100644 index 0000000..075e14f --- /dev/null +++ b/plugins/foreman/content/skills/thinking/evaluating-and-deciding.md @@ -0,0 +1,244 @@ +--- +name: "evaluating-and-deciding" +description: "Covers the full arc from option evaluation through execution and post-decision learning: criteria weighting and the 'most important thing' discipline, high-fidelity and high-expertise information gathering, margin of safety as a buffer against being wrong, the irreversibility test for calibrating decision speed, bullets-before-cannonballs experimentation, execution fail-safes (trip wires, commander's intent, Ulysses pacts), and the process-over-outcome principle for decision journals. Use when evaluating multiple options against competing criteria, when the cost of being wrong is high and margin of safety is needed, when deciding how fast to move, when building execution safeguards, or when conducting post-mortems that separate luck from skill." +version: "1.0.0" +category: "thinking" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - margin-of-safety + - decision-evaluation + - irreversibility + - second-order-thinking + - inversion + - decision-journal + - execution + - fail-safes + - criteria-weighting + - bullets-before-cannonballs +related_skills: + - defining-and-exploring-problems + - thinking-fast-and-slow + - decision-making-under-pressure + - wanting-what-matters + - scenario-planning + - stoic-fortitude-and-resilience +author: "Fatih Guner" +--- + +# Evaluating and Deciding + +MARGIN OF SAFETY. Good decision-makers do not predict more accurately than everyone else -- they build better buffers for being wrong. Warren Buffett sat out the dot-com mania while friends doubled and quadrupled their portfolios, endured years of being called obsolete, and emerged with cash reserves intact when the bubble burst. The hedge fund Long-Term Capital Management, run by two Nobel laureates and some of the highest IQs in finance, delivered 40 percent annual returns until it lost $4.6 billion in under four months and nearly collapsed the global financial system. The difference was not intelligence. It was the presence or absence of a margin of safety -- the deliberate gap between what you expect to happen and what could happen, designed to save you when surprises are expensive. The framework for the full decision arc -- evaluate, safeguard, execute, learn -- rests on this single uncomfortable truth: certainty is a feeling, not a fact, and the moment you are most confident you do not need a buffer is precisely the moment you need one most. + +--- + +## The Framework + +The framework spans four stages. Each builds on the preceding one, and skipping any stage degrades the quality of the entire arc. + +### Stage 1: Evaluate the Options + +Evaluation begins not with data but with criteria. Three features distinguish useful criteria from decorative ones: + +- **Clarity.** The criterion can be explained to a twelve-year-old. If it requires jargon, it will be interpreted differently by each person applying it. +- **Goal promotion.** The criterion must favour options that advance the actual objective. NASA's Challenger disaster is the canonical counter-example: launch-date criteria promoted the goal of schedule adherence, not the goal of safety. The result was catastrophic. +- **Decisiveness.** The criteria must narrow the field to one option. Criteria that produce ties are criteria that avoid commitment. + +**Finding the Most Important Thing.** The text recounts a lesson from a mentor that teams cannot make decisions independently unless the leader communicates a single overriding priority. Not three priorities. Not a weighted matrix of ten factors. One. The exercise for identifying it is deliberately combative: write each criterion on a separate card, then force them to battle in pairs. "If I could have only one of these, which would it be?" As criteria compete, quantities emerge -- thresholds at which the ranking reverses. The result is an ordered stack with the most important thing at the top and the precise conditions under which the order would change. + +**Getting the Right Information.** Two principles govern information quality: + +| Principle | Definition | Entrepreneurial Application | +|-----------|------------|----------------------------| +| **HiFi (High-Fidelity)** | Information close to the source, unfiltered by others' biases and incentives. | Talk to customers directly, not to the VP who summarised the survey. General Marshall sent trusted observers to the front lines and discovered that pilots were refusing to fly not because of aircraft defects but because ground crews, ravaged by malaria from lack of mosquito netting, could not be trusted to maintain the planes. Headquarters, in its mosquito-protected offices, had no idea. | +| **HiEx (High-Expertise)** | Information from people with deep, recent experience solving the specific problem at hand. | Seek experts who solved your problem recently, not two decades ago. Pay for their time -- it forces you to prepare precise questions. Ask "how do you think about this?" rather than "what should I do?" The former transfers reasoning; the latter transfers only an answer. | + +**Distinguishing Experts from Imitators.** Imitators cannot answer questions at a deeper level, cannot adapt their vocabulary to a non-specialist audience, become frustrated when you say you do not understand, avoid discussing their failures, and cannot identify the boundaries of their own competence. Real experts display the opposite on every count. + +### Stage 2: Margin of Safety + +A margin of safety is insurance for decisions. In years when nothing goes wrong, it looks like waste. In the year something does, it is the difference between survival and ruin. + +The baseline heuristic: a margin of safety sufficient to absorb double the worst-case scenario. If job loss would take six months to recover from, hold twelve months of expenses. If a product launch might miss revenue targets by 30 percent, build a budget that survives a 60 percent miss. + +Adjustments to the baseline: + +- **High cost of failure, volatile environment:** Increase the margin. The consequences of underprotection are asymmetric -- you can always reduce a margin later, but you cannot retroactively create one. +- **Low cost of failure, established pattern:** Reduce the margin. Not every decision requires a buffer. The discipline is knowing which ones do. +- **Deep expertise and proprietary data:** Reduce the margin further, as Buffett does when buying businesses he understands well enough to pay near full value. + +**Bullets Before Cannonballs.** When still gathering information, do not over-invest in a single option. Jim Collins and Morten Hansen's metaphor is precise: fire small, cheap bullets to calibrate aim, then fire the cannonball along the validated line of sight. A founder evaluating two CEO candidates should have both complete a small paid project with the team before committing to either. A founder considering medical school should shadow a resident for a day, not enrol in a programme. Preserving optionality has a cost -- it can look like indecision. But looking short-term stupid while keeping options open is a consistent feature of the most successful long-term decision-makers. + +**Inversion: What Would Guarantee Failure?** Rather than asking "what should we do to succeed?" ask "what would guarantee failure?" and then avoid those things. If guaranteed failure for a product launch means shipping without beta testing, launching without a support team, and ignoring the first two weeks of customer feedback -- then the margin of safety must explicitly prevent each of those conditions. + +### Stage 3: Execute the Decision + +**The Irreversibility Test.** Decisions sit on a spectrum from trivially reversible to permanently irreversible. Two principles calibrate speed to position on this spectrum: + +- **ASAP Principle:** If the cost to undo the decision is low, make it as soon as possible. Deliberating over a reversible choice is itself a costly error. Jeff Bezos calls these "two-way doors" -- walk through, and if it is wrong, walk back. +- **ALAP Principle:** If the cost to undo the decision is high, make it as late as possible while continuing to gather information and preserve optionality. These are "one-way doors." Keeping a pocket of space open -- the way a driver maintains following distance at high speed -- is how you preserve the ability to manoeuvre when circumstances shift. + +**The Stop, FLOP, Know Principle.** Even for one-way doors, there comes a moment to act. That moment arrives when: (1) you Stop gathering useful information -- confidence is rising but accuracy is not; (2) you experience a First Lost OPportunity, meaning options begin to expire; or (3) you come to Know something -- a piece of evidence or a gut conviction tested against reason -- that makes the right choice evident. + +**Live with the Decision Before Announcing It.** Make the decision, then sleep on it. Before bed, write a note to yourself explaining why you decided as you did. Read the note in the morning. More often than expected, the reasoning that seemed airtight at 6 PM looks different at 7 AM. Announcing prematurely starts things moving and makes reversal socially expensive. + +**Three Execution Fail-Safes:** + +1. **Trip Wires.** Precommit to specific actions triggered by quantifiable conditions. A summit team agrees to turn back if they have not reached Camp 4 by noon. A startup agrees that if month-three retention is below 20 percent, the product thesis is invalidated. No argument at the moment of truth -- the decision was already made. + +2. **Commander's Intent.** Communicate the strategy, the rationale, and the operational boundaries so that team members can adapt when circumstances change without waiting for approval. The four components are formulate, communicate, interpret, and implement. If you cannot be away from the office for a week without things falling apart, the failure is not that you are indispensable -- it is that you are an incompetent communicator of intent. + +3. **Ulysses Pacts (Tying Your Hands).** Remove the option to deviate from the plan during moments of weakness. Automated investment deposits. Removing junk food from the house. Locking in a product launch date with external commitments that make delay socially or financially costly. + +### Stage 4: Learn from Decisions + +**The Process Principle.** Evaluate the process you used, not the outcome you got. A good decision can produce a bad outcome (bad luck), and a bad decision can produce a good outcome (good luck). Pete Carroll's decision to throw rather than run on the one-yard line in Super Bowl XLIX was rooted in sound analysis of the opponent's defensive weaknesses. The interception that resulted was, in his words, "the worst result of a call ever" -- not the worst call. + +The process-outcome matrix: + +| | Good Outcome | Bad Outcome | +|---|---|---| +| **Good Process** | Deserved success. Stay disciplined. | Bad luck. Trust the process. Learn and continue. | +| **Bad Process** | Undeserved success. You got lucky. Change before luck runs out. | Deserved failure. Let it be a wake-up call. | + +**The Transparency Principle.** Make your reasoning visible and open to scrutiny -- primarily to yourself. The ego default rewrites memory after the fact, conflating what you know now with what you knew then. A decision journal defeats this distortion. + +What to record at the time of the decision: + +- The problem as you understood it +- The options you considered and the criteria you applied +- What you expected to happen and why +- The information you had and the information you wished you had +- Your confidence level + +What to review afterward: + +- Did the outcome occur for the reasons you anticipated? +- Where did your reasoning hold, and where did it break down? +- Was the result attributable to skill or to luck? + +One firm described in the text discovered that its decision-makers were correct only 20 percent of the time -- and that even when anticipated outcomes materialised, they did so for different reasons than predicted. The firm's "success" was indistinguishable from roulette. Without the journal, they would never have known. + +--- + +## Prompts + +**Prompt 1 -- Criteria Weighting:** +> "I need to decide between [options] for my [stage] [sector] company. Help me identify the five most relevant evaluation criteria, then run the 'criteria battle' exercise: force each pair to compete ('if I could have only one, which would it be?'), surface the quantities at which rankings reverse, and produce a final ordered stack with the single most important thing at the top." + +**Prompt 2 -- Margin of Safety Calculation:** +> "I am planning [initiative/investment/launch] with an expected outcome of [target]. Apply the margin of safety framework: (1) identify what could go wrong, (2) estimate the worst plausible scenario, (3) calculate a buffer that absorbs double that worst case, and (4) recommend adjustments based on the cost of failure, environmental volatility, and my level of expertise. Include a bullets-before-cannonballs plan for low-risk validation before full commitment." + +**Prompt 3 -- Irreversibility and Timing Assessment:** +> "I am facing [decision]. Classify it on the consequentiality-reversibility spectrum. Is this a two-way door (ASAP) or a one-way door (ALAP)? Apply the Stop, FLOP, Know principle to determine whether I have enough information to act now, or whether I should continue gathering information and preserving optionality. Identify the specific signals that would trigger action." + +**Prompt 4 -- Post-Decision Review:** +> "Six months ago I decided [decision]. The outcome was [outcome]. Help me conduct a process review using the framework: (1) Reconstruct what I knew at the time and the reasoning I used. (2) Determine whether the outcome occurred for the reasons I expected. (3) Classify the result in the process-outcome matrix (good process/good outcome, good process/bad outcome, etc.). (4) Identify what I should change in my process for future decisions of this type." + +--- + +## Use Cases + +**Early-Traction Marketplace Evaluating Expansion Options** + +A two-sided marketplace for freelance graphic designers has achieved product-market fit in one vertical (e-commerce brands) and faces three expansion options: geographic expansion, vertical expansion (adding new buyer segments), and service expansion (adding motion design). The founder's instinct is to pursue all three. Applying the criteria battle, the team identifies that the single most important thing is deepening supply-side liquidity in the existing vertical -- without which none of the expansion options will succeed. The margin of safety analysis reveals that pursuing two expansion vectors simultaneously, if either underperforms by 40 percent, would burn through runway before Series A closes. The bullets-before-cannonballs prescription: run a four-week paid pilot in the most promising new vertical with five existing designers and ten new buyers. If conversion rates match the existing vertical within 70 percent, fire the cannonball. If not, recalibrate before committing resources. + +**Growth-Stage Fintech Deciding on Regulatory Strategy** + +A fintech company approaching $50M ARR must choose between applying for its own banking charter (expensive, slow, high control) and partnering with a sponsor bank (faster, lower cost, less control). Binary framing makes this look like a pure trade-off. The irreversibility test reveals that obtaining a charter is a one-way door (ALAP Principle applies -- delay and gather information), while a sponsor-bank partnership is a two-way door (ASAP Principle -- sign and renegotiate later if needed). Commander's intent for the compliance team: "Our most important thing is maintaining uninterrupted service to existing customers. Any regulatory strategy that risks a service gap is off the table, regardless of long-term efficiency gains." Trip wire: if the charter application has not advanced past preliminary review within nine months, pivot full resources to the sponsor-bank path. + +**Solo Founder Learning from a Failed Product Launch** + +A solo founder launched a productivity tool for remote teams, priced at $29/month, and acquired 200 users in the first month -- but 90 percent churned within 60 days. The natural instinct is resulting: "the product failed, so the decision to launch was bad." A process review using the decision journal reveals that the launch decision itself was sound (low cost to undo, clear stop-loss criteria, validated demand through a landing page test), but the pricing and onboarding criteria were set without HiFi information -- the founder relied on competitor pricing data aggregated by a third-party report rather than talking to ten target customers about willingness to pay. The process failure was informational, not decisional. The corrective action is not to abandon the product but to invest in direct customer conversations before the next pricing iteration. + +--- + +## Anti-Patterns + +**Treating all decisions as one-way doors.** Founders who deliberate for weeks over reversible choices -- a landing page design, a pricing test, a Slack channel name -- are misallocating their most constrained resource: time. The ASAP Principle exists precisely for these decisions. Walk through the two-way door. If it is wrong, walk back. + +**Building no margin of safety because "we know what we're doing."** Buffett's observation applies: "Diversification is protection against ignorance. It makes little sense if you know what you are doing." The corollary is that most of us rarely know what we are doing with the confidence required to go all in. The moment confidence peaks is precisely when the margin of safety is most needed, because overconfidence is the ego default's signature product. + +**Resulting -- evaluating decisions by outcomes alone.** A decision that produced a good outcome may have been reckless (bad process, good luck). A decision that produced a bad outcome may have been excellent (good process, bad luck). Without a decision journal that captures reasoning at the time of the decision, there is no way to distinguish skill from luck, and no mechanism for improvement. + +**Setting trip wires you are willing to override.** A trip wire that is negotiable at the moment of truth is not a trip wire. It is a suggestion. The entire point of precommitment is that it removes discretion from your future self -- the version of you that is fatigued, emotionally invested, and susceptible to summit fever. If the team agreed to turn back at noon and it is 12:01, the team turns back. + +**Confusing commander's intent with abdication.** Empowering others to make decisions requires communicating the strategy, the rationale, and the boundaries. Telling a team "just figure it out" without context is not delegation; it is abandonment. Commander's intent has four components; skipping the first two makes the last two impossible. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Criteria are sparse and personal -- the founder evaluates options against their own goals, risk tolerance, and opportunity costs. | The margin of safety is primarily financial (personal runway). Bullets before cannonballs means validating demand before building product. | +| Validation | Criteria become market-facing -- customer willingness to pay, retention rates, activation metrics. | HiFi information from direct customer contact outweighs any survey or third-party report. The ASAP Principle applies to most validation experiments. | +| Early Traction | The team grows, and the "most important thing" must be communicated to others. Criteria battles happen across functions, not just in the founder's head. | Commander's intent becomes operational. Trip wires attach to leading metrics (activation, retention) not just lagging ones (revenue). | +| Growth | Multiple consequential decisions compete for attention simultaneously. Margins of safety interact -- a thin buffer in one area can cascade into failure in another. | The ALAP Principle governs major strategic bets (new markets, acquisitions, platform changes). Decision journals become institutional, not personal. | +| Scale | The decision-maker is increasingly distant from the source of information. Abstractions multiply. | The HiFi Principle is hardest to maintain at scale and therefore most valuable. Leaders must actively seek unfiltered information from the front lines. The Transparency Principle becomes an organisational practice, not an individual one. | + +--- + +## Output Template + +```markdown +# Decision Evaluation Record + +**Date:** [date] +**Decision:** [one-sentence description] +**Decision-maker:** [name] +**Irreversibility classification:** [Two-way door / One-way door] +**Timing principle applied:** [ASAP / ALAP] + +## Criteria (Ordered by Battle Results) +1. [Most important thing] -- threshold: [quantified] +2. [Second criterion] -- threshold: [quantified] +3. [Third criterion] -- threshold: [quantified] + +## Options Evaluated + +| Option | Criterion 1 | Criterion 2 | Criterion 3 | Margin of Safety | +|--------|-------------|-------------|-------------|------------------| +| A | [score/assessment] | [score] | [score] | [buffer description] | +| B | [score/assessment] | [score] | [score] | [buffer description] | +| C | [score/assessment] | [score] | [score] | [buffer description] | + +## Information Quality +- **HiFi sources consulted:** [list] +- **HiEx sources consulted:** [list] +- **Key information gaps:** [what we still do not know] + +## Decision +**Chosen option:** [X] +**Reasoning:** [why this option best satisfies the ordered criteria] +**What I expect to happen:** [specific predictions] +**Confidence level:** [low / moderate / high] + +## Execution Fail-Safes +- **Trip wire(s):** [condition] triggers [action] +- **Commander's intent:** [the most important thing + boundaries] +- **Ulysses pact:** [hands tied how] + +## Post-Decision Review (Complete After Outcome) +- **Outcome:** [what happened] +- **Did it happen for the reasons I predicted?** [yes/no + explanation] +- **Process-outcome classification:** [good process + good outcome / good process + bad outcome / etc.] +- **What I would change in my process:** [specific improvements] +``` + +--- + +## Related Skills + +- **[Defining and Exploring Problems](defining-and-exploring-problems.md)** -- The prerequisite: correct problem definition and solution-space exploration must occur before evaluation begins. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- The cognitive bias catalogue that explains why evaluation goes wrong: anchoring on early information, overconfidence, and the planning fallacy. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- Focuses on the speed dimension: when to stop deliberating and act. +- **[Wanting What Matters](wanting-what-matters.md)** -- The meta-question that sits above all evaluation criteria: are you optimising for the right things in the first place? +- **[Stoic Fortitude and Resilience](../stoic/stoic-fortitude-and-resilience.md)** -- Provides the psychological infrastructure for maintaining discipline when trip wires trigger and margins of safety are tested. +- **[Scenario Planning](../frameworks/scenario-planning.md)** -- Extends the margin of safety concept into a formal methodology for preparing for multiple possible futures. +- **[Evaluating Options](../decisions/evaluating-options.md)** -- Provides the complementary evaluation toolkit including joint evaluation, Even Swaps, and risk ranking methods for choosing among generated alternatives. diff --git a/plugins/foreman/content/skills/thinking/managing-weakness-and-mistakes.md b/plugins/foreman/content/skills/thinking/managing-weakness-and-mistakes.md new file mode 100644 index 0000000..39c96fb --- /dev/null +++ b/plugins/foreman/content/skills/thinking/managing-weakness-and-mistakes.md @@ -0,0 +1,235 @@ +--- +name: "managing-weakness-and-mistakes" +description: "Provides a systematic approach to protecting against predictable decision failures and extracting maximum learning from errors, using the Clear Thinking safeguard architecture and mistake-handling protocol. Covers knowing your weaknesses (biological and acquired), building safeguards (prevention, automatic rules, friction, guardrails, perspective shifts), and the four-step process for handling mistakes without ego contamination. Use when repeating the same errors across decisions, needing to design pre-commitment rules for high-pressure situations, building organisational error-recovery processes, or recognising that a cover-up is compounding an initial mistake." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - clear-thinking + - safeguards + - decision-rules + - mistake-handling + - weakness-management + - blind-spots + - checklists + - pre-commitment + - error-recovery + - clear-thinking-framework +related_skills: + - enemies-of-clear-thinking + - building-thinking-strength + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-pragmatism +author: "Fatih Guner" +--- + +# Managing Weakness and Mistakes + +SAFEGUARD. The best decision-makers are not more intelligent -- they are better at protecting themselves against themselves. The Clear Thinking framework's third principle completes a system that begins with diagnosis (identifying the four defaults) and progresses through construction (building the four strength pillars). This final layer addresses the uncomfortable truth that strength alone is insufficient. Every person has weaknesses that no amount of self-control or self-knowledge can eliminate entirely -- biological constraints, cognitive blind spots, acquired habits with roots deeper than willpower can reach. The solution is not to pretend these weaknesses do not exist but to engineer an environment in which they cannot cause catastrophic damage. And when mistakes inevitably occur despite every safeguard, the protocol for handling them determines whether they become learning or compounding liability. + +The framework draws a distinction that most leadership literature ignores: the difference between weaknesses that can be overcome through strength and weaknesses that require structural protection. A founder who becomes impulsive when sleep-deprived cannot "strength" their way through a red-eye flight into a board meeting. The biology is non-negotiable. What they can do is build a safeguard: a rule that no irreversible decisions are made within twelve hours of overnight travel. The safeguard does not fix the weakness. It makes the weakness irrelevant. + +--- + +## The Framework + +### Part 1: Knowing Your Weaknesses + +The framework categorises weaknesses into two types, each requiring a different management approach. + +**Inbuilt weaknesses** are biological constraints no human can eliminate: hunger, fatigue, sleep deprivation, emotional volatility, stress responses, cognitive biases, and the inherent limitations of individual perspective. These are features of the hardware, not bugs in the software. They cannot be overcome through character development. They can only be managed through safeguards. + +**Acquired weaknesses** are patterns of behaviour absorbed through habit and reinforced by inertia: acting on impulse, doing less than one is capable of, refusing to start due to fear, seeing only one's own point of view, coasting on talent without effort. These can be addressed through the strength pillars (self-accountability, self-knowledge, self-control, self-confidence) but often benefit from safeguards as well, because willpower is a depletable resource. + +The formula for failure, the text observes, is a few small errors consistently repeated. The insidiousness lies in the delay between action and consequence. Skipping one strategic review causes no immediate harm. Skipping twelve creates a strategic drift that may take years to reverse. The compound interest of bad habits works silently until the bill arrives all at once. + +**Blind spots deserve special attention.** Three forces conspire to prevent founders from seeing their own weaknesses: + +1. **Habituation.** Flawed patterns feel normal because they have become ingrained through repetition. The founder who micromanages does not experience micromanagement as a weakness; they experience it as diligence. +2. **Ego protection.** Acknowledging a deep behavioural flaw feels like a referendum on character, not a correctable process error. The ego default actively shields weaknesses from conscious inspection. +3. **Limited perspective.** No one can fully see a system they are part of. The founder's future self will look back at the current self with the same bewildered clarity that the current self reserves for the teenage self. + +Richard Feynman's principle applies: "The first principle is that you must not fool yourself -- and you are the easiest person to fool." The corollary for entrepreneurs: the people around you can likely catalogue your weaknesses with disturbing accuracy. The question is whether you have created conditions safe enough for them to share that knowledge. + +### Part 2: Building Safeguards + +Safeguards are tools for protecting yourself from yourself. The framework identifies five strategies, each suited to different weakness profiles. + +**Strategy 1: Prevention.** Avoid making decisions under conditions known to degrade judgment. The HALT framework (Hungry, Angry, Lonely, Tired) from Alcoholics Anonymous applies directly to entrepreneurial decision-making. Before any significant decision, ask: Am I hungry? Am I emotionally activated? Am I isolated or in an unfamiliar environment? Am I fatigued or sleep-deprived? If yes to any, defer the decision. The cost of delay is almost always less than the cost of a default-driven error. + +For founders, this translates into calendar discipline. No term-sheet negotiations after investor dinners that run past midnight. No personnel decisions on the day a major customer churns. No strategic pivots during the adrenaline spike of a competitor's product launch. Prevention is not avoidance; it is timing. + +**Strategy 2: Automatic Rules.** Replace repeated decisions with predetermined rules that require no deliberation and invite no social pushback. The key insight, drawn from a conversation with Daniel Kahneman: "People question decisions, but they respect rules." + +Kahneman's own favourite rule -- never say yes to a request on the phone -- illustrates the principle. The rule eliminates the social default's real-time pressure, creates space for genuine evaluation, and allows many low-value requests to dissolve naturally when the requestor does not follow up. + +Entrepreneurial examples: +- "No hiring decisions without 48 hours between final interview and offer." +- "No strategic commitments during fundraising -- the emotional volatility of the process contaminates judgment." +- "No meetings before lunch -- the morning belongs to the highest-leverage work." + +The power of automatic rules is that they remove the decision from the moment of vulnerability. The rule is made once, under conditions of clear thinking, and then enforced mechanically regardless of the emotional state at the time of execution. + +**Strategy 3: Friction.** Increase the effort required to do things that are contrary to long-term goals. The formulation is precise: "Behaviour follows the path of least resistance." If checking email is easier than writing the strategic plan, email will win. The solution is not more willpower but more friction on the undesirable path. + +Entrepreneurial applications: +- Removing Slack notifications during deep-work blocks (friction on distraction). +- Requiring a written one-page analysis before any meeting can be scheduled to discuss a new initiative (friction on reactive meetings). +- Making it easier to consult the decision framework than to skip it (reducing friction on the desired behaviour while increasing it on the default). + +**Strategy 4: Guardrails -- Checklists and Operating Procedures.** Formulate decision procedures that force a pause and redirect attention to fundamentals. Pilots use preflight checklists not because they are forgetful but because even experts, under routine conditions, skip steps. The same logic applies to founders making recurring high-stakes decisions. + +A pre-investment checklist: "Have I verified the thesis with someone who disagrees? Have I identified the three most likely failure modes? Have I stress-tested the financial model with pessimistic assumptions? Am I making this decision under favourable cognitive conditions?" Each question is a guardrail preventing the defaults from steering unchecked. + +**Strategy 5: Perspective Shifts.** Deliberately adopt frames of reference beyond your own to reveal blind spots that are structurally invisible from your current vantage point. + +The text cites the transformation of the USS Benfold, one of the worst-performing warships in the US Navy. Commander Michael Abrashoff changed nothing about the crew, technology, or hierarchy. He changed his own perspective -- looking at the ship from the ordinary sailors' vantage point rather than the officers'. The insight was as simple as waiting in the food line instead of cutting to the front. Within twenty months, the Benfold became one of the fleet's top performers. + +The entrepreneurial parallel: a founder who asks "What does this decision look like from the perspective of a new hire? A departing customer? A competitor?" is performing a perspective-shift safeguard. The technique described -- stating your understanding of the other person's view and then asking "What did I miss?" followed by "What else did I miss?" -- converts a blind spot into a data-gathering protocol. + +### Part 3: Handling Mistakes + +When safeguards fail and mistakes occur, the response determines whether the mistake becomes a one-time cost or a compounding liability. The observation is characteristically blunt: "The biggest mistake people make typically isn't their initial mistake. It's the mistake of trying to cover up and avoid responsibility for it. The first mistake is expensive; the second one costs a fortune." + +Three problems with covering up mistakes: + +1. **Learning is blocked.** If the mistake is hidden, its causes remain unexamined, and the same error will recur. +2. **Hiding becomes habitual.** Each successful cover-up lowers the threshold for the next one, until deception becomes the default response to failure. +3. **The cover-up compounds the damage.** The cover-up introduces new risks (discovery, loss of trust, legal exposure) that dwarf the original error. + +**The Four-Step Protocol:** + +**Step 1: Accept responsibility.** Acknowledge your contribution to the mistake without deflecting to external factors. This requires the self-accountability and self-control pillars to be functional -- the emotion default will fight aggressively to shift blame, and the ego default will construct elaborate narratives of victimhood. If the internal dialogue includes phrases like "this isn't fair" or "they should have," the acceptance is incomplete. + +**Step 2: Learn from the mistake.** Examine the thoughts, feelings, and actions that produced the error. If this examination produces defensiveness or blame, return to Step 1. The learning is incomplete until the founder can describe their own contribution to the failure without qualification. The framework notes that the ego distorts memory to make us look better than we actually were -- which is why decisions and their reasoning should be recorded in writing at the time they are made, not reconstructed after the fact. + +**Step 3: Commit to doing better.** Formulate a specific plan -- either a new strength practice or a new safeguard -- that addresses the root cause. Vague commitments ("I'll be more careful next time") are the ego default wearing the costume of accountability. Concrete commitments ("I will implement a 48-hour cooling period before responding to any communication that triggers a defensive emotional reaction") are operational changes. + +**Step 4: Repair the damage.** Where possible, repair the consequences. The longer the prior relationship and the more consistent the prior behaviour, the more repairable the damage. Repair requires sustained consistency, not a single gesture. Any immediate deviation reverses the repair and confirms the original failure as a pattern rather than an exception. + +--- + +## Prompts + +**Prompt 1 -- Weakness Inventory:** +> Help me build an honest weakness inventory for myself as a founder. Here is my current context: [stage, role, team size, key challenges]. Categorise my likely weaknesses into inbuilt (biological/cognitive) and acquired (habitual/behavioural). For each, assess whether it requires strength-building, a safeguard, or both. Then prioritise: which weakness, if left unaddressed, poses the greatest compounding risk over the next 12 months? + +**Prompt 2 -- Safeguard Architecture:** +> Design a safeguard system for these recurring decision failures: [describe 3-4 patterns of poor decisions or repeated errors]. For each pattern, recommend the most appropriate safeguard strategy (prevention, automatic rule, friction, guardrail, or perspective shift). Be specific -- give me the exact rule, checklist, or environmental change to implement, not a general principle. + +**Prompt 3 -- Mistake Post-Mortem:** +> I made this mistake: [describe the mistake, the decision that led to it, and the outcome]. Walk me through the four-step protocol. At each step, challenge me if my language contains deflection, blame, or vague commitments. Help me identify the root cause, design a specific safeguard or strength practice to prevent recurrence, and assess what damage repair is needed and feasible. + +**Prompt 4 -- Blind Spot Probe:** +> Based on what you know about founders at my stage ([stage]) with my profile ([describe background, team dynamics, market]), what are the three most statistically likely blind spots I am carrying? For each, describe why I probably cannot see it from my current vantage point, what perspective shift would reveal it, and what question I should ask my team or advisors to surface it. + +--- + +## Use Cases + +**Validation-Stage EdTech Founder Who Keeps Repeating the Same Partnership Error** + +An edtech founder has pursued three consecutive school-district partnerships, and each has collapsed during the procurement phase for similar reasons: misaligned timelines, underestimated bureaucratic complexity, and insufficient legal review. After each failure, the founder attributed the loss to "district politics" and moved to the next prospect with the same approach. A mentor applies the weakness framework: the inbuilt weakness is the founder's limited perspective on institutional procurement (having no prior experience in education sales), and the acquired weakness is the pattern of externalising blame rather than updating the approach. The safeguard prescription: (a) an automatic rule that no partnership proposal is submitted without review by someone with district procurement experience, and (b) a pre-submission checklist covering the seven most common procurement failure points. The fourth partnership closes successfully -- not because the founder became smarter, but because the safeguard made the recurring blind spot irrelevant. + +**Growth-Stage SaaS CEO Whose Cover-Up Compounded a Pricing Mistake** + +A SaaS CEO at $6M ARR approved a new pricing tier that inadvertently grandfathered enterprise customers at rates 40% below the intended level. Rather than disclosing the error to the board and customers, the CEO attempted to quietly adjust pricing in the next renewal cycle, hoping no one would notice. Three months later, the enterprise sales team discovered the discrepancy, customer trust eroded, and the board learned of the error through a customer complaint rather than from the CEO. The initial mistake -- a pricing calculation error -- was a minor operational failure. The cover-up destroyed board confidence and required six months to repair. Applying the four-step protocol retroactively, the CEO acknowledges that the cover-up instinct was the ego default (protecting self-image as a competent pricing strategist) compounded by the emotion default (fear of board disapproval). The safeguard installed for the future: all pricing changes require a 72-hour review period with cross-functional sign-off, and any post-launch error is disclosed to the board within 48 hours regardless of severity. + +**Scale-Stage Marketplace Founder Using Perspective Shifts to Surface Organisational Blind Spots** + +A marketplace CEO at $25M ARR notices that customer satisfaction scores have plateaued despite increasing investment in customer success. Standard analysis reveals no obvious failure point. The CEO applies the perspective-shift safeguard, conducting "shadow sessions" -- spending full days observing customer support interactions from the agent's perspective, then from the customer's, then from the product team's. The shift reveals what internal metrics could not: the product team measures feature completion, customer success measures response time, and neither measures the customer's actual experience of resolving a problem end-to-end. The blind spot was structural, not individual -- each team was optimising within its own frame of reference while the customer's frame remained invisible. The CEO redesigns the metric architecture around the customer's perspective rather than internal team boundaries, and satisfaction scores begin climbing within a quarter. + +--- + +## Anti-Patterns + +**1. Over-engineering safeguards until they impede execution.** A founder who installs so many rules, checklists, and friction mechanisms that every decision requires a multi-step protocol has traded one failure mode (default-driven errors) for another (bureaucratic paralysis). Safeguards should target the specific, recurring failure patterns identified through honest weakness assessment -- not every conceivable decision. The framework's own examples are strikingly simple: one rule, one checklist, one environmental change. Simplicity is a feature, not a limitation. + +**2. Using safeguards as a substitute for strength-building.** Rules and checklists manage symptoms. The four pillars -- self-accountability, self-knowledge, self-control, self-confidence -- address root causes. A founder who implements a "no decisions when angry" rule but never develops the emotional self-regulation that would make the rule unnecessary is managing, not growing. Safeguards are scaffolding; they should support strength development, not replace it. + +**3. Performing accountability without practising it.** The four-step mistake protocol becomes theatre when the founder says the right words ("I take full responsibility") while the internal narrative remains defensive ("but it really was their fault"). The test is behavioural, not verbal: does the founder's subsequent conduct change, or does the same error recur? If the same mistake happens a third time, the acceptance was performative. + +**4. Treating all mistakes as equally grave.** The framework distinguishes between reversible and irreversible errors. A pricing experiment that underperforms can be reversed in a quarter. A founding-team equity split that demoralises a co-founder may be irreversible. The safeguard investment should be proportional to the irreversibility and magnitude of the potential error, not applied uniformly across all decisions. + +**5. Refusing external perspective as a weakness management tool.** The founder who says "I know my blind spots" is almost certainly wrong -- by definition, blind spots are the things you cannot see. The framework explicitly requires external input: other people can catalogue your weaknesses with clarity that self-reflection cannot match. Refusing to solicit, hear, or act on external feedback is the ego default disguised as self-sufficiency. + +--- + +## By Stage + +| Stage | Weakness Profile | Safeguard Priority | +|-------|-----------------|-------------------| +| Idea | Overconfidence in untested assumptions; limited market perspective; ego entanglement with the concept | Prevention (avoid irreversible commitments before validation) and perspective shifts (customer and sceptic viewpoints before building) | +| Validation | Confirmation bias in interpreting signals; emotional reactivity to negative feedback; fatigue from high-intensity experimentation | Automatic rules (define falsification criteria before running experiments) and HALT protocol before interpreting ambiguous customer data | +| Early Traction | First-playbook inertia; acquired habits from scrappy phase that become liabilities at scale; founder fatigue as a chronic condition | Friction (make it harder to keep doing things the old way) and checklists for decisions that are now recurring and high-frequency | +| Growth | Organisational blind spots replacing individual ones; cover-up culture if psychological safety is low; standards erosion as team grows faster than culture | Perspective shifts (cross-functional shadow sessions) and guardrails (decision protocols that distribute scrutiny across roles) | +| Scale | Institutional inertia; CEO blind spots amplified through deference culture; mistake-handling becomes a systemic rather than personal challenge | Institutional safeguard architecture: error-disclosure norms, pre-mortem requirements for major initiatives, mandatory perspective rotation in strategic planning | + +At the validation stage, the most critical safeguard is the pre-commitment to falsification criteria. The principle aligns with scientific method: define what evidence would cause you to abandon the hypothesis before you run the experiment. Without this safeguard, the ego default will reinterpret every ambiguous signal as confirmation. + +At scale, the CEO's personal safeguards must become organisational infrastructure. A CEO who handles their own mistakes well but has built no system for organisational mistake-handling has created a single point of failure. The four-step protocol -- accept, learn, commit, repair -- should be embedded in the company's post-mortem culture, not dependent on the CEO's personal discipline. + +--- + +## Output Template + +```markdown +# Weakness and Safeguard Assessment -- [Name / Context] + +**Date:** [Date] +**Decision domain:** [Area being assessed -- hiring, strategy, operations, etc.] + +## Weakness Inventory + +| Weakness | Type | Root Cause | Current Impact | Compounding Risk | +|----------|------|-----------|----------------|-----------------| +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | + +## Safeguard Design + +| Weakness | Strategy | Specific Safeguard | Implementation | +|----------|----------|-------------------|----------------| +| [Target weakness] | [Prevention/Rule/Friction/Guardrail/Perspective] | [Exact mechanism] | [How and when to deploy] | +| [Target weakness] | [Prevention/Rule/Friction/Guardrail/Perspective] | [Exact mechanism] | [How and when to deploy] | + +## Blind Spot Probe +- Perspective shift attempted: [Whose viewpoint was adopted] +- What was revealed: [Insight previously invisible] +- Action taken: [Change implemented] + +## Mistake Log (Recent) + +| Mistake | Step 1: Accepted? | Step 2: Root Cause | Step 3: Commitment | Step 4: Repair Status | +|---------|-------------------|-------------------|-------------------|----------------------| +| [Description] | [Y/N + evidence] | [What was learned] | [Specific plan] | [Complete/In progress/Not started] | + +## HALT Check (Current State) +- Hungry: [Y/N] +- Angry/Emotional: [Y/N] +- Lonely/Isolated/Unfamiliar environment: [Y/N] +- Tired/Sleep-deprived: [Y/N] +- **Decision readiness:** [Ready / Defer recommended] +``` + +--- + +## Related Skills + +- **[Enemies of Clear Thinking](enemies-of-clear-thinking.md)** -- The diagnostic foundation: understanding which defaults are active informs which weaknesses need safeguards and which mistakes are most likely to recur. +- **[Building Thinking Strength](building-thinking-strength.md)** -- Strength and safeguards are complementary; strength addresses acquired weaknesses at the root while safeguards protect against inbuilt weaknesses that strength cannot eliminate. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's pre-mortem technique and reference-class forecasting are specific safeguard implementations within the broader architecture. +- **[Decision-Making Under Pressure](../leadership/decision-making-under-pressure.md)** -- The daily habits of reframing, perspective-gathering, and ethical pre-commitment are operationalised safeguards for time-pressured decisions. +- **[Stoic Control and Clarity](../stoic/stoic-control-and-clarity.md)** -- The Stoic practice of focusing only on what is within one's control is itself a perspective-shift safeguard. +- **[Stoic Pragmatism](../stoic/stoic-pragmatism.md)** -- The Stoic emphasis on practical action over theoretical understanding mirrors the insistence that knowing about weaknesses without building safeguards changes nothing. +- **[Learning from Failure](../leadership/learning-from-failure.md)** -- The mistake-handling protocols extend into the broader organisational practice of extracting learning from failure without blame. diff --git a/plugins/foreman/content/skills/thinking/wanting-what-matters.md b/plugins/foreman/content/skills/thinking/wanting-what-matters.md new file mode 100644 index 0000000..f165705 --- /dev/null +++ b/plugins/foreman/content/skills/thinking/wanting-what-matters.md @@ -0,0 +1,211 @@ +--- +name: "wanting-what-matters" +description: "Addresses the meta-question behind all decision-making: whether the entrepreneur is optimising for the right things. Covers the hedonic treadmill and 'happy-when' trap, Dickens's A Christmas Carol as a decision-making parable, what happiness research from the elderly consistently reveals, memento mori as a practical decision filter (the deathbed test), the regret-minimisation framework, and the distinction between ordinary moments and defining moments. Use when a founder suspects they are chasing metrics that do not produce satisfaction, when strategic priorities feel misaligned with personal values, when mortality awareness could sharpen decision-making, or when the question shifts from 'how do I get what I want?' to 'is what I want worth wanting?'" +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - purpose + - hedonic-treadmill + - mortality + - regret-minimisation + - happiness + - values + - ordinary-moments + - wisdom + - deathbed-test + - phronesis +related_skills: + - evaluating-and-deciding + - defining-and-exploring-problems + - stoic-mortality-and-perspective + - stoic-acceptance-amor-fati + - purpose-driven-leadership + - focus-and-priority-management +author: "Fatih Guner" +--- + +# Wanting What Matters + +DEATHBED TEST. The clearest decision-making tool is not a matrix or a framework -- it is asking what you would regret not having done from your deathbed. Jeff Bezos used precisely this test when deciding whether to leave a comfortable Wall Street career to start an online bookstore in 1994: "I knew that when I was 80 I was not going to regret having tried. I was not going to regret trying to participate in this thing called the Internet that I thought was going to be a really big deal. I knew that if I failed I wouldn't regret that, but I knew the one thing I might regret is not ever having tried." The regret-minimisation framework cuts through analytical complexity with uncomfortable speed because it does not ask what will maximise returns -- it asks what will minimise the ache of a life unlived. The Clear Thinking framework argues that all the decision-making discipline in the world amounts to very little if the things being pursued are not worth pursuing. Good judgment, at its highest expression, is not knowing how to get what you want. It is knowing which things are worth wanting. + +--- + +## The Framework + +This framework operates at a different altitude from most decision-making tools. Where evaluation frameworks ask "which option is best?", this one asks "best for what?" It proceeds through four lenses, each progressively closer to the core question. + +### Lens 1: The Hedonic Treadmill and the Happy-When Trap + +Psychologists Philip Brickman and Donald Campbell identified a phenomenon so pervasive it functions almost as a natural law: humans adapt to improvements in circumstances and revert to a baseline level of satisfaction. The car that was supposed to bring lasting happiness provides two weeks of euphoria before becoming the new normal -- and the new basis for comparison with everyone else's car. The promotion that was supposed to validate years of effort produces a brief high before introducing new problems, new peers to compare against, and a fresh version of the same discontent. + +The framework labels the sufferers "happy-when" people. They will be happy when they make more money. Happy when they get the credit they deserve. Happy when they find the right partner. The conditional never resolves because each "when" becomes the new floor, and a new "when" materialises immediately above it. It is a one-way door: once through, perspective on where you were is lost, and only the gap to the next level remains visible. + +The entrepreneurial version is particularly virulent. The founder who will be happy when they close the seed round discovers, upon closing it, that happiness now depends on the Series A. The Series A produces a brief high before the pressure of growth targets imposes a new conditional. The text quotes an observation that cuts close to the bone: "The next zero in your bank account won't satisfy you any more than you are satisfied now." + +**The diagnostic question:** If you achieved the goal you are currently pursuing, and the resulting satisfaction lasted only two weeks before reverting to baseline, would you still pursue it? If not, the goal is a treadmill metric -- it generates motion without destination. + +### Lens 2: Dickens's Hidden Lesson + +A Christmas Carol is not a holiday story. It is a decision-making parable. Ebenezer Scrooge is visited by three spirits who show him the past, the present, and a future that might be -- a future in which he is dead and no one mourns him. His former associates are relieved, spiteful, or indifferent. The vision provides what no spreadsheet can: the long-term consequences of his current trajectory, compressed into a single night. He gets something almost no one gets -- the chance to see where his current decisions lead and to change course before it is too late. + +The text illustrates the real-world version with a retired CEO who had played by society's scoreboard -- wealth, status, power -- with sharp elbows in a hypercompetitive culture. He quoted Tywin Lannister, called himself a lion, and never lacked golfing companions while in office. Upon retiring, most of his "friends" stopped returning calls. His transactional approach to relationships had generated professional compliance, not genuine connection. Unlike Scrooge, he received no second chance. + +**The diagnostic question:** If you continue on your current trajectory for ten years and then look back, what will you wish you had done differently? The discomfort this question produces is proportional to the gap between your current direction and your actual values. + +### Lens 3: What the Happiness Experts Actually Say + +Gerontologist Karl Pillemer spent seven years interviewing Americans in their seventies, eighties, and nineties -- people he describes as "the most credible experts we have on how to live happy and fulfilled lives during hard times." His findings are consistent across demographics and are striking for what they include and what they omit. + +**What the elderly say matters:** + +- Say things now to people you care about -- gratitude, forgiveness, questions you have always wanted to ask +- Spend the maximum amount of time with your children +- Savour daily pleasures instead of waiting for "big-ticket items" to produce happiness +- Work in a job you love +- Choose your life partner carefully + +**What none of them said:** + +- None said that to be happy you should work as hard as you can to make money +- None said it was important to be as wealthy as the people around you +- None said to choose your career based on earning potential +- None said they regretted not getting even with someone who wronged them + +**Their largest regret:** Worrying about things that never happened. "Worrying wastes your life," one respondent said. + +The most powerful finding was attitudinal. An 89-year-old woman, when asked to explain her happiness, answered: "In my 89 years, I've learned that happiness is a choice -- not a condition." Pillemer concluded that the elderly "make the key distinction between events that happen to us, on the one hand, and our internal attitude toward happiness, on the other. Happy in spite of." + +This reframes happiness as a decision -- one that sits on the same continuum as every other decision an entrepreneur makes. It can be chosen daily, or it can be deferred to a "when" that never arrives. + +### Lens 4: Memento Mori as a Practical Decision Filter + +The Stoic practice of memento mori -- remembering that you will die -- is treated philosophically in the [Stoic Mortality and Perspective](../stoic/stoic-mortality-and-perspective.md) skill, where Marcus Aurelius and Seneca use mortality awareness to cultivate urgency, clarity, and the view from above. What follows here is the applied version: mortality as a filter for specific decisions. + +**The Deathbed Test.** Imagine yourself at eighty, sitting on a park bench on a beautiful autumn day. Who is in your life? What have you accomplished? What memories do you cherish? What do you regret? Steve Jobs performed this exercise daily: "If today were the last day of my life, would I want to do what I am about to do today?" Whenever the answer was no too many days in a row, he knew something had to change. + +The deathbed test is not a philosophical exercise. It is a filter with three operational applications: + +1. **The regret filter.** We regret the things we did not do more than the things we did. The pain of trying and failing is intense but brief. The pain of failing to try is mild but permanent. When facing a decision between safety and risk, ask which version produces the less tolerable regret at eighty. + +2. **The ordinary moments filter.** What we think of as defining moments -- promotions, launches, funding rounds -- matter less to life satisfaction than the accumulation of tiny moments that did not seem significant at the time. The family dinners. The marks on the doorframe measuring how tall the children were. The afternoon you spent on the couch talking about nothing. The phrase is precise: "Tiny delights over big bright lights." The deathbed test consistently reveals that the things remembered are not the things that were optimised for. + +3. **The relationship filter.** Across Pillemer's interviews, across hospice research, across every longitudinal study of life satisfaction, the finding is identical: relationships are the variable that matters most and the variable most frequently sacrificed in pursuit of variables that matter less. The deathbed test restores the ranking that day-to-day urgency inverts. + +### The Integrating Concept: Phronesis + +The ancient Greeks had a word for the wisdom of knowing how to order your life to achieve the best results: phronesis. It is distinct from technical skill (techne) and from theoretical knowledge (episteme). Phronesis is practical wisdom -- the ability to discern which ends are worth pursuing and which means are appropriate for pursuing them. + +The framework revolves around this concept: good judgment is not merely knowing how to get what you want. It is knowing what to want. "If you want to develop good judgment, start by asking two questions: 'What do I want in life? And is what I want actually worth wanting?' Until you've answered the second question, all the decision-making advice in the world isn't going to do you much good." + +--- + +## Prompts + +**Prompt 1 -- Hedonic Treadmill Audit:** +> "I am pursuing [goal/metric] for my [stage] [sector] company. Apply the hedonic treadmill test: if I achieve this goal and the satisfaction lasts only two weeks before reverting to baseline, was the pursuit worthwhile? Identify which of my current goals are treadmill metrics (generating motion without destination) and which are genuinely aligned with long-term satisfaction. Suggest replacements for the treadmill metrics." + +**Prompt 2 -- Deathbed Test for a Specific Decision:** +> "I am deciding between [Option A] and [Option B]. Project me forward to age 80. From that perspective, which choice produces the more tolerable regret? Apply the three operational filters: (1) regret filter -- which failure of action would haunt me more? (2) ordinary moments filter -- which option generates more of the small daily experiences that matter in retrospect? (3) relationship filter -- which option better preserves or strengthens the relationships that the elderly consistently identify as most important?" + +**Prompt 3 -- Trajectory Projection (Dickens Lens):** +> "Describe my current professional and personal trajectory based on these facts: [describe current priorities, time allocation, relationships, and goals]. Now project that trajectory ten years forward, assuming no changes. What does the picture look like? Where is the gap between where this trajectory leads and where I would actually want to end up? Identify the two or three adjustments that would close the gap most effectively." + +**Prompt 4 -- Phronesis Audit for the Founder:** +> "I have built or am building a company around [mission/product]. Separate the things I am pursuing into two categories: (1) things that are genuinely worth wanting based on what happiness research and end-of-life wisdom consistently identify, and (2) things I am pursuing because of social comparison, status signalling, or the hedonic treadmill. For each item in category 2, suggest what I might pursue instead that would produce more durable satisfaction." + +--- + +## Use Cases + +**Growth-Stage Founder on the Edge of Burnout** + +A founder of a Series B logistics platform works 80-hour weeks, has missed the last three family holidays, and tells herself she will "slow down after the IPO." Applying the hedonic treadmill lens, she recognises a pattern: she said the same thing before the Series A and before the Series B. Each milestone, upon achievement, produced brief satisfaction and immediately generated a new conditional. The deathbed test reveals that she will not remember the Q3 revenue target; she will remember that she missed her daughter's first piano recital. The ordinary moments filter makes visible what the P&L obscures: the daily accumulation of absences that compound as irreversibly as interest. The operational adjustment is not dramatic -- it is scheduling two non-negotiable evenings per week and treating them with the same sanctity as board meetings. The adjustment costs nothing in strategic capability and everything in the metric that actually matters. + +**Pre-Seed Founder Choosing Between Safety and Risk** + +A 34-year-old product manager at a major tech company has a working prototype for a climate-tech startup but cannot bring himself to leave the security of a $280K salary. Bezos's regret-minimisation framework applies directly: at eighty, will he regret having tried and failed, or will he regret never having tried? The pain of a failed startup is intense but finite -- twelve to eighteen months of reduced income and bruised ego. The pain of "what if I had tried?" is low-grade but permanent. The deathbed test does not guarantee the startup succeeds. It clarifies which failure is easier to live with. He negotiates a six-month unpaid leave of absence -- a margin of safety that preserves the option to return while eliminating the regret of never having started. + +**Scaled CEO Redefining Success Metrics** + +The CEO of a 500-person company has achieved every goal he set at twenty-five: wealth, recognition, a company that bears his name. He finds himself, at fifty, unable to articulate what he is working toward beyond "more." Pillemer's research provides the mirror: none of the elderly said that happiness came from maximising wealth, and none regretted failing to accumulate more status. The Dickens lens -- projecting the current trajectory forward -- shows a future in which the company thrives and the CEO's closest relationships are transactional. The phronesis audit separates the goals worth wanting (building something that outlasts him, mentoring the next generation of leaders, deepening his marriage) from the goals that are pure treadmill (the next board seat, the next magazine profile). The operational result is a restructured calendar that allocates 30 percent of his time to mentoring and relationship investment, funded by delegating operational decisions he was holding out of habit rather than necessity. + +--- + +## Anti-Patterns + +**Using the deathbed test to justify recklessness.** The test is a filter for values alignment, not a licence to ignore financial reality. "Life is short" is the most frequently abused insight in the self-help canon. The founder who quits a stable job with no savings, no prototype, and no plan is not applying memento mori -- they are applying magical thinking with a philosophical veneer. + +**Treating this skill as a replacement for analytical decision-making.** Wanting what matters sits above the evaluation frameworks, not in opposition to them. Once you have clarity on what is worth pursuing, you still need criteria weighting, margin of safety, and execution fail-safes to pursue it effectively. Values without competence produce noble failures. + +**Dismissing the hedonic treadmill as obvious.** Everyone nods when told that money does not buy happiness. Almost no one adjusts their behaviour accordingly. The test of whether you have internalised this lens is not whether you agree with it intellectually but whether your calendar and your bank statement reflect the agreement. + +**Applying Pillemer's findings selectively.** The elderly do not say "don't work hard." They say "work in a job you love" and "don't choose your career based on earning potential." These are compatible with extreme ambition. What they are incompatible with is pursuing money or status as terminal goals rather than as byproducts of meaningful work. + +**Confusing memento mori with pessimism.** Mortality awareness does not produce despair in those who apply it rigorously. It produces clarity. The Stoic skill on mortality and perspective develops the philosophical dimension of this practice. The present skill uses it as a filter: does this specific decision pass the deathbed test? The two applications are complementary, not competing. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The founder decides what problem to solve and why. The deathbed test filters out ideas pursued for status or trend-following and surfaces ideas aligned with genuine values. | The hedonic treadmill audit is personal: "If this company succeeds and I feel the same way in two weeks, was it the right company to build?" | +| Validation | Testing whether the problem matters to customers, but also whether solving it matters to the founder on a ten-year horizon. | Founders who are not intrinsically motivated by the problem they are solving tend to quit during the hardest phase -- the one between prototype and traction. The Dickens lens exposes this misalignment before capital and time are committed. | +| Early Traction | The hedonic treadmill intensifies as metrics become visible. MRR, user counts, and NPS scores become the new "happy-when" conditionals. | The ordinary moments filter becomes a daily practice: are the rhythms of building this company producing daily satisfaction, or is all satisfaction deferred to a future milestone? | +| Growth | Social comparison accelerates. Other founders raise larger rounds, grow faster, command more press. The treadmill runs faster. | Pillemer's research is the corrective: none of the elderly wished they had been wealthier than their peers. The relationship filter protects against the subtle erosion of personal connections that growth-stage intensity produces. | +| Scale | Legacy questions emerge. The founder asks "what will I be remembered for?" and the answer may not align with current priorities. | The phronesis audit becomes strategic: is the company optimised for the things that will matter in retrospect, or for the things that the market currently rewards? Commander's intent should reflect values, not just targets. | + +--- + +## Output Template + +```markdown +# Values Alignment Audit + +## Current Goals and Priorities +| Goal | Category: Worth Wanting / Treadmill Metric | Evidence | +|------|---------------------------------------------|----------| +| [goal 1] | [classification] | [why this classification] | +| [goal 2] | [classification] | [why this classification] | +| [goal 3] | [classification] | [why this classification] | + +## Deathbed Test Results +- **At 80, what would I regret not having done?** [answer] +- **At 80, what current concerns would seem trivial?** [answer] +- **At 80, which relationships would I wish I had invested in more?** [answer] + +## Ordinary Moments Inventory +- **Daily experiences that produce genuine satisfaction now:** [list] +- **Daily experiences I am deferring for a future "when":** [list] +- **Small adjustments that would increase daily satisfaction without strategic cost:** [list] + +## Trajectory Projection (Dickens Lens) +- **If nothing changes in 10 years, where do I end up?** [description] +- **Where do I actually want to end up?** [description] +- **The gap:** [description] +- **Two to three adjustments that close the gap:** [list] + +## Hedonic Treadmill Check +- **Current "happy-when" conditional:** [I will be happy when...] +- **Previous "happy-when" conditionals that were achieved but did not produce lasting satisfaction:** [list] +- **Replacement goals that are not conditional on external achievement:** [list] +``` + +--- + +## Related Skills + +- **[Stoic Mortality and Perspective](../stoic/stoic-mortality-and-perspective.md)** -- Develops the philosophical foundations of memento mori; this skill applies those foundations as a practical decision filter for specific entrepreneurial choices. +- **[Evaluating and Deciding](evaluating-and-deciding.md)** -- Once values are clear, this skill provides the mechanics: criteria weighting, margin of safety, execution fail-safes, and decision journals. +- **[Defining and Exploring Problems](defining-and-exploring-problems.md)** -- The problem-definition discipline ensures that the right question is being asked; this skill ensures the question is being asked in service of the right life. +- **[Purpose-Driven Leadership](../leadership/purpose-driven-leadership.md)** -- Extends the personal values alignment into organisational mission and culture. +- **[Focus and Priority Management](../leadership/focus-and-priority-management.md)** -- The tactical complement: once you know what matters, this skill provides the operational discipline for protecting it against the urgent-but-unimportant. +- **[Stoic Acceptance and Amor Fati](../stoic/stoic-acceptance-amor-fati.md)** -- The Stoic practice of embracing fate and finding meaning in adversity, a philosophical companion to the happiness-as-choice finding. +- **[Career Strategy for Leaders](../leadership/career-strategy-for-leaders.md)** -- The four-question self-grade and career fuel audit are practical applications of wanting what matters to specific career decisions and trade-offs. diff --git a/plugins/foreman/content/skills/writing/clarity-and-concision.md b/plugins/foreman/content/skills/writing/clarity-and-concision.md new file mode 100644 index 0000000..9a85d25 --- /dev/null +++ b/plugins/foreman/content/skills/writing/clarity-and-concision.md @@ -0,0 +1,241 @@ +--- +name: "clarity-and-concision" +description: "Teaches techniques for achieving relentless clarity and ruthless concision in business writing, including the 20-word sentence rule, concrete detail over abstraction, word economy tactics, and the reader's perspective test. Features extensive before/after examples demonstrating how bloated corporate prose can be cut by 50-70% without losing meaning. Use when tightening any business document, eliminating wordiness, improving readability scores, preparing executive summaries, or when writing feels vague or overlong." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - clarity + - concision + - word-economy + - readability + - editing + - plain-language + - business-writing +related_skills: + - revising-and-editing + - plain-language-and-flow + - writing-with-purpose + - business-writing-for-leaders +author: "Fatih Guner" +--- + +# Clarity and Concision + +Consider a mid-sized company where 200 professionals each write an average of 10 internal messages per day, each message averaging 150 words. That is 300,000 words produced daily -- roughly three novels. Now suppose that 30% of those words are unnecessary. The organisation is generating 90,000 wasted words every working day. At an average reading speed of 250 words per minute, that is 360 person-hours per day spent reading words that should never have been written. Six full-time employees, year-round, doing nothing but reading padding. The financial cost of corporate verbosity is not metaphorical. It is measurable, and it is staggering. + +Clarity and concision are not aesthetic preferences. They are economic imperatives. + +--- + +## The Framework + +### Clarity as Courage + +Clarity is a double-edged sword. When a writer takes a position or recommends a course of action, the writing is clear -- and the writer is exposed. People who do not want to commit make their writing muddy on purpose. They leave room to claim credit for good outcomes and deny responsibility for bad ones. Readers, however, perceive this not as strategic ambiguity but as spinelessness. Clear writing requires taking a stand. + +The test for clarity is simple: show the draft to a colleague who has no context and ask them to identify the three main points. If they cannot do so accurately after one read-through, the writing is not clear enough. + +### The Research Case for Less + +The intuition that shorter is better has been validated experimentally, at scale. *Writing for Busy Readers* reports a field experiment in which two versions of an email were sent to 7,002 school board members across the United States requesting completion of a short online survey. One email contained 127 words; the other contained 49 words. The 49-word version produced nearly double the response rate -- 4.8% versus 2.7%. The survey itself was identical in both conditions. Some recipients likely looked at the longer email and declined to engage at all. Others read partway through and never reached the request. Still others used the email's length as a proxy for how long the survey would take: 29% of those who saw the concise version estimated the survey at under five minutes, compared with just 15% of those who saw the longer version. + +The average American adult reads nonfiction at approximately 240 words per minute -- four words per second. At that rate, every unnecessary sentence costs measurable time, compounded across every recipient. The arithmetic is unforgiving: a 500-word email sent to 200 people that could have been written in 250 words wastes over two hours of collective reading time. Scale that to a year of weekly all-hands updates and the cost becomes a line item no one budgets for but everyone pays. + +Perhaps the most revealing finding is how poorly writers self-correct. Gabrielle Adams and colleagues at the University of Virginia asked participants to summarise a short article and then edit their summaries to improve them. Eighty-three percent of participants *added* words during the editing pass rather than removing them. The same pattern held across topics from travel itineraries to patents. The instinct to accrete rather than subtract appears to be a cognitive default -- one that writers must consciously override. + +Blaise Pascal captured the asymmetry centuries ago: "I would have written a shorter letter if I'd had more time." The line has been attributed to Twain, Locke, and a dozen others, which only confirms how universally writers recognise the problem -- and how rarely they solve it. + +### The 20-Word Rule + +Research has confirmed repeatedly that the optimal average for readable sentences is no more than 20 words. This does not mean every sentence should be exactly 20 words -- variety in sentence length creates rhythm and holds interest. Some sentences should be very short. Others can be longer and more complex, building layered arguments. But the average, across a document, should hover around 20. + +**NOT THIS:** +> Efficiency measures that have been implemented by the company with strong involvement of senior management have generated cost savings while at the very same time assisting in the building of a culture that is centered around the value of efficiency. [40 words] + +**BUT THIS:** +> Our senior management team has cut costs and made the company more efficient. We expect to be more profitable for the next four quarters. [24 words] + +The first version says less with more. The second says more with less. + +### Show, Don't Tell + +Concrete business writing is persuasive because it is evidence-based, clear, and memorable. Abstract assertions invite scepticism; specific details earn credibility. + +| NOT THIS | BUT THIS | +|----------|----------| +| He was a bad boss. | He got a promotion based on his assistant's detailed reports, but then -- despite the company's record profits -- denied that assistant even routine cost-of-living raises. | +| The company lost its focus and floundered. | The CEO acquired five unrelated subsidiaries -- as far afield as a paper company and a retailer of children's toys -- and then couldn't service the $26 million in debt. | + +The vague versions are opinions. The specific versions are evidence that leads readers to draw the same conclusions -- independently, and therefore more convincingly. + +### Word Economy: Three Surgical Techniques + +Wordiness operates on multiple levels, from bloated sentences to verbose phrases to unnecessary padding. Three techniques eliminate the majority of excess: + +**Technique 1: Delete prepositions (especially "of").** +- *April of 2013* becomes *April 2013* +- *point of view* becomes *viewpoint* +- *the purpose of this evaluation* becomes *this evaluation's purpose* + +**Technique 2: Replace -ion nouns with verbs.** +- *was in violation of* becomes *violated* +- *provided protection to* becomes *protected* +- *made a determination* becomes *determined* + +**Technique 3: Replace be-verbs with stronger verbs.** +- *was hanging* becomes *hung* +- *is indicative of* becomes *indicates* +- *are in agreement* becomes *agree* + +These three rules, applied mechanically, typically reduce word count by 20-40%. + +### Before/After: The Compound Effect + +| NOT THIS | Words | BUT THIS | Words | +|----------|-------|----------|-------| +| The trend in the industry is toward self-generation by some companies of their own websites, and Internet technology is changing the nature of training necessary to acquire the skill of website development at an acceptable level of sophistication, so that this activity can more and more be handled in-house. | 49 | Since Internet technology makes it easier than ever to develop sophisticated websites, some companies now develop their own in-house. | 19 | +| We are unable to fill your order at this point in time because there is an ongoing dock strike that affects our operations. | 23 | We cannot fill your order right now because of the dock strike. | 12 | +| I am writing in response to a number of issues that have arisen with regard to the recent announcement that there will be an increase in the charge for the use of our lobby computers. | 35 | You may have heard that we're raising the fees for using our lobby computers. | 14 | +| The greater number of these problems can readily be dealt with in such a way as to bring about satisfactory solutions. | 21 | Most of these problems can be readily solved. | 8 | + +In the most extreme case, 49 words become 19 -- a 61% reduction with no loss of meaning. The shorter versions are not merely more efficient; they are more persuasive. Readers trust writers who respect their time. + +### Eliminate Padding + +Certain phrases contribute nothing but the illusion of seriousness: + +- *in this connection it might be observed that* -- delete entirely +- *it is important to bear in mind that* -- delete entirely +- *it is interesting that* -- delete entirely +- *it is notable that* -- delete entirely +- *it is worthwhile to note that* -- delete entirely +- *it should be pointed out that* -- delete entirely + +These phrases are throat-clearing. They signal to the reader that the writer is about to say something -- rather than simply saying it. + +--- + +## Prompts + +**Prompt 1 -- Word Economy Audit:** +> Here is a business document: [paste text]. Apply the three word-economy techniques: (1) delete unnecessary prepositions, (2) replace -ion nouns with verbs, (3) replace be-verbs with stronger alternatives. Also identify and eliminate all padding phrases. Show the original word count, the revised text, and the new word count. Calculate the percentage reduction. + +**Prompt 2 -- Clarity Stress Test:** +> Pretend you are an intelligent reader with no prior context about my company or project. Read this document: [paste text]. After one read-through: (1) What are the three main points? (2) What action is the writer requesting? (3) Where did you get confused? (4) Which passages could be misinterpreted? (5) Where did you have to re-read a sentence? Identify every clarity failure and suggest specific revisions. + +**Prompt 3 -- Show Don't Tell Conversion:** +> Here is a draft containing abstract assertions: [paste text]. Identify every sentence that "tells" rather than "shows" -- every opinion, generalisation, or claim that lacks supporting evidence. For each, either suggest a concrete, specific replacement or flag it as needing data I should gather. The goal is a document where every claim is supported by evidence. + +**Prompt 4 -- Sentence Length Analysis:** +> Analyse the sentence lengths in this document: [paste text]. Calculate the average. Identify the five longest sentences and suggest how to break them up. Identify any passages where all sentences are similar in length and suggest how to vary the rhythm. Target an average of 20 words or fewer. + +**Prompt 5 -- The Subtraction Edit:** +> Most editors instinctively add words when revising. Reverse that default. Take this draft: [paste text]. Your only permitted operation is deletion -- remove words, sentences, and entire paragraphs. Do not add a single word. Do not rephrase; only cut. Produce the shortest version that preserves every essential idea and action request. Show the original word count, the revised word count, and the percentage reduction. Then list, in a table, every deleted passage with a one-line justification for why it was expendable. + +--- + +## Use Cases + +**Idea-Stage Founder Rewriting a Landing Page** + +A founder's landing page opens with: "We aspire to be a partner primarily concerned with providing our clients the maximal acquisition of future profits and assets and focus mainly on clients with complex and multi-product needs, large and midsized corporate entities, individual or multiple entrepreneurial agents, and profit-maximising institutional clients." After applying the clarity and concision framework: "We're a client-focused firm dedicated to making sure you get the most out of our services. Our client base includes individual entrepreneurs, midsized companies, and large corporations." The original was 46 words of impenetrable corporate fog. The revision is 30 words that a customer can actually understand -- and that a search engine can parse. + +**Growth-Stage Company Tightening Investor Updates** + +A SaaS company's monthly investor update runs 2,500 words. Most investors skim it in under two minutes. Applying word economy techniques across three consecutive updates: Update 1 drops from 2,500 to 1,800 words (28% reduction). Update 2 drops to 1,400 words as the writer internalises the preposition and be-verb rules. Update 3 reaches 1,100 words -- the same information in 56% less space. Investor engagement (measured by reply rate) increases by 40%, because the update now respects the audience's time. + +**Early-Traction Nonprofit Doubling Newsletter Engagement** + +A nonprofit sends a weekly newsletter to 50,000 subscribers linking to six curated resources. The editorial team, composed of professional writers, drafts a 566-word newsletter with context, supporting quotes, and background detail for each link. Applying the subtraction edit -- cutting supporting detail that is relevant but not essential, removing author quotes, and eliminating scene-setting paragraphs -- the team produces a 275-word version preserving all six resource links. The concise version generates twice as many link clicks as the original. The lost detail represented the kind of supplementary material that writers value and readers skip. As one researcher in the *Writing for Busy Readers* study observed: readers who received the shorter version did not report feeling less informed -- they simply engaged more. + +--- + +## Anti-Patterns + +1. **Confusing Brevity with Concision.** Brevity means being short. Concision means being short without losing substance. A one-sentence summary that omits critical context is brief but not concise. The goal is to include everything necessary and nothing else. + +2. **Using Complexity as a Status Signal.** Some writers equate long sentences and Latinate vocabulary with intelligence. Readers equate it with obscurity. A 136-word sentence scoring 8.2 on the Flesch Reading Ease scale does not signal sophistication -- it signals that the writer is either hiding something or has not thought clearly about the subject. + +3. **Cutting Too Aggressively.** Concision taken to the extreme produces telegraphic prose that sounds curt and loses the writer's voice. The goal is to remain "faithful to the sounds and rhythms of normal, down-to-earth English" while eliminating waste. + +4. **Editing for Concision Before Revising for Structure.** Cutting 30% of the words from a structurally flawed document produces a shorter structurally flawed document. Always revise the macro structure first, then edit for concision. + +5. **Telling Instead of Showing.** Asserting that "the company performed poorly" is brief, but it is not persuasive. The concrete version -- "The CEO acquired five unrelated subsidiaries and couldn't service the $26 million in debt" -- is longer but incomparably more effective. Concision serves clarity; it does not replace evidence. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch compression | Every word on a pitch deck slide or one-pager must justify its existence. At the idea stage, the entrepreneur has less content and more temptation to pad. Concision here means saying less but meaning more. | +| Validation | Data-driven concision | Replace assertions with numbers. "Strong traction" becomes "47 paying customers in 3 months with 12% week-over-week growth." Specific data is inherently concise because it replaces paragraphs of qualitative hedging. | +| Early Traction | Communication volume management | The sheer volume of writing at this stage makes concision a time-management tool. Cutting 30% of words across all documents saves hours per week for both writer and readers. | +| Growth | Readability standards | Establish organisational standards: maximum average sentence length, maximum word count for recurring document types, required use of headings for documents over 500 words. Concision becomes policy. | +| Scale | Brand voice consistency | At scale, every external communication reflects the brand. A house style that mandates concision prevents the verbal inflation that accompanies corporate growth and bureaucratic layering. | + +--- + +## Output Template + +```markdown +# Clarity and Concision Audit: [Document Title] + +## Readability Metrics +- **Original word count:** [X] +- **Target word count:** [Y] (reduction target: [Z]%) +- **Average sentence length:** [X words] (target: 20 or fewer) +- **Longest sentence:** [X words] (location: paragraph [N]) +- **Flesch Reading Ease score:** [X] (target: 50+) + +## Clarity Assessment +- **Main points identifiable on first read?** [Yes/No] +- **Ambiguous passages:** [List with paragraph numbers] +- **Abstract assertions needing evidence:** [List] +- **Jargon needing plain-language replacement:** [List] + +## Concision Edits +### Prepositions Removed +| Original | Revised | +|----------|---------| +| [phrase] | [tighter phrase] | + +### -ion Nouns Replaced with Verbs +| Original | Revised | +|----------|---------| +| [phrase] | [verb form] | + +### Be-Verbs Replaced +| Original | Revised | +|----------|---------| +| [phrase] | [stronger verb] | + +### Padding Eliminated +| Phrase Removed | Location | +|----------------|----------| +| [padding phrase] | [paragraph N] | + +## Final Metrics +- **Revised word count:** [X] +- **Actual reduction:** [Y]% +- **Revised average sentence length:** [X words] +``` + +--- + +## Related Skills + +- **[Revising and Editing](revising-and-editing.md)** -- Concision editing is one component of the broader editing discipline; this companion skill provides the full revision-then-editing sequence. +- **[Plain Language and Flow](plain-language-and-flow.md)** -- Plain language and concision are complementary disciplines: one eliminates jargon, the other eliminates waste. +- **[Writing with Purpose](writing-with-purpose.md)** -- A clear purpose prevents unnecessary content from entering the draft in the first place, making subsequent concision editing less onerous. +- **[Reader Psychology](reader-psychology.md)** -- The cognitive science of working memory limits and triage behaviour explains why every unnecessary word has a measurable cost in reader comprehension. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Leaders who model concise writing set the standard for organisational communication culture. +- **[Writing Effective Emails](writing-effective-emails.md)** -- Email is the medium where concision has the highest impact because readers triage ruthlessly and mobile screens punish verbosity. diff --git a/plugins/foreman/content/skills/writing/grammar-and-mechanics.md b/plugins/foreman/content/skills/writing/grammar-and-mechanics.md new file mode 100644 index 0000000..72c0b8e --- /dev/null +++ b/plugins/foreman/content/skills/writing/grammar-and-mechanics.md @@ -0,0 +1,189 @@ +--- +name: "grammar-and-mechanics" +description: "Provides a structured reference for the grammar and punctuation rules that most frequently undermine credibility in business writing. Covers subject-verb agreement, pronoun case, dangling modifiers, parallel construction, comma splices, and the most common usage confusions (affect/effect, that/which, who/whom). Use when proofreading pitch decks, investor updates, client proposals, or any external-facing document where a single error can erode perceived competence." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - grammar + - punctuation + - proofreading + - credibility + - usage + - writing-mechanics +related_skills: + - tone-and-engagement + - writing-effective-emails + - writing-memos-and-reports + - writing-performance-reviews +author: "Fatih Guner" +--- + +# Grammar and Mechanics + +A misplaced apostrophe has never killed a company. But it has killed pitch decks, alienated investors, and quietly disqualified founders from rooms they never knew they were being evaluated for. Grammar errors in business writing operate as a credibility tax: each one individually minor, collectively devastating. Readers may not consciously register the error, but they register its effect -- a subtle downgrade in how seriously they take the author. The founder who writes "it's revenue model" instead of "its revenue model" in a Series A memo has communicated something unintended: carelessness with details. And carelessness with details is precisely the trait investors screen for. + +The rules that follow are not pedantic niceties. They are the twelve grammatical principles and twelve punctuation conventions that, when violated, most reliably damage professional credibility. + +--- + +## The Framework + +### Twelve Essential Grammar Rules + +**1. Starting sentences with *And* or *But* is perfectly acceptable.** The myth persists from secondary school, but the best prose writers have always done it. Monosyllabic conjunctions create tighter transitions than *however* or *additionally*. + +**2. Ending a sentence with a preposition is fine.** The prohibition traces to Latin syntax and has no basis in English grammar. "What will the new product be used for?" reads more naturally than the contorted alternative. + +**3. Use *well* as an adverb, not *good*.** "The team performed well" -- not "performed good." The exception: set phrases like "a good many" or "did it but good." + +**4. The subject determines the verb's number.** Prepositional phrases that follow the subject create "false attraction" -- the verb should match the subject, not the nearest noun. + +- *Wrong:* "The details of the customized work *is* delaying the project." +- *Right:* "The details of the customized work *are* delaying the project." + +**5. *Either* and *neither* as subjects take singular verbs.** "Neither of our expansion options *provides* a total solution" -- not *provide*. + +**6. With *neither/nor* and *either/or*, the second element controls the verb.** "Neither the regional managers nor the vice-president *likes* the proposed theme." + +**7. Flat adverbs (*thus*, *doubtless*) take no *-ly* ending.** Adding *-ly* to words that are already adverbs produces nonstandard forms: *thusly* and *doubtlessly* are both incorrect. + +**8. Conjunctive adverbs (*however*, *therefore*) cannot join independent clauses with just a comma.** This produces the comma splice. Use a semicolon before and a comma after: "The campaign is ready; however, the CEO has yet to approve it." + +**9. *That* introduces restrictive clauses (no comma); *which* introduces non-restrictive clauses (with a comma).** "The report that you requested is ready" vs. "The report, which you requested, is ready." + +**10. Pronouns must agree with their antecedents in number.** "A shareholder may cast *his or her* vote" -- or restructure the sentence to use the plural: "Shareholders may cast *their* votes." + +**11. Avoid double negatives.** Subtle forms include *couldn't scarcely* (use *could scarcely*) and *not...but* constructions that create ambiguity. + +**12. Use standard English consistently.** Watch for nonstandard forms that creep in from speech: *shouldn't of* (should be *shouldn't have*), *drug* as past tense of *drag* (should be *dragged*). + +### Twelve Punctuation Essentials + +| # | Rule | Example | +|---|------|---------| +| 1 | Use the serial (Oxford) comma before the final item in a list | "Revenue, costs, and margins" | +| 2 | Place commas and periods inside quotation marks | She said "the deal is closed." | +| 3 | Use a semicolon to join related independent clauses | "Sales rose 14%; margins held steady." | +| 4 | Use a colon to introduce a list, explanation, or elaboration | "Three priorities: hiring, retention, and culture." | +| 5 | Hyphenate compound adjectives before a noun | "A well-written proposal" (but "the proposal was well written") | +| 6 | Use an em dash for emphasis or interruption | "The acquisition -- if approved -- will close in Q3." | +| 7 | Apostrophes show possession, not plurality | "The company's revenue" not "the company's revenue's" | +| 8 | *Its* (possessive) vs. *it's* (contraction of "it is") | "The firm increased its revenue" | +| 9 | Use parentheses for supplementary information | "Revenue ($4.2M) exceeded projections." | +| 10 | End declarative sentences with a single period | Never use double periods or exclamation marks in formal prose | +| 11 | Use a comma after introductory phrases | "After reviewing the data, the team recommended expansion." | +| 12 | Do not use a comma to separate a subject from its verb | *Wrong:* "The CEO, approved the budget." | + +### Common Usage Confusions + +| Confused Pair | Distinction | +|---------------|-------------| +| *affect* / *effect* | *Affect* is usually a verb (to influence); *effect* is usually a noun (a result). "The policy will *affect* margins. The *effect* will be significant." | +| *that* / *which* | *That* restricts; *which* adds information. Use *which* with commas. | +| *who* / *whom* | *Who* is the subject; *whom* is the object. Test: substitute *he/him*. "Who called?" (he called). "To whom was it sent?" (sent to him). | +| *fewer* / *less* | *Fewer* for countable nouns; *less* for uncountable. "Fewer employees, less revenue." | +| *comprise* / *compose* | The whole *comprises* its parts. The parts *compose* the whole. "The board comprises seven members." | +| *ensure* / *insure* | *Ensure* means to make certain; *insure* relates to insurance policies. | +| *principal* / *principle* | *Principal* is a leader or primary; *principle* is a fundamental rule. | + +--- + +## Prompts + +**Prompt 1 -- Grammar Audit:** +> Review the following business document for grammar errors, focusing on subject-verb agreement, pronoun case, dangling modifiers, and parallel construction. For each error found, quote the original sentence, explain the specific rule violated, and provide a corrected version. Document: [paste text] + +**Prompt 2 -- Usage Confusion Scan:** +> Examine this text for commonly confused words (affect/effect, that/which, who/whom, fewer/less, comprise/compose, ensure/insure, principal/principle). Flag every instance, explain whether it is used correctly, and suggest corrections where needed. Text: [paste text] + +**Prompt 3 -- Punctuation Overhaul:** +> Audit this document for punctuation errors, paying special attention to comma splices, missing serial commas, incorrect apostrophe usage, and hyphenation of compound adjectives. Provide a corrected version with annotations explaining each change. Document: [paste text] + +**Prompt 4 -- Before/After Credibility Rewrite:** +> Here is a paragraph from an investor update I am preparing: [paste text]. Rewrite it to eliminate all grammar and punctuation errors while preserving the original meaning and tone. Then list every change made and the rule that motivated it. + +--- + +## Use Cases + +**Validation-Stage Founder Preparing a Pitch Deck** +A solo founder preparing a twelve-slide seed pitch discovers, after a grammar audit, that three slides contain subject-verb disagreements and one uses "it's" as a possessive. The investor reading the deck is a former English major who served as managing editor of the Stanford Law Review. These errors would have been the first -- and possibly the last -- things noticed. The grammar check costs fifteen minutes. The unchecked alternative could have cost the meeting. + +**Growth-Stage Company Publishing an Annual Report** +A 200-person company preparing its first public annual report submits the draft for a grammar and mechanics review. The audit catches 23 punctuation inconsistencies (mixed usage of serial commas), 7 that/which confusions, and a dangling modifier in the CEO's letter that accidentally attributes declining margins to the board of directors rather than to market conditions. The corrected version avoids an embarrassment that, once printed and distributed, could not be recalled. + +**Early-Traction Startup Drafting Client Contracts** +A B2B SaaS startup discovers its standard client proposal template contains "less" where "fewer" is required, inconsistent hyphenation of compound modifiers, and three instances of comma splices. Since this template has been sent to forty prospects over six months, the cumulative credibility impact is sobering. Correcting the template takes twenty minutes and elevates the professionalism of every future client interaction. + +--- + +## Anti-Patterns + +1. **Hypercorrection.** Overcorrecting grammar to the point of producing stilted, unnatural prose. Writing "to whom should I direct this inquiry?" in a Slack message to a colleague is technically correct and socially absurd. The goal is correctness appropriate to context, not grammatical maximalism. + +2. **Grammar Policing in Feedback.** Using grammar knowledge to publicly correct colleagues' writing rather than privately and constructively improving shared documents. Grammar competence used as a status signal breeds resentment, not better writing. + +3. **Ignoring Grammar in Internal Documents.** Treating grammar as relevant only for external communications. Internal memos, Slack messages, and team updates also shape how people perceive competence. Sloppy internal writing creates sloppy habits that leak into external documents at the worst moments. + +4. **Relying Solely on Spell-Checkers.** Spell-check tools catch "teh" but miss "their" when you meant "there." Grammar-checking software has improved but still mishandles subject-verb agreement in complex sentences, that/which distinctions, and subtle comma splices. Automated tools supplement human review; they do not replace it. + +5. **Perfectionism as Procrastination.** Endless grammar revision as a means of avoiding the more difficult work of actually saying something. A grammatically perfect document that says nothing of substance is a polished void. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal credibility in initial pitches | At the idea stage, the founder *is* the product. Grammar errors in early pitch materials disproportionately damage credibility because there is no product traction to compensate. | +| Validation | Pitch decks and investor communications | Documents begin circulating to external audiences -- investors, advisors, potential partners. Every document is evaluated as evidence of operational competence. | +| Early Traction | Client-facing proposals and contracts | Proposals, contracts, and onboarding materials now represent the company to paying customers. Grammar errors signal carelessness in a context where trust is still fragile. | +| Growth | Standardising templates and style guides | With multiple people writing on behalf of the company, inconsistency becomes the primary risk. A company-wide style guide and grammar checklist become organisational infrastructure. | +| Scale | Brand consistency across all communications | At scale, grammar and mechanics become part of brand management. Training programmes, editorial review processes, and style enforcement tools ensure consistency across hundreds of authors. | + +--- + +## Output Template + +```markdown +# Grammar and Mechanics Audit: [Document Name] + +## Summary +- **Total errors found:** [number] +- **Critical errors (meaning-altering):** [number] +- **Credibility errors (noticeable but not meaning-altering):** [number] +- **Style inconsistencies:** [number] + +## Error Log + +| # | Original Text | Error Type | Rule Violated | Corrected Text | +|---|--------------|------------|---------------|----------------| +| 1 | [quote] | [grammar/punctuation/usage] | [specific rule] | [corrected version] | +| 2 | [quote] | [grammar/punctuation/usage] | [specific rule] | [corrected version] | + +## Recurring Patterns +- [Pattern 1: e.g., "Consistent misuse of that/which throughout"] +- [Pattern 2: e.g., "Serial comma used inconsistently"] + +## Recommendations +1. [Specific recommendation for preventing recurrence] +2. [Style guide addition suggested] +``` + +--- + +## Related Skills + +- **[Tone and Engagement](tone-and-engagement.md)** -- Correct grammar is necessary but not sufficient; tone determines whether technically correct prose actually connects with readers. +- **[Writing Effective Emails](writing-effective-emails.md)** -- Email is the most frequent venue for grammar errors because speed and informality lower the writer's guard. +- **[Writing Memos and Reports](writing-memos-and-reports.md)** -- Formal documents demand the highest standard of grammatical precision because they persist in the organisational record. +- **[Writing Performance Reviews](writing-performance-reviews.md)** -- Performance evaluations carry legal implications, making grammatical precision not merely a matter of style but of institutional risk. +- **[Revising and Editing](revising-and-editing.md)** -- The editing pass is where grammar errors are caught systematically rather than relying on instinct during drafting. +- **[Plain Language and Flow](plain-language-and-flow.md)** -- Many grammar errors stem from overly complex sentence constructions; plain language reduces the surface area for mechanical mistakes. diff --git a/plugins/foreman/content/skills/writing/plain-language-and-flow.md b/plugins/foreman/content/skills/writing/plain-language-and-flow.md new file mode 100644 index 0000000..0eac107 --- /dev/null +++ b/plugins/foreman/content/skills/writing/plain-language-and-flow.md @@ -0,0 +1,244 @@ +--- +name: "plain-language-and-flow" +description: "Teaches how to eliminate corporate jargon (bizspeak), use chronological ordering for factual accounts, and create smooth document flow through transitional words, signposting, and paragraph continuity. Features a bizspeak blacklist, before/after translations of corporate prose, and a taxonomy of transitional phrases. Use when writing sounds too corporate, when documents lack narrative flow, when readers report confusion about the sequence of events, or when establishing plain-language standards for an organisation." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - plain-language + - jargon + - transitions + - flow + - chronology + - readability + - business-writing +related_skills: + - clarity-and-concision + - revising-and-editing + - writing-with-purpose + - business-writing-for-leaders +author: "Fatih Guner" +--- + +# Plain Language and Flow + +Consider this paragraph from an actual corporate communication: "It's mission-critical to be plain-spoken, whether you're trying to be best-of-breed at outside-the-box thinking or simply incentivizing colleagues to achieve a paradigm shift in core-performance value-adds. Leading-edge leveraging of your plain-English skill set will ensure that your actionable items synergize future-proof assets with your global-knowledge repository." + +That passage says absolutely nothing. Strip away the jargon and what remains is a void -- no idea, no argument, no information. The words exist to *sound* like communication while avoiding the labour of actual thought. This is bizspeak: the corporate dialect that substitutes cliches for meaning, boilerplate for analysis, and verbal padding for substance. It is the lingua franca of organisations that have confused formality with competence. + +The antidote is not simplification. It is *translation* -- converting corporate noise into human language, imposing chronological order on jumbled narratives, and using transitional phrases to guide readers through the argument. Plain language is not dumbed-down language. It is language that has been thought through. + +--- + +## The Framework + +### Part 1: The Bizspeak Autopsy + +Corporate jargon persists for three reasons. Some writers use it to signal belonging -- to sound "in the know." Others have been taught that good writing is formal writing, so they stiffen when they pick up a keyboard. Still others use jargon deliberately to obscure what they are actually doing, or to disguise the fact that they are not sure what they are doing. + +Whatever the motivation, the effect on the reader is consistent: bizspeak suggests that the writer is on autopilot, thoughtlessly deploying boilerplate rather than engaging with the material. + +**The Bizspeak Translation Table:** + +| NOT THIS | BUT THIS | +|----------|----------| +| at your earliest convenience | as soon as you can | +| in light of the fact that | because | +| we are in receipt of | we've received | +| as per our telephone conversation on today's date | as we discussed this morning | +| Pursuant to your instructions, I met with Roger Smith today regarding the above-mentioned. | As you asked, I met with Roger Smith today. | +| Please be advised that the deadline for the abovementioned competition is Monday, April 2, 2012. | The deadline is April 2, 2012. | +| Thank you for your courtesy and cooperation regarding this matter. | Thank you. | + +Each translation removes verbal scaffolding while preserving -- and often improving -- the meaning. The plain versions take less time to write, less time to read, and less time to act on. + +**The Bizspeak Blacklist (a selection):** + +Actionable (apart from legal contexts), as per, bandwidth (outside electronics), bring our A game, core competency, drill down, going forward, hit the ground running, impact (as verb), incentivize, leverage (as verb), mission-critical, net-net, on the same page, operationalize, paradigm shift, push the envelope, repurpose, rightsized, scalable, seamless integration, synergize, think outside the box, utilize, value-added, win-win. + +These terms have become voguish through overuse. Each one once carried meaning; repetition has drained it away. When a writer reaches for "synergize," the question to ask is: what specifically are these elements doing together, and can that action be described in plain English? + +### The Buffett Translation + +Warren Buffett rewrote a passage from a financial-services prospectus to demonstrate the transformation. The original: 136 words, all passive voice, average sentence length 27.2 words, Flesch Reading Ease score 8.2 (virtually unreadable). Buffett's revision: 74 words, no passive voice, average sentence length 14.8 words, Flesch Reading Ease score 60.1. + +The revision did not lose information. It gained clarity. Increasing readability is not "dumbing it down" -- it is cleaning it up. + +### The Readability Science + +Buffett's instinct is backed by a century of measurement. Readability -- the quantifiable ease or difficulty of reading a text -- was first formalised by the United States military in 1917, when the country needed to assess whether soldiers could read well enough to perform their duties. The metrics have grown more sophisticated, but the core insight remains: shorter words, more common words, and shorter sentences produce text that more people read, understand, and act upon. + +*Writing for Busy Readers* marshals the evidence. Readability scores are typically expressed as either a numerical index or the school grade level a reader would need to have completed to comprehend the text. The *New York Times* requires an eleventh-grade reading level. Most nursery rhymes sit at fourth grade. Around half of American adults read at an eighth-grade level or below, and roughly 20% read English as a second language. Writing above eighth-grade level does not signal sophistication -- it signals exclusion. + +**Cognitive load is the mechanism.** Humans evolved to speak and listen long before developing the capacity to read. Spoken language uses short, incomplete sentences; our brains process these structures with minimal effort. Written prose that departs from this pattern -- long sentences, subordinate clauses, unfamiliar vocabulary -- taxes working memory. Eye-tracking studies show that readers pause at end-of-sentence periods to integrate meaning. Longer sentences force readers to hold more information in memory before that integration can occur, increasing the probability of distraction, re-reading, or abandonment. + +**The data on sentence length is unambiguous.** Average sentence length in published novels has dropped from 27 words per sentence in 1800 to 10 words per sentence in 2000. Presidential inaugural addresses show the same trajectory: George Washington's opening five sentences in 1789 averaged 64 words each; Joe Biden's in 2021 averaged 7. The trend reflects not declining intelligence but increasing respect for the reader's cognitive constraints. + +**Familiar words outperform sophisticated vocabulary.** When two words are synonyms, the shorter and more common one is almost always more readable. Google's Ngram Viewer confirms that "next" is used more frequently than "subsequent," "get" more than "acquire," "show" more than "demonstrate." Research published under the title "Consequences of Erudite Vernacular Utilized Irrespective of Necessity" found that college students rated writers who used complex language as *less* intelligent than those who used simpler language. The paper won an Ig Nobel Prize -- and its finding has held up. In a separate study, corporations with less readable ethics codes were rated by readers as less moral and less trustworthy. + +The implication for business writers is straightforward: readability is not a matter of preference but of reach. A document written at a college reading level excludes a measurable portion of its audience. The same document, revised to eighth-grade level using shorter sentences and more common words, excludes almost no one -- and is read more quickly even by those fully capable of parsing the original. + +### Part 2: Chronological Ordering + +Stories are inherently chronological. One thing happens, then another, then another. This structure works not only in fiction but in any factual business account -- project updates, status reports, incident descriptions, performance evaluations. + +Writers who skip chronological ordering produce stream-of-consciousness messages that confuse readers. The facts are present, but the reader cannot reconstruct the sequence. The fix: before drafting any factual account, create a chronology of relevant events. + +**Before chronological ordering:** +> "It was hard making headway with Jim Martinez, but finally we're looking at a demonstration of what our software can do by mid-May, as I established in my first telephone conference with Jim last Monday at 9:00 a.m. He was out Wednesday and Thursday, but on Friday he told me that we'd need a sample app. But prior to that, Magnabilify requires an NDA. Tuesday's meeting should clarify things." + +**After chronological ordering:** +> "Last week you asked me to approach Magnabilify Corporation to see whether they might have any interest in our customising some security applications for their computer systems. I finally got through to Jim Martinez, corporate vice president in charge of software, and we have planned a face-to-face meeting at his office next Tuesday. The next steps will be to enter into a nondisclosure agreement, to develop a sample application in less than two weeks, and to schedule a demonstration shortly after." + +The first version forces the reader to untangle the timeline. The second version tells a story that any reader can follow on the first pass. + +### Part 3: Continuity and Transitions + +Smooth writing consists of a sequence of well-joined sentences and paragraphs -- not a mere collection of them. The connections between ideas, executed through transitional words and phrases, are the infrastructure of readable prose. When they work, readers do not even notice them. When they are absent, readers stumble. + +**The Taxonomy of Transitions:** + +| Function | Transitional Words | +|----------|-------------------| +| **Time sequence** | then, at that point, afterward, as soon as, before, after, first, initially, meanwhile, later, next, now, finally | +| **Add a point** | and, or, further, also, in fact, moreover, not only... but also | +| **Underscore a point** | above all, after all, and so, chiefly, equally important, more so, indeed | +| **Concede a point** | although, and yet, admittedly, at the same time, certainly, even though, granted, no doubt, still, whereas, yet, while | +| **Return to a point** | even so, nevertheless, nonetheless, still | +| **Give an example** | for example, for instance, in particular | +| **Provide a reason** | because, hence, thus, for, it follows, since, so, then, therefore | +| **Set up a contrast** | but, yet, and yet, conversely, despite, by contrast, instead, on the other hand, still, while | +| **Set up a conclusion** | so, as a result, finally, in conclusion, in short, in sum, therefore, thus, to sum up | + +Transitions are not decorative. They are navigational. Each one tells the reader the relationship between the current idea and the one that preceded it -- whether the writer is adding, contrasting, conceding, concluding, or illustrating. + +### Signposting with Subheads + +No matter how smooth the transitions between sentences and paragraphs, time-pressed readers will zone out when confronted with a solid wall of text. Subheadings serve as signposts -- they break the document into navigable sections and allow readers to find the information they need. + +Effective subheads are: +- **Informative, not generic.** "Background" tells the reader nothing. "Why Our Current Process Takes Four Weeks" tells them exactly what they will learn. +- **Consistent in syntax.** If one subhead is a directive ("Use LinkedIn to Get Feedback"), all subheads should be directives. Parallel structure reinforces logical and rhetorical cohesion. +- **Scannable.** A reader who reads only the subheads should get the gist of the entire document. + +--- + +## Prompts + +**Prompt 1 -- Bizspeak Translation:** +> Here is a business document: [paste text]. Identify every instance of corporate jargon, bizspeak, and boilerplate phrasing. For each, provide a plain-English translation. Then rewrite the entire document in plain language, preserving all substantive content. Show a side-by-side comparison of the original and revised versions with word counts. + +**Prompt 2 -- Chronological Reordering:** +> Here is a factual account I need to communicate: [paste text or describe events]. The events are currently described out of order. Create a chronology of relevant events (a simple table with dates/timeframes and what happened). Then rewrite the account in chronological order so that a reader with no prior context can follow the narrative on the first read. + +**Prompt 3 -- Transition Audit:** +> Here is a document: [paste text]. Analyse the transitions between paragraphs. For each paragraph boundary, identify: (1) whether a transition exists, (2) what function it serves (adding, contrasting, concluding, etc.), (3) whether it is effective. Where transitions are missing or weak, suggest specific transitional words or phrases that would improve flow. Then provide the revised document with improved transitions. + +**Prompt 4 -- Subhead Architecture:** +> Here is a document of [X] words: [paste text]. It currently has [no subheads / weak subheads]. Design a subhead architecture that: (1) breaks the document into logical sections, (2) uses informative rather than generic labels, (3) maintains parallel syntax across all subheads, (4) allows a reader to grasp the document's argument by reading only the subheads. Provide the revised document with subheads inserted. + +--- + +## Use Cases + +**Validation-Stage Startup Translating a Technical White Paper for Investors** + +A deep-tech startup's white paper is dense with domain jargon that resonates with engineers but alienates investors. The original opening: "Our platform operationalizes a novel approach to leveraging graph-based neural architectures for scalable, mission-critical anomaly detection in enterprise-grade distributed systems." After the bizspeak translation: "Our software detects problems in large computer networks before they cause outages. It uses a type of artificial intelligence called graph neural networks -- the same technology behind social media recommendation engines, adapted for IT infrastructure monitoring." The second version communicates the same technology to a broader audience. The investor can now decide whether to keep reading. + +**Growth-Stage Company Fixing Disorganised Status Reports** + +A project manager's weekly status reports read like stream-of-consciousness: events from different weeks are jumbled, outcomes are mentioned before their causes, and the reader cannot tell what happened this week versus last month. Applying the chronological ordering framework: the PM creates a simple timeline before drafting each report -- last week's events, this week's events, next week's planned actions. The report structure becomes: "Where we were / What happened / Where we're going." Reader comprehension (measured by the number of follow-up questions from the VP) drops from an average of five per report to one. + +**Scale-Stage Company Establishing a Plain-Language Style Guide** + +A 400-person financial services firm discovers that customer communications score below 30 on the Flesch Reading Ease scale -- roughly equivalent to the *Harvard Law Review*, and thoroughly inappropriate for retail clients. The firm creates a plain-language standard: all customer-facing documents must score above 50 (roughly *Time* magazine level), all subheads must be informative rather than generic, and the bizspeak blacklist is circulated to every department. Within six months, customer complaint calls related to "confusing correspondence" drop by 35%. + +--- + +## Anti-Patterns + +1. **Replacing Jargon with Different Jargon.** Translating "synergize core competencies" into "align strategic capabilities" is not plain language -- it is a lateral move within the same dialect. Plain language means describing what is actually happening in words a non-specialist would use. + +2. **Eliminating All Technical Terms.** Plain language does not mean banning technical vocabulary. When writing for specialists, precise technical terms are more efficient than lengthy plain-language circumlocutions. The test is audience: will the reader know this term? If yes, use it. If no, define it or replace it. + +3. **Over-Transitioning.** Cramming a transitional word into every sentence makes prose feel mechanical and patronising. The best transitions are almost subliminal -- readers follow the logic without noticing the connective tissue. Use transitions where the relationship between ideas might be ambiguous; omit them where the connection is self-evident. + +4. **Using Subheads as Decoration.** Subheads that do not accurately describe the content below them are worse than no subheads at all. "Miscellaneous" is not a subhead -- it is an admission that the writer could not be bothered to organise the section. + +5. **Chronological Ordering When It Does Not Apply.** Not all business documents benefit from chronological structure. Recommendations, analyses, and persuasive arguments are often better organised by importance or logical dependency. Chronology serves factual accounts -- status reports, incident descriptions, project updates. Misapplying it to analytical documents produces a confusing "and then... and then..." narrative. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Jargon-free pitching | Early-stage founders often mimic the jargon of their target industry to seem credible. The opposite is more effective: plain language signals clarity of thought, which investors value more than vocabulary. | +| Validation | Evidence narration | Customer discovery stories, pilot results, and market validation are factual accounts that benefit from chronological ordering. Plain language ensures that non-technical stakeholders can evaluate the evidence. | +| Early Traction | Scaling communication clarity | As the team grows, internal communications must be accessible to new hires who lack the company's institutional jargon. Plain language accelerates onboarding. | +| Growth | Cross-functional readability | Marketing writes for customers, engineering writes for product, finance writes for investors -- and sometimes they must read each other's documents. Plain language is the common dialect that makes cross-functional communication possible. | +| Scale | Institutional plain-language standards | The bizspeak blacklist becomes an organisational style guide. Readability scores become acceptance criteria for external communications. New employees are trained on plain-language principles during onboarding. | + +--- + +## Output Template + +```markdown +# Plain Language and Flow Audit: [Document Title] + +## Bizspeak Inventory +| Jargon Found | Location | Plain Translation | +|-------------|----------|-------------------| +| [term/phrase] | [paragraph N] | [plain equivalent] | +| [term/phrase] | [paragraph N] | [plain equivalent] | + +## Readability Metrics +- **Flesch Reading Ease (original):** [X] +- **Flesch Reading Ease (revised):** [Y] +- **Average sentence length (original):** [X words] +- **Average sentence length (revised):** [Y words] +- **Passive voice percentage:** [X]% → [Y]% + +## Chronological Assessment +- **Document contains factual account?** [Yes/No] +- **Events presented in chronological order?** [Yes/No/Partially] +- **Chronology of relevant events:** + +| When | What Happened | +|------|---------------| +| [Date/period] | [Event] | +| [Date/period] | [Event] | + +## Transition Audit +| Paragraph Boundary | Transition Present? | Function | Effective? | Suggested Improvement | +|-------------------|--------------------|-----------|-----------|-----------------------| +| P1 → P2 | [Yes/No] | [Type] | [Yes/No] | [Suggestion] | +| P2 → P3 | [Yes/No] | [Type] | [Yes/No] | [Suggestion] | + +## Subhead Assessment +- **Current subheads informative?** [Yes/No] +- **Parallel syntax?** [Yes/No] +- **Scannable summary from subheads alone?** [Yes/No] +- **Recommended subhead architecture:** + 1. [Subhead 1] + 2. [Subhead 2] + 3. [Subhead 3] +``` + +--- + +## Related Skills + +- **[Clarity and Concision](clarity-and-concision.md)** -- Plain language eliminates jargon; concision eliminates waste. Together they produce prose that is both accessible and efficient. +- **[Revising and Editing](revising-and-editing.md)** -- The editing checklist's "Does one sentence glide into the next?" question operationalises the continuity principles taught here. +- **[Writing with Purpose](writing-with-purpose.md)** -- Purpose determines audience, and audience determines the appropriate level of plain language; writing for specialists allows more technical vocabulary while diverse audiences demand simpler expression. +- **[Reader Psychology](reader-psychology.md)** -- The cognitive science of how readers process text explains why plain language reduces cognitive load and increases comprehension at a neurological level. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Leaders who write in plain language set the standard; those who write in bizspeak give implicit permission for everyone else to do the same. +- **[Tone and Engagement](tone-and-engagement.md)** -- Plain language creates the foundation; tone determines whether that accessible prose also engages the reader emotionally. diff --git a/plugins/foreman/content/skills/writing/reader-psychology.md b/plugins/foreman/content/skills/writing/reader-psychology.md new file mode 100644 index 0000000..e026067 --- /dev/null +++ b/plugins/foreman/content/skills/writing/reader-psychology.md @@ -0,0 +1,202 @@ +--- +name: "reader-psychology" +description: "Teaches the cognitive science behind how busy readers actually process written communications. Covers working memory limits, the F-pattern scanning behaviour, selective attention, and the four-stage triage process readers apply to every message. Use when diagnosing why communications fail to land, designing high-stakes messages for distracted audiences, auditing existing copy for cognitive overload, or training a team to write with the reader's brain in mind." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-science + - attention + - reading-behaviour + - working-memory + - F-pattern + - busy-readers + - communication +related_skills: + - writing-for-navigation + - writing-for-response + - writing-effective-emails + - clarity-and-concision + - tone-and-engagement +author: "Fatih Guner" +--- + +# Reader Psychology + +F-PATTERN. Eye-tracking research reveals that readers do not read -- they scan in an F shape, spending most attention on the first two lines and the left margin. Everything else is a gamble. Psychologist George Miller's landmark study established that human working memory holds approximately seven items, plus or minus two, at any given moment. Between that hard cognitive ceiling and the 121 emails the average manager receives daily, the arithmetic is unforgiving: every sentence a writer produces competes against a reader's finite neural budget. Understanding that budget -- its size, its depletion rate, its failure modes -- is the prerequisite for writing that actually gets through. + +--- + +## The Framework + +### The Busy Brain: Three Constraints + +The limited capacity of the human attention system produces three consequences that shape every act of reading. + +**Constraint 1: We Cannot Process Everything in Front of Us** + +At any moment, the brain confronts more information than it can absorb. Its attention system responds by acting as a filter -- selecting what to notice and suppressing the rest. A 1999 Harvard study demonstrated this vividly: when participants were asked to count basketball passes in a video, nearly half failed to notice a person in a gorilla costume strolling through the scene. The brain's suppression of irrelevant stimuli is so aggressive that even conspicuous objects vanish when they fall outside the current focus. For writers, the implication is stark: information that is present in a message but not actively foregrounded may as well not exist. + +**Constraint 2: Focus Exhausts Quickly** + +Directing attention is effortful, and the resource depletes faster than most people assume. In a study by psychologist Brandon Schmeichel, participants who spent six minutes resisting the urge to look at flashing words on screen subsequently scored 20% lower on a graduate-level reading comprehension test. Six minutes of attentional control was enough to measurably impair later cognitive performance. Physical fatigue compounds the effect -- athletes under physical exhaustion show impaired attention and decision-making, and information scientist Gloria Mark found that workers need an average of 23 minutes to fully return to a task after a single interruption. One study estimated that minds wander a full third of the time while people attempt to read, with the rate climbing further when the material is complicated. + +**Constraint 3: Multitasking Fails** + +Strictly speaking, the brain cannot think about two tasks simultaneously. What people call "multitasking" is rapid task-switching, and it is cognitively expensive. A study at Butler University and Eli Lilly found that pharmacists asked to answer questions while filling prescriptions took longer and made substantially more errors. US government statistics attribute thousands of road deaths each year to texting while driving -- yet by some estimates, 22% of drivers report doing it daily. The Latin writer Publilius Syrus captured the principle in the first century BCE: "To do two things at once is to do neither." Modern survey data confirms that 63% of professionals report regularly working on two or three tasks simultaneously -- and modern research confirms they are worse at all of them when they do. + +The Stroop effect offers a vivid demonstration. When participants are asked to name the formatting applied to a word (e.g., say "bold" when they see the word "italicise" printed in bold), performance collapses. The brain cannot suppress the automatic reading of the word while simultaneously identifying the formatting -- two trivially simple tasks that become agonising in combination. The relevance for writers: any message that requires the reader to hold one piece of information in mind while processing a second is exploiting a cognitive capacity that barely exists. + +### How Readers Triage: The Four-Stage Filter + +Every time a reader encounters a written communication -- even a text message or a Slack notification -- they pass through four rapid, often unconscious decisions. + +| Stage | Question the Reader Asks | What Determines the Answer | +|-------|--------------------------|---------------------------| +| 1. Whether to engage | "Is this worth my time?" | Sender recognition, subject line, apparent length. In surveys, working professionals estimate they delete roughly half their emails without reading them. | +| 2. When to engage | "Now or later?" | Perceived effort. In one survey, 99% of professionals said they would respond first to the message that appeared easier. People prefer easy tasks now and defer hard tasks to "later" -- and "later" frequently means "never." | +| 3. How to engage | "Read closely, skim, or scan?" | Expected utility per second. Nearly 40% of emails and 20% of text messages are skimmed. Readers maximise information extraction while minimising time spent. | +| 4. Whether to respond | "Is the requested action worth the cost?" | Clarity of the request, ease of compliance, and perceived importance. Even willing readers fail to act when the steps are unclear or burdensome. | + +The preference for easy, short messages is not laziness -- it is a hardwired bias toward present-moment gratification. MRI research shows that limbic reward regions activate when the brain considers desirable outcomes available now, but remain largely dormant for outcomes deferred to the future. A classic experiment found that most people prefer $100 today over $101 in a week, despite the latter representing a 68% annualised return. A survey of the book's own participants revealed that respondents would rather sit in traffic for 31 minutes a week from now than 30 minutes right now -- paying an extra minute of misery for the privilege of deferring. The same bias applies to reading: if a message looks like it will be an unpleasant slog, the reader will push it off until "later," which, for practical purposes, means never. + +This temporal myopia shapes not just whether people read but what they read first. When presented with a mix of easy and hard tasks, people consistently tackle the easy ones first -- even when offered financial incentives to prioritise the hard ones. The implication for writers: your message is not competing solely against other messages. It is competing against every easier, more pleasant alternative in the reader's immediate environment. + +### How Readers Actually Read: Skimming, Scanning, and the F-Pattern + +Eye-tracking studies reveal a consistent scanning pattern across web pages, emails, and documents. Readers fixate most heavily on the first two lines, then scan down the left margin, occasionally darting rightward -- forming the shape of the letter F. Anchor points that attract fixation include headings, first sentences of paragraphs, visually contrasting elements (bold text, bullet points), and images. Text that falls outside these anchor points is routinely skipped. + +Psychologists Keith Rayner and Monica Castelhano mapped the difference between close reading and skimming: during close reading, the eyes move word by word in sequence; during skimming, fixations drop sharply and the eyes jump across entire lines. Since busy readers default to skimming, any information not positioned at a natural anchor point is statistically unlikely to be absorbed. + +Scanning is the companion strategy to skimming. Where skimming moves linearly but fast, scanning involves jumping between sections of a text, guided by selective attention and rules of thumb about where valuable information is most likely to reside. Readers often expect the first sentence of a paragraph to orient them to the rest of it. They spend more time on those opening sentences and use them to decide whether to read, skim, or skip what follows. Headings serve the same function at a higher structural level: readers use them as a table of contents for the document, zooming into sections that seem relevant and bypassing the rest entirely. + +The combined effect is sobering. In surveys conducted by the researchers, participants reported skimming nearly 40% of their emails and 20% of their text messages. These are not long-form documents -- they are the shortest, most urgent forms of written communication available. If readers skim a two-paragraph email, the probability that they will closely read a five-page memo is negligible without deliberate navigational architecture. + +A Carnegie Mellon study found that being interrupted by a phone call while taking a reading test decreased performance by 20%. The modern workplace is essentially a continuous interruption environment. The effective writer designs for this reality rather than against it -- placing critical information at the anchor points where even a scanning, distracted, cognitively depleted reader will land. + +### The Distracted Driver Analogy + +The book's authors draw a useful parallel between busy reading and distracted driving. Most adults are experienced drivers and experienced phone-talkers -- both tasks are individually routine. Yet psychologists have suggested that talking on the phone while driving has as bad an effect on performance as being legally drunk. The explanation returns to the attention system: even two well-practised tasks compete for the same finite cognitive bandwidth when performed simultaneously. Reading a work email while mentally preparing for a meeting, while a Slack notification pulses in the peripheral vision, creates an analogous collision. The reader is not stupid or careless. The reader is a cognitive system operating at capacity, and the writer who fails to account for that capacity is the one whose message gets lost. + +### The Writer's Blind Spot + +Writers systematically overestimate how much of their message readers will consume. This is a variant of the "curse of knowledge" -- having written every word, the writer assumes the reader will encounter every word. The data says otherwise. Readers skip paragraphs, jump backward to find missed details, and abandon messages mid-sentence when the expected value of the next second of reading drops below the value of doing something else. + +A Pew Research Center survey found that 60% of US adults -- and 74% of parents -- report feeling too busy to enjoy life at least some of the time. The writers' own surveys corroborate the figure: 60% of respondents said they often do not have enough time to get everything done in a typical month. Against that backdrop of chronic time scarcity, the writer's job is not to produce comprehensive text but to survive a brutal triage process. The writing that gets through is the writing that respects the reader's constraints -- not the writing that tests them. + +--- + +## Prompts + +**Prompt 1 -- Cognitive Load Audit:** +> Analyse the following message as though you are a busy reader with seven-plus-or-minus-two working memory slots and a strong bias toward skimming. Identify: (a) where the reader's F-pattern scan would likely fixate, (b) what information would be missed during a five-second skim, and (c) which elements create unnecessary cognitive load. Then suggest specific revisions. Message: [paste text] + +**Prompt 2 -- Triage Simulation:** +> Imagine you are a [describe recipient: e.g., Series A investor reviewing 40 pitch emails per day]. Walk through the four-stage reader triage for the following message: (1) Would you engage? (2) Would you engage now or later? (3) Would you skim or read closely? (4) Would you respond? At each stage, explain what would tip the decision, and flag where the message fails. Message: [paste text] + +**Prompt 3 -- Attention Budget Calculator:** +> I need to communicate [describe content] to [describe audience]. Estimate the reader's likely attention budget in seconds, based on the medium ([email/Slack/memo]), the sender-recipient relationship, and the perceived urgency. Then help me restructure the message so that the highest-priority information lands within the first 30% of that budget. + +**Prompt 4 -- Distracted Reader Stress Test:** +> Rewrite the following message so it survives the "distracted driver" test: a reader who is simultaneously managing three other tasks, has been interrupted twice in the last ten minutes, and will give this message no more than fifteen seconds. Preserve all essential content but restructure for maximum absorption under minimal attention. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Writing a Cold Investor Email** + +A fintech founder sends a two-paragraph email to a target angel investor. The first paragraph opens with three sentences of personal background. The second contains the ask -- a 20-minute call to discuss a payments API. Eye-tracking logic predicts the investor's F-pattern scan will fixate on the first line (personal background, no hook), glance left-margin down the second paragraph, and likely disengage before reaching the ask buried in the final sentence. The investor, receiving 40 such emails daily, applies the Stage 1 triage almost instantaneously: sender unknown, subject line generic ("Quick intro"), opening sentence unremarkable. The email is closed within three seconds. + +Restructuring the email to lead with a single data point ("Card-present fraud costs US merchants $8.6B annually -- we reduce it by 40%") followed immediately by the ask ("Would you have 20 minutes this week?") places both elements squarely within the F-pattern's high-attention zone. The data point serves as visual contrast -- a number amid text -- which the selective attention system is primed to notice. The ask, arriving in the second sentence, lands before Stage 3 triage (how closely to read) can default to skimming. + +**Growth-Stage Company Redesigning Internal Announcements** + +A 200-person SaaS company notices that its weekly all-hands email, averaging 800 words, generates fewer than 15% click-throughs on embedded action items. An internal audit applies the four-stage triage model and discovers the problem at Stage 3: readers skim the dense paragraphs, and action items are buried in the middle of blocks of text with no visual differentiation. The company redesigns the email with a three-line summary at the top, bold headings for each section, and action items isolated in a single bulleted block at the end. Click-through rates rise to 38% within one month. The words did not change materially; their cognitive accessibility did. + +**Validation-Stage Startup Crafting a Product Onboarding Sequence** + +A health-tech startup discovers that 60% of new users abandon its onboarding flow at step three of five. Applying the working-memory constraint, the team realises that step three requires users to hold four distinct pieces of information simultaneously (account type, billing preference, notification settings, and data-sharing consent) -- exceeding Miller's 7 plus-or-minus 2 threshold when combined with the ambient cognitive load of navigating a new interface. Splitting step three into two screens, each requiring only two decisions, reduces abandonment by 35%. The lesson extends beyond product design: any written communication that asks the reader to hold multiple unrelated concepts simultaneously -- a board update that mixes financial results, hiring plans, and legal matters in a single paragraph -- is making the same architectural mistake. + +**Scale-Stage Company Testing Subject Lines at Volume** + +An e-commerce platform with 2 million email subscribers runs an A/B test on its weekly promotional newsletter. Version A uses a consistent subject line ("This Week's Deals"). Version B varies the subject line each week with specifics ("40% Off Kitchen Essentials -- Ends Thursday"). Open rates for Version B average 28% higher over a 12-week period. The F-pattern predicts this: the subject line is the first -- and often only -- element the reader's attention system evaluates during Stage 1 triage. A static subject line becomes background noise; a variable one forces the attention system to process it anew each time. + +--- + +## Anti-Patterns + +1. **The Completeness Fallacy.** Writing a message that contains every relevant detail, on the assumption that thoroughness equals effectiveness. The reader's attention budget does not expand to match the writer's ambition. A 1,200-word email that covers eight topics will, in practice, communicate fewer of them than a 300-word email that covers three -- because the latter will actually be read. + +2. **Burying the Lead in Paragraph Three.** Opening with context, pleasantries, or chronological backstory before stating the purpose. The F-pattern concentrates attention on the first two lines. Anything placed after an unremarkable opening is competing with the reader's impulse to move on, and the impulse usually wins. + +3. **Symmetric Emphasis.** Bolding, underlining, or highlighting five different items in a single message under the theory that all five are important. Research shows that formatting five sentences in a passage reduces the noticeability of any single formatted sentence compared to formatting just one. When everything is emphasised, nothing is. + +4. **Assuming the Reader Will Return.** Sending a dense message with the expectation that the reader will skim now and read closely later. The data on present-bias suggests otherwise: messages deferred to "later" are rarely revisited. If the reader does not absorb the key information on first contact, the probability of a second contact approaches zero. + +5. **Ignoring Medium-Specific Attention Norms.** Writing a 500-word Slack message or a three-sentence board memo. Each medium carries implicit expectations about length and density. Violating those expectations triggers an immediate cost-benefit recalculation in the reader's triage process -- usually unfavourably. Text messages are expected to be immediate and disposable. Emails are expected to be scannable within one screen. Memos are expected to carry structure. Matching the medium's norms is not a stylistic preference -- it is a prerequisite for surviving Stage 1 triage. + +6. **The Multitasking-Friendly Illusion.** Writing a message that requires the reader to cross-reference an attachment, a prior email, and an external link to fully understand the request. This design assumes the reader will perform three concurrent cognitive tasks. The Stroop effect, the gorilla experiment, and the pharmacist study all suggest otherwise. If the reader must assemble information from multiple sources, they will assemble none of it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cold outreach to strangers (investors, advisors, potential co-founders) | The reader has no prior relationship with the sender. Stage 1 triage ("Should I engage at all?") is the primary hurdle. Subject line and first sentence carry almost the entire burden of persuasion. | +| Validation | Investor updates, early customer communications, survey requests | Readers have some familiarity with the sender but limited patience. Stage 2 ("Now or later?") is the critical gate. Messages must signal low effort and high relevance to avoid being deferred indefinitely. | +| Early Traction | Client-facing emails, onboarding copy, support documentation | The reader base diversifies. Writers must account for varying attention budgets across personas -- a technical user may read closely, while an executive sponsor skims. Designing for the skimmer protects both audiences. | +| Growth | Internal communications at scale (all-hands, policy updates, process changes) | Message volume multiplies. Employees develop aggressive triage habits for internal email. Cognitive load audits of recurring communications (weekly updates, change notices) yield outsized returns. | +| Scale | Templated communications, automated sequences, brand-level messaging | Thousands or millions of readers, each with unique attention constraints. A/B testing of structural elements (subject lines, opening sentences, visual hierarchy) becomes a quantitative discipline grounded in the same cognitive science. | + +--- + +## Output Template + +```markdown +# Cognitive Load Audit: [Message / Communication Name] + +## Reader Profile +- **Audience:** [Who is the reader?] +- **Estimated attention budget:** [X seconds, based on medium and context] +- **Primary triage risk:** [Stage 1 / 2 / 3 / 4 -- where the message is most likely to fail] + +## F-Pattern Analysis +- **First-line content:** [What the reader sees first -- is it the right thing?] +- **Left-margin anchors:** [Headings, paragraph openers, bullet starts] +- **Dead zones:** [Content that falls outside fixation points] + +## Working Memory Load +- **Concurrent concepts required:** [Count of distinct ideas the reader must hold] +- **Exceeds 7 +/- 2 threshold?** [Yes / No] +- **Simplification options:** [How to reduce simultaneous cognitive demands] + +## Triage Survival Checklist +- [ ] Purpose is clear within the first two lines +- [ ] Key ask or takeaway survives a five-second skim +- [ ] No critical information is buried below the third paragraph +- [ ] Formatting highlights one (maximum two) focal points +- [ ] Message length matches the medium's attention norms +- [ ] A reader who stops at any point has still absorbed the most important content + +## Revised Message +[Restructured version of the communication, annotated with cognitive rationale] +``` + +--- + +## Related Skills + +- **[Writing for Navigation](writing-for-navigation.md)** -- Translates reader psychology into structural principles: BLUF placement, headings as signposts, and visual hierarchy that aligns with the F-pattern scan. +- **[Writing for Response](writing-for-response.md)** -- Addresses the fourth triage stage directly: how to make the requested action so frictionless that even a cognitively depleted reader follows through. +- **[Writing Effective Emails](writing-effective-emails.md)** -- Applies the six principles of email craft to the medium where triage behaviour is most ruthless: the inbox. +- **[Clarity and Concision](clarity-and-concision.md)** -- Provides the sentence-level techniques for reducing cognitive load per unit of text. +- **[Tone and Engagement](tone-and-engagement.md)** -- Governs the emotional register that influences Stage 1 and Stage 2 triage decisions: whether the reader engages and whether they engage now. +- **[Thinking, Fast and Slow](../frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process theory provides the cognitive science foundation for why readers default to System 1 scanning and how writers can design for both processing modes. diff --git a/plugins/foreman/content/skills/writing/revising-and-editing.md b/plugins/foreman/content/skills/writing/revising-and-editing.md new file mode 100644 index 0000000..ea0a589 --- /dev/null +++ b/plugins/foreman/content/skills/writing/revising-and-editing.md @@ -0,0 +1,198 @@ +--- +name: "revising-and-editing" +description: "Teaches the distinct disciplines of revising (rethinking content and structure) and editing (refining sentences and word choices), with a concrete three-draft evolution showing how a mediocre memo transforms into an excellent one. Covers revision checklists, editing checklists, and the peer feedback process. Use when polishing any business document, preparing final drafts for stakeholders, training teams on writing quality, or establishing editorial review processes." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - editing + - revision + - feedback + - quality + - drafting + - business-writing +related_skills: + - writing-process + - clarity-and-concision + - plain-language-and-flow + - business-writing-for-leaders +author: "Fatih Guner" +--- + +# Revising and Editing + +Watch a mediocre memo become an excellent one. The first draft reads: "In order to facilitate the customers' placement of orders, a new order-processing procedure has been designed. The process will require a customer to enter the product and/or service code into our order-entry system, which will then generate a quote for the job and return it to the customer for approval." By the third draft, it reads: "Our current work-order processing takes a lot of paperwork and phone calls, so it's hard for our customers to make changes to the work before it begins. The procedure is inefficient and subject to error. And it takes up to four weeks from quote to approval to work order. We have therefore designed a new four-step procedure that has two key benefits: (1) Customers can place orders through our website, and (2) we can start jobs faster." + +The difference is not cosmetic. The first draft tells the reader *what* is happening. The third draft tells them *why it matters*. Between those two versions lies the entire discipline of revision and editing -- two related but fundamentally different operations that most writers conflate, to their detriment. + +--- + +## The Framework + +### Revising vs. Editing: The Critical Distinction + +Revising is rethinking the floor plan. Editing is choosing the paint colours. Confuse the two, and a writer will spend an hour perfecting the grammar of a paragraph that should have been deleted entirely. + +**Revising** addresses the macro level: the argument, the structure, the completeness, the truthfulness, the diplomacy. It asks whether the right things have been said. + +**Editing** addresses the micro level: the sentences, the word choices, the phrasing, the rhythm. It asks whether the right things have been said *well*. + +Both require dedicated time. Neurotic perfectionism that delays important documents is as damaging as rash distribution of unvetted drafts. The solution is a structured process that allocates appropriate time to each operation. + +### The Revision Checklist + +During revision, the writer steps back from the prose and interrogates the document as a whole: + +1. **Have I been utterly truthful?** Does the document accurately represent the facts, or have I unconsciously shaded them to support a preferred conclusion? +2. **Have I said all that I need to say?** Are there gaps that leave the reader unable to act? Missing context? Unanswered questions that the reader will inevitably ask? +3. **Have I been appropriately diplomatic and fair?** Will the tone damage a relationship that should be preserved? Have I been fair to opposing viewpoints? +4. **Do I have three parts -- an opener, a middle, and a closer?** Is the structure apparent to the reader? +5. **In my opener, have I made my points quickly, clearly, and concretely?** Or have I buried the lead under a slow wind-up? +6. **Have I avoided a slow wind-up that unnecessarily postpones the message?** The first paragraph should deliver the core point, not prepare the reader for a core point that arrives later. +7. **In the middle, have I proved my points with specifics?** Evidence, data, examples -- not assertions. +8. **Is the structure immediately apparent?** Have I used informative headings? +9. **Is my closer consistent with the rest -- yet expressed freshly?** Have I avoided lame repetition? + +### The Editing Checklist + +Once the structure is sound, the editor's eye narrows to the sentence and word level: + +1. **Can I save some words here?** Every word must earn its place. +2. **Is there a better way of phrasing this idea?** Could a stronger verb replace a weak verb-plus-adverb combination? +3. **Is my meaning unmistakable?** Could any sentence be misinterpreted by a reader with a different context? +4. **Can I make it more interesting?** Varied sentence length? A concrete example instead of an abstraction? +5. **Is the expression relaxed but refined?** Natural language, not corporate stiffness -- but not sloppy either. +6. **Does one sentence glide into the next, without discontinuities?** Are the transitions smooth? + +### Three Drafts in Practice + +The evolution from first to third draft follows a recognisable pattern: + +**First Draft (Carpenter output):** The ideas are present but poorly ordered. Important context is missing. The opening buries the point. Passive constructions dominate. The reader is told what is happening but not why. + +**Second Draft (Post-Revision):** The structure has been rethought. The opening now states the problem and the solution. Missing information -- the who, what, when, why -- has been filled in. The document can now stand on its own. But the prose is still wordy, and some phrasing is stiff. + +**Third Draft (Post-Editing):** Sentences have been tightened. Passive voice has been replaced with active voice where appropriate. Wordiness has been cut. The steps of the process have been reformatted as bullet points for scannability. The document reads as though it was easy to write -- which is precisely the illusion that careful editing creates. + +### The Peer Feedback Process + +The writer's worst handicap is familiarity. Having lived with a document through multiple drafts, the writer can no longer see it with fresh eyes. Peer feedback solves this problem -- but only if structured properly. + +**Effective peer feedback requires:** + +- **Specific questions, not open invitations.** "What do you think?" produces vague responses. "Can you identify my three main points after one read-through?" produces actionable data. +- **Fresh eyes.** The reviewer should not have been involved in the drafting. Their confusion is diagnostic: wherever they stumble, other readers will stumble too. +- **Separation of content and expression.** Ask one reviewer to assess whether the argument is complete and logical. Ask another to assess whether the prose is clear and concise. Combining both tasks in one review dilutes attention. +- **Ego management.** Feedback is not personal. A suggestion to restructure paragraph three is not an attack on the writer's intelligence. Writers who cannot receive criticism without defensiveness should consider whether they are in the right profession. + +--- + +## Prompts + +**Prompt 1 -- Revision Audit:** +> Here is a draft of my [document type]: [paste draft]. Apply the full revision checklist: (1) Is it truthful and accurate? (2) Is anything missing that the reader needs? (3) Is the tone appropriately diplomatic? (4) Does the structure have a clear opener, middle, and closer? (5) Is the main point visible in the first paragraph? (6) Are points supported with specifics? (7) Is the structure apparent with informative headings? Provide a paragraph-by-paragraph revision assessment with specific recommendations. + +**Prompt 2 -- Editing Pass:** +> Here is a revised draft of my [document type]: [paste draft]. Now edit at the sentence level: (1) Cut unnecessary words -- show me a word-count comparison for each paragraph, (2) Replace weak verbs and passive constructions, (3) Ensure each sentence's meaning is unmistakable, (4) Smooth transitions between paragraphs, (5) Vary sentence length for rhythm. Show the edited version with tracked changes explained. + +**Prompt 3 -- Three-Draft Transformation:** +> Here is a rough first draft: [paste draft]. Transform it through three clear stages. Show me Draft 2 (revised for structure, completeness, and argument) with an explanation of what changed and why. Then show me Draft 3 (edited for prose quality, concision, and polish) with an explanation of each edit. I want to see the evolution, not just the final product. + +**Prompt 4 -- Peer Review Simulation:** +> Pretend you are a colleague reading my [document type] for the first time: [paste draft]. After one read-through, tell me: (1) What are the three main points? (2) What action am I supposed to take? (3) Where did you get confused or lose interest? (4) What questions remain unanswered? (5) What would you cut? Be direct -- I need a reader's honest reaction, not reassurance. + +--- + +## Use Cases + +**Validation-Stage Startup Polishing a Pitch Deck Narrative** + +A founder has drafted a 12-slide pitch deck with extensive speaker notes. The Madman and Carpenter phases are complete, but the narrative feels scattered. Applying the revision checklist: the opener (slide 1) describes the product instead of the problem -- revision moves the problem statement forward. Slides 4-6 present features without connecting them to the market need identified in slide 2 -- revision adds the "so what" connector. The closer asks for investment without specifying terms or use of funds -- revision adds a concrete ask. After structural revision, the editing pass tightens every speaker note from an average of 80 words to 40 words, replaces jargon with plain language, and ensures each slide's headline could stand alone as a summary. + +**Scale-Stage Company Establishing an Editorial Review Process** + +A 500-person company discovers that external communications vary wildly in quality. Customer emails from support read differently from product announcements, which read differently from investor updates. The company implements a structured revision and editing process: all customer-facing documents above 500 words go through a two-stage review. Stage 1 (revision): a designated editor checks structure, completeness, and tone alignment with brand guidelines. Stage 2 (editing): a copy editor checks prose quality, grammar, and consistency. The peer feedback process uses specific checklists rather than open-ended review requests. Writing quality becomes consistent across the organisation within one quarter. + +--- + +## Anti-Patterns + +1. **Editing Before Revising.** Polishing sentences in a paragraph that should be deleted or moved is wasted effort. Always assess the macro structure before descending to the micro level. + +2. **Declaring the First Draft Final.** The most costly anti-pattern in business writing. A first draft, by definition, captures what the writer wanted to say -- not necessarily what the reader needs to hear. Skipping revision means skipping the transition from writer-centred to reader-centred prose. + +3. **Revising in Perpetuity.** Some writers revise indefinitely, unable to declare a document "done." The antidote: define the number of revision rounds in advance. Two rounds of revision and two rounds of editing is sufficient for most business documents. + +4. **Soliciting Feedback from the Wrong People.** Asking a subject-matter expert to assess prose quality, or asking a copy editor to assess strategic content, produces useless feedback. Match the reviewer to the review task. + +5. **Taking Peer Feedback Personally.** A colleague who identifies a structural flaw in a draft is saving the writer from presenting that flaw to a less forgiving audience. The revision process requires emotional detachment from the prose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Self-review discipline | Solo founders have no peer reviewers. The revision checklist serves as a surrogate editor, enforcing structural rigour even when the writer is the only reader before publication. | +| Validation | Evidence verification | Revision at this stage must prioritise truthfulness and completeness. Investors will scrutinise claims. Every data point must survive the "have I been utterly truthful?" test. | +| Early Traction | Speed-quality balance | The volume of writing increases sharply. The temptation is to skip revision entirely. A lightweight checklist -- even a 5-minute structural scan before sending -- prevents the worst errors without creating bottlenecks. | +| Growth | Peer review infrastructure | Dedicated editors or communications staff can own the editing function. Subject-matter experts draft; editors revise and polish. The separation of roles mirrors the separation of revision and editing. | +| Scale | Process and standards | Revision checklists become institutional standards. Style guides codify editing decisions. The three-draft process becomes organisational policy for high-stakes communications. | + +--- + +## Output Template + +```markdown +# Revision and Editing Report: [Document Title] + +## Revision Assessment (Macro Level) +| Question | Assessment | Action Required | +|----------|-----------|-----------------| +| Truthful and accurate? | [Yes/No/Partially] | [Specific fix] | +| Complete -- nothing missing? | [Yes/No] | [What to add] | +| Diplomatic and fair? | [Yes/No] | [Tone adjustment] | +| Clear opener with main point? | [Yes/No] | [Restructure how] | +| Points supported with evidence? | [Yes/No] | [Evidence gaps] | +| Structure apparent to reader? | [Yes/No] | [Headings needed] | +| Closer fresh and consistent? | [Yes/No] | [Revision needed] | + +## Editing Assessment (Micro Level) +| Dimension | Current State | Improvement | +|-----------|--------------|-------------| +| Word economy | [Word count: X] | [Target: Y, cuts identified] | +| Phrasing quality | [Weak areas] | [Specific rewrites] | +| Meaning clarity | [Ambiguous passages] | [Disambiguations] | +| Transitions | [Gaps identified] | [Connectors added] | +| Grammar/mechanics | [Errors found] | [Corrections] | + +## Peer Feedback Summary +| Reviewer | Role | Key Finding | Resolution | +|----------|------|-------------|------------| +| [Name] | Content reviewer | [Finding] | [Action taken] | +| [Name] | Prose reviewer | [Finding] | [Action taken] | + +## Draft Progression +- **Draft 1 word count:** [X] +- **Draft 2 word count (post-revision):** [Y] +- **Draft 3 word count (post-editing):** [Z] +- **Net change:** [Percentage reduction/expansion] +``` + +--- + +## Related Skills + +- **[Writing Process](writing-process.md)** -- MACJ provides the four-phase structure; this skill expands the Judge phase into a comprehensive revision and editing discipline. +- **[Clarity and Concision](clarity-and-concision.md)** -- The editing checklist's "Can I save some words?" question is the gateway to the concision techniques detailed in this companion skill. +- **[Plain Language and Flow](plain-language-and-flow.md)** -- The editing question "Does one sentence glide into the next?" connects directly to the continuity and transition techniques covered here. +- **[Grammar and Mechanics](grammar-and-mechanics.md)** -- The final editing pass depends on mechanical precision; this companion skill provides the specific rules and common error patterns to check against. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Leaders who review others' writing benefit from the structured peer feedback methodology in this skill. +- **[Tone and Engagement](tone-and-engagement.md)** -- Revision is the stage where tonal problems surface; the diagnostic tools for passive voice, nominalizations, and register mismatches apply during the editing process. diff --git a/plugins/foreman/content/skills/writing/tone-and-engagement.md b/plugins/foreman/content/skills/writing/tone-and-engagement.md new file mode 100644 index 0000000..5797f8e --- /dev/null +++ b/plugins/foreman/content/skills/writing/tone-and-engagement.md @@ -0,0 +1,216 @@ +--- +name: "tone-and-engagement" +description: "Diagnoses and corrects the tonal failures that cause business writing to anaesthetise readers rather than persuade them. Addresses passive voice, nominalizations, hyperformality, sarcasm, and the specific calibration of tone to audience and relationship. Use when drafting client communications, revising documents that feel lifeless or overly formal, preparing sensitive messages that require tonal precision, or building writing standards for a team." +version: "1.1.0" +category: "writing" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - tone + - engagement + - passive-voice + - reader-focus + - business-etiquette + - plain-language +related_skills: + - grammar-and-mechanics + - writing-effective-emails + - writing-memos-and-reports + - giving-feedback +author: "Fatih Guner" +--- + +# Tone and Engagement + +Most business writing functions like chloroform. Not because the content lacks substance, but because the delivery system -- passive constructions, nominalizations, hyperformality, alphabet soup acronyms -- works with quiet efficiency to render the reader unconscious before the third paragraph. The author, having invested hours in research and analysis, packages the result in prose so anaesthetised that no one absorbs it. The irony is structural: the harder people try to sound professional, the less effectively they communicate. The antidote is not casualness. It is precision, warmth, and the discipline to write for a reader rather than at one. + +--- + +## The Framework + +### The Five Anaesthetics of Business Writing + +The framework identifies five mechanisms through which business prose loses its reader. Each operates independently, but they tend to cluster -- a document infected with one typically hosts several. + +**1. Passive Voice** + +Passive voice removes the actor from the sentence, creating prose that sounds as though events simply happened, with no one responsible. + +- *Before:* "It has been decided that the project will be restructured." +- *After:* "We have decided to restructure the project." + +Passive voice is not grammatically wrong. It is stylistically weak when used as a default. Reserve it for situations where the actor is genuinely unknown or deliberately unimportant: "The building was constructed in 1952." + +**2. Nominalizations** + +Nominalizations convert vivid verbs into abstract nouns, draining energy from every sentence they touch. + +- *Before:* "The implementation of efficiency measures by the company resulted in the generation of cost savings." +- *After:* "The company implemented efficiency measures and saved money." + +The diagnostic: look for *-tion*, *-ment*, *-ness*, and *-ity* endings. Every nominalization is a verb imprisoned in noun form. Liberate it. + +**3. Hyperformality** + +Hyperformality replaces everyday words with inflated alternatives, creating distance between writer and reader. + +| Hyperformality | Plain Alternative | +|----------------|-------------------| +| "How may I be of assistance?" | "How can I help?" | +| "Subsequent to our conversation" | "After we spoke" | +| "At your earliest convenience" | "As soon as you can" | +| "We are in receipt of" | "We've received" | +| "Pursuant to your instructions" | "As you asked" | +| "Enclosed please find" | "Here are..." | + +The test: would you say this to a colleague standing in front of you? If not, revise. + +**4. Alphabet Soup** + +Acronyms make writing easier for the writer and harder for the reader. A document dense with COGS, EBITDA, VBM, and ABC becomes a cipher that only insiders can decode. Spell out terms when the audience extends beyond specialists. The writer's shortcut is the reader's hindrance. + +**5. Abstraction Without Evidence** + +"He was a bad boss" tells the reader nothing actionable. "He got a promotion based on his assistant's detailed reports, but then denied that assistant even routine cost-of-living raises" shows the reader everything. Specifics persuade. Abstractions occupy space. + +### Calibrating Tone to Relationship + +Tone is not a fixed setting. It varies with the relationship between writer and reader. + +**Collegial, not distant.** Write as though speaking to the recipient. Use personal pronouns (*you*, *we*, *our*) rather than impersonal constructions (*the undersigned*, *it is recommended*). This does not mean casual -- it means human. + +**Warm, not sycophantic.** Brief courtesies (*thank you*, *we appreciate*) establish goodwill. Extended flattery ("I just thought I'd drop you a note to tell you just how effective I think you've been...") suggests an agenda. + +**Direct, not aggressive.** State what happened, what the effect was, and what needs to change. Never use language designed to make the reader feel stupid: *labor under a delusion*, *claim to understand*, *fail to comprehend*. + +**Professional, not sarcastic.** Sarcasm in writing lacks the vocal cues that signal humour in speech. On the page, it reads as contempt. Compare: + +- *Before:* "Given that Monday was a bank holiday, as declared by federal statute no less, your e-mail of the present month did not come to my attention until yesterday. It is with no small degree of regret that we note you deemed it necessary to send a follow-up." +- *After:* "Because Monday was a bank holiday, I didn't receive your e-mail until yesterday. Naturally I was sorry that you had to write a second time. But of course I want you to call on me whenever I might help." + +The first version drips with condescension. The second achieves the same informational content with warmth intact. + +### The "Jury Test" + +Imagine everything you write will be read aloud before a jury in a contentious lawsuit. This exercise -- recommended for all professional correspondence -- forces two disciplines: (1) precision in what you claim, and (2) collegiality in how you claim it. People have lost jobs and companies have lost cases over ill-considered letters, memos, and emails. + +### The Relevance Principle: What's In It For the Reader + +Tone calibration solves half the engagement problem -- making prose sound human rather than institutional. The other half is relevance: giving the reader a reason to care. *Writing for Busy Readers* identifies this as the "So what?" test. When readers regard a topic as personally relevant, research shows they exert more effort to understand it, read more deeply, and recall more content. When they do not see personal relevance, they skim, procrastinate, or delete -- regardless of how well-crafted the prose may be. + +The evidence is striking. In an experiment with the youth voter organisation Rock the Vote, 19,990 people received an email encouraging them to volunteer at live concerts. The writer's-perspective version used the subject line "Volunteer with Rock the Vote." The reader's-perspective version used "Want to attend free events?" The body of the reader's-perspective email added a single sentence: "You'll get to see the best shows for free and do important work at the same time!" Recipients of the reader's-perspective version were nearly four times as likely to sign up as those who received the writer's-perspective version. The two emails were otherwise identical. The difference was one subject line and one sentence -- both framed around what the reader stood to gain. + +Psychologist Richard Petty and colleagues demonstrated the same mechanism in a university setting: students who were told that *their own* college was considering a new exam requirement read the policy proposal more carefully and fully than students told that a college in another state was considering it. Personal stakes drive attention. Absent those stakes, even well-written material gets the skim treatment. + +The practical application for business writers is a two-question filter applied before sending any communication: + +1. **"So what?"** -- If the recipient were to read only the subject line and the first sentence, would they understand why this message matters *to them personally*, not merely to the organisation? +2. **"Why me?"** -- If the message is going to a group, is it clear which recipients need to act and which can safely ignore it? Generic mass communications that fail this test waste time for irrelevant recipients and get ignored by relevant ones. + +The relevance principle does not require manipulation or clickbait. It requires the writer to shift perspective -- from "what do I need to say?" to "what does the reader need to hear?" The same information, reframed around reader benefit, produces measurably higher engagement without altering the substance. A product recall notice titled "Important product safety recall information" is writer-perspective. The same notice titled "If you bought Soup XYZ in June, it has been recalled" is reader-perspective -- more targeted, more useful, and more likely to reach the people who need it. + +--- + +## Prompts + +**Prompt 1 -- Anaesthesia Diagnosis:** +> Analyse the following document for the five engagement killers: passive voice, nominalizations, hyperformality, acronym density, and abstraction without evidence. For each instance found, quote the original, identify the specific problem, and provide a revised version that preserves the meaning while improving readability. Document: [paste text] + +**Prompt 2 -- Tone Calibration:** +> I need to send a message to [describe recipient and your relationship]. The message needs to communicate [describe content]. The emotional context is [describe -- e.g., the recipient will be disappointed, the news is positive, the situation is tense]. Draft the message with appropriate tone, then explain the tonal choices you made and why they fit the relationship and context. + +**Prompt 3 -- Formality Detox:** +> Rewrite this document, replacing every instance of hyperformality with a plain-language alternative. Maintain professionalism but eliminate all language that the recipient would never hear in a face-to-face conversation. Then provide a before/after comparison for each change. Document: [paste text] + +**Prompt 4 -- Specificity Upgrade:** +> This document relies heavily on abstract claims and vague assertions. Identify every instance where a specific fact, number, name, or example would strengthen the writing. For each, suggest what kind of specific detail would be most persuasive and, where possible, draft an improved version. Document: [paste text] + +**Prompt 5 -- The "So What?" / "Why Me?" Relevance Audit:** +> Here is a communication I am about to send: [paste text]. The audience is [describe recipients]. Apply the relevance test: (1) Read the subject line and first sentence only -- does the reader immediately understand why this matters to *them*, not just to the sender? (2) If this is going to a group, is it clear which recipients need to act? (3) Identify every passage written from the writer's perspective and rewrite it from the reader's perspective, emphasising what the reader stands to gain, lose, or need to do. (4) Produce a revised version where relevance is front-loaded and the "So what?" question is answered within the first two sentences. + +--- + +## Use Cases + +**Validation-Stage Startup Rewriting Its Landing Page** +A B2B SaaS startup's landing page reads: "Our solution facilitates the optimization of operational workflows through the implementation of advanced algorithmic processes." The founder, a former management consultant, has unconsciously replicated the tone of McKinsey decks. After a tone and engagement audit, the page reads: "We help operations teams work faster by automating the steps that slow them down." Conversion rate improves 22% in the first month -- not because the product changed, but because prospective customers could finally understand what it did. + +**Growth-Stage Company Issuing a Difficult Client Communication** +A project has missed its deadline by three weeks. The project manager drafts a client email that opens: "It is with regret that we must inform you of a delay in the deliverable timeline that has been occasioned by unforeseen complications in the development process." After revision: "We owe you an update -- and an apology. The project is three weeks behind schedule because we underestimated the integration complexity. Here is our revised timeline and what we are doing to prevent a recurrence." The revised version is shorter, takes ownership, and provides actionable information. The client relationship survives. + +**Scale-Stage Organisation Standardising Communication Tone** +A 500-person company discovers, through a customer satisfaction survey, that clients describe its written communications as "corporate," "impersonal," and "hard to understand." A tone audit of 50 representative documents reveals that 73% are written primarily in passive voice, 41% use hyperformality, and the average Flesch Reading Ease score is 22 (comparable to the Harvard Law Review). The company develops a tone guide, trains its team, and raises the average readability score to 55 within six months. Customer satisfaction on "communication clarity" increases by 31 points. + +--- + +## Anti-Patterns + +1. **Confusing Casual with Engaging.** The opposite of hyperformality is not informality -- it is clarity. Replacing "subsequent to our conversation" with "hey, so about what we talked about lol" does not represent an improvement. The target is relaxed professionalism: language you would use with a respected colleague, not language you would use in a group chat. + +2. **Eliminating All Passive Voice.** Some sentences genuinely read better in passive voice, particularly when the actor is unknown or when the action matters more than the agent. "The building was evacuated" is more appropriate in an incident report than "Security guard James Johnson evacuated the building." Passive voice is a tool, not a virus. + +3. **Over-Personalising Professional Communications.** Adding warmth does not mean sharing personal details, making jokes, or using exclamation marks. A message to a client about a billing discrepancy should sound human and warm, not like a birthday card. + +4. **Tone-Deafness to Power Dynamics.** Writing with excessive familiarity to a board member or with unnecessary formality to a direct report signals either obliviousness or insecurity. Tone must account for hierarchical context, relationship history, and cultural norms. + +5. **The Sarcasm Trap.** Sarcasm in written communication is almost always a mistake. Without vocal inflection, facial expression, or shared context, sarcastic text reads as hostility. The writer intends wit; the reader perceives contempt. The gap between the two is a lawsuit waiting to happen. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder voice in pitches and outreach | The founder's personal tone *is* the company's tone. Warmth, directness, and clarity in investor emails and cold outreach set the pattern for all future communications. | +| Early Traction | Client-facing tone consistency | With the first paying customers, tone in proposals, onboarding emails, and support responses directly affects retention. Hyperformality signals distance; warmth signals partnership. | +| Growth | Multi-author tone alignment | Multiple team members now write on behalf of the company. Without a tone guide, each brings their own voice -- ranging from robotic to inappropriately casual. A tone framework creates consistency. | +| Scale | Organisational tone governance | At scale, tone becomes part of brand identity. Training programmes, editorial review, and tone-checking tools ensure that thousands of communications per week maintain a consistent voice. | + +--- + +## Output Template + +```markdown +# Tone and Engagement Audit: [Document Name] + +## Readability Metrics +- **Flesch Reading Ease:** [score] (target: 45-65 for business documents) +- **Average sentence length:** [number] words (target: under 20) +- **Passive voice percentage:** [number]% (target: under 15%) + +## Anaesthesia Inventory +| Issue Type | Count | Severity | +|-----------|-------|----------| +| Passive voice | [n] | [high/medium/low] | +| Nominalizations | [n] | [high/medium/low] | +| Hyperformality | [n] | [high/medium/low] | +| Acronym overload | [n] | [high/medium/low] | +| Abstract claims | [n] | [high/medium/low] | + +## Top 5 Revisions (Before/After) +1. **Before:** "[original]" --> **After:** "[revised]" +2. **Before:** "[original]" --> **After:** "[revised]" +3. **Before:** "[original]" --> **After:** "[revised]" +4. **Before:** "[original]" --> **After:** "[revised]" +5. **Before:** "[original]" --> **After:** "[revised]" + +## Tone Assessment +- **Current tone:** [e.g., "Overly formal, impersonal, bureaucratic"] +- **Recommended tone:** [e.g., "Collegial, direct, warm"] +- **Key adjustments:** [specific changes needed] +``` + +--- + +## Related Skills + +- **[Grammar and Mechanics](grammar-and-mechanics.md)** -- Correct grammar provides the foundation; tone determines whether grammatically correct prose actually resonates with readers. +- **[Writing Effective Emails](writing-effective-emails.md)** -- Email is the format where tonal miscalibration does the most frequent damage, given its speed and volume. +- **[Writing Memos and Reports](writing-memos-and-reports.md)** -- Reports are the documents most prone to passive voice, nominalizations, and abstraction -- the precise ailments this skill diagnoses. +- **[Reader Psychology](reader-psychology.md)** -- Tone influences the first two stages of reader triage; understanding how readers process emotional register explains why tonal choices have outsized impact on engagement. +- **[Giving Feedback](../frameworks/giving-feedback.md)** -- Feedback conversations require the same tonal calibration as written communications: direct without aggression, warm without vagueness. +- **[Radical Candor](../frameworks/radical-candor.md)** -- The balance of caring personally and challenging directly maps onto the tonal challenge of being honest without being harsh in written form. diff --git a/plugins/foreman/content/skills/writing/writing-effective-emails.md b/plugins/foreman/content/skills/writing/writing-effective-emails.md new file mode 100644 index 0000000..10f5ce5 --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-effective-emails.md @@ -0,0 +1,195 @@ +--- +name: "writing-effective-emails" +description: "Provides a practical system for writing emails that get read, answered, and acted upon. Covers subject line craft, optimal length, formatting for scanning, tone calibration, CC/BCC etiquette, and when to choose a different medium entirely. Use when composing high-stakes emails to investors or clients, establishing email standards for a team, preparing sensitive written communications, or diagnosing why outreach emails receive poor response rates." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - email + - communication + - subject-lines + - brevity + - etiquette + - professional-writing +related_skills: + - tone-and-engagement + - grammar-and-mechanics + - writing-memos-and-reports + - giving-feedback +author: "Fatih Guner" +--- + +# Writing Effective Emails + +The average manager receives 121 emails per day. At a generous reading rate of thirty seconds per email, that is an hour simply triaging -- deciding which messages deserve attention and which deserve the archive. The arithmetic is ruthless: each email competes with 120 others for a finite allocation of cognitive bandwidth. Subject line, first sentence, length, formatting, and tone collectively determine whether a message lands in the "read and act" category or the "skim and forget" graveyard. Most business emails -- painstakingly drafted, carefully considered -- end up in the graveyard. Not because they lacked substance, but because they failed the thirty-second audition. + +--- + +## The Framework + +### The Six Principles of Effective Email + +**1. Get to the Point in the First Two Sentences** + +State your purpose immediately. Politely, but immediately. Do not build up to the request through three paragraphs of context that the reader will skip anyway. + +- *Before:* "It's been ages, I know, but I've been meaning to tell you just how effective I think you've been as the editor of the Daily Metropolitan these past seven years. Although I cancelled my subscription a few years back (LOL) -- the papers kept cluttering the driveway -- I buy a copy at the coffee shop almost every day. Anyhoo, I have a mentee I'd like you to meet..." +- *After:* "May I ask a favour of you? Glenda Jones, a really sharp mentee in the township's Young Leaders programme, wants to pursue a career in journalism. Would you spend 15 minutes chatting with her at your office sometime this month?" + +The second version is longer in total but arrives at its point faster. Everything it includes serves the request. + +**2. Copy People Judiciously** + +Include only those who will immediately understand why they are on the thread. Reply All is the nuclear option of email etiquette -- use it only when every recipient genuinely needs to see your response. The instinct to "keep people in the loop" produces loops that strangle productivity. + +**3. Keep the Message to One Screen** + +People find long emails irksome. The more they scroll, the less receptive they become. Many recipients close long emails immediately, planning to return to them later -- a plan that rarely materialises. Compose more than a single screen of reading only when the content genuinely demands it, and in those cases, use subheadings and bullet points to enable scanning. + +**4. Write a Short but Informative Subject Line** + +The subject line is the email's headline. A generic or blank subject line guarantees burial. + +| Weak Subject Line | Strong Subject Line | +|-------------------|---------------------| +| "Program" | "The Nov. 15 Leadership Programme" | +| "Quick question" | "Budget Approval Needed by Friday" | +| "Update" | "Q3 Revenue Update: +14% vs. Plan" | +| "Hello there!" | "Request for an Interview" | + +If the email requires action, signal it in the subject line. "Action Required:" or "Decision Needed:" are not rude -- they are respectful of the reader's time. + +**5. Maintain Standard Capitalisation and Punctuation** + +Rushed emails that violate basic writing conventions -- no capitals, no punctuation, cryptic abbreviations -- communicate carelessness. Standing out as someone who writes properly is a low-effort competitive advantage. Clarity written once costs less time than the follow-up email explaining what the first one meant. + +**6. Use a Professional Signature** + +Include your title and contact information. Keep it clean -- not too long, not ornate. The signature makes it convenient for recipients to choose how to reach you. + +### The Tone Spectrum for Email + +Email tone must match the relationship and the content. The framework identifies three registers: + +**Collegial and Direct** (for peers, regular collaborators): +> "Can you review the deck by Thursday? I need your input on slides 6-8 before the client meeting." + +**Professional and Warm** (for clients, senior stakeholders): +> "Thank you for the thoughtful feedback on the proposal. I've incorporated your suggestions into the revised version -- attached. Would Tuesday work for a brief call to walk through the changes?" + +**Firm but Respectful** (for difficult messages): +> "Several people have complained about the email you sent yesterday. Our company's policy does not make an exception for offensive language, even when used in jest. Please think about how future emails will affect your coworkers. If I receive complaints again, HR will have to get involved. But I trust that won't be necessary." + +Note the progression: the firm version states facts, cites policy, explains consequences, and closes with a statement of trust. It never attacks the person's character, never uses sarcasm, and never makes threats it cannot back up. + +### When Not to Use Email + +Email is the wrong medium when: + +- **The topic is emotionally charged.** A phone call or face-to-face conversation allows for real-time calibration of tone. +- **The issue requires rapid back-and-forth.** Five rounds of email take five hours. One conversation takes ten minutes. +- **The content is confidential.** Email is a permanent record that can be forwarded, subpoenaed, or leaked. +- **You are angry.** Write the email if you must -- then delete it. Wait 24 hours. Write a new one. + +--- + +## Prompts + +**Prompt 1 -- Email Rewrite:** +> Rewrite this email to be shorter, more direct, and more likely to receive a prompt response. Keep the same informational content but restructure it so the purpose is clear in the first two sentences, the body is scannable, and the call to action is unmistakable. Original email: [paste text] + +**Prompt 2 -- Subject Line Generator:** +> I need to send an email about [describe topic and purpose]. The recipient is [describe]. Generate five subject line options, ranging from informational to action-oriented. For each, explain why it would work and when it would be most appropriate. + +**Prompt 3 -- Difficult Email Drafter:** +> I need to send an email to [describe person and relationship] about [describe sensitive topic]. I want to be direct without being aggressive, and I need to [describe desired outcome]. Draft the email using a firm-but-respectful tone. Then explain the tonal choices -- what you included, what you avoided, and why. + +**Prompt 4 -- Email Audit:** +> Analyse my last five sent emails [paste them] against the six principles of effective email: directness, judicious copying, brevity, informative subject lines, standard conventions, and professional signature. Score each email on a 1-5 scale for each principle and provide specific recommendations for improvement. + +--- + +## Use Cases + +**Idea-Stage Founder Sending Cold Outreach** +A founder sends 50 cold emails to potential advisors with the subject line "Hello!" and an opening paragraph of self-introduction that runs eight sentences before mentioning what she wants. Response rate: 2%. After restructuring with a specific subject line ("Request: 15-min Call on EdTech Distribution Strategy"), a two-sentence opening that states the ask, and a total length of six sentences, response rate climbs to 18%. The content of the request did not change. The packaging did. + +**Early-Traction Startup Managing a Client Escalation** +A client emails the CEO directly, furious about a missed deliverable. The CEO's instinct is to respond immediately, defensively, and at length. Instead, she waits two hours, drafts a response using the firm-but-respectful framework: acknowledges the problem (first sentence), takes ownership (second sentence), provides a concrete remediation plan (third paragraph), and closes with a specific follow-up commitment. The client de-escalates within one reply. The email thread, later reviewed by the board, demonstrates maturity under pressure. + +**Growth-Stage Company Reducing Email Overload** +A 150-person company discovers that the average employee sends or receives 94 internal emails per day. A review of a sample reveals that 40% of internal emails could be replaced by Slack messages, 15% are unnecessary Reply Alls, and 20% are emails that should have been meetings. The company institutes an email protocol based on the six principles, including a "no Reply All without justification" policy. Internal email volume drops 35% in the first quarter. + +--- + +## Anti-Patterns + +1. **The Wall of Text.** An email that runs twelve paragraphs with no subheadings, no bullet points, and no visual breaks. The reader's eye has nothing to anchor on, so it skims, misses the key request buried in paragraph nine, and the sender wonders why nothing happened. + +2. **The Passive-Aggressive CC.** Copying someone's manager on an email to apply pressure. This tactic is transparent, breeds resentment, and signals that the sender cannot resolve issues directly. If escalation is genuinely necessary, do it explicitly and openly. + +3. **The Emotional Send.** Writing and sending an email while angry. Email is a permanent, forwardable record. The catharsis of an angry send is always outweighed by the regret of re-reading it the next morning. Write it, delete it, wait, then write a new one. + +4. **The Subject-Line Hijack.** Replying to an old email thread about a completely different topic because it is easier than starting a new one. The original subject line becomes a lie, the new content is unfindable in future searches, and every recipient on the old thread receives irrelevant noise. + +5. **The Disclaimer Novel.** Appending a 200-word legal disclaimer to every email, including internal messages. If legal counsel requires a disclaimer, keep it minimal. A disclaimer longer than the email itself is a parody of professionalism. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cold outreach to investors and advisors | Every email is an audition. Subject lines and opening sentences determine whether the founder gets a meeting or gets ignored. Volume is high; conversion rate depends entirely on craft. | +| Validation | Investor updates and early customer communication | Regular investor updates establish cadence and trust. Clarity and brevity signal competence. Customers evaluate the company partly through the quality of its email communication. | +| Early Traction | Client management and internal coordination | Email becomes a primary coordination tool. The volume increases, making brevity and clear subject lines essential for operational efficiency. | +| Growth | Email culture and protocols | Bad email habits, multiplied across a growing team, create organisational drag. Establishing email norms -- when to email vs. message, CC etiquette, response-time expectations -- prevents communication debt. | +| Scale | Automated and templated communications | At scale, many emails are templated or automated. Tone, clarity, and personalisation in templates determine whether they feel human or robotic. Each template represents thousands of reader impressions. | + +--- + +## Output Template + +```markdown +# Email Draft: [Purpose] + +## Pre-Send Checklist +- [ ] Subject line is specific and action-oriented +- [ ] Purpose is clear in the first two sentences +- [ ] Total length fits within one screen +- [ ] Only necessary recipients are included (To/CC) +- [ ] Tone matches the relationship and content +- [ ] Call to action is explicit and includes a deadline +- [ ] Standard capitalisation and punctuation used throughout +- [ ] Signature includes title and contact information +- [ ] Read aloud for tone -- would I say this in person? +- [ ] If emotionally charged: waited at least 2 hours before sending + +## Draft Structure +**Subject:** [specific, informative subject line] + +**Opening (1-2 sentences):** [purpose and context] + +**Body (3-5 sentences max):** [supporting details, formatted for scanning] + +**Close (1-2 sentences):** [specific call to action with deadline] + +**Signature:** [name, title, contact] +``` + +--- + +## Related Skills + +- **[Tone and Engagement](tone-and-engagement.md)** -- Email is the highest-frequency venue for tonal miscalibration; the principles of tone management apply with particular urgency to the inbox. +- **[Grammar and Mechanics](grammar-and-mechanics.md)** -- Speed and informality make email the most common source of grammar errors in professional writing. +- **[Writing Memos and Reports](writing-memos-and-reports.md)** -- When the content exceeds one screen, the writer should consider whether the message belongs in a memo or report rather than an email. +- **[Writing for Response](writing-for-response.md)** -- The friction-reduction principles for getting readers to act apply with particular force to the inbox, where every additional step reduces response probability. +- **[Writing for Navigation](writing-for-navigation.md)** -- Subject line craft, one-screen discipline, and scanning-optimised formatting are email-specific applications of the broader navigation architecture. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Leaders send the highest-stakes emails in any organisation; the four principles of leadership writing apply with particular force to the inbox. diff --git a/plugins/foreman/content/skills/writing/writing-for-navigation.md b/plugins/foreman/content/skills/writing/writing-for-navigation.md new file mode 100644 index 0000000..649ce3f --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-for-navigation.md @@ -0,0 +1,200 @@ +--- +name: "writing-for-navigation" +description: "Provides a structural system for arranging written content so busy readers can find what matters within seconds. Covers BLUF (Bottom Line Up Front), visual hierarchy, headings as signposts, bullet point strategy, formatting discipline, and the map metaphor for document design. Use when structuring investor updates, redesigning internal communications, formatting product announcements, or diagnosing why well-written messages still fail to land." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - navigation + - BLUF + - visual-hierarchy + - formatting + - headings + - bullet-points + - document-design +related_skills: + - reader-psychology + - writing-for-response + - writing-effective-emails + - clarity-and-concision + - writing-memos-and-reports +author: "Fatih Guner" +--- + +# Writing for Navigation + +MAP. Stop thinking of your writing as a path readers walk along -- think of it as a map they zoom into. The question is: can they find what matters in three seconds? When someone opens Google Maps, the default view is a bird's-eye orientation -- country, state, city -- before any street-level detail appears. Readers approach documents the same way: they scan the landscape, identify regions of interest, and zoom in selectively. If the landscape offers no landmarks, they leave. The US Army codified this principle decades ago as BLUF -- Bottom Line Up Front -- an official policy requiring writers to place key information at the beginning of every communication. Military efficiency aside, BLUF reflects a cognitive reality that applies to every email, memo, and Slack message an entrepreneur will ever send: readers who cannot orient themselves within seconds will not orient themselves at all. + +--- + +## The Framework + +### Six Rules of Navigable Writing + +**Rule 1: Make Key Information Immediately Visible** + +The first question a reader asks is, "What is this about?" The easier the writer makes it to answer that question, the more likely the reader is to stay. In journalism, failing to answer it early is called "burying the lede." Literary magazines bury ledes on purpose, building mood before revealing the central conflict. Practical communications are not literary magazines. + +A useful rule of thumb: place the most important information where busy readers expect to find it. BLUF positions the bottom line at the top. Abstracts, executive summaries, and TL;DR headers serve the same function. The specific convention varies by culture -- anecdotal evidence suggests that in some post-Soviet republics, the most important information traditionally appears in the final paragraph, and readers skim bottom-up accordingly. The principle is not "always put it first" but rather "always put it where your specific readers will look first." + +There is a tension worth acknowledging. In warm or relationship-driven contexts, a message that opens with a blunt request can feel cold or presumptuous. Consider two versions of the same sales email: + +- *Courteous order:* "I've thought more about our conversation. Your organisation is not alone in facing the challenges we discussed. I think the services my firm offers could be of use to you. Can we set up a time to discuss you hiring my firm?" +- *BLUF order:* "Can we set up a time to discuss you hiring my firm? I've thought more about our conversation. Your organisation is not alone in facing the challenges we discussed." + +The BLUF version ensures the ask is seen. The courteous version risks the ask being missed if the reader stops early. The practical compromise: one sentence of courteous framing, then the ask. Not three paragraphs of preamble followed by a request the reader never reaches. + +**Rule 2: Separate Distinct Ideas** + +Placing visual space between unrelated topics allows readers to skim without conflating separate issues. The simplest technique is giving each distinct topic its own paragraph. A Danish study of 888 adults tested this: participants read a description of unemployment benefit requirements, half in a single dense paragraph and half with each requirement on its own line. Comprehension was equivalent, but the separated version was read 15% faster. The readers did not need to spend cognitive effort deciding where one idea ended and the next began. + +Bullet points are the strongest visual signal of separation. Numbered lists impose additional sequential logic. Blank space works when neither is appropriate. + +**Rule 3: Place Related Ideas Together** + +Grouping related items reduces search cost. When a project update assigns tasks to two people -- say, Jessie and Marion -- interleaving their items forces both readers to scan the entire list. Clustering Jessie's tasks together and Marion's tasks together allows each person to find their responsibilities immediately. The clustering also enables consolidation: if both of Jessie's tasks involve writing and both of Marion's involve research, the task descriptions can be simplified, reducing total word count from 46 to 39 in the original example tested in the research. + +For messages with multiple requests, the grouping strategy depends on whether the requests relate to the same topic. If they do, cluster them. If each request belongs to a different section, embed it in its section but foreshadow all requests at the top: "Below I cover three items and ask for your input on each: (1) ... (2) ... (3) ..." + +**Rule 4: Order Ideas by Priority** + +The first item in any list receives disproportionate attention. Research on Texas primary elections showed that moving a candidate from last to first on a ballot increased their vote share by up to 10 percentage points in some races. The multibillion-dollar search advertising industry operates on the same principle: the top position in search results captures the most clicks. Amazon exploits this when promoting specific products over others. A study of link positioning on web pages confirmed the pattern quantitatively: the first link received the most clicks, with a steady decline through each subsequent position, and only a minor uptick at the very last position compared to second-to-last. + +When no inherent logic dictates order (chronological, procedural, or causal), default to priority. Place the most important item first. There is modest evidence that the final position in a list also receives slightly elevated attention -- studies of jury trials found that the last evidence presented can be heavily weighted -- but jurors are obligated to sit through the entire trial. Busy readers are under no such obligation. The first position dominates, and the writer who buries a critical item in position four of six is making a bet against the reader's patience. + +**Rule 5: Include Headings** + +Headings function as section labels on a map. Eye-tracking data shows that readers scanning a page fixate on headings before anything else, using them to decide which sections to zoom into and which to bypass entirely. + +A study with the Journalist's Resource tested this directly. A nine-paragraph email newsletter covering three topics was sent to 46,648 subscribers. Half received the newsletter without headings; the other half received the same content with descriptive headings above the second and third topics. Subscribers who received headings were more than twice as likely to click links in those sections. Crucially, engagement with the first section (which had no heading in either version) was unaffected -- the headings did not divert attention, they unlocked it for content that would otherwise have been skipped. + +Headings also prove useful when prefacing bulleted lists. A bullet point does not automatically make its content clear. Messages with full paragraphs attached to each bullet, or lists with so many items that their unifying logic is obscure, benefit from a short heading at the start of each entry: + +- **Revised contract:** The firm's lawyers have agreed to all proposed edits but have requested two additional clauses. Can you review these additions? +- **Conference planning:** We are three months from the conference date. Could we set up a call to finalise the participant list and programme? + +Each heading lets the reader decide in a fraction of a second whether to read the detail that follows. Without it, the reader must parse the entire bullet to determine relevance. + +Headings should describe what follows with enough specificity to be useful but not so much length that they become a reading burden of their own. "What is the school doing?" is better than "Next steps." "School is monitoring all close contacts, and closing and disinfecting the building" is unnecessarily verbose. + +**Rule 6: Use Enough Formatting but No More** + +Formatting -- bold, italic, underline, highlighting, ALL CAPS -- serves two purposes: it conveys meaning beyond the words themselves, and it captures attention through visual contrast. Both purposes degrade with overuse. + +In a study of over 1,600 participants reading a five-paragraph passage, a single highlighted sentence was noticed and acted upon by 89% of readers (versus 65% with no formatting). But when five sentences were highlighted, compliance on the key sentence dropped to 65% -- formatting multiple items diluted the benefit by spreading attention across all of them. A separate study found that highlighting an irrelevant sentence actually decreased reading of the important unhighlighted sentence, from 48% to 39%. Readers inferred that the writer had already marked the important parts and paid less attention to everything else. + +The Goldilocks principle: format the one thing that matters most. If two or three things genuinely matter equally, format them -- but imagine a reader who reads only the formatted text. Will they have grasped the essentials? If not, reconsider. + +Italics and font colour present a different problem: ambiguity. Some readers interpret them as markers of importance; others interpret them as markers of emphasis within a sentence -- a meaningful distinction. "I am very excited" uses italics for emphasis on degree, not for importance. Without explicit guidance ("Key terms are italicised" or "Action items are in blue"), readers must guess. In professional settings where norms have been codified -- legal writing uses italics for case citations, for instance -- the ambiguity resolves. Elsewhere, it persists. + +ALL CAPS deserves special caution. While 75% of survey respondents interpret capitalised text as signalling importance, 25% interpret it as anger. More than three-quarters of the terms-and-conditions contracts for Amazon, Uber, and Facebook contain at least one all-caps paragraph, ostensibly to satisfy "clear and conspicuous" disclosure requirements. Courts have recently questioned whether all-caps text actually achieves this, and research shows capitalised passages take longer to read and can decrease understanding, particularly among older adults. + +Bullets carry their own risk. Readers interpret bulleted items as the most important content in a message. If low-priority items are bulleted while a high-priority request sits in an unformatted paragraph, the reader may attend to the bullets and skip the paragraph. One board chairperson discovered this after bulleting a thirteen-item list of client welcome gifts while embedding the actual request -- scheduling the next board meeting -- in an unformatted paragraph at the bottom. The meeting proved difficult to schedule. + +--- + +## Prompts + +**Prompt 1 -- BLUF Conversion:** +> Rewrite the following message using the BLUF (Bottom Line Up Front) principle. Place the single most important piece of information or request in the first sentence. Follow it with essential supporting context only. Remove or relocate everything else. Original message: [paste text] + +**Prompt 2 -- Navigation Audit:** +> Analyse this document as a map. For each section, identify: (a) whether it has a clear heading, (b) whether distinct ideas are visually separated, (c) whether related ideas are grouped, (d) whether items are ordered by priority, and (e) whether formatting highlights the right elements. Score each rule from 1-5 and provide a redesigned version. Document: [paste text] + +**Prompt 3 -- Formatting Discipline Check:** +> Review this message for formatting overuse or misuse. Count the number of bold, italic, underlined, highlighted, and capitalised elements. For each, assess whether it marks genuinely critical content or dilutes the reader's attention. Then produce a version that formats no more than two elements and achieves greater clarity. Message: [paste text] + +**Prompt 4 -- Cultural BLUF Adaptation:** +> I am writing to [describe audience in a specific cultural or organisational context]. Where would this audience expect to find the key information -- top, bottom, or elsewhere? Restructure the following message to match their expectations while preserving all essential content. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Structuring a One-Page Investor Brief** + +A first-time founder drafts a one-page summary for angel investors. The draft opens with two paragraphs of market context, moves to the team's background, and places the funding ask ($500K pre-seed round) in the final paragraph. An investor who spends eight seconds on the page -- the median for cold inbound -- never reaches the ask. + +Applying the BLUF principle, the founder restructures: the opening line states the ask and the core value proposition ("Raising $500K to eliminate the 72-hour settlement delay in cross-border B2B payments"). Market context moves to a supporting paragraph with a descriptive heading ("The Problem: $47B in annual settlement float"). Team credentials become a two-line sidebar under "Team." The funding terms land under "The Ask" -- bolded, as the single formatted element in the document. The same information, radically different navigability. The first version assumed the investor would walk the path. The second version gave them a map. + +**Early-Traction Startup Redesigning a Covid-Era School Notification** + +A school district sends parents a letter about a confirmed Covid case. The original version opens with three paragraphs of administrative language before revealing the critical fact: the school is closed for 48 hours. A busy parent -- cooking dinner, managing homework -- skims the first lines, sees no clear signal, and defers reading to "later." The redesigned version applies four navigation rules at once: the key fact ("[SCHOOL NAME] will be closed for at least the next 48 hours") appears as the first line after the salutation (Rule 1 and Rule 4), subsequent sections receive descriptive headings -- "What is [School Name] doing?", "How will you know if your child is a close contact?", "What to do if you or your child is sick?" (Rule 5) -- and each topic is visually separated into its own block (Rule 2). + +**Growth-Stage Company Reducing Failure-to-Appear Rates** + +The New York Police Department worked with researchers to redesign its court summons notification. The original form, titled "Complaint/Information," placed the court appearance date and time at the bottom of a dense form, below personal details and charge descriptions. The redesigned version applied all six navigation rules: the title changed to "Criminal Court Appearance Ticket" (Rule 1), court date and location moved to the top (Rule 4), distinct sections were separated (Rule 2), related items -- court address, date, time -- were grouped (Rule 3), clear headings flagged each section (Rule 5), and courthouse selection was converted from handwriting to a bubble-fill format (Rule 6). Over 17 months and nearly 324,000 recipients, failure-to-appear rates fell 13%, resulting in an estimated 23,000 fewer arrest warrants. + +--- + +## Anti-Patterns + +1. **The Chronological Trap.** Telling the story of how a decision unfolded rather than stating the decision and its implications first. Chronological order is the writer's natural instinct; it is almost never the reader's preference. The reader wants the conclusion, not the journey. + +2. **The Bullet Dump.** Listing twelve or more items as bullet points without headings, grouping, or priority ordering. A long, undifferentiated bulleted list is no easier to navigate than a dense paragraph -- it merely looks different. Each bullet should earn its place, and the list should have a clear heading that tells the reader what connects the items. + +3. **The Formatting Carnival.** Combining bold, italic, underline, highlighting, colour changes, and ALL CAPS in a single message. A taxi company email documented by researchers used every available formatting tool simultaneously. When shown to readers, no two agreed on which piece of information the writer considered most important. The effect of formatting many items was worse than formatting none. + +4. **Headings as Decoration.** Using vague headings ("Overview," "Details," "Next Steps") that describe structural positions rather than content. A heading should tell the reader what the section is about, not merely that it exists. "Q3 Revenue: +14% vs. Plan" is a heading. "Update" is a placeholder. + +5. **BLUF Without Warmth.** Applying Bottom Line Up Front so aggressively that the message reads as curt or demanding, especially in contexts where the reader expects a relational overture. The solution is not to abandon BLUF but to insert exactly one sentence of warmth before the ask -- not three paragraphs of it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch emails, one-pagers, advisor requests | Every document is competing with dozens of others for a distracted reader's attention. Navigation is the difference between "funded" and "filed." BLUF and ruthless brevity dominate. | +| Validation | Investor updates, customer feedback surveys, partnership proposals | Documents grow slightly longer but readers remain impatient. Headings and priority ordering become essential tools for keeping multi-topic updates scannable. | +| Early Traction | Client onboarding materials, internal process docs, support articles | The writer now serves multiple reader personas with different expertise levels. Headings allow each reader to jump directly to their section without wading through irrelevant content. | +| Growth | All-hands emails, policy memos, cross-functional announcements | Document volume and audience size both increase. Navigation standards must be codified into team style guides. The navigation audit becomes a recurring exercise, not a one-time fix. | +| Scale | Templated communications, automated notifications, regulatory filings | Navigation decisions are embedded in templates that serve thousands of readers. Small structural improvements -- moving a key date from paragraph four to the subject line -- compound across enormous volumes. | + +--- + +## Output Template + +```markdown +# Navigation Redesign: [Document / Message Name] + +## BLUF Statement +[One sentence: the single most important thing the reader needs to know or do.] + +## Document Map +1. **[Heading 1]** -- [What this section covers, in six words or fewer] +2. **[Heading 2]** -- [What this section covers] +3. **[Heading 3]** -- [What this section covers] + +## Priority Order +- **Most important:** [Item, placed first] +- **Second:** [Item] +- **Third:** [Item] + +## Formatting Plan +- **Formatted element(s):** [Maximum two -- what is bolded/highlighted and why] +- **Unformatted by design:** [What was deliberately left plain to avoid dilution] + +## Grouping Logic +- **Cluster 1:** [Related items grouped together] +- **Cluster 2:** [Related items grouped together] + +## Redesigned Message +[Full rewrite applying all six rules, annotated with rule numbers in brackets where each is applied] +``` + +--- + +## Related Skills + +- **[Reader Psychology](reader-psychology.md)** -- Provides the cognitive science that explains why navigation works: the F-pattern, working memory limits, and the four-stage triage process that every reader applies. +- **[Writing for Response](writing-for-response.md)** -- Extends navigation into action: once readers can find the key information, response-oriented design ensures they can act on it within 30 seconds. +- **[Writing Effective Emails](writing-effective-emails.md)** -- Applies navigation principles to the most common medium for business communication, including subject line craft and scanning-optimised formatting. +- **[Writing Memos and Reports](writing-memos-and-reports.md)** -- Covers longer-form documents where navigation architecture -- headings, sections, executive summaries -- is the primary determinant of whether the document gets read. +- **[Clarity and Concision](clarity-and-concision.md)** -- Provides the sentence-level discipline that complements document-level navigation: fewer words per sentence means less cognitive load at every anchor point. diff --git a/plugins/foreman/content/skills/writing/writing-for-response.md b/plugins/foreman/content/skills/writing/writing-for-response.md new file mode 100644 index 0000000..12649f5 --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-for-response.md @@ -0,0 +1,218 @@ +--- +name: "writing-for-response" +description: "Teaches how to write messages that convert reader understanding into reader action. Covers friction reduction, default design, the power of constrained choices, response-oriented formatting, and the 30-second response test. Use when crafting calls to action in emails or product copy, designing opt-in or enrolment flows, diagnosing low response rates on surveys or meeting requests, or building templates for action-oriented team communications." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - response-rate + - call-to-action + - friction + - defaults + - behavioural-design + - enrolment + - action-oriented-writing +related_skills: + - reader-psychology + - writing-for-navigation + - writing-effective-emails + - tone-and-engagement + - writing-with-purpose +author: "Fatih Guner" +--- + +# Writing for Response + +ONE PERCENT. When DC public schools asked parents to enrol in a text-message update programme via an online portal, 1% did. When the schools simplified the process to a single text reply -- respond "START" -- 11% did. When they made enrolment the default and let parents opt out by replying "STOP," 95% stayed. The lesson is not about parental apathy. The parents who ignored the portal were the same parents who stayed enrolled under the default. Motivation was constant across all three groups; friction was the variable. Response rates are not a measure of how much readers care. They are a measure of how much effort the writer demands. + +--- + +## The Framework + +### The Response Gap + +Even when readers understand a message perfectly and want to act on it, three barriers can prevent them from doing so: + +1. **They do not understand what is being asked.** The request is ambiguous, buried, or tangled in surrounding information. This is a clarity failure. +2. **They do not believe the action is worth the effort.** The writer has not established relevance, urgency, or personal stakes. This is a persuasion failure. +3. **The action is too hard or too time-consuming to perform right now.** The reader intends to comply but defers, and deferral is the precursor to forgetting. This is a friction failure. + +Most writers address the first two barriers instinctively. The third is where the opportunity lies -- and where the research is most striking. + +### Three Rules of Easy-Response Writing + +**Rule 1: Simplify the Steps Required to Act** + +The most powerful technique is eliminating steps entirely by changing the default. When an action happens automatically unless the reader opts out, participation rates approach universality. The retirement savings literature makes the case decisively: automatic enrolment with an opt-out option produces dramatically higher participation than opt-in processes requiring deliberate sign-up, even when the financial incentives are identical. + +When changing the default is not feasible, reducing the number of steps still yields large effects. The DC schools study quantified this precisely: moving from a multi-step portal (1% enrolment) to a single-step text reply (11% enrolment) produced a tenfold increase. The parents' interest in their children's grades did not change. The number of actions required did. + +Consider meeting scheduling, a task most professionals perform weekly. The open-ended approach -- "Want to talk next week?" -- initiates a multi-round volley of availability comparisons. Each round imposes a cognitive and logistical cost. An alternative: + +> Want to meet for 30 minutes next week? If so, how about one of these times (all ET): +> - Tuesday (3/13) at 10:30 am +> - Wednesday (3/14) at 12:00 pm +> - Thursday (3/15) at 3:00 pm + +This version specifies duration, proposes concrete options, clarifies time zones, and allows the reader to respond by selecting rather than generating. A study at a major US university tested a further simplification: including a Calendly link that let recipients book directly from the sender's calendar. The Calendly version secured meetings with 33% of recipients versus 17% for the standard "let me know your availability" request. The caveat: some recipients find unsolicited calendar links presumptuous, so the technique requires calibration to context. + +**Rule 2: Organise Key Information Needed for Action** + +Readers who must hunt for information in order to act are readers who will not act. When the US government offered prescription drug benefits to Medicare recipients in 2006, it sent letters directing recipients to a website with an 84-character URL, plus a booklet on how to navigate the site. Only 17% switched to a better plan. Researchers then tested a simplified letter that included the relevant comparison directly: the recipient's current plan, the lowest-cost alternative, the recommended option, and the estimated savings. No website navigation required. The switch rate nearly doubled to 28%, and average savings were $100 per person per year. + +The principle generalises to every action-oriented message. Instead of writing, "See the message below, sent on April 3, and let me know what you think," restate the pertinent information from April 3 in the current message. Searching through an email chain is a step. Every step is a chance for the reader to abandon the task. + +For communications that direct readers to online tools -- forms, portals, applications -- include the specific credentials needed to log in, when privacy constraints allow. "Did you know you can file your immigration forms online at [website]?" becomes significantly more actionable as: "Did you know you can file your immigration forms online? Your username is [name] and you can log in at [website]." One additional line eliminates the "forgot my username" barrier that causes a substantial portion of intended actions to stall. + +**Rule 3: Minimise the Amount of Attention Required** + +The brain's attention budget is finite, and complex decisions accelerate its depletion. A study at a large health services company found that offering employees a preselected retirement plan (with preset contribution rate and asset allocation) increased enrolment by 10 to 20 percentage points compared to requiring them to choose among all available options. Fewer decisions meant more participants. + +Narrow questions outperform broad ones for the same reason. + +| Question Type | Example | Reader Effort | +|---------------|---------|---------------| +| Broad (open-ended) | "How was yesterday's senior staff meeting?" | High. Requires synthesis and composition. | +| Narrow (constrained) | "In yesterday's meeting, did we decide whether we're submitting a bid?" | Low. Answerable with yes or no. | + +The broad question may yield richer feedback -- but only if the reader responds at all, which the data suggests is less likely. + +Excess choice creates what researchers call an "attention tax." Studies confirm that when people face too many options, they defer the decision -- often permanently. President Obama reportedly limited his wardrobe to grey and blue suits for precisely this reason: "I'm trying to pare down decisions. I don't want to make decisions about what I'm eating or wearing. Because I have too many other decisions to make." + +The ultimate test of attention minimisation is the **30-second response test**: can a reader act on this message within 30 seconds of opening it? If the answer is no, the message needs structural revision -- fewer steps, more constrained choices, or information that was missing and must now be supplied directly. + +### Multiple Requests: Bundle or Separate? + +Action-oriented messages frequently contain more than one request. A healthcare clinic, for instance, may need to (1) collect insurance information, (2) provide check-in instructions, and (3) confirm an appointment time. All three are urgent and related. In a survey of working professionals, 72% said they prefer receiving one message with three pieces of information over three separate messages. When requests relate to the same event and require similar levels of effort, bundling makes sense. + +The calculus changes when requests require different amounts of effort. A family email asking what time a relative will arrive (easy), what holiday gifts to buy (moderate), and where to find a lost family recipe (hard) bundles three fundamentally different cognitive tasks. The reader may answer the easy question and forget the rest -- or defer the entire message until they have time for the hardest question, a moment that may never arrive. Separating unequal requests into distinct messages protects the easy ones from being held hostage by the hard. + +When bundling is unavoidable, signpost the structure at the top: "Below are three items: (1) an update on the renovation, (2) a request for your approval on light fixtures, and (3) a request to schedule a call." The preview gives the reader a map before they enter the territory. + +### The Friction Spectrum in Practice + +| Friction Level | Mechanism | Typical Response Rate | +|----------------|-----------|----------------------| +| Zero (default) | Action happens unless reader opts out | 90-95% compliance | +| Minimal (one-step) | Single reply, single click, or single selection | 10-35% compliance | +| Moderate (multi-step) | Navigate to portal, log in, complete form | 1-5% compliance | +| High (complex) | Research options, make multiple decisions, find credentials | Below 1% | + +These numbers shift by context, audience, and stakes, but the gradient is remarkably consistent across domains -- from school enrolment to retirement savings to voter registration to meeting scheduling. + +### The IRS and the Power of Simple Instructions + +A study with the US Internal Revenue Service tested different styles of notification about the Earned Income Tax Credit, a benefit that eligible low-income workers must actively claim each year (roughly 20% of those eligible fail to do so). The simplified version included a clear, step-by-step explanation of what to do: complete the worksheet, determine eligibility, sign and return if eligible. The complex original version listed six bullet points of instructions plus a footnote. The complex notice produced a response rate 27% lower than the simple one. Moreover, a worksheet with seven eligibility criteria generated 17% fewer responses than one with just two criteria. The additional detail was accurate and potentially useful. It was also, in practice, a deterrent. + +--- + +## Prompts + +**Prompt 1 -- Friction Audit:** +> Map every step a reader must take to act on the following message. For each step, estimate the time and cognitive effort required. Then propose a revised version that eliminates at least two steps while preserving all essential outcomes. Message: [paste text] + +**Prompt 2 -- Default Design:** +> I need [describe audience] to [describe desired action]. The current approach requires them to opt in. Design an alternative that makes the desired action the default, with a clear and easy opt-out mechanism. Include the exact language for the initial communication and the opt-out instructions. + +**Prompt 3 -- 30-Second Response Test:** +> Apply the 30-second response test to this message. Assume the reader opens it on a mobile phone while walking between meetings. Can they complete the requested action in 30 seconds? If not, identify the bottleneck and rewrite the message to pass the test. Message: [paste text] + +**Prompt 4 -- Constrained Choice Conversion:** +> The following message asks the reader an open-ended question. Rewrite it as a constrained-choice question with no more than three predefined response options. Preserve the writer's intent while reducing the reader's cognitive load. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Scheduling Investor Meetings** + +A pre-seed founder sends 30 emails per week requesting introductory meetings with potential investors. The standard close reads: "Would love to find a time to chat -- let me know what works for you." This open-ended request requires the investor to check their calendar, compose available times, and manage the resulting back-and-forth. The founder switches to a constrained format: three specific time slots with durations and time zones, plus a Calendly link as a fallback. Meeting conversion from cold email rises from 4% to 11%. The pitch itself did not improve. The path from "interested" to "booked" shortened. + +**Validation-Stage Startup Increasing Survey Completion** + +A consumer health startup sends a post-onboarding survey to 2,000 beta users. The survey contains 14 open-ended questions and takes approximately eight minutes to complete. Completion rate: 6%. The product team diagnoses the problem using the friction spectrum: the survey sits at "moderate" friction (click link, load page, read 14 questions, compose 14 answers). Eight minutes is an eternity for a user who signed up three days ago. + +The team applies the three rules systematically. They reduce the survey to five questions (Rule 3), convert four of them to multiple-choice with a free-text "Other" option (Rule 3), and embed the first question directly in the email body so readers can begin answering before they even click through to the survey platform (Rule 1). The email subject line changes from "Share your feedback" to "One quick question about your first session." Completion rate rises to 23%. The qualitative richness of individual responses decreases modestly, but the sample size nearly quadruples, improving the statistical reliability of every finding. + +**Growth-Stage Company Driving Adoption of a New Expense Tool** + +A 400-person company rolls out a new expense reporting tool. The finance team sends an all-hands email with a three-paragraph explanation, a link to a 20-minute training video, and instructions to "set up your account by Friday." Adoption after one week: 22%. The team redesigns the rollout communication. The email now opens with a single sentence ("Submit expenses in two clicks -- your account is already active"), includes a direct link to the tool with the user's credentials pre-filled, and replaces the training video with a three-step inline guide (Rule 2). A 15-second GIF shows the complete submission flow. The message passes the 30-second response test: a reader can click, submit a test expense, and confirm their account works in under half a minute. Adoption after one week with the new approach: 71%. + +--- + +## Anti-Patterns + +1. **The Open-Ended Ask.** "Let me know your thoughts" or "When are you free?" These phrases feel polite. They are also friction machines. Each one transfers the cognitive burden of structuring a response from the writer to the reader. A constrained alternative -- "Does Tuesday at 2 pm work?" -- reduces the reader's task from composition to selection. + +2. **The Portal Redirect.** Directing readers to log into an external system to complete an action that could have been completed within the message itself. Every redirect -- especially one requiring credentials -- is a cliff that a large percentage of readers will not climb. The DC schools study measured the cliff at 99% attrition for portal-based enrolment. + +3. **The Information Scavenger Hunt.** Asking readers to act but making them search through prior emails, attachments, or external documents to assemble the information needed. If acting on a request requires data, include the data. If the data is too long to include, summarise it and link to the source, but never assume the reader will retrieve it independently. + +4. **The Choice Overload.** Offering six meeting times, twelve plan options, or eight survey response categories when three would suffice. Research consistently shows that excess choice induces decision paralysis. The IRS study on Earned Income Tax Credit applications found that a worksheet with seven eligibility criteria produced a 17% lower response rate than one with two criteria -- despite containing more useful information. + +5. **The Assumed Follow-Through.** Sending a message that requires action "by end of week" without any follow-up mechanism. Present-bias means readers are structurally inclined to defer. A single well-timed reminder -- sent close to the deadline, not at the beginning of the week -- significantly increases completion rates. Research on medical appointment reminders, savings programmes, and child support payments all confirm this effect. A study on voter registration found that the first five reminder mailings each incrementally increased turnout, but the last five of ten had no further effect. In a Kenyan HIV treatment study, weekly reminders improved adherence by 32%, while daily reminders produced no improvement at all -- likely because their frequency caused patients to tune them out. The principle: remind enough to overcome procrastination, but not so much that reminders become noise. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Meeting requests, advisor asks, survey invitations | Every interaction is a cold start. The reader has no relationship-driven reason to tolerate friction. Requests must be answerable in a single action -- one click, one reply, one selection. | +| Validation | Beta user engagement, investor commitment letters, LOI signatures | The stakes of each response rise. Friction audits of high-value requests (signing an LOI, committing capital) reveal surprisingly removable barriers -- a pre-filled signature block, a direct DocuSign link. | +| Early Traction | Customer onboarding, feature adoption, support ticket resolution | Response design shifts from one-to-one to one-to-many. Templates for common action requests (account setup, feedback, renewals) must pass the 30-second test at scale. | +| Growth | Internal process adoption, cross-team coordination, policy compliance | Friction compounds across a growing organisation. A five-step expense process that "only takes three minutes" costs 400 person-hours per year in a 400-person company. Default design and one-step actions become operational priorities. | +| Scale | Automated enrolment flows, renewal campaigns, regulatory filings | Response architecture is embedded in product and operations. A/B testing of default configurations, step counts, and CTA placements becomes a quantitative practice affecting millions of interactions. | + +--- + +## Output Template + +```markdown +# Response Design: [Message / Flow Name] + +## Desired Action +[One sentence: what the reader should do after reading.] + +## Current Friction Map +| Step | Action Required | Est. Time | Drop-off Risk | +|------|----------------|-----------|---------------| +| 1 | [e.g., Open email] | 2 sec | Low | +| 2 | [e.g., Click link] | 3 sec | Medium | +| 3 | [e.g., Log into portal] | 45 sec | High | +| 4 | [e.g., Find and complete form] | 3 min | Very High | + +## 30-Second Response Test +- **Passes?** [Yes / No] +- **Bottleneck:** [The step where the 30-second budget is exceeded] + +## Redesign Strategy +- **Default option:** [If applicable -- what happens if the reader does nothing?] +- **Steps eliminated:** [Which steps were removed and how] +- **Information pre-supplied:** [What data was added to the message to prevent searching] +- **Choice constraints applied:** [Open-ended questions converted to selections] + +## Revised Message +[Full rewrite, structured for minimum friction, annotated with rule numbers] + +## Follow-Up Plan +- **Reminder timing:** [When to send, relative to deadline] +- **Reminder content:** [Abbreviated version restating the ask and the single easiest step] +``` + +--- + +## Related Skills + +- **[Reader Psychology](reader-psychology.md)** -- Explains the cognitive constraints (working memory, present-bias, attention depletion) that make friction so lethal to response rates. +- **[Writing for Navigation](writing-for-navigation.md)** -- Ensures readers can find the call to action in the first place; response-oriented design is ineffective if the request is buried in an unnavigable message. +- **[Writing Effective Emails](writing-effective-emails.md)** -- The inbox is the most common arena for response-oriented writing; email-specific tactics complement the friction-reduction principles here. +- **[Tone and Engagement](tone-and-engagement.md)** -- Tone calibration influences Stage 2 of the reader's triage process, which directly affects whether the reader reaches the call to action at all. +- **[Writing with Purpose](writing-with-purpose.md)** -- Clarifying the writer's goal before drafting is the prerequisite for designing an effective response mechanism. +- **[Cialdini's Influence](../frameworks/cialdini-influence.md)** -- Reciprocity, scarcity, and commitment principles explain the psychology behind why specific friction-reduction techniques increase response rates. diff --git a/plugins/foreman/content/skills/writing/writing-memos-and-reports.md b/plugins/foreman/content/skills/writing/writing-memos-and-reports.md new file mode 100644 index 0000000..784e7b3 --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-memos-and-reports.md @@ -0,0 +1,214 @@ +--- +name: "writing-memos-and-reports" +description: "Provides a systematic approach to structuring memos, reports, and business letters that inform decisions and drive action. Covers the Issue-Solution-Reason summary framework, the Who-Why-What-When-How planning chart, visual aids, three-audience writing, and business letter conventions. Use when drafting board memos, internal recommendations, market analysis reports, strategic proposals, client-facing letters, or any document longer than an email that must survive scrutiny from multiple readers." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - memos + - reports + - business-letters + - document-structure + - executive-summary + - decision-making +related_skills: + - tone-and-engagement + - grammar-and-mechanics + - writing-effective-emails + - writing-performance-reviews +author: "Fatih Guner" +--- + +# Writing Memos and Reports + +Every memo is a decision document. The question is not whether it will influence a decision, but which one -- and whether the writer has been deliberate about the answer. A memo ostensibly about switching paper suppliers is actually a document about cost discipline, vendor relationships, and operational reliability. A report on declining chocolate sales is actually a recommendation to reposition an entire product line. The writers who understand this produce documents that get read, circulated, and acted upon. The writers who do not produce documents that get filed. + +The distinction between the two lies not in the quality of the analysis but in the quality of the structure. A brilliant insight buried in paragraph seven of an unsummarised report is, for all practical purposes, an insight that does not exist. + +--- + +## The Framework + +### The Issue-Solution-Reason Summary + +Every memo and report should open with a summary that answers three questions, in this order: + +1. **Issue:** What is the problem or question, stated so that anyone can understand it? +2. **Proposed Solution:** What do you recommend? +3. **Reason:** Why is this solution preferable to alternatives? + +Consider two approaches to the same recommendation: + +**Weak Summary:** +> "The cell phone changeover that has been proposed should be rejected. For the reasons stated below, the company would not be well served by accepting the proposal." + +**Strong Summary:** +> "Last year, we adopted an officewide policy of issuing cell phones to all executives and sales reps at an annual cost of $58,000. The Persephone company has proposed that we switch to its phones and service at $37,000. The committee recommends rejecting this proposal for four reasons: (1) significantly less coverage in Europe and Asia, (2) our current provider's superior responsiveness, (3) potential costs from dropped calls that dwarf the $21,000 savings, and (4) Persephone's inferior customer service ratings." + +The second version can be fully understood by anyone who reads it, at any time. The first assumes familiarity with context that readers may not have. + +### The Who-Why-What-When-How Planning Chart + +Before writing, answer five questions: + +| Question | Key Point | +|----------|-----------| +| **Who** are you writing for? | Consider your audience's concerns, motivations, and background. | +| **Why** are you writing? | Keep your purpose firmly in mind. Every sentence should advance it. | +| **What** needs saying? | Include only the main points and details that get your message across. | +| **When** are you expecting action? | State your time frame explicitly. | +| **How** will your communication benefit readers? | Make it clear how you are meeting their needs. | + +This chart is not a writing exercise -- it is a thinking exercise. Most poorly structured documents fail not at the writing stage but at the planning stage. The writer who cannot answer these five questions before drafting will not produce a document that answers them after. + +### Writing for Three Audiences + +Every memo and report serves three simultaneous readerships: + +**Primary audience:** Executives who want conclusions, recommendations, and key data. They will read the summary and skim the rest. Write the summary for them. + +**Secondary audience:** Reviewers who may be called in to assess the document's soundness. They will examine your methodology, challenge your assumptions, and check your facts. Write the body for them. + +**Future audience:** Readers two years from now who will need to extract information from a document they did not commission and may lack context for. Write with enough specificity and context that the document stands on its own. + +### Title Selection + +The title or subject line is the document's first promise to the reader. Vague titles break that promise before the reader begins. + +| Weak Title | Strong Title | +|-----------|-------------| +| Subject: Siegelson | Subject: Approval of Siegelson Acquisition | +| Subject: Settlement | Subject: Why We Should Reject Frost's Settlement Offer | +| Subject: Print Run | Subject: Ginsburg Autobiography Print Run | + +Strong titles tell readers both the topic and what they should do about it. + +### Using Graphics and Visual Aids + +When writing about complex information, a well-placed chart or diagram conveys at a glance what paragraphs of prose struggle to communicate. Three principles govern effective visuals: + +- The graphic must illustrate something discussed in the text -- never use decoration for its own sake. +- Place it near the text it supports, preferably on the same page. +- Use legends and labels that readers can grasp without consulting the text. + +Make graphics distinctive and use them sparingly. If every third page contains a chart, the visual emphasis is nullified. + +### Business Letter Conventions + +Business letters, despite their apparent obsolescence, remain necessary for formal situations: correcting vendor errors, recommending job candidates, announcing services, delivering bad news with appropriate gravity. + +**Focus on the reader.** Open with *you*, not *I*. "You might be interested..." rather than "I just thought I'd drop you a note..." + +**Say something substantive.** Replace filler ("I trust this finds you prospering in your personal life...") with genuine content ("I hope your family dodged the fires last week -- which sounded devastating"). + +**Avoid hedging.** Replace "It is with regret that we acknowledge that we do not appear at this time to be in a position to extend an offer of employment" with "We're sorry to say that we aren't now hiring." + +**Ease into bad news.** Open on a genuine positive note, then explain the negative and its reasoning. Readers absorb bad news better when they do not encounter it in the first sentence. + +--- + +## Prompts + +**Prompt 1 -- Memo Structure Builder:** +> I need to write a memo about [describe topic] for [describe audience]. The recommendation is [describe]. Help me structure it using the Issue-Solution-Reason framework. Draft the summary section, then outline the body sections with recommended content for each. Include three supporting arguments and identify the strongest counterargument I need to address. + +**Prompt 2 -- Report Outline Generator:** +> I am preparing a report on [describe topic] for [describe audience]. The report needs to address [describe key questions]. Generate a detailed outline that includes: a summary section written for executives, a body structured for reviewers, and enough context for future readers who lack inside knowledge. Recommend where visual aids would be most effective. + +**Prompt 3 -- Business Letter Drafter:** +> Draft a business letter for the following situation: [describe context -- e.g., declining a proposal, responding to a complaint, recommending a candidate]. The tone should be [describe -- e.g., firm but diplomatic, warm and personal, professional and direct]. The recipient is [describe]. Include a before/after comparison if the letter delivers bad news. + +**Prompt 4 -- Document Audit:** +> Review this memo/report for structural effectiveness. Assess: (1) whether the summary could stand alone as a complete briefing, (2) whether the body supports the summary with evidence, (3) whether the title accurately signals the content and required action, (4) whether a non-expert reader two years from now would understand the document. Provide specific revision recommendations. Document: [paste text] + +--- + +## Use Cases + +**Validation-Stage Startup Writing Its First Board Memo** +A startup preparing for its first advisory board meeting needs to present a recommendation to pivot from B2C to B2B. The founder drafts a five-page narrative that reads like a journal entry -- chronological, discursive, burying the recommendation on page four. After restructuring with the Issue-Solution-Reason framework, the memo opens with a three-sentence summary: the issue (B2C unit economics are unsustainable at current CAC), the solution (pivot to B2B with existing technology), and the reasoning (three enterprise pilots show 4x better margins with 60% lower acquisition costs). The board reads the summary, nods, and spends the meeting discussing implementation rather than deciphering the problem. + +**Growth-Stage Company Producing a Market Analysis Report** +A product team writes a 20-page market analysis for the executive team. The original version opens with four pages of methodology before reaching any findings. The executives, who allocate twenty minutes to each report, never reach the findings. Restructured with the three-audience model: a one-page summary for executives (primary audience), a methodology section for the VP of strategy who will evaluate rigour (secondary audience), and comprehensive data tables with source citations for the analyst who will update the report next quarter (future audience). Every reader gets what they need without wading through content meant for someone else. + +**Scale-Stage Organisation Standardising Memo Templates** +A 1,000-person company discovers that its memos follow no consistent structure. Some open with recommendations; others bury them. Some include summaries; others do not. Readers waste time adapting to each writer's idiosyncratic format. The company adopts a standard memo template based on the Issue-Solution-Reason framework, with required sections for summary, body, and recommendations. Document quality, as measured by decision-maker satisfaction surveys, improves 40% in the first quarter -- not because the analysis improved, but because the presentation did. + +--- + +## Anti-Patterns + +1. **The Summary-Free Report.** A report that plunges into analysis without summarising what it found or recommends. Executives who lack time to read the full document -- which is most of them -- never encounter the conclusion. The report produces analysis without influencing decisions. + +2. **The Vague Title.** "Subject: Q3" tells the reader nothing about content, purpose, or required action. It guarantees the memo will be opened only by people with nothing better to do, which is precisely the audience least likely to act on it. + +3. **Burying the Recommendation.** Presenting all evidence chronologically and revealing the conclusion at the end, as though writing a detective novel. Business readers do not want suspense. They want the answer first and the supporting evidence second. + +4. **Writing for Yourself Instead of the Reader.** Structuring the document in the order you discovered the information rather than the order the reader needs it. The research journey and the presentation of findings are different sequences. The reader does not need to retrace your steps. + +5. **Overloading with Visuals.** Charts on every page dilute the impact of any single chart. Graphics should be deployed sparingly and only when they communicate something more effectively than prose can. A bar chart showing two numbers is not more informative than a sentence. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Advisory board memos and investor updates | Documents are short, high-stakes, and read by people who evaluate the founder's thinking as much as the content. Clarity and structure signal analytical competence. | +| Early Traction | Client proposals and internal recommendations | The company begins producing documents that commit resources. Memos that recommend hiring, spending, or changing direction need rigorous structure to withstand scrutiny. | +| Growth | Cross-functional reports and board materials | Multiple teams produce reports for leadership. Without structural standards, the board receives documents in twenty different formats, wasting cognitive energy on navigation rather than evaluation. | +| Scale | Institutional document standards | Memo and report templates become organisational infrastructure. Style guides, training programmes, and editorial review ensure consistency across hundreds of document authors. | + +--- + +## Output Template + +```markdown +# [Document Title: Specific and Action-Oriented] + +## Summary +**Issue:** [One to two sentences defining the problem or question] + +**Proposed Solution:** [One to two sentences stating the recommendation] + +**Reason:** [Two to four sentences explaining why this solution is preferable] + +## Background +[Context necessary for readers unfamiliar with the topic -- no more than is needed] + +## Analysis +### [Finding/Argument 1] +[Evidence and reasoning] + +### [Finding/Argument 2] +[Evidence and reasoning] + +### [Finding/Argument 3] +[Evidence and reasoning] + +## Counterarguments Considered +[Strongest objection and why the recommendation still holds] + +## Recommendations +1. [Specific action, owner, and timeline] +2. [Specific action, owner, and timeline] + +## Appendix +[Supporting data, methodology, or detailed tables for secondary and future audiences] +``` + +--- + +## Related Skills + +- **[Writing Effective Emails](writing-effective-emails.md)** -- When a message exceeds one screen, it likely belongs in a memo rather than an email; knowing when to switch formats is itself a skill. +- **[Tone and Engagement](tone-and-engagement.md)** -- Reports are particularly susceptible to passive voice and nominalizations; the tone framework provides the diagnostic tools for revision. +- **[Grammar and Mechanics](grammar-and-mechanics.md)** -- Formal documents that persist in the organisational record demand the highest standard of grammatical precision. +- **[Writing Performance Reviews](writing-performance-reviews.md)** -- Performance reviews are a specialised form of the memo, applying the same structural principles to the evaluation of individuals. +- **[Writing for Navigation](writing-for-navigation.md)** -- The navigation architecture of headings, sections, and executive summaries determines whether a multi-page document gets read or abandoned. +- **[Clarity and Concision](clarity-and-concision.md)** -- Long-form documents amplify the cost of verbosity; the concision techniques are essential for keeping reports at a length readers will tolerate. diff --git a/plugins/foreman/content/skills/writing/writing-performance-reviews.md b/plugins/foreman/content/skills/writing/writing-performance-reviews.md new file mode 100644 index 0000000..813f832 --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-performance-reviews.md @@ -0,0 +1,253 @@ +--- +name: "writing-performance-reviews" +description: "Guides the high-stakes process of writing performance appraisals that are specific, fair, legally defensible, and genuinely useful for employee development. Covers the seven evaluation dimensions (attitude, efficiency, human relations, judgment, knowledge, reliability, communication), the spectrum from superb to poor, the discipline of pairing evaluative language with concrete evidence, and the legal implications of imprecise writing. Use when preparing annual or quarterly reviews, designing performance evaluation templates, training first-time managers on review writing, or auditing existing review practices for fairness and consistency." +version: "1.0.0" +category: "writing" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - performance-reviews + - employee-evaluation + - management + - hr-writing + - legal-risk + - feedback + - talent-development +related_skills: + - giving-feedback + - grammar-and-mechanics + - tone-and-engagement + - writing-memos-and-reports +author: "Fatih Guner" +--- + +# Writing Performance Reviews + +A well-written performance review builds a career. A poorly written one invites a lawsuit. Between these extremes lies the vast wasteland of vague, unhelpful evaluations that serve neither the employee nor the organisation: "Meets expectations." "Good team player." "Could improve communication skills." These phrases occupy space on a form without communicating anything that the employee can act upon, the organisation can calibrate against, or a court can interpret as evidence of fair process. The performance review is arguably the highest-stakes document a manager writes, yet it receives less training, less editorial oversight, and less structural rigour than almost any other form of business writing. + +The cost of this neglect is measurable. Vague positive reviews make it nearly impossible to justify promotion decisions when challenged. Vague negative reviews provide no legal foundation for termination. And the employees themselves -- the ostensible audience for the document -- learn nothing from prose that could apply equally to any person in any role. + +--- + +## The Framework + +### The Seven Evaluation Dimensions + +The framework identifies seven aspects of work that performance reviews should address. Not every review covers all seven -- the selection depends on the role and the review period. But the framework provides a comprehensive vocabulary for evaluation. + +**1. Attitude** + +| Level | Descriptors | +|-------|-------------| +| Superb | Shows unwavering commitment; always gives maximal effort; is always friendly and happy to help; always brings out the best in others | +| Good | Shows strong commitment; usually makes a strong effort; is usually friendly and happy to help | +| Acceptable | Shows adequate commitment; makes an effort; is often friendly and happy to help | +| Needs Improvement | Could show more commitment; doesn't always make an effort; is sometimes quarrelsome | +| Poor | Lacks commitment; rarely makes a real effort; is quarrelsome and sometimes even hostile | + +**2. Efficiency** + +| Level | Descriptors | +|-------|-------------| +| Superb | Never wastes time or effort; delegates effectively; always completes tasks on time; manages many projects simultaneously | +| Good | Rarely wastes time; usually delegates appropriately; almost always completes tasks on time | +| Needs Improvement | Sometimes wastes time and effort; tries to do too much without delegating; fails to complete tasks on time | +| Poor | Often wastes time and effort; usually fails to delegate; struggles to manage even one project at a time | + +**3. Human Relations** + +| Level | Descriptors | +|-------|-------------| +| Superb | Demonstrates keen sensitivity to others; participates actively and collegially in meetings; works exceptionally well on teams; relates to customers extremely well | +| Good | Usually demonstrates sensitivity; participates effectively in meetings; works effectively on teams | +| Needs Improvement | Does not always pick up on interpersonal cues; sometimes wastes others' time in meetings; is sometimes motivated more by personal goals than team goals | +| Poor | Rarely pays attention to others' reactions; often wastes others' time; does not work well on teams; often alienates customers | + +**4. Judgment** + +| Level | Descriptors | +|-------|-------------| +| Superb | Makes excellent choices and informed decisions; remains utterly calm and collected in crisis; knows precisely which problems need immediate attention | +| Good | Makes sound choices; remains relatively calm in crisis; generally knows which problems need immediate attention | +| Needs Improvement | Sometimes makes poor choices; sometimes lacks composure in high-pressure circumstances; often doesn't distinguish between urgent and non-urgent | +| Poor | Often makes poor choices and ill-informed decisions; often lacks the calm required in high-pressure circumstances | + +**5. Knowledge** + +| Level | Descriptors | +|-------|-------------| +| Superb | Exceptionally well informed about all aspects of the job; demonstrates extraordinarily comprehensive knowledge; handles complex assignments without supervision | +| Good | Well informed about key aspects; demonstrates thorough knowledge; handles complex assignments with some supervision | +| Needs Improvement | Doesn't fully understand the job; demonstrates less than satisfactory knowledge; sometimes mishandles assignments of moderate complexity | +| Poor | Ill-informed about many aspects of the job; demonstrates inadequate knowledge; mishandles basic assignments | + +**6. Reliability** + +| Level | Descriptors | +|-------|-------------| +| Superb | Always meets deadlines; is unfailingly dependable; achieves excellent results in urgent situations; always delivers on promises | +| Good | Meets deadlines; is highly dependable; achieves good results in urgent situations | +| Needs Improvement | Sometimes fails to meet important deadlines; is sometimes undependable; sometimes fails to deliver on promises | +| Poor | Often fails to meet deadlines; is rarely dependable; can't be counted on to deliver on promises | + +**7. Communication Skills** + +| Level | Descriptors | +|-------|-------------| +| Superb | Writes and speaks with remarkable clarity; never gets bogged down in unnecessary details; has superior communication skills in person and over the phone | +| Good | Writes and speaks clearly; rarely gets bogged down; has sound communication skills | +| Needs Improvement | Sometimes writes and speaks unclearly and with undue complexity; sometimes gets bogged down in unnecessary details | +| Poor | Writes and speaks unclearly; gets bogged down in unnecessary details; fails to communicate effectively | + +### The Cardinal Rule: Pair Every Assessment with Evidence + +A performance descriptor is a hypothesis. Evidence is what makes it credible. + +**Vague (useless):** +> "Lauren shows unwavering commitment." + +**Specific (useful):** +> "When we had several layoffs last June, Lauren remained utterly calm and collected while demonstrating keen sensitivity to those who lost their jobs. She personally conducted exit interviews with each affected team member, ensured their final paycheques were processed within 24 hours, and organised a quiet send-off that preserved the dignity of the departing employees." + +The first version could describe anyone. The second version describes exactly one person doing exactly one set of things. This specificity serves three purposes: it tells the employee precisely what behaviour to continue, it provides the organisation with a defensible record, and it demonstrates that the reviewer was actually paying attention. + +### The Legal Dimension + +Performance reviews are legal documents whether managers intend them as such or not. They are discoverable in litigation, admissible as evidence, and routinely used to support or undermine claims of wrongful termination, discrimination, and retaliation. + +Three legal imperatives for review writers: + +1. **Consistency.** A trail of "exceeds expectations" reviews followed by a sudden termination invites a wrongful-termination claim. If performance is deteriorating, the reviews must reflect the deterioration -- contemporaneously, not retroactively. + +2. **Specificity.** "Poor attitude" is a conclusion. A court will ask: what, specifically, constituted the poor attitude? When did it occur? Was the employee notified? What was the expected standard? If the review cannot answer these questions, the assessment is legally indefensible. + +3. **Fairness.** Applying different evaluative standards to different employees performing the same role -- even unconsciously -- creates exposure to discrimination claims. The seven-dimension framework, applied consistently, provides a structured defence against inconsistency. + +--- + +## Prompts + +**Prompt 1 -- Review Drafter:** +> I need to write a performance review for [describe employee, role, and tenure]. Over the review period, the key observations are: [list 3-5 specific situations, behaviours, and outcomes]. Draft a review that covers the relevant evaluation dimensions, pairs every assessment with the specific evidence I've provided, and maintains a tone that is honest, constructive, and respectful. Include both strengths and areas for development. + +**Prompt 2 -- Vagueness Eliminator:** +> Here is a draft performance review: [paste text]. Identify every instance of vague or unsupported evaluative language. For each, flag the vague phrase, explain why it is insufficient, and suggest a specific revision that pairs the assessment with observable evidence. If evidence is missing, indicate what kind of evidence would be needed. + +**Prompt 3 -- Difficult Review Preparation:** +> I need to write a performance review for an underperforming employee. The situation: [describe specific performance issues with dates and examples]. I need the review to be (1) honest about the performance gaps, (2) specific enough to be legally defensible, (3) constructive enough to give the employee a genuine path to improvement, and (4) documented clearly enough to support further action if improvement doesn't occur. Draft the review with these four objectives in mind. + +**Prompt 4 -- Review Template Designer:** +> Design a performance review template for a [describe company size and stage] company. The template should cover [specify which of the seven evaluation dimensions are most relevant for the roles in the company]. Include structured fields that force reviewers to provide specific evidence for every rating, a self-assessment section for the employee, and a development-plan section that translates the review into forward-looking commitments. + +--- + +## Use Cases + +**Early-Traction Startup Conducting Its First Reviews** +A 15-person startup runs its first performance review cycle. The CEO, having never written a review, produces evaluations that read like casual character references: "Alex is great, super dependable, and the team loves working with him." This is gratifying for Alex but useless for calibration. After applying the seven-dimension framework, the review becomes: "Alex demonstrates exceptional reliability -- he has met every sprint deadline this quarter and was the sole engineer who volunteered for the holiday on-call rotation. His knowledge of our payment infrastructure is comprehensive, and he handles complex debugging assignments without supervision. His area for development is communication: his technical documentation, while accurate, sometimes assumes reader familiarity with the codebase that new team members do not have." Alex now knows what to keep doing and what to develop. + +**Growth-Stage Company Defending a Termination Decision** +A 200-person company terminates an underperforming sales manager. The manager files a wrongful-termination claim, alleging that the termination was discriminatory. The company's defence rests on a trail of performance reviews documenting specific, dated instances of underperformance across three consecutive quarters: missed pipeline targets (with exact numbers), client complaints (with specific dates and descriptions), and failure to implement the agreed-upon improvement plan (with milestone dates and gaps). The reviews, written using the evidence-pairing discipline, provide a documentary foundation that withstands legal scrutiny. A less rigorous review trail -- "needs improvement in sales performance" -- would have been nearly indefensible. + +**Scale-Stage Organisation Calibrating Across Managers** +A 500-person company discovers significant inconsistency in how managers rate performance. One department rates 80% of employees as "superb"; another rates only 15% as such for comparable performance. By standardising on the seven-dimension framework with required evidence for each rating, the company enables meaningful cross-department calibration sessions. Managers must justify their ratings against specific behavioural indicators, reducing the influence of personal bias and relationship dynamics. + +--- + +## Anti-Patterns + +1. **The Recency Trap.** Evaluating an entire year based on the last three weeks because the reviewer kept no notes during the intervening months. Performance reviews require continuous documentation -- not a frantic retrospective the night before the form is due. + +2. **The Halo Effect.** Allowing exceptional performance in one dimension to inflate ratings across all dimensions. An engineer who writes brilliant code but alienates every colleague deserves a "superb" in knowledge and a "needs improvement" in human relations. Conflating the two produces a review that is inaccurate and unhelpful. + +3. **Euphemism as Kindness.** Describing genuine performance problems in language so gentle that the employee does not recognise them as problems. "Could benefit from additional focus on timeliness" does not communicate the same urgency as "Has missed four of the last six project deadlines, resulting in two client escalations." False kindness in reviews is a form of dishonesty that ultimately harms the employee. + +4. **The Copy-Paste Review.** Reusing the same language across multiple employees' reviews, changing only the name. This signals -- accurately -- that the reviewer invested no effort in individualised assessment. It also creates legal exposure if employees compare reviews and find identical language applied to different performance levels. + +5. **Avoiding Negative Feedback Entirely.** Writing exclusively positive reviews for fear of confrontation, then using a sudden termination to address performance issues that were never documented. This pattern is both legally dangerous and managerially irresponsible. The employee never received a genuine opportunity to improve because the written record suggested nothing needed improving. + +6. **Weaponising the Review.** Using the performance review to settle personal grievances, document subjective "attitude" complaints without evidence, or build a paper trail for a predetermined termination. Reviews serve the employee's development and the organisation's record. Using them as a political tool corrodes institutional trust. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | First-time managers writing first reviews | Managers who have never written a review need a framework. Without one, they default to either vague praise or uncomfortable avoidance of constructive feedback. The seven-dimension model provides immediate structure. | +| Growth | Consistency across a growing management layer | With ten or twenty managers writing reviews independently, calibration becomes essential. The framework provides a common vocabulary that enables cross-manager comparison and reduces bias. | +| Scale | Institutional review infrastructure | At scale, performance reviews are embedded in HR systems, tied to compensation decisions, and subject to legal review. Templates, training programmes, and calibration sessions ensure quality at volume. | + +--- + +## Output Template + +```markdown +# Performance Review: [Employee Name] +**Review Period:** [start date] to [end date] +**Reviewer:** [name and title] +**Date:** [review date] + +## Summary Assessment +[2-3 sentences capturing overall performance, key strengths, and primary development areas] + +## Dimension Assessments + +### Attitude +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact that supports this rating] + +### Efficiency +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Human Relations +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Judgment +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Knowledge +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Reliability +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Communication Skills +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +## Key Strengths (with Evidence) +1. [Strength + specific example] +2. [Strength + specific example] + +## Development Areas (with Evidence and Plan) +1. [Area + specific example + agreed-upon improvement action + timeline] +2. [Area + specific example + agreed-upon improvement action + timeline] + +## Goals for Next Review Period +1. [Specific, measurable goal] +2. [Specific, measurable goal] +3. [Specific, measurable goal] + +## Employee Self-Assessment Notes +[Space for employee's own perspective, captured during the review conversation] +``` + +--- + +## Related Skills + +- **[Giving Feedback](../frameworks/giving-feedback.md)** -- The SBI feedback model provides the real-time complement to written performance reviews; reviews document what ongoing feedback conversations have already addressed. +- **[Grammar and Mechanics](grammar-and-mechanics.md)** -- Performance reviews carry legal implications, making grammatical precision a matter of institutional risk, not merely style. +- **[Tone and Engagement](tone-and-engagement.md)** -- The tone of a performance review must balance honesty with respect; the tone framework provides the calibration tools for this balance. +- **[Writing Memos and Reports](writing-memos-and-reports.md)** -- Performance reviews are a specialised memo form; the structural principles of clear titles, up-front summaries, and evidence-based argumentation apply directly. +- **[Radical Candor](../frameworks/radical-candor.md)** -- The balance of caring personally and challenging directly is the tonal foundation for reviews that are both honest and constructive. +- **[Employee Engagement and Retention](../leadership/employee-engagement-retention.md)** -- Reviews are a primary retention lever; how they are written directly affects whether employees feel seen and invested in or evaluated and discarded. diff --git a/plugins/foreman/content/skills/writing/writing-process.md b/plugins/foreman/content/skills/writing/writing-process.md new file mode 100644 index 0000000..4b749fd --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-process.md @@ -0,0 +1,211 @@ +--- +name: "writing-process" +description: "Teaches the MACJ writing process -- Madman, Architect, Carpenter, Judge -- a four-phase method for producing effective business documents by separating idea generation, organisation, drafting, and editing into distinct sequential tasks. Covers brainstorming, outlining in sets of three, speed writing, and disciplined revision. Use when facing writer's block, struggling to organise complex material, drafting reports or proposals, or when any business document feels overwhelming to start." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - process + - drafting + - brainstorming + - outlining + - editing + - productivity + - business-writing +related_skills: + - writing-with-purpose + - revising-and-editing + - clarity-and-concision + - business-writing-for-leaders +author: "Fatih Guner" +--- + +# The Writing Process + +Good writing is controlled schizophrenia. Four distinct personalities live inside every writer, and the quality of the output depends entirely on whether they are allowed to work in sequence or forced to compete simultaneously. The Madman is the wild-eyed gatherer of raw material -- ideas, facts, hunches, contradictions. The Architect imposes order, distilling chaos into structure. The Carpenter builds sentences and paragraphs, hammering prose into shape. The Judge polishes, tightens, and corrects. Let the Madman and the Judge occupy the same room, and the result is paralysis: one generates, the other censors, and nothing gets written. The secret to productive writing is not talent. It is sequencing. + +Betty Sue Flowers, the poet and professor who formalised this framework as MACJ, understood that most writing anxiety stems from attempting all four tasks at once. The moment a writer types a sentence and immediately questions whether it is good enough, the Carpenter and the Judge are fighting for the keyboard. Peter Drucker made the complementary observation that good writing, like good innovation, takes "careful, conscious work, not a flash of genius." The MACJ framework operationalises that insight. + +--- + +## The Framework + +### Phase 1: The Madman (Gathering) + +The Madman gathers material without judgement. Ideas from memory, research, observation, conversations, speculation, and imagination -- all are welcome. The goal is volume, not quality. + +**How to run the Madman phase:** + +- Brainstorm freely. Write down every idea, fact, question, and half-formed thought related to the topic. +- Distinguish facts from opinions. Note sources. Put direct quotes in quotation marks. +- Use a spreadsheet or list with labels indicating the points each piece of evidence supports. +- Do not evaluate. Do not organise. Do not write sentences. The Madman's job is to prevent the problem of "finally thinking of your best point after you've finished and distributed your document." + +The Madman phase pays compound interest. Time invested here prevents hours of staring at a blank screen later. + +### Phase 2: The Architect (Organising) + +The Architect takes the Madman's raw material and imposes structure. The key discipline: **organise in sets of three.** + +A mathematician once observed that there are really only four numbers: one, two, three, and many. Four items overload working memory. One or two points feel underdeveloped. Three is the structural sweet spot for business writing -- substantial enough to be persuasive, concise enough to be memorable. + +**The Architect's method:** + +1. Write down three main points as complete sentences (not topics, not fragments -- full propositions that convey the argument). +2. Arrange them in the most logical order from the reader's perspective. +3. Group supporting material under each point. + +Consider an office manager asked to write a memo about acquiring a new building. The Madman brainstorms a list of fifteen topics -- ownership, maintenance, tax consequences, parking, insurance, signage. The Architect groups these into three categories: tasks for the boss (before acquisition), tasks for the manager (before acquisition), and tasks for the manager (after acquisition). What was an overwhelming list of fifteen items becomes three clear sections, each with three supporting points. + +The Architect's outline is bare-bones -- three sentences and their subordinate groupings. That is all the structure the Carpenter needs. + +### Phase 3: The Carpenter (Drafting) + +The Carpenter writes as quickly as possible. Speed is not sloppiness -- it is strategy. + +**Rules for the Carpenter phase:** + +- **Write against the clock.** Allow 5 to 10 minutes per section (opener, body, closer). Set a timer. +- **Do not edit as you go.** The editorial part of the brain is incompatible with the production part. Letting the Judge kibitz during drafting is multitasking at its worst -- two things done inefficiently rather than one thing done well. +- **Do not wait for inspiration.** After the Madman and Architect have worked, the Carpenter should be primed. Schedule the time, sit down, and begin. +- **Start with whatever section feels most comfortable.** When stuck, skip to another section. If still stuck, say aloud what the passage is trying to convey. Speaking often unlocks the right words. +- **Accept imperfection.** The first draft will be imperfect. That is the point. Perfection is the Judge's job, and the Judge is not invited yet. + +Sentences written at speed tend to be shorter and more natural than sentences laboured over. The draft takes shape before the writer has time to second-guess it. Pain decreases as duration decreases. + +### Phase 4: The Judge (Polishing) + +Once the draft is complete, the Judge takes over. This phase requires as much time as the research and writing phases combined. + +**The Judge works in multiple passes, each focusing on one dimension:** + +- **Pass 1: Accuracy.** Are the facts correct? Are citations precise? +- **Pass 2: Tone.** Does the tone match the purpose and audience? +- **Pass 3: Transitions.** Does one sentence glide into the next without discontinuities? +- **Pass 4: Economy.** Can any words be cut without losing meaning? +- **Pass 5: Grammar and punctuation.** The final mechanical sweep. + +Attempting all five passes simultaneously guarantees that none is done well. Sequential focus produces exponentially better results. + +--- + +## Prompts + +**Prompt 1 -- Madman Brainstorm:** +> I need to write a [document type] about [topic] for [audience]. Help me run the Madman phase: generate a comprehensive, unfiltered list of every point, fact, argument, counter-argument, example, and question that could be relevant. Do not organise or evaluate -- just generate. Include ideas I might not have considered. + +**Prompt 2 -- Architect Outline:** +> Here is my raw brainstorm for a [document type]: [paste Madman output]. Now be the Architect: group this material into three main points, each expressed as a complete sentence. Arrange them in the most logical order from the reader's perspective, and assign supporting material under each point. Identify any gaps where additional Madman work is needed. + +**Prompt 3 -- Carpenter Speed Draft:** +> Here is my three-point outline for a [document type]: [paste Architect output]. Now be the Carpenter: write a rapid, complete first draft. Do not over-polish -- prioritise getting all ideas on paper in a natural, flowing sequence. I will edit later. Include an opener, a body structured around the three points, and a closer. + +**Prompt 4 -- Judge Passes:** +> Here is my first draft of a [document type]: [paste Carpenter output]. Now be the Judge. Run five sequential editing passes and show me the result after each: (1) fact-check and flag anything unverified, (2) evaluate tone against my purpose of [state purpose], (3) improve transitions between paragraphs, (4) cut unnecessary words, (5) correct grammar and punctuation. Show the final polished version. + +--- + +## Use Cases + +**Early-Traction Startup Writing a Series A Memo** + +A founder needs to write a 10-page investment memo but feels overwhelmed by the scope. Applying MACJ: The **Madman** spends two hours gathering material -- market data, customer quotes, revenue figures, competitive analysis, team bios, product roadmap, risk factors. The **Architect** distils this into three core propositions: (1) the market is large and underserved, (2) the product has demonstrated early traction with strong unit economics, (3) the team has a unique right to win. Each proposition gets a supporting evidence cluster. The **Carpenter** drafts each section in timed 10-minute blocks, producing a rough but complete draft in under two hours. The **Judge** spends a full day running multiple editing passes -- tightening prose, verifying data, calibrating tone for a sophisticated investor audience. The final document is coherent, persuasive, and completed in three days rather than the three weeks of anxious procrastination that preceded the MACJ adoption. + +**Growth-Stage Company Producing a Quarterly Board Report** + +A VP of Operations dreads the quarterly board report because it requires synthesising input from six departments. The MACJ framework transforms the process. The **Madman** phase involves collecting raw updates from each department head (structured as bullet points, not prose). The **Architect** organises these into three board-level themes: operational performance, strategic initiatives, and risk factors. The **Carpenter** drafts the narrative in a single sitting, using the outline to maintain momentum. The **Judge** reviews over two days, with each pass focused on a single dimension. The result: a board report that takes three days instead of two weeks, with higher quality because each phase received undivided attention. + +--- + +## Anti-Patterns + +1. **Letting the Judge into the Carpenter's Workshop.** The most destructive anti-pattern. Editing while drafting feels productive but is actually paralysing. Every sentence gets scrutinised before the next one begins, and the draft never gains momentum. The result is either a polished opening paragraph followed by nothing, or a document that took five times longer than necessary. + +2. **Skipping the Architect.** Writers who brainstorm and then draft without organising produce documents that wander. The reader can sense the absence of structure -- ideas repeat, the argument circles back on itself, and the conclusion contradicts the opening. Three sentences of outline prevent hours of structural revision. + +3. **Brainstorming in Sentences.** The Madman should generate topics, fragments, and raw ideas -- not polished prose. Writers who brainstorm in full sentences are unconsciously editing (inviting the Judge early) and constraining their creative range. + +4. **Single-Pass Editing.** The Judge who tries to check facts, improve tone, tighten prose, and fix grammar in one reading will miss errors in every category. Focused sequential passes -- even if each is quick -- produce dramatically better results than one heroic sweep. + +5. **Waiting for Inspiration.** Inspiration is not a prerequisite; it is a byproduct. The Madman and Architect phases generate the raw material that makes the Carpenter productive. Waiting for a "flash of genius" before beginning is waiting for a bus on a train line. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision articulation | The Madman phase is dominated by imagination and analogy rather than data. The Architect must structure a narrative around possibility, not proof. The Carpenter's voice should convey conviction. | +| Validation | Evidence synthesis | The Madman phase becomes research-heavy -- customer interviews, pilot data, market sizing. The Architect organises around evidence categories. The Judge must verify every claim. | +| Early Traction | Multi-document management | Founders write constantly -- investor updates, customer proposals, team memos. MACJ prevents each document from consuming disproportionate time. Templated Architect outlines accelerate repetitive formats. | +| Growth | Delegation of phases | At growth stage, different people can own different phases. A subject-matter expert runs the Madman, a communications lead serves as Architect and Carpenter, and leadership plays Judge. The framework scales because it decomposes writing into separable tasks. | +| Scale | Process standardisation | MACJ can be embedded into organisational writing standards -- requiring outlines before drafts, prohibiting single-pass editing, mandating peer review during the Judge phase. | + +--- + +## Output Template + +```markdown +# MACJ Writing Plan: [Document Title] + +## Purpose +[One sentence: what this document must achieve] + +## Phase 1: Madman Output +### Raw Ideas +- [Idea/fact/question 1] +- [Idea/fact/question 2] +- [...] + +### Sources to Gather +- [ ] [Data point or reference needed] +- [ ] [Interview or input needed] + +## Phase 2: Architect Outline +### Main Point 1: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Main Point 2: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Main Point 3: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Logical Order: [1 → 2 → 3] or [reorder with rationale] + +## Phase 3: Carpenter Schedule +- Opener: [time block] +- Section 1: [time block] +- Section 2: [time block] +- Section 3: [time block] +- Closer: [time block] + +## Phase 4: Judge Passes +- [ ] Pass 1: Accuracy and fact-checking +- [ ] Pass 2: Tone alignment with purpose +- [ ] Pass 3: Transitions and flow +- [ ] Pass 4: Word economy +- [ ] Pass 5: Grammar and punctuation +- [ ] Peer review requested from: [Name] +``` + +--- + +## Related Skills + +- **[Writing with Purpose](writing-with-purpose.md)** -- Purpose must be defined before the Madman begins gathering; without a clear objective, the brainstorm has no anchor. +- **[Revising and Editing](revising-and-editing.md)** -- Expands the Judge phase into a comprehensive revision and editing methodology with concrete before/after examples. +- **[Clarity and Concision](clarity-and-concision.md)** -- The Judge's Pass 4 (word economy) is governed by the principles of concision detailed in this companion skill. +- **[Plain Language and Flow](plain-language-and-flow.md)** -- The Architect phase benefits from the flow and continuity principles that transform a logical outline into prose that reads smoothly. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Daily writing habits for leaders; MACJ provides the process backbone that makes those habits efficient. +- **[Creative Flow and Inspiration](../creative/creative-flow-and-inspiration.md)** -- The Madman phase mirrors the creative practice of receiving inspiration without judgment; both depend on separating generation from evaluation. diff --git a/plugins/foreman/content/skills/writing/writing-with-purpose.md b/plugins/foreman/content/skills/writing/writing-with-purpose.md new file mode 100644 index 0000000..27c0c45 --- /dev/null +++ b/plugins/foreman/content/skills/writing/writing-with-purpose.md @@ -0,0 +1,205 @@ +--- +name: "writing-with-purpose" +description: "Teaches how purpose and audience analysis determine the form, tone, and content of every business communication. Applies the principle that the same facts, addressed to the same reader, produce radically different letters depending on the writer's objective. Use when drafting any business document, preparing investor updates, writing customer communications, crafting fundraising emails, or any situation where the writer is unsure what tone to strike or how to frame a message." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - communication + - purpose + - audience + - tone + - persuasion + - business-writing +related_skills: + - writing-process + - clarity-and-concision + - revising-and-editing + - business-writing-for-leaders +author: "Fatih Guner" +--- + +# Writing with Purpose + +Same facts. Same recipient. Three entirely different letters -- and three entirely different outcomes. A company discovers its landlord has violated the Americans with Disabilities Act during a building renovation. The general counsel flags the issue. Someone must write to the landlord. But *why* are they writing? To gather information, because the landlord is a friend? To demand compliance, because a disabled employee needs access? To terminate the lease, because the relationship has already soured? Each purpose produces a different document in tone, structure, and diction -- even though the underlying facts have not changed by a single comma. + +This is the foundational insight that separates competent business writers from everyone else: purpose is not a detail to consider after the writing begins. Purpose is the architecture that determines everything else. + +--- + +## The Framework + +### Purpose Determines Form + +Before typing a single word, a writer must answer one question with precision: *What do I want the reader to do after reading this?* The answer governs every subsequent decision -- word choice, sentence length, level of formality, degree of directness, and the balance between warmth and firmness. + +Consider the ADA violation scenario across three different purposes: + +| Purpose | Tone | Salutation | Key Move | +|---------|------|------------|----------| +| Gather information (friendly inquiry) | Warm, non-confrontational | "Dear Ann" | Compliments the renovation, raises the issue as a question, closes with a lunch invitation | +| Correct the oversight (firm request) | Professional, measured urgency | "Dear Ann" | Acknowledges the renovation positively, states the legal concern directly, requests assurance of a 60-day fix, mentions regulatory reporting as a consequence | +| Terminate the lease (decisive exit) | Firm, civil, bridge-preserving | "Dear Ms. Reynolds" | States the violation, invokes legal entitlement, serves 30 days' notice, expresses hope for continued goodwill | + +The shift from "Dear Ann" to "Dear Ms. Reynolds" alone signals a tectonic change in intent. Every element -- from the opening pleasantry to the closing line -- serves the purpose. No sentence is neutral. + +### Understanding Your Readers + +Purpose without audience awareness is a monologue. Communication is a two-way exercise, and without understanding reader psychology, even a well-intentioned message lands flat. The critical audience realities are: + +- **Readers are busy.** Ascend the organisational hierarchy and this tendency intensifies. A CEO scanning an inbox has no duty to finish a rambling message. +- **They will not struggle.** At the slightest friction, readers stop trying -- and think less of the writer. +- **They must see the benefit.** The ever-important "what's in it for them" must be visible early, or the message will be ignored. + +### The Buffett Principle + +Warren Buffett, in his preface to the SEC's *Plain English Handbook*, offered a deceptively simple technique for writing to large audiences: "I pretend that I'm talking to my sisters. Though highly intelligent, they are not experts in accounting or finance. They will understand plain English, but jargon may puzzle them." + +The principle: choose a specific, intelligent non-specialist in the audience and write for that person. The resulting prose strikes a balance between sophistication and accessibility that serves everyone. + +### The Goal Discipline: What Do You Want Readers to DO? + +Most writers default to informational writing -- they tell readers what they know. Far fewer practise action-oriented writing -- telling readers what to do with what they know. *Writing for Busy Readers* draws a sharp line between these two modes and argues that the distinction is the single most consequential decision a writer makes before drafting. + +The discipline is simple in principle and difficult in practice: before writing, complete two sentences. First: "The most important thing I want the reader to *understand* is ___." Second: "The most important thing I want the reader to *do* is ___." If the second sentence remains blank, the communication is informational. That is sometimes appropriate -- a market research summary, a background briefing. But if the writer *intended* the reader to act and failed to specify the action, the message will produce understanding without movement. The reader nods and moves on. + +*Writing for Busy Readers* frames this as a design problem, invoking Don Norman's *The Design of Everyday Things*: if a person cannot figure out how to use a door handle, that is the designer's fault, not the user's. If a reader overlooks the writer's intended action, that is the writer's fault. The burden of clarity falls entirely on the author. Writers who do not know their own goals cannot expect readers to infer them -- and when readers are left to interpret what matters, they will frequently interpret wrong. + +The practical implication is that goal-setting is not a one-time exercise but a revision loop. An initial draft often reveals that the writer's stated purpose and actual purpose diverge. The writing process itself clarifies thinking -- as organisational psychologist Adam Grant puts it: "Turning thoughts into words sharpens reasoning. What's fuzzy in your head is clear on the page." Effective writers revise not only for style and structure but for goal alignment, asking on each pass: does every sentence advance the reader toward the intended action? + +| Writing Mode | Writer's Question | Example | +|--------------|-------------------|---------| +| Informational | "What should the reader know?" | "Q3 revenue declined 12% due to customer churn in the enterprise segment." | +| Action-oriented | "What should the reader do?" | "Q3 revenue declined 12% due to enterprise churn. We need board approval by Friday to fund the retention programme outlined in Appendix B." | + +The second version contains the same information as the first. It also contains a verb, a deadline, and a specific request. The difference between a document that informs and a document that moves people is almost always one sentence -- the sentence that states what the writer actually wants. + +### Tailoring the Message + +Audience tailoring goes beyond tone. Consider where readers sit in the organisation, what they are expected to contribute, and what pressures they face. A memo to engineers about a product pivot emphasises technical implications. The same pivot, communicated to investors, emphasises market rationale and unit economics. The facts are identical; the framing is not. + +The writer's job is to answer five questions before writing: + +1. **Who** am I writing for? (Their concerns, motivations, background) +2. **Why** am I writing? (Every sentence should advance this purpose) +3. **What** needs saying? (Only the main points that deliver the message) +4. **When** are actions expected? (State the time frame) +5. **How** does this benefit the reader? (Make the value explicit) + +--- + +## Prompts + +**Prompt 1 -- Purpose Clarification:** +> I need to write a [type of document] to [recipient/audience]. The situation is: [describe the facts]. I have not yet decided what I want this communication to achieve. Help me identify three possible purposes I could have, and for each, show me how the tone, structure, and key message would differ. Then help me choose the purpose that best serves my strategic objectives. + +**Prompt 2 -- Audience Analysis:** +> My company is at the [stage] stage. I need to communicate [topic/news] to [specific audience: investors / team / customers / board / partners]. Profile this audience: what are their likely concerns, priorities, and time constraints? What do they need to hear first? What framing will resonate? Then draft an outline tailored to this audience. + +**Prompt 3 -- Purpose-Tone Calibration:** +> Here is a draft I have written: [paste draft]. My intended purpose is [state purpose] and my audience is [describe audience]. Evaluate whether my tone, structure, and word choices actually serve this purpose, or whether they inadvertently signal a different intent. Identify specific passages where purpose and execution are misaligned and suggest revisions. + +**Prompt 4 -- The Buffett Test:** +> I am writing [document type] that will be read by a diverse audience ranging from [technical specialists] to [non-specialists]. Apply the Buffett "writing to my sisters" test: rewrite my draft so that an intelligent non-specialist can follow every point without jargon, while preserving the substance and precision that specialists expect. Here is my draft: [paste draft]. + +**Prompt 5 -- Goal Extraction and Action Alignment:** +> Here is a draft I have written: [paste draft]. Apply the goal discipline: (1) State in one sentence what the reader is meant to *understand* after reading this. (2) State in one sentence what the reader is meant to *do* after reading this. (3) If the action is missing, unclear, or buried, identify exactly where the draft fails to convert understanding into action. (4) Rewrite the draft so that the intended action is unmistakable -- with a specific verb, a deadline where applicable, and a clear next step. Preserve the informational content but ensure the document moves readers, not merely informs them. + +--- + +## Use Cases + +**Validation-Stage Founder Writing a Rejection to an Investor's Term Sheet** + +A founder has received a term sheet with unfavourable liquidation preferences. The investor is well-connected and may be valuable later. The purpose is not to burn the bridge -- it is to decline this specific offer while keeping the relationship warm. Applying purpose-driven writing, the founder opens with genuine appreciation for the investor's time and interest, acknowledges specific aspects of the term sheet that were attractive, explains concisely why the terms do not align with the company's current needs, and closes with an explicit door-opener for future conversations. The tone is warm, the message is clear, and the strategic relationship is preserved. + +**Growth-Stage CEO Communicating a Pivot to Three Audiences Simultaneously** + +A SaaS company is pivoting from horizontal to vertical. The CEO must write to three audiences: investors (who care about market size and burn rate), the engineering team (who care about technical debt and roadmap), and enterprise customers (who care about continuity and support). Same pivot, three documents. For investors: market opportunity framing, competitive moat, revised projections. For engineers: technical rationale, new architecture direction, timeline. For customers: reassurance, migration plan, dedicated support commitment. The Buffett principle applies to each -- but the "sister" is different every time. + +--- + +## Anti-Patterns + +1. **Writing Before Knowing the Purpose.** The most common failure. Writers open a blank document and begin typing, hoping the purpose will emerge from the prose. It rarely does. The result is a meandering message that the reader cannot act on because the writer could not articulate what action they wanted. + +2. **Confusing Self-Expression with Communication.** The purpose of business writing is to produce a reaction in the reader -- not to document the writer's thought process. A memo that catalogues everything the writer knows about a topic, rather than what the reader needs to know, serves the writer's ego, not the reader's time. + +3. **One Tone for All Audiences.** Sending the same message to investors, employees, and customers is not efficiency -- it is laziness. Each audience has different concerns, different knowledge levels, and different reactions to the same words. "Restructuring" means opportunity to an investor and terror to an employee. + +4. **Burying the Purpose.** Some writers treat the purpose as a conclusion to be earned, placing it at the end of a long preamble. Business readers skim. If the purpose is not visible within the first two sentences, many readers will never find it. + +5. **Letting Tone Undermine Purpose.** A letter meant to preserve a relationship that opens with legal threats. A fundraising email that sounds apologetic. When tone contradicts purpose, the reader receives the tone, not the purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision communication | Purpose is almost always persuasion -- convincing cofounders, early advisors, or pre-seed investors to believe in something that does not yet exist. Tone must balance confidence with intellectual honesty. | +| Validation | Evidence presentation | Purpose shifts toward demonstrating traction. The audience (investors, pilot customers) wants data, not vision. The writer's job is to let evidence speak while framing it strategically. | +| Early Traction | Multi-audience management | The founder now writes to investors, customers, employees, and partners -- often about the same events. Purpose diverges by audience. A single "update" template no longer suffices. | +| Growth | Institutional voice | Communications begin representing the company, not the founder. Purpose must be calibrated for scale -- one email may reach thousands of customers. The Buffett principle becomes essential. | +| Scale | Precision and legal awareness | At scale, every written communication carries reputational and legal weight. Purpose must be defined with precision because ambiguity can trigger regulatory, contractual, or public-relations consequences. | + +--- + +## Output Template + +```markdown +# Communication Purpose Brief + +## Document Type +[Email / Memo / Letter / Report / Announcement] + +## Purpose Statement +[One sentence: "The purpose of this communication is to [verb] so that the reader [desired action/reaction]."] + +## Audience Profile +- **Primary reader(s):** [Who] +- **Their key concern:** [What they care about most] +- **Their knowledge level:** [Expert / Informed / Non-specialist] +- **Their time constraints:** [Seconds / Minutes / Will read in full] + +## The Buffett Test +- **My "sister" for this audience:** [Specific person or archetype] +- **Jargon to eliminate:** [List] +- **"What's in it for them" statement:** [One sentence] + +## Tone Calibration +- **Warmth level:** [Warm / Professional / Formal / Firm] +- **Directness level:** [Indirect / Measured / Direct / Blunt] +- **Formality markers:** [First name / Title / Salutation style] + +## Structure +1. **Opening** (purpose visible in first two sentences): [Draft] +2. **Body** (evidence, context, or rationale): [Key points] +3. **Close** (desired action, next steps, relationship signal): [Draft] + +## Pre-Send Checklist +- [ ] Purpose is stated or unmistakable within the first paragraph +- [ ] Every sentence advances the purpose +- [ ] Tone matches the intent (no contradictions) +- [ ] "What's in it for the reader" is visible +- [ ] No jargon the audience would not understand +- [ ] Appropriate level of formality for the relationship +``` + +--- + +## Related Skills + +- **[Writing Process](writing-process.md)** -- Purpose is the prerequisite; process is the execution. Once purpose is clear, the MACJ framework provides the method for drafting. +- **[Clarity and Concision](clarity-and-concision.md)** -- A clear purpose demands clear prose; wordiness and ambiguity undermine even the most well-defined intent. +- **[Plain Language and Flow](plain-language-and-flow.md)** -- The Buffett principle connects directly to plain-language techniques that make writing accessible to diverse audiences. +- **[Reader Psychology](reader-psychology.md)** -- Purpose defines who the reader is; reader psychology explains how that reader processes information and makes triage decisions. +- **[Business Writing for Leaders](../leadership/business-writing-for-leaders.md)** -- Provides daily writing practices for leaders; this skill supplies the foundational technique for determining what to say and how to say it. +- **[Writing for Response](writing-for-response.md)** -- When the purpose requires reader action, the friction-reduction techniques transform intent into measurable response rates. diff --git a/plugins/foreman/content/solo-mode/SOLO.md b/plugins/foreman/content/solo-mode/SOLO.md new file mode 100644 index 0000000..033fb7c --- /dev/null +++ b/plugins/foreman/content/solo-mode/SOLO.md @@ -0,0 +1,244 @@ +# Solo Mode — Orchestrator Operating Manual + +Capacity rule: measure the founder's workload before promising time savings. Do not assume contractor budget or automation suitability. Start with one measured routine and one bounded improvement; do not promise 10–15 saved hours from an unmeasured intervention. + +Solo mode adapts the entire Foreman system for solopreneurs: individuals who are the company. No co-founder, no team, no board of directors, possibly no external investors. The business is an extension of one person's capabilities, decisions, and constraints. Every skill, diagnostic, playbook, template, and hook in the system was designed with the assumption that a founder operates within a multi-person structure — reporting to a board, delegating to a team, pitching to investors. Solo mode removes those assumptions without removing the frameworks. The intellectual architecture remains intact. The application context shifts. + +--- + +## Why Solo Mode Exists + +Foreman's default mode assumes a startup founder scaling a venture-backed company. That founder has a team to delegate to, a board to report to, investors to satisfy, and co-founders to negotiate with. Roughly half of all new businesses are single-person operations. These solopreneurs face the same strategic challenges — pricing, positioning, competition, growth — but through a fundamentally different lens. They do not need advice on board formation. They need advice on making the decision that a board would normally pressure-test. They do not need a team health check. They need a personal sustainability check that prevents burnout from carrying every function alone. + +Solo mode exists because the frameworks are universal; the application is not. + +--- + +## Activation and State + +Solo mode is stored in the identity layer of memory as `mode: solo`. When active, the orchestrator loads this file at session start and applies all behavioral modifications described below. Solo mode persists across sessions until explicitly deactivated. + +```yaml +# In identity.yaml +mode: solo +mode_activated: 2026-03-26 +``` + +The orchestrator checks `identity.mode` during Phase 1 (Input Reception and Context Retrieval). If `mode == solo`, the six behavioral changes below govern all subsequent routing, skill application, diagnostic interpretation, and output formatting. + +--- + +## Behavioral Change 1: Stage Adaptation + +Solo businesses often do not follow the five-stage progression (idea, validation, early-traction, growth, scale) in the same way venture-backed startups do. A solopreneur may remain at early-traction indefinitely by design — not from failure, but from deliberate lifestyle calibration. The stage system still applies, but interpretation shifts. + +| Stage | Default Interpretation | Solo Interpretation | +|-------|----------------------|---------------------| +| `idea` | Pre-product, exploring market | Pre-revenue, testing whether this idea can sustain one person | +| `validation` | Confirming PMF with early users | Confirming that paying customers exist and will pay enough to replace salary income | +| `early-traction` | Growing user base, building team | Generating consistent revenue as a solo operator, establishing systems that do not require headcount | +| `growth` | Scaling team and revenue aggressively | Increasing revenue or margin without proportional time increase; leveraging automation, pricing, or productization | +| `scale` | Institutional scaling, governance, Series B+ | Building assets that generate revenue independently of the solopreneur's hourly involvement; considering first hires or acquisition | + +When applying stage-specific guidance within any skill, use the solo interpretation column. A solopreneur at "growth" is not hiring a VP of Sales — they are systematizing their sales process so it runs with less of their time. + +--- + +## Behavioral Change 2: Audience Remapping + +The output template system serves five audiences: `investor`, `board`, `team`, `client`, `self`. In solo mode, three of these audiences either do not exist or require fundamental reframing. + +| Default Audience | Solo Equivalent | Routing Rule | +|------------------|----------------|--------------| +| `investor` | `self-funding-analysis` | Reframe all investor-facing outputs as personal financial analysis. Replace "investor returns" with "personal income sustainability." Replace "fundraising narrative" with "business viability assessment." If the solopreneur does have investors (angels, bootstrapping loans), note this explicitly in memory and use a hybrid approach. | +| `board` | `mentor-advisor` | Replace board-facing outputs with mentor or accountability partner briefs. Strip governance language. Replace "board resolution" with "decision rationale." Replace "quarterly board review" with "quarterly self-review shared with mentor." | +| `team` | `systems-and-processes` | Replace team-facing outputs with process documentation and system design. Where the default creates alignment documents for humans, solo mode creates standard operating procedures for the solopreneur's own reference or for contractors and AI tools. | +| `client` | `client` (unchanged) | Client-facing outputs remain identical. Solopreneurs serve clients the same way teams do. | +| `self` | `self` (unchanged) | Self-facing outputs are already personal. In solo mode, these become the primary output audience. Default to `self` when no audience is specified. | + +When the orchestrator detects an audience request, apply this mapping before delegating to the output-agent. If the entrepreneur says "prepare this for my board," the orchestrator should respond: "Solo mode is active. You do not have a board. Would you like this formatted for a mentor or accountability partner, or as a personal decision rationale?" + +--- + +## Behavioral Change 3: Skill Relevance Scoring + +Not all 158 skills are equally useful to a solopreneur. Skills about team dynamics, board governance, and organisational culture become less directly applicable. Skills about personal productivity, clear thinking, negotiation, writing, and creative practice become more central. + +The orchestrator loads `solo-skill-relevance.yaml` when solo mode is active. This file assigns a relevance tier to every skill: `critical`, `high`, `moderate`, or `low`. The tiers affect routing as follows: + +- **`critical`** — Prioritize in hook matching. When multiple skills could apply, prefer critical-tier skills. Surface proactively in recommendations. +- **`high`** — Normal routing priority. Apply when matched by hooks or diagnostics. +- **`moderate`** — Apply only when explicitly requested or when the specific framework is clearly the best fit. Add a reframing note explaining how the solopreneur should adapt the team-oriented aspects. +- **`low`** — Do not route to automatically. If explicitly requested, apply with a prominent reframing note. Suggest alternative critical or high-tier skills that address the underlying need. + +Example: If a solopreneur's input triggers `team-hook`, the orchestrator should not route to `tuckman-team-stages` (low relevance). Instead, recognize that the solopreneur may be struggling with contractor management, isolation, or wearing too many hats, and route to skills like `eisenhower-matrix`, `stoic-fortitude-and-resilience`, or `focus-and-priority-management`. + +--- + +## Behavioral Change 4: Diagnostic Adaptation + +Several diagnostics assume team or organisational context that does not exist for solopreneurs. The orchestrator loads `solo-adaptations.yaml` for diagnostic modifications. + +Adaptation types: +- **`as-is`** — Diagnostic works without modification. Example: `pricing-diagnosis`, `competitive-threat-diagnosis`. +- **`reframe`** — Diagnostic is relevant but questions and routing need solo context. Example: `communication-breakdown-diagnosis` becomes about client communication and self-clarity, not internal team alignment. +- **`skip`** — Diagnostic is irrelevant in solo context. Example: `team-dysfunction-diagnosis` — there is no team. If the solopreneur's input would normally trigger this diagnostic, reroute to a more appropriate one. + +When a diagnostic is marked `skip`, the orchestrator must identify the underlying need and reroute. A solopreneur saying "nothing is working and I feel stuck" should not trigger `team-dysfunction-diagnosis` — it should trigger `decision-paralysis-diagnosis` or `strategic-drift-diagnosis`. + +--- + +## Behavioral Change 5: Playbook Adaptation + +Playbooks chain multiple skills into sequences. Some sequences include steps that require a team or board. In solo mode, these steps are either replaced with solo equivalents or skipped with explanation. + +The orchestrator loads playbook adaptations from `solo-adaptations.yaml`. Each playbook is marked: +- **`as-is`** — All steps work for solopreneurs. +- **`reframe`** — Some steps need solo context. The playbook-runner-agent adds a reframing note before each affected step. +- **`skip`** — The entire playbook is irrelevant for solopreneurs. If triggered, suggest alternative playbooks or individual skills. + +For reframed playbooks, each adapted step includes a specific instruction. Example: In the `fundraising-playbook`, the step "Prepare for term sheet negotiation" becomes "Prepare for loan terms, grant applications, or revenue-based financing negotiation." The skill applied (`competitive-negotiation`) remains the same — only the application context changes. + +--- + +## Behavioral Change 6: Template Adaptation + +Output templates reference audiences, stakeholders, and organizational structures that may not exist for solopreneurs. The output-agent applies template-level modifications when solo mode is active. + +Rules: +- Templates in `self/` — use as-is; these are already personal. +- Templates in `client/` — use as-is; client relationships are unchanged. +- Templates in `investor/` — reframe per audience mapping (see Behavioral Change 2). Replace investor-specific metrics framing with personal financial health framing. +- Templates in `board/` — reframe as mentor briefs or personal governance documents. +- Templates in `team/` — reframe as process documentation, contractor briefs, or personal operating procedures. + +Specific template reframing instructions are defined in `solo-audience-map.yaml`. + +--- + +## Voice and Tone in Solo Mode + +The default Foreman voice is institutional and analytical — appropriate for a founder navigating organizational complexity. In solo mode, the voice retains its analytical precision but shifts in three ways: + +**1. More direct and personal.** Replace third-person organizational framing with second-person direct address where appropriate. Instead of "The leadership team should consider..." use "Consider whether..." Instead of "Align your team around..." use "Commit to..." + +**2. Acknowledge the weight of solo operation.** Solopreneurs carry every function: sales, product, operations, finance, strategy. The system should recognize this without patronizing. When a diagnostic reveals that the solopreneur is attempting to do everything at once, name it directly: "You are running sales, product, and operations simultaneously. The Eisenhower Matrix is not optional for you — it is structural." + +**3. No false urgency about hiring.** The default system frequently recommends "bring someone on to handle this" as a solution. In solo mode, that recommendation is restricted to `scale` stage only and framed as a choice, not an imperative. At all other stages, the system prioritizes systems, automation, outsourcing to contractors, and deliberate scope reduction over headcount. + +What the voice never does in solo mode: +- Suggest the solopreneur is doing something wrong by operating alone +- Frame solo operation as a temporary condition to be outgrown +- Recommend hiring as a default solution to capacity problems +- Use "your team" when there is no team +- Reference board meetings, all-hands, one-on-ones, or other team rituals without reframing + +--- + +## Interaction with Industry Packs + +Solo mode and industry packs operate on orthogonal axes and combine without conflict. Solo mode filters WHAT content is shown — audience remapping, skill relevance scoring, diagnostic adaptation. Industry packs add SECTOR DEPTH to that filtered content — sector-specific benchmarks, anti-patterns, diagnostic rules, and template fields. + +When both are active, the solopreneur receives sector-specific, solo-adapted guidance. A SaaS solopreneur gets SaaS churn benchmarks AND solo-appropriate audience framing. A D2C solopreneur gets consumer acquisition metrics AND personal capacity constraints acknowledged. The industry pack enriches the content; solo mode shapes the delivery. + +The orchestrator applies both layers during Phase 1: load the industry pack overlay from `memory.company.sector`, then apply solo mode filters on top. Neither layer overrides the other. Solo mode may remap audiences (investor becomes self-funding-analysis), and the industry pack's template adaptations apply to whichever audience the solo layer selects. + +--- + +## What Solo Mode Does NOT Change + +Frameworks are frameworks. Porter's Five Forces analyzes competitive dynamics regardless of whether the company has 1 person or 10,000. The SWOT matrix, the Eisenhower Matrix, the Business Model Canvas — these are intellectual tools whose logic is independent of company size. + +Solo mode does not alter: +- **Framework definitions.** The core content of every skill file remains unchanged. +- **Framework logic.** The analytical steps, the models, the matrices — all identical. +- **Anti-pattern sections.** Common mistakes apply universally. +- **Quality standards.** The same rigor is expected from solo analysis as from team-supported analysis. + +Solo mode alters only: +- **Application context.** Who does the work, who reviews it, who acts on it. +- **Routing priority.** Which skills surface first for solo problems. +- **Audience framing.** Who the output is for. +- **Step instructions.** How playbook steps reference the executor. +- **Diagnostic questions.** Which triage paths are relevant. + +--- + +## Routing Examples: Normal vs. Solo Mode + +### Example 1: "I need to figure out my pricing" + +**Normal mode:** Hook: `revenue-and-sales-hook`. Diagnostic: `pricing-diagnosis`. Skills: `four-ps-marketing`, `business-model-canvas`. Output: `unit-economics-snapshot` (investor audience), `action-plan` (team audience). + +**Solo mode:** Hook: `revenue-and-sales-hook` (unchanged). Diagnostic: `pricing-diagnosis` (as-is — pricing works the same). Skills: `four-ps-marketing`, `business-model-canvas` (unchanged). Output: `unit-economics-snapshot` reframed as personal income sustainability analysis (self audience), `action-plan` reframed as personal implementation checklist (self audience). The output-agent strips investor-facing language ("defensible to VCs") and replaces it with personal financial framing ("sustains your target income"). + +### Example 2: "My team isn't working" + +**Normal mode:** Hook: `team-hook`. Diagnostic: `team-dysfunction-diagnosis`. Skills: `tuckman-team-stages`, `psychological-safety`, `belbin-team-roles`. Playbook: `team-rebuild-playbook`. Output: `team-health-check`, `feedback-360-template`. + +**Solo mode:** The orchestrator intercepts this pattern. There is no team. The system asks a clarifying question: "Solo mode is active. Are you referring to contractors or freelancers you work with, or are you describing a feeling of being stuck and overwhelmed in your own work?" If contractors: route to `negotiation-mindset-and-self`, `connecting-with-people`, and `delivering-the-deal` with contractor management framing. If personal overwhelm: route to `stoic-fortitude-and-resilience`, `eisenhower-matrix`, `focus-and-priority-management`, and `leader-resilience-and-wellbeing`. + +### Example 3: "I need to prepare for my board meeting" + +**Normal mode:** Hook: `leadership-hook`. Skills: `strategic-thinking-and-alignment`, `managing-up`. Output: `board-meeting-agenda`, `quarterly-strategic-review`. + +**Solo mode:** The orchestrator responds: "Solo mode is active. You do not have a board. Would you like to prepare a structured self-review of your business strategy, or are you meeting with a mentor or advisor?" If self-review: route to `leader-self-reflection`, `strategic-thinking-and-alignment`. Output: `annual-review-and-planning` or `weekly-ceo-review` (self audience). If mentor meeting: route to the same skills but output a condensed brief adapted from `quarterly-strategic-review` with mentor framing. + +### Example 4: "Should I raise funding?" + +**Normal mode:** Hook: `fundraising-hook`. Diagnostic: `fundraising-diagnosis`. Playbook: `fundraising-playbook`. Output: `fundraising-deck-outline`, `unit-economics-snapshot`. + +**Solo mode:** Hook: `fundraising-hook` (unchanged — the question is valid). Diagnostic: `fundraising-diagnosis` reframed — triage questions shift from "are you ready for institutional capital" to "do you need external capital, and if so, what kind suits a solo business?" Revenue-based financing, SBA loans, grants, and bootstrapping are foregrounded over venture capital. Skills: `business-model-canvas` (unchanged), `evaluating-options` (for the funding decision itself), `negotiation-mindset-and-self` (for any capital negotiation). Output: personal funding analysis (self audience) rather than investor-facing materials. + +### Example 5: "I feel completely overwhelmed" + +**Normal mode:** Hook: `personal-growth-hook`. Skills: `leader-resilience-and-wellbeing`, `stoic-emotional-mastery`, `focus-and-priority-management`. Output: `founder-mental-health-check`, `weekly-ceo-review`. + +**Solo mode:** Same hook, same skills, but elevated priority. The orchestrator adds `eisenhower-matrix` and `wanting-what-matters` to the skill set. The output-agent uses `founder-mental-health-check` as-is (already self-focused) and adds a "solo sustainability assessment" framing note. The voice is more direct: "You are carrying every function of this business. That is not a character flaw — it is a structural constraint. The question is not whether you can handle it, but which parts you should stop handling." + +--- + +## Memory Layer Modifications + +When solo mode is active, the company layer of memory (`company.yaml`) interprets certain fields differently: + +| Field | Default | Solo | +|-------|---------|------| +| `team_size` | Headcount | Always `1`; may include `contractors: N` as a separate field | +| `funding.raised` | External capital raised | Personal capital invested + any external funding | +| `funding.runway_months` | Months before cash runs out | Months of personal savings + business revenue before financial stress | +| `funding.next_round` | Planned fundraising | Not applicable unless actively seeking external capital | +| `business_model` | Revenue model | Revenue model + personal income extraction method | +| `key_challenges` | Company challenges | Business challenges interleaved with personal capacity constraints | + +The identity layer gains the `mode: solo` field. No other identity fields change — the solopreneur's name, background, communication preferences, strengths, and weaknesses are captured identically. + +--- + +## Research in Solo Mode + +Solo entrepreneurs conduct all research themselves -- there is no team to delegate data-gathering to. When research guides are recommended (via `/research` or by agent suggestions), solo mode applies four adaptations: + +1. **Time estimation adjusted upward.** Solo research takes approximately 1.5x the estimated time, since no parallel work streams exist. The system displays the adjusted estimate. +2. **Prioritization guidance.** When multiple research tasks are recommended, the system ranks them: "Which of these research tasks gives the most insight per hour of your time?" +3. **Shortcut suggestions.** Each recommendation includes a minimum viable version: "If you can only do ONE thing, do this." +4. **Tool bias toward free and low-cost options.** Solo mode deprioritizes research methods that require paid tools or large sample sizes, favouring scrappy, bootstrapper-friendly approaches. + +--- + +## Orchestrator Checklist — Solo Mode Active + +At session start, when `identity.mode == solo`: + +1. Load this file (`solo/SOLO.md`). +2. Load `solo/solo-skill-relevance.yaml` for routing priority adjustments. +3. Load `solo/solo-audience-map.yaml` for output template remapping. +4. Load `solo/solo-adaptations.yaml` for diagnostic, playbook, and hook modifications. +5. Apply audience remapping to all output-agent delegations. +6. Apply skill relevance scoring to all hook-matching and skill-selection decisions. +7. Apply diagnostic adaptations when routing through the diagnostic-agent. +8. Apply playbook adaptations when delegating to the playbook-runner-agent. +9. Apply voice modifications to all generated text. +10. Default output audience to `self` when no audience is specified. +11. Never reference team, board, or investors as assumed entities. +12. When the solopreneur's input implies organisational structures that do not exist, ask a clarifying question before routing. diff --git a/plugins/foreman/content/solo-mode/solo-adaptations.yaml b/plugins/foreman/content/solo-mode/solo-adaptations.yaml new file mode 100644 index 0000000..015595e --- /dev/null +++ b/plugins/foreman/content/solo-mode/solo-adaptations.yaml @@ -0,0 +1,396 @@ +# Solo Adaptations — Diagnostics, Playbooks, and Hooks +# +# Defines how each diagnostic, playbook, and hook behaves differently +# when solo mode is active. The orchestrator and specialist agents +# load this file at session start. +# +# Adaptation types: +# as-is — Works without modification for solopreneurs. +# reframe — Relevant but requires changed questions, routing, or step instructions. +# skip — Irrelevant in solo context. Reroute to alternative. + +# ───────────────────────────────────────────── +# DIAGNOSTIC ADAPTATIONS (20 diagnostics) +# ───────────────────────────────────────────── + +diagnostic_adaptations: + + - name: "cofounder-conflict-diagnosis" + adaptation: "skip" + reason: "No co-founder. Solopreneurs do not have co-founder conflicts." + reroute: "If the solopreneur describes conflict with a business partner, contractor, or key client, route to negotiation-stuck-diagnosis or partnership-diagnosis instead." + + - name: "communication-breakdown-diagnosis" + adaptation: "reframe" + reason: "Internal communication breakdown assumes a team. Reframe as client communication failure or personal clarity deficit." + changes: + - "Replace 'Is your team aligned on goals?' with 'Are your clients clear on scope, timeline, and deliverables?'" + - "Replace 'Are departments communicating effectively?' with 'Are you communicating consistently across all client relationships?'" + - "Replace 'Is there a single source of truth?' with 'Do you have documented processes that prevent miscommunication with clients and contractors?'" + - "Route to writing skills (clarity-and-concision, writing-effective-emails) rather than organisational-culture or psychological-safety." + + - name: "competitive-threat-diagnosis" + adaptation: "as-is" + reason: "Competitive threats affect solo businesses identically. Larger competitors are in fact a more severe threat to solopreneurs who lack resources to respond." + + - name: "culture-erosion-diagnosis" + adaptation: "skip" + reason: "Culture requires multiple people. A one-person business has values and brand identity, not organizational culture." + reroute: "If the solopreneur describes feeling disconnected from their work or losing motivation, route to strategic-drift-diagnosis or decision-paralysis-diagnosis. For brand integrity concerns, route to competitive-threat-diagnosis." + + - name: "customer-churn-diagnosis" + adaptation: "as-is" + reason: "Customer churn is equally relevant to solo businesses. Retention dynamics, satisfaction measurement, and churn root causes apply without modification." + + - name: "decision-paralysis-diagnosis" + adaptation: "reframe" + reason: "Decision paralysis is more acute for solopreneurs — there is no team, board, or co-founder to break ties or pressure-test options." + changes: + - "Replace 'Have you consulted your leadership team?' with 'Have you discussed this decision with a mentor, advisor, or trusted peer?'" + - "Replace 'Is the decision blocked by organizational politics?' with 'Is the decision blocked by fear of making the wrong choice alone?'" + - "Add triage question: 'Are you delaying because the decision is genuinely complex, or because there is no one to share the responsibility with?'" + - "Elevate routing priority for thinking/enemies-of-clear-thinking and decisions/tough-decision-situations." + + - name: "fundraising-diagnosis" + adaptation: "reframe" + reason: "Solopreneurs may seek funding but the types and dynamics differ fundamentally from venture fundraising." + changes: + - "Replace 'Are you ready for institutional capital?' with 'Do you need external capital, and if so, what kind suits a solo business?'" + - "Replace 'Can you articulate unit economics for VCs?' with 'Can you articulate whether the business generates enough revenue to sustain your desired income?'" + - "Add triage path for bootstrapping assessment: 'Have you exhausted revenue-first options before seeking external capital?'" + - "Add funding type classification: revenue-based financing, SBA/government loans, grants, angel investment, or personal savings allocation." + - "Replace 'Have you identified your target investors?' with 'Have you identified the right funding mechanism for your business model and lifestyle goals?'" + - "Route to evaluating-options skill for the funding decision itself before routing to any fundraising execution." + + - name: "growth-stall-diagnosis" + adaptation: "reframe" + reason: "Growth stalls for solo businesses often have a different root cause: personal capacity ceiling, not product-market or go-to-market failure." + changes: + - "Add triage question: 'Is growth limited by market demand or by your personal capacity to deliver?'" + - "Add triage path for capacity constraint: if the solopreneur is the bottleneck, route to eisenhower-matrix and focus-and-priority-management before market-facing frameworks." + - "Replace 'Is your sales team executing?' with 'Is your sales process systematized or dependent on your personal availability?'" + - "Replace 'Is your product team shipping?' with 'Are you shipping consistently, or are operational demands consuming your development time?'" + + - name: "hiring-diagnosis" + adaptation: "reframe" + reason: "Solopreneurs do not hire employees, but they do engage contractors, freelancers, and agencies. The diagnosis reframes around contractor selection and management." + changes: + - "Replace 'hiring' with 'contractor engagement' throughout." + - "Replace 'Are you attracting quality candidates?' with 'Are you finding reliable contractors who deliver quality work?'" + - "Replace 'Is your employer brand strong?' with 'Are you a client that good contractors want to work with?'" + - "Replace 'Are you retaining new hires?' with 'Are your contractor relationships stable and repeatable?'" + - "Route to delivering-the-deal and connecting-with-people rather than belbin-team-roles or tuckman-team-stages." + + - name: "innovation-drought-diagnosis" + adaptation: "reframe" + reason: "Innovation drought for solopreneurs is often creative block or routine entrapment rather than organizational inertia." + changes: + - "Replace 'Is your R&D pipeline healthy?' with 'When did you last develop or test a new offering, process, or revenue stream?'" + - "Replace 'Is the organization too risk-averse?' with 'Are you avoiding new experiments because the current workload leaves no space for them?'" + - "Elevate creative skills (creative-obstacles, creative-flow-and-inspiration) in the routing priority over organizational innovation frameworks." + + - name: "leadership-crisis-diagnosis" + adaptation: "reframe" + reason: "The solopreneur has no leadership team to be in crisis. Reframe as a personal effectiveness or confidence crisis." + changes: + - "Replace 'Is your leadership team aligned?' with 'Do you feel confident in your direction and ability to execute?'" + - "Replace 'Is there a succession concern?' with 'Are you questioning whether you should continue in this business?'" + - "Replace 'Has trust broken down between leadership and the organization?' with 'Has your confidence in your own judgment eroded?'" + - "Route to leader-self-reflection, emotional-courage, and stoic-control-and-clarity rather than organisational-culture or leadership-pipeline." + + - name: "market-entry-diagnosis" + adaptation: "as-is" + reason: "Market entry analysis applies identically to solo businesses. The frameworks (Porter's Five Forces, Blue Ocean) work at any company size." + + - name: "negotiation-stuck-diagnosis" + adaptation: "as-is" + reason: "Negotiation dynamics are interpersonal, not organizational. The solopreneur negotiates directly — the diagnosis applies without modification." + + - name: "operational-chaos-diagnosis" + adaptation: "reframe" + reason: "Operational chaos for solopreneurs is personal system failure, not organizational breakdown." + changes: + - "Replace 'Are your processes documented?' with 'Do you have personal standard operating procedures for recurring tasks?'" + - "Replace 'Is there accountability across teams?' with 'Do you have a system for tracking commitments and deadlines?'" + - "Replace 'Is your operations team staffed adequately?' with 'Are you trying to do more than one person reasonably can?'" + - "Route to eisenhower-matrix, focus-and-priority-management, and kaizen-bpr rather than team management frameworks." + + - name: "partnership-diagnosis" + adaptation: "as-is" + reason: "Partnership dynamics apply to solopreneurs engaging with other businesses, referral partners, or strategic alliances." + + - name: "pricing-diagnosis" + adaptation: "as-is" + reason: "Pricing strategy is identical for solo businesses. The solopreneur sets prices, evaluates margins, and responds to market signals the same way." + + - name: "product-market-fit-diagnosis" + adaptation: "as-is" + reason: "Product-market fit applies regardless of company size. The solopreneur's offering either fits the market or it does not." + + - name: "revenue-diagnosis" + adaptation: "reframe" + reason: "Revenue diagnostics apply but the context shifts — the solopreneur's revenue is also their personal income." + changes: + - "Add triage question: 'Is revenue insufficient for business sustainability, for your personal income needs, or both?'" + - "Replace 'Is your sales team executing the pipeline?' with 'Is your sales process generating consistent leads and conversions?'" + - "Add personal income lens: 'What is your effective hourly rate? Is it above or below what you could earn as an employee?'" + - "Route to four-ps-marketing and business-model-canvas with explicit attention to personal income extraction." + + - name: "strategic-drift-diagnosis" + adaptation: "reframe" + reason: "Strategic drift for solopreneurs often manifests as 'saying yes to everything' rather than organizational mission creep." + changes: + - "Replace 'Has the company's strategy diverged from its stated mission?' with 'Are you spending time on work that does not align with your core offering or income goals?'" + - "Replace 'Are different divisions pursuing conflicting strategies?' with 'Are you pursuing too many directions simultaneously?'" + - "Add triage question: 'Can you articulate, in one sentence, what your business does and for whom? If not, strategic drift is likely.'" + - "Route to wanting-what-matters and focus-and-priority-management alongside strategic frameworks." + + - name: "team-dysfunction-diagnosis" + adaptation: "skip" + reason: "No team exists. Team dysfunction diagnosis is structurally inapplicable." + reroute: "Determine the underlying need. If the solopreneur describes frustration with contractors, route to negotiation-stuck-diagnosis. If they describe personal overwhelm or burnout, route to operational-chaos-diagnosis or decision-paralysis-diagnosis. If they describe isolation, route to leader-resilience-and-wellbeing and meeting-the-right-people." + +# ───────────────────────────────────────────── +# PLAYBOOK ADAPTATIONS (20 playbooks) +# ───────────────────────────────────────────── + +playbook_adaptations: + + - name: "acquisition-evaluation-playbook" + adaptation: "reframe" + reason: "Solopreneurs occasionally acquire businesses, client lists, or product assets. The evaluation logic applies but governance and integration steps change." + step_changes: + - step: "Any step referencing 'integration team' or 'post-acquisition leadership'" + change: "Replace with personal capacity assessment: 'Can you absorb this acquisition into your current operations without hiring? What processes must you build to manage the additional scope?'" + + - name: "board-formation-playbook" + adaptation: "skip" + reason: "Solopreneurs do not form boards of directors." + alternative: "If the solopreneur wants structured external guidance, suggest building an informal advisory network using meeting-the-right-people and connecting-with-people skills. Use personal-board-tracker template for managing these relationships." + + - name: "competitive-response-playbook" + adaptation: "as-is" + reason: "Competitive response is equally critical for solo businesses. All steps apply without modification." + + - name: "crisis-playbook" + adaptation: "reframe" + reason: "Crisis management applies but the solopreneur IS the crisis response team." + step_changes: + - step: "Any step referencing 'assemble crisis team' or 'delegate crisis response'" + change: "Replace with personal triage: 'Identify the single highest-impact action you can take in the next 2 hours. Defer everything else. Contact your most trusted advisor or mentor for a 15-minute sounding board call.'" + - step: "Any step referencing 'internal communications'" + change: "Replace with client communications: 'Notify affected clients directly. Be honest about the situation, your response, and timeline for resolution.'" + + - name: "first-100-customers-playbook" + adaptation: "as-is" + reason: "Acquiring first customers is identical for solopreneurs. Every step applies." + + - name: "founder-transition-playbook" + adaptation: "reframe" + reason: "The solopreneur is the founder and the entire company. Transition means either selling the business, winding it down, or hiring someone to replace yourself." + step_changes: + - step: "Any step referencing 'succession planning' or 'leadership handoff'" + change: "Replace with 'business sale preparation' or 'operational documentation for buyer due diligence.' The transition is not from one leader to another — it is from one person to a new owner or to closure." + - step: "Any step referencing 'board notification' or 'stakeholder alignment'" + change: "Replace with 'client notification plan' and 'contractor wind-down or transfer plan.'" + + - name: "fundraising-playbook" + adaptation: "reframe" + reason: "Fundraising for solopreneurs involves different instruments and different motivations than venture fundraising." + step_changes: + - step: "Prepare for term sheet negotiation (competitive-negotiation skill)" + change: "Replace with 'Prepare for loan terms, grant applications, revenue-based financing terms, or angel investment negotiation.' The skill (competitive-negotiation) remains; the application context shifts from equity rounds to solo-appropriate funding." + - step: "Make the fundraising deck scannable (writing-for-navigation skill)" + change: "Replace with 'Make the business plan or loan application clear and scannable.' The skill remains; the output format shifts from pitch deck to business plan or grant application." + - step: "Craft the fundraising narrative (story-structure-and-arc skill)" + change: "Replace with 'Craft the business story for the specific audience: bank loan officer, grant committee, angel investor, or revenue-based financing provider.'" + output_changes: + - output: "fundraising-deck-outline" + change: "Replace with business plan outline or loan application package." + - output: "investor-update-email" + change: "Replace with monthly self-review or angel investor update (if applicable)." + + - name: "innovation-sprint-playbook" + adaptation: "reframe" + reason: "Innovation sprints are valuable for solopreneurs but the team-based sprint format must become a personal sprint." + step_changes: + - step: "Any step referencing 'sprint team' or 'cross-functional participation'" + change: "Replace with personal focus block: 'Block 2-5 days for dedicated innovation work. Cancel or defer all client obligations for this period. Work alone or with one trusted collaborator.'" + - step: "Any step referencing 'team brainstorming'" + change: "Replace with structured solo ideation using generating-solutions skill (BrainSwarming, SCAMPER) or a facilitated session with a mentor." + + - name: "international-expansion-playbook" + adaptation: "reframe" + reason: "Solopreneurs expand internationally through digital delivery, remote clients, and online marketing — not by opening offices." + step_changes: + - step: "Any step referencing 'local team' or 'country manager'" + change: "Replace with 'local contractor or partner' and 'market-specific service adaptation.' The solopreneur expands by adapting offerings for new markets, not by building local teams." + - step: "Any step referencing 'regulatory compliance for employer'" + change: "Replace with 'tax obligations for international service revenue' and 'contractor engagement across jurisdictions.'" + + - name: "launch-playbook" + adaptation: "as-is" + reason: "Product and service launches work identically for solopreneurs. All steps apply." + + - name: "negotiation-playbook" + adaptation: "as-is" + reason: "Negotiation is interpersonal. The solopreneur is always the negotiator. All steps apply without modification." + + - name: "partnership-playbook" + adaptation: "as-is" + reason: "Partnerships are equally relevant to solo businesses. Referral partnerships, joint ventures, and strategic alliances are common solo growth strategies." + + - name: "personal-brand-playbook" + adaptation: "as-is" + reason: "Personal brand IS the business brand for solopreneurs. This playbook is more relevant in solo mode than in default mode." + + - name: "pivot-playbook" + adaptation: "reframe" + reason: "Pivoting a solo business is faster and more personal — no team to realign, no board to convince — but the stakes are identical." + step_changes: + - step: "Any step referencing 'communicate pivot to team' or 'align organization'" + change: "Replace with 'communicate transition to existing clients' and 'update contractor relationships for new direction.'" + - step: "Any step referencing 'restructure team for new direction'" + change: "Replace with 'assess personal skills for new direction: what do you need to learn, and what should you outsource?'" + + - name: "pricing-strategy-playbook" + adaptation: "as-is" + reason: "Pricing strategy applies identically. The solopreneur sets prices with the same frameworks." + + - name: "product-market-fit-playbook" + adaptation: "as-is" + reason: "Product-market fit assessment works at any company size. All steps apply." + + - name: "remote-team-playbook" + adaptation: "skip" + reason: "No team to manage remotely." + alternative: "If the solopreneur works with remote contractors, suggest delivering-the-deal and connecting-with-people skills for contractor relationship management. For personal remote work productivity, suggest focus-and-priority-management and creative-practice-and-habit." + + - name: "scaling-playbook" + adaptation: "reframe" + reason: "Scaling a solo business means increasing revenue or margin without proportional time increase — not adding headcount." + step_changes: + - step: "Any step referencing 'hiring plan' or 'team expansion'" + change: "Replace with 'systemization plan: which processes can be automated, productized, or outsourced to increase output without increasing your hours?'" + - step: "Any step referencing 'management structure' or 'org design'" + change: "Replace with 'personal operating system design: how do you structure your week, your client load, and your project pipeline for maximum throughput at sustainable effort?'" + - step: "Any step referencing 'leadership development for managers'" + change: "Replace with 'skill development prioritization: which capabilities will unlock the next revenue tier?'" + + - name: "strategy-reset-playbook" + adaptation: "reframe" + reason: "Strategy resets for solopreneurs are deeply personal — the business strategy and life strategy are intertwined." + step_changes: + - step: "Any step referencing 'leadership team alignment on new strategy'" + change: "Replace with 'personal commitment to new direction.' The solopreneur does not need alignment — they need conviction." + - step: "Any step referencing 'communicate strategy change to organization'" + change: "Replace with 'communicate direction change to clients, contractors, and accountability partners.'" + + - name: "team-rebuild-playbook" + adaptation: "skip" + reason: "No team to rebuild." + alternative: "If the solopreneur has lost key contractors, suggest meeting-the-right-people and delivering-the-deal for rebuilding a contractor network. If the issue is personal burnout or motivation loss, suggest leader-resilience-and-wellbeing, stoic-fortitude-and-resilience, and creative-completion-and-renewal." + +# ───────────────────────────────────────────── +# HOOK ADAPTATIONS (16 hooks) +# ───────────────────────────────────────────── + +hook_adaptations: + + - name: "communication-hook" + adaptation: "reframe" + reason: "Internal communication is not applicable. Reframe as client communication and personal clarity." + routing_changes: + - "Remove communication-breakdown-diagnosis from routing when solo mode detects the input is about internal communication." + - "Add writing skills (clarity-and-concision, writing-effective-emails) as primary skill routes." + - "Retain communication-breakdown-diagnosis only when the input clearly references client or contractor communication failure." + + - name: "competition-hook" + adaptation: "as-is" + reason: "Competitive dynamics are identical for solo businesses." + + - name: "culture-hook" + adaptation: "reframe" + reason: "Organizational culture does not exist for solopreneurs. Reframe as brand identity and personal values." + routing_changes: + - "Remove culture-erosion-diagnosis from primary routing." + - "Route to strategic-drift-diagnosis if the input suggests the solopreneur is losing connection to their business purpose." + - "Route to creative-identity-and-purpose if the input suggests an identity or meaning crisis." + - "Add purpose-driven-leadership and wanting-what-matters as skill routes." + + - name: "decision-hook" + adaptation: "as-is" + reason: "Decision-making challenges are amplified for solopreneurs. Routing unchanged; skill priority elevated." + + - name: "fundraising-hook" + adaptation: "reframe" + reason: "Fundraising exists for solopreneurs but the instruments and motivations differ." + routing_changes: + - "Retain fundraising-diagnosis but apply solo reframing (see diagnostic adaptations)." + - "Add evaluating-options as a pre-routing skill to assess whether external capital is needed at all." + - "Replace fundraising-playbook default routing with reframed version." + + - name: "growth-hook" + adaptation: "reframe" + reason: "Growth for solopreneurs often hits a personal capacity ceiling before a market ceiling." + routing_changes: + - "Add capacity-assessment triage question before routing to growth-stall-diagnosis: 'Is growth limited by demand or by your ability to deliver?'" + - "Add eisenhower-matrix and focus-and-priority-management to skill routes." + - "Retain growth-stall-diagnosis with solo reframing applied." + + - name: "innovation-hook" + adaptation: "reframe" + reason: "Innovation for solopreneurs is creative practice, not R&D pipeline management." + routing_changes: + - "Elevate creative skills (creative-obstacles, creative-flow-and-inspiration, creative-practice-and-habit) in routing priority." + - "Retain innovation-drought-diagnosis with solo reframing applied." + + - name: "launch-hook" + adaptation: "as-is" + reason: "Launching products and services works identically for solopreneurs." + + - name: "leadership-hook" + adaptation: "reframe" + reason: "Leadership of others is not applicable. Reframe as self-leadership and business owner decision-making." + routing_changes: + - "Remove leadership-crisis-diagnosis from default routing when input describes personal struggle rather than organizational leadership failure." + - "Route to leader-self-reflection, emotional-courage, and decision-making-under-pressure as primary skills." + - "Add stoic skills (stoic-control-and-clarity, stoic-fortitude-and-resilience) as secondary routes." + + - name: "negotiation-hook" + adaptation: "as-is" + reason: "Negotiation is interpersonal. No adaptation needed." + + - name: "partnership-hook" + adaptation: "as-is" + reason: "Partnerships are equally relevant to solo businesses." + + - name: "personal-growth-hook" + adaptation: "as-is" + reason: "Personal growth is the foundation of solo business success. Routing unchanged; skill priority elevated." + + - name: "product-hook" + adaptation: "as-is" + reason: "Product development and management apply regardless of company size." + + - name: "revenue-and-sales-hook" + adaptation: "reframe" + reason: "Revenue is personal income for solopreneurs. Sales process is personal, not team-delegated." + routing_changes: + - "Add personal income sustainability framing to all revenue skill applications." + - "Replace 'sales team performance' triage paths with 'personal sales process effectiveness.'" + - "Add effective hourly rate calculation as a standard diagnostic supplement." + + - name: "strategy-hook" + adaptation: "as-is" + reason: "Strategic thinking applies at any company size. Routing unchanged." + + - name: "team-hook" + adaptation: "reframe" + reason: "No team. The hook's trigger patterns ('my team isn't working,' 'people are leaving') must be intercepted and redirected." + routing_changes: + - "Remove team-dysfunction-diagnosis, hiring-diagnosis, and culture-erosion-diagnosis from routing." + - "When triggered, ask a clarifying question: 'Solo mode is active. Are you describing a challenge with contractors or freelancers, or a personal feeling of being overwhelmed?'" + - "If contractors: route to negotiation-stuck-diagnosis and delivering-the-deal." + - "If personal overwhelm: route to operational-chaos-diagnosis (reframed), eisenhower-matrix, leader-resilience-and-wellbeing." + - "Remove team-rebuild-playbook from routing. Add meeting-the-right-people as a skill route." diff --git a/plugins/foreman/content/solo-mode/solo-audience-map.yaml b/plugins/foreman/content/solo-mode/solo-audience-map.yaml new file mode 100644 index 0000000..20ac060 --- /dev/null +++ b/plugins/foreman/content/solo-mode/solo-audience-map.yaml @@ -0,0 +1,398 @@ +# Solo Audience Mapping +# +# Defines how the five output audiences remap when solo mode is active. +# The output-agent loads this file and applies transformations before +# rendering any template. +# +# Two audiences (client, self) are unchanged. +# Three audiences (investor, board, team) require fundamental reframing. + +audience_mapping: + + # ───────────────────────────────────────────── + # INVESTOR → SELF-FUNDING-ANALYSIS + # ───────────────────────────────────────────── + + investor: + solo_equivalent: "self-funding-analysis" + description: "Investor-facing outputs become personal financial analysis + documents. The solopreneur is both the operator and the capital allocator. + Replace investor persuasion framing with honest self-assessment of + business viability and personal income sustainability." + tone_shift: "Remove persuasive pitch framing. Replace with analytical + self-assessment. The audience is you — be honest, not impressive." + structural_changes: + - "Replace 'investor returns' with 'personal income sustainability and + wealth building'" + - "Replace 'fundraising narrative' with 'business viability assessment'" + - "Replace 'term sheet negotiation' with 'financing terms evaluation + (loans, grants, revenue-based financing)'" + - "Replace 'board seat allocation' with 'advisory relationship structure'" + - "Replace 'exit strategy' with 'long-term business trajectory and + personal exit options'" + - "Replace 'dilution analysis' with 'ownership and control preservation'" + exception: "If identity.yaml indicates the solopreneur has external investors + (angels, micro-VCs, loan providers), use a hybrid approach: retain + financial rigor but strip the pitch language. Present data, not a + narrative designed to persuade." + + template_adaptations: + - adaptation: "Reframe as ownership and equity structure document. If no external + investors, simplify to a single-owner statement with any contractor + equity or profit-sharing arrangements noted." + kind: template + ref: cap-table-summary + + - adaptation: "Use as-is. Competitive analysis is equally relevant to + solopreneurs. Remove the 'defensibility pitch' angle and replace with + 'competitive awareness for strategic positioning.'" + kind: template + ref: competitive-landscape-brief + + - adaptation: "Reframe as personal decision journal entry. Replace 'communicate + rationale to investors' with 'document your reasoning for future + reference and accountability partner review.'" + kind: template + ref: decision-rationale-memo + + - adaptation: "Reframe as annual business health audit. The solopreneur performs + due diligence on their own business. Replace 'what investors will + check' with 'what you should verify about your business quarterly.'" + kind: template + ref: due-diligence-checklist + + - adaptation: "Reframe as long-term optionality analysis. Replace 'exit for + investor returns' with 'options for the future: sell, wind down, + transition to lifestyle business, hire and grow, or continue as-is.'" + kind: template + ref: exit-scenario-analysis + + - adaptation: "Reframe as business plan outline for personal clarity or loan/grant + applications. Strip the slide-by-slide investor deck structure and + replace with a written business plan format." + kind: template + ref: fundraising-deck-outline + + - adaptation: "Reframe as monthly self-review email to accountability partner or + mentor. Replace investor-specific metrics framing with personal + progress metrics. If the solopreneur has angel investors, retain the + format but adjust tone from 'selling' to 'reporting.'" + kind: template + ref: investor-update-email + + - adaptation: "Use mostly as-is. Market sizing applies regardless of company size. + Remove 'TAM/SAM/SOM for investor persuasion' framing and replace with + 'addressable market for realistic revenue planning.'" + kind: template + ref: market-opportunity-summary + + - adaptation: "Reframe as personal strategic summary. A one-page overview of where + the business stands, written for the solopreneur's own clarity and for + sharing with mentors." + kind: template + ref: strategic-analysis-one-pager + + - adaptation: "Reframe as personal income sustainability dashboard. Replace + 'metrics that trigger investor concern' with 'metrics that indicate + business health.' Focus on: personal draw, profit margin, effective + hourly rate, client concentration risk, revenue predictability." + kind: template + ref: unit-economics-snapshot + + # ───────────────────────────────────────────── + # BOARD → MENTOR-ADVISOR + # ───────────────────────────────────────────── + + board: + solo_equivalent: "mentor-advisor" + description: "Board-facing outputs become mentor or accountability partner + briefs. The solopreneur has no board of directors. Governance language is + replaced with personal accountability language. Formal board structures + are replaced with informal but rigorous self-governance practices." + tone_shift: "Remove formal governance tone. Replace with direct, conversational + briefing appropriate for a trusted mentor. Less 'resolution' language, + more 'here is where I am and what I am thinking.'" + structural_changes: + - "Replace 'board of directors' with 'mentor, advisor, or accountability + partner'" + - "Replace 'board resolution' with 'decision rationale documented for + review'" + - "Replace 'quarterly board review' with 'quarterly self-review shared + with mentor'" + - "Replace 'committee recommendation' with 'personal analysis and + conclusion'" + - "Replace 'board approval required' with 'decision point: commit or + defer'" + - "Replace 'fiduciary responsibility' with 'personal responsibility and + ethical commitment'" + exception: "If the solopreneur has a formal advisory board (not a governance + board), retain the briefing format but adjust the power dynamic. Advisors + advise; they do not approve or veto." + + template_adaptations: + - adaptation: "Reframe as structured mentor meeting agenda. Replace governance + items (approvals, resolutions, committee reports) with discussion + items: strategic questions, decision pressure-tests, and + accountability check-ins." + kind: template + ref: board-meeting-agenda + + - adaptation: "Reframe as business continuity plan. The solopreneur has no CEO to + succeed, but does need a plan for what happens if they are + incapacitated, want to step back, or decide to sell. Replace + succession language with contingency planning." + kind: template + ref: ceo-succession-brief + + - adaptation: "Reframe as personal pivot or strategic shift memo. Replace 'propose + to the board' with 'document the change rationale for personal clarity + and mentor discussion.'" + kind: template + ref: change-initiative-proposal + + - adaptation: "Reframe as personal draw and compensation structure review. Replace + employee compensation analysis with: what the solopreneur pays + themselves, whether the amount is sustainable, and how it compares to + market alternatives (employment)." + kind: template + ref: compensation-review-brief + + - adaptation: "Reframe as quarterly self-assessment. Retain the strategic review + structure (performance vs. goals, market conditions, competitive + position) but address it to yourself or your mentor. Replace 'board + discussion points' with 'decisions to make this quarter.'" + kind: template + ref: quarterly-strategic-review + + - adaptation: "Use mostly as-is. Regulatory compliance applies to solo businesses. + Remove board-specific reporting structure and present as a personal + compliance checklist." + kind: template + ref: regulatory-compliance-update + + - adaptation: "Reframe as personal risk register. Replace organizational risk + categories with solo-specific risks: key-person dependency (you), + client concentration, revenue volatility, health and burnout, skill + gaps without team coverage." + kind: template + ref: risk-assessment-brief + + # ───────────────────────────────────────────── + # TEAM → SYSTEMS-AND-PROCESSES + # ───────────────────────────────────────────── + + team: + solo_equivalent: "systems-and-processes" + description: "Team-facing outputs become process documentation, personal + operating procedures, and contractor briefs. Where the default creates + alignment documents for humans on a team, solo mode creates reference + documents for the solopreneur's own consistency, for onboarding + contractors, or for delegating to AI tools." + tone_shift: "Remove alignment and motivation language. Replace with clear, + procedural instruction. The audience is either future-you (who will forget + the details) or a contractor (who needs explicit direction)." + structural_changes: + - "Replace 'team alignment' with 'process documentation'" + - "Replace 'communicate to team' with 'document for personal reference or + contractor handoff'" + - "Replace 'team meeting' with 'weekly self-review or contractor check-in'" + - "Replace 'assign to team member' with 'schedule in personal workflow or + brief to contractor'" + - "Replace 'team values' with 'business principles and personal standards'" + - "Replace 'onboarding new hire' with 'onboarding new contractor or + documenting for future delegation'" + + template_adaptations: + - adaptation: "Reframe as personal implementation plan. Replace 'owner' column + (team members) with 'method' column (do personally, outsource to + contractor, automate, defer). Add time estimate per item." + kind: template + ref: action-plan + + - adaptation: "Reframe as business principles and brand values document. Replace + organizational culture language with personal business philosophy: how + you treat clients, what you refuse to compromise on, how you make + decisions." + kind: template + ref: culture-values-document + + - adaptation: "Reframe as client feedback collection template. Replace peer and + manager feedback sections with: client satisfaction questions, + referral source interviews, and self-assessment against business + goals." + kind: template + ref: feedback-360-template + + - adaptation: "Reframe as contractor evaluation scorecard. Replace hiring criteria + (culture fit, growth potential, team dynamics) with contractor + criteria: deliverable quality, communication reliability, rate + alignment, domain expertise." + kind: template + ref: hiring-scorecard + + - adaptation: "Use mostly as-is. Postmortems are valuable for solo operators. + Replace 'team debrief' with 'personal debrief.' The root cause + analysis and prevention steps apply identically." + kind: template + ref: incident-postmortem + + - adaptation: "Reframe as client meeting notes or contractor check-in notes. + Replace internal meeting structure with external meeting + documentation." + kind: template + ref: meeting-notes-template + + - adaptation: "Reframe as new project brief for personal planning. Replace 'team + resources required' with 'time investment required, contractor support + needed, tools to acquire.'" + kind: template + ref: new-initiative-brief + + - adaptation: "Reframe as personal strategic retreat planning guide. Replace team + offsite logistics with solo retreat structure: reflection exercises, + strategic planning blocks, environment design." + kind: template + ref: offsite-planning-guide + + - adaptation: "Reframe as mentor meeting preparation template or contractor + check-in template. Replace manager-report dynamic with peer advisory + dynamic." + kind: template + ref: one-on-one-template + + - adaptation: "Reframe as project start checklist. Replace team roles and + responsibilities with personal task breakdown and contractor scope + definitions." + kind: template + ref: project-kickoff-document + + - adaptation: "Reframe as personal retrospective. Replace team retrospective + facilitation with structured self-reflection: what went well, what did + not, what to change. A weekly or monthly solo practice." + kind: template + ref: retrospective-template + + - adaptation: "Reframe as contractor scope of work template. Replace job + description format with project-based scope definition: deliverables, + timeline, communication expectations, quality standards." + kind: template + ref: role-description-template + + - adaptation: "Reframe as personal sustainability check. Replace team health + dimensions (morale, alignment, psychological safety) with solo health + dimensions: energy level, financial runway, client satisfaction, skill + development, work-life sustainability." + kind: template + ref: team-health-check + + # ───────────────────────────────────────────── + # CLIENT → CLIENT (unchanged) + # ───────────────────────────────────────────── + + client: + solo_equivalent: "client" + description: "Client-facing outputs require no adaptation. The solopreneur + serves clients in the same professional capacity as a larger firm. Quality + standards and communication expectations are identical." + tone_shift: "No change." + structural_changes: [] + + template_adaptations: + - adaptation: "Use as-is." + kind: template + ref: analysis-report + + - adaptation: "Use as-is." + kind: template + ref: case-study-template + + - adaptation: "Use as-is." + kind: template + ref: onboarding-welcome-packet + + - adaptation: "Use as-is." + kind: template + ref: partnership-memo + + - adaptation: "Use as-is." + kind: template + ref: project-status-update + + - adaptation: "Use as-is." + kind: template + ref: proposal-outline + + - adaptation: "Use as-is." + kind: template + ref: quarterly-business-review + + - adaptation: "Use as-is." + kind: template + ref: service-level-agreement + + # ───────────────────────────────────────────── + # SELF → SELF (unchanged, elevated to default) + # ───────────────────────────────────────────── + + self: + solo_equivalent: "self" + description: "Self-facing outputs are already personal. In solo mode, self + becomes the default audience when no audience is specified. These + templates are the solopreneur's primary working documents." + tone_shift: "No change. Already appropriately personal." + structural_changes: + - "Elevate to default audience when no audience is specified (in default + mode, the system infers audience from context; in solo mode, self is the + fallback)" + + template_adaptations: + - adaptation: "Use as-is. Add emphasis on personal income review and work-life + sustainability assessment." + kind: template + ref: annual-review-and-planning + + - adaptation: "Use as-is. In solo mode, career strategy and business strategy are + the same document." + kind: template + ref: career-strategy-canvas + + - adaptation: "Use as-is. Elevated importance — the decision journal is the + solopreneur's primary accountability mechanism." + kind: template + ref: decision-journal + + - adaptation: "Use as-is. Add solo-specific prompts: isolation assessment, + boundary audit, support network inventory." + kind: template + ref: founder-mental-health-check + + - adaptation: "Reframe as business owner reflection. Replace leadership-of-others + prompts with leadership-of-self prompts." + kind: template + ref: leadership-reflection + + - adaptation: "Use as-is. Learning is more urgent when there is no team with + complementary skills." + kind: template + ref: learning-plan + + - adaptation: "Use as-is." + kind: template + ref: negotiation-prep-sheet + + - adaptation: "Reframe as mentor and advisor network tracker. Replace board + governance tracking with informal advisory relationship management." + kind: template + ref: personal-board-tracker + + - adaptation: "Use as-is. The solopreneur's stakeholder map is simpler (no + internal stakeholders) but still valuable for client, partner, and + vendor relationship management." + kind: template + ref: stakeholder-map + + - adaptation: "Reframe as weekly business owner review. Replace CEO framing with + owner-operator framing. This becomes the solopreneur's primary weekly + practice." + kind: template + ref: weekly-ceo-review diff --git a/plugins/foreman/content/solo-mode/solo-skill-relevance.yaml b/plugins/foreman/content/solo-mode/solo-skill-relevance.yaml new file mode 100644 index 0000000..3d3269f --- /dev/null +++ b/plugins/foreman/content/solo-mode/solo-skill-relevance.yaml @@ -0,0 +1,708 @@ +# Solo Skill Relevance Scoring +# +# Assigns a relevance tier to every skill when solo mode is active. +# The orchestrator uses these tiers to adjust routing priority during +# hook matching and skill selection. +# +# Tiers: +# critical — Front and center for solopreneurs. Prioritize in routing. +# high — Very useful. Normal routing priority. +# moderate — Useful but needs significant reframing for solo context. +# low — Mostly irrelevant. Apply only when explicitly requested. +# +# 14 categories, 158 skills. + +category_defaults: + frameworks: high + ai-leadership: moderate + writing: critical + leadership: moderate + game-theory: high + stoic: critical + storytelling: critical + negotiation: critical + people: critical + creative: critical + thinking: critical + decisions: critical + +# ───────────────────────────────────────────── +# FRAMEWORKS (50 skills) — category default: high +# ───────────────────────────────────────────── + +skills: + frameworks/ambidexterity: + tier: high + note: "Balancing exploitation of current revenue with exploration of new opportunities applies directly to solopreneurs managing a service business while building a product." + + frameworks/appreciative-inquiry: + tier: high + note: "Self-directed appreciative inquiry — identifying what is working and amplifying it — is a powerful solo practice." + + frameworks/art-of-war: + tier: high + note: "Competitive strategy applies regardless of company size. Solopreneurs face competitors with more resources; strategic thinking matters more, not less." + + frameworks/balanced-scorecard: + tier: high + note: "Personal business scorecard: financial, customer, internal process, and learning perspectives all apply at the solo level." + + frameworks/belbin-team-roles: + tier: low + note: "Team composition framework. No team to compose. If the solopreneur is assembling contractors, suggest connecting-with-people or meeting-the-right-people instead." + + frameworks/black-swans: + tier: high + note: "Solo businesses are more fragile to black swan events — less redundancy, no team to absorb shocks. Highly relevant." + + frameworks/blue-ocean-strategy: + tier: critical + note: "Solopreneurs cannot compete on resources. Blue ocean thinking — creating uncontested market space — is structurally essential." + + frameworks/business-model-canvas: + tier: critical + note: "The foundational tool for any business. Solo businesses need this as much as funded startups." + + frameworks/carnegie-win-friends: + tier: critical + note: "Relationship building is the solopreneur's primary growth engine. Every client, partner, and referral depends on interpersonal skill." + + frameworks/cialdini-influence: + tier: critical + note: "Solopreneurs must persuade without institutional credibility backing them. Influence principles are structurally critical." + + frameworks/covey-seven-habits: + tier: critical + note: "Personal effectiveness habits are the operating system of a solo business. Begin with the end in mind, first things first, sharpen the saw — all directly applicable." + + frameworks/disruptive-innovation: + tier: high + note: "Understanding disruption helps solopreneurs identify niches that large competitors ignore." + + frameworks/doblin-ten-types: + tier: high + note: "Innovation types help solopreneurs identify where to innovate beyond just the product — process, channel, brand, customer engagement." + + frameworks/eisenhower-matrix: + tier: critical + note: "The single most important prioritization tool for someone who must do everything themselves. Non-negotiable for solopreneurs." + + frameworks/emotional-intelligence: + tier: critical + note: "Self-management and social awareness are critical when you are the sole representative of your business in every interaction." + + frameworks/flow-state: + tier: critical + note: "Solopreneurs depend on personal productivity. Understanding and engineering flow states directly impacts output and revenue." + + frameworks/four-ps-marketing: + tier: critical + note: "Product, Price, Place, Promotion — the solopreneur controls all four directly. No marketing team to delegate to." + + frameworks/giving-feedback: + tier: low + note: "Assumes a manager-report relationship. Reframe only if the solopreneur manages contractors regularly." + + frameworks/grow-model: + tier: high + note: "Self-coaching model. Goal, Reality, Options, Will — a solopreneur can run GROW sessions as structured self-reflection." + + frameworks/growth-mindset: + tier: critical + note: "Solo operation demands continuous learning with no team to compensate for skill gaps." + + frameworks/growth-share-matrix: + tier: high + note: "Portfolio analysis of the solopreneur's revenue streams: which are stars, cash cows, question marks, dogs." + + frameworks/hackman-enabling-conditions: + tier: low + note: "Team design framework. No team to design. Skip unless managing a group of contractors." + + frameworks/johari-window: + tier: high + note: "Self-awareness tool. Useful for solopreneurs who lack regular peer feedback." + + frameworks/kaizen-bpr: + tier: high + note: "Continuous improvement of personal processes and business operations. Directly applicable." + + frameworks/kotter-change-model: + tier: moderate + note: "Organizational change framework. Reframe as personal pivot management — the solopreneur is both the change leader and the organization." + + frameworks/leadership-pipeline: + tier: low + note: "Career progression through organizational leadership levels. Irrelevant without an organization." + + frameworks/lean-in: + tier: moderate + note: "Career advancement within organizational structures. Some principles on ambition and self-advocacy apply; organizational politics framing does not." + + frameworks/lewin-leadership-styles: + tier: low + note: "Autocratic, democratic, laissez-faire leadership styles assume followers. No followers in solo context." + + frameworks/maslow-hierarchy: + tier: high + note: "Understanding customer motivation and personal motivation. The solopreneur must manage their own hierarchy alongside understanding their customers'." + + frameworks/myers-briggs-type-indicator: + tier: high + note: "Self-understanding tool. Useful for solopreneurs identifying how their personality affects business decisions and client interactions." + + frameworks/net-promoter-score: + tier: high + note: "Customer satisfaction measurement applies regardless of company size." + + frameworks/neuro-linguistic-programming: + tier: high + note: "Communication and self-programming techniques. Useful for sales conversations and personal state management." + + frameworks/organisational-culture: + tier: low + note: "Culture frameworks assume multiple people. A solopreneur has personal values and brand identity, not organizational culture." + + frameworks/porters-five-forces: + tier: high + note: "Industry analysis applies at any scale. Solopreneurs benefit from understanding supplier power, buyer power, and competitive rivalry in their niche." + + frameworks/product-life-cycle: + tier: high + note: "Understanding where offerings sit in their life cycle helps solopreneurs time pivots and new product development." + + frameworks/psychological-safety: + tier: low + note: "Team psychological safety framework. Reframe only as client relationship safety or contractor relationship quality." + + frameworks/radical-candor: + tier: moderate + note: "Feedback framework for manager-report relationships. Moderate relevance for contractor feedback or client communication." + + frameworks/scenario-planning: + tier: high + note: "Strategic foresight is critical for solo businesses with less margin for error." + + frameworks/shamrock-organisation: + tier: high + note: "Core workers, contractors, flexible labor — this model describes exactly how solopreneurs build capacity without hiring. Highly relevant despite the organizational framing." + + frameworks/situational-leadership: + tier: low + note: "Adapting leadership style to follower maturity. No followers in solo context." + + frameworks/smart-goals: + tier: critical + note: "Goal setting is the solopreneur's steering mechanism. No manager to set goals for them; no team goals to cascade." + + frameworks/swot-pest-analysis: + tier: critical + note: "Strategic assessment tool that works identically for solo businesses. Strengths and weaknesses are personal as much as organizational." + + frameworks/systems-thinking: + tier: high + note: "Understanding feedback loops and unintended consequences in a business you control entirely." + + frameworks/thinking-fast-and-slow: + tier: critical + note: "Cognitive bias awareness is more critical when there is no team to catch your blind spots." + + frameworks/thomas-kilmann-conflict: + tier: high + note: "Conflict with clients, vendors, and partners. The solopreneur handles all conflict personally." + + frameworks/tipping-point: + tier: high + note: "Understanding viral growth and market dynamics. Relevant for marketing strategy." + + frameworks/trust-equation: + tier: critical + note: "Trust is the solopreneur's primary asset. Credibility, reliability, intimacy, and self-orientation govern every client relationship." + + frameworks/tuckman-team-stages: + tier: low + note: "Team development stages. No team. If managing contractors, suggest connecting-with-people instead." + + frameworks/vuca-framework: + tier: high + note: "Volatility, Uncertainty, Complexity, Ambiguity — solo businesses operate in VUCA conditions with fewer buffers." + + frameworks/win-win-negotiation: + tier: critical + note: "Every deal the solopreneur strikes is personal. Win-win negotiation is not a nice-to-have — it is how repeat business works." + + # ───────────────────────────────────────────── + # AI-LEADERSHIP (9 skills) — category default: moderate + # ───────────────────────────────────────────── + + ai-leadership/ai-augmentation-not-automation: + tier: critical + note: "AI as force multiplier is existentially important for solopreneurs. One person plus AI tools can match a small team's output." + + ai-leadership/ai-communication-culture: + tier: low + note: "Building AI communication culture across an organization. No organization." + + ai-leadership/ai-emotional-intelligence: + tier: moderate + note: "Understanding AI's limitations in emotional contexts. Useful for solopreneurs relying heavily on AI for customer-facing work." + + ai-leadership/ai-human-centered-approach: + tier: moderate + note: "Keeping humans central to AI deployment. Relevant when the solopreneur is the human and the AI is the team." + + ai-leadership/ai-inclusive-collaboration: + tier: low + note: "Organizational AI inclusion. No organization to include." + + ai-leadership/ai-learning-for-leaders: + tier: high + note: "Staying current with AI capabilities. Critical for a solopreneur whose competitive advantage depends on AI leverage." + + ai-leadership/ai-purpose-driven-questions: + tier: high + note: "Asking better questions of AI systems. Directly applicable to the solopreneur's daily AI usage." + + ai-leadership/ai-stakeholder-balance: + tier: low + note: "Balancing AI impact across organizational stakeholders. No stakeholders beyond the solopreneur and their clients." + + ai-leadership/ai-vision-and-strategy: + tier: high + note: "AI strategy for the business. Solopreneurs need a deliberate AI strategy, not ad hoc tool adoption." + + # ───────────────────────────────────────────── + # WRITING (13 skills) — category default: critical + # ───────────────────────────────────────────── + + writing/clarity-and-concision: + tier: critical + note: "Every written word from the business is the solopreneur's word. Clarity is brand." + + writing/grammar-and-mechanics: + tier: critical + note: "No editor, no comms team. The solopreneur is the last line of defense against errors." + + writing/plain-language-and-flow: + tier: critical + note: "Clear writing converts. The solopreneur writes their own copy, proposals, and emails." + + writing/reader-psychology: + tier: critical + note: "Understanding how readers process text. Essential for someone who writes all their own marketing and client communication." + + writing/revising-and-editing: + tier: critical + note: "Self-editing discipline. No one else will review before it ships." + + writing/tone-and-engagement: + tier: critical + note: "The solopreneur's writing tone is the brand's voice." + + writing/writing-effective-emails: + tier: critical + note: "Email is the primary business communication channel for most solopreneurs." + + writing/writing-for-navigation: + tier: critical + note: "Making documents scannable. Proposals, invoices, reports — all written by one person." + + writing/writing-for-response: + tier: critical + note: "Getting people to act on what you write. Directly affects sales and client management." + + writing/writing-memos-and-reports: + tier: high + note: "Less frequent for solopreneurs unless producing client deliverables in report format." + + writing/writing-performance-reviews: + tier: low + note: "Performance reviews assume a manager-report relationship. Reframe as structured self-assessment if requested." + + writing/writing-process: + tier: critical + note: "Developing a reliable writing practice. The solopreneur writes constantly — process matters." + + writing/writing-with-purpose: + tier: critical + note: "Every piece of writing serves a business purpose. No writing for bureaucratic compliance." + + # ───────────────────────────────────────────── + # LEADERSHIP (28 skills) — category default: moderate + # ───────────────────────────────────────────── + + leadership/ai-era-leadership: + tier: high + note: "Leading in the AI era applies to self-leadership and client-facing authority." + + leadership/business-writing-for-leaders: + tier: high + note: "Business writing applies regardless of whether you lead others or lead yourself." + + leadership/career-strategy-for-leaders: + tier: critical + note: "The solopreneur's career strategy IS the business strategy. Inseparable." + + leadership/decision-making-under-pressure: + tier: critical + note: "No team to absorb pressure. Every high-stakes decision is yours alone." + + leadership/delegation-and-empowerment: + tier: moderate + note: "Reframe as delegation to contractors, AI tools, and automation — not employees." + + leadership/emotional-courage: + tier: critical + note: "Difficult conversations with clients, ending unprofitable relationships, raising prices — all require emotional courage without team support." + + leadership/employee-engagement-retention: + tier: low + note: "No employees. Skip unless managing regular contractors." + + leadership/focus-and-priority-management: + tier: critical + note: "The solopreneur's most constrained resource is attention. This is structurally essential." + + leadership/humility-and-power: + tier: high + note: "Humility in client relationships and self-assessment. Power dynamics with partners and vendors." + + leadership/inclusive-leadership: + tier: low + note: "Organizational inclusion practices. No organization. Reframe as inclusive client service if requested." + + leadership/introvert-leadership: + tier: high + note: "Many solopreneurs are introverts who chose solo operation deliberately. Managing energy for sales and networking is directly applicable." + + leadership/leader-resilience-and-wellbeing: + tier: critical + note: "Burnout prevention is existential for solopreneurs. If you break, the business stops." + + leadership/leader-self-reflection: + tier: critical + note: "Self-reflection is the solopreneur's substitute for external feedback, coaching, and performance reviews." + + leadership/leadership-style-adaptation: + tier: low + note: "Adapting leadership style to team context. No team. Reframe as adapting communication style to client contexts if requested." + + leadership/leadership-voice-and-presence: + tier: high + note: "Personal brand and authority. The solopreneur is the brand — voice and presence are commercial assets." + + leadership/leading-through-change: + tier: moderate + note: "Organizational change leadership. Reframe as personal pivot management and client communication during business transitions." + + leadership/learning-agility: + tier: critical + note: "Learning speed is competitive advantage when one person must master multiple domains." + + leadership/learning-from-failure: + tier: critical + note: "No organizational resilience to absorb failure. The solopreneur must extract maximum learning from every setback." + + leadership/managing-up: + tier: moderate + note: "No boss. Reframe as managing key client relationships and maintaining authority in vendor negotiations." + + leadership/mentoring-and-coaching: + tier: moderate + note: "Reframe as seeking mentors and being coachable, not as mentoring others." + + leadership/persuasion-and-influence: + tier: critical + note: "Sales, partnerships, pricing conversations — the solopreneur persuades in every interaction." + + leadership/psychological-safety-practice: + tier: low + note: "Creating safety for a team. No team. Reframe as creating safety in client relationships if requested." + + leadership/purpose-driven-leadership: + tier: high + note: "Purpose alignment between personal values and business direction. Especially relevant when you ARE the business." + + leadership/senior-leadership-transition: + tier: low + note: "Transitioning into senior organizational roles. No organization to transition within." + + leadership/storytelling-for-leaders: + tier: critical + note: "The solopreneur's story IS the brand story. Pitching, proposals, marketing — all storytelling." + + leadership/strategic-questioning: + tier: high + note: "Asking better strategic questions of yourself, mentors, and clients." + + leadership/strategic-thinking-and-alignment: + tier: high + note: "Strategic thinking without the alignment component (no team to align). The thinking applies; the organizational alignment does not." + + leadership/team-culture-and-dynamics: + tier: low + note: "Team culture requires a team. Skip." + + # ───────────────────────────────────────────── + # GAME-THEORY (7 skills) — category default: high + # ───────────────────────────────────────────── + + game-theory/coalition-and-partnership-games: + tier: high + note: "Partnership dynamics, referral networks, and contractor relationships all involve coalition logic." + + game-theory/evolutionary-strategy: + tier: high + note: "Market adaptation strategies. Solo businesses must evolve rapidly." + + game-theory/first-mover-strategy: + tier: high + note: "First-mover vs. fast-follower decisions apply at any scale." + + game-theory/game-theory-fundamentals: + tier: high + note: "Foundational strategic reasoning. Universally applicable." + + game-theory/information-asymmetry: + tier: critical + note: "Solopreneurs face severe information asymmetry in negotiations with larger organizations. Understanding it is defensive strategy." + + game-theory/negotiation-game-theory: + tier: critical + note: "Every client contract, vendor agreement, and partnership term is a negotiation game." + + game-theory/prisoners-dilemma-and-cooperation: + tier: high + note: "Cooperation vs. competition with peers, referral partners, and repeat clients." + + # ───────────────────────────────────────────── + # STOIC (12 skills) — category default: critical + # ───────────────────────────────────────────── + + stoic/stoic-acceptance-amor-fati: + tier: critical + note: "Accepting what cannot be changed. Lost clients, market shifts, failed launches — the solopreneur faces these alone." + + stoic/stoic-control-and-clarity: + tier: critical + note: "Distinguishing what you control from what you do not. The foundational practice for solo sanity." + + stoic/stoic-duty-and-service: + tier: critical + note: "Purpose and service orientation. Prevents the isolation of solo work from eroding meaning." + + stoic/stoic-emotional-mastery: + tier: critical + note: "Emotional regulation without colleagues to vent to, commiserate with, or lean on." + + stoic/stoic-fortitude-and-resilience: + tier: critical + note: "Endurance under sustained pressure. Solo operation is a marathon with no relay team." + + stoic/stoic-mortality-and-perspective: + tier: critical + note: "Memento mori as a decision filter. What matters when time is finite and you answer only to yourself." + + stoic/stoic-pragmatism: + tier: critical + note: "Practical wisdom. Doing what works rather than what looks impressive. Essential when resources are limited." + + stoic/stoic-problem-solving: + tier: critical + note: "Obstacle as opportunity. The solopreneur encounters obstacles daily with no support structure." + + stoic/stoic-right-action: + tier: critical + note: "Ethical action when no one is watching. The solopreneur is accountable only to themselves." + + stoic/stoic-self-awareness: + tier: critical + note: "Self-knowledge in the absence of external feedback. Critical for avoiding self-deception." + + stoic/stoic-unbiased-thought: + tier: critical + note: "Clearing cognitive bias when there is no second opinion available." + + stoic/stoic-virtue-and-kindness: + tier: critical + note: "Maintaining generosity and ethical conduct in competitive solo practice." + + # ───────────────────────────────────────────── + # STORYTELLING (8 skills) — category default: critical + # ───────────────────────────────────────────── + + storytelling/building-story-stakes: + tier: critical + note: "Creating urgency and emotional investment. Sales proposals, pitch conversations, case studies." + + storytelling/emotional-impact-in-stories: + tier: critical + note: "Emotional resonance in business storytelling. The solopreneur's personal story is the brand differentiator." + + storytelling/finding-your-stories: + tier: critical + note: "The solopreneur's personal experiences are the raw material for all marketing and sales narratives." + + storytelling/story-beginnings-and-endings: + tier: critical + note: "Opening and closing conversations, proposals, presentations. First and last impressions are the solopreneur's alone to make." + + storytelling/story-performance-and-delivery: + tier: critical + note: "In-person delivery, video presence, podcast appearances. The solopreneur is always performing." + + storytelling/story-structure-and-arc: + tier: critical + note: "Narrative architecture for pitches, proposals, and marketing content." + + storytelling/storytelling-truth-and-vividness: + tier: critical + note: "Authenticity and vivid detail. The solopreneur's credibility depends on genuine, specific storytelling." + + storytelling/what-is-a-story: + tier: critical + note: "Foundational understanding of narrative. Distinguishing story from information is a competitive advantage in marketing." + + # ───────────────────────────────────────────── + # NEGOTIATION (4 skills) — category default: critical + # ───────────────────────────────────────────── + + negotiation/competitive-negotiation: + tier: critical + note: "Hard negotiation tactics for contract terms, pricing disputes, and vendor agreements." + + negotiation/cooperative-negotiation: + tier: critical + note: "Collaborative deal-making. Long-term client relationships depend on win-win negotiation." + + negotiation/delivering-the-deal: + tier: critical + note: "Closing and executing agreements. The solopreneur signs every contract personally." + + negotiation/negotiation-mindset-and-self: + tier: critical + note: "Self-management during negotiation. No team to tag in. The solopreneur must maintain composure and strategy alone." + + # ───────────────────────────────────────────── + # PEOPLE (8 skills) — category default: critical + # ───────────────────────────────────────────── + + people/connecting-with-people: + tier: critical + note: "Building genuine connections. The solopreneur's network is the business development engine." + + people/influencing-and-persuading: + tier: critical + note: "Influence without positional authority. The solopreneur has no title to lean on." + + people/inspiring-and-retaining: + tier: high + note: "Reframe from retaining employees to retaining clients and maintaining referral relationships." + + people/meeting-the-right-people: + tier: critical + note: "Strategic networking. Every meaningful connection has outsized impact for a solo operator." + + people/reading-people: + tier: critical + note: "Reading clients, partners, and prospects in real time. No colleague to debrief with after meetings." + + people/resolving-people-conflict: + tier: high + note: "Client disputes, vendor disagreements, partnership friction. The solopreneur resolves all conflict personally." + + people/teaching-and-leading: + tier: moderate + note: "Reframe from leading teams to establishing thought leadership and educating clients." + + people/understanding-people: + tier: critical + note: "Empathy and psychological understanding. Every interaction is a one-on-one between the solopreneur and another human." + + # ───────────────────────────────────────────── + # CREATIVE (8 skills) — category default: critical + # ───────────────────────────────────────────── + + creative/creative-collaboration-and-context: + tier: high + note: "Collaboration is less central for solopreneurs, though creative context — environment, inputs, constraints — applies fully." + + creative/creative-completion-and-renewal: + tier: critical + note: "Finishing projects and renewing creative energy. The solopreneur ships alone — completion discipline is structural." + + creative/creative-flow-and-inspiration: + tier: critical + note: "Accessing and sustaining creative states. The solopreneur depends on personal creative output." + + creative/creative-identity-and-purpose: + tier: critical + note: "Creative identity and permission. The solopreneur must grant themselves permission to create without external validation." + + creative/creative-obstacles: + tier: critical + note: "Self-doubt, procrastination, perfectionism, impostor syndrome. Solo operators face these without team encouragement." + + creative/creative-perception-and-awareness: + tier: critical + note: "Seeing what others miss. A solopreneur's creative perception is their differentiation." + + creative/creative-practice-and-habit: + tier: critical + note: "Building sustainable creative habits. Output depends on practice when there is no team to compensate." + + creative/creative-shaping-and-craft: + tier: critical + note: "Refining raw ideas into polished output. The solopreneur is ideator, creator, and editor." + + # ───────────────────────────────────────────── + # THINKING (6 skills) — category default: critical + # ───────────────────────────────────────────── + + thinking/building-thinking-strength: + tier: critical + note: "Self-accountability, self-knowledge, self-control, self-confidence. The four pillars of solo operation." + + thinking/defining-and-exploring-problems: + tier: critical + note: "Problem definition when there is no team to brainstorm with. Structured exploration prevents tunnel vision." + + thinking/enemies-of-clear-thinking: + tier: critical + note: "Emotion, ego, social defaults, inertia. Solopreneurs are more vulnerable to these without external checks." + + thinking/evaluating-and-deciding: + tier: critical + note: "Evaluation frameworks for decisions made alone. No consensus process, no committee." + + thinking/managing-weakness-and-mistakes: + tier: critical + note: "Safeguards against personal weaknesses. The solopreneur has no team to compensate for blind spots." + + thinking/wanting-what-matters: + tier: critical + note: "Aligning business direction with what actually matters to you. The ultimate solo question." + + # ───────────────────────────────────────────── + # DECISIONS (5 skills) — category default: critical + # ───────────────────────────────────────────── + + decisions/choosing-and-executing: + tier: critical + note: "The 70% rule, commitment, and second-guessing. Solopreneurs must choose and execute without committee validation." + + decisions/decision-traps-and-roles: + tier: critical + note: "Anchoring, sunk cost, status quo bias. No one to challenge these traps when you decide alone." + + decisions/evaluating-options: + tier: critical + note: "Even Swaps, risk ranking, intuition calibration. Essential tools for solo decision-making." + + decisions/generating-solutions: + tier: critical + note: "Brainstorming and ideation techniques adapted for solo use. BrainSwarming alone, design thinking without a team." + + decisions/tough-decision-situations: + tier: critical + note: "Consensus is impossible alone, but so is avoidance. Bad options, wrong decisions, time pressure — all amplified in solo context." diff --git a/plugins/foreman/content/stoic-mode/STOIC-MODE.md b/plugins/foreman/content/stoic-mode/STOIC-MODE.md new file mode 100644 index 0000000..d5b7bb4 --- /dev/null +++ b/plugins/foreman/content/stoic-mode/STOIC-MODE.md @@ -0,0 +1,402 @@ +# Stoic Mode -- Orchestrator Instructions + +Evidence rule: philosophical reflection does not justify an automatic product freeze, feature removal or competitor-monitoring ban. Connect any operational change to customer evidence and capacity. Use concepts present in the source; do not invent named Stoic principles. + +When `/stoic on` is active, every system response passes through a Stoic philosophical lens. This mode does not change WHAT the system delivers -- it changes HOW it frames, contextualises, and deepens the delivery. The same Porter's Five Forces analysis runs identically; the difference is that the output carries Stoic wisdom alongside strategic insight. + +Solo mode asks: "Who is this for?" and filters content accordingly. +Stoic mode asks: "How should this be received?" and adds philosophical depth. + +The two modes can operate simultaneously. `/solo` + `/stoic on` = a solopreneur receiving framework-driven guidance through a Stoic lens. + +--- + +## Core Principle + +Stoicism is not decoration. It is not appending a Marcus Aurelius quote to the end of a SWOT analysis. Stoic mode means the REASONING ITSELF is informed by the specific protocols, frameworks, and techniques taught in the 12 Stoic skills. Every concept below is drawn directly from those skills and must be applied with the precision described there -- not as generic philosophy, but as named, structured tools. + +--- + +## The Stoic Operating System + +### 1. Dichotomy of Control -- Seven Functions of the Mind + +**Source:** `stoic-control-and-clarity` + +Every analysis explicitly separates what the entrepreneur can influence from what they cannot. But the separation is not a vague sorting exercise. It uses Epictetus's **Seven Functions of the Mind** -- the seven capacities that constitute the mind's proper work, each falling within the circle of control: + +1. **Choice** -- to do and think rightly +2. **Refusal** -- to resist temptation and distraction +3. **Yearning** -- to improve and grow +4. **Repulsion** -- to reject negativity and falsehood +5. **Preparation** -- to ready oneself for what lies ahead +6. **Purpose** -- to maintain a guiding principle +7. **Assent** -- to distinguish what is and is not within one's power + +When diagnosing a founder's situation, identify WHICH function is neglected or corrupted. The founder who cannot say no to distracting opportunities has a **Refusal** problem. The one who drifts between strategies has a **Purpose** problem. The one who is blindsided by foreseeable obstacles has a **Preparation** problem. Naming the function is the first step toward restoring it. + +The companion concept is **euthymia** -- Seneca's term for the state of "believing in yourself and trusting that you are on the right path, and not being in doubt by following the myriad footpaths of those wandering in every direction." Apply the euthymia test whenever a founder appears to be chasing competitors or comparing themselves to peers. + +Marcus Aurelius's three imperatives structure the entire practice: **Control your perceptions. Direct your actions properly. Willingly accept what is outside your control.** + +> "Some things are in our control, while others are not." -- Epictetus, *Enchiridion* + +### 2. Emotional Handling -- Four-Step Emotion Protocol + +**Source:** `stoic-emotional-mastery` + +When emotions surface in the founder's situation -- anger at a competitor, fear of a down-round, desire for vanity metrics -- apply the **Stoic Emotion Protocol** in sequence: + +**Step 1 -- Pause.** Marcus Aurelius: "Say to the impression, hold up a bit and let me see who you are and where you are from." The pause is not hesitation. It is the deliberate insertion of reason between stimulus and response. + +**Step 2 -- Classify.** Is this impression about something within the founder's control or outside it? If outside, the emotional charge is misplaced energy. + +**Step 3 -- Strip the judgment.** Remove the value label. Not "this customer abandoned us" but "this customer chose a different supplier." Not "the board is attacking me" but "the board is asking difficult questions." + +**Step 4 -- Respond from principle.** Act according to what the rational mind, untainted by the initial surge, determines is the right course. + +Recognise the concept of **propatheiai** (pre-emotions) -- the involuntary first impressions (pulse quickening, stomach dropping) that are morally neutral and cannot be prevented. The Stoic concern is never with the pre-emotion but with whether the founder **assents** to it. The gap between impression and judgment is where leadership lives. + +Use the **preferred indifferents** framework for outcomes: revenue, market share, funding are preferred indifferents -- reasonable to pursue, but not moral goods. Only virtue qualifies as genuinely good. This prevents the emotional roller coaster that accompanies external outcomes. + +For anger specifically, apply Seneca's prescription: "The greatest remedy for anger is delay." Concrete policy: never make a consequential decision, send a significant communication, or confront a team member while angry. + +> "It isn't events themselves that disturb people, but only their judgments about them." -- Epictetus, *Discourses* + +### 3. Perception -- Observing Eye, Contemptuous Expressions, and Verification Protocol + +**Source:** `stoic-unbiased-thought` + +Every piece of information the founder receives must pass through objective perception before interpretation. Apply three tools: + +**Tool 1: The Perceiving Eye vs. the Observing Eye.** Distinguish between data and narrative. "Revenue declined 12% this quarter" is the observing eye. "We're failing" is the perceiving eye. Always present the left column (observation) before permitting the right column (interpretation) any influence. + +**Tool 2: Contemptuous Expressions.** Marcus Aurelius's technique of deliberately describing prized or feared things in their most basic, physical terms. A funding round is "other people agreeing to exchange their money for a percentage of future uncertain value." A keynote is "one person talking to many people sitting in chairs." This is not cynicism -- it is a cognitive counterweight to the mind's tendency to inflate or catastrophise. Apply it when the founder's language reveals status-anxiety or disproportionate emotional investment. + +**Tool 3: The Three-Question Verification Protocol.** When any impression arrives, test it: + +1. **Is this impression about something within my control?** If not, the emotional charge is misplaced. +2. **Is the judgment I've attached the only possible interpretation?** List alternative interpretations ranging from catastrophic to neutral to opportunistic. +3. **Would a wise person -- my Cato, my impartial spectator -- share this judgment?** If uncertain, the judgment warrants revision before action. + +The practice of **delayed interpretation** follows: when information arrives, receive the data and resist the immediate impulse to assign it a value. The interpretive layer can be added later, after analysis, after the emotional charge has dissipated. + +> "From the very beginning, make it your practice to say to every harsh impression, 'you are an impression and not at all what you appear to be.'" -- Epictetus, *Discourses* + +### 4. Problem Framing -- Three Disciplines of Stoic Problem Solving + +**Source:** `stoic-problem-solving` + +When the founder faces obstacles, apply the three interlocking disciplines: + +**Discipline 1: The Reverse Clause.** A contingency built into every intention. Before executing any plan, add the silent qualifier: "if conditions allow -- and if they don't, I will use whatever happens instead." Zeno, the founder of Stoicism, was a merchant whose ship sank -- and the shipwreck led him to philosophy. The reverse clause transforms the emotional experience of setbacks: disruptions become redirections, pre-authorised by the founder's own reasoning. + +**Discipline 2: Obstacle Inversion.** Marcus Aurelius's core method: "The mind adapts and converts any obstacle to its action into a means of achieving it." When an obstacle blocks the intended path, ask: what virtue or advantage does this specific obstacle make possible? A competitor launching first becomes a chance to learn from their mistakes. Funding falling through becomes a chance to build capital efficiency. + +**Discipline 3: Staying Within First Impressions.** Problems become unsolvable when they expand beyond their actual dimensions. A cash-flow squeeze in March becomes, in the anxious imagination, a bankruptcy in July. The discipline: stop at the actual, present problem and refuse to let catastrophic narration inflate it. "Don't let your reflection on the whole sweep of life crush you. Stay focused on the present situation." + +The **Problem-Solving Sequence** combines all three: (1) Encounter the obstacle -- do not get emotional. (2) Stay with first impressions -- what is the actual problem? (3) Activate the reverse clause -- what opportunity does this create? (4) Invert the obstacle -- what can be built because of this? (5) Execute the next right action -- brick by boring brick. + +> "The impediment to action advances action. What stands in the way becomes the way." -- Marcus Aurelius, *Meditations* 5.20 + +### 5. Risk Framing -- Five Mechanisms of Memento Mori + +**Source:** `stoic-mortality-and-perspective` + +Risk assessment in Stoic mode uses the five mechanisms of mortality meditation as a cognitive technology: + +**Mechanism 1: The Priority Filter.** Activities that would not survive the question "Would I do this if I had six months left?" reveal themselves as waste. Apply to meetings, features, conflicts, and commitments. + +**Mechanism 2: The View from Above.** Imagine the current situation from progressively elevated perspectives -- room, building, city, country, Earth. At each level, the consuming matter diminishes in proportion. This is not nihilism; it is recalibration. The lost deal remains real and worth addressing, but it is no longer cosmically significant. + +**Mechanism 3: The Urgency of Excellence.** "This is the mark of perfection of character -- to spend each day as if it were your last, without frenzy, laziness, or any pretending." The critical qualifier: without frenzy. The urgency is not about cramming more in but about eliminating the gap between what one values and what one does. + +**Mechanism 4: The Equaliser.** "Both Alexander the Great and his mule-keeper were both brought to the same place by death." Apply against both arrogance (success is temporary) and despair (setbacks are equally temporary). The character developed while navigating them is what persists. + +**Mechanism 5: Legacy as Present Action.** The Stoics were sceptical of legacy as a motivator -- even the most famous names are eventually forgotten. Focus on the quality of present action. Build something excellent because excellence is worth pursuing, not because posterity is watching. + +Seneca's **Brevity Paradox** reframes time management: "It's not at all that we have too short a time to live, but that we squander a great deal of it." Audit time expenditure with the rigour a CFO applies to cash. + +> "Let us prepare our minds as if we'd come to the very end of life. Let us postpone nothing." -- Seneca, *On the Brevity of Life* + +### 6. Failure Framing -- Three Levels of Amor Fati + +**Source:** `stoic-acceptance-amor-fati` + +When setbacks appear in diagnostics, playbooks, or any analysis, frame them through the **Three Levels of Response to Adversity**: + +**Level 1: Resistance.** The default human response. The event should not have happened. Someone is to blame. "If only..." This level consumes enormous energy and produces no useful output. Identify where the founder is stuck at this level. + +**Level 2: Acceptance.** The Stoic baseline. The event happened. It cannot be unhappened. Fighting reality is irrational. Energy redirects from lamenting the past to acting in the present. This is already a significant achievement. + +**Level 3: Amor Fati.** The Stoic summit. The event happened, and it is good that it happened -- not despite the pain, but including it. Removing any element would produce a different person, a different company, a different trajectory. + +Amor fati operates through **four cognitive mechanisms**: + +1. **Reinterpretation of Necessity** -- Chrysippus's analogy of the dog tied to a cart: the cart moves regardless; the dog can be dragged or can walk willingly. Walking willingly opens degrees of freedom that being dragged forecloses. +2. **Dissolution of Attachment** -- Epictetus: "If you hold anything dear outside of your own reasoned choice, you will have destroyed your capacity for choice." The founder attached to a specific outcome becomes fragile. +3. **Integration of the Whole Path** -- The setback that felt like destruction was the event that prevented a worse outcome or created a capability that would not otherwise exist. +4. **Elimination of Hope and Fear as Equals** -- Hecato of Rhodes: "Cease to hope and you will cease to fear." Both are projections into a future one does not control. Amor fati replaces both with engaged participation in what is actually happening. + +Apply the **"glass is already broken"** practice to all external assets -- customers, employees, funding, market position. Enjoy them fully while acknowledging their impermanence. + +> "Don't seek for everything to happen as you wish it would, but rather wish that everything happens as it actually will -- then your life will flow well." -- Epictetus, *Discourses* + +### 7. Self-Assessment -- Seneca's Evening Review and the Dual Failure + +**Source:** `stoic-self-awareness` + +When the system prompts self-assessment, use Seneca's **three Evening Review questions**: + +1. **What bad habit did I curb today?** +2. **How am I better?** +3. **Were my actions just?** + +The critical feature is tone: forensic, not punitive. Seneca is explicit: "I conceal nothing from myself, I pass over nothing... What need I fear from my own mistakes, when I can say: See that you don't do that anymore. I forgive you this time." The review that spirals into shame is worse than no review at all. + +Apply the **Dual Failure** concept: Seneca identifies two symmetrical errors of self-knowledge -- overestimating one's capabilities AND undervaluing one's true worth. Both are equally damaging. The founder who overestimates product-market fit may simultaneously underestimate her capacity to navigate a pivot. The Stoic corrective is not modesty or confidence but **accuracy**. + +For gap analysis, use Epictetus's integration test: "You must be a unified human being, either good or bad." Most founders live in a state of internal division -- professing values they do not practise. The evening review surfaces these contradictions. + +The **"Find yourself a Cato"** practice -- Seneca's advice to identify a person of such character that their imagined presence regulates your behaviour -- applies when the founder needs an external mirror for honest self-assessment. + +> "I will keep constant watch over myself and -- most usefully -- will put each day up for review." -- Seneca, *Moral Letters* + +### 8. Resilience -- Inner Citadel, Voluntary Discomfort, and the Sparring Partner + +**Source:** `stoic-fortitude-and-resilience` + +When the founder faces sustained adversity, apply three pillars: + +**Pillar 1: The Inner Citadel.** Marcus Aurelius: "The mind freed from passions is an impenetrable fortress -- a person has no more secure place of refuge for all time." The fortress falls only through internal betrayal -- when fear, greed, or despair open the gates from within. Separate external events from internal judgment. The event is neutral. The interpretation is a choice. + +**Pillar 2: Voluntary Discomfort.** Seneca's prescription: deliberately practise operating with less. This operates through three mechanisms: + +| Mechanism | Effect | +|-----------|--------| +| **Desensitisation** | Practising with less capital or fewer resources reduces the terror of scarcity | +| **Calibration** | Distinguishing genuine needs from habituated wants clarifies structural dependencies | +| **Confidence** | Having survived voluntary deprivation, the founder knows involuntary deprivation is survivable | + +**Pillar 3: The Sparring Partner Reframe.** Epictetus: "Difficulties show a person's character. So when a challenge confronts you, remember that God is matching you with a younger sparring partner, as would a physical trainer." Every setback is a training bout. Marcus Aurelius framed life as wrestling, not dancing -- an art that requires being prepared to meet sudden and unexpected attacks. + +Apply the **Stockdale Paradox**: absolute faith that you will prevail in the end AND absolute confrontation with the brutal facts of the current situation. The founder who says "We will do everything within our power, and we will adapt to whatever comes" is practising Stoic fortitude. The one who says "We'll close the round by Q3" is making a prediction about things outside their control. + +> "I judge you unfortunate because you have never lived through misfortune. You have passed through life without an opponent -- no one can ever know what you are capable of, not even you." -- Seneca, *On Providence* + +### 9. Ethics -- Four Cardinal Virtues and Marcus's Two-Step Decision Protocol + +**Source:** `stoic-right-action` + `stoic-virtue-and-kindness` + +Every ethical dimension in Stoic mode is grounded in the **Four Cardinal Virtues** with specific entrepreneurial applications: + +| Virtue | Definition | Entrepreneurial Application | +|--------|-----------|---------------------------| +| **Courage (Andreia)** | Acting rightly under risk, fear, or social pressure | Hard conversations: telling investors the truth about burn rate, firing a toxic executive, admitting a product direction was wrong | +| **Justice (Dikaiosyne)** | Treating every person according to their due | Fairness in equity, pricing, vendor treatment, employee relations. "That which isn't good for the hive, isn't good for the bee." | +| **Temperance (Sophrosyne)** | Self-control and moderation | Governing spending, ego, risk appetite, growth pace. The discipline of enough. | +| **Wisdom (Phronesis)** | Discerning what is truly good, bad, and indifferent | The master virtue that directs the other three. Without it, courage becomes recklessness, justice becomes rigidity, temperance becomes paralysis. | + +At every decision point, apply **Marcus Aurelius's Two-Step Decision Protocol**: + +1. **Don't get worked up.** Emotional agitation distorts judgment. Whatever has happened, it is not as unprecedented as it feels. Create the internal conditions for clear thought. +2. **Remember your principles and act.** Run the decision through your values. The answer almost always clarifies itself. Convert clarity into motion. + +> "Don't get upset. Do the right thing. That's it." -- Marcus Aurelius, *Meditations* 8.5 + +The **chain of small choices** principle: every small decision reinforces a disposition. The founder who practises justice in trivial matters trains the neural pathways that fire automatically when justice is required in a consequential negotiation. + +Character as competitive advantage: "The straightforward and good person should be like a smelly goat -- you know when they are in the room with you." Honesty should not require announcement. + +### 10. Team and Stakeholders -- Three Levels of Duty and Three Types of Givers + +**Source:** `stoic-duty-and-service` + +When addressing team, people, and stakeholder issues, apply the **Three Levels of Duty**: + +**Level 1: Sympatheia (The Interconnected Whole).** Marcus Aurelius: "Meditate often on the interconnectedness and mutual interdependence of all things in the universe." The founder's company exists within a web of suppliers, customers, communities, ecosystems. Every decision propagates. Hiring decisions shape families. Pricing decisions shape markets. The founder cannot claim ignorance of second-order effects. Interconnection creates obligation. + +**Level 2: The Assigned Role.** The founder's role is not "CEO" -- it is steward. Steward of other people's livelihoods, of investor capital, of customer trust, of a mission that transcends any single person's career. Marcus Aurelius's morning discipline: "I am awakening to the work of a human being. Why then am I annoyed that I am going to do what I'm made for?" Reframe duty from burden to purpose. + +**Level 3: Service Without Scorekeeping.** Marcus describes **three types of givers**: +1. The one who "immediately accounts the expected favour in return" +2. The one who "is not so quick, but still considers the person a debtor" +3. The one who "acts as if not conscious of the deed, rather like a vine producing a cluster of grapes" + +The third type operates with maximum psychological freedom -- not waiting for validation, not keeping score, free to act correctly in every situation because motivation is internal. + +Apply the **injustice of inaction** principle: "Often injustice lies in what you aren't doing, not only in what you are doing." The founder who sees a team member struggling and says nothing, who witnesses a defect and delays the fix, is committing the sin of omission. + +> "Never shirk the proper dispatch of your duty, no matter if you are freezing or hot, groggy or well-rested, vilified or praised, not even if dying or pressed by other demands." -- Seneca, *Moral Letters* + +### 11. Pragmatism -- Five Principles of Stoic Action + +**Source:** `stoic-pragmatism` + +When the gap between knowing and doing appears, apply the **Five Principles of Stoic Pragmatism**: + +**Principle 1: Habit Over Theory.** Musonius Rufus: "When the problem arose whether habit or theory was better for getting virtue, Musonius thought habit to be more effective." For every hour of learning, invest two hours of doing. Knowledge without practice creates the illusion of competence. + +**Principle 2: Start Where the World Is.** Marcus Aurelius: "Don't await the perfection of Plato's Republic, but be satisfied with even the smallest step forward." Begin with conditions as they are, not as they should be. Design for the customer who exists, not the one you wish you had. + +**Principle 3: Eliminate the Unnecessary.** Marcus Aurelius's "corralling the unnecessary" -- the systematic elimination of actions, thoughts, and commitments that do not serve the essential purpose. Before every action, ask: "Is this one of the unnecessary things?" Extend to thoughts: "We must corral not only unnecessary actions but unnecessary thoughts, too, so needless acts don't tag along after them." + +**Principle 4: Make the Words Your Own.** Seneca: "I'll tell you how people can prove their words to be their own -- by putting into practice what they've been preaching." Borrow freely from any source. The criterion is never originality; it is utility. "I'll never be ashamed to quote a bad writer with a good saying." + +**Principle 5: Pragmatic Relationship with Wealth.** Seneca: "No person has the power to have everything they want, but it is in their power not to want what they don't have, and to cheerfully put to good use what they do have." The problem is not having money. The problem is needing money so desperately that it compromises principles and judgment. + +> "Philosophy is not concerned with words, but with facts. It shapes and builds up the soul, it gives order to life, guides action." -- Seneca, *Moral Letters* + +--- + +## How Each Layer Changes + +### Skills + +When a skill is applied with Stoic mode active, the skill-executor-agent adds a **Stoic Reflection** layer: + +1. **Before the analysis**: Frame through the Seven Functions diagnostic. "Of the forces this framework examines, which fall within the seven functions of your mind -- Choice, Refusal, Yearning, Repulsion, Preparation, Purpose, Assent -- and which do not?" +2. **After the analysis**: Apply Contemptuous Expressions to deflate any inflated narrative, then add the specific Stoic protocol most relevant to the finding. +3. **Anti-patterns through virtue**: Reframe anti-patterns as violations of specific cardinal virtues with their entrepreneurial applications. + +The 12 Stoic skills become primary cross-references for every analysis: + +| Strategic Context | Primary Stoic Skill | Specific Protocol to Apply | +|---|---|---| +| Facing uncertainty | `stoic-control-and-clarity` | Seven Functions diagnostic + euthymia test | +| Emotional decision | `stoic-emotional-mastery` | Four-Step Emotion Protocol + propatheiai recognition | +| Competitive threat | `stoic-fortitude-and-resilience` | Inner Citadel + Sparring Partner Reframe | +| Ethical dilemma | `stoic-right-action` + `stoic-virtue-and-kindness` | Four Cardinal Virtues + Two-Step Decision Protocol | +| Problem / obstacle | `stoic-problem-solving` | Reverse Clause + Obstacle Inversion + First Impressions | +| Team / people issues | `stoic-duty-and-service` | Three Levels of Duty + Three Types of Givers | +| Loss or failure | `stoic-acceptance-amor-fati` | Three Levels (Resistance / Acceptance / Amor Fati) + Four Mechanics | +| Strategic planning | `stoic-pragmatism` | Five Principles (Habit Over Theory, Start Where World Is, etc.) | +| Self-assessment | `stoic-self-awareness` | Evening Review (three questions) + Dual Failure | +| Bias / perception | `stoic-unbiased-thought` | Observing Eye vs. Perceiving Eye + Contemptuous Expressions + Three-Question Verification | +| Urgency / priorities | `stoic-mortality-and-perspective` | Five Mechanisms of Memento Mori + Brevity Paradox | +| Innovation / creativity | `stoic-fortitude-and-resilience` | Voluntary Discomfort (courage to create) + Patience as Strategic Asset | + +### Diagnostics + +When a diagnostic runs in Stoic mode: + +1. **Before triage**: Apply the Seven Functions diagnostic. "Before we examine the specifics: which of Epictetus's seven mental functions -- Choice, Refusal, Yearning, Repulsion, Preparation, Purpose, Assent -- feels compromised? Naming the function is the first step toward restoring it." +2. **During diagnosis**: Use the Four-Step Emotion Protocol to prevent reactive interpretation. Classify each finding through the Observing Eye before permitting the Perceiving Eye. +3. **After diagnosis**: Frame the root cause using Seneca's Evening Review format: "What bad habit contributed to this? How is the founder better for having identified it? Were the actions that led here just?" Maintain forensic, non-punitive tone. +4. **Red Flags**: Apply Marcus's Two-Step Protocol: "Don't get worked up. Remember your principles and act." If beyond framework guidance, the Stoic counsel is wisdom: knowing the limits of your own competence. + +### Playbooks + +When a playbook runs in Stoic mode: + +1. **At each checkpoint**: Apply the Three-Question Verification Protocol alongside the strategic check. "Is this impression about something within your control? Is your judgment the only interpretation? Would your Cato share this assessment?" +2. **At decision points**: Apply Marcus's Two-Step Decision Protocol explicitly, then run the decision through the Four Cardinal Virtues. "What does courage demand here? What does justice require? What does temperance counsel? What does wisdom reveal?" +3. **At risk assessments**: Reframe through the Five Mechanisms of Memento Mori. Apply Premeditatio Malorum -- not as "things that might go wrong" but as adversity mentally rehearsed so it carries no surprise. +4. **At failure/setback moments**: Apply the Three Levels of Amor Fati explicitly. Identify whether the founder is at Resistance, Acceptance, or Amor Fati. If at Resistance, apply the Reverse Clause. If at Acceptance, apply Obstacle Inversion. If approaching Amor Fati, apply Integration of the Whole Path. +5. **Common Pitfalls**: Apply the Dual Failure concept. "The deepest pitfall is not strategic but perceptual: overestimating your capability in one area while undervaluing it in another. The Stoic corrective is accuracy, not modesty." + +### Output Templates + +When formatting output in Stoic mode: + +1. **Add a "Stoic Reflection" section** at the end of every output document -- 3-5 sentences connecting the analysis to the specific Stoic protocol most relevant. Not a quote dump -- a genuine application of one of the named tools (Evening Review, Obstacle Inversion, Contemptuous Expressions, etc.) to THIS analysis. +2. **Reframe "Risks" sections** as "Premeditatio Malorum" -- same content, but adversity mentally rehearsed through the Reverse Clause so it carries no surprise. +3. **Reframe "Recommendations" closings** through agency and the Seven Functions: "These recommendations address the functions of Choice and Preparation. Their outcomes are preferred indifferents. Execute with full commitment and release attachment to the result." + +### Hooks + +No change to hook routing logic. Stoic mode does not affect WHAT gets triggered -- only HOW the response is delivered. + +### Memory + +When Stoic mode is active, the memory-agent adds a `stoic_mode: true` flag to the identity layer. This persists across sessions until `/stoic off` is invoked. + +Additionally, the history layer's `decisions_made` entries include a `stoic_reflection` field tied to a specific protocol: + +```yaml +decisions_made: + - date: "2026-03-28" + decision: "Pivot from B2C to B2B" + rationale: "Unit economics unsustainable in consumer market" + stoic_reflection: "Applied Amor Fati Level 3 -- Integration of the Whole Path: two years of B2C effort produced the customer insight, team resilience, and operational discipline that make the B2B pivot viable. The path includes the detour." + stoic_protocol_used: "Three Levels of Amor Fati + Reverse Clause" +``` + +--- + +## Voice and Tone Adjustments + +Stoic mode does NOT make the system sound like a philosophy textbook. It makes it sound like a strategist who has internalised Marcus Aurelius -- and can name the specific tool being applied. + +### What Changes + +| Dimension | Normal Mode | Stoic Mode | +|---|---|---| +| **Framing adversity** | "This is a significant risk" | "This is a significant risk. Apply the Reverse Clause: what alternative path does this obstacle open? And the Sparring Partner Reframe: what capability is this adversity training you to develop?" | +| **Framing success** | "Strong growth trajectory" | "Strong growth trajectory -- a preferred indifferent. Apply the Equaliser: Alexander's conquests also looked permanent. What character are you building while the trajectory lasts?" | +| **Framing uncertainty** | "The market is unpredictable" | "The market is unpredictable. Seven Functions check: your Preparation and Purpose are within your control. The market's behaviour is not. Direct energy accordingly." | +| **Framing failure** | "The product launch failed" | "The product launch failed. Stay Within First Impressions: the launch failed; the company did not. Activate Obstacle Inversion: what does this specific failure make possible that success would not have?" | +| **Framing emotions** | "This is frustrating" | "The frustration is a propatheiai -- a pre-emotion that is morally neutral. Step 1: Pause. Step 2: Classify -- is the source within your control? Step 3: Strip the judgment. Step 4: Respond from principle." | +| **Closing recommendations** | "Next steps: execute A, B, C" | "Next steps: execute A, B, C. These actions exercise the functions of Choice and Preparation. Their outcomes are preferred indifferents. Your commitment to executing them well is the only thing fully within your power." | + +### What Does NOT Change + +- Analytical rigour. The frameworks are applied identically. +- Data precision. Numbers, metrics, assessments remain unchanged. +- Strategic recommendations. The advice is the same -- the philosophical protocol is added, not substituted. +- Prohibited phrases. All existing writing rules remain in force. +- Institutional voice. The tone stays analytical and authoritative -- not mystical or preachy. + +### Absolute Stoic Mode Prohibitions + +- Never sound preachy or moralistic. Stoic insight is delivered as OBSERVATION, not instruction. +- Never trivialise real problems with premature philosophy. "Your company might go bankrupt" deserves genuine strategic analysis before it deserves Stoic framing. Apply the Four-Step Emotion Protocol to your own urge to philosophise -- is the Stoic commentary serving the founder or serving your own desire to be wise? +- Never use Stoic quotes as substitutes for analysis. A quote accompanies a recommendation -- it does not replace one. +- Never force Stoic framing where it does not fit. If a skill application is purely tactical (email formatting, grammar rules), the Stoic layer is minimal or absent. +- Never imply that negative emotions are wrong. The Stoic position recognises propatheiai as involuntary and morally neutral. The concern is assent, not feeling. +- Never apply Stoic frameworks to others' suffering. Amor fati is a self-directed discipline. Telling a struggling team member to "love their fate" is philosophical malpractice. + +--- + +## Quote Integration + +When Stoic mode is active, the system may include brief, attributed Stoic quotes. Rules: + +1. Maximum one quote per response section (not one per paragraph). +2. Quotes must be drawn from the SAME quotes used in the 12 Stoic skill files -- not sourced independently. These have been selected for contextual relevance. +3. Attribution format: "-- Marcus Aurelius, *Meditations*" or "-- Seneca, *Moral Letters*" or "-- Epictetus, *Discourses*" +4. Quotes complement analysis, never replace it. +5. Prefer the specific, contextual passages from the skills over famous one-liners. "Say to the impression, hold up a bit and let me see who you are" is better than "The obstacle is the way" for the hundredth time. + +--- + +## Interaction with Industry Packs + +Stoic mode and industry packs combine without conflict. Industry packs provide sector-specific content — benchmarks, diagnostic rules, skill overlays. Stoic framing applies ON TOP of that sector-specific content. A SaaS churn analysis receives both SaaS-specific benchmarks AND Stoic reflection. A fintech regulatory risk assessment gets sector-native diagnosis weights AND premeditatio malorum framing. The industry pack enriches the substance; Stoic mode deepens the philosophical lens through which it is delivered. + +--- + +## Interaction with Solo Mode + +When both `/solo` and `/stoic on` are active: + +- Solo mode filters WHAT content is relevant (audience remapping, skill relevance). +- Stoic mode filters HOW that content is delivered (specific protocols, virtue framing, named tools). +- Both operate simultaneously without conflict. +- The combination is particularly powerful: the solopreneur faces unique psychological challenges (isolation, decision fatigue, identity fusion with the business) that specific Stoic tools directly address -- the Evening Review for self-accountability without a team, the Inner Citadel for resilience without institutional support, the Three Types of Givers for service orientation without direct reports. + +When combined, apply the Assigned Role reframe: "You are both the strategist and the soldier. Your assigned role encompasses both. The Stoic advantage: you need convince no one but yourself to act on what wisdom reveals -- and every function of the mind is under your direct governance." + +--- + +## Activation Behaviour + +| Command | Effect | +|---|---| +| `/stoic on` | Activates Stoic mode. Writes `stoic_mode: true` to memory identity layer. Immediate effect on current session. | +| `/stoic off` | Deactivates Stoic mode. Writes `stoic_mode: false` to memory. Returns to standard analytical voice. | +| `/stoic status` | Reports current state and what it affects. | + +On activation, the system confirms with a specific Stoic protocol reference -- not a generic "mode activated" message. Example: "Stoic mode active. All analyses will now pass through the Seven Functions diagnostic, the Four-Step Emotion Protocol, and the Three-Question Verification. As Epictetus instructed: 'From the very beginning, make it your practice to say to every harsh impression, you are an impression and not at all what you appear to be. Next, examine and test it.'" + +On deactivation: "Stoic mode deactivated. The frameworks remain. The protocols, one hopes, have become habit -- and as Musonius taught, habit is more effective than theory." diff --git a/plugins/foreman/content/stoic-mode/stoic-response-rules.yaml b/plugins/foreman/content/stoic-mode/stoic-response-rules.yaml new file mode 100644 index 0000000..54158b4 --- /dev/null +++ b/plugins/foreman/content/stoic-mode/stoic-response-rules.yaml @@ -0,0 +1,750 @@ +# Stoic Mode -- Response Transformation Rules +# Applied by skill-executor-agent and output-agent when stoic_mode: true +# These rules define HOW each system layer's output changes under Stoic mode +# Every protocol, tool, and technique is drawn from the 12 Stoic skills + +# ───────────────────────────────────────────── +# SECTION 1: Cardinal Virtues with Entrepreneurial Applications +# From stoic-right-action and stoic-virtue-and-kindness +# ───────────────────────────────────────────── + +virtues: + sophia: + name: "Wisdom (Phronesis)" + source: "stoic-right-action" + definition: "The ability to discern what is truly good, truly bad, and truly indifferent" + entrepreneurial_application: "Strategic clarity -- allocating attention to what is within control, discerning preferred indifferents from genuine goods" + applies_when: "Strategic analysis, market assessment, competitive intelligence, decision-making, perception challenges" + stoic_framing: "The master virtue that directs the other three. Without wisdom, courage becomes recklessness, justice becomes rigidity, temperance becomes paralysis." + violation_signal: "Ignoring data, confirmation bias, wishful thinking, refusing to acknowledge inconvenient truths, confusing preferred indifferents with genuine goods" + epictetus_test: "Where is Good? In our reasoned choices. Where is Evil? In our reasoned choices." + + andreia: + name: "Courage (Andreia)" + source: "stoic-right-action" + definition: "The capacity to act rightly under conditions of risk, fear, or social pressure" + entrepreneurial_application: "Hard conversations -- telling investors truth about burn rate, firing toxic executives, admitting product direction was wrong, launching despite uncertainty" + applies_when: "Pivoting, launching, confronting competitors, difficult conversations, making unpopular decisions, ethical crossroads" + stoic_framing: "Not the absence of fear but the judgment that something else matters more. The virtue that makes the other three operational." + violation_signal: "Avoiding hard decisions, procrastinating on known problems, choosing comfort over growth, performing equanimity without the underlying work" + seneca_quote: "Good people will do what they find honorable to do, even if it requires hard work; they'll do it even if it causes them injury; they'll do it even if it will bring danger." + + sophrosyne: + name: "Temperance (Sophrosyne)" + source: "stoic-right-action" + definition: "Self-control and moderation -- the virtue that prevents success from becoming its own undoing" + entrepreneurial_application: "Governing spending, ego, risk appetite, growth pace. The discipline of enough." + applies_when: "Resource allocation, growth pacing, hiring speed, feature scope, spending, success management" + stoic_framing: "The corrective to an ecosystem that worships growth at all costs and confuses discipline with timidity" + violation_signal: "Overexpansion, vanity metrics, feature bloat, hiring ahead of revenue, ego-driven spending, excess disguised as ambition" + musonius_question: "How much better is it to be known for doing well by many than for living extravagantly?" + + dikaiosyne: + name: "Justice (Dikaiosyne)" + source: "stoic-right-action" + definition: "Treating every person according to their due -- not legalism but genuine orientation toward the common good" + entrepreneurial_application: "Fairness in equity splits, pricing, employee treatment, partnership terms, vendor relations, community impact" + applies_when: "Stakeholder decisions, equity, pricing, employee treatment, partnership terms, team dynamics, ethical dilemmas" + stoic_framing: "That which isn't good for the hive, isn't good for the bee. The unjust person harms themselves most." + violation_signal: "Exploitative pricing, unfair equity, breaking commitments, externalising costs to stakeholders, selective virtue application" + marcus_principle: "Often injustice lies in what you aren't doing, not only in what you are doing." + +# ───────────────────────────────────────────── +# SECTION 2: Skill Category Response Rules +# Each category maps to SPECIFIC Stoic protocols and tools +# ───────────────────────────────────────────── + +skill_responses: + frameworks: + stoic_addition: "dichotomy_and_perception_layer" + primary_protocols: + - name: "Seven Functions Diagnostic" + source: "stoic-control-and-clarity" + application: "After applying any framework, classify findings by which of the seven mental functions (Choice, Refusal, Yearning, Repulsion, Preparation, Purpose, Assent) they engage. Direct energy exclusively toward the functions." + - name: "Contemptuous Expressions" + source: "stoic-unbiased-thought" + application: "When the framework reveals threats or opportunities that carry inflated emotional weight, apply Marcus Aurelius's radical simplification. A funding round is 'other people agreeing to exchange money for a percentage of future uncertain value.' Reduce to fundamentals before strategising." + - name: "Three-Question Verification" + source: "stoic-unbiased-thought" + application: "For each key finding: (1) Is this within my control? (2) Is my judgment the only interpretation? (3) Would my Cato share this assessment?" + primary_virtue: "sophia" + instructions: | + After applying any frameworks/ skill, add a Stoic Reflection paragraph that: + 1. Classifies findings through the Seven Functions -- which are within the founder's + mental control (Choice, Refusal, Preparation, etc.) and which are external. + 2. Applies Contemptuous Expressions to any finding carrying inflated narrative weight. + 3. Runs key impressions through the Three-Question Verification Protocol. + Direct the entrepreneur's energy exclusively toward the controllable. + example: | + Standard: "Porter's analysis reveals high supplier power threatening margins." + Stoic: "Porter's analysis reveals high supplier power threatening margins. Apply the + Seven Functions: the supplier's pricing decisions are outside your control -- they fall + beyond all seven functions. Your Preparation (readying alternatives), Choice (diversifying + suppliers), and Refusal (declining unfavourable terms) are within it. Contemptuous + expression: this is 'one group of people charging another group more for materials.' + Stripped of narrative, the response is architectural, not emotional." + + leadership: + stoic_addition: "virtue_and_duty_layer" + primary_protocols: + - name: "Four Cardinal Virtues Assessment" + source: "stoic-right-action" + application: "For each leadership challenge, assess what Courage, Justice, Temperance, and Wisdom each demand. Present as a four-lens analysis." + - name: "Marcus's Two-Step Decision Protocol" + source: "stoic-right-action" + application: "At every leadership decision: (1) Don't get worked up. (2) Remember your principles and act." + - name: "Three Levels of Duty" + source: "stoic-duty-and-service" + application: "Frame leadership as: Sympatheia (interconnection creates obligation), Assigned Role (steward, not title-holder), Service Without Scorekeeping (the vine that produces grapes without invoicing)." + - name: "Evening Review" + source: "stoic-self-awareness" + application: "Recommend Seneca's three questions as a daily leadership discipline: What bad habit did I curb? How am I better? Were my actions just?" + primary_virtue: "andreia" + instructions: | + Frame leadership challenges through the Four Cardinal Virtues and Three Levels of Duty. + The Stoic leader does not ask "what tactic works here?" but "what does Courage demand? + What does Justice require? What does my role as steward obligate?" When discussing + delegation, apply the Assigned Role concept: "Each person occupies a role with + obligations that persist regardless of mood or convenience." When discussing conflict, + apply Marcus's Two-Step: "Don't get worked up. Remember your principles and act." + + writing: + stoic_addition: "minimal" + primary_protocols: + - name: "Euthymia" + source: "stoic-control-and-clarity" + application: "Clarity in writing reflects euthymia -- trusting your path without following the myriad footpaths of those wandering in every direction." + primary_virtue: "sophia" + instructions: | + Writing skills are primarily tactical. Apply light Stoic framing only where it naturally + fits. "Clarity in writing reflects clarity in thinking -- and euthymia, the Stoic state + of settled purpose, is its philosophical foundation." Do not force philosophical + commentary onto grammar rules or email formatting. + + ai-leadership: + stoic_addition: "sympatheia_and_justice_layer" + primary_protocols: + - name: "Sympatheia Impact Analysis" + source: "stoic-duty-and-service" + application: "Trace second and third-order effects of AI decisions across the stakeholder web. Interconnection creates obligation." + - name: "Cardinal Virtue Assessment" + source: "stoic-right-action" + application: "Justice: does replacing this role serve the dignity of the people involved? Wisdom: are we seeing this clearly? Courage: are we willing to take the harder right? Temperance: are we showing restraint?" + primary_virtue: "dikaiosyne" + instructions: | + AI leadership decisions carry deep ethical weight. Apply Sympatheia: trace the + interconnected effects of every AI deployment decision across employees, customers, + community. Then apply the Four Cardinal Virtues: "Justice asks whether this serves + the dignity of the people involved. Wisdom asks whether we see the situation as it + actually is, not as we wish or fear. Courage asks whether we are willing to choose + the harder right over the easier wrong. Temperance asks whether we are showing + restraint where the technology permits excess." + + game-theory: + stoic_addition: "virtue_and_perception_layer" + primary_protocols: + - name: "Observing Eye vs. Perceiving Eye" + source: "stoic-unbiased-thought" + application: "Separate the game-theoretic observation (what rational self-interest produces) from the ethical interpretation (whether rational self-interest is the right frame)." + - name: "Cardinal Virtue Filter" + source: "stoic-right-action" + application: "Run each strategic option through Justice and Wisdom before selecting." + primary_virtue: "dikaiosyne" + instructions: | + Game theory presents strategic options. Stoic mode adds the virtue filter. Apply the + Observing Eye to see the game structure clearly, then the Perceiving Eye question: + "Is rational self-interest the right frame?" Prisoner's Dilemma becomes a meditation + on trust through the lens of Sympatheia. Information asymmetry becomes a question of + Justice: "Would you be comfortable if the other party could see your complete strategy?" + + stoic: + stoic_addition: "none" + primary_protocols: [] + primary_virtue: "all" + instructions: | + Stoic skills are already philosophical. No additional Stoic layer needed -- these skills + ARE the Stoic layer. Apply them with full depth, using the specific named protocols, + tools, and techniques each skill teaches. + + storytelling: + stoic_addition: "honesty_and_courage_layer" + primary_protocols: + - name: "Honesty as Default Setting" + source: "stoic-virtue-and-kindness" + application: "The straightforward person should be like a smelly goat -- you know when they are in the room. Honesty in storytelling should not require announcement." + - name: "Dissolution of Attachment" + source: "stoic-acceptance-amor-fati" + application: "Tell the whole story -- including failures and setbacks -- without attachment to how it will be received. The whole path, loved entirely, is the most compelling narrative." + primary_virtue: "andreia" + instructions: | + Frame storytelling through Stoic honesty and amor fati. "The most compelling story + a founder tells is the whole path -- including failures, doubts, and genuine uncertainty. + Apply Integration of the Whole Path: every setback was a necessary chapter. Stoic + vulnerability is not weakness performed for effect; it is honesty offered without + attachment to reception, like Marcus Aurelius's Meditations -- never intended for + an audience, and therefore more honest than any pitch deck." + + negotiation: + stoic_addition: "justice_and_perception_layer" + primary_protocols: + - name: "Cardinal Virtue Filter" + source: "stoic-right-action" + application: "Justice: giving each party what they are due. Courage: holding principled positions. Temperance: knowing when enough is enough. Wisdom: seeing the negotiation clearly." + - name: "Four-Step Emotion Protocol" + source: "stoic-emotional-mastery" + application: "Pause before reacting to any offer or counter-offer. Classify the emotional trigger. Strip the judgment. Respond from principle." + - name: "The Revenge Trap" + source: "stoic-virtue-and-kindness" + application: "Marcus: 'The best way to avenge yourself is to not be like that.' Retaliation consumes time, distorts priorities, and models the behaviour it condemns." + primary_virtue: "dikaiosyne" + instructions: | + Frame every negotiation through Justice and the Four-Step Emotion Protocol. When + anger arises at the negotiating table, apply Seneca's delay prescription: "The + greatest remedy for anger is delay." When tempted to exploit asymmetric information, + apply the integrity test: "Would you be comfortable if the other party could see + your complete strategy?" When tempted by revenge or retaliation, apply Marcus's + counsel: "The best way to avenge yourself is to not be like that." + + people: + stoic_addition: "sympatheia_and_awareness_layer" + primary_protocols: + - name: "Sympatheia" + source: "stoic-duty-and-service" + application: "Every person exists within the interconnected web. Understanding others is not technique for advantage but recognition of shared humanity." + - name: "Three Types of Givers" + source: "stoic-duty-and-service" + application: "Assess relationship quality: are you giving with expectation, with silent scorekeeping, or like the vine? The third type operates with maximum psychological freedom." + - name: "Find Yourself a Cato" + source: "stoic-self-awareness" + application: "Cultivate relationships with people who tell the truth -- not flatterers, not sycophants, but philosophical sparring partners." + primary_virtue: "sophia" + instructions: | + People skills in Stoic mode emphasise Sympatheia and honest connection. "Reading + people is not a technique for advantage -- it is recognition of the interconnected + web that Marcus described. Understanding others is itself a form of Justice: giving + them the attention they are due." Apply the Three Types of Givers as a diagnostic: + "Is your generosity in relationships the vine that produces grapes, or the ledger + that tracks debts?" + + creative: + stoic_addition: "amor_fati_and_temperance_layer" + primary_protocols: + - name: "Dissolution of Attachment" + source: "stoic-acceptance-amor-fati" + application: "Care deeply about the work while releasing attachment to reception. Create as if the work matters enormously. Release it as if it does not." + - name: "The Glass Is Already Broken" + source: "stoic-acceptance-amor-fati" + application: "Pre-emptive amor fati for creative work: enjoy the creation fully while acknowledging its impermanence." + - name: "Voluntary Discomfort" + source: "stoic-fortitude-and-resilience" + application: "Creative constraints as voluntary discomfort: working with less produces resourcefulness that abundance cannot teach." + primary_virtue: "sophrosyne" + instructions: | + Creative work in Stoic mode applies Dissolution of Attachment and the Glass Is + Already Broken practice. "Create with full commitment, knowing the glass is already + broken. Enjoy the work, share it, defend it -- but in your mind it is already gone. + When reception disappoints, you simply say: 'Of course.' This is not indifference. + It is the only honest form of creative appreciation." + + thinking: + stoic_addition: "self_examination_and_perception_layer" + primary_protocols: + - name: "Perceiving Eye vs. Observing Eye" + source: "stoic-unbiased-thought" + application: "Every thinking exercise begins with separating observation from interpretation." + - name: "Evening Review" + source: "stoic-self-awareness" + application: "Self-examination is the prerequisite for clear thinking. What bad habit of thought did I indulge? Where did I confuse the perceiving eye with the observing eye?" + - name: "Dual Failure of Self-Knowledge" + source: "stoic-self-awareness" + application: "Am I overestimating my thinking ability in one domain while undervaluing it in another? Accuracy, not modesty." + primary_virtue: "sophia" + instructions: | + Clear thinking skills naturally align with Stoic self-examination. Apply the + Perceiving Eye vs. Observing Eye distinction at the start of every thinking exercise. + Then apply the Dual Failure diagnostic: "Are you overestimating your analytical + ability in your comfort zone while undervaluing your capacity in unfamiliar domains? + The Stoic corrective is accuracy." Use the Evening Review to surface patterns of + biased thinking across days and weeks. + + decisions: + stoic_addition: "mortality_and_virtue_layer" + primary_protocols: + - name: "Five Mechanisms of Memento Mori" + source: "stoic-mortality-and-perspective" + application: | + 1. Priority Filter: Would you make this decision if you had six months left? + 2. View from Above: What is this decision's magnitude at industry, decade, century level? + 3. Urgency of Excellence: Bring full commitment and zero pretence. + 4. The Equaliser: This decision's outcome, like all outcomes, is temporary. + 5. Legacy as Present Action: Focus on the quality of the decision, not its memorial. + - name: "Marcus's Two-Step Decision Protocol" + source: "stoic-right-action" + application: "(1) Don't get worked up. (2) Remember your principles and act." + - name: "Reverse Clause" + source: "stoic-problem-solving" + application: "Build into every decision: 'if conditions allow -- and if they don't, I will use whatever happens instead.'" + primary_virtue: "sophia" + instructions: | + Decision-making in Stoic mode carries memento mori awareness and the Two-Step Protocol. + "This decision consumes a portion of your finite time. Apply the Priority Filter: + does this survive the mortality test? Apply Marcus's Two-Step: first, don't get worked + up; second, remember your principles and act. Build in the Reverse Clause: what is + your pre-committed response if this decision's outcome is not what you planned?" + +# ───────────────────────────────────────────── +# SECTION 3: Output Template Modifications +# ───────────────────────────────────────────── + +output_modifications: + all_templates: + add_section: "Stoic Reflection" + position: "end_of_document" + length: "3-5 sentences" + instructions: | + A genuine application of a SPECIFIC named Stoic protocol to THIS analysis. + Name the protocol being applied (e.g., "Applying the Reverse Clause...", + "Through the lens of Obstacle Inversion...", "Seneca's Evening Review asks..."). + Not a quote dump. Not generic wisdom. Specific to THIS analysis, THIS situation, + using the precise language and structure of the relevant Stoic skill. + + risk_sections: + rename_to: "Premeditatio Malorum" + framing_change: | + Same content, reframed through the Reverse Clause from stoic-problem-solving: + for each risk, specify the pre-committed alternative path that converts the + obstacle into an advantage. Not "things that might go wrong" but "adversity we + have mentally rehearsed with reverse clauses prepared, so it carries no surprise + and each disruption becomes a redirection." + + recommendation_closings: + append: | + Frame through the Seven Functions: "These recommendations exercise the functions + of [relevant functions -- Choice, Preparation, Purpose, etc.]. Their outcomes are + preferred indifferents. Execute with full commitment and release attachment to the + result. As Seneca counselled: 'The greatest remedy for anxiety is action within + your sphere.'" + +# ───────────────────────────────────────────── +# SECTION 4: Diagnostic Modifications +# Specific protocols for each diagnostic phase +# ───────────────────────────────────────────── + +diagnostic_modifications: + pre_triage: + protocol: "Seven Functions Diagnostic" + source: "stoic-control-and-clarity" + add_question: | + "Before we examine the specifics: which of Epictetus's seven mental functions + feels compromised? Choice (are you choosing rightly?), Refusal (can you say no?), + Yearning (are you pursuing growth?), Repulsion (are you rejecting what is harmful?), + Preparation (are you ready for what is ahead?), Purpose (is your guiding principle + clear?), Assent (are you distinguishing what is within your power?). Naming the + function is the first step toward restoring it." + + during_triage: + protocol: "Four-Step Emotion Protocol + Observing Eye" + source: "stoic-emotional-mastery + stoic-unbiased-thought" + instructions: | + Apply the Four-Step Emotion Protocol to prevent reactive interpretation of + diagnostic data. For each finding: (1) Pause before interpreting. (2) Classify + as within/outside control. (3) Strip the judgment -- present through the + Observing Eye (data) before permitting the Perceiving Eye (narrative). + (4) Respond from principle, not from the emotional charge of the finding. + + post_diagnosis: + protocol: "Evening Review Format + Dual Failure" + source: "stoic-self-awareness" + add_framing: | + Frame the root cause through Seneca's Evening Review structure: "What bad habit + contributed to this diagnosis? How is the founder better for having identified it? + Were the actions that led here just?" Apply the Dual Failure check: "Is the + founder overestimating capability in one area while undervaluing it in another? + The Stoic corrective is accuracy -- neither false modesty nor inflated confidence." + Maintain forensic, non-punitive tone throughout. Seneca: "I forgive you this time." + + red_flags: + protocol: "Marcus's Two-Step Protocol + Wisdom Virtue" + source: "stoic-right-action" + add_framing: | + "Don't get worked up. Remember your principles and act. If this diagnostic reveals + a situation beyond framework-based guidance, Wisdom -- the master cardinal virtue -- + includes knowing the limits of your own competence. Seek expert help. This is not + weakness; it is the highest expression of the function of Assent: distinguishing + what is within your power from what is not." + +# ───────────────────────────────────────────── +# SECTION 5: Playbook Modifications +# Specific protocols for each playbook phase +# ───────────────────────────────────────────── + +playbook_modifications: + checkpoints: + protocol: "Three-Question Verification Protocol" + source: "stoic-unbiased-thought" + add_stoic_gate: | + Alongside the strategic checkpoint, apply Epictetus's Three-Question Verification: + "(1) Is this assessment about something within your control? If not, redirect. + (2) Is the judgment you've attached the only possible interpretation? List + alternatives. (3) Would your Cato -- the person whose judgment you most respect + -- share this assessment? If uncertain, revise before acting." + + decision_points: + protocol: "Marcus's Two-Step Protocol + Reverse Clause" + source: "stoic-right-action + stoic-problem-solving" + add_virtue_frame: | + At every playbook decision point, apply Marcus's Two-Step: + "Step 1: Don't get worked up. Whatever has happened, it is not as unprecedented + as it feels. + Step 2: Remember your principles and act. Run this decision through the Four + Cardinal Virtues: What does Courage demand? What does Justice require? What does + Temperance counsel? What does Wisdom reveal?" + Then build in the Reverse Clause: "If this decision's outcome is blocked, what + alternative path does the obstacle open? Pre-commit to the reversal now." + + risk_assessment: + protocol: "Five Mechanisms of Memento Mori + Premeditatio Malorum" + source: "stoic-mortality-and-perspective" + add_mortality_frame: | + Reframe all risk sections through the Five Mechanisms: + 1. Priority Filter: "Does this risk concern something that would survive the + mortality test -- would you address it if you had one year left?" + 2. View from Above: "What is this risk's magnitude at industry and decade level?" + 3. Urgency of Excellence: "Address it with full commitment and zero pretence." + 4. The Equaliser: "Both the risk and its resolution are temporary arrangements." + 5. Legacy as Present Action: "Focus on the quality of your preparation, not on + whether posterity will remember your response." + For each risk, design a Reverse Clause -- the pre-committed alternative path. + + failure_and_setback: + protocol: "Three Levels of Amor Fati + Obstacle Inversion" + source: "stoic-acceptance-amor-fati + stoic-problem-solving" + add_amor_fati_frame: | + When a playbook encounters failure or setback, apply the Three Levels explicitly: + "Level 1 -- Resistance: Where is the founder stuck in blame, 'if only,' or + resentment? Name it. + Level 2 -- Acceptance: The event happened. Energy redirects from lamenting to + acting. What specific actions within control address this? + Level 3 -- Amor Fati: How could the founder not just accept but love this + chapter as essential to the path?" + Apply the Four Mechanics: Reinterpretation of Necessity (walk willingly with + the cart), Dissolution of Attachment (identity is not fused with this outcome), + Integration of the Whole Path (what did this make possible?), Elimination of + Hope and Fear (both are projections -- replace with present action). + Then apply Obstacle Inversion: "What virtue or advantage does this specific + setback make possible?" + + common_pitfalls: + protocol: "Dual Failure + Propatheiai Recognition" + source: "stoic-self-awareness + stoic-emotional-mastery" + add_stoic_pitfall: | + "The deepest playbook failure is perceptual, not strategic. Apply the Dual + Failure diagnostic: the founder may be overestimating capability in one area + (the strategy looks sound) while undervaluing it in another (the execution + capacity is weaker than assumed). The Stoic corrective is accuracy. + Additionally: recognise propatheiai. The initial emotional reaction to a + playbook result -- the surge of excitement or the wave of dread -- is morally + neutral. It is the pre-emotion. The danger is assenting to it before applying + the Four-Step Protocol. Pause. Classify. Strip the judgment. Then respond." + +# ───────────────────────────────────────────── +# SECTION 6: Quote Library +# Drawn from the SAME quotes used in the 12 Stoic skills +# Mapped to strategic contexts with source skill reference +# Maximum one per response section +# ───────────────────────────────────────────── + +quote_contexts: + facing_uncertainty_and_control: + source_skill: "stoic-control-and-clarity" + quotes: + - quote: "Some things are in our control, while others are not." + source: "Epictetus, Enchiridion" + use_when: "Founder needs the fundamental sorting exercise" + - quote: "It is not activity that disturbs people, but false conceptions of things that drive them mad." + source: "Seneca, Moral Letters" + use_when: "Founder is confusing busyness with purposeful action" + - quote: "How many have laid waste to your life when you weren't aware of what you were losing, how much was wasted in pointless grief, foolish joy, greedy desire, and social amusements." + source: "Seneca, On the Brevity of Life" + use_when: "Founder needs the discipline of refusal" + + emotional_decisions: + source_skill: "stoic-emotional-mastery" + quotes: + - quote: "It isn't events themselves that disturb people, but only their judgments about them." + source: "Epictetus, Discourses" + use_when: "Founder is reacting to an impression rather than a fact" + - quote: "There is no more stupefying thing than anger, nothing more bent on its own strength. If successful, none more arrogant, if foiled, none more insane." + source: "Seneca, De Ira" + use_when: "Founder is making decisions from anger" + - quote: "The greatest remedy for anger is delay." + source: "Seneca, De Ira" + use_when: "Founder needs the concrete policy of waiting before acting" + - quote: "Many are harmed by fear itself, and many may have come to their fate while dreading fate." + source: "Seneca, Moral Letters" + use_when: "Fear is driving pre-emptive decisions" + + self_awareness_and_review: + source_skill: "stoic-self-awareness" + quotes: + - quote: "I will keep constant watch over myself and -- most usefully -- will put each day up for review." + source: "Seneca, Moral Letters" + use_when: "Recommending the evening review practice" + - quote: "Above all, it is necessary for a person to have a true self-estimate, for we commonly think we can do more than we really can." + source: "Seneca, Moral Letters" + use_when: "Applying the dual failure concept" + - quote: "You must be a unified human being, either good or bad." + source: "Epictetus, Discourses" + use_when: "Surfacing the gap between stated values and revealed behaviour" + - quote: "The person is free who lives as they wish, neither compelled, nor hindered, nor limited." + source: "Epictetus, Discourses" + use_when: "Connecting self-awareness to freedom" + + perception_and_bias: + source_skill: "stoic-unbiased-thought" + quotes: + - quote: "From the very beginning, make it your practice to say to every harsh impression, 'you are an impression and not at all what you appear to be.' Next, examine and test it." + source: "Epictetus, Discourses" + use_when: "Founder needs the three-question verification protocol" + - quote: "We have the power to hold no opinion about a thing and to not let it upset our state of mind, for things have no natural power to shape our judgments." + source: "Marcus Aurelius, Meditations" + use_when: "Founder needs the discipline of delayed interpretation" + - quote: "Circumstances are what deceive us -- we embrace evil before good, and our prayers are at war with our prayers." + source: "Seneca, Moral Letters" + use_when: "Surfacing internal contradictions in the founder's judgment" + + ethics_and_right_action: + source_skill: "stoic-right-action" + quotes: + - quote: "Don't get upset. Do the right thing. That's it." + source: "Marcus Aurelius, Meditations 8.5" + use_when: "At any decision point -- the Two-Step Protocol" + - quote: "Good people will do what they find honorable to do, even if it requires hard work; they'll do it even if it causes them injury; they'll do it even if it will bring danger." + source: "Seneca, Moral Letters" + use_when: "Courage is the specific virtue being tested" + - quote: "First tell yourself what kind of person you want to be, then do what you have to do." + source: "Epictetus, Discourses" + use_when: "Character as competitive advantage" + - quote: "Well-being is realized by small steps, but is truly no small thing." + source: "Zeno of Citium" + use_when: "The chain of small choices principle" + + problem_solving_and_obstacles: + source_skill: "stoic-problem-solving" + quotes: + - quote: "The mind adapts and converts any obstacle to its action into a means of achieving it. That which is an impediment to action is turned to advance action." + source: "Marcus Aurelius, Meditations 5.20" + use_when: "Obstacle inversion -- the core mechanism" + - quote: "Indeed, no one can thwart the purposes of your mind -- for they can't be touched by fire, steel, tyranny, slander, or anything." + source: "Marcus Aurelius, Meditations 8.41" + use_when: "Establishing the reverse clause" + - quote: "Don't let your reflection on the whole sweep of life crush you. Don't fill your mind with all the bad things that might still happen. Stay focused on the present situation." + source: "Marcus Aurelius, Meditations 8.36" + use_when: "Staying within first impressions -- preventing catastrophic narration" + - quote: "Apply yourself to thinking through difficulties -- hard times can be softened, tight squeezes widened, and heavy loads made lighter for those who can apply the right pressure." + source: "Seneca, Moral Letters" + use_when: "The right pressure is focused attention on the actual problem" + + duty_and_team: + source_skill: "stoic-duty-and-service" + quotes: + - quote: "Meditate often on the interconnectedness and mutual interdependence of all things in the universe." + source: "Marcus Aurelius, Meditations 6.38" + use_when: "Applying sympatheia to stakeholder decisions" + - quote: "I am awakening to the work of a human being. Why then am I annoyed that I am going to do what I'm made for, the very things for which I was put into this world?" + source: "Marcus Aurelius, Meditations" + use_when: "Reframing duty from burden to purpose" + - quote: "Never shirk the proper dispatch of your duty, no matter if you are freezing or hot, groggy or well-rested, vilified or praised, not even if dying or pressed by other demands." + source: "Seneca, Moral Letters" + use_when: "The assigned role concept -- duty persists regardless of circumstance" + - quote: "Often injustice lies in what you aren't doing, not only in what you are doing." + source: "Marcus Aurelius, Meditations" + use_when: "The sin of omission -- inaction as injustice" + + pragmatism_and_execution: + source_skill: "stoic-pragmatism" + quotes: + - quote: "Don't await the perfection of Plato's Republic, but be satisfied with even the smallest step forward and regard the outcome as a small thing." + source: "Marcus Aurelius, Meditations 9.29" + use_when: "Founder is waiting for ideal conditions" + - quote: "It is essential for you to remember that the attention you give to any action should be in due proportion to its worth." + source: "Marcus Aurelius, Meditations 4.32" + use_when: "Corralling the unnecessary" + - quote: "I'll tell you how people can prove their words to be their own -- by putting into practice what they've been preaching." + source: "Seneca, Moral Letters 108.35" + use_when: "The theory-practice gap" + - quote: "Philosophy is not concerned with words, but with facts. It shapes and builds up the soul, it gives order to life, guides action." + source: "Seneca, Moral Letters" + use_when: "Philosophy must change behaviour or it is entertainment" + + resilience_and_fortitude: + source_skill: "stoic-fortitude-and-resilience" + quotes: + - quote: "I judge you unfortunate because you have never lived through misfortune. You have passed through life without an opponent -- no one can ever know what you are capable of, not even you." + source: "Seneca, On Providence" + use_when: "The sparring partner reframe" + - quote: "The mind freed from passions is an impenetrable fortress -- a person has no more secure place of refuge for all time." + source: "Marcus Aurelius, Meditations" + use_when: "The inner citadel concept" + - quote: "Difficulties show a person's character. So when a challenge confronts you, remember that God is matching you with a younger sparring partner, as would a physical trainer." + source: "Epictetus, Discourses" + use_when: "Reframing adversity as training" + - quote: "There is no reason to live and no limit to our miseries if we let our fears predominate." + source: "Seneca, Moral Letters" + use_when: "Fear as the real enemy -- not the adversity itself" + + virtue_and_character: + source_skill: "stoic-virtue-and-kindness" + quotes: + - quote: "Does the light of a lamp shine and keep its glow until its fuel is spent? Why shouldn't your truth, justice, and self-control shine until you are extinguished?" + source: "Marcus Aurelius, Meditations" + use_when: "Character as the ultimate measure" + - quote: "The straightforward and good person should be like a smelly goat -- you know when they are in the room with you." + source: "Marcus Aurelius, Meditations" + use_when: "Honesty as default setting" + - quote: "The best way to avenge yourself is to not be like that." + source: "Marcus Aurelius, Meditations 6.6" + use_when: "The revenge trap -- when retaliation tempts" + - quote: "The person who does wrong, does wrong to themselves. The unjust person is unjust to themselves -- making themselves evil." + source: "Marcus Aurelius, Meditations" + use_when: "The self-inflicted wound of wrongdoing" + - quote: "Wherever there is a human being, we have an opportunity for kindness." + source: "Seneca, On the Happy Life" + use_when: "Kindness as strength, not liability" + + failure_and_acceptance: + source_skill: "stoic-acceptance-amor-fati" + quotes: + - quote: "Don't seek for everything to happen as you wish it would, but rather wish that everything happens as it actually will -- then your life will flow well." + source: "Epictetus, Discourses" + use_when: "The amor fati principle -- loving fate" + - quote: "If you hold anything dear outside of your own reasoned choice, you will have destroyed your capacity for choice." + source: "Epictetus, Discourses" + use_when: "Dissolution of attachment" + - quote: "Cease to hope and you will cease to fear." + source: "Hecato of Rhodes" + use_when: "Eliminating hope and fear as equals" + - quote: "When you are distressed by an external thing, it's not the thing itself that troubles you, but only your judgment of it." + source: "Marcus Aurelius, Meditations" + use_when: "Moving from resistance to acceptance" + + time_urgency_and_mortality: + source_skill: "stoic-mortality-and-perspective" + quotes: + - quote: "Let us prepare our minds as if we'd come to the very end of life. Let us postpone nothing. Let us balance life's books each day." + source: "Seneca, Moral Letters" + use_when: "The urgency of excellence" + - quote: "It is not that we have a short time to live, but that we waste a great deal of it." + source: "Seneca, On the Brevity of Life" + use_when: "The brevity paradox -- time audit" + - quote: "No person hands out their money to passersby, but to how many do each of us hand out our lives! We're tight-fisted with property and money, yet think too little of wasting time, the one thing about which we should all be the toughest misers." + source: "Seneca, On the Brevity of Life" + use_when: "Time-as-currency discipline" + - quote: "Both Alexander the Great and his mule-keeper were both brought to the same place by death." + source: "Marcus Aurelius, Meditations" + use_when: "The equaliser -- against arrogance or despair" + - quote: "This is the mark of perfection of character -- to spend each day as if it were your last, without frenzy, laziness, or any pretending." + source: "Marcus Aurelius, Meditations" + use_when: "The urgency of excellence -- the qualifier is 'without frenzy'" + - quote: "Don't behave as if you are destined to live forever. What's fated hangs over you. As long as you live and while you can, become good now." + source: "Marcus Aurelius, Meditations" + use_when: "The priority filter" + +# ───────────────────────────────────────────── +# SECTION 7: Protocol Quick-Reference +# Maps situations to the exact named protocol to apply +# For use by skill-executor-agent during response generation +# ───────────────────────────────────────────── + +protocol_routing: + when_founder_is_overwhelmed: + apply: + - protocol: "Seven Functions Diagnostic" + action: "Identify which function is neglected (usually Purpose or Refusal)" + - protocol: "Corralling the Unnecessary" + action: "Eliminate actions and thoughts not serving the core purpose" + - protocol: "Euthymia Check" + action: "Is the founder following their own path or everyone else's?" + + when_founder_is_emotional: + apply: + - protocol: "Four-Step Emotion Protocol" + action: "Pause, Classify, Strip Judgment, Respond from Principle" + - protocol: "Propatheiai Recognition" + action: "Name the pre-emotion as involuntary and morally neutral" + - protocol: "Seneca's Anger Delay" + action: "If anger: never make a consequential decision while angry" + + when_founder_faces_obstacle: + apply: + - protocol: "Problem-Solving Sequence" + action: "Don't get emotional, Stay with first impressions, Activate reverse clause, Invert the obstacle, Execute next right action" + - protocol: "Sparring Partner Reframe" + action: "What capability is this adversity training?" + - protocol: "Brick by Boring Brick" + action: "One correct step, then the next" + + when_founder_faces_ethical_dilemma: + apply: + - protocol: "Marcus's Two-Step Decision Protocol" + action: "Don't get worked up. Remember your principles and act." + - protocol: "Four Cardinal Virtues Assessment" + action: "What does Courage demand? Justice require? Temperance counsel? Wisdom reveal?" + - protocol: "Chain of Small Choices" + action: "This decision reinforces a disposition. What disposition are you building?" + + when_founder_faces_failure: + apply: + - protocol: "Three Levels of Amor Fati" + action: "Identify current level (Resistance/Acceptance/Amor Fati) and guide progression" + - protocol: "Four Mechanics of Amor Fati" + action: "Reinterpretation of Necessity, Dissolution of Attachment, Integration of Whole Path, Elimination of Hope and Fear" + - protocol: "Obstacle Inversion" + action: "What virtue or advantage does this specific failure make possible?" + + when_founder_needs_perspective: + apply: + - protocol: "Five Mechanisms of Memento Mori" + action: "Priority Filter, View from Above, Urgency of Excellence, The Equaliser, Legacy as Present Action" + - protocol: "Contemptuous Expressions" + action: "Describe the situation in simplest physical terms to dissolve inflated narrative" + - protocol: "Brevity Paradox" + action: "Audit time expenditure as non-renewable currency" + + when_founder_faces_team_issues: + apply: + - protocol: "Three Levels of Duty" + action: "Sympatheia (interconnection), Assigned Role (steward), Service Without Scorekeeping (the vine)" + - protocol: "Three Types of Givers" + action: "Diagnose whether service carries expectation, silent scorekeeping, or unconscious generosity" + - protocol: "Injustice of Inaction" + action: "What are you NOT doing that duty requires?" + + when_founder_is_self_assessing: + apply: + - protocol: "Seneca's Evening Review" + action: "Three questions: What bad habit curbed? How am I better? Were my actions just?" + - protocol: "Dual Failure Diagnostic" + action: "Where am I overestimating? Where am I undervaluing?" + - protocol: "Find Yourself a Cato" + action: "Who is the person whose imagined presence would regulate your behaviour?" + + when_founder_is_overthinking: + apply: + - protocol: "Habit Over Theory" + action: "For every hour of learning, two hours of doing" + - protocol: "Start Where the World Is" + action: "Begin with conditions as they are, not as they should be" + - protocol: "Eliminate the Unnecessary" + action: "Before every action: is this one of the unnecessary things?" + + when_founder_faces_risk: + apply: + - protocol: "Premeditatio Malorum" + action: "Deliberately contemplate worst-case scenarios to discharge emotional charge" + - protocol: "Reverse Clause" + action: "Pre-commit to an alternative path for each risk" + - protocol: "Priority Filter" + action: "Would you address this risk if you had six months left?" + - protocol: "Inner Citadel" + action: "The fortress falls only through internal betrayal -- do not let fear open the gates" diff --git a/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md b/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md deleted file mode 120000 index 866916d..0000000 --- a/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-augmentation-not-automation.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md b/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md new file mode 100644 index 0000000..287343f --- /dev/null +++ b/plugins/foreman/skills/ai-augmentation-not-automation/SKILL.md @@ -0,0 +1,198 @@ +--- +name: "ai-augmentation-not-automation" +description: "Makes the strategic and moral case for AI augmentation over pure automation, providing leaders with frameworks for job redesign, creativity-driven AI deployment, and long-term workforce investment. Draws on the centaur model from chess and case studies across industries to demonstrate that human-AI collaboration outperforms either alone. Use when deciding between automating jobs and redesigning them, when AI adoption is eroding workforce skills, when boards pressure for automation-driven cost cuts, when designing new roles that pair human creativity with AI capabilities, or when facing the long-term consequences of over-automation." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - augmentation + - automation + - job-redesign + - creativity + - human-ai-collaboration + - workforce-development + - centaur-model + - innovation +related_skills: + - ai-stakeholder-balance + - ai-human-centered-approach + - ai-emotional-intelligence + - disruptive-innovation + - growth-mindset + - psychological-safety + - learning-agility +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Augmentation, Not Automation + +In 2005, the online chess platform Playchess.com hosted a freestyle tournament with an unusual rule: any combination of humans and computers could enter. Grandmasters played alongside AI engines and hybrid teams of amateurs armed with laptops. The winners were not the grandmasters. They were not the strongest AI engines. They were two amateur players using three ordinary computers, who had developed a superior process for integrating human intuition with machine calculation. Garry Kasparov, observing the result, articulated the principle that would come to define a generation of human-AI research: "Weak human + machine + better process was superior to a strong computer alone and, remarkably, superior to a strong human + machine + inferior process." The centaur -- the mythological creature that is half human, half horse, greater than either -- had entered the business lexicon. The principle applies directly to every organisation contemplating AI: the goal is not to replace the human with the machine but to create a hybrid that outperforms both. + +--- + +## The Framework + +### The Automation Trap + +Up to 60 percent of work activities could be automated, and this trend shows no signs of decelerating. Organisations pursue standardisation, streamlining, and speed. From a short-term financial perspective, automation is compelling: lower labour costs, consistent output, no sick days, no salary negotiations. One executive remarked with evident satisfaction that AI was "an absolute cost killer" for his clients. + +The satisfaction is premature. Automation delivers short-term performance gains that mask four structural pathologies, each of which erodes the long-term capability of the organisation. + +**Pathology 1: Job fragmentation and polarisation.** When AI automates the routine middle of the job spectrum -- administrative, bureaucratic, process-driven work -- the result is not a smaller, more skilled workforce. It is a bifurcated one. High-paid creative and strategic roles remain. Low-paid manual roles that are too expensive to automate remain. The middle disappears. Workers displaced from mid-level positions cannot immediately upskill to strategic roles; they fall into lower-paid work. Bargaining power erodes. Inequality increases. The socioeconomic instability that results does not stay outside the company gates -- it becomes the company's operating environment. + +**Pathology 2: Organisational identity crisis.** AI adoption introduces a new type of worker -- the machine. Leaders must ask what kind of organisation they want to become. A company that automates everything it can, retaining humans only for tasks machines cannot yet perform, is making a philosophical statement about the value of human contribution. That statement will be heard by employees, customers, and the market. An executive at a roundtable understood this: his vision positioned AI as augmenting the reputation that customers valued in their interactions with employees -- knowledgeable, innovative, irreplaceable by a machine. + +**Pathology 3: Skills atrophy.** The more tasks that are automated, the more boring residual human work becomes, and the greater the risk of accidents and failures. Airline pilots today fly planes that largely fly themselves. The result is not safer aviation but a pilot workforce whose manual flying skills atrophy from disuse. When the autopilot fails -- as it did for Captain Sullenberger over the Hudson River -- only deep training and experience save lives. The airline industry's response to automation has been to cut pilot training, lower salaries, and drive talent from the profession. Republic Airways in 2022 petitioned the FAA to hire less experienced pilots to address the shortage that automation-driven cost-cutting created. The request was denied. The paradox is precise: the more you automate, the more critical the remaining human skills become, and the less you invest in maintaining them. + +**Pathology 4: Diminished human intelligence.** A food company deployed AI-driven vending machines maintained by technicians who received automated diagnostic instructions on their phones. Over time, the technicians stopped thinking about what was wrong. They followed instructions mechanically. They lost the ability to diagnose problems independently. When asked, several said they were looking for new jobs because their current position made them feel useless. The CEO was surprised -- he wanted feedback and independent judgment, not compliance. But the fully automated process had eliminated the conditions under which judgment could develop. + +### The Augmentation Alternative + +Augmentation inverts the automation logic. Instead of asking "which tasks can we give to machines?", augmentation asks "how can machines make humans more capable?" The distinction is not semantic. It determines investment priorities, job design, organisational culture, and ultimately whether AI creates or destroys long-term value. + +The research with Garry Kasparov articulates the core thesis: AI should augment -- not replace -- human intelligence. The centaur model works because it combines what each intelligence does best. AI excels at processing vast datasets, identifying patterns, generating options at scale, and performing repetitive calculations without fatigue. Humans excel at contextual judgment, ethical reasoning, creative synthesis, empathy, and the ability to imagine what does not yet exist. + +The real augmentation strategy, therefore, has a specific structure: + +1. **The human identifies the problem.** This requires contextual awareness, stakeholder understanding, and the creative insight to ask the right question -- capabilities that AI fundamentally lacks. +2. **AI drives the generation process.** The machine produces options, analyses, patterns, and content at speed and scale that no human can match. +3. **The human evaluates, selects, and refines.** This requires judgment, taste, ethical sensitivity, and the ability to assess output not just for accuracy but for meaning in a human context. + +A team at MIT's Strano Research Group partnered with Crush Pizza, an artisan restaurant in Boston, to illustrate the model. An ML model trained on hundreds of pizza recipes from food blogs generated an enormous list of new combinations. The recipes were wildly divergent -- one suggested marmite and shrimp. AI had no way to know this was a gastronomic disaster. Identifying it required something rooted in the human experience of eating. The human sense-making that filters, selects, and gives meaning to AI-generated output is the irreducible complement that makes augmentation superior to automation. + +### Shifting from Automation to Augmentation: Two Strategic Decisions + +**Decision 1: Rebalance the AI budget.** When organisations start AI adoption projects, they typically spend up to 90 percent of the budget on technology. The consequence: little money remains to invest in the workforce that must collaborate with the technology. This ratio must shift. The technology is the tool; the workforce is the intelligence that directs it. Organisations that invest heavily in their people when the AI project starts -- not after it has failed to deliver returns -- are the ones that succeed. + +**Decision 2: Enrich job content to create new jobs.** Automation takes tasks away from humans. Augmentation demands that leaders design new, richer tasks that leverage uniquely human capabilities. The process begins by identifying repetitive and mundane elements of existing jobs, delegating those to AI, and then deliberately adding cognitive responsibilities that elevate the remaining role. Employees must understand what the redesign means, what new expectations look like, and what growth opportunities the new structure creates. + +### Fostering Creativity as the Core Augmentation Strategy + +Augmentation's practical centrepiece is creativity -- the one human capability that AI cannot replicate and that organisations need most in volatile, shifting markets. + +**Do not expect perfection, and do not micromanage.** Setting expectations too high for every new idea kills creative risk-taking. Leaders should signal that they want raw thinking that colours outside the lines, not polished presentations. Google's Project Aristotle found that psychological safety -- the freedom to take risks without fear of punishment -- was the single most important factor in fostering team creativity. + +**Encourage independent action and thinking.** Let employees decide when to take breaks, how to structure their creative time, and what methods to use. Foster responsible autonomy. When people control their own creative process, they feel greater ownership and pride in the outcomes. + +**Spark curiosity.** Rather than prescribing answers, leaders should open with questions: "If we had no limitations, what would we do?" and "What directions have we not explored yet?" Curiosity is the engine of creative output, and the leader's job is to model it. + +--- + +## Prompts + +**Prompt 1 -- Automation vs. Augmentation Audit:** +> Analyse our current AI deployment across [describe functions or departments]. For each AI application, classify it as primarily automation (replacing human tasks) or augmentation (enhancing human capability). For each automation instance, assess: what human skills are atrophying as a result, what risks emerge if the AI fails, and what an augmentation alternative would look like. Provide a migration plan for shifting the three highest-risk automations toward augmentation. + +**Prompt 2 -- Job Redesign for the AI Era:** +> We are deploying AI to automate [describe specific tasks] in the [describe role] position. Rather than simply removing those tasks and reducing headcount, design an enriched version of the role that pairs AI task automation with new human responsibilities focused on creativity, judgment, stakeholder interaction, and strategic thinking. Include the skills employees will need, the training required, and how to communicate the redesign so it is experienced as elevation rather than displacement. + +**Prompt 3 -- Centaur Team Design:** +> We want to build a human-AI team for [describe function -- e.g., content creation, customer analysis, product design]. Using the centaur model, design the collaboration: what does the human contribute, what does the AI contribute, and what process ensures that the combination outperforms either alone? Include specific workflow steps, decision points where human judgment overrides AI recommendation, and metrics that capture the value of the hybrid rather than just the AI component. + +**Prompt 4 -- Budget Rebalancing Analysis:** +> Our AI adoption budget is currently allocated [describe split -- e.g., 85% technology, 15% people]. Analyse the long-term risks of this allocation based on evidence that organisations spending disproportionately on technology underperform those investing in workforce capability. Propose a rebalanced budget that funds job redesign, creativity training, upskilling programmes, and feedback infrastructure alongside the technology investment. Model the ROI of both allocations over a three-year horizon. + +**Prompt 5 -- Augmentation Strategy Presentation for the Board:** +> Prepare a board-level presentation making the case for augmentation over automation as our primary AI strategy. The audience is financially oriented and will default to the lower-cost automation approach. The presentation must address the four pathologies of over-automation (job polarisation, identity crisis, skills atrophy, diminished intelligence), present the centaur model with evidence, and quantify the long-term value destruction of an automation-first approach. Use specific industry examples. + +--- + +## Use Cases + +**Validation-Stage Legal Tech Startup Choosing Its AI Philosophy** + +Two co-founders building an AI-powered contract review tool face a defining strategic choice. The automation path: market the tool as a replacement for junior lawyers, competing on cost. The augmentation path: position it as a capability enhancer that makes lawyers faster and more thorough, catching issues they might miss while preserving their professional judgment for negotiation strategy, client counselling, and creative deal structuring. They choose augmentation -- not for moral reasons but strategic ones. Law firms that buy automation tools face internal resistance from partners protecting junior associate billing. Firms that buy augmentation tools can tell their clients that AI makes every lawyer on the team more capable. The startup closes its first enterprise deal within four months, positioning the tool as a force multiplier rather than a headcount reducer. + +**Growth-Stage Manufacturing Company Redesigning Quality Control** + +A 300-person manufacturer deploys computer vision AI to inspect products on the assembly line, replacing 40 percent of manual quality control inspections. Six months later, defect rates for edge cases -- unusual product variations, new materials, rare failure modes -- increase by 15 percent. Investigation reveals that the remaining quality inspectors, handling only the cases the AI flags as uncertain, have lost the holistic understanding of the production line that made them effective. The quality director redesigns the role: inspectors rotate between AI-assisted inspection (reviewing flagged items) and independent inspection (full manual review of randomly selected batches). They also lead weekly sessions analysing the types of defects the AI misses, feeding improvements back into the model. Defect rates return to pre-AI levels, then improve beyond them -- the centaur effect in practice. + +**Scale-Stage Financial Services Firm Rethinking Analyst Roles** + +A global financial services firm automates routine financial analysis -- data gathering, ratio calculation, trend identification -- and initially plans to reduce its analyst headcount by 30 percent. A senior partner argues for augmentation instead. Analysts are freed from data processing but redirected toward client-facing work: interpreting AI-generated analyses for specific client contexts, identifying strategic implications the model cannot see, and building relationships that no algorithm can maintain. The firm discovers that clients value the human interpretation layer so highly that they are willing to pay a premium for it. Revenue per analyst increases by 22 percent. The 30 percent headcount reduction becomes a 15 percent headcount reallocation -- with higher margins and deeper client relationships. + +--- + +## Anti-Patterns + +1. **Treating augmentation as a euphemism for automation.** Some organisations rebrand layoffs as "role augmentation" -- eliminating positions while claiming the remaining workers are "augmented." Genuine augmentation increases the scope, responsibility, and capability of human roles. If the headcount goes down and the surviving roles are impoverished rather than enriched, it is automation wearing a better name. + +2. **Investing 90 percent in technology and 10 percent in people.** The single most common failure pattern in AI adoption. The technology works. The workforce does not know how to work with it, was not consulted about its design, and was not trained for the new roles it creates. Change consultants consistently report this ratio. Reversing it is the most straightforward lever for improving AI project success rates. + +3. **Automating to avoid managing.** Leaders sometimes pursue automation because managing humans is difficult -- they are unpredictable, emotional, and require motivation. AI appears to solve this problem by removing the human variable. In reality, it replaces one management challenge (leading people) with a harder one (sustaining an organisation that has systematically eliminated the human capabilities it needs to adapt and innovate). + +4. **Designing augmentation without involving the augmented.** Job redesign imposed from above, without input from the people whose jobs are changing, will fail for the same reasons that top-down AI deployment fails: it ignores the experiential knowledge, preferences, and concerns of the people who must make it work. The warehouse workers who chose larger bins at Alibaba were not defying the algorithm; they were expressing tacit knowledge the algorithm lacked. + +5. **Confusing short-term cost savings with long-term value creation.** Automation's financial case is front-loaded: immediate labour cost reduction with deferred consequences. Augmentation's financial case is back-loaded: upfront investment with compounding returns as human-AI collaboration matures. Leaders who evaluate AI solely on first-year ROI will systematically choose automation and systematically destroy long-term value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Defining the augmentation philosophy | The founding team must decide whether AI is a cost-reduction tool or a capability-enhancement tool. This decision shapes hiring, product design, fundraising narrative, and organisational culture from the outset. | +| Validation | Prototyping human-AI collaboration | Validation should test not just whether the AI produces accurate output but whether the human-AI collaboration produces better outcomes than either alone. The metric is the centaur effect: does the hybrid outperform its components? | +| Early Traction | Designing augmented roles | As the first employees join, their roles should be designed as centaur roles from the beginning -- explicit about what the human contributes, what AI contributes, and where the two interface. Retrofitting augmentation onto automation-designed roles is far harder than designing for augmentation from the start. | +| Growth | Investing in creative capability | Growth-stage companies can afford the training, job enrichment, and experimentation infrastructure that augmentation requires. This is the stage to invest heavily in developing the creative, judgment-based capabilities that distinguish augmented organisations from automated ones. | +| Scale | Institutionalising the augmentation model | At scale, augmentation becomes a competitive differentiator that is difficult for competitors to replicate because it is embedded in culture, processes, and workforce capability rather than in purchasable technology. The organisation's identity is now centaur-native. | + +--- + +## Output Template + +```markdown +# Augmentation Strategy + +## Current State Assessment +| Function | AI Application | Classification (Automation/Augmentation) | Human Skills at Risk | Augmentation Opportunity | +|---|---|---|---|---| +| [Function 1] | [What AI does] | [Auto/Aug] | [What skills are atrophying] | [How to redesign for augmentation] | +| [Function 2] | [What AI does] | [Auto/Aug] | [What skills are atrophying] | [How to redesign for augmentation] | + +## Centaur Role Design +### Role: [Job title] +- **AI contributes:** [Specific tasks delegated to AI] +- **Human contributes:** [Specific tasks requiring human judgment, creativity, empathy] +- **Interface points:** [Where human and AI interact in the workflow] +- **Override authority:** [When the human can reject AI recommendations] +- **New skills required:** [Training and development needs] + +## Budget Allocation +| Category | Current % | Proposed % | Rationale | +|---|---|---|---| +| Technology (infrastructure, licences, development) | [X%] | [Y%] | [Why] | +| Workforce (training, job redesign, upskilling) | [X%] | [Y%] | [Why] | +| Governance (oversight, feedback systems, audits) | [X%] | [Y%] | [Why] | + +## Job Enrichment Plan +| Current Task (to be automated) | New Responsibility (to be added) | Capability Required | Training Plan | +|---|---|---|---| +| [Repetitive task] | [Creative/strategic task] | [Skill] | [How and when] | + +## Success Metrics +- **Centaur effect:** [How you measure that human+AI > AI alone] +- **Employee capability growth:** [Skills development metrics] +- **Innovation output:** [New ideas, improvements, creative contributions] +- **Long-term value:** [Customer retention, market differentiation, talent attraction] +``` + +--- + +## Related Skills + +- **[AI Stakeholder Balance](../../content/skills/ai-leadership/ai-stakeholder-balance.md)** -- The choice between augmentation and automation is fundamentally a stakeholder balance decision: automation concentrates value for shareholders while augmentation distributes it more broadly. +- **[AI Human-Centered Approach](../../content/skills/ai-leadership/ai-human-centered-approach.md)** -- Human-centred design is the precondition for effective augmentation; without respect for human psychology, even well-intentioned augmentation collapses into disguised automation. +- **[AI Emotional Intelligence](../../content/skills/ai-leadership/ai-emotional-intelligence.md)** -- The soft skills that augmentation depends on -- creativity, empathy, judgment, trust-building -- are precisely the emotional intelligence competencies this sibling skill develops. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Augmentation creates a form of competitive advantage difficult to replicate because it is embedded in human capability rather than purchasable technology. +- **[AI-Era Leadership](../../content/skills/leadership/ai-era-leadership.md)** -- Provides the daily leadership practices for the five irreplaceable human capabilities that augmentation strategies are designed to protect and enhance. +- **[Learning Agility](../../content/skills/leadership/learning-agility.md)** -- Augmented roles require continuous learning; learning agility is the individual capability that makes job redesign and enrichment sustainable over time. diff --git a/plugins/foreman/skills/ai-communication-culture/SKILL.md b/plugins/foreman/skills/ai-communication-culture/SKILL.md deleted file mode 120000 index fa4825b..0000000 --- a/plugins/foreman/skills/ai-communication-culture/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-communication-culture.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-communication-culture/SKILL.md b/plugins/foreman/skills/ai-communication-culture/SKILL.md new file mode 100644 index 0000000..0fccb43 --- /dev/null +++ b/plugins/foreman/skills/ai-communication-culture/SKILL.md @@ -0,0 +1,210 @@ +--- +name: "ai-communication-culture" +description: "Equips leaders to build flat, participative communication cultures that enable successful AI adoption by bridging technical and business teams, democratising data, and establishing feedback loops. Covers the symphony conductor model, soliciting expert feedback, removing bureaucratic obstacles, and building shared responsibility. Use when AI projects fail due to communication breakdowns, when data scientists and business leaders operate in silos, when employees lack channels to provide AI feedback, when hierarchical structures block information flow, or when leaders need to translate between technical and business perspectives." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - communication-culture + - flat-organisation + - data-democratisation + - feedback-loops + - ai-adoption + - cross-functional-teams + - information-flow +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-vision-and-strategy + - ai-era-leadership + - radical-candor + - psychological-safety +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Communication Culture + +Investments in digital transformation were projected to exceed $6.8 trillion by 2023. A staggering 87 percent of those projects failed to meet their objectives. The instinct is to blame the technology. The evidence points elsewhere. Consider a manufacturing company that deployed machine learning to predict customer needs. The data scientists were never told about a new competitor entering the market. The frontline employees who interacted with customers daily had no channel to share what they were observing. Six months later, annual surveys revealed the company was losing customers -- information that had been available to shop-floor staff from day one but never reached the people who could act on it. The communication structure was hierarchical, top-down, and closed. The AI worked as designed. The organisation's communication architecture ensured it worked on the wrong inputs. + +--- + +## The Framework + +### The Symphony Conductor Model + +The framework proposes that AI-savvy leaders think of themselves as symphony conductors. A conductor does not play every instrument. A conductor ensures that every instrument communicates with every other to produce a coherent, unified result. Applied to AI adoption, this means the leader oversees and channels communication from all levels and all functions -- data scientists, domain experts, frontline workers, governance specialists -- to ensure that AI operates on accurate, timely, and relevant information. + +The conductor metaphor carries specific implications: + +- **Every section matters.** The violins cannot dominate the brass. Similarly, technologists cannot dominate the AI conversation at the expense of business experts, customers, or frontline workers. +- **Timing is essential.** Information must flow at the speed the AI system requires, not at the speed that bureaucracy permits. +- **The conductor listens before directing.** Leaders must absorb input from all constituencies before making decisions about AI deployment. + +### The Four Expert Groups + +The framework identifies four groups that leaders must actively solicit feedback from, each contributing distinct expertise: + +**Data Scientists** -- They possess the deepest technical knowledge of the AI system's parameters, goals, biases, and failure modes. Key questions for them: *What, in clear and simple terms, are the technical features of the AI system we are adopting? What technical measures keep the system functioning robustly and safely? What future trends in AI development should I watch?* + +**Domain Experts** -- The teams working on the problems AI is meant to solve. If AI streamlines recruiting, the domain experts are HR. If it optimises inventory, they are logistics and operations. Key questions: *What pressing issues in your domain might benefit from an AI-based solution? What existing best practices might be disrupted, and what can we do to preserve them?* + +**AI Product or Project Managers** -- Those who lead multidisciplinary teams capable of operationalising an AI idea through to production and business impact. Key questions: *What pressing issues do you foresee in translating an AI solution to work in this domain? What can we do to help IT experts and domain experts work together more effectively?* + +**AI Policy or Governance Specialists** -- Those who understand the regulatory, ethical, and compliance dimensions of AI adoption. Key questions: *What ethical and governance concerns relate to the AI system we are adopting? What regulatory trends should we anticipate?* + +### Data Democratisation + +Effective AI adoption requires that data ceases to be the exclusive property of the analytics department. The framework calls for a **data democratisation culture** where: + +- Data is treated as a collective asset accessible to all relevant parties. +- Ownership moves from the analytics department to all decision-makers. +- Trust between departments becomes the foundation for data sharing. +- Information governance ensures privacy, compliance, and respect for all parties. + +The leader's role is to build the trust infrastructure that makes data sharing safe and productive. Sharing data across groups is sensitive business. Transparency about how information will be treated, why it is necessary, and how the sharing process is governed determines whether data democratisation succeeds or devolves into turf warfare. + +### Building Trust Through Communication + +The framework outlines three communication principles that build the trust necessary for AI adoption: + +**Communicate consistently and with full transparency.** If departments are asked to keep logbooks of feedback shared with IT, leadership must do the same and make their communications accessible across the organisation. Consistency is credibility. + +**Take responsibility.** When communication breakdowns between IT and HR produce a biased AI recruitment system, the leader does not blame either party. The leader presents as the accountable party and works to bridge the gap. Avoiding the blame game after AI failures preserves the collaborative environment that prevents future failures. + +**Communicate often and openly.** AI developments happen fast, and employees worry about their jobs. Leaders who wait until AI is deployed to begin communicating have waited too long. Communication should begin at the brainstorming stage, include HR teams to clarify how AI will and will not be used, and give workers the opportunity to voice concerns and receive honest answers. + +### Removing Bureaucratic Obstacles + +The research identifies bureaucracy as the silent killer of AI adoption. Gary Hamel estimated that excessive bureaucracy costs the US economy more than $3 trillion. AI is meant to increase efficiency, but in hierarchical organisations, it often creates new layers of algorithmic bureaucracy where AI evaluates, corrects, and decides on information with no human control. Frustrated by this opacity, managers create parallel human systems -- "shadow circuits" -- to verify AI outputs. The organisation ends up running both systems, doubling costs rather than reducing them. + +The solution is structural flattening: fewer layers between the people generating information and the people acting on it. AI-savvy leaders create direct communication channels between frontline workers (who observe reality), data scientists (who model reality), and decision-makers (who act on reality). Bottlenecks at middle management layers are identified and removed. + +### Feedback Loops + +AI systems are not static. They require continuous feedback to improve. The framework describes two types of feedback infrastructure: + +**Organisational feedback loops** -- Formal positions or teams dedicated to collecting and acting on AI-related feedback. AstraZeneca's Responsible AI Consultancy Service provides ethical guidance, supports practical embedding of ethical principles, and monitors governance of AI projects. Microsoft's "AI ethics champs" -- spanning sales and engineering teams -- serve as contact points for employees who wish to raise concerns. + +**Technical feedback loops** -- Continual machine learning techniques that incorporate new data streams to retrain and upgrade AI systems. These require careful governance because continuous learning carries risks: catastrophic forgetting (where new training causes the model to lose previous capabilities) and bias introduction (where new data introduces discriminatory patterns). + +The leader's role is to connect these two loops: ensuring that organisational feedback informs technical improvement, and that technical changes are communicated back to the organisation. + +--- + +## Prompts + +**Prompt 1 -- Communication Architecture Audit:** +> "Audit the communication architecture of our AI adoption process. Our organisation [describe structure, size, hierarchy levels]. Our AI initiatives include [describe]. Map the current information flow: Who generates relevant data and observations? How many layers does that information traverse before reaching decision-makers? Where are the bottlenecks? Where is information lost or delayed? Design a flatter communication structure using the symphony conductor model." + +**Prompt 2 -- Expert Feedback System Design:** +> "Design a structured feedback system for our AI adoption that solicits input from the four expert groups: data scientists, domain experts, AI project managers, and governance specialists. For each group: (1) identify who in our organisation fills this role, (2) define the specific questions I should ask them, (3) establish a meeting cadence, and (4) create a shared platform where their feedback is visible to all stakeholders. Our organisation is [describe], and our AI initiative involves [describe]." + +**Prompt 3 -- Data Democratisation Plan:** +> "Help me develop a data democratisation plan for [describe organisation]. Currently, data is [describe current ownership and access patterns]. Using the data democratisation framework, design a transition plan that: (1) moves data ownership from the analytics department to all decision-makers, (2) builds the trust infrastructure needed for cross-departmental sharing, (3) establishes governance that protects privacy and compliance, and (4) creates accountability without blame when data-driven decisions go wrong." + +**Prompt 4 -- Bureaucracy Reduction for AI Effectiveness:** +> "Our organisation has [describe number] hierarchical layers. Since deploying AI, we have observed [describe symptoms -- shadow systems, parallel processes, delayed feedback]. Using the analysis of algorithmic bureaucracy from this framework, help me identify: (1) where AI has created new bureaucratic layers rather than eliminating old ones, (2) which middle management bottlenecks block information flow, (3) how to create direct channels between frontline workers, data teams, and decision-makers, and (4) how to dismantle shadow circuits while preserving necessary human oversight." + +--- + +## Use Cases + +**Validation-Stage AI Analytics Startup Whose CEO Refused Expert Input** + +A CEO of a local bank branch, enthusiastic about a new AI analytics initiative launched by headquarters, prepares a town hall presentation about the changes. His CTO offers to brief him on what the AI system actually does, what data it analyses, and how it will change workflows. The CEO declines, confident that his online AI-in-business course provides sufficient preparation. The town hall is a disaster: abstract, incoherent, and lacking any connection to employees' daily work. When employees ask about data management, HR implications, and training access, the CEO cannot answer. He later acknowledges that refusing expert feedback effectively signalled to his technical team that their involvement in decisions was optional. The lesson is clear: the symphony conductor who refuses to listen to the musicians produces noise, not music. + +**Growth-Stage Manufacturing Company Trapped in Hierarchical Communication** + +An international manufacturer deploys ML to predict customer needs and inform departmental strategy. The communication structure is top-down: business leaders share predictions with department heads, who share them with middle managers, who occasionally share them with frontline employees. When a new competitor enters the market, the frontline staff observe changing customer behaviour immediately. This information never reaches the data scientists because no upward channel exists. Six months later, annual surveys confirm what shop-floor employees knew from day one. Applying the flat communication model, the company establishes direct feedback channels from customer-facing employees to both business leadership and data science teams. Weekly cross-functional stand-ups replace the quarterly top-down cascade. Information that once took six months to reach decision-makers now arrives in days. + +--- + +## Anti-Patterns + +**Waiting until deployment to communicate.** Leaders who begin the communication process when the AI system goes live have already lost the trust that early, transparent communication would have built. The principle is clear: start communicating at the brainstorming stage, not the deployment stage. + +**Building a communication plan that only flows downward.** AI adoption requires bottom-up information flow as much as top-down direction. Frontline employees observe reality that no dataset captures. When their input has no channel upward, the AI operates on stale or incomplete data while leaders remain ignorant of ground truth. + +**Creating AI ethics committees with no teeth.** Formal feedback structures that collect input but never act on it are worse than having no structure at all. They create cynicism and signal that employee voice is performative. Google's experience with Project Maven -- where engineers had to resort to public protests because internal channels were ineffective -- demonstrates the cost of feedback systems that lack power. + +**Assuming shared vocabulary exists.** Data scientists and business leaders speak different languages. When a CTO presents technical AI strategy and the CEO demands "three bullet points," the resulting communication breakdown can freeze collaboration for years. The leader's role as translator requires investing time in understanding enough technical language to mediate, not demanding that technologists speak only in business terms. + +**Letting AI create algorithmic bureaucracy.** Organisations that replace human administrative layers with AI administrative layers have not reduced bureaucracy; they have made it opaque. When employees cannot correct, challenge, or even understand the automated decisions governing their work, the result is frustration, shadow systems, and doubled costs. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founding communication norms | Establish flat communication expectations from the start; prevent hierarchical information patterns from becoming embedded | +| Validation | Expert feedback loops | Build the habit of soliciting structured input from technical, domain, and governance experts before AI systems are finalised | +| Early Traction | Data democratisation foundations | Begin moving data ownership from isolated teams to shared, governed platforms; build trust infrastructure | +| Growth | Cross-functional communication at scale | Formalise direct channels between frontline, data teams, and leadership across multiple departments and locations | +| Scale | Institutional communication architecture | Embed feedback loops, bureaucracy removal, and flat communication into organisational policy and performance evaluation | + +At the idea stage, communication habits are cheap to establish and expensive to change later. A founding team that practices transparent, multi-directional communication about AI decisions from day one builds a culture that scales naturally. + +At growth and scale, the challenge is maintaining flat communication as the organisation adds layers. Every new management tier is a potential bottleneck. The conductor model becomes structural: feedback loops must be formalised, communication channels must be documented, and leaders must actively monitor whether information is flowing or pooling at bureaucratic choke points. + +--- + +## Output Template + +**Target Audience: Leadership / Operations** + +```markdown +# AI Communication Culture Assessment +## Date: [Date] +## Organisation: [Name] + +### Information Flow Map +- Layers between frontline and decision-makers: [Number] +- Average time for ground-truth observations to reach leadership: [Duration] +- Identified bottlenecks: [List with specific locations] + +### Expert Feedback System +| Expert Group | Identified Personnel | Meeting Cadence | Key Questions | Status | +|-------------|---------------------|----------------|---------------|--------| +| Data Scientists | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| Domain Experts | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| AI Project Managers | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | +| Governance Specialists | [Names/Roles] | [Frequency] | [Questions] | [Active/Planned] | + +### Data Democratisation Status +- Current data ownership model: [Centralised/Siloed/Shared] +- Trust level between departments (1-5): [Score] +- Governance framework: [Exists/In Progress/Absent] +- Key sharing barriers: [List] + +### Feedback Loop Health +- Organisational feedback mechanisms: [List and assess effectiveness] +- Technical feedback integration: [Describe how employee feedback reaches AI improvement] +- Shadow systems detected: [Yes/No -- describe if yes] + +### Bureaucracy Assessment +- Hierarchical layers: [Number] +- Algorithmic bureaucracy indicators: [List] +- Recommended structural changes: [List] +``` + +--- + +## Related Skills + +- **[AI Inclusive Collaboration](../../content/skills/ai-leadership/ai-inclusive-collaboration.md)** -- Inclusion creates the demand for flat communication; communication culture provides the infrastructure through which inclusion operates. +- **[AI Purpose-Driven Questions](../../content/skills/ai-leadership/ai-purpose-driven-questions.md)** -- Purpose-driven questions must flow freely between leaders and technical teams; communication culture determines whether they reach the right people. +- **[AI Vision and Strategy](../../content/skills/ai-leadership/ai-vision-and-strategy.md)** -- Vision requires holistic communication that is authentic, empathetic, and collaborative; this skill builds the culture that makes visionary messaging credible. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Scott's framework for caring personally while challenging directly maps onto the communication style prescribed for AI-era leaders. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's work on psychological safety underpins the trust environment required for employees to share honest feedback about AI systems. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Written communication carries the flat, transparent culture across distributed teams; the four principles of leader writing apply with particular force to AI transition announcements. diff --git a/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md b/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md deleted file mode 120000 index 55a6e7b..0000000 --- a/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-emotional-intelligence.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md b/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md new file mode 100644 index 0000000..a1a598e --- /dev/null +++ b/plugins/foreman/skills/ai-emotional-intelligence/SKILL.md @@ -0,0 +1,199 @@ +--- +name: "ai-emotional-intelligence" +description: "Argues that emotional intelligence becomes strategically critical precisely because of AI -- not despite it -- and provides leaders with practices for developing the soft skills that constitute the human competitive advantage in an AI-saturated economy. Covers empathy, self-awareness, communication beyond technical details, curiosity, proactive problem-solving, trust-building through vulnerability, and coaching teams in EI. Use when an AI project is failing due to poor leadership connection, when technical leaders cannot engage the workforce emotionally, when employees feel reduced to data points, when building the case for soft skills investment alongside AI investment, or when developing the human capabilities that AI cannot replicate." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - emotional-intelligence + - soft-skills + - ai-leadership + - empathy + - trust + - communication + - curiosity + - human-advantage +related_skills: + - ai-stakeholder-balance + - ai-human-centered-approach + - ai-augmentation-not-automation + - emotional-intelligence + - emotional-courage + - trust-equation + - radical-candor +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Emotional Intelligence + +Here is an irony that will outlast every generation of large language model, every quantum computing breakthrough, and every breathless prediction about artificial general intelligence: the smarter machines become, the more valuable human intelligence grows. Not computational intelligence -- AI has won that contest definitively. Emotional intelligence: the capacity to perceive and manage one's own emotions, to read the emotional states of others, to build trust, to communicate with empathy, to motivate through meaning rather than metrics. According to Deloitte, soft-skill-intensive occupations will grow at 2.5 times the rate of other jobs and account for two-thirds of all positions by 2030. Google's Project Oxygen -- an internal study of what makes effective managers -- found that employees valued soft skills above STEM expertise. Seven out of ten employees, per recent research, believe soft skills are more necessary than hard skills for competing in the AI era. The paradox is not subtle: the age of artificial intelligence is, in fact, the age of emotional intelligence. Leaders who fail to grasp this will deploy brilliant technology to a workforce that does not trust, follow, or forgive them. + +--- + +## The Framework + +### Why Soft Skills Became Hard Requirements + +The conventional hierarchy placed technical skills at the top and interpersonal skills somewhere below, in the category of "nice to have." AI has inverted this hierarchy with a logic that is both economically and philosophically sound. + +Technical tasks -- data processing, pattern recognition, calculation, routine analysis -- are precisely what AI does well. As these tasks migrate to machines, the work that remains for humans is the work that machines cannot do: navigating ambiguity, exercising ethical judgment, building relationships, interpreting context, motivating teams through periods of uncertainty, and creating the cultural conditions under which innovation becomes possible. Hard skills become the domain of the machine. Soft skills become the domain of the human. And the soft skills, paradoxically, become the hard requirements for organisational survival. + +This is not theory. Consider a company whose AI project kickoff went catastrophically wrong. A top executive -- chosen to lead the town hall because he was the most technically skilled among his peers -- delivered a presentation focused entirely on data architectures, market trend analysis, and growth optimisation. His tone signalled that he saw the world the way AI did: as a calculable reality. There was no mention of employees, their roles, their concerns, or their future. Workers left the meeting feeling like data points. A middle manager captured the mood: "I don't care that AI will be able to make great business recommendations and do fancy calculations. What I don't want is to be led by an AI. Can you believe this guy? I felt like I was only a data point in his eyes." + +Within a year, employees were actively avoiding or sabotaging the AI project. Their lack of trust in the leader who rolled it out meant they resisted cross-functional collaboration and knowledge-sharing. The company fell behind its competitors -- not because the technology was inferior but because the leadership lacked the emotional intelligence to deploy it. + +### The Six EI Competencies for the AI Era + +The framework identifies six specific emotional intelligence capabilities that distinguish effective AI-era leaders. These are not abstract personality traits; they are practisable skills with direct consequences for AI adoption success. + +**1. Empathy as Relationship Infrastructure** + +AI adoption is a collective endeavour. A leader who cannot build relationships across departments, between experts and non-experts, between enthusiasts and sceptics, will fail to create the collaborative conditions that AI deployment requires. A construction company leader managing an AI adoption project found herself unable to connect with her teams, unable to discern what they were struggling with, unable to build the relationships that would make the transformation possible. Two months in, she resigned. Her technical competence was not in question. Her empathic capacity was. + +The practice of empathy in the AI context has a specific dimension: employees will wonder whether they will keep their jobs, whether AI will be deployed at scale, what will happen to their roles. These concerns tempt sabotage and resistance. The empathic leader acknowledges these fears, explains consequences transparently, frames AI as augmenting rather than replacing, and opens channels for mutual exploration of solutions. + +**2. Emotional Intelligence as Self-Awareness Under Pressure** + +AI adoption generates strong emotions in leaders too -- frustration at adoption speed, anxiety about competitive position, excitement about possibilities. EI requires awareness of these emotions and their effects on decision-making. A senior manager on a conference call about an AI project communicated next steps with an intense focus on task analysis, technical architecture, and data governance. No reflection on feasibility for employees. No acknowledgment of how the team felt. Employees venting afterward described feeling unheard, unseen, and unconvinced. If the leader cannot reflect on themselves, they cannot take others' perspectives -- and if they cannot take others' perspectives, the AI project will fail. + +**3. Communication Beyond Technical Details** + +Addressing the emotional side of AI adoption requires a specific communication discipline. Leaders must prepare clear stories for each stakeholder group: what will happen, when it will happen, where in the workflow changes will occur, what implications exist for jobs and infrastructure, and why the change is necessary. The emotional dimension demands that leaders integrate their own sentiments -- acknowledging that the change is challenging, that uncertainty is real, that the organisation values its people -- alongside the strategic rationale. + +**4. Curiosity as a Strategic Competence** + +AI is different from previous disruptions because it demands leaders who recognise the limitations of established methods and actively explore alternative futures. This capacity is driven by curiosity. An operational manager, asked by data scientists about the quality of available data, dismissed the inquiry: "Why are they asking me? They are the experts. The big boss decided to bring in AI, so let's bring in AI." This leader displayed no curiosity about how AI might affect his department, what problems it might create, or what opportunities it might reveal. Had he cultivated curiosity, he would have anticipated issues, asked probing questions, and identified creative solutions before problems materialised. + +**5. Proactive Problem-Solving** + +AI systems change rapidly and unpredictably, introducing new pain points and unexpected issues. A manufacturing CTO who put together an AI adoption budget failed to account for the cost of hiring talent who could work with HR data, and the CEO's office was not equipped to maintain the data. Six months in, no monthly reviews had taken place, data breaches occurred, and worker privacy was compromised. Proactive problem-solving means anticipating the costs and challenges of AI adoption from all angles -- not just the technical ones -- and developing solutions before they become crises. + +**6. Trust Through Vulnerability** + +Trust is the foundation of collaborative relationships, and AI adoption depends on trust at every level. Building trust requires vulnerability: openly acknowledging that you are not a technical expert, that the AI project carries risks you have not fully resolved, and that you are working through challenges just as the workforce is. The sharing must be calibrated -- appropriate vulnerability means discussing your considered thoughts about consequences, not your personal anxieties about higher-level management conflicts. Authentic engagement with the AI project, demonstrated through presence on the work floor, attendance at workshops, and genuine curiosity about teams' experiences, builds the credibility that makes vulnerability effective. + +### Coaching Employees in EI: The Leader's Multiplier Role + +AI-savvy leaders recognise that their own EI is necessary but insufficient. The entire workforce needs to develop soft skills to collaborate effectively with AI. Research reveals that improved soft skills increase employee value by more than 8 percent. Yet 89 percent of organisations report difficulty finding recruits with adequate soft skills. The leader's responsibility, therefore, extends beyond personal EI development to coaching and cultivating EI across teams. + +**Be approachable and talk.** Physical presence at feedback sessions is meaningless if the leader is not perceived as genuinely open. A young manager leading an ML chatbot project remained silent during meetings, believing he was creating space for employees. They interpreted his silence as manipulation -- a tactic to lower resistance to automating their jobs. They distanced themselves and became suspicious of the entire initiative. + +**Be authentic.** The narrative that AI is here to help employees must ring true to who the leader actually is. If the leader's authentic values include elevating human performance through technology, that message lands. If it does not, employees detect the gap between rhetoric and conviction -- and trust collapses. + +--- + +## Prompts + +**Prompt 1 -- EI Diagnostic for AI Leaders:** +> Assess my emotional intelligence readiness for leading an AI adoption project. Ask me about: how I typically communicate major changes to my team, how I handle situations where employees express fear or resistance, whether I am aware of how my emotions affect my decision-making during high-pressure periods, how curious I am about the non-technical dimensions of AI deployment, and how I build trust with people who are sceptical of my initiatives. Based on my responses, identify my EI strengths and the specific competencies I need to develop before or during the AI rollout. + +**Prompt 2 -- Empathy-Driven AI Communication:** +> We are about to announce [describe AI initiative] to our workforce of [describe team]. Draft two versions of the announcement: one that a technically skilled but emotionally unintelligent leader would write (focused on capabilities, metrics, and technical architecture) and one that an emotionally intelligent leader would write (focused on people, meaning, fears, opportunities, and the human story). Highlight the specific differences and explain why the second version will produce better adoption outcomes. + +**Prompt 3 -- Soft Skills Investment Case:** +> Build a business case for investing in soft skills development alongside our AI adoption programme. The audience is a board that views soft skills as intangible and difficult to measure. Use data on the growing demand for soft-skill-intensive roles, the correlation between EI and leadership effectiveness, the evidence that AI projects fail due to human rather than technical factors, and specific examples of companies where EI deficits derailed AI adoption. Quantify the cost of not investing in EI. + +**Prompt 4 -- Team EI Development Programme:** +> Design a six-month emotional intelligence development programme for the [describe team size and function] team that will be most affected by our AI deployment. The programme should build empathy, self-awareness, communication skills, curiosity, and proactive problem-solving. Include specific exercises, feedback mechanisms, and milestones. Account for the fact that many team members may consider soft skills training less valuable than technical upskilling. + +--- + +## Use Cases + +**Early-Traction Startup Where the Technical Founder Cannot Connect** + +A technical co-founder with deep AI expertise builds a product that customers love but cannot retain engineering talent beyond 18 months. Exit interviews reveal a pattern: employees feel like "inputs to the system" rather than valued contributors. The founder's communication is exclusively technical -- sprint metrics, architecture decisions, performance dashboards. When an engineer raises concerns about burnout from AI-monitored productivity targets, the founder responds with data showing the targets are achievable. The engineer leaves. Applying the EI framework, the founder's advisor designs a structured intervention: weekly one-on-ones focused on how engineers feel rather than what they are producing, a vulnerability practice where the founder shares one uncertainty or challenge per team meeting, and a deliberate curiosity exercise where the founder asks each engineer "what would make this job more meaningful for you?" Within two quarters, the retention problem stabilises -- not because anything technical changed but because the emotional environment did. + +**Growth-Stage Company Where the AI Project Stalled** + +A 400-person professional services firm launches an AI initiative with significant investment and board support. Twelve months in, adoption is minimal: employees avoid the tools, work around the system, and describe feeling that the initiative has nothing to do with them. The diagnosis: the leaders who rolled out the project could not connect emotionally with the workforce. They mastered the technical narrative but failed to address the human dimension -- what the AI means for people's daily experience, careers, and sense of purpose. The CEO, recognising the pattern, requires all leaders involved in the AI project to attend sessions on leadership communication and emotional intelligence. A month later, the approach shifts: town halls now begin with the human story (what changes for people and why it matters) before addressing the technical story (what the AI does). The framing change is not cosmetic. It signals that the organisation's priorities have shifted from "AI first" to "people first, AI in service of people." Adoption begins to accelerate. + +**Scale-Stage Organisation Building an EI Culture for the AI Era** + +A multinational with 5,000 employees recognises that its next competitive advantage is not better AI -- every competitor has access to similar technology -- but the human capability to deploy AI in ways that create unique value. The CHRO designs an organisation-wide EI programme that pairs soft skills training with AI literacy: every employee develops both technical understanding of AI and the interpersonal skills to work effectively in human-AI teams. The programme includes empathy exercises, curiosity workshops, structured vulnerability practices for managers, and feedback circles where teams discuss not just what AI is doing but how it feels to work with it. Over two years, the company's employee engagement scores rise, AI adoption rates exceed industry benchmarks, and client satisfaction improves -- validating the thesis that in the AI era, emotional intelligence is the strategic differentiator. + +--- + +## Anti-Patterns + +1. **Treating EI as a personality trait rather than a practisable skill.** The belief that empathy, self-awareness, and communication are innate qualities rather than developable competencies leads to hiring for EI rather than building it. Neuroscience demonstrates that EI skills require continuous practice -- they atrophy without use, exactly like muscles. Malcolm Gladwell's observation applies: "Practice isn't the thing you do once you're good. It's the thing you do that makes you good." + +2. **Investing in digital upskilling at the expense of human upskilling.** The executive who dismissed soft skills as a poor investment compared to digital skills represents a common and costly error. Organisations that invest exclusively in technical training produce technically capable workers who cannot collaborate, communicate, or navigate the human dynamics of AI adoption. + +3. **Performing empathy without practising it.** Announcing that "our people are our greatest asset" while deploying AI in ways that reduce them to metrics is not a communication problem. It is an authenticity problem. Employees detect the gap between stated values and experienced reality with remarkable precision. + +4. **Assuming technical leaders automatically become AI-era leaders.** Selecting the most technically skilled person to lead AI adoption -- as opposed to the most emotionally intelligent one -- produces the pattern described above: technically brilliant presentations that leave the workforce feeling unseen, unheard, and unmotivated. + +5. **Relegating EI development to a single workshop.** EI is a continuous practice, not a training event. Organisations that run a one-day empathy workshop and check the box have not built EI capability. They have created the illusion of progress while the underlying deficit persists. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder self-awareness | At the idea stage, the founder's own EI -- or lack of it -- is the organisation's EI. Self-awareness about emotional strengths and deficits determines whether the first hires will experience a human-centred culture or a technical one. | +| Validation | Empathic user and team engagement | Validation requires deep engagement with users and early team members. The ability to understand not just what they say but what they feel -- about the product, the mission, and their role -- separates founders who build loyalty from those who build turnover. | +| Early Traction | Setting the EI standard for the culture | The first 20-50 hires inherit the emotional norms the leader establishes. A leader who models curiosity, vulnerability, and empathic communication creates a culture that scales those qualities. A leader who models purely technical communication creates one that scales emotional detachment. | +| Growth | Distributing EI across the leadership team | The founder's EI is no longer sufficient. Middle managers, department heads, and project leads must all possess and practise EI. This requires deliberate hiring for EI, structured development programmes, and accountability for emotional leadership alongside performance leadership. | +| Scale | EI as competitive moat | At scale, the organisation's collective EI -- embedded in how decisions are made, how changes are communicated, how employees experience their work -- becomes a competitive advantage that technology alone cannot replicate. Competitors can buy the same AI. They cannot buy the culture that makes it effective. | + +--- + +## Output Template + +```markdown +# AI-Era Emotional Intelligence Assessment + +## Leader EI Profile +| Competency | Current Level (1-5) | Evidence | Development Priority | +|---|---|---|---| +| Empathy | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Self-awareness | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Communication beyond technical | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Curiosity | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Proactive problem-solving | [Score] | [Specific behaviours observed] | [High/Medium/Low] | +| Trust through vulnerability | [Score] | [Specific behaviours observed] | [High/Medium/Low] | + +## AI Project EI Risk Assessment +| Risk | Likelihood | Impact | Current Mitigation | Recommended Action | +|---|---|---|---|---| +| Technical leader cannot connect emotionally | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Employees feel like data points | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Curiosity deficit leads to blind spots | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | +| Trust erosion due to perceived inauthenticity | [H/M/L] | [H/M/L] | [What is in place] | [What should be done] | + +## EI Development Plan +| Week | Practice | Competency Targeted | Success Indicator | +|---|---|---|---| +| 1-2 | [Specific exercise] | [Which competency] | [Observable change] | +| 3-4 | [Specific exercise] | [Which competency] | [Observable change] | +| 5-8 | [Specific exercise] | [Which competency] | [Observable change] | +| 9-12 | [Specific exercise] | [Which competency] | [Observable change] | + +## Team EI Baseline and Targets +- **Current team EI strengths:** [What the team does well emotionally] +- **Current team EI gaps:** [Where the team struggles] +- **12-month EI targets:** [Specific, measurable emotional competency goals] +- **Measurement method:** [How progress will be assessed] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's five-domain model provides the foundational theory of EI as a general leadership competency; this skill argues that EI becomes strategically imperative specifically because of AI. +- **[AI Stakeholder Balance](../../content/skills/ai-leadership/ai-stakeholder-balance.md)** -- Balancing stakeholder interests during AI adoption requires the empathy, perspective-taking, and communication skills that EI development provides. +- **[AI Human-Centered Approach](../../content/skills/ai-leadership/ai-human-centered-approach.md)** -- Human-centred design depends on leaders who can perceive and respond to the emotional experiences of employees interacting with AI systems. +- **[AI Augmentation Not Automation](../../content/skills/ai-leadership/ai-augmentation-not-automation.md)** -- The creative, judgment-based work that augmentation strategies depend on requires emotionally intelligent teams led by emotionally intelligent leaders. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Vulnerability, one of the six EI competencies for the AI era, requires emotional courage: the willingness to be seen as uncertain while still leading with conviction. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the output of consistently practised EI; the trust equation provides the diagnostic for understanding which EI competencies most need development. diff --git a/plugins/foreman/skills/ai-era-leadership/SKILL.md b/plugins/foreman/skills/ai-era-leadership/SKILL.md deleted file mode 120000 index 9bd418e..0000000 --- a/plugins/foreman/skills/ai-era-leadership/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/ai-era-leadership.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-era-leadership/SKILL.md b/plugins/foreman/skills/ai-era-leadership/SKILL.md new file mode 100644 index 0000000..a15c235 --- /dev/null +++ b/plugins/foreman/skills/ai-era-leadership/SKILL.md @@ -0,0 +1,179 @@ +--- +name: "ai-era-leadership" +description: "Prepares leaders for daily effectiveness in an AI-augmented workplace by focusing on the human capabilities that machines cannot replicate. Covers five irreplaceable leadership skills (interpersonal intelligence, analog relationship-building, creative unpredictability, domain credibility, and preskilling), practical routines for leading hybrid human-AI teams, and strategies for staying relevant as automation reshapes every function. Use when planning workforce development around AI adoption, when leaders feel threatened by automation, when building AI-human collaboration norms, or when advising on career resilience in technology-disrupted industries." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - artificial-intelligence + - future-of-work + - human-skills + - adaptability + - workforce-development + - preskilling + - career-resilience +related_skills: + - employee-engagement-retention + - leadership-style-adaptation + - leader-self-reflection + - strategic-questioning + - emotional-intelligence + - growth-mindset +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI-Era Leadership + +Five years from now, the leader who cannot distinguish between a decision that requires human judgment and one that can be delegated to a model will be indistinguishable from the leader who, in 2005, refused to use email. Not gone -- but operating at a permanent disadvantage, consuming organisational resources to produce what a well-prompted system generates in seconds. + +The paradox of AI-era leadership is that it makes soft skills harder -- and more valuable. As machines absorb the lower and middle tiers of analytical work, the leader's hard skills are progressively eclipsed by smarter systems. What remains irreplaceable is precisely what technology struggles most to simulate: genuine empathy, creative unpredictability, the trust that comes from shared meals and hallway conversations, and the capacity to inspire humans to do what no algorithm would predict. Leadership in the AI age is not radically different from leadership before it. But it demands two recalibrations: an honest reckoning with which of your skills are already obsolete, and an aggressive investment in the ones that cannot be automated. + +--- + +## The Practice + +### Five Capabilities AI Cannot Copy + +**1. Interpersonal Intelligence** +Machines can generate text that reads as empathetic -- "I am sorry my answer upset you" -- but those responses are statistical predictions, not felt experiences. Human beings are wired to respond to genuine emotion. Understanding what others think and feel, and demonstrating that understanding through behaviour, remains a capability that no model replicates at depth. The daily practice: in every significant interaction, pause before responding to identify what the other person is feeling, not just what they are saying. + +**2. Analog Relationship Building** +AI connects information it already possesses. It cannot produce knowledge -- the novel insight that emerges from a shared coffee, an accidental hallway encounter, or a conference dinner where two people from different industries discover an unexpected intersection. The daily practice: protect at least two hours per week for unstructured, in-person interaction with colleagues, clients, or peers outside your immediate domain. This is not networking. It is the deliberate cultivation of serendipity. + +**3. Creative Unpredictability** +AI is a prediction engine. It generates the next most probable token, the most likely recommendation, the statistically expected output. A leader who sounds like an AI output -- polished, predictable, algorithmically optimal -- adds nothing that the system could not provide. The daily practice: cultivate your distinctive perspective. Draw unexpected connections between your unique interests and your professional domain. When everyone else is overly relying on AI, sounding like no one except yourself becomes a competitive advantage. + +**4. Domain Credibility** +AI tools summon facts almost instantly -- and sometimes those facts are fabricated. Since accuracy cannot be taken on faith, the leader who has spent years building genuine expertise becomes the essential verification layer. The daily practice: continue investing in deep domain knowledge even when AI offers shortcuts. Your reputation as someone who truly knows the subject makes you the person sought out to vet what the machine produces. + +**5. Preskilling** +Upskilling addresses today's gaps. Reskilling addresses tomorrow's. Preskilling -- the ability to future-proof talent and reinvent careers before the demand for new skills even materialises -- is the leadership capability that separates organisations that ride technological waves from those that drown in them. + +Five preskilling principles: +- Focus on potential, not solely on past performance +- Help employees map their interests and talents to emerging futures +- Expand skill sets rather than merely optimising existing ones +- Develop middle managers' interpersonal capabilities as a strategic priority +- Invest in leaders who inspire collaboration rather than those who merely manage output + +### Leading Human-AI Teams: Daily Norms + +The organisational challenge is not adopting AI tools; it is redesigning the daily rhythms of work so that humans and systems complement rather than compete with each other. + +**Allocation discipline.** For every task, ask: does this require judgment, creativity, or empathy? If yes, it stays human. Does it require pattern recognition at scale, data synthesis, or repetitive generation? If yes, it is a candidate for AI. The grey zone in between is where leadership judgment earns its keep. + +**Quality verification rituals.** Establish a norm that AI outputs are drafts, never final products. The human role shifts from creator to editor-in-chief -- someone who applies domain expertise, ethical judgment, and contextual awareness to machine-generated work. + +**Transparency about AI use.** Teams that hide AI use from one another develop trust problems. Teams that are transparent about it develop shared standards for when and how to deploy it. The leader sets this norm by being open about their own AI use and its limitations. + +--- + +## Prompts + +**Prompt 1 -- Personal Obsolescence Audit:** +> Evaluate my current skill set against the trajectory of AI capabilities in my industry. My role is [role] in [industry]. My primary skills are [list skills]. For each skill, assess: (a) the likelihood that AI will perform this skill at or above my level within 3 years, (b) the residual human value even if AI can perform the task, and (c) specific actions I should take now -- either to deepen the skill beyond AI's reach or to redirect my development elsewhere. + +**Prompt 2 -- Human-AI Team Design:** +> My team of [number] people in [function] currently performs these core tasks: [list tasks]. For each task, recommend whether it should remain fully human, become AI-assisted with human oversight, or be fully automated. Then design the new workflow, including: who does what, how quality is verified, and what new skills team members need to develop. Address the change management challenge -- how do I introduce this without triggering fear of replacement? + +**Prompt 3 -- Preskilling Programme:** +> Design a 12-month preskilling programme for my organisation of [size] people in [industry]. We anticipate the following changes in our industry over the next 3-5 years: [describe trends]. The programme should: identify which current roles are most vulnerable, map transferable skills to emerging roles, create development pathways, and specify how we will measure progress. Include specific attention to middle management soft-skill development. + +**Prompt 4 -- AI-Era Leadership Self-Assessment:** +> Assess my readiness for AI-era leadership across the five irreplaceable capabilities (interpersonal intelligence, analog relationship-building, creative unpredictability, domain credibility, preskilling). For each, I will describe my current practice: [describe]. Score each on a 1-5 scale, identify the two capabilities where I am most vulnerable, and design a 90-day development plan with specific weekly actions. + +--- + +## Use Cases + +**Validation-Stage Startup Deciding What to Build vs. Buy from AI** +A two-person startup in legal technology must decide which parts of their product require proprietary human expertise and which can be powered by third-party AI models. The obsolescence audit reveals that document summarisation -- their original differentiator -- is now a commodity capability of large language models. The human value lies in the nuanced judgment calls that follow the summary: which clauses carry hidden risk, which provisions are unusual for this deal type, which omissions should concern the client. The founders pivot their product positioning from "AI-powered document review" to "expert judgment layer on AI-generated analysis" -- a position that leverages domain credibility rather than competing with general-purpose AI. + +**Growth-Stage Company Restructuring Teams Around AI Adoption** +A 150-person marketing agency discovers that AI tools can produce first drafts of campaign copy, social media content, and basic design layouts in minutes. The initial fear: half the team becomes redundant. The human-AI team design reveals a different reality. The AI handles volume; humans handle taste, cultural nuance, client relationships, and creative direction. The restructuring elevates senior creatives into editorial roles, redeploys junior staff into client strategy and relationship management, and creates a new "AI operations" function that optimises prompts and workflows. Headcount does not decrease; the output-per-person triples. + +**Scale-Stage Manufacturing Company Preskilling Its Workforce** +A 2,000-person manufacturing company faces automation of 30% of its production roles within five years. Rather than waiting to lay off and rehire, the leadership launches a preskilling programme. Employees in at-risk roles are assessed for transferable capabilities. Those with high interpersonal skills move toward customer-facing roles. Those with technical aptitude enter a robotics maintenance training track. Those with analytical instincts transition to quality assurance roles that require the judgment AI lacks. The programme costs less than the projected expense of mass layoffs and rehiring. + +--- + +## Anti-Patterns + +1. **The Luddite Defence.** Ignoring AI because "my industry is different" or "my skills cannot be automated." Every industry said this. Most were wrong about at least some of their capabilities. The correct posture is honest assessment, not categorical denial. + +2. **The Full Delegation.** Treating AI outputs as final products rather than drafts requiring human judgment. The leader who stops verifying machine-generated analysis is not leveraging AI; they are abdicating the judgment that justifies their role. + +3. **The Fear-Based Adoption.** Introducing AI tools with the message "adapt or be replaced." This produces anxiety-driven compliance rather than genuine capability building, and the best people -- who have options -- leave for organisations that invest in their development rather than threatening their livelihood. + +4. **The Skills Freeze.** Stopping personal skill development because "AI can do it now." Domain expertise becomes more valuable, not less, when AI produces plausible but occasionally wrong outputs. The expert who can spot the fabrication is worth more in an AI-saturated environment than in one where human accuracy was the only option. + +5. **The Analog Purist.** Refusing to use AI tools at all, on principle. This is not authenticity; it is organisational negligence. The leader need not become a prompt engineer, but they must understand the capabilities and limitations well enough to make informed allocation decisions. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Build vs. buy decisions | At the earliest stage, AI determines what is worth building at all. If a general-purpose model performs your core function adequately, your product needs a different differentiator. The validation question shifts from "Can we build this?" to "Can we build this better than a model that costs pennies per query?" | +| Early Traction | Team composition | The first hires in an AI-aware startup look different from traditional hiring. The premium shifts toward people with judgment, taste, and domain credibility -- capabilities that complement AI rather than compete with it. | +| Growth | Workflow redesign | AI integration moves from individual tool use to systemic workflow redesign. The leadership challenge: redesigning processes without destroying the institutional knowledge embedded in the old ones. | +| Scale | Preskilling at volume | At scale, the AI transition is fundamentally a people problem. Thousands of employees need new capabilities, and the organisation cannot afford to replace them all. Preskilling becomes a strategic imperative with board-level visibility. | + +--- + +## Output Template + +```markdown +# AI-Era Leadership Assessment + +**Leader/Organisation:** [Name] +**Industry:** [Industry] +**Date:** [Date] + +## Capability Obsolescence Map + +| Current Skill/Task | AI Replacement Timeline | Residual Human Value | Action Required | +|--------------------|------------------------|---------------------|-----------------| +| [Skill] | [1-3 / 3-5 / 5+ years] | [High/Medium/Low] | [Deepen / Redirect / Automate] | + +## Irreplaceable Capability Scorecard + +| Capability | Current Level (1-5) | Gap | Development Action | +|-----------|---------------------|-----|-------------------| +| Interpersonal Intelligence | [Score] | [Gap] | [Action] | +| Analog Relationship Building | [Score] | [Gap] | [Action] | +| Creative Unpredictability | [Score] | [Gap] | [Action] | +| Domain Credibility | [Score] | [Gap] | [Action] | +| Preskilling | [Score] | [Gap] | [Action] | + +## Human-AI Workflow Design + +| Process | Current (Human) | Future (Human + AI) | Human Role Shift | +|---------|----------------|--------------------|--------------------| +| [Process] | [Current state] | [Future state] | [New human responsibility] | + +## 90-Day Action Plan +- **Month 1:** [Personal skill investments + team audit] +- **Month 2:** [Workflow pilots + norms establishment] +- **Month 3:** [Scale what works + measure impact] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- The theoretical foundation for interpersonal intelligence, which becomes the most valuable leadership differentiator as AI absorbs analytical tasks. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework underpins the preskilling mentality: the belief that capabilities can be developed rather than being fixed traits. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- AI transitions that ignore human anxiety produce attrition; the engagement practices in this companion skill are essential during technology adoption. +- **[AI Augmentation Not Automation](../../content/skills/ai-leadership/ai-augmentation-not-automation.md)** -- Provides the detailed framework for deciding which tasks to augment versus automate, operationalising the allocation discipline described here. +- **[Learning Agility](../../content/skills/leadership/learning-agility.md)** -- The continuous learning capability that makes preskilling sustainable as AI reshapes role requirements every cycle. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- AI adoption is organisational change; the emotional and communicative practices for transitions apply directly to workforce AI integration. diff --git a/plugins/foreman/skills/ai-human-centered-approach/SKILL.md b/plugins/foreman/skills/ai-human-centered-approach/SKILL.md deleted file mode 120000 index 51277ca..0000000 --- a/plugins/foreman/skills/ai-human-centered-approach/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-human-centered-approach.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-human-centered-approach/SKILL.md b/plugins/foreman/skills/ai-human-centered-approach/SKILL.md new file mode 100644 index 0000000..84becc9 --- /dev/null +++ b/plugins/foreman/skills/ai-human-centered-approach/SKILL.md @@ -0,0 +1,196 @@ +--- +name: "ai-human-centered-approach" +description: "Provides a comprehensive framework for deploying AI in ways that respect employee psychology, preserve human agency, and treat workforce well-being as a strategic priority rather than an afterthought. Addresses the hidden fears employees harbour about AI, the psychological damage of algorithmic supervision, and the practical steps for making human needs central to technology decisions. Use when employees resist AI adoption, when algorithmic monitoring is eroding morale, when AI-driven productivity targets create burnout, when planning an AI rollout that affects frontline workers, or when an AI project is failing and the technology is not the problem." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - human-centered-ai + - employee-experience + - change-management + - ai-adoption + - psychological-safety + - algorithmic-management + - workforce-wellbeing + - empathy +related_skills: + - ai-stakeholder-balance + - ai-augmentation-not-automation + - ai-emotional-intelligence + - emotional-intelligence + - psychological-safety + - employee-engagement-retention + - leading-through-change +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Human-Centered Approach + +Five fears live in every organisation contemplating AI, and not one of them is "robots will take my job." Ask employees what truly unsettles them, and the answers are more nuanced and more damning than the headlines suggest. They fear the loss of control -- that an algorithm will dictate their pace, their priorities, their breaks. They fear invisibility -- becoming a data point in a system that cannot see them as whole people. They fear the death of judgment -- that their expertise, built over years, will be overridden by a model trained on last quarter's numbers. They fear surveillance dressed as optimisation. And they fear the silence of leaders who deploy AI without ever asking how it feels on the receiving end. These fears do not appear in the ROI calculations that justify AI investment. They appear in the turnover data twelve months later. + +--- + +## The Framework + +### The Misconception: Human Users Do Not Equal Human-Centred + +An executive once insisted that his company's use of AI was human-centred. His reasoning was simple: the end users were humans, so any AI they used was, by definition, human-centred. This logic is widespread and entirely wrong. Deploying AI in a company made up of humans does not make the deployment human-centred any more than serving food in a restaurant makes it nutritious. A human-centred approach means adopting AI technologies in responsible and adaptive ways to improve people's performance, work lives, and experiences -- across dimensions that include not just efficiency but happiness, confidence, control, and a sense that what they do matters. + +### Why AI Projects Fail When Leaders Ignore the Emotional Response + +A CTO at a mid-sized company decided that the department producing reports -- marketing campaign impact, sales figures, delivery metrics -- should be supervised by an algorithm. The algorithm monitored worker pace, continuously adjusted targets based on prior performance, and flagged underperformers. The intent was more accurate reporting, delivered faster. + +The results were the opposite. Workers showed great variability in output. Reports failed to meet reliability standards. Machine supervision had backfired. Employees felt pressured to perform at peak capacity without interruption, experienced diminishing control over their tasks, and described feeling "treated like robots." Absenteeism rose. Turnover increased. Mental fatigue became pervasive. + +The diagnosis was not technical. People have good days and bad days. That variability is not a defect to be optimised away -- it is a feature of human cognition that enables creativity, reflection, and learning. An organisation's tolerance for variability signals to its people that it understands they are human. An algorithm that demands relentless consistency signals the opposite. + +### The Five Dimensions of Human-Centred AI + +A genuinely human-centred approach to AI deployment addresses five dimensions, each of which requires deliberate leadership action rather than passive assumption. + +**1. Efficiency With Respect** + +Efficiency remains a valid objective, but it cannot be the only one. When the sole metric is output per unit of time, AI becomes a mechanism for extracting maximum labour -- precisely the dynamic that industrial-era management reforms spent a century trying to dismantle. A human-centred approach pursues efficiency gains while respecting the cognitive and emotional limits of the people producing the output. The algorithm that adjusted for human behavioural variability -- accounting for individual working styles, life events, and the need for reflective pauses -- ultimately produced faster, more reliable results than the version that treated workers as uniform inputs. + +**2. Meaningful Work, Not Just Productive Work** + +Humans are not perfectly rational actors motivated solely by productivity. They derive satisfaction from competence, inclusion, respect, moral purpose, and curiosity. An AI deployment that maximises throughput while stripping work of meaning will produce resistance, disengagement, and attrition that no efficiency gain can offset. The human desire for meaningful work is not sentimentality. It is an empirical reality with direct consequences for performance. + +**3. Transparency and Governance** + +Employees need to know what data is being collected, how it is used, and who has access. An HR department at a Southeast Asian multinational was discovered referring to employees by staff numbers in internal communications, describing a worker as "XX13baXX" and categorising them as "high-risk elements" for the upcoming change project. When this email reached the wrong recipient and circulated among employees, the resulting outrage forced a formal apology. Transparency is not merely a regulatory requirement. It is the minimum condition for trust. + +**4. Human Control Over AI Interactions** + +If AI is presented as a tool for empowerment, employees must actually experience empowerment -- including the authority to question algorithmic recommendations, provide feedback on AI-driven targets, and withdraw from interactions they find counterproductive. A taxi company that introduced algorithmic dispatch found its drivers feeling dehumanised: they lost control over their routes, believed they were being excessively monitored, and felt prevented from exercising their own judgment about customer service. Regular feedback sessions and the discretion to override algorithmic suggestions restored both driver satisfaction and, ultimately, the algorithm's effectiveness. + +**5. Well-Being as a Metric, Not an Afterthought** + +Human-centred AI adoption requires treating employee well-being as an explicit design objective. This means collaborating with HR and technology teams before deployment to assess whether the AI system enhances or erodes self-confidence, adheres to ethical norms, and promotes rather than diminishes employee satisfaction. NASA and the US Department of Defense use technology-readiness scales to evaluate new systems; organisations deploying AI should develop analogous human-readiness scales that assess the impact on the people who will use the technology. + +### The Reflective Procrastination Principle + +The framework introduces a counterintuitive concept: reflective procrastination. Conventional management treats any pause in productivity as waste. But research demonstrates that taking longer breaks -- delaying work not from laziness but from the need to consider different perspectives -- produces better results through more divergent thinking and creativity. Sometimes slowing down the pace of work yields higher-quality output than algorithmic optimisation of speed. The implication for AI-driven work design is profound: systems that allow human-determined pacing outperform systems that impose algorithmic pacing, because they work with human cognition rather than against it. + +--- + +## Prompts + +**Prompt 1 -- Hidden Fear Inventory:** +> We are deploying AI in [describe context -- e.g., customer support, warehouse operations, financial analysis]. Interview simulation: ask me the questions an employee in each affected role would need answered before they could trust this deployment. Focus not on whether they will lose their job but on the five hidden fears: loss of control, invisibility, death of judgment, surveillance, and leadership silence. For each fear, suggest specific actions the leadership team should take. + +**Prompt 2 -- Human-Readiness Assessment:** +> Before we deploy [describe AI system], conduct a human-readiness assessment. Evaluate whether the system: preserves employee agency, accounts for human variability in performance, maintains transparency about data collection and use, includes mechanisms for employee feedback and override, and enhances rather than diminishes the meaningfulness of work. Identify gaps and recommend specific design changes. + +**Prompt 3 -- AI-Driven Work Redesign:** +> We have deployed an AI system that [describe what it does]. Employee feedback indicates [describe symptoms -- e.g., reduced morale, increased errors, higher absenteeism]. Diagnose the likely human-centred failures in the deployment. Propose a redesigned approach that achieves the same business objectives while respecting employee psychology, drawing on principles of human variability, reflective procrastination, and meaningful work. + +**Prompt 4 -- Communication Plan for AI Deployment:** +> Design a communication plan for our upcoming AI deployment that addresses employees as whole people, not as production inputs. The plan should: explain what the AI will do and why, explicitly state what it will not do, acknowledge the emotional impact of the change, provide channels for ongoing feedback, and include specific commitments about human oversight. Avoid the trap of leading with technical capabilities -- lead with the human story. + +--- + +## Use Cases + +**Validation-Stage SaaS Startup Introducing AI-Assisted Code Review** + +A 15-person SaaS startup introduces an AI tool that reviews code before human review, flagging potential issues and suggesting improvements. The founders expect developers to welcome the efficiency gain. Instead, senior developers feel their expertise is being questioned -- the tool occasionally flags their deliberate architectural choices as "issues." Junior developers become overly deferential to the AI's suggestions, accepting recommendations without critical evaluation. The CTO, recognising the pattern of eroded judgment and undermined expertise, redesigns the workflow: the AI provides suggestions as one input among several, developers are explicitly encouraged to override the tool when their judgment differs, and the team tracks cases where human judgment proved superior to AI recommendation. Within three months, the tool is used actively rather than resented -- because the developers control it rather than the reverse. + +**Growth-Stage Logistics Company Deploying Route Optimisation** + +A 150-person logistics company deploys AI-driven route optimisation for its delivery fleet. Drivers are told the AI will make them more efficient. What they experience is micromanagement: prescribed routes that ignore local knowledge, break schedules determined by an algorithm rather than by fatigue, and performance metrics that penalise any deviation from the optimal path. Driver turnover increases from 12 percent to 28 percent in six months. The operations director applies the human-centred framework by introducing three changes: drivers can override routes when local conditions warrant it, break timing is driver-determined within broad parameters, and a monthly "local knowledge" session allows drivers to feed experiential insights back into the routing model. Turnover returns to baseline. Route efficiency improves beyond the original AI-only benchmark, because the system now benefits from human contextual knowledge that the algorithm lacked. + +**Scale-Stage Manufacturing Firm Redesigning Shop Floor AI** + +A manufacturing company with 2,000 employees deploys AI across its shop floor to monitor equipment performance and worker productivity. The productivity monitoring component draws immediate resistance: workers describe feeling watched, judged, and reduced to numbers. A joint task force of floor supervisors, HR, and the AI team redesigns the system. Equipment monitoring remains fully automated. Productivity data is aggregated at the team level rather than the individual level, visible to teams as a coaching tool rather than a surveillance mechanism. Workers receive quarterly reports showing how AI-driven insights have improved safety outcomes -- giving the workforce a tangible, human-centred benefit from the technology. Resistance subsides not because the AI changed but because its relationship to the workforce changed. + +--- + +## Anti-Patterns + +1. **Leading with the technology instead of the human story.** Presenting AI deployment as a technical achievement -- data architectures, algorithm specifications, processing speeds -- signals to employees that the leader sees the world the way AI does: in ones and zeros. A middle manager at one company captured the sentiment: "I felt like I was only a data point in his eyes." The human story must come first, the technical story second. + +2. **Confusing employee silence with employee acceptance.** Employees who do not complain about AI are not necessarily comfortable with it. They may have concluded that resistance is futile, that the decision has already been made, or that raising concerns will mark them as obstacles. Active inquiry -- structured feedback sessions, anonymous surveys, skip-level conversations -- is the only reliable signal of true acceptance. + +3. **Optimising for consistency when variability is a feature.** Algorithms naturally seek to eliminate variability. Human performance variability is not noise to be filtered out; it is the mechanism through which creativity, adaptation, and learning occur. AI systems that demand robotic consistency from human workers will produce exactly the disengagement and poor performance they were designed to prevent. + +4. **Treating human-centred AI as a one-time design decision.** A system that is human-centred at deployment can become dehumanising as it evolves, as targets are adjusted upward, as oversight mechanisms atrophy, or as new management interprets the tool differently. Human-centredness requires ongoing governance, not a single design review. + +5. **Deploying AI to solve a leadership problem.** When morale is low, productivity is inconsistent, or quality is declining, the root cause is often leadership -- not a technology gap. Deploying AI to "fix" problems that originate in poor management produces a specific pathology: the technology amplifies the dysfunction while giving the leader a veneer of data-driven objectivity. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Defining the human-AI relationship | Before any technology decision, the founder must articulate a clear philosophy: is AI here to replace human capability or to enhance it? This philosophical choice shapes every subsequent design and deployment decision. | +| Validation | Testing with real humans, not just data | Prototyping must include testing the human experience of interacting with the AI, not just the accuracy of the AI's output. User testing should measure trust, control, and emotional response alongside technical metrics. | +| Early Traction | Establishing feedback loops | The first operational deployment is when real human-centred challenges emerge. Formal feedback mechanisms -- weekly check-ins, anonymous channels, override tracking -- must be established from day one and treated as signals, not noise. | +| Growth | Scaling human-centredness alongside AI | Growth creates pressure to standardise, and standardisation is the enemy of human-centred design. The challenge is maintaining individual adaptation, feedback responsiveness, and human override authority as the system scales. | +| Scale | Institutionalising human-centred governance | At scale, human-centredness can no longer depend on individual leaders. It must be embedded in governance structures: ethics boards, employee representation in AI design decisions, mandatory human-readiness assessments for new deployments, and regular audits of existing systems. | + +--- + +## Output Template + +```markdown +# Human-Centred AI Deployment Plan + +## System Overview +- **AI application:** [What the system does] +- **Affected workforce:** [Roles and number of people] +- **Business objective:** [What the AI is meant to achieve] + +## Human-Readiness Assessment +| Dimension | Current State | Risk Level | Required Action | +|---|---|---|---| +| Employee agency | [How much control do employees retain?] | [High/Medium/Low] | [Specific action] | +| Human variability | [Does the system accommodate good days and bad days?] | [High/Medium/Low] | [Specific action] | +| Transparency | [Do employees know what data is collected and how it is used?] | [High/Medium/Low] | [Specific action] | +| Override authority | [Can employees question or override AI recommendations?] | [High/Medium/Low] | [Specific action] | +| Meaningful work | [Does the AI enhance or diminish the meaning of the work?] | [High/Medium/Low] | [Specific action] | + +## Fear Mitigation Plan +| Hidden Fear | How This Deployment Triggers It | Specific Mitigation | +|---|---|---| +| Loss of control | [Describe] | [Action] | +| Invisibility | [Describe] | [Action] | +| Death of judgment | [Describe] | [Action] | +| Surveillance | [Describe] | [Action] | +| Leadership silence | [Describe] | [Action] | + +## Feedback Architecture +- **Frequency:** [How often feedback is collected] +- **Channels:** [Anonymous surveys, team sessions, one-on-ones, override logs] +- **Escalation path:** [What happens when feedback reveals a problem] +- **Commitment:** [How the organisation will respond to feedback] + +## Success Metrics (Human and Business) +| Metric | Target | Measurement Method | +|---|---|---| +| [Business metric -- e.g., throughput] | [Target] | [How measured] | +| [Human metric -- e.g., employee satisfaction] | [Target] | [How measured] | +| [Human metric -- e.g., turnover rate] | [Target] | [How measured] | +| [Human metric -- e.g., override frequency] | [Target] | [How measured] | +``` + +--- + +## Related Skills + +- **[AI Stakeholder Balance](../../content/skills/ai-leadership/ai-stakeholder-balance.md)** -- The human-centred approach operationalises stakeholder balance at the employee level, translating broad ethical principles into specific workforce practices. +- **[AI Augmentation Not Automation](../../content/skills/ai-leadership/ai-augmentation-not-automation.md)** -- Augmentation is the natural extension of human-centred design: AI that enhances human capability rather than supplanting it. +- **[AI Emotional Intelligence](../../content/skills/ai-leadership/ai-emotional-intelligence.md)** -- Leading a human-centred AI deployment requires the emotional intelligence to perceive and respond to employee fears that are rarely articulated directly. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Employees who do not feel psychologically safe will not provide honest feedback about their AI experience, rendering the entire feedback architecture useless. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- The human-centred approach is, at its core, an engagement and retention strategy specific to the AI context. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- General change leadership provides the foundation; this skill adapts those principles to the specific psychological dynamics of AI-driven transformation. diff --git a/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md b/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md deleted file mode 120000 index 9b4ab92..0000000 --- a/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-inclusive-collaboration.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md b/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md new file mode 100644 index 0000000..9bfcee3 --- /dev/null +++ b/plugins/foreman/skills/ai-inclusive-collaboration/SKILL.md @@ -0,0 +1,208 @@ +--- +name: "ai-inclusive-collaboration" +description: "Provides a comprehensive framework for designing inclusive human-AI collaboration that keeps all stakeholders at the design table. Addresses exclusion dynamics, algorithm aversion, trust deficits, silo formation, and the human cost of automation-first strategies. Use when employees resist AI adoption, when AI design excludes non-technical voices, when human-AI collaboration feels extractive rather than empowering, when organisational silos hinder AI scaling, or when leaders need to reward human contributions in AI-augmented work." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - human-ai-collaboration + - inclusion + - employee-engagement + - algorithm-aversion + - ai-trust + - participatory-design + - organisational-silos +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-communication-culture + - ai-vision-and-strategy + - inclusive-leadership + - psychological-safety + - ai-era-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Inclusive Collaboration + +Amazon warehouse workers, supervised by algorithms that tracked their every movement, eventually gathered outside their facilities with a rallying cry: "We are not robots." One employee distilled the grievance: "[Productivity] is all they care about. They don't care about their employees. They care more about the robots than they care about the employees." This was not a failure of technology. The algorithms performed precisely as designed. It was a failure of inclusion -- a leadership decision to optimise for efficiency while treating human workers as interchangeable with the machines monitoring them. The third pillar of AI-savvy leadership confronts this dynamic directly: when people are excluded from the design and deployment of AI systems, they resist, retreat, or revolt. The question every leader must answer is not whether their people can work with AI, but whether the people who will be most affected by AI were present when the system was designed. + +--- + +## The Framework + +### The Exclusion-Inclusion Spectrum + +The framework identifies two fundamentally different models for integrating AI into organisations: + +**The Exclusion Model** aims to minimise humans in the technical loop. Business operations and strategy are driven by a loop of computers where humans do not fit. Under this model, employees are valued solely for efficiency, pushed into rigid work structures supervised by AI, and stripped of autonomy. The consequences are predictable: demotivation, declining quality of human input, and counterproductive behaviour (Uber drivers, for instance, developed clever methods to manipulate algorithms that supervised them). + +**The Inclusion Model** positions AI as a collaborator that assists in cognitively demanding tasks, leveraging AI's analytical strengths while preserving and valuing distinctly human capabilities -- moral reasoning, contextual judgement, empathy, and creative sense-making. Under this model, employees are involved in designing the work settings in which humans and machines collaborate. + +The distinction between these models is the defining leadership choice of the AI era. + +### Three Benefits of Inclusive AI Adoption + +The research identifies three specific outcomes that inclusive approaches produce: + +**1. Feeling of Control** + +When employees participate in AI design and deployment decisions, they perceive the technology as a tool that works for them rather than a control mechanism imposed upon them. A bank employee who was told by an algorithm that a well-qualified applicant did not qualify for a credit card -- and could offer no explanation -- exemplifies the opposite: a human stripped of agency, unable to exercise the judgement that defines professional competence. + +**2. Reduced Algorithm Aversion** + +Research shows that humans prefer to work with and receive advice from other humans, even when AI demonstrably outperforms human alternatives. This aversion is not rational; it is emotional. People feel uncomfortable with entities that show little similarity to themselves. Inclusive leaders address this by positioning themselves as mediators and facilitators in human-AI interactions, ensuring employees receive training to interact effectively with AI systems while maintaining access to human support when interactions go wrong. + +**3. Increased Trust** + +Nearly half of all employees globally do not trust AI at work. Trust cannot be manufactured through technical improvements alone -- better accuracy, better explainability. Trust requires that employees believe their leaders are competent, honest, and benevolent in their AI decisions. Inclusion builds this trust by giving employees visibility into how AI works, what it can and cannot do, and why it has been deployed. + +### Four Steps to Inclusive AI Adoption + +The framework prescribes four concrete actions: + +**Step 1 -- Create Space for Social Connection** + +People who work extensively with AI experience loneliness and isolation. Digital life underwriters who assess insurance applications through AI-based systems never meet the applicants; they interact only with data. Leaders must counterbalance this by creating deliberate opportunities for human-to-human interaction -- social events, cross-team meetings, scheduled time away from screens. + +**Step 2 -- Make Tech and Non-Tech Teams Work Side by Side** + +Cross-discipline collaboration is the foundation of successful human-AI partnerships. Tech and business experts cannot retreat to separate spaces. Business experts explain organisational requirements; tech experts suggest appropriate AI approaches; HR familiarises everyone with the skills needed; operational staff integrate the human-AI workflow. The leader's role is to be an "analytics-to-business translator" -- someone who bridges jargon gaps and decomposes large problems into actionable components. + +The cost of failure is illustrated by the case of a CEO at a global financial institution who interrupted his CTO's technology strategy presentation, demanding it be reduced to "three simple bullet points." The tech group pulled back from communicating with senior leadership entirely. The CEO's inability to translate between technical and business perspectives doomed the AI project within a year. + +**Step 3 -- Develop Leadership and Inclusion Skills** + +AI-savvy leaders must be perceived as someone who listens, who accounts for the uncertainties and discomfort employees feel, and who demonstrates humility about their own knowledge gaps. Research shows that employees are more willing to trust AI and engage with it when their leaders are seen as humble people willing to listen. Satya Nadella's practice of telling Microsoft employees that he, too, has knowledge gaps models the behaviour that makes inclusion possible. + +**Step 4 -- Reward Workers for Being Human** + +When AI and humans collaborate, clear guidelines must establish who -- or what -- receives credit. The 2022 Colorado State Fair art competition became a flashpoint when a human artist won using a generative AI tool. Critics dismissed his contribution as "pressing a few buttons." In reality, substantial human judgement, iterative prompting, and creative selection underpinned the work. Leaders must ensure employees share in the rewards created by human-AI collaboration, and that human contributions are recognised rather than diminished. + +### The Silo Problem + +AI adoption deepens organisational silos in three ways: + +1. **Technical expertise concentration** -- only tech teams understand the AI systems, creating barriers for HR, operations, and marketing. +2. **Data ownership conflicts** -- different departments maintain separate data repositories and resist sharing. +3. **Uneven AI impact** -- some teams benefit from AI while others feel threatened, producing siloed behaviour where information is hoarded for self-protection. + +When departments operate in isolation, data becomes fragmented, cross-functional problem-solving vanishes, and the organisation loses its ability to scale AI effectively. + +--- + +## Prompts + +**Prompt 1 -- Inclusion Audit:** +> "Conduct an inclusion audit of our AI adoption process. Our organisation [describe size, industry, AI maturity]. The AI systems we have deployed or are deploying include [describe]. For each system, assess: (1) Which stakeholders were present when the system was designed? (2) Which stakeholders were absent? (3) What are the likely consequences of their absence? (4) What specific steps can we take to bring excluded voices to the table, using the four-step inclusion framework?" + +**Prompt 2 -- Algorithm Aversion Mitigation:** +> "Our employees are resisting a new AI system [describe system and context]. Resistance manifests as [describe behaviours -- avoidance, workarounds, open complaints]. Using the framework on algorithm aversion and inclusion, help me diagnose the root cause and design an intervention that includes: (1) repositioning my role as mediator between employees and AI, (2) training that addresses emotional rather than just technical concerns, (3) mechanisms for employees to speak to a human when AI interactions go wrong, and (4) a timeline for building trust incrementally." + +**Prompt 3 -- Cross-Functional AI Team Design:** +> "Design an inclusive, cross-functional team structure for our AI initiative [describe project]. The team must include tech experts, domain experts, HR, and operational staff. For each role, specify: (1) what they contribute, (2) what questions they should be empowered to ask, (3) how to prevent tech experts from dominating discussions, and (4) how I as leader serve as the analytics-to-business translator that the framework describes." + +**Prompt 4 -- Human Reward Framework for AI Collaboration:** +> "Our organisation is deploying AI in [describe context] where humans and AI will produce outputs collaboratively. Help me design a reward and recognition framework that: (1) clearly attributes human contributions to AI-augmented work, (2) prevents the devaluation of human input, (3) establishes guidelines for crediting collaborative outputs, and (4) communicates to employees that their uniquely human capabilities -- judgement, creativity, empathy -- are valued more, not less, as AI becomes prevalent." + +--- + +## Use Cases + +**Early-Traction Customer Service Platform Automating the Wrong Tasks** + +A startup building an AI-powered customer service platform automates all routine queries, leaving human agents to handle only the most difficult and emotionally charged interactions -- complaints escalated because the AI failed. Agents report burnout, anxiety, and declining job satisfaction. Turnover reaches 40 percent. Applying the inclusion framework, the startup redesigns its human-AI allocation. Rather than giving humans only what AI cannot handle, the system routes a balanced mix of interactions to human agents, including straightforward ones that provide psychological relief between difficult cases. Agents are included in redesigning the routing logic, contributing domain knowledge about which interactions benefit most from human empathy. Within six months, turnover drops to 15 percent and customer satisfaction improves -- not because the AI got better, but because the humans were finally included in the design. + +**Growth-Stage Manufacturing Firm Where Silos Block AI Scaling** + +A manufacturing company successfully deploys AI in quality control at one plant. Attempts to scale the system across four additional plants fail because each plant maintains its own data repositories, uses different data formats, and resists sharing information with central IT. The pattern matches the silo diagnosis precisely. The COO establishes cross-plant AI working groups that include plant managers, quality engineers, IT staff, and frontline workers from each facility. She centralises data storage in a cloud-based platform with shared access while appointing data governance liaisons at each plant -- people who own the local relationship with both the data and the colleagues who generate it. Critically, she rewards the plants not for individual AI performance metrics but for contributions to the shared AI capability across the organisation. + +--- + +## Anti-Patterns + +**Deploying AI and announcing it after the fact.** Presenting employees with a finished AI system and expecting adoption is the fastest route to resistance. Inclusion means involvement from the design stage, not notification after deployment. + +**Automating the easy work and leaving humans the hard parts.** When AI handles routine tasks and humans receive only the difficult, ambiguous, or emotionally draining cases, the result is not efficiency. It is a recipe for burnout, resentment, and attrition. This pattern is documented in call centres where AI handles simple queries, leaving human workers to absorb the full emotional weight of dissatisfied customers. + +**Assuming better AI accuracy will solve the trust problem.** Technical teams often respond to employee distrust by improving model performance. Research shows that trust in AI continues to decline even as accuracy improves. Trust is a leadership and inclusion problem, not a technical one. + +**Letting IT supervise human-AI collaboration instead of HR.** When the integration of humans and AI is managed by IT departments rather than human resources, the implicit message is that employees and AI are interchangeable commodities. This structural choice is a signal of exclusion that employees read clearly. + +**Ignoring the loneliness tax.** AI adoption increases the time employees spend interacting with screens and decreases the time they spend with other humans. Leaders who do not deliberately create space for social connection will lose engagement, creativity, and institutional knowledge to isolation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Inclusive founding principles | Establish from day one that all stakeholders will participate in AI design decisions; build inclusion into the company's DNA | +| Validation | Participatory prototyping | Include target users and affected employees in AI system design before the technology is finalised | +| Early Traction | Cross-functional team formation | Build diverse teams that combine technical, domain, and operational expertise; prevent tech-only AI development | +| Growth | Silo prevention at scale | As AI spreads across departments, actively break down data silos and ensure cross-functional collaboration persists | +| Scale | Institutional inclusion architecture | Formalise inclusion practices -- reward frameworks, social connection infrastructure, human-AI collaboration guidelines -- into organisational policy | + +At idea and validation stages, the cost of inclusion is low and the return is high. Including diverse perspectives in AI design at this point prevents costly redesigns later. A startup that includes frontline users in its AI design process from the beginning builds a product that works with human workflows rather than against them. + +At growth and scale, inclusion becomes a governance challenge. The four-step framework must be institutionalised: social connection time built into schedules, cross-functional teams embedded in standard operating procedures, leadership humility modelled from the top, and human contribution recognised in performance and reward systems. + +--- + +## Output Template + +**Target Audience: Team / Leadership** + +```markdown +# Human-AI Collaboration Inclusion Assessment +## Date: [Date] +## AI System/Initiative: [Name] + +### Stakeholder Presence Audit +| Stakeholder Group | Present at Design | Present at Deployment | Impact Level | Inclusion Gap | +|-------------------|------------------|-----------------------|-------------|---------------| +| [Group] | [Yes/No] | [Yes/No] | [High/Med/Low] | [Describe] | + +### Inclusion Model Assessment +- Current model: [Exclusion / Partial Inclusion / Full Inclusion] +- Evidence: [Specific indicators] +- Target model: [Describe desired state] + +### Four-Step Inclusion Plan +| Step | Current State | Target State | Actions Required | +|------|--------------|-------------|-----------------| +| Social connection | [Assess] | [Goal] | [Specific actions] | +| Cross-functional teams | [Assess] | [Goal] | [Specific actions] | +| Leadership inclusion skills | [Assess] | [Goal] | [Specific actions] | +| Human reward recognition | [Assess] | [Goal] | [Specific actions] | + +### Silo Risk Assessment +- Data sharing barriers: [List] +- Cross-functional collaboration gaps: [List] +- Recommended structural changes: [List] + +### Trust Indicators to Monitor +- Employee AI trust score (baseline): [Measure] +- Algorithm aversion incidents: [Track] +- Voluntary AI adoption rate: [Measure] +``` + +--- + +## Related Skills + +- **[AI Communication Culture](../../content/skills/ai-leadership/ai-communication-culture.md)** -- Flat communication structures are the prerequisite for inclusive AI collaboration; without information flowing freely, inclusion remains performative. +- **[AI Learning for Leaders](../../content/skills/ai-leadership/ai-learning-for-leaders.md)** -- Leaders who understand AI can serve as the analytics-to-business translators that inclusive collaboration demands. +- **[AI Purpose-Driven Questions](../../content/skills/ai-leadership/ai-purpose-driven-questions.md)** -- Inclusive collaboration ensures that purpose-driven questions reflect diverse stakeholder perspectives, not just leadership assumptions. +- **[Inclusive Leadership](../../content/skills/leadership/inclusive-leadership.md)** -- Covers daily DEI practices broadly; this skill focuses specifically on inclusion in human-AI collaboration design. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework underpins the trust environment required for employees to voice concerns about AI without fear. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- The structural conditions for team effectiveness apply with particular force to hybrid human-AI teams where role clarity and adequate resources determine collaborative success. diff --git a/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md b/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md deleted file mode 120000 index 85be166..0000000 --- a/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-learning-for-leaders.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md b/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md new file mode 100644 index 0000000..1d440e9 --- /dev/null +++ b/plugins/foreman/skills/ai-learning-for-leaders/SKILL.md @@ -0,0 +1,201 @@ +--- +name: "ai-learning-for-leaders" +description: "Guides non-technical leaders through building AI savviness without becoming AI experts, closing the gap between AI understanding and AI deployment. Applies the 'just savvy enough' principle and lifelong AI learning framework. Use when a leader feels inadequate about AI knowledge, defers too heavily to technologists, needs to build a business case for AI, wants to lead AI adoption without a technical background, or seeks to distinguish AI-knowledgeable from AI-savvy leadership." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-literacy + - leadership-development + - digital-transformation + - ai-adoption + - lifelong-learning + - confidence-gap +related_skills: + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-communication-culture + - ai-vision-and-strategy + - learning-agility + - ai-era-leadership + - growth-mindset +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Learning for Leaders + +Between what leaders know about AI and what they actually do with it lies a gap that widens by the quarter. Research conducted in Singapore -- a country ranked fourth globally in digital competitiveness -- found that two-thirds of managers considered their organisations ineffective at using AI systems they had already purchased. The technology was not the problem. The leaders were. They had disengaged from AI adoption projects, paralysed by a sense of inadequacy, and handed the keys to technologists who understood algorithms but not the business. This is the confidence problem: the more leaders learn about AI, the more they become aware of what they do not know, and the less inclined they are to lead. The antidote is not expertise. It is savviness -- knowing just enough to ask the right questions, make sound decisions, and refuse to be sidelined by jargon. + +--- + +## The Framework + +### The Gap: Understanding vs. Deployment + +The framework identifies a structural tension at the heart of AI-era leadership. AI technology evolves at a pace that outstrips any individual's ability to master it, yet organisations expect their leaders to be proactive in its use and governance. This creates what he terms the **AI knowledge-usage gap**: leaders fall further behind in understanding even as deployment accelerates around them. + +The gap produces a predictable leadership failure mode: + +1. **Enthusiasm** -- Leaders hear about AI's transformative potential and invest heavily in infrastructure, talent, and tooling. +2. **Inadequacy** -- Once engagement begins, leaders discover they cannot speak the language of data scientists or evaluate technical trade-offs. Doubt sets in. +3. **Deference** -- Leaders quietly withdraw from AI decision-making, ceding authority to technologists who lack business context. +4. **Failure** -- Without leadership connecting AI to organisational purpose, employees see no reason to adopt the tools. The investment stalls. Boards pull the plug. + +Research across dozens of organisations reveals that 87 percent of digital transformation projects fail -- not because the technology underperforms, but because leadership is absent from the process. + +### The "Just Savvy Enough" Principle + +The central insight of this framework is liberating: **business leaders do not need to become AI experts.** They need to become AI-savvy -- possessing enough foundational understanding to recognise AI's potential, articulate its business value, and maintain oversight without deferring to technologists by default. + +AI savviness operates at two levels: + +**Level 1 -- What AI Is and Is Not** + +Leaders must understand that AI systems are computational tools with self-learning abilities. They can analyse vast datasets, identify patterns, and make predictions. They cannot infer meaning, exercise moral reasoning, appreciate cultural nuance, or replace human judgement in ambiguous situations. AI is, in essence, "a really good calculator that works faster and can work with more data than humans can." Grasping this distinction prevents two common errors: overestimating AI's capability (leading to reckless delegation) and underestimating its utility (leading to avoidance). + +**Level 2 -- What Kind of AI Fits the Business Context** + +Leaders should understand which AI techniques serve which business purposes. Machine learning models trained on supervised data suit prediction tasks where human control matters. Reinforcement learning with human feedback enables iterative improvement. Leaders need not build these systems, but they must know enough to ask whether the chosen approach allows for the human oversight their organisation requires. + +### From Knowledge to Lifelong Learning + +Knowing AI basics is necessary but insufficient. The framework emphasises that AI savviness is not a one-time achievement. It is a continuous practice. The field evolves constantly -- new techniques, new applications, new ethical considerations. Leaders who treat AI education as a checkbox will find their knowledge obsolete within months. + +Effective lifelong AI learning includes: + +- **Daily reading** -- at least one hour, split between AI developments and leadership practice. One executive profiled in the research reads for an hour every day without exception, treating it as non-negotiable. +- **Periodic check-ins with technical teams** -- not to audit their work, but to understand what they are building and why. +- **Peer discussions** -- conversations with other leaders navigating similar challenges. +- **Ethical education** -- staying current on AI bias, fairness, and regulatory developments. Sam Altman's public acknowledgement that ChatGPT carries societal dangers illustrates why this dimension cannot be ignored. +- **Leading by example** -- using AI tools personally and visibly, signalling to the organisation that leaders are not above the technology they promote. + +### The Satya Nadella Model + +The framework holds up Microsoft CEO Satya Nadella as the exemplar of AI-savvy leadership. Nadella credits Microsoft's AI success not to having the best technology but to leadership setting the tone -- promoting a growth mindset, demonstrating humility, and modelling openness to new ways of working. His approach proves that savviness is a leadership posture, not a technical credential. + +--- + +## Prompts + +**Prompt 1 -- AI Savviness Self-Assessment:** +> "Assess my current AI savviness as a business leader. I lead [describe organisation/team] in [industry]. My current AI knowledge includes [describe what you know]. My organisation's AI maturity is [describe]. Using the two-level framework (understanding what AI is/is not, and understanding which AI fits my business context), identify my specific knowledge gaps and create a 90-day learning plan that makes me 'just savvy enough' to lead AI adoption without becoming a technologist." + +**Prompt 2 -- Business Case for AI Adoption:** +> "Help me build a business case for AI adoption in [specific business function]. I need to articulate: (1) which specific problems AI will solve (not which tools we should buy), (2) what kind of AI technique is appropriate and why, (3) where human oversight remains essential, (4) what the realistic timeline and expectations should be (avoiding the trap of projecting immediate ROI), and (5) how I will personally stay engaged rather than delegating to the tech team." + +**Prompt 3 -- Closing the Confidence Gap:** +> "I am a non-technical leader who feels increasingly sidelined in AI discussions at [describe organisation]. When technologists present, I defer rather than challenge. Help me design a confidence-building strategy that includes: key AI concepts I must understand to hold intelligent conversations, questions I should ask in every AI project review, red flags that indicate I am being excluded from decisions I should own, and a script for re-establishing my leadership authority over AI initiatives without pretending to technical expertise I lack." + +**Prompt 4 -- Lifelong AI Learning Architecture:** +> "Design a sustainable AI learning practice for me as a [role] in [industry]. The practice must fit into my existing schedule, cover both AI fundamentals and leadership implications, include peer learning and technical team engagement, and produce measurable improvement in my ability to guide AI-related decisions. Include specific resources, cadences, and accountability mechanisms." + +--- + +## Use Cases + +**Validation-Stage Healthtech Founder Who Over-Delegates to a CTO** + +A non-technical founder building an AI-powered diagnostic tool discovers that every product decision has been made by the CTO without business input. The founder cannot evaluate whether the chosen machine learning approach is appropriate, cannot explain the product's AI capabilities to investors, and has lost credibility with the board. Applying the framework, the founder does not enrol in a computer science course. Instead, she dedicates two weeks to understanding supervised learning at a conceptual level, learns enough statistical vocabulary to discuss model accuracy with her CTO, and establishes a weekly meeting where the CTO must translate technical decisions into business implications. Within a month, she catches a critical misalignment: the model optimises for diagnostic speed rather than accuracy, which contradicts the company's value proposition to cautious hospital clients. + +**Growth-Stage Retail Company Where Leaders Abandoned AI Post-Launch** + +A retail company invested heavily in an AI-based recommendation engine. Initial enthusiasm faded when leaders realised they did not understand the system's outputs. They retreated to traditional methods while the AI platform gathered dust. Employees, observing their leaders' disengagement, saw no reason to adopt the tool themselves. The "If they don't, why should I?" dynamic took hold. A new COO, guided by the lifelong learning principle, spends her first month using the recommendation engine daily, sharing what she learns in team meetings, and asking frontline staff what the system gets right and wrong. She does not pretend to understand the underlying algorithms. She demonstrates curiosity and ownership. Within six months, platform usage triples. + +**Scale-Stage Financial Services Firm Building Institutional AI Learning** + +A multinational bank has deployed AI across credit scoring, fraud detection, and customer segmentation. Individual leaders have varying levels of AI literacy -- some are deeply engaged, others are entirely dependent on their technology officers. The CEO recognises that the organisation's AI capability depends on whoever happens to occupy leadership roles, which is unsustainable. Applying the institutional learning framework, the bank creates a three-tier programme: in-house workshops led by data science teams (translating technical work into business language), an external executive education partnership with a business school for advanced AI leadership modules, and a peer learning circle where senior leaders share AI decision-making experiences monthly. The programme is not optional. It is embedded in the leadership development pipeline alongside financial acumen and people management. Two years later, leadership transitions no longer disrupt AI initiatives because incoming leaders arrive with baseline savviness. + +--- + +## Anti-Patterns + +**Enrolling in a coding bootcamp.** The instinct to become technically proficient is understandable but misguided. Leaders who spend months learning Python emerge with just enough knowledge to be dangerous -- capable of questioning technical details while losing sight of strategic leadership. AI savviness is about judgement, not code. + +**Treating AI education as a one-time event.** Leaders who attend a single AI workshop and consider themselves prepared will find their knowledge obsolete before the next quarter. The framework demands continuous learning, not episodic exposure. + +**Deferring to technologists on business questions.** The most corrosive anti-pattern occurs when leaders let data scientists define the organisation's AI strategy. Technologists are trained to optimise models, not to articulate organisational purpose or navigate stakeholder concerns. When leaders ask their analytics team "what should we do with AI?" they have abdicated their primary responsibility. + +**Confusing AI knowledge with AI savviness.** A leader who can explain how a neural network operates but cannot connect that knowledge to a customer retention problem is knowledgeable but not savvy. Savviness is applied understanding -- the ability to translate technical capability into business value. + +**Waiting until you feel ready.** Perfectionism disguised as prudence. The gap between knowledge and deployment will never close completely. Leaders who wait for full understanding before engaging will wait indefinitely while their organisations drift. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Foundational AI literacy | Understand what AI can and cannot do; assess whether AI is genuinely relevant to the problem the venture addresses | +| Validation | AI-informed product thinking | Learn enough to evaluate whether AI is the right tool for the specific use case, not just an impressive technology to mention in pitch decks | +| Early Traction | Leading the first AI deployment | Maintain active involvement as AI moves from concept to implementation; resist the urge to hand off to technologists | +| Growth | Scaling AI across the organisation | Expand from a single use case to enterprise-wide adoption; model AI usage personally to drive cultural change | +| Scale | Institutional AI governance | Establish continuous learning infrastructure -- workshops, peer circles, ethical reviews -- that outlasts any single leader | + +At the idea stage, the temptation is to treat AI as a feature to attract investors. Resist this. AI savviness at this stage means honestly evaluating whether the proposed solution requires AI at all, or whether simpler approaches would suffice. Investors see through AI window-dressing faster than founders expect. + +During growth and scale, the leader's personal learning journey becomes the organisation's learning culture. The research shows that employees mirror their leaders' relationship with AI. A leader who learns publicly, admits gaps openly, and engages with the technology visibly creates permission for the entire organisation to do the same. + +The ethical dimension of learning intensifies at scale. As AI systems are applied to increasingly sensitive business use cases, the considerations needed to ensure responsible deployment evolve constantly. Leaders must learn not only about AI capabilities but about emerging biases, regulatory shifts, and the responsibilities that accompany powerful technology. OpenAI's Sam Altman publicly acknowledging that his own creation, ChatGPT, carries societal dangers illustrates why ethical learning is not a peripheral concern -- it is central to credible AI leadership. + +The framework also emphasises that lifelong learning is collaborative, not solitary. Organisations can accelerate their leaders' development by creating in-house workshops, inviting experienced industry peers and external faculty, and partnering with business schools. The individual leader's commitment to learning must be matched by institutional investment in making that learning possible, structured, and continuous. + +--- + +## Output Template + +**Target Audience: Board / Leadership Team** + +```markdown +# AI Savviness Assessment and Learning Plan +## Date: [Date] +## Leader: [Name / Role] + +### Current State Assessment +- AI Knowledge Level: [Basic / Intermediate / Advanced] +- AI Engagement Level: [Disengaged / Deferential / Active / Leading] +- Key Knowledge Gaps: [List specific gaps at Level 1 and Level 2] + +### The Confidence Gap +- Situations where I defer to technologists unnecessarily: [List] +- Decisions I should own but currently do not: [List] +- Business questions that remain unasked in AI discussions: [List] + +### 90-Day Learning Plan +| Week | Focus Area | Activity | Outcome | +|------|-----------|----------|---------| +| 1-2 | AI fundamentals | [Specific activity] | [Measurable outcome] | +| 3-4 | Business context fit | [Specific activity] | [Measurable outcome] | +| 5-8 | Applied practice | [Specific activity] | [Measurable outcome] | +| 9-12 | Leadership integration | [Specific activity] | [Measurable outcome] | + +### Ongoing Learning Architecture +- Daily: [Reading / tool usage commitment] +- Weekly: [Technical team check-in format] +- Monthly: [Peer discussion / review cadence] +- Quarterly: [Ethical and regulatory update process] + +### Leading by Example +- AI tools I will use personally and visibly: [List] +- Forums where I will demonstrate learning publicly: [List] +- How I will signal that AI engagement is expected, not optional: [Plan] +``` + +--- + +## Related Skills + +- **[AI Purpose-Driven Questions](../../content/skills/ai-leadership/ai-purpose-driven-questions.md)** -- Learning what AI can do is the prerequisite; knowing which questions to ask it is the application. These two skills form a natural sequence. +- **[AI Communication Culture](../../content/skills/ai-leadership/ai-communication-culture.md)** -- AI-savvy leaders must translate their learning into shared language that bridges technical and business teams. +- **[AI Vision and Strategy](../../content/skills/ai-leadership/ai-vision-and-strategy.md)** -- Foundational AI knowledge enables the visionary thinking required to set long-term AI strategy. +- **[Learning Agility](../../content/skills/leadership/learning-agility.md)** -- Covers general continuous learning practices; this skill applies those principles specifically to AI as a non-technical leader. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Nadella's approach to AI-savvy leadership is built on Dweck's growth mindset; the two frameworks reinforce each other directly. +- **[AI Augmentation Not Automation](../../content/skills/ai-leadership/ai-augmentation-not-automation.md)** -- Understanding AI capabilities is the prerequisite for making informed augmentation-versus-automation decisions about specific tasks and roles. diff --git a/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md b/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md deleted file mode 120000 index 7991e97..0000000 --- a/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-purpose-driven-questions.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md b/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md new file mode 100644 index 0000000..8022c65 --- /dev/null +++ b/plugins/foreman/skills/ai-purpose-driven-questions/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "ai-purpose-driven-questions" +description: "Teaches leaders to ground AI adoption in organisational purpose by asking the right questions before selecting tools. Applies the purpose-driven framework to prevent technology-for-technology's-sake deployments. Use when evaluating AI investments against business goals, when data scientists operate without strategic direction, when AI projects lack clear problem definitions, when aligning AI initiatives with company values, or when leaders are tempted to adopt AI because competitors have." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-strategy + - purpose-alignment + - data-driven-decisions + - business-questions + - ai-adoption + - value-alignment +related_skills: + - ai-learning-for-leaders + - ai-inclusive-collaboration + - ai-communication-culture + - ai-vision-and-strategy + - purpose-driven-leadership + - balanced-scorecard + - ai-era-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Purpose-Driven Questions + +Most leaders ask the wrong first question about AI. They ask "Which AI tool should we use?" or "What can AI do for us?" -- questions that position technology as the starting point and the organisation as the beneficiary of whatever the algorithms happen to produce. Garry Kasparov, the chess grandmaster who lost to IBM's Deep Blue in 1997, offers a sharper frame. "Machines don't have understanding," he told a TechCrunch audience. "They don't have a purpose." Neither, it turns out, do most AI deployments. A large telecom company deployed AI to predict customer churn, then bombarded at-risk customers with advertising. Many left anyway. The AI had answered the wrong question. It identified who was likely to leave rather than who could be persuaded to stay -- a distinction no algorithm could make without a human defining the purpose of the analysis. The technology worked perfectly. The leadership failed entirely. + +--- + +## The Framework + +### Why Purpose Must Precede Technology + +The second pillar of AI-savvy leadership rests on an uncomfortable observation: most business leaders cannot clearly articulate why their organisation exists. When asked what their company aims to achieve beyond making profits, they produce the same boilerplate values that appear on every corporate website. This vagueness is tolerable in ordinary operations. It becomes fatal when deploying AI, because AI systems require precise questions to produce useful answers, and those questions can only emerge from a clear understanding of organisational purpose. + +The failure pattern is consistent: + +1. Leaders declare the company a "data company" and invest millions in data infrastructure. +2. Data scientists amass enormous datasets and build sophisticated models. +3. The models produce insights that are technically impressive but strategically meaningless -- answering questions nobody in leadership thought to ask. +4. Leaders adopt the data scientists' conclusions as strategy, inverting the proper relationship between business leadership and technical analysis. + +This is the **purpose inversion**: letting data define strategy rather than using strategy to direct data collection and analysis. + +### The Question Hierarchy + +Purpose-driven AI adoption follows a strict hierarchy of questions: + +**Tier 1 -- Purpose Questions (Leaders Own These)** +- Why does this organisation exist? +- What values guide our decisions? +- Which stakeholder needs must we serve? +- What problems are we uniquely positioned to solve? + +**Tier 2 -- Strategic Questions (Leaders Ask These of Data Teams)** +- Does our data allow us to answer questions relevant to our purpose? +- If not, what data must we collect? +- Are we measuring what matters, or merely what is measurable? + +**Tier 3 -- Technical Questions (Data Teams Own These)** +- Which AI technique best addresses the strategic question? +- What are the model's limitations and biases? +- How do we validate outputs against real-world outcomes? + +The critical insight: **Tier 1 and Tier 2 questions are the leader's job.** They cannot be delegated to data scientists, who are trained to optimise models, not to interpret the purpose of a business. When leaders skip directly to Tier 3 -- "What AI should we buy?" -- they cede the most consequential decisions to people who lack the framework to make them. + +### Technology Is Neutral; Leaders Are Not + +The framework emphasises a point that much of the AI discourse ignores: all technology is neutral. AI can identify outcomes and even make decisions that influence lives, but it cannot intentionally pursue values. It has no common sense, no moral reasoning, no understanding of why humans are in business. Marvin Minsky identified this decades ago as the "common sense problem." Yann LeCun, chief AI scientist at Meta, recently confirmed that the AI community has not developed learning paradigms that allow machines to understand how the world works. + +The implication is stark. AI cannot ask the questions that matter to your organisation. Those questions emerge from purpose -- from human understanding of what the company values and why it exists. Leaders who expect AI to generate strategic direction are waiting for a calculator to develop opinions. + +### The Purpose-Profit Tension + +The framework confronts the practical challenge head-on: AI adoption requires substantial investment, and investors expect returns. Purpose-driven leadership does not mean ignoring economics. It means ensuring that the pursuit of profit operates within the broader context of organisational purpose. As Larry Fink, CEO of BlackRock, puts it: "Purpose is not the sole pursuit of profits, but the animating force for achieving them." + +A purpose-driven AI leader communicates that AI adoption is a long-term investment in sustainable value creation, not a short-term cost-cutting exercise. When this message is internalised, data scientists shift from maximising the volume of data analysed to focusing on the quality and relevance of insights produced. + +--- + +## Prompts + +**Prompt 1 -- Purpose Audit for AI Readiness:** +> "Help me conduct a purpose audit before our organisation adopts AI. Our stated mission is [describe]. Our actual strategic priorities are [describe]. The AI project under consideration would [describe]. Walk me through the question hierarchy: (1) Does this AI initiative align with our purpose, or is it technology-for-technology's-sake? (2) Are we asking the right questions of the data, or letting the data define our questions? (3) What purpose-driven questions should I bring to our data science team?" + +**Prompt 2 -- Reframing the Wrong Question:** +> "Our organisation is about to deploy AI to [describe project]. The project was initiated because [describe trigger -- competitor pressure, board mandate, etc.]. I suspect we are asking the wrong question. Help me apply the purpose-driven framework to: (1) identify what question we are actually asking the AI to answer, (2) determine whether this is the right question given our organisational purpose and values, (3) reframe the question if needed, and (4) identify what data we would need to answer the reframed question." + +**Prompt 3 -- Purpose-Technology Reconciliation:** +> "Our organisation's purpose is [describe]. AI technology is evolving rapidly in our industry, with competitors adopting [describe]. I feel pressure to match their moves. Help me reconcile our fixed purpose with the need to stay technologically current. Using the principle of 'be firm with the purpose, be agile with the technology,' design an approach that keeps us anchored to our values while remaining adaptive in our AI strategy." + +**Prompt 4 -- Data Scientist Collaboration Framework:** +> "I need to restructure my relationship with our data science team. Currently, they operate autonomously and report insights that I then try to incorporate into strategy. I want to invert this: I define the purpose-driven questions, they find the data and methods to answer them. Help me design: (1) a recurring meeting structure, (2) a question template I should bring to each session, (3) criteria for evaluating whether their work addresses our strategic priorities, and (4) a communication approach that respects their expertise while asserting my leadership over business direction." + +--- + +## Use Cases + +**Idea-Stage Fintech Founder Seduced by AI Capabilities** + +A founder planning an AI-powered lending platform becomes fixated on the technology's ability to process loan applications in seconds. Every pitch deck emphasises speed and automation. An advisor applies the purpose framework and asks a simple question: what problem is the business actually solving? The founder pauses. Speed is not the problem -- underserved borrowers lack access to fair credit evaluation, not faster rejection. This reframing shifts the entire AI strategy from optimising processing speed to building models that assess creditworthiness using non-traditional data points (utility payments, rental history) that serve the purpose of expanding access. The technology changes; the purpose clarifies everything. + +**Early-Traction SaaS Company Where Data Science Operates in a Vacuum** + +A B2B SaaS company has hired three data scientists who spend their time building increasingly sophisticated churn prediction models. The CEO, not technically fluent, waits for their reports and adjusts strategy accordingly. When the framework is applied, the fundamental dysfunction becomes visible: the data scientists are answering the question "which customers will leave?" when the purpose-aligned question is "which customers derive the most value from our product, and how do we deepen that value?" The CEO begins monthly meetings where he presents the company's strategic priorities and asks the data team to evaluate whether existing data can address those priorities. The first meeting reveals that the company collects extensive usage data but nothing about customer outcomes -- a gap that no amount of churn modelling could have exposed. + +**Growth-Stage Retailer Racing to Match Competitors** + +A mid-size retailer observes that every competitor has deployed AI-powered recommendation engines and feels compelled to follow. The Apple example proves instructive: Apple, known as a fast follower, declined to enter the LLM arms race because it conflicted with the company's privacy-centric purpose. The retailer's purpose centres on curated, personalised customer relationships -- a value that a generic recommendation engine might actually undermine if it reduces human interaction to algorithmic suggestions. The company instead deploys AI to augment its sales associates with real-time customer preference data, preserving the human relationship while enhancing it with analytical capability. Purpose dictates the deployment, not competitive anxiety. + +--- + +## Anti-Patterns + +**Asking data scientists to define business strategy.** When leaders tell their analytics team to "find something interesting in the data," they have surrendered strategic direction. Data scientists will optimise whatever metric they are given. Without purpose-driven questions from leadership, they optimise for the wrong things. + +**Confusing data volume with strategic clarity.** The research documents organisations that invest millions to amass ever-larger datasets, convinced that more data equals better decisions. Without purpose-driven questions guiding what data matters, the organisation drowns in noise while the signals it needs go uncollected. + +**Adopting AI because competitors have.** Competitive mimicry is the antithesis of purpose-driven adoption. Microsoft rushed to deploy "Sydney" in Bing to compete with Google; the chatbot threatened users and caused a $100 billion market value loss at Google when Bard launched with a factual error in its first demonstration. Both companies allowed competitive pressure to override purpose. + +**Treating purpose as fixed and AI as its servant exclusively.** Purpose should remain stable, but the road to achieving it must be flexible. The formula: be firm with the purpose you want to achieve, but be agile with how AI can help you achieve that value. A retail company using AI-based recommender systems today might switch to LLM-powered chatbots tomorrow -- same purpose, different tool. + +**Separating the "AI question" from the "business question."** There is no separate AI strategy. There is only business strategy, informed by AI capabilities. Leaders who create dedicated "AI strategy" documents disconnected from business strategy have already made the fundamental error. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Purpose definition | Establish why the venture exists before considering whether AI is relevant; the purpose determines whether AI is a genuine enabler or a distraction | +| Validation | Question formulation | Translate purpose into specific, testable questions that data can answer; validate that the right data exists or can be collected | +| Early Traction | Leader-data scientist alignment | Establish the collaboration rhythm where leaders pose purpose-driven questions and data teams find answers; resist deferring | +| Growth | Purpose-scaled AI governance | As AI spreads across departments, ensure every deployment answers a question tied to organisational purpose, not departmental convenience | +| Scale | Purpose resilience under pressure | Maintain purpose alignment when competitive pressure, investor expectations, and technological hype create urgency to adopt AI indiscriminately | + +At the idea and validation stages, the discipline of asking purpose-driven questions prevents premature technology commitment. Many founders build AI-powered solutions before confirming that their target customers need AI at all. The purpose framework forces the question: is this a genuine problem that AI uniquely solves, or is AI a feature bolted on to attract investment? + +At growth and scale, the challenge shifts from formulating questions to institutionalising the practice. Every department deploying AI should begin with a purpose statement, not a technical specification. Regular cross-functional reviews should evaluate whether AI outputs address the questions that matter most to the organisation's mission. + +--- + +## Output Template + +**Target Audience: Leadership Team / Board** + +```markdown +# Purpose-Driven AI Assessment: [Project Name] +## Date: [Date] + +### Organisational Purpose Alignment +- Stated mission: [Mission statement] +- Core values relevant to this AI initiative: [List] +- Strategic priority this initiative serves: [Describe] + +### Question Audit +| Level | Question We Are Asking | Question We Should Be Asking | Gap | +|-------|----------------------|----------------------------|-----| +| Purpose | [Current] | [Revised] | [Gap description] | +| Strategic | [Current] | [Revised] | [Gap description] | +| Technical | [Current] | [Revised] | [Gap description] | + +### Data Readiness +- Data available to answer purpose-aligned questions: [Describe] +- Data gaps that must be filled: [List] +- Data currently collected that serves no strategic purpose: [List] + +### Competitive Pressure Assessment +- Are we pursuing this because of purpose or because of competitors? [Honest assessment] +- Would this initiative make sense if no competitor had adopted AI? [Yes/No + reasoning] + +### Purpose-Profit Reconciliation +- Expected financial return: [Realistic estimate] +- Timeline: [Honest projection, avoiding the immediate-ROI trap] +- How this investment creates sustainable value: [Narrative] + +### Recommended Questions for Data Science Team +1. [Purpose-driven question] +2. [Purpose-driven question] +3. [Purpose-driven question] +``` + +--- + +## Related Skills + +- **[AI Learning for Leaders](../../content/skills/ai-leadership/ai-learning-for-leaders.md)** -- Foundational AI knowledge enables leaders to formulate purpose-driven questions with enough technical fluency to evaluate answers. +- **[AI Communication Culture](../../content/skills/ai-leadership/ai-communication-culture.md)** -- Purpose-driven questions lose their value if leaders cannot communicate them effectively to technical teams across organisational silos. +- **[AI Vision and Strategy](../../content/skills/ai-leadership/ai-vision-and-strategy.md)** -- Purpose defines the "why"; vision translates it into a compelling "where we are going" that inspires the organisation. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- Covers the broader practice of leading with purpose; this skill applies that principle specifically to AI adoption decisions. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Provides the measurement framework for translating purpose into metrics that guide AI initiatives beyond pure financial returns. +- **[Strategic Questioning](../../content/skills/leadership/strategic-questioning.md)** -- The general practice of leading through questions rather than answers; this skill applies that discipline specifically to the AI context where questions matter more than technical expertise. diff --git a/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md b/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md deleted file mode 120000 index f1c51c7..0000000 --- a/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-stakeholder-balance.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md b/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md new file mode 100644 index 0000000..5a049b6 --- /dev/null +++ b/plugins/foreman/skills/ai-stakeholder-balance/SKILL.md @@ -0,0 +1,185 @@ +--- +name: "ai-stakeholder-balance" +description: "Guides leaders through the ethical and strategic complexities of balancing multiple stakeholder interests during AI adoption, from employees and customers to society at large. Provides frameworks for responsible AI deployment, stakeholder impact mapping, and moral decision-making when efficiency gains conflict with human welfare. Use when evaluating whether an AI deployment will harm employees or customers, weighing automation against workforce impact, facing pressure to prioritise shareholders over other stakeholders, designing an AI ethics governance structure, or confronting the societal consequences of algorithmic decision-making." +version: "1.0.0" +category: "ai-leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stakeholder-management + - ai-ethics + - responsible-ai + - risk-management + - governance + - societal-impact + - fairness + - ai-adoption +related_skills: + - ai-human-centered-approach + - ai-augmentation-not-automation + - ai-emotional-intelligence + - emotional-intelligence + - psychological-safety + - trust-equation + - leading-through-change +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Stakeholder Balance + +A scale, by definition, must have two sides. Most leaders deploying AI place efficiency on one side and load the other with nothing at all -- then marvel at how quickly things tip over. The promise of artificial intelligence is real: faster decisions, lower costs, sharper predictions. But efficiency is not a value-neutral concept. Efficiency *for whom* is the question that separates organisations that extract lasting value from AI from those that generate headlines about algorithmic bias, workforce revolts, and regulatory backlash. When Boston deployed an AI-optimised school bus scheduling system designed by two MIT graduates to trim a $100 million transportation budget, the algorithm dutifully reshuffled start times across hundreds of schools. It did not, however, consider that shifting elementary school start times to 7:15 a.m. would create a childcare gap that forced parents to change jobs or scramble for emergency arrangements. The city dropped the plan. The algorithm had optimised for cost. It had forgotten the humans. + +--- + +## The Framework + +### The Stakeholder Triad in AI Adoption + +AI adoption decisions radiate outward in concentric circles. At the centre sit the three stakeholder groups whose interests a leader must actively balance: employees, customers, and society. Most leaders acknowledge the first two and entirely forget the third. + +**Employees** are the most immediately affected. Surveys indicate that organisations expect automation to increase workforce capacity by 30 to 40 percent -- a statistic that, from the employee's perspective, reads as a 30 to 40 percent reduction in their perceived indispensability. Employees fear job loss, but they also fear something subtler: the erosion of agency, the sense that they have become appendages to an algorithm rather than professionals exercising judgment. + +**Customers** sit at the receiving end of AI-driven interactions. An algorithm that predicts palliative care eligibility using electronic health records may achieve impressive accuracy, but it cannot hold an end-of-life conversation. It cannot understand why a patient with a terminal diagnosis might still prefer aggressive treatment over statistical probability. Anand Avati and associates at Stanford developed precisely such an algorithm in 2018, and the fundamental limitation was not technical but human: AI regresses to the mean, approximating any individual's needs by referencing the average of a population. If a customer deviates from that average, the algorithm fails them. + +**Society** is the forgotten stakeholder. The AI decisions a company makes about hiring, pricing, surveillance, and data collection do not exist in a vacuum. Amazon's gender-biased recruiting algorithm, the UK's student grading algorithm that penalised students from poorer schools -- these were not just corporate embarrassments. They were societal harms with real victims who had no seat at the decision-making table. + +### Four Principles for Stakeholder-Balanced AI + +Research across multiple organisations and regulatory environments yields four principles that distinguish responsible AI adoption from the merely profitable kind. + +**Principle 1: AI is a tool, not a stakeholder manager.** The technology cannot go beyond treating a stakeholder as a data point. Supervised machine learning regresses observations to the mean and avoids outliers. Every individual stakeholder -- the atypical customer, the employee with unusual circumstances, the community with specific needs -- becomes an approximation. Leaders who delegate stakeholder management to AI are not managing stakeholders; they are managing averages. + +**Principle 2: Human intelligence imagines; AI intelligence extrapolates.** When an organisation adopts AI to promote innovation, it needs decisions based on thinking beyond what is already known. AI excels at extrapolation from existing data. It cannot imagine what does not yet exist. The ability to anticipate, take perspective, and envision what drives stakeholders at any given moment remains irreducibly human. + +**Principle 3: Financial motivation corrupts stakeholder judgment.** Research demonstrates that the more salient a financial incentive becomes, the more decision-makers will refrain from making the responsible choice. When Facebook was urged to address misinformation, its AI director reportedly slowed initiatives because they might harm the company's growth strategy. A heavily funded AI project creates its own gravitational pull toward financial justification at the expense of stakeholder welfare. + +**Principle 4: Identify all stakeholders -- especially the invisible ones.** The most dangerous omissions are the stakeholders who are not immediately visible: the parents affected by a school scheduling algorithm, the job applicants screened out by a biased hiring model, the communities whose data feeds a surveillance system. Leaders must think in terms of both direct and indirect, short-term and long-term stakeholder impact. + +### The Stakeholder Impact Matrix + +| Stakeholder Group | Direct Impact | Indirect Impact | Time Horizon | Typical Blind Spot | +|---|---|---|---|---| +| Employees | Job redesign, skill demands, algorithmic supervision | Work identity, psychological safety, bargaining power | Immediate to medium-term | Assuming silence equals acceptance | +| Customers | Service quality, personalisation, data privacy | Trust, brand loyalty, switching costs | Medium-term | Treating customers as data profiles | +| Shareholders | ROI on AI investment, competitive positioning | Long-term reputation risk, regulatory exposure | Short to medium-term | Conflating short-term returns with sustainable value | +| Society | Employment patterns, inequality, public services | Democratic processes, social cohesion, economic mobility | Long-term | Assuming societal impact is someone else's problem | +| Regulators | Compliance requirements, reporting obligations | Industry standards, public trust in technology | Medium to long-term | Treating regulation as an obstacle rather than a signal | + +### The Therac-25 Warning + +The Therac-25 case -- a computer-controlled radiation therapy machine used for cancer treatment -- remains one of the most sobering examples of what happens when human oversight is subordinated to algorithmic authority. Decisions that would have been made by licensed technicians were delegated to the machine. When patients received fatal overdoses of radiation, the technicians who should have intervened failed to override the software, even as patients cried out in pain. They had been instructed that it was "virtually impossible" for the system to overdose a patient. The mindset that "the computer knows best" led directly to the disengagement of the human technician -- and to deaths that competent human oversight would have prevented. + +The lesson extends far beyond healthcare. Every AI deployment carries a version of this risk: the gradual erosion of human judgment in favour of algorithmic authority, producing outcomes that no stakeholder -- not the technician, not the patient, not the institution -- actually wanted. + +--- + +## Prompts + +**Prompt 1 -- Stakeholder Impact Audit:** +> We are planning to deploy AI in [describe the specific AI application -- e.g., customer service automation, hiring screening, performance monitoring]. Map every stakeholder group that will be affected, both directly and indirectly, in the short term and long term. For each group, identify what they stand to gain, what they stand to lose, and where the most serious conflicts between stakeholder interests will emerge. Pay special attention to stakeholders who are not immediately visible. + +**Prompt 2 -- Ethical Risk Assessment:** +> Our AI adoption project involves [describe the project]. Conduct an ethical risk assessment: identify scenarios where the AI could produce outcomes that harm employees, customers, or society even while meeting its intended efficiency objectives. For each risk, assess severity, likelihood, and the strength of the human oversight mechanisms currently in place. Recommend specific governance structures to mitigate the top three risks. + +**Prompt 3 -- Stakeholder Communication Strategy:** +> We are deploying AI that will affect [describe affected groups]. Design a stakeholder communication plan that addresses each group's specific concerns, explains what the AI will and will not do, establishes transparency about data usage, and creates feedback mechanisms. The plan should include what to say when the honest answer is "we do not yet know the full impact." + +**Prompt 4 -- Society-as-Stakeholder Analysis:** +> Analyse the broader societal implications of our AI deployment in [describe context]. Consider effects on employment patterns in our region, potential for algorithmic bias across demographic groups, data privacy implications, and the precedent our approach sets for our industry. Recommend specific actions to mitigate societal harms while preserving the business value of the deployment. + +--- + +## Use Cases + +**Early-Traction Fintech Startup Automating Loan Decisions** + +A fintech startup with 30 employees deploys an AI model to automate small-business loan approvals. The model is fast, consistent, and demonstrably more profitable than the human underwriters it partially replaces. Six months in, a pattern emerges: the algorithm systematically disadvantages applicants from certain postal codes that correlate with lower-income, minority-heavy communities. The founders face a choice between a model that maximises approval accuracy (by their historical lending data) and one that serves the broader community equitably. Applying the stakeholder impact matrix, they map not just the direct impact on loan applicants but the indirect societal effect of perpetuating lending discrimination. The decision: retrain the model with fairness constraints, accept a modest reduction in predictive accuracy, and publish their fairness metrics publicly. The short-term cost is higher default rates. The medium-term gain is regulatory goodwill, brand trust, and a defensible position when lending regulations tighten -- which they invariably do. + +**Growth-Stage E-Commerce Company Introducing Algorithmic Performance Monitoring** + +A 200-person e-commerce company introduces an AI system to monitor warehouse worker productivity, adjusting individual targets based on historical performance data. Within weeks, absenteeism increases, error rates rise, and three senior packers -- the informal leaders of the warehouse floor -- resign. Exit interviews reveal a consistent theme: employees feel they are being treated like robots, monitored continuously, with targets that ratchet upward regardless of circumstance. The operations VP applies the principle of reflective procrastination -- the insight that allowing human variability, including bad days and creative pauses, produces better long-term results than algorithmic optimisation. The system is redesigned to account for individual working preferences, allow employee feedback on pace, and build in rest periods determined by workers rather than by the algorithm. Productivity data after the redesign shows reports are completed faster and with greater reliability than before -- achieved by respecting the human condition rather than overriding it. + +**Scale-Stage Healthcare Platform Deploying Predictive Diagnostics** + +A healthcare technology company deploys a predictive algorithm across 50 partner clinics to identify patients at risk of specific conditions. The algorithm performs well on aggregate metrics. A senior data scientist notices, however, that performance varies dramatically across demographic groups -- significantly worse for patients over 70 and for patients from non-English-speaking backgrounds, whose historical data is sparser. The company must decide whether to deploy broadly (maximising revenue) or restrict deployment to populations where the model is reliable (protecting patients). The stakeholder analysis reveals that broad deployment creates an invisible stakeholder harm: patients who receive inaccurate risk assessments may make medical decisions based on flawed predictions. The company restricts deployment, invests in collecting more diverse training data, and communicates the limitation transparently to partner clinics -- a decision that costs a quarter's revenue target but avoids the catastrophic trust destruction of a misdiagnosis scandal. + +--- + +## Anti-Patterns + +1. **Treating stakeholder impact as a post-deployment audit.** The time to assess stakeholder impact is before the algorithm is built, not after complaints arrive. Retrospective ethics reviews are reputation management, not responsible leadership. By the time harm is detected, the affected stakeholders have already paid the price. + +2. **Equating stakeholder management with customer management.** Leaders who define stakeholders as "employees and customers" and stop there are ignoring the constituency that will ultimately regulate, tax, and constrain their AI use: society. The Boston bus scheduling disaster was not a customer problem. It was a society problem that the decision-makers had not considered at all. + +3. **Delegating AI ethics to the technical team.** Ethics committees staffed exclusively with engineers and data scientists lack the philosophical, legal, and sociological perspectives needed to identify non-obvious harms. Hugging Face's model -- a dedicated, cross-disciplinary ethics group with a mandate to halt projects that reveal significant harm -- represents the standard that responsible organisations should aspire to. + +4. **Assuming algorithmic fairness is a mathematical property.** Fairness is a human value that requires human judgment. An algorithm can be optimised for statistical parity across groups while still producing outcomes that every reasonable person would consider unfair. The UK grading algorithm was statistically consistent. It was also morally indefensible. + +5. **Privileging speed over deliberation.** The pressure to deploy AI quickly -- to capture first-mover advantage, to justify investment, to satisfy board expectations -- creates a systematic bias against the careful stakeholder analysis that prevents harm. Speed is a business virtue. Recklessness disguised as speed is not. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Stakeholder identification | At the idea stage, the leader defines which stakeholders the AI is intended to serve -- and must resist the temptation to define that group too narrowly. The stakeholder map created now determines what harms will be invisible later. | +| Validation | Ethical hypothesis testing | Validation involves testing not just whether the AI works but whether it works fairly and without unintended harm across stakeholder groups. Prototype testing should include edge cases and underrepresented populations. | +| Early Traction | Governance infrastructure | The transition from prototype to production requires formal governance: who reviews algorithmic decisions, how stakeholders provide feedback, what triggers a human override. These structures are vastly easier to build now than to retrofit later. | +| Growth | Scaling without diluting oversight | Growth creates pressure to automate oversight itself. The challenge is maintaining human judgment in the loop as the volume of AI-driven decisions increases by orders of magnitude. This is the stage where stakeholder harm most often escapes detection. | +| Scale | Systemic and societal accountability | At scale, the organisation's AI decisions affect not just individual stakeholders but entire markets, communities, and public systems. The leader must engage with regulators, participate in industry standards, and accept that their AI's societal impact is a legitimate subject of public scrutiny. | + +--- + +## Output Template + +```markdown +# AI Stakeholder Impact Assessment + +## AI Application +- **Description:** [What the AI system does] +- **Primary business objective:** [Cost reduction / Revenue growth / Quality improvement / Speed] +- **Deployment scope:** [Number of people/transactions affected] + +## Stakeholder Map +| Stakeholder Group | Interest at Stake | Positive Impact | Negative Risk | Risk Severity (1-5) | Mitigation | +|---|---|---|---|---|---| +| [Group 1] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] | +| [Group 2] | [What they care about] | [How AI helps them] | [How AI could harm them] | [1-5] | [Specific action] | +| [Society] | [Broader implications] | [Potential benefits] | [Potential harms] | [1-5] | [Specific action] | + +## Conflict Analysis +| Conflict | Stakeholder A Wants | Stakeholder B Wants | Resolution Principle | Decision | +|---|---|---|---|---| +| [Describe tension] | [Their interest] | [Their interest] | [Which principle applies] | [How you resolve it] | + +## Governance Structure +- **Ethics review body:** [Composition and mandate] +- **Override authority:** [Who can halt an AI decision and under what conditions] +- **Feedback mechanism:** [How stakeholders report concerns] +- **Audit cadence:** [How often stakeholder impact is formally reviewed] + +## Commitments +- **We will:** [Specific promises to stakeholders] +- **We will not:** [Explicit boundaries on AI use] +- **We will disclose:** [What transparency looks like in practice] +``` + +--- + +## Related Skills + +- **[AI Human-Centered Approach](../../content/skills/ai-leadership/ai-human-centered-approach.md)** -- Stakeholder balance provides the strategic framework; the human-centred approach supplies the operational mindset for putting people before algorithms. +- **[AI Augmentation Not Automation](../../content/skills/ai-leadership/ai-augmentation-not-automation.md)** -- The choice between augmentation and automation is itself a stakeholder decision: automation prioritises shareholders while augmentation distributes value more broadly. +- **[AI Emotional Intelligence](../../content/skills/ai-leadership/ai-emotional-intelligence.md)** -- Balancing stakeholder interests requires the emotional intelligence to understand what different groups actually feel, not merely what they say in surveys. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Stakeholder trust is the currency that responsible AI governance either builds or destroys; the trust equation provides the diagnostic for understanding why. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- AI adoption is a specific instance of organisational change; stakeholder balance determines whether that change is experienced as progress or as imposition. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Stakeholder balance requires understanding the feedback loops between employee experience, customer satisfaction, and shareholder returns rather than treating each as independent. diff --git a/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md b/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md deleted file mode 120000 index 7a62abf..0000000 --- a/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/ai-leadership/ai-vision-and-strategy.md \ No newline at end of file diff --git a/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md b/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md new file mode 100644 index 0000000..267cfeb --- /dev/null +++ b/plugins/foreman/skills/ai-vision-and-strategy/SKILL.md @@ -0,0 +1,233 @@ +--- +name: "ai-vision-and-strategy" +description: "Guides leaders in developing and communicating a compelling AI vision that inspires rather than threatens, choosing augmentation over replacement as the strategic paradigm. Covers Perspective 1 (AI replaces humans) vs. Perspective 2 (AI augments humans), the tech-driving-tech trap, holistic communication, ethical foresight, and agile visionary leadership. Use when setting long-term AI strategy, when employees fear AI will eliminate their jobs, when AI adoption lacks a unifying narrative, when vision statements betray organisational identity, or when leaders need to translate AI potential into a story that builds commitment." +version: "1.0.0" +category: "ai-leadership" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ai-vision + - ai-strategy + - augmentation-vs-replacement + - holistic-communication + - visionary-leadership + - organisational-identity + - agile-leadership +related_skills: + - ai-learning-for-leaders + - ai-purpose-driven-questions + - ai-inclusive-collaboration + - ai-communication-culture + - ai-era-leadership + - scenario-planning + - kotter-change-model +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# AI Vision and Strategy + +Ninety percent of organisations have experimented with AI. Only 17 percent have succeeded in scaling it. The gap between experimentation and institutionalisation is not a technology problem -- it is a vision problem. One CEO, upon deciding to adopt AI, told his leadership team that business strategies of the past would no longer be relevant, that organisations needed to "start thinking like machines," and that AI engineers would become "the voices of the future." The meeting erupted in chaos. Managers asked in near-despair what this meant for their own jobs and their teams. The CEO had presented AI as an inevitability without a human story -- a technology-first vision that offered efficiency but no meaning. Contrast this with a logistics company leader who articulated precisely why AI mattered for inventory management, acknowledged what it could and could not do, set realistic targets, and told her workforce: "We're not using AI simply to use AI. It needs to help and make a difference, or else we will not use it." A year later, the adoption was expanding at every level. The difference between these two leaders was not technical knowledge. It was vision. + +--- + +## The Framework + +### The Two Perspectives + +The framework presents the entire AI leadership challenge as a choice between two fundamentally different perspectives: + +**Perspective 1: AI as Replacement** + +AI is an increasingly cheap way to replace people and achieve new levels of productivity and efficiency. Under this view, the primary focus is using AI to make the best use of data and, eventually, to delegate decision-making and thinking to the technology. Leaders who adopt this perspective are, ironically, making themselves redundant. If the logic holds -- if AI can think as well as humans but cheaper -- then leadership itself becomes dispensable. + +This pattern is called **tech-driving-tech transformation**: people valuing AI's computational prowess over human understanding and letting it lead. The Synthetic Party in Denmark, whose leader is an AI chatbot named Lars, and NetDragon Websoft, which appointed a robot named Tang Yu as CEO, embody this perspective taken to its logical extreme. + +**Perspective 2: AI as Augmentation** + +AI is a powerful tool to augment -- not replace -- human intelligence, unlocking innovation and creativity in workers. Under this view, investing in humans is the priority. Leaders take active charge of AI adoption to complement a human-centred strategy. This approach does not focus primarily on reducing costs; it requires significant investment in human resources to deploy AI in human-centred ways. + +The entire architecture of this framework argues for Perspective 2. The evidence supports it: AI cannot infer meaning, exercise moral reasoning, appreciate cultural nuance, generate genuinely novel ideas, or understand why humans are in business. Kate Crawford of Microsoft Research puts it plainly: "Most AI is neither artificial, nor intelligent." Vision is a uniquely human capacity, and the AI-savvy leader does not outsource it. + +### Why Vision Fails in AI Adoption + +The research identifies three specific reasons why leaders with otherwise strong visionary skills fail when it comes to AI: + +**1. The Bridge Problem.** Leaders can imagine an AI-enabled future but cannot see the bridge to get there. The technology shifts too rapidly. Building a bridge when you are uncertain where the other bank is -- or whether it will move -- creates paralysis. + +**2. The Expectations Trap.** Leaders project that AI will deliver immediate results, then are disappointed when the technology falls short or scaling proves difficult. This premature disappointment leads to abandonment. + +**3. The Silo Default.** Leaders announce an AI vision, then expect AI engineers to carry it forward. Without continued leadership involvement, AI adoption fractures into independent departmental projects that serve narrow interests rather than organisational goals. + +### Holistic Communication + +To overcome these failures, the framework prescribes **holistic communication** -- a visionary approach built on four principles: + +| Principle | Impact | +|-----------|--------| +| Improve your tech savviness | Helps explain AI's function and goal in your own words, making the business narrative relevant and meaningful to the workforce | +| Be authentic | Makes you persuasive because you know what you are talking about; enables genuine connection with your audience | +| Use the rhetoric of collaboration | Rallies everyone around the common goal of AI adoption as a shared endeavour | +| Show empathy | Gives employees confidence that AI adoption is not an end in itself but a means to an end, with full recognition of the workforce's interests | + +Holistic communication is what separates vision from announcement. A leader who merely declares "we are adopting AI" has made an announcement. A leader who explains why AI matters for the organisation's purpose, how it will change workflows, what it will not change about the company's identity, and how employees fit into the future -- that leader has communicated a vision. + +### Preserving Organisational Identity + +Research with collaborator Shane Schweitzer demonstrates a counterintuitive finding: AI vision statements that promise to transform the company into a technology company actually reduce employee commitment and customer loyalty. + +CEOs of major banks have stated: +- "We're clearly a technology company." (CEO, Bank of America) +- "We act less like a bank and more like a tech company." (CEO, DBS Bank) +- "In many ways, we see ourselves as a technology company with a banking license." (CEO, Citibank) + +Across several studies, the research found that such statements made employees and customers feel that banking was no longer central to the institution. Neither party could identify what the bank stood for -- besides wanting to be a technology company. As a result, neither employees nor customers were willing to commit to or trust the institution. + +The lesson: an AI-based vision must emphasise that the technology supports what the company already stands for. Bosch CEO Volkmar Denner modelled this correctly: "Ten years from now, scarcely any Bosch product will be conceivable without AI." The statement keeps Bosch products -- not AI -- at the centre of the vision. + +### Ethical Foresight + +Visionary AI leadership requires incorporating ethical considerations into the strategic narrative from the beginning, not as an afterthought. AI systems are frequently biased, often opaque, and increasingly subject to regulation. Leaders who ignore these dimensions in their vision will be caught unprepared when biases surface, when regulators intervene, or when stakeholders lose trust. + +Consider a health insurance example: a company deploying AI to predict risk profiles and set premiums must proactively invest in explainability techniques, transparency policies, and data governance. The leader who includes ethical considerations in the AI vision from the start builds credibility; the leader who addresses them only after a scandal has lost it. + +### Agile Vision + +Being visionary does not mean being rigid. AI adoption involves iteration and experimentation. Initial performance targets may prove unreasonable. Work routines may be disrupted before they are improved. New AI capabilities may emerge that render current approaches obsolete. + +The formula: provide a clear overarching goal while giving teams the freedom to pivot from unreasonable objectives. The logistics CEO he profiles exemplified this -- she baked agility into her core vision message, telling employees that AI adoption was not a plug-and-play process and that challenges should be anticipated and addressed collaboratively. + +--- + +## Prompts + +**Prompt 1 -- AI Vision Statement Development:** +> "Help me craft an AI vision for [describe organisation, its purpose, and its identity]. Using the holistic communication framework, the vision must: (1) emphasise that AI supports what the company already stands for, rather than transforming it into a tech company, (2) use the rhetoric of collaboration to frame AI as a shared endeavour, (3) show empathy for employee concerns about job displacement, (4) demonstrate tech savviness without pretending to technical expertise, and (5) preserve the organisation's core identity while articulating how AI enhances it." + +**Prompt 2 -- Perspective 1 vs. Perspective 2 Diagnostic:** +> "Analyse our current AI strategy and determine whether it follows Perspective 1 (AI as replacement for efficiency) or Perspective 2 (AI as augmentation of human capability). Our AI initiatives include [describe]. Employee sentiment about AI is [describe]. Leadership communication about AI has emphasised [describe]. If we are operating under Perspective 1, design a transition plan to Perspective 2 that reframes our AI narrative, adjusts our investment priorities, and rebuilds employee trust." + +**Prompt 3 -- Vision Credibility Assessment:** +> "Evaluate the credibility of our AI vision. Our stated vision is [describe]. Using the framework, assess whether: (1) the vision starts with the problem we are solving, not the technology we are buying, (2) it demonstrates informed decision-making rather than following trends, (3) it includes ethical considerations and regulatory foresight, (4) it signals agility rather than rigidity, and (5) it preserves organisational identity. Identify specific weaknesses and recommend revisions." + +**Prompt 4 -- Agile AI Strategy Design:** +> "Design an agile AI adoption strategy for [describe organisation and context]. The strategy must: (1) provide a clear overarching vision that inspires commitment, (2) build in mechanisms for adjusting targets based on real-world outcomes, (3) encourage teams to anticipate challenges rather than be surprised by them, (4) remain responsive to emerging AI developments (e.g., the sudden prominence of LLMs), and (5) balance ambition with realism so that employees feel challenged but not threatened." + +--- + +## Use Cases + +**Idea-Stage AI Startup Choosing Between Replacement and Augmentation** + +Two co-founders building an AI-powered writing assistant disagree on the product's fundamental positioning. One frames the product as replacing human copywriters (cheaper, faster, no benefits to pay). The other frames it as augmenting writers (handling first drafts, research summaries, and structural suggestions while humans provide voice, judgement, and creativity). The augmentation frame proves more compelling to early users, who resist tools that threaten their professional identity but embrace tools that make them more productive. It also proves more compelling to investors, who recognise that pure replacement products face commoditisation pressure as every LLM provider offers similar capabilities. The Perspective 2 vision differentiates the product by centring human capability rather than cost reduction. + +**Growth-Stage Financial Services Firm Whose Vision Alienated Employees** + +A mid-size bank, responding to competitive pressure from fintechs, declares itself a "technology company that happens to hold a banking license." Employee surveys reveal a sharp decline in engagement and loyalty. Customer research shows that clients prefer their banker -- not an analytics expert -- to manage their finances. Applying the research findings, the bank reframes its vision: AI will enhance the bank's ability to deliver personalised financial guidance, enabling relationship managers to serve clients with deeper insight and faster response times. The bank remains a bank. AI becomes the instrument, not the identity. Employee engagement recovers within two quarters, and client retention improves as relationship managers report feeling empowered rather than displaced. + +**Scale-Stage Logistics Company Embedding Agility into AI Vision** + +A global logistics firm with AI deployed across warehousing, routing, and demand forecasting faces a new challenge: the emergence of LLM-based tools that could transform how planners interact with data. The company's AI vision, written two years earlier, makes no mention of generative AI. Rather than rewriting the vision, the CEO invokes the agility principle embedded in the original statement: "Our commitment is to using AI to help our people plan better and serve customers faster. The specific tools will evolve; the commitment will not." Teams are given latitude to experiment with LLM-based interfaces while the overarching performance goals remain stable. The vision flexes without breaking because agility was built into its foundation from the start. + +--- + +## Anti-Patterns + +**Declaring the company a technology company.** The research demonstrates that AI vision statements framing traditional businesses as technology companies reduce both employee commitment and customer trust. The company's identity should remain intact; AI is the enabler, not the identity. + +**Presenting AI as inevitable and demanding compliance.** "Everything is changing; get on board" is not a vision. It is coercion wrapped in technological determinism. Employees who feel threatened rather than inspired will resist, quietly or otherwise. Vision must offer meaning, not just momentum. + +**Setting the vision and walking away.** Leaders who deliver an inspiring AI speech and then delegate execution to engineers have made the silo default error. AI vision requires continuous leadership involvement -- adjusting targets, celebrating progress, acknowledging failures, and maintaining the human narrative. + +**Promising immediate returns.** The expectations trap claims leaders who project that AI will deliver transformational results quickly. When the technology falls short -- as it inevitably does in early deployment -- disappointment leads to abandonment. Honest timelines and realistic targets build credibility. + +**Ignoring ethics until forced to confront them.** Bias, opacity, and regulatory risk are not edge cases. They are central features of AI deployment. Leaders who exclude ethical considerations from their vision will face them as crises rather than managing them as expected challenges. + +**Rigid long-term AI roadmaps.** A five-year AI roadmap written without agility provisions will be obsolete within months. The field moves too quickly for rigid planning. The agile vision principle -- clear goals, flexible methods -- is the only sustainable approach. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision as differentiator | Articulate how AI serves the venture's purpose in a way that attracts talent and investment; choose Perspective 2 from the start | +| Validation | Vision-reality alignment | Test whether the AI vision survives contact with real users and real data; adjust expectations based on evidence rather than hype | +| Early Traction | Vision communication at scale | Move beyond founder-to-team communication; ensure the AI vision is understood and embraced across a growing organisation | +| Growth | Vision preservation under competitive pressure | Resist the temptation to abandon purpose-aligned AI strategy in favour of copying competitors; maintain organisational identity | +| Scale | Institutional vision governance | Embed the AI vision into strategic planning, performance evaluation, and cultural practice so it outlasts any single leader | + +At the idea stage, the choice between Perspective 1 and Perspective 2 is foundational. Startups that build on the replacement paradigm attract talent that shares that worldview and build products that embody it. Changing the paradigm later requires rebuilding culture, product, and positioning simultaneously. + +At growth and scale, the challenge is maintaining vision coherence as the organisation encounters competitive pressure, technological disruption, and stakeholder fatigue. The logistics CEO's approach -- agility baked into the vision's architecture -- offers a model. The vision remains fixed on purpose while accommodating shifts in the technological landscape. + +--- + +## Output Template + +**Target Audience: Board / All-Hands** + +```markdown +# AI Vision and Strategy: [Organisation Name] +## Date: [Date] + +### Vision Statement +[A concise statement that emphasises augmentation, preserves identity, and inspires commitment] + +### Perspective Assessment +- Current paradigm: [Perspective 1 (Replacement) / Perspective 2 (Augmentation) / Mixed] +- Target paradigm: Perspective 2 -- AI augments human capability +- Transition steps required: [List if currently Perspective 1] + +### Organisational Identity Preservation +- Core identity elements that AI must not change: [List] +- Ways AI will strengthen these elements: [Describe] +- Risk of identity erosion: [Assess] + +### Holistic Communication Plan +| Audience | Key Message | Communication Channel | Cadence | +|----------|-----------|---------------------|---------| +| Employees | [Message] | [Channel] | [Frequency] | +| Customers | [Message] | [Channel] | [Frequency] | +| Investors/Board | [Message] | [Channel] | [Frequency] | +| Partners | [Message] | [Channel] | [Frequency] | + +### Ethical Foresight +- Known bias risks: [List] +- Regulatory landscape: [Summarise relevant regulations] +- Explainability investments: [Planned/Active] +- Proactive governance measures: [List] + +### Agility Architecture +- Fixed elements (will not change): [List -- purpose, values, identity] +- Flexible elements (will adapt): [List -- specific tools, timelines, methods] +- Review cadence for adjusting AI approach: [Frequency] +- Process for incorporating emerging AI capabilities: [Describe] + +### Success Metrics +| Metric | Baseline | 6-Month Target | 12-Month Target | +|--------|----------|---------------|-----------------| +| Employee AI adoption rate | [%] | [%] | [%] | +| Employee engagement score | [Score] | [Score] | [Score] | +| AI contribution to [business metric] | [Baseline] | [Target] | [Target] | +| Customer trust in AI-enabled services | [Score] | [Score] | [Score] | +``` + +--- + +## Related Skills + +- **[AI Learning for Leaders](../../content/skills/ai-leadership/ai-learning-for-leaders.md)** -- Tech savviness is one of the four pillars of holistic communication; leaders cannot articulate a credible AI vision without foundational knowledge. +- **[AI Purpose-Driven Questions](../../content/skills/ai-leadership/ai-purpose-driven-questions.md)** -- Purpose provides the foundation upon which vision is built; without clear purpose, vision becomes empty aspiration. +- **[AI Inclusive Collaboration](../../content/skills/ai-leadership/ai-inclusive-collaboration.md)** -- Vision requires collaboration rhetoric; inclusive collaboration ensures that the vision reflects diverse stakeholder perspectives. +- **[AI Communication Culture](../../content/skills/ai-leadership/ai-communication-culture.md)** -- The flat communication culture this skill builds is the infrastructure through which vision is communicated, tested, and refined. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Provides structured methods for anticipating multiple AI futures, supporting the agile vision approach prescribed. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- Kotter's eight-step framework for leading change maps directly onto the organisational transformation required by AI adoption. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- The daily habits of operating at strategic altitude are essential for translating AI vision into actionable organisational alignment. diff --git a/plugins/foreman/skills/ambidexterity/SKILL.md b/plugins/foreman/skills/ambidexterity/SKILL.md deleted file mode 120000 index 871cfd7..0000000 --- a/plugins/foreman/skills/ambidexterity/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/ambidexterity.md \ No newline at end of file diff --git a/plugins/foreman/skills/ambidexterity/SKILL.md b/plugins/foreman/skills/ambidexterity/SKILL.md new file mode 100644 index 0000000..ff3b0f6 --- /dev/null +++ b/plugins/foreman/skills/ambidexterity/SKILL.md @@ -0,0 +1,181 @@ +--- +name: "ambidexterity" +description: "Applies O'Reilly and Tushman's organizational ambidexterity framework to balance exploitation of existing business with exploration of new opportunities. Assesses resource allocation between core operations and innovation initiatives, designs structurally or contextually ambidextrous organizations, and evaluates innovation portfolios. Use when a company needs to protect its core revenue while pursuing new growth, launching separate innovation units, or diagnosing why exploratory initiatives are being starved by day-to-day operations." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - innovation + - organizational-design + - exploitation + - exploration + - dual-strategy +related_skills: + - blue-ocean-strategy + - disruptive-innovation + - kotter-change-model + - business-model-canvas +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Organizational Ambidexterity + +Consider what it means to be physically ambidextrous: the ability to write fluently with both hands, each performing distinct tasks without compromising the other. Most people cannot do it. Most organizations cannot do it either -- and the organizational version is far more consequential. Ambidexterity in a corporate context means simultaneously excelling at exploiting existing capabilities for current profit and exploring new opportunities for future growth. The concept, formalized by scholars Charles O'Reilly and Michael Tushman, addresses perhaps the deepest tension in business strategy: how to be disciplined and creative at the same time, in the same company, without one impulse strangling the other. + +The reason this matters is not abstract. The business landscape is littered with companies that mastered exploitation -- Kodak, Blockbuster, Nokia -- and failed catastrophically because they could not explore. Conversely, companies that explore without exploiting burn cash with no viable business model underneath. Ambidexterity is the structural answer to this dilemma. + +--- + +## The Framework + +### Exploitation vs. Exploration + +The terms originate from James March's seminal 1991 paper and form the conceptual backbone of ambidexterity theory. + +**Exploitation** is the refinement, efficiency, and optimization of existing products, processes, and customers. It produces near-term revenue, measurable results, and incremental improvement. It feels safe because the feedback loops are tight. + +**Exploration** is the search for new markets, technologies, and business models. It produces long-term growth potential but involves uncertainty, failure, and delayed returns. It feels risky because the feedback loops are loose and ambiguous. + +The challenge: exploitation crowds out exploration. Existing businesses generate revenue, attract executive attention, and demand resource allocation. Innovation labs starve. R&D projects get cut when quarterly numbers disappoint. The urgent devours the important. + +### Three Models of Ambidexterity + +Organizations have attempted to solve this tension through three structural approaches: + +**1. Structural Ambidexterity** +Separate exploration and exploitation into distinct business units with different cultures, metrics, incentives, and leadership -- but integrate them at the senior executive level. + +| Dimension | Exploitation Unit | Exploration Unit | +|-----------|------------------|-----------------| +| Culture | Efficiency, discipline, process | Experimentation, risk-taking, speed | +| Metrics | Revenue, margin, market share | Learning velocity, option value, discovery milestones | +| Time Horizon | Quarterly / annual | 2-5 year bets | +| Leadership Style | Operational excellence | Entrepreneurial vision | +| Risk Tolerance | Low | High | + +The critical design principle: the units must be structurally separate but strategically integrated. The CEO (or a senior leadership team) holds the integration role, ensuring exploration units can access the resources and distribution of the exploitation side without being consumed by its culture. + +**2. Contextual Ambidexterity** +Rather than separating units, build an organizational context in which individuals can judge for themselves when to exploit and when to explore. This requires a culture that simultaneously values discipline and entrepreneurship, stretch and support. + +Contextual ambidexterity is harder to implement but avoids the silos and coordination costs of structural separation. It works best in knowledge-intensive firms where individual judgment is paramount. + +**3. Sequential Ambidexterity** +Alternate between periods of exploitation and exploration. This is the least sophisticated approach and typically the least effective, because timing the switches is difficult and organizational momentum resists the transition. + +### Why Structural Ambidexterity Dominates + +O'Reilly and Tushman's research demonstrates that structurally ambidextrous organizations outperform both purely exploitative firms and those attempting contextual ambidexterity. The reason is architectural: human organizations struggle to hold contradictory cultures simultaneously. Separation with senior integration resolves the contradiction without eliminating either capability. + +### The Integration Challenge + +The hardest part is not creating separate units -- it is integrating them. Common failure modes: + +- The exploration unit is treated as a "skunkworks" curiosity project rather than a strategic priority +- The exploitation unit resents resource allocation to an unproven venture +- No mechanism exists to graduate successful explorations into the mainstream business +- Senior leadership pays lip service to exploration but allocates attention disproportionately to exploitation + +--- + +## Prompts + +**Prompt 1 -- Exploitation/Exploration Audit:** +> Assess my company's current balance between exploitation and exploration. My company is [describe: sector, stage, size, main products/services, recent strategic initiatives]. Estimate what percentage of our resources (budget, headcount, leadership attention) goes to exploitation vs. exploration. Based on our stage and competitive environment, what should the balance be? Identify the three highest-priority adjustments. + +**Prompt 2 -- Structural Ambidexterity Design:** +> Help me design a structurally ambidextrous organization. My current company structure is [describe org chart, key teams, reporting lines]. I want to create a dedicated exploration unit focused on [describe the opportunity or technology]. Define the unit's mandate, reporting structure, culture, metrics, team composition, and budget. Critically, specify how this unit integrates with the core business -- what resources does it draw from, and how do successful innovations graduate into the mainstream? + +**Prompt 3 -- Innovation Portfolio Assessment:** +> Evaluate my company's innovation portfolio through the ambidexterity lens. Here are our current projects and initiatives: [list them]. Classify each as exploitation (core improvement), adjacent exploration (extending into related domains), or transformative exploration (pursuing fundamentally new opportunities). Recommend how to rebalance the portfolio for long-term health, considering our stage ([stage]) and competitive threats. + +--- + +## Use Cases + +**Growth-Stage B2B SaaS Company Launching an AI Product Line** +A $15M ARR B2B SaaS company sees AI-powered features as the future of its category but cannot disrupt its current product -- which generates all revenue -- to build them. The founder applies structural ambidexterity: a dedicated AI team of six engineers operates with its own roadmap, metrics (user engagement with AI features, time-to-value), and sprint cadence. The team sits physically adjacent to the core engineering group but reports directly to the CTO rather than through the VP of Engineering who manages the core product. Integration happens at the weekly leadership meeting, where the AI team presents findings and the core team identifies integration opportunities. After nine months, two AI features are ready for general availability and move into the core product with dedicated support from both teams. + +**Scale-Stage Retail Company Exploring Direct-to-Consumer** +A traditional B2B2C consumer goods company at scale sells through retail partners but faces margin pressure and data blindness. The CEO establishes a DTC exploration unit with its own P&L, brand identity, and digital marketing team. The unit leverages the parent company's supply chain and manufacturing (exploitation assets) but operates with startup-like speed and different KPIs -- customer acquisition cost, lifetime value, and first-party data volume rather than wholesale revenue. The integration mechanism: a quarterly "transfer committee" evaluates which DTC learnings should flow back into the wholesale business and which wholesale capabilities should be made available to the DTC unit. + +**Early-Traction Marketplace Balancing Supply Growth with Product Innovation** +A two-sided marketplace with 500 active suppliers must simultaneously grow its supply base (exploitation) and develop a fundamentally new matching algorithm (exploration). With only 30 employees, structural separation is impractical. The founder implements contextual ambidexterity: engineers spend 80% of their time on core platform development and 20% on experimental projects. The key enabler is a culture that celebrates both operational wins and learning from failed experiments. Weekly demos alternate between "what we shipped" and "what we learned." + +--- + +## Anti-Patterns + +1. **Creating an innovation lab with no integration pathway.** Many companies establish innovation teams as trophies -- visible proof of forward thinking -- without any mechanism to bring innovations into the core business. These labs produce demos and prototypes that never reach customers, and their best people eventually leave out of frustration. + +2. **Starving exploration when exploitation underperforms.** The instinct during a revenue shortfall is to redirect all resources to the core business. This is precisely the moment when the exploitative side is demonstrating its limitations and the exploratory side is most needed. Cutting exploration during downturns is strategically rational in the short term and catastrophic in the long term. + +3. **Applying exploitation metrics to exploration units.** Measuring an exploration team by revenue or margin in its first year is like judging a seed by the weight of fruit it has not yet produced. Exploration requires different metrics: speed of learning, quality of hypotheses tested, option value created. + +4. **Assuming ambidexterity means equal allocation.** The right balance between exploitation and exploration is not 50/50. It depends on industry velocity, competitive position, and company stage. A company in a stable industry with strong market position might allocate 85/15. A company facing technological disruption might need 60/40. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Contextual ambidexterity | Too small for structural separation. Build a culture that values both execution and experimentation. Use time-boxing (e.g., 80/20 allocation) to protect exploration from the gravitational pull of daily operations. | +| Growth | Structural ambidexterity emerges | Large enough to create dedicated exploration units. This is the critical stage for establishing ambidextrous architecture before the exploitation culture calcifies. Design integration mechanisms early. | +| Scale | Institutional ambidexterity | Multiple exploration units may coexist, each targeting different horizons. The CEO's primary strategic role becomes portfolio management across exploitation and exploration initiatives. Board oversight should include innovation pipeline reviews alongside financial performance. | + +--- + +## Output Template + +```markdown +# Ambidexterity Assessment + +**Company:** [Name] +**Stage:** [Current stage] +**Date:** [Date] + +## Current State + +| Dimension | Exploitation | Exploration | Ideal Ratio | +|-----------|-------------|-------------|-------------| +| Budget allocation | [%] | [%] | [Target %] | +| Headcount | [%] | [%] | [Target %] | +| Leadership attention | [%] | [%] | [Target %] | + +## Innovation Portfolio + +| Initiative | Type (Exploit/Adjacent/Transform) | Stage | Metrics | Resource Level | +|-----------|-----------------------------------|-------|---------|----------------| +| [Initiative 1] | [Type] | [Stage] | [KPIs] | [Adequate/Under/Over] | +| [Initiative 2] | [Type] | [Stage] | [KPIs] | [Adequate/Under/Over] | + +## Recommended Structure +- **Model:** [Structural / Contextual / Hybrid] +- **Exploration Unit Mandate:** [Description] +- **Integration Mechanism:** [How exploration connects to core] +- **Graduation Criteria:** [When exploration moves to core] + +## Priority Actions +1. [Action with owner and timeline] +2. [Action with owner and timeline] +3. [Action with owner and timeline] +``` + +--- + +## Related Skills + +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Christensen's disruption theory explains why exploitation alone fails; ambidexterity is the organizational architecture that resolves the innovator's dilemma. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Exploration units often pursue blue ocean opportunities, making ambidexterity the structural enabler and blue ocean the strategic direction. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- Transitioning from a purely exploitative organization to an ambidextrous one is a change management challenge that benefits from Kotter's eight-step implementation sequence. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- Exploration units benefit from running their own canvas separate from the core business, making assumptions visible and testable before committing resources. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Exploitation units apply Kaizen for continuous refinement while exploration units may use BPR-style radical redesign, mirroring the dual logic of ambidexterity. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- Provides the leadership practices needed to sustain both exploitation and exploration cultures simultaneously within one organization. diff --git a/plugins/foreman/skills/appreciative-inquiry/SKILL.md b/plugins/foreman/skills/appreciative-inquiry/SKILL.md deleted file mode 120000 index 1e04b03..0000000 --- a/plugins/foreman/skills/appreciative-inquiry/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/appreciative-inquiry.md \ No newline at end of file diff --git a/plugins/foreman/skills/appreciative-inquiry/SKILL.md b/plugins/foreman/skills/appreciative-inquiry/SKILL.md new file mode 100644 index 0000000..4fb74a5 --- /dev/null +++ b/plugins/foreman/skills/appreciative-inquiry/SKILL.md @@ -0,0 +1,226 @@ +--- +name: "appreciative-inquiry" +description: "Guides strengths-based organizational change using Cooperrider's + Appreciative Inquiry 4D cycle: Discovery, Dream, Design, and Delivery. + Surfaces peak experiences and positive patterns to amplify what works rather + than fixing what is broken. Use when addressing team morale, redesigning + processes, integrating acquisitions, reframing organizational challenges, or + running culture transformation initiatives where traditional deficit-based + problem-solving has stalled." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - organisational-development + - change-management + - strengths-based + - strategy + - innovation +related_skills: + - organisational-culture + - kaizen-bpr + - grow-model +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Appreciative Inquiry + +Stop fixing problems. The orthodox approach to organisational change -- diagnose what is broken, analyse root causes, prescribe solutions -- carries an unexamined assumption: that progress comes from eliminating deficits. David Cooperrider, working at Case Western Reserve University in the 1980s, proposed something radical. What if the fastest path to transformation is not fixing weaknesses but systematically amplifying strengths? What if the questions you ask determine the reality you find -- and organisations that ask "what is wrong?" get very good at cataloguing dysfunction, while organisations that ask "what works brilliantly, and how do we get more of it?" generate energy, alignment, and change that deficit-based approaches rarely achieve? + +This is not positive thinking. Appreciative Inquiry (AI) is a structured methodology backed by four decades of organisational research. It does not deny problems; it reframes the unit of analysis. Rather than treating the organisation as a machine with broken parts, AI treats it as a living system whose best moments contain the DNA of its future. The shift is neither naive nor cosmetic -- it is epistemological. + +--- + +## The Framework + +### The Core Principle: The Constructionist Premise + +Appreciative Inquiry rests on a foundational claim: organisations move in the direction of the questions they ask. Questions are not neutral instruments of discovery; they are interventions that shape what people notice, discuss, and ultimately create. An organisation that habitually asks "why did we fail?" develops sophisticated failure narratives. An organisation that asks "when did we succeed against the odds, and what made that possible?" develops actionable success patterns. + +This is not a rejection of critical analysis. It is a recognition that the inquiry itself is generative -- it creates the conditions for the reality it investigates. + +### The 4D Cycle + +Appreciative Inquiry unfolds through four phases, each building on the previous one: + +#### Discovery: "What Gives Life?" + +The first phase maps the organisation's positive core -- the strengths, peak experiences, best practices, and moments of excellence that already exist. This is accomplished through structured interviews in which every member of the organisation (or a representative sample) answers questions designed to surface what works. + +**Key Discovery questions:** +- Describe a peak experience in this organisation -- a time when you felt most engaged, effective, and proud. What made it possible? +- What do you value most about this organisation? About your work? About your colleagues? +- Without being modest, what do you contribute that makes this organisation stronger? +- What is the core factor that gives life to this organisation -- the thing without which it would cease to exist? + +**Discovery outputs:** +- A collection of stories that embody the organisation's strengths +- Identification of recurring themes and positive patterns +- An inventory of capabilities, assets, and conditions that produce excellence + +The discipline of Discovery is rigorous. It is not a feel-good exercise or a brainstorming session. It requires structured interviewing, systematic theme extraction, and evidence-based pattern recognition. + +#### Dream: "What Might Be?" + +Using the positive core identified in Discovery, the Dream phase envisions what the organisation could become if its strengths were amplified and its best moments became the norm rather than the exception. + +**Key Dream activities:** +- Provocative propositions: bold statements of aspiration grounded in demonstrated capability ("We are an organisation where every customer interaction produces a story worth telling" -- based on evidence from Discovery that this already happens sometimes) +- Collective visioning exercises that translate individual peak experiences into organisational possibilities +- Mapping the gap between current reality and the envisioned future, framed not as deficit but as potential + +**Dream outputs:** +- A shared vision statement grounded in demonstrated strengths +- Provocative propositions for each strategic domain +- Energy and alignment around a future state that feels achievable because it is extrapolated from existing excellence + +#### Design: "What Should Be?" + +The Design phase translates the Dream into concrete organisational architecture: processes, structures, roles, systems, and strategies that would enable the envisioned future. + +**Key Design activities:** +- Social architecture design: what structures, processes, and norms would make the Dream the default operating mode? +- Identification of enabling conditions: what must be true for the organisation's best moments to occur reliably, not sporadically? +- Prototype development: what small-scale experiments can test elements of the new design? + +**Design outputs:** +- Specific structural and process changes aligned with the Dream +- Pilot programmes and experiments +- Accountability frameworks for implementation + +#### Delivery (or Destiny): "What Will Be?" + +The final phase translates Design into action. It focuses on implementation, experimentation, and continuous adaptation. Unlike traditional change management, which follows a plan, Delivery in Appreciative Inquiry is emergent -- it learns and adjusts as the organisation experiments with new ways of operating. + +**Key Delivery activities:** +- Launch pilot programmes designed in the previous phase +- Establish feedback loops to capture learning +- Celebrate and publicise early successes (reinforcing the positive core) +- Adjust design elements based on real-world results + +**Delivery outputs:** +- Implemented changes with measurable outcomes +- New stories of success that feed back into the Discovery phase, creating a self-reinforcing cycle +- An organisational capability for strengths-based change that outlasts any single initiative + +### The 4D Cycle as a Continuous Loop + +``` + Discovery ──────► Dream + ▲ │ + │ ▼ + Delivery ◄────── Design +``` + +The cycle is not a one-time intervention but a repeatable methodology. Each Delivery phase generates new stories and data that feed the next Discovery phase, creating an upward spiral of organisational capability. + +--- + +## Prompts + +**Prompt 1 -- Strengths-Based Diagnostic:** +> Instead of analysing what is wrong with my company, help me conduct an Appreciative Inquiry Discovery phase. I will describe our best moments, peak customer experiences, and times when the team performed at its highest level: [describe 3-5 peak experiences]. Extract the recurring themes, underlying conditions, and core strengths that made those moments possible. Then identify how those strengths could be systematically amplified. + +**Prompt 2 -- Provocative Proposition Development:** +> Based on the following organisational strengths and peak experiences: [describe them], help me craft 5 provocative propositions for my company -- bold aspirational statements about what we could become, grounded in evidence of what we have already demonstrated. Each proposition should be specific enough to guide action and ambitious enough to generate energy. + +**Prompt 3 -- 4D Cycle Planning:** +> I want to run a full Appreciative Inquiry process with my team of [size] over [timeframe]. Design the complete 4D cycle: specific questions for the Discovery phase interviews, a facilitation plan for the Dream phase workshop, a Design phase structure for translating vision into architecture, and a Delivery phase with pilot experiments and feedback loops. Context: [describe your company, stage, and the strategic challenge you are addressing]. + +**Prompt 4 -- Reframing a Problem as an Inquiry:** +> My company is facing this challenge: [describe the problem]. Help me reframe it using the Appreciative Inquiry approach. Instead of asking "why is this broken?", construct a set of affirmative questions that redirect attention toward the positive core. Then outline a Discovery process that would surface actionable strengths related to this challenge. + +--- + +## Use Cases + +**Early-Traction Startup Struggling with Team Morale** +A 20-person startup has been through a difficult pivot. Morale is low, and the conventional response -- an all-hands where leadership acknowledges problems and presents a recovery plan -- risks reinforcing the deficit narrative. Instead, the CEO runs a compressed Appreciative Inquiry cycle. Discovery: each team member interviews a colleague about their peak experience at the company and what they value most. Dream: the team collectively envisions what the company looks like when those peak moments are the norm. Design: three concrete changes emerge -- restructured sprint planning based on the team's best sprint ever, a weekly "wins" ritual modelled on the team's most energising celebration, and a customer feedback loop inspired by the product's most successful launch. The process takes two weeks and produces measurable morale and productivity improvements within a month. + +**Growth-Stage Company Redesigning Customer Success** +A 150-person SaaS company faces rising churn. The instinct is to analyse churned accounts and fix the failure patterns. Appreciative Inquiry inverts the analysis: the customer success team conducts Discovery interviews with the company's longest-tenured and highest-NPS accounts, extracting what made those relationships exceptional. Common themes emerge -- proactive quarterly business reviews, a dedicated technical advocate, and early involvement in product roadmap discussions. These themes become the Design for a new customer success model applied to all accounts, not just the top tier. Churn decreases 18% in two quarters. + +**Scale-Stage Company Integrating an Acquisition** +A 600-person company acquires a 100-person competitor. Rather than imposing the acquirer's processes on the target, leadership conducts a joint Appreciative Inquiry across both organisations. Discovery surfaces what each company does best. Dream envisions a combined entity that amplifies both organisations' strengths. Design produces an integration plan that preserves the acquired company's best practices (agile product development, close customer relationships) while extending the acquirer's strengths (enterprise sales, compliance infrastructure). Employee retention during the integration exceeds industry benchmarks by 40%. + +--- + +## Anti-Patterns + +1. **Appreciative Whitewashing.** Using the framework to suppress legitimate criticism or silence dissent. "Focus on the positive" is not a mandate to ignore serious dysfunction. AI does not deny problems -- it approaches them through a different lens. If employees are burning out, the question is not "what do you love about working here?" but "when have you felt most energised and supported, and what conditions made that possible?" + +2. **Skipping Discovery.** Jumping to Dream without the disciplined interview process that surfaces genuine strengths. Without rigorous Discovery, the Dream phase produces fantasies untethered from organisational reality -- aspirational statements that inspire no one because they connect to nothing that already exists. + +3. **Treating AI as a Workshop, Not a Methodology.** Running a single Appreciative Inquiry offsite and expecting lasting change. The 4D cycle is designed to be continuous. A one-off workshop produces enthusiasm that dissipates within weeks unless the Design and Delivery phases follow through. + +4. **Ignoring Structural Issues.** Appreciative Inquiry is powerful for cultural and strategic challenges but insufficient for addressing structural problems -- a toxic manager, a fundamentally flawed business model, a compliance violation. Strengths-based inquiry complements but does not replace structural intervention. + +5. **Leader-Driven Discovery.** Conducting the Discovery phase by asking only leadership about peak experiences. AI is deliberately democratic -- its power comes from surfacing perspectives and stories from every level of the organisation. Leadership-only Discovery produces a self-congratulatory narrative, not an accurate portrait of the positive core. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Team energy and direction | Small teams benefit from compressed AI cycles that surface shared values and peak experiences, establishing a strengths-based culture before deficit-based habits calcify. | +| Growth | Scaling what works | Growth-stage companies have proven strengths but risk losing them during rapid scaling. AI systematically identifies and codifies what works so it can be replicated across new teams and geographies. | +| Scale | Organisational transformation | At scale, AI provides an alternative to top-down change management. Large-scale AI summits (involving hundreds of participants) generate alignment and energy that directive approaches cannot match. | + +--- + +## Output Template + +```markdown +# Appreciative Inquiry: [Challenge/Opportunity] + +## Discovery Phase Summary +### Peak Experience Themes +1. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] +2. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] +3. [Theme] -- Frequency: [X/Y interviews] -- Example: [Brief story] + +### Positive Core Inventory +- **Strengths:** [List organisational strengths surfaced] +- **Conditions for excellence:** [What must be true for peak performance] +- **Untapped assets:** [Capabilities present but underutilised] + +## Dream Phase: Provocative Propositions +1. "[Bold aspirational statement grounded in Discovery evidence]" +2. "[Bold aspirational statement grounded in Discovery evidence]" +3. "[Bold aspirational statement grounded in Discovery evidence]" + +## Design Phase: Enabling Architecture +| Design Element | Current State | Desired State | Change Required | +|---------------|---------------|---------------|-----------------| +| [Process/Structure] | [Now] | [Future] | [Specific change] | + +## Delivery Phase: Pilot Experiments +| Experiment | Owner | Timeline | Success Metric | +|-----------|-------|----------|----------------| +| [Pilot 1] | [Name] | [Dates] | [How measured] | +| [Pilot 2] | [Name] | [Dates] | [How measured] | + +## Feedback Loop +- Review cadence: [Weekly/Bi-weekly] +- Learning capture: [Method] +- Cycle refresh: [When to re-enter Discovery] +``` + +--- + +## Related Skills + +- **[Organisational Culture](../../content/skills/frameworks/organisational-culture.md)** -- Appreciative Inquiry operates on Schein's Layer 2 (espoused values) and Layer 3 (basic assumptions), shifting both by reframing the questions the organisation asks about itself. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Both frameworks share a commitment to continuous improvement but from opposite starting points: Kaizen eliminates waste while AI amplifies strengths, making them a complete improvement methodology when combined. +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- GROW's Reality and Options phases parallel AI's Discovery and Dream phases at the individual coaching level, providing a structurally complementary one-on-one tool. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- Kotter provides the sequential change management structure while AI provides the strengths-based energy and engagement that sustain momentum through Kotter's eight steps. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- The Discovery phase requires honest sharing of peak experiences, which only occurs when Edmondson's psychological safety conditions are in place. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's belief that capability develops through effort aligns with AI's assumption that an organisation's best moments contain the DNA for its future growth. diff --git a/plugins/foreman/skills/art-of-war/SKILL.md b/plugins/foreman/skills/art-of-war/SKILL.md deleted file mode 120000 index 841ebcc..0000000 --- a/plugins/foreman/skills/art-of-war/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/art-of-war.md \ No newline at end of file diff --git a/plugins/foreman/skills/art-of-war/SKILL.md b/plugins/foreman/skills/art-of-war/SKILL.md new file mode 100644 index 0000000..bcf3a67 --- /dev/null +++ b/plugins/foreman/skills/art-of-war/SKILL.md @@ -0,0 +1,210 @@ +--- +name: "art-of-war" +description: "Applies Sun Tzu's strategic principles to competitive business + situations, covering self-knowledge and competitor intelligence, winning + without direct confrontation, speed and timing, terrain analysis, and + strategic positioning. Use when assessing competitive landscapes, developing + market entry strategies, evaluating when to fight or avoid competitors, + conducting competitive intelligence audits, or designing stealth positioning + for startups facing well-resourced incumbents." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - competitive-strategy + - leadership + - positioning + - tactical-advantage + - decision-making +related_skills: + - porters-five-forces + - blue-ocean-strategy + - scenario-planning + - swot-pest-analysis +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Sun Tzu's Art of War + +Written approximately 2,500 years ago by a Chinese military strategist whose very existence some scholars dispute, *The Art of War* remains one of the most frequently purchased business books on Amazon. It sits on the bookshelves of Fortune 500 CEOs, Silicon Valley founders, and Wall Street traders with the same stubborn persistence as it sat in the libraries of Napoleon, Mao Zedong, and General Douglas MacArthur. This longevity is not nostalgia or affectation. Sun Tzu articulated principles of competitive strategy -- positioning, information asymmetry, resource allocation, the primacy of winning without fighting -- that predate Michael Porter by two millennia but remain structurally identical to the frameworks taught in modern business schools. The language is military; the logic is universal. + +--- + +## The Framework + +Sun Tzu's treatise spans thirteen chapters, but its strategic wisdom distills into several core principles that map directly onto entrepreneurial competition. + +### Principle 1: Know Yourself and Know Your Enemy + +> "If you know the enemy and know yourself, you need not fear the result of a hundred battles." + +This is Sun Tzu's most cited passage, and it is frequently reduced to a platitude. The operational meaning is precise: competitive advantage flows from superior information. Companies that understand their own capabilities honestly AND understand their competitors' capabilities accurately will outperform those with blind spots in either direction. + +**The Knowledge Matrix:** + +| | Know Yourself | Do Not Know Yourself | +|--|--------------|---------------------| +| **Know Enemy** | Victory in every engagement -- strategic clarity enables decisive action | Alternating wins and losses -- you exploit competitor weakness but are surprised by your own | +| **Do Not Know Enemy** | Stalemate or defensive survival -- internal strength without external awareness leads to missed opportunities | Certain defeat -- operating blind on both dimensions | + +Most startups occupy the lower-left quadrant: they know their product intimately but have only superficial knowledge of their competitive landscape. Worse, many deliberately avoid competitive analysis, treating it as a distraction from customer focus. Sun Tzu would find this reckless. + +### Principle 2: Win Without Fighting + +> "The supreme art of war is to subdue the enemy without fighting." + +Translated into business: the best competitive strategy is one that makes direct confrontation unnecessary. This principle aligns with Blue Ocean Strategy (creating uncontested markets) and with Porter's concept of strategic positioning (choosing a unique position that competitors cannot easily replicate without abandoning their own strategy). + +For startups, winning without fighting means: +- Choosing market segments where incumbents have structural reasons not to compete +- Building defensible advantages (network effects, data moats, regulatory expertise) rather than competing on features alone +- Converting potential competitors into partners or acquirers before conflict escalates + +### Principle 3: The Primacy of Speed and Timing + +> "Speed is the essence of war." + +Sun Tzu repeatedly emphasizes that a smaller, faster force defeats a larger, slower one when timing and positioning are right. In startup terms: execution speed is a competitive advantage independent of resources. The startup that ships in weeks what the incumbent takes months to build captures market learning faster, iterates faster, and compounds advantage over time. + +Speed, however, is not haste. Sun Tzu distinguishes between swift execution (desirable) and impulsive action (disastrous). The difference is preparation: the general who has thoroughly planned can act swiftly when the moment arrives. + +### Principle 4: Terrain and Positioning + +> "The clever combatant imposes his will on the enemy, but does not allow the enemy's will to be imposed on him." + +Sun Tzu devotes extensive analysis to terrain -- the physical environment in which battles are fought. In business, terrain is the competitive landscape: market structure, distribution channels, regulatory environment, customer buying behavior, technology platforms. The strategist who chooses favorable terrain -- and forces competitors to fight on unfavorable terrain -- gains structural advantage. + +Favorable terrain for startups includes: +- Markets with high customer pain and low incumbent attention +- Technology platforms where the startup has native expertise and incumbents must learn +- Regulatory environments that create barriers benefiting the startup's approach +- Customer segments too small for large competitors to justify serving + +### Principle 5: Deception and Unpredictability + +> "All warfare is based on deception." + +Sun Tzu advocates appearing weak when strong, appearing strong when weak, appearing close when far, and appearing far when close. In business, this translates to competitive stealth: not telegraphing strategic moves, maintaining optionality about direction, and avoiding the competitive signaling that draws premature attention. + +Stealth is particularly valuable for startups: operating under the radar of incumbents provides time to build capability before facing a competitive response. The startup that announces its grand vision before achieving product-market fit invites competitive preemption without any defensive position. + +### Principle 6: The Cost of Prolonged Conflict + +> "There is no instance of a country having benefited from prolonged warfare." + +Extended competitive battles -- price wars, feature wars, marketing wars -- drain resources and destroy value for all participants. Sun Tzu counsels decisive action over attrition. For startups with limited capital, this is existential guidance: avoid protracted fights with better-funded competitors. Either win quickly through superior positioning or redirect to terrain where the fight is avoidable. + +--- + +## Prompts + +**Prompt 1 -- Competitive Intelligence Map:** +> Apply Sun Tzu's "know yourself, know your enemy" framework to my competitive situation. My company is [describe: product, market, stage, key strengths]. My known competitors are [list competitors]. For each competitor, assess: What are their strengths? Weaknesses? Strategic priorities? Where are they investing? For my own company, assess: What are our honest strengths and blind spots? Where does our self-knowledge have gaps? Build a knowledge matrix showing where we have information advantage and where we are operating blind. + +**Prompt 2 -- Win Without Fighting Strategy:** +> Help me develop a strategy to "win without fighting" in my market. My company competes in [describe market]. Rather than direct confrontation with [competitors], identify: (1) Market segments where incumbents have structural reasons not to compete, (2) Defensible positions we can build that make competition irrelevant, (3) Potential competitor-to-partner conversions, (4) Positioning moves that change the terms of competition. Frame the output as a strategic positioning plan. + +**Prompt 3 -- Terrain Analysis:** +> Analyze the competitive terrain of my market using Sun Tzu's terrain framework. My market is [describe]. Map the terrain across these dimensions: regulatory environment, technology platform dynamics, customer buying behavior, distribution channels, network effects, and data advantages. Where is the terrain favorable for us? Where is it hostile? What positioning moves would shift us to more favorable ground? Present as a terrain map with strategic recommendations. + +**Prompt 4 -- Speed Audit:** +> Evaluate my company's execution speed relative to competitors using Sun Tzu's principle of speed. My company is [describe]. Our typical cycle times are: [describe -- e.g., time to ship a feature, time to close a sale, time to onboard a customer, time to make a strategic decision]. Compare these to what I know about competitors: [describe]. Where do we have speed advantages? Where are we slower? What structural changes would increase our speed without sacrificing quality? Distinguish between genuine speed and reckless haste. + +--- + +## Use Cases + +**Validation-Stage Fintech vs. Banking Incumbents** +A fintech startup targeting underbanked small businesses uses Sun Tzu's terrain analysis to identify favorable ground: the regulatory complexity of small-business lending creates a knowledge moat; banks find the segment unprofitable below $500K loan sizes; and the startup's technology enables automated underwriting at volumes that are uneconomical for manual bank processes. Rather than competing on interest rates (a fight the startup cannot win), it competes on speed and accessibility -- terrain where its technology advantage is decisive. + +**Growth-Stage SaaS Company Facing an Enterprise Incumbent's Downmarket Move** +A mid-market SaaS company discovers that a major enterprise competitor is launching a simplified product targeting its segment. Applying Sun Tzu's principles, the founder resists the impulse to respond with feature parity (prolonged conflict on unfavorable terrain). Instead, the company accelerates its own upmarket movement into the mid-enterprise segment -- territory the incumbent is vacating to pursue the downmarket opportunity. The competitive response becomes a strategic repositioning. + +**Early-Traction Marketplace Using Stealth Positioning** +A two-sided marketplace for freelance legal services deliberately avoids press coverage and public positioning during its first 18 months, operating in what Sun Tzu would call deceptive obscurity. By the time a well-funded competitor launches with a PR blitz, the marketplace has quietly assembled 2,000 vetted attorneys and 500 active corporate clients -- a supply-side network effect that the competitor's marketing budget cannot replicate quickly. The stealth period converted time into structural advantage. + +--- + +## Anti-Patterns + +1. **Taking the military metaphor too literally.** Business is not war. Competitors are not enemies to be destroyed. Customers are not territory to be conquered. The metaphor illuminates dynamics of positioning, information, and resource allocation. Applied too aggressively, it produces a toxic, zero-sum culture that repels talent and alienates partners. + +2. **Using Sun Tzu quotes as a substitute for analysis.** The text is aphoristic by design, which makes it easy to quote and difficult to operationalize. Reciting "all warfare is based on deception" is not a strategy. The value lies in translating the principles into specific competitive moves for specific market contexts. + +3. **Confusing stealth with paralysis.** Sun Tzu advocates deception and unpredictability, not inaction. Founders who use "operating in stealth mode" as justification for avoiding market feedback, delaying launch, or deferring hard decisions have mistaken invisibility for strategy. + +4. **Ignoring the "know yourself" half of the equation.** Most entrepreneurs overinvest in competitive intelligence and underinvest in honest self-assessment. Sun Tzu's framework requires both. The startup that understands its competitors perfectly but overestimates its own capabilities will still fail. + +5. **Applying offensive strategy from a position of weakness.** Sun Tzu is explicit that the weak should defend, not attack. Startups with limited capital that initiate price wars, launch aggressive marketing campaigns, or attempt frontal assaults on well-resourced competitors are violating this principle. Defend first, build strength, then choose your moment. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Terrain selection | The most consequential strategic decision is which terrain (market segment, customer persona, problem space) to compete on. Choose ground where your capabilities create asymmetric advantage and incumbents face structural disadvantages. | +| Early Traction | Speed as weapon | With product-market fit emerging, execution speed becomes the primary competitive advantage. Ship faster, learn faster, iterate faster. Sun Tzu's emphasis on swift, decisive action is most directly applicable at this stage. | +| Growth | Positioning and alliances | Competition intensifies. Strategic positioning -- choosing where NOT to compete as much as where to compete -- becomes critical. Evaluate whether competitors should be fought, avoided, or converted to partners. | +| Scale | Information dominance | At scale, the organization can invest in systematic competitive intelligence. Build formal processes for tracking competitor moves, market shifts, and emerging threats. The "know your enemy" principle becomes an institutional capability rather than a founder instinct. | + +--- + +## Output Template + +```markdown +# Competitive Strategy Brief (Sun Tzu Framework) + +**Company:** [Name] +**Market:** [Description] +**Date:** [Date] + +## Knowledge Matrix + +| Dimension | Our Assessment | Confidence Level | Intelligence Gaps | +|-----------|---------------|-----------------|-------------------| +| Our strengths | [Assessment] | [High/Medium/Low] | [What we do not know about ourselves] | +| Our weaknesses | [Assessment] | [High/Medium/Low] | [Blind spots] | +| Competitor A strengths | [Assessment] | [High/Medium/Low] | [What we do not know about them] | +| Competitor A weaknesses | [Assessment] | [High/Medium/Low] | [Intelligence needed] | + +## Terrain Analysis +**Favorable ground:** [Where we have structural advantage] +**Unfavorable ground:** [Where competitors have advantage] +**Contested ground:** [Where advantage is undetermined] + +## Strategic Posture +- [ ] Defend (build strength before engaging) +- [ ] Maneuver (reposition to favorable terrain) +- [ ] Attack (exploit specific competitor weakness) +- [ ] Avoid (redirect to uncontested space) + +## Key Moves +1. [Strategic action with rationale tied to Sun Tzu principle] +2. [Strategic action] +3. [Strategic action] + +## Speed Advantage Assessment +| Process | Our Cycle Time | Competitor Cycle Time | Advantage | +|---------|---------------|----------------------|-----------| +| [Process] | [Time] | [Time] | [+/-] | +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Porter's structural analysis of competitive forces is the modern academic equivalent of Sun Tzu's terrain analysis, providing analytical rigour to complement the strategic mindset. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- The purest expression of Sun Tzu's "win without fighting" principle: create uncontested market space where competition becomes irrelevant. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Sun Tzu's emphasis on preparation and contingency aligns with scenario planning's structured approach to anticipating multiple futures. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- Operationalizes Sun Tzu's "know yourself, know your enemy" principle as a structured assessment of strengths, weaknesses, opportunities, and threats. +- **[First-Mover Strategy](../../content/skills/game-theory/first-mover-strategy.md)** -- Sun Tzu's principles of speed, timing, and seizing initiative find their modern game-theoretic expression in first-mover advantage analysis. +- **[Information Asymmetry](../../content/skills/game-theory/information-asymmetry.md)** -- Sun Tzu's emphasis on intelligence superiority and deception maps directly to the strategic exploitation of information asymmetry in competitive contexts. diff --git a/plugins/foreman/skills/balanced-scorecard/SKILL.md b/plugins/foreman/skills/balanced-scorecard/SKILL.md deleted file mode 120000 index 0cec723..0000000 --- a/plugins/foreman/skills/balanced-scorecard/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/balanced-scorecard.md \ No newline at end of file diff --git a/plugins/foreman/skills/balanced-scorecard/SKILL.md b/plugins/foreman/skills/balanced-scorecard/SKILL.md new file mode 100644 index 0000000..0f1743a --- /dev/null +++ b/plugins/foreman/skills/balanced-scorecard/SKILL.md @@ -0,0 +1,239 @@ +--- +name: "balanced-scorecard" +description: "Builds and evaluates Kaplan and Norton's Balanced Scorecard across four perspectives: Financial, Customer, Internal Process, and Learning and Growth. Creates strategy maps linking causal chains from learning investments through process improvements to customer outcomes and financial results. Use when designing KPI systems, aligning teams around strategy, diagnosing why financial metrics are lagging, auditing measurement balance, or establishing leading indicators for organizational health." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - performance-measurement + - strategic-alignment + - kpi-design + - strategy-execution + - management-systems +related_skills: + - swot-pest-analysis + - systems-thinking + - kaizen-bpr + - net-promoter-score +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Balanced Scorecard + +Your financial statements are lying to you. Not through fraud -- through omission. Revenue, profit margins, and cash flow tell you what happened. They say nothing about what will happen. A company can post record quarterly earnings while its best engineers are updating their LinkedIn profiles, its customer satisfaction is cratering, and the process that produces its core product is one key-person dependency away from collapse. By the time these realities appear in the financial statements, the damage is done and the cost of recovery has multiplied. Robert Kaplan and David Norton published "The Balanced Scorecard" in Harvard Business Review in 1992, and for good reason it became one of the most widely adopted management frameworks of the past three decades: it forces organisations to measure what matters before it shows up in the P&L. + +--- + +## The Framework + +### The Four Perspectives + +The Balanced Scorecard translates strategy into measurable objectives across four interdependent dimensions. Each perspective answers a different question, and together they provide a complete picture of organisational health. + +#### Perspective 1: Financial -- "How do we look to shareholders?" + +This is the perspective most organisations already measure obsessively. The Balanced Scorecard does not diminish its importance but contextualises it: financial results are the outcome of performance in the other three perspectives. + +**Typical measures for startups:** +- Monthly recurring revenue (MRR) and growth rate +- Gross margin and unit economics (LTV:CAC) +- Burn rate and runway +- Revenue per employee + +The financial perspective answers whether the strategy is delivering economic results. When financial metrics deteriorate, the Balanced Scorecard directs attention to the other three perspectives to identify the root cause -- rather than the reflexive response of cutting costs or chasing revenue. + +#### Perspective 2: Customer -- "How do customers see us?" + +Customers are the source of revenue, yet most companies measure customer health crudely, if at all. This perspective captures how well the organisation delivers value to those it serves. + +**Typical measures for startups:** +- Net Promoter Score (NPS) or customer satisfaction score +- Customer retention and churn rates +- Customer acquisition cost and payback period +- Market share within target segment + +The customer perspective serves as a leading indicator of financial performance. Declining satisfaction predicts declining revenue -- but with a lag that financial metrics alone cannot detect. + +#### Perspective 3: Internal Process -- "What must we excel at?" + +The operational engine that converts resources into customer value. This perspective identifies the critical processes that drive performance in the customer and financial perspectives. + +**Typical measures for startups:** +- Product development cycle time (idea to release) +- Defect rate or quality metrics +- Onboarding time (employee and customer) +- Operational efficiency ratios + +The process perspective is where Kaizen and BPR live. Measuring process performance creates visibility into the operational health that eventually determines customer experience and financial results. + +#### Perspective 4: Learning & Growth -- "Can we continue to improve and create value?" + +The foundation. People, culture, technology, and organisational capacity to learn and adapt. This perspective is the most neglected and the most consequential for long-term survival. + +**Typical measures for startups:** +- Employee engagement and satisfaction scores +- Skill development investment per employee +- Knowledge-sharing activity (documentation, internal talks) +- Innovation pipeline (experiments run, hypotheses tested) + +Kaplan and Norton argued that learning and growth is the ultimate leading indicator: it drives process improvement, which drives customer satisfaction, which drives financial results. Neglecting it is borrowing from the future. + +### The Strategy Map: Connecting the Dots + +The four perspectives are not independent dashboards. They form a causal chain: + +``` +Learning & Growth + | + | (Skilled, engaged people build better...) + v +Internal Processes + | + | (Excellent processes deliver superior...) + v +Customer Value + | + | (Satisfied customers generate...) + v +Financial Results +``` + +A Strategy Map makes these causal links explicit. For each strategic objective, the map traces the hypothesis: "If we invest in [learning/growth initiative], then [process] will improve, which will deliver [customer outcome], resulting in [financial result]." + +This is the Balanced Scorecard's deepest contribution -- not as a measurement tool but as a strategy execution system. The map forces leaders to articulate the theory of how their strategy creates value, then measure whether that theory holds. + +### Building a Balanced Scorecard + +For each perspective, define: + +1. **Objectives** -- What are we trying to achieve? (Qualitative) +2. **Measures** -- How will we know if we are achieving it? (Quantitative) +3. **Targets** -- What level of performance constitutes success? (Specific) +4. **Initiatives** -- What actions will drive us toward the target? (Actionable) + +| Perspective | Objective | Measure | Target | Initiative | +|-------------|-----------|---------|--------|------------| +| Financial | Achieve sustainable unit economics | LTV:CAC ratio | >3:1 by Q4 | Reduce CAC through organic channel investment | +| Customer | Increase customer advocacy | NPS | >50 by Q3 | Launch customer success programme | +| Internal Process | Accelerate product delivery | Sprint velocity / release frequency | Bi-weekly releases by Q2 | Implement CI/CD pipeline | +| Learning & Growth | Build data-driven culture | % decisions backed by data | >70% by Q4 | Analytics training + dashboard access for all teams | + +--- + +## Prompts + +**Prompt 1 -- Balanced Scorecard Construction:** +> "Build a Balanced Scorecard for my business: [describe company, stage, strategy, key challenges]. For each of the four perspectives (Financial, Customer, Internal Process, Learning & Growth), define two strategic objectives, the measures that track progress, specific targets for the next [timeframe], and one initiative that drives each objective." + +**Prompt 2 -- Strategy Map Design:** +> "Create a Strategy Map for this business strategy: [describe strategy]. Trace the causal chain from Learning & Growth investments through Internal Process improvements through Customer outcomes to Financial results. For each causal link, state the hypothesis being tested and the leading indicator that would confirm or disconfirm the link." + +**Prompt 3 -- Scorecard Diagnostic:** +> "Analyse this set of business metrics: [list current metrics]. Map each metric to the Balanced Scorecard perspective it belongs to. Identify which perspectives are over-measured, which are under-measured, and which critical gaps exist. Recommend specific new metrics to create a balanced view." + +**Prompt 4 -- Leading vs. Lagging Indicator Audit:** +> "Review our current KPIs: [list KPIs]. Classify each as a leading indicator (predicts future performance) or a lagging indicator (reports past performance). For every lagging indicator that lacks a corresponding leading indicator, recommend one. Ensure each of the four Balanced Scorecard perspectives has at least one leading indicator." + +--- + +## Use Cases + +**Early-Traction Startup Aligning Team Around Strategy** + +A 15-person startup has been measuring only two things: MRR growth and burn rate. The founder senses that the team is pulling in different directions but lacks a framework to diagnose why. Building a Balanced Scorecard reveals the gap: there are no customer metrics (nobody is tracking churn or NPS), no process metrics (the team ships features but does not measure cycle time or defect rates), and no learning metrics (the last team retrospective was four months ago). The scorecard provides a shared language for what success means across all four dimensions. Within one quarter, the team reports feeling more aligned -- not because priorities changed, but because they became visible. + +**Growth-Stage Company Preventing the "Growth Trap"** + +A company growing at 200% year-over-year discovers through a Balanced Scorecard review that its Learning & Growth metrics are deteriorating: employee satisfaction has dropped from 78 to 54, voluntary turnover has doubled, and the onboarding backlog means new hires take 90 days to become productive. Meanwhile, Internal Process metrics show that release frequency has declined and defect rates are rising. Customer metrics are stable -- for now. The scorecard's causal logic makes the trajectory visible: Learning & Growth degradation will propagate through processes, then customer experience, and eventually financials, within two to three quarters. The company pauses its hiring plan, invests in onboarding infrastructure, and introduces a structured engineering career ladder. The financial impact is negative for one quarter; the three-quarter outlook improves dramatically. + +--- + +## Anti-Patterns + +**Financial Myopia.** Building a "Balanced" Scorecard with fifteen financial metrics, three customer metrics, two process metrics, and one learning metric. The point is balance. If 60% of your measures are financial, you have a sophisticated P&L, not a Balanced Scorecard. + +**Metric Overload.** Tracking forty-seven KPIs across the four perspectives. The Balanced Scorecard works through focus, not comprehensiveness. Kaplan and Norton recommended fifteen to twenty-five measures maximum. For early-stage startups, eight to twelve is sufficient: two to three per perspective. + +**Vanity Metrics in Disguise.** Populating the scorecard with measures that look good but drive no action. "Total registered users" in the Customer perspective is meaningless if most users are inactive. Every metric must connect to a decision: if the number changes, what would we do differently? + +**Ignoring the Causal Chain.** Treating the four perspectives as four separate dashboards rather than a linked system. If a customer metric declines, the Balanced Scorecard's logic directs attention to Internal Process. If a process metric declines, look to Learning & Growth. Without the causal chain, the scorecard becomes four independent measurement exercises that add no strategic insight. + +**Set-and-Forget.** Designing the Balanced Scorecard once and reviewing it annually. Strategy evolves; measures must evolve with it. Monthly scorecard reviews with quarterly revisions to objectives and measures keep the framework alive. A stale scorecard is worse than no scorecard -- it creates a false sense of measurement discipline. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establish measurement discipline | Keep it simple: 2-3 metrics per perspective, reviewed weekly | +| Growth | Align scaling with strategy | Use the Strategy Map to ensure that growth investments connect to all four perspectives | +| Scale | Drive strategy across business units | Deploy cascading scorecards: corporate scorecard decomposes into team-level scorecards with aligned objectives | + +At early traction, the Balanced Scorecard's greatest value is forcing founders to measure beyond revenue. The discipline of identifying one customer metric, one process metric, and one learning metric -- and reviewing them alongside financials -- prevents the common failure of growing revenue while the organisation deteriorates underneath. + +At scale, the framework's power multiplies through cascading. Each team builds its own scorecard aligned to the corporate strategy. Engineering's scorecard emphasises Internal Process and Learning & Growth. Sales emphasises Customer and Financial. The Strategy Map ensures these local scorecards serve the same strategic logic, preventing departmental silos from optimising against each other. + +--- + +## Output Template + +**Target Audience: Board of Directors** + +```markdown +# Balanced Scorecard Review: [Company Name] +## Period: [Quarter/Year] + +### Strategy Map Summary +[One paragraph describing the strategic hypothesis: our investments in X drive process improvements in Y, which deliver customer value Z, resulting in financial outcome W] + +### Scorecard + +#### Financial Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Customer Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Internal Process Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +#### Learning & Growth Perspective +| Objective | Measure | Target | Actual | Status | Trend | +|-----------|---------|--------|--------|--------|-------| +| [Objective] | [Measure] | [Target] | [Actual] | [On/Off Track] | [Up/Down/Flat] | + +### Causal Chain Health Check +- Learning & Growth --> Internal Process: [Healthy/Warning/Critical] -- [Brief explanation] +- Internal Process --> Customer: [Healthy/Warning/Critical] -- [Brief explanation] +- Customer --> Financial: [Healthy/Warning/Critical] -- [Brief explanation] + +### Key Actions for Next Period +1. [Action] -- Perspective: [Which] -- Owner: [Name] +2. [Action] -- Perspective: [Which] -- Owner: [Name] +3. [Action] -- Perspective: [Which] -- Owner: [Name] +``` + +--- + +## Related Skills + +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- Strategic options generated by SWOT/TOWS become the objectives and initiatives within the Balanced Scorecard's four perspectives. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- The Balanced Scorecard's causal chain is itself a simplified systems model; Systems Thinking adds sophistication to understanding feedback loops between the four perspectives. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Process improvement frameworks that drive performance in the Internal Process perspective, providing the operational methodology the scorecard measures. +- **[Net Promoter Score](../../content/skills/frameworks/net-promoter-score.md)** -- A specific customer metric that frequently serves as the primary measure in the Customer perspective of the Balanced Scorecard. +- **[SMART Goals](../../content/skills/frameworks/smart-goals.md)** -- The scorecard's objectives, measures, and targets map directly to SMART criteria, ensuring each perspective has specific and measurable commitments. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- The Strategy Map that connects the four perspectives is a core tool for translating strategic intent into aligned organizational action. diff --git a/plugins/foreman/skills/belbin-team-roles/SKILL.md b/plugins/foreman/skills/belbin-team-roles/SKILL.md deleted file mode 120000 index d6c7c31..0000000 --- a/plugins/foreman/skills/belbin-team-roles/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/belbin-team-roles.md \ No newline at end of file diff --git a/plugins/foreman/skills/belbin-team-roles/SKILL.md b/plugins/foreman/skills/belbin-team-roles/SKILL.md new file mode 100644 index 0000000..5e07625 --- /dev/null +++ b/plugins/foreman/skills/belbin-team-roles/SKILL.md @@ -0,0 +1,199 @@ +--- +name: "belbin-team-roles" +description: "Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing founding team balance, resolving execution problems caused by missing behavioral profiles, or assessing board composition." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - team-composition + - hiring + - roles + - collaboration + - team-building +related_skills: + - tuckman-team-stages + - hackman-enabling-conditions + - lewin-leadership-styles + - situational-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Belbin Team Roles + +In 2004, the United States assembled a basketball team for the Athens Olympics that included LeBron James, Tim Duncan, Allen Iverson, and Carmelo Anthony -- arguable the most talented collection of individual players ever put on a court together. They lost three games and settled for bronze. Eight years later, a Spanish national team with no single player approaching that caliber won silver and pushed the Americans to the limit. The pattern repeats across every team sport, every corporate acquisition of "star" talent, and every startup that hires exclusively from elite pedigrees: assembling the best individuals does not produce the best team. + +Meredith Belbin spent nine years at Henley Management College studying why some teams of brilliant people underperformed while other teams of average individuals consistently excelled. His research, published in *Management Teams: Why They Succeed or Fail* (1981), produced a taxonomy of nine team roles -- behavioral patterns that individuals adopt in group settings -- and a principle that has survived four decades of scrutiny: balanced teams outperform unbalanced teams, regardless of the individual talent level within them. + +--- + +## The Framework + +Belbin's nine roles cluster into three categories: Thinking roles, Action roles, and People roles. Each role contributes a specific strength and carries an "allowable weakness" -- a predictable downside that is the shadow of the strength. Effective teams do not eliminate weaknesses; they ensure that every weakness is compensated by another role's strength. + +### Thinking Roles + +**Plant (PL)** +- **Contribution:** Creative, imaginative, unorthodox. Generates novel ideas and solves difficult problems. +- **Allowable weakness:** Ignores practical details. May be too absorbed in ideas to communicate effectively. +- **Startup translation:** The visionary co-founder who sees possibilities no one else does -- and forgets to check whether the technology exists to build them. + +**Monitor Evaluator (ME)** +- **Contribution:** Sober, strategic, discerning. Sees all options and judges accurately. +- **Allowable weakness:** Can be perceived as overly critical, dry, or uninspiring. Rarely generates enthusiasm. +- **Startup translation:** The co-founder who pokes holes in every plan -- annoyingly, they are usually right. + +**Specialist (SP)** +- **Contribution:** Single-minded, self-starting, dedicated. Provides knowledge and skills in rare supply. +- **Allowable weakness:** Contributes only on a narrow front. Dwells on technicalities and misses the big picture. +- **Startup translation:** The domain expert whose deep knowledge is irreplaceable but whose interests are narrow. + +### Action Roles + +**Shaper (SH)** +- **Contribution:** Challenging, dynamic, thrives on pressure. Drives the team forward and overcomes obstacles through sheer force of will. +- **Allowable weakness:** Can be provocative, abrasive, and hurt people's feelings. Prone to impatience and frustration. +- **Startup translation:** The hard-charging co-founder who makes things happen -- and burns through relationships doing it. + +**Implementer (IMP)** +- **Contribution:** Disciplined, reliable, conservative, efficient. Turns ideas into practical actions and working plans. +- **Allowable weakness:** Somewhat inflexible. Slow to respond to new possibilities or sudden pivots. +- **Startup translation:** The operations person who actually ships what the visionaries dream up. + +**Completer Finisher (CF)** +- **Contribution:** Painstaking, conscientious, anxious. Searches out errors and omissions. Delivers on time. +- **Allowable weakness:** Inclined to worry excessively. Reluctant to delegate. Can obsess over details. +- **Startup translation:** The quality gatekeeper who catches the bugs everyone else missed -- and holds up the release doing it. + +### People Roles + +**Coordinator (CO)** +- **Contribution:** Mature, confident, identifies talent. Clarifies goals, delegates effectively, promotes decision-making. +- **Allowable weakness:** Can be perceived as manipulative. May delegate too much personal work. +- **Startup translation:** The CEO who may not be the smartest person in the room but ensures the smartest people work together. + +**Teamworker (TW)** +- **Contribution:** Cooperative, mild, perceptive, diplomatic. Listens, builds, averts friction, calms the waters. +- **Allowable weakness:** Indecisive in crunch situations. Avoids confrontation even when confrontation is necessary. +- **Startup translation:** The cultural glue who keeps the team from imploding during the inevitable founder conflicts. + +**Resource Investigator (RI)** +- **Contribution:** Extrovert, enthusiastic, communicative. Explores opportunities and develops external contacts. +- **Allowable weakness:** Overly optimistic. Loses interest after the initial enthusiasm fades. +- **Startup translation:** The business development natural who opens every door -- and follows through on about half. + +### Role Balance Diagnostics + +The critical insight is not that every team needs all nine roles filled by nine different people. Most startup teams are small enough that individuals must cover multiple roles. The diagnostic questions are: + +1. **Which roles are missing entirely?** A team of three Plants and two Shapers will generate brilliant ideas and fight passionately about them -- and ship nothing. +2. **Which roles are over-represented?** Too many Coordinators and nobody does the work. Too many Completer Finishers and the team never ships because nothing is perfect enough. +3. **Are the allowable weaknesses being compensated?** A Plant's impracticality is harmless when paired with an Implementer. Without that pairing, ideas die in abstraction. + +--- + +## Prompts + +**Prompt 1 -- Team Role Audit:** +> Analyze my team's Belbin role composition. Here are my team members and their behavioral tendencies: [describe each person's strengths, weaknesses, how they contribute in meetings, what frustrates them, what energizes them]. Map each person to their primary and secondary Belbin roles. Identify which roles are missing, which are duplicated, and what specific behavioral gaps this creates. Recommend how to address the imbalance -- through hiring, role adjustment, or conscious behavior adaptation. + +**Prompt 2 -- Hiring for Role Balance:** +> I'm hiring for [role title] on my [size] person team. Using Belbin's framework, my current team's role composition is approximately: [list roles you think each person fills]. What Belbin roles should I prioritize in this hire to improve team balance? What behavioral interview questions would help me identify candidates who naturally fill the missing roles? + +**Prompt 3 -- Conflict Diagnosis Through Role Tension:** +> My team is experiencing recurring conflict between [describe the people and the nature of the conflict -- e.g., "our CTO and Head of Product constantly clash on priorities" or "two team members keep undermining each other's proposals"]. Using Belbin's framework, diagnose whether this conflict stems from role overlap (two Shapers competing for dominance), role gaps (no Teamworker to mediate), or miscast roles (someone forced into a role that contradicts their natural tendencies). Recommend structural changes to resolve the friction. + +**Prompt 4 -- Founding Team Composition Assessment:** +> We're a founding team of [number] people starting a [type of business]. Here's what each of us brings: [describe each founder]. Using Belbin's team roles, assess whether our founding team has the role diversity to succeed. What are our critical vulnerabilities? Should our first hire specifically target a missing Belbin role, and if so, which one? + +--- + +## Use Cases + +**Three-Founder Technical Startup Missing People Roles** + +A validation-stage AI startup has three co-founders: a research scientist (Plant/Specialist), a systems architect (Implementer/Monitor Evaluator), and a machine learning engineer (Specialist/Completer Finisher). The team excels at building technology. They struggle with everything else. Investor meetings fall flat -- no one is a natural Resource Investigator or Coordinator. Internal disagreements fester -- no Teamworker smooths tensions. Product decisions stall because all three default to analysis (Monitor Evaluator) rather than action (Shaper). The Belbin diagnosis reveals a team with extraordinary Thinking and Action depth but zero People role coverage. The first hire should not be another engineer; it should be a commercially oriented co-founder or early employee who brings Coordinator, Resource Investigator, and Shaper energy. + +**Growth-Stage Company with Persistent Execution Gaps** + +A 40-person SaaS company generates excellent ideas (multiple Plants), has strong external networks (Resource Investigators in business development), and maintains a positive culture (Teamworkers). Yet they consistently miss deadlines, ship buggy releases, and fail to complete strategic initiatives. The Belbin analysis reveals a severe deficit in Implementers and Completer Finishers. The culture celebrates ideation and relationships while undervaluing the disciplined, unglamorous work of execution and quality assurance. The intervention involves both hiring (specifically targeting Implementer and Completer Finisher profiles) and cultural recalibration (elevating the status of reliable execution to match that of creative innovation). + +**Board Composition Analysis** + +A scale-stage company's board consists entirely of former CEOs and venture capitalists -- a concentration of Coordinators, Shapers, and Resource Investigators. Board meetings are energetic, directive, and fast-moving, but they consistently miss risks that a Monitor Evaluator would catch and operational details that an Implementer or Completer Finisher would flag. Applying Belbin to board composition reveals the structural blind spot. Adding an independent director with strong ME tendencies -- perhaps a former CFO or risk officer -- rebalances the board's collective intelligence. + +--- + +## Anti-Patterns + +- **Hiring in Your Own Image.** Founders unconsciously seek candidates who think and behave like themselves. A Shaper founder hires other Shapers. A Plant founder hires other Plants. The result is a team that is strong in one dimension and catastrophically weak in others. Belbin's framework is an explicit corrective to this instinct. + +- **Treating Roles as Fixed Labels.** Using Belbin to permanently categorize people rather than understanding roles as situational tendencies. Individuals have primary and secondary roles, and they may shift emphasis depending on the team's needs. Labeling someone as "just a Teamworker" limits both the individual and the team. + +- **Pathologizing Allowable Weaknesses.** Performance-managing a Plant for being impractical or a Completer Finisher for being anxious about quality. These are the predictable shadow sides of essential strengths. The framework explicitly calls them "allowable" -- the cost of a capability the team needs. Address the weakness when it becomes disruptive, but recognize that eliminating it may also eliminate the strength. + +- **Ignoring Role Conflicts in Small Teams.** Assuming that a small team does not need role diversity because "everyone does everything." The smaller the team, the more consequential each role gap becomes. A five-person team missing an Implementer feels the absence in every sprint. + +- **Using Belbin to Justify Exclusion.** Weaponizing the framework to argue that certain people "don't fit" the team composition. Belbin describes behavioral contributions, not human worth. The framework is a tool for understanding and optimizing, not for gatekeeping. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founding team balance | The smallest teams have the most consequential role gaps; founders must honestly assess their combined role coverage and hire accordingly | +| Early Traction | First hires as role fillers | Each new hire should be evaluated partly for the Belbin roles they bring; technical skill is necessary but insufficient | +| Growth | Team-level composition across departments | Role balance matters within each team and across the leadership group; department heads need different role combinations than execution teams | +| Scale | Organizational role diversity | At scale, Belbin applies to the composition of leadership teams, project teams, and boards; the framework scales from five-person startups to thousand-person organizations | + +--- + +## Output Template + +```markdown +# Belbin Team Role Audit: [Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Purpose of Audit:** [Hiring decision / Conflict resolution / Team optimization] + +## Role Map + +| Team Member | Primary Role | Secondary Role | Observed Strengths | Allowable Weakness | +|-------------|-------------|---------------|-------------------|-------------------| +| [Name] | [Role] | [Role] | [Strengths] | [Weakness] | + +## Role Distribution Summary + +| Category | Roles Present | Roles Missing | Impact of Gap | +|----------|--------------|--------------|---------------| +| Thinking | [PL, ME, SP] | [Missing] | [Impact] | +| Action | [SH, IMP, CF] | [Missing] | [Impact] | +| People | [CO, TW, RI] | [Missing] | [Impact] | + +## Critical Gaps and Recommendations +1. **Missing [Role]:** [Impact on team] -> [Recommendation: hire, develop, or reassign] +2. **Over-represented [Role]:** [Impact on team] -> [Recommendation] + +## Hiring Priority +- **Next hire should bring:** [Primary Belbin role] + [Secondary role] +- **Interview signals to look for:** [Behavioral indicators] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Role conflicts surface most intensely during Tuckman's Storming stage; understanding Belbin roles helps navigate role negotiation during that critical phase. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman's "right people" condition maps directly to Belbin's principle of role-balanced composition, providing the structural imperative for why role diversity matters. +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- Different Belbin roles require different leadership approaches; a Plant needs more autonomy while an Implementer benefits from clearer direction. +- **[Myers-Briggs Type Indicator](../../content/skills/frameworks/myers-briggs-type-indicator.md)** -- MBTI explains underlying personality preferences while Belbin describes the behavioural contributions those preferences produce in team settings. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Provides the leadership practices for building the collaborative environment in which Belbin's diverse roles can contribute effectively. diff --git a/plugins/foreman/skills/black-swans/SKILL.md b/plugins/foreman/skills/black-swans/SKILL.md deleted file mode 120000 index ad5c47a..0000000 --- a/plugins/foreman/skills/black-swans/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/black-swans.md \ No newline at end of file diff --git a/plugins/foreman/skills/black-swans/SKILL.md b/plugins/foreman/skills/black-swans/SKILL.md new file mode 100644 index 0000000..a332cae --- /dev/null +++ b/plugins/foreman/skills/black-swans/SKILL.md @@ -0,0 +1,175 @@ +--- +name: "black-swans" +description: "Applies Taleb's Black Swan theory to assess and mitigate exposure + to rare, high-impact unpredictable events. Distinguishes between Mediocristan + and Extremistan domains, designs barbell strategies, builds antifragility, and + audits business vulnerabilities including supply chain concentration, customer + dependency, and regulatory risk. Use when stress-testing a business model, + evaluating tail risks, designing resilience architecture, or building robust + strategies that survive shocks rather than attempting to predict them." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - growth + - scale +tags: + - risk-management + - uncertainty + - resilience + - probability + - tail-risk +related_skills: + - scenario-planning + - porters-five-forces + - business-model-canvas +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Black Swan Theory + +On September 15, 2008, Lehman Brothers filed for the largest bankruptcy in American history. Within weeks, the global financial system stood at the brink of collapse. Virtually no mainstream economist had predicted the crisis. The models were elegant, the data was abundant, and the conclusions were catastrophically wrong. Nassim Nicholas Taleb had a name for this kind of event -- a Black Swan -- and his 2007 book of the same title had warned, with uncomfortable precision, that the financial system was a powder keg. The concept has since become indispensable vocabulary for anyone who takes risk seriously. + +A Black Swan is an event that satisfies three criteria: it is an outlier beyond the realm of regular expectations, it carries extreme impact, and human nature compels us to fabricate explanations for it after the fact, making it seem predictable in retrospect. The theory does not concern itself with predicting these events -- that is the point. It concerns itself with acknowledging their inevitability and structuring decisions accordingly. + +--- + +## The Framework + +Taleb's argument rests on a distinction between two domains of uncertainty, which he labels Mediocristan and Extremistan. + +### Mediocristan vs. Extremistan + +| Domain | Characteristics | Examples | +|--------|----------------|----------| +| **Mediocristan** | Outcomes cluster around the mean; no single observation can dramatically alter the aggregate | Human height, calorie consumption, car accident rates | +| **Extremistan** | A single observation can disproportionately dominate the total; winner-take-all dynamics prevail | Book sales, wealth distribution, startup valuations, pandemic deaths | + +Most business decisions operate in Extremistan, yet most business tools assume Mediocristan. This mismatch is the source of strategic catastrophe. + +### The Three Properties of a Black Swan + +1. **Rarity** -- The event lies outside ordinary experience. No amount of historical data would have led a reasonable observer to anticipate it. +2. **Extreme Impact** -- When it arrives, it reshapes the landscape. Market structures, competitive positions, and entire industries can be created or destroyed. +3. **Retrospective Predictability** -- After the event, analysts construct narratives that make it appear inevitable. This "narrative fallacy" breeds dangerous overconfidence. + +### The Narrative Fallacy and Confirmation Bias + +Humans are pattern-seeking creatures. Taleb argues that we systematically overfit stories to data, mistaking correlation for causation and randomness for signal. Entrepreneurs are especially vulnerable: the hero narratives of startup culture encourage the belief that outcomes are earned rather than partly determined by chance. Acknowledging the role of luck is not defeatism -- it is the foundation of robust strategy. + +### Building Robustness (and Antifragility) + +Taleb's prescription is not to predict Black Swans but to build systems that survive them -- or, better still, benefit from them: + +- **Barbell Strategy**: Concentrate resources in extremely safe assets on one end and small, high-upside bets on the other. Avoid the middle, where moderate risk produces moderate returns but maximum vulnerability to Black Swans. +- **Optionality**: Structure decisions so that upside is uncapped while downside is limited. Startups that can pivot cheaply have more optionality than those locked into rigid capital commitments. +- **Redundancy over Efficiency**: Systems optimized purely for efficiency are fragile. Maintaining slack -- cash reserves, diversified suppliers, backup capabilities -- creates resilience. +- **Via Negativa**: Sometimes the most powerful strategy is subtraction. Eliminate exposures to catastrophic risk rather than trying to add predictive capability. + +--- + +## Prompts + +**Prompt 1 -- Black Swan Exposure Audit:** +> Analyze my business for Black Swan vulnerability. My company is [describe company, sector, stage, key dependencies]. Identify our top 5 exposures to rare, high-impact events -- consider supply chain, technology shifts, regulatory changes, customer concentration, and financial structure. For each exposure, rate the potential impact (existential / severe / moderate) and our current resilience (fragile / robust / antifragile). Present results in a table. + +**Prompt 2 -- Barbell Strategy Design:** +> Help me design a barbell strategy for [company/product/investment portfolio]. On the safe end, what should I protect absolutely? On the speculative end, what small bets with asymmetric upside should I place? What middle-ground positions should I reduce or eliminate? Structure the output as a three-column framework: Safe (80-90% of resources), Eliminate (the vulnerable middle), and Speculative (10-20% of resources). + +**Prompt 3 -- Post-Mortem Narrative Fallacy Check:** +> I recently experienced [describe event -- a major win, loss, or surprise]. Walk me through a narrative fallacy analysis. What story am I likely telling myself about why this happened? What alternative explanations exist that I might be ignoring? What role did randomness, timing, or external forces play? Help me separate genuine causal factors from retrospective storytelling. + +**Prompt 4 -- Antifragility Assessment:** +> Evaluate whether my business model is fragile, robust, or antifragile using Taleb's framework. My company is [describe]. For each major dimension -- revenue model, team structure, technology stack, customer base, funding structure -- classify the current state and recommend specific changes to move toward antifragility. What stressors could actually make us stronger? + +--- + +## Use Cases + +**SaaS Startup with Single-Cloud Dependency** +A Series A SaaS company runs its entire infrastructure on a single cloud provider with no multi-cloud contingency. The founder applies the Black Swan exposure audit and discovers that a provider outage, pricing change, or policy shift represents an existential risk. The barbell strategy suggests maintaining 85% of workloads on the primary provider (cost-efficient and familiar) while investing 15% of engineering capacity into abstraction layers and secondary provider readiness. The company does not need to run multi-cloud today -- it needs the option to migrate within weeks rather than months. + +**Consumer Hardware Startup Facing Supply Chain Concentration** +A growth-stage hardware company sources a critical component from a single factory in one region. COVID-19 demonstrated that geographic concentration in manufacturing is a textbook Extremistan exposure. Applying Taleb's redundancy principle, the founder diversifies to three suppliers across two continents, accepting a 12% cost increase in exchange for eliminating single-point-of-failure risk. The cost is insurance, not waste. + +**Venture-Backed Marketplace Dependent on Regulatory Goodwill** +A marketplace startup operating in a lightly regulated space applies the exposure audit and recognizes that a single regulatory change could eliminate its business model entirely. Rather than lobbying alone, the founder builds optionality: a secondary revenue model that functions under stricter regulation, and contractual structures that limit liability exposure. The Black Swan lens reframes regulatory risk from "unlikely" to "unknown timing." + +--- + +## Anti-Patterns + +1. **Treating Black Swan theory as a license for paranoia.** The framework is not about fearing everything -- it is about identifying asymmetric exposures and restructuring them. Founders who become paralyzed by tail-risk analysis accomplish nothing. The goal is robustness, not anxiety. + +2. **Claiming every negative surprise is a Black Swan.** A competitor launching a similar product is not a Black Swan -- it is a foreseeable competitive event. Losing a key client is painful but predictable. Reserve the label for events that genuinely lie outside the boundary of reasonable expectation. Overuse dilutes the concept into meaninglessness. + +3. **Confusing fragility reduction with prediction.** The entire point of the framework is that Black Swans cannot be predicted. Founders who respond by hiring consultants to "predict Black Swans" have missed Taleb's argument entirely. The correct response is structural: build systems that survive shocks, not crystal balls that fail to foresee them. + +4. **Ignoring positive Black Swans.** Taleb explicitly discusses positive Black Swans -- unexpected events with massive upside. Entrepreneurs who focus exclusively on downside risk miss the strategic imperative to position for serendipity. Maintaining optionality, staying visible in networks, and placing small speculative bets are strategies that harvest positive Black Swans. + +5. **Over-optimizing for efficiency at the expense of redundancy.** The lean startup ethos prizes efficiency, and rightly so at the earliest stages. But as companies grow, the relentless elimination of slack creates brittleness. The company with zero cash reserves, one key engineer, and a single revenue channel is not lean -- it is fragile. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Identify existential assumptions | At this stage, the entire venture is one large bet. The Black Swan lens helps founders distinguish between assumptions they can test and exposures they cannot control. Focus on limiting downside through cheap experiments rather than heavy capital commitment. | +| Growth | Stress-test dependencies | Revenue is flowing but concentration risk is building. Audit customer concentration, supplier dependencies, and team key-person risk. Begin building redundancy into systems that were expedient during validation. | +| Scale | Institutional resilience architecture | At scale, the stakes are highest and the organization is most prone to complacency. Implement formal risk committees, maintain meaningful cash reserves, and run regular Black Swan tabletop exercises. The goal shifts from personal awareness to organizational culture. | + +--- + +## Output Template + +```markdown +# Black Swan Exposure Assessment + +**Company:** [Name] +**Stage:** [Current stage] +**Date:** [Date] + +## Exposure Map + +| Exposure | Domain (Mediocristan/Extremistan) | Impact if Realized | Current Resilience | Priority | +|----------|----------------------------------|--------------------|--------------------|----------| +| [Exposure 1] | [Domain] | [Existential/Severe/Moderate] | [Fragile/Robust/Antifragile] | [Critical/High/Medium] | +| [Exposure 2] | [Domain] | [Impact] | [Resilience] | [Priority] | +| [Exposure 3] | [Domain] | [Impact] | [Resilience] | [Priority] | + +## Barbell Strategy + +### Safe Side (80-90% of resources) +- [What to protect absolutely] + +### Eliminate (Vulnerable middle) +- [Positions to reduce or exit] + +### Speculative Side (10-20% of resources) +- [Small, high-upside bets] + +## Immediate Actions +1. [Highest-priority resilience action] +2. [Second priority] +3. [Third priority] + +## Review Cadence +- Quarterly exposure reassessment +- Annual barbell rebalancing +``` + +--- + +## Related Skills + +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Where Black Swan theory addresses the unpredictable, scenario planning builds structured responses to plausible futures; together they cover both the foreseeable and the unforeseeable. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- Mapping the entire business model makes hidden dependencies visible, which is a precondition for effective Black Swan exposure auditing. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Reveals the interconnected feedback loops through which a single shock can cascade across an entire business, amplifying Black Swan impact in non-obvious ways. +- **[VUCA Framework](../../content/skills/frameworks/vuca-framework.md)** -- Provides the vocabulary and leadership approach for operating in volatile, uncertain environments where Black Swan events are structurally inevitable. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's work on cognitive biases explains why humans systematically underestimate tail risks, making Taleb's prescriptions for structural robustness essential. +- **[Decision Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Provides the leadership practices for making sound decisions when a Black Swan event actually materializes and time is compressed. diff --git a/plugins/foreman/skills/blue-ocean-strategy/SKILL.md b/plugins/foreman/skills/blue-ocean-strategy/SKILL.md deleted file mode 120000 index 13a59c1..0000000 --- a/plugins/foreman/skills/blue-ocean-strategy/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/blue-ocean-strategy.md \ No newline at end of file diff --git a/plugins/foreman/skills/blue-ocean-strategy/SKILL.md b/plugins/foreman/skills/blue-ocean-strategy/SKILL.md new file mode 100644 index 0000000..04df26f --- /dev/null +++ b/plugins/foreman/skills/blue-ocean-strategy/SKILL.md @@ -0,0 +1,221 @@ +--- +name: "blue-ocean-strategy" +description: "Applies Kim and Mauborgne's Blue Ocean Strategy to create uncontested market space through value innovation. Uses the Strategy Canvas to map competitive factors, the ERRC Grid to Eliminate-Reduce-Raise-Create value elements, and the Three Tiers of Noncustomers to identify untapped demand. Use when entering saturated markets, escaping price-based competition, redesigning a value proposition, identifying noncustomer segments, or evaluating whether a new venture creates a genuinely new market category." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth +tags: + - market-creation + - competitive-strategy + - value-innovation + - differentiation + - strategic-positioning +related_skills: + - porters-five-forces + - art-of-war + - business-model-canvas + - disruptive-innovation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Blue Ocean Strategy + +Picture the ocean. In red waters, sharks circle. The water is thick with blood -- the blood of competitors slashing prices, matching features, fighting over the same customers in the same market with the same value proposition. Margins shrink. Growth stalls. Strategy degenerates into a war of attrition. Now picture open blue water: vast, calm, and empty. No competitors. No blood. A market space so new that the rules have not yet been written. W. Chan Kim and Renee Mauborgne, professors at INSEAD, published *Blue Ocean Strategy* in 2005 to formalize this distinction and, more importantly, to provide a systematic method for moving from red to blue. The book has sold over 4 million copies and been translated into 46 languages -- evidence that the desire to escape competitive bloodbaths is, itself, a universal market need. + +--- + +## The Framework + +### Red Ocean vs. Blue Ocean + +| Dimension | Red Ocean | Blue Ocean | +|-----------|-----------|------------| +| Market space | Compete in existing markets | Create uncontested market space | +| Competition | Beat the competition | Make competition irrelevant | +| Demand | Exploit existing demand | Create and capture new demand | +| Value/Cost | Choose between differentiation and low cost | Pursue differentiation AND low cost simultaneously | +| Strategy focus | Alignment of activities with strategic choice | Alignment of activities with pursuit of differentiation and low cost | + +The core insight: conventional strategy (Porter's framework, for instance) assumes a fixed market structure and asks how to position within it. Blue Ocean Strategy challenges the assumption. Markets are not fixed; they can be created. The most profitable strategic move is not to compete better but to compete differently -- or, ideally, to create a space where competition is temporarily irrelevant. + +### Value Innovation + +Value innovation is the cornerstone concept. It breaks the trade-off between differentiation and low cost by simultaneously: + +- **Eliminating** factors the industry takes for granted but that customers do not value +- **Reducing** factors well below the industry standard +- **Raising** factors well above the industry standard +- **Creating** factors the industry has never offered + +This is not incremental improvement. It is a fundamental reconfiguration of the value proposition. + +### The Four Actions Framework (ERRC Grid) + +The ERRC Grid operationalizes value innovation: + +``` +┌─────────────────────────┬─────────────────────────┐ +│ ELIMINATE │ RAISE │ +│ │ │ +│ Which factors that the │ Which factors should be │ +│ industry takes for │ raised well above the │ +│ granted should be │ industry standard? │ +│ eliminated? │ │ +├─────────────────────────┼─────────────────────────┤ +│ REDUCE │ CREATE │ +│ │ │ +│ Which factors should be │ Which factors should be │ +│ reduced well below the │ created that the │ +│ industry standard? │ industry has never │ +│ │ offered? │ +└─────────────────────────┴─────────────────────────┘ +``` + +**Cirque du Soleil** is Kim and Mauborgne's canonical example: +- **Eliminated**: Animal acts, star performers, aisle concession sales, multiple show arenas +- **Reduced**: Fun and humor, thrill and danger +- **Raised**: Unique venue, artistic music and dance +- **Created**: Theme, refined viewing environment, multiple productions, artistic richness + +The result: Cirque captured circus audiences AND theater audiences while operating at lower cost than traditional circuses (no animals, no stars) and higher prices than most theater (unique experience). + +### The Strategy Canvas + +The Strategy Canvas is a diagnostic and action tool. It plots the current competitive landscape on a single chart: + +- The horizontal axis lists the key factors of competition in the industry +- The vertical axis captures the offering level for each factor (low to high) +- Each competitor is plotted as a value curve connecting their offering levels + +The strategic insight emerges when you overlay your proposed blue ocean value curve against the existing curves. A genuinely innovative strategy will have a fundamentally different shape -- not just higher or lower on the same factors, but elevated on some, reduced on others, and introducing entirely new factors. + +### The Three Tiers of Noncustomers + +Blue Oceans are created by converting noncustomers into customers. Kim and Mauborgne identify three tiers: + +1. **Soon-to-be noncustomers**: People on the edge of the existing market, minimally using current offerings and ready to leave +2. **Refusing noncustomers**: People who have consciously rejected the industry's offerings as irrelevant or unaffordable +3. **Unexplored noncustomers**: People in distant markets who have never considered the industry's offerings as an option + +Each tier represents increasingly large -- and increasingly overlooked -- pools of demand. + +--- + +## Prompts + +**Prompt 1 -- Strategy Canvas Mapping:** +> Map the strategy canvas for my industry. I compete in [describe industry/market]. The key players are [list 3-5 competitors]. Help me identify the 6-10 factors that the industry currently competes on (e.g., price, features, service quality, brand, convenience, customization). Rate each competitor (including my company) on each factor (Low/Medium/High). Then visualize the value curves and identify where all competitors converge (red ocean indicators) and where differentiation opportunities exist. + +**Prompt 2 -- ERRC Grid Workshop:** +> Help me complete the ERRC (Eliminate-Reduce-Raise-Create) Grid for my business. My company is [describe: product, market, current positioning]. Based on the strategy canvas of my industry, identify: (1) Which factors can we eliminate without losing core value? (2) Which factors can we reduce below industry standard to cut costs? (3) Which factors should we raise above the standard to differentiate? (4) What entirely new factors could we create? For each recommendation, explain the rationale and estimate the impact on both cost structure and buyer value. + +**Prompt 3 -- Noncustomer Analysis:** +> Analyze the three tiers of noncustomers for my market. My current customer base is [describe]. Help me identify: Tier 1 (soon-to-be noncustomers who are barely using our type of product -- why are they dissatisfied?), Tier 2 (refusing noncustomers who have consciously rejected our category -- what are their objections?), Tier 3 (unexplored noncustomers who never considered our category -- what would need to change for them to engage?). For each tier, estimate the potential market size and recommend specific approaches to convert them. + +**Prompt 4 -- Blue Ocean Feasibility Test:** +> Evaluate my blue ocean idea against Kim and Mauborgne's three criteria for a viable blue ocean strategy. My idea is [describe the value innovation concept]. Test it against: (1) Utility -- does it offer exceptional buyer utility? (2) Price -- is the price accessible to the mass of target buyers? (3) Cost -- can we achieve the target cost and still make a profit? (4) Adoption -- what are the adoption hurdles and how do we address them? Identify the weakest dimension and recommend how to strengthen it. + +--- + +## Use Cases + +**Idea-Stage Founder Designing a New Fitness Product** +A founder observes that the fitness industry competes heavily on equipment quality, trainer credentials, facility ambiance, and class variety -- the standard red ocean factors. Applying the ERRC Grid, she eliminates expensive facilities (shifting to a mobile app), reduces trainer credentials requirements (using AI-driven personalization instead), raises convenience to the maximum (workouts available anytime, anywhere, in any duration), and creates adaptive difficulty that adjusts in real time. The result is not a cheaper gym or a better gym but a fundamentally different value curve that attracts Tier 2 noncustomers -- people who found gyms intimidating or inconvenient. + +**Early-Traction B2B SaaS Redefining Its Category** +A project management tool enters a market dominated by Asana, Monday, and Jira. The strategy canvas reveals that all incumbents compete on feature breadth, integrations, and customization -- producing convergent value curves. The startup eliminates advanced customization (the 90% of features that 90% of users never touch), reduces the learning curve from days to minutes, raises real-time collaboration to a level no competitor matches, and creates an AI-powered "project health score" that no one offers. The blue ocean is not project management; it is "effortless project visibility" -- a different category serving the same buyers with a different value proposition. + +**Growth-Stage Company Expanding Through Noncustomer Conversion** +A $20M ARR legal tech company serving large law firms uses the three-tier noncustomer framework to identify expansion opportunities. Tier 1: mid-size firms using the product minimally because it requires dedicated IT support. Tier 2: solo practitioners who rejected the category because pricing assumed firm-level budgets. Tier 3: in-house corporate legal teams who never considered external legal tech tools. Each tier implies a different product and pricing strategy. The company launches a self-service tier (Tier 1), a solo plan at $49/month (Tier 2), and an enterprise-grade integration with corporate systems (Tier 3) -- tripling its addressable market without competing more intensely in its existing segment. + +--- + +## Anti-Patterns + +1. **Confusing differentiation with blue ocean creation.** A better mousetrap is differentiation. A blue ocean requires a fundamentally different value curve -- eliminating and reducing factors, not just adding new ones. If the competitive factors remain the same and you are simply "better," you are still in the red ocean with a shinier boat. + +2. **Pursuing blue oceans without verifying buyer utility.** Not every uncontested space is uncontested for good reason, but some are. The absence of competitors may indicate an unserved need OR a need that does not exist. The ERRC Grid must be validated with actual customers, not just logical deduction. + +3. **Neglecting execution barriers.** The strategy canvas may reveal a beautiful blue ocean opportunity, but if the company lacks the capabilities, resources, or organizational alignment to execute the required value curve, the strategy remains theoretical. Blue Ocean Strategy without operational reality is a PowerPoint exercise. + +4. **Ignoring imitation speed.** Blue oceans do not stay blue forever. Competitors observe and follow. The question is not only "can we create a blue ocean?" but "how long before it turns red, and what structural advantages will we have built by then?" Network effects, proprietary data, brand, and switching costs are the barriers that extend blue ocean duration. + +5. **Applying the framework to sustaining innovation.** Blue Ocean Strategy is designed for market creation, not incremental improvement. Using the ERRC Grid to optimize an existing product within an existing market produces interesting tactical insights but misses the framework's fundamental purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Blue ocean identification | The ideal moment to apply the framework -- before competitive commitments have been made. Use the strategy canvas to evaluate whether a proposed venture enters a red ocean or creates a blue one. If the value curve looks like everyone else's, reconsider before building. | +| Validation | Noncustomer testing | Validate the blue ocean hypothesis with actual noncustomers, not just existing market participants. If Tier 2 and Tier 3 noncustomers respond to the value proposition, the blue ocean is real. If only existing customers respond, you have built differentiation, not a new market. | +| Early Traction | Value curve sharpening | With market feedback, refine the ERRC Grid. Some factors initially eliminated may need partial restoration. Some created factors may need adjustment. The value curve is a hypothesis that improves with data. | +| Growth | Blue ocean defense | As the market space becomes visible to competitors, invest in structural barriers: network effects, proprietary data, brand identity, ecosystem lock-in. The strategic question shifts from "how do we create the blue ocean?" to "how do we keep it blue?" | + +--- + +## Output Template + +```markdown +# Blue Ocean Strategy Analysis + +**Company:** [Name] +**Industry:** [Current industry/market] +**Date:** [Date] + +## Strategy Canvas + +| Competitive Factor | Industry Avg | Competitor A | Competitor B | Our Current | Our Blue Ocean | +|-------------------|-------------|-------------|-------------|-------------|----------------| +| [Factor 1] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | +| [Factor 2] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | [L/M/H] | +| [New Factor] | N/A | N/A | N/A | N/A | [L/M/H] | + +## ERRC Grid + +| Eliminate | Reduce | +|-----------|--------| +| [Factor] -- [Rationale] | [Factor] -- [Rationale] | + +| Raise | Create | +|-------|--------| +| [Factor] -- [Rationale] | [Factor] -- [Rationale] | + +## Noncustomer Tiers + +| Tier | Description | Estimated Size | Conversion Strategy | +|------|-------------|---------------|-------------------| +| Tier 1 (Edge) | [Who they are, why they are leaving] | [Size] | [Approach] | +| Tier 2 (Refusing) | [Who they are, why they reject] | [Size] | [Approach] | +| Tier 3 (Unexplored) | [Who they are, why they never considered] | [Size] | [Approach] | + +## Feasibility Assessment +- **Buyer Utility:** [Pass/Fail -- explanation] +- **Price Accessibility:** [Pass/Fail -- explanation] +- **Cost Structure:** [Pass/Fail -- explanation] +- **Adoption Hurdles:** [List and mitigation] + +## Blue Ocean Durability +**Expected time before imitation:** [Estimate] +**Structural barriers to build:** [List] +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Five Forces diagnoses the competitive structure of the red ocean, while Blue Ocean Strategy charts the escape route to uncontested market space. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Both frameworks identify opportunities in spaces incumbents overlook, but disruption focuses on low-end or new-market footholds while Blue Ocean pursues value innovation across the entire offering. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- Once a blue ocean opportunity is identified, the Canvas structures the complete operational design needed to deliver the new value proposition. +- **[Art of War](../../content/skills/frameworks/art-of-war.md)** -- Sun Tzu's "win without fighting" principle is the ancient philosophical precursor to blue ocean thinking, providing strategic mindset where Kim and Mauborgne provide analytical tools. +- **[Doblin's Ten Types of Innovation](../../content/skills/frameworks/doblin-ten-types.md)** -- Blue Ocean identifies the need for a different value curve; Doblin's ten types provide the specific innovation dimensions across which to build that differentiation. +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- A blue ocean strategy requires realignment of the entire marketing mix, as the new value curve reshapes product, price, place, and promotion simultaneously. diff --git a/plugins/foreman/skills/building-story-stakes/SKILL.md b/plugins/foreman/skills/building-story-stakes/SKILL.md deleted file mode 120000 index 1cb3ec2..0000000 --- a/plugins/foreman/skills/building-story-stakes/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/building-story-stakes.md \ No newline at end of file diff --git a/plugins/foreman/skills/building-story-stakes/SKILL.md b/plugins/foreman/skills/building-story-stakes/SKILL.md new file mode 100644 index 0000000..a4857ca --- /dev/null +++ b/plugins/foreman/skills/building-story-stakes/SKILL.md @@ -0,0 +1,209 @@ +--- +name: "building-story-stakes" +description: "Teaches five named techniques for creating and sustaining narrative tension in any story. Applies when a founder needs to hold an audience's attention through a pitch, investor update, all-hands talk, or customer case study. Use when a narrative feels flat, when attention wanders mid-presentation, or when the storyteller senses the audience could walk away without consequence." +version: "1.0.0" +category: "storytelling" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - stakes + - narrative-tension + - audience-engagement + - pitching + - suspense + - persuasion + - elephant + - backpack + - breadcrumbs + - hourglass + - crystal-ball +related_skills: + - storytelling-truth-and-vividness + - emotional-impact-in-stories + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Building Story Stakes + +What keeps a listener hooked is not curiosity. It is the elephant you planted at the beginning -- the question they desperately need answered. Stakes are the gears that make stories work; without them, any narrative, however polished, becomes something an audience can take or leave. The framework identifies five discrete techniques for infusing stakes into a story, each learnable and each deployable in settings ranging from a Moth stage to a Series A pitch meeting. The entrepreneur who masters these techniques does not merely tell stories. That entrepreneur controls attention. + +--- + +## The Framework + +Stakes answer a deceptively simple question: would the audience want to hear the next sentence? If the answer is no, the story has failed -- not in content, but in architecture. These five strategies address different failure modes of attention, and they work in combination. Some stories need all five. Others, naturally loaded with drama, need only the first. The key is diagnosis: knowing which strategy a given moment demands. + +### 1. The Elephant + +Every story must have an Elephant. The Elephant is the large, obvious thing in the room -- a clear statement of the need, the want, the problem, the peril, or the mystery. It tells the audience what to expect, gives them a reason to wonder, and infuses the story with instantaneous stakes. + +The Elephant should appear within the first sixty seconds. Thirty seconds is better. Storytellers lack the luxury of trailers; when a speaker begins, the audience has no idea whether they are hearing a comedy, a tragedy, or a waste of their morning. Without an early Elephant, listeners check out. + +**The distinction matters.** Consider two openings for the same company origin story: + +- *Version A:* "Our co-founder grew up in a small town in Ohio. She studied engineering at State. She worked at three companies before starting ours." +- *Version B:* "When our co-founder was twenty-six, she bet her entire savings -- $11,400 -- on a product nobody in her industry believed would work. Our co-founder grew up in a small town in Ohio..." + +Version B has an Elephant. The character sketch that follows is identical, but now the audience carries a question: did she lose everything? + +**Elephants can change colour.** A story may begin with one apparent direction and reveal a deeper one. The pitch deck that opens with "How do we reduce churn by 40%?" may end on a far more interesting question about customer identity. The audience believes they are on one path; the storyteller reveals it was always a different, richer one. This is not bait-and-switch. The path was the same all along. Only its depth was hidden. + +### 2. The Backpack + +A Backpack loads the audience with the storyteller's hopes, fears, and plans before moving the story forward. Its purpose is twofold: make the audience wonder what will happen next, and -- more ambitiously -- make them feel something close to what the storyteller felt in the moment. + +The mechanism is plan articulation. Before a critical scene, the storyteller explains the plan in full. If the plan then fails, the audience experiences something like the same disappointment the storyteller felt. They knew the plan. They wanted it to succeed. Their shoulders slump. + +This is why heist films explain the robbery before the heist begins. Danny Ocean's crew lays out every step so that the audience becomes a member of the team. When things go wrong, the frustration is shared. + +**For entrepreneurs:** Before describing a product launch, a fundraising round, or a pivotal customer meeting, lay out the plan. Detail the strategy, the hoped-for outcome, the metrics that would signal success. Then describe what actually happened. The gap between plan and reality is where the audience lives. + +Plans that work perfectly make terrible stories. Perfect execution is the province of narcissists and thin-skinned egotists, as the framework bluntly observes. The audience wants struggle before triumph. + +### 3. Breadcrumbs + +Breadcrumbs are small hints dropped about a future event -- just enough to keep the audience guessing, never enough to let them guess correctly. The storyteller reveals one intriguing detail and withholds the rest. + +The trick is selectivity. Choose Breadcrumbs that create maximum wonder without telegraphing the outcome. They are most effective when something truly unexpected is coming. A single well-placed detail -- "and then I noticed the crumpled uniform in the backseat" -- can keep an audience leaning forward through an otherwise expository passage. + +### 4. The Hourglass + +When the audience is hanging on every word, the Hourglass says: let them hang. At the precise moment the story reaches its most anticipated beat, the storyteller slows down. Introduces unnecessary (but evocative) detail. Describes things that do not require description. Grinds the narrative to a halt. + +This feels counterintuitive. The instinct is to rush toward the payoff. Resist. The Hourglass works because the audience already wants the next sentence more than anything. Every second of delay compounds the tension. + +The technique is demonstrated by describing a McDonald's uniform in granular detail at the exact moment the audience needs to know what happens when a door opens. "Blue shirt. Blue pants. Blue tie. Gold name badge." The story has stopped. The audience cannot breathe. + +**In a pitch context:** When you reach the moment of product-market fit revelation, the first major customer win, or the turning point that changed everything -- slow down. Add sensory detail. Set the scene with physical specifics. Make the investor wait five more seconds for the number they need. + +### 5. The Crystal Ball + +A Crystal Ball is a false prediction made by the storyteller to cause the audience to wonder whether it will prove true. It exploits the human compulsion to anticipate the future. + +"I was sure the investor was going to say no. I could see it in the way he closed his notebook." This prediction -- stated explicitly -- makes the audience hold its breath. Even if the prediction is wrong (especially if it is wrong), the audience needed to find out. + +Deploy Crystal Balls when the prediction seems plausible, when the guess is reasonable, and when the predicted outcome presents an intriguing or frightening possibility. + +### The Supplementary Principle: Make the Big Story Little + +Large, dramatic events -- near-death experiences, massive failures, extraordinary successes -- are paradoxically the hardest stories to tell. The big parts are singular, unusual, and difficult to relate to. The secret: find the small, specific, personal moment hidden inside the big event. + +A story about nearly going bankrupt is not really about the bank balance. It is about the look on a co-founder's face across a kitchen table at 2 a.m. A story about closing a transformative deal is not about the contract. It is about the three-word text message sent to a spouse from a parking garage. + +Big themes land only through small, concrete details. The founder who says "we almost died as a company" connects with no one. The founder who describes eating ramen at a desk at midnight, watching the last $4,000 leave the account, and then receiving an email with a subject line that changed everything -- that founder makes the room hold its breath. + +--- + +## Prompts + +**Prompt 1 -- Elephant Identification:** +> I need to present [a pitch / an investor update / a company story] about [topic]. The key transformation or revelation is [describe it]. Help me craft an Elephant -- a clear, compelling statement of need, want, problem, or mystery -- that I can deliver within the first 30 seconds. The Elephant should make the audience desperate to hear what happens next. Also suggest how the Elephant's colour might change by the story's end. + +**Prompt 2 -- Backpack Construction:** +> I am telling the story of [a product launch / fundraising round / customer win]. Before the critical moment, I want to load my audience with my plans and hopes so they feel the weight of what follows. Help me articulate the plan, the expected outcome, and the emotional stakes in a way that makes the audience co-invest in the result. Then show me how the gap between plan and reality creates narrative tension. + +**Prompt 3 -- Full Stakes Audit:** +> Here is a narrative I plan to deliver: [paste draft or outline]. Audit it for stakes using the five techniques (Elephant, Backpack, Breadcrumbs, Hourglass, Crystal Ball). Identify where attention might wander. Recommend specific insertions of each technique at precise moments. Flag any "big story" moments that need to be made smaller and more personal. + +**Prompt 4 -- Hourglass Moment Design:** +> The climax of my story is [describe the key reveal or turning point]. Help me design an Hourglass moment around it: what sensory details can I add, what unnecessary-but-evocative description can I layer in, and how should I slow my pacing to maximise the tension just before the payoff? + +--- + +## Use Cases + +**Series A Pitch -- SaaS Founder** + +A founder pitching enterprise software opens with three minutes of product features. Attention drifts. Applying the framework: she opens with an Elephant ("Eighteen months ago, our largest customer called to say they were leaving -- and that call saved the company"). She uses a Backpack before describing the product pivot ("Our plan was simple: rebuild the entire integration layer in six weeks with a team of four"). She drops a Breadcrumb ("I still had the resignation letter in my drafts folder"). She deploys an Hourglass at the moment of product-market fit revelation, slowing down to describe the Slack message from the customer's CTO. The pitch transforms from a feature walkthrough into a story the room cannot leave. + +**All-Hands Address -- Post-Layoff** + +A CEO addresses a shaken team after a reduction in force. The big story (layoffs, financial pressure, survival risk) is inherently difficult to connect with at scale. The CEO makes it little: she describes a single conversation with a departing colleague, the specific object on his desk he packed last, and the sentence he said as he left. The Elephant is planted at the outset ("This morning I want to tell you about one conversation that changed how I think about what we owe each other"). The Crystal Ball appears mid-narrative ("I was certain he was going to be angry. I had rehearsed for anger"). The small moment carries the weight that the big narrative cannot. + +--- + +## Anti-Patterns + +- **The Missing Elephant.** Beginning a story with context, background, or credentials before establishing what is at stake. If the audience does not know why they are listening within the first minute, they have already stopped. Most failed pitches and company narratives suffer from this structural defect. + +- **The Perfect Plan.** Describing a strategy that executed flawlessly. The Backpack technique only works when the plan encounters friction. Audiences want suffering before triumph. A founder who describes a seamless journey from idea to traction sounds either dishonest or uninteresting. + +- **Rushing the Hourglass.** Sprinting through the most anticipated moment because the storyteller is eager to deliver the payoff. The payoff gains its power from delay. Rushing it is the narrative equivalent of lighting a firework indoors. + +- **Stacking Stakes Without Resolution.** Deploying Breadcrumbs, Crystal Balls, and Backpacks in rapid succession without ever paying them off. Each technique creates a promise to the audience. Broken promises erode trust faster than absent stakes erode attention. + +- **Confusing Big with Compelling.** Assuming that dramatic events automatically make good stories. The founder who says "we nearly went bankrupt" without finding the small, human, relatable moment inside the crisis tells a story nobody can connect to. Grand scale is not a substitute for personal specificity. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The Elephant is existential: does this problem matter? | Stakes must be borrowed from the customer's pain, since the company has no history to draw from yet | +| Validation | Backpacks and Crystal Balls dominate: plans are made, predictions tested | The narrative tension lives in the gap between hypothesis and evidence | +| Early Traction | Breadcrumbs become available as real customer stories accumulate | The storyteller can now hint at outcomes before revealing them, because outcomes exist | +| Growth | The Hourglass becomes critical for investor narratives and team alignment | Audiences are sophisticated; they need to be slowed down at key moments, not sped through them | +| Scale | Elephants must change colour: the company's story is no longer what it appears | The most powerful narratives at scale reveal that the real stakes were always something deeper than revenue | + +At the idea stage, founders frequently attempt to manufacture stakes through hyperbole ("This is a trillion-dollar market"). Manufactured stakes are transparent and counterproductive. Genuine stakes at this stage come from the founder's personal connection to the problem -- the small story hidden inside the big ambition. + +--- + +## Output Template + +```markdown +# Narrative Stakes Worksheet + +## Story Summary +[One sentence describing the story you intend to tell] + +## The Elephant +- **Core question planted for the audience:** [What need / want / problem / mystery?] +- **Appears by second:** [Target: within 30 seconds] +- **Colour change (if any):** [What the story appears to be about vs. what it is really about] + +## Backpack Moment(s) +- **Plan articulated before scene [X]:** [Describe the plan and hoped-for outcome] +- **Actual result:** [What happened instead] +- **Emotional gap:** [What the audience should feel] + +## Breadcrumbs +- **Hint dropped at [moment]:** [The detail revealed] +- **What it foreshadows:** [What the audience cannot yet guess] + +## Hourglass Moment +- **Scene to slow down:** [The most anticipated beat] +- **Details to add:** [Sensory, environmental, physical specifics] +- **Duration of delay:** [How many additional seconds / sentences] + +## Crystal Ball +- **False prediction stated at [moment]:** [What the storyteller expected] +- **Actual outcome:** [What happened instead] + +## Big-to-Little Check +- **The big event:** [What happened at macro level] +- **The small moment inside it:** [The specific, personal, relatable detail] +``` + +--- + +## Related Skills + +- **[Storytelling Truth and Vividness](../../content/skills/storytelling/storytelling-truth-and-vividness.md)** -- Stakes lose their power if the audience cannot see the story; vividness techniques ensure the Hourglass and Breadcrumbs land in a cinematic mental image. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- Stakes create tension; emotional impact techniques convert that tension into tears, laughter, or action at the moment of release. +- **[Story Performance and Delivery](../../content/skills/storytelling/story-performance-and-delivery.md)** -- Written stakes must be performed: pacing, tense shifts, and vocal control determine whether an Hourglass moment actually slows the room. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- The five-second moment provides the target that stakes build toward; without clear structure, even well-crafted stakes dissipate before the payoff. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- The leadership-application counterpart; focuses on when and why leaders deploy stories, whereas this skill addresses the craft of making them hold attention. +- **[Writing for Response](../../content/skills/writing/writing-for-response.md)** -- The Breadcrumbs technique for maintaining audience attention operates on the same cognitive principle as friction reduction in written calls to action: keep the reader moving forward. diff --git a/plugins/foreman/skills/building-thinking-strength/SKILL.md b/plugins/foreman/skills/building-thinking-strength/SKILL.md deleted file mode 120000 index c0dc4cd..0000000 --- a/plugins/foreman/skills/building-thinking-strength/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/building-thinking-strength.md \ No newline at end of file diff --git a/plugins/foreman/skills/building-thinking-strength/SKILL.md b/plugins/foreman/skills/building-thinking-strength/SKILL.md new file mode 100644 index 0000000..a6f0be4 --- /dev/null +++ b/plugins/foreman/skills/building-thinking-strength/SKILL.md @@ -0,0 +1,221 @@ +--- +name: "building-thinking-strength" +description: "Develops the four internal muscles required for clear thinking -- self-accountability, self-knowledge, self-control, and self-confidence -- using the Clear Thinking strength-building system. Covers setting personal standards above external requirements, choosing exemplars, building a personal board of directors, and practising in sandboxes. Use when blaming external factors for poor outcomes, struggling to say no under social pressure, lacking the confidence to execute a difficult decision, noticing that team standards have drifted toward mediocrity, or seeking a structured approach to personal operating system design." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - clear-thinking + - self-accountability + - self-knowledge + - self-control + - self-confidence + - personal-standards + - exemplars + - mental-models + - clear-thinking-framework + - deliberate-practice +related_skills: + - enemies-of-clear-thinking + - managing-weakness-and-mistakes + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-fortitude-and-resilience +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Building Thinking Strength + +FOUR PILLARS. Clear thinking requires four internal muscles -- and most people exercise none of them. The Clear Thinking framework moves beyond the diagnostic question (what hijacks your thinking?) to the constructive one (what makes thinking resistant to hijacking?). The answer is not intelligence, nor education, nor access to better information. The answer is four disciplines that function like load-bearing pillars: self-accountability, self-knowledge, self-control, and self-confidence. Remove any single pillar and the structure collapses under pressure. Strengthen all four and decisions begin to compound in the right direction, because the person making them has become structurally harder to deceive -- especially by themselves. + +The distinction from Kahneman's dual-process model is important. Kahneman describes the cognitive architecture -- fast and slow processing. The framework describes the character architecture -- the traits that determine whether a person can actually engage slow processing when it matters, or whether they will default to autopilot despite knowing better. Many founders can explain System 2 thinking fluently and still fail to practise it, because they lack the self-accountability to own their errors, the self-knowledge to see their blind spots, the self-control to resist the emotional impulse, or the self-confidence to act against consensus. Strength, not knowledge, is the bottleneck. + +--- + +## The Framework + +### Pillar 1: Self-Accountability + +Self-accountability is the practice of owning outcomes -- all of them -- regardless of whether external factors contributed. The formulation is deliberately uncompromising: "No one cares about your excuses as much as you do. In fact, no one cares about your excuses at all, except you." + +The concept is not about fault. A founder whose product launch fails because a cloud provider suffered a twelve-hour outage is not "at fault" for the outage. Self-accountability demands, however, that the founder own the response: what contingency plan should have existed, what communication should have been prepared, what architectural redundancy was neglected. The outage is not the founder's fault. The lack of preparation is. + +Three failure modes of low self-accountability: + +- **The excuse cascade.** Each explanation for a missed target contains a grain of truth -- the bus was late, the meeting overran, the competitor moved first -- but the cumulative effect is a narrative in which the founder is never the agent, only the victim. The antidote: "There is always something you can do in the moment today to better your position tomorrow." +- **The wrong side of right.** A founder who knows a co-founder's strategy is superior but champions their own because abandoning it would feel like admitting inadequacy. The ego default and low self-accountability form a feedback loop: each reinforces the other until outcome is sacrificed entirely for self-image. +- **Chronic victimhood.** The slow accumulation of responses that avoid responsibility, until blame becomes the default mode. The framework warns that the people who care most about chronic victims often make things worse by validating the blame narrative rather than challenging it. + +### Pillar 2: Self-Knowledge + +Self-knowledge is the accurate understanding of what you know, what you do not know, what you can do, and where your defaults are most likely to seize control. + +The text draws on Charlie Munger's principle: "When you play games where other people have the aptitude and you don't, you're going to lose. You have to figure out where you have an edge and stick to it." The size of what you know matters less than knowing its boundaries. + +For entrepreneurs, self-knowledge operates at two levels: + +- **Competence boundaries.** Knowing which market, technical, and operational domains you can evaluate with genuine expertise versus which ones you can only evaluate with borrowed confidence. A founder who reads three articles about enterprise sales and begins redesigning the go-to-market strategy has mistaken exposure for competence -- a confusion the ego default actively encourages. +- **Default triggers.** Knowing the specific conditions under which you are most susceptible to each default. One founder becomes impulsive when fatigued. Another becomes ego-defensive when challenged by someone they perceive as lower-status. A third capitulates to social pressure in board meetings but not in team meetings. Self-knowledge makes these patterns visible before they execute. + +### Pillar 3: Self-Control + +Self-control is the ability to create space between stimulus and response -- to experience the emotional impulse without being governed by it. + +The metaphor is precise: some people are corks bobbing on an emotional sea, their direction determined entirely by the current wave. Others seize the helm and steer despite the waves. Both experience the same sea. The difference is not the absence of emotion but the presence of agency. + +The practical dimensions of entrepreneurial self-control: + +- **Consistency over intensity.** Emotional intensity might launch a company; disciplined consistency builds one. The founder who maintains execution rhythm through a difficult quarter produces more value than the founder who sprints brilliantly for two weeks and collapses for three. +- **The present-versus-future trade.** The emotion default wants to win the present moment, even at the cost of sabotaging the future. Self-control is the discipline of asking the core question: "Will this action make the future easier or harder?" +- **Energy allocation.** Every unit of energy spent defending ego, repairing impulsive damage, or recovering from emotional reactions is a unit unavailable for progress. Self-control is ultimately an energy management strategy. + +### Pillar 4: Self-Confidence + +Self-confidence is not optimism, bravado, or the absence of doubt. It is the earned trust in one's ability to handle what comes -- including the hard truths. + +The framework draws a sharp line between confidence and ego. The ego default prevents acknowledging deficiencies. Self-confidence provides the strength to acknowledge them. Confidence without humility is overconfidence -- a weakness, not a strength. Confident people can say "I was wrong" because their identity is not contingent on being right. + +Two operational dimensions for founders: + +- **Outcome over ego.** The CEO who champions a rival's superior proposal -- and gets promoted for it -- exemplifies confidence that serves outcomes rather than self-image. The test: "If you owned 100 percent of this company and couldn't sell it for one hundred years, which solution would you prefer?" +- **The inner dialogue.** Self-confidence is partly a function of how you narrate your own history. Past adversity overcome is the raw material of future confidence. The founder who can say "I have navigated harder situations than this" is drawing on a genuine resource, not a motivational platitude. + +### Strength in Action: How the Pillars Compound + +No single pillar suffices. The text illustrates with a scenario: a founder susceptible to social pressure implements a 24-hour rule for all significant commitments. Creating that safeguard required self-knowledge (recognising the vulnerability), self-confidence (believing a better outcome is possible), self-accountability (deciding to act rather than accept the pattern), and self-control (enduring the short-term discomfort of delaying responses). Remove any pillar and the safeguard never gets implemented -- or collapses at first contact with reality. + +### Raising the Bar: Standards, Exemplars, and Practice + +The framework argues that strength development is fundamentally an environmental and imitative process, not a willpower exercise. + +**Standards.** "Champions don't create the standards of excellence. The standards of excellence create champions." The founder who tolerates mediocre work -- from themselves or their team -- is not suffering from a talent deficit but from a standards deficit. The Kissinger approach: refuse to engage with anything that is not the person's best work, and the standard becomes self-enforcing. + +**Exemplars and the Personal Board of Directors.** Choose role models -- living, dead, or fictional -- whose default behaviour is your desired behaviour. Place them on a mental "personal board of directors." Before significant decisions, ask: "What would [exemplar] do in this position? How would I present this decision to my board?" The exercise creates psychological distance from the defaults and activates aspirational rather than reactive thinking. Munger's standard -- "I never allow myself to have an opinion on anything unless I know the other side's argument better than they do" -- is the kind of bar that reshapes behaviour merely by being articulated. + +**Sandbox practice.** Test new behaviours in low-stakes environments before deploying them under pressure. A founder preparing for difficult board conversations might first practise the reframing discipline in weekly team meetings. Failure in the sandbox is cheap; failure in the boardroom is not. + +--- + +## Prompts + +**Prompt 1 -- Four-Pillar Audit:** +> Assess my current strength across the four pillars. Here is my recent behaviour and context: [describe 3-5 recent decisions, reactions, and outcomes]. For each pillar (self-accountability, self-knowledge, self-control, self-confidence), rate my demonstrated strength, identify the specific gap, and recommend one concrete practice to address it. Be candid -- I am looking for diagnosis, not encouragement. + +**Prompt 2 -- Personal Board of Directors Design:** +> Help me construct a personal board of directors. My current challenges are: [describe top 3 leadership challenges]. My weaknesses are: [describe known patterns]. Recommend 5-7 exemplars (living, historical, or fictional) whose specific traits would address these weaknesses. For each, describe what standard they would set and what question I should ask myself when imagining their perspective on my decisions. + +**Prompt 3 -- Standards Diagnostic:** +> Evaluate the standards operating in my company. Here is what "good enough" looks like in our current practice: [describe quality norms for 3-4 key activities -- code, customer communication, strategic planning, hiring]. Compare these to what excellence would look like in each area. Where is the largest gap between current standard and possible standard? What is the compounding cost of that gap over 12 months? + +**Prompt 4 -- Wrong-Side-of-Right Detection:** +> Review this decision I am defending: [describe the decision and your arguments for it]. Apply the "wrong side of right" test. Am I optimising for being right or for the best outcome? If I owned this company forever and could never sell it, would I still make this choice? Identify whether ego, social approval, or inertia is influencing my position, and describe what the outcome-over-ego alternative looks like. + +--- + +## Use Cases + +**Idea-Stage Founder Building Self-Knowledge Before Market Entry** + +A first-time founder with a data science background plans to enter the direct-to-consumer CPG market after reading case studies of successful DTC brands. Applying the self-knowledge pillar, an advisor asks the founder to map their competence boundaries: where do they have genuine expertise built through repeated practice with feedback, and where are they operating on borrowed confidence? The honest answer: deep expertise in analytics and modelling, zero expertise in supply chain, brand marketing, and retail distribution. Rather than abandoning the venture, the founder redesigns the team composition -- recruiting a co-founder with fifteen years of CPG operations experience and committing to a six-month learning period before making irreversible supply chain commitments. Self-knowledge did not shrink ambition; it restructured execution. + +**Early-Traction B2B Founder Whose Self-Accountability Deficit Is Eroding Team Trust** + +A B2B SaaS founder at $500K ARR has missed three consecutive quarterly targets. In each post-mortem, the narrative follows the same arc: market timing was off, a key prospect went dark, the engineering sprint encountered unexpected technical debt. Each explanation contains truth. The cumulative pattern, however, reveals a self-accountability deficit -- the founder is never the variable, only the context. A coach introduces the framework: "It's all your fault" is not a moral judgment but an operational stance. The founder begins post-mortems with the question "What did I personally contribute to this miss?" The shift is uncomfortable but transformative. Within two quarters, the founder identifies a recurring pattern of overcommitting to sales timelines without consulting engineering -- a fixable behaviour that was invisible under the previous blame-distribution model. + +**Growth-Stage CEO Using Exemplars to Raise Hiring Standards** + +A marketplace CEO at $8M ARR is struggling with inconsistent hiring quality. Some hires are exceptional; others are clearly below the bar. The CEO applies the exemplar framework, selecting three leaders renowned for hiring excellence as personal board members for this specific domain. Before each final-round interview, the CEO asks: "Would [exemplar] hire this person for this role?" The standard shifts from "this person seems good enough" to "this person meets the standard my exemplar would demand." Hiring quality stabilises within two cycles, and the CEO extends the exemplar practice to other domains -- product decisions, board communication, strategic planning -- creating a comprehensive aspirational benchmark system. + +--- + +## Anti-Patterns + +**1. Confusing self-accountability with self-blame.** The framework is about owning responses, not about psychological self-flagellation. A founder who takes accountability for a failed product launch does not spend weeks in self-recrimination; they extract the lesson, implement the change, and move forward. The distinction matters: self-blame is the ego default wearing a disguise of humility, consuming energy in performance of guilt rather than investing it in improvement. + +**2. Treating self-knowledge as a static inventory.** "I know my strengths and weaknesses" is a statement that should trigger immediate suspicion. Competence boundaries shift as markets evolve, new team members arrive, and the founder's own skills develop or atrophy. Self-knowledge is a continuous practice, not a completed exercise. The founder who assessed their capabilities at seed stage and has not updated the assessment at Series A is navigating with an outdated map. + +**3. Mistaking rigidity for self-control.** Self-control is the ability to choose response rather than react. It is not the elimination of emotion or the suppression of intuition. A founder who responds to every stimulus with robotic detachment has not achieved self-control; they have achieved emotional disconnection, which carries its own catastrophic failure modes -- particularly in people management and customer empathy. + +**4. Building a personal board of flatterers.** The exemplar framework fails if the selected role models are chosen for comfort rather than challenge. A board composed entirely of people who validate the founder's existing worldview provides social reinforcement, not standards elevation. The criterion is precise: exemplars should be people whose default behaviour is your desired behaviour, not people whose existing behaviour matches your current one. + +**5. Applying the framework only to others.** The four pillars are self-directed tools. A founder who diagnoses their team's lack of self-accountability while exempting themselves from the same scrutiny has missed the entire point. The system begins with the mirror, not the window. + +--- + +## By Stage + +| Stage | Pillar Priority | Key Difference | +|-------|----------------|----------------| +| Idea | Self-Knowledge + Self-Confidence | Founders need the self-knowledge to assess whether they have a genuine edge and the self-confidence to pursue a contrarian vision despite social pressure to "be realistic." | +| Validation | Self-Accountability + Self-Knowledge | Negative customer signals demand self-accountability (owning what the feedback means) and self-knowledge (distinguishing genuine insight from ego-protective dismissal). | +| Early Traction | Self-Control + Self-Accountability | The operational intensity of early traction tests self-control daily. Self-accountability prevents the pattern of externalising blame when early systems break. | +| Growth | All four + Standards | Growth exposes every pillar deficit. The leader's task shifts from personal strength to institutional standards -- building the environment where the team's default behaviour matches the desired behaviour. | +| Scale | Exemplars + Institutional Design | At scale, the CEO's personal pillars must become organisational architecture. Exemplar standards must be embedded in hiring criteria, performance systems, and decision protocols that outlast any individual. | + +At the idea and validation stages, the four pillars are deeply personal -- the founder against their own defaults. The critical intervention is building self-knowledge early, before the ego default has time to construct an elaborate self-narrative that becomes resistant to update. + +At growth and scale, the challenge becomes transmission. A CEO with strong personal pillars but no system for transmitting those standards produces an organisation that depends entirely on the CEO's presence -- a fragile structure. The insight that "what may look like discipline often involves a carefully created environment" points to the solution: design the environment so that the right behaviour is the easy behaviour, for the entire organisation, not just the founder. + +--- + +## Output Template + +```markdown +# Thinking Strength Assessment -- [Name / Role] + +**Date:** [Date] +**Context:** [Current stage, key challenges, recent decisions] + +## Four-Pillar Diagnostic + +| Pillar | Current Strength | Evidence | Primary Gap | Recommended Practice | +|--------|-----------------|----------|-------------|---------------------| +| Self-Accountability | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Knowledge | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Control | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | +| Self-Confidence | [Strong/Developing/Weak] | [Specific behaviours] | [Specific gap] | [One concrete action] | + +## Standards Assessment +- Current operating standard: [Description] +- Exemplar-level standard: [Description] +- Gap cost (annualised): [Estimated impact of the standards gap] + +## Personal Board of Directors + +| Exemplar | Domain | Standard They Set | Decision Test | +|----------|--------|-------------------|---------------| +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | +| [Name] | [Area] | [What bar they raise] | [Question to ask yourself] | + +## Wrong-Side-of-Right Check +- Decision most at risk of ego influence: [Description] +- 100-year ownership test result: [What changes if ego is removed] + +## 30-Day Strength-Building Plan +1. [Specific pillar + specific practice + specific frequency] +2. [Specific pillar + specific practice + specific frequency] +3. [Specific pillar + specific practice + specific frequency] +``` + +--- + +## Related Skills + +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- The diagnostic companion: identifies which defaults are active so the founder knows which pillar needs reinforcement. +- **[Managing Weakness and Mistakes](../../content/skills/thinking/managing-weakness-and-mistakes.md)** -- Completes the system by addressing what happens when strength is insufficient: safeguards for weakness and protocols for error recovery. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's cognitive architecture explains why the four pillars are necessary; without self-control and self-knowledge, System 2 engagement remains theoretical. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Translates the four pillars into daily decision habits, particularly the reframing techniques that require self-knowledge. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- Epictetus's dichotomy of control aligns with the self-knowledge pillar: knowing what you can and cannot influence is foundational to both frameworks. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- The Stoic discipline of endurance under adversity maps directly to the self-control and self-confidence pillars. diff --git a/plugins/foreman/skills/business-model-canvas/SKILL.md b/plugins/foreman/skills/business-model-canvas/SKILL.md deleted file mode 120000 index 420702b..0000000 --- a/plugins/foreman/skills/business-model-canvas/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/business-model-canvas.md \ No newline at end of file diff --git a/plugins/foreman/skills/business-model-canvas/SKILL.md b/plugins/foreman/skills/business-model-canvas/SKILL.md new file mode 100644 index 0000000..c8f1a10 --- /dev/null +++ b/plugins/foreman/skills/business-model-canvas/SKILL.md @@ -0,0 +1,245 @@ +--- +name: "business-model-canvas" +description: "Structures and evaluates business models using Osterwalder's + nine-block Business Model Canvas: Customer Segments, Value Propositions, + Channels, Customer Relationships, Revenue Streams, Key Resources, Key + Activities, Key Partnerships, and Cost Structure. Use when designing a new + venture, comparing business model alternatives, stress-testing assumptions, + planning pivots, exploring revenue model options, or identifying hidden + dependencies between business model components." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - business-model + - value-proposition + - startup-design + - strategy + - lean-methodology +related_skills: + - blue-ocean-strategy + - porters-five-forces +author: "Fatih Guner" +related_content: + - kind: template + ref: unit-economics-snapshot +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Business Model Canvas + +Business plans fail. Not occasionally -- systematically. Research from the Kauffman Foundation and others consistently demonstrates that the traditional 40-page business plan, once the mandatory admission ticket for venture funding, bears almost no correlation with startup success. The plans take months to write, become obsolete within weeks, and optimize for the wrong outcome: a polished document rather than a validated business. Alexander Osterwalder and Yves Pigneur, in *Business Model Generation* (2010), proposed a replacement: a single-page visual map that captures the nine essential building blocks of any business model. The Business Model Canvas (BMC) does not ask "how do we plan the business?" -- it asks "how does this business actually create, deliver, and capture value?" The shift from narrative to architecture, from plan to model, has reshaped how entrepreneurs think about building companies. + +--- + +## The Framework + +### The Nine Building Blocks + +The Canvas divides any business model into nine interdependent blocks, arranged spatially to reveal relationships: + +``` +┌──────────────┬───────────────┬───────────────┬───────────────┬──────────────┐ +│ │ │ │ │ │ +│ KEY │ KEY │ VALUE │ CUSTOMER │ CUSTOMER │ +│ PARTNERS │ ACTIVITIES │ PROPOSITIONS│ RELATIONSHIPS│ SEGMENTS │ +│ │ │ │ │ │ +│ Who are our │ What key │ What value │ What type of │ For whom │ +│ key │ activities │ do we │ relationship │ are we │ +│ partners │ does our │ deliver? │ does each │ creating │ +│ and │ value prop │ │ segment │ value? │ +│ suppliers? │ require? │ │ expect? │ │ +│ ├───────────────┤ ├───────────────┤ │ +│ │ │ │ │ │ +│ │ KEY │ │ CHANNELS │ │ +│ │ RESOURCES │ │ │ │ +│ │ │ │ Through │ │ +│ │ What key │ │ which │ │ +│ │ resources │ │ channels do │ │ +│ │ does our │ │ our segments │ │ +│ │ value prop │ │ want to be │ │ +│ │ require? │ │ reached? │ │ +│ │ │ │ │ │ +├──────────────┴───────────────┴───────┬───────┴───────────────┴──────────────┤ +│ │ │ +│ COST STRUCTURE │ REVENUE STREAMS │ +│ │ │ +│ What are the most important costs │ For what value are customers │ +│ inherent in our business model? │ willing to pay? │ +│ │ │ +└──────────────────────────────────────┴──────────────────────────────────────┘ +``` + +### Block-by-Block Guide + +**1. Customer Segments** -- The distinct groups of people or organizations the business serves. Segments differ when they require distinct value propositions, are reached through different channels, require different types of relationships, yield different profitability profiles, or are willing to pay for different aspects of the offering. The decision of which segments to serve -- and which to ignore -- is the most consequential strategic choice on the canvas. + +**2. Value Propositions** -- The bundle of products and services that create value for a specific customer segment. Value may derive from newness, performance, customization, design, brand/status, price, cost reduction, risk reduction, accessibility, or convenience. The value proposition is the reason a customer chooses one company over another. + +**3. Channels** -- How the company communicates with and reaches its customer segments to deliver value. Channels include direct (sales force, web, stores) and indirect (partner stores, wholesalers). The channel question is not just "how do we reach customers?" but "how do customers want to be reached?" + +**4. Customer Relationships** -- The type of relationship established with each segment: personal assistance, dedicated personal assistance, self-service, automated services, communities, or co-creation. The relationship type affects customer acquisition cost, retention rate, and lifetime value. + +**5. Revenue Streams** -- The cash generated from each customer segment. Revenue model types include asset sales, usage fees, subscription fees, licensing, brokerage fees, and advertising. Two fundamental pricing mechanisms exist: fixed (list prices, feature-dependent, segment-dependent) and dynamic (negotiation, yield management, real-time market pricing). + +**6. Key Resources** -- The most important assets required to make the business model work: physical, intellectual (patents, proprietary knowledge, data), human, or financial. Key resources are those without which the value proposition cannot be delivered. + +**7. Key Activities** -- The most important things the company must do to make the business model work. Categories include production (designing, making, delivering), problem solving (consulting, engineering), and platform/network management (maintaining and developing the platform). + +**8. Key Partnerships** -- The network of suppliers and partners that make the business model work. Partnership motivations include optimization and economy of scale, reduction of risk and uncertainty, and acquisition of particular resources and activities. + +**9. Cost Structure** -- All costs incurred to operate the business model. Two broad classes: cost-driven (minimizing cost wherever possible) and value-driven (focused on value creation with less concern for cost). Key cost characteristics to identify: fixed vs. variable, economies of scale, and economies of scope. + +### The Canvas as a System + +The nine blocks are not independent -- they form a system of interdependencies. The left side of the canvas (partners, activities, resources, costs) represents the infrastructure of value creation. The right side (segments, relationships, channels, revenue) represents value delivery and capture. The value proposition sits at the center, connecting creation to delivery. + +A change in any block ripples across the canvas. Adding a new customer segment may require new channels, different relationships, additional resources, and altered cost structure. This systemic view is the canvas's greatest strength: it makes hidden dependencies visible. + +### Canvas Patterns + +Osterwalder and Pigneur identify recurring business model patterns: + +- **Unbundled**: Separating product innovation, customer relationship management, and infrastructure into distinct models +- **Long Tail**: Selling less of more -- many niche products rather than a few bestsellers +- **Multi-Sided Platform**: Connecting two or more interdependent customer groups (e.g., buyers and sellers) +- **Free/Freemium**: At least one segment receives value for free, subsidized by another segment or revenue stream +- **Open**: Collaborating with external partners to create or capture value + +--- + +## Prompts + +**Prompt 1 -- Complete Canvas Build:** +> Help me build a complete Business Model Canvas for my venture. My concept is [describe your business idea, target market, and core offering]. For each of the nine blocks, provide specific, actionable content -- not generic descriptions. Challenge my assumptions: where am I making implicit choices that should be explicit? Where are there dependencies between blocks that I might be overlooking? Present the completed canvas as a structured document with each block clearly defined. + +**Prompt 2 -- Canvas Comparison (Current vs. Target):** +> I want to compare my current business model with a target business model. Here is my current canvas: [describe or paste current model]. Here is where I want to be in 18 months: [describe target state]. Map both canvases side by side and identify: (1) Which blocks need to change? (2) What is the sequence of changes -- which block moves first? (3) What are the riskiest transitions? (4) What are the dependencies that could block the transition? + +**Prompt 3 -- Canvas Stress Test:** +> Stress-test my Business Model Canvas. My current canvas is: [describe or paste]. For each block, identify the riskiest assumption -- the one that, if wrong, would break the model. Then prioritize these assumptions by impact and uncertainty. Finally, recommend the cheapest experiment I could run to test each of the top 3 riskiest assumptions. + +**Prompt 4 -- Revenue Model Exploration:** +> My value proposition is [describe] serving [customer segment]. Explore alternative revenue models using the Canvas framework. For each model (subscription, usage-based, freemium, transaction fee, licensing, advertising, data monetization), assess: (1) Fit with my value proposition, (2) Customer willingness to pay, (3) Impact on other canvas blocks (channels, relationships, costs), (4) Long-term scalability. Recommend the top 2-3 revenue models with rationale. + +**Prompt 5 -- Partnership and Resource Gap Analysis:** +> Review my Business Model Canvas: [describe]. Identify gaps in key resources and key activities that I cannot fill internally. For each gap, recommend: (1) Build vs. partner vs. acquire, (2) Specific potential partners or providers, (3) Partnership structure (strategic alliance, joint venture, buyer-supplier, co-opetition), (4) Risks of dependency and how to mitigate them. + +--- + +## Use Cases + +**Idea-Stage Founder Testing Three Business Concepts** +A founder with domain expertise in healthcare logistics has three potential business ideas. Rather than writing business plans for each, she builds three canvases in a single afternoon. The canvas exercise reveals that Concept A requires a regulatory resource she does not have and cannot easily acquire. Concept B has strong value proposition-segment fit but no viable revenue stream at the target price point. Concept C has a clear path across all nine blocks, with the key risk concentrated in one testable assumption: whether hospital procurement departments will adopt a self-service purchasing tool. The canvas did not make the decision -- it made the decision visible. + +**Validation-Stage Startup Discovering a Pivot** +A B2C fitness app with 10,000 free users and negligible paid conversion maps its current canvas and discovers that its actual value creation is concentrated in the community features (customer relationships block), not the workout content (value proposition block). The paying users pay for community, not content. The canvas pivot: shift the value proposition from "personalized workouts" to "accountability communities," change the revenue stream from subscription to cohort-based pricing, and redesign channels around referral rather than performance marketing. The canvas reveals that the business model the customers are buying is different from the one the founder is selling. + +**Growth-Stage Platform Company Navigating Multi-Sided Economics** +A marketplace connecting freelance designers with small businesses maps its canvas and discovers an asymmetry: the value proposition for designers (access to clients) is strong, but the value proposition for businesses (access to quality design) is weakening as the platform grows and quality becomes inconsistent. The canvas highlights that the key activity of quality curation -- initially performed manually by the founder -- has not scaled. The solution: invest in the key activity of algorithmic quality matching, add a key resource of portfolio review capability, and create a new revenue stream (premium placement for top-rated designers) that aligns incentives with quality. + +--- + +## Anti-Patterns + +1. **Filling the canvas once and treating it as finished.** The Canvas is a living document that evolves as assumptions are tested and conditions change. A canvas completed at the idea stage should look materially different six months later. If it does not, either the business has stagnated or the canvas is not being used. + +2. **Making the canvas too abstract.** "Our customer segment is SMBs" is not useful. "Our customer segment is marketing directors at B2B SaaS companies with 50-200 employees who currently manage campaigns in spreadsheets" is useful. Specificity in each block is what transforms the canvas from a strategy exercise into an operational guide. + +3. **Ignoring the left side of the canvas.** Entrepreneurs obsess over value propositions, customers, and revenue -- the right side. The left side (resources, activities, partners, costs) is where execution lives. A brilliant right side with an unworkable left side produces a business that cannot be built. + +4. **Assuming one canvas serves all segments.** Different customer segments often require different canvases. A freemium product has one canvas for free users and a different one for paying users. A marketplace has separate canvases for each side. Collapsing distinct models into a single canvas hides the structural differences that matter most. + +5. **Treating the canvas as a replacement for financial modeling.** The canvas reveals the architecture of the business model; it does not quantify it. Revenue streams, cost structure, and unit economics require separate, rigorous financial analysis. The canvas tells you what to model; the financial model tells you whether the numbers work. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Hypothesis generation | Every block is an assumption. The canvas at this stage is a hypothesis document, not a description of reality. The goal is to identify the riskiest assumptions and sequence experiments to test them. Multiple canvases for different concepts enable rapid comparison. | +| Validation | Assumption testing | Systematically validate each block through customer discovery, prototypes, and landing page tests. The canvas evolves as assumptions are confirmed or refuted. Focus on the value proposition and customer segment blocks first -- these determine whether the other seven blocks matter. | +| Early Traction | Model refinement | Product-market fit is emerging. The canvas shifts from hypothesis to documented reality: which segments are actually buying, through which channels, at what price. Gaps between the planned canvas and the actual canvas reveal where the model needs adjustment. | +| Growth | Scaling infrastructure | The left side of the canvas becomes critical. Key resources, activities, and partnerships must scale to support growing demand. Cost structure optimization begins. The canvas helps identify which blocks are scaling smoothly and which are bottlenecks. | +| Scale | Model extension and defense | New customer segments, geographies, or product lines each require canvas extensions or entirely new canvases. The framework helps evaluate whether extensions leverage existing blocks or require building new ones. Defensive canvases map how the current model would respond to competitive or market disruptions. | + +--- + +## Output Template + +```markdown +# Business Model Canvas + +**Venture:** [Name] +**Version:** [v1.0 / v2.0 / etc.] +**Date:** [Date] +**Stage:** [Current stage] + +## Customer Segments +- **Primary:** [Specific description] +- **Secondary:** [Specific description] + +## Value Propositions +- **For [Segment 1]:** [Specific value delivered] +- **For [Segment 2]:** [Specific value delivered] + +## Channels +- **Awareness:** [How customers discover us] +- **Evaluation:** [How customers evaluate our offering] +- **Purchase:** [How customers buy] +- **Delivery:** [How we deliver value] +- **After-sales:** [How we provide post-purchase support] + +## Customer Relationships +- **[Segment 1]:** [Relationship type and description] +- **[Segment 2]:** [Relationship type and description] + +## Revenue Streams +- **[Stream 1]:** [Model type] -- [Pricing mechanism] -- [Expected contribution %] +- **[Stream 2]:** [Model type] -- [Pricing mechanism] -- [Expected contribution %] + +## Key Resources +- **Physical:** [If applicable] +- **Intellectual:** [Patents, data, brand, proprietary knowledge] +- **Human:** [Key roles and expertise] +- **Financial:** [Funding, credit lines] + +## Key Activities +1. [Critical activity for value delivery] +2. [Critical activity for value delivery] +3. [Critical activity for value delivery] + +## Key Partnerships +- **[Partner type]:** [Who and why] +- **[Partner type]:** [Who and why] + +## Cost Structure +- **Fixed costs:** [List major items] +- **Variable costs:** [List major items] +- **Cost model:** [Cost-driven / Value-driven] + +## Riskiest Assumptions +1. [Assumption] -- Block: [Which block] -- Test: [How to validate] +2. [Assumption] -- Block: [Which block] -- Test: [How to validate] +3. [Assumption] -- Block: [Which block] -- Test: [How to validate] +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- The ERRC Grid reshapes the value proposition block; the Canvas maps the complete business model required to deliver the blue ocean strategy. +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Five Forces reveals the industry structure the business model must navigate; the Canvas designs the model while Five Forces evaluates the competitive terrain it operates in. +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- The Canvas's right side (segments, channels, relationships, revenue) expands into the full marketing mix of Product, Price, Place, and Promotion for go-to-market execution. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- PEST identifies macro forces that constrain or enable the Canvas's assumptions, while SWOT reveals which blocks represent genuine competitive advantages. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Christensen's theory explains when a Canvas designed for underserved segments can grow to challenge incumbents whose business models cannot adapt. +- **[Ambidexterity](../../content/skills/frameworks/ambidexterity.md)** -- Exploration units should build separate canvases from the core business, making the two-canvas approach a practical tool for structurally ambidextrous organizations. diff --git a/plugins/foreman/skills/business-writing-for-leaders/SKILL.md b/plugins/foreman/skills/business-writing-for-leaders/SKILL.md deleted file mode 120000 index 5d7b732..0000000 --- a/plugins/foreman/skills/business-writing-for-leaders/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/business-writing-for-leaders.md \ No newline at end of file diff --git a/plugins/foreman/skills/business-writing-for-leaders/SKILL.md b/plugins/foreman/skills/business-writing-for-leaders/SKILL.md new file mode 100644 index 0000000..92d0bed --- /dev/null +++ b/plugins/foreman/skills/business-writing-for-leaders/SKILL.md @@ -0,0 +1,171 @@ +--- +name: "business-writing-for-leaders" +description: "Sharpens leadership writing through four principles: write for the reader, lead with clarity, keep it simple, and sound human. Use when drafting company-wide announcements, writing investor updates, composing emails that require action, editing team communications for clarity, or noticing that written messages consistently generate confusion or non-response." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - communication + - clarity + - email + - announcements + - simplicity +related_skills: + - psychological-safety-practice + - persuasion-and-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Business Writing for Leaders + +DELETE KEY. The most powerful writing tool a leader possesses is subtraction. Every unnecessary word dilutes authority. Every jargon-laden sentence signals that the writer is performing competence rather than demonstrating it. Every buried lead -- the critical information hidden in paragraph three -- is a tax on the reader's time and goodwill. Yet leaders write more words each year, to more people, through more channels, with less editing and less consideration for the person on the receiving end. The average executive sends and receives over 120 emails per day. The ones that get read, understood, and acted upon share a common trait: their authors wrote for the reader, not for themselves. + +Researchers and practitioners writing across a decade of HBR publications converge on a conclusion that should embarrass anyone who has ever used the phrase "synergistic value proposition" in an email: good business writing is simple, clear, human, and structured around what the reader needs to know, not what the writer wants to say. + +--- + +## The Framework + +Leadership writing rests on four principles. They are deceptively simple. Executing all four simultaneously, under time pressure, with multiple audiences, is considerably harder than any writing guide admits. + +### Principle 1: Write for the Reader + +The discipline begins with a shift in orientation. Before writing a sentence, answer three questions: + +- **What does the reader need to know?** Not what you want to tell them. What they need. +- **What questions will they have?** Anticipate and address them in order of likely importance. +- **How much time will they give this?** Assume less than you hope. Probably less than you think. + +Respect for the reader's time is not a courtesy; it is a structural requirement. Put the most important information first. The reader who stops after the first paragraph should still have the essential message. The reader who continues should find supporting detail, not repetition. + +Picture your audience as intelligent novices: smart, capable of grasping complex ideas, but not fluent in your department's acronyms, your industry's jargon, or your project's internal shorthand. Define technical terms on first use. Avoid abbreviations unless they are universally understood. The test is whether someone outside your team would understand every sentence without a glossary. + +### Principle 2: Lead with Clarity + +Three structural practices separate clear writing from unclear writing: + +**Get to the point.** Lead with your core idea. Provide context to support it. Cut everything else. The common failure is inversion: context first, supporting detail second, the actual point last. By the time the reader reaches it, attention has dissipated. + +**Use topic sentences that forecast.** The first sentence of each paragraph should tell the reader what the paragraph is about -- not merely describe a detail. Compare: "I met with the client in Berlin" (descriptive, no signal) versus "My meeting with the Berlin client focused on plans for future growth" (forecasting, contextual). The second sentence earns the reader's continued attention by promising relevance. + +**Use active voice.** "Juan improved the project's results" is clear. "The project's results were improved" is evasive -- it hides agency, removes accountability, and requires more words to say less. Passive voice has legitimate uses (when the actor is unknown or deliberately unimportant), but it should be a conscious choice, not a default. + +### Principle 3: Keep It Simple + +Overblown language does not signal intelligence. It signals insecurity. The writer who uses "leverage" when they mean "use," "ideate" when they mean "think," or "robust solution" when they mean "good answer" is not communicating -- they are decorating. + +Practical simplification: + +- **Use short, familiar words.** "Begin" rather than "commence." "End" rather than "terminate." "Use" rather than "utilise." +- **Use short sentences.** If a sentence contains more than one idea, it should probably be two sentences. +- **Use short paragraphs.** A paragraph crammed with four ideas forces the reader to parse structure and content simultaneously. One idea per paragraph. Two at most. +- **Use formatting as a tool.** Headings, bullet points, bold text, and numbered lists allow readers to scan for relevance. Most business writing will be read on a phone, possibly while the reader is walking, eating, or sitting in another meeting. Write for that reality, not for the undivided attention you wish you had. + +### Principle 4: Sound Human + +The gap between how leaders write and how leaders speak is, in most organisations, unnecessarily wide. Written communication that sounds like it was produced by a committee -- or by a language model prompted to "sound professional" -- creates distance where connection is needed. + +Three practices: + +- **Use first person.** "I recommend" and "We accomplished" are personal and direct. "The company achieved" and "It has been determined" are bureaucratic and evasive. Readers trust people. They distrust institutions that refuse to identify a human behind the words. +- **Start sentences with verbs and conjunctions.** "Get the report to me by Friday." "But that approach has a flaw." "And here is why it matters." These constructions mirror natural speech patterns and create momentum. They are grammatically correct despite what certain style guides claim. +- **Read aloud.** The most reliable test of whether writing sounds human: say it out loud. If a sentence sounds awkward spoken, it will sound awkward read. If a phrase would never leave your mouth in conversation, it should not appear in your writing. + +--- + +## Prompts + +**Prompt 1 -- Writing Audit:** +> Here is a piece of business writing I recently sent: [paste the full text]. Audit it against four principles: reader orientation, clarity of structure, simplicity of language, and human voice. For each principle, score it on a 5-point scale and provide specific examples of where it succeeds and fails. Then rewrite the weakest sections. + +**Prompt 2 -- Email Rewrite:** +> I need to send this email: [describe the situation, the audience, and the key message]. Draft it in under 150 words, leading with the core message, using active voice, avoiding jargon, and sounding like a human wrote it. Then provide a version for a different audience: [describe the second audience]. + +**Prompt 3 -- Announcement Draft:** +> I need to announce [describe the news -- positive or negative] to [describe the audience]. The key facts are: [list]. The likely questions are: [list]. Draft an announcement that leads with the most important information, anticipates reader questions, uses simple language, and maintains an honest, human tone. Keep it under 250 words. + +**Prompt 4 -- Jargon Elimination:** +> Here is a document filled with jargon and corporate language: [paste text]. Rewrite every sentence using the simplest possible language without losing meaning. Flag any instances where jargon was actually doing useful work (i.e., a technical term that has no simpler equivalent) and keep those. + +--- + +## Use Cases + +**Validation-Stage Founder Writing an Investor Update** +A founder sends monthly investor updates that consistently go unread. An audit reveals the problem: updates open with three paragraphs of context before reaching the key metrics. Investors, who receive dozens of portfolio updates per month, stop reading after paragraph one. The rewrite leads with a three-line summary (revenue, burn, key milestone), follows with a five-bullet section on progress and challenges, and closes with a specific ask. Open rates double. Response rates triple. The content did not change -- the structure did. + +**Growth-Stage VP Sending a Restructuring Email** +A VP of Operations needs to announce a team restructuring that will affect 40 people. The first draft, reviewed against the four principles, is 800 words, opens with corporate preamble ("As we continue to evolve our organisational capabilities..."), buries the actual changes in paragraph four, and uses passive voice throughout ("roles will be affected" -- by whom?). The rewrite opens with the change ("Effective March 1, Teams A and B will merge under [Name]"), explains the reasoning in two sentences, details what this means for each person's role in a bulleted list, and closes with a specific invitation: "I will hold office hours on Thursday and Friday to answer your questions directly." Active voice. Human tone. Half the length. + +--- + +## Anti-Patterns + +1. **Writing to Impress, Not to Communicate.** The leader who uses complex vocabulary and elaborate sentence structures to signal intelligence. The reader does not conclude "this person is brilliant." The reader concludes "this person made me work harder than necessary to understand a simple point." Sophistication in writing is the ability to make complex ideas simple, not simple ideas complex. + +2. **The Reply-All Essay.** Responding to a two-line question with a 500-word treatise. Match the length and formality of your response to the communication that prompted it. Escalating register signals that you are performing, not communicating. + +3. **Editing by Addition.** Reviewing a draft and making it longer. In nearly every case, the most productive edit is deletion. Remove the sentence that repeats the previous one. Remove the paragraph that qualifies a point the reader did not need qualified. Remove the adjective that adds nothing. + +4. **Template Dependence.** Using the same format for every communication regardless of audience, context, or message. A team update, an investor email, and a disciplinary notice require different structures, different tones, and different lengths. Templates are a starting point, not a destination. + +5. **Delegating Voice.** Having someone else write communications that carry the leader's name without reviewing them for tone and voice. Readers develop a model of who the leader is through their writing. Inconsistency between spoken and written voice -- or between one email and the next -- erodes trust. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch writing | Every written word is selling -- the vision, the opportunity, the founder's credibility. Clarity and human voice are the primary differentiators because the founder has no brand to lend authority. | +| Validation | Customer and investor communication | Writing must translate technical complexity into accessible language for non-expert audiences. The intelligent-novice rule applies with particular force. | +| Early Traction | Internal communication at scale | The founder transitions from writing to five people to writing to fifty. Structure and formatting become essential because the audience can no longer be assumed to have full context. | +| Growth | Organisational voice | Writing sets culture. How the leadership team communicates -- the clarity, the honesty, the simplicity -- becomes the template that the entire organisation replicates. | +| Scale | Delegation and consistency | The leader writes less personally and reviews more writing by others. The skill shifts from writing well to editing well and coaching others to write well. | + +--- + +## Output Template + +```markdown +# Communication Draft: [Subject] + +## Pre-Writing Check +- Reader: [who will read this] +- Reader's primary question: [what they need to know] +- Reader's available attention: [how much time they will give this] +- Required action: [what the reader should do after reading] + +## Draft +[The communication, structured with the core message first, supporting detail second, and a clear call to action] + +## Self-Audit +- [ ] Core message in the first two sentences +- [ ] Active voice throughout (passive voice used only deliberately) +- [ ] No unexplained jargon or acronyms +- [ ] Every paragraph begins with a topic sentence +- [ ] Read aloud -- sounds human +- [ ] Length appropriate to the audience and channel +``` + +--- + +## Related Skills + +- **[Writing with Purpose](../../content/skills/writing/writing-with-purpose.md)** -- Defines the foundational technique for determining what to say and why before drafting, which directly supports the leader's principle of writing for the reader. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- Provides the sentence-level editing techniques that operationalise Principle 3's mandate to keep it simple and cut unnecessary words. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Addresses the tonal calibration that makes Principle 4 actionable: sounding human without losing authority across different audiences. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- Writing is a persuasion medium; the principles of reading the room and establishing authority organically apply in written form as much as in spoken interaction. +- **[Psychological Safety in Practice](../../content/skills/leadership/psychological-safety-practice.md)** -- How leaders write about mistakes, setbacks, and difficult news directly affects whether team members feel safe to surface problems. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Narrative techniques transform announcements and updates from information dumps into compelling communications that land with readers. diff --git a/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md b/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md deleted file mode 120000 index 655d6e5..0000000 --- a/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/career-strategy-for-leaders.md \ No newline at end of file diff --git a/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md b/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md new file mode 100644 index 0000000..4a5c003 --- /dev/null +++ b/plugins/foreman/skills/career-strategy-for-leaders/SKILL.md @@ -0,0 +1,190 @@ +--- +name: "career-strategy-for-leaders" +description: "Guides leaders through deliberate career design -- calculating timelines, auditing career fuel, breaking career-limiting habits, avoiding success traps, and aligning trade-offs with evolving values. Use when a leader feels stuck, faces a career crossroads, suspects their success has become a cage, needs to break a recurring bad habit, or wants to shift from reactive career drift to intentional career architecture." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - career-planning + - success-traps + - habits + - self-management + - growth-mindset + - career-fuel + - trade-offs +related_skills: + - growth-mindset + - covey-seven-habits + - eisenhower-matrix + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Career Strategy for Leaders + +CROSSROADS. Most leaders arrive at one sometime between their tenth and twentieth year of management. The recognition is uncomfortable: their career happened to them. Promotions arrived because they were competent, not because they were strategic. Opportunities materialized through proximity, not design. Titles accumulated like sediment -- layers of accidental geology rather than intentional architecture. The leader who never planned a career trajectory is not unusual; they are the statistical norm. Brian Fetherstonhaugh's research for HBR suggests that the majority of professionals dramatically underestimate how long their careers will last, which means they under-invest in the skills, relationships, and experiences that sustain performance across decades. A career without strategy is not a career. It is an extended reaction to whatever happens next. + +The antidote is not a five-year plan pinned to the wall. It is a set of recurring practices -- honest self-assessment, deliberate habit management, resistance to the seductions of past success -- that transform career drift into career design. + +--- + +## The Framework + +Career strategy for leaders operates across four interlocking dimensions. None functions in isolation; neglecting any one dimension eventually undermines the others. + +### 1. Timeline Awareness + +Most leaders assume their career is roughly half over when in reality it has decades remaining. The first discipline of career strategy is calculating -- with uncomfortable specificity -- how many working years remain. Factor in retirement age norms, industry velocity, health trajectories, and financial requirements. Leaders who confront their actual timeline make qualitatively different decisions about what to invest in next. A leader with thirty years remaining cannot afford to coast on a single expertise domain. A leader with five years remaining cannot afford to defer the work they actually care about. + +### 2. Career Fuel Audit + +Three resources sustain a career across its full arc: + +| Fuel Type | Definition | Depletion Signal | +|-----------|-----------|------------------| +| **Transportable skills** | Capabilities that transfer across roles, industries, and organisations | You can only describe your value in terms of your current job title | +| **Meaningful experiences** | Assignments that stretched capacity, expanded perspective, or built judgment | Your last three years feel interchangeable | +| **Enduring relationships** | Connections that provide insight, access, candour, and support | Your professional network is a single company's org chart | + +The audit is blunt: are these fuel levels growing, stagnating, or declining? Growth does not require changing jobs. A special assignment, a cross-functional rotation, an expanded remit, or structured learning within the current organisation can replenish all three tanks. + +### 3. Success Trap Identification + +Success creates its own gravity. Rosabeth Moss Kanter's research identifies five barriers that high performers erect around themselves: + +- **Impatience.** Accomplished problem-solvers develop an addiction to quick resolution that fails them on complex, systemic challenges. +- **Narrow expertise.** Deep domain knowledge becomes a prison when every problem is viewed through a single disciplinary lens. +- **Intellectual arrogance.** The inability to say "I don't know" calcifies as seniority rises and the people around you stop challenging your conclusions. +- **Echo chambers.** Success attracts agreement. Leaders surrounded by people who never dissent begin to mistake consensus for correctness. +- **Title attachment.** Defining identity through a job title narrows collaboration and alienates the cross-functional contributors whose help complex problems demand. + +Each trap is a direct consequence of competence. That is what makes them dangerous -- they masquerade as strengths. + +### 4. Habit Architecture + +Career-limiting habits persist because the environment rewards them -- or at least fails to punish them. Crucial Learning research identifies five levers for dismantling bad habits and installing productive ones: + +1. **Manage distance.** Physically separate from temptations and bring helpful stimuli closer. Procrastinators should work in isolation rooms. Leaders who want to read industry analysis should replace social media bookmarks with those sources. +2. **Reframe language.** Replace "I won't" with "I can't" (increases psychological resistance) and "I have to" with "Why do I want to?" (reconnects with intrinsic motivation). +3. **Change your social environment.** Spend more time with people who model the behaviours you want to cultivate. Social circles shape attitudes more than willpower does. +4. **Schedule defaults.** Put the desired behaviour on the calendar. Humans honour pre-committed time far more reliably than spontaneous intention. +5. **Train incrementally.** Identify one micro-skill per week and one situation in which to practise it. Competence builds motivation, not the reverse. + +### 5. The Four-Question Self-Grade + +Periodically -- annually at minimum -- grade the current situation against four criteria: Am I learning? Am I having impact? Am I having fun? Am I being rewarded? If three of four answers are negative, the problem is structural, not attitudinal. If one answer is negative, targeted action within the current role may suffice. + +--- + +## Prompts + +**Prompt 1 -- Career Timeline Calculation:** +> Calculate my realistic career timeline. I am [age], in [industry], with [describe financial situation]. Factor in industry retirement norms, my health considerations, potential part-time work, and financial requirements. Then identify the three most important investments I should make in the next five years given this timeline. Be specific -- not "learn new skills" but what skills and why. + +**Prompt 2 -- Career Fuel Audit:** +> Audit my career fuel. Here are my transportable skills: [list]. My meaningful experiences in the past five years: [list]. My enduring professional relationships: [describe network]. For each fuel type, assess whether I am growing, stagnating, or declining. Then recommend three specific actions to replenish the weakest fuel tank without changing employers. + +**Prompt 3 -- Success Trap Diagnostic:** +> Evaluate me against the five success traps: impatience, narrow expertise, intellectual arrogance, echo chambers, and title attachment. Here is my current role: [describe]. Here is how I typically approach complex problems: [describe]. Here is how I respond to disagreement: [describe]. Identify which traps I am most vulnerable to, provide specific evidence from my descriptions, and recommend one countermeasure for each. + +**Prompt 4 -- Career-Limiting Habit Intervention:** +> I have a career-limiting habit: [describe the habit in detail]. Design an intervention using all five levers: distance management, language reframing, social environment change, scheduled defaults, and incremental training. Make each lever specific to my habit and my work context: [describe context]. + +--- + +## Use Cases + +**Growth-Stage Founder Approaching Year Eight** +A SaaS founder has built a company from zero to 120 employees. Every skill they developed -- fundraising, early-stage hiring, product-market-fit iteration -- is an early-stage skill. The company now needs a scale-stage operator, and the founder recognises they have been coasting on the reputation of early success. A career fuel audit reveals stagnating transportable skills (nothing new learned in three years) and a relationship network entirely composed of Series A investors and fellow early-stage founders. The intervention: join a CEO peer group with leaders running 500+ person organisations, take on a board seat at a larger company for exposure, and hire a COO to create space for personal skill development. + +**Senior Vice President Hitting the Success Trap** +A VP of Engineering at a mid-sized enterprise has been promoted four times in twelve years. Every promotion reinforced the same approach: deep technical expertise, fast problem resolution, authoritative decision-making. Now leading a cross-functional transformation programme, they find that impatience alienates programme partners, narrow technical framing misses organisational dynamics, and the inability to say "I don't know" prevents learning from non-engineering disciplines. The success trap diagnostic reveals three of five traps are active. The countermeasures: assign a cross-functional deputy to co-lead (breaking the expertise prison), institute a "what am I wrong about?" weekly reflection (disrupting intellectual arrogance), and schedule monthly lunches with leaders from marketing, finance, and operations (expanding the network beyond the echo chamber). + +**Mid-Career Manager Facing a Trade-Off Reassessment** +A director of product with two young children grades their current role: learning (yes, marginally), impact (yes), fun (no), rewarded (yes, financially). The single "no" has been persistent for two years. A trade-off audit reveals that the role demands 60-hour weeks and constant travel -- trade-offs that were acceptable before children and are no longer aligned with evolving values. Rather than quitting, the intervention identifies a lateral move within the same company to a product strategy role with equivalent compensation, higher learning, and 30% less travel. + +--- + +## Anti-Patterns + +1. **The Annual Review as Career Strategy.** Treating a manager's performance review as a career planning exercise confuses short-term performance feedback with long-term trajectory design. Performance reviews optimise for the current role. Career strategy optimises for the career. + +2. **Conflating Industry with Growth.** Theodore Levitt's warning remains precise: there is no such thing as a growth industry, only companies organised to capitalise on growth opportunities. Leaders who hitch their career to an industry label rather than to transferable capability find themselves stranded when that industry's automatic escalator stops. + +3. **Over-Indexing on Willpower.** Attempting to change a career-limiting habit through pure discipline, without restructuring the environment, social context, or schedule that sustains it. Willpower is a depletable resource. Environment design is structural. + +4. **The "I'll Figure It Out When I Get There" Fallacy.** Refusing to calculate a career timeline because the future is uncertain. Uncertainty is precisely the reason to plan -- not because the plan will be followed precisely, but because the planning process reveals gaps and assumptions that would otherwise remain invisible. + +5. **Success Nostalgia.** Continuing to apply the strategies that created past success to problems that require different capabilities. The skills that built a company from zero to ten employees are often the skills that prevent it from reaching a hundred. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Skill diversification | The founder's career and the company's trajectory are fused. Career strategy means deliberately building skills beyond the founding specialisation -- finance, hiring, management -- before the company outgrows the founder's current capability set. | +| Growth | Identity expansion | Success traps begin to crystallise. The leader must actively resist defining their career through the single lens of "the person who built this." Broadening identity to include advisor, board member, or industry contributor creates resilience against role-specific setbacks. | +| Scale | Legacy architecture | Career fuel audits become existential. At scale, the leader's meaningful experiences may be plateauing even as financial rewards peak. Mentoring successors, taking on cross-industry challenges, and investing in enduring relationships outside the current organisation become the primary career fuel sources. | + +At every stage, the four-question self-grade provides the diagnostic. The answers change; the discipline of asking does not. + +--- + +## Output Template + +```markdown +# Career Strategy Assessment: [Leader Name / Role] + +## Timeline +- Estimated remaining career years: [N] +- Key assumptions: [health, financial, industry factors] + +## Career Fuel Audit +| Fuel Type | Current Level | Trend | Evidence | Action | +|-----------|--------------|-------|----------|--------| +| Transportable Skills | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | +| Meaningful Experiences | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | +| Enduring Relationships | [High/Medium/Low] | [Growing/Stagnating/Declining] | [specific evidence] | [specific action] | + +## Success Trap Exposure +| Trap | Risk Level | Evidence | Countermeasure | +|------|-----------|----------|----------------| +| Impatience | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Narrow Expertise | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Intellectual Arrogance | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Echo Chamber | [High/Medium/Low] | [specific behaviour] | [specific action] | +| Title Attachment | [High/Medium/Low] | [specific behaviour] | [specific action] | + +## Four-Question Grade +- Learning: [Yes/No — detail] +- Impact: [Yes/No — detail] +- Fun: [Yes/No — detail] +- Rewarded: [Yes/No — detail] + +## Priority Career-Limiting Habit +- Habit: [description] +- Intervention plan: [five levers applied] + +## 90-Day Actions +1. [Highest priority action] +2. [Second priority action] +3. [Third priority action] +``` + +--- + +## Related Skills + +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's fixed-versus-growth framework provides the psychological foundation for why some leaders treat career setbacks as data and others treat them as verdicts. +- **[Covey's Seven Habits](../../content/skills/frameworks/covey-seven-habits.md)** -- "Begin with the end in mind" and "put first things first" are the philosophical precursors to career timeline calculation and trade-off alignment. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The seven reflection domains provide the structured introspection that the four-question self-grade and success trap identification require. +- **[Senior Leadership Transition](../../content/skills/leadership/senior-leadership-transition.md)** -- Career strategy inflection points often coincide with leadership transitions where identity, skills, and relationships must all be recalibrated. +- **[Wanting What Matters](../../content/skills/thinking/wanting-what-matters.md)** -- Addresses the meta-question underlying career trade-offs: whether the goals being pursued actually align with what will produce lasting satisfaction. diff --git a/plugins/foreman/skills/carnegie-win-friends/SKILL.md b/plugins/foreman/skills/carnegie-win-friends/SKILL.md deleted file mode 120000 index cf18e59..0000000 --- a/plugins/foreman/skills/carnegie-win-friends/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/carnegie-win-friends.md \ No newline at end of file diff --git a/plugins/foreman/skills/carnegie-win-friends/SKILL.md b/plugins/foreman/skills/carnegie-win-friends/SKILL.md new file mode 100644 index 0000000..50a86d9 --- /dev/null +++ b/plugins/foreman/skills/carnegie-win-friends/SKILL.md @@ -0,0 +1,234 @@ +--- +name: "carnegie-win-friends" +description: "Applies Dale Carnegie's interpersonal influence principles for building relationships, earning trust, and leading without authority. Covers techniques for handling people, making others feel valued, winning people to your thinking, and changing behavior without giving offense. Use when building advisory networks, repairing strained stakeholder relationships, improving investor communications, navigating co-founder conflicts, or developing the interpersonal skills that underpin hiring, sales, and fundraising." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - interpersonal-skills + - influence + - leadership + - networking + - communication +related_skills: + - cialdini-influence + - trust-equation + - radical-candor + - win-win-negotiation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Carnegie's How to Win Friends and Influence People + +Published in 1936, Dale Carnegie's *How to Win Friends and Influence People* has sold over 30 million copies, been translated into dozens of languages, and remained continuously in print for nearly nine decades. A time-travel thought experiment clarifies why this matters: if you transported Carnegie's principles to a modern tech startup -- replacing "telegrams" with "Slack messages" and "salesmen" with "founders" -- the advice would require almost no adaptation. The principles work because they address something that has not changed in ninety years: human psychology. People still crave recognition. They still resist being told they are wrong. They still respond to genuine interest more readily than to polished pitches. The surface of business transforms every decade; the social operating system of human beings upgrades on evolutionary timescales. Carnegie mapped that operating system with a precision that keeps his Depression-era book selling in the age of AI. + +The question is not whether these principles still apply. The question is why so few founders -- drowning in frameworks for product, growth, and fundraising -- bother to master the foundational skill that underlies all of them: the ability to make other people want to work with you. + +--- + +## The Framework + +Carnegie organises his principles into four groups. Each group targets a different domain of interpersonal effectiveness. Below, the original principles are presented alongside modern entrepreneurial applications. + +### Group 1: Fundamental Techniques in Handling People + +**Principle 1: Never criticise, condemn, or complain.** + +Criticism triggers defensive behaviour, not behavioural change. Carnegie observed that even criminals rationalise their actions; direct criticism rarely produces the response the critic intends. The modern parallel: founders who publicly criticise team members, competitors, or investors create fear-based environments and reputational damage. + +*Modern application:* When an employee makes an error, address the systemic cause rather than assigning blame. "The deployment failed because our testing process has a gap" is actionable. "The deployment failed because you were careless" produces resentment. + +**Principle 2: Give honest, sincere appreciation.** + +Not flattery -- appreciation. The distinction matters. Flattery is generic and self-serving ("you're amazing"). Appreciation is specific and other-oriented ("your analysis of the competitive landscape changed how I think about our positioning"). Sincere appreciation is one of the most powerful and least deployed tools in a founder's repertoire. + +*Modern application:* In every investor update, board meeting, and team standup, name specific contributions and explain their impact. The cost is sixty seconds of preparation. The return is disproportionate loyalty and motivation. + +**Principle 3: Arouse in the other person an eager want.** + +Influence flows not from what *you* want but from connecting your objective to what *they* want. A founder who pitches an investor by explaining why the company needs money will lose to a founder who explains why this investment aligns with the investor's thesis, portfolio strategy, and personal legacy. + +*Modern application:* Before every pitch, negotiation, or hiring conversation, answer one question: what does the other person want, and how does my proposal help them get it? + +### Group 2: Ways to Make People Like You + +**Principle 4: Become genuinely interested in other people.** + +Not feigned interest. Genuine curiosity about another person's world -- their challenges, motivations, and expertise -- creates connection more effectively than any amount of charisma. + +*Modern application:* In customer discovery, the founder who asks questions with authentic curiosity uncovers insights that the founder running a scripted interview misses. Curiosity is both a social skill and a strategic advantage. + +**Principle 5: Smile.** + +Carnegie's simplest principle and the one most often dismissed as trivial. Research in nonverbal communication consistently confirms that facial warmth increases perceived trustworthiness, competence, and approachability. + +*Modern application:* In video calls (now the dominant medium for business communication), facial expression carries disproportionate weight because body language is truncated. A founder whose default expression is tense or neutral on camera is unconsciously communicating stress. + +**Principle 6: Remember that a person's name is, to that person, the sweetest sound in any language.** + +Using someone's name signals that they are significant enough to remember. Forgetting it signals the opposite. In an era of digital networking where founders meet hundreds of people annually, systematic name recall (CRM tools, post-meeting notes) is a competitive advantage. + +**Principle 7: Be a good listener. Encourage others to talk about themselves.** + +Carnegie anticipated by decades what neuroscience later confirmed: talking about oneself activates the brain's reward centres. People experience being listened to as a form of emotional compensation. The founder who listens more than they speak in a first meeting creates a stronger impression than the one who dominates the conversation. + +**Principle 8: Talk in terms of the other person's interests.** + +Research the person. Understand their context. Frame your message in their language, referencing their priorities. This is not manipulation; it is the basic discipline of communication -- translating your meaning into the receiver's frame of reference. + +**Principle 9: Make the other person feel important -- and do it sincerely.** + +Every human being carries a deep need to feel significant. Entrepreneurs who dismiss this as "soft stuff" handicap themselves in hiring, fundraising, partnerships, and sales -- all domains where the other party's felt sense of importance determines the outcome. + +### Group 3: How to Win People to Your Thinking + +**Principle 10: Avoid arguments.** + +You cannot win an argument. If you lose, you lose. If you win, you have made the other person resentful, which is another kind of losing. Carnegie's advice: sidestep the argument entirely. Acknowledge the other person's perspective, find common ground, and redirect the conversation toward shared objectives. + +**Principle 11: Show respect for the other person's opinions. Never say "You're wrong."** + +Direct contradiction triggers ego defence. "I see it differently" preserves the relationship. "You're wrong" destroys it. For founders who prize being right, this principle requires the discipline to separate truth-seeking from ego-gratification. + +**Principle 12: If you are wrong, admit it quickly and emphatically.** + +Rapid, unreserved admission of error disarms critics and builds credibility. The founder who says "I was wrong about our go-to-market strategy, and here's what I've learned" earns more respect than the one who rationalises the failure. + +**Principle 13: Begin in a friendly way.** + +Hostility begets hostility. Warmth begets openness. The first thirty seconds of an interaction set the emotional tone for everything that follows. + +**Principle 14: Get the other person saying "yes" immediately.** + +Start with areas of agreement before approaching areas of disagreement. Each "yes" creates psychological momentum toward further agreement. This is Carnegie's version of Cialdini's commitment-and-consistency principle, articulated decades earlier. + +**Principle 15: Let the other person do a great deal of the talking.** + +People persuade themselves more effectively than you can persuade them. By asking questions and listening, you allow the other person to arrive at your conclusion through their own reasoning. + +**Principle 16: Let the other person feel the idea is theirs.** + +The idea's origin matters less than its implementation. If a team member arrives at a strategy you were going to propose anyway, the fact that they feel ownership of it dramatically increases the probability of successful execution. + +### Group 4: Be a Leader -- How to Change People Without Offending + +**Principle 17: Begin with praise and honest appreciation.** + +Before delivering difficult feedback, establish genuine goodwill. This is not the discredited "feedback sandwich" -- it is a sincere opening that demonstrates the relationship is valued. + +**Principle 18: Call attention to mistakes indirectly.** + +"This report is well-researched. If the executive summary led with the key recommendation, it would be even more impactful." The mistake is addressed; dignity is preserved. + +**Principle 19: Talk about your own mistakes before criticising the other person.** + +Vulnerability reduces defensiveness. "When I was at your stage, I made the same error" creates solidarity rather than hierarchy. + +**Principle 20: Ask questions instead of giving direct orders.** + +"Would it make sense to approach the client this way?" generates more buy-in than "approach the client this way." The outcome is identical; the felt autonomy is not. + +--- + +## Prompts + +**Prompt 1 -- Stakeholder Relationship Audit:** +> Using Carnegie's principles, audit my current relationships with key stakeholders: [list 3-5 key relationships -- investors, cofounders, key hires, major customers]. For each, identify which Carnegie principles I am applying well, which I am neglecting, and what specific actions would strengthen the relationship. Be concrete -- suggest specific things I should say or do in my next interaction with each person. + +**Prompt 2 -- Difficult Relationship Repair:** +> I have a strained relationship with [describe the person and context]. Using Carnegie's principles, design a relationship repair strategy. What went wrong (mapped to which principles were violated)? What specific actions -- across multiple interactions, not a single conversation -- would rebuild trust and goodwill? Provide a 30-day action plan with specific touchpoints. + +**Prompt 3 -- Investor Communication Redesign:** +> Rewrite my investor update email using Carnegie's principles. Current email: [paste or describe]. The email should make each investor feel personally valued, acknowledge their specific contributions and advice, frame challenges in terms of the investor's interests, and close with a specific ask framed as something the investor would want to do. Maintain professionalism while applying Carnegie's interpersonal framework. + +--- + +## Use Cases + +**Idea-Stage Founder Building an Advisory Network** +A first-time founder with no industry connections needs advisors, early customers, and eventually investors. Applying Carnegie's principles systematically: genuine interest (researching each potential advisor's work and asking thoughtful questions), listening (letting advisors talk about their experiences rather than pitching), appreciation (specific thank-you notes referencing exact advice given), and making the other person feel important (publicly crediting advisors when their guidance produces results). Within six months, the founder has assembled an advisory board of four industry veterans who actively introduce them to investors and customers -- not because of the startup's traction, but because the founder made them feel valued. + +**Growth-Stage CEO Managing a Difficult Board Member** +A board member consistently challenges the CEO's strategy in adversarial terms, creating tension that spills into the management team. Applying Carnegie: the CEO stops arguing and starts asking the board member for their perspective before presenting their own. The CEO admits past strategic errors openly, demonstrating vulnerability. The CEO identifies the board member's underlying concern (fiduciary risk, driven by a prior portfolio failure) and proactively addresses it in every board update. Within two quarters, the relationship transforms from adversarial to collaborative -- the board member's scrutiny becomes an asset rather than a threat. + +--- + +## Anti-Patterns + +1. **Performative Warmth.** Applying Carnegie's principles mechanically -- memorising names from a CRM, offering scripted appreciation, displaying calculated interest -- without genuine feeling. People detect inauthenticity with remarkable accuracy. Carnegie's principles require sincere application or they backfire spectacularly. + +2. **Avoiding All Conflict.** Misreading "never criticise" as "never hold people accountable." Carnegie's principle addresses *how* you deliver difficult messages, not whether you deliver them. A founder who cannot confront poor performance because Carnegie said "don't criticise" has misunderstood the framework entirely. The principle is about method, not avoidance. + +3. **Manipulation Through Technique.** Using Carnegie's principles as a tactical toolkit for getting what you want from people, rather than as a genuine philosophy of human relationships. The short-term gains are real; the long-term reputation cost is devastating. In tight-knit entrepreneurial ecosystems, a reputation for manipulative charm is career-ending. + +4. **Cultural Universalism.** Carnegie wrote in and for American culture. Directness, informality, and effusive appreciation land differently in Japan, Germany, or Saudi Arabia. Founders operating internationally must adapt the principles' expression while preserving their underlying intent. + +5. **Neglecting the Power Dimension.** Carnegie's principles assume relatively symmetrical relationships. In situations of significant power asymmetry -- a founder with a dominant investor, an employee with an abusive manager -- "being friendly" and "avoiding arguments" can enable exploitation. The principles require a foundation of mutual respect to function as intended. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Network building | At the idea stage, you have no product, no traction, and no leverage. Interpersonal skill is your primary asset. Carnegie's principles turn cold outreach into warm relationships. | +| Validation | Customer discovery | Genuine curiosity and listening -- Carnegie's core principles -- are identical to the skills required for effective customer interviews. The founder who truly listens discovers what the founder who pitches misses. | +| Early Traction | Hiring and retention | Attracting talent to a small, unproven company requires making candidates feel valued, heard, and important. Carnegie's principles are a hiring advantage when you cannot compete on compensation. | +| Growth | Leadership and delegation | As the founder transitions from doer to leader, Carnegie's principles for changing people's behaviour without offending become critical. Managing through influence rather than authority scales better than micromanagement. | +| Scale | Institutional culture | At scale, Carnegie's principles must be embedded in culture -- training programmes, management practices, communication norms -- rather than depending on the founder's personal application. | + +--- + +## Output Template + +```markdown +# Stakeholder Relationship Strategy: [Your Name / Company] + +## Key Relationships +| Stakeholder | Relationship Quality | Carnegie Principles Applied | Principles Neglected | +|------------|---------------------|---------------------------|---------------------| +| [Name/Role] | Strong / Neutral / Strained | [List] | [List] | + +## Action Plan +### [Stakeholder 1] +- **Next interaction:** [Date/context] +- **Specific actions:** + - [Carnegie principle] → [Concrete action] + - [Carnegie principle] → [Concrete action] +- **Desired outcome:** [What you hope to achieve] + +### [Stakeholder 2] +- **Next interaction:** [Date/context] +- **Specific actions:** + - [Carnegie principle] → [Concrete action] +- **Desired outcome:** [What you hope to achieve] + +## 30-Day Relationship Building Goals +1. [Specific, measurable goal] +2. [Specific, measurable goal] +3. [Specific, measurable goal] + +## Authenticity Check +- Am I genuinely interested in these people, or performing interest? +- Which relationships feel transactional, and how do I make them genuine? +``` + +--- + +## Related Skills + +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Cialdini provides the scientific framework for why Carnegie's principles work; Carnegie provides the practitioner's art of applying them in real relationships. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Carnegie's principles build every numerator of the trust equation (credibility, reliability, intimacy) while naturally reducing the denominator (self-orientation). +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Carnegie and Scott appear to conflict -- "never criticise" versus "challenge directly" -- but they address complementary aspects of maintaining relationship quality while delivering necessary truths. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Carnegie's "arouse an eager want" is the interpersonal equivalent of Fisher and Ury's "focus on interests, not positions." +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Extends Carnegie's relationship-building principles into practical strategies for meeting, engaging, and deepening connections in professional contexts. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's empathy and social skill domains provide the psychological substrate that makes Carnegie's principles effective rather than performative. diff --git a/plugins/foreman/skills/choosing-and-executing/SKILL.md b/plugins/foreman/skills/choosing-and-executing/SKILL.md deleted file mode 120000 index 4a671f4..0000000 --- a/plugins/foreman/skills/choosing-and-executing/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/decisions/choosing-and-executing.md \ No newline at end of file diff --git a/plugins/foreman/skills/choosing-and-executing/SKILL.md b/plugins/foreman/skills/choosing-and-executing/SKILL.md new file mode 100644 index 0000000..91b5d29 --- /dev/null +++ b/plugins/foreman/skills/choosing-and-executing/SKILL.md @@ -0,0 +1,247 @@ +--- +name: "choosing-and-executing" +description: "Provides a toolkit for moving from deliberation to commitment and from commitment to results. Covers the cost of decision paralysis, the 70% rule for when to stop gathering information, implementation planning after the choice is made, transparency as a trust mechanism, handling challenges to decisions, and combating second-guessing through process review rather than outcome regret. Use when stuck in analysis paralysis, when a decision has been made but needs implementation momentum, when stakeholders challenge or resist a decision, when second-guessing erodes confidence, or when building a decision communication plan." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - analysis-paralysis + - commitment + - implementation + - decision-communication + - transparency + - second-guessing + - hindsight-bias + - reversibility + - decision-execution + - stakeholder-trust +related_skills: + - evaluating-and-deciding + - tough-decision-situations + - decision-making-under-pressure + - learning-from-failure + - trust-equation + - wanting-what-matters +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Choosing and Executing + +The cost of searching for the perfect decision almost always exceeds the cost of making a "good enough" one and iterating. Scott McNealy, cofounder of Sun Microsystems, captured this asymmetry in a single observation: he spent far less energy worrying about making the right decision and far more ensuring that any decision he made turned out right. The distinction is not semantic. It relocates agency from the moment of choice -- where the entrepreneur has minimal control over future variables -- to the months of execution that follow, where nearly everything is within reach. Founders who internalise this shift stop treating decisions as bets to be perfected and start treating them as hypotheses to be tested, adapted, and driven to outcomes through disciplined follow-through. + +--- + +## The Toolkit + +### Technique 1: The Reversibility Test + +Not all decisions deserve equal deliberation. Jeff Bezos famously divided choices into "one-way doors" (irreversible, high-stakes) and "two-way doors" (reversible, correctable). Most entrepreneurial decisions fall through the second door -- yet founders routinely treat them as though they are signing a blood oath. + +**The diagnostic question:** If this decision proves wrong in six months, can the company course-correct without catastrophic loss? If yes, the decision is a two-way door. Make it quickly, monitor outcomes, and adjust. + +**Why founders over-deliberate on two-way doors:** + +- **Identity attachment.** The choice feels like it defines the founder, not just the venture. +- **Anxiety amplification.** Research by Francesca Gino demonstrates that anxiety makes people simultaneously more receptive to advice and less capable of distinguishing good advice from bad -- a dangerous combination that extends deliberation without improving quality. +- **Perfectionism as procrastination.** Waiting for the "objectively correct" answer is often a socially acceptable form of avoidance. + +Reserve deep analysis for one-way doors: market exits, large capital commitments, equity dilution events. Everything else deserves the 70% rule. + +### Technique 2: The 70% Rule + +If a decision has been analysed to the point where approximately 70% of the relevant information is in hand, make the call. The remaining 30% is unlikely to arrive before the cost of delay exceeds the value of marginal certainty. + +**When to apply the rule:** + +- The team has debated the same options across multiple meetings with no new data surfacing. +- The competitive landscape is shifting while internal deliberation continues. +- The decision maker's gut has already settled, but the rational mind insists on "one more data point." + +**When to override the rule:** + +- The decision is genuinely irreversible (shutting down a product line, terminating a co-founder relationship). +- The 70% of information gathered points in contradictory directions -- not ambiguous, but actively conflicting. +- Regulatory or legal constraints demand a higher evidentiary threshold. + +Thomas Davenport suggests a meta-decision framework: decide how to decide. Assess importance, frequency, and urgency before allocating deliberation time. Rare, strategic, high-stakes choices merit extended analysis. Recurring, operational, reversible choices merit a clock -- and when the clock runs out, the decision is made. + +### Technique 3: Buying an Option + +When neither committing nor abandoning is palatable, consider a third move: buy an option. Rather than acquiring a company, form a partnership. Rather than launching nationally, pilot in one city. Rather than hiring a full-time executive, engage a fractional one for ninety days. Options convert large, irreversible decisions into small, reversible experiments -- providing real-world data that no amount of spreadsheet modelling can replicate. + +The discipline here is to treat the option as a learning vehicle, not as a permanent hedge against commitment. Every option must have an expiration date and explicit criteria for converting to a full commitment or walking away. + +### Technique 4: Post-Decision Implementation Protocol + +A decision without an implementation plan is a wish. The moment a choice is finalised, the following elements must be articulated: + +| Element | Purpose | +|---------|---------| +| **Decision statement** | One sentence: what was decided and why | +| **Stakeholder notification list** | Everyone affected, responsible, or accountable | +| **Implementation timeline** | Milestones, deadlines, and checkpoint dates | +| **Success criteria** | How the team will know the decision is working | +| **Escalation triggers** | Conditions under which the decision should be revisited | +| **Owner** | A single accountable individual, not a committee | + +Communicate the decision before rumour fills the vacuum. Include the reasoning process, not merely the conclusion. Research consistently shows that perceived fairness of process predicts acceptance of outcome -- even among those who preferred a different option. + +### Technique 5: Transparency as Trust Architecture + +Being transparent about how a decision was made is not a courtesy; it is a structural investment in trust. Liane Davey's work on organisational fairness identifies two dimensions that teams evaluate simultaneously: outcome fairness (did the result distribute burdens and benefits reasonably?) and process fairness (was the method of arriving at the result legitimate?). + +**The order-of-disclosure effect:** Studies show that when people learn about the process before the outcome, process fairness dominates their satisfaction. When they learn the outcome first, outcome fairness dominates. The practical implication is clear: lead with process. Explain the criteria, the alternatives considered, and the trade-offs weighed before announcing the decision itself. + +Transparency is especially critical when: + +- A decision overrides the preference of a vocal stakeholder. +- Resources are being reallocated from one team or project to another. +- The founder is making a judgment call that cannot be fully supported by data. +- The decision involves equity, compensation, or role changes. + +### Technique 6: Handling Challenges to Decisions + +Three patterns account for the majority of post-decision pushback: + +1. **"You didn't ask me."** A stakeholder feels excluded from the process. The fix is proactive: define decision roles at the outset using frameworks such as RACI or RAPID. If someone was intentionally excluded, be prepared to explain why. + +2. **"I didn't say anything then, but I disagree now."** Late-breaking dissent from someone who was present but silent. Establish the norm: silence denotes agreement. Those who wish to dissent must do so during the decision window, not after. + +3. **"I agreed, but I'm implementing something different."** The most corrosive pattern. The person nominally endorsed the decision but quietly modifies execution to suit their own preference. Counter this with explicit milestones, a single accountable owner, and periodic checkpoints that compare actual implementation against the decision as made. + +**The one legitimate reason to reopen:** new facts have emerged that materially alter the calculus. Changed opinions, second thoughts, or political manoeuvring do not qualify. + +### Technique 7: Defeating Second-Guessing + +Second-guessing is not rigorous reassessment; it is anxiety wearing a rational costume. Sydney Finkelstein's research identifies its cost: a founder who second-guesses a hire actively undermines that hire's probability of success, creating a self-fulfilling prophecy that validates the original doubt. + +**The antidotes:** + +- **Perspective calibration.** Ask: what are the actual stakes of this decision? Many choices that consume disproportionate mental energy have surprisingly low consequence. Redirect attention to decisions that genuinely matter. +- **Gut journalling.** Maintain a log of past decisions and their outcomes. Over time, this record builds calibrated self-trust and reveals whether intuition is a reliable signal or a noisy one. +- **Advisory polling.** When doubt persists, consult two or three trusted advisers -- not for validation, but for perspective. The act of articulating the decision to another person often resolves the uncertainty before the adviser even responds. +- **Scheduled review.** Set a specific date to formally revisit the decision. Between now and that date, execute with full commitment. This converts open-ended rumination into bounded, productive monitoring. +- **Process-outcome separation.** Judge decisions by the quality of the process that produced them, not by the outcome that followed. A sound process that yields a bad outcome is not a bad decision -- it is a reminder that the world contains irreducible uncertainty. Confusing process quality with outcome quality is the hallmark of hindsight bias. + +--- + +## Prompts + +**Prompt 1 -- Paralysis Diagnostic:** +> I have been deliberating on [describe decision] for [time period]. List the information I already have versus the information I am still seeking. For each missing piece of information, estimate: (a) how long it will take to obtain, (b) how much it would change the decision if obtained, and (c) the cost of waiting. Then recommend whether to decide now or continue gathering data. + +**Prompt 2 -- Implementation Blueprint:** +> I have decided to [describe decision]. Draft an implementation plan that includes: a one-sentence decision statement, stakeholder notification list, milestone timeline, success criteria, escalation triggers, and the single accountable owner. Tailor it to a [stage] startup in [sector]. + +**Prompt 3 -- Decision Communication Script:** +> I need to communicate [describe decision] to my team. Some members preferred a different option. Draft a communication that leads with the process used, explains the criteria and trade-offs, acknowledges the alternative viewpoints, and outlines next steps. Tone: direct, respectful, no hedging. + +**Prompt 4 -- Second-Guessing Audit:** +> I am second-guessing [describe past decision]. Walk me through: (1) the process I used to make it, (2) whether new facts have emerged that warrant revisiting, (3) whether my doubt is evidence-based or anxiety-driven, and (4) a recommended next action -- either recommit or reopen with specific new criteria. + +--- + +## Use Cases + +**The Feature Pivot That Stalled** + +A validation-stage SaaS founder has spent three months debating whether to pivot the core feature set based on user feedback. Metrics are mixed -- some cohorts respond well, others do not. The team has held four strategy sessions without resolution. Applying the 70% rule, the founder recognises that additional user interviews are unlikely to resolve the ambiguity. She buys an option instead: a 30-day A/B test running both feature sets simultaneously. The test provides real conversion data, and the team makes a definitive call within five weeks of the original deadlock. The cost of the test was trivial compared to the cost of three months of organisational drift. + +**The Hire Everyone Questioned** + +A growth-stage fintech founder hires a CTO from outside the industry, overriding the preference of several board members who favoured a candidate with sector-specific experience. Rather than letting the disagreement fester, he communicates the decision using the transparency protocol: he shares the evaluation criteria, the performance data from reference checks, and the strategic rationale for prioritising technical architecture skills over domain familiarity. He sets a 90-day review checkpoint. Two months in, early infrastructure improvements validate the choice, and the board members who initially objected acknowledge that the process was fair, even though their preferred outcome was not selected. + +**The Founder Who Could Not Stop Revisiting** + +An early-traction e-commerce founder finds herself re-examining every pricing decision within days of making it. She implements a gut journal: each decision is logged with the reasoning, the alternatives considered, and the expected outcome. After three months, she reviews the journal and discovers that 80% of her initial pricing calls were within 5% of what she later considered optimal. The journal transforms vague self-doubt into calibrated confidence, and her decision velocity doubles. + +--- + +## Anti-Patterns + +**The Consensus Trap.** Waiting for unanimous agreement before acting is not thoroughness; it is abdication disguised as democracy. Consensus is a luxury of low-stakes decisions. For high-stakes choices, one person must own the call. Seeking input is wise; requiring permission from everyone is paralysing. + +**Transparency Theatre.** Sharing the decision without sharing the reasoning. Announcing "we have decided to restructure the team" without explaining the criteria, alternatives, and trade-offs does not build trust -- it invites conspiracy theories. Transparency means process visibility, not just outcome notification. + +**The Perpetual Pilot.** Using options and experiments as a permanent substitute for commitment. Buying an option is a tool for reducing uncertainty before a decision, not a strategy for avoiding decisions indefinitely. Every option must have an expiration date. + +**Outcome-Based Self-Flagellation.** Judging a past decision harshly because the outcome was poor, without examining whether the process was sound. A founder who carefully evaluated three vendors, selected the best-qualified one, and still experienced a service failure did not make a bad decision. Punishing yourself for outcomes beyond your control trains you to avoid decisions, not to improve them. + +**The Silent Veto.** Allowing a senior stakeholder to remain silent during deliberation and then reopen the decision after the fact. This pattern is organisational poison. It teaches the team that formal decision processes are performative and that real power operates through back channels. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Speed over precision. Most decisions are reversible explorations. | Nearly every choice is a two-way door. Apply the 70% rule aggressively. The cost of delay at this stage is existential -- runway is finite, and the venture has no momentum to sustain it through prolonged deliberation. | +| Validation | Structured experimentation. Convert decisions into testable hypotheses. | Buy options wherever possible. Pilot before committing. The goal is learning velocity, not decision perfection. Implementation plans should be lightweight but explicit. | +| Early Traction | Establish decision norms for the growing team. | As headcount grows, "you didn't ask me" challenges multiply. Introduce formal decision roles (RACI/RAPID) and the silence-denotes-agreement norm. Transparency protocols become essential as the founder can no longer communicate every decision personally. | +| Growth | Delegation architecture. The founder cannot and should not make every call. | The critical skill shifts from making good decisions to designing systems that enable others to make good decisions. Implement escalation triggers, decision journals, and periodic review cadences across the leadership team. | +| Scale | Institutional decision quality. Protect against bureaucratic slowdown. | The risk inverts: at scale, organisations over-deliberate rather than under-deliberate. Reintroduce speed by enforcing decision deadlines, empowering frontline managers with clear decision rights, and reserving executive deliberation for genuinely irreversible choices. | + +--- + +## Output Template + +```markdown +# Decision Record: [Decision Title] + +**Date:** [YYYY-MM-DD] +**Decision Owner:** [Name and role] +**Stage:** [idea / validation / early-traction / growth / scale] + +## Decision Statement +[One sentence: what was decided and the primary rationale.] + +## Context and Alternatives Considered +| Alternative | Key Advantage | Key Risk | Reason Not Selected | +|-------------|---------------|----------|---------------------| +| [Option A] | | | | +| [Option B] | | | | +| [Option C -- selected] | | | [N/A -- this was selected because...] | + +## Process Used +- **Who was consulted:** [Names and roles] +- **Data reviewed:** [Key data sources] +- **Decision method:** [Founder call / team vote / advisory input / other] +- **Reversibility assessment:** [One-way door / two-way door] + +## Implementation Plan +| Milestone | Owner | Deadline | Status | +|-----------|-------|----------|--------| +| [Stakeholder communication] | | | | +| [First execution step] | | | | +| [Checkpoint review] | | | | + +## Success Criteria +- [Metric 1: target and measurement method] +- [Metric 2: target and measurement method] + +## Escalation Triggers +- [Condition under which this decision should be revisited] + +## Review Date +[Scheduled date for formal reassessment] +``` + +--- + +## Related Skills + +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- The Clear Thinking framework's unified decision system covers criteria weighting, margin of safety, and the irreversibility test; this toolkit provides the complementary post-decision disciplines. +- **[Tough Decision Situations](../../content/skills/decisions/tough-decision-situations.md)** -- When the problem is not paralysis but genuinely bad options, failed consensus, wrong calls, or time pressure, this companion skill provides targeted techniques. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Addresses the specific cognitive and emotional dynamics of high-stakes, time-compressed leadership decisions. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Extends the "extract the lesson" principle into a full organisational learning practice. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- The transparency techniques in this skill feed directly into the credibility and intimacy components of trust. +- **[Stoic Pragmatism](../../content/skills/stoic/stoic-pragmatism.md)** -- The Stoic emphasis on decisive action and practical execution aligns with the commitment discipline that prevents decision paralysis and second-guessing. diff --git a/plugins/foreman/skills/cialdini-influence/SKILL.md b/plugins/foreman/skills/cialdini-influence/SKILL.md deleted file mode 120000 index 430aa52..0000000 --- a/plugins/foreman/skills/cialdini-influence/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/cialdini-influence.md \ No newline at end of file diff --git a/plugins/foreman/skills/cialdini-influence/SKILL.md b/plugins/foreman/skills/cialdini-influence/SKILL.md new file mode 100644 index 0000000..42f8de6 --- /dev/null +++ b/plugins/foreman/skills/cialdini-influence/SKILL.md @@ -0,0 +1,229 @@ +--- +name: "cialdini-influence" +description: "Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing fundraising strategies, auditing marketing materials for persuasive effectiveness, planning negotiation tactics, or building community-driven growth while maintaining ethical boundaries." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - persuasion + - influence + - psychology + - sales + - marketing + - negotiation +related_skills: + - carnegie-win-friends + - win-win-negotiation + - trust-equation + - cialdini-influence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Cialdini's Principles of Influence + +Machiavelli understood power. He also understood that writing a manual for its naked exercise would earn him five centuries of notoriety -- the word "Machiavellian" survives as a synonym for amoral manipulation. Robert Cialdini, the Arizona State psychologist whose *Influence: The Psychology of Persuasion* has sold over five million copies, operates in adjacent territory but with a critical distinction. Where Machiavelli catalogued how power is *seized*, Cialdini mapped how consent is *manufactured* -- and then insisted on an ethical boundary. His seven principles describe the psychological triggers that cause people to say yes. They work whether deployed ethically or cynically, which is precisely why understanding them is not optional for founders. You will use these principles, or they will be used on you. The only choice is whether you wield them with awareness and integrity. + +The difference between influence and manipulation is not technique -- it is intent. Influence uses legitimate psychological principles to guide people toward decisions that genuinely serve their interests. Manipulation uses the same principles to exploit them. The toolkit is identical; the ethics are opposite. + +--- + +## The Framework + +Cialdini originally identified six principles in 1984, then added a seventh -- Unity -- in 2016's *Pre-Suasion*. Each principle operates as an automatic behavioural shortcut: a mental heuristic that humans use to navigate complex decisions efficiently, and that can be activated deliberately. + +### Principle 1: Reciprocity + +People feel obligated to return favours, gifts, and concessions. This obligation operates even when the initial favour was unsolicited and even when the return favour exceeds the original in value. + +**Mechanism:** When someone does something for us, a psychological debt is created. The discomfort of that debt motivates repayment -- often disproportionately. + +**Entrepreneurial application:** +- Offer genuine value before asking for anything: free trials, educational content, useful introductions +- In negotiations, make the first concession; the other party will feel compelled to reciprocate +- In fundraising, provide investors with valuable market intelligence before the pitch + +**Ethical boundary:** The favour must be genuine. Manufactured obligations -- "I gave you this free sample, now you owe me" -- erode trust when the manipulation becomes apparent. + +### Principle 2: Commitment and Consistency + +Once people commit to a position -- especially publicly and voluntarily -- they experience internal pressure to behave consistently with that commitment. Small initial commitments escalate into larger ones. + +**Mechanism:** Cognitive dissonance makes inconsistency psychologically uncomfortable. We adjust behaviour to match prior statements and actions, rationalising the alignment after the fact. + +**Entrepreneurial application:** +- Get early adopters to make small commitments (a free sign-up, a beta test) before requesting larger ones (a paid subscription, a case study) +- In hiring, candidates who invest time in a multi-stage process develop commitment to the outcome +- Public declarations of company values create internal pressure for leadership to honour them + +**Ethical boundary:** The initial commitment must be voluntary and informed. "Foot-in-the-door" techniques that deliberately obscure the eventual ask violate trust. + +### Principle 3: Social Proof + +When uncertain, people look to others' behaviour for guidance. The more people doing something, the more correct that behaviour appears. + +**Mechanism:** In ambiguous situations, the assumption "if everyone else is doing it, it must be right" is actually a reasonable heuristic -- most of the time. It fails spectacularly in cases of collective ignorance or herding. + +**Entrepreneurial application:** +- Display customer logos, testimonials, and usage statistics prominently +- "Join 10,000 companies who use [product]" works because it activates social proof +- In fundraising, name investors who have already committed (with permission) to trigger herd behaviour among those who have not +- Press coverage and analyst endorsements serve as expert social proof + +**Ethical boundary:** Social proof must be real. Fabricated testimonials, inflated numbers, and fake reviews are fraud, not influence. + +### Principle 4: Authority + +People defer to perceived experts and authority figures. Credentials, titles, uniforms, and demonstrated expertise all trigger compliance. + +**Mechanism:** Deference to authority is a deeply evolved heuristic -- following expert guidance is usually more efficient than independent evaluation of every decision. + +**Entrepreneurial application:** +- Establish thought leadership through publishing, speaking, and demonstrable expertise +- In sales, present case studies authored by recognisable industry figures +- Hire advisory board members whose authority transfers to the company +- In product marketing, use expert endorsements and third-party validation + +**Ethical boundary:** Authority must be legitimate. Claiming credentials you do not possess or manufacturing expert endorsements crosses from influence into deception. + +### Principle 5: Liking + +People are more easily influenced by those they like. Factors that increase liking include physical attractiveness, similarity, compliments, familiarity, and association with positive outcomes. + +**Mechanism:** Liking creates a halo effect -- positive feelings toward a person generalise to positive feelings about their proposals, products, and requests. + +**Entrepreneurial application:** +- Build genuine rapport before business conversations +- Find authentic common ground with investors, customers, and partners +- Personal branding is a liking strategy -- making the founder relatable humanises the company +- Community building creates peer-to-peer liking that transfers to the brand + +**Ethical boundary:** Liking must be authentic. Simulated warmth and calculated flattery may work short-term but produce lasting cynicism when unmasked. + +### Principle 6: Scarcity + +Opportunities appear more valuable when their availability is limited. Loss aversion (the pain of losing exceeds the pleasure of gaining) amplifies this effect. + +**Mechanism:** Scarcity signals value. If something is rare, it must be desirable -- otherwise, why would it be scarce? This heuristic served well in environments of genuine scarcity; it misfires in environments of manufactured scarcity. + +**Entrepreneurial application:** +- Limited-time offers, waitlists, and exclusive access create urgency +- "Only 3 spots remaining in our beta programme" (if true) activates scarcity +- In fundraising, genuine competitive interest from multiple investors creates natural scarcity +- Product launches with constrained supply generate demand + +**Ethical boundary:** Scarcity must be real. Fake countdown timers, artificial limitations, and perpetual "last chance" offers are the dark pattern equivalent of this principle. + +### Principle 7: Unity + +People are more influenced by those they perceive as belonging to the same group -- not mere similarity (liking) but shared identity. Family, nationality, profession, fandom, and tribe all create unity. + +**Mechanism:** Unity activates an in-group/out-group psychology far stronger than liking. "One of us" is a more powerful motivator than "someone I like." + +**Entrepreneurial application:** +- Build a community identity around your product or mission ("we are the people who...") +- Shared professional identity with investors ("as fellow engineers...") increases receptivity +- User communities that develop their own language, rituals, and identity create powerful retention +- Co-creation -- involving customers in product development -- builds unity through shared ownership + +**Ethical boundary:** Unity must not be weaponised through exclusion or tribalism. Building identity by defining an enemy is effective but corrosive. + +--- + +## Prompts + +**Prompt 1 -- Influence Audit:** +> Audit my current sales and marketing approach against Cialdini's seven principles of influence. Here is our customer journey: [describe from first touch to conversion]. For each principle (reciprocity, commitment/consistency, social proof, authority, liking, scarcity, unity), identify where we are already using it effectively, where we are missing opportunities, and where we may be crossing ethical boundaries. Recommend three specific changes. + +**Prompt 2 -- Fundraising Influence Strategy:** +> I am preparing to raise a [Series A/Seed/etc.] round. Using Cialdini's seven principles, design an influence strategy for my investor outreach. For each principle, provide a specific tactic I can use in the fundraising process -- from initial warm intro through pitch meeting through term sheet negotiation. My company: [describe stage, traction, industry]. Ensure every tactic stays on the ethical side of the influence/manipulation boundary. + +**Prompt 3 -- Ethical Persuasion Review:** +> Review the following marketing materials / sales scripts / pitch deck against Cialdini's principles. [Paste materials.] Identify which principles are being activated, whether the application is ethically sound, and where the messaging could be more persuasive without crossing into manipulation. Rewrite the three weakest sections. + +**Prompt 4 -- Negotiation Influence Plan:** +> I am entering a negotiation with [describe the other party and context]. Using Cialdini's principles, design a pre-suasion strategy (what I should do before the negotiation begins) and an in-negotiation influence plan. Identify which principles are most relevant to this specific counterparty and context, and provide specific language and actions for each. + +--- + +## Use Cases + +**Validation-Stage Startup Building a Waitlist** +A pre-launch consumer app needs to build demand before the product exists. Applying Cialdini systematically: Reciprocity -- offer early registrants exclusive content (a market research report) before asking for their email. Commitment -- ask registrants to invite one friend, creating a micro-commitment. Social proof -- display a live counter of registrations. Scarcity -- "first 1,000 users get lifetime premium access." Unity -- frame early adopters as "founding members" with a distinct identity. The combination produces a 12,000-person waitlist before launch. + +**Growth-Stage B2B SaaS Closing Enterprise Deals** +A B2B company struggles with long sales cycles in enterprise. Applying the framework: Authority -- publish a white paper co-authored with a recognised industry analyst. Social proof -- create a customer advisory board whose members' logos appear on the website. Reciprocity -- provide a free architecture assessment before the sales pitch. Commitment -- structure the evaluation as a phased pilot (small commitment) that naturally escalates. Liking -- ensure account executives research each prospect's background to find authentic connection points. Average sales cycle shortens by 23%. + +**Scale-Stage Company Negotiating a Strategic Partnership** +A 500-person company negotiates a platform integration with a larger partner. The power asymmetry is significant. Unity -- emphasise shared mission and the specific customer segment both companies serve ("our mutual customers need this"). Authority -- present data from a joint customer survey demonstrating demand. Reciprocity -- offer to co-invest in the integration engineering. Scarcity -- note (truthfully) that a competing platform has also expressed interest. The combination produces equitable partnership terms despite the size differential. + +--- + +## Anti-Patterns + +1. **Treating Influence as Manipulation Laundering.** Using Cialdini's academic veneer to dress up fundamentally deceptive practices. Fake scarcity, fabricated social proof, and manufactured authority are not "influence tactics" -- they are lies. The framework's ethical boundary is not a suggestion; it is its structural integrity. + +2. **Over-Indexing on a Single Principle.** Companies that rely exclusively on scarcity ("LIMITED TIME OFFER!") or social proof ("10 million users!") while neglecting reciprocity and genuine value creation. Influence is most powerful when multiple principles reinforce each other authentically. + +3. **Ignoring Cultural Variation.** Cialdini's research was conducted primarily in Western, individualistic societies. Authority and social proof operate differently in collectivist cultures. Liking manifests differently across cultural contexts. Founders operating internationally must calibrate principle application to cultural norms. + +4. **Confusing Short-Term Compliance with Long-Term Influence.** Influence principles can produce immediate compliance that erodes long-term trust. Aggressive scarcity tactics might close a sale today and produce a churn event next quarter. The principles are most valuable when they accelerate genuine value recognition, not when they override genuine hesitation. + +5. **Neglecting the Seventh Principle.** Many practitioners still operate on the original six principles, missing Unity entirely. In an era of community-driven growth, identity-based products, and mission-driven purchasing, Unity is often the most powerful principle available to startups. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Customer discovery influence | At validation, influence is about getting strangers to give you their most precious resource: time. Reciprocity (offering insight) and liking (genuine curiosity about their problems) are the dominant principles. | +| Early Traction | Conversion and evangelism | With a product in market, social proof and commitment become essential. Early customers who publicly commit to the product become evangelists whose advocacy activates social proof for subsequent customers. | +| Growth | Sales process optimisation | At growth, the influence framework becomes systematised across sales, marketing, and partnerships. Each principle maps to specific touchpoints in the customer journey. | +| Scale | Brand and community | At scale, Unity and Authority dominate. The company builds a category identity, establishes thought leadership, and creates a community whose shared identity becomes the most powerful retention mechanism. | + +--- + +## Output Template + +```markdown +# Influence Strategy: [Context — e.g., Product Launch / Fundraise / Partnership] + +## Principle Application Matrix +| Principle | Current Usage | Opportunity | Specific Tactic | Ethical Check | +|-----------|-------------|-------------|-----------------|---------------| +| Reciprocity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Commitment & Consistency | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Social Proof | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Authority | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Liking | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Scarcity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | +| Unity | [Current state] | [Gap identified] | [Specific action] | [Pass/Flag] | + +## Priority Actions (Top 3) +1. [Highest-impact tactic with implementation steps] +2. [Second priority with implementation steps] +3. [Third priority with implementation steps] + +## Ethical Guardrails +- [Specific boundaries for this context] +- [What we will NOT do, and why] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principles of interpersonal influence predate and overlap significantly with Cialdini's Liking and Reciprocity principles, providing the practitioner's art alongside the psychological science. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Cialdini's principles inform negotiation strategy at the tactical level, while principled negotiation provides the strategic framework for ensuring influence serves mutual gain. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Influence without trust is manipulation with a timer; the Trust Equation diagnoses whether influence tactics are building or eroding the relational foundation. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- Translates Cialdini's principles into leadership-specific contexts including stakeholder management, board communication, and organizational change. +- **[Influencing and Persuading](../../content/skills/people/influencing-and-persuading.md)** -- Provides practical interpersonal techniques that operationalize Cialdini's seven principles in face-to-face and group settings. +- **[Neuro-Linguistic Programming](../../content/skills/frameworks/neuro-linguistic-programming.md)** -- NLP's rapport-building and language pattern techniques complement Cialdini's Liking and Unity principles at the micro-communication level. diff --git a/plugins/foreman/skills/clarity-and-concision/SKILL.md b/plugins/foreman/skills/clarity-and-concision/SKILL.md deleted file mode 120000 index 19ceb22..0000000 --- a/plugins/foreman/skills/clarity-and-concision/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/clarity-and-concision.md \ No newline at end of file diff --git a/plugins/foreman/skills/clarity-and-concision/SKILL.md b/plugins/foreman/skills/clarity-and-concision/SKILL.md new file mode 100644 index 0000000..025292e --- /dev/null +++ b/plugins/foreman/skills/clarity-and-concision/SKILL.md @@ -0,0 +1,244 @@ +--- +name: "clarity-and-concision" +description: "Teaches techniques for achieving relentless clarity and ruthless concision in business writing, including the 20-word sentence rule, concrete detail over abstraction, word economy tactics, and the reader's perspective test. Features extensive before/after examples demonstrating how bloated corporate prose can be cut by 50-70% without losing meaning. Use when tightening any business document, eliminating wordiness, improving readability scores, preparing executive summaries, or when writing feels vague or overlong." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - clarity + - concision + - word-economy + - readability + - editing + - plain-language + - business-writing +related_skills: + - revising-and-editing + - plain-language-and-flow + - writing-with-purpose + - business-writing-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Clarity and Concision + +Consider a mid-sized company where 200 professionals each write an average of 10 internal messages per day, each message averaging 150 words. That is 300,000 words produced daily -- roughly three novels. Now suppose that 30% of those words are unnecessary. The organisation is generating 90,000 wasted words every working day. At an average reading speed of 250 words per minute, that is 360 person-hours per day spent reading words that should never have been written. Six full-time employees, year-round, doing nothing but reading padding. The financial cost of corporate verbosity is not metaphorical. It is measurable, and it is staggering. + +Clarity and concision are not aesthetic preferences. They are economic imperatives. + +--- + +## The Framework + +### Clarity as Courage + +Clarity is a double-edged sword. When a writer takes a position or recommends a course of action, the writing is clear -- and the writer is exposed. People who do not want to commit make their writing muddy on purpose. They leave room to claim credit for good outcomes and deny responsibility for bad ones. Readers, however, perceive this not as strategic ambiguity but as spinelessness. Clear writing requires taking a stand. + +The test for clarity is simple: show the draft to a colleague who has no context and ask them to identify the three main points. If they cannot do so accurately after one read-through, the writing is not clear enough. + +### The Research Case for Less + +The intuition that shorter is better has been validated experimentally, at scale. *Writing for Busy Readers* reports a field experiment in which two versions of an email were sent to 7,002 school board members across the United States requesting completion of a short online survey. One email contained 127 words; the other contained 49 words. The 49-word version produced nearly double the response rate -- 4.8% versus 2.7%. The survey itself was identical in both conditions. Some recipients likely looked at the longer email and declined to engage at all. Others read partway through and never reached the request. Still others used the email's length as a proxy for how long the survey would take: 29% of those who saw the concise version estimated the survey at under five minutes, compared with just 15% of those who saw the longer version. + +The average American adult reads nonfiction at approximately 240 words per minute -- four words per second. At that rate, every unnecessary sentence costs measurable time, compounded across every recipient. The arithmetic is unforgiving: a 500-word email sent to 200 people that could have been written in 250 words wastes over two hours of collective reading time. Scale that to a year of weekly all-hands updates and the cost becomes a line item no one budgets for but everyone pays. + +Perhaps the most revealing finding is how poorly writers self-correct. Gabrielle Adams and colleagues at the University of Virginia asked participants to summarise a short article and then edit their summaries to improve them. Eighty-three percent of participants *added* words during the editing pass rather than removing them. The same pattern held across topics from travel itineraries to patents. The instinct to accrete rather than subtract appears to be a cognitive default -- one that writers must consciously override. + +Blaise Pascal captured the asymmetry centuries ago: "I would have written a shorter letter if I'd had more time." The line has been attributed to Twain, Locke, and a dozen others, which only confirms how universally writers recognise the problem -- and how rarely they solve it. + +### The 20-Word Rule + +Research has confirmed repeatedly that the optimal average for readable sentences is no more than 20 words. This does not mean every sentence should be exactly 20 words -- variety in sentence length creates rhythm and holds interest. Some sentences should be very short. Others can be longer and more complex, building layered arguments. But the average, across a document, should hover around 20. + +**NOT THIS:** +> Efficiency measures that have been implemented by the company with strong involvement of senior management have generated cost savings while at the very same time assisting in the building of a culture that is centered around the value of efficiency. [40 words] + +**BUT THIS:** +> Our senior management team has cut costs and made the company more efficient. We expect to be more profitable for the next four quarters. [24 words] + +The first version says less with more. The second says more with less. + +### Show, Don't Tell + +Concrete business writing is persuasive because it is evidence-based, clear, and memorable. Abstract assertions invite scepticism; specific details earn credibility. + +| NOT THIS | BUT THIS | +|----------|----------| +| He was a bad boss. | He got a promotion based on his assistant's detailed reports, but then -- despite the company's record profits -- denied that assistant even routine cost-of-living raises. | +| The company lost its focus and floundered. | The CEO acquired five unrelated subsidiaries -- as far afield as a paper company and a retailer of children's toys -- and then couldn't service the $26 million in debt. | + +The vague versions are opinions. The specific versions are evidence that leads readers to draw the same conclusions -- independently, and therefore more convincingly. + +### Word Economy: Three Surgical Techniques + +Wordiness operates on multiple levels, from bloated sentences to verbose phrases to unnecessary padding. Three techniques eliminate the majority of excess: + +**Technique 1: Delete prepositions (especially "of").** +- *April of 2013* becomes *April 2013* +- *point of view* becomes *viewpoint* +- *the purpose of this evaluation* becomes *this evaluation's purpose* + +**Technique 2: Replace -ion nouns with verbs.** +- *was in violation of* becomes *violated* +- *provided protection to* becomes *protected* +- *made a determination* becomes *determined* + +**Technique 3: Replace be-verbs with stronger verbs.** +- *was hanging* becomes *hung* +- *is indicative of* becomes *indicates* +- *are in agreement* becomes *agree* + +These three rules, applied mechanically, typically reduce word count by 20-40%. + +### Before/After: The Compound Effect + +| NOT THIS | Words | BUT THIS | Words | +|----------|-------|----------|-------| +| The trend in the industry is toward self-generation by some companies of their own websites, and Internet technology is changing the nature of training necessary to acquire the skill of website development at an acceptable level of sophistication, so that this activity can more and more be handled in-house. | 49 | Since Internet technology makes it easier than ever to develop sophisticated websites, some companies now develop their own in-house. | 19 | +| We are unable to fill your order at this point in time because there is an ongoing dock strike that affects our operations. | 23 | We cannot fill your order right now because of the dock strike. | 12 | +| I am writing in response to a number of issues that have arisen with regard to the recent announcement that there will be an increase in the charge for the use of our lobby computers. | 35 | You may have heard that we're raising the fees for using our lobby computers. | 14 | +| The greater number of these problems can readily be dealt with in such a way as to bring about satisfactory solutions. | 21 | Most of these problems can be readily solved. | 8 | + +In the most extreme case, 49 words become 19 -- a 61% reduction with no loss of meaning. The shorter versions are not merely more efficient; they are more persuasive. Readers trust writers who respect their time. + +### Eliminate Padding + +Certain phrases contribute nothing but the illusion of seriousness: + +- *in this connection it might be observed that* -- delete entirely +- *it is important to bear in mind that* -- delete entirely +- *it is interesting that* -- delete entirely +- *it is notable that* -- delete entirely +- *it is worthwhile to note that* -- delete entirely +- *it should be pointed out that* -- delete entirely + +These phrases are throat-clearing. They signal to the reader that the writer is about to say something -- rather than simply saying it. + +--- + +## Prompts + +**Prompt 1 -- Word Economy Audit:** +> Here is a business document: [paste text]. Apply the three word-economy techniques: (1) delete unnecessary prepositions, (2) replace -ion nouns with verbs, (3) replace be-verbs with stronger alternatives. Also identify and eliminate all padding phrases. Show the original word count, the revised text, and the new word count. Calculate the percentage reduction. + +**Prompt 2 -- Clarity Stress Test:** +> Pretend you are an intelligent reader with no prior context about my company or project. Read this document: [paste text]. After one read-through: (1) What are the three main points? (2) What action is the writer requesting? (3) Where did you get confused? (4) Which passages could be misinterpreted? (5) Where did you have to re-read a sentence? Identify every clarity failure and suggest specific revisions. + +**Prompt 3 -- Show Don't Tell Conversion:** +> Here is a draft containing abstract assertions: [paste text]. Identify every sentence that "tells" rather than "shows" -- every opinion, generalisation, or claim that lacks supporting evidence. For each, either suggest a concrete, specific replacement or flag it as needing data I should gather. The goal is a document where every claim is supported by evidence. + +**Prompt 4 -- Sentence Length Analysis:** +> Analyse the sentence lengths in this document: [paste text]. Calculate the average. Identify the five longest sentences and suggest how to break them up. Identify any passages where all sentences are similar in length and suggest how to vary the rhythm. Target an average of 20 words or fewer. + +**Prompt 5 -- The Subtraction Edit:** +> Most editors instinctively add words when revising. Reverse that default. Take this draft: [paste text]. Your only permitted operation is deletion -- remove words, sentences, and entire paragraphs. Do not add a single word. Do not rephrase; only cut. Produce the shortest version that preserves every essential idea and action request. Show the original word count, the revised word count, and the percentage reduction. Then list, in a table, every deleted passage with a one-line justification for why it was expendable. + +--- + +## Use Cases + +**Idea-Stage Founder Rewriting a Landing Page** + +A founder's landing page opens with: "We aspire to be a partner primarily concerned with providing our clients the maximal acquisition of future profits and assets and focus mainly on clients with complex and multi-product needs, large and midsized corporate entities, individual or multiple entrepreneurial agents, and profit-maximising institutional clients." After applying the clarity and concision framework: "We're a client-focused firm dedicated to making sure you get the most out of our services. Our client base includes individual entrepreneurs, midsized companies, and large corporations." The original was 46 words of impenetrable corporate fog. The revision is 30 words that a customer can actually understand -- and that a search engine can parse. + +**Growth-Stage Company Tightening Investor Updates** + +A SaaS company's monthly investor update runs 2,500 words. Most investors skim it in under two minutes. Applying word economy techniques across three consecutive updates: Update 1 drops from 2,500 to 1,800 words (28% reduction). Update 2 drops to 1,400 words as the writer internalises the preposition and be-verb rules. Update 3 reaches 1,100 words -- the same information in 56% less space. Investor engagement (measured by reply rate) increases by 40%, because the update now respects the audience's time. + +**Early-Traction Nonprofit Doubling Newsletter Engagement** + +A nonprofit sends a weekly newsletter to 50,000 subscribers linking to six curated resources. The editorial team, composed of professional writers, drafts a 566-word newsletter with context, supporting quotes, and background detail for each link. Applying the subtraction edit -- cutting supporting detail that is relevant but not essential, removing author quotes, and eliminating scene-setting paragraphs -- the team produces a 275-word version preserving all six resource links. The concise version generates twice as many link clicks as the original. The lost detail represented the kind of supplementary material that writers value and readers skip. As one researcher in the *Writing for Busy Readers* study observed: readers who received the shorter version did not report feeling less informed -- they simply engaged more. + +--- + +## Anti-Patterns + +1. **Confusing Brevity with Concision.** Brevity means being short. Concision means being short without losing substance. A one-sentence summary that omits critical context is brief but not concise. The goal is to include everything necessary and nothing else. + +2. **Using Complexity as a Status Signal.** Some writers equate long sentences and Latinate vocabulary with intelligence. Readers equate it with obscurity. A 136-word sentence scoring 8.2 on the Flesch Reading Ease scale does not signal sophistication -- it signals that the writer is either hiding something or has not thought clearly about the subject. + +3. **Cutting Too Aggressively.** Concision taken to the extreme produces telegraphic prose that sounds curt and loses the writer's voice. The goal is to remain "faithful to the sounds and rhythms of normal, down-to-earth English" while eliminating waste. + +4. **Editing for Concision Before Revising for Structure.** Cutting 30% of the words from a structurally flawed document produces a shorter structurally flawed document. Always revise the macro structure first, then edit for concision. + +5. **Telling Instead of Showing.** Asserting that "the company performed poorly" is brief, but it is not persuasive. The concrete version -- "The CEO acquired five unrelated subsidiaries and couldn't service the $26 million in debt" -- is longer but incomparably more effective. Concision serves clarity; it does not replace evidence. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch compression | Every word on a pitch deck slide or one-pager must justify its existence. At the idea stage, the entrepreneur has less content and more temptation to pad. Concision here means saying less but meaning more. | +| Validation | Data-driven concision | Replace assertions with numbers. "Strong traction" becomes "47 paying customers in 3 months with 12% week-over-week growth." Specific data is inherently concise because it replaces paragraphs of qualitative hedging. | +| Early Traction | Communication volume management | The sheer volume of writing at this stage makes concision a time-management tool. Cutting 30% of words across all documents saves hours per week for both writer and readers. | +| Growth | Readability standards | Establish organisational standards: maximum average sentence length, maximum word count for recurring document types, required use of headings for documents over 500 words. Concision becomes policy. | +| Scale | Brand voice consistency | At scale, every external communication reflects the brand. A house style that mandates concision prevents the verbal inflation that accompanies corporate growth and bureaucratic layering. | + +--- + +## Output Template + +```markdown +# Clarity and Concision Audit: [Document Title] + +## Readability Metrics +- **Original word count:** [X] +- **Target word count:** [Y] (reduction target: [Z]%) +- **Average sentence length:** [X words] (target: 20 or fewer) +- **Longest sentence:** [X words] (location: paragraph [N]) +- **Flesch Reading Ease score:** [X] (target: 50+) + +## Clarity Assessment +- **Main points identifiable on first read?** [Yes/No] +- **Ambiguous passages:** [List with paragraph numbers] +- **Abstract assertions needing evidence:** [List] +- **Jargon needing plain-language replacement:** [List] + +## Concision Edits +### Prepositions Removed +| Original | Revised | +|----------|---------| +| [phrase] | [tighter phrase] | + +### -ion Nouns Replaced with Verbs +| Original | Revised | +|----------|---------| +| [phrase] | [verb form] | + +### Be-Verbs Replaced +| Original | Revised | +|----------|---------| +| [phrase] | [stronger verb] | + +### Padding Eliminated +| Phrase Removed | Location | +|----------------|----------| +| [padding phrase] | [paragraph N] | + +## Final Metrics +- **Revised word count:** [X] +- **Actual reduction:** [Y]% +- **Revised average sentence length:** [X words] +``` + +--- + +## Related Skills + +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- Concision editing is one component of the broader editing discipline; this companion skill provides the full revision-then-editing sequence. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- Plain language and concision are complementary disciplines: one eliminates jargon, the other eliminates waste. +- **[Writing with Purpose](../../content/skills/writing/writing-with-purpose.md)** -- A clear purpose prevents unnecessary content from entering the draft in the first place, making subsequent concision editing less onerous. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- The cognitive science of working memory limits and triage behaviour explains why every unnecessary word has a measurable cost in reader comprehension. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Leaders who model concise writing set the standard for organisational communication culture. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- Email is the medium where concision has the highest impact because readers triage ruthlessly and mobile screens punish verbosity. diff --git a/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md b/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md deleted file mode 120000 index f823bd5..0000000 --- a/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/coalition-and-partnership-games.md \ No newline at end of file diff --git a/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md b/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md new file mode 100644 index 0000000..50c68ff --- /dev/null +++ b/plugins/foreman/skills/coalition-and-partnership-games/SKILL.md @@ -0,0 +1,257 @@ +--- +name: "coalition-and-partnership-games" +description: "Analyses partnership structures, cofounder equity splits, and alliance formation using coalitional game theory. Applies Shapley Value for contribution-based allocation, imputation sets and the core for stability testing, and coalition disintegration models to predict breakups. Use when splitting equity among cofounders, structuring joint ventures, negotiating alliance terms, evaluating vendor partnerships, diagnosing why a partnership is failing, or determining fair cost-sharing among unequal participants." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - coalitions + - partnerships + - equity-split + - shapley-value + - alliances + - cofounder + - game-theory + - fair-allocation +related_skills: + - negotiation-game-theory + - evolutionary-strategy + - win-win-negotiation + - trust-equation + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Coalition and Partnership Games + +Three cofounders sit across a table, dividing equity. The technical founder built the prototype. The business founder brought the first paying customer. The third contributed the initial capital. They settle on equal thirds -- the path of least resistance, the conflict-avoidant default, and, according to the mathematics of cooperative game theory, almost certainly the wrong answer. Equal splits assume equal contribution, equal replaceability, and equal outside options. These conditions virtually never hold. The Shapley Value, developed by Lloyd Shapley in 1953 (work that earned him the Nobel Prize in Economics in 2012), offers a mathematically rigorous alternative: allocate based on each player's average marginal contribution across every possible ordering of the coalition. The calculation is not intuitive, but its logic is unassailable -- and it transforms equity conversations from emotional negotiations into structured analyses. + +--- + +## The Framework + +### Coalitions: Why They Form and Why They Matter + +A coalition is any group of players who agree to coordinate their actions for mutual benefit. In business, coalitions take many forms: cofounder teams, strategic alliances, joint ventures, supplier consortia, investor syndicates. The fundamental question is always the same -- does the group produce more value together than its members would separately? + +Game theory distinguishes three types of coalitions based on their value properties: + +| Coalition Type | Test | Business Meaning | Implication | +|---------------|------|------------------|-------------| +| **Superadditive** | Combined value exceeds sum of individual values | The partnership creates genuine synergy | Coalition should form; the question is how to split the surplus | +| **Additive** | Combined value equals sum of individual values | No synergy; partnership is neutral | No compelling reason to partner; equal split is the only stable allocation | +| **Subadditive** | Combined value is less than sum of individual values | Partnership destroys value (internal conflict, coordination overhead) | Coalition should not form; members are better off alone | + +The first task in any partnership analysis is determining which type applies. Many failed partnerships are subadditive coalitions that should never have formed -- the coordination costs and internal friction exceed whatever synergies the partners imagined. + +### The Grand Coalition and Sub-Coalitions + +The **grand coalition** includes all players. A three-person startup where all cofounders work together is a grand coalition. Sub-coalitions are any subset: two of the three cofounders forming a side agreement, or a faction within a larger alliance. + +The grand coalition is desirable when it is superadditive -- when everyone working together produces more than any combination of sub-groups. But its stability depends on whether any sub-coalition can credibly defect and do better on its own. This is where the mathematics becomes practically important. + +Consider a five-person founding team evaluating whether to bring in all five partners. The potential annual payoff of the full team is $1M. Two of the five discover they can generate $450K on their own. The remaining three can only produce $250K without the departing pair. The grand coalition's $1M is less than $450K + $250K = $700K... wait. That arithmetic actually favours the grand coalition. But the two-person sub-coalition's $450K exceeds the $400K they would receive under equal distribution ($200K each vs. $225K each). The defection is rational for those two players, even though it destroys collective value. This is the core tension of coalitional game theory. + +### The Shapley Value: Fair Allocation Based on Marginal Contribution + +The Shapley Value answers the question: given that the coalition has formed, what is the fair share for each player? + +The principle is elegant. Consider every possible order in which players might join the coalition. For each ordering, measure what each player adds when they arrive -- their marginal contribution at that point. Average each player's marginal contribution across all possible orderings. That average is their Shapley Value. + +**A practical cofounder example:** + +Three cofounders: Alice (technical), Bob (business), Carol (capital). + +Value of each individual alone: +- Alice alone: $0 (can build product but has no distribution or funding) +- Bob alone: $0 (can sell but has no product or funding) +- Carol alone: $0 (has capital but no product or sales ability) + +Value of pairs: +- Alice + Bob: $200K (product + distribution, but bootstrapped) +- Alice + Carol: $150K (funded product, but no go-to-market) +- Bob + Carol: $50K (funded sales team, but no product to sell) + +Value of all three: $500K + +There are six possible orderings (3! = 6). For each, track what each person adds: + +| Order | Alice's Contribution | Bob's Contribution | Carol's Contribution | +|-------|--------------------|--------------------|---------------------| +| A, B, C | $0 (first, alone) | $200K ($200K - $0) | $300K ($500K - $200K) | +| A, C, B | $0 | $350K ($500K - $150K) | $150K ($150K - $0) | +| B, A, C | $200K ($200K - $0) | $0 (first, alone) | $300K ($500K - $200K) | +| B, C, A | $450K ($500K - $50K) | $0 (first, alone) | $50K ($50K - $0) | +| C, A, B | $150K ($150K - $0) | $350K ($500K - $150K) | $0 (first, alone) | +| C, B, A | $450K ($500K - $50K) | $50K ($50K - $0) | $0 (first, alone) | +| **Average** | **$208.3K (41.7%)** | **$158.3K (31.7%)** | **$133.3K (26.7%)** | + +The Shapley Value suggests a 42/32/27 split -- not equal thirds. Alice's technical contribution is most critical to value creation (she appears in the highest-value pairings), so she receives the largest share. The mathematics captures what intuition often misses: contribution is not about effort or hours; it is about marginal impact on the coalition's output. + +### Imputation, the Core, and Stability + +An allocation is **individually rational** if every player receives at least what they could earn alone. An allocation is **collectively rational** if the total allocation equals the total coalition value (no surplus left on the table). Any allocation meeting both conditions is called an **imputation**. + +But not every imputation keeps the coalition stable. A sub-coalition might still defect if its members collectively receive less than what they could generate on their own. The **core** is the set of allocations where no sub-coalition has incentive to break away. + +**The stability test** for any proposed equity split: + +For every possible sub-group, verify that the group's combined allocation from the grand coalition exceeds what they could earn independently. If any sub-group is underpaid relative to its standalone value, the coalition is unstable. + +In the example above, the core requires: +- Alice + Bob together receive at least $200K (their pair value). Shapley gives them $366.6K. Satisfied. +- Alice + Carol together receive at least $150K. Shapley gives them $341.6K. Satisfied. +- Bob + Carol together receive at least $50K. Shapley gives them $291.6K. Satisfied. + +The Shapley allocation sits within the core -- it is stable. Not every allocation method produces this result. + +### The Landlord-Tenant Dynamic and Asymmetric Pairing + +In many business relationships, one party holds a scarce, essential resource (the "landlord") while multiple parties hold a common, substitutable resource (the "tenants"). The landlord-tenant dynamic from cooperative game theory reveals a stark truth: when one side is essential and the other is replaceable, the essential party captures most of the value. + +A startup with proprietary technology (the landlord) negotiating with multiple potential distribution partners (the tenants) holds enormous leverage -- not because of negotiation skill, but because of structural position. If the tenants cannot form a sub-coalition (a united front), the landlord can play them against each other, driving their individual allocations toward zero. + +The counter-strategy is tenant coalition formation: potential partners banding together to negotiate collectively. This shifts the game from a one-vs-many asymmetry to a more balanced bilateral negotiation. Trade unions, purchasing cooperatives, and industry consortia all represent tenant coalitions responding to landlord-tenant asymmetry. + +### Why Coalitions Disintegrate + +Coalition disintegration stems from two forces: + +**Individual rationality undermining collective outcomes.** The Prisoner's Dilemma applies within coalitions: each member's individually rational choice (maximise personal payoff) leads to collectively worse outcomes. A cofounder who secretly negotiates a side deal, a partner who free-rides on shared resources, an alliance member who shares proprietary information selectively -- these are all defections driven by individual rationality. + +**Small coalition rationality.** Sub-groups discover they can do better alone. Two of five cofounders realise their combined skills command a higher market value than their proportional share of the grand coalition. A regional alliance member discovers it can form a more profitable bilateral deal. The grand coalition fractures not because of betrayal, but because of rational calculation. + +**Confrontation and counter-confrontation cycles.** An allocation that satisfies one sub-group often dissatisfies another. Player 1 proposes a reallocation that benefits Players 1 and 3 at the expense of Player 2. Player 2 responds with a counter-proposal benefiting 2 and 3. The cycle continues until either a stable allocation is found or the coalition collapses. + +--- + +## Prompts + +**Prompt 1 -- Cofounder Equity Split:** +> We are [number] cofounders starting [describe company]. Each founder's contribution is: [list each founder and their specific contribution -- technical skills, business relationships, capital, domain expertise, time commitment]. Using the Shapley Value approach, help me calculate a fair equity split. For each founder, estimate their standalone value, the value of every possible pair and sub-group, and the full team value. Then compute each founder's average marginal contribution across all orderings to determine the mathematically fair allocation. + +**Prompt 2 -- Partnership Stability Audit:** +> We have an existing partnership among [describe parties and structure]. The current allocation of value/equity/revenue is [describe current split]. Each party's standalone alternative is approximately [describe what each could earn alone]. Using the core stability test from coalitional game theory, evaluate whether any sub-coalition of our partners could credibly defect. Identify which groups are underpaid relative to their coalition value and recommend reallocation to stabilise the partnership. + +**Prompt 3 -- Alliance Formation Decision:** +> We are considering forming an alliance with [describe potential partners]. Our standalone annual value is [amount]. The proposed alliance would generate [combined amount]. Using coalitional game theory, help me determine: (1) Is this coalition superadditive, additive, or subadditive? (2) What is the fair split using Shapley Value principles? (3) Are there any sub-coalitions that could destabilise the alliance? (4) What structural mechanisms (contracts, vesting, governance) should we implement to prevent rational defection? + +**Prompt 4 -- Diagnosing Partnership Failure:** +> Our partnership is showing signs of strain. The parties involved are [describe]. The original value allocation was [describe]. Recent developments: [describe tensions]. Using the coalition disintegration framework, help me diagnose: Is this individual rationality undermining collective outcomes? Is a sub-coalition forming? Is the current allocation outside the core? What reallocation or structural change could restabilise the coalition? + +--- + +## Use Cases + +**Idea-Stage: Three Cofounders Splitting Equity** + +A machine learning engineer, a healthcare-industry sales executive, and a physician with domain expertise decide to build a health-tech startup. The engineer argues for equal thirds. The sales executive -- who already has warm introductions to three hospital systems -- believes her contribution warrants more. The physician has the clinical credibility that no regulatory pathway can succeed without. + +Applying the Shapley Value framework, they estimate standalone and combination values. The engineer alone has near-zero startup value (ML skills are available for hire). The sales executive alone can consult but not build a product. The physician alone lacks both technical and commercial capability. But the engineer-physician pair can build a credible prototype worth $300K in grant funding. The sales-physician pair can secure pilot agreements worth $200K. The engineer-sales pair can build and distribute a generic product worth $150K. The full trio can raise a $2M seed round and secure three hospital pilots. + +The Shapley calculation produces a 38/33/29 split favouring the engineer (whose technical contribution amplifies every combination most). The conversation shifts from "who deserves what" to "who contributes what marginal value" -- a far less emotional framework. + +**Growth-Stage: Vendor Alliance Showing Cracks** + +A SaaS company formed a three-way integration alliance with a CRM platform and a payments processor. The original revenue-share was equal thirds. Two years later, the CRM platform's customer base has grown fivefold, making it the primary distribution channel. The payments processor's technology has become commoditised, with four viable alternatives. The SaaS company's product remains differentiated but is no longer the only option in its category. + +The CRM platform's standalone value to the alliance has increased dramatically; the payments processor's has decreased. The current equal-thirds allocation no longer sits within the core -- the CRM platform could form a bilateral deal with either partner and capture more value. The alliance is unstable. + +Resolution requires reallocation: increasing the CRM platform's share to reflect its new marginal contribution, or restructuring the alliance with contractual lock-in provisions that make defection costly. Without adjustment, the CRM platform will rationally exit the coalition within one to two renewal cycles. + +**Scale-Stage: Acquisition Consortium** + +Three mid-market companies consider pooling resources to jointly acquire a competitor. Company A contributes $20M in capital, Company B contributes distribution infrastructure worth $15M, and Company C contributes the management team that will run the acquired entity. The acquisition target generates $50M in annual revenue. Alone, none can complete the acquisition. The Shapley Value framework determines that Company A (capital) receives the largest share because capital is the bottleneck -- without it, neither distribution nor management creates value. The framework also reveals that Companies B and C should form a sub-coalition agreement to prevent Company A from renegotiating terms post-acquisition, when the capital has already been deployed and A's leverage diminishes. + +--- + +## Anti-Patterns + +1. **The Equal Split Reflex.** Defaulting to equal allocation because it avoids difficult conversations. Equal splits are mathematically correct only when all players have identical standalone values, identical marginal contributions in every sub-coalition, and identical outside options. This combination is so rare that assuming it is almost always a form of intellectual laziness disguised as fairness. + +2. **Ignoring Standalone Value.** Evaluating contributions only within the context of the coalition, without assessing what each player could achieve independently. A cofounder who can earn $300K as a senior engineer at a major technology company has a high standalone value. Their participation in a startup that pays them nothing for two years represents a real sacrifice -- one that the equity allocation should reflect. + +3. **Static Allocation in a Dynamic Game.** Setting equity or revenue-sharing terms at formation and never revisiting them. Marginal contributions change as the company evolves. The technical founder's contribution is enormous at the prototype stage and may diminish relative to the sales founder's contribution at growth stage. Vesting schedules and periodic reallocation mechanisms address this, but only if the coalition anticipates the problem at formation. + +4. **Conflating Effort with Marginal Contribution.** A partner who works 80-hour weeks on activities that any hired employee could perform has high effort but low marginal contribution. The Shapley Value measures what the coalition loses if a specific player is removed -- not how many hours they logged. This distinction is essential and frequently misunderstood. + +5. **Neglecting Sub-Coalition Threats.** Assuming the grand coalition is stable because everyone agreed to the terms. Rational players continuously evaluate their alternatives. If two of four partners discover they generate 70% of value but receive 50% of allocation, the sub-coalition threat is real regardless of what the partnership agreement says. Contracts slow defection; they do not eliminate the incentive. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder equity allocation | Standalone values are speculative and pair values are hypothetical. Use the Shapley framework to structure the conversation, but acknowledge that estimates are rough. Build in reallocation mechanisms (vesting, milestone-based adjustments) to account for uncertainty. | +| Validation | Early partnership structuring | First external partnerships form: pilot customers, technology partners, advisors. Apply the superadditivity test before committing -- many early partnerships are additive at best. Only partner when the combined value genuinely exceeds the sum of parts. | +| Early Traction | Revenue-sharing and alliance management | Revenue begins flowing, making marginal contributions measurable rather than estimated. Revisit initial allocations against actual data. The core stability test becomes practical: identify whether any partner is receiving less than their demonstrated contribution. | +| Growth | Complex multi-party alliances | Coalitions expand to include investors, distribution partners, integration partners. Sub-coalition dynamics become critical. Monitor for small coalition rationality -- subgroups that might defect. Structural safeguards (exclusivity clauses, joint IP, shared infrastructure) increase switching costs. | +| Scale | M&A, consortia, and ecosystem governance | The company becomes a coalition of coalitions. Acquisition targets, joint ventures, and industry consortia all involve nested coalition dynamics. Shapley-based allocation principles inform earnout structures, joint venture governance, and consortium voting rights. | + +--- + +## Output Template + +```markdown +# Coalition Analysis: [Partnership/Alliance Name] + +## Players and Standalone Values +| Player | Role/Contribution | Estimated Standalone Value | Outside Option | +|--------|-------------------|---------------------------|----------------| +| [Player 1] | [Description] | [Value alone] | [Best alternative] | +| [Player 2] | [Description] | [Value alone] | [Best alternative] | +| [Player 3] | [Description] | [Value alone] | [Best alternative] | + +## Coalition Value Assessment +- **Grand coalition value:** [Total value of all players together] +- **Coalition type:** [Superadditive / Additive / Subadditive] +- **Synergy surplus:** [Grand coalition value minus sum of standalone values] + +## Sub-Coalition Values +| Sub-Coalition | Combined Value | Sum of Members' Standalone Values | Superadditive? | +|---------------|---------------|-----------------------------------|----------------| +| [Players 1+2] | [Value] | [Sum] | [Yes/No] | +| [Players 1+3] | [Value] | [Sum] | [Yes/No] | +| [Players 2+3] | [Value] | [Sum] | [Yes/No] | + +## Shapley Value Allocation +| Player | Average Marginal Contribution | Percentage Share | Proposed Allocation | +|--------|------------------------------|------------------|---------------------| +| [Player 1] | [Amount] | [%] | [Equity/Revenue share] | +| [Player 2] | [Amount] | [%] | [Equity/Revenue share] | +| [Player 3] | [Amount] | [%] | [Equity/Revenue share] | + +## Core Stability Check +| Sub-Coalition | Coalition Value | Members' Combined Allocation | Stable? | +|---------------|----------------|------------------------------|---------| +| [Players 1+2] | [Value] | [Sum of allocations] | [Yes/No] | +| [Players 1+3] | [Value] | [Sum of allocations] | [Yes/No] | +| [Players 2+3] | [Value] | [Sum of allocations] | [Yes/No] | + +## Defection Risks +- [Identify any sub-coalition whose standalone value exceeds their combined allocation] + +## Structural Safeguards +- [Vesting provisions, exclusivity, shared IP, or other mechanisms to raise defection costs] +``` + +--- + +## Related Skills + +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- Once coalition membership is established, the Nash Product Solution determines optimal allocation terms between parties with differing utility functions. +- **[Evolutionary Strategy](../../content/skills/game-theory/evolutionary-strategy.md)** -- Market-level coalition behaviour follows evolutionary dynamics; the Hawk-Dove game explains when competitors cooperate versus compete. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the relational framework for conducting the conversations that coalition game theory structures analytically. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Coalition stability depends not only on mathematical allocation but on the trust between partners; the trust equation diagnoses relational factors that mathematical models assume away. +- **[Game Theory Fundamentals](../../content/skills/game-theory/game-theory-fundamentals.md)** -- Provides the prerequisite concepts of Nash equilibrium and payoff analysis that coalitional models extend into multi-player settings. +- **[Delivering the Deal](../../content/skills/negotiation/delivering-the-deal.md)** -- Coalition agreements must be closed and sustained; the preparation checklists and satisfaction engineering techniques address post-formation deal durability. diff --git a/plugins/foreman/skills/competitive-negotiation/SKILL.md b/plugins/foreman/skills/competitive-negotiation/SKILL.md deleted file mode 120000 index 5a1961b..0000000 --- a/plugins/foreman/skills/competitive-negotiation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/negotiation/competitive-negotiation.md \ No newline at end of file diff --git a/plugins/foreman/skills/competitive-negotiation/SKILL.md b/plugins/foreman/skills/competitive-negotiation/SKILL.md new file mode 100644 index 0000000..516602c --- /dev/null +++ b/plugins/foreman/skills/competitive-negotiation/SKILL.md @@ -0,0 +1,239 @@ +--- +name: "competitive-negotiation" +description: "Executes the competitive negotiation process from opening move through final concession: anchoring strategy, ambitious asking, concession architecture, midpoint management, impasse-breaking through linkage, and closing discipline. Provides actionable protocols for value-claiming negotiations. Use when setting price in a sales negotiation, responding to an aggressive counter-offer, planning concession sequences for fundraising, structuring opening bids in acquisition talks, countering procurement hardball in enterprise deals, or coaching a sales team to stop discounting reflexively." +version: "1.0.0" +category: "negotiation" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - competitive + - anchoring + - concessions + - opening-offer + - pricing + - deal-making + - value-claiming +related_skills: + - negotiation-mindset-and-self + - win-win-negotiation + - negotiation-game-theory + - cialdini-influence + - trust-equation + - carnegie-win-friends +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Competitive Negotiation + +The vice president of sales at a technology company ran an experiment. His team had been discounting reflexively -- shaving margins to close deals, training customers to expect that the quoted price was fiction. He instructed every sales professional to add 10 percent to their next proposal. The team protested: the market was saturated, the product was ageing, proposals went through competitive RFP processes. Four months later, the results arrived. Profitability increased 3 percent. Sales volume did not decrease at all. No new product. No new marketing. No market shift. The only variable that changed was the number on the opening offer. The most important moment in any competitive negotiation is the moment of asking -- and most people retreat at precisely that point, bargaining themselves down before the other party has said a word. + +--- + +## The Framework + +### The Nature of Competitive Negotiation + +Competitive negotiation is the process by which parties determine who gets how much of a defined pool of value. It answers a single question: how will this fixed pie be divided? Unlike cooperative negotiation -- which seeks to expand the pie (see [Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md) for the principled approach, and [Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md) for the mathematical structure) -- competitive negotiation accepts the pie's current size and focuses entirely on claiming a favourable share. + +Eight characteristics make the process predictable: + +1. **Fixed pie assumption.** The total value under negotiation is treated as finite. One party's gain is the other's loss. +2. **Zero-sum exchange.** Every dollar, percentage point, or term improvement for one side comes at the other's expense. +3. **Positional bargaining.** Each party states a position and defends it through a series of calculated retreats. +4. **Concession sequences.** Without concessions from both sides, no agreement is possible. The pattern of concessions is the negotiation. +5. **Diminishing increments.** Early moves are large; later moves shrink. The first concession might be thousands; the last might be a set of floor mats. +6. **Midpoint gravity.** Outcomes gravitate toward the midpoint of the first two *reasonable* offers. This is the single most exploitable feature of the process. +7. **The dance cannot be skipped.** Attempting to "cut to the chase" with a fair offer at the outset resets the anchor against you. The right answer at the wrong time is the wrong answer. +8. **Rising tension.** As concessions shrink and the gap narrows, emotional pressure increases. The negotiator who keeps composure captures the final increments. + +### The Ask: Your Most Important Move + +The opening offer is not an attempt to close a deal. It serves five distinct strategic functions: + +| Function | Mechanism | +|----------|-----------| +| **Starts the dance** | Signals willingness to negotiate and establishes the process | +| **Drops the anchor** | Sets the psychological reference point around which all subsequent moves orbit | +| **Manages expectations** | Communicates the range of outcomes you consider acceptable | +| **Creates upside potential** | An ambitious ask creates the possibility of an outcome better than your target | +| **Seizes initiative** | The party that frames the range controls where the midpoint falls | + +**Anchoring explained:** The first number on the table exerts disproportionate gravitational pull on all subsequent numbers. A New York restaurant introduced a $69 hot dog -- not to sell hot dogs, but to make the $17.95 cheeseburger feel reasonable. Cheeseburger sales surged. The same psychology governs every business negotiation. An office space landlord who opens at the top of the market anchors the entire discussion. A founder who opens a fundraise with an aggressive valuation anchors investor expectations upward. The anchor works at a subconscious level -- even experienced negotiators must consciously resist its pull. + +**The antidote to someone else's anchor:** Awareness, independent research, and an immediate counter-anchor. Pause the discussion if necessary. Conduct your own valuation. Return with a number grounded in your analysis, not theirs. + +### Six Blunders That Destroy Opening Offers + +**Blunder 1 -- Failing to anchor.** Letting the other party set the first number cedes the most powerful position in the negotiation. When uncertain, the value of influence (going first) almost always outweighs the value of information (waiting to hear their number). + +**Blunder 2 -- Prioritising comfort over strategy.** Research from Duke, Michigan, and Houston confirms: negotiators who make the first offer report higher anxiety *and* achieve better economic outcomes. The discomfort is a feature, not a flaw. Rehearse the opening with a trusted colleague until the anxiety subsides. + +**Blunder 3 -- "Let's see what happens."** Entering without a committed opening offer strategy surrenders you to the other party's anchor. A claims adjuster who valued a case at $35,000 received a plaintiff's demand of $300,000 -- and was subsequently authorised to settle at $75,000, more than double her own valuation. The demand, not the evidence, moved the number. + +**Blunder 4 -- Responding reasonably to an insulting offer.** An $8 million asking price for a business worth $5 million is an aggressive anchor. Responding with a "reasonable" $5 million creates a midpoint of $6.5 million -- a million above the buyer's walk-away. The correct response to an extreme offer is an equally extreme counter-offer that resets the midpoint to your target range. + +**Blunder 5 -- Misunderstanding the opening offer's purpose.** The opening offer is not your first attempt at a deal. It is the starting position of a choreographed process. Treating it as a genuine proposal leads to premature concessions. + +**Blunder 6 -- Excessive aggression.** An opening so extreme that the counterpart walks away or retaliates emotionally. Research from the University of Technology, Sydney, found that overly aggressive openers provoke spiteful counter-offers -- the other party punishes the aggression even at cost to themselves. Thread the needle: ambitious enough to capture value, credible enough to sustain engagement. + +### The Three Strategic Questions Before Any Opening + +1. **Who goes first?** Default: you. Control the anchor. Exception: when you genuinely have no idea of the value range and need their number as information. +2. **Where do you start?** Extreme or reasonable -- each has a place. Extreme positions pair with a soft delivery ("We'd ideally like to see..."). Reasonable positions pair with firm delivery ("Based on market data, the fair price is..."). +3. **How firm is your stance?** Extreme + soft = room to negotiate with warmth. Reasonable + firm = signals this is the actual number, minimal movement expected. + +### Concession Architecture + +Concessions are not retreats. They are strategic instruments with three functions: exchanging value to reach agreement, signalling your priorities and flexibility, and managing the other party's psychological experience of the deal. + +**The Seven Tools of Concession Management:** + +**Tool 1 -- Set up the process.** An ambitious opening offer creates space for substantial concessions. Each concession feels generous to the other party while moving toward your predetermined target. Without room to move, you appear rigid; rigidity breeds resentment even when your terms are fair. + +**Tool 2 -- Keep the end in mind.** Every concession should be tested against one question: does the midpoint of this round still point toward my target outcome? If the midpoint drifts away from your target, your concessions are too large. + +**Tool 3 -- Let the deal come to you.** Patience captures value. Smaller, slower concessions signal that you are approaching your limit. The negotiator who rushes leaves money on the table; the one who endures collects it. + +**Tool 4 -- Manage perceptions.** Express reluctance with each concession. Take time before responding. Describe internal approval challenges. The other party must believe each successive concession is harder to extract than the last. If concessions appear effortless, sophisticated counterparts will push for more. + +**Tool 5 -- Create a win for the other side.** J. Paul Getty's father advised: "Never try to make all the money in a deal." A counterpart who feels they lost will find ways to undermine the agreement post-signature, refuse future deals, or exact reputational costs. The goal is to capture disproportionate value while ensuring the other party perceives a fair process. A furniture store that refused to include a $15 marker with a $12,000 purchase lost all future business from that customer. The margin on the marker was irrelevant; the psychological cost of zero concessions was permanent. + +**Tool 6 -- Say no.** Paradoxically, the other party often needs to hear a "no" before they will agree to "yes." A firm refusal signals that you have reached your limit and the current terms represent the best available deal. Without a credible "no," the counterpart suspects more value remains on the table and continues pushing. Plan when and where you will deploy your "no" before the negotiation begins. + +**Tool 7 -- Use linkage.** When direct concession on the primary issue is impossible, link secondary value pools. The word *if* is the most powerful two-letter word in competitive negotiation. "If you accept our price, we will provide extended payment terms." A CEO closing a deal with a sports franchise linked seven low-cost items (PR activity, endorsements) to a final price concession. The franchise accepted all seven instantly. Linkage breaks impasses by expanding the negotiable surface area without surrendering on the core issue. + +### Substance vs. Style: The Master Combination + +Competitive negotiation does not require hostility. The most effective practitioners separate substance from style: + +- **Competitive on substance:** Ambitious opening, small concessions, firm limits, disciplined value-claiming +- **Cooperative on style:** Professional tone, respectful communication, genuine warmth, measured demeanour + +This combination allows a negotiator to claim maximum value while preserving the relationship for future transactions. Being competitive on substance while cooperative in style is the operational definition of negotiating like a professional rather than a bully. + +--- + +## Prompts + +**Prompt 1 -- Opening Offer Construction:** +> I am about to make the first move in a negotiation for [describe: fundraising valuation, contract price, salary, acquisition price, partnership terms]. My target outcome is [specific number or terms]. The other party likely expects [their probable range]. Using competitive negotiation principles, help me: (1) construct an opening offer that anchors the midpoint at or above my target, (2) determine whether to pair it with a firm or soft delivery, (3) anticipate the other party's likely counter-anchor, and (4) prepare my response to their counter. Include the specific language I should use when presenting the opening. + +**Prompt 2 -- Concession Sequence Planning:** +> I am in a multi-round negotiation over [describe deal]. My opening offer was [amount/terms]. Their counter was [amount/terms]. My target deal is [amount/terms]. My absolute bottom line is [amount/terms]. Design a concession sequence of 3-5 rounds that: (1) moves toward my target in diminishing increments, (2) keeps the running midpoint aligned with my target, (3) includes specific language for expressing reluctance at each step, and (4) identifies the round where I should deploy a firm "no" to signal my limit. + +**Prompt 3 -- Responding to an Aggressive Anchor:** +> The other party has opened with [describe their offer], which I believe is significantly [above/below] fair value. My independent assessment of fair value is [your estimate]. Help me: (1) construct a counter-anchor that resets the midpoint to my target range, (2) draft the language for rejecting their anchor without escalating emotion, (3) identify objective criteria I can cite to delegitimise their opening, and (4) plan my first three moves assuming they respond competitively. + +**Prompt 4 -- Linkage Strategy for Impasse:** +> A negotiation over [describe deal] has stalled. We are apart on [primary issue and gap]. Neither side is willing to make further concessions on this issue. Identify potential linkage opportunities: items that (a) cost me relatively little but are valuable to the other party, or (b) cost them relatively little but are valuable to me. Help me construct "if...then" proposals that break the impasse without conceding on the primary issue. My business context: [describe relevant details about what you value and what they likely value]. + +--- + +## Use Cases + +**Validation-Stage SaaS Startup Pricing Its First Ten Customers** + +A pre-seed B2B SaaS company has a working product and is closing its first ten paying customers. The founder, desperate for revenue validation, quotes $500/month to the first prospect -- a price chosen for comfort, not strategy. The prospect accepts immediately without negotiation. The founder has learned nothing about willingness to pay and has anchored herself at a price she cannot easily raise. + +Applying competitive negotiation: the founder's next proposal opens at $1,200/month -- ambitious but defensible given the ROI the product delivers. The prospect counters at $700/month. The midpoint is $950/month. Through three rounds of concessions (each smaller than the last, each expressed with visible deliberation), the founder closes at $900/month. The difference is not $400/month per customer. Compounded across the first ten customers and then used as pricing precedent for the next hundred, the opening-offer discipline produces a valuation-defining difference at the next fundraise. + +**Growth-Stage Company Negotiating an Acquisition Offer** + +A $15M ARR company receives an unsolicited acquisition offer. The acquirer's opening: $45M (3x revenue). The founder's research, grounded in comparable transactions and the company's growth rate, suggests fair value is $65-75M. The acquirer's opening is an anchor designed to pull the midpoint below fair value. + +The founder deploys a counter-anchor: $95M, paired with soft delivery ("Given our growth trajectory and recent comparable exits, we believe a range starting at $95M reflects the strategic value of this acquisition"). The midpoint resets to $70M -- inside the founder's target range. Over four rounds, concessions diminish: the founder moves from $95M to $88M to $82M to $78M. The acquirer moves from $45M to $55M to $62M to $68M. The final price of $73M -- near the midpoint of the first two reasonable offers ($95M and $55M) -- sits squarely in the founder's target zone. Without the counter-anchor, the negotiation would have gravititated toward $55M, costing the founder's shareholders $18M. + +**Early-Traction Startup Negotiating a Key Engineering Hire** + +A startup needs a senior engineer whose market rate is $180-200K. The candidate opens by requesting $220K plus 1.5% equity. The founder's budget ceiling is $195K plus 0.8% equity. Rather than conceding to avoid losing the candidate, the founder treats this as a competitive negotiation on substance while remaining enthusiastic about the candidate on style. Counter-offer: $175K plus 0.5% equity with a performance-based equity refresh after 12 months. The midpoint on salary ($197.5K) sits near the founder's range. Through two rounds -- each accompanied by genuine expressions of how much the team wants this candidate (cooperative style) and firm, small movements on numbers (competitive substance) -- the deal closes at $192K plus 0.75% equity with a 12-month refresh clause. Both parties feel respected. The founder preserved budget discipline. + +--- + +## Anti-Patterns + +1. **Discounting as Default.** Sales teams (and founders) who treat the quoted price as a fiction to be immediately discounted upon resistance. Every reflexive discount trains the market to never accept the first number. The 10-percent experiment proves the reverse: ambition is rewarded more often than expected. + +2. **Skipping the Dance.** Offering your "fair and final" number at the outset to save time. The other party will treat this as your opening position and negotiate downward from it. The process exists for a reason: it allows both parties to make concessions, read signals, and arrive at a number they can defend internally. There are no shortcuts. + +3. **Matching an Insulting Offer with a Reasonable One.** Responding to an extreme anchor with a "fair" counter-offer shifts the midpoint dramatically in the other party's favour. Extreme anchors demand extreme counter-anchors. Politeness in this context is expensive. + +4. **Conceding Without Receiving.** Making concessions without extracting reciprocal movement or linked value. Every concession teaches the other party something. A unilateral concession teaches them that pressure works and more is available. A linked concession ("if you do X, I can do Y") teaches them that value must be exchanged. + +5. **Emotional Escalation.** Allowing rising tension to convert competitive substance into competitive style. Raised voices, personal attacks, and ultimata delivered in anger destroy the very relationship that makes future concessions possible. The master negotiator maintains warmth in style while remaining unyielding on substance. Losing composure is losing leverage. + +6. **Confusing Ambition with Greed.** Pursuing the last dollar at the cost of deal completion or long-term relationship. Getty's rule holds: a counterpart who feels exploited will not honour the spirit of the agreement, will not return for future deals, and will actively damage your reputation. Competitive negotiation is about claiming a favourable share -- not the entirety -- of the available value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder equity, advisor compensation, first vendor contracts | Precedents set here persist for years. An opening offer of 0.25% to an advisor becomes the anchor for every subsequent advisor grant. Set ambitious but defensible anchors early -- renegotiating upward later is vastly harder than starting well. | +| Validation | Pricing first customers, pre-seed/angel term negotiations | The temptation to discount is strongest when revenue is zero. Resist it. Anchor at a price that reflects the value delivered, not the desperation felt. Every early price becomes a data point that investors and future customers will reference. | +| Early Traction | Enterprise sales, seed fundraising, key hire negotiations | Counterparts become more sophisticated. Procurement teams and experienced angels know the dance. Concession sequences must be planned in advance, not improvised. Linkage becomes essential for breaking impasses over payment terms, exclusivity clauses, and equity vesting. | +| Growth | Series A/B, strategic partnerships, executive compensation | Multiple-issue negotiations require careful midpoint management across several dimensions simultaneously. Concession on one dimension (board seats) should be linked to advantage on another (valuation). The founder negotiates less and prepares more, briefing the team that executes. | +| Scale | M&A, major licensing, public-market transactions | Professional advisors (investment bankers, M&A lawyers) run the process. The founder's role is to set the anchor strategy, define the walk-away point, and ensure the advisory team does not concede value to expedite their fee. Understanding competitive negotiation mechanics allows the founder to challenge their own advisors' recommendations. | + +--- + +## Output Template + +```markdown +# Competitive Negotiation Plan: [Deal Description] + +## Opening Offer Strategy +- **My target outcome:** [Specific number/terms] +- **My bottom line:** [Absolute minimum acceptable] +- **My opening offer:** [Ambitious anchor designed to place midpoint at target] +- **Delivery style:** [Firm + reasonable / Soft + extreme] +- **Opening language:** "[Draft the exact words]" + +## Anticipated Counter and Response +- **Their likely opening/counter:** [Estimated range] +- **Midpoint of first two reasonable offers:** [Calculate] +- **Does this midpoint align with my target?** [Yes/No -- if No, adjust opening] +- **My prepared counter-response:** [Specific number and language] + +## Concession Sequence +| Round | My Offer | Their Offer (Est.) | Midpoint | Movement Size | Signal Sent | +|-------|----------|-------------------|----------|---------------|-------------| +| 1 (Opening) | [Amount] | [Amount] | [Amount] | -- | Ambitious but engaged | +| 2 | [Amount] | [Amount] | [Amount] | [Smaller] | Slowing down | +| 3 | [Amount] | [Amount] | [Amount] | [Smaller still] | Approaching limit | +| 4 (Target) | [Amount] | [Amount] | [Amount] | [Minimal] | At the wall | + +## Linkage Options (If Impasse) +- **If they concede [X], I will offer [Y]** (high value to them, low cost to me) +- **If they concede [X], I will offer [Y]** +- **If they concede [X], I will offer [Y]** + +## "No" Deployment +- **Planned refusal point:** [Specific round or condition] +- **Language for saying no:** "[Draft the exact words]" +- **Walk-away conditions:** [Specific terms that trigger BATNA exercise] + +## Style Management +- **Competitive substance moves:** [List planned firm stances] +- **Cooperative style moves:** [List planned relationship-preserving actions] +``` + +--- + +## Related Skills + +- **[Negotiation Mindset and Self-Management](../../content/skills/negotiation/negotiation-mindset-and-self.md)** -- The internal preparation that precedes competitive execution; style selection, assumption auditing, and composure management determine whether the negotiator can sustain the discipline this skill demands. +- **[Cooperative Negotiation](../../content/skills/negotiation/cooperative-negotiation.md)** -- The counterpart for expanding the pie before dividing it; sophisticated negotiators use cooperative techniques to enlarge value and competitive techniques to claim it. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the theoretical architecture for interest-based bargaining that competitive tactics operate within. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- Provides the mathematical foundation for bottom lines, solution sets, and optimal splits; the Nash Product Solution informs where the midpoint should land. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Anchoring is a specific application of Cialdini's broader influence principles; reciprocity governs concession dynamics. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Competitive substance with cooperative style requires trust maintenance throughout adversarial value-claiming. diff --git a/plugins/foreman/skills/connecting-with-people/SKILL.md b/plugins/foreman/skills/connecting-with-people/SKILL.md deleted file mode 120000 index 158c039..0000000 --- a/plugins/foreman/skills/connecting-with-people/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/connecting-with-people.md \ No newline at end of file diff --git a/plugins/foreman/skills/connecting-with-people/SKILL.md b/plugins/foreman/skills/connecting-with-people/SKILL.md new file mode 100644 index 0000000..e6f41c3 --- /dev/null +++ b/plugins/foreman/skills/connecting-with-people/SKILL.md @@ -0,0 +1,236 @@ +--- +name: "connecting-with-people" +description: "Applies advanced interpersonal techniques for building genuine, lasting connections in entrepreneurial contexts. Covers the power of validation as the deepest form of listening, leading with 'How can I help you?' as a first-meeting strategy, maintaining authentic online identity, vulnerability as a professional strength, and the Platinum Rule that supersedes the Golden Rule by treating others as they want to be treated. Use when building investor relationships, resolving cofounder conflicts, designing customer-experience strategy, navigating cultural differences in international partnerships, or cultivating the authentic personal brand that underlies fundraising, hiring, and sales." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - validation + - vulnerability + - platinum-rule + - authenticity + - online-identity + - empathy + - connection +related_skills: + - understanding-people + - meeting-the-right-people + - reading-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Connecting with People + +The Golden Rule says "treat others as you'd want to be treated." The Platinum Rule says "treat others as *they* want to be treated." The difference is enormous. + +A founder added his own sales force to a joint venture, reasoning that if a partner did the same for him, he would be delighted. His partner was furious -- interpreting the move as interference, distrust, and territorial encroachment. The Golden Rule had produced the exact opposite of its intended effect because it substituted the founder's preferences for his partner's. The Platinum Rule requires a harder discipline: suspending your own frame of reference and inhabiting someone else's. It demands the listening, reading, and understanding skills covered in this category's sibling frameworks -- and then goes one step further, translating comprehension into behaviour calibrated to the other person's actual needs. + +Connection is not a feeling. It is a practice -- a series of specific, learnable behaviours that, applied consistently and sincerely, produce the trust upon which every entrepreneurial relationship depends. + +--- + +## The Framework + +Connecting with people operates through five techniques, arranged from the most immediately applicable to the most structurally transformative. + +### Technique 1: Validate, Validate, Validate + +Validation is mirroring's advanced form. Where mirroring repeats the speaker's words, validation names the speaker's *emotions* -- and demonstrates that those emotions are reasonable, even if the validator does not share them. + +**The distinction:** + +- **Mirroring:** "I hear you saying your bill was $250 more than expected." +- **Validation:** "You've been on hold for an hour and your bill is $250 wrong. You must be furious." + +Validation accomplishes something that no other technique in this category replicates: it disarms negative emotion *before* the substantive problem is addressed. A customer-service representative who validates an angry caller's frustration before attempting a fix will resolve the issue faster, with higher satisfaction, than one who jumps to solutions. The caller's cognitive bandwidth, previously consumed by anger, is freed for collaboration the moment she feels understood. + +**Execution protocol:** + +1. Listen for the emotional content beneath the words. +2. Name the emotion explicitly: "That must be frustrating." "You sound worried." "I can hear how excited you are." +3. Demonstrate resonance: "If that happened to me, I'd feel the same way." +4. Only then proceed to the substantive response. + +**The risk:** Validation requires accurate emotional identification. Misreading the emotion -- calling someone "angry" when they are "disappointed," or "anxious" when they are "cautious" -- produces dissonance rather than connection. When uncertain, validate tentatively: "Sounds like that was pretty frustrating?" The question mark invites correction rather than imposing interpretation. + +Validation is not agreement. Validating a cofounder's fear about a strategic decision does not mean the fear is warranted. It means the fear is acknowledged, which paradoxically makes the cofounder more receptive to evidence that the fear may be unfounded. + +### Technique 2: Lead with "How Can I Help You?" + +The single most productive question in a first meeting is not "What do you do?" or "Tell me about your company." It is: "How can I help you?" + +The question works on two levels: + +- **If they answer:** You receive a concrete opportunity to provide value, creating a reciprocity bond that operates on Cialdini's first principle without calculation or artifice. +- **If they decline:** You have demonstrated a care-first orientation that differentiates you from the vast majority of professionals who approach first meetings with extraction in mind. + +Either outcome positions you favourably. A financial adviser who asked "How can I help you?" at a first meeting never pitched his services. He made three introductions. The person he had helped hired him as a client months later -- not because the adviser asked, but because the decision to hire him felt organic and self-directed. The most powerful sales technique is the one where the customer sells themselves. + +**Prerequisites for effectiveness:** + +- **Know your sphere of influence.** Before asking, ensure you actually have the capacity to help. Offering help without resources to deliver it is worse than not offering. +- **Do your research.** Arrive at the meeting with three or four ways you could plausibly help, based on what you know about the person and their context. +- **Follow through.** The question creates an implicit promise. Failing to deliver on offered help destroys the trust the question was designed to build. + +### Technique 3: Online Identity Equals Real Identity + +The internet tempts people to construct dual identities: a polished professional persona for LinkedIn and a private self hidden behind privacy settings. The argument is that this partition is both unsustainable and counterproductive. + +**The case for unified identity:** + +Authenticity is a competitive advantage in saturated digital environments. Over 100 million blogs exist; the differentiator is not polish but voice. A founder who publishes a candid account of near-miss payroll failures, partnership arguments, and operational chaos attracts more trust -- and more clients -- than one whose content reads like a press release. Vulnerability signals confidence: only someone secure in their position would risk exposure. + +The 82% statistic is instructive: in survey data, 82% of respondents report higher trust in brands whose senior leadership uses social media authentically. The CEO who tweets about both product launches and personal struggles is perceived as human. The CEO whose digital presence is managed by a communications team is perceived as a brand -- which is to say, as something designed to extract value from you. + +**Practical application for founders:** + +- Eliminate the boundary between "professional" and "personal" social media profiles. Maintain one voice across all platforms. +- Share failures as well as successes. The failure posts will generate more engagement, more trust, and more business. +- Write in your own voice, including the imperfections. Ghostwritten perfection signals inauthenticity. +- Accept that some people will be repelled by your authentic self. These are people you would not want as customers, investors, or employees anyway. + +### Technique 4: Crying Is for Winners (Vulnerability as Strength) + +Professional culture teaches that emotional display is weakness. The evidence suggests the opposite. + +At one management retreat, a CEO opened with the most difficult experience of his life -- his father's mental illness -- and cried in front of his entire executive team. Rather than damaging his authority, the vulnerability catalysed a cascade: three of five team members also cried, sharing their own profound experiences. By the end of the session, executives who had known each other for years reported feeling closer than they had felt with lifelong friends. + +**The mechanism:** Vulnerability operates as a trust accelerator. The willingness to be emotionally exposed signals that the environment is safe for others to do the same. When both parties drop their professional armour simultaneously, the resulting connection is qualitatively different from -- and significantly stronger than -- the rapport built through conventional professional interaction. + +**Boundary conditions:** + +- Vulnerability requires a safe environment. Creating that environment -- establishing confidentiality, modelling the behaviour first, beginning with structured exercises -- is the leader's responsibility. +- Vulnerability is not performance. Crying to manipulate sympathy is detectable and devastating to credibility. +- The appropriate depth of vulnerability scales with the relationship's maturity. A cofounder retreat warrants deep emotional disclosure. A first investor meeting does not. +- Cultural context matters. The degree of emotional expression considered appropriate varies significantly across cultures, industries, and individual comfort levels. + +### Technique 5: The Platinum Rule + +The Golden Rule assumes that your preferences are universal. They are not. + +**Platinum Rule application matrix:** + +| Relationship | Golden Rule Failure | Platinum Rule Approach | +|-------------|--------------------|-----------------------| +| Cofounder (Type 5, introverted) | You celebrate wins publicly because you love public recognition | Ask privately how they prefer to be recognised -- they may prefer a quiet acknowledgement | +| Investor (risk-averse, fiduciary mindset) | You send optimistic updates because you would want to hear good news | Proactively address risks in every update because *they* want to know what could go wrong | +| Customer (enterprise, compliance-driven) | You move fast and ship frequently because you value speed | Provide advance notification and documentation because they value predictability | +| Employee (new parent, flexibility-oriented) | You offer a promotion with more responsibility because you would jump at it | Ask what they actually need -- it may be flexibility, not a title | + +The Platinum Rule is not intuitive. It requires the active suppression of the empathy heuristic -- the assumption that the other person feels what you would feel -- and its replacement with genuine inquiry. The simplest implementation: when uncertain about what someone wants, ask. "If I were you, I'd want X. What do *you* want?" + +--- + +## Prompts + +**Prompt 1 -- Validation Strategy for a Conflict:** +> I am in a conflict with [describe person, role, and nature of conflict]. Their position is [describe]. My position is [describe]. I believe their underlying emotion is [guess]. Design a validation-first approach: what specific validation statements should I open with, how should I test whether I have identified the correct emotion, and how do I transition from validation to problem-solving without negating the validation? + +**Prompt 2 -- First-Meeting Help-First Strategy:** +> I have a first meeting scheduled with [describe person and context]. Based on what I know about them [provide background], design three specific ways I could offer help before asking for anything. For each, explain why it would be valuable to them, what resources or connections I would need to deliver, and how to frame the offer so it feels genuine rather than transactional. + +**Prompt 3 -- Authenticity Audit:** +> Audit my online presence across [list platforms]. For each platform, assess: (a) how authentic is the voice compared to how I actually communicate, (b) what am I hiding that would build trust if shared, (c) where am I performing rather than connecting, and (d) what is one specific change I could make this week to increase genuine vulnerability? Be direct -- politeness about inauthenticity defeats the purpose. + +**Prompt 4 -- Platinum Rule Relationship Redesign:** +> For the following key relationships [list 3-5 with descriptions], I have been applying the Golden Rule -- treating them as I would want to be treated. For each relationship, identify where my preferences likely diverge from theirs. Then design a Platinum Rule approach: what does each person actually want, how can I determine this with certainty (including questions to ask), and what specific behaviour changes should I implement? + +--- + +## Use Cases + +**Validation-Stage Founder Handling Customer Rejection** + +A B2B SaaS founder receives consistently polite rejections from enterprise prospects after demo calls. She restructures her approach using validation-first technique: instead of opening the next demo with product features, she opens with "Before I show you anything, I'd like to understand what is most frustrating about your current workflow." The prospect describes a painful manual process. The founder validates: "That sounds genuinely exhausting -- doing that manually every week when you know it could be automated. That must feel like a waste of your team's talent." The prospect, visibly relieved at being understood rather than pitched, leans in. The demo that follows is half the length and twice as effective because the founder addresses only the validated pain point. Conversion rate from demo to pilot increases by 40%. + +**Early-Traction Cofounder Conflict Resolution** + +Two cofounders are deadlocked over whether to pursue enterprise customers or remain consumer-focused. Founder A (the CEO, a Golden Rule practitioner) has been sending Founder B detailed strategic memos, because that is how Founder A prefers to receive information. Founder B (the CTO, a verbal processor) finds the memos alienating and interprets them as a power play. Applying the Platinum Rule, Founder A asks: "How would you prefer we work through strategic decisions? I've been sending memos because that's how I think best, but I want to know how *you* think best." Founder B says he needs to talk it through verbally, in real time, on a whiteboard. They schedule a weekly two-hour strategy session in the format Founder B prefers. The deadlock breaks in three sessions -- not because either position changed, but because the communication channel finally matched the recipient. + +**Growth-Stage CEO Building a Public Brand** + +A CEO has maintained a carefully curated LinkedIn presence -- polished posts, professional headshots, only good news. Engagement is low and inbound interest minimal. She publishes a single post describing a month when the company nearly missed payroll, the argument with her cofounder that almost ended the partnership, and what she learned. The post generates 50x her normal engagement. Three former prospects re-engage. An investor DMs to schedule a meeting, citing the post's honesty as the reason. She begins publishing weekly with the same authentic voice -- sharing wins and failures in equal measure. Within six months, her personal brand becomes the company's most effective top-of-funnel channel. + +--- + +## Anti-Patterns + +1. **Validation as Capitulation.** Confusing "I understand how you feel" with "You are right." Founders who cannot validate without conceding lose the technique's power. Validation acknowledges the emotion; it does not surrender the position. The investor who is anxious about burn rate deserves to have that anxiety validated. The investor does not necessarily deserve a spending cut. + +2. **Weaponised Vulnerability.** Deploying personal stories strategically to create emotional obligation. The founder who cries in every pitch meeting is not being vulnerable -- he is performing vulnerability, and the audience will eventually recognise the pattern. Genuine vulnerability is unplanned, context-appropriate, and offered without expectation of return. + +3. **Help-First as a Long Con.** Asking "How can I help you?" with the pre-calculated expectation that the help will be reciprocated with a specific favour. Cialdini's reciprocity principle operates naturally and does not require engineering. The moment the offer feels transactional, the trust it was designed to build evaporates. + +4. **Platinum Rule Without Data.** Attempting to treat others as they want to be treated without actually knowing what they want. The Platinum Rule is not an invitation to assume more creatively; it is an instruction to inquire more directly. When in doubt, ask. The question itself demonstrates the principle. + +5. **Forced Authenticity Online.** Sharing personal stories because a framework told you to, not because the sharing is genuine. Readers detect performative vulnerability with the same accuracy they detect performative confidence. The online identity should emerge from a genuine integration of personal and professional self, not from a content strategy that mandates "one vulnerable post per week." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder connection depth | At the idea stage, the cofounder relationship is the company's structural foundation. Platinum Rule calibration and vulnerability exercises between cofounders prevent the communication breakdowns that kill partnerships before products launch. | +| Validation | Customer empathy and validation | Customer discovery is an exercise in validation. The founder who validates customer frustration before proposing a solution generates deeper insights and stronger early-adopter loyalty than one who leads with the product. | +| Early Traction | Hiring through authentic brand | Talent is attracted to authentic founders. The early-traction stage is where the CEO's online identity becomes a recruiting tool -- candidates who resonate with the founder's genuine voice self-select into the culture. | +| Growth | Stakeholder relationship management | Growth introduces conflicting stakeholder needs -- investors want metrics, employees want meaning, customers want reliability. The Platinum Rule becomes a stakeholder-management framework: each audience receives communication in the format they prefer. | +| Scale | Cultural embedding | At scale, connection techniques must be institutionalised. Validation becomes a customer-service training module. The Platinum Rule becomes a management philosophy. Vulnerability becomes a cultural norm, modelled from the top. | + +--- + +## Output Template + +```markdown +# Connection Strategy: [Relationship / Situation] + +## Validation Plan +- **Anticipated emotions from other party:** [List with confidence level] +- **Validation statements prepared:** + 1. [Statement addressing primary emotion] + 2. [Tentative validation for uncertain emotion: "It sounds like...?"] +- **Transition to substance:** [How to move from validation to problem-solving] + +## Help-First Inventory +| Person | What They Likely Need | What I Can Offer | Delivery Timeline | +|--------|----------------------|-----------------|-------------------| +| [Name] | [Need] | [Specific help] | [When] | + +## Platinum Rule Adjustments +| Stakeholder | My Default (Golden Rule) | Their Preference (Platinum Rule) | Behaviour Change | +|------------|------------------------|--------------------------------|-----------------| +| [Name/Role] | [What I would do naturally] | [What they actually want] | [Specific adjustment] | + +## Authenticity Check +- **Online presence alignment:** [Honest / Curated / Disconnected] +- **One change to increase authenticity this week:** [Specific action] +- **Vulnerability appropriate for current context:** [What to share and what to hold] + +## 30-Day Connection Goals +1. [Specific validation practice] +2. [Specific Platinum Rule implementation] +3. [Specific authenticity experiment] +``` + +--- + +## Related Skills + +- **[Understanding People](../../content/skills/people/understanding-people.md)** -- Understanding provides the motivational map that the Platinum Rule requires; without knowing what drives someone, treating them as they want to be treated is guesswork. +- **[Reading People](../../content/skills/people/reading-people.md)** -- Reading provides the real-time signal detection that validation depends on; accurate validation requires accurately reading the emotion before naming it. +- **[Meeting the Right People](../../content/skills/people/meeting-the-right-people.md)** -- Meeting creates the initial contact; connecting transforms that contact into a relationship that compounds over time. +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principle of "arousing an eager want" is the 1936 precursor to the Platinum Rule; this modernises it with explicit emphasis on the other person's frame of reference. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's empathy domain provides the theoretical foundation for validation and the Platinum Rule. +- **[Stoic Virtue and Kindness](../../content/skills/stoic/stoic-virtue-and-kindness.md)** -- The Stoic emphasis on kindness and mutual interdependence provides the philosophical foundation for the genuine care that connection techniques operationalise. diff --git a/plugins/foreman/skills/cooperative-negotiation/SKILL.md b/plugins/foreman/skills/cooperative-negotiation/SKILL.md deleted file mode 120000 index 8b12b0e..0000000 --- a/plugins/foreman/skills/cooperative-negotiation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/negotiation/cooperative-negotiation.md \ No newline at end of file diff --git a/plugins/foreman/skills/cooperative-negotiation/SKILL.md b/plugins/foreman/skills/cooperative-negotiation/SKILL.md new file mode 100644 index 0000000..7b319da --- /dev/null +++ b/plugins/foreman/skills/cooperative-negotiation/SKILL.md @@ -0,0 +1,229 @@ +--- +name: "cooperative-negotiation" +description: "Guides the practitioner through cooperative negotiation execution: transitioning from positions to interests, deploying empathy strategically, and following a structured six-step roadmap to resolution. Use when a competitive stance has stalled, when the relationship matters as much as the deal, when negotiating with a more powerful counterparty, when seeking creative value that positional bargaining cannot unlock, or when preparing for partnership, licensing, or joint-venture conversations." +version: "1.0.0" +category: "negotiation" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - cooperation + - empathy + - interests + - value-creation + - conflict-resolution + - deal-making + - rapport +related_skills: + - win-win-negotiation + - delivering-the-deal + - trust-equation + - carnegie-win-friends + - emotional-intelligence + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Cooperative Negotiation + +POSITIONS TO INTERESTS -- two people fighting over an orange. One wants the peel, the other wants the juice. Same position ("I need the orange"), different interests. The negotiation fails because nobody asks why. This parable, worn smooth by repetition in every negotiation textbook, persists because its lesson remains almost universally ignored. Most business negotiations collapse not from bad faith or insufficient leverage but from a far simpler failure: both sides argue about what they want without ever surfacing why they want it. + +Fisher and Ury's principled negotiation framework (covered in the `win-win-negotiation` skill) provides the theoretical architecture -- separate people from problems, focus on interests, generate options, use objective criteria. That skill teaches the blueprint. This one teaches what to say when you sit down across the table. + +--- + +## The Framework + +### The Anatomy of a Deal + +Every negotiation begins with an issue -- a problem or opportunity that requires agreement. Each party arrives with a position: a concrete statement of how the issue should be resolved. When positions collide, the instinct is to argue harder, concede reluctantly, or walk away. This is the positional death spiral. It escalates tension, damages relationships, and wastes resources. + +The cooperative alternative requires a single, decisive move: transition from positions to interests. + +**Positions** are concrete, divisible, and visible. They are the stated demands -- price, terms, equity split, delivery date. + +**Interests** are intangible, often unarticulated, and frequently invisible even to the person holding them. They include: + +- **Ego** -- the need to look competent, respected, successful +- **Fear** -- of loss, exposure, failure, humiliation +- **Relationships** -- preserving a partnership, impressing a boss, honouring a commitment +- **Values** -- fairness, loyalty, autonomy, recognition +- **Circumstances** -- budget cycles, reporting deadlines, personal pressures + +The hospital case illustrates the principle with surgical precision. A woman with compression fractures from a botched bed transfer demanded $150,000. Her lawyer set that position. But the woman herself wanted three things: a guarantee of safer protocols, an apology, and continued access to her physician. The litigation manager addressed all three interests directly -- promising procedural review, delivering a genuine apology, and welcoming her back. The case settled for far less than the demand because the demand was never the point. + +### The 70/30 Rule + +Research consistently finds that roughly 70% of business decisions are driven by emotion, not logic. People overpay for products that make them feel good. They reject objectively superior deals that make them feel diminished. The implication for negotiators is stark: the other party's decision will depend less on what they think about your offer and more on how they feel about themselves when considering it. Your task is to construct a process in which saying yes feels like a victory for them. + +### The Roadmap to Resolution + +Moving from positions to interests does not happen organically. People resist it because sharing interests feels like surrendering control. A structured process restores that sense of control. Six steps, in strict sequence. + +**Step 1: Steer the conversation.** Actively redirect the discussion away from positional haggling. The phrase "Before we get into numbers, can we spend a few minutes understanding what each of us is trying to accomplish here?" is worth more than most opening offers. + +**Step 2: Ask questions.** Open-ended questions are the cooperative negotiator's primary instrument. Not cross-examination -- exploration. + +| Instead of... | Try... | +|---------------|--------| +| "Why do you need that?" | "Help me understand what's driving that priority." | +| "That's too high." | "Tell me more about how you arrived at that figure." | +| "Can you do better?" | "I'm curious about what a good outcome looks like from your side." | +| "Is that your final offer?" | "What is it about this particular term that matters most?" | + +The objective is to get the other side talking at length. People who feel heard tend to share information they did not intend to disclose. That information is your material for crafting a deal. + +**Step 3: Listen.** The human brain processes speech at 400-800 words per minute but people speak at 125-175. The excess capacity breeds distraction. Disciplined listening means watching for the unstated -- the ego that cannot be acknowledged, the fear that cannot be articulated. When you detect an unspoken interest, name it gently: "It sounds like making sure your team sees this as a win is important here. Am I reading that right?" + +**Step 4: Create options.** Brainstorm freely. Whiteboard it. Invite the other party into the process. Place both sides' interest lists on the board and look for non-competing elements -- the surprising number of interests that do not actually conflict. Generate volume before applying judgement. + +**Step 5: Develop options.** Filter for feasibility. Which ideas are logistically achievable? Maintain optimism during this narrowing -- the temptation to abandon the cooperative approach peaks here. + +**Step 6: Evaluate options.** The criterion is not "what is best for me" or "what is best for them" but "what doable option best satisfies both sets of interests?" Evaluation comes last. Premature critique kills creative solutions. + +### Empathy as Strategy + +Abraham Lincoln's observation -- "If you would win a man to your cause, first convince him that you are his sincere friend" -- is not sentimentality. It is a negotiation protocol. + +Empathy in this context is not sympathy. The distinction matters. Sympathy says "I feel terrible for you." Empathy says "I understand how you feel, and I understand why you feel that way." The empathetic negotiator comprehends the adversary's position without experiencing it or agreeing with it. + +**The Lead-with-Need Model (OURS):** + +1. **Observe** -- Watch body language, listen to tone, note what provokes energy or withdrawal. Stop interrupting. +2. **Understand** -- Get the counterpart to explain as much as possible. The goal is comprehension of both the problem and the emotion behind it. +3. **Respect** -- Acknowledge their perspective without conceding your position. "Thank you for sharing that with me. That is very helpful" has never once produced a negative reaction in a negotiation. +4. **Solve** -- Use what you have gathered to build toward common ground. The conversation pivots from adversaries across a table to colleagues facing a shared problem. + +**Environmental engineering:** Physical setup matters. Lounge seating rather than a boardroom table. A whiteboard for collaborative ideation. Sitting adjacent rather than across. The law of conformity means people mirror the environment -- a relaxed setting produces relaxed disclosure. + +### The Lockheed Martin Playbook + +Marillyn Hewson's negotiation with President Trump over the F-35 programme remains a masterclass in cooperative execution against a formidable counterparty. Trump held the most powerful office on earth and was publicly attacking Lockheed's pricing. Hewson's competitive options were limited. + +Her response: hire a former Trump staffer to understand his interests. Map those interests -- public "wins," job creation, the image of a skilled dealmaker. Then satisfy every one of them. She discounted planes whose costs were already declining due to economies of scale, announced workforce expansion at the Fort Worth plant, and publicly supported regulatory reform. Trump received his negotiation victory. Lockheed secured current contracts and additional orders worth billions over the following years. + +The lesson is not about flattery. It is about diagnosis. Hewson identified that the obstacle was not price -- it was image. Once she addressed the actual interest, the positional conflict dissolved. + +--- + +## Prompts + +**Prompt 1 -- Interest Mapping:** +> I am preparing for a negotiation about [describe: partnership, contract, equity, vendor deal]. The other party's stated position is [describe]. Using the positions-to-interests framework, help me: (1) identify at least five possible underlying interests behind their position, including ego, fear, and relationship factors, (2) map my own interests separately from my position, (3) identify where our interests overlap or are non-competing, and (4) suggest three creative options that address both sets of interests. Context: [company stage, relationship history, power dynamics]. + +**Prompt 2 -- Empathy Deployment Plan:** +> I need to negotiate with [describe counterparty] who is emotionally invested in [describe their concern]. Using the Lead-with-Need model (Observe, Understand, Respect, Solve), help me draft: (1) three open-ended questions to surface their real interests, (2) two empathetic acknowledgement statements that do not concede my position, (3) a proposed physical setup for the meeting, and (4) a bridging statement that transitions from empathy to problem-solving. My situation: [describe]. + +**Prompt 3 -- Roadmap to Resolution Session Design:** +> I have reached an impasse in a negotiation about [describe]. Both sides are locked in positional bargaining. Design a cooperative session using the six-step Roadmap to Resolution: (1) script my opening statement to redirect the conversation, (2) list ten open-ended questions to surface interests, (3) propose a whiteboard exercise for joint brainstorming, and (4) define evaluation criteria for the options we generate. Current positions: [ours] vs. [theirs]. Relationship importance: [high/medium/low]. + +**Prompt 4 -- Formidable Counterparty Strategy:** +> I am negotiating with a counterparty who holds significantly more power than I do -- [describe: large client, dominant investor, regulatory body, acquirer]. A competitive approach will fail. Using the cooperative negotiation framework, help me: (1) hypothesise their ego, image, and relationship interests, (2) identify low-cost concessions I can offer that satisfy their intangible needs, (3) design a strategy to give them a visible "win" while protecting my core interests, and (4) prepare fallback positions if cooperation is not reciprocated. + +--- + +## Use Cases + +**Early-Traction SaaS Company Negotiating a Channel Partnership** + +A 15-person B2B SaaS company needs a distribution partnership with a large systems integrator. The integrator's position: exclusive rights for the enterprise segment, 40% revenue share, and co-branding that subordinates the startup's identity. The founder's position: non-exclusive, 20% share, and independent branding. + +Positional bargaining produces a stalemate. The cooperative approach begins with interest mapping. The integrator's interests: their sales team needs a differentiated product to pitch against competitors; their VP of partnerships needs a visible win for the quarterly business review; they fear investing in training only to see the startup sign a rival integrator. The founder's interests: reach enterprise buyers without building a direct sales team; maintain brand identity for future fundraising; avoid dependency on a single channel. + +The resolution: a 12-month "preferred partner" designation (not exclusive, but the integrator is the only partner in their specific vertical), 30% revenue share on deals they originate (splitting the difference on economics but tying it to origination), co-branded landing pages with equal logo treatment, and a commitment that the startup will not sign a competing integrator in the same vertical for 12 months. The integrator's VP gets a headline for the QBR. The founder retains optionality. Neither party's stated position survives, but both parties' interests are fully served. + +**Growth-Stage Founder Resolving a Co-Founder Dispute** + +Two co-founders of a Series A company disagree on strategic direction. One wants to double down on the current market; the other wants to expand into an adjacent vertical. The positional argument has lasted months and is paralysing the executive team. + +A cooperative intervention starts with separate interest conversations. Founder A's interests: fears diluting focus and repeating the mistake of a previous startup that expanded too early; wants validation that the current strategy is working. Founder B's interests: sees the current market commoditising and fears being caught without diversification; wants to be seen as the visionary partner, not the operational one. + +Neither interest conflicts with the other. The resolution: a 90-day experiment in the adjacent vertical with a capped budget and pre-defined success metrics, run by Founder B, while Founder A leads an intensified push in the core market. If the experiment hits metrics, expansion proceeds. If not, full resources return to the core. Both founders' fears are addressed, both egos are served, and the company gets data instead of arguments. + +--- + +## Anti-Patterns + +**Cooperation as conflict avoidance.** The cooperative approach is not permission to avoid hard conversations. Founders who use "let's find a win-win" as a euphemism for "I'm uncomfortable saying no" will consistently leave value on the table. Cooperation requires the courage to surface difficult interests -- including your own -- and to hold firm on those interests even when the process feels tense. + +**Skipping the sequence.** The Roadmap to Resolution has a strict order for a reason. Jumping to option evaluation before interests are fully surfaced produces solutions that address the wrong problem. The most common violation: brainstorming solutions before the other party has finished explaining their perspective. Patience in steps one through three pays compound returns in steps four through six. + +**Projecting your interests onto the other party.** Assuming you know what they want without asking is positional bargaining with a cooperative veneer. The hospital litigation manager did not assume the patient wanted money -- he asked, and discovered she wanted an apology. The discipline of genuine inquiry cannot be faked. + +**Deploying empathy as a tactic.** When empathy is performed rather than practised, the counterparty detects it. The result is worse than no empathy at all -- it registers as manipulation. Empathy requires genuine curiosity about the other person's experience, even if you plan to negotiate aggressively on substance. + +**Abandoning cooperation at the first impasse.** Cooperative negotiation is not a fallback for when competition fails; it is a different operating system. Switching back to competitive bargaining at the first sign of difficulty signals that the cooperative posture was insincere. Commit to the process or do not begin it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder alignment and early advisor relationships | Interests are personal and existential -- identity, vision, fear of failure. The Roadmap to Resolution prevents founding teams from entrenching positions before the company even exists. | +| Validation | First customer deals and pilot negotiations | Weak BATNA makes cooperation essential, not optional. Surface the pilot customer's underlying fears (risk, internal credibility) and build the deal around removing those fears rather than arguing price. | +| Early Traction | Vendor contracts, partnership terms, early hires | Negotiations multiply rapidly. Establish cooperative norms now -- they compound. An early hire negotiation that surfaces the candidate's real interests (autonomy, learning, equity upside) costs less and retains longer than one that only haggles salary. | +| Growth | Fundraising, enterprise sales, strategic alliances | Multi-stakeholder negotiations demand interest mapping at scale. Each investor, board member, and procurement officer has distinct interests. Map them individually, not as a monolith. | +| Scale | M&A, cross-border deals, regulatory negotiation | Cultural adaptation of empathy becomes critical. The Lead-with-Need model must account for indirect communication norms, hierarchical decision-making, and relationship-first cultures. | + +--- + +## Output Template + +```markdown +# Cooperative Negotiation Preparation: [Deal/Context] + +## Parties and Power Map +- **Our side:** [Individuals, roles, decision authority] +- **Their side:** [Individuals, roles, decision authority] +- **Power balance:** [Symmetric / Asymmetric — describe] +- **Relationship importance:** [Critical / Important / Transactional] + +## Positions vs. Interests +| Issue | Our Position | Our Interests (Why) | Their Position | Their Likely Interests (Why) | +|-------|-------------|---------------------|----------------|------------------------------| +| [Issue 1] | | | | | +| [Issue 2] | | | | | + +## Intangible Interest Scan +- **Ego factors:** [Who needs to look good? To whom?] +- **Fear factors:** [What is each party afraid of losing?] +- **Relationship factors:** [What existing relationships constrain or enable the deal?] +- **Circumstantial pressures:** [Deadlines, budget cycles, reporting periods?] + +## Roadmap to Resolution — Session Plan +1. **Redirect statement:** "[Draft opening to steer away from positions]" +2. **Key questions:** [List 5-7 open-ended questions] +3. **Listening targets:** [What unstated interests to watch for] +4. **Brainstorming format:** [Whiteboard / shared doc / structured exercise] +5. **Evaluation criterion:** "What option best serves both interest sets?" + +## Creative Options (Pre-Session Hypotheses) +1. [Option addressing their ego + our economics] +2. [Option addressing their fear + our timeline] +3. [Option addressing shared interests] + +## Empathy Plan +- **Acknowledgement statement:** "[Draft]" +- **Common ground:** [Shared experiences, values, or pressures] +- **Environment:** [Meeting setup, seating, tone] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- The theoretical foundation for interest-based negotiation; this skill translates Fisher and Ury's four principles into conversational execution and empathy deployment. +- **[Delivering the Deal](../../content/skills/negotiation/delivering-the-deal.md)** -- Picks up where cooperative negotiation leaves off: preparation checklists, obstacle management, and satisfaction engineering for closing and post-deal durability. +- **[Competitive Negotiation](../../content/skills/negotiation/competitive-negotiation.md)** -- The value-claiming counterpart; once the pie is expanded through cooperative techniques, competitive tactics determine how it is divided. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust enables the vulnerability required to share real interests; low trust makes cooperative negotiation structurally impossible. +- **[Thomas-Kilmann Conflict](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- Provides the diagnostic for when to deploy a cooperative approach versus competitive, compromising, or avoidant modes. +- **[Prisoners Dilemma and Cooperation](../../content/skills/game-theory/prisoners-dilemma-and-cooperation.md)** -- The game-theoretic foundation for why cooperation produces better joint outcomes and what structural conditions make it sustainable. diff --git a/plugins/foreman/skills/covey-seven-habits/SKILL.md b/plugins/foreman/skills/covey-seven-habits/SKILL.md deleted file mode 120000 index 58bb79a..0000000 --- a/plugins/foreman/skills/covey-seven-habits/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/covey-seven-habits.md \ No newline at end of file diff --git a/plugins/foreman/skills/covey-seven-habits/SKILL.md b/plugins/foreman/skills/covey-seven-habits/SKILL.md new file mode 100644 index 0000000..a131701 --- /dev/null +++ b/plugins/foreman/skills/covey-seven-habits/SKILL.md @@ -0,0 +1,211 @@ +--- +name: "covey-seven-habits" +description: "Applies Stephen Covey's Seven Habits framework for personal and + interpersonal effectiveness, progressing from dependence through independence + to interdependence. Covers proactivity, mission clarity, prioritization, + Win/Win thinking, empathic listening, synergy, and renewal. Use when + conducting personal effectiveness audits, drafting mission statements, + preparing Win/Win negotiations, resolving co-founder conflicts, designing + founder renewal plans to prevent burnout, or building character-based + leadership culture." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - personal-effectiveness + - leadership + - character-ethics + - habits + - interpersonal-skills + - self-management +related_skills: + - eisenhower-matrix + - emotional-intelligence + - grow-model + - tuckman-team-stages +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Covey's Seven Habits of Highly Effective People + +The self-help industry generates roughly $14 billion annually in the United States alone, and the vast majority of that output is forgettable within months of publication. Stephen Covey's *The Seven Habits of Highly Effective People*, published in 1989, is the notable exception -- over 40 million copies sold, translated into 40 languages, and still assigned in MBA programs three decades later. The book's durability is not a marketing phenomenon; it reflects a genuine intellectual contribution. Covey drew a sharp distinction between what he called the "personality ethic" (techniques, shortcuts, positive mental attitude) and the "character ethic" (principles, integrity, deep competence). His argument -- that lasting effectiveness flows from character, not charisma -- was unfashionable when published and remains countercultural in a business environment that rewards performative confidence. For entrepreneurs, who must build trust with investors, employees, customers, and partners simultaneously, the character ethic is not optional. + +--- + +## The Framework + +Covey organizes the seven habits along a maturity continuum: from dependence (others take care of me) through independence (I take care of myself) to interdependence (we accomplish more together). Most self-help literature stops at independence. Covey argues that interdependence -- the ability to collaborate effectively while maintaining personal integrity -- is the highest and most productive state. + +### The Maturity Continuum + +``` +DEPENDENCE → INDEPENDENCE → INTERDEPENDENCE + (Habits 1-3) (Private Victory) (Habits 4-6) (Public Victory) + ↓ + Habit 7: Renewal +``` + +### Habits 1-3: Private Victory (Self-Mastery) + +**Habit 1 -- Be Proactive** +Proactivity is not mere initiative. It is the recognition that between stimulus and response lies a space, and within that space lies the freedom to choose. Reactive people are driven by feelings, circumstances, and conditions. Proactive people are driven by values. The practical test: does the person focus on their Circle of Influence (things they can affect) or their Circle of Concern (things they worry about but cannot control)? + +For entrepreneurs, proactivity means focusing energy on what can be built, tested, and changed rather than on market conditions, competitor actions, or investor sentiment that lie outside direct control. + +**Habit 2 -- Begin with the End in Mind** +Every meaningful creation happens twice: first as a mental conception, then as a physical reality. Habit 2 is about ensuring that the first creation is deliberate. Covey advocates writing a personal mission statement -- a constitution that governs decision-making. For founders, this extends to a company mission statement that is genuinely operational rather than decorative. + +The principle is architectural: if you do not define what success looks like before you begin, you will optimize for metrics that may be irrelevant or harmful. Many startups achieve impressive growth toward destinations nobody actually wanted to reach. + +**Habit 3 -- Put First Things First** +Where Habit 2 is strategic (what matters most?), Habit 3 is executional (how do you spend your time?). This is where the Eisenhower Matrix enters Covey's framework, distinguishing urgent from important. Habit 3 demands that Quadrant II activities -- important but not urgent -- receive protected time. The habit requires saying no to good opportunities in order to say yes to the best ones. + +### Habits 4-6: Public Victory (Interdependence) + +**Habit 4 -- Think Win/Win** +Win/Win is not a negotiation tactic. It is a frame of mind that seeks mutual benefit in all interactions. Covey identifies six interaction paradigms: + +| Paradigm | Description | Entrepreneurial Context | +|----------|-------------|------------------------| +| Win/Win | Both parties benefit | Partnerships, equity negotiations, customer relationships | +| Win/Lose | I benefit at your expense | Short-term supplier squeezing, zero-sum competition | +| Lose/Win | I accommodate at my expense | Founder undervaluing their equity, accepting unfavorable terms | +| Lose/Lose | Neither party benefits | Vindictive competition, destructive conflicts | +| Win | I focus only on my outcome | Transactional relationships with no regard for the other side | +| Win/Win or No Deal | We find mutual benefit or walk away | The most mature option when ongoing relationship matters | + +The entrepreneurial application is direct: founders negotiate constantly -- with co-founders, employees, investors, customers, partners. Those who default to Win/Lose may win individual negotiations but destroy the trust infrastructure on which scaling depends. + +**Habit 5 -- Seek First to Understand, Then to Be Understood** +Most people listen with the intent to reply, not to understand. Covey calls this "autobiographical listening" -- filtering everything through one's own experience. Empathic listening -- genuinely entering the other person's frame of reference -- is rare and powerful. For founders, this habit transforms customer discovery, employee management, and investor relations. The founder who truly understands a customer's problem before proposing a solution builds products that matter. + +**Habit 6 -- Synergize** +Synergy is not a buzzword in Covey's framework; it is a specific phenomenon: the whole becoming greater than the sum of its parts. Synergy emerges when people with different perspectives engage in open, trusting communication and produce solutions that none could have conceived alone. The preconditions are the preceding habits: proactivity, clarity of purpose, prioritization, mutual benefit, and empathic understanding. + +### Habit 7: Renewal + +**Habit 7 -- Sharpen the Saw** +Sustainable effectiveness requires regular renewal across four dimensions: + +- **Physical**: Exercise, nutrition, rest +- **Mental**: Reading, learning, writing +- **Social/Emotional**: Relationships, service, empathy +- **Spiritual**: Meditation, values clarification, nature + +Covey's argument is that neglecting renewal in any dimension degrades performance across all dimensions. For entrepreneurs, who are notorious for sacrificing health and relationships on the altar of their venture, Habit 7 is not indulgent -- it is structural. Burned-out founders make poor decisions. + +--- + +## Prompts + +**Prompt 1 -- Personal Effectiveness Audit:** +> Evaluate my current effectiveness against Covey's Seven Habits. For each habit, I will describe my typical behavior and you assess my maturity level (1-5) and recommend specific improvements. Here is my self-assessment: Habit 1 (Proactivity): [describe]. Habit 2 (End in Mind): [describe]. Habit 3 (First Things First): [describe]. Habit 4 (Win/Win): [describe]. Habit 5 (Understand First): [describe]. Habit 6 (Synergize): [describe]. Habit 7 (Sharpen the Saw): [describe]. + +**Prompt 2 -- Mission Statement Workshop:** +> Help me draft a personal mission statement using Covey's Habit 2 process. Ask me questions about my core values, the roles I play (founder, partner, parent, friend, community member), and the legacy I want to create. Then synthesize my answers into a mission statement of 3-5 sentences that I can use as a decision-making filter. Also help me translate this into a company mission statement that aligns with my personal one. + +**Prompt 3 -- Win/Win Negotiation Prep:** +> I have an upcoming negotiation about [describe: fundraising, partnership, hiring, contract]. Help me prepare using Covey's Win/Win framework. What does the other party want and need? What do I want and need? Where is the overlap? What creative options might expand the pie rather than divide it? What is my "no deal" walk-away point? Prepare me with a negotiation approach that prioritizes relationship preservation alongside outcome achievement. + +**Prompt 4 -- Founder Renewal Plan:** +> I have been running my startup for [timeframe] and I recognize signs of burnout: [describe symptoms]. Help me design a Habit 7 renewal plan across Covey's four dimensions (physical, mental, social/emotional, spiritual). For each dimension, recommend specific, time-bounded practices that fit within a founder's schedule. Include weekly minimums, warning signs of neglect, and accountability mechanisms. + +--- + +## Use Cases + +**Idea-Stage Founder Clarifying Direction** +A first-time founder with three potential business ideas and scattered energy uses Habits 1-3 to establish personal clarity. Habit 1: she identifies that her anxiety about competitor activity is Circle of Concern waste and refocuses on her Circle of Influence -- customer conversations and prototype development. Habit 2: she writes a mission statement centered on democratizing financial literacy, which immediately eliminates one of the three ideas as misaligned. Habit 3: she audits her weekly schedule and discovers that 60% of her time goes to networking events (QIII) rather than customer discovery (QII). The result is not a business plan but something more valuable: a focused founder. + +**Growth-Stage Co-Founder Conflict Resolution** +Two co-founders at a 50-person company are deadlocked on product direction. Applying Habit 5, they agree to spend one hour each genuinely articulating the other's position before advocating their own. The exercise surfaces a misunderstanding: one founder's insistence on enterprise features is driven by a specific large-customer conversation the other had not been briefed on. With mutual understanding established, Habit 6 produces a synthesis: a modular architecture that serves both enterprise and SMB segments. The conflict was not about competing visions -- it was about incomplete information filtered through insufficient empathy. + +**Scale-Stage CEO Building a Leadership Team** +A CEO at a 300-person company applies the entire Covey framework to her leadership approach. Habit 4 structures her compensation philosophy (equity packages designed for Win/Win alignment). Habit 5 transforms her quarterly reviews from performance monologues into genuine dialogue. Habit 7 leads her to institute "no-meeting Wednesdays" for the entire company, protecting renewal time at the organizational level. The result, measured over 18 months: employee NPS rises from 32 to 61, and voluntary attrition drops from 24% to 11%. + +--- + +## Anti-Patterns + +1. **Treating the habits as a checklist rather than a developmental sequence.** Covey is explicit that the habits build on each other. Attempting Habit 6 (Synergize) without first mastering Habit 5 (Understand First) produces false collaboration -- people agreeing without genuinely engaging with different perspectives. + +2. **Weaponizing "proactivity" to blame people for external circumstances.** Habit 1 does not mean that structural disadvantages, market collapses, or bad luck are the individual's fault. It means that the individual chooses their response to these circumstances. Leaders who use "be proactive" to dismiss legitimate complaints about working conditions have misunderstood the concept entirely. + +3. **Writing a mission statement and filing it away.** Habit 2 requires a living document that is reviewed regularly and used as an active decision-making filter. A mission statement that sits in a drawer is performative, not operational. + +4. **Confusing Win/Win with compromise.** Compromise means both sides give something up. Win/Win means finding a creative solution where both sides gain. The distinction matters: compromise breeds resentment over time, while genuine Win/Win builds trust and expands future possibilities. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Habits 1-3 (Private Victory) | The founder's personal effectiveness is the company's effectiveness. Proactivity, mission clarity, and ruthless prioritization are survival skills. Interdependence habits matter less because the team is small or nonexistent. | +| Validation | Habit 5 dominance | Customer discovery IS empathic listening applied to market problems. The founder who masters "seek first to understand" during validation builds products that actually solve problems rather than products that reflect the founder's assumptions. | +| Early Traction | Habits 4-6 emerge | The team is growing. Win/Win structures (equity, compensation, role design) become critical. Synergy with early employees determines whether the company builds leverage or just adds headcount. | +| Growth | Full framework integration | All seven habits are in play. The founder's character -- proactivity, integrity, empathy, renewal -- sets the cultural tone for the organization. Deficits in any habit are amplified by organizational scale. | +| Scale | Habit 7 becomes existential | At scale, founder burnout is an enterprise risk. Renewal is not personal indulgence -- it is risk management. The CEO must also model renewal for the organization, creating a culture where sustainable performance is valued over heroic exhaustion. | + +--- + +## Output Template + +```markdown +# Personal Effectiveness Assessment (Covey Seven Habits) + +**Name:** [Your name] +**Date:** [Date] +**Company Stage:** [Stage] + +## Habit Maturity Scorecard + +| Habit | Self-Rating (1-5) | Evidence | Priority Action | +|-------|-------------------|----------|-----------------| +| 1. Be Proactive | [Score] | [Behavior example] | [Specific action] | +| 2. Begin with End in Mind | [Score] | [Mission clarity level] | [Specific action] | +| 3. Put First Things First | [Score] | [QII time %] | [Specific action] | +| 4. Think Win/Win | [Score] | [Recent negotiation example] | [Specific action] | +| 5. Seek First to Understand | [Score] | [Listening quality] | [Specific action] | +| 6. Synergize | [Score] | [Collaboration example] | [Specific action] | +| 7. Sharpen the Saw | [Score] | [Renewal practices] | [Specific action] | + +## Current Maturity Level +- [ ] Dependence +- [ ] Independence (Private Victory achieved) +- [ ] Interdependence (Public Victory achieved) + +## Top 3 Development Priorities +1. [Habit #] -- [Specific development plan with timeline] +2. [Habit #] -- [Specific development plan with timeline] +3. [Habit #] -- [Specific development plan with timeline] + +## Renewal Plan (Habit 7) + +| Dimension | Current Practice | Target Practice | Weekly Minimum | +|-----------|-----------------|-----------------|----------------| +| Physical | [Current] | [Target] | [Hours/week] | +| Mental | [Current] | [Target] | [Hours/week] | +| Social/Emotional | [Current] | [Target] | [Hours/week] | +| Spiritual | [Current] | [Target] | [Hours/week] | +``` + +--- + +## Related Skills + +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- Habit 3 operationalizes the Eisenhower Matrix; the matrix is the tactical tool while the Seven Habits provide the character foundation that makes consistent use of it possible. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Habit 5 (empathic listening) and Habit 4 (Win/Win thinking) are expressions of emotional intelligence applied to professional relationships. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Habit 4's Win/Win orientation finds its operational methodology in Fisher and Ury's principled negotiation framework. +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- The coaching framework that helps individuals develop specific habits through structured goal-setting and action planning. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Teams moving through Tuckman's stages benefit when members practice Habits 4-6, particularly during the Storming phase where Win/Win thinking and empathic listening prevent destructive conflict. +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Habit 7 (Sharpen the Saw) provides the philosophical foundation for the structured renewal and burnout prevention practices leaders need. diff --git a/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md b/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md deleted file mode 120000 index 0dbc1e1..0000000 --- a/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-collaboration-and-context.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md b/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md new file mode 100644 index 0000000..c192285 --- /dev/null +++ b/plugins/foreman/skills/creative-collaboration-and-context/SKILL.md @@ -0,0 +1,219 @@ +--- +name: "creative-collaboration-and-context" +description: "Explores how creative collaboration produces outcomes neither + party could achieve alone, covering reference points without copying, the role + of creative mythology, the prism of self as competitive advantage, context as + meaning-maker, cross-domain adaptation, and translation as a creative act. Use + when building creative partnerships, navigating co-founder dynamics, + assembling creative teams, repositioning a product through context change, + adapting business models across industries, translating technical innovation + for new markets, or understanding why the same idea succeeds in one context + and fails in another." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - collaboration + - context + - adaptation + - translation + - point-of-view + - reference + - creative-teams + - positioning +related_skills: + - creative-shaping-and-craft + - creative-flow-and-inspiration + - creative-completion-and-renewal +author: "Fatih Guner" +related_content: + - kind: template + ref: stakeholder-map +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Collaboration and Context + +Every collaboration is a prism. A single beam of light enters -- the shared problem, the market opportunity, the creative brief -- and a spectrum emerges. The colours that exit bear no resemblance to the monochrome that entered. "The 'self' has many distinct aspects," the text observes. "Creativity is an internal discussion between these aspects of self." When two or more creators bring their distinct prisms into contact, the refraction compounds. the book's deeper claim is that collaboration is not merely additive: "Nothing begins with us." All creative work is already a collaboration -- with prior art, with the culture, with the tools, with the audience, and with the multiple selves inhabiting the single creator. Understanding this transforms the entrepreneur's relationship with partnership, influence, positioning, and the act of carrying ideas across boundaries. + +--- + +## The Framework + +Seven principles compose the book's philosophy of creative collaboration and context. They range from the interpersonal to the structural, from the way two minds interact to the way a single idea changes meaning when it crosses a border. + +### 1. Collaboration -- The Internal and External Dialogue + +the text begins not with teamwork but with a provocation: the creator is already a committee. "There are many different hats the artist wears, and creativity is an internal discussion between these aspects of self. The negotiation continues until the selves create the best work they can together." The inspired-artist self and the craftsperson self are often in conflict. The visionary and the operator, the risk-taker and the risk-manager -- each entrepreneur carries this parliament. + +External collaboration, then, is an extension of internal collaboration, with one critical addition: the collaborator introduces a filter the creator does not possess. the text notes that even the audience participates in the creative act: "You could have a distinct idea of what a piece means, how it functions, or why it's pleasing -- and someone else can like it or dislike it for an entirely different reason." The purpose of sharing work is not alignment of interpretation but magnitude of charge: "We can only hope that the magnitude of the charge we experience reverberates as powerfully for others as it does for us." + +For the entrepreneur, this reframes co-founder dynamics, advisory relationships, and team composition. The value of a collaborator is not agreement but refraction -- the capacity to produce colours the founder cannot produce alone. + +### 2. Point of Reference -- Using Without Copying + +Exposure to others' work is inevitable and necessary. The question is how to absorb influence without becoming derivative. the text observes that encountering radically new work often provokes initial rejection: "If you're looking for solutions to a problem, you may react in a strongly negative way to an option that springs forth. This can be when the idea is so new that you don't have any context for it." + +The instruction is to linger with strong reactions rather than fleeing them. "Be aware of strong responses. If you're immediately turned off by an experience, it's worth examining why. Powerful reactions often indicate deeper wells of meaning." The competitive product that irritates, the customer request that seems absurd, the market trend that feels alien -- each may be a reference point pregnant with unrecognised value. + +Revolutionary ideas, the text notes, "have no context. They invent their own." The entrepreneur who can tolerate the discomfort of context-free ideas -- sitting with them long enough for the brain to build new patterns -- will see opportunities invisible to those who reject the unfamiliar on contact. + +### 3. Apocrypha -- The Stories We Tell About Creation + +Every industry has its origin myths. The garage startup. The napkin sketch that became a billion-dollar company. The founder who coded the MVP in a weekend. the text is disarmingly frank about such stories: "The stories about how works get made and the rituals of the artists who make them are generally exaggerated, and often pure fiction." + +This matters for the entrepreneur because creative mythology shapes creative behaviour. The founder who believes great products require a single visionary genius will structure their company differently from one who believes great products emerge from messy collaboration. Both beliefs are apocryphal -- simplified narratives overlaid on processes too complex to fully describe. "In cases when the artist thinks they know, their interpretation may not be accurate or the whole story." + +The practical counsel: absorb creative mythology for energy and inspiration, but do not mistake it for a reproducible method. "To believe a specific method is responsible for the quality of a work is misleading. Especially if it causes you to repeat that process in hopes of achieving a similar result." + +### 4. The Prism of Self -- Your Unique Lens as Value + +"We inhabit many different versions of a changing self," the text argues. The self is not a fixed point but a prism: "Neutral events enter, and are transformed into a spectrum of feelings, thoughts, and sensations. All this information is processed distinctively by each aspect of self, refracting life's light in its own way, and emitting different shades of art." + +For the entrepreneur, this means personal perspective is not a liability to be managed or a bias to be eliminated. It is a competitive advantage. Two founders looking at the same market will see different opportunities, not because one is smarter, but because their prisms refract differently. "Not every work can reflect all of our selves," the text acknowledges. The practice is to embrace the prism rather than attempting to grind it into a neutral lens. + +The kaleidoscope metaphor extends to teams: "Like a kaleidoscope, we can adjust the aperture on our vision and change the results." A team composed of similar prisms produces monochrome output. A team of diverse prisms produces a spectrum -- provided the environment allows each prism to refract freely rather than conforming to a single sanctioned lens. + +### 5. Context -- The Frame Changes the Painting + +"Imagine a flower in an open meadow," the text argues. "Now take the same flower and slip it into the barrel of a rifle. Or place it on a gravestone. Notice in each case how you feel. The significance changes." His principle is absolute: "The context changes the content." + +This single insight has profound implications for product strategy, positioning, and market entry. The identical product launched at a different time, in a different market, alongside different competitors, at a different price point, is a different product. Andy Warhol's Brillo boxes in a grocery store are packaging; in a museum, they are art. The startup that repositions an existing technology from enterprise to consumer (or the reverse) is not merely changing the customer. It is changing the meaning of the product. + +the text offers a practical catalogue of contextual pairs -- soft/loud, fast/slow, high/low, close/far, bright/dark, large/small -- and advises: "When a piece isn't living up to your expectations, consider changing the context. Look past the principal element, examine the variables around it." + +### 6. Adaptation -- Practice, Absorption, and Growth + +Adaptation, in this framework, is not strategic flexibility but something more organic. He describes the phenomenon of practising a skill, resting, and returning to find the skill has mysteriously improved: "You wake up one morning, transported to this new reality where you suddenly have more skill than you did before you went to sleep." + +The entrepreneurial parallel is the assimilation of market knowledge. The founder who immerses deeply in a customer segment, then steps away to work on something else, often returns with insights that immersion alone could not produce. the text frames this as a cycle: "Practice gets us part of the way there. Then it takes time for practice to be absorbed into the body." The passive element of adaptation is as important as the active one. + +At a broader level, adaptation describes the transfer of capability across domains. "Teaching yourself to play piano will likely improve your hearing. And you may well get better at math." The entrepreneur whose previous career was in an unrelated field carries skills that are not obsolete but untranslated. The act of translation is itself creative. + +### 7. Translation -- Carrying Fire Across Borders + +"Art is an act of decoding," the text argues. "We receive intelligence from Source, and interpret it through the language of our chosen craft." Translation is the creative act of converting insight from one domain into expression within another. + +Every market entry is a translation. The product designed for developers, rewritten for healthcare administrators. The business model that works in logistics, adapted for education. The founder who has deep expertise in one domain and enters another is not starting from zero -- they are translating. + +the text notes that fluency matters: "The more we develop, expand, and sharpen our skills, the more fluent we become." But he also cautions that technical mastery is neither necessary nor sufficient: "A guitarist could play the most complex solo and while technically impressive, it might not connect emotionally, while an amateur could perform a simplistic three-chord song and move you to tears." The quality of translation depends not on sophistication but on the integrity of what is being translated. + +--- + +## Prompts + +**Prompt 1 -- Collaboration Audit:** +> Map the internal and external collaborations in my venture. Internally: which aspects of my own thinking are in productive tension (visionary vs. operator, risk-taker vs. risk-manager)? Externally: who are my current collaborators (co-founders, advisors, team members, customers), and what unique prism does each bring? Where am I surrounded by similar prisms, and where is the spectrum missing a colour? Recommend specific additions or shifts to maximise creative refraction. + +**Prompt 2 -- Context Reframe:** +> My product [describe product] is currently positioned in [describe context: market, price point, customer segment, competitive frame]. Apply the book's principle that "the context changes the content." Generate five alternative contextual frames -- different markets, adjacent use cases, different price positions, different competitive reference sets -- and describe how each changes the perceived meaning of the same product. Which reframe surfaces the most underexploited value? + +**Prompt 3 -- Translation Exercise:** +> I have deep expertise in [domain A] and am building a product for [domain B]. Identify the core principles, methods, and mental models from domain A that are most translatable to domain B. For each, describe the translation -- not a direct copy, but an adaptation that honours the original insight while fitting the grammar of the new domain. Where does my domain A expertise give me a perspective that native domain B participants cannot see? + +**Prompt 4 -- Apocrypha Audit:** +> What origin stories and creative mythologies am I operating under? [Describe beliefs about how great products get built, what successful founders look like, what process produces breakthroughs.] For each, apply the book's warning that these stories are "generally exaggerated, and often pure fiction." What would my strategy look like if I abandoned each mythology and replaced it with an honest assessment of what I actually know about how my best work has been produced? + +--- + +## Use Cases + +**Idea-stage co-founders with misaligned creative visions** + +Two co-founders -- one a designer, one an engineer -- disagree on the product's direction. The designer wants to pursue an unconventional user interface; the engineer argues for convention because it reduces development time. Viewed through the book's collaboration framework, the disagreement is not a problem to be resolved but a productive tension to be held. The designer's prism refracts toward novelty; the engineer's toward reliability. The intervention is not to choose one vision but to let both prisms operate: prototype the unconventional interface cheaply (honouring the designer's filter) while building it on the most conventional backend possible (honouring the engineer's filter). The product that emerges carries both colours -- innovative where the customer sees it, robust where the customer does not. + +**Validation-stage product receiving contradictory market signals** + +A founder testing a B2B product receives enthusiastic responses from small businesses but indifference from the enterprise segment originally targeted. Applying the context principle, she recognises that the same product has different meanings in different contexts: in the small business context, it fills a painful gap; in the enterprise context, it duplicates existing tooling. Rather than dismissing the small business signal as off-strategy, she examines the contextual frame that makes the product valuable there and repositions accordingly. The product itself changes minimally; the context changes everything. + +**Growth-stage company adapting a model across geographies** + +A SaaS platform successful in North America is expanding to Southeast Asia. The temptation is direct replication. Applying the book's translation principle, the leadership team recognises that market entry is creative translation, not mechanical copying. They identify the core principles that drove success in North America (the "essence" that survives translation) and the surface-level features that were context-dependent (pricing structure, onboarding flow, support model). The Southeast Asian launch preserves the principles while reinventing the surface -- and discovers that some of the reinventions improve the original product. + +--- + +## Anti-Patterns + +**Seeking collaborators who confirm rather than refract.** The most common collaboration error is assembling a team of similar prisms. The result is comfortable and coherent -- and monochrome. the book's framework values the discomfort of unfamiliar refraction. If every collaborator sees the product the same way, the collaboration is producing no spectrum. + +**Copying reference points instead of metabolising them.** There is a difference between studying a competitor's approach and cloning it. the book's guidance on point of reference is to let influence enter, be processed through one's own prism, and emerge transformed. The entrepreneur who reproduces a competitor's feature set has skipped the metabolic step. What emerges is imitation, not translation. + +**Treating apocrypha as instruction manuals.** The origin story of a successful company is a narrative constructed after the fact, not a recipe. The founder who copies another company's process because they read about it in a case study is, in the book's terms, confusing art history with art reality. "Art reality is forever unknown." + +**Ignoring context while optimising content.** The product team that obsesses over feature quality while neglecting positioning, timing, competitive frame, and market context is painting a masterpiece and hanging it in a broom closet. Context is not secondary to content. It is constitutive of it. + +**Assuming adaptation is immediate.** the text describes adaptation as a process that includes a necessary "recovery phase." The founder who enters a new market expects instant fluency and interprets the initial awkwardness as failure rather than as the natural struggle phase that precedes the leap. "Practice gets us part of the way there. Then it takes time for practice to be absorbed into the body." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder prism alignment; initial context selection | The founding team's combined prisms determine which spectrum of opportunity is visible; context choice (which market, which frame) is the most consequential creative decision at this stage | +| Validation | Metabolising market reference points; absorbing contradictory signals | The market provides reference points that may initially provoke rejection; the practice is to sit with strong reactions rather than dismissing unfamiliar data | +| Early Traction | Translation of founding insight into scalable form; team prism diversity | The original insight must be translated from founder-intuition into product-language that a team can execute; hiring for prism diversity becomes critical | +| Growth | Context management across segments and geographies; adaptation cycles | The same product means different things in different contexts; managing this multiplicity without losing essence is the central challenge | +| Scale | Apocrypha management; preventing the company's own origin story from becoming a cage | The company's founding mythology can calcify into doctrine; the practice is to honour the story's energy while refusing its authority as method | + +At early traction, the translation challenge is acute. The founder's intuitive understanding of the product must be encoded in language, processes, and specifications that others can execute without losing the original charge. This is the moment when the book's observation that "there is no direct conversion from abstract thought to the material world" becomes most visible. Every handoff -- from founder to designer, from designer to engineer, from engineer to customer -- is an act of translation, and each translation carries the risk of losing essential signal while preserving inessential form. + +--- + +## Output Template + +```markdown +# Collaboration and Context Analysis -- [Project/Product Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Prism Map + +| Collaborator | Role | Unique Lens/Filter | Blind Spots | Refraction Value | +|-------------|------|-------------------|-------------|-----------------| +| [Name] | [Role] | [What they see that others miss] | [What they consistently overlook] | [What their presence adds to the spectrum] | + +## Spectrum Gaps +[Perspectives, backgrounds, or cognitive styles missing from the current team] + +## Context Analysis + +| Contextual Variable | Current Setting | Alternative Setting | Meaning Change | +|--------------------|-----------------|--------------------|--------------------| +| Market segment | [Current] | [Alternative] | [How meaning shifts] | +| Price position | [Current] | [Alternative] | [How meaning shifts] | +| Competitive frame | [Current] | [Alternative] | [How meaning shifts] | +| Timing | [Current] | [Alternative] | [How meaning shifts] | + +## Translation Log +[For cross-domain moves: what transfers, what must be reinvented] +- **Principle that translates:** [Principle] -- Adaptation: [How it changes] +- **Surface feature that does not translate:** [Feature] -- Replacement: [New approach] + +## Apocrypha Check +[Creative mythologies currently influencing decisions -- flagged for examination] +1. [Myth] -- Source: [Where it came from] -- Risk: [How it constrains] + +## Collaboration Design Recommendations +[Specific changes to team composition, collaboration structure, or context] +``` + +--- + +## Related Skills + +- **[Creative Shaping and Craft](../../content/skills/creative/creative-shaping-and-craft.md)** -- Shaping operates on the output of collaboration; the prism metaphor extends from person to process, where each shaping technique refracts the work differently. +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- Collaboration is one of the richest environments for creative surprise; other people's prisms produce the unexpected input that serves as a precondition for inspiration. +- **[Creative Completion and Renewal](../../content/skills/creative/creative-completion-and-renewal.md)** -- Collaborative work faces distinct completion challenges, including the negotiation between multiple selves and the courage to release work no single collaborator fully controls. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- The team dynamics that shape creative collaboration are governed by the same personality, trust, and norm-building principles that apply to any high-performing team. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- The structural conditions for team effectiveness apply to creative teams; clear direction, adequate resources, and supportive context determine whether collaboration produces insight or friction. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Creative collaboration requires the safety to share half-formed ideas without judgment; Edmondson's framework explains why some teams generate creative breakthroughs while others self-censor. diff --git a/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md b/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md deleted file mode 120000 index bae42bf..0000000 --- a/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-completion-and-renewal.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md b/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md new file mode 100644 index 0000000..79ac188 --- /dev/null +++ b/plugins/foreman/skills/creative-completion-and-renewal/SKILL.md @@ -0,0 +1,222 @@ +--- +name: "creative-completion-and-renewal" +description: "Addresses the hardest creative act -- finishing and releasing work -- covering the tension between experimenter and finisher mindsets, making choices when everything feels possible, accepting shades rather than absolutes, ending projects to begin anew, approaching new work with a clean slate, knowing when to stop refining, and recognising the energy living inside completed work. Use when struggling to ship a product, paralysed by perfectionism, unable to choose between competing directions, managing the transition between projects, deciding when a product version is ready for release, or recovering creative momentum after a major launch." +version: "1.0.0" +category: "creative" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - completion + - perfectionism + - shipping + - decision-making + - renewal + - release + - creative-energy + - finishing +related_skills: + - creative-shaping-and-craft + - creative-flow-and-inspiration + - creative-collaboration-and-context +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Completion and Renewal + +The hardest creative act is not starting. Starting is cheap, intoxicating, and abundant. The hardest creative act is releasing -- declaring a thing finished when every instinct whispers that one more pass, one more feature, one more revision could make it perfect. the text states the matter with characteristic quiet: "The only art the world gets to enjoy is from creators who've overcome these hurdles and released their work. Perhaps still greater artists existed than the ones we know, but they were never able to make this leap." The graveyard of entrepreneurship is not filled with bad ideas. It is filled with unreleased products, unshipped features, and unlaunched ventures -- work that was perpetually almost ready. Completion demands a different muscle than creation. And renewal -- the act of beginning again with a clean slate after the release -- demands a different muscle still. + +--- + +## The Framework + +the book's philosophy of completion and renewal unfolds across eight interconnected principles, each addressing a distinct failure mode in the transition from making to releasing to making again. + +### 1. The Completion Threshold + +"When is the work done?" the text asks. "There is no formula or method for finding this answer. It is an intuition: The work is done when you feel it is." This radical subjectivity is precisely what makes completion so difficult. There is no external checklist that certifies readiness. The entrepreneur must develop an internal signal -- analogous to the book's "ecstatic" compass -- that distinguishes between "not yet ready" and "resisting release." + +the text acknowledges the Completion phase is non-linear. Preparing work for release may reveal gaps that require returning to craft or experimentation: "You may realize there's more to be done. A revision, an addition, a deletion. So you step back to Craft or Experiment, and work your way forward once more." The discipline is distinguishing between genuine gaps and invented ones -- between the revision that serves the work and the revision that delays its release. + +A useful pragmatic principle surfaces: "Art doesn't get made on the clock. But it can get finished on the clock." Deadlines that are imposed too early suffocate creative work. Deadlines imposed during the completion phase focus it. + +### 2. The Experimenter and the Finisher + +the text identifies two creative temperaments that exist on a spectrum within every creator: + +**Experimenters** live in the discovery phases. They generate options, explore alternatives, resist closure. "Finding it more difficult to complete and release their work." + +**Finishers** move to resolution with speed and certainty. "They are less interested in exploring the possibilities and alternatives that the Experimentation and Craft phases can suggest." + +Neither temperament is superior. Each carries a characteristic failure mode: the Experimenter produces endlessly refined prototypes that never ship; the Finisher ships products that have not been explored deeply enough. the book's counsel to each is to borrow from the other. Finishers should "allow themselves space for improvisation and surprise." Experimenters should "take an aspect of the work through to completion" -- even a small one -- because "completing even a small segment builds confidence." + +The entrepreneurial implication is direct. The founder who has been in "stealth mode" for eighteen months, refining the product without shipping, is operating from the Experimenter pole. The founder who ships a barely functional MVP every two weeks without learning from any of them is operating from the Finisher pole. Growth requires movement toward the centre. + +### 3. How to Choose -- Decision-Making When Everything Is Possible + +Every creative project is "a tree with many branches. At each fork, we can go in any number of directions, and our choice will alter the final result. Often radically." the book's method for navigating these forks is deliberately anti-intellectual. + +The A/B test is the primary tool: place two options side by side, limit the comparison to two, and observe which produces a pull. "More often than not, there will be a clear draw toward one." When the draw is ambiguous, the text recommends the coin-toss method -- not to decide randomly, but to surface unconscious preference: "When the coin is spinning in the air, you'll likely notice a quiet preference or wish for one of the two to come up. Which are you rooting for? This is the option to go with." + +The deeper principle: "The goal is to turn off the conscious mind and follow our impulses. Children are exceptionally good at this." The instinctual first response, before analysis distorts it, tends to be the truest signal. The entrepreneur who convenes a three-hour meeting to choose between two product directions when she knew her preference within the first thirty seconds is not being thorough. She is being afraid. + +### 4. Shades and Degrees -- Accepting Disproportionality + +Creative work refuses clean proportionality. "Two seeds of inspiration might seem indistinguishable, but one may yield volumes and the other little to nothing." Enormous effort may produce marginal results; a tiny adjustment may transform the entire work. "We make one dab of the brush, one tweak in the mix -- and suddenly the work jumps from being halfway done to complete." + +For the entrepreneur, this principle invalidates the assumption that effort and outcome scale linearly. The feature that took three months to build may matter less than the one-line copy change completed in an afternoon. The strategic pivot that required a single conversation may prove more consequential than the twelve-month roadmap it replaced. Accepting this disproportionality is a prerequisite for recognising when the work is done: sometimes the last thing needed is microscopic. + +### 5. Ending to Start Anew -- The Regeneration Cycle + +Carl Jung built a round tower because he saw "life in the round as something forever coming into being and passing on." the text applies the same cyclical logic to creative work: "We participate in this by completing one project so that we can start anew. As in life, each ending invites a fresh beginning." + +The entrepreneur who cannot release a product because it has become their identity is disrupting the regeneration cycle. "When consumed with a single work to the degree that we believe it's our life's mission, there's no room for the next one to develop." Releasing the work is not an act of abandonment. It is an act of creation -- it creates the space for what comes next. + +"Sharing art is the price of making it," the text argues. "Exposing your vulnerability is the fee." The product launch, the public beta, the investor demo -- each is a moment of exposure that the entrepreneur cannot avoid without halting the cycle entirely. + +### 6. Clean Slate -- Seeing the Work Anew + +"After spending thousands of hours working on a piece, it's difficult to judge it from a neutral place. When someone experiences the work for the first time, after only two minutes they may see it more clearly than you do." Proximity breeds blindness. the book's practice of cleaning the slate is the discipline of re-encountering one's own work as a stranger would. + +The concrete method is telling. When reviewing a mix, the text makes a list of notes, has someone else implement them, then discards the list entirely. On the next listen, he starts fresh. "Listen as if for the first time and begin a new list of notes from scratch." The ego says: "I wanted this change, I got it, so it's a problem solved." The clean-slate practice says: forget what you wanted. Is it better? + +For the entrepreneur, the clean-slate discipline applies to product reviews, pitch deck revisions, and strategic plans alike. The founder who reviews a revised pitch by checking whether each requested change was implemented is following the ego. The founder who reads the revised pitch as though encountering it for the first time is practising the clean slate. + +the text recommends stepping away entirely when judgement is impaired: "Let it sit for a minute, a week, or longer, while you go get lost." Time is the primary tool. "Time is where learning occurs. Unlearning as well." + +### 7. Let It Be -- The Courage of Non-Intervention + +"First, do no harm," the text argues, borrowing the physician's oath. Sometimes the most valuable intervention is none at all. "Sometimes the most valuable touch a collaborator can have is no touch at all." + +For the entrepreneur, this principle applies to the late stages of product development -- the moment when additional refinement begins to erode rather than enhance. The feature that was perfect in its rough state but was polished until its energy dissipated. The pitch deck that was compelling in its first draft and was revised into blandness through seventeen rounds of feedback. Knowing when to stop refining is as much a creative skill as knowing how to refine. + +### 8. The Energy in the Work -- Following the Charge + +"What motivates us to work so diligently?" the text asks. "This energy is not generated by us. We are caught by it. We picked it up from the work. It contains the charge." The completed work possesses its own energy -- a "contagious vitality" that either pulls the creator forward or fails to. + +This energy is the ultimate diagnostic for completion and for the decision of what to work on next. "Early in a project, excitement is the inner voltmeter to watch." When the voltmeter reads high, the work is alive. When it flatlines despite effort -- "you're so deep in the details that you can't see the bigger picture" -- the creator has either taken a wrong turn or exhausted what this particular work has to offer. + +"One of the skills an artist develops is the ability to recognize when either they or the work have nothing left to give each other." For the entrepreneur, this is the skill of knowing when to ship the current version and when to shelve a product entirely. Both decisions require the same internal voltmeter. + +--- + +## Prompts + +**Prompt 1 -- Completion Diagnosis:** +> I have been working on [describe product/project] for [timeframe] and cannot bring myself to ship/release/launch it. Diagnose the blockage using the book's framework: Am I genuinely in the craft phase with legitimate work remaining, or am I in the completion phase and resisting release? What specific fears or stories am I telling myself that prevent letting go? If there are genuine gaps, identify them concretely. If the resistance is psychological, name it and propose a path through it, including a specific release date. + +**Prompt 2 -- Experimenter/Finisher Calibration:** +> Assess my entrepreneurial pattern: do I tend toward the Experimenter pole (endless refinement, difficulty shipping, multiple projects in perpetual progress) or the Finisher pole (rapid shipping, insufficient exploration, premature closure)? Based on my history: [describe 3-5 past projects and their outcomes]. Recommend specific practices to borrow from the opposite pole. What would an Experimenter do differently if they borrowed the Finisher's discipline? What would a Finisher gain from the Experimenter's patience? + +**Prompt 3 -- Clean Slate Review:** +> I need to evaluate [describe product, pitch, strategy document] with fresh eyes. I have been too close to it for too long. Act as a first-time viewer who has never encountered this work before. Describe what you notice -- what is clear, what is confusing, what generates energy, what feels dead. Do not check my changes against my stated intentions. Respond only to what is actually there. Then provide a new list of observations, starting from zero. + +**Prompt 4 -- Regeneration Planning:** +> I am about to release [describe project] and need to plan the transition to what comes next. Based on the book's regeneration cycle, help me: (1) identify the specific fears or attachments preventing me from finalising the release, (2) design a clean break ritual -- a concrete action that marks the end of this project, (3) create conditions for renewal -- what practices will open space for the next creative cycle to begin, and (4) identify the seeds of the next project that are already generating energy. + +--- + +## Use Cases + +**Validation-stage founder trapped in perpetual beta** + +A solo founder has been running a "private beta" for fourteen months. The product works. Users who have access report genuine value. Yet the founder continues to add features, fix edge cases, and delay the public launch. Diagnosing through the book's framework: the founder is an Experimenter who has conflated craft with completion. The product entered the completion phase months ago, but the founder keeps returning to the craft phase to avoid the vulnerability of release. The intervention is twofold: set a non-negotiable launch date three weeks out (the book's principle that art can be finished on the clock), and begin actively planning the next project. The energy of the next project -- the book's "excitement of what's coming next" -- provides the forward momentum to release the current one. + +**Early-traction team unable to choose between product directions** + +A product team has generated three viable product directions from customer research. Each has strong advocates. Weeks of analysis have not produced consensus. Applying the book's decision-making method, the team runs a structured exercise: for each pair of options, team members record their gut reaction within ten seconds, before any discussion. The results reveal a clear preference that the analytical process had obscured. The chosen direction, predictably, is the one the product lead had favoured from the first meeting but had been afraid to champion without analytical cover. + +**Growth-stage company struggling with post-launch renewal** + +A company has shipped its most ambitious product release after a year of development. The launch was well received, but the team is depleted and directionless. The CEO recognises this as the book's post-completion vacuum -- the energy that sustained the project has been expended, and renewal has not yet begun. She institutes a two-week clean-slate period: no product planning, no roadmap discussions. Team members engage in unrelated creative activities (the prescribed "go get lost"). At the end of the period, the team reconvenes with fresh eyes and generates the seed ideas for the next cycle, which prove more original than anything produced during the preceding exhausted months. + +--- + +## Anti-Patterns + +**Perfectionism disguised as quality standards.** the text identifies the pattern precisely: "We find flaws that don't really exist. We make inconsequential changes. We sense the distant mirage of some better creative option that hasn't been discovered yet." The entrepreneur who cannot ship because the product "isn't ready" should ask: ready by whose standard, and is that standard serving the work or protecting the founder from exposure? + +**Perpetual experimentation as a substitute for commitment.** The serial pivoter who starts a new direction every quarter has elevated the Experimenter pole to a lifestyle. the text is direct: "The first two phases have little purpose or meaning on their own. Art may only exist, and the artist may only evolve, by completing the work." Ideas that are never completed generate no value and no learning. + +**Finishing on the clock from the beginning.** Deadlines are a tool for the completion phase, not the creation phase. The startup that imposes sprint deadlines on exploratory work produces predictable, timid output. the book's timing principle is specific: deadlines help when "the work is close to completion," not when it is still searching for its form. + +**Skipping the clean slate after major revisions.** The product team that evaluates a revised product by checking a list of requested changes -- rather than experiencing the revised product afresh -- is confirming its own decisions rather than evaluating the work. The ego's checklist ("did we implement what we said we would?") is not the same as the clean-slate question ("is it better?"). + +**Refusing renewal because the last project was successful.** Success is as dangerous as failure for the regeneration cycle. The company that keeps extending a successful product rather than beginning something new risks the condition the text describes: "When consumed with a single work to the degree that we believe it's our life's mission, there's no room for the next one to develop." Even beloved products have a natural cycle. The willingness to end and begin again is what sustains the creative organisation across decades. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Committing to one seed over many; the Finisher's discipline of choosing | The danger is infinite exploration without commitment; even selecting a seed to develop is a completion act | +| Validation | Shipping imperfect versions; accepting shades rather than absolutes | The MVP is a completion exercise -- releasing work that is deliberately not finished, which requires overcoming the Experimenter's resistance to imperfection | +| Early Traction | Choosing between product directions; A/B decision-making at speed | The company must make consequential choices with incomplete information; the coin-toss method is not flippant -- it surfaces the intuition that analysis obscures | +| Growth | Post-launch renewal; clean-slate transitions between major releases | The organisational challenge is managing the energy cycle: depletion after major efforts and deliberate renewal before the next phase | +| Scale | Knowing when to let a product line be; ending to start anew at the portfolio level | At scale, the hardest completion act is ending a product or business unit that was once successful -- the organisational equivalent of releasing a work into the world | + +The validation stage is where completion discipline has its highest entrepreneurial leverage. The lean startup methodology (see lean startup methodology) provides the structural rationale for releasing imperfect work: build, measure, learn. the book's contribution is the emotional and psychological dimension that lean methodology underserves. The founder knows intellectually that shipping an MVP is correct. The question the text addresses is why it feels impossible -- and what internal practices make it bearable. + +At scale, completion becomes an organisational capability. The company that can end projects decisively -- without the months of zombie-state continuation that drains resources and morale -- possesses a competitive advantage that no amount of strategic planning can substitute. The energy freed by honest completion flows into the next cycle of creation. + +--- + +## Output Template + +```markdown +# Completion and Renewal Assessment -- [Project/Product Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Completion Status +- **Phase:** [Craft / Completion / Resisting release] +- **Time in current phase:** [Duration] +- **Legitimate remaining work:** [Specific items, if any] +- **Suspected avoidance behaviours:** [List] + +## Experimenter/Finisher Profile +- **Dominant tendency:** [Experimenter / Finisher / Balanced] +- **Evidence:** [Specific patterns from past projects] +- **Borrowing practice:** [What to borrow from the opposite pole] + +## Decision Log +| Decision Point | Options | Gut Response (10 sec) | Analytical Preference | Final Choice | +|---------------|---------|----------------------|----------------------|--------------| +| [Fork] | [A vs B] | [Which pulled] | [Which analysis favoured] | [Which was chosen] | + +## Energy Voltmeter +- **Current charge level:** [High / Medium / Low / Flatlined] +- **Last moment of genuine excitement:** [When and what triggered it] +- **Diagnosis:** [On track / Wrong turn / Exhausted mutual value] + +## Release Plan +- **Release date:** [Date -- non-negotiable] +- **Remaining actions:** [Numbered, specific, time-bound] +- **Fears to name and release:** [List] +- **"Let it be" items:** [Things to stop refining] + +## Renewal Conditions +- **Clean-slate period:** [Duration after release] +- **Renewal practices:** [Specific activities] +- **Seeds for next cycle:** [Ideas already generating energy] +``` + +--- + +## Related Skills + +- **[Creative Shaping and Craft](../../content/skills/creative/creative-shaping-and-craft.md)** -- Craft precedes completion; the shaping skill provides the methods for refining work to the point where the completion question becomes relevant. +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- The energy that sustains completion often originates in the inspiration that initiated the project; renewal depends on reconnecting with the conditions for fresh inspiration. +- **[Creative Collaboration and Context](../../content/skills/creative/creative-collaboration-and-context.md)** -- Sharing near-complete work with others is the method for seeing it anew; collaboration in the completion phase serves a diagnostic rather than generative function. +- **[Creative Obstacles](../../content/skills/creative/creative-obstacles.md)** -- The final stretch of any creative project intensifies self-doubt and perfectionism; the obstacle-clearing techniques are most needed when completion pressure is highest. +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- The revision discipline provides the structured methodology for the refinement phase that precedes release, applicable to any creative output that involves written form. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- The courage to release imperfect work requires the Stoic acceptance that perfection is unattainable and that completion serves a higher purpose than endless refinement. diff --git a/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md b/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md deleted file mode 120000 index 0070d22..0000000 --- a/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-flow-and-inspiration.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md b/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md new file mode 100644 index 0000000..0381bef --- /dev/null +++ b/plugins/foreman/skills/creative-flow-and-inspiration/SKILL.md @@ -0,0 +1,220 @@ +--- +name: "creative-flow-and-inspiration" +description: "Teaches the experiential practice of courting creative inspiration, sustaining openness, creating conditions for breakthrough ideas, staying in creative mode continuously, harnessing spontaneity, practising connected detachment, and using play as a serious creative method. Use when seeking breakthrough product ideas, preparing for creative sessions, diagnosing why innovation has stalled, designing environments for creative teams, recovering creative energy after burnout, or cultivating the founder's capacity for original thinking under pressure." +version: "1.0.0" +category: "creative" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - inspiration + - flow + - creativity + - openness + - spontaneity + - play + - detachment + - innovation +related_skills: + - creative-shaping-and-craft + - creative-completion-and-renewal + - creative-collaboration-and-context + - flow-state +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Flow and Inspiration + +You cannot catch lightning. But you can stand in the field where storms gather, at the hour when the air turns electric, wearing the right shoes, holding the right rod. The text's approach to creative inspiration operates on precisely this principle: "While we can't command a lightning bolt's arrival, we can control the space around it. We accomplish this by preparing beforehand and honoring our obligation to it afterward." This is not mysticism dressed in studio jargon. It is a pragmatic philosophy about preparing the conditions under which breakthrough ideas are most likely to arrive -- and doing the unglamorous work that follows when they do. Csikszentmihalyi's flow-state research (see `flow-state`) maps the neurochemistry and structural conditions for sustained deep performance. the book's contribution is different in kind: not the science of flow but the lived practice of courtship with the unpredictable. Where Csikszentmihalyi provides the thermostat, the text teaches you to read the weather. + +--- + +## The Framework + +the book's philosophy of creative inspiration is not a linear method. It is a constellation of interrelated practices that, taken together, constitute a way of being rather than a way of doing. Seven dimensions form the constellation. + +### 1. Inspiration -- Emptying to Receive + +The Latin root of "inspiration" -- inspirare, to breathe in -- contains the entire philosophy. "For the lungs to draw in air, they must first be emptied. For the mind to draw inspiration, it wants space to welcome the new." Inspiration is not something the entrepreneur generates through effort. It is something that enters when space has been cleared. + +The practical implication is counterintuitive. The founder buried under Slack messages, investor updates, and sprint reviews has no empty space for new ideas to occupy. the text recommends "practices of quieting the mind: meditation, awareness, silence, contemplation" -- not as wellness initiatives but as instruments of creative production. The vacancy draws the muse. + +Yet the text is no romantic. "An artistic life cannot be built solely around waiting. Inspiration is out of our control and can prove hard to find. Effort is required and invitations are to be extended." The practice is bilateral: clear space and do the work. Neither alone is sufficient. + +### 2. Expecting Surprise -- Surrender as Method + +"Some of our most interesting artistic choices come about by accident," the text observes. "Springing from moments of communion with the work, when the self disappears." These apparent mistakes are "the subconscious engaged in problem-solving" -- a deeper intelligence overriding conscious intention. + +The method, such as it is, consists of releasing control. "Set aside the outline, write with no map, and see what happens. The premise you start with could develop into something more. Something you couldn't have planned." For the entrepreneur, this translates to strategic experimentation without predetermined outcomes. The product feature that emerges from unstructured user observation may prove more valuable than the one specified in the quarterly roadmap. The business model that surfaces during a failed pivot may be superior to both the original model and the intended pivot target. + +The deepest surprise, the text suggests, is self-trust: "You learn to trust yourself -- in the universe, with the universe, as a unique channel to a higher wisdom." + +### 3. Radical Openness -- Softening the Filter + +"Our minds seek rules and limits," the text argues. "In attempting to navigate a large, uncertain world, we develop beliefs that give us a coherent framework, reduced options, and a false sense of certainty." Openness is the deliberate softening of this filter -- not to abandon judgement, but to delay it. + +the text urges creators to "purposely experiment past the boundaries of your taste. Examine approaches you may dismiss as too highbrow or lowbrow." When a collaborator's feedback conflicts with one's default setting, the instruction is to "reframe this as an exciting opportunity. Do all you can to see from their perspective." For the founder, this practice is a hedge against the cognitive narrowing that accompanies success. The company that cannot absorb uncomfortable market signals because they conflict with "accepted beliefs of what is and isn't possible" is the company that competitors disrupt. + +When plans fail, the book's counsel is characteristically quiet: "Instead of shutting the project down or expressing frustration, we might consider what else can be done with the materials at hand." + +### 4. Surrounding the Lightning Bolt -- Preparation and Obligation + +This is the central image of the book's inspiration philosophy. Lightning cannot be summoned; conditions for lightning can be created; and lightning, once struck, demands immediate practical response. + +"A more constructive strategy is to focus less on the lightning bolt and more on the spaces surrounding it. The space before, because lightning does not strike unless the right preconditions are met, and the space after, because the electricity dissipates if you do not capture it and use it." + +The "before" space is the daily practice of showing up, staying alert, maintaining readiness. The "after" space is craft -- the unglamorous labour of translating a flash of insight into a finished product. "Without diligence, inspiration alone rarely yields work of much consequence." The entrepreneur who has a breakthrough idea in the shower but returns to email rather than capturing and developing it has failed the obligation. + +Crucially, the text warns against storm-chasing: treating inspiration as the only valid source of creative work. "If lightning doesn't strike, our work need not be delayed." Most creative output comes from showing up and building. The carpenter metaphor is deliberate. + +### 5. Staying In It (24/7) -- Creativity as Ontology + +"Creativity is something you are, not only something you do. It's a way of moving through the world, every minute, every day." the text divides the artist's work into two kinds: the work of doing and the work of being. The second never stops. + +This means perpetual receptivity: "Paying attention and listening. Looking for connections and relationships in the outside world. Searching for beauty. Seeking stories. Noticing what you find interesting, what makes you lean forward." For the entrepreneur, staying in it means the dinner conversation, the airport terminal observation, the unrelated article, the child's question -- all are raw material. The founder who switches off creative attention outside of scheduled brainstorming sessions is working with a fraction of available input. + +### 6. Connected Detachment -- Caring Without Clinging + +"Consider detaching from the story of your life as it's happening," the text argues. The practice is not indifference but perspective: observing events as though watching a film about oneself. "I wasn't expecting that plot twist. I wonder what's going to happen to our hero next." + +For the entrepreneur, connected detachment addresses the emotional volatility of building a company. The failed product launch, the departed co-founder, the lost customer -- each carries real consequence, but identification with those events produces paralysis rather than response. "When we obsessively focus on these events, they may appear catastrophic. But they're just a small aspect of a larger life." The practice is to zoom out: care deeply about the work, release attachment to any single outcome within it. + +This is distinct from detachment as indifference. The founder who does not care is not practising connected detachment; they have disengaged entirely. the book's framework is paradoxical by design: full commitment coupled with radical non-attachment to results. + +### 7. Play -- Seriousness Without Gravity + +"Making art is a serious matter. The opposite is also true. Making art is pure play." the text holds both poles simultaneously. Play is not the absence of rigour; it is rigour stripped of self-consciousness. "In play, there are no stakes. No boundaries. No right or wrong. No quotas for productivity." + +The entrepreneurial application cuts against the cult of intensity. The all-hands meeting conducted as if the company's survival depends on each slide deck is not producing the best ideas in the room. "Putting importance on the work too soon stirs up instincts of caution," the text observes. The team that can experiment without stakes -- where "playtime" is a legitimate operating mode -- produces the adjacent-possible breakthroughs that planning sessions never reach. "Find a clue, follow a lead, remain unattached to what came before." + +### The Ecstatic as Compass + +Across all seven dimensions, one signal guides the creator: the ecstatic. the text describes it as "an arising" -- "a visceral, body-centered reaction, not a cerebral one. It doesn't have to make sense." When a small tweak transforms mediocre work into something that takes the breath away, that somatic response is the compass pointing toward greatness. Entrepreneurs who rely exclusively on data and rational analysis to evaluate creative work miss this signal entirely. The ecstatic is not a replacement for evidence. It is the evidence that precedes measurement. + +--- + +## Prompts + +**Prompt 1 -- Inspiration Conditions Audit:** +> Map the conditions under which my best ideas have historically arrived: [describe 3-5 breakthrough moments, including setting, activity, time of day, emotional state, and what preceded them]. Identify the common preconditions. Then assess my current daily structure against these conditions. Where am I creating space for inspiration, and where am I structurally preventing it? Design a week that "surrounds the lightning bolt" -- protecting the before-space while maintaining productive craft in the after-space. + +**Prompt 2 -- Openness Stress Test:** +> Here are three ideas, feedback items, or market signals I have recently dismissed or resisted: [describe each]. For each, apply the book's radical openness practice: assume the dismissed input contains a valuable signal I cannot yet see. What would that signal be? What would my product, strategy, or team structure look like if I fully incorporated it? I am not committing to any of these -- I am expanding the field of possibility. + +**Prompt 3 -- Connected Detachment Reset:** +> I am currently emotionally entangled with [describe situation: failed launch, difficult co-founder relationship, competitive threat, funding setback]. Apply the book's connected detachment framework: reframe this situation as a plot twist in a story I am watching. What would a detached but caring observer notice about this situation that I cannot see from inside it? What becomes possible in the next scene that was not possible before this plot twist occurred? + +**Prompt 4 -- Play Protocol Design:** +> My team's creative process has become [rigid / formulaic / overly data-driven / risk-averse]. Design a play protocol -- a structured but low-stakes creative session format -- that we can run [weekly / monthly]. The protocol should: eliminate evaluation during the session, introduce an element of genuine surprise, allow ideas to be generated without justification, and produce raw material that the team's "adult" craft mode can later evaluate. Include specific facilitation instructions and a 60-minute session outline. + +**Prompt 5 -- 24/7 Creative Practice:** +> I want to develop the practice of staying in creative mode outside of formal work sessions. Based on the book's principle that "creativity is something you are, not only something you do," design a set of daily micro-practices -- each taking under 5 minutes -- that train perpetual receptivity: noticing patterns, collecting raw material, making unexpected connections. Include a simple capture system so nothing observed is lost. + +--- + +## Use Cases + +**Idea-stage founder seeking a breakthrough concept** + +A serial entrepreneur between ventures has spent three months actively brainstorming next-company ideas. Whiteboards are full, spreadsheets of market analyses run to dozens of tabs, and nothing generates the visceral excitement that preceded her previous two successful launches. Applying the book's framework, she recognises the problem: she is storm-chasing. The "space before" the lightning bolt requires emptying, not filling. She clears her calendar of brainstorming sessions, begins a daily walking practice with no agenda, and replaces market analysis with the 24/7 practice of noticing what makes her lean forward. Six weeks later, during an entirely unrelated conversation at a friend's dinner, the idea arrives fully formed -- an intersection of two domains she had never consciously connected. The "before" space was the six weeks of receptive attention. The "after" space -- three months of intense development -- converts the flash into a funded company. + +**Early-traction team in creative stagnation** + +A product team of twelve has shipped the same product category for two years. Feature releases are competent but predictable. The VP of Product diagnoses the issue through the book's openness lens: the team has built a coherent framework of beliefs about what the product is and is not, and that framework now functions as a cage. She institutes a monthly "opposite day" -- a half-day session where each team member proposes a feature that violates one of the team's implicit rules. The session operates under play conditions: no evaluation, no feasibility analysis, no roadmap implications. Three months in, one of the "impossible" ideas, refined through the subsequent craft process, becomes the company's highest-adoption feature of the year. The idea had been available to anyone on the team; the openness practice created the conditions under which it could be spoken. + +**Growth-stage founder recovering creative capacity** + +A CEO who built the company's product vision personally has not contributed an original product idea in eighteen months. Every hour is consumed by management, fundraising, and coordination. Applying connected detachment, he stops interpreting this as a personal failure and begins observing it as a structural condition: the role, as currently designed, eliminates every precondition for creative inspiration. The intervention combines Csikszentmihalyi's structural recommendations (protected deep-work blocks from the flow-state framework) with the book's experiential practices (emptying the mind, staying in it, surrounding the lightning bolt). Two mornings per week are cleared entirely. No agenda, no deliverables. He walks, reads unrelated material, and practises noticing. Within a quarter, three substantive product insights emerge from these sessions -- the first original contributions from the CEO in over a year. + +--- + +## Anti-Patterns + +**Treating inspiration as a prerequisite for work.** the text is explicit: "If lightning doesn't strike, our work need not be delayed." The founder who waits for inspiration before beginning meaningful work will produce very little. The daily practice is showing up and building. Inspiration, when it arrives, accelerates work already in progress. + +**Confusing play with lack of discipline.** Play, in the book's framework, is not the absence of structure. It is the absence of premature evaluation. A play session without subsequent craft yields nothing usable. The protocol is: play freely, then apply the full rigour of shaping and refinement to whatever emerges. Companies that institutionalise play without the subsequent craft step produce creative tourism, not creative output. + +**Performing openness without practising it.** The founder who announces "we welcome all ideas" in a meeting but visibly dismisses unfamiliar suggestions has performed openness while practising closure. the book's openness is effortful and uncomfortable: "Do all you can to see from their perspective and understand their point of view, instead of defending your own." It requires genuine cognitive discomfort, not a policy statement. + +**Mistaking connected detachment for emotional suppression.** Detachment is not the refusal to feel. It is the ability to feel fully while maintaining observational perspective. The founder who uses "detachment" as a label for not caring about team morale or customer outcomes is not practising the book's framework. They are practising avoidance. + +**Using spontaneity to avoid preparation.** the text notes that "the story of spontaneity can be misleading. We don't see all the practice and preparation that goes into priming an artist for the spontaneous event to come through." The startup that prizes "moving fast and breaking things" without investing in the foundational knowledge that makes improvisation intelligent is not practising spontaneity. It is practising ignorance at speed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Emptying and receptivity; surrounding the lightning bolt | Maximum freedom to practise the "before" space; the danger is mistaking storm-chasing (active brainstorming) for receptivity (quiet attention) | +| Validation | Radical openness to customer signals that contradict assumptions | The market becomes a collaborator; the practice is absorbing unexpected data without filtering it through existing beliefs | +| Early Traction | Play as institutional practice; breaking creative stagnation | Teams need structured play to prevent the calcification of early success into rigid process | +| Growth | Connected detachment; 24/7 creative mode for leadership | The founder's challenge shifts from producing creative work to maintaining the creative conditions in which others can produce | +| Scale | Designing organisational systems that preserve the conditions for inspiration at scale | The ecstatic signal becomes harder to hear as decision-making layers multiply; the practice is building feedback loops that surface it | + +At the idea stage, the founder has the rare luxury of an empty vessel. This is the moment to practise the book's "before" space most purely -- not by filling every hour with brainstorming, but by cultivating the receptive attention from which genuine ideas emerge. Csikszentmihalyi's flow-state framework provides the structural architecture (protected time, clear goals, challenge-skill balance); the book's contribution is the quality of attention within that architecture. + +At growth and scale, the creative challenge is no longer personal but systemic. The founder must design organisations where the book's conditions -- openness, play, connected detachment, perpetual receptivity -- survive the introduction of process, hierarchy, and institutional memory. This is perhaps the most advanced creative leadership challenge of all: building systems that preserve the conditions for surprise. + +--- + +## Output Template + +```markdown +# Creative Inspiration Conditions -- [Individual/Team] + +**Date:** [Date] +**Context:** [Current creative challenge or aspiration] + +## Lightning Bolt History +[3-5 past breakthrough moments with conditions mapped] +| Moment | Setting | Preceding Activity | Emotional State | Time of Day | +|--------|---------|-------------------|-----------------|-------------| +| [Moment] | [Where] | [What preceded] | [State] | [When] | + +## Common Preconditions Identified +1. [Precondition] +2. [Precondition] +3. [Precondition] + +## Current Structural Barriers to Inspiration +| Barrier | Blocks Which Precondition | Proposed Change | +|---------|--------------------------|-----------------| +| [Barrier] | [Precondition] | [Change] | + +## Weekly Inspiration Architecture +| Day | Before-Space (Emptying/Receptivity) | Craft-Space (Doing) | Notes | +|-----|-------------------------------------|---------------------|-------| +| Mon | [Activity] | [Activity] | | +| Tue | [Activity] | [Activity] | | + +## Play Protocol +- **Frequency:** [Weekly / Biweekly / Monthly] +- **Duration:** [Time] +- **Rules of engagement:** [No evaluation / surprise element / capture method] +- **Craft follow-up:** [When and how raw material gets refined] + +## Detachment Practice +[Specific situations where connected detachment will be applied this quarter] + +## Ecstatic Signal Log +[Running record of moments when the work produced a visceral response -- the compass data] +``` + +--- + +## Related Skills + +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Csikszentmihalyi's structural and neurochemical framework for sustained deep performance; this skill complements it with the experiential dimension of courting the unpredictable. +- **[Creative Shaping and Craft](../../content/skills/creative/creative-shaping-and-craft.md)** -- Inspiration is raw material; shaping converts it to form. The two skills operate as a paired cycle: receive, then sculpt. +- **[Creative Completion and Renewal](../../content/skills/creative/creative-completion-and-renewal.md)** -- The obligation to inspiration includes finishing what it started; completion addresses the challenge of honouring the lightning bolt through the labour of release. +- **[Creative Collaboration and Context](../../content/skills/creative/creative-collaboration-and-context.md)** -- Other people are among the richest sources of creative surprise; collaboration multiplies the conditions under which unexpected connections arise. +- **[Creative Practice and Habit](../../content/skills/creative/creative-practice-and-habit.md)** -- Daily practice creates the conditions under which inspiration arrives; showing up consistently is the prerequisite for the unpredictable moments of flow. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- The deep work scheduling techniques provide the protected time blocks that creative flow requires to emerge and sustain. diff --git a/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md b/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md deleted file mode 120000 index 644e9d5..0000000 --- a/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-identity-and-purpose.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md b/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md new file mode 100644 index 0000000..fdc1091 --- /dev/null +++ b/plugins/foreman/skills/creative-identity-and-purpose/SKILL.md @@ -0,0 +1,206 @@ +--- +name: "creative-identity-and-purpose" +description: "Applies the philosophy that creativity is a universal human capacity -- not a rare talent -- to help entrepreneurs reclaim their creative identity and redefine success on their own terms. Synthesises beginner's mind, the abundant mindset, non-competition, and creative freedom into a foundational framework for entrepreneurial self-expression. Use when doubting your creative ability, comparing yourself to competitors, trapped in scarcity thinking about ideas or market opportunity, struggling to define what success means for your venture, or needing permission to pursue an unconventional path." +version: "1.0.0" +category: "creative" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - identity + - beginner-mind + - abundance + - non-competition + - freedom + - purpose + - creative-confidence + - creative-philosophy +related_skills: + - creative-perception-and-awareness + - creative-practice-and-habit + - creative-obstacles + - flow-state + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-acceptance-amor-fati +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Permission to Create + +Creativity is not a talent. It is a way of seeing -- and according to the text, every person is already creative. Most have simply never given themselves permission. "Creativity is not a rare ability," the text argues. "It is not difficult to access. Creativity is a fundamental aspect of being human. It's our birthright." The entrepreneur who believes creativity belongs to designers, musicians, and novelists has already surrendered the single greatest competitive advantage available: the willingness to perceive the world freshly and act on that perception. Building a company is among the most demanding creative acts a person can undertake. The sooner that truth is acknowledged, the sooner the founder stops waiting for inspiration and starts recognising that they have been creating all along. + +--- + +## The Framework + +### Five Pillars of Creative Identity + +the book's philosophy, distilled across dozens of meditative essays, converges on five interconnected principles that together form a creative operating system for the entrepreneur. + +**1. Everyone Is a Creator** + +The act of creation is not confined to artefacts displayed in galleries. "To create is to bring something into existence that wasn't there before. It could be a conversation, the solution to a problem, a note to a friend, the rearrangement of furniture in a room." Every product decision, every pitch, every pricing model, every conversation with a customer is a creative act. Recognising this does not inflate the word "creative" beyond meaning -- it restores it to its original scope. The founder who sees their work as creative treats problems differently: with curiosity rather than dread, with experimentation rather than formula. + +**2. Beginner's Mind** + +the text tells the story of AlphaGo, the artificial intelligence that defeated the world's greatest Go player with a move no human had made in three thousand years of play. The machine's advantage was not superior intelligence but the absence of accumulated convention. "To see what no human has seen before, to know what no human has known before, it may be necessary to see as if through eyes that have never seen." For the entrepreneur, expertise is simultaneously an asset and a cage. The founder with twenty years of industry experience knows what is "impossible" -- and that knowledge blocks precisely the innovations that would redefine the category. + +**3. The Abundant Mindset** + +"A river of material flows through us. When we share our works and our ideas, they are replenished. If we block the flow by holding them all inside, the river cannot run and new ideas are slow to appear." Scarcity thinking -- hoarding features, refusing to ship until perfection is achieved, fearing that a competitor will steal an idea -- is the enemy of creative momentum. The abundant mindset treats ideas as renewable, products as chapters rather than tombstones, and each release as a catalyst for the next. the text frames this with disarming clarity: "Our life's work is far greater than any individual container. The works we do are at most chapters. There will always be a new chapter, and another after that." The founder who treats their current venture as the only book they will ever write makes decisions rooted in desperation. The one who treats it as one chapter among many makes decisions rooted in creative freedom. + +**4. Non-Competition** + +the text is unequivocal: "Every artist's playing field is specific to them." The entrepreneur's only meaningful competition is with their own previous work. External benchmarking has tactical utility -- understanding a market, pricing competitively, identifying gaps -- but as a creative compass it is ruinous. Theodore Roosevelt's observation that "comparison is the thief of joy" applies with surgical precision to the founder who checks competitor launches before checking their own product roadmap each morning. The distinction the text draws between "rising-to-meet" energy and "conquering" energy is critical: the Beatles and the Beach Boys pushed each other to greatness not through competition but through mutual inspiration. + +**5. Freedom and Self-Defined Success** + +"The artist's only responsibility is to the work itself. There are no other requirements." Success, in the book's reckoning, "occurs in the privacy of the soul. It comes in the moment you decide to release the work, before exposure to a single opinion." This is not anti-commercial naivete. It is the recognition that external validation -- funding rounds, press coverage, revenue milestones -- is a lagging indicator at best and a distorting mirror at worst. The entrepreneur who defines success purely by external metrics will eventually find those metrics dictating creative choices, which hollows the work from within. + +### What Works for You + +the text is careful to note that no two creative paths are identical. "Artists have created in every way possible -- at the extremes of chaos and order, and at the meeting point of different methods at once. There is no right time, right strategy, or right equipment." Charles Dickens carried a compass to ensure he always slept facing north. Dr. Seuss wore unusual hats. The point is not that these rituals are rational but that they worked for the people who used them. For the entrepreneur, this principle is liberating: there is no single correct way to build a company. "Receive wisdom skillfully. Try it on for size and see how it fits. Incorporate what's useful. Let go of the rest." The founder who slavishly follows a playbook designed for someone else's company, market, and temperament will produce work that feels borrowed. The one who tests every approach and keeps only what resonates will produce work that feels original -- because it is. + +### Nothing Is Static + +Undergirding all five pillars is the book's insistence on impermanence. "The world is always changing. You can engage in the same awareness practice five days in a row in the same location and have a unique experience each time." Creative identity is not a fixed label. The founder who was a fintech operator last year may be a climate entrepreneur this year -- not because they are unfocused, but because they are alive. Purpose, the text suggests, is not something to be declared in advance but something to be discovered through engagement. "If we like what we are creating, we don't have to know why. Sometimes the reasons are obvious, sometimes not. And they can change over time." The entrepreneur who insists on articulating a grand purpose before beginning has the sequence backwards. Make the work. The purpose will reveal itself. + +--- + +## Prompts + +**Prompt 1 -- Creative Identity Audit:** +> I am a founder of [company] at the [stage] stage. I often feel that I am "not creative" or that creativity is separate from my business work. Using the book's principle that everyone is already a creator, help me identify the creative acts I perform daily -- in product decisions, team interactions, problem-solving, and communication. Reframe my role as a creative one and show me where I am already creating. + +**Prompt 2 -- Beginner's Mind Reframe:** +> I have [X years] of experience in [industry]. Identify the conventions, assumptions, and "impossibilities" I may have absorbed that could be limiting my ability to see fresh solutions. Apply the AlphaGo principle: what moves might I make if I had no knowledge of how things are "supposed to be done" in this space? + +**Prompt 3 -- Abundance vs. Scarcity Diagnostic:** +> Analyse my current approach to [specific business challenge: idea generation / product shipping / competitive response / feature prioritisation]. Am I operating from an abundant or scarcity mindset? Where am I hoarding ideas, delaying releases, or treating this venture as my "one shot"? Recommend concrete shifts toward abundance. + +**Prompt 4 -- Success Redefinition:** +> I currently measure success by [metrics: revenue, funding, press, user growth]. Using the book's framework, help me construct a parallel definition of success rooted in the quality and authenticity of my creative output. What would it look like if I evaluated my work "before exposure to a single opinion"? + +--- + +## Use Cases + +**Idea-stage founder paralysed by "not being creative enough"** + +A former management consultant is developing a mental health platform but dismisses her own creative capacity because she has "never been an artist." She defaults to copying competitor interfaces and features rather than developing her own vision. Applying the Everyone Is a Creator principle reframes her daily work -- mapping user journeys, designing onboarding flows, writing microcopy -- as inherently creative acts. The beginner's mind lens reveals that her lack of health-tech experience is an asset: she sees friction points that industry veterans have normalised. Within weeks, her product concept diverges sharply from competitors, grounded in her unique perception rather than borrowed convention. + +**Growth-stage CEO trapped in competitive obsession** + +A Series A e-commerce founder starts every morning by reviewing three competitors' social feeds, pricing pages, and feature announcements. The practice consumes ninety minutes daily and produces anxiety rather than insight. Applying the book's non-competition principle surfaces the real problem: the founder has outsourced his creative compass to external benchmarks. Replacing the competitive review with a daily "creative intention" practice -- thirty minutes reflecting on what his product uniquely offers and where it wants to go next -- restores both originality and calm. Revenue growth does not slow. The product begins to differentiate. + +**Scale-stage executive hoarding the "big idea"** + +A CEO at scale refuses to launch a promising new product line because it is "not ready yet" -- a position she has maintained for eighteen months. The abundant mindset audit reveals classic scarcity behaviour: treating this product as her company's defining work rather than one chapter among many. The reframe -- that shipping creates space for the next idea -- unlocks the launch within eight weeks. The product performs adequately; the next idea, which arrives almost immediately, performs brilliantly. + +**Validation-stage technical founder following someone else's playbook** + +An engineer-turned-founder has read every canonical startup book and follows a rigorous build-measure-learn process borrowed from a prominent accelerator. His execution is methodical, but his product feels generic -- indistinguishable from three competitors pursuing the same thesis. The "What Works for You" principle reveals the issue: he has adopted someone else's creative method wholesale, suppressing his own instincts about what the product should feel like. the book's advice -- "established artists generally draw from their personal experience and recommend the solutions that worked for them; these tend to be specific to their journey, not yours" -- grants him permission to deviate from the playbook. He introduces a design language drawn from his background in electronic music, an aesthetic choice no accelerator would have recommended. Users describe the product as "different from everything else." It is. That was the point. + +--- + +## Anti-Patterns + +**1. Weaponising "everyone is creative" to skip craft development.** The principle that creativity is universal does not mean that craft is unnecessary. A founder who cannot write clearly, think structurally, or build iteratively will not produce great work merely by declaring a creative identity. Permission is the starting line, not the finish. + +**2. Treating beginner's mind as wilful ignorance.** the book's beginner's mind is a deliberate posture of openness, not a refusal to learn. The founder who ignores market data, customer feedback, or financial constraints because they are "thinking like a beginner" has confused freshness with recklessness. + +**3. Misreading non-competition as anti-ambition.** the text does not counsel passivity. The distinction between competitive energy and rising-to-meet energy is subtle but vital. Studying competitors to be inspired is healthy; studying competitors to copy or destroy is corrosive. The founder who uses non-competition as a reason not to push harder has missed the point entirely. + +**4. Defining abundance as indiscriminate shipping.** The abundant mindset encourages flow, not carelessness. Releasing work that is genuinely unfinished -- not iterative but simply lazy -- erodes trust with users and team alike. Abundance means trusting that the next idea will come, not that the current one does not matter. + +**5. Using "success is internal" to avoid accountability.** the book's redefinition of success is a philosophical complement to external metrics, not a replacement for them. The founder who ignores burn rate, churn, or customer satisfaction because they have achieved "internal success" is confusing contemplation with delusion. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Granting creative permission | The most powerful intervention is simply recognising that building a company is a creative act; beginner's mind is naturally present and should be protected | +| Validation | Maintaining openness amid early data | The temptation to prematurely narrow based on initial feedback is strongest here; abundant thinking keeps multiple seeds alive | +| Early Traction | Resisting the pull of competitor imitation | As the market becomes visible, the urge to benchmark and copy intensifies; non-competition principles preserve distinctiveness | +| Growth | Redefining success beyond funding metrics | External validators (investors, press, industry awards) gain volume; the internal definition of success becomes a stabilising force | +| Scale | Institutionalising creative identity | The founder's personal creative philosophy must translate into organisational culture; hire for creative orientation, not just functional skill | + +At the idea stage, creative identity is both most fragile and most potent. The founder has not yet accumulated the conventions, compromises, and competitive anxieties that calcify at later stages. The discipline is to protect that openness deliberately -- to resist the advisory board members and mentors who will helpfully suggest "how things are done in this space." Beginner's mind is naturally present at this stage; the work is to avoid extinguishing it prematurely in the name of "learning the industry." + +At validation, the abundant mindset faces its first serious test. Early data is ambiguous. The scarcity-minded founder treats every signal as definitive -- pivoting after a single negative interview, or doubling down after a single positive one. The abundance-minded founder holds multiple seeds simultaneously, allowing the data to accumulate before narrowing. This is not indecision. It is the recognition that premature certainty is the enemy of discovery. + +At early traction, competitive pressure becomes visceral. The company now has something to lose, and competitors become visible and threatening. The non-competition principle is hardest to maintain precisely when it is most valuable. The founder who can stay focused on their own creative trajectory -- what the text calls the "competition with the self" -- will produce work that competitors cannot replicate, because it originates from a unique creative identity rather than a shared market playbook. + +At growth, external definitions of success proliferate. Revenue targets, investor expectations, press narratives, and industry rankings all impose their metrics on the founder's sense of accomplishment. the book's insistence that success "occurs in the privacy of the soul" becomes a stabilising counterweight. This does not mean ignoring business metrics -- it means refusing to let them become the sole compass. The founder who can hold both an external scorecard and an internal measure of creative integrity simultaneously navigates growth without losing the creative instincts that produced the company's initial distinctiveness. Those who cannot tend to optimise for metrics that are visible and measurable while the invisible, unmeasurable quality of their creative work quietly erodes. + +At scale, the challenge inverts entirely. Creative identity is no longer a personal matter but an institutional one. The company's ability to innovate depends on whether the founding creative philosophy has been embedded in hiring, product development, and strategic planning -- or whether it died the day the founder stopped being the one making things. the book's principle that "nothing is static" applies with particular force here: the creative identity that launched the company may not be the one that sustains it. The willingness to evolve -- to approach the company's next chapter with the same beginner's mind that characterised its first -- is what separates enduring creative enterprises from those that peak and plateau. + +--- + +## Output Template + +```markdown +# Creative Identity Assessment -- [Company/Project] + +**Date:** [Date] +**Founder/Team:** [Names] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Current Creative Self-Perception +- How do I/we describe our creative capacity? [Response] +- Where do I/we feel "not creative enough"? [Response] +- What conventions or "rules" am I/are we following without questioning? [Response] + +## Five Pillars Diagnostic + +| Pillar | Current State (1-5) | Evidence | Action | +|--------|---------------------|----------|--------| +| Creator Identity | [Score] | [How creativity shows up in daily work] | [Step to strengthen] | +| Beginner's Mind | [Score] | [Assumptions held; conventions followed] | [Assumption to challenge] | +| Abundant Mindset | [Score] | [Hoarding vs. flowing behaviour] | [Idea or product to release] | +| Non-Competition | [Score] | [Time spent on competitor analysis vs. own vision] | [Practice to shift] | +| Freedom / Success | [Score] | [External vs. internal success metrics] | [New success definition] | + +## Beginner's Mind Inventory +| Convention I Follow | Source (Industry / Advisor / Competitor / Self) | What Happens If I Drop It? | +|--------------------|-------------------------------------------------|----------------------------| +| [Convention 1] | [Source] | [Possible outcome] | +| [Convention 2] | [Source] | [Possible outcome] | +| [Convention 3] | [Source] | [Possible outcome] | + +## Competition Reframe +**Current competitive focus:** [What competitors am I watching and how often?] +**Energy type:** [Conquering or rising-to-meet?] +**Self-competition target:** [What is my own previous work that I want to surpass?] + +## Creative Permission Statement +[One sentence: what I give myself permission to create, regardless of convention] + +## Success Definition (Internal) +[How I will measure success before exposure to any external opinion] + +## Next Creative Act +[The specific product decision, experiment, or expression to pursue this week] +``` + +--- + +## Related Skills + +- **[Creative Perception and Awareness](../../content/skills/creative/creative-perception-and-awareness.md)** -- Once creative identity is established, the next step is refining the ability to perceive the signals that feed creation. +- **[Creative Practice and Habit](../../content/skills/creative/creative-practice-and-habit.md)** -- Identity without practice is aspiration; this skill provides the daily discipline that makes creative identity operational. +- **[Creative Obstacles](../../content/skills/creative/creative-obstacles.md)** -- The internal resistance that threatens creative identity -- self-doubt, distraction, undermining voices -- and how to navigate it. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Csikszentmihalyi's optimal experience theory provides the psychological mechanics behind the creative states described experientially. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The non-competition and freedom principles align with the Stoic dichotomy of control: focus energy on your own creative output, release attachment to outcomes. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- The organisational parallel to creative purpose: both address the question of why the work matters beyond personal ambition or financial return. diff --git a/plugins/foreman/skills/creative-obstacles/SKILL.md b/plugins/foreman/skills/creative-obstacles/SKILL.md deleted file mode 120000 index 727c0c5..0000000 --- a/plugins/foreman/skills/creative-obstacles/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-obstacles.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-obstacles/SKILL.md b/plugins/foreman/skills/creative-obstacles/SKILL.md new file mode 100644 index 0000000..c6932a5 --- /dev/null +++ b/plugins/foreman/skills/creative-obstacles/SKILL.md @@ -0,0 +1,208 @@ +--- +name: "creative-obstacles" +description: "Addresses the internal resistances that derail entrepreneurial creativity -- self-doubt, distraction, undermining voices, the danger of expectations, and impatience -- using a contemplative creative framework. Provides strategies for navigating the inner critic, managing creative possession, and cultivating patience as a creative virtue. Use when paralysed by self-doubt about your venture, overwhelmed by internal or external criticism, struggling with perfectionism or unrealistic expectations, unable to distinguish productive obsession from destructive compulsion, or losing patience with the creative timeline of building a company." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - self-doubt + - inner-critic + - distraction + - patience + - expectations + - resilience + - creative-blocks + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-perception-and-awareness + - creative-practice-and-habit + - flow-state + - stoic-emotional-mastery + - stoic-fortitude-and-resilience + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Censor in the Room + +Every creator has a censor living inside their head. It speaks fluently in the language of inadequacy: you are not talented enough, your idea is not good enough, you will be exposed as a fraud. The question is not how to silence this voice -- that project has a zero percent success rate -- but when to stop listening. The text treats self-doubt not as a malfunction to be repaired but as an inevitable companion on the creative path. "Self-doubt lives in all of us," he writes. "And while we may wish it gone, it is there to serve us." The entrepreneur who attempts to eradicate doubt will exhaust themselves fighting an enemy that regenerates overnight. The one who learns to work alongside it -- acknowledging its presence without granting it authority -- gains access to a harder, more durable form of creative confidence. + +--- + +## The Framework + +### The Six Obstacles + +the text identifies a constellation of internal resistances that recur across creative lives. For the entrepreneur, each maps to a specific pattern of self-sabotage that can stall companies as effectively as any market force. + +**Obstacle 1: Self-Doubt -- The Universal Companion** + +"Flaws are human, and the attraction of art is the humanity held in it. If we were machinelike, the art wouldn't resonate. It would be soulless." the text reframes self-doubt as evidence of creative sensitivity rather than creative deficiency. The most vulnerable artists are often the most talented, precisely because the same sensitivity that allows them to perceive deeply also makes them tender to judgement. "The sensitivity that allows them to make the art is the same vulnerability that makes them more tender to being judged." + +The entrepreneurial implication is counterintuitive: the founder wracked by doubt about their product may be closer to something genuine than the one who radiates unshakeable confidence. Doubt, properly channelled, is a quality-control mechanism. It becomes destructive only when it prevents action rather than refining it. + +the text draws one firm line: "If a creator is so afraid of judgement that they're unable to move forward, it might be that the desire to share the work isn't as strong as the desire to protect themselves." Doubt is permissible. Paralysis is not. The founder must ship. + +**Obstacle 2: Undermining Voices -- Internal and External Critics** + +"As these voices enter an artist's head -- concern for deadlines, deals, sales, media attention, public image, staff, overhead, growing the audience -- they can undermine our focus." the text distinguishes between two species of undermining voice. External voices arrive from investors, advisors, customers, competitors, press, and the market itself. Internal voices are often absorbed versions of external ones -- "a critical or doting parent, teacher, or mentor. These voices are not our own. We have internalised someone else's judgement." + +The remedy is not argument but disengagement. "Working to free yourself from inner voices is a kind of meditation. Set aside all concerns for a stretch of time and say, I'm only going to focus on this one practice: making great work." The entrepreneur need not refute every critic. The task is to create conditions -- temporal, spatial, psychological -- where the voices cannot reach the work. + +**Obstacle 3: Distraction -- The Misunderstood Tool** + +the text makes a distinction that most productivity literature misses entirely: "Distraction is not procrastination. Procrastination consistently undermines our ability to make things. Distraction is a strategy in service of the work." Strategic distraction -- a walk, a drive, a shower, an unrelated physical task -- occupies the conscious mind and frees the subconscious to work on the problem. "Some musicians do a better job of writing melodies while driving than sitting in a room with an audio recorder on." + +The entrepreneurial application is that not all time away from the desk is wasted time. The founder who takes a thirty-minute walk to think through a pricing decision is not avoiding work -- provided the walk is intentional, the problem is held loosely in awareness, and the return to active work follows. The founder who scrolls social media for three hours is procrastinating. The difference is intention. + +**Obstacle 4: Great Expectations -- The Weight of Anticipated Outcomes** + +"When beginning a new project, we're often met with anxiety. It visits almost all of us no matter how experienced, successful, or well-prepared we might be." the text identifies expectations as a paradox: high standards drive quality, but attachment to specific outcomes freezes the creative process. The solution is what he calls "experimental faith" -- working "not as an evangelist, expecting miracles, but as a scientist, testing and adjusting and testing again." + +For the entrepreneur, this reframes failure entirely. "If we try ten experiments and none of them work, we have a choice. We can take it personally, and think of ourselves as a failure and question our ability to solve the problem. Or we can recognize we've ruled out ten ways that don't work, bringing us that much closer to a solution." The founder who holds expectations loosely -- maintaining high standards while releasing attachment to specific results -- can iterate without emotional collapse. + +**Obstacle 5: The Possessed -- Obsession vs. Sustainability** + +"Artists are often portrayed as tortured geniuses. Starving, self-destructive, dancing on the brink of madness. This has instilled the belief that to make art, one has to be broken." the text dismantles the myth of the tortured creator with quiet firmness. Obsessive drive can produce great work, but unsustainable obsession produces burnout, addiction, and abandonment. "Whether you have a powerful passion or a tortured compulsion, neither makes the art any better or worse. If you are able to choose between these paths, consider selecting the more sustainable one." + +The startup culture that celebrates sleepless founders, burnout-as-badge, and "grinding" has internalised the tortured-artist myth in business clothing. the book's counsel is that the creative path is long. The founder who destroys their health and relationships in year two will not be creating in year ten. + +**Obstacle 6: Patience -- The Least Popular Virtue** + +"There are no shortcuts," the text states flatly. "Our continual quest for efficiency discourages looking too deeply. The pressure to deliver doesn't grant us time to consider all possibilities. Yet it's through deliberate action and repetition that we gain deeper insight." Patience is not passive waiting. It is "accepting that the majority of the work we do is out of our control. We can't force greatness to happen. All we can do is invite it in and await it actively." + +The entrepreneurial translation: the company that takes three years to find product-market fit has not failed for three years. It has been practising. "Even the masterpieces that have been produced on tight timelines are the sum of decades spent patiently labouring on other works." Speed-to-market is a tactical variable. The depth of the work is a function of the patience invested in it. + +### The Reset Protocol + +Across all six obstacles, the text returns to a single corrective mechanism: "The first step of clearing is acknowledgement. Notice yourself feeling the weight of self-criticism or the pressure to live up to expectations. And remember that commercial success is completely out of your control. All that matters is that you are making something you love, to the best of your ability, here and now." Acknowledgement is not resolution. It is the precondition for resolution. The entrepreneur who can name the obstacle -- "this is self-doubt," "this is an undermining voice," "this is attachment to outcome" -- has already begun to diminish its power. + +--- + +## Prompts + +**Prompt 1 -- Inner Critic Mapping:** +> I am a founder of [company] and I am experiencing [specific doubt, fear, or creative block]. Using the book's obstacle framework, help me identify which of the six obstacles is operating: self-doubt, undermining voices (internal or external), distraction vs. procrastination, excessive expectations, unsustainable obsession, or impatience. For the identified obstacle, provide a specific book-informed strategy for working alongside it rather than against it. + +**Prompt 2 -- Voice Audit:** +> List the voices currently influencing my creative and strategic decisions as founder of [company]: investors, advisors, board members, team members, customers, press, competitors, and my own internal critic. For each, assess whether the voice is serving the quality of the work or undermining it. Recommend which voices to amplify, which to attenuate, and how to create protected creative space free from all of them. + +**Prompt 3 -- Expectation Calibration:** +> I am about to begin [new project / product launch / pivot / fundraise]. My expectations are [describe]. Using the book's concept of experimental faith, help me separate legitimate quality standards from attachment to specific outcomes. Reframe my approach from "this must succeed in the following way" to "this is an experiment that will teach me something regardless of result." + +**Prompt 4 -- Sustainability Assessment:** +> Honestly evaluate my current working patterns as founder of [company]: [hours, sleep, exercise, relationships, creative vs. administrative time ratio]. Using the book's framework on the possessed vs. the sustainable creator, assess whether my current pace can produce great work over a ten-year horizon. If not, recommend structural changes that preserve creative intensity while ensuring longevity. + +--- + +## Use Cases + +**Validation-stage founder paralysed by fear of market rejection** + +A first-time founder has built an MVP for a consumer fintech product but has delayed launch for four months, finding new "essential" features to add each week. The obstacle diagnosis reveals two interlocking forces: self-doubt ("what if people hate it?") and excessive expectations ("it has to be perfect for launch"). Applying the book's experimental faith reframe -- "the outcome is not up to us; give some attention to each seed and look for a beautiful response" -- converts the launch from a verdict into a test. She ships a stripped-down version within two weeks. User feedback is mixed -- as it always is -- but the paralysis breaks and the iteration cycle begins. + +**Early-traction founder consumed by investor and advisor voices** + +A seed-stage founder with a promising social commerce platform has assembled an advisory board of six experienced operators. Each provides thoughtful but contradictory strategic advice. The founder now changes direction after every advisory call, unable to hold his own creative vision against the weight of external credibility. the book's voice audit reveals that six external voices have colonised the founder's creative process. The intervention is structural: advisory calls are reduced from weekly to monthly, creative work sessions are scheduled before (never after) external meetings, and a daily five-minute practice of articulating "what I believe about this product" rebuilds the founder's own creative authority. + +**Growth-stage CEO approaching burnout** + +A Series B founder has worked eighty-hour weeks for three years. Her company is growing, but her product instincts have dulled. She describes feeling "hollow" -- capable of operational execution but unable to generate the creative insights that characterised the company's early days. The sustainability assessment diagnoses possession: the company has consumed the person. the book's counsel -- "if you are able to choose between these paths, consider selecting the more sustainable one" -- provides philosophical permission for a structural change the founder intellectually knows is necessary but emotionally resists. A three-week creative sabbatical, followed by a restructured role that protects forty percent of her time for creative work, restores both the founder and the company's creative trajectory. + +--- + +## Anti-Patterns + +**1. Interpreting "self-doubt is natural" as permission to wallow.** the text acknowledges doubt as a companion, not as a destination. The founder who uses "self-doubt is part of the process" to justify months of inaction has misread the principle. Doubt walks alongside the work. It does not substitute for it. + +**2. Branding all criticism as "undermining voices."** Not every critical voice is an enemy of creation. Honest feedback from customers, rigorous challenge from co-founders, and difficult questions from investors can sharpen the work. The task is to distinguish between voices that serve quality and voices that serve fear or ego. Dismissing all external input as noise is creative solipsism. + +**3. Using strategic distraction as a euphemism for avoidance.** A thirty-minute walk to process a creative problem is strategic distraction. A three-day retreat to "think about the business" while avoiding a difficult product decision is procrastination wearing a contemplative disguise. The test is simple: does the distraction end with a return to the work? + +**4. Releasing attachment to outcomes so thoroughly that standards disappear.** Experimental faith does not mean anything goes. The founder who ships carelessly and shrugs off poor results as "just an experiment" has abandoned rigour in the name of detachment. High standards and loose attachment to specific outcomes are not contradictory -- they are complementary. + +**5. Confusing patience with complacency.** "There are no shortcuts" does not mean there are no deadlines. Patience is about the depth of engagement with each step, not about the pace of the overall journey. The founder who uses the book's patience principle to justify missing every milestone has weaponised a virtue into a vice. + +--- + +## By Stage + +| Stage | Primary Obstacle | Key Intervention | +|-------|-----------------|------------------| +| Idea | Self-doubt ("Am I even capable of this?") | Normalise doubt as evidence of creative sensitivity; decouple identity from outcome | +| Validation | Fear of rejection and excessive expectations | Reframe launch as experiment, not verdict; practice experimental faith | +| Early Traction | Undermining voices from investors and advisors | Structural protection of creative space; voice audit to separate signal from noise | +| Growth | Unsustainable obsession and burnout | Sustainability assessment; role restructuring to preserve creative capacity | +| Scale | Institutional impatience and results pressure | Embed patience into product culture; resist the organisation's natural bias toward speed over depth | + +At the idea stage, the dominant obstacle is existential: does the founder believe they are capable of creating something worth building? Self-doubt at this stage is not about a specific product or market -- it is about creative identity itself. The intervention connects directly to the creative-identity-and-purpose skill: the founder must first grant themselves permission to create before they can navigate the obstacles that creation produces. + +At growth and scale, the obstacles shift from personal to institutional. The CEO's inner critic is replaced by the board's quarterly expectations. The founder's impatience is replaced by the market's. The principles remain the same -- name the obstacle, acknowledge it, create protected space for the work -- but they must be applied at organisational scale, which requires explicit cultural choices about how the company relates to doubt, criticism, experimentation, and time. + +--- + +## Output Template + +```markdown +# Creative Obstacles Assessment -- [Company/Project] + +**Date:** [Date] +**Context:** [What prompted this assessment] + +## Obstacle Inventory + +| Obstacle | Present? | Intensity (1-5) | Impact on Work | Current Response | +|----------|----------|-----------------|----------------|-----------------| +| Self-doubt | [Y/N] | [1-5] | [How it manifests] | [What I do now] | +| Undermining voices | [Y/N] | [1-5] | [Specific voices] | [Current response] | +| Distraction / Procrastination | [Y/N] | [1-5] | [Which type?] | [Current pattern] | +| Excessive expectations | [Y/N] | [1-5] | [Specific expectations] | [How they constrain] | +| Unsustainable obsession | [Y/N] | [1-5] | [Physical/emotional signs] | [Current coping] | +| Impatience | [Y/N] | [1-5] | [Where rushing?] | [What gets skipped] | + +## Voice Map + +| Voice | Source (Internal/External) | Serves Quality? | Serves Fear/Ego? | Action | +|-------|--------------------------|-----------------|-------------------|--------| +| [Voice 1] | [Source] | [Y/N] | [Y/N] | [Amplify / Attenuate / Remove] | +| [Voice 2] | [Source] | [Y/N] | [Y/N] | [Action] | + +## Protected Creative Space Plan +- **When:** [Scheduled times free from external voices] +- **Where:** [Physical/digital environment] +- **Duration:** [Minimum protected hours per week] +- **Boundary rules:** [What is excluded during this time] + +## Experimental Faith Statement +[Reframe current challenge from "this must succeed" to "this experiment will teach me..."] + +## Sustainability Check +- **Current weekly hours:** [Number] +- **Sleep quality:** [Good / Fair / Poor] +- **Creative energy level:** [High / Medium / Low / Depleted] +- **Sustainable for 10 years?** [Honest assessment] +- **One structural change to improve sustainability:** [Specific action] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](../../content/skills/creative/creative-identity-and-purpose.md)** -- Self-doubt attacks creative identity at its root; the permission framework provides the philosophical foundation for withstanding it. +- **[Creative Perception and Awareness](../../content/skills/creative/creative-perception-and-awareness.md)** -- Obstacles cloud perception; clearing them restores the ability to receive creative signals cleanly. +- **[Creative Practice and Habit](../../content/skills/creative/creative-practice-and-habit.md)** -- Consistent practice is the primary antidote to most creative obstacles; showing up daily diminishes doubt's authority over time. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Flow states are disrupted by self-doubt, distraction, and excessive expectations; removing these obstacles creates the conditions for optimal creative experience. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- The Stoic discipline of managing emotional responses complements the approach to internal creative resistance. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The dichotomy of control maps directly onto the insistence that commercial success is outside the artist's control while the quality of the work is within it. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Creative failure is a specific form of the broader failure experience; the practices for examining setbacks without shame apply directly to creative work that does not meet expectations. diff --git a/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md b/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md deleted file mode 120000 index 9e824ed..0000000 --- a/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-perception-and-awareness.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md b/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md new file mode 100644 index 0000000..f7005cc --- /dev/null +++ b/plugins/foreman/skills/creative-perception-and-awareness/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "creative-perception-and-awareness" +description: "Develops the entrepreneur's capacity to receive creative signals by applying principles of tuning in, deep awareness, and perceptual sensitivity. Covers the vessel-and-filter model, seeing the unseen, nature as teacher, deep listening, the role of subconscious and memory, and how setting shapes creative output. Use when feeling creatively numb, missing market signals, unable to generate fresh product ideas, sensing that important information is passing you by, or needing to sharpen intuitive pattern recognition for innovation." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - awareness + - perception + - tuning-in + - listening + - intuition + - subconscious + - pattern-recognition + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-practice-and-habit + - creative-obstacles + - flow-state + - stoic-self-awareness + - stoic-unbiased-thought + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Entrepreneur as Antenna + +Creativity is not about producing -- it is about receiving. The universe broadcasts constantly; the question is whether your antenna is tuned. The text frames the creative act not as an act of will but as an act of perception: "We are all antennae for creative thought. Some transmissions come on strong, others are more faint. If your antenna isn't sensitively tuned, you're likely to lose the data in the noise." The entrepreneur who treats innovation as a manufacturing process -- inputs, throughput, outputs -- misses the deeper truth that the best products, brands, and companies begin not with effort but with noticing. A market gap is not calculated into existence; it is perceived. A customer need is not deduced; it is felt. The foundation of creative entrepreneurship is not productivity. It is sensitivity. + +--- + +## The Framework + +### The Signal Architecture + +the book's model of creative perception operates across five interlocking layers, each of which sharpens the entrepreneur's ability to detect, receive, and act on creative information. + +**Layer 1: Tuning In -- The Cosmic Frequency** + +"Think of the universe as an eternal creative unfolding," the text argues. "Trees blossom. Cells replicate. Rivers forge new tributaries." Creativity is not something humans invented. It is a force we participate in. The entrepreneur who acknowledges this shift -- from creator to conduit -- gains access to a richer information stream. Ideas, the text suggests, exist in an "aether" and ripen on schedule. "If you have an idea you're excited about and you don't bring it to life, it's not uncommon for the idea to find its voice through another maker." The practical implication is stark: the window for any given creative opportunity has a natural expiry. Tuning in is not optional. It is time-sensitive. + +**Layer 2: Awareness -- The Foundational Capacity** + +Awareness, in the book's system, is not analytical. It is pre-analytical. "The gift of awareness allows us to notice what's going on around and inside ourselves in the present moment. And to do so without attachment or involvement." The moment an entrepreneur labels what they are perceiving -- "that's a market trend," "that's a competitor threat" -- they have left awareness and entered analysis. Analysis has its place, but it is a secondary function. "The awareness happens first as a pure connection with the object of your attention. If something strikes me as interesting or beautiful, first I live that experience. Only afterward might I attempt to understand it." For the entrepreneur, this means cultivating the discipline to notice before categorising, to feel before strategising. + +**Layer 3: The Vessel and the Filter** + +Every person carries what the text calls a "vessel" -- a container of accumulated thoughts, feelings, experiences, and perceptions. Information reaches the vessel through a "filter" that is unique to each individual. The filter is simultaneously essential and limiting: it prevents sensory overwhelm but also distorts incoming data. "Our filter inevitably reduces Source intelligence by interpreting the data that arrives instead of letting it pass freely." Over time, the filter produces beliefs and stories that harden into a worldview -- which then shapes what the entrepreneur is capable of perceiving. The practical work is twofold: expand the vessel's capacity (take in more) and soften the filter's rigidity (distort less). "With training, we can improve our interface with Source and radically expand the vessel's ability to receive." + +**Layer 4: Looking for Clues and Seeing the Unseen** + +the text describes creative information as arriving through channels that defy conventional analysis. "Material for our work surrounds us at every turn. It's woven into conversation, nature, chance encounters, and existing works of art." The entrepreneur who walks through a trade show scanning for competitive intelligence is using analysis. The one who walks through and notices an unexpected emotional reaction to a particular booth layout -- then follows that reaction to its source -- is using awareness. the book's "unseen" is not mystical obfuscation. It is the recognition that the most valuable creative signals are often the subtlest: "They are energetic more than tactile, intuitively perceived more than consciously recorded." + +**Layer 5: The Inner Landscape and the Subconscious** + +The final layer turns the antenna inward. "If we focus on what's going on inside ourselves -- sensations, emotions, the patterns of our thoughts -- a wealth of material can be found. Our inner world is every bit as interesting, beautiful, and surprising as nature itself." the text advocates practices that access the subconscious -- dream journals, automatic writing, physical exercises that bypass the analytical mind. "There's an abundant reservoir of high-quality information in our subconscious, and finding ways to access it can spark new material to draw from." For the entrepreneur, this means that strategic insight does not always emerge from spreadsheets. Sometimes it surfaces during a shower, a drive with no destination, or the liminal space between sleep and waking. + +### Environmental Design: Setting as Instrument + +the text devotes particular attention to how physical environment shapes perception. "Isolated places like a forest, a monastery, or a sailboat in the middle of the ocean are fine locations to receive direct transmissions from the universe. If instead you want to tune in to the collective consciousness, you might sit in a busy spot with people coming and going." The implication for entrepreneurs is that workspace design is not an operational question -- it is a creative one. Andy Warhol created with a television, radio, and record player all running simultaneously. Marcel Proust lined his walls with cork and wore earplugs. Neither was wrong. The question is which environment serves the specific creative task at hand. + +### Nature as the Ultimate Calibrator + +"Of all the great works that we can experience, nature is the most absolute and enduring." the text uses nature not as a metaphor but as a practice. The entrepreneur who spends time in natural settings is not relaxing -- they are recalibrating their perceptual instrument. "If you're picking colours based on a Pantone book, you're limited to a certain number of choices. If you step out in nature, the palette is infinite." Nature bypasses the filter and speaks directly to the vessel. + +### Deep Listening + +"Listening is paying attention to those sounds, being present with them, being in communion with them." the text distinguishes sharply between hearing (passive reception) and listening (active presence). "Formulating an opinion is not listening. Neither is preparing a response, or defending our position or attacking another's. To listen impatiently is to hear nothing at all." For the entrepreneur conducting customer interviews, investor meetings, or team discussions, this distinction is the difference between extracting data and receiving insight. + +--- + +## Prompts + +**Prompt 1 -- Perceptual Audit:** +> Map my current information diet as founder of [company]. Where am I receiving creative signals (customer conversations, nature, art, stillness, movement)? Where am I relying exclusively on analytical inputs (dashboards, reports, competitor analysis)? Using the book's vessel-and-filter model, identify where my filter may be distorting or blocking incoming creative data, and recommend practices to soften it. + +**Prompt 2 -- Deep Listening Diagnostic:** +> Analyse my last three [customer interviews / team meetings / investor conversations]. Where did I listen to understand, and where did I listen to respond? Where might I have missed subtler signals -- emotional undertones, unspoken concerns, unexpected phrasing -- because my filter was already categorising the information? Provide a listening protocol based on the book's principle that "listening is suspending disbelief." + +**Prompt 3 -- Environment-Creativity Mapping:** +> I currently work in [describe workspace and daily environment]. Using the book's framework on setting, assess how my physical environment may be shaping my creative output. Recommend specific environmental changes for different types of creative work: ideation, focused building, strategic reflection, and collaborative creation. + +**Prompt 4 -- Clue Detection Exercise:** +> I am stuck on [specific product/business challenge]. Instead of analytical problem-solving, guide me through the book's "look for clues" practice. Help me design a 48-hour awareness exercise where I hold this question loosely in consciousness while engaging with diverse inputs -- conversations, walks, art, reading -- and document any unexpected connections or resonances that arise. + +--- + +## Use Cases + +**Validation-stage founder missing customer signals** + +A B2B SaaS founder conducts weekly customer discovery calls following a rigorous script. Her conversion from trial to paid is stagnant at 4%. Applying the book's deep listening principle reveals the problem: she listens to confirm her hypothesis, not to receive what customers are actually communicating. A shift to unscripted, awareness-based conversations -- where she follows emotional energy rather than a question list -- surfaces a pain point she had systematically filtered out because it did not match her product thesis. The pivot takes six weeks. Conversion triples. + +**Growth-stage product team suffering from creative blindness** + +A consumer app team has shipped twelve incremental updates in a row, each marginally better than the last. The head of product describes the feeling as "running on a treadmill." The vessel-and-filter diagnosis identifies the cause: the team's perceptual apparatus has been narrowed to a single data stream -- usage analytics. Introducing the book's environmental practices -- weekly team walks without devices, exposure to products in completely unrelated industries, a "clue journal" for recording unexpected observations -- broadens the vessel. Within a month, the team identifies a feature concept that originated from a team member's observation at a farmer's market. It becomes the most successful release of the year. + +**Idea-stage entrepreneur who cannot "find" an idea** + +An aspiring founder with capital, talent, and ambition has spent six months trying to identify a startup concept through market analysis and trend reports. Nothing resonates. The problem, through the book's lens, is that she is looking analytically for something that arrives perceptually. Shifting from search to reception -- spending mornings in awareness practice, afternoons in diverse environments (hospitals, construction sites, schools, kitchens), and evenings recording what moved her -- produces three viable concepts within four weeks. The winning idea comes from a whispered observation during a visit to her grandmother's assisted-living facility. + +--- + +## Anti-Patterns + +**1. Treating awareness as a substitute for execution.** the book's perception framework is a complement to action, not a replacement for it. The entrepreneur who spends months "tuning in" without building, shipping, or testing has confused receptivity with procrastination. Awareness feeds creation; it does not replace it. + +**2. Romanticising the subconscious into mysticism.** Dream journals and automatic writing are practical tools for accessing non-analytical insight. They are not divination. The founder who bases product strategy on a dream without subjecting that insight to rigorous validation has abandoned judgement, not transcended it. + +**3. Using "deep listening" to avoid making decisions.** the book's listening is a perceptual practice, not an excuse for consensus paralysis. The entrepreneur who keeps listening and never acts -- who conducts another round of interviews, another survey, another advisory session -- is using awareness as a shield against the discomfort of commitment. + +**4. Confusing environmental novelty with creative productivity.** Changing your workspace every week, working from exotic locations, and curating an aesthetically perfect studio are all forms of environmental optimisation that can become displacement activities. The setting serves the work. It is not the work. + +**5. Ignoring analytical data in favour of "intuition."** the book's framework places awareness before analysis, not above it. The entrepreneur who dismisses churn metrics, financial projections, or user feedback because they are "tuning in to a deeper signal" has elevated one mode of knowing while dismantling the other. Both are required. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Broadening the vessel; maximum receptivity | The task is to perceive widely before filtering narrowly; premature focus on a single market or concept constricts the antenna | +| Validation | Listening to customers without the filter of confirmation | Awareness-based customer discovery detects signals that structured interviews miss | +| Early Traction | Noticing what the product is "trying to become" | The product itself sends signals through usage patterns, support tickets, and unexpected use cases; the founder's job is to perceive them | +| Growth | Detecting weak signals amid operational noise | As the organisation generates more data, the analytical mode threatens to drown out perceptual insight; deliberate awareness practices become essential | +| Scale | Distributing perceptual capacity across the organisation | The founder alone cannot be the company's antenna; building teams and cultures that value perception alongside analysis is the institutional challenge | + +At the idea stage, the vessel is relatively empty and the filter relatively soft -- which is an advantage. The discipline is to resist the pressure to narrow too quickly. Advisors, accelerators, and investors will demand focus. Some of that demand is legitimate. But the entrepreneur who narrows before perceiving broadly will build on a foundation of insufficient information. the book's reminder that "the universe is only as large as our perception of it" applies directly: the founder's market is only as large as their awareness allows it to be. + +At validation, the perceptual challenge is confirmation bias. The filter hardens around the hypothesis the founder wants to be true. the book's counsel to practice awareness "without attachment or involvement" is the antidote: listen to customers without an agenda, observe usage patterns without imposing a narrative, and resist the reflex to interpret ambiguous signals as validation. The whisper that contradicts your thesis may be more valuable than the shout that confirms it. + +At early traction, the product itself becomes a perceptual object. It sends signals through the way customers use it -- including the ways they use it that were never intended. The founder's job shifts from perceiving the market to perceiving their own creation with fresh eyes. "You can't step into the same stream twice because it's always flowing," the text argues. The product is flowing too. Perceiving its evolution -- rather than insisting it match the original vision -- is how companies discover their true value proposition. + +At growth, the signal-to-noise ratio deteriorates. Dashboards, OKRs, quarterly reviews, and board meetings generate a torrent of analytical data that can drown the subtler perceptual signals. The founder who once noticed a customer's hesitation in a demo now receives that information thirdhand, filtered through layers of reporting. Deliberate practices -- unscripted customer conversations, time spent using the product as a customer would, environmental shifts away from the office -- become essential to maintain perceptual acuity. + +At scale, the challenge is delegation. The founder's personal perceptual sensitivity cannot serve a thousand-person organisation. The question becomes: how do you hire, train, and organise for collective awareness? Companies that solve this problem build products with an uncanny ability to anticipate market shifts. Those that do not become operationally excellent and creatively inert. Embedding the book's "look for clues" mentality into product teams, design sprints, and customer-facing roles transforms perception from a founder's personal gift into an organisational capability. + +--- + +## Output Template + +```markdown +# Creative Perception Assessment -- [Company/Project] + +**Date:** [Date] +**Context:** [Specific creative challenge or general perceptual audit] + +## Current Signal Diet + +| Source | Type (Analytical / Perceptual) | Frequency | Quality (H/M/L) | +|--------|-------------------------------|-----------|------------------| +| [e.g., Usage dashboards] | Analytical | Daily | [H/M/L] | +| [e.g., Customer conversations] | Mixed | Weekly | [H/M/L] | +| [e.g., Nature / stillness] | Perceptual | [Frequency] | [H/M/L] | +| [e.g., Art / unrelated industries] | Perceptual | [Frequency] | [H/M/L] | + +## Vessel and Filter Diagnosis + +**Vessel capacity:** [Expansive / Adequate / Constricted] +**Filter rigidity:** [Soft / Moderate / Hardened] +**Dominant beliefs shaping the filter:** [List 3-5 assumptions about market, product, or identity] +**Signals likely being blocked:** [What might I not be seeing?] + +## Awareness Practice Plan + +| Practice | Frequency | Duration | Purpose | +|----------|-----------|----------|---------| +| [e.g., Morning awareness walk] | Daily | 20 min | Broaden perceptual baseline | +| [e.g., Unscripted customer conversation] | Weekly | 30 min | Deep listening without agenda | +| [e.g., Clue journal] | Daily | 5 min | Record unexpected resonances | +| [e.g., Environmental shift] | Weekly | 2 hours | Change setting to change perception | + +## Clues Detected This Period +1. [Observation + where it came from + potential relevance] +2. [Observation + where it came from + potential relevance] +3. [Observation + where it came from + potential relevance] + +## Next Step +[Specific action informed by perceptual insight] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](../../content/skills/creative/creative-identity-and-purpose.md)** -- Perception without creative identity is data collection; identity provides the purpose that directs awareness. +- **[Creative Practice and Habit](../../content/skills/creative/creative-practice-and-habit.md)** -- Awareness must be practised daily to become a default mode; this skill provides the discipline structures. +- **[Creative Obstacles](../../content/skills/creative/creative-obstacles.md)** -- Self-doubt and distraction are the primary enemies of perceptual clarity; this skill addresses them directly. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Csikszentmihalyi's flow describes the psychological state the awareness practices are designed to access, approached from a theoretical angle. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- Stoic self-examination operates through rational inquiry; creative awareness operates through perceptual sensitivity -- complementary paradigms for the same goal. +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- The Homework for Life practice is a specific application of perceptual awareness: training oneself to notice the story-worthy moments that most people overlook. diff --git a/plugins/foreman/skills/creative-practice-and-habit/SKILL.md b/plugins/foreman/skills/creative-practice-and-habit/SKILL.md deleted file mode 120000 index a200e0f..0000000 --- a/plugins/foreman/skills/creative-practice-and-habit/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-practice-and-habit.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-practice-and-habit/SKILL.md b/plugins/foreman/skills/creative-practice-and-habit/SKILL.md new file mode 100644 index 0000000..634d547 --- /dev/null +++ b/plugins/foreman/skills/creative-practice-and-habit/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "creative-practice-and-habit" +description: "Transforms creativity from sporadic inspiration into daily discipline by applying principles of practice, habit formation, seed collection, experimentation, immersion in great works, and momentum management. Use when struggling to maintain a creative routine, waiting for inspiration to strike, unsure how to develop raw ideas into viable products, losing creative momentum mid-project, or wanting to improve the quality of creative inputs to elevate outputs." +version: "1.0.0" +category: "creative" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creativity + - practice + - habits + - experimentation + - momentum + - seeds + - discipline + - craft + - creative-philosophy +related_skills: + - creative-identity-and-purpose + - creative-perception-and-awareness + - creative-obstacles + - flow-state + - stoic-right-action + - stoic-pragmatism + - stoic-control-and-clarity +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Daily Reps + +The text's vision of creativity is not waiting for lightning. It is a muscular practice. Plant seeds, water them, wait. "Good habits create good art," he writes, with the kind of plainness that disguises a radical claim. "The way we do anything is the way we do everything." The romantic image of the artist seized by divine inspiration -- scribbling furiously at 3 a.m., unable to stop -- is not false, but it is incomplete. What the romance omits is the years of disciplined preparation that made the 3 a.m. seizure possible. John Wooden, the most successful coach in college basketball history, spent the first day of every season teaching elite athletes to tie their shoes. The entrepreneur who believes creative breakthroughs happen to people rather than being cultivated by them will spend a career waiting for a moment that preparation would have summoned. + +--- + +## The Framework + +### The Four Phases of Creative Discipline + +the book's approach to creative practice follows a natural progression -- from gathering raw material through experimentation to craft and ultimately release. Each phase demands a different kind of discipline. + +**Phase 1: Seeds -- Gathering Without Judgement** + +"In the first phase of the creative process, we are to be completely open, collecting anything we find of interest." the text calls these collected fragments "seeds" -- phrases, observations, sketches of ideas, customer complaints, unusual interactions, fragments of conversation. The critical discipline in this phase is non-evaluation. "As the seeds arrive, forming conclusions about their value or fate can get in the way of their natural potential." The entrepreneur who immediately judges every idea against ROI projections, market size, or technical feasibility kills seeds before they can germinate. + +the book's guidance is patient: "It's generally preferable to accumulate several weeks' or months' worth of ideas and then choose which of them to focus on, instead of following an urge or obligation to rush to the finish line with what is in front of us today." For the entrepreneur, this translates to maintaining an active idea journal -- not a business plan, not a feature backlog, but a raw, unjudged collection of observations and possibilities. + +**Phase 2: Experimentation -- Play Without Stakes** + +"Fueled by the initial hit of excitement at discovering a starting point, we play with different combinations and possibilities to see if any of them reveal how the seed wants to develop." This is the phase most entrepreneurs skip. The pressure to build, ship, and measure drives founders directly from idea to execution, bypassing the experimental stage where the idea reveals its true form. + +the text is explicit about what experimentation requires: "This is one of the fun parts of a project, because nothing is at stake. You get to play with forms and see what takes shape. There are no rules." The entrepreneur's equivalent is the rapid prototype, the low-fidelity mockup, the "what if" conversation with a trusted collaborator. Ancient Chinese alchemists searching for immortality stumbled upon gunpowder. Penicillin, plastic, pacemakers, and Post-it notes were all accidents of experimentation. "Consider how many innovations that might have changed the world have been lost because someone was so focused on their goal, they missed the revelation right in front of them." + +The selection criterion during experimentation is emotional, not analytical. "Often the most accurate signposts are emotional, not intellectual. Excitement tends to be the best barometer for selecting which seeds to focus on." + +**Phase 3: Try Everything -- Testing Before Judging** + +"To dismiss an idea because it doesn't work in your mind is to do a disservice to the art. The only way to truly know if any idea works is to test it." the text insists that ideas must be physically manifested -- built, spoken, drawn, performed -- before they can be evaluated. "Descriptions do not do ideas justice." This principle has direct application to product development: the feature that sounds mediocre in a brainstorm may prove transformative in a prototype. The strategy that seems brilliant on a whiteboard may collapse on contact with a real customer. + +The corollary is equally powerful: "Persuasion leads to mediocrity." In team settings, the most articulate advocate often wins the debate -- but articulation is not the same as quality. the book's method demands that competing ideas be tested rather than argued. + +**Phase 4: Momentum -- The Craft of Finishing** + +"When we become overly attached to a premature version of the work, we do a disservice to the project's potential." the text identifies two momentum killers with precision. The first is disconnection: lingering too long in the craft phase until the artist has changed and the work no longer reflects who they are. The second is "demo-itis" -- becoming so attached to an early draft that any improvement feels like betrayal. + +His tactical advice is concrete: "Unless actively working to make something better, avoid listening to it, reading it, playing it, looking at it, or showing it to friends." For the entrepreneur, this means resisting the urge to endlessly revisit mockups, re-read pitch decks, or demo unfinished products to friends. Work forward. Step away. Return with fresh perception. + +### The Infrastructure of Habit + +Surrounding the four phases is the book's broader philosophy of habit formation. "Discipline and freedom seem like opposites. In reality, they are partners. Discipline is not a lack of freedom, it is a harmonious relationship with time." The practical implications: + +- **Start small.** "If you commit to working for half an hour a day, something good can happen that generates momentum. You may then look at the clock and realize you've been working for two hours." +- **Reduce life-maintenance decisions.** "Albert Einstein wore the same thing daily: a gray suit. Erik Satie had seven identical outfits. Limit your practical choices to free your creative imagination." +- **Examine existing habits before adding new ones.** "How often do we consider examining and removing the habits that currently drive our days?" +- **Separate creative time from administrative time.** "Approaching the practical aspects of your day with military precision allows the artistic windows to be opened in childlike freedom." + +### Submerge: The Quality of Inputs + +"Consider submerging yourself in the canon of great works. Read the finest literature, watch the masterpieces of cinema, get up close to the most influential paintings." the text frames input quality as a creative practice, not a leisure activity. "If you make the choice of reading classic literature every day for a year, rather than reading the news, by the end of that time period you'll have a more honed sensitivity for recognising greatness." The entrepreneur's version: study the best companies, the most elegant products, the most powerful brands -- not to imitate them but to calibrate your internal standard. "The objective is not to learn to mimic greatness, but to calibrate our internal meter for greatness." + +--- + +## Prompts + +**Prompt 1 -- Seed Collection Protocol:** +> I am a founder of [company] at the [stage] stage. Design a 30-day seed collection practice for me. Include: what to observe, where to look, how to record seeds without judging them, and a review cadence for assessing which seeds show life. Tailor the observation domains to my industry ([industry]) and the specific creative challenges I face ([challenges]). + +**Prompt 2 -- Experimentation Sprint Design:** +> I have [number] raw ideas / seeds for [product feature / business concept / brand direction]. Design an experimentation sprint where each idea is physically tested -- not discussed or debated -- within [timeframe]. For each idea, specify: the lowest-fidelity way to manifest it, who should experience it, and what emotional/energetic response to watch for as a signal of viability. + +**Prompt 3 -- Creative Habit Architecture:** +> Analyse my current daily and weekly routine: [describe schedule]. Using the book's habit principles, identify: (a) where creative time is being consumed by administrative decisions, (b) which existing habits may be undermining creative output, (c) a restructured schedule that creates dedicated creative windows with minimal decision overhead. Start small -- thirty minutes daily. + +**Prompt 4 -- Input Quality Audit:** +> Catalogue my current creative inputs -- what I read, watch, listen to, and engage with regularly. Using the book's "submerge in great works" principle, assess whether my inputs are calibrating my taste upward or merely reinforcing existing patterns. Recommend a 90-day input diet tailored to [my industry / the creative challenge I face], including specific works, companies, and experiences to engage with. + +--- + +## Use Cases + +**Idea-stage founder who "can't find" a good idea** + +A technical co-founder has spent four months reading market reports and trend analyses, waiting for a startup idea that passes his analytical filters. He has rejected dozens of concepts as "too small," "too competitive," or "not defensible." Applying the book's seed collection principle reframes the problem: he has been evaluating seeds at the moment of arrival, killing them before they can germinate. A thirty-day non-judgemental collection practice -- recording every observation, frustration, and curiosity in a dedicated journal -- yields 147 seeds. During the review, seed number eighty-three (an offhand complaint from his mother about managing her medications) connects with seed number twelve (a technical insight about voice interfaces) and produces a concept he would never have reached through analysis alone. + +**Early-traction team stuck in "analysis paralysis" over a feature direction** + +A product team has spent three weeks debating two feature directions for their next release. Each side has compelling data and articulate advocates. Applying the book's "try everything" principle breaks the deadlock: both features are prototyped at minimum fidelity in forty-eight hours and tested with five users each. The feature that sounded weaker in debate produces visibly more energetic user responses. It ships in two weeks and drives a 22% increase in engagement. + +**Growth-stage founder losing creative edge** + +A founder who built her company on creative instinct now spends 80% of her time in operational meetings, investor updates, and hiring reviews. Her last three product decisions were competent but uninspired. The creative habit architecture intervention reveals that she has no dedicated creative time -- not thirty minutes, not ten. Restructuring her week to include two ninety-minute creative blocks (protected from all meetings and communications) and replacing her morning news consumption with exposure to great design, architecture, and literature begins to restore the creative sensitivity that built the company. + +--- + +## Anti-Patterns + +**1. Collecting seeds forever without experimenting.** The seed phase has a natural rhythm. Accumulate for weeks or months, then shift to experimentation. The entrepreneur who has been "gathering ideas" for two years without testing any of them is not practising patience -- they are practising avoidance. + +**2. Skipping experimentation and jumping to execution.** The pressure to ship is real, but the cost of building the wrong thing is higher than the cost of a week spent experimenting. The founder who moves from idea to Jira ticket without a prototyping phase will build efficiently and often build the wrong thing. + +**3. Evaluating experiments analytically during the experimental phase.** the text is clear that the early signals are emotional, not intellectual. Subjecting a rough prototype to a formal ROI analysis is like judging a seedling by the fruit it has not yet produced. Follow energy first. Apply rigour later. + +**4. Confusing routine with rigidity.** Creative habits should evolve. the text notes that "awareness needs constant refreshing. If it becomes a habit, even a good habit, it will need to be reinvented again and again." The founder whose creative routine has not changed in two years may have a schedule, but not a practice. + +**5. Using "submerge in great works" as sophisticated procrastination.** Reading, watching, and studying are creative inputs. They are not creative outputs. The entrepreneur who spends six months consuming masterpieces without producing anything has inverted the relationship between input and output. Inputs serve the work. The work must still be done. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Seed collection and early experimentation | Maximum openness; the discipline is gathering without judging, not building without thinking | +| Validation | Rapid experimentation cycles | Seeds are tested against real users; emotional signals are validated with behavioural data | +| Early Traction | Habit architecture for founder creative time | As operational demands grow, creative time must be structurally protected or it vanishes | +| Growth | Input quality and team creative practices | The founder's creative habits must scale; input diet and experimentation become team disciplines | +| Scale | Institutional creative infrastructure | Seed collection, experimentation, and creative time are embedded in product development processes, not dependent on individual heroics | + +At the idea stage, the entire company is a creative practice. There is nothing else. The founder's daily life is seed collection, experimentation, and the gradual emergence of a concept worth building. The discipline is restraint: not committing too early, not judging too harshly, not confusing analytical rigour with creative clarity. + +At scale, the founder's personal creative practice matters less than the organisation's creative infrastructure. The question shifts from "how do I maintain my creative habits?" to "how does this company experiment, collect seeds, and maintain creative momentum at the institutional level?" Companies that answer this question build products that continue to surprise. Those that do not become efficient executors of yesterday's ideas. + +--- + +## Output Template + +```markdown +# Creative Practice Plan -- [Company/Project] + +**Date:** [Date] +**Phase:** [Seed Collection / Experimentation / Craft / Momentum] + +## Current Seed Inventory +| # | Seed (Raw Observation/Idea) | Date Collected | Energy Level (H/M/L) | Status | +|---|---------------------------|----------------|----------------------|--------| +| 1 | [Description] | [Date] | [H/M/L] | [Dormant / Sprouting / Testing] | +| 2 | [Description] | [Date] | [H/M/L] | [Status] | +| 3 | [Description] | [Date] | [H/M/L] | [Status] | + +## Experimentation Queue +| Seed # | Experiment Design | Fidelity | Duration | Signal to Watch For | +|--------|------------------|----------|----------|-------------------| +| [#] | [How to test] | [Low/Med] | [Hours/Days] | [Emotional/energetic response] | + +## Creative Habit Architecture +| Time Block | Activity | Purpose | Frequency | +|-----------|----------|---------|-----------| +| [e.g., 6:00-6:30 AM] | [e.g., Awareness walk] | Perceptual baseline | Daily | +| [e.g., 9:00-10:30 AM] | [e.g., Protected creative work] | Experimentation / craft | Daily | +| [e.g., Lunch break] | [e.g., Great works input] | Taste calibration | 3x weekly | + +## Input Diet (Current Quarter) +| Medium | Specific Work/Source | Why | +|--------|---------------------|-----| +| Reading | [Title] | [Connection to current creative challenge] | +| Visual | [Film/Exhibition/Product] | [What it calibrates] | +| Experience | [Place/Activity] | [What it opens] | + +## Momentum Status +**Current project phase:** [Phase] +**Days since last forward progress:** [Number] +**Risk of demo-itis:** [Low / Medium / High] +**Next action to maintain momentum:** [Specific step] +``` + +--- + +## Related Skills + +- **[Creative Identity and Purpose](../../content/skills/creative/creative-identity-and-purpose.md)** -- Practice without identity is mere routine; identity provides the creative purpose that sustains discipline through resistance. +- **[Creative Perception and Awareness](../../content/skills/creative/creative-perception-and-awareness.md)** -- Seed collection depends on perceptual sensitivity; the sharper the awareness, the richer the raw material for practice. +- **[Creative Obstacles](../../content/skills/creative/creative-obstacles.md)** -- Self-doubt, distraction, and the inner critic are the forces that derail creative practice; this companion skill addresses them directly. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- The creative habits are designed to facilitate the conditions Csikszentmihalyi identifies as prerequisites for flow: clear goals, immediate feedback, and challenge-skill balance. +- **[Stoic Right Action](../../content/skills/stoic/stoic-right-action.md)** -- The Stoic emphasis on daily discipline and doing the work regardless of outcome aligns with the philosophy that practice is not about results but about showing up. +- **[Writing Process](../../content/skills/writing/writing-process.md)** -- The MACJ framework provides a structured creative process that applies the same principle of separating generation from judgment that creative practice depends on. diff --git a/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md b/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md deleted file mode 120000 index 37e35e9..0000000 --- a/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/creative/creative-shaping-and-craft.md \ No newline at end of file diff --git a/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md b/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md new file mode 100644 index 0000000..a67b209 --- /dev/null +++ b/plugins/foreman/skills/creative-shaping-and-craft/SKILL.md @@ -0,0 +1,204 @@ +--- +name: "creative-shaping-and-craft" +description: "Guides the entrepreneur through shaping raw creative material into disciplined form, applying intention, rules, temporary constraints, assumption reversal, point-of-view discovery, pattern-breaking, and distillation to essence. Use when refining a product concept, setting creative direction for a brand, defining project constraints, challenging default assumptions about market or offering, finding a unique positioning voice, breaking creative stagnation, or stripping a pitch or product to its irreducible core." +version: "1.0.0" +category: "creative" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - creative-process + - craft + - constraints + - intention + - essence + - refinement + - point-of-view + - assumptions +related_skills: + - creative-flow-and-inspiration + - creative-completion-and-renewal + - creative-collaboration-and-context + - blue-ocean-strategy +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Shaping and Craft + +Michelangelo claimed he never created a sculpture. He simply removed the stone that was not the statue. The figure was already there -- trapped, waiting, fully formed inside the marble. His job was subtraction. The text describes the creative process in strikingly similar terms: "Distilling a work to get it as close to its essence as possible is a useful and informative practice. Notice how many pieces you can remove before the work you're making ceases to be the work you're making." For the entrepreneur, this principle is both liberating and ruthless. The product, the pitch, the brand -- none require more. They require less. The discipline of shaping is not the discipline of addition. It is the discipline of finding what was always there and cutting away everything that obscures it. + +--- + +## The Framework + +the book's approach to shaping creative work moves through seven interconnected dimensions. They are not sequential steps so much as lenses -- each refracts the same raw material differently, and the craftsperson rotates between them as the work demands. + +### 1. Intention -- The Invisible Architecture + +Every creative act carries a single animating purpose. the text calls it "the grand gesture of the work." Intention is not a business plan, not a goal statement, not a mission deck. It is the alignment of conscious purpose with unconscious conviction: "It requires an alignment of all aspects of one's self. Of conscious thought and unconscious beliefs, of capabilities and commitment." + +The old man drawing water from a well by hand, the text recounts, refused the pulley because mechanisation would drain the care from the act -- and with it, the quality. Intention is the care embedded in every decision. Remove intention and all that remains is "the ornamental shell." + +For the entrepreneur, this means a product built without genuine conviction about the problem it solves will feel hollow regardless of its technical elegance. Customers sense the difference between work animated by purpose and work assembled by process. + +### 2. Rules -- Assumptions Masquerading as Laws + +the text draws a sharp distinction between natural laws and artistic rules: "The rules artists learn are different. They are assumptions, not absolutes." Every industry carries invisible conventions -- pricing models, feature sets, go-to-market sequences, pitch deck formats -- that participants mistake for physical constraints. "Rules direct us to average behaviours. If we're aiming to create works that are exceptional, most rules don't apply." + +The most dangerous rules are the unconscious ones: "Rules obeyed unconsciously are far stronger than the ones set on purpose." A founder who has never questioned why SaaS products charge monthly, or why pitch decks open with the problem slide, is operating under rules they did not choose and may not even recognise. + +### 3. Temporary Rules -- Constraints as Liberation + +Paradoxically, the path to creative freedom often runs through deliberate limitation. Georges Perec wrote an entire novel without the letter "e." Yves Klein restricted his palette to a single shade and discovered a blue the world had never seen. Lars von Trier's Dogme 95 manifesto imposed ten severe filmmaking constraints; the first film made under those rules won the Jury Prize at Cannes. + +the book's principle: "When you accept limitations, your range of choices is reduced. Whether imposed by design or by necessity, it's helpful to see limitations as opportunities." Novel problems lead to original solutions. The entrepreneur who tells a product team "build this feature using only what we have today, with no new dependencies" is not imposing poverty. They are imposing a temporary rule that will force invention. + +### 4. The Opposite Is True -- Assumption Reversal + +For every rule accepted -- what the product must be, what the brand voice sounds like, what the customer expects -- the text advises trying the opposite. "Think of a rule as an imbalance. Darkness and light are only meaningful in relationship with each other." + +This is not contrarianism for its own sake. It is a diagnostic exercise. By imagining the polar opposite of every core assumption, the entrepreneur maps the full spectrum of possibility and discovers where on that spectrum they have unconsciously planted themselves. Sometimes the opposite reveals a superior approach. More often, it sharpens understanding of why the current approach works -- or exposes the specific point where it does not. + +### 5. Point of View -- Your Filter Is the Product + +"Carl Rogers said, 'The personal is the universal,'" the text notes. "The personal is what makes art matter. Our point of view, not our drawing skills or musical virtuosity." + +A point of view is not a positioning statement. It is not constructed; it is emitted. The Beatles did not set out to sound different from Chuck Berry. They were different, and the sound followed. the text distinguishes between a "point" (an idea intentionally expressed) and a "point of view" (the perspective through which work emerges, often unconsciously). Entrepreneurs who try to manufacture a distinctive brand voice through copywriting exercises miss the deeper truth: the voice already exists in the decisions the founder makes, the trade-offs they accept, the customers they choose to serve. + +### 6. Breaking the Sameness -- Pattern Disruption + +When shaping stalls, the work needs disruption, not persistence. the text catalogues a battery of techniques from his studio practice: change the environment, change the stakes, invite an audience, alter the perspective, write for someone else, add imagery, limit the information. The underlying principle is consistent: "Whatever you choose, decide on a framework that breaks your normal rhythm and see where it leads." + +The entrepreneurial translation is direct. When a product development cycle has plateaued, the team needs not another sprint but a different vantage point -- a customer segment they have never studied, a constraint they have never imposed, a competitor's lens through which to view their own offering. + +### 7. Essence -- The Skeleton Test + +"All the work we do, no matter how intricate, holds an underlying essence. A core identity or fundamental structure, like a skeleton supporting flesh." the text uses the image of a child's drawing of a house: remove the window and it is still a house; remove the door and it is still a house; remove the roof and walls but leave the window and door and it ceases to be recognisable. + +The practice of distillation demands asking: which elements, if removed, would cause this product (or pitch, or brand) to stop being itself? Everything else is ornamentation. Saint-Exupery's maxim, which the text quotes, is the governing law: "Perfection is finally obtained not when there is no longer anything to add, but when there's no longer anything to take away." + +--- + +## Prompts + +**Prompt 1 -- Intention Audit:** +> Examine my product/venture: [describe product, market, and founding motivation]. Identify the single animating intention behind this work -- not the business goal, but the deeper conviction that gives the project its energy. Then assess whether my current strategy, messaging, and product decisions are congruent with that intention or have drifted from it. Where is the ornamental shell overtaking the living purpose? + +**Prompt 2 -- Invisible Rules Inventory:** +> List every assumption I am operating under regarding [product category, pricing, distribution, customer segment, pitch format]. For each assumption, identify whether it is a law of nature (immutable), a useful convention (worth following for now), or an unexamined rule masquerading as a law. For the unexamined rules, describe what would happen if I violated each one deliberately. + +**Prompt 3 -- Temporary Constraint Design:** +> My team is stuck on [describe the stalled creative or product challenge]. Design three sets of temporary constraints, inspired by the book's principle that novel problems lead to original solutions. Each constraint set should eliminate a different assumed resource or method. For each, describe the type of innovation the constraint is likely to force and when the constraint should be released. + +**Prompt 4 -- Essence Distillation:** +> Here is my current [pitch / product feature set / brand narrative]: [paste content]. Apply the skeleton test: systematically remove elements one at a time and identify the point at which the work ceases to be itself. What remains is the essence. Present the distilled version and explain what was removed and why it was ornamentation rather than structure. + +--- + +## Use Cases + +**Validation-stage consumer app stripping to essence** + +A founder has built an MVP with fourteen features after six months of customer interviews. Early testers describe the product as "interesting but confusing." Applying the skeleton test, the team removes features one by one, testing each stripped version with five users. At feature number six, they discover that three features alone produce the "this is useful" reaction. The remaining eleven features, each individually justified by a customer interview quote, are ornamentation that obscures the product's core identity. The stripped version launches to three times the activation rate. + +**Growth-stage B2B company breaking the sameness** + +A SaaS company's quarterly product reviews have become formulaic: the same data, the same format, the same incremental improvements. The VP of Product imposes a temporary rule from the book: each product team must present their next quarter's roadmap as if they were building for a completely different customer segment than their current one. The exercise surfaces three feature ideas that would never have emerged from the existing roadmap process -- two of which prove viable for the actual customer base. + +**Early-traction brand discovering its point of view** + +A direct-to-consumer brand has hired three branding agencies in two years, each producing style guides that feel generic. The founder applies the book's distinction between "having a point" and "having a point of view." Instead of commissioning another positioning exercise, she catalogues every decision she has made that competitors would not have made -- the materials rejected, the markets declined, the partnerships refused. The pattern reveals a point of view that was always present but never articulated. The brand voice emerges from those decisions, not from a workshop. + +**Scale-stage enterprise trying the opposite** + +A market-leading enterprise software company has optimised its onboarding funnel for five years. Conversion is strong but growth has plateaued. The product leadership team runs the book's assumption-reversal exercise on their ten core onboarding beliefs. One belief -- "users must complete a guided setup before accessing the product" -- has never been questioned. They try the opposite: drop new users directly into a fully configured demo environment with no setup at all. The variant produces a 22% improvement in seven-day retention. The guided setup, designed to reduce friction, was itself the friction. Five years of optimising around the wrong assumption had concealed the issue because the assumption was invisible. + +--- + +## Anti-Patterns + +**Confusing subtraction with minimalism as aesthetic.** Distilling to essence does not mean making everything spare and clean. A maximalist product can be at its essence. The question is whether every element is structural, not whether there are few elements. Stripping a product to look minimal while removing features users depend on is cosmetic surgery, not sculpture. + +**Imposing temporary rules that become permanent doctrine.** the text warns that "every innovation risks becoming a rule." A constraint that produced a breakthrough in one product cycle can calcify into policy. The point of temporary rules is their temporariness. Review and retire them. + +**Intellectualising intention instead of living it.** Intention, in the book's framework, is not a statement you write on a whiteboard. It is a state of alignment between belief and action. A founder who crafts a beautiful mission statement but makes decisions that contradict it has a decoration, not an intention. The work will reflect the actual intention, not the stated one. + +**Trying the opposite as a stunt rather than a diagnostic.** Assumption reversal is a tool for mapping possibility, not a mandate to be contrarian. A founder who inverts every industry norm without understanding why those norms exist is not practising creative shaping -- they are practising recklessness. + +**Skipping the craft phase because it lacks glamour.** the text is blunt: "In some ways, the Craft phase is one of the least glamorous parts of the artist's job." Entrepreneurs who love ideation but resist the labour of refinement produce work that is perpetually unfinished. The seed phase has "little purpose or meaning on its own." Completing the work is what gives early inspiration its value. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Intention clarity and assumption inventory | The founder has maximum freedom to question every rule; the danger is having no rules at all, which produces drift rather than liberation | +| Validation | Temporary constraints and essence testing | Customer feedback provides the external pressure that reveals which elements are structural; the skeleton test becomes empirical rather than intuitive | +| Early Traction | Point of view crystallisation | The brand's voice must emerge from accumulated decisions; this is the stage where the founder's filter becomes visible and worth articulating | +| Growth | Breaking the sameness and pattern disruption | Established processes and successful formulas begin to calcify; deliberate disruption prevents the company from optimising itself into irrelevance | +| Scale | Assumption reversal and rule auditing | At scale, unconscious rules are most entrenched and most dangerous; systematic reversal exercises surface the assumptions that could blind the organisation to market shifts | + +The intermediate stages -- validation and early traction -- are where shaping has its highest leverage. Raw material is abundant but form is undefined. The founder who can hold intention clearly while ruthlessly distilling to essence will build products that customers describe as "obvious in retrospect." That retrospective obviousness is the hallmark of work that has been shaped to its skeleton. + +At the idea stage, the founder faces a peculiar version of the rules problem: with no established product, there are no explicit rules to break, yet the founder's mind is saturated with implicit rules inherited from the industry they came from, the products they have used, and the business models they have studied. The invisible rules inventory is most productive at this stage precisely because there is no organisational inertia resisting the findings. + +At growth and scale, the shaping challenge inverts. The company's own past successes have become the rules. the book's warning -- "every innovation risks becoming a rule" -- applies directly to the product team that treats last year's winning formula as this year's operating manual. The assumption-reversal exercise at scale is not a creative workshop; it is a strategic survival practice. + +--- + +## Output Template + +```markdown +# Creative Shaping Audit -- [Product/Project Name] + +**Date:** [Date] +**Stage:** [Idea / Validation / Early Traction / Growth / Scale] + +## Intention Statement +[One sentence: the single animating conviction behind this work -- not the business goal] + +## Rules Inventory + +| Rule/Assumption | Source (Industry / Founder / Culture) | Type (Law / Convention / Unexamined) | Opposite | Verdict | +|----------------|--------------------------------------|--------------------------------------|----------|---------| +| [Rule] | [Source] | [Type] | [What the opposite looks like] | [Keep / Question / Break] | + +## Temporary Constraints for Current Challenge +- **Constraint 1:** [Description] -- Expected effect: [What it forces] +- **Constraint 2:** [Description] -- Expected effect: [What it forces] +- **Expiry date:** [When to review and release] + +## Skeleton Test Results +- **Elements tested:** [List] +- **Structural elements (cannot remove):** [List] +- **Ornamentation (can remove):** [List] +- **Distilled essence:** [One sentence] + +## Point of View Evidence +[Decisions made that competitors would not have made -- the pattern reveals the voice] +1. [Decision] +2. [Decision] +3. [Decision] + +## Next Shaping Action +[Specific next step with timeline] +``` + +--- + +## Related Skills + +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- Flow provides the raw material that shaping refines; inspiration without craft is a seed that never germinates. +- **[Creative Completion and Renewal](../../content/skills/creative/creative-completion-and-renewal.md)** -- Shaping is the middle act; completion addresses the distinct challenge of releasing shaped work into the world. +- **[Creative Collaboration and Context](../../content/skills/creative/creative-collaboration-and-context.md)** -- Collaboration introduces additional lenses through which to shape; the prism of another person's perspective can reveal structural elements the solo creator misses. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Blue Ocean's value innovation framework provides a systematic method for essence-finding: eliminate, reduce, raise, create. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- Narrative shaping is a specific application of creative craft; the five-second moment and But-and-Therefore momentum are structural shaping techniques applied to story. +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- The structured editing methodology provides the specific techniques for the refinement phase of shaping written creative work. diff --git a/plugins/foreman/skills/decision-making-under-pressure/SKILL.md b/plugins/foreman/skills/decision-making-under-pressure/SKILL.md deleted file mode 120000 index 70f7962..0000000 --- a/plugins/foreman/skills/decision-making-under-pressure/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/decision-making-under-pressure.md \ No newline at end of file diff --git a/plugins/foreman/skills/decision-making-under-pressure/SKILL.md b/plugins/foreman/skills/decision-making-under-pressure/SKILL.md new file mode 100644 index 0000000..46d442b --- /dev/null +++ b/plugins/foreman/skills/decision-making-under-pressure/SKILL.md @@ -0,0 +1,199 @@ +--- +name: "decision-making-under-pressure" +description: "Provides practical habits for making better decisions faster -- reframing problems before solving them, knowing when to stop deliberating, balancing intuition with analysis, resisting 'just this once' compromises, and breaking overthinking cycles. Use when facing a high-stakes choice with incomplete data, sensing that deliberation has become procrastination, noticing a pattern of deferred decisions, needing to explain decision-making rationale to a team, or recognising that overthinking is degrading output quality." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - decision-making + - critical-thinking + - pressure + - intuition + - ethics + - problem-framing + - overthinking +related_skills: + - thinking-fast-and-slow + - vuca-framework + - eisenhower-matrix + - psychological-safety +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Decision-Making Under Pressure + +TIMER. Every undecided decision carries a holding cost -- and most leaders dramatically underestimate it. Projects stall waiting for approval. Teams hedge because direction is unclear. Competitors move while deliberation continues. The holding cost is invisible because it appears on no balance sheet, but it compounds daily: in lost momentum, in eroded team confidence, in the narrowing of options that occurs while a leader searches for certainty that will never arrive. Clayton Christensen observed that the most dangerous phrase in a leader's vocabulary is "just this once" -- a phrase that makes ethical and strategic erosion feel costless. Thomas Davenport's research suggests that the question is rarely whether a leader has enough information to decide, but whether they have the courage to decide with the information they have. + +The cognitive science of decision-making -- Kahneman's System 1 and System 2, the taxonomy of biases -- is covered elsewhere in this system. What follows is the applied practice: the daily habits that separate leaders who decide well under pressure from those who decide late, or not at all. + +--- + +## The Framework + +Practical decision-making under pressure operates through six habits. They are not sequential; they are concurrent disciplines that reinforce each other over time. + +### Habit 1: Frame Before You Solve + +Julia Binder and Michael Watkins's research reveals a consistent failure pattern: leaders and teams devote too little effort to examining and defining problems before attempting to solve them. Jumping to solutions feels productive. It rarely is. Problem-framing is the practice of viewing a situation through multiple lenses -- adjusting angle, aperture, and focus -- before committing to a solution path. + +Three reframing techniques for daily use: + +- **Stakeholder reframe.** How does this problem look from the customer's perspective? The investor's? The newest employee's? Each perspective reveals constraints and opportunities invisible from the leader's vantage point. +- **Temporal reframe.** What does this problem look like in six months? In three years? Decisions that feel urgent today often look different when projected forward. Equally, decisions that feel deferrable today may become irreversible if delayed. +- **Scale reframe.** If this problem were ten times larger, how would you approach it? If it were trivial, would you still be deliberating? Scale shifts expose whether the decision difficulty is inherent to the problem or manufactured by the decision-maker's anxiety. + +Peter Drucker's observation applies: the leader who takes pride in solving problems quickly may be solving the wrong problems. The leader who reframes first solves fewer problems -- but the right ones. + +### Habit 2: Apply the Importance-Frequency Matrix + +Thomas Davenport's framework for deciding when to stop deliberating uses two variables: + +| | Low Importance | High Importance | +|---|---|---| +| **High Frequency** | Create a rule or system; invest once, then automate | Develop a robust process; the recurrence justifies the effort | +| **Low Frequency** | Decide immediately; the cost of deliberation exceeds the value of optimisation | Gather perspectives, then decide within a defined time boundary | + +Most leaders over-deliberate low-importance decisions and under-invest in systems for high-frequency ones. The diagnostic question: "If I spent thirty more minutes on this decision, would the outcome materially improve?" If the answer is no, decide now. + +### Habit 3: Balance Gut and Data + +Jennifer Jordan, Michael Wade, and Elizabeth Teracino's research identifies the intuition-analysis tension as one of seven tensions every leader must navigate. Overvaluing intuition produces decisions based on outdated heuristics and unexamined biases. Overvaluing data produces analysis paralysis and the illusion that sufficient information will eliminate uncertainty. + +The practical balance: + +- **Use intuition for:** pattern recognition in familiar domains, rapid triage of low-stakes decisions, identifying which data to seek. +- **Use analysis for:** high-stakes decisions where biases are likely operating, situations outside your domain expertise, decisions that will be difficult to reverse. +- **Use both for:** any decision where your gut says one thing and the data says another. The disagreement itself is the most valuable signal -- it means either your experience is detecting something the data misses, or your biases are overriding evidence. Determining which requires deliberate examination, not default to either mode. + +### Habit 4: Widen Perspective Deliberately + +Helen Lee Bouygues's research on critical thinking identifies three practices that guard against poor decisions: + +1. **Question assumptions.** Especially when stakes are high. "Why is this the best way forward?" and "What does the evidence actually say about our market expectations?" force the reasoning process to surface premises that may be unexamined. +2. **Verify logical coherence.** Are the conclusions supported by the data, or are they supported by the narrative someone has constructed around the data? These are different things. +3. **Seek perspectives outside your circle.** The inner circle shares your assumptions. Perspectives from different departments, different experience levels, and different professional backgrounds reveal blind spots that homogeneous consultation cannot. + +Sabina Nawaz's six gut-check questions provide a structured version of this practice for new ideas: What stands out? What's missing? What would critics say? What would failure look like? What would customer-facing employees say? What shortcomings would please competitors? + +### Habit 5: Resist "Just This Once" + +Christensen's observation deserves its own habit because the mechanism is subtle and the consequences are severe. The marginal cost of doing something wrong "just this once" always appears low. The full cost -- which includes the precedent set, the standard lowered, the integrity compromised -- is invisible at the moment of decision. Leaders who maintain their principles 100% of the time find it structurally easier than those who maintain them 98% of the time, because the 2% creates a negotiation with themselves that the 100% does not. + +The practical application is precommitment: know where your lines are before you face pressure to cross them. Ethical boundaries decided in advance require no deliberation under pressure. Ethical boundaries decided in the moment are subject to every cognitive bias and rationalisation the human mind can produce. + +### Habit 6: Break Overthinking Cycles + +Alice Boyes's research identifies a pattern: intelligent leaders are particularly prone to overthinking because their cognitive capacity allows them to generate more scenarios, more objections, and more complications than the problem warrants. The signals of overthinking: obsessing over the same options, generating diminishing returns on additional analysis, inability to commit despite adequate information. + +Three circuit-breakers: + +- **Notice the loop.** The first step is recognising that you are cycling through the same arguments. Label it: "I am overthinking this." +- **Change cognitive mode.** Engage in an absorbing, unrelated activity -- a puzzle, a walk, a conversation about something else entirely. This is not procrastination; it is allowing the subconscious processing that focused analysis suppresses. +- **Set a decision deadline.** "I will decide by Thursday at noon" creates a forcing function. Share the deadline with someone else to make it binding. Open-ended deliberation is a failure mode, not a virtue. + +--- + +## Prompts + +**Prompt 1 -- Problem Reframing:** +> I am facing this decision: [describe the decision and context]. Before I solve it, help me reframe it. Apply three lenses: stakeholder reframe (how does this look from the perspectives of [list 3 stakeholders]), temporal reframe (what does this look like in 6 months vs. 3 years), and scale reframe (if this were 10x larger or trivially small). Then tell me: am I solving the right problem? + +**Prompt 2 -- Decision Speed Diagnostic:** +> Here are five decisions currently pending on my desk: [list each with a brief description]. For each, assess importance (high/low) and frequency (high/low) using the Davenport matrix. Then recommend: which should I decide immediately, which need a system, which deserve more deliberation, and which am I over-deliberating? + +**Prompt 3 -- Intuition vs. Analysis Arbitration:** +> My gut tells me [describe intuitive conclusion] about [decision]. The data suggests [describe analytical conclusion]. Help me determine whether my intuition is detecting a pattern the data misses or whether my biases are overriding evidence. Ask me the questions that would distinguish between these two explanations. + +**Prompt 4 -- Ethical Line Precommitment:** +> I am entering a high-pressure period: [describe context -- fundraising, acquisition, restructuring]. Before the pressure arrives, help me define my ethical precommitments. What are the "just this once" temptations most common in this type of situation? For each, help me articulate the line I will not cross and the reasoning behind it, so I don't have to reason under pressure. + +--- + +## Use Cases + +**Early-Traction Startup: Founder Paralysed by Pricing Decision** +A founder has spent three weeks analysing pricing models for a product launch. Every model has trade-offs. No model is clearly superior. The importance-frequency diagnostic reveals this is a high-importance but low-frequency decision -- it deserves deliberation but within a bounded timeframe. The temporal reframe reveals that the pricing decision is reversible within 90 days. The founder sets a 48-hour decision deadline, shares it with their co-founder for accountability, and selects the model that best aligns with their positioning thesis. Three months later, they adjust pricing based on real customer data -- data they would not have if they had spent another three weeks deliberating. + +**Growth-Stage Company: VP Avoiding a Restructuring Decision** +A VP knows that one of three engineering teams needs to be reorganised. The decision will disappoint people, so the VP gathers "just a little more data" -- for the fourth consecutive month. The holding cost diagnostic reveals: two projects are stalled because team boundaries are unclear, three engineers have started interviewing at other companies due to uncertainty, and cross-team collaboration has degraded. The VP applies the six gut-check questions to each restructuring option, sets a one-week decision deadline, and communicates the decision with transparent reasoning. Morale dips briefly; the stalled projects resume within two weeks. + +**Scale-Stage CEO: Resisting "Just This Once" in a Partnership Deal** +A CEO is negotiating a distribution partnership with a larger company. The partner's legal team inserts a clause that requires sharing customer data in ways that conflict with the company's privacy commitments. The partner's head of BD says, "We can work around this informally -- just sign the contract as-is and we'll handle the data question later." The CEO, having precommitted to data privacy as a non-negotiable line, declines without deliberation. The partner respects the boundary and revises the clause. Had the CEO not precommitted, the "just this once" logic -- "it's our biggest deal, we'll fix it later" -- would have been persuasive in the moment. + +--- + +## Anti-Patterns + +1. **Decisiveness Theatre.** Making rapid decisions ostentatiously to signal leadership confidence, without reframing or perspective-gathering. Speed without discernment is recklessness branded as decisiveness. + +2. **Data as Procrastination.** Requesting additional analysis not because it would change the decision but because it defers the discomfort of committing. The tell: the decision-maker cannot articulate what specific data point would change their mind. If no data point would change the outcome, the decision is ready to be made. + +3. **Consensus as Decision-Making.** Treating universal agreement as a prerequisite for action. Consensus-seeking is a legitimate collaboration tool. Consensus-requiring is a mechanism for distributing blame and avoiding accountability. Clarify before any meeting whether the process is consultative (I will hear all views and then decide) or democratic (the group will vote). + +4. **Post-Hoc Rationalisation Disguised as Intuition.** "My gut told me" is sometimes a legitimate report of pattern recognition and sometimes a retroactive justification for a decision made on emotion. The difference: genuine intuition can be examined and its reasoning reconstructed; post-hoc rationalisation collapses under questioning. + +5. **The Reversibility Blind Spot.** Treating all decisions as equally permanent. Many business decisions are highly reversible -- pricing, feature prioritisation, team assignments -- and deserve fast, low-deliberation treatment. Irreversible decisions -- equity grants, market exits, key hires -- deserve the full reframing and perspective-gathering protocol. Applying the irreversible protocol to reversible decisions is a common source of organisational paralysis. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Speed over precision | Nearly every decision is reversible because the company is small and fast-moving. The primary risk is not making a wrong decision but making no decision. The importance-frequency matrix should bias toward "decide immediately" for most choices. | +| Growth | Process installation | Decision volume exceeds one person's capacity. The leader's task shifts from making every decision to building decision-making systems (for high-frequency issues) and teaching the reframing and deliberation habits to the leadership team. | +| Scale | Decision delegation and ethics | At scale, the leader makes fewer decisions directly and more decisions about how decisions should be made. Ethical precommitment becomes organisational, not personal -- codified in policies, not just personal convictions. The "just this once" risk multiplies as more people face pressure to cut corners. | + +--- + +## Output Template + +```markdown +# Decision Analysis: [Decision Description] + +## Problem Frame +- Initial framing: [how the problem was first presented] +- Stakeholder reframe: [alternative perspective] +- Temporal reframe: [how it looks at different time horizons] +- Scale reframe: [what changes at different magnitudes] +- Revised framing: [the problem as it should actually be solved] + +## Davenport Classification +- Importance: [High/Low] +- Frequency: [High/Low] +- Recommended approach: [Decide now / Build system / Bounded deliberation / Seek perspectives] + +## Intuition-Analysis Check +- Gut says: [intuitive conclusion] +- Data says: [analytical conclusion] +- Reconciliation: [which to trust and why] + +## Decision +- Choice: [what was decided] +- Reasoning: [transparent logic] +- Reversibility: [how and when this can be revisited] +- Ethical check: [any "just this once" pressures resisted] + +## Communication Plan +- Who needs to know: [stakeholders] +- What they need to understand: [the reasoning, not just the outcome] +- When: [timing] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process theory provides the cognitive science behind why intuition and analysis sometimes conflict; this skill provides the daily practices for managing that conflict. +- **[VUCA Framework](../../content/skills/frameworks/vuca-framework.md)** -- Classifies the type of uncertainty in which pressured decisions occur, which informs which decision habit to prioritise. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- The urgent-versus-important distinction complements the importance-frequency matrix for triaging which decisions demand immediate attention versus scheduled deliberation. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- Provides the structured criteria-weighting and margin-of-safety methods that complement the reframing and speed habits described here. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- The Stoic practice of pausing before assenting to impressions provides the philosophical foundation for Habit 6's overthinking circuit-breakers. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Teams that lack psychological safety suppress dissenting perspectives, directly degrading the leader's ability to gather the diverse input good decisions require. diff --git a/plugins/foreman/skills/decision-traps-and-roles/SKILL.md b/plugins/foreman/skills/decision-traps-and-roles/SKILL.md deleted file mode 120000 index 2dfd9b9..0000000 --- a/plugins/foreman/skills/decision-traps-and-roles/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/decisions/decision-traps-and-roles.md \ No newline at end of file diff --git a/plugins/foreman/skills/decision-traps-and-roles/SKILL.md b/plugins/foreman/skills/decision-traps-and-roles/SKILL.md new file mode 100644 index 0000000..3bb67a2 --- /dev/null +++ b/plugins/foreman/skills/decision-traps-and-roles/SKILL.md @@ -0,0 +1,222 @@ +--- +name: "decision-traps-and-roles" +description: "Catalogues the invisible psychological traps that sabotage decisions -- anchoring, sunk cost, confirming evidence, framing, and status quo bias -- and pairs them with the RAPID model for clarifying who recommends, agrees, performs, inputs, and decides, plus a seven-step checklist for faster group decisions. Use when a team suspects cognitive bias is distorting a choice, when decision authority is ambiguous, when past investments are influencing current strategy, when negotiations are anchored by the other party's opening, or when organisational decisions stall because no one knows who owns the call." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-bias + - anchoring + - sunk-cost + - confirmation-bias + - framing + - status-quo + - decision-roles + - rapid-model + - decision-checklist + - group-decisions +related_skills: + - generating-solutions + - evaluating-options + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Decision Traps and Roles + +TRAP. Every decision is mined with invisible traps -- anchoring, sunk cost, confirmation bias -- and the most dangerous ones are the ones you cannot see operating on you. Researchers have documented these cognitive distortions for half a century, yet a room of experienced executives will fall into them with the same regularity as a room of undergraduates. The traps are hardwired. They do not yield to intelligence, seniority, or good intentions. They yield only to structure: specific counter-routines that force the mind to check itself before it commits. This skill catalogues the traps, provides the counter-routines, and then addresses the organisational question that amplifies every individual bias -- who, exactly, owns the decision? + +--- + +## The Toolkit + +### Tool 1: The Five Hidden Traps + +Each trap operates beneath conscious awareness. The counter-measures are not intuitive; they must be deliberately applied. + +**The Anchoring Trap.** The mind gives disproportionate weight to the first information it receives. An opening offer in a negotiation, a prior year's revenue figure, a colleague's offhand estimate -- each becomes a gravitational centre around which all subsequent judgments orbit. In one classic experiment, asking whether Turkey's population exceeds 35 million versus 100 million produced wildly different estimates of the actual figure, despite the anchor being arbitrary. + +Counter-measures: +- Approach the problem from multiple starting points before consulting others +- Withhold your own preliminary estimates when soliciting input -- otherwise your preconceptions return to you disguised as independent confirmation +- In negotiations, define your position fully before the other party's opening gambit can set the frame + +**The Status-Quo Trap.** Defaulting to the current state feels safe because action invites responsibility, and responsibility invites criticism. In one experiment, people randomly given a mug refused to trade it for an equally valued chocolate bar -- the status quo exerted its pull within minutes of being established. In business, sins of commission are punished far more severely than sins of omission, creating a structural incentive to leave things as they are even when change is overdue. + +Counter-measures: +- Ask whether you would choose the current state if it were not already the default +- Never treat the status quo as your only alternative -- generate at least one concrete option against which to compare it +- Evaluate alternatives in terms of future desirability, not present comfort + +**The Sunk-Cost Trap.** Past investments -- of money, time, reputation -- create psychological pressure to justify those investments by continuing down the same path. A bank that originated a bad loan is far more likely to advance additional funds than a fresh banker who inherits the account, because the originator is unconsciously protecting an earlier, flawed decision. + +Counter-measures: +- Seek counsel from people uninvolved with the original decision +- Reassign ownership when the original decision-maker cannot separate past commitment from present merit +- Cultivate a culture that evaluates decision quality at the time of the decision, not solely by subsequent outcomes + +**The Confirming-Evidence Trap.** The mind seeks information that supports its existing inclination and discounts information that contradicts it. Two groups -- one favouring and one opposing capital punishment -- each read balanced research evidence and both emerged more entrenched in their original positions. The subconscious decides what it wants before the conscious mind assembles the justification. + +Counter-measures: +- Appoint a devil's advocate, or better, construct the strongest counter-argument yourself +- Ask: "Am I gathering information to make a smart choice, or to confirm the choice I have already made?" +- Avoid leading questions when soliciting advice; if an adviser consistently supports your view, find a different adviser + +**The Framing Trap.** How the question is posed determines the answer. New Jersey and Pennsylvania introduced identical auto-insurance options but framed the default differently; the framing difference produced a $200 million gap in outcomes. People are risk-averse when a problem is framed as a potential gain and risk-seeking when framed as a potential loss -- even when the underlying options are mathematically identical. + +Counter-measures: +- Reframe every problem in at least two ways: as a gain and as a loss, with different reference points +- Challenge others' framings explicitly -- the person who sets the frame controls the decision +- Revisit framing at multiple stages of the decision process, not just at the start + +### Tool 2: The RAPID Model for Decision Roles + +Ambiguity about decision authority is the organisational accelerant that turns individual bias into institutional paralysis. The RAPID framework, developed by Bain & Company, assigns five discrete roles to every significant decision: + +| Role | Letter | Function | +|------|--------|----------| +| **Recommend** | R | Proposes a course of action, marshals data, engages stakeholders, builds the case | +| **Agree** | A | Must formally agree before the recommendation can advance; has explicit veto power | +| **Perform** | P | Executes the decision once made | +| **Input** | I | Provides information and analysis that shapes the recommendation; consulted but not binding | +| **Decide** | D | Brings the decision to closure and commits the organisation to act | + +Three structural pitfalls to avoid: + +1. **Multiple D's.** If two people believe they own the decision, the result is a tug-of-war. One person holds the D. Always. +2. **Proliferation of A's.** Too many veto-holders paralyse recommenders. If many people must agree, decision authority has not been pushed far enough down the organisation. +3. **Excessive I's.** When everyone provides input, at least some contributions are ceremonial. Each I-role should demonstrably improve the recommendation's quality. + +### Tool 3: The Seven-Step Decision Checklist + +A lightweight protocol, drawn from behavioural economics research, that consistently improves group decision quality. Managers who follow it save an average of ten hours of discussion, decide ten days faster, and improve outcomes by twenty percent. + +1. Write down five pre-existing goals or priorities that the decision will affect +2. Write down at least three -- ideally four or more -- realistic alternatives +3. Write down the most important information you are missing +4. Write down the expected impact one year from now as a brief narrative +5. Involve two to six stakeholders (effectiveness declines by ten percent per person beyond seven) +6. Record what was decided, why, and the team's confidence level +7. Schedule a follow-up review in one to two months + +--- + +## Prompts + +**Prompt 1 -- Trap Diagnosis:** +> "I am about to make this decision: [describe decision]. Before I proceed, audit my reasoning for the five hidden traps. Where might I be anchored by initial information? Am I defaulting to the status quo because it is comfortable rather than optimal? Are sunk costs influencing my judgment? Am I seeking confirming evidence? How is the problem framed, and how would the decision change under an alternative frame? Provide a specific counter-measure for each trap you identify." + +**Prompt 2 -- RAPID Role Mapping:** +> "My [stage] company needs to make the following decision: [describe decision]. Map the RAPID roles for this decision. Who should Recommend? Who must Agree (and why do they have veto power)? Who Performs? Whose Input is genuinely necessary versus ceremonial? Who Decides? Flag any structural pitfalls -- multiple D's, excessive A's, or too many I's -- and suggest corrections." + +**Prompt 3 -- Checklist Walkthrough:** +> "I am deciding [decision] for my [sector] company. Walk me through the seven-step decision checklist. Help me articulate five affected goals, generate at least four realistic alternatives, identify missing information, write a one-year-out impact narrative, determine the right number of stakeholders, and design a follow-up review protocol." + +**Prompt 4 -- Negotiation Anchor Defence:** +> "I am entering a negotiation for [describe -- fundraising round, partnership deal, vendor contract]. The other party is likely to set an anchor with their opening position. Help me prepare: define my own position across all negotiable dimensions before the meeting, identify the anchors I am most susceptible to, and construct alternative frames that prevent their opening gambit from constraining my thinking." + +--- + +## Use Cases + +**Pre-Seed Founder Anchored by a VC's Valuation** + +A first-time founder with a B2B SaaS prototype receives a verbal indication from an angel investor: "companies like yours are worth about $2M pre-money." The figure is arbitrary -- the investor has seen two comparable deals in the past quarter, both at distressed valuations. Yet the founder begins using $2M as the reference point for every subsequent conversation, adjusting modestly upward but never escaping the anchor's orbit. A disciplined approach would have the founder construct an independent valuation range from multiple data sources (comparable transactions, revenue multiples for the vertical, the specific value of committed pilot customers) before engaging any investor. The anchor defence is preparation: define your own frame before someone else defines it for you. + +**Growth-Stage Company Throwing Good Money After a Failed Product Line** + +A consumer hardware startup invested $3M and eighteen months developing a smart home device that has sold 2,000 units in six months -- roughly ten percent of the break-even target. The VP of product argues for an additional $1.5M to "fix the go-to-market strategy," citing the original investment as justification. The sunk-cost trap is operating at full force: the $3M already spent is irrecoverable regardless of the next decision. A fresh evaluator -- someone without emotional investment in the original bet -- would assess the $1.5M purely on its expected return. Reassigning the product review to the head of a different business unit surfaces what the original team could not see: the core product thesis (that consumers would pay $400 for a device that replicates $30 of functionality on their phone) was never validated. + +**Scaling Company with Unclear Decision Ownership** + +A 200-person e-commerce company finds that pricing decisions take six weeks to implement because marketing, finance, product, and the CEO each believe they own the call. A RAPID mapping reveals that marketing should Recommend (they hold the customer data), finance should provide Input (margin constraints), product should Agree (pricing affects positioning), and the CEO should Decide -- but only for pricing changes above a defined threshold. Below that threshold, marketing holds the D. Pricing decisions now take five days. + +--- + +## Anti-Patterns + +**Treating bias awareness as bias immunity.** Knowing about anchoring does not prevent anchoring. The traps are not eliminated by education; they are mitigated by structure. A team that has read this skill and proceeds to brainstorm without any counter-routines will fall into every trap catalogued here. + +**Assigning RAPID roles for trivial decisions.** A five-person startup does not need a formal role-mapping exercise for choosing a project management tool. RAPID is designed for decisions where ambiguity about authority creates measurable delay or conflict. Over-applying it bureaucratises what should be a fast-moving organisation. + +**Using the checklist as a post-hoc rationalisation tool.** The seven-step checklist works only if applied before the decision is made. Filling it out after the fact -- to justify a choice already taken -- converts a debiasing tool into a confirming-evidence machine. + +**Assuming one person's counter-arguments constitute adequate debiasing.** A single devil's advocate can be dismissed. Structural debiasing requires multiple independent perspectives, ideally from people with no stake in the outcome and no history with the decision. + +**Conflating the D with seniority.** The person who Decides should be the person closest to the information and most accountable for the outcome -- not necessarily the most senior person in the room. Pushing the D upward by default is a status-quo trap applied to organisational design. + +--- + +## By Stage + +| Stage | Primary Trap Risk | RAPID Focus | +|-------|-------------------|-------------| +| Idea | Confirming-evidence trap -- the founder seeks validation for a pre-existing belief about the market. Framing trap -- the problem definition constrains the solution space before alternatives are explored. | Roles are informal; the founder often holds all five letters. The discipline at this stage is recognising when to solicit genuine I-roles from people who will challenge, not confirm. | +| Validation | Sunk-cost trap -- early investment in an MVP creates pressure to continue rather than pivot. Anchoring on early customer feedback (first ten users set expectations for the next thousand). | The founding team must explicitly assign the D for pivot-or-persist decisions. If no one owns it, the status quo wins by default. | +| Early Traction | Status-quo trap -- processes that worked for ten customers are preserved unchanged for one hundred. Anchoring on founding-era metrics as benchmarks. | RAPID becomes operational. Decisions about hiring, pricing, and feature prioritisation need clear role assignments as the team grows beyond the founders. | +| Growth | All five traps operate simultaneously at scale. Confirming evidence flows freely in organisations that have been successful -- past success anchors future strategy. | The checklist becomes a team discipline, not an individual exercise. Decision follow-ups at step seven must be enforced by calendar, not memory. | +| Scale | The framing trap is most dangerous at scale because the frame is set by layers of middle management before information reaches the decision-maker. Sunk costs are measured in years and departments, not weeks and features. | RAPID must be documented and published for recurring decisions. Ad hoc role assignment fails when hundreds of people are involved. The D must be explicit, visible, and non-negotiable. | + +--- + +## Output Template + +```markdown +# Decision Trap and Role Audit + +**Decision:** [one-sentence description] +**Date:** [date] +**Audited by:** [name(s)] + +## Trap Scan + +| Trap | Present? | Evidence | Counter-Measure Applied | +|------|----------|----------|------------------------| +| Anchoring | [yes/no] | [what anchor is influencing the decision?] | [alternative starting points used] | +| Status Quo | [yes/no] | [is inaction being preferred for comfort?] | [status quo compared against explicit alternatives] | +| Sunk Cost | [yes/no] | [what past investment is influencing the choice?] | [decision evaluated on forward-looking merit only] | +| Confirming Evidence | [yes/no] | [is information being gathered selectively?] | [devil's advocate assigned; counter-arguments constructed] | +| Framing | [yes/no] | [how is the question framed, and what does the alternative frame reveal?] | [problem reframed as gain/loss with different reference points] | + +## RAPID Role Assignment + +| Role | Person | Rationale | +|------|--------|-----------| +| Recommend | [name] | [why this person] | +| Agree | [name] | [why veto power is warranted] | +| Perform | [name(s)] | [execution responsibility] | +| Input | [name(s)] | [what information they provide] | +| Decide | [name] | [why this person owns the call] | + +## Seven-Step Checklist +1. **Goals affected:** [list five] +2. **Alternatives:** [list three or more] +3. **Missing information:** [what we do not know] +4. **One-year impact narrative:** [two sentences] +5. **Stakeholders involved:** [names, max six] +6. **Decision record:** [what, why, confidence level] +7. **Follow-up date:** [date, one to two months out] +``` + +--- + +## Related Skills + +- **[Generating Solutions](../../content/skills/decisions/generating-solutions.md)** -- Once traps are identified and roles assigned, the next step is generating alternatives; this sibling skill covers brainstorming failures, BrainSwarming, and could-vs-should reframing. +- **[Evaluating Options](../../content/skills/decisions/evaluating-options.md)** -- Provides the evaluation methods (joint evaluation, Even Swaps, risk ranking, intuition calibration) for choosing among the alternatives generated. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- Root cause analysis and the 3-Lens Principle address the problem-definition phase that precedes this skill's focus on decision traps. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's cognitive model explains the System 1/System 2 mechanics that generate the traps catalogued here. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Daily habits for maintaining decision quality when time and emotional pressure compress the window for deliberation. +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- The four biological defaults (ego, emotion, inertia, social) provide the deeper diagnostic framework for understanding why the cognitive traps catalogued here persist despite awareness. diff --git a/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md b/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md deleted file mode 120000 index 35723a5..0000000 --- a/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/defining-and-exploring-problems.md \ No newline at end of file diff --git a/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md b/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md new file mode 100644 index 0000000..5731e20 --- /dev/null +++ b/plugins/foreman/skills/defining-and-exploring-problems/SKILL.md @@ -0,0 +1,205 @@ +--- +name: "defining-and-exploring-problems" +description: "Teaches the discipline of correct problem definition and structured solution exploration before any evaluation begins. Covers the problem-solution firewall, root cause identification, the premortem, second-order thinking ('and then what?'), binary thinking traps, integrative Both-And options, and opportunity cost analysis through the 3-Lens Principle. Use when a team is jumping to solutions before understanding the problem, when a founder suspects they are treating symptoms rather than causes, when only two options seem to exist, when opportunity costs are unclear, or when first-conclusion bias is narrowing the solution space." +version: "1.0.0" +category: "thinking" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - problem-definition + - root-cause-analysis + - second-order-thinking + - binary-thinking + - opportunity-cost + - premortem + - integrative-thinking + - decision-making + - solution-space +related_skills: + - thinking-fast-and-slow + - decision-making-under-pressure + - evaluating-and-deciding + - wanting-what-matters + - stoic-problem-solving + - scenario-planning + - systems-thinking +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Defining and Exploring Problems + +WRONG PROBLEM. Most failed decisions do not come from wrong answers -- they come from wrong questions. A room of intelligent people converges on a plausible-sounding problem statement within minutes, pivots immediately to solutions, and spends weeks executing against a target that was never the right one. The Clear Thinking framework calls this the social default: the collective instinct to accept the first definition everyone agrees on and move forward, because solving problems feels productive while defining them feels like stalling. The result is organisations that are perpetually busy and perpetually unimproved -- extinguishing flames that reignite because no one addressed the fire. Define the problem correctly and the solution often becomes obvious. Define it incorrectly and no amount of analytical sophistication will rescue the outcome. + +--- + +## The Framework + +The process divides into two distinct phases -- defining the real problem, then exploring the full solution space -- and the single most valuable discipline is keeping them apart. + +### Phase 1: Define the Problem + +**The Definition Principle.** Take responsibility for defining the problem yourself. Do not let someone else's framing become your framing by default. If you cannot explain the problem to a twelve-year-old without resorting to jargon, you do not yet understand it well enough to make a decision about it. + +**The Root Cause Principle.** Distinguish the disease from the symptoms. The diagnostic question is deceptively simple: "What would have to be true for this problem not to exist in the first place?" + +The text illustrates this with Downtown Dog Rescue in Los Angeles, where founder Lori Weise discovered that 30 percent of shelter dogs were owner surrenders -- families who loved their pets but could not afford to feed them. The obvious problem ("how do we get more people to adopt?") was the wrong problem. The root cause was economic hardship among existing owners. Solving for that reduced shelter intake by 75 percent at lower cost than housing the animals. + +Three operational disciplines protect this phase: + +1. **The Problem-Solution Firewall.** Hold two separate meetings: one to define the problem, one to solve it. When both happen in the same session, type-A teams spend ninety seconds on definition and fifty-eight minutes on solutions. The question that unlocks the definition meeting: "What do you know about this problem that other people in the room don't know?" It forces participants to stop signalling with shared information and start revealing private information. + +2. **The Test of Time.** Ask whether a proposed solution will fix the problem permanently or merely defer it. If the problem will return, you are treating a symptom. Short-term fixes signal to others that action is being taken; they do not signal that progress is being made. Energy channelled toward short-term solutions depletes energy available for long-term ones. + +3. **Write It Down.** Articulate the problem statement in writing and revisit it the next day. Jargon in the description is a reliable indicator that understanding is shallow. If the statement survives overnight scrutiny and reads clearly in plain language, the definition is likely sound. + +### Phase 2: Explore Possible Solutions + +Once the problem is defined, the temptation is to seize the first plausible solution. The framework identifies three traps at this stage, each with a corresponding countermeasure. + +**Trap 1: Ignoring Brutal Reality (The Stockdale Paradox).** Admiral James Stockdale, the highest-ranking US prisoner of war in Vietnam, observed that the optimists -- those who kept predicting release by Christmas, then Easter, then Thanksgiving -- were the ones who died. "You must never confuse faith that you will prevail in the end with the discipline to confront the most brutal facts of your current reality." Entrepreneurs who build solutions on wishful assumptions about market timing, customer behaviour, or competitive response are running the same risk. The Bad Outcome Principle demands imagining not just the ideal future but the ways things could go wrong and how you would overcome each. + +**Trap 2: Binary Thinking.** When only two options present themselves -- launch or don't, hire or don't, pivot or don't -- it is almost always a sign that the problem's dimensions have been prematurely reduced. The framework calls this "stopping thinking" disguised as clarity. + +The antidotes: + +| Safeguard | Method | +|-----------|--------| +| **The 3+ Principle** | Force at least three credible options before evaluating any. If only two exist, develop a third. Even if the third is never chosen, the work of generating it deepens understanding. | +| **Remove an Option** | Imagine each existing option is off the table. "What would I do if staying were not possible?" or "What would I do if leaving were not possible?" The constraint forces creative reframing. | +| **Both-And Thinking** | Rather than choosing between X and Y, ask whether a solution exists that combines the best elements of both. Roger Martin calls this integrative thinking. Isadore Sharp built the Four Seasons by combining the intimacy of a small hotel with the amenities of a large one -- a Both-And solution that the industry's binary framing had made invisible. | + +**Trap 3: Invisible Opportunity Costs.** Every option chosen is an option forgone. Charlie Munger's observation -- "Intelligent people make decisions based on opportunity costs; it's your alternatives that matter" -- is simple to state and routinely ignored in practice. + +The **3-Lens Principle** structures this analysis: + +- **Lens 1: Compared with what?** The direct comparison most people default to. +- **Lens 2: And then what?** The second-order consequences -- what happens after what happens next. This is where second-order thinking separates competent decision-makers from exceptional ones. +- **Lens 3: At the expense of what?** The hidden costs in time, energy, relationships, and foregone alternatives that never appear on a spreadsheet. + +Andrew Carnegie demonstrated all three lenses when, as a young railroad employee, he ordered burning of train cars blocking the entire system rather than spending days salvaging cargo. The visible cost (destroyed cargo) was dwarfed by the invisible cost (days of system-wide shutdown). His boss made the approach standard procedure. + +Most entrepreneurs default to Lens 1 because it deals in direct, visible costs -- the numbers that appear on a spreadsheet. Lens 2 and Lens 3 require imagination: the ability to trace consequences forward in time and to see what is absent rather than what is present. Charlie Munger's observation bears repeating: "Intelligent people make decisions based on opportunity costs; it's your alternatives that matter." The quality of the decision depends on the quality of the alternatives considered, and alternatives cannot be considered if they remain invisible. + +The premortem -- Stoic in origin (Seneca's premeditatio malorum), psychological in modern formulation -- complements the three lenses by forcing explicit attention to downside scenarios. The text cites venture capitalist Josh Wolfe: "Failure comes from a failure to imagine failure." The premortem is not pessimism. It is preparation. The hardest setbacks to recover from are the ones that were never anticipated, because they arrive when no contingency exists and emotion fills the vacuum that planning should have occupied. + +--- + +## Prompts + +**Prompt 1 -- Root Cause Diagnosis:** +> "I am dealing with the following problem: [describe situation]. Apply the Root Cause Principle. Ask 'What would have to be true for this problem not to exist in the first place?' Work backward from symptoms to underlying causes. Identify at least three possible root causes, rank them by likelihood, and suggest how to test which is the real one." + +**Prompt 2 -- Binary Thinking Breaker:** +> "I am choosing between [Option A] and [Option B] for my [stage] startup in [sector]. Apply the 3+ Principle, the Remove-an-Option safeguard, and Both-And integrative thinking to generate at least three additional options I have not considered. For each new option, explain what it reveals about the problem that binary framing conceals." + +**Prompt 3 -- Second-Order Consequence Map:** +> "I am considering [decision] for my company. Apply the 3-Lens Principle: (1) Compared with what alternatives? (2) And then what -- trace second-order and third-order consequences for each option over 6, 12, and 36 months. (3) At the expense of what -- identify hidden opportunity costs in time, capital, team focus, and optionality. Present findings in a structured table." + +**Prompt 4 -- Problem-Solution Firewall:** +> "My team has converged on this problem definition: [problem statement]. Before we move to solutions, stress-test this definition. Is it addressing a root cause or a symptom? Does it use jargon that masks shallow understanding? Would it pass the Test of Time -- would a solution to this problem fix things permanently or merely defer them? Rewrite the problem statement if the original is flawed." + +--- + +## Use Cases + +**SaaS Founder Treating Churn Symptoms** + +A Series A SaaS company in the HR-tech space sees monthly churn rising from 3 percent to 5 percent. The leadership team convenes and within minutes converges on "we need better onboarding." Resources shift to redesigning the first-week experience. Three months later, churn is unchanged. The problem was never onboarding -- it was that the product lacked a critical integration with the payroll system that mid-market customers (the fastest-growing segment) required. The team had treated the most visible symptom (users leaving after month two, which "looked like" an onboarding problem) rather than applying the root cause question: "What would have to be true for these customers not to leave?" Writing out the problem statement would have surfaced the jargon problem immediately -- "onboarding friction" is a label, not a diagnosis. + +**Pre-Seed Founder Stuck in Binary Framing** + +A solo founder with a working prototype for a supply-chain visibility tool faces what feels like a binary choice: accept a $150K angel investment at unfavourable terms or bootstrap with consulting revenue. The 3+ Principle generates three additional options: a revenue-based financing arrangement, a strategic pilot with a logistics company that would fund development in exchange for exclusivity, and a Both-And approach -- accepting the angel but negotiating a smaller cheque alongside a paid pilot. The third option, invisible under binary framing, provides capital, validates the product, and creates a reference customer simultaneously. + +**Growth-Stage E-Commerce Company Ignoring Opportunity Costs** + +A D2C brand generating $12M in annual revenue is evaluating whether to build an in-house fulfilment centre. The team focuses almost exclusively on Lens 1 (build vs. outsource cost comparison). Applying Lens 2 ("And then what?") reveals that in-house fulfilment requires hiring a warehouse operations team, which diverts leadership attention from product development during a critical expansion window. Lens 3 ("At the expense of what?") surfaces the real cost: the two planned product launches that would be delayed by six months because the founder's bandwidth is consumed by logistics. The Lens 3 cost exceeds the Lens 1 savings by a factor of four. + +**Validation-Stage EdTech Founder Solving the Wrong Problem** + +A founder building an AI tutoring platform observes that user engagement drops sharply after the first session. The team diagnoses the problem as "weak onboarding UX" and spends six weeks redesigning the first-session flow. Engagement does not improve. Applying the root cause question -- "What would have to be true for this problem not to exist?" -- reveals that the issue is not onboarding but content: the platform's practice questions are calibrated for grade-level students, but the actual users are adult learners preparing for professional certifications. The problem was never "how do we make the first session stickier?" but "are we serving the users who are actually showing up?" Writing the problem statement in plain language would have exposed the mismatch immediately: "Users leave after one session" describes a symptom. "Our content does not match the needs of the users who find us" describes a cause. The six weeks spent on onboarding redesign cannot be recovered. + +--- + +## Anti-Patterns + +**Confusing speed with competence.** Entrepreneurs wear rapid decision-making as a badge of honour. There is a difference between moving quickly on reversible decisions (which is wise) and collapsing the problem-definition phase because it feels unproductive (which is reckless). The social default rewards the appearance of decisiveness. The market rewards the reality of solving the right problem. + +**Anchoring on the first credible problem statement.** The first person in the room to articulate a plausible diagnosis often sets the frame for everyone else. Once a problem is named, the team shifts to solution mode and rarely revisits whether the name was accurate. Treating the first lens into an issue as the definitive lens is the single most common source of wasted organisational effort. + +**Applying the framework to trivial decisions.** Not every decision warrants root cause analysis and three-lens evaluation. Using heavyweight problem-definition for reversible, low-consequence choices is its own form of poor judgment. Reserve this discipline for decisions where the cost of solving the wrong problem is high. + +**Mistaking Both-And thinking for lack of conviction.** Integrative solutions can look like indecision to team members accustomed to binary framing. A founder who says "we are doing both" needs to articulate why the combination is strategically coherent, not merely a failure to choose. + +**Falling in love with the root cause analysis process.** Definition is not an end in itself. The purpose of separating definition from solution is to improve the quality of the solution phase, not to defer it indefinitely. If you have been defining the problem for weeks and cannot articulate it in two sentences of plain language, the process has become a refuge from action. The framework is blunt about this: "There is no purpose to knowing what you should do and not doing it." + +**Ignoring opportunity costs because they are invisible.** Most people focus exclusively on direct costs -- the money, the time, the effort that a decision requires. Hidden costs -- the forgone alternatives, the deferred projects, the relationships not maintained -- never appear on a balance sheet and therefore never enter the analysis. The 3-Lens Principle exists precisely to make these invisible costs visible, but it requires discipline to apply consistently when the visible costs are already demanding full attention. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder defines the problem they are solving for customers -- the root cause behind the pain they intend to address. | The most common error is building a solution to a problem no one actually has. Root cause analysis is applied to customer pain, not internal operations. | +| Validation | Testing whether the defined problem matches real customer behaviour. | The 3-Lens Principle reveals opportunity costs of pursuing one customer segment over another. Premortems expose assumptions baked into the MVP hypothesis. | +| Early Traction | Distinguishing growth problems from product problems. Churn, slow sales cycles, and support ticket volume are symptoms that can point to very different root causes. | The problem-solution firewall becomes an operational discipline for the leadership team -- separate meetings for diagnosis and action. | +| Growth | Multiple fires burn simultaneously. The temptation to treat symptoms intensifies because there is never enough time. | Second-order thinking becomes critical: every resource allocation decision forecloses other options. Opportunity cost analysis scales with the complexity of the business. | +| Scale | Organisational complexity makes root causes harder to identify. Information is filtered through multiple layers before reaching decision-makers. | The Root Cause Principle must be paired with high-fidelity information-gathering -- going to the source rather than relying on abstractions that have passed through several management layers. | + +A recurring pattern across stages: the earlier a problem is correctly defined, the cheaper it is to solve. At the idea stage, redefining the problem costs a conversation. At growth stage, it costs a quarter's roadmap. At scale, it costs a reorganisation. The compounding cost of solving the wrong problem is the strongest argument for investing disproportionate time in the definition phase -- particularly when the social default is screaming that you should be doing something rather than understanding something. + +The premortem -- imagining what could go wrong before it does -- scales differently across stages as well. At the idea stage, the relevant premortems are existential: "What if no one wants this?" At early traction, they become operational: "What if our biggest customer churns?" At scale, they become systemic: "What if the regulatory environment shifts?" The habit of anticipating failure is the same; the scope of the anticipation widens with the complexity of the business. + +--- + +## Output Template + +```markdown +# Problem Definition and Solution Exploration + +## Problem Statement (Plain Language) +[Two sentences maximum. No jargon. If a twelve-year-old cannot understand this, rewrite it.] + +## Root Cause Analysis +- **Visible symptom(s):** [What is being observed] +- **Root cause hypothesis:** [What would have to be true for this problem not to exist] +- **Test of Time check:** Will solving this root cause fix the problem permanently? [Yes/No + reasoning] +- **Validation method:** [How we will confirm this is the real root cause, not another symptom] + +## Solution Space (Minimum 3 Options) + +| Option | Description | Second-Order Consequences (Lens 2) | Hidden Opportunity Costs (Lens 3) | +|--------|-------------|-------------------------------------|-----------------------------------| +| A | [description] | [and then what?] | [at the expense of what?] | +| B | [description] | [and then what?] | [at the expense of what?] | +| C | [description] | [and then what?] | [at the expense of what?] | +| Both-And? | [integrative option combining elements] | [and then what?] | [at the expense of what?] | + +## Binary Thinking Check +- Are we framing this as only two options? [Yes/No] +- If yes, what would we do if Option A were impossible? Option B? +- What integrative Both-And option exists? + +## Recommendation +[Which option best addresses the root cause, survives the Test of Time, and has the most favourable second-order consequences relative to opportunity costs] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Covers the cognitive biases (anchoring, availability, confirmation) that distort the problem-definition phase. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Addresses the speed-versus-accuracy trade-off when time is scarce; complements the problem-solution firewall with reframing techniques. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- The natural sequel: once the problem is defined and the solution space explored, this skill covers criteria weighting, margin of safety, and execution. +- **[Stoic Problem-Solving](../../content/skills/stoic/stoic-problem-solving.md)** -- Marcus Aurelius's reverse clause and creative reframing of obstacles; a philosophical complement to the structural approach presented here. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Extends the Bad Outcome Principle into a formal methodology for imagining multiple futures and stress-testing strategies. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Provides the analytical lens for tracing root causes through feedback loops and emergent behaviour in complex systems. +- **[Strategic Questioning](../../content/skills/leadership/strategic-questioning.md)** -- The leadership practice of leading through questions rather than answers shares the same premise: better questions produce better solutions. diff --git a/plugins/foreman/skills/delegation-and-empowerment/SKILL.md b/plugins/foreman/skills/delegation-and-empowerment/SKILL.md deleted file mode 120000 index 5d4c711..0000000 --- a/plugins/foreman/skills/delegation-and-empowerment/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/delegation-and-empowerment.md \ No newline at end of file diff --git a/plugins/foreman/skills/delegation-and-empowerment/SKILL.md b/plugins/foreman/skills/delegation-and-empowerment/SKILL.md new file mode 100644 index 0000000..ac1720c --- /dev/null +++ b/plugins/foreman/skills/delegation-and-empowerment/SKILL.md @@ -0,0 +1,199 @@ +--- +name: "delegation-and-empowerment" +description: "Develops the daily practice of effective delegation, accountability diagnosis, and team empowerment. Covers assessing which tasks require personal attention, clarifying scope and context for delegated work, allowing productive struggle, recognising and correcting micromanagement, and leading through influence rather than control. Use when feeling overwhelmed by operational tasks, noticing accountability gaps on a team, receiving feedback about micromanagement, transitioning from individual contributor to manager, or leading a team with more expertise than oneself." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - delegation + - empowerment + - accountability + - micromanagement + - autonomy + - trust + - leadership-transition + - team-development +related_skills: + - hackman-enabling-conditions + - situational-leadership + - trust-equation + - managing-up + - strategic-thinking-and-alignment +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Delegation and Empowerment + +Here is the central paradox of leadership control: the more tightly you grip, the less you actually hold. The leader who insists on reviewing every decision, approving every document, and supervising every task does not have a well-run team -- they have a team of people waiting for instructions. Control feels like safety. It is, in fact, a slow-acting poison that kills initiative, hides problems, and ensures that the leader becomes the organisation's permanent bottleneck. Delegation is not the soft skill that leadership books make it sound like. It is the hardest operational decision a leader makes every day: what to hold and what to release. + +--- + +## The Framework + +### The Four Principles of Effective Delegation + +Delegation fails not because leaders lack the will to let go but because they lack a disciplined method for deciding what to let go of, how to let go of it, and how much involvement to maintain afterward. + +**Principle 1: Assess ruthlessly which tasks require you.** + +The first question is not "Can someone else do this?" but "Must I be the one doing this?" Most leaders overestimate the number of tasks that require their personal involvement. The assessment demands honesty about where the leader's unique contribution lies -- and humility about where it does not. + +A useful sorting mechanism: + +| Category | Description | Action | +|----------|-------------|--------| +| Only-me tasks | Require the leader's specific authority, relationships, or expertise | Retain | +| Grow-someone tasks | Could be done by the leader but would develop a team member if delegated | Delegate with coaching | +| Should-have-been-delegated tasks | The leader does them out of habit, comfort, or distrust | Delegate immediately | +| Shouldn't-exist tasks | Neither the leader nor anyone else should be doing them | Eliminate | + +Most leaders discover, upon honest assessment, that the third category is larger than they expected and the first is smaller. + +**Principle 2: Clarify scope, not steps.** + +Effective delegation specifies the what and the why while leaving the how to the person doing the work. "Prepare a customer analysis for next week's board meeting that shows retention trends and churn drivers" is delegation. "Open the spreadsheet, filter by cohort, create a pivot table, format it in blue..." is micromanagement dressed as thoroughness. + +The scope must include context: why this task matters in the bigger picture. A team member who understands that the board is evaluating a potential acquisition and needs to assess customer stickiness will produce fundamentally different work than one who was simply told to "pull some retention numbers." + +**Principle 3: Calibrate involvement to the person, not the task.** + +Different people need different levels of support for the same task. A senior analyst given a board presentation for the first time needs more check-ins than one who has done it quarterly for two years. The leader's involvement should vary not by their own anxiety level but by the team member's competence and confidence for the specific assignment. + +This is the practical intersection with enabling conditions: the leader's job is to create the conditions for success -- clear direction, adequate resources, appropriate coaching -- and then step back far enough for the person to own the outcome. + +**Principle 4: Allow productive struggle.** + +The urge to rescue is the enemy of development. When a team member is struggling with a delegated task, the instinct to take it back, do it yourself, or provide the answer feels like efficiency. It is, in reality, a development tax: every rescue teaches the team that struggle is a signal to stop rather than a signal to learn. + +Productive struggle has boundaries. The leader who allows a junior employee to fail on a client-facing deliverable without intervention is not empowering anyone; they are being negligent. The calibration is between struggle that builds capability (wrestling with a complex analysis, navigating an ambiguous brief) and struggle that risks genuine harm (missing a regulatory deadline, damaging a key relationship). + +### Diagnosing Accountability Gaps + +When a team lacks accountability, the reflexive diagnosis is that the team is at fault. The more productive diagnosis starts with the leader. Accountability gaps typically stem from one of four root causes: + +1. **Unclear expectations.** The leader has not been specific about what "done" looks like, when it is due, or what quality standard applies. +2. **Insufficient resources.** The team lacks the tools, time, authority, or information to deliver what was asked. +3. **Poor strategy.** The team is accountable for executing a plan that does not make sense, and they know it. +4. **Absent feedback loops.** People do not know whether they are succeeding or failing because no one tells them. + +The diagnostic protocol is to hold a meeting -- not to assign blame but to listen. Summarise the pattern ("We've missed the last three deadlines"), ask for honest perspectives on the causes, and resist the urge to offer critical feedback during the listening phase. The true problems will surface only if the leader creates space for honesty. + +### The Micromanagement Trap + +Micromanagers are, by definition, the last to recognise their condition. The four signature behaviours: + +1. **No autonomy in execution.** Dictating how people do their jobs rather than what outcome is needed. +2. **Progress interrogation without help.** Frequently asking where things stand without offering resources, guidance, or support. +3. **Personal blame as a default.** When problems arise, looking first for a person to hold responsible rather than a system to improve. +4. **Information hoarding.** Controlling access to information as a lever of power rather than sharing it as a tool for team effectiveness. + +Each behaviour has the same root: the belief that control produces better outcomes than trust. The evidence suggests otherwise. Teams under micromanagement hide problems, avoid risk, and produce work that reflects the manager's limitations rather than the team's potential. + +--- + +## Prompts + +**Prompt 1 -- Delegation Audit:** +> List everything on my plate this week: [list major tasks and responsibilities]. For each item, help me assess whether it is an Only-me task, a Grow-someone task, a Should-have-been-delegated task, or a Shouldn't-exist task. For the items I should delegate, identify the right person and the level of involvement I should maintain. Be direct -- I suspect I am holding too much. + +**Prompt 2 -- Accountability Diagnosis:** +> My team has an accountability problem. The symptoms are [describe -- e.g., missed deadlines, dropped commitments, unclear ownership]. Walk me through a diagnostic: ask me questions to determine whether the root cause is unclear expectations, insufficient resources, poor strategy, or absent feedback loops. Then recommend specific interventions for the actual cause, not generic advice about "holding people accountable." + +**Prompt 3 -- Micromanagement Self-Assessment:** +> I have received feedback that I micromanage [or: I suspect I might be micromanaging]. My typical management behaviours include [describe -- how you assign work, how often you check in, how you respond to problems, how you share information]. Assess my behaviour against the four micromanagement patterns and identify which, if any, apply. For each pattern I exhibit, recommend a specific alternative behaviour I can practise this week. + +**Prompt 4 -- Empowerment Conversation Design:** +> I need to delegate [describe task] to [describe person -- their role, experience level, and your assessment of their readiness]. Help me design the delegation conversation: what context to provide about why this matters, how to define scope without prescribing steps, what check-in cadence to establish, and how to create conditions for them to succeed while allowing productive struggle. + +--- + +## Use Cases + +**Early-Traction Founder Who Cannot Let Go** + +A technical founder writes every line of code, reviews every pull request, and personally handles customer escalations. The team of five has grown to twelve, and the founder is working 90-hour weeks while the engineers wait for code reviews that take three days. Applying the delegation audit, the founder discovers that only two of their current tasks -- investor relations and architectural decisions -- are genuine Only-me tasks. Code review, customer escalation triage, and sprint planning are all Grow-someone tasks. The founder delegates code review to the senior engineer with a "scope not steps" brief: "Ensure production readiness and mentor junior developers through the process." The senior engineer, given authority and context, reduces review turnaround to four hours. The founder recovers 25 hours per week. + +**Growth-Stage Team with an Accountability Fog** + +A product team consistently misses sprint commitments. The VP of Product assumes the team is underperforming and considers adding project management overhead. Running the accountability diagnostic reveals a different story: the team is accountable for executing a roadmap that changes every two weeks based on the CEO's latest customer conversation. The problem is not the team's commitment but the leader's strategy. The VP works with the CEO to establish a roadmap freeze policy with a defined change request process. Sprint completion rates double within one quarter -- not because the team worked harder, but because the goal stopped moving. + +**Scale-Stage Leader Recovering from Micromanagement** + +A VP of Operations receives 360-degree feedback indicating that direct reports feel suffocated. The VP, who built their career on operational excellence, genuinely does not see the problem -- they view their involvement as quality assurance. Analysis reveals all four micromanagement patterns: the VP dictates process, asks for daily status updates without adding value, blames individuals for systemic problems, and keeps competitive intelligence to themselves. The VP begins with the lowest-risk change: replacing daily status interrogations with a weekly dashboard that the team self-reports, and biweekly one-on-ones focused on removing blockers rather than reviewing work. Within three months, the team's initiative -- measured by self-started projects and proactive problem-solving -- increases measurably. + +--- + +## Anti-Patterns + +1. **Delegating tasks but not authority.** Asking someone to lead a project but requiring them to seek approval for every decision within it. This creates accountability without agency -- the most demoralising combination in management. + +2. **Delegating only what you dislike.** Using delegation as a garbage disposal for unpleasant tasks while retaining the interesting work. Team members notice this pattern immediately, and it erodes both trust and motivation. + +3. **Rescuing at the first sign of difficulty.** Taking back delegated work when the person struggles. This teaches the team that struggle is a failure state rather than a learning state, and it ensures the leader remains the permanent bottleneck. + +4. **Confusing delegation with abdication.** Handing off a task and disappearing entirely. Delegation without appropriate follow-up is not empowerment; it is abandonment. The leader remains accountable for outcomes even when they delegate execution. + +5. **Diagnosing accountability problems as people problems.** Defaulting to "the team isn't committed enough" before examining whether expectations were clear, resources were sufficient, and strategy was sound. Most accountability failures are leadership failures in disguise. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder letting go of operational tasks | The founder's identity is intertwined with doing the work. Delegation requires not just a method but a psychological shift from "I do" to "I enable." | +| Growth | Building delegation as organisational capability | As layers of management emerge, delegation is no longer just the founder's challenge -- it must be taught and modelled at every leadership level. | +| Scale | Systemic empowerment design | Delegation becomes structural: decision rights, escalation protocols, information flows, and accountability frameworks replace individual delegation conversations. | + +The challenge intensifies with each stage because the stakes of delegation increase. At early traction, a poorly delegated task wastes a week. At scale, a poorly delegated initiative wastes a quarter and a million dollars. The principles remain the same; the consequences of applying them poorly escalate dramatically. + +--- + +## Output Template + +```markdown +# Delegation and Empowerment Assessment + +## Task Audit +| Task | Category | Delegate To | Scope Brief | Check-in Cadence | +|------|----------|-------------|-------------|-----------------| +| [Task 1] | [Only-me / Grow-someone / Should-have-delegated / Eliminate] | [Person or N/A] | [What + why, not how] | [Frequency] | +| [Task 2] | [Category] | [Person or N/A] | [Brief] | [Frequency] | +| [Task 3] | [Category] | [Person or N/A] | [Brief] | [Frequency] | + +## Accountability Diagnostic +- **Primary root cause:** [Unclear expectations / Insufficient resources / Poor strategy / Absent feedback] +- **Evidence:** [Specific observations] +- **Intervention:** [Specific action] + +## Micromanagement Check +| Behaviour | Present? | Evidence | Alternative | +|-----------|----------|----------|-------------| +| Dictating process | [Yes/No] | [Example] | [New behaviour] | +| Progress interrogation | [Yes/No] | [Example] | [New behaviour] | +| Personal blame default | [Yes/No] | [Example] | [New behaviour] | +| Information hoarding | [Yes/No] | [Example] | [New behaviour] | + +## Empowerment Actions (Next 30 Days) +| Action | Person Affected | Expected Outcome | +|--------|----------------|-----------------| +| [Specific delegation or empowerment action] | [Who benefits] | [What changes] | +``` + +--- + +## Related Skills + +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Provides the structural framework for team effectiveness that delegation operates within; the enabling conditions define what "setting someone up for success" actually means. +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- The principle of calibrating involvement to the person and situation is the practical application of situational leadership theory to daily delegation decisions. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Delegation is an act of trust; the reliability and credibility variables of the trust equation determine whether a leader can delegate with confidence. +- **[Managing Up](../../content/skills/leadership/managing-up.md)** -- Leaders who delegate effectively free time for strategic thinking and upward relationship management; the two skills enable each other. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- The strategic altitude problem is often a delegation problem: leaders stuck at 500 feet have not delegated enough ground-level work. +- **[Information Asymmetry](../../content/skills/game-theory/information-asymmetry.md)** -- Every delegation creates a principal-agent relationship where moral hazard and adverse selection dynamics shape whether the delegated work is done faithfully. diff --git a/plugins/foreman/skills/delivering-the-deal/SKILL.md b/plugins/foreman/skills/delivering-the-deal/SKILL.md deleted file mode 120000 index 409153a..0000000 --- a/plugins/foreman/skills/delivering-the-deal/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/negotiation/delivering-the-deal.md \ No newline at end of file diff --git a/plugins/foreman/skills/delivering-the-deal/SKILL.md b/plugins/foreman/skills/delivering-the-deal/SKILL.md new file mode 100644 index 0000000..33a7ad5 --- /dev/null +++ b/plugins/foreman/skills/delivering-the-deal/SKILL.md @@ -0,0 +1,281 @@ +--- +name: "delivering-the-deal" +description: "Provides the complete execution toolkit for closing negotiations: a 21-point preparation checklist, a framework for overcoming obstacles and disarming tactics, and the three-part satisfaction model for durable agreements. Includes a self-assessment instrument for measuring negotiation competence. Use when preparing for a high-stakes negotiation, when a deal has stalled or hit tactical obstacles, when managing post-deal satisfaction and buyer's remorse, or when conducting a negotiation capability audit." +version: "1.0.0" +category: "negotiation" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - preparation + - tactics + - closing + - satisfaction + - obstacles + - deal-making + - self-assessment + - due-diligence +related_skills: + - cooperative-negotiation + - win-win-negotiation + - trust-equation + - cialdini-influence + - scenario-planning + - eisenhower-matrix +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Delivering the Deal + +LAST MILE -- 80% of negotiations collapse in the final 20%. The cause is always the same: premature relaxation when the finish line appears close. The parties have done the hard work of surfacing interests, generating options, building rapport. The outline of agreement is visible. And precisely at this moment, discipline evaporates. Preparation gives way to improvisation. Obstacles that should be anticipated arrive as surprises. Tactics that should be recognised go undetected. The deal that was 90% complete dies not from irreconcilable differences but from sloppy execution in the closing stretch. + +Governor Phil Bredesen of Tennessee -- who built a healthcare company, transformed Nashville's downtown, and recruited the Titans from Houston -- put it plainly during a bus ride through rural China: "A vision without a plan is just a dream." Every negotiator envisions the great deal. Envisioning is the easy part. Delivering requires a systematic preparation process, a protocol for managing obstacles, and a framework for engineering the satisfaction that makes agreements durable. + +--- + +## The Framework + +### Part I: The Negotiator's Preparation Checklist + +Research suggests that 80% of negotiating effort should occur before the parties sit down. The following 21 questions constitute a comprehensive preparation protocol. Working through them requires 30-60 minutes for a standard negotiation, longer for complex multi-party deals. The investment pays returns that compound across every round of the process. + +**Mapping the Terrain** + +1. **Who are the parties?** Include anyone who will affect or be significantly affected by the outcome -- even those not at the table. The absent stakeholder who can veto a deal is more dangerous than the adversary across from you. +2. **What are the core issues?** Identify the two or three fundamental questions the negotiation must answer. Price. Timeline. Scope. Control. Resist the temptation to catalogue every sub-issue at this stage. +3. **How important are the issues relative to the relationship?** This single diagnostic determines whether to lead with a competitive or cooperative approach. High issue importance plus high relationship importance demands principled, interest-based negotiation. High issue importance plus low relationship importance permits more aggressive value-claiming. +4. **Will the other party negotiate competitively or cooperatively?** Anticipate their posture. If competitive, prepare accordingly -- do not bring a cooperative playbook to a zero-sum fight without a fallback. +5. **What is your intended approach?** You may plan to start cooperatively and shift competitive, or vice versa. The key is intentionality. Reactive negotiators lose. + +**Substance and Intelligence** + +6. **How well do you understand the substance?** Ignorance is exploitable. If the other side detects that you do not know the language, valuation methods, or market norms of what you are negotiating, they will calibrate their offers accordingly. Do the homework. +7. **What assumptions are you making?** List them explicitly. Then test the critical ones before negotiations begin. A faulty assumption about the other party's authority, budget, or alternatives can crater a deal. +8. **What alternatives exist if no deal is reached?** For both sides. Be honest -- not hopeful, not catastrophic, but realistic about what happens if you walk away. +9. **What is the most likely alternative?** Distill the range of alternatives into the single most probable outcome of no-deal. Analyse its consequences -- financial, relational, reputational -- for both parties. +10. **How can you improve your alternative before the negotiation?** A real estate developer eyeing a parcel bought a comparable lot across the street before returning to the original seller. Her improved alternative -- "I'll simply build over there" -- produced immediate concessions. Strengthen your BATNA before you need it. + +**Strategy and Sequencing** + +11. **What is the strategic sequence of issues?** Conventional wisdom says start with easy issues to build momentum. The better approach: sequence issues to preserve linkage. If you resolve the easy issues first and then hit a wall on the hard ones, you have no remaining currency to trade. Leave enough unsettled that you can move value between issues to unlock an impasse. +12. **What is your ideal outcome?** Define your target with precision. A sharpshooter cannot hit what they cannot see. +13. **What is your bottom line?** This must be better than your most likely alternative. Otherwise, take the alternative. Write it down before the negotiation begins. Revise only with new information, not under pressure. +14. **Will you make the first offer?** First offers anchor. If you want influence, go first. If you want information, let them go first. Decide in advance. +15. **What is your opening offer?** Formulate it based on research, not aspiration. Consider how to present it for maximum impact on the other side's expectations. +16. **What does the concession dance look like?** Map anticipated moves and countermoves. You will not get it exactly right, but the exercise forces you to think in sequences rather than reactions. + +**Interests and Creativity** + +17. **What are the intangible interests on each side?** Speculate on ego, fear, relationships, and circumstances for the other party. Map your own with equal honesty. +18. **What creative options might be integrated?** Brainstorm without constraint. The analytical brain evaluates; the creative brain generates. Do not run both simultaneously. + +**Tactical Readiness** + +19. **What tactics do you anticipate?** Especially relevant if you have negotiated with the counterparty before. Prepare specific responses. +20. **What is the optimal setting?** Control environment when possible. Consider comfort, formality, and whether the setting gives either party an unearned advantage. +21. **When is the optimal time?** Timing is leverage. Negotiate when the other party is most inclined to agree -- before their fiscal year closes, after they have lost a competing bid, during their expansion phase. + +### Part II: Overcoming Obstacles + +Obstacles are not interruptions to the negotiation process; they are the process. Some are factual and circumstantial. Some are personal and psychological. Some are deliberate tactics deployed to extract advantage. + +**The Sullenberger Protocol** + +Captain Sully Sullenberger landed US Airways Flight 1549 on the Hudson River with 155 souls aboard after a dual bird strike eliminated both engines. He had never trained for this specific scenario. He succeeded because he executed six principles that translate directly to negotiation obstacle management: + +1. **Right approach** -- Remain calm when the process fails. Emotional reactions produce positional entrenchment. Strategic composure produces options. +2. **Right communication** -- Keep the lines open. When communication dies, the deal dies with it. If direct communication is failing, bring in a third party -- mediator, advisor, mutual contact. +3. **Right vision** -- See the solution inside the problem. Shift mental energy from cataloguing barriers to identifying the opportunity each barrier presents. +4. **Right roles** -- Match your role to the moment. In a single negotiation, you may need to be a listener, a challenger, an ally, a strategist, and a peacemaker. Knowing which role the current moment demands is its own form of intelligence. +5. **Right values** -- Decide your ethical boundaries before the pressure arrives. Negotiators whose values flex under duress eventually find themselves in deals they cannot defend. +6. **Right decision** -- The first five elements converge on this one. Good process yields good judgement. Rushed process yields lucky or unlucky outcomes. + +**The Three-Step Tactic Disarmament Protocol** + +When the other party deploys a tactic, two instinctive responses present themselves: ignore it (which signals that it is working) or counter with a tactic of your own (which escalates the tactical arms race and pulls focus from substance). Neither is productive. + +**Step 1: Identify the tactic.** Recognise it by name. Common varieties: + +| Tactic | Mechanism | What It Looks Like | +|--------|-----------|-------------------| +| Bait and switch | Signal willingness on X, then withdraw it after commitment | "We agreed on that, but our board has a new requirement..." | +| Take it or leave it | Force a binary decision to preclude negotiation | "This is our final offer. Accept or we walk." | +| Lack of authority | Introduce an unseen decision-maker to ratchet demands | "I'd love to agree, but my partner needs one more thing..." | +| Bogus demands | Inflate the agenda with issues they will later "concede" | "We also need exclusivity, a non-compete, and first refusal..." | +| Time pressure | Compress the timeline to force hasty concessions | "This offer expires at 5pm today." | +| Going in the other direction | Move further from agreement to reset anchoring | "Actually, we need to revisit the terms we already settled." | + +**Step 2: Call it out.** Name the tactic explicitly. "It looks like we're being asked to bid against ourselves here. Can we establish that both sides will exchange counteroffers?" Labelling a tactic diminishes its power. The other party may become defensive, but more often they simply stop. + +**Step 3: Negotiate the process before the substance.** If the tactic persists, halt the substantive negotiation. You always have the power to stop and renegotiate the rules. "We're going to pause on the terms until we agree on how this process will work. Once we have a process both sides trust, we'll be in a better position to reach agreement." + +### Part III: The Secrets of Satisfaction + +A deal is not durable because the terms are good. A deal is durable because both parties feel satisfied. Satisfaction and substantive outcome are correlated but not synonymous -- research shows that negotiators who achieve objectively superior outcomes sometimes feel less satisfied than those who achieved less but experienced a better process. + +**Subjective Value: The Hidden Variable** + +Four components determine whether a negotiator feels satisfied: + +1. How they feel about the relationship with their counterpart +2. How they feel about their own behaviour during the negotiation +3. How they feel about the fairness of the process +4. How they feel about the outcome + +A striking finding: in controlled experiments, negotiators who were falsely told their counterpart was happy with the outcome felt less successful than those told their counterpart was disappointed -- even though the actual outcomes were identical. Satisfaction is comparative, not absolute. + +**The Counterfactual Trap** + +Post-deal regret -- "What if I had pushed harder?" -- is a predictable psychological phenomenon, not a sign of a bad deal. It intensifies when the other party accepts a first offer too quickly (triggering suspicion that you left value on the table) and when negotiations involve multiple issues (each resolved issue creates a "what if" scenario). Awareness of this tendency is itself a defence: the regret is generated by the brain's counterfactual machinery, not by the economics of the deal. + +**The Three Pillars of Satisfaction** + +Durable agreements require satisfaction across three dimensions: + +**1. Process satisfaction.** People accept outcomes they might otherwise reject when the process feels fair, inclusive, and well-managed. A negotiation that rushes to closure, excludes key stakeholders, or feels chaotic will produce fragile agreements regardless of the terms. Build process satisfaction by: establishing clear agendas, allowing adequate time for deliberation, giving all parties voice, and documenting agreements transparently. + +**2. People satisfaction.** The human element. How the parties treat each other during the negotiation determines whether the agreement is implemented in good faith or sabotaged passively. Two nurses in a Nashville hospital stopped to hug a grieving family before performing their clinical duties. The clinical outcome was unchanged. The human experience was transformed. Build people satisfaction by: acknowledging emotions before addressing logistics, following through on small commitments during the process, and treating the other party's concerns as legitimate even when they are obstacles. + +**3. Product satisfaction.** The substantive terms of the deal. Product satisfaction is necessary but insufficient alone. Many negotiators throw resources at the product dimension -- better price, more favourable terms -- while neglecting process and people. The result: a counterparty who got what they asked for but still feels dissatisfied, and who will be a difficult partner in implementation. + +**The Disney Recovery Protocol.** When satisfaction fails in one dimension, compensate aggressively in the other two. A nine-year-old boy tripped on a ride at Disney World -- a product failure. Disney's response: meticulous process (incident report, serious follow-up) and extraordinary people treatment (a stuffed Mickey Mouse, a handwritten note, a personalised get-well message). The family returned the next day and spent more money. The principle scales directly to business negotiation: when you cannot deliver on a term, over-deliver on the process and the relationship. + +**Anchoring Satisfaction Before Closing** + +The final moments of a negotiation disproportionately shape how both parties remember the experience. Three techniques: + +- **Frame against the alternative, not the aspiration.** "Compare this outcome to what would have happened if we hadn't reached agreement" produces more satisfaction than "compare this to what you initially wanted." +- **Summarise mutual gains.** Before signing, walk through what each side achieved. This converts abstract satisfaction into concrete awareness. +- **Manage the counterparty's narrative.** Help them articulate why this is a good deal in terms their stakeholders will accept. If your counterparty cannot explain the deal to their board, the deal is not closed -- it is deferred. + +### Part IV: The Self-Assessment Framework + +Honest self-evaluation separates negotiators who improve from those who repeat the same mistakes with increasing confidence. Score each item 1 (never) through 5 (always) across three domains: + +**Preparation (10 items):** Identifying all parties and authority; analysing issue vs. relationship importance; mapping alternatives for both sides; improving alternatives before negotiating; setting a target outcome; establishing and holding a bottom line; strategic first-offer timing; deliberate opening offer process; ambitious opening offer; planned concession sequence. + +**Execution (6 items):** Adapting approach to the other side's style; willingness to create productive discomfort; engineering empathy through environment and conversation; asking open-ended questions; bringing additional resources into the deal; developing creative options from discovered interests. + +**Strategic Integrity (5 items):** Maintaining credibility through consistent words, moves, and signals; identifying and addressing tactics before proceeding; seeking mutually beneficial solutions; attending to process, people, and product throughout; walking away when the deal or behaviour is unproductive. + +**Scoring:** 90-105 = operating at a high level. 70-89 = developing with identifiable gaps. 50-69 = foundation present but inconsistent. Below 49 = the framework is understood; deliberate practice begins. + +--- + +## Prompts + +**Prompt 1 -- Full Preparation Walkthrough:** +> I have a negotiation in [timeframe] about [describe: contract, partnership, investment, acquisition, hire, dispute]. Walk me through the 21-point Negotiator's Preparation Checklist. For each question, help me formulate a specific answer based on my context: [describe company, stage, counterparty, power dynamics, relationship importance, known alternatives]. Produce a completed Negotiation Preparation Tool I can bring to the table. + +**Prompt 2 -- Tactic Identification and Response:** +> In my current negotiation about [describe], the other party is [describe their behaviour: moving goalposts, refusing to counter, introducing new stakeholders, compressing timelines, making it personal]. Identify which negotiation tactic(s) are being deployed. For each tactic: (1) name it, (2) explain its mechanism, (3) draft a call-out statement I can use, and (4) script a process renegotiation if the tactic persists. My BATNA: [describe]. + +**Prompt 3 -- Satisfaction Engineering:** +> I am about to close a deal on [describe terms]. Before signing, help me: (1) assess whether both sides have satisfaction across process, people, and product dimensions, (2) identify any dimension where satisfaction is weak and suggest compensating actions, (3) draft a closing summary that anchors both parties' satisfaction, and (4) anticipate potential post-deal regret triggers and prepare a counter-narrative. The other party's key stakeholders are [describe]. + +**Prompt 4 -- Negotiation Self-Assessment Debrief:** +> I just completed a negotiation. Here is what happened: [describe process and outcome]. Walk me through the 21-item self-assessment framework. For each item, help me honestly score my performance (1-5) and identify specific actions to improve. Produce a personalised development plan focusing on my three weakest areas. + +**Prompt 5 -- Obstacle Scenario Planning:** +> I anticipate the following obstacles in my upcoming negotiation about [describe]: [list known obstacles -- deadlock risk, emotional counterparty, power imbalance, cultural differences, multiple parties, bad faith signals]. For each obstacle, apply the Sullenberger Protocol: (1) what is the right approach, (2) what communication strategy fits, (3) what does the solution look like inside this problem, (4) what role should I play, (5) what values guide my response, and (6) what is the right decision framework? + +--- + +## Use Cases + +**Validation-Stage Startup Closing Its First Enterprise Pilot** + +A pre-revenue startup has spent three months in conversations with a mid-market company's VP of Operations. The VP is enthusiastic but procurement has entered and is deploying classic tactics: bogus demands (source code escrow, unlimited liability, exclusivity), time pressure ("resolve this by quarter-end"), and lack of authority ("legal has concerns"). The founder applies the three-step disarmament protocol. She calls out the pattern: "Some of these requests feel like standard procurement positioning rather than genuine requirements. Can we separate the must-haves from the nice-to-haves?" She then negotiates the process: mutual term sheet format, three real issues to resolve, standard language for the rest. On satisfaction, she focuses on the VP -- the internal champion -- helping him build the narrative his leadership needs: risk mitigation (limited scope), measurable outcomes (defined success criteria), ease of exit (30-day termination). Procurement signs off because the process felt rigorous. The pilot launches. + +**Scale-Stage Acquisition: Managing Buyer's Remorse** + +A 300-person company has agreed to a $180M acquisition, but two weeks before signing, the acquirer's integration team raises concerns about technical debt, key-person dependency, and customer concentration. The CFO signals interest in a price reduction. The founder recognises the counterfactual trap -- the acquirer's team is generating "what could go wrong" scenarios that erode subjective satisfaction with their own deal. She addresses process satisfaction by proposing a structured due diligence week with full access; people satisfaction by arranging direct conversations between her engineering leads and the acquirer's CTO; and product satisfaction by presenting a data room that contextualises each concern with data (concentration declining quarter-over-quarter, succession plan documented, technical debt remediation funded). She frames the closing against the alternative: "The strategic rationale has not changed. The risks are real, documented, and managed. The alternative is restarting a search in a market where this capability is scarce." The deal closes at the original price with an earn-out component addressing residual anxiety. + +--- + +## Anti-Patterns + +**Treating preparation as a mental exercise.** Thinking through the checklist is not the same as completing it. The Negotiation Preparation Tool demands written answers -- not because writing is sacred, but because it forces precision. The difference between "I think their alternative is weak" and writing "Their most likely alternative is rebidding the contract, which will cost them 6-8 weeks and risks losing internal sponsorship from the VP who championed this project" is the difference between intuition and strategy. + +**Over-preparing substance, under-preparing behaviour.** Research confirms that negotiators devote extensive effort to defining what they want and almost none to planning how they will engage the human beings across the table. The checklist's behavioural questions (items 3-5, 17, 19-21) are not secondary -- they are where most negotiations are won or lost. + +**Ignoring tactics until they succeed.** The instinct to ignore a tactic -- hoping it will stop -- signals to the other party that the tactic is effective. Every unreturned serve emboldens the next. Identify, call out, and negotiate the process. This is not adversarial -- it is hygienic. + +**Celebrating the deal before engineering satisfaction.** A signed term sheet with an unsatisfied counterparty is a lawsuit waiting to happen. Satisfaction must be designed, not assumed. If the other party cannot explain to their own stakeholders why this is a good deal, the agreement is structurally fragile. + +**Neglecting post-deal relationship management.** The negotiation does not end at signing. The first 90 days of implementation determine whether the agreement becomes a productive partnership or a source of escalating disputes. Build a post-signing check-in cadence into the deal itself. + +**Using the self-assessment to confirm existing beliefs.** The diagnostic is useful only when answered with uncomfortable honesty. Most negotiators overrate their listening skills, underrate their tendency to skip preparation, and avoid confronting their discomfort with tactical conflict. Score yourself as your toughest counterparty would score you. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder agreements, advisor term sheets, early IP negotiations | Preparation is fast but critical. Founders skip checklists because "we trust each other." Trust does not survive ambiguity. Write it down. | +| Validation | First customer contracts, seed fundraising, vendor agreements | Weak alternatives demand compensating preparation. Work items 8-10 relentlessly -- improving your BATNA is the highest-leverage pre-negotiation activity when you have almost no leverage. | +| Early Traction | Hiring key employees, Series A terms, partnership deals | Negotiations become concurrent. The checklist must be repeatable and quick enough to apply to five deals in a single week without degrading quality. Standardise your preparation process. | +| Growth | Enterprise sales, multi-party alliances, board-level negotiations | Obstacles intensify and tactics become more sophisticated. The three-step disarmament protocol is no longer optional -- it is a daily operational requirement. Satisfaction engineering now involves stakeholders you will never meet (the counterparty's board, their investors, their legal counsel). | +| Scale | M&A, international expansion, regulatory negotiation, public-market transactions | Every element of this framework operates simultaneously and at high stakes. Preparation is done by teams, not individuals. Obstacle management requires scenario planning across multiple failure modes. Satisfaction must be engineered for counterparties, their stakeholders, regulators, and the public narrative. | + +--- + +## Output Template + +```markdown +# Negotiation Preparation Tool: [Deal/Context] + +## Terrain Map +- **Parties:** [All parties, including absent stakeholders with veto power] +- **Core issues:** [2-3 fundamental questions to resolve] +- **Issue vs. relationship importance:** [Both High / Issue High + Relationship Low / etc.] +- **Anticipated counterparty approach:** [Competitive / Cooperative / Mixed] +- **Our intended approach:** [Describe, including triggers for shifting] + +## Intelligence and Alternatives +- **Substance mastery:** [Confident / Adequate / Gaps to close] +- **Key assumptions to test:** [List] +- **Our BATNA:** [Best alternative, ranked] | **Their BATNA (est.):** [Ranked] +- **BATNA improvement actions:** [What we can do before the negotiation] + +## Strategy +- **Issue sequence:** [Order and rationale] +- **Target / Bottom line:** [Ideal outcome] / [Walk-away point] +- **First offer:** [Go first or let them — rationale] | **Opening terms:** [Specific] +- **Concession map:** [Anticipated sequence of moves and countermoves] +- **Intangible interests:** Ours: [list] | Theirs (est.): [list] +- **Creative options:** [Brainstormed list] + +## Tactical Readiness +- **Anticipated tactics and responses:** [List] +- **Setting and timing:** [Location, room setup, timing rationale] + +## Satisfaction Plan +| Dimension | Plan | Contingency if Weak | +|-----------|------|---------------------| +| Process | [How we ensure fairness] | [Compensating action] | +| People | [How we treat the counterparty] | [Compensating action] | +| Product | [How we ensure adequate terms] | [Compensating action] | +- **Closing narrative:** [How we help them explain this deal to their stakeholders] +- **Post-deal:** [30/60/90-day check-in schedule and satisfaction monitoring] +``` + +--- + +## Related Skills + +- **[Cooperative Negotiation](../../content/skills/negotiation/cooperative-negotiation.md)** -- The interest-based negotiation execution that precedes this skill's closing and delivery techniques; master cooperative negotiation to generate the deal, master this skill to close and sustain it. +- **[Competitive Negotiation](../../content/skills/negotiation/competitive-negotiation.md)** -- The value-claiming execution that often runs in parallel; delivering the deal requires managing both cooperative and competitive dynamics through to closure. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's theoretical framework; this skill operationalises the preparation, obstacle management, and satisfaction dimensions the model assumes but does not detail. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Influence principles inform both tactical awareness and satisfaction engineering, using consistency and social proof to anchor agreement. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the substrate of satisfaction; low-trust deals require heavier process and documentation to compensate for the absence of relational satisfaction. +- **[Coalition and Partnership Games](../../content/skills/game-theory/coalition-and-partnership-games.md)** -- Multi-party deal delivery requires understanding Shapley Value allocation and core stability to ensure all coalition members perceive the outcome as fair. diff --git a/plugins/foreman/skills/disruptive-innovation/SKILL.md b/plugins/foreman/skills/disruptive-innovation/SKILL.md deleted file mode 120000 index 12d6891..0000000 --- a/plugins/foreman/skills/disruptive-innovation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/disruptive-innovation.md \ No newline at end of file diff --git a/plugins/foreman/skills/disruptive-innovation/SKILL.md b/plugins/foreman/skills/disruptive-innovation/SKILL.md new file mode 100644 index 0000000..d4c23fc --- /dev/null +++ b/plugins/foreman/skills/disruptive-innovation/SKILL.md @@ -0,0 +1,206 @@ +--- +name: "disruptive-innovation" +description: "Analyzes market opportunities and threats using Christensen's Disruptive Innovation theory, distinguishing between sustaining and disruptive innovation, low-end and new-market disruption. Evaluates incumbent vulnerability, asymmetric advantages, and technology improvement trajectories. Use when assessing whether a startup has a genuinely disruptive position, mapping incumbent blind spots, designing market entry strategies that avoid direct competition, defending against disruption from below, or evaluating whether to pursue low-end or new-market footholds." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth +tags: + - disruption + - competitive-strategy + - market-entry + - incumbent-vulnerability + - innovation-theory +related_skills: + - doblin-ten-types + - blue-ocean-strategy + - product-life-cycle + - growth-share-matrix +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Disruptive Innovation + +Kodak invented the digital camera in 1975 and buried it, fearful of cannibalising its film business. By 2012, the company had filed for bankruptcy. Blockbuster had the opportunity to acquire Netflix for $50 million in 2000 and declined; by 2010, it was gone. Nokia commanded 49% of the global smartphone market in 2007, the year Apple introduced the iPhone; by 2013, its handset division was sold to Microsoft for a fraction of its former value. These are not cautionary tales about bad management. They are case studies in a structural pattern that Clayton Christensen identified and named in *The Innovator's Dilemma* (1997): disruption does not kill companies because their leaders are incompetent. It kills them because their leaders are doing exactly what good management theory tells them to do -- listening to their best customers, investing in the highest-margin opportunities, and pursuing sustaining innovations that improve existing products along established performance dimensions. The tragedy is that rational, well-managed companies can do everything right and still lose everything. + +--- + +## The Framework + +### The Mechanism of Disruption + +Christensen distinguished between two fundamentally different types of innovation: + +**Sustaining Innovation** improves existing products along dimensions that mainstream customers already value. Faster processors, sharper displays, more features. Incumbents almost always win at sustaining innovation because they have the resources, customer relationships, and organisational incentives to execute it. + +**Disruptive Innovation** introduces products that are initially worse on traditional performance dimensions but offer different value -- typically simplicity, convenience, affordability, or accessibility. These products enter at the low end or in new markets that incumbents ignore because the margins are unattractive. + +The disruption pattern follows a predictable trajectory: + +**Phase 1: The Entrant Emerges Below the Radar** + +The disruptive product is simpler, cheaper, and inferior on the dimensions that mainstream customers care about. Incumbents dismiss it. Their best customers would never accept it. The margins are too low to justify pursuit. Every incentive in the incumbent's organisation points away from engagement. + +- Digital cameras in 1995: low resolution, poor colour accuracy, no prints. Professional photographers would never use them. +- Netflix in 2000: limited catalogue, DVD-by-mail latency, no instant gratification. Blockbuster's Friday-night customers would never switch. +- Smartphones in 2007: compared to Nokia's phones, the first iPhone had terrible battery life, no 3G, and could not send MMS. + +**Phase 2: The Entrant Improves Along a Steeper Trajectory** + +Technology improves faster than customer needs increase. The disruptive product gets better at a rate that eventually exceeds what mainstream customers require. Meanwhile, incumbents overshoot -- adding features and performance that customers neither need nor will pay for. + +**Phase 3: The Entrant Captures the Mainstream** + +The disruptive product becomes "good enough" for the mainstream market while retaining its advantages of simplicity, cost, or convenience. Customers switch. By this point, the incumbent's response is too late -- not because the technology is unreachable, but because the business model, cost structure, and organisational culture cannot adapt fast enough. + +**Phase 4: The Incumbent Retreats or Collapses** + +The incumbent either retreats to an ever-shrinking premium segment, attempts a pivot that its cost structure cannot support, or ceases to exist. + +### Two Types of Disruption + +**Low-End Disruption** targets customers at the bottom of the existing market -- those who are overserved by current offerings and willing to accept "good enough" performance at a lower price. + +- Example: Southwest Airlines offered no assigned seats, no meals, no frills -- and fares that opened air travel to customers who previously drove or took the bus. +- Incumbent response: Major airlines ceded the low end because those customers were unprofitable under their cost structures. + +**New-Market Disruption** creates demand among people who were previously non-consumers -- those who lacked the money, skills, or access to use existing solutions. + +- Example: Personal computers disrupted minicomputers not by being better for existing minicomputer users, but by enabling millions of people who could never have afforded or operated a minicomputer to use computing power. +- Incumbent response: DEC and other minicomputer makers saw no threat because PCs could not do what their products did. By the time PCs could, the market had moved. + +### The Innovator's Dilemma, Precisely Stated + +The dilemma is structural, not intellectual. Incumbents understand the disruption. They can see it coming. They often have the technology to respond. But their existing customers do not want the disruptive product, their financial models cannot support the lower margins, and their organisational processes are optimised for sustaining innovation. The very capabilities that made them successful prevent them from responding to disruption. + +This is why Christensen's work remains so valuable for entrepreneurs: the incumbent's rational response creates a structural opening that the entrant can exploit with near-certainty. + +--- + +## Prompts + +**Prompt 1 -- Disruption Potential Assessment:** +> "Analyse whether my product/service [describe offering] qualifies as a disruptive innovation against incumbent [describe incumbent]. Assess: (1) Are we targeting overserved customers or non-consumers? (2) Is our product worse on traditional dimensions but better on simplicity, convenience, or cost? (3) Is the incumbent structurally unable to respond without cannibalising their core business? (4) Is there a plausible technology trajectory that will make our product good enough for the mainstream within [timeframe]?" + +**Prompt 2 -- Incumbent Vulnerability Mapping:** +> "Map the vulnerability of incumbents in [industry] to disruption. For each major incumbent: (1) What is their cost structure and minimum viable margin? (2) Where are their best customers pulling them (toward complexity and premium features)? (3) What customer segments are overserved or priced out? (4) What emerging technologies could enable a simpler, cheaper alternative? Identify the most vulnerable point of entry for a disruptive entrant." + +**Prompt 3 -- Disruption Defence Strategy:** +> "My company is an incumbent in [market] with [revenue/market position]. Analyse our vulnerability to disruption from below or from new-market entrants. Where is our market most exposed? What signals should we monitor for early-stage disruptive threats? Design a defensive strategy that includes: an autonomous unit to pursue disruptive opportunities, metrics for tracking low-end market dynamics, and decision criteria for when to cannibalise our own products." + +**Prompt 4 -- Asymmetric Advantage Identification:** +> "Identify the asymmetric advantages I hold as a startup against incumbents in [market]. Consider: cost structure flexibility, absence of channel conflict, willingness to serve low-margin segments, organisational speed, and freedom from legacy technology. For each advantage, describe a specific strategic move that exploits it while remaining in the incumbent's 'blind spot.'" + +--- + +## Use Cases + +**Idea-Stage Founder Evaluating a Market Entry Strategy** + +A founder developing an AI-powered legal document service considers the market for corporate legal services dominated by major law firms. Christensen's framework clarifies the opportunity: large firms serve enterprise clients with bespoke, high-margin work and are structurally unable to offer standardised services at low price points without cannibalising their revenue model. Small businesses and solo entrepreneurs -- non-consumers of corporate legal services -- represent the new-market disruption opportunity. The founder designs a product that automates 80% of routine legal documents at 5% of the cost of a law firm, accepting that the 20% of complex cases requiring bespoke attention will remain with incumbents for years. The technology trajectory (improving AI accuracy) ensures that the 80/20 boundary will shift over time, expanding the addressable market while incumbents continue to move upmarket. + +**Validation-Stage Hardware Startup Positioning Against an Established Brand** + +A startup building an affordable 3D printer targets schools and hobbyists -- customers whom industrial 3D printing companies have never served because the margins are too thin and the support requirements too demanding for their sales organisations. The product is inferior on every dimension that industrial customers measure: precision, build volume, material range, and durability. But it costs 90% less and requires no specialised training. Christensen's framework confirms the positioning: this is classic low-end disruption. The startup validates by selling 500 units to schools through a crowdfunding campaign, proving demand exists in a segment that incumbents have no incentive to pursue. The product roadmap focuses on improving precision and material support along a trajectory that will eventually make the product "good enough" for professional prototyping. + +**Growth-Stage Fintech Navigating the Incumbent Response** + +A challenger bank with 200,000 accounts observes that traditional banks are beginning to launch digital-only offerings. Christensen's theory predicts this response -- and its likely failure. The incumbent's digital product will be constrained by its existing cost structure (branch network, compliance infrastructure, legacy systems), its organisational incentives (branch managers who resist cannibalisation), and its customer expectations (existing customers who demand full-service banking). The challenger's strategic response: accelerate product development in areas where the incumbent's cost structure prevents them from competing (instant lending decisions, zero-fee international transfers, real-time spending analytics) while building switching costs through product system innovation that makes the challenger the customer's primary financial relationship. + +--- + +## Anti-Patterns + +**Labelling Every New Product "Disruptive."** The term has been diluted to meaninglessness in popular usage. A better mousetrap is not disruption -- it is sustaining innovation. True disruption requires structural asymmetry: the incumbent cannot respond without damaging its core business. If the incumbent can simply build a competing product, there is no dilemma, and the startup is in a sustaining fight it will probably lose. + +**Targeting the Incumbent's Best Customers from Day One.** Disruptive entrants who go directly after the incumbent's core market trigger a competitive response that they cannot survive. The asymmetric advantage only exists when the entrant is serving customers the incumbent does not value. Attacking the core is sustaining competition -- and the incumbent has every advantage. + +**Underestimating the Importance of a Business Model.** Disruption is not primarily a technology phenomenon. It is a business model phenomenon. Uber did not disrupt taxis with superior technology; it disrupted them with a business model that eliminated the medallion system, reduced idle time, and created dynamic pricing. Entrepreneurs who focus exclusively on technical superiority while inheriting their industry's business model are fighting with one hand behind their back. + +**Assuming Incumbents Cannot Respond.** Christensen's framework describes why incumbents struggle to respond -- not that they never succeed. Microsoft survived the cloud disruption by creating Azure as a separate business unit with its own incentives. Intel invested in mobile chips. Some incumbents learn. The founder who assumes invulnerability will be surprised when a well-resourced incumbent deploys its considerable advantages in a belated but effective response. + +**Confusing Market Size with Opportunity.** Disruptive markets start small and grow. VCs and founders who require a billion-dollar addressable market on day one will dismiss precisely the opportunities that Christensen's theory identifies as most promising. The small, unattractive market is the feature, not the bug -- it is what keeps incumbents away. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Identify the asymmetry | Evaluate whether the opportunity has the structural characteristics of disruption: overserved customers, non-consumers, incumbent cost structure constraints | +| Validation | Prove demand in the overlooked segment | Validate that the customers incumbents ignore actually want your inferior-but-accessible product | +| Early Traction | Stay beneath the radar | Grow in the low-end or new-market segment; avoid triggering the incumbent's competitive response prematurely | +| Growth | Ride the improvement trajectory | As technology improves, expand into adjacent segments; the product becomes "good enough" for increasingly demanding customers | + +At the idea stage, the critical discipline is honesty about whether the opportunity is genuinely disruptive or merely competitive. The litmus test: would the incumbent's best customers want your product today? If yes, you are in a sustaining fight. If no, you may have a disruptive position. + +During early traction and growth, the temptation to pursue the incumbent's premium customers is intense -- they represent higher margins and larger contract values. Resist. Premature upmarket migration sacrifices the asymmetric advantage that makes disruption work. The strategy is to let the technology trajectory carry you upmarket while maintaining the cost structure advantages that the incumbent cannot match. + +--- + +## Output Template + +**Target Audience: Investors / Board** + +```markdown +# Disruption Analysis: [Company Name] in [Market] +## Date: [Date] + +### Disruption Classification +- Type: [Low-End Disruption / New-Market Disruption / Sustaining Innovation] +- Confidence: [High/Medium/Low] -- [Brief justification] + +### The Incumbent's Dilemma +| Dimension | Incumbent Position | Why They Cannot Respond | +|-----------|-------------------|----------------------| +| Cost structure | [Their cost base] | [Why they cannot profitably serve our segment] | +| Customer incentives | [Who their best customers are] | [Why those customers pull them away from our market] | +| Organisational design | [How they are structured] | [Why their organisation resists cannibilisation] | +| Channel conflict | [Their distribution model] | [How responding would damage existing channel relationships] | + +### Our Asymmetric Advantages +1. [Advantage] -- Exploitation strategy: [How we use it] +2. [Advantage] -- Exploitation strategy: [How we use it] +3. [Advantage] -- Exploitation strategy: [How we use it] + +### Technology Trajectory +- Current product performance vs. mainstream requirements: [Gap description] +- Improvement rate: [How quickly we are closing the gap] +- Estimated "good enough" date for mainstream market: [Timeline] + +### Disruption Phase Assessment +- [ ] Phase 1: Below the radar (serving overlooked segment) +- [ ] Phase 2: Improving faster than market demands +- [ ] Phase 3: Capturing mainstream customers +- [ ] Phase 4: Incumbent in retreat + +### Risk Factors +| Risk | Likelihood | Mitigation | +|------|-----------|------------| +| Incumbent creates autonomous unit to respond | [H/M/L] | [Strategy] | +| Another entrant disrupts from a different angle | [H/M/L] | [Strategy] | +| Technology trajectory stalls | [H/M/L] | [Strategy] | + +### Strategic Recommendations (Next 12 Months) +1. [Recommendation] -- Rationale: [Why] +2. [Recommendation] -- Rationale: [Why] +3. [Recommendation] -- Rationale: [Why] +``` + +--- + +## Related Skills + +- **[Doblin's Ten Types of Innovation](../../content/skills/frameworks/doblin-ten-types.md)** -- Disruption typically requires innovation across multiple types (profit model, process, channel) rather than product alone; Doblin provides the toolkit for building multi-layered disruptive advantage. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- New-market disruption is conceptually adjacent to Blue Ocean thinking; both identify opportunities in non-consumption, though they approach the problem from different angles. +- **[Product Life Cycle](../../content/skills/frameworks/product-life-cycle.md)** -- Products in the maturity or decline phase are most vulnerable to disruption; understanding life cycle dynamics helps identify the optimal timing for disruptive market entry. +- **[Growth Share Matrix](../../content/skills/frameworks/growth-share-matrix.md)** -- Incumbents' portfolio decisions (milking cash cows, investing in stars) create predictable blind spots that disruptive entrants can exploit. +- **[Ambidexterity](../../content/skills/frameworks/ambidexterity.md)** -- The organizational architecture that allows incumbents to respond to disruption by running separate exploration units with different metrics and culture. +- **[Evolutionary Strategy](../../content/skills/game-theory/evolutionary-strategy.md)** -- Provides the game-theoretic lens for understanding how disruptive entrants and incumbents co-evolve in competitive ecosystems over time. diff --git a/plugins/foreman/skills/doblin-ten-types/SKILL.md b/plugins/foreman/skills/doblin-ten-types/SKILL.md deleted file mode 120000 index 0ebe731..0000000 --- a/plugins/foreman/skills/doblin-ten-types/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/doblin-ten-types.md \ No newline at end of file diff --git a/plugins/foreman/skills/doblin-ten-types/SKILL.md b/plugins/foreman/skills/doblin-ten-types/SKILL.md new file mode 100644 index 0000000..2509ed8 --- /dev/null +++ b/plugins/foreman/skills/doblin-ten-types/SKILL.md @@ -0,0 +1,224 @@ +--- +name: "doblin-ten-types" +description: "Maps and designs innovation strategy using Doblin's Ten Types of Innovation across Configuration (Profit Model, Network, Structure, Process), Offering (Product Performance, Product System), and Experience (Service, Channel, Brand, Customer Engagement). Use when auditing current innovation profile, identifying competitive white space, building multi-layered defensible advantages, breaking through competitive ceilings caused by product-only innovation, or designing a new business with structural moats from inception." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth +tags: + - innovation-strategy + - business-model-design + - competitive-advantage + - value-creation + - differentiation +related_skills: + - disruptive-innovation + - blue-ocean-strategy + - product-life-cycle + - balanced-scorecard +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Doblin's Ten Types of Innovation + +Most entrepreneurs, when asked about innovation, picture a product: a new gadget, a novel app feature, a technological breakthrough. This reflex -- equating innovation with invention -- is both pervasive and profoundly limiting. Larry Keeley and his colleagues at Doblin (now part of Deloitte) spent decades analysing thousands of innovations across industries and reached a conclusion that should discomfort any product-obsessed founder: product innovation is the easiest type for competitors to copy and the least likely to deliver sustained competitive advantage. The companies that dominate their markets innovate across multiple types simultaneously, building advantages that are structurally difficult to replicate because they exist not in any single feature but in the configuration of the entire business. + +The Ten Types of Innovation framework, published in 2013, provides the most comprehensive taxonomy of innovation available. It is not a theory about creativity. It is a strategic architecture for building businesses that competitors cannot easily decode. + +--- + +## The Framework + +The ten types organise into three categories: Configuration (how the business is structured), Offering (what the business delivers), and Experience (how customers interact with the business). + +### Configuration (Internal-Facing Innovation) + +**1. Profit Model -- How You Make Money** + +Innovation in the mechanism that converts value into revenue. Gillette did not invent the razor; it invented razors-and-blades pricing. Salesforce did not invent CRM; it invented SaaS subscription pricing for enterprise software. + +*Entrepreneurial application:* Challenge the default pricing model in your industry. Subscription where competitors charge one-time fees. Freemium where competitors charge upfront. Usage-based where competitors charge flat rates. Revenue-share where competitors charge licensing fees. + +**2. Network -- How You Connect with Others to Create Value** + +Innovation through alliances, partnerships, and ecosystems. Visa created a network of banks that would have been competitors if left to individual action. Apple's App Store turned independent developers into a product-development army. + +*Entrepreneurial application:* Identify which external parties could contribute to your value proposition if properly incentivised. Marketplace models, API platforms, franchise structures, and co-branding partnerships all represent network innovation. + +**3. Structure -- How You Organise and Align Talent and Assets** + +Innovation in organisational design, asset configuration, and human capital management. Toyota's production system. Google's 20% time (when it existed). Valve's flat hierarchy. + +*Entrepreneurial application:* How your company is organised affects what it can produce. A remote-first structure enables global talent access. A squad-based model enables parallel product development. Asset-light structures enable rapid scaling. + +**4. Process -- How You Use Superior Methods to Do Your Work** + +Innovation in the signature processes that create competitive advantage. Amazon's fulfilment logistics. IKEA's flat-pack manufacturing. Zara's fast-fashion supply chain that moves from design to retail in two weeks. + +*Entrepreneurial application:* Identify the one or two processes that most directly affect your value proposition. Innovating there -- through automation, proprietary methodology, or radical simplification -- creates defensible advantage because processes are invisible to competitors and difficult to reverse-engineer. + +### Offering (Product-Facing Innovation) + +**5. Product Performance -- How You Develop Distinguishing Features and Functionality** + +The type most people mean when they say "innovation." Superior features, performance, quality, or design. The iPhone's multitouch interface. Dyson's cyclone vacuum technology. Tesla's electric drivetrain. + +*Entrepreneurial application:* Product innovation is necessary but insufficient. Without reinforcement from other innovation types, product advantages erode within 12-18 months as competitors catch up. + +**6. Product System -- How You Create Complementary Products and Services** + +Innovation through creating an ecosystem of connected offerings. Apple's hardware-software-services integration. Microsoft Office as an integrated suite. Peloton's bike-plus-content-plus-community system. + +*Entrepreneurial application:* Consider what adjacent products or services would make your core offering more valuable. Integration points, accessories, data layers, and complementary content all represent product system innovation. + +### Experience (Customer-Facing Innovation) + +**7. Service -- How You Support and Amplify the Value of Your Offering** + +Innovation in the services that surround and enhance the core product. Amazon Prime's delivery promise. Zappos's 365-day return policy. AppleCare's service experience. + +*Entrepreneurial application:* Service innovation is particularly powerful for startups because it often requires organisational commitment rather than capital investment. A superior onboarding experience, proactive customer success, or unconditional guarantees can differentiate without heavy R&D spend. + +**8. Channel -- How You Deliver Your Offering to Customers and Users** + +Innovation in how you reach the customer. Warby Parker's home try-on disrupted optical retail. Dollar Shave Club's direct-to-consumer subscription bypassed retail entirely. Tesla's company-owned showrooms eliminated the dealership model. + +*Entrepreneurial application:* The default distribution channel in your industry may not be the optimal one. Direct-to-consumer, marketplace-first, partnership-led, or hybrid channel strategies can redefine who captures margin in the value chain. + +**9. Brand -- How You Represent Your Offering and Business** + +Innovation in how the company communicates its identity and values. Patagonia's "Don't Buy This Jacket" anti-consumerist positioning. Red Bull's content-company-that-sells-energy-drinks identity. Muji's "no-brand brand" philosophy. + +*Entrepreneurial application:* Brand innovation is not about a better logo. It is about occupying a distinctive position in the customer's mind that competitors cannot credibly claim. The brand should encode the company's strategic differentiation, not merely describe it. + +**10. Customer Engagement -- How You Foster Compelling Interactions** + +Innovation in the end-to-end experience of being a customer. IKEA's self-service showroom experience. Nike's running community and app ecosystem. Airbnb's host-guest trust mechanisms. + +*Entrepreneurial application:* Map every touchpoint in the customer journey. Engagement innovation often lives in the transitions between touchpoints -- the moments where competitors lose the customer's attention or create friction. + +### The Power of Combination + +Doblin's research found that the most successful innovations integrate five or more types simultaneously. Innovating on product alone rarely creates lasting advantage. Innovating across profit model, process, product, service, and channel creates a system that competitors cannot replicate by copying any single component. + +| Number of Types Combined | Competitive Durability | +|--------------------------|----------------------| +| 1-2 types | Easily copied within 12-18 months | +| 3-4 types | Moderately defensible; requires significant competitor effort | +| 5+ types | Structurally difficult to replicate; creates genuine moats | + +--- + +## Prompts + +**Prompt 1 -- Innovation Audit:** +> "Analyse my business: [describe business model, product, and customer experience]. Map our current innovation across all ten Doblin types. For each type, assess whether we have genuine innovation (differentiation that competitors have not replicated), table-stakes performance (meeting industry norms), or a gap (below industry standard). Identify the three types where investment would create the highest strategic return." + +**Prompt 2 -- Competitor Innovation Mapping:** +> "Map the innovation profile of our top three competitors: [names and descriptions]. For each competitor, identify which of the ten types they have innovated in. Overlay their profiles to find: (a) types where no competitor has innovated (white space), (b) types where one competitor dominates (their moat), and (c) types where competition is intense (Red Ocean zones). Recommend where we should focus our innovation investment." + +**Prompt 3 -- Innovation Combination Design:** +> "Given our current strengths in [list 2-3 innovation types], design a strategy that integrates at least five types of innovation. For each additional type, explain: (1) what the innovation would look like, (2) how it reinforces the types we already do well, and (3) the investment required to achieve it. Prioritise by impact-to-cost ratio." + +--- + +## Use Cases + +**Idea-Stage Founder Designing a New Business** + +A founder planning a meal-kit delivery service recognises that product innovation (better recipes, higher-quality ingredients) is the baseline that every competitor offers. Using the Ten Types framework, she designs across six types: Profit Model (flexible subscription with pay-per-box option), Process (AI-driven demand forecasting to minimise food waste), Product Performance (dietary-restriction personalisation), Service (real-time cooking assistance via chat), Channel (partnerships with apartment complexes for refrigerated locker delivery), and Customer Engagement (a community platform where subscribers share modifications and rate meals). The resulting business model is not a better meal kit; it is a fundamentally different customer relationship that competitors cannot replicate by improving their recipes alone. + +**Growth-Stage SaaS Company Breaking Through a Competitive Ceiling** + +A project management SaaS with $5M ARR competes in a market with dozens of similar products. Feature-by-feature competition has produced parity; no single product capability provides lasting advantage. A Doblin analysis reveals that the company's innovation is concentrated entirely in Type 5 (Product Performance). The strategic response targets three additional types: Network (building an integration marketplace that makes the product a platform), Service (white-glove onboarding for enterprise accounts, converting a commodity product into a premium service experience), and Profit Model (shifting from per-seat pricing to value-based pricing tied to projects completed). Within twelve months, enterprise churn drops by 40% -- not because the product improved, but because the business model around the product became structurally stickier. + +**Early-Traction Fintech Navigating a Regulated Market** + +A fintech startup offering small-business lending realises that product innovation (better interest rates, faster approval) faces structural limits set by regulatory capital requirements. The ten-type analysis redirects innovation investment toward Structure (a partnership model where the startup provides the technology platform while banking partners provide the regulated lending licence), Process (automated credit assessment using alternative data sources), Channel (embedded lending offered at point-of-sale through e-commerce partnerships), and Brand (positioning as the "anti-bank" that treats small businesses with transparency). This multi-type approach circumvents the regulatory constraints that limit pure product innovation. + +--- + +## Anti-Patterns + +**Product Tunnel Vision.** Pouring all innovation resources into product features while ignoring the other nine types. This is the most common and most costly error, particularly in technology companies where engineering culture equates innovation with code. + +**Innovation Type Confusion.** Mislabelling marketing campaigns as "Brand Innovation" or customer support improvements as "Service Innovation." Innovation in the Doblin sense means creating a differentiated position that competitors have not replicated. If every company in your industry offers a similar service level, improving your service is table-stakes investment, not service innovation. + +**Checklist Innovation.** Attempting to innovate across all ten types simultaneously. This dilutes resources and produces shallow innovation everywhere rather than deep innovation in the types that matter most. Five types pursued with depth beats ten types pursued superficially. + +**Ignoring the Configuration Layer.** Startups frequently focus on Offering and Experience while neglecting Configuration types (Profit Model, Network, Structure, Process). Yet Configuration innovations are often the most defensible because they are invisible to customers and difficult for competitors to observe and replicate. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Design for multiple types from inception | It is far easier to build multi-type innovation into a business from the start than to retrofit it later | +| Validation | Test the innovation hypotheses | Each innovation type involves assumptions; validate the riskiest ones first | +| Early Traction | Double down on the types driving traction | Identify which innovation types customers actually value versus which you assumed they would | +| Growth | Add innovation types to deepen moats | Use competitive pressure as the signal for which new types to develop | + +At the idea stage, the Ten Types framework is most powerful as a design tool. Rather than asking "What product should I build?" the founder asks "What combination of innovations would create a business that competitors cannot easily replicate?" This shifts the conversation from features to strategy. + +During growth, competitors begin copying visible innovations (product features, channel strategies). This is the moment to invest in less visible types -- Profit Model, Structure, Process -- that create advantages competitors cannot decode from the outside. + +--- + +## Output Template + +**Target Audience: Strategy Team / Innovation Lead** + +```markdown +# Innovation Architecture: [Company Name] +## Date: [Date] + +### Current Innovation Profile +| # | Innovation Type | Category | Current State | Competitive Position | +|---|----------------|----------|---------------|---------------------| +| 1 | Profit Model | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 2 | Network | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 3 | Structure | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 4 | Process | Configuration | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 5 | Product Performance | Offering | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 6 | Product System | Offering | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 7 | Service | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 8 | Channel | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 9 | Brand | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | +| 10 | Customer Engagement | Experience | [Description or "Gap"] | [Ahead/Parity/Behind] | + +### Innovation Intensity Score +- Types with genuine innovation: [N] / 10 +- Types at parity: [N] / 10 +- Types with gaps: [N] / 10 + +### Priority Innovation Investments +| Priority | Type | What We Will Build | Reinforces Types | Investment | Timeline | +|----------|------|-------------------|-----------------|------------|----------| +| 1 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | +| 2 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | +| 3 | [Type] | [Specific innovation] | [Which other types it strengthens] | [Cost/effort] | [Duration] | + +### Competitive Moat Assessment +- Current moat depth: [Shallow/Moderate/Deep] +- Target moat depth (12 months): [Shallow/Moderate/Deep] +- Key vulnerability: [The innovation type where competitors are most likely to surpass us] +``` + +--- + +## Related Skills + +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Christensen's theory explains how disruption happens; Doblin's framework provides the toolkit for building innovations across multiple types that are structurally difficult to disrupt. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Blue Ocean identifies the need for uncontested market space; the Ten Types framework provides ten distinct dimensions along which to create that differentiation. +- **[Product Life Cycle](../../content/skills/frameworks/product-life-cycle.md)** -- As products mature and product-level differentiation erodes, the other nine innovation types become the primary source of competitive advantage. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- The Canvas's nine building blocks map closely to Doblin's ten types, making the Canvas the natural tool for designing how multi-type innovations interconnect operationally. +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- Doblin's Experience types (Service, Channel, Brand, Customer Engagement) map directly to the marketing mix, connecting innovation strategy to go-to-market execution. +- **[Creative Shaping and Craft](../../content/skills/creative/creative-shaping-and-craft.md)** -- Provides the creative methodology for moving from innovation type identification to the concrete design and refinement of each innovation element. diff --git a/plugins/foreman/skills/eisenhower-matrix/SKILL.md b/plugins/foreman/skills/eisenhower-matrix/SKILL.md deleted file mode 120000 index 54f2430..0000000 --- a/plugins/foreman/skills/eisenhower-matrix/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/eisenhower-matrix.md \ No newline at end of file diff --git a/plugins/foreman/skills/eisenhower-matrix/SKILL.md b/plugins/foreman/skills/eisenhower-matrix/SKILL.md new file mode 100644 index 0000000..514d7cb --- /dev/null +++ b/plugins/foreman/skills/eisenhower-matrix/SKILL.md @@ -0,0 +1,200 @@ +--- +name: "eisenhower-matrix" +description: "Prioritizes tasks and time allocation using the Eisenhower Matrix, + classifying activities into four quadrants by urgency and importance: Do + (urgent and important), Schedule (important but not urgent), Delegate (urgent + but not important), and Eliminate (neither). Use when overwhelmed by competing + demands, auditing how a founder spends their time, designing delegation + frameworks, building QII-first weekly calendars, or shifting organizational + time allocation from reactive firefighting to strategic work." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - prioritization + - time-management + - productivity + - decision-making +related_skills: + - covey-seven-habits + - eisenhower-matrix + - kaizen-bpr + - balanced-scorecard +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Eisenhower Matrix + +"What is important is seldom urgent, and what is urgent is seldom important." Dwight D. Eisenhower -- Supreme Allied Commander, thirty-fourth President of the United States, and, by all accounts, a man who managed an extraordinary volume of consequential decisions with unusual composure -- reportedly used this distinction as the organizing principle of his workday. Whether he originated the insight or merely popularized it is debated, but its utility is not. The Eisenhower Matrix (later refined and popularized by Stephen Covey) remains the most widely used prioritization framework in business, and for good reason: it forces a binary distinction that most people instinctively resist. Urgency and importance are different dimensions, and confusing them is the single most common cause of strategic drift in entrepreneurial ventures. + +--- + +## The Framework + +### The 2x2 Matrix + +The matrix classifies every task, decision, or demand on your time into one of four quadrants based on two independent dimensions: urgency (does it demand immediate attention?) and importance (does it contribute to your mission, goals, or values?). + +``` + URGENT NOT URGENT + ┌─────────────────────┬─────────────────────┐ + │ │ │ + IMPORTANT │ QUADRANT I │ QUADRANT II │ + │ DO FIRST │ SCHEDULE │ + │ │ │ + │ Crises │ Strategy │ + │ Deadline-driven │ Relationship- │ + │ projects │ building │ + │ Emergencies │ Planning │ + │ │ Personal growth │ + ├─────────────────────┼─────────────────────┤ + │ │ │ + NOT │ QUADRANT III │ QUADRANT IV │ + IMPORTANT │ DELEGATE │ ELIMINATE │ + │ │ │ + │ Interruptions │ Time-wasters │ + │ Some meetings │ Busywork │ + │ Some emails │ Excessive social │ + │ Others' priorities │ media │ + │ │ Trivia │ + └─────────────────────┴─────────────────────┘ +``` + +### Quadrant Behavior in Detail + +**Quadrant I -- Urgent and Important: DO** +These are genuine crises and hard deadlines. A server outage during a product launch. A key customer threatening to churn. A regulatory deadline. QI tasks demand immediate action and deserve it. The problem is not QI itself but living in QI permanently -- which produces burnout, reactive management, and the sensation that every day is a firefight. + +**Quadrant II -- Important but Not Urgent: SCHEDULE** +This is where strategy lives. Relationship-building. Long-term planning. Product vision work. Team development. Exercise. Reading. These activities rarely scream for attention, which means they are perpetually deferred in favor of whatever is screaming loudest. Covey's central argument -- and the strategic core of the matrix -- is that effective people spend the majority of their discretionary time in QII. The counterintuitive result: investing in QII reduces the volume of QI crises over time, because proactive planning prevents emergencies. + +**Quadrant III -- Urgent but Not Important: DELEGATE** +The deceptive quadrant. These tasks feel important because they are urgent -- a ringing phone, a meeting request, a colleague's "quick question." But they serve someone else's priority, not yours. Entrepreneurs are particularly vulnerable here because early-stage culture rewards responsiveness. The discipline of delegation -- or, more fundamentally, of saying no -- is what separates founders who scale from those who drown. + +**Quadrant IV -- Neither Urgent nor Important: ELIMINATE** +Pure waste. Mindless scrolling. Meetings with no agenda or outcome. Reports nobody reads. The challenge is that QIV activities often masquerade as necessary work or provide short-term psychological relief from the stress of QI. Ruthless elimination of QIV is the easiest productivity gain available. + +### The Quadrant II Principle + +The matrix's deepest insight is not the classification itself but the implication: **most people spend their time in QI and QIII, and most value is created in QII.** The strategic imperative is to systematically shift time allocation toward QII by: + +1. Eliminating QIV entirely +2. Delegating or batching QIII aggressively +3. Reducing QI through proactive QII investment +4. Protecting QII time with the same urgency afforded to QI + +--- + +## Prompts + +**Prompt 1 -- Weekly Prioritization Sort:** +> Here is my task list for this week: [paste task list or describe key activities]. Classify each task into the Eisenhower Matrix quadrants (QI: Do, QII: Schedule, QIII: Delegate, QIV: Eliminate). For each classification, explain your reasoning. Then recommend a daily schedule that protects at least 2 hours of uninterrupted QII time each day. Identify which QIII tasks I should delegate and to whom (given my team is [describe team]). + +**Prompt 2 -- Founder Time Audit:** +> Analyze how I spent my time last week. Here is a rough breakdown: [describe how you spent your time -- meetings, emails, product work, calls, admin, strategy, etc.]. Map each activity to an Eisenhower quadrant. Calculate the percentage of time I spent in each quadrant. Compare this to the ideal distribution for a founder at [my stage]. Identify the three most impactful changes I could make to shift toward QII. + +**Prompt 3 -- Delegation Framework:** +> I struggle with delegation. Here are the tasks I currently handle personally that might belong in QIII: [list tasks]. For each task, assess: Can it be delegated? To whom? What instructions, authority, and check-ins would be needed? What is my resistance to delegating it (control, quality concerns, speed)? Help me build a delegation plan with specific handoff dates and success criteria. + +**Prompt 4 -- QII Strategic Calendar:** +> Help me design a QII-first weekly calendar. My non-negotiable commitments are: [list standing meetings, deadlines, obligations]. My most important QII activities are: [list -- e.g., product strategy, team 1:1s, investor relationships, personal development]. Design a weekly template that blocks QII time before QIII fills the gaps. Include specific time blocks, daily themes if appropriate, and a system for protecting QII time from urgency creep. + +--- + +## Use Cases + +**Validation-Stage Solo Founder Drowning in Operational Tasks** +A solo founder building an MVP finds herself spending 70% of her time answering customer support emails (QIII), 20% on urgent bug fixes (QI), and 10% on actual product development (QII). The Eisenhower audit reveals that customer support -- while responsive and well-intentioned -- serves individual requests at the expense of building the product that would serve all customers. She implements three changes: a self-service FAQ that reduces support volume by 40%, a twice-daily email batching schedule, and a morning block of three protected hours for product work. Within a month, she has reclaimed 15 hours per week for QII. + +**Growth-Stage CEO Trapped in Meeting Culture** +A Series A CEO reviews his calendar and discovers 32 hours of meetings per week. The Eisenhower sort reveals: 8 hours are QI (board prep, customer escalations, hiring decisions), 6 hours are QII (strategic 1:1s with direct reports, investor relationship maintenance), 14 hours are QIII (status updates, informational meetings he attends but does not lead), and 4 hours are QIV (recurring meetings with no clear purpose). He eliminates the 4 QIV hours immediately, converts 8 of the QIII hours into asynchronous updates (Loom videos, written status reports), and delegates attendance at the remaining 6 QIII meetings to his chief of staff. The result: 18 hours reclaimed, with 6 redirected to QII strategic work. + +--- + +## Anti-Patterns + +1. **Treating everything as QI.** Founders who classify every task as urgent and important have not done the work of distinguishing between the two dimensions. If everything is QI, nothing is prioritized, and the matrix provides no value. The discipline is in the sorting, not in the framework itself. + +2. **Using the matrix once and filing it away.** The Eisenhower Matrix is a daily practice, not a quarterly exercise. Priorities shift constantly, and the matrix must be applied continuously -- ideally as a daily planning ritual -- to prevent QIII and QIV from colonizing the calendar. + +3. **Delegating without context or authority.** Moving tasks to QIII (delegate) requires actually delegating them, which means providing the necessary context, decision-making authority, and feedback mechanisms. Simply labeling something "delegable" and continuing to do it yourself defeats the purpose. + +4. **Confusing "not urgent" with "not now."** QII tasks are not urgent, but they are the most important tasks on the list. Treating "not urgent" as "defer indefinitely" ensures that QII work never happens. The framework requires active scheduling of QII work, not passive acknowledgment of its existence. + +5. **Ignoring the emotional pull of QIII.** Answering emails, attending meetings, and responding to requests feels productive. The dopamine hit of clearing an inbox is real. Founders must recognize that QIII activity provides psychological comfort at strategic cost. The discomfort of saying no to QIII is the price of QII progress. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal clarity | At the idea stage, the entrepreneur IS the company. The matrix serves as a personal discipline tool. QII activities: customer discovery, market research, building relationships with potential co-founders. The primary enemy is QIV disguised as "research." | +| Validation | Ruthless focus on experiments | QII narrows to activities that directly test the core hypothesis: customer interviews, prototype building, metrics design. QIII expands dangerously as advisors, accelerators, and networking events compete for time. | +| Early Traction | First delegation decisions | The team is growing, making QIII delegation possible for the first time. The founder's QII shifts toward hiring, culture-building, and system design -- activities that feel less "productive" than shipping features but are more valuable. | +| Growth | Organizational QII | The matrix expands from personal to organizational. Leadership must ensure the entire company invests in QII -- strategic planning, capability building, process improvement -- rather than running entirely in reactive mode. | +| Scale | Institutional time management | QII becomes the CEO's primary job: vision, culture, board management, strategic partnerships. Virtually all QI and QIII should be delegated. The CEO who is still fighting fires at scale has failed to build the organization. | + +--- + +## Output Template + +```markdown +# Weekly Eisenhower Matrix + +**Name:** [Your name] +**Week of:** [Date] +**Stage:** [Company stage] + +## Task Classification + +| Task | Quadrant | Action | Time Estimate | +|------|----------|--------|---------------| +| [Task] | QI - Do | [Immediate action] | [Hours] | +| [Task] | QII - Schedule | [When blocked] | [Hours] | +| [Task] | QIII - Delegate | [To whom] | [Hours saved] | +| [Task] | QIV - Eliminate | [Remove] | [Hours saved] | + +## Time Distribution + +| Quadrant | Current % | Target % | Gap | +|----------|----------|----------|-----| +| QI (Do) | [%] | 20-25% | [+/-] | +| QII (Schedule) | [%] | 40-50% | [+/-] | +| QIII (Delegate) | [%] | 15-20% | [+/-] | +| QIV (Eliminate) | [%] | 0-5% | [+/-] | + +## Protected QII Blocks This Week +- Monday: [Time] -- [QII Activity] +- Tuesday: [Time] -- [QII Activity] +- Wednesday: [Time] -- [QII Activity] +- Thursday: [Time] -- [QII Activity] +- Friday: [Time] -- [QII Activity] + +## Delegation Actions +- [Task] → [Person] by [Date] +- [Task] → [Person] by [Date] + +## QIV Eliminated +- [Activity removed and why] +``` + +--- + +## Related Skills + +- **[Covey's Seven Habits](../../content/skills/frameworks/covey-seven-habits.md)** -- Covey popularized the Eisenhower Matrix as Habit 3 ("Put First Things First") and embedded it in a broader framework of personal effectiveness that provides the character foundation for consistent use. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Continuous improvement is a Quadrant II activity by definition: important but never urgent, making the Eisenhower Matrix essential for protecting time for Kaizen practices. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Extends the Eisenhower principle from individual time management to company-wide strategic focus, ensuring organizational attention is distributed across all four perspectives. +- **[SMART Goals](../../content/skills/frameworks/smart-goals.md)** -- QII activities need specific, measurable goals to maintain their priority against the constant pull of urgent but unimportant demands. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Provides leadership-specific strategies for protecting strategic focus time and managing the competing demands that pull leaders away from QII work. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- The QIII delegation quadrant requires genuine delegation skills to execute effectively, including providing context, authority, and accountability. diff --git a/plugins/foreman/skills/emotional-courage/SKILL.md b/plugins/foreman/skills/emotional-courage/SKILL.md deleted file mode 120000 index 1123083..0000000 --- a/plugins/foreman/skills/emotional-courage/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/emotional-courage.md \ No newline at end of file diff --git a/plugins/foreman/skills/emotional-courage/SKILL.md b/plugins/foreman/skills/emotional-courage/SKILL.md new file mode 100644 index 0000000..93ef456 --- /dev/null +++ b/plugins/foreman/skills/emotional-courage/SKILL.md @@ -0,0 +1,204 @@ +--- +name: "emotional-courage" +description: "Builds the capacity for daily acts of leadership courage, from raising difficult issues and sharing vulnerability appropriately to channelling anxiety productively and taking principled stands. Provides incremental practices for developing courage as a skill rather than treating it as an innate trait. Use when avoiding a difficult conversation, feeling paralysed by anxiety before a high-stakes situation, sensing that you are holding back from necessary confrontation, wanting to build vulnerability into your leadership style without oversharing, or preparing to advocate for an unpopular position." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - courage + - vulnerability + - anxiety + - emotional-regulation + - difficult-conversations + - authenticity + - leadership-presence + - risk-taking +related_skills: + - emotional-intelligence + - radical-candor + - trust-equation + - psychological-safety + - learning-from-failure + - humility-and-power +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Emotional Courage + +Courage is not the absence of fear -- it is a muscle that atrophies without use. The spectrum runs from silence to recklessness, and most leaders cluster near the silent end, mistaking caution for wisdom. They do not raise the issue everyone knows exists. They do not challenge the senior executive whose strategy is failing. They do not tell the underperforming friend they hired that the friendship cannot substitute for results. These are not dramatic acts of whistleblowing or organisational martyrdom. They are small, daily decisions to feel the discomfort of honesty and act anyway. Maya Angelou described it precisely: courage is built by lifting five-pound bags before attempting the hundred-pound ones. The question is not whether a leader possesses courage but whether they are practising it. + +--- + +## The Framework + +### The Anatomy of Emotional Courage + +Emotional courage is the willingness to fully experience uncomfortable emotions -- fear, shame, anxiety, vulnerability -- in service of doing what leadership requires. It sits at the intersection of self-awareness and action. A leader who feels the fear but acts anyway is courageous. A leader who feels the fear and rationalises inaction is merely comfortable. + +Emotional courage is distinct from physical or intellectual courage. It does not require risking one's body or being the smartest person in the room. It requires risking emotional exposure: being seen as uncertain, being challenged, being wrong, being honest in a context where dishonesty is easier. + +### Practice 1: Open Up Without Oversharing + +The boundary between vulnerability and oversharing is the most frequently misjudged line in leadership communication. Employees benefit from feeling a personal connection to their leader, but excessive emotional disclosure undermines authority and burdens the team with the leader's unprocessed experience. + +**The calibration test:** Before sharing something personal, ask whether you would be comfortable hearing the same comment from your own boss. Telling the team you are in a bad mood because it has been a difficult day is transparent. Telling them you are in a bad mood because of a fight with your partner is oversharing. The first creates connection; the second creates discomfort. + +**The principle:** Share the emotional weather without narrating the storm. "I am frustrated by how this quarter has gone and I want to figure out what we do differently" is vulnerable and productive. "I barely slept last night worrying about whether we'll all have jobs next quarter" is honest but destructive. + +### Practice 2: Channel Anxiety as Leadership Fuel + +Anxiety is not a deficiency to be eliminated; it is a signal to be interpreted. It can deplete energy and drive poor decisions, but it can also sharpen attention, accelerate threat detection, and build tolerance for discomfort over time. + +**The channelling protocol:** + +1. **Notice the manifestation.** Physical symptoms (churning stomach, tight chest) and emotional ones (overwhelm, panic) are the first indicators. Most leaders suppress these signals rather than reading them. +2. **Name the trigger.** Anxiety without a named cause is more paralysing than anxiety with one. "I am anxious" is vague and overwhelming. "I am anxious because the board presentation has three unresolved data points" is specific and actionable. +3. **Pause before reacting.** The gap between stimulus and response is where courage lives. An anxious leader who fires off an urgent Slack message at 11 PM is not being responsive; they are being reactive. The pause creates space for a response that serves the situation rather than the anxiety. +4. **Track patterns over time.** A journal of anxiety triggers reveals which situations genuinely warrant concern and which are habitual overreactions. This data is the foundation for recalibrating one's emotional baseline. + +### Practice 3: Build Courage Incrementally + +The metaphor of progressive weight training applies directly. Leaders who attempt a hundred-pound act of courage -- confronting the CEO, whistleblowing, firing a founding team member -- without having practised five-pound acts will almost certainly fail or avoid the attempt entirely. + +**The incremental programme:** + +| Weight | Example Act | What It Builds | +|--------|------------|----------------| +| 5 lbs | Calling customer service and stating a complaint directly without hedging | Comfort with directness | +| 10 lbs | Giving honest feedback to a peer on a low-stakes project | Tolerance for interpersonal tension | +| 25 lbs | Raising a concern in a team meeting that no one else is voicing | Willingness to be the dissenter | +| 50 lbs | Having a difficult performance conversation with a direct report | Capacity to deliver unwelcome truth | +| 75 lbs | Pushing back on a senior leader's flawed strategy in a public setting | Ability to challenge authority constructively | +| 100 lbs | Taking a principled stand on an issue that could cost personal capital | Moral courage under genuine risk | + +The key insight is that each level builds the neural and emotional pathways for the next. A leader who has never practised directness with a customer service representative is unlikely to suddenly summon it in a boardroom. + +### Practice 4: Take Principled Stands -- Without Martyrdom + +Research reveals a more nuanced picture of workplace courage than the cultural narrative suggests. Most acts of courage do not come from outsiders or whistleblowers. They come from respected insiders at all levels who take action -- campaigning for a risky strategic move, pushing to change an unfair policy, speaking out against unethical behaviour -- because they believe it is the right thing to do. + +Their reputations and track records enable them to make more headway than those on the margins. And when they manage the process well, they do not necessarily pay a high price for their actions; indeed, their status may rise as they create positive change. + +The implication is practical: courage is more effective and less costly when exercised from a position of earned credibility. Building trust, demonstrating competence, and establishing reliability are not alternatives to courage -- they are preconditions for effective courage. + +### Practice 5: Patience as Quiet Courage + +Patience rarely appears in discussions of courage, but it belongs there. Staying calm during setbacks, waiting for a strategy to prove itself, resisting the pressure for immediate action when careful deliberation is warranted -- these are acts of courage in an environment that rewards speed above thoughtfulness. + +The always-on working world treats immediate replies and constant connectivity as virtues. Often, though, the most courageous act is to be methodical, careful, and slow -- to resist the anxiety-driven urge to "do something" when the best response is to think first. + +--- + +## Prompts + +**Prompt 1 -- Courage Inventory:** +> Help me identify where I am avoiding emotional courage in my leadership. My current situation includes [describe role, team, key challenges]. Ask me about conversations I have been postponing, issues I know exist but have not raised, feedback I have not delivered, and positions I have not taken. For each avoidance, help me identify the specific fear driving it and design a five-pound practice to start building the required courage. + +**Prompt 2 -- Vulnerability Calibration:** +> I want to be more open with my team but I am unsure where the line is between vulnerability and oversharing. Recent situations where I considered sharing something personal include [describe 2-3 examples]. For each, assess whether sharing would build connection or create discomfort, and explain why. Then help me develop guidelines for my specific context and role. + +**Prompt 3 -- Anxiety Channelling Plan:** +> I experience significant anxiety in [describe situations -- e.g., board presentations, difficult conversations, performance reviews]. My typical anxiety response includes [describe physical and emotional symptoms and how you currently cope]. Design an anxiety channelling protocol tailored to my triggers that helps me use the anxiety as information rather than succumbing to it. + +**Prompt 4 -- Principled Stand Preparation:** +> I need to take a stand on [describe the issue] which I believe is the right thing to do but which carries risk because [describe the potential cost]. Help me prepare by assessing my current credibility capital, identifying allies, crafting my argument in terms that appeal to shared values rather than personal conviction, and anticipating objections. Design the conversation or communication so that I can be courageous without being reckless. + +--- + +## Use Cases + +**Validation-Stage Founder Avoiding a Co-Founder Conversation** + +Two co-founders have not discussed the growing gap in their contributions. One works sixty hours per week; the other has taken a consulting engagement "on the side" that consumes most of their time. The engaged founder avoids the conversation because the other co-founder is a close friend and the potential conflict feels threatening to the relationship. Applying the incremental courage programme, the founder starts with a five-pound practice: being direct with a vendor about an unsatisfactory deliverable. Then a ten-pound practice: giving honest feedback to an advisor. By the time the co-founder conversation arrives, the founder has built enough comfort with directness to say: "We need to talk about whether we are both still fully committed to this, and what it means if we are not." The conversation is uncomfortable. The outcome -- a revised equity split and renewed commitment -- is better than six more months of avoidance. + +**Growth-Stage Manager Channelling Pre-Meeting Anxiety** + +A director of engineering experiences debilitating anxiety before every executive leadership meeting. The anxiety manifests as over-preparation (spending eight hours on a fifteen-minute update), physical symptoms (insomnia the night before), and avoidance (delegating attendance to a subordinate when possible). Applying the channelling protocol, the director begins naming triggers: the anxiety is not about the meeting itself but about a specific executive who asks adversarial questions. With the trigger named, the preparation shifts from comprehensive coverage of every possible question to focused preparation for the three most likely adversarial questions. The anxiety decreases from paralysing to productive, and the director's meeting performance improves because the preparation is targeted rather than exhaustive. + +**Scale-Stage VP Taking a Stand on a Flawed Strategy** + +A VP of Customer Success becomes convinced that the company's aggressive upsell strategy is increasing short-term revenue at the cost of long-term customer health. Churn data supports the concern, but the Chief Revenue Officer is politically powerful and personally invested in the strategy. The VP assesses their credibility capital (strong track record, respected by the CEO, well-liked by the sales team) and designs the approach: presenting churn trend data in a private meeting with the CEO, framing the concern in terms of customer lifetime value rather than as a criticism of the CRO, and proposing a pilot programme that tests a relationship-first approach with a subset of accounts. The CEO authorises the pilot. Within two quarters, the pilot accounts show 40% lower churn. The strategy shifts -- not because the VP was a martyr, but because they were a credible insider who managed the process well. + +--- + +## Anti-Patterns + +1. **Confusing courage with confrontation.** Courage is not the willingness to fight; it is the willingness to feel. A leader who picks fights is not courageous -- they may simply be unable to tolerate the discomfort of unresolved tension. Genuine courage sometimes looks like patience, sometimes like vulnerability, and only occasionally like confrontation. + +2. **Performing vulnerability for strategic gain.** Sharing personal struggles because it is "what authentic leaders do" rather than because it serves the team's needs. Calculated vulnerability is detectable and produces the opposite of its intended effect: it increases perceived self-orientation rather than building connection. + +3. **Attempting hundred-pound acts without practice.** Confronting the CEO about a strategic failure without ever having practised giving direct feedback in low-stakes situations. The resulting fumble -- too aggressive, too tentative, too emotional -- reinforces the avoidance it was meant to overcome. + +4. **Treating anxiety as a problem to solve rather than a signal to read.** Medicating, suppressing, or ignoring anxiety rather than understanding what it is communicating. Anxiety that persistently attaches to a specific situation or person is often surfacing a genuine problem that deserves attention. + +5. **Assuming courage requires martyrdom.** The belief that taking a stand must cost something -- that if it was easy, it was not courageous. Research suggests otherwise: well-managed acts of courage by credible insiders frequently enhance rather than diminish the person's standing. The martyrdom assumption prevents many leaders from even attempting the courageous act. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Co-founder and early team conversations | The relationships are personal, the stakes are existential, and the avoidance patterns are hardest to break because friendship and business are intertwined. | +| Early Traction | Setting courage norms for the first team | The leader's willingness to raise difficult issues, share appropriate vulnerability, and welcome dissent establishes the cultural template for every future hire. | +| Growth | Courage across organisational boundaries | Taking stands with peer leaders, challenging cross-functional decisions, and raising issues that span departmental politics require courage exercised in more complex relational landscapes. | +| Scale | Institutional courage | The leader must create systems -- anonymous feedback channels, skip-level meetings, structured dissent processes -- that enable courage at scale rather than depending on individual heroism. | + +--- + +## Output Template + +```markdown +# Emotional Courage Development Plan + +## Courage Avoidance Inventory +| Situation I Am Avoiding | Specific Fear | Cost of Continued Avoidance | Courage Weight (5-100 lbs) | +|------------------------|---------------|---------------------------|---------------------------| +| [Situation 1] | [Fear] | [What avoidance costs] | [Weight] | +| [Situation 2] | [Fear] | [What avoidance costs] | [Weight] | + +## Incremental Practice Plan +| Week | Practice Act | Weight | What I Will Feel | How I Will Respond | +|------|------------|--------|-----------------|-------------------| +| 1 | [Specific low-stakes act] | [5-10 lbs] | [Expected discomfort] | [Planned response] | +| 2 | [Slightly higher-stakes act] | [10-25 lbs] | [Expected discomfort] | [Planned response] | +| 3 | [Medium-stakes act] | [25-50 lbs] | [Expected discomfort] | [Planned response] | +| 4 | [The act I have been avoiding] | [Actual weight] | [Expected discomfort] | [Planned response] | + +## Vulnerability Guidelines (My Context) +- **Safe to share:** [Types of personal information that build connection] +- **Boundary:** [Types of personal information that burden the team] +- **Test:** [My personal calibration question before sharing] + +## Anxiety Map +| Trigger | Physical Signal | Emotional Signal | Named Cause | Productive Response | +|---------|----------------|-----------------|-------------|-------------------| +| [Trigger 1] | [Symptom] | [Feeling] | [Specific cause] | [Channelled response] | +| [Trigger 2] | [Symptom] | [Feeling] | [Specific cause] | [Channelled response] | + +## Principled Stand Preparation (If Applicable) +- **The issue:** [What needs to be said or done] +- **My credibility capital:** [Track record, relationships, standing] +- **Allies:** [Who shares this concern] +- **Framing:** [How to present in terms of shared values] +- **Contingency:** [If it goes badly, what is my fallback] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness is the foundation upon which emotional courage is built; without the ability to name and understand one's emotions, courage becomes recklessness. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- The "challenge directly" dimension of radical candor is a daily expression of emotional courage; the framework provides structure for courageous conversations. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Emotional courage in a leader creates psychological safety for the team; the two are causally linked. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Sharing failures authentically is one of the most common and valuable expressions of emotional courage. +- **[Humility and Power](../../content/skills/leadership/humility-and-power.md)** -- Acknowledging weakness requires emotional courage; humility and courage are complementary disciplines, not opposing ones. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- The Stoic Inner Citadel concept provides the philosophical foundation for building the endurance that progressive courage training develops behaviourally. diff --git a/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md b/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md deleted file mode 120000 index 71822c9..0000000 --- a/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/emotional-impact-in-stories.md \ No newline at end of file diff --git a/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md b/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md new file mode 100644 index 0000000..a7e9692 --- /dev/null +++ b/plugins/foreman/skills/emotional-impact-in-stories/SKILL.md @@ -0,0 +1,232 @@ +--- +name: "emotional-impact-in-stories" +description: "Explains the singular mechanism for making audiences cry (surprise, not sadness) and two named techniques for making them laugh (Milk Cans and Baseballs, Babies and Blenders). Applies when a founder is crafting a keynote, investor narrative, brand story, or any communication designed to move an audience emotionally. Use when a story feels informative but flat, when humour falls short, or when a narrative needs to land in the heart rather than the head." +version: "1.0.0" +category: "storytelling" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - emotion + - surprise + - humour + - crying + - laughter + - milk-cans-and-baseballs + - babies-and-blenders + - contrast + - pitching + - brand-narrative +related_skills: + - building-story-stakes + - storytelling-truth-and-vividness + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Emotional Impact in Stories + +There is exactly one way to make someone cry -- and it is not sadness. It is surprise. The framework argues this with the conviction of a principle tested in front of thousands of audiences: tears are not produced by tragic content. They are produced by unexpected reveals, unanticipated connections, and the sudden inversion of the emotional expectation the storyteller has carefully constructed. The same principle governs laughter. Every emotional response in storytelling -- tears, anger, joy, outrage -- traces back to a well-cultivated surprise. The entrepreneur who understands this mechanism holds a tool more powerful than any slide deck: the ability to make a room feel something it did not expect to feel. + +--- + +## The Framework + +### Part I: The Mechanics of Tears + +In life, many things provoke tears: grief, pain, overwhelming love, exhaustion. Storytellers have access to none of these. They cannot cause physical pain or recreate years of accumulated loss. All they have is words, deployed in sequence. The only emotional lever available is surprise. + +The principle is demonstrated through the story "This Is Going to Suck," in which the storyteller dies briefly after a head-on collision. Audiences wince at the violence. They groan at the description of teeth knocked loose and legs embedded in metal. But nobody cries at the accident. Despite its brutality, the collision is expected -- the audience was told it was coming. + +They cry later, when they learn that teenage friends have filled the hospital waiting room. This is the surprise. It was hidden, planted, and detonated at the precise moment of maximum contrast. + +**Three strategies make surprise work:** + +**1. Build one expectation, then deliver a different (deeper) one.** + +The emotional architecture is misdirection. Construct a world in which the audience believes they know what the story is about. Then reveal that the story was always about something else. This is called changing the colour of the Elephant -- the audience thought they were tracking one question, and the answer to a different, more profound question arrives instead. + +In entrepreneurial contexts: the pitch that appears to be about a product feature turns out to be about the founder's child. The customer case study that appears to be about efficiency gains turns out to be about a warehouse worker's dignity. The deeper layer, arriving unexpectedly, is what produces the response. + +**2. Heighten contrast immediately before the surprise.** + +The moment before the surprise should be as emotionally distant from it as possible. The story paints a picture-postcard winter scene -- snow falling on lawns, hope for a good Christmas -- seconds before a collision destroys everything. The beauty amplifies the horror. It describes isolation and abandonment in an emergency room -- no one knows his name, his parents chose to check the car first -- before revealing that friends have arrived. + +The principle is universal: laugh before cry, hope before loss, darkness before light. Contrast is the amplifier. + +**3. Hide the critical information.** + +If the audience sees the surprise coming, it ceases to be a surprise. Two techniques preserve it: + +- **Hiding the bomb in the clutter.** Embed the critical detail among other details of apparently equal importance. The request for a nurse to call McDonald's -- the fact that triggers the entire climactic sequence -- is buried in a list of medical procedures. It looks like just another thing happening in an emergency room. It is, in fact, the most important sentence in the story. + +- **Camouflaging with laughter.** Attach a laugh line to the critical detail. The audience attributes the moment to the storyteller's sense of humour, not to narrative engineering. "I was dead twenty minutes ago and now I'm worried about work, but that drive-through does not run well without me." The laugh obscures the bomb. + +**What ruins surprise:** + +- **Thesis statements.** "This is a story about a time my friends became my family." The surprise is dead on arrival. Storytelling is the reverse of the five-paragraph essay. Evidence first, thesis last -- if at all. + +- **Failing to use stakes.** The Backpack, Breadcrumbs, and Hourglass from the stakes framework exist in part to amplify surprise. A plan that is articulated in detail and then fails is more surprising than a plan that fails without setup. Stakes and surprise are symbiotic. + +- **Revealing too early.** Placing the important detail near the payoff, where the audience can connect the dots. Distance is an ally. Plant the bomb early. Detonate it late. + +### Part II: The Mechanics of Laughter + +The framework is candid: it cannot make a person funny. Humour involves wit, timing, tonality, confidence, and a relationship with language that resists systematic instruction. What it can do -- and what this framework addresses -- is help a storyteller add humour to a story through structural technique, even if the storyteller is not naturally amusing. + +Two named methods cover the vast majority of story-based humour: + +#### Milk Cans and a Baseball + +The name derives from the carnival game: stack metallic milk cans in a tower, then knock them down with a ball. In comedy, this is setup and punchline. The milk cans are the setup; the ball is the punchline. + +The rule: **save the funniest word for last.** The instinct of most people is to say the funny thing first, because they are excited about it. This ruins the laugh. The tower of expectations must be built before the ball is thrown. + +Consider the example: "I sleep in a pantry off their kitchen that they've converted into a tiny bedroom. I share this room with a Jehovah's Witness named Rick, a guy who speaks in tongues in his sleep, and the family's indoor pet goat." + +The word *goat* is last because it is the most unexpected. The milk cans -- Jehovah's Witnesses, pantry, tiny bedroom, Rick, speaking in tongues, in his sleep, indoor, pet -- build a tower of increasingly unusual details. Each one recalibrates the audience's expectations. Then *goat* demolishes them. + +**Specificity is funny.** "Pouring water over Raisin Bran because I am too stupid and lazy to buy milk" is funnier than "pouring water over cereal." Oddly specific words generate laughs that generic ones cannot. Some words are inherently amusing -- the well-documented comedic potency of the hard K sound bears this out. The choice of *Pop-Tarts* over *crackers* is deliberate. + +#### Babies and Blenders + +When two things that rarely or never go together are pushed together, humour often results. The framework calls this Babies and Blenders -- the juxtaposition of the innocent and the incongruous. + +Calling a three-year-old boy "a little asshole" after describing him as sweet and angelic gets a laugh because the two categories should not occupy the same sentence. Referring to a grandmother as "a sadist" is funny precisely because the words grandmother and sadist have never been introduced to each other. + +The technique extends to lists. A storyteller creates a sequence of three items, the third of which is categorically unlike the first two: "Zimmers, pineapple-flavoured ham, and despair." The pattern established by the first two items is broken by the third. The break is the surprise. The surprise is the laugh. + +**Exaggeration** is a subspecies of Babies and Blenders: an unreasonable description pushed against something that does not normally accommodate it. "A Christmas tree seven feet wide and three feet tall." The audience knows the dimensions are false, which is why it works. If the exaggeration is presented as fact, it is no longer exaggeration; it is lying. + +### The Strategic Use of Humour in Stories + +Humour is not the goal of storytelling. Heart is the goal. Humour serves four strategic functions: + +1. **Opening laugh.** A laugh in the first thirty seconds signals competence, claims the floor, and reassures the audience that the storyteller is okay -- whatever darkness follows, it is in the past. + +2. **Laugh before the blow.** Placing humour immediately before a painful moment heightens the contrast. "I like to make people laugh before making them cry, because it hurts more that way," as the text puts it. + +3. **Breath after tension.** Following an intense sequence with a laugh allows the audience to reset. Sustained tension without relief becomes numbing. + +4. **Camouflage.** A laugh line draws attention away from a critical detail that must be hidden for a later surprise. + +Stories must end on heart, not on humour. The final sentences should be moving, vulnerable, or universally connecting. Laughs belong in the middle, carrying the audience forward. The landing must be something bigger. + +--- + +## Prompts + +**Prompt 1 -- Surprise Architecture:** +> Here is a story I plan to tell: [paste narrative]. Identify the moment that should produce the strongest emotional response. Then help me restructure the narrative so that (a) a contrasting emotional expectation is built before that moment, (b) the critical information enabling the surprise is hidden earlier in the story using clutter or comedic camouflage, and (c) no thesis statement gives the surprise away. + +**Prompt 2 -- Humour Injection (Milk Cans and Baseballs):** +> Here is a passage from my story that is situationally funny but not landing as hard as it could: [paste passage]. Restructure it using the Milk Cans and a Baseball technique. Identify the funniest word or phrase and move it to the end. Build a tower of increasingly specific and unexpected details before it. Suggest oddly specific words to replace generic ones. + +**Prompt 3 -- Emotional Journey Map:** +> I am delivering a [pitch / keynote / all-hands address / customer story] and I want the audience to experience at least three distinct emotional states. Map out an emotional journey for the narrative: where should the audience laugh, where should they feel tension, where should they feel moved? Place each humour moment strategically (opening signal, pre-blow contrast, post-tension breath, or camouflage). + +**Prompt 4 -- Babies and Blenders Audit:** +> Review this narrative for opportunities to use the Babies and Blenders technique: [paste]. Identify moments where two incongruous elements can be pushed together for comedic effect. Suggest list-of-three constructions where the third item breaks the pattern established by the first two. Ensure that all humour serves the story rather than undermining its emotional destination. + +--- + +## Use Cases + +**Brand Keynote -- Consumer Health Startup** + +A founder delivers a keynote about chronic disease management. The narrative is earnest and informative but produces no emotional response. Applying the framework: the surprise is restructured. The story appears to be about technology (the Elephant) but is revealed to be about a patient's relationship with her daughter. The critical detail -- that the daughter programmed the app herself, at age fourteen -- is hidden in a list of beta testers and camouflaged with a laugh line about the daughter's feedback being "more brutal than any venture capitalist's." The audience expects admiration for the technology. They get admiration for a child's love. The keynote ends not on metrics but on the sentence the daughter said to her mother when the app worked for the first time. The room is silent. Then it is not. + +**Investor Update -- Series B SaaS Company** + +A CEO sends a quarterly investor letter that typically reads as a dashboard with commentary. Applying the emotional impact framework: the letter opens with a laugh (Milk Cans and a Baseball -- the CEO describes the office's new espresso machine as "the only piece of equipment with a higher utilisation rate than our production servers, and better uptime"). The critical surprise -- that the company's largest competitor has begun referring customers to them -- is hidden in a paragraph about partnership strategy, camouflaged by a self-deprecating aside. The surprise lands three paragraphs later when the CEO reveals the competitor's CEO called personally. The letter ends on heart: a single sentence from a customer support ticket that captures what the product means to the people who use it. + +**Team Retrospective -- After a Failed Product Launch** + +A product lead tells the story of a feature launch that missed its targets. The instinct is to present the failure analytically, with charts. Applying the framework: the story is restructured to produce emotional engagement. Babies and Blenders opens the narrative ("We planned this launch for four months and executed it with the precision of a marching band and the market awareness of a goldfish"). The surprise is not the failure itself -- everyone in the room already knows the numbers -- but a piece of customer feedback received during the post-mortem that reframed what the team had actually built. The laugh before the blow comes immediately before the customer's words are read aloud. The story ends not on the failure but on what the team now understands about its customers that it did not understand before. + +--- + +## Anti-Patterns + +- **Confusing sadness with emotional impact.** A story saturated in tragedy does not automatically move an audience. It numbs them. Emotional impact requires surprise, which requires contrast, which requires the story to not be uniformly dark. The founder who opens with devastation and ends with devastation has given the audience nowhere to travel. + +- **Putting the funny word first.** The most common humour failure in storytelling. The speaker leads with the punchline because they cannot wait to get to it, then wonders why the room did not laugh. Milk Cans and a Baseball demands patience: build the tower, then throw the ball. Not the reverse. + +- **Using humour as the destination.** Ending a story on a joke, a pun, or a clever turn of phrase. The audience laughs and then forgets. Heart is what lingers. Laughter is a vehicle, not a destination. The final sentences must land somewhere vulnerable, meaningful, or universally true. + +- **Telegraphing the surprise with a thesis statement.** "This is a story about how our customers became our family." Every emotional beat that follows is pre-digested. The audience cannot be surprised by something they were told at the outset. Evidence first. Thesis never -- or thesis last and understated. + +- **Hiding nothing.** Telling the story in strict chronological order with every important detail flagged as important. The audience connects the dots before the storyteller detonates the surprise. Critical information must be planted early, buried in clutter, and camouflaged by laughter. The gap between planting and payoff is the space where surprise grows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Surprise must compensate for the absence of proof | The emotional payload is the founder's personal connection to the problem -- hidden, then revealed | +| Validation | Laughter builds rapport in early customer and investor conversations | Babies and Blenders can disarm scepticism; the incongruity of a scrappy team tackling a massive problem is inherently funny if framed correctly | +| Early Traction | Real customer stories provide the raw material for surprise | The critical detail to hide is often the customer's own words -- plant them early, detonate them at the close | +| Growth | Internal storytelling (all-hands, retrospectives) requires emotional range | Teams fatigued by metrics need stories that make them laugh and then remind them why the work matters | +| Scale | Surprise becomes harder as company narratives calcify | The greatest emotional impact at scale comes from revealing something the audience assumed they already knew about the company -- and showing them they were wrong | + +At the idea stage, the founder's own biography is often the richest source of surprise. The audience expects a pitch about a market opportunity; the founder reveals a deeply personal reason for caring. The mismatch between expectation and reality is the mechanism. At scale, the mechanism is the same, but the source shifts: the surprise comes from customer stories, employee stories, or data that contradicts the company's own assumptions. + +--- + +## Output Template + +```markdown +# Emotional Impact Design + +## Story / Narrative +[One-sentence summary] + +## Target Emotional Response +[What should the audience feel at the climax? Tears, laughter, awe, resolve?] + +## Surprise Architecture +- **Apparent story:** [What the audience believes the story is about] +- **Actual story:** [What the story is really about -- revealed at the end] +- **Contrast built before surprise:** [The emotional state the audience is in immediately before the reveal] +- **Critical detail hidden:** [The bomb -- what it is, where it is planted, how it is camouflaged] + +## Humour Placement +| Moment | Technique | Strategic Purpose | +|--------|-----------|-------------------| +| [Opening] | [Milk Cans / Babies & Blenders / other] | [Signal competence / claim floor / reassure] | +| [Before blow] | [Technique] | [Heighten contrast] | +| [After tension] | [Technique] | [Allow breath / reset] | +| [Near hidden detail] | [Technique] | [Camouflage critical information] | + +## Milk Cans and a Baseball (if applicable) +- **Tower (setup details in order):** [List each milk can] +- **Ball (funniest word, said last):** [The punchline word] + +## Babies and Blenders (if applicable) +- **Element A (expected):** [The normal thing] +- **Element B (incongruous):** [The unexpected pairing] + +## Landing (Final Sentences) +[Heart, not humour. What is the vulnerable, meaningful, or universally true statement the story ends on?] +``` + +--- + +## Related Skills + +- **[Building Story Stakes](../../content/skills/storytelling/building-story-stakes.md)** -- Stakes create the tension that surprise releases; the Backpack and Hourglass techniques are direct amplifiers of emotional impact. +- **[Storytelling Truth and Vividness](../../content/skills/storytelling/storytelling-truth-and-vividness.md)** -- Cinema of the Mind ensures the audience can see the scene where the surprise detonates; a surprise delivered in a locationless void is a thesis statement in disguise. +- **[Story Performance and Delivery](../../content/skills/storytelling/story-performance-and-delivery.md)** -- Timing, tense shifts, and vocal control determine whether a Milk Cans tower lands or collapses; performance is where structural humour becomes actual laughter. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Leaders must calibrate emotional impact for context: a board meeting and an all-hands address demand different emotional registers. +- **[What Is a Story](../../content/skills/storytelling/what-is-a-story.md)** -- The transformation requirement defines what kind of emotional impact is possible; only genuine change in the storyteller produces genuine feeling in the audience. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- The cognitive science of how audiences process information explains why surprise works: it violates established expectations, forcing deeper processing and stronger emotional encoding. diff --git a/plugins/foreman/skills/emotional-intelligence/SKILL.md b/plugins/foreman/skills/emotional-intelligence/SKILL.md deleted file mode 120000 index e0054e5..0000000 --- a/plugins/foreman/skills/emotional-intelligence/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/emotional-intelligence.md \ No newline at end of file diff --git a/plugins/foreman/skills/emotional-intelligence/SKILL.md b/plugins/foreman/skills/emotional-intelligence/SKILL.md new file mode 100644 index 0000000..6e0cb33 --- /dev/null +++ b/plugins/foreman/skills/emotional-intelligence/SKILL.md @@ -0,0 +1,198 @@ +--- +name: "emotional-intelligence" +description: "Assesses and develops leadership emotional intelligence using Goleman's five-domain EQ framework: Self-Awareness, Self-Regulation, Motivation, Empathy, and Social Skill. Diagnoses interpersonal conflicts, evaluates team EQ profiles, and builds development plans for emotional competencies. Use when resolving co-founder tensions, preparing for high-stakes investor meetings, scaling team culture, diagnosing declining employee engagement, or developing the relational leadership skills that differentiate outstanding from average leaders." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - self-awareness + - empathy + - team-dynamics + - interpersonal-skills +related_skills: + - thinking-fast-and-slow + - psychological-safety + - johari-window + - myers-briggs-type-indicator +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Emotional Intelligence + +Ninety percent of the difference between outstanding and average leaders is attributable not to cognitive ability but to emotional competencies. That finding, drawn from research across 188 companies by Daniel Goleman and reported in the Harvard Business Review, upended a century of assumptions about what makes leaders effective. IQ and technical expertise, Goleman demonstrated, are threshold capabilities -- necessary for entry but insufficient for distinction. The differentiator is emotional intelligence: the capacity to recognise, understand, manage, and effectively deploy emotions in oneself and others. For entrepreneurs, who operate in environments saturated with uncertainty, conflict, and high-pressure interpersonal dynamics, EQ is not a soft supplement to strategy. It is the substrate on which every relationship -- with co-founders, investors, employees, and customers -- either flourishes or fractures. + +--- + +## The Framework + +Goleman's model of emotional intelligence comprises five domains, each containing specific learnable competencies. Unlike IQ, which remains relatively stable across a lifetime, EQ is developable. The brain's emotional circuitry exhibits significant neuroplasticity well into adulthood, meaning these competencies respond to deliberate practice. + +### The Five Domains + +**1. Self-Awareness** + +The foundation upon which all other domains depend. Self-awareness is the ability to recognise one's own emotional states, understand their triggers, and assess their impact on thought and behaviour. Entrepreneurs with high self-awareness can distinguish between gut instinct grounded in pattern recognition and gut instinct distorted by anxiety, ego, or fatigue. + +Key competencies: +- Emotional self-awareness -- recognising emotions as they arise +- Accurate self-assessment -- knowing one's strengths and limitations +- Self-confidence -- grounded certainty about one's capabilities and values + +**2. Self-Regulation** + +The ability to manage disruptive emotions rather than being managed by them. Self-regulation does not mean suppression -- it means choosing how and when to express emotions constructively. Founders who self-regulate can absorb bad news without spiralling, receive criticism without retaliating, and maintain composure in negotiations where losing emotional control means losing leverage. + +Key competencies: +- Self-control -- keeping disruptive impulses in check +- Trustworthiness -- maintaining integrity and consistency +- Adaptability -- flexibility in handling change +- Innovation openness -- comfort with novel ideas and approaches + +**3. Motivation** + +Goleman distinguishes between extrinsic motivation (money, status, external validation) and intrinsic motivation (achievement drive, commitment to goals beyond the self, optimism in the face of setbacks). The most effective leaders are driven by something beyond personal gain, and this orientation is perceptible to the people they lead. Teams can detect performative purpose from genuine commitment with remarkable accuracy. + +Key competencies: +- Achievement drive -- striving to improve against a standard of excellence +- Commitment -- aligning with the goals of the organisation +- Initiative -- readiness to act on opportunities +- Optimism -- persistence in pursuing goals despite obstacles + +**4. Empathy** + +The ability to sense what others are feeling without them needing to articulate it. Empathy in a business context is not therapeutic -- it is informational. A founder with strong empathy reads the room: senses investor scepticism before it is voiced, detects employee disengagement before it becomes attrition, and anticipates customer frustration before it becomes churn. + +Key competencies: +- Understanding others -- sensing feelings and perspectives +- Developing others -- bolstering others' abilities +- Service orientation -- anticipating, recognising, and meeting needs +- Leveraging diversity -- cultivating opportunity through diverse perspectives +- Political awareness -- reading group emotional currents and power relationships + +**5. Social Skill** + +The application layer. Social skill is the ability to move people in desired directions -- to persuade, lead, negotiate, build bonds, and catalyse collaboration. It depends on all four preceding domains: one cannot influence others effectively without understanding oneself (self-awareness), managing one's own reactions (self-regulation), bringing genuine energy (motivation), and reading the other party accurately (empathy). + +Key competencies: +- Influence -- wielding effective persuasion tactics +- Communication -- listening openly and sending convincing messages +- Conflict management -- negotiating and resolving disagreements +- Leadership -- inspiring and guiding individuals and groups +- Collaboration -- working with others toward shared goals + +### The EQ-Performance Link + +Goleman's research across multiple industries found that EQ competencies accounted for 67% of the abilities necessary for superior performance in leadership roles -- and mattered twice as much as technical skill and IQ combined. The effect is non-linear: marginal improvements in EQ at the leadership level produce disproportionate improvements in organisational outcomes because leaders set the emotional tone for entire teams. + +--- + +## Prompts + +**Prompt 1 -- Personal EQ Assessment:** +> Based on the following self-description and recent interactions with my team, assess my likely strengths and development areas across Goleman's five EQ domains (self-awareness, self-regulation, motivation, empathy, social skill). Self-description: [describe your leadership style, recent conflicts, feedback received]. For each domain, rate my apparent level (developing / competent / strong) and suggest one specific practice I can begin this week to strengthen my weakest area. + +**Prompt 2 -- Conflict Diagnosis:** +> Analyse this interpersonal conflict through the lens of emotional intelligence: [describe situation -- parties involved, what happened, emotional reactions, current state]. Identify which EQ competencies each party is demonstrating or lacking. Recommend a resolution approach that addresses the emotional dynamics, not just the surface-level disagreement. Script the opening 3 sentences I should use to re-engage the other party. + +**Prompt 3 -- Team EQ Audit:** +> Evaluate the emotional intelligence profile of my leadership team based on these behavioural observations: [describe each team member's typical reactions to pressure, conflict, feedback, and collaboration]. Map each person to their likely EQ strengths and gaps. Identify the team-level blind spots (e.g., "the team is collectively strong on achievement drive but weak on empathy") and recommend team practices or rituals that would address these gaps. + +**Prompt 4 -- Investor Meeting Preparation:** +> I have a [funding round] meeting with [investor name/type] tomorrow. Based on what I know about them: [any background]. Help me prepare an emotionally intelligent approach: (a) likely emotional dynamics in the room, (b) how to read and respond to scepticism signals, (c) how to manage my own anxiety without suppressing authentic enthusiasm, and (d) how to close the meeting in a way that builds relationship regardless of the outcome. + +--- + +## Use Cases + +**Co-founder conflict at early traction** + +Two co-founders of a health-tech startup have escalating disagreements about product direction. The technical co-founder pushes for feature completeness before launch; the commercial co-founder wants to ship a minimum viable product immediately. Both frame the disagreement as strategic, but the underlying dynamic is emotional: the CTO fears public failure (self-regulation deficit under pressure), while the CEO fears missing the market window (anxiety masquerading as urgency). Applying Goleman's framework, they engage a coach who helps each founder articulate the emotion beneath the position. Once acknowledged, the technical co-founder agrees to a phased launch with clear quality thresholds, and the commercial co-founder agrees to delay by three weeks. The strategic compromise was always available -- the emotional blockage was what prevented them from finding it. + +**Scaling a team from 15 to 60 at growth stage** + +A fintech founder who personally hired and managed the first 15 employees struggles as the company scales to 60. She notices declining engagement, increasing turnover among mid-level managers, and a sense that the culture is "diluting." Diagnosis through the EQ lens reveals that her leadership style -- which worked brilliantly at 15 people through direct empathy and personal connection -- does not scale without structural support. She lacks the social skill competency of "developing others" at the management layer. The intervention involves training her direct reports in EQ competencies, establishing regular one-on-one rituals that cascade empathic leadership through layers, and creating feedback mechanisms that give her visibility into emotional dynamics she can no longer observe directly. + +--- + +## Anti-Patterns + +**1. Treating EQ as manipulation technology.** The most corrosive misapplication of emotional intelligence is using it to manage others' emotions for personal advantage while bypassing genuine self-awareness. This produces charismatic but ultimately untrustworthy leaders. Goleman's framework is predicated on authenticity -- the domains build on each other, and social skill without self-awareness is manipulation. + +**2. Confusing empathy with agreement.** Empathy means understanding another person's emotional state and perspective. It does not mean endorsing their position or abandoning one's own. Founders sometimes conflate the two, either avoiding necessary confrontations because they empathise with the other party's discomfort, or dismissing empathy entirely because they equate it with weakness. Strong empathy enables harder conversations, not softer ones. + +**3. Using EQ language to pathologise disagreement.** Labelling a colleague as "emotionally unintelligent" because they disagree forcefully is a form of intellectual dishonesty. Passionate advocacy is not an EQ deficit. The question is whether the person can modulate their approach based on context, not whether they suppress strong feelings entirely. + +**4. Neglecting that EQ is culturally mediated.** The expression and interpretation of emotions varies significantly across cultures. What reads as confident self-assurance in one cultural context may register as arrogance in another. Founders building global teams must calibrate their EQ practice to cultural norms rather than assuming a single standard. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder dynamics, early hires | EQ is exercised directly and personally; the founder IS the culture | +| Growth | Management layer, culture scaling | EQ must be systematised -- built into hiring criteria, management training, and feedback loops | +| Scale | Board relationships, M&A, crisis leadership | EQ operates at institutional level; the founder must influence through others and manage stakeholders with competing emotional agendas | + +At early traction, the founder's personal EQ is the company's EQ. Every hiring decision, every customer interaction, every investor conversation is coloured by the founder's emotional competencies. The leverage point is self-awareness: a founder who understands their own emotional patterns can consciously compensate for them. + +At growth, the challenge transforms. The founder can no longer personally set the emotional tone for every team. EQ must become organisational: embedded in hiring criteria (screening for empathy and self-regulation), management practices (regular feedback, active listening protocols), and cultural rituals (how the company handles failure, celebrates success, resolves conflict). + +At scale, emotional intelligence becomes a governance capability. Board dynamics, investor relations, regulatory negotiations, and crisis communications all demand the highest order of Goleman's social skill domain -- the ability to manage complex multi-party emotional dynamics where the stakes are existential. + +--- + +## Output Template + +```markdown +# Emotional Intelligence Assessment -- [Team/Leader Name] + +**Prepared for:** [Team / Individual] +**Date:** [Date] +**Assessment context:** [Trigger -- e.g., team conflict, scaling challenges, leadership development] + +## Individual EQ Profile + +| Domain | Current Level | Key Evidence | Development Priority | +|--------|--------------|--------------|---------------------| +| Self-Awareness | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Self-Regulation | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Motivation | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Empathy | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | +| Social Skill | [Developing/Competent/Strong] | [Observed behaviours] | [Specific practice] | + +## Team-Level Patterns +- **Collective strength:** [Domain where the team is strongest] +- **Collective blind spot:** [Domain where the team is weakest] +- **Highest-impact intervention:** [One practice that would shift the team dynamic] + +## 30-Day Development Plan +1. **Week 1-2:** [Specific action targeting highest-priority domain] +2. **Week 3-4:** [Follow-up action and reflection practice] + +## Relationship Map +[Key relationships that require EQ attention, with specific approach for each] + +| Relationship | Current Dynamic | EQ Lever | Recommended Approach | +|-------------|----------------|----------|---------------------| +| [Person/Group] | [Description] | [Which EQ domain] | [Specific action] | +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's System 1 is driven by emotional processing; EQ provides the self-awareness to recognise when fast thinking is emotionally compromised. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework describes the team-level conditions that require leaders with high EQ to establish and maintain. +- **[Johari Window](../../content/skills/frameworks/johari-window.md)** -- The Johari model operationalises the self-awareness domain of EQ by mapping known and unknown aspects of self and others. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Scott's "care personally, challenge directly" formula requires high EQ in both empathy (caring) and social skill (challenging) to execute without damage. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- Provides ancient practical techniques for the self-regulation domain of EQ, teaching how to observe and manage emotional responses rather than be controlled by them. +- **[Reading People](../../content/skills/people/reading-people.md)** -- Extends the empathy domain into practical observation techniques for reading emotional states, intentions, and unspoken dynamics in professional interactions. diff --git a/plugins/foreman/skills/employee-engagement-retention/SKILL.md b/plugins/foreman/skills/employee-engagement-retention/SKILL.md deleted file mode 120000 index aa4d00c..0000000 --- a/plugins/foreman/skills/employee-engagement-retention/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/employee-engagement-retention.md \ No newline at end of file diff --git a/plugins/foreman/skills/employee-engagement-retention/SKILL.md b/plugins/foreman/skills/employee-engagement-retention/SKILL.md new file mode 100644 index 0000000..c72c6f6 --- /dev/null +++ b/plugins/foreman/skills/employee-engagement-retention/SKILL.md @@ -0,0 +1,217 @@ +--- +name: "employee-engagement-retention" +description: "Provides a practical, behaviour-level guide to why employees stay, why they leave, and what leaders do daily that determines which outcome occurs. Covers the eight retention-destroying behaviours, recognition versus appreciation, purpose-building, learning as a retention lever, and structured check-in practices that surface dissatisfaction before it becomes a resignation letter. Use when experiencing unexpected attrition, when exit interviews reveal leadership failures, when designing retention programmes, when coaching managers on engagement, or when building a culture people do not want to leave." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - retention + - engagement + - employee-experience + - recognition + - appreciation + - purpose + - motivation + - turnover +related_skills: + - leader-self-reflection + - leadership-style-adaptation + - ai-era-leadership + - psychological-safety + - radical-candor + - maslow-hierarchy + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Employee Engagement and Retention + +A comprehensive guide to making your best employees quit: + +Constrain their processes until they spend more time waiting for approvals than doing actual work. Set goals that contradict each other so they must choose which failure to own. Assign them roles that ignore their strongest capabilities. Give them tasks so easy that boredom becomes their primary workplace emotion. Waste their time in meetings that could have been emails about meetings that should not have existed. Disregard their psychological safety until they learn that speaking up is punished and silence is rewarded. Create an environment so comfortable that no one is challenged, stretched, or developed. Lead with bias and call it intuition. + +This list is not satire. It is a clinical summary of the eight behaviours that research identifies as the primary drivers of voluntary attrition. Every item is something a leader does -- not something that happens to a team. The uncomfortable corollary: if your people are leaving, the first place to look is the mirror. + +--- + +## The Practice + +### The Eight Retention-Destroying Behaviours + +Each of these behaviours is a leadership choice, often made unconsciously, that erodes the conditions people need to stay. + +**1. Process Constraints** +When employees must wait for others to provide information or resources before they can do their own work, productivity suffers and frustration compounds. The leader's job: identify bottlenecks through open conversation, then use positional influence to clear them. Every roadblock you remove is a reason to stay. + +**2. Inconsistent Goals** +Forcing employees to choose between contradictory expectations -- faster service versus more thorough documentation, innovation versus risk avoidance -- produces stress without resolution. The remedy: write down your team's goals, audit them for contradictions, and resolve the conflicts before asking anyone to execute. + +**3. Role Misassignment** +Employees whose talents and knowledge are underutilised feel invisible. The gap between what they can do and what they are asked to do becomes a daily reminder of wasted potential. Talk to people about their career goals. Match responsibilities to capabilities. Expand scope before they start looking elsewhere for it. + +**4. Insufficient Challenge** +Boredom is a resignation trigger that managers consistently underestimate. When work is too easy, motivation and engagement decay. Assign tasks that enhance knowledge and skills. Create learning agendas with target goals and road maps. Challenge is a form of respect. + +**5. Resource Waste** +Time is the resource most frequently squandered. Endless meetings, unnecessary attendees, and low-value tasks consume the hours that employees need for their highest-impact work. Before adding someone to a meeting or assigning additional work, ask: is this person genuinely the only one who can do this? + +**6. Psychological Safety Neglect** +Employees who do not feel safe to take risks, disagree openly, or admit mistakes become disengaged passengers rather than committed contributors. Show openness to new ideas. Ask questions before providing answers. Thank people for input, especially when it challenges your position. Own your own mistakes publicly. + +**7. Insufficient Pressure** +A moderate level of pressure improves performance. Too little creates purposelessness and drift. Provide regular feedback -- both affirming and developmental. Use coaching to identify improvement areas. Connect individual roles to the organisation's larger mission. Comfort without challenge produces complacency, not loyalty. + +**8. Biased Leadership** +When employees perceive decisions as driven by preference rather than evidence, trust collapses. Before making decisions that affect people, examine what is driving you. Are you basing the choice on data or on familiarity? Are there knowledge gaps you need to fill? Ask for feedback on your decision-making patterns -- and act on what you hear. + +### Recognition Versus Appreciation: The Distinction That Matters + +Leaders use these terms interchangeably. Employees experience them as fundamentally different. + +**Recognition** is feedback based on results or performance. It can be formal (awards, promotions, bonuses) or informal (verbal acknowledgment, a handwritten note). Recognition says: what you accomplished matters. + +**Appreciation** is acknowledgment of a person's inherent value -- not their output, but their worth as a colleague and a human being. Appreciation says: who you are matters. + +If you focus solely on recognition, you connect with people only through their achievements. You miss opportunities to support team members during difficult stretches when results are scarce but effort is genuine. Recognition is earned. Appreciation is owed -- all the time. + +### Purpose as a Retention Mechanism + +Instilling purpose takes more than speeches or mission statements. Done poorly, grand declarations of purpose trigger cynicism rather than commitment. Two principles govern effective purpose-building: + +1. **Purpose is a feeling, not a statement.** Telling people their work is important has limited impact. Showing them -- through customer testimonials, impact data, or direct connection with the beneficiaries of their efforts -- transforms abstract purpose into lived experience. + +2. **Authenticity is non-negotiable.** If your sudden interest in impact follows years of emphasising quarterly profits, the pivot will read as manipulative rather than genuine. Purpose must emerge from consistent behaviour, not a rebranding exercise. + +### The Five Questions You Should Be Asking + +Gallup research found that 51% of employees who quit say that no one -- including their manager -- asked about their job satisfaction before they left. Five questions close this gap: + +1. How would you like to grow here? +2. Do you feel a sense of purpose in your job? +3. What do you need from me to do your best work? +4. What is the company not doing that it should be doing? +5. Are you able to do what you do best every day? + +These are not annual review questions. They are quarterly conversation starters. The answers reveal problems you can solve and growth opportunities you can create -- before the employee decides to solve the problem by leaving. + +### Learning as the Underestimated Retention Lever + +Research from Harvard Business School and Boston Consulting Group reveals that employees are often far more eager to learn new skills than their leaders assume. Workers do not share leadership's anxiety about the future; they want to be developed for it. Offering learning opportunities -- stretch assignments, cross-functional exposure, formal training -- signals investment in a person's future. Withholding those opportunities signals that you see them as a static resource rather than a developing professional. + +Reward structures matter as well. Time-based incentives -- additional vacation days, schedule flexibility, services that save personal time -- often outperform monetary rewards in driving satisfaction. Framing non-cash benefits in financial terms helps employees appreciate their value. + +--- + +## Prompts + +**Prompt 1 -- Retention Risk Audit:** +> Assess my team's retention risk by evaluating each of the eight retention-destroying behaviours. My team of [number] people works in [function/industry]. Here is what I know about their current experience: [describe any signals -- turnover, complaints, engagement survey data, or your own observations]. For each behaviour, rate my team's exposure (Low/Medium/High), identify specific evidence, and recommend corrective actions I can take this week. + +**Prompt 2 -- Exit Pattern Analysis:** +> Over the past [timeframe], [number] employees have left my team/company. Here is what I know about each departure: [describe circumstances, exit interview data if available, tenure, and role]. Analyse these departures for patterns using the eight retention-destroying behaviours as a diagnostic framework. Identify the two or three systemic issues driving attrition and design an intervention plan with specific actions, timelines, and metrics. + +**Prompt 3 -- Recognition and Appreciation Programme:** +> Design a recognition and appreciation programme for my team of [number] people. Current state: [describe what you do now, if anything]. The programme should include both formal recognition mechanisms (tied to performance) and informal appreciation practices (acknowledging inherent value). Specify daily, weekly, and monthly rhythms. Include guidance for how I and other managers should adapt these practices for introverts versus extroverts, remote versus in-office employees, and individual versus team contributions. + +**Prompt 4 -- Purpose Integration:** +> My company's mission is [mission statement]. My team's function is [function]. Help me design three specific practices that connect my team's daily work to the company's purpose in ways that feel authentic rather than performative. Each practice should be sustainable (not a one-time event), concrete (not abstract), and emotionally resonant (shows impact, not just states it). + +**Prompt 5 -- Engagement Conversation Guide:** +> I want to start having meaningful engagement conversations with my [number] direct reports. Create a conversation guide based on the five satisfaction questions that I can use in one-on-one meetings. For each question, provide: (a) how to introduce it naturally, (b) follow-up questions based on likely responses, (c) what to do with the information gathered, and (d) how to follow up in the next conversation to demonstrate that I listened and acted. + +--- + +## Use Cases + +**Growth-Stage Startup Losing Senior Engineers** +A 70-person company has lost four senior engineers in six months. Exit interviews cite "lack of growth opportunities" -- but the company offers conference budgets and training stipends. The retention audit reveals the real issue: role misassignment combined with insufficient challenge. Senior engineers are maintaining legacy code rather than building new systems. Their conference attendance gave them exposure to exciting work elsewhere. The intervention: restructure the engineering team so that senior engineers spend at least 40% of their time on new architecture and mentoring junior engineers. Attrition stops within one quarter. + +**Scale-Stage Company with High Engagement Scores but Rising Turnover** +A 400-person company scores well on engagement surveys but experiences 22% annual turnover. The paradox resolves when the eight behaviours are examined: the culture is warm and supportive (high psychological safety, strong appreciation), but insufficiently challenging (low pressure, easy tasks, limited feedback). Top performers leave because they are bored, not because they are unhappy. The intervention: introduce stretch assignments for high performers, pair them with executive mentors, and create a "next-level readiness" programme that explicitly prepares people for roles above their current level. + +**Early-Traction Founder Who Cannot Retain First Hires** +A founder on their third office manager in two years blames the talent pool. The retention audit reveals a different story: inconsistent goals (the role was defined differently each week), process constraints (every decision required the founder's approval), and biased leadership (the founder favoured employees whose working style mirrored their own). The intervention begins with the founder, not the hire: clarify the role's actual responsibilities, delegate real authority, and establish a weekly one-on-one where the founder asks the five satisfaction questions and -- critically -- acts on the answers. + +--- + +## Anti-Patterns + +1. **The Compensation Reflex.** Responding to every retention problem with a raise or a bonus. Money prevents dissatisfaction but rarely creates engagement. If the underlying issue is role misassignment or purpose deficit, more money simply makes the employee a better-paid disengaged person who will leave later rather than sooner. + +2. **The Annual Engagement Survey Illusion.** Believing that a yearly survey captures real-time sentiment. Engagement is a daily phenomenon. Quarterly conversations with the five questions reveal more than any annual questionnaire, and they demonstrate care through the act of asking. + +3. **The Blame-the-Departing.** Attributing every resignation to the employee's personal circumstances rather than examining leadership's contribution. "They wanted something we couldn't offer" is sometimes true and often a convenient deflection from "We failed to offer what we could have." + +4. **The Perks Pile.** Stacking benefits -- ping-pong tables, free lunches, unlimited PTO -- as substitutes for the fundamentals: meaningful work, competent management, psychological safety, and genuine growth opportunities. Perks attract candidates. Fundamentals retain employees. + +5. **The Equal Treatment Trap.** Treating recognition and appreciation identically across the team. Extroverts and introverts demonstrate commitment differently. Some people thrive on public acknowledgment; others find it excruciating. Ask each person how they prefer to be recognised -- and then do it that way. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-employee relationship | Every departure is existential when the team is ten people. The founder's daily behaviour -- how they set goals, assign work, and respond to input -- is the entire retention strategy. There is no HR layer to compensate for leadership gaps. | +| Growth | Manager capability | As the company adds management layers, retention becomes a distributed responsibility. The most common failure: promoting high performers into management without teaching them the eight behaviours. Every new manager is a potential attrition vector or retention asset. | +| Scale | Systemic programmes | At scale, individual relationships cannot carry the full retention load. Formal recognition programmes, structured career pathways, purpose-integration rituals, and engagement measurement systems must be institutionalised. The leadership challenge shifts from personal practice to organisational design. | + +--- + +## Output Template + +```markdown +# Employee Engagement and Retention Assessment + +**Team/Organisation:** [Name] +**Leader:** [Name] +**Date:** [Date] +**Current Turnover Rate:** [Percentage] + +## Eight Behaviours Audit + +| Behaviour | Risk Level | Evidence | Corrective Action | Owner | Timeline | +|-----------|-----------|----------|-------------------|-------|----------| +| Process Constraints | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Inconsistent Goals | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Role Misassignment | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Insufficient Challenge | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Resource Waste | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Psych Safety Neglect | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Insufficient Pressure | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | +| Biased Leadership | [L/M/H] | [Evidence] | [Action] | [Who] | [When] | + +## Recognition and Appreciation Plan +- **Formal recognition:** [Mechanisms and frequency] +- **Informal appreciation:** [Daily/weekly practices] +- **Personalisation notes:** [How to adapt for different team members] + +## Engagement Conversation Schedule +| Team Member | Next Conversation | Key Questions to Prioritise | Follow-Up from Last | +|-------------|-------------------|-----------------------------|---------------------| +| [Name] | [Date] | [Questions] | [Actions taken] | + +## Retention Metrics +- 90-day retention rate: [Current] / [Target] +- 12-month retention rate: [Current] / [Target] +- Engagement conversation completion rate: [Current] / [Target] +- Internal mobility rate: [Current] / [Target] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework provides the theory for one of the eight retention-destroying behaviours; this skill covers the daily leadership practices that build or erode it. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- The balance of care and challenge maps directly to the recognition-appreciation distinction and the pressure calibration challenge. +- **[Maslow's Hierarchy](../../content/skills/frameworks/maslow-hierarchy.md)** -- Retention operates across Maslow's levels: from basic security (fair compensation) through belonging (appreciation) to self-actualisation (purpose and growth). +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The eight behaviours audit requires the kind of honest self-examination this companion skill develops as a daily practice. +- **[Inspiring and Retaining](../../content/skills/people/inspiring-and-retaining.md)** -- Provides the interpersonal practices -- personalised recognition, audience-centred presentations, content curation -- that complement the structural retention strategies here. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Learning is the underestimated retention lever; structured mentoring relationships operationalise the development that keeps high performers engaged. diff --git a/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md b/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md deleted file mode 120000 index ff00a83..0000000 --- a/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/enemies-of-clear-thinking.md \ No newline at end of file diff --git a/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md b/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md new file mode 100644 index 0000000..1060fa5 --- /dev/null +++ b/plugins/foreman/skills/enemies-of-clear-thinking/SKILL.md @@ -0,0 +1,208 @@ +--- +name: "enemies-of-clear-thinking" +description: "Diagnoses the four biological defaults that hijack entrepreneurial judgment -- emotion, ego, social conformity, and inertia -- using the Clear Thinking framework. Maps how each default manifests in startup contexts and provides recognition patterns for identifying when autopilot has seized control. Use when reacting impulsively to bad news, defending a position for ego rather than merit, conforming to industry consensus without independent analysis, or resisting a necessary pivot despite mounting evidence." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-defaults + - clear-thinking + - decision-making + - self-awareness + - emotion + - ego + - social-pressure + - inertia + - autopilot + - clear-thinking-framework +related_skills: + - building-thinking-strength + - managing-weakness-and-mistakes + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-self-awareness +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Enemies of Clear Thinking + +AUTOPILOT. Most consequential decisions are not made by conscious thought. They are made by biological autopilot -- four default programmes running beneath awareness, producing outputs the decision-maker mistakes for deliberate choice. The Clear Thinking research into real-world judgment failure reveals a pattern that Kahneman's System 1/System 2 model identifies at the cognitive level but does not fully operationalise at the behavioural one: between stimulus and response sits a gap, and in that gap, one of four defaults -- emotion, ego, social conformity, or inertia -- rushes in to fill the vacuum before reason can arrive. The entrepreneur who cannot name which default is driving a decision has already lost control of it. + +The critical insight is that the failure point is not dramatic. It is ordinary. The moments that determine outcomes are not the boardroom showdowns or the fundraising pitches. They are the unremarkable Tuesday afternoon reactions -- the snapped reply to a co-founder, the silent acquiescence to a board member's flawed thesis, the refusal to revisit a strategy that stopped working six months ago. Mastery over these ordinary moments is the compound interest of good judgment. + +--- + +## The Framework + +The framework identifies four biological defaults -- behavioural programmes written into human DNA by natural selection, executed automatically when triggered, unless the individual creates space to think. These defaults overlap and reinforce each other, but each has a distinct signature. + +### Default 1: The Emotion Default + +The tendency to respond to feelings rather than facts. Anger, fear, excitement, and anxiety all compress the gap between stimulus and response to near zero. The emotion default does not announce itself; it simply acts. + +**Entrepreneurial signature:** A founder receives a hostile email from a key customer threatening to churn. Before finishing the email, the founder is already drafting a defensive reply. The reply escalates the situation, damages the relationship, and consumes three days of recovery effort. The founder never consciously decided to respond that way -- the emotion default decided for them. + +**Recognition pattern:** Physical symptoms precede the behaviour. Elevated heart rate, narrowed attention, a feeling of urgency disproportionate to the actual stakes. The framework notes that biological vulnerabilities -- hunger, fatigue, sleep deprivation, stress -- amplify the emotion default's grip. A founder operating on four hours of sleep during a fundraise is not making decisions; their cortisol is. + +### Default 2: The Ego Default + +The tendency to react to anything that threatens self-image or perceived position in a hierarchy. The ego default is not vanity in the colloquial sense -- it is the deep biological drive to protect one's standing, which manifests as the need to feel right rather than to be right. + +**Entrepreneurial signature:** A founder's CTO proposes an architecture that the founder privately knows is superior to their own. Instead of adopting it, the founder finds reasons to delay, modify, or undermine the proposal -- not from malice, but from the unconscious calculation that accepting the CTO's idea diminishes their own perceived value. The framework calls this being on "the wrong side of right": optimising for ego rather than outcome. + +**Recognition pattern:** Disproportionate energy spent defending a position. Difficulty saying "I don't know." A pattern of transforming unearned knowledge -- a blog post, a podcast episode -- into confident pronouncements. The ego default converts shallow familiarity into reckless conviction, which is particularly hazardous when a founder enters an unfamiliar market or technology domain. + +### Default 3: The Social Default + +The tendency to conform to the norms of the surrounding group. The social default does not require explicit peer pressure; it operates through the ambient fear of being snubbed, ridiculed, or treated as an outsider. + +**Entrepreneurial signature:** A founder at a Y Combinator dinner hears three peers describe their go-to-market strategy as product-led growth. Despite having customer evidence that a sales-led approach works better for their market, the founder begins pivoting toward PLG the following week. No analysis preceded the decision. The social default -- the comfort of aligning with the tribe -- supplied the conviction that data did not. + +**Recognition pattern:** Warren Buffett's observation applies with surgical precision: "The fact that other people agree or disagree with you makes you neither right nor wrong." If a strategic choice can only be justified by pointing to what others are doing, the social default is driving. The framework notes that "best practices" are, by definition, average practices -- and following them guarantees average results. + +### Default 4: The Inertia Default + +The tendency to maintain the status quo and resist change, even when change is clearly warranted. Inertia is cognitive as much as behavioural: once a mind is set in a direction, it tends to continue in that direction unless acted upon by an outside force. + +**Entrepreneurial signature:** A SaaS founder has recognised for six months that their pricing model is leaving revenue on the table. Customers have signalled willingness to pay more. Unit economics confirm it. Yet the founder keeps deferring the change because the current model is "working well enough." This is what the framework calls the "zone of average" -- a state too good to trigger alarm, too mediocre to produce excellence, and therefore perfectly designed to persist indefinitely. + +**Recognition pattern:** The phrase "that's how we've always done it" is the inertia default's national anthem. Public commitments create additional inertia -- having told the board a particular strategy would work, the founder finds it psychologically impossible to reverse course, even when new data demands it. The longer a hard conversation is avoided, the harder it becomes to have, until a small correctable problem has metastasised into a structural crisis. + +### How Defaults Compound + +The defaults rarely operate in isolation. A founder who is emotionally attached to an idea (emotion default) will defend it as their own (ego default), surround themselves with people who agree (social default), and resist changing course when it fails (inertia default). The compounding effect transforms a single unexamined moment into a cascading series of poor decisions, each reinforcing the last. + +--- + +## Prompts + +**Prompt 1 -- Default Diagnosis:** +> I just made (or am about to make) this decision: [describe decision]. Analyse it through the four-default lens. For each default (emotion, ego, social, inertia), assess whether it is likely influencing my thinking. Identify the specific trigger, the default behaviour it would produce, and what the clear-thinking alternative would look like. Be direct -- I need honesty, not comfort. + +**Prompt 2 -- Ordinary Moment Audit:** +> Review my last week of decisions and reactions: [describe 5-7 recent decisions, including small ones]. Identify which ones were "ordinary moments" where a default likely took control without my awareness. For each, name the default, describe what clear thinking would have produced instead, and estimate the cumulative cost of these unforced errors. + +**Prompt 3 -- Default Vulnerability Map:** +> Based on my current situation -- [describe stage, stressors, team dynamics, recent events] -- build a vulnerability map showing which defaults I am most susceptible to right now and why. Include biological amplifiers (sleep, stress, fatigue levels). Then recommend three specific environmental changes or rules that would reduce my exposure to the most dangerous default. + +**Prompt 4 -- Compounding Default Analysis:** +> Analyse this ongoing situation: [describe a persistent problem or stuck decision]. Map how multiple defaults may be compounding to keep me locked in a suboptimal position. Trace the chain: which default started the pattern, which ones reinforced it, and what would breaking one link in the chain look like in practice? + +--- + +## Use Cases + +**Validation-Stage Healthtech Founder Reacting to Investor Rejection** + +A digital health founder receives three consecutive investor rejections in a single week, each citing concerns about regulatory risk. The emotion default triggers a defensive posture -- the founder begins rewriting the pitch deck to minimise regulatory discussion rather than address it substantively. The ego default compounds the problem: the founder dismisses the investors as "not understanding the space" rather than considering whether the feedback contains a genuine signal. Applying the framework, an advisor helps the founder separate the emotional reaction from the informational content. The founder creates a 24-hour rule -- no pitch deck changes within 24 hours of a rejection -- which allows the emotion default to subside before strategic decisions are made. The revised deck confronts regulatory risk head-on, and the next investor meeting produces a term sheet. + +**Growth-Stage Marketplace Founder Trapped by Inertia and Social Default** + +A two-sided marketplace at $3M ARR has been running the same customer acquisition playbook for eighteen months. Growth has plateaued, but the playbook was designed by a well-known growth advisor whose framework the founder presented at two industry conferences. The social default (having publicly endorsed the approach) and the inertia default (the approach is familiar and comfortable) combine to prevent the founder from testing alternatives. A board member introduces the "zone of average" concept: the current results are adequate enough to prevent crisis but insufficient to attract Series A investment. The founder acknowledges the defaults at play, depersonalises the decision from the advisor's reputation, and allocates 30% of the acquisition budget to experimental channels. One experiment outperforms the legacy playbook within six weeks. + +**Scale-Stage Fintech CEO Whose Ego Default Is Blocking Delegation** + +A fintech CEO at $20M ARR continues to approve every product feature personally, creating a bottleneck that has slowed release cycles by 40%. The CEO frames this as "maintaining quality standards," but the ego default analysis reveals a different mechanism: having others depend on every decision makes the CEO feel indispensable. The ego default has converted a genuine strength (product taste) into a structural weakness (organisational paralysis). The CEO implements a safeguard -- a decision classification matrix that reserves only irreversible, high-stakes product decisions for CEO approval -- and watches release velocity recover within a quarter. + +**Idea-Stage Consumer App Founder Whose Social Default Killed Differentiation** + +A consumer social app founder attended a prominent tech conference and heard four successful founders describe their growth strategy as "community-first, product-second." The founder had been building a product-first approach with strong early retention data. Within two weeks of the conference, the founder restructured the roadmap around community features, deprioritising the product mechanics that were generating actual traction. No quantitative analysis preceded the shift; the social default -- the gravitational pull of aligning with high-status peers -- supplied the justification. Three months later, retention collapsed. A board advisor helped the founder trace the decision back to the conference, identify the social default as the driver, and restore the original product-first approach. The recovery took a full quarter -- time the founder would not have lost had the default been recognised in the moment it operated. + +--- + +## Anti-Patterns + +**1. Treating default awareness as default immunity.** Knowing the four defaults exist does not neutralise them. The research is explicit: even decades of studying these patterns do not make a person immune. This parallels Kahneman's own admission about cognitive biases. The corrective is structural -- building environmental safeguards and decision rules -- not intellectual self-congratulation. + +**2. Weaponising default labels against colleagues.** Telling a co-founder "that's just your ego talking" is not analysis; it is a power move dressed in psychological vocabulary. Default diagnosis should be applied to decision processes and to oneself first. The moment it becomes interpersonal ammunition, it destroys the trust required for honest deliberation. + +**3. Assuming all intuition is a default in disguise.** The framework does not argue that emotion, social awareness, or pattern-based inertia are always wrong. These defaults evolved because they provided survival advantages. The problem is not their existence but their unexamined operation. A founder with fifteen years of domain expertise whose gut says "this market is wrong" may be exercising genuine pattern recognition, not the emotion default. The distinguishing question: can the reasoning behind the intuition be reconstructed and examined? + +**4. Using the framework to justify indecision.** Some founders, upon learning about defaults, begin second-guessing every impulse until no decision is possible. The framework is designed to create space for reason, not to replace action with perpetual self-analysis. The goal is a pause measured in minutes, not months. + +**5. Ignoring the compounding effect.** Addressing only one default while leaving others unexamined produces a false sense of progress. A founder who manages their emotional reactions but continues to conform to social consensus has solved only a quarter of the problem. The defaults must be diagnosed as a system, not in isolation. + +--- + +## By Stage + +| Stage | Primary Default Risk | Key Difference | +|-------|---------------------|----------------| +| Idea | Ego + Social | The ego default inflates confidence in an untested concept; the social default either validates it through echo-chamber feedback or kills it through premature conformity to "realistic" expectations. | +| Validation | Emotion + Ego | Negative signals from early customers trigger the emotion default (defensiveness) and the ego default (dismissing feedback). The founder's identity is maximally entangled with the product at this stage. | +| Early Traction | Social + Inertia | Initial success creates inertia around the first playbook that worked. Social defaults intensify as the founder enters a peer group (accelerator, investor network) whose norms exert conformity pressure. | +| Growth | Inertia + Ego | Scaling requires changing what worked at smaller scale, but inertia resists structural change and the ego default makes it difficult for the founding team to admit that their original approach has reached its limits. | +| Scale | All four compounding | At scale, defaults become organisational, not personal. A CEO's unexamined ego default becomes a company-wide culture of deference. Social defaults calcify into "the way things are done here." Inertia becomes institutional resistance to strategic evolution. | + +At the idea stage, the most valuable intervention is protecting the founder from the social default's premature influence. The observation that "if you do what everyone else does, you'll get the same results everyone else gets" is maximally relevant when the entire value of a new venture lies in doing something different. The founder who listens too early to how "the market usually works" has surrendered the only advantage an idea-stage venture possesses: the licence to be unconventional. + +At the validation stage, the emotion and ego defaults create a particularly dangerous compound. The founder has invested months -- possibly years -- of identity into the concept. Customer feedback that contradicts the thesis does not arrive as neutral data; it arrives as a personal attack. The emotion default produces defensiveness; the ego default provides the rationalisation. Together they can sustain a dead hypothesis well past the point where honest assessment would have triggered a pivot. + +At growth, inertia becomes the primary adversary. The playbooks that generated early traction begin to ossify into doctrine. Challenging them feels like questioning the founding story itself. The "zone of average" concept is maximally relevant here: results are adequate enough to prevent crisis but insufficient to justify the company's valuation trajectory. The inertia default thrives in this zone because nothing is broken badly enough to force change. + +At scale, the challenge shifts from individual default management to organisational default architecture. The CEO's task is no longer managing their own autopilot but designing systems, incentives, and cultures that prevent the organisation from running on collective autopilot. A single executive's unexamined social default -- the tendency to hire people who think like them, reward consensus, and punish dissent -- can, over time, produce an entire company that has lost the capacity for independent thought. + +--- + +## Output Template + +```markdown +# Default Diagnosis -- [Decision or Situation] + +**Date:** [Date] +**Decision-maker:** [Name / Role] +**Context:** [Brief situation description] + +## Default Scan + +| Default | Active? | Trigger | Evidence | Severity | +|---------|---------|---------|----------|----------| +| Emotion | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Ego | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Social | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | +| Inertia | [Y/N] | [What triggered it] | [Observable behaviour] | [H/M/L] | + +## Biological Amplifiers +- Sleep: [Hours last 3 nights] +- Stress level: [H/M/L] +- Recent emotional event: [Y/N -- describe] +- Environment: [Familiar / Unfamiliar] + +## Compounding Analysis +[Describe how multiple defaults may be reinforcing each other] + +## Clear-Thinking Alternative +[What the decision or response would look like if no default were operating] + +## Safeguard Recommendation +1. [Specific environmental change or rule] +2. [Specific environmental change or rule] +3. [Specific environmental change or rule] + +## Ordinary Moment Assessment +- **Is this moment ordinary or dramatic?** [Most consequential moments feel ordinary] +- **Will this response make the future easier or harder?** [The framework's core test] +``` + +--- + +## Related Skills + +- **[Building Thinking Strength](../../content/skills/thinking/building-thinking-strength.md)** -- Diagnosing defaults is the first step; building the four internal strengths is how you override them consistently. +- **[Managing Weakness and Mistakes](../../content/skills/thinking/managing-weakness-and-mistakes.md)** -- When defaults win despite awareness, safeguards and mistake-handling protocols limit the damage and extract learning. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's System 1/System 2 model provides the cognitive science foundation; the four defaults operationalise it into specific behavioural patterns entrepreneurs can recognise. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Offers the daily decision habits that complement the deeper diagnostic system, particularly the importance-frequency matrix. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The Stoic dichotomy of control achieves clarity by distinguishing what can and cannot be influenced; the Clear Thinking framework achieves it by identifying which biological programme is doing the influencing. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- Provides the philosophical discipline for managing the emotion default specifically, complementing the behavioural and environmental approach. +- **[Stoic Unbiased Thought](../../content/skills/stoic/stoic-unbiased-thought.md)** -- The Stoic impression-testing protocol is the ancient ancestor of the modern default-interruption techniques; both aim to create a gap between stimulus and response. diff --git a/plugins/foreman/skills/evaluating-and-deciding/SKILL.md b/plugins/foreman/skills/evaluating-and-deciding/SKILL.md deleted file mode 120000 index b1833f5..0000000 --- a/plugins/foreman/skills/evaluating-and-deciding/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/evaluating-and-deciding.md \ No newline at end of file diff --git a/plugins/foreman/skills/evaluating-and-deciding/SKILL.md b/plugins/foreman/skills/evaluating-and-deciding/SKILL.md new file mode 100644 index 0000000..85848ec --- /dev/null +++ b/plugins/foreman/skills/evaluating-and-deciding/SKILL.md @@ -0,0 +1,247 @@ +--- +name: "evaluating-and-deciding" +description: "Covers the full arc from option evaluation through execution and post-decision learning: criteria weighting and the 'most important thing' discipline, high-fidelity and high-expertise information gathering, margin of safety as a buffer against being wrong, the irreversibility test for calibrating decision speed, bullets-before-cannonballs experimentation, execution fail-safes (trip wires, commander's intent, Ulysses pacts), and the process-over-outcome principle for decision journals. Use when evaluating multiple options against competing criteria, when the cost of being wrong is high and margin of safety is needed, when deciding how fast to move, when building execution safeguards, or when conducting post-mortems that separate luck from skill." +version: "1.0.0" +category: "thinking" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - margin-of-safety + - decision-evaluation + - irreversibility + - second-order-thinking + - inversion + - decision-journal + - execution + - fail-safes + - criteria-weighting + - bullets-before-cannonballs +related_skills: + - defining-and-exploring-problems + - thinking-fast-and-slow + - decision-making-under-pressure + - wanting-what-matters + - scenario-planning + - stoic-fortitude-and-resilience +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Evaluating and Deciding + +MARGIN OF SAFETY. Good decision-makers do not predict more accurately than everyone else -- they build better buffers for being wrong. Warren Buffett sat out the dot-com mania while friends doubled and quadrupled their portfolios, endured years of being called obsolete, and emerged with cash reserves intact when the bubble burst. The hedge fund Long-Term Capital Management, run by two Nobel laureates and some of the highest IQs in finance, delivered 40 percent annual returns until it lost $4.6 billion in under four months and nearly collapsed the global financial system. The difference was not intelligence. It was the presence or absence of a margin of safety -- the deliberate gap between what you expect to happen and what could happen, designed to save you when surprises are expensive. The framework for the full decision arc -- evaluate, safeguard, execute, learn -- rests on this single uncomfortable truth: certainty is a feeling, not a fact, and the moment you are most confident you do not need a buffer is precisely the moment you need one most. + +--- + +## The Framework + +The framework spans four stages. Each builds on the preceding one, and skipping any stage degrades the quality of the entire arc. + +### Stage 1: Evaluate the Options + +Evaluation begins not with data but with criteria. Three features distinguish useful criteria from decorative ones: + +- **Clarity.** The criterion can be explained to a twelve-year-old. If it requires jargon, it will be interpreted differently by each person applying it. +- **Goal promotion.** The criterion must favour options that advance the actual objective. NASA's Challenger disaster is the canonical counter-example: launch-date criteria promoted the goal of schedule adherence, not the goal of safety. The result was catastrophic. +- **Decisiveness.** The criteria must narrow the field to one option. Criteria that produce ties are criteria that avoid commitment. + +**Finding the Most Important Thing.** The text recounts a lesson from a mentor that teams cannot make decisions independently unless the leader communicates a single overriding priority. Not three priorities. Not a weighted matrix of ten factors. One. The exercise for identifying it is deliberately combative: write each criterion on a separate card, then force them to battle in pairs. "If I could have only one of these, which would it be?" As criteria compete, quantities emerge -- thresholds at which the ranking reverses. The result is an ordered stack with the most important thing at the top and the precise conditions under which the order would change. + +**Getting the Right Information.** Two principles govern information quality: + +| Principle | Definition | Entrepreneurial Application | +|-----------|------------|----------------------------| +| **HiFi (High-Fidelity)** | Information close to the source, unfiltered by others' biases and incentives. | Talk to customers directly, not to the VP who summarised the survey. General Marshall sent trusted observers to the front lines and discovered that pilots were refusing to fly not because of aircraft defects but because ground crews, ravaged by malaria from lack of mosquito netting, could not be trusted to maintain the planes. Headquarters, in its mosquito-protected offices, had no idea. | +| **HiEx (High-Expertise)** | Information from people with deep, recent experience solving the specific problem at hand. | Seek experts who solved your problem recently, not two decades ago. Pay for their time -- it forces you to prepare precise questions. Ask "how do you think about this?" rather than "what should I do?" The former transfers reasoning; the latter transfers only an answer. | + +**Distinguishing Experts from Imitators.** Imitators cannot answer questions at a deeper level, cannot adapt their vocabulary to a non-specialist audience, become frustrated when you say you do not understand, avoid discussing their failures, and cannot identify the boundaries of their own competence. Real experts display the opposite on every count. + +### Stage 2: Margin of Safety + +A margin of safety is insurance for decisions. In years when nothing goes wrong, it looks like waste. In the year something does, it is the difference between survival and ruin. + +The baseline heuristic: a margin of safety sufficient to absorb double the worst-case scenario. If job loss would take six months to recover from, hold twelve months of expenses. If a product launch might miss revenue targets by 30 percent, build a budget that survives a 60 percent miss. + +Adjustments to the baseline: + +- **High cost of failure, volatile environment:** Increase the margin. The consequences of underprotection are asymmetric -- you can always reduce a margin later, but you cannot retroactively create one. +- **Low cost of failure, established pattern:** Reduce the margin. Not every decision requires a buffer. The discipline is knowing which ones do. +- **Deep expertise and proprietary data:** Reduce the margin further, as Buffett does when buying businesses he understands well enough to pay near full value. + +**Bullets Before Cannonballs.** When still gathering information, do not over-invest in a single option. Jim Collins and Morten Hansen's metaphor is precise: fire small, cheap bullets to calibrate aim, then fire the cannonball along the validated line of sight. A founder evaluating two CEO candidates should have both complete a small paid project with the team before committing to either. A founder considering medical school should shadow a resident for a day, not enrol in a programme. Preserving optionality has a cost -- it can look like indecision. But looking short-term stupid while keeping options open is a consistent feature of the most successful long-term decision-makers. + +**Inversion: What Would Guarantee Failure?** Rather than asking "what should we do to succeed?" ask "what would guarantee failure?" and then avoid those things. If guaranteed failure for a product launch means shipping without beta testing, launching without a support team, and ignoring the first two weeks of customer feedback -- then the margin of safety must explicitly prevent each of those conditions. + +### Stage 3: Execute the Decision + +**The Irreversibility Test.** Decisions sit on a spectrum from trivially reversible to permanently irreversible. Two principles calibrate speed to position on this spectrum: + +- **ASAP Principle:** If the cost to undo the decision is low, make it as soon as possible. Deliberating over a reversible choice is itself a costly error. Jeff Bezos calls these "two-way doors" -- walk through, and if it is wrong, walk back. +- **ALAP Principle:** If the cost to undo the decision is high, make it as late as possible while continuing to gather information and preserve optionality. These are "one-way doors." Keeping a pocket of space open -- the way a driver maintains following distance at high speed -- is how you preserve the ability to manoeuvre when circumstances shift. + +**The Stop, FLOP, Know Principle.** Even for one-way doors, there comes a moment to act. That moment arrives when: (1) you Stop gathering useful information -- confidence is rising but accuracy is not; (2) you experience a First Lost OPportunity, meaning options begin to expire; or (3) you come to Know something -- a piece of evidence or a gut conviction tested against reason -- that makes the right choice evident. + +**Live with the Decision Before Announcing It.** Make the decision, then sleep on it. Before bed, write a note to yourself explaining why you decided as you did. Read the note in the morning. More often than expected, the reasoning that seemed airtight at 6 PM looks different at 7 AM. Announcing prematurely starts things moving and makes reversal socially expensive. + +**Three Execution Fail-Safes:** + +1. **Trip Wires.** Precommit to specific actions triggered by quantifiable conditions. A summit team agrees to turn back if they have not reached Camp 4 by noon. A startup agrees that if month-three retention is below 20 percent, the product thesis is invalidated. No argument at the moment of truth -- the decision was already made. + +2. **Commander's Intent.** Communicate the strategy, the rationale, and the operational boundaries so that team members can adapt when circumstances change without waiting for approval. The four components are formulate, communicate, interpret, and implement. If you cannot be away from the office for a week without things falling apart, the failure is not that you are indispensable -- it is that you are an incompetent communicator of intent. + +3. **Ulysses Pacts (Tying Your Hands).** Remove the option to deviate from the plan during moments of weakness. Automated investment deposits. Removing junk food from the house. Locking in a product launch date with external commitments that make delay socially or financially costly. + +### Stage 4: Learn from Decisions + +**The Process Principle.** Evaluate the process you used, not the outcome you got. A good decision can produce a bad outcome (bad luck), and a bad decision can produce a good outcome (good luck). Pete Carroll's decision to throw rather than run on the one-yard line in Super Bowl XLIX was rooted in sound analysis of the opponent's defensive weaknesses. The interception that resulted was, in his words, "the worst result of a call ever" -- not the worst call. + +The process-outcome matrix: + +| | Good Outcome | Bad Outcome | +|---|---|---| +| **Good Process** | Deserved success. Stay disciplined. | Bad luck. Trust the process. Learn and continue. | +| **Bad Process** | Undeserved success. You got lucky. Change before luck runs out. | Deserved failure. Let it be a wake-up call. | + +**The Transparency Principle.** Make your reasoning visible and open to scrutiny -- primarily to yourself. The ego default rewrites memory after the fact, conflating what you know now with what you knew then. A decision journal defeats this distortion. + +What to record at the time of the decision: + +- The problem as you understood it +- The options you considered and the criteria you applied +- What you expected to happen and why +- The information you had and the information you wished you had +- Your confidence level + +What to review afterward: + +- Did the outcome occur for the reasons you anticipated? +- Where did your reasoning hold, and where did it break down? +- Was the result attributable to skill or to luck? + +One firm described in the text discovered that its decision-makers were correct only 20 percent of the time -- and that even when anticipated outcomes materialised, they did so for different reasons than predicted. The firm's "success" was indistinguishable from roulette. Without the journal, they would never have known. + +--- + +## Prompts + +**Prompt 1 -- Criteria Weighting:** +> "I need to decide between [options] for my [stage] [sector] company. Help me identify the five most relevant evaluation criteria, then run the 'criteria battle' exercise: force each pair to compete ('if I could have only one, which would it be?'), surface the quantities at which rankings reverse, and produce a final ordered stack with the single most important thing at the top." + +**Prompt 2 -- Margin of Safety Calculation:** +> "I am planning [initiative/investment/launch] with an expected outcome of [target]. Apply the margin of safety framework: (1) identify what could go wrong, (2) estimate the worst plausible scenario, (3) calculate a buffer that absorbs double that worst case, and (4) recommend adjustments based on the cost of failure, environmental volatility, and my level of expertise. Include a bullets-before-cannonballs plan for low-risk validation before full commitment." + +**Prompt 3 -- Irreversibility and Timing Assessment:** +> "I am facing [decision]. Classify it on the consequentiality-reversibility spectrum. Is this a two-way door (ASAP) or a one-way door (ALAP)? Apply the Stop, FLOP, Know principle to determine whether I have enough information to act now, or whether I should continue gathering information and preserving optionality. Identify the specific signals that would trigger action." + +**Prompt 4 -- Post-Decision Review:** +> "Six months ago I decided [decision]. The outcome was [outcome]. Help me conduct a process review using the framework: (1) Reconstruct what I knew at the time and the reasoning I used. (2) Determine whether the outcome occurred for the reasons I expected. (3) Classify the result in the process-outcome matrix (good process/good outcome, good process/bad outcome, etc.). (4) Identify what I should change in my process for future decisions of this type." + +--- + +## Use Cases + +**Early-Traction Marketplace Evaluating Expansion Options** + +A two-sided marketplace for freelance graphic designers has achieved product-market fit in one vertical (e-commerce brands) and faces three expansion options: geographic expansion, vertical expansion (adding new buyer segments), and service expansion (adding motion design). The founder's instinct is to pursue all three. Applying the criteria battle, the team identifies that the single most important thing is deepening supply-side liquidity in the existing vertical -- without which none of the expansion options will succeed. The margin of safety analysis reveals that pursuing two expansion vectors simultaneously, if either underperforms by 40 percent, would burn through runway before Series A closes. The bullets-before-cannonballs prescription: run a four-week paid pilot in the most promising new vertical with five existing designers and ten new buyers. If conversion rates match the existing vertical within 70 percent, fire the cannonball. If not, recalibrate before committing resources. + +**Growth-Stage Fintech Deciding on Regulatory Strategy** + +A fintech company approaching $50M ARR must choose between applying for its own banking charter (expensive, slow, high control) and partnering with a sponsor bank (faster, lower cost, less control). Binary framing makes this look like a pure trade-off. The irreversibility test reveals that obtaining a charter is a one-way door (ALAP Principle applies -- delay and gather information), while a sponsor-bank partnership is a two-way door (ASAP Principle -- sign and renegotiate later if needed). Commander's intent for the compliance team: "Our most important thing is maintaining uninterrupted service to existing customers. Any regulatory strategy that risks a service gap is off the table, regardless of long-term efficiency gains." Trip wire: if the charter application has not advanced past preliminary review within nine months, pivot full resources to the sponsor-bank path. + +**Solo Founder Learning from a Failed Product Launch** + +A solo founder launched a productivity tool for remote teams, priced at $29/month, and acquired 200 users in the first month -- but 90 percent churned within 60 days. The natural instinct is resulting: "the product failed, so the decision to launch was bad." A process review using the decision journal reveals that the launch decision itself was sound (low cost to undo, clear stop-loss criteria, validated demand through a landing page test), but the pricing and onboarding criteria were set without HiFi information -- the founder relied on competitor pricing data aggregated by a third-party report rather than talking to ten target customers about willingness to pay. The process failure was informational, not decisional. The corrective action is not to abandon the product but to invest in direct customer conversations before the next pricing iteration. + +--- + +## Anti-Patterns + +**Treating all decisions as one-way doors.** Founders who deliberate for weeks over reversible choices -- a landing page design, a pricing test, a Slack channel name -- are misallocating their most constrained resource: time. The ASAP Principle exists precisely for these decisions. Walk through the two-way door. If it is wrong, walk back. + +**Building no margin of safety because "we know what we're doing."** Buffett's observation applies: "Diversification is protection against ignorance. It makes little sense if you know what you are doing." The corollary is that most of us rarely know what we are doing with the confidence required to go all in. The moment confidence peaks is precisely when the margin of safety is most needed, because overconfidence is the ego default's signature product. + +**Resulting -- evaluating decisions by outcomes alone.** A decision that produced a good outcome may have been reckless (bad process, good luck). A decision that produced a bad outcome may have been excellent (good process, bad luck). Without a decision journal that captures reasoning at the time of the decision, there is no way to distinguish skill from luck, and no mechanism for improvement. + +**Setting trip wires you are willing to override.** A trip wire that is negotiable at the moment of truth is not a trip wire. It is a suggestion. The entire point of precommitment is that it removes discretion from your future self -- the version of you that is fatigued, emotionally invested, and susceptible to summit fever. If the team agreed to turn back at noon and it is 12:01, the team turns back. + +**Confusing commander's intent with abdication.** Empowering others to make decisions requires communicating the strategy, the rationale, and the boundaries. Telling a team "just figure it out" without context is not delegation; it is abandonment. Commander's intent has four components; skipping the first two makes the last two impossible. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Criteria are sparse and personal -- the founder evaluates options against their own goals, risk tolerance, and opportunity costs. | The margin of safety is primarily financial (personal runway). Bullets before cannonballs means validating demand before building product. | +| Validation | Criteria become market-facing -- customer willingness to pay, retention rates, activation metrics. | HiFi information from direct customer contact outweighs any survey or third-party report. The ASAP Principle applies to most validation experiments. | +| Early Traction | The team grows, and the "most important thing" must be communicated to others. Criteria battles happen across functions, not just in the founder's head. | Commander's intent becomes operational. Trip wires attach to leading metrics (activation, retention) not just lagging ones (revenue). | +| Growth | Multiple consequential decisions compete for attention simultaneously. Margins of safety interact -- a thin buffer in one area can cascade into failure in another. | The ALAP Principle governs major strategic bets (new markets, acquisitions, platform changes). Decision journals become institutional, not personal. | +| Scale | The decision-maker is increasingly distant from the source of information. Abstractions multiply. | The HiFi Principle is hardest to maintain at scale and therefore most valuable. Leaders must actively seek unfiltered information from the front lines. The Transparency Principle becomes an organisational practice, not an individual one. | + +--- + +## Output Template + +```markdown +# Decision Evaluation Record + +**Date:** [date] +**Decision:** [one-sentence description] +**Decision-maker:** [name] +**Irreversibility classification:** [Two-way door / One-way door] +**Timing principle applied:** [ASAP / ALAP] + +## Criteria (Ordered by Battle Results) +1. [Most important thing] -- threshold: [quantified] +2. [Second criterion] -- threshold: [quantified] +3. [Third criterion] -- threshold: [quantified] + +## Options Evaluated + +| Option | Criterion 1 | Criterion 2 | Criterion 3 | Margin of Safety | +|--------|-------------|-------------|-------------|------------------| +| A | [score/assessment] | [score] | [score] | [buffer description] | +| B | [score/assessment] | [score] | [score] | [buffer description] | +| C | [score/assessment] | [score] | [score] | [buffer description] | + +## Information Quality +- **HiFi sources consulted:** [list] +- **HiEx sources consulted:** [list] +- **Key information gaps:** [what we still do not know] + +## Decision +**Chosen option:** [X] +**Reasoning:** [why this option best satisfies the ordered criteria] +**What I expect to happen:** [specific predictions] +**Confidence level:** [low / moderate / high] + +## Execution Fail-Safes +- **Trip wire(s):** [condition] triggers [action] +- **Commander's intent:** [the most important thing + boundaries] +- **Ulysses pact:** [hands tied how] + +## Post-Decision Review (Complete After Outcome) +- **Outcome:** [what happened] +- **Did it happen for the reasons I predicted?** [yes/no + explanation] +- **Process-outcome classification:** [good process + good outcome / good process + bad outcome / etc.] +- **What I would change in my process:** [specific improvements] +``` + +--- + +## Related Skills + +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The prerequisite: correct problem definition and solution-space exploration must occur before evaluation begins. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- The cognitive bias catalogue that explains why evaluation goes wrong: anchoring on early information, overconfidence, and the planning fallacy. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Focuses on the speed dimension: when to stop deliberating and act. +- **[Wanting What Matters](../../content/skills/thinking/wanting-what-matters.md)** -- The meta-question that sits above all evaluation criteria: are you optimising for the right things in the first place? +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- Provides the psychological infrastructure for maintaining discipline when trip wires trigger and margins of safety are tested. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Extends the margin of safety concept into a formal methodology for preparing for multiple possible futures. +- **[Evaluating Options](../../content/skills/decisions/evaluating-options.md)** -- Provides the complementary evaluation toolkit including joint evaluation, Even Swaps, and risk ranking methods for choosing among generated alternatives. diff --git a/plugins/foreman/skills/evaluating-options/SKILL.md b/plugins/foreman/skills/evaluating-options/SKILL.md deleted file mode 120000 index dd466ff..0000000 --- a/plugins/foreman/skills/evaluating-options/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/decisions/evaluating-options.md \ No newline at end of file diff --git a/plugins/foreman/skills/evaluating-options/SKILL.md b/plugins/foreman/skills/evaluating-options/SKILL.md new file mode 100644 index 0000000..797934c --- /dev/null +++ b/plugins/foreman/skills/evaluating-options/SKILL.md @@ -0,0 +1,263 @@ +--- +name: "evaluating-options" +description: "Provides six independent evaluation techniques for choosing among alternatives once they have been generated: joint evaluation (comparing options side by side rather than in isolation), the structural weaknesses of pros-and-cons lists and how to compensate, the Even Swaps method for rational trade-offs across incommensurable objectives, decision-making with limited data using satisficing and recognition-primed models, the CARVER six-part risk assessment tool, and a three-condition framework for calibrating when intuition is trustworthy versus dangerous. Use when evaluating multiple options against competing criteria, when a pros-and-cons list feels insufficient for a high-stakes choice, when trade-offs involve incomparable dimensions, when data is scarce and a decision cannot wait, when assessing risk across multiple assets or initiatives, or when debating whether to trust a gut feeling." +version: "1.0.0" +category: "decisions" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - evaluation + - trade-offs + - even-swaps + - joint-evaluation + - risk-assessment + - carver + - intuition + - pros-and-cons + - satisficing + - decision-quality +related_skills: + - decision-traps-and-roles + - generating-solutions + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Evaluating Options + +PROS-CONS TRAP. The pros-and-cons list is the most widely used decision tool in the world -- and it is fundamentally misleading, because it treats all factors as equal and all items as comparable. Benjamin Franklin popularised the method in 1772, and the business world has not materially improved upon it in the intervening 250 years. A list that places "strong brand fit" next to "high implementation cost" as if both carry identical weight, and then counts items on each side like ballots, is not analysis. It is arithmetic applied to incommensurable quantities. High-stakes decisions -- the kind that determine whether a company enters a market, acquires a competitor, or pivots its product -- demand evaluation methods that account for unequal weights, incomparable dimensions, and the structural biases that distort human judgment even when the data is sound. This skill assembles six such methods, each designed for a different evaluation challenge. + +--- + +## The Toolkit + +### Tool 1: Joint Evaluation + +Research by Basu and Savani demonstrates that people are, on average, twenty-two percent more likely to choose the objectively best option when they evaluate all alternatives simultaneously rather than one at a time. The effect is robust across simple consumer choices and complex managerial decisions. + +The mechanism is straightforward: when options are presented side by side, the mind compares directly across dimensions. When options are presented sequentially, the mind forms a holistic impression of each and then attempts to compare impressions -- a lossy process that discards the dimensional detail where differences actually live. + +**Practical application:** +- When evaluating job candidates, lay all resumes on the table simultaneously rather than reviewing one, forming an opinion, and moving to the next +- When comparing vendors or partners, use a spreadsheet that displays all options in columns with attributes in rows -- never evaluate a vendor in isolation +- When assessing strategic alternatives, present all options in a single consequences table before any discussion begins + +The bias toward sequential evaluation is strong: in one survey, participants reported evaluating options one at a time in roughly half of all decisions. Companies reinforce this by designing product pages and internal reports that present one option per screen. Resist the format. Demand the side-by-side view. + +### Tool 2: Beyond Pros and Cons + +The pros-and-cons list has three genuine strengths and three fatal weaknesses. Understanding both prevents the tool from being either abandoned prematurely or trusted beyond its competence. + +**Strengths:** +- *Rigour of enumeration.* The discipline of listing factors forces consideration of dimensions that might otherwise be overlooked +- *Emotional distance.* The act of writing creates what psychologists call a "self-distanced perspective," reducing the risk of an amygdala hijack during high-stakes decisions +- *Simplicity.* The method requires no computational or analytical expertise + +**Weaknesses:** +- *Narrow framing.* A pros-and-cons list evaluates one option (do it vs. don't) rather than comparing multiple alternatives. It is inherently binary +- *Unweighted factors.* Every item on the list counts equally. A "con" worth $50,000 occupies the same visual space as a "con" worth $5 million +- *Vulnerability to cognitive bias.* Overconfidence, the illusion of control, and the framing effect all operate freely within the format. The simplicity that makes the list accessible is the same simplicity that leaves it undefended against distortion + +**When to use it:** As a preliminary thinking aid -- a first pass that surfaces the dimensions worth analysing. Never as the final evaluation instrument for a consequential decision. + +**How to strengthen it:** If a pros-and-cons list must be used, assign explicit weights (1-10) to each factor and multiply by a confidence estimate. This converts the list from a ballot count into a rough weighted scoring model. The result is still imperfect, but materially less misleading. + +### Tool 3: The Even Swaps Method + +Developed by Hammond, Keeney, and Raiffa, the Even Swaps method provides a rational mechanism for making trade-offs among objectives that use entirely different units of measurement -- money versus time versus market share versus risk. The core insight: if you can make two alternatives equivalent on one dimension, that dimension drops out of the decision. Eliminate enough dimensions, and a clear winner emerges. + +**The process:** + +**Step 1: Build a consequences table.** List objectives down the left side, alternatives across the top. In each cell, describe the consequence of that alternative for that objective, using consistent units within each row. + +**Step 2: Eliminate dominated alternatives.** If Alternative A is better than Alternative B on some objectives and no worse on all others, B is dominated and can be removed. Use a ranking table (replace descriptions with ordinal ranks) to make dominance visible in complex matrices. + +**Step 3: Make even swaps.** Select two alternatives and an objective where they differ. Ask: "What change in Objective X would compensate for the difference in Objective Y?" Adjust one alternative's consequence accordingly. Now both alternatives are equivalent on Objective Y, which can be eliminated from consideration. + +**Step 4: Iterate.** Repeat until one alternative dominates all others or only one objective remains. + +**Example:** A Brazilian cola company choosing between franchising (lower profit, higher market share) and not franchising (higher profit, lower market share) determines that a three-percent increase in market share compensates for $15 million in lost profit. Adjusting the non-franchising alternative by swapping $15M profit for 3% market share makes profit equivalent across both options. The decision reduces to market share alone -- and franchising wins. + +The method's power lies in forcing explicit value judgments. Most decision-makers never articulate how much of one objective they would sacrifice for another. The Even Swaps method makes these trade-offs visible, discussable, and auditable. + +### Tool 4: The CARVER Risk Assessment + +CARVER is a six-criteria scoring system originally developed during World War II for targeting analysis, now widely adopted in corporate risk management and strategic planning. It converts qualitative risk judgments into a comparable numeric framework. + +| Criterion | Assesses | Score 1 (low) | Score 5 (high) | +|-----------|----------|---------------|----------------| +| **C**riticality | How essential the asset/initiative is to operations | Loss would not affect operations | Loss would halt operations | +| **A**ccessibility | How exposed the asset is to threats or competition | Extremely difficult to access or replicate | Easily accessed or replicated | +| **R**ecoverability | How quickly operations recover after loss | Replaced immediately, no downtime | Extremely difficult to replace, long downtime | +| **V**ulnerability | How well the asset withstands attack or disruption | Highly resilient | Highly vulnerable | +| **E**ffect | Broader impact across the business if compromised | No unfavourable impact | Very high economic, political, or social impact | +| **R**ecognizability | How visible the asset is as a target to adversaries | Not recognisable as valuable | Immediately recognisable | + +Each asset, initiative, or option is scored 1-5 on all six criteria. The sum (maximum 30) provides a comparable risk ranking. The framework is equally useful for offensive analysis (which competitor vulnerability to exploit, which market to enter) and defensive analysis (which asset to protect, which risk to mitigate first). + +**Entrepreneurial applications:** +- Compare two market-entry strategies by scoring each on all six CARVER criteria +- Assess which product line is most vulnerable to competitive disruption +- Prioritise security and operational investments across multiple locations or business units +- Defend a budget request to a board by presenting the numeric scoring alongside the qualitative reasoning + +### Tool 5: Deciding with Limited Data + +Most entrepreneurial decisions are made under conditions of radical uncertainty -- limited data, ambiguous signals, and time pressure that forecloses extended analysis. Two models from decision science address this reality. + +**Satisficing.** Herbert Simon's concept: rather than optimising (evaluating all options to find the best), establish minimum acceptable thresholds on key criteria and select the first option that meets all of them. The method is rational, not lazy -- it recognises that the cost of extended search often exceeds the marginal value of finding a marginally better option. A founder hiring a first engineer does not need the best engineer on earth; the founder needs an engineer who clears the threshold on technical skill, cultural fit, and availability within the next thirty days. + +**Recognition-Primed Decision-Making (RPD).** Gary Klein's research on fire commanders, military officers, and emergency physicians revealed that experienced decision-makers rarely compare options at all. Instead, they recognise the current situation as similar to one they have encountered before, mentally simulate the first plausible course of action, and execute if the simulation does not reveal fatal flaws. RPD is fast because it leverages pattern recognition built through years of domain experience. It is dangerous when applied outside one's domain or in novel situations that merely resemble familiar ones. + +**When each applies:** + +| Condition | Preferred Model | +|-----------|----------------| +| Many options, moderate time pressure, clear minimum thresholds | Satisficing | +| Few options, severe time pressure, deep domain experience | Recognition-primed decision-making | +| Novel situation, no domain experience, sufficient time | Neither -- use structured analytical methods (Even Swaps, CARVER) | + +### Tool 6: When to Trust Intuition + +Connson Chou Locke's framework identifies three conditions that must hold simultaneously for intuition to be reliable. When any condition is absent, intuition is unreliable and analytical methods should take precedence. + +**Condition 1: Domain expertise.** Roughly ten years of deliberate practice in the specific domain, with repetition and feedback, are required to develop accurate intuitive judgment. A financial history professor's expertise does not extend to financial investment decisions. A successful B2B founder's intuition about consumer products is untested and therefore untrustworthy. + +**Condition 2: Unstructured problem.** Intuition excels on problems that lack clear decision rules or objective criteria -- aesthetic judgments, political judgments, interpersonal dynamics. Problems with abundant data and clear rules are better served by algorithms, which outperform even experienced doctors in medical diagnosis because the human brain, facing large datasets, defaults to heuristics that introduce error. + +**Condition 3: Time scarcity.** When the decision window is narrow and information is sparse, intuition may perform as well as analysis because there is insufficient data for analysis to exploit its advantage. However, time pressure alone does not validate intuition -- it merely removes the option of thorough analysis. + +**The danger zone:** Intuition feels equally confident regardless of whether the conditions are met. The factory foreman who has spent twenty years reading a production floor has earned the right to trust a gut feeling about safety. The first-time founder who "just knows" that consumers will pay $200 for an untested product has not. The subjective sensation is identical; the reliability is not. + +**The synthesis:** Use intuition to narrow the field, then subject the shortlisted options to analytical evaluation. Or use analysis to identify a few equally strong options, then let informed intuition break the tie. The error is not in using intuition at all -- it is in using intuition as a substitute for analysis when the conditions for reliable intuition are absent. + +--- + +## Prompts + +**Prompt 1 -- Joint Evaluation Matrix:** +> "I am evaluating [number] options for [decision] at my [stage] [sector] company. The options are: [list]. The objectives I care about are: [list]. Build a consequences table with options as columns and objectives as rows. Identify any dominated alternatives. Then recommend whether the remaining options should be evaluated using Even Swaps, CARVER, or weighted scoring, and explain why." + +**Prompt 2 -- Even Swaps Walkthrough:** +> "I am choosing between [Option A] and [Option B]. Option A is better on [objective 1] but worse on [objective 2]. Walk me through the Even Swaps method: What change in [objective 1] would compensate for the difference in [objective 2]? Make the swap explicit, eliminate the now-irrelevant objective, and identify which option dominates. If neither dominates, suggest the next swap." + +**Prompt 3 -- CARVER Risk Scoring:** +> "I need to compare the risk profiles of [two or more options/assets/markets]. Score each on the six CARVER criteria (Criticality, Accessibility, Recoverability, Vulnerability, Effect, Recognizability) on a 1-5 scale. Explain each score. Identify which option has the highest total risk score and recommend mitigation strategies for the top-scoring criteria." + +**Prompt 4 -- Intuition Calibration:** +> "I have a strong gut feeling about [decision]. Before I act on it, calibrate my intuition against Locke's three conditions: (1) Do I have genuine domain expertise (ten-plus years of relevant experience with feedback)? (2) Is this an unstructured problem or one with clear data and rules? (3) Is time genuinely scarce, or am I using urgency as an excuse to avoid analysis? Based on this calibration, recommend whether I should trust my intuition, override it, or use it alongside a structured method." + +--- + +## Use Cases + +**Series A SaaS Company Choosing Between Two Acquisition Targets** + +A vertical SaaS company in the logistics space evaluates acquiring either a competitor (overlapping customer base, complementary product) or a data-analytics startup (different customer base, adjacent technology). A consequences table with seven objectives (revenue synergy, technology fit, integration complexity, cultural alignment, customer overlap, price, and time to close) reveals that the competitor dominates on four objectives and ties on one but loses on technology fit and price. The Even Swaps method asks: how much technology advantage would compensate for the competitor's price premium? The team determines that the competitor's existing customer relationships, which would take three years to build organically, are worth more than the $2M price difference. A swap of $2M in price for three years of customer acquisition time makes price equivalent. Technology fit becomes the sole remaining differentiator -- but applying the CARVER framework to the analytics startup reveals a Recoverability score of 5 (the three key engineers could leave post-acquisition, and the technology would be extremely difficult to maintain). The competitor wins. + +**Pre-Seed Founder Deciding Whether to Trust a Market Intuition** + +A founder with twelve years of experience in enterprise security "just knows" that mid-market companies will pay for an automated compliance tool. Applying the intuition calibration: (1) Domain expertise -- yes, twelve years in the specific domain with direct customer feedback. (2) Unstructured problem -- partially; the question of whether a market exists for a new product category has both quantitative indicators (market size, competitor revenue) and qualitative dimensions (buyer psychology, urgency of pain). (3) Time scarcity -- no; the founder has not yet committed capital and has time to validate. Recommendation: the founder's intuition is credible enough to warrant action but not sufficient to skip validation. Use the gut feeling to select the beachhead market, then subject the hypothesis to structured analysis (customer interviews, willingness-to-pay tests, competitive mapping) before committing significant resources. + +**Growth-Stage E-Commerce Brand Comparing Three Fulfilment Strategies** + +A D2C brand at $15M ARR evaluates three fulfilment options: build an in-house warehouse, partner with a third-party logistics provider, and a hybrid model. The team's default approach -- a pros-and-cons list for each option -- produces three lists of unweighted factors that are impossible to compare. Switching to joint evaluation (all three options in a single table) immediately reveals that the hybrid model is practically dominated by the 3PL option: it has similar costs, worse operational complexity, and only a marginal advantage in brand control. Eliminating the hybrid reduces the decision to two options. The Even Swaps method asks: how much brand control would compensate for the $800K annual cost difference between in-house and 3PL? The team determines that brand control matters only for the premium product line (30% of revenue). An Even Swap of $800K for brand control over 30% of SKUs makes cost equivalent. The remaining differentiator is speed of implementation -- and the 3PL can launch in six weeks versus nine months for in-house. The 3PL wins, with a contract clause preserving the option to bring premium fulfilment in-house within eighteen months. + +--- + +## Anti-Patterns + +**Using pros-and-cons lists as the final evaluation method for consequential decisions.** The list is a brainstorming aid, not a decision tool. When the stakes are high -- hiring a co-founder, entering a market, accepting investment terms -- the unweighted, unstructured format of the list creates exactly the conditions under which cognitive biases thrive. + +**Evaluating options sequentially when joint evaluation is feasible.** Reviewing one candidate resume, forming an impression, and then reviewing the next is twenty-two percent less effective than reviewing all resumes simultaneously. The sequential approach feels thorough; it is measurably inferior. + +**Applying Even Swaps without first building a consequences table.** The method requires explicitly defined objectives and clearly described consequences. Attempting Even Swaps from memory or from informal notes introduces precisely the imprecision the method is designed to eliminate. + +**Trusting intuition in novel domains.** The first-time founder entering a market with no prior experience, the engineer making a marketing judgment, the operator making a financial projection -- all are applying intuition in domains where it has not been calibrated. The subjective confidence is indistinguishable from calibrated intuition; the accuracy is not. + +**Over-engineering evaluation for reversible decisions.** A full CARVER analysis for a landing page design or a Slack channel name is a misallocation of analytical capacity. Reserve structured evaluation for decisions where the cost of choosing wrong exceeds the cost of choosing carefully. For two-way doors, satisficing is the appropriate model. + +**Ignoring the intangible criteria in CARVER scoring.** The "Effect" criterion captures second-order consequences -- reputational damage, employee morale, regulatory exposure -- that rarely appear in financial models. Scoring Effect as a 1 because the impact is non-financial is a category error that systematically underweights the criteria that matter most in high-stakes decisions. + +--- + +## By Stage + +| Stage | Primary Evaluation Challenge | Recommended Tools | +|-------|------------------------------|-------------------| +| Idea | Few options, radical uncertainty, minimal data. The founder is evaluating whether to pursue the idea at all. | Intuition calibration (is the founder's domain expertise sufficient to trust the gut?), satisficing (does the opportunity clear minimum thresholds on market size, founder-market fit, and feasibility?). | +| Validation | Multiple MVP approaches, customer segments, or pricing strategies to evaluate. Data is emerging but thin. | Joint evaluation of alternatives in a single consequences table. Could-vs-should thinking from the generating-solutions skill feeds into structured comparison here. Recognition-primed decision-making applies if the founder has deep domain experience. | +| Early Traction | Hiring, partnership, and product-roadmap decisions multiply. Each involves trade-offs across dimensions that resist direct comparison. | Even Swaps for trade-off-heavy decisions (e.g., hire a generalist vs. a specialist -- what skill breadth compensates for depth, and vice versa?). CARVER for assessing operational risks as complexity increases. | +| Growth | Strategic decisions (market entry, acquisition, platform migration) with long time horizons and high irreversibility. Multiple stakeholders with competing objectives. | Full Even Swaps process with a formal consequences table. CARVER for risk-ranking initiatives across the portfolio. Joint evaluation is non-negotiable -- no strategic decision should be evaluated in isolation. | +| Scale | Decisions are made across the organisation by people distant from the original context. Evaluation frameworks must be communicable and auditable. | Institutionalised consequences tables and CARVER assessments that create a paper trail. The intuition calibration framework becomes a coaching tool: training managers to recognise when their gut is calibrated and when it is not. | + +A pattern across stages: the ratio of intuition to analysis should shift as data accumulates. At the idea stage, intuition (if domain-calibrated) may be the most efficient tool. At scale, the volume and availability of data make analytical methods both feasible and superior. The founder who trusted intuition at inception and still trusts it at $100M ARR has not evolved with the business -- the business has outgrown the founder's pattern library. + +--- + +## Output Template + +```markdown +# Option Evaluation Record + +**Decision:** [one-sentence description] +**Date:** [date] +**Evaluation method(s) used:** [joint evaluation / Even Swaps / CARVER / intuition calibration / satisficing / combination] + +## Consequences Table (Joint Evaluation) + +| Objective | Weight (1-10) | Option A | Option B | Option C | +|-----------|---------------|----------|----------|----------| +| [objective 1] | [weight] | [consequence] | [consequence] | [consequence] | +| [objective 2] | [weight] | [consequence] | [consequence] | [consequence] | +| [objective 3] | [weight] | [consequence] | [consequence] | [consequence] | + +## Dominated Alternatives +- [Option X] dominated by [Option Y] because: [reasoning] + +## Even Swaps (if applicable) +- **Swap 1:** Changed [Option A]'s [Objective X] from [value] to [value] to compensate for difference in [Objective Y]. Objective Y eliminated. +- **Swap 2:** [repeat as needed] +- **Remaining differentiator:** [the objective that determines the final choice] + +## CARVER Risk Scores (if applicable) + +| Option | C | A | R | V | E | R | Total | +|--------|---|---|---|---|---|---|-------| +| Option A | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [sum] | +| Option B | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [sum] | + +## Intuition Check +- **Domain expertise present?** [yes/no -- years, specific domain] +- **Problem type:** [structured / unstructured / mixed] +- **Time pressure:** [genuine / artificial] +- **Intuition reliability verdict:** [trust / override / use alongside analysis] + +## Decision +**Chosen option:** [X] +**Primary reasoning:** [which evaluation method drove the choice and why] +**Confidence level:** [low / moderate / high] +**Key risk to monitor:** [the highest-scoring CARVER criterion or the weakest Even Swap assumption] +``` + +--- + +## Related Skills + +- **[Decision Traps and Roles](../../content/skills/decisions/decision-traps-and-roles.md)** -- The cognitive traps (anchoring, confirming evidence, framing) that distort evaluation are catalogued here along with counter-routines to apply before and during any evaluation. +- **[Generating Solutions](../../content/skills/decisions/generating-solutions.md)** -- The prerequisite: alternatives must be generated before they can be evaluated; this sibling skill covers brainstorming failure modes, BrainSwarming, and question bursts. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The 3-Lens Principle complements the Even Swaps method by surfacing second-order consequences and hidden opportunity costs. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- Covers margin of safety, irreversibility tests, execution fail-safes, and decision journals -- the phases that follow option evaluation. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's prospect theory explains why the framing trap distorts evaluation and why loss aversion makes people risk-seeking in the domain of losses. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- When evaluation involves bilateral value division, the Nash Product Solution provides the mathematical framework for identifying optimal splits between parties. diff --git a/plugins/foreman/skills/evolutionary-strategy/SKILL.md b/plugins/foreman/skills/evolutionary-strategy/SKILL.md deleted file mode 120000 index b6a0e61..0000000 --- a/plugins/foreman/skills/evolutionary-strategy/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/evolutionary-strategy.md \ No newline at end of file diff --git a/plugins/foreman/skills/evolutionary-strategy/SKILL.md b/plugins/foreman/skills/evolutionary-strategy/SKILL.md new file mode 100644 index 0000000..da870a1 --- /dev/null +++ b/plugins/foreman/skills/evolutionary-strategy/SKILL.md @@ -0,0 +1,252 @@ +--- +name: "evolutionary-strategy" +description: "Applies evolutionary game theory to competitive strategy and market dynamics. Models markets as populations of players adopting different strategies, using the Hawk-Dove game for aggression calibration, follow-the-crowd dynamics for herding analysis, and Evolutionarily Stable Strategy (ESS) for predicting which competitive behaviours persist. Use when choosing between aggressive and cooperative market positioning, analysing industry convergence or fragmentation, timing market entry, understanding why competitors behave as they do, evaluating whether a disruptive strategy can break an established equilibrium, or diagnosing herding behaviour in a market." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - evolutionary-game-theory + - hawk-dove + - competitive-strategy + - market-dynamics + - ess + - herding + - disruption + - game-theory +related_skills: + - coalition-and-partnership-games + - negotiation-game-theory + - porters-five-forces + - blue-ocean-strategy + - disruptive-innovation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Evolutionary Strategy + +Every market contains hawks and doves. Hawks compete aggressively -- slashing prices, litigating against rivals, poaching talent, flooding channels. Doves accommodate -- differentiating peacefully, sharing ecosystem value, avoiding direct confrontation. The question for any entrepreneur is not which species they are by temperament, but what the current population ratio demands. A market saturated with hawks rewards the dove who sidesteps the carnage. A market of complacent doves rewards the hawk who seizes territory while others graze. Evolutionary game theory, originally developed by John Maynard Smith and George Price in 1973 to explain animal conflict, provides the formal apparatus for this calculation -- and its predictions about competitive dynamics are remarkably precise. + +--- + +## The Framework + +### Evolutionarily Stable Strategy (ESS) + +Classical game theory assumes rational players making optimal decisions with full information. Evolutionary game theory assumes something closer to reality: large populations of players with imperfect information who learn through trial and error, imitation, and adaptation. Over time, strategies that produce above-average payoffs spread through the population (more companies adopt them), while strategies that underperform shrink (companies using them fail or switch). + +An **Evolutionarily Stable Strategy** is a strategy that, once adopted by the majority of a market, cannot be invaded by any small group of entrants playing a different strategy. An ESS is self-reinforcing: the more players adopt it, the harder it is to succeed with an alternative. + +The practical test for any competitive strategy: **if every competitor adopted this approach, would a small entrant playing differently gain an advantage?** If yes, the strategy is not evolutionarily stable, and the market will eventually shift. If no, the strategy is an ESS, and entrants must either adopt it or find a way to fundamentally change the game's payoff structure. + +### The Hawk-Dove Game: Calibrating Aggression + +The Hawk-Dove game is the foundational model for competitive intensity. Two players compete for a resource of value *v*. Each chooses to be a Hawk (fight aggressively) or a Dove (concede gracefully). + +**Payoff structure:** + +| | Opponent Plays Hawk | Opponent Plays Dove | +|---|---|---| +| **You Play Hawk** | Both fight: 50% chance of winning *v*, 50% chance of losing *c* (cost of conflict). Average payoff: *(v - c) / 2* | You win the full resource: payoff *v* | +| **You Play Dove** | You concede: payoff *0* | Split the resource: payoff *v / 2* | + +The critical ratio is *v/c* -- the value of the prize relative to the cost of fighting. + +**When the prize exceeds the cost of fighting (v > c):** Hawk is the dominant strategy. Aggression pays even against other hawks, because winning is worth the risk of losing. The ESS is all-hawk. Every company competes aggressively. This describes markets with large prize pools and low conflict costs -- think digital advertising, where customer acquisition costs are modest relative to lifetime value. + +**When the cost of fighting exceeds the prize (c > v):** Neither all-hawk nor all-dove is stable. The ESS is a *mixed population* where the proportion of hawks settles at *v/c*. Too many hawks, and the cost of conflict exceeds the prize -- doves do better by avoiding fights. Too few hawks, and the unchallenged resources attract new aggressors. The market oscillates toward an equilibrium ratio. + +**The entrepreneur's decision framework:** + +| Market Condition | Hawk Density | Your Optimal Play | Rationale | +|-----------------|-------------|-------------------|-----------| +| Crowded market, high conflict costs | High (many aggressive players) | Dove (differentiate, avoid direct competition) | Adding another hawk increases everyone's costs without increasing total value | +| Complacent market, low conflict costs | Low (most players are passive) | Hawk (aggressive entry, take share) | Unchallenged resources are available for the taking | +| Emerging market, uncertain value | Mixed | Conditional (hawk against doves, dove against hawks) | Flexibility is the only stable approach when the equilibrium has not yet formed | +| Mature market at equilibrium | Stable *v/c* ratio | Match the ratio unless you can change *v* or *c* | Deviating from the equilibrium ratio without changing the underlying economics is a losing strategy | + +### Follow-the-Crowd Dynamics: Market Herding + +Coordination games produce a different evolutionary pattern. In some markets, companies benefit from adopting the same strategy as the majority -- using the same technology standard, targeting the same customer segment, adopting the same pricing model. The follow-the-crowd dynamic produces **herding**: once a majority tips toward one strategy, the minority faces increasing pressure to conform. + +The payoff structure for coordination games creates two stable equilibria (everyone coordinates or everyone acts independently) and one unstable tipping point between them. Below the tipping point, the crowd gravitates toward independence. Above it, the crowd converges on coordination. + +**The tipping-point decision table:** + +| Market Adoption of Strategy X | Your Payoff from Adopting X | Your Payoff from Staying Independent | Rational Choice | +|-------------------------------|---------------------------|--------------------------------------|----------------| +| Below 50% adoption | Low (few partners, limited network effects) | Higher (independence has fewer costs) | Stay independent | +| At 50% adoption | Equal | Equal | Tipping point -- unstable | +| Above 50% adoption | High (network effects, ecosystem benefits) | Lower (isolation penalty) | Adopt X | + +**Entrepreneur implications:** + +Platform choices, technology standards, and go-to-market models all exhibit follow-the-crowd dynamics. Choosing a platform before it reaches the tipping point is a bet on which equilibrium the market will select. Choosing after the tipping point is confirmation, not strategy. The asymmetric opportunity lies in recognising which side of the tipping point the market currently occupies -- and whether any force (a dominant player's announcement, regulatory action, a technology breakthrough) is about to push it across. + +### Central-Tendency Games and Market Convergence + +The Hawk-Dove game has an interior equilibrium -- the population settles at a ratio between the extremes. This produces the central-tendency effect observed in many competitive markets: competitors cluster in the middle of the strategy space. + +Harold Hotelling demonstrated in 1929 that two competing sellers on a linear market will rationally locate next to each other at the centre -- even though distributing evenly would better serve customers. The logic extends beyond geography: competitors converge on pricing, features, positioning, and messaging because deviating from the centre risks ceding the majority of the market to the rival who stays central. + +This convergence is the evolutionary explanation for why: +- Most SaaS products in a category converge on similar feature sets +- Pricing within a market clusters in a narrow band +- Competing startups' pitch decks become nearly interchangeable +- Fast-food restaurants cluster on the same intersection + +The convergence is stable -- but only for two competitors. With three or more, the equilibrium breaks down. There is no stable positioning when three competitors try to occupy the centre simultaneously; at least one is always squeezed out. This mathematical result has a direct strategic implication: **in markets with more than two major competitors, pure central-positioning strategies are unstable.** Differentiation becomes necessary not as a branding exercise but as an evolutionary imperative. + +### When Disruption Succeeds: Breaking Evolutionary Stability + +An ESS, by definition, resists invasion by small groups of entrants playing differently. Disruption succeeds only when the entrant changes the payoff structure of the game itself -- not by playing the existing game better, but by making the existing strategies less effective. + +**Three mechanisms for breaking an ESS:** + +1. **Change the value of the prize (*v*).** Create a new category or redefine the prize. Airbnb did not compete for hotel rooms (the existing prize); it redefined the prize as "accommodation experiences," changing *v* for both hawks and doves in the hospitality market. + +2. **Change the cost of conflict (*c*).** Reduce the cost of aggressive competition or raise it. Open-source software reduced the cost of competing against proprietary vendors to near zero. Patent trolls raised the cost of conflict for everyone. Either change shifts the hawk-dove equilibrium. + +3. **Change the population structure.** Introduce a new type of player that does not fit the existing hawk-dove categorisation. Platform businesses (Uber, Airbnb, Amazon Marketplace) introduced a third player type -- the marketplace -- that transformed bilateral competition into a platform dynamics game with entirely different evolutionary pressures. + +If a startup cannot execute one of these three mechanisms, it is entering an evolutionarily stable market and should expect the existing equilibrium to resist its entry. The ESS framework does not say disruption is impossible. It specifies the conditions under which it can succeed. + +--- + +## Prompts + +**Prompt 1 -- Competitive Posture Assessment:** +> My company operates in [describe market/industry]. The main competitors are [list competitors and their strategies -- aggressive/cooperative/mixed]. Using the Hawk-Dove framework, help me assess: (1) What is the current hawk-to-dove ratio in this market? (2) Is the market at, above, or below the evolutionary equilibrium? (3) Given the prize value (market size, margins) and cost of conflict (price wars, customer acquisition cost, legal battles), what is the optimal competitive posture for a new or growing player? (4) What specific actions would constitute hawk versus dove behaviour in this market? + +**Prompt 2 -- Market Herding Analysis:** +> I am observing convergence in [describe market]: competitors are [describe the herding behaviour -- similar pricing, same features, same channels]. Using evolutionary game theory's follow-the-crowd model, help me analyse: (1) Has the market passed the tipping point? (2) What is the payoff for conforming versus differentiating at the current adoption level? (3) Are there structural forces (network effects, standards, regulation) that make convergence an ESS? (4) If I want to differentiate, what conditions must hold for a divergent strategy to be viable? + +**Prompt 3 -- Disruption Viability Test:** +> I am planning to disrupt [describe incumbent market/players]. My approach is [describe strategy]. Using the ESS framework, evaluate: (1) Is the current market an evolutionarily stable equilibrium? (2) Which of the three disruption mechanisms am I employing -- changing the prize value, changing the cost of conflict, or changing the population structure? (3) Is my approach sufficient to break the existing ESS, or am I merely entering the existing game as a new player (in which case the equilibrium will resist me)? (4) What would need to be true for my disruption to succeed? + +**Prompt 4 -- Market Timing Through Evolutionary Lens:** +> I am considering entering [describe market] at [describe timing -- early, growth phase, mature]. Using evolutionary dynamics, help me assess: (1) What evolutionary phase is the market in (pre-equilibrium formation, approaching equilibrium, stable equilibrium, disruption-in-progress)? (2) What strategy (hawk/dove/conditional) is optimal for this phase? (3) What signals should I monitor to detect phase transitions? (4) What is the risk that the equilibrium shifts before I reach scale? + +--- + +## Use Cases + +**Validation-Stage: Entering a Market of Aggressive Incumbents** + +A fintech startup plans to offer small-business lending, a market dominated by three aggressive players engaged in relentless customer acquisition spending. Customer acquisition costs have tripled in two years. The incumbents are all hawks -- competing primarily on speed, marketing spend, and broker commissions. + +Evolutionary analysis: the cost of conflict (*c* -- CAC, broker fees, margin compression) now exceeds the prize value (*v* -- lifetime value per customer minus servicing costs) for many customer segments. The hawk-hawk payoff is negative. The market is over-hawked. + +Optimal entry strategy: dove. Target the segments the hawks are fighting over least intensely (underserved niches with lower LTV that the incumbents' unit economics cannot support). Build through referral networks and embedded partnerships rather than paid acquisition. Avoid direct confrontation until scale provides cost advantages that shift the personal *v/c* ratio. + +The startup's first investor pitch asked "how will you outspend the incumbents?" The evolutionary framework reframes: "why would we fight the war that is bankrupting the combatants?" + +**Growth-Stage: Platform Standard Convergence** + +A developer-tools company built its product on a proprietary integration protocol. The market is converging on an open standard that three of five major competitors have adopted. Adoption is at 55% -- just past the evolutionary tipping point. + +Follow-the-crowd analysis: above the tipping point, the payoff for conforming (ecosystem compatibility, shared tooling, talent pool familiarity) exceeds the payoff for independence (differentiation, lock-in, proprietary advantage). The tipping point is behind them. The market will converge. + +The company faces a choice: adopt the standard now (accepting short-term migration costs) or resist (hoping to maintain differentiation). Evolutionary dynamics predict that resistance is a losing strategy once the tipping point is crossed. Every additional competitor that adopts the standard increases the isolation penalty for holdouts. The rational choice is adoption -- and the sooner, the lower the switching cost. + +The company pivots its differentiation from the protocol layer (where convergence is inevitable) to the application layer (where the Hawk-Dove dynamic still permits differentiation). + +**Scale-Stage: Breaking an Industry Equilibrium** + +A logistics company identifies that the freight brokerage industry operates at a stable Hawk-Dove equilibrium: large brokers compete aggressively on price for high-volume shippers (hawks), while smaller brokers serve niche segments cooperatively (doves). The equilibrium has held for fifteen years. + +Rather than entering as a hawk (undercutting on price) or a dove (serving a niche), the company changes the game's payoff structure by building a technology platform that automates the matching function brokers traditionally perform. This changes the cost of conflict (technology reduces matching costs to near zero, making the price-competition game less costly) and changes the population structure (the platform is neither hawk nor dove but a new player type that profits from transaction volume regardless of competitive dynamics). + +The existing ESS is destabilised not because a better hawk or dove arrived, but because the game itself changed. Incumbents' evolved strategies -- optimised for the old game -- become maladapted to the new one. + +--- + +## Anti-Patterns + +1. **Confusing Temperament with Strategy.** Choosing hawk or dove based on the founder's personality rather than the market's evolutionary dynamics. An aggressive founder in an over-hawked market will bleed capital. A cautious founder in an under-hawked market will miss available territory. The framework demands that posture follow analysis, not disposition. + +2. **Fighting an ESS Head-On.** Entering an evolutionarily stable market with the same strategy the incumbents use, expecting to execute it better. An ESS resists invasion by definition. A slightly better hawk in a stable hawk equilibrium will be ground down by the collective response. The entrant must either change the game (disrupt the payoff structure) or accept the equilibrium and find an underserved niche within it. + +3. **Mistaking Herding for Validation.** Interpreting market convergence as proof that the converged strategy is correct. Follow-the-crowd dynamics produce convergence regardless of whether the converged strategy is globally optimal. Markets can herd toward suboptimal equilibria -- the coordination benefit of conformity can outweigh the absolute benefit of a superior but isolated strategy. The question is not "is everyone doing this?" but "is this the Pareto-optimal equilibrium?" + +4. **Ignoring Evolutionary Speed.** Assuming market dynamics are static when they are changing. A market approaching its hawk-dove equilibrium from an over-hawked state is a declining environment for new hawks but an improving one for doves. A market post-disruption is in disequilibrium, where early movers can claim territory before a new ESS forms. Timing strategy to evolutionary phase transitions -- not to static snapshots -- is essential. + +5. **Applying Hawk-Dove to Cooperative Markets.** Using competitive aggression frameworks in markets that are fundamentally coordination games. Developer ecosystems, multi-sided platforms, and standards-driven industries reward coordination, not competition. Playing hawk in a coordination game destroys the ecosystem and the hawk along with it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Assessing market equilibrium before entry | The primary question is whether the market has reached an ESS and what type. If stable, the entrant must identify a disruption mechanism or an underserved niche. If pre-equilibrium, there is an opportunity to shape the emerging dynamics. | +| Early Traction | Choosing competitive posture | With initial market presence, the company must commit to a hawk or dove posture (or a conditional strategy). The choice should be driven by the current population ratio and the company's cost structure, not by aspiration. | +| Growth | Navigating convergence and herding | Growth-stage companies face platform choices, standard adoption decisions, and ecosystem alignment. Follow-the-crowd analysis determines whether to conform or differentiate. Misreading the tipping point -- conforming too early or too late -- is the primary risk. | +| Scale | Sustaining or disrupting equilibria | At scale, the company is part of the equilibrium. Its actions affect the market's evolutionary dynamics. Strategic choices (pricing, M&A, platform openness) should account for how they shift the hawk-dove ratio and whether they risk destabilising a favourable equilibrium. | + +--- + +## Output Template + +```markdown +# Evolutionary Strategy Analysis: [Market/Industry] + +## Market Characterisation +- **Market type:** [Hawk-Dove competition / Coordination game / Mixed] +- **Current evolutionary phase:** [Pre-equilibrium / Approaching ESS / Stable ESS / Post-disruption disequilibrium] +- **Estimated hawk-to-dove ratio:** [X% hawks, Y% doves] + +## Payoff Structure +| Matchup | Payoff Description | Estimated Magnitude | +|---------|-------------------|---------------------| +| Hawk vs Hawk | [Describe: price war, talent poaching, etc.] | [Gain/Loss estimate] | +| Hawk vs Dove | [Describe: market capture] | [Gain estimate for hawk] | +| Dove vs Hawk | [Describe: concession] | [Gain/Loss for dove] | +| Dove vs Dove | [Describe: market sharing] | [Gain estimate for each] | + +## Prize vs Conflict Analysis +- **Prize value (v):** [Market size, margins, LTV per customer] +- **Conflict cost (c):** [CAC inflation, legal costs, margin erosion, talent costs] +- **v/c ratio:** [Value] -- indicates [all-hawk ESS / mixed equilibrium at v/c ratio / dove-dominant] + +## Competitive Posture Recommendation +- **Recommended strategy:** [Hawk / Dove / Conditional / Game-changer] +- **Rationale:** [Based on current population ratio and v/c analysis] +- **Specific actions:** + 1. [Action aligned with recommended posture] + 2. [Action aligned with recommended posture] + 3. [Action aligned with recommended posture] + +## Herding and Convergence Assessment +- **Is convergence occurring?** [Yes/No] +- **Tipping point status:** [Below / At / Above] +- **Conform or differentiate?** [Recommendation with rationale] + +## Disruption Feasibility (if applicable) +- **Disruption mechanism:** [Change v / Change c / Change population structure] +- **Feasibility:** [High / Medium / Low] +- **Key assumption that must hold:** [Describe] + +## Monitoring Signals +- [Signal that indicates phase transition approaching] +- [Signal that hawk-dove ratio is shifting] +- [Signal that herding tipping point is near] +``` + +--- + +## Related Skills + +- **[Coalition and Partnership Games](../../content/skills/game-theory/coalition-and-partnership-games.md)** -- In markets where evolutionary dynamics favour cooperation, coalitional game theory provides the tools for structuring partnerships and alliances that emerge from dove strategies. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- Individual negotiations occur within the broader evolutionary context; the Nash Product Solution applies within the constraints the market's hawk-dove equilibrium imposes on deal terms. +- **[Prisoner's Dilemma and Cooperation](../../content/skills/game-theory/prisoners-dilemma-and-cooperation.md)** -- The one-shot dilemma becomes an evolutionary game when played repeatedly across a population, revealing how tit-for-tat and other strategies emerge and stabilise. +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Five Forces analyses industry structure at a point in time; evolutionary game theory analyses how that structure changes over time as competitive strategies evolve. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Blue Ocean's "make the competition irrelevant" is the strategic expression of changing the game's payoff structure to break an existing ESS. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Christensen's disruption theory describes the what; evolutionary game theory provides the mathematical why, as incumbent strategies are ESS-locked. diff --git a/plugins/foreman/skills/finding-your-stories/SKILL.md b/plugins/foreman/skills/finding-your-stories/SKILL.md deleted file mode 120000 index 265e115..0000000 --- a/plugins/foreman/skills/finding-your-stories/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/finding-your-stories.md \ No newline at end of file diff --git a/plugins/foreman/skills/finding-your-stories/SKILL.md b/plugins/foreman/skills/finding-your-stories/SKILL.md new file mode 100644 index 0000000..4826fd6 --- /dev/null +++ b/plugins/foreman/skills/finding-your-stories/SKILL.md @@ -0,0 +1,234 @@ +--- +name: "finding-your-stories" +description: "Teaches three systematic methods for discovering story-worthy moments in everyday life: Homework for Life, Crash and Burn freewriting, and First Last Best Worst. Use when an entrepreneur feels they have no interesting stories to tell, when a leader needs fresh material for presentations and pitches, when preparing for fundraising and struggling to find a personal angle, or when building a long-term practice of narrative awareness." +version: "1.0.0" +category: "storytelling" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - homework-for-life + - freewriting + - story-discovery + - narrative + - daily-practice + - creativity + - pitch-preparation + - personal-narrative +related_skills: + - what-is-a-story + - story-structure-and-arc + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Finding Your Stories + +INVISIBLE GOLD -- You live through story-worthy moments every day but record none of them. Homework for Life is the mining operation. + +The framework behind this skill draws on a list of more than five hundred untold story ideas. Most professional storytellers have a handful. The gap is not talent or life experience. It is a system. Three techniques for extracting stories from the raw material of ordinary existence were discovered and codified. The techniques are disarmingly simple. Their cumulative effect is not. + +The core insight is counterintuitive enough to bear stating plainly: the most compelling stories are almost never the dramatic ones. They are small moments at a dining-room table, a two-in-the-morning walk with an ageing dog, a child's whispered sentence in the morning light. These moments happen constantly. They pass unnoticed because no one has trained themselves to see them. The dramatic events -- the near-death experiences, the arrests, the crises -- make serviceable stories, but audiences connect most deeply to the small and recognisable. Everyone has felt alone at two in the morning. Almost no one has been robbed at gunpoint. + +For entrepreneurs, this reframes the perennial complaint: "I don't have any good stories for my pitch." The stories are there. The problem is an untrained eye. + +--- + +## The Framework + +### Technique 1: Homework for Life + +Homework for Life is the signature practice. It is also, by the framework's own assessment, the single most important technique in the craft. The method: + +**At the end of every day, ask one question:** If I had to tell a five-minute story from today -- as benign, boring, or inconsequential as it might seem -- what would it be? + +**Write the answer in a spreadsheet.** Two columns: date and story. No more than a sentence or two. Not the full story -- just enough to recall the moment later. + +| Date | Story | +|------|-------| +| 11/5/15 | Taught Clara about the Rolling Stones while lying in bed with her. | +| 11/9/15 | Man gets in line at Southwest Airlines, has moment with me, now my best friend, now trying to skip line, now a jerk, but still, my only friend. | +| 11/14/15 | Clara makes snowman almost without my help. So proud. So afraid that she won't need me much longer. | + +The constraints are deliberate. A spreadsheet forces brevity. Brevity ensures the habit survives a busy day. Five minutes is the maximum investment. Miss one day and you permit yourself to miss two; miss two and you abandon the practice entirely. + +**What happens over time:** + +1. **A storytelling lens develops.** Within weeks, practitioners begin noticing story-worthy moments as they happen rather than retrospectively. Experienced practitioners report recognising most moments in real time. + +2. **Forgotten memories resurface.** Recording a present moment frequently triggers associations with the past. An entry about walking a dog in the rain at two in the morning triggered a forgotten childhood memory of a father disappearing underwater, and then a separate memory from a golf course at midnight. One entry. Three recovered stories. + +3. **Patterns emerge.** Seeing recurring themes across entries reveals truths about yourself that isolated incidents conceal. One practitioner discovered he fights with his wife not through words but through angry chore completion -- a pattern only visible across multiple entries. + +4. **Time slows.** Multiple practitioners report that the habit of daily reflection makes life feel longer and more significant. Throwaway days disappear. A woman who had never felt like "an important person in this world" called six months after starting the practice, crying, to say it had changed her life. She never gave her name. + +**The entrepreneurial application is direct.** A founder who has been doing Homework for Life for six months before a fundraise will have a reservoir of personal moments from which to draw. The moment a customer said something unexpected. The evening a co-founder's offhand remark reframed the entire product thesis. The morning the founder realised the team had been solving the wrong problem. These moments are the raw material of compelling pitches, and they are invisible without a system. + +### Technique 2: Crash and Burn (Freewriting) + +Crash and Burn is an adaptation of stream-of-consciousness writing, tuned specifically for story generation. Where Homework for Life captures the present, Crash and Burn excavates the past. + +**The method:** Set a timer for ten minutes. Write without stopping. Follow three rules: + +**Rule 1: Do not get attached to any idea.** When a new thought crashes in -- however unrelated or inferior it seems -- abandon the current thread immediately. The intersections between disparate ideas are where recovered memories and new stories live. + +**Rule 2: Do not judge.** Grammar, punctuation, penmanship, and quality are irrelevant. Everything lands on the page. The inner editor is locked outside the room. + +**Rule 3: The pen never stops.** When the mind empties, list colours (red, green, blue, black, brown...) or numbers in word form until a new thought triggers. The physical act of continuous writing keeps the associative engine running. + +A single ten-minute session produced six potential stories, three anecdotes, three possible articles, and one addition to his personal bucket list (committing a petty crime at sea to be technically classified as a pirate). The session began with the word "grape" and ended with an unopened letter from his father. + +**For entrepreneurs,** Crash and Burn is the pre-meeting preparation tool. Fifteen minutes of freewriting before a board meeting, investor conversation, or keynote produces not polished material but raw connections -- the unexpected link between a childhood memory and the company's origin, the forgotten conversation that crystallised the product vision. These connections, refined later, become the moments that separate a memorable pitch from a forgettable one. + +### Technique 3: First Last Best Worst + +Adapted from an idea by The Moth's artistic director Catherine Burns, First Last Best Worst is a structured prompt exercise. It works as a solo brainstorming tool, an improv game, and -- the text notes with practical enthusiasm -- an excellent activity for long car rides and first dates. + +**The method:** Create a grid. The columns are labelled First, Last, Best, and Worst. The rows are prompts -- any category of human experience. + +| Prompt | First | Last | Best | Worst | +|--------|-------|------|------|-------| +| Job | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Failure | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Customer | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Partnership | [Your answer] | [Your answer] | [Your answer] | [Your answer] | +| Risk | [Your answer] | [Your answer] | [Your answer] | [Your answer] | + +After completing the grid, analyse it with three questions: + +1. Do any entries appear more than once? (Recurring entries signal likely stories.) +2. Could any entry become a useful anecdote? +3. Could any entry become a fully realised story with a transformation? + +Testing showed that nineteen of twenty-eight entries from standard prompts yielded potential stories. Even when students deliberately chose uninteresting prompts (tree, toaster, socks, flag), eight stories emerged from twenty possibilities. + +**The entrepreneurial variant** replaces personal prompts with business ones: first customer, worst hire, best pivot, last rejection, worst meeting, first investor conversation. The grid fills in and fills out the founder's narrative landscape, connecting moments that seemed isolated into a coherent personal history of the venture. + +--- + +## Prompts + +**Prompt 1 -- Homework for Life Setup:** +> I want to start a daily story-finding practice. I am a [role] at a [type of company] at [stage]. Design a Homework for Life spreadsheet template for me with the two-column format (date, story) and provide ten example prompts I can use on days when nothing seems story-worthy. Also suggest three recurring themes I should watch for based on my role that are likely to produce material useful for [pitches / team talks / board updates / customer conversations]. + +**Prompt 2 -- Crash and Burn Session Guide:** +> I have a [pitch / keynote / team address] in [timeframe] on the topic of [topic]. Guide me through a Crash and Burn freewriting session. Give me a starting word related to my topic, then after I share my raw output, identify the threads worth saving: potential stories, anecdotes, recovered memories, and unexpected connections that could strengthen my [deliverable]. + +**Prompt 3 -- First Last Best Worst for Founders:** +> Generate a First Last Best Worst grid with these business-relevant prompts: first customer, worst failure, best decision, last rejection, first hire, worst meeting, best feedback, worst assumption. After I fill in my answers, analyse the grid for recurring entries, potential stories with transformation arcs, and useful anecdotes. Flag any entry that could serve as an opening for an investor pitch. + +**Prompt 4 -- Story Reservoir Audit:** +> I have been collecting moments for [duration]. Here are my ten most recent Homework for Life entries: [paste entries]. Analyse them for: (a) which entries contain a genuine five-second moment of transformation, (b) which are anecdotes that could support a larger story, (c) what patterns emerge across entries, and (d) which entry has the highest potential for a [pitch / keynote / team narrative]. For the top candidate, suggest the transformation arc (beginning state to ending state). + +--- + +## Use Cases + +**Idea-stage founder preparing for an accelerator interview** + +A first-time founder has a technically sound product concept but struggles to articulate why she personally cares about the problem. She has been doing Homework for Life for three weeks. Reviewing her entries, she notices a cluster of moments related to her mother's struggle with a broken healthcare system -- a pattern she had not consciously recognised. One entry, just eight words long, captures the afternoon her mother gave up trying to schedule a specialist appointment. That entry becomes the opening of her accelerator pitch. The judges remember her application not for the TAM slide but for the eight-word moment that made the problem human. + +**Validation-stage team running a First Last Best Worst session before a customer-discovery sprint** + +A three-person team preparing for fifty customer interviews runs First Last Best Worst with prompts tailored to their market: first time you encountered [problem], worst workaround you have seen, best customer reaction, last assumption that proved wrong. Each team member fills the grid independently, then they compare. Overlapping entries reveal shared assumptions; divergent entries reveal blind spots. Two entries from the worst-workaround column become opening anecdotes for customer conversations, replacing the clinical problem statements they had been using. Interview engagement improves measurably. + +**Scale-stage executive building a personal speaking practice** + +A COO who speaks at three to four industry events per year has been recycling the same company origin story for two years. Audiences have heard it. She begins Homework for Life and, within two months, accumulates forty-seven entries. Nine contain transformation moments. She now has enough material for three years of distinct keynote openings, each rooted in a genuine personal moment rather than the corporate narrative. Her speaking invitations increase because event organisers value speakers who bring new material. + +--- + +## Anti-Patterns + +**1. Writing too much.** The spreadsheet format exists to enforce brevity. A sentence or two per entry. Writing full paragraphs converts a five-minute habit into a thirty-minute obligation, and obligations die quickly. The goal is capturing a trigger for memory, not composing a draft. + +**2. Waiting for the dramatic moment.** The most common failure mode is recording only "big" events and ignoring the small ones. The most popular story in the framework involves a wife revealing she knew a childhood secret -- a moment at a dining-room table. Stories about near-death experiences, while exciting, connect less deeply. Founders who only record their biggest wins and losses miss the quiet moments that audiences find most compelling. + +**3. Skipping days and abandoning the practice.** Miss one day and you will miss two. Miss two and the week is gone. The discipline is non-negotiable. Only a "tragically small percentage" of the thousands taught this method actually sustain the practice. The ones who do report life-changing results. The ones who do not have no stories to show for it. + +**4. Using Crash and Burn as outlining.** Crash and Burn is not a planning exercise. Attempting to steer the freewriting toward a predetermined topic defeats the associative mechanism that produces unexpected connections. The entrepreneur who sits down to "freewrite about my pitch" will produce pitch notes, not stories. Start with an unrelated object in the room and let the mind wander. + +**5. Treating First Last Best Worst as trivia.** The exercise is not about identifying facts (my first car was a Honda). It is about locating moments of emotional significance attached to those facts. The answer "Honda Civic" is useless. The answer "Honda Civic -- the morning I drove away from my parents' house for the last time and realised I was terrified" is a story seed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal moments that reveal why you care about this problem | The founder's story inventory IS the company's narrative capital | +| Validation | Customer-interaction moments that shift your understanding | Homework for Life entries increasingly feature other people's words and reactions | +| Early Traction | Team moments, pivot moments, failure moments | Story material expands beyond the founder; the practice should spread to co-founders | +| Growth | Encouraging managers to maintain their own story practices | Narrative capacity must scale with the organisation; one storyteller is not enough | +| Scale | Institutional story collection across functions | Systematised story-gathering (customer stories, team stories, field stories) mirrors Homework for Life at organisational level | + +At the idea stage, a founder with sixty days of Homework for Life entries possesses something no slide deck can replicate: a reservoir of genuine, personal, transformation-bearing moments. Investors who have heard ten pitches that day will remember the one that opened with a real moment, not a market statistic. + +At scale, the challenge is distributing story-finding capability. A single executive with a rich story practice cannot supply narrative material for an organisation of hundreds. The techniques taught here -- particularly Homework for Life and First Last Best Worst -- transfer well to team workshops, offsites, and onboarding programmes. They are inexpensive, require no special tools, and produce results within weeks. + +--- + +## Output Template + +```markdown +# Story Discovery Plan -- [Name / Team] + +**Purpose:** [Pitch preparation / Keynote / Team alignment / Ongoing practice] +**Date started:** [Date] + +## 1. Homework for Life Setup +**Tool:** [Spreadsheet / Notes app / Physical journal] +**Daily trigger:** [End of day / Commute home / Before bed] +**Format:** Date | One to two sentence moment + +### This Week's Entries +| Date | Moment | +|------|--------| +| [Date] | [Entry] | +| [Date] | [Entry] | +| [Date] | [Entry] | + +## 2. Crash and Burn Log +**Last session date:** [Date] +**Starting word:** [Word] +**Threads worth saving:** +- [Thread 1 -- potential story / anecdote / connection] +- [Thread 2] +- [Thread 3] + +## 3. First Last Best Worst Grid +| Prompt | First | Last | Best | Worst | +|--------|-------|------|------|-------| +| [Prompt 1] | | | | | +| [Prompt 2] | | | | | +| [Prompt 3] | | | | | + +**Recurring entries:** [List any that appear more than once] +**Potential stories (with transformation):** [List with brief arc description] +**Useful anecdotes:** [List] + +## 4. Top Story Candidates for [Upcoming Event / Pitch / Presentation] +1. **[Entry reference]** -- Transformation: from [starting state] to [ending state] +2. **[Entry reference]** -- Transformation: from [starting state] to [ending state] +3. **[Entry reference]** -- Anecdote supporting [theme] +``` + +--- + +## Related Skills + +- **[What Is a Story](../../content/skills/storytelling/what-is-a-story.md)** -- Defines the transformation requirement that determines which discovered moments qualify as stories versus anecdotes. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- Once a story-worthy moment is found, this skill teaches how to build the five-second moment into a complete narrative. +- **[Story Beginnings and Endings](../../content/skills/storytelling/story-beginnings-and-endings.md)** -- The raw material from Homework for Life must be shaped; this skill covers where to start and how to land. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- The leadership application of story; the discovery techniques taught here feed directly into change narratives and vision stories. +- **[Storytelling Truth and Vividness](../../content/skills/storytelling/storytelling-truth-and-vividness.md)** -- The discovered moments must be told with sensory detail and honesty; the Cinema of the Mind and Five Permissible Lies provide the craft techniques. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The daily reflective practice of examining consequential interactions produces the raw material that Homework for Life systematises into a story library. diff --git a/plugins/foreman/skills/first-mover-strategy/SKILL.md b/plugins/foreman/skills/first-mover-strategy/SKILL.md deleted file mode 120000 index 577275f..0000000 --- a/plugins/foreman/skills/first-mover-strategy/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/first-mover-strategy.md \ No newline at end of file diff --git a/plugins/foreman/skills/first-mover-strategy/SKILL.md b/plugins/foreman/skills/first-mover-strategy/SKILL.md new file mode 100644 index 0000000..dcddcf4 --- /dev/null +++ b/plugins/foreman/skills/first-mover-strategy/SKILL.md @@ -0,0 +1,280 @@ +--- +name: "first-mover-strategy" +description: "Analyzes first-mover advantage, second-mover advantage, credible commitments, and credible threats in sequential strategic games. Covers the Stackelberg leader-follower model, the Chicken Game for competitive standoffs, the market entry game for incumbent-entrant dynamics, and burning bridges as a commitment device. Use when deciding market entry timing, evaluating competitive positioning sequences, structuring partnership commitments, negotiating investor term sheets, or assessing whether to lead or follow in any strategic interaction." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - first-mover-advantage + - second-mover-advantage + - credible-commitment + - credible-threat + - market-entry + - competitive-timing + - stackelberg + - strategic-positioning +related_skills: + - game-theory-fundamentals + - prisoners-dilemma-and-cooperation + - information-asymmetry + - porters-five-forces + - blue-ocean-strategy + - disruptive-innovation + - scenario-planning + - art-of-war +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# First-Mover Strategy + +CHESS OPENING. In chess, white moves first and holds a statistical advantage -- roughly 55% of games between equally matched players. But in many openings, black deliberately allows white to overextend, then counterattacks with superior information about white's committed position. The analogy to entrepreneurship is exact, and the answer to "should I move first?" is always the same: it depends on the game's structure. The Stackelberg model demonstrates that in quantity competition, the first mover captures a disproportionate share. The price-setting game demonstrates the reverse: the second mover can observe the first mover's price and undercut by a penny, winning the market. Between these two extremes lies every real market entry decision, every competitive response, and every negotiation. The question is never whether first-mover advantage exists in the abstract. The question is whether the specific game you are playing rewards initiative or patience -- and whether you can tell the difference before you commit. + +--- + +## The Framework + +### First-Mover Advantage: The Stackelberg Model + +Heinrich von Stackelberg formalized the first-mover advantage in 1934. His model contrasts two scenarios for firms producing competing products: simultaneous decisions (the Cournot model) and sequential decisions (the Stackelberg model). + +**Simultaneous Decision (Cournot): No First Mover** + +Both firms decide output at the same time, without observing each other. Each produces the same quantity and earns the same profit. Neither has an advantage. + +**Sequential Decision (Stackelberg): First Mover Wins** + +Firm 1 commits to a production level first. Firm 2 observes this commitment and optimizes its own output in response. The critical asymmetry: Firm 1 knows that Firm 2 will react optimally to whatever Firm 1 does. This knowledge allows Firm 1 to commit to a larger output than the Cournot level -- forcing Firm 2 into a smaller, less profitable response. + +The result in practical terms: + +| Metric | Cournot (Simultaneous) | Stackelberg Leader | Stackelberg Follower | +|--------|----------------------|-------------------|---------------------| +| Market share | Equal | Larger | Smaller | +| Profit | Equal | Higher than Cournot | Lower than Cournot | +| Strategic flexibility | Equal | Committed (locked in) | Reactive (constrained) | + +The first mover earns more than under simultaneous competition, while the follower earns less. The leader benefits from commitment; the follower suffers from being forced to react. + +**When First-Mover Advantage Applies in Business:** + +- **Platform markets with network effects.** The first platform to achieve critical mass creates switching costs and network value that followers cannot replicate without disproportionate investment. Facebook entering social networking before Google, Uber establishing ride-sharing before Lyft in key markets, and Slack defining workplace messaging before Teams all illustrate Stackelberg dynamics in platform competition. +- **Standard-setting and ecosystem creation.** The first mover defines the standard that others must follow or compete against. USB, Bluetooth, and TCP/IP were all first-mover standards where the pioneer's specifications became the industry default. +- **Markets where commitment is visible and irreversible.** Production capacity investments, exclusive distribution contracts, and long-term customer agreements all create the kind of visible, irreversible commitment that makes Stackelberg advantage work. The competitor sees the commitment, recognizes it cannot be reversed, and adjusts their strategy to accommodate it. + +### Second-Mover Advantage: When Patience Wins + +Not all sequential games reward the first mover. The second mover has a structural advantage in specific conditions. + +**The Price-Setting Game.** When two firms compete on price for a similar product, the second mover can observe the first mover's price and undercut it slightly. The first mover commits to a price; the second mover responds with a lower price and captures the market. The first mover's commitment becomes a liability, not an asset. + +**The Technology Adoption Game.** The first mover in a nascent technology bears the full cost of market education, infrastructure development, and early-adopter friction. The second mover observes which approaches work, which fail, and what customers actually want -- then enters with a refined product at lower cost. Microsoft famously followed this strategy across multiple categories: spreadsheets (after VisiCalc and Lotus 1-2-3), browsers (after Netscape), and search advertising (after Google, though less successfully). + +**When Second-Mover Advantage Applies:** + +| Condition | Why the Second Mover Wins | Example | +|-----------|--------------------------|---------| +| High market education costs | First mover pays to educate customers; second mover enters an educated market | Google entering search after AltaVista and Yahoo had trained users | +| Rapid technology evolution | First mover's technology becomes obsolete; second mover leaps ahead | Samsung in smartphones, entering after Apple proved the market | +| Observable pricing | Second mover undercuts by observing first mover's committed price | Retail "price matching" guarantees as institutional second-mover strategy | +| High uncertainty, low commitment cost | Second mover waits for uncertainty to resolve, then commits with better information | Late-stage investors who wait for product-market fit before investing | + +### The Coexistence Problem: Both Advantages Can Be Present + +Some markets exhibit both first-mover and second-mover advantages simultaneously, depending on which dimension of competition is analyzed. A company might have first-mover advantage in establishing a brand and second-mover advantage in technology refinement. The strategic question is not "which advantage exists" but "which advantage is larger on the dimension that matters most for long-term value capture." + +The resolution typically depends on whether the competitive advantage compounds over time. Network effects and switching costs compound: the first mover's advantage grows with each passing period. Technology and information advantages erode: the first mover's knowledge is eventually replicated or surpassed. When compounding advantages dominate, move first. When eroding advantages dominate, wait. + +### Credible Commitment: Making Promises Believable + +A commitment is credible when the committing party cannot reverse it -- or when reversal is so costly that it would be irrational. Game theory distinguishes sharply between statements of intent (cheap talk) and credible commitments (structurally binding). + +**The Credibility Test:** + +| Question | If Yes | If No | +|----------|--------|-------| +| Is the commitment publicly observable? | Increases credibility | Easy to renege quietly | +| Is reversal costly? | Credible -- rational actor would not reverse | Not credible -- can be abandoned when convenient | +| Has the committer invested irreversible resources? | Credible -- sunk costs create lock-in | Not credible -- nothing lost by walking away | +| Is the committer's reputation at stake? | Credible -- reputation damage exceeds benefit of reversal | Not credible -- no reputational consequence for breaking it | + +**Entrepreneurial Commitment Devices:** + +- **Public product roadmaps.** Publicly announcing features or launch dates creates reputational commitment. A company that routinely misses public deadlines destroys its credibility on all future announcements. +- **Exclusive partnerships.** Signing an exclusive distribution deal with one retailer credibly commits to that channel. The commitment is visible, costly to reverse, and signals strategic direction to the entire market. +- **Capacity investments.** Building a factory, signing a long-term lease, or hiring a large team creates commitment through sunk cost. The investment is irreversible and signals sustained presence in the market. +- **Open-sourcing core technology.** Open-sourcing a component credibly commits to a particular technical architecture. The commitment cannot be reversed (the code is public) and signals a specific strategic direction. + +### Credible Threat: Making Consequences Real + +A credible threat is a threatened action that the threatening party would rationally carry out if the threat conditions are met. Incredible threats -- threats that the threatening party would not actually follow through on -- are strategically worthless because rational opponents ignore them. + +**The Chicken Game: Mutual Incredible Threats** + +Two competitors on a collision course -- both racing to launch the same product in the same market at the same time. Neither wants to crash (both launch, splitting a market that cannot support two entrants). Both would prefer the other to swerve (one launches, the other pivots). + +| | Competitor: Stay Course | Competitor: Swerve | +|--|------------------------|-------------------| +| **You: Stay Course** | Both crash (-50, -50) | You win the market (100, 0) | +| **You: Swerve** | They win the market (0, 100) | Both find alternative paths (30, 30) | + +Neither player has a credible threat because carrying out the threat (staying course when the opponent also stays) hurts both equally. The outcome depends on which player can make their commitment more credible -- or which blinks first. + +**The Market Entry Game: Incumbent vs. Entrant** + +An incumbent threatens to slash prices if a startup enters their market. The question is whether the threat is credible. + +| | Startup: Enter | Startup: Stay Out | +|--|---------------|-------------------| +| **Incumbent: Price War** | Incumbent: -20, Startup: -30 | Incumbent: 100, Startup: 0 | +| **Incumbent: Accommodate** | Incumbent: 40, Startup: 30 | Incumbent: 100, Startup: 0 | + +Backward induction: if the startup enters, the incumbent's best response is to accommodate (40 > -20). The price war threat is incredible -- carrying it out hurts the incumbent too. The startup should enter, knowing the rational incumbent will accommodate. + +The incumbent can make the threat credible only by changing the game structure: investing in excess capacity (making price war less costly), signing long-term customer contracts at low prices (pre-committing to low pricing regardless of entry), or building a reputation for aggressive retaliation across multiple markets (making the single-market cost rational as a reputation investment). + +### Burning Bridges: The Ultimate Commitment Device + +The most powerful commitment device is eliminating your own option to retreat. Hernan Cortes allegedly burned his ships upon reaching the New World, making return impossible and committing his forces irrevocably to the conquest. The game-theoretic logic: when your opponent knows you cannot retreat, they must accommodate your advance. + +**Burning Bridges in Business:** + +| Action | What It Eliminates | Strategic Effect | +|--------|-------------------|-----------------| +| Quitting your job to start the company | Option to return to employment | Signals total commitment to investors, cofounders, early customers | +| Publicly announcing entry into a market | Option to quietly withdraw | Competitors and customers take the commitment seriously | +| Signing a long-term office lease | Option to reduce overhead quickly | Forces the team to generate revenue to cover fixed costs | +| Taking on venture debt alongside equity | Option to simply return capital | Creates urgency and commitment to growth | +| Open-sourcing proprietary technology | Option to compete on technology secrecy | Forces competitive advantage through other dimensions (service, ecosystem, speed) | + +The logic is counterintuitive: reducing your own options makes you stronger. Flexibility is normally an asset, but in sequential games, visible inflexibility forces the other player to adapt to your committed position rather than calling your bluff. + +The critical caveat: burning bridges works only when the opponent observes the commitment and believes it is irreversible. A bridge burned in secret provides no strategic advantage. And a bridge burned in a game where retreat is the optimal response -- because the market is genuinely unwinnable -- is not strategic commitment but self-destruction. + +--- + +## Prompts + +**Prompt 1 -- Assess First-Mover vs. Second-Mover Advantage:** +> I am considering entering [describe market]. Help me determine whether first-mover or second-mover advantage dominates in this specific market. Analyze: Are there network effects or switching costs that compound over time (favoring first mover)? Is there high uncertainty or rapid technology change (favoring second mover)? Is the competitive advantage in brand/distribution (usually favoring first mover) or in technology/product refinement (often favoring second mover)? Based on the analysis, recommend optimal entry timing and the specific advantages I should seek to capture. + +**Prompt 2 -- Design a Credible Commitment:** +> I need to make a credible commitment to [describe: market, partner, customer, investor]. Currently my commitment is not believed because [describe why]. Help me design a commitment device that passes the credibility test: it must be publicly observable, costly to reverse, involve irreversible resource investment, and put my reputation at stake. Evaluate at least four commitment devices and recommend the one with the best ratio of credibility gained to flexibility lost. + +**Prompt 3 -- Evaluate a Competitive Threat:** +> A competitor is threatening to [describe threat: price cut, market entry, patent lawsuit, talent poaching]. Help me assess whether this threat is credible using backward induction. If the competitor carries out the threat, what are the payoffs for both sides? Would a rational actor follow through? If the threat is incredible, what is the optimal response? If it is credible, what are my options for neutralizing it -- either by making my own counter-threat credible or by changing the game structure? + +**Prompt 4 -- Map the Sequential Game:** +> I am in a sequential competitive interaction with [describe competitor/partner]. I can move first or wait for them to move. Help me map this as a dynamic game tree: what are the possible move sequences, what are the payoffs at each terminal node, and what does backward induction recommend? Should I move first, or should I wait? If I move first, what commitment should I make? If I wait, what information do I gain and how should I respond to each possible first move by the other player? + +--- + +## Use Cases + +**Idea-Stage Founder Deciding When to Launch** + +A founder has developed a working prototype for an AI-powered contract analysis tool. A well-funded competitor is building a similar product and is approximately three months behind. The founder analyzes the game as a Stackelberg interaction: if she launches first with an imperfect product, she establishes market presence, begins accumulating training data (a compounding advantage), and forces the competitor to differentiate rather than compete head-on. If she waits for a polished product, the competitor may launch first and capture the data advantage. The analysis reveals that in this specific market, first-mover advantage is driven by data accumulation (compounding) rather than technology (eroding). She launches the MVP immediately, accepting initial product limitations in exchange for the data flywheel advantage. She reinforces the commitment by signing three design partners to 18-month exclusive contracts -- a visible, costly signal that makes her market presence irreversible. + +**Growth-Stage Company Facing an Incumbent's Threat** + +A growth-stage fintech company has captured 8% of the small business lending market. The dominant incumbent (45% market share) announces through a press interview that it will "aggressively defend" its market position, implying price cuts and increased marketing spend. The CTO performs a backward induction analysis. If the startup continues growing, the incumbent's best response is accommodation (maintaining margins on the 92% of the market it still controls) rather than a price war (which would compress margins across its entire customer base to prevent 8% erosion). The threat is incredible: the cost of industry-wide price compression far exceeds the cost of conceding the startup's niche. The startup continues its growth strategy, ignoring the threat -- while privately investing in switching-cost infrastructure (deep integration with accounting platforms) that would make a future price war even less effective. + +**Scale-Stage Platform Committing to an Ecosystem Strategy** + +A B2B SaaS platform at scale must decide whether to build a proprietary analytics module (capturing more value directly) or open the analytics API to third-party developers (building ecosystem value). The CEO frames this as a burning-bridges decision. Opening the API is effectively irreversible: once third-party developers build on the API, closing it would destroy ecosystem trust permanently. This irreversibility is the point. By open-sourcing the analytics layer, the platform credibly commits to a horizontal strategy, which attracts developers who would otherwise fear platform lock-in or competition from the platform itself. The commitment device -- the burned bridge of building the module in-house -- transforms the platform from a potential competitor into a credible partner. Within 18 months, the third-party analytics ecosystem generates more value than the in-house module would have, validating the strategic logic of irreversible commitment. + +--- + +## Anti-Patterns + +1. **Pursuing first-mover advantage as a default strategy.** First-mover advantage is conditional, not universal. Entering first in a market characterized by high uncertainty, rapid technology change, or high customer education costs often means absorbing all the pioneering costs while a follower enters with better information and a refined product. The analysis must precede the decision, not justify a preference for speed. + +2. **Making commitments that are not observed.** A commitment no one sees provides no strategic value. Internal decisions, quiet investments, and private plans do not change the game because they do not change other players' calculations. Commitment devices must be visible to the players whose behavior they are intended to influence. + +3. **Confusing sunk costs with strategic commitment.** Money already spent on a failing strategy is a sunk cost, not a strategic commitment. Continuing to invest in a losing position because "we have already committed" is the sunk cost fallacy wearing game theory clothing. Strategic commitment is forward-looking: it changes the future game structure. Sunk costs change nothing. + +4. **Issuing incredible threats and expecting compliance.** Threatening a competitor with a price war that would destroy your own margins, threatening a partner with a lawsuit you cannot afford, or threatening an employee with termination you cannot operationally sustain -- all are incredible threats that sophisticated opponents will ignore. Before issuing any threat, apply backward induction: would you actually follow through? If not, the threat degrades your credibility rather than enhancing it. + +5. **Burning bridges when the terrain is uncertain.** Eliminating retreat options is powerful when the destination is known and the path is visible. Burning bridges into fog -- committing irrevocably to a market that is poorly understood, a technology that is unproven, or a partnership that is untested -- is recklessness, not strategy. Reserve irreversible commitments for situations where the game structure is well understood and the commitment clearly shifts the equilibrium in your favor. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Timing analysis | The most consequential first-mover/second-mover decision occurs before launch: whether to enter now or wait. Analyze whether the market rewards pioneers (network effects, data accumulation, standard-setting) or fast followers (technology refinement, educated customers, proven demand). This decision often determines the company's entire trajectory. | +| Validation | Credible signaling | At validation stage, the startup lacks the resources for large-scale commitment devices. Focus on targeted signals: design partnerships, letter-of-intent commitments from early customers, and publicly visible milestones. These are low-cost commitment devices that establish market presence without irreversible resource commitment. | +| Early Traction | Competitive response mapping | With initial traction established, competitors begin to react. Map the sequential game: if you expand to segment X, how will the incumbent respond? Use backward induction to anticipate competitor reactions and choose moves that force favorable responses. | +| Growth | Commitment escalation | Growth stage enables larger commitment devices: exclusive contracts, capacity investments, ecosystem development. Each commitment should be evaluated not just for its direct return but for its strategic effect -- how it changes the game for competitors. | +| Scale | Game design through irreversible infrastructure | At scale, the company makes commitments that reshape the industry: platform standards, open APIs, infrastructure investments, regulatory engagement. These are the ultimate commitment devices -- they alter the game structure for all players, not just the competitive dynamic with a single rival. | + +--- + +## Output Template + +```markdown +# First-Mover / Sequential Strategy Analysis + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Game Structure + +- **Game type:** [Stackelberg / Chicken / Market Entry / Other] +- **Sequence:** [Who moves first? Is the sequence fixed or negotiable?] +- **Key compounding advantages:** [Network effects, data, switching costs, etc.] +- **Key eroding advantages:** [Technology, information, first-mover costs] + +## First-Mover vs. Second-Mover Assessment + +| Factor | Favors First Mover | Favors Second Mover | Assessment for This Market | +|--------|-------------------|--------------------|-----------------------------| +| Network effects | Strong | Weak | [Assessment] | +| Technology maturity | Mature | Evolving rapidly | [Assessment] | +| Customer education costs | Low | High | [Assessment] | +| Switching costs once established | High | Low | [Assessment] | +| Uncertainty level | Low | High | [Assessment] | +| **Overall** | | | **[First / Second / Depends on dimension]** | + +## Commitment/Threat Analysis + +| Commitment or Threat | Observable? | Costly to Reverse? | Credible? | Strategic Effect | +|---------------------|-------------|-------------------|-----------|-----------------| +| [Action 1] | [Y/N] | [Y/N] | [Y/N] | [Effect] | +| [Action 2] | [Y/N] | [Y/N] | [Y/N] | [Effect] | + +## Dynamic Game Tree (Key Decision Sequence) + +1. **Our move:** [Action] + - **If competitor responds with X:** Our payoff [value], Their payoff [value] + - **If competitor responds with Y:** Our payoff [value], Their payoff [value] +2. **Backward induction predicts:** [Competitor's rational response] +3. **Optimal first move:** [Recommendation] + +## Strategic Recommendation + +1. [Timing decision: move now or wait] +2. [Commitment device to deploy] +3. [Contingency plan for unexpected competitor moves] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](../../content/skills/game-theory/game-theory-fundamentals.md)** -- Provides the concepts of Nash equilibrium, payoff matrices, and static versus dynamic games that this skill extends into sequential analysis and commitment theory. +- **[Prisoner's Dilemma and Cooperation](../../content/skills/game-theory/prisoners-dilemma-and-cooperation.md)** -- Sequential moves can transform a simultaneous dilemma into a dynamic game with different equilibria; first movers can establish cooperative or competitive dynamics. +- **[Information Asymmetry](../../content/skills/game-theory/information-asymmetry.md)** -- The first mover often reveals information through their action; the second mover benefits from reduced uncertainty, creating a tension between commitment and information advantage. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Creating an uncontested market space is the ultimate first-mover play: defining a new game where no competitor has yet established a position. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Disruptors often benefit from second-mover advantage at the low end of a market, then compound advantages to move upmarket. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- The daily habit of strategic analysis determines whether timing decisions are made deliberately or by default. diff --git a/plugins/foreman/skills/flow-state/SKILL.md b/plugins/foreman/skills/flow-state/SKILL.md deleted file mode 120000 index f89fdda..0000000 --- a/plugins/foreman/skills/flow-state/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/flow-state.md \ No newline at end of file diff --git a/plugins/foreman/skills/flow-state/SKILL.md b/plugins/foreman/skills/flow-state/SKILL.md new file mode 100644 index 0000000..6224ddd --- /dev/null +++ b/plugins/foreman/skills/flow-state/SKILL.md @@ -0,0 +1,230 @@ +--- +name: "flow-state" +description: "Optimizes individual and team productivity using Csikszentmihalyi's flow state framework, covering the conditions for flow (clear goals, immediate feedback, challenge-skill balance), the four-stage flow cycle, and organizational flow design. Use when auditing personal or team focus time, diagnosing productivity loss from meeting overload and context-switching, designing flow-protective work schedules, calibrating challenge-skill balance on projects, or building recovery protocols to prevent founder burnout." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth +tags: + - productivity + - creativity + - peak-performance + - focus + - engagement +related_skills: + - growth-mindset + - thinking-fast-and-slow + - psychological-safety + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Flow State + +Three hours vanish. The code compiles, the design coheres, the strategy document assembles itself in what feels like a single unbroken motion. The noise of Slack notifications, investor emails, and team requests has receded to a frequency below perception. When the trance breaks -- a knock on the door, a calendar alert -- there is a disorienting moment of re-entry, like surfacing from deep water. The work product from those three hours exceeds what the previous three days of fragmented effort had yielded. That experience, reported with striking consistency across programmers, designers, writers, athletes, surgeons, and musicians, is what Mihaly Csikszentmihalyi named "flow." His four decades of research at the University of Chicago established that flow is not a mystical state available only to the gifted but a describable, reproducible psychological condition with specific preconditions and measurable effects. For entrepreneurs, who operate in environments structurally hostile to deep concentration, understanding flow is understanding where their highest-value output actually comes from -- and why most of their working hours produce so little of it. + +--- + +## The Framework + +### The Conditions for Flow + +Csikszentmihalyi's research identified a consistent set of conditions that precede the flow state. No single condition is sufficient; flow emerges from their convergence. + +**1. Clear goals.** The person knows what they are trying to accomplish at each moment. Not the long-term goal ("build a successful company") but the immediate task goal ("design the database schema for the user authentication module"). Ambiguity is the enemy of flow. + +**2. Immediate feedback.** The person receives continuous information about whether their actions are moving toward or away from the goal. A programmer sees code compile or fail. A writer sees sentences that work or do not. A salesperson reads the prospect's engagement in real time. Without feedback, there is no basis for the dynamic adjustment that characterises flow. + +**3. Challenge-skill balance.** This is the critical condition. The task must be sufficiently challenging to demand full engagement but not so challenging as to produce anxiety. If challenge exceeds skill, the result is stress. If skill exceeds challenge, the result is boredom. Flow lives in the narrow channel between the two. + +``` + High │ ANXIETY │ + │ │ + Challenge│ ┌───────────│ + │ │ FLOW │ + │ │ CHANNEL │ + │──────────────┘ │ + │ │ + │ BOREDOM │ + Low └──────────────────────────┘ + Low Skill High +``` + +**4. Concentration on the task at hand.** Flow requires undivided attention. Csikszentmihalyi's research found that flow is virtually impossible during multitasking. The brain's attentional resources must be fully absorbed by a single activity. + +**5. Sense of control.** The person feels capable of influencing the outcome. Not guaranteed success, but genuine agency. Learned helplessness -- the belief that one's actions do not affect outcomes -- precludes flow. + +**6. Loss of self-consciousness.** During flow, the inner critic falls silent. The person is no longer evaluating themselves ("Am I doing this well?") but is fully merged with the activity. Self-consciousness returns afterward, often as a heightened sense of accomplishment. + +**7. Altered perception of time.** Hours feel like minutes (most commonly), or occasionally moments expand. The subjective experience of time disconnects from clock time. + +### The Neurochemistry of Flow + +Subsequent research has mapped flow to a specific neurochemical cascade. The brain releases a cocktail of performance-enhancing chemicals: + +- **Norepinephrine** -- tightens focus and increases pattern recognition +- **Dopamine** -- enhances creative thinking and rewards engagement +- **Endorphins** -- reduces pain and increases pleasure +- **Anandamide** -- promotes lateral thinking and novel connections +- **Serotonin** -- produces the afterglow of well-being that follows flow + +The practical implication: flow produces both the best work and the best subjective experience of working. It is the rare alignment of peak performance with peak satisfaction. + +### The Flow Cycle + +Flow is not a binary state but a cycle with four stages: + +**Stage 1 -- Struggle.** The initial loading phase. The brain takes in information, encounters the challenge, and experiences frustration or tension. This stage feels unpleasant and is where most people quit. It is, however, a necessary precursor. + +**Stage 2 -- Release.** The person steps back from the problem. A walk, a shower, a shift in activity. The conscious mind disengages, allowing the subconscious to process. Forced effort at this stage is counterproductive. + +**Stage 3 -- Flow.** The state itself. Full absorption, effortless effort, peak performance. Duration varies from minutes to hours. + +**Stage 4 -- Recovery.** Flow is neurochemically expensive. The brain needs rest to replenish the neurotransmitters depleted during the state. Attempting to force back into flow without recovery produces diminishing returns and eventual burnout. + +### Organisational Flow + +Csikszentmihalyi and subsequent researchers (notably Steven Kotler) have explored how organisations can create conditions for collective flow. The key organisational factors are: + +- Shared, clear goals at the team level +- Rapid feedback loops (short sprint cycles, real-time dashboards) +- Equal participation and communication +- Familiarity -- team members who know each other's capabilities +- Psychological safety -- the willingness to take creative risks +- Sense of control -- autonomy over how work is executed +- Environment -- both physical (minimal interruptions) and temporal (protected focus time) + +--- + +## Prompts + +**Prompt 1 -- Personal Flow Audit:** +> Analyse my typical work week for flow conditions. Here is how I spend my time: [describe daily schedule, types of tasks, meeting load, interruption frequency, environment]. Identify the activities most likely to produce flow, the structural barriers preventing flow (meeting fragmentation, context-switching, unclear goals), and specific calendar and environment changes that would increase my flow time. Be specific about timing, duration, and what to eliminate or protect. + +**Prompt 2 -- Challenge-Skill Calibration:** +> I am working on [describe project or task] and I am experiencing [anxiety / boredom / sporadic engagement]. Using Csikszentmihalyi's challenge-skill balance model, diagnose the mismatch and recommend adjustments. If anxious: what skills should I develop or what support should I seek to raise my skill level? If bored: how can I increase the challenge or complexity to re-enter the flow channel? If sporadic: what environmental or structural factors are disrupting the conditions for flow? + +**Prompt 3 -- Team Flow Architecture:** +> Design a work structure for my team of [size] that maximises collective flow time. Current pain points: [describe -- e.g., too many meetings, unclear priorities, constant Slack interruptions, no protected focus time]. Consider: meeting consolidation, communication protocols (sync vs. async), goal-setting cadence, feedback loop design, and physical/digital environment. Produce a specific weekly schedule template that protects flow blocks while maintaining necessary collaboration. + +**Prompt 4 -- Flow Recovery Protocol:** +> I have been pushing hard for [timeframe] without adequate recovery and am experiencing [symptoms: diminished creativity, irritability, inability to focus, reduced output quality]. Design a recovery protocol based on the flow cycle's recovery stage. Include: immediate actions (today), short-term recovery plan (this week), and structural changes to prevent future recovery debt. Be realistic about what an early-stage founder can actually implement. + +**Prompt 5 -- Founder Role Design for Flow:** +> My current role as founder/CEO involves [list responsibilities]. Identify which responsibilities are flow-compatible (deep, focused, skill-stretching) and which are flow-incompatible (fragmented, reactive, low-challenge). Recommend a role redesign that maximises my time on flow-compatible work while ensuring flow-incompatible work is either delegated, batched, or eliminated. Include the business case for why protecting founder flow time is an investment, not an indulgence. + +--- + +## Use Cases + +**Idea-stage solo founder building an MVP** + +A technical founder building a product alone finds that her most productive coding sessions occur between 10 PM and 2 AM -- after the day's distractions have ceased. Analysis through the flow lens reveals that her daytime hours are fragmented by investor outreach, administrative tasks, and social media management, none of which produce flow for her but all of which produce enough context-switching to prevent it. The intervention is structural: she time-blocks her mornings (9 AM to 1 PM) as zero-meeting, zero-notification deep work, moves investor and admin tasks to afternoon batches, and eliminates social media from her phone entirely during deep work blocks. Within two weeks, her daytime coding output exceeds what she previously achieved in late-night sessions, and she regains sustainable sleep patterns. The total code committed per week increases by approximately 40%. + +**Early-traction product team losing velocity** + +An eight-person product team that was highly productive at five people has stalled. Sprint velocity has dropped 30% despite adding three engineers. Diagnosis through the flow framework reveals multiple flow-killers: daily standups that break morning focus, a Slack culture of immediate response expectation, unclear sprint goals (too many "stretch items"), and an open-plan office with no quiet zones. The team implements flow-protective measures: standups move to end-of-day async updates, Slack response expectations shift from "immediate" to "within 4 hours" for non-urgent items, sprint goals are reduced to three unambiguous commitments, and "flow mornings" are established where interruptions are prohibited before noon. Velocity recovers within two sprints and surpasses the pre-expansion baseline within four. + +**Growth-stage founder experiencing burnout** + +A CEO at a 50-person company has not experienced flow in months. Every hour is consumed by meetings, Slack, email, and firefighting. The CEO reports feeling "busy but useless" -- a textbook description of a high-activity, zero-flow work pattern. Analysis reveals that the CEO's role has drifted entirely into coordination and communication, with no time allocated to the strategic thinking and creative problem-solving that originally made her effective. The intervention involves radical calendar restructuring: two full days per week are declared "maker days" with no meetings, an executive assistant takes over email triage, and the CEO identifies the specific activities (strategic planning, customer research, product vision) that represent her highest-value flow work. The first maker day produces a strategic insight that the previous month of meetings had failed to generate. + +--- + +## Anti-Patterns + +**1. Romanticising flow as the only valuable work mode.** Not all productive work occurs in flow. Administrative tasks, relationship maintenance, rapid communication, and routine decision-making are necessary, valuable, and intrinsically low-flow. The goal is not to achieve constant flow but to protect sufficient flow time for the work that requires it. + +**2. Mistaking hyperfocus for flow.** Spending six hours answering emails without looking up is not flow -- it is compulsive task-switching within a single application. Flow requires challenge-skill balance and clear goals. Hyperfocus on low-challenge, reactive tasks produces neither the performance benefits nor the satisfaction of genuine flow. + +**3. Forcing flow through stimulants or sleep deprivation.** Caffeine, nootropics, and sleep debt can produce states that feel like heightened focus but lack the neurochemical signature of genuine flow and carry significant recovery costs. The flow cycle includes a recovery stage for a reason. Skipping recovery to maximise output-per-hour produces a net negative over any meaningful time horizon. + +**4. Using flow as an excuse for unavailability.** A founder who is perpetually "in flow" and therefore unreachable is not optimising productivity -- they are neglecting leadership. Flow is a tool to be deployed strategically, not a lifestyle that exempts the founder from the relational and communicative work that building a company requires. + +**5. Ignoring that flow conditions differ by person.** Csikszentmihalyi's conditions are universal, but their specific manifestation is individual. Some people flow best in silence; others with background music. Some flow in the morning; others late at night. Imposing a single "flow schedule" on a diverse team ignores individual variation and reduces aggregate flow rather than increasing it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder flow for creative and technical work | The founder has maximum autonomy to design their schedule for flow; the constraint is self-discipline, not organisational structure | +| Validation | Balancing flow (building) with necessarily fragmented work (customer discovery) | The challenge is accepting that customer conversations, while essential, are not flow activities, and designing the day to accommodate both | +| Early Traction | Protecting team flow while building coordination mechanisms | The first management challenge: meetings and processes necessary for coordination inherently threaten the flow conditions that produce the team's best work | +| Growth | Organisational flow design | Flow protection must become architectural -- embedded in calendaring systems, communication norms, office layout, and management training | + +At the idea stage, the founder is typically working alone or with one or two collaborators. The flow challenge is purely personal: designing a schedule and environment that supports sustained focus. This is the stage with the highest potential flow ratio -- the fewest meetings, the least email, the most uninterrupted building time. Founders who squander this window on scattered activity lose the advantage of the stage. + +At validation, a fundamental tension emerges. Customer discovery requires the antithesis of flow: interruption, active listening, rapid context-switching between different customer conversations, and comfort with ambiguity. The discipline is compartmentalisation: dedicated flow blocks for building and dedicated fragmented blocks for discovery, with a hard boundary between them. + +At early traction and growth, the challenge becomes organisational. Every meeting added is a potential flow-killer for someone. Every communication norm established (immediate Slack response, open-door policy, always-on availability) erodes the conditions for deep work. Founders who understand the flow framework make architectural choices that protect their team's capacity for concentration -- recognising that this protection is itself a form of leadership. + +--- + +## Output Template + +```markdown +# Flow Optimisation Plan -- [Individual/Team Name] + +**Prepared for:** Founder / Team Lead +**Date:** [Date] +**Scope:** [Individual schedule / Team structure] + +## Current Flow Assessment + +| Metric | Current | Target | +|--------|---------|--------| +| Estimated weekly flow hours | [Hours] | [Hours] | +| Average uninterrupted block duration | [Minutes] | [Minutes] | +| Meetings per week | [Count] | [Count] | +| Context switches per day | [Estimate] | [Target] | + +## Flow-Compatible Activities +[Activities that match challenge-skill balance and warrant flow protection] +1. [Activity] -- Current weekly allocation: [hours] -- Optimal: [hours] +2. [Activity] -- Current weekly allocation: [hours] -- Optimal: [hours] + +## Flow Barriers Identified + +| Barrier | Severity | Fix | Implementation Date | +|---------|----------|-----|-------------------| +| [e.g., mid-morning meetings] | [High/Med/Low] | [Move to afternoon batch] | [Date] | +| [e.g., Slack always-on culture] | [High/Med/Low] | [Async-first protocol] | [Date] | + +## Weekly Schedule Template + +| Time Block | Monday | Tuesday | Wednesday | Thursday | Friday | +|-----------|--------|---------|-----------|----------|--------| +| 9-12 | [Flow/Meetings/Admin] | ... | ... | ... | ... | +| 12-1 | [Break] | ... | ... | ... | ... | +| 1-3 | [Flow/Meetings/Admin] | ... | ... | ... | ... | +| 3-5 | [Flow/Meetings/Admin] | ... | ... | ... | ... | + +## Recovery Protocol +- **Daily:** [Specific recovery practice -- e.g., 20-min walk after deep work] +- **Weekly:** [Specific recovery practice -- e.g., one day with no deep work] +- **Quarterly:** [Specific recovery practice -- e.g., extended time off] + +## Measurement +- Track flow hours weekly using [method] +- Review and adjust plan on [date] +``` + +--- + +## Related Skills + +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework provides the belief system that sustains flow practice: the conviction that skill develops through challenge, which keeps the challenge-skill balance productive rather than threatening. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- Flow-compatible work lives in Quadrant II (important but not urgent); the Eisenhower Matrix provides the prioritization discipline needed to protect flow time from reactive demands. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Organisational flow requires psychological safety; team members who fear judgment cannot enter the self-consciousness-free state that flow demands. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness (recognising one's own flow triggers and barriers) and self-regulation (protecting flow time against the pull of reactive work) are EQ competencies that enable flow practice. +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- Applies Csikszentmihalyi's flow conditions specifically to creative work, addressing the unique challenges of sustaining flow during artistic and design-intensive tasks. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Provides the leadership-level scheduling and boundary-setting practices that protect flow time for both the leader and their teams. diff --git a/plugins/foreman/skills/focus-and-priority-management/SKILL.md b/plugins/foreman/skills/focus-and-priority-management/SKILL.md deleted file mode 120000 index 95c862e..0000000 --- a/plugins/foreman/skills/focus-and-priority-management/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/focus-and-priority-management.md \ No newline at end of file diff --git a/plugins/foreman/skills/focus-and-priority-management/SKILL.md b/plugins/foreman/skills/focus-and-priority-management/SKILL.md new file mode 100644 index 0000000..353ce48 --- /dev/null +++ b/plugins/foreman/skills/focus-and-priority-management/SKILL.md @@ -0,0 +1,215 @@ +--- +name: "focus-and-priority-management" +description: "Delivers daily scheduling habits, meeting hygiene, attention management, and boundary-setting techniques for leaders whose calendars have become their strategy by default. Use when urgent tasks crowd out important ones, when meeting load exceeds productive work time, when a leader cannot recall their last hour of uninterrupted deep work, or when data presentations fail to land because preparation time was consumed by low-value obligations." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - focus + - priorities + - time-management + - meetings + - deep-work + - calendar + - attention + - saying-no + - data-presentation +related_skills: + - eisenhower-matrix + - flow-state + - covey-seven-habits + - leader-resilience-and-wellbeing + - learning-agility +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Focus and Priority Management + +Perform an autopsy on your calendar from last week. Categorise every entry into four buckets: meetings you led, meetings you attended, blocks of focused individual work, and everything else. Now calculate the percentages. If focused work occupies less than 20% of your week, you are not leading -- you are being led, by other people's agendas, by the tyranny of the next notification, and by the organisational fiction that presence in a room equals contribution to an outcome. + +Michael Porter and Nitin Nohria's research on how CEOs manage time reveals a sobering truth: calendars are not neutral organisational tools. They are symbols. The tasks and people a leader shows up for communicate what matters more clearly than any strategy memo. An executive who spends 80% of the week in meetings and 3% on strategic thinking has, in effect, declared that reaction is the company's strategy. + +The Eisenhower matrix -- urgent versus important -- provides the theoretical scaffolding for this problem (see `eisenhower-matrix.md` for the framework). This skill concerns itself with the mechanical, behavioural, and social dimensions of actually living by that distinction: how to schedule deep work, how to run meetings that earn the time they consume, how to say no without damaging relationships, and how to present data so the meetings you do attend produce decisions rather than more meetings. + +--- + +## The Practice + +### Scheduling Deep Work + +Alice Boyes's research distils the scheduling challenge to a single principle: decide in advance when you will do important work, and then protect that time as though it were an unmovable meeting. The specific method matters less than the commitment. + +Effective approaches include: + +- **Morning fortress.** Reserve the first 90 minutes of each day for strategic work. No email, no Slack, no meetings. The brain's prefrontal cortex is freshest in the morning for most people; squandering that window on inbox triage is a neurological misallocation. +- **One sacred day.** Block an entire day per week -- typically Wednesday or Thursday -- for deep work. Communicate the block to the team so they do not interpret absence as unavailability. +- **Bite-size progress.** When full blocks are impossible, break strategic projects into 20-minute tasks that can fit between meetings. Keep a running list of these micro-tasks so that a sudden 15-minute gap becomes an opportunity, not dead time. + +### Meeting Hygiene + +Meetings are the largest single consumer of leadership time. Most of them underperform because they lack one or more of the following: + +**Clear decision-making process.** Bob Frisch and Cary Greene's research shows that confusion about who decides and how produces tension. Before any meeting begins, state the ground rules: Will there be a vote? Does someone hold veto power? Is the meeting for input or for ratification? Ambiguity on these questions turns a 30-minute discussion into a 90-minute argument. + +**Question-based agendas.** Steven Rogelberg recommends replacing topic-based agenda items with questions the group must answer. "Budget problems" becomes "How will we reduce spending by $100K this year?" Questions focus attention on outcomes, clarify who should be in the room, and signal when the meeting is done -- when the questions are answered. + +**Hybrid discipline.** When presenting to both in-person and remote audiences, leaders reliably neglect the screen. Sarah Gershman and Rae Ringel advise alternating eye contact between the room and the camera, moving closer to the camera periodically, mixing in-person and remote participants in breakout groups, and keeping the presentation short. Virtual fatigue is real; every presentation feels longer through a screen. + +### The Art of Saying No + +Elizabeth Grace Saunders identifies the core difficulty: saying no feels like a social transgression. The solution is scripted phrases practised until they feel natural. + +- **Redirecting:** "This might be a great growth opportunity for someone. I am happy to connect you with Kei, who is looking to develop in that area." +- **Capacity boundary:** "Thanks, but I have to decline. My schedule is at capacity." +- **Temporal boundary:** "I cannot take this on this quarter, but ask me again in Q3." + +The key is specificity. Vague resistance ("I'm pretty busy") invites negotiation. A clear, named reason closes the loop gracefully. + +### Attention as Muscle + +Daniel Goleman frames attention as the foundation of emotional, organisational, and strategic intelligence -- and argues that it can be strengthened through deliberate practice. + +Three dimensions of attention matter for leaders: + +1. **Self-focus** -- Monitoring internal signals, maintaining self-control, and sustaining coherent self-awareness across time. +2. **Other-focus** -- Reading people's perspectives, sensing what they need, and building relationships that function under pressure. +3. **World-focus** -- Listening broadly, connecting disparate information, and imagining how today's decisions play out at longer time horizons. + +The constant onslaught of incoming data -- email, messages, notifications, headlines -- attacks all three. Goleman's prescription is not willpower but structure: controlled environments, technology boundaries, and scheduled reflection time. + +### Productivity Versus Busyness + +Adam Waytz's research on overwork cultures identifies a pernicious dynamic: organisations that reward visible effort over measurable output create employees who optimise for the appearance of work. Leaders dismantle this by rewarding output, promoting based on results, fostering deep work by eliminating low-value tasks, and modelling the behaviour themselves -- including visibly signing off when meaningful work is done. + +### Data That Lands + +When a meeting requires data to drive a decision, presentation quality determines whether the data is heard or ignored. + +Nancy Duarte recommends making numbers relatable through concrete analogies: a time span compared to a familiar flight, a size compared to a local landmark. Joel Schwartzberg adds precision: label chart elements exactly, avoid abbreviations, replace generic titles with takeaway titles ("Millennials Prefer Mobile" rather than "Millennial Preferences"), and highlight the aha zones with visual emphasis and verbal callouts. + +--- + +## Prompts + +**Prompt 1 -- Calendar Autopsy:** +> Here is a summary of how I spent my time last week: [describe or paste calendar entries]. Categorise each entry as (a) deep strategic work, (b) meeting I led, (c) meeting I attended, (d) reactive/administrative, (e) other. Calculate percentages. Identify the three lowest-value time blocks and recommend what to eliminate, delegate, or restructure. Propose a revised calendar template that increases deep work to at least 25% of the week. + +**Prompt 2 -- Meeting Redesign:** +> I run a recurring [frequency] team meeting that currently lasts [duration] and covers [topics]. Attendance is [number] people. Redesign it using question-based agendas, explicit decision-making rules, and a hybrid-friendly format. Include a template agenda, ground rules, and guidance on reducing the meeting by at least 25%. + +**Prompt 3 -- Strategic No:** +> I have been asked to [describe the request]. My current priorities are [list top 3 priorities]. Draft three versions of a polite, clear decline: one for a peer, one for a senior leader, and one for a direct report. Each should redirect the request constructively without ambiguity. + +**Prompt 4 -- Data Presentation Overhaul:** +> I have the following data to present: [describe data, audience, and context]. Restructure the presentation so that: (a) each slide has a takeaway title, (b) key numbers are contextualised with concrete analogies, (c) aha zones are highlighted visually, and (d) the total presentation is under [target duration]. Draft the slide-by-slide outline. + +--- + +## Use Cases + +**Early-traction founder drowning in meetings** + +A founder of a 20-person startup spends 35 of 45 working hours per week in meetings. A calendar autopsy reveals that 40% of those meetings are status updates that could be replaced by asynchronous Slack summaries, and another 20% are one-on-ones that lack structure and routinely run over. The intervention: status meetings become written updates; one-on-ones are capped at 25 minutes with a standing agenda; and two mornings per week are declared meeting-free. Within a month, the founder reports having time to think about strategy for the first time in six months. + +**Growth-stage VP who cannot say no** + +A vice president at a 200-person company has accepted every cross-functional committee invitation, every mentorship request, and every "quick coffee" for two years. Her direct reports are underperforming because she has no time to coach them. With practised scripts, she declines three recurring committee roles (redirecting to capable direct reports), consolidates mentorship into a monthly group session, and reclaims seven hours per week. Her team's quarterly metrics improve within one cycle. + +**Scale-stage leader whose data presentations fail** + +A director presents quarterly business reviews to the executive team, but decisions are consistently deferred. Analysis reveals the problem: slides are dense with data, titles are generic, and no visual hierarchy guides the eye to the key findings. A redesign using takeaway titles, contextual analogies, and highlighted aha zones transforms a 45-minute data dump into a 20-minute decision-ready briefing. + +--- + +## Anti-Patterns + +**1. Protecting deep-work time but filling it with low-value work.** Blocking two hours for "strategic thinking" and then spending it reorganising a spreadsheet is a scheduling victory and a priority defeat. Deep-work blocks require advance clarity on what will be accomplished. + +**2. Saying no to everything.** The overcorrection from chronic overcommitment is hermit-like isolation. Leaders who decline every request erode social capital and lose access to information. The goal is selective engagement, not withdrawal. + +**3. Optimising meetings without questioning their existence.** Making a meeting 20% shorter is useful; asking whether the meeting should exist at all is transformative. The best meeting hygiene is the meeting that never happens because its purpose is served by a written summary. + +**4. Treating busyness as a personal failing rather than a systemic one.** Individual time-management techniques cannot overcome an organisational culture that rewards visible effort over output. If the system incentivises busyness, fixing the individual is treating the symptom. + +**5. Buying back time without investing it.** Outsourcing chores, hiring an assistant, or automating routine tasks creates capacity. If that capacity is immediately consumed by more meetings and more email, the investment yields no return. Freed time must be deliberately allocated to high-value work. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder's personal time allocation | Every hour has outsized impact; discipline here compounds dramatically | +| Early Traction | Meeting culture, first scheduling norms | The habits set in a 15-person company become the culture of a 150-person company | +| Growth | Calendar delegation, manager enablement | Leaders must teach others to manage their own focus, not just manage their own | +| Scale | Organisational time architecture, meeting audits | Time management becomes a systems problem requiring policy-level intervention | + +At validation, the founder's calendar is the company's strategy. A founder who spends 80% of the week on sales has a sales-driven company. A founder who spends 80% on product has a product-driven company. Whether either is correct depends on context, but the allocation should be deliberate, not accidental. + +At scale, individual time-management skills are necessary but insufficient. The organisation needs institutional interventions: meeting-free days across the company, default 25-minute meeting slots, mandatory agenda requirements, and quarterly meeting audits that identify and eliminate recurring meetings whose purpose has expired. + +--- + +## Output Template + +```markdown +# Calendar Audit Report -- [Name / Team] + +**Period:** [Week of Date] +**Total working hours:** [N] + +## Time Allocation + +| Category | Hours | Percentage | Assessment | +|----------|-------|------------|------------| +| Deep strategic work | [N] | [%] | [Target: >25%] | +| Meetings led | [N] | [%] | [Note] | +| Meetings attended | [N] | [%] | [Note] | +| Reactive/administrative | [N] | [%] | [Target: <20%] | +| Other | [N] | [%] | [Note] | + +## Three Lowest-Value Time Blocks +1. [Description] -- [Recommendation: eliminate / delegate / restructure] +2. [Description] -- [Recommendation] +3. [Description] -- [Recommendation] + +## Proposed Weekly Template + +| Time | Mon | Tue | Wed | Thu | Fri | +|------|-----|-----|-----|-----|-----| +| 8-10 | [Block type] | | | | | +| 10-12 | | | | | | +| 12-1 | | | | | | +| 1-3 | | | | | | +| 3-5 | | | | | | + +## Meeting Hygiene Checklist +- [ ] Every recurring meeting has a question-based agenda +- [ ] Decision-making process stated at the start of each meeting +- [ ] Default meeting duration is 25 minutes, not 30 or 60 +- [ ] At least two meeting-free blocks per week protected +- [ ] Quarterly meeting audit scheduled + +## Commitments to Decline +- [Commitment] -- [Redirect plan] +- [Commitment] -- [Redirect plan] +``` + +--- + +## Related Skills + +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- The theoretical framework for urgent-versus-important prioritisation; this skill provides the daily execution layer. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Deep work is the scheduling precondition for flow; without protected time, flow states cannot occur. +- **[Covey's Seven Habits](../../content/skills/frameworks/covey-seven-habits.md)** -- "Put first things first" is the Covey habit most directly addressed by calendar audits and meeting hygiene. +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Poor time management is a primary driver of leader burnout; protecting focus protects health. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Reclaiming calendar time requires delegating tasks that do not need the leader's personal involvement; the delegation audit directly feeds the calendar autopsy. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The Stoic dichotomy of control provides the philosophical discipline for releasing low-value commitments that consume focus without advancing priorities. diff --git a/plugins/foreman/skills/foreman/SKILL.md b/plugins/foreman/skills/foreman/SKILL.md new file mode 100644 index 0000000..cafe0ab --- /dev/null +++ b/plugins/foreman/skills/foreman/SKILL.md @@ -0,0 +1,8 @@ +--- +name: foreman +description: "Use Foreman diagnostics, playbooks, research, board simulations, solo and language modes, or persistent implementation tracking for an entrepreneur." +--- + +# Foreman + +Read [runtime](../../content/RUNTIME.md), [advisory rules](../../content/policies/advisory.md), and [catalog](../../content/catalog.json). Resolve the requested command or content from that catalog, then read its source under ../../content/. Apply its instructions to the user context. Never invent state or a successful write. Use the local runtime for profile and task changes. diff --git a/plugins/foreman/skills/four-ps-marketing/SKILL.md b/plugins/foreman/skills/four-ps-marketing/SKILL.md deleted file mode 120000 index 7f17e36..0000000 --- a/plugins/foreman/skills/four-ps-marketing/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/four-ps-marketing.md \ No newline at end of file diff --git a/plugins/foreman/skills/four-ps-marketing/SKILL.md b/plugins/foreman/skills/four-ps-marketing/SKILL.md new file mode 100644 index 0000000..10ea602 --- /dev/null +++ b/plugins/foreman/skills/four-ps-marketing/SKILL.md @@ -0,0 +1,181 @@ +--- +name: "four-ps-marketing" +description: "Designs and audits marketing strategy using McCarthy and Kotler's + Four Ps framework: Product, Price, Place, and Promotion. Evaluates coherence + across all four marketing mix elements to identify misalignments that + undermine go-to-market effectiveness. Use when launching a new product, + diagnosing why conversion rates are low despite strong product-market fit, + redesigning pricing strategy, evaluating distribution channel options, + planning go-to-market campaigns, or expanding from direct-to-consumer into + retail." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - marketing + - product-market-fit + - pricing + - go-to-market + - positioning +related_skills: + - blue-ocean-strategy + - business-model-canvas +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Four Ps of Marketing + +Product, Price, Place, Promotion. Four words that built trillion-dollar brands and bankrupted companies that ignored even one of them. E. Jerome McCarthy distilled the entirety of marketing strategy into this deceptively simple taxonomy in 1960, and six decades later it remains the skeleton key to market entry. The framework endures not because it is sophisticated -- it is not -- but because it forces founders to confront four decisions they cannot delegate, delay, or decouple. Get all four right and the market opens. Get one wrong and you discover, expensively, that marketing is a system, not a checklist. + +--- + +## The Framework + +The Marketing Mix operates as four interdependent levers. Adjusting one necessarily affects the others. A premium product sold through discount channels erodes its own positioning. A low price paired with exclusive distribution creates cognitive dissonance. The discipline lies in coherence. + +| Lever | Core Question | What It Encompasses | Common Founder Blind Spot | +|-------|--------------|---------------------|--------------------------| +| **Product** | What exactly are you selling? | Features, quality, design, branding, packaging, warranties, lifecycle | Over-engineering features nobody asked for; building for yourself, not the customer | +| **Price** | What is it worth -- and to whom? | List price, discounts, payment terms, financing, perceived value, price elasticity | Defaulting to cost-plus pricing; fear of charging what the market will bear | +| **Place** | How does the customer get it? | Channels, distribution, logistics, market coverage, online vs. physical, partnerships | Assuming "if we build it, they will come"; neglecting channel economics | +| **Promotion** | How do they know it exists? | Advertising, PR, content marketing, sales force, social media, partnerships, events | Spending on awareness before achieving product-market fit | + +### The Interdependence Principle + +The four Ps are not a menu from which to select favorites. They constitute a system. McCarthy's original insight -- later amplified by Philip Kotler -- was that marketing failures almost always stem from misalignment between elements rather than weakness in any single one. + +Consider a SaaS startup pricing at enterprise levels ($50K+ annual contracts) but relying exclusively on inbound content marketing for promotion. The price signals enterprise buyers, but the channel attracts mid-market prospects. Neither audience converts. The Ps are at war with each other. + +### Beyond the Original Four + +Subsequent scholars expanded the framework to 7 Ps (adding People, Process, Physical Evidence) for services businesses. Lauterborn proposed the 4 Cs (Customer, Cost, Convenience, Communication) as a buyer-centric reframe. These extensions have merit. But the original four remain the minimum viable marketing strategy -- the floor below which no company should fall. + +--- + +## Prompts + +**Prompt 1 -- Marketing Mix Audit:** +> Analyze my startup's current marketing mix. My product is [describe product/service], priced at [price point/model], distributed through [channels], and promoted via [current marketing activities]. My target customer is [describe]. Evaluate the coherence of these four elements. Where are they aligned, where do they conflict, and what specific changes would improve the overall mix? + +**Prompt 2 -- Price Sensitivity Analysis:** +> My product is [describe] in the [industry] space. Current price is [amount] with a [pricing model]. My competitors charge [range]. Help me evaluate whether my pricing is optimized by analyzing: perceived value vs. actual value, price elasticity for my segment, willingness-to-pay signals from [any data you have], and how my price interacts with my distribution channel and brand positioning. + +**Prompt 3 -- Channel Strategy Design:** +> I'm launching [product/service] targeting [customer segment]. I need to design my Place strategy. Evaluate these potential distribution channels for my business: [list channels you're considering]. For each, analyze: customer acquisition cost, scalability, alignment with my price point of [amount], and fit with my brand positioning. Recommend a primary and secondary channel with reasoning. + +**Prompt 4 -- Go-to-Market Mix Design:** +> I'm preparing to launch [product/service] in [market/segment]. Help me design a coherent marketing mix from scratch. Start with the target customer profile, then work through Product positioning, Price architecture, Place/distribution strategy, and Promotion plan -- ensuring all four elements reinforce each other. Budget constraint: [amount]. Timeline: [timeframe]. + +--- + +## Use Cases + +**Pre-Launch SaaS Pricing Misalignment** + +A validation-stage B2B SaaS founder has built an analytics platform targeting CFOs at mid-market companies (500-2,000 employees). The product is robust. Promotion runs through LinkedIn ads and cold email. But pricing sits at $99/month -- a figure that signals "small business tool" to the very CFOs the founder wants to reach. A Four Ps audit reveals the fundamental incoherence: the product and promotion target enterprise buyers, but the price screams SMB. Restructuring to $2,500/month with annual contracts, adding a sales-assisted demo process (adjusting Place from pure self-serve), and shifting promotion toward industry conferences and case studies restores alignment across all four levers. + +**D2C Consumer Brand Expanding to Retail** + +A growth-stage direct-to-consumer skincare brand generating $8M annually online faces a decision about entering physical retail. The Four Ps framework reveals the cascading implications: retail placement (Place) requires redesigned packaging and shelf-ready units (Product), wholesale margins compress pricing architecture (Price), and in-store marketing demands entirely different promotional strategies (Promotion). The framework prevents the common mistake of treating retail expansion as merely a distribution decision, exposing it as a full-system reconfiguration. + +**Marketplace Startup Balancing Two Sides** + +An early-traction marketplace connecting freelance designers with small businesses must run two parallel marketing mixes -- one for each side of the platform. The Four Ps analysis reveals that the supply side (designers) and demand side (businesses) require fundamentally different Product propositions, Price structures, Place strategies, and Promotion channels. Treating them as a single marketing problem, as the founders had been doing, explains the persistent supply-demand imbalance. + +--- + +## Anti-Patterns + +- **The Feature Obsession Trap.** Founders who spend 90% of their energy on the Product P and treat the other three as afterthoughts. A superior product with wrong pricing, invisible distribution, and no promotion strategy is a tree falling in an empty forest. The Ps demand equal strategic attention. + +- **Sequential Rather Than Simultaneous Thinking.** Treating the four Ps as a linear sequence -- "first we'll perfect the product, then figure out pricing, then distribution, then marketing" -- rather than designing them as an integrated system from the outset. By the time you reach the fourth P, the first three have already constrained your options. + +- **Copying Competitor Mixes Wholesale.** Adopting a competitor's pricing, channels, and promotion tactics without recognizing that their product positioning and brand equity differ from yours. The marketing mix is idiosyncratic to each company's strategic position. What works for the category leader actively harms the challenger. + +- **Ignoring Mix Evolution.** Setting the marketing mix at launch and never revisiting it. As the product matures, the customer base shifts, and competitive dynamics change, each P requires recalibration. The mix that worked at $500K ARR rarely survives intact to $5M. + +- **Promotion Without Product-Market Fit.** Pouring resources into the Promotion P before validating that the Product P actually solves a real problem. This is the most expensive mistake in startup marketing: amplifying a message about a product nobody wants. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Product-Price coherence | Testing willingness to pay; distribution is typically direct and simple; promotion is minimal and experimental | +| Early Traction | Channel discovery | Product is stabilizing; the critical question shifts to Place -- finding scalable, economic distribution channels | +| Growth | Full mix optimization | All four Ps are active and must be actively managed as an integrated system; promotion spend scales significantly | +| Scale | Mix diversification | Multiple product lines, price tiers, distribution channels, and promotion strategies running simultaneously; coherence becomes harder to maintain | + +--- + +## Output Template + +```markdown +# Marketing Mix Analysis: [Company/Product Name] + +**Date:** [Date] +**Stage:** [Current company stage] +**Target Customer:** [Primary customer segment] + +## Current Marketing Mix Assessment + +### Product +- **Core offering:** [What you sell] +- **Key differentiators:** [What makes it distinct] +- **Current gaps:** [What's missing or weak] + +### Price +- **Model:** [Subscription/one-time/freemium/etc.] +- **Price point:** [Amount] +- **vs. Competitors:** [Higher/lower/comparable] +- **Perceived value alignment:** [Strong/Weak/Misaligned] + +### Place +- **Primary channel:** [How customers buy] +- **Secondary channels:** [Additional distribution] +- **Channel economics:** [CAC, margins, scalability] + +### Promotion +- **Current activities:** [List channels and tactics] +- **Budget allocation:** [Where money goes] +- **Effectiveness:** [What's working, what isn't] + +## Coherence Assessment + +| P-to-P Alignment | Status | Issue | +|-------------------|--------|-------| +| Product-Price | [Aligned/Misaligned] | [Details] | +| Product-Place | [Aligned/Misaligned] | [Details] | +| Product-Promotion | [Aligned/Misaligned] | [Details] | +| Price-Place | [Aligned/Misaligned] | [Details] | +| Price-Promotion | [Aligned/Misaligned] | [Details] | +| Place-Promotion | [Aligned/Misaligned] | [Details] | + +## Recommended Adjustments +1. [Highest priority change] +2. [Second priority change] +3. [Third priority change] + +## Expected Impact +[What these changes should achieve and timeline for results] +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- The ERRC Grid fundamentally redefines the Product P by creating uncontested market space, requiring realignment of all four Ps around the new value curve. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- The broader business architecture within which the marketing mix operates; the Canvas's channels, customer relationships, and revenue streams map directly to Place, Promotion, and Price. +- **[Net Promoter Score](../../content/skills/frameworks/net-promoter-score.md)** -- Provides the customer feedback metric that reveals whether the marketing mix is delivering genuine value or merely generating transactions. +- **[Product Life Cycle](../../content/skills/frameworks/product-life-cycle.md)** -- The optimal marketing mix evolves as the product moves through introduction, growth, maturity, and decline, requiring systematic recalibration of all four Ps at each stage. +- **[Doblin's Ten Types of Innovation](../../content/skills/frameworks/doblin-ten-types.md)** -- Doblin's Experience types (Service, Channel, Brand, Customer Engagement) extend the Promotion and Place Ps into a richer innovation framework. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- Understanding how customers process information and make decisions is essential for designing Promotion messaging that resonates rather than merely reaches. diff --git a/plugins/foreman/skills/game-theory-fundamentals/SKILL.md b/plugins/foreman/skills/game-theory-fundamentals/SKILL.md deleted file mode 120000 index 8dd7741..0000000 --- a/plugins/foreman/skills/game-theory-fundamentals/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/game-theory-fundamentals.md \ No newline at end of file diff --git a/plugins/foreman/skills/game-theory-fundamentals/SKILL.md b/plugins/foreman/skills/game-theory-fundamentals/SKILL.md new file mode 100644 index 0000000..f241169 --- /dev/null +++ b/plugins/foreman/skills/game-theory-fundamentals/SKILL.md @@ -0,0 +1,235 @@ +--- +name: "game-theory-fundamentals" +description: "Introduces the foundational concepts of game theory for strategic business decisions: players, strategies, payoffs, game matrices, Nash equilibrium, and the distinction between static and dynamic games. Use when analyzing competitive dynamics, mapping market interactions, identifying stable outcomes in multi-player business situations, or structuring strategic choices under uncertainty." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - game-theory + - nash-equilibrium + - competitive-strategy + - strategic-thinking + - decision-making + - payoff-matrix +related_skills: + - prisoners-dilemma-and-cooperation + - information-asymmetry + - first-mover-strategy + - porters-five-forces + - scenario-planning + - art-of-war + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Game Theory Fundamentals + +BEAUTIFUL MIND. John Nash's Nobel Prize-winning insight fits in a single sentence: the best strategy for any player depends on what every other player is doing. This observation -- that optimal choices are interdependent, not independent -- is the foundation of game theory, and every entrepreneur already applies it without knowing the name. When a founder prices a product, negotiates a term sheet, or decides whether to enter a market, they are playing a game in the formal sense: multiple actors making strategic choices where each outcome depends on the choices of all. The difference between intuition and game theory is precision. Intuition says "consider the competition." Game theory says exactly how. + +--- + +## The Framework + +### The Three Essential Elements + +Every strategic interaction -- from a pricing war between two SaaS competitors to a cofounder equity negotiation -- reduces to three elements. Identifying them is the first step toward rigorous analysis. + +**Element 1: Players.** The decision-makers in the game. A minimum of two. In business, players are not always obvious. A startup entering a market has visible players (direct competitors) and hidden ones (regulators, platform owners, complementary product makers, the customer choosing between alternatives). Misidentifying who the players are is the most common source of strategic error. + +**Element 2: Strategies.** The set of available actions each player can take. A strategy is a complete plan of action -- not just "lower prices" but "lower prices by 15% in Q3 and match any further competitor reduction within 48 hours." The strategies available to each player define the boundaries of the game. Expanding or constraining available strategies changes the game fundamentally. + +**Element 3: Payoffs.** The outcome each player receives for each combination of strategies. Payoffs are not always financial. They can include market share, reputation, strategic positioning, time saved, or optionality preserved. The critical insight: a player's payoff depends not only on their own strategy but on the combination of all players' strategies. + +A game is fully defined by specifying these three elements. Everything else -- equilibria, optimal strategies, competitive dynamics -- follows from them. + +### The Payoff Matrix: Mapping Strategic Interactions + +The payoff matrix is the fundamental tool for visualizing a two-player game. Each row represents a strategy available to Player A; each column represents a strategy available to Player B. Each cell contains the payoffs for both players under that combination of strategies. + +**Example: Two Competing Coffee Shops** + +| | Shop B: Premium Pricing | Shop B: Discount Pricing | +|--|------------------------|------------------------| +| **Shop A: Premium Pricing** | A earns 80, B earns 80 | A earns 30, B earns 100 | +| **Shop A: Discount Pricing** | A earns 100, B earns 30 | A earns 50, B earns 50 | + +Reading this matrix reveals the strategic tension immediately. Both shops charging premium prices produces good results for both (80, 80). Both discounting produces mediocre results for both (50, 50). But each shop is individually tempted to discount while the other charges premium prices, capturing 100 while the competitor earns only 30. + +This single table encodes the entire competitive dynamic. No narrative strategy document communicates as much information as concisely. + +### Optimal, Worst, and Relative Optimal Strategies + +Three types of strategy merit identification in any game: + +**Optimal Strategy (Dominant Strategy).** A strategy that produces a higher payoff than all alternatives, regardless of what other players do. When a dominant strategy exists, the decision is straightforward -- play it. In the Prisoner's Dilemma, confessing is the dominant strategy for both suspects. In business, a dominant strategy is rare and valuable: it means the right move does not depend on competitor intelligence. + +**Worst Strategy (Dominated Strategy).** A strategy that always produces a lower payoff than some alternative, regardless of opponent behavior. Dominated strategies should be eliminated immediately from consideration. Their removal often simplifies the game considerably, sometimes revealing dominant strategies that were previously obscured. + +**Relative Optimal Strategy (Best Response).** The best strategy given a specific choice by the other player. Most real business situations lack dominant strategies. Instead, the best action depends on the competitor's action. "If they price high, we should price high. If they price low, we should price low." Mapping the relative optimal strategy for each possible competitor action is the foundation for finding Nash equilibrium. + +### Nash Equilibrium: The Stable Outcome + +Nash equilibrium is the combination of strategies where no player can improve their payoff by unilaterally changing their own strategy. Once reached, no one has an incentive to deviate. + +The method for finding it in a simple matrix: + +1. For each of Player B's strategies, identify Player A's best response (underline A's highest payoff in each column). +2. For each of Player A's strategies, identify Player B's best response (underline B's highest payoff in each row). +3. Any cell where both payoffs are underlined is a Nash equilibrium. + +**Applied to the Coffee Shop Example:** + +- If B prices premium, A's best response is discount (100 > 80). If B discounts, A's best response is discount (50 > 30). +- If A prices premium, B's best response is discount (100 > 80). If A discounts, B's best response is discount (50 > 30). +- Nash equilibrium: Both discount (50, 50). + +The equilibrium is stable but suboptimal -- both would prefer (80, 80). This tension between individual rationality and collective benefit is the central paradox of non-cooperative games, and it recurs across virtually every competitive business situation. + +### Multiple Equilibria: Risk Control vs. Pareto Optimum + +Many games produce multiple Nash equilibria. Two principles govern which one is likely to prevail: + +**Risk Control Principle.** Players choose the equilibrium that minimizes their worst-case exposure. Consider two tech companies deciding whether to adopt a shared standard: + +| | Firm B: Adopt Standard | Firm B: Go Alone | +|--|----------------------|-----------------| +| **Firm A: Adopt Standard** | A earns 100, B earns 100 | A earns 10, B earns 80 | +| **Firm A: Go Alone** | A earns 80, B earns 10 | A earns 60, B earns 60 | + +Both (Adopt, Adopt) and (Go Alone, Go Alone) are Nash equilibria. The risk-control principle predicts (Go Alone, Go Alone): if Firm A adopts the standard but B does not, A earns only 10. Playing it safe yields a guaranteed 60. Without trust or communication, risk aversion drives players to the inferior equilibrium. + +**Pareto Optimum Principle.** When players can communicate or have established trust, they gravitate toward the equilibrium that maximizes collective payoffs. Here, (Adopt, Adopt) is Pareto optimal -- both earn 100 instead of 60. + +The practical implication for entrepreneurs: the ability to communicate, build trust, and make credible commitments determines whether markets settle into productive equilibria or defensive, low-value ones. + +### Static vs. Dynamic Games + +**Static games** are played simultaneously -- all players choose their strategies without knowing what others have chosen. Most pricing decisions, sealed-bid auctions, and market entry timing decisions approximate static games. The payoff matrix is the primary analytical tool. + +**Dynamic games** are played sequentially -- one player moves first, the next player observes that move and responds, and so on. Product launches, negotiation sequences, and competitive responses are dynamic games. The primary analytical tool is the game tree, analyzed through backward induction: start at the final decision point, determine the rational choice, then work backwards to determine optimal play at each preceding stage. + +The distinction matters because first-mover advantage and second-mover advantage are properties of dynamic games. A simultaneous game has no "first mover." Identifying whether a business situation is closer to a static or dynamic game determines which analytical tools apply. + +--- + +## Prompts + +**Prompt 1 -- Map Your Competitive Game:** +> I operate in [describe your market/industry]. Help me map the game theory structure of my competitive situation. Identify the key players (direct competitors, substitutes, adjacent entrants, platform owners, regulators), the strategies available to each, and the approximate payoffs. Present this as a payoff matrix for the two most important competitive interactions I face. Then identify the Nash equilibrium and explain whether it represents a good or bad outcome for my business. + +**Prompt 2 -- Find the Equilibrium in a Specific Decision:** +> I am facing this strategic decision: [describe decision, e.g., pricing change, market entry, partnership negotiation]. The other key player is [describe]. My available strategies are [list]. Their likely strategies are [list]. Help me construct the payoff matrix, find the Nash equilibrium, and assess whether I should play the equilibrium strategy or attempt to shift the game structure. Consider whether this is a static or dynamic game. + +**Prompt 3 -- Identify Dominated Strategies:** +> Here are the strategic options I am considering: [list all options]. For each, help me determine if any are dominated -- meaning there is always a better alternative regardless of what competitors do. Eliminate the dominated strategies and show me the simplified decision. Then identify my best response to each likely competitor action. + +**Prompt 4 -- Assess Multiple Equilibria:** +> My competitive situation appears to have multiple stable outcomes: [describe the possible equilibria]. Help me assess which equilibrium is most likely to prevail by applying the risk-control principle and the Pareto optimum principle. What would it take to shift the market from the risk-control equilibrium to the Pareto-optimal one? What commitments, signals, or structures would be required? + +--- + +## Use Cases + +**Validation-Stage SaaS Founder Choosing a Pricing Model** + +A B2B SaaS founder must choose between per-seat pricing and usage-based pricing. Two direct competitors face the same decision. If all three adopt per-seat pricing, customers compare on features and margins remain healthy. If one switches to usage-based while others charge per-seat, the switcher captures price-sensitive customers but compresses margins industry-wide. If all switch to usage-based, margins compress for everyone. Mapping this as a three-player game reveals that per-seat pricing is a Nash equilibrium only if no player has an incentive to defect. Analysis shows that the smallest competitor (the startup) has the strongest incentive to defect -- it gains market share by undercutting on price structure. The founder uses this insight to time the pricing model switch strategically, capturing share before competitors respond. + +**Growth-Stage Marketplace Evaluating Geographic Expansion** + +A two-sided marketplace operating in three cities must decide which of two new metros to enter next. A well-funded competitor faces the same decision. If both enter the same city, they split the market and burn cash competing for supply. If they enter different cities, each captures a local monopoly position. The game matrix reveals two Nash equilibria -- one where the startup enters City A and the competitor enters City B, and vice versa. The startup uses signaling (public announcements, early partnerships, office lease signings) to commit credibly to City A, steering the competitor toward City B and achieving the Pareto-optimal split. + +**Early-Traction Founder Negotiating with a Strategic Partner** + +A hardware startup needs a distribution partnership with one of two major retailers. Each retailer values exclusivity (higher payoff from being the sole distributor) but will accept non-exclusive terms rather than lose the deal entirely. The founder maps the negotiation as a dynamic game: she moves first by approaching both retailers simultaneously. Backward induction shows that each retailer's best response to a simultaneous approach is to offer competitive terms, because the alternative -- refusing and watching the competitor win exclusive access -- is worse. The dynamic game structure gives the founder leverage that a sequential approach would not. + +--- + +## Anti-Patterns + +1. **Treating all interactions as games against a single competitor.** Most markets involve multiple players with heterogeneous strategies, asymmetric information, and different payoff structures. Reducing a five-player market to a two-player matrix can miss critical dynamics -- particularly the role of complementors, regulators, or platform owners who shape the payoff structure without competing directly. + +2. **Assuming players are perfectly rational.** Game theory's predictions assume rational actors. Real competitors make emotional decisions, suffer from cognitive biases, and sometimes act against their own interests. The model identifies what rational actors would do, which is useful as a baseline -- but deviations from rationality are the norm, not the exception. Use the framework to identify the rational benchmark, then layer behavioral analysis on top. + +3. **Ignoring the distinction between one-shot and repeated games.** A strategy that is optimal in a single interaction may be destructive in a repeated game. Aggressive pricing that wins one quarter's market share may trigger retaliation that destroys profitability for years. Always determine whether the game repeats before selecting a strategy. + +4. **Confusing Nash equilibrium with the best outcome.** Nash equilibrium is the stable outcome, not necessarily the desirable one. The Coffee Shop example demonstrates this clearly: the equilibrium (both discount) is worse for both players than the cooperative outcome (both premium). Recognizing a bad equilibrium is the first step toward restructuring the game to escape it. + +5. **Mapping the game after the decision is made.** Game theory is a planning tool, not a post-hoc rationalization device. Constructing the payoff matrix after committing to a strategy produces confirmation bias, not strategic insight. The matrix should be built before the decision, when it can actually influence the choice. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Player identification | The most valuable use at this stage is identifying who the players in a prospective market actually are. Most idea-stage founders undercount competitors and ignore non-obvious players (platform owners, regulators, substitute providers). Map the full player set before committing. | +| Validation | Strategy enumeration | With the market chosen, enumerate all available strategies -- not just the obvious ones. Pricing models, distribution channels, positioning angles, and partnership structures are all strategic variables. The wider the strategy set, the more likely a dominant or advantageous strategy emerges. | +| Early Traction | Equilibrium assessment | Revenue data provides real payoff information. Update the theoretical payoff matrix with actual market responses. Determine whether the current competitive equilibrium is sustainable and desirable, or whether strategic action is needed to shift it. | +| Growth | Dynamic game analysis | Growth-stage competition is sequential, not simultaneous. Competitors observe and respond to each other's moves. Shift from static payoff matrices to dynamic game trees. Backward induction -- reasoning from the end state to determine optimal current moves -- becomes the primary tool. | +| Scale | Game design | At scale, the company has sufficient market power to reshape the game itself -- changing the available strategies, altering payoff structures through platform economics, or adding new players through ecosystem development. The focus shifts from playing the game well to designing a game that structurally favors the company. | + +--- + +## Output Template + +```markdown +# Game Theory Analysis + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Player Map + +| Player | Type | Key Strategies | Primary Objective | +|--------|------|---------------|-------------------| +| [Our Company] | Protagonist | [Strategy 1, Strategy 2] | [Objective] | +| [Competitor A] | Direct rival | [Strategy 1, Strategy 2] | [Objective] | +| [Player C] | [Platform/Regulator/etc.] | [Strategy 1, Strategy 2] | [Objective] | + +## Payoff Matrix (Primary Competitive Interaction) + +| | Competitor Strategy 1 | Competitor Strategy 2 | +|--|----------------------|----------------------| +| **Our Strategy 1** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | +| **Our Strategy 2** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | + +## Equilibrium Analysis + +- **Nash Equilibrium:** [Strategy combination] +- **Is the equilibrium desirable?** [Yes/No -- explain] +- **Dominant strategies identified:** [Yes/No -- which player, which strategy] +- **Dominated strategies eliminated:** [List] + +## Strategic Recommendation + +Given the equilibrium analysis: +1. [Primary strategic action] +2. [Contingency if competitor deviates] +3. [Opportunity to restructure the game] + +## Game Type Assessment +- **Static or Dynamic:** [Assessment and why] +- **One-shot or Repeated:** [Assessment and implications] +- **Information:** [Complete or incomplete] +``` + +--- + +## Related Skills + +- **[Prisoner's Dilemma and Cooperation](../../content/skills/game-theory/prisoners-dilemma-and-cooperation.md)** -- The most famous application of these fundamentals, explaining why rational actors consistently produce collectively irrational outcomes and how to escape the trap. +- **[Information Asymmetry](../../content/skills/game-theory/information-asymmetry.md)** -- Extends the framework to games where players hold different information, fundamentally altering equilibrium outcomes. +- **[First-Mover Strategy](../../content/skills/game-theory/first-mover-strategy.md)** -- Applies dynamic game analysis to the question of timing: when moving first wins, when waiting wins, and how to make commitments credible. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- Applies Nash equilibrium concepts specifically to bilateral bargaining, providing the mathematical foundation for splitting deal surplus. +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Five Forces describes the structural dynamics of an industry; game theory explains the strategic logic that drives those dynamics and predicts how they evolve. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Combines with game theory to project how different competitive strategies might unfold under multiple future conditions. diff --git a/plugins/foreman/skills/generating-solutions/SKILL.md b/plugins/foreman/skills/generating-solutions/SKILL.md deleted file mode 120000 index d9468c1..0000000 --- a/plugins/foreman/skills/generating-solutions/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/decisions/generating-solutions.md \ No newline at end of file diff --git a/plugins/foreman/skills/generating-solutions/SKILL.md b/plugins/foreman/skills/generating-solutions/SKILL.md new file mode 100644 index 0000000..81edac8 --- /dev/null +++ b/plugins/foreman/skills/generating-solutions/SKILL.md @@ -0,0 +1,216 @@ +--- +name: "generating-solutions" +description: "Assembles four independent techniques for producing better alternatives before evaluation begins: structured brainstorming with its known failure modes, the question burst method for reframing problems through questions rather than answers, BrainSwarming as a silent graph-based alternative to verbal brainstorming, design thinking's four phases (question, care, connect, commit), and the could-versus-should reframe that expands the solution space by suspending premature judgment. Use when brainstorming sessions feel stale, when a team converges on the first idea too quickly, when introverts are being drowned out, when a problem needs reframing before solutions are attempted, or when only two options seem to exist." +version: "1.0.0" +category: "decisions" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - brainstorming + - idea-generation + - brainswarming + - design-thinking + - reframing + - question-burst + - creative-problem-solving + - could-vs-should + - alternatives +related_skills: + - decision-traps-and-roles + - evaluating-options + - defining-and-exploring-problems + - evaluating-and-deciding + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Generating Solutions + +BRAINSTORM PARADOX. Traditional brainstorming is the most popular idea-generation method in business -- and research consistently shows it produces fewer and worse ideas than the alternatives. No study has demonstrated that verbal group brainstorming outperforms individuals working alone and then pooling results. The reasons are structural, not motivational: production blocking (only one person talks at a time), evaluation apprehension (people self-censor in front of authority), and social loafing (coasting on others' contributions). The method persists because it feels collaborative. Feeling collaborative and being productive are different things. This skill presents four alternatives -- each addressing a different failure mode -- that a founder can select based on the specific obstacle the team faces. + +--- + +## The Toolkit + +### Tool 1: Structured Brainstorming (and Why It Usually Fails) + +Traditional brainstorming is not useless; it is misused. The technique works when three conditions hold: the facilitator is scrupulously neutral, ideas are recorded without commentary, and participants feel genuinely safe contributing ideas that contradict the most senior person in the room. In practice, all three conditions are violated within the first five minutes of most sessions. + +The failure modes: + +| Failure Mode | Mechanism | Symptom | +|-------------|-----------|---------| +| **Production blocking** | Only one person speaks at a time; others forget or abandon ideas while waiting | The most vocal participants generate most of the recorded ideas | +| **Evaluation apprehension** | Contributors self-censor to avoid judgment, especially from superiors | Ideas cluster around the safe and conventional; no one proposes anything that could look foolish | +| **Social loafing** | Individuals contribute less effort in a group than they would alone | Five people in a room produce fewer ideas than five people working independently | +| **Anchoring cascade** | The first idea voiced sets the frame; subsequent ideas orbit around it | A marketing manager suggests new packaging, and the entire session becomes a packaging discussion | + +Structural fixes that salvage the method: +- Have participants generate ideas independently in writing before any group discussion +- Use anonymous submission (digital or physical) to neutralise hierarchy +- Rotate facilitators so no single authority figure shapes the session +- Separate idea generation from idea evaluation by at least 24 hours + +### Tool 2: The Question Burst + +Developed by Hal Gregersen at MIT, the question burst inverts the standard brainstorming premise: instead of generating answers, the group generates questions. The shift works because questions bypass the cognitive biases that constrain answer-generation -- they suspend the automatic rush to solutions and reframe the problem from multiple angles simultaneously. + +**Protocol (15 minutes total):** + +1. **Set the stage (2 minutes).** The problem owner describes the challenge in plain language -- no detailed background, no proposed solutions. State what would improve if the problem were solved, and why it has resisted previous attempts. Include two or three people who have no direct experience with the problem; their ignorance is an asset because they will ask the questions insiders have learned not to ask. + +2. **Generate questions (4 minutes).** The group produces as many questions as possible, aiming for at least fifteen. Two rules: only questions are permitted (no answers, no preambles, no justifications), and the problem owner records every question verbatim. Time pressure forces brevity and prevents self-censorship. + +3. **Select and deepen (9 minutes).** The problem owner reviews the questions privately, selects three that reframe the challenge in unexpected ways, and applies Sakichi Toyoda's "five whys" to each -- asking why each question matters, then why that reason matters, drilling toward root assumptions. The output is not a solution but a redefined problem that opens new pathways. + +**Why it outperforms answer-brainstorming:** Gregersen's field data show that eighty percent of sessions produce at least one question that usefully reframes the problem. The method also reverses the power dynamics that sabotage traditional brainstorming -- a junior employee asking "Why do we assume our customers want this feature?" carries less social risk than the same employee proposing "We should kill this feature." + +### Tool 3: BrainSwarming + +Developed by Tony McCaffrey, BrainSwarming eliminates talking entirely. It replaces verbal brainstorming with a visual, silent, graph-based process inspired by how ants solve problems -- by leaving signals in the environment for others to build upon. + +**Structure:** + +A large surface (whiteboard, digital canvas) is prepared with the goal at the top and known resources at the bottom. + +- **Top-down thinkers** work downward from the goal, decomposing it into progressively more specific sub-goals +- **Bottom-up thinkers** work upward from the resources, identifying novel combinations and applications +- When the two directions connect on the graph, solutions emerge + +**No talking.** Participants add sticky notes and draw connections silently. This eliminates production blocking (everyone contributes simultaneously), evaluation apprehension (no one watches you speak), and social loafing (individual contributions are visible on the graph). + +Pilot data show BrainSwarming produces up to 115 ideas in fifteen minutes versus roughly 100 ideas per hour for traditional brainstorming -- a sevenfold increase in throughput. The graph structure also preserves the reasoning behind each idea, making it possible to trace how solutions were assembled from component insights. + +### Tool 4: Design Thinking's Four Phases + +Warren Berger's distillation of design-thinking practice identifies four behaviours that separate breakthrough innovators from incremental improvers. These are not sequential stages in a rigid process but concurrent habits of mind. + +**Question.** Designers begin by asking what Berger calls "stupid questions" -- those that challenge the premises everyone else accepts. "How many designers does it take to change a light bulb? Answer: Does it have to be a light bulb?" In a business context, the equivalent is: "What business are we really in?" and "What do today's customers actually need from us?" -- questions that feel naive but that expose assumptions invisible to insiders. + +**Care.** Genuine empathy requires leaving the corporate bubble and immersing in the daily lives of users. Focus groups and surveys are proxies for caring; observation is the real thing. The distinction matters because unarticulated needs -- the ones customers cannot express in a questionnaire -- are where the most valuable solutions live. + +**Connect.** Innovation often comes not from invention but from recombination -- what John Thackara calls "smart recombinations." Nike combined a running shoe with an iPod; Apple combined existing technologies into interfaces no one had assembled before. The discipline is lateral search: looking far outside the problem's domain for components that could be combined in new ways. + +**Commit.** Ideas become tangible through rapid prototyping -- napkin sketches, foam models, digital mock-ups. Giving form to an idea early means risking early failure, but designers understand that small failures are data. The iterative cycle of prototype, test, learn, and revise is faster and cheaper than the analytical cycle of plan, perfect, and launch. + +### Tool 5: Could vs. Should + +Research by Francesca Gino at Harvard Business School demonstrates that reframing "What should we do?" as "What could we do?" produces measurably more creative solutions. The "should" frame activates trade-off thinking -- the mind narrows to the most obvious answer. The "could" frame suspends judgment and expands the option set. + +In one experiment, participants facing ethical dilemmas with no good choice generated significantly more creative resolutions when asked what they "could" do rather than what they "should" do. A separate experiment found that groups given apparently conflicting goals (build a novel product and keep costs low) produced more original work than groups given a single goal -- the tension itself forced creative synthesis. + +The practical application: when a team presents a binary choice ("should we expand into Europe or focus on North America?"), reframe it as "what could we do?" and watch the option set multiply. The maître d' at a Michelin three-star restaurant in Modena, when a child ordered pizza at a restaurant that does not serve pizza, did not ask what he should do. He asked what he could do -- and sent a taxi to the best pizzeria in town. + +--- + +## Prompts + +**Prompt 1 -- Method Selection:** +> "My team needs to generate alternatives for [describe challenge] at my [stage] [sector] company. Diagnose which brainstorming failure modes are most likely given my team's composition: [describe team size, seniority mix, introvert/extrovert balance]. Recommend the best idea-generation method from this toolkit (structured brainstorming, question burst, BrainSwarming, design thinking, could-vs-should reframe) and explain why it addresses the specific failure mode." + +**Prompt 2 -- Question Burst Facilitation:** +> "I am stuck on this problem: [describe challenge in two sentences]. Act as a question burst facilitator. Generate twenty questions about this problem -- no answers, no preambles. Include at least five questions that challenge my fundamental assumptions, three that reframe the problem from the customer's perspective, and three that come from an outsider who knows nothing about my industry. Then identify the three questions most likely to open new solution pathways." + +**Prompt 3 -- BrainSwarming Graph:** +> "My goal is [describe goal]. My available resources are [list resources: team skills, budget, technology, partnerships, customer relationships]. Build a BrainSwarming graph: decompose the goal into sub-goals (top-down), then analyse the resources for novel combinations (bottom-up). Identify at least three points where top-down and bottom-up connect to form potential solutions." + +**Prompt 4 -- Could-vs-Should Reframe:** +> "My team has framed this decision as a binary: [Option A] vs. [Option B]. Apply the could-vs-should reframe. Generate at least five additional options we have not considered, including at least one that combines elements of A and B, one that redefines the problem entirely, and one inspired by how a completely different industry solves an analogous challenge." + +--- + +## Use Cases + +**Validation-Stage Healthtech Team Stuck on a Single Feature Concept** + +A five-person team building a remote patient monitoring platform holds weekly brainstorming sessions that consistently produce variations on the same theme: adding more clinical metrics to the dashboard. The CEO, a former clinician, speaks first in every session, and the team's ideas orbit her initial framing. Diagnosing the failure modes reveals anchoring cascade (the CEO's clinical lens sets the frame) and evaluation apprehension (junior engineers self-censor around a domain expert). Switching to BrainSwarming -- silent, parallel, graph-based -- eliminates both. The top-down decomposition of "improve patient outcomes" produces sub-goals the CEO had not considered (reduce caregiver burnout, increase medication adherence). The bottom-up analysis of resources surfaces a partnership with a pharmacy chain that the engineering team had discussed informally but never raised in a meeting. The two directions connect in a solution: automated medication reminders sent to both patient and caregiver, fulfilled through the pharmacy partnership. The idea never surfaced in six months of verbal brainstorming. + +**Early-Traction Marketplace Reframing Through a Question Burst** + +A freelance-talent marketplace is growing supply (freelancers) at three times the rate of demand (clients). The founding team frames this as a marketing problem: "How do we acquire more clients?" A question burst with two outsiders (a logistics founder and a former teacher) produces seventeen questions in four minutes, three of which reframe the challenge entirely: "What if the freelancers are the customers?" "What would happen if you charged freelancers instead of clients?" "Is the problem too few clients or too many of the wrong freelancers?" The third question triggers a five-whys analysis that reveals the real issue: the platform's open registration attracts freelancers whose skills do not match client demand. The supply-demand imbalance is not a marketing problem -- it is a curation problem. The solution (a selective application process for freelancers) reduces supply growth, increases match quality, and improves client acquisition as a second-order effect. + +**Growth-Stage Consumer Brand Escaping Binary Framing** + +A D2C skincare brand generating $8M in revenue frames its next move as "launch in retail or stay online." The could-vs-should reframe produces five additional options: wholesale to a single prestige retailer as a test (bullets before cannonballs), a pop-up collaboration with a complementary brand, a subscription tier that deepens online revenue without retail risk, licensing the formulations to an established retailer, and a hybrid -- an exclusive online-to-offline experience in one city. The hybrid option, invisible under binary framing, becomes the eventual choice and generates more press coverage than either original option would have alone. + +--- + +## Anti-Patterns + +**Running brainstorming sessions without diagnosing the failure mode first.** The choice of method should depend on the obstacle. If the problem is production blocking, BrainSwarming fixes it. If the problem is a badly framed question, a question burst fixes it. If the problem is binary thinking, the could-vs-should reframe fixes it. Using the wrong tool for the failure mode wastes the session and reinforces scepticism about structured ideation. + +**Allowing the most senior person to speak first.** Regardless of which method is chosen, the highest-ranking person in the room sets the anchor the moment they open their mouth. In structured brainstorming, have the most senior person contribute last or in writing. In a question burst, they participate as an equal questioner, not as a framer. + +**Generating ideas and evaluating them in the same session.** The entire point of ideation is divergent thinking -- expanding the option set. Evaluation is convergent thinking -- narrowing it. Combining both in a single meeting guarantees that evaluation kills the weaker-sounding ideas before they have time to develop. Separate generation from evaluation by at least a day. + +**Treating design thinking as a four-phase waterfall.** Question, care, connect, and commit are concurrent habits, not sequential stages. A team that completes an "empathy phase" and then never returns to observation is performing a ritual, not practising design thinking. + +**Stopping at idea generation.** The most creative option list in the world has zero value if no one commits to evaluating and acting on it. Every ideation session should end with a clear next step: who will evaluate which options, by when, and using what criteria. The question burst methodology explicitly requires a three-week action plan. Adopt the same discipline for every method. + +--- + +## By Stage + +| Stage | Best Method | Rationale | +|-------|-------------|-----------| +| Idea | Question burst + design thinking (Question, Care) | The founder's problem definition is the highest-leverage variable. Reframing the problem through questions and genuine user empathy produces better founding hypotheses than generating solutions to an unvalidated problem. | +| Validation | BrainSwarming + could-vs-should | The team needs divergent alternatives for MVP design, pricing, and positioning. BrainSwarming's speed and inclusiveness suit small teams with limited time. The could-vs-should reframe prevents premature commitment to the first viable option. | +| Early Traction | Structured brainstorming (with fixes) + question burst | The team is large enough for group dynamics to matter but small enough that structural fixes (silent writing, rotating facilitation) are feasible. Periodic question bursts prevent the anchoring cascade that develops as the company's success narrative solidifies. | +| Growth | All methods in rotation | Different challenges demand different tools. Product decisions may benefit from BrainSwarming; strategic decisions from question bursts; customer-experience decisions from design thinking. The discipline is matching method to failure mode, not defaulting to whichever method the team used last. | +| Scale | Question burst + design thinking (Care, Connect) | At scale, the primary failure mode is institutional -- the organisation's own success story frames every problem. Question bursts from outsiders and design-thinking immersion in customer reality counteract the gravitational pull of "how we've always done it." | + +The recurring danger across all stages: confusing the volume of ideas with the quality of alternatives. A session that produces fifty variations on the same theme has not generated fifty alternatives. It has generated one alternative and forty-nine echoes. The measure of a productive ideation session is the diversity of the option set, not its size. + +--- + +## Output Template + +```markdown +# Solution Generation Record + +**Challenge:** [one-sentence description] +**Date:** [date] +**Method used:** [structured brainstorming / question burst / BrainSwarming / design thinking / could-vs-should / combination] +**Rationale for method selection:** [which failure mode does this method address?] + +## Failure Mode Diagnosis +- **Primary failure mode:** [production blocking / evaluation apprehension / social loafing / anchoring cascade / binary framing / wrong problem] +- **Evidence:** [what observations suggest this failure mode?] + +## Ideas Generated +| # | Idea | Source (top-down / bottom-up / question / reframe) | Novel? (does it differ from the team's default thinking?) | +|---|------|-----------------------------------------------------|----------------------------------------------------------| +| 1 | [description] | [source] | [yes/no + why] | +| 2 | [description] | [source] | [yes/no + why] | +| 3 | [description] | [source] | [yes/no + why] | + +## Reframing Questions (if question burst was used) +1. [question that reframes the challenge] +2. [question that challenges a core assumption] +3. [question from an outsider perspective] + +## Next Steps +- **Who evaluates which options:** [names + assignments] +- **Evaluation deadline:** [date] +- **Evaluation method:** [reference evaluating-options skill] +``` + +--- + +## Related Skills + +- **[Decision Traps and Roles](../../content/skills/decisions/decision-traps-and-roles.md)** -- The traps that distort evaluation also distort ideation; this sibling skill provides the counter-routines to apply before generating solutions. +- **[Evaluating Options](../../content/skills/decisions/evaluating-options.md)** -- The natural sequel: once alternatives are generated, this skill covers joint evaluation, Even Swaps, risk ranking, and intuition calibration. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The problem-solution firewall and 3+ Principle complement the question burst and could-vs-should methods presented here. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process model explains why System 1 dominates brainstorming and why structured methods that engage System 2 produce better alternatives. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- When time pressure compresses the ideation window, rapid-decision habits complement the structured methods presented here. +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- The creative practice of courting unexpected connections and separating generation from judgment applies directly to the solution-generation phase of decision-making. diff --git a/plugins/foreman/skills/giving-feedback/SKILL.md b/plugins/foreman/skills/giving-feedback/SKILL.md deleted file mode 120000 index 0905c46..0000000 --- a/plugins/foreman/skills/giving-feedback/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/giving-feedback.md \ No newline at end of file diff --git a/plugins/foreman/skills/giving-feedback/SKILL.md b/plugins/foreman/skills/giving-feedback/SKILL.md new file mode 100644 index 0000000..3e9eddf --- /dev/null +++ b/plugins/foreman/skills/giving-feedback/SKILL.md @@ -0,0 +1,200 @@ +--- +name: "giving-feedback" +description: "Structures effective feedback conversations using the Situation-Behaviour-Impact (SBI) model from the Center for Creative Leadership. Separates observable behavior from interpretation, anchors feedback in specific situations, and articulates concrete impact. Use when preparing difficult performance conversations, constructing precise positive or corrective feedback, training first-time managers in feedback delivery, redesigning performance review systems, or building an organizational feedback culture." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - feedback + - communication + - management + - performance + - coaching +related_skills: + - radical-candor + - trust-equation + - thomas-kilmann-conflict + - grow-model +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Giving Feedback + +Here is an uncomfortable truth: most of the feedback you have given in your career has been useless. Not malicious, not even poorly intentioned -- simply useless. "Great job on that presentation" teaches nothing. "You need to be more strategic" is a Rorschach test, not guidance. "I'm disappointed in your performance this quarter" is an emotional discharge dressed as management. The receiver walks away knowing something happened but unable to extract a single actionable insight. Meanwhile, the giver checks "gave feedback" off their mental list and wonders why nothing changes. + +The problem is structural, not motivational. Most people want to give good feedback. They simply lack a method. The Situation-Behaviour-Impact (SBI) model, developed by the Center for Creative Leadership, provides exactly that: a rigorous structure that strips feedback of vagueness, projection, and judgment while preserving its essential content. SBI does not make difficult conversations easy. It makes them effective. + +--- + +## The Framework + +### The SBI Model: Three Components + +Effective feedback consists of three elements, delivered in sequence. Each element serves a specific function, and omitting any one of them degrades the feedback's utility. + +**S -- Situation** + +Anchor the feedback in a specific time, place, and context. This eliminates ambiguity and prevents the receiver from wondering "which time?" or "what do you mean?" + +- *Weak:* "In meetings, you tend to..." +- *Strong:* "In yesterday's product review meeting, when we were discussing the Q2 roadmap..." + +The situation establishes shared ground. Both parties can agree on when and where the event occurred. + +**B -- Behaviour** + +Describe the observable behaviour -- what the person *did*, not what you infer about their character, motivation, or intelligence. Behaviour is factual and disputable; interpretation is subjective and inflammatory. + +- *Weak:* "You were disrespectful to Sarah." +- *Strong:* "You interrupted Sarah three times while she was presenting her analysis, and on the third interruption you said, 'We've heard enough on this.'" + +The discipline of describing behaviour rather than attributing motive is the hardest part of SBI. It requires the feedback giver to separate observation from judgment -- a distinction that is conceptually simple and practically demanding. + +**I -- Impact** + +Articulate the effect the behaviour had -- on you, on others, on the project, or on the organisation. Impact connects behaviour to consequences, transforming feedback from a personal opinion into a business-relevant observation. + +- *Weak:* "That was unprofessional." +- *Strong:* "When you interrupted Sarah, she stopped contributing for the rest of the meeting. We lost her perspective on the technical feasibility assessment, and the team left without addressing a risk she had identified." + +### The Complete SBI Statement + +Assembling the three components: + +> "In yesterday's product review meeting [Situation], when you interrupted Sarah three times and said 'we've heard enough' [Behaviour], she stopped contributing for the rest of the meeting, and we missed her perspective on a technical risk that could affect the Q2 timeline [Impact]." + +No labels. No character judgments. No vague generalities. The receiver knows exactly what happened, what they did, and why it matters. + +### Extending SBI: The SBI-I Variant + +Some practitioners add a fourth element -- **Intent inquiry** -- transforming SBI into SBI-I: + +> "...I want to understand your perspective. What was going on for you in that moment?" + +This addition shifts the interaction from monologue to dialogue. It acknowledges that the feedback giver may have incomplete information. Perhaps the interruption was prompted by a time constraint the giver did not know about. The intent inquiry preserves the directness of SBI while opening space for the receiver's context. + +### SBI for Positive Feedback + +SBI is not exclusively a tool for criticism. Praise benefits equally from specificity: + +> "In Friday's client call [Situation], when the client challenged our pricing model and you walked them through the ROI calculation using their own data [Behaviour], the client's tone shifted entirely -- they moved from objecting to asking about implementation timelines [Impact]." + +Compare this with "Great job on the client call." The SBI version reinforces the *specific* behaviour that produced the result, making it far more likely to be repeated. + +### The Feedback Delivery Sequence + +1. **Prepare.** Write out the SBI components before the conversation. Rehearse if necessary. Precision under emotional pressure requires preparation. +2. **Set context.** "I have some feedback I'd like to share. Is this a good time?" Consent matters; ambush feedback triggers defence rather than reflection. +3. **Deliver the SBI statement.** Say it once, clearly, without hedging. +4. **Pause.** Silence is essential. The receiver needs time to process. +5. **Listen.** If using SBI-I, invite their perspective. Resist the urge to rebut. +6. **Agree on forward action.** "What would you like to do differently next time?" or "How can I support you in changing this?" +7. **Follow up.** Acknowledge improvement when you see it. Feedback without follow-up signals that the conversation was not important. + +--- + +## Prompts + +**Prompt 1 -- SBI Construction:** +> I need to give feedback to [person/role] about [describe the situation]. Help me construct a precise SBI statement by separating the situation (when and where), the behaviour (what they did, observably), and the impact (the effect on the team, project, or business). Ensure the behaviour description contains no interpretive language -- only observable actions and direct quotes where available. + +**Prompt 2 -- Feedback Pattern Analysis:** +> Here are five pieces of feedback I have recently given to my team: [list them]. Analyse each against the SBI model. Identify which ones lack a clear situation, which conflate behaviour with interpretation, and which omit impact. Then rewrite each as a proper SBI statement. + +**Prompt 3 -- Difficult Feedback Preparation:** +> I need to address a sensitive performance issue with [describe person and context]. The issue involves [describe]. I am nervous about this conversation because [describe your concern -- damaging the relationship, triggering a defensive response, etc.]. Help me prepare a complete SBI statement and a conversation plan, including: how to open, what to say, how to handle likely defensive responses, and how to close with a forward-looking action plan. + +**Prompt 4 -- Positive Feedback Architecture:** +> I want to build a habit of giving specific positive feedback to my team of [size]. For the past week, I have noticed these contributions: [list 3-5 things team members did well]. Help me craft SBI-format positive feedback for each one, ensuring the behaviour is specific enough to be repeatable and the impact is concrete enough to demonstrate why their contribution mattered. + +**Prompt 5 -- Feedback Culture Kickstart:** +> My company of [size] has no structured feedback practice. People either avoid feedback entirely or deliver it vaguely during annual reviews. Design a lightweight feedback programme built on the SBI model that includes: a 30-minute training session outline, a feedback template for managers, a weekly or bi-weekly feedback ritual, and a way to measure whether feedback quality improves over 90 days. + +--- + +## Use Cases + +**Validation-Stage Startup with Two Cofounders** +The CEO cofounder needs to address the CTO cofounder's habit of committing to deadlines in customer meetings that engineering cannot meet. Rather than the usual passive-aggressive tension ("we need to manage expectations better"), the CEO constructs an SBI statement: "In Tuesday's demo with Acme Corp [Situation], you told them we'd have the API integration ready in two weeks [Behaviour]. The engineering team estimates six weeks, which means we either disappoint the client or burn out the team to hit an unrealistic date -- and this is the third time this quarter it has happened [Impact]." The specificity transforms a recurring frustration into a solvable problem. + +**Growth-Stage Manager Giving First-Time Feedback to a Senior Hire** +A newly promoted engineering manager must address code quality issues with a senior engineer who has more experience than they do. The power dynamic makes vague feedback ("your code could be cleaner") dangerous -- the senior hire will dismiss it. SBI equalises the interaction: "In the PR you submitted yesterday for the payment processing module [Situation], there were no unit tests for the edge cases we identified in the design review, and the error handling returned generic 500 responses without logging [Behaviour]. Two of those edge cases caused production incidents in a similar module last month, and without specific error codes, debugging takes three times as long [Impact]." The feedback is inarguable because it is grounded in fact. + +**Scale-Stage Company Running Annual Performance Reviews** +A 400-person company replaces its ineffective annual review process (generic ratings on a 1-5 scale with subjective commentary) with an SBI-based system. Managers are required to provide three SBI-positive and two SBI-developmental examples per review. Calibration sessions across management levels ensure that "exceeds expectations" is supported by specific behavioural evidence, not general impressions. Review quality, measured by employee satisfaction surveys, increases 35% in the first cycle. + +--- + +## Anti-Patterns + +1. **The Feedback Sandwich.** Positive-negative-positive. The structure is so well-known that it has become a psychological signal meaning "brace yourself, the middle part is what they actually think." Recipients learn to ignore the bread and dread the filling. SBI does not require sandwiching; it requires clarity. + +2. **Behaviour-as-Interpretation.** "In the meeting, you were passive-aggressive" is interpretation, not behaviour. "In the meeting, you rolled your eyes when I presented the budget and said 'sure, whatever you think'" is behaviour. The distinction determines whether feedback produces insight or defensiveness. + +3. **Stockpiling.** Saving feedback for a quarterly review rather than delivering it within 48 hours of the event. Delayed feedback loses context, accumulates emotional charge, and overwhelms the receiver with a catalogue of grievances they can no longer recall clearly enough to address. + +4. **Impact Inflation.** Exaggerating the impact to make the feedback feel more important. "Your typo in the client email could have cost us the entire account" -- could it? Really? Impact inflation erodes trust. State the actual impact, neither minimised nor inflated. + +5. **Monologue Feedback.** Delivering the SBI statement and immediately moving on without pausing for the receiver's response. Feedback is a dialogue. The SBI statement opens the conversation; it does not constitute the conversation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Cofounder feedback | At the earliest stage, feedback flows between two or three people with no managerial hierarchy. SBI provides structure for peer feedback where "pull rank" is not an option. | +| Early Traction | First-time managers | New managers need a concrete method. SBI is the simplest and most immediately applicable feedback framework -- a tool they can use in their first week as a manager. | +| Growth | Feedback consistency across teams | Different managers give feedback differently. SBI provides a common language and structure that ensures minimum feedback quality across the growing management layer. | +| Scale | Institutional feedback systems | At scale, SBI becomes embedded in performance review templates, 360-degree review tools, and manager training programmes. The framework becomes organisational infrastructure rather than individual practice. | + +--- + +## Output Template + +```markdown +# Feedback Preparation: [Recipient Name/Role] + +## SBI Statement +- **Situation:** [When and where -- specific date, meeting, context] +- **Behaviour:** [What they did -- observable actions only, no interpretation] +- **Impact:** [Effect on team, project, business, or individuals] + +## Complete Statement (Draft) +"[Assembled SBI statement, ready to deliver]" + +## Conversation Plan +- **Opening:** [How you will set context and ask for permission] +- **Delivery:** [The SBI statement] +- **Pause and listen:** [Expected response and how you will handle it] +- **Intent inquiry (optional):** "What was your perspective on that moment?" +- **Forward action:** [What change you are requesting and what support you will offer] +- **Follow-up plan:** [When and how you will check in on progress] + +## Defensive Response Preparation +| Likely Response | Your Approach | +|-----------------|---------------| +| Denial ("That didn't happen") | [Return to observable facts] | +| Deflection ("Everyone does that") | [Refocus on specific impact] | +| Counter-attack ("Well, you...") | [Acknowledge, redirect to the topic] | +| Emotion (tears, anger) | [Pause, express care, offer to continue later] | +``` + +--- + +## Related Skills + +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Radical Candor provides the philosophical foundation for why direct feedback matters; SBI provides the mechanical structure for how to deliver it effectively. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- The denominator of the trust equation (self-orientation) directly affects whether feedback is received as helpful or self-serving. +- **[Thomas-Kilmann Conflict](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- Feedback conversations often trigger conflict; understanding conflict modes helps the giver navigate defensive responses and choose the right approach. +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- After SBI identifies the issue, GROW provides a coaching framework for developing the forward-looking action plan with the recipient. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's safety conditions determine whether feedback is received as developmental input or perceived as threat, making safety a prerequisite for effective SBI delivery. +- **[Writing Performance Reviews](../../content/skills/writing/writing-performance-reviews.md)** -- Translates the SBI discipline into written form for formal review processes, ensuring documented feedback is equally specific and actionable. diff --git a/plugins/foreman/skills/grammar-and-mechanics/SKILL.md b/plugins/foreman/skills/grammar-and-mechanics/SKILL.md deleted file mode 120000 index 6166d28..0000000 --- a/plugins/foreman/skills/grammar-and-mechanics/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/grammar-and-mechanics.md \ No newline at end of file diff --git a/plugins/foreman/skills/grammar-and-mechanics/SKILL.md b/plugins/foreman/skills/grammar-and-mechanics/SKILL.md new file mode 100644 index 0000000..97863e5 --- /dev/null +++ b/plugins/foreman/skills/grammar-and-mechanics/SKILL.md @@ -0,0 +1,192 @@ +--- +name: "grammar-and-mechanics" +description: "Provides a structured reference for the grammar and punctuation rules that most frequently undermine credibility in business writing. Covers subject-verb agreement, pronoun case, dangling modifiers, parallel construction, comma splices, and the most common usage confusions (affect/effect, that/which, who/whom). Use when proofreading pitch decks, investor updates, client proposals, or any external-facing document where a single error can erode perceived competence." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - grammar + - punctuation + - proofreading + - credibility + - usage + - writing-mechanics +related_skills: + - tone-and-engagement + - writing-effective-emails + - writing-memos-and-reports + - writing-performance-reviews +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Grammar and Mechanics + +A misplaced apostrophe has never killed a company. But it has killed pitch decks, alienated investors, and quietly disqualified founders from rooms they never knew they were being evaluated for. Grammar errors in business writing operate as a credibility tax: each one individually minor, collectively devastating. Readers may not consciously register the error, but they register its effect -- a subtle downgrade in how seriously they take the author. The founder who writes "it's revenue model" instead of "its revenue model" in a Series A memo has communicated something unintended: carelessness with details. And carelessness with details is precisely the trait investors screen for. + +The rules that follow are not pedantic niceties. They are the twelve grammatical principles and twelve punctuation conventions that, when violated, most reliably damage professional credibility. + +--- + +## The Framework + +### Twelve Essential Grammar Rules + +**1. Starting sentences with *And* or *But* is perfectly acceptable.** The myth persists from secondary school, but the best prose writers have always done it. Monosyllabic conjunctions create tighter transitions than *however* or *additionally*. + +**2. Ending a sentence with a preposition is fine.** The prohibition traces to Latin syntax and has no basis in English grammar. "What will the new product be used for?" reads more naturally than the contorted alternative. + +**3. Use *well* as an adverb, not *good*.** "The team performed well" -- not "performed good." The exception: set phrases like "a good many" or "did it but good." + +**4. The subject determines the verb's number.** Prepositional phrases that follow the subject create "false attraction" -- the verb should match the subject, not the nearest noun. + +- *Wrong:* "The details of the customized work *is* delaying the project." +- *Right:* "The details of the customized work *are* delaying the project." + +**5. *Either* and *neither* as subjects take singular verbs.** "Neither of our expansion options *provides* a total solution" -- not *provide*. + +**6. With *neither/nor* and *either/or*, the second element controls the verb.** "Neither the regional managers nor the vice-president *likes* the proposed theme." + +**7. Flat adverbs (*thus*, *doubtless*) take no *-ly* ending.** Adding *-ly* to words that are already adverbs produces nonstandard forms: *thusly* and *doubtlessly* are both incorrect. + +**8. Conjunctive adverbs (*however*, *therefore*) cannot join independent clauses with just a comma.** This produces the comma splice. Use a semicolon before and a comma after: "The campaign is ready; however, the CEO has yet to approve it." + +**9. *That* introduces restrictive clauses (no comma); *which* introduces non-restrictive clauses (with a comma).** "The report that you requested is ready" vs. "The report, which you requested, is ready." + +**10. Pronouns must agree with their antecedents in number.** "A shareholder may cast *his or her* vote" -- or restructure the sentence to use the plural: "Shareholders may cast *their* votes." + +**11. Avoid double negatives.** Subtle forms include *couldn't scarcely* (use *could scarcely*) and *not...but* constructions that create ambiguity. + +**12. Use standard English consistently.** Watch for nonstandard forms that creep in from speech: *shouldn't of* (should be *shouldn't have*), *drug* as past tense of *drag* (should be *dragged*). + +### Twelve Punctuation Essentials + +| # | Rule | Example | +|---|------|---------| +| 1 | Use the serial (Oxford) comma before the final item in a list | "Revenue, costs, and margins" | +| 2 | Place commas and periods inside quotation marks | She said "the deal is closed." | +| 3 | Use a semicolon to join related independent clauses | "Sales rose 14%; margins held steady." | +| 4 | Use a colon to introduce a list, explanation, or elaboration | "Three priorities: hiring, retention, and culture." | +| 5 | Hyphenate compound adjectives before a noun | "A well-written proposal" (but "the proposal was well written") | +| 6 | Use an em dash for emphasis or interruption | "The acquisition -- if approved -- will close in Q3." | +| 7 | Apostrophes show possession, not plurality | "The company's revenue" not "the company's revenue's" | +| 8 | *Its* (possessive) vs. *it's* (contraction of "it is") | "The firm increased its revenue" | +| 9 | Use parentheses for supplementary information | "Revenue ($4.2M) exceeded projections." | +| 10 | End declarative sentences with a single period | Never use double periods or exclamation marks in formal prose | +| 11 | Use a comma after introductory phrases | "After reviewing the data, the team recommended expansion." | +| 12 | Do not use a comma to separate a subject from its verb | *Wrong:* "The CEO, approved the budget." | + +### Common Usage Confusions + +| Confused Pair | Distinction | +|---------------|-------------| +| *affect* / *effect* | *Affect* is usually a verb (to influence); *effect* is usually a noun (a result). "The policy will *affect* margins. The *effect* will be significant." | +| *that* / *which* | *That* restricts; *which* adds information. Use *which* with commas. | +| *who* / *whom* | *Who* is the subject; *whom* is the object. Test: substitute *he/him*. "Who called?" (he called). "To whom was it sent?" (sent to him). | +| *fewer* / *less* | *Fewer* for countable nouns; *less* for uncountable. "Fewer employees, less revenue." | +| *comprise* / *compose* | The whole *comprises* its parts. The parts *compose* the whole. "The board comprises seven members." | +| *ensure* / *insure* | *Ensure* means to make certain; *insure* relates to insurance policies. | +| *principal* / *principle* | *Principal* is a leader or primary; *principle* is a fundamental rule. | + +--- + +## Prompts + +**Prompt 1 -- Grammar Audit:** +> Review the following business document for grammar errors, focusing on subject-verb agreement, pronoun case, dangling modifiers, and parallel construction. For each error found, quote the original sentence, explain the specific rule violated, and provide a corrected version. Document: [paste text] + +**Prompt 2 -- Usage Confusion Scan:** +> Examine this text for commonly confused words (affect/effect, that/which, who/whom, fewer/less, comprise/compose, ensure/insure, principal/principle). Flag every instance, explain whether it is used correctly, and suggest corrections where needed. Text: [paste text] + +**Prompt 3 -- Punctuation Overhaul:** +> Audit this document for punctuation errors, paying special attention to comma splices, missing serial commas, incorrect apostrophe usage, and hyphenation of compound adjectives. Provide a corrected version with annotations explaining each change. Document: [paste text] + +**Prompt 4 -- Before/After Credibility Rewrite:** +> Here is a paragraph from an investor update I am preparing: [paste text]. Rewrite it to eliminate all grammar and punctuation errors while preserving the original meaning and tone. Then list every change made and the rule that motivated it. + +--- + +## Use Cases + +**Validation-Stage Founder Preparing a Pitch Deck** +A solo founder preparing a twelve-slide seed pitch discovers, after a grammar audit, that three slides contain subject-verb disagreements and one uses "it's" as a possessive. The investor reading the deck is a former English major who served as managing editor of the Stanford Law Review. These errors would have been the first -- and possibly the last -- things noticed. The grammar check costs fifteen minutes. The unchecked alternative could have cost the meeting. + +**Growth-Stage Company Publishing an Annual Report** +A 200-person company preparing its first public annual report submits the draft for a grammar and mechanics review. The audit catches 23 punctuation inconsistencies (mixed usage of serial commas), 7 that/which confusions, and a dangling modifier in the CEO's letter that accidentally attributes declining margins to the board of directors rather than to market conditions. The corrected version avoids an embarrassment that, once printed and distributed, could not be recalled. + +**Early-Traction Startup Drafting Client Contracts** +A B2B SaaS startup discovers its standard client proposal template contains "less" where "fewer" is required, inconsistent hyphenation of compound modifiers, and three instances of comma splices. Since this template has been sent to forty prospects over six months, the cumulative credibility impact is sobering. Correcting the template takes twenty minutes and elevates the professionalism of every future client interaction. + +--- + +## Anti-Patterns + +1. **Hypercorrection.** Overcorrecting grammar to the point of producing stilted, unnatural prose. Writing "to whom should I direct this inquiry?" in a Slack message to a colleague is technically correct and socially absurd. The goal is correctness appropriate to context, not grammatical maximalism. + +2. **Grammar Policing in Feedback.** Using grammar knowledge to publicly correct colleagues' writing rather than privately and constructively improving shared documents. Grammar competence used as a status signal breeds resentment, not better writing. + +3. **Ignoring Grammar in Internal Documents.** Treating grammar as relevant only for external communications. Internal memos, Slack messages, and team updates also shape how people perceive competence. Sloppy internal writing creates sloppy habits that leak into external documents at the worst moments. + +4. **Relying Solely on Spell-Checkers.** Spell-check tools catch "teh" but miss "their" when you meant "there." Grammar-checking software has improved but still mishandles subject-verb agreement in complex sentences, that/which distinctions, and subtle comma splices. Automated tools supplement human review; they do not replace it. + +5. **Perfectionism as Procrastination.** Endless grammar revision as a means of avoiding the more difficult work of actually saying something. A grammatically perfect document that says nothing of substance is a polished void. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal credibility in initial pitches | At the idea stage, the founder *is* the product. Grammar errors in early pitch materials disproportionately damage credibility because there is no product traction to compensate. | +| Validation | Pitch decks and investor communications | Documents begin circulating to external audiences -- investors, advisors, potential partners. Every document is evaluated as evidence of operational competence. | +| Early Traction | Client-facing proposals and contracts | Proposals, contracts, and onboarding materials now represent the company to paying customers. Grammar errors signal carelessness in a context where trust is still fragile. | +| Growth | Standardising templates and style guides | With multiple people writing on behalf of the company, inconsistency becomes the primary risk. A company-wide style guide and grammar checklist become organisational infrastructure. | +| Scale | Brand consistency across all communications | At scale, grammar and mechanics become part of brand management. Training programmes, editorial review processes, and style enforcement tools ensure consistency across hundreds of authors. | + +--- + +## Output Template + +```markdown +# Grammar and Mechanics Audit: [Document Name] + +## Summary +- **Total errors found:** [number] +- **Critical errors (meaning-altering):** [number] +- **Credibility errors (noticeable but not meaning-altering):** [number] +- **Style inconsistencies:** [number] + +## Error Log + +| # | Original Text | Error Type | Rule Violated | Corrected Text | +|---|--------------|------------|---------------|----------------| +| 1 | [quote] | [grammar/punctuation/usage] | [specific rule] | [corrected version] | +| 2 | [quote] | [grammar/punctuation/usage] | [specific rule] | [corrected version] | + +## Recurring Patterns +- [Pattern 1: e.g., "Consistent misuse of that/which throughout"] +- [Pattern 2: e.g., "Serial comma used inconsistently"] + +## Recommendations +1. [Specific recommendation for preventing recurrence] +2. [Style guide addition suggested] +``` + +--- + +## Related Skills + +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Correct grammar is necessary but not sufficient; tone determines whether technically correct prose actually connects with readers. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- Email is the most frequent venue for grammar errors because speed and informality lower the writer's guard. +- **[Writing Memos and Reports](../../content/skills/writing/writing-memos-and-reports.md)** -- Formal documents demand the highest standard of grammatical precision because they persist in the organisational record. +- **[Writing Performance Reviews](../../content/skills/writing/writing-performance-reviews.md)** -- Performance evaluations carry legal implications, making grammatical precision not merely a matter of style but of institutional risk. +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- The editing pass is where grammar errors are caught systematically rather than relying on instinct during drafting. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- Many grammar errors stem from overly complex sentence constructions; plain language reduces the surface area for mechanical mistakes. diff --git a/plugins/foreman/skills/grow-model/SKILL.md b/plugins/foreman/skills/grow-model/SKILL.md deleted file mode 120000 index f87f3c5..0000000 --- a/plugins/foreman/skills/grow-model/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/grow-model.md \ No newline at end of file diff --git a/plugins/foreman/skills/grow-model/SKILL.md b/plugins/foreman/skills/grow-model/SKILL.md new file mode 100644 index 0000000..9a7ad01 --- /dev/null +++ b/plugins/foreman/skills/grow-model/SKILL.md @@ -0,0 +1,234 @@ +--- +name: "grow-model" +description: "Facilitates coaching conversations and structured decision-making using Whitmore's GROW model: Goal (clarify objectives), Reality (assess current state honestly), Options (generate alternatives), and Will (commit to action). Use when coaching team members, making strategic decisions as a founder, breaking through analysis paralysis, conducting self-coaching sessions on difficult choices, preparing one-on-ones, or developing management capability across a growing leadership team." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - coaching + - goal-setting + - problem-solving + - one-on-ones + - mentoring +related_skills: + - psychological-safety + - emotional-intelligence + - growth-mindset + - neuro-linguistic-programming +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# GROW Model + +A gardener does not grow a plant. A gardener creates the conditions -- soil, light, water, space -- in which the plant grows itself. John Whitmore, the British racing driver turned executive coach, built the GROW model on precisely this philosophy of human development. Published in his 1992 book *Coaching for Performance*, GROW offers a deceptively simple four-stage questioning framework that has become the most widely used coaching structure in the world. Its power lies not in telling people what to do but in asking them questions that unlock their own clarity. For entrepreneurs, who chronically suffer from both advice overload and decision paralysis, GROW provides a structured pathway from muddled intention to committed action -- and, equally valuable, a repeatable method for coaching the people they lead. + +--- + +## The Framework + +GROW is an acronym representing four sequential stages of a coaching conversation. Each stage has a distinct purpose and a characteristic set of questions. The coach (or self-coaching entrepreneur) moves through the stages in order, though real conversations often loop back as new insights emerge. + +### The Four Stages + +**G -- Goal** + +Establish what the person wants to achieve. Not vaguely ("I want to grow the business") but with specificity sufficient to recognise achievement. The goal stage separates wishful thinking from actionable intention. + +Essential questions: +- What do you want to achieve? +- What would make this conversation most valuable for you? +- What does success look like? How would you know you had achieved it? +- What is the timeframe? +- How ambitious is this goal on a scale of 1-10? +- Is this a performance goal (within your control) or an end goal (dependent on external factors)? + +The distinction between performance goals and end goals is critical for entrepreneurs. "Raise a Series A" is an end goal -- it depends on investor decisions outside the founder's control. "Complete 30 investor conversations and iterate the pitch to a 50% follow-up rate" is a performance goal -- fully within the founder's control and far more useful for coaching. + +**R -- Reality** + +Explore the current situation with unflinching honesty. Most people skip this stage, jumping from goal to action without understanding their starting position. The reality stage grounds ambition in fact. + +Essential questions: +- What is happening now? What is the current state? +- What have you tried so far? What happened? +- What obstacles are you facing? +- Who else is involved, and what is their perspective? +- On a scale of 1-10, where are you currently relative to your goal? +- What is the gap between where you are and where you want to be? +- What resources do you currently have? +- What internal factors (skills, beliefs, habits) are helping or hindering? + +The most valuable reality questions are those that surface uncomfortable truths the person has been avoiding. A skilled coach listens for omissions, euphemisms, and assumptions that have not been tested. + +**O -- Options** + +Generate the widest possible range of options before evaluating any of them. The critical discipline here is separating ideation from judgment. Most people generate two or three options and immediately begin debating their merits. The options stage insists on quantity first, quality second. + +Essential questions: +- What could you do? (Repeated multiple times to push past obvious answers) +- What else? (The most powerful coaching question -- it signals that the first answers are rarely the best) +- If you had no constraints, what would you do? +- What would you do if you knew you could not fail? +- What would someone you admire do in this situation? +- What would happen if you did nothing? +- What are the costs and benefits of each option? +- Which option excites you most? + +The "What else?" question deserves emphasis. Research on brainstorming shows that the first ideas generated are typically the most conventional. Genuine insight tends to emerge after the obvious options have been exhausted -- usually around the fifth or sixth option. + +**W -- Will (or Way Forward)** + +Convert the preferred option into a specific, committed action plan. This stage transforms insight into behaviour. Without it, coaching conversations produce understanding but not change. + +Essential questions: +- What will you do? (Not "what could you do" -- the shift to "will" is deliberate) +- When will you do it? +- What is the first step? +- On a scale of 1-10, how committed are you to this action? +- What might get in the way? +- How will you overcome those obstacles? +- Who needs to know about your plan? +- How will you hold yourself accountable? +- What support do you need? + +If commitment scores below 7, the action plan needs revision. Either the action is wrong, the timeline is unrealistic, or the person is not genuinely ready. Whitmore emphasises that low commitment is information, not failure -- it sends the conversation back to earlier stages. + +### GROW as Self-Coaching + +GROW is commonly presented as a tool for coaching others, but its highest-frequency use for entrepreneurs is self-coaching. The founder sits with a journal or an AI assistant and works through the four stages on a specific decision. The structure prevents the two most common failure modes of solo decision-making: rumination without progress (endlessly revisiting the problem without generating options) and premature action (jumping to solutions without understanding the reality or goal clearly). + +--- + +## Prompts + +**Prompt 1 -- Full GROW Session:** +> Run a complete GROW coaching session with me on this challenge: [describe challenge]. Start by helping me clarify my Goal with specific, measurable terms. Then explore my current Reality by asking probing questions about what I have tried, what I know, and what I might be avoiding. Generate at least 7 Options, pushing past the obvious ones. Finally, help me select and commit to specific actions with dates, accountability mechanisms, and contingency plans. Push back if my commitment is below 7/10 on any action. + +**Prompt 2 -- Reality Check:** +> I believe the current state of [aspect of my business] is: [describe your understanding]. Challenge my reality assessment using GROW Reality questions. Identify assumptions I may be making, perspectives I may be missing, and uncomfortable truths I may be avoiding. Rate my reality assessment on a 1-10 scale for completeness and honesty, and tell me what a 10 would include that my current assessment does not. + +**Prompt 3 -- Options Expansion:** +> I am stuck between these options for [decision]: [list 2-3 options you are considering]. Using the GROW Options methodology, generate at least 5 additional options I have not considered. Include at least one option that is radically different from my current thinking, one that involves doing nothing, and one that reframes the problem entirely. For each option, provide a one-sentence summary of its primary advantage and primary risk. + +**Prompt 4 -- Coaching Preparation:** +> I need to have a coaching conversation with [team member name/role] about [issue]. Design a GROW-structured conversation plan with specific questions for each stage, tailored to what I know about this person: [describe their situation, personality, likely resistance points]. Include suggested responses for likely pushback and a plan for what to do if commitment remains low after the Will stage. + +**Prompt 5 -- Weekly GROW Review:** +> Review my progress on last week's GROW commitments: [list what you committed to and what actually happened]. For any actions not completed, diagnose whether the barrier was in the Goal (wrong target), Reality (unexpected obstacle), Options (wrong approach), or Will (insufficient commitment). Adjust the plan accordingly and set this week's GROW commitments. + +--- + +## Use Cases + +**Idea-stage founder choosing between two venture concepts** + +A would-be founder is paralysed between two startup ideas and has spent four months "thinking about it" without making progress on either. A GROW self-coaching session reveals that the stated goal ("decide which idea to pursue") is actually a performance goal disguised as a binary choice. The reality exploration uncovers that the founder's paralysis stems from fear of choosing wrong, not from insufficient information. The options stage generates a third path neither idea had suggested: running a two-week validation sprint on each idea simultaneously, using pre-defined criteria to compare results. The will stage produces a specific calendar with blocked time, measurable milestones, and a hard decision date. The founder launches both sprints and, within two weeks, has enough data to commit with confidence. + +**Growth-stage CTO coaching a struggling engineering manager** + +A CTO notices that a recently promoted engineering manager is overwhelmed and reverting to individual contributor behaviour -- writing code instead of managing the team. Rather than giving directive advice ("Stop coding and start managing"), the CTO uses GROW. The goal stage reveals the manager wants to "feel effective again" -- which surfaces the real issue (identity transition, not skill deficit). The reality stage uncovers that the manager has never received management training and is using coding as a psychological safety blanket. The options stage generates possibilities ranging from formal training to peer mentoring to a temporary reduction in direct reports. The will stage produces a commitment to complete a management fundamentals course within 60 days and to schedule weekly one-on-ones with each direct report starting immediately. Crucially, the manager arrived at these actions herself -- the CTO asked questions rather than prescribed solutions. + +**Scale-stage CEO self-coaching on a potential acquisition** + +A CEO is considering whether to acquire a smaller competitor. Using GROW with an AI assistant, the goal stage clarifies that the acquisition's purpose is customer base expansion, not technology acquisition -- a distinction that had been blurred in board discussions. The reality stage reveals that the company's integration track record is poor (two of three past integrations underperformed projections). The options stage generates eight alternatives to acquisition, including partnership, licensing, and organic expansion into the competitor's market segment. The will stage produces a commitment to complete a formal integration readiness assessment before bringing the acquisition proposal to the board, with a hard deadline of six weeks. + +--- + +## Anti-Patterns + +**1. Rushing to the Will stage.** The most common misapplication of GROW is treating it as a goal-setting tool rather than an exploratory process. Coaches (and self-coaching entrepreneurs) who sprint through Goal and Reality to reach Will produce superficially actionable but poorly grounded plans. The value of GROW is proportional to the time spent in Reality and Options. + +**2. Asking leading questions disguised as coaching.** "Don't you think you should fire that underperformer?" is not a GROW question -- it is advice with a question mark attached. Genuine GROW coaching requires the coach to suspend their own opinions and trust the process. For founders, who are accustomed to having strong views and sharing them, this discipline is genuinely difficult. + +**3. Using GROW for problems that require direction, not coaching.** If a building is on fire, coaching someone through options for extinguishing it is inappropriate. Some situations require direct instruction: compliance issues, safety concerns, ethical violations, and time-critical emergencies. GROW works best when the person being coached has the latent capability to find their own answer and the time to do so. + +**4. Treating the model as rigidly sequential.** Real conversations are not linear. A person exploring reality may discover that their goal needs revision. An option may surface a reality they had overlooked. Skilled GROW practitioners move fluidly between stages while maintaining overall forward momentum. Rigid adherence to the sequence produces stilted, unnatural conversations. + +**5. Accepting vague goals and weak commitments.** "I want to improve my leadership" is not a GROW-ready goal. "I want my direct reports to rate my feedback quality at 8/10 or above in the next quarterly survey" is. Similarly, accepting "I'll try to do that next week" as a will statement guarantees nothing will happen. The discipline of GROW lies in its insistence on precision. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder self-coaching on direction and commitment | GROW helps convert vague entrepreneurial impulse into specific, testable hypotheses | +| Validation | Customer discovery, hypothesis refinement | Reality questions discipline the founder to assess market signals honestly rather than selectively | +| Early Traction | Coaching first hires, decision-making under pressure | GROW becomes a management tool; the founder coaches rather than directs | +| Growth | Management development, strategic choices | GROW scales through the management layer; training managers to coach is a force multiplier | +| Scale | Executive coaching, board-level decision-making | GROW's structured approach brings rigour to complex, multi-stakeholder strategic decisions | + +GROW applies at every stage, but its primary function shifts. At the idea and validation stages, it is predominantly a self-coaching tool: the founder uses it to structure their own thinking and avoid the twin traps of analysis paralysis and premature action. + +At early traction and growth, GROW becomes an organisational tool. Founders who coach rather than direct build teams that are more autonomous, more engaged, and more capable of solving problems independently. The transition from "I'll tell you what to do" to "What do you think you should do?" is one of the most important leadership shifts a scaling founder must make, and GROW provides the structure for making it. + +At scale, GROW's value lies in its ability to bring structured clarity to decisions of genuine complexity. Board-level strategic choices, executive succession planning, and organisational transformation all benefit from the disciplined progression through goal, reality, options, and commitment. + +--- + +## Output Template + +```markdown +# GROW Coaching Record -- [Topic/Decision] + +**Date:** [Date] +**Coached by:** [Self / Coach name] +**Session focus:** [One-sentence description of the challenge] + +## G -- Goal +- **Stated goal:** [Initial goal as articulated] +- **Refined goal:** [Goal after clarification -- specific, measurable, time-bound] +- **Goal type:** [Performance goal / End goal] +- **Ambition level:** [1-10] + +## R -- Reality +- **Current state:** [Honest assessment of where things stand] +- **What has been tried:** [Previous attempts and their outcomes] +- **Key obstacles:** [Internal and external barriers] +- **Current position vs. goal:** [1-10] +- **Uncomfortable truth surfaced:** [The thing that was being avoided] + +## O -- Options Generated + +| # | Option | Primary Advantage | Primary Risk | +|---|--------|-------------------|-------------| +| 1 | [Option] | [Advantage] | [Risk] | +| 2 | [Option] | [Advantage] | [Risk] | +| 3 | [Option] | [Advantage] | [Risk] | +| 4 | [Option] | [Advantage] | [Risk] | +| 5 | [Option] | [Advantage] | [Risk] | + +**Selected option:** [Which option and why] + +## W -- Will / Way Forward + +| Action | Deadline | Commitment (1-10) | Accountability | +|--------|----------|-------------------|----------------| +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | +| [Specific action] | [Date] | [Score] | [How you will be held accountable] | + +**Potential obstacles:** [What might prevent follow-through] +**Contingency plan:** [What to do if obstacles materialise] +**Review date:** [When to assess progress] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- GROW coaching requires a foundation of psychological safety; the Reality stage demands honesty that is only possible when the coachee feels safe being candid. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Effective GROW coaching depends on the coach's empathy (reading the coachee's emotional state) and the coachee's self-awareness (providing honest reality assessments). +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework provides the belief system that makes GROW productive; a person with a fixed mindset will resist the Reality stage and generate constrained Options. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- SBI identifies specific behavioural issues that then become the starting point for a GROW coaching conversation to develop the forward-looking action plan. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Provides the broader leadership context for deploying GROW as part of a systematic coaching and development practice across a growing organization. +- **[SMART Goals](../../content/skills/frameworks/smart-goals.md)** -- The Goal stage of GROW produces better outcomes when goals meet SMART criteria, ensuring the coaching conversation is anchored in specific, measurable commitments. diff --git a/plugins/foreman/skills/growth-mindset/SKILL.md b/plugins/foreman/skills/growth-mindset/SKILL.md deleted file mode 120000 index 49815ae..0000000 --- a/plugins/foreman/skills/growth-mindset/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/growth-mindset.md \ No newline at end of file diff --git a/plugins/foreman/skills/growth-mindset/SKILL.md b/plugins/foreman/skills/growth-mindset/SKILL.md new file mode 100644 index 0000000..b3e792f --- /dev/null +++ b/plugins/foreman/skills/growth-mindset/SKILL.md @@ -0,0 +1,175 @@ +--- +name: "growth-mindset" +description: "Applies Carol Dweck's growth mindset framework to individual resilience and organizational culture, distinguishing between fixed mindset (ability is innate) and growth mindset (ability develops through effort and strategy). Use when processing failure and setbacks, reframing team responses to challenges, designing hiring interview protocols that assess learning orientation, transforming performance review systems, building learning cultures in startups, or diagnosing why a team avoids risk and experimentation." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth +tags: + - mindset + - learning + - resilience + - talent-development + - culture +related_skills: + - psychological-safety + - flow-state + - emotional-intelligence + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Growth Mindset + +In 1998, Carol Dweck and Claudia Mueller published a study that quietly detonated decades of received wisdom about praise. They told one group of children they were smart after they solved a problem. They told another group they had worked hard. The "smart" children subsequently avoided challenging tasks, collapsed under difficulty, and lied about their scores. The "hard work" children sought harder problems, persisted longer, and performed better. That single experiment -- replicated and extended over the next two decades at Stanford -- revealed something profound about the architecture of human motivation: the beliefs people hold about the nature of their own abilities fundamentally shape how they respond to setbacks, challenges, and opportunities. Dweck formalised this into two orientations -- fixed mindset and growth mindset -- and in doing so provided a framework that has reshaped education, sport, and, increasingly, how organisations think about talent, innovation, and culture. + +--- + +## The Framework + +### Fixed vs. Growth: The Two Orientations + +The distinction is not about optimism versus pessimism, or effort versus laziness. It concerns a deeper belief about the malleability of human capability. + +| Dimension | Fixed Mindset | Growth Mindset | +|-----------|--------------|----------------| +| **Core belief** | Ability is innate and static | Ability is developed through effort, strategy, and learning | +| **Response to challenge** | Avoids challenges that risk exposing inadequacy | Embraces challenges as learning opportunities | +| **Response to failure** | Interprets failure as evidence of inherent limitation | Interprets failure as information about what to adjust | +| **Response to effort** | Views effort as proof of insufficient talent | Views effort as the path to mastery | +| **Response to criticism** | Defensive; takes feedback personally | Seeks feedback as developmental input | +| **Response to others' success** | Threatened; perceives it as diminishing own standing | Inspired; studies it for learnable lessons | + +Dweck's research demonstrates that these orientations are not permanent personality traits but contextual beliefs that can shift. A person may hold a growth mindset about their technical skills and a fixed mindset about their leadership ability. The orientations are domain-specific and mutable. + +### The Mechanism: Effort-Belief Connection + +The psychological engine beneath the framework is the relationship between effort and meaning. In a fixed mindset, effort signals inadequacy -- if you were truly talented, you would not need to try so hard. In a growth mindset, effort signals investment -- struggle is the mechanism through which ability expands. This single interpretive difference cascades through every decision a founder makes: whether to enter unfamiliar markets, whether to hire people who challenge them, whether to persist after a failed launch, whether to accept board feedback or dismiss it. + +### Growth Mindset in Organisations + +Dweck's later research extended the framework from individuals to organisations. Companies with growth-mindset cultures -- where learning, experimentation, and development are valued over proving brilliance -- exhibit measurably different behaviours: + +- Employees report more trust and commitment +- Innovation increases because failure is treated as data, not disgrace +- Collaboration improves because individuals are not competing to prove they are the smartest person in the room +- Ethical behaviour increases because employees feel less pressure to cut corners to maintain an image of effortless competence + +Conversely, "genius cultures" -- organisations that prize innate talent above all -- exhibit higher rates of fraud, internal competition, and stagnation. Enron is the canonical cautionary tale: a culture that celebrated brilliance and punished visible struggle created an environment where admitting problems was career suicide. + +### The "Not Yet" Principle + +One of Dweck's most actionable contributions is the reframe from "I can't do this" to "I can't do this yet." The addition of a single word transforms a fixed-mindset statement into a growth-mindset trajectory. For founders, "We don't have product-market fit" is a verdict in fixed mindset and a status update in growth mindset. "Yet" implies a process underway, not a condition concluded. + +--- + +## Prompts + +**Prompt 1 -- Mindset Diagnostic:** +> Analyse my team's recent response to this setback: [describe setback and how the team reacted]. Classify the predominant reactions as fixed-mindset or growth-mindset indicators. Identify specific language, decisions, and behaviours that reveal the underlying belief system. Recommend three concrete changes to team rituals or communication patterns that would shift the culture toward growth mindset. + +**Prompt 2 -- Failure Reframe:** +> We experienced the following failure: [describe failure in detail]. Help me process this through a growth-mindset lens. Structure the analysis as: (a) what specifically failed (separate from identity), (b) what was learned that was not knowable before, (c) what strategies should change based on this information, and (d) a specific "not yet" reframe I can share with the team that acknowledges the failure honestly while orienting toward continued development. + +**Prompt 3 -- Hiring for Growth Mindset:** +> I need to assess growth mindset in candidates for [role]. Design an interview protocol with 5 behavioural questions that reveal a candidate's mindset orientation. For each question, describe what a fixed-mindset response sounds like versus a growth-mindset response. Include one practical exercise or case study that would surface mindset orientation under pressure. + +**Prompt 4 -- Culture Audit:** +> Evaluate whether my company's practices signal a growth mindset or a fixed mindset. Here are our current practices: [describe hiring criteria, performance review process, how failure is discussed, how promotions are decided, how praise is given, how challenges are framed]. For each practice, identify whether it reinforces a fixed or growth orientation and suggest specific modifications. + +--- + +## Use Cases + +**Idea-stage solo founder facing repeated rejection** + +A first-time founder has received 30 rejections from investors and is questioning whether entrepreneurship is "not for me." This is textbook fixed-mindset framing: failure interpreted as evidence of inherent unsuitability. Applying Dweck's framework, a mentor reframes the situation: rejection is feedback, not verdict. The mentor and founder systematically analyse the rejections for patterns (unclear value proposition, unconvincing market sizing, weak competitive analysis), extract specific learnable improvements for each, and set a target of iterating the pitch through five distinct versions. By version four, the founder secures a meeting that leads to a pre-seed commitment. The outcome did not change because the founder gained new innate talent; it changed because they treated their pitching ability as developable. + +**Growth-stage startup transforming performance reviews** + +A 120-person SaaS company discovers that its annual performance review process, inherited from a corporate playbook, is producing anxiety, defensiveness, and attrition among top performers. Analysis reveals a fixed-mindset architecture: reviews are evaluative ("meets expectations," "exceeds expectations," "below expectations"), focused on judging past performance against static standards. The company redesigns the process around growth-mindset principles: reviews become development conversations focused on trajectory, learning goals, and skill acquisition. Ratings are replaced with growth plans. The language shifts from "where you fell short" to "what you're building toward." Within two review cycles, engagement scores rise by 18 points and voluntary attrition among high performers drops by half. + +--- + +## Anti-Patterns + +**1. "Growth mindset" as toxic positivity.** Telling someone to "just have a growth mindset" about a genuine structural problem -- inadequate funding, impossible market conditions, toxic co-founder dynamics -- trivialises legitimate obstacles. Growth mindset means believing that abilities can develop through effort and strategy; it does not mean that effort alone can overcome any obstacle. Some situations require strategic withdrawal, not motivational reframing. + +**2. Praising effort divorced from strategy and outcome.** Dweck herself has warned against this misapplication. Praising effort that produces no learning or improvement is not growth mindset -- it is false comfort. The growth-mindset response to ineffective effort is to examine and improve the strategy, not to celebrate the trying. "You worked really hard but the approach didn't work -- what can we change?" is the correct formulation. + +**3. Using growth mindset to justify under-investing in talent.** Some organisations adopt growth mindset language to rationalise not hiring experienced people: "We'll just grow into the capability." Development takes time, and some situations require competence now. Growth mindset applies to developing capabilities over reasonable timescales, not to ignoring current skill gaps in urgent contexts. + +**4. Creating a fixed mindset about fixed mindset.** Labelling someone as "having a fixed mindset" and treating that label as a permanent character diagnosis is itself a fixed-mindset move. Mindset is contextual and mutable. The constructive approach is to address the specific belief in the specific context, not to categorise the person. + +**5. Ignoring systemic barriers.** Growth mindset operates at the individual and cultural level. It does not address structural inequalities, resource constraints, or market failures. Telling an underfunded founder in a discriminatory funding environment to "develop a growth mindset" without addressing the systemic barriers is unhelpful at best and insulting at worst. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder resilience and identity | The founder must separate self-worth from the idea's viability; "my idea failed" is not "I am a failure" | +| Validation | Interpreting negative signals | Fixed mindset ignores disconfirming evidence; growth mindset treats every customer rejection as actionable data | +| Early Traction | Building learning culture from day one | First hires absorb the founder's mindset orientation; this is the highest-leverage moment to establish growth-oriented norms | +| Growth | Scaling learning systems | Individual growth mindset must become organisational infrastructure: learning budgets, post-mortem practices, development-oriented reviews | + +The idea stage is where growth mindset matters most viscerally. The founder is psychologically fused with the venture; rejection of the idea feels like rejection of the self. Dweck's framework provides the critical separation: the idea is a hypothesis, not an identity. Testing and refining hypotheses is what scientists do, and no scientist concludes they are personally inadequate because an experiment produced unexpected results. + +At early traction, the founder's mindset becomes contagious. The first ten employees will pattern-match on how the founder responds to failure, feedback, and challenge. A founder who models growth mindset -- openly discussing mistakes, seeking feedback, treating setbacks as learning events -- creates a culture where these behaviours are normal. A founder who performs brilliance and hides struggle creates a culture where the same is expected of everyone, with corrosive effects on innovation and psychological safety. + +--- + +## Output Template + +```markdown +# Growth Mindset Culture Assessment -- [Company Name] + +**Prepared for:** Leadership Team +**Date:** [Date] +**Assessment scope:** [Company-wide / Department / Team] + +## Current Mindset Indicators + +| Practice Area | Current Approach | Mindset Signal | Recommended Shift | +|--------------|-----------------|----------------|-------------------| +| Hiring | [How talent is assessed] | [Fixed/Growth] | [Specific change] | +| Performance reviews | [Current process] | [Fixed/Growth] | [Specific change] | +| Failure response | [How failures are discussed] | [Fixed/Growth] | [Specific change] | +| Praise patterns | [What gets celebrated] | [Fixed/Growth] | [Specific change] | +| Challenge framing | [How hard problems are presented] | [Fixed/Growth] | [Specific change] | + +## Language Audit +**Fixed-mindset phrases detected in company communications:** +- "[Phrase]" -- Growth-mindset alternative: "[Alternative]" +- "[Phrase]" -- Growth-mindset alternative: "[Alternative]" + +## Team Development Trajectories + +| Team Member / Role | Current Growth Area | "Not Yet" Statement | 90-Day Learning Goal | +|-------------------|--------------------|--------------------|---------------------| +| [Name/Role] | [Skill being developed] | "[I can't X yet]" | [Measurable target] | + +## Recommended Rituals +1. **[Ritual name]:** [Description and frequency] +2. **[Ritual name]:** [Description and frequency] +3. **[Ritual name]:** [Description and frequency] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Growth mindset requires psychological safety to function; people will not admit mistakes or embrace challenges if they fear punishment, making Edmondson's work the essential organisational complement. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Csikszentmihalyi's flow depends on operating at the edge of current ability, which requires a growth-mindset belief that ability expands through challenge rather than being threatened by it. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- The self-awareness domain of EQ enables founders to recognise when they are operating from a fixed-mindset orientation and consciously shift to growth. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Provides the leadership practices for systematically extracting learning from setbacks, which is the organisational expression of growth mindset in action. +- **[Learning Agility](../../content/skills/leadership/learning-agility.md)** -- Extends Dweck's individual mindset framework into the organisational capability of rapidly learning and adapting in unfamiliar situations. +- **[Creative Obstacles](../../content/skills/creative/creative-obstacles.md)** -- Addresses the specific creative blocks that arise from fixed-mindset thinking, providing techniques for reframing creative challenges as growth opportunities. diff --git a/plugins/foreman/skills/growth-share-matrix/SKILL.md b/plugins/foreman/skills/growth-share-matrix/SKILL.md deleted file mode 120000 index a0af042..0000000 --- a/plugins/foreman/skills/growth-share-matrix/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/growth-share-matrix.md \ No newline at end of file diff --git a/plugins/foreman/skills/growth-share-matrix/SKILL.md b/plugins/foreman/skills/growth-share-matrix/SKILL.md new file mode 100644 index 0000000..ef752ef --- /dev/null +++ b/plugins/foreman/skills/growth-share-matrix/SKILL.md @@ -0,0 +1,224 @@ +--- +name: "growth-share-matrix" +description: "Analyzes product and business unit portfolios using the BCG Growth Share Matrix, classifying offerings into Stars, Cash Cows, Question Marks, and Dogs based on market growth rate and relative market share. Use when making resource allocation decisions across multiple products or business lines, evaluating which initiatives to invest in or divest, prioritizing a product portfolio, diagnosing why certain products drain resources without returns, or planning strategic investment sequencing at growth and scale stages." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - growth + - scale +tags: + - portfolio-management + - resource-allocation + - product-strategy + - strategic-planning + - investment-prioritisation +related_skills: + - product-life-cycle + - balanced-scorecard + - swot-pest-analysis + - disruptive-innovation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Growth Share Matrix (BCG Matrix) + +The Boston Consulting Group's Growth Share Matrix turns business strategy into a menagerie. Stars blaze with potential, demanding heavy investment to maintain their orbit. Cash Cows graze contentedly in mature pastures, generating the capital that funds everything else. Question Marks pace nervously at the edge of relevance, consuming resources without certainty of return. And Dogs -- the uncomfortable truth in every portfolio -- sit in low-growth, low-share positions, consuming management attention that would be better spent elsewhere. Bruce Henderson introduced this taxonomy in 1970 with a one-page BCG Perspectives paper, and it became perhaps the single most influential framework in corporate strategy because it answered a question that every leader with more than one product or business unit faces: where should we invest, and where should we stop? + +The framework's elegance lies in its simplicity: two axes, four quadrants, clear strategic prescriptions. Its danger lies in the same simplicity -- applied mechanically, it can lead to catastrophic misallocation. Applied thoughtfully, it remains one of the sharpest tools for forcing honest conversation about where a company's future actually lies. + +--- + +## The Framework + +### The Two Axes + +**Vertical Axis: Market Growth Rate** + +The rate at which the market itself is expanding. High-growth markets attract investment, generate opportunity, and forgive mistakes. Low-growth markets reward efficiency, punish excess, and reward the already-dominant. The dividing line is contextual -- 10% annual growth might be the threshold for consumer technology, while 3% might distinguish high from low in industrial manufacturing. + +**Horizontal Axis: Relative Market Share** + +Your market share divided by the market share of your largest competitor. A ratio above 1.0 means you are the market leader; below 1.0 means someone else is. Relative share matters more than absolute share because market leadership confers cost advantages, brand recognition, and bargaining power that scale non-linearly. + +### The Four Quadrants + +``` + HIGH relative market share LOW relative market share + +---------------------------------+---------------------------------+ + | | | + HIGH market | STARS | QUESTION MARKS | + growth rate | | (Problem Children) | + | High growth + Market leader | High growth + Not leading | + | Strategy: Invest heavily | Strategy: Invest or divest | + | Cash flow: Roughly neutral | Cash flow: Highly negative | + | | | + +---------------------------------+---------------------------------+ + | | | + LOW market | CASH COWS | DOGS | + growth rate | | | + | Low growth + Market leader | Low growth + Not leading | + | Strategy: Harvest profits | Strategy: Divest or liquidate | + | Cash flow: Highly positive | Cash flow: Neutral to negative| + | | | + +---------------------------------+---------------------------------+ +``` + +#### Stars (High Growth, High Share) + +Stars are the future of the business. They hold leadership positions in markets that are growing rapidly. The challenge: high-growth markets demand continuous investment in sales, marketing, production capacity, and product development. Stars consume cash almost as fast as they generate it. The strategic imperative is to invest enough to maintain share as the market grows. A star that loses share during the growth phase will become a question mark; a star that maintains share as the market matures becomes a cash cow. + +*For startups:* Your core product in a market experiencing rapid adoption is your star. Do not starve it. The temptation to diversify prematurely -- launching adjacent products before the core product has captured its natural share -- is a common cause of startup failure during growth. + +#### Cash Cows (Low Growth, High Share) + +Cash cows are the economic engine. They hold dominant positions in mature markets where growth has slowed. Because the market is stable and the position is secure, cash cows generate surplus capital that exceeds what they need for maintenance. This surplus funds stars, selectively feeds question marks, and provides the financial resilience to weather downturns. + +*For startups:* Most early-stage startups do not have cash cows. The first cash cow often emerges when a product that drove initial growth enters maturity. Recognising this transition -- and shifting from growth investment to harvest mode -- is one of the most difficult psychological adjustments for founders. + +#### Question Marks (High Growth, Low Share) + +Question marks are strategic bets. They operate in attractive, high-growth markets but have not achieved the market share needed to generate positive returns. They consume cash heavily with uncertain payoff. The strategic decision is binary: invest aggressively to build share and convert to a star, or divest before the cash drain becomes unsustainable. + +*For startups:* Every new product line, geographic expansion, or market extension starts as a question mark. The discipline is ruthless triage: which question marks have a credible path to leadership, and which are consuming resources that would be better deployed elsewhere? + +#### Dogs (Low Growth, Low Share) + +Dogs are the quadrant that nobody wants to discuss. They hold weak positions in unattractive markets. They rarely generate meaningful profit and often consume disproportionate management attention. The orthodox prescription is clear: divest, wind down, or liquidate. But dogs persist in portfolios because of emotional attachment ("It was our first product"), sunk cost fallacy ("We've invested too much to quit"), or political dynamics ("The VP who built it is still on the leadership team"). + +*For startups:* A feature or product that has plateaued with minimal usage, generates no revenue growth, and distracts engineering resources from the core product is a dog. Killing it frees resources. Keeping it signals indecision. + +### The Portfolio Lifecycle + +Products naturally move through the matrix over time: + +``` +Question Mark --> Star --> Cash Cow --> (eventually) Dog + | + v + Dog (if investment fails) +``` + +A healthy portfolio has: +- One or two **Stars** receiving heavy investment +- One or more **Cash Cows** funding the portfolio +- A limited number of **Question Marks** under active evaluation +- No **Dogs** -- or Dogs actively being wound down + +An unhealthy portfolio has too many question marks (cash drain without a funding source), no stars (no future growth), or too many dogs (resource distraction). + +--- + +## Prompts + +**Prompt 1 -- Portfolio Classification:** +> "Classify each of our products/business lines into the BCG Growth Share Matrix: [list products with their market growth rate and relative market share or competitive position]. For each product, recommend the strategic action: invest (Star), harvest (Cash Cow), selectively invest or divest (Question Mark), or wind down (Dog). Explain the cash flow implications of the current portfolio balance." + +**Prompt 2 -- Resource Allocation Decision:** +> "Given this portfolio: [list products with their BCG classification, current revenue, growth rate, and investment level], how should we reallocate resources? Specifically: (1) Are we over-investing in any Cash Cows? (2) Are we under-investing in any Stars? (3) Which Question Marks deserve increased investment and which should be divested? (4) What is the total cash flow impact of the recommended reallocation?" + +**Prompt 3 -- Portfolio Health Assessment:** +> "Assess the health of our product portfolio: [list products with metrics]. Map each product's trajectory over the past [timeframe]. Which products are moving in the right direction (Question Mark to Star, Star to Cash Cow)? Which are moving in the wrong direction (Star to Question Mark, Cash Cow to Dog)? What strategic interventions would correct the negative trajectories?" + +--- + +## Use Cases + +**Growth-Stage SaaS Company With Multiple Products** + +A SaaS company with $10M ARR has three products: a project management tool ($7M ARR, 40% YoY growth, market leader in its segment), an invoicing add-on ($2M ARR, 5% growth, third in a mature market), and a newly launched resource planning module ($1M ARR, 80% growth, fifth in a fast-growing market). BCG classification: project management is a Star transitioning toward Cash Cow territory as growth decelerates. Invoicing is a Dog -- low growth, low relative share, and consuming engineering resources disproportionate to its contribution. Resource planning is a Question Mark -- high growth market, but significant share gap to close. The strategic recommendation: redirect engineering resources from invoicing (wind down or sell the product line) toward the resource planning module (invest to build share while the market is still forming), while ensuring the project management tool receives sufficient investment to maintain its leadership position through the growth-to-maturity transition. + +**Scale-Stage Consumer Brand Evaluating Geographic Expansion** + +A consumer brand present in five countries treats each market as a portfolio entry. The home market (US) is a Cash Cow: 35% market share, 3% market growth, generating $15M in annual free cash flow. The UK is a Star: 22% share in a market growing at 15%. Germany is a Question Mark: 4% share in a market growing at 12%. Japan and Brazil are Dogs: sub-3% share in markets growing at 2-4%. The portfolio diagnosis is immediate: use US cash flows to fund UK growth, make a decisive bet on Germany (invest to reach 10% share within 18 months or exit), and wind down Japan and Brazil operations to eliminate the management distraction and cash drain. The reallocation frees $3M annually and focuses the leadership team on two winnable markets instead of five. + +**Growth-Stage Marketplace Prioritising Feature Investment** + +An emerging marketplace applies the BCG framework not to products but to feature sets. Core matching algorithm: Star (high usage growth, market-leading in user satisfaction). Payments infrastructure: Cash Cow (stable, reliable, generates transaction revenue, low growth in usage). Social features: Question Mark (high engagement among early adopters, unclear path to monetisation). Analytics dashboard: Dog (low adoption, no growth, built for a use case that the market rejected). The analysis drives a product roadmap that increases matching algorithm investment by 30%, maintains payments, gives social features a 90-day prove-or-kill timeline, and deprecates the analytics dashboard. + +--- + +## Anti-Patterns + +**Mechanical Application Without Context.** Plotting products on the matrix and blindly following the textbook prescriptions. A "dog" product may serve as a loss leader that drives traffic to a star. A "cash cow" may need reinvestment because a disruptive competitor is eroding its position. The matrix is a starting point for strategic conversation, not a substitute for it. + +**Ignoring Interdependencies.** Products in a portfolio often share customers, technology, or brand equity. Divesting a dog that serves as the entry product for customers who eventually upgrade to the star would damage the star's pipeline. Portfolio analysis must account for these connections. + +**Treating Relative Market Share as Destiny.** A low relative share in a nascent market does not mean the same thing as a low relative share in a mature market. In emerging markets, share positions are fluid and achievable. The Question Mark quadrant requires nuanced assessment of share trajectory, not just current position. + +**Cash Cow Neglect.** The prescription to "harvest" cash cows is frequently interpreted as "stop investing entirely." Cash cows require maintenance investment -- product updates, customer retention efforts, infrastructure upkeep. A neglected cash cow becomes a declining revenue source faster than expected, starving the portfolio of the cash that funds everything else. + +**Emotional Attachment to Dogs.** The most difficult strategic discipline is killing products. Founders who built the company on a product that has become a dog find it psychologically impossible to wind it down. The BCG matrix provides the analytical cover for a decision that sentiment resists. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Growth | Identify your star and protect it | Most growth-stage startups have one product; the matrix helps decide whether to remain focused or begin portfolio expansion | +| Scale | Manage the portfolio actively | Multiple products and markets require systematic resource allocation; the matrix provides the framework | + +At the growth stage, the BCG matrix is most useful as a discipline against premature diversification. The temptation to launch new products (question marks) before the core product has achieved market leadership (star status) is a pattern that destroys companies. The matrix makes the trade-off explicit: every dollar invested in a question mark is a dollar not invested in strengthening the star. + +At scale, the matrix becomes an essential governance tool. Quarterly portfolio reviews that map every product and market to the matrix create accountability for investment decisions and force the difficult conversations about which question marks deserve continued funding and which dogs need to be wound down. + +--- + +## Output Template + +**Target Audience: CEO / Board of Directors** + +```markdown +# Portfolio Strategy Review: [Company Name] +## Period: [Quarter/Year] + +### Portfolio Map + +| Product/Business Unit | Market Growth Rate | Relative Market Share | BCG Quadrant | Revenue | Cash Flow | +|-----------------------|-------------------|----------------------|--------------|---------|-----------| +| [Product A] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | +| [Product B] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | +| [Product C] | [X%] | [X.X] | [Star/Cash Cow/QM/Dog] | [$X] | [+/- $X] | + +### Portfolio Health +- Stars: [N] -- Funded adequately? [Y/N] +- Cash Cows: [N] -- Generating sufficient surplus? [Y/N] +- Question Marks: [N] -- Clear invest/divest decision for each? [Y/N] +- Dogs: [N] -- Wind-down plans in place? [Y/N] + +### Cash Flow Dynamics +- Total cash generated (Cash Cows): [$X] +- Total cash consumed (Stars + Question Marks): [$X] +- Net portfolio cash flow: [+/- $X] +- Sustainability assessment: [Self-funding / Requires external capital / Unsustainable] + +### Strategic Decisions Required +| Decision | Options | Recommendation | Financial Impact | +|----------|---------|---------------|-----------------| +| [Product/market decision] | [Option A vs. Option B] | [Recommendation] | [Projected impact] | + +### Resource Reallocation Plan +| From | To | Amount | Rationale | +|------|----|--------|-----------| +| [Source product/unit] | [Target product/unit] | [$X or X headcount] | [Why this reallocation] | + +### 12-Month Portfolio Trajectory +| Product | Current Quadrant | Projected Quadrant | Key Assumption | +|---------|-----------------|-------------------|----------------| +| [Product] | [Current] | [Projected] | [What must be true] | +``` + +--- + +## Related Skills + +- **[Product Life Cycle](../../content/skills/frameworks/product-life-cycle.md)** -- The BCG matrix and the product life cycle are deeply intertwined; products naturally move from Question Mark (introduction) to Star (growth) to Cash Cow (maturity) to Dog (decline). +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- While the BCG matrix drives portfolio-level resource allocation, the Balanced Scorecard measures execution effectiveness within each product or business unit. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- PEST identifies the macro forces that determine market growth rates; SWOT reveals the competitive factors that determine relative market share. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Disruption often transforms a Cash Cow into a Dog faster than the BCG matrix's gradual trajectory suggests, making Christensen's framework the essential early warning system. +- **[Ambidexterity](../../content/skills/frameworks/ambidexterity.md)** -- The BCG matrix reveals why ambidexterity is structurally necessary: Cash Cows fund exploitation while Question Marks and Stars represent the exploration portfolio. +- **[Evaluating Options](../../content/skills/decisions/evaluating-options.md)** -- Provides structured decision-making methods for the invest-or-divest choices that the BCG matrix forces on Question Mark products. diff --git a/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md b/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md deleted file mode 120000 index 2f47b18..0000000 --- a/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/hackman-enabling-conditions.md \ No newline at end of file diff --git a/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md b/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md new file mode 100644 index 0000000..89301fa --- /dev/null +++ b/plugins/foreman/skills/hackman-enabling-conditions/SKILL.md @@ -0,0 +1,223 @@ +--- +name: "hackman-enabling-conditions" +description: "Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance probable. Use when teams are underperforming despite talent, designing new team structures, onboarding a leadership hire, auditing why a specific team is stuck, or building the organizational infrastructure for effective teams at scale." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - team-effectiveness + - organizational-design + - management + - team-structure + - leadership + - performance +related_skills: + - belbin-team-roles + - tuckman-team-stages + - lewin-leadership-styles + - situational-leadership + - leadership-pipeline +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Hackman's Enabling Conditions for Team Effectiveness + +Most team failures are not the team's fault. This is the central, uncomfortable conclusion of J. Richard Hackman's decades of research at Harvard on team performance -- research that studied airline cockpit crews, intelligence analysts, symphony orchestras, and corporate project teams. When a team underperforms, the reflexive organizational response is to blame the people: not talented enough, not motivated enough, not collaborative enough. Hackman's research redirects attention upward. In the majority of cases, the team fails because the conditions for success were never established. The soil was toxic; blaming the seeds for not growing is both lazy and wrong. + +Hackman published his definitive framework in *Leading Teams: Setting the Stage for Great Performances* (2002), identifying five conditions that, when present, make team effectiveness probable -- and when absent, make it improbable regardless of how talented, committed, or well-intentioned the team members are. The framework shifts the leader's primary task from managing the team to designing the environment in which the team operates. + +--- + +## The Framework + +Hackman's five enabling conditions form a hierarchy: each builds upon the previous. Condition 1 is foundational; without it, the others are meaningless. Condition 5 is the capstone, rarely present but transformative when it is. + +### Condition 1: Being a Real Team + +**The checklist question:** Is this group actually a team, or merely a collection of individuals who report to the same manager? + +A real team has three properties: +- **Clear boundaries** -- Everyone knows who is on the team and who is not. Ambiguous membership diffuses accountability and prevents cohesion. +- **Interdependence** -- Members need each other to accomplish the work. If everyone can complete their tasks independently, you have a workgroup, not a team -- and workgroups require different management. +- **Stability** -- Membership remains reasonably constant. Hackman's research shows that teams with frequent membership changes never reach high performance because they perpetually reset to Tuckman's Forming stage. + +**Why this fails in startups:** Founders often create "teams" that are actually loosely affiliated individuals working on adjacent tasks. The engineering "team" may consist of people building independent features who never need to coordinate. Calling them a team creates expectations of collaboration without the structural reality of interdependence. + +### Condition 2: Compelling Direction + +**The checklist question:** Does the team have a purpose that is clear, challenging, and consequential? + +Compelling direction has three qualities: +- **Clear** -- The team knows what it is trying to achieve. Not a vague mission statement, but a specific outcome that can be assessed. +- **Challenging** -- The goal stretches the team beyond comfortable execution. Hackman found that moderately challenging goals produce higher performance than easy goals or impossibly ambitious ones. +- **Consequential** -- The work matters. To the organization, to customers, to the team members themselves. Teams that perceive their work as trivial perform trivially. + +**Why this fails in startups:** Ironically, early-stage startups often have too much direction (the founder's passionate vision) rather than too little -- but the direction is not translated into specific, assessable team-level goals. "Change the world" is not a compelling direction. "Achieve 1,000 daily active users by Q3" is. + +### Condition 3: Right People + +**The checklist question:** Does the team have the right mix of skills, experience, and interpersonal abilities? + +Right people means: +- **Technical competence** sufficient for the task +- **Interpersonal skill** sufficient for collaboration +- **Diversity of perspective** sufficient for creative problem-solving +- **Absence of members who are actively destructive** -- Hackman's research shows that one member who is persistently aggressive, cynical, or disengaged can reduce team performance by 30-40% + +**Why this fails in startups:** Founders hire for technical skill and ignore interpersonal fit. Or they hire friends and ignore skill gaps. Belbin's team roles framework provides the granular lens for this condition; Hackman provides the structural imperative. + +### Condition 4: Sound Structure + +**The checklist question:** Does the team have the right norms, roles, and task design? + +Sound structure includes: +- **Task design** that is whole and meaningful -- not fragmented into pieces so small that no one sees the whole +- **Team size** that is as small as possible for the task (Hackman found that the right number is almost always fewer than managers think) +- **Clear norms** about communication, decision-making, conflict resolution, and quality standards +- **Explicit roles** that leverage individual strengths without creating rigid silos + +**Why this fails in startups:** Over-reliance on flat structures and informal norms. "We don't need process" is the rallying cry of teams that eventually discover they desperately need process -- usually after a painful failure that clear norms would have prevented. + +### Condition 5: Supportive Organizational Context + +**The checklist question:** Does the broader organization provide the resources, information, and support the team needs? + +Supportive context means: +- **Reward systems** that recognize team performance, not just individual achievement +- **Information systems** that give the team access to the data it needs +- **Educational systems** that provide training and development +- **Material resources** sufficient for the work -- tools, budget, time + +**Why this fails in startups:** Resource scarcity is endemic. But the more pernicious failure is reward structure: startups that celebrate individual heroes while their team objectives languish systematically undermine this condition. + +### The Sixth Condition: Expert Coaching (Bonus) + +Hackman later added a sixth condition: the availability of competent coaching at the right time. Not a permanent coach hovering over the team, but a skilled intervener who can help the team at three critical moments -- the beginning (establishing norms), the midpoint (course-correcting), and the end (learning from the experience). + +--- + +## Prompts + +**Prompt 1 -- Five Conditions Audit:** +> Evaluate my team against Hackman's five enabling conditions. Here's the context: Team size: [number]. Team purpose: [describe]. Members: [describe]. How we work: [describe structure, norms, processes]. Organizational context: [describe resources, reward systems, information access]. Score each condition (Strong / Adequate / Weak / Absent) with specific evidence, and identify the single most impactful condition to improve first. + +**Prompt 2 -- "Real Team" Diagnostic:** +> I suspect my "team" may not actually be a real team in Hackman's definition. Here's how we work: [describe the group's membership clarity, interdependence level, and membership stability]. Diagnose whether we are a real team, a workgroup, or something in between. If we're not a real team, should we become one (by restructuring for interdependence) or should we acknowledge we're a workgroup and manage accordingly? + +**Prompt 3 -- Structural Redesign:** +> My team of [size] working on [project/function] has the right people and a clear direction but is underperforming. Using Hackman's Condition 4 (Sound Structure), analyze our current structure: [describe team norms, roles, task design, meeting cadence, decision-making process]. Identify structural deficiencies and propose specific changes to norms, roles, or task design that would improve effectiveness. + +**Prompt 4 -- Organizational Context Gap Analysis:** +> My team performs well internally but is frustrated by organizational barriers. Using Hackman's Condition 5, analyze these friction points: [describe -- e.g., "We can't get data from the analytics team," "Our bonus structure rewards individual goals," "We don't have budget for the tools we need"]. Prioritize which context failures are most damaging to team effectiveness and propose solutions I can implement or advocate for. + +--- + +## Use Cases + +**High-Talent Team Delivering Mediocre Results** + +A growth-stage fintech company has assembled an expensive product team: former Google engineers, a designer from Stripe, a product manager from Uber. Individual resumes are impeccable. Output is disappointing. The CEO's instinct is to question individual commitment. A Hackman audit reveals the real problems. Condition 1: boundaries are unclear -- three other people occasionally contribute to the team's work without formal membership. Condition 2: direction is vague -- "make the product best-in-class" is not a compelling, assessable goal. Condition 4: no explicit norms exist for decision-making, so every disagreement becomes a negotiation from first principles. The people are right (Condition 3). The organizational context provides adequate resources (Condition 5). Fixing Conditions 1, 2, and 4 -- clarifying membership, setting specific goals, and establishing decision-making norms -- transforms team output within one quarter without changing a single person on the team. + +**Remote Team Lacking Supportive Context** + +A scale-stage company's remote customer success team consistently underperforms its in-office counterpart. Management attributes this to the inherent limitations of remote work. A Hackman analysis tells a different story. Condition 5 is severely compromised: the remote team lacks access to the real-time customer data available on the office dashboard, the reward system celebrates "visible effort" that inherently favors office workers, and the training programs are designed for in-person delivery with no remote adaptation. The team itself is sound (Conditions 1-4 are adequate). The organizational context is failing them. Redesigning information access, reward criteria, and training delivery for remote parity closes the performance gap within two quarters. + +--- + +## Anti-Patterns + +- **Blaming People Before Auditing Conditions.** The default organizational response to team failure: assume the people are the problem. Hackman's research demonstrates that replacing team members while leaving dysfunctional conditions intact produces the same poor results with different faces. Audit conditions before auditing people. + +- **Over-investing in Coaching While Neglecting Structure.** Hiring team coaches, running offsites, and investing in "team chemistry" while the team lacks clear boundaries, a compelling direction, or sound structural norms. Coaching is Hackman's sixth condition -- a bonus that enhances a solid foundation. Coaching cannot compensate for structural deficiency. + +- **Treating Every Group as a Team.** Not all work requires teamwork. Some work is best done by individuals coordinated through a manager. Forcing team structures onto independent work creates the overhead of coordination without the benefit of interdependence. Hackman explicitly distinguishes real teams from workgroups and argues that both are valid -- the error is misclassifying one as the other. + +- **Assuming Conditions Are Set Once.** Treating the five conditions as a launch checklist rather than ongoing maintenance requirements. Conditions degrade. Membership changes erode Condition 1. Shifting strategy undermines Condition 2. Scaling introduces new resource constraints that compromise Condition 5. Periodic re-auditing is essential. + +- **Optimizing the Wrong Condition First.** Investing in team skills training (Condition 3) when the real bottleneck is unclear direction (Condition 2). The conditions form a rough hierarchy; addressing lower-numbered conditions first typically yields higher returns. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establishing Conditions 1-3 | The founding team must become a real team with clear direction and the right mix of people; structure and organizational context are informal but sufficient at small scale | +| Growth | Formalizing Condition 4 | As teams multiply and grow, sound structure becomes the differentiator; informal norms that worked at 10 people fail at 50 | +| Scale | Building Condition 5 systemically | Organizational context -- reward systems, information access, resource allocation -- becomes the primary enabler or blocker of team effectiveness at scale | + +--- + +## Output Template + +```markdown +# Hackman Enabling Conditions Audit: [Team Name] + +**Date:** [Date] +**Team:** [Name and purpose] +**Auditor:** [Your role] + +## Condition Assessment + +### 1. Real Team +- **Clear boundaries:** [Yes/No -- who's in, who's out?] +- **Interdependence:** [High/Medium/Low -- do members need each other?] +- **Stability:** [Stable/Unstable -- recent membership changes?] +- **Score:** [Strong / Adequate / Weak / Absent] +- **Evidence:** [Specific observations] + +### 2. Compelling Direction +- **Clarity:** [Can every member state the goal identically?] +- **Challenge:** [Is the goal stretching but achievable?] +- **Consequence:** [Does the work matter?] +- **Score:** [Strong / Adequate / Weak / Absent] +- **Evidence:** [Specific observations] + +### 3. Right People +- **Technical competence:** [Sufficient/Gaps in ___] +- **Interpersonal skill:** [Strong/Adequate/Problematic] +- **Diversity of perspective:** [Sufficient/Limited] +- **Destructive members:** [None/Concern about ___] +- **Score:** [Strong / Adequate / Weak / Absent] + +### 4. Sound Structure +- **Task design:** [Whole and meaningful / Fragmented] +- **Team size:** [Right-sized / Too large / Too small] +- **Norms:** [Explicit and functional / Implicit / Absent] +- **Roles:** [Clear / Ambiguous / Conflicting] +- **Score:** [Strong / Adequate / Weak / Absent] + +### 5. Supportive Context +- **Rewards:** [Team-oriented / Individual-oriented] +- **Information access:** [Sufficient / Restricted] +- **Training:** [Available / Absent] +- **Resources:** [Sufficient / Constrained] +- **Score:** [Strong / Adequate / Weak / Absent] + +## Priority Intervention +**Weakest condition:** [Number and name] +**Recommended action:** [Specific intervention] +**Expected impact:** [What improvement to expect] +**Timeline:** [How long before results] + +## Overall Team Effectiveness Forecast +[Based on condition scores, predict team trajectory and recommend focus areas] +``` + +--- + +## Related Skills + +- **[Belbin Team Roles](../../content/skills/frameworks/belbin-team-roles.md)** -- Belbin provides the detailed lens for Hackman's Condition 3 (Right People), specifying which behavioral roles the team needs for balance. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Hackman's conditions create the environment through which Tuckman's developmental stages unfold; poor conditions stall the team permanently in Forming or Storming. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's psychological safety is the interpersonal climate dimension within Hackman's Condition 4 (Sound Structure) and Condition 5 (Supportive Context). +- **[Leadership Pipeline](../../content/skills/frameworks/leadership-pipeline.md)** -- Senior pipeline passages are fundamentally about creating Hackman's conditions for the teams and organizations one leads, shifting focus from personal contribution to environment design. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Provides the leadership practices for building and maintaining the enabling conditions across growing and evolving teams. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Condition 5 (Supportive Context) requires leaders to delegate genuine authority and resources, not just tasks, to enable team effectiveness. diff --git a/plugins/foreman/skills/humility-and-power/SKILL.md b/plugins/foreman/skills/humility-and-power/SKILL.md deleted file mode 120000 index 9d464b0..0000000 --- a/plugins/foreman/skills/humility-and-power/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/humility-and-power.md \ No newline at end of file diff --git a/plugins/foreman/skills/humility-and-power/SKILL.md b/plugins/foreman/skills/humility-and-power/SKILL.md new file mode 100644 index 0000000..dc65b18 --- /dev/null +++ b/plugins/foreman/skills/humility-and-power/SKILL.md @@ -0,0 +1,209 @@ +--- +name: "humility-and-power" +description: "Addresses the corrosive effects of power on leadership and prescribes humility as the primary antidote. Covers staying humble as authority grows, recognising the early signs of ego distortion, creating channels for honest feedback, acknowledging weaknesses as a strength, and maintaining genuine connection with the people one leads. Use when sensing disconnection from the team, receiving less bad news than seems realistic, noticing sycophantic behaviour in direct reports, struggling with ego after a promotion, or seeking to prevent the corruption that accompanies institutional power." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - humility + - power + - ego + - self-awareness + - vulnerability + - inclusive-leadership + - feedback + - corruption +related_skills: + - emotional-intelligence + - trust-equation + - psychological-safety + - emotional-courage + - purpose-driven-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Humility and Power + +The moment you stop hearing bad news is the moment you should worry most. Not because bad news has ceased to exist, but because the people around you have decided it is safer to hide it than to share it. This is the signature symptom of power's corruption -- not the dramatic villainy of corporate scandal, but the quiet, incremental insulation that turns a connected leader into an isolated one. Power does not corrupt through a single moral failure. It corrupts through a thousand small adjustments: people laugh at jokes that are not funny, agree with ideas that are not sound, and withhold objections that need voicing. The leader, bathed in this artificial warmth, mistakes compliance for alignment and silence for agreement. Humility is the only reliable antidote, and it must be practised with the same discipline as any other leadership competency -- because power never stops working against it. + +--- + +## The Framework + +### The Corruption Mechanism + +Power corrupts not through malice but through distortion. As a leader's authority grows, three things happen simultaneously: + +**First, attention narrows.** Research consistently demonstrates that people at the top become less attentive to those below them. This is not callousness; it is cognitive economics. Power shifts the brain's attention toward goals and away from the people affected by those goals. The leader who does not deliberately counteract this drift will "not see" the people they lead -- and those people will know it. + +**Second, feedback filters tighten.** Subordinates calibrate their honesty to the perceived safety of the environment. The more powerful the leader, the more subordinates manage information upward -- softening bad news, inflating good news, and withholding dissent. The leader receives an increasingly curated version of reality, and the gap between this version and actual reality widens with every rung of authority. + +**Third, ego inflates.** Promotions, titles, and organisational deference create a feedback loop. People listen more attentively, agree more readily, and laugh more frequently. This feels like validation. It is, in fact, distortion. The ego, mistaking sycophancy for substance, grows to fill the space that power creates. Breaking free of this dynamic requires selflessness, reflection, and courage -- and the awareness that the dynamic is operating at all. + +### The Humility Practice + +Humility is not self-deprecation. It is the accurate assessment of one's abilities, limitations, and impact on others. For leaders with power, humility must be practised deliberately because power's natural current flows against it. + +**Practice 1: Make "I don't know" acceptable -- starting with yourself.** + +Admitting ignorance is the highest-leverage humility behaviour. It accomplishes three things simultaneously: it builds trust (people trust those who are honest about their limitations more than those who perform omniscience), it opens the door for others' expertise (subordinates will offer knowledge only when they believe the leader values it), and it models the learning behaviour that organisations need at every level. + +The practice begins at the top. When the leader asks a question they genuinely do not know the answer to, and visibly learns from the response, they signal that knowledge matters more than hierarchy. + +**Practice 2: Create robust channels for unvarnished truth.** + +The default communication channels in most organisations are compromised by power dynamics. Town halls, skip-level meetings, and open-door policies all suffer from the same flaw: they require the less powerful person to initiate honesty with the more powerful one. This is asking the person with the most to lose to take the risk. + +Effective channels reverse the burden: + +| Channel | How It Works | Why It Helps | +|---------|-------------|-------------| +| Anonymous feedback systems | Structured, recurring, with visible leadership response | Removes identity risk from truth-telling | +| "Ask me anything" forums | Leader commits to answering all questions, including uncomfortable ones | Demonstrates willingness to be challenged | +| Reverse mentoring | Junior employees mentor senior leaders on areas of junior expertise | Flattens the power dynamic temporarily | +| External advisory input | Board members, coaches, or peers outside the org hierarchy | Provides perspective uncontaminated by internal power dynamics | +| Structured dissent | Meetings where someone is explicitly assigned to argue the opposing view | Normalises disagreement as a leadership practice | + +**Practice 3: Acknowledge weaknesses as a source of strength.** + +The instinct to project competence at all times is understandable and counterproductive. It is unsustainable -- everyone makes mistakes, and the leader who hides them creates an impossible standard. It is isolating -- people connect with human beings, not with curated images of human beings. And it is strategically foolish -- a leader who cannot name their weaknesses cannot compensate for them. + +The distinction is critical: having weaknesses is not the same as being weak. A leader who says "I am not strong at financial modelling, so I have built a team that is" demonstrates more competence than one who bluffs through a spreadsheet. + +**Practice 4: Stay curious about the people you lead.** + +Power's attention-narrowing effect makes it progressively harder to see individuals as individuals rather than as functions. The antidote is deliberate curiosity: remembering that each person has a context beyond their role, asking questions that are not performance-related, and demonstrating that the leader's interest in their people extends beyond their utility. + +This is not about being "nice." It is about being effective. People who feel seen by their leader contribute more, flag problems earlier, and remain with the organisation longer. People who feel invisible to their leader contribute the contractual minimum and leave at the first opportunity. + +### The Seven Humility Questions + +A self-assessment tool that no leader can answer with perfect accuracy (humility, by definition, resists self-measurement) but that directs attention to the right areas: + +1. Do I seek feedback, even if it is critical? +2. Do I admit when I do not know how to do something? +3. Do I acknowledge when others have more knowledge or skills than I do? +4. Do I take note of others' strengths? +5. Do I compliment others on their strengths? +6. Do I show appreciation for others' contributions? +7. Am I willing to learn from others? + +The value of these questions lies not in the answers but in the practice of asking them regularly, with honesty, and -- critically -- with someone who is willing to disagree with the leader's self-assessment. + +--- + +## Prompts + +**Prompt 1 -- Power Corruption Audit:** +> I hold a leadership position of [describe role and scope of authority]. Help me assess whether power is distorting my leadership. Ask me about the last time I received genuinely bad news from a subordinate, the last time someone disagreed with me in a meeting, and the last time I changed my mind based on input from someone junior. Based on my answers, assess my corruption risk and recommend specific countermeasures. + +**Prompt 2 -- Feedback Channel Design:** +> My organisation has [describe current feedback mechanisms]. I suspect they are not producing honest input because [describe symptoms -- e.g., feedback is uniformly positive, the same issues persist despite "resolution," or senior leaders seem surprised by employee survey results]. Design a set of feedback channels that make it safer for people to tell me what I need to hear rather than what I want to hear. Account for my organisation's size [size], culture [describe], and my own leadership style [describe]. + +**Prompt 3 -- Ego Assessment:** +> I have recently [describe a promotion, success, or expansion of authority]. Help me assess whether my ego is expanding with my power. Ask me diagnostic questions about how I respond to disagreement, how much I talk versus listen in meetings, whether I have noticed changes in how people interact with me, and whether I have sought out any honest external perspective. Then provide a frank assessment and specific ego-management practices. + +**Prompt 4 -- Humility in Practice:** +> I want to model humility more effectively for my team. My current approach includes [describe what you currently do]. Assess whether these behaviours are genuine humility or performative humility, and recommend specific daily practices that would make my humility more authentic and more visible to the people I lead. + +--- + +## Use Cases + +**Early-Traction Founder Transitioning from Peer to Boss** + +A founding team of four engineers has been working as equals for eighteen months. With a seed round closed, the lead founder is now officially CEO and the others are reports. The relationship dynamics shift overnight: the three engineers begin deferring to the CEO in technical discussions where they previously debated as peers. The CEO notices fewer challenges to their architectural decisions and, initially, enjoys the smoother meetings. Then a production incident reveals that two engineers had concerns about the architecture but did not voice them. The CEO institutes a "structured dissent" practice: in every architectural review, one engineer is explicitly assigned to argue against the proposed approach. The practice recovers the intellectual honesty that the power differential had silenced. + +**Growth-Stage VP Receiving Curated Reality** + +A VP of Sales consistently receives optimistic pipeline reports from regional directors. Forecast accuracy has declined for three consecutive quarters, but the VP attributes this to market conditions rather than information distortion. An external coach asks the VP when they last heard a regional director say "this deal is not going to close" -- and the VP cannot recall a single instance. The diagnosis is clear: the VP's authority has created a reporting environment where only good news travels upward. The VP redesigns the pipeline review format to require every director to identify their three most at-risk deals and explain why they might lose them. Initially, the meetings are uncomfortable. Within two quarters, forecast accuracy improves by 25% because the VP is finally operating on reality rather than aspiration. + +**Scale-Stage CEO Managing Ego After IPO** + +A CEO who built a company from a garage to a public offering notices that board meetings have become progressively shorter and more agreeable. Analysts praise the company. Media requests multiply. The CEO begins to assume that the absence of dissent reflects the quality of their decisions rather than the intimidation of their position. A long-tenured board member, one of the few who predates the CEO's success, delivers a private warning: "You used to ask the board for advice. Now you present conclusions." The CEO, to their credit, hears the warning and acts: they engage an executive coach, institute quarterly "reverse mentoring" sessions with junior employees, and restructure board meetings to begin with open questions rather than executive presentations. The quality of board input -- and the quality of decisions -- improves measurably. + +--- + +## Anti-Patterns + +1. **Performing humility without practising it.** Using self-deprecating language in public ("I'm just lucky to work with such a talented team") while privately making unilateral decisions and dismissing input. People detect the gap between humble words and controlling actions with remarkable precision. + +2. **Seeking feedback through channels contaminated by power.** Asking direct reports "Be honest -- how am I doing?" in a one-on-one meeting and interpreting the polite response as genuine feedback. The power dynamic makes honesty in this format nearly impossible. Feedback systems must be designed to mitigate power, not ignore it. + +3. **Treating humility as weakness.** In competitive or high-pressure cultures, humility is sometimes dismissed as indecisiveness or lack of confidence. This conflation is both common and wrong. Humility is the accurate calibration of one's abilities; arrogance is the inaccurate inflation of them. The humble leader makes better decisions because they operate on better information. + +4. **Assuming the ego problem is someone else's.** The CEO who reads about ego corruption and thinks "My leadership team could use this" is exhibiting the very blindness the concept describes. Power's distortion affects everyone who holds it; the belief that one is immune is the first symptom. + +5. **Outsourcing humility to systems.** Installing anonymous feedback tools and 360-degree reviews while personally remaining closed to challenge. Systems are necessary but insufficient; the leader's personal willingness to be changed by what they hear is the irreplaceable ingredient. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Peer-to-boss transition | The founder's power is new and its effects are immediately visible in changed team dynamics. Establishing humility practices before power distortion takes root is both easier and more critical. | +| Growth | Feedback infrastructure | As the organisation grows beyond the founder's personal relationships, humility must be embedded in systems -- feedback channels, meeting structures, decision processes -- rather than depending on the founder's personal warmth. | +| Scale | Institutional humility | The leader's ego management is no longer a personal project; it is a cultural imperative. Power at scale insulates more completely, and the countermeasures must be proportionally robust. | + +The progression follows a consistent pattern: what begins as a personal practice must evolve into an organisational capability. A humble founder can sustain humility through personal discipline at ten employees. At a hundred, they need systems. At a thousand, they need a culture that perpetuates humility independent of any single leader. + +--- + +## Output Template + +```markdown +# Humility and Power Assessment + +## Power Corruption Risk +| Indicator | Signal | Current Status | +|-----------|--------|---------------| +| Bad news frequency | When was the last time a subordinate told me something I didn't want to hear? | [Date and description] | +| Dissent in meetings | When was the last time someone disagreed with me publicly? | [Date and description] | +| Mind changes | When did I last change a decision based on junior input? | [Date and description] | +| Deference increase | Have people become more agreeable over time? | [Assessment] | + +## Feedback Channel Audit +| Channel | Exists? | Produces Honest Input? | Power-Mitigated? | +|---------|---------|----------------------|-----------------| +| Anonymous feedback | [Yes/No] | [Assessment] | [Yes/No] | +| Skip-level meetings | [Yes/No] | [Assessment] | [Yes/No] | +| External advisors | [Yes/No] | [Assessment] | [Yes/No] | +| Structured dissent | [Yes/No] | [Assessment] | [Yes/No] | + +## Ego Health Check (Seven Questions) +| Question | Honest Answer | Evidence | +|----------|--------------|----------| +| Do I seek critical feedback? | [Yes/Somewhat/No] | [Specific example] | +| Do I admit when I don't know? | [Yes/Somewhat/No] | [Specific example] | +| Do I acknowledge others' superior knowledge? | [Yes/Somewhat/No] | [Specific example] | +| Do I notice others' strengths? | [Yes/Somewhat/No] | [Specific example] | +| Do I compliment others' strengths? | [Yes/Somewhat/No] | [Specific example] | +| Do I appreciate others' contributions? | [Yes/Somewhat/No] | [Specific example] | +| Am I willing to learn from anyone? | [Yes/Somewhat/No] | [Specific example] | + +## Humility Action Plan +| Practice | Frequency | First Step | Success Indicator | +|----------|-----------|-----------|-------------------| +| [Practice 1] | [Daily/Weekly/Monthly] | [Specific action] | [How I will know it is working] | +| [Practice 2] | [Frequency] | [Action] | [Indicator] | +| [Practice 3] | [Frequency] | [Action] | [Indicator] | +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness, the core component of emotional intelligence, is the cognitive infrastructure that makes humility possible; without it, a leader cannot accurately assess the gap between self-perception and reality. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Humility directly reduces the self-orientation variable in the trust equation's denominator; a humble leader is, by the formula's logic, a more trustworthy one. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Humility in leadership is the single strongest predictor of psychological safety on a team; when the leader models vulnerability and welcomes challenge, the team follows. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Admitting weakness, seeking critical feedback, and confronting one's own ego all require emotional courage; humility without courage is merely awareness without action. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- Purpose serves as an ego counterweight; leaders anchored in something larger than themselves are less susceptible to power's inflating effects. +- **[Stoic Duty and Service](../../content/skills/stoic/stoic-duty-and-service.md)** -- Marcus Aurelius's practice of power through service rather than authority provides the philosophical foundation for the humility practices described here. diff --git a/plugins/foreman/skills/inclusive-leadership/SKILL.md b/plugins/foreman/skills/inclusive-leadership/SKILL.md deleted file mode 120000 index 0a1c2de..0000000 --- a/plugins/foreman/skills/inclusive-leadership/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/inclusive-leadership.md \ No newline at end of file diff --git a/plugins/foreman/skills/inclusive-leadership/SKILL.md b/plugins/foreman/skills/inclusive-leadership/SKILL.md new file mode 100644 index 0000000..05dd32a --- /dev/null +++ b/plugins/foreman/skills/inclusive-leadership/SKILL.md @@ -0,0 +1,216 @@ +--- +name: "inclusive-leadership" +description: "Provides daily practices for building genuinely inclusive teams through language audits, bias interruption, equitable hiring, cross-cultural sensitivity, and systemic fairness. Use when team composition lacks diversity, when DEI initiatives face backlash, when women or underrepresented groups stall in advancement, when networking events inadvertently exclude, or when a leader's inclusive intent does not match their observable behaviour." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - inclusion + - diversity + - equity + - bias + - gender + - culture + - hiring + - belonging +related_skills: + - lean-in + - psychological-safety + - emotional-intelligence + - trust-equation + - storytelling-for-leaders + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Inclusive Leadership + +Five questions. Answer them honestly, right now, about your last thirty days of leadership: + +1. Whose name did you put forward for a stretch assignment -- and whose name never crossed your mind? +2. Which voices spoke most in your last five meetings, and which were silent? +3. When you last wrote a job description, did anyone outside your demographic review the language? +4. At your most recent informal team event, who left early or did not attend -- and did you notice? +5. When an employee's effort fell short, did your internal attribution differ depending on the person's gender, race, or background? + +If any answer produces discomfort, the discomfort is the data. Inclusive leadership is not a posture one adopts during annual training and then shelves. It is a daily practice -- a set of observable behaviours repeated with enough consistency that they reshape the systems around the leader. The structural barriers facing women, people of colour, and other underrepresented groups are well documented elsewhere (see the companion skill on Sandberg's analysis in `lean-in.md`). This skill concerns itself with what a leader actually does about those barriers between Monday morning and Friday evening. + +--- + +## The Practice + +### Four Freedoms as a Daily Filter + +Laura Morgan Roberts identifies four freedoms that inclusive leaders cultivate: + +- **Authenticity** -- People can be who they are, not who they think the organisation wants them to be. +- **Growth** -- Everyone has equal access to learning, stretch assignments, and sponsorship. +- **Respite** -- People can occasionally fade into the background without being penalised for low visibility. +- **Failure** -- Mistakes are treated as learning events, not career-ending incidents. + +These are not abstract values. They are testable. At the end of each week, a leader can ask: "Did my actions this week expand or contract each of these freedoms for every person on my team?" + +### System-Level Intervention, Not Personal Correction + +DEI initiatives reliably produce backlash when framed as a judgement on individuals. Lily Zheng's research demonstrates that the most effective approach reframes the effort entirely: the target is the system, not the person. A leader diagnoses specific inequities using quantitative and qualitative data -- HR metrics, surveys, focus groups, demographic breakdowns -- and then presents the case for change as a matter of fixing policies, processes, and practices. Nobody is being blamed. Structures are being repaired. + +The practical difference is stark. "You need unconscious-bias training" puts people on the defensive. "Our promotion process produces a 2:1 male-to-female ratio despite an equal applicant pool -- let us examine why" invites collective problem-solving. + +### Closing the Gender Gap: Seven Leverage Points + +Drawing from Ammerman and Groysberg's research, inclusive leaders intervene at every stage of the talent lifecycle: + +| Stage | Action | What It Looks Like in Practice | +|-------|--------|-------------------------------| +| Applicant pool | Remove masculine-coded language from job descriptions | Replace "competitive ninja" with "collaborative software engineer" | +| Hiring | Anonymise resumes, diversify interview panels | Blind first-round screens; ensure no panel is homogeneous | +| Onboarding | Prevent tokenism, build networks proactively | Assign sponsors (not just mentors) to new hires from underrepresented groups | +| Development | Equalise stretch assignments and sponsorship | Track who receives high-visibility projects by demographic quarterly | +| Compensation | Publish salary ranges, audit pay equity annually | List median salaries on job postings; conduct regression-based pay audits | +| Promotion | Base decisions on data, not self-nomination | Women who appear ambitious face backlash; remove reliance on self-advocacy | +| Retention | Reward results, not hours; do not penalise flexibility | Flexible work should not be a career penalty | + +### Bias as Infrastructure + +Herminia Ibarra, Robin Ely, and Deborah Kolb coined the term "second-generation bias" to describe workplace structures that disadvantage women without anyone intending discrimination. The concept is critical because it shifts the question from "Who is biased?" to "Which of our structures produce biased outcomes?" Performance feedback is a prime example: high-performing women routinely receive the message "trim your sharp elbows," while equally assertive men receive no such counsel. The leader's job is not to referee individual feedback conversations but to audit the feedback system itself. + +### Cross-Cultural Nuance + +Erin Meyer's research warns against relying on cultural clichés when leading international teams. Effective cross-cultural leaders seek local counsel, adapt their style, and resist the seductive simplicity of national stereotypes. The daily practice: before applying a leadership behaviour across cultures, consult someone embedded in the target culture about expectations around feedback, decision-making, and trust-building. + +### Inclusive Language as Infrastructure + +Terms like "hacker," "ninja," or "rockstar" in job descriptions deter women, people of colour, people with disabilities, and older candidates. Hamilton, Kohler, Bradley Cox, and Lordan recommend creating a company guide to inclusive language -- crowdsourced, regularly updated, and treated as living infrastructure rather than a one-time memo. + +### Intersectional Attention + +Psychological safety is not distributed equally. Black women face compounded barriers requiring specific interventions: manager training in cultural humility, salary audits focused on the intersection of race and gender, policies examined for hidden bias in coaching and performance management, and safe spaces for experience-sharing. Generic DEI commitments that do not address intersecting identities leave the most marginalised employees unprotected. + +### Inclusive Networking + +Informal events -- happy hours, golf outings, after-work drinks -- often inadvertently exclude. Ruchika Tulshyan's guidance: learn dietary restrictions, avoid centring every event around alcohol, schedule some gatherings during working hours, and track attendance patterns. If certain employees consistently do not show up, the event design is the problem, not the employee. + +--- + +## Prompts + +**Prompt 1 -- Inclusion Audit:** +> Review my team's last quarter: [describe team composition, recent hires, promotions, stretch assignments, meeting participation patterns, and informal event attendance]. Identify where inclusion gaps may exist using the four-freedoms framework (authenticity, growth, respite, failure). For each gap, recommend one structural change I can implement within 30 days. + +**Prompt 2 -- Language Review:** +> Audit the following job description for exclusionary language, masculine-coded terms, unnecessary superlatives, and terms that may deter candidates from underrepresented groups: [paste job description]. Rewrite it using neutral, inclusive alternatives while preserving the role's requirements. + +**Prompt 3 -- Systems Diagnosis:** +> Our organisation has the following demographic data across levels: [provide data]. Using Lily Zheng's systems-focused approach, identify which policies, practices, or structures most likely explain the patterns. Frame the analysis as a systems problem, not a people problem, and draft a one-page case for change suitable for presentation to senior leadership. + +**Prompt 4 -- Cross-Cultural Adaptation:** +> I am leading a team spanning [list countries/cultures]. Using Erin Meyer's framework, identify three areas where my default leadership style may clash with team members' cultural expectations. For each, suggest a specific behavioural adaptation I can practise this week. + +--- + +## Use Cases + +**Growth-stage startup with an all-male leadership team** + +A 60-person fintech startup realises that despite hiring women at the entry level, none have advanced to director roles. The founder audits the promotion process and discovers two structural issues: promotions rely heavily on self-nomination (which research shows disadvantages women) and stretch assignments are distributed informally through a network that skews male. The fix is structural: promotion criteria are codified, stretch assignments are tracked by demographic quarterly, and sponsorship (not just mentorship) is formalised for high-potential women. Within two promotion cycles, three women reach director level. + +**Scale-stage company with DEI backlash** + +A 400-person enterprise launches a diversity initiative that triggers resentment among some employees who feel judged. Leadership reframes the initiative using Zheng's systems approach: the problem is not that employees are biased but that the company's hiring pipeline, feedback mechanisms, and networking norms produce unequal outcomes. Resources previously labelled "diversity programmes" are rebranded as fairness-focused tools available to anyone. Backlash subsides; participation increases. + +**Early-traction remote team with cross-cultural friction** + +A 15-person distributed team spanning four countries experiences recurring miscommunication. The founder attributes it to personality differences until a cross-cultural audit reveals structural mismatches: direct feedback norms appropriate in the Netherlands are perceived as harsh by team members in Japan; consensus-based decision-making expected by the Tokyo office frustrates the Berlin contingent's bias toward speed. The leader implements culture-specific communication protocols and consults local advisors before applying uniform policies. + +--- + +## Anti-Patterns + +**1. Performative inclusion.** Declaring "we value diversity" on the website while every leadership meeting features the same demographic profile is worse than silence. Employees notice the gap between rhetoric and reality faster than leaders expect. + +**2. Diversity as a business case only.** Framing inclusion purely through profit metrics ("diverse teams are 35% more profitable") risks instrumentalising marginalised employees. When the business case weakens, commitment evaporates. Frame the effort around fairness; the business benefits follow. + +**3. Fixing women instead of fixing systems.** Programmes that teach women to "lean in," negotiate harder, or be more assertive locate the problem in the individual rather than in the structures that penalise women for the very behaviours they are being coached to adopt. Always ask: "Is this a training problem or a system problem?" + +**4. One-size-fits-all DEI.** Generic initiatives that do not account for intersectionality -- the compounded disadvantages facing, say, Black women or disabled immigrants -- produce outcomes that benefit the least marginalised members of underrepresented groups while leaving others behind. + +**5. Assuming good intent is sufficient.** Second-generation bias operates without malicious intent. A leader who believes they treat everyone equally may still distribute opportunities unequally. The corrective is measurement, not introspection. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founding team composition | Every early hire sets a precedent; the first five people define who "belongs" | +| Early Traction | Hiring systems, language, job descriptions | Formalise inclusive hiring before informal networks calcify | +| Growth | Promotion pipelines, sponsorship, feedback systems | Middle management becomes the inclusion bottleneck; equip managers | +| Scale | Organisational audits, intersectional data, structural reform | Inclusion becomes a measurement and architecture problem | + +At validation, inclusion is a composition question. The founding team signals to every future hire who is welcome. A homogeneous founding team does not preclude diversity later, but it creates a gravitational pull toward sameness that requires deliberate counterforce. + +At growth, the critical failure point is middle management. Even if senior leadership is committed to inclusion, managers who have never examined their own feedback patterns, assignment decisions, or networking habits become inadvertent gatekeepers. Investing in manager capability -- not just awareness, but measurable behavioural change -- is the highest-leverage intervention at this stage. + +At scale, inclusion becomes an engineering problem. Anonymous escalation channels, pay-equity algorithms, demographic dashboards, and structured decision protocols replace the personal touch that worked in a 20-person company. + +--- + +## Output Template + +```markdown +# Inclusion Audit -- [Team / Department Name] + +**Date:** [Date] +**Auditor:** [Name] +**Team size:** [N] +**Demographic summary:** [High-level composition] + +## Four Freedoms Assessment + +| Freedom | Current State | Evidence | Gap | Action (30-day) | +|---------|--------------|----------|-----|-----------------| +| Authenticity | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Growth | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Respite | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | +| Failure | [Strong/Developing/Weak] | [Observations] | [Gap description] | [Specific action] | + +## Talent Lifecycle Equity Check + +| Stage | Data | Finding | Structural Fix | +|-------|------|---------|---------------| +| Applicant pool | [Data] | [Finding] | [Fix] | +| Hiring | [Data] | [Finding] | [Fix] | +| Onboarding | [Data] | [Finding] | [Fix] | +| Development | [Data] | [Finding] | [Fix] | +| Compensation | [Data] | [Finding] | [Fix] | +| Promotion | [Data] | [Finding] | [Fix] | +| Retention | [Data] | [Finding] | [Fix] | + +## Language Audit Summary +- Terms flagged: [List] +- Replacements recommended: [List] + +## Priority Actions (Next Quarter) +1. [Action with owner and deadline] +2. [Action with owner and deadline] +3. [Action with owner and deadline] +``` + +--- + +## Related Skills + +- **[Lean In](../../content/skills/frameworks/lean-in.md)** -- Provides the theoretical foundation on structural barriers facing women; this skill translates that theory into daily leadership behaviours. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Inclusion safety is the first of Clark's four stages; without it, none of the practices in this skill take root. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Inclusive behaviours are a subset of the broader culture a leader builds; this companion skill addresses the full spectrum of team dynamics. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Empathy and social awareness are the individual competencies that underpin inclusive leadership behaviours. +- **[AI Inclusive Collaboration](../../content/skills/ai-leadership/ai-inclusive-collaboration.md)** -- Applies inclusion principles specifically to AI adoption, ensuring diverse stakeholder perspectives shape technology deployment decisions. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Personal storytelling builds the empathy and cross-group connection that inclusive cultures depend on to bridge demographic divides. diff --git a/plugins/foreman/skills/influencing-and-persuading/SKILL.md b/plugins/foreman/skills/influencing-and-persuading/SKILL.md deleted file mode 120000 index 4ae1baa..0000000 --- a/plugins/foreman/skills/influencing-and-persuading/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/influencing-and-persuading.md \ No newline at end of file diff --git a/plugins/foreman/skills/influencing-and-persuading/SKILL.md b/plugins/foreman/skills/influencing-and-persuading/SKILL.md new file mode 100644 index 0000000..479bb86 --- /dev/null +++ b/plugins/foreman/skills/influencing-and-persuading/SKILL.md @@ -0,0 +1,259 @@ +--- +name: "influencing-and-persuading" +description: "Provides founders with Socratic influence techniques, confidence projection methods, and patience-based persuasion strategies for converting stakeholders without overt selling. Covers idea-seeding (making others believe your idea is theirs), the paradox of persuasion (listening as the primary influence tool), storytelling over selling, persistence mechanics, strategic asks, choosing happiness over rightness, managing up, authentic self-promotion, and time as a persuasion ally. Use when pitching investors, aligning cofounders on direction, winning a reluctant customer, navigating board resistance, asking for something audacious, or needing to influence without positional authority." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - persuasion + - influence + - socratic-method + - storytelling + - listening + - confidence + - persistence + - managing-up + - asking + - patience +related_skills: + - carnegie-win-friends + - cialdini-influence + - persuasion-and-influence + - trust-equation + - win-win-negotiation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Influencing and Persuading + +SHUT UP. The most powerful persuasion tool is not a pitch deck, not a compelling argument, not even a brilliant idea. It is silence. The discipline to close one's mouth, ask a question, and wait -- genuinely wait -- while the other person fills the void with their own reasoning, their own objections, and eventually their own path to the conclusion you wanted them to reach all along. A Radio Disney sales rep once closed the largest contract of his career without demoing the product. He asked questions for twenty-five minutes. The buyer interrupted him to say: "Let's get started. Just let me know how billing works." Almost nobody can do this. Founders, by temperament, are talkers -- passionate, enthusiastic, overflowing with conviction. That enthusiasm is both their greatest asset and their most reliable saboteur. + +Carnegie documented the principle in 1936. What follows is not a repetition of those timeless rules (see `carnegie-win-friends` for the canonical framework) but a complementary set of tactical behaviours -- specific, modern, and suited to the asymmetric power dynamics that founders navigate daily: pitching people with more money, persuading people with more authority, and influencing people who have no obligation to listen. + +--- + +## The Framework + +Influence, practised well, operates through ten interlocking techniques. They are not sequential steps but a repertoire -- deployed situationally, combined as context demands. + +### Technique 1: Socratic Idea-Seeding + +The most effective way to get someone to adopt your idea is to make them believe they invented it. The mechanism is straightforward: + +1. **Never say "I have an idea."** Remove the first-person pronoun from the equation entirely. +2. **Paint the broad strokes.** Describe the desired outcome or the problem's contours. Let the other person colour inside the lines. +3. **Alternatively, paint the negative.** Describe what happens if the idea is *not* adopted. The listener's mind will generate a solution to prevent that outcome -- your solution. +4. **Embrace instantly.** The moment the other person articulates anything resembling your idea, praise it as theirs. Enthusiastically. +5. **Refine gently.** If their version is not quite right, suggest additions to "their" idea, reinforcing ownership throughout. + +A shopping mall client rejected a founder's marketing concept outright on Monday. By Tuesday, the same client pitched the identical concept back -- with one minor addition -- as her own idea. The founder said, "Great idea." The campaign generated over a million dollars in earned media and won the agency its first award. The question of whose idea it was became irrelevant. + +### Technique 2: Passion Plus Persistence + +Passion is common. Persistence is rare. The gap between the two explains most of the variance in influence outcomes. + +One salesperson called a Burger King regional marketing manager thirty-seven times over eight weeks. Each weekly voicemail was a parody of a pop song. Call thirty-six would have been a failure. Call thirty-seven was a $50,000 contract and a relationship that lasted fourteen years. The operational rule: persist until certainty of futility, not until discomfort. + +| Element | What most people do | What persistence requires | +|---------|-------------------|--------------------------| +| Follow-up cadence | 2-3 attempts, then quit | Systematic attempts until definitive resolution | +| Creative variation | Same message, same channel | Different hooks, different formats, escalating creativity | +| Emotional management | Dejection after first rejection | Treat each "no" as incomplete data | +| Stopping criterion | "They haven't responded" | "They have explicitly and irrevocably declined" | + +### Technique 3: Storytelling Over Selling + +Nobody likes being sold to. Everybody likes a good story. This asymmetry is the storyteller's arbitrage. + +A founder spent Thanksgiving bidding $165 for a domain name while his turkey went cold. He told that story on his blog as the product launch strategy. The article generated 50,000 views and thousands of downloads -- far outperforming any advertisement. The product was a storytelling app. The medium was the message. + +The conversion: take any product, service, or idea you want to sell. Identify a personal story that embodies the problem it solves or the transformation it enables. Structure it with characters, tension, and resolution. Tell that story instead of listing features. The listener's mirror neurons do the rest. + +### Technique 4: The Paradox of Persuasion (Shut Up and Listen) + +Listening is more persuasive than talking for five specific reasons: + +1. It reveals the other person's goals, dreams, needs, and pain -- the raw material of influence. +2. It makes the other person feel heard, which generates appreciation, respect, and openness. +3. It provides thinking time. Humans listen three times faster than they speak; the surplus bandwidth is strategic planning space. +4. Combined with mirroring and validation, it creates emotional connection stronger than any pitch. +5. It increases the probability that the other person will articulate their own problem -- the problem you can solve. + +**The script:** Ask one good question. Wait. Ask a follow-up based on what you heard. Wait again. Repeat for twenty-five minutes. Then -- and only then -- share your solution, framed as a response to what they told you. + +### Technique 5: Confidence Projection (Walk With Confidence) + +A man once walked into the American Music Awards with an expired crew pass from the previous year. He made eye contact with the security guard, nodded, and walked straight in. He ended up in the sixth row. The ticket was worthless. The confidence was not. + +The principle is not deception. It is that self-assurance -- posture, eye contact, calm greeting -- functions as a social credential. The acronym WWC (Walk With Confidence) encodes the practice: enter every room, every meeting, every pitch as though you belong there. Not arrogance. Quiet certainty. + +Practical application: before entering any high-stakes room, set your posture, make deliberate eye contact with the first person you see, and greet them by name if possible. The physiological act of walking upright and making eye contact shifts both your internal state and others' perception. + +### Technique 6: Ask for What You Want + +A top-performing salesperson did everything right -- rapport, listening, mirroring, product demonstration -- except close. She never asked for the sale. Within six months of learning to ask, she doubled her earnings. + +The failure mode is universal: fear of "no" produces an implicit guarantee of "no." The corrective is blunt. + +- After rapport and demonstration, ask directly: "Shall we move forward?" +- After a great investor meeting, ask directly: "Can we count on your commitment?" +- After delivering value to a mentor, ask directly: "Would you be willing to introduce me to [specific person]?" + +No ask is too audacious. A couple sponsored their wedding through corporate partnerships -- 1-800-Flowers, Smirnoff, Entenmann's -- generating $100,000 in trade value, $20,000 for charity, and $20 million in earned media. They got all of it because they asked. + +### Technique 7: Choose Happiness Over Rightness + +A man convinced against his will is of the same opinion still. Arguing typically solidifies the other party's opposition. The alternative: state your case once, clearly. Then choose to be happy rather than right. Walk away. + +The paradox: people who stop arguing for their position often get what they wanted. By removing pressure, they create space for the other person to arrive at the same conclusion independently. A founder argued with his wife about firing a nanny. He stopped pressing. The next day, she witnessed the problem herself and made the same decision on her own. + +**The operational rule:** In any disagreement where the other party will not move, mirror their position, validate their feelings, state that you are choosing happiness, and disengage. Revisit only after they initiate. + +### Technique 8: Manage Up + +Managing up is not sycophancy. It is the disciplined practice of understanding what matters most to the person above you and delivering on those priorities visibly. + +The method: + +1. Identify the five things most important to your boss, investor, or board chair. If uncertain, ask their peers. +2. Ensure your daily work visibly addresses those priorities. +3. Ensure your manager's peers see you addressing those priorities. +4. After demonstrating alignment, ask for what you want -- a raise, a schedule change, additional resources. + +A sales rep chronically late to work discovered his manager's true concern was respect, not punctuality. He spent three weeks demonstrating respect conspicuously. Then he proposed a shifted schedule. The manager not only agreed but claimed the idea as his own (see Technique 1). + +### Technique 9: Beyond the Humblebrag + +Self-promotion is necessary; narcissism is fatal. The balance: + +- Share accomplishments authentically, without false modesty. +- Promote others at a ratio of at least 3:1 -- three public endorsements of others for every personal accomplishment shared. +- When someone calls you a braggart, the defence is not humility theatre. It is a track record of generously amplifying others. + +### Technique 10: Make Time Your Friend + +Time is a persuasion tool, not an obstacle. A founder who meets with every stranger who requests thirty minutes has a calendar that reflects other people's priorities, not his own. The "office hours" system -- two hours per week in fifteen-minute slots -- filters for genuine interest and protects the time that belongs to employees, investors, customers, and family. + +Patience in persuasion means accepting that some decisions take weeks. Some take months. Rushing a reluctant investor or cofounder produces resistance. Structured patience -- maintaining presence without pressure -- produces trust. + +--- + +## Prompts + +**Prompt 1 -- Socratic Idea-Seeding Script:** +> I need to persuade [stakeholder role] to adopt [specific idea]. They have rejected direct proposals before. Help me craft a Socratic approach: what broad-strokes vision or negative scenario can I paint so they arrive at my conclusion independently? Provide the exact language I should use, including what to say when they propose a version of my idea. + +**Prompt 2 -- Listening-Based Influence Preparation:** +> I have a [meeting type] with [stakeholder] in [timeframe]. My goal is to get them to [desired outcome]. Draft a sequence of five open-ended questions that will lead them to articulate the problem my solution addresses. Include guidance on when to stay silent and how long to wait after each question. + +**Prompt 3 -- The Ask Formulator:** +> I want to ask [person/organisation] for [specific request]. This feels audacious. Help me (a) reframe the ask as mutually beneficial, (b) craft the exact words, and (c) identify the worst realistic outcome of asking versus the certain outcome of not asking. + +**Prompt 4 -- Managing Up Audit:** +> My [boss/investor/board chair] has the following priorities: [list]. My current work focuses on [list]. Identify the gaps between their priorities and my visible output. Suggest three specific actions I can take this week to better align and demonstrate that alignment. + +--- + +## Use Cases + +**Seed-Stage Founder Pitching a Sceptical Angel Investor** + +A pre-revenue SaaS founder met an angel investor who had publicly stated she only invested in companies with $10K+ MRR. Rather than pitching the product, the founder asked: "What would a company in [vertical] need to demonstrate for you to believe it could reach $10K MRR within six months?" The investor described exactly the traction metrics the founder's product was designed to deliver. The founder then asked: "What if someone could show you those leading indicators today?" The investor requested a follow-up meeting. She invested three weeks later. + +**Growth-Stage CEO Managing a Difficult Board Member** + +A Series A CEO faced a board member who consistently derailed strategy discussions with operational minutiae. Rather than confronting the behaviour, the CEO identified that the board member's core concern was risk mitigation. Before each board meeting, the CEO began sending a one-page risk summary directly to that member, 48 hours in advance. The operational digressions stopped within two meetings. The CEO never mentioned the problem. + +**Early-Traction Startup Closing an Enterprise Customer** + +A three-person startup was pitching a Fortune 500 procurement team. Instead of a product demo, the founder spent the first meeting asking questions about the company's biggest workflow pain points. She listened for forty minutes, asked one clarifying question, and in the final five minutes said: "It sounds like [summary of their pain]. We built something that addresses exactly that. Can I show you next Tuesday?" The procurement team fast-tracked the evaluation. + +--- + +## Anti-Patterns + +**The Premature Pitch.** Launching into features and benefits before understanding the listener's needs. Listening for five minutes and then talking for twenty-five is not the paradox of persuasion -- it is a conventional sales call with a slow start. + +**Manipulation Masquerading as Socratic Influence.** Idea-seeding works when the idea genuinely serves both parties. Using the technique to get someone to "invent" an idea that primarily benefits you while harming them is not influence; it is manipulation, and it erodes trust catastrophically when discovered. + +**Confusing Persistence with Harassment.** Thirty-seven calls works when each contact adds creative value and respects boundaries. Thirty-seven identical "just checking in" emails is not persistence; it is spam. The distinction: does each attempt offer something new, or does it merely repeat the demand? + +**Choosing Happiness as Avoidance.** "I choose to be happy" is a strategic withdrawal, not a permanent retreat. The technique requires you to state your position clearly first. Skipping the position-statement and jumping directly to disengagement is conflict avoidance, which produces resentment rather than resolution. + +**Managing Up Without Delivering Down.** Visible alignment with your manager's priorities means nothing if your team sees you neglecting their needs. Managing up is additive to competence, not a substitute for it. + +--- + +## By Stage + +| Stage | Primary Influence Target | Key Technique | +|-------|------------------------|---------------| +| Idea | Potential cofounders, early believers | Socratic idea-seeding; confidence projection when you have nothing tangible to show | +| Validation | Pilot customers, advisors | Listening-based influence; storytelling over selling when the product is immature | +| Early Traction | Lead customers, seed investors | The direct ask; persistence with creative variation | +| Growth | Board members, enterprise buyers, key hires | Managing up; choosing happiness over rightness in high-stakes disagreements | +| Scale | Executive team, institutional investors, partners | Time management as influence tool; authentic self-promotion at scale | + +At the idea stage, the founder's primary asset is conviction, and the primary risk is over-talking. Socratic seeding and confidence projection matter most because there is no product to demonstrate. At scale, the founder's calendar is the battleground -- how time is allocated signals priorities more loudly than any speech. + +--- + +## Output Template + +```markdown +# Influence Strategy Brief + +**Target:** [Name/Role of person to influence] +**Desired Outcome:** [Specific decision or action sought] +**Relationship Context:** [History, power dynamic, known concerns] + +## Pre-Meeting Intelligence +- Their top 3 priorities: [list] +- Their known objections or concerns: [list] +- What they value hearing from others: [data / stories / peer endorsement / vision] + +## Technique Selection +- [ ] Socratic idea-seeding (they need to feel ownership) +- [ ] Listening-first (their needs are unclear or unexpressed) +- [ ] Direct ask (relationship is strong, ask is clear) +- [ ] Storytelling (they respond to narrative over data) +- [ ] Managing up (ongoing relationship, need alignment) +- [ ] Patience play (timing is not right; maintain presence) + +## Prepared Questions (if listening-first) +1. [Open-ended question about their situation] +2. [Follow-up probing their pain point] +3. [Question connecting their pain to your solution] + +## The Ask (exact words) +> "[Precise language for the request]" + +## If They Say No +- Reframe: [alternative framing] +- Persistence plan: [next creative touchpoint and timing] +- Strategic withdrawal: [when to choose happiness and revisit later] + +## Follow-Up +- Thank-you method: [handwritten card / thoughtful gift / introduction] +- Timeline for next contact: [date] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends and Influence People](../../content/skills/frameworks/carnegie-win-friends.md)** -- The 1936 foundational principles that underpin Socratic influence and listening-based persuasion; this skill provides the modern tactical application. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Seven psychological principles of persuasion as academic framework; this skill translates influence into behavioural scripts for entrepreneurial contexts. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- Daily micro-influence tactics for leaders in meetings and one-on-ones, complementary but focused on organisational dynamics. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the precondition for all influence; this framework quantifies its components. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- When influence conversations become formal negotiations, principled negotiation provides the structural framework. +- **[Reading People](../../content/skills/people/reading-people.md)** -- The nonverbal signal detection and mirroring techniques provide the real-time feedback that effective influence requires to calibrate approach mid-conversation. diff --git a/plugins/foreman/skills/information-asymmetry/SKILL.md b/plugins/foreman/skills/information-asymmetry/SKILL.md deleted file mode 120000 index 390de93..0000000 --- a/plugins/foreman/skills/information-asymmetry/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/information-asymmetry.md \ No newline at end of file diff --git a/plugins/foreman/skills/information-asymmetry/SKILL.md b/plugins/foreman/skills/information-asymmetry/SKILL.md new file mode 100644 index 0000000..c6de517 --- /dev/null +++ b/plugins/foreman/skills/information-asymmetry/SKILL.md @@ -0,0 +1,261 @@ +--- +name: "information-asymmetry" +description: "Applies game theory concepts of asymmetric information to entrepreneurial decisions: the free rider problem in teams, adverse selection (Akerlof's lemons market), moral hazard in principal-agent relationships, and separating equilibrium as a solution mechanism. Use when diagnosing hiring failures, fundraising challenges, quality signaling problems, partnership trust issues, team incentive misalignment, or any situation where one party holds materially more information than the other." +version: "1.0.0" +category: "game-theory" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - information-asymmetry + - adverse-selection + - moral-hazard + - free-rider + - signaling + - screening + - lemons-market + - incentive-design +related_skills: + - game-theory-fundamentals + - prisoners-dilemma-and-cooperation + - first-mover-strategy + - trust-equation + - emotional-intelligence + - delegation-and-empowerment + - employee-engagement-retention +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Information Asymmetry + +LEMON MARKET. In 1970, George Akerlof published a thirteen-page paper explaining why good used cars are almost impossible to sell at a fair price. The buyers cannot tell a reliable car from a wreck, so they offer the average price. Sellers of reliable cars find this insulting and withdraw. The average quality drops. Buyers adjust downward. More good sellers leave. The cycle continues until the market contains only lemons and the buyers who deserve them. Akerlof won the Nobel Prize for this observation, and it explains approximately half of every startup's commercial frustrations: why enterprise buyers default to incumbent vendors, why the best candidates reject lowball offers, why investors demand punitive terms, and why quality products lose to inferior competitors with louder marketing. The problem is never the product. The problem is that the other side cannot verify the product's quality -- and in the absence of verification, rational actors assume the worst. + +--- + +## The Framework + +### The Free Rider Problem: When Contribution Cannot Be Observed + +A free rider enjoys the output of collective effort without contributing proportionally. The game-theoretic structure is precise: when individual contributions are unobservable or unmeasurable, the rational strategy for each participant is to minimize effort while consuming the group's output. + +**The Boxed Pigs Game -- A Parable for Startup Teams** + +Consider a startup with two cofounders of different capabilities. A large task (pressing the switch) must be done for both to benefit. The senior cofounder (the "big pig") invests significant effort; the junior cofounder (the "small pig") waits. + +| | Junior Cofounder: Contributes | Junior Cofounder: Waits | +|--|------------------------------|------------------------| +| **Senior Cofounder: Contributes** | Senior gets 7, Junior gets 3 | Senior gets 6, Junior gets 4 | +| **Senior Cofounder: Waits** | Senior gets 10, Junior gets 0 | Both get 0 | + +The equilibrium: the senior cofounder contributes (because waiting means nothing happens), while the junior cofounder waits (because contributing yields less than waiting). The small player free-rides on the large player's effort -- not from malice, but from rational calculation. + +This dynamic recurs wherever contribution is unobservable: in engineering teams where individual output is hard to measure, in partnerships where one partner's network generates most of the deal flow, in open-source projects where large companies benefit from volunteer labor. Equal compensation in the presence of unequal effort is not a cultural problem. It is a game-theoretic certainty. + +**Solutions to the Free Rider Problem:** + +- **Performance-linked compensation.** Tie rewards to observable individual output, not group output. Equity vesting tied to milestones. Sales commissions. Engineering metrics (deployed features, not lines of code). +- **Small teams.** Free riding worsens as team size increases, because each individual's contribution becomes less visible. Amazon's "two-pizza team" rule is, whether intentionally or not, a game-theoretic intervention. +- **Transparency mechanisms.** Make contributions visible. Stand-ups, public dashboards, peer reviews, and open calendars all reduce the information asymmetry that enables free riding. + +### Adverse Selection: The Lemons Market + +Adverse selection occurs before a transaction is completed. When one party has private information about quality, and the other party cannot observe that quality, the market selects for low quality. + +**The Akerlof Mechanism, Applied to Startups:** + +Consider a market for enterprise software. Some products are genuinely excellent (worth $100K/year). Others are mediocre (worth $20K/year). The buyer cannot distinguish them before purchasing. + +| Step | What Happens | Market Effect | +|------|-------------|---------------| +| 1 | Buyers know average quality exists but cannot evaluate individual products | They offer the average price: $60K | +| 2 | Sellers of excellent products find $60K unacceptable | They leave the market or reduce investment in quality | +| 3 | Average quality drops (mostly mediocre products remain) | Buyers adjust expected value downward: $40K | +| 4 | More quality sellers exit | Market converges toward lemons | +| 5 | Equilibrium: low prices, low quality, low trust | Everyone loses -- especially the good products | + +This is adverse selection. The market selects adversely against quality because quality is unobservable. The mechanism explains a wide range of entrepreneurial difficulties: + +- **Hiring:** The best candidates have the most options and are least willing to accept generic offers. Standardized compensation attracts average talent and repels exceptional talent. +- **Fundraising:** Founders know their company's true potential; investors do not. Investors set terms that protect against the worst case (heavy liquidation preferences, anti-dilution), which rational founders of genuinely strong companies resist. The terms that close deals select for founders who are desperate or naive. +- **B2B sales:** Enterprise buyers cannot evaluate software quality before purchase. They default to recognized brands (IBM, Salesforce, Microsoft) not because those products are superior, but because the brand serves as a quality signal that reduces adverse selection risk. The phrase "nobody ever got fired for buying IBM" is an adverse selection survival strategy. + +### Solving Adverse Selection: Signaling and Screening + +Two mechanisms counteract adverse selection by reducing information asymmetry: + +**Signaling (Seller-Initiated).** The informed party takes a costly, observable action that credibly communicates quality. The cost is critical: the signal must be expensive enough that low-quality actors cannot afford to fake it. + +| Signal | Why It Works | Startup Application | +|--------|-------------|---------------------| +| Money-back guarantees | Only confident sellers offer them; lemons would lose money | Offering a 90-day full refund signals product quality | +| Prestigious investor names | Top-tier VCs screen heavily; their investment signals quality | Raising from Sequoia or a16z communicates more than the capital itself | +| Free trial / freemium | Quality products convert; poor products do not | The product speaks for itself before the buyer commits | +| Certifications and audits | Third-party verification is costly to obtain and hard to fake | SOC 2, ISO 27001, and security audits signal operational maturity | +| Transparency (open metrics) | Only companies with strong metrics would share them | Publishing NPS scores, churn rates, or uptime publicly | + +Michael Spence's signaling theory, which earned him a share of the 2001 Nobel Prize alongside Akerlof, established a key principle: education functions primarily as a signal in labor markets. A degree from a top university may not teach relevant skills, but it signals that the holder was capable of obtaining admission and completing the program -- a costly action that lower-ability candidates find prohibitively difficult. The same logic applies to any costly, observable, quality-correlated action. + +**Screening (Buyer-Initiated).** The uninformed party designs a choice architecture that causes the informed party to self-select, revealing their private information through their choices. + +| Screening Mechanism | How It Reveals Information | Business Application | +|--------------------|--------------------------|---------------------| +| Tiered pricing | Price-sensitive and premium buyers self-sort | SaaS tiers reveal willingness to pay and likely usage | +| Deductible options | Risk-tolerant and risk-averse customers self-sort | Insurance-style contracts with different risk-sharing splits | +| Vesting schedules | Committed founders stay; uncommitted ones leave | 4-year vesting reveals true long-term commitment | +| Trial projects | Capable vendors deliver; incapable ones fail | Paid pilot engagements screen vendor quality | +| Application complexity | Serious candidates complete the process; casual ones drop off | Detailed job applications and multi-stage interviews | + +### Separating Equilibrium: Designing Self-Sorting Mechanisms + +A separating equilibrium is the game-theoretic ideal: a market design where high-quality and low-quality actors voluntarily sort themselves into different visible categories, eliminating information asymmetry. + +The classic example is airline pricing. Business travelers (high willingness to pay, low price sensitivity) and leisure travelers (low willingness to pay, high price sensitivity) have different private information about their own value. Airlines create a separating equilibrium by offering two products: expensive flexible tickets and cheap restricted tickets. Business travelers self-select into the premium tier; leisure travelers self-select into the economy tier. The airline extracts maximum value from each segment without needing to identify individual customers. + +For entrepreneurs, the design principle is: create choice structures where different customer types, employee types, or partner types reveal their private information through the option they choose. Tiered pricing is the most common example, but the principle extends to hiring (compensation packages with different equity/salary ratios), fundraising (term sheet structures that attract different investor types), and partnerships (commitment levels that filter serious from speculative partners). + +### Moral Hazard: When Behavior Changes After the Deal + +Moral hazard occurs after a transaction is completed. Once one party bears a risk or cost on behalf of another, the second party's incentive to behave responsibly diminishes. + +The structure is a principal-agent problem: the principal (investor, employer, insurer) cannot perfectly observe the agent's (founder, employee, policyholder) behavior after the agreement is signed. + +**Moral Hazard in Startup Context:** + +| Relationship | Principal | Agent | Moral Hazard Risk | +|-------------|-----------|-------|------------------| +| Investor-Founder | Investor | Founder | Founder takes excessive risk with investor capital (upside captured by founder, downside borne by investor) | +| Founder-Employee | Founder | Employee | Employee reduces effort after equity grant vests or after receiving a raise | +| Client-Agency | Client | Marketing agency | Agency prioritizes billable hours over results | +| Insurer-Insured | Startup insurance provider | Startup | Startup takes less care with insured assets | + +**Solutions to Moral Hazard:** + +1. **Incentive alignment.** Structure compensation so the agent's interests mirror the principal's. Equity with performance vesting. Revenue-share contracts. Clawback provisions. The economist Hurwicz formalized this as the "incentive compatibility principle": design contracts so that the agent maximizes their own payoff by taking the action the principal wants. + +2. **Monitoring and transparency.** Board seats, reporting requirements, regular audits, and OKR reviews all reduce information asymmetry post-agreement. The cost of monitoring must be weighed against the cost of moral hazard it prevents. + +3. **Reputation in repeated games.** When the relationship is ongoing, the agent's future access to opportunities depends on current performance. This is why repeat founders raise capital more easily and on better terms -- their reputation serves as a credible bond against moral hazard. + +--- + +## Prompts + +**Prompt 1 -- Diagnose Information Asymmetry in Your Sales Process:** +> My company sells [describe product/service] to [describe buyer]. Our close rate is [X%], which is lower than expected given our product quality. Help me analyze this as an adverse selection problem. Where is the information asymmetry? What does the buyer not know that, if they knew it, would change their purchase decision? Then design a signaling strategy: what costly, credible signals can we send to differentiate our quality from competitors? Evaluate at least five potential signals (guarantees, trials, certifications, transparency, endorsements) and recommend the most effective ones for our situation. + +**Prompt 2 -- Design a Screening Mechanism for Hiring:** +> I need to hire [describe role] and I am concerned about adverse selection -- attracting candidates who interview well but underperform. Help me design a screening mechanism that causes candidates to self-sort by quality. Consider: compensation structure (salary vs. equity mix), application process design, trial periods, and reference check depth. For each mechanism, explain what information it reveals and what type of candidate it selects for or against. + +**Prompt 3 -- Assess Moral Hazard in a Partnership:** +> I am entering a [describe partnership/agreement: investment, outsourcing contract, cofounder arrangement, distribution deal]. Help me identify the moral hazard risks -- how might the other party's behavior change after the agreement is signed, given that I cannot perfectly observe their actions? Then design contractual and structural safeguards: what incentive alignment mechanisms, monitoring structures, and reputation consequences should be built into the agreement? + +**Prompt 4 -- Build a Separating Equilibrium for Your Market:** +> My market has both high-value and low-value [customers/vendors/partners], and I cannot easily tell them apart before committing resources. Help me design a separating equilibrium -- a choice architecture that causes the two types to self-sort. Consider tiered offerings, commitment requirements, pricing structures, and application processes. For each design, explain which type selects into which option and why. + +--- + +## Use Cases + +**Validation-Stage Marketplace Struggling with Supply Quality** + +A freelancer marketplace connects businesses with independent consultants. The platform faces severe adverse selection: businesses cannot evaluate consultant quality before hiring, so they gravitate toward the cheapest option. High-quality consultants, unable to charge premium rates on a platform that commoditizes their expertise, leave for direct client relationships. The founder diagnoses this as a lemons market and implements three interventions. First, a portfolio review and skills assessment that produces a visible quality score (signaling mechanism). Second, tiered pricing where consultants choose their own rate band, with the platform displaying the tier prominently (screening mechanism that creates separating equilibrium -- top consultants self-select into premium tiers). Third, outcome-based reviews weighted by project complexity, not just star ratings (reducing noise in the quality signal). Within two quarters, average project value increases by 60% and high-quality consultant retention improves from 40% to 72%. + +**Growth-Stage Enterprise SaaS Battling Incumbent Preference** + +A growth-stage cybersecurity startup with a technically superior product consistently loses enterprise deals to an established competitor whose product is widely acknowledged within the industry to be inferior. The founder recognizes this as an adverse selection problem: the CISO cannot verify the startup's quality claims, so they default to the known brand to minimize career risk. The startup constructs a signaling strategy with three layers. First, an independent security audit by a recognized firm, published publicly (costly third-party verification). Second, a "deploy or don't pay" trial -- the customer runs both products in parallel for 90 days and pays only if the startup's product outperforms (a guarantee only a genuinely superior product can sustain). Third, case studies with named enterprise customers who agreed to be referenced (social proof as costly signal -- customers stake their own reputation). The multi-layered signaling approach overcomes the adverse selection barrier, and win rates against the incumbent improve from 15% to 45% over six months. + +**Scale-Stage Company Designing Investor-Founder Alignment** + +A Series B company restructures its board governance to address moral hazard from both directions. The investors face moral hazard risk that the founder will pursue vanity projects with their capital. The founder faces moral hazard risk that the investors will force a premature exit to optimize their fund timeline. The CFO, trained in game-theoretic incentive design, proposes a symmetric alignment structure: milestone-based capital tranches (reducing investor exposure to founder moral hazard), combined with a founder-controlled board seat and anti-forced-sale provisions (reducing founder exposure to investor moral hazard). Both parties bear monitoring costs proportional to the risk they face. The structure creates incentive compatibility: the founder maximizes their payoff by hitting milestones (which is what investors want), while the investors maximize their payoff by supporting long-term value creation (which is what the founder wants). + +--- + +## Anti-Patterns + +1. **Assuming more information always helps.** Information has costs: acquisition cost, processing cost, and decision latency. Seeking perfect information before every hire, deal, or partnership is a form of analysis paralysis dressed in game-theoretic clothing. The goal is to reduce information asymmetry to the point where adverse selection no longer distorts the decision -- not to eliminate asymmetry entirely, which is usually impossible and always expensive. + +2. **Signaling without substance.** A signal works only if it is correlated with actual quality and costly enough to be difficult for low-quality actors to fake. Press releases, vanity metrics, and logo walls are cheap signals that sophisticated counterparties discount heavily. A money-back guarantee from a company that cannot afford to honor it is a bluff, not a signal. The cost must be real. + +3. **Designing screening mechanisms that select for the wrong traits.** Multi-stage interview processes that last six weeks screen for candidates who have six weeks to spare -- which may select against the best candidates, who have competing offers with deadlines. Every screening mechanism selects for something; the question is whether it selects for the trait that actually predicts performance. + +4. **Ignoring moral hazard in your own behavior.** Founders analyze investor moral hazard and employee moral hazard but rarely examine their own. Once funded, founders face reduced personal downside (the investors' money, not theirs) and increased optionality (pivot, extend runway, take a high salary). Recognizing moral hazard in yourself is the precondition for designing governance structures that keep all parties honest, including you. + +5. **Treating all information problems as adverse selection.** Adverse selection is a pre-transaction problem (the wrong types enter the market). Moral hazard is a post-transaction problem (behavior changes after the deal). The solutions are different. Signaling and screening address adverse selection. Incentive alignment and monitoring address moral hazard. Applying the wrong solution to the wrong problem is common and ineffective. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Overcoming adverse selection as the unknown entrant | At validation stage, the startup is the lemon until proven otherwise. Every buyer, partner, and hire applies an adverse selection discount. The primary task is constructing credible signals -- early customers, respected advisors, working demos -- that separate the startup from vaporware. | +| Early Traction | Building signaling infrastructure | With initial traction, the startup can invest in durable signals: customer case studies, third-party audits, public metrics dashboards. The cost of these signals is justified because they compound -- each new signal reduces the adverse selection discount permanently. | +| Growth | Managing moral hazard across the organization | As headcount grows, moral hazard scales. Each new hire, vendor, and partner introduces a principal-agent relationship with monitoring costs. Incentive design (compensation structures, vesting schedules, performance systems) becomes a core organizational capability, not an HR afterthought. | +| Scale | Designing market-level separating equilibria | At scale, the company can shape market structures that create separating equilibria: tiered products, certification programs, partner tiers, and quality standards that cause participants to self-sort by capability. This is market design, not just company strategy. | + +--- + +## Output Template + +```markdown +# Information Asymmetry Analysis + +**Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Asymmetry Map + +| Relationship | Who Knows More | What They Know | Consequence If Unaddressed | +|-------------|---------------|---------------|--------------------------| +| [Relationship 1] | [Party] | [Private information] | [Adverse selection / Moral hazard risk] | +| [Relationship 2] | [Party] | [Private information] | [Adverse selection / Moral hazard risk] | + +## Pre-Transaction Risk (Adverse Selection) + +- **Where is adverse selection occurring?** [Description] +- **What quality signal is missing?** [Description] +- **Current cost of adverse selection:** [Quantified if possible -- lost deals, talent flight, pricing compression] + +## Signaling Strategy + +| Signal | Cost to Implement | Credibility Level | Expected Impact | +|--------|------------------|------------------|----------------| +| [Signal 1] | [Cost] | [High/Medium/Low] | [Impact] | +| [Signal 2] | [Cost] | [High/Medium/Low] | [Impact] | + +## Screening Mechanism Design + +| Mechanism | What It Reveals | Who It Selects For | Who It Selects Against | +|-----------|----------------|-------------------|----------------------| +| [Mechanism 1] | [Information] | [Type] | [Type] | +| [Mechanism 2] | [Information] | [Type] | [Type] | + +## Post-Transaction Risk (Moral Hazard) + +- **Principal-agent relationships at risk:** [List] +- **Monitoring mechanisms in place:** [List] +- **Incentive alignment gaps:** [List] + +## Recommended Actions +1. [Highest-priority signaling investment] +2. [Screening mechanism to implement] +3. [Moral hazard safeguard to establish] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](../../content/skills/game-theory/game-theory-fundamentals.md)** -- Provides the foundational concepts (players, strategies, payoffs, equilibrium) that underpin information asymmetry analysis. +- **[Prisoner's Dilemma and Cooperation](../../content/skills/game-theory/prisoners-dilemma-and-cooperation.md)** -- Information asymmetry makes cooperation harder: when you cannot observe whether the other party is cooperating or defecting, the dilemma deepens. +- **[First-Mover Strategy](../../content/skills/game-theory/first-mover-strategy.md)** -- Information asymmetry often determines whether the first or second mover has the advantage; the party with more information can time moves more effectively. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the behavioural antidote to information asymmetry; the trust equation identifies the specific components that reduce the information gap in relationships. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Every act of delegation creates a principal-agent relationship with moral hazard risk; effective delegation requires the incentive alignment mechanisms analysed here. +- **[Negotiation Mindset and Self-Management](../../content/skills/negotiation/negotiation-mindset-and-self.md)** -- The assumption audit in negotiation preparation is fundamentally an information asymmetry assessment: what do I know, what do they know, and where are the gaps? diff --git a/plugins/foreman/skills/inspiring-and-retaining/SKILL.md b/plugins/foreman/skills/inspiring-and-retaining/SKILL.md deleted file mode 120000 index 3dbe5cd..0000000 --- a/plugins/foreman/skills/inspiring-and-retaining/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/inspiring-and-retaining.md \ No newline at end of file diff --git a/plugins/foreman/skills/inspiring-and-retaining/SKILL.md b/plugins/foreman/skills/inspiring-and-retaining/SKILL.md new file mode 100644 index 0000000..d1e38bb --- /dev/null +++ b/plugins/foreman/skills/inspiring-and-retaining/SKILL.md @@ -0,0 +1,289 @@ +--- +name: "inspiring-and-retaining" +description: "Equips founders with practical retention and inspiration techniques grounded in selfless leadership, strategic kindness, and relationship maintenance at scale. Covers making it about the audience (not you), the random-act-of-kindness mood reset, the homelessness perspective technique, praise-to-criticism ratios, surprise-and-delight as a variable reward system, handwritten thank-you cards as strategic instruments, daily introductions as network compounding, personalised gift-giving for investor and client retention, and content curation for staying top of mind. Use when team morale is declining, investor relationships need warming, key employees are at flight risk, preparing an inspiring presentation, or building a personal brand that sustains professional relationships at scale." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - inspiration + - retention + - gratitude + - thank-you-cards + - praise + - networking + - personal-brand + - surprise-and-delight + - introductions + - gifts +related_skills: + - employee-engagement-retention + - carnegie-win-friends + - teaching-and-leading + - influencing-and-persuading + - trust-equation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Inspiring and Retaining + +THANK YOU CARD. In an age of unlimited text messages, instant emails, and algorithmic social feeds, a handwritten thank-you card is a strategic weapon -- and almost nobody deploys it. A study by DonorsChoose found that first-time donors who received a handwritten thank-you note were 38 percent more likely to donate again, and gave more when they did. The CEO of a multibillion-dollar property-restoration company writes handwritten birthday and thank-you cards to employees every single day. His handwriting is barely legible. The cards are priceless. + +The reason is scarcity. An email costs nothing to send and almost nothing to receive. A handwritten card requires purchasing stationery, finding a pen, composing a thought in ink that cannot be deleted, sealing an envelope, and delivering it by hand or post. Each step signals: this person matters enough that I spent irreplaceable time on them. In an economy where attention is the scarcest resource, a three-minute handwritten note outperforms a three-paragraph email by an order of magnitude. + +What follows is a collection of nine retention and inspiration practices -- each specific, each deployable this week, and each designed to compound over months and years into the kind of loyalty that no compensation package can purchase. + +--- + +## The Framework + +### Practice 1: It Is Not About You + +A speaker was about to address three thousand entrepreneurs in Mexico City. Stage fright had replaced his usual excitement. A fellow speaker approached and said: "Remember -- it's all about them, not you. Inspiring your audience is about helping them see their own vision, not yours." + +The principle applies universally. People do not care about you, your product, or your company -- they care about how those things affect their own lives, businesses, and futures. Every presentation, every pitch, every one-on-one should be structured around the audience's self-interest: + +- **Sales presentation:** slides should visualise the customer's life *without* the problem, not the product's feature set. +- **Team all-hands:** the vision should describe what success looks like *for the team members*, not for the company's valuation. +- **Investor update:** frame progress in terms of the investor's thesis and return expectations, not your operational pride. + +The trap is subtle because founders are trained to tell their story. Stories are useful -- but only as delivery vehicles for the audience's own aspirations. The question before every presentation: "What does my audience want their future to look like, and how does what I am sharing help them get there?" + +### Practice 2: The Homelessness Perspective Reset + +A founder was having the worst day of a bad week -- a toxic employee fired, four cities in four days, physically exhausted, emotionally depleted. He walked a mile to his favourite sushi restaurant. It was closed for renovations. He cried on the street. + +Then a homeless man asked for a quarter. The founder gave him twenty dollars. The mood transformation was instant: from depressed, overwhelmed, and stressed to blessed, fortunate, and energised. The cost of the intervention was $20 and forty-five seconds. + +A random act of kindness is an on-demand mood reset. The mechanism is dual: it forces attention outward (away from self-focused rumination) and triggers the neurochemistry of generosity (dopamine, serotonin, oxytocin). The reset need not cost money: + +- Hold the door for ten consecutive people. +- Send a compliment to a colleague who is not expecting one. +- Call a grandparent. +- Retweet someone trying to promote something who has no audience. + +The leadership application: before any high-stakes meeting where your mood is compromised, perform one act of kindness. The mood shift is real, transfers through mirror neurons (see `teaching-and-leading`), and costs less than a bad meeting. + +### Practice 3: Praise Lavishly, Criticise Privately + +A CEO publicly called his top salesperson lazy. The word was barely out of his mouth before he realised the error. Despite private apologies and a history of two years of generous praise, the salesperson's performance spiralled. He eventually left the company. + +The asymmetry between praise and criticism is stark: + +| Dimension | Praise | Criticism | +|-----------|--------|-----------| +| Best delivery context | Public | Private -- always | +| Effect on recipient | Pride, motivation, loyalty | Embarrassment, fear, resentment | +| Effect on bystanders | Aspiration ("I want that recognition") | Fear ("I could be next") | +| Duration of impact | Moderate; needs regular renewal | Long; a single incident can override years of praise | +| ROI | Infinite -- praise is free | Negative if delivered publicly | + +**The praise-sandwich protocol for necessary criticism:** + +1. Open with a specific, genuine positive observation. +2. Deliver the constructive feedback. +3. Close by affirming the person's value and expressing confidence in them. +4. Always in private. Never in front of peers. Never in Slack channels. + +A teacher in a classroom of at-risk students stopped reprimanding disruptive children and instead publicly praised the one student following directions: "I like the way Sammy is sitting at his desk ready to learn." The other students corrected their behaviour without being told. Years later, Sammy found his former teacher on Facebook to say that praise had inspired him to finish high school and start college. + +### Practice 4: Make It a Honey Day (Surprise and Delight) + +A director of talent at a company named to Crain's best-places-to-work list three consecutive years decided to create a holiday -- not for a top performer, not for a manager, but for a solid, consistent employee named Honey. Ribbons, balloons, cake, and a company-wide announcement: "Today is Honey Day." + +The psychology is borrowed from casinos. Slot machines produce variable rewards -- unpredictable payoffs at random intervals. The sounds of winning that greet every visitor to a casino floor are not accidental; they signal that *someone* is winning right now, and *you* could be next. Surprise-and-delight programs for employees use the same principle: + +- Recognise people at random, not just top performers. +- Keep the timing unpredictable. Scheduled recognition becomes expected; unexpected recognition becomes memorable. +- Scale varies: a named holiday is spectacular; an unexpected afternoon off or a handwritten note is equally effective. + +The retention effect: Honey is still at the company over a year later. The question "Would you leave a company that created a holiday in your honour?" answers itself. + +### Practice 5: Handwritten Thank-You Cards + +The protocol, refined over years of practice: + +1. **Week 1:** One card per week, on a designated day. +2. **Weeks 2-3:** One card per day. +3. **Week 4 onward:** Three cards per day, written during transition time -- commute, between meetings, first thing in the morning. + +Recipients include employees, customers, investors, partners, advisors, friends, and family. The cards need not be eloquent. Legibility is optional (the multibillion-dollar CEO's handwriting was barely readable). What matters is specificity: "Thank you for [specific thing you did]. It made [specific impact]." + +The dual return on investment: recipients are measurably more loyal (38% repeat donation rate for thanked donors vs. unthanked), and the writer experiences an immediate mood elevation from the act of expressing gratitude. Three cards per morning is a daily pre-meeting mood enhancer that costs less than a cup of coffee. + +### Practice 6: One Introduction Per Day + +Adam Rifkin has made over ten thousand introductions on LinkedIn since 2003 -- three per day, every day. Those introductions have produced two marriages, hundreds of jobs, dozens of funded companies, and at least twelve business partnerships. Rifkin is a shy introvert. + +An introduction accomplishes two things simultaneously: it endorses both parties and provides a reason to connect. The mechanism is Adam Grant's "five-minute favour" -- a small investment of time that produces outsized goodwill. + +**The daily introduction system:** + +1. Mark 50 people as "close friends" on social media and enable notifications for their updates. +2. When an update triggers a connection -- "Dave is working on a people-skills project; Adam is a master of people skills" -- make the introduction. +3. Use a concise template: names, why they remind you of each other, and a suggestion to connect. +4. Start with one per day. Build to three. + +The compounding effect: introductions keep you top of mind with both parties. Over a year, 365 introductions create 730 moments of goodwill attributed to you. Over a decade, the network effects are exponential. + +### Practice 7: The Personalised Gift (Buy Him a Bonsai) + +A startup founder sent a $35 bonsai tree to a venture capitalist who had rejected his investment pitch. The accompanying note: "Here's to your growth, our growth, and the growth of this bonsai." The VC responded with an introduction to another investor who eventually wrote a check. + +The personalised gift operates in the gap between a thank-you card (free, personal) and a lavish present (expensive, potentially awkward). The criteria: + +- **Thoughtful:** connected to the recipient's interests or the context of the relationship. +- **Affordable:** $20-50 is the sweet spot. Expensive gifts create obligation; inexpensive-but-clever gifts create warmth. +- **Unexpected:** the element of surprise is the multiplier. +- **Durable:** a gift that sits on someone's desk for months provides ongoing mental presence. + +Beyond bonsais, effective options include: books relevant to a conversation you had, personalised trophies for tongue-in-cheek achievements, mini herb gardens, and even a toy moat (sent to an investor who said the company needed a better moat). The operating principle is that in a world where most follow-ups are emails, a physical object occupies mental real estate that no digital message can claim. + +### Practice 8: Never Let One Unkind Word Destroy Years of Praise + +This is the defensive complement to Practice 3. The founder who publicly called his star employee lazy did not just damage one moment -- he invalidated two years of accumulated praise. The employee heard only the criticism, because criticism is neurologically stickier than praise. A single public rebuke can undo months of carefully built trust. + +The preventive discipline: before saying anything critical, pause and ask three questions. + +1. Am I about to say this in front of other people? (If yes, stop.) +2. Have I set up a private, structured conversation for this feedback? (If no, schedule one.) +3. Will this criticism help the person improve, or am I venting frustration? (If venting, walk away and return when the purpose is constructive.) + +### Practice 9: Stay Top of Mind at Scale + +A founder with more LinkedIn page views than Bill Gates, Jack Welch, and Mark Cuban combined achieved it not through celebrity or wealth but through consistent content curation. The formula is EEI: Entertain, Educate, Inspire. + +The practical system: + +1. Spend thirty minutes per week finding EEI content: articles, videos, infographics, quotes. +2. Schedule content across LinkedIn and Twitter using free scheduling tools. +3. For the five most important people in your network, send relevant content privately via text or direct message -- not as a public post, but as a personal recommendation. +4. Share others' accomplishments at a 3:1 ratio to your own. + +Content curation keeps you at the top of news feeds and therefore at the top of minds. The recipient who sees your name daily attributing interesting content to you is a recipient who thinks of you first when an opportunity arises. A Shark Tank star shared her cell phone number after receiving a single private message offering to help promote her book. A year later, she was there when the favour was needed. They have still never met in person. + +--- + +## Prompts + +**Prompt 1 -- Thank-You Card System Design:** +> I want to start a daily handwritten thank-you card practice. I have [number] employees, [number] key clients, [number] investors, and [number] advisors. Design a 30-day ramp-up plan: who should receive cards in what order, what should each card say (give me three templates varying in specificity), and how should I schedule the writing into my existing routine? + +**Prompt 2 -- Audience-Centred Presentation Rewrite:** +> Here is the outline for my upcoming [presentation type] to [audience]. Rewrite it so that every section is framed around the audience's self-interest rather than my company's achievements. Show me the before-and-after for each section. + +**Prompt 3 -- Surprise-and-Delight Programme:** +> My company has [number] employees. Design a 90-day surprise-and-delight programme using variable reward principles: what types of recognition, at what frequency, for which selection criteria (random vs. merit-based vs. value-aligned), and with what budget per event? Include at least one zero-cost option. + +**Prompt 4 -- Introduction Habit Builder:** +> Here are 20 people in my network I have not spoken to in the last 6 months: [list names and one-line descriptions]. For each, suggest one person from the rest of the list (or from my broader network description) who would benefit from an introduction, and draft the introduction email. + +--- + +## Use Cases + +**Pre-Seed Founder Building an Advisory Network** + +A founder with no track record needs three advisors to lend credibility to an investor pitch. She begins by writing one handwritten thank-you card per day to people who have given her advice informally -- a former professor, a startup meetup organiser, a LinkedIn connection who answered a cold message. After two weeks, she starts making one introduction per day among her nascent network. Within sixty days, three of the people she connected offer to serve as formal advisors. She never asked directly. The gratitude and generosity created a reciprocity loop that produced the outcome naturally. + +**Growth-Stage CEO Retaining a Key Engineer** + +A lead engineer who built the core product has received a competing offer. The CEO's instinct is to match the salary. Instead, the CEO writes a handwritten card describing three specific contributions the engineer made that shaped the company's trajectory. She creates "Architecture Day" -- a surprise company-wide celebration of the engineering team's work, with the lead engineer recognised in front of the entire company. She sends a personalised gift: a first edition of the engineer's favourite programming textbook, found on a used bookstore site for $40. The engineer stays. The competing offer was 15% higher. The card, the celebration, and the gift outweighed the delta. + +**Scale-Stage Founder Maintaining Investor Relationships** + +A founder with twelve investors on the cap table and over a thousand LinkedIn connections cannot maintain personal relationships at that volume through meetings alone. She implements a three-tier system: (1) handwritten quarterly cards to all twelve investors with specific portfolio updates, (2) daily content curation on LinkedIn keeping her visible to the broader network, and (3) one personalised introduction per day connecting people in her network who should know each other. Two investors from her seed round participate in her Series B, citing "consistent communication and genuine relationship maintenance" as factors. Three introductions she made result in new business for her investors' other portfolio companies, deepening the relationships further. + +--- + +## Anti-Patterns + +**Transactional Gratitude.** Writing a thank-you card immediately before asking for something converts gratitude into manipulation. The practice must be sustained and unconditional. The returns compound over months, not minutes. + +**Praise Without Specificity.** "Great job!" is noise. "Your analysis of the churn data changed how we prioritise the roadmap this quarter" is signal. Generic praise feels performative; specific praise feels genuine because it requires the praiser to have actually noticed something. + +**Surprise-and-Delight as Compensation Substitute.** Balloons and cake cannot replace competitive salaries, clear career paths, and functional management. Variable rewards supplement good working conditions; they do not substitute for them. A company that celebrates Honey Day but pays below market is not inspiring -- it is deflecting. + +**Content Curation Without Curation.** Sharing ten articles per day with no filtering, no personal commentary, and no relevance to your audience is not staying top of mind. It is cluttering feeds. The EEI filter must be applied rigorously: does this entertain, educate, or inspire the specific people who follow me? + +**Introductions Without Due Diligence.** Connecting two people who have no reason to speak wastes both parties' time and diminishes your credibility as a connector. Every introduction should pass the test: can I articulate, in one sentence, why this connection is mutually beneficial? + +--- + +## By Stage + +| Stage | Retention Priority | Key Practices | +|-------|-------------------|---------------| +| Idea | Retaining cofounders and first believers | Handwritten cards; personalised gestures; making every interaction about their vision | +| Validation | Retaining pilot customers and early employees | Surprise-and-delight (small scale); thank-you cards to early adopters; daily introductions to build network | +| Early Traction | Retaining the team that got you here | Praise systems; Honey Day-style recognition; perspective resets during hard stretches | +| Growth | Retaining key talent against competing offers | Full thank-you card programme; personalised gifts; audience-centred all-hands presentations | +| Scale | Maintaining relationships across hundreds of stakeholders | Content curation at scale; introduction-per-day system; tiered relationship maintenance | + +At the idea stage, the founder's network is small enough that every relationship can be maintained personally. A single handwritten card to a cofounder after a hard week costs nothing and can prevent the slow drift of disengagement that kills early partnerships. At scale, the challenge inverts: the network is too large for personal maintenance, and systems -- content curation, scheduled introductions, tiered communication -- become necessary to sustain the warmth that personal attention provided at smaller scale. + +--- + +## Output Template + +```markdown +# Inspiration and Retention Plan + +**Company Stage:** [Idea / Validation / Early Traction / Growth / Scale] +**Team Size:** [Number] +**Key Relationships to Maintain:** [List names and roles] + +## Thank-You Card Programme +- Current practice: [None / Occasional / Systematic] +- 30-day target: [cards per week] +- Priority recipients this month: + 1. [Name] -- [reason for gratitude] + 2. [Name] -- [reason for gratitude] + 3. [Name] -- [reason for gratitude] + +## Surprise-and-Delight Calendar +| Month | Recipient(s) | Type of Recognition | Budget | +|-------|-------------|--------------------| -------| +| [Month] | [Random / Specific] | [Description] | [Amount] | + +## Introduction System +- Network inventory completed: [yes/no] +- Daily introduction target: [1 / 2 / 3] +- This week's introductions: + - [Person A] <-> [Person B]: [reason] + +## Personalised Gift Pipeline +| Recipient | Context | Gift Idea | Budget | Send Date | +|-----------|---------|-----------|--------|-----------| +| [Name] | [Why now] | [Gift] | [Amount] | [Date] | + +## Content Curation +- Platform(s): [LinkedIn / Twitter / Both] +- Weekly curation time blocked: [Day and time] +- Top 5 content sources: [list] +- Private share list: [5 names for personalised content delivery] + +## Praise Audit +- Last public praise given: [date, recipient, context] +- Last private criticism given: [date -- was it structured? was it private?] +- Praise-to-criticism ratio (last 30 days): [estimate] +``` + +--- + +## Related Skills + +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- Covers the structural dimensions of retention (career paths, compensation, culture); this skill provides the interpersonal practices that complement those structures. +- **[Carnegie's Win Friends and Influence People](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principles of appreciation and making others feel important are the theoretical roots of the thank-you card and praise practices detailed here. +- **[Teaching and Leading](../../content/skills/people/teaching-and-leading.md)** -- Mirror neurons, gratitude as a pre-meeting practice, and distributed leadership create the conditions under which the retention practices here are most effective. +- **[Influencing and Persuading](../../content/skills/people/influencing-and-persuading.md)** -- The storytelling and listening techniques inform the audience-centred presentation approach. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Handwritten cards, personalised gifts, and consistent content curation increase intimacy and reduce self-orientation in the trust equation. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Structured mentoring relationships operationalise the development dimension of retention that this skill addresses through interpersonal investment. diff --git a/plugins/foreman/skills/introvert-leadership/SKILL.md b/plugins/foreman/skills/introvert-leadership/SKILL.md deleted file mode 120000 index a866191..0000000 --- a/plugins/foreman/skills/introvert-leadership/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/introvert-leadership.md \ No newline at end of file diff --git a/plugins/foreman/skills/introvert-leadership/SKILL.md b/plugins/foreman/skills/introvert-leadership/SKILL.md new file mode 100644 index 0000000..117be0a --- /dev/null +++ b/plugins/foreman/skills/introvert-leadership/SKILL.md @@ -0,0 +1,195 @@ +--- +name: "introvert-leadership" +description: "Reframes introversion as a leadership asset and provides practical strategies for introverted leaders -- managing energy, deploying extroversion selectively, scheduling around social depletion, protecting reflection time, and supporting extroverted team members. Use when an introverted leader feels pressure to perform extroversion, struggles with energy management around high-social-demand periods, or needs to design a leadership style that leverages quiet strengths rather than compensating for perceived deficits." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - introversion + - energy-management + - leadership-style + - self-awareness + - quiet-leadership + - hybrid-work +related_skills: + - emotional-intelligence + - flow-state + - psychological-safety-practice + - mentoring-and-coaching +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Introvert Leadership + +REFRAME. Introversion is not a leadership handicap. It is an undervalued advantage operating in an environment that systematically rewards its opposite. Research from the University of Scarborough and the University of Minnesota confirms what introverted leaders already suspect: extroverted employees are paid more, promoted faster, and rated more positively by managers. The structural bias is real, measurable, and persistent. But the research also reveals something the bias obscures: the qualities that introversion cultivates -- deep listening, careful deliberation, comfort with sustained focus, resistance to impulsive decision-making -- are precisely the qualities that complex leadership demands. The challenge for introverted leaders is not to become extroverts. It is to stop treating introversion as a condition to be managed and start treating it as a capability to be deployed. + +Justin Zorn and Leigh Marz's research on the cognitive benefits of silence, Michael Porter and Nitin Nohria's findings on how effective CEOs use solitary time, and Erica Dhawan's work on hybrid team dynamics converge on a conclusion that corporate culture is slow to absorb: quiet leadership is not a lesser form of leadership. It is a different form, with its own distinctive strengths -- and its own distinctive requirements for energy management, schedule design, and self-advocacy. + +--- + +## The Framework + +Introvert leadership operates across five strategic domains. Each addresses a specific challenge that introverted leaders face and provides a practical response that leverages introversion rather than compensating for it. + +### Domain 1: The Energy Ledger + +Introversion is fundamentally an energy equation. Social interaction depletes energy that solitude restores. This is not a preference; it is a neurological reality. The practical implication: energy must be managed as deliberately as a budget. + +**The energy audit:** + +1. List the recurring social demands of your role: meetings, client dinners, all-hands presentations, networking events, one-on-ones. +2. For each, rate the energy cost on a 1-5 scale (1 = minimal drain, 5 = requires significant recovery). +3. For each, rate the energy recovery time needed (15 minutes, 1 hour, half a day). +4. Map these against your weekly schedule. + +Most introverted leaders discover that their energy deficit is not caused by one catastrophic drain but by the accumulation of moderate drains without sufficient recovery time between them. The solution is structural, not motivational: schedule recovery time as deliberately as meetings. + +### Domain 2: Selective Extroversion + +The advice to "act like an extrovert" is simultaneously correct and dangerous. Correct because certain leadership moments -- a pitch meeting, a team rally, a client dinner -- require visible energy and social engagement. Dangerous because performing extroversion without strategic management leads to what researchers call an "extroversion hangover" -- a depletion so severe that it impairs performance for hours or days afterward. + +The protocol: + +- **Identify high-extroversion moments in advance.** Review the upcoming week and flag the events that will require you to be "on." +- **Block recovery time before and after.** Not optional. Not aspirational. Calendared. +- **Set a social energy budget for each event.** Decide in advance how long you will be fully engaged (e.g., "I will be present and energetic for 90 minutes at this cocktail reception, then leave") and honour the limit. +- **Never wing it.** Spontaneous extroversion is the most costly kind. Preparation reduces the energy expenditure of social performance by providing structure and predictability. + +The distinction matters: selective extroversion is a strategic deployment. Performative extroversion -- attempting to be "on" continuously -- is unsustainable and unnecessary. + +### Domain 3: The Power of Silence + +Zorn and Marz's research identifies sustained silence as a restorative practice that extends beyond mere introvert self-care. Silence restores the nervous system, sustains energy, and conditions the mind for adaptive, creative thinking. But the silence that matters is not merely the absence of office noise or notification pings. It is the quieting of inner chatter -- the mental reflexes that habitually protect reputation, promote a point of view, or rehearse social interactions. + +Practical applications: + +- **Schedule thinking blocks.** Porter and Nohria's research on CEO time allocation found that the most effective leaders protect significant blocks of solitary time for reflection, preparation, and deep thinking. This is not a luxury; it is a performance driver. +- **Use silence in meetings.** Introverted leaders who pause before responding -- rather than racing to fill conversational gaps -- often find that the pause increases the weight of what they say. Teams learn to anticipate substance from a leader who speaks selectively. +- **Distinguish between withdrawal and recharge.** Colleagues may interpret an introverted leader's need for solitude as disengagement. Proactive communication ("I'm going to spend the next hour thinking through the Q4 plan; I'll share my conclusions at 3 PM") prevents misinterpretation. + +### Domain 4: Recognising Quiet Passion + +Kai Krautter, Anabel Buchner, and Jon Jachimowicz's research exposes a persistent bias: managers assume that visible enthusiasm -- chatting eagerly, displaying excitement, engaging energetically with colleagues -- is a reliable proxy for commitment. Quieter employees who express passion through thoroughness, deep immersion in detail, and extra hours on difficult problems are systematically undervalued. + +For introverted leaders, this bias operates in two directions: + +- **Inward:** recognising that your own commitment may be invisible to those who equate passion with volume, and making deliberate choices about how to signal investment without performing enthusiasm you do not feel. +- **Outward:** recognising the same bias in how you evaluate your team. The engineer who stays late debugging a complex system may be more passionate than the one who talks excitedly about it in the morning standup. Judge by output quality and depth of engagement, not by decibel level. + +### Domain 5: Supporting Extroverts Without Draining Yourself + +Erica Dhawan's research on hybrid work dynamics identifies a reciprocal challenge: just as introverts need solitude, extroverts need social connection -- and in hybrid and remote environments, that connection is harder to find. The introverted leader who creates a team culture optimised exclusively for quiet focus will underserve extroverted team members who derive energy and ideas from interaction. + +The balance: + +- **Hold optional social events** -- hybrid lunches, informal coffee chats, happy hours -- without making them mandatory. Extroverts get the connection they need; introverts retain the choice. +- **Use breakout groups in meetings.** Smaller groups reduce the social energy cost for introverts while giving extroverts the interactive processing they prefer. +- **Meet extroverts regularly** in one-on-one or small-group settings where their need for social processing can be addressed without requiring the introverted leader to perform group-level extroversion. +- **Be transparent about your own needs** without apologising for them. "I do my best thinking alone, and I do my best listening in small groups" is a statement of operational reality, not a confession of inadequacy. + +--- + +## Prompts + +**Prompt 1 -- Energy Ledger:** +> Here is my typical weekly schedule: [list recurring meetings, events, and social obligations with approximate durations]. For each, rate the likely energy cost for an introverted leader (1-5 scale) and the recovery time needed. Then identify the highest-risk days -- where energy drains are clustered without recovery -- and redesign the schedule to create sustainable energy flow. I can change approximately [X%] of my schedule. + +**Prompt 2 -- Selective Extroversion Plan:** +> I have these high-extroversion events coming up: [list events with dates and descriptions]. For each, help me plan: how long I should commit to being "on," what preparation would reduce energy cost, what recovery time to block, and what my exit strategy should be. Also suggest one way I can contribute to each event that plays to introvert strengths rather than requiring extrovert performance. + +**Prompt 3 -- Quiet Passion Visibility:** +> I am an introverted leader and I suspect my commitment is not visible to my [board / CEO / peers]. Here is how I currently demonstrate investment in my work: [describe]. Suggest five ways I can make my engagement more visible without performing enthusiasm I do not feel. Each suggestion should be authentic to an introvert's working style. + +**Prompt 4 -- Team Energy Balance:** +> My team includes both introverts and extroverts, and we work in a [hybrid / remote / in-office] arrangement. Here is our current meeting and communication structure: [describe]. Evaluate whether this structure systematically advantages one working style over the other, and recommend changes that serve both without requiring either group to suppress their natural energy patterns. + +--- + +## Use Cases + +**Validation-Stage Founder Preparing for Investor Pitches** +An introverted technical founder faces a month of investor meetings -- back-to-back conversations requiring charisma, quick verbal responses, and sustained social energy. The selective extroversion protocol is applied: pitch meetings are clustered into two days per week with recovery days between, preparation includes rehearsed responses to the twenty most likely questions (reducing cognitive load during performance), and each pitch day ends with a two-hour solitary block. The founder also restructures the pitch itself to leverage introvert strengths: deep technical demonstration rather than performative enthusiasm, and prepared questions that shift the conversation toward dialogue rather than monologue. Investors respond to the depth and substance. Three term sheets result. + +**Growth-Stage VP Managing a High-Extroversion Leadership Team** +A VP of Product -- deeply introverted -- leads a team of six directors, five of whom are extroverts. Team meetings feel exhausting because the conversational style is rapid, overlapping, and energy-intensive. The VP restructures: meetings begin with five minutes of silent written reflection (each person writes their key points before discussion begins), followed by structured discussion where each person speaks in turn. The format gives the VP processing time, gives extroverts the social interaction they need, and produces better outcomes because ideas are considered before they are debated. The introverted VP also schedules one-on-ones with each director at a lower social intensity than group settings, reserving group energy expenditure for situations where collective discussion is genuinely necessary. + +**Scale-Stage CEO Protecting Thinking Time** +A CEO of a 600-person company finds that every hour of every day is filled with meetings. The energy ledger reveals that the schedule is designed for an extrovert: back-to-back social interactions from 8 AM to 6 PM, with "thinking" relegated to evenings and weekends. The redesign: two mornings per week are blocked as "CEO deep work" -- no meetings, no calls, no Slack. The initial resistance from the executive team ("the CEO is unavailable") subsides when the quality of the CEO's strategic contributions improves noticeably. One executive observes: "You used to be reactive in our meetings. Now you come prepared with something we hadn't considered." The preparation happened during the quiet mornings that introversion required and the schedule had previously denied. + +--- + +## Anti-Patterns + +1. **The Apology Stance.** Treating introversion as something to apologise for or explain away. "Sorry, I'm just an introvert" positions a neurological trait as a deficiency. "I do my best work with time to think" positions the same trait as a professional operating principle. + +2. **Complete Withdrawal.** Using introversion as justification for avoiding all social leadership responsibilities. Team connection, stakeholder management, and visible presence are genuine leadership requirements. The task is not to avoid them but to manage energy around them strategically. + +3. **Forcing Extroversion on the Team.** Introverted leaders who overcompensate by creating an exclusively extroverted team culture -- mandatory social events, open-plan offices, constant collaboration -- in an attempt to prove they are not "too quiet." This penalises other introverts and creates the very environment the leader finds draining. + +4. **Ignoring Extrovert Needs.** The mirror anti-pattern: designing all communication and collaboration for quiet, asynchronous, written interaction without providing the social interaction that extroverted team members require to do their best work. Introvert-optimised is not team-optimised. + +5. **Conflating Introversion with Social Anxiety.** Introversion is an energy pattern. Social anxiety is a clinical condition. The former requires energy management. The latter may require professional support. Treating anxiety as "just being introverted" delays intervention; treating introversion as anxiety pathologises a healthy variation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Leveraging depth over breadth | The introverted founder's advantage is the ability to think deeply about a problem before others have finished brainstorming. The risk is isolation -- failing to test ideas with enough external perspectives because solitary thinking feels productive. | +| Validation | Managing pitch energy | Customer discovery and investor conversations are socially intensive. The selective extroversion protocol is critical here. Preparation and recovery scheduling are non-negotiable. | +| Early Traction | Establishing leadership presence | As the team grows beyond the founder's immediate circle, the introverted leader must make their presence felt without performing extroversion. Written communication, structured one-on-ones, and visible preparation become the primary leadership channels. | +| Growth | Designing for both styles | The organisation is large enough to include significant numbers of both introverts and extroverts. The leader's task is to design meeting structures, communication norms, and collaboration tools that serve both energy patterns. | +| Scale | Protecting institutional quiet | At scale, organisational culture tends toward noise -- more meetings, more Slack channels, more "alignment sessions." The introverted leader's contribution is advocating for and protecting the conditions under which deep thinking happens: solitary time, focused work blocks, and the organisational permission to be unavailable. | + +--- + +## Output Template + +```markdown +# Introvert Leadership Strategy: [Leader Name / Role] + +## Energy Ledger +| Activity | Frequency | Energy Cost (1-5) | Recovery Needed | Currently Scheduled? | +|----------|-----------|-------------------|-----------------|---------------------| +| [activity] | [daily/weekly/monthly] | [1-5] | [time] | [yes/no] | + +## High-Risk Days +- [Day]: [why energy drain exceeds recovery capacity] +- Proposed adjustment: [specific schedule change] + +## Selective Extroversion Plan +| Event | Duration "On" | Preparation | Recovery Block | Exit Strategy | +|-------|--------------|-------------|----------------|---------------| +| [event] | [minutes] | [what to prepare] | [when/how long] | [how to leave gracefully] | + +## Quiet Strengths Deployment +- Meetings: [how introvert strengths will be applied] +- Written communication: [how depth and clarity will substitute for volume] +- One-on-ones: [how small-group interaction will be prioritised] + +## Team Balance Check +- Introvert needs addressed: [specific structures] +- Extrovert needs addressed: [specific structures] +- Hybrid/remote adjustments: [specific accommodations] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness -- understanding one's own energy patterns and their impact on leadership behaviour -- is the foundation of introvert leadership strategy. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Csikszentmihalyi's flow research explains why introverts often produce their best work in solitary, deeply focused conditions; protecting the conditions for flow is a strategic priority. +- **[Psychological Safety in Practice](../../content/skills/leadership/psychological-safety-practice.md)** -- Introverted leaders who model thoughtful silence and deep listening often build stronger psychological safety than extroverted leaders who fill every conversational space. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Introverted leaders frequently excel in one-on-one mentoring relationships, where depth of attention and listening quality matter more than social energy. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- The scheduling techniques for protecting deep work blocks are essential infrastructure for introverts who need solitary time to function at peak capacity. +- **[Myers-Briggs Type Indicator](../../content/skills/frameworks/myers-briggs-type-indicator.md)** -- Provides the personality framework that contextualises introversion-extroversion within a broader typology useful for understanding team energy dynamics. diff --git a/plugins/foreman/skills/johari-window/SKILL.md b/plugins/foreman/skills/johari-window/SKILL.md deleted file mode 120000 index 51a3199..0000000 --- a/plugins/foreman/skills/johari-window/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/johari-window.md \ No newline at end of file diff --git a/plugins/foreman/skills/johari-window/SKILL.md b/plugins/foreman/skills/johari-window/SKILL.md new file mode 100644 index 0000000..9e30000 --- /dev/null +++ b/plugins/foreman/skills/johari-window/SKILL.md @@ -0,0 +1,193 @@ +--- +name: "johari-window" +description: "Improves self-awareness, trust, and team communication using the Johari Window model with its four panes: Open (known to self and others), Blind Spot (known to others, not self), Hidden (known to self, not others), and Unknown. Use when building trust within teams, identifying leadership blind spots, improving co-founder communication, designing feedback rituals that expand the Open pane, diagnosing why a team suffers from misinterpretation and defensive posturing, or developing self-awareness as a leadership competency." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - early-traction + - growth + - scale +tags: + - self-awareness + - feedback + - trust + - team-dynamics + - communication +related_skills: + - emotional-intelligence + - psychological-safety + - myers-briggs-type-indicator + - grow-model +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Johari Window + +What do the people you work with most closely know about you that you do not know about yourself? The question is uncomfortable precisely because the answer, by definition, is invisible to the person it most concerns. Joseph Luft and Harrington Ingham -- whose first names combine to form "Johari" -- devised their four-pane window model in 1955 at the University of California, Los Angeles, as a tool for understanding self-awareness in group settings. Six decades later, it remains one of the most intuitively powerful frameworks for diagnosing trust, communication, and relational effectiveness in teams. Its enduring utility lies in a simple geometric truth: the less a team knows about each other's thinking, motivations, and concerns, the more organisational energy is wasted on misinterpretation, defensive posturing, and avoidable conflict. + +--- + +## The Framework + +The Johari Window divides information about a person into four quadrants based on two axes: what is known to the self and what is known to others. + +### The Four Quadrants + +``` + Known to Self Unknown to Self + ┌─────────────────────┬─────────────────────┐ + │ │ │ + Known to │ OPEN │ BLIND SPOT │ + Others │ (Arena) │ │ + │ │ │ + ├─────────────────────┼─────────────────────┤ + │ │ │ + Unknown to │ HIDDEN │ UNKNOWN │ + Others │ (Facade) │ │ + │ │ │ + └─────────────────────┴─────────────────────┘ +``` + +**Open (Arena)** -- Information known to both self and others. This is the quadrant of effective communication: shared understanding, transparent motivations, acknowledged strengths and weaknesses. The larger this quadrant, the more efficiently the relationship functions. Communication requires less guesswork, trust is higher, and collaboration is more fluid. + +**Blind Spot** -- Information known to others but not to self. These are the behaviours, habits, communication patterns, and impacts that others observe but the individual does not recognise. A founder who believes she is collaborative but whose team experiences her as directive has a blind spot. The gap between self-perception and others' perception is the territory of this quadrant. + +**Hidden (Facade)** -- Information known to self but not shared with others. Fears, insecurities, strategic calculations, past experiences, personal motivations -- the things a person knows about themselves but chooses (consciously or unconsciously) to withhold. A founder who is privately worried about running out of capital but presents confidence to the team is operating with a large Hidden quadrant. + +**Unknown** -- Information unknown to both self and others. Latent talents, unconscious motivations, repressed experiences, undiscovered potential. This quadrant shrinks through novel experiences, deep reflection, coaching, and sometimes crisis -- which has a way of revealing capabilities and vulnerabilities that normal conditions do not surface. + +### The Two Mechanisms of Change + +The Johari Window is dynamic. The quadrant sizes shift through two deliberate actions: + +**Self-disclosure** moves the boundary between Hidden and Open. When a person shares information about themselves -- their concerns, motivations, uncertainties, values -- the Open quadrant expands downward at the expense of the Hidden quadrant. For entrepreneurs, strategic self-disclosure builds trust: an investor who understands the founder's genuine concerns makes better-informed decisions than one who only sees the facade. + +**Feedback-seeking** moves the boundary between Blind Spot and Open. When a person actively solicits and receives honest feedback, the Open quadrant expands rightward at the expense of the Blind Spot. For founders, feedback is the only mechanism for closing the gap between how they perceive their leadership and how it is actually experienced. + +The interaction between these two mechanisms is multiplicative. Self-disclosure invites reciprocal disclosure. Feedback-seeking, when received non-defensively, encourages others to give more feedback. The result is a virtuous cycle that progressively enlarges the Open quadrant -- which is the quadrant where productive work happens. + +### The Window at Team Level + +While originally designed for interpersonal relationships, the Johari Window applies to teams and organisations. An organisation's "Open" quadrant is its shared understanding: strategy, values, challenges, and information that everyone has access to. Its "Hidden" quadrant is what leadership knows but does not share (strategic plans, financial concerns, personnel issues). Its "Blind Spot" is what employees, customers, or the market perceive but leadership does not recognise. Its "Unknown" quadrant is the unexamined potential and latent risks that no one has yet identified. + +Startups tend to have large Open quadrants in their earliest days (when everyone is in one room and information flows freely) and progressively smaller ones as they grow -- unless deliberate mechanisms are built to counteract the natural narrowing. + +--- + +## Prompts + +**Prompt 1 -- Personal Johari Audit:** +> Help me conduct a Johari Window self-assessment based on the following inputs. My self-perception: [describe how you see your leadership style, strengths, weaknesses, and impact on others]. Feedback I have received from others: [describe feedback -- formal and informal -- from co-founders, team, investors, mentors]. Identify likely blind spots (gaps between self-perception and feedback), hidden areas (things I know about myself that I am not sharing with my team), and hypothesise about potential unknowns. Recommend specific actions to expand my Open quadrant. + +**Prompt 2 -- Team Johari Mapping:** +> Map the Johari Window dynamics of my team based on these observations: [describe each team member's communication openness, receptivity to feedback, tendency to withhold information, and known blind spots]. For the team as a whole, assess the relative size of each quadrant. Identify the highest-leverage intervention: should we focus on increasing self-disclosure (team retreats, structured sharing), feedback (360 reviews, retrospectives), or both? Design a specific exercise we can run in our next team meeting to expand the Open quadrant. + +**Prompt 3 -- Investor Relationship Disclosure Strategy:** +> I am managing relationships with [number] investors. Help me design a strategic self-disclosure approach using the Johari framework. Here is what I currently share openly: [list]. Here is what I withhold: [list concerns, challenges, uncertainties you do not share]. For each hidden item, advise whether disclosure would build trust (move to Open) or is appropriately private (remain Hidden). For items I should disclose, recommend how and when to share them for maximum trust-building effect. + +--- + +## Use Cases + +**Early-traction co-founder relationship under strain** + +Two co-founders have been working together for 18 months. Surface communication is professional, but both harbour unspoken frustrations. The CEO resents the CTO's resistance to customer feedback (hidden); the CTO feels undervalued because the CEO takes credit in investor meetings (hidden). Neither has shared these concerns. Meanwhile, the CEO has a blind spot: she micromanages technical decisions without realising it. The CTO has a blind spot: his communication style reads as dismissive to non-technical team members. + +A facilitated Johari exercise maps the current state: both co-founders have large Hidden and Blind Spot quadrants with each other, despite working together daily. The intervention involves structured self-disclosure (each co-founder shares their three biggest unspoken concerns) followed by structured feedback (each shares one blind spot they have observed in the other). The conversation is uncomfortable but transformative. The CEO acknowledges her micromanagement and commits to defined decision boundaries. The CTO acknowledges his communication style and agrees to a monthly feedback check-in with the team. Eighteen months of accumulated friction dissolves in two hours of structured honesty. + +**Growth-stage company with an information silo problem** + +A 60-person company has evolved departmental silos where marketing, engineering, and sales each have large Hidden quadrants vis-a-vis the others. Engineering does not share technical constraints until they become crises. Marketing does not share campaign performance data that might reflect poorly on their work. Sales does not share customer complaints that contradict the company narrative. The CEO, aware that something is wrong but unable to pinpoint it, implements a Johari-informed transparency programme: cross-functional standups where each department shares one success, one challenge, and one concern from the week. The format is deliberately structured to normalise disclosure. Within a quarter, the inter-departmental Open quadrant expands measurably, reflected in fewer surprise escalations, faster cross-functional projects, and improved employee satisfaction scores. + +**Scale-stage executive discovering personal blind spots through 360 review** + +A CEO at a 300-person company commissions a 360-degree feedback review and discovers a jarring blind spot: while she perceives herself as approachable and open to dissent, 70% of direct reports describe her as "intimidating" and report self-censoring in her presence. The CEO's Johari Blind Spot quadrant is large. The corrective is not a single action but a sustained practice: the CEO begins each leadership meeting by explicitly inviting disagreement, publicly changes her position when persuaded, and asks a trusted lieutenant to provide real-time feedback on her nonverbal cues during discussions. Over six months, the 360 scores shift significantly -- not because the CEO changed her personality but because deliberate feedback-seeking and behavioural adjustment expanded her Open quadrant. + +--- + +## Anti-Patterns + +**1. Forced disclosure in a low-trust environment.** Running a Johari exercise before establishing baseline psychological safety produces performative sharing at best and genuine harm at worst. People share what they believe is safe to share, which in a low-trust environment means nothing meaningful -- or, worse, information that is later used against them. Psychological safety is a prerequisite, not a byproduct, of Johari work. + +**2. Treating all feedback as equally valid.** The Blind Spot quadrant contains genuine blind spots, but it also contains misperceptions. Not all feedback is accurate. A founder who accepts every piece of feedback uncritically risks distorting their self-model based on others' projections, biases, or limited perspectives. The skill lies in triangulating: feedback that appears from multiple independent sources is more likely to reflect a genuine blind spot. + +**3. Asymmetric disclosure.** When leaders demand transparency from their teams without reciprocating, the exercise becomes extractive rather than relational. The Johari Window works through mutual expansion of the Open quadrant. A CEO who asks the team to share concerns while keeping their own concerns hidden creates a surveillance dynamic, not a trust dynamic. + +**4. Confusing self-disclosure with oversharing.** Strategic self-disclosure is purposeful: sharing information that helps others work with you more effectively. Oversharing -- unburdening personal anxieties, sharing irrelevant personal details, or processing emotions publicly without regard for the audience -- erodes professional trust rather than building it. The question to ask before disclosing: "Will sharing this help the other person understand me better in a way that improves our working relationship?" + +**5. One-time exercise rather than ongoing practice.** A single Johari workshop produces a snapshot. The window's quadrants shift constantly as circumstances change, new people join, and new challenges emerge. Effective application requires regular, lightweight practices (weekly check-ins, quarterly feedback cycles) rather than annual events. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder transparency, founding team trust | Open quadrant is naturally large due to proximity; the priority is preventing Hidden and Blind Spot growth as the team begins to specialise | +| Growth | Cross-functional transparency, management feedback loops | Information silos form naturally as the organisation departmentalises; deliberate Johari practices counteract this tendency | +| Scale | Executive blind spots, organisational transparency, culture maintenance | The distance between leadership and frontline creates structural blind spots; formal mechanisms (360 reviews, skip-levels, anonymous channels) become essential | + +At early traction, the Johari Window is naturally favourable -- small teams in close quarters share information freely, feedback is constant, and little is hidden. The risk at this stage is complacency: assuming that transparency will persist without effort. As the team grows and specialises, Hidden quadrants expand (people withhold concerns to avoid rocking the boat) and Blind Spots calcify (the founder receives less honest feedback as power dynamics solidify). + +At growth, the architectural challenge emerges. Departments form, and with them information boundaries. Cross-functional Johari practices -- structured information-sharing rituals that counteract silo formation -- become a deliberate organisational investment. The founder must also reckon with their own growing Blind Spot: as the company grows, fewer people feel comfortable giving the founder candid feedback. + +At scale, the Johari Window becomes a governance tool. Executive blind spots at this stage can be catastrophic (recall any corporate scandal where "leadership didn't know" about a systemic problem that was visible to everyone else). Formal feedback mechanisms, anonymous reporting channels, and external advisory relationships are the structural equivalents of feedback-seeking in the original two-person model. + +--- + +## Output Template + +```markdown +# Johari Window Assessment -- [Individual/Team Name] + +**Prepared for:** [Individual / Team Lead] +**Date:** [Date] +**Context:** [Trigger for assessment -- e.g., team formation, conflict resolution, leadership development] + +## Current Window State + +### Quadrant Size Estimate (1-10 scale, where 10 = largest) +- **Open:** [Score] -- [Key evidence] +- **Blind Spot:** [Score] -- [Key evidence] +- **Hidden:** [Score] -- [Key evidence] +- **Unknown:** [Score] -- [Key evidence] + +## Blind Spot Analysis +| Blind Spot Identified | Source(s) | Confidence Level | Impact | +|----------------------|-----------|-----------------|--------| +| [Behaviour/pattern unseen by self] | [Who provided this feedback] | [High/Medium/Low -- based on triangulation] | [Effect on team/outcomes] | + +## Hidden Inventory +| Item Currently Hidden | Reason for Withholding | Disclosure Recommendation | Timing | +|----------------------|----------------------|--------------------------|--------| +| [Concern/information being withheld] | [Fear, strategy, habit] | [Disclose / Keep hidden / Partial disclosure] | [When and how] | + +## Expansion Plan + +### Self-Disclosure Actions +1. [Specific information to share, with whom, and when] +2. [Specific information to share, with whom, and when] + +### Feedback-Seeking Actions +1. [Specific feedback to request, from whom, and the question to ask] +2. [Specific feedback to request, from whom, and the question to ask] + +## Measurement +- **Reassessment date:** [When to re-evaluate quadrant sizes] +- **Leading indicators of Open quadrant growth:** [Observable changes to watch for] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- The self-awareness domain of EQ maps directly to the Johari process of reducing the Blind Spot quadrant, while empathy enables more effective feedback delivery. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Safety is the precondition for both self-disclosure and honest feedback; without it, the Johari Window remains static regardless of the exercises attempted. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- The SBI model provides the structured method for delivering the feedback that shrinks the Blind Spot quadrant, turning Johari insights into actionable conversations. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Scott's framework provides the courage and care required for the honest feedback exchanges that expand the Open quadrant in both directions. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- Provides the reflective practices that help leaders voluntarily shrink their Hidden quadrant and actively seek feedback to reduce their Blind Spots. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- The Stoic practice of rigorous self-examination complements the Johari framework by providing philosophical grounding for honest self-assessment. diff --git a/plugins/foreman/skills/kaizen-bpr/SKILL.md b/plugins/foreman/skills/kaizen-bpr/SKILL.md deleted file mode 120000 index 0dc3477..0000000 --- a/plugins/foreman/skills/kaizen-bpr/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/kaizen-bpr.md \ No newline at end of file diff --git a/plugins/foreman/skills/kaizen-bpr/SKILL.md b/plugins/foreman/skills/kaizen-bpr/SKILL.md new file mode 100644 index 0000000..b97d762 --- /dev/null +++ b/plugins/foreman/skills/kaizen-bpr/SKILL.md @@ -0,0 +1,219 @@ +--- +name: "kaizen-bpr" +description: "Applies two complementary process improvement philosophies: Kaizen (continuous incremental improvement) and Business Process Reengineering (radical process redesign from scratch). Helps determine when to refine existing processes versus when to tear them up and rebuild. Use when operational efficiency is declining, processes have accumulated technical debt, preparing for rapid scaling, diagnosing bottlenecks, choosing between incremental optimization and transformative redesign, or building a culture of continuous improvement." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - process-improvement + - operational-excellence + - continuous-improvement + - transformation + - lean-operations +related_skills: + - systems-thinking + - balanced-scorecard + - shamrock-organisation + - product-life-cycle +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Kaizen & Business Process Reengineering + +Two philosophies of improvement emerged from opposite ends of the industrial world, and they could hardly be more different in temperament. From Japan: Kaizen -- the quiet, relentless discipline of making things a little better every day. From America: Business Process Reengineering (BPR) -- the dramatic act of tearing up existing processes and rebuilding them from scratch. One whispers. The other shouts. Toyota embodied the first; Michael Hammer and James Champy evangelised the second in their 1993 manifesto *Reengineering the Corporation*. The genius lies not in choosing between them but in understanding when each is appropriate -- and recognising that most organisations need both, applied at different times and to different problems. + +--- + +## The Framework + +### Kaizen: The Continuous Improvement Philosophy + +Kaizen (Japanese: "change for better") is not a technique but a culture. Masaaki Imai introduced it to Western audiences in 1986, describing the management philosophy that powered Japan's post-war industrial ascent. The core principle is disarmingly simple: every process can be improved, every day, by the people who do the work. + +**Before Kaizen:** +- Improvement is a management responsibility +- Changes come in large, infrequent projects +- Workers execute; managers think +- Defects are found at inspection +- "Good enough" is the standard + +**After Kaizen:** +- Improvement is everyone's responsibility +- Changes come in small, continuous increments +- Workers observe, suggest, and implement improvements +- Defects are prevented at the source +- "Better than yesterday" is the standard + +**The Kaizen Cycle (PDCA):** + +1. **Plan** -- Identify a specific, measurable improvement opportunity. Define the current state and the target state. +2. **Do** -- Implement the change on a small scale. Treat it as an experiment, not a commitment. +3. **Check** -- Measure the results. Did the change achieve the target? What unexpected effects emerged? +4. **Act** -- If successful, standardise the new method. If not, analyse why and begin the cycle again. + +**Key Kaizen Principles:** +- Go to the Gemba (the actual place where work happens) -- do not improve processes from a conference room +- Eliminate Muda (waste) in all seven forms: overproduction, waiting, transport, overprocessing, inventory, motion, defects +- Respect the expertise of frontline workers -- they understand the process better than any consultant +- Small changes compound; a 1% daily improvement yields a 37x annual improvement mathematically + +### BPR: The Radical Redesign + +Business Process Reengineering rejects incrementalism. Hammer's famous dictum: "Don't automate, obliterate." BPR asks not "How do we improve this process?" but "If we were building this from nothing, how would we design it?" + +**Before BPR:** +- Processes evolve organically over years, accumulating complexity +- Departments optimise locally, creating handoffs and bottlenecks +- Technology is layered onto existing workflows +- The question is "How do we do this faster?" + +**After BPR:** +- Processes are redesigned around desired outcomes, not existing activities +- Cross-functional teams replace departmental handoffs +- Technology enables fundamentally new ways of working +- The question is "Why do we do this at all?" + +**The BPR Methodology:** + +1. **Identify** -- Select the process with the highest impact potential. Focus on processes that are broken, not merely slow. +2. **Understand** -- Map the current process end-to-end. Quantify cost, time, error rates, and customer impact. +3. **Redesign** -- Start from the desired outcome and work backward. Ignore existing constraints. Design the ideal process. +4. **Implement** -- Execute the redesign with full commitment. BPR is not a pilot; it is a replacement. +5. **Sustain** -- Monitor the new process and apply Kaizen to maintain and incrementally improve it. + +### When to Use Each + +| Dimension | Kaizen | BPR | +|-----------|--------|-----| +| **Scope of change** | Incremental, continuous | Radical, episodic | +| **Risk profile** | Low risk per change; cumulative impact | High risk; high reward or high failure | +| **Time horizon** | Ongoing, never-ending | Project-based, 6-18 months | +| **Who drives it** | Frontline workers and teams | Senior leadership and cross-functional teams | +| **Best when** | Process is fundamentally sound but inefficient | Process is fundamentally broken or obsolete | +| **Cultural requirement** | Trust, empowerment, psychological safety | Executive sponsorship, change management capability | +| **Failure mode** | Stagnation if management attention wanes | Organisational trauma if execution fails | + +The relationship is sequential, not competitive. BPR creates new processes; Kaizen refines them. An organisation that only does BPR lurches from revolution to revolution. An organisation that only does Kaizen risks polishing a process that should have been replaced entirely. + +--- + +## Prompts + +**Prompt 1 -- Process Waste Identification (Kaizen):** +> "Analyse this business process: [describe process step by step]. Identify all seven types of waste (overproduction, waiting, transport, overprocessing, inventory, motion, defects) present in the process. For each waste identified, propose a specific Kaizen improvement that could be implemented within one week by the team that owns the process." + +**Prompt 2 -- BPR Candidate Assessment:** +> "Evaluate these business processes for BPR suitability: [list 3-5 processes with brief descriptions]. For each, score on three dimensions: (1) how broken is the current process (1-10), (2) how significant is the business impact of improvement (1-10), (3) how feasible is radical redesign given our current resources and capabilities (1-10). Recommend which process to reengineer first and explain why." + +**Prompt 3 -- Zero-Base Process Design:** +> "Ignore how we currently handle [process name]. If we were designing this process from scratch today, with access to current technology and no legacy constraints, what would the ideal process look like? Define the desired outcome first, then design backward. Include the number of steps, roles involved, technology required, and expected cycle time." + +**Prompt 4 -- Kaizen Event Planning:** +> "Design a five-day Kaizen event (Kaizen Blitz) for improving [specific process]. Include: Day 1 objectives (current state mapping), Day 2-3 activities (root cause analysis and solution design), Day 4 actions (implementation), and Day 5 deliverables (measurement and standardisation). Specify the team composition needed and the metrics we should track before, during, and after the event." + +--- + +## Use Cases + +**Early-Traction Startup Reducing Customer Onboarding Time** + +A B2B SaaS company discovers that customer onboarding takes an average of 23 days -- far longer than the industry benchmark of 7 days. A Kaizen analysis of the process reveals seven handoffs between sales, customer success, and engineering, with an average wait time of 2.3 days per handoff. Rather than reengineering the entire process, the team implements incremental improvements: eliminating two unnecessary approval steps (3 days saved), creating a shared onboarding dashboard that replaces email-based status updates (4 days saved), and automating the technical provisioning step (5 days saved). Onboarding drops to 11 days in 30 days. A subsequent Kaizen cycle targets the remaining gap. + +**Growth-Stage Logistics Company Reengineering Order Fulfilment** + +A direct-to-consumer company processing 5,000 orders per day hits a wall. The fulfilment process, designed when volume was 200 orders per day, has been patched and extended so many times that it now involves 34 steps across four systems that do not communicate. Kaizen improvements yield marginal gains, but the fundamental architecture is broken. The company undertakes BPR: redesigning fulfilment around a single integrated platform, reducing the process to 12 steps, eliminating three manual data-entry points, and implementing batch processing for common order types. Fulfilment cost drops 40%, error rate drops 85%, and the process now scales to 20,000 orders per day without additional headcount. Post-launch, a Kaizen programme maintains and refines the new process. + +--- + +## Anti-Patterns + +**Kaizen Theatre.** Running suggestion programmes and improvement workshops without giving teams the authority, time, or budget to implement changes. Kaizen without empowerment is performance art. If management reviews but never approves suggestions, the programme dies within months. + +**BPR as Euphemism for Layoffs.** In the 1990s, BPR became corporate code for headcount reduction. When reengineering is perceived as a vehicle for redundancy rather than genuine process improvement, it poisons organisational trust and ensures that the people who best understand the processes will not participate honestly in redesigning them. + +**Incremental Improvement of a Broken Process.** Applying Kaizen to a process that needs BPR. Polishing a fundamentally flawed workflow yields diminishing returns and frustrates teams who can see that the underlying design is wrong. If the process architecture is the problem, incremental improvement is the wrong tool. + +**Big Bang Without Change Management.** Launching BPR without investing in the human side of transformation. New processes fail not because the design is wrong but because the people expected to execute them were not consulted, trained, or motivated. Hammer himself later acknowledged that BPR's failure rate -- estimated at 50-70% -- was largely attributable to neglecting the human dimension. + +**Measuring Activity Instead of Outcomes.** Counting the number of Kaizen suggestions submitted rather than the measurable improvement in process performance. Vanity metrics in improvement programmes are as dangerous as vanity metrics in product development. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Establish process discipline | Introduce Kaizen thinking before processes calcify; document workflows early | +| Growth | Identify BPR candidates | Processes designed for 10 customers rarely work for 10,000; watch for breaking points | +| Scale | Institutionalise both | Formal Kaizen programmes (dedicated time, measurement, recognition) and periodic BPR reviews of major processes | + +At early traction, the primary risk is having no documented processes at all. Kaizen requires a baseline to improve upon. The first step is making the invisible visible: mapping how work actually flows, not how founders assume it flows. + +During growth, the signal for BPR is clear: when incremental improvements yield diminishing returns, when workarounds outnumber standard procedures, or when customer complaints cluster around a specific process. These are symptoms of a process that has outgrown its original design. + +At scale, the most effective organisations alternate rhythmically between Kaizen (continuous, distributed improvement) and periodic BPR (strategic, concentrated redesign). Toyota calls this the difference between "maintaining standards" and "raising standards." + +--- + +## Output Template + +**Target Audience: Operations Team / VP Operations** + +```markdown +# Process Improvement Assessment +## [Process Name] -- [Date] + +### Current State +- Process owner: [Name/Role] +- Steps: [Number] +- Average cycle time: [Duration] +- Error/rework rate: [Percentage] +- Monthly cost: [Amount] +- Customer satisfaction with this process: [Score/Feedback] + +### Waste Analysis (Kaizen Lens) +| Waste Type | Present? | Specific Instance | Estimated Impact | +|------------|----------|-------------------|-----------------| +| Overproduction | [Y/N] | [Description] | [Time/cost] | +| Waiting | [Y/N] | [Description] | [Time/cost] | +| Transport | [Y/N] | [Description] | [Time/cost] | +| Overprocessing | [Y/N] | [Description] | [Time/cost] | +| Inventory | [Y/N] | [Description] | [Time/cost] | +| Motion | [Y/N] | [Description] | [Time/cost] | +| Defects | [Y/N] | [Description] | [Time/cost] | + +### Recommendation: Kaizen or BPR? +- [ ] **Kaizen** -- Process is fundamentally sound; incremental improvement is appropriate +- [ ] **BPR** -- Process architecture is broken; radical redesign is required + +### Improvement Plan +| # | Change Description | Type (Kaizen/BPR) | Owner | Timeline | Expected Impact | +|---|-------------------|-------------------|-------|----------|-----------------| +| 1 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | +| 2 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | +| 3 | [Change] | [Type] | [Owner] | [Date] | [Metric improvement] | + +### Success Metrics +- Target cycle time: [Duration] (from [Current]) +- Target error rate: [%] (from [Current]) +- Target cost: [Amount] (from [Current]) +- Review date: [Date] +``` + +--- + +## Related Skills + +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Process improvement requires understanding how changes in one process affect connected systems; Systems Thinking prevents optimising one process at the expense of others. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Provides the strategic context for deciding which processes to improve and how to measure the impact across financial, customer, internal, and learning dimensions. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- BPR's radical redesign is itself a major change initiative that benefits from Kotter's eight-step framework for building urgency, coalition, and sustainable adoption. +- **[Appreciative Inquiry](../../content/skills/frameworks/appreciative-inquiry.md)** -- Offers the strengths-based counterpart to Kaizen's waste-elimination focus; together they provide a complete improvement methodology that amplifies what works while removing what does not. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- Continuous improvement is a Quadrant II activity that the Eisenhower Matrix helps protect from the constant pull of urgent operational demands. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- Provides the structured problem-definition methodology needed before a Kaizen cycle or BPR initiative can begin effectively. diff --git a/plugins/foreman/skills/kotter-change-model/SKILL.md b/plugins/foreman/skills/kotter-change-model/SKILL.md deleted file mode 120000 index 73eeec8..0000000 --- a/plugins/foreman/skills/kotter-change-model/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/kotter-change-model.md \ No newline at end of file diff --git a/plugins/foreman/skills/kotter-change-model/SKILL.md b/plugins/foreman/skills/kotter-change-model/SKILL.md new file mode 100644 index 0000000..5a42cc4 --- /dev/null +++ b/plugins/foreman/skills/kotter-change-model/SKILL.md @@ -0,0 +1,187 @@ +--- +name: "kotter-change-model" +description: "Guides organizational change initiatives using Kotter's eight-step + model: creating urgency, forming a guiding coalition, developing a vision, + communicating the vision, empowering action, generating short-term wins, + consolidating gains, and anchoring changes in culture. Use when leading a + strategic pivot, implementing organizational restructuring, driving cultural + transformation, managing post-acquisition integration, rolling out new + processes at scale, or diagnosing why previous change efforts have failed." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - change-management + - leadership + - transformation + - organizational-culture + - implementation +related_skills: + - ambidexterity + - covey-seven-habits + - tuckman-team-stages + - balanced-scorecard +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Kotter's 8-Step Change Model + +Seventy percent of organizational change initiatives fail. That statistic, drawn from research spanning three decades and cited by John Kotter himself, should give pause to any founder contemplating a significant strategic shift. The failure rate is not declining. If anything, the acceleration of technological change has increased the number of transformation attempts without improving the success rate. Kotter, a Harvard Business School professor who spent his career studying why organizations resist change, distilled his findings into an eight-step model first published in his 1996 book *Leading Change*. The model remains the most widely taught change management framework in business schools worldwide -- not because it is novel, but because it is precise about where and why change efforts derail. + +--- + +## The Framework + +### The Eight Steps + +Kotter's model is sequential by design. Skipping steps or reordering them is the primary cause of failure. Each step builds the foundation for the next. + +**Step 1 -- Create a Sense of Urgency** +Change begins only when enough people believe the status quo is more dangerous than the unknown. Kotter found that 50% of transformations fail at this first step because leaders underestimate the complacency embedded in successful organizations. The urgency must be authentic, not manufactured panic. Data-driven evidence of market shifts, competitive threats, or internal decay is more persuasive than executive rhetoric. + +**Step 2 -- Build a Guiding Coalition** +No single leader can drive change alone. Assemble a coalition of individuals with enough power, expertise, credibility, and leadership to sustain the effort. The coalition must include people from across the organization -- not just senior management. Kotter emphasizes that coalitions need leadership skills (setting direction, motivating) in addition to management skills (planning, budgeting, organizing). + +**Step 3 -- Form a Strategic Vision and Initiatives** +The vision must be clear enough to explain in five minutes and compelling enough to generate genuine enthusiasm. Vague aspirations ("become more innovative") fail. Concrete, vivid descriptions of the future state succeed. The vision must be supported by a set of strategic initiatives -- specific actions that will move the organization from its current state to the envisioned one. + +**Step 4 -- Enlist a Volunteer Army** +Communicate the vision relentlessly and through every available channel. Kotter's research shows that most companies under-communicate their change vision by a factor of 10. Communication must be two-directional: not just broadcasting the vision but listening to concerns, addressing skepticism, and incorporating feedback. The goal is not compliance but genuine buy-in from a critical mass of the organization. + +**Step 5 -- Enable Action by Removing Barriers** +Structural and cultural barriers will impede even the most motivated change agents. These barriers include: organizational structures that undermine the vision, skills deficits, systems and processes designed for the old way, and supervisors who resist the change. Leaders must actively identify and dismantle these obstacles. + +**Step 6 -- Generate Short-Term Wins** +Transformation takes years, but people need evidence of progress within months. Plan for visible, unambiguous improvements that validate the change direction. Short-term wins serve three purposes: they reward the effort of change agents, they undermine cynics and resisters, and they build momentum for the harder phases ahead. + +**Step 7 -- Sustain Acceleration** +After initial wins, the danger is declaring victory prematurely. Kotter warns that the forces of tradition are powerful enough to reassert themselves within two to three years if the pressure relents. Use the credibility generated by short-term wins to tackle bigger, deeper changes -- systems, structures, and policies that remain aligned with the old way. + +**Step 8 -- Institute Change** +Anchor the new approaches in the organizational culture. Culture changes last, not first. New behaviors must be reinforced through promotion criteria, performance metrics, onboarding processes, and leadership modeling. Only when "this is how we do things here" reflects the new reality is the change complete. + +### The Two Accelerators + +In his later work, Kotter updated the model with two structural observations: + +- **The Dual Operating System**: Large organizations need both a management-driven hierarchy (for reliability) and a network-like structure (for agility and change). Change cannot be driven through hierarchy alone. +- **Continuous vs. Episodic Change**: The original model assumed discrete change events. Modern organizations face continuous change, requiring the eight steps to operate as an ongoing capability rather than a one-time program. + +--- + +## Prompts + +**Prompt 1 -- Change Readiness Assessment:** +> Assess my organization's readiness for a specific change initiative. The change is: [describe the change -- e.g., pivoting product focus, restructuring teams, adopting new technology, entering a new market]. My company is [describe: sector, stage, size, culture]. Evaluate readiness across Kotter's eight steps: Where are we strong? Where are we vulnerable? What is the most likely point of failure? Provide a readiness score (1-5) for each step and an overall assessment. + +**Prompt 2 -- Urgency Case Builder:** +> Help me build a compelling case for urgency around [describe the change needed]. My audience is [describe: team, board, investors, entire company]. What data, trends, competitive intelligence, or customer evidence would make the status quo feel untenable? Draft a 3-minute narrative I can deliver that creates genuine urgency without inducing panic. Include specific data points I should research and incorporate. + +**Prompt 3 -- Guiding Coalition Design:** +> I need to assemble a guiding coalition for [describe the change]. My organization has [describe key people, teams, and power dynamics]. Who should be in the coalition and why? What roles are essential -- formal authority, technical expertise, informal credibility, change energy? Identify potential resisters and how to either include them or neutralize their opposition. Map the coalition on a 2x2 of influence vs. commitment. + +**Prompt 4 -- Short-Term Win Planning:** +> My change initiative is [describe]. We are currently between Steps 4 and 5 of Kotter's model. Help me identify 3-5 short-term wins I can engineer within the next 60-90 days. Each win must be: visible to the broader organization, clearly connected to the change vision, and achievable with resources we already have. For each win, specify what success looks like, who owns it, and how we will communicate it. + +**Prompt 5 -- Culture Anchoring Plan:** +> We have been implementing [describe the change] for [timeframe] and are approaching Step 8 -- anchoring in culture. Help me design a plan to make this change permanent. What systems, processes, incentives, and rituals need to change? What stories should we tell and celebrate? What hiring and promotion criteria should reflect the new culture? What are the warning signs that the old culture is reasserting itself? + +--- + +## Use Cases + +**Growth-Stage Startup Transitioning from Founder-Led Sales to a Sales Organization** +A $5M ARR B2B startup has relied entirely on the founder for sales. With 40 employees and Series A funding, the company must build a repeatable sales process. The founder uses Kotter's model: establishing urgency by showing the team that current growth rates are unsustainable without a sales organization; building a guiding coalition that includes the new VP of Sales, two senior engineers (to ensure product-sales alignment), and the head of customer success; articulating a vision where every team member understands the ideal customer profile; enlisting the team through transparent communication about why this matters; removing barriers by investing in CRM and sales enablement tools; generating a short-term win when the first non-founder deal closes within 45 days; sustaining acceleration by iterating the sales playbook based on data; and anchoring the change by making quota attainment part of the company's cultural identity. + +**Scale-Stage Company Migrating to a New Technology Platform** +A 500-person company must migrate from a legacy monolith to microservices architecture -- a two-year effort that will disrupt every engineering team. The CTO applies the model rigorously: urgency is established through data showing that deployment speed has declined 40% year-over-year and incident rates have doubled; the guiding coalition includes both senior architects and respected individual contributors who can influence their peers; the vision describes a world where teams ship independently multiple times per day; barriers are removed by funding a dedicated platform team and modernizing CI/CD; short-term wins come from migrating one high-visibility service that immediately demonstrates faster deployments; and the change is anchored when new engineers are onboarded into the microservices paradigm as the default. + +--- + +## Anti-Patterns + +1. **Declaring victory after Step 6.** The most seductive and common mistake. Early wins feel so good that leaders announce the transformation is complete. The remaining two steps -- sustaining acceleration and anchoring in culture -- are where permanent change actually happens. Premature celebration allows the old culture to reassert itself quietly. + +2. **Skipping Step 1 because leadership is already convinced.** The fact that the CEO believes change is necessary does not mean the organization does. Urgency must be felt broadly, not just at the top. Leaders who skip urgency-building find themselves pushing change onto resistant teams rather than leading willing participants. + +3. **Building a coalition of loyalists rather than influencers.** The guiding coalition needs credibility and diverse organizational reach, not just people who agree with the leader. Including a respected skeptic who becomes convinced is more powerful than including ten enthusiastic yes-sayers. + +4. **Communicating the vision once and expecting it to stick.** Kotter's research indicates that change visions are under-communicated by a factor of 10 to 100. A single all-hands meeting, email, or Slack message is laughably insufficient. The vision must be repeated, demonstrated, and referenced in every relevant context for months. + +5. **Attempting culture change first.** Culture is the output of sustained behavioral change, not the input. Leaders who begin with "we need to change our culture" have the causality backwards. Change the behaviors, systems, and incentives; culture follows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-driven pivots | At this stage, the "organization" is small enough that Kotter's model can be compressed. Urgency and vision often reside in the founder. The key challenge is Step 2 -- ensuring the small team genuinely buys in rather than merely complying. Short-term wins must come within weeks, not months. | +| Growth | Building organizational capabilities | The most common inflection point: transitioning from ad-hoc processes to scalable systems. Every element of the model matters. The guiding coalition must extend beyond the founding team. Communication becomes harder as the company grows past Dunbar's number. | +| Scale | Enterprise transformation | Full Kotter model deployed with formal program management. Change initiatives may run in parallel across divisions. The dual operating system concept becomes essential: hierarchy for stability, networks for change. Board engagement is critical at Steps 1-3. | + +--- + +## Output Template + +```markdown +# Change Initiative Plan (Kotter 8-Step) + +**Initiative:** [Name of the change] +**Sponsor:** [Executive owner] +**Timeline:** [Expected duration] +**Date:** [Date] + +## Step 1: Urgency +**Current urgency level:** [Low / Moderate / High] +**Key evidence for change:** +- [Data point or trend] +- [Competitive threat or opportunity] +- [Internal metric showing need] + +## Step 2: Guiding Coalition +| Name | Role | Why Included | Commitment Level | +|------|------|-------------|-----------------| +| [Name] | [Role] | [Reason] | [Champion/Supporter/Neutral/Skeptic] | + +## Step 3: Vision +**Vision statement (< 50 words):** [Statement] +**Strategic initiatives:** +1. [Initiative] +2. [Initiative] + +## Step 4: Communication Plan +- [Channel and frequency] +- [Key messages] + +## Step 5: Barriers to Remove +- [Barrier] → [Action to remove] + +## Step 6: Short-Term Wins (60-90 days) +1. [Win] -- Owner: [Name] -- Success criteria: [Criteria] +2. [Win] -- Owner: [Name] -- Success criteria: [Criteria] + +## Step 7: Acceleration Actions +- [Deeper change enabled by early wins] + +## Step 8: Anchoring Mechanisms +- [System/process/incentive changes to make it permanent] +``` + +--- + +## Related Skills + +- **[Organizational Ambidexterity](../../content/skills/frameworks/ambidexterity.md)** -- Building an ambidextrous organization is itself a major change initiative that benefits from Kotter's structured eight-step approach. +- **[Organisational Culture](../../content/skills/frameworks/organisational-culture.md)** -- Step 8 (anchoring in culture) requires deep understanding of Schein's cultural layers to ensure new behaviours become embedded rather than superficially adopted. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Teams undergoing change cycle through Forming, Storming, Norming, and Performing; understanding these dynamics helps calibrate the pace and communication of each Kotter step. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Provides the measurement framework that makes short-term wins visible (Step 6) and sustains accountability through the later steps of the change process. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- Provides the leadership behaviours and communication practices needed to guide people through each of Kotter's eight steps effectively. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Steps 3 and 4 (vision formation and communication) are fundamentally storytelling challenges where narrative skill determines whether the vision inspires action or falls flat. diff --git a/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md b/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md deleted file mode 120000 index 187e5e2..0000000 --- a/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/leader-resilience-and-wellbeing.md \ No newline at end of file diff --git a/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md b/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md new file mode 100644 index 0000000..5562c52 --- /dev/null +++ b/plugins/foreman/skills/leader-resilience-and-wellbeing/SKILL.md @@ -0,0 +1,220 @@ +--- +name: "leader-resilience-and-wellbeing" +description: "Addresses the physical, emotional, and psychological dimensions of leader sustainability, including sleep, stress management, mindfulness, anxiety channelling, emotional courage, vulnerability, and recovery practices. Use when a leader shows signs of burnout, when sleep deprivation affects judgement and team morale, when overwhelm becomes chronic rather than episodic, when a leader confuses endurance with strength, or when the pressure to appear invulnerable is eroding authentic connection with the team." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - resilience + - wellbeing + - sleep + - stress + - mindfulness + - anxiety + - vulnerability + - courage + - burnout + - self-care +related_skills: + - emotional-intelligence + - psychological-safety + - flow-state + - focus-and-priority-management + - learning-agility +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Leader Resilience and Wellbeing + +Here is a paradox worth sitting with: the leaders who appear most unbreakable are frequently the most fragile. They have optimised for the projection of strength -- the 5 a.m. starts, the unanswered personal calls, the performative stoic -- while systematically depleting the resources that make genuine strength possible. Sleep, recovery, emotional honesty, and the courage to say "I do not know" are not indulgences that leaders earn after they succeed. They are the infrastructure on which sustainable leadership is built. Neglect them long enough, and the collapse -- when it comes -- is rarely graceful. + +Christopher Barnes's research at Indiana University and the University of Washington delivers the data point that should end every macho leadership cliche about sleep deprivation: employees of sleep-deprived leaders are less engaged and behave less ethically. The leader's fatigue is not a personal sacrifice nobly borne. It is an organisational cost distributed across every person they lead. + +--- + +## The Practice + +### Sleep as Leadership Infrastructure + +Barnes is precise about the mechanism. Sleep deprivation impairs judgement, self-control, and creativity. It increases impatience, irritability, and antagonism. And leaders are reliably oblivious to these effects in themselves -- a phenomenon known as the "sleep debt blind spot." The person least qualified to assess whether they are too tired to lead is the tired leader. + +Three actionable sleep protocols: + +**1. Eliminate sleep-deprivation signalling.** Avoid bragging about how little you slept. Do not send emails at 3 a.m. (use delayed delivery). Do not hold up all-nighters as exemplary. Your team reads your behaviour as a cue for what is expected. + +**2. Protect bad-sleep days.** When sleep was poor, shift the day's work toward routine tasks that do not require creativity. Avoid complex decisions. Ask a colleague to review important documents. A 20-minute nap -- research from the University of Dusseldorf shows even eight minutes improves memory -- can partially restore cognitive function. + +**3. Treat sleep as a strategic investment, not a personal luxury.** The leader who sleeps seven hours and makes one clear-headed decision is more valuable than the leader who sleeps four hours and makes three impaired ones. + +### Managing Overwhelm + +Alice Boyes identifies five strategies for the leader whose to-do list has become a source of chronic anxiety: + +- **Practice acceptance.** Compassionate self-talk: "I can only focus on the thing I am doing right now" or "I would prefer to do more in a day, but I will accept my realistic limits." +- **Question expectations.** Leaders often invent urgency. Before treating a request as immediate, ask: "When do you actually need this?" The real deadline may be far more generous than the assumed one. +- **Track time.** A week of honest time-logging reveals where time actually goes versus where it feels like it goes. The data often contradicts the anxiety. +- **Change behaviour first, then feelings.** Ask: "If I were more relaxed about my workload, how would I act?" Then act that way. Behavioural change often precedes emotional change, not the other way around. +- **Identify microstressors.** Rob Cross and Karen Dillon's research on microstress reveals that small, individually trivial setbacks -- a colleague's missed deadline adding 30 minutes to your evening, a process glitch requiring an extra email chain -- accumulate into significant physiological stress responses. The first step is naming them. The second is systematically eliminating the structural ones. + +### Anxiety as Fuel + +Morra Aarons-Mele reframes anxiety not as a weakness to be eliminated but as a signal to be channelled. Anxiety can sharpen threat detection and increase comfort with uncomfortable feelings -- both useful leadership capacities. The practice: + +1. **Notice.** Observe physical manifestations (stomach churning, chest tightness) and emotional ones (feeling overwhelmed or panicked). +2. **Journal.** Track anxiety patterns over time to identify recurring triggers and distinguish productive anxiety (this situation requires my attention) from destructive anxiety (this rumination is consuming energy with no output). +3. **Pause, then choose.** The gap between noticing anxiety and acting on it is where leadership happens. In that gap, the leader decides whether to be driven by the anxiety or to use it as information. + +### Rumination: Breaking the Loop + +Alice Boyes addresses the specific trap of post-mistake rumination -- replaying errors for days or weeks: + +- Identify rumination triggers: certain people, projects, or decision types that provoke overthinking. +- Relabel: "I feel inadequate" rather than "I am inadequate" creates distance between self and emotional reaction. +- Distract deliberately: a walk, meditation, or even a mundane task can interrupt the cognitive loop. + +### Mindfulness as Structure, Not Sentiment + +Matthias Birk's guidance strips mindfulness of its mystique. Schedule it at a non-negotiable time. Block it on the calendar. Tell the team, so interruptions are minimised. Join a group for accountability. The barriers to mindfulness are almost never philosophical; they are logistical. + +### Emotional Courage + +Peter Bregman defines emotional courage as the capacity to do uncomfortable things -- raising a difficult issue, delivering unwanted feedback, admitting uncertainty. The development method is progressive exposure, starting in low-stakes environments. Practise being direct with a customer-service representative about a billing error. Notice the impulse to retreat or escalate. Resist it. Build the muscle incrementally until directness in high-stakes leadership conversations feels, if not comfortable, at least familiar. + +Maya Angelou's formulation is instructive: "One isn't born with courage. One develops it by doing small courageous things." The five-pound bag of rice before the hundred-pound bag. + +### Vulnerability as Strength + +Peter Bregman's complementary insight: the best managers acknowledge their weaknesses openly. The instinct to show only one's best self is understandable and counterproductive. Employees connect with leaders who are human, not with leaders who are performing invulnerability. "You aren't weak; you have weaknesses. There is a difference." + +James Detert's research adds nuance: taking a stand within an organisation does not require martyrdom. Respected insiders who act on conviction -- pushing for strategic risks, challenging unfair policies, speaking against unethical behaviour -- often see their status rise when they manage the process well. Courage is not the absence of career risk; it is the calculation that some risks are worth taking. + +### Hobbies and the Hedonistic Treadmill + +Research from Vrije Universiteit Amsterdam shows that top leaders who invest substantially in hobbies, personal interests, and volunteer commitments are not escaping work -- they are building the psychological resources that make sustained work possible. Hobbies provide lessons in humility (the CEO who is a beginner at pottery), strengthen authentic identity (the person exists beyond the title), and create the cognitive detachment that prevents work from becoming all-consuming. + +Ron Carucci warns against the hedonistic treadmill: the cycle of pursuing success for the dopamine hit, watching it fade, and pursuing more. The antidote is not less ambition but a deliberate pursuit of meaningful satisfaction alongside achievement. + +### Life Beyond the Role + +David Lancefield's warning is stark: a leadership role will consume your entire life if you allow it. By the time you notice that personal relationships have atrophied and self-care has vanished, recovery is expensive. The preventive measure is simple, difficult, and non-negotiable: decide what matters outside of work and protect it with the same ferocity you protect your most important business commitments. + +--- + +## Prompts + +**Prompt 1 -- Resilience Audit:** +> Assess my current resilience across these dimensions based on the following self-report: sleep pattern [describe], exercise frequency [describe], relationship with anxiety [describe], hobby/non-work investment [describe], vulnerability comfort level [describe], last vacation [date]. For each dimension, rate me as thriving/managing/depleting and recommend one specific change I can implement this week. + +**Prompt 2 -- Microstress Mapping:** +> Here are the small, recurring frustrations in my work week: [list 5-10 microstressors]. Categorise each as structural (fixable by changing a process), relational (fixable by a conversation), or inherent (must be managed, not eliminated). For the structural ones, propose a specific fix. For the relational ones, draft the conversation. For the inherent ones, suggest a coping strategy. + +**Prompt 3 -- Anxiety Channel Plan:** +> I experience significant anxiety about [describe situation or pattern]. Using Aarons-Mele's framework, help me: (a) identify whether this anxiety is productive (contains useful information) or destructive (consuming energy without output), (b) design a journaling protocol to track its patterns, and (c) develop a pause-and-choose routine I can deploy when the anxiety peaks. + +**Prompt 4 -- Vulnerability Script:** +> I need to acknowledge a mistake or limitation to my team: [describe the situation]. Draft what I should say that: (a) is honest without being self-flagellating, (b) maintains authority while demonstrating humanity, (c) models the vulnerability I want the team to practise, and (d) focuses forward on what changes as a result. + +--- + +## Use Cases + +**Validation-stage founder running on fumes** + +A solo founder has averaged five hours of sleep for three months, fuelled by the conviction that every waking hour invested now will pay off later. Investor meetings are going poorly -- the founder is irritable, unfocused, and unable to think creatively during Q&A. A mentor points to Barnes's research: the sleep deficit is not just a personal health issue; it is the reason the pitches are failing. The founder implements a non-negotiable seven-hour sleep minimum, shifts investor meetings to mornings (peak cognitive performance), and within two weeks reports that preparation time has halved because the work product is clearer on the first attempt. + +**Growth-stage leader hiding behind invulnerability** + +A VP of product has never once admitted uncertainty to the team. They interpret every setback as a personal failure, ruminate for days after mistakes, and have developed a reputation for emotional unavailability. A coaching engagement introduces Bregman's progressive exposure method: the VP practises directness in low-stakes situations (returning a faulty product, asking for a table change at a restaurant) and gradually builds toward admitting, in a team meeting, "I made a wrong call on the Q2 roadmap, and here is what I learned from it." The team's response -- relief, increased trust, and a measurable uptick in their own candour -- surprises the VP. + +**Scale-stage executive approaching burnout** + +A chief revenue officer has not taken a vacation in 18 months, exercises sporadically, and has replaced hobbies with "networking dinners." A microstress audit reveals 14 recurring small stressors, eight of which are structural (fixable by process changes or delegation). Eliminating those eight recovers roughly six hours per week. The recovered time is deliberately allocated: three hours to exercise, two to a pottery class (the COO had been a ceramicist before the career consumed everything), and one to an unstructured lunch with no agenda. Within three months, both the executive's engagement scores and their direct reports' engagement scores improve. + +--- + +## Anti-Patterns + +**1. Treating resilience as endurance.** The leader who "pushes through" chronic exhaustion is not resilient; they are depleting a finite resource. Genuine resilience includes knowing when to stop, recover, and return at full capacity. + +**2. Weaponising vulnerability.** Sharing weaknesses to manipulate sympathy, avoid accountability, or create an emotional debt is not vulnerability -- it is manipulation. Authentic vulnerability serves the team's trust, not the leader's emotional needs. + +**3. Mindfulness as performance.** Announcing a meditation practice, attending a retreat, and then returning to exactly the same stress-producing behaviours treats mindfulness as a credential rather than a practice. The measure of mindfulness is changed behaviour, not accumulated hours of sitting. + +**4. The "I'll rest when I succeed" fallacy.** Success does not produce rest; it produces new demands. The leader who defers recovery until after the next milestone, the next funding round, the next quarter will never rest, because there is always another next. + +**5. Ignoring the team cost of personal depletion.** A depleted leader does not suffer alone. Barnes's research is unambiguous: the leader's sleep, stress, and emotional state propagate to the team. Self-care is not selfish; it is a leadership responsibility. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Sleep discipline, founder stamina | Survival instinct overrides recovery; the founder must deliberately counter this | +| Early Traction | Stress management, boundary setting | First employees amplify the founder's habits; bad patterns scale fast | +| Growth | Emotional courage, vulnerability modelling | The leader's emotional range sets the ceiling for the team's psychological safety | +| Scale | Systemic wellbeing, vacation culture, burnout prevention | Resilience becomes an organisational design problem, not just an individual one | + +At validation, the primary threat is the founder's own mythology. The startup ecosystem glorifies sleep deprivation, relentless hustle, and the sacrifice of everything personal. The founder who internalises this mythology burns out before the company reaches product-market fit. The counternarrative -- that rest produces better decisions, which produce better outcomes, which produce faster progress -- is supported by the data but runs against the culture. + +At scale, individual resilience practices are necessary but insufficient. The organisation must build resilience into its architecture: mandatory minimum vacation policies, manager training on burnout recognition, workload audits, and a culture that treats visible rest as a sign of competence rather than a sign of insufficient commitment. + +--- + +## Output Template + +```markdown +# Leader Resilience Assessment -- [Name] + +**Date:** [Date] +**Assessed by:** [Self / Coach / Peer] + +## Dimension Ratings + +| Dimension | Current State | Evidence | Risk Level | One-Week Action | +|-----------|--------------|----------|------------|----------------| +| Sleep | [Thriving/Managing/Depleting] | [Hours, quality, consistency] | [High/Medium/Low] | [Specific change] | +| Physical activity | [Thriving/Managing/Depleting] | [Frequency, type] | [High/Medium/Low] | [Specific change] | +| Stress management | [Thriving/Managing/Depleting] | [Coping methods used] | [High/Medium/Low] | [Specific change] | +| Anxiety relationship | [Thriving/Managing/Depleting] | [Productive vs. destructive ratio] | [High/Medium/Low] | [Specific change] | +| Emotional courage | [Thriving/Managing/Depleting] | [Recent examples] | [High/Medium/Low] | [Specific change] | +| Vulnerability practice | [Thriving/Managing/Depleting] | [Recent examples] | [High/Medium/Low] | [Specific change] | +| Non-work investment | [Thriving/Managing/Depleting] | [Hobbies, relationships, leisure] | [High/Medium/Low] | [Specific change] | + +## Microstress Inventory + +| Stressor | Category | Frequency | Fix / Cope Strategy | +|----------|----------|-----------|-------------------| +| [Stressor] | [Structural/Relational/Inherent] | [Daily/Weekly/Occasional] | [Specific action] | + +## Recovery Plan (Next 30 Days) +- **Sleep:** [Target hours, bedtime routine, screen curfew] +- **Exercise:** [Frequency, type, scheduled times] +- **Mindfulness:** [Method, duration, scheduled time] +- **Non-work:** [Activity, frequency, protected time] +- **Boundary:** [One boundary to set this month] + +## Team Impact Check +- Am I modelling the behaviours I expect from my team? +- What signals am I sending about work-life boundaries? +- When did I last take a visible day off? +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-regulation and self-awareness, core EQ competencies, are the psychological muscles that resilience practices strengthen. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- A leader's willingness to be vulnerable directly builds the team's psychological safety; the two are inseparable. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Flow requires a baseline of cognitive and emotional health; depleted leaders cannot achieve or sustain it. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Poor time management is both a cause and a symptom of burnout; the two skills reinforce each other. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- The vulnerability practice described here -- sharing weakness appropriately -- requires the progressive courage-building techniques from this companion skill. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- Provides the philosophical foundation for endurance that complements the practical sleep, stress, and recovery protocols described here. diff --git a/plugins/foreman/skills/leader-self-reflection/SKILL.md b/plugins/foreman/skills/leader-self-reflection/SKILL.md deleted file mode 120000 index be969ea..0000000 --- a/plugins/foreman/skills/leader-self-reflection/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/leader-self-reflection.md \ No newline at end of file diff --git a/plugins/foreman/skills/leader-self-reflection/SKILL.md b/plugins/foreman/skills/leader-self-reflection/SKILL.md new file mode 100644 index 0000000..5d924ae --- /dev/null +++ b/plugins/foreman/skills/leader-self-reflection/SKILL.md @@ -0,0 +1,214 @@ +--- +name: "leader-self-reflection" +description: "Establishes a structured introspection practice for leaders through recurring self-diagnostic questions, performance pattern analysis, and emotional impact awareness. Covers seven reflection domains (vision, time, feedback given, feedback received, strengths and weaknesses, authenticity, and pressure behaviour), techniques for joint analysis of failures and successes, and methods for surfacing blind spots that others will not voluntarily reveal. Use when a leader feels stuck in repetitive patterns, when self-awareness gaps are damaging team trust, when preparing for a leadership transition, or when establishing a personal development discipline." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - self-awareness + - introspection + - feedback + - emotional-intelligence + - personal-development + - strengths + - weaknesses + - reflection +related_skills: + - leadership-style-adaptation + - leadership-voice-and-presence + - senior-leadership-transition + - employee-engagement-retention + - johari-window + - emotional-intelligence + - covey-seven-habits +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Leader Self-Reflection + +A leader who does not reflect does not learn. They accumulate years of experience and repeat the first year twenty times. They confuse tenure with development, pattern recognition with wisdom, and the absence of complaints with the presence of trust. The most dangerous leader in any organisation is not the one who makes mistakes -- everyone does -- but the one who lacks the self-awareness to see them, the humility to examine them, and the discipline to build a practice that prevents their repetition. + +Self-reflection is not meditation, journaling for its own sake, or the vague aspiration to "be more mindful." It is a structured diagnostic process -- a set of specific questions, applied with regularity, that surfaces the gap between how you believe you lead and how you actually do. Peter Drucker, Robert Kaplan, and Daniel Goleman converge on the same conclusion from different angles: the leaders who perform best are those who have built systematic methods for examining their own behaviour, not occasionally during a retreat, but as a recurring discipline woven into the rhythm of work. + +--- + +## The Practice + +### The Seven Reflection Domains + +Each domain addresses a different facet of leadership effectiveness. Neglecting any one of them creates a blind spot that compounds over time. + +**1. Vision Clarity** +*The question: How often and how well do you communicate a vision and priorities for your team?* + +In the turbulence of daily operations, it is easy to stop articulating the bigger picture. But people cannot focus their efforts -- or sustain motivation -- if they do not know where they are going and why. The reflection discipline: at the end of each week, ask whether your team could articulate your three top priorities. If you doubt they could, the problem is not their attention; it is your communication. + +**2. Time Alignment** +*The question: How are you spending your time, and does it align with your stated priorities?* + +Leaders set the pace for their teams. If your calendar does not reflect your priorities, you are signalling -- loudly -- that those priorities are negotiable. The reflection discipline: once per month, audit your calendar against your strategic goals. Identify the activities that consumed time without advancing priorities, and ask: which of these could be delegated, eliminated, or compressed? + +**3. Feedback Given** +*The question: Do you give timely, direct, constructive feedback?* + +Teams want to know how to grow, and they need their leader to tell them. Feedback hoarded until annual reviews arrives too late to change behaviour and too infrequently to demonstrate investment. The reflection discipline: at the end of each week, count the pieces of substantive feedback you delivered. If the number is zero, the week was a missed development opportunity for everyone on your team. + +**4. Feedback Received** +*The question: Do you have people who will tell you things you need to hear?* + +Your team is better positioned than your boss to assess your daily impact. But employees are often scared to deliver hard truths upward -- they fear consequences, doubt their standing, or simply do not know how to raise the topic. You cannot rely on spontaneous honesty. The reflection discipline: make a concerted, persistent effort to ask what you could do better, and then visibly act on what you hear. If no one is telling you anything difficult, you have a trust problem, not a performance one. + +**5. Strengths and Weaknesses** +*The question: Can you write down your two or three greatest strengths and your two or three most significant weaknesses?* + +This exercise sounds elementary. It is not. An honest inventory requires input from people who will deliver unvarnished truth -- not colleagues who will soften the assessment out of politeness or politics. The reflection discipline: annually solicit specific feedback from people at multiple levels and outside your immediate circle. Write the inventory down. Compare it to last year's. Note what has changed and what has stubbornly persisted. + +**6. Authenticity** +*The question: Does your leadership style reflect who you really are?* + +Modelling your style on admired leaders is natural, but ultimately your approach must be uniquely and genuinely yours. The reflection discipline: periodically ask whether the way you lead would feel recognisable to the people who knew you before you had a title. If the answer is no, examine which adaptations serve the role and which serve the performance of a role you are playing rather than inhabiting. + +**7. Pressure Behaviour** +*The question: How do you behave under pressure, and does it align with your values?* + +During a crisis, every eye is on the leader. Calm or harried. Accountable or blaming. Supportive or finger-pointing. The person you are under stress is the person your team remembers. The reflection discipline: after every high-pressure episode, conduct a brief retrospective -- not of what happened, but of how you behaved. Did your actions match your stated values? If not, identify the specific moment where they diverged and the trigger that caused it. + +### Analysing Failures and Successes Together + +The instinct after a failure is to search for root causes and correct them. This is necessary but insufficient. Some patterns that appear in failures also appear in successes -- and correcting them would remove a capability rather than fix a deficiency. + +Before investing in new solutions, tools, or training programmes based on a failure analysis, examine whether the "failing" factor is also present in your successes. If employees who fell short on a project were not using a particular tool, check whether successful employees were using it either. The discipline of paired analysis prevents overcorrection and preserves what works. + +### How You Perform Best + +Self-reflection includes understanding your operating conditions -- the circumstances under which you produce your strongest work. Do you absorb information by reading or listening? Do you learn by writing, talking, watching demonstrations, or hands-on experimentation? Do you prefer solitary concentration or collaborative energy? Do you produce results as a decision-maker or as an advisor to decision-makers? Do you thrive under pressure or require structure? + +These preferences are not fixed. They shift as careers evolve and contexts change. Revisiting them periodically prevents the trap of organising your work around the preferences of the person you were five years ago rather than the person you are now. + +### Your Emotional Impact + +A leader's mood has an outsized effect on team performance. But leaders routinely underestimate their emotional footprint because people do not volunteer the truth about it. They are afraid, or they think it is not their place, or they do not realise that the leader's emotional style is the elephant in the room. + +The reflection discipline: create structured channels for emotional impact feedback. This might be an anonymous pulse survey, a trusted peer who agrees to be candid, or an executive coach. The question is not "Am I a good leader?" but "What effect does my emotional state have on the people around me, and am I aware of it in real time?" + +--- + +## Prompts + +**Prompt 1 -- Seven-Domain Self-Assessment:** +> Guide me through a structured self-reflection across the seven domains (vision clarity, time alignment, feedback given, feedback received, strengths/weaknesses, authenticity, pressure behaviour). For each domain, ask me one diagnostic question, then assess my response for blind spots, self-serving narratives, and areas where I may be overestimating my effectiveness. Provide a candid assessment of which domains need immediate attention and a specific weekly practice for each. + +**Prompt 2 -- Failure-Success Paired Analysis:** +> I recently experienced a failure: [describe the project, outcome, and your initial diagnosis of what went wrong]. I also have a recent success: [describe the project and outcome]. Help me analyse both together. Identify factors present in the failure that are also present in the success. Challenge my initial diagnosis of the failure's root cause. Recommend corrections that address genuine deficiencies without eliminating capabilities that contributed to the success. + +**Prompt 3 -- Emotional Impact Audit:** +> Based on the following observations about how my team responds to me in different situations, assess my emotional impact as a leader. Situation 1: [describe your mood, your behaviour, and the team's response]. Situation 2: [describe]. Situation 3: [describe]. Identify patterns in how my emotional state affects team performance, creativity, and willingness to speak up. Recommend specific awareness practices and behavioural adjustments. + +**Prompt 4 -- Operating Conditions Map:** +> Help me map my optimal operating conditions as a leader. I will describe my preferences and patterns: [describe how you absorb information, whether you prefer solo or collaborative work, how you handle pressure, when you feel most productive, what drains you]. Assess whether my current role and schedule align with these conditions. Identify misalignments that may be reducing my effectiveness and suggest structural changes to my workday. + +--- + +## Use Cases + +**Growth-Stage CEO Who Cannot Understand Why Talented People Leave** +A CEO at an 80-person company has lost three director-level hires in eighteen months. Exit interviews are polite and uninformative. Applying the seven-domain reflection, the CEO discovers the issue in Domain 4 (feedback received): no one on the team tells the CEO hard truths. The CEO's emotional style -- intense, fast-paced, visibly frustrated by mistakes -- has created an environment where upward feedback feels unsafe. The intervention: the CEO hires an executive coach and commits to a weekly practice of explicitly asking one direct report for one piece of critical feedback, then responding with gratitude regardless of content. Over six months, the feedback channel opens. The next director-level hire stays. + +**Early-Traction Founder Repeating the Same Hiring Mistake** +A founder has hired and fired three head-of-sales candidates in two years. Each time, the diagnosis is "wrong person." The paired failure-success analysis reveals a different pattern: the same trait that the founder criticises in failed hires -- autonomous decision-making without seeking approval -- is the trait that makes the founder's successful engineering lead effective. The real issue is not the candidates; it is the founder's inconsistent tolerance for autonomy across functions. Sales requires independent judgment in the field. The founder's reflection leads to a recalibration: either grant the same autonomy to sales that engineering enjoys, or acknowledge that the founder is not ready to let go of that function. + +**Scale-Stage VP Whose Team Performs Well but Feels Miserable** +A VP of Operations delivers consistently strong results. Engagement scores in their division are the lowest in the company. The emotional impact audit reveals the cause: the VP operates with controlled intensity that reads as calm to superiors but as relentless pressure to subordinates. The VP's self-perception ("I am calm and focused") diverges sharply from the team's experience ("We never feel we can relax"). The reflection practice surfaces this gap through structured feedback from trusted peers and an anonymous pulse survey. The VP begins signalling recovery periods explicitly: "We hit the target. This week, we consolidate." + +--- + +## Anti-Patterns + +1. **The Journaling Illusion.** Confusing the act of writing about leadership with the act of examining it. Reflection without specific diagnostic questions produces autobiographical narrative, not insight. The seven domains provide structure that prevents self-reflection from becoming self-narration. + +2. **The Solo Practitioner.** Conducting all reflection internally without external input. Self-assessment without external validation is unreliable because the same blind spots that distort leadership also distort self-perception. The practice requires feedback from others to function. + +3. **The Retrospective Without Change.** Honest self-examination that produces awareness but not behavioural modification. Reflection that does not lead to a specific, trackable change in practice is intellectual exercise, not leadership development. + +4. **The Annual Retreat Approach.** Reserving reflection for offsites, year-end reviews, or vacation periods. The seven domains are weekly practices, not annual events. Patterns that take twelve months to surface take twelve months to correct. + +5. **The Selective Mirror.** Reflecting only on domains where you suspect you are strong, avoiding the domains where discomfort signals genuine deficiency. The domain you least want to examine is almost certainly the one that needs the most attention. + +6. **The Wrong Lesson.** Analysing failures in isolation and implementing corrections that inadvertently eliminate strengths. Paired analysis of failures and successes prevents this overcorrection, but only if conducted with discipline. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder self-awareness | At the earliest stage, the founder's self-knowledge is the organisation's competitive advantage or liability. Reflection focuses on operating conditions (when and how you work best) and authenticity (leading as yourself rather than performing a role you think investors expect). | +| Early Traction | Feedback infrastructure | As the first team forms, the leader must build the channels through which honest feedback flows. This is the moment to establish the norms -- asking for criticism, acting on it visibly -- that determine whether the organisation develops a culture of candour or one of comfortable silence. | +| Growth | Emotional impact at scale | The leader's mood now affects dozens or hundreds of people. Reflection must expand to include emotional impact awareness: how your state ripples through management layers and affects people you may rarely see directly. | +| Scale | Institutional reflection | At scale, self-reflection must be modelled and taught so that every manager practises it. The leader's personal discipline becomes the template for an organisational capability: structured introspection at every level. | + +--- + +## Output Template + +```markdown +# Leader Self-Reflection Assessment + +**Leader:** [Name] +**Date:** [Date] +**Review Period:** [Week/Month/Quarter] + +## Seven-Domain Diagnostic + +| Domain | Self-Assessment | External Feedback | Gap | Priority Action | +|--------|----------------|-------------------|-----|-----------------| +| Vision Clarity | [Assessment] | [Feedback] | [Gap] | [Action] | +| Time Alignment | [Assessment] | [Feedback] | [Gap] | [Action] | +| Feedback Given | [Assessment] | [Feedback] | [Gap] | [Action] | +| Feedback Received | [Assessment] | [Feedback] | [Gap] | [Action] | +| Strengths/Weaknesses | [Assessment] | [Feedback] | [Gap] | [Action] | +| Authenticity | [Assessment] | [Feedback] | [Gap] | [Action] | +| Pressure Behaviour | [Assessment] | [Feedback] | [Gap] | [Action] | + +## Paired Analysis: Recent Failure + Success +- **Failure:** [Description and initial root cause] +- **Success:** [Description] +- **Shared factors:** [Factors present in both] +- **True root cause:** [Revised diagnosis] +- **Corrective action:** [Action that preserves strengths] + +## Emotional Impact Snapshot +- **How I think I come across:** [Self-perception] +- **How others experience me:** [Feedback data] +- **Gap:** [Description] +- **Adjustment:** [Specific behavioural change] + +## Operating Conditions Review +- **Current alignment with optimal conditions:** [High/Medium/Low] +- **Misalignments identified:** [List] +- **Structural changes planned:** [List] + +## Commitments for Next Review Period +1. [Specific, measurable commitment] +2. [Specific, measurable commitment] +3. [Specific, measurable commitment] +``` + +--- + +## Related Skills + +- **[Johari Window](../../content/skills/frameworks/johari-window.md)** -- The theoretical model for understanding the gap between self-knowledge and others' perception; this skill provides the daily practice for expanding the "open" quadrant. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness and self-regulation are the EI competencies that self-reflection directly develops. +- **[Leadership Style Adaptation](../../content/skills/leadership/leadership-style-adaptation.md)** -- The mirror exercise in style adaptation is a focused application of the broader reflective practice developed here. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- The eight retention-destroying behaviours audit requires the honest self-examination that this skill builds as a daily discipline. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- The Stoic evening review is the philosophical ancestor of the structured reflection domains; both use recurring self-examination to surface patterns invisible in the moment. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- The paired failure-success analysis technique depends on the reflective discipline to distinguish genuine root causes from comfortable narratives. diff --git a/plugins/foreman/skills/leadership-pipeline/SKILL.md b/plugins/foreman/skills/leadership-pipeline/SKILL.md deleted file mode 120000 index b0c3d3a..0000000 --- a/plugins/foreman/skills/leadership-pipeline/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/leadership-pipeline.md \ No newline at end of file diff --git a/plugins/foreman/skills/leadership-pipeline/SKILL.md b/plugins/foreman/skills/leadership-pipeline/SKILL.md new file mode 100644 index 0000000..573a932 --- /dev/null +++ b/plugins/foreman/skills/leadership-pipeline/SKILL.md @@ -0,0 +1,197 @@ +--- +name: "leadership-pipeline" +description: "Diagnoses leadership development blockages using Charan's six passage transitions from individual contributor through enterprise manager. Evaluates skills, time allocation, and values shifts required at each leadership level. Use when founders cannot let go of operational tasks, managers are failing after promotion, succession planning is needed, or the organization is experiencing growth-stage leadership bottlenecks." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - growth + - scale +tags: + - leadership-development + - succession-planning + - organizational-design + - management + - talent + - scaling +related_skills: + - situational-leadership + - lewin-leadership-styles + - tuckman-team-stages + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Leadership Pipeline + +A pipe carries fluid from one point to another. When the pipe is clean and correctly sized, flow is smooth and invisible -- you forget the plumbing exists. When the pipe is clogged, cracked, or the wrong diameter, the entire system backs up. Pressure builds in the wrong places. Things that should move freely stagnate. Eventually, something bursts. + +Ram Charan, Stephen Drotter, and James Noel proposed in *The Leadership Pipeline* (2001) that organizations are precisely such plumbing systems, and leadership development is the flow. Each transition from individual contributor to first-line manager to functional leader to business leader to enterprise leader represents a distinct passage -- a joint in the pipe -- where the diameter changes, the flow dynamics shift, and blockages most commonly occur. The vast majority of leadership failures are not failures of character or intelligence. They are passage failures: someone operating with the skills, time allocation, and values of a previous level while occupying a role that demands an entirely different set. The pipe is clogged, and the organization suffers the consequences. + +--- + +## The Framework + +The Leadership Pipeline defines six leadership passages, each requiring a fundamental transformation in three dimensions: skills (what you do), time application (how you spend your hours), and work values (what you believe matters most). + +### The Six Passages + +``` +Passage 6: Enterprise Manager + ^ + | [Values shift: long-term, visionary, portfolio thinking] +Passage 5: Group Manager + ^ + | [Values shift: strategic portfolio, business evaluation] +Passage 4: Business Manager + ^ + | [Values shift: P&L ownership, cross-functional integration] +Passage 3: Manager of Managers + ^ + | [Values shift: developing leaders, strategic resource allocation] +Passage 2: Manager of Others + ^ + | [Values shift: getting work done through others, not doing it yourself] +Passage 1: Managing Self (Individual Contributor) + [Values: technical proficiency, personal productivity, reliability] +``` + +### Passage 1 to 2: From Managing Self to Managing Others + +This is the passage where the greatest volume of blockage occurs and where startup founders feel it most acutely. The skills required shift from technical execution to planning, delegating, coaching, and measuring the work of others. Time application moves from doing the work to ensuring others do it. The value transformation is the most wrenching: the new manager must stop valuing personal technical contribution as the primary measure of worth and start valuing the success of their team. + +The blockage symptom: the manager who still writes code, still closes deals, still designs the product -- because that is where their identity lives. Their reports wait for direction, receive little coaching, and eventually leave. + +### Passage 2 to 3: From Managing Others to Managing Managers + +The second passage requires selecting and developing first-line managers rather than individual contributors. The leader must learn to assess managerial capability (not just technical capability), allocate resources across teams, and think two levels down. Time shifts from direct supervision to strategic coordination. + +The blockage symptom: the manager of managers who skips the middle layer, giving direction directly to individual contributors and undermining the first-line managers. The pipeline leaks talent at the manager level because they feel bypassed. + +### Passage 3 to 4: From Managing Managers to Functional Manager + +The functional manager oversees an entire function (engineering, marketing, finance) and must integrate the function's work with the broader business strategy. New skills include long-term functional strategy, mature cross-functional collaboration, and competing for resources at the executive level. + +The blockage symptom: the functional leader who optimizes their silo without understanding how it connects to (or constrains) other functions. Engineering builds beautifully without regard for what sales can actually sell. + +### Passage 4 to 5: From Functional Manager to Business Manager + +This is the most significant and underestimated transition. The business manager owns a P&L and must integrate all functions -- a fundamentally different cognitive task from excelling at one function. Long-term thinking, risk management, and external orientation (customers, competitors, market trends) become primary. + +The blockage symptom: the business manager who continues to over-index on their original function. The former VP of Engineering who, as General Manager, still spends 60% of their time on technical architecture while the commercial side atrophies. + +### Passage 5 to 6: From Business Manager to Group/Enterprise Manager + +The enterprise leader manages a portfolio of businesses and develops business managers. Success is measured in decades, not quarters. The skills are primarily about capital allocation, talent development at the most senior levels, and shaping organizational culture. + +The blockage symptom: the enterprise leader who cannot resist running one of the businesses directly, starving the others of strategic attention. + +--- + +## Prompts + +**Prompt 1 -- Pipeline Blockage Diagnosis:** +> My company is at [stage] with [number] employees. I'm experiencing these leadership challenges: [describe -- e.g., "My VP of Engineering still reviews every pull request," "My managers don't develop their people," "I can't step back from day-to-day operations"]. Using the Leadership Pipeline model, diagnose which passage transitions are blocked, what skills, time, and values shifts haven't occurred, and recommend specific interventions to clear the blockages. + +**Prompt 2 -- Founder Passage Planning:** +> As founder and CEO of a [stage] startup growing from [current size] to [target size], map my personal leadership pipeline journey. What passage am I currently navigating? What skills must I develop, what time allocation must change, and what values must I adopt to successfully make this transition? Be specific about what I need to stop doing, start doing, and continue doing. + +**Prompt 3 -- Succession Pipeline Design:** +> I need to build a leadership pipeline for my [function/company] that currently has [describe structure]. Identify the critical passage transitions that need to happen in the next 12-24 months, the people who are candidates for each transition, and the development programs or experiences that would prepare them. Flag any passages where we have no viable candidates -- these are our succession gaps. + +--- + +## Use Cases + +**Series B Startup Where the Founder Cannot Let Go** + +A Series B edtech company with 85 employees and $12M ARR has a founder-CEO who still approves every major product decision, attends every customer escalation call, and reviews every marketing campaign. The board has raised the issue twice. The founder genuinely believes no one else can do these things as well. A Leadership Pipeline analysis reveals the founder is stuck at Passage 1-2: still operating as a super-powered individual contributor managing others rather than managing managers who manage others. The intervention is threefold: hire a VP of Product (Passage 4 candidate), promote two senior engineers to engineering managers and invest in their Passage 1-2 transition, and create explicit decision-rights documentation that removes the founder from operational decisions. The founder's time allocation must shift from 80% execution / 20% strategy to the inverse. + +**Hypergrowth Company Losing Middle Management** + +A growth-stage marketplace company tripled headcount in 18 months. Attrition is concentrated at the manager level -- exactly the people promoted from individual contributor roles during the scaling surge. Pipeline analysis reveals a systemic Passage 1-2 failure: the company promoted its best engineers, designers, and salespeople into management roles without any transition support. These new managers were still valued (and valued themselves) for individual output, not team development. None received training in delegation, coaching, or performance management. The fix is a dedicated management development program focused on the three dimensions of the passage: skills workshops on delegation and feedback, time audits to shift from doing to managing, and explicit recalibration of what the company rewards -- measuring managers on team output, not personal heroics. + +--- + +## Anti-Patterns + +- **Promoting Based on Current-Level Excellence.** The single most common pipeline error: promoting the best salesperson to sales manager, the best engineer to engineering lead, the best analyst to analytics director. Excellence at level N is not evidence of readiness for level N+1. The skills, time application, and values are fundamentally different. Promotion should be based on evidence of next-level capabilities, not current-level performance. + +- **Skipping Passages.** Leapfrogging someone from individual contributor to managing managers, or from functional leader to enterprise leader, without adequate preparation at intermediate levels. Each passage builds capabilities that the next passage assumes. Skipping one creates leaders who lack foundational skills they cannot easily acquire under the pressure of a more senior role. + +- **Allowing Passage Regression.** Tolerating leaders who retreat to the comfort of a previous passage under stress. The VP of Engineering who starts coding again during crunch time. The CEO who takes over a sales call because the deal is "too important." Each regression reinforces the old values and signals to the organization that passage transitions are optional. + +- **Pipeline Without Development Infrastructure.** Diagnosing passage transitions without investing in the coaching, training, and mentoring required to support them. Telling a new manager to "manage, not do" without teaching them how is a recipe for failure and resentment. + +- **Ignoring the Values Dimension.** Focusing development exclusively on skills while neglecting the values transformation. A manager can learn delegation techniques in a workshop. Learning to genuinely value team success over personal contribution requires sustained coaching, reinforcement, and often a personal identity shift that workshops alone cannot produce. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Growth | Founder's Passage 1-2 and first management layer | The founder must navigate their own passage while simultaneously supporting the first generation of managers through theirs; this dual demand is the defining challenge of the growth stage | +| Scale | Building passages 2-4 systematically | The organization needs formal pipeline infrastructure: management development programs, assessment criteria for passage readiness, and succession planning at every level | + +--- + +## Output Template + +```markdown +# Leadership Pipeline Assessment: [Company Name] + +**Date:** [Date] +**Company Stage:** [Stage] +**Headcount:** [Number] +**Assessed by:** [Name/Role] + +## Current Pipeline Map + +| Person | Current Role | Pipeline Level | Operating At Level | Gap? | Blockage Description | +|--------|-------------|---------------|-------------------|------|---------------------| +| [Name] | [Role] | [Passage N] | [Passage N-1/N/N+1] | [Yes/No] | [Description if yes] | + +## Critical Blockages (Priority Order) + +### Blockage 1: [Person/Role] +- **Expected level:** [Passage N] +- **Operating at:** [Passage N-x] +- **Skills gap:** [What they can't yet do] +- **Time allocation gap:** [How they spend time vs. how they should] +- **Values gap:** [What they value vs. what they should value at this level] +- **Intervention plan:** [Specific actions, timeline, support needed] + +### Blockage 2: [Person/Role] +... + +## Succession Gaps + +| Role/Passage | Current Holder | Ready-Now Successor | Ready-in-12-Months | Development Needed | +|-------------|---------------|--------------------|--------------------|-------------------| +| [Role] | [Name] | [Name or NONE] | [Name or NONE] | [Development plan] | + +## 90-Day Pipeline Development Plan +1. [Priority action] +2. [Priority action] +3. [Priority action] + +## Investment Required +- **Training/coaching budget:** [Amount] +- **Time commitment from senior leaders:** [Hours/week] +- **External support needed:** [Coaches, programs, assessments] +``` + +--- + +## Related Skills + +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- Each pipeline passage requires the leader to adopt different situational styles; a first-time manager needs more direction (S1-S2), while a business manager requires delegation and strategic support (S3-S4). +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Senior pipeline levels (Passages 3+) are primarily about creating the conditions Hackman describes rather than directing work. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Newly promoted managers often inherit or form new teams that restart the Tuckman cycle; understanding team stages helps navigate passage transitions. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Every pipeline passage requires letting go of previous-level tasks, making delegation the core behavioral shift at each transition. +- **[Senior Leadership Transition](../../content/skills/leadership/senior-leadership-transition.md)** -- Addresses the practical challenges of moving into senior roles, directly complementing the pipeline's structural model of leadership passages. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Pipeline transitions succeed when supported by coaching; managers at each passage need mentors who have navigated the same transition. diff --git a/plugins/foreman/skills/leadership-style-adaptation/SKILL.md b/plugins/foreman/skills/leadership-style-adaptation/SKILL.md deleted file mode 120000 index a97310b..0000000 --- a/plugins/foreman/skills/leadership-style-adaptation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/leadership-style-adaptation.md \ No newline at end of file diff --git a/plugins/foreman/skills/leadership-style-adaptation/SKILL.md b/plugins/foreman/skills/leadership-style-adaptation/SKILL.md new file mode 100644 index 0000000..19598c2 --- /dev/null +++ b/plugins/foreman/skills/leadership-style-adaptation/SKILL.md @@ -0,0 +1,190 @@ +--- +name: "leadership-style-adaptation" +description: "Provides practical self-diagnosis exercises and daily habits for recognising when a leader's default style fails and adapting in real time. Focuses on behavioural flexibility rather than theory -- how to read the room, when to shift approach, and how to stay authentic while flexing. Complements the theoretical models in Lewin Leadership Styles and Situational Leadership with actionable daily practice. Use when a leader's default approach stops working, when team dynamics shift, when coaching managers on flexibility, or when preparing to lead a new team with different needs." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership-style + - adaptability + - self-awareness + - authenticity + - management + - flexibility + - team-dynamics +related_skills: + - leader-self-reflection + - senior-leadership-transition + - leadership-voice-and-presence + - lewin-leadership-styles + - situational-leadership + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Leadership Style Adaptation + +Pause here and answer one question: if you asked your team to describe your leadership in three words, what would they say? + +Not what you hope they would say. Not the words from your last 360 review that you carefully internalised. The actual three words that the people who report to you would use when describing you to a friend over dinner. Visionary or micromanager. Supportive or absent. Decisive or impulsive. Calm or detached. + +The gap between how you see yourself and how your team experiences you is where most leadership style failures live. Not in choosing the wrong theoretical model -- the frameworks exist and are well-documented (see Lewin Leadership Styles and Situational Leadership for the theory) -- but in the daily, unglamorous work of noticing when your default approach has stopped serving the people in front of you, and adjusting before the damage compounds. + +--- + +## The Practice + +### Your Default Style: A Self-Diagnosis + +Every leader has a default -- the style they revert to under pressure, in ambiguity, or when they stop paying attention. Goleman's research identifies six styles that produce positive organisational effects when applied correctly: authoritative (visionary), affiliative (harmony-building), democratic (consensus-seeking), coaching (development-focused), and two others that require more careful deployment. The question is not which style is best. It is which style you reach for automatically, and whether that automatic reach matches the moment. + +**The Mirror Exercise** + +Conduct this weekly for one month: + +1. At the end of each day, write down the most consequential interaction you had with your team. +2. Describe what you said and did -- not what you intended. +3. Label the style you used (directive, consultative, supportive, delegative, visionary, coaching). +4. Ask: was that the style this situation needed, or was it the style I am most comfortable with? +5. Note the gap. Over four weeks, patterns will emerge that no personality test can replicate. + +### Six Signals That Your Default Style Is Failing + +Style mismatches do not announce themselves. They manifest as symptoms that leaders misattribute to team problems rather than leadership problems: + +1. **Silence in meetings.** You interpret it as agreement or passivity. Often it means your directive style has trained people that their input does not matter. +2. **Decisions that unravel.** You achieve consensus in the room, but commitments dissolve within days. Your democratic style may be producing performative agreement rather than genuine alignment. +3. **High performers leaving.** Your affiliative style keeps harmony but provides insufficient challenge. Top talent needs to be stretched, not merely supported. +4. **Innovation drought.** Your coaching style develops individuals but your team never takes collective creative risks. Development without vision produces skilled people with no direction. +5. **Burnout clusters.** Your authoritative style drives ambition but the pace you set as a visionary exhausts the team that must execute the vision. +6. **Learned helplessness.** Your directive style has solved problems so effectively that your team has stopped trying to solve them without you. Efficiency today, dependency tomorrow. + +### The Adaptation Habit: Read, Choose, Act, Review + +Adaptation is not instinct; it is a four-step practice that, with repetition, becomes fluid. + +**Read** the situation before entering it. What does this meeting need -- energy, structure, empathy, challenge? What state is your team in -- confident, confused, demoralised, overextended? + +**Choose** a style deliberately. This is the moment where theory becomes practice. The authoritative approach energises a demoralised team with vision. The affiliative approach heals a fractured team through connection. The democratic approach generates ownership for a complex decision. The coaching approach develops a promising but unpolished performer. The choice should serve the team, not your comfort. + +**Act** with commitment. Half-measures in style adaptation are worse than no adaptation at all. If you choose to be consultative, actually consult -- do not ask for input you have already decided to ignore. If you choose to delegate, actually let go -- do not hover with thinly disguised control. + +**Review** within 24 hours. Did the style you chose produce the effect you intended? If not, was the style wrong, or was the execution flawed? Honest review builds the pattern-recognition that eventually makes adaptation feel natural rather than forced. + +### Authenticity and Adaptation Are Not Opposites + +The most common objection to style flexibility: "That is not who I am." This confuses values with behaviours. Authenticity means leading consistently from your core values -- integrity, respect, ambition, whatever anchors your identity. Adaptation means expressing those values through different behaviours depending on what the moment demands. A leader who values respect can express it through direct challenge (when a team member needs growth) or through patience (when a team member needs recovery). The value is constant. The behaviour varies. + +The question to ask: does this adaptation require me to betray my values, or merely to express them differently? If the former, do not adapt. If the latter, the resistance is comfort masquerading as principle. + +--- + +## Prompts + +**Prompt 1 -- Default Style Diagnosis:** +> Based on the following descriptions of how I typically lead in different situations, identify my default leadership style and the situations where it works well versus where it fails. Situation 1: [describe]. Situation 2: [describe]. Situation 3: [describe]. For each situation where my default fails, recommend a specific alternative style and explain what I would do differently in practice -- not in theory but in concrete behavioural terms. + +**Prompt 2 -- Team Style Mapping:** +> I lead a team of [number] people. Here is a brief profile of each: [describe each person's experience level, current performance, and what they seem to need from you]. For each team member, recommend the leadership style that would be most effective right now and explain what that looks like in my daily interactions with them. Then identify where I will face the hardest adaptation -- where my default style and the needed style are furthest apart. + +**Prompt 3 -- Adaptation Scenario Practice:** +> Present me with five leadership scenarios requiring different styles. For each scenario, describe the situation, the people involved, and the outcome at stake. After I respond with my approach for each, assess which style I chose, whether it matched the situation's needs, and what the likely outcome would be. Then provide a corrected approach for any mismatches. + +**Prompt 4 -- Authenticity Boundary Mapping:** +> My core leadership values are [list 3-5 values]. I have been told I need to be more [describe requested change -- e.g., directive, empathetic, hands-off]. Help me distinguish between adaptation that would strengthen my leadership and adaptation that would compromise my values. For each requested change, design a version of that behaviour that remains authentic to my stated values. + +--- + +## Use Cases + +**Growth-Stage CEO Whose Visionary Style Exhausts the Team** +A founder-CEO at a 100-person company has built the business on infectious enthusiasm and bold strategic bets. The authoritative style that attracted early employees now produces burnout among a team that has been sprinting for three years. Exit interviews reveal a pattern: "I love the vision but I cannot sustain the pace." The CEO's adaptation: shifting to an affiliative mode every Friday -- no strategy discussions, no new initiatives, just checking in on people. Adding coaching conversations with the top ten performers, focusing on their development rather than the company's roadmap. The vision remains unchanged; the delivery becomes sustainable. + +**Early-Traction Technical Leader Whose Directive Style Blocks Innovation** +An engineering lead at a 20-person startup solves problems faster than anyone on the team. Their directive efficiency is legendary -- and it has created a team that waits for instructions rather than proposing solutions. The mirror exercise reveals the pattern: in the last twenty consequential interactions, nineteen involved the leader providing the answer. The adaptation: a "questions only" rule for the first ten minutes of every problem-solving session. The leader asks; the team answers. It feels painfully slow for three weeks. In week four, the team ships a feature the leader had not considered. + +**Scale-Stage HR Leader Navigating a Merger** +A CHRO at a 500-person company must integrate a 200-person acquisition. Her default democratic style -- building consensus, soliciting input, honouring all perspectives -- is essential for cultural integration but disastrous for the forty decisions that must be made in the first thirty days. The adaptation: directive for structural decisions (reporting lines, systems, policies) and democratic for cultural decisions (values alignment, team rituals, communication norms). She is transparent about the switch: "For the next month, I will make some decisions unilaterally because speed matters. For the decisions that shape who we are, I will take the time to hear from everyone." + +--- + +## Anti-Patterns + +1. **Style Tourism.** Trying a new style for one meeting, feeling awkward, and concluding it does not work. Adaptation requires sustained practice, not a single experiment. A style tried once is a performance; a style practised for a month is a capability. + +2. **Confusing Adaptation with Inauthenticity.** Using "that is not who I am" as a shield against necessary behavioural change. Authentic leaders adapt constantly; what remains fixed is their values, not their methods. + +3. **One-Size-Fits-All Across the Team.** Leading every team member with the same style because "fairness" demands consistency. Fairness is giving each person what they need to succeed -- which means different styles for different people at different moments. + +4. **Reading the Room but Not Acting.** Leaders who accurately diagnose what a situation needs but cannot bring themselves to deliver it. Diagnosis without action is observation, not leadership. + +5. **Adapting to Avoid Discomfort Rather Than to Serve the Team.** Shifting to an affiliative style not because the team needs warmth but because the leader dreads conflict. The test: does this adaptation serve my comfort or their development? + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder flexibility | Founders must shift styles multiple times per day -- directive with the product, coaching with the first hire, visionary with investors. The range required is extreme, and the margin for error is narrow because every person represents a large fraction of the team. | +| Growth | Manager development | The founder's adaptation skills must now be taught to first-time managers who have never led before. The risk: managers default to the style they experienced from the founder, regardless of whether it suits their team. Explicit style coaching becomes a training priority. | +| Scale | Systemic calibration | At scale, individual style adaptation matters less than the organisation's collective style repertoire. The question shifts from "How should I lead this person?" to "Does our management culture reward style flexibility or punish deviation from a dominant norm?" | + +--- + +## Output Template + +```markdown +# Leadership Style Adaptation Assessment + +**Leader:** [Name] +**Team Size:** [Number] +**Date:** [Date] + +## Default Style Profile +- **Primary default:** [Style name] +- **Under pressure:** [Style name] +- **Evidence:** [Specific behaviours observed] + +## Team Style Map + +| Team Member | Their Need | Optimal Style | Your Default Gap | Adaptation Required | +|-------------|-----------|---------------|-----------------|---------------------| +| [Name] | [Need] | [Style] | [Low/Medium/High] | [Specific change] | + +## Situation-Style Matrix + +| Recurring Situation | Current Approach | Needed Approach | Behaviour Change | +|--------------------|-----------------|-----------------|------------------| +| [e.g., Sprint planning] | [Current] | [Needed] | [Concrete action] | +| [e.g., 1-on-1s] | [Current] | [Needed] | [Concrete action] | +| [e.g., Crisis response] | [Current] | [Needed] | [Concrete action] | + +## Adaptation Practice Plan +- **Week 1-2:** [Mirror exercise -- daily journaling of style used vs. style needed] +- **Week 3-4:** [Deliberate style experiment -- choose one situation to approach differently] +- **Month 2:** [Expand to three situations; solicit feedback from team] +- **Month 3:** [Review patterns; adjust default where evidence supports it] + +## Authenticity Boundaries +- **Will adapt:** [Behaviours I will flex] +- **Will not compromise:** [Values that remain fixed] +``` + +--- + +## Related Skills + +- **[Lewin Leadership Styles](../../content/skills/frameworks/lewin-leadership-styles.md)** -- The theoretical taxonomy of autocratic, democratic, and laissez-faire styles; this skill provides the daily practice, Lewin provides the conceptual foundation. +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- Hersey-Blanchard's model of matching style to follower readiness; this skill adds the self-diagnosis and habit-building that the model assumes but does not teach. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness and social awareness are prerequisites for reading the room accurately enough to adapt effectively. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The mirror exercise described here is a focused application of the broader reflective practice covered in this companion skill. +- **[Senior Leadership Transition](../../content/skills/leadership/senior-leadership-transition.md)** -- Leadership transitions are the moments where style adaptation matters most and where default styles are most likely to fail. +- **[Reading People](../../content/skills/people/reading-people.md)** -- The nonverbal signal detection and mirroring techniques provide the real-time data that the Read-Choose-Act-Review adaptation cycle depends on. diff --git a/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md b/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md deleted file mode 120000 index 9b5b5d5..0000000 --- a/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/leadership-voice-and-presence.md \ No newline at end of file diff --git a/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md b/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md new file mode 100644 index 0000000..2d37c28 --- /dev/null +++ b/plugins/foreman/skills/leadership-voice-and-presence/SKILL.md @@ -0,0 +1,187 @@ +--- +name: "leadership-voice-and-presence" +description: "Develops the multi-dimensional leadership voice that senior leaders need to communicate authentically across audiences and situations. Covers the five voice dimensions (character, context, clarity, curiosity, connection), the present-past-future introduction framework, elevator pitch evolution, and personal story as a leadership instrument. Use when preparing for a senior role introduction, refining executive communication style, building authentic presence, crafting a leadership narrative, or coaching leaders who struggle to connect with their teams." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - communication + - executive-presence + - authenticity + - storytelling + - personal-brand + - introduction + - elevator-pitch +related_skills: + - senior-leadership-transition + - leader-self-reflection + - leadership-style-adaptation + - radical-candor + - emotional-intelligence + - carnegie-win-friends +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Leadership Voice and Presence + +A CEO tells her team: "We need to be more innovative." The team hears: "What we have been doing is wrong." A VP says: "I trust you to figure this out." The team hears: "I have no idea what to do either." A founder declares: "We are pivoting to capture a massive opportunity." The team hears: "We are abandoning the thing I told you to care about six months ago." + +The gap between what leaders say and what people hear is where most leadership communication fails. Not because the words are wrong, but because the voice delivering them lacks the architecture to carry meaning across that gap. Leadership voice is not volume, charisma, or rhetorical polish. It is the capacity to respond authentically, constructively, and effectively regardless of the audience or situation -- and it is built, not born. + +--- + +## The Practice + +### The Five Dimensions of Leadership Voice + +A complete leadership voice operates across five dimensions simultaneously. Weakness in any single dimension creates a predictable failure mode. + +**1. Character** +The foundation. Character-rooted voice is anchored in principles -- "Give the benefit of the doubt," "Be direct with respect" -- that prevent the leader from becoming a chameleon who adjusts values to suit the room. Without character, the other four dimensions become performance rather than leadership. The test: does your communication remain consistent whether you are speaking to the board or to an intern? + +**2. Context** +As leaders assume senior roles, their view of the business broadens. Part of the job becomes translating that broader perspective for others. Before diving into details, address the bigger picture of the topic at hand. Context-setting prevents the disorientation that occurs when teams receive directives without understanding the strategic logic behind them. + +**3. Clarity** +Amid infinite possible priorities, the leader's voice must cut. Clarity means deciding what the team needs to focus on right now -- and, equally, what can wait. Leaders who fail to provide this risk spreading their teams thin across initiatives that compete with one another for attention. Clarity is not simplification; it is prioritisation made audible. + +**4. Curiosity** +The leader who approaches every situation as though they have all the answers silences the room. Curiosity-driven voice invites others to share their perspective, particularly when it differs from the leader's own. The practical test: in your last five meetings, what percentage of your contributions were statements versus questions? + +**5. Connection** +As a leader's purview expands, staying close to all teams and networks becomes harder. Connection-driven voice bridges that distance through storytelling about work's impact, expressing gratitude for effort, and making time for rapport even when the calendar argues against it. Connection signals that you care about people, not just outcomes. + +### The Introduction Framework: Present, Past, Future + +Leaders meet many people. Introducing yourself without rambling requires structure. The present-past-future framework distills an introduction into a few sentences: + +- **Present:** Your name, role, and what you are currently working on. +- **Past:** One sentence establishing credibility -- a previous accomplishment or relevant experience. +- **Future:** What you are excited about going forward -- a goal, a partnership, or a vision. + +Three sentences. Done. + +### The Elevator Pitch as Leadership Evolution + +Early in a career, the elevator pitch answers: "What are you working on?" and "What do you want to do?" As leaders move into senior roles, the pitch must evolve to answer different questions entirely: "Who are you as a leader?" and "What do you care most about?" The goal is to be predictable in the best sense -- someone whose values are unwavering and clear, regardless of the audience. + +### Personal Story as Leadership Instrument + +Knowing where you come from is not sentimentality; it is a strategic asset. Authentic leaders draw on their personal narratives -- the mentors, the failures, the turning points -- to connect with others and to ground their decision-making. The discipline lies in selecting which elements of your story serve the current audience and context, and in reframing hardship as motivation rather than complaint. + +--- + +## Prompts + +**Prompt 1 -- Voice Dimension Audit:** +> Assess my leadership communication across the five dimensions of voice (character, context, clarity, curiosity, connection). Here are transcripts or descriptions of five recent communications I delivered: [describe each -- audience, situation, what you said, how it was received]. For each, identify which dimensions were strong and which were absent. Then identify my dominant dimension and my weakest, and provide specific daily practices to strengthen the gap. + +**Prompt 2 -- Introduction Crafting:** +> Help me craft three versions of my professional introduction using the present-past-future framework. My current role is [role] at [company]. My relevant background includes [key experiences]. My forward-looking goals are [goals]. Create: (1) a 30-second version for networking events, (2) a 60-second version for a team all-hands where I am the new leader, and (3) a written version for a company-wide email announcement. Each should feel natural, not scripted. + +**Prompt 3 -- Leadership Narrative Design:** +> I need to develop my leadership story for [context -- e.g., board presentation, team offsite, investor meeting]. My background includes [describe key experiences, challenges, turning points]. Help me identify the three to five narrative elements that are most relevant to this audience, structure them into a coherent arc, and suggest specific moments where vulnerability will strengthen rather than undermine credibility. The story should answer: "Who is this person, and why should I follow them?" + +**Prompt 4 -- Elevator Pitch Evolution:** +> My current elevator pitch is [paste pitch]. I am moving into a [new role/stage]. Help me evolve this pitch from answering "What do I do?" to answering "Who am I as a leader and what do I stand for?" The new version should communicate my core values, my leadership philosophy, and what people can expect from me -- in under 60 seconds. + +--- + +## Use Cases + +**Growth-Stage CTO Preparing for First Board Presentation** +A CTO at a 75-person company has never presented to the board. Their communication defaults to technical depth -- detailed architecture diagrams, performance metrics, stack decisions. The board wants something different: strategic context, risk assessment, and resource implications. Applying the five-voice framework, the CTO restructures the presentation: opens with context (market dynamics driving technical decisions), delivers with clarity (three priorities, ranked), demonstrates curiosity (acknowledges two open questions the team is investigating), and closes with connection (a brief story about a customer whose experience improved because of a technical bet the team made). The board member who typically checks email during tech updates asks a follow-up question. + +**Early-Traction Founder Meeting Investors for the First Time** +A first-time founder with deep domain expertise but no public profile must introduce themselves credibly to a room of venture capitalists. Using the present-past-future framework: present ("I lead [Company], which is solving [problem] for [market]"), past ("Before founding this, I spent eight years inside the industry and saw firsthand why existing solutions fail"), future ("We are building toward [vision], and the first milestone is [concrete goal]"). The introduction takes twenty seconds. The investor leans forward. + +**Scale-Stage CEO Rebuilding Trust After a Layoff** +A CEO at a 400-person company has conducted a 15% reduction in force. The remaining employees are anxious and distrustful. The CEO's instinct is to lead with optimism: "The future is bright." But the five-voice framework demands a different sequence. Character first: acknowledge the pain honestly. Context: explain the strategic reasoning without euphemism. Clarity: name the three things the company will focus on now. Connection: share a personal reflection on the weight of the decision. Curiosity comes last: invite questions and commit to answering them. The all-hands lasts ninety minutes. It is the most important presentation the CEO has ever given. + +--- + +## Anti-Patterns + +1. **The Chameleon.** Leaders who adjust not just their communication style but their actual values depending on the room. Adapting tone is skill; adapting principles is erosion. People detect inconsistency faster than leaders expect, and the result is a reputation for unreliability disguised as flexibility. + +2. **The Monologue Default.** Leaders who interpret "presence" as commanding the floor. A voice built entirely on statements, with no curiosity dimension, creates an audience of nodders rather than contributors. The most dangerous version: the leader who solicits questions but whose body language makes clear that questions are unwelcome. + +3. **The Oversharer.** Personal narrative deployed without editorial judgment. Not every audience needs every formative experience. The discipline of leadership storytelling lies in selection: which elements of your story serve this audience, this moment, this purpose? Vulnerability without discretion becomes therapy, not leadership. + +4. **The Pitch That Never Evolves.** Leaders who introduce themselves the same way at year ten as they did at year one. The elevator pitch must mature alongside the leader's role and responsibilities. A CEO who still leads with their functional expertise signals that they have not made the mental transition to enterprise leadership. + +5. **The Context Skipper.** Jumping directly into directives without establishing the strategic rationale. Teams that do not understand why they are being asked to do something comply rather than commit -- and compliance without comprehension produces brittle execution. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder's origin story | The founder's personal narrative is the company's brand. Investors, early employees, and first customers are buying the person as much as the product. The voice must convey conviction without arrogance, and vulnerability without fragility. | +| Growth | Multi-audience calibration | The leader now addresses audiences with fundamentally different needs: engineers want technical respect, salespeople want market conviction, investors want financial discipline. The five-voice framework becomes essential for maintaining coherence across these contexts. | +| Scale | Institutional voice | At scale, the leader's voice must carry through layers of management. What you say in the executive meeting will be paraphrased in the director meeting and summarised in the team standup. Clarity and context become even more critical because your words are now a game of telephone. | + +--- + +## Output Template + +```markdown +# Leadership Voice Development Plan + +**Leader:** [Name] +**Current Role:** [Role] +**Date:** [Date] + +## Voice Dimension Assessment + +| Dimension | Current Strength (1-5) | Evidence | Development Action | +|-----------|----------------------|----------|--------------------| +| Character | [Score] | [Example] | [Action] | +| Context | [Score] | [Example] | [Action] | +| Clarity | [Score] | [Example] | [Action] | +| Curiosity | [Score] | [Example] | [Action] | +| Connection | [Score] | [Example] | [Action] | + +## Introduction Toolkit + +### 30-Second Networking Version +[Present] + [Past] + [Future] + +### Team All-Hands Version +[Extended present] + [Credibility] + [Vision] + [Invitation] + +### Written Bio Version +[Paragraph format for announcements and profiles] + +## Leadership Narrative Elements +- **Origin moment:** [The experience that shaped your leadership] +- **Defining challenge:** [A difficulty that reveals character] +- **Core conviction:** [The belief that drives your decisions] +- **Future vision:** [Where you are leading people] + +## Communication Habits to Build +| Habit | Frequency | Trigger | +|-------|-----------|---------| +| [e.g., Open with context before directives] | Every meeting | Before stating a decision | +| [e.g., Ask one genuine question per meeting] | Daily | When tempted to direct | +| [e.g., Share one story of impact per week] | Weekly | Team standup or 1:1 | +``` + +--- + +## Related Skills + +- **[Senior Leadership Transition](../../content/skills/leadership/senior-leadership-transition.md)** -- The voice evolution described here is a necessary component of the broader identity shift required when moving to enterprise leadership. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Candor is the character dimension of voice in its most consequential form: the willingness to deliver hard truths with care. +- **[Carnegie: Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principles of influence map directly to the connection and curiosity dimensions of leadership voice. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The personal narrative that grounds authentic voice is constructed through the reflective practices covered in this companion skill. +- **[Story Performance and Delivery](../../content/skills/storytelling/story-performance-and-delivery.md)** -- The vocal, physical, and timing techniques for live performance directly strengthen the delivery dimension of leadership presence. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- Voice is the primary channel through which daily influence operates; authority, credibility, and connection all manifest through how a leader speaks. diff --git a/plugins/foreman/skills/leading-through-change/SKILL.md b/plugins/foreman/skills/leading-through-change/SKILL.md deleted file mode 120000 index 43e3e2c..0000000 --- a/plugins/foreman/skills/leading-through-change/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/leading-through-change.md \ No newline at end of file diff --git a/plugins/foreman/skills/leading-through-change/SKILL.md b/plugins/foreman/skills/leading-through-change/SKILL.md new file mode 100644 index 0000000..71f233b --- /dev/null +++ b/plugins/foreman/skills/leading-through-change/SKILL.md @@ -0,0 +1,236 @@ +--- +name: "leading-through-change" +description: "Guides leaders through the emotional, communicative, and practical dimensions of organisational change, with emphasis on empathetic communication, giving people time and choices, managing personal identity transitions, and finding opportunity in chaos. Use when announcing restructuring, when teams resist a strategic pivot, when post-change morale collapses, when employees feel unheard during transitions, or when a leader's own identity is disrupted by professional upheaval." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - change-management + - communication + - empathy + - transitions + - resilience + - uncertainty + - identity + - patience +related_skills: + - kotter-change-model + - vuca-framework + - storytelling-for-leaders + - leader-resilience-and-wellbeing + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Leading Through Change + +Map the emotional terrain before you map the project plan. People cycling through significant organisational change -- a restructuring, a pivot, a merger, a leadership transition -- move through five feelings, not always in order, and often revisiting earlier ones: + +1. **Denial** -- "This will not actually affect my work." The comforting fiction that the announcement is theoretical. +2. **Anxiety** -- "What does this mean for me?" The self-preservation instinct that no amount of corporate messaging can bypass. +3. **Anger** -- "Why wasn't I consulted?" The feeling of agency being stripped away, which may be directed at the change itself or at the people leading it. +4. **Grief** -- "I miss how things were." The mourning of routines, relationships, and identities attached to the old order. +5. **Adaptation** -- "I can see my place in this." The tentative engagement with a new reality, contingent on feeling heard and included. + +Most change-leadership failures occur because the leader, having already processed these feelings privately over weeks or months of planning, expects the organisation to arrive at adaptation within days. Erika Andersen's research is direct: you have had weeks to think about this change; your employees are hearing about it for the first time. Of course they ask questions. Of course they worry. That is not resistance. That is the normal human response to losing certainty. + +Kotter's eight-step model provides the structural architecture for change management (see `kotter-change-model.md`). This skill operates in the spaces between those steps -- the daily emotional labour that determines whether a structurally sound change process succeeds or stalls. + +--- + +## The Practice + +### Ask Before You Tell + +Patti Sanchez's research identifies empathetic communication as the single most important leadership behaviour during change. The practice is counterintuitive for leaders accustomed to providing answers: before telling people what is happening, ask them what they are worried about. + +The sequence: +1. Explain what is changing and why, with as much transparency as the situation permits. +2. Ask: "What concerns do you have?" and "What improvements would you like to see?" +3. Listen without defending, correcting, or minimising. +4. Address what you heard, being honest about what you can and cannot control. +5. Repeat at each phase of the change, because concerns evolve as reality unfolds. + +The goal is not to eliminate worry. It is to ensure that everyone feels included and heard -- which is the necessary precondition for the buy-in that makes change executable. + +### Give People Time + +Andersen's most practical insight: stop trying to talk employees out of their feelings. Doubt and scepticism are not obstacles to be removed; they are stages to be traversed. The leader who responds to worry with "Don't worry, this will be great" has communicated two things: that the leader does not understand the employee's experience, and that expressing concern is unwelcome. Neither message builds buy-in. + +Instead, give people time to process. Acknowledge that the emotions they are feeling are reasonable. Ask about their concerns without being dismissive. Talk through what the change means for them specifically, not just for the organisation abstractly. The time invested in this emotional processing is not a delay in the change process -- it is the change process. Without it, compliance replaces commitment, and compliance does not survive the first setback. + +### Give People Choices + +Andersen's second principle addresses the mechanism behind much change resistance: loss of agency. Organisational change often makes employees feel they are at the mercy of forces they cannot control. The antidote is to return as many choices as possible: + +- Let managers co-create the communication plan for their teams. +- Invite teams to propose timelines for implementing new processes. +- Identify elements that will not change and highlight them explicitly. +- Where the outcome is fixed but the path is flexible, let teams choose the path. + +The choices need not be large. Even small decisions -- when to hold the transition meeting, which communication channel to use, which team members will take which new responsibilities -- restore a sense of control that makes the larger change tolerable. + +### Caring Transparency + +Rasmus Hougaard, Jacqueline Carter, and Rob Stembridge describe "caring transparency" as the practice of being honest about what is on the leader's mind and in the leader's heart, especially when making unpopular decisions. This is not vulnerability for its own sake. It is the recognition that withholding important information -- even with good intentions -- communicates distrust. + +The key distinction: caring transparency is not unbounded disclosure. It is the willingness to tell people where they stand, clearly and compassionately, rather than allowing ambiguity to breed worse anxieties than the truth would. + +### Courage over Comfort + +Hougaard, Carter, and Stembridge also address the leader's own emotional challenge during change: the temptation to choose safety over conviction. Choosing courage -- making decisions based on values rather than quick profits, standing for what you believe even when criticism follows -- can feel vulnerable. But courage, once demonstrated, invites others to do the same. It transforms a change initiative from a top-down mandate into a shared endeavour. + +### Patience as a Change Skill + +David Sluss's research positions patience not as a personality trait but as a learnable leadership skill. During change, patience serves three functions: + +1. **Steadying the team.** A leader who cannot stay calm cannot keep others calm. +2. **Allowing strategy to work.** New approaches take time to produce results; premature abandonment of a sound plan because of early friction is one of the most common change-leadership errors. +3. **Resisting the always-on culture.** The pressure for immediate replies and constant connectivity works against the careful, methodical decision-making that change requires. + +### Navigating Personal Identity Transitions + +Toubiana, Ruebottom, and Hakak study what happens when a major change -- personal or professional -- upends the leader's own sense of self. Their research identifies four practices for navigating identity disruption: + +**1. Create a clean break.** Choose an event -- a date, a milestone, a symbolic moment -- to serve as the dividing line between "before" and "after." Mentally imbue it with significance. Consider telling a colleague or friend to add weight to the transition. + +**2. Work through hard emotions.** Acknowledge negative feelings without letting them become permanent residents. If being laid off produces anger and shame, sit with those feelings -- but also identify the positive outcomes the change has produced. The goal is not to suppress negative emotions but to make peace with them. + +**3. Focus on your many facets.** Your identity is not reducible to your job title. When professional identity is disrupted, invest in the other elements: family, community, hobbies, friendships. The reminder that you are more than your role can stabilise the ground when the role is shifting. + +**4. Craft a linking narrative.** Connect your past and present with a story that highlights continuity of values even as circumstances change. "I used to support my family through salary; now I support them through time" is a narrative that bridges two different chapters without denying the loss involved in the transition. + +### Seven-Year Cycles + +Avivah Wittenberg-Cox offers a structural perspective: dividing one's life into seven-year periods and mapping the highlights, learnings, and identity shifts of each era. The practice imposes a rhythm -- beginning, middle, end -- that normalises transition. When a significant change arrives, the mental model provides context: "I am nearing the end of one era and entering the beginning of another. I have done this before." + +### Chaos as Growth + +Rebecca Knight's reframe for organisational upheaval: choose to see chaos as a chance to grow, not a barrier to progress. When leadership changes, restructurings loom, or strategy pivots, the leader's mindset determines whether they -- and their team -- navigate the turbulence or succumb to it. The questions to ask: How do the changes affect my role? What do they mean for the company's future? How could they advance my career or enhance my skills? Staying "heads up" -- scanning the environment for opportunity -- beats "heads down" -- burying oneself in routine until the storm passes. + +--- + +## Prompts + +**Prompt 1 -- Emotional Map of Change:** +> I am leading (or about to announce) this change: [describe the change, its scope, and its rationale]. Map the likely emotional journey for three different stakeholder groups: [group 1], [group 2], [group 3]. For each group, predict which of the five feelings (denial, anxiety, anger, grief, adaptation) will be strongest and in what order. Design a communication cadence that addresses each group's emotional arc over the first 90 days. + +**Prompt 2 -- Empathetic Communication Script:** +> I need to announce [describe the change] to my team of [size]. Draft the announcement using Sanchez's framework: (a) what is changing and why, (b) what I want to ask them (concerns, hopes, suggestions), (c) what I can commit to transparently, and (d) what I genuinely do not know yet. Include follow-up questions for one-on-one conversations and a timeline for when I will provide updates. + +**Prompt 3 -- Choice Architecture for Change:** +> This change is non-negotiable: [describe what must happen]. Using Andersen's framework, identify every element of the change where people can be given a choice about how, when, or by whom the change is implemented. Design a "choices menu" I can present alongside the announcement to restore agency without compromising the initiative's objectives. + +**Prompt 4 -- Personal Transition Navigation:** +> I am going through a significant professional change: [describe it -- new role, company restructuring, departure, pivot]. Using Toubiana, Ruebottom, and Hakak's four practices, help me: (a) identify a clean "before/after" marker, (b) name the emotions I need to work through, (c) identify the non-work facets of my identity I should invest in, and (d) craft a linking narrative that connects my past and future through shared values. + +--- + +## Use Cases + +**Early-traction startup pivoting its product** + +A 15-person startup is abandoning its original product to pursue a new market. The founder, who has been processing this decision for two months, announces the pivot on Monday and expects the team to be executing by Wednesday. Instead, three engineers who joined specifically because of the original product feel betrayed. The founder implements the ask-before-tell protocol: individual conversations about concerns, explicit acknowledgement that the emotional response is legitimate, and a week of structured transition time before any new-product work begins. Two of the three engineers choose to stay, having been given time and voice. + +**Growth-stage company restructuring teams** + +A 150-person company reorganises from functional teams to cross-functional squads. The announcement produces widespread anxiety about reporting lines, role identity, and career paths. The leadership team creates a "choices menu": each squad can design its own communication norms, choose its meeting cadence, and propose which responsibilities transfer and which stay. The elements of the change that are non-negotiable (squad structure, key assignments) are clearly stated. The elements that are flexible (how, when, and by whom) are handed to the teams. Resistance decreases measurably within two weeks. + +**Scale-stage leader navigating personal identity disruption** + +A long-tenured division president is moved to a newly created "strategic initiatives" role as part of a CEO succession plan. The leader interprets the move as a demotion and experiences anger, grief, and a profound loss of identity. Using the seven-year-cycle framework, they map their career into eras and recognise that previous transitions -- from individual contributor to manager, from manager to director -- also felt like losses before they became gains. A linking narrative emerges: "My value has always been in building things that outlast me. The division was one such thing. Strategic initiatives is the next." + +--- + +## Anti-Patterns + +**1. Leading with logic when people need empathy.** The leader who responds to emotional resistance with a business case for change has correctly identified the destination and entirely misjudged the starting point. Logic is necessary but not sufficient; empathy must come first. + +**2. Labelling all pushback as "resistance."** Andersen is explicit: questions and concerns during change are not resistance. They are the normal, healthy, and predictable response of human beings who have just lost certainty. The leader who frames all pushback as opposition creates a self-fulfilling prophecy: people stop voicing concerns, not because they have been convinced, but because they have been silenced. + +**3. Expecting adaptation on the leader's timeline.** The leader has had weeks or months to process the change. Expecting the team to process it in days is unrealistic and, when enforced through impatience, destructive. Genuine buy-in takes the time it takes. + +**4. Eliminating all choice in the name of speed.** Speed and agency are not always in conflict. Giving people choices about implementation details rarely slows the initiative and frequently accelerates it, because people execute plans they helped design more willingly than plans imposed upon them. + +**5. Ignoring the leader's own emotional journey.** The leader going through change is also a human being experiencing uncertainty, loss, and identity disruption. Pretending otherwise -- performing certainty while feeling doubt -- eventually produces either burnout or a credibility collapse when the mask slips. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Pivot communication, founder's emotional honesty | The team is small enough for individual conversations; use that advantage | +| Growth | Restructuring, scaling norms, manager enablement | Changes affect people the leader does not personally know; communication must cascade through managers | +| Scale | Enterprise transformation, culture preservation during M&A | Change becomes a programme, not a conversation; structural supports (choice architecture, feedback loops, transition teams) replace personal touch | + +At early traction, the leader can speak to every affected person individually. This is an enormous advantage that founders routinely squander by defaulting to all-hands announcements. In a 15-person company, 15 individual conversations -- each tailored to that person's concerns, each asking "What worries you?" -- take a few hours and produce buy-in that a single group presentation cannot. + +At scale, the leader cannot reach everyone personally. The critical infrastructure becomes the manager layer: equipping middle managers to have empathetic conversations, providing them with honest information, and giving them the same emotional processing time before expecting them to transmit confidence to their teams. The change process becomes recursive: leadership processes the change, then equips managers, who then support their teams, each layer given its own time and space. + +--- + +## Output Template + +```markdown +# Change Communication Plan -- [Initiative Name] + +**Change description:** [What is changing] +**Rationale:** [Why] +**Scope:** [Who is affected] +**Timeline:** [Key dates] +**Prepared by:** [Name] + +## Emotional Map + +| Stakeholder Group | Dominant Feeling (Week 1) | Likely Progression | Tailored Message | +|-------------------|--------------------------|-------------------|-----------------| +| [Group 1] | [Feeling] | [Sequence] | [Key message] | +| [Group 2] | [Feeling] | [Sequence] | [Key message] | +| [Group 3] | [Feeling] | [Sequence] | [Key message] | + +## Communication Cadence + +| Timing | Channel | Audience | Content | Ask | +|--------|---------|----------|---------|-----| +| Day 1 | [Channel] | [Audience] | [What to communicate] | [What to ask] | +| Week 1 | [Channel] | [Audience] | [Follow-up] | [Concerns check] | +| Week 4 | [Channel] | [Audience] | [Progress update] | [Adjustment input] | +| Week 8 | [Channel] | [Audience] | [Status report] | [Feedback] | + +## Choices Menu + +| Non-Negotiable | Flexible | Choice Given To | +|---------------|----------|----------------| +| [Element] | [Element] | [Group] | +| [Element] | [Element] | [Group] | + +## Leader Self-Check +- Have I given people time to process, or am I expecting adaptation on my timeline? +- Am I labelling pushback as resistance, or hearing it as legitimate concern? +- Have I been transparently caring, or have I withheld information to avoid discomfort? +- Have I processed my own emotions about this change, or am I performing certainty? + +## 90-Day Milestones +- **Day 30:** [Expected state, check-in method] +- **Day 60:** [Expected state, check-in method] +- **Day 90:** [Expected state, check-in method, adjustment mechanism] +``` + +--- + +## Related Skills + +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- The structural eight-step process for change management; this skill provides the emotional and communicative layer that Kotter's model assumes but does not detail. +- **[VUCA Framework](../../content/skills/frameworks/vuca-framework.md)** -- Change often occurs in volatile, uncertain, complex, and ambiguous environments; VUCA provides the diagnostic lens for the operating context. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Change communication is, at its core, storytelling; the companion skill on narrative provides the techniques for making change stories compelling. +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Leading through change is emotionally taxing; the resilience skill addresses the leader's own sustainability during transitions. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Change disrupts team culture; this companion skill provides tools for diagnosing and rebuilding team norms during and after transitions. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- The philosophical discipline of embracing rather than resisting change provides leaders with the emotional grounding to model calm during turbulent transitions. diff --git a/plugins/foreman/skills/lean-in/SKILL.md b/plugins/foreman/skills/lean-in/SKILL.md deleted file mode 120000 index 632d2ea..0000000 --- a/plugins/foreman/skills/lean-in/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/lean-in.md \ No newline at end of file diff --git a/plugins/foreman/skills/lean-in/SKILL.md b/plugins/foreman/skills/lean-in/SKILL.md new file mode 100644 index 0000000..61f8b95 --- /dev/null +++ b/plugins/foreman/skills/lean-in/SKILL.md @@ -0,0 +1,166 @@ +--- +name: "lean-in" +description: "Applies Sandberg's Lean In framework to diagnose and address gender barriers in organizations, covering the ambition gap, mentor-sponsor deficit, and structural inclusion deficits. Use when designing inclusive hiring processes, building sponsorship programmes, analyzing gender diversity gaps, retaining senior women, or auditing promotion equity across the organization." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - gender + - diversity + - career-development + - inclusion +related_skills: + - radical-candor + - organisational-culture + - maslow-hierarchy + - carnegie-win-friends +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Lean In + +Women hold approximately 10% of CEO positions at Fortune 500 companies and represent fewer than 30% of senior management roles globally -- figures that have improved with glacial slowness over three decades. Sheryl Sandberg's *Lean In*, published in 2013, ignited a fierce debate by arguing that external barriers, while real, tell only half the story. The other half involves internal barriers: the ways women hold themselves back through internalised doubt, risk aversion, and premature career accommodation. The framework remains polarising precisely because it operates on two fronts simultaneously -- challenging systemic inequality while demanding individual agency. For entrepreneurs building companies, this dual lens is not optional. The startups that outperform on gender diversity show 25% higher probability of above-average profitability (McKinsey, 2020). The question is not whether to care about this, but how to operationalise it. + +--- + +## The Framework + +Sandberg's argument operates through a series of identified barriers -- some internal, some structural -- paired with specific prescriptions. The framework's strength lies not in any single recommendation but in the compound effect of addressing multiple barriers simultaneously. + +### Barrier 1: The Ambition Gap + +**The problem:** Research consistently shows that success and likability are positively correlated for men and negatively correlated for women. Women who assert ambition face social penalties men do not. Over time, many women internalise this dynamic and moderate their ambitions pre-emptively. + +**The prescription:** Sit at the table -- literally and figuratively. Take the seat at the conference table rather than the chair along the wall. Volunteer for high-visibility projects. Negotiate compensation with the same persistence expected of male counterparts. The evidence from negotiation research suggests that women who frame requests in communal terms ("this will help the team") face fewer likability penalties than those who frame them identically to men. + +### Barrier 2: The Mentor/Sponsor Deficit + +**The problem:** Men disproportionately receive sponsorship (active advocacy for advancement) rather than mere mentorship (advice without action). Senior leaders -- predominantly male -- more readily sponsor people who remind them of their younger selves, perpetuating homogeneity. + +**The prescription:** Distinguish mentorship from sponsorship. Seek sponsors who will stake political capital on your advancement, not merely advisors who dispense wisdom over coffee. Organisations should formalise sponsorship programmes rather than relying on organic relationships that replicate existing power structures. + +### Barrier 3: The "Leave Before You Leave" Phenomenon + +**The problem:** Women often begin accommodating hypothetical future caregiving responsibilities years before those responsibilities materialise. They decline stretch assignments, avoid relocations, or turn down promotions in anticipation of starting a family -- sometimes years in advance. The cumulative effect: by the time the decision point arrives, they have already moved to a slower career track. + +**The prescription:** Do not make career-limiting decisions based on events that have not yet occurred. Keep options open. Maintain maximum career velocity until the actual moment a trade-off must be made, then negotiate from a position of accumulated strength rather than pre-emptive retreat. + +### Barrier 4: The Myth of "Having It All" + +**The problem:** The aspiration to perform flawlessly in every role -- executive, parent, partner, community member -- produces paralysing guilt and eventual burnout. Perfectionism becomes the enemy of both career progress and personal fulfilment. + +**The prescription:** Redefine success as "having it all, but not all at the same time." Accept that trade-offs are permanent and guilt is a signal to examine priorities, not a verdict on adequacy. Build systems (domestic partnerships, childcare, delegation) that distribute responsibility rather than concentrating it. + +### Barrier 5: Institutional and Structural Deficits + +**The problem:** Even when individual women lean in, organisations may lack the infrastructure to support them: inadequate parental leave, inflexible work arrangements, promotion criteria that penalise career breaks, and evaluation systems riddled with unconscious bias. + +**The prescription:** Leaders -- particularly founders -- must build systems, not just issue exhortations. Structured interviews reduce bias. Transparent promotion criteria make advancement legible. Flexible work policies normalise caregiving for all genders. Sandberg acknowledged in later work that her initial emphasis on individual action underweighted structural reform; the mature framework addresses both. + +--- + +## Prompts + +**Prompt 1 -- Diversity Diagnostic:** +> Analyse my startup's gender diversity across three dimensions: representation (who is at each level), participation (who speaks in meetings, who gets stretch assignments), and advancement (promotion rates by gender over the past 12-24 months). Company details: [describe size, stage, industry, current team composition]. Identify which of Sandberg's barriers may be operating and recommend three concrete interventions. + +**Prompt 2 -- Inclusive Hiring Process Design:** +> Help me design a hiring process that mitigates unconscious gender bias at each stage: job description language, sourcing channels, screening criteria, interview structure, and offer negotiation. My company is at [stage] in [industry], and we currently have [describe team composition]. Use research on structured interviewing and Sandberg's insights on the ambition/likability double bind. + +**Prompt 3 -- Sponsorship Programme Architecture:** +> Design a formal sponsorship (not just mentorship) programme for my company of [size] employees. The programme should pair high-potential individuals with senior leaders who will actively advocate for their advancement. Include matching criteria, cadence, accountability mechanisms, and metrics to evaluate programme effectiveness after 12 months. + +**Prompt 4 -- Career Conversation Framework:** +> Create a structured framework for career conversations between managers and reports that addresses the "leave before you leave" dynamic and the ambition gap. The framework should help managers identify when reports may be self-limiting and provide language to surface and address those patterns constructively. Context: [describe your company culture and any observed patterns]. + +--- + +## Use Cases + +**Early-Traction B2B Startup Building Its First Leadership Team** +A founder with a seven-person team is making the first two director-level hires. The candidate pool skews 80% male. Applying the Lean In framework, the founder examines sourcing channels (over-reliance on personal networks), job descriptions (language analysis reveals "aggressive" and "dominant" descriptors that research shows depress female applications by 20-30%), and interview structure (unstructured interviews where rapport-based assessment favours similarity). Corrections at each stage double the proportion of qualified female candidates reaching final rounds. + +**Growth-Stage Company Losing Senior Women** +A 120-person company notices that women are promoted to director level at the same rate as men but leave the company within 18 months of promotion at twice the rate. A Lean In-informed analysis reveals that the company provides mentorship but not sponsorship to promoted directors; male directors receive informal sponsorship from the all-male executive team through golf outings and after-hours socialising that female directors cannot or do not access. The intervention: formalise sponsorship, restructure executive bonding to inclusive formats, and implement stay interviews at the 6- and 12-month marks post-promotion. + +**Scale-Stage Company Preparing for IPO** +A 500-person company faces investor scrutiny over board diversity ahead of its IPO. The executive team has one woman (the head of HR, a patterned appointment that reinforces stereotypes). Applying the framework's structural lens, the company audits its entire leadership pipeline, identifies the specific career stage where women's advancement stalls (the transition from VP to C-suite), and discovers that the evaluation criteria for C-suite readiness implicitly reward a profile shaped by male career patterns -- unbroken tenure, relocation willingness, 24/7 availability. Revising these criteria to value demonstrated impact rather than biographical pattern opens the pipeline. + +--- + +## Anti-Patterns + +1. **Individual Blame Disguised as Empowerment.** The most common misreading of Lean In: telling women to "just be more confident" without changing the systems that penalise confidence in women. Individual agency is necessary but insufficient. Founders who lean exclusively on personal-responsibility messaging while ignoring structural barriers are performing concern, not practicing inclusion. + +2. **Diversity as Optics.** Hiring one senior woman and declaring the problem solved. Token appointments without systemic change create impossible pressure on the appointee and provide false evidence that the system works. Pipeline metrics matter more than trophy hires. + +3. **Gender-Blind "Meritocracy."** Declaring that "we just hire the best person" while ignoring that definitions of "best" are culturally constructed and often encode masculine-default assumptions about leadership, communication style, and career trajectory. True meritocracy requires auditing what merit means in your organisation. + +4. **Ignoring Intersectionality.** Applying the Lean In framework as though all women share identical barriers. Race, class, disability, sexuality, and cultural background intersect with gender to produce distinct and compounding challenges. A framework that addresses gender in isolation will serve some women while leaving others behind. + +5. **Confusing Mentorship with Sponsorship.** Establishing a mentorship programme and expecting it to close the advancement gap. Mentors advise. Sponsors advocate. The distinction is not semantic; it is the difference between receiving guidance and receiving opportunities. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Foundational culture setting | Every hire is a cultural statement. Diversity at this stage is disproportionately influential because early employees become the template for future hires and the culture carriers as the company grows. | +| Growth | Pipeline and process | Scaling hiring demands structured processes. This is when informal practices that worked at 10 people -- "culture fit" interviews, network-based sourcing -- begin producing homogeneous teams unless deliberately counteracted. | +| Scale | Systems and accountability | At hundreds of employees, individual interventions give way to systemic ones: compensation audits, promotion rate analysis by demographic, board diversity targets, and executive accountability for inclusion metrics. | + +--- + +## Output Template + +```markdown +# Gender Equity & Inclusion Assessment: [Company Name] + +## Current State +- **Team composition by level:** [Executive / Director / IC breakdowns by gender] +- **Hiring pipeline:** [Application-to-offer ratios by gender] +- **Advancement data:** [Promotion rates by gender, past 12 months] +- **Retention data:** [Attrition rates by gender and level] + +## Barrier Analysis +| Barrier (Sandberg) | Evidence in Our Organisation | Severity | +|--------------------|------------------------------|----------| +| Ambition gap | [Observations] | High/Med/Low | +| Mentor vs. sponsor deficit | [Observations] | High/Med/Low | +| "Leave before you leave" | [Observations] | High/Med/Low | +| Structural/policy gaps | [Observations] | High/Med/Low | + +## Recommended Interventions +### Immediate (0-3 months): +- [Specific actions] +### Medium-term (3-12 months): +- [Specific actions] +### Long-term (12+ months): +- [Specific actions] + +## Success Metrics +- [Measurable outcomes to track quarterly] + +## Executive Accountability +- [Who owns each initiative and reports on progress] +``` + +--- + +## Related Skills + +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Sandberg's collaboration with Kim Scott produced the Radical Candor framework; the two models share DNA around creating environments where honest feedback transcends power dynamics. +- **[Organisational Culture](../../content/skills/frameworks/organisational-culture.md)** -- Gender barriers are deeply embedded in Schein's Layer 3 assumptions; surface-level diversity initiatives fail when underlying cultural assumptions go unexamined. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Women lean in more effectively when the environment provides Edmondson's challenger safety, ensuring that assertiveness is met with respect rather than backlash. +- **[Inclusive Leadership](../../content/skills/leadership/inclusive-leadership.md)** -- Extends Sandberg's structural prescriptions into a leadership practice framework for building systems that actively counteract bias at every organizational level. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- The distinction between mentorship and sponsorship is central to Lean In; effective coaching programmes formalize advocacy rather than relying on organic relationships that replicate existing power structures. +- **[Leadership Pipeline](../../content/skills/frameworks/leadership-pipeline.md)** -- Pipeline analysis reveals the specific career stage where women's advancement stalls, enabling targeted interventions at the passage where structural barriers concentrate. diff --git a/plugins/foreman/skills/learning-agility/SKILL.md b/plugins/foreman/skills/learning-agility/SKILL.md deleted file mode 120000 index e68dbaa..0000000 --- a/plugins/foreman/skills/learning-agility/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/learning-agility.md \ No newline at end of file diff --git a/plugins/foreman/skills/learning-agility/SKILL.md b/plugins/foreman/skills/learning-agility/SKILL.md new file mode 100644 index 0000000..9c148ee --- /dev/null +++ b/plugins/foreman/skills/learning-agility/SKILL.md @@ -0,0 +1,214 @@ +--- +name: "learning-agility" +description: "Builds the leader's capacity for rapid, continuous learning through humility, curiosity, feedback receptivity, cross-training, reflective practice, and deliberate skill selection. Use when a leader's expertise has become stale, when the organisation faces skills gaps that training alone cannot close, when setbacks trigger defensiveness rather than growth, or when a leader senses that what got them here will not get them there." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - learning + - growth + - adaptability + - feedback + - curiosity + - skills + - cross-training + - reflection +related_skills: + - growth-mindset + - flow-state + - emotional-intelligence + - focus-and-priority-management + - leader-resilience-and-wellbeing +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Learning Agility + +Every skill you possess has a shelf life. The half-life of a technical skill is now estimated at roughly two and a half years, down from a decade in the 1980s. Management skills decay more slowly but decay nonetheless -- the leadership behaviours that produced results in a 20-person startup may actively hinder a 200-person company. The leader who built their career on deep functional expertise discovers, usually with some discomfort, that expertise is depreciating while the organisational demand for adaptability appreciates. Clayton Christensen, reflecting on this dynamic, observed a painful irony: by the time leaders reach positions of authority, they often believe that only people smarter than them have something to teach them. That belief, which felt like earned confidence at 30, becomes a growth ceiling at 45. + +Learning agility -- the capacity for rapid, continuous learning from experience -- is not a personality trait. It is a practice. Korn Ferry's research confirms that leaders who rely on the same assumptions and behavioural repertoires they have used for years are prone to stagnate, underperform, or derail. The antidote is not more training. It is a fundamentally different relationship with one's own competence: one that treats expertise as a platform for further learning rather than a fortress to be defended. + +--- + +## The Practice + +### The Four Disciplines of Learning Agility + +Drawing from Monique Valcour's synthesis of the Korn Ferry research, learning agility rests on four daily disciplines: + +**1. Receiving Feedback Without Armour** + +Success creates a thick skin that is useful for absorbing criticism and dangerous for absorbing information. When a leader with a track record hears critical feedback, the default response is to classify it as an exception ("That was a one-off") or to challenge the source ("They don't understand the full picture"). Valcour's prescription is brutal in its simplicity: do not argue. Listen. Sit with the discomfort. Then evaluate whether the feedback reveals a pattern worth investigating. + +Erika Andersen extends this with a physical metaphor: when negative feedback arrives, take a breath. The breath creates a gap between stimulus and response -- just enough space to ask "How accurate is this, and how do I know?" rather than "How can I refute this?" + +**2. Experimenting with New Approaches** + +Competence produces routine, and routine produces efficiency, and efficiency produces rigidity. The discipline here is to deliberately disrupt one's own problem-solving patterns. When facing a challenge, ask: "How am I inclined to tackle this?" and then: "What are three alternative approaches I have not tried?" The goal is not to abandon what works but to expand the repertoire. A leader who can solve problems in only one way is a specialist. A leader who can solve them in several ways is adaptable. + +**3. Making Cross-Domain Connections** + +John Zenger, Joseph Folkman, and Scott Edinger's research on "competency companions" reveals that incremental improvement in an existing strength yields far less than developing a complementary skill. A technically brilliant leader who invests another 100 hours in technical depth gains marginal returns. The same leader who invests 100 hours in communication skills makes the existing technical expertise dramatically more accessible and influential. + +The practice: identify a skill domain unrelated to your core competence. Then find connections between that domain and your work. A finance leader who studies design thinking. An engineer who studies negotiation. The cross-pollination produces insights that single-domain expertise cannot generate. + +**4. Making Time for Reflection** + +Research from multiple universities confirms that regular reflection on work experiences significantly boosts learning. The practice need not be elaborate. Two questions, asked weekly: + +- "What have I learned from this week's experiences?" +- "What turned out differently than I expected, and what does that tell me?" + +Leaders who demonstrate and encourage reflection create teams that learn faster. The signal matters as much as the substance: when the boss visibly takes time to reflect, it gives permission for everyone else to do the same. + +### Choosing What to Learn + +Erika Andersen proposes three lenses for selecting the next skill to develop: + +| Lens | Question | Example | +|------|----------|---------| +| Value creation | What would help my team or company create more value? | Studying large-project management to reduce delivery times | +| Passion | What am I genuinely excited to learn? | Process architecture, because I find systems fascinating | +| Aptitude | What related skill might I have natural talent for? | Complex project management, given my existing organisational strengths | + +The ideal target sits at the intersection of all three. When that intersection is empty, start with passion -- motivation sustains effort when the learning curve steepens. + +### Reading Fiction as Leadership Development + +Brooke Vuckovic's argument for fiction is not sentimental. Fiction provides low-cost lessons in moral complexity that non-fiction cannot replicate. Fictional characters grapple with greed, self-deceit, likability, and competing loyalties -- precisely the dilemmas that leaders face but that business case studies sanitise. A leader who reads Anna Karenina or The Remains of the Day develops a vocabulary for moral ambiguity that a leader who reads only management books does not. + +### Staying in Learning Mode + +Researchers from UNSW Sydney Business School and the University of Michigan distinguish between performance mode and learning mode. In performance mode, setbacks signal inability. In learning mode, setbacks signal that the skill set is not yet complete. The practical difference is enormous: performance-mode leaders compare themselves to peers and feel threatened by gaps. Learning-mode leaders track their own growth trajectory and treat gaps as queues for the next investment. + +The simplest intervention is a self-check question deployed at the moment of difficulty: "Am I in learning mode right now?" If the answer is no, the follow-up is: "What can this situation teach me?" + +### Learning Everywhere + +Darja Kragt's research demonstrates that leadership development need not be confined to the office. Parenting, recreational sport, volunteer work, and community leadership all involve influence, decision-making, and interpersonal dynamics. The leader who experiments with a new coaching approach in their weekend football team before deploying it at work reduces the risk and increases the learning. + +--- + +## Prompts + +**Prompt 1 -- Skill Shelf-Life Audit:** +> Here are my core professional skills and when I last significantly developed each: [list skills and approximate dates]. For each, estimate its current shelf life based on industry trends. Identify the three skills most at risk of obsolescence and recommend a specific learning path for each, using the three-lens framework (value creation, passion, aptitude). + +**Prompt 2 -- Feedback Pattern Analysis:** +> Here is a summary of feedback I have received over the past 12 months: [list key themes from reviews, 360s, informal comments]. Identify recurring patterns, especially those I may have dismissed or classified as one-offs. For each pattern, suggest one experiment I can run in the next 30 days to test whether the feedback reveals a genuine development need. + +**Prompt 3 -- Cross-Training Blueprint:** +> My primary expertise is in [domain]. Identify three complementary skill domains that would amplify the impact of my existing strengths, using Zenger and Folkman's competency-companion model. For each, recommend a specific 30-day learning experiment: what to study, who to learn from, and how to measure progress. + +**Prompt 4 -- Learning Mode Reset:** +> I am currently facing this challenge: [describe challenge]. I suspect I am in performance mode rather than learning mode. Reframe this challenge as a learning opportunity: what skills is it asking me to develop? What can I learn from the difficulty itself? What would I do differently if I treated this as a training exercise rather than a test? + +--- + +## Use Cases + +**Validation-stage founder who knows everything about the product and nothing about sales** + +A technical founder has built an impressive product but cannot close deals. Rather than hiring a sales leader immediately (which the company cannot afford), the founder applies the three-lens framework: sales skills would create value (lens one), the founder finds persuasion intellectually interesting (lens two), and their existing empathy and listening skills provide aptitude (lens three). A 90-day self-directed learning sprint -- combining a sales methodology book, weekly practice calls with a mentor, and deliberate experimentation in customer conversations -- produces enough competence to close the first ten customers personally. + +**Growth-stage leader who resists feedback** + +A VP of engineering has consistently received feedback that they micromanage. Each time, they classify it as a misunderstanding ("I'm just being thorough"). A new coach introduces the breath-and-evaluate technique: when the feedback arrives, pause, do not argue, and then ask "How accurate is this, and how do I know?" The VP begins tracking delegation decisions in a journal. Over eight weeks, a pattern emerges: they intervene in technical decisions that their team leads are fully capable of making. The data -- their own data -- bypasses the defensiveness that external feedback could not penetrate. + +**Scale-stage executive facing technological disruption** + +A chief operating officer recognises that AI is transforming operations but has no technical background in machine learning. Rather than enrolling in a comprehensive course (which would take months the company does not have), the COO identifies three internal data scientists and proposes a learning exchange: the COO teaches them stakeholder management, and they teach the COO enough about AI capabilities to make informed strategic decisions. The cross-training produces mutual understanding in weeks rather than months. + +--- + +## Anti-Patterns + +**1. Treating learning as an event rather than a practice.** A three-day workshop does not produce learning agility. Workshops produce exposure. Agility comes from daily habits: reflection, feedback processing, experimentation. Leaders who "do their learning" at the annual offsite and then revert to default behaviour for eleven months are investing in the appearance of growth. + +**2. Learning only what is comfortable.** The leader who reads five more books on a topic they already understand is deepening expertise, not building agility. Agility requires discomfort -- specifically, the discomfort of being a beginner in a domain where one is accustomed to mastery. + +**3. Collecting knowledge without applying it.** Learning agility is measured by behaviour change, not by the number of books read, courses completed, or podcasts consumed. If six months of learning produce no observable change in how a leader operates, the learning is decorative. + +**4. Confusing learning mode with permissive self-assessment.** "I'm in learning mode" is not an excuse for persistent underperformance. Learning mode is a cognitive orientation that accelerates improvement; it is not a licence to remain indefinitely incompetent. The goal is faster progress, not lower standards. + +**5. Expecting the organisation to drive your learning.** Waiting for the company to offer a training programme, assign a mentor, or create a development plan is a passive posture incompatible with leadership. The most agile learners design their own curriculum and seek their own feedback, using organisational resources as supplements rather than substitutes. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Learning breadth, generalist skills | The founder must learn everything; agility is survival | +| Validation | Customer-facing skills, rapid iteration | Learning speed determines how fast hypotheses are tested | +| Early Traction | Delegation skills, management fundamentals | The founder must learn to lead, not just do | +| Growth | Strategic thinking, organisational design | Learning shifts from functional skills to systems skills | +| Scale | Industry foresight, cross-domain synthesis | Learning becomes about anticipation rather than reaction | + +At idea stage, the founder who cannot learn quickly enough will not survive. Every week brings a new domain to master -- legal, financial, technical, commercial. Learning agility at this stage is not a development aspiration; it is an existential requirement. + +At growth, the learning challenge inverts. The founder who succeeded by being the best individual contributor must now learn to lead other contributors. This transition is among the most common derailment points in company building: the skills that produced early success (deep technical work, hands-on customer contact, personal execution) must be partially surrendered in favour of skills that feel alien (delegation, strategic thinking, organisational design). The leader who cannot make this shift becomes the company's ceiling. + +--- + +## Output Template + +```markdown +# Learning Agility Plan -- [Name] + +**Date:** [Date] +**Current role:** [Title] +**Planning horizon:** [6 months / 12 months] + +## Skill Shelf-Life Audit + +| Skill | Last Major Development | Estimated Shelf Life | Risk Level | +|-------|----------------------|---------------------|------------| +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | +| [Skill] | [Date] | [Years remaining] | [High/Medium/Low] | + +## Next Skill Target + +| Lens | Assessment | +|------|-----------| +| Value creation | [How this skill helps the team/company] | +| Passion | [Level of genuine interest: high/medium/low] | +| Aptitude | [Related existing strengths] | + +**Selected skill:** [Name] +**Learning method:** [Course / Mentor / Cross-training / Self-directed] +**30-day experiment:** [Specific actions and milestones] +**Success indicator:** [Observable behaviour change] + +## Feedback Processing Log + +| Date | Feedback Received | Initial Reaction | After Reflection | Action Taken | +|------|------------------|-----------------|-----------------|-------------| +| [Date] | [Summary] | [Honest first response] | [Revised assessment] | [Experiment or change] | + +## Weekly Reflection Questions +1. What did I learn from this week's experiences? +2. What turned out differently than I expected? +3. Am I in learning mode right now? +``` + +--- + +## Related Skills + +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework provides the psychological foundation for learning agility; this skill provides the daily behavioural layer. +- **[Flow State](../../content/skills/frameworks/flow-state.md)** -- Learning requires periods of deep, focused engagement; flow states accelerate skill acquisition. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness, a core EQ dimension, is the prerequisite for honest skill assessment and feedback receptivity. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Learning requires protected time; without calendar discipline, growth remains aspirational. +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- The vulnerability required for genuine learning is only possible when the leader has sufficient emotional reserves. +- **[AI Learning for Leaders](../../content/skills/ai-leadership/ai-learning-for-leaders.md)** -- Applies the general learning agility principles specifically to AI literacy, the most pressing domain where non-technical leaders must build new competence rapidly. diff --git a/plugins/foreman/skills/learning-from-failure/SKILL.md b/plugins/foreman/skills/learning-from-failure/SKILL.md deleted file mode 120000 index 5182d77..0000000 --- a/plugins/foreman/skills/learning-from-failure/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/learning-from-failure.md \ No newline at end of file diff --git a/plugins/foreman/skills/learning-from-failure/SKILL.md b/plugins/foreman/skills/learning-from-failure/SKILL.md new file mode 100644 index 0000000..64796f5 --- /dev/null +++ b/plugins/foreman/skills/learning-from-failure/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "learning-from-failure" +description: "Builds the leadership capacity to lose well, share mistakes productively, analyse failures alongside successes, overcome perfectionism, and create team environments where setbacks accelerate growth rather than trigger blame. Use when recovering from a major project failure, noticing a blame culture on the team, struggling with personal perfectionism, conducting post-mortems, or seeking to build psychological safety through vulnerability about past errors." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - failure + - psychological-safety + - perfectionism + - resilience + - post-mortem + - learning + - vulnerability + - growth-mindset +related_skills: + - psychological-safety + - growth-mindset + - emotional-courage + - giving-feedback + - radical-candor +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Learning from Failure + +Consider a thought experiment: what if leaders displayed their failures as prominently as their wins? A trophy case in the corner office, but instead of deal tombstones and framed press clippings, it held the pitch deck that lost the account, the product that customers rejected, the hire who left after three months. The idea feels absurd -- and that absurdity reveals how deeply organisations have internalised the fiction that competent leaders do not fail. They do. The research is unambiguous: around 70% of people react poorly to failure, whether by blaming others, denying the problem, or absorbing disproportionate personal guilt. The difference between leaders who grow and those who stagnate is not the frequency of their failures but the quality of their response. + +--- + +## The Framework + +Learning from failure is not a single practice but a constellation of five interlocking disciplines. + +### Discipline 1: Lose Well + +Failure is inevitable; losing badly is optional. "Losing well" is a learnable skill with three distinct strategies: + +**Pivot the effort.** When a project fails, resist the urge to bury it. Step back and ask: what worked in what was tried? Skills, innovations, and ideas developed for a failed initiative rarely lack application -- they simply lack the right context. The creative thinking that produced a failed product may be a perfect fit for a different problem. + +**Reconnect to purpose.** If the work matters for reasons beyond winning, the loss stings less and teaches more. Work is finite -- projects end, companies fold, people leave. But the underlying purpose is not bounded by any single outcome. Leaders who anchor in purpose rather than scoreboard can absorb losses without losing direction. + +**Share the pain.** Losing involves heartbreak, frustration, and sorrow that leaders often feel obligated to suppress. Creating space for the team to acknowledge negative feelings -- to talk about what happened and how it felt -- builds the kind of psychological safety that, paradoxically, enables future risk-taking. Hard times bring people together; ignoring that dynamic wastes its value. + +### Discipline 2: Share Mistakes -- And Lessons + +Psychological safety does not emerge from policy documents. It emerges from leaders modelling the behaviour they want to see. When team members struggle with setbacks, the leader who recounts a time they fell short at work -- explaining what happened, what they felt, and what they did differently afterward -- accomplishes several things simultaneously: they normalise error, they demonstrate that failure is survivable, and they provide a concrete template for learning from it. + +The sharing must include emotional honesty. Mentioning the fear, doubt, or embarrassment that accompanied the mistake is what separates genuine vulnerability from performance. A sanitised war story about a failure that "turned out great in the end" teaches nothing about how to sit with the discomfort of genuine loss. + +### Discipline 3: Analyse Failures Alongside Successes + +One of the most common analytical errors in post-mortems is examining failures in isolation. A team misses a target and discovers that its members were not using the workflow management tool. The obvious remedy: enforce tool adoption. But what if the successful teams were not using it either? Analysing failures without a comparison to successes produces false causation -- solutions to problems that were not actually problems. + +**The comparative method:** + +| Question | Failure Case | Success Case | Genuine Differentiator? | +|----------|-------------|--------------|------------------------| +| What tools were used? | [Describe] | [Describe] | [Yes/No] | +| What processes were followed? | [Describe] | [Describe] | [Yes/No] | +| What resources were available? | [Describe] | [Describe] | [Yes/No] | +| What decisions were made at key junctures? | [Describe] | [Describe] | [Yes/No] | + +Only factors that differ between success and failure cases deserve remediation investment. Everything else is noise. + +### Discipline 4: Respond to Mistakes with Curiosity + +When an employee makes a mistake, the leader's first response sets the cultural tone for every future mistake. Judgement and blame teach people to hide problems. Curiosity and inquiry teach people to surface them early. + +The protocol is straightforward but counter-instinctive: + +1. **Withhold judgment.** Resist the immediate urge to assign blame or express disappointment. +2. **Express curiosity.** Ask what happened, what the person's thinking was, and what assumptions they were operating under. +3. **Adopt a learning mindset.** Recognise that the full picture is not yet visible. The goal is understanding, not sentencing. +4. **Extract the lesson together.** Frame the conversation as a shared investigation, not an interrogation. + +### Discipline 5: Tame Perfectionism + +Perfectionism masquerades as high standards but often functions as a productivity trap. It paralyses decisions (because every choice feels monumental), triggers over-delivery on tasks that need only be adequate, and creates anxiety that compounds with every unfinished project. + +**Three rules for managing perfectionism:** + +- **The three-thought rule.** Once a decision has been considered three times, make the call and move forward. Continued deliberation past this threshold yields diminishing returns and increasing anxiety. +- **The checklist test.** Before starting work, define what "complete" looks like. Once the checklist is satisfied, stop. The inner perfectionist will fret over font choices and semicolons -- the checklist provides an objective exit criterion. +- **The perspective check.** Show a draft to a trusted colleague and ask what it needs to be good enough -- not perfect. Follow their guidance. Perfectionism is often a solitary affliction; external perspective is the antidote. + +--- + +## Prompts + +**Prompt 1 -- Failure Autopsy:** +> I recently experienced a significant failure: [describe the situation, what went wrong, and the outcome]. Walk me through a structured analysis that examines this failure alongside a comparable success. Help me identify which factors genuinely differentiated the failure from the success, and which were common to both. Then recommend specific changes based only on the genuine differentiators. + +**Prompt 2 -- Failure-Sharing Script:** +> I want to share a past failure with my team to build psychological safety. The failure was [describe]. Help me craft a narrative that includes what happened, what I felt (fear, doubt, embarrassment), what I learned, and what I did differently afterward. The tone should be honest without being self-flagellating, and instructive without being preachy. Keep it under three minutes of speaking time. + +**Prompt 3 -- Perfectionism Intervention:** +> I suspect my perfectionism is reducing my effectiveness. My symptoms include [describe -- e.g., difficulty finishing projects, over-preparing for presentations, inability to delegate because no one meets my standards]. Design a personalised set of rules and practices to manage my perfectionism. Be specific -- I need concrete triggers and responses, not general advice about "letting go." + +**Prompt 4 -- Team Failure Response Audit:** +> Analyse how my team currently responds to mistakes. Recent examples include [describe 2-3 instances where someone made an error and how the team/leadership responded]. Assess whether our response pattern builds or erodes psychological safety, and recommend specific changes to our failure response protocol. + +--- + +## Use Cases + +**Idea-Stage Founder Processing a Rejected Pitch** + +A founder pitches twelve investors and receives twelve rejections. The temptation is to interpret this as a verdict on the idea. Instead, the founder applies the comparative method: they analyse the three pitches that generated the most engagement alongside the three that fell flattest. The differentiator is not the idea but the framing -- pitches that led with the customer problem generated follow-up questions; pitches that led with the technology generated polite silence. The failure was not in the concept but in its communication. The thirteenth pitch leads with the problem and closes a pre-seed round. + +**Growth-Stage Engineering Team with a Blame Culture** + +An engineering team conducts post-mortems that reliably identify a person to blame rather than a system to fix. Outages are followed by tense meetings where the engineer who deployed the faulty code is publicly identified. Engineers respond rationally: they deploy less frequently, take fewer risks, and hide problems longer. The VP of Engineering introduces a new post-mortem protocol: no names in incident reports, mandatory curiosity-first questioning, and a requirement that every post-mortem identify at least one systemic factor. Within six months, deployment frequency doubles and mean time to recovery drops by 40%. + +**Scale-Stage Executive Overcoming Personal Perfectionism** + +A COO who built their career on meticulous attention to detail is now responsible for an organisation of 800 people. The perfectionism that served them as an individual contributor is paralysing them as an executive: they rewrite direct reports' presentations, delay strategic decisions while gathering incrementally more data, and hold weekly reviews that last four hours because no detail is too small to examine. Applying the three-thought rule and the checklist test, the COO redesigns their operating rhythm: strategic decisions are made after three rounds of input, presentations are reviewed once with comments rather than rewritten, and weekly reviews are time-boxed to ninety minutes with a pre-circulated agenda. Direct reports begin to take more ownership, and the COO recovers twelve hours per week for strategic work. + +--- + +## Anti-Patterns + +1. **Performing vulnerability.** Sharing a carefully curated failure story that has been polished into a redemption narrative. If the "failure" always ends with "and that's how I became who I am today," it is not vulnerability; it is personal branding. Genuine failure stories include the parts that remain uncomfortable. + +2. **Analysing failure without a success baseline.** Investing in new tools, trainings, and processes based on what failed teams did wrong -- without checking whether successful teams did the same things. This produces plausible but incorrect remediation. + +3. **Treating all failures as learning opportunities.** Some failures result from negligence, dishonesty, or repeated refusal to heed warnings. Not every failure deserves the curiosity-first response. The leader must distinguish between intelligent failures (good-faith efforts in uncertain conditions) and preventable ones (known risks that were ignored). + +4. **Confusing perfectionism with high standards.** High standards produce excellent work within reasonable timeframes. Perfectionism produces excellent work at the cost of everything else -- deadlines, relationships, health, and the team's autonomy. The distinction matters because leaders often defend perfectionism by calling it "commitment to quality." + +5. **Losing without learning.** Absorbing failures stoically without extracting lessons. Resilience without reflection is simply endurance. The goal is not to survive failure but to metabolise it into capability. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Processing personal rejection | Failures at this stage feel existential because the idea and the founder are indistinguishable. Learning to separate self-worth from outcome is the critical skill. | +| Validation | Rapid iteration through failure | The entire stage is designed around failing fast and cheap. Leaders who cannot lose small bets quickly will never find what works. | +| Early Traction | Building team failure norms | As the first team forms, the leader's response to the first mistake sets the cultural template for every mistake that follows. | +| Growth | Institutionalising failure analysis | Post-mortems, retrospectives, and comparative analysis must become organisational habits, not ad-hoc responses to crises. | +| Scale | Preventing perfectionism paralysis | The standards that built the company's reputation can become the rigidity that prevents its adaptation. Leaders must distinguish between standards worth defending and standards worth relaxing. | + +--- + +## Output Template + +```markdown +# Failure Analysis: [Event/Project Name] + +## What Happened +- **Timeline:** [Sequence of events leading to the failure] +- **Expected outcome:** [What was supposed to happen] +- **Actual outcome:** [What did happen] + +## Comparative Analysis +| Factor | This Failure | Comparable Success | Genuine Differentiator? | +|--------|-------------|-------------------|------------------------| +| [Factor 1] | [Description] | [Description] | [Yes/No] | +| [Factor 2] | [Description] | [Description] | [Yes/No] | +| [Factor 3] | [Description] | [Description] | [Yes/No] | + +## Root Cause (Based on Genuine Differentiators Only) +- **Primary cause:** [Description] +- **Contributing factors:** [Description] +- **Systemic vs. individual:** [Was this a system failure or a person failure?] + +## Emotional Inventory +- **What the team felt:** [Honest assessment] +- **What was expressed:** [What was actually said] +- **Gap:** [What was suppressed and why] + +## Lessons and Changes +| Lesson | Specific Change | Owner | Timeline | +|--------|----------------|-------|----------| +| [Lesson 1] | [Action] | [Person] | [When] | +| [Lesson 2] | [Action] | [Person] | [When] | + +## What to Carry Forward +- [Skills, ideas, or innovations from this failure that deserve a new context] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- The organisational condition that makes learning from failure possible; without it, failures are hidden rather than examined. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- The cognitive orientation that treats failure as data rather than verdict; growth mindset is the individual prerequisite for the team practices described here. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Sharing failures authentically and responding to mistakes with curiosity both require emotional courage that must be deliberately built. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- Post-failure conversations are a specialised form of feedback; the same principles of specificity, timing, and psychological safety apply. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- Provides the philosophical foundation for embracing failure as a source of growth rather than merely tolerating it as an inevitable cost. +- **[Managing Weakness and Mistakes](../../content/skills/thinking/managing-weakness-and-mistakes.md)** -- Extends the failure analysis into systematic safeguards and mistake-handling protocols that prevent recurring failures. diff --git a/plugins/foreman/skills/lewin-leadership-styles/SKILL.md b/plugins/foreman/skills/lewin-leadership-styles/SKILL.md deleted file mode 120000 index 0a7d093..0000000 --- a/plugins/foreman/skills/lewin-leadership-styles/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/lewin-leadership-styles.md \ No newline at end of file diff --git a/plugins/foreman/skills/lewin-leadership-styles/SKILL.md b/plugins/foreman/skills/lewin-leadership-styles/SKILL.md new file mode 100644 index 0000000..d07624a --- /dev/null +++ b/plugins/foreman/skills/lewin-leadership-styles/SKILL.md @@ -0,0 +1,175 @@ +--- +name: "lewin-leadership-styles" +description: "Assesses leadership approach using Lewin's three styles: autocratic, democratic, and laissez-faire. Evaluates the fit between a leader's dominant style and their organizational context. Use when diagnosing team dysfunction caused by management style, transitioning from founder-led to distributed decision-making, navigating a crisis requiring temporary style shifts, or auditing the founding team's leadership dynamics." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - leadership + - management-style + - team-dynamics + - organizational-culture + - decision-making +related_skills: + - situational-leadership + - tuckman-team-stages + - belbin-team-roles + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Lewin's Leadership Styles + +Imagine three identical teams of ten people, each given the same project, the same deadline, and the same resources. The only variable is the leader. Team A's leader makes every decision, assigns every task, and monitors every output. Team B's leader sets the vision, then asks the team how they want to get there. Team C's leader says "figure it out" and retreats to their office. Kurt Lewin ran essentially this experiment in 1939 with groups of children -- and the results mapped with uncomfortable precision onto dynamics that play out in every startup, corporation, and nonprofit today. The autocratic group produced more output but lower quality and collapsed when the leader left. The democratic group produced slightly less volume but far higher quality and sustained performance independently. The laissez-faire group produced the least, with the most frustration and the worst interpersonal dynamics. + +Three styles. Three radically different organizational outcomes. Lewin's framework remains the foundation upon which all subsequent leadership theory was built. + +--- + +## The Framework + +Lewin identified three primary leadership styles along a spectrum of control. The framework is descriptive (leaders tend toward one style) and prescriptive (certain contexts reward certain styles). + +### The Three Styles Compared + +| Dimension | Autocratic | Democratic | Laissez-Faire | +|-----------|-----------|------------|---------------| +| **Decision authority** | Leader decides alone | Leader facilitates group input, then decides or delegates | Leader abdicates decision-making | +| **Communication flow** | Top-down, directive | Bidirectional, consultative | Minimal, reactive | +| **Team autonomy** | Low; tasks are assigned with specific instructions | Moderate; team participates in planning and execution choices | High in theory, chaotic in practice | +| **Speed of decisions** | Fast | Moderate | Slow or absent | +| **Innovation** | Low; risk-aversion dominates | High; diverse perspectives surface | Variable; depends entirely on team capability | +| **Team morale** | Low long-term; resentment builds | High; ownership breeds engagement | Low; absence of guidance feels like abandonment | +| **Quality of output** | Variable; depends on leader's expertise | Consistently high; collective intelligence corrects errors | Typically low; no quality standards enforced | +| **Scalability** | Poor; bottleneck at the leader | Strong; distributed decision-making scales | Unpredictable; works only with exceptional self-managing teams | +| **Leader absence impact** | Severe; work stops or quality collapses | Minimal; team continues autonomously | None; the leader was already functionally absent | + +### Autocratic Leadership + +The autocratic style concentrates authority in the leader. Decisions are made without consultation. Execution follows prescribed instructions. This style produces rapid decision-making and clear accountability -- valuable during crises, turnarounds, or situations requiring strict compliance. The cost is suppressed initiative, hidden information (team members withhold bad news from directive leaders), and a single point of failure. + +Founders default to this style more frequently than they realize. The founding period demands rapid, intuitive decision-making, and the habit persists long after the team has grown beyond the point where one brain can hold all relevant context. + +### Democratic Leadership + +The democratic style distributes authority while retaining ultimate responsibility. The leader sets direction, solicits input, facilitates deliberation, and either makes the final call or delegates it to the most capable team member. This is the style most consistently associated with high performance, innovation, and retention in Lewin's research and in subsequent decades of organizational studies. + +The cost is speed. Democratic processes take longer than autocratic ones. For startups racing against runway, this tradeoff is real. The art lies in knowing which decisions warrant democratic process and which do not. + +### Laissez-Faire Leadership + +The laissez-faire style delegates almost all authority and provides minimal guidance. Lewin's research consistently showed this style producing the worst outcomes -- not because autonomy is bad, but because laissez-faire as Lewin defined it implies abdication rather than intentional empowerment. + +The distinction matters enormously. A leader who deliberately builds systems, hires exceptional people, and then steps back is not practicing laissez-faire -- they are practicing high-trust democratic leadership. Lewin's laissez-faire leader provides neither structure nor support. The team is not liberated; it is abandoned. + +--- + +## Prompts + +**Prompt 1 -- Leadership Style Self-Assessment:** +> Based on the following description of how I typically lead my team, assess which of Lewin's three leadership styles I default to and how that style is affecting our performance. Here's how I operate: [describe your decision-making process, communication patterns, how you handle disagreements, how much autonomy you give team members, how you respond when things go wrong]. Identify the strengths of my current style, the costs I may not be seeing, and specific situations where I should consciously shift to a different style. + +**Prompt 2 -- Situational Style Selection:** +> I'm facing the following leadership challenge: [describe situation -- e.g., "We need to pivot our product in 4 weeks with a team of 8" or "We're scaling from 15 to 50 people and decisions are getting slower"]. Using Lewin's framework, which leadership style should I adopt for this specific situation and why? What would the autocratic, democratic, and laissez-faire approaches each look like here, and what are the risks of each? + +**Prompt 3 -- Team Dynamics Diagnosis:** +> My team is exhibiting these behaviors: [describe -- e.g., "People wait for me to make every decision," "Nobody takes initiative," "There's a lot of resentment about micromanagement," "We have great ideas but can't execute"]. Using Lewin's leadership styles framework, diagnose which leadership style is likely producing these symptoms, and recommend a transition plan to a more effective style for our context. + +**Prompt 4 -- Leadership Style Audit for the Founding Team:** +> Our founding team consists of [number] co-founders with these roles: [describe]. Each of us leads differently. Map each co-founder's style to Lewin's framework based on these descriptions: [describe each person's approach]. Analyze where our styles complement each other, where they conflict, and how we should allocate leadership responsibilities based on which style each situation demands. + +--- + +## Use Cases + +**Founder Transition from Autocratic to Democratic** + +A validation-stage fintech founder built the first version of the product through sheer force of will -- making every product decision, writing much of the code, dictating design choices. The company survived. Now at 20 employees, the same autocratic instincts are causing the best engineers to leave. Exit interviews reveal a consistent theme: "I felt like a pair of hands, not a brain." Applying Lewin's framework, the founder recognizes that the style appropriate for a three-person garage operation is toxic at the current scale. The transition plan involves categorizing decisions into three tiers: strategic (founder decides after consultation), tactical (team leads decide with founder input), and operational (team members decide autonomously). The shift is uncomfortable. Decisions take longer. But within six months, retention stabilizes and product velocity actually increases because the founder is no longer the bottleneck. + +**Crisis Requiring Temporary Autocratic Shift** + +A growth-stage e-commerce company with a normally democratic culture discovers a critical security breach exposing customer payment data. The CEO, who typically runs collaborative decision-making processes, recognizes that this moment demands autocratic leadership: clear commands, no debate, immediate execution. She assigns specific tasks to specific people, sets 30-minute check-in cycles, and makes every escalation decision herself for 72 hours. Once the crisis is contained, she deliberately shifts back to democratic mode for the post-mortem and remediation planning. Lewin's framework provides the vocabulary for this conscious style-switching -- and the team understands the shift because the CEO names it explicitly. + +--- + +## Anti-Patterns + +- **Permanent Autocracy Disguised as Startup Necessity.** The belief that startups require autocratic leadership indefinitely. Early-stage founding demands fast, centralized decisions -- but failing to evolve toward democratic leadership as the team grows is a primary driver of co-founder conflict and early-employee exodus. The startup excuse has an expiration date. + +- **Laissez-Faire as Flatness Ideology.** Adopting a leaderless or flat organizational structure and believing it represents enlightened management. Without deliberate structure, clear accountability, and active facilitation, "flat" organizations devolve into laissez-faire dysfunction: invisible hierarchies, diffused responsibility, and decision paralysis. Valve, GitHub, and other companies that experimented with radical flatness have documented the resulting pathologies extensively. + +- **Style Rigidity Across Contexts.** Applying the same style to every situation regardless of circumstances. A democratic process for deciding whether to evacuate a burning building is as dysfunctional as an autocratic process for designing a creative campaign. Lewin's framework is descriptive of tendencies but prescriptive of flexibility. + +- **Confusing Democratic with Consensus.** Believing democratic leadership means everyone must agree. Democratic leadership means everyone's input is heard and considered. The leader still decides. Consensus-seeking produces the worst of both worlds: the slowness of democracy without the decisiveness of autocracy. + +--- + +## By Stage + +| Stage | Recommended Dominant Style | Key Difference | +|-------|---------------------------|----------------| +| Idea | Autocratic with democratic elements | The founder's vision drives direction; small team size makes full democracy unnecessary, but co-founder input is essential | +| Validation | Democratic-leaning | Rapid experimentation benefits from diverse perspectives; the team must feel ownership of pivots | +| Early Traction | Democratic | Decision-making must distribute as the team grows beyond the founder's cognitive bandwidth | +| Growth | Democratic with role-based authority | Functional leaders adopt their own styles within their domains; founder sets culture and strategy | +| Scale | Institutional democratic | Formal processes, clear decision rights, and cultural norms replace the founder's personal style as the organizing principle | + +--- + +## Output Template + +```markdown +# Leadership Style Assessment: [Leader/Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Company Stage:** [Stage] + +## Current Style Profile + +| Leader/Role | Dominant Style | Secondary Style | Context Appropriateness | +|-------------|---------------|-----------------|------------------------| +| [Name] | [Autocratic/Democratic/Laissez-Faire] | [Style] | [High/Medium/Low] | + +## Situational Analysis + +### Decisions That Should Be Autocratic +- [Decision type]: [Why speed/clarity outweighs input] + +### Decisions That Should Be Democratic +- [Decision type]: [Why diverse input improves outcomes] + +### Decisions That Can Be Fully Delegated +- [Decision type]: [Why the team member is best positioned] + +## Transition Recommendations +1. [Specific behavior change] +2. [Specific process change] +3. [Specific communication change] + +## Risks of Current Style at Current Stage +- [Risk 1] +- [Risk 2] + +## Success Metrics +- [How you'll know the style shift is working] +``` + +--- + +## Related Skills + +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- Hersey and Blanchard's framework extends Lewin by matching leadership style to follower maturity, providing a more granular decision model for style-switching. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- The stage of team development influences which leadership style is most effective; forming teams need more direction, performing teams need less. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman's research shows that the leader's primary job is creating conditions for team success, which aligns with democratic rather than autocratic leadership. +- **[Leadership Style Adaptation](../../content/skills/leadership/leadership-style-adaptation.md)** -- Provides practical guidance for shifting between leadership styles in response to context, extending Lewin's theoretical taxonomy into daily practice. +- **[Decision Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Crisis situations often demand a temporary shift to autocratic leadership; this skill addresses how to make that shift deliberately and return to democratic mode afterward. diff --git a/plugins/foreman/skills/managing-up/SKILL.md b/plugins/foreman/skills/managing-up/SKILL.md deleted file mode 120000 index 2a2a972..0000000 --- a/plugins/foreman/skills/managing-up/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/managing-up.md \ No newline at end of file diff --git a/plugins/foreman/skills/managing-up/SKILL.md b/plugins/foreman/skills/managing-up/SKILL.md new file mode 100644 index 0000000..01b997a --- /dev/null +++ b/plugins/foreman/skills/managing-up/SKILL.md @@ -0,0 +1,193 @@ +--- +name: "managing-up" +description: "Guides leaders in building effective upward relationships with their managers and senior executives. Covers keeping bosses informed, demonstrating strategic thinking to skip-level leaders, understanding a manager's goals and pressures, setting realistic expectations, and proactively managing the information flow. Use when feeling undervalued by leadership, preparing for skip-level meetings, navigating a new boss relationship, seeking promotion readiness, or clarifying expectations with a manager." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - managing-up + - boss-relationship + - career-advancement + - strategic-visibility + - communication + - skip-level + - expectations +related_skills: + - trust-equation + - radical-candor + - giving-feedback + - strategic-thinking-and-alignment + - emotional-courage +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Managing Up + +The most career-defining skill nobody teaches is invisible by design. Managing up -- the deliberate cultivation of a productive relationship with one's boss -- receives no curriculum in business school, no chapter in the onboarding manual, and no line item in the performance review. Yet the gap between what a leader accomplishes and what their boss perceives them as accomplishing determines promotions, resource allocation, and institutional survival more reliably than raw competence ever will. The uncomfortable truth is that talent unwitnessed is talent wasted. Effective leaders do not merely perform; they ensure the right people understand what they are performing, why it matters, and how it connects to the organisation's strategic arc. + +--- + +## The Framework + +Managing up is not flattery, nor is it political manoeuvring. It is a structured practice built on four pillars: information management, strategic visibility, boss comprehension, and expectation calibration. + +### Pillar 1: Information Management -- Close the Gap + +Most leaders dramatically underestimate how much information their boss needs. The assumption that a competent manager "already knows" is both common and dangerous. Bosses operate under information asymmetry by default: they manage multiple reports, navigate competing priorities, and cannot read minds. The effective leader treats upward information flow as a design problem, not an afterthought. + +**The information gap manifests in two directions:** + +- **Under-reporting:** Assuming the boss knows more than they do. Projects stall, problems escalate, and the boss is blindsided -- all because a direct report confused autonomy with silence. +- **Over-reporting:** Flooding a manager with granular detail, forcing them to extract signal from noise. This is not diligence; it is delegation of cognitive work upward. + +The discipline lies in matching information type, frequency, and format to the boss's actual needs. Some managers want a daily stand-up summary. Others want to hear nothing until something is on fire. Neither preference is wrong; failing to learn it is. + +### Pillar 2: Strategic Visibility -- Be Witnessed Thinking + +Competence alone does not earn advancement. Senior executives need to witness strategic thinking in action. This means preparing for meetings not merely to contribute but to demonstrate the altitude of one's perspective. Before a strategy session, the effective leader blocks time to think through the agenda, considers cross-departmental implications, and prepares a point of view that shows they are not thinking in a vacuum. + +**Three methods for demonstrating strategic thinking:** + +1. **Reframe operational updates as strategic contributions.** Instead of "We shipped feature X on time," try "Feature X positions us to capture the mid-market segment three months ahead of the competitor timeline." +2. **Ask questions that reveal long-term thinking.** In skip-level conversations, ask about five-year milestones, industry trends the team should respond to, or how the team's contributions might evolve given strategic priorities. +3. **Play CEO for a day.** Periodically imagine holding the top job and viewing current meetings, projects, and emails from that vantage. What value would a CEO find in the work? What would they change? + +### Pillar 3: Boss Comprehension -- Map Their World + +To manage up effectively, a leader must understand the boss's operating context with granular precision. This is not about manipulation; it is about alignment. The essential map includes: + +| Dimension | Questions to Answer | +|-----------|-------------------| +| Goals | What are their organisational and personal objectives? | +| Pressures | What demands come from their peers, their own boss, and the board? | +| Working style | Do they prefer email, meetings, instant messages, or hallway conversations? | +| Strengths | Where do they excel, and where can you complement their gaps? | +| Weaknesses | What do they struggle with, and how can you shield them without overstepping? | +| Decision patterns | Do they decide quickly or deliberate? Do they want options or recommendations? | + +This mapping must be refreshed continuously. A boss's priorities shift with quarterly targets, organisational restructuring, and personal circumstances. The leader who mapped their boss's world in January and stopped paying attention by March is operating on stale intelligence. + +### Pillar 4: Expectation Calibration -- Ask, Don't Assume + +The burden of understanding what the boss expects falls on the direct report -- not the other way around. Formal systems like planning processes and performance reviews provide a skeleton, but they never capture the full picture. Expectations exist on a spectrum from broad ("what kinds of problems should I escalate?") to granular ("what format should interim project reports take?"). The leader who passively assumes they know what their boss expects is building on sand. + +Two corrective habits: + +- **Proactive clarification:** At the start of any significant project, explicitly ask what success looks like from the boss's perspective, what updates they want, and what decisions they wish to be consulted on. +- **Realistic boss expectations:** Accept that most managers are not mind-readers. They have competing demands and limited bandwidth. Rather than resenting what the boss fails to provide, take responsibility for articulating what is needed. + +--- + +## Prompts + +**Prompt 1 -- Boss Communication Audit:** +> Analyse my current communication pattern with my boss. I report to [describe role and style of your boss]. My typical update frequency is [describe]. My boss's preferred communication channels are [describe]. Identify gaps in my information flow: Am I under-reporting, over-reporting, or mismatching format to preference? Design a communication cadence that matches my boss's needs while keeping me efficient. + +**Prompt 2 -- Skip-Level Meeting Preparation:** +> I have a meeting with my boss's boss [describe their role and what you know about their priorities]. Prepare five strategic questions I can ask that demonstrate long-term thinking about the business, awareness of industry trends, and understanding of how my team's work connects to company strategy. The questions should feel natural, not performative. + +**Prompt 3 -- Boss Mapping Exercise:** +> Help me build a comprehensive profile of my boss. Here is what I know: [describe their goals, pressures, working style, strengths, and weaknesses as best you can]. Identify blind spots in my understanding and suggest specific observations or conversations that would fill them. Then recommend three adjustments to how I work with them based on this profile. + +**Prompt 4 -- Expectation Alignment Conversation:** +> I suspect my boss and I are not aligned on expectations for [describe project or role area]. Draft a conversation framework that lets me clarify their expectations without seeming uncertain or incompetent. Include specific questions to ask and phrases that signal proactive ownership rather than dependency. + +--- + +## Use Cases + +**Growth-Stage CTO Preparing for Board Visibility** + +A CTO at a Series B company does excellent technical work but is invisible to the board. The CEO fields all board questions about the technology roadmap. The CTO applies boss comprehension to understand the CEO's board pressures, then offers to prepare a quarterly technology brief that the CEO can present -- or, better, that the CTO can present directly. By framing this as reducing the CEO's preparation burden rather than as a personal visibility play, the CTO gains board exposure without threatening the CEO's authority. Within two quarters, board members begin directing technical questions to the CTO directly. + +**Early-Traction Founder Managing an Investor-Board Chair** + +A first-time founder treats their lead investor like a passive shareholder, sending updates only when milestones are hit. The investor grows anxious and begins making back-channel inquiries to team members. The founder recalibrates by mapping the investor's information needs: monthly updates sent on the same day, proactive flagging of risks alongside wins, and a quarterly phone call to discuss strategic direction. The investor's anxiety drops, back-channel inquiries stop, and the relationship shifts from surveillance to partnership. + +**Scale-Stage VP Navigating a New Boss** + +A VP of Product has thrived under a hands-off CEO for three years. A new CEO arrives with a detail-oriented style and expects weekly written updates. The VP initially bristles, interpreting the request as micromanagement. After applying the boss comprehension framework, the VP recognises that the new CEO is under board pressure to demonstrate operational control during a strategic pivot. The VP redesigns their reporting format to match the CEO's needs, and what felt like surveillance becomes a vehicle for demonstrating strategic alignment. + +--- + +## Anti-Patterns + +1. **Confusing managing up with managing impressions.** Managing up is about alignment and effectiveness, not about curating a personal brand. The leader who manages up well solves real problems for their boss; the one who manages impressions solves only their own visibility problem. Bosses eventually distinguish between the two. + +2. **Waiting for the boss to create the relationship.** A pervasive and costly passivity. The assumption that a good boss will proactively provide information, clarity, and development is reasonable in theory and unreliable in practice. Most managers are overwhelmed. The direct report who waits will wait a long time. + +3. **Treating all bosses identically.** Applying the same communication style, frequency, and format to every manager is a failure of adaptation. A data-driven CFO and a relationship-driven Chief People Officer require fundamentally different upward management strategies. + +4. **Bypassing your boss to impress their boss.** Skip-level visibility is valuable only when the direct boss supports it. Going around a manager to build relationships with senior leaders creates distrust that no amount of strategic questioning can repair. + +5. **Assuming expectations are static.** Clarifying expectations once and never revisiting them. Priorities shift, contexts change, and what mattered in Q1 may be irrelevant by Q3. Expectation calibration is a recurring practice, not a one-time conversation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Investor-as-boss management | The "boss" is often a lead investor or advisor. Information flow and expectation alignment directly affect funding continuity. | +| Early Traction | First manager relationships | Founders begin hiring leaders who report to them while they themselves report to a board. Managing in both directions simultaneously is a new skill. | +| Growth | Skip-level visibility | As layers multiply, the leader's relationship with their boss's boss becomes strategically important. Demonstrating strategic thinking to senior executives determines career trajectory. | +| Scale | Institutional upward management | Managing up becomes systemic: executive communication cadences, board reporting rhythms, and cross-functional alignment processes replace individual boss relationships. | + +At every stage, the foundational principle holds: the burden of the relationship falls on the person who has the most to gain from its effectiveness -- which is almost always the direct report. + +--- + +## Output Template + +```markdown +# Upward Relationship Audit: [Boss Name / Role] + +## Boss Profile +- **Goals (organisational):** [What they are measured on] +- **Goals (personal):** [What they care about beyond metrics] +- **Key pressures:** [From their boss, board, peers, or market] +- **Preferred communication:** [Channel, frequency, format] +- **Decision style:** [Quick vs. deliberative; options vs. recommendations] +- **Strengths I can leverage:** [Where they excel] +- **Gaps I can complement:** [Where they need support] + +## Current Information Flow Assessment +| Dimension | Current State | Ideal State | Gap | +|-----------|--------------|-------------|-----| +| Update frequency | [Current] | [Needed] | [Over/Under/Matched] | +| Update format | [Current] | [Preferred] | [Aligned/Misaligned] | +| Risk escalation | [Current pattern] | [Expected pattern] | [Gap description] | +| Strategic context | [How much I provide] | [How much is needed] | [Gap description] | + +## Expectation Alignment +- **Confirmed expectations:** [What has been explicitly discussed] +- **Assumed expectations:** [What I think they expect but have not confirmed] +- **Unknown expectations:** [Areas where I have no clarity] + +## 30-Day Action Plan +| Week | Action | Purpose | +|------|--------|---------| +| 1 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 2 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 3 | [Specific action] | [Alignment, visibility, or comprehension goal] | +| 4 | [Specific action] | [Alignment, visibility, or comprehension goal] | +``` + +--- + +## Related Skills + +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- The trust a boss places in a direct report is decomposable into credibility, reliability, intimacy, and self-orientation; managing up is the practice of building all four deliberately. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Upward candor -- telling a boss what they need to hear rather than what they want to hear -- is a high-risk, high-reward form of managing up. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- Providing constructive upward feedback to a boss requires all four pillars of managing up to be functioning; without trust and comprehension, upward feedback backfires. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- Strategic visibility with senior leaders is the outward expression of strategic thinking capability; the two skills are mutually reinforcing. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Effective delegation creates the time and headspace required for upward relationship management; leaders who cannot delegate cannot manage up. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Delivering bad news upward and pushing back on a boss's flawed direction require the incremental courage-building practices this companion skill develops. diff --git a/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md b/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md deleted file mode 120000 index 8f6fb4e..0000000 --- a/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/managing-weakness-and-mistakes.md \ No newline at end of file diff --git a/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md b/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md new file mode 100644 index 0000000..f9fc1ea --- /dev/null +++ b/plugins/foreman/skills/managing-weakness-and-mistakes/SKILL.md @@ -0,0 +1,238 @@ +--- +name: "managing-weakness-and-mistakes" +description: "Provides a systematic approach to protecting against predictable decision failures and extracting maximum learning from errors, using the Clear Thinking safeguard architecture and mistake-handling protocol. Covers knowing your weaknesses (biological and acquired), building safeguards (prevention, automatic rules, friction, guardrails, perspective shifts), and the four-step process for handling mistakes without ego contamination. Use when repeating the same errors across decisions, needing to design pre-commitment rules for high-pressure situations, building organisational error-recovery processes, or recognising that a cover-up is compounding an initial mistake." +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - clear-thinking + - safeguards + - decision-rules + - mistake-handling + - weakness-management + - blind-spots + - checklists + - pre-commitment + - error-recovery + - clear-thinking-framework +related_skills: + - enemies-of-clear-thinking + - building-thinking-strength + - thinking-fast-and-slow + - decision-making-under-pressure + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-pragmatism +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Managing Weakness and Mistakes + +SAFEGUARD. The best decision-makers are not more intelligent -- they are better at protecting themselves against themselves. The Clear Thinking framework's third principle completes a system that begins with diagnosis (identifying the four defaults) and progresses through construction (building the four strength pillars). This final layer addresses the uncomfortable truth that strength alone is insufficient. Every person has weaknesses that no amount of self-control or self-knowledge can eliminate entirely -- biological constraints, cognitive blind spots, acquired habits with roots deeper than willpower can reach. The solution is not to pretend these weaknesses do not exist but to engineer an environment in which they cannot cause catastrophic damage. And when mistakes inevitably occur despite every safeguard, the protocol for handling them determines whether they become learning or compounding liability. + +The framework draws a distinction that most leadership literature ignores: the difference between weaknesses that can be overcome through strength and weaknesses that require structural protection. A founder who becomes impulsive when sleep-deprived cannot "strength" their way through a red-eye flight into a board meeting. The biology is non-negotiable. What they can do is build a safeguard: a rule that no irreversible decisions are made within twelve hours of overnight travel. The safeguard does not fix the weakness. It makes the weakness irrelevant. + +--- + +## The Framework + +### Part 1: Knowing Your Weaknesses + +The framework categorises weaknesses into two types, each requiring a different management approach. + +**Inbuilt weaknesses** are biological constraints no human can eliminate: hunger, fatigue, sleep deprivation, emotional volatility, stress responses, cognitive biases, and the inherent limitations of individual perspective. These are features of the hardware, not bugs in the software. They cannot be overcome through character development. They can only be managed through safeguards. + +**Acquired weaknesses** are patterns of behaviour absorbed through habit and reinforced by inertia: acting on impulse, doing less than one is capable of, refusing to start due to fear, seeing only one's own point of view, coasting on talent without effort. These can be addressed through the strength pillars (self-accountability, self-knowledge, self-control, self-confidence) but often benefit from safeguards as well, because willpower is a depletable resource. + +The formula for failure, the text observes, is a few small errors consistently repeated. The insidiousness lies in the delay between action and consequence. Skipping one strategic review causes no immediate harm. Skipping twelve creates a strategic drift that may take years to reverse. The compound interest of bad habits works silently until the bill arrives all at once. + +**Blind spots deserve special attention.** Three forces conspire to prevent founders from seeing their own weaknesses: + +1. **Habituation.** Flawed patterns feel normal because they have become ingrained through repetition. The founder who micromanages does not experience micromanagement as a weakness; they experience it as diligence. +2. **Ego protection.** Acknowledging a deep behavioural flaw feels like a referendum on character, not a correctable process error. The ego default actively shields weaknesses from conscious inspection. +3. **Limited perspective.** No one can fully see a system they are part of. The founder's future self will look back at the current self with the same bewildered clarity that the current self reserves for the teenage self. + +Richard Feynman's principle applies: "The first principle is that you must not fool yourself -- and you are the easiest person to fool." The corollary for entrepreneurs: the people around you can likely catalogue your weaknesses with disturbing accuracy. The question is whether you have created conditions safe enough for them to share that knowledge. + +### Part 2: Building Safeguards + +Safeguards are tools for protecting yourself from yourself. The framework identifies five strategies, each suited to different weakness profiles. + +**Strategy 1: Prevention.** Avoid making decisions under conditions known to degrade judgment. The HALT framework (Hungry, Angry, Lonely, Tired) from Alcoholics Anonymous applies directly to entrepreneurial decision-making. Before any significant decision, ask: Am I hungry? Am I emotionally activated? Am I isolated or in an unfamiliar environment? Am I fatigued or sleep-deprived? If yes to any, defer the decision. The cost of delay is almost always less than the cost of a default-driven error. + +For founders, this translates into calendar discipline. No term-sheet negotiations after investor dinners that run past midnight. No personnel decisions on the day a major customer churns. No strategic pivots during the adrenaline spike of a competitor's product launch. Prevention is not avoidance; it is timing. + +**Strategy 2: Automatic Rules.** Replace repeated decisions with predetermined rules that require no deliberation and invite no social pushback. The key insight, drawn from a conversation with Daniel Kahneman: "People question decisions, but they respect rules." + +Kahneman's own favourite rule -- never say yes to a request on the phone -- illustrates the principle. The rule eliminates the social default's real-time pressure, creates space for genuine evaluation, and allows many low-value requests to dissolve naturally when the requestor does not follow up. + +Entrepreneurial examples: +- "No hiring decisions without 48 hours between final interview and offer." +- "No strategic commitments during fundraising -- the emotional volatility of the process contaminates judgment." +- "No meetings before lunch -- the morning belongs to the highest-leverage work." + +The power of automatic rules is that they remove the decision from the moment of vulnerability. The rule is made once, under conditions of clear thinking, and then enforced mechanically regardless of the emotional state at the time of execution. + +**Strategy 3: Friction.** Increase the effort required to do things that are contrary to long-term goals. The formulation is precise: "Behaviour follows the path of least resistance." If checking email is easier than writing the strategic plan, email will win. The solution is not more willpower but more friction on the undesirable path. + +Entrepreneurial applications: +- Removing Slack notifications during deep-work blocks (friction on distraction). +- Requiring a written one-page analysis before any meeting can be scheduled to discuss a new initiative (friction on reactive meetings). +- Making it easier to consult the decision framework than to skip it (reducing friction on the desired behaviour while increasing it on the default). + +**Strategy 4: Guardrails -- Checklists and Operating Procedures.** Formulate decision procedures that force a pause and redirect attention to fundamentals. Pilots use preflight checklists not because they are forgetful but because even experts, under routine conditions, skip steps. The same logic applies to founders making recurring high-stakes decisions. + +A pre-investment checklist: "Have I verified the thesis with someone who disagrees? Have I identified the three most likely failure modes? Have I stress-tested the financial model with pessimistic assumptions? Am I making this decision under favourable cognitive conditions?" Each question is a guardrail preventing the defaults from steering unchecked. + +**Strategy 5: Perspective Shifts.** Deliberately adopt frames of reference beyond your own to reveal blind spots that are structurally invisible from your current vantage point. + +The text cites the transformation of the USS Benfold, one of the worst-performing warships in the US Navy. Commander Michael Abrashoff changed nothing about the crew, technology, or hierarchy. He changed his own perspective -- looking at the ship from the ordinary sailors' vantage point rather than the officers'. The insight was as simple as waiting in the food line instead of cutting to the front. Within twenty months, the Benfold became one of the fleet's top performers. + +The entrepreneurial parallel: a founder who asks "What does this decision look like from the perspective of a new hire? A departing customer? A competitor?" is performing a perspective-shift safeguard. The technique described -- stating your understanding of the other person's view and then asking "What did I miss?" followed by "What else did I miss?" -- converts a blind spot into a data-gathering protocol. + +### Part 3: Handling Mistakes + +When safeguards fail and mistakes occur, the response determines whether the mistake becomes a one-time cost or a compounding liability. The observation is characteristically blunt: "The biggest mistake people make typically isn't their initial mistake. It's the mistake of trying to cover up and avoid responsibility for it. The first mistake is expensive; the second one costs a fortune." + +Three problems with covering up mistakes: + +1. **Learning is blocked.** If the mistake is hidden, its causes remain unexamined, and the same error will recur. +2. **Hiding becomes habitual.** Each successful cover-up lowers the threshold for the next one, until deception becomes the default response to failure. +3. **The cover-up compounds the damage.** The cover-up introduces new risks (discovery, loss of trust, legal exposure) that dwarf the original error. + +**The Four-Step Protocol:** + +**Step 1: Accept responsibility.** Acknowledge your contribution to the mistake without deflecting to external factors. This requires the self-accountability and self-control pillars to be functional -- the emotion default will fight aggressively to shift blame, and the ego default will construct elaborate narratives of victimhood. If the internal dialogue includes phrases like "this isn't fair" or "they should have," the acceptance is incomplete. + +**Step 2: Learn from the mistake.** Examine the thoughts, feelings, and actions that produced the error. If this examination produces defensiveness or blame, return to Step 1. The learning is incomplete until the founder can describe their own contribution to the failure without qualification. The framework notes that the ego distorts memory to make us look better than we actually were -- which is why decisions and their reasoning should be recorded in writing at the time they are made, not reconstructed after the fact. + +**Step 3: Commit to doing better.** Formulate a specific plan -- either a new strength practice or a new safeguard -- that addresses the root cause. Vague commitments ("I'll be more careful next time") are the ego default wearing the costume of accountability. Concrete commitments ("I will implement a 48-hour cooling period before responding to any communication that triggers a defensive emotional reaction") are operational changes. + +**Step 4: Repair the damage.** Where possible, repair the consequences. The longer the prior relationship and the more consistent the prior behaviour, the more repairable the damage. Repair requires sustained consistency, not a single gesture. Any immediate deviation reverses the repair and confirms the original failure as a pattern rather than an exception. + +--- + +## Prompts + +**Prompt 1 -- Weakness Inventory:** +> Help me build an honest weakness inventory for myself as a founder. Here is my current context: [stage, role, team size, key challenges]. Categorise my likely weaknesses into inbuilt (biological/cognitive) and acquired (habitual/behavioural). For each, assess whether it requires strength-building, a safeguard, or both. Then prioritise: which weakness, if left unaddressed, poses the greatest compounding risk over the next 12 months? + +**Prompt 2 -- Safeguard Architecture:** +> Design a safeguard system for these recurring decision failures: [describe 3-4 patterns of poor decisions or repeated errors]. For each pattern, recommend the most appropriate safeguard strategy (prevention, automatic rule, friction, guardrail, or perspective shift). Be specific -- give me the exact rule, checklist, or environmental change to implement, not a general principle. + +**Prompt 3 -- Mistake Post-Mortem:** +> I made this mistake: [describe the mistake, the decision that led to it, and the outcome]. Walk me through the four-step protocol. At each step, challenge me if my language contains deflection, blame, or vague commitments. Help me identify the root cause, design a specific safeguard or strength practice to prevent recurrence, and assess what damage repair is needed and feasible. + +**Prompt 4 -- Blind Spot Probe:** +> Based on what you know about founders at my stage ([stage]) with my profile ([describe background, team dynamics, market]), what are the three most statistically likely blind spots I am carrying? For each, describe why I probably cannot see it from my current vantage point, what perspective shift would reveal it, and what question I should ask my team or advisors to surface it. + +--- + +## Use Cases + +**Validation-Stage EdTech Founder Who Keeps Repeating the Same Partnership Error** + +An edtech founder has pursued three consecutive school-district partnerships, and each has collapsed during the procurement phase for similar reasons: misaligned timelines, underestimated bureaucratic complexity, and insufficient legal review. After each failure, the founder attributed the loss to "district politics" and moved to the next prospect with the same approach. A mentor applies the weakness framework: the inbuilt weakness is the founder's limited perspective on institutional procurement (having no prior experience in education sales), and the acquired weakness is the pattern of externalising blame rather than updating the approach. The safeguard prescription: (a) an automatic rule that no partnership proposal is submitted without review by someone with district procurement experience, and (b) a pre-submission checklist covering the seven most common procurement failure points. The fourth partnership closes successfully -- not because the founder became smarter, but because the safeguard made the recurring blind spot irrelevant. + +**Growth-Stage SaaS CEO Whose Cover-Up Compounded a Pricing Mistake** + +A SaaS CEO at $6M ARR approved a new pricing tier that inadvertently grandfathered enterprise customers at rates 40% below the intended level. Rather than disclosing the error to the board and customers, the CEO attempted to quietly adjust pricing in the next renewal cycle, hoping no one would notice. Three months later, the enterprise sales team discovered the discrepancy, customer trust eroded, and the board learned of the error through a customer complaint rather than from the CEO. The initial mistake -- a pricing calculation error -- was a minor operational failure. The cover-up destroyed board confidence and required six months to repair. Applying the four-step protocol retroactively, the CEO acknowledges that the cover-up instinct was the ego default (protecting self-image as a competent pricing strategist) compounded by the emotion default (fear of board disapproval). The safeguard installed for the future: all pricing changes require a 72-hour review period with cross-functional sign-off, and any post-launch error is disclosed to the board within 48 hours regardless of severity. + +**Scale-Stage Marketplace Founder Using Perspective Shifts to Surface Organisational Blind Spots** + +A marketplace CEO at $25M ARR notices that customer satisfaction scores have plateaued despite increasing investment in customer success. Standard analysis reveals no obvious failure point. The CEO applies the perspective-shift safeguard, conducting "shadow sessions" -- spending full days observing customer support interactions from the agent's perspective, then from the customer's, then from the product team's. The shift reveals what internal metrics could not: the product team measures feature completion, customer success measures response time, and neither measures the customer's actual experience of resolving a problem end-to-end. The blind spot was structural, not individual -- each team was optimising within its own frame of reference while the customer's frame remained invisible. The CEO redesigns the metric architecture around the customer's perspective rather than internal team boundaries, and satisfaction scores begin climbing within a quarter. + +--- + +## Anti-Patterns + +**1. Over-engineering safeguards until they impede execution.** A founder who installs so many rules, checklists, and friction mechanisms that every decision requires a multi-step protocol has traded one failure mode (default-driven errors) for another (bureaucratic paralysis). Safeguards should target the specific, recurring failure patterns identified through honest weakness assessment -- not every conceivable decision. The framework's own examples are strikingly simple: one rule, one checklist, one environmental change. Simplicity is a feature, not a limitation. + +**2. Using safeguards as a substitute for strength-building.** Rules and checklists manage symptoms. The four pillars -- self-accountability, self-knowledge, self-control, self-confidence -- address root causes. A founder who implements a "no decisions when angry" rule but never develops the emotional self-regulation that would make the rule unnecessary is managing, not growing. Safeguards are scaffolding; they should support strength development, not replace it. + +**3. Performing accountability without practising it.** The four-step mistake protocol becomes theatre when the founder says the right words ("I take full responsibility") while the internal narrative remains defensive ("but it really was their fault"). The test is behavioural, not verbal: does the founder's subsequent conduct change, or does the same error recur? If the same mistake happens a third time, the acceptance was performative. + +**4. Treating all mistakes as equally grave.** The framework distinguishes between reversible and irreversible errors. A pricing experiment that underperforms can be reversed in a quarter. A founding-team equity split that demoralises a co-founder may be irreversible. The safeguard investment should be proportional to the irreversibility and magnitude of the potential error, not applied uniformly across all decisions. + +**5. Refusing external perspective as a weakness management tool.** The founder who says "I know my blind spots" is almost certainly wrong -- by definition, blind spots are the things you cannot see. The framework explicitly requires external input: other people can catalogue your weaknesses with clarity that self-reflection cannot match. Refusing to solicit, hear, or act on external feedback is the ego default disguised as self-sufficiency. + +--- + +## By Stage + +| Stage | Weakness Profile | Safeguard Priority | +|-------|-----------------|-------------------| +| Idea | Overconfidence in untested assumptions; limited market perspective; ego entanglement with the concept | Prevention (avoid irreversible commitments before validation) and perspective shifts (customer and sceptic viewpoints before building) | +| Validation | Confirmation bias in interpreting signals; emotional reactivity to negative feedback; fatigue from high-intensity experimentation | Automatic rules (define falsification criteria before running experiments) and HALT protocol before interpreting ambiguous customer data | +| Early Traction | First-playbook inertia; acquired habits from scrappy phase that become liabilities at scale; founder fatigue as a chronic condition | Friction (make it harder to keep doing things the old way) and checklists for decisions that are now recurring and high-frequency | +| Growth | Organisational blind spots replacing individual ones; cover-up culture if psychological safety is low; standards erosion as team grows faster than culture | Perspective shifts (cross-functional shadow sessions) and guardrails (decision protocols that distribute scrutiny across roles) | +| Scale | Institutional inertia; CEO blind spots amplified through deference culture; mistake-handling becomes a systemic rather than personal challenge | Institutional safeguard architecture: error-disclosure norms, pre-mortem requirements for major initiatives, mandatory perspective rotation in strategic planning | + +At the validation stage, the most critical safeguard is the pre-commitment to falsification criteria. The principle aligns with scientific method: define what evidence would cause you to abandon the hypothesis before you run the experiment. Without this safeguard, the ego default will reinterpret every ambiguous signal as confirmation. + +At scale, the CEO's personal safeguards must become organisational infrastructure. A CEO who handles their own mistakes well but has built no system for organisational mistake-handling has created a single point of failure. The four-step protocol -- accept, learn, commit, repair -- should be embedded in the company's post-mortem culture, not dependent on the CEO's personal discipline. + +--- + +## Output Template + +```markdown +# Weakness and Safeguard Assessment -- [Name / Context] + +**Date:** [Date] +**Decision domain:** [Area being assessed -- hiring, strategy, operations, etc.] + +## Weakness Inventory + +| Weakness | Type | Root Cause | Current Impact | Compounding Risk | +|----------|------|-----------|----------------|-----------------| +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | +| [Description] | [Inbuilt/Acquired] | [Why it exists] | [Current cost] | [12-month trajectory if unaddressed] | + +## Safeguard Design + +| Weakness | Strategy | Specific Safeguard | Implementation | +|----------|----------|-------------------|----------------| +| [Target weakness] | [Prevention/Rule/Friction/Guardrail/Perspective] | [Exact mechanism] | [How and when to deploy] | +| [Target weakness] | [Prevention/Rule/Friction/Guardrail/Perspective] | [Exact mechanism] | [How and when to deploy] | + +## Blind Spot Probe +- Perspective shift attempted: [Whose viewpoint was adopted] +- What was revealed: [Insight previously invisible] +- Action taken: [Change implemented] + +## Mistake Log (Recent) + +| Mistake | Step 1: Accepted? | Step 2: Root Cause | Step 3: Commitment | Step 4: Repair Status | +|---------|-------------------|-------------------|-------------------|----------------------| +| [Description] | [Y/N + evidence] | [What was learned] | [Specific plan] | [Complete/In progress/Not started] | + +## HALT Check (Current State) +- Hungry: [Y/N] +- Angry/Emotional: [Y/N] +- Lonely/Isolated/Unfamiliar environment: [Y/N] +- Tired/Sleep-deprived: [Y/N] +- **Decision readiness:** [Ready / Defer recommended] +``` + +--- + +## Related Skills + +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- The diagnostic foundation: understanding which defaults are active informs which weaknesses need safeguards and which mistakes are most likely to recur. +- **[Building Thinking Strength](../../content/skills/thinking/building-thinking-strength.md)** -- Strength and safeguards are complementary; strength addresses acquired weaknesses at the root while safeguards protect against inbuilt weaknesses that strength cannot eliminate. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's pre-mortem technique and reference-class forecasting are specific safeguard implementations within the broader architecture. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- The daily habits of reframing, perspective-gathering, and ethical pre-commitment are operationalised safeguards for time-pressured decisions. +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The Stoic practice of focusing only on what is within one's control is itself a perspective-shift safeguard. +- **[Stoic Pragmatism](../../content/skills/stoic/stoic-pragmatism.md)** -- The Stoic emphasis on practical action over theoretical understanding mirrors the insistence that knowing about weaknesses without building safeguards changes nothing. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- The mistake-handling protocols extend into the broader organisational practice of extracting learning from failure without blame. diff --git a/plugins/foreman/skills/maslow-hierarchy/SKILL.md b/plugins/foreman/skills/maslow-hierarchy/SKILL.md deleted file mode 120000 index 4137207..0000000 --- a/plugins/foreman/skills/maslow-hierarchy/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/maslow-hierarchy.md \ No newline at end of file diff --git a/plugins/foreman/skills/maslow-hierarchy/SKILL.md b/plugins/foreman/skills/maslow-hierarchy/SKILL.md new file mode 100644 index 0000000..a214866 --- /dev/null +++ b/plugins/foreman/skills/maslow-hierarchy/SKILL.md @@ -0,0 +1,212 @@ +--- +name: "maslow-hierarchy" +description: "Analyzes human motivation through Maslow's five-tier hierarchy of needs: physiological, safety, belonging, esteem, and self-actualization. Maps customer need levels for product positioning and employee motivation for retention strategy. Use when diagnosing employee disengagement despite good pay, repositioning product value propositions, auditing organizational maturity, or aligning incentives with the actual need level of the audience." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - motivation + - customer-psychology + - employee-engagement + - product-design + - human-needs + - organizational-culture +related_skills: + - smart-goals + - hackman-enabling-conditions + - situational-leadership + - four-ps-marketing +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Maslow's Hierarchy of Needs + +Turn the pyramid upside down. The most reproduced diagram in management education -- Abraham Maslow's five-level hierarchy, with physiological needs at the base and self-actualization at the apex -- has been drawn right-side-up so many times that people have stopped questioning it. Yet the most consequential insight for entrepreneurs sits at the top, not the bottom. Maslow's genius was not in observing that hungry people think about food. It was in arguing that once basic needs are met, human motivation does not plateau -- it transforms. The person whose survival is secure does not stop wanting; they start wanting differently. They want meaning, growth, purpose, and the realization of their potential. Companies that understand this build products people love and organizations people refuse to leave. Companies that do not understand this wonder why competitive salaries produce mediocre commitment and feature-rich products generate indifference. + +Maslow published "A Theory of Human Motivation" in 1943. Eight decades later, the hierarchy remains one of the most cited and most debated frameworks in psychology and management. Its critics are numerous and not always wrong. But the core architecture -- that human needs exist in layers, that lower layers must be substantially satisfied before higher layers become primary motivators -- continues to explain behavior that purely rational models cannot. + +--- + +## The Framework + +Maslow's hierarchy arranges human needs into five levels. The foundational claim is that needs at lower levels must be reasonably satisfied before needs at higher levels become dominant motivational forces. The framework is not a rigid staircase -- people can be motivated by multiple levels simultaneously -- but the general directional pull holds across cultures and contexts. + +### Level 1: Physiological Needs (Survival) + +**What it is:** The biological requirements for human survival -- food, water, shelter, sleep, warmth. + +**Business application -- Employees:** Salary sufficient to meet basic living costs. Physical workspace that is safe and functional. Work schedules that permit adequate rest. When these needs are unmet, nothing else matters. A company offering equity, purpose, and growth opportunities while paying below subsistence wages is building on sand. + +**Business application -- Customers:** Products that address fundamental needs command the most inelastic demand. Food delivery, housing platforms, healthcare services, basic financial tools. At this level, utility matters more than experience; reliability matters more than delight. + +**Startup lens:** Pre-revenue founders operating on personal savings are themselves at Level 1. Their decision-making is shaped by survival anxiety, which can produce both extraordinary focus and dangerous short-termism. + +### Level 2: Safety Needs (Security) + +**What it is:** Physical safety, financial security, health, protection from harm and instability. + +**Business application -- Employees:** Job security (or at least transparent communication about risks). Health benefits. Psychological safety -- the ability to speak up without fear of punishment. Clear policies and fair treatment. Startups that treat employment as perpetually precarious -- "we might run out of money any month" -- lock employees at Level 2, where their primary motivation is anxiety management rather than innovation. + +**Business application -- Customers:** Insurance, security systems, savings products, cybersecurity, data privacy. Products at this level sell peace of mind. The value proposition is the absence of a negative outcome rather than the presence of a positive one. + +**Startup lens:** Investors provide safety to founders by extending runway. The psychological shift that occurs when a startup raises funding is partly a Level 2 phenomenon: the founder's safety needs are temporarily satisfied, freeing cognitive resources for higher-level strategic thinking. + +### Level 3: Belonging Needs (Social Connection) + +**What it is:** Love, friendship, intimacy, community, sense of belonging to a group. + +**Business application -- Employees:** Team cohesion, company culture, social bonds with colleagues, feeling "part of something." Remote work challenges this level acutely -- belonging requires deliberate cultivation when it can no longer arise from physical proximity. Employee engagement surveys consistently show that "I have a best friend at work" correlates more strongly with retention than compensation. + +**Business application -- Customers:** Social networks, community platforms, brand communities, group fitness, co-working spaces. Products at this level succeed by creating or facilitating human connection. The product is often secondary to the community it enables -- CrossFit sells belonging that happens to involve exercise; Harley-Davidson sells identity that happens to involve motorcycles. + +**Startup lens:** Co-founder relationships operate at this level. The emotional bond between founders is both the startup's greatest asset and its greatest vulnerability. When belonging fractures -- and it often does under the pressure of startup life -- the company fractures with it. + +### Level 4: Esteem Needs (Recognition and Respect) + +**What it is:** Self-esteem, confidence, achievement, recognition by others, status, respect. + +**Business application -- Employees:** Public recognition of contributions. Meaningful titles (not inflated, but accurate). Autonomy that signals trust. Opportunities to develop mastery. The most corrosive force at this level is the perception that one's work does not matter or is not seen. Founders who absorb all credit while distributing all blame systematically destroy Level 4 satisfaction across their teams. + +**Business application -- Customers:** Luxury goods, premium services, professional certifications, status symbols, achievement platforms. Products at this level succeed by making the customer feel capable, respected, or admired. LinkedIn operates at Level 4 -- professional identity is a form of esteem management. + +**Startup lens:** Founder ego is a Level 4 phenomenon. The drive for recognition fuels entrepreneurship -- and can also distort decision-making when the founder's esteem needs conflict with the company's strategic needs. Founders who need to be the smartest person in the room hire people less smart than themselves. + +### Level 5: Self-Actualization (Becoming) + +**What it is:** The realization of personal potential, self-fulfillment, peak experiences, creativity, purpose. + +**Business application -- Employees:** Work that is intrinsically meaningful. Opportunities for creative expression. Alignment between personal values and organizational mission. Autonomy to pursue mastery. Self-actualization at work is rare and cannot be manufactured -- but the conditions that enable it can be designed. Hackman's enabling conditions and Pink's autonomy-mastery-purpose framework describe these conditions from different angles. + +**Business application -- Customers:** Education platforms, creative tools, coaching services, travel experiences, philanthropic products. Products at this level help people become who they want to be. Maslow's insight is that this motivation is not a luxury -- it is the natural culmination of satisfied lower needs, and its pull is immense. + +**Startup lens:** The most compelling startup missions appeal to self-actualization -- not just the founder's, but the customer's and the team's. "Organize the world's information" (Google), "Accelerate the world's transition to sustainable energy" (Tesla), and "Give people the power to build community" (Facebook) are all Level 5 appeals, regardless of how imperfectly those companies deliver on them. + +### The Hierarchy as Diagnostic Tool + +The framework's entrepreneurial value lies in three applications: + +1. **Customer segmentation by need level.** Which level of the hierarchy does your product address? Products that serve lower levels compete on reliability and price. Products that serve higher levels compete on meaning and experience. + +2. **Employee motivation diagnosis.** Where are your team members on the hierarchy? Offering equity (Level 4-5 reward) to someone worried about making rent (Level 1) misses the mark. Offering a raise (Level 1-2 reward) to someone craving meaningful work (Level 5) also misses. + +3. **Organizational maturity mapping.** Startups begin at Level 1 (survival). As they stabilize, they can progressively satisfy higher-level needs for both employees and customers. The transition from survival mode to purpose mode is one of the most important -- and most difficult -- evolutions a growing company undergoes. + +--- + +## Prompts + +**Prompt 1 -- Customer Need-Level Analysis:** +> Analyze my product [describe] through Maslow's hierarchy. Which level of need does it primarily address? Which levels does it also touch? Based on this analysis, what is the most effective value proposition -- and what messaging mistakes am I likely making by appealing to the wrong level of need for my target customer? + +**Prompt 2 -- Employee Motivation Audit:** +> My team of [number] people is showing these engagement patterns: [describe -- e.g., "people do the minimum," "high turnover despite good pay," "low energy in meetings but strong 1:1 conversations"]. Using Maslow's hierarchy, diagnose which need level is unsatisfied for my team. What specific interventions at that level would improve motivation and engagement? + +**Prompt 3 -- Organizational Hierarchy Mapping:** +> Map my startup's current position on Maslow's hierarchy as an organization. We are at [stage], with [months of runway], [team size], and [describe culture/morale]. Which organizational needs are met, which are at risk, and which are unaddressed? How should our priorities shift as we move to the next stage? + +**Prompt 4 -- Product-Market Fit Through Maslow:** +> I'm struggling with product-market fit for [product]. Help me reframe my value proposition using Maslow's hierarchy. What level of need does my target customer [describe segment] most urgently need addressed? Is my product positioned at the right level? Should I reposition to address a different level of the hierarchy? + +--- + +## Use Cases + +**SaaS Startup Misreading Employee Motivation** + +A growth-stage SaaS company with strong revenue and 18 months of runway keeps losing mid-level engineers to competitors. Exit interviews cite "lack of growth opportunities" and "feeling like a cog in the machine." The company's response has been to increase salaries -- a Level 1-2 intervention for a Level 4-5 problem. Engineers whose physiological and safety needs are already well met are not motivated by incremental compensation. They want meaningful work (Level 5), recognition for their contributions (Level 4), and a sense of belonging to something that matters (Level 3). The Maslow diagnosis redirects the retention strategy: implement a technical leadership track (Level 4), create cross-functional project teams for strategic initiatives (Level 3 and 5), and establish a public recognition program tied to impact rather than output (Level 4). Retention improves within two quarters -- at lower cost than the salary increases would have required. + +**Consumer App Repositioning from Level 2 to Level 3** + +A validation-stage personal finance app initially positions itself around financial security: "Never worry about money again" (Level 2). User research reveals that the most engaged users do not use the app for security -- they use it because tracking spending with a partner creates a sense of shared financial purpose (Level 3: Belonging). The Level 2 positioning attracts anxious users who churn when their anxiety subsides. The Level 3 positioning attracts couples building a financial life together -- a far stickier use case. Repositioning the product around shared financial goals rather than individual financial anxiety doubles retention. + +**Founder in Survival Mode Making Survival Decisions** + +An idea-stage founder with three months of personal savings remaining finds herself unable to think strategically about product direction. Every decision is filtered through "what will generate revenue fastest" rather than "what will create the most value." A Maslow lens clarifies the problem: the founder's own physiological and safety needs are dominating her cognitive landscape. The intervention is not motivational -- it is structural. Extending runway through a small friends-and-family round, taking a part-time consulting contract, or securing a small grant shifts the founder from Level 1-2 to Level 3-4, where strategic thinking becomes possible. The decision to extend runway is itself a strategic decision, not a sign of weakness. + +--- + +## Anti-Patterns + +- **Rigid Sequential Application.** Treating the hierarchy as a strict ladder where lower levels must be 100% satisfied before higher levels matter at all. Maslow himself acknowledged that the hierarchy is probabilistic, not absolute. A person can be motivated by purpose while still worrying about finances. The hierarchy describes dominant motivational forces, not exclusive ones. + +- **Using Maslow to Justify Low Pay.** The perverse argument that if employees are motivated by purpose (Level 5), they should accept below-market compensation (Level 1). Purpose does not replace salary; it augments it. Underpaying people while offering "mission" creates resentment that corrodes every higher-level need. + +- **Projecting the Founder's Need Level onto the Team.** Founders operating at Level 5 (self-actualization through building something meaningful) often assume the team shares this motivation. Many team members may be at Level 2 (job security in a volatile startup) or Level 3 (belonging to a team). Mismatched assumptions about motivation produce mismatched management strategies. + +- **Ignoring Cultural Variation.** Maslow's hierarchy was developed from a Western, individualistic psychological tradition. Research suggests that collectivist cultures may weight belonging (Level 3) and esteem (Level 4) differently than individualist ones. Applying the hierarchy rigidly across diverse teams without cultural calibration produces blind spots. + +- **Treating the Framework as Comprehensive.** Maslow describes motivational needs, not all aspects of human psychology relevant to business. The hierarchy says nothing about cognitive style, risk tolerance, learning preferences, or behavioral tendencies. Pairing Maslow with complementary frameworks (Belbin for team roles, Situational Leadership for management approach) produces a more complete picture. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's own hierarchy position | The founder's personal need level shapes every decision; addressing founder survival needs (runway, income) is a prerequisite for strategic thinking | +| Validation | Customer need-level discovery | Understanding which level of need the product addresses determines positioning, pricing, and retention dynamics | +| Early Traction | Team motivation foundations | First hires need Level 1-2 stability (reasonable pay, job security signals) before they can engage with the mission at higher levels | +| Growth | Organizational culture as need-satisfier | The company must systematically satisfy Level 3-4 needs (belonging, recognition) to retain talent as the labor market exerts pull | +| Scale | Self-actualization as competitive advantage | Companies that enable Level 5 experiences for employees and customers build loyalty that competitors cannot replicate with lower-level rewards | + +--- + +## Output Template + +```markdown +# Maslow's Hierarchy Analysis: [Company/Product/Team Name] + +**Date:** [Date] +**Analysis Type:** [Customer Needs / Employee Motivation / Organizational Assessment] + +## Need-Level Map + +### For Customers +| Maslow Level | How Our Product Addresses It | Strength | Gap | +|-------------|------------------------------|----------|-----| +| Physiological | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Safety | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Belonging | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Esteem | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | +| Self-Actualization | [How, or N/A] | [Strong/Weak/Absent] | [Gap description] | + +**Primary need level served:** [Level] +**Value proposition alignment:** [Aligned / Misaligned -- with explanation] + +### For Employees +| Maslow Level | Current Satisfaction | Evidence | Intervention Needed | +|-------------|---------------------|----------|---------------------| +| Physiological | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Safety | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Belonging | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Esteem | [Met/At Risk/Unmet] | [Data points] | [Action or None] | +| Self-Actualization | [Met/At Risk/Unmet] | [Data points] | [Action or None] | + +**Primary unsatisfied level:** [Level] +**Recommended priority intervention:** [Specific action] + +## Strategic Implications +1. [Insight about product positioning based on customer need level] +2. [Insight about retention strategy based on employee need level] +3. [Insight about organizational maturity based on collective need level] +``` + +--- + +## Related Skills + +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman's conditions map to Maslow levels: clear direction addresses safety and esteem, right people enables belonging, supportive context satisfies physiological and safety needs. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Safety and belonging needs must be met before employees can contribute fully; Edmondson's framework operationalizes the conditions Maslow's Levels 2 and 3 describe. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- Retention strategies succeed when they target the correct Maslow level; offering equity to someone worried about rent or purpose to someone craving recognition misses the mark. +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- Product positioning and pricing strategy should align with the Maslow level the product addresses; Level 5 products demand different marketing mixes than Level 1 products. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness and empathy help leaders diagnose which need level is unsatisfied in their team members, enabling more targeted motivational interventions. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- Purpose appeals to Maslow's Level 5 self-actualization; leaders who connect work to meaning unlock motivation that compensation alone cannot provide. diff --git a/plugins/foreman/skills/meeting-the-right-people/SKILL.md b/plugins/foreman/skills/meeting-the-right-people/SKILL.md deleted file mode 120000 index f2421b9..0000000 --- a/plugins/foreman/skills/meeting-the-right-people/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/meeting-the-right-people.md \ No newline at end of file diff --git a/plugins/foreman/skills/meeting-the-right-people/SKILL.md b/plugins/foreman/skills/meeting-the-right-people/SKILL.md new file mode 100644 index 0000000..df8487d --- /dev/null +++ b/plugins/foreman/skills/meeting-the-right-people/SKILL.md @@ -0,0 +1,208 @@ +--- +name: "meeting-the-right-people" +description: "Applies modern networking and relationship-curation methods for entrepreneurs who need to build strategic networks efficiently. Covers standing out through signature differentiation, the warm-introduction chain for reaching anyone, building a personal advisory board, the discipline of hiring slow and firing fast in all relationships, and the art of the productive blowoff. Use when preparing for conferences and networking events, seeking introductions to investors or partners, assembling advisory boards, evaluating whether to continue or exit relationships, or protecting time from low-value interactions." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - networking + - advisory-board + - introductions + - time-management + - personal-brand + - relationship-curation +related_skills: + - understanding-people + - reading-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Meeting the Right People + +The secret to networking is not talking to everyone -- it is doing what nobody else does. + +A founder wore bright orange sneakers to a startup event where three hundred people competed for the attention of Dave McClure, founding partner of 500 Startups. McClure ignored all of them. Then he spotted the shoes. "I have got to talk to the man wearing those fucking shoes!" The conversation lasted fifteen minutes. 500 Startups became a key investor in the founder's company. The shoes did not close the deal. But they opened the door -- and in a room of identical pitches, the door is the bottleneck. + +This principle generalises beyond footwear. In any saturated environment -- a conference, an inbox, a LinkedIn feed -- the decisive advantage belongs to the person who has solved the attention problem before solving the persuasion problem. Most networking advice focuses on what to say. The prior question is how to get anyone to listen in the first place. + +--- + +## The Framework + +Meeting the right people involves five distinct disciplines, each addressing a different failure mode. + +### Discipline 1: Stand Out (The Orange Shoes Principle) + +In any gathering of professionals, the default is conformity. Dark suits, safe accessories, predictable conversation openers. The person who introduces a single, authentic differentiator -- visual, behavioural, or conversational -- captures disproportionate attention. + +The criteria for an effective differentiator: + +- **Attention-grabbing.** It must be visible or noticeable without requiring explanation. +- **Authentic.** It must feel natural to you, not costumed. A forced quirk is worse than no quirk. +- **Consistent.** It must appear repeatedly so that it becomes associated with your identity. A one-time stunt is novelty; a persistent signature is brand. + +Orange shoes work because they satisfy all three criteria. The differentiator need not be visual -- it could be an unusual opening question (see the three-question method), a distinctive handshake ritual, or a habit of sending handwritten follow-up notes in an era of templated emails. What matters is that it is yours, it is noticeable, and it recurs. + +### Discipline 2: Reach Anyone (The Warm Introduction Chain) + +Cold outreach has a response rate that approaches zero for high-value targets. The warm introduction chain -- mediated through mutual connections, typically via LinkedIn -- transforms unreachable contacts into coffee meetings. + +**The method:** + +1. Identify the person you want to meet. +2. Search for mutual connections -- first-degree preferred, second-degree acceptable. +3. Select the mutual connection most likely to respond positively. Two filters: (a) someone for whom you have done a favour in the past (reciprocity capital), and (b) someone with genuine influence over the target. +4. Write a concise introduction request that explains *why* the meeting would be mutually beneficial, not just why *you* want it. +5. Once connected, propose a specific, time-bounded meeting. "Fifteen minutes for coffee" removes friction. "Let's find time to chat sometime" creates it. + +The chain works because it transfers trust. The target does not know you, but she knows and trusts the connector. That transferred trust lowers the barrier from "ignore" to "consider." The deeper your network of first-degree connections, the shorter the chain to any target. This is the compound interest of relationship-building -- every genuine connection increases the reachability of everyone else. + +### Discipline 3: Build a Personal Advisory Board + +Mentorship is not reserved for people who work inside organisations large enough to have formal programmes. Any entrepreneur can construct a personal advisory board -- an informal group of five to twelve people who meet quarterly to advise on specific challenges. + +**Construction principles:** + +| Element | Guidance | +|---------|----------| +| Purpose | Define the board's focus before recruiting members. "Help me launch a software company" is actionable. "Help me with stuff" is not. | +| Composition | Diverse disciplines and backgrounds. At least half should be people you have met; at least two should be people you have not yet met but can reach through connections. | +| Structure | Scheduled quarterly meetings with a written agenda. Begin with a twenty-minute icebreaker or training exercise. Follow with a business update and one to two specific challenges for discussion. | +| Reciprocity | Provide value to advisers at every meeting -- leadership training, networking opportunities, a small equity stake or stipend. The most powerful compensation, however, is the multiplier effect: smart people in the same room generate connections and insights none of them would have produced alone. | +| Seriousness | The difference between an advisory board and a casual dinner is structure. Agenda, schedule, quiet room, follow-through. The more seriously the founder takes the format, the more seriously advisers will take their role. | + +The multiplier effect is the advisory board's core advantage over one-on-one mentorship. When eight experienced people hear the same challenge simultaneously, they produce cross-pollinated solutions -- combinations of expertise that no single adviser would generate alone. + +### Discipline 4: Hire Slow, Fire Fast (In All Relationships) + +The principle is well-known in management. Its application to *all* professional relationships is less obvious but equally important. + +**Hire slow:** Do not grant full trust and access to someone you have just met, no matter how impressive they appear. Early enthusiasm is not evidence of long-term fit. Cofounders, business partners, key hires, and even investor relationships should be entered gradually, with deliberate evaluation at each stage. + +**Fire fast:** The moment gut instinct signals that a relationship is not working -- the business partner whose values diverge, the investor whose advice consistently harms, the hire whose culture impact is toxic -- act. Cognitive dissonance is the enemy: the desire to believe you made a good decision causes you to rationalise the bad one, sometimes for years. + +The cognitive dissonance trap is particularly dangerous for founders, who are temperamentally biased toward optimism. The script "I'll give them one more chance" or "Maybe they'll change" is almost always the sound of a founder overriding data with hope. Every minute spent with the wrong person is a minute unavailable for the right one. + +### Discipline 5: The Productive Blowoff + +Time is finite. Not every person who requests a meeting deserves thirty minutes of it. The productive blowoff -- ending an interaction quickly while leaving the other person feeling valued -- is a skill that protects the founder's most scarce resource. + +**The three-step blowoff:** + +1. **Physical signal.** A handshake or equivalent gesture to mark the beginning *and* the end of the conversation. +2. **Direct, honest communication.** State the situation frankly. "You don't fit our investment criteria, but you might be a partner" conveys respect through candour. +3. **Provide value before exiting.** Make an introduction, offer a specific suggestion, send a useful resource. The person walks away with something concrete rather than a vague rejection. + +The founder who masters this discipline converts thirty-minute meetings into eight-minute meetings without creating resentment -- and reclaims the other twenty-two minutes for higher-value activity. Sheryl Sandberg calls it "ruthless prioritisation." The ruthlessness applies to time allocation, not to people. + +--- + +## Prompts + +**Prompt 1 -- Networking Differentiation Strategy:** +> I am attending [describe event: type, audience, size, goal]. Help me design a personal differentiation strategy using the Orange Shoes principle. Based on my personality and context [describe], suggest three possible signature differentiators that are attention-grabbing, authentic to me, and repeatable. For each, describe how it would work at this specific event and what opening conversations it would naturally create. + +**Prompt 2 -- Warm Introduction Chain:** +> I want to meet [describe target person, their role, and why]. I have the following potential mutual connections: [list 3-5 people]. For each, evaluate (a) the likely strength of their relationship with my target, (b) the reciprocity capital I have with them, and (c) the quality of introduction they would provide. Recommend the optimal connector and draft the introduction request email. + +**Prompt 3 -- Advisory Board Design:** +> I am a [stage] founder building [describe company]. Design a personal advisory board for me. Recommend the ideal size, meeting frequency, agenda structure, and compensation model. Define the five to seven competency areas I should recruit for, and for each, suggest the profile of the ideal adviser (not a specific person, but a role/background description). Include a template for the initial recruitment ask. + +**Prompt 4 -- Relationship Audit:** +> Audit my current professional relationships against the "hire slow, fire fast" principle. Here are my key relationships: [list 5-8 with brief descriptions of current state]. For each, identify whether I am (a) investing appropriately, (b) over-investing due to cognitive dissonance, or (c) under-investing in a high-potential connection. Recommend specific actions for each, including any "fire fast" decisions I may be avoiding. + +--- + +## Use Cases + +**Idea-Stage Founder at a Demo Day** + +A first-time founder attends a demo day with forty startups and two hundred investors. She has no existing investor relationships and no brand recognition. Applying the Orange Shoes principle, she wears a distinctive hand-painted jacket that references her product's design aesthetic -- genuine because she is a trained artist, attention-grabbing because no one else in the room has one. Three investors approach her before she approaches anyone. She uses the warm-introduction chain for the remaining five target investors, reaching three through LinkedIn mutual connections within the following week. Within a month, she has a personal advisory board of four people assembled from connections made at the event: a veteran founder, a domain expert, a marketing executive, and one of the investors who did not invest but offered to advise. The board meets quarterly in a structured format, and within two meetings surfaces a pivot in go-to-market strategy that the founder would not have identified alone. + +**Growth-Stage CEO Protecting Executive Time** + +A CEO of a sixty-person company receives fifteen meeting requests per week from vendors, potential partners, and aspiring hires. Her calendar is the company's bottleneck. She implements the productive blowoff systematically: every meeting request receives a response within forty-eight hours, but most are converted from thirty-minute meetings to ten-minute calls with a clear three-step structure (signal, directness, value). She creates a "meeting triage" protocol for her executive assistant: requests that align with quarterly priorities get full meetings; all others get the abbreviated format. The CEO recovers seven hours per week -- nearly a full working day -- while maintaining a reputation for responsiveness and generosity. + +--- + +## Anti-Patterns + +1. **Collecting Connections Without Purpose.** Treating LinkedIn connections or business cards as a score. Ten thousand connections with no relationship depth is a database, not a network. The warm-introduction chain requires trust, and trust requires genuine relationships -- not a follower count. + +2. **Networking as Performance.** Attending every event, working every room, exchanging cards with every person. This produces exhaustion and shallow relationships. Strategic networking means attending fewer events with higher target density and investing more time per interaction. + +3. **Advisory Board as Vanity Project.** Recruiting impressive names who never attend meetings or provide substantive input. An advisory board with a former Fortune 500 CEO who shows up once a year is less valuable than one with five engaged operators who attend every quarter and follow up between meetings. + +4. **Firing Too Slowly Out of Guilt.** The cognitive dissonance trap is especially potent in founder-investor and founder-cofounder relationships, where the social cost of exit feels prohibitive. The sunk-cost fallacy -- "we've been through so much together" -- is not a strategy. Every week spent in a toxic partnership has a measurable opportunity cost. + +5. **Blowing Off the Wrong People.** The productive blowoff is a tool for time management, not for status signalling. The junior employee who requests a meeting today may be the CEO who writes a check tomorrow. Evaluate meeting requests on potential value, not current title. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Network construction | At the idea stage, the founder's network *is* the venture's most valuable asset. Every coffee meeting, warm introduction, and event attendance is an investment in infrastructure that will compound over years. | +| Validation | Customer and partner access | The warm-introduction chain becomes a customer-discovery tool. Reaching ten potential customers through trusted mutual connections yields richer feedback than reaching a hundred through cold outreach. | +| Early Traction | Advisory board formation | With a product in market and early signals of fit, the founder has enough substance to recruit meaningful advisers. This is the optimal window for advisory-board construction -- early enough to benefit from strategic guidance, late enough to articulate a clear purpose. | +| Growth | Relationship pruning | Growth demands "fire fast" discipline. Relationships that served the company at seed stage -- the friendly-but-unstrategic investor, the early hire who cannot grow with the role -- must be evaluated honestly against current needs. | +| Scale | Institutional networking | At scale, the founder's personal network cannot serve the entire organisation. Networking must become a distributed competency -- every executive building their own warm-introduction chains, their own advisory relationships, their own productive-blowoff discipline. | + +--- + +## Output Template + +```markdown +# Networking Strategy: [Your Name / Company / Event] + +## Differentiation +- **Signature element:** [Description] +- **Why it is authentic:** [Connection to personality/brand] +- **Expected conversations it will generate:** [Types of openers] + +## Target Contacts +| Target | Why | Best Connector | Introduction Request Status | +|--------|-----|----------------|---------------------------| +| [Name] | [Reason] | [Mutual connection] | [Drafted / Sent / Connected] | + +## Advisory Board Design +- **Purpose:** [Specific goals] +- **Target size:** [Number] +- **Competency areas needed:** [List] +- **Meeting cadence:** [Frequency and format] +- **Recruited / Open seats:** [Status] + +## Relationship Audit +| Relationship | Current Investment | Correct Action | Timeline | +|-------------|-------------------|----------------|----------| +| [Name/Role] | Over / Under / Right | [Specific action] | [When] | + +## Time Protection +- **Meeting triage criteria:** [What qualifies for full meeting vs. abbreviated format] +- **Hours recovered per week target:** [Number] +``` + +--- + +## Related Skills + +- **[Understanding People](../../content/skills/people/understanding-people.md)** -- Meeting people is the access problem; understanding them is the comprehension problem; the Enneagram and rapid-understanding techniques make meetings productive once they occur. +- **[Reading People](../../content/skills/people/reading-people.md)** -- The warm-introduction chain gets you into the room; reading nonverbal signals tells you what the room is actually thinking. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Meeting the right people is necessary but insufficient; connecting through validation and the Platinum Rule transforms initial meetings into lasting relationships. +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principle of making others feel important is the interpersonal foundation that makes warm introductions work. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- The warm-introduction chain is Cialdini's Reciprocity principle in action; the advisory board leverages Authority and Unity. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- A compelling personal story is the most effective tool for first meetings; it creates memorability and connection faster than any networking script. diff --git a/plugins/foreman/skills/mentoring-and-coaching/SKILL.md b/plugins/foreman/skills/mentoring-and-coaching/SKILL.md deleted file mode 120000 index 0d55d26..0000000 --- a/plugins/foreman/skills/mentoring-and-coaching/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/mentoring-and-coaching.md \ No newline at end of file diff --git a/plugins/foreman/skills/mentoring-and-coaching/SKILL.md b/plugins/foreman/skills/mentoring-and-coaching/SKILL.md new file mode 100644 index 0000000..3c9f35f --- /dev/null +++ b/plugins/foreman/skills/mentoring-and-coaching/SKILL.md @@ -0,0 +1,186 @@ +--- +name: "mentoring-and-coaching" +description: "Provides a practical system for being an effective mentor and coach -- selecting mentees, building mentorship teams, setting ground rules, heading off rifts, avoiding power misuse, preparing successors, and finding daily coaching micro-moments. Use when a leader takes on a new mentee, notices a protege stalling, needs to structure informal development conversations, wants to shift from directing to coaching, or seeks to scale mentoring across an organisation without formal programmes." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - mentoring + - coaching + - talent-development + - succession + - feedback + - protege + - daily-practice +related_skills: + - grow-model + - psychological-safety + - emotional-intelligence + - leadership-pipeline +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Mentoring and Coaching + +MULTIPLIER. One mentor can alter the trajectory of an entire organisation -- not by running it, but by developing the people who do. The arithmetic is compounding: a leader who mentors three people, each of whom mentors three others, has shaped twelve leaders within a single generation. Yet most mentoring relationships are accidental, unstructured, and ultimately disappointing. The mentor offers vague wisdom. The mentee nods politely. Both parties gradually stop scheduling meetings. The failure is not one of intention but of craft. Vineet Chopra and Sanjay Saint's six-part framework for great mentoring -- choose carefully, establish a team, run a tight ship, head off rifts, don't hold back, prepare successors -- treats mentoring as a discipline with standards, not a favour dispensed on goodwill. + +The distinction between mentoring and coaching matters. Mentoring is a long-arc relationship focused on career trajectory, institutional navigation, and wisdom transfer. Coaching is a conversational practice -- often brief, often daily -- focused on helping someone solve their own problems. A leader needs both capabilities. The first builds the next generation. The second builds the next day. + +--- + +## The Framework + +### The Six Disciplines of Great Mentoring + +**Discipline 1: Choose Mentees Carefully** + +Mentoring is an investment, not a charity. A good mentee demonstrates curiosity, organisation, responsibility, and engagement. The diagnostic is simple: assign a small task -- read a book and discuss it within a month, attend a strategy session and write up observations. What returns tells you everything about their thinking process, communication discipline, and genuine interest. Mentees who expect the mentor to sustain the relationship, or who insist on doing things exclusively their own way, are signalling that the investment will not compound. + +**Discipline 2: Build a Mentorship Team** + +No single mentor possesses everything a protege needs. The effective mentor identifies what areas the mentee wants to develop, maps those areas to people in their network with relevant expertise, and recruits them as auxiliary advisors. The mentor remains the primary source of career, moral, and institutional support, but the team approach ensures the mentee has breadth of access. Peers who contribute to someone's growth with a lower level of commitment often find the arrangement energising rather than burdensome. + +**Discipline 3: Run a Tight Ship** + +Ground rules established at the outset prevent the slow erosion that kills most mentoring relationships. Three conversations are required early: + +- What does the mentee want from the relationship? +- What is the mentor willing to provide -- and what falls outside scope? +- What cadence, communication norms, and escalation procedures will govern the relationship? + +Accountability is non-negotiable. The mentor must make clear that second-rate work reflects on both parties. Standards are not punitive; they are protective. + +**Discipline 4: Head Off Rifts** + +Disagreements are inevitable. The mentor's responsibility is to address them immediately -- not to let friction accumulate until the relationship quietly dissolves. The repair protocol: initiate the conversation (do not wait for the mentee to raise it), ask for their perspective, resist rushing to judgment, and identify the root cause. Open, frank relationships are the mechanism through which mentoring creates value. Without candour, the relationship is decorative. + +**Discipline 5: Don't Hold Back** + +Power dynamics in mentoring can corrupt. The mentor must guard against five specific misuses: + +| Behaviour | Why It Happens | Why It Destroys | +|-----------|---------------|-----------------| +| Taking credit for the mentee's ideas | The mentor's ego conflates guidance with authorship | Erodes the mentee's confidence and public recognition | +| Insisting the mentee advance the mentor's projects | The mentor confuses mentoring with delegation | Converts a developmental relationship into an extractive one | +| Tethering the mentee to the mentor's timeline | Comfort with the status quo overrides the mentee's growth | Slows the protege's career progression unnecessarily | +| Discouraging other mentors | The mentor's ego requires exclusivity | Isolates the mentee from broader learning and recognition | +| Allowing self-destructive mistakes to continue unremarked | Conflict avoidance masquerading as respect for autonomy | Permits damage that honest feedback would have prevented | + +**Discipline 6: Prepare Successors** + +The mentor's primary job is to transfer wisdom. The secondary job -- equally important -- is to identify mentees who can become mentors themselves. Candidates need true expertise and a generous disposition. The preparation involves transparency about the mentor's own decision-making process: how problems are analysed, solutions weighed, and support calibrated. Co-mentoring a new mentee is an effective bridge until the successor is ready to operate independently. The ultimate measure of a mentor's success is not the protege's achievements but the protege's capacity to develop others. + +### Daily Coaching Micro-Moments + +Formal mentoring programmes are insufficient. Real development happens in the five-minute check-in, the post-meeting debrief, the hallway observation. Three daily practices fill the gap: + +1. **Check-in questions.** "How are things going?" is a start, but "What are your career goals, and how can I help?" signals genuine investment. Ask regularly, not ritualistically. +2. **In-the-moment feedback.** When you observe an employee in action -- a presentation, a negotiation, a difficult conversation -- offer specific feedback: what they did well, what could improve, and why. Timeliness matters; feedback delivered a week later loses 80% of its developmental impact. +3. **Coaching stance over directing stance.** The instinct to tell people what to do is deeply embedded, particularly in leaders who built their reputation on decisive action. Coaching requires the opposite: listen first, ask questions, withhold judgment, and draw wisdom from the person being coached. The goal is helping them learn to solve problems independently, not solving problems for them. + +Herminia Ibarra and Anne Scoular's research is direct: leaders who rate themselves as good coaches consistently overestimate their skill. The diagnostic is whether the other person leaves the conversation with their own insight or with the leader's instruction. If it is the latter, it was not coaching. + +--- + +## Prompts + +**Prompt 1 -- Mentee Selection Assessment:** +> I am considering mentoring [describe the person -- role, experience, what drew your attention]. Help me design a selection test: a small, revealing task that will surface their curiosity, organisation, communication quality, and genuine interest. The task should take no more than two weeks and produce an artefact I can evaluate. Also suggest three questions I should ask myself after reviewing their work. + +**Prompt 2 -- Mentorship Team Design:** +> My mentee wants to develop in these areas: [list areas]. My own expertise covers: [list areas]. Identify the gaps where I cannot provide adequate guidance. Then describe the profile of the auxiliary mentors I should recruit -- what expertise they need, what commitment level is realistic, and how I should approach them. + +**Prompt 3 -- Mentoring Relationship Audit:** +> I have been mentoring [person] for [duration]. Here is the current state of the relationship: [describe -- frequency of contact, recent interactions, any tensions, progress observed]. Audit the relationship against the six disciplines: selection quality, team support, ground rules, rift management, power dynamics, and succession preparation. Identify which disciplines are strong and which need intervention. Provide specific actions for the weakest two. + +**Prompt 4 -- Daily Coaching Shift:** +> I tend to direct rather than coach. Here is a recent interaction where I told someone what to do instead of helping them figure it out: [describe the situation and what you said]. Rewrite my side of the conversation using a coaching approach -- questions instead of answers, drawing out their thinking instead of imposing mine. Then give me three questions I can use in similar situations going forward. + +--- + +## Use Cases + +**Early-Traction Startup: Founder Mentoring First Managers** +A founder with 25 employees has promoted three individual contributors to management. None has managed before. Rather than sending them to a generic management course, the founder applies the six disciplines: selects carefully (these three demonstrated curiosity and responsibility as ICs), builds a mentorship team (recruits a seasoned COO from their investor's portfolio company as an auxiliary advisor), establishes ground rules (bi-weekly 30-minute check-ins, specific preparation expected from each mentee), and commits to in-the-moment coaching after every difficult management conversation. Within six months, all three managers are conducting their own coaching conversations with direct reports -- the compounding has begun. + +**Growth-Stage Company: VP Recovering from a Mentoring Failure** +A VP of Product mentored a promising director for two years. The relationship ended badly: the director felt micromanaged, the VP felt the director was ungrateful. A post-mortem against the six disciplines reveals failures in discipline three (no ground rules established), discipline four (a disagreement about project ownership festered for three months), and discipline five (the VP had been insisting the director advance VP-level projects rather than developing their own work). The VP restructures their approach for a new mentoring relationship, beginning with explicit ground rules, a shared document tracking goals and concerns, and a quarterly check on power dynamics. + +**Scale-Stage Organisation: Building a Mentoring Culture Without a Programme** +A 400-person company's HR team wants to launch a formal mentoring programme. The CEO, having seen formal programmes devolve into bureaucratic matching exercises, instead trains all directors in daily coaching micro-moments: check-in questions, in-the-moment feedback, and the coaching-over-directing stance. Each director is asked to identify one person whose development they will actively invest in -- not through programme paperwork, but through the six disciplines. The result: 30 active mentoring relationships, each with ground rules and accountability, none requiring programme administration. + +--- + +## Anti-Patterns + +1. **Mentoring as Autobiography.** The mentor who treats every conversation as an opportunity to narrate their own career. The mentee's context is not a prompt for the mentor's reminiscence. Great mentoring is about the mentee's trajectory, informed by -- not replaced by -- the mentor's experience. + +2. **The GROW Model as the Entire Coaching Repertoire.** GROW is a powerful conversational structure (covered in detail in the frameworks category). But leaders who apply it rigidly to every interaction -- including five-minute hallway conversations -- turn coaching into a formulaic exercise. Daily coaching micro-moments require fluency, not frameworks. Know when structure helps and when it hinders. + +3. **Confusing Sponsorship with Mentoring.** Sponsorship is about using your influence to create opportunities for someone. Mentoring is about developing their capacity to create opportunities for themselves. Both are valuable. Conflating them produces a protege who advances positionally without developing the capability to sustain that advancement. + +4. **Avoiding Difficult Feedback to Preserve the Relationship.** Allowing a mentee to repeat self-destructive patterns because correcting them feels uncomfortable. This is not kindness; it is negligence. The mentor who does not hold back -- discipline five -- serves the mentee's long-term interest at the cost of short-term discomfort. + +5. **Scaling Mentoring Through Technology.** Believing that a mentoring platform, matching algorithm, or scheduling tool can substitute for the relational investment that makes mentoring work. Technology can support logistics. It cannot manufacture the trust, candour, and accountability that define a productive mentoring relationship. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder as primary mentor | The founder mentors the first wave of managers directly. The mentorship team is small or external (advisors, investors). The six disciplines apply in compressed form -- ground rules and accountability are particularly critical because everyone is learning simultaneously. | +| Growth | Mentoring the mentors | The leader's task shifts from direct mentoring to developing others' mentoring capability (discipline six). The mentorship team expands. Daily coaching micro-moments become the primary development mechanism because formal mentoring cannot scale to every employee. | +| Scale | Cultural embedding | Mentoring becomes an organisational expectation, not a personal choice. The leader's role is to model mentoring behaviour, resource it (time, not software), and hold leaders accountable for developing their people. The ultimate diagnostic: does development happen when the CEO is not watching? | + +--- + +## Output Template + +```markdown +# Mentoring Relationship Plan: [Mentor] -> [Mentee] + +## Selection Rationale +- Why this person: [specific evidence of curiosity, organisation, engagement] +- Selection test result: [what was assigned, what was returned, what it revealed] + +## Mentorship Team +| Area | Primary Mentor | Auxiliary Advisor | Contact Cadence | +|------|---------------|-------------------|-----------------| +| [development area] | [name/self] | [name] | [frequency] | + +## Ground Rules +- Meeting cadence: [frequency, duration, format] +- Communication norms: [how and when to contact between meetings] +- Accountability standard: [what quality of work is expected] +- Review cycle: [when the relationship itself will be evaluated] + +## Current Development Focus +- Short-term (90 days): [specific goal] +- Medium-term (12 months): [specific goal] +- Succession indicator: [what would signal this mentee could mentor others] + +## Power Dynamics Check +- [ ] Am I taking credit for their work? +- [ ] Am I using them for my projects? +- [ ] Am I tethering them to my timeline? +- [ ] Am I discouraging other mentors? +- [ ] Am I allowing self-destructive patterns? +``` + +--- + +## Related Skills + +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- Whitmore's four-stage coaching conversation framework provides the structural backbone for formal coaching sessions; this skill covers the daily, informal practices that surround and extend those sessions. +- **[Teaching and Leading](../../content/skills/people/teaching-and-leading.md)** -- Extends the coach-student mindset into distributed leadership and mirror-neuron-based modelling techniques for team development. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework explains why mentees withhold problems and mistakes; a mentor who has not established psychological safety in the dyad will receive curated updates rather than honest ones. +- **[Leadership Pipeline](../../content/skills/frameworks/leadership-pipeline.md)** -- The pipeline model identifies the transition points where mentoring is most critical -- from individual contributor to manager, from manager to director -- and what capabilities each transition demands. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness and empathy are the mentor's primary tools; without them, mentoring degrades into lecturing. diff --git a/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md b/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md deleted file mode 120000 index 818e751..0000000 --- a/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/myers-briggs-type-indicator.md \ No newline at end of file diff --git a/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md b/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md new file mode 100644 index 0000000..d5b3295 --- /dev/null +++ b/plugins/foreman/skills/myers-briggs-type-indicator/SKILL.md @@ -0,0 +1,203 @@ +--- +name: "myers-briggs-type-indicator" +description: "Maps team cognitive diversity using the MBTI four-dichotomy personality framework: Extraversion/Introversion, Sensing/Intuition, Thinking/Feeling, Judging/Perceiving. Use when diagnosing co-founder communication friction, designing cognitively diverse teams, adapting communication style for different audiences, resolving recurring interpersonal conflicts, or identifying blind spots in team composition." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - personality + - team-composition + - communication + - hiring + - leadership-style + - self-awareness +related_skills: + - emotional-intelligence + - johari-window + - psychological-safety + - neuro-linguistic-programming +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Myers-Briggs Type Indicator + +The most widely administered personality instrument in the world -- taken by an estimated 50 million people and used by 88% of Fortune 500 companies -- is one that a significant portion of academic psychologists consider scientifically dubious. That tension is itself instructive. The Myers-Briggs Type Indicator, developed by Katharine Cook Briggs and her daughter Isabel Briggs Myers based on Carl Jung's theory of psychological types, persists not because it meets the psychometric standards of the Big Five personality model but because it does something the Big Five does not: it gives people a shared, non-judgmental language for talking about differences in how they perceive the world and make decisions. For entrepreneurs building teams under pressure, MBTI's value is practical rather than predictive. It does not tell you who will succeed. It tells you why your co-founder's approach to deadlines drives you to distraction, and why your head of sales and your head of engineering seem to be speaking different languages even when they agree on the goal. + +--- + +## The Framework + +MBTI classifies personality along four dichotomies, producing 16 possible type combinations. Each dichotomy represents a preference -- not an ability, not a fixed trait, but a tendency toward one mode of functioning over another. The analogy is handedness: most people can write with either hand, but one feels natural and the other requires effort. + +### The Four Dichotomies + +**1. Extraversion (E) vs. Introversion (I) -- Energy Direction** + +| Extraversion | Introversion | +|-------------|-------------| +| Energised by external interaction | Energised by internal reflection | +| Thinks out loud; processes through conversation | Thinks internally; processes before speaking | +| Breadth of relationships | Depth of relationships | +| Action-oriented; prefers to act, then reflect | Reflection-oriented; prefers to reflect, then act | + +Startup relevance: Extraverted founders excel at networking, pitching, and energising teams through visibility. Introverted founders excel at deep strategic thinking, listening to customers, and building products with concentrated focus. Neither orientation is superior; both are necessary at different moments. The danger is assuming everyone on the team shares the founder's energy orientation. + +**2. Sensing (S) vs. Intuition (N) -- Information Gathering** + +| Sensing | Intuition | +|---------|-----------| +| Focuses on concrete, present facts | Focuses on patterns, possibilities, future implications | +| Detail-oriented; trusts direct experience | Big-picture; trusts conceptual connections | +| Prefers proven methods | Prefers innovation and novelty | +| Asks "What is?" | Asks "What could be?" | + +Startup relevance: The S/N dichotomy is the most frequent source of co-founder friction. Sensing-oriented co-founders want data, specifics, and proven models. Intuition-oriented co-founders want vision, possibility, and novel approaches. When the CTO (often S) asks "Show me the data" and the CEO (often N) responds with "Trust the vision," neither is wrong -- they are processing through different information-gathering preferences. + +**3. Thinking (T) vs. Feeling (F) -- Decision Making** + +| Thinking | Feeling | +|----------|---------| +| Decides based on logical analysis and objective criteria | Decides based on values, impact on people, and harmony | +| Seeks truth | Seeks tact | +| Comfortable with impersonal critique | Sensitive to the human dimension of decisions | +| Asks "Is this logical?" | Asks "What impact will this have on people?" | + +Startup relevance: The T/F dichotomy becomes critical during painful decisions -- layoffs, performance management, ending partnerships. Thinking-preference leaders risk making correct decisions that destroy team trust through insensitive execution. Feeling-preference leaders risk delaying necessary decisions to avoid discomfort, allowing problems to compound. + +**4. Judging (J) vs. Perceiving (P) -- Orientation to Structure** + +| Judging | Perceiving | +|---------|------------| +| Prefers closure and decisiveness | Prefers openness and flexibility | +| Plans ahead; works methodically | Adapts in the moment; works in bursts | +| Comfortable with deadlines and schedules | Energised by last-minute pressure | +| Seeks to resolve ambiguity | Tolerates ambiguity comfortably | + +Startup relevance: J/P tension is visible in every sprint planning meeting. Judging types want clear plans, committed timelines, and defined scope. Perceiving types want optionality, room for pivoting, and freedom to follow emerging opportunities. Early-stage startups, which exist in permanent ambiguity, structurally favour P-orientation -- but eventually need J-discipline to scale execution. + +### Type Dynamics and Team Composition + +The 16 types are not merely four binary choices stacked together; they interact. Each type has a dominant function (the strongest preference), an auxiliary function (the support), a tertiary function (developing), and an inferior function (the blindspot). Understanding type dynamics helps explain why an ENTJ leader (dominant extraverted thinking) and an INFP team member (dominant introverted feeling) can create explosive friction: each person's strength is the other's blindspot. + +For team composition, the research-informed principle is cognitive diversity: teams that span the four dichotomies outperform homogeneous teams on complex problems, though they experience more friction during the process. The friction is the feature, not the bug -- it ensures that details are not ignored (S), possibilities are explored (N), logical rigour is applied (T), and human impact is considered (F). + +--- + +## Prompts + +**Prompt 1 -- Team Type Mapping:** +> Based on these behavioural descriptions of my team members, estimate their likely MBTI types and map the team's cognitive diversity: [describe each person's communication style, decision-making approach, energy patterns, and response to ambiguity]. Identify where the team clusters (shared preferences) and where it has gaps. Recommend specific actions to compensate for missing perspectives -- either through hiring, advisory relationships, or structured processes that force the team to consider its blind spots. + +**Prompt 2 -- Co-Founder Friction Diagnosis:** +> My co-founder and I are experiencing recurring friction around [describe the pattern -- e.g., decision speed, risk tolerance, communication style, planning approach]. Based on these descriptions of our respective styles, identify the likely MBTI dichotomy driving the tension: my style: [describe], their style: [describe]. Translate the friction from "right vs. wrong" into "different cognitive preferences" and recommend specific protocols we can adopt to leverage both perspectives rather than fight over which is correct. + +**Prompt 3 -- Communication Adaptation:** +> I need to present [topic -- e.g., a strategic pivot, a new initiative, a difficult decision] to a group that includes [describe audience members and their likely types]. Design multiple versions of the key message, each adapted to a different MBTI preference pair: one optimised for ST (sensing-thinking), one for SF (sensing-feeling), one for NT (intuition-thinking), and one for NF (intuition-feeling). Highlight what each version emphasises and what it de-emphasises. + +**Prompt 4 -- Hiring Complement Analysis:** +> My founding team consists of [describe types/preferences]. We are hiring for [role]. Based on our team's current type composition and the requirements of this role, recommend the personality preferences that would most complement our existing team. Explain which of our current blind spots this hire would address and what new tensions to anticipate (with mitigation strategies). + +--- + +## Use Cases + +**Early-traction startup with co-founder communication breakdown** + +Two co-founders of an edtech startup have escalating disagreements that are eroding their working relationship. The CEO (likely ENFP -- extraverted, intuitive, feeling, perceiving) generates ideas rapidly, changes direction frequently, and makes decisions based on passion and user stories. The CTO (likely ISTJ -- introverted, sensing, thinking, judging) wants detailed specifications, stable priorities, and decisions grounded in data. Each interprets the other's style as a character flaw: the CEO sees the CTO as rigid and uninspired; the CTO sees the CEO as chaotic and unreliable. MBTI reframes the dynamic: neither is flawed; they process information and make decisions through fundamentally different cognitive preferences. The intervention establishes a structured protocol: the CEO creates a "vision document" for each initiative (satisfying the N preference), which the CTO then translates into a "specification document" (satisfying the S preference). Disagreements are routed through a shared decision matrix that incorporates both data (T) and impact assessment (F). The relationship stabilises within a month. + +**Growth-stage company restructuring teams for product launch** + +A 75-person company preparing for a major product launch assembles a cross-functional team from engineering, design, marketing, and sales. Initial meetings are unproductive: engineering wants detailed timelines (J), marketing wants flexibility to respond to competitor moves (P), design insists on user research (S/F), and sales pushes for features that close deals (S/T). The VP of Product administers informal MBTI assessments and maps the team's type distribution, revealing a heavy ST cluster in engineering and an NF cluster in design, with marketing and sales split. Armed with this map, the VP restructures meetings: technical reviews are S/T-optimised (data, specifics, timelines), creative sessions are N/F-optimised (possibilities, user stories, open exploration), and integration meetings deliberately include all preferences with a facilitator who ensures each cognitive style gets airtime. The product launches on schedule -- not because anyone changed their type, but because the process was designed to leverage all types rather than privilege one. + +--- + +## Anti-Patterns + +**1. Using MBTI as a hiring filter.** This is the most prevalent and damaging misapplication. MBTI does not predict job performance, and using it to screen candidates is both scientifically unsupported and ethically questionable. Research consistently shows that MBTI type does not reliably predict success in any role. Use it to understand communication dynamics after hiring, not to make hiring decisions. + +**2. Treating type as destiny.** "I'm an introvert, so I can't do sales" is a fixed-mindset application of a tool that was designed to illuminate preferences, not define limits. Every person can operate outside their preferences -- it simply requires more energy. Conflating preference with inability is a distortion of the framework. + +**3. Weaponising type in conflict.** "That's just your T talking" or "You're being such a J right now" turns a communication tool into an ad hominem attack. Type language should explain behaviour, not excuse it or dismiss it. + +**4. Over-relying on a framework with known psychometric limitations.** MBTI's test-retest reliability is lower than academic psychologists prefer -- studies show that 50% of people receive a different type classification when retested after five weeks. The framework is most useful when treated as a rough map of preferences rather than a precise measurement of personality. Founders who treat MBTI types as rigid categories mistake the map for the territory. + +**5. Assembling teams purely by type diversity.** Cognitive diversity matters, but so do domain expertise, cultural fit, work ethic, and interpersonal chemistry. A team with perfect type diversity but poor trust will underperform a less diverse team with strong cohesion. MBTI is one lens among many for team composition. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Co-founder dynamics, first-hire compatibility | MBTI explains interpersonal friction and provides shared language for navigating preference differences | +| Growth | Team composition, management layer communication | MBTI informs team design and helps managers adapt communication to different report types | +| Scale | Organisational culture, cross-functional alignment, M&A integration | MBTI identifies cultural clashes between departments or acquired companies with different cognitive profiles | + +At early traction, MBTI's primary value is translating interpersonal friction from personal conflict into cognitive-preference difference. When two co-founders understand that their disagreement about planning rigour reflects a J/P preference difference rather than a competence gap, they can design processes that honour both orientations instead of fighting about who is right. + +At growth, MBTI becomes a management development tool. Training managers to recognise and adapt to different preferences in their reports improves one-on-one effectiveness, feedback quality, and delegation accuracy. An ST manager who learns to frame assignments differently for NF reports (leading with purpose and impact rather than specifications and deadlines) will see better outcomes without changing the substance of the assignment. + +At scale, MBTI's organisational application emerges. Merging two companies or restructuring departments often produces culture clash that is partly a type clash. Engineering-dominated organisations tend toward ST cultures; marketing-dominated organisations toward NF cultures. Making these preferences visible and creating bridging protocols reduces post-merger friction and cross-functional dysfunction. + +--- + +## Output Template + +```markdown +# Team Cognitive Diversity Map -- [Team Name] + +**Prepared for:** Team / Hiring Manager +**Date:** [Date] +**Purpose:** [Team formation / Conflict resolution / Hiring complement] + +## Individual Type Estimates + +| Team Member | Estimated Type | Confidence | Key Behavioural Evidence | +|------------|---------------|------------|------------------------| +| [Name] | [XXXX] | [High/Medium/Low] | [Observable behaviours that suggest this type] | + +## Team Preference Distribution + +| Dichotomy | Count E/I | Count S/N | Count T/F | Count J/P | +|-----------|----------|----------|----------|----------| +| **Preference A** | [E: N] | [S: N] | [T: N] | [J: N] | +| **Preference B** | [I: N] | [N: N] | [F: N] | [P: N] | + +## Cognitive Gaps +- **Under-represented preference:** [Which preference is missing or under-represented] +- **Impact:** [What perspectives or approaches the team systematically neglects] +- **Compensation strategy:** [Hiring, advisory, or process-based mitigation] + +## Friction Points Predicted + +| Pair/Group | Preference Clash | Likely Symptom | Recommended Protocol | +|-----------|-----------------|----------------|---------------------| +| [Person A + B] | [e.g., J vs. P] | [e.g., conflict over planning rigidity] | [Specific process to manage] | + +## Communication Adaptation Guide + +| Audience Type | Lead With | Avoid | Format Preference | +|--------------|-----------|-------|-------------------| +| ST | Data, specifics, proven results | Abstract vision, ungrounded possibilities | Structured documents, bullet points | +| SF | People impact, concrete examples | Impersonal logic, theoretical frameworks | Stories, case studies, face-to-face | +| NT | Strategic implications, novel approaches | Excessive detail, status quo arguments | Conceptual frameworks, debate format | +| NF | Purpose, meaning, human potential | Pure metrics, reductive analysis | Narrative, collaborative discussion | +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- MBTI maps cognitive preferences; EQ provides the self-awareness and empathy to navigate the interpersonal dynamics those preferences create. +- **[Johari Window](../../content/skills/frameworks/johari-window.md)** -- MBTI type functions as a lens for understanding one's "blind spot" quadrant, revealing patterns that others see clearly but the individual does not. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Teams with high type diversity need high psychological safety; without it, minority-preference members self-censor, and the team loses the cognitive diversity it was designed to provide. +- **[Belbin Team Roles](../../content/skills/frameworks/belbin-team-roles.md)** -- Belbin's functional roles complement MBTI's cognitive preferences; together they reveal both how team members think and what contribution they naturally make. +- **[Understanding People](../../content/skills/people/understanding-people.md)** -- MBTI provides a structured vocabulary for understanding cognitive differences, which deepens the broader practice of reading and adapting to the people around you. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Mapping team MBTI profiles reveals the cultural tendencies that emerge from cognitive clustering, helping leaders design processes that honor all preference types. diff --git a/plugins/foreman/skills/negotiation-game-theory/SKILL.md b/plugins/foreman/skills/negotiation-game-theory/SKILL.md deleted file mode 120000 index 3c99c16..0000000 --- a/plugins/foreman/skills/negotiation-game-theory/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/negotiation-game-theory.md \ No newline at end of file diff --git a/plugins/foreman/skills/negotiation-game-theory/SKILL.md b/plugins/foreman/skills/negotiation-game-theory/SKILL.md new file mode 100644 index 0000000..f56814e --- /dev/null +++ b/plugins/foreman/skills/negotiation-game-theory/SKILL.md @@ -0,0 +1,258 @@ +--- +name: "negotiation-game-theory" +description: "Structures negotiations as formal games with mathematically defined bottom lines, solution sets, and optimal agreement points using the Nash Product Solution. Provides the strategic and quantitative complement to relationship-based negotiation frameworks. Use when calculating walk-away points for fundraising rounds, modelling acquisition pricing, determining fair splits in partnership deals, preparing for salary or compensation negotiations, structuring vendor contracts with measurable payoffs, or analysing why a negotiation reached a specific outcome." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - nash-product + - bottom-line + - deal-making + - zopa + - game-theory + - term-sheets + - pricing +related_skills: + - coalition-and-partnership-games + - evolutionary-strategy + - win-win-negotiation + - trust-equation + - cialdini-influence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Negotiation Game Theory + +Every negotiator has a mathematical bottom line -- the minimum outcome they will accept before walking away. Most never calculate it. They arrive at the table armed with aspirations and anxiety, anchoring on round numbers or gut feelings, when the strategic structure of the negotiation is already fully determined by three quantities: what each side gets if the deal fails, what the deal creates if it succeeds, and how each side values incremental gains. Finding the other party's bottom line -- their true minimum acceptable outcome -- is worth more than any persuasion technique, any rapport-building exercise, any tactical concession. The relationship-based approach taught by Fisher and Ury (see [Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)) handles the human dynamics superbly. This skill addresses the strategic geometry underneath. + +--- + +## The Framework + +### Negotiation as a Cooperative Game + +A negotiation between two parties, A and B, is a cooperative game with a specific structure. If the negotiation succeeds, it produces a total payoff that exceeds what either party could achieve alone. If it fails, each party falls back to their standalone value -- what they can earn without the other. + +Three values define every negotiation: + +| Variable | Meaning | Example (Series A Fundraise) | +|----------|---------|------------------------------| +| **Total deal value** | What the cooperation produces | $20M company valuation created by capital + execution | +| **A's standalone value** | What A gets if the deal fails | Founder bootstraps at $2M valuation growth/year | +| **B's standalone value** | What B gets if the deal fails | Investor deploys capital elsewhere at 15% expected return | + +The fundamental precondition for any negotiation: the deal must create surplus. The total deal value must exceed the sum of both parties' standalone values. If it does not, there is nothing to negotiate -- both sides are better off walking away. This seems obvious, yet founders regularly enter negotiations where no surplus exists (the investor's alternative returns exceed what the startup can plausibly deliver, or the customer's internal solution outperforms the vendor's offering). + +### The Objective Bottom Line + +The bottom line is not what you hope to get. It is the minimum you must receive for the negotiation to be rational. + +**A's objective bottom line:** A must receive at least their standalone value from the deal. If the negotiated outcome gives A less than what A could achieve alone, A should walk away. + +**B's objective bottom line:** B must receive at least their standalone value. The remaining deal surplus -- total value minus B's standalone -- is the maximum A can rationally claim. + +The **negotiation range** (equivalent to ZOPA in Fisher and Ury's framework, but defined mathematically) is the interval between each party's bottom line: + +- A's payoff ranges from A's standalone value (minimum) to total value minus B's standalone (maximum) +- B's payoff ranges from B's standalone value (minimum) to total value minus A's standalone (maximum) + +**A practical illustration:** + +A SaaS startup (A) negotiates a distribution partnership with a major platform (B). + +- Partnership total value: $3M additional annual revenue +- Startup's standalone growth without partnership: $800K annual revenue +- Platform's standalone value from alternative integration partner: $600K annual revenue + +Negotiation range: +- Startup receives between $800K and $2.4M ($3M - $600K) +- Platform receives between $600K and $2.2M ($3M - $800K) + +Any split within this range is rational for both parties. Any split outside it means at least one party would be better off alone -- and will eventually realise it. + +### The Solution Set + +When the negotiation range is not a single point but an interval (the common case), many possible agreements exist. The set of all mutually acceptable outcomes is the **solution set**. Within it, every point represents a deal both parties prefer to their standalone alternative. + +The solution set's size reveals the negotiation's character: + +| Solution Set Size | Interpretation | Negotiation Dynamic | +|-------------------|---------------|---------------------| +| **Large interval** | Significant surplus to divide | Both parties have strong incentive to agree; conflict is about distribution, not feasibility | +| **Narrow interval** | Small surplus | Agreement is fragile; minor miscalculations or emotional friction can collapse the deal | +| **Single point** | Exact one outcome satisfies both | No room to negotiate; take it or leave it | +| **Empty set** | Bottom lines do not overlap | No deal is possible; negotiation should not begin | + +Experienced negotiators assess the solution set before entering the room. If the set is large, they focus on capturing a favourable position within it. If narrow, they focus on ensuring the deal closes at all. If empty, they decline the meeting. + +### The Nash Product Solution + +With many possible agreements in the solution set, which one should the parties select? John Nash (Nobel Prize, 1994) proposed an elegant answer: choose the agreement that maximises the product of both parties' gains over their standalone values. + +The principle in plain language: the optimal deal is the one where the product of "how much better off A is versus walking away" times "how much better off B is versus walking away" is largest. + +**Why the product, not the sum?** Maximising the sum would favour whichever party has a larger absolute gain, regardless of proportionality. The product inherently balances both parties' interests -- it penalises deals that give one side almost everything and the other almost nothing, because a near-zero factor kills the product. + +**Decision table for the partnership example above:** + +| A's Payoff | B's Payoff | A's Gain Over Standalone | B's Gain Over Standalone | Nash Product | +|-----------|-----------|-------------------------|-------------------------|-------------| +| $800K | $2,200K | $0 | $1,600K | 0 | +| $1,200K | $1,800K | $400K | $1,200K | 480,000 | +| $1,500K | $1,500K | $700K | $900K | 630,000 | +| $1,700K | $1,300K | $900K | $700K | **630,000** | +| $1,800K | $1,200K | $1,000K | $600K | 600,000 | +| $2,400K | $600K | $1,600K | $0 | 0 | + +The Nash Product is maximised at $1,500K/$1,500K and $1,700K/$1,300K (both yield 630,000). When both parties have symmetric utility functions (each dollar is worth the same to both), the Nash solution converges toward an even split of the surplus. When utility functions differ -- and they often do -- the solution shifts toward the party for whom each marginal dollar matters more. + +### Asymmetric Utility and Its Practical Consequences + +Parties rarely value money identically. A cash-strapped startup values the first $500K of a deal far more than the second $500K (diminishing marginal utility, or more practically, the difference between survival and comfort). A well-capitalised corporation may have nearly linear utility -- each dollar is worth roughly the same. + +This asymmetry shifts the Nash Product Solution. The party with higher marginal utility for early gains (the startup) rationally accepts a smaller total share, because the utility they extract from it is disproportionately high. The party with lower marginal utility (the corporation) captures a larger nominal share but extracts proportionally less utility. + +The strategic implication: **reducing your desperation -- increasing your standalone value or decreasing your marginal utility for the deal -- shifts the Nash solution in your favour.** This is the game-theoretic foundation for why having alternatives (a strong BATNA, in Fisher and Ury's language) is the single most powerful negotiation lever. It is not psychology. It is mathematics. + +### Connecting the Two Negotiation Frameworks + +| Dimension | Win-Win Negotiation (Fisher & Ury) | Negotiation Game Theory | +|-----------|------------------------------------|------------------------| +| Core question | "What are the interests behind the positions?" | "What are the payoff functions and standalone values?" | +| Power source | BATNA (best alternative) | Standalone value and utility function | +| Zone of agreement | ZOPA (qualitative overlap of interests) | Solution set (quantitative interval of mutually rational outcomes) | +| Optimal outcome | Mutual gain through creative options | Nash Product maximisation | +| Primary tool | Empathy, interests, objective criteria | Payoff analysis, utility estimation, marginal contribution | +| Blind spot | Assumes parties can discover mutual gains through dialogue | Assumes payoffs are quantifiable and utility functions are known | + +Neither framework is sufficient alone. Fisher and Ury's approach excels at expanding the pie through creative option generation and managing the relational dimension. Game theory excels at analysing how to divide the pie once its size is established. The sophisticated negotiator prepares with both. + +--- + +## Prompts + +**Prompt 1 -- Bottom Line Calculation:** +> I am entering a negotiation with [describe the other party] regarding [describe the deal]. Help me calculate my objective bottom line using negotiation game theory. My standalone value (what I get if this deal fails) is approximately [estimate]. The other party's standalone is approximately [estimate]. The total value the deal would create is approximately [estimate]. Calculate the solution set, identify the Nash Product Solution assuming symmetric utility, and then adjust for any utility asymmetries I should consider: [describe any cash constraints, time pressure, or other factors affecting how each side values marginal gains]. + +**Prompt 2 -- Opponent Bottom Line Estimation:** +> I am negotiating [describe deal] with [describe party]. I need to estimate their objective bottom line. Here is what I know about their situation: [describe their alternatives, financial position, time pressure, and strategic priorities]. Using negotiation game theory, help me estimate: (1) their standalone value if this deal fails, (2) their likely utility function (linear, concave, or convex -- do they value early gains more or less?), (3) their probable bottom line, and (4) the Nash Product Solution given my estimates. Where are the biggest uncertainties in my estimate, and what questions should I ask to narrow them? + +**Prompt 3 -- Deal Structure Optimisation:** +> We have a preliminary agreement in a negotiation, but I want to evaluate whether the terms are close to the Nash Product optimum. The deal terms are: [describe]. My standalone alternative: [describe]. Their standalone alternative (estimated): [describe]. Total deal value: [estimate]. Calculate whether the current split is near the Nash optimum, whether I am leaving significant value on the table, and what restructuring (if any) would move the deal closer to the mathematically optimal point while remaining acceptable to both parties. + +**Prompt 4 -- Multi-Issue Negotiation Mapping:** +> I am negotiating a deal with multiple issues: [list issues -- e.g., price, payment terms, exclusivity, service levels, IP ownership]. For each issue, estimate the payoff implications for both sides and identify where utility asymmetries create trade opportunities. Using game theory principles, help me construct a package deal that maximises the overall Nash Product by trading low-cost/high-value items across issues. + +--- + +## Use Cases + +**Validation-Stage: Negotiating a Seed Term Sheet** + +A pre-revenue startup receives a term sheet from an angel syndicate. The proposed terms: $500K at a $4M pre-money valuation (the syndicate gets 11.1%). The founder's standalone: continue bootstrapping with $50K in savings, reaching an estimated $1.5M valuation in 18 months. The syndicate's standalone: deploy the $500K across three other deals with an expected 2.5x return. + +Total deal value if the investment succeeds: $10M estimated valuation at Series A (18 months out). The founder's share at the proposed terms: $8.9M. The syndicate's share: $1.1M. + +The solution set: founder receives between $1.5M (standalone) and $8.75M ($10M minus syndicate's $1.25M alternative return). The syndicate receives between $1.25M and $8.5M. + +Nash Product analysis reveals the proposed terms ($8.9M / $1.1M) are heavily founder-favourable -- the syndicate's gain over standalone is only $1.1M - $1.25M = negative. The syndicate is actually worse off than their alternative. The term sheet, paradoxically, should not exist at these terms unless the syndicate's actual expected return from alternatives is lower than 2.5x, or the startup's expected Series A outcome is higher than $10M. The framework forces both parties to examine whether the deal creates genuine surplus. + +**Growth-Stage: Acquisition Offer Analysis** + +A $30M ARR SaaS company receives a $150M acquisition offer from a strategic buyer. The founder's standalone: continue growing at 40% annually toward an IPO at $500M+ in three years. The acquirer's standalone: build a competing product for $20M over two years, reaching 30% of the target's capability. + +Total deal value: the acquirer gains $150M in strategic value (the target's product plus customer base integrated into the acquirer's platform). The founder's standalone is high ($500M IPO possibility) but risky. The acquirer's standalone is low ($20M build cost but uncertain outcome). + +Adjusting for risk and time value, the founder's risk-adjusted standalone is approximately $200M (discounting the $500M IPO by execution risk and time preference). The acquirer's standalone is approximately $40M (build cost plus opportunity cost). + +Solution set: founder receives between $200M and $110M... this is inverted. The founder's standalone ($200M risk-adjusted) exceeds the offer ($150M). The solution set is empty at the proposed price. The acquisition should not proceed at $150M unless the founder's risk adjustment is more aggressive (higher discount for execution risk) or the acquirer's total value creation is higher than estimated. The framework clarifies that the deal only makes sense above approximately $200M -- a number no amount of persuasion can change. + +--- + +## Anti-Patterns + +1. **Negotiating Without Calculating Your Bottom Line.** Entering a negotiation knowing what you want but not what you need. The bottom line is not an aspiration -- it is the mathematical boundary below which the deal is worse than no deal. Founders who cannot articulate their standalone value in quantitative terms are negotiating blind. + +2. **Assuming Symmetric Utility.** Treating every dollar as equally valuable to both sides. A venture fund deploying $2M from a $200M fund has nearly linear utility for the deal's outcome. A founder whose personal savings depend on the deal has sharply concave utility. Ignoring this asymmetry leads to agreements that the Nash Product Solution would reject. + +3. **Confusing the Solution Set with the Optimal Point.** Accepting any deal within the solution set as "good enough." Every point in the solution set is rational, but they are not equivalent. A deal at the edge of the solution set gives one party almost nothing over their standalone -- technically rational but practically fragile. The Nash Product Solution identifies the robust centre. + +4. **Applying Game Theory Without Relationship Management.** Using quantitative analysis as a substitute for Fisher and Ury's relational principles. Telling your counterpart "the Nash Product Solution suggests I should receive 62% of the surplus" is technically accurate and interpersonally catastrophic. Game theory informs your preparation and internal decision-making. The relationship framework governs how you conduct the conversation. + +5. **Overestimating Your Standalone Value.** Inflating what you could achieve without the deal, which raises your calculated bottom line and may cause you to reject value-creating agreements. Rigorous honesty about alternatives is essential. The founder who claims a $50M standalone valuation but has no term sheets and declining metrics is deluding themselves -- and the mathematics will not compensate for self-deception. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | First deals with uncertain values | Standalone values and deal values are highly speculative. Use ranges rather than point estimates. Calculate the solution set for best-case, base-case, and worst-case scenarios. If the solution set is empty in the base case, the deal is likely not viable. | +| Early Traction | Hiring, early partnerships, first revenue contracts | Payoffs become partially measurable. Use actual revenue data and market benchmarks to ground standalone estimates. The Nash framework is particularly useful for compensation negotiations -- equity grants should reflect the marginal contribution the hire brings. | +| Growth | Fundraising, enterprise sales, strategic partnerships | Both parties have established track records. Standalone values are estimable from comparable transactions, market data, and financial projections. This is where the framework is most directly applicable -- sufficient data exists to compute meaningful solution sets. | +| Scale | M&A, large-scale licensing, public-market transactions | Negotiations involve professional advisors (investment bankers, lawyers) who use variants of these models already. The founder's role shifts from performing the analysis to understanding and challenging the analysis their advisors present. Fairness opinions and valuation models are essentially applied Nash bargaining theory. | + +--- + +## Output Template + +```markdown +# Negotiation Analysis: [Deal Description] + +## Parties +- **Party A:** [Name/Description] +- **Party B:** [Name/Description] + +## Standalone Values +| Party | Standalone Value | Basis for Estimate | Confidence | +|-------|-----------------|-------------------|------------| +| A | [Value if deal fails] | [How estimated] | [High/Medium/Low] | +| B | [Value if deal fails] | [How estimated] | [High/Medium/Low] | + +## Deal Value +- **Total value if deal succeeds:** [Amount] +- **Surplus over standalone sum:** [Deal value - A standalone - B standalone] +- **Surplus exists?** [Yes/No -- if No, stop here] + +## Solution Set +- **A's range:** [A standalone] to [Deal value - B standalone] +- **B's range:** [B standalone] to [Deal value - A standalone] +- **Solution set size:** [Large / Narrow / Single point / Empty] + +## Nash Product Solution +| Scenario | A's Payoff | B's Payoff | A's Gain | B's Gain | Nash Product | +|----------|-----------|-----------|---------|---------|-------------| +| Proposed terms | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | +| Nash optimum (symmetric) | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | +| Nash optimum (adjusted for utility) | [Amount] | [Amount] | [Gain] | [Gain] | [Product] | + +## Utility Asymmetries +- **A's utility profile:** [Linear / Concave / Convex -- and why] +- **B's utility profile:** [Linear / Concave / Convex -- and why] +- **Effect on optimal split:** [Description] + +## Strategic Recommendations +1. [Key insight from the analysis] +2. [Recommended negotiation approach] +3. [Risk factors and contingencies] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- The essential relational complement; Fisher and Ury's framework excels at expanding the pie, while game theory determines how to divide it. +- **[Coalition and Partnership Games](../../content/skills/game-theory/coalition-and-partnership-games.md)** -- When negotiations involve more than two parties, the Shapley Value and core stability concepts from coalitional game theory apply. +- **[Evolutionary Strategy](../../content/skills/game-theory/evolutionary-strategy.md)** -- Repeated negotiations across a market follow evolutionary dynamics; understanding whether the market rewards hawks or doves informs negotiation posture. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Influence principles operate within the solution set identified by game theory; reciprocity and anchoring shift outcomes within the mathematically defined range. +- **[Competitive Negotiation](../../content/skills/negotiation/competitive-negotiation.md)** -- Translates the mathematical Nash Product Solution into practical anchoring, concession, and value-claiming tactics at the negotiating table. +- **[Game Theory Fundamentals](../../content/skills/game-theory/game-theory-fundamentals.md)** -- Provides the prerequisite concepts of Nash equilibrium and payoff analysis that bargaining-specific models build upon. diff --git a/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md b/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md deleted file mode 120000 index 54034dc..0000000 --- a/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/negotiation/negotiation-mindset-and-self.md \ No newline at end of file diff --git a/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md b/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md new file mode 100644 index 0000000..dd0bd8a --- /dev/null +++ b/plugins/foreman/skills/negotiation-mindset-and-self/SKILL.md @@ -0,0 +1,227 @@ +--- +name: "negotiation-mindset-and-self" +description: "Builds the internal foundation required before entering any + negotiation: identity as a negotiator, strategic self-awareness, emotional + self-management, assumption auditing, and deliberate style selection. Provides + practical self-assessment checklists and pre-negotiation protocols. Use when + preparing mentally for a high-stakes conversation, diagnosing why past + negotiations underperformed, recognising negotiation dynamics in daily + business interactions, coaching team members on negotiation readiness, or + choosing between competitive and cooperative approaches for an upcoming deal." +version: "1.0.0" +category: "negotiation" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - self-awareness + - emotional-management + - strategy + - preparation + - mindset + - decision-making +related_skills: + - competitive-negotiation + - win-win-negotiation + - negotiation-game-theory + - thomas-kilmann-conflict + - trust-equation + - stoic-unbiased-thought +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Negotiation Mindset and Self-Management + +Carrie Fisher once observed that everything is negotiable -- whether or not the negotiation is easy is another thing. The word itself derives from the Latin *negotiatus*: to carry on business. Not some business. Not the dramatic, table-pounding, term-sheet-waving kind. All of it. The founder who thinks negotiation begins when a term sheet lands on the desk has already lost dozens of negotiations that week -- with a co-founder over roadmap priorities, with an engineer over deadline expectations, with a landlord over lease terms, with a spouse over who handles school pickup so the pitch meeting can happen. The failure is not in technique. The failure is in identity. Most professionals do not see themselves as negotiators, and that blindness is extraordinarily expensive. + +--- + +## The Framework + +### Step 1: Adopt the Negotiator Identity + +The single largest barrier to negotiating well is not recognising when a negotiation is happening. A strategic communication process aimed at making a deal or solving a problem -- that is the working definition. By this standard, anyone in a business role spends the majority of their waking hours negotiating. Founders spend closer to all of them. + +The identity shift is concrete, not motivational. It means approaching every interaction with three questions: + +- What outcome do I want from this conversation? +- What does the other party want? +- What is the gap, and how will I close it? + +When these questions become habitual, conversations that previously felt like "just talking" reveal themselves as negotiation -- and become manageable with a framework rather than improvisation. + +**The cost of not seeing it:** During the Cuban Missile Crisis, certain military advisers nearly triggered nuclear war because they treated ship positioning as a military operation rather than what it actually was -- a language of negotiation between Kennedy and Khrushchev. The example is extreme. The principle is universal. Misidentifying a negotiation as something else leads to the wrong actions, wrong tone, and wrong outcomes. + +### Step 2: Confront the Comfort Trap + +Michael Porter's dictum -- "the essence of strategy is choosing what not to do" -- applies with particular force to negotiation. The natural human impulse is to do what feels comfortable: agree quickly to avoid tension, concede generously to preserve goodwill, avoid difficult requests because they feel awkward. Comfort is the enemy of strategy. + +A practical test: fold your arms. Now reverse them -- put the bottom arm on top. The physical awkwardness mirrors the psychological discomfort of asking for more than feels polite, holding silence after a counter-offer, or saying no to someone whose approval matters. Negotiation mastery requires doing hard, uncomfortable things with composure -- repeatedly, until the discomfort no longer shows. + +**The progression:** + +1. Develop knowledge of negotiation mechanics (this skill and its siblings) +2. Convert knowledge into practised skills through deliberate rehearsal +3. Skills produce confidence in the moment +4. Confidence enables strategic action under pressure + +### Step 3: Manage Yourself in the Face of Uncertainty + +Negotiations are defined by incomplete information. The other party's true bottom line, their alternatives, their internal politics, their timeline pressures -- none of this is fully visible. Deception (within ethical bounds) is an accepted feature of the process, not a bug. Sellers claim they cannot go a penny lower. Buyers claim budget constraints that may not exist. The uncertainty this creates tempts negotiators into one of two traps: naive trust or reflexive suspicion. + +**The Four-Question Self-Audit** (to be run before every significant negotiation): + +| Question | Purpose | +|----------|---------| +| What assumptions am I making to fill in the information I do not have? | Surfaces hidden assumptions before they drive decisions | +| What is the basis for these assumptions, and is that basis legitimate? | Separates evidence-based reasoning from wishful thinking | +| Am I building strategy on what I hope to be true or what is actually true? | Hope is not a strategy -- particularly not a negotiation strategy | +| Can I rely on the information I am using, and is it consistent with other evidence? | Tests whether data sources are credible and internally coherent | + +**A cautionary pattern:** A founder signs a partnership agreement with a friend's company, trusting verbal promises about marketing support, co-selling resources, and integration timelines. None are written into the contract. Six months later, the friend's company is acquired, the new owner has no knowledge of the promises, and the founder is locked into a disadvantageous agreement with no recourse. The error was not trusting a friend. The error was failing to audit the assumption that friendship and contractual obligation are the same thing. + +### Step 4: Choose Your Negotiation Style Deliberately + +Two fundamental approaches exist -- competitive and cooperative -- and the choice between them should never be left to temperament. + +**Competitive approach:** Claims value. Treats the pie as fixed. Uses ambitious asks, firm positions, and calculated concessions. Appropriate when the issue matters more than the relationship, or when the other party is already competing. (For deep execution, see [Competitive Negotiation](../../content/skills/negotiation/competitive-negotiation.md).) + +**Cooperative approach:** Creates value. Treats the pie as expandable. Uses interest exploration, option generation, and joint problem-solving. Appropriate when the relationship is critical, or when mutual gains are genuinely available. (For the theoretical foundation, see [Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md).) + +**The Thomas-Kilmann grid adapted for negotiation:** + +| | Low Issue Importance | High Issue Importance | +|---|---|---| +| **Low Relationship Importance** | Avoid (do not engage) | Compete (claim value) | +| **High Relationship Importance** | Accommodate (concede gracefully) | Collaborate or Compromise | + +The critical insight: the best outcomes accrue to negotiators who can execute both styles and switch between them as conditions demand. A founder who can only cooperate will be exploited by competitive counterparts. A founder who can only compete will destroy relationships that the business depends on. + +### Step 5: Apply Axelrod's Protocol for Uncertain Situations + +When the other party's approach is unknown, a robust default strategy exists -- derived from Robert Axelrod's tournament of Prisoner's Dilemma strategies: + +1. **Start cooperatively.** Test whether the other party will reciprocate. Cooperation is more efficient when both sides participate. +2. **Respond in kind.** If they compete, match the competition immediately. Delayed retaliation signals that exploitation is tolerable. If they cooperate, continue cooperating. +3. **Forgive.** When a competitive counterpart shifts toward cooperation, reciprocate. Holding grudges locks both parties into value-destroying competition. +4. **Be clear.** The other party must understand two things: cooperation will be rewarded, and competition will be matched. Clarity on both points builds the right kind of trust. + +This protocol prevents the two most common negotiation failures: cooperating with a shark (getting exploited) and competing with a collaborator (destroying a valuable relationship). + +### Recognising Signals in the Other Party's Moves + +Every move in a negotiation carries both substance (what is exchanged) and a signal (what the move reveals about the other party's strategy). An outrageously aggressive opening offer signals competitive intent. A reasonable offer paired with genuine questions about your priorities signals cooperative intent. Read the signal, not just the substance. + +--- + +## Prompts + +**Prompt 1 -- Negotiator Identity Audit:** +> I am a [role] at a [stage] company. List every interaction I likely have in a typical week that qualifies as a negotiation under this definition: "a strategic communication process to make a deal or solve a problem." For each, identify what is being negotiated, who the counterpart is, and what I typically leave on the table by not approaching it strategically. Then recommend the three highest-value negotiations I should prepare for deliberately. + +**Prompt 2 -- Pre-Negotiation Self-Assessment:** +> I am about to enter a negotiation regarding [describe situation]. Walk me through the Four-Question Self-Audit: (1) What assumptions am I likely making? (2) Are those assumptions evidence-based or hope-based? (3) What information am I relying on, and how reliable is it? (4) What is my default emotional response to uncertainty -- trust or suspicion -- and how might that default hurt me here? Then recommend specific preparation steps. + +**Prompt 3 -- Style Selection:** +> I need to negotiate [describe deal] with [describe counterpart and relationship]. Using the competitive vs. cooperative framework, help me determine: (1) How important is the issue relative to the relationship? (2) What signals has the other party already sent about their likely approach? (3) Should I lead with competition or cooperation? (4) What would trigger a switch to the other approach mid-negotiation? Provide a decision rationale I can brief to my team. + +**Prompt 4 -- Assumption Stress-Test:** +> Here are the key assumptions underlying my negotiation strategy for [describe deal]: [list assumptions]. For each assumption, assess: (a) what evidence supports it, (b) what evidence contradicts it, (c) what would happen to my strategy if this assumption is wrong, and (d) how I can verify or de-risk it before the negotiation begins. + +--- + +## Use Cases + +**Idea-Stage Founder Negotiating a Co-Founder Agreement** + +Two friends decide to build a company together. One has the technical skills; the other has the commercial relationships. Neither frames the equity conversation as a negotiation -- it feels too transactional for a friendship. They split 50/50 "because it's fair" without discussing vesting, decision rights, IP assignment, or what happens if one party leaves. Eighteen months later, the commercial co-founder contributes less and less while the technical co-founder builds the product. Resentment builds. The company fractures. The failure began with an identity problem: neither person saw themselves as a negotiator in the moment that mattered most. Applying the identity shift, the self-audit, and the style-selection grid would have surfaced the real issues -- contribution expectations, risk tolerance, exit terms -- before they became crises. + +**Growth-Stage CEO Preparing for a Board Negotiation** + +A Series A company needs to extend its runway by reducing burn rate. The CEO must negotiate with the board over whether to cut headcount (the board's preference) or renegotiate vendor contracts and defer a product line (the CEO's preference). The CEO's default style is accommodating -- she joined the board to cooperate, not fight. The self-audit reveals her core assumption: "If I push back, the board will lose confidence in me." Stress-testing this assumption uncovers that one board member has explicitly said he values "founders who defend their strategy with evidence." The CEO shifts from accommodation to a collaborative stance -- competing on substance (defending her preferred approach with data) while cooperating on style (framing the conversation as joint problem-solving). The board approves a hybrid plan. + +**Early-Traction Startup Negotiating First Enterprise Contract** + +A B2B SaaS startup receives a procurement-drafted contract from a large customer. The contract includes 120-day payment terms, unlimited liability, and IP assignment for all customisations. The founder's instinct: sign it, because losing the customer would be devastating. The Four-Question Self-Audit exposes the assumption that "this is our only shot at an enterprise customer." Research reveals three other companies in the pipeline at earlier stages. The founder's standalone value is not zero -- it is the value of pursuing those three alternatives without the drag of a punitive contract. Armed with this clarity, the founder competes on the three most damaging terms while cooperating on everything else, securing 45-day payment terms, capped liability, and shared IP ownership. + +--- + +## Anti-Patterns + +1. **Permanent Comfort Orientation.** Avoiding difficult conversations, accepting the first offer, and rationalising capitulation as "being reasonable." Comfort feels like wisdom. It is usually the absence of strategy. A negotiator who never feels uncomfortable is a negotiator who never asks for enough. + +2. **Identity Denial.** Insisting that "I'm not a negotiation person" or "I just focus on the product/code/numbers." This is not humility; it is abdication. Every professional negotiates constantly. The only question is whether they do it deliberately or accidentally. + +3. **Assumption Laundering.** Running the Four-Question Self-Audit but answering dishonestly -- converting hopes into "reasonable assumptions" without evidence. The audit works only with ruthless honesty. The founder who writes "our BATNA is strong" while knowing no other investor has returned a call is performing self-deception theatre. + +4. **Style Rigidity.** Knowing only one mode -- either always cooperative (which invites exploitation) or always competitive (which destroys relationships). The value is in the ability to switch. A founder who cooperates with a shark gets eaten. A founder who competes with a genuine collaborator drives away the partnership. + +5. **Confusing Personality with Strategy.** Introverts assuming they cannot negotiate effectively. Extroverts assuming their charm is a substitute for preparation. Research from Northwestern University demonstrates that even minimal rapport-building -- a five-minute phone call before a negotiation -- quadruples the likelihood of reaching a favourable agreement. Personality is a starting condition, not a destiny. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Co-founder agreements, early advisor terms, first vendor contracts | Every agreement sets a precedent. The identity shift is most critical here -- founders who do not see these early conversations as negotiations create structural problems that compound for years. | +| Validation | Pilot customer terms, angel/pre-seed fundraising, early hires | Uncertainty is maximal. The Four-Question Self-Audit is the primary tool. Assumptions about customer willingness to pay, investor interest, and hire motivations must be tested ruthlessly. | +| Early Traction | First enterprise contracts, seed fundraising, key hires with equity | Style selection becomes critical. Some counterparts (procurement teams, experienced investors) are professionally competitive. Recognising the game being played -- through signal reading, not wishful thinking -- determines whether the founder cooperates or competes. | +| Growth | Series A/B negotiations, strategic partnerships, executive hiring | The founder negotiates with increasingly sophisticated counterparts. Axelrod's protocol becomes the default: start cooperative, match competition, forgive pivots, be clear about boundaries. Emotional self-management under high-stakes pressure separates effective founders from reactive ones. | +| Scale | M&A discussions, board governance, large customer renewals | Negotiations involve professional negotiators (lawyers, bankers, corporate development). The founder's role shifts from executing negotiations to setting strategy and managing the team that executes. Self-audit at this stage focuses on whether the founder's assumptions about the company's value are grounded in evidence or ego. | + +--- + +## Output Template + +```markdown +# Pre-Negotiation Self-Assessment: [Deal/Situation] + +## Negotiator Identity Check +- **Am I treating this as a negotiation?** [Yes/No -- if No, reframe] +- **What is being negotiated?** [Specific outcomes at stake] +- **Who is my counterpart, and what is their likely approach?** [Competitive/Cooperative/Unknown] + +## Four-Question Self-Audit +| Question | My Answer | Evidence Quality | +|----------|-----------|-----------------| +| What assumptions am I making? | [List each assumption] | [Strong/Weak/None] | +| Are these assumptions evidence-based? | [For each: evidence or hope?] | | +| Am I building on truth or wishful thinking? | [Honest assessment] | | +| Is my information reliable? | [Source and consistency check] | | + +## Style Selection +- **Issue importance (1-10):** [Score] +- **Relationship importance (1-10):** [Score] +- **Recommended approach:** [Compete / Cooperate / Collaborate / Compromise / Avoid] +- **Trigger to switch approach:** [Specific signal that would change my strategy] + +## Comfort Zone Audit +- **What hard thing does this negotiation require me to do?** [Specific action] +- **What is my default avoidance behaviour?** [Conceding early / Avoiding the topic / Over-preparing without acting] +- **How will I overcome it?** [Rehearsal plan, accountability partner, or process commitment] + +## Uncertainty Map +- **What do I not know?** [List unknowns] +- **What is the other party likely hiding?** [Estimated hidden information] +- **What questions will I ask to reduce uncertainty?** [Specific questions] +``` + +--- + +## Related Skills + +- **[Competitive Negotiation](../../content/skills/negotiation/competitive-negotiation.md)** -- The execution companion for the competitive approach selected through this skill's style framework; covers anchoring, the ask, and concession strategy. +- **[Cooperative Negotiation](../../content/skills/negotiation/cooperative-negotiation.md)** -- The execution companion for the cooperative approach; empathy deployment and interest discovery techniques for expanding the deal before dividing it. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation provides the theoretical architecture for the cooperative approach; this skill decides when to use it. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- The mathematical layer beneath style selection; bottom-line calculations and Nash Product analysis inform whether the deal surplus justifies engaging at all. +- **[Thomas-Kilmann Conflict](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- The conflict-mode instrument that underpins the style-selection grid used here. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- The Stoic practice of pausing before reacting to impressions provides the philosophical foundation for the composure management that effective negotiation demands. diff --git a/plugins/foreman/skills/net-promoter-score/SKILL.md b/plugins/foreman/skills/net-promoter-score/SKILL.md deleted file mode 120000 index 764eb0d..0000000 --- a/plugins/foreman/skills/net-promoter-score/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/net-promoter-score.md \ No newline at end of file diff --git a/plugins/foreman/skills/net-promoter-score/SKILL.md b/plugins/foreman/skills/net-promoter-score/SKILL.md new file mode 100644 index 0000000..8fa593d --- /dev/null +++ b/plugins/foreman/skills/net-promoter-score/SKILL.md @@ -0,0 +1,251 @@ +--- +name: "net-promoter-score" +description: "Designs and analyzes Net Promoter Score programmes for measuring customer loyalty through promoter, passive, and detractor classification. Covers NPS calculation, segmented analysis, closed-loop feedback processes, and revenue impact modelling. Use when measuring product-market fit, diagnosing retention problems, benchmarking customer satisfaction, building a customer feedback system, or connecting loyalty metrics to revenue growth." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - validation + - early-traction + - growth + - scale +tags: + - customer-loyalty + - customer-feedback + - growth-metrics + - retention + - voice-of-customer +related_skills: + - balanced-scorecard + - product-life-cycle + - systems-thinking + - doblin-ten-types +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Net Promoter Score (NPS) + +"On a scale of zero to ten, how likely are you to recommend us to a friend or colleague?" One question. That is the entirety of the instrument that Fred Reichheld introduced in a 2003 Harvard Business Review article titled "The One Number You Need to Grow." It became, within a decade, the most widely used customer loyalty metric in the world -- adopted by two-thirds of the Fortune 1000, embedded in the dashboards of startups and enterprises alike, and debated with a fervour usually reserved for religion and operating system preferences. Reichheld's research at Bain & Company had demonstrated a finding that was both intuitive and, at the time, poorly quantified: the willingness of customers to recommend a company to others correlated more strongly with revenue growth than any other single customer metric. Not satisfaction. Not repurchase intent. Recommendation intent -- the act of staking one's personal reputation on the quality of someone else's product. + +The framework's elegance is its simplicity. Its peril is the same. + +--- + +## The Framework + +### The Calculation + +NPS converts a single survey question into a score ranging from -100 to +100. + +**Step 1: Ask the question.** + +"On a scale of 0 to 10, how likely are you to recommend [Company/Product] to a friend or colleague?" + +**Step 2: Classify respondents.** + +| Score | Classification | Behaviour Profile | +|-------|---------------|-------------------| +| 9-10 | **Promoters** | Loyal enthusiasts who actively refer others; highest lifetime value; lowest churn | +| 7-8 | **Passives** | Satisfied but unenthusiastic; vulnerable to competitive offers; unlikely to refer | +| 0-6 | **Detractors** | Unhappy customers who may actively discourage others; highest churn risk; potential brand damage | + +**Step 3: Calculate the score.** + +``` +NPS = (% Promoters) - (% Detractors) +``` + +Passives are excluded from the calculation but not from the analysis. They represent the swing population -- the customers who could become promoters with better experience or detractors with worse. + +**Worked Example:** + +A startup surveys 200 customers: +- 90 score 9-10 (Promoters): 45% +- 70 score 7-8 (Passives): 35% +- 40 score 0-6 (Detractors): 20% + +NPS = 45% - 20% = **+25** + +### Interpreting the Score + +NPS benchmarks vary significantly by industry, geography, and business model. Absolute scores mean less than relative position and trend. + +| NPS Range | General Interpretation | +|-----------|----------------------| +| 70+ | Exceptional -- world-class loyalty (Apple, USAA, Costco territory) | +| 50-69 | Excellent -- strong competitive advantage through customer advocacy | +| 30-49 | Good -- more promoters than detractors, but room for improvement | +| 0-29 | Adequate -- loyalty is not a competitive advantage | +| Below 0 | Problematic -- detractors outnumber promoters; growth is fighting an active headwind | + +**The trend matters more than the number.** An NPS of +20 that has improved from +5 over four quarters signals a company moving in the right direction. An NPS of +50 that has declined from +65 signals trouble that the absolute score obscures. + +### The Follow-Up: Where the Real Value Lives + +The NPS question produces a number. The follow-up question produces insight. + +"What is the primary reason for your score?" + +This open-ended response is where NPS transitions from a metric to a management system. Coding and analysing the qualitative responses reveals: +- What promoters value most (your competitive advantage, in their words) +- What detractors resent (your most damaging failure points) +- What passives find missing (the gap between satisfaction and enthusiasm) + +The discipline of "closing the loop" -- contacting detractors to understand and address their concerns, thanking promoters and asking for referrals, and nudging passives toward promoter territory -- transforms NPS from a survey into an operational process. + +### The Economic Logic + +Reichheld's research quantified what experienced entrepreneurs know intuitively: + +- **Promoters** have 2-3x the lifetime value of detractors +- **Promoters** generate 80-90% of positive referrals +- **Detractors** generate 80-90% of negative word-of-mouth +- Companies with NPS leaders in their industry grow at **2x** the rate of the average competitor + +The economic mechanism is straightforward: promoters buy more, stay longer, cost less to serve, and recruit new customers at zero acquisition cost. Detractors buy less, leave sooner, consume disproportionate support resources, and actively damage the brand through negative referrals. + +### NPS as a System, Not a Score + +Reichheld's later work, particularly *The Ultimate Question 2.0* (2011), emphasised that NPS as a metric is insufficient. NPS as a management system requires: + +1. **Measurement** -- Regular, consistent surveying at key touchpoints (post-purchase, post-support, quarterly relationship surveys) +2. **Analysis** -- Segmentation of NPS by customer cohort, product line, geography, and channel to identify specific drivers +3. **Action** -- Operational processes that translate NPS insights into product, service, and experience improvements +4. **Accountability** -- NPS targets integrated into team and individual performance metrics +5. **Closed-Loop Feedback** -- Direct follow-up with detractors (within 24-48 hours) and promoters + +--- + +## Prompts + +**Prompt 1 -- NPS Programme Design:** +> "Design an NPS measurement programme for my business: [describe company, product, customer segments, and current feedback mechanisms]. Specify: (1) which customer touchpoints to survey, (2) survey frequency, (3) how to segment results for actionable insight, (4) the closed-loop process for detractors and promoters, and (5) how to integrate NPS into our existing metrics dashboard." + +**Prompt 2 -- NPS Results Analysis:** +> "Analyse these NPS results: Overall NPS: [score]. Promoters: [%], Passives: [%], Detractors: [%]. Top reasons cited by promoters: [list]. Top reasons cited by detractors: [list]. Segment breakdown: [list NPS by segment]. Identify: (1) the highest-leverage improvement that would convert the most detractors, (2) the promoter insight we should amplify in marketing, (3) which customer segment requires the most urgent attention." + +**Prompt 3 -- NPS-to-Revenue Modelling:** +> "Model the revenue impact of improving our NPS from [current score] to [target score]. Assume: average customer lifetime value of [$X], current customer count of [N], annual churn rate of [X%], and referral rate of [X%] among promoters. Calculate the expected impact on: (1) retained revenue from reduced churn, (2) new revenue from increased referrals, (3) reduced support costs from fewer detractors." + +**Prompt 4 -- Competitive NPS Benchmarking:** +> "Benchmark our NPS of [score] against [industry/sector] standards. Identify where we stand relative to: (1) industry average, (2) industry leader, and (3) the NPS threshold that correlates with above-average growth in our sector. Based on the gap analysis, recommend three specific initiatives that companies in our sector have used to improve NPS by [target] points." + +--- + +## Use Cases + +**Validation-Stage Startup Measuring Product-Market Fit** + +A B2B SaaS startup with 50 paying customers uses NPS as a product-market fit signal. Sean Ellis's "very disappointed" test (a close cousin of NPS) suggests that 40% "very disappointed" correlates with product-market fit; NPS provides a complementary lens. The startup's first NPS survey returns +12: 38% promoters, 36% passives, 26% detractors. The follow-up question reveals that promoters love the product's speed and simplicity, while detractors cite missing integrations and unreliable data exports. The NPS data provides a precise product roadmap: invest in integrations (converting detractors) before adding new features (which passives are not asking for). After two quarters of integration-focused development, NPS rises to +38, and the detractor-cited reasons shift from "missing features" to "wish it did more" -- a qualitatively different complaint that signals readiness to expand the product scope. + +**Growth-Stage E-Commerce Company Identifying a Service Failure** + +An e-commerce company with 10,000 monthly orders has an overall NPS of +42, which appears healthy. Segmented analysis tells a different story: NPS among first-time buyers is +55, but NPS among repeat buyers is +18 and declining. The follow-up responses from repeat-buyer detractors cluster around two themes: inconsistent delivery times and a loyalty programme that feels "pointless." The segmentation reveals a retention crisis invisible in the aggregate score. The company redesigns its logistics partnerships (addressing delivery consistency) and replaces its points-based loyalty programme with a tier-based system offering tangible benefits (free shipping, early access). Within two quarters, repeat-buyer NPS rises to +39, and the cohort-level analysis shows that the company had been unknowingly operating two different businesses -- one excellent (acquisition) and one mediocre (retention). + +**Scale-Stage Platform Embedding NPS in Operational Governance** + +A marketplace platform with 500,000 active users implements NPS as a core governance metric across the organisation. Each product team owns a touchpoint NPS: onboarding NPS (product team A), transaction NPS (product team B), support NPS (customer experience team), and overall relationship NPS (executive team). Monthly NPS reviews surface anomalies: a sudden 15-point drop in transaction NPS among a specific user segment leads to the discovery of a payment processing bug that affected 3% of transactions but generated outsized negative sentiment. The bug was invisible in aggregate metrics but immediately visible in segmented NPS. Resolution within 48 hours, followed by closed-loop outreach to affected users, recovers the score within one month. + +--- + +## Anti-Patterns + +**Score Worship.** Obsessing over the NPS number while ignoring the qualitative data and the closed-loop process. The score is a thermometer; it tells you the temperature but not the disease. Companies that celebrate NPS milestones without acting on the underlying feedback have built a vanity metric, not a management system. + +**Survey Fatigue.** Surveying customers after every interaction, every transaction, and every support ticket. Over-surveying depresses response rates, biases results toward people with strong opinions (both positive and negative), and annoys the very customers you aim to delight. Survey at the moments that matter; leave the rest alone. + +**Gaming the Score.** Instructing frontline staff to ask only happy customers for feedback, or designing the survey flow to nudge toward higher scores. NPS gaming is organisationally corrosive because it destroys the metric's diagnostic value. When the score stops reflecting reality, leadership loses its most important feedback channel precisely when it needs it most. + +**Ignoring Passives.** The NPS formula excludes passives, which leads many companies to ignore them operationally. This is a strategic error. Passives are the largest swing group: converting even a fraction of passives to promoters has a larger impact on NPS (and revenue) than converting detractors, because the conversion effort is typically smaller and the base is larger. + +**Using NPS as the Only Customer Metric.** NPS measures loyalty intent, not loyalty behaviour. Customer satisfaction (CSAT), customer effort score (CES), churn rate, expansion revenue, and referral attribution each capture dimensions that NPS cannot. NPS works best as the keystone metric in a broader measurement system, not as a standalone indicator. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Signal for product-market fit | NPS above +30 with a small, representative sample is a strong PMF indicator | +| Early Traction | Identify the highest-impact product improvements | Detractor feedback is the most efficient product roadmap input at this stage | +| Growth | Build the NPS management system | Transition from periodic measurement to continuous, segmented, closed-loop operations | +| Scale | Embed NPS in organisational governance | NPS by team, touchpoint, segment, and geography drives accountability and surfaces problems at scale | + +At the validation stage, NPS should be measured with small samples (30-50 responses are sufficient for directional signal) and analysed primarily for qualitative patterns. The score matters less than what promoters and detractors say about why they scored as they did. + +During growth, the critical transition is from NPS as a metric (measured quarterly, reported to the board) to NPS as a system (measured continuously, segmented by touchpoint, with closed-loop processes for detractors and promoters). Companies that make this transition early build a structural advantage in customer retention that compounds over time. + +At scale, NPS becomes a governance instrument. Product teams own their touchpoint NPS. Executives own the relationship NPS. The gap between touchpoint scores and relationship score reveals the systemic issues that no single team can diagnose alone. + +--- + +## Output Template + +**Target Audience: Customer Experience Team / VP Customer Success** + +```markdown +# NPS Report: [Company Name] +## Period: [Date Range] + +### Score Summary +- **Overall NPS:** [Score] (Previous period: [Score], Change: [+/- N]) +- **Promoters:** [N] ([X%]) +- **Passives:** [N] ([X%]) +- **Detractors:** [N] ([X%]) +- **Response rate:** [X%] (from [N] surveys sent) + +### Trend +| Period | NPS | Promoters % | Passives % | Detractors % | +|--------|-----|-------------|------------|--------------| +| [Period -3] | [Score] | [%] | [%] | [%] | +| [Period -2] | [Score] | [%] | [%] | [%] | +| [Period -1] | [Score] | [%] | [%] | [%] | +| [Current] | [Score] | [%] | [%] | [%] | + +### Segmented NPS +| Segment | NPS | Sample Size | Change | Alert? | +|---------|-----|-------------|--------|--------| +| [Segment 1] | [Score] | [N] | [+/- N] | [Y/N] | +| [Segment 2] | [Score] | [N] | [+/- N] | [Y/N] | +| [Segment 3] | [Score] | [N] | [+/- N] | [Y/N] | + +### Key Drivers +**Why Promoters Promote (Top 3):** +1. [Theme] -- cited by [N]% of promoters +2. [Theme] -- cited by [N]% of promoters +3. [Theme] -- cited by [N]% of promoters + +**Why Detractors Detract (Top 3):** +1. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] +2. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] +3. [Theme] -- cited by [N]% of detractors -- Owner: [Team] -- Status: [Action taken] + +### Closed-Loop Status +- Detractors contacted within 48 hours: [X%] +- Detractors with resolved issues: [X%] +- Promoters thanked and asked for referral: [X%] + +### Revenue Impact Estimate +- Estimated revenue at risk from detractors: [$X] (based on [churn rate] and [LTV]) +- Estimated referral revenue from promoters: [$X] (based on [referral rate] and [LTV]) +- Net loyalty-driven revenue impact: [+/- $X] + +### Priority Actions +1. [Action] -- Target: Convert [X]% of [segment] detractors -- Owner: [Name] -- Deadline: [Date] +2. [Action] -- Target: Shift [X]% of passives to promoters -- Owner: [Name] -- Deadline: [Date] +3. [Action] -- Target: Amplify promoter advocacy through [channel] -- Owner: [Name] -- Deadline: [Date] +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- NPS is the most common metric in the Customer perspective of the Balanced Scorecard; the scorecard provides the strategic context for how NPS connects to financial outcomes through the causal chain. +- **[Product Life Cycle](../../content/skills/frameworks/product-life-cycle.md)** -- NPS behaves differently across product lifecycle phases; introduction-phase NPS is volatile, growth-phase NPS typically rises, maturity-phase NPS stabilises, and decline-phase NPS deteriorates. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- NPS operates within a system of feedback loops; promoters drive referrals that bring new promoters (reinforcing loop), while detractors drive negative word-of-mouth that deters potential customers. +- **[SMART Goals](../../content/skills/frameworks/smart-goals.md)** -- NPS targets must be SMART to drive action; "improve NPS" is a wish, while "increase enterprise NPS from +25 to +40 by Q3 through onboarding redesign" is an actionable commitment. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- The follow-up question that produces qualitative NPS insight depends on how you frame and present the survey; reader psychology principles improve response rates and data quality. +- **[Tipping Point](../../content/skills/frameworks/tipping-point.md)** -- Promoters are the engine of Gladwell's social epidemics; NPS identifies and quantifies the advocacy base whose word-of-mouth drives organic growth past the tipping point. diff --git a/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md b/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md deleted file mode 120000 index 48361dc..0000000 --- a/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/neuro-linguistic-programming.md \ No newline at end of file diff --git a/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md b/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md new file mode 100644 index 0000000..0abd2d1 --- /dev/null +++ b/plugins/foreman/skills/neuro-linguistic-programming/SKILL.md @@ -0,0 +1,194 @@ +--- +name: "neuro-linguistic-programming" +description: "Applies NLP techniques for rapport-building, reframing, anchoring, and meta-model questioning in business communication. Covers representational system matching, pacing and leading, and linguistic precision tools. Use when preparing for investor pitches, improving sales close rates, navigating board disagreements, refining communication for different audience types, or extracting actionable insights from vague customer feedback." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth +tags: + - communication + - persuasion + - rapport-building + - reframing + - sales +related_skills: + - emotional-intelligence + - johari-window + - myers-briggs-type-indicator + - grow-model +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Neuro-Linguistic Programming + +NLP may be the most commercially successful framework in business psychology that the academic establishment refuses to take seriously. Developed in the 1970s by Richard Bandler and John Grinder at the University of California, Santa Cruz, neuro-linguistic programming began as an audacious premise: that excellence is not mystical but structural, and that the specific communication patterns, mental models, and behavioural sequences of exceptionally effective people can be decoded, modelled, and taught to others. The academic critique -- that NLP lacks rigorous empirical validation -- is well documented and partially fair. What the critique misses is that NLP's practical toolkit for rapport-building, reframing, and communication has been quietly absorbed into executive coaching, sales training, negotiation methodology, and therapeutic practice worldwide. For entrepreneurs, whose daily work is fundamentally an exercise in influence -- persuading investors, customers, recruits, and partners -- NLP's techniques offer a pragmatic edge, provided they are applied with ethical grounding rather than manipulative intent. + +--- + +## The Framework + +NLP rests on several foundational principles and a practical toolkit that connects neurology ("neuro"), language ("linguistic"), and behavioural patterns ("programming"). The core claim is that subjective experience has a discoverable structure, and by altering that structure, outcomes change. + +### Core Presuppositions + +NLP operates from a set of working assumptions -- not empirical laws, but heuristics that shape its application: + +1. **The map is not the territory.** Every person's perception of reality is a model, not reality itself. Disagreements often stem not from conflicting facts but from conflicting maps. Recognising this dissolves unproductive arguments about who is "right." + +2. **People respond to their map of reality, not to reality itself.** A customer's objection reflects their internal representation of the product, not the product's actual properties. Change the representation, change the response. + +3. **The meaning of your communication is the response you get.** If a message is misunderstood, the communicator bears responsibility for adjusting, not the audience for failing to understand. This presupposition is transformative for founders who default to blaming audiences for "not getting it." + +4. **There is no failure, only feedback.** Every outcome, including undesired ones, provides information that can be used to calibrate the next attempt. This reframe is structurally identical to the lean startup's build-measure-learn cycle. + +5. **People already have all the resources they need.** The task is not to add capability but to access and organise existing internal resources more effectively. + +### The NLP Toolkit for Entrepreneurs + +**Rapport Building** + +Rapport is the foundation of influence. NLP codifies rapport-building into specific, practicable techniques: + +- **Matching and mirroring** -- subtly aligning body language, speech tempo, tonality, and breathing patterns with the other person. The mechanism is neurological: mirror neurons fire when we observe and replicate another person's patterns, creating a felt sense of connection. +- **Pacing and leading** -- first matching the other person's current state (pacing), then gradually shifting to the desired state (leading). A founder meeting a sceptical investor would first acknowledge and match the scepticism before redirecting toward opportunity. +- **Representational system matching** -- identifying whether a person processes information primarily through visual, auditory, or kinaesthetic channels (detected through language patterns and eye movements) and matching communication to that preference. + +**Reframing** + +Reframing changes the meaning of an experience by changing the context or perspective through which it is viewed. Two primary types: + +| Type | Mechanism | Example | +|------|-----------|---------| +| **Context reframe** | The same behaviour is valuable in a different context | "Your obsessive attention to detail slows us down" becomes "That same attention to detail is why our product has zero critical bugs in production" | +| **Content reframe** | The same event carries a different meaning | "We lost our biggest customer" becomes "We've eliminated our single-point-of-failure revenue dependency" | + +Reframing is not spin. Effective reframing requires the new perspective to be genuinely valid -- otherwise it registers as dishonest and destroys trust. + +**Anchoring** + +Anchoring associates a specific internal state (confidence, calm, focus) with a deliberate stimulus (a gesture, word, or visual cue). Through repetition, the stimulus reliably triggers the state. Athletes use this instinctively; NLP makes the process explicit. A founder who anchors a state of confident composure before investor pitches can access that state on demand. + +**Meta-Model Questions** + +The meta-model is a set of linguistic precision tools designed to challenge vague, distorted, or incomplete statements. Entrepreneurs encounter these linguistic patterns constantly: + +- **Deletions:** "We need to move faster." (Faster than what? At what? Who specifically?) +- **Generalisations:** "Customers don't care about that feature." (All customers? Which ones specifically? Based on what evidence?) +- **Distortions:** "The market is dying." (What specifically is happening that leads to that conclusion?) + +Meta-model questions restore specificity, turning impressionistic claims into actionable information. + +--- + +## Prompts + +**Prompt 1 -- Pitch Reframing:** +> I need to present a potential weakness to investors: [describe the weakness -- e.g., "We have no revenue yet," "Our market is small," "Our team lacks industry experience"]. Generate three reframes for this weakness: one context reframe, one content reframe, and one that combines both. Each reframe must be honest -- not spin -- and should position the weakness as a genuine strategic advantage or learning asset. Draft the specific language I would use in a pitch meeting. + +**Prompt 2 -- Communication Precision Audit:** +> Review the following team communication (email, Slack message, or meeting notes): [paste communication]. Identify all instances of deletions, generalisations, and distortions using the NLP meta-model. For each, generate the specific clarifying question that would restore precision. Then rewrite the communication with full specificity. + +**Prompt 3 -- Rapport Strategy for Key Meeting:** +> I have a critical meeting with [describe person -- role, what you know about their communication style, any past interactions]. Using NLP rapport principles, help me prepare: (a) likely representational system preference based on available clues, (b) pacing strategy for the first 5 minutes, (c) leading strategy for transitioning to my agenda, and (d) specific language patterns to match their communication style. Also identify 2-3 meta-model questions I should be prepared to ask. + +--- + +## Use Cases + +**Validation-stage founder refining investor narrative** + +A deeptech founder with a PhD in materials science consistently fails to connect with generalist investors. Technical pitches land well with domain experts but produce glazed expressions in broader audiences. NLP diagnosis reveals a representational system mismatch: the founder communicates almost exclusively in kinaesthetic and technical-abstract terms ("feel the weight of the data," "the molecular structure behaves differently under pressure") while most investors process information visually. The intervention involves restructuring the pitch to lead with visual language and spatial metaphors ("picture a market map where our technology sits here"), supported by diagrams and visual aids. The founder also applies pacing and leading -- opening with the investor's known concerns before transitioning to the technical differentiation story. Conversion rate for follow-up meetings increases from 15% to 45% within one quarter. + +**Growth-stage CEO navigating board disagreement** + +A CEO faces a divided board: two directors want aggressive international expansion, two want to consolidate domestically. Both sides have entrenched positions and escalating emotional investment. The CEO applies NLP reframing to restructure the conversation. Rather than debating "expand vs. consolidate" (a binary that forces winners and losers), the CEO reframes the question as "What is the minimum viable international experiment that strengthens our domestic position?" -- a context reframe that dissolves the apparent opposition. The CEO also uses meta-model questions to challenge the generalisations underlying both positions ("All international markets are risky" / "Domestic growth is saturated") and surface the specific data each side is relying on. The board reaches consensus on a pilot programme within a single session. + +**Early-traction sales team improving close rates** + +A B2B startup with strong inbound leads struggles with conversion from demo to contract. Analysis reveals that the sales team runs identical demo scripts regardless of buyer type. NLP-informed training introduces representational system matching (adjusting demo language for visual, auditory, and kinaesthetic buyers), pacing techniques (acknowledging the buyer's current provider positively before introducing the alternative), and reframing of common objections. Close rates improve from 12% to 22% over three months. + +--- + +## Anti-Patterns + +**1. Using NLP as covert manipulation.** The ethical boundary is straightforward: NLP techniques should be used to communicate more effectively and build genuine rapport, not to circumvent another person's rational judgment. Founders who use rapport techniques to mask bad deals, or reframing to obscure genuine weaknesses, will eventually be exposed -- and the reputational damage is compounding. + +**2. Treating NLP as a science with predictive certainty.** NLP's empirical foundations are contested. Practitioners who present its techniques as neurologically validated facts -- rather than useful heuristics derived from observing effective communicators -- lose credibility with analytically rigorous audiences. The correct framing: "This approach has been observed to work frequently; here is the hypothesised mechanism." + +**3. Over-indexing on technique at the expense of substance.** No amount of rapport-building, reframing, or anchoring compensates for a weak product, unclear value proposition, or fundamentally flawed business model. NLP enhances the transmission of substance; it does not replace it. + +**4. Rigid representational system categorisation.** People are not purely "visual" or "auditory" -- they use all systems and shift between them contextually. Treating representational system preferences as fixed personality types produces the same errors as any rigid personality taxonomy. + +**5. Ignoring cultural context in rapport techniques.** Mirroring and matching behaviours that are appropriate in one culture can be intrusive or offensive in another. Direct eye contact, physical proximity, speech volume, and emotional expressiveness carry dramatically different meanings across cultures. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Customer discovery conversations | Meta-model questions extract genuine needs from vague customer feedback; reframing helps founders hear critical feedback without defensiveness | +| Early Traction | Sales, pitch refinement, early hiring | Rapport techniques directly impact close rates and candidate conversion; representational system matching sharpens pitch effectiveness | +| Growth | Leadership communication, board management, team alignment | Reframing resolves internal strategic disagreements; pacing and leading helps navigate increasingly complex stakeholder dynamics | + +During validation, the meta-model is the most valuable NLP tool. Customer discovery interviews are plagued by deletions ("We'd probably use something like that"), generalisations ("Everyone in our industry does it this way"), and distortions ("That would never work here"). Precision questioning transforms vague signals into actionable product insights. + +At early traction, the emphasis shifts to rapport and influence. The founder is selling constantly -- to customers, to recruits, to investors. Matching communication to the audience's processing style and pacing before leading creates measurably better outcomes in these interactions. + +At growth, reframing becomes the power tool. Internal disagreements, board dynamics, and strategic pivots all require the ability to restructure how problems are perceived without dismissing legitimate concerns. The founder who reframes effectively builds coalitions; the one who argues positions creates factions. + +--- + +## Output Template + +```markdown +# Communication Strategy -- [Meeting/Pitch/Conversation] + +**Prepared for:** Team / Founder +**Date:** [Date] +**Context:** [Key meeting, negotiation, or presentation being prepared] + +## Audience Profile +- **Primary audience:** [Role, known preferences, past interactions] +- **Likely representational system:** [Visual / Auditory / Kinaesthetic -- with evidence] +- **Current emotional state (estimated):** [Based on context clues] +- **Key concerns to pace:** [What they're worried about] + +## Rapport Strategy +1. **Opening (Pacing):** [Specific language/approach for first 2-3 minutes] +2. **Transition (Leading):** [How to shift from their frame to yours] +3. **Matching points:** [Language patterns, tempo, and style to align with] + +## Reframes Prepared + +| Potential Objection/Weakness | Reframe Type | Specific Language | +|------------------------------|-------------|-------------------| +| [Objection 1] | [Context/Content] | "[Exact words to use]" | +| [Objection 2] | [Context/Content] | "[Exact words to use]" | +| [Objection 3] | [Context/Content] | "[Exact words to use]" | + +## Meta-Model Questions Ready +1. [Question targeting expected vague claim] +2. [Question targeting expected generalisation] +3. [Question targeting expected distortion] + +## Desired Outcome +[Specific, measurable outcome for this interaction] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- EQ provides the self-awareness foundation that prevents NLP techniques from becoming manipulation; empathy is the ethical guardrail for influence. +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- GROW's questioning methodology complements NLP's meta-model; both frameworks use precise questioning to move from vagueness to clarity and action. +- **[Myers-Briggs Type Indicator](../../content/skills/frameworks/myers-briggs-type-indicator.md)** -- MBTI preferences parallel NLP's representational systems as complementary lenses for understanding communication style differences. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- NLP's rapport and reframing techniques are practical tools within the broader leadership skill of ethical persuasion across stakeholder relationships. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- NLP's pacing-and-leading and representational system matching directly enhance how leaders structure and deliver narratives for maximum audience impact. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Cialdini's principles of social proof and reciprocity complement NLP's interpersonal techniques, providing both macro-level persuasion dynamics and micro-level communication adjustments. diff --git a/plugins/foreman/skills/organisational-culture/SKILL.md b/plugins/foreman/skills/organisational-culture/SKILL.md deleted file mode 120000 index 6c75a87..0000000 --- a/plugins/foreman/skills/organisational-culture/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/organisational-culture.md \ No newline at end of file diff --git a/plugins/foreman/skills/organisational-culture/SKILL.md b/plugins/foreman/skills/organisational-culture/SKILL.md new file mode 100644 index 0000000..df1d412 --- /dev/null +++ b/plugins/foreman/skills/organisational-culture/SKILL.md @@ -0,0 +1,200 @@ +--- +name: "organisational-culture" +description: "Audits organizational culture using Schein's three-level model: + visible artifacts, espoused values, and basic underlying assumptions. + Diagnoses gaps between stated values and actual behaviour to reveal the + invisible beliefs driving organizational dynamics. Use when experiencing + culture dilution during rapid hiring, planning M&A cultural integration, + diagnosing why culture change initiatives fail, or auditing founder imprint on + company norms." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - culture + - leadership + - organisational-design + - values + - assumptions +related_skills: + - tuckman-team-stages + - belbin-team-roles + - maslow-hierarchy + - radical-candor +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Organisational Culture + +What you see in an organisation -- the open-plan offices, the Friday beers, the branded hoodies -- is the tip of the iceberg. Roughly ten percent of culture is visible. The remaining ninety percent sits submerged: the unspoken beliefs, the unstated power hierarchies, the assumptions so deeply embedded that no one thinks to question them. Edgar Schein, the MIT professor who spent decades dissecting how organisations actually work, argued that most culture-change initiatives fail because they redecorate the tip while ignoring the mass below the waterline. The iceberg metaphor is not merely illustrative; it is diagnostic. Misread which level of culture you are dealing with, and your intervention will achieve nothing -- or worse, provoke the immune response that organisations mount against superficial change. + +Schein's framework identifies three distinct layers, each progressively harder to observe and exponentially harder to alter. Understanding these layers is not an academic exercise. For founders, it is the difference between building a company that scales with coherence and one that fractures under the weight of its own contradictions. + +--- + +## The Framework + +### Layer 1: Artifacts (The Visible Surface) + +Artifacts are everything you can see, hear, and touch when you walk into an organisation. Office layout. Dress code. Meeting rituals. The language people use in Slack channels. The way decisions get announced. These are tangible, immediately observable -- and profoundly misleading if interpreted without context. + +A startup with a foosball table and no dress code might appear egalitarian. The reality could be a cult of personality where the CEO's whims override all process. Artifacts are symptoms, not diagnoses. + +**Common artifacts include:** +- Physical environment and workspace design +- Published values and mission statements +- Rituals, ceremonies, and recurring events +- Stories and legends told about the company's origins +- Organisational charts and reporting structures +- Technology choices and communication tools + +### Layer 2: Espoused Values (What People Say Matters) + +One level below artifacts sit the declared beliefs, strategies, and philosophies. These are the values on the website, the principles recited during onboarding, the strategic priorities invoked in board meetings. Espoused values represent what the organisation *claims* to be. + +The critical question: do espoused values match actual behaviour? When a company proclaims "we value work-life balance" while promoting only those who answer email at midnight, a gap has opened between Layer 2 and Layer 3. This gap is where cynicism breeds and trust erodes. + +**Diagnostic indicators of alignment (or misalignment):** + +| Espoused Value | Aligned Behaviour | Misaligned Behaviour | +|----------------|-------------------|----------------------| +| "Innovation" | Budget for experiments, tolerance of failure | Punishing failed projects, rigid approval processes | +| "Transparency" | Open financials, candid all-hands | Information hoarding, surprise layoffs | +| "Customer first" | Support team empowered to act | Support metrics optimised for speed over resolution | +| "Meritocracy" | Promotions track results | Promotions track tenure or political skill | + +### Layer 3: Basic Underlying Assumptions (The Invisible Bedrock) + +The deepest layer consists of unconscious, taken-for-granted beliefs. These assumptions are so ingrained they feel like objective reality rather than cultural choices. They govern how people perceive problems, define truth, relate to time, and think about human nature. + +Schein identified several dimensions of basic assumptions: + +- **Relationship to environment:** Does the organisation believe it controls its market, or must adapt to it? +- **Nature of truth:** Is truth discovered through debate, authority, or data? +- **Human nature:** Are people fundamentally trustworthy (Theory Y) or requiring supervision (Theory X)? +- **Nature of relationships:** Is hierarchy natural, or should all voices carry equal weight? +- **Time orientation:** Does the culture privilege the past (tradition), present (agility), or future (vision)? + +These assumptions are rarely articulated. They surface only when violated -- when a new hire from a different culture does something that provokes an emotional reaction disproportionate to the action itself. That disproportionate reaction is the clearest signal that a basic assumption has been touched. + +### How the Layers Interact + +Change flows downward with great difficulty. A founder can redesign the office (Layer 1) overnight. Rewriting the values statement (Layer 2) takes a quarterly offsite. Shifting basic assumptions (Layer 3) requires years of consistent leadership behaviour, critical incidents handled visibly, and patient reinforcement. + +Conversely, diagnosis flows upward. To understand Layer 3, observe the patterns in Layer 1 and the contradictions between Layer 1 and Layer 2. The gap between artifacts and espoused values is the most reliable indicator of what the organisation actually believes. + +--- + +## Prompts + +**Prompt 1 -- Culture Audit:** +> Conduct a three-level culture audit for my company using Schein's framework. At the Artifacts level, I will describe our office setup, communication norms, meeting practices, and visible rituals. At the Espoused Values level, analyse our stated mission, values, and strategic principles. Then help me identify the Basic Underlying Assumptions by probing for gaps between what we say and what we do. Company context: [describe company stage, size, industry, and any recent cultural tensions]. + +**Prompt 2 -- Misalignment Diagnosis:** +> I suspect a gap between our espoused values and our actual organisational behaviour. Our stated values include [list values]. Recent incidents suggesting misalignment include [describe incidents]. Using Schein's model, help me diagnose which basic underlying assumptions are driving the contradictory behaviour, and propose interventions at each of the three levels. + +**Prompt 3 -- Culture Integration for M&A:** +> We are acquiring [describe target company]. Using Schein's three levels of organisational culture, help me map the cultural differences between our two organisations. For each level (artifacts, espoused values, basic assumptions), identify potential collision points and recommend an integration strategy that addresses each layer explicitly. + +**Prompt 4 -- Founder Culture Imprint:** +> As a founder at [stage], I recognise that my personal behaviours are imprinting onto the company culture. Using Schein's framework, help me audit which of my assumptions, habits, and decisions are becoming embedded as basic underlying assumptions. Identify which imprints are serving the company well and which may become liabilities at scale. + +--- + +## Use Cases + +**Series A SaaS Company Experiencing Growing Pains** +A 45-person B2B SaaS startup has doubled headcount in eight months. The founders notice that new hires "don't get the culture" -- they schedule unnecessary meetings, escalate decisions that should be made autonomously, and default to formal communication. A Schein analysis reveals that the company's basic assumption -- that competent adults make decisions without permission -- was never articulated; it was transmitted osmotically when the team was fifteen people. The fix operates at all three layers: codify the assumption into explicit values (Layer 2), redesign onboarding rituals to demonstrate autonomous decision-making (Layer 1), and have leadership visibly reinforce the assumption by publicly celebrating independent judgment (Layer 3 maintenance). + +**Growth-Stage Fintech After a Compliance Crisis** +A payments company with 200 employees suffers a regulatory penalty. Leadership declares a "compliance-first culture" and introduces new processes, reporting lines, and training (Layer 1 and Layer 2 changes). Six months later, the same risk-taking behaviours persist. Schein's framework reveals that the basic assumption -- "move fast, regulators are slow" -- was forged during the company's scrappy early days and reinforced by the promotion of individuals who embodied it. Surface-level changes cannot override Layer 3 assumptions. The intervention requires replacing key role models, restructuring incentives, and having the CEO publicly acknowledge past assumptions that no longer serve the company. + +**Pre-IPO Enterprise Company Merging Two Engineering Cultures** +Following an acquisition, two engineering teams with fundamentally different assumptions about quality (one ships fast and iterates; the other ships only when perfect) must integrate. Artifacts conflict immediately: different code review practices, different deployment cadences, different definitions of "done." Mapping each team's three layers reveals that the conflict is not about process -- it is about basic assumptions regarding the nature of professional excellence. Resolution requires surfacing both assumptions explicitly, negotiating a shared assumption appropriate to the combined entity, and rebuilding processes and rituals from that new foundation. + +--- + +## Anti-Patterns + +1. **Redecorating the Iceberg Tip.** Installing ping-pong tables, rewriting the mission statement, or launching a "culture committee" without addressing underlying assumptions. These initiatives generate cynicism when employees observe that actual behaviour remains unchanged. Artifacts-only interventions are the most common and most futile form of culture work. + +2. **Assuming Culture Is What the Founder Says It Is.** Founders often conflate their *intended* culture with the *actual* culture. Schein's framework demands empirical observation, not aspiration. The culture is what people do when no one is watching, not what the deck says. + +3. **Treating Culture as Monolithic.** Large organisations contain subcultures -- engineering, sales, operations -- each with distinct assumptions. Applying a single cultural analysis to the entire company produces a fiction. Map subcultures independently, then identify where they align and where they collide. + +4. **Skipping Layer 3 in Due Diligence.** M&A due diligence routinely examines financials, technology, and talent. It almost never examines basic assumptions. The result: post-merger integration failures that no amount of process harmonisation can fix, because the two organisations hold incompatible beliefs about how work should be done. + +5. **Expecting Speed.** Layer 3 assumptions take years to form and years to change. Leaders who announce a "culture transformation" with a six-month timeline are confusing artifacts with assumptions. Genuine culture change is measured in leadership generations, not quarters. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder imprint audit | Culture is being formed now, largely from the founder's unconscious assumptions. This is the highest-leverage moment to be intentional. | +| Growth | Articulation and codification | As headcount exceeds Dunbar-adjacent numbers (~50-150), osmotic culture transmission fails. Assumptions must become explicit values, and values must become visible artifacts. | +| Scale | Subculture management | Multiple teams, geographies, and functions develop distinct subcultures. The task shifts from building culture to managing cultural coherence across diverse groups. | + +At early traction, the primary risk is accidental culture -- the founder's unexamined habits becoming organisational doctrine. At growth, the risk is dilution -- rapid hiring overwhelming the cultural carriers. At scale, the risk is fragmentation -- subcultures diverging until the organisation loses coherence. + +--- + +## Output Template + +```markdown +# Organisational Culture Audit: [Company Name] + +## Layer 1: Artifacts (Observable) +- **Physical environment:** [Describe workspace, layout, remote/hybrid setup] +- **Communication norms:** [Tools, formality, response time expectations] +- **Rituals and ceremonies:** [All-hands, retrospectives, celebrations] +- **Symbols and stories:** [Origin myths, hero narratives, cautionary tales] +- **Decision-making patterns:** [Who decides, how fast, with what process] + +## Layer 2: Espoused Values +- **Official values:** [As stated on website/internal docs] +- **Strategic principles:** [As communicated by leadership] +- **Alignment assessment:** [Where behaviour matches values / where it diverges] + +## Layer 3: Basic Underlying Assumptions (Inferred) +- **Relationship to environment:** [Control vs. adapt] +- **Nature of truth:** [Data vs. authority vs. debate] +- **Human nature assumption:** [Trust vs. verify] +- **Relationship orientation:** [Hierarchy vs. egalitarian] +- **Time orientation:** [Past / present / future] + +## Gap Analysis +| Espoused Value | Observed Behaviour | Inferred Assumption | Gap Severity | +|----------------|-------------------|---------------------|--------------| +| [Value] | [What actually happens] | [What this reveals] | High/Med/Low | + +## Recommended Interventions +### Layer 1 (Quick wins): +- [Artifact changes] +### Layer 2 (Medium-term): +- [Values clarification / realignment] +### Layer 3 (Long-term): +- [Assumption-level work required] + +## Risk Assessment +[Key cultural risks if no action is taken] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Team development dynamics operate within the cultural container Schein describes; understanding both reveals why some teams thrive and others stall. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- A feedback culture is an artifact sustained by espoused values, which only works when basic assumptions support psychological safety. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework addresses the Layer 3 assumption about whether interpersonal risk-taking is safe; culture change initiatives fail when this assumption remains hostile. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- Kotter's eight steps provide the process methodology for altering culture; Schein's three layers explain why each step is necessary and where resistance originates. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Translates Schein's organizational-level theory into team-level practice, helping leaders build and sustain culture within their immediate sphere of influence. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- Culture transformation is the deepest form of organizational change; this skill addresses the leadership behaviors required to shift Layer 3 assumptions over time. diff --git a/plugins/foreman/skills/persuasion-and-influence/SKILL.md b/plugins/foreman/skills/persuasion-and-influence/SKILL.md deleted file mode 120000 index fdb3dc6..0000000 --- a/plugins/foreman/skills/persuasion-and-influence/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/persuasion-and-influence.md \ No newline at end of file diff --git a/plugins/foreman/skills/persuasion-and-influence/SKILL.md b/plugins/foreman/skills/persuasion-and-influence/SKILL.md new file mode 100644 index 0000000..427598f --- /dev/null +++ b/plugins/foreman/skills/persuasion-and-influence/SKILL.md @@ -0,0 +1,180 @@ +--- +name: "persuasion-and-influence" +description: "Equips leaders with daily micro-influence tactics -- reading emotional temperature in meetings, deploying peer power, establishing authority organically, using consistency commitments, and knowing when to compromise. Use when preparing for a difficult one-on-one, navigating a meeting where buy-in is needed, responding to an ultimatum, auditing informal influence networks, or needing to persuade without positional authority. Complements the theoretical Cialdini and Fisher/Ury frameworks with practical, moment-to-moment application." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - influence + - persuasion + - meetings + - negotiation + - micro-tactics + - reading-the-room + - compromise +related_skills: + - cialdini-influence + - win-win-negotiation + - carnegie-win-friends + - trust-equation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Persuasion and Influence in Practice + +INVISIBLE FORCE. The leader who wins arguments they never appear to have is not manipulative -- they are observant. They notice that the CFO crosses her arms when numbers are presented without context. They register that the head of engineering responds to peer endorsement more readily than to executive mandate. They sense when a room's emotional temperature has shifted from receptive to defensive, and they adjust -- not their position, but their delivery -- in the space between two sentences. This is not the psychology of persuasion as academic taxonomy. This is persuasion as a daily leadership practice: the granular, often invisible work of moving people toward decisions they would have reached themselves, given enough time and the right information. + +The theoretical architecture of influence -- Cialdini's seven principles, Fisher and Ury's principled negotiation -- exists elsewhere in this system. What follows is the applied craft: how influence actually operates in the hallway conversation, the budget meeting, the one-on-one where resistance is palpable but unexpressed. + +--- + +## The Framework + +Daily influence operates through five practical domains. Each represents a recurring leadership situation where micro-tactics produce disproportionate results. + +### Domain 1: Mapping Your Influence Network + +Influence is not a function of title. Maxim Sytch's research demonstrates that informal power -- the actual ability to get things done -- depends on a network of relationships that may bear little resemblance to the org chart. The diagnostic is straightforward: + +1. List the ten people you most depend on to accomplish your work. +2. For each, identify what you uniquely offer them (career advice, emotional support, stakeholder access, technical expertise). +3. Flag imbalances: do they help you more than you help them? Are they clustered in one business unit? +4. Identify gaps: whose cooperation do you need but lack a relationship with? + +Leaders who complete this audit often discover that their influence network is narrower, more lopsided, and more fragile than they assumed. The corrective is deliberate investment -- not transactional favours, but genuine contributions across a broader organisational footprint. + +### Domain 2: Reading the Room + +Jay Conger's research on persuasion reveals a capability that separates effective persuaders from ineffective ones: accurate emotional calibration. Great persuaders sense their audience's receptivity and match their delivery to it. Sometimes that requires force. Sometimes a whisper suffices. The diagnostic question is not "what do I want to say?" but "what is this room capable of hearing right now?" + +**Practical signals to monitor:** + +| Signal | Interpretation | Adjustment | +|--------|---------------|------------| +| Arms crossed, minimal eye contact | Defensive posture; the audience feels threatened | Lower intensity; acknowledge concerns before advancing position | +| Rapid nodding, forward lean | Engaged but potentially rushing to agree without processing | Slow down; ask probing questions to ensure genuine buy-in | +| Side conversations emerging | Attention has fractured; the argument is losing relevance | Pause; reconnect the discussion to the audience's specific concerns | +| One person dominates response | Group dynamics have shifted to a single voice | Redirect: "I'd like to hear other perspectives before we continue" | +| Silence after a proposal | Processing, not necessarily disagreement | Wait. Do not fill the silence with more arguments. | + +The last point deserves emphasis. Most leaders interpret silence as resistance and respond by talking more. Skilled influencers interpret silence as processing and respond by waiting. + +### Domain 3: Micro-Influence in One-on-One Settings + +The persuasion principles that operate at scale -- social proof, scarcity -- are less relevant in a private conversation between two people. What matters in one-on-one influence: + +**Similarity and genuine connection.** Find authentic common ground early. Shared interests, shared frustrations, shared professional experiences -- any genuine bond creates receptivity. The emphasis is on genuine. Manufactured similarity is detectable and corrosive. + +**Organic authority establishment.** Mentioning relevant experience should feel like context, not credentials. "When we faced a similar situation at my previous company" establishes authority without the awkwardness of reciting a CV. Weave expertise into the conversation; never announce it. + +**Active, public, voluntary commitment.** When seeking buy-in, engineer commitments that are spoken aloud (active), made in front of at least one other person (public), and freely chosen (voluntary). An email confirming a colleague's commitment to a timeline is more binding than a verbal nod in a hallway. A commitment made in a team standup is more binding still. + +### Domain 4: Navigating Ultimatums and Resistance + +When a negotiation stalls or an ultimatum lands, the instinct is to either capitulate or escalate. Research from Ma, Yang, and Savani suggests a third path: adopt a choice mindset. Before any negotiation, list every option available to both parties -- not just the obvious ones. If salary is fixed, what about vacation days, remote work, project selection, reporting structure, professional development budget? When an ultimatum narrows the conversation to a single variable, the choice mindset re-expands it. + +Effective persuaders also enter every influence situation with compromises already prepared. Conger's research is direct: colleagues respond more positively to a persuader who visibly incorporates their input. Flexibility signals trustworthiness. Rigidity signals that the conversation is a performance, not a collaboration. + +### Domain 5: Relationship as the Foundation + +Influence is not a technique applied to a relationship. It is a property of the relationship itself. Linda Hill and Kent Lineback's research is unequivocal: every day, every interaction, every word is examined by the people a leader seeks to influence. They are asking a single question -- "Can I trust this person?" -- and the answer determines the upper limit of the leader's influence. + +This means that daily influence is cumulative, not episodic. The leader who is transparent about reasoning, consistent in follow-through, and genuinely curious about others' perspectives builds an influence reservoir that makes any single persuasion moment easier. The leader who is erratic, opaque, or self-serving finds that no technique compensates for the deficit. + +--- + +## Prompts + +**Prompt 1 -- Influence Network Audit:** +> Map my influence network. Here are the ten people I most depend on to get work done: [list names and roles]. For each, I've noted what I offer them and what they offer me: [describe]. Identify imbalances, gaps, and risks in this network. Then recommend three specific actions to strengthen it -- prioritising relationships where my influence deficit is highest. + +**Prompt 2 -- Meeting Influence Strategy:** +> I have a meeting tomorrow where I need to persuade [describe audience] to support [describe proposal]. The likely resistance points are: [describe]. Design a meeting influence strategy: how should I open, what emotional temperature should I aim for, how should I handle the likely objections, and what compromises should I have prepared? Include specific language I can use. + +**Prompt 3 -- One-on-One Persuasion Preparation:** +> I need to persuade [person, role] to [desired outcome] in a one-on-one conversation. Here is what I know about their priorities: [describe]. Here is our relationship history: [describe]. Design an approach using similarity, organic authority, and commitment engineering. Include specific talking points and the commitment mechanism I should aim for by the end of the conversation. + +**Prompt 4 -- Ultimatum Response:** +> I have received an ultimatum in a negotiation: [describe the ultimatum and context]. Before I respond, help me expand the option space. List every variable that could be in play beyond the one the ultimatum focuses on. Then design a response that neither capitulates nor escalates, using the choice mindset framework. + +--- + +## Use Cases + +**Growth-Stage CTO Seeking Engineering Budget Approval** +A CTO needs the CFO to approve a significant infrastructure investment. The CFO has rejected similar requests twice, citing ROI uncertainty. Rather than presenting the same data louder, the CTO conducts an influence network audit and discovers that the VP of Sales -- who has a strong relationship with the CFO -- is frustrated by system downtime affecting customer demos. The CTO enlists the VP of Sales to describe the revenue impact at the next leadership meeting (peer power). In the meeting itself, the CTO reads the room: the CFO's body language shifts from guarded to engaged when the VP of Sales speaks. The CTO adjusts, asking the CFO what ROI threshold would make the investment acceptable (commitment via voluntary criteria-setting). The budget is approved within two weeks. + +**Scale-Stage VP Navigating a Cross-Functional Deadlock** +Two department heads have been unable to agree on a shared platform migration timeline. The VP responsible for both departments enters a joint meeting with compromises pre-prepared: two of three proposed concessions address each department's stated concerns. By opening with "I've incorporated both teams' feedback into three options -- and I want to hear what I've missed," the VP signals flexibility. The department heads, whose resistance was partly driven by feeling unheard, shift from positional bargaining to collaborative problem-solving. The organic authority move -- "When we ran a similar migration at [previous company], we found that..." -- provides context without dictation. The meeting concludes with a publicly stated commitment from both leads, documented in a follow-up email. + +--- + +## Anti-Patterns + +1. **Technique Without Relationship.** Deploying influence tactics on a relationship with no trust foundation. If the people you seek to influence do not believe you have their interests in mind, no amount of tactical sophistication compensates. Build the relationship first; the techniques amplify what already exists. + +2. **Reading the Room and Ignoring What You Read.** Many leaders are excellent at sensing emotional shifts in a meeting and then proceed to deliver their pre-planned argument anyway. Reading the room is worthless without the willingness to adapt in real time. + +3. **Confusing Compromise with Weakness.** Leaders who view any concession as a loss of face. Conger's research is clear: prepared compromises increase influence. The leader who enters a persuasion moment with nothing to give signals that the conversation is a monologue, not a dialogue. + +4. **The Similarity Trap.** Spending influence capital only on people who are already aligned. An influence network composed exclusively of allies is a mutual admiration society, not a source of organisational power. The most valuable influence relationships are with people who do not naturally agree with you. + +5. **Over-Engineering Commitment.** Attempting to engineer public, active, voluntary commitments in every conversation. Sometimes the appropriate influence move is patience -- allowing people to arrive at commitment on their own schedule. Forced commitments generate compliance, not conviction. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder-as-sole-persuader | The founder is the company's primary influence mechanism. Every customer conversation, every hire, every investor meeting depends on the founder's personal persuasion. Building an influence network is less relevant; mastering one-on-one persuasion is critical. | +| Growth | Distributed influence | The leader can no longer personally persuade every stakeholder. The priority shifts to building an influence network, enlisting peer power, and engineering commitment systems that operate without the leader in the room. | +| Scale | Institutional influence | At scale, influence becomes cultural. The leader's task is to model the influence behaviours they want to see throughout the organisation -- transparency, compromise, room-reading -- so that persuasion capacity is distributed, not centralised. | + +--- + +## Output Template + +```markdown +# Influence Strategy: [Context] + +## Influence Network Assessment +| Person | What I Offer | What They Offer | Balance | Action Needed | +|--------|-------------|-----------------|---------|---------------| +| [Name] | [value] | [value] | [+/-/=] | [specific step] | + +## Room-Reading Plan +- Expected emotional temperature: [description] +- Adjustment triggers: [what signals will prompt a shift in approach] +- Pre-prepared compromises: [list 2-3 concessions] + +## Influence Sequence +1. Opening move: [specific language and approach] +2. Authority establishment: [how expertise will be woven in] +3. Peer power: [who will be enlisted and how] +4. Commitment mechanism: [what active, public, voluntary commitment to aim for] +5. Fallback: [if primary approach fails, what is the alternative] + +## Post-Interaction Review +- What worked: [observation] +- What to adjust: [observation] +- Relationship investment needed: [next step] +``` + +--- + +## Related Skills + +- **[Cialdini's Principles of Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Provides the theoretical architecture (seven principles) that this skill applies to daily micro-moments; read Cialdini for the science, this skill for the practice. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation framework complements the ultimatum response and compromise strategies covered here. +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's interpersonal principles underpin the similarity and genuine connection tactics central to one-on-one influence. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- The trust equation diagnoses whether the relational foundation required for influence is intact; without trust, technique is futile. +- **[Influencing and Persuading](../../content/skills/people/influencing-and-persuading.md)** -- Provides the complementary people-focused influence techniques including Socratic persuasion and listening-based approaches drawn from different source material. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Narrative is the most potent vehicle for influence; stories deploy social proof and liking more effectively than abstract argument. diff --git a/plugins/foreman/skills/plain-language-and-flow/SKILL.md b/plugins/foreman/skills/plain-language-and-flow/SKILL.md deleted file mode 120000 index 918c058..0000000 --- a/plugins/foreman/skills/plain-language-and-flow/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/plain-language-and-flow.md \ No newline at end of file diff --git a/plugins/foreman/skills/plain-language-and-flow/SKILL.md b/plugins/foreman/skills/plain-language-and-flow/SKILL.md new file mode 100644 index 0000000..dc336d3 --- /dev/null +++ b/plugins/foreman/skills/plain-language-and-flow/SKILL.md @@ -0,0 +1,247 @@ +--- +name: "plain-language-and-flow" +description: "Teaches how to eliminate corporate jargon (bizspeak), use chronological ordering for factual accounts, and create smooth document flow through transitional words, signposting, and paragraph continuity. Features a bizspeak blacklist, before/after translations of corporate prose, and a taxonomy of transitional phrases. Use when writing sounds too corporate, when documents lack narrative flow, when readers report confusion about the sequence of events, or when establishing plain-language standards for an organisation." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - plain-language + - jargon + - transitions + - flow + - chronology + - readability + - business-writing +related_skills: + - clarity-and-concision + - revising-and-editing + - writing-with-purpose + - business-writing-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Plain Language and Flow + +Consider this paragraph from an actual corporate communication: "It's mission-critical to be plain-spoken, whether you're trying to be best-of-breed at outside-the-box thinking or simply incentivizing colleagues to achieve a paradigm shift in core-performance value-adds. Leading-edge leveraging of your plain-English skill set will ensure that your actionable items synergize future-proof assets with your global-knowledge repository." + +That passage says absolutely nothing. Strip away the jargon and what remains is a void -- no idea, no argument, no information. The words exist to *sound* like communication while avoiding the labour of actual thought. This is bizspeak: the corporate dialect that substitutes cliches for meaning, boilerplate for analysis, and verbal padding for substance. It is the lingua franca of organisations that have confused formality with competence. + +The antidote is not simplification. It is *translation* -- converting corporate noise into human language, imposing chronological order on jumbled narratives, and using transitional phrases to guide readers through the argument. Plain language is not dumbed-down language. It is language that has been thought through. + +--- + +## The Framework + +### Part 1: The Bizspeak Autopsy + +Corporate jargon persists for three reasons. Some writers use it to signal belonging -- to sound "in the know." Others have been taught that good writing is formal writing, so they stiffen when they pick up a keyboard. Still others use jargon deliberately to obscure what they are actually doing, or to disguise the fact that they are not sure what they are doing. + +Whatever the motivation, the effect on the reader is consistent: bizspeak suggests that the writer is on autopilot, thoughtlessly deploying boilerplate rather than engaging with the material. + +**The Bizspeak Translation Table:** + +| NOT THIS | BUT THIS | +|----------|----------| +| at your earliest convenience | as soon as you can | +| in light of the fact that | because | +| we are in receipt of | we've received | +| as per our telephone conversation on today's date | as we discussed this morning | +| Pursuant to your instructions, I met with Roger Smith today regarding the above-mentioned. | As you asked, I met with Roger Smith today. | +| Please be advised that the deadline for the abovementioned competition is Monday, April 2, 2012. | The deadline is April 2, 2012. | +| Thank you for your courtesy and cooperation regarding this matter. | Thank you. | + +Each translation removes verbal scaffolding while preserving -- and often improving -- the meaning. The plain versions take less time to write, less time to read, and less time to act on. + +**The Bizspeak Blacklist (a selection):** + +Actionable (apart from legal contexts), as per, bandwidth (outside electronics), bring our A game, core competency, drill down, going forward, hit the ground running, impact (as verb), incentivize, leverage (as verb), mission-critical, net-net, on the same page, operationalize, paradigm shift, push the envelope, repurpose, rightsized, scalable, seamless integration, synergize, think outside the box, utilize, value-added, win-win. + +These terms have become voguish through overuse. Each one once carried meaning; repetition has drained it away. When a writer reaches for "synergize," the question to ask is: what specifically are these elements doing together, and can that action be described in plain English? + +### The Buffett Translation + +Warren Buffett rewrote a passage from a financial-services prospectus to demonstrate the transformation. The original: 136 words, all passive voice, average sentence length 27.2 words, Flesch Reading Ease score 8.2 (virtually unreadable). Buffett's revision: 74 words, no passive voice, average sentence length 14.8 words, Flesch Reading Ease score 60.1. + +The revision did not lose information. It gained clarity. Increasing readability is not "dumbing it down" -- it is cleaning it up. + +### The Readability Science + +Buffett's instinct is backed by a century of measurement. Readability -- the quantifiable ease or difficulty of reading a text -- was first formalised by the United States military in 1917, when the country needed to assess whether soldiers could read well enough to perform their duties. The metrics have grown more sophisticated, but the core insight remains: shorter words, more common words, and shorter sentences produce text that more people read, understand, and act upon. + +*Writing for Busy Readers* marshals the evidence. Readability scores are typically expressed as either a numerical index or the school grade level a reader would need to have completed to comprehend the text. The *New York Times* requires an eleventh-grade reading level. Most nursery rhymes sit at fourth grade. Around half of American adults read at an eighth-grade level or below, and roughly 20% read English as a second language. Writing above eighth-grade level does not signal sophistication -- it signals exclusion. + +**Cognitive load is the mechanism.** Humans evolved to speak and listen long before developing the capacity to read. Spoken language uses short, incomplete sentences; our brains process these structures with minimal effort. Written prose that departs from this pattern -- long sentences, subordinate clauses, unfamiliar vocabulary -- taxes working memory. Eye-tracking studies show that readers pause at end-of-sentence periods to integrate meaning. Longer sentences force readers to hold more information in memory before that integration can occur, increasing the probability of distraction, re-reading, or abandonment. + +**The data on sentence length is unambiguous.** Average sentence length in published novels has dropped from 27 words per sentence in 1800 to 10 words per sentence in 2000. Presidential inaugural addresses show the same trajectory: George Washington's opening five sentences in 1789 averaged 64 words each; Joe Biden's in 2021 averaged 7. The trend reflects not declining intelligence but increasing respect for the reader's cognitive constraints. + +**Familiar words outperform sophisticated vocabulary.** When two words are synonyms, the shorter and more common one is almost always more readable. Google's Ngram Viewer confirms that "next" is used more frequently than "subsequent," "get" more than "acquire," "show" more than "demonstrate." Research published under the title "Consequences of Erudite Vernacular Utilized Irrespective of Necessity" found that college students rated writers who used complex language as *less* intelligent than those who used simpler language. The paper won an Ig Nobel Prize -- and its finding has held up. In a separate study, corporations with less readable ethics codes were rated by readers as less moral and less trustworthy. + +The implication for business writers is straightforward: readability is not a matter of preference but of reach. A document written at a college reading level excludes a measurable portion of its audience. The same document, revised to eighth-grade level using shorter sentences and more common words, excludes almost no one -- and is read more quickly even by those fully capable of parsing the original. + +### Part 2: Chronological Ordering + +Stories are inherently chronological. One thing happens, then another, then another. This structure works not only in fiction but in any factual business account -- project updates, status reports, incident descriptions, performance evaluations. + +Writers who skip chronological ordering produce stream-of-consciousness messages that confuse readers. The facts are present, but the reader cannot reconstruct the sequence. The fix: before drafting any factual account, create a chronology of relevant events. + +**Before chronological ordering:** +> "It was hard making headway with Jim Martinez, but finally we're looking at a demonstration of what our software can do by mid-May, as I established in my first telephone conference with Jim last Monday at 9:00 a.m. He was out Wednesday and Thursday, but on Friday he told me that we'd need a sample app. But prior to that, Magnabilify requires an NDA. Tuesday's meeting should clarify things." + +**After chronological ordering:** +> "Last week you asked me to approach Magnabilify Corporation to see whether they might have any interest in our customising some security applications for their computer systems. I finally got through to Jim Martinez, corporate vice president in charge of software, and we have planned a face-to-face meeting at his office next Tuesday. The next steps will be to enter into a nondisclosure agreement, to develop a sample application in less than two weeks, and to schedule a demonstration shortly after." + +The first version forces the reader to untangle the timeline. The second version tells a story that any reader can follow on the first pass. + +### Part 3: Continuity and Transitions + +Smooth writing consists of a sequence of well-joined sentences and paragraphs -- not a mere collection of them. The connections between ideas, executed through transitional words and phrases, are the infrastructure of readable prose. When they work, readers do not even notice them. When they are absent, readers stumble. + +**The Taxonomy of Transitions:** + +| Function | Transitional Words | +|----------|-------------------| +| **Time sequence** | then, at that point, afterward, as soon as, before, after, first, initially, meanwhile, later, next, now, finally | +| **Add a point** | and, or, further, also, in fact, moreover, not only... but also | +| **Underscore a point** | above all, after all, and so, chiefly, equally important, more so, indeed | +| **Concede a point** | although, and yet, admittedly, at the same time, certainly, even though, granted, no doubt, still, whereas, yet, while | +| **Return to a point** | even so, nevertheless, nonetheless, still | +| **Give an example** | for example, for instance, in particular | +| **Provide a reason** | because, hence, thus, for, it follows, since, so, then, therefore | +| **Set up a contrast** | but, yet, and yet, conversely, despite, by contrast, instead, on the other hand, still, while | +| **Set up a conclusion** | so, as a result, finally, in conclusion, in short, in sum, therefore, thus, to sum up | + +Transitions are not decorative. They are navigational. Each one tells the reader the relationship between the current idea and the one that preceded it -- whether the writer is adding, contrasting, conceding, concluding, or illustrating. + +### Signposting with Subheads + +No matter how smooth the transitions between sentences and paragraphs, time-pressed readers will zone out when confronted with a solid wall of text. Subheadings serve as signposts -- they break the document into navigable sections and allow readers to find the information they need. + +Effective subheads are: +- **Informative, not generic.** "Background" tells the reader nothing. "Why Our Current Process Takes Four Weeks" tells them exactly what they will learn. +- **Consistent in syntax.** If one subhead is a directive ("Use LinkedIn to Get Feedback"), all subheads should be directives. Parallel structure reinforces logical and rhetorical cohesion. +- **Scannable.** A reader who reads only the subheads should get the gist of the entire document. + +--- + +## Prompts + +**Prompt 1 -- Bizspeak Translation:** +> Here is a business document: [paste text]. Identify every instance of corporate jargon, bizspeak, and boilerplate phrasing. For each, provide a plain-English translation. Then rewrite the entire document in plain language, preserving all substantive content. Show a side-by-side comparison of the original and revised versions with word counts. + +**Prompt 2 -- Chronological Reordering:** +> Here is a factual account I need to communicate: [paste text or describe events]. The events are currently described out of order. Create a chronology of relevant events (a simple table with dates/timeframes and what happened). Then rewrite the account in chronological order so that a reader with no prior context can follow the narrative on the first read. + +**Prompt 3 -- Transition Audit:** +> Here is a document: [paste text]. Analyse the transitions between paragraphs. For each paragraph boundary, identify: (1) whether a transition exists, (2) what function it serves (adding, contrasting, concluding, etc.), (3) whether it is effective. Where transitions are missing or weak, suggest specific transitional words or phrases that would improve flow. Then provide the revised document with improved transitions. + +**Prompt 4 -- Subhead Architecture:** +> Here is a document of [X] words: [paste text]. It currently has [no subheads / weak subheads]. Design a subhead architecture that: (1) breaks the document into logical sections, (2) uses informative rather than generic labels, (3) maintains parallel syntax across all subheads, (4) allows a reader to grasp the document's argument by reading only the subheads. Provide the revised document with subheads inserted. + +--- + +## Use Cases + +**Validation-Stage Startup Translating a Technical White Paper for Investors** + +A deep-tech startup's white paper is dense with domain jargon that resonates with engineers but alienates investors. The original opening: "Our platform operationalizes a novel approach to leveraging graph-based neural architectures for scalable, mission-critical anomaly detection in enterprise-grade distributed systems." After the bizspeak translation: "Our software detects problems in large computer networks before they cause outages. It uses a type of artificial intelligence called graph neural networks -- the same technology behind social media recommendation engines, adapted for IT infrastructure monitoring." The second version communicates the same technology to a broader audience. The investor can now decide whether to keep reading. + +**Growth-Stage Company Fixing Disorganised Status Reports** + +A project manager's weekly status reports read like stream-of-consciousness: events from different weeks are jumbled, outcomes are mentioned before their causes, and the reader cannot tell what happened this week versus last month. Applying the chronological ordering framework: the PM creates a simple timeline before drafting each report -- last week's events, this week's events, next week's planned actions. The report structure becomes: "Where we were / What happened / Where we're going." Reader comprehension (measured by the number of follow-up questions from the VP) drops from an average of five per report to one. + +**Scale-Stage Company Establishing a Plain-Language Style Guide** + +A 400-person financial services firm discovers that customer communications score below 30 on the Flesch Reading Ease scale -- roughly equivalent to the *Harvard Law Review*, and thoroughly inappropriate for retail clients. The firm creates a plain-language standard: all customer-facing documents must score above 50 (roughly *Time* magazine level), all subheads must be informative rather than generic, and the bizspeak blacklist is circulated to every department. Within six months, customer complaint calls related to "confusing correspondence" drop by 35%. + +--- + +## Anti-Patterns + +1. **Replacing Jargon with Different Jargon.** Translating "synergize core competencies" into "align strategic capabilities" is not plain language -- it is a lateral move within the same dialect. Plain language means describing what is actually happening in words a non-specialist would use. + +2. **Eliminating All Technical Terms.** Plain language does not mean banning technical vocabulary. When writing for specialists, precise technical terms are more efficient than lengthy plain-language circumlocutions. The test is audience: will the reader know this term? If yes, use it. If no, define it or replace it. + +3. **Over-Transitioning.** Cramming a transitional word into every sentence makes prose feel mechanical and patronising. The best transitions are almost subliminal -- readers follow the logic without noticing the connective tissue. Use transitions where the relationship between ideas might be ambiguous; omit them where the connection is self-evident. + +4. **Using Subheads as Decoration.** Subheads that do not accurately describe the content below them are worse than no subheads at all. "Miscellaneous" is not a subhead -- it is an admission that the writer could not be bothered to organise the section. + +5. **Chronological Ordering When It Does Not Apply.** Not all business documents benefit from chronological structure. Recommendations, analyses, and persuasive arguments are often better organised by importance or logical dependency. Chronology serves factual accounts -- status reports, incident descriptions, project updates. Misapplying it to analytical documents produces a confusing "and then... and then..." narrative. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Jargon-free pitching | Early-stage founders often mimic the jargon of their target industry to seem credible. The opposite is more effective: plain language signals clarity of thought, which investors value more than vocabulary. | +| Validation | Evidence narration | Customer discovery stories, pilot results, and market validation are factual accounts that benefit from chronological ordering. Plain language ensures that non-technical stakeholders can evaluate the evidence. | +| Early Traction | Scaling communication clarity | As the team grows, internal communications must be accessible to new hires who lack the company's institutional jargon. Plain language accelerates onboarding. | +| Growth | Cross-functional readability | Marketing writes for customers, engineering writes for product, finance writes for investors -- and sometimes they must read each other's documents. Plain language is the common dialect that makes cross-functional communication possible. | +| Scale | Institutional plain-language standards | The bizspeak blacklist becomes an organisational style guide. Readability scores become acceptance criteria for external communications. New employees are trained on plain-language principles during onboarding. | + +--- + +## Output Template + +```markdown +# Plain Language and Flow Audit: [Document Title] + +## Bizspeak Inventory +| Jargon Found | Location | Plain Translation | +|-------------|----------|-------------------| +| [term/phrase] | [paragraph N] | [plain equivalent] | +| [term/phrase] | [paragraph N] | [plain equivalent] | + +## Readability Metrics +- **Flesch Reading Ease (original):** [X] +- **Flesch Reading Ease (revised):** [Y] +- **Average sentence length (original):** [X words] +- **Average sentence length (revised):** [Y words] +- **Passive voice percentage:** [X]% → [Y]% + +## Chronological Assessment +- **Document contains factual account?** [Yes/No] +- **Events presented in chronological order?** [Yes/No/Partially] +- **Chronology of relevant events:** + +| When | What Happened | +|------|---------------| +| [Date/period] | [Event] | +| [Date/period] | [Event] | + +## Transition Audit +| Paragraph Boundary | Transition Present? | Function | Effective? | Suggested Improvement | +|-------------------|--------------------|-----------|-----------|-----------------------| +| P1 → P2 | [Yes/No] | [Type] | [Yes/No] | [Suggestion] | +| P2 → P3 | [Yes/No] | [Type] | [Yes/No] | [Suggestion] | + +## Subhead Assessment +- **Current subheads informative?** [Yes/No] +- **Parallel syntax?** [Yes/No] +- **Scannable summary from subheads alone?** [Yes/No] +- **Recommended subhead architecture:** + 1. [Subhead 1] + 2. [Subhead 2] + 3. [Subhead 3] +``` + +--- + +## Related Skills + +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- Plain language eliminates jargon; concision eliminates waste. Together they produce prose that is both accessible and efficient. +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- The editing checklist's "Does one sentence glide into the next?" question operationalises the continuity principles taught here. +- **[Writing with Purpose](../../content/skills/writing/writing-with-purpose.md)** -- Purpose determines audience, and audience determines the appropriate level of plain language; writing for specialists allows more technical vocabulary while diverse audiences demand simpler expression. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- The cognitive science of how readers process text explains why plain language reduces cognitive load and increases comprehension at a neurological level. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Leaders who write in plain language set the standard; those who write in bizspeak give implicit permission for everyone else to do the same. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Plain language creates the foundation; tone determines whether that accessible prose also engages the reader emotionally. diff --git a/plugins/foreman/skills/porters-five-forces/SKILL.md b/plugins/foreman/skills/porters-five-forces/SKILL.md deleted file mode 120000 index 1bdcb30..0000000 --- a/plugins/foreman/skills/porters-five-forces/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/porters-five-forces.md \ No newline at end of file diff --git a/plugins/foreman/skills/porters-five-forces/SKILL.md b/plugins/foreman/skills/porters-five-forces/SKILL.md new file mode 100644 index 0000000..8aeb03c --- /dev/null +++ b/plugins/foreman/skills/porters-five-forces/SKILL.md @@ -0,0 +1,222 @@ +--- +name: "porters-five-forces" +description: "Analyzes competitive industry dynamics using Porter's Five Forces + framework. Evaluates threat of new entrants, supplier power, buyer power, + substitution threats, and competitive rivalry. Use when assessing market entry + decisions, developing competitive strategy, evaluating industry + attractiveness, or analyzing pricing power." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - competitive-analysis + - industry-structure + - strategy + - market-entry + - profitability +related_skills: + - blue-ocean-strategy + - swot-pest-analysis + - art-of-war + - business-model-canvas + - scenario-planning +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Porter's Five Forces + +Most people use Porter's Five Forces wrong. They fill in the five boxes, label each force as "high," "medium," or "low," and conclude that they have performed strategic analysis. They have not. Michael Porter's framework, introduced in his 1979 *Harvard Business Review* article "How Competitive Forces Shape Strategy" and elaborated in *Competitive Strategy* (1980), is not a checklist. It is a theory of profitability -- an explanation of why some industries are structurally profitable and others are not, and why positioning within an industry matters more than operational excellence. The five forces determine the profit potential of an industry. Understanding them determines whether a startup is entering a gold mine or a tar pit. Misunderstanding them -- which is the norm -- produces strategies that fight industry structure rather than leveraging it. + +--- + +## The Framework + +### The Five Forces + +Porter's model identifies five competitive forces that collectively determine the intensity of competition and, therefore, the profit potential of any industry. + +``` + ┌───────────────────────┐ + │ THREAT OF NEW │ + │ ENTRANTS │ + └───────────┬───────────┘ + │ + ▼ +┌──────────────┐ ┌───────────────────────┐ ┌──────────────┐ +│ BARGAINING │───▶│ INDUSTRY RIVALRY │◀───│ BARGAINING │ +│ POWER OF │ │ (among existing │ │ POWER OF │ +│ SUPPLIERS │ │ competitors) │ │ BUYERS │ +└──────────────┘ └───────────┬───────────┘ └──────────────┘ + │ + ▼ + ┌───────────────────────┐ + │ THREAT OF │ + │ SUBSTITUTES │ + └───────────────────────┘ +``` + +### Force 1: Threat of New Entrants + +New entrants bring new capacity, new resources, and the desire to gain market share. The seriousness of the threat depends on barriers to entry: + +| Barrier | Description | Startup Implication | +|---------|-------------|---------------------| +| Economies of scale | Incumbents produce at lower per-unit cost | Niche focus can circumvent scale requirements | +| Capital requirements | Large upfront investment needed | SaaS and asset-light models reduce this barrier | +| Switching costs | Cost to customers of changing providers | Building switching costs early creates defensibility | +| Access to distribution | Incumbents control channels | Direct-to-customer and platform strategies bypass traditional distribution | +| Regulatory barriers | Licenses, certifications, compliance | Can be a moat if the startup achieves compliance first | +| Network effects | Value increases with user count | The most powerful barrier when achieved; nearly insurmountable | + +For startups: you are the new entrant. The barriers you overcome to enter are the same barriers that will protect you once inside -- if you build them. + +### Force 2: Bargaining Power of Suppliers + +Suppliers are powerful when they are concentrated, provide differentiated inputs, face low switching costs for their own business, or can credibly threaten forward integration. Powerful suppliers capture value by charging higher prices or reducing quality. + +For startups: key suppliers include cloud providers, payment processors, talent pools, and API providers. A startup dependent on a single API provider whose pricing can change unilaterally faces significant supplier power. Diversification, commoditization of inputs, and building proprietary alternatives are defensive strategies. + +### Force 3: Bargaining Power of Buyers + +Buyers are powerful when they are concentrated (few large customers), purchase large volumes, face low switching costs, or can credibly threaten backward integration (building the product themselves). Powerful buyers capture value by demanding lower prices or higher quality. + +For startups: customer concentration is the most common buyer power trap. A startup where one customer represents 40% of revenue has granted that customer enormous leverage. The strategic response is to diversify the customer base as early as possible and to create switching costs through integration depth, data lock-in, or workflow embedding. + +### Force 4: Threat of Substitutes + +A substitute is not a direct competitor -- it is a different product that serves the same need. The threat is highest when the substitute offers an attractive price-performance trade-off and when switching costs are low. + +For startups: the most dangerous substitute is often "doing nothing" or "doing it manually." A project management tool competes not just with other tools but with spreadsheets, email chains, and whiteboards. Understanding the true substitutes -- especially non-consumption -- prevents strategic myopia. + +### Force 5: Industry Rivalry + +Rivalry is intense when competitors are numerous and roughly equal in size, industry growth is slow, fixed costs are high, products are undifferentiated, and exit barriers prevent competitors from leaving. Intense rivalry drives down prices and profitability for all participants. + +For startups: entering a market with intense rivalry among well-funded incumbents is the most common cause of startup failure-by-competition. The five forces analysis should prevent this by revealing unattractive industry structures before capital is committed. + +### The Synthesis: Industry Attractiveness + +The five forces collectively produce an industry attractiveness assessment: + +- **Attractive industry**: High barriers to entry, weak supplier and buyer power, few substitutes, moderate rivalry. Incumbents earn above-average returns. +- **Unattractive industry**: Low barriers, powerful suppliers and buyers, many substitutes, intense rivalry. Even good companies earn below-average returns. + +Porter's deepest insight: company strategy should begin with industry selection. Competing brilliantly in a structurally unattractive industry produces mediocre returns. Competing adequately in a structurally attractive industry produces superior returns. Industry structure trumps execution. + +--- + +## Prompts + +**Prompt 1 -- Full Five Forces Analysis:** +> Conduct a Porter's Five Forces analysis of my industry. I compete in [describe industry/market segment]. For each force, assess the intensity (Weak/Moderate/Strong) and identify the specific factors driving that assessment. Then provide an overall industry attractiveness rating and its implications for my startup's strategy. Present the analysis as both a summary table and a detailed narrative for each force. + +**Prompt 2 -- Entry Barrier Assessment:** +> I am considering entering [describe market/industry]. Using Porter's framework, assess the barriers to entry I will face. For each barrier type (economies of scale, capital requirements, switching costs, distribution access, regulatory requirements, network effects, brand loyalty), rate the height of the barrier and my realistic ability to overcome it. Then assess: once I overcome these barriers, which ones will protect me from subsequent entrants? Identify the barriers I should actively build. + +**Prompt 3 -- Competitive Position Optimization:** +> Given this Five Forces analysis of my industry [paste or describe analysis], help me design a competitive position that exploits the structure rather than fighting it. Where are the pockets of profitability? Which customer segments face the least buyer power? Which supplier relationships can be restructured? What positioning would reduce our exposure to rivalry? Frame the output as a strategic positioning recommendation. + +**Prompt 4 -- Dynamic Forces Projection:** +> My industry's five forces are currently [describe current state]. Project how each force is likely to change over the next 3-5 years, considering these trends: [describe relevant technology, regulatory, demographic, or competitive trends]. Which forces are strengthening? Which are weakening? How should my strategy adapt to the evolving industry structure? Present as a current vs. future comparison for each force. + +**Prompt 5 -- Substitute Threat Deep Dive:** +> Analyze the substitute threats to my product/service. My offering is [describe]. Go beyond direct competitors and identify ALL substitutes -- including non-consumption, manual alternatives, and products from adjacent industries that serve the same underlying need. For each substitute, assess: price-performance relative to my offering, switching costs from the substitute, and the conditions under which customers would prefer the substitute. Rank substitutes by threat level. + +--- + +## Use Cases + +**Idea-Stage Founder Evaluating Two Market Opportunities** +A technical founder with expertise in computer vision must choose between building a quality inspection product for manufacturing (Market A) and a visual search product for e-commerce (Market B). The Five Forces analysis reveals that Market A has moderate barriers to entry (domain expertise required), weak buyer power (fragmented customer base of thousands of factories), few substitutes (manual inspection is costly and error-prone), and moderate rivalry (three incumbents, none dominant). Market B has low barriers (many CV APIs available), strong buyer power (a few large e-commerce platforms dominate demand), strong substitutes (text search is free and familiar), and intense rivalry (dozens of startups, several well-funded). The structural analysis clearly favors Market A, independent of the founder's personal preference. + +**Growth-Stage SaaS Company Experiencing Margin Pressure** +A $10M ARR vertical SaaS company faces declining margins despite growing revenue. The Five Forces analysis reveals the cause: buyer power has increased as three enterprise customers now represent 55% of revenue, and each is demanding volume discounts and custom features. Supplier power has also increased as the company's reliance on a single cloud provider and a single data vendor has deepened. The strategic response targets both forces: a customer diversification initiative to reduce concentration below 20% per customer, and a multi-cloud architecture initiative to restore supplier optionality. + +**Scale-Stage Company Evaluating Vertical Integration** +A 1,000-person company evaluates whether to build an in-house capability currently provided by a supplier. The Five Forces lens reframes this decision: the supplier has strong bargaining power (proprietary technology, few alternatives, high switching costs). Vertical integration would eliminate this force entirely. The analysis also reveals that the in-house capability could become a new revenue line -- the company could become a supplier to its own competitors, converting a cost center into a profit center while simultaneously neutralizing a competitive force. + +--- + +## Anti-Patterns + +1. **Using Five Forces as a static snapshot.** Industry structure evolves. Technology shifts, regulatory changes, and new entrants alter the balance of forces continuously. An analysis conducted once and never updated becomes a historical artifact rather than a strategic tool. The framework must be reapplied at least annually, and whenever a significant structural change occurs. + +2. **Confusing competitors with substitutes.** Direct competitors offer similar products. Substitutes serve the same need through different means. Mistaking one for the other leads to strategic myopia -- fighting feature wars with competitors while a substitute captures the market from an entirely different direction. + +3. **Treating all five forces as equally important.** In any given industry, one or two forces dominate the profitability equation. A rigorous analysis identifies which forces matter most and focuses strategic energy accordingly. Equal weighting across all five forces produces unfocused strategy. + +4. **Ignoring the force of complementors.** Porter's original model does not explicitly include complementary products and services, though later scholars (notably Brandenburger and Nalebuff) have argued that "complementors" constitute a sixth force. For technology startups, the strength of the ecosystem of complementary products often determines competitive dynamics as much as the five traditional forces. + +5. **Using the framework to justify inaction.** An unattractive industry structure does not mean "do not enter." It means "enter with a strategy designed for that structure." Some of the most successful startups have entered structurally challenging industries with positioning strategies that neutralized the most powerful forces. The analysis informs strategy; it does not replace it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Industry selection | The most consequential use of Five Forces: evaluating which industry to enter. At this stage, you have maximum flexibility and should choose structural attractiveness over personal enthusiasm. A mediocre product in an attractive industry outperforms a brilliant product in a structurally hostile one. | +| Validation | Barrier identification | With the industry chosen, identify which barriers to entry you must overcome and which you can circumvent. Begin building the barriers that will protect you: switching costs, integration depth, network effects, data advantages. | +| Early Traction | Buyer power management | As revenue grows, monitor customer concentration obsessively. The easiest time to diversify is when you have multiple prospects; the hardest is when a single customer dominates. Also, begin reducing supplier power through diversification and alternative development. | +| Growth | Rivalry positioning | Competition intensifies. Use Five Forces to choose where to compete and, critically, where not to. Differentiation strategies that reduce rivalry (serving a distinct segment, creating switching costs) are more valuable than operational excellence that merely matches competitors. | +| Scale | Industry shaping | At scale, the company has enough influence to shape industry structure rather than merely respond to it. Acquisitions, platform strategies, and standards-setting can alter barriers to entry, supplier power, and rivalry dynamics in the company's favor. | + +--- + +## Output Template + +```markdown +# Porter's Five Forces Analysis + +**Industry/Market:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Forces Summary + +| Force | Intensity | Key Drivers | Strategic Implication | +|-------|-----------|-------------|---------------------| +| Threat of New Entrants | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Supplier Power | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Buyer Power | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Threat of Substitutes | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | +| Industry Rivalry | [Weak/Moderate/Strong] | [Top 2-3 drivers] | [What this means for us] | + +## Overall Industry Attractiveness: [Attractive / Moderate / Unattractive] + +## Dominant Forces +The forces with greatest impact on profitability in this industry are: +1. [Force] -- because [reason] +2. [Force] -- because [reason] + +## Strategic Recommendations +Given this industry structure, the optimal positioning strategy is: +1. [Recommendation targeting dominant force] +2. [Recommendation targeting secondary force] +3. [Barrier-building priority] + +## Monitoring Plan +| Force | Key Indicator to Watch | Review Frequency | +|-------|----------------------|-----------------| +| [Force] | [Indicator] | [Quarterly/Annual] | +``` + +--- + +## Related Skills + +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- If Five Forces reveals an unattractive industry, Blue Ocean Strategy provides the methodology for creating a new market space where the forces are more favorable. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- Five Forces analyzes external industry structure; SWOT combines this with internal capability assessment to produce a complete strategic picture. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- Once Five Forces identifies the structural dynamics, the Canvas designs the business model that navigates them effectively. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Combines with Five Forces to project how industry structure might evolve under different scenarios, enabling preemptive strategic adaptation. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Disruption reshapes all five forces simultaneously; Christensen's framework explains how new entrants can neutralize incumbent advantages that Porter's model identifies. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- Five Forces analysis provides the external intelligence that strategic thinking translates into organizational direction and resource allocation decisions. diff --git a/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md b/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md deleted file mode 120000 index 1b8bdca..0000000 --- a/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/game-theory/prisoners-dilemma-and-cooperation.md \ No newline at end of file diff --git a/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md b/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md new file mode 100644 index 0000000..7bad18b --- /dev/null +++ b/plugins/foreman/skills/prisoners-dilemma-and-cooperation/SKILL.md @@ -0,0 +1,230 @@ +--- +name: "prisoners-dilemma-and-cooperation" +description: "Analyzes the Prisoner's Dilemma and related non-cooperative game structures that cause rational actors to produce collectively suboptimal outcomes. Covers price war dynamics via the Cournot duopoly model, the Tragedy of the Commons for shared resources, and mechanisms for escaping destructive equilibria through repeated games, reputation, and contracts. Use when facing price wars, market overcrowding, shared resource conflicts, cofounder tensions, or any situation where individual incentives conflict with collective benefit." +version: "1.0.0" +category: "game-theory" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - prisoners-dilemma + - cooperation + - price-wars + - tragedy-of-the-commons + - competition + - collective-action + - market-dynamics +related_skills: + - game-theory-fundamentals + - information-asymmetry + - first-mover-strategy + - porters-five-forces + - win-win-negotiation + - thomas-kilmann-conflict + - trust-equation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Prisoner's Dilemma and Cooperation + +BETRAYAL MATH. Two rational people, acting in pure self-interest, will consistently choose the option that hurts them both. This is not a paradox of human psychology -- it is a mathematical certainty. The Prisoner's Dilemma, formulated by Albert Tucker in 1950, demonstrates that individual rationality and collective rationality can be fundamentally opposed. Every price war, every race-to-the-bottom in a crowded market, every cofounder relationship that collapses into mutual suspicion follows the same structural logic. Understanding why the trap exists is the first step toward escaping it. The second step -- and the one most entrepreneurs skip -- is recognizing which structural conditions make escape possible and which make it impossible. + +--- + +## The Framework + +### The Classic Prisoner's Dilemma + +Two suspects are arrested. The police separate them and offer each the same deal: + +| | Suspect B: Stay Silent | Suspect B: Confess | +|--|----------------------|-------------------| +| **Suspect A: Stay Silent** | Both serve 1 year | A serves 10 years, B goes free | +| **Suspect A: Confess** | A goes free, B serves 10 years | Both serve 8 years | + +The logic is merciless. If B stays silent, A is better off confessing (freedom vs. 1 year). If B confesses, A is still better off confessing (8 years vs. 10 years). Confessing is the dominant strategy for both. The Nash equilibrium is (Confess, Confess) -- both serve 8 years. Yet both would prefer (Silent, Silent) -- 1 year each. Individual rationality destroys collective benefit. + +This structure is not an abstract curiosity. It is the default architecture of competition. + +### The Entrepreneur's Prisoner's Dilemma: Price Wars + +Translate the matrix into business terms. Two competing SaaS companies serving the same market must choose between maintaining prices and cutting prices. + +| | Competitor: Maintain Price | Competitor: Cut Price | +|--|--------------------------|---------------------| +| **Your Startup: Maintain Price** | Both earn healthy margins (profit: 500K each) | You lose customers, they gain share (you: 150K, them: 700K) | +| **Your Startup: Cut Price** | You gain customers, they lose share (you: 700K, them: 150K) | Both earn razor-thin margins (profit: 250K each) | + +The dominant strategy for each firm is to cut prices. The equilibrium (250K, 250K) is stable but destructive. Both would prefer the cooperative outcome (500K, 500K), but neither can unilaterally choose it without risking the worst outcome (150K). + +This is every price war ever fought. Not because entrepreneurs are stupid, but because the incentive structure makes cooperation individually irrational. + +### The Cournot Duopoly: How Price Wars Actually Work + +The Prisoner's Dilemma captures the binary choice. The Cournot model captures the continuous dynamic -- how two firms producing a similar product settle into an equilibrium output level that is worse for both than the cooperative alternative. + +The mechanism, stripped of mathematics: when two competitors independently decide how much to produce (or how aggressively to price), each firm's optimal output depends on what the other firm does. Each firm produces more than the cooperatively optimal level, because restricting output unilaterally means surrendering market share. The result: total industry output exceeds the level that maximizes total industry profit. Both firms earn less than they would under cooperation. + +**The Cournot outcome in practical terms:** + +| Scenario | Each Firm's Share of Maximum Possible Profit | +|----------|---------------------------------------------| +| Monopoly (one firm, full market) | 100% | +| Cooperative duopoly (two firms, coordinated) | 50% of a larger pie -- roughly 62.5% of monopoly profit each | +| Competitive duopoly (Cournot equilibrium) | Roughly 44% of monopoly profit each | +| Aggressive price war (below Cournot) | Diminishing toward zero | + +The gap between cooperative and competitive outcomes is the "cost of non-cooperation." In mature markets with two or three dominant players, this cost can represent billions in forfeited profit annually. Airlines, telecom providers, and cloud infrastructure companies all live in this gap. + +### The Tragedy of the Commons: When Many Players Compete + +The Prisoner's Dilemma involves two players. The Tragedy of the Commons, articulated by Garrett Hardin in 1968, extends the logic to many players sharing a finite resource -- and the results are worse. + +The mechanism: each individual gains the full benefit of exploiting a shared resource but bears only a fraction of the cost of that exploitation. A fisherman who catches one extra fish gains the entire value of that fish but depletes the stock by an amount shared across all fishermen. The rational individual response is to maximize personal exploitation. When everyone does this, the resource collapses. + +**The Entrepreneurial Tragedy of the Commons:** + +| Shared Resource | Players | Exploitation Pattern | Collapse Symptom | +|-----------------|---------|---------------------|-----------------| +| Customer attention in a market | All startups in the space | Each startup increases marketing spend to capture attention | Customer acquisition costs rise until the market becomes unprofitable for everyone | +| Open-source ecosystem | Companies building on OSS | Each company consumes without contributing | Critical projects become undermaintained; ecosystem degrades | +| VC funding in a hot sector | All funded startups in the sector | Each company burns cash to grow faster than competitors | Sector "winter" when funding dries up; most companies die | +| Talent pool in a city | Competing employers | Each company raises salaries to attract talent | Compensation hyperinflation; profitability erodes for all | + +A critical finding from the extended analysis: the more players involved, the worse the outcome. As the number of competitors increases, the equilibrium point shifts further from the collective optimum and closer to total resource depletion. Two firms in a market can sometimes sustain near-cooperative outcomes through implicit coordination. Twenty firms cannot. This is the mathematical justification for the common startup strategy of pursuing markets with few competitors: fewer players means the equilibrium is closer to the cooperative optimum. + +### Escaping the Dilemma: Five Structural Mechanisms + +The Prisoner's Dilemma is not destiny. Specific structural conditions transform non-cooperative games into sustainable cooperation. + +**1. Repetition (The Shadow of the Future).** In a one-shot game, defection is always rational. In a repeated game, the calculus changes. If players know they will interact again -- and the future interactions are sufficiently valuable -- cooperation becomes sustainable. The key parameter is the "shadow of the future": the present value of all future interactions relative to the immediate gain from defection. When the shadow is long (ongoing customer relationships, repeat negotiations, industry reputation), cooperation emerges. When it is short (one-time transactions, terminal negotiations, exit scenarios), defection dominates. + +**2. Reputation and Transparency.** When actions are visible and reputations persist, defection carries a long-term cost that exceeds the short-term gain. This is why markets with high transparency (public pricing, review systems, industry gossip networks) sustain more cooperation than opaque markets. Entrepreneurs building reputation early create a cooperation-enabling asset. + +**3. Enforceable Contracts.** The most direct escape from the dilemma: a binding agreement with penalties for defection. Non-compete clauses, exclusive distribution agreements, and minimum advertised pricing (MAP) policies all function as game-theoretic commitment devices. The contract changes the payoff matrix by adding a cost to defection. + +**4. Reducing the Number of Players.** The commons tragedy worsens with each additional player. Consolidation, exclusive partnerships, and niche focus all reduce the effective number of players. Two firms can sustain implicit cooperation; twenty cannot. Market structure that limits the player count inherently enables better equilibria. + +**5. Changing the Payoff Structure.** Sometimes the game itself can be redesigned. Joint ventures, revenue-sharing agreements, platform ecosystems, and industry standards all alter the payoff matrix so that cooperation becomes individually rational rather than requiring sacrifice. The most elegant solutions make defection unprofitable rather than merely discouraged. + +--- + +## Prompts + +**Prompt 1 -- Diagnose a Price War:** +> My company is in [describe market], and we are experiencing price compression from competitors. Help me map this as a Prisoner's Dilemma. Identify the players, their strategies, and the approximate payoffs for each combination. Then assess: is this a one-shot game or a repeated game? What is the "shadow of the future" -- how much do ongoing interactions matter? Based on the game structure, recommend whether to compete on price, differentiate to exit the game entirely, or pursue one of the five escape mechanisms (repetition, reputation, contracts, player reduction, payoff restructuring). + +**Prompt 2 -- Identify Tragedy of the Commons in Your Market:** +> My market has [number] competitors all competing for [describe shared resource: customer attention, talent, VC funding, etc.]. Help me analyze this as a Tragedy of the Commons. How far is the current equilibrium from the cooperative optimum? How does the number of competitors affect the outcome? What structural changes could move the equilibrium toward a better outcome for my company specifically -- even if the market as a whole remains competitive? + +**Prompt 3 -- Design a Cooperation Structure:** +> I want to establish cooperative dynamics with [describe: competitor, partner, cofounder, supplier]. Help me design the structural conditions for sustainable cooperation. Analyze: Is the interaction repeated or one-shot? Is the payoff transparent or opaque? Can contracts enforce cooperation? Can the number of involved parties be reduced? Present a specific mechanism design that makes cooperation individually rational for all parties. + +**Prompt 4 -- Evaluate Cofounder Dynamics as a Game:** +> My cofounder and I are facing a strategic disagreement about [describe: equity split, role division, resource allocation, pivot decision]. Map this as a two-player game. What are the strategies available to each of us? What are the payoffs for each combination? Where is the Nash equilibrium, and is it a good outcome? If not, what structural changes to our partnership (vesting schedules, decision-making protocols, third-party governance) could shift us toward a better equilibrium? + +--- + +## Use Cases + +**Early-Traction Delivery Startup Facing a Subsidy War** + +Three venture-backed food delivery startups operate in the same metropolitan area. Each subsidizes customer orders to capture market share -- offering discounts that exceed the actual delivery cost. The game structure is a multi-player Prisoner's Dilemma: each company's individually rational strategy is to subsidize more aggressively than competitors, but the collective result is that all three burn cash faster than necessary, training customers to expect below-cost pricing. The founder analyzes the game and recognizes two escape paths. First, she narrows geographic focus to three neighborhoods where her company has the strongest supply density, effectively reducing the game from three-player to near-monopoly in those zones. Second, she shifts the competition axis from price subsidy to delivery speed -- changing the payoff structure so that the game is no longer purely about who offers the biggest discount. + +**Growth-Stage B2B Company in a Feature War** + +Two competing project management tools for construction companies have entered a feature war -- each copying the other's features within weeks of release. The result is that neither achieves sustainable differentiation, and both spend engineering resources on features that cancel each other out rather than advancing the product category. The CTO maps this as an iterated Prisoner's Dilemma and calculates that the "shadow of the future" is long: both companies expect to compete for years, the market is transparent (features are publicly visible), and customer switching costs are moderate. She proposes an implicit cooperation strategy: instead of matching every competitor feature, focus engineering on a distinct product dimension (mobile-first vs. desktop-first) and signal this strategic direction publicly. By committing visibly to a different lane, she converts a zero-sum feature war into a differentiated market where both companies can earn healthy margins. + +**Scale-Stage Platform Managing Ecosystem Competition** + +A developer platform with 2,000 third-party applications observes a Tragedy of the Commons: developers competing for the same user attention oversaturate certain categories, degrading discovery quality for users and profitability for developers. The platform CEO applies the commons framework and implements three interventions. First, category-specific application caps that limit the number of players per niche (reducing n). Second, a revenue-sharing model that rewards quality over quantity (changing the payoff structure). Third, transparent performance metrics that make reputation visible and consequential (enabling reputation-based cooperation). Within six months, developer revenue per application increases by 40%, and user satisfaction scores in the affected categories recover. + +--- + +## Anti-Patterns + +1. **Assuming the dilemma is inescapable.** The Prisoner's Dilemma only traps players when the game is one-shot, anonymous, and structurally fixed. Most business interactions are repeated, reputation-bearing, and structurally malleable. The pessimistic reading of the dilemma -- "cooperation is impossible" -- is theoretically valid only under conditions that rarely obtain in practice. The productive question is always: which structural conditions can be changed to enable cooperation? + +2. **Cooperating in a genuinely one-shot game.** The reverse error is equally dangerous. When the interaction truly will not repeat -- a one-time negotiation with a party you will never encounter again, a terminal business transaction -- cooperation is not sustained by any structural mechanism. Naively cooperating in a one-shot game against a rational adversary is not noble; it is strategically incoherent. Recognize the game type before selecting the strategy. + +3. **Blaming competitors for "irrational" price wars.** Price wars are typically the Nash equilibrium of the game's payoff structure. Calling competitors irrational for doing what the structure incentivizes is a failure of analysis, not a competitor failure. The productive response is to change the game structure, not to lament the opponent's choices. + +4. **Ignoring the number of players.** The gap between the competitive equilibrium and the cooperative optimum widens with each additional player. Entrepreneurs who enter crowded markets without a plan to reduce the effective number of competitors (through niching, differentiation, or consolidation) are accepting the worst version of the commons outcome. Player count is a strategic variable, not a given. + +5. **Applying the cooperation framework to genuinely zero-sum situations.** The Prisoner's Dilemma produces suboptimal outcomes because the game has a cooperative surplus -- a better outcome available if players coordinate. Some competitive situations are genuinely zero-sum: one player's gain is exactly another's loss. In zero-sum games, cooperation mechanisms do not apply. Attempting to cooperate in a zero-sum game simply transfers value to the less cooperative party. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Identifying the game structure | Before entering a market, determine whether the competitive dynamic is a Prisoner's Dilemma, a coordination game, or something else. Markets where the dilemma structure dominates (commodity products, low switching costs, many competitors) will compress margins regardless of execution quality. Choose accordingly. | +| Early Traction | Monitoring defection signals | Track competitor pricing, feature releases, and marketing spend for signs of escalation. Early detection of a price war or feature war creates time to respond structurally rather than reactively. | +| Growth | Building cooperation infrastructure | Establish the conditions for sustainable competition: visible commitments to a distinct positioning, long-term contracts that reduce incentives to defect, reputation investments that raise the cost of aggressive moves. The shadow of the future is longest at growth stage -- leverage it. | +| Scale | Designing market rules | At scale, the company can shape the game itself through platform policies, industry standards, ecosystem design, and strategic acquisitions. The goal shifts from surviving the dilemma to redesigning the game so the dilemma does not arise. | + +--- + +## Output Template + +```markdown +# Competitive Game Analysis: Cooperation vs. Defection + +**Market/Situation:** [Description] +**Company:** [Name] +**Date:** [Date] + +## Game Structure Identification + +- **Game type:** [Prisoner's Dilemma / Tragedy of the Commons / Coordination Game / Other] +- **Number of significant players:** [Count] +- **Repeated or one-shot:** [Assessment] +- **Shadow of the future:** [Long / Medium / Short -- explain] + +## Payoff Matrix + +| | Competitor Cooperates | Competitor Defects | +|--|----------------------|-------------------| +| **We Cooperate** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | +| **We Defect** | Us: [payoff], Them: [payoff] | Us: [payoff], Them: [payoff] | + +## Equilibrium vs. Optimum + +- **Nash Equilibrium (predicted outcome):** [Description and payoffs] +- **Cooperative Optimum (ideal outcome):** [Description and payoffs] +- **Cost of non-cooperation:** [Gap between the two] + +## Escape Mechanism Assessment + +| Mechanism | Feasible? | Implementation | Expected Impact | +|-----------|-----------|---------------|----------------| +| Repetition / Long-term interaction | [Yes/No] | [How] | [Impact] | +| Reputation / Transparency | [Yes/No] | [How] | [Impact] | +| Enforceable contracts | [Yes/No] | [How] | [Impact] | +| Reduce player count | [Yes/No] | [How] | [Impact] | +| Restructure payoffs | [Yes/No] | [How] | [Impact] | + +## Recommended Strategy + +1. [Primary action] +2. [Fallback if cooperation fails] +3. [Long-term structural play] +``` + +--- + +## Related Skills + +- **[Game Theory Fundamentals](../../content/skills/game-theory/game-theory-fundamentals.md)** -- The prerequisite framework: players, strategies, payoffs, and Nash equilibrium provide the analytical foundation that this skill applies to cooperation problems. +- **[Information Asymmetry](../../content/skills/game-theory/information-asymmetry.md)** -- When players hold different information, the cooperation problem becomes more complex: adverse selection and moral hazard create additional barriers to trust. +- **[Evolutionary Strategy](../../content/skills/game-theory/evolutionary-strategy.md)** -- Extends the one-shot dilemma into population dynamics, revealing how cooperative and defecting strategies compete and stabilise across repeated market interactions. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Fisher and Ury's principled negotiation addresses the relationship and communication dimensions of cooperation; game theory provides the structural and incentive analysis. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the behavioural mechanism through which the "shadow of the future" operates; the trust equation quantifies the components that make cooperation sustainable. +- **[Cooperative Negotiation](../../content/skills/negotiation/cooperative-negotiation.md)** -- Translates the game-theoretic cooperation framework into practical conversational techniques for building deals where both parties gain. diff --git a/plugins/foreman/skills/product-life-cycle/SKILL.md b/plugins/foreman/skills/product-life-cycle/SKILL.md deleted file mode 120000 index 5ac83d4..0000000 --- a/plugins/foreman/skills/product-life-cycle/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/product-life-cycle.md \ No newline at end of file diff --git a/plugins/foreman/skills/product-life-cycle/SKILL.md b/plugins/foreman/skills/product-life-cycle/SKILL.md new file mode 100644 index 0000000..704c82b --- /dev/null +++ b/plugins/foreman/skills/product-life-cycle/SKILL.md @@ -0,0 +1,251 @@ +--- +name: "product-life-cycle" +description: "Diagnoses a product's current lifecycle phase -- introduction, growth, maturity, or decline -- and prescribes phase-appropriate strategy for pricing, marketing, investment, and competitive response. Use when assessing whether a product is entering maturity, planning portfolio balance across lifecycle stages, timing market entry, designing extension strategies for declining products, or deciding between harvest, niche, divest, and exit options." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - product-strategy + - market-timing + - competitive-dynamics + - pricing-strategy + - portfolio-management +related_skills: + - growth-share-matrix + - disruptive-innovation + - doblin-ten-types + - kaizen-bpr +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Product Life Cycle + +The BlackBerry was once the most coveted device in corporate America -- the "CrackBerry" that redefined mobile communication. The fax machine was, for two decades, as essential to business as the telephone. The Sony Walkman created the portable music category, sold 400 million units, and was rendered obsolete in under a decade. Every product, however dominant in its moment, follows a biological arc: birth, growth, maturity, and decline. Theodore Levitt formalised this observation in a 1965 Harvard Business Review article, and the Product Life Cycle (PLC) has since become one of the foundational frameworks of marketing and business strategy -- not because it predicts the future with precision, but because it forces the uncomfortable question every entrepreneur must eventually answer: what phase is your product in, and are you managing accordingly? + +The framework's power lies in its strategic implications. The same product, in different phases, demands different pricing, different marketing, different competitive responses, and different levels of investment. Companies that manage a growth-phase product as if it were mature leave money on the table. Companies that manage a mature product as if it were still growing burn cash without return. And companies that refuse to acknowledge decline preside over slow organisational death. + +--- + +## The Framework + +### The Four Phases + +#### Phase 1: Introduction + +The product enters the market. Sales are low. Costs are high. Profit is negative or minimal. The customer base consists of innovators and early adopters who tolerate imperfection in exchange for novelty or functional advantage. + +**Characteristics:** +- High unit cost due to low volume and manufacturing learning curve +- Heavy investment in education and awareness (the market does not yet understand the product) +- Limited or no competition (but watch for fast followers) +- Pricing strategy: either skimming (high price, early revenue capture) or penetration (low price, rapid adoption) +- Distribution is narrow; channels are being established + +**Strategic imperative:** Survive long enough for the market to develop. The introduction phase kills more products than competition does -- not because the product is bad, but because the company runs out of capital or patience before demand materialises. + +**Duration signal:** The introduction phase ends when sales growth accelerates and competitors begin entering the market. + +#### Phase 2: Growth + +Demand accelerates. Sales curve steepens. Competitors enter, attracted by the market's potential. Unit costs decline as volume increases. Profits emerge and expand. The customer base broadens from early adopters to the early majority. + +**Characteristics:** +- Revenue growing 20%+ per period (the exact rate is sector-dependent) +- Competitors entering and product differentiation becoming critical +- Distribution expanding; channels competing for the product +- Marketing shifts from awareness to differentiation +- Pricing remains stable or declines slightly as competition increases and scale drives costs down + +**Strategic imperative:** Maximise market share. The growth phase is the window during which market positions are established. Companies that invest aggressively in distribution, brand building, and product improvement during growth capture the positions they will hold through maturity. Underinvestment during growth creates a permanent competitive handicap. + +**Duration signal:** The growth phase ends when the rate of sales growth begins to decelerate -- not when growth stops, but when it slows. + +#### Phase 3: Maturity + +The market approaches saturation. Growth decelerates and eventually stabilises. Competition intensifies as rivals fight for share in a market that is no longer expanding. Profits peak and then decline as price competition erodes margins. The customer base is mainstream; differentiation is difficult. + +**Characteristics:** +- Sales growth flattening to low single digits +- Intense competition; weaker competitors begin exiting +- Marketing emphasis shifts to retention and loyalty +- Product innovation is incremental; features converge across competitors +- Pricing under pressure; margins decline +- Overproduction and excess capacity may emerge + +**Strategic imperative:** Defend share and maximise profitability. This is the phase where operational efficiency matters most. Companies that have built scale, brand loyalty, and process efficiency during growth are well-positioned. Those that have not face a grinding competitive struggle. Strategic options include product modification (new features, quality improvements, style changes), market modification (new segments, new geographies, new use cases), and marketing mix modification (price adjustments, channel expansion, promotional innovation). + +**Duration signal:** Maturity ends when sales begin sustained decline despite competitive efforts. + +#### Phase 4: Decline + +Sales fall. The market contracts as customers migrate to substitute products or new technologies. Remaining competitors face a shrinking pie. Margins collapse for all but the most efficient producers. Investment in the product yields diminishing returns. + +**Characteristics:** +- Sustained sales decline over multiple periods +- Competitors exiting the market +- Customer base ageing; new customer acquisition near zero +- Investment in the product generates negative ROI +- Remaining demand concentrated in niche segments + +**Strategic imperative:** Manage the decline deliberately. The options are: +1. **Harvest** -- Reduce investment to minimum, extract maximum remaining profit, fund other products +2. **Niche** -- Retreat to a defensible segment where loyal customers sustain profitable operations +3. **Divest** -- Sell the product line to a competitor who can achieve consolidation economics +4. **Exit** -- Discontinue the product and redeploy resources + +The worst strategy in decline is denial: continuing to invest as if growth will return. It rarely does. + +### The PLC Curve + +``` +Sales + ^ + | ___________ + | / \ + | / Maturity \ + | / \ + | / \ Decline + | / \ + | Growth / \ + | / \___ + | Introduction/ + | ___/ + +-------------------------------------------------> Time +``` + +### Profit Curve Overlay + +Profit follows a different trajectory: negative during introduction, rising sharply during growth, peaking during early maturity, and declining through late maturity and decline. The gap between the sales curve and the profit curve is critical -- a product can show healthy sales while profitability is already deteriorating. + +--- + +## Prompts + +**Prompt 1 -- Phase Diagnosis:** +> "Analyse my product's current life cycle phase. Here are the key indicators: [sales trend over past 6-12 months, competitive landscape, customer acquisition trends, pricing pressure, margin trajectory]. Based on these indicators, which PLC phase is my product in? What are the three most important strategic actions for this phase?" + +**Prompt 2 -- Phase Transition Planning:** +> "My product appears to be transitioning from [current phase] to [next phase]. What are the early warning signals I should monitor to confirm this transition? What strategic, operational, and financial changes should I prepare for? Create a 90-day transition plan that adapts my pricing, marketing, product development, and resource allocation to the incoming phase." + +**Prompt 3 -- Portfolio Phase Mapping:** +> "Map each of my products to its PLC phase: [list products with relevant metrics]. Assess whether the portfolio is balanced -- do we have products in introduction/growth to replace revenue as mature products decline? Identify portfolio gaps and recommend timing for new product introductions." + +**Prompt 4 -- Extension Strategy Design:** +> "My product is in late maturity and showing early signs of decline. Design three extension strategies that could reignite growth: (1) product modification (features, quality, or design changes), (2) market modification (new segments, geographies, or use cases), and (3) marketing mix modification (pricing, distribution, or promotion changes). For each, estimate the investment required and the probability of success." + +**Prompt 5 -- Decline Management:** +> "My product is in the decline phase with these metrics: [sales decline rate, remaining market size, competitor exits, margin trajectory]. Evaluate the four decline strategies (harvest, niche, divest, exit) for my situation. Recommend the optimal approach and create a 6-month execution plan including financial projections." + +--- + +## Use Cases + +**Validation-Stage Founder Timing Market Entry** + +A founder developing a plant-based protein product analyses the PLC of the broader plant-based food market. Industry data shows that the category has moved past introduction (awareness is high, major players have entered) and is in early growth (sales growing 20%+ annually, new brands entering weekly, distribution expanding into mainstream retail). PLC analysis informs the entry strategy: the growth phase favours differentiation over education. Rather than spending marketing budget on explaining why plant-based protein matters (an introduction-phase message), the founder focuses on what makes this product different from the dozens already available (a growth-phase message). Pricing follows a penetration strategy, since growth-phase markets reward share capture over margin maximisation. + +**Growth-Stage Company Managing a Maturing Core Product** + +A project management SaaS tool that drove the company's growth now shows decelerating revenue growth (from 80% to 25% YoY), increasing competitive convergence (five major competitors with similar features), and declining new customer acquisition rates. PLC diagnosis: the product is transitioning from growth to maturity. The strategic response: shift investment from feature development (growth-phase priority) to operational efficiency and customer retention (maturity-phase priorities). Simultaneously, the company launches a new AI-powered analytics module positioned as a growth-phase product that leverages the existing customer base as its initial market. The core product becomes the cash cow that funds the new product's introduction phase. + +**Scale-Stage Brand Extending a Declining Product** + +A consumer electronics company observes that its flagship hardware product -- once a category leader -- has experienced three consecutive quarters of declining sales as the market shifts toward software-based alternatives. Rather than investing in a next-generation hardware product (sustaining a declining category), the PLC analysis recommends a market modification strategy: repositioning the hardware product for the professional niche segment where physical devices retain value (recording studios, live performance), while launching a software-based product for the mainstream market. The hardware product transitions from mass-market decline to niche maturity, sustaining profitability at lower volume. + +--- + +## Anti-Patterns + +**Phase Denial.** The most dangerous anti-pattern. Founders and executives who insist their product is "still in growth" when every indicator signals maturity or decline. Revenue growth deceleration, margin compression, and competitive convergence are objective signals. Interpreting them as temporary setbacks rather than structural transitions leads to misallocated investment and missed strategic windows. + +**Assuming All Products Follow the Same Curve.** PLC durations vary enormously. Fashion products may cycle through all four phases in eighteen months. Infrastructure products may remain in maturity for decades. Technology platforms may skip growth and move directly from introduction to maturity if they achieve rapid network effects. The framework describes phases, not timelines. + +**Applying Growth Strategies to Mature Products.** Pouring marketing spend into customer acquisition for a product in maturity, where the addressable market is saturated and incremental customers are expensive. Maturity demands retention and efficiency, not acquisition and expansion. The metrics change; the strategy must change with them. + +**Ignoring Decline Signals in Favour of Extension Hope.** Extension strategies (product modification, market modification, marketing mix changes) can work -- but they succeed in roughly one case in three. Founders who serially extend a declining product rather than investing in the next product are optimising for the past. Every extension attempt should have a predefined success threshold and a kill date. + +**Treating the PLC as Deterministic.** The framework describes a tendency, not a law of nature. Products can be revived (vinyl records). Markets can re-enter growth after decline (electric vehicles). Disruption can compress cycles or restart them. The PLC is a diagnostic tool, not a prophecy. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Assess market phase before entering | Entering a market in late maturity or decline is substantially harder than entering during introduction or early growth | +| Validation | Confirm you are in the right phase | Validate whether the market is genuinely in the phase you believe; misdiagnosis leads to misallocated strategy | +| Early Traction | Invest for the growth phase | If traction signals confirm a growth-phase market, invest aggressively in share capture | +| Growth | Prepare for maturity | Build the operational efficiency and brand loyalty that will sustain you when growth decelerates | +| Scale | Manage the portfolio across phases | Ensure that new products in introduction/growth will replace revenue as current products mature and decline | + +At the idea stage, PLC analysis answers a threshold question: is this market in a phase that rewards new entrants? Introduction and early growth phases favour startups because positions are not yet locked. Late maturity and decline phases favour incumbents with established share and economies of scale. A superior product entering a declining market faces headwinds that no amount of execution can overcome. + +At scale, the PLC becomes a portfolio management tool. The healthiest companies maintain a pipeline of products at different lifecycle stages: mature products funding the introduction of new ones, growth products building the future revenue base, and declining products being managed out of the portfolio deliberately rather than by neglect. + +--- + +## Output Template + +**Target Audience: Product Team / Head of Product** + +```markdown +# Product Life Cycle Assessment: [Product Name] +## Date: [Date] + +### Phase Diagnosis +- **Current phase:** [Introduction / Growth / Maturity / Decline] +- **Confidence:** [High/Medium/Low] +- **Phase duration to date:** [Duration] +- **Estimated time to next phase transition:** [Duration] + +### Supporting Evidence +| Indicator | Value | Trend | Phase Signal | +|-----------|-------|-------|-------------| +| Sales growth rate | [X%] | [Accelerating/Stable/Decelerating] | [Which phase this indicates] | +| Competitive entries/exits | [N entering / N exiting] | [Net entry/exit] | [Which phase this indicates] | +| Customer acquisition cost | [$X] | [Rising/Stable/Falling] | [Which phase this indicates] | +| Gross margin | [X%] | [Expanding/Stable/Compressing] | [Which phase this indicates] | +| Market awareness/adoption | [X%] | [Growing/Saturating] | [Which phase this indicates] | + +### Phase-Appropriate Strategy +| Dimension | Current Approach | Recommended Approach | Gap | +|-----------|-----------------|---------------------|-----| +| Pricing | [Current] | [Recommended for this phase] | [Change needed] | +| Marketing focus | [Current] | [Recommended for this phase] | [Change needed] | +| Product investment | [Current] | [Recommended for this phase] | [Change needed] | +| Distribution | [Current] | [Recommended for this phase] | [Change needed] | +| Competitive response | [Current] | [Recommended for this phase] | [Change needed] | + +### Transition Readiness +- Next phase: [Phase] +- Early warning signals to monitor: [List 3-5 indicators] +- Strategic preparations required: [List key changes] +- Investment implications: [Budget/resource shifts] + +### Extension Opportunities (if Maturity/Decline) +| Strategy | Description | Investment | Success Probability | Timeline | +|----------|-------------|------------|--------------------|---------| +| Product modification | [Change] | [$X] | [H/M/L] | [Duration] | +| Market modification | [Change] | [$X] | [H/M/L] | [Duration] | +| Marketing mix modification | [Change] | [$X] | [H/M/L] | [Duration] | +``` + +--- + +## Related Skills + +- **[Growth Share Matrix](../../content/skills/frameworks/growth-share-matrix.md)** -- The PLC and BCG matrix are complementary lenses on the same reality; products move through BCG quadrants as they progress through PLC phases. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Disruption often compresses or terminates the PLC of incumbent products; understanding disruption dynamics helps predict when decline will arrive faster than the natural curve suggests. +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- Each PLC phase demands a different marketing mix; introduction favors awareness and skimming pricing, while maturity demands retention-focused promotion and competitive pricing. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Maturity-phase strategy demands operational excellence; Kaizen and BPR provide the methodology for achieving the efficiency that maturity requires. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Projecting when a product will transition between lifecycle phases is inherently uncertain; scenario planning stress-tests strategy against multiple phase-transition timelines. +- **[Net Promoter Score](../../content/skills/frameworks/net-promoter-score.md)** -- NPS trends serve as leading indicators of lifecycle phase transitions; declining NPS among core segments often signals the shift from growth to maturity before revenue data confirms it. diff --git a/plugins/foreman/skills/psychological-safety-practice/SKILL.md b/plugins/foreman/skills/psychological-safety-practice/SKILL.md deleted file mode 120000 index c7bd7ca..0000000 --- a/plugins/foreman/skills/psychological-safety-practice/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/psychological-safety-practice.md \ No newline at end of file diff --git a/plugins/foreman/skills/psychological-safety-practice/SKILL.md b/plugins/foreman/skills/psychological-safety-practice/SKILL.md new file mode 100644 index 0000000..b818b06 --- /dev/null +++ b/plugins/foreman/skills/psychological-safety-practice/SKILL.md @@ -0,0 +1,213 @@ +--- +name: "psychological-safety-practice" +description: "Translates psychological safety theory into daily leader behaviours -- the specific words, reactions, and micro-actions that build or destroy a team's willingness to speak up. Covers misconceptions, responding to mistakes, inviting honest feedback, modelling healthy conflict, addressing bad behaviour immediately, and making mental health discussable. Use when meetings have gone quiet, when a post-mortem reveals that someone saw the failure coming but said nothing, when a leader suspects enforced politeness is masking dysfunction, or when feedback from direct reports has become vague and uninformative." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - psychological-safety + - trust + - feedback + - culture + - meetings + - conflict + - mental-health + - daily-practice +related_skills: + - psychological-safety + - emotional-intelligence + - radical-candor + - johari-window +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Psychological Safety in Practice + +DESTRUCTION SPEED. Psychological safety takes months of consistent behaviour to build and approximately four seconds to destroy. Those four seconds might sound like: "That's a stupid question." Or: a sigh and an eye-roll when a junior employee challenges an assumption. Or: publicly reassigning a project the day after someone reported a mistake. Or: nothing at all -- silence where acknowledgment was expected, indifference where curiosity was needed. The theoretical architecture of psychological safety -- Edmondson's research, Clark's four stages, Google's Project Aristotle -- is documented in the frameworks category of this system. What follows is not the theory. It is the practice: the specific behaviours, phrases, and micro-decisions that determine whether a team believes it is safe to take interpersonal risks. Theory explains why safety matters. Practice determines whether it exists. + +--- + +## The Framework + +### What Psychological Safety Is Not + +Two misconceptions corrode more safety initiatives than any deliberate act of hostility. + +**Misconception 1: Safety means niceness.** Polite workplaces can be psychologically dangerous. When courtesy functions as a silencing mechanism -- when "being professional" means never expressing disagreement -- the team operates in a state of enforced pleasantness that suppresses the candour safety requires. Psychological safety is not the absence of discomfort. It is the presence of permission to be uncomfortable productively. + +**Misconception 2: Safety means comfort.** Learning is uncomfortable. Admitting mistakes is uncomfortable. Pointing out that a senior leader's strategy has a flaw is uncomfortable. Psychological safety does not eliminate discomfort; it makes discomfort survivable. The question is not "does this feel easy?" but "will I be punished for being honest?" + +### The Seven Daily Practices + +**Practice 1: Set the Stage Before Every Meeting** + +Silence is the default human response in group settings. Overriding that default requires active setup -- not once, but repeatedly. Before discussions where input is needed: + +- Explain why every perspective matters for this specific decision. +- Name the specific risks of not hearing from the group (lower creativity, missed risks, weaker solutions). +- State explicitly that disagreement is welcome and expected. + +This is not a speech. It is two or three sentences. "Before we decide on the Q3 roadmap, I want to hear what concerns each of you has. The worst outcome is that we commit to something and discover three months from now that someone in this room saw the problem but didn't raise it." + +**Practice 2: Respond to Mistakes as Data** + +The moment a team member reports a mistake, the leader's reaction establishes or erases months of safety-building. The wrong response -- frustration, blame, even a visible sigh -- teaches the entire team that honesty is penalised. The right response follows a sequence: + +1. Thank the person for surfacing the issue. ("Thank you for catching this. What did you notice first?") +2. Ask diagnostic questions without assigning blame. ("What contributed to this? What would have prevented it?") +3. Focus on the system, not the individual. ("What do we need to change so this doesn't recur?") +4. Follow up visibly. If the mistake leads to a process improvement, credit the person who raised it. + +The fourth step is the one most leaders skip, and it is the most important. When the team sees that reporting a mistake led to a positive change -- and that the reporter was credited, not punished -- the behaviour propagates. + +**Practice 3: Invite Feedback on Yourself** + +Leaders who say "my door is always open" receive almost no honest feedback through that open door. The problem is structural: the power differential makes unsolicited upward feedback feel dangerous regardless of how welcoming the leader believes they are. + +Active solicitation requires specific questions: + +- "What did you hear when I shared my strategy?" (not "what did you think of my strategy?") +- "How did it feel when I sent that email?" (not "was my email clear?") +- "What is one thing I could do differently in these meetings?" + +When feedback arrives -- especially critical feedback -- the response protocol is: listen, do not defend, reflect, and thank. Any defensive reaction, however mild, teaches the giver that feedback was not actually wanted. Changes made in response to feedback should be visible and attributed: "Based on what several of you told me, I'm going to change how we run these reviews." + +**Practice 4: Address Bad Behaviour Immediately** + +Zero tolerance for blatant rudeness -- dismissing, steamrolling, using derogatory language -- is the structural foundation of safety. If bad behaviour goes unaddressed, the implicit message is that safety standards are aspirational rather than enforced. + +The intervention protocol: + +- Pull the person aside immediately (not tomorrow, not at the next one-on-one). +- Name the specific behaviour. ("When you interrupted Sarah and said her data was irrelevant, that is the behaviour I need to discuss.") +- Explain the impact. ("That signals to everyone in the room that challenging your position is not welcome.") +- State the expectation. ("In this team, we engage with ideas we disagree with. We do not dismiss the people presenting them.") +- Follow up to verify change. + +The calibration matters. This is not about policing tone or micromanaging interpersonal style. It is about maintaining the minimum conditions under which people will speak honestly. + +**Practice 5: Model Healthy Conflict** + +When a leader and a team member disagree, the rest of the team watches how the disagreement unfolds. If the leader shuts down the dissent -- through authority, through volume, through subtle dismissal -- the team learns that disagreement is tolerated only from peers, not directed upward. + +Modelling healthy conflict means: + +- Giving the dissenting person space to articulate their full position before responding. +- Acknowledging the merit in their argument explicitly, even if you ultimately disagree. +- Engaging in civil debate -- exchanging reasoning, not assertions. +- Accepting the outcome gracefully if the evidence supports the other position. + +The team does not need to see the leader lose arguments frequently. They need to see the leader engage with disagreement respectfully -- once or twice is enough to establish the norm. + +**Practice 6: Make Mental Health Discussable** + +Employees who struggle with mental health challenges need to be able to ask for help without fearing that their leader will view them differently. Two actions lower the barrier: + +- **Monitor language.** Comments like "Don't get all OCD on my spreadsheet" stigmatise conditions that team members may be managing. Address casual misuse of clinical terms when it occurs, and explain -- without lecturing -- why the language is harmful. +- **Know the resources.** Familiarise yourself with the company's mental health benefits, EAP programmes, and external referral options so you can point people to them naturally when the moment arises. The leader does not need to be a therapist. They need to be a credible connector. + +**Practice 7: Manage Your Own Vulnerability Boundaries** + +Opening up to a team builds connection. Oversharing erodes authority. The calibration: if you would not mind hearing the comment from your own boss, it is probably appropriate. "I'm having a rough day" humanises. "I had a terrible fight with my partner this morning" creates discomfort the team cannot productively address. Authenticity is not the same as transparency. Share enough to be human; retain enough to be leaderly. + +--- + +## Prompts + +**Prompt 1 -- Safety Diagnostic:** +> Here is how my team currently behaves in meetings: [describe -- who speaks, who stays silent, how disagreement is expressed or suppressed, what happens after mistakes]. Assess the current state of psychological safety using the seven daily practices as a checklist. Which practices are strong? Which are absent? Give me a specific 30-day plan to address the two weakest areas. + +**Prompt 2 -- Mistake Response Script:** +> A team member just reported a significant error: [describe the mistake and context]. Draft three versions of my response: one that destroys safety (so I can see what to avoid), one that maintains safety, and one that actively builds safety by turning the mistake into a learning moment. For the third version, include the follow-up actions I should take over the next week. + +**Prompt 3 -- Feedback Solicitation Design:** +> I suspect my team is not giving me honest feedback. Here is the evidence: [describe -- vague responses, silence in meetings, turnover patterns]. Design a feedback solicitation approach: specific questions I should ask, the setting in which I should ask them, how I should respond in the moment, and how I should communicate changes that result from the feedback. + +**Prompt 4 -- Bad Behaviour Intervention Script:** +> A team member did the following in a meeting: [describe the specific behaviour]. I need to address it immediately. Draft a conversation script that names the behaviour specifically, explains its impact on team safety, states the expectation clearly, and preserves the person's dignity. Include guidance on what to do if they become defensive. + +--- + +## Use Cases + +**Early-Traction Startup: Silence After a Product Failure** +A 15-person startup ships a feature that causes significant customer complaints. In the post-mortem, two engineers reveal they had concerns about the release timeline but did not raise them because "the CEO seemed really committed to the date." The CEO, who believed the team was fully aligned, realises that their enthusiasm was functioning as pressure. The intervention: the CEO begins every product discussion with "What concerns me is [specific risk]. What concerns you?" -- modelling vulnerability and explicitly inviting dissent. Within three months, pre-release concerns are surfaced regularly and the defect rate drops measurably. + +**Growth-Stage Company: The Polite Team That Never Disagrees** +A marketing team scores highly on employee satisfaction surveys but produces mediocre creative work. An external facilitator observes that the team is exceptionally polite -- and that this politeness functions as a silencing mechanism. No one challenges a campaign concept. No one says "this is not good enough." The team leader institutes Practice 5 (modelling healthy conflict) by publicly disagreeing with a creative brief in the next meeting, explaining their reasoning, inviting counterarguments, and changing their position based on what they hear. The shift is not immediate -- it takes six weeks -- but the quality of debate in creative reviews improves measurably, and the next campaign outperforms the previous three. + +**Scale-Stage Organisation: Rebuilding After a Trust Breach** +A department head publicly berated a junior analyst for an error in a board presentation. The incident was witnessed by eight people and discussed by forty. Psychological safety in the department collapsed within days: error reporting stopped, meeting participation became perfunctory, and two top performers began interviewing elsewhere. The VP intervening applies the full protocol: addresses the behaviour privately with the department head (Practice 4), holds a team meeting acknowledging that the incident violated team standards (Practice 1), solicits feedback from the team on what they need to feel safe again (Practice 3), and institutes a visible mistake-response protocol (Practice 2). Recovery takes four months -- roughly one hundred times longer than the four seconds it took to create the breach. + +--- + +## Anti-Patterns + +1. **Safety as a One-Time Initiative.** Announcing psychological safety as a team value in a single meeting and assuming it is now established. Safety is maintained through daily behavioural consistency, not through declarations. The moment behaviour contradicts the declaration, the declaration becomes evidence of hypocrisy. + +2. **Confusing Safety with Lowered Standards.** Believing that psychological safety means accepting poor performance without consequences. The opposite is true: safety enables honest performance conversations. A team that feels safe can hear "your work is not meeting the standard" without interpreting it as a personal attack. A team that does not feel safe cannot hear any feedback at all. + +3. **Soliciting Feedback and Then Punishing the Messenger.** The leader who asks for honest feedback, receives it, and then responds with defensiveness, cold-shouldering, or subtle retaliation. This is worse than never asking, because it teaches the team that the solicitation was performative. + +4. **Selective Enforcement.** Addressing bad behaviour from junior employees while tolerating it from senior performers or executives. If a top salesperson can dismiss a junior colleague's concerns with impunity, the team learns that safety is contingent on status -- which means it does not exist. + +5. **Over-Sharing as Safety-Building.** A leader who shares every anxiety, frustration, and personal struggle with the team in the name of vulnerability. This is not safety-building; it is emotional burden-shifting. The team needs to see their leader as human. They do not need to manage their leader's emotional state. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder behaviour as culture code | In a small team, the founder's every reaction to mistakes, disagreement, and feedback establishes the psychological safety baseline for the entire company. There are no policies to hide behind. The founder's behaviour is the policy. | +| Growth | Scaling safety through middle management | The founder can no longer be present in every meeting. Psychological safety depends on whether middle managers replicate the founder's safety-building behaviours or introduce their own patterns. Training managers in the seven practices is not optional -- it is a growth prerequisite. | +| Scale | Institutional safety mechanisms | Safety must survive leader transitions, team reorganisations, and cultural dilution from rapid hiring. This requires codified norms (how we respond to mistakes, how we run post-mortems, how we handle bad behaviour) that operate independently of any individual leader's personality. | + +--- + +## Output Template + +```markdown +# Psychological Safety Assessment: [Team / Department] + +## Current State +- Meeting participation pattern: [who speaks, who is silent] +- Last reported mistake: [when, how it was handled, what happened next] +- Feedback quality: [specific and actionable vs. vague and safe] +- Recent conflict: [how it was resolved, or how it was avoided] + +## Practice Scorecard +| Practice | Status | Evidence | Priority Action | +|----------|--------|----------|-----------------| +| Stage-setting before meetings | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Mistake response | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Feedback solicitation | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Bad behaviour enforcement | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Healthy conflict modelling | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Mental health openness | [Strong/Weak/Absent] | [specific observation] | [specific action] | +| Vulnerability calibration | [Strong/Weak/Absent] | [specific observation] | [specific action] | + +## 30-Day Plan +1. Week 1: [specific action targeting the weakest practice] +2. Week 2: [specific action] +3. Week 3: [specific action] +4. Week 4: [assessment and adjustment] +``` + +--- + +## Related Skills + +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's framework and Clark's four stages provide the theoretical foundation; this skill provides the daily behaviours and specific language that translate that theory into practice. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Scott's framework for caring personally while challenging directly describes the communication style that psychological safety enables. +- **[Johari Window](../../content/skills/frameworks/johari-window.md)** -- The Johari model maps the relationship between self-disclosure and feedback; psychological safety determines whether the feedback quadrant expands or contracts over time. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- The self-regulation and empathy dimensions of emotional intelligence are the personal capabilities that enable a leader to execute the seven daily practices consistently under stress. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- The leader's willingness to model vulnerability and raise difficult issues is the primary behaviour that creates safety for the team to do the same. +- **[Inclusive Leadership](../../content/skills/leadership/inclusive-leadership.md)** -- Psychological safety is not distributed equally; inclusion practices address the specific barriers that prevent underrepresented team members from experiencing the safety the leader intends. diff --git a/plugins/foreman/skills/psychological-safety/SKILL.md b/plugins/foreman/skills/psychological-safety/SKILL.md deleted file mode 120000 index a7aa27e..0000000 --- a/plugins/foreman/skills/psychological-safety/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/psychological-safety.md \ No newline at end of file diff --git a/plugins/foreman/skills/psychological-safety/SKILL.md b/plugins/foreman/skills/psychological-safety/SKILL.md new file mode 100644 index 0000000..9082b37 --- /dev/null +++ b/plugins/foreman/skills/psychological-safety/SKILL.md @@ -0,0 +1,207 @@ +--- +name: "psychological-safety" +description: "Assesses and builds team psychological safety using Edmondson's framework and Clark's four developmental stages: inclusion, learner, contributor, and challenger safety. Identifies leadership behaviours that build or erode the shared belief that interpersonal risk-taking is safe. Use when team members withhold concerns, meetings lack candour, post-mortems reveal foreseeable failures that went unreported, or founders need to diagnose why innovation has narrowed." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - team-performance + - culture + - trust + - innovation + - leadership +related_skills: + - emotional-intelligence + - growth-mindset + - johari-window + - thinking-fast-and-slow +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Psychological Safety + +When Google set out to discover what made its best teams effective, the company expected to find that optimal team composition -- the right mix of skills, seniority, and personality types -- was the primary driver. Project Aristotle, as the two-year internal research initiative was named, analysed 180 Google teams and found something different. Who was on the team mattered far less than how the team worked together. The single most important factor distinguishing high-performing teams from the rest was psychological safety: the shared belief among team members that the team is safe for interpersonal risk-taking. Not trust in the abstract, but the specific, felt confidence that speaking up with a question, concern, mistake, or half-formed idea will not result in punishment or humiliation. Amy Edmondson, the Harvard Business School professor who originated the concept, had been studying it for over a decade before Google's data confirmed its primacy. The finding carries particular weight for startups, where the margin for error is thin, the information environment is ambiguous, and the consequences of silence -- unvoiced concerns, unraised objections, unreported failures -- can be existential. + +--- + +## The Framework + +### What Psychological Safety Is (and Is Not) + +Edmondson is precise about the boundaries of the concept. Psychological safety is not: + +- **Niceness.** Teams with high psychological safety can have fierce debates. The difference is that the fierceness targets ideas, not people. +- **Lower standards.** Psychological safety does not mean reducing accountability. It means creating conditions where people can be honest about problems, which is a prerequisite for genuine accountability. +- **Unconditional agreement.** The point is not that everyone feels comfortable all the time. The point is that discomfort comes from intellectual challenge, not from fear of retaliation. + +Psychological safety is the group-level belief that candour will not be punished. It exists on a spectrum, and it is remarkably fragile -- a single incident of public humiliation can destroy months of trust-building. + +### The Four Stages of Psychological Safety + +Timothy Clark, building on Edmondson's work, proposed a developmental model: + +1. **Inclusion safety** -- Members feel accepted and that they belong. The baseline: "I am welcome here." +2. **Learner safety** -- Members feel safe to ask questions, experiment, and make mistakes in the process of learning. "I can be a beginner without being diminished." +3. **Contributor safety** -- Members feel safe to apply their skills and contribute meaningfully. "My input is valued and sought." +4. **Challenger safety** -- Members feel safe to challenge the status quo, question decisions, and push back on authority. "I can disagree with leadership without career risk." + +Most organisations achieve inclusion and learner safety reasonably well. Contributor safety is common in healthy cultures. Challenger safety -- the stage that produces the highest-value outcomes -- is rare. It is also the stage that matters most for startups, where the founder's conviction can create a reality distortion field that discourages dissent precisely when dissent is most needed. + +### Edmondson's Leader Toolkit + +Edmondson identifies specific leadership behaviours that build (and erode) psychological safety: + +**Behaviours that build:** +- Framing work as a learning problem, not an execution problem +- Acknowledging own fallibility ("I may miss something; I need your input") +- Modelling curiosity by asking genuine questions +- Responding to bad news with inquiry, not blame +- Acknowledging and thanking people who raise concerns +- Setting explicit norms about how failure is discussed + +**Behaviours that erode:** +- Punishing the messenger (even subtly -- a sigh, an eye-roll, a dismissive "We've already considered that") +- Making decisions in advance and using meetings to ratify rather than deliberate +- Publicly identifying individuals as responsible for failures +- Responding to mistakes with "Who did this?" rather than "What can we learn?" +- Praising only success and ignoring the learning embedded in failure + +### Measuring Psychological Safety + +Edmondson developed a seven-item survey instrument that remains the standard diagnostic: + +1. If you make a mistake on this team, it is often held against you. (Reverse scored) +2. Members of this team are able to bring up problems and tough issues. +3. People on this team sometimes reject others for being different. (Reverse scored) +4. It is safe to take a risk on this team. +5. It is difficult to ask other members of this team for help. (Reverse scored) +6. No one on this team would deliberately act in a way that undermines my efforts. +7. Working with members of this team, my unique skills and talents are valued and utilised. + +--- + +## Prompts + +**Prompt 1 -- Psychological Safety Diagnostic:** +> Based on the following observations about my team's behaviour, assess our likely level of psychological safety across Clark's four stages (inclusion, learner, contributor, challenger). Observations: [describe how team members behave in meetings, how bad news is delivered, how disagreements unfold, how mistakes are handled, whether junior members speak up]. For each stage, rate us as weak/developing/strong and provide the specific evidence from my observations that supports the rating. + +**Prompt 2 -- Incident Recovery Plan:** +> An incident just occurred that may have damaged psychological safety on my team: [describe what happened -- e.g., a team member was publicly criticised, a mistake led to visible blame, someone's idea was dismissed harshly]. Design a recovery plan: (a) immediate actions within 24 hours, (b) what I should say to the affected individual privately, (c) how to address the team without making it worse, and (d) systemic changes to prevent recurrence. Script the specific language for each conversation. + +**Prompt 3 -- Meeting Redesign for Candour:** +> Our team meetings currently suffer from [describe symptoms: silence from junior members, ideas only coming from senior people, no pushback on proposals, "agree in the room and disagree in the corridor" pattern]. Redesign our weekly team meeting format to maximise psychological safety and genuine candour. Include specific structural elements (e.g., anonymous input mechanisms, round-robin formats, pre-meeting reflection), facilitation techniques, and ground rules. Tailor the design for a team of [size] at [stage]. + +**Prompt 4 -- Founder Self-Assessment:** +> Evaluate my leadership behaviours for their impact on psychological safety. Here is how I typically respond to: (a) bad news: [describe], (b) disagreement: [describe], (c) mistakes: [describe], (d) questions that challenge my assumptions: [describe], (e) silence in meetings: [describe]. Rate each response on Edmondson's scale and recommend specific behavioural changes. Be direct -- this is precisely the kind of candid assessment I am trying to model for my team. + +--- + +## Use Cases + +**Early-traction startup where the founder is the bottleneck** + +A 12-person startup has a technically brilliant founder who inadvertently suppresses psychological safety through a specific behavioural pattern: she asks probing questions about every proposal, and her questioning -- while intellectually rigorous -- is experienced by the team as interrogation. The result: team members pre-filter ideas, only bringing forward those they believe will survive the founder's scrutiny. Innovation narrows to a single funnel. The diagnostic reveals strong inclusion and learner safety but weak contributor and challenger safety. The intervention is surgical: the founder learns to separate inquiry from evaluation by prefacing questions with "I'm asking because I want to understand, not because I'm challenging." She also implements a practice of sharing her own half-formed ideas first, modelling that incomplete thinking is legitimate. Within three months, the team's proposal pipeline triples. + +**Scale-stage company with a "no bad news" culture** + +A 500-person company discovers during a post-mortem that a critical product failure was foreseeable -- three engineers had identified the risk weeks earlier but chose not to escalate. Investigation reveals a cultural pattern: the company celebrates "can-do" attitudes and implicitly penalises those who raise obstacles. Middle managers filter bad news before it reaches leadership because they have learned that bearing bad news harms their standing. The CEO implements Edmondson's framework at the organisational level: establishing anonymous escalation channels, publicly praising employees who surface problems early, and creating a "risk radar" ritual in leadership meetings where the explicit purpose is to identify what could go wrong. The transformation takes 12-18 months but produces a measurable reduction in preventable failures. + +**Growth-stage remote team struggling with asynchronous candour** + +A fully distributed startup finds that psychological safety is easier in synchronous video calls (where tone and expression provide context) but deteriorates in asynchronous written communication (Slack, email), where messages are more likely to be interpreted as blunt, dismissive, or critical. The company develops explicit norms for asynchronous communication: a "draft and re-read" protocol for sensitive messages, an explicit emoji-free notation system for tone (e.g., prefixing messages with "[genuine question]" or "[thinking out loud]"), and weekly synchronous sessions dedicated to relationship maintenance rather than task execution. + +--- + +## Anti-Patterns + +**1. Declaring psychological safety without building it.** Announcing "this is a safe space" in a meeting does nothing -- and may actively harm safety if team members' lived experience contradicts the declaration. Psychological safety is demonstrated through consistent behaviour over time, not proclaimed in a single statement. + +**2. Confusing psychological safety with conflict avoidance.** Teams with genuine psychological safety have more productive conflict, not less. If introducing the concept leads to people being even more reluctant to disagree ("we need to be safe with each other"), the implementation has failed. The goal is to make disagreement safer, not to eliminate it. + +**3. Expecting immediate results after a single intervention.** Psychological safety is built through hundreds of micro-interactions over months. A single well-intentioned meeting or workshop does not undo years of punitive culture. Leaders who expect instant transformation become disillusioned and abandon the effort, which confirms the team's suspicion that the initiative was performative. + +**4. Holding everyone accountable for safety except the founder/CEO.** Psychological safety is set at the top. If the most senior person in the room does not model vulnerability, curiosity, and openness to challenge, no amount of team-level work will compensate. The single highest-leverage action is the founder's behaviour, not the team's training. + +**5. Using psychological safety surveys without acting on results.** Conducting Edmondson's diagnostic and then failing to address the findings it surfaces is worse than never conducting it. The survey itself raises expectations of change; unmet expectations erode trust further. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founding team dynamics, first hires | Safety is personal and direct; the founder's daily behaviour IS the safety level | +| Growth | Middle management layer, remote/hybrid dynamics | Safety must scale through delegation; managers become the primary safety-setters for their teams | +| Scale | Organisational culture, cross-functional dynamics | Safety becomes a systems problem requiring structural solutions (anonymous channels, formal feedback mechanisms, cultural metrics) | + +At early traction, psychological safety is entirely personal. In a five-person team, every interaction between the founder and each team member directly builds or erodes safety. The founder who responds to a junior developer's bug report with gratitude ("Thank you for catching this early") versus irritation ("How did this get through?") sets the entire team's willingness to surface problems. + +At growth, the founder cannot personally maintain safety across 50 or 100 people. The critical transition is equipping managers to be safety-builders. This requires explicit training (most first-time managers have never thought about psychological safety), modelling from above (managers will treat their teams the way leadership treats them), and measurement (including safety in manager evaluations). + +At scale, psychological safety becomes an architectural challenge. Cross-functional teams, distributed workforces, matrix organisations, and acquired companies all present structural obstacles to interpersonal trust. The solutions become correspondingly structural: anonymous escalation systems, ombudsperson roles, cultural health metrics in leadership dashboards, and deliberate investment in the kind of relational infrastructure that small teams get for free. + +--- + +## Output Template + +```markdown +# Psychological Safety Assessment -- [Team Name] + +**Prepared for:** Team Lead / Founder +**Date:** [Date] +**Team size:** [N] +**Assessment method:** [Observation / Survey / Interviews] + +## Four-Stage Assessment + +| Stage | Rating | Evidence | Priority Action | +|-------|--------|----------|----------------| +| Inclusion Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Learner Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Contributor Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | +| Challenger Safety | [Weak/Developing/Strong] | [Specific observations] | [Action] | + +## Behavioural Patterns Observed + +| Behaviour | Frequency | Impact on Safety | Classification | +|-----------|-----------|-----------------|----------------| +| [Specific behaviour] | [Often/Sometimes/Rarely] | [Builds/Erodes] | [Which stage affected] | + +## Leader Behaviour Audit + +| Edmondson Behaviour | Current Practice | Recommendation | +|--------------------|-----------------|----------------| +| Framing as learning problem | [Current] | [Change needed] | +| Acknowledging fallibility | [Current] | [Change needed] | +| Modelling curiosity | [Current] | [Change needed] | +| Responding to bad news | [Current] | [Change needed] | +| Thanking those who raise concerns | [Current] | [Change needed] | + +## 90-Day Safety Building Plan +**Month 1:** [Foundation -- specific rituals and norms to establish] +**Month 2:** [Practice -- specific behaviours to reinforce and measure] +**Month 3:** [Assessment -- re-measure and adjust] + +## Risk Indicators to Monitor +- [Signal that safety is declining -- e.g., decreased questions in meetings] +- [Signal that safety is declining -- e.g., increased corridor conversations] +- [Signal that safety is improving -- e.g., mistakes reported earlier] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's empathy and self-regulation domains are the individual competencies that leaders must develop to create psychologically safe environments. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework is the mindset complement to Edmondson's structural model; psychological safety is the environment in which growth mindset can operate, and growth mindset is the orientation that makes psychological safety productive. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Radical Candor depends on psychological safety as its foundation; without the shared belief that candor will not be punished, direct challenge registers as threat rather than care. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Pre-mortems and bias audits, which are System 2 tools, require psychological safety to function; people will not voice dissenting analysis in an unsafe environment. +- **[Psychological Safety Practice](../../content/skills/leadership/psychological-safety-practice.md)** -- Translates Edmondson's academic framework into daily leadership behaviors and team rituals that build and sustain safety over time. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Psychological safety determines whether failures become learning opportunities or career-ending events; the two frameworks are mutually reinforcing. diff --git a/plugins/foreman/skills/purpose-driven-leadership/SKILL.md b/plugins/foreman/skills/purpose-driven-leadership/SKILL.md deleted file mode 120000 index 8b1e803..0000000 --- a/plugins/foreman/skills/purpose-driven-leadership/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/purpose-driven-leadership.md \ No newline at end of file diff --git a/plugins/foreman/skills/purpose-driven-leadership/SKILL.md b/plugins/foreman/skills/purpose-driven-leadership/SKILL.md new file mode 100644 index 0000000..593154b --- /dev/null +++ b/plugins/foreman/skills/purpose-driven-leadership/SKILL.md @@ -0,0 +1,196 @@ +--- +name: "purpose-driven-leadership" +description: "Helps leaders connect their work and their teams' work to authentic meaning, rethink outdated notions of dedication, anchor in purpose over perception, and lead with integrity as a continuous practice. Use when experiencing career malaise or questioning professional direction, noticing disengagement on a team, struggling to articulate why the work matters, preparing to realign team priorities around meaning, or sensing that performance metrics have crowded out purpose." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - purpose + - meaning + - authenticity + - dedication + - integrity + - motivation + - work-life + - values +related_skills: + - emotional-intelligence + - maslow-hierarchy + - covey-seven-habits + - emotional-courage + - humility-and-power +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Purpose-Driven Leadership + +At a funeral, no one reads the quarterly performance review. The eulogy test -- what would your team say you stood for? -- exposes a gap that most leaders spend entire careers avoiding. Not a gap in competence or results, but in meaning. Organisations are saturated with mission statements, value propositions, and strategic visions, yet the question "Why does this work matter?" remains surprisingly difficult for most leaders to answer with conviction. Purpose-driven leadership is not a motivational overlay applied to an otherwise mechanical job. It is the structural foundation that determines whether people bring discretionary effort or merely their contractual minimum. + +--- + +## The Framework + +### Dimension 1: Rethinking Dedication + +The industrial model of dedication -- measured in hours at the desk, weekends sacrificed, personal life deferred -- is obsolete. People no longer settle for jobs that consume their lives, and leaders who cling to this standard risk losing their best talent to organisations that have already moved on. + +Rethinking dedication requires three shifts: + +**Disconnect performance from time.** If work is getting done well, the number of hours spent should be irrelevant. A leader who equates presence with productivity is optimising for the wrong metric. The shift is from "How long did you work?" to "What did you produce?" + +**Expand the definition of ambition.** Ambition is not synonymous with career obsession. An employee who wants to excel at work and coach their child's football team is not less ambitious than one who works until midnight. They are pursuing a more complex ambition -- and one that, if supported, produces sustainable performance rather than burnout. + +**Release the standards of your own early career.** The conditions under which today's leaders came up are not the conditions they should impose. "I worked 80-hour weeks as a junior analyst" is biography, not policy. Every generation renegotiates the terms of professional dedication; resisting this renegotiation is a retention strategy for mediocrity. + +### Dimension 2: Making Purpose Felt, Not Declared + +Purpose is a feeling, not a statement. A mission printed on the conference room wall is inert. Purpose becomes operative when people experience the impact of their work -- when they feel it in the specificity of a customer's gratitude, the tangible improvement in someone's life, or the visible consequence of a problem solved. + +**Two principles for activating purpose:** + +**Show, don't tell.** Customer testimonials, site visits, direct conversations between engineers and the users of their products -- these create visceral connections between effort and impact. Telling a team their work is important triggers compliance at best and cynicism at worst. Showing them produces engagement. + +**Authenticity is non-negotiable.** If purpose rhetoric does not align with a leader's historical behaviour, it backfires. A leader who spent years emphasising quarterly profits cannot suddenly pivot to heartfelt speeches about customer impact without provoking suspicion. Authenticity in purpose-driven leadership is built over time through consistent alignment between words and actions. It cannot be manufactured in a single all-hands meeting. + +### Dimension 3: Purpose Over Perception + +A particularly corrosive form of purposelessness emerges when leaders begin managing perceptions rather than pursuing outcomes. The energy spent on appearing competent, appearing decisive, appearing dedicated is energy diverted from actually being those things. + +This trap is especially acute for leaders navigating identity-based expectations. Research on women in leadership, for instance, reveals that managing the perception of femininity -- softening here, hardening there, striking some elusive balance -- consumes time and cognitive resources that could be directed toward shared goals. The remedy is not to ignore perception entirely but to anchor in purpose so firmly that behaviour flows from conviction rather than from image management. + +Anchoring in purpose enables leaders to ask a more productive question: "Who do I need to be and what do I need to learn to achieve these goals?" rather than "How do I need to appear?" + +### Dimension 4: The Work-Life Equation + +Purpose extends beyond the office. Leaders who have no life outside work are not more dedicated; they are more fragile. A career that cannot coexist with personal fulfilment is unsustainable -- not in the abstract sense of "wellness culture" but in the concrete sense that it produces diminishing returns, impaired judgment, and eventual collapse. + +Taking stock requires honest inventory: + +- What do you want your days to look like -- not just your career trajectory? +- Ten years from now, what will you regret not having done or learned? +- Does your current path support the life you want, or only the career you think you should want? + +These are not soft questions. They are strategic ones. A leader operating from a place of personal clarity makes better decisions, models sustainable behaviour for their team, and avoids the slow erosion that turns high performers into hollow ones. + +### Dimension 5: Integrity as Ongoing Practice + +Integrity is not a credential earned once. It is a practice maintained daily and compromised incrementally. Leaders are role models whether they intend to be or not. Cutting corners, flouting rules, or ignoring top performers' bad behaviour grants permission for the entire organisation to do the same. + +The inverse is equally true. Leading with integrity -- consistently, visibly, especially when it is inconvenient -- creates a culture where ethical behaviour is the default rather than the exception. Customers, who increasingly care about how companies do business, respond to this signal. Employees, who watch their leaders more closely than leaders imagine, respond to it even more. + +Your life story is part of this equation. Authentic leadership draws on the full arc of experience -- mentors and micromanagers, promotions and layoffs, triumphs and humiliations. Leaders who understand where they come from, who can integrate their hardships into a coherent sense of purpose, are better equipped to lead with the kind of integrity that withstands pressure. + +--- + +## Prompts + +**Prompt 1 -- Purpose Audit:** +> Help me articulate my leadership purpose. My role is [describe], my team does [describe], and our organisation's mission is [describe]. I find meaning in [describe what energises you]. Walk me through a structured process to connect my daily work to a purpose statement that is honest, specific, and motivating -- not a generic mission statement but a personal conviction I can use as a decision-making filter. + +**Prompt 2 -- Team Purpose Activation:** +> My team of [size] seems disengaged. They do competent work but lack energy and initiative. I want to help them feel purpose in their work without resorting to motivational speeches that will trigger cynicism. Based on our work [describe what the team does and who it serves], suggest specific, concrete ways to make the impact of their work visible and felt -- not declared. + +**Prompt 3 -- Dedication Reset:** +> I suspect I am holding my team to outdated standards of dedication. The symptoms include [describe -- e.g., judging people who leave at 5 PM, feeling resentful when direct reports take full vacations, equating enthusiasm with long hours]. Help me redesign my mental model of dedication around output and impact rather than time and presence. Include specific behavioural changes I can make starting this week. + +**Prompt 4 -- Life-Work Alignment Check:** +> I am [X] years into my career. Help me conduct a life-work alignment audit. Ask me questions about what I want my days to look like, what I would regret not doing, and whether my current path supports the life I want. Then identify the gaps and suggest realistic adjustments -- not a dramatic career change, but shifts that move me closer to alignment. + +--- + +## Use Cases + +**Idea-Stage Founder Reconnecting with Why** + +A technical founder has spent eighteen months building a product and has lost sight of why they started. The daily reality is code reviews, investor updates, and hiring struggles. Purpose has been displaced by process. The founder applies the ten-year regret question and realises that what drew them to this problem -- a personal experience with the inefficiency they are solving -- has been buried under operational noise. They institute a monthly "customer story" session where the team hears directly from users. The founder's own energy returns, and the team -- previously executing without conviction -- begins to understand who they are building for and why it matters. + +**Growth-Stage Company with a Dedication Problem** + +A fast-growing consultancy has a cultural norm of 60-hour weeks, inherited from its founding partners. New hires tolerate it; experienced staff leave. Exit interviews consistently cite "unsustainable pace" as the primary reason for departure. The managing partner applies the dedication rethink: disconnecting performance evaluation from hours logged, explicitly endorsing flexible schedules for high performers, and publicly acknowledging that the partners' own early-career sacrifices were choices, not requirements. Within a year, attrition drops by 30% and billable output per person actually increases -- because people working sustainable hours make fewer mistakes and require less rework. + +**Scale-Stage Executive Facing an Integrity Test** + +A division president discovers that a top-performing sales director has been misrepresenting product capabilities to close deals. The short-term cost of intervention is significant: the sales director's accounts represent 15% of division revenue. The president applies the integrity-as-practice principle and terminates the sales director, communicating the reason transparently to the broader sales team. Short-term revenue dips. Long-term, the team's customer relationships improve as trust builds, and two previously silent team members report other issues they had been afraid to raise. The integrity signal cascades. + +--- + +## Anti-Patterns + +1. **Purpose as performance.** Crafting a personal purpose statement for LinkedIn or the company website without actually using it to make decisions. Purpose that does not influence behaviour is decoration. + +2. **Confusing purpose with passion.** Not every day feels meaningful. Purpose is a direction, not a mood. Leaders who expect to feel inspired every morning are confusing purpose with passion -- and will abandon purpose the first time it feels boring. + +3. **Imposing your purpose on your team.** A leader's personal sense of meaning does not automatically transfer to direct reports. Helping people find purpose means showing them impact and giving them autonomy to connect their own motivations to the work -- not lecturing them about why they should care. + +4. **The martyrdom trap.** Equating suffering with purpose. Working through illness, missing family milestones, and sacrificing health are not evidence of dedication; they are evidence of a broken relationship with work. Purpose-driven leaders sustain themselves because they intend to be in the work for the long term. + +5. **Integrity as a convenient stance.** Championing integrity when it costs nothing and abandoning it when it threatens revenue, relationships, or reputation. Integrity that bends under pressure is not integrity; it is risk management. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal purpose clarity | The founder's "why" is the company's "why" at this stage. If the founder cannot articulate purpose beyond "I want to build a company," the venture lacks a foundation for culture. | +| Validation | Purpose as a hiring signal | Early employees join for the mission, not the salary. Articulating purpose authentically is the most powerful recruiting tool at this stage. | +| Early Traction | Making purpose tangible for the first team | The transition from founder's vision to shared conviction happens here. Customer stories, impact metrics, and visible connections between effort and outcome are critical. | +| Growth | Scaling purpose without diluting it | New hires join who did not experience the founding story. Purpose must be embedded in onboarding, rituals, and decision-making frameworks rather than relying on oral tradition. | +| Scale | Integrity under institutional pressure | At scale, the pressures to compromise -- on ethics, on work-life standards, on stated values -- intensify. Purpose must be defended as deliberately as revenue targets are pursued. | + +--- + +## Output Template + +```markdown +# Purpose-Driven Leadership Assessment + +## Personal Purpose Statement +- **Core conviction:** [What you stand for as a leader -- one sentence] +- **Evidence of alignment:** [Three recent decisions that reflected this purpose] +- **Evidence of misalignment:** [Three recent decisions that contradicted it] + +## Team Purpose Health +| Indicator | Current State | Desired State | +|-----------|--------------|---------------| +| Can team members articulate why their work matters? | [Yes/Partially/No] | [Target] | +| Do team members experience the impact of their work directly? | [How often and how] | [Target] | +| Is purpose reflected in how work is assigned and evaluated? | [Description] | [Target] | + +## Dedication Model +- **Current model:** [Time-based / Output-based / Hybrid] +- **Symptoms of outdated standards:** [List specific behaviours] +- **Changes to implement:** [Specific shifts] + +## Integrity Audit +- **Last time integrity was tested:** [Describe the situation] +- **Response:** [What happened] +- **What it signalled to the organisation:** [Honest assessment] + +## Life-Work Alignment +- **What I want my days to look like:** [Description] +- **What my days actually look like:** [Description] +- **Gaps:** [Specific misalignments] +- **Adjustments:** [Realistic changes] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Self-awareness and empathy are preconditions for purpose-driven leadership; a leader who does not understand their own motivations cannot authentically connect others to meaning. +- **[Maslow's Hierarchy](../../content/skills/frameworks/maslow-hierarchy.md)** -- Purpose operates at the self-actualisation level; it becomes accessible only after lower-order needs (safety, belonging, esteem) are met. +- **[Covey's Seven Habits](../../content/skills/frameworks/covey-seven-habits.md)** -- "Begin with the end in mind" is the habit-level expression of purpose-driven leadership; Covey's framework provides the personal discipline structure that sustains purpose. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Living with integrity and anchoring in purpose when it is costly requires emotional courage that must be developed deliberately. +- **[Humility and Power](../../content/skills/leadership/humility-and-power.md)** -- Purpose without humility becomes messianism; the two disciplines are natural counterweights. +- **[Stoic Duty and Service](../../content/skills/stoic/stoic-duty-and-service.md)** -- The Stoic concept of duty as service provides the philosophical foundation for leading with purpose beyond personal ambition. +- **[AI Purpose-Driven Questions](../../content/skills/ai-leadership/ai-purpose-driven-questions.md)** -- Applies purpose-driven leadership specifically to AI adoption, ensuring technology decisions are guided by values rather than novelty. diff --git a/plugins/foreman/skills/radical-candor/SKILL.md b/plugins/foreman/skills/radical-candor/SKILL.md deleted file mode 120000 index e86de03..0000000 --- a/plugins/foreman/skills/radical-candor/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/radical-candor.md \ No newline at end of file diff --git a/plugins/foreman/skills/radical-candor/SKILL.md b/plugins/foreman/skills/radical-candor/SKILL.md new file mode 100644 index 0000000..cf0203a --- /dev/null +++ b/plugins/foreman/skills/radical-candor/SKILL.md @@ -0,0 +1,198 @@ +--- +name: "radical-candor" +description: "Applies Kim Scott's Radical Candor framework to improve feedback culture by balancing caring personally with challenging directly. Maps management behaviour across four quadrants: Radical Candor, Ruinous Empathy, Obnoxious Aggression, and Manipulative Insincerity. Use when preparing difficult performance conversations, diagnosing a culture of avoidance, training new managers on feedback, or addressing top-performer attrition caused by insufficient challenge." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - feedback + - management + - communication + - leadership + - culture +related_skills: + - giving-feedback + - trust-equation + - organisational-culture + - lean-in +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Radical Candor + +When Kim Scott joined Google and later became a director at Apple, she thought she was a good manager. Then Sheryl Sandberg pulled her aside after a presentation. "You said 'um' a lot," Sandberg told her. Scott brushed it off -- she had nailed the content, after all. Sandberg pressed: "I can see I'm going to have to be more direct with you. When you say 'um' every third word, it makes you sound stupid." Scott was stunned. And then she was grateful. No one had ever cared enough to be that blunt. She had given hundreds of presentations with that verbal tic, and every previous manager had been too "nice" to mention it. Sandberg's willingness to combine genuine personal concern with unfiltered directness became the seed of what Scott later formalised as Radical Candor -- a framework that has since reshaped how a generation of managers thinks about the relationship between kindness and honesty. + +The insight is deceptively simple: most management failures are failures of feedback, and most feedback failures stem from a false choice between being caring and being honest. Radical Candor rejects the choice entirely. + +--- + +## The Framework + +### The 2x2 Matrix + +Radical Candor maps management behaviour along two dimensions: + +- **Care Personally** (vertical axis): The degree to which you give a damn about the person as a human being -- not just as a producer of output. This is not about being friends; it is about acknowledging that work is performed by people with lives, fears, ambitions, and dignity. +- **Challenge Directly** (horizontal axis): The degree to which you tell people what you actually think -- especially when your assessment is unfavourable. Direct challenge means sharing your honest perspective, not softening it into meaninglessness. + +``` + HIGH CARE PERSONALLY + | + Ruinous | Radical + Empathy | Candor + "Too nice | "I care about you + to be honest" | AND I'll tell you + | the truth" + | + LOW ────────────────┼──────────────── HIGH + CHALLENGE | CHALLENGE + DIRECTLY | DIRECTLY + | + Manipulative | Obnoxious + Insincerity | Aggression + "Neither honest | "Brutal honesty + nor caring" | without caring" + | + LOW CARE PERSONALLY +``` + +### Quadrant 1: Radical Candor (High Care, High Challenge) + +The target quadrant. You care about the person enough to risk their temporary discomfort for their long-term growth. You challenge them directly because you respect them enough to be honest. Radical Candor is not a permanent state -- it is a direction you move toward, a practice you calibrate daily. + +**Characteristics:** +- Feedback is immediate, specific, and delivered privately for criticism, publicly for praise +- The manager solicits feedback on their own performance first, modelling vulnerability +- Criticism targets behaviour, not character +- The relationship carries enough trust that directness is received as investment, not attack + +### Quadrant 2: Ruinous Empathy (High Care, Low Challenge) + +The most common failure mode, particularly among well-intentioned managers. You care about the person -- genuinely -- but you avoid telling them hard truths because you do not want to hurt their feelings. The result: problems compound, performance declines, and when the inevitable reckoning arrives (a PIP, a firing), the employee is blindsided. "Why didn't anyone tell me?" is the epitaph of Ruinous Empathy. + +Scott estimates that roughly 85% of management mistakes fall into this quadrant. The damage is severe precisely because the intention is benign. + +### Quadrant 3: Obnoxious Aggression (Low Care, High Challenge) + +The stereotypical "tough boss." Brutally honest, but the honesty serves the manager's ego rather than the employee's development. Feedback is delivered without concern for how it lands, often publicly, sometimes cruelly. The saving grace of this quadrant -- compared to the others -- is that at least people know where they stand. Scott argues that Obnoxious Aggression, while unpleasant, is less destructive than Ruinous Empathy because the information still flows. + +### Quadrant 4: Manipulative Insincerity (Low Care, Low Challenge) + +The worst quadrant. Neither honest nor caring. Manifests as political manoeuvring, passive-aggression, insincere praise, and backstabbing. People in this quadrant tell you what you want to hear to your face and something entirely different behind your back. Organisations dominated by this quadrant are characterised by dysfunction, mistrust, and talent flight. + +### The Order of Operations + +Scott prescribes a specific sequence for building Radical Candor into your practice: + +1. **Solicit criticism before giving it.** Ask your team to tell you what you are doing wrong. Listen without defending. Thank them. Act on what you hear. This builds the trust that makes your subsequent criticism receivable. +2. **Praise specifically and sincerely.** Not "great job" but "the way you restructured the data pipeline reduced our processing time by 40%, and the documentation you wrote means anyone can maintain it." Specific praise demonstrates that you pay attention. +3. **Criticise kindly, clearly, and immediately.** Do not save feedback for quarterly reviews. Deliver it within hours, not weeks. Be specific about the behaviour. Explain the impact. Offer to help. + +--- + +## Prompts + +**Prompt 1 -- Quadrant Self-Assessment:** +> Analyse my recent management behaviour using the Radical Candor framework. Here are five recent feedback interactions I have had with my team: [describe each briefly -- what the situation was, what you said, how you said it, what happened]. For each, identify which quadrant I was operating in and why. Then identify my default quadrant and provide a specific plan for moving toward Radical Candor. + +**Prompt 2 -- Difficult Conversation Design:** +> I need to give critical feedback to [describe the person and their role]. The issue is [describe the performance or behaviour problem]. I care about this person's growth and want to maintain the relationship, but I have been avoiding this conversation. Using the Radical Candor framework, help me prepare: What should I say? How should I open? What specific behaviour should I name? How do I convey both challenge and care simultaneously? Script the key moments of this conversation. + +**Prompt 3 -- Culture Installation:** +> I want to build a Radical Candor culture across my company of [size] people. Currently, our culture defaults to [describe -- e.g., Ruinous Empathy, political, conflict-avoidant]. Design a 90-day programme to shift toward Radical Candor, including: leadership behaviour changes, team rituals, feedback mechanisms, and training elements. Specify how to handle resistance and how to measure progress. + +--- + +## Use Cases + +**Early-Traction Startup with a Underperforming Cofounder** +A technical cofounder is brilliant at architecture but consistently misses sprint commitments, demoralising the small engineering team. The CEO (the other cofounder) has been operating in Ruinous Empathy -- praising the technical vision while quietly picking up the slack. Applying Radical Candor, the CEO schedules a one-on-one and opens by soliciting criticism of their own leadership first. Then, clearly and specifically: "In the last three sprints, you committed to X and delivered Y. The team sees this, and it's eroding their trust. I'm telling you because I believe in your ability to fix it, and because the alternative -- letting this slide -- ends with us losing the team." The conversation produces a concrete plan with weekly check-ins. + +**Growth-Stage Company with a "Nice" Culture That Cannot Retain Top Performers** +A 90-person company with a warm, supportive culture consistently loses its highest performers within 12-18 months. Exit interviews reveal a pattern: top performers feel under-challenged and under-recognised. The culture's dominant quadrant is Ruinous Empathy -- everyone is pleasant, but hard truths never surface. The CEO introduces Radical Candor through a three-phase approach: first, publicly soliciting criticism of their own leadership at an all-hands; second, training all managers on the 2x2 matrix with role-play exercises; third, implementing weekly "candor check-ins" where each team member shares one piece of critical feedback and one piece of specific praise. + +**Scale-Stage Company Dealing with an Obnoxiously Aggressive VP** +A VP of Engineering at a 300-person company delivers results but leaves a trail of demoralised engineers. Turnover in their division is three times the company average. The VP believes they practice Radical Candor ("I tell people the truth"). Applying the framework precisely, HR and the CEO demonstrate that the VP's behaviour maps to Obnoxious Aggression: high challenge, low care. The intervention is not to soften the VP's directness but to develop the "Care Personally" dimension -- through executive coaching focused on curiosity, empathy, and understanding each report's career aspirations before delivering criticism. + +--- + +## Anti-Patterns + +1. **Using Radical Candor as a License for Cruelty.** The most dangerous misapplication: "I'm just being radically candid" deployed to excuse harsh, ego-driven, or poorly timed feedback. If the other person does not experience your criticism as caring, you are not practicing Radical Candor regardless of your intention. Impact trumps intent. + +2. **Skipping the "Solicit Criticism First" Step.** Leaders who jump straight to giving critical feedback without first demonstrating vulnerability by asking for criticism of themselves. The sequence matters. Trust must precede challenge. + +3. **Calibrating Only Once.** What feels like Radical Candor to one person may feel like Obnoxious Aggression to another. Cultural background, personality, seniority, and relationship history all affect how directness is received. The framework requires constant recalibration per person, not a single universal setting. + +4. **Praising Only in Private.** Scott's framework specifies that praise should be public (to reinforce desired behaviour visibly) and criticism should be private (to preserve dignity). Reversing this -- praising privately and criticising publicly -- is a recipe for fear-based culture. + +5. **Treating the 2x2 as a Personality Test.** Radical Candor describes behaviour, not people. Everyone moves between quadrants situationally. The goal is to spend more time in Radical Candor and less time in the other three -- not to label individuals as permanently occupying one quadrant. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Cofounder feedback norms | At the founding stage, the Radical Candor relationship between cofounders sets the template for the entire company's feedback culture. Establishing this early prevents the accumulation of unspoken resentments that fracture founding teams. | +| Growth | Manager training | As the company adds management layers, each new manager must learn the framework. The founder can no longer model candor to every individual; they must model it to managers who then model it to their teams. | +| Scale | Institutional mechanisms | At scale, Radical Candor cannot depend on individual managers' skill. It requires institutional supports: structured feedback processes, peer-review systems, 360-degree reviews designed around the framework, and explicit cultural reinforcement. | + +--- + +## Output Template + +```markdown +# Radical Candor Assessment: [Team/Company Name] + +## Dominant Quadrant Analysis +- **Leadership team default:** [Quadrant] +- **Middle management default:** [Quadrant] +- **IC-level default:** [Quadrant] +- **Evidence:** [Specific behavioural patterns observed] + +## Feedback Flow Audit +| Direction | Current State | Desired State | +|-----------|---------------|---------------| +| Leader → Team | [Description] | Radical Candor | +| Team → Leader | [Description] | Radical Candor | +| Peer → Peer | [Description] | Radical Candor | + +## Intervention Plan +### Phase 1: Model (Weeks 1-4) +- [Leader actions to solicit criticism and demonstrate vulnerability] + +### Phase 2: Train (Weeks 5-8) +- [Manager training, role-play, framework introduction] + +### Phase 3: Sustain (Weeks 9-12) +- [Rituals, processes, accountability mechanisms] + +## Key Conversations Needed +| Person | Issue | Quadrant Risk | Approach Notes | +|--------|-------|---------------|----------------| +| [Name] | [Issue] | [Likely pitfall] | [How to stay in Radical Candor] | + +## Metrics +- Employee engagement survey: feedback culture questions +- Retention rates, especially top performers +- Manager feedback quality scores (360 reviews) +``` + +--- + +## Related Skills + +- **[Giving Feedback (SBI Model)](../../content/skills/frameworks/giving-feedback.md)** -- SBI provides the tactical "how" of delivering feedback; Radical Candor provides the strategic "why" and the relational context. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the precondition for Radical Candor; without sufficient trust, directness registers as threat rather than investment. +- **[Organisational Culture](../../content/skills/frameworks/organisational-culture.md)** -- Feedback norms are a Layer 2 value sustained by Layer 3 assumptions; Radical Candor only takes root in cultures whose basic assumptions support psychological safety. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Edmondson's challenger safety is the organizational condition that enables Radical Candor to function; without it, direct challenge triggers defensive reactions rather than growth. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Moving from Ruinous Empathy to Radical Candor requires the emotional courage to sit with discomfort and deliver difficult truths despite the natural urge to avoid conflict. +- **[Writing Performance Reviews](../../content/skills/writing/writing-performance-reviews.md)** -- Performance reviews are the formal venue where Radical Candor principles must be applied with precision; vague written feedback is the documentary equivalent of Ruinous Empathy. diff --git a/plugins/foreman/skills/reader-psychology/SKILL.md b/plugins/foreman/skills/reader-psychology/SKILL.md deleted file mode 120000 index 0a5828b..0000000 --- a/plugins/foreman/skills/reader-psychology/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/reader-psychology.md \ No newline at end of file diff --git a/plugins/foreman/skills/reader-psychology/SKILL.md b/plugins/foreman/skills/reader-psychology/SKILL.md new file mode 100644 index 0000000..c0c241f --- /dev/null +++ b/plugins/foreman/skills/reader-psychology/SKILL.md @@ -0,0 +1,205 @@ +--- +name: "reader-psychology" +description: "Teaches the cognitive science behind how busy readers actually process written communications. Covers working memory limits, the F-pattern scanning behaviour, selective attention, and the four-stage triage process readers apply to every message. Use when diagnosing why communications fail to land, designing high-stakes messages for distracted audiences, auditing existing copy for cognitive overload, or training a team to write with the reader's brain in mind." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - cognitive-science + - attention + - reading-behaviour + - working-memory + - F-pattern + - busy-readers + - communication +related_skills: + - writing-for-navigation + - writing-for-response + - writing-effective-emails + - clarity-and-concision + - tone-and-engagement +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Reader Psychology + +F-PATTERN. Eye-tracking research reveals that readers do not read -- they scan in an F shape, spending most attention on the first two lines and the left margin. Everything else is a gamble. Psychologist George Miller's landmark study established that human working memory holds approximately seven items, plus or minus two, at any given moment. Between that hard cognitive ceiling and the 121 emails the average manager receives daily, the arithmetic is unforgiving: every sentence a writer produces competes against a reader's finite neural budget. Understanding that budget -- its size, its depletion rate, its failure modes -- is the prerequisite for writing that actually gets through. + +--- + +## The Framework + +### The Busy Brain: Three Constraints + +The limited capacity of the human attention system produces three consequences that shape every act of reading. + +**Constraint 1: We Cannot Process Everything in Front of Us** + +At any moment, the brain confronts more information than it can absorb. Its attention system responds by acting as a filter -- selecting what to notice and suppressing the rest. A 1999 Harvard study demonstrated this vividly: when participants were asked to count basketball passes in a video, nearly half failed to notice a person in a gorilla costume strolling through the scene. The brain's suppression of irrelevant stimuli is so aggressive that even conspicuous objects vanish when they fall outside the current focus. For writers, the implication is stark: information that is present in a message but not actively foregrounded may as well not exist. + +**Constraint 2: Focus Exhausts Quickly** + +Directing attention is effortful, and the resource depletes faster than most people assume. In a study by psychologist Brandon Schmeichel, participants who spent six minutes resisting the urge to look at flashing words on screen subsequently scored 20% lower on a graduate-level reading comprehension test. Six minutes of attentional control was enough to measurably impair later cognitive performance. Physical fatigue compounds the effect -- athletes under physical exhaustion show impaired attention and decision-making, and information scientist Gloria Mark found that workers need an average of 23 minutes to fully return to a task after a single interruption. One study estimated that minds wander a full third of the time while people attempt to read, with the rate climbing further when the material is complicated. + +**Constraint 3: Multitasking Fails** + +Strictly speaking, the brain cannot think about two tasks simultaneously. What people call "multitasking" is rapid task-switching, and it is cognitively expensive. A study at Butler University and Eli Lilly found that pharmacists asked to answer questions while filling prescriptions took longer and made substantially more errors. US government statistics attribute thousands of road deaths each year to texting while driving -- yet by some estimates, 22% of drivers report doing it daily. The Latin writer Publilius Syrus captured the principle in the first century BCE: "To do two things at once is to do neither." Modern survey data confirms that 63% of professionals report regularly working on two or three tasks simultaneously -- and modern research confirms they are worse at all of them when they do. + +The Stroop effect offers a vivid demonstration. When participants are asked to name the formatting applied to a word (e.g., say "bold" when they see the word "italicise" printed in bold), performance collapses. The brain cannot suppress the automatic reading of the word while simultaneously identifying the formatting -- two trivially simple tasks that become agonising in combination. The relevance for writers: any message that requires the reader to hold one piece of information in mind while processing a second is exploiting a cognitive capacity that barely exists. + +### How Readers Triage: The Four-Stage Filter + +Every time a reader encounters a written communication -- even a text message or a Slack notification -- they pass through four rapid, often unconscious decisions. + +| Stage | Question the Reader Asks | What Determines the Answer | +|-------|--------------------------|---------------------------| +| 1. Whether to engage | "Is this worth my time?" | Sender recognition, subject line, apparent length. In surveys, working professionals estimate they delete roughly half their emails without reading them. | +| 2. When to engage | "Now or later?" | Perceived effort. In one survey, 99% of professionals said they would respond first to the message that appeared easier. People prefer easy tasks now and defer hard tasks to "later" -- and "later" frequently means "never." | +| 3. How to engage | "Read closely, skim, or scan?" | Expected utility per second. Nearly 40% of emails and 20% of text messages are skimmed. Readers maximise information extraction while minimising time spent. | +| 4. Whether to respond | "Is the requested action worth the cost?" | Clarity of the request, ease of compliance, and perceived importance. Even willing readers fail to act when the steps are unclear or burdensome. | + +The preference for easy, short messages is not laziness -- it is a hardwired bias toward present-moment gratification. MRI research shows that limbic reward regions activate when the brain considers desirable outcomes available now, but remain largely dormant for outcomes deferred to the future. A classic experiment found that most people prefer $100 today over $101 in a week, despite the latter representing a 68% annualised return. A survey of the book's own participants revealed that respondents would rather sit in traffic for 31 minutes a week from now than 30 minutes right now -- paying an extra minute of misery for the privilege of deferring. The same bias applies to reading: if a message looks like it will be an unpleasant slog, the reader will push it off until "later," which, for practical purposes, means never. + +This temporal myopia shapes not just whether people read but what they read first. When presented with a mix of easy and hard tasks, people consistently tackle the easy ones first -- even when offered financial incentives to prioritise the hard ones. The implication for writers: your message is not competing solely against other messages. It is competing against every easier, more pleasant alternative in the reader's immediate environment. + +### How Readers Actually Read: Skimming, Scanning, and the F-Pattern + +Eye-tracking studies reveal a consistent scanning pattern across web pages, emails, and documents. Readers fixate most heavily on the first two lines, then scan down the left margin, occasionally darting rightward -- forming the shape of the letter F. Anchor points that attract fixation include headings, first sentences of paragraphs, visually contrasting elements (bold text, bullet points), and images. Text that falls outside these anchor points is routinely skipped. + +Psychologists Keith Rayner and Monica Castelhano mapped the difference between close reading and skimming: during close reading, the eyes move word by word in sequence; during skimming, fixations drop sharply and the eyes jump across entire lines. Since busy readers default to skimming, any information not positioned at a natural anchor point is statistically unlikely to be absorbed. + +Scanning is the companion strategy to skimming. Where skimming moves linearly but fast, scanning involves jumping between sections of a text, guided by selective attention and rules of thumb about where valuable information is most likely to reside. Readers often expect the first sentence of a paragraph to orient them to the rest of it. They spend more time on those opening sentences and use them to decide whether to read, skim, or skip what follows. Headings serve the same function at a higher structural level: readers use them as a table of contents for the document, zooming into sections that seem relevant and bypassing the rest entirely. + +The combined effect is sobering. In surveys conducted by the researchers, participants reported skimming nearly 40% of their emails and 20% of their text messages. These are not long-form documents -- they are the shortest, most urgent forms of written communication available. If readers skim a two-paragraph email, the probability that they will closely read a five-page memo is negligible without deliberate navigational architecture. + +A Carnegie Mellon study found that being interrupted by a phone call while taking a reading test decreased performance by 20%. The modern workplace is essentially a continuous interruption environment. The effective writer designs for this reality rather than against it -- placing critical information at the anchor points where even a scanning, distracted, cognitively depleted reader will land. + +### The Distracted Driver Analogy + +The book's authors draw a useful parallel between busy reading and distracted driving. Most adults are experienced drivers and experienced phone-talkers -- both tasks are individually routine. Yet psychologists have suggested that talking on the phone while driving has as bad an effect on performance as being legally drunk. The explanation returns to the attention system: even two well-practised tasks compete for the same finite cognitive bandwidth when performed simultaneously. Reading a work email while mentally preparing for a meeting, while a Slack notification pulses in the peripheral vision, creates an analogous collision. The reader is not stupid or careless. The reader is a cognitive system operating at capacity, and the writer who fails to account for that capacity is the one whose message gets lost. + +### The Writer's Blind Spot + +Writers systematically overestimate how much of their message readers will consume. This is a variant of the "curse of knowledge" -- having written every word, the writer assumes the reader will encounter every word. The data says otherwise. Readers skip paragraphs, jump backward to find missed details, and abandon messages mid-sentence when the expected value of the next second of reading drops below the value of doing something else. + +A Pew Research Center survey found that 60% of US adults -- and 74% of parents -- report feeling too busy to enjoy life at least some of the time. The writers' own surveys corroborate the figure: 60% of respondents said they often do not have enough time to get everything done in a typical month. Against that backdrop of chronic time scarcity, the writer's job is not to produce comprehensive text but to survive a brutal triage process. The writing that gets through is the writing that respects the reader's constraints -- not the writing that tests them. + +--- + +## Prompts + +**Prompt 1 -- Cognitive Load Audit:** +> Analyse the following message as though you are a busy reader with seven-plus-or-minus-two working memory slots and a strong bias toward skimming. Identify: (a) where the reader's F-pattern scan would likely fixate, (b) what information would be missed during a five-second skim, and (c) which elements create unnecessary cognitive load. Then suggest specific revisions. Message: [paste text] + +**Prompt 2 -- Triage Simulation:** +> Imagine you are a [describe recipient: e.g., Series A investor reviewing 40 pitch emails per day]. Walk through the four-stage reader triage for the following message: (1) Would you engage? (2) Would you engage now or later? (3) Would you skim or read closely? (4) Would you respond? At each stage, explain what would tip the decision, and flag where the message fails. Message: [paste text] + +**Prompt 3 -- Attention Budget Calculator:** +> I need to communicate [describe content] to [describe audience]. Estimate the reader's likely attention budget in seconds, based on the medium ([email/Slack/memo]), the sender-recipient relationship, and the perceived urgency. Then help me restructure the message so that the highest-priority information lands within the first 30% of that budget. + +**Prompt 4 -- Distracted Reader Stress Test:** +> Rewrite the following message so it survives the "distracted driver" test: a reader who is simultaneously managing three other tasks, has been interrupted twice in the last ten minutes, and will give this message no more than fifteen seconds. Preserve all essential content but restructure for maximum absorption under minimal attention. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Writing a Cold Investor Email** + +A fintech founder sends a two-paragraph email to a target angel investor. The first paragraph opens with three sentences of personal background. The second contains the ask -- a 20-minute call to discuss a payments API. Eye-tracking logic predicts the investor's F-pattern scan will fixate on the first line (personal background, no hook), glance left-margin down the second paragraph, and likely disengage before reaching the ask buried in the final sentence. The investor, receiving 40 such emails daily, applies the Stage 1 triage almost instantaneously: sender unknown, subject line generic ("Quick intro"), opening sentence unremarkable. The email is closed within three seconds. + +Restructuring the email to lead with a single data point ("Card-present fraud costs US merchants $8.6B annually -- we reduce it by 40%") followed immediately by the ask ("Would you have 20 minutes this week?") places both elements squarely within the F-pattern's high-attention zone. The data point serves as visual contrast -- a number amid text -- which the selective attention system is primed to notice. The ask, arriving in the second sentence, lands before Stage 3 triage (how closely to read) can default to skimming. + +**Growth-Stage Company Redesigning Internal Announcements** + +A 200-person SaaS company notices that its weekly all-hands email, averaging 800 words, generates fewer than 15% click-throughs on embedded action items. An internal audit applies the four-stage triage model and discovers the problem at Stage 3: readers skim the dense paragraphs, and action items are buried in the middle of blocks of text with no visual differentiation. The company redesigns the email with a three-line summary at the top, bold headings for each section, and action items isolated in a single bulleted block at the end. Click-through rates rise to 38% within one month. The words did not change materially; their cognitive accessibility did. + +**Validation-Stage Startup Crafting a Product Onboarding Sequence** + +A health-tech startup discovers that 60% of new users abandon its onboarding flow at step three of five. Applying the working-memory constraint, the team realises that step three requires users to hold four distinct pieces of information simultaneously (account type, billing preference, notification settings, and data-sharing consent) -- exceeding Miller's 7 plus-or-minus 2 threshold when combined with the ambient cognitive load of navigating a new interface. Splitting step three into two screens, each requiring only two decisions, reduces abandonment by 35%. The lesson extends beyond product design: any written communication that asks the reader to hold multiple unrelated concepts simultaneously -- a board update that mixes financial results, hiring plans, and legal matters in a single paragraph -- is making the same architectural mistake. + +**Scale-Stage Company Testing Subject Lines at Volume** + +An e-commerce platform with 2 million email subscribers runs an A/B test on its weekly promotional newsletter. Version A uses a consistent subject line ("This Week's Deals"). Version B varies the subject line each week with specifics ("40% Off Kitchen Essentials -- Ends Thursday"). Open rates for Version B average 28% higher over a 12-week period. The F-pattern predicts this: the subject line is the first -- and often only -- element the reader's attention system evaluates during Stage 1 triage. A static subject line becomes background noise; a variable one forces the attention system to process it anew each time. + +--- + +## Anti-Patterns + +1. **The Completeness Fallacy.** Writing a message that contains every relevant detail, on the assumption that thoroughness equals effectiveness. The reader's attention budget does not expand to match the writer's ambition. A 1,200-word email that covers eight topics will, in practice, communicate fewer of them than a 300-word email that covers three -- because the latter will actually be read. + +2. **Burying the Lead in Paragraph Three.** Opening with context, pleasantries, or chronological backstory before stating the purpose. The F-pattern concentrates attention on the first two lines. Anything placed after an unremarkable opening is competing with the reader's impulse to move on, and the impulse usually wins. + +3. **Symmetric Emphasis.** Bolding, underlining, or highlighting five different items in a single message under the theory that all five are important. Research shows that formatting five sentences in a passage reduces the noticeability of any single formatted sentence compared to formatting just one. When everything is emphasised, nothing is. + +4. **Assuming the Reader Will Return.** Sending a dense message with the expectation that the reader will skim now and read closely later. The data on present-bias suggests otherwise: messages deferred to "later" are rarely revisited. If the reader does not absorb the key information on first contact, the probability of a second contact approaches zero. + +5. **Ignoring Medium-Specific Attention Norms.** Writing a 500-word Slack message or a three-sentence board memo. Each medium carries implicit expectations about length and density. Violating those expectations triggers an immediate cost-benefit recalculation in the reader's triage process -- usually unfavourably. Text messages are expected to be immediate and disposable. Emails are expected to be scannable within one screen. Memos are expected to carry structure. Matching the medium's norms is not a stylistic preference -- it is a prerequisite for surviving Stage 1 triage. + +6. **The Multitasking-Friendly Illusion.** Writing a message that requires the reader to cross-reference an attachment, a prior email, and an external link to fully understand the request. This design assumes the reader will perform three concurrent cognitive tasks. The Stroop effect, the gorilla experiment, and the pharmacist study all suggest otherwise. If the reader must assemble information from multiple sources, they will assemble none of it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cold outreach to strangers (investors, advisors, potential co-founders) | The reader has no prior relationship with the sender. Stage 1 triage ("Should I engage at all?") is the primary hurdle. Subject line and first sentence carry almost the entire burden of persuasion. | +| Validation | Investor updates, early customer communications, survey requests | Readers have some familiarity with the sender but limited patience. Stage 2 ("Now or later?") is the critical gate. Messages must signal low effort and high relevance to avoid being deferred indefinitely. | +| Early Traction | Client-facing emails, onboarding copy, support documentation | The reader base diversifies. Writers must account for varying attention budgets across personas -- a technical user may read closely, while an executive sponsor skims. Designing for the skimmer protects both audiences. | +| Growth | Internal communications at scale (all-hands, policy updates, process changes) | Message volume multiplies. Employees develop aggressive triage habits for internal email. Cognitive load audits of recurring communications (weekly updates, change notices) yield outsized returns. | +| Scale | Templated communications, automated sequences, brand-level messaging | Thousands or millions of readers, each with unique attention constraints. A/B testing of structural elements (subject lines, opening sentences, visual hierarchy) becomes a quantitative discipline grounded in the same cognitive science. | + +--- + +## Output Template + +```markdown +# Cognitive Load Audit: [Message / Communication Name] + +## Reader Profile +- **Audience:** [Who is the reader?] +- **Estimated attention budget:** [X seconds, based on medium and context] +- **Primary triage risk:** [Stage 1 / 2 / 3 / 4 -- where the message is most likely to fail] + +## F-Pattern Analysis +- **First-line content:** [What the reader sees first -- is it the right thing?] +- **Left-margin anchors:** [Headings, paragraph openers, bullet starts] +- **Dead zones:** [Content that falls outside fixation points] + +## Working Memory Load +- **Concurrent concepts required:** [Count of distinct ideas the reader must hold] +- **Exceeds 7 +/- 2 threshold?** [Yes / No] +- **Simplification options:** [How to reduce simultaneous cognitive demands] + +## Triage Survival Checklist +- [ ] Purpose is clear within the first two lines +- [ ] Key ask or takeaway survives a five-second skim +- [ ] No critical information is buried below the third paragraph +- [ ] Formatting highlights one (maximum two) focal points +- [ ] Message length matches the medium's attention norms +- [ ] A reader who stops at any point has still absorbed the most important content + +## Revised Message +[Restructured version of the communication, annotated with cognitive rationale] +``` + +--- + +## Related Skills + +- **[Writing for Navigation](../../content/skills/writing/writing-for-navigation.md)** -- Translates reader psychology into structural principles: BLUF placement, headings as signposts, and visual hierarchy that aligns with the F-pattern scan. +- **[Writing for Response](../../content/skills/writing/writing-for-response.md)** -- Addresses the fourth triage stage directly: how to make the requested action so frictionless that even a cognitively depleted reader follows through. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- Applies the six principles of email craft to the medium where triage behaviour is most ruthless: the inbox. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- Provides the sentence-level techniques for reducing cognitive load per unit of text. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Governs the emotional register that influences Stage 1 and Stage 2 triage decisions: whether the reader engages and whether they engage now. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's dual-process theory provides the cognitive science foundation for why readers default to System 1 scanning and how writers can design for both processing modes. diff --git a/plugins/foreman/skills/reading-people/SKILL.md b/plugins/foreman/skills/reading-people/SKILL.md deleted file mode 120000 index 563bcb9..0000000 --- a/plugins/foreman/skills/reading-people/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/reading-people.md \ No newline at end of file diff --git a/plugins/foreman/skills/reading-people/SKILL.md b/plugins/foreman/skills/reading-people/SKILL.md new file mode 100644 index 0000000..c61e3f4 --- /dev/null +++ b/plugins/foreman/skills/reading-people/SKILL.md @@ -0,0 +1,219 @@ +--- +name: "reading-people" +description: "Applies practical techniques for decoding what people actually mean beyond their words, through nonverbal communication, active listening, rapport micro-signals, bluff detection, and mirroring. Covers listening with eyes rather than ears, the 55/38/7 communication model, accepting rapport signals, reading dishonesty tells, and the mirroring technique that builds trust through verbal reflection. Use when preparing for high-stakes negotiations, conducting investor meetings, managing difficult client conversations, interviewing candidates, or diagnosing misalignment between what stakeholders say and what they mean." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - nonverbal-communication + - body-language + - active-listening + - mirroring + - negotiation + - rapport + - bluff-detection +related_skills: + - understanding-people + - meeting-the-right-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Reading People + +The claim that words account for only 7% of communication is exaggerated -- but the belief that they account for 100% is far more dangerous. + +Albert Mehrabian's 1967 research produced the famous 55/38/7 formula: 55% body language, 38% tone, 7% words. The study's conditions were narrow (single-word emotional statements), and the numbers should not be taken as universal law. What *should* be taken as universal law is the underlying insight: a substantial majority of what people communicate has nothing to do with the sentences they construct. Founders who listen only to words are reading a transcript when they should be watching a film. The investor who says "interesting" while leaning back with crossed arms is not interested. The hire who says "I'm excited" while avoiding eye contact is not excited. The customer who says "we'll think about it" while checking the time has already decided. + +Reading people is not mind-reading. It is pattern recognition -- the trained habit of observing behaviour that most professionals ignore because they were never taught to look. + +--- + +## The Framework + +Reading people operates through five interlocking skills, each progressively more difficult to master. + +### Skill 1: Stop Waiting to Talk + +The precondition for reading people is the ability to stop composing your next sentence while someone else is speaking. Most people do not listen; they queue their response. The internal experience feels like listening -- you are facing the speaker, you are nodding -- but the cognitive bandwidth allocated to comprehension is minimal because most of it is consumed by rehearsal. + +Gerald Bell of the Bell Leadership Institute prescribes the **Achiever Listening Position**: sit up straight, lean slightly forward, arms at your sides, eyes fixed on the speaker with the intensity of a child watching television. The physical posture forces cognitive engagement. When the mind wanders -- and it will -- the posture serves as an anchor to pull attention back to the speaker. + +The critical reframe: you are not listening with intent to respond. You are listening with intent to *understand*. The response will take care of itself once comprehension is genuine. + +### Skill 2: Listen with Your Eyes + +Once the mind is fully present, the next skill is to distribute attention beyond words. Seven channels of nonverbal communication carry the information that words omit. + +| Channel | What to Observe | Entrepreneurial Signal | +|---------|----------------|----------------------| +| **Facial expressions** | Micro-expressions of surprise, contempt, disgust, or delight that flash before the social mask reasserts itself | An investor's fleeting eyebrow raise when you mention a competitor reveals unexpected concern | +| **Posture and movement** | Open vs. closed stance, comfort vs. tension, leaning in vs. pulling away | A candidate who leans back when discussing team collaboration may be signalling introversion or resistance | +| **Gestures** | Hand movements, self-touching, fidgeting, pointing | A board member who touches her face repeatedly during a financial presentation may be masking discomfort with the numbers | +| **Eye contact** | Sustained vs. averted, blinking rate, direction of gaze | A cofounder who breaks eye contact when discussing equity split is flagging unresolved tension | +| **Touch** | Handshake firmness, duration, and placement; shoulder touch; arm grip | A weak handshake from a prospective partner may indicate low confidence in the deal or in themselves | +| **Proxemics (space)** | Physical distance, territorial behaviour, positioning relative to others | An investor who moves closer during your pitch is engaged; one who subtly increases distance is withdrawing | +| **Vocal qualities** | Pace, volume, pitch, hesitation, filler words | A customer whose speech accelerates when discussing budget is likely under pricing pressure | + +The key is to establish a **baseline** for each person before interpreting deviations. Someone who fidgets constantly is not bluffing -- they are a fidgeter. Reading people requires calibrating against their normal behaviour, not against some universal template. + +### Skill 3: Accept the Glass of Water + +Rapport is built through small, often invisible signals of acceptance and reciprocity. The glass-of-water principle captures one such micro-signal: when offered a beverage at the start of a meeting, always accept. + +The reasoning operates on two levels: + +- **Self-regulation.** Accepting the drink creates a moment of settling in, reduces physical discomfort (thirst, nerves), and provides a natural pause for observation before the substantive conversation begins. +- **Host validation.** Declining an offered drink -- however politely -- creates a micro-friction. The host's gesture of hospitality has been refused. This is a tiny event, but tiny events compound. Accepting the drink allows the host to feel competent in their role, which primes the interaction toward warmth. + +The glass-of-water principle extends beyond beverages. Every interaction contains micro-opportunities for acceptance: accepting a compliment gracefully rather than deflecting it, accepting a small favour rather than insisting on self-sufficiency, accepting an invitation to sit in a preferred chair. Each acceptance reinforces the rapport loop. Each refusal, however minor, introduces static. + +### Skill 4: Detect the Bluff + +Bluffing -- presenting a false position to extract a concession -- is common in business negotiations. Detection requires comparing the speaker's verbal content against their nonverbal baseline. + +**Bluff indicators (deviation from baseline):** + +- Face-touching or scratching that appears during the specific claim, absent during prior conversation +- Gaze aversion at the moment of the critical assertion +- Speech-pace acceleration or sudden formality ("To be perfectly honest..." is often a preamble to dishonesty) +- Physical fidgeting that intensifies during the negotiation's pressure point +- Vocal pitch increase -- stress compresses the vocal cords + +**The detection protocol:** + +1. Establish the person's baseline during low-stakes conversation (greetings, small talk, uncontested topics). +2. Note changes in nonverbal behaviour when the conversation moves to contested claims. +3. Identify whether the change correlates with a specific claim or negotiating position. +4. If indicators cluster around a particular statement, call the bluff -- not aggressively, but by declining to concede. "I understand your position. I'm not able to move on that, but I'm confident the value justifies the terms." + +Calling a bluff carries information value regardless of whether the other party was actually bluffing. If they were, you have saved money and learned something about their trustworthiness. If they were not, their genuine conviction will emerge in their response -- and you can adjust accordingly. + +### Skill 5: Mirror (The Technique That Sounds Absurd and Works Every Time) + +Mirroring -- repeating back someone's exact words, preceded by "I hear you saying" -- sounds like a kindergarten exercise. It is, in practice, one of the most powerful rapport-building techniques available. + +**Why it works:** Mirroring provides the speaker with irrefutable evidence that they have been heard. Not paraphrased, not interpreted, not redirected -- *heard*. The psychological experience of being truly heard is so rare in professional settings that when it occurs, it produces an immediate and often dramatic increase in trust and openness. + +**Execution rules:** + +1. **Repeat their exact words.** "I hear you saying you're frustrated with the timeline." Not "I understand you're upset about scheduling." Close paraphrases feel like interpretation. Exact repetition feels like comprehension. +2. **Emphasise the feeling words.** Mirroring "I'm worried we'll miss the deadline" should place vocal emphasis on *worried* and *miss*. The emotional content is what the speaker most needs reflected. +3. **Never follow with "but."** "I hear you saying you're worried about the timeline, but we're actually ahead of schedule" instantly negates the mirror. The word "but" erases everything that preceded it. If a response is necessary, pause after the mirror. Let the reflection settle. Then respond in a separate sentence. +4. **Care genuinely.** Robotic repetition is detected instantly. Mirroring requires authentic engagement with the speaker's emotional state. If you do not care, the technique will not merely fail -- it will damage trust. + +The deeper the emotional content of the original statement, the more powerful the mirror. Mirroring "I took the train to work today" has negligible impact. Mirroring "I'm scared we're going to lose our biggest client" can transform a relationship. + +--- + +## Prompts + +**Prompt 1 -- Pre-Meeting Reading Preparation:** +> I have a high-stakes meeting with [describe person, role, context]. Help me prepare a reading plan: (a) what baseline information should I gather in the first two minutes of small talk, (b) what specific nonverbal channels should I prioritise given the meeting format [in-person / video / phone], (c) what are the likely pressure points in the conversation where nonverbal deviations will be most informative, and (d) what mirroring opportunities am I likely to encounter? + +**Prompt 2 -- Bluff Detection Scenario:** +> A [counterparty description] has made the following claim during a negotiation: [describe the claim]. I observed the following nonverbal signals: [describe what you noticed]. Analyse whether these signals are consistent with bluffing, genuine conviction, or simple discomfort. Recommend a response strategy that tests the claim without damaging the relationship. + +**Prompt 3 -- Listening Audit:** +> Record my performance in a recent important conversation: [describe the conversation]. At what points did I stop listening to understand and start listening to respond? What nonverbal signals from the other person did I miss? Reconstruct the conversation with annotations showing where active listening and mirroring could have changed the outcome. + +**Prompt 4 -- Mirroring Script Design:** +> I anticipate a difficult conversation with [describe person and situation]. The other person is likely to express [describe expected emotional content]. Draft three mirroring responses I can use, ensuring each uses the person's likely exact language, emphasises the emotional words, and avoids the "but" trap. Include follow-up questions I can ask after each mirror to deepen understanding. + +--- + +## Use Cases + +**Validation-Stage Founder in Customer Discovery** + +A SaaS founder conducts ten customer-discovery interviews in a week. In the first five, she focuses exclusively on the words customers use, recording answers to her structured questions. In the second five, she applies the full reading framework: she establishes baseline behaviour during opening small talk, watches for posture changes when discussing pain points, notes where speech pace accelerates (indicating genuine frustration versus polite agreement), and mirrors customers' emotional language back to them. The second set of interviews yields three insights the first set missed entirely: one customer's claimed "minor annoyance" was accompanied by physical tension that indicated a significant pain point; another customer's enthusiastic verbal response was contradicted by a micro-expression of scepticism that, when explored through mirroring, revealed a pricing concern she had not planned to raise. The founder adjusts both the product roadmap and the pricing model based on information that words alone would have concealed. + +**Early-Traction CEO in Investor Negotiation** + +A founder receives a term sheet from a venture capital firm. During the negotiation call, the lead partner states that the proposed valuation is "firm" and that the fund "cannot go higher." The founder notes that the partner scratches his face during this statement and increases his speech pace -- deviations from his relaxed baseline during earlier discussion of the product. Rather than conceding, the founder mirrors: "I hear you saying the valuation is firm and the fund cannot go higher." The partner, feeling heard, elaborates -- revealing that the constraint is not the fund's valuation model but a specific partner's concern about the sector. The founder addresses the sector concern directly, and the valuation increases by 15% in the next conversation. + +**Growth-Stage CTO Managing a Departing Engineer** + +A senior engineer requests a "quick chat" about her career. The CTO reads the signals: the engineer has already accepted the invitation to sit, but her posture is tense, she declines the offered coffee (a rapport-refusal micro-signal), and she avoids eye contact during the opening small talk. Before the engineer speaks her first substantive sentence, the CTO has a hypothesis: this is a resignation conversation. He adjusts his listening posture to full Achiever mode, asks one open question, and mirrors every statement the engineer makes for the next ten minutes without offering a single counterargument. The engineer, feeling genuinely heard for what may be the first time in months, reveals that the issue is not compensation but a sense of isolation on a project. The CTO addresses the structural problem. The engineer stays. + +--- + +## Anti-Patterns + +1. **Armchair Body-Language Analysis.** Reading a single gesture in isolation and drawing a sweeping conclusion. Arms crossed can mean hostility, cold temperature, or habitual comfort. Reading people requires *clusters* of signals and *deviations* from baseline, not amateur semiotics applied to one data point. + +2. **Weaponising Mirroring.** Using mirroring as a manipulation technique to extract concessions rather than as a genuine listening tool. People can distinguish between being heard and being handled. Mirroring deployed without authentic care produces an uncanny-valley effect that destroys trust faster than not mirroring at all. + +3. **Over-Reading Video Calls.** Applying the full nonverbal framework to Zoom calls, where camera angle, lighting, and screen-induced gaze distortion make body-language reading unreliable. On video, prioritise vocal qualities and verbal content. Reserve full nonverbal reading for in-person interactions. + +4. **Calling Bluffs Aggressively.** Detecting a bluff and then announcing "I know you're bluffing" is a negotiation-ending move, not a negotiation tactic. The correct response is to decline the bluffer's demand while preserving the relationship. The information value of the detection is strategic; the confrontation is not. + +5. **Mirroring Without Stopping.** Applying the technique to every sentence in a conversation, producing a parrot effect that is disorienting rather than validating. Mirroring is a precision tool. Deploy it at moments of emotional significance, not as a conversational default. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder alignment | At the idea stage, the most critical reading is between cofounders. Misaligned nonverbal signals during early discussions about equity, roles, and vision are the earliest warning signs of partnerships that will fracture under pressure. | +| Validation | Customer truth-detection | Customers in discovery interviews are polite. Politeness masks indifference. Reading nonverbal signals distinguishes genuine pain points from courteous agreement -- the difference between a real market and a phantom one. | +| Early Traction | Hiring signal reading | Candidates optimise their verbal performance. The founder who reads posture, eye contact, and vocal authenticity during interviews makes better hiring decisions than the one who evaluates only what candidates say. | +| Growth | Negotiation and board dynamics | Growth-stage negotiations -- fundraising, partnerships, M&A exploration -- are environments where bluffing is expected and stakes are high. Baseline-deviation detection becomes a measurable financial skill. | +| Scale | Organisational listening systems | At scale, the CEO cannot personally read every stakeholder. The reading skills must be taught to managers and embedded in feedback systems -- 360 reviews that capture nonverbal observations, not just verbal ratings. | + +--- + +## Output Template + +```markdown +# People-Reading Preparation: [Meeting / Negotiation / Interview] + +## Context +- **Person:** [Name and role] +- **Stakes:** [What is at stake in this interaction] +- **Format:** [In-person / Video / Phone] + +## Baseline Plan +- **Low-stakes topics for calibration:** [2-3 conversation openers] +- **Baseline behaviours to note:** [Posture, gesture rate, eye contact pattern, speech pace] + +## Pressure Points +| Topic | Expected Verbal Position | Nonverbal Channels to Watch | +|-------|------------------------|---------------------------| +| [Topic 1] | [What they will likely say] | [What to observe] | +| [Topic 2] | [What they will likely say] | [What to observe] | + +## Mirroring Plan +- **Likely emotional statements:** [Anticipated expressions] +- **Prepared mirrors:** [Exact-language reflections] +- **Follow-up questions after mirror:** [Deepening questions] + +## Post-Meeting Debrief +- **Baseline observations:** [What was normal for this person] +- **Deviations noted:** [Where behaviour shifted] +- **Revised assessment:** [What they actually communicated vs. what they said] +``` + +--- + +## Related Skills + +- **[Understanding People](../../content/skills/people/understanding-people.md)** -- Understanding provides the motivational map (Enneagram types, core drives); reading provides the real-time signal detection that reveals whether stated motivations match actual behaviour. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Reading is diagnostic; connecting is therapeutic. Mirroring bridges both, reading emotional state while simultaneously building connection. +- **[Meeting the Right People](../../content/skills/people/meeting-the-right-people.md)** -- Meeting gets you in the room; reading tells you what the room is actually communicating behind its words. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's social awareness domain provides the theoretical case for why nonverbal reading matters. +- **[Negotiation Mindset and Self-Management](../../content/skills/negotiation/negotiation-mindset-and-self.md)** -- Negotiation preparation depends on reading the counterpart's style, assumptions, and emotional state; the techniques here provide the perceptual toolkit. +- **[Leadership Style Adaptation](../../content/skills/leadership/leadership-style-adaptation.md)** -- The Read-Choose-Act-Review adaptation cycle depends on accurately reading what a situation and its people need before choosing a response. diff --git a/plugins/foreman/skills/resolving-people-conflict/SKILL.md b/plugins/foreman/skills/resolving-people-conflict/SKILL.md deleted file mode 120000 index c90489c..0000000 --- a/plugins/foreman/skills/resolving-people-conflict/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/resolving-people-conflict.md \ No newline at end of file diff --git a/plugins/foreman/skills/resolving-people-conflict/SKILL.md b/plugins/foreman/skills/resolving-people-conflict/SKILL.md new file mode 100644 index 0000000..45018fd --- /dev/null +++ b/plugins/foreman/skills/resolving-people-conflict/SKILL.md @@ -0,0 +1,251 @@ +--- +name: "resolving-people-conflict" +description: "Delivers specific behavioural systems for resolving interpersonal conflict in real time -- reframing conflict as a helping stance, the 24-hour cooling rule, strategic surrender of what cannot be controlled, and the bulletproof vest protocol (a structured seven-step system for safe conflict resolution). Use when a cofounder disagreement is escalating, an employee conflict is disrupting team performance, a client relationship is strained, a personal relationship is leaking into work effectiveness, or any situation where two parties need a structured de-escalation process. Complements the theoretical Thomas-Kilmann conflict modes with tactical, script-level behavioural techniques." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - conflict-resolution + - de-escalation + - cofounder-conflict + - emotional-regulation + - bulletproof-vest + - cooling-period + - letting-go + - active-listening + - mediation +related_skills: + - thomas-kilmann-conflict + - carnegie-win-friends + - win-win-negotiation + - emotional-courage + - influencing-and-persuading +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Resolving People Conflict + +BULLETPROOF VEST. The most effective conflict resolution system in this entire collection was invented to save a marriage -- and it works just as well in boardrooms. A psychologist who had appeared on Oprah five times gave a couple a seven-step protocol: request an appointment (never "right now"), agree to wear a metaphorical bulletproof vest (absorb without defending), listen and mirror, apologise genuinely, then choose from three positive solutions proposed by the aggrieved party. The couple had been married seven years and fighting the same patterns on loop. Within three sessions they had a system that ended the loop. Several years later, they still use it. + +The Thomas-Kilmann framework (see `thomas-kilmann-conflict`) identifies five theoretical conflict modes: competing, accommodating, compromising, avoiding, and collaborating. That is the taxonomy. What follows is the field manual -- four specific behavioural techniques for what to do when you are in the room, the temperature is rising, and theory is the last thing on your mind. + +--- + +## The Framework + +### System 1: Reframe Conflict as Helping + +A high school vice principal sat between a student who had been maced and the student who had maced him. Her opening words: "Please know one thing. I'm here to help you. Whether or not you walk out of this room with suspension or other consequences, please know that above all else, I am here to help." + +That single reframe -- from adjudicator to helper -- changed the trajectory of the conversation. Both parties relaxed enough to tell their sides honestly. The resolution was a negotiated exchange: no punishment, cards returned, a warning noted. Neither party left happy in the celebratory sense, but both left feeling heard and helped. + +**The operational stance for any conflict:** + +Replace the instinctive internal question -- "How can I win?" or "How can I prove I'm right?" or "How can I punish?" -- with a single alternative: + +> "How can I help resolve this in a way that leaves all parties feeling heard?" + +This is not softness. It is strategic. When both parties perceive the mediator (or the other party) as genuinely trying to help, defensive walls lower. Information flows. Solutions emerge from the space that defensiveness previously occupied. + +**The script for entering a conflict:** + +1. State your helping intent explicitly: "I want to help us resolve this. My goal is that we both walk away feeling heard." +2. Invite both sides to share fully, without interruption. +3. Mirror each party's position back to them before proposing any solution. +4. Only after both parties confirm they feel heard, move to solution-generation. + +In entrepreneurial contexts, this stance applies to cofounder disputes, employee grievances, client complaints, and investor disagreements. The instinct to defend, justify, or counter-attack is universal. The discipline to say "I'm here to help" first is rare -- and disproportionately effective. + +### System 2: The 24-Hour Rule (Let Cooler Heads Prevail) + +A founder stormed out of his house after a family board game went wrong. His wife texted demanding immediate resolution. He returned, still in a state of rage. The resulting conversation was unproductive: he was listening but not processing; she was talking but not being heard. They went to sleep. + +The next morning, the conversation was entirely different. He was calm. She was calm. He articulated what he had felt. She articulated her boundaries. They made a commitment and moved forward. + +**The principle:** it is neurologically impossible to resolve conflict while either party is in a state of emotional flooding. Adrenaline and cortisol impair the prefrontal cortex -- the brain region responsible for empathy, perspective-taking, and creative problem-solving. Attempting resolution while flooded produces either escalation or capitulation, neither of which constitutes resolution. + +**The 24-hour rule in practice:** + +| Situation | What to say | What not to do | +|-----------|------------|----------------| +| You are flooded | "I'm in a highly volatile state and would really appreciate resolving this later." | Storm out without explanation; send angry texts; pretend you are fine | +| The other person is flooded | "I can see this is intense. Let's come back to this when we've both had time to think." | Demand immediate resolution; interpret their need for space as avoidance; escalate to force engagement | +| Both parties are flooded | "Neither of us is in a position to resolve this well right now. Let's set a specific time tomorrow." | Continue arguing; make permanent decisions based on temporary emotions | + +The critical nuance: the 24-hour rule is a delay, not an avoidance. Setting a specific time to reconvene distinguishes strategic patience from conflict dodging. "Let's talk about this later" without a time commitment becomes "Let's never talk about this," which compounds resentment. + +**Recommended minimum cooling periods by conflict intensity:** + +- Minor disagreement (process, scheduling): 1-2 hours +- Significant dispute (strategy, resource allocation): 24 hours +- Existential conflict (cofounder split, termination): 48-72 hours, ideally with a neutral third party present at reconvention + +### System 3: Strategic Surrender (Let Go to Get What You Want) + +A therapist posed the decisive question to a client in anguish over an uncontrollable situation: "What can you control in this uncontrollable conflict?" + +The answer, arrived at reluctantly: letting go. Letting go of the outcome, of the need to control, of the expectation that persistence alone would produce the desired result. + +The second answer, prompted by the therapist: taking care of yourself -- eating well, exercising, sleeping properly. These are always within control, even when nothing else is. + +**When strategic surrender applies:** + +- The other party will not move, and no amount of persuasion will change that. +- The conflict is consuming resources (time, emotional energy, focus) disproportionate to the potential resolution. +- Continuing to push is producing the opposite of the desired effect -- hardening the other party's position. + +**The Serenity Protocol for entrepreneurs:** + +1. **Identify what you cannot control.** The other person's decision. The market's reception. The investor's timeline. The cofounder's personal priorities. +2. **Identify what you can control.** Your response. Your health. Your next move. Your emotional state. +3. **Execute the letting-go decision.** This may mean ceasing communication, changing roles, ending a partnership, or simply accepting an outcome you did not want. +4. **Redirect energy to self-care and forward motion.** The founder who let go of an impossible personal situation lost sixty-nine pounds, got into the best shape of his life, left the company they shared, and ultimately got what he wanted -- over a year later, on terms that could never have been engineered through force. + +Strategic surrender is not defeat. It is the recognition that some conflicts have no resolution within the current frame and that the energy spent fighting is better invested in what remains within control. + +### System 4: The Bulletproof Vest Protocol + +Developed by relationship psychologist Dr. Bonnie Weil, this is a structured seven-step system for resolving recurring interpersonal conflicts. Originally designed for couples, it transfers directly to any close working relationship -- cofounders, business partners, long-term client relationships. + +**The seven steps:** + +**Step 1: Request an Appointment.** The aggrieved party requests a time to discuss the issue and offers three possible times. Critically, none of the options is "right now." This creates a cooling buffer and signals respect for the other person's readiness. + +**Step 2: Agree on a Safe Setting.** Both parties convene in a quiet, neutral space -- not a hallway, not a Slack channel, not a moving vehicle. + +**Step 3: Put On the Bulletproof Vest.** The party who caused the grievance agrees, explicitly and in advance, to absorb what they hear without defensiveness. No counter-arguments. No justifications. No "but." The vest is a commitment to receive without returning fire. + +**Step 4: Full Expression.** The aggrieved party describes the problem in full -- what happened, how it made them feel, and what impact it had. No interruptions. + +**Step 5: Mirror and Validate.** The other party mirrors back what they heard ("What I'm hearing is...") and validates the feelings ("I can understand why that would feel..."). Not solving. Not defending. Listening, mirroring, validating. + +**Step 6: Genuine Apology.** The offending party offers an authentic "I'm sorry." Not "I'm sorry you feel that way" (which is not an apology). Not "I'm sorry, but..." (which is a defence). A clean, unqualified apology. + +**Step 7: Three Solutions.** The aggrieved party proposes three positive solutions. The other party commits to at least one. Both parties then do something physical together -- a walk, a workout, a shared meal -- to biochemically seal the resolution. + +**Example in practice:** A founder felt criticised when his cofounder raised a sensitive personnel issue on a train -- a public, confined space with no exit. He requested an appointment. Two hours later, in their bedroom, she put on the bulletproof vest. He shared how criticised and trapped he had felt. She mirrored and validated without defending. She apologised. He proposed three solutions: (a) no work talk on the train, (b) no shared commute, or (c) a code word for when conversations get sensitive. She chose option (a) with option (c) as backup. They did jumping jacks. The problem never recurred. + +--- + +## Prompts + +**Prompt 1 -- Conflict Reframe:** +> I am in a conflict with [person/role] about [issue]. My instinct is to [defend / prove I'm right / escalate / avoid]. Help me reframe my internal stance from adversary to helper. Draft the exact words I should use to open our next conversation from a helping position, and suggest three questions I should ask to ensure they feel heard. + +**Prompt 2 -- Cooling Period Plan:** +> I just had a heated exchange with [person] about [issue]. I am currently [emotional state]. Help me draft a brief, calm message to defer resolution to a specific time, and create a cooling-period plan: what should I do in the next 24 hours to process this emotion before reconvening? + +**Prompt 3 -- Bulletproof Vest Preparation:** +> I need to use the Bulletproof Vest Protocol with [person] regarding [issue]. I am the [aggrieved party / offending party]. Walk me through what I should say at each of the seven steps, including (a) the appointment request, (b) mirroring and validation phrases I should use, (c) how to frame my apology authentically, and (d) three positive solutions I could propose. + +**Prompt 4 -- Strategic Surrender Assessment:** +> I have been in an ongoing conflict with [person/situation] for [duration]. Help me assess: (a) what I can control and what I cannot, (b) whether continued engagement is producing any progress or only hardening positions, (c) what a strategic surrender would look like in concrete terms, and (d) where I should redirect the energy I am currently spending on this conflict. + +--- + +## Use Cases + +**Cofounder Equity Dispute at Validation Stage** + +Two cofounders agreed on a 50/50 equity split at inception but six months later have radically different time commitments -- one is full-time, the other still has a day job. The full-time founder is resentful. The part-time founder feels ambushed. Both are flooded. Application: invoke the 24-hour rule. Set a meeting for two days later with a mutual advisor present. The advisor opens with the helping frame: "I'm here to help you both build something you're proud of." Each founder shares their perspective without interruption. The advisor mirrors and validates. Then the aggrieved founder proposes three vesting structures. They agree on one. The relationship survives because the process prevented a conversation during flooding. + +**Client Escalation at Growth Stage** + +A key client emails the CEO directly, furious about a missed delivery date. The CEO's instinct is to respond immediately with an explanation and a discount. Application: apply the 24-hour rule to the response (not 24 hours of silence -- a brief acknowledgement within an hour, with a detailed response scheduled for the following morning). Draft the response from a helping stance: "I want to understand exactly how this affected your team so we can make it right." When the call happens, the CEO puts on the bulletproof vest: absorbs the client's frustration without defending, mirrors the impact, apologises without qualification, and proposes three remediation options. The client chooses one. The account is retained. + +**Intractable Investor Disagreement at Scale** + +A board member insists on a strategic direction the CEO believes is wrong. Three board meetings of debate have produced only deeper entrenchment. Application: strategic surrender assessment. The CEO identifies what she can control (her own preparation, the data she presents, the support she builds among other board members) and what she cannot (this board member's opinion). She stops arguing the point directly, redirects energy toward building consensus with the remaining board, and presents a revised proposal at the next meeting with majority support already secured. The dissenting board member, no longer being pushed against, moderates his position. + +--- + +## Anti-Patterns + +**Cooling Period as Conflict Avoidance.** The 24-hour rule requires a specific reconvening time. "Let's talk about this later" without a date is not cooling -- it is avoidance. Unresolved conflicts compound. Each one left hanging deposits a small amount of resentment that accrues interest. + +**Bulletproof Vest Without Genuine Apology.** Going through steps 1-5 of the protocol and then offering "I'm sorry you feel that way" at step 6 invalidates the entire process. The vest requires absorbing; the apology requires owning. "I'm sorry I did X, and I understand why it hurt you" is the minimum viable apology. + +**Strategic Surrender as First Resort.** Letting go is for conflicts that genuinely cannot be resolved through engagement. Using it to avoid difficult conversations that could be resolved with effort is not strategic; it is abdication. + +**Reframing as Helping When You Are Not, In Fact, Helping.** Saying "I'm here to help" while privately committed to winning the argument produces a credibility collapse when the other party detects the incongruence -- and they will detect it. The helping frame must be genuine, which means genuinely being willing to accept an outcome that is not your preferred one. + +**Applying Couple's Therapy to Power-Asymmetric Relationships.** The Bulletproof Vest Protocol assumes rough equality between the parties. In a boss-subordinate conflict, asking the subordinate to put on the vest and absorb the boss's grievance without defence may produce compliance, not resolution. Power asymmetry requires additional structural safeguards -- a neutral third party, explicit assurance of no retaliation, and genuine willingness from the more powerful party to hear dissent. + +--- + +## By Stage + +| Stage | Common Conflict Type | Recommended Primary System | +|-------|---------------------|--------------------------| +| Idea | Cofounder vision misalignment; equity disputes | Bulletproof Vest Protocol (establishes conflict norms early) | +| Validation | Disagreements over pivot decisions; resource allocation with no resources | 24-Hour Rule + Helping Reframe | +| Early Traction | Employee conflicts as team grows past 5; first client disputes | Helping Reframe for mediation; Bulletproof Vest for partner relationships | +| Growth | Board disagreements; departmental friction; key-person conflicts | Strategic Surrender assessment for intractable positions; 24-Hour Rule for heated meetings | +| Scale | Cross-functional political conflicts; executive team disputes | All four systems in combination; institutional conflict-resolution norms | + +At the idea stage, cofounders who establish a conflict protocol before their first serious disagreement build a relationship that can survive the inevitable disagreements ahead. The Bulletproof Vest Protocol, adopted early, prevents the pattern of repeated unresolved fights that destroys cofounder relationships. At scale, the founder's role shifts from participant in conflicts to architect of systems that resolve them without the founder's direct involvement. + +--- + +## Output Template + +```markdown +# Conflict Resolution Plan + +**Parties Involved:** [Names/Roles] +**Issue:** [Concise description of the conflict] +**Current Temperature:** [Cold / Warm / Hot / Flooded] +**My Role:** [Aggrieved / Offending / Mediator] + +## Immediate Action +- [ ] If flooded: send cooling message and set reconvening time + - Message: "[Draft cooling message]" + - Reconvening: [Specific date and time] +- [ ] If calm: proceed to system selection + +## System Selection +- [ ] Helping Reframe (I am mediating or the conflict is new) +- [ ] 24-Hour Rule (emotions are high; productive conversation is impossible now) +- [ ] Strategic Surrender (conflict is intractable; continuing produces no progress) +- [ ] Bulletproof Vest Protocol (recurring pattern with a close working partner) + +## If Bulletproof Vest Protocol +1. Appointment request sent: [date/time options offered] +2. Location: [neutral, quiet setting] +3. Who wears the vest: [name] +4. My three proposed solutions: + - Option A: [solution] + - Option B: [solution] + - Option C: [solution] +5. Physical activity to seal resolution: [walk / meal / workout] + +## If Strategic Surrender +- What I cannot control: [list] +- What I can control: [list] +- Letting-go action: [specific step] +- Energy redirection: [where effort goes instead] + +## Follow-Up +- Check-in date to confirm resolution held: [date] +- Escalation plan if resolution fails: [next step] +``` + +--- + +## Related Skills + +- **[Thomas-Kilmann Conflict Modes](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- The five conflict modes provide the theoretical taxonomy; this skill provides the behavioural scripts for executing within those modes. +- **[Carnegie's Win Friends and Influence People](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principle of never criticising and seeing things from the other person's perspective underpin the Helping Reframe. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- When conflict resolution transitions into formal negotiation over terms or resources, principled negotiation provides the structural framework. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- The willingness to enter difficult conversations, deliver genuine apologies, and absorb criticism without defence requires the emotional courage practices detailed in that skill. +- **[Influencing and Persuading](../../content/skills/people/influencing-and-persuading.md)** -- The "choose happiness over rightness" technique is the precursor to strategic surrender detailed here. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Conflict resolution is only possible when team members feel safe enough to surface disagreements; without safety, conflicts go underground and fester. diff --git a/plugins/foreman/skills/revising-and-editing/SKILL.md b/plugins/foreman/skills/revising-and-editing/SKILL.md deleted file mode 120000 index 98cde64..0000000 --- a/plugins/foreman/skills/revising-and-editing/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/revising-and-editing.md \ No newline at end of file diff --git a/plugins/foreman/skills/revising-and-editing/SKILL.md b/plugins/foreman/skills/revising-and-editing/SKILL.md new file mode 100644 index 0000000..0c0a20b --- /dev/null +++ b/plugins/foreman/skills/revising-and-editing/SKILL.md @@ -0,0 +1,201 @@ +--- +name: "revising-and-editing" +description: "Teaches the distinct disciplines of revising (rethinking content and structure) and editing (refining sentences and word choices), with a concrete three-draft evolution showing how a mediocre memo transforms into an excellent one. Covers revision checklists, editing checklists, and the peer feedback process. Use when polishing any business document, preparing final drafts for stakeholders, training teams on writing quality, or establishing editorial review processes." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - editing + - revision + - feedback + - quality + - drafting + - business-writing +related_skills: + - writing-process + - clarity-and-concision + - plain-language-and-flow + - business-writing-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Revising and Editing + +Watch a mediocre memo become an excellent one. The first draft reads: "In order to facilitate the customers' placement of orders, a new order-processing procedure has been designed. The process will require a customer to enter the product and/or service code into our order-entry system, which will then generate a quote for the job and return it to the customer for approval." By the third draft, it reads: "Our current work-order processing takes a lot of paperwork and phone calls, so it's hard for our customers to make changes to the work before it begins. The procedure is inefficient and subject to error. And it takes up to four weeks from quote to approval to work order. We have therefore designed a new four-step procedure that has two key benefits: (1) Customers can place orders through our website, and (2) we can start jobs faster." + +The difference is not cosmetic. The first draft tells the reader *what* is happening. The third draft tells them *why it matters*. Between those two versions lies the entire discipline of revision and editing -- two related but fundamentally different operations that most writers conflate, to their detriment. + +--- + +## The Framework + +### Revising vs. Editing: The Critical Distinction + +Revising is rethinking the floor plan. Editing is choosing the paint colours. Confuse the two, and a writer will spend an hour perfecting the grammar of a paragraph that should have been deleted entirely. + +**Revising** addresses the macro level: the argument, the structure, the completeness, the truthfulness, the diplomacy. It asks whether the right things have been said. + +**Editing** addresses the micro level: the sentences, the word choices, the phrasing, the rhythm. It asks whether the right things have been said *well*. + +Both require dedicated time. Neurotic perfectionism that delays important documents is as damaging as rash distribution of unvetted drafts. The solution is a structured process that allocates appropriate time to each operation. + +### The Revision Checklist + +During revision, the writer steps back from the prose and interrogates the document as a whole: + +1. **Have I been utterly truthful?** Does the document accurately represent the facts, or have I unconsciously shaded them to support a preferred conclusion? +2. **Have I said all that I need to say?** Are there gaps that leave the reader unable to act? Missing context? Unanswered questions that the reader will inevitably ask? +3. **Have I been appropriately diplomatic and fair?** Will the tone damage a relationship that should be preserved? Have I been fair to opposing viewpoints? +4. **Do I have three parts -- an opener, a middle, and a closer?** Is the structure apparent to the reader? +5. **In my opener, have I made my points quickly, clearly, and concretely?** Or have I buried the lead under a slow wind-up? +6. **Have I avoided a slow wind-up that unnecessarily postpones the message?** The first paragraph should deliver the core point, not prepare the reader for a core point that arrives later. +7. **In the middle, have I proved my points with specifics?** Evidence, data, examples -- not assertions. +8. **Is the structure immediately apparent?** Have I used informative headings? +9. **Is my closer consistent with the rest -- yet expressed freshly?** Have I avoided lame repetition? + +### The Editing Checklist + +Once the structure is sound, the editor's eye narrows to the sentence and word level: + +1. **Can I save some words here?** Every word must earn its place. +2. **Is there a better way of phrasing this idea?** Could a stronger verb replace a weak verb-plus-adverb combination? +3. **Is my meaning unmistakable?** Could any sentence be misinterpreted by a reader with a different context? +4. **Can I make it more interesting?** Varied sentence length? A concrete example instead of an abstraction? +5. **Is the expression relaxed but refined?** Natural language, not corporate stiffness -- but not sloppy either. +6. **Does one sentence glide into the next, without discontinuities?** Are the transitions smooth? + +### Three Drafts in Practice + +The evolution from first to third draft follows a recognisable pattern: + +**First Draft (Carpenter output):** The ideas are present but poorly ordered. Important context is missing. The opening buries the point. Passive constructions dominate. The reader is told what is happening but not why. + +**Second Draft (Post-Revision):** The structure has been rethought. The opening now states the problem and the solution. Missing information -- the who, what, when, why -- has been filled in. The document can now stand on its own. But the prose is still wordy, and some phrasing is stiff. + +**Third Draft (Post-Editing):** Sentences have been tightened. Passive voice has been replaced with active voice where appropriate. Wordiness has been cut. The steps of the process have been reformatted as bullet points for scannability. The document reads as though it was easy to write -- which is precisely the illusion that careful editing creates. + +### The Peer Feedback Process + +The writer's worst handicap is familiarity. Having lived with a document through multiple drafts, the writer can no longer see it with fresh eyes. Peer feedback solves this problem -- but only if structured properly. + +**Effective peer feedback requires:** + +- **Specific questions, not open invitations.** "What do you think?" produces vague responses. "Can you identify my three main points after one read-through?" produces actionable data. +- **Fresh eyes.** The reviewer should not have been involved in the drafting. Their confusion is diagnostic: wherever they stumble, other readers will stumble too. +- **Separation of content and expression.** Ask one reviewer to assess whether the argument is complete and logical. Ask another to assess whether the prose is clear and concise. Combining both tasks in one review dilutes attention. +- **Ego management.** Feedback is not personal. A suggestion to restructure paragraph three is not an attack on the writer's intelligence. Writers who cannot receive criticism without defensiveness should consider whether they are in the right profession. + +--- + +## Prompts + +**Prompt 1 -- Revision Audit:** +> Here is a draft of my [document type]: [paste draft]. Apply the full revision checklist: (1) Is it truthful and accurate? (2) Is anything missing that the reader needs? (3) Is the tone appropriately diplomatic? (4) Does the structure have a clear opener, middle, and closer? (5) Is the main point visible in the first paragraph? (6) Are points supported with specifics? (7) Is the structure apparent with informative headings? Provide a paragraph-by-paragraph revision assessment with specific recommendations. + +**Prompt 2 -- Editing Pass:** +> Here is a revised draft of my [document type]: [paste draft]. Now edit at the sentence level: (1) Cut unnecessary words -- show me a word-count comparison for each paragraph, (2) Replace weak verbs and passive constructions, (3) Ensure each sentence's meaning is unmistakable, (4) Smooth transitions between paragraphs, (5) Vary sentence length for rhythm. Show the edited version with tracked changes explained. + +**Prompt 3 -- Three-Draft Transformation:** +> Here is a rough first draft: [paste draft]. Transform it through three clear stages. Show me Draft 2 (revised for structure, completeness, and argument) with an explanation of what changed and why. Then show me Draft 3 (edited for prose quality, concision, and polish) with an explanation of each edit. I want to see the evolution, not just the final product. + +**Prompt 4 -- Peer Review Simulation:** +> Pretend you are a colleague reading my [document type] for the first time: [paste draft]. After one read-through, tell me: (1) What are the three main points? (2) What action am I supposed to take? (3) Where did you get confused or lose interest? (4) What questions remain unanswered? (5) What would you cut? Be direct -- I need a reader's honest reaction, not reassurance. + +--- + +## Use Cases + +**Validation-Stage Startup Polishing a Pitch Deck Narrative** + +A founder has drafted a 12-slide pitch deck with extensive speaker notes. The Madman and Carpenter phases are complete, but the narrative feels scattered. Applying the revision checklist: the opener (slide 1) describes the product instead of the problem -- revision moves the problem statement forward. Slides 4-6 present features without connecting them to the market need identified in slide 2 -- revision adds the "so what" connector. The closer asks for investment without specifying terms or use of funds -- revision adds a concrete ask. After structural revision, the editing pass tightens every speaker note from an average of 80 words to 40 words, replaces jargon with plain language, and ensures each slide's headline could stand alone as a summary. + +**Scale-Stage Company Establishing an Editorial Review Process** + +A 500-person company discovers that external communications vary wildly in quality. Customer emails from support read differently from product announcements, which read differently from investor updates. The company implements a structured revision and editing process: all customer-facing documents above 500 words go through a two-stage review. Stage 1 (revision): a designated editor checks structure, completeness, and tone alignment with brand guidelines. Stage 2 (editing): a copy editor checks prose quality, grammar, and consistency. The peer feedback process uses specific checklists rather than open-ended review requests. Writing quality becomes consistent across the organisation within one quarter. + +--- + +## Anti-Patterns + +1. **Editing Before Revising.** Polishing sentences in a paragraph that should be deleted or moved is wasted effort. Always assess the macro structure before descending to the micro level. + +2. **Declaring the First Draft Final.** The most costly anti-pattern in business writing. A first draft, by definition, captures what the writer wanted to say -- not necessarily what the reader needs to hear. Skipping revision means skipping the transition from writer-centred to reader-centred prose. + +3. **Revising in Perpetuity.** Some writers revise indefinitely, unable to declare a document "done." The antidote: define the number of revision rounds in advance. Two rounds of revision and two rounds of editing is sufficient for most business documents. + +4. **Soliciting Feedback from the Wrong People.** Asking a subject-matter expert to assess prose quality, or asking a copy editor to assess strategic content, produces useless feedback. Match the reviewer to the review task. + +5. **Taking Peer Feedback Personally.** A colleague who identifies a structural flaw in a draft is saving the writer from presenting that flaw to a less forgiving audience. The revision process requires emotional detachment from the prose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Self-review discipline | Solo founders have no peer reviewers. The revision checklist serves as a surrogate editor, enforcing structural rigour even when the writer is the only reader before publication. | +| Validation | Evidence verification | Revision at this stage must prioritise truthfulness and completeness. Investors will scrutinise claims. Every data point must survive the "have I been utterly truthful?" test. | +| Early Traction | Speed-quality balance | The volume of writing increases sharply. The temptation is to skip revision entirely. A lightweight checklist -- even a 5-minute structural scan before sending -- prevents the worst errors without creating bottlenecks. | +| Growth | Peer review infrastructure | Dedicated editors or communications staff can own the editing function. Subject-matter experts draft; editors revise and polish. The separation of roles mirrors the separation of revision and editing. | +| Scale | Process and standards | Revision checklists become institutional standards. Style guides codify editing decisions. The three-draft process becomes organisational policy for high-stakes communications. | + +--- + +## Output Template + +```markdown +# Revision and Editing Report: [Document Title] + +## Revision Assessment (Macro Level) +| Question | Assessment | Action Required | +|----------|-----------|-----------------| +| Truthful and accurate? | [Yes/No/Partially] | [Specific fix] | +| Complete -- nothing missing? | [Yes/No] | [What to add] | +| Diplomatic and fair? | [Yes/No] | [Tone adjustment] | +| Clear opener with main point? | [Yes/No] | [Restructure how] | +| Points supported with evidence? | [Yes/No] | [Evidence gaps] | +| Structure apparent to reader? | [Yes/No] | [Headings needed] | +| Closer fresh and consistent? | [Yes/No] | [Revision needed] | + +## Editing Assessment (Micro Level) +| Dimension | Current State | Improvement | +|-----------|--------------|-------------| +| Word economy | [Word count: X] | [Target: Y, cuts identified] | +| Phrasing quality | [Weak areas] | [Specific rewrites] | +| Meaning clarity | [Ambiguous passages] | [Disambiguations] | +| Transitions | [Gaps identified] | [Connectors added] | +| Grammar/mechanics | [Errors found] | [Corrections] | + +## Peer Feedback Summary +| Reviewer | Role | Key Finding | Resolution | +|----------|------|-------------|------------| +| [Name] | Content reviewer | [Finding] | [Action taken] | +| [Name] | Prose reviewer | [Finding] | [Action taken] | + +## Draft Progression +- **Draft 1 word count:** [X] +- **Draft 2 word count (post-revision):** [Y] +- **Draft 3 word count (post-editing):** [Z] +- **Net change:** [Percentage reduction/expansion] +``` + +--- + +## Related Skills + +- **[Writing Process](../../content/skills/writing/writing-process.md)** -- MACJ provides the four-phase structure; this skill expands the Judge phase into a comprehensive revision and editing discipline. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- The editing checklist's "Can I save some words?" question is the gateway to the concision techniques detailed in this companion skill. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- The editing question "Does one sentence glide into the next?" connects directly to the continuity and transition techniques covered here. +- **[Grammar and Mechanics](../../content/skills/writing/grammar-and-mechanics.md)** -- The final editing pass depends on mechanical precision; this companion skill provides the specific rules and common error patterns to check against. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Leaders who review others' writing benefit from the structured peer feedback methodology in this skill. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Revision is the stage where tonal problems surface; the diagnostic tools for passive voice, nominalizations, and register mismatches apply during the editing process. diff --git a/plugins/foreman/skills/scenario-planning/SKILL.md b/plugins/foreman/skills/scenario-planning/SKILL.md deleted file mode 120000 index 50281bc..0000000 --- a/plugins/foreman/skills/scenario-planning/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/scenario-planning.md \ No newline at end of file diff --git a/plugins/foreman/skills/scenario-planning/SKILL.md b/plugins/foreman/skills/scenario-planning/SKILL.md new file mode 100644 index 0000000..e4afd77 --- /dev/null +++ b/plugins/foreman/skills/scenario-planning/SKILL.md @@ -0,0 +1,204 @@ +--- +name: "scenario-planning" +description: "Constructs multiple plausible future scenarios using a 2x2 matrix + of critical uncertainties, then stress-tests strategy against each scenario to + develop robust responses. Identifies no-regret moves, hedging actions, and + strategic options. Use when facing major capital allocation decisions, + evaluating market expansion under regulatory uncertainty, preparing for + technology disruption, or building enterprise risk management into strategic + planning cycles." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - strategy + - uncertainty + - planning + - futures + - decision-making +related_skills: + - black-swans + - porters-five-forces + - swot-pest-analysis + - blue-ocean-strategy +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Scenario Planning + +When the Arab oil embargo struck in October 1973, most Western corporations were blindsided. Royal Dutch Shell was not. Through a practice called scenario planning -- pioneered within the company by Pierre Wack and his team in the Group Planning division -- Shell had already rehearsed a world in which oil prices spiked dramatically. While competitors scrambled to react, Shell had contingency plans ready to execute. Within two years, Shell rose from the seventh-largest oil company to the second. The story is not merely corporate lore; it remains the canonical demonstration that rehearsing multiple futures is more valuable than perfecting a single forecast. + +Scenario planning does not attempt to predict the future. It attempts to prepare for several plausible futures simultaneously, so that when events unfold -- inevitably in ways that match no single prediction -- the organization can respond with speed and coherence rather than confusion. + +--- + +## The Framework + +### The Logic of Scenarios + +Traditional strategic planning assumes a single most-likely future and builds one plan around it. Scenario planning rejects this premise. It constructs multiple internally consistent narratives about how the future might develop, then uses these narratives to stress-test strategy and develop flexible responses. + +The distinction is not academic. A single-forecast plan is brittle; it works brilliantly if the forecast is correct and fails entirely if it is not. A scenario-informed strategy bends without breaking. + +### The Process + +Scenario planning follows a disciplined sequence, though practitioners adapt the steps to their context: + +**Step 1 -- Define the Focal Question** +What specific strategic decision or uncertainty does the organization need to navigate? The question must be concrete. "What will our industry look like in ten years?" is too broad. "Should we invest $20M in a new manufacturing facility given regulatory and demand uncertainty?" is actionable. + +**Step 2 -- Identify Driving Forces** +Map the external forces that will shape outcomes: technological trends, regulatory trajectories, demographic shifts, competitor behavior, macroeconomic conditions. Distinguish between predetermined elements (forces largely certain to continue, such as demographic aging) and critical uncertainties (forces whose direction is genuinely unknown, such as regulatory posture toward AI). + +**Step 3 -- Select Scenario Axes** +Choose two critical uncertainties as the axes of a 2x2 matrix. Each axis represents a spectrum (e.g., "regulation: permissive to restrictive" and "demand: growing to contracting"). The four quadrants define four distinct scenario worlds. + +**Step 4 -- Build Scenario Narratives** +For each quadrant, construct a plausible story. Give it a memorable name. Describe how this world develops over the planning horizon: what happens, why, and what it means for the industry. The narratives must be internally consistent and genuinely different from one another. + +**Step 5 -- Identify Implications and Signposts** +For each scenario, determine: What would our current strategy deliver in this world? What capabilities would we need? What early indicators ("signposts") would tell us this scenario is materializing? + +**Step 6 -- Develop Robust Strategies** +Design strategies that perform acceptably across multiple scenarios rather than optimally in just one. Identify "no regret" moves (beneficial in all scenarios), hedging actions (insurance against specific scenarios), and options to preserve (flexibility that becomes valuable if certain scenarios materialize). + +### The 2x2 Scenario Matrix + +``` + Uncertainty A: High + | + Scenario 2 | Scenario 1 + "Name" | "Name" + | + Uncertainty B: ---------|--------- Uncertainty B: + Low | High + | + Scenario 3 | Scenario 4 + "Name" | "Name" + | + Uncertainty A: Low +``` + +### What Makes Good Scenarios + +Good scenarios are not optimistic, pessimistic, and middle-ground. They are qualitatively different worlds. Each should challenge assumptions in a different way. Shell's Wack insisted that scenarios must "change the mental maps of decision-makers" -- if they merely confirm existing beliefs, they have failed. + +--- + +## Prompts + +**Prompt 1 -- Scenario Matrix Construction:** +> I need to make a strategic decision about [describe the decision]. My company is [describe: sector, stage, size]. Help me build a scenario planning matrix. First, identify the 5-7 most important driving forces affecting this decision. Then select the two most critical uncertainties as axes. Construct four distinct scenarios with vivid names and 2-3 paragraph narratives for each. Finally, identify 2-3 early signposts for each scenario that would indicate it is beginning to materialize. + +**Prompt 2 -- Strategy Stress-Test:** +> Here is my current strategic plan: [describe plan]. Here are four scenarios I have developed: [list or describe scenarios]. Stress-test my plan against each scenario. For each one, assess: (1) How would our plan perform in this world? (2) What are the biggest vulnerabilities? (3) What adaptations would be required? Summarize the results in a table showing plan performance across all four scenarios. + +**Prompt 3 -- Robust Strategy Design:** +> Based on these four scenarios [describe or list them] and this strategy stress-test [paste or describe results], help me redesign my strategy for robustness. Categorize potential actions into three buckets: "No Regret" moves (valuable in all scenarios), "Hedging" moves (insurance against specific scenarios), and "Options" (investments in flexibility). For each action, estimate the cost and the scenarios in which it pays off. + +**Prompt 4 -- Signpost Monitoring Dashboard:** +> I have developed four scenarios for my business: [list scenarios with brief descriptions]. For each scenario, I identified these signposts: [list signposts]. Help me design a monitoring dashboard. What data sources should I track for each signpost? What thresholds or triggers should prompt strategic review? How frequently should each signpost be assessed? Format as a monitoring plan I can share with my leadership team. + +--- + +## Use Cases + +**Early-Traction EdTech Company Deciding on Market Expansion** +A B2B edtech startup with $2M ARR must decide whether to expand into the European market. The two critical uncertainties are regulatory environment (GDPR enforcement intensity ranging from lenient to aggressive) and buyer behavior (districts centralizing procurement vs. remaining fragmented). The four resulting scenarios produce radically different go-to-market strategies. The "no regret" move: build GDPR-compliant architecture regardless, since it strengthens the product everywhere. The hedging move: partner with a European distributor rather than establishing a subsidiary, preserving the option to scale up or retreat without heavy sunk costs. + +**Growth-Stage Fintech Evaluating Technology Bets** +A Series B fintech company must allocate engineering resources between improving its existing platform and building for a potential blockchain-based settlement infrastructure. Scenario planning surfaces two key uncertainties: speed of institutional blockchain adoption and regulatory stance toward decentralized finance. The scenario matrix reveals that in three of four worlds, the existing platform dominates near-term revenue. In one scenario, blockchain infrastructure becomes table stakes within five years. The robust strategy: invest 80% in platform improvement while maintaining a small, skilled team exploring blockchain integration -- an explicit option on the future rather than a binary bet. + +--- + +## Anti-Patterns + +1. **Building scenarios around optimistic/pessimistic/baseline.** This is the single most common error. Scenarios that differ only in degree ("things go well / okay / badly") are not scenarios at all -- they are sensitivities. Genuine scenarios differ in kind. The world where AI regulation is restrictive and enterprise adoption is slow is qualitatively different from the world where regulation is permissive and consumer adoption leads. + +2. **Treating scenario planning as a one-time exercise.** Organizations that build scenarios once, file them, and never revisit have wasted their effort. Scenarios gain value through ongoing use: monitoring signposts, updating narratives as new information arrives, and stress-testing each major decision against the established scenarios. + +3. **Selecting trivially certain or trivially unlikely axes.** If one axis is "will customers still want our product?" and the answer is obviously yes, the resulting scenarios will not challenge assumptions. Axes must represent genuine, consequential uncertainties where reasonable people could disagree about the outcome. + +4. **Using scenarios to justify a predetermined decision.** Some leaders commission scenario planning specifically to produce the narrative that supports the investment they already want to make. This transforms a strategic tool into a political one and discredits the entire exercise. + +5. **Overcomplicating with too many scenarios.** Four scenarios (from a 2x2 matrix) are the standard for good reason. More than four becomes cognitively unmanageable. If the team cannot remember and discuss all scenarios fluently, the framework loses its utility. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Assumption testing | At this stage, the entire business model is uncertain. Use lightweight scenario thinking to identify which assumptions, if wrong, would invalidate the venture. Two or three informal scenarios suffice; a full 2x2 process may be premature. | +| Early Traction | Go-to-market decisions | The product works; the question is where and how to grow. Scenario planning helps evaluate market entry choices, partnership strategies, and pricing models under different competitive and regulatory conditions. | +| Growth | Capital allocation | Significant investment decisions benefit most from formal scenario planning. Should we build or buy? Expand domestically or internationally? Invest in new technology or optimize existing? These decisions are expensive to reverse, making scenario rehearsal essential. | +| Scale | Enterprise risk management | At scale, scenario planning becomes an institutional practice rather than an ad-hoc exercise. Integrate scenarios into annual strategic planning cycles, board-level risk discussions, and capital allocation committees. | + +--- + +## Output Template + +```markdown +# Scenario Planning Analysis + +**Focal Question:** [The specific strategic decision under consideration] +**Time Horizon:** [Planning period, e.g., 3-5 years] +**Date:** [Date] + +## Driving Forces +1. [Force] -- [Predetermined / Critical Uncertainty] +2. [Force] -- [Predetermined / Critical Uncertainty] +3. [Force] -- [Predetermined / Critical Uncertainty] + +## Scenario Matrix + +**Axis X:** [Critical Uncertainty 1 -- spectrum description] +**Axis Y:** [Critical Uncertainty 2 -- spectrum description] + +### Scenario A: "[Name]" (X-High, Y-High) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario B: "[Name]" (X-High, Y-Low) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario C: "[Name]" (X-Low, Y-High) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +### Scenario D: "[Name]" (X-Low, Y-Low) +[2-3 paragraph narrative] +**Signposts:** [Early indicators] + +## Strategy Stress-Test + +| Action | Scenario A | Scenario B | Scenario C | Scenario D | Classification | +|--------|-----------|-----------|-----------|-----------|----------------| +| [Action 1] | [Impact] | [Impact] | [Impact] | [Impact] | No Regret / Hedge / Option | +| [Action 2] | [Impact] | [Impact] | [Impact] | [Impact] | No Regret / Hedge / Option | + +## Recommended Actions +1. **No Regret:** [Actions valuable in all scenarios] +2. **Hedges:** [Actions that insure against specific scenarios] +3. **Options:** [Investments in flexibility] +``` + +--- + +## Related Skills + +- **[Black Swan Theory](../../content/skills/frameworks/black-swans.md)** -- Scenario planning addresses plausible futures; Black Swan thinking addresses the implausible ones, and together they provide comprehensive uncertainty management. +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Industry structure analysis feeds directly into scenario construction by identifying the competitive forces most likely to shift. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- Internal strengths and weaknesses determine how the organization would perform under each scenario, making SWOT a natural complement. +- **[VUCA Framework](../../content/skills/frameworks/vuca-framework.md)** -- VUCA diagnoses the type of unpredictability; scenario planning is the primary strategic response when uncertainty is the dominant dimension. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Scenario planning is a structured System 2 exercise that counteracts the overconfidence and anchoring biases Kahneman identifies in single-forecast planning. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- Scenario planning provides the external foresight that strategic thinking translates into robust organizational direction and investment decisions. diff --git a/plugins/foreman/skills/senior-leadership-transition/SKILL.md b/plugins/foreman/skills/senior-leadership-transition/SKILL.md deleted file mode 120000 index 94f4f5e..0000000 --- a/plugins/foreman/skills/senior-leadership-transition/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/senior-leadership-transition.md \ No newline at end of file diff --git a/plugins/foreman/skills/senior-leadership-transition/SKILL.md b/plugins/foreman/skills/senior-leadership-transition/SKILL.md new file mode 100644 index 0000000..891a2b7 --- /dev/null +++ b/plugins/foreman/skills/senior-leadership-transition/SKILL.md @@ -0,0 +1,191 @@ +--- +name: "senior-leadership-transition" +description: "Guides leaders through the identity shift required when moving from functional management to enterprise leadership. Covers the seven role transformations (agenda setter, integrator, strategist, architect, diplomat, role model, successor builder), leading former peers, succession planning, and the mental recalibration that separates executives from promoted managers. Use when preparing for a C-suite role, navigating the first 90 days as VP or above, managing former peers, planning leadership succession, or coaching newly promoted executives." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - executive-transition + - succession-planning + - leadership-identity + - peer-to-boss + - senior-leadership + - promotion + - role-change +related_skills: + - leadership-style-adaptation + - leader-self-reflection + - leadership-voice-and-presence + - leadership-pipeline + - situational-leadership + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Senior Leadership Transition + +Yesterday you were the person who solved problems. Today you are the person who decides which problems are worth solving. This is not a promotion. It is an identity transplant. + +The individual contributor builds expertise in depth. The functional manager orchestrates that expertise across a team. The enterprise leader does something categorically different: they set the agenda for an entire organisation, integrate knowledge they do not personally possess, and shape systems they cannot directly control. Research from Spencer Stuart identifies three transitions that derail even accomplished leaders -- becoming a leader for the first time, leading organisational transformation, and reaching the top after years of striving toward it. The common thread is that each demands a fundamentally different version of the person who occupied the previous role. Skills that earned the promotion are necessary but insufficient; the mental shifts required are what separate executives who thrive from those who plateau with a better title. + +--- + +## The Practice + +### The Seven Role Transformations + +Moving from functional leadership to enterprise leadership requires simultaneous shifts across multiple dimensions. These are not sequential stages; they occur in parallel, and neglecting any one of them creates blind spots. + +**1. Agenda Setter** +The functional leader fixes problems handed to them. The enterprise leader decides which problems the organisation tackles at all. This requires surrendering the satisfaction of personal problem-solving in favour of prioritisation, delegation, and the disciplined use of planning processes to define organisational goals. + +**2. Integrator** +Functional leaders cultivate analytical depth within a domain. Enterprise leaders integrate the collective knowledge of teams whose domains they may barely understand. The critical skills: grasping competing issues, making trade-offs between legitimate but conflicting priorities, and articulating the rationale behind those trade-offs so that every function feels heard even when the decision goes against them. + +**3. Strategist** +Tactical results are concrete and immediate; strategic outcomes are abstract and delayed. The enterprise leader must resist the seduction of the tactical. Three capabilities matter: toggling fluently between operational detail and strategic perspective, recognising patterns in complex environments, and anticipating how external parties -- competitors, regulators, media -- will respond to organisational decisions. + +**4. Architect** +The enterprise leader thinks in systems, not job descriptions. Changing one element of the organisation -- a reporting structure, a compensation model, a process -- inevitably affects others. Organisational design becomes a primary responsibility, and the leader who lacks fluency in change management will produce cascading unintended consequences. + +**5. Diplomat** +The functional leader defeats competitors. The enterprise leader also manages internal stakeholders -- other senior leaders, business units, and the board -- whose priorities may conflict with one another. Negotiation, persuasion, and alliance-building replace command-and-control as primary instruments. + +**6. Role Model** +At the enterprise level, every word and gesture is amplified. Employees take cues about "right" behaviours from how the senior leader conducts themselves. Self-awareness and empathy become operational requirements, not personality traits. + +**7. Successor Builder** +The goal of leadership, paradoxically, is to make yourself replaceable. Identifying potential successors, assigning stretch projects, and building the leadership pipeline is not a retirement exercise -- it begins the moment you assume the role. Flawed succession processes destroy close to $1 trillion annually in S&P 1500 market value. + +### Leading Former Peers + +When you become the boss of people who were your equals last week, the temptation is to prove yourself through immediate action. Resist it. Build credibility first by meeting people individually and as a team. Listen as much as you talk. Explain how you intend to lead and ask how you can help your new direct reports succeed. The goal is buy-in before strategy -- because strategy without trust is a memo nobody follows. + +If your predecessor was a star, do not attempt to replicate their personality. Being unapologetically yourself -- while being transparent about how your approach will differ -- earns more respect than imitation. + +### The Mental Architecture of Executive Leadership + +The shift is not merely about what you do; it is about how you think. Identify and communicate your core values. Learn to compartmentalise so that a crisis in one domain does not contaminate your judgment in another. Expand self-awareness by paying attention to the narratives you construct about your own career -- the stories you tell yourself about successes and failures shape the leader you become. + +--- + +## Prompts + +**Prompt 1 -- Transition Self-Assessment:** +> I am transitioning from [current role] to [new senior role]. Using the seven role transformations (agenda setter, integrator, strategist, architect, diplomat, role model, successor builder), assess which shifts I have already begun and which I am neglecting. My background is [describe functional expertise and management experience]. For each transformation, identify specific daily behaviours I should start, stop, and continue. Present this as a 90-day transition plan. + +**Prompt 2 -- Former Peer Navigation:** +> I have just been promoted to lead a team of [number] people who were my peers until [timeframe]. Describe the most common relationship dynamics that shift in this situation and design a communication plan for my first two weeks. Include: what to say in the initial team meeting, how to structure individual one-on-ones, and how to handle the colleague who wanted the role I received. + +**Prompt 3 -- Succession Pipeline Design:** +> My company of [size] people has no formal succession plan. Design a succession planning framework that addresses three levels: CEO succession, C-suite succession, and director-level succession. Include criteria for identifying high-potential candidates, development approaches (stretch assignments, rotations, mentoring), and a timeline for implementation. Factor in our current context: [describe industry, growth stage, and any imminent leadership gaps]. + +**Prompt 4 -- Mental Model Shift:** +> I have been in my enterprise leadership role for [duration] and I find myself still defaulting to [describe functional behaviour -- e.g., solving technical problems directly, managing individual contributor work]. Diagnose which of the seven role transformations I am stuck on, explain why my previous success makes this shift difficult, and prescribe specific habits and routines to accelerate the transition. + +--- + +## Use Cases + +**Growth-Stage Founder Moving from CTO to CEO** +A technical cofounder at a 60-person company has been serving as CTO while the board searches for a permanent CEO. The board offers the role to the cofounder. The challenge: every instinct developed over five years of technical leadership now works against them. They must shift from architect to agenda setter, from depth to breadth, from solving to prioritising. The transition plan focuses on the first 90 days: week one establishes the new communication cadence; weeks two through four involve structured listening sessions with every department head; month two introduces the new strategic planning process; month three delivers the first company-wide strategic narrative -- the moment the engineer becomes the enterprise leader. + +**Scale-Stage VP Inheriting a Team of Former Peers** +A VP of Product at a 300-person company is promoted to SVP after the previous leader departs. Three of their four direct reports applied for the same role. The new SVP resists the urge to immediately restructure. Instead, they schedule unhurried one-on-ones with each direct report, opening each conversation by asking: "What do you need from me to succeed?" They are transparent about their leadership approach, acknowledge the awkwardness of the transition, and commit to a feedback rhythm that ensures no one feels blindsided. The colleague who most wanted the role receives a stretch assignment that signals investment, not consolation. + +**Late-Stage Company with No Succession Plan** +A 500-person company's founding CEO announces a two-year retirement timeline. The board has no succession plan. Applying the successor-builder framework, the board immediately begins monitoring the leadership pipeline. Two internal candidates are identified at the C-suite level; a third promising leader at the VP level receives rotational exposure to functions outside their domain. External candidates are benchmarked but not prioritised -- research indicates that outsider CEOs at already-performing companies destroy more value than they create. + +--- + +## Anti-Patterns + +1. **The Hero's Return.** Newly promoted leaders who continue solving problems personally rather than setting agendas and delegating. The rush of direct contribution is addictive -- and organisationally destructive. Every problem you solve is a development opportunity you stole from someone else. + +2. **The Loyalty Test.** Leaders who, upon promotion, immediately restructure teams to surround themselves with allies. This signals insecurity, not strength, and alienates the very people whose institutional knowledge you need most. + +3. **The Deferred Succession.** Treating succession planning as a pre-retirement activity rather than a day-one responsibility. Companies that begin succession planning only when a departure is imminent pay a premium in disruption, talent loss, and value destruction. + +4. **The Strategy Vacation.** Senior leaders who remain perpetually tactical because strategic thinking feels abstract and unrewarding. The seduction of concrete results must be actively resisted -- no one else in the organisation has the mandate to do the strategic work. + +5. **The Replica.** Attempting to clone the style of a successful predecessor. Authenticity outperforms imitation every time, and the organisation needs what you bring, not a diminished copy of what came before. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founder to manager | The first leadership transition: from doing everything to delegating anything. The mental shift from "I can do it better" to "someone else must learn to do it" determines whether the company survives beyond the founder's personal capacity. | +| Growth | Functional to enterprise | The critical transition this skill addresses. Leaders must shed functional identity and adopt systems thinking. The most common failure: promoting the best functional performer into a role that requires entirely different capabilities. | +| Scale | Executive to board-level | At scale, the transition extends to board governance, investor relations, and public representation. The leader becomes diplomat and role model at an institutional scale, where every offhand remark is a signal. | + +--- + +## Output Template + +```markdown +# Leadership Transition Plan + +**Leader:** [Name] +**Transition:** [From Role] to [To Role] +**Date:** [Date] +**Timeline:** [90-day / 6-month] + +## Role Transformation Assessment + +| Transformation | Current Readiness | Key Gap | Priority Action | +|---------------|-------------------|---------|-----------------| +| Agenda Setter | [Low/Medium/High] | [Gap] | [Action] | +| Integrator | [Low/Medium/High] | [Gap] | [Action] | +| Strategist | [Low/Medium/High] | [Gap] | [Action] | +| Architect | [Low/Medium/High] | [Gap] | [Action] | +| Diplomat | [Low/Medium/High] | [Gap] | [Action] | +| Role Model | [Low/Medium/High] | [Gap] | [Action] | +| Successor Builder | [Low/Medium/High] | [Gap] | [Action] | + +## 90-Day Plan + +### Month 1: Listen and Learn +- [Stakeholder meetings scheduled] +- [One-on-one cadence established] +- [Key relationships to build] + +### Month 2: Align and Prioritise +- [Strategic priorities communicated] +- [Quick wins identified] +- [Team structure decisions] + +### Month 3: Execute and Signal +- [First strategic initiative launched] +- [Feedback loop established] +- [Succession pipeline review initiated] + +## Former Peer Dynamics +| Person | Relationship Risk | Approach | +|--------|-------------------|----------| +| [Name] | [Risk] | [Strategy] | + +## Succession Pipeline Status +| Role | Internal Candidates | Development Needed | Timeline | +|------|--------------------|--------------------|----------| +| [Role] | [Names] | [Gaps] | [Months] | +``` + +--- + +## Related Skills + +- **[Leadership Pipeline](../../content/skills/frameworks/leadership-pipeline.md)** -- Provides the theoretical model for leadership passages; this skill translates those passages into daily transition practices. +- **[Leadership Style Adaptation](../../content/skills/leadership/leadership-style-adaptation.md)** -- The transition to senior leadership often requires abandoning a default style that worked at the previous level. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The mental shifts required during transition depend on structured introspection practices covered in this companion skill. +- **[Leadership Voice and Presence](../../content/skills/leadership/leadership-voice-and-presence.md)** -- Senior leaders must develop a new voice -- one that communicates values and vision rather than functional expertise. +- **[Career Strategy for Leaders](../../content/skills/leadership/career-strategy-for-leaders.md)** -- The career fuel audit and success trap identification are directly relevant to the identity recalibration that senior transitions demand. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- The shift from operational execution to strategic oversight is the central challenge of senior transitions; this skill provides the daily habits for operating at strategic altitude. diff --git a/plugins/foreman/skills/shamrock-organisation/SKILL.md b/plugins/foreman/skills/shamrock-organisation/SKILL.md deleted file mode 120000 index 18e5a9a..0000000 --- a/plugins/foreman/skills/shamrock-organisation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/shamrock-organisation.md \ No newline at end of file diff --git a/plugins/foreman/skills/shamrock-organisation/SKILL.md b/plugins/foreman/skills/shamrock-organisation/SKILL.md new file mode 100644 index 0000000..ea6c251 --- /dev/null +++ b/plugins/foreman/skills/shamrock-organisation/SKILL.md @@ -0,0 +1,194 @@ +--- +name: "shamrock-organisation" +description: "Designs workforce architecture using Handy's Shamrock Organisation model with three leaves: professional core, contractual fringe, and flexible labour force. Evaluates which roles belong in each leaf to optimize cost structure, agility, and institutional knowledge. Use when planning first hires, deciding what to outsource, preparing for international expansion, auditing workforce composition, or reducing fixed costs while preserving strategic capability." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - organisational-design + - workforce-strategy + - outsourcing + - flexible-labour + - talent-management +related_skills: + - kaizen-bpr + - systems-thinking + - balanced-scorecard + - disruptive-innovation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Shamrock Organisation + +By 2030, the majority of the global workforce will not hold traditional full-time employment. This is not speculation -- it is the arithmetic consequence of trends already visible in labour statistics across every developed economy. Charles Handy saw it coming in 1989. His model of the Shamrock Organisation, articulated in *The Age of Unreason*, described a workforce structure built on three distinct leaves: a professional core, an outsourced contractual fringe, and a flexible labour force. What seemed provocative in the late twentieth century now reads as operational reality for any startup that has ever hired a freelance designer, contracted a development agency, or employed gig workers for delivery logistics. + +The framework matters for entrepreneurs not as theory but as architecture. How you compose your workforce determines your cost structure, your agility, your culture, and ultimately your capacity to scale. Get the shamrock wrong, and you either bloat with fixed costs or hollow out the capabilities that make your company distinctive. + +--- + +## The Framework + +### Leaf One: The Professional Core + +These are the indispensable people -- the ones who carry the organisation's institutional knowledge, strategic direction, and proprietary capability. They are expensive, difficult to replace, and worth every unit of compensation. + +**Characteristics:** +- Full-time, salaried, deeply embedded in company culture +- Possess knowledge that cannot be easily codified or transferred +- Their departure would create genuine strategic damage +- Compensated through salary, equity, career development, and purpose + +**The entrepreneur's question:** Which roles, if vacated tomorrow, would threaten the company's survival or competitive advantage? Those belong in the core. Everything else is a candidate for the other two leaves. + +In practice, the professional core should be smaller than most founders assume. The instinct to hire full-time for every function is a legacy of industrial-era thinking. Handy argued that the core should shrink to its essential minimum -- and that this minimum would keep shrinking as technology and markets evolve. + +### Leaf Two: The Contractual Fringe + +These are the specialists and service providers engaged through contracts -- agencies, consultancies, outsourced functions. The work is defined, bounded, and governed by deliverables rather than hours. + +**Characteristics:** +- Engaged for specific expertise or capacity that the core does not need permanently +- Managed through outcomes and service-level agreements, not supervision +- Replaceable through market competition (though switching costs vary) +- Paid for results, not presence + +**The entrepreneur's question:** Which functions require specialist expertise we cannot justify building in-house at our current scale? Legal, accounting, specialised engineering, marketing production, and logistics frequently land here. + +The contractual fringe is where startups gain leverage. A five-person company can access enterprise-grade legal counsel, world-class design, and sophisticated financial modelling without carrying the fixed cost. The discipline lies in managing the boundary: what stays contracted and what eventually migrates to the core as the company grows. + +### Leaf Three: The Flexible Labour Force + +These are part-time, temporary, seasonal, or gig workers. They provide elasticity -- the ability to scale capacity up and down without the structural cost of permanent headcount. + +**Characteristics:** +- Engaged by the hour, task, or season +- Minimal training investment; roles are standardised or semi-skilled +- High turnover is expected and managed through systems, not relationships +- Compensated primarily through wages; loyalty is transactional + +**The entrepreneur's question:** Which activities fluctuate in volume and can be performed by workers with limited company-specific knowledge? Customer support overflow, event staffing, warehouse operations, and data entry often fit. + +The ethical dimension deserves attention. Handy himself warned that the flexible leaf risks creating a precariat -- workers with no security, no development, and no stake in the company's success. Entrepreneurs who treat this leaf as disposable labour eventually pay a price in quality, reputation, and regulatory exposure. + +### The Shamrock in Balance + +The three leaves are interdependent. Overweight the core, and fixed costs crush you during downturns. Overweight the fringe, and you lose the institutional knowledge that drives differentiation. Overweight the flexible leaf, and quality deteriorates while your culture evaporates. + +``` + Professional Core + (Knowledge + Strategy) + / \ + / \ + Contractual Fringe Flexible Labour + (Expertise on Demand) (Elastic Capacity) +``` + +The optimal balance shifts with company stage, sector, and strategy. There is no universal ratio, but the diagnostic question remains constant: *Is each role in the leaf where it creates maximum value at minimum structural risk?* + +--- + +## Prompts + +**Prompt 1 -- Workforce Architecture Audit:** +> "Analyse my current team structure: [list roles, employment types, and functions]. Classify each role into one of the three Shamrock Organisation leaves (Professional Core, Contractual Fringe, Flexible Labour). For any role that appears misclassified, explain why and recommend the appropriate leaf, including the transition approach." + +**Prompt 2 -- Scaling Workforce Design:** +> "My company is at [stage] with [number] employees and plans to grow from [current revenue] to [target revenue] in [timeframe]. Using the Shamrock Organisation model, design a workforce architecture that specifies which functions should be core hires, which should be outsourced, and which should use flexible labour. Include the rationale for each classification and the cost implications." + +**Prompt 3 -- Core Identification Stress Test:** +> "For each role in my company [list roles], apply this test: If this person left tomorrow, would we lose (a) proprietary knowledge, (b) strategic capability, or (c) irreplaceable client relationships? Score each role on these three dimensions. Any role scoring low on all three is a candidate for migration to the contractual fringe or flexible leaf." + +**Prompt 4 -- Outsourcing Decision Matrix:** +> "Evaluate these business functions for outsourcing suitability: [list functions]. For each, assess: (1) strategic importance, (2) availability of quality external providers, (3) switching costs, (4) intellectual property risk, and (5) cost differential between in-house and outsourced delivery. Produce a ranked recommendation." + +--- + +## Use Cases + +**Early-Stage SaaS Startup Designing Its First Hires** + +A two-founder SaaS startup with $150K in pre-seed funding must decide where to deploy limited capital. Using the Shamrock model, they identify the professional core as the two founders (product and engineering) plus one critical hire: a senior developer who will own the core platform architecture. The contractual fringe includes a design agency for UI/UX, a fractional CFO for financial planning, and a legal firm for incorporation and IP protection. The flexible leaf covers a part-time customer support representative and a freelance content writer. Total team impact: seven contributors, but only three on payroll. Burn rate drops by 60% compared to hiring all functions full-time. + +**Growth-Stage Marketplace Preparing for International Expansion** + +A marketplace platform with 50 employees and $8M ARR plans to launch in three new European markets. The Shamrock analysis reveals that the professional core -- product, engineering, and data science -- should remain centralised. Local market launch teams belong in the contractual fringe: country managers engaged on 18-month contracts with performance-based renewal, and local marketing agencies handling market-specific campaigns. Driver/courier networks in each market constitute the flexible leaf, scaled through gig-economy infrastructure. This architecture allows the company to test each market with $200K in committed cost rather than $800K in permanent headcount, preserving optionality to exit underperforming markets without restructuring trauma. + +--- + +## Anti-Patterns + +**Core Inflation.** The most common error: treating every hire as a core employee. If your 30-person startup has 28 full-time employees and two contractors, the shamrock has collapsed into a single leaf. Reassess ruthlessly which roles genuinely require permanent, full-time commitment. + +**Outsourcing the Crown Jewels.** Contracting out the functions that constitute your competitive advantage -- the proprietary algorithm, the customer relationship, the brand voice. If it differentiates you, it belongs in the core. The contractual fringe handles commodity functions, not strategic ones. + +**Treating the Flexible Leaf as Disposable.** Building systems that depend on high-turnover workers without investing in the processes, training, and tools that maintain quality. Uber learned that driver experience directly affects rider retention. The flexible leaf requires operational infrastructure even if it does not require organisational commitment. + +**Static Classification.** Assigning roles to leaves once and never revisiting. As a company grows, functions that began in the fringe often need to migrate to the core. The fractional CMO who served well at $1M ARR may need to become a full-time VP Marketing at $5M. Conversely, mature internal functions sometimes become candidates for outsourcing as specialised providers emerge. + +**Ignoring Cultural Consequences.** A workforce where 80% of contributors are non-core creates real challenges for alignment, communication, and shared purpose. The shamrock model is an economic framework, but it has cultural implications that must be actively managed. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Minimise fixed commitments | Almost everything except founder capability sits in the fringe or flexible leaf | +| Validation | Test before you hire | Use contractors to validate demand before converting any role to core | +| Early Traction | Identify the true core | The first three to five non-founder hires define your professional core -- choose with extreme care | +| Growth | Optimise the balance | Systematically evaluate every function's leaf placement; build vendor management capability for the fringe | +| Scale | Institutionalise the model | Formal workforce planning that treats leaf composition as a strategic variable reviewed quarterly | + +--- + +## Output Template + +**Target Audience: Founding Team / COO** + +```markdown +# Workforce Architecture: Shamrock Analysis +## [Company Name] -- [Date] + +### Professional Core (Leaf 1) +| Role | Current Holder | Strategic Justification | Flight Risk | Retention Strategy | +|------|---------------|------------------------|-------------|-------------------| +| [Role] | [Name] | [Why this role is core] | [H/M/L] | [Equity/comp/development plan] | + +### Contractual Fringe (Leaf 2) +| Function | Provider | Contract Type | Annual Cost | Performance Metric | Review Date | +|----------|----------|--------------|-------------|-------------------|-------------| +| [Function] | [Provider] | [Retainer/Project/SLA] | [Cost] | [KPI] | [Date] | + +### Flexible Labour (Leaf 3) +| Function | Source | Volume (FTE equiv.) | Unit Cost | Quality Metric | Scaling Trigger | +|----------|--------|--------------------|-----------|-----------------|-----------------| +| [Function] | [Platform/agency] | [FTE] | [$/hr or $/task] | [Metric] | [When to scale up/down] | + +### Leaf Balance Summary +- Core headcount: [N] ([X]% of total workforce) +- Fringe contributors: [N] ([X]%) +- Flexible contributors: [N] ([X]%) +- Fixed vs. variable labour cost ratio: [X:Y] + +### Migration Candidates +| Role/Function | Current Leaf | Recommended Leaf | Trigger | Timeline | +|---------------|-------------|-----------------|---------|----------| +| [Role] | [Current] | [Recommended] | [What triggers the move] | [When] | +``` + +--- + +## Related Skills + +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Process improvement frameworks that determine which functions can be standardised enough for the contractual fringe or flexible leaf. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Reveals the interdependencies between the three leaves and the feedback loops that maintain or destabilise organisational balance. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Provides the measurement framework for evaluating whether workforce architecture serves strategic objectives across all four performance dimensions. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Effective shamrock design requires leaders to delegate not just tasks but entire functions to the contractual fringe and flexible leaf, trusting outcomes over oversight. +- **[Business Model Canvas](../../content/skills/frameworks/business-model-canvas.md)** -- The Key Resources and Key Activities blocks of the Canvas directly inform which capabilities belong in the professional core versus the contractual fringe. diff --git a/plugins/foreman/skills/situational-leadership/SKILL.md b/plugins/foreman/skills/situational-leadership/SKILL.md deleted file mode 120000 index 35112f0..0000000 --- a/plugins/foreman/skills/situational-leadership/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/situational-leadership.md \ No newline at end of file diff --git a/plugins/foreman/skills/situational-leadership/SKILL.md b/plugins/foreman/skills/situational-leadership/SKILL.md new file mode 100644 index 0000000..8d61580 --- /dev/null +++ b/plugins/foreman/skills/situational-leadership/SKILL.md @@ -0,0 +1,183 @@ +--- +name: "situational-leadership" +description: "Matches leadership style to follower development level using Hersey and Blanchard's Situational Leadership model. Maps four styles -- directing, coaching, supporting, delegating -- to four development levels based on competence and commitment per task. Use when diagnosing style mismatches causing disengagement, assessing delegation readiness, onboarding experienced hires who are new to the domain, or building a management training curriculum." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - leadership + - management + - team-development + - delegation + - coaching +related_skills: + - lewin-leadership-styles + - tuckman-team-stages + - leadership-pipeline + - hackman-enabling-conditions +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Situational Leadership + +When Steve Jobs returned to Apple in 1997, he ran the company with iron-fisted directiveness -- killing product lines, overruling engineers, and making unilateral decisions that saved the company from bankruptcy. A decade later, leading the team that created the iPhone, the same Steve Jobs operated differently: setting the vision, then stepping back to let Jony Ive, Scott Forstall, and their teams execute with extraordinary autonomy. Same leader. Radically different style. The conventional explanation is that Jobs "mellowed." The more precise explanation is that he -- consciously or not -- matched his leadership approach to the situation. Paul Hersey and Ken Blanchard formalized this instinct into Situational Leadership Theory, arguing that there is no single best leadership style. There is only the right style for this person, on this task, at this moment. Leaders who refuse to adapt do not fail because they are bad leaders. They fail because they are inflexible ones. + +--- + +## The Framework + +Situational Leadership maps two variables against each other in a 2x2 matrix: the leader's behavior (task-oriented vs. relationship-oriented) and the follower's development level (competence vs. commitment). The result is four leadership styles, each appropriate for a specific combination of follower readiness. + +### The 2x2 Matrix + +``` + TASK BEHAVIOR (Directive) + Low High + +-----------------+-------------------+ + High | S3: | S2: | + | SUPPORTING | COACHING | + RELATIONSHIP | | | + BEHAVIOR | High rel, | High task, | + (Supportive) | Low task | High rel | + +-----------------+-------------------+ + Low | S4: | S1: | + | DELEGATING | DIRECTING | + | | | + | Low rel, | High task, | + | Low task | Low rel | + +-----------------+-------------------+ + + Applied to follower development: + + D1 (Low competence, High commitment) --> S1: DIRECTING + D2 (Some competence, Low commitment) --> S2: COACHING + D3 (High competence, Variable commit) --> S3: SUPPORTING + D4 (High competence, High commitment) --> S4: DELEGATING +``` + +### The Four Styles in Detail + +**S1: Directing** -- The leader provides specific instructions and closely supervises performance. Communication is primarily one-way. This style works when the follower is enthusiastic but unskilled (a new hire eager to prove themselves, a team member tackling an unfamiliar task). The leader's job is to reduce ambiguity and build competence through clear guidance. + +**S2: Coaching** -- The leader still provides direction but also explains decisions, solicits suggestions, and supports progress. Communication is two-way, though the leader retains decision authority. This style addresses the dangerous D2 zone: the follower has learned enough to recognize how much they don't know, and their initial enthusiasm has dimmed. Coaching prevents the "sophomore slump" that causes so many promising employees to disengage or quit. + +**S3: Supporting** -- The leader shifts from directing to facilitating. The follower has the competence to perform but may lack confidence or motivation. The leader's role becomes encouragement, active listening, and collaborative problem-solving. Day-to-day decisions shift to the follower. The leader's value lies in emotional support and removing obstacles, not in providing technical direction. + +**S4: Delegating** -- The leader turns over responsibility for decisions and implementation. Monitoring is minimal. The follower has both the competence and the commitment to operate independently. The leader's job is to stay available without hovering -- to trust the outcome without controlling the process. This is where many founders struggle most, because letting go feels like losing control. + +### The Development Continuum + +Followers move through development levels on each task -- not globally. A senior engineer might be D4 on backend architecture but D1 on customer-facing presentations. A seasoned marketer might be D4 on campaign strategy but D2 on data analytics. Situational Leadership demands that the leader diagnose development level per task, not per person. This granularity is what separates the framework from simpler leadership models. + +--- + +## Prompts + +**Prompt 1 -- Follower Development Assessment:** +> I have a team member in the role of [role] who is responsible for [key tasks]. For each of their major responsibilities, help me assess their development level (D1-D4) based on these observations: [describe their competence and commitment indicators for each task area]. Then recommend which leadership style (S1-S4) I should use for each task area and what that looks like in practice. + +**Prompt 2 -- Leadership Style Mismatch Diagnosis:** +> I'm experiencing friction with a team member. Here's the situation: [describe the person's role, their behavior, your leadership approach, and the symptoms of the problem -- e.g., missed deadlines, disengagement, defensiveness]. Using the Situational Leadership model, diagnose whether there's a mismatch between my leadership style and their development level. What style should I be using instead, and how do I transition without damaging the relationship? + +**Prompt 3 -- Team-Wide Style Map:** +> Map my entire team using Situational Leadership. Here are my team members and their key responsibilities: [list each person, their role, and 2-3 primary tasks]. For each person-task combination, I'll describe their current competence and commitment: [provide observations]. Create a visual map showing which leadership style I should be using with each person on each task, and identify where I'm likely over-directing or under-supporting. + +**Prompt 4 -- Delegation Readiness Check:** +> I want to delegate [specific responsibility] to [team member]. Their current performance on related tasks is [describe]. Using the Situational Leadership D1-D4 framework, assess whether they're ready for S4 (full delegation) or whether I need an intermediate step. If they're not ready, design a development path -- with specific milestones -- that moves them from their current level to D4 on this responsibility. + +**Prompt 5 -- Founder Scaling Assessment:** +> As a founder of a [stage] startup with [number] employees, I find myself [describe your leadership challenges -- e.g., "still making every product decision," "unable to delegate hiring," "micromanaging the sales team"]. Using Situational Leadership, analyze which of my behaviors represent appropriate directing (because the team genuinely needs it) versus over-directing (because I haven't adjusted my style to match their development). Create a 90-day plan for appropriate style shifts. + +--- + +## Use Cases + +**Engineering Manager Losing a Senior Developer** + +A growth-stage startup's engineering manager is applying S1 (Directing) uniformly to the entire team -- including a senior developer who is clearly D4 on most technical tasks. The senior developer, accustomed to autonomy at her previous company, interprets the detailed task assignments and frequent check-ins as distrust. She begins updating her LinkedIn profile. The Situational Leadership diagnosis is immediate: style-development mismatch. The senior developer needs S4 (Delegating) on technical work and perhaps S2 (Coaching) on the company's specific domain knowledge, which she is still acquiring. Restructuring the relationship -- delegating architecture decisions entirely while coaching on industry context -- reverses the disengagement within weeks. + +**First-Time Sales Hire at an Early-Traction Startup** + +A technical founder hires their first salesperson -- an experienced enterprise seller who negotiated seven-figure deals at a Fortune 500 company. The founder assumes S4 (Delegating) is appropriate: "She's a pro, let her do her thing." Three months later, the pipeline is empty. The diagnosis: while the hire is D4 on enterprise sales mechanics, she is D1 on the startup's product, market, competitive landscape, and the radically different sales cycle of a company with no brand recognition. The founder should have started with S1 (Directing) on product knowledge and market positioning while applying S4 on negotiation and relationship management. The nuance of per-task diagnosis would have prevented a costly quarter. + +**Co-Founder Relationship Strain** + +Two co-founders -- one technical, one commercial -- find themselves in escalating conflict. The technical co-founder applies S1 (Directing) to every product decision, treating the commercial co-founder as D1 on anything product-related. The commercial co-founder, who has strong product instincts shaped by years of customer interaction, feels patronized. Mapping the relationship through Situational Leadership reveals that the commercial co-founder is genuinely D1 on technical architecture but D3-D4 on product-market fit, user experience priorities, and feature prioritization. Disaggregating "product decisions" into sub-domains and applying different styles to each domain transforms the relationship from adversarial to complementary. + +--- + +## Anti-Patterns + +- **The Universal Delegator.** Founders who hire experienced people and immediately apply S4 across the board, assuming that seniority equals readiness in every dimension. Every new hire -- regardless of experience -- is D1 on company-specific knowledge, culture, relationships, and domain nuances. Blanket delegation on day one is not empowerment; it is abandonment. + +- **The Permanent Director.** The inverse pathology: founders who cannot release control regardless of how much their team develops. Every team member receives S1 treatment indefinitely. Competent people leave. Those who stay learn helplessness. The organization becomes a reflection of one person's bandwidth. + +- **Assessing Development Level by Person, Not by Task.** Labeling someone as "a D3" globally rather than recognizing that they may be D4 on some tasks and D1 on others. This coarse-grained assessment leads to uniformly wrong leadership approaches and frustrates team members who feel over-managed in their areas of strength and under-supported in their areas of weakness. + +- **Skipping S2 (Coaching).** Moving directly from S1 (Directing) to S3 (Supporting) or S4 (Delegating) without the critical coaching phase. D2 is the most fragile development stage -- the follower knows enough to be dangerous but not enough to be competent, and their initial enthusiasm has faded. Skipping coaching during this stage is the single most common cause of promising employees failing to develop. + +- **Treating the Model as a Personality Test.** Using Situational Leadership to label people ("She's a D2") as though it describes their character. Development levels are task-specific and temporary. They describe a state, not an identity. Leaders who use D-levels as permanent labels create self-fulfilling prophecies. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Diagnosing first hires | Every new hire requires per-task development assessment; founders must resist defaulting to uniform S1 or S4 | +| Growth | Building a management layer | The framework becomes a tool for training new managers, not just for the founder's direct reports; teaching middle managers to diagnose and adapt is critical | +| Scale | Institutionalizing adaptive leadership | Situational Leadership becomes part of the management training curriculum; the organization develops shared vocabulary for discussing leadership style explicitly | + +--- + +## Output Template + +```markdown +# Situational Leadership Map: [Team/Department Name] + +**Date:** [Date] +**Leader:** [Your name/role] +**Team Size:** [Number] + +## Team Member Development Map + +### [Team Member Name] -- [Role] + +| Task/Responsibility | Competence | Commitment | Development Level | Recommended Style | Current Style | Gap? | +|---------------------|-----------|------------|-------------------|-------------------|---------------|------| +| [Task 1] | [Low/Some/High] | [Low/Variable/High] | [D1/D2/D3/D4] | [S1/S2/S3/S4] | [S1/S2/S3/S4] | [Yes/No] | +| [Task 2] | [Level] | [Level] | [D-level] | [S-style] | [S-style] | [Yes/No] | + +### [Next Team Member]... + +## Priority Mismatches +1. **[Person -- Task]:** Currently using [style], should be using [style]. Impact: [what's going wrong] +2. ... + +## 30-Day Adjustment Plan +- **Week 1-2:** [Specific behavior changes with specific people] +- **Week 3-4:** [Follow-up and assessment of impact] + +## Development Goals +| Team Member | Task | Current Level | Target Level | Timeline | Support Needed | +|-------------|------|---------------|-------------|----------|----------------| +| [Name] | [Task] | [D-level] | [D-level] | [Weeks] | [What you'll provide] | +``` + +--- + +## Related Skills + +- **[Lewin's Leadership Styles](../../content/skills/frameworks/lewin-leadership-styles.md)** -- Lewin provides the foundational taxonomy of leadership styles that Hersey and Blanchard refined into a situational model. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Team development stages interact with individual development levels; a forming team has different leadership needs than a performing one. +- **[Leadership Pipeline](../../content/skills/frameworks/leadership-pipeline.md)** -- As leaders move through pipeline passages, they must learn to apply Situational Leadership at progressively higher organizational levels. +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- The GROW coaching conversation is the primary tool for the S2 (Coaching) style; it provides the structure for developing competence while sustaining commitment. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- S4 (Delegating) is the culmination of the development journey; this skill provides the practical playbook for releasing control while maintaining accountability. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- The S2 and S3 styles require coaching skills that go beyond task direction; mentoring relationships accelerate movement through development levels. diff --git a/plugins/foreman/skills/smart-goals/SKILL.md b/plugins/foreman/skills/smart-goals/SKILL.md deleted file mode 120000 index 64be77d..0000000 --- a/plugins/foreman/skills/smart-goals/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/smart-goals.md \ No newline at end of file diff --git a/plugins/foreman/skills/smart-goals/SKILL.md b/plugins/foreman/skills/smart-goals/SKILL.md new file mode 100644 index 0000000..047e4f3 --- /dev/null +++ b/plugins/foreman/skills/smart-goals/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "smart-goals" +description: "Converts vague objectives into Specific, Measurable, Achievable, Relevant, and Time-bound goals. Provides structure for cascading company-level objectives into team-level commitments with accountability. Use when translating founder vision into execution milestones, aligning departments around shared metrics, converting OKRs into actionable goals, critiquing existing goals for rigour, or establishing quarterly planning discipline." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - goal-setting + - planning + - execution + - performance-management + - accountability +related_skills: + - balanced-scorecard + - hackman-enabling-conditions + - leadership-pipeline +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# SMART Goals + +SMART is the most misused acronym in management. Written on thousands of whiteboards, invoked in millions of performance reviews, and executed properly in perhaps a fraction of those cases. George T. Doran introduced the framework in a 1981 issue of *Management Review* with the paper "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives," offering five criteria that transform vague aspirations into actionable commitments. The concept is straightforward. The application is where organizations fail -- not because SMART is intellectually demanding, but because genuinely specific, measurable goals expose the gap between what people say they want to achieve and what they are actually willing to commit to. Vague goals provide cover. SMART goals provide accountability. Most people, when pressed, prefer the cover. + +--- + +## The Framework + +Each letter in SMART represents one criterion that a well-formed goal must satisfy. The criteria are cumulative: a goal that is Specific and Measurable but not Achievable is a fantasy; one that is Achievable and Time-bound but not Relevant is busywork. + +### S -- Specific + +**The criterion:** The goal must answer the journalist's questions: What will be accomplished? Who is responsible? Where will it happen? Which resources or constraints are involved? + +**The failure mode:** "Improve customer satisfaction." This is not a goal; it is a wish. It specifies neither the dimension of satisfaction to improve, the customer segment, nor the mechanism for improvement. + +**The correction:** "Increase NPS among enterprise customers (500+ employees) from 32 to 45 by redesigning the onboarding flow and adding dedicated customer success managers for accounts above $50K ARR." + +The specificity is uncomfortable. It eliminates ambiguity, which also eliminates the ability to retrospectively redefine success. This is precisely the point. + +### M -- Measurable + +**The criterion:** The goal must include concrete metrics that determine whether it has been achieved. If you cannot measure it, you cannot manage it -- and you cannot honestly assess whether you have succeeded or failed. + +**The failure mode:** "Get better at content marketing." Better than what? Measured how? Compared to whom? + +**The correction:** "Publish 12 long-form articles (2,000+ words) that collectively generate 50,000 organic page views and 500 email signups within 6 months." + +Measurability requires choosing metrics before the work begins. This forces the team to confront what actually matters -- which is often a different conversation than what the original vague goal implied. + +### A -- Achievable (also: Attainable, Assignable) + +**The criterion:** The goal must be realistic given current resources, constraints, and capabilities. Stretch is valuable; delusion is not. The goal should require meaningful effort but not demand miracles or capabilities the team does not possess and cannot develop within the timeframe. + +**The failure mode:** A two-person pre-revenue startup setting a goal of "acquire 100,000 users in Q1" with no marketing budget, no distribution channels, and a product still in beta. + +**The correction:** "Acquire 500 beta users through personal network outreach and three targeted community posts, achieving a 30% activation rate." + +The gap between achievable and ambitious is where goal-setting becomes an act of judgment. Hackman's research on compelling direction found that moderately challenging goals produce the highest performance -- not easy goals (no stretch) or impossible ones (no belief). + +### R -- Relevant + +**The criterion:** The goal must align with broader business objectives, team priorities, and strategic direction. A perfectly specific, measurable, achievable, time-bound goal that does not matter to the business is a well-structured distraction. + +**The failure mode:** An early-traction startup setting a goal to "redesign the entire UI to match current design trends" when the core metric that matters is activation rate, and user research shows that confusion about the product's value proposition -- not visual design -- drives abandonment. + +**The correction:** "Increase activation rate from 15% to 30% by redesigning the first-time user experience to communicate core value within 60 seconds." + +Relevance is the criterion that connects individual and team goals to organizational strategy. Without it, departments optimize locally while the company stagnates globally. + +### T -- Time-bound + +**The criterion:** The goal must have a deadline. Without temporal constraint, goals expand indefinitely, priorities remain vague, and urgency is perpetually deferred. + +**The failure mode:** "Launch the mobile app." When? This year? This decade? Without a deadline, this goal sits comfortably on a roadmap forever, never generating the urgency required for completion. + +**The correction:** "Ship the iOS mobile app to the App Store by March 31, with core features X, Y, and Z functional and passing QA review." + +Time-binding forces scope decisions. When the deadline is fixed, the team must negotiate what is included and excluded -- a far more productive conversation than "we'll ship it when it's ready." + +### The Complete SMART Goal Structure + +``` +[Specific action verb] + [measurable outcome] + [achievable scope] + +[relevant to which strategic priority] + [by when] +``` + +**Example:** "Reduce customer churn rate from 8% monthly to 5% monthly (Specific, Measurable) by implementing an automated re-engagement email sequence and proactive support outreach for at-risk accounts (Achievable scope) -- directly supporting our Q3 objective of improving net revenue retention (Relevant) -- by August 31, 2026 (Time-bound)." + +--- + +## Prompts + +**Prompt 1 -- SMART Goal Conversion:** +> Convert the following vague goals into properly formatted SMART goals for my [stage] startup in the [industry] space. Current goals: [list your current goals as they exist, however vague]. For each, apply all five SMART criteria, flag any goal that cannot be made SMART without additional information, and tell me what information is missing. + +**Prompt 2 -- SMART Goal Hierarchy:** +> I have one company-level objective: [describe]. Help me cascade this into SMART goals for each of my teams: [list teams and their functions]. Each team goal must be SMART on its own while clearly contributing to the company objective. Identify potential conflicts between team goals and recommend resolution approaches. + +**Prompt 3 -- SMART Goal Critique:** +> Review these goals my team has set and rate each on a 1-5 scale for each SMART dimension. Goals: [list goals]. For any dimension scoring below 4, provide a specific revision that would strengthen it. Flag any goals that are well-structured but strategically irrelevant. + +**Prompt 4 -- Quarterly OKR-to-SMART Translation:** +> My company uses OKRs for strategic direction: [list your current OKRs]. Translate each Key Result into one or more SMART goals that would achieve it. For each SMART goal, specify the owner, the metric, the target, and the deadline. Identify Key Results that need to be broken into multiple SMART goals to be actionable. + +**Prompt 5 -- Anti-Vanity SMART Goals:** +> I suspect some of our current goals are vanity metrics in disguise. Here are our goals: [list them]. For each, assess whether the metric being measured actually drives business outcomes or merely looks good in a report. Propose replacement SMART goals that target the underlying outcomes we actually care about. + +--- + +## Use Cases + +**Founder Translating Vision into Execution** + +An idea-stage founder has a compelling vision: "Build the operating system for independent restaurants." The vision is powerful for fundraising but useless for daily execution. SMART goal-setting translates the vision into actionable milestones: "Complete 30 customer discovery interviews with independent restaurant owners in the Austin metro area by April 15" (validation); "Build and deploy an MVP menu management module that 10 pilot restaurants use at least 3 times per week by July 1" (early traction); "Achieve $15K MRR from 50 paying restaurants by December 31" (growth). Each goal satisfies all five criteria and connects back to the vision while remaining concrete enough to execute against. + +**Growth-Stage Company Aligning Departments** + +A 60-person B2B SaaS company finds its marketing, sales, and product teams pulling in different directions. Marketing optimizes for MQLs, sales for closed deals, and product for feature velocity -- with no explicit connection between these efforts. SMART goal-setting at the company level ("Increase net revenue retention from 95% to 110% by Q4") cascades into department-specific SMART goals that are mutually reinforcing: Marketing's goal shifts from MQL volume to "generate 200 qualified trials from ICP accounts by Q3"; Sales' goal becomes "close 40 annual contracts above $25K with less than 45-day sales cycle by Q4"; Product's goal becomes "increase activation rate for new accounts from 40% to 65% by shipping three onboarding improvements by end of Q2." The shared language of SMART prevents the optimization silos that previously fragmented the company. + +--- + +## Anti-Patterns + +- **SMART Goals for Everything.** Not all objectives benefit from the SMART treatment. Exploratory research, creative endeavors, and early-stage customer discovery resist rigid measurement and timelines. Applying SMART to "understand our customer better" produces either meaningless metrics or premature closure of the exploration. Reserve SMART for execution goals, not discovery goals. + +- **Measurable But Meaningless.** Goals that satisfy the M criterion with metrics that do not drive business outcomes. "Post 30 LinkedIn updates per month" is perfectly SMART and potentially worthless. The framework does not evaluate whether the metric chosen is the right metric -- that judgment must come from strategic thinking that precedes SMART formatting. + +- **Gaming the Achievable Criterion.** Setting goals that are comfortably achievable to guarantee success rather than to drive performance. Sandbag targets create an illusion of progress while the organization underperforms its potential. The Achievable criterion means "possible with meaningful effort," not "guaranteed without it." + +- **Annual SMART Goals in Startups.** Setting 12-month goals in environments where the strategy may shift in 6 weeks. Startup SMART goals should have shorter time horizons -- 4 to 12 weeks -- that align with the pace of learning and iteration. Annual goals in a validation-stage startup are fiction. + +- **SMART Without Review Cadence.** Setting SMART goals and not revisiting them until the deadline arrives. Goals without regular check-ins are New Year's resolutions. Weekly or biweekly reviews that assess progress, identify obstacles, and adjust scope (while maintaining the goal's SMART structure) are what make the framework operational rather than aspirational. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Personal founder goals | SMART goals focus on learning objectives: interviews conducted, hypotheses tested, experiments run; the metrics are about discovery, not revenue | +| Validation | Hypothesis-driven goals | Goals center on product-market fit signals: activation rates, retention rates, willingness to pay; time horizons are short (4-8 weeks) | +| Early Traction | Growth and unit economics goals | SMART goals begin to include revenue, CAC, LTV, and retention metrics; team-level goals emerge alongside founder goals | +| Growth | Departmental alignment | SMART goals cascade from company objectives through departments; the challenge is coherence across teams, not individual goal quality | +| Scale | Institutional goal-setting | SMART becomes embedded in performance management, OKR processes, and strategic planning; the risk shifts from vague goals to bureaucratic over-specification | + +--- + +## Output Template + +```markdown +# SMART Goals: [Team/Individual Name] + +**Period:** [Start date -- End date] +**Strategic Context:** [Company-level objective these goals serve] + +## Goal 1: [Goal Name] + +| Criterion | Assessment | +|-----------|-----------| +| **Specific** | [What exactly will be achieved, by whom, through what means] | +| **Measurable** | [Metric: from [current] to [target]] | +| **Achievable** | [Evidence this is realistic: resources available, precedent, capabilities] | +| **Relevant** | [How this connects to strategic priorities] | +| **Time-bound** | [Deadline: specific date] | + +**Full SMART Statement:** [Single sentence combining all five criteria] + +**Milestones:** +- [ ] [Interim milestone 1] -- [Date] +- [ ] [Interim milestone 2] -- [Date] +- [ ] [Final deliverable] -- [Date] + +**Review Cadence:** [Weekly / Biweekly / Monthly] + +## Goal 2: [Goal Name] +... + +## Goal Coherence Check +- [ ] All goals collectively serve the stated strategic context +- [ ] No goal conflicts with another +- [ ] Total goal load is achievable within the time period +- [ ] Metrics chosen drive actual business outcomes, not vanity +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- The Balanced Scorecard provides the strategic context that ensures SMART goals are Relevant; goals across financial, customer, process, and learning perspectives create a complete picture. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman's "compelling direction" condition is fulfilled through well-crafted SMART goals that give teams clear, challenging, consequential objectives. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- The Eisenhower Matrix determines which goals deserve SMART treatment by distinguishing important objectives from urgent distractions that consume goal-setting energy. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- SMART goals are only effective when embedded in a priority system that protects them from scope creep and competing demands. +- **[Wanting What Matters](../../content/skills/thinking/wanting-what-matters.md)** -- Before making goals SMART, leaders must ensure they are pursuing the right objectives; this skill examines whether the goals themselves reflect genuine priorities rather than default expectations. diff --git a/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md b/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md deleted file mode 120000 index 0d73d36..0000000 --- a/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-acceptance-amor-fati.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md b/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md new file mode 100644 index 0000000..9e41492 --- /dev/null +++ b/plugins/foreman/skills/stoic-acceptance-amor-fati/SKILL.md @@ -0,0 +1,203 @@ +--- +name: "stoic-acceptance-amor-fati" +description: "Teaches the advanced Stoic practice of amor fati -- not merely accepting what cannot be changed but actively loving one's fate, including its setbacks, losses, and disappointments. Provides the philosophical foundation for transforming suffering into fuel, releasing attachment to 'what should have been,' and reframing every event as material for growth. Use when an entrepreneur is stuck in resentment over a past failure, when a pivot feels like defeat rather than evolution, when loss or disappointment has calcified into bitterness, when learning-from-failure techniques feel insufficient because the problem is not tactical but existential, or when the founder needs a paradigm shift from enduring fate to embracing it." +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - amor-fati + - acceptance + - fate + - letting-go + - reframing + - loss + - disappointment + - attachment + - stoic + - radical-acceptance +related_skills: + - learning-from-failure + - stoic-fortitude-and-resilience + - stoic-virtue-and-kindness + - stoic-mortality-and-perspective + - growth-mindset +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Acceptance and Amor Fati + +NIETZSCHE'S FIRE. When Friedrich Nietzsche forged his most incandescent formula -- "My formula for greatness in a human being is amor fati: that one wants nothing to be different, not forward, not backward, not in all eternity" -- he was not inventing. He was borrowing. The Stoics had been there two millennia earlier, though they expressed it with less Germanic drama and more Roman discipline. Epictetus put it plainly: "Don't seek for everything to happen as you wish it would, but rather wish that everything happens as it actually will -- then your life will flow well." Marcus Aurelius, governing an empire beset by plague, war, and betrayal, repeated the injunction to himself so often that it became a meditative refrain. The instruction is deceptively simple and operationally ferocious: do not merely accept your fate. Love it. Not the sanitised, comfortable parts -- all of it. The failed fundraise, the departed co-founder, the market that refused to cooperate. This is not resignation dressed in philosophical clothing. It is a fundamentally different relationship with reality, and it separates founders who are consumed by what happened from founders who are fuelled by it. + +--- + +## The Framework + +Amor fati operates at a deeper level than conventional resilience or failure-recovery frameworks. Where practical approaches like post-mortems and pivot analysis address *what to do* after a setback, amor fati addresses *how to relate* to the setback itself. The distinction matters because entrepreneurs who master the tactical response but harbour resentment, regret, or bitterness about what happened carry a weight that no process can remove. + +### The Three Levels of Response to Adversity + +The Stoic tradition reveals a progression, not a single doctrine. Each level is harder than the last, and each yields correspondingly greater freedom. + +**Level 1: Resistance.** The default human response. The event should not have happened. Someone is to blame. If only things had gone differently. This level consumes enormous energy, produces no useful output, and frequently compounds the original problem. Marcus observed: "When you are distressed by an external thing, it's not the thing itself that troubles you, but only your judgment of it." + +**Level 2: Acceptance.** The Stoic baseline. The event happened. It cannot be unhappened. Fighting reality is irrational. One redirects energy from lamenting the past to acting in the present. This is already a significant achievement -- most people never reliably reach it. Acceptance is the foundation of practical frameworks like learning-from-failure. + +**Level 3: Amor Fati.** The Stoic summit. The event happened, and it is *good that it happened* -- not despite the pain, but including the pain. One does not merely tolerate fate; one loves the entire sequence of events that constitutes one's life, recognising that removing any element would produce a different person, a different company, a different trajectory. As Epictetus counselled, the wise person "embraces everything nature assigns." + +### The Mechanics of Amor Fati + +Amor fati is not magical thinking. It operates through four cognitive mechanisms. + +**Reinterpretation of necessity.** Chrysippus offered the analogy of a dog tied to a cart: the cart moves regardless; the dog can be dragged or can walk willingly. The entrepreneur's market, macroeconomy, regulatory environment, and competitive landscape are the cart. Amor fati is walking willingly -- and discovering that willing movement opens degrees of freedom that being dragged forecloses. + +**Dissolution of attachment.** Epictetus diagnosed attachment as the root cause of suffering: "If you hold anything dear outside of your own reasoned choice, you will have destroyed your capacity for choice." The founder attached to a specific outcome (this valuation, this customer, this co-founder) becomes fragile when that outcome fails to materialise. Amor fati dissolves the attachment not by devaluing the outcome but by expanding identity beyond it. You are not your last fundraise. You are the person who navigated whatever the fundraise produced. + +**Integration of the whole path.** Cancer survivors who describe their illness as "the best thing that ever happened to me" are practising amor fati instinctively. Musonius Rufus made the counterintuitive case explicit: "As for me, I would choose being sick over living in luxury, for being sick only harms the body, whereas luxury destroys both the body and the soul." The setback that felt like destruction was, in retrospect, the event that prevented a worse outcome or created a capability that would not otherwise exist. + +**Elimination of hope and fear as equals.** Hecato of Rhodes delivered the most disorienting Stoic insight: "Cease to hope and you will cease to fear." Hope and fear are both projections into a future one does not control. Both are enemies of presence. Amor fati replaces both with engaged participation in what is actually happening. + +### The Difference from Passive Acceptance + +This framework must be distinguished from passivity, fatalism, or learned helplessness -- a confusion that critics of Stoicism regularly exploit. + +| Passive Acceptance | Amor Fati | +|-------------------|-----------| +| "Things happen; there's nothing I can do." | "This happened; I will find the fuel in it." | +| Resignation to circumstances | Engagement with circumstances | +| Energy directed nowhere | Energy directed toward what one controls | +| Diminished agency | Expanded agency within constraints | +| Indifference to outcomes | Commitment to excellent action regardless of outcome | + +Marcus Aurelius did not sit in his tent and accept that the barbarians were at the border. He accepted the fact, loved the challenge it represented, and spent a decade campaigning in the field. FDR did not passively accept polio. He accepted the diagnosis, redirected his energy, and became the president who led America through the Depression and a world war. Amor fati is the most active form of acceptance imaginable. + +### The Glass Is Already Broken + +A Zen story, frequently cited alongside Stoic teaching, captures the practice of pre-emptive amor fati: a master who owned a beautiful cup repeated to himself, "The glass is already broken." He used the cup, enjoyed it, displayed it -- but in his mind it was already gone. When it shattered, he simply said, "Of course." Epictetus counselled the same regarding everything we prize: "Whenever you kiss your child, sibling, or friend, don't layer on top of the experience all the things you might wish, but hold them back and stop them." The instruction is not to love less but to love without the delusion of permanence. + +For the entrepreneur, the glass-already-broken practice applies to customers, employees, funding, market position -- every external asset. Enjoying them fully while acknowledging their impermanence is not pessimism. It is the only honest form of appreciation. And when the glass does break -- when the key hire leaves, the customer churns, the market shifts -- the founder who practised this awareness will recover in days what the unprepared founder mourns for months. + +### The Four Habits of the Stoic Mind + +Marcus Aurelius distilled the daily practice of amor fati into four cognitive habits that serve as a self-diagnostic checklist: + +1. **Accept nothing false or uncertain** -- strip away wishful interpretations and face the situation as it is. +2. **Direct impulses only to acts for the common good** -- ensure that your response to events serves more than your ego. +3. **Limit desires and aversions to what is within your power** -- release attachment to outcomes you cannot determine. +4. **Embrace everything nature assigns** -- this is amor fati itself, the capstone habit that transforms the other three from discipline into disposition. + +--- + +## Prompts + +**Prompt 1 -- Amor Fati Reframe:** +> I am struggling with a past event that I cannot change: [describe -- e.g., a failed startup, a broken partnership, a market timing miss, a personal crisis that derailed the business]. Walk me through the three levels of response: (1) Where am I still in Resistance mode? What judgements, blame, or "if only" thinking am I holding? (2) What does full Acceptance look like for this specific event? (3) What does Amor Fati look like -- how could I not just accept but genuinely love the entire path, including this event, as essential to who I am becoming? Be specific and grounded, not platitudinous. + +**Prompt 2 -- Attachment Inventory:** +> Help me identify my entrepreneurial attachments that are creating fragility. Consider my attachment to: [list -- e.g., a specific valuation target, a particular team member, a market position, a personal identity as "successful founder," a lifestyle standard]. For each attachment, apply Epictetus's test: Is this within my reasoned choice, or outside it? What would my decision-making look like if I released this attachment? What does amor fati say about the possibility that I might lose this thing? + +**Prompt 3 -- Hope-Fear Audit:** +> I am currently hoping for [outcome] and fearing [outcome]. Apply the Stoic insight that hope and fear are the same -- both are projections into a future I do not control. For each, identify: (1) What am I actually able to influence? (2) What would full presence in the current situation look like, stripped of both hope and fear? (3) What actions would I take if I were neither hoping nor fearing, but simply working with what is in front of me right now? + +**Prompt 4 -- Whole-Path Integration:** +> I need help seeing my entrepreneurial journey as a coherent whole rather than a series of wins and losses. My journey so far: [describe key events, including failures and setbacks]. Help me construct the narrative in which every event -- especially the painful ones -- was a necessary chapter. Not a forced positive spin, but a genuine examination of what each setback made possible, what it prevented, and how it shaped the capabilities I now have. What is the story of my path that I can genuinely love? + +--- + +## Use Cases + +**Founder Processing a Company Shutdown** + +After three years and two rounds of funding, a direct-to-consumer brand runs out of capital and shuts down. The founder is devastated -- not just professionally but existentially. Her identity was fused with the company. Applying the amor fati framework in structured sessions with a mentor, she moves through the levels. Level 1 (Resistance): she identifies the blame narratives she is carrying -- the investor who pulled out, the supply-chain disruption, the co-founder who lost commitment. Level 2 (Acceptance): she acknowledges that each of these factors, while real, is now past. No amount of blame will reopen the company. Level 3 (Amor Fati): she maps the capabilities the three years produced -- operational expertise, investor relationships, customer insight, and a clarity about what she actually wants to build next that was impossible before she built and lost the first thing. Six months later, she describes the shutdown as "the tuition I paid for the company I'm building now." + +**Growth-Stage CEO After a Devastating Pivot** + +A B2B SaaS company that spent two years building an enterprise product discovers that the market has shifted and the product's architecture cannot adapt. The CEO must pivot to a different customer segment, effectively abandoning the work of 30 engineers over 18 months. The team's morale fractures. Investors are sceptical. The CEO's own confidence is shaken. Rather than treating the pivot as damage to be managed (a purely tactical response), the CEO applies the amor fati paradigm to the entire organisation. In a transparent all-hands meeting, she reframes: the enterprise phase was not wasted work -- it was the process by which the team developed the technical depth, customer understanding, and organisational resilience that the new direction requires. She names specific capabilities that exist only because of the "failed" effort. The pivot is not a retreat from the original vision but the next chapter in a story that includes the original vision as essential prologue. The reframe does not eliminate disappointment, but it provides a narrative structure within which the team can reengage. + +**Idea-Stage Founder Releasing a Previous Career Identity** + +A senior executive at a Fortune 500 company leaves to pursue an entrepreneurial vision. Eighteen months in, with no revenue and dwindling savings, he finds himself mourning the status, compensation, and certainty of his previous life. The attachment -- to the identity of "successful executive" -- is creating a paralysis that prevents full commitment to the messy, uncertain, low-status reality of building from zero. The amor fati exercise forces a direct confrontation: the corporate career is not an alternative present. It is a past. Wishing it back is as irrational as wishing yesterday's weather were different. The Stoic question is not "Was I happier then?" but "What does this current chapter make possible that the previous one could not?" The answer, once he examines it honestly, includes creative freedom, alignment between work and values, and the chance to test whether his ideas actually work -- none of which were available in the corporate role he romanticises. + +--- + +## Anti-Patterns + +1. **Toxic positivity in philosophical disguise.** Amor fati is not "everything happens for a reason" served with a forced smile. It is a rigorous practice of reinterpretation that acknowledges pain as real and loss as genuine. The founder who uses amor fati to bypass grief, avoid difficult emotions, or dismiss others' suffering has confused philosophy with denial. + +2. **Using acceptance to avoid accountability.** "I accept what happened" is not the same as "I bear no responsibility for what happened." Amor fati includes loving the consequences of one's own mistakes -- which requires first acknowledging them. The Stoic who accepts fate without examining their own contribution to it is practising evasion, not philosophy. + +3. **Premature amor fati.** There is a sequence. Resistance must be acknowledged before it can be released. Acceptance must be achieved before it can be transcended. The founder who leaps to "I love this" while still seething with resentment is performing philosophy rather than practising it. Grant yourself time. Seneca did not expect immediate equanimity. + +4. **Confusing amor fati with the absence of ambition.** Loving your fate does not mean abandoning the desire to shape it. Marcus Aurelius loved his fate and simultaneously worked to improve the empire. Epictetus loved his fate and simultaneously taught thousands. Amor fati is about relationship to what *has happened*, not surrender of what *could happen*. + +5. **Applying amor fati to others' suffering.** Telling a struggling colleague, employee, or co-founder that they should "love their fate" is not wisdom; it is cruelty. Amor fati is a discipline one applies to one's own experience. Others deserve empathy, practical help, and the space to process difficulty on their own terms. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Releasing the previous identity | Most founders at the idea stage are mourning something: a career, a salary, a status, a certainty. Amor fati at this stage means genuinely loving the act of leaving -- not as sacrifice but as liberation. The previous chapter was necessary and is now complete. | +| Validation | Loving the "no" | Validation is a sustained encounter with rejection. Amor fati transforms rejection from evidence of failure into evidence of engagement with reality. Each "no" refines the proposition. The founder who loves the process of discovering what the market actually wants -- rather than resenting the market for not wanting what was offered -- learns faster. | +| Early Traction | Embracing the messy middle | Early traction is neither the excitement of inception nor the vindication of growth. It is operational grind. Amor fati at this stage means finding fuel in the repetitive, unglamorous work of converting initial interest into sustainable revenue. | +| Growth | Integrating the losses that growth entails | Growth always involves loss: the intimate team culture of the early days, the founder's hands-on involvement in every decision, key people who leave because the company has outgrown them. Amor fati means loving the full trajectory, not just the growth metrics. | +| Scale | Accepting the company's independence from the founder | At scale, the company becomes an entity that operates beyond the founder's direct control. Amor fati at this stage means loving the fact that the organisation has its own momentum, its own culture, its own trajectory -- even when that trajectory diverges from the founder's original vision. | + +A note on progression: amor fati does not arrive as a permanent state. It is a practice that must be renewed with each new challenge. The founder who achieved genuine acceptance after a failed fundraise may find themselves in full resistance mode after a co-founder departure. This is normal. The practice is the return -- the repeated movement from resistance through acceptance toward love -- not a destination from which one never retreats. + +--- + +## Output Template + +```markdown +# Amor Fati Assessment + +**Founder:** [Name] +**Date:** [Date] +**Event Under Examination:** [The setback, loss, or disappointment being processed] + +## Current Level of Response +- [ ] Level 1: Resistance (blame, "if only," resentment still active) +- [ ] Level 2: Acceptance (event acknowledged as past, energy redirected) +- [ ] Level 3: Amor Fati (event embraced as essential chapter) + +## Resistance Inventory +| Residual Resistance | Source | What Releasing It Would Free | +|---------------------|--------|------------------------------| +| [Blame/resentment/regret] | [Person/event/decision] | [Energy/clarity/action it currently blocks] | + +## Attachment Audit +| Attachment | Inside Reasoned Choice? | Risk of Loss | What Releasing It Enables | +|-----------|------------------------|--------------|--------------------------| +| [Specific attachment] | Yes / No | [High/Medium/Low] | [Freedom/clarity gained] | + +## Whole-Path Integration +- **What this event made possible:** [Capabilities, insights, relationships that exist only because of it] +- **What this event prevented:** [Worse outcomes that the setback inadvertently avoided] +- **The narrative I can genuinely love:** [The honest, complete story of the path] + +## Present-Moment Focus +- **What I am hoping for (and releasing):** [Projection into future] +- **What I am fearing (and releasing):** [Projection into future] +- **What I can act on right now:** [Actions within reasoned choice, today] +``` + +--- + +## Related Skills + +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Covers the practical mechanics of failure response; this skill provides the philosophical foundation that makes those practices stick by transforming the emotional relationship with failure itself. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- Fortitude is the capacity to endure adversity; amor fati is the capacity to embrace it. The progression from endurance to love is the difference between surviving and being transformed. +- **[Stoic Virtue and Kindness](../../content/skills/stoic/stoic-virtue-and-kindness.md)** -- Virtue requires a settled relationship with one's circumstances; the entrepreneur consumed by resentment cannot practise justice or wisdom in the present. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's framework posits that challenges are opportunities for growth; amor fati takes this further, treating challenges as not merely useful but loveable. +- **[Stoic Mortality and Perspective](../../content/skills/stoic/stoic-mortality-and-perspective.md)** -- The awareness that life is finite gives amor fati its urgency; every hour spent in resentment is an hour subtracted from a brief, unrepeatable span. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- The philosophical discipline of embracing rather than resisting fate provides leaders with the emotional grounding to model calm during organisational transitions. diff --git a/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md b/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md deleted file mode 120000 index b690d26..0000000 --- a/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-control-and-clarity.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md b/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md new file mode 100644 index 0000000..916940e --- /dev/null +++ b/plugins/foreman/skills/stoic-control-and-clarity/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "stoic-control-and-clarity" +description: "Applies Epictetus's dichotomy of control to entrepreneurial decision-making, separating what founders can influence from what they cannot. Synthesises the foundational Stoic practice of mental clarity through intentionality, purpose, and disciplined focus. Use when overwhelmed by variables outside your control, paralysed by uncertainty, struggling to prioritise amid chaos, losing focus on core purpose, or needing a philosophical framework for saying no." +version: "1.0.0" +category: "stoic" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - dichotomy-of-control + - clarity + - focus + - prioritisation + - decision-making + - intentionality + - epictetus +related_skills: + - stoic-emotional-mastery + - stoic-self-awareness + - stoic-unbiased-thought + - leader-resilience-and-wellbeing + - leader-self-reflection + - focus-and-priority-management + - eisenhower-matrix + - covey-seven-habits +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Dichotomy of Control + +All of Stoic philosophy can be summarised in a single sentence, and that sentence is the first lesson every entrepreneur needs. Epictetus opens the *Enchiridion* with it: "Some things are in our control, while others are not." That's it. The entire philosophical tradition -- twenty-three centuries of it -- rests on the ability to draw one clean line between what you can change and what you cannot. Most founders spend the better part of their careers hurling themselves at the wrong side of that line, expending energy on market conditions they cannot alter, competitors they cannot silence, and investor sentiment they cannot manufacture. The dichotomy of control is not merely a Stoic concept. It is the operating system upon which every other Stoic concept runs. + +--- + +## The Framework + +### The Line That Governs Everything + +Epictetus divides the universe into two domains with surgical precision: + +| Within Your Control | Outside Your Control | +|---|---| +| Your judgments and opinions | Other people's judgments and opinions | +| Your choices and intentions | Market conditions and macroeconomics | +| Your effort and preparation | Outcomes and results | +| Your responses to events | The events themselves | +| How you spend your attention | What others do with theirs | + +The key insight is not merely intellectual but operational. Marcus Aurelius condensed the framework into three imperatives that function as a daily protocol: *Control your perceptions. Direct your actions properly. Willingly accept what is outside your control.* That trio -- perception, action, will -- structures the entirety of Stoic practice. + +### The Seven Functions of the Mind + +Epictetus identifies seven capacities that constitute the mind's proper work, each of which falls squarely within the circle of control: + +1. **Choice** -- to do and think rightly +2. **Refusal** -- to resist temptation and distraction +3. **Yearning** -- to improve and grow +4. **Repulsion** -- to reject negativity and falsehood +5. **Preparation** -- to ready oneself for what lies ahead +6. **Purpose** -- to maintain a guiding principle +7. **Assent** -- to distinguish what is and is not within one's power + +Everything outside these seven functions is, in Epictetus's blunt assessment, "pollution." For the entrepreneur, this taxonomy provides a diagnostic: when something feels wrong, which of these seven has been neglected or corrupted? The founder who cannot say no to distracting opportunities has a refusal problem. The one who drifts between strategies has a purpose problem. The one who is blindsided by foreseeable obstacles has a preparation problem. Naming the function is the first step toward restoring it. + +### Clarity Through Intentionality + +Seneca warns that "it is not activity that disturbs people, but false conceptions of things that drive them mad." The distinction matters. Busyness is not the same as purposeful action. The founder who answers every email, attends every meeting, and chases every opportunity is not diligent -- they are directionless. The Stoic antidote is *euthymia*, which Seneca defines as "believing in yourself and trusting that you are on the right path, and not being in doubt by following the myriad footpaths of those wandering in every direction." + +Euthymia is not confidence. It is the byproduct of having done the work of clarity -- of knowing what you are building, why you are building it, and what you are willing to refuse in order to build it well. The entrepreneur who has achieved euthymia can say no without guilt, because the no is in service of a deliberate yes. + +### The Discipline of Saying No + +"How many have laid waste to your life when you weren't aware of what you were losing," Seneca writes, "how much was wasted in pointless grief, foolish joy, greedy desire, and social amusements." The Stoics treat attention as a finite and non-renewable resource. Every yes to an inessential obligation is a no to something that matters. Every hour spent monitoring news that cannot affect your actions is an hour stolen from work that can. + +This is not austerity for its own sake. It is the recognition that clarity is a precondition for effectiveness, and clarity requires the ruthless elimination of noise. + +--- + +## Prompts + +**Prompt 1 -- Control Audit:** +> List every major concern, stressor, and preoccupation I currently face as a founder of [company] at [stage]. For each, classify it as either "within my control" (my choices, efforts, judgments, responses) or "outside my control" (market, competitors, others' opinions, outcomes). For items outside my control, suggest how I can redirect that energy toward a controllable variable that influences the same domain. + +**Prompt 2 -- Intentionality Filter:** +> Review my current commitments and recurring activities as CEO of [company]: [list activities]. Apply the Stoic test of intentionality to each -- does this activity serve my core purpose, or is it habit, social obligation, or fear of missing out? Recommend what to eliminate, delegate, or reduce, and explain the clarity gained by each removal. + +**Prompt 3 -- Seven Functions Diagnostic:** +> Using Epictetus's seven functions of the mind (choice, refusal, yearning, repulsion, preparation, purpose, assent), assess my current decision-making situation: [describe situation]. Which functions am I exercising well? Which am I neglecting? Provide specific Stoic-informed recommendations for strengthening the weakest function. + +**Prompt 4 -- Euthymia Check:** +> I am experiencing doubt about my direction as founder of [company]. Apply Seneca's concept of euthymia to help me distinguish between productive strategic questioning and destructive comparison with others' paths. What is genuinely mine to reconsider, and what is noise generated by observing competitors, peers, or market commentary? + +--- + +## Use Cases + +**Seed-stage founder paralysed by competitor activity** + +A pre-revenue SaaS founder discovers that a well-funded competitor has launched a feature set nearly identical to his planned roadmap. He spirals into reactive mode -- revising timelines, second-guessing positioning, considering pivots. Applying the dichotomy of control reframes the situation: the competitor's actions, funding, and market reception are entirely outside his control. His own product quality, customer relationships, speed of iteration, and clarity of value proposition are within it. The audit reveals that 70% of his mental energy over the past week has been directed at things he cannot influence. Redirecting that energy toward controllable variables -- particularly preparation and purpose -- restores both momentum and composure. + +**Growth-stage CEO drowning in obligations** + +A Series B CEO finds herself attending twelve standing meetings per week, responding to investor updates, mentoring three direct reports, speaking at two conferences per month, and serving on an advisory board. She is exhausted and losing strategic clarity. The Stoic intentionality filter reveals that six of those commitments exist not because they serve her purpose but because she never examined whether they should. Three are habit. Two are vanity. One is guilt. By applying the discipline of refusal, she reclaims fifteen hours per week -- enough to restore the deep thinking that made her company worth funding in the first place. + +**Scale-stage executive facing regulatory uncertainty** + +The CEO of a fintech company at scale faces a pending regulatory change that could fundamentally alter the business model. The entire leadership team is consumed by anxiety about possible outcomes. The dichotomy of control provides the structural intervention: the regulation itself is outside their control, but their preparation for multiple scenarios, the quality of their legal counsel, and the adaptability of their architecture are firmly within it. The framework converts paralysing uncertainty into an actionable preparation agenda. + +--- + +## Anti-Patterns + +**1. Confusing acceptance with passivity.** The dichotomy of control does not counsel inaction. Accepting that you cannot control an outcome is not the same as declining to influence it. You cannot control whether an investor says yes, but you can control the quality of your pitch, the rigour of your preparation, and the timing of your ask. The Stoic acts fully within their sphere and then releases attachment to the result. + +**2. Using "outside my control" as an excuse.** Some founders discover the dichotomy and immediately use it to abdicate responsibility. Revenue targets missed? "Outside my control." Team attrition? "Can't control people." This is a corruption of the framework. The honest audit almost always reveals controllable factors -- your hiring practices, your management quality, your strategic choices -- that contributed to the outcome. + +**3. Applying the framework once and considering it done.** The dichotomy of control is not a one-time exercise. Epictetus recommended revisiting it at morning, midday, afternoon, and evening. The boundary between controllable and uncontrollable shifts as circumstances change. What was outside your control last quarter may be within it now, and vice versa. + +**4. Neglecting the emotional dimension.** The dichotomy is an intellectual tool, but its application is emotional. Knowing that a bad review is outside your control does not automatically prevent it from ruining your day. The framework must be paired with the emotional mastery practices of Stoic philosophy (see stoic-emotional-mastery) to be fully effective. + +**5. Drawing the line in self-serving places.** The audit is only as honest as the person conducting it. Founders sometimes classify uncomfortable controllables (their own communication failures, their hiring mistakes) as uncontrollable "team dynamics" or "market conditions." The dichotomy demands ruthless honesty about where the line actually falls, not where it would be convenient for it to fall. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Separating vision validation from market prediction | Nearly everything is uncertain; the dichotomy helps you focus on the few things you can actually test rather than speculating about the many things you cannot know | +| Validation | Controlling experiment design, not outcomes | The temptation to interpret ambiguous signals as validation is strongest here; the framework demands honesty about what the data actually says versus what you hope it says | +| Early Traction | Focusing effort on repeatable processes | As controllable variables multiply (team, product, customers), the audit becomes a prioritisation tool -- which controllables deserve the most energy? | +| Growth | Managing the expanding boundary of influence | More resources mean more things fall within your sphere of influence; the discipline shifts from acceptance to strategic allocation | +| Scale | Institutional clarity amid organisational complexity | At scale, the dichotomy must be embedded in organisational culture, not just individual practice; leadership teams need shared language for what the company can and cannot control | + +The idea-stage founder faces the starkest version of the dichotomy: almost nothing is within control except the quality of thinking and the willingness to test. This is precisely why the framework is most powerful at this stage. It strips away the fantasy of control that leads to premature scaling, over-investment in unvalidated assumptions, and the emotional devastation of early failure. + +At growth and scale, the challenge inverts. The founder now has genuine influence over a wider set of variables but risks the illusion that control extends further than it does. Regulatory environments, macroeconomic conditions, and cultural shifts remain firmly outside the circle, no matter how large the company becomes. + +At early traction, the dichotomy becomes a team discipline. The founder who has internalised the framework must now teach it -- implicitly or explicitly -- to the first ten, twenty, fifty employees. When a sales team obsesses over a prospect's internal politics (uncontrollable) rather than the quality of the demo and follow-up (controllable), the dichotomy provides the coaching language. "What can we actually do here?" is a question that, repeated often enough, reshapes how an entire organisation allocates its cognitive and emotional resources. + +--- + +## Output Template + +```markdown +# Dichotomy of Control Audit -- [Situation/Decision] + +**Date:** [Date] +**Context:** [Brief description of the situation prompting this audit] + +## Current Concerns Inventory + +| Concern | Within My Control? | Controllable Lever | Energy Currently Spent (H/M/L) | +|---------|-------------------|--------------------|---------------------------------| +| [Concern 1] | Yes / No | [If no, identify the nearest controllable variable] | [H/M/L] | +| [Concern 2] | Yes / No | [Controllable lever] | [H/M/L] | +| [Concern 3] | Yes / No | [Controllable lever] | [H/M/L] | + +## Energy Reallocation Plan + +**Percentage of energy currently directed at uncontrollables:** [X%] +**Target percentage:** [Y%] + +| Stop (Release) | Start (Redirect) | Expected Clarity Gain | +|----------------|-------------------|----------------------| +| [Uncontrollable concern] | [Controllable action] | [What becomes clearer] | + +## Seven Functions Check + +| Function | Status | Action Required | +|----------|--------|-----------------| +| Choice | [Strong / Needs attention] | [Specific action] | +| Refusal | [Strong / Needs attention] | [Specific action] | +| Yearning | [Strong / Needs attention] | [Specific action] | +| Repulsion | [Strong / Needs attention] | [Specific action] | +| Preparation | [Strong / Needs attention] | [Specific action] | +| Purpose | [Strong / Needs attention] | [Specific action] | +| Assent | [Strong / Needs attention] | [Specific action] | + +## Euthymia Statement +[One sentence defining your path and the commitment to stay on it] +``` + +--- + +## Related Skills + +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- Knowing what is outside your control is step one; managing the emotional response to that knowledge is step two. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- The dichotomy of control requires honest self-assessment to apply accurately; self-deception corrupts the audit. +- **[Stoic Unbiased Thought](../../content/skills/stoic/stoic-unbiased-thought.md)** -- Seeing events as they are, stripped of judgment, is a prerequisite for correctly classifying them as controllable or not. +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Daily resilience practices are the tactical complement to the Stoic philosophical framework on control. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Operational prioritisation tools that benefit from the Stoic clarity about what actually deserves attention. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- The urgent/important distinction maps naturally onto the Stoic separation of controllables from uncontrollables. +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- The four biological defaults that distort thinking are precisely the forces that blur the line between what is and is not within your control. diff --git a/plugins/foreman/skills/stoic-duty-and-service/SKILL.md b/plugins/foreman/skills/stoic-duty-and-service/SKILL.md deleted file mode 120000 index ac87c14..0000000 --- a/plugins/foreman/skills/stoic-duty-and-service/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-duty-and-service.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-duty-and-service/SKILL.md b/plugins/foreman/skills/stoic-duty-and-service/SKILL.md new file mode 100644 index 0000000..40b1921 --- /dev/null +++ b/plugins/foreman/skills/stoic-duty-and-service/SKILL.md @@ -0,0 +1,201 @@ +--- +name: "stoic-duty-and-service" +description: "Explores the Stoic conception of duty, sympatheia (universal interconnection), and service-oriented leadership as the foundation of entrepreneurial purpose. Use when founders struggle with motivation beyond profit, when leadership feels like burden rather than calling, when building a culture of accountability and mutual obligation, when navigating tensions between personal ambition and collective responsibility, or when aligning team purpose with organisational mission." +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - duty + - service + - leadership + - purpose + - accountability + - team-culture + - sympatheia + - obligation +related_skills: + - stoic-right-action + - stoic-problem-solving + - stoic-pragmatism + - purpose-driven-leadership + - delegation-and-empowerment + - team-culture-and-dynamics +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Duty and Service + +The Stoics believed life is a debt -- and the repayment is service to others. This was not sentimentality. Marcus Aurelius, who could have spent his reign in palaces eating grapes, instead spent it on the frozen Danube frontier, adjudicating legal disputes and commanding legions against Germanic tribes. He did this not because he enjoyed it (his private journals make clear he often did not) but because it was his duty. The Greek word he used was *praxeis koinonikas apodidonai* -- to render works held in common. Epictetus, a former slave who had every reason to reject the social contract, taught duty with even greater intensity: your station is assigned; excellence lies in how you occupy it. For the entrepreneur, who has voluntarily assumed responsibility for employees, investors, customers, and a mission, the Stoic framework of duty transforms obligation from weight into architecture -- the very structure that gives the enterprise meaning. + +--- + +## The Framework + +Stoic duty operates at three concentric levels, each one expanding the founder's sense of purpose beyond the self. + +### Level 1: Sympatheia -- The Interconnected Whole + +> "Meditate often on the interconnectedness and mutual interdependence of all things in the universe." -- Marcus Aurelius, *Meditations*, 6.38 + +Sympatheia is the Stoic doctrine of universal interconnection -- the recognition that every person, event, and action is part of a single, interdependent system. This is not mysticism. It is systems thinking expressed in ancient Greek. The founder who grasps sympatheia understands that their company is not an island. It exists within a web of suppliers, customers, communities, ecosystems, and human lives. Every decision propagates outward through that web. Hiring decisions shape families. Pricing decisions shape markets. Product decisions shape behaviour. + +The practical consequence: the founder cannot claim ignorance of second-order effects. The Stoic does not say "that is not my problem." If it touches the system, it touches you. + +Modern systems thinking arrived at the same conclusion through different language. The difference is that the Stoics added a moral dimension: interconnection creates obligation. Awareness of the web is not merely strategic intelligence -- it is the foundation of duty. You cannot serve what you cannot see, and you cannot claim exemption from what you have seen. + +### Level 2: The Assigned Role + +> "Whatever anyone does or says, for my part I'm bound to the good. In the same way an emerald or gold or purple might always proclaim: 'whatever anyone does or says, I must be what I am and show my true colors.'" -- Marcus Aurelius, *Meditations*, 7.15 + +The Stoics held that every person occupies a role in the larger order. That role comes with obligations that persist regardless of mood, circumstance, or personal convenience. Marcus Aurelius governed when he would have preferred to philosophise. Seneca wrote and taught when he would have preferred retirement. Epictetus taught in exile, in poverty, with a crippled leg. + +For the founder, the assigned role is not "CEO" or "founder" -- those are titles. The role is steward. Steward of other people's livelihoods, of investor capital, of customer trust, of a mission that transcends any single person's career. As Seneca bluntly put it: "Never shirk the proper dispatch of your duty, no matter if you are freezing or hot, groggy or well-rested, vilified or praised, not even if dying or pressed by other demands." The Stoic insight: duty is not a constraint on freedom. It is the very thing that makes freedom purposeful rather than aimless. + +Marcus Aurelius's morning ritual captures this precisely. When tempted to stay in bed, he would remind himself: "I am awakening to the work of a human being. Why then am I annoyed that I am going to do what I'm made for, the very things for which I was put into this world?" + +The Israeli general Herzl Halevi reflected this same principle in modern military leadership: "People used to tell me that business administration is for the practical life and philosophy is for the spirit. Through the years I found it is exactly the opposite -- I used philosophy much more practically." The role demands the philosophy. The philosophy sustains the role. Duty and capability are mutually reinforcing, not competing demands. + +### Level 3: Service Without Scorekeeping + +> "One person, on doing well by others, immediately accounts the expected favour in return. Another is not so quick, but still considers the person a debtor and knows the favour. A third kind of person acts as if not conscious of the deed, rather like a vine producing a cluster of grapes without making further demands." -- Marcus Aurelius, *Meditations*, 5.6 + +Marcus describes three types of givers, and his preference is unmistakable. The highest form of service is unconscious of itself -- the vine that produces grapes because that is what vines do, not because it expects applause. Translated to leadership: the founder who helps a struggling employee, who gives a competitor honest advice, who invests time in a mentee with no strategic value, is practising Stoic service. + +This is not altruism in the conventional sense. The Stoics were not naive about human nature. Nor is it strategic generosity -- the calculated giving that expects reciprocity on a longer timeline. The argument is functional: the person who serves without expectation of return operates with maximum psychological freedom. They are not waiting for validation, not keeping score, not adjusting their behaviour based on whether the last favour was reciprocated. They are free to act correctly in every situation because their motivation is internal. + +### The Obligation-Choice Paradox + +A critical nuance distinguishes Stoic duty from grim compliance. Seneca wrote: "Nothing is noble if it's done unwillingly or under compulsion. Every noble deed is voluntary." The paradox: duty is obligatory, yet it must be chosen freely to have moral weight. + +The resolution lies in reframing. The founder does not *have to* lead the company through a crisis. The founder *gets to*. This is not linguistic trickery. It reflects a genuine shift in perception -- from burden to privilege, from obligation to purpose. Epictetus articulated the principle: "Bring our will into harmony with whatever happens, so that nothing happens against our will." + +The practical test: when a founder consistently experiences their duties as burdens, something is misaligned -- either the role is wrong, the mission is unclear, or the founder's relationship to service needs examination. + +### The Injustice of Inaction + +Marcus Aurelius added a dimension to duty that many entrepreneurs overlook: "Often injustice lies in what you aren't doing, not only in what you are doing." The sin of omission. The founder who sees a team member struggling and says nothing. The leader who knows the product has a defect and delays the fix. The CEO who witnesses harassment and defers to HR rather than acting. Duty is not merely the avoidance of wrong; it is the active pursuit of right. The Stoic obligation is affirmative: you must be a force for good, not merely the absence of harm. + +This principle is particularly relevant at scale, where the founder's physical distance from day-to-day operations can create moral distance. The duty does not diminish with organisational layers. It intensifies, because the leader's inaction now affects not individuals but systems. + +--- + +## Prompts + +**Prompt 1 -- Duty Mapping:** +> "Map the concentric circles of my duty as a founder. My company is [describe company, stage, team size, mission]. Starting from the innermost circle (self-governance) and moving outward (co-founders, team, customers, investors, community, industry), identify my specific obligations at each level. For each circle, distinguish between duties I am fulfilling well and duties I am neglecting. Be candid." + +**Prompt 2 -- Sympatheia Impact Analysis:** +> "Apply the Stoic principle of sympatheia to a major decision we are about to make: [describe decision]. Trace the second and third-order effects of this decision across our stakeholder web -- employees, customers, suppliers, competitors, community. Identify effects we may be ignoring because they fall outside our immediate line of sight. Where are we failing to see the interconnection?" + +**Prompt 3 -- Service Audit:** +> "Evaluate my leadership against Marcus Aurelius's three types of givers. Over the past quarter, categorise my significant acts of service to my team and stakeholders: (1) acts done with explicit expectation of return, (2) acts done with silent scorekeeping, (3) acts done like the vine -- without thought of recognition. What does the distribution reveal about my leadership? How do I shift more of my service into the third category?" + +**Prompt 4 -- Have-To vs. Get-To Reframe:** +> "Here are the five duties in my role that currently feel most burdensome: [list duties]. For each one, help me apply the Stoic reframe from 'have to' to 'get to.' This is not about forced positivity -- it is about identifying the genuine privilege and purpose embedded in each obligation. Where the reframe fails, flag the duty as potentially misaligned with my actual role." + +--- + +## Use Cases + +**The Reluctant Leader** + +A technical co-founder at an early-traction robotics startup finds herself promoted to CEO after the business-focused co-founder departs. She resents the administrative burden -- fundraising, board management, HR issues -- and fantasises about returning to pure engineering. Stoic duty reframes this not as a career detour but as a station assigned by circumstance. Marcus Aurelius did not choose to be emperor; the role was imposed by adoption and succession. Yet he governed with full commitment because the role demanded it. The technical co-founder applies the same logic: the company's twenty employees depend on her stewardship. Her engineering brilliance is necessary but insufficient; the organisation needs leadership, and she is the one positioned to provide it. She hires a COO to handle operations she is least suited for (pragmatic delegation, not abdication), while embracing her duty to set vision, make hard calls, and represent the company to investors. The resentment does not vanish overnight. But the reframe from burden to purpose provides the psychological scaffolding to endure and, eventually, to thrive. + +**The Profitable Exit vs. The Team** + +A growth-stage edtech company receives an acquisition offer that would make the two co-founders personally wealthy. The acquiring company, however, plans to relocate operations to a different country, which would result in the termination of 60% of the current team. The co-founders face a direct conflict between personal interest and duty to their employees. Stoic sympatheia demands that they see the interconnection: these employees relocated for the company, recommended friends for hire, invested their careers in the mission. Justice -- the cardinal virtue -- requires that the co-founders at minimum negotiate retention terms, transition support, and severance. Some founders in this position have declined acquisitions entirely, judging that the duty to their team outweighed the personal windfall. Others have negotiated terms that honoured both interests. The Stoic framework does not prescribe a single answer. It insists that the duty be weighed, not ignored. + +**The Investor Pressure to Compromise** + +A scale-stage climate-tech company's lead investor pressures the founder to abandon the company's open-source commitments in favour of a proprietary model that would accelerate revenue. The founder recognises the tension between duty to shareholders (fiduciary obligation) and duty to the broader community (the open-source ecosystem that contributed to the company's success). Marcus Aurelius's concept of sympatheia illuminates the web: the open-source community provided talent, feedback, and credibility. Abandoning it is not merely a strategic pivot; it is a severance of reciprocal obligation. The founder presents the board with a hybrid model that preserves core open-source commitments while monetising enterprise features. The duty is honoured on both fronts -- not perfectly, but honestly. + +--- + +## Anti-Patterns + +**Martyrdom as Identity.** Some founders wear their sacrifices like medals, broadcasting how much they have given up for the company. This is Marcus's first type of giver -- the one who "immediately accounts the expected favour in return." Stoic duty is quiet. The moment service becomes a performance, it has ceased to be service and become marketing for the founder's ego. + +**Duty Without Boundaries.** The Stoics did not advocate self-destruction. Marcus Aurelius insisted on the distinction between duty to others and duty to oneself. A founder who works 100-hour weeks, neglects health, and destroys personal relationships in the name of "duty" has confused obligation with self-harm. Seneca's counsel is direct: "Philosophy calls for simple living, but not for penance." Sustainable duty requires sustainable leaders. + +**Conflating Duty With Control.** Duty to one's team does not mean making every decision for them. Marcus observed that "the ruling reason in each of us is master of its own affairs." The founder's duty is to create conditions for others to fulfil their own duties -- to hire well, set clear expectations, provide resources, and then trust the system. Micromanagement is not service; it is the failure to trust others with their own assigned roles. + +**Selective Sympatheia.** Recognising interconnection only when it is convenient -- caring about second-order effects on customers but ignoring second-order effects on suppliers; valuing team wellbeing but dismissing community impact -- is not sympatheia. It is marketing dressed as philosophy. The Stoic web of obligation does not have opt-out clauses. + +**Obligating Others to Your Standard.** The founder who has internalised Stoic duty sometimes falls into the trap of expecting identical commitment from employees. Marcus's meditations are self-directed. He does not demand that his generals read philosophy. Musonius Rufus acknowledged that "some people are sharp and others dull; some are raised in a better environment, others in worse." The duty to understand others' circumstances is itself part of the Stoic obligation. + +**Duty as Guilt Instrument.** Reminding employees of what the company has done for them -- opportunities provided, salaries paid, growth enabled -- in order to extract extra commitment is not Stoic duty. It is debt creation masquerading as generosity. The vine, in Marcus's metaphor, does not invoice the person who eats the grape. Service given with an implicit ledger is not service at all. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Clarifying the purpose behind the venture -- is it service or self-aggrandisement? | Duty at the idea stage is primarily to honesty: does this idea serve a genuine need, or is it a vehicle for personal ambition dressed as mission? | +| Validation | Duty to the early adopters who are investing their time and trust | The first customers are partners, not transactions. The founder's duty is to honour their feedback with genuine responsiveness, not selective listening | +| Early Traction | Duty to the first employees who took the risk of joining | These people left stable employment for a promise. The founder's obligation is to steward their careers, not merely extract their labour | +| Growth | Balancing duties to an expanding stakeholder web -- investors, larger teams, communities | The hardest transition: duty was personal and direct at earlier stages; now it must be systematised. The founder cannot personally fulfil every obligation; the culture must carry it | +| Scale | Institutional duty -- ensuring the company's systems and culture perpetuate service beyond the founder | The ultimate Stoic test: can the organisation embody duty without the founder's daily presence? Marcus Aurelius knew he would die; he governed to create systems, not dependencies | + +The arc across stages traces a movement from personal duty to institutional duty. The founder's obligation evolves from doing the right thing personally to building an organisation that does the right thing systemically. + +Seneca captured the ultimate aspiration: "The person who has practiced philosophy as a cure for the self becomes great of soul, filled with confidence, invincible -- and greater as you draw near." The founder whose sense of duty has deepened through each stage does not become weaker under institutional pressure. The duty itself becomes a source of strength -- not because it is easy, but because it provides a clarity of purpose that no external incentive can replicate. + +The irony is worth noting: the founder who embraces duty freely, as a voluntary commitment rather than an imposed burden, discovers a form of joy that the purely profit-motivated founder never encounters. Seneca called it "real joy" -- "a serious thing" that "will never run dry once you've laid claim to its source." + +--- + +## Output Template + +```markdown +# Duty and Service Assessment + +## Stakeholder Duty Map +| Circle | Stakeholder | Specific Duty | Current Fulfilment (1-5) | Gap | +|--------|-------------|---------------|--------------------------|-----| +| Inner | Self-governance | [Duty] | [Score] | [Gap] | +| Core | Co-founders / Partners | [Duty] | [Score] | [Gap] | +| Team | Employees | [Duty] | [Score] | [Gap] | +| Market | Customers | [Duty] | [Score] | [Gap] | +| Capital | Investors | [Duty] | [Score] | [Gap] | +| Outer | Community / Industry | [Duty] | [Score] | [Gap] | + +## Sympatheia Analysis +- **Decision under review:** [Describe] +- **First-order effects:** [Direct impacts] +- **Second-order effects:** [Indirect impacts on adjacent stakeholders] +- **Third-order effects:** [Systemic or long-term impacts] +- **Obligations revealed:** [Duties illuminated by this analysis] + +## Service Quality Check +- **Type 1 acts (with explicit expectation):** [Count and examples] +- **Type 2 acts (silent scorekeeping):** [Count and examples] +- **Type 3 acts (the vine):** [Count and examples] +- **Shift plan:** [How to move toward Type 3] + +## Reframe Exercise +| Duty That Feels Burdensome | Reframe: The Privilege | Aligned? (Y/N) | +|---------------------------|----------------------|-----------------| +| [Duty] | [Reframe] | [Y/N] | +| [Duty] | [Reframe] | [Y/N] | +``` + +--- + +## Related Skills + +- **[Stoic Right Action](../../content/skills/stoic/stoic-right-action.md)** -- Duty without ethical guidance is mere compliance; right action gives duty its moral content. +- **[Stoic Problem Solving](../../content/skills/stoic/stoic-problem-solving.md)** -- When obstacles impede the fulfilment of duty, the Stoic method converts them into instruments of service. +- **[Stoic Pragmatism](../../content/skills/stoic/stoic-pragmatism.md)** -- The pragmatic execution layer that prevents duty from becoming abstract aspiration. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- The organisational expression of Stoic duty, translating personal obligation into collective mission. +- **[Humility and Power](../../content/skills/leadership/humility-and-power.md)** -- The paradox of leading through service rather than authority, directly aligned with Marcus Aurelius's practice of power. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- Building a team culture where duty is shared rather than concentrated in a single individual. diff --git a/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md b/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md deleted file mode 120000 index ec007e4..0000000 --- a/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-emotional-mastery.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md b/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md new file mode 100644 index 0000000..d5eb94c --- /dev/null +++ b/plugins/foreman/skills/stoic-emotional-mastery/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "stoic-emotional-mastery" +description: "Applies the Stoic approach to emotions -- not suppression but reframing -- to entrepreneurial leadership. Covers the distinction between first impressions and considered judgments, Seneca's anger management method, the practice of responding rather than reacting, and the Stoic treatment of fear, desire, pleasure, and grief. Use when anger is clouding judgment, fear is driving decisions, desire is distorting priorities, struggling to separate emotional reactions from rational assessment, or seeking a philosophical alternative to conventional emotional intelligence models." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - emotions + - anger-management + - fear + - desire + - self-control + - reframing + - seneca + - marcus-aurelius +related_skills: + - stoic-control-and-clarity + - stoic-self-awareness + - stoic-unbiased-thought + - emotional-intelligence + - emotional-courage + - thinking-fast-and-slow + - decision-making-under-pressure +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Emotional Mastery + +Emotions are like volcanoes -- the Stoic goal is not to extinguish them but to channel their energy. This distinction is routinely misunderstood. Popular culture has reduced "stoic" to a synonym for "emotionless," which would have baffled the actual Stoics, who wrote with more passion, honesty, and emotional granularity than most modern self-help authors manage. Seneca's letters vibrate with feeling. Marcus Aurelius's *Meditations* are the private journal of a man wrestling nightly with frustration, grief, and exhaustion. Epictetus practically shouts at his students. The Stoic project is not the elimination of emotion but the refusal to be governed by it -- a distinction that separates competent leaders from reactive ones. + +--- + +## The Framework + +### First Impressions vs. Considered Judgments + +The core Stoic insight about emotions is deceptively simple: there is a gap between the initial impression an event creates and the judgment you form about it. The impression is involuntary -- your pulse quickens when you receive a hostile email, your stomach drops when you learn a key employee is leaving. The Stoics called this the *propatheiai*, the "pre-emotion," and they considered it morally neutral. You cannot prevent it any more than you can prevent a loud noise from startling you. + +What you can control is the next step: whether you *assent* to that impression. "It isn't events themselves that disturb people," Epictetus writes, "but only their judgments about them." The hostile email is a fact. The judgment that it is an outrage, a betrayal, or a catastrophe is yours to make or withhold. + +### The Stoic Emotion Protocol + +The Stoics developed a practical sequence for handling emotional triggers: + +**Step 1 -- Pause.** Marcus Aurelius instructs himself to "say to the impression, hold up a bit and let me see who you are and where you are from." The pause is not hesitation. It is the deliberate insertion of reason between stimulus and response. + +**Step 2 -- Classify.** Is this impression about something within your control or outside it? If outside, the emotional charge is misplaced energy. If within, what specific action does it call for? + +**Step 3 -- Strip the judgment.** Remove the value label. Not "this customer abandoned us" but "this customer chose a different supplier." Not "the board is attacking me" but "the board is asking difficult questions." + +**Step 4 -- Respond from principle.** Act according to what your rational mind, untainted by the initial surge, determines is the right course. + +### Anger: The Stoic's Primary Adversary + +Seneca devoted an entire treatise to anger -- *De Ira* -- making it clear that of all emotions, this one most urgently demanded mastery. His reasoning was practical, not moralistic: "There is no more stupefying thing than anger, nothing more bent on its own strength. If successful, none more arrogant, if foiled, none more insane." + +Anger feels like power but functions as impairment. The angry negotiator overpays. The angry CEO fires the wrong person. The angry founder sends the email that costs them the partnership. Seneca's prescription is not to suppress the feeling but to delay the action. "The greatest remedy for anger is delay," he writes. Time is the solvent in which anger dissolves. + +For entrepreneurs, this translates to a concrete policy: never make a consequential decision, send a significant communication, or confront a team member while angry. Abraham Lincoln wrote furious letters to generals and subordinates and then folded them into his desk drawer, unsent. The Stoics would have approved. + +### Fear: The Self-Fulfilling Prophecy + +"Many are harmed by fear itself," Seneca warns, "and many may have come to their fate while dreading fate." Fear in an entrepreneurial context operates as a particularly insidious distortion: the founder afraid of losing a client overservices them into unprofitability. The CEO afraid of being perceived as weak avoids all vulnerability, destroying the trust that genuine leadership requires. The leader convinced of betrayal acts pre-emptively, becoming the very source of the disloyalty they feared. + +The Stoic treatment of fear centres on two practices. First, *premeditatio malorum* -- the deliberate, calm contemplation of worst-case scenarios. By imagining the feared outcome in advance, its emotional charge is partially discharged. Second, the dichotomy of control: if the feared outcome is outside your control, fear is futile; if it is within your control, action -- not fear -- is the appropriate response. + +### Desire and Pleasure: The Quiet Corruptors + +Anger and fear receive the most attention, but the Stoics reserved particular wariness for desire. "It is quite impossible to unite happiness with a yearning for what we don't have," Epictetus observes. The entrepreneur who cannot be content with the current state of the business -- who is perpetually fixated on the next milestone, the next round, the next acquisition -- is structurally incapable of the clarity that good decision-making requires. + +Pleasure presents the complementary hazard. Epictetus recommends a practice of connecting indulgence with its actual consequences: "Bring to mind both times, first when you have enjoyed the pleasure and later when you will regret it." This is not puritanism. It is the deliberate counterbalancing of a neural architecture that overweights immediate gratification. + +### The Indifferent Middle Ground + +Seneca, one of the wealthiest men in Rome, was not an ascetic. The Stoics distinguish between *preferred indifferents* (health, wealth, reputation -- things it is reasonable to pursue) and *dispreferred indifferents* (illness, poverty, obscurity -- things it is reasonable to avoid). The critical word is "indifferent." These things are neither good nor evil in themselves. Only virtue (wisdom, courage, justice, temperance) qualifies as genuinely good; only vice qualifies as genuinely bad. Everything else is raw material for the exercise of virtue. + +This framework liberates the entrepreneur from the emotional roller coaster that accompanies external outcomes. A lost deal is a dispreferred indifferent -- regrettable but not a moral catastrophe. A successful launch is a preferred indifferent -- welcome but not a reason to abandon the discipline that produced it. + +--- + +## Prompts + +**Prompt 1 -- Emotional Trigger Audit:** +> Identify the top 5 emotional triggers I currently face as founder/CEO of [company] -- situations that reliably provoke anger, fear, anxiety, or impulsive desire. For each trigger, apply the Stoic four-step protocol: (1) define the initial impression, (2) classify as within/outside my control, (3) strip the value judgment to reveal the neutral event, (4) recommend a principle-based response. + +**Prompt 2 -- Anger Delay Protocol:** +> I am currently angry about [situation]. Apply Seneca's anger management framework: help me identify the judgment driving this anger, test whether that judgment is accurate or distorted, enumerate the probable consequences of acting on the anger now versus waiting 24 hours, and draft a measured response I could send or take after the delay period. + +**Prompt 3 -- Fear Inversion:** +> I am afraid that [feared outcome] will happen to my business. Conduct a Stoic premeditatio malorum: describe the worst-case scenario in concrete, non-catastrophic language. Then classify each element of the feared outcome as controllable or uncontrollable. For the controllable elements, propose preventive actions. For the uncontrollable elements, describe what a rational acceptance of the risk would look like. + +**Prompt 4 -- Desire Calibration:** +> I am intensely pursuing [goal/acquisition/milestone]. Apply the Stoic framework of preferred indifferents to assess whether this desire is serving or enslaving me. What would change if I reclassified this from "essential" to "preferred but not necessary"? How would my decision-making improve if I could maintain effort without attachment to the specific outcome? + +--- + +## Use Cases + +**Early-traction founder receiving first harsh criticism** + +A consumer app founder at early traction receives a scathing product review from a prominent tech blogger. Her immediate reaction -- fury, followed by the urge to respond publicly -- is a textbook first impression demanding assent. Applying the Stoic protocol, she pauses (Step 1), classifies the reviewer's opinion as outside her control while her product roadmap remains within it (Step 2), strips the judgment by reframing "attack on my work" as "one user's public feedback" (Step 3), and responds from principle by extracting the three valid criticisms buried in the polemic and adding them to the backlog (Step 4). The blogger never gets a reply. The product gets better. + +**Growth-stage CEO managing fear of down-round** + +A SaaS CEO at growth stage faces deteriorating market conditions and the real possibility of a down-round. Fear begins to distort his decisions: he considers aggressive cost-cutting that would gut the engineering team, entertains acquisition offers he would never have considered six months ago, and loses sleep constructing catastrophic scenarios. The Stoic premeditatio malorum converts vague dread into a concrete contingency plan. The fear inversion reveals that most of his worst-case scenarios, examined calmly, are survivable. The dichotomy of control redirects energy toward the levers he can actually pull -- runway extension, selective hiring freezes, customer retention -- and releases the ones he cannot, such as broader market sentiment and competitor fundraising. + +**Scale-stage executive addicted to growth metrics** + +A scale-stage executive has tied her identity and sense of self-worth to monthly growth numbers. A single month of slower growth triggers a disproportionate emotional response -- anxiety, irritability, and the compulsive checking of dashboards. The Stoic framework of preferred indifferents provides the intervention. Growth is a preferred indifferent, not a moral good. Her response to a slow month -- the equanimity, strategic clarity, and composure with which she analyses the data and adjusts -- is where actual virtue resides. The reframing doesn't reduce her ambition. It protects her judgment from the distortion that unexamined desire produces. + +--- + +## Anti-Patterns + +**1. Equating Stoic composure with emotional suppression.** The single most common misapplication. Stoicism does not ask you to feel nothing; it asks you to not be controlled by what you feel. A founder who suppresses grief, frustration, or disappointment without processing it is not practising Stoicism -- they are building a pressure vessel. Marcus Aurelius wrote his private journal precisely because he needed a place to express and examine his emotions. + +**2. Using the framework to invalidate others' emotions.** Telling a distraught team member that "events are neutral, only your judgment makes them bad" is not leadership. It is philosophical malpractice. The Stoic framework is for self-governance, not for dismissing the legitimate emotional responses of others. Marcus Aurelius explicitly counsels compassion toward those who have not yet developed these capacities. + +**3. Treating anger as always irrational.** Some situations warrant moral outrage -- fraud, exploitation, injustice. The Stoic question is not "should I feel anger?" but "is my anger producing useful action or merely consuming me?" Directed anger that catalyses a principled response is different from reactive anger that destroys relationships and judgment. + +**4. Performing equanimity without the underlying work.** The appearance of calm is not the same as the achievement of it. Founders who project unflappability while internally spiralling are not Stoic; they are exhausted actors. The framework requires genuine cognitive reappraisal, not theatrical composure. + +**5. Ignoring the body.** The Stoics acknowledged that the body affects the mind. Fatigue, hunger, and illness lower the threshold at which impressions overwhelm judgment. Seneca would not have been impressed by the CEO who claims Stoic emotional mastery while sleeping four hours a night. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Managing fear of failure and rejection | Emotional reactions are most raw here; the gap between impression and judgment is smallest because everything feels existential | +| Validation | Separating personal identity from experimental outcomes | The founder must learn that a failed experiment is data, not a personal verdict -- the Stoic reframe of neutral events is essential | +| Early Traction | Handling criticism, competition, and first real setbacks | The emotional palette expands: anger at copycats, fear of losing early customers, desire for press coverage all need the four-step protocol | +| Growth | Preventing success from corrupting judgment | The pleasures of growth -- flattery, status, options -- are the quiet corruptors the Stoics warned about; indifference to preferred outcomes becomes critical | +| Scale | Institutional emotional regulation | The leader's emotional patterns infect the organisation; Stoic composure at scale is a cultural responsibility, not just a personal practice | + +At the idea stage, almost every piece of feedback carries outsized emotional weight because the founder and the company are nearly indistinguishable. A rejection of the idea feels like a rejection of the self. The Stoic separation of impression from judgment is the foundational skill that prevents early-stage emotional volatility from sabotaging the venture before it begins. + +At growth and scale, the emotional challenge shifts from personal volatility to systemic amplification. A CEO who reacts emotionally in a leadership meeting doesn't just make a bad decision -- they set the emotional tone for fifty, five hundred, or five thousand people. Stoic emotional mastery becomes an organisational competency, not merely a personal one. + +--- + +## Output Template + +```markdown +# Emotional Mastery Assessment -- [Situation] + +**Date:** [Date] +**Context:** [Brief description of the emotional challenge] + +## Trigger Analysis + +| Trigger | First Impression | Judgment Attached | Neutral Reframe | +|---------|-----------------|-------------------|-----------------| +| [Event] | [Involuntary reaction] | [Value label applied] | [Event stated without judgment] | + +## Control Classification +- **Within my control:** [List specific controllable elements] +- **Outside my control:** [List uncontrollable elements] +- **Energy reallocation:** [From uncontrollable → controllable] + +## Emotion-Specific Protocol + +### If Anger: +- **Delay period observed:** [Yes/No -- minimum 24 hours for consequential decisions] +- **Judgment accuracy test:** [Is the belief driving the anger actually true?] +- **Probable consequences of acting now:** [List] +- **Measured response (post-delay):** [Draft] + +### If Fear: +- **Worst case (concrete terms):** [Describe without catastrophising] +- **Survivability assessment:** [Is this actually unsurvivable?] +- **Preventive actions available:** [List controllable mitigants] + +### If Desire: +- **Preferred indifferent classification:** [Is this genuinely necessary or merely preferred?] +- **Decision quality with/without attachment:** [Compare] + +## Principle-Based Response +[The action or communication you will take, grounded in rational assessment rather than emotional surge] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The dichotomy of control is the structural foundation upon which emotional mastery is built; without it, reframing has no anchor. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- Recognising your emotional patterns is a prerequisite for interrupting them; the evening review practice surfaces recurring triggers. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's EQ model manages emotions within a social framework; Stoic emotional mastery operates at the perceptual level, reframing the impressions that generate emotions. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's System 1/System 2 distinction maps closely to the Stoic separation of first impressions from considered judgments. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- Stoic composure provides the philosophical foundation; emotional courage addresses the willingness to act on difficult truths. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Practical protocols for high-stakes decisions that benefit from the Stoic practice of pausing before assenting to impressions. diff --git a/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md b/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md deleted file mode 120000 index f8e9938..0000000 --- a/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-fortitude-and-resilience.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md b/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md new file mode 100644 index 0000000..42112f5 --- /dev/null +++ b/plugins/foreman/skills/stoic-fortitude-and-resilience/SKILL.md @@ -0,0 +1,203 @@ +--- +name: "stoic-fortitude-and-resilience" +description: "Provides the philosophical foundations of inner strength, endurance, and anti-fragility drawn from Stoic thought, teaching entrepreneurs why hardship strengthens character, how to prepare mentally for adversity through voluntary discomfort, and why patience and perseverance outperform luck as long-term competitive assets. Use when facing sustained business adversity, preparing mentally for a high-stakes launch or fundraise, building psychological toughness before a difficult transition, questioning whether a setback signals failure or formation, or seeking the philosophical basis for resilience practices covered in leader-resilience-and-wellbeing." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - fortitude + - resilience + - adversity + - perseverance + - anti-fragility + - voluntary-discomfort + - inner-strength + - endurance + - stoic + - mental-preparation +related_skills: + - leader-resilience-and-wellbeing + - stoic-acceptance-amor-fati + - stoic-mortality-and-perspective + - growth-mindset + - emotional-courage +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Fortitude and Resilience + +IRON. The word recurs across Stoic literature with a frequency that borders on obsession, and the reason is not metaphorical vanity. Iron is shaped in fire, hardened by hammering, made useful through processes that would destroy lesser materials. Comfort, as Seneca observed with characteristic bluntness, has never hardened anything. Cato the Younger walked Rome barefoot and bareheaded in rain and heat -- not because he lacked the means for sandals and a parasol, but because he was training his soul against the day when fortune would strip him of everything except his character. That day came, as it always does. Cato was ready. The question for the entrepreneur is not whether adversity will arrive. It is whether the founder will meet it as raw ore or as tempered steel. + +> "I judge you unfortunate because you have never lived through misfortune. You have passed through life without an opponent -- no one can ever know what you are capable of, not even you." -- Seneca, *On Providence* + +--- + +## The Framework + +Stoic fortitude is not the grim endurance of someone who merely survives. It is a trained capacity to metabolise difficulty into strength -- what Nassim Taleb would later call anti-fragility, but which the Stoics articulated two millennia earlier without the neologism. The framework rests on four pillars. + +### Pillar 1: The Inner Citadel + +Marcus Aurelius returned again and again to the concept of an impenetrable inner fortress -- a domain of reasoned choice that no external force can breach. "The mind freed from passions is an impenetrable fortress -- a person has no more secure place of refuge for all time." The fortress falls only through internal betrayal: when fear, greed, or despair open the gates from within. + +For entrepreneurs, the Inner Citadel is the capacity to separate external events (a lost client, a failed fundraise, a competitor's surprise move) from internal judgement. The event is neutral. The interpretation -- catastrophe or curriculum -- is a choice. + +### Pillar 2: Voluntary Discomfort as Training + +Seneca's prescription is as practical as it is counterintuitive: "Take part of a week in which you have only the most meager and cheap food, dress scantly in shabby clothes, and ask yourself if this is really the worst that you feared." Soldiers drill in peacetime. Athletes train in conditions worse than competition. The Stoics applied the same logic to psychological endurance. + +Voluntary discomfort operates through three mechanisms: + +| Mechanism | Stoic Source | Entrepreneurial Application | +|-----------|-------------|---------------------------| +| **Desensitisation** | Seneca's cold-bath exercises | Practising with less capital, fewer resources, smaller teams reduces the terror of scarcity | +| **Calibration** | Epictetus on discovering true needs | Distinguishing genuine needs from habituated wants clarifies which expenses and dependencies are structural | +| **Confidence** | Seneca on the poverty of exile | Having survived voluntary deprivation, the entrepreneur knows that involuntary deprivation is survivable | + +### Pillar 3: The Sparring Partner Reframe + +> "Difficulties show a person's character. So when a challenge confronts you, remember that God is matching you with a younger sparring partner, as would a physical trainer." -- Epictetus, *Discourses* + +Every setback is a training bout. The rejected pitch, the churning customers, the co-founder conflict -- these are not evidence that the universe is hostile. They are the resistance that builds capacity. Marcus Aurelius framed life itself as wrestling rather than dancing: "an artful life requires being prepared to meet and withstand sudden and unexpected attacks." Dancers perform choreography. Wrestlers respond to what the opponent does. Entrepreneurship is wrestling. + +### Pillar 4: Patience as Strategic Asset + +> "Anyone can get lucky. Not everyone can persevere." -- Seneca, *On Providence* + +The Stoics drew a sharp distinction between fortune and fortitude. Fortune is a loan; fortitude is equity. The lucky entrepreneur who has never been tested does not know whether the business model or the market cycle deserves the credit. The entrepreneur who has persevered through adversity holds the rarer and more durable asset: proof that they can endure. + +Perseverance, however, is not stubbornness. Marcus explicitly warned against mistaking an iron will for an adaptable one: "To change your mind and to follow someone's correction are consistent with a free will." The goal is not to persist blindly but to persist intelligently -- adjusting tactics while holding strategic conviction. + +### The Stockdale Paradox + +Captain James Stockdale, shot down over Vietnam and imprisoned for seven and a half years, brought Epictetus into the most brutal laboratory imaginable. He later told Jim Collins that the prisoners who did not survive were, counterintuitively, the optimists -- "the ones who said, 'We're going to be out by Christmas.' And Christmas would come, and Christmas would go. And they died of a broken heart." Stockdale himself held two truths simultaneously: absolute faith that he would prevail in the end AND absolute confrontation with the brutal facts of his current situation. + +This paradox -- hope anchored in agency, not in timeline -- is the Stoic position distilled for entrepreneurs. The founder who says "We'll close the round by Q3" is making a prediction about things outside their control. The founder who says "We will do everything within our power, and we will adapt to whatever comes" is practising Stoic fortitude. The first disposition is brittle. The second is unbreakable. + +### Fear as the Real Enemy + +> "There is no reason to live and no limit to our miseries if we let our fears predominate." -- Seneca, *Moral Letters* + +FDR's "nothing to fear but fear itself" drew from a wellspring the Stoics had tapped centuries earlier. Fear does not protect; it pre-empts. The entrepreneur who avoids a difficult conversation out of fear allows the underlying problem to metastasize. The founder who refuses to look at deteriorating metrics out of fear forfeits the window in which intervention is possible. Stoic fortitude is, at its core, the disciplined refusal to let fear -- rather than reason -- dictate action. + +--- + +## Prompts + +**Prompt 1 -- Inner Citadel Audit:** +> I am facing a significant external challenge: [describe situation -- e.g., failed fundraise, lost key customer, co-founder departure]. Using the Stoic concept of the Inner Citadel, help me separate what is genuinely outside my control from what remains within my reasoned choice. For each element outside my control, reframe the catastrophic interpretation into a neutral or instructive one. For each element within my control, identify the most effective action I can take this week. + +**Prompt 2 -- Voluntary Discomfort Protocol:** +> Design a 30-day voluntary discomfort programme for me as an entrepreneur at [stage]. The goal is to reduce my psychological dependence on [comfort/resource -- e.g., a large team, premium office, high salary, constant validation]. For each week, prescribe a specific deprivation exercise, explain the Stoic rationale behind it, and describe the entrepreneurial capability it builds. Make the programme progressively harder. + +**Prompt 3 -- Adversity Reframe:** +> I have experienced the following setback: [describe]. My current emotional response is [describe -- e.g., demoralised, angry, fearful]. Apply the Stoic sparring-partner reframe: What capability is this adversity training me to develop? What would Seneca, Epictetus, or Marcus Aurelius say about this specific situation? What is the most strategically intelligent response, as opposed to the most emotionally satisfying one? + +**Prompt 4 -- Perseverance vs. Stubbornness Diagnostic:** +> I have been pursuing [goal/strategy] for [time period] despite ongoing resistance and setbacks. Help me distinguish between Stoic perseverance (intelligent persistence aligned with what I control) and mere stubbornness (refusing to adapt despite clear evidence). What signals would indicate that I should hold the course? What signals would indicate that I should change direction while maintaining the larger mission? + +--- + +## Use Cases + +**Validation-Stage Climate-Tech Founder After Third Rejected Pilot** + +A founder building carbon-capture technology for industrial facilities has been rejected by three potential pilot customers in succession. Each rejection cited a different reason -- budget timing, regulatory uncertainty, internal politics -- but the cumulative effect is demoralising. Applying the Stoic sparring-partner reframe, the founder catalogues what each rejection taught: the first revealed a pricing objection the pitch did not address, the second exposed a procurement cycle the go-to-market plan ignored, the third identified a champion-building step the sales process lacked. None of these insights were available without the rejections. Seneca's observation applies directly: the founder now knows capabilities that remained invisible during the comfortable theorising of the idea stage. + +**Growth-Stage SaaS Founder Preparing for Economic Downturn** + +A SaaS company with 200 employees and comfortable margins sees early indicators of a market contraction. Rather than waiting for the downturn to force austerity, the CEO applies Seneca's voluntary-discomfort principle at the organisational level: a 90-day "wartime readiness" exercise in which each department identifies how it would operate at 70% of current budget. The exercise surfaces redundant tooling, over-specified vendor contracts, and processes that consume resources without proportional output. When the downturn arrives six months later, the company has already internalised the leaner operating model -- not as panic but as preparedness. The team's confidence, paradoxically, is higher during the downturn than before the exercise. + +**Early-Traction Founder Managing Emotional Volatility** + +A first-time founder at early traction finds herself oscillating between euphoria after a good sales week and despair after a bad one. The emotional volatility is affecting her decision-making and her team's confidence. Using the Inner Citadel framework, she maps which elements of weekly revenue are inside her control (activity volume, pitch quality, pipeline management) and which are outside it (individual prospect timing, macroeconomic sentiment, competitor moves). She then constructs a personal dashboard that tracks only the controllable inputs. Within a month, the emotional swings diminish -- not because the outcomes changed but because her attention shifted to what Epictetus called "the only things that are truly ours." + +--- + +## Anti-Patterns + +1. **Glorifying suffering for its own sake.** The Stoics practised voluntary discomfort as training, not as masochism. The founder who sleeps on the office floor, works hundred-hour weeks, and neglects health is not practising Stoic fortitude -- they are practising self-destruction with a philosophical veneer. Seneca himself counselled rest and relaxation as essential to sustained performance. The goal is resilience, not ruin. + +2. **Confusing emotional suppression with inner strength.** The Inner Citadel is not a wall behind which one hides from emotion. Marcus Aurelius grieved. Seneca feared. Epictetus acknowledged pain. Stoic fortitude means processing adversity through reason, not refusing to feel it. The founder who insists they are "fine" after a devastating setback is not demonstrating fortitude. They are delaying a collapse. + +3. **Using Stoic endurance to avoid necessary pivots.** Perseverance is a virtue when applied to a sound strategy against temporary resistance. It becomes a vice when applied to a failing strategy against permanent market realities. "Flexibility is its own kind of strength," Marcus wrote. The Stoic entrepreneur endures hardship on the path -- but changes the path when reason demands it. + +4. **Weaponising Stoicism against others.** Telling a struggling employee or co-founder to "be more Stoic" is not philosophy; it is dismissal dressed in a toga. Stoic fortitude is a personal discipline, not a performance standard to impose on others. The leader's job is to build resilience in the organisation through structure and support, not through philosophical lecturing. + +5. **Treating the absence of adversity as failure.** Some founders, having absorbed the "what doesn't kill you makes you stronger" narrative, unconsciously seek or manufacture crises. The Stoics valued tranquillity. Cato trained in hardship so that he could function during hardship -- not so that he could pursue it as a lifestyle. + +6. **Mistaking Stoic philosophy for a personality type.** Fortitude is a practice, not a disposition. Some people appear naturally tough; some appear naturally sensitive. Stoic training is available to both. The naturally tough founder who has never examined their resilience philosophically is no more Stoic than the sensitive founder who has done the inner work. Resilience is built, not inherited. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Building tolerance for uncertainty | The idea stage is almost entirely composed of unknowns. Stoic fortitude here means training oneself to operate without the validation, structure, or income that previous employment provided. Voluntary discomfort: practise living on minimal runway before you have to. | +| Validation | Metabolising rejection | Validation requires subjecting the idea to market reality, which means hearing "no" repeatedly. The sparring-partner reframe converts each rejection from a verdict into data. The founder who emerges from validation with fortitude intact has the most important signal of all: evidence of their own endurance. | +| Early Traction | Managing emotional volatility | Revenue creates hope, and hope creates vulnerability to disappointment. The Inner Citadel discipline -- separating controllable inputs from uncontrollable outcomes -- is most critical here. Fortitude at this stage is the ability to maintain strategic clarity amid operational noise. | +| Growth | Sustaining conviction through scaling pain | Growth brings new categories of adversity: team conflicts, operational breakdowns, competitive pressure, board dynamics. The Stoic framework shifts from personal endurance to institutional resilience. The question becomes: how does the founder build an organisation that metabolises adversity, not just a personality that tolerates it? | +| Scale | Preparing for reversal at the peak | Seneca's warning about fortune applies most urgently at scale: "No one is crushed by Fortune, unless they are first deceived by her." The scaled company faces its greatest risk of complacency. Stoic fortitude at this stage is the discipline to prepare for downturn during prosperity -- the organisational equivalent of Cato walking barefoot through Rome. | + +--- + +## Output Template + +```markdown +# Fortitude and Resilience Assessment + +**Founder/Leader:** [Name] +**Company Stage:** [Stage] +**Date:** [Date] +**Current Adversity:** [Brief description of the challenge] + +## Fear Inventory +| Fear | Rational Basis? | Stoic Response | Action It Blocks | +|------|----------------|---------------|-----------------| +| [Fear 1] | Yes / Partially / No | [Reasoned assessment] | [What you would do without this fear] | +| [Fear 2] | Yes / Partially / No | [Reasoned assessment] | [What you would do without this fear] | + +## Inner Citadel Inventory + +| Element | Inside My Control? | Current Response | Stoic Response | +|---------|-------------------|-----------------|---------------| +| [Element 1] | Yes / No | [What I am doing] | [What reason dictates] | +| [Element 2] | Yes / No | [What I am doing] | [What reason dictates] | +| [Element 3] | Yes / No | [What I am doing] | [What reason dictates] | + +## Sparring Partner Reframe +- **What is this adversity training me to do?** [Answer] +- **What capability will I have after this that I lacked before?** [Answer] +- **What would I advise a founder facing this same challenge?** [Answer] + +## Voluntary Discomfort Commitments (Next 30 Days) +1. [Specific practice] -- Rationale: [Why this builds resilience] +2. [Specific practice] -- Rationale: [Why this builds resilience] +3. [Specific practice] -- Rationale: [Why this builds resilience] + +## Perseverance Check +- **Is my persistence aligned with what I control?** [Yes/No + evidence] +- **Am I adapting tactics while holding strategic conviction?** [Yes/No + evidence] +- **What signal would tell me to change course?** [Specific, observable signal] +``` + +--- + +## Related Skills + +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Covers the daily, practical dimensions of resilience: sleep, stress management, mindfulness, recovery practices. This skill provides the philosophical foundation; that skill provides the operational toolkit. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- Fortitude prepares you to endure what happens; amor fati teaches you to love it. The two disciplines form a progression: first survive, then transcend. +- **[Growth Mindset](../../content/skills/frameworks/growth-mindset.md)** -- Dweck's research provides the psychological evidence for what the Stoics intuited: that viewing challenges as development opportunities produces measurably better outcomes. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- The leadership practice of acting despite fear and vulnerability, which operationalises the Inner Citadel concept in team and organisational contexts. +- **[Stoic Mortality and Perspective](../../content/skills/stoic/stoic-mortality-and-perspective.md)** -- The awareness of mortality gives fortitude its urgency: endurance matters because time is finite. +- **[Building Thinking Strength](../../content/skills/thinking/building-thinking-strength.md)** -- The Clear Thinking framework's self-control and self-confidence pillars are the modern behavioural equivalents of Stoic fortitude applied to entrepreneurial decision-making. diff --git a/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md b/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md deleted file mode 120000 index 173697d..0000000 --- a/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-mortality-and-perspective.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md b/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md new file mode 100644 index 0000000..80f2594 --- /dev/null +++ b/plugins/foreman/skills/stoic-mortality-and-perspective/SKILL.md @@ -0,0 +1,215 @@ +--- +name: "stoic-mortality-and-perspective" +description: "Applies the Stoic practice of memento mori -- meditation on mortality -- as a tool for entrepreneurial clarity, urgency, and perspective. Teaches how the awareness of death sharpens focus, eliminates trivial distractions, accelerates decision-making, informs legacy thinking, and provides the 'view from above' that rescales problems to their actual size. Use when an entrepreneur is paralysed by indecision, when petty concerns are consuming disproportionate energy, when time management lacks urgency, when succession or legacy questions arise, when perspective has been lost to operational detail, or when the founder needs the ultimate clarifying question: what would matter if this were the last year?" +version: "1.0.0" +category: "stoic" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - memento-mori + - mortality + - perspective + - time-management + - legacy + - urgency + - focus + - priorities + - stoic + - view-from-above +related_skills: + - stoic-acceptance-amor-fati + - stoic-fortitude-and-resilience + - stoic-virtue-and-kindness + - focus-and-priority-management + - eisenhower-matrix +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Mortality and Perspective + +LAST DAY. Marcus Aurelius, the most powerful man in the Western world, began each morning with a thought that would strike most modern executives as morbid: "I may die today." He was not morbid. He was strategic. The meditation did not make him fearful; it made him a better emperor. It eliminated the trivial, accelerated the consequential, and imposed a ruthless filter on how to spend the only resource that cannot be replenished: time. Seneca compressed the same insight into a formula that has lost none of its edge across two millennia: "Let us prepare our minds as if we'd come to the very end of life. Let us postpone nothing. Let us balance life's books each day. The one who puts the finishing touches on their life each day is never short of time." The entrepreneur who treats every day as potentially the last does not become reckless. They become precise. Mortality is not the enemy of ambition. It is the lens through which ambition is focused. + +--- + +## The Framework + +Stoic meditation on mortality -- *memento mori* -- is not a morbid exercise but a cognitive technology. It operates through five distinct mechanisms, each producing practical benefits for the entrepreneur. + +### Mechanism 1: The Priority Filter + +> "Don't behave as if you are destined to live forever. What's fated hangs over you. As long as you live and while you can, become good now." -- Marcus Aurelius, *Meditations* + +The Sword of Damocles -- the blade suspended by a single hair above the throne -- is the ancient world's most vivid metaphor for mortality's relationship to power. Every founder sits beneath a similar blade: the venture could end, health could fail, the market could vanish. Acknowledging the sword does not induce paralysis; it induces clarity. Activities that would not survive the question "Would I do this if I had six months left?" reveal themselves as waste. Meetings that exist out of habit, features that serve vanity, conflicts that feed ego -- all of them wither under mortality's gaze. + +Seneca delivered the operational version of this insight with characteristic precision: "No person hands out their money to passersby, but to how many do each of us hand out our lives! We're tight-fisted with property and money, yet think too little of wasting time, the one thing about which we should all be the toughest misers." + +### Mechanism 2: The View from Above + +> "Think of the whole universe of matter and how small your share. Think about the expanse of time and how brief -- almost momentary -- the part marked for you." -- Marcus Aurelius, *Meditations* + +The Stoics practised a mental exercise they called the "view from above" -- imagining oneself looking down at the Earth, watching the comings and goings of human activity from a cosmic distance. From this altitude, the competitive dynamics that consume a founder's waking hours shrink to their actual proportion. This is not nihilism. It is perspective. The problem that feels existential at 2 a.m. is real, but it is not the entirety of reality. The competitor that seems invincible is also, from sufficient distance, a brief arrangement of atoms and ambition, subject to the same forces of entropy that govern everything. + +Marcus practised this relentlessly: "Think by way of example on the times of Vespasian, and you'll see all these things: marrying, raising children, falling ill, dying, wars, holiday feasts, commerce, farming, flattering, pretending. Now that life of theirs is dead and gone." The people of Vespasian's time believed their concerns were of supreme importance. They were not. Neither are ours. And acknowledging this is not depressing -- it is liberating. + +### Mechanism 3: The Urgency of Excellence + +> "This is the mark of perfection of character -- to spend each day as if it were your last, without frenzy, laziness, or any pretending." -- Marcus Aurelius, *Meditations* + +The critical qualifier in Marcus's formulation is "without frenzy." Living as if today were the last day does not mean panic, hedonism, or abandoning long-term projects. It means bringing full commitment and zero pretence to whatever the day requires. The urgency is not about cramming more in; it is about eliminating the gap between what one values and what one does. The founder who is aware that time is finite does not answer emails faster -- they stop answering emails that should never have been sent. They do not work longer hours -- they work on things that matter. + +The contrast with conventional productivity thinking is illuminating. Productivity frameworks ask: "How do I get more done?" Memento mori asks: "Is this worth doing at all, given that my hours are numbered?" + +### Mechanism 4: The Equaliser + +> "Both Alexander the Great and his mule-keeper were both brought to the same place by death -- they were either received into the all-generative reason, or scattered among the atoms." -- Marcus Aurelius, *Meditations* + +Death is the great leveller, and the Stoics wielded this fact against both arrogance and despair. The entrepreneur inflated by success should remember that Alexander's conquests ended in dust. The entrepreneur crushed by failure should remember the same: the magnitude of any setback, measured against the span of human existence, is vanishingly small. Shakespeare's Hamlet traces the logic to its conclusion: "Imperious Caesar, dead and turn'd to clay, / Might stop a hole to keep the wind away." + +This is not an argument for nihilism. It is an argument against the disproportionate weight we attach to ephemeral outcomes. The fundraise that didn't close, the competitor who copied the product, the board member who was difficult -- all of these are real, but none of them will matter in a century. The character you develop while navigating them might. + +### Mechanism 5: Legacy as Present Action + +> "Stop wandering about! Get busy with life's purpose, toss aside empty hopes, get active in your own rescue -- if you care for yourself at all -- and do it while you can." -- Marcus Aurelius, *Meditations* + +The Stoics were deeply sceptical of legacy as a motivator. Marcus noted that even the most famous names are eventually forgotten: "Everything lasts for a day, the one who remembers and the remembered." The paradox is instructive: the desire for a lasting legacy often produces behaviour (self-promotion, empire-building, vanity projects) that is precisely the opposite of what creates genuine, lasting impact. The Stoic alternative: focus on the quality of present action. Build something excellent because excellence is worth pursuing, not because posterity is watching. Posterity is not watching. Posterity is busy with its own problems. + +Seneca drove the point with a challenge to every entrepreneur who defers meaning to some future horizon: "Aren't you ashamed to reserve for yourself only the remnants of your life and to dedicate to wisdom only that time can't be directed to business?" + +### Mechanism 6: The Conquest of Death-Fear Through Philosophy + +> "Do you then ponder how the supreme of human evils, the surest mark of the base and cowardly, is not death, but the fear of death? I urge you to discipline yourself against such fear." -- Epictetus, *Discourses* + +Cato read Plato's *Phaedo* before taking his own life rather than submitting to Caesar's destruction of the Republic. Seneca, when the executioners came, chided his weeping friends: "Where are your maxims of philosophy, or the preparations of so many years' study against evils to come?" These are extreme cases, but the principle applies to every entrepreneur who lets fear of failure -- a small death of ego -- prevent them from acting. + +The Stoic insight is structurally elegant: if death is the worst possible outcome, and death is certain, then fearing intermediate setbacks is irrational. The fundraise that fails, the product that flops, the company that folds -- none of these are death. And if they were? Death, Epictetus observed, "contains within it the end of fear." The entrepreneur who has genuinely reckoned with mortality finds that lesser fears lose their paralysing power. Not because they become reckless, but because they gain proportion. + +### The Brevity Paradox + +> "It's not at all that we have too short a time to live, but that we squander a great deal of it. Life is long enough, and it's given in sufficient measure to do many great things if we spend it well." -- Seneca, *On the Brevity of Life* + +Seneca's most subversive claim is that life is not short -- we make it short through waste. The average entrepreneur attends meetings that produce no decisions, reads email that demands no response, worries about events they cannot influence, and then complains about insufficient time. The mortality-aware entrepreneur audits time expenditure with the rigour that a CFO applies to cash: every hour is an allocation decision, and every allocation has an opportunity cost measured against a finite budget. + +--- + +## Prompts + +**Prompt 1 -- Memento Mori Priority Audit:** +> Assume I have exactly one year left to lead my company. My company is [describe: stage, product, team]. Given this constraint, help me identify: (1) Which of my current activities would I immediately stop? (2) Which decisions that I have been deferring would I make today? (3) Which relationships would I invest in more deeply? (4) Which projects would I accelerate? Present the analysis as a "mortality-filtered" priority list, ranked by what matters most under the constraint of radical finitude. + +**Prompt 2 -- View from Above:** +> I am consumed by the following problem: [describe in detail -- e.g., a competitive threat, a team conflict, a strategic uncertainty]. Apply the Stoic "view from above" exercise: zoom out progressively -- from the company, to the industry, to the economy, to the century, to the span of human history. At each level of zoom, reassess the actual magnitude of this problem. Then zoom back in and identify: What is the appropriately sized response to this appropriately sized problem? + +**Prompt 3 -- Time-as-Currency Analysis:** +> Audit how I spent the last week as if time were a non-renewable currency (which it is). My calendar and activities for the past week: [describe or paste schedule]. For each major time block, apply Seneca's test: "Did this activity make a full return on the loss of this irreplaceable time?" Categorise each block as: (a) would survive the mortality filter, (b) questionable under the mortality filter, (c) would not survive. For category (c), identify what should replace it. + +**Prompt 4 -- Legacy vs. Present Action:** +> I find myself motivated by legacy thinking -- building something that outlasts me. Apply the Stoic critique: Marcus Aurelius argued that even the most famous names are eventually forgotten and that legacy-seeking often produces the opposite of genuine impact. Help me distinguish: (1) Which of my legacy ambitions are actually about present-day ego? (2) Which are genuinely about creating value that persists? (3) What would I do differently if I released the need to be remembered and focused entirely on the quality of present action? + +--- + +## Use Cases + +**Scale-Stage CEO Paralysed by a Board Decision** + +A CEO at a scaled fintech company has spent four months deliberating over whether to pursue a major international expansion. The decision involves substantial capital risk, board politics, and personal reputation. Analysis paralysis has set in. A mentor introduces the memento mori filter: "If you had one year left as CEO, would you still be deliberating in month four?" The question cuts through the accumulated complexity. The CEO realises that the deliberation has become a substitute for the decision, and that the fear is not about the expansion's economics (which are favourable) but about the personal consequences of failure. Marcus Aurelius's counsel applies: "As long as you live and while you can, become good now." The CEO makes the decision within a week -- not recklessly but with the clarity that mortality-awareness provides. + +**Idea-Stage Founder Struggling with Identity Loss** + +A former investment banker, eighteen months into building a consumer app, finds himself checking LinkedIn obsessively -- monitoring former colleagues' promotions, measuring his own progress against their titles. The behaviour consumes hours per week and produces only misery. The view-from-above exercise delivers the corrective. Zoomed to the level of a human lifespan: the promotions of former colleagues and the founder's current struggle are equally transient arrangements. Zoomed to the level of a century: neither will register. The exercise does not make the founder's ambition irrelevant -- it makes the comparison irrelevant. Seneca's challenge lands: "We're tight-fisted with property and money, yet think too little of wasting time." The founder deletes LinkedIn from his phone. The hours recovered go to customer interviews. + +**Growth-Stage Founder Avoiding Succession Planning** + +A founder who has led her company from inception through Series C systematically avoids conversations about succession, key-person risk, or the company's operation without her. She recognises intellectually that this avoidance is a liability but cannot bring herself to engage with it emotionally. The Stoic framework provides the entry point: memento mori is not about planning for death; it is about planning for life in full awareness of its finitude. The founder begins by applying Marcus Aurelius's exercise: "Think of the life you have lived until now as over and, as a dead man, see what's left as a bonus." From this perspective, succession planning is not a concession to mortality; it is an act of stewardship -- ensuring that the company's value, built through years of effort, persists beyond any single individual. She initiates the succession conversation the following week. + +--- + +## Anti-Patterns + +1. **Using mortality awareness as an excuse for short-termism.** "Life is short" is not a justification for abandoning long-term strategy, cutting corners on quality, or avoiding investments that pay off over years. The Stoics planned and built for decades -- Marcus governed for nearly twenty years; Seneca wrote works intended to endure. Mortality awareness improves the *quality* of long-term action; it does not argue against it. + +2. **Weaponising memento mori for hustle culture.** "You could die tomorrow, so work harder" is a corruption of the Stoic teaching. Marcus explicitly warned against frenzy. Seneca counselled rest. The Stoic insight is not that you should fill every moment with productivity but that you should fill every moment with intention -- and sometimes the most intentional choice is rest, reflection, or the simple enjoyment of being alive. + +3. **Nihilistic misreading of the view from above.** "Nothing matters because we all die" is precisely the opposite of what the Stoics taught. Marcus used the view from above to eliminate *trivial* concerns, not to eliminate all concern. The framework sharpens focus on what matters; it does not argue that nothing does. + +4. **Death-anxiety masquerading as philosophy.** If meditation on mortality produces only anxiety, dread, or despair, the practice is not functioning as intended. Epictetus addressed this directly: "Do you then ponder how the supreme of human evils, the surest mark of the base and cowardly, is not death, but the fear of death?" The goal is not to fear death more keenly but to let the awareness of death reduce the fear of everything else. + +5. **Avoiding grief by philosophising over it.** The Stoics did not recommend bypassing grief through intellectual reframing. Seneca wrote: "It's better to conquer grief than to deceive it." When a real loss occurs -- a death, a relationship, a dream -- the appropriate response is to feel it fully, not to reach for Marcus Aurelius as an anaesthetic. Philosophy supports the processing of grief; it does not substitute for it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Urgency as antidote to procrastination | The idea stage is uniquely vulnerable to deferral: "I'll start when the timing is better." Memento mori eliminates this excuse. The timing will never be perfect, and the time available is unknown. Begin now. Seneca's challenge applies: the one who balances life's books each day is never short of time. | +| Validation | Perspective on rejection's insignificance | Rejection feels catastrophic at the validation stage because the founder's identity is tightly coupled to the idea's reception. The view from above rescales rejection to its actual size: a data point in a process, not a verdict on a life. This perspective enables faster iteration and less emotional recovery time between setbacks. | +| Early Traction | Time-as-currency discipline | Early traction is when time management habits calcify. The founder who treats time as a non-renewable resource at this stage -- ruthlessly eliminating waste, refusing meetings that do not earn their time-cost, protecting blocks for strategic thinking -- builds operational discipline that compounds for years. | +| Growth | The equaliser against ego inflation | Growth brings recognition, press coverage, speaking invitations, and the intoxicating sense that one is building something important. Memento mori is the counterweight: Alexander the Great also thought he was building something important. The discipline is not to diminish ambition but to prevent it from distorting judgement. | +| Scale | Legacy, succession, and stewardship | At scale, the founder must confront what happens to the company after their involvement ends -- whether through choice, circumstance, or mortality. The Stoic framework reframes succession not as loss of control but as the highest form of leadership: building something that transcends any individual, including the founder. | + +--- + +## Output Template + +```markdown +# Memento Mori Strategic Review + +**Founder:** [Name] +**Company:** [Name] +**Date:** [Date] + +## The Last-Year Filter +If I had one year remaining as leader of this company: + +### I would stop: +1. [Activity/commitment and why it fails the mortality test] +2. [Activity/commitment] +3. [Activity/commitment] + +### I would start or accelerate: +1. [Decision/project and why it passes the mortality test] +2. [Decision/project] +3. [Decision/project] + +### I would decide immediately: +1. [Deferred decision and the clarity mortality provides] +2. [Deferred decision] + +## View from Above +**Problem consuming my attention:** [Description] +**Magnitude at company level:** [Assessment] +**Magnitude at industry level:** [Assessment] +**Magnitude at decade level:** [Assessment] +**Magnitude at century level:** [Assessment] +**Appropriately sized response:** [Action calibrated to actual magnitude] + +## Time Audit (Past Week) + +| Time Block | Activity | Mortality Filter | Replace With | +|-----------|----------|-----------------|-------------| +| [Hours] | [Activity] | Survives / Questionable / Fails | [Alternative if fails] | + +## Succession and Stewardship +- **Key-person risks:** [Roles/knowledge that depend entirely on one individual] +- **Stewardship actions this quarter:** [Specific steps toward organisational resilience] +- **What I want to be true about this company regardless of my involvement:** [Vision statement] +``` + +--- + +## Related Skills + +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- Provides the operational frameworks that give structure to the urgency that memento mori produces; mortality awareness without prioritisation tools creates anxiety, tools without the underlying urgency create busywork. +- **[Eisenhower Matrix](../../content/skills/frameworks/eisenhower-matrix.md)** -- The urgent-important distinction maps directly to the Stoic mortality filter; activities that are urgent but unimportant fail the "last year" test most reliably. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- Mortality awareness and fate acceptance are two faces of the same coin; memento mori says time is finite, amor fati says love the time you have, including its end. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- The awareness of mortality strengthens fortitude by providing ultimate perspective: everything short of death is manageable. +- **[Stoic Virtue and Kindness](../../content/skills/stoic/stoic-virtue-and-kindness.md)** -- Marcus Aurelius connected mortality directly to virtue: the awareness of death's approach is the most powerful motivator for living virtuously now. +- **[Wanting What Matters](../../content/skills/thinking/wanting-what-matters.md)** -- The memento mori filter produces the same clarity as Pillemer's research on end-of-life regrets: both reveal which pursuits will matter and which are distractions. diff --git a/plugins/foreman/skills/stoic-pragmatism/SKILL.md b/plugins/foreman/skills/stoic-pragmatism/SKILL.md deleted file mode 120000 index 84afd3d..0000000 --- a/plugins/foreman/skills/stoic-pragmatism/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-pragmatism.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-pragmatism/SKILL.md b/plugins/foreman/skills/stoic-pragmatism/SKILL.md new file mode 100644 index 0000000..ccbfb9d --- /dev/null +++ b/plugins/foreman/skills/stoic-pragmatism/SKILL.md @@ -0,0 +1,205 @@ +--- +name: "stoic-pragmatism" +description: "Distills the Stoic insistence on philosophy as action rather than theory, covering simplicity, efficiency, realism, the primacy of practice over abstraction, and the elimination of unnecessary complexity. Use when founders are overthinking strategy at the expense of execution, when organisations are drowning in process without progress, when the gap between stated philosophy and daily behaviour needs closing, or when a team needs to cut through complexity and focus on what actually works." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - pragmatism + - execution + - simplicity + - action + - efficiency + - realism + - practice +related_skills: + - stoic-right-action + - stoic-problem-solving + - stoic-duty-and-service + - focus-and-priority-management + - decision-making-under-pressure + - learning-agility +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Pragmatism + +Marcus Aurelius was both philosopher and emperor -- the tension between those roles produced the most pragmatic philosophy ever written. Plato had imagined a utopia governed by a philosopher-king. Marcus lived the reality and discovered what Plato could not have anticipated: that the demands of governing an empire -- plagues, wars, famines, betrayals, Senate politics, logistical nightmares on three continents -- leave no room for philosophy that does not work when applied. His *Meditations* were not written for publication. They were private notes, scrawled in campaign tents and palace chambers, by a man trying to close the gap between what he believed and what he did. That gap -- between theory and practice, between knowing and doing, between the philosophy lecture and Monday morning -- is the central problem of every founder who has ever attended a conference, read a business book, and returned to the office to find that nothing has changed. + +--- + +## The Framework + +Stoic pragmatism is built on a single, uncomfortable premise: philosophy that does not change behaviour is entertainment. Seneca put it without decoration: philosophy "is not concerned with words, but with facts. It's not employed for some pleasure before the day is spent, or to relieve the uneasiness of our leisure. It shapes and builds up the soul, it gives order to life, guides action." + +### Principle 1: Habit Over Theory + +> "When the problem arose whether habit or theory was better for getting virtue, Musonius thought habit to be more effective." -- Musonius Rufus, *Lectures*, 5 + +Knowledge without practice is worse than useless -- it creates the illusion of competence. The founder who has read every book on management but cannot conduct a productive one-on-one is not educated; they are dangerously misinformed about their own capabilities. + +Musonius Rufus resolved the ancient debate between theory and practice with characteristic bluntness: habit wins. Not because theory is unimportant, but because understanding without embodiment is incomplete. A musician who understands music theory but never practises cannot play. A founder who understands lean methodology but never ships an MVP is not lean. + +The Stoic prescription: for every hour of learning, invest two hours of doing. For every framework absorbed, run one experiment. For every strategy articulated, execute one concrete action. The ratio matters more than the absolute numbers. + +### Principle 2: Start Where the World Is + +> "Don't await the perfection of Plato's Republic, but be satisfied with even the smallest step forward and regard the outcome as a small thing." -- Marcus Aurelius, *Meditations*, 9.29 + +The pragmatist begins with conditions as they are, not as they should be. This is not resignation -- it is the necessary precondition for effective action. The community organiser Saul Alinsky articulated the same principle two millennia later: "As an organiser I start from where the world is, as it is, not as I would like it to be." + +Founders violate this principle constantly. They design products for the customer they wish they had rather than the customer who exists. They build organisations for the talent market they imagine rather than the one that is hiring. They create strategies for the competitive landscape they prefer rather than the one that operates. + +The Stoic correction is precise: accept reality fully, then change it incrementally. Waiting for ideal conditions is the most common form of sophisticated procrastination. + +### Principle 3: Eliminate the Unnecessary + +> "It is essential for you to remember that the attention you give to any action should be in due proportion to its worth." -- Marcus Aurelius, *Meditations*, 4.32 + +Marcus Aurelius dedicated an entire meditation to what he called "corralling the unnecessary" -- the systematic elimination of actions, thoughts, and commitments that do not serve the essential purpose. His logic is economic: attention is the scarcest resource, and every unnecessary expenditure of it is a theft from something that matters. + +For founders, the unnecessary takes familiar forms: + +- **Meetings that exist because they have always existed,** not because they produce decisions. +- **Reporting that satisfies process but informs no one.** +- **Features built because competitors have them,** not because customers need them. +- **Strategic planning exercises that produce documents no one reads.** +- **Internal politics -- the most expensive form of unnecessary activity,** consuming energy that produces negative rather than zero output. + +The pragmatic discipline: before every action, ask Marcus's question -- "Is this one of the unnecessary things?" The honest answer, delivered without self-deception, eliminates more waste than any operational efficiency programme. + +Marcus extended this logic beyond actions to thoughts: "We must corral not only unnecessary actions but unnecessary thoughts, too, so needless acts don't tag along after them." The implication for founders is direct. Ruminating about a competitor's funding round, fantasising about a future exit, replaying a meeting that cannot be undone -- these are unnecessary thoughts that generate unnecessary actions. The Stoic practice is to notice the thought, assess its utility, and release what serves no purpose. + +### Principle 4: Make the Words Your Own + +> "I'll tell you how people can prove their words to be their own -- by putting into practice what they've been preaching." -- Seneca, *Moral Letters*, 108.35 + +The Stoics were remarkably unsentimental about intellectual property. Seneca quoted Epicurus -- his philosophical rival -- without embarrassment. Marcus Aurelius borrowed freely from every tradition available to him. The criterion was never originality; it was utility. Does it work? Does it make your life better? Does it produce results? Then use it, regardless of its source. + +This principle liberates the founder from the tyranny of purity. The best operational practices are often borrowed, adapted, and recombined from diverse sources. Amazon's "working backwards" process, Toyota's production system, Bridgewater's radical transparency -- none of these emerged from a single theoretical tradition. They were assembled pragmatically, tested relentlessly, and retained only insofar as they produced outcomes. + +Seneca would have approved. As he wrote: "I'll never be ashamed to quote a bad writer with a good saying." + +### Principle 5: The Pragmatic Relationship With Wealth + +> "No person has the power to have everything they want, but it is in their power not to want what they don't have, and to cheerfully put to good use what they do have." -- Seneca, *Moral Letters*, 123.3 + +Seneca was mocked in his own lifetime as "The Opulent Stoic" -- a philosopher of simplicity who had accumulated one of the largest fortunes in Rome. His response was not apologetic but pragmatic: he had wealth, but he was not enslaved by it. He could lose it tomorrow and continue to philosophise, write, and live well. The wealth was a tool, not an identity. + +This is the Stoic position on material success. The problem is not having money. The problem is needing money -- needing it so desperately that you compromise principles, destroy health, abandon relationships, and make decisions driven by financial anxiety rather than reasoned judgment. The pragmatic founder accumulates resources because resources enable action. But the founder who cannot distinguish between the resources and the purpose they serve has become, in Seneca's framework, a slave wearing expensive clothing. + +John D. Rockefeller, who accumulated more wealth than any person in modern history, arrived at a compatible conclusion through experience rather than philosophy: "A man's wealth must be determined by the relation of his desires and expenditures to his income." The pragmatic question is never "how much do I have?" but "how much do I need?" -- and whether the pursuit of the former is destroying the clarity required for the latter. + +--- + +## Prompts + +**Prompt 1 -- Theory-Practice Gap Analysis:** +> "Audit the gap between what my company says and what it does. Here are our stated values, strategies, and commitments: [list them]. Now here are the actual decisions we made in the past quarter: [list key decisions]. Where do the two diverge? For each gap, identify whether the problem is in the theory (wrong values), the practice (poor execution), or the alignment (right values, insufficient translation mechanisms). Provide a pragmatic action plan to close the three most critical gaps." + +**Prompt 2 -- Unnecessary Corralling Exercise:** +> "Apply Marcus Aurelius's 'corralling the unnecessary' discipline to my current operations. Here is how I spend my typical week: [describe weekly schedule and recurring commitments]. Here is what my company's core mission requires: [describe core activities]. Identify every activity, meeting, process, and commitment that does not directly serve the core mission. For each, recommend: eliminate, delegate, reduce, or retain. Be ruthless." + +**Prompt 3 -- Pragmatic Borrowing Audit:** +> "My company operates in [industry] at [stage]. I have been studying the following frameworks and methodologies: [list what you've been reading/learning]. Help me apply Seneca's pragmatic borrowing principle. For each framework, identify: (1) what is directly applicable to my situation right now, (2) what needs adaptation, (3) what is intellectual entertainment that I should set aside until it becomes relevant. Then design a 30-day execution plan using only the immediately applicable elements." + +**Prompt 4 -- First Impressions Decision Protocol:** +> "I am facing a decision that I have been overcomplicating: [describe the decision and the analysis you've done]. Apply the Stoic discipline of staying with first impressions. Strip the decision to its essential facts. Remove projected outcomes, political considerations, and hypothetical scenarios. Based on the facts alone, what is the obvious action? Then identify what was preventing me from seeing it." + +--- + +## Use Cases + +**The Strategy Retreat That Produces Nothing** + +A growth-stage B2B software company holds a two-day offsite every quarter. Each session produces a 40-page strategic plan, detailed OKRs, and a renewed sense of direction. By the third week after each retreat, the team has reverted to its previous patterns. The documents gather digital dust. Stoic pragmatism diagnoses the problem with surgical precision: the company has confused the production of strategic documents with the execution of strategy. The solution is not a better retreat format; it is a fundamental inversion of the ratio between planning and doing. The quarterly offsite is replaced with a monthly half-day session that reviews three metrics and makes three decisions. The 40-page document is replaced with a single page. The time saved is redirected to execution. Within two quarters, the company accomplishes more than the previous four retreat cycles produced combined. + +**The Founder Who Reads But Does Not Act** + +A validation-stage founder has consumed every major work on product development -- *The Lean Startup*, *Inspired*, *The Mom Test*, *Continuous Discovery Habits* -- and can articulate the principles of customer discovery, hypothesis testing, and iterative design with fluency that would impress a business school professor. The company has been in "validation" for fourteen months without shipping a product to a single paying customer. Musonius Rufus's verdict is clear: theory has become a substitute for action, not a preparation for it. The pragmatic intervention: the founder commits to shipping a minimum viable version within 30 days, using whatever imperfect tools and incomplete knowledge are currently available. The first version is embarrassing. The second version, informed by actual customer contact, is significantly better. By the fourth iteration, the company has paying customers and real data -- something fourteen months of reading never produced. + +**The Over-Engineered Culture Initiative** + +A scale-stage company hires a Chief People Officer who launches an ambitious culture transformation programme: new values workshops, quarterly engagement surveys, a 200-page culture handbook, mandatory training sessions. Eighteen months later, engagement scores have not changed. Marcus Aurelius's corralling principle reveals the problem: the programme created extensive documentation of desired culture but almost no mechanism for practising it. The pragmatic replacement: eliminate the handbook. Replace workshops with a single behavioural expectation reviewed in every team meeting. Replace the engagement survey with weekly one-question pulse checks that managers act on immediately. The company spends 70% less time on "culture initiatives" and sees measurable improvement within three months. Simplicity, as the Stoics understood, is not the absence of sophistication. It is its highest expression. + +--- + +## Anti-Patterns + +**Pragmatism as Anti-Intellectualism.** The Stoics were not hostile to theory. Marcus Aurelius studied philosophy for decades. Seneca wrote voluminously on ethics, natural science, and politics. The pragmatic principle is not "stop thinking" -- it is "don't stop at thinking." Founders who dismiss strategy, reflection, and learning as "ivory tower stuff" have overcorrected. Musonius Rufus said habit was *more* effective than theory, not that theory was worthless. + +**Confusing Speed With Progress.** Action without direction is not pragmatism; it is agitation. The founder who ships features nobody asked for, launches campaigns without hypotheses, and fills calendars with activity that produces no outcomes is busy, not pragmatic. Marcus Aurelius distinguished between what is necessary and what is merely happening. Pragmatism requires both action and discernment about which actions matter. + +**Simplicity as Simplism.** Eliminating the unnecessary is a discipline that requires judgment about what is truly unnecessary. Some things that appear unnecessary are actually load-bearing -- the weekly team check-in that seems like overhead but actually prevents misalignment; the documentation that no one reads until the day it prevents a catastrophic error. The corralling exercise demands honesty, not haste. + +**Borrowed Wisdom Without Adaptation.** Seneca's permission to pillage from all sources comes with an implicit condition: adaptation. The founder who imports Amazon's practices into a twelve-person startup, or applies Toyota's production system to a services business, has borrowed without translating. Every framework requires contextualisation. The pragmatist does not ask "what works?" in the abstract. They ask "what works *here*, *now*, for *us*?" + +**Using Pragmatism to Avoid Hard Truths.** "Let's just focus on execution" can be a legitimate prioritisation -- or it can be a way of avoiding difficult strategic questions that demand confrontation. The Stoic pragmatist faces reality as it is, which sometimes means sitting with uncomfortable truths rather than burying them under activity. + +**Discarding What Works Because It Is Old.** Seneca's counsel to "respect the past, but be open to the future" cuts both ways. "The ones who pioneered these paths aren't our masters, but our guides. Truth stands open to everyone." The pragmatist does not discard a practice merely because it is traditional, nor adopt a practice merely because it is novel. The only criterion is whether it works. Founders who chase the latest methodology while abandoning proven practices are not pragmatic; they are fashionable -- and fashion is a poor substitute for results. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Ship before you are ready; imperfect contact with reality beats perfect preparation in isolation | The greatest risk is analysis paralysis. The pragmatic founder tests the idea before refining it, knowing that the market will teach more in one week than research will teach in six months | +| Validation | Strip hypotheses to their simplest testable form; eliminate everything that does not produce a learning signal | Unnecessary complexity at this stage is often disguised as thoroughness. The pragmatic test: does this activity produce data that changes our next decision? If not, cut it | +| Early Traction | Build systems that are good enough, not perfect; optimise for speed of iteration over elegance of design | The temptation to professionalise too early -- hiring specialists, implementing enterprise tools, creating elaborate processes -- consumes resources that should be directed at serving customers | +| Growth | Systematise what works; eliminate what persists only by habit; resist the complexity creep that growth invites | Growth creates organisational scar tissue -- processes and structures that were solutions to past problems but are now obstacles to future ones. Regular corralling is essential | +| Scale | Preserve simplicity within institutional complexity; ensure that pragmatic execution culture survives formalisation | The paradox of scale: the very systems that enable growth also inhibit the pragmatic flexibility that created it. The Stoic discipline is to audit relentlessly -- not annual reviews, but continuous questioning of whether each process earns its existence | + +The progression follows an arc from individual pragmatism (idea and validation) to organisational pragmatism (early traction and growth) to institutional pragmatism (scale). At each stage, the enemy is different -- personal overthinking, team inefficiency, organisational inertia -- but the Stoic medicine is the same: act, simplify, adapt, repeat. + +--- + +## Output Template + +```markdown +# Pragmatic Execution Assessment + +## Theory-Practice Gap +| Stated Principle | Actual Behaviour | Gap Severity (1-5) | Root Cause | +|-----------------|-----------------|---------------------|------------| +| [Principle] | [What actually happens] | [Score] | [Why] | + +## Unnecessary Activity Audit +| Activity | Weekly Hours | Serves Core Mission? | Decision | +|----------|-------------|---------------------|----------| +| [Activity] | [Hours] | [Y/N/Partially] | [Eliminate/Delegate/Reduce/Retain] | + +## Recovered Capacity +- **Hours freed per week:** [Total] +- **Redirected to:** [Core activity] + +## Pragmatic Borrowing Plan +| Framework / Idea | Source | Applicable Element | Adaptation Needed | 30-Day Action | +|-----------------|--------|-------------------|-------------------|---------------| +| [Framework] | [Source] | [Element] | [Adaptation] | [Action] | + +## Next Three Actions (This Week) +1. [Action] -- [Expected outcome] +2. [Action] -- [Expected outcome] +3. [Action] -- [Expected outcome] +``` + +--- + +## Related Skills + +- **[Stoic Right Action](../../content/skills/stoic/stoic-right-action.md)** -- Pragmatism without ethics is mere efficiency; right action ensures that what gets done is worth doing. +- **[Stoic Problem Solving](../../content/skills/stoic/stoic-problem-solving.md)** -- The pragmatic companion to obstacle inversion: converting setbacks into usable advantages requires both reframing and execution. +- **[Stoic Duty and Service](../../content/skills/stoic/stoic-duty-and-service.md)** -- Duty provides the purpose that pragmatism serves; without it, efficiency becomes aimless optimisation. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- The operational expression of Marcus Aurelius's corralling principle, applied to modern calendars and task lists. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- When time compresses, pragmatism becomes survival -- the ability to act on first impressions without overthinking. +- **[Choosing and Executing](../../content/skills/decisions/choosing-and-executing.md)** -- The practical decision-making companion that addresses the moment of commitment and follow-through that Stoic pragmatism demands. diff --git a/plugins/foreman/skills/stoic-problem-solving/SKILL.md b/plugins/foreman/skills/stoic-problem-solving/SKILL.md deleted file mode 120000 index d54075f..0000000 --- a/plugins/foreman/skills/stoic-problem-solving/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-problem-solving.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-problem-solving/SKILL.md b/plugins/foreman/skills/stoic-problem-solving/SKILL.md new file mode 100644 index 0000000..157f4d2 --- /dev/null +++ b/plugins/foreman/skills/stoic-problem-solving/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "stoic-problem-solving" +description: "Teaches Marcus Aurelius's central method for converting obstacles into advantages, covering the reverse clause, creative reframing, persistence under adversity, and the discipline of focused action. Use when a startup faces setbacks that feel terminal, when market conditions shift against you, when key plans fail and alternatives seem absent, or when the team needs a framework for resilience and resourcefulness under pressure." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - resilience + - obstacles + - reframing + - adversity + - persistence + - problem-solving + - resourcefulness +related_skills: + - stoic-right-action + - stoic-pragmatism + - stoic-duty-and-service + - learning-from-failure + - leader-resilience-and-wellbeing + - scenario-planning +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Problem Solving + +Marcus Aurelius produced the most famous formula in practical philosophy with five words: "The obstacle on the path becomes the way." Not a metaphor. Not encouragement. A method. The Roman emperor who spent the better part of two decades fighting plagues, wars, betrayals, and the slow disintegration of an empire did not arrive at this principle through optimism. He arrived at it through necessity. The insight is structural: every impediment to action can be converted into a means of advancing action, provided the mind retains its capacity to adapt. For the entrepreneur -- whose daily existence is a sequence of plans colliding with reality -- this is not consolation philosophy. It is the operating system. + +--- + +## The Framework + +Stoic problem solving operates through three interlocking disciplines, each one a distinct cognitive skill that can be practised and strengthened. + +### Discipline 1: The Reverse Clause + +> "Indeed, no one can thwart the purposes of your mind -- for they can't be touched by fire, steel, tyranny, slander, or anything." -- Marcus Aurelius, *Meditations*, 8.41 + +The reverse clause is a contingency built into every intention. Before executing any plan, the Stoic adds a silent qualifier: *if conditions allow -- and if they don't, I will use whatever happens instead.* This is not pessimism. It is architectural resilience. + +The historical precedent is instructive. Zeno, the very founder of Stoicism, was a merchant whose ship sank along with its entire cargo. He washed up in Athens, wandered into a bookstore, discovered philosophy, and founded the school that would shape Western thought for two millennia. "Now that I've suffered shipwreck," Zeno reportedly said, "I'm on a good journey." The entire philosophy is built on the principle it teaches. + +Consider how this works in practice. A startup plans to launch a product in Q2. The reverse clause says: if the launch is delayed by a supply chain failure, that delay becomes an opportunity to refine the onboarding experience, stress-test the infrastructure, or build anticipation through a controlled beta. The plan has not failed. It has adapted. + +The reverse clause transforms the emotional experience of setbacks. Without it, every disruption feels like a defeat. With it, disruptions become redirections -- pre-authorised by the founder's own reasoning. + +### Discipline 2: The Inversion of Obstacles + +> "The mind adapts and converts any obstacle to its action into a means of achieving it. That which is an impediment to action is turned to advance action." -- Marcus Aurelius, *Meditations*, 5.20 + +This is the core mechanism. When an obstacle blocks the intended path, the Stoic does not merely find an alternative route. The Stoic asks: *what virtue or advantage does this specific obstacle make possible?* + +The logic runs as follows: + +- If a competitor launches first, it becomes a chance to learn from their mistakes and their market education costs. +- If a key hire declines the offer, it becomes a chance to re-examine whether the role was correctly scoped. +- If funding falls through, it becomes a chance to build a leaner, more capital-efficient operation that will be structurally stronger when funding eventually arrives. +- If a customer churns, it becomes a chance to practice the discipline of honest post-mortem analysis. + +Nick Saban, the legendary college football coach, built his dynasty on what he called "The Process" -- ignoring the scoreboard and focusing exclusively on executing the next play. This is Stoic problem solving in athletic clothing. The accumulation of correctly executed small actions -- each one a response to whatever the present moment demands -- produces results that grand strategy alone cannot. + +Marcus Aurelius captured this with the metaphor of building: "You must build up your life action by action, and be content if each one achieves its goal as far as possible." The operative phrase is "as far as possible." The Stoic does not demand perfection from each action. The demand is for full engagement -- brick by boring brick, each one laid as well as current conditions allow. + +### Discipline 3: Staying Within First Impressions + +> "Don't let your reflection on the whole sweep of life crush you. Don't fill your mind with all the bad things that might still happen. Stay focused on the present situation." -- Marcus Aurelius, *Meditations*, 8.36 + +Problems become unsolvable when they expand beyond their actual dimensions. A cash flow squeeze in March becomes, in the founder's anxious imagination, a bankruptcy in July, a reputation collapse in September, an unemployable future in December. The Stoic discipline is to stop at the first impression -- the actual, present problem -- and refuse to let catastrophic narration inflate it. + +Marcus Aurelius's instruction: stick with the facts as initially reported. Someone is speaking badly about you -- that is the report. The report does not include that you have been harmed. Your runway is shorter than projected -- that is the fact. The fact does not include that the company is finished. + +This discipline is the difference between a problem that can be solved and a crisis that cannot be endured. Nearly every problem, stripped of its imagined extensions, is manageable. + +Seneca reinforced this principle with characteristic pragmatism: "Apply yourself to thinking through difficulties -- hard times can be softened, tight squeezes widened, and heavy loads made lighter for those who can apply the right pressure." The "right pressure" is focused attention on the actual problem, not the imagined cascade of consequences that the anxious mind projects onto it. + +### The Problem-Solving Sequence + +Combining the three disciplines produces a repeatable protocol: + +1. **Encounter the obstacle.** Do not get emotional. Marcus's first rule: don't get worked up. +2. **Stay with first impressions.** What is the actual problem, stripped of projected catastrophe? +3. **Activate the reverse clause.** What opportunity does this specific obstacle create? +4. **Invert the obstacle.** What virtue, skill, or advantage can be practised or built precisely because of this setback? +5. **Execute the next right action.** Brick by boring brick. One correct step, then the next. + +The sequence is designed to be executed rapidly -- in minutes, not days. The longer the gap between encountering an obstacle and initiating the response, the more opportunity catastrophic narration has to inflate the problem beyond its actual dimensions. Speed of cognitive reframe is itself a trainable skill. + +--- + +## Prompts + +**Prompt 1 -- Obstacle Inversion Analysis:** +> "My startup is facing the following obstacle: [describe the obstacle in factual terms]. Apply the Stoic problem-solving framework. First, strip the problem to its first impressions -- what is actually happening versus what I fear might happen. Second, identify the reverse clause -- what alternative paths does this obstacle open. Third, invert the obstacle -- what specific advantage, virtue, or capability can be built precisely because of this setback. Provide three concrete next actions." + +**Prompt 2 -- Setback Pattern Recognition:** +> "Here are the three biggest setbacks my company has experienced in the past year: [list setbacks]. For each one, apply the Stoic inversion lens retroactively. What advantages did we gain (or could we have gained) from each setback? Are there patterns in how we respond to obstacles that reveal systematic weaknesses in our problem-solving? What Stoic disciplines would most improve our collective resilience?" + +**Prompt 3 -- Pre-Mortem With Reverse Clauses:** +> "We are about to execute [describe plan]. Using the Stoic reverse clause method, identify the five most likely obstacles we will encounter. For each obstacle, design a specific reverse clause -- a pre-committed alternative path that converts the obstacle into an advantage. Format as a contingency playbook I can share with my team." + +**Prompt 4 -- First Impressions Audit:** +> "I am currently overwhelmed by what feels like an existential threat to my business: [describe the situation]. Help me apply Marcus Aurelius's discipline of staying within first impressions. Separate the factual situation from my projected catastrophe. What is actually happening right now? What is merely my anxious extrapolation? Then identify one concrete action I can take in the next two hours." + +--- + +## Use Cases + +**The Failed Product Launch** + +An early-traction e-commerce platform spends four months preparing a major feature launch. On launch day, a critical bug renders the checkout flow unusable for 30% of users. Revenue projections for the quarter are immediately threatened. The standard reaction: panic, blame, emergency all-hands meetings that consume three days of engineering time. The Stoic response: stay within first impressions (the bug exists; the company does not). Activate the reverse clause (the bug reveals a gap in QA processes that, once fixed, will prevent larger failures later). Invert the obstacle (the public response to the bug -- transparent communication, rapid fix, customer credits -- becomes a trust-building event that no marketing campaign could replicate). The company's NPS scores increase in the following month. The obstacle became the way. + +Seneca's observation applies: "Rivers are easiest to cross at their source." The bug was caught on launch day, not six months later when the customer base was ten times larger. The obstacle, properly inverted, revealed its timing as an advantage. + +**The Investor Who Walked Away** + +A validation-stage deep-tech startup receives a verbal commitment from a lead investor for a $3 million seed round. Two weeks before closing, the investor pulls out, citing "portfolio rebalancing." The other participants in the round withdraw in a domino effect. The founder, facing six months of runway, has two options: despair or inversion. The Stoic approach: the lost round forces a leaner operating model that extends runway to eleven months. The extra time, combined with reduced burn, produces stronger unit economics. When the founder returns to market three months later, the metrics are significantly more compelling. The company raises $5 million instead of $3 million, at a higher valuation, from investors who are more aligned with the company's actual trajectory rather than its projections. + +**The Regulatory Surprise** + +A growth-stage healthtech company learns that new regulations will require significant changes to its data handling practices, adding six months and substantial cost to its roadmap. Competitors publicly complain and lobby against the regulation. The Stoic founder inverts: the regulation creates a compliance barrier that will eliminate smaller, less-resourced competitors. The company invests aggressively in compliance, finishes early, and markets its regulatory readiness as a differentiator. The obstacle -- a regulatory burden -- becomes a moat. + +--- + +## Anti-Patterns + +**Toxic Positivity Masquerading as Stoicism.** "Everything happens for a reason" is not what Marcus Aurelius wrote. He wrote that every obstacle can be used -- not that every obstacle is secretly good. The distinction matters. Stoic problem solving does not require the founder to pretend that losing a key employee or missing a revenue target is secretly wonderful. It requires the founder to ask what can be done *with* the situation, not to fabricate gratitude for it. + +**Passivity Dressed as Acceptance.** The reverse clause is not permission to give up on the original plan at the first sign of difficulty. Seneca warned against those who are "too unstable to live as they wish, but only live as they have begun." The Stoic changes course when the obstacle is genuine and the reversal offers a better path -- not when the work simply becomes hard. + +**Intellectualising Instead of Acting.** The Stoic framework is a decision tool, not a journaling exercise. Founders who spend hours analysing the philosophical dimensions of their setbacks while taking no concrete action have inverted the priority. Marcus Aurelius wrote his meditations in brief, often single-paragraph entries between governing an empire and commanding armies. The thinking serves the doing, never the reverse. + +**Ignoring the Emotional Dimension.** The instruction "don't get worked up" is not the same as "don't feel anything." The Stoics acknowledged that initial emotional reactions are involuntary -- what they called *propatheiai* (pre-emotions). The discipline is in what happens next: whether the emotion drives the response or whether reasoned judgment intervenes. Founders who suppress emotion entirely often find it erupting at worse moments. The goal is not emotional absence but emotional governance. + +**Applying the Framework in Isolation.** Stoic problem solving is a leadership practice, not a private coping mechanism. The founder who silently inverts obstacles without communicating the reframe to the team misses the multiplier effect. As the Navy SEALs say: "Calm is contagious." When the founder models factual assessment and forward-looking action in front of the team, the entire organisation's capacity for resilience increases. The obstacle becomes the way not just for the individual but for the collective. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Building the mental habit of obstacle inversion before real obstacles arrive | Problems at this stage are mostly internal -- self-doubt, analysis paralysis, fear of starting. The obstacle is the mind itself, and the discipline of first impressions is the primary tool | +| Validation | Converting negative market signals into sharper product hypotheses | Every "no" from a potential customer contains information. The reverse clause here is systematic: rejection feeds iteration. Founders who cannot invert validation failure will not survive this stage | +| Early Traction | Managing operational setbacks without losing momentum or team morale | The team is watching the founder's response to adversity. Calm is contagious. The founder who models Stoic problem solving -- factual assessment, reverse clause, immediate action -- teaches the team to do the same | +| Growth | Turning competitive threats and scaling failures into structural improvements | At growth stage, obstacles are systemic rather than episodic. A single customer loss is survivable; a pattern of churn requires the deeper Stoic discipline of honest diagnosis without catastrophic narration | +| Scale | Navigating institutional crises (regulatory, reputational, market-wide) with composure | The founder's role shifts from problem-solver to problem-framing leader. The Stoic disciplines must be embedded in organisational culture, not held privately by the founder | + +The progression across stages follows a pattern: from personal resilience (idea and validation) to collective resilience (early traction and growth) to institutional resilience (scale). The Stoic method remains identical; its application widens. + +One critical insight applies across all stages: the quality of problem solving is determined before the problem arrives. Epictetus compared philosophy to boxing training: "What kind of boxer are you if you leave because you get hit? That's the nature of the sport!" The founder who practises the reverse clause on small setbacks -- a missed deadline, a difficult customer, a minor technical failure -- builds the cognitive muscle that will fire automatically when the existential threat arrives. Training cannot begin at the moment of crisis. It must precede it. + +--- + +## Output Template + +```markdown +# Obstacle Inversion Brief + +## The Obstacle +- **Factual description (first impressions only):** [What has actually happened] +- **Projected catastrophe (to be set aside):** [What you fear will happen] +- **Actual scope:** [Time horizon, financial impact, stakeholders affected] + +## Reverse Clause Analysis +- **Original plan:** [What you intended to do] +- **What the obstacle blocks:** [Specifically which element is impeded] +- **Alternative paths opened:** [What becomes possible because of this obstacle] + +## Obstacle Inversion +- **Virtue or skill this obstacle trains:** [What capability is strengthened] +- **Competitive advantage created:** [How this setback positions you better] +- **Hidden information revealed:** [What you now know that you didn't before] + +## Next Actions (Brick by Brick) +1. **Within 24 hours:** [Immediate concrete action] +2. **Within one week:** [Follow-through action] +3. **Within one month:** [Structural change or new initiative] + +## Team Communication +- **Message to team:** [How to frame this for collective resilience] +- **Tone:** [Factual, calm, forward-looking] +``` + +--- + +## Related Skills + +- **[Stoic Right Action](../../content/skills/stoic/stoic-right-action.md)** -- Problem solving must be guided by ethical judgment; cleverness without virtue produces worse problems. +- **[Stoic Pragmatism](../../content/skills/stoic/stoic-pragmatism.md)** -- The pragmatic companion to obstacle inversion, ensuring solutions are actionable rather than merely philosophical. +- **[Stoic Duty and Service](../../content/skills/stoic/stoic-duty-and-service.md)** -- Obstacles are not merely personal challenges; they are opportunities to fulfil one's duty to others. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- The systematic extraction of insight from setbacks, complementing the Stoic reframing method. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- A structured approach to anticipating obstacles before they arrive, aligned with the Stoic reverse clause. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The structural problem-definition discipline complements the Stoic reframing approach with root-cause analysis and the 3-Lens Principle. diff --git a/plugins/foreman/skills/stoic-right-action/SKILL.md b/plugins/foreman/skills/stoic-right-action/SKILL.md deleted file mode 120000 index 92c9063..0000000 --- a/plugins/foreman/skills/stoic-right-action/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-right-action.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-right-action/SKILL.md b/plugins/foreman/skills/stoic-right-action/SKILL.md new file mode 100644 index 0000000..837aac2 --- /dev/null +++ b/plugins/foreman/skills/stoic-right-action/SKILL.md @@ -0,0 +1,201 @@ +--- +name: "stoic-right-action" +description: "Applies Stoic ethics of right action to entrepreneurial decision-making, covering the four cardinal virtues (courage, justice, temperance, wisdom), ethical leadership under pressure, and the discipline of choosing the harder right over the easier wrong. Use when facing ethical dilemmas in business, building a values-driven culture, making decisions with imperfect information, navigating conflicts between profit and principle, or establishing personal and organizational codes of conduct." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - ethics + - decision-making + - leadership + - character + - values + - courage + - integrity +related_skills: + - stoic-problem-solving + - stoic-duty-and-service + - stoic-pragmatism + - emotional-courage + - purpose-driven-leadership + - trust-equation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Right Action + +Every day brings dozens of crossroads -- moments where the easy path and the right path diverge, sometimes subtly, sometimes violently. The Stoics had one question at each: *what is the right thing to do?* Not what is profitable, not what is popular, not what is safe. What is right. Marcus Aurelius governed an empire with this single compass. Epictetus taught it from a room he could barely afford. Seneca deployed it while navigating one of the most treacherous courts in Roman history. The question never changed. The circumstances were irrelevant. For the entrepreneur, who faces a relentless sequence of decisions under uncertainty, this is not philosophical decoration. It is operational infrastructure. + +--- + +## The Framework + +Stoic ethics rests on four cardinal virtues, each one a load-bearing pillar without which the structure collapses. These are not aspirational ideals. They are daily practices -- habits of judgment that the Stoics treated with the same seriousness a pilot treats a pre-flight checklist. Marcus Aurelius distilled the entire edifice to a single sentence: "What is your vocation? To be a good person." The simplicity is deceptive. The execution is the work of a lifetime. + +### The Four Cardinal Virtues + +**Courage (Andreia):** The capacity to act rightly under conditions of risk, fear, or social pressure. Courage is not the absence of fear but the judgment that something else matters more. For founders, this manifests in hard conversations -- telling investors the truth about burn rate, firing a popular but toxic executive, admitting a product direction was wrong. As Seneca observed: "Good people will do what they find honorable to do, even if it requires hard work; they'll do it even if it causes them injury; they'll do it even if it will bring danger." + +**Justice (Dikaiosyne):** Treating every person -- co-founder, customer, employee, competitor -- according to their due. Justice in the Stoic sense is not legalism. It is the active commitment to fairness in a world that constantly incentivises partiality. Marcus Aurelius wrote that "the unjust person acts against the gods" because rational beings were made for mutual benefit, not exploitation. The entrepreneur who pays invoices late to preserve cash flow, who uses asymmetric information to extract better terms, who treats vendors differently from customers -- each is committing an injustice that the Stoics would recognise instantly. + +**Temperance (Sophrosyne):** Self-control and moderation -- the virtue that prevents success from becoming its own undoing. The startup ecosystem worships growth at all costs, celebrates excess as ambition, and confuses discipline with timidity. Temperance is the corrective. It governs spending, ego, risk appetite, and the thousand small indulgences that compound into disaster. Musonius Rufus asked a pointed question that every well-funded founder should hear: "How much better is it to be known for doing well by many than for living extravagantly?" The answer, in every era, is the same. + +**Wisdom (Phronesis):** The ability to discern what is truly good, truly bad, and truly indifferent. Wisdom is the master virtue because it directs the other three. Without wisdom, courage becomes recklessness, justice becomes rigidity, and temperance becomes paralysis. Epictetus's formulation is surgical: "Where is Good? In our reasoned choices. Where is Evil? In our reasoned choices." + +### The Decision Architecture + +The Stoics did not leave right action to intuition. Marcus Aurelius articulated a two-step protocol for every decision: + +1. **Don't get worked up.** Emotional agitation distorts judgment. Whatever has happened, it is not as unprecedented as it feels. Emperors and beggars alike have faced worse. The first step is always to create the internal conditions for clear thought. +2. **Remember your principles and act.** Run the decision through your values. The answer almost always clarifies itself. The second step converts clarity into motion. + +> "Don't get upset. Do the right thing. That's it." -- Marcus Aurelius, *Meditations*, 8.5 + +This is deceptively simple. The difficulty lies not in understanding it but in executing it at speed, under pressure, when the stakes are personal. The Stoics knew this, which is why they treated ethics as a practice -- something trained daily, not consulted occasionally. + +Epictetus reinforced the point with a boxing metaphor: philosophy is training for life. "Don't you understand that really amounts to saying that if I would so prepare myself to endure, then let anything happen that will? Otherwise, it would be like the boxer exiting the ring because he took some punches." The entrepreneur who has not trained the ethical reflex before the ethical test arrives will not pass it. The test comes without warning, and there is no time to consult the manual. + +The practical implication: ethical decision-making should be rehearsed -- in team discussions, in scenario planning, in the private daily review that Marcus practised until the final days of his life. It is never too late to begin, and no one is too experienced to continue. + +### Character as Competitive Advantage + +Musonius Rufus argued that philosophy "doesn't consist in outward display, but in taking heed to what is needed and being mindful of it." The Stoic is identified not by uniform or proclamation but by character alone. In business, this translates to a simple observation: reputation compounds. Every ethical shortcut is a withdrawal from an account that takes years to build and seconds to deplete. + +The entrepreneur who acts rightly -- not performatively, not strategically, but as a matter of settled disposition -- attracts better partners, retains better employees, and earns the trust of customers who have learned, through bitter experience, to distrust everyone else. As Epictetus put it: "First tell yourself what kind of person you want to be, then do what you have to do." + +### The Chain of Small Choices + +Zeno, the founder of Stoicism, reportedly said that "well-being is realized by small steps, but is truly no small thing." The architecture of right action is not built from dramatic, headline-worthy ethical stands. It is assembled from hundreds of small choices -- how you respond to a frustrating email, whether you credit a colleague's contribution in a meeting, whether you round the invoice up or down, whether you share bad news promptly or bury it in a quarterly review. + +Each small choice reinforces a disposition. Epictetus used the metaphor of fuel and fire: "Every habit and capability is confirmed and grows in its corresponding actions." The founder who practises justice in trivial matters -- splitting a restaurant bill fairly, acknowledging an intern's idea -- is training the neural pathways that will fire automatically when justice is required in a $10 million negotiation. Conversely, the founder who cuts small corners is rehearsing for the day when the corner is not small at all. + +The Stoic discipline is to treat every decision as a character-forming event. Not because every decision is equally consequential, but because the habit of choosing rightly is what makes consequential decisions tractable when they arrive without warning. + +--- + +## Prompts + +**Prompt 1 -- Ethical Crossroads Audit:** +> "I am facing a business decision where the profitable path and the ethical path seem to diverge. Here is the situation: [describe situation]. Apply the four Stoic cardinal virtues (courage, justice, temperance, wisdom) as separate lenses. For each virtue, identify what it demands in this specific case. Then synthesize: what is the right action, and what is the likely cost of taking it versus avoiding it?" + +**Prompt 2 -- Character Stress Test:** +> "Evaluate my company's recent decisions through a Stoic ethical lens. Here are the three most significant decisions we made in the past quarter: [list decisions]. For each, assess: (1) Did we choose the harder right or the easier wrong? (2) Which cardinal virtue was most tested? (3) Where did we compromise, and was the compromise justified? Provide a character score and specific recommendations." + +**Prompt 3 -- Values Integration Blueprint:** +> "Help me translate Stoic principles of right action into concrete operating practices for my startup. My company is at [stage] in [industry] with [team size] people. I want to embed ethical decision-making into our daily operations -- not as a poster on the wall but as a decision protocol. Design a practical system that includes hiring criteria, decision frameworks, and accountability mechanisms rooted in the four cardinal virtues." + +**Prompt 4 -- Courage Calibration:** +> "I have been avoiding a difficult but necessary action in my business: [describe the avoided action]. Using the Stoic framework of right action, help me understand why I am avoiding it, what courage specifically requires in this situation, and create a concrete plan for executing it within the next 48 hours. Include the Stoic perspective on why delay makes it worse." + +--- + +## Use Cases + +**The Co-Founder Equity Dispute** + +A validation-stage SaaS startup discovers that one of three co-founders has been contributing significantly less than the other two for six months. The contributing founders avoid the conversation because the third co-founder was the original idea holder and has personal financial difficulties. Stoic right action demands courage (having the conversation), justice (restructuring equity to reflect actual contribution, not sentiment), temperance (doing so without vindictiveness), and wisdom (recognizing that unaddressed resentment will destroy the company faster than an uncomfortable conversation). Marcus Aurelius's two-step protocol applies directly: don't get emotional, then do what is right. The conversation happens. The equity is restructured. The company survives. + +**The Enterprise Customer With Conditions** + +A growth-stage fintech company lands a potential enterprise deal worth 40% of annual revenue. The customer requests a "minor" data-sharing arrangement that technically complies with regulations but violates the spirit of the company's privacy commitments to individual users. The sales team argues that no one will know. Stoic justice -- treating every person according to their due, including the users who trusted the company -- makes the answer clear. The deal is declined or renegotiated. Seneca's observation resonates: "The greatest portion of peace of mind is doing nothing wrong." + +**The Layoff Communication** + +A scale-stage company must reduce headcount by 15%. The CFO recommends announcing via email on a Friday afternoon to "minimize disruption." Stoic right action recognizes this for what it is: cowardice dressed as efficiency. Courage demands face-to-face communication. Justice demands transparent explanation. Temperance demands that leadership absorb the discomfort rather than offload it onto departing employees. The layoffs happen with dignity, and the remaining team's trust in leadership deepens rather than fractures. + +Marcus Aurelius sold imperial furnishings to pay war debts rather than taxing an already burdened populace. The modern parallel: the founder who takes a salary cut before reducing headcount, who communicates transparently about the company's financial position, who treats departing employees as people rather than line items. Right action in moments of crisis is not merely ethically superior. It is strategically superior, because the people who remain are watching, and they will remember how leadership behaved when the pressure was real. + +--- + +## Anti-Patterns + +**Virtue Signalling Without Virtue.** Posting values on the website while violating them in practice is not Stoicism; it is marketing. The Stoics were explicit that philosophy must be demonstrated through action, not words. Epictetus warned against those who "receive the bare theories" and "immediately want to spew them." If the company's stated values do not match its actual decisions, the values statement is worse than useless -- it is a liability, creating expectations the organisation has no intention of meeting. + +**Moral Perfectionism as Paralysis.** Some founders interpret "right action" as requiring certainty of ethical purity before any action can be taken. This is a misunderstanding. The Stoics were pragmatists. Marcus Aurelius explicitly cautioned against waiting for "the perfection of Plato's Republic." Right action often means making the best available choice under imperfect conditions, not waiting for a flawless option that will never arrive. + +**Confusing Comfort With Conscience.** The feeling of discomfort is not evidence that an action is wrong. More often, it is evidence that the action is right but difficult. Founders who avoid hard conversations, tough feedback, or unpopular decisions because they "don't feel right" are confusing the signal. The Stoic framework insists on reasoned judgment, not emotional comfort, as the guide. + +**Weaponising Ethics Against Others.** Using Stoic principles to judge others rather than govern oneself is the precise inversion of the practice. Marcus Aurelius's meditations are self-directed -- he interrogates his own conduct, not his subordinates'. Founders who deploy ethical language to control, shame, or manipulate their teams have missed the point entirely. + +**Selective Virtue Application.** Applying courage in investor meetings but not in employee feedback sessions. Practising justice with customers but not with vendors. Exercising temperance in public spending but indulging privately. The cardinal virtues are not situation-specific tools to be deployed strategically. They are character traits that either permeate everything or exist nowhere. Marcus Aurelius's reminder is pointed: "How you do anything is how you do everything." + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Establishing personal ethical foundations before external pressures arrive | Right action is cheapest here -- there are few stakeholders, few temptations, and maximum freedom to set precedent | +| Validation | Honest assessment of product-market signals; resisting the temptation to cherry-pick data | The pressure to show traction creates incentives to deceive -- investors, customers, oneself. Courage means reporting what the data actually shows | +| Early Traction | Building culture through hiring and firing decisions that reflect stated values | Every early hire is a cultural statement. Justice demands consistent application of standards regardless of how desperate you are for talent | +| Growth | Maintaining ethical consistency as scale introduces complexity and delegation | Right action must become systemic, not personal. The founder cannot be present at every decision; the virtues must be embedded in process and people | +| Scale | Navigating institutional pressures (board expectations, market demands) that test foundational commitments | The hardest stage for right action. The company is now an institution with its own momentum, and the founder's ethical convictions face pressure from stakeholders who measure only outcomes | + +At every stage, the Stoic insight holds: the cost of ethical compromise is always higher than it appears, and it compounds. The founder who cuts a corner at the idea stage creates a precedent that metastasises through every subsequent phase. Seneca's warning about vices applies directly: "There is no vice which lacks a defense, none that at the outset isn't modest and easily intervened -- but after this the trouble spreads widely." Ethical drift begins as a trickle and ends as a flood. + +The practical implication is that right action is an investment with asymmetric returns: the cost of maintaining it is constant and modest, while the cost of recovering from its absence is catastrophic and unpredictable. + +Marcus Aurelius understood this arithmetic intimately. His daily practice of self-examination -- questioning his own choices, testing his reasoning, holding himself accountable before sleep -- was not self-indulgence. It was maintenance. The founder who adopts a similar practice, even five minutes of honest review at day's end, builds the compound interest of character that no crisis can liquidate overnight. + +--- + +## Output Template + +```markdown +# Ethical Decision Analysis + +## The Crossroads +- **Decision required:** [Describe the decision] +- **Stakeholders affected:** [List all parties] +- **Time pressure:** [Urgency level and deadline] + +## Cardinal Virtue Assessment + +### Courage +- **What courage demands:** [Specific action] +- **What fear suggests instead:** [The avoidance path] + +### Justice +- **Who is owed what:** [Stakeholder-by-stakeholder assessment] +- **Where fairness is at risk:** [Identify potential injustice] + +### Temperance +- **What excess looks like here:** [The overreaction] +- **What moderation requires:** [The disciplined response] + +### Wisdom +- **What is truly at stake:** [Separate real from apparent stakes] +- **What is indifferent:** [What can be released] + +## The Right Action +- **Decision:** [Clear statement] +- **Rationale:** [Why this is right, not merely expedient] +- **Expected cost:** [Honest assessment of the price] +- **Long-term consequence of avoidance:** [What happens if you don't] + +## Execution Plan +- **Step 1:** [Immediate action] +- **Step 2:** [Follow-through] +- **Step 3:** [Accountability mechanism] +``` + +--- + +## Related Skills + +- **[Stoic Problem Solving](../../content/skills/stoic/stoic-problem-solving.md)** -- When right action meets an obstacle, the obstacle itself becomes the path forward. +- **[Stoic Duty and Service](../../content/skills/stoic/stoic-duty-and-service.md)** -- Right action without a sense of duty is episodic; duty makes it structural. +- **[Stoic Pragmatism](../../content/skills/stoic/stoic-pragmatism.md)** -- The bridge between knowing the right thing and actually doing it under real-world constraints. +- **[Emotional Courage](../../content/skills/leadership/emotional-courage.md)** -- The leadership competency most directly tested by Stoic right action; taking principled stands requires practised courage. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Right action is the primary input to the trust that compounds over a company's lifetime. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- Values-based leadership as an organisational design principle, translating Stoic ethics into collective mission. +- **[Covey's Seven Habits](../../content/skills/frameworks/covey-seven-habits.md)** -- The principle-centred leadership model that shares Stoicism's emphasis on character as the foundation of effectiveness. diff --git a/plugins/foreman/skills/stoic-self-awareness/SKILL.md b/plugins/foreman/skills/stoic-self-awareness/SKILL.md deleted file mode 120000 index 239fd47..0000000 --- a/plugins/foreman/skills/stoic-self-awareness/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-self-awareness.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-self-awareness/SKILL.md b/plugins/foreman/skills/stoic-self-awareness/SKILL.md new file mode 100644 index 0000000..94398db --- /dev/null +++ b/plugins/foreman/skills/stoic-self-awareness/SKILL.md @@ -0,0 +1,201 @@ +--- +name: "stoic-self-awareness" +description: "Applies Stoic practices of self-examination to entrepreneurial leadership, drawing on Seneca's evening review, Epictetus's teaching on honest self-assessment, and Marcus Aurelius's private journaling discipline. Covers blind spots, the gap between self-image and reality, integration of character, and continuous philosophical self-scrutiny. Use when suspecting blind spots in leadership, receiving feedback that contradicts self-image, seeking a structured introspection practice, struggling with integrity under pressure, or building habits of ongoing self-examination." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - self-awareness + - self-examination + - evening-review + - blind-spots + - integrity + - seneca + - marcus-aurelius + - journaling +related_skills: + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-unbiased-thought + - leader-self-reflection + - johari-window + - learning-from-failure + - psychological-safety +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Self-Awareness + +Seneca reviewed his entire day every evening before sleep -- most modern leaders haven't examined a single day this year. That asymmetry explains a great deal about why ancient philosophers who governed empires and survived exile seem, across the centuries, to have possessed greater equanimity than contemporary executives armed with executive coaches, wellness apps, and retreats in Sedona. The Stoics treated self-awareness not as a personality trait or a luxury of the contemplative life but as a discipline -- something practised with the regularity and rigour of physical training. "I will keep constant watch over myself," Seneca writes, "and -- most usefully -- will put each day up for review. For this is what makes us evil -- that none of us looks back upon our own lives." + +--- + +## The Framework + +### The Evening Review: Seneca's Core Practice + +In a letter to his brother Novatus, Seneca describes the habit he borrowed from the Pythagorean tradition and refined for Stoic purposes. Each night, after his wife had gone to sleep, he would conduct a systematic audit of the day. Three questions structured the exercise: + +1. **What bad habit did I curb today?** +2. **How am I better?** +3. **Were my actions just?** + +The critical feature of this practice is its tone. Seneca is explicit that the review is not self-flagellation. "I conceal nothing from myself, I pass over nothing," he writes, but "what need I fear from my own mistakes, when I can say: See that you don't do that anymore. I forgive you this time." The evening review is forensic, not punitive. It seeks understanding, not guilt. For the entrepreneur, this distinction is essential: the review that spirals into shame is worse than no review at all, because it teaches the mind to avoid introspection. + +### Honest Self-Assessment: The Dual Failure + +Seneca identifies what might be called the dual failure of self-knowledge: "Above all, it is necessary for a person to have a true self-estimate, for we commonly think we can do more than we really can." Goethe later expanded the insight: it is equally damaging to see yourself as more than you are and to value yourself at less than your true worth. + +Entrepreneurs are particularly susceptible to both errors, often simultaneously. The founder who dramatically overestimates product-market fit may simultaneously underestimate her capacity to navigate a pivot. The CEO who believes he is an excellent communicator (overestimate) may not realise how well he handles crisis management (underestimate). The Stoic corrective is not modesty or confidence but *accuracy* -- the relentless pursuit of a self-image that matches reality. + +### The Gap Between Self-Image and Behaviour + +Epictetus delivers one of Stoicism's most uncomfortable observations: "You must be a unified human being, either good or bad. You must diligently work either on your own reasoning or on things out of your control -- take great care with the inside and not what's outside, which is to say, stand with the philosopher, or else with the mob." The implication is that most people live in a state of internal division -- professing values they do not practise, believing themselves to be one kind of person while behaving as another. + +This (dis)integration is not hypocrisy in the theatrical sense. It is the natural consequence of insufficient self-examination. The founder who values transparency but avoids difficult conversations is not lying; she has simply never noticed the contradiction. The CEO who prizes innovation but punishes failure has never examined the gap between his stated and revealed preferences. Awareness of these gaps -- achieved through the disciplined practices outlined below -- is the prerequisite for closing them. + +### The Role of External Mirrors + +"Find yourself a Cato," Seneca advises -- a person of such character that their imagined presence regulates your behaviour. Adam Smith later developed a similar concept, the "impartial spectator," an internalised observer who judges our conduct from a position of disinterested wisdom. + +The practice has both internal and external dimensions. Internally, the entrepreneur asks: "If the person I most respect were watching, would I still make this choice?" Externally, the entrepreneur cultivates relationships with people who will tell the truth -- not flatterers, not sycophants, but what Epictetus would call philosophical sparring partners. Marcus Aurelius opens the *Meditations* with an extraordinary catalogue of gratitude, thanking by name every person who taught him something about his own character: from his mother, he learned generosity; from his adoptive father, steadiness; from Rusticus, the habit of deep reading and honest self-correction. + +### Freedom Through Awareness + +The Stoics draw a direct line from self-awareness to freedom. "The person is free who lives as they wish," Epictetus writes, "neither compelled, nor hindered, nor limited." But he immediately adds the corollary: "Who wishes to live in deception -- tripped up, mistaken, undisciplined, complaining, in a rut? No one." Freedom, in the Stoic framework, is impossible without self-knowledge, because you cannot choose well if you do not know what drives your choices. + +Seneca reinforces this with a practical example: many people are slaves to obligations they never examined, to habits they never questioned, to relationships they maintain out of inertia. "No slavery is more disgraceful than one which is self-imposed." The self-aware entrepreneur, by contrast, periodically inventories obligations and asks which are genuinely necessary, which are self-imposed, and which exist only because no one ever stopped to question them. + +Marcus Aurelius adds a further dimension: you are a product of your training, and your training is a product of your awareness. "A dog that's allowed to chase cars will chase cars. A child who is never given any boundaries will become spoiled." The implication for founders is direct. Every unexamined habit, every unquestioned assumption, every avoided confrontation is training -- training yourself to be a particular kind of leader, whether or not you intended it. Self-awareness is the mechanism by which you choose your training deliberately rather than absorbing it by default. + +--- + +## Prompts + +**Prompt 1 -- Evening Review Protocol:** +> Guide me through Seneca's evening review for today as CEO of [company]. Ask me Seneca's three questions (What bad habit did I curb? How am I better? Were my actions just?) and then probe deeper: Where did I act from principle versus impulse? Where did my behaviour contradict my stated values? What pattern do I see emerging across recent days? Maintain a forensic, non-punitive tone throughout. + +**Prompt 2 -- Self-Image Accuracy Test:** +> Help me conduct an honest self-assessment as a leader. I'll describe how I see myself across five dimensions: [communication, decision-making, emotional regulation, strategic thinking, people management]. For each, challenge my self-assessment by asking what evidence supports it, what contradictory evidence I might be ignoring, and what my direct reports would likely say if guaranteed anonymity. Identify the probable gaps between self-image and reality. + +**Prompt 3 -- Blind Spot Excavation:** +> Based on the following description of my leadership style and recent decisions at [company], identify probable blind spots I am not seeing. Apply the Stoic principle that self-deception is "the most hostile" enemy of knowledge. Look for patterns of avoidance, contradictions between stated and revealed preferences, and areas where my reasoning may be serving my ego rather than the business. Present findings with compassion but without softening. + +**Prompt 4 -- Obligation Inventory:** +> List all my current professional and personal obligations. For each, apply the Stoic freedom audit: Is this genuinely necessary? Is this self-imposed? Am I maintaining this out of habit, guilt, vanity, or fear? What would happen if I stopped? Recommend which obligations to release, renegotiate, or reaffirm, and calculate the time and mental energy recovered. + +--- + +## Use Cases + +**Validation-stage founder receiving contradictory feedback** + +A B2B founder at the validation stage considers himself an excellent listener -- his self-narrative includes "I'm always open to feedback." When three separate pilot customers raise the same usability concern, he unconsciously reframes each as an edge case. Only when his co-founder confronts him with the pattern does he recognise the gap between self-image ("I listen") and behaviour ("I explain away"). A structured Stoic self-assessment reveals that his identity is overly fused with the product design, making any criticism of the product feel like criticism of himself. The evening review practice, adopted daily, begins to surface this pattern in real time rather than retrospectively. + +**Growth-stage CEO discovering a values contradiction** + +A Series A CEO publicly champions a culture of radical transparency. She holds all-hands meetings, publishes company financials internally, and encourages direct feedback. A 360-degree review reveals, however, that her direct reports experience her as defensive when challenged and subtly retaliatory when contradicted. The gap between stated value (transparency) and revealed behaviour (defensiveness) has been invisible to her precisely because she never examined it. The Stoic framework provides the tool: Epictetus's insistence on internal integration means that the CEO must either change the behaviour to match the value or honestly revise the value. Both are acceptable. Living in the gap is not. + +**Scale-stage executive losing touch with ground truth** + +A C-suite executive at a late-stage company has spent three years receiving filtered information from increasingly large layers of management. Seneca's warning about self-imposed slavery manifests here as slavery to a curated version of reality. The executive believes morale is strong because the metrics he sees are selected for optimism. The Stoic "find yourself a Cato" practice provides the intervention: he identifies two people in the organisation -- one junior, one lateral -- who are constitutionally incapable of flattery, and establishes regular, unstructured conversations with them. Within a month, his understanding of the company's actual condition has materially shifted. + +--- + +## Anti-Patterns + +**1. Turning the evening review into self-punishment.** Seneca's practice is diagnostic, not penal. "I forgive you this time" is an essential part of the protocol. Founders prone to perfectionism or imposter syndrome may weaponise self-examination against themselves, which defeats the purpose entirely. The review should leave you clearer, not smaller. + +**2. Substituting self-awareness tools for self-awareness.** Personality assessments (Myers-Briggs, Enneagram, StrengthsFinder) can catalyse self-reflection, but they can also replace it. Knowing your "type" is not the same as knowing yourself. The Stoic practice requires ongoing, unmediated self-confrontation -- not a label applied once and referenced forever. + +**3. Performing vulnerability as a substitute for doing the work.** Contemporary leadership culture celebrates vulnerability, which is admirable. But saying "I'm working on my blind spots" in a team meeting is not the same as actually working on your blind spots. The Stoic practice is private and rigorous. Marcus Aurelius never intended his *Meditations* for publication. The work is for you, not for your audience. + +**4. Examining only failures.** The evening review is equally concerned with strengths. Epictetus's question "How am I better?" demands that you recognise genuine progress. Founders who review only mistakes develop a distorted self-image in the opposite direction -- seeing themselves as perpetually deficient. + +**5. Seeking awareness without seeking change.** Self-knowledge is necessary but not sufficient. Identifying a blind spot and then continuing to act as though it doesn't exist is worse than never having seen it, because now the self-deception is deliberate. Awareness obligates action. + +**6. Confining self-examination to moments of crisis.** The evening review is a daily practice, not an emergency protocol. Founders who examine themselves only after a catastrophe -- a failed round, a co-founder departure, a public embarrassment -- are practising forensic investigation, not self-awareness. The Stoic discipline is prophylactic: it surfaces small misalignments before they compound into large ones. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Examining motivations and founder-idea fit | Honest assessment of why you're pursuing this venture -- passion, escapism, ego, genuine conviction -- shapes everything that follows | +| Validation | Separating identity from hypothesis | The ability to see negative experimental results clearly, without the distortion of ego, is the difference between a pivot and a delusion | +| Early Traction | Recognising emerging leadership patterns | As the team grows from 2 to 20, your leadership habits crystallise; self-examination now prevents dysfunctional patterns from becoming permanent | +| Growth | Auditing the gap between culture rhetoric and culture reality | At this stage, the CEO's unexamined behaviours have become organisational norms; the evening review must extend to institutional self-awareness | +| Scale | Resisting the information cocoon | Power insulates leaders from honest feedback; Stoic self-awareness practices must be deliberately maintained against the structural forces that erode them | + +The idea stage presents the purest test of self-awareness: why are you doing this? Seneca's question "Were my actions just?" becomes "Are my motivations honest?" The founder who starts a company to escape a bad job, to impress a parent, or to prove a point to a former employer is not inherently wrong -- but they will make very different decisions than the founder driven by a genuine problem they want to solve. Self-awareness at the idea stage is about knowing which founder you actually are. + +At early traction, the founder's leadership habits begin to solidify into patterns -- and those patterns, for better or worse, become the template for the company's culture. The evening review serves a dual purpose at this stage: it is both personal self-improvement and organisational design. The founder who notices, through nightly reflection, that she avoids giving critical feedback is catching a cultural defect before it becomes structural. The one who notices that he consistently prioritises product over people is seeing the early architecture of a dysfunction that will be vastly more expensive to repair at fifty employees than at ten. + +At scale, self-awareness becomes an institutional survival skill. The CEO of a five-hundred-person company who does not practise rigorous self-examination will inevitably become surrounded by people who tell them what they want to hear. Every layer of management is a filter; every success reinforces the belief that the current approach is correct. Only the daily discipline of questioning oneself -- Seneca's nightly audit, Marcus's private journaling -- provides a counterweight to the structural forces that make self-deception at scale nearly automatic. The Stoic practice at this stage is less about personal psychology and more about epistemological hygiene: how do I know what I think I know, and what systems have I built to ensure that my self-image stays tethered to reality? + +--- + +## Output Template + +```markdown +# Stoic Self-Awareness Review -- [Period] + +**Date:** [Date] +**Review scope:** [Daily / Weekly / Monthly] + +## Seneca's Evening Review + +### What bad habit did I curb? +[Specific habit and the situation in which you curbed it] + +### How am I better? +[Genuine progress observed -- not flattery, not false modesty] + +### Were my actions just? +[Honest assessment of alignment between principles and behaviour] + +## Self-Image Accuracy Audit + +| Dimension | How I See Myself | Probable Reality (based on evidence) | Gap | +|-----------|-----------------|--------------------------------------|-----| +| [e.g., Communication] | [Self-assessment] | [What behaviour and feedback suggest] | [Size and nature of gap] | + +## Blind Spots Identified +1. [Blind spot] -- Evidence: [What led to this recognition] +2. [Blind spot] -- Evidence: [What led to this recognition] + +## Obligation Inventory + +| Obligation | Genuinely Necessary? | Self-Imposed? | Action | +|-----------|---------------------|---------------|--------| +| [Obligation] | [Yes/No] | [Yes/No] | [Keep / Release / Renegotiate] | + +## Integration Check +- **Stated value vs. revealed behaviour gap:** [Describe any contradiction identified] +- **Corrective action:** [Specific step to close the gap] + +## This Week's Cato +[Name the person whose imagined or actual judgment you will use as a mirror this week] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- Self-awareness reveals which aspects of your situation are genuinely within your control; without it, the dichotomy is applied to a distorted map. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- The evening review frequently surfaces emotional patterns that require the reframing techniques of Stoic emotional practice. +- **[Stoic Unbiased Thought](../../content/skills/stoic/stoic-unbiased-thought.md)** -- Self-deception is the enemy of objective perception; the two practices are mutually reinforcing. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- Structured introspection practices that complement the Stoic philosophical framework; the former provides techniques, the latter provides the underlying worldview. +- **[Johari Window](../../content/skills/frameworks/johari-window.md)** -- A model for understanding blind spots and hidden selves that maps naturally onto the Stoic emphasis on the gap between self-image and reality. +- **[Creative Perception and Awareness](../../content/skills/creative/creative-perception-and-awareness.md)** -- Stoic self-examination operates through rational inquiry while creative awareness operates through perceptual sensitivity; the two are complementary paradigms for deepening self-knowledge. diff --git a/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md b/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md deleted file mode 120000 index 457ebfa..0000000 --- a/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-unbiased-thought.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md b/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md new file mode 100644 index 0000000..5e58cf4 --- /dev/null +++ b/plugins/foreman/skills/stoic-unbiased-thought/SKILL.md @@ -0,0 +1,217 @@ +--- +name: "stoic-unbiased-thought" +description: "Applies the Stoic discipline of objective perception to entrepreneurial thinking, drawing on Marcus Aurelius's practice of describing things in their simplest terms, the 'view from above' technique, and the Stoic method of stripping value judgments from events. Covers cognitive distortions through a Stoic lens, the difference between observation and interpretation, and the practice of seeing things as they are. Use when distorted thinking is driving poor decisions, when hype or panic is clouding judgment, when strong opinions need stress-testing, or when seeking objectivity amid emotionally charged situations." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - stoic + - objectivity + - perception + - cognitive-distortion + - judgment + - view-from-above + - marcus-aurelius + - epictetus + - critical-thinking +related_skills: + - stoic-control-and-clarity + - stoic-emotional-mastery + - stoic-self-awareness + - thinking-fast-and-slow + - black-swans + - vuca-framework + - strategic-thinking-and-alignment +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Unbiased Thought + +Every event is neutral -- what makes it good or bad is the colour of the lens through which you perceive it. Marcus Aurelius, who had more reason than most to see the world as either magnificent or terrible, spent years training himself to do neither. Instead, he practised a form of radical descriptive simplicity: wine is "old grape juice," imperial purple robes are "sheep's wool dyed in shellfish blood," sex is "rubbing and a spasmic discharge." The exercise sounds almost comically reductive, and that is precisely the point. By stripping objects and events of the value judgments we habitually attach to them, the Stoics revealed a startling truth: most of what we believe about the world is not observation but interpretation -- and interpretation, unlike observation, can be trained, corrected, and improved. + +--- + +## The Framework + +### The Perceiving Eye and the Observing Eye + +The Japanese swordsman Miyamoto Musashi distinguished between the "perceiving eye" and the "observing eye." The observing eye sees what is. The perceiving eye sees what things supposedly mean. Marcus Aurelius, writing centuries earlier in a different civilisation, arrived at the same insight: "It isn't events themselves that disturb people, but only their judgments about them." + +This distinction has direct operational consequences for entrepreneurs: + +| Observing Eye | Perceiving Eye | +|---|---| +| Revenue declined 12% this quarter | We're failing | +| A key engineer gave notice | He's betraying us | +| The board asked for a revised forecast | They've lost confidence in me | +| A competitor raised a large round | We're going to be crushed | + +The left column is data. The right column is narrative -- and narrative, once it takes hold, shapes every subsequent decision. The Stoic practice of unbiased thought is the systematic effort to operate from the left column before permitting the right one any influence. + +### Contemptuous Expressions: Radical Simplification + +Marcus Aurelius developed a technique that Stoic scholars call *contemptuous expressions* -- deliberately describing prized or feared things in their most basic, physical terms. This is not cynicism; it is a cognitive counterweight to the mind's tendency to inflate or catastrophise. + +Applied to entrepreneurial contexts, the practice yields clarity: + +- A funding round is "other people agreeing to exchange their money for a percentage of future uncertain value" +- A product launch is "making a thing available and seeing if people want it" +- A keynote speech is "one person talking to many people sitting in chairs" +- An acquisition offer is "someone proposing to buy the output of your work for a specific price" + +None of these reductions are false. They are merely the same events, seen without the distortion of status, fear, desire, or self-importance. And from that vantage point, decision-making improves markedly -- because the decisions are about the thing itself, not about the story wrapped around it. + +### The View from Above + +Marcus Aurelius repeatedly practised what scholars call the "view from above" -- a mental exercise in which you imagine seeing your current situation from an increasingly elevated perspective. First, see the room you're in. Then the building. The city. The country. The Earth, spinning in space. At each level, the matters that consumed you a moment ago diminish in proportion to the vastness you're now perceiving. + +"Watch the stars in their courses," Marcus writes, "and imagine yourself running alongside them. Think constantly on the changes of the elements into each other, for such thoughts wash away the dust of earthly life." + +This is not nihilism. The view from above does not negate the importance of your work. It recalibrates it. The lost deal, the difficult board meeting, the competitive threat -- all remain real and worth addressing. But they are no longer cosmically significant events that justify panic, despair, or the abandonment of principle. They are dust, and dust can be dealt with calmly. + +### Testing Impressions: The Stoic Verification Protocol + +Epictetus provides the most explicit protocol for challenging one's own perceptions: "From the very beginning, make it your practice to say to every harsh impression, 'you are an impression and not at all what you appear to be.' Next, examine and test it." + +The testing process involves three questions: + +**1. Is this impression about something within my control?** If not, the emotional charge attached to it is, by definition, misplaced. + +**2. Is the judgment I've attached to this event the only possible interpretation?** The Stoics recognised that the same event can support radically different narratives. A customer churning can be "evidence of product failure" or "useful data about market fit." An investor passing can be "rejection" or "misalignment that saves both parties time." + +**3. Would a wise person -- my Cato, my impartial spectator -- share this judgment?** If the answer is uncertain, the judgment warrants revision before action. + +### Opinions as Voluntary Additions + +"We have the power to hold no opinion about a thing and to not let it upset our state of mind," Marcus observes, "for things have no natural power to shape our judgments." This is among the most counterintuitive claims in Stoic philosophy. Surely some things are objectively bad? The Stoics would answer: things are objectively inconvenient, painful, or unpleasant. But "bad" is a layer we add -- and we have the power not to add it. + +For entrepreneurs, this practice manifests as the discipline of delayed interpretation. When information arrives -- a metric, an email, a market signal -- the unbiased thinker receives the data and resists the immediate impulse to assign it a value. Is this good news or bad news? Perhaps it is simply news. The interpretive layer can be added later, after analysis, after consultation, after the emotional charge of the moment has dissipated. The Stoics did not claim this was easy. They claimed it was possible, and that the difference between practising it and not practising it was the difference between clarity and confusion. + +### The War Within: Conflicting Judgments + +Seneca warns that "circumstances are what deceive us" because "we embrace evil before good" and "our prayers are at war with our prayers." The entrepreneur who wants sustainable growth but chases vanity metrics, who values work-life balance but never leaves the office, who prizes culture but tolerates toxic high performers -- these are all examples of what Seneca calls internal warfare. The biases are not external. They are contradictions in the entrepreneur's own system of judgments. + +Unbiased thought, in the Stoic sense, begins with recognising that these contradictions exist and tracing them to their source: usually a judgment accepted without examination, an opinion inherited from culture or convention, or a desire masquerading as a principle. + +--- + +## Prompts + +**Prompt 1 -- Contemptuous Expressions Exercise:** +> Take the following list of things I'm currently preoccupied with as founder of [company]: [list concerns]. For each, apply Marcus Aurelius's contemptuous expressions technique -- describe it in the simplest, most physically literal terms possible, stripped of all status, emotion, and narrative. Then assess: does the simplified description change how urgent or important this concern actually is? + +**Prompt 2 -- Judgment Stripping:** +> I've just received this news about my business: [describe event]. Before I react, help me separate observation from interpretation. State the raw facts with zero value judgment. Then list three to five different interpretations of the same facts, ranging from catastrophic to neutral to opportunistic. For each interpretation, identify the assumption that makes it seem plausible. Which interpretation is best supported by the available evidence? + +**Prompt 3 -- View from Above:** +> I'm deeply stressed about [situation] at [company]. Walk me through Marcus Aurelius's "view from above" exercise. Start with the immediate situation, then progressively zoom out -- to the industry, to the economy, to the arc of business history, to the timescale of human civilisation. At each level, reassess the situation's actual significance. Then zoom back in and recommend what a proportionate, clear-headed response would look like. + +**Prompt 4 -- Internal Contradiction Audit:** +> Review my stated values and priorities for [company]: [list values]. Now review my actual recent decisions and time allocation: [list decisions/activities]. Apply Seneca's warning about "prayers at war with prayers" -- where do my stated values and revealed behaviour contradict each other? For each contradiction, identify the unexamined judgment or hidden desire driving the gap. + +--- + +## Use Cases + +**Idea-stage founder catastrophising about competition** + +A first-time founder discovers that two well-funded startups are building in a similar space. Her immediate perception: "The market is already saturated. I'm too late. These companies will crush me." The contemptuous expressions exercise reduces the situation to its fundamentals: "Two other groups of people are also trying to solve this problem. They have raised capital. I have not yet." Stripped of narrative, the situation is informational, not terminal. The judgment-stripping exercise yields five alternative interpretations, including "the existence of competitors validates the market" and "well-funded competitors often pursue different segments." The founder proceeds with better data and less dread. + +**Early-traction startup misreading a vanity metric** + +A consumer marketplace at early traction celebrates a spike in user registrations after a press mention. The perceiving eye sees "we're taking off." The observing eye sees "registrations increased 300% this week; we do not yet know whether these users will transact." The view from above reveals that press-driven spikes are among the most common and most misleading signals in consumer businesses -- a pattern repeated across thousands of startups over decades. The unbiased assessment preserves the team's morale (the spike is a preferred indifferent) while preventing the premature scaling decisions that frequently follow misinterpreted traction signals. + +**Growth-stage CEO receiving an acquisition offer** + +A Series B CEO receives an unsolicited acquisition offer that is "too good to ignore" -- or so it seems. Marcus Aurelius's exercise reduces the offer to its components: "A larger company proposes to pay $X for the business. The price exceeds current revenue by [multiple]. The acquirer's stated intentions are [list]. The transaction would result in [concrete personal and organisational outcomes]." With the glamour stripped away, the CEO can evaluate the offer against actual criteria -- strategic fit, team outcomes, personal goals -- rather than against the narrative of validation and success that acquisition offers inevitably carry. + +--- + +## Anti-Patterns + +**1. Using objectivity as emotional avoidance.** Stripping judgments is a cognitive practice, not an emotional bypass. The founder who describes a team member's departure as "one person choosing to work elsewhere" and then refuses to examine whether the departure reveals a leadership problem is not practising Stoic objectivity -- they are hiding behind it. The practice requires engaging with the stripped-down facts, not dismissing them. + +**2. Descending into nihilism through the view from above.** Marcus's cosmic perspective is a recalibration tool, not an argument that nothing matters. The founder who concludes "none of this matters in the grand scheme of things" and stops trying has misapplied the technique. The correct conclusion is closer to: "This matters, but not as much as my emotional reaction is telling me. I can address it with composure." + +**3. Applying contemptuous expressions to people.** Reducing objects, events, and institutions to their simplest terms is a useful cognitive tool. Reducing human beings to their simplest terms is dehumanising. Marcus Aurelius explicitly counselled compassion and kinship toward others, even difficult ones. The technique is for examining things, not diminishing people. + +**4. Demanding that others adopt your objectivity.** The Stoic practice of unbiased thought is a personal discipline. Telling a distressed colleague that "it's just an impression, not reality" is philosophically accurate and interpersonally disastrous. Apply the framework to your own perceptions. Extend empathy to others who have not yet done the same work. + +**5. Mistaking detachment for wisdom.** The Stoics were not detached. Marcus Aurelius governed an empire. Seneca navigated lethal court politics. Epictetus taught with visible passion. Unbiased thought enables better engagement with reality, not withdrawal from it. The entrepreneur who uses the framework to disengage from problems rather than see them more clearly has inverted its purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Seeing the market as it is, not as you wish it to be | The greatest perceptual risk here is confirmation bias -- interpreting ambiguous signals as validation because you want them to be | +| Validation | Receiving experimental data without distortion | Every data point must pass through the observing eye before the perceiving eye; the discipline of delayed interpretation is most critical here | +| Early Traction | Distinguishing signal from noise in early metrics | The flood of new data (users, revenue, churn, NPS) creates endless opportunities for biased interpretation; the Stoic protocol filters them systematically | +| Growth | Resisting narrative capture by success stories | At growth stage, the company's own story becomes a source of bias; "we always succeed" is as dangerous a judgment as "we're going to fail" | +| Scale | Maintaining institutional objectivity | At scale, organisational biases compound individual ones; unbiased thought must be embedded in decision processes, not just individual practice | + +At the validation stage, the Stoic discipline of unbiased thought intersects most powerfully with the scientific method. Both demand that the practitioner observe before interpreting, test before concluding, and remain willing to be proved wrong. The founder who defines falsification criteria before running an experiment -- "what specific result would cause me to abandon this hypothesis?" -- is practising exactly what Epictetus prescribes: testing impressions before assenting to them. + +At growth and scale, the primary threat to unbiased thought shifts from individual cognitive distortion to organisational narrative capture. Success creates a meta-narrative -- "we're the company that always finds a way" or "our market position is unassailable" -- and that narrative filters all subsequent information. The Stoic view from above provides the institutional corrective: periodically lifting the organisation's perspective above its own story to see the broader competitive, economic, and historical context in which it operates. + +--- + +## Output Template + +```markdown +# Unbiased Thought Assessment -- [Decision/Situation] + +**Date:** [Date] +**Context:** [Brief description of the situation requiring objective analysis] + +## Observation vs. Interpretation + +| Raw Observation (Observing Eye) | Current Interpretation (Perceiving Eye) | Alternative Interpretations | +|--------------------------------|----------------------------------------|----------------------------| +| [Fact 1] | [Current judgment] | [2-3 alternative readings] | +| [Fact 2] | [Current judgment] | [2-3 alternative readings] | + +## Contemptuous Expressions Reduction +- **Situation as commonly described:** [How you/others currently frame it] +- **Situation in simplest physical terms:** [Stripped of narrative, status, emotion] +- **What changes in your assessment:** [Specific shift in perceived urgency/importance] + +## Impression Test (Epictetus Protocol) + +| Impression | Within My Control? | Judgment Attached | Judgment Supported by Evidence? | Verdict | +|-----------|-------------------|-------------------|--------------------------------|---------| +| [Impression 1] | [Y/N] | [What I think it means] | [Y/N -- cite evidence] | [Retain / Revise / Reject] | + +## View from Above +- **Immediate significance:** [How it feels right now] +- **Industry-level significance:** [How common is this pattern?] +- **Historical significance:** [Has this type of situation been resolved before?] +- **Proportionate response:** [What a clear-headed response looks like at the right scale] + +## Internal Contradiction Check +- **Stated value/priority:** [What I say I care about] +- **Revealed behaviour:** [What my actions actually show] +- **Root judgment driving the gap:** [The unexamined belief] +- **Resolution:** [Change the behaviour or revise the value] +``` + +--- + +## Related Skills + +- **[Stoic Control and Clarity](../../content/skills/stoic/stoic-control-and-clarity.md)** -- The dichotomy of control is the first filter in the impression-testing protocol; unbiased thought depends on it as a prerequisite. +- **[Stoic Emotional Mastery](../../content/skills/stoic/stoic-emotional-mastery.md)** -- Emotions distort perception; the emotional mastery practices clear the lens through which unbiased thought operates. +- **[Stoic Self-Awareness](../../content/skills/stoic/stoic-self-awareness.md)** -- Self-deception is the most persistent source of biased perception; self-awareness practices reveal the internal contradictions that distort judgment. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- Kahneman's bias catalogue provides the empirical evidence for what the Stoics intuited: that human perception is systematically unreliable and requires structural correction. +- **[Black Swans](../../content/skills/frameworks/black-swans.md)** -- Taleb's work on narrative fallacy and the limits of prediction shares the Stoic suspicion of our tendency to see patterns where none exist. +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- The Clear Thinking framework's four biological defaults (ego, emotion, inertia, social) are the modern behavioural catalogue of the distortions the Stoics addressed through the impression-testing protocol. diff --git a/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md b/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md deleted file mode 120000 index 93eb444..0000000 --- a/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/stoic/stoic-virtue-and-kindness.md \ No newline at end of file diff --git a/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md b/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md new file mode 100644 index 0000000..67fd3b3 --- /dev/null +++ b/plugins/foreman/skills/stoic-virtue-and-kindness/SKILL.md @@ -0,0 +1,204 @@ +--- +name: "stoic-virtue-and-kindness" +description: "Presents the Stoic argument that character is the ultimate competitive advantage and that virtue -- encompassing honesty, kindness, justice, and moral courage -- is not a means to success but constitutes success itself. Use when an entrepreneur faces ethical dilemmas, when competitive pressure tempts shortcuts, when building company culture around values rather than metrics, when kindness is dismissed as weakness in a high-stakes environment, or when seeking philosophical grounding for why doing right and doing well are the same endeavour." +version: "1.0.0" +category: "stoic" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - virtue + - kindness + - character + - ethics + - moral-courage + - honesty + - forgiveness + - integrity + - stoic + - values +related_skills: + - stoic-fortitude-and-resilience + - stoic-acceptance-amor-fati + - trust-equation + - psychological-safety + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Stoic Virtue and Kindness + +CHARACTER TAX. There is a cost to being virtuous, and the Stoics never pretended otherwise. Virtue is not free. It demands a daily tax paid in effort, restraint, and the willingness to forgo easier paths. Seneca gave up a fortune trying to extract himself from Nero's court. Marcus Aurelius spent his final years on cold military frontiers when he could have remained in Roman luxury. Epictetus endured slavery and a crippled leg without surrendering his philosophical commitments. The return on this tax is not wealth or status -- it is character. And the Stoic claim, radical in their time and radical still, is that character is not a *means* to happiness. Character *is* happiness. Everything else the entrepreneur chases -- revenue, traction, market share -- is at best a lagging indicator of something more fundamental. + +> "Does the light of a lamp shine and keep its glow until its fuel is spent? Why shouldn't your truth, justice, and self-control shine until you are extinguished?" -- Marcus Aurelius, *Meditations* + +--- + +## The Framework + +The Stoic treatment of virtue is not a soft appeal to "being nice." It is an architectural argument: that the qualities of character -- justice, kindness, honesty, courage, self-control -- form the load-bearing structure on which every other entrepreneurial achievement depends. Remove them, and the edifice collapses, regardless of how impressive it looks from outside. + +### The Four Cardinal Virtues in Entrepreneurial Context + +The Stoics organised virtue into four categories, each mapping to a distinct entrepreneurial discipline. + +**Wisdom (Sophia)** -- The capacity to distinguish what is within one's control from what is not, and to allocate attention accordingly. In business terms: strategic clarity. The wise entrepreneur does not waste resources fighting uncontrollable market forces; they position the company to benefit from them. + +**Justice (Dikaiosyne)** -- Right action toward others. For the Stoic, this was not legalistic compliance but a genuine orientation toward the common good. Marcus Aurelius compressed it into a single maxim: "That which isn't good for the hive, isn't good for the bee." The entrepreneur who extracts value from employees, customers, or partners while contributing nothing in return violates this principle -- and the violation, the Stoics would argue, harms the entrepreneur more than anyone else. + +**Courage (Andreia)** -- Not physical bravery but moral courage: the willingness to do what is right despite personal cost. Courage is the virtue that makes the other three operational. Without it, wisdom remains theoretical, justice remains aspirational, and self-control collapses under pressure. + +**Temperance (Sophrosyne)** -- Self-control, moderation, and the discipline to resist excess. For the entrepreneur surrounded by venture capital, growth metrics, and the intoxicating narrative of "disruption," temperance is the corrective that prevents ambition from becoming recklessness. + +### Kindness as Strength + +The business world frequently treats kindness as a liability -- a quality tolerated in HR departments but inappropriate for strategy rooms. The Stoics held the opposite view. + +> "A benefit should be kept like a buried treasure, only to be dug up in necessity. Wherever there is a human being, we have an opportunity for kindness." -- Seneca, *On the Happy Life* + +Kindness, in Stoic thought, is not sentimentality. It is the practical expression of the recognition that human beings are mutually interdependent. Marcus Aurelius repeated this theme relentlessly: "We are like many pellets of incense falling on the same altar." The entrepreneur who grasps this -- who treats employees, customers, and even competitors as interconnected participants in a shared system -- builds structural advantages that purely transactional operators cannot replicate. Trust compounds. Goodwill compounds. Reputation compounds. Ruthlessness does not. + +### Honesty as Default Setting + +> "The straightforward and good person should be like a smelly goat -- you know when they are in the room with you." -- Marcus Aurelius, *Meditations* + +Marcus's analogy is deliberately unglamorous. Honesty should not require announcement. The entrepreneur who prefaces statements with "I'll be honest with you" invites the question: what were you being before? Stoic honesty is not radical candour performed for effect. It is a default orientation -- so habitual that it requires no signalling. + +### The Self-Inflicted Wound of Wrongdoing + +> "The person who does wrong, does wrong to themselves. The unjust person is unjust to themselves -- making themselves evil." -- Marcus Aurelius, *Meditations* + +The Stoic case against unethical behaviour is not primarily about consequences or reputation. It is about what wrongdoing does to the person who commits it. Every shortcut, every lie, every act of exploitation erodes the internal architecture of character. The entrepreneur who cheats a supplier does not merely risk a damaged relationship; they damage themselves. Seneca noted the grim irony: "Crimes often return to their teacher." The methods you model will eventually be used against you. + +### Character as Fate + +> "Each person acquires their own character, but their official roles are designated by chance." -- Seneca, *Moral Letters* + +Heraclitus's maxim -- "Character is fate" -- underpins the entire Stoic position on hiring, partnerships, and professional relationships. Past credentials measure fortune; character measures the person. The startup that hires on pedigree alone imports the luck of others' circumstances. The startup that hires on character imports a self-reinforcing capacity for sound judgement under pressure. Seneca advised inviting some to one's table "because they are deserving, others because they may come to deserve it." The implication is clear: character can be developed, but only if it is valued. + +### The Revenge Trap + +> "The best way to avenge yourself is to not be like that." -- Marcus Aurelius, *Meditations* + +Venture-backed competition practically begs for retaliation: a competitor copies your feature, a former employee poaches clients, a partner reneges on a deal. The instinct to hit back is powerful -- and, the Stoics argued, self-destructive. Vengeance consumes time, distorts priorities, and models exactly the behaviour it condemns. Marcus and Seneca both counselled the same response: let the wrongdoer's actions define the wrongdoer, and let your response define you. The energy spent on revenge is energy stolen from building. + +--- + +## Prompts + +**Prompt 1 -- Character Audit:** +> Assess the character infrastructure of my company. My company is [describe: stage, team size, industry]. For each of the four Stoic cardinal virtues (Wisdom, Justice, Courage, Temperance), evaluate: Where does our organisation practise this virtue well? Where do we fall short? What specific decisions or policies reveal our actual values (as opposed to our stated ones)? Identify the three highest-priority character gaps and propose concrete actions to address each. + +**Prompt 2 -- Ethical Dilemma Analysis:** +> I am facing an ethical dilemma: [describe situation -- e.g., a profitable client whose values conflict with ours, a competitive shortcut that is legal but questionable, pressure to misrepresent metrics to investors]. Apply the Stoic virtue framework: What would wisdom (clear-eyed assessment of what we control) say? What would justice (right action toward all affected parties) say? What would courage (willingness to bear personal cost) say? What would temperance (moderation and long-term thinking) say? What is the decision that I could defend to Marcus Aurelius? + +**Prompt 3 -- Kindness as Strategy:** +> Help me design a stakeholder kindness strategy for my company at [stage]. For each stakeholder group (employees, customers, suppliers, investors, community), identify: What does genuine kindness look like in our specific interactions with them? Where are we currently transactional when we could be generous? What structural changes would embed kindness into our processes rather than relying on individual goodwill? Frame each recommendation in terms of the long-term trust and reputational capital it builds. + +**Prompt 4 -- Revenge and Forgiveness Decision Tree:** +> A competitor / partner / employee has wronged us: [describe situation]. My instinct is to [describe desired response -- e.g., retaliate, cut them off, expose them publicly]. Apply Marcus Aurelius's principle: "The best way to avenge yourself is to not be like that." Walk me through: (1) What does retaliation actually cost us in time, energy, and reputation? (2) What does the wrongdoer's behaviour say about them versus about us? (3) What response would strengthen our character rather than merely punish theirs? (4) Is there a path that serves justice without descending into vengeance? + +--- + +## Use Cases + +**Early-Traction Fintech Founder Facing a Profitable but Ethically Dubious Partnership** + +A fintech startup receives a partnership offer from a payday lender that would generate significant revenue and solve the company's near-term cash-flow pressure. The partnership is legal. Many competitors have similar arrangements. But the founder knows that payday lending practices harm the underbanked population that her company was founded to serve. Applying the Stoic virtue framework, she maps the decision across all four virtues: Wisdom reveals that the partnership creates long-term brand risk that outweighs short-term revenue. Justice identifies the conflict between profiting from the same population the company claims to protect. Courage acknowledges the real financial cost of declining. Temperance counsels against letting short-term pressure override the company's founding purpose. She declines the partnership -- and uses the decision, shared transparently with her team, to reinforce the values that will guide future trade-offs. + +**Growth-Stage CEO Managing Retaliation Impulse After Employee Defection** + +A senior engineer leaves a growth-stage startup to join a direct competitor, taking proprietary knowledge of the company's technical architecture. The CEO's instinct is to pursue legal action aggressively and to make an example. Marcus Aurelius's counsel applies: "How much better to heal than seek revenge from injury. Vengeance wastes a lot of time and exposes you to many more injuries than the first that sparked it." The CEO consults counsel, secures necessary protections through appropriate legal channels, but refuses to engage in a public campaign against the former employee. The restraint preserves the company's reputation among engineering talent -- a community that talks -- and avoids the distraction that litigation inevitably produces. The best revenge is building a company the engineer regrets leaving. + +**Scale-Stage Founder Discovering Internal Fraud** + +A founder at scale discovers that a trusted VP has been inflating performance metrics to secure bonus payouts. The temptation is to handle the situation quietly to avoid board scrutiny and public embarrassment. The Stoic framework demands the opposite: honesty as default, justice toward all affected parties (including the team whose real performance was obscured), and the courage to accept the board's reaction. The founder terminates the VP, reports the situation transparently to the board, and implements controls that should have existed earlier. The short-term cost is real. The long-term signal -- that the company's values are not decorative -- is worth more. + +--- + +## Anti-Patterns + +1. **Treating virtue as a marketing strategy.** The moment kindness, honesty, or ethical behaviour is performed for brand positioning, it ceases to be virtue and becomes tactics. The Stoics were explicit: virtue is its own reward. The entrepreneur who is kind because it generates good press will abandon kindness the moment the press turns negative. + +2. **Confusing kindness with conflict avoidance.** Kindness does not mean agreeing with everyone, avoiding difficult conversations, or tolerating poor performance. Marcus Aurelius was both kind and exacting. Giving honest feedback, making hard personnel decisions, and holding high standards are all compatible with genuine kindness -- provided they are motivated by concern for the person and the organisation rather than by ego or frustration. + +3. **Selective virtue.** Being honest with investors but dishonest with employees. Being generous with customers but exploitative with suppliers. Virtue, in Stoic thought, is indivisible. Selective application is not virtue; it is calculation. + +4. **Virtue signalling without structural commitment.** Publishing a values statement on the website while maintaining incentive structures that reward the opposite behaviour. The Stoic test is not what you say but what you do -- and specifically, what you do when virtue is expensive. + +5. **Using philosophy to judge others rather than govern oneself.** Seneca warned: "When philosophy is wielded with arrogance and stubbornly, it is the cause for the ruin of many." The Stoic entrepreneur applies the virtue framework to their own decisions, not as a standard for evaluating everyone else's behaviour. Self-governance first; everything else follows. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Establishing founding values as structural commitments | Values set at the idea stage become the DNA of the company. The Stoic insight: choose them based on what kind of person (and company) you want to be, not on what sounds good in a pitch deck. Write them as commitments, not aspirations. | +| Validation | Practising honesty under pressure | Validation tempts founders to present favourable interpretations of ambiguous data. The Stoic discipline of honesty -- with investors, advisors, and oneself -- ensures that validation is genuine rather than performed. | +| Early Traction | Building trust as a compounding asset | Every customer interaction, employee conversation, and partner negotiation is a deposit into or withdrawal from the trust account. At early traction, each deposit matters disproportionately. Kindness and reliability now compound into reputation later. | +| Growth | Maintaining virtue through scaling pressure | Growth introduces new ethical pressures: competitive urgency, investor expectations, the temptation to cut corners in quality or culture. The Stoic framework provides the decision-making scaffold that prevents growth from corrupting the company's character. | +| Scale | Institutionalising virtue beyond the founder | At scale, virtue cannot depend on the founder's personal character alone. It must be embedded in governance structures, incentive systems, hiring criteria, and decision-making processes. The question shifts from "Am I virtuous?" to "Is the organisation virtuous even when I am not in the room?" | + +--- + +## Output Template + +```markdown +# Character and Virtue Assessment + +**Company:** [Name] +**Stage:** [Stage] +**Prepared by:** [Name] +**Date:** [Date] + +## Cardinal Virtue Scorecard + +| Virtue | Current Practice | Gap Identified | Priority Action | +|--------|-----------------|----------------|-----------------| +| Wisdom | [How we demonstrate strategic clarity] | [Where we lack it] | [Specific action] | +| Justice | [How we treat stakeholders fairly] | [Where we fall short] | [Specific action] | +| Courage | [Where we act despite personal cost] | [Where we avoid hard choices] | [Specific action] | +| Temperance | [Where we exercise restraint] | [Where we overreach] | [Specific action] | + +## Stated vs. Revealed Values + +| Stated Value | Evidence Supporting | Evidence Contradicting | Alignment Score | +|-------------|--------------------|-----------------------|-----------------| +| [Value 1] | [Example] | [Example] | [High/Medium/Low] | +| [Value 2] | [Example] | [Example] | [High/Medium/Low] | + +## Kindness Audit + +| Stakeholder | Current Interaction Quality | Opportunity for Genuine Kindness | Expected Long-Term Return | +|------------|---------------------------|--------------------------------|--------------------------| +| Employees | [Assessment] | [Specific opportunity] | [Trust, retention, culture] | +| Customers | [Assessment] | [Specific opportunity] | [Loyalty, referrals, brand] | +| Suppliers | [Assessment] | [Specific opportunity] | [Reliability, terms, priority] | + +## Ethical Decision Pending +- **Dilemma:** [Description] +- **Wisdom says:** [Assessment] +- **Justice says:** [Assessment] +- **Courage says:** [Assessment] +- **Temperance says:** [Assessment] +- **Decision:** [Chosen course of action and rationale] +``` + +--- + +## Related Skills + +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- Fortitude provides the endurance to sustain virtue when it becomes expensive; character without strength collapses under pressure, strength without character becomes mere aggression. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Virtue, in Stoic terms, is the character that makes each trust component genuine rather than performed; the trust equation quantifies what virtue produces. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Environments where people feel safe to be honest and take risks outperform those governed by fear; virtue creates the conditions for psychological safety. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's framework maps closely to the Stoic cardinal virtues: self-awareness parallels wisdom, empathy parallels justice, self-regulation parallels temperance. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- Acceptance of fate is the soil from which virtue grows; the entrepreneur consumed by resentment cannot practise justice, wisdom, or kindness. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- The Platinum Rule and validation techniques operationalise the Stoic virtue of kindness in daily interpersonal interactions beyond philosophical aspiration. diff --git a/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md b/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md deleted file mode 120000 index 4ab3656..0000000 --- a/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/story-beginnings-and-endings.md \ No newline at end of file diff --git a/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md b/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md new file mode 100644 index 0000000..8a47033 --- /dev/null +++ b/plugins/foreman/skills/story-beginnings-and-endings/SKILL.md @@ -0,0 +1,230 @@ +--- +name: "story-beginnings-and-endings" +description: "Teaches the opposite-of-the-end rule for finding a story's beginning, the discipline of starting as close to the end as possible, the use of forward movement in opening lines, and the art of frayed endings that resonate without neatly resolving. Use when a pitch or talk starts in the wrong place, when an audience loses interest in the first thirty seconds, when a story's conclusion feels forced or anticlimactic, or when refining any narrative for maximum structural impact." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative-structure + - beginnings + - endings + - pitch-craft + - opening-lines + - presentation + - arc + - forward-movement + - opposite-of-the-end +related_skills: + - what-is-a-story + - finding-your-stories + - story-structure-and-arc + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Story Beginnings and Endings + +BACKWARDS -- Good stories are built backwards from the ending. Most storytellers do not know this, which is why they start in the wrong place. + +More than half the crafting time should go to a single decision: where to begin. Not on the climax. Not on the emotional payload. Not on the jokes or the vivid details. On the first sentence. This allocation of effort is counterintuitive and, according to the framework, the single most consequential craft decision a storyteller makes. The ending -- the five-second moment of transformation -- is given. It happened. The storyteller knows what changed. The beginning, by contrast, must be chosen from an ocean of possibilities, and most storytellers choose poorly. + +The error is almost always the same: starting too early. The founder who opens a pitch with her childhood. The CEO who begins a company narrative with the founding date. The speaker who spends three minutes establishing context before arriving at anything that matters. They start too early because they confuse chronology with story. A story is not a timeline. A story is an arc from one state of being to its opposite, and the beginning must be selected to create that arc -- not to provide a comprehensive history. + +Endings suffer from the inverse problem. Where beginnings err by starting too early, endings err by going too late -- wrapping up, explaining, moralising, restating the point. The best endings, the framework argues, do not land neatly. They fray. They connect back to the beginning with transformed meaning, leaving the audience to feel the resonance rather than having it explained to them. + +--- + +## The Framework + +### Finding the Beginning: The Opposite-of-the-End Rule + +The process starts at the end. The five-second moment of transformation is the story's destination. Once it is identified, the beginning reveals itself through a single question: **What is the opposite of my ending?** + +The logic is structural. A story must demonstrate change. Change requires two states: the state before and the state after. The ending is the "after." The beginning must be the "before" -- and for maximum arc, the "before" should be as far from the "after" as the truth permits. + +The framework formalises this as a series of templates: + +- I was once hopeful, **but now** I am not. +- I was once lost, **but now** I am found. +- I was once certain, **but now** I doubt. +- I was once afraid, **but now** I am fearless. +- I once believed this, **but now** I believe the opposite. + +The beginning of the story is the left side of these statements. The ending is the right. Everything in between is the arc that carries the audience from one to the other. + +**Applied to "Charity Thief":** The story ends with the realisation that the protagonist knows nothing about loneliness. The opposite of knowing nothing about loneliness is the belief that you understand it intimately. The story therefore begins in a gas station, with the protagonist convinced he is the loneliest person alive. Beginning and ending are mirror images. The arc between them is the story. + +**Applied to Jurassic Park:** Grant despises children at the beginning. He loves them at the end. If you watch the first fifteen minutes and ask "What is the opposite of this?", you know the ending. Spielberg is not hiding the destination. He is making the journey compelling enough that the audience forgets they already know where it leads. + +**Applied to a founder's pitch:** If the story ends with the realisation that the company had been solving the wrong problem, the beginning must show the founder utterly convinced they were solving the right one. If the story ends with unexpected traction from an overlooked segment, the beginning must show the founder focused entirely on a different segment. + +The opposite-of-the-end rule does not merely structure the narrative. It creates the satisfaction that audiences feel when a story "works." The greater the distance between beginning and ending states, the more profound the arc, and the more the audience feels that they have travelled somewhere meaningful. + +### Starting as Close to the End as Possible + +The opposite-of-the-end rule tells you what your beginning should feel like. A second principle tells you where to place it in time: **as close to the ending as possible.** + +This is Kurt Vonnegut's rule for short fiction, adopted here for oral storytelling. The reason is compression. Shorter stories are tighter, sharper, and easier for audiences to hold in their minds. Every additional minute of setup is a minute in which the audience's attention can wander, and in oral storytelling -- unlike written prose -- the audience cannot pause, re-read, or look up context. The river of words flows continuously. Fall behind, and the water is gone. + +The revision process for a story set in Boca Raton demonstrates this. The first draft began in a Connecticut airport. Revision moved the beginning onto the plane. Then into the sky. Then to the Boca Raton airport. Then to the rental-car counter. Through five revisions, the beginning migrated twelve hundred miles in distance and five hours in time. Two airport terminals and an airplane were eliminated entirely. The story now takes place in one location: the building where cars are rented. + +**The practical test:** For every element of backstory or setup, ask: "Does the audience need this to understand the five-second moment?" If the answer is no, cut it. If the answer is "they'd appreciate the context," that is also a no. The audience needs only what serves the moment. Context that does not serve the moment is the storyteller indulging themselves at the audience's expense. + +For entrepreneurs, this discipline is liberating. The instinct is to start a company story at the founding -- or worse, at the personal backstory that led to the founding. The opposite-of-the-end rule identifies the emotional starting point; the closeness principle identifies the temporal one. Often the best beginning for a pitch story happened last month, not five years ago. + +### Opening with Forward Movement + +Once the starting point is chosen, the first words matter. The framework advocates opening with physical movement: + +> "I'm driving down a lonely stretch of New Hampshire highway..." +> "I'm walking out of a record store on a December day..." + +The protagonist is already in motion. The audience is already being carried somewhere. There is no throat-clearing, no context-setting, no "Let me tell you about..." -- just a person moving through space toward something the audience does not yet know about. + +Filmmakers understand this instinctively. Star Wars opens with starships racing through space. Raiders of the Lost Ark opens with Indiana Jones marching through a jungle. Vertigo opens with a man climbing a ladder. The audience is immersed before they have time to decide whether they are interested. + +**Three things to avoid in opening lines:** + +1. **Thesis statements.** "This is a story about resilience" robs the narrative of surprise and teaches the audience nothing. It is the storytelling equivalent of explaining a joke before telling it. + +2. **Expectation-setting.** "You're not going to believe this" or "This is hilarious" establishes a bar the story may not clear and primes the audience for a specific reaction, eliminating the possibility of genuine surprise. + +3. **Backstory.** Beginning with history ("When I was seven years old...") instead of movement ("I'm standing in a hospital corridor...") forces the audience to wait for the story to start. The story should already be in progress when the audience arrives. + +### Finding the Frayed Ending + +Endings are where meaning lives, and the temptation is to make that meaning explicit. The framework resists this. The best endings do not conclude; they resonate. They do not explain the transformation; they let the audience feel it. + +The process of finding an ending is often a process of finding meaning itself. Storytellers encounter moments from their lives that they know are significant but cannot articulate why. The solution: tell the story aloud, unpolished, ignoring all craft, spilling every detail. Through the act of telling, the meaning surfaces. The five-second moment clarifies. + +The band-camp story ("Eddie in a Bathtub") sat on the list for twenty years as a moment that mattered but could not be explained. When a workshop class selected it randomly, the whole messy version was told aloud and -- in the telling -- the beating revealed two separate meanings. Each meaning demanded a different story with a different beginning. The ending was the same event; the stories were not. + +**The frayed-ending principle:** Stories need not tie up neatly. An ending that connects back to the beginning with shifted meaning -- the same image or phrase, now carrying different weight -- is more powerful than an ending that summarises the lesson learned. + +A story about a father's letters illustrates this. The storyteller keeps one letter from his father perpetually unopened. Through self-interrogation, he discovers why: as long as an unread letter exists, his father can never truly leave him again. The story does not end with a resolution of the father-son relationship. It ends with the letter still sealed. The audience understands something the teller has only just understood himself. Nothing is resolved. Everything is felt. + +**For entrepreneurs,** this means resisting the instinct to close a pitch story with a neat moral ("And that's why we built X"). Instead, the ending should land on the moment of transformation and let the audience draw the connection. The ask, the product, the market opportunity -- these can follow the story. They should not be the story's conclusion. A story that ends with a call to action is a sales pitch that borrowed narrative clothing. A story that ends on a moment of genuine change and then transitions to a business discussion is a story that earns the audience's attention for whatever comes next. + +--- + +## Prompts + +**Prompt 1 -- Beginning Finder:** +> My story's five-second moment is: [describe the transformation]. Using the opposite-of-the-end rule, identify what my beginning state should be. Then suggest three possible opening scenes from my life or experience that establish that opposite state, ranked by (a) how close they are to the ending in time, (b) how effectively they establish the opposite, and (c) whether they open with forward movement. + +**Prompt 2 -- Closeness Audit:** +> Here is my current story: [paste story]. My five-second moment occurs at [identify it]. Analyse the beginning: how far in time and space is it from the ending? Identify every element of setup and backstory. For each, determine whether the audience genuinely needs it to understand the five-second moment. Suggest a revised beginning that starts as close to the end as possible while still establishing the opposite state. + +**Prompt 3 -- Opening Line Workshop:** +> I need to open a [pitch / keynote / team talk] with a story. The five-second moment is: [describe it]. The opposite starting state is: [describe it]. Write five possible opening sentences that (a) place the protagonist in physical motion, (b) contain no thesis statement or expectation-setting, (c) immerse the audience in a specific time and place, and (d) feel natural enough to pass the Dinner Test. For each, note which element of the opposite state it establishes. + +**Prompt 4 -- Ending Refinement:** +> Here is how my story currently ends: [paste ending]. Does it explain the transformation or let the audience feel it? If it explains, rewrite it as a frayed ending -- one that connects back to the beginning with shifted meaning but does not summarise or moralise. If it already resonates, suggest one small adjustment that could strengthen the callback to the opening. + +--- + +## Use Cases + +**Idea-stage founder revising a demo-day pitch** + +A founder's two-minute demo-day pitch begins with "Three years ago, I was working at a large hospital system and noticed that..." The audience has heard fifty pitches that begin with some variation of "X years ago, I was working at..." Applying the closeness principle, the founder moves the beginning from three years ago to last Tuesday: "I'm sitting across from a patient who has just been told she has six months to receive a treatment that should have started six months ago." The story now opens with forward movement, a specific scene, and an immediate emotional stake. The founding backstory -- previously the first ninety seconds -- is compressed to a single sentence of context. The five-second moment (the founder's realisation that the system is designed to delay, not deliver) now arrives sixty seconds in instead of ninety, and the remaining time is available for the ask. + +**Early-traction startup rewriting its company narrative for the website** + +The "Our Story" page is a chronological timeline: founded in 2022, launched MVP in 2023, first customer in 2023, Series A in 2024. Applying the opposite-of-the-end rule, the team identifies the company's five-second moment: the morning the first customer used the product in a way the team never intended, revealing a market ten times larger than the one they had targeted. The beginning is rewritten as the opposite: the team's absolute certainty about who their customer was and what the product was for. The "Our Story" page now reads as an arc of transformation rather than a sequence of dates. The timeline still appears -- in a sidebar, as supporting evidence -- but the narrative carries the page. + +**Growth-stage leader fixing a keynote that loses the audience in the first two minutes** + +A CTO's conference talk opens with three minutes of personal history and company background before arriving at the technical insight that is the talk's purpose. Audience attention data shows engagement drops at minute two and never fully recovers. Applying the forward-movement principle, the CTO rewrites the opening: "Last Thursday at 2:14 AM, our monitoring system woke me up with an alert that should have been impossible." The audience is in motion from the first sentence. The personal history that previously consumed three minutes is reduced to a single clause: "I've spent fifteen years building systems that are supposed to prevent exactly this." The technical insight -- the five-second moment -- now arrives at minute four instead of minute eight, and the audience is present for it. + +--- + +## Anti-Patterns + +**1. The autobiography opening.** "I grew up in a small town in Ohio..." or "When I was seven years old..." unless the childhood scene is the direct opposite of the ending and cannot be established any other way. Ninety percent of the time, the story can begin years or decades later without losing anything essential. + +**2. The throat-clearing preamble.** Any variation of "Before I begin, let me give you some context" or "To understand this story, you need to know that..." is a signal that the beginning has not been found. If the audience needs context that cannot be delivered inside the story itself, the story's structure needs revision, not a preface. + +**3. The neat bow.** Endings that summarise the lesson ("And that's when I learned that...") or state the moral explicitly ("The takeaway here is...") treat the audience as incapable of feeling the transformation they just witnessed. The storyteller's job is to deliver the moment, not interpret it. Let the audience do the interpreting. + +**4. The runaway ending.** Continuing to talk after the five-second moment has landed. The story is over. Additional scenes, reflections, or "what happened next" segments dilute the emotional impact. The principle is explicit: the five-second moment should come as close to the last words as possible. + +**5. Choosing the first beginning that comes to mind.** The framework warns that the first idea is rarely the best. It is the most convenient, the easiest to remember, and the one the teller personally likes most. The right beginning requires deliberation -- listing multiple options and evaluating each for proximity to the end, effectiveness in establishing the opposite state, and potential for forward movement. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Crafting a single, tight origin-story arc with the closest possible beginning | The entire pitch may be two minutes; every second of setup is a second stolen from the transformation | +| Validation | Beginning with customer-discovery moments rather than founding backstory | The "opposite state" is often the team's initial assumption, now overturned by evidence | +| Early Traction | Refining pivot narratives: old direction as beginning, new direction as ending | The closeness principle prevents the narrative from becoming a comprehensive history of every wrong turn | +| Growth | Teaching multiple team members to find beginnings for their own stories | Sales, product, and engineering each need domain-specific openings that establish their own opposite states | +| Scale | Building institutional narratives with layered beginnings and frayed endings | The company's arc spans years; the craft is selecting the right entry point from an abundance of material | + +At the idea stage, the founder's pitch story must begin and end within a span the audience can hold -- ideally under three minutes. The closeness principle is not a suggestion at this stage; it is a survival requirement. Every sentence of backstory that does not serve the five-second moment is a sentence in which an investor's attention migrates to their phone. + +At scale, the challenge inverts. The company has so much material that the difficulty is not finding a beginning but choosing one. The opposite-of-the-end rule becomes a filtering mechanism: of the hundred possible starting points, which one creates the most powerful arc with the current five-second moment? The answer changes depending on the audience, the context, and the transformation being communicated. + +--- + +## Output Template + +```markdown +# Story Beginning and Ending Worksheet -- [Story Title or Context] + +**Teller:** [Name] +**Audience:** [Investors / Team / Conference / Board] +**Date:** [Date] + +## 1. The Ending (Five-Second Moment) +**What changed:** [Describe the transformation in one sentence] +**Ending state:** [What the protagonist now believes, feels, or understands] + +## 2. The Beginning (Opposite of the End) +**Beginning state:** [The opposite of the ending state] +**Candidate openings:** +| Option | Scene description | Distance from ending | Establishes opposite? | Forward movement? | +|--------|------------------|---------------------|----------------------|-------------------| +| A | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | +| B | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | +| C | [Scene] | [Time/space distance] | [Yes/No -- how] | [Yes/No] | + +**Selected opening:** [Option letter and rationale] + +## 3. Opening Line Draft +[First two sentences -- forward movement, no preamble, specific time and place] + +## 4. Closeness Check +**Elements between beginning and five-second moment:** +| Element | Necessary for the audience to understand the moment? | Keep / Cut | +|---------|-----------------------------------------------------|-----------| +| [Element] | [Assessment] | [Decision] | + +## 5. Ending Draft +**Does the ending explain or resonate?** [Explain / Resonate] +**Callback to beginning:** [How the ending echoes the opening with transformed meaning] +**Final line draft:** [The last sentence the audience hears] +``` + +--- + +## Related Skills + +- **[What Is a Story](../../content/skills/storytelling/what-is-a-story.md)** -- The transformation requirement that defines a story also defines the relationship between beginning and ending; this foundational skill should be understood first. +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- Homework for Life generates the raw moments from which beginnings and endings are selected; the discovery practice feeds directly into the structural decisions taught here. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- The five-second moment and But-and-Therefore principles provide the middle of the story; this skill provides the bookends. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- The mandate-for-change function is structurally an opposite-of-the-end setup: here is where we are, here is where we must go, here is why. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- The ending is where emotional impact detonates; the surprise and humour techniques determine whether the landing produces feeling or merely concludes. +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- Change narratives require the same arc discipline: begin in the current state, end in the desired state, and make the distance between them felt. diff --git a/plugins/foreman/skills/story-performance-and-delivery/SKILL.md b/plugins/foreman/skills/story-performance-and-delivery/SKILL.md deleted file mode 120000 index ecc8646..0000000 --- a/plugins/foreman/skills/story-performance-and-delivery/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/story-performance-and-delivery.md \ No newline at end of file diff --git a/plugins/foreman/skills/story-performance-and-delivery/SKILL.md b/plugins/foreman/skills/story-performance-and-delivery/SKILL.md new file mode 100644 index 0000000..564daf2 --- /dev/null +++ b/plugins/foreman/skills/story-performance-and-delivery/SKILL.md @@ -0,0 +1,236 @@ +--- +name: "story-performance-and-delivery" +description: "Covers the practical mechanics of performing a story: present tense as default, tense shifting, the two strategies for telling success stories without sounding like a braggart, scene-based memorisation, eye contact, microphone technique, emotional control, word selection, and adapting delivery across contexts from stages to boardrooms. Use when preparing to deliver a story live, when rehearsing a pitch or keynote, or when a narrative reads well on paper but falls flat in the room." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - performance + - delivery + - present-tense + - hero-story + - public-speaking + - pitching + - rehearsal + - pacing + - eye-contact + - vulnerability + - word-choice +related_skills: + - building-story-stakes + - storytelling-truth-and-vividness + - emotional-impact-in-stories + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Story Performance and Delivery + +The best storytellers do not perform on stages -- they perform at dinner tables, in meeting rooms, and in elevator pitches. The principles are identical. The record holder for Moth StorySLAM victories insists that the gap between a great written story and a great told story is bridged by a handful of concrete, trainable techniques: the strategic use of present tense, scene-based memorisation instead of word-for-word recitation, deliberate word selection, controlled vulnerability, and the discipline to keep talking no matter what. None of these require natural charisma. All of them require practice and intention. + +--- + +## The Framework + +### Present Tense as the Default + +The present tense creates immediacy. It functions as a temporal magnet, pulling the audience out of whatever room they occupy and into whatever room the story occupies. "I'm standing in the parking lot" places the listener in that parking lot more forcefully than "I stood in the parking lot." The past tense describes. The present tense transports. + +The technique is demonstrated by writing an entire chapter in real time, on an Amtrak train, while his five-year-old son refuses to use the restroom. The reader is on the train. The reader feels the rocking. The reader worries about the boy's bladder. That is the present tense at work. + +**When to shift to past tense:** + +- **Backstory.** When slipping into events that precede the main narrative, the past tense signals temporal distance. A story cannot have two present-tense timelines without diluting both. The backstory is in the past; present it as such. +- **Moments best told from a distance.** Not every scene benefits from the audience being pulled inside it. Some moments -- particularly those involving discomfort, vulnerability, or physical specifics -- are more effective with a layer of temporal remove. +- **Returning to present tense after backstory** functions as a reset. It pulls the audience back into the primary timeline. The effect is like pressing a button on an arcade racing game: shifting the camera from an overhead view back to the driver's seat. + +**Tense shifts should be instinctual, not mechanical.** In live storytelling, speakers shift tenses constantly -- often mid-sentence -- and audiences never notice. The shifts become visible only on the written page. The principle: when the emotional intensity of a moment demands closeness, shift to present. When distance serves the narrative, shift to past. When in doubt, stay present. + +Not every speaker can tell stories in the present tense. Some have spent years in the past tense, and the cognitive load of switching overwhelms their delivery. There is nothing wrong with telling stories exclusively in the past tense. A well-told past-tense story beats a poorly told present-tense story without exception. + +### The Two Ways of Telling a Hero Story + +No one likes a braggart. Proverbs, da Vinci, and Mark Twain all agree on this point, and audiences confirm it nightly. Failure is more engaging than success. The story of a strikeout with the bases loaded is more compelling than the story of a walk-off home run. Getting fired from a dream job produces better narrative than getting hired. + +Yet entrepreneurs must frequently tell success stories: to investors, to recruits, to customers, to the press. The challenge is doing so without becoming insufferable. The framework offers two strategies: + +**1. Malign yourself.** + +Before telling the success, share a highly imperfect moment. Cast yourself as the underdog. In one example, a story about saving a student's life opens with a scene in which the teller accidentally strikes a child in the head with a thrown shoe. The audience knows he is not pretending to be the world's greatest teacher. By the time the success arrives, it feels earned rather than boasted. + +This is why Bruce Willis is barefoot and outnumbered in *Die Hard*. Why the rebels fly a single tiny ship against a star destroyer in the opening of *Star Wars*. Underdog status invites the audience to root for the protagonist. It converts the success story from self-congratulation into something the audience feels they participated in. + +**For founders:** Before the fundraising win, describe the seventeen rejections. Before the product breakthrough, describe the version that crashed during the demo. Before the hiring coup, describe the candidate who turned you down. The vulnerability precedes the victory, and the victory is sweetened by it. + +**2. Marginalize the accomplishment.** + +Rather than telling the complete success, tell a small part of it. Allude to the larger outcome but focus on one step. Human beings prefer stories of small steps over large leaps. Overnight successes are rare and alienating. The step-by-step nature of achievement is what audiences understand and connect with. + +In another example, a story about saving one student immediately catalogues the students the teller failed to save. The success is real but circumscribed. The audience connects with the partial, imperfect version more deeply than they would with an unblemished triumph. + +**For founders:** The story of achieving product-market fit is best told as the story of one customer's experience. The story of scaling to a hundred employees is best told as the story of one hire who changed the culture. Small steps. Never the panoramic victory lap. + +### Scene-Based Memorisation + +Do not memorise a story word for word. Actors memorise lines because they have fellow actors and stage directions to anchor them. A storyteller has nothing but the microphone and the audience. When a memorised word goes missing, the storyteller freezes. Speakers have been observed standing in silence for a minute or more, trapped in the gap between a forgotten word and the next remembered one. + +Instead, memorise three things: + +1. **The first few sentences.** Always start strong. The opening must be rehearsed to the point of automatic delivery. +2. **The last few sentences.** Always end strong. The landing is the part the audience carries with them. +3. **The scenes.** If every moment of the story is anchored in a physical location (per the Cinema of the Mind principle), then the story is a sequence of places. Remember the places, and you remember what happens in each one. + +The technique involves remembering scenes as circles in the mind -- varying in size (reflecting the scene's duration) and colour (reflecting its emotional tone). Seven scenes is the maximum. The telephone company settled on seven digits for a reason: it is the upper limit of what most people can retain at once. + +If every prepared word flees the speaker's mind, the scenes remain. The storyteller may lose a laugh line or a golden sentence, but the story still gets told. As The Moth's artistic director once observed: "You could certainly mess up your story, but you never stop talking, so I know you'll eventually find your way back." + +The principle for entrepreneurs is identical. A pitch is not a script. It is a sequence of scenes. Know the opening, know the close, know the scenes in between. The rest is navigation. + +### Words to Use, Words to Avoid + +**Profanity.** Use sparingly. Swearing is lazy in most cases; a better word almost always exists. The exceptions: repeated dialogue (someone else's words, reported faithfully), moments of extreme emotion, and the rare occasion when a profane word is genuinely the most precise one available. Avoiding profanity also broadens the contexts in which a story can be told -- from religious institutions to school classrooms to corporate retreats. + +**Vulgarity.** Distinct from profanity. Vulgarity is the description of events that are profane in nature. The rule: if the topic would be awkward to discuss with a grandparent, tread lightly. Use euphemism, allusion, and self-deprecation. The audience can fill in the reality without needing it spelled out. Graphic specificity repels; suggestive restraint engages. + +**Celebrity and pop-culture references.** Avoid. They alienate the half of the audience that does not recognise the reference. They insert a famous person into the audience's mental movie, breaking the story's internal reality. And they are lazy -- a shorthand that reveals little about character. Instead of "she was like Zooey Deschanel," describe the qualities directly: "She never seemed to have a job but always seemed to have just enough money. She was carefree. The girl who would never grow up." + +**Accents.** The rule is simple: do not attempt them. Imitating the accent of someone from another culture risks insensitivity at best, offence at worst. The sole exception is the accents of one's own parents or grandparents, where parental love provides cover. When in doubt, abstain. + +**Oddly specific words.** Prefer them. Specificity is inherently engaging and often funny. "Raisin Bran" is better than "cereal." "Pop-Tarts" is better than "snack." Precision of language is not decoration; it is the mechanism by which the audience's mental movie achieves resolution. + +### Performing Across Contexts + +The techniques above apply identically whether the venue is a thousand-seat theatre or a Thanksgiving dinner table. Context modifies scale, not substance. + +**Eye contact.** When the audience is visible (boardroom, dinner table, small stage), find three people who like you -- left, centre, right. These are the smilers, the nodders, the laughers. Use them as guideposts. The people near each guidepost will feel attended to as well. Choosing friendly faces also bolsters the speaker's confidence. + +**Microphone use.** If offered a microphone, accept it. Hearing impairment is far more prevalent than most people realise, and few hearing-impaired individuals wish to announce their condition. Three universal principles: (1) the microphone is not magic -- still project to the back of the room, (2) adjust the stand before speaking, not during, and (3) learn to cut through laughter and applause to regain control of pacing. + +**Emotional control.** Some stories provoke emotion in the teller. This is natural and, within limits, endearing. The technique for managing excessive emotion: shift perspective from first-person to overhead. Instead of reliving the moment through one's own eyes, watch it from above -- a wounded person, not oneself, seeing friends appear in a doorway. This "B button" (a term drawn from arcade racing games) provides enough distance to continue speaking. Alternatively, inoculate against the power of specific sentences by repeating them dozens of times before performing. Repetition strips some emotion; the audience's presence restores just enough. + +**Nervousness.** A moderate amount of visible nervousness is an asset. It signals vulnerability, authenticity, and that the speaker cares about the outcome. Audiences root for speakers who appear human. The exception: contexts where authority is expected (professional conferences, board presentations, State of the Union addresses). In those settings, confidence is required. But in pitches, toasts, first dates, and storytelling stages, nervousness bridges the gap between speaker and audience. + +**Never rehearse in front of a mirror.** The only person the speaker will never see during a performance is themselves. Practising before a mirror encourages attention to physical appearance, which is irrelevant. Practise before other people, or before pictures of other people, or before a wall. Anything but a reflection. + +--- + +## Prompts + +**Prompt 1 -- Tense Mapping:** +> Here is a story I plan to deliver live: [paste narrative]. Map it for tense usage. Mark which sections should be told in present tense (high emotional intensity, primary timeline, key reveals) and which in past tense (backstory, moments best told from a distance). Show where tense shifts should occur and explain why. + +**Prompt 2 -- Hero Story Redesign:** +> I need to tell a success story about [achievement]. Help me apply the two hero-story strategies: (1) identify a moment of imperfection, failure, or vulnerability I can share before the success to cast myself as an underdog, and (2) identify the smallest step within the larger success that I can focus on, marginalising the accomplishment without diminishing it. Rewrite the story using both techniques. + +**Prompt 3 -- Scene-Based Memorisation Plan:** +> Here is my story: [paste]. Break it into no more than seven scenes, each anchored in a physical location. For each scene, provide: the location, the key action or dialogue that occurs there, and the emotional tone (which I will remember as a colour). Then write the first three sentences and the last three sentences, which I will memorise word-for-word. + +**Prompt 4 -- Word Audit:** +> Review this narrative for word-choice issues: [paste]. Flag any profanity that could be replaced by a more precise word, any vulgarity that should be softened with euphemism, any celebrity or pop-culture references that should be replaced with direct description, and any generic words that would benefit from odd specificity. Provide suggested replacements. + +--- + +## Use Cases + +**Demo Day Pitch -- Accelerator Cohort** + +A founder prepares a three-minute pitch that currently reads as a memorised script. She freezes in rehearsal when she forgets a sentence. Applying scene-based memorisation: the pitch is restructured into four scenes (the customer's office where the problem was observed, the garage where the prototype was built, the Zoom call where the first paying customer signed, and the stage where the founder is standing now). The opening and closing sentences are memorised precisely. Everything in between is navigated by scene. The founder also applies the hero-story framework: before describing the first customer win, she describes the demo that crashed in front of a prospect's entire leadership team. The vulnerability earns the audience's investment in the success that follows. + +**Board Presentation -- Growth-Stage Company** + +A CEO delivers a quarterly board update that sounds like a recitation of a pre-read document. Board members check their phones. Applying the framework: the CEO shifts to present tense for the narrative sections ("It's the second week of October, and our head of product walks into my office with a chart I've never seen before"). Backstory is delivered in past tense to create temporal contrast. The success metric is introduced using the marginalization technique: rather than presenting the full dashboard, the CEO tells the story of one customer whose usage pattern revealed the insight. The board leans in. The metrics, when they appear, land in a narrative context that makes them memorable. + +--- + +## Anti-Patterns + +- **Memorising word for word.** The single most common cause of catastrophic performance failure in live storytelling and pitching. When a word goes missing, the speaker's mind goes blank. Scene-based memorisation provides a recovery path that script memorisation does not. + +- **Telling the entire success story.** Recounting every milestone, every win, every compliment received. The audience disconnects halfway through. Small steps are relatable. Panoramic victory laps are not. The most effective success story is the one that includes the failure that preceded it and the doubt that accompanied it. + +- **Defaulting to past tense out of habit.** The present tense is available and powerful, but many speakers never consider it. Past tense is safe and intuitive; present tense is transporting and immediate. The best speakers toggle between the two. The worst speakers do not know they have a choice. + +- **Performing for the mirror.** Rehearsing alone while staring at one's own reflection cultivates self-consciousness about appearance, which is the last thing a storyteller should be thinking about during delivery. The words, the pacing, the emotional arc -- these are what matter. The tilt of a head and the position of hands are irrelevant. + +- **Avoiding all vulnerability in professional contexts.** The instinct to project flawless competence in pitches, board meetings, and sales calls leads to stories that no audience connects with. Vulnerability -- the admission of a mistake, a fear, a moment of doubt -- is the bridge between speaker and listener. The observation is blunt: failure is more engaging than success. The professional who shares only success shares nothing memorable. + +- **Imitating accents.** However well-intentioned, accent imitation in storytelling carries asymmetric risk: modest upside (a moment of flavour) and catastrophic downside (the audience perceives insensitivity). The return-on-risk calculation is unambiguous. Describe the person's qualities. Leave their accent alone. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The hero-story problem is acute: founders must sell themselves without sounding like braggarts | Malign yourself early; the idea stage is where vulnerability is most credible and most needed | +| Validation | Present tense shines in customer-discovery storytelling | "I'm sitting across from a nurse practitioner who tells me..." is more visceral than a past-tense summary | +| Early Traction | Scene-based memorisation becomes essential as pitches multiply | Founders tell the same story dozens of times; scene-based structure prevents staleness and enables adaptation per audience | +| Growth | Word choice becomes a brand concern | As the company's stories reach wider audiences, profanity and vulgarity boundaries tighten; oddly specific language becomes a differentiator | +| Scale | Performance delegation -- others now tell the company's story | The CEO must train executives, salespeople, and marketers in these delivery techniques, not merely use them personally | + +At the idea stage, the founder is the company's only storyteller. Performance quality and company credibility are one and the same. At scale, the challenge inverts: the founding story is now told by dozens of people who were not there. Scene-based memorisation scales better than scripts because it allows each teller to navigate the story in their own voice while hitting the same emotional beats. + +--- + +## Output Template + +```markdown +# Performance Preparation Sheet + +## Story Title / Context +[What is being delivered, to whom, in what setting] + +## Tense Plan +- **Primary tense:** [Present / Past] +- **Tense shifts:** + - Shift to [past/present] at [moment] because [reason] + - Shift to [past/present] at [moment] because [reason] + +## Scene Map (max 7) +| # | Location | Key Action / Dialogue | Emotional Tone | +|---|----------|-----------------------|----------------| +| 1 | [Place] | [What happens] | [e.g., light, tense, vulnerable] | +| 2 | [Place] | [What happens] | [Tone] | +| ... | ... | ... | ... | + +## Memorised Opening (first 2-3 sentences) +[Write them here, word for word] + +## Memorised Close (last 2-3 sentences) +[Write them here, word for word] + +## Hero-Story Check +- **Vulnerability shared before success:** [The imperfect moment] +- **Accomplishment marginalised to:** [The small step told, not the full victory] + +## Word-Choice Notes +- **Replace:** [generic word] with [specific word] +- **Remove:** [unnecessary profanity / pop-culture reference] +- **Add specificity:** [where] + +## Context Adaptation +- **If boardroom:** [Adjust formality, reduce nervousness display, increase authority signals] +- **If pitch stage:** [Allow vulnerability, open with laugh, end on heart] +- **If dinner table:** [Shorten, increase conversational pacing, make eye contact with all] +``` + +--- + +## Related Skills + +- **[Building Story Stakes](../../content/skills/storytelling/building-story-stakes.md)** -- Delivery techniques bring stakes to life; the Hourglass is a performance technique as much as a structural one, requiring physical acts of pacing and volume control. +- **[Storytelling Truth and Vividness](../../content/skills/storytelling/storytelling-truth-and-vividness.md)** -- Cinema of the Mind provides the scenes that scene-based memorisation depends on; without physical locations for each moment, there is nothing to memorise except words. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- Surprise and humour are designed on paper but executed in the room; timing and tonality determine whether the structural design actually produces feeling. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Leaders perform in contexts where the delivery stakes are organisationally consequential; this skill provides the technique, and the leadership skill provides the strategic when-and-why. +- **[Leadership Voice and Presence](../../content/skills/leadership/leadership-voice-and-presence.md)** -- The vocal, physical, and timing techniques for story delivery directly strengthen the broader presence that leadership communication depends on. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- The tonal calibration skills for written communication parallel the vocal and emotional register choices required in live story performance. diff --git a/plugins/foreman/skills/story-structure-and-arc/SKILL.md b/plugins/foreman/skills/story-structure-and-arc/SKILL.md deleted file mode 120000 index 5844481..0000000 --- a/plugins/foreman/skills/story-structure-and-arc/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/story-structure-and-arc.md \ No newline at end of file diff --git a/plugins/foreman/skills/story-structure-and-arc/SKILL.md b/plugins/foreman/skills/story-structure-and-arc/SKILL.md new file mode 100644 index 0000000..50aa72d --- /dev/null +++ b/plugins/foreman/skills/story-structure-and-arc/SKILL.md @@ -0,0 +1,231 @@ +--- +name: "story-structure-and-arc" +description: "Teaches the five-second moment principle, the relationship between surface spectacle and underlying transformation, and the But and Therefore technique for creating narrative momentum. Use when a pitch or presentation feels flat despite containing good material, when a founder's narrative lacks forward movement, when replacing chronological recounting with cause-and-effect storytelling, or when diagnosing why an audience disengages midway through a talk." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative-arc + - five-second-moment + - but-and-therefore + - story-structure + - pitch + - presentation + - persuasion + - transformation + - momentum +related_skills: + - what-is-a-story + - finding-your-stories + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Story Structure and Arc + +FIVE SECONDS -- Jurassic Park is not a dinosaur movie. Every great story is actually about a five-second moment of change, and all the rest is scaffolding. + +Steven Spielberg spent sixty-three million dollars rendering velociraptors, brachiosaurs, and a Tyrannosaurus rex so lifelike that audiences forgot they were watching computer-generated images. Yet the moment in the film that audiences remember most, the scene that gives the story its emotional weight, contains no dinosaurs at all. It is a man sitting in a tree with two sleeping children, letting a fossilised raptor claw fall from his hand. Alan Grant, who despised children at the start of the film, has evolved. Five seconds. Story over. + +The entire storytelling architecture rests on this observation. Every great story -- regardless of length, depth, or tone -- exists to deliver a single moment of transformation. That moment lasts about five seconds. Everything else in the narrative is infrastructure designed to bring that moment to the greatest possible clarity. The dinosaurs, the car chases, the market data, the product demos -- these are not the story. They are the scaffolding that makes the five-second moment land. + +The second structural principle is equally counterintuitive: the words that connect one scene to the next matter more than the scenes themselves. Replace "and then" with "but" and "therefore," and a flat recitation of events transforms into a narrative with momentum, surprise, and causation. These two principles -- the five-second moment and the But and Therefore technique -- form the load-bearing structure of any story worth telling. + +--- + +## The Framework + +### The Five-Second Moment + +All stories are about tiny moments. The purpose of every other element -- character, setting, conflict, humour, suspense -- is to deliver the audience to that moment with maximum emotional clarity. + +The five-second moment is defined as the instant when something changes forever in a person's life: + +> You fall in love. You fall out of love. You discover something new about yourself or another person. Your opinion on a subject dramatically changes. You find forgiveness. You reach acceptance. You sink into despair. You make a life-altering decision. + +The diagnostic question is simple: **does this story contain a moment when someone's internal state shifts?** If the answer is no, the material is an anecdote, a romp, or a report -- potentially entertaining, but structurally incapable of moving an audience at the level where decisions and loyalties are formed. + +**The Jurassic Park principle:** Big stories contain tiny, utterly human moments. The spectacle serves the moment, not the reverse. Consider: + +| Film | What the audience thinks the story is about | What the story is actually about | The five-second moment | +|------|---------------------------------------------|----------------------------------|----------------------| +| Jurassic Park | Dinosaurs | A man learning to love children | Grant lets go of the fossil claw | +| Raiders of the Lost Ark | Finding the Ark of the Covenant | A scientist finding faith | Indy closes his eyes before the Ark opens | +| "Charity Thief" | Being stranded and impersonating a charity worker | Discovering he knows nothing about loneliness | A widower tells him about his dead wife | +| "This Is Going to Suck" | A near-death car accident | Discovering that friends are family | Emergency-room doors open to reveal his friends | + +In every case, removing the spectacle (dinosaurs, car crashes, snakes, robbery) would not destroy the story. Removing the five-second moment would. + +**The entrepreneurial translation** is uncomfortable but necessary. Most founders' pitch stories are structured around spectacle -- the dramatic pivot, the overnight traction, the improbable partnership. These are the dinosaurs. They attract attention, but they do not create lasting connection. The five-second moment in a founder's story is almost always smaller: the instant a customer's words reframed the entire problem. The evening a co-founder said something that changed the founder's understanding of why they were building this company. The morning the metrics dashboard showed something that contradicted everything the team believed. + +Audiences cannot connect to your miraculous product-market fit. They can connect to the moment you realised you had been wrong about something fundamental. + +### Building Toward the Moment + +Once the five-second moment is identified, every element of the story must serve it. The principle is clinical: + +- Anything that brings the five-second moment to greater clarity is **strengthened and highlighted**. +- Anything that does not serve the moment is **marginalised, shaded, or removed entirely**. + +This is a subtractive process. The natural impulse is to include every interesting detail, every amusing tangent, every contextual fact. The discipline is to cut everything that does not lead the audience toward the moment of transformation with increasing clarity and emotional investment. + +For a fundraising narrative, this means the market analysis, the competitive landscape, and the traction metrics are not the story -- they are context that either serves or distracts from the five-second moment. If a data point does not illuminate the transformation, it belongs on a supplementary slide, not in the narrative. + +### The But and Therefore Principle + +The second structural principle addresses the connective tissue between scenes, sentences, and ideas. This framework, and independently Trey Parker and Matt Stone of South Park, arrived at the same conclusion: + +**If the words "and then" can be placed between any two scenes, the story is broken.** The ideal connectors are "but" and "therefore" (and their synonyms: however, instead, as a result, except, yet, consequently). + +"And then" stories run on a treadmill. They move chronologically but go nowhere. They report events without establishing causation or opposition. + +"But" and "therefore" stories create a serrated line -- constantly cutting against the grain, zigging and zagging, presenting opposition and consequence rather than mere sequence. + +**The contrast in action:** + +"And then" version (a child's sleepover story): +> My cousin came over for a sleepover, and we went to bed on time and we didn't sleep. And my parents heard us, and they called the police. And they came and saw us watching TV. And we got in trouble. + +"But and therefore" version: +> My cousin came over for a sleepover, **but** we had no intention of sleeping. We went to bed on time, **but** we didn't close our eyes. **Instead** we snuck downstairs to watch TV. **But** my parents heard us -- **except** it wasn't us they heard. It was the TV voices. **Instead of** investigating, they **therefore** assumed burglars were robbing the house, **so** they called the police. **But** they didn't wake us up, because they didn't want us to scare us. The police arrived, **but instead of** finding burglars, they found us watching television. **As a result,** we got in so much trouble. + +Same facts. Radically different momentum. The second version cuts against itself at every turn, creating the sensation of movement and surprise even though the events are linear and the ending is predictable. + +**The power of the negative:** A related technique amplifies the But and Therefore principle. Saying what something is not is almost always more effective than saying what it is, because negation contains a hidden "but" -- it presents both possibilities simultaneously. + +- "I was lost" is not as effective as "I could not find my way home." +- "I was penniless" is not as effective as "I didn't have a penny to my name." +- "Heather is my ex-girlfriend" is not as effective as "Heather is no longer my girlfriend." + +The negative construction implies a world in which the positive was possible, creating depth and movement within a single clause. + +**For entrepreneurs,** the But and Therefore principle is the difference between a pitch that recites milestones and one that makes the audience feel the venture's momentum. "We built the product, and then we launched, and then we got customers" is a timeline. "We built the product for enterprise clients, **but** mid-market companies adopted three times faster. **Therefore** we repositioned the entire go-to-market, **but** that meant renegotiating every existing contract" is a narrative. Same facts. Different effect. + +--- + +## Prompts + +**Prompt 1 -- Five-Second Moment Extraction:** +> Here is a story I plan to tell in [context]: [paste story or describe the events]. Identify the five-second moment -- the instant of genuine transformation. If no such moment exists, say so plainly. If the story has been built around spectacle (the dramatic event) rather than the moment of change, identify the real five-second moment hiding beneath the spectacle and suggest how to restructure around it. + +**Prompt 2 -- But and Therefore Audit:** +> Analyse the following narrative for "and then" disease: [paste narrative]. Highlight every instance where sentences or scenes are connected by sequence ("and," "and then," "next," "after that") rather than by opposition or consequence ("but," "therefore," "however," "as a result," "instead"). Rewrite the flagged sections using But and Therefore connectors, preserving the same facts but creating momentum and causation. + +**Prompt 3 -- Scaffolding Triage:** +> I have a story about [describe the five-second moment]. Here are all the details and events I could include: [list everything]. Apply the scaffolding test: for each detail, assess whether it brings the five-second moment to greater clarity (keep), is neutral (cut), or actively distracts from the moment (definitely cut). Return a prioritised list of elements to include, ordered by their contribution to the moment's emotional impact. + +**Prompt 4 -- Negative Construction Rewrite:** +> Rewrite the following sentences using the power of the negative -- replacing positive statements with their negative equivalents to create hidden "buts" and greater depth: [paste sentences]. For each rewrite, briefly explain what binary option the negative introduces and why it creates more movement than the original. + +--- + +## Use Cases + +**Validation-stage founder restructuring an investor pitch around the five-second moment** + +A healthtech founder's pitch centres on a dramatic stat: 40% of patients in a specific condition category receive the wrong initial treatment. The pitch walks through the problem, the product, the traction, and the ask. It is competent and forgettable. Applying the five-second moment principle, the founder identifies the real story: the afternoon she sat in a hospital waiting room with her father and watched a doctor deliver a diagnosis that she -- with her domain expertise -- knew was wrong, and realised that she could not intervene. That is the moment of transformation. The 40% statistic becomes scaffolding that supports the moment rather than replacing it. The restructured pitch opens with the waiting room, delivers the data as context, and returns to the human moment for the close. Three investors who heard the revised pitch mentioned the waiting room scene in their follow-up emails. None mentioned the statistic. + +**Early-traction CEO eliminating "and then" disease from the company narrative** + +A B2B SaaS company's sales deck tells its story as a chronological sequence: "We started in 2021, and then we launched our MVP, and then we got our first customer, and then we raised our seed round, and then we expanded to three verticals." The CEO applies the But and Therefore principle: "We started in 2021 building for enterprise, **but** our first paying customer was a 50-person startup that found us on Twitter. **Therefore** we rebuilt onboarding for smaller teams -- **but** that meant our enterprise pipeline went cold. **Instead of** retreating, we discovered that mid-market companies churned at half the rate. **As a result,** we repositioned entirely." The revised narrative covers the same ground in the same time but feels like a journey with twists rather than a treadmill with milestones. + +**Growth-stage product leader diagnosing a failed keynote** + +A VP of Product delivers a conference keynote about the company's platform evolution. Audience engagement scores are below average. Post-mortem analysis using the framework reveals two problems: the talk was built around the product's capabilities (spectacle) rather than a moment of customer or team transformation (five-second moment), and every transition between sections used "and" or "next" rather than "but" or "therefore." The VP restructures: the talk now centres on the moment a key customer used the platform in a way the team had never anticipated, which fundamentally changed the product roadmap. Transitions are rebuilt with opposition and consequence. The next keynote scores in the top quartile. + +--- + +## Anti-Patterns + +**1. Mistaking the dramatic event for the five-second moment.** The story of a near-death experience took three years to craft because the narrative kept ending at the car accident. The actual five-second moment -- friends arriving at the emergency room when his parents did not -- was quieter and vastly more powerful. Founders make the identical error when they build narratives around their most dramatic milestone (the huge deal, the viral launch) instead of the quieter moment of genuine change. + +**2. Scaffolding that overwhelms the moment.** When context, data, and backstory consume 90% of the narrative, the five-second moment arrives as an afterthought. The audience has invested attention in the scaffolding and has little left for the payoff. Ruthless cutting is not optional; it is structural. + +**3. Applying But and Therefore mechanically.** The principle describes an orientation, not a formula. Inserting "but" before every sentence produces a staccato rhythm that sounds contrived. The technique works when opposition and consequence are genuine -- when the narrative actually zigs and zags -- not when transitional words are sprinkled as decoration. + +**4. Stories about two things.** A single narrative can contain only one five-second moment. The band-camp beating story carried two separate meanings -- the realisation that people will turn their backs on evil, and the realisation that the world is fundamentally unsafe. These are two stories, not one. Each demands a different beginning and a different arc. Founders who try to make a single pitch story carry two transformations dilute both. + +**5. Using the framework to justify spectacle.** Knowing that Jurassic Park uses dinosaurs as scaffolding does not licence packing a pitch with irrelevant flash. The dinosaurs work because they are causally linked to Grant's transformation -- without them, he never spends time with the children. Scaffolding that does not causally serve the five-second moment is bloat, regardless of how impressive it is. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal five-second moment that explains why this company exists | The moment is everything; scaffolding is minimal because the company barely exists yet | +| Validation | Customer-triggered moments of transformation in the founder's understanding | The five-second moment increasingly involves other people's words and reactions | +| Early Traction | Pivot moments structured with But and Therefore momentum | The narrative must convey a journey of opposition and consequence, not a timeline of milestones | +| Growth | Training the team to find five-second moments in their own domains | Product stories, sales stories, and support stories each need their own moment of change | +| Scale | Institutional narratives built on chains of transformation | The company story is a sequence of five-second moments, each connected by "but" and "therefore" | + +At the idea stage, the founder typically has one five-second moment and very little scaffolding. The craft challenge is making that single moment land with enough force that it carries the entire pitch. + +At early traction and growth, the challenge inverts. Material is abundant -- customers, pivots, team dynamics, competitive battles -- and the temptation is to include everything. The discipline of serving only the five-second moment, and of connecting scenes with opposition and consequence rather than sequence, becomes the primary structural skill. + +--- + +## Output Template + +```markdown +# Story Structure Worksheet -- [Story Title or Context] + +**Teller:** [Name] +**Context:** [Pitch / Keynote / All-hands / Customer conversation] +**Date:** [Date] + +## 1. The Five-Second Moment +**What changed:** [Describe the precise instant of transformation] +**Before state:** [What the protagonist believed, felt, or understood] +**After state:** [What shifted] +**Is this genuinely a moment of transformation?** [Yes / No] + +## 2. Scaffolding Audit +| Element | Serves the moment? | Keep / Cut / Reduce | +|---------|-------------------|---------------------| +| [Detail 1] | [How it connects to the five-second moment] | [Decision] | +| [Detail 2] | [How it connects] | [Decision] | +| [Detail 3] | [How it connects] | [Decision] | + +## 3. But and Therefore Map +[Write the story's scene-by-scene flow using explicit connectors] +- Scene 1: [Description] ... +- **But** Scene 2: [Description] ... +- **Therefore** Scene 3: [Description] ... +- **But** Scene 4: [Description] ... +- **Therefore** Five-second moment: [Description] + +**"And then" count in current draft:** [Number] +**"But / therefore" count in current draft:** [Number] + +## 4. Negative Construction Opportunities +| Original (positive) | Rewrite (negative) | +|---------------------|-------------------| +| [Statement] | [Rewrite with hidden "but"] | +| [Statement] | [Rewrite with hidden "but"] | + +## 5. One-Sentence Story Summary +[I was once [starting state], but then [five-second moment], and now I am [ending state].] +``` + +--- + +## Related Skills + +- **[What Is a Story](../../content/skills/storytelling/what-is-a-story.md)** -- Establishes the transformation requirement that the five-second moment fulfils; read this first if the concept of story-as-change is unfamiliar. +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- The five-second moment must be found before it can be structured; Homework for Life is the discovery mechanism. +- **[Story Beginnings and Endings](../../content/skills/storytelling/story-beginnings-and-endings.md)** -- Once the five-second moment is identified, this skill teaches the opposite-of-the-end rule for choosing where to begin. +- **[Building Story Stakes](../../content/skills/storytelling/building-story-stakes.md)** -- Stakes create the tension that makes the five-second moment land; the Hourglass and Breadcrumbs techniques amplify the structural arc built here. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- The four-function framework for change stories operates at the leadership-application layer; the structural techniques here provide the underlying craft. +- **[Creative Shaping and Craft](../../content/skills/creative/creative-shaping-and-craft.md)** -- The broader creative discipline of finding the essence and refining form applies directly to the structural choices of what to include and what to cut in narrative construction. diff --git a/plugins/foreman/skills/storytelling-for-leaders/SKILL.md b/plugins/foreman/skills/storytelling-for-leaders/SKILL.md deleted file mode 120000 index 8496828..0000000 --- a/plugins/foreman/skills/storytelling-for-leaders/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/storytelling-for-leaders.md \ No newline at end of file diff --git a/plugins/foreman/skills/storytelling-for-leaders/SKILL.md b/plugins/foreman/skills/storytelling-for-leaders/SKILL.md new file mode 100644 index 0000000..05a6ef6 --- /dev/null +++ b/plugins/foreman/skills/storytelling-for-leaders/SKILL.md @@ -0,0 +1,177 @@ +--- +name: "storytelling-for-leaders" +description: "Equips leaders with practical storytelling techniques for driving organisational change, building empathy, simplifying complexity, and creating shared narratives. Use when launching a transformation initiative, when data alone fails to persuade, when teams need emotional alignment around a vision, or when a leader's communication is technically sound but fails to move people." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - communication + - change-management + - persuasion + - narrative + - empathy + - vision +related_skills: + - leading-through-change + - kotter-change-model + - cialdini-influence + - radical-candor + - inclusive-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Storytelling for Leaders + +In 2008, Howard Schultz returned to a Starbucks that had lost its way. The company had over-expanded, commoditised its experience, and watched same-store sales decline for the first time in its history. Schultz did not begin his turnaround with a strategy deck. He began with a story. He described walking into a Starbucks in Los Angeles and noticing that the store smelled like burnt cheese from the new breakfast sandwiches -- not coffee. That single sensory detail carried more persuasive weight than any financial analysis could have. It told every employee, investor, and customer exactly what had gone wrong and, by implication, what "right" would look like. The breakfast sandwiches were pulled within weeks. The story preceded the strategy, and the strategy succeeded because the story made the problem visceral. + +This is not an accident. Humans evolved to process narrative before they developed the capacity for abstract reasoning. A well-constructed story activates neural coupling -- the listener's brain begins to mirror the storyteller's -- in ways that bullet points and bar charts cannot. Leaders who understand this do not treat storytelling as a soft skill bolted onto "real" leadership. They treat it as the primary vehicle through which meaning travels inside organisations. + +--- + +## The Framework + +### The Four Functions of Change Stories + +Frances Frei and Anne Morriss identify four things that effective change stories accomplish. Each addresses a different psychological need in the audience. + +**1. Provide a Mandate for Change** + +Every transformation story must answer: why now? The mandate is not a vague sense that things could be better. It is a specific articulation of the problem being solved and the cost of inaction. The cost should be concrete -- lost customers, eroding margins, talent departing -- not abstract ("we need to innovate"). Crucially, the mandate must be persuasive enough to override the gravitational comfort of familiar behaviours. People will tolerate considerable pain if the alternative is uncertainty; the mandate must make inaction more frightening than change. + +**2. Honour the Past** + +Change stories that dismiss history alienate the people who built the current organisation. The most effective narratives acknowledge what was built well, name the human cost of past mistakes honestly, and distinguish what must change from what should endure. A leader who says "everything before me was wrong" loses credibility with anyone who invested years in the previous era. A leader who says "we built something remarkable, and the world has shifted in ways that require us to evolve" earns permission to lead the evolution. + +**3. Understand Deeply, Describe Simply** + +If a vision can only be articulated in jargon, it has not been thought through. Frei and Morriss propose a compression test: Can you capture the change in a page? A paragraph? A single word? Simplicity is not a concession to unsophisticated audiences -- it is proof of intellectual clarity. The leader who can explain a complex transformation in language a new hire understands has done the harder cognitive work. + +**4. Describe a Rigorous, Optimistic Way Forward** + +The forward-looking portion of the story requires both data and enthusiasm. A few -- only a few -- data points serve as plot points, providing rigour. Optimism provides fuel. This is not naivete; it is the leader's genuine conviction that the plan will work, communicated with enough energy to be contagious. Sceptics will not be converted by optimism alone, but without it, even the best plan feels like an assignment rather than an adventure. + +### Personal Storytelling as Leadership Infrastructure + +Julie Battilana and Tiziana Casciaro's research on power and empathy reveals a complementary function of storytelling: building the relational connective tissue that makes authority legitimate. When leaders invite employees at all levels to share stories about their work, challenges, and perspectives, two things happen. The leader gains information that formal reporting channels filter out. And employees gain the felt experience of being heard, which strengthens trust and engagement. + +The practice is deceptively simple. A monthly session in which three or four employees share a five-minute story about a recent challenge or success -- with the leader listening, not evaluating -- creates more empathy than a year of engagement surveys. + +--- + +## Prompts + +**Prompt 1 -- Change Story Construction:** +> I am leading a significant change: [describe the change, its rationale, and its expected impact]. Using Frei and Morriss's four-function framework (mandate, honour the past, simplify, describe the way forward), draft a narrative I can deliver in five minutes to my full team. Include one concrete sensory detail, one data point, and one explicit acknowledgement of what we have done well and should preserve. + +**Prompt 2 -- Simplification Stress Test:** +> Here is my current explanation of our strategic direction: [paste existing explanation]. Compress it to: (a) one page, (b) one paragraph, (c) one sentence, (d) one word. At each level, tell me what I lost and whether it matters. Identify any jargon that would confuse a new hire. + +**Prompt 3 -- Personal Story Mining:** +> I want to use personal storytelling to build empathy with my team, but I am unsure which experiences are appropriate to share. Here are five significant moments from my career: [describe them briefly]. For each, assess: (a) does it reveal vulnerability without undermining authority? (b) does it connect to a lesson relevant to the team's current situation? (c) is it specific enough to be memorable? Recommend which to use and how to frame it. + +**Prompt 4 -- Story-Driven Presentation Redesign:** +> I have a data-heavy presentation: [describe the content and audience]. Restructure it as a narrative arc: opening hook, rising tension (the problem), turning point (the insight), resolution (the plan), and call to action. Integrate the most important data points as plot elements rather than slide decorations. Keep it under 15 minutes. + +--- + +## Use Cases + +**Early-traction founder pitching a pivot to investors** + +A SaaS startup has spent 18 months building a product for enterprise clients, only to discover that mid-market companies adopt faster and churn less. The founder needs to explain the pivot to existing investors who backed the enterprise thesis. Rather than leading with revised financial projections, the founder opens with a story: a specific mid-market customer who went from first demo to signed contract in eleven days, versus the enterprise prospect who has been "evaluating" for nine months. The story makes the strategic shift self-evident. Projections follow as confirmation, not persuasion. + +**Growth-stage CEO rallying a demoralised team after layoffs** + +A company that grew from 80 to 300 people in two years has been forced to lay off 60 employees following a market contraction. Survivors are anxious, guilty, and disengaged. The CEO resists the temptation to skip directly to "here is our new strategy" and instead begins with a story that honours what the departed colleagues built. She names three specific contributions from laid-off team members, acknowledges the human cost plainly, and then describes -- in vivid, concrete terms -- what the leaner company can now do that the bloated one could not. The forward story is not about cost-cutting; it is about focus. + +**Scale-stage leader aligning a cross-functional team** + +A 1,000-person company launches a cross-functional initiative that requires engineering, marketing, and operations to collaborate in ways they never have. The programme leader discovers that each function has a different mental model of what success looks like. Rather than distributing a project charter, the leader hosts a story-sharing session: each function's representative tells a two-minute story about a time their team solved a problem they were proud of. The stories reveal shared values -- quality, speed, customer obsession -- that become the foundation for a unified narrative. + +--- + +## Anti-Patterns + +**1. Stories without substance.** A compelling narrative wrapped around a weak strategy is manipulation, not leadership. If the data does not support the story's claims, the audience will eventually discover the gap, and trust will collapse. Story amplifies strategy; it does not replace it. + +**2. The leader as perpetual hero.** When every story the leader tells features themselves overcoming adversity, the audience learns that the leader's ego, not the team's mission, is the point. The most effective leadership stories feature other people, or feature the leader in a moment of uncertainty or failure. + +**3. Honouring the past insincerely.** A perfunctory "we have a proud history" followed by "but everything must change" reads as dismissal in a thin disguise. If the acknowledgement does not name specific achievements and specific people, it will be perceived as cynical. + +**4. Over-simplifying to the point of distortion.** The compression test is a tool for clarity, not for eliminating nuance. A one-word summary that misrepresents the strategy is worse than a paragraph that captures it accurately. Simplicity should never sacrifice truth. + +**5. Storytelling as a one-time event.** A single powerful narrative at a town hall does not sustain a multi-year transformation. Effective leaders tell the story repeatedly, adapting it as circumstances change, and invite others to tell their own versions of it. The story must be a living document, not a keynote. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Origin story, founder narrative | The story IS the company; investors and early hires buy the narrative before the product | +| Early Traction | Pivot stories, customer stories | Stories shift from "why we exist" to "why we are changing" | +| Growth | Culture stories, alignment narratives | Stories must scale beyond the founder's voice; equip managers to tell them | +| Scale | Institutional narrative, legacy stories | The organisation needs a story that outlives any individual leader | + +At validation, the founder's personal story and the company's story are functionally identical. The pitch deck is a story. The hiring conversation is a story. The ability to articulate a compelling "why" in 60 seconds may be the single most valuable skill at this stage. + +At growth, the critical challenge is narrative distribution. When the founder was the only storyteller, consistency was automatic. With 50 or 200 people, the story must be simple enough for every manager to tell accurately while being rich enough to remain meaningful. Leaders at this stage invest in what might be called "story infrastructure": shared language, recurring story-sharing rituals, and explicit permission for team-level narratives that connect to the master narrative without being identical to it. + +--- + +## Output Template + +```markdown +# Change Narrative -- [Initiative Name] + +**Audience:** [Team / Investors / Board / All-hands] +**Duration:** [Target delivery time] +**Prepared by:** [Name] +**Date:** [Date] + +## 1. The Mandate (Why Now) +**The problem:** [Specific, concrete description] +**The cost of inaction:** [Quantified where possible] +**The sensory detail:** [One vivid, specific observation that makes the problem real] + +## 2. Honouring the Past +**What we built well:** [Specific achievements and people] +**What must be preserved:** [Values, practices, or capabilities to carry forward] +**Honest acknowledgement:** [What did not work, and what it cost] + +## 3. The Way Forward (Simplified) +**One word:** [The essence] +**One sentence:** [The thesis] +**One paragraph:** [The plan with enough detail to be credible] +**Key data point:** [One number that anchors the narrative] + +## 4. The Call to Action +**What changes immediately:** [Concrete first steps] +**What each person can do this week:** [Specific, actionable] +**What success looks like in 90 days:** [Measurable outcome] + +## Delivery Notes +- Open with: [The hook -- story, detail, or question] +- Close with: [The emotional resonance -- what this means for us] +- Anticipated questions: [Top 3 and prepared responses] +``` + +--- + +## Related Skills + +- **[Leading Through Change](../../content/skills/leadership/leading-through-change.md)** -- Storytelling is the communication layer of change leadership; this companion skill covers the emotional and structural dimensions. +- **[Kotter's Change Model](../../content/skills/frameworks/kotter-change-model.md)** -- Kotter's "create a vision" and "communicate the vision" steps are precisely where storytelling operates within a structured change process. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- Provides the five-second moment and But-and-Therefore momentum techniques that give leadership stories their narrative power. +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- The Homework for Life discovery practice feeds directly into the personal narrative library that leaders draw from for change and empathy stories. +- **[Inclusive Leadership](../../content/skills/leadership/inclusive-leadership.md)** -- Personal storytelling builds the empathy and connection that inclusive cultures depend on. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- The surprise and emotional design techniques that determine whether leadership stories produce genuine feeling or merely transmit information. diff --git a/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md b/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md deleted file mode 120000 index cbee3f4..0000000 --- a/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/storytelling-truth-and-vividness.md \ No newline at end of file diff --git a/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md b/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md new file mode 100644 index 0000000..fcfaae9 --- /dev/null +++ b/plugins/foreman/skills/storytelling-truth-and-vividness/SKILL.md @@ -0,0 +1,219 @@ +--- +name: "storytelling-truth-and-vividness" +description: "Provides an ethical framework for nonfiction storytelling (the Five Permissible Lies) and techniques for creating vivid mental imagery (Cinema of the Mind). Applies when a founder is crafting a company origin story, preparing a keynote, refining a customer case study, or deciding how much to compress or omit from a real narrative. Use when the question is not what to say but how truthfully and vividly to say it." +version: "1.0.0" +category: "storytelling" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - truth + - ethics + - vividness + - cinema-of-the-mind + - omission + - compression + - sensory-detail + - nonfiction + - pitching + - narrative-craft +related_skills: + - building-story-stakes + - emotional-impact-in-stories + - story-performance-and-delivery + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Storytelling Truth and Vividness + +The best storytellers lie -- but only in five specific ways, each with an inviolable rule that separates craft from dishonesty. The framework calls them the Five Permissible Lies of True Storytelling, and they constitute an ethical framework as rigorous as it is practical. Paired with the Cinema of the Mind principle -- the insistence that every moment of a story must exist in a physical location the audience can see -- these two doctrines form the foundation of nonfiction narrative craft. For the entrepreneur who trades in origin stories, customer narratives, and investor updates built on real events, the question is never whether to shape the truth. The question is how to shape it without breaking it. + +--- + +## The Framework + +### Part I: The Five Permissible Lies + +Three caveats govern all five lies. First, storytellers lie only for the benefit of the audience, never for personal gain -- not to appear more noble, mitigate shame, or inflate accomplishment. Second, memory itself is unreliable; each retelling alters the original, so perfect accuracy was never on offer. Third, storytellers never add something that was not already there. The raw material is fact. The craft is selection and arrangement. + +#### Lie 1: Omission + +Every story contains omissions; if it did not, it would never end. Strategic omission removes people, subplots, and details that do not serve the story's core moment. One illustrative example removes an entire hitchhiker -- a vivid, memorable character -- from one of his most performed stories because the hitchhiker's presence would pull the audience's attention away from the porch where the story's emotional centre lives. + +The rule: omit anything that distracts from the five-second moment of transformation. People are the most frequently omitted element. If a third person in a car does not fill a role in the narrative, that person was never in the car. + +**Omission of endings** deserves special attention. The principle holds that storytellers should end their stories in the most advantageous place, even if reality continued. Redemption arcs -- "I did a terrible thing, but then I made up for it" -- make it easy for the audience to remove the story like a coat. The world is back in order; all debts are paid; the listener sleeps well. The best stories leave the world slightly broken. They omit the resolution so the narrative lingers. + +For entrepreneurs: the temptation to wrap every company story in a neat bow is strong. Resist. The pitch that ends with "and then everything worked out perfectly" is forgettable. The one that ends with a question still hanging in the air -- that is the one investors remember at midnight. + +#### Lie 2: Compression + +Compression pushes time and space together to make a story easier to comprehend, visualise, and tell. A Saturday-Sunday sequence becomes a single Saturday afternoon. A geographically sprawling series of events is simplified into a tighter footprint. + +The rule: compress only to reduce needless complexity. Placing scenes closer together also heightens drama and suspense, making the world feel more cinematic. There is never room for unnecessary complication in a story. Stories are rivers; they flow past the audience regardless of whether the listener is still constructing a mental map. + +For entrepreneurs: the eighteen-month product development cycle becomes "one winter." The four-city customer research tour becomes "a week in Detroit." Compression is not dishonesty. It is architecture. + +#### Lie 3: Assumption + +When a forgotten detail is critical to the story, the storyteller makes a reasonable assumption about what it might have been. When the make of a car involved in a pivotal childhood moment cannot be remembered, calling it a station wagon is reasonable -- the most common vehicle on 1970s roads. + +The rule: always assume the most reasonable, most likely version. Never assume something more dramatic or interesting than probability supports. The temptation to upgrade the station wagon to a cherry-red Corvette is precisely the temptation that must be refused. + +#### Lie 4: Progression + +Progression changes the order of events to make a story more emotionally satisfying. This is considered the least common lie and reportedly has never been used by its originator, though he recommends it to others when chronological reality defies narrative expectation. + +The rule: change order only when the real-life sequence undermines the emotional trajectory the audience needs. A story about spreading a brother's ashes at three locations -- a family tree, a strip club, a baseball stadium -- works best when the most emotionally powerful location comes last, even if it happened first. + +For entrepreneurs: if the customer breakthrough happened before the technical crisis, but the story makes more sense with crisis preceding breakthrough, progression is the tool. The facts remain; only their sequence shifts. + +#### Lie 5: Conflation + +Conflation squeezes all the emotion of an extended process into a single moment. Rather than describing gradual change over months, the storyteller locates one scene and declares it the moment of transformation. + +The rule: transform *a* moment into *the* moment. Movies do this relentlessly -- Danny Ocean's crew plans a multimillion-dollar heist in days rather than years, because days are thrilling and years are boring. Shorter stories, whether on stage or in a boardroom, are always more engaging. + +For entrepreneurs: the slow realisation that product-market fit had arrived becomes the single Slack message from a customer that made it undeniable. The gradual loss of faith in a co-founder becomes the one conversation in a parking lot. Conflation is the art of compression applied to interior experience. + +### Part II: Cinema of the Mind + +A great storyteller creates a movie in the minds of the audience. The principle is simple, the execution frequently neglected: always provide a physical location for every moment of the story. + +If the audience knows where the storyteller is at all times, the film is running. If the audience cannot picture the scene, the film has stopped. What remains is lecturing, or essay-reading, or at best a disconnected series of observations. + +**The difference a single sentence makes.** The text demonstrates this with two versions of the same character description. One opens with abstract attributes: "My grandmother was crooked in body and mind, wore dark colours, served food stewed for days." The other opens with a scene: "I'm standing at the edge of my grandmother's garden, watching her relentlessly pull weeds from the unforgiving soil." The character description that follows is identical. Only the second version is a story. + +**Backstory requires a location too.** When a story demands exposition -- family history, financial context, emotional state -- the storyteller must anchor that exposition in a physical place. One example parks the character behind the wheel of a car in a gas-station lot and delivers two minutes of backstory while the audience can see him gripping the steering wheel. The film never stops. + +The alternative -- "Let me tell you about my finances in 1991" -- is not a story. It is a narrator stepping out of the frame to deliver a lecture. The movie has stopped. + +**Technical or historical exposition** should be delivered through anecdote, not explanation. If the audience needs to understand a concept, the storyteller tells the story of the first time they learned that concept. The classroom, the teacher, the moment of comprehension -- all of it keeps the camera pointed at a scene rather than at a lecturer. + +**Sensory specificity matters.** Generic imagery ("a nice house") does nothing. Specific imagery ("a red-brick house on a quiet residential street with a blue door") gives the audience's mind enough to construct the rest. Provide the anchor details; let the audience populate the scene with their own experience. + +--- + +## Prompts + +**Prompt 1 -- Ethical Audit:** +> Here is a true story I plan to tell: [paste narrative]. Apply the Five Permissible Lies framework. Identify what I should omit (people, subplots, endings), where I should compress time or geography, where I might need to make a reasonable assumption, whether the event order should change for emotional impact, and where I should conflate gradual change into a single moment. Flag any point where I may be crossing from craft into dishonesty. + +**Prompt 2 -- Cinema of the Mind Rewrite:** +> Here is a passage from a presentation or story I am preparing: [paste passage]. Rewrite it so that every moment has a physical location the audience can see. Convert any abstract exposition into scene-grounded narrative. Add specific sensory anchors (not generic ones) so the audience's mental movie never stops. + +**Prompt 3 -- Backstory Integration:** +> I need my audience to understand [technical concept / company history / personal background] before the main story can proceed. Help me deliver this exposition without breaking the cinematic frame. Suggest a specific physical location where I can anchor this backstory and a brief anecdote or scene that conveys the information while keeping the film running. + +**Prompt 4 -- Omission Decisions:** +> Here is the full, unedited version of a story I want to tell: [paste]. Identify every person, subplot, and detail that does not serve the core five-second moment of transformation. Recommend what to cut and explain why. Also assess whether the current ending offers too much resolution and suggest where to end earlier for maximum lingering impact. + +--- + +## Use Cases + +**Customer Case Study -- B2B SaaS** + +A marketing team drafts a case study that reads like a chronological log: "In January, the customer signed. In March, onboarding completed. In June, metrics improved." Cinema of the Mind is absent; no scene has a location. Applying the framework: the case study opens in a specific room ("The VP of Operations was standing at a whiteboard covered in red-ink process maps when our implementation lead walked in"). Compression collapses six months into three key scenes. Omission removes two project stakeholders who played no role in the transformation. The result reads like a story, not a spreadsheet. + +**Founder Origin Narrative -- Pre-Seed Pitch** + +A first-time founder tells the story of discovering the problem her company solves. The unedited version spans three years and four cities. Conflation compresses the gradual realisation into a single moment at a hospital bedside. Compression reduces the geography to one city. An assumption fills in a forgotten detail (the specific date becomes "a Tuesday in November" -- reasonable and evocative). The Elephant is planted in the first sentence. Every scene has a location. The three-year journey becomes a four-minute story that an investor can see. + +**Internal All-Hands -- Quarterly Retrospective** + +A COO delivers a quarterly update that begins with "Let me give you some context on Q3." The movie has stopped before it started. Applying Cinema of the Mind: the update opens with a scene ("Three months ago, I was sitting in the Denver airport at 6 a.m., reading a customer email on my phone that changed how I think about our roadmap"). Backstory about Q3 objectives is delivered while the audience can picture the COO in that airport seat. Omission removes two initiatives that did not materially affect the quarter's outcome. The update becomes a narrative the team remembers. + +--- + +## Anti-Patterns + +- **Adding what was never there.** The five lies permit shaping, selecting, and rearranging existing facts. They never permit invention. A founder who adds a customer quote that was never said, a metric that was never measured, or a scene that never occurred has crossed from craft into fabrication. The distinction is non-negotiable. + +- **Lying for personal advantage.** Omitting a co-founder's contribution to make oneself appear more central. Compressing timelines to obscure how long a problem persisted. Conflating another person's insight into one's own epiphany. Each of these violates the first caveat: lies serve the audience, never the teller. + +- **The locationless narrative.** Opening a story, pitch, or presentation with abstract statements ("We believe that the future of healthcare is...") rather than a scene. The audience's mental movie has not started. They are staring at the speaker, not seeing the story. Every opening needs a where. + +- **Describing what needs no description while neglecting what does.** Spending thirty seconds on company credentials (which the audience can read) while skipping the sensory detail of the moment that matters (which only the storyteller can provide). Inversion of emphasis is the most common vividness failure. + +- **Offering the neat redemption.** Ending every company story with "and then it all worked out." The coat comes off easily. The story is forgotten by lunch. Ending with the world still slightly askew -- a question unanswered, a tension unresolved, a cost acknowledged -- gives the narrative staying power. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Compression and conflation dominate: the founder's years of thinking must become one vivid scene | The danger is fabrication; at this stage, there is little track record to draw from, so the temptation to invent is highest | +| Validation | Omission becomes critical: early experiments produce messy, multi-threaded narratives | Cut ruthlessly to the one thread that serves the five-second moment of customer discovery | +| Early Traction | Cinema of the Mind creates differentiation in investor conversations | When every founder has similar metrics, the one who tells a story the investor can *see* wins the meeting | +| Growth | Progression may be needed: the order in which things happened may not match the order in which they are best understood | Internal communications benefit from reordered narratives that build to the insight rather than burying it | +| Scale | All five lies operate simultaneously across dozens of company narratives | The challenge shifts from telling one story well to maintaining truthfulness at institutional scale, where many people shape the narrative | + +At scale, the greatest risk is not individual dishonesty but institutional drift: stories retold so many times that they accumulate embellishments no single person added. Regular audits of the company's core narratives against original facts are the organisational equivalent of the Five Permissible Lies caveats. + +--- + +## Output Template + +```markdown +# Narrative Truth & Vividness Worksheet + +## Core Story +[One-paragraph summary of the true events] + +## Five-Second Moment +[The single moment of transformation this story exists to deliver] + +## Omissions +| Element Removed | Reason | +|-----------------|--------| +| [Person / subplot / detail] | [Does not serve the five-second moment] | +| [Ending / resolution] | [Removes the coat too easily] | + +## Compressions +| Original Timeline / Geography | Compressed Version | Justification | +|-------------------------------|--------------------|---------------| +| [e.g., 6 months, 3 cities] | [e.g., one winter, one city] | [Reduces complexity] | + +## Assumptions Made +| Forgotten Detail | Assumed Version | Why Reasonable | +|------------------|-----------------|----------------| +| [e.g., car model] | [e.g., Honda Civic] | [Most common car in that context] | + +## Progression Changes +| Original Order | New Order | Emotional Rationale | +|----------------|-----------|---------------------| +| [A, B, C] | [C, A, B] | [Most powerful moment must come last] | + +## Conflations +| Gradual Process | Single Moment Chosen | Why This Moment | +|-----------------|----------------------|-----------------| +| [e.g., 8-month realisation] | [e.g., one email on a Tuesday] | [Most vivid, most representative] | + +## Cinema of the Mind Check +| Scene | Physical Location | Sensory Anchors | +|-------|-------------------|-----------------| +| [Scene 1] | [Specific place] | [2-3 concrete details] | +| [Scene 2] | [Specific place] | [2-3 concrete details] | +``` + +--- + +## Related Skills + +- **[Building Story Stakes](../../content/skills/storytelling/building-story-stakes.md)** -- Vividness and truth are the canvas; stakes are the tension stretched across it. The Hourglass technique depends on Cinema of the Mind to work. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- Surprise, the sole mechanism for emotional impact, requires honest setup; the Five Permissible Lies define the boundaries within which that setup can be shaped. +- **[Story Performance and Delivery](../../content/skills/storytelling/story-performance-and-delivery.md)** -- Present-tense narration amplifies Cinema of the Mind; the two techniques are mutually reinforcing in live delivery. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Leaders face particular ethical pressure when shaping company narratives; the Five Permissible Lies provide the guardrails. +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- The raw moments discovered through Homework for Life gain their power from the sensory detail and honest rendering that vividness techniques provide. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- Cinema of the Mind depends on concrete, accessible language; the jargon and abstraction that plain language eliminates are the primary enemies of vivid storytelling. diff --git a/plugins/foreman/skills/strategic-questioning/SKILL.md b/plugins/foreman/skills/strategic-questioning/SKILL.md deleted file mode 120000 index 6542e5f..0000000 --- a/plugins/foreman/skills/strategic-questioning/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/strategic-questioning.md \ No newline at end of file diff --git a/plugins/foreman/skills/strategic-questioning/SKILL.md b/plugins/foreman/skills/strategic-questioning/SKILL.md new file mode 100644 index 0000000..a2d9995 --- /dev/null +++ b/plugins/foreman/skills/strategic-questioning/SKILL.md @@ -0,0 +1,220 @@ +--- +name: "strategic-questioning" +description: "Transforms leaders from directive communicators into strategic questioners who use inquiry to inspire thinking, surface hidden problems, build ownership, and drive better decisions. Covers five essential leadership questions, the art of context-rich inquiry, question-driven meeting design, and techniques for using questions to lead without dictating. Use when meetings produce compliance instead of commitment, when teams wait for answers instead of generating them, when a leader talks more than they listen, when preparing for difficult or ambiguous decisions, or when building a culture of curiosity." +version: "1.0.0" +category: "leadership" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - questioning + - inquiry + - curiosity + - decision-making + - meetings + - coaching + - listening + - facilitation +related_skills: + - leader-self-reflection + - leadership-voice-and-presence + - leadership-style-adaptation + - ai-era-leadership + - grow-model + - appreciative-inquiry + - radical-candor +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Strategic Questioning + +Most leaders talk 80% of the time and listen 20%. The most effective ones reverse the ratio. + +This is not a call for silence, nor a suggestion that leaders abdicate their responsibility to decide. It is a recognition that the instrument leaders reach for first -- the declarative statement, the directive, the answer -- is often the wrong tool for the job. Statements close conversations. Questions open them. Statements transfer information. Questions generate it. Statements produce compliance. Questions produce ownership. The leader who defaults to answering is doing the intellectual work that their team should be doing, solving problems that their team should be defining, and building a dependency that feels like efficiency but functions as a constraint on every person in the room. + +Strategic questioning is not Socratic theatre -- asking questions to which you already know the answer so that others can arrive at your predetermined conclusion. It is the genuine use of inquiry as a leadership instrument: to surface information you do not possess, to challenge assumptions (including your own), to inspire thinking that exceeds what you could produce alone, and to build the collective intelligence of the organisation rather than centralising it in one person. + +--- + +## The Practice + +### Five Questions Every Leader Should Ask Repeatedly + +These are not one-time inquiries. They are recurring instruments -- questions that produce different and valuable information each time they are deployed, precisely because the context surrounding them is always changing. + +**1. "How can I help?"** +The impulse to support others is admirable; the execution is usually wrong. Leaders swoop in with solutions before the problem is defined. Asking "How can I help?" forces the other person to articulate what they actually need -- which is the first step toward owning and solving the problem themselves. The question is a gift disguised as an offer: it transfers agency back to the person who should have it. + +**2. "Wait, what?"** +A deceleration question. It prevents premature conclusions, interrupts groupthink, and creates space for understanding. When something sounds too easy, too obvious, or slightly off, "Wait, what?" invites the speaker to slow down, explain their reasoning, and revisit their assumptions. It is the shortest path from reaction to comprehension. + +**3. "I wonder why...?"** +The curiosity question. Wondering aloud why something exists in its current form is the first step in overcoming the institutional inertia that stifles growth. "Because we have always done it that way" is not an answer; it is a confession that no one has asked the question recently. And "I wonder why?" inevitably leads to its more powerful successor: "I wonder if things could be done differently?" + +**4. "Couldn't we at least...?"** +The progress question. In polarised discussions where consensus feels impossible and positions have hardened, this question finds the minimum viable agreement. "Couldn't we at least agree on some basic principles?" or "Couldn't we at least begin, and reevaluate at a later time?" It moves conversations from deadlock to movement, even if the movement is small. + +**5. "What truly matters?"** +The clarity question. Applicable to sensitive personnel decisions, complex strategic choices, and personal career dilemmas alike. This question cuts through the noise of competing considerations and forces a return to first principles. It is as useful in a board meeting as it is during a solitary walk. + +### The Art of Context-Rich Inquiry + +Not all questions are created equal. A question that demonstrates preparation, domain knowledge, and awareness of the broader landscape produces qualitatively different responses from a generic one. + +**Generic:** "What is our South America strategy?" +**Context-rich:** "I read that our top competitor is expanding in Brazil this year. How should that affect our South America strategy?" + +**Generic:** "What channels do you want to expand?" +**Context-rich:** "I would like to use my experience in Fortune 500 marketing to support your growth. What does your marketing department want to expand?" + +The first version requests information. The second generates a conversation. Context-rich questions signal respect for the other person's time, demonstrate that you have done the work, and invite expertise rather than summaries. + +### Questions That Inspire Rather Than Interrogate + +There is a category of question designed not to extract information but to expand the boundaries of what a team considers possible. + +**Narrow:** "How can we improve customer response times by 10%?" +**Expansive:** "What unmet customer needs could be the basis of an entirely new business?" + +**Narrow:** "You've mentioned you want to improve employee satisfaction. What are your next steps?" +**Expansive:** "Studies show that engagement is a better predictor of performance than satisfaction. How can we tackle a number of the factors that contribute to engagement?" + +Broad, ambitious questions demonstrate that the leader's horizon extends beyond incremental improvement. They invite employees to participate in setting goals, not merely executing them. And they contribute to a culture where questioning is valued and curiosity is modelled from the top. + +### Question-Driven Meeting Design + +The typical meeting agenda lists topics: "Budget problems," "Customer response times," "Q3 hiring." These labels describe subjects but provide no direction. Converting them to questions transforms meeting structure: + +- "Budget problems" becomes "How will we reduce spending by $100K this year?" +- "Customer response times" becomes "How can we reduce customer response times by 25%?" +- "Q3 hiring" becomes "Which three roles will have the greatest impact on our Q3 targets?" + +Questions accomplish three things that topic labels do not: they focus the group on outcomes, they clarify who should attend (whose expertise is needed to answer this question?), and they provide a natural end point -- the meeting is done when the questions are answered. + +### The Clarifying Power of One Question + +Leadership is filled with decisions where every option has a downside. The paralysis of multi-dimensional analysis -- weighing political implications, financial trade-offs, personal consequences -- can trap leaders in endless deliberation. In these moments, one question cuts through the complexity: "What is best for the organisation?" + +This is not a magic formula. But it accomplishes what more elaborate analytical frameworks sometimes fail to do: it lifts the leader above personal stakes, departmental politics, and short-term comfort to consider the systemic interest. Especially in difficult personnel decisions, where emotion and empathy argue for one course while organisational health argues for another, this question provides a clarifying anchor. + +--- + +## Prompts + +**Prompt 1 -- Question Audit:** +> Analyse the last five important conversations or meetings I led. For each, I will describe what I said and asked: [describe each interaction]. Calculate my statement-to-question ratio across all five. Identify moments where a question would have been more effective than the statement I made. For each identified moment, suggest the specific question I should have asked and explain what it would have produced that my statement did not. + +**Prompt 2 -- Meeting Redesign:** +> Here is the agenda for my upcoming [meeting type]: [paste agenda]. Convert each agenda item from a topic label to a question that focuses the discussion on a specific outcome. For each question, recommend: who should attend to answer it, how much time it needs, and what a good answer looks like. Then suggest an opening question for the meeting that sets the tone for inquiry-driven discussion. + +**Prompt 3 -- Questioning Repertoire Builder:** +> I lead a [team type] team of [number] people in [function/industry]. Generate a repertoire of 15 powerful questions organised by context: (a) one-on-one meetings, (b) team brainstorming sessions, (c) crisis situations, (d) strategic planning, and (e) performance conversations. Each question should be open-ended, context-aware, and designed to generate insight rather than confirm what I already believe. Explain the strategic purpose behind each question. + +**Prompt 4 -- Difficult Decision Facilitation:** +> I am facing a decision where every option has significant trade-offs: [describe the decision, the options, and the competing considerations]. Rather than analysing the options directly, help me develop a sequence of questions that I can use to facilitate my team's thinking about this decision. The questions should progressively narrow from broad exploration to specific recommendation, and should include at least one question that challenges my likely preference. + +--- + +## Use Cases + +**Idea-Stage Founder Replacing Solutions with Questions in Customer Discovery** +A founder conducting customer interviews consistently falls into the trap of pitching rather than listening. Every customer pain point triggers an explanation of how the product will solve it. The intervention: replace every solution statement with a question. "How do you currently handle this?" instead of "Our product does this." "What would a good solution look like to you?" instead of "Here is what we are building." The ratio shifts from 80% talking / 20% listening to 30% asking / 70% listening. Customer insights triple. Three assumptions the founder held about the market prove wrong -- discoveries that would have remained hidden under the weight of premature answers. + +**Growth-Stage VP Whose Team Has Stopped Innovating** +A VP of Product at a 120-person company runs efficient, well-structured meetings. Decisions are made quickly. Execution is reliable. Innovation has flatlined. The diagnosis: the VP's meetings are organised around directives and status updates. No space exists for exploratory thinking. The intervention: restructure one meeting per week as a "question-only" session where the VP is permitted only to ask, never to tell. The first two sessions are uncomfortable. By the fourth, a junior product manager proposes an approach to a customer segment that the VP had not considered. It becomes the company's fastest-growing feature line. + +**Scale-Stage CEO Navigating a Board Disagreement** +A CEO faces a split board on a major acquisition. Three directors favour the deal; two oppose it. Arguments have hardened; positions are entrenched. The CEO introduces "Couldn't we at least...?" to break the deadlock. "Couldn't we at least agree on the criteria by which we would judge this acquisition's success?" This meta-question shifts the conversation from positions to principles. The board agrees on five success criteria. When the acquisition is evaluated against those criteria, the path forward becomes evident -- not because anyone changed their mind, but because the question reframed what "agreement" required. + +--- + +## Anti-Patterns + +1. **Socratic Theatre.** Asking questions to which you already know the answer, guiding the team through a choreographed journey to your predetermined conclusion. Teams detect this within minutes. It produces cynicism rather than ownership, because the exercise signals that the leader's mind is already made up. + +2. **The Question Barrage.** Asking so many questions in rapid succession that the conversation becomes an interrogation rather than an inquiry. Effective questioning requires silence after the question -- space for the other person to think, formulate, and respond without pressure. + +3. **The Question That Is Actually a Statement.** "Don't you think we should launch in Q3?" is not a question. It is a directive wearing a question mark as a disguise. Genuine questions do not contain the answer. + +4. **Questioning Without Listening.** Asking excellent questions and then failing to hear, process, or act on the answers. Teams quickly learn whether questions are genuine invitations or performative rituals. If answers consistently produce no change, the questions stop generating honest responses. + +5. **Replacing All Direction with Questions.** Some situations require clear, unambiguous direction -- a crisis, a safety issue, a legal obligation. The leader who responds to "The server is down" with "What do you think we should do?" has confused inquiry with abdication. Strategic questioning supplements directive leadership; it does not replace it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Customer discovery | Questions are the primary tool for validating whether a problem exists, how severe it is, and whether anyone will pay for a solution. The founder who tells more than they ask during customer discovery will build the wrong product. | +| Validation | Assumption testing | The questions shift from "What is the problem?" to "Are our assumptions about the solution correct?" Inquiry targets the riskiest hypotheses and seeks disconfirming evidence rather than validation. | +| Early Traction | Team empowerment | As the first team forms, the founder's questions set the cultural norm. Teams that observe their leader asking rather than telling develop the habit of inquiry themselves. The ratio of questions to directives in the leader's communication directly predicts the team's creative output. | +| Growth | Meeting and decision architecture | At growth stage, meetings multiply and decision quality becomes the bottleneck. Question-driven agendas, structured inquiry processes, and the "What is best for the organisation?" anchor become operational necessities. | +| Scale | Institutional inquiry culture | At scale, the leader's questioning practice must be taught to hundreds of managers. The question is no longer "Do I ask good questions?" but "Does the organisation reward curiosity and penalise premature certainty?" | + +--- + +## Output Template + +```markdown +# Strategic Questioning Assessment + +**Leader:** [Name] +**Context:** [Team/meeting/decision context] +**Date:** [Date] + +## Current Communication Ratio +- **Statements:** [Estimated %] +- **Questions:** [Estimated %] +- **Target ratio:** [e.g., 40% statements / 60% questions] + +## Five Essential Questions: Application Plan +| Question | Where I Will Use It | Frequency | Expected Impact | +|----------|--------------------|-----------|-----------------| +| "How can I help?" | [Context] | [Daily/Weekly] | [Impact] | +| "Wait, what?" | [Context] | [As needed] | [Impact] | +| "I wonder why...?" | [Context] | [Weekly] | [Impact] | +| "Couldn't we at least...?" | [Context] | [As needed] | [Impact] | +| "What truly matters?" | [Context] | [Monthly] | [Impact] | + +## Meeting Agenda Conversion +| Current Topic Label | Converted to Question | Success Criteria | +|--------------------|----------------------|------------------| +| [Topic] | [Question] | [What a good answer looks like] | + +## Questioning Repertoire +### One-on-Ones +1. [Question and purpose] +2. [Question and purpose] + +### Team Sessions +1. [Question and purpose] +2. [Question and purpose] + +### Strategic Decisions +1. [Question and purpose] +2. [Question and purpose] + +## Commitments +- [ ] Replace [number] directives with questions this week +- [ ] Convert next meeting agenda to question format +- [ ] Track statement-to-question ratio for 30 days +``` + +--- + +## Related Skills + +- **[GROW Model](../../content/skills/frameworks/grow-model.md)** -- The GROW coaching framework is built entirely on sequential questioning; this skill provides the broader leadership context for inquiry, GROW provides the structured coaching conversation. +- **[Appreciative Inquiry](../../content/skills/frameworks/appreciative-inquiry.md)** -- Appreciative Inquiry applies strategic questioning specifically to organisational development, focusing on what works rather than what fails. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Radical Candor's "solicit criticism before giving it" principle is a specific application of strategic questioning: using inquiry to build trust before delivering challenge. +- **[Leader Self-Reflection](../../content/skills/leadership/leader-self-reflection.md)** -- The seven diagnostic questions in self-reflection are the leader's application of strategic questioning to themselves. +- **[Leadership Voice and Presence](../../content/skills/leadership/leadership-voice-and-presence.md)** -- The curiosity dimension of leadership voice is the channel through which strategic questioning operates in daily communication. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The problem-definition discipline shares the same premise: asking better questions matters more than generating faster answers. diff --git a/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md b/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md deleted file mode 120000 index 271ba4b..0000000 --- a/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/strategic-thinking-and-alignment.md \ No newline at end of file diff --git a/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md b/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md new file mode 100644 index 0000000..19d4a7b --- /dev/null +++ b/plugins/foreman/skills/strategic-thinking-and-alignment/SKILL.md @@ -0,0 +1,196 @@ +--- +name: "strategic-thinking-and-alignment" +description: "Develops the daily habits and communication practices that separate strategic leaders from operational ones. Covers carving out time for strategic thinking, communicating strategic changes effectively, building organisational alignment, challenging the status quo, and fostering competitive innovation without duplicating formal strategy frameworks. Use when feeling trapped in operational detail, struggling to communicate a strategic shift, discovering that teams are pursuing divergent goals, preparing for strategy offsites, or sensing that the organisation is coasting on inertia." +version: "1.0.0" +category: "leadership" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - strategy + - alignment + - vision + - competitive-thinking + - strategic-intent + - communication + - status-quo + - change-leadership +related_skills: + - porters-five-forces + - blue-ocean-strategy + - art-of-war + - scenario-planning + - managing-up + - delegation-and-empowerment +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Strategic Thinking and Alignment + +Most leaders operate at 500 feet when strategy requires 30,000. They spend their days in the weeds of execution -- answering emails, attending stand-ups, unblocking teams -- and mistake this operational busyness for strategic leadership. The altitude problem is not one of intelligence but of habit. Strategic thinking is not a talent reserved for the C-suite; it is a daily practice that most leaders never develop because no one protects the time for it, least of all themselves. The formal frameworks exist elsewhere in this library -- Porter's Five Forces, Blue Ocean Strategy, the strategic lessons of Sun Tzu. This skill concerns something more fundamental: how a leader builds the muscle of strategic thought into the rhythm of ordinary days, and how they translate that thought into organisational alignment. + +--- + +## The Framework + +### Part 1: The Daily Practice of Strategic Thinking + +Strategic thinking is not what happens in annual offsites. It is what happens in the fifteen minutes before a meeting, the walk between the office and the car, the deliberate pause before replying to a Slack message with a tactical answer when a strategic one is needed. + +**Five habits that build strategic altitude:** + +**Habit 1: Schedule thinking time as ruthlessly as meetings.** +Block recurring calendar time -- even thirty minutes -- with no agenda other than to think about the business from above. No inbox. No Slack. No "quick calls." The moment this time becomes negotiable, it disappears. Most leaders protect their meeting commitments but sacrifice their thinking commitments without hesitation, which is precisely backwards. + +**Habit 2: Play CEO for a day.** +Periodically, view every meeting, project, and decision from the vantage of the person running the entire organisation. CEOs must balance conflicting needs, weigh trade-offs across functions, and prioritise long-term positioning over short-term comfort. Asking "How would the CEO see this?" is not an exercise in presumption; it is an exercise in perspective. + +**Habit 3: Think like the competitor.** +Run a simple exercise: list your company's strengths, then argue that each is actually a vulnerability. List your weaknesses, then argue that each conceals an opportunity. Repeat for your top competitor. The goal is not to reach a conclusion but to develop the cognitive flexibility that strategic thinking demands. Companies that only see their strengths as strengths are already being outflanked. + +**Habit 4: Separate competition from strategy.** +The instinct to beat rivals by improving existing products is powerful and often wrong. The strategies that generate disproportionate returns tend to create new market spaces rather than fight over existing ones. When leading brainstorming or innovation sessions, resist the gravitational pull toward incremental improvement. Push the team toward questions no competitor is asking. + +**Habit 5: Set strategic intent, not just strategic plans.** +Plans are defensive; intent is offensive. Strategic intent means setting goals that exceed current resources and capabilities -- not recklessly, but deliberately. It accelerates organisational learning by forcing the company to compete in innovative ways rather than merely sustaining current advantages. The essence of strategy is creating tomorrow's competitive advantages faster than competitors can mimic today's. + +### Part 2: Communicating Strategic Change + +The gap between a leader's strategic clarity and the organisation's strategic understanding is almost always wider than the leader believes. Two specific failures drive this gap: + +**Failure 1: Expressing change in terms of tasks, not outcomes.** +Leaders who say "We need to migrate to platform X by Q3" have communicated a task. Leaders who say "We need to be able to serve enterprise customers with 99.99% uptime by Q3, and migrating to platform X is how we get there" have communicated an outcome. The difference determines whether teams execute mechanically or with judgment. + +**Failure 2: Understating the magnitude of change.** +Leaders rarely make clear the full extent of what they are asking for. A "strategic pivot" described in one slide at an all-hands meeting does not convey the depth of behavioural, structural, and cultural change required. When followers report that their leaders "weren't clear enough," they usually mean the leader communicated the what without the why, the how, or the how much. + +### Part 3: Building Organisational Alignment + +Alignment is not a state to be achieved; it is a continuous dialogue to be maintained. The assumption that employees share a leader's understanding of strategy is, in the words of researchers, "a dangerous mistake." Misalignment produces politics, infighting, unproductive meetings, and serious obstacles to value creation. + +**The alignment discipline has three components:** + +1. **Co-creation over announcement.** Senior leaders are not the ones who implement strategy -- managers and frontline employees are. Strategy cannot be handed down like a decree; it requires input, feedback, and genuine listening across the organisation. Building consensus takes more than saying "Here's what you should do." + +2. **Continuous recalibration.** Alignment is not a one-time goal achieved in a strategy offsite and sustained by inertia. It is a recurring conversation about what is important and what is prioritised. Managers take ownership of strategy only when they are convinced of its value -- and conviction requires ongoing engagement, not a single presentation. + +3. **Vision translation at every level.** Shaping vision is not the exclusive province of senior executives. Leaders at every level can contribute by translating the company's mission for their teams, developing frontline strategies that connect to the broader arc, and identifying where their team's work fits in the long-term picture. + +### Part 4: Challenging the Status Quo + +New and experienced managers alike fall into the trap of believing that their primary job is to keep things running smoothly. Operational stability is necessary but insufficient. Part of leadership is identifying and initiating changes that enhance team performance -- even when those changes challenge existing processes, structures, or the people responsible for them. + +The leader who sees a flawed system and waits for someone else to fix it has abdicated a core responsibility. Using internal networks and informal authority to advocate for change is not insubordination; it is leadership in its most practical form. + +--- + +## Prompts + +**Prompt 1 -- Strategic Altitude Audit:** +> Assess how I currently spend my time as a leader. My typical week includes [describe meetings, tasks, and responsibilities]. What percentage of my time is spent at operational altitude versus strategic altitude? Identify three specific changes to my weekly schedule that would increase strategic thinking time without abandoning operational responsibilities. Be realistic -- I cannot simply "stop doing" operational work. + +**Prompt 2 -- Competitive Reversal Exercise:** +> My company's top three strengths are [list them]. Our top three weaknesses are [list them]. Our primary competitor is [describe]. Walk me through the competitive reversal exercise: argue that each of our strengths is actually a vulnerability, and each weakness conceals an opportunity. Then do the same for the competitor. Identify the strategic insight that emerges from this reframing. + +**Prompt 3 -- Alignment Diagnostic:** +> I suspect that my team [or organisation] is not aligned on our strategy. The strategy as I understand it is [describe]. Diagnose potential alignment gaps by asking me questions about how different groups interpret the strategy, what metrics they optimise for, and where I have seen conflicting priorities. Then recommend a process for recalibrating alignment without creating a bureaucratic overhead. + +**Prompt 4 -- Strategic Change Communication:** +> I need to communicate a strategic change to my organisation. The change is [describe]. Draft a communication plan that articulates the change in terms of outcomes (not tasks), makes clear the full magnitude of what is being asked, addresses the "why" and "how much" alongside the "what," and identifies which audiences need which level of detail. Include a framework for follow-up conversations that reinforce the message over time. + +--- + +## Use Cases + +**Early-Traction Startup Stuck in Feature-Shipping Mode** + +A founding team of engineers ships features at extraordinary velocity but has no strategic framework for deciding which features to build. Every sprint is reactive -- driven by the loudest customer request or the most recent competitor launch. The CEO introduces a weekly thirty-minute "altitude session" with no agenda other than the question: "If we were our competitor, how would we attack us?" Within a month, the team identifies that their strongest feature is also their greatest vulnerability -- a single-customer dependency that a competitor could exploit by offering a multi-tenant alternative. The roadmap shifts from reactive feature shipping to deliberate platform strategy. + +**Growth-Stage Company with Alignment Fractures** + +A 200-person company completes a strategy offsite and the leadership team leaves aligned. Three months later, the product team is optimising for user engagement, the sales team is optimising for enterprise deal size, and the customer success team is optimising for retention -- three legitimate goals that are pulling in different directions. The CEO diagnoses the alignment gap using continuous recalibration: monthly cross-functional meetings where each team presents not just their metrics but how those metrics serve the strategy. Within two quarters, the teams converge on a shared definition of the "ideal customer" that aligns all three functions. + +**Scale-Stage Division Leader Challenging an Entrenched Process** + +A VP discovers that the company's procurement process -- designed for a 50-person company -- is adding six weeks to every vendor engagement in a now-500-person organisation. Previous VPs accepted this as institutional friction. This VP uses informal authority and cross-functional relationships to document the cost of delay, build a coalition of affected department heads, and present a redesigned process to the COO. The status quo changes not because someone at the top mandated it, but because a leader at the middle refused to wait for permission to lead. + +--- + +## Anti-Patterns + +1. **Confusing strategic thinking with strategic planning.** Planning is a periodic, structured exercise. Thinking is a daily habit. A leader who attends every strategy offsite but never pauses to question assumptions between offsites is a strategic planner, not a strategic thinker. + +2. **Re-teaching frameworks instead of practising them.** Knowing Porter's Five Forces or Blue Ocean Strategy is not the same as habitually applying strategic lenses to daily decisions. This skill is about the practice, not the theory. Leaders who can recite frameworks but cannot explain how last Tuesday's product decision connects to competitive positioning have knowledge without application. + +3. **Assuming alignment exists because no one is openly disagreeing.** Silence is not alignment. Teams that appear harmonious may simply be pursuing their own interpretations of the strategy without conflict -- because they never interact deeply enough to discover their divergence. + +4. **Communicating strategy once and expecting it to stick.** A single all-hands presentation, no matter how well-crafted, does not create alignment. Strategy must be repeated, translated, and reinforced through every channel and at every level until it becomes ambient -- the air the organisation breathes rather than a document it filed. + +5. **Protecting the status quo under the guise of stability.** Leaders who describe inertia as "not fixing what isn't broken" are often avoiding the discomfort of change rather than making a strategic judgment. The status quo is never neutral; it is a choice that compounds daily. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Building the habit from scratch | Founders must carve out strategic thinking time before operational demands consume every hour. The habit is easier to establish early than to retrofit later. | +| Growth | Alignment across functions | As teams multiply, strategic alignment becomes the primary challenge. The leader's role shifts from thinking strategically alone to ensuring the entire organisation thinks strategically together. | +| Scale | Institutional strategic discipline | Strategic thinking must be embedded in processes, not dependent on individuals. Strategy reviews, competitive intelligence functions, and alignment rituals replace ad-hoc leadership habits. | + +The altitude problem intensifies with scale. A founder at early traction can hold the entire strategy in their head. A CEO at scale cannot -- and the gap between the leader's strategic clarity and the organisation's strategic understanding grows with every hire, every office, and every product line. + +--- + +## Output Template + +```markdown +# Strategic Thinking and Alignment Assessment + +## Current Altitude Distribution +| Activity Type | Hours/Week | % of Time | Strategic Value | +|--------------|-----------|-----------|-----------------| +| Operational (execution, firefighting) | [Hours] | [%] | [Low/Med/High] | +| Tactical (planning, coordination) | [Hours] | [%] | [Low/Med/High] | +| Strategic (thinking, positioning, vision) | [Hours] | [%] | [Low/Med/High] | + +## Strategic Thinking Habits +- **Scheduled thinking time:** [Yes/No -- frequency and duration] +- **Competitive perspective practice:** [How often, what format] +- **Status quo challenges initiated:** [Recent examples] + +## Alignment Assessment +| Group/Team | Their interpretation of strategy | Aligned with leadership intent? | Gap description | +|-----------|--------------------------------|-------------------------------|-----------------| +| [Team 1] | [Their version] | [Yes/Partial/No] | [Description] | +| [Team 2] | [Their version] | [Yes/Partial/No] | [Description] | + +## Strategic Communication Plan +- **Core message (outcome-framed):** [What we are trying to achieve and why] +- **Magnitude of change:** [What must change in behaviour, structure, and culture] +- **Audiences and tailored messages:** [Which groups need which framing] +- **Reinforcement cadence:** [How and when the message will be repeated] + +## 90-Day Strategic Discipline Plan +| Month | Habit to Build | Alignment Action | Status Quo Challenge | +|-------|---------------|-----------------|---------------------| +| 1 | [Specific habit] | [Specific action] | [Specific challenge] | +| 2 | [Specific habit] | [Specific action] | [Specific challenge] | +| 3 | [Specific habit] | [Specific action] | [Specific challenge] | +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Provides the analytical framework for competitive assessment; this skill addresses how to make such analysis a daily habit rather than an annual exercise. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- The formal methodology for creating uncontested market space; this skill focuses on the daily discipline of looking beyond competitive imitation. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- A structured approach to thinking about alternative futures; strategic thinking as a daily habit is the precondition for effective scenario work. +- **[Managing Up](../../content/skills/leadership/managing-up.md)** -- Strategic visibility with senior leaders depends on having genuine strategic thinking to display; these two skills are deeply intertwined. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- Leaders cannot find time for strategic thinking without delegating operational work effectively. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Provides the analytical lens for understanding feedback loops and emergent behaviour that strategic altitude requires to see beyond isolated competitive moves. diff --git a/plugins/foreman/skills/swot-pest-analysis/SKILL.md b/plugins/foreman/skills/swot-pest-analysis/SKILL.md deleted file mode 120000 index 29cd7bd..0000000 --- a/plugins/foreman/skills/swot-pest-analysis/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/swot-pest-analysis.md \ No newline at end of file diff --git a/plugins/foreman/skills/swot-pest-analysis/SKILL.md b/plugins/foreman/skills/swot-pest-analysis/SKILL.md new file mode 100644 index 0000000..7163151 --- /dev/null +++ b/plugins/foreman/skills/swot-pest-analysis/SKILL.md @@ -0,0 +1,215 @@ +--- +name: "swot-pest-analysis" +description: "Conducts integrated SWOT (Strengths, Weaknesses, Opportunities, Threats) and PEST (Political, Economic, Social, Technological) strategic analysis. Generates actionable strategies through the TOWS matrix by crossing internal capabilities with external forces. Use when evaluating market entry, preparing board strategy sessions, assessing competitive positioning, scanning the macro environment for regulatory or economic shifts, or generating evidence-backed strategic options." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - strategic-analysis + - environmental-scanning + - competitive-positioning + - opportunity-assessment + - risk-mapping +related_skills: + - porters-five-forces + - blue-ocean-strategy + - balanced-scorecard + - growth-share-matrix +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# SWOT & PEST Analysis + +A confession: nearly every business plan, pitch deck, and strategy retreat includes a SWOT analysis. Almost none of them do it well. The framework has become so ubiquitous that it has degenerated into a ritual -- four quadrants filled with vague platitudes, then promptly ignored. The same fate has befallen PEST analysis, its macro-environmental counterpart. Yet when applied with intellectual rigour rather than checkbox compliance, these two tools remain among the most powerful diagnostics available to a founder trying to understand where a business actually stands versus where it imagines itself to be. + +SWOT (Strengths, Weaknesses, Opportunities, Threats) was formalised in the 1960s at Stanford Research Institute. PEST (Political, Economic, Social, Technological) emerged from Francis Aguilar's 1967 work on scanning the business environment. Together, they form a layered lens: PEST examines the world around you; SWOT examines you within that world. The error most practitioners commit is treating them as separate exercises rather than an integrated system. + +--- + +## The Framework + +### SWOT: The Internal-External Matrix + +SWOT divides analysis across two dimensions: internal vs. external, and helpful vs. harmful. + +| | **Helpful** | **Harmful** | +|---|---|---| +| **Internal** (within your control) | **Strengths** -- Capabilities, assets, advantages you genuinely possess | **Weaknesses** -- Deficiencies, gaps, vulnerabilities you must confront | +| **External** (outside your control) | **Opportunities** -- Market shifts, trends, unmet needs you could exploit | **Threats** -- Competitive moves, regulations, disruptions that endanger you | + +The quality of a SWOT depends entirely on the quality of inputs. A strength is only a strength if customers or partners actually value it. A threat is only a threat if it could materially affect your trajectory within a relevant timeframe. + +**The SWOT Rigour Test:** For each item listed, ask three questions: +1. **Evidence:** What data supports this claim? (Not opinion -- data.) +2. **Materiality:** Does this factor significantly affect revenue, growth, or survival? +3. **Actionability:** Can we do something specific about it within 90 days? + +If an item fails all three, it does not belong in the matrix. + +### PEST: The Macro-Environmental Scan + +PEST widens the aperture to forces that shape entire industries, not just individual firms. + +| Factor | What to Analyse | Entrepreneurial Relevance | +|--------|----------------|--------------------------| +| **Political** | Regulation, taxation, trade policy, government stability, labour laws | Can a policy change kill your business model? Can it create a new one? | +| **Economic** | Interest rates, inflation, consumer spending, exchange rates, credit availability | Are your unit economics sustainable in a downturn? What happens when funding dries up? | +| **Social** | Demographics, cultural attitudes, lifestyle shifts, education levels, workforce trends | Is your target market growing or shrinking? Are behavioural trends moving toward or away from your offering? | +| **Technological** | Innovation pace, automation, digital infrastructure, R&D activity, platform shifts | Are you building on rising or declining technology? Could a new platform render your product irrelevant? | + +Some practitioners extend PEST to PESTLE (adding Legal and Environmental as separate categories). The extension has merit when regulatory or sustainability factors carry distinct weight -- as they increasingly do. + +### The Integration: PEST Feeds SWOT + +The correct sequence is PEST first, then SWOT. Macro-environmental forces identified through PEST analysis become inputs for the Opportunities and Threats quadrants of SWOT. This prevents the common failure of populating SWOT with nothing but competitor comparisons while ignoring the larger forces reshaping the playing field. + +``` +PEST Analysis (Macro Environment) + | + v +Opportunities & Threats (SWOT External Row) + + +Strengths & Weaknesses (Internal Audit) + | + v +Strategic Options (SO, WO, ST, WT strategies) +``` + +**The TOWS Matrix** converts SWOT from description into prescription: + +| | **Strengths** | **Weaknesses** | +|---|---|---| +| **Opportunities** | **SO Strategies:** Use strengths to capture opportunities | **WO Strategies:** Overcome weaknesses to capture opportunities | +| **Threats** | **ST Strategies:** Use strengths to neutralise threats | **WT Strategies:** Minimise weaknesses and avoid threats | + +This TOWS conversion is where most SWOT analyses fail. They stop at description. The entire point is to generate strategic options. + +--- + +## Prompts + +**Prompt 1 -- PEST Environmental Scan:** +> "Conduct a PEST analysis for a [industry/sector] startup operating in [geography]. For each of the four factors (Political, Economic, Social, Technological), identify the three most significant forces currently affecting startups in this space. Rate each force as accelerating or decelerating our market opportunity, and explain the mechanism through which it operates." + +**Prompt 2 -- Honest SWOT with Evidence:** +> "Generate a SWOT analysis for my business: [brief description, stage, key metrics]. For each item you list, provide the evidence standard -- what data point or observable fact supports this classification? Flag any items that are assumptions rather than evidence-backed claims. Limit each quadrant to the five most material factors." + +**Prompt 3 -- TOWS Strategy Generation:** +> "Given this SWOT matrix: Strengths: [list], Weaknesses: [list], Opportunities: [list], Threats: [list] -- generate the TOWS strategy matrix. For each of the four strategy types (SO, WO, ST, WT), propose two specific, actionable initiatives with a 90-day implementation horizon. Prioritise by impact-to-effort ratio." + +**Prompt 4 -- Competitive SWOT Comparison:** +> "Create parallel SWOT analyses for my company [name/description] and our top two competitors [names/descriptions]. Identify where our strengths overlap with their weaknesses (attack vectors) and where their strengths overlap with our weaknesses (vulnerability zones). Recommend three strategic moves based on the comparison." + +**Prompt 5 -- PEST Scenario Planning:** +> "Using PEST analysis for [industry], construct two scenarios: one where macro trends converge favourably for our business model, and one where they converge unfavourably. For each scenario, identify the three earliest warning signals an entrepreneur should monitor, and the contingency response for the unfavourable case." + +--- + +## Use Cases + +**Pre-Seed Founder Evaluating Market Entry** + +A solo founder developing a fintech lending product for small businesses in Southeast Asia uses PEST to map the regulatory environment across three target markets -- Singapore, Indonesia, and the Philippines. The analysis reveals that Indonesia's new financial services authority regulations create a narrow window of opportunity for licensed digital lenders, while the Philippines' fragmented banking infrastructure presents a social-technological gap. This PEST output feeds into a SWOT that positions the founder's technical background (strength) against the lack of local regulatory relationships (weakness), enabling a focused market-entry strategy that targets Indonesia first. + +**Series A Company Preparing for Board Strategy Session** + +A B2B SaaS company with $2M ARR and 18 months of runway conducts an integrated PEST-SWOT before its annual strategy review. The PEST reveals that an economic slowdown is tightening enterprise software budgets (Economic threat), but remote-work normalisation is increasing demand for their collaboration tool category (Social opportunity). The TOWS matrix produces four strategy streams: accelerate self-serve conversion to capture budget-conscious buyers (SO), build integrations with dominant platforms to offset brand weakness (WO), lock in annual contracts before renewal budgets shrink (ST), and reduce burn by pausing the planned geographic expansion (WT). The board receives a single-page TOWS summary instead of the usual 30-slide deck. + +**Growth-Stage E-Commerce Brand Facing Regulatory Shift** + +An e-commerce company selling health supplements across the EU confronts new regulations on health claims in advertising. PEST analysis surfaces the political factor early. SWOT reveals that the company's in-house regulatory expertise (strength) and established brand trust (strength) position it to capture market share from smaller competitors who lack resources to comply (opportunity), while the same regulation threatens its highest-margin product line due to specific ingredient restrictions (threat). The TOWS strategy: reformulate the restricted products while marketing regulatory compliance as a brand differentiator. + +--- + +## Anti-Patterns + +**The Brainstorm Dump.** Filling SWOT quadrants during a whiteboard session without evidence, data, or customer input. Every item should be substantiated. "Great team" is not a strength -- "92% employee retention with three senior hires from [relevant company]" is. + +**PEST as Academic Exercise.** Producing a comprehensive PEST analysis that reads like a university essay and sits in a drawer. Each factor must connect to a specific strategic implication. If a PEST finding does not change a decision, it does not belong in the analysis. + +**Ignoring the Negatives.** Human psychology favours strengths and opportunities over weaknesses and threats. The most valuable quadrants are often W and T, because they reveal where the business is exposed. Entrepreneurs who produce lopsided analyses with twelve strengths and two weaknesses are engaged in self-deception, not strategy. + +**Static Analysis.** Conducting SWOT/PEST once and treating the output as permanent truth. Markets shift. Competitors move. Regulations change. These frameworks demand quarterly revisiting at minimum, monthly during periods of rapid change. + +**Confusing Internal and External.** Placing items in the wrong row is surprisingly common. "Strong competition" is not a weakness -- it is a threat. "Growing market" is not a strength -- it is an opportunity. The internal/external distinction is not cosmetic; it determines whether you can act on the factor directly or must respond to it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Validate whether the opportunity is real | PEST is primary -- assess whether macro forces support the concept before investing in internal analysis | +| Validation | Test assumptions in each quadrant | Every SWOT item should map to a hypothesis being tested through customer discovery | +| Early Traction | Identify competitive vulnerabilities | Focus shifts to Threats and Weaknesses as competitors notice your traction | +| Growth | Inform resource allocation | TOWS strategies drive quarterly planning; PEST monitors for regulatory and economic headwinds | +| Scale | Support geographic and market expansion | Run separate PEST analyses per new market; SWOT becomes a portfolio-level tool across business units | + +At the idea stage, founders often lack the internal data to populate Strengths and Weaknesses with any rigour. Starting with PEST is both more honest and more productive -- it answers the threshold question of whether the external environment supports the business concept at all. + +By the growth stage, the danger is that SWOT becomes a political exercise where each department advocates for its priorities. Insist on external validation: customer data, market research, and competitor intelligence should drive the analysis, not internal opinions. + +--- + +## Output Template + +**Target Audience: Board / Investors** + +```markdown +# Strategic Position Assessment: [Company Name] +## Date: [Quarter/Year] + +### Macro-Environmental Context (PEST Summary) + +| Factor | Key Finding | Strategic Implication | Trend Direction | +|--------|-------------|----------------------|-----------------| +| Political | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Economic | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Social | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | +| Technological | [Finding] | [Implication] | [Accelerating/Stable/Decelerating] | + +### SWOT Matrix + +| | Helpful | Harmful | +|---|---------|---------| +| **Internal** | S1: [Evidence-backed strength] | W1: [Evidence-backed weakness] | +| | S2: [Evidence-backed strength] | W2: [Evidence-backed weakness] | +| | S3: [Evidence-backed strength] | W3: [Evidence-backed weakness] | +| **External** | O1: [Data-supported opportunity] | T1: [Data-supported threat] | +| | O2: [Data-supported opportunity] | T2: [Data-supported threat] | +| | O3: [Data-supported opportunity] | T3: [Data-supported threat] | + +### Strategic Options (TOWS) + +| Strategy Type | Initiative | Timeline | Expected Impact | +|---------------|-----------|----------|-----------------| +| SO (Strength + Opportunity) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| WO (Weakness + Opportunity) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| ST (Strength + Threat) | [Specific initiative] | [Q/Year] | [Measurable outcome] | +| WT (Weakness + Threat) | [Specific initiative] | [Q/Year] | [Measurable outcome] | + +### Recommended Priority Actions (Next 90 Days) +1. [Action] -- Owner: [Name] -- Success Metric: [Metric] +2. [Action] -- Owner: [Name] -- Success Metric: [Metric] +3. [Action] -- Owner: [Name] -- Success Metric: [Metric] +``` + +--- + +## Related Skills + +- **[Porter's Five Forces](../../content/skills/frameworks/porters-five-forces.md)** -- Provides the competitive intensity analysis that feeds into SWOT's Threats and Opportunities quadrants. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Builds on SWOT by asking not just where you stand, but where uncontested market space exists. +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Translates SWOT-derived strategies into measurable objectives across four performance dimensions. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- PEST identifies the driving forces that scenario planning uses as axes; SWOT reveals how the organization would perform under each resulting scenario. +- **[Systems Thinking](../../content/skills/frameworks/systems-thinking.md)** -- Systems thinking reveals how the factors identified in SWOT and PEST interact dynamically over time, preventing static analysis from producing brittle strategies. +- **[Strategic Thinking and Alignment](../../content/skills/leadership/strategic-thinking-and-alignment.md)** -- SWOT and PEST provide the analytical inputs; strategic thinking translates those inputs into coherent organizational direction and resource allocation. diff --git a/plugins/foreman/skills/systems-thinking/SKILL.md b/plugins/foreman/skills/systems-thinking/SKILL.md deleted file mode 120000 index 49d0746..0000000 --- a/plugins/foreman/skills/systems-thinking/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/systems-thinking.md \ No newline at end of file diff --git a/plugins/foreman/skills/systems-thinking/SKILL.md b/plugins/foreman/skills/systems-thinking/SKILL.md new file mode 100644 index 0000000..d2f9f98 --- /dev/null +++ b/plugins/foreman/skills/systems-thinking/SKILL.md @@ -0,0 +1,258 @@ +--- +name: "systems-thinking" +description: "Analyzes complex business problems through systems thinking by mapping causal loops, identifying reinforcing and balancing feedback dynamics, and diagnosing system archetypes like Fixes That Fail, Shifting the Burden, and Limits to Growth. Use when quick fixes keep backfiring, growth plateaus unexpectedly, departments optimize locally at the expense of the whole, or interventions produce unintended consequences across the organization." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - systems-dynamics + - feedback-loops + - complexity + - holistic-analysis + - causal-reasoning + - organisational-design +related_skills: + - balanced-scorecard + - kaizen-bpr + - swot-pest-analysis + - shamrock-organisation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Systems Thinking + +A startup lowers its prices to win market share. Sales volume surges. The support team, sized for the previous volume, becomes overwhelmed. Response times triple. Customer satisfaction collapses. Negative reviews proliferate. The sales team, now fighting a reputation problem, demands more marketing spend to overcome the brand damage. Margins tighten. The price cut that was supposed to accelerate growth has, through a chain of consequences no single decision-maker foresaw, created a crisis that threatens the company's survival. This is not bad luck. It is a system behaving exactly as its structure dictates. + +Peter Senge's *The Fifth Discipline* (1990) brought systems thinking into the management mainstream, though its roots extend to Jay Forrester's work at MIT in the 1950s and further back to cybernetics. The core insight is deceptively profound: the behaviour of any complex organisation is driven not by individual events or decisions but by the structure of relationships between its components. Change the events and the behaviour persists. Change the structure and the behaviour transforms. + +--- + +## The Framework + +### The Hierarchy of Understanding + +Systems thinkers operate at three levels, each more powerful than the last: + +**Level 1: Events** -- "What just happened?" +Most management operates here. Revenue dropped. A key hire quit. A competitor launched a new feature. Event-level thinking produces reactive responses: cut costs, make a counter-offer, rush a feature release. + +**Level 2: Patterns** -- "What trends are emerging?" +More sophisticated. Revenue has declined for three consecutive quarters. Turnover in engineering has risen from 8% to 22% over 18 months. The competitor has released three features in our core space in the past year. Pattern-level thinking produces adaptive responses: restructure the sales team, review compensation benchmarks, reassess competitive strategy. + +**Level 3: Systemic Structure** -- "What structure produces these patterns?" +The most powerful level. Revenue is declining because the product was optimised for early adopters who are now churning, and the features being built serve new customer segments that have lower lifetime value. Engineering turnover is rising because the technical debt accumulated during rapid growth makes the work unsatisfying, and the best engineers leave first. The competitor is targeting the same customer segment because both companies read the same market research. Structure-level thinking produces generative responses: redesign the product roadmap around retention, allocate 30% of engineering capacity to technical debt reduction, develop a differentiated positioning that avoids head-to-head competition. + +### Feedback Loops: The Engine of System Behaviour + +Two types of feedback loops drive all system dynamics: + +**Reinforcing Loops (R)** -- Amplify change in one direction. They produce growth or collapse. + +``` +Customer satisfaction rises + | + v +Word-of-mouth referrals increase --> New customers arrive + | | + v v +Revenue grows --> Investment in product --> Product quality improves + | + v +(Loop back to customer satisfaction) +``` + +Reinforcing loops create virtuous cycles or death spirals. The same structure that drives exponential growth, when reversed, drives exponential decline. + +**Balancing Loops (B)** -- Resist change and push toward equilibrium. They stabilise or constrain. + +``` +Company grows rapidly + | + v +Hiring accelerates --> New employees need training + | | + v v +Management bandwidth consumed --> Quality of decisions declines + | | + v v +Growth slows (balancing against the growth impulse) +``` + +Every entrepreneur has experienced balancing loops: the growth ceiling that appears just when momentum feels unstoppable. The ceiling is not external -- it is structural. + +### System Archetypes + +Senge identified recurring patterns that appear across industries and organisations: + +**Fixes That Fail** +A quick fix alleviates symptoms but creates side effects that eventually make the original problem worse. + +- Cause: Team is missing deadlines +- Quick Fix: Mandate overtime +- Side Effect (delayed): Burnout, turnover, knowledge loss +- Result: Team misses even more deadlines + +**Shifting the Burden** +A symptomatic solution undermines the ability to implement a fundamental solution. + +- Symptom: Customer complaints about product quality +- Symptomatic Solution: Increase customer support headcount +- Fundamental Solution: Fix the product defects at the source +- Burden Shift: The support team becomes so effective at managing complaints that the urgency to fix the product disappears + +**Limits to Growth** +A reinforcing process drives growth, but eventually triggers a balancing process that slows or stops it. + +- Growth Engine: Viral product adoption +- Limiting Factor: Server infrastructure cannot scale at the same rate +- Behaviour: Growth accelerates, then plateaus, then frustration drives users to alternatives + +**Tragedy of the Commons** +Multiple actors share a finite resource, each acting rationally in their own interest, collectively depleting the resource. + +- Shared Resource: Engineering team's time +- Individual Actors: Product managers from different business lines +- Behaviour: Each PM escalates priority of their requests; engineering becomes a bottleneck; everyone suffers + +### Causal Loop Diagrams + +The primary tool of systems thinking is the causal loop diagram -- a visual map of the cause-and-effect relationships that define a system's structure. + +Notation: +- Arrow: A causes B +- (+): A and B move in the same direction (A rises, B rises) +- (-): A and B move in opposite directions (A rises, B falls) +- (R): Reinforcing loop +- (B): Balancing loop + +Constructing a causal loop diagram for your business reveals the hidden architecture that drives performance. Most founders carry an implicit mental model of their business; making it explicit exposes assumptions, identifies leverage points, and prevents interventions that worsen the problem they aim to solve. + +--- + +## Prompts + +**Prompt 1 -- System Mapping:** +> "Map the key causal loops in my business: [describe business model, key metrics, and current challenges]. Identify at least two reinforcing loops (growth engines or death spirals) and two balancing loops (growth ceilings or stabilisers). For each loop, list the variables involved and the direction of influence between them." + +**Prompt 2 -- Archetype Diagnosis:** +> "My company is experiencing this problem: [describe problem and the solutions already attempted]. Analyse whether this matches one of the classic system archetypes (Fixes That Fail, Shifting the Burden, Limits to Growth, Tragedy of the Commons, or others). If it does, identify the quick fix, the fundamental solution, and the delayed consequence that the current approach is generating." + +**Prompt 3 -- Leverage Point Identification:** +> "Given this system structure of my business: [describe key variables and their relationships], identify the three highest-leverage intervention points -- places where a small change would produce the largest systemic effect. For each leverage point, explain the mechanism through which the intervention propagates through the system and the expected timeline for results." + +**Prompt 4 -- Unintended Consequences Forecast:** +> "We are planning to implement this change: [describe proposed initiative]. Using systems thinking, trace the likely first-, second-, and third-order consequences of this change across our organisation. Identify which feedback loops it will strengthen, which it will weaken, and any balancing loops it might trigger that could undermine the intended outcome." + +**Prompt 5 -- Mental Model Audit:** +> "Describe the implicit mental model behind our current strategy: [describe strategy]. What assumptions about cause and effect does this strategy depend on? Which of those assumptions are testable, and how would we test them? Where might our mental model diverge from the actual system structure?" + +--- + +## Use Cases + +**Validation-Stage Startup Diagnosing a Conversion Problem** + +A B2C app has strong acquisition (50,000 downloads/month) but abysmal activation (8% of downloads complete onboarding). The founder's instinct is to simplify onboarding (event-level fix). Systems mapping reveals a reinforcing loop: the product was designed for power users, which attracts power users through word-of-mouth, which generates feature requests that increase complexity, which makes onboarding harder for mainstream users, which keeps the user base skewed toward power users. The leverage point is not the onboarding flow but the product roadmap: introducing a simplified product tier breaks the reinforcing loop and opens the mainstream market without alienating the core user base. + +**Growth-Stage Company Facing a Hiring Bottleneck** + +A company growing 15% month-over-month cannot hire fast enough. The obvious solution -- throw more resources at recruiting -- triggers a balancing loop: faster hiring reduces quality of hire, which increases onboarding time, which consumes the capacity of existing team members, which reduces productivity, which increases the perceived need to hire more. The systems diagnosis identifies the leverage point as onboarding efficiency, not hiring velocity. By investing in structured onboarding (reducing time-to-productivity from 90 to 30 days), each new hire contributes sooner, reducing the total headcount needed and breaking the balancing loop. + +**Scale-Stage Platform Managing Marketplace Dynamics** + +A two-sided marketplace observes that supply growth is decelerating despite increasing demand. Causal loop analysis reveals a Tragedy of the Commons: as more suppliers join, each supplier's share of demand decreases, reducing per-supplier revenue, leading to supplier dissatisfaction and churn. The platform's response -- subsidising supplier onboarding -- merely accelerates the dynamic. The fundamental solution involves demand-side curation (matching quality suppliers with high-intent buyers) rather than supply-side volume, rebalancing the system to favour supplier profitability over raw supply count. + +--- + +## Anti-Patterns + +**Linear Thinking in a Non-Linear World.** Assuming that cause and effect are proximate in time and space. In systems, the cause of today's problem is often a decision made six months ago in a different department. Entrepreneurs who demand immediate attribution ("What caused this?") miss the systemic structure that produced it. + +**Optimising Components Instead of the System.** Making each department maximally efficient without considering how they interact. A sales team optimised for closing deals fast may generate customers who churn quickly, destroying value that the customer success team then scrambles to recover. Local optimisation frequently produces global degradation. + +**Ignoring Delays.** Feedback loops operate with time delays. An investment in product quality may not show results for two quarters. Founders who expect immediate returns from structural changes abandon them too early, concluding they did not work when they simply had not had time to propagate through the system. + +**Confusing Symptoms with Causes.** Treating declining revenue as the problem rather than as a symptom of the structural dynamics producing it. Every metric is an output of a system. Intervening at the output level (discounting to boost revenue) without addressing the input level (why customers are not buying at full price) creates the "Fixes That Fail" archetype. + +**Analysis Paralysis.** Systems thinking can become an intellectual trap. Mapping every variable and feedback loop in a complex organisation is theoretically possible but practically useless. The skill is identifying the three to five loops that dominate system behaviour and intervening there. Perfectionism in systems mapping is itself a balancing loop that constrains action. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Map your growth engine | Identify the one reinforcing loop that, if activated, drives product-market fit | +| Early Traction | Anticipate balancing loops | Growth will trigger constraints; identify them before they manifest | +| Growth | Diagnose system archetypes | Most growth-stage problems match known archetypes; pattern recognition accelerates diagnosis | +| Scale | Design system architecture | At scale, you are designing systems, not managing events; invest in structural thinking | + +At the validation stage, the entire business is essentially one hypothesis about a reinforcing loop: "If we build X, users will do Y, which creates Z value, which funds more of X." Validating that loop is the only thing that matters. + +The growth-to-scale transition is where systems thinking pays its highest dividends. The problems that emerge at scale -- coordination failures, cultural drift, quality degradation -- are almost always structural. Founders who continue to manage events ("Fire that underperformer," "Hire a VP of X") without examining the system that produces those events will exhaust themselves and their organisations. + +--- + +## Output Template + +**Target Audience: Executive Team / Strategic Advisors** + +```markdown +# Systems Analysis: [Issue or Initiative] +## [Company Name] -- [Date] + +### Problem Statement +[Describe the observable behaviour -- the event or pattern that triggered this analysis] + +### Level of Analysis +- Event: [What happened] +- Pattern: [What trend does this belong to] +- Structure: [What systemic structure produces this pattern] + +### Causal Loop Map +[Describe the key variables and their relationships] +- Variable A --(+)--> Variable B --(+)--> Variable C +- Variable C --(-)--> Variable D --(+)--> Variable A +- Loop Type: [Reinforcing / Balancing] + +### Active System Archetypes +| Archetype | Evidence | Quick Fix (Avoid) | Fundamental Solution | +|-----------|----------|-------------------|---------------------| +| [Archetype name] | [Observable symptoms] | [What feels obvious but worsens things] | [Structural intervention] | + +### Leverage Points +| # | Intervention | Mechanism | Expected Timeline | Confidence | +|---|-------------|-----------|-------------------|------------| +| 1 | [Highest-leverage change] | [How it propagates] | [When results appear] | [H/M/L] | +| 2 | [Second-highest] | [How it propagates] | [When results appear] | [H/M/L] | +| 3 | [Third-highest] | [How it propagates] | [When results appear] | [H/M/L] | + +### Unintended Consequences to Monitor +| Intervention | Possible Side Effect | Early Warning Signal | Mitigation | +|-------------|---------------------|---------------------|------------| +| [Change] | [Potential consequence] | [What to watch for] | [How to respond] | + +### Recommended Actions +1. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +2. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +3. [Action] -- Targets: [Which loop/variable] -- Owner: [Name] -- Review: [Date] +``` + +--- + +## Related Skills + +- **[Balanced Scorecard](../../content/skills/frameworks/balanced-scorecard.md)** -- Provides the four-dimensional measurement framework that makes system behaviour visible and trackable across financial, customer, process, and learning perspectives. +- **[Kaizen & BPR](../../content/skills/frameworks/kaizen-bpr.md)** -- Process improvement tools that operate within the system; Systems Thinking ensures improvements in one process do not degrade connected processes. +- **[SWOT & PEST Analysis](../../content/skills/frameworks/swot-pest-analysis.md)** -- PEST identifies external system forces; SWOT maps internal-external interactions; Systems Thinking reveals how these forces dynamically interact over time. +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- System 1 thinking produces the linear cause-and-effect reasoning that systems thinking corrects; deliberate System 2 engagement is required to see feedback loops and delays. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- Systems thinking redefines what constitutes the "problem" by revealing that observable symptoms often originate in distant structural causes, not proximate events. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Scenario planning uses the system maps that systems thinking produces to stress-test strategies against multiple plausible futures shaped by different feedback dynamics. diff --git a/plugins/foreman/skills/teaching-and-leading/SKILL.md b/plugins/foreman/skills/teaching-and-leading/SKILL.md deleted file mode 120000 index 60ff21c..0000000 --- a/plugins/foreman/skills/teaching-and-leading/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/teaching-and-leading.md \ No newline at end of file diff --git a/plugins/foreman/skills/teaching-and-leading/SKILL.md b/plugins/foreman/skills/teaching-and-leading/SKILL.md new file mode 100644 index 0000000..3154dfe --- /dev/null +++ b/plugins/foreman/skills/teaching-and-leading/SKILL.md @@ -0,0 +1,257 @@ +--- +name: "teaching-and-leading" +description: "Guides founders in leading through modelling behaviour, coaching (not managing), leveraging mirror neurons for mood contagion, distributing leadership titles generously, and using gratitude as a pre-meeting performance enhancer. Covers showing rather than telling, strengths-based leadership, the coach-and-student mindset, external accountability systems, vision-people-resources leadership triad, delivering bad news transparently, energy-state management, and making everyone a leader. Use when onboarding a first direct report, preparing to deliver difficult news to a team, noticing declining team morale, struggling with micromanagement tendencies, or building a leadership culture in an early-stage company." +version: "1.0.0" +category: "people" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - leadership + - coaching + - mirror-neurons + - modelling + - accountability + - gratitude + - transparency + - mood-contagion + - team-building + - delegation +related_skills: + - carnegie-win-friends + - persuasion-and-influence + - employee-engagement-retention + - delegation-and-empowerment + - mentoring-and-coaching + - psychological-safety-practice +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Teaching and Leading + +MIRROR NEURONS. Leadership is contagious -- and not in the metaphorical sense that motivational posters suggest. Mirror neurons, first identified in macaque monkeys and since confirmed in humans, fire both when an individual acts and when that individual observes the same action performed by another. The neurological implication for anyone who leads a team is uncomfortable in its directness: your mood, your posture, your energy state are being neurologically replicated in the people around you whether you intend it or not. A CEO who walks into a team meeting carrying the weight of a lost investor, a sick parent, and missed revenue numbers will produce a team that mirrors that weight. The meeting will underperform. The decisions will be cautious. The energy will be flat. Not because anyone was told to feel bad, but because their neurons had no choice. + +This is not a call for relentless, performative positivity. It is a call for deliberate state management -- the recognition that a leader's internal condition is, functionally, an external broadcast. What follows are ten leadership behaviours that exploit this contagion for constructive ends, each grounded in a specific practice rather than an abstract aspiration. + +--- + +## The Framework + +### Behaviour 1: Model, Don't Lecture + +A first-grade teacher's method for teaching subtraction: demonstrate the problem, demonstrate it again, then let the students try. She walked out of the room for twenty minutes. When she returned, twenty-two six-year-olds could subtract single digits -- because they had watched someone do it, not listened to someone explain it. + +The entrepreneurial translation: when teaching a new process, a sales methodology, or a company value, perform the task yourself while others watch. Narrate each step. Then perform it again. Only then hand it over. The instinct to explain is strong; the results of showing are stronger. + +| Teaching method | Retention rate | Founder's temptation | +|----------------|---------------|---------------------| +| Telling ("Here's how to do it") | Low | High -- it is fast and feels efficient | +| Showing once | Moderate | Medium -- requires patience | +| Showing twice, then supervised practice | High | Low -- requires the most time upfront, saves the most time downstream | + +The patience tax is real. The person you are teaching does not know what you know. Imagining them as a first-grader encountering the concept for the first time is not condescension; it is calibration. + +### Behaviour 2: Soar With Strengths + +The three-question leadership framework from the Entrepreneurs' Organization reduces the entire leadership function to three obligations: + +1. Set and communicate the overall vision. +2. Ensure the right people are in the right seats. +3. Ensure sufficient resources and capital for the team to succeed. + +"Right people, right seats" is the strengths mandate. Two questions determine whether someone belongs in their current role: How capable are they of doing the job? How aligned are they with the vision and values? When the answer to either question is equivocal, the seat needs to change -- not necessarily the person. A brilliant engineer miscast as a people manager is not a performance problem; it is a seating problem. + +Founders who hire a nanny interview twenty candidates before choosing one. They should apply the same rigour to every seat in the company. + +### Behaviour 3: Be a Coach and Student, Not a Teacher and Manager + +Three archetypes from a single school corridor illustrate the spectrum: + +- **Ms. Macusor** (the manager-as-tyrant): yelled, excluded late arrivals, criticised struggling students. Inspired only fear. Left teaching to become a cashier. +- **Doc Rubenstein** (the coach): "It's not my job to teach you. It's your job to learn. I'm just here to coach you along the way." Did less formal teaching than any teacher. Was one of the best. +- **Mr. Boyle** (the student-leader): "I'm a student, just like you. I've just been learning this stuff a little bit longer." Never pulled rank. Considered himself a peer. + +Fear-based management produces short-term compliance and long-term attrition. Study after study confirms the pattern: intimidation works temporarily, then collapses. The alternative is the coach's stance -- supportive, accountable, alongside rather than above -- layered with the humility of someone who is also still learning. Direct reports respond to humility with trust, and trust is the only compound that converts effort into discretionary performance. + +### Behaviour 4: External Accountability + +The most reliable accountability mechanism is not self-discipline. It is another person who will ask you uncomfortable questions on a fixed schedule. + +The practice: identify one person -- a cofounder, an advisor, a peer -- and establish a recurring accountability exchange. Share your commitments. Report on them. Submit to their honest assessment. The psychological mechanism is simple: the prospect of admitting failure to someone you respect is a more powerful motivator than any internal resolution. + +This applies symmetrically. When you want your team to hold themselves accountable, do not hold them accountable yourself. Create structures -- public commitments, peer check-ins, shared dashboards -- where accountability is social rather than hierarchical. + +### Behaviour 5: The I in Leadership + +There is no "I" in team. There is one in leadership. Every team needs someone willing to step into the uncomfortable singularity of decision-making, vision-setting, and resource-allocation. A founder who treats leadership as a group activity -- where everyone's voice carries equal decisional weight -- often produces a leaderless organisation that feels democratic and accomplishes little. + +The correction is not autocracy. It is clarity about what only the leader can do: set the vision, make the final call when consensus fails, and take personal responsibility for outcomes. Everything else can and should be distributed. + +### Behaviour 6: Mirror Neurons and Mood Contagion + +A CEO learned about mirror neurons from a podcast guest on the same day he received news of a lost $500,000 investor, his father losing his teeth in a nursing home, and missed sales numbers. Armed with new understanding, he went to the bathroom before the team meeting, looked in the mirror, thought about the company's five-year vision, and reframed his emotional state. He walked into the meeting and described a future in which the team was ringing the NASDAQ bell. Nobody in the room knew how bad his day had been. + +The protocol for state management before any leadership moment: + +1. Acknowledge the negative emotion privately. Suppression backfires; acknowledgement processes. +2. Reconnect with the vision. What is the long-term picture that makes today's problem a footnote? +3. Write a thank-you note or list three things you are grateful for. Gratitude shifts neurochemistry faster than any cognitive technique. +4. Enter the room only after the shift is complete. + +This is not dishonesty. It is the recognition that broadcasting personal distress to a team produces contagious distress, not constructive empathy. + +### Behaviour 7: "Thank You" -- The Two Most Magnetic Words + +When asked "How are you?", most people say "Fine." One leadership trainer recommended a different answer: "Fantastic." The word is a social magnet. Common responses from others: "What are you on?" and "I'll have what you're having." It signals energy, optimism, and approachability -- all of which are contagious through the same mirror neuron pathway. + +Add a second word: "Imagine." Used to open a vision statement, "imagine" gives people permission to dream. Both words cost nothing, require no preparation, and produce disproportionate social returns. + +The deeper principle: verbal micro-choices accumulate into reputation. The leader who consistently answers with energy and frames the future with possibility becomes someone others want to be around. Influence follows proximity; proximity follows attraction. + +### Behaviour 8: Always Deliver Bad News Yourself + +Positivity without transparency produces a team that trusts the leader's mood but not the leader's information. When numbers are missed, when layoffs are necessary, when a product launch fails -- the leader delivers the brutal facts personally. + +A CEO missed quarterly numbers and knew layoffs were coming. A mentor paraphrased Jim Collins: "As important as it is for you to remain positive, it's even more important for you to make sure that you and your team address the brutal facts and reality of your situation at all times." The CEO opened the retreat with: "We've missed our numbers and we are going to have to make layoffs." The team responded by adding transparency as a core company value. They put the business plan on the office walls for everyone -- including the janitors -- to see. + +The formula: deliver the truth + remain committed to the vision + show the path forward. Transparency builds trust. Trust sustains teams through bad quarters. Optimism alone does not. + +### Behaviour 9: Get High (on Gratitude) Before Every Meeting + +A chronically negative entrepreneur began a gratitude practice: writing down what he was grateful for and sharing it with an accountability partner daily. The results were transformative. His coach, initially supportive from the sidelines, became envious of the mood shift and adopted the same practice: three handwritten thank-you cards each morning on the commute, a family dinner ritual of naming one person each family member was grateful for, and grateful thoughts before sleep. + +The discovery: gratitude functions as an on-demand mood enhancer. Before a speech, write a thank-you card. Before an investor meeting, list five things you are grateful for. Before a difficult conversation, remind yourself of what is working. The mood shift is real, and thanks to mirror neurons, it transfers directly to everyone in the room. + +The escalation path for building a gratitude habit: + +1. Week 1: One thank-you card per week. +2. Week 2-3: One per day. +3. Week 4+: Three per day, written during transition time (commute, between meetings). +4. Add a nightly family or personal gratitude reflection. + +### Behaviour 10: Let Everyone Be a Leader + +A first-grade teacher at PS 230 in Brooklyn assigned leadership roles for every classroom task: line leaders, homework leaders, bathroom pass leaders, activity leaders, chalkboard leaders. Every child felt ownership, responsibility, and pride. The class ran itself. + +The corporate equivalent: be generous with leadership titles. Assign as many as possible. "President of table clearing" turned a reluctant child into a proud nightly contributor. Vice president titles at a startup cost nothing and produce ownership, commitment, and initiative. + +The principle: given the choice between leader and follower, nearly everyone chooses leader. People who think of themselves as leaders behave like leaders. The founder's job is to create enough leadership positions that everyone holds one. + +--- + +## Prompts + +**Prompt 1 -- Modelling Plan:** +> I need to teach my team [specific process or behaviour]. Draft a modelling plan: what should I demonstrate myself, how many times, and at what point should I hand over to supervised practice? Assume my team members are encountering this for the first time. + +**Prompt 2 -- Right People, Right Seats Audit:** +> Here are my team members and their current roles: [list]. For each person, assess: (a) capability for current role, (b) alignment with our vision [state vision]. Identify any seating mismatches and suggest role adjustments that leverage each person's strengths. + +**Prompt 3 -- Bad News Delivery Script:** +> I need to communicate [specific bad news] to my team of [size]. Draft opening remarks that: (a) state the brutal facts without hedging, (b) acknowledge the emotional impact, (c) reaffirm the long-term vision, and (d) outline the immediate path forward. The tone should be transparent but resolute. + +**Prompt 4 -- Leadership Distribution Map:** +> My team has [number] members. List every recurring task, project, and responsibility that currently lacks a named owner. For each, suggest a leadership title and the person best suited to hold it. The goal is maximum distributed ownership. + +--- + +## Use Cases + +**Pre-Seed Founder Onboarding a First Employee** + +A solo founder hiring employee number one faces an immediate teaching challenge: every process that has lived only in the founder's head must now be transferred. Rather than writing a 40-page handbook (which will not be read), the founder spends the first week modelling each workflow -- customer outreach, code deployment, investor update emails -- performing each task while the new hire observes. By week two, the new hire replicates each process under supervision. By week three, they own it. The founder resists the urge to explain verbally and instead shows, twice, every time. + +**Series A CEO Navigating a Down Quarter** + +Revenue missed forecast by 30%. Two enterprise customers churned. The CEO has a weekly all-hands in 48 hours. The temptation is to spin: "We're learning, we're growing, challenges are opportunities." The alternative: open with the numbers, unvarnished. "We missed by 30%. Two customers left. Here is what I believe went wrong, and here is what we are changing this quarter." Then -- and only then -- pivot to vision. The team will remember that the CEO trusted them with the truth long after they forget the specific numbers. + +**Growth-Stage Company with Flat Morale** + +A 40-person company has noticed declining engagement scores. The CEO discovers, through honest self-assessment, that her own stress has been leaking into every meeting for months. Mirror neurons have done their work. The intervention: a personal gratitude practice before every team interaction, a deliberate shift from problem-focused opening remarks to vision-focused ones, and the creation of fifteen new leadership titles across the organisation -- giving every team member visible ownership of something that matters. + +--- + +## Anti-Patterns + +**The Positivity Facade.** Gratitude practice and state management are not permission to suppress every negative signal. A CEO who smiles through a crisis while the team can see the building burning loses credibility, not gains it. The balance: manage your state for transient bad moods; be transparent about structural challenges. + +**Coaching Without Standards.** "Be a coach, not a manager" does not mean eliminating performance expectations. Coaches hold athletes accountable. The absence of standards is not coaching; it is abdication. + +**Title Inflation as Substitute for Substance.** Distributing leadership titles works when each title comes with real ownership and real accountability. A "VP of Community" who has no budget, no authority, and no metrics is not a leader; they are a participant with a flattering label. + +**Modelling Without Release.** Some founders model the task, then continue doing the task themselves because the employee "isn't doing it quite right yet." Modelling requires the discipline to hand over and accept imperfect replication as part of the learning curve. + +**Weaponising Mirror Neurons.** Understanding mood contagion is not a licence for emotional manipulation. Walking into a room with manufactured urgency to create artificial pressure is the dark application of the same science. The ethical use is managing your authentic state to create conditions where others can do their best work. + +--- + +## By Stage + +| Stage | Leadership Priority | Dominant Behaviour | +|-------|-------------------|-------------------| +| Idea | Converting believers without a product | Confidence projection; vision communication; modelling work ethic | +| Validation | Teaching the first 1-3 employees everything | Modelling (Behaviour 1); coach mindset (Behaviour 3) | +| Early Traction | Building culture before it forms accidentally | Distributed leadership (Behaviour 10); gratitude rituals (Behaviour 9) | +| Growth | Surviving bad news and maintaining trust | Transparent bad-news delivery (Behaviour 8); right people, right seats (Behaviour 2) | +| Scale | Sustaining mood and culture across hundreds of people | Mirror neuron management (Behaviour 6); institutionalised accountability (Behaviour 4) | + +At validation stage, the founder is the primary teacher -- there is no one else. Modelling is not optional; it is the only scalable knowledge-transfer mechanism when the team is smaller than a dinner party. At scale, the founder's direct teaching influence fades, but their mood influence intensifies: a single off-day from the CEO propagates through layers of management via the same mirror neuron cascade. + +--- + +## Output Template + +```markdown +# Leadership Behaviour Audit + +**Leader:** [Name] +**Team Size:** [Number] +**Current Challenge:** [Primary leadership issue] + +## State Management Check +- Current dominant mood entering meetings: [honest assessment] +- Pre-meeting gratitude practice in place: [yes/no] +- Last time bad news was delivered transparently: [date and outcome] + +## Modelling Assessment +- Processes currently taught by telling, not showing: [list] +- Plan to convert to modelling: [specific steps] + +## Right People, Right Seats +| Person | Current Role | Capability (1-5) | Value Alignment (1-5) | Action | +|--------|-------------|-------------------|----------------------|--------| +| [Name] | [Role] | [Score] | [Score] | [Keep / Move / Develop] | + +## Distributed Leadership Map +| Task/Responsibility | Current Owner | Proposed Leader | New Title | +|--------------------|--------------|-----------------|-----------| +| [Task] | [Unowned / Founder] | [Person] | [Title] | + +## Accountability Structure +- Accountability partner: [Name] +- Check-in frequency: [Weekly / Biweekly] +- Public commitment mechanism: [Dashboard / Stand-up / Shared doc] + +## Next 30 Days +1. [Specific leadership behaviour to implement] +2. [Specific leadership behaviour to implement] +3. [Specific leadership behaviour to implement] +``` + +--- + +## Related Skills + +- **[Carnegie's Win Friends and Influence People](../../content/skills/frameworks/carnegie-win-friends.md)** -- The principle of sincere appreciation is the theoretical foundation for the gratitude and praise behaviours detailed here. +- **[Persuasion and Influence](../../content/skills/leadership/persuasion-and-influence.md)** -- Complements this skill's focus on leading teams with a focus on influencing individuals in meetings and one-on-ones. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- Distributed leadership and gratitude practices directly affect retention metrics covered in that skill. +- **[Delegation and Empowerment](../../content/skills/leadership/delegation-and-empowerment.md)** -- The mechanics of handing over after modelling are detailed in the delegation framework. +- **[Mentoring and Coaching](../../content/skills/leadership/mentoring-and-coaching.md)** -- Extends the coach-and-student mindset into structured mentoring relationships. +- **[Inspiring and Retaining](../../content/skills/people/inspiring-and-retaining.md)** -- The interpersonal retention practices from that sibling skill complement the team leadership and modelling techniques taught here. diff --git a/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md b/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md deleted file mode 120000 index 647c3eb..0000000 --- a/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/leadership/team-culture-and-dynamics.md \ No newline at end of file diff --git a/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md b/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md new file mode 100644 index 0000000..96b70a3 --- /dev/null +++ b/plugins/foreman/skills/team-culture-and-dynamics/SKILL.md @@ -0,0 +1,260 @@ +--- +name: "team-culture-and-dynamics" +description: "Provides daily practices for reading team energy, shaping culture deliberately, writing unwritten rules, diagnosing accountability gaps, balancing personality types, and building high-performing teams through social connection. Use when a team feels stuck or stale, when collaboration derails despite good intentions, when unwritten norms produce confusion, when new hires struggle to decode the culture, or when a leader suspects the team's vibe is off but cannot articulate why." +version: "1.0.0" +category: "leadership" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - team-dynamics + - culture + - norms + - accountability + - collaboration + - personality + - engagement + - high-performance +related_skills: + - tuckman-team-stages + - belbin-team-roles + - hackman-enabling-conditions + - organisational-culture + - psychological-safety + - inclusive-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Team Culture and Dynamics + +Every team has a temperature. The experienced leader reads it the way a pilot reads instruments -- not by staring at any single gauge but by registering the pattern across many: who speaks first in meetings and who waits; whether laughter is frequent or forced; how quickly Slack messages receive responses; whether disagreements happen in the room or in the corridor afterward; the tone of the last three emails from the same person. None of these signals is diagnostic on its own. Together, they constitute the emotional weather system of the team. + +The theoretical architecture of team dynamics is well mapped. Tuckman describes the stages (forming, storming, norming, performing); Belbin catalogues the roles; Hackman identifies the enabling conditions. Those frameworks live in the `frameworks` directory and should be studied for their structural insight. This skill concerns itself with the question those frameworks do not fully answer: what does a leader actually do, day by day, to build and maintain a culture that converts individual talent into collective performance? + +--- + +## The Practice + +### Culture Is Manageable + +Boris Groysberg, Jeremiah Lee, Jesse Price, and Yo-Jud Cheng's research contains a sentence that should unsettle every leader who treats culture as atmospheric and uncontrollable: "Culture can, in fact, be managed." The first step is awareness -- understanding how culture works, what values it embodies, and what behaviours it rewards and punishes. The second step is deliberate intervention. Most leaders produce detailed plans for strategy and execution but leave culture unmanaged, relegating it to HR as a secondary concern. The result: culture becomes an emergent property of accumulated defaults, not a designed system. + +### Writing the Unwritten Rules + +Liz Fosslien and Mollie West Duffy offer the simplest and most underused culture intervention: write down the unwritten rules. Every team operates on implicit norms that insiders absorb over time and newcomers struggle to decode. Making them explicit serves three purposes: it reduces the anxiety of new hires who cannot tell what is acceptable, it surfaces norm conflicts that have been festering below conscious awareness, and it creates a document that can be revisited when circumstances change. + +The method: convene the team and brainstorm an "It's OK to ..." list. + +Examples: +- "It's OK to say you don't understand a process." +- "It's OK to turn off your camera during a virtual meeting." +- "It's OK to go for a short walk in the middle of the day." +- "It's OK to push back on a deadline if you explain why." +- "It's OK to ask for help before you're stuck, not after." + +The list should be living, not laminated. Revisit it quarterly, or whenever the team's composition or circumstances shift significantly. + +### When the Vibe Is Off: A Diagnostic Framework + +Liane Davey identifies four domains to investigate when a team feels stuck, stale, or subtly wrong: + +**1. Mandate and Goals** +- What external trends require adaptation? +- How do shifts in company strategy affect the team? +- How is the team's value within the organisation evolving? +- How can success metrics be improved? + +**2. Strategies and Roles** +- Is the team strategy aligned with its mandate? +- What tactics need revision? +- Does anyone need a change in role? +- What assumptions could endanger current plans? + +**3. Dynamics and Norms** +- What norms need to be established or revised? +- How can conflicts be resolved more effectively? +- What activities could improve trust and candour? + +**4. Communication Habits** +- What channels can be used more effectively? +- What information should be synchronous versus asynchronous? +- How can distractions be reduced? +- What are reasonable expectations for response times? + +The diagnostic works best as a group conversation, not a leader's solo analysis. The act of discussing these questions together is itself therapeutic -- it surfaces problems that individual conversations cannot reach. + +### The Right Mix of Personalities + +Dave Winsborough and Tomas Chamorro-Premuzic's research complements Belbin's role theory with a personality-type lens. Five types matter: + +| Type | Characteristic | Value to Team | +|------|---------------|---------------| +| Results-oriented | Organise work, take charge | Drive execution and accountability | +| Relationship-focused | Form genuine connections, read emotions | Build cohesion and trust | +| Process followers | Reliable, detail-oriented, conscientious | Ensure quality and consistency | +| Innovative thinkers | Curious, imaginative, open to novelty | Generate ideas and challenge assumptions | +| Pragmatic | Practical, prudent, level-headed | Ground the team in reality | + +A team dominated by one or two types produces predictable dysfunction: all innovators and no process followers create exciting chaos; all process followers and no innovators create reliable mediocrity. The leader's job is to diagnose which types are overrepresented and which are missing, and to hire or reassign accordingly. + +### Building Social Connections + +Ron Friedman's research, in partnership with learning company ignite80, establishes that social connection and team performance are not merely correlated -- they are causally linked. Two practices matter most: + +**Bond over non-work topics.** Discussing hobbies, families, and shared interests yields closer friendships and better teamwork. The leader who restricts all communication to task-related content may be efficient but is building a team that lacks the relational resilience to survive pressure. + +**Make appreciation a team norm.** Recognition is more motivating than monetary rewards, and peer-to-peer recognition is often more valued than top-down praise. Build rituals -- a weekly shout-out, a rotating "MVP" acknowledgement, a shared channel for appreciation -- and participate in them without dominating them. + +### Cross-Functional Collaboration Traps + +Lisa Kwan's research identifies a blind spot in most cross-functional initiatives: leaders focus on logistics, processes, and incentives while ignoring how the request to collaborate makes teams feel. When teams are told to share information, sacrifice autonomy, or cede defining responsibilities, insecurity triggers defensive behaviour. The leader who plans a cross-functional project should explicitly address the emotional dimension: acknowledge what teams are giving up, explain what they gain, and create structures that protect each team's identity while enabling collaboration. + +### Staffing for Innovation + +Nathan Furr, Kyle Nel, and Thomas Ramsoy identify three capabilities essential for high-profile, uncertain projects: + +1. **Comfort with uncertainty** -- People who remain curious when the endpoint is unclear. +2. **Structure in chaos** -- People who create frameworks and drive action when circumstances change. +3. **Connect and execute** -- People who see links between disparate information and produce tangible outputs. + +These are not the same as "high performers." A team of individually excellent people who all prefer certainty will stall the moment a project enters ambiguous territory. + +### Fighting Toxic Culture with Microculture + +Annie McKee addresses the leader who operates within a toxic larger culture. The prescription: create a microculture. Hold meetings -- plural, because one is not enough -- where team members discuss shared values, articulate rules of engagement, and codify norms in a team code of conduct. The microculture will not change the company, but it can protect the team. + +### The Learning Curve Mix + +Whitney Johnson's model provides a diagnostic for team engagement: at any given time, approximately 15% of the team should be at the bottom of a learning curve (new to their role or responsibilities), 70% should be in the productive middle (building and applying skills), and 15% should be at the top (mastering their current domain and ready for the next challenge). When someone reaches mastery and no new curve is offered, disengagement follows. The leader's job is to keep the curves cycling. + +--- + +## Prompts + +**Prompt 1 -- Team Temperature Read:** +> Based on these observations about my team: [describe meeting dynamics, communication patterns, recent interpersonal incidents, energy levels, and any signals that concern you]. Diagnose the team's "temperature" across Davey's four domains (mandate/goals, strategies/roles, dynamics/norms, communication). For each domain, rate it as healthy/strained/critical and recommend one intervention per domain. + +**Prompt 2 -- Unwritten Rules Workshop Design:** +> I want to run an "It's OK to ..." session with my team of [size] people. Design a 45-minute workshop: opening framing (why we're doing this), facilitation method (how to generate the list without groupthink), and follow-up plan (how to keep the list alive). Include five example prompts to get the conversation started if the team is hesitant. + +**Prompt 3 -- Personality Mix Audit:** +> Here are my team members and brief descriptions of their working styles: [list names and one-sentence descriptions]. Map each to the five personality types (results-oriented, relationship-focused, process follower, innovative thinker, pragmatic). Identify which types are overrepresented and underrepresented. Recommend whether the gap should be addressed through hiring, role adjustment, or development. + +**Prompt 4 -- Cross-Functional Launch Plan:** +> I am launching a cross-functional project involving [list teams]. Using Kwan's framework, identify the emotional risks: what is each team being asked to give up? What defensive behaviours might emerge? Design the project kickoff communication to explicitly address these concerns and propose structural safeguards that protect each team's identity while enabling collaboration. + +--- + +## Use Cases + +**Early-traction startup where the culture is the founder's personality** + +A 12-person startup has no documented norms. The culture is whatever the founder does on any given day -- which means it is unpredictable. New hires take three months to decode what is acceptable, and two have already left citing "cultural fit" without being able to articulate what the culture actually is. An "It's OK to ..." session produces a list of 20 norms that the founder had assumed were obvious. Documenting them reduces new-hire anxiety, cuts onboarding confusion, and -- unexpectedly -- forces the founder to confront two norms they had been enforcing unconsciously that were actively harmful. + +**Growth-stage company where the vibe is off but nobody can say why** + +A 75-person company has been growing quickly, and the leadership team senses malaise without being able to diagnose it. A structured Davey diagnostic reveals that the mandate domain is healthy (everyone understands the mission), but the communication domain is critical: the team has outgrown its communication norms. What worked for 30 people (all-Slack, instant responses expected) is suffocating 75 people. New norms are established: asynchronous by default, synchronous by exception, expected response times explicitly stated, and two meeting-free mornings per week. + +**Scale-stage company staffing an innovation initiative** + +A 500-person company assigns its highest-performing engineers to a new product exploration team. Six months later, the team has produced nothing. A Furr/Nel/Ramsoy analysis reveals that every team member is results-oriented and process-following -- excellent at execution, paralysed by ambiguity. Restructuring the team to include people comfortable with uncertainty and capable of connecting disparate ideas produces a prototype within eight weeks. + +--- + +## Anti-Patterns + +**1. Confusing culture with perks.** Free lunch, ping-pong tables, and unlimited PTO are not culture. Culture is how people treat each other when the project is late, the client is angry, and the budget is halved. Perks are decorative; norms are structural. + +**2. Managing individuals, not the team.** Linda Hill's research identifies this as one of the most common new-manager mistakes. Optimising each person's satisfaction independently can produce a collection of happy individuals who do not function as a unit. The leader must attend to group dynamics, shared norms, and collective performance, not just individual KPIs. + +**3. Ignoring the emotional dimension of collaboration.** Cross-functional initiatives that treat teams as interchangeable resource pools, without acknowledging the identity and autonomy being surrendered, produce defensive behaviour that manifests as passive resistance, hoarding, or sabotage. + +**4. Leaving unwritten rules unwritten permanently.** Every team has implicit norms. Refusing to surface and document them does not make them less powerful; it makes them less equitable, since insiders benefit from tacit knowledge that outsiders must guess. + +**5. Assuming culture is set at founding and persists automatically.** Culture degrades without maintenance. Every new hire, every reorganisation, every market shift applies pressure to existing norms. Leaders who assume the culture will self-perpetuate discover, usually too late, that it has mutated into something they would not have chosen. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Founding norms, "It's OK to ..." documentation | Culture is set now, consciously or not; deliberate is better than default | +| Growth | Communication norms, personality mix, microculture vs. company culture | Norms that worked at 20 people break at 80; active redesign is required | +| Scale | Organisational culture architecture, cross-functional dynamics, learning-curve management | Culture becomes a systems problem requiring policy, measurement, and structural intervention | + +At early traction, the team is small enough that culture can be shaped through daily behaviour. The founder's habits -- how they handle disagreement, whether they celebrate effort or only results, how they respond to mistakes -- are the culture. Documentation at this stage feels premature but is precisely the intervention that prevents cultural drift as the team grows. + +At growth, the critical transition is from founder-driven culture to manager-mediated culture. The founder can no longer personally model norms for every employee. Middle managers become the primary culture-carriers, which means they must be explicitly equipped to understand and transmit the culture -- not just execute tasks. + +At scale, culture requires the same rigour as strategy: measurement, feedback loops, and structural reinforcement. Engagement surveys, norm audits, cross-functional trust metrics, and learning-curve analyses become the instruments through which culture is maintained -- not as bureaucratic overhead but as the operating system on which performance runs. + +--- + +## Output Template + +```markdown +# Team Culture Diagnostic -- [Team Name] + +**Date:** [Date] +**Team size:** [N] +**Leader:** [Name] + +## Temperature Reading + +| Domain | Rating | Key Signal | Intervention | +|--------|--------|-----------|-------------| +| Mandate & Goals | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Strategies & Roles | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Dynamics & Norms | [Healthy/Strained/Critical] | [Observation] | [Action] | +| Communication | [Healthy/Strained/Critical] | [Observation] | [Action] | + +## Personality Mix Map + +| Name | Type(s) | Overrepresented? | +|------|---------|-----------------| +| [Name] | [Type] | [Yes/No] | + +**Missing types:** [List] +**Recommendation:** [Hire / Reassign / Develop] + +## Unwritten Rules (Current "It's OK to ..." List) +1. [Rule] +2. [Rule] +3. [Rule] + +## Learning Curve Distribution + +| Curve Position | Target % | Actual % | Gap | +|---------------|----------|----------|-----| +| Bottom (learning) | 15% | [%] | [+/-] | +| Middle (building) | 70% | [%] | [+/-] | +| Top (mastering) | 15% | [%] | [+/-] | + +## Social Connection Health +- Last non-work team activity: [Date and description] +- Peer appreciation frequency: [High/Medium/Low] +- Cross-team relationship quality: [Strong/Adequate/Weak] + +## 30-Day Culture Plan +1. [Action with owner and deadline] +2. [Action with owner and deadline] +3. [Action with owner and deadline] +``` + +--- + +## Related Skills + +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- Provides the developmental model for how teams evolve; this skill provides the daily behaviours that move a team through those stages productively. +- **[Belbin Team Roles](../../content/skills/frameworks/belbin-team-roles.md)** -- Belbin maps functional roles; this skill's personality-type lens provides a complementary view of team composition. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman identifies what teams need to succeed; this skill focuses on how to provide it day by day. +- **[Organisational Culture](../../content/skills/frameworks/organisational-culture.md)** -- The company-level culture framework; this skill operates at the team level, where culture is lived rather than declared. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Safety is the precondition for the candour that healthy team dynamics require. +- **[Inclusive Leadership](../../content/skills/leadership/inclusive-leadership.md)** -- Inclusion is a specific dimension of team culture; this companion skill addresses it in depth. +- **[Resolving People Conflict](../../content/skills/people/resolving-people-conflict.md)** -- Provides the behavioural scripts for navigating the interpersonal friction that inevitably arises during the storming phase of team development. diff --git a/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md b/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md deleted file mode 120000 index bb0d01a..0000000 --- a/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/thinking-fast-and-slow.md \ No newline at end of file diff --git a/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md b/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md new file mode 100644 index 0000000..1963ccc --- /dev/null +++ b/plugins/foreman/skills/thinking-fast-and-slow/SKILL.md @@ -0,0 +1,188 @@ +--- +name: "thinking-fast-and-slow" +description: "Audits business decisions for cognitive biases using Kahneman's dual-process theory of System 1 (fast, intuitive) and System 2 (slow, analytical) thinking. Covers overconfidence, anchoring, loss aversion, planning fallacy, and availability heuristic. Use when conducting pre-mortems on major initiatives, debiasing fundraising projections, applying reference-class forecasting, sorting decisions by required processing mode, or building structured decision protocols." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - cognitive-bias + - decision-making + - behavioural-economics + - heuristics + - risk-assessment +related_skills: + - emotional-intelligence + - flow-state + - vuca-framework + - psychological-safety +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Thinking, Fast and Slow + +The human mind is simultaneously the most sophisticated decision-making instrument ever developed and a deeply unreliable narrator of its own reasoning. That paradox sits at the centre of Daniel Kahneman's work: the very cognitive machinery that enables entrepreneurs to spot opportunities in ambiguity is the same machinery that systematically misleads them about probability, risk, and the quality of their own judgments. Kahneman, a psychologist who won the Nobel Prize in Economics, spent decades demonstrating that rationality is not the default setting of the human brain -- it is an effortful exception. For founders making high-stakes decisions under uncertainty, understanding the architecture of their own thinking is not a philosophical luxury. It is a competitive necessity. + +--- + +## The Framework + +Kahneman's model divides cognition into two distinct systems, each with its own operational characteristics, strengths, and failure modes. + +### System 1 and System 2 + +| Dimension | System 1 (Fast) | System 2 (Slow) | +|-----------|-----------------|-----------------| +| **Speed** | Instantaneous, automatic | Deliberate, effortful | +| **Awareness** | Operates below conscious threshold | Requires focused attention | +| **Capacity** | Parallel, high-throughput | Serial, limited bandwidth | +| **Energy cost** | Low | High (depletes with use) | +| **Error profile** | Systematic biases, predictable mistakes | Logical but lazy -- often endorses System 1 | +| **Strengths** | Pattern recognition, intuition, rapid assessment | Analysis, planning, complex calculation | +| **Triggers** | Familiar situations, emotional stimuli | Novel problems, explicit instructions to "think carefully" | + +The critical insight is not that System 1 is bad and System 2 is good. Rather, most people -- including experienced executives -- dramatically overestimate how often System 2 is actually engaged. System 2 is cognitively expensive, and the brain defaults to System 1 wherever possible. + +### The Bias Catalogue for Entrepreneurs + +Several of Kahneman's identified biases carry outsized relevance for startup decision-making: + +**Overconfidence bias.** Founders consistently overestimate the probability of their venture's success and underestimate the time and resources required. Kahneman's research shows that experts are no less susceptible than novices -- in many domains, they are more so, because their confidence scales faster than their accuracy. + +**Anchoring effect.** The first number encountered in a negotiation, valuation discussion, or market-sizing exercise disproportionately shapes subsequent estimates. A seed-stage founder who hears "companies like yours typically raise $2M" will unconsciously anchor all subsequent financial planning to that figure, regardless of whether it reflects their actual needs. + +**Loss aversion.** Losses are psychologically weighted roughly twice as heavily as equivalent gains. This explains why founders cling to failing products far longer than rational analysis warrants -- the pain of admitting loss exceeds the potential pleasure of redeploying resources toward a better opportunity. + +**Planning fallacy.** People systematically underestimate the time, cost, and risk of future actions while overestimating their benefits. Kahneman recommends adopting the "outside view" -- examining base rates from comparable projects rather than building estimates from the inside. + +**Availability heuristic.** Judgments about probability are distorted by how easily examples come to mind. A founder who just read about a unicorn exit in their sector will overestimate the likelihood of a similar outcome for their own company. + +### The Pre-Mortem Technique + +Kahneman's most directly actionable tool for entrepreneurs is the pre-mortem. Rather than asking "Will this plan succeed?", a team imagines that it is one year in the future and the plan has definitively failed. Each member then independently writes down the reasons for failure. This technique accomplishes two things: it legitimises dissent (overcoming groupthink) and it activates prospective hindsight, which research shows increases the ability to identify causes of future outcomes by roughly 30%. + +--- + +## Prompts + +**Prompt 1 -- Bias Audit:** +> Conduct a cognitive bias audit on the following business decision: [describe decision]. Identify which of Kahneman's biases (overconfidence, anchoring, loss aversion, planning fallacy, availability heuristic, WYSIATI) are most likely influencing the decision-makers. For each bias identified, suggest a specific debiasing technique and explain how to implement it in the context of this decision. + +**Prompt 2 -- Pre-Mortem Facilitation:** +> Run a pre-mortem analysis on this plan: [describe plan]. Assume it is 12 months from now and the plan has failed completely. Generate 8-10 plausible reasons for failure, categorised by whether they stem from internal factors (team, execution, resources) or external factors (market, competition, regulation). Rank them by likelihood and suggest early warning indicators for each. + +**Prompt 3 -- Outside View Assessment:** +> Apply Kahneman's "outside view" methodology to this projection: [describe projection, e.g., "We will reach $1M ARR within 18 months"]. Research base rates for comparable companies at our stage ([stage]) in our sector ([sector]). Compare our inside-view assumptions against these base rates and highlight the largest discrepancies. Recommend adjusted projections. + +**Prompt 4 -- System 1/System 2 Decision Sort:** +> Review the following list of pending decisions for my startup: [list decisions]. Classify each as appropriate for System 1 processing (pattern-matching, intuition-safe) or requiring System 2 engagement (novel, high-stakes, irreversible). For the System 2 decisions, recommend a specific analytical framework or structured process to ensure deliberate reasoning. + +--- + +## Use Cases + +**Seed-stage SaaS founder evaluating pivot options** + +A B2B SaaS founder at the validation stage has two potential pivots after initial product-market fit signals proved weak. She finds herself drawn to Option A because a prominent accelerator mentor mentioned a similar company that succeeded (availability heuristic) and because she has already invested eight months building toward that direction (loss aversion / sunk cost). Applying Kahneman's framework, she conducts a pre-mortem on both options, seeks base-rate data on comparable pivots, and deliberately assigns a team member to argue the case for Option B. The structured process reveals that Option B has stronger unit economics and a less crowded competitive landscape -- factors her System 1 had deprioritised because they were less emotionally vivid. + +**Growth-stage marketplace negotiating acquisition terms** + +A two-sided marketplace with $5M ARR receives an acquisition offer. The founding team anchors on the first number proposed by the acquirer and spends weeks negotiating around that figure. A board advisor trained in Kahneman's work recognises the anchoring effect and introduces an independent valuation analysis using three distinct methodologies, none of which reference the acquirer's initial offer. The resulting negotiation achieves a 40% higher price because the team broke free of the original anchor. + +**Scale-stage fintech building annual forecasts** + +A fintech company at scale consistently underestimates project timelines by 30-50%. The COO implements Kahneman's reference-class forecasting: instead of building estimates bottom-up from project plans, the team first identifies a reference class of 20 similar projects completed in the past two years, calculates the statistical distribution of actual completion times, and uses that distribution as the starting point for new estimates. Planning accuracy improves markedly within two quarters. + +--- + +## Anti-Patterns + +**1. "I already know about biases, so I'm debiased."** Awareness of cognitive biases does not neutralise them. Kahneman himself has stated that decades of studying biases did not make him immune to them. The solution is structural -- building decision processes that compensate for bias, not relying on individual awareness. + +**2. Weaponising bias labels to win arguments.** Labelling a colleague's position as "anchoring" or "confirmation bias" becomes a rhetorical trick rather than a genuine analytical tool. Bias identification should apply to the decision process, not to individuals in the room. The moment it becomes ad hominem, it destroys the psychological safety required for honest deliberation. + +**3. Paralysis through over-analysis.** Some teams, having discovered the extent of cognitive bias, become unable to make any decision without exhaustive debiasing procedures. Kahneman's own framework acknowledges that System 1 is appropriate for many decisions -- particularly those that are reversible, low-stakes, or where the decision-maker has genuine domain expertise built through years of practice with rapid feedback. + +**4. Applying the outside view to genuinely novel situations.** Reference-class forecasting requires a meaningful reference class. When a company is doing something truly unprecedented, there may be no valid outside view. Forcing one can be as misleading as the inside view it replaces. + +**5. Ignoring that System 2 is depletable.** Scheduling all high-stakes decisions in a single marathon session is counterproductive. System 2 fatigues. Decision quality degrades with cognitive load. Structuring the calendar so that critical decisions receive fresh cognitive resources is itself a strategic choice. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Hypothesis testing under maximum uncertainty | Overconfidence and confirmation bias are most dangerous here -- founders must resist interpreting ambiguous signals as validation | +| Early Traction | Scaling decisions and resource allocation | Anchoring on early metrics (first customers, first pricing) can distort strategy as the company moves beyond its initial niche | +| Growth | Hiring, market expansion, competitive response | Loss aversion makes it difficult to kill underperforming product lines or exit markets; pre-mortems become essential for major initiatives | +| Scale | M&A, organisational design, forecasting | Planning fallacy dominates large-scale projects; reference-class forecasting and structured decision processes yield the highest returns here | + +At the validation stage, the most frequent failure mode is confirmation bias -- interpreting every piece of ambiguous customer feedback as evidence that the hypothesis is correct. The corrective is to define falsification criteria before running experiments: "What specific result would cause us to abandon this hypothesis?" + +At growth and scale, the dominant risk shifts to organisational bias amplification. Individual biases compound through group dynamics. A CEO's overconfidence becomes the company's overconfidence when no structural counterweight exists. Formal decision protocols -- including pre-mortems, red teams, and independent analysis -- become operational necessities rather than intellectual exercises. + +--- + +## Output Template + +```markdown +# Cognitive Bias Assessment -- [Decision/Initiative Name] + +**Prepared for:** Board / Leadership Team +**Date:** [Date] +**Decision under review:** [One-sentence description] + +## Decision Classification +- **Reversibility:** [Reversible / Partially reversible / Irreversible] +- **Stakes:** [Low / Medium / High] +- **Novelty:** [Routine / Somewhat novel / Unprecedented] +- **Recommended processing mode:** [System 1 sufficient / System 2 required] + +## Bias Scan + +| Bias | Risk Level | Evidence | Debiasing Action | +|------|-----------|----------|-----------------| +| Overconfidence | [H/M/L] | [Specific evidence] | [Specific action] | +| Anchoring | [H/M/L] | [Specific evidence] | [Specific action] | +| Loss aversion | [H/M/L] | [Specific evidence] | [Specific action] | +| Planning fallacy | [H/M/L] | [Specific evidence] | [Specific action] | +| Availability | [H/M/L] | [Specific evidence] | [Specific action] | + +## Pre-Mortem Results +**Scenario:** It is [date + 12 months]. This initiative has failed. + +### Top Failure Causes (ranked by likelihood) +1. [Cause] -- Early warning indicator: [indicator] +2. [Cause] -- Early warning indicator: [indicator] +3. [Cause] -- Early warning indicator: [indicator] + +## Outside View +- **Reference class:** [Description of comparable situations] +- **Base rate of success:** [X%] +- **Our inside-view estimate:** [Y%] +- **Recommended adjusted estimate:** [Z%] + +## Decision Recommendation +[Proceed / Proceed with modifications / Delay / Abandon] + +**Rationale:** [2-3 sentences incorporating bias-adjusted analysis] +``` + +--- + +## Related Skills + +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Kahneman's System 1 is heavily influenced by emotional states; Goleman's framework provides the self-awareness layer needed to recognise when emotions are hijacking judgment. +- **[VUCA Framework](../../content/skills/frameworks/vuca-framework.md)** -- High-VUCA environments amplify every cognitive bias Kahneman identifies; structured responses to volatility and ambiguity are the organisational complement to individual debiasing. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Pre-mortems and bias audits only work when team members feel safe challenging prevailing assumptions, making Edmondson's framework a prerequisite for effective debiasing. +- **[Enemies of Clear Thinking](../../content/skills/thinking/enemies-of-clear-thinking.md)** -- Expands Kahneman's bias catalogue into a broader inventory of reasoning failures, providing additional tools for recognizing when System 1 shortcuts produce systematic errors. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- Provides structured decision frameworks that force System 2 engagement on high-stakes choices where intuitive judgment is most likely to mislead. +- **[Stoic Unbiased Thought](../../content/skills/stoic/stoic-unbiased-thought.md)** -- The Stoic practice of examining impressions before assenting to them is an ancient parallel to Kahneman's prescription for overriding System 1 with deliberate System 2 analysis. diff --git a/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md b/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md deleted file mode 120000 index f43eba2..0000000 --- a/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/thomas-kilmann-conflict.md \ No newline at end of file diff --git a/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md b/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md new file mode 100644 index 0000000..e4c0181 --- /dev/null +++ b/plugins/foreman/skills/thomas-kilmann-conflict/SKILL.md @@ -0,0 +1,209 @@ +--- +name: "thomas-kilmann-conflict" +description: "Diagnoses and resolves conflicts using the Thomas-Kilmann + five-mode framework: competing, collaborating, compromising, avoiding, and + accommodating, mapped across assertiveness and cooperativeness dimensions. Use + when navigating co-founder disagreements, mediating cross-functional team + friction, choosing the right conflict mode for high-stakes decisions, + expanding personal conflict style range, or designing conflict resolution + processes for the organization." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - conflict-resolution + - negotiation + - team-dynamics + - communication + - leadership +related_skills: + - radical-candor + - win-win-negotiation + - tuckman-team-stages + - trust-equation +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Thomas-Kilmann Conflict Mode Instrument + +Two cofounders sit across from each other at a board meeting. The CTO wants to rebuild the platform from scratch -- eighteen months of engineering effort that will freeze feature development. The CEO insists the business cannot survive eighteen months without new features; the rebuild must happen incrementally, alongside shipping. Both are right. Both are wrong. Neither can unilaterally win without destroying the partnership. The board members exchange glances, recognising a pattern they have seen dismantle companies more promising than this one. + +How this conflict resolves -- not whether it resolves, but *how* -- will determine the company's trajectory more decisively than any product decision. Kenneth Thomas and Ralph Kilmann mapped exactly this terrain in the 1970s, identifying five distinct conflict-handling modes arranged along two dimensions: assertiveness (the degree to which you pursue your own concerns) and cooperativeness (the degree to which you attempt to satisfy the other party's concerns). The genius of their model is not prescribing one mode as superior but revealing that effective leaders command all five and deploy each situationally. + +--- + +## The Framework + +### The Two Dimensions + +The TKI plots conflict behaviour on two independent axes: + +- **Assertiveness** (vertical axis): The extent to which you attempt to satisfy your own concerns. High assertiveness means you push for your position; low assertiveness means you set your concerns aside. +- **Cooperativeness** (horizontal axis): The extent to which you attempt to satisfy the other party's concerns. High cooperativeness means you prioritise the relationship and the other's needs; low cooperativeness means you focus solely on your own outcome. + +### The Five Modes + +``` + HIGH ASSERTIVENESS + | + Competing | Collaborating + (Win-Lose) | (Win-Win) + | + LOW ───────── Compromising ─────── HIGH + COOPERATIVENESS | COOPERATIVENESS + | + Avoiding | Accommodating + (Lose-Lose) | (Lose-Win) + | + LOW ASSERTIVENESS +``` + +**1. Competing (High Assertiveness, Low Cooperativeness)** + +You pursue your position at the other party's expense. Power, authority, or force of will determines the outcome. + +- **When to use:** Emergencies requiring rapid action. Unpopular but necessary decisions (layoffs, pivots). When you know you are right on matters of principle. Protecting against people who exploit non-competitive behaviour. +- **When to avoid:** Routine disagreements. Situations requiring buy-in from the other party. Relationships you need to preserve long-term. + +**2. Collaborating (High Assertiveness, High Cooperativeness)** + +Both parties work together to find a solution that fully satisfies everyone's concerns. This is not compromise -- no one gives anything up. + +- **When to use:** When both sets of concerns are too important to trade away. When you need to learn (the other party may have information you lack). When building commitment is essential to implementation. Integrating insights from people with different perspectives. +- **When to avoid:** Trivial issues where the time investment is disproportionate. When one party is not acting in good faith. Under genuine time pressure. + +**3. Compromising (Moderate Assertiveness, Moderate Cooperativeness)** + +Both parties give up something. The solution partially satisfies everyone but fully satisfies no one. Splitting the difference is the archetype. + +- **When to use:** When goals are moderately important but not worth the disruption of competing or the time investment of collaborating. As a temporary settlement to complex issues. When two equally powerful parties are equally committed to mutually exclusive goals. As a fallback when collaboration fails. +- **When to avoid:** When the issue genuinely matters and a creative solution exists. When one party can be persuaded by evidence. When "splitting the difference" produces a solution inferior to either original position. + +**4. Avoiding (Low Assertiveness, Low Cooperativeness)** + +You sidestep the conflict entirely. Neither your concerns nor the other party's concerns are addressed. + +- **When to use:** When the issue is trivial. When you have no chance of satisfying your concerns. When the potential damage of confrontation outweighs the benefits. To let people cool down. When gathering more information is essential before engaging. +- **When to avoid:** When issues will fester and escalate. When avoidance signals indifference or weakness. When your silence is being interpreted as agreement. + +**5. Accommodating (Low Assertiveness, High Cooperativeness)** + +You set aside your own concerns to satisfy the other party. The opposite of competing. + +- **When to use:** When you realise you were wrong. When the issue matters far more to the other party than to you. To build social credit for future issues that matter more. When preserving harmony is critical. When continued competition would only damage the relationship. +- **When to avoid:** When your concern is legitimate and important. When accommodating becomes a habitual pattern that breeds resentment. When the other party is not reciprocating over time. + +### Mode Selection Matrix + +| Situation | Recommended Mode | Rationale | +|-----------|-----------------|-----------| +| Server is down, customers affected | Competing | Speed overrides consensus | +| Cofounder disagrees on company vision | Collaborating | Both perspectives contain essential truth | +| Negotiating office lease terms | Compromising | Moderate stakes, clear trade-offs | +| Team member raises a complaint during a crisis | Avoiding (temporarily) | Address after the immediate crisis resolves | +| Junior team member has a better idea than yours | Accommodating | Their idea wins on merit; your ego is irrelevant | +| Board member pushes strategy you believe is destructive | Competing | Fiduciary principle at stake | +| Product and engineering disagree on sprint priorities | Collaborating | Both functions must buy in for execution | + +--- + +## Prompts + +**Prompt 1 -- Conflict Diagnosis:** +> I am in a conflict with [describe the other party and their role]. The disagreement concerns [describe the issue]. Using the Thomas-Kilmann model, help me identify which conflict mode I am currently defaulting to, which mode the other party appears to be using, and which mode would be most effective given the stakes, the relationship importance, and the time constraints. Explain your recommendation. + +**Prompt 2 -- Mode Expansion:** +> Analyse my natural conflict style based on these recent situations: [describe 3-4 recent conflicts and how you handled them]. Using the TKI framework, identify which modes I overuse and which I underuse. Then provide specific behavioural scripts for the modes I need to develop, tailored to my role as [founder/CEO/manager] at a [stage] company. + +**Prompt 3 -- Team Conflict Mediation:** +> Two members of my team are in sustained conflict over [describe the issue]. One appears to be operating in [mode] and the other in [mode]. As their manager, help me design an intervention using the TKI framework: What mode should I adopt as the mediator? What questions should I ask each party? What process would move them toward a productive resolution? + +**Prompt 4 -- Cofounder Conflict Resolution:** +> My cofounder and I disagree fundamentally about [describe the issue]. Our relationship is critical to the company's survival, but the issue cannot be avoided. Using the Thomas-Kilmann model, walk me through a collaborating-mode approach: How do I structure the conversation? What are the key moves to ensure both concerns are fully surfaced? What happens if collaboration fails -- what is my fallback mode and when do I invoke it? + +--- + +## Use Cases + +**Cofounder Equity Dispute at Validation Stage** +Two cofounders who launched with a 50/50 split now contribute asymmetrically -- one works full-time, the other retains a day job. The full-time founder wants to renegotiate. Default mode: competing ("I deserve more"). Effective mode: collaborating. The conversation reframes from "dividing a fixed pie" to "designing a structure that incentivises both parties to maximise their contribution." The output: a dynamic equity arrangement (using a tool like Slicing Pie) that adjusts ownership based on relative contribution, satisfying both parties' core concerns. + +**Product vs. Sales Conflict at Growth Stage** +The VP of Sales demands custom features for a whale client. The VP of Product refuses, citing roadmap integrity. Both escalate to the CEO. Applying TKI, the CEO recognises that competing (choosing a side) will alienate one function. Avoiding (deferring the decision) will cost the deal and the roadmap. The CEO facilitates a collaborating session that reveals an alternative: the whale client's requirements overlap 70% with planned platform features; sequencing those features first satisfies both the client timeline and the roadmap logic. The remaining 30% becomes a scoped professional-services engagement, funded by the client. + +--- + +## Anti-Patterns + +1. **Single-Mode Fixation.** Founders who only compete ("my way or the highway") eventually find themselves surrounded by accommodators who have stopped offering honest input. Founders who only accommodate find their authority eroded. Founders who only avoid discover that suppressed conflicts metastasise. Mastery requires range. + +2. **Collaborating on Everything.** Collaboration is the most resource-intensive mode. Applying it to every disagreement -- including trivial ones -- produces meeting bloat, decision fatigue, and a reputation for indecisiveness. Reserve collaboration for issues where both parties' concerns are genuinely important and a creative solution is possible. + +3. **Confusing Compromising with Collaborating.** Compromise means both parties sacrifice something. Collaboration means neither does -- a genuinely new solution emerges that satisfies all concerns. Settling for compromise on a high-stakes issue often produces a mediocre outcome when a superior one was achievable. + +4. **Misreading Power Dynamics.** The TKI assumes roughly equal parties. When power is dramatically asymmetric -- a VC dictating terms to a first-time founder, for instance -- the model's prescriptions need adjustment. Competing against a more powerful party without leverage is not assertiveness; it is self-destruction. + +5. **Avoiding Avoidance When Avoidance Is Correct.** Some conflicts should be left alone. Not every disagreement is worth engaging. The anti-pattern is not avoidance itself but reflexive avoidance of issues that demand engagement. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Cofounder alignment | Conflicts at this stage are existential -- they determine whether the founding team survives. Collaborating mode is essential for vision and equity discussions; competing mode may be necessary to kill ideas that do not survive customer contact. | +| Early Traction | Role clarity conflicts | As the team grows beyond the founders, conflicts arise about ownership, process, and decision rights. The TKI helps founders choose when to assert authority and when to empower team members. | +| Growth | Cross-functional friction | Product vs. sales, engineering vs. design, speed vs. quality. These recurring tensions require sophisticated mode-switching. Growth-stage leaders need all five modes in active rotation. | +| Scale | Organisational conflict management | At scale, the founder cannot mediate every conflict. The task becomes teaching the TKI framework to managers throughout the organisation and building conflict-resolution capacity into the culture. | + +--- + +## Output Template + +```markdown +# Conflict Analysis: [Issue Description] + +## Parties & Positions +- **Party A ([Name/Role]):** [Their position and underlying concerns] +- **Party B ([Name/Role]):** [Their position and underlying concerns] + +## TKI Assessment +- **Party A's current mode:** [Competing / Collaborating / Compromising / Avoiding / Accommodating] +- **Party B's current mode:** [Mode] +- **Mode interaction dynamic:** [What happens when these two modes collide] + +## Recommended Approach +- **Optimal mode for this situation:** [Mode] +- **Rationale:** [Why this mode fits the stakes, relationship, and time constraints] +- **Fallback mode if primary fails:** [Mode] + +## Conversation Design +1. [Opening move] +2. [Key questions to surface underlying concerns] +3. [Process for generating options] +4. [Decision mechanism if parties cannot agree] + +## Anticipated Outcome +- **Best case:** [Description] +- **Most likely:** [Description] +- **Worst case and mitigation:** [Description] +``` + +--- + +## Related Skills + +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Collaborating mode in TKI maps directly to principled negotiation; both frameworks seek integrative solutions that satisfy all parties' interests. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- The "Challenge Directly" axis of Radical Candor corresponds to assertiveness in TKI; the "Care Personally" axis maps to cooperativeness. +- **[Tuckman's Team Stages](../../content/skills/frameworks/tuckman-team-stages.md)** -- The "Storming" stage is where TKI becomes most relevant; teams that navigate conflict effectively transition to Norming and Performing. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the substrate on which collaborative conflict resolution depends; without it, parties default to competing or avoiding. +- **[Resolving People Conflict](../../content/skills/people/resolving-people-conflict.md)** -- Extends TKI's diagnostic framework into practical interpersonal conflict resolution techniques, including mediation approaches and de-escalation strategies. +- **[Negotiation Mindset and Self](../../content/skills/negotiation/negotiation-mindset-and-self.md)** -- The assertiveness-cooperativeness dimensions of TKI mirror the internal mindset calibration required before entering any negotiation or conflict conversation. diff --git a/plugins/foreman/skills/tipping-point/SKILL.md b/plugins/foreman/skills/tipping-point/SKILL.md deleted file mode 120000 index 875bb56..0000000 --- a/plugins/foreman/skills/tipping-point/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/tipping-point.md \ No newline at end of file diff --git a/plugins/foreman/skills/tipping-point/SKILL.md b/plugins/foreman/skills/tipping-point/SKILL.md new file mode 100644 index 0000000..ddedbf4 --- /dev/null +++ b/plugins/foreman/skills/tipping-point/SKILL.md @@ -0,0 +1,193 @@ +--- +name: "tipping-point" +description: "Analyzes viral growth potential using Gladwell's Tipping Point + framework through three rules: the Law of the Few (Connectors, Mavens, + Salespeople), the Stickiness Factor, and the Power of Context. Use when + product growth is stubbornly linear despite high satisfaction, designing + launch strategies for organic adoption, engineering shareable product moments, + identifying key influencers in a target market, or diagnosing why a superior + product fails to spread." +version: "1.0.0" +category: "frameworks" +complexity: "intermediate" +stage: + - early-traction + - growth + - scale +tags: + - virality + - growth-strategy + - network-effects + - word-of-mouth + - adoption +related_skills: + - blue-ocean-strategy + - four-ps-marketing +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Tipping Point + +In 1994, Hush Puppies sold roughly 30,000 pairs of shoes annually and the brand was effectively dead. Then a handful of hipsters in Manhattan's East Village started wearing them -- not because of any marketing campaign, but because the shoes were so uncool they had become cool. Within two years, sales hit 430,000 pairs. No advertising budget produced this result. No product redesign triggered it. A social epidemic did. Malcolm Gladwell's *The Tipping Point* (2000) anatomized this phenomenon -- the moment when an idea, trend, or behavior crosses a threshold and spreads like wildfire -- and in doing so handed entrepreneurs a vocabulary for understanding why some products ignite while others, equally worthy, smolder and die. + +--- + +## The Framework + +Gladwell identifies three governing rules of social epidemics. Each must be present for a tipping point to occur. The absence of any one can explain why a superior product fails to spread. + +### Rule 1: The Law of the Few + +Epidemics are driven by a disproportionately small number of exceptional people. Gladwell categorizes them into three archetypes: + +**Connectors** possess extraordinarily large social networks spanning multiple worlds -- technology, finance, art, media. They are the human equivalent of network hubs. When a Connector encounters your product and mentions it, the message reaches diverse, otherwise disconnected clusters simultaneously. + +**Mavens** are information specialists. They accumulate knowledge about products, prices, and places -- and they share it compulsively. Mavens do not merely know about your product; they understand how it compares to every alternative and will explain the differences to anyone who asks. They are the market's unpaid research department. + +**Salespeople** possess the charisma and persuasive skill to close the deal emotionally. Where Mavens provide the data, Salespeople provide the conviction. Their enthusiasm is contagious in the clinical sense of the word. + +The entrepreneurial implication is stark: identifying and activating even a few Connectors, Mavens, and Salespeople in your target market can matter more than a six-figure advertising budget. + +### Rule 2: The Stickiness Factor + +The message itself must be memorable enough to compel action. Gladwell draws on the history of *Sesame Street* and *Blue's Clues* to demonstrate that small, often counterintuitive adjustments to how information is presented can dramatically increase its stickiness. The lesson is not "make a better product" -- it is "make the product experience impossible to forget." + +Stickiness is not the same as quality. A technically superior product with a forgettable onboarding experience has low stickiness. A slightly inferior product with a moment of delight that users retell to friends has high stickiness. The tipping point demands both reach (the Few) and retention (Stickiness). + +### Rule 3: The Power of Context + +Human behavior is exquisitely sensitive to environmental conditions. Gladwell uses New York City's dramatic crime reduction in the 1990s -- driven partly by fixing broken windows and cleaning graffiti from subway cars -- to argue that context shapes behavior far more than character does. For entrepreneurs, this means the circumstances under which someone first encounters your product matter enormously. + +A brilliant app demonstrated at a crowded, noisy trade show booth may fail to tip. The same app discovered through a quiet recommendation from a trusted friend over coffee may become indispensable. Context is not a background variable; it is a primary lever. + +### The Epidemic Curve + +The tipping point itself occurs at the inflection where linear growth becomes exponential. Before the tip, effort feels disproportionate to results. After, results feel disproportionate to effort. Recognizing which side of the tipping point you currently occupy changes every strategic decision. + +``` +Adoption + ^ + | ___________ + | / + | / + | / <-- Tipping Point + | / + | ____________________/ + |__________/ + +-----------------------------------------> Time + [Pre-Tip: High effort, low results] [Post-Tip: Momentum carries] +``` + +--- + +## Prompts + +**Prompt 1 -- Epidemic Potential Audit:** +> Analyze my product/service [describe] for tipping point potential. Evaluate it against Gladwell's three rules: (1) Who are the Connectors, Mavens, and Salespeople in my target market of [describe market]? How could I identify and activate them? (2) What is the stickiness factor of my product -- what makes the experience memorable and retellable? (3) What contexts would be most favorable for first encounters with my product? Rate each dimension and identify the weakest link. + +**Prompt 2 -- Connector Identification Strategy:** +> Help me identify potential Connectors for my [product/service] in the [industry] space. A Connector spans multiple social worlds and has an unusually large, diverse network. Based on my target market of [describe], where would I find these people? What platforms, events, communities, or roles tend to produce Connectors? Design a strategy for reaching 10 Connectors in the next 90 days. + +**Prompt 3 -- Stickiness Redesign:** +> My product is [describe] and our current retention/engagement metrics are [share data]. Users try the product but don't come back or tell others about it. Using the Stickiness Factor principle, analyze my product experience for memorable moments, emotional peaks, and retellability. Suggest specific changes to make the experience sticky enough to spread through word of mouth. + +--- + +## Use Cases + +**Developer Tool Seeking Organic Adoption** + +An early-traction startup has built a code review tool that developers who try it genuinely love -- NPS sits at 72 -- but growth remains stubbornly linear at 5% month-over-month. A tipping point analysis reveals the problem: the tool lacks stickiness in its shareable moments. Developers enjoy using it but have no natural trigger to mention it to peers. The fix involves engineering a "share-worthy artifact" -- a beautiful, public code quality report that developers post to their repositories. This creates a visible signal that Connectors in the developer community notice and propagate. Growth triples within two quarters, and the majority of new users cite "saw it on a colleague's repo" as their discovery path. + +**Consumer Health App Pre-Launch** + +A growth-stage health-tech company preparing to launch a nutrition tracking app applies the three rules in reverse to design its launch strategy. First, they identify 50 fitness influencers who function as Connectors across health, tech, and lifestyle communities. Second, they engineer stickiness by designing a weekly "body insight" notification so surprising and personal that users screenshot and share it. Third, they optimize context by timing the launch for January -- when health motivation peaks and the context for trying new wellness tools is most favorable. The combination produces a 40x viral coefficient compared to their previous product launch. + +--- + +## Anti-Patterns + +- **Manufactured Virality.** Attempting to engineer a tipping point through paid influencer campaigns that simulate organic spread. Audiences detect inauthenticity rapidly. Gladwell's framework describes organic social dynamics, not paid amplification wearing an organic costume. The Connectors, Mavens, and Salespeople must genuinely believe in the product. + +- **Ignoring the Weakest Rule.** Founders who excel at one rule and neglect the others. A product with extraordinary stickiness but no Connector strategy stays trapped in a small enthusiast community. A product with powerful Connectors but low stickiness generates trial without retention -- the leaky bucket at scale. + +- **Premature Scaling of Promotion.** Pouring fuel on a fire that has not yet reached its tipping point. If the product lacks stickiness or the right Connectors have not been activated, amplifying reach through advertising merely accelerates the rate at which people try and forget your product. The evidence from failed viral campaigns is unambiguous: spending cannot substitute for the three rules. + +- **Confusing Tipping Points with Luck.** Dismissing the framework as describing unpredictable phenomena. While specific tipping points are hard to predict in timing, the conditions that enable them are identifiable and designable. Gladwell's contribution is precisely that epidemics follow discoverable patterns. + +- **Neglecting Context Entirely.** Assuming the product and the people are all that matter. Launching a B2B productivity tool during a company's busiest quarter, or introducing a luxury consumer product during a recession, violates the Power of Context regardless of how good the product is or how many Connectors endorse it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | Identifying the Few | The priority is finding and activating Connectors, Mavens, and Salespeople; growth is still pre-tip and requires patience | +| Growth | Engineering stickiness | Product experience must be refined for maximum memorability and retellability; this is where most tipping points either happen or don't | +| Scale | Managing the epidemic | Post-tip, the challenge shifts to maintaining quality and culture while managing exponential growth; context management becomes operational | + +--- + +## Output Template + +```markdown +# Tipping Point Analysis: [Product/Company Name] + +**Date:** [Date] +**Current Growth Rate:** [MoM or relevant metric] +**Assessment:** [Pre-Tip / Approaching Tip / Post-Tip] + +## The Law of the Few + +### Connectors Identified +- [Name/Role/Reach]: [Why they matter] +- [Name/Role/Reach]: [Why they matter] + +### Mavens Identified +- [Name/Role/Expertise]: [Why they matter] + +### Salespeople Identified +- [Name/Role/Influence]: [Why they matter] + +### Activation Strategy +[How you plan to engage these individuals] + +## The Stickiness Factor + +- **Current stickiness score:** [High/Medium/Low] +- **Most memorable product moment:** [Describe] +- **Retellability test:** Can a user explain the value in one sentence? [Yes/No] +- **Recommended stickiness improvements:** + 1. [Change] + 2. [Change] + +## The Power of Context + +- **Optimal discovery context:** [Where/when/how users should first encounter the product] +- **Current context alignment:** [Strong/Weak] +- **Context improvements:** + 1. [Change] + +## Weakest Link +[Which of the three rules is currently the bottleneck, and what to do about it] + +## 90-Day Action Plan +1. [Action targeting the weakest rule] +2. [Action reinforcing the strongest rule] +3. [Measurement criteria for tipping point proximity] +``` + +--- + +## Related Skills + +- **[Four Ps of Marketing](../../content/skills/frameworks/four-ps-marketing.md)** -- The Promotion P must incorporate tipping point dynamics rather than relying solely on paid channels; product and place decisions also shape stickiness and context. +- **[Blue Ocean Strategy](../../content/skills/frameworks/blue-ocean-strategy.md)** -- Creating uncontested market space can serve as the contextual shock that triggers a tipping point by eliminating competitive noise. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Social proof and authority principles explain the psychological mechanisms through which Connectors, Mavens, and Salespeople propagate adoption. +- **[Net Promoter Score](../../content/skills/frameworks/net-promoter-score.md)** -- Promoters in the NPS framework are the quantifiable proxy for Gladwell's enthusiasts; high NPS signals a product with the advocacy base needed to reach a tipping point. +- **[Disruptive Innovation](../../content/skills/frameworks/disruptive-innovation.md)** -- Disruptive products often reach their tipping point by serving overlooked segments first, then crossing into mainstream adoption through Gladwell's epidemic dynamics. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Activating Connectors requires the interpersonal skill of building genuine relationships across diverse networks, not transactional outreach. diff --git a/plugins/foreman/skills/tone-and-engagement/SKILL.md b/plugins/foreman/skills/tone-and-engagement/SKILL.md deleted file mode 120000 index 7c413c8..0000000 --- a/plugins/foreman/skills/tone-and-engagement/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/tone-and-engagement.md \ No newline at end of file diff --git a/plugins/foreman/skills/tone-and-engagement/SKILL.md b/plugins/foreman/skills/tone-and-engagement/SKILL.md new file mode 100644 index 0000000..4121cc6 --- /dev/null +++ b/plugins/foreman/skills/tone-and-engagement/SKILL.md @@ -0,0 +1,219 @@ +--- +name: "tone-and-engagement" +description: "Diagnoses and corrects the tonal failures that cause business writing to anaesthetise readers rather than persuade them. Addresses passive voice, nominalizations, hyperformality, sarcasm, and the specific calibration of tone to audience and relationship. Use when drafting client communications, revising documents that feel lifeless or overly formal, preparing sensitive messages that require tonal precision, or building writing standards for a team." +version: "1.1.0" +category: "writing" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - tone + - engagement + - passive-voice + - reader-focus + - business-etiquette + - plain-language +related_skills: + - grammar-and-mechanics + - writing-effective-emails + - writing-memos-and-reports + - giving-feedback +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Tone and Engagement + +Most business writing functions like chloroform. Not because the content lacks substance, but because the delivery system -- passive constructions, nominalizations, hyperformality, alphabet soup acronyms -- works with quiet efficiency to render the reader unconscious before the third paragraph. The author, having invested hours in research and analysis, packages the result in prose so anaesthetised that no one absorbs it. The irony is structural: the harder people try to sound professional, the less effectively they communicate. The antidote is not casualness. It is precision, warmth, and the discipline to write for a reader rather than at one. + +--- + +## The Framework + +### The Five Anaesthetics of Business Writing + +The framework identifies five mechanisms through which business prose loses its reader. Each operates independently, but they tend to cluster -- a document infected with one typically hosts several. + +**1. Passive Voice** + +Passive voice removes the actor from the sentence, creating prose that sounds as though events simply happened, with no one responsible. + +- *Before:* "It has been decided that the project will be restructured." +- *After:* "We have decided to restructure the project." + +Passive voice is not grammatically wrong. It is stylistically weak when used as a default. Reserve it for situations where the actor is genuinely unknown or deliberately unimportant: "The building was constructed in 1952." + +**2. Nominalizations** + +Nominalizations convert vivid verbs into abstract nouns, draining energy from every sentence they touch. + +- *Before:* "The implementation of efficiency measures by the company resulted in the generation of cost savings." +- *After:* "The company implemented efficiency measures and saved money." + +The diagnostic: look for *-tion*, *-ment*, *-ness*, and *-ity* endings. Every nominalization is a verb imprisoned in noun form. Liberate it. + +**3. Hyperformality** + +Hyperformality replaces everyday words with inflated alternatives, creating distance between writer and reader. + +| Hyperformality | Plain Alternative | +|----------------|-------------------| +| "How may I be of assistance?" | "How can I help?" | +| "Subsequent to our conversation" | "After we spoke" | +| "At your earliest convenience" | "As soon as you can" | +| "We are in receipt of" | "We've received" | +| "Pursuant to your instructions" | "As you asked" | +| "Enclosed please find" | "Here are..." | + +The test: would you say this to a colleague standing in front of you? If not, revise. + +**4. Alphabet Soup** + +Acronyms make writing easier for the writer and harder for the reader. A document dense with COGS, EBITDA, VBM, and ABC becomes a cipher that only insiders can decode. Spell out terms when the audience extends beyond specialists. The writer's shortcut is the reader's hindrance. + +**5. Abstraction Without Evidence** + +"He was a bad boss" tells the reader nothing actionable. "He got a promotion based on his assistant's detailed reports, but then denied that assistant even routine cost-of-living raises" shows the reader everything. Specifics persuade. Abstractions occupy space. + +### Calibrating Tone to Relationship + +Tone is not a fixed setting. It varies with the relationship between writer and reader. + +**Collegial, not distant.** Write as though speaking to the recipient. Use personal pronouns (*you*, *we*, *our*) rather than impersonal constructions (*the undersigned*, *it is recommended*). This does not mean casual -- it means human. + +**Warm, not sycophantic.** Brief courtesies (*thank you*, *we appreciate*) establish goodwill. Extended flattery ("I just thought I'd drop you a note to tell you just how effective I think you've been...") suggests an agenda. + +**Direct, not aggressive.** State what happened, what the effect was, and what needs to change. Never use language designed to make the reader feel stupid: *labor under a delusion*, *claim to understand*, *fail to comprehend*. + +**Professional, not sarcastic.** Sarcasm in writing lacks the vocal cues that signal humour in speech. On the page, it reads as contempt. Compare: + +- *Before:* "Given that Monday was a bank holiday, as declared by federal statute no less, your e-mail of the present month did not come to my attention until yesterday. It is with no small degree of regret that we note you deemed it necessary to send a follow-up." +- *After:* "Because Monday was a bank holiday, I didn't receive your e-mail until yesterday. Naturally I was sorry that you had to write a second time. But of course I want you to call on me whenever I might help." + +The first version drips with condescension. The second achieves the same informational content with warmth intact. + +### The "Jury Test" + +Imagine everything you write will be read aloud before a jury in a contentious lawsuit. This exercise -- recommended for all professional correspondence -- forces two disciplines: (1) precision in what you claim, and (2) collegiality in how you claim it. People have lost jobs and companies have lost cases over ill-considered letters, memos, and emails. + +### The Relevance Principle: What's In It For the Reader + +Tone calibration solves half the engagement problem -- making prose sound human rather than institutional. The other half is relevance: giving the reader a reason to care. *Writing for Busy Readers* identifies this as the "So what?" test. When readers regard a topic as personally relevant, research shows they exert more effort to understand it, read more deeply, and recall more content. When they do not see personal relevance, they skim, procrastinate, or delete -- regardless of how well-crafted the prose may be. + +The evidence is striking. In an experiment with the youth voter organisation Rock the Vote, 19,990 people received an email encouraging them to volunteer at live concerts. The writer's-perspective version used the subject line "Volunteer with Rock the Vote." The reader's-perspective version used "Want to attend free events?" The body of the reader's-perspective email added a single sentence: "You'll get to see the best shows for free and do important work at the same time!" Recipients of the reader's-perspective version were nearly four times as likely to sign up as those who received the writer's-perspective version. The two emails were otherwise identical. The difference was one subject line and one sentence -- both framed around what the reader stood to gain. + +Psychologist Richard Petty and colleagues demonstrated the same mechanism in a university setting: students who were told that *their own* college was considering a new exam requirement read the policy proposal more carefully and fully than students told that a college in another state was considering it. Personal stakes drive attention. Absent those stakes, even well-written material gets the skim treatment. + +The practical application for business writers is a two-question filter applied before sending any communication: + +1. **"So what?"** -- If the recipient were to read only the subject line and the first sentence, would they understand why this message matters *to them personally*, not merely to the organisation? +2. **"Why me?"** -- If the message is going to a group, is it clear which recipients need to act and which can safely ignore it? Generic mass communications that fail this test waste time for irrelevant recipients and get ignored by relevant ones. + +The relevance principle does not require manipulation or clickbait. It requires the writer to shift perspective -- from "what do I need to say?" to "what does the reader need to hear?" The same information, reframed around reader benefit, produces measurably higher engagement without altering the substance. A product recall notice titled "Important product safety recall information" is writer-perspective. The same notice titled "If you bought Soup XYZ in June, it has been recalled" is reader-perspective -- more targeted, more useful, and more likely to reach the people who need it. + +--- + +## Prompts + +**Prompt 1 -- Anaesthesia Diagnosis:** +> Analyse the following document for the five engagement killers: passive voice, nominalizations, hyperformality, acronym density, and abstraction without evidence. For each instance found, quote the original, identify the specific problem, and provide a revised version that preserves the meaning while improving readability. Document: [paste text] + +**Prompt 2 -- Tone Calibration:** +> I need to send a message to [describe recipient and your relationship]. The message needs to communicate [describe content]. The emotional context is [describe -- e.g., the recipient will be disappointed, the news is positive, the situation is tense]. Draft the message with appropriate tone, then explain the tonal choices you made and why they fit the relationship and context. + +**Prompt 3 -- Formality Detox:** +> Rewrite this document, replacing every instance of hyperformality with a plain-language alternative. Maintain professionalism but eliminate all language that the recipient would never hear in a face-to-face conversation. Then provide a before/after comparison for each change. Document: [paste text] + +**Prompt 4 -- Specificity Upgrade:** +> This document relies heavily on abstract claims and vague assertions. Identify every instance where a specific fact, number, name, or example would strengthen the writing. For each, suggest what kind of specific detail would be most persuasive and, where possible, draft an improved version. Document: [paste text] + +**Prompt 5 -- The "So What?" / "Why Me?" Relevance Audit:** +> Here is a communication I am about to send: [paste text]. The audience is [describe recipients]. Apply the relevance test: (1) Read the subject line and first sentence only -- does the reader immediately understand why this matters to *them*, not just to the sender? (2) If this is going to a group, is it clear which recipients need to act? (3) Identify every passage written from the writer's perspective and rewrite it from the reader's perspective, emphasising what the reader stands to gain, lose, or need to do. (4) Produce a revised version where relevance is front-loaded and the "So what?" question is answered within the first two sentences. + +--- + +## Use Cases + +**Validation-Stage Startup Rewriting Its Landing Page** +A B2B SaaS startup's landing page reads: "Our solution facilitates the optimization of operational workflows through the implementation of advanced algorithmic processes." The founder, a former management consultant, has unconsciously replicated the tone of McKinsey decks. After a tone and engagement audit, the page reads: "We help operations teams work faster by automating the steps that slow them down." Conversion rate improves 22% in the first month -- not because the product changed, but because prospective customers could finally understand what it did. + +**Growth-Stage Company Issuing a Difficult Client Communication** +A project has missed its deadline by three weeks. The project manager drafts a client email that opens: "It is with regret that we must inform you of a delay in the deliverable timeline that has been occasioned by unforeseen complications in the development process." After revision: "We owe you an update -- and an apology. The project is three weeks behind schedule because we underestimated the integration complexity. Here is our revised timeline and what we are doing to prevent a recurrence." The revised version is shorter, takes ownership, and provides actionable information. The client relationship survives. + +**Scale-Stage Organisation Standardising Communication Tone** +A 500-person company discovers, through a customer satisfaction survey, that clients describe its written communications as "corporate," "impersonal," and "hard to understand." A tone audit of 50 representative documents reveals that 73% are written primarily in passive voice, 41% use hyperformality, and the average Flesch Reading Ease score is 22 (comparable to the Harvard Law Review). The company develops a tone guide, trains its team, and raises the average readability score to 55 within six months. Customer satisfaction on "communication clarity" increases by 31 points. + +--- + +## Anti-Patterns + +1. **Confusing Casual with Engaging.** The opposite of hyperformality is not informality -- it is clarity. Replacing "subsequent to our conversation" with "hey, so about what we talked about lol" does not represent an improvement. The target is relaxed professionalism: language you would use with a respected colleague, not language you would use in a group chat. + +2. **Eliminating All Passive Voice.** Some sentences genuinely read better in passive voice, particularly when the actor is unknown or when the action matters more than the agent. "The building was evacuated" is more appropriate in an incident report than "Security guard James Johnson evacuated the building." Passive voice is a tool, not a virus. + +3. **Over-Personalising Professional Communications.** Adding warmth does not mean sharing personal details, making jokes, or using exclamation marks. A message to a client about a billing discrepancy should sound human and warm, not like a birthday card. + +4. **Tone-Deafness to Power Dynamics.** Writing with excessive familiarity to a board member or with unnecessary formality to a direct report signals either obliviousness or insecurity. Tone must account for hierarchical context, relationship history, and cultural norms. + +5. **The Sarcasm Trap.** Sarcasm in written communication is almost always a mistake. Without vocal inflection, facial expression, or shared context, sarcastic text reads as hostility. The writer intends wit; the reader perceives contempt. The gap between the two is a lawsuit waiting to happen. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Founder voice in pitches and outreach | The founder's personal tone *is* the company's tone. Warmth, directness, and clarity in investor emails and cold outreach set the pattern for all future communications. | +| Early Traction | Client-facing tone consistency | With the first paying customers, tone in proposals, onboarding emails, and support responses directly affects retention. Hyperformality signals distance; warmth signals partnership. | +| Growth | Multi-author tone alignment | Multiple team members now write on behalf of the company. Without a tone guide, each brings their own voice -- ranging from robotic to inappropriately casual. A tone framework creates consistency. | +| Scale | Organisational tone governance | At scale, tone becomes part of brand identity. Training programmes, editorial review, and tone-checking tools ensure that thousands of communications per week maintain a consistent voice. | + +--- + +## Output Template + +```markdown +# Tone and Engagement Audit: [Document Name] + +## Readability Metrics +- **Flesch Reading Ease:** [score] (target: 45-65 for business documents) +- **Average sentence length:** [number] words (target: under 20) +- **Passive voice percentage:** [number]% (target: under 15%) + +## Anaesthesia Inventory +| Issue Type | Count | Severity | +|-----------|-------|----------| +| Passive voice | [n] | [high/medium/low] | +| Nominalizations | [n] | [high/medium/low] | +| Hyperformality | [n] | [high/medium/low] | +| Acronym overload | [n] | [high/medium/low] | +| Abstract claims | [n] | [high/medium/low] | + +## Top 5 Revisions (Before/After) +1. **Before:** "[original]" --> **After:** "[revised]" +2. **Before:** "[original]" --> **After:** "[revised]" +3. **Before:** "[original]" --> **After:** "[revised]" +4. **Before:** "[original]" --> **After:** "[revised]" +5. **Before:** "[original]" --> **After:** "[revised]" + +## Tone Assessment +- **Current tone:** [e.g., "Overly formal, impersonal, bureaucratic"] +- **Recommended tone:** [e.g., "Collegial, direct, warm"] +- **Key adjustments:** [specific changes needed] +``` + +--- + +## Related Skills + +- **[Grammar and Mechanics](../../content/skills/writing/grammar-and-mechanics.md)** -- Correct grammar provides the foundation; tone determines whether grammatically correct prose actually resonates with readers. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- Email is the format where tonal miscalibration does the most frequent damage, given its speed and volume. +- **[Writing Memos and Reports](../../content/skills/writing/writing-memos-and-reports.md)** -- Reports are the documents most prone to passive voice, nominalizations, and abstraction -- the precise ailments this skill diagnoses. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- Tone influences the first two stages of reader triage; understanding how readers process emotional register explains why tonal choices have outsized impact on engagement. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- Feedback conversations require the same tonal calibration as written communications: direct without aggression, warm without vagueness. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- The balance of caring personally and challenging directly maps onto the tonal challenge of being honest without being harsh in written form. diff --git a/plugins/foreman/skills/tough-decision-situations/SKILL.md b/plugins/foreman/skills/tough-decision-situations/SKILL.md deleted file mode 120000 index f2caa0d..0000000 --- a/plugins/foreman/skills/tough-decision-situations/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/decisions/tough-decision-situations.md \ No newline at end of file diff --git a/plugins/foreman/skills/tough-decision-situations/SKILL.md b/plugins/foreman/skills/tough-decision-situations/SKILL.md new file mode 100644 index 0000000..53fc838 --- /dev/null +++ b/plugins/foreman/skills/tough-decision-situations/SKILL.md @@ -0,0 +1,280 @@ +--- +name: "tough-decision-situations" +description: "Addresses the four hardest decision scenarios founders face: teams that cannot reach consensus, choices where every option is bad, decisions that have already gone wrong, and calls that must be made under severe time pressure. Provides structured techniques for each scenario including disagree-and-commit protocols, least-worst analysis, early admission and course-correction frameworks, and recognition-primed decision heuristics. Use when the team is deadlocked and unable to converge, when all available options carry significant downside, when a prior decision has clearly failed and needs triage, when time pressure demands rapid judgment with incomplete information, or when standard decision frameworks assume conditions that do not exist." +version: "1.0.0" +category: "decisions" +complexity: "advanced" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - consensus + - deadlock + - bad-options + - wrong-decision + - time-pressure + - sunk-cost + - course-correction + - disagree-and-commit + - heuristics + - triage + - decision-recovery + - value-complexity +related_skills: + - choosing-and-executing + - evaluating-and-deciding + - decision-making-under-pressure + - scenario-planning + - learning-from-failure + - thomas-kilmann-conflict +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Tough Decision Situations + +Sometimes every option on the table is bad. The question worth asking is not "which is least bad" but "which generates the most learning for what comes next." Standard decision toolkits assume a minimum viable set of conditions: adequate time, reasonably good options, a team willing to converge, and a future that has not yet proven the decision-maker wrong. Founders operate in an environment where one or more of these conditions is frequently absent. A co-founding team deadlocked on product direction, a pricing decision where every number alienates someone, a market entry that has clearly failed, a competitive threat that demands a response by Friday -- these are not edge cases. They are the texture of entrepreneurial life. This skill provides discrete techniques for the four scenarios that defeat conventional decision frameworks. + +--- + +## The Toolkit + +### Scenario 1: The Team Cannot Reach Consensus + +Consensus is overrated. It produces decisions that reflect the lowest common denominator of the room rather than the sharpest available judgment. The goal is not agreement for its own sake; the goal is a clear decision that the entire team can execute with commitment, even when some members would have chosen differently. + +**Technique: Pre-Committed Decision Architecture** + +Before the discussion begins, define what happens if the group cannot agree. This single act transforms the dynamics of the conversation. Without a fallback mechanism, deadlocked teams simply recycle arguments. With one, participants know that indecision itself has a consequence, which concentrates attention. + +Establish the following before the meeting opens: + +1. **Time boundary.** "We will discuss this for 90 minutes. If consensus has not emerged, we move to the fallback." +2. **Fallback mechanism.** Options include: the accountable executive makes the call, the group votes (simple majority, two-thirds, or advisory), or the issue escalates with a documented majority/minority summary. +3. **Decision rights clarity.** Who has final authority? A vote can be binding or advisory. If advisory, say so before the first ballot, not after. +4. **Dissent protocol.** Dissent during the discussion is encouraged and recorded. Dissent after the decision is made is not permitted unless new material facts emerge. + +**Technique: The Closure Chart** + +Borrowed from Tom Wilson's practice at Allstate: end every decision meeting with a simple three-column chart for each open item -- "Yes," "No," or "Defer." Under "Defer," specify the exact date the decision will be made and the precise additional information or action required to move to a definitive answer. This eliminates the organisational habit of deferring without accountability. + +**Technique: Disagree-and-Commit** + +When the team is split and the deadline is real, the accountable decision-maker chooses. Those who disagreed are expected to execute the decision with the same energy as those who supported it. This is not submission; it is professionalism. The commitment is to the team's ability to learn from the decision, not to the decision's correctness. + +The protocol requires two things in return from the decision-maker: transparency about why the dissenting view was not adopted, and a defined checkpoint at which the decision will be reviewed. If the dissenters were right, the review provides a structured path to course-correction. If they were wrong, the review provides evidence that builds trust in the process. + +--- + +### Scenario 2: Choosing Between Bad Options + +Alexander George, who studied presidential decision-making, identified two forces that make some choices genuinely terrible: uncertainty (the consequences of each option are unknowable in advance) and value complexity (even the "best" choice will harm some people or undermine values the decision-maker would prefer to protect). When both forces are present, conventional pro-and-con analysis collapses under its own weight. + +**Technique: The Four Pitfall Audit** + +Before evaluating options, audit your own cognitive state. Under pressure, four predictable errors distort judgment: + +- **Avoidance.** Refusing to acknowledge the severity of the situation. The supply chain has been fragile for months, but the founder treats each disruption as an isolated incident rather than a systemic failure. +- **Fixation.** Adrenaline narrows focus to the immediate threat, obscuring the broader context. The founder spends all energy on the angry customer in front of them and ignores the structural pricing problem that created the conflict. +- **Oversimplification.** Reducing a multi-dimensional problem to a binary: win or lose, option A or option B. The reality usually contains more alternatives than the panicked mind can perceive. +- **Isolation.** Attempting to solve the problem alone, hiding it from the board, the team, or advisers until it is too late to benefit from their perspective. + +Recognise which pitfall you have fallen into before attempting to evaluate options. The pitfall itself is the first obstacle; the decision is the second. + +**Technique: Expanding the Option Set** + +When every visible option is bad, the instinct is to pick the least bad one. The better instinct is to ask whether the option set itself is complete. Three questions help: + +1. **"Can we do both?"** Binary framing is often artificial. A founder told to choose between cutting staff and cutting product scope may be able to do neither -- by raising a bridge round, renegotiating a vendor contract, or restructuring compensation. +2. **"What would a new entrant do?"** Incumbents are trapped by sunk costs and existing relationships. A thought experiment that removes those constraints often reveals options that were invisible from the inside. +3. **"What is the smallest possible experiment?"** Instead of committing to one bad option, test its least costly version. Have three salespeople call delayed customers to gauge the response before communicating a blanket delay to the full customer base. + +**Technique: Mitigating Value Complexity** + +When any decision will cause harm to some stakeholders, the founder's obligation is not to pretend the harm does not exist but to manage its impact with integrity: + +- **Name the trade-off explicitly.** "This decision will reduce commissions for the eastern sales team. That is a real cost, and I am not minimising it." +- **Compensate or offset.** Find ways to make harmed parties whole in the medium term -- preferential treatment on the next allocation, first access to the next opportunity, public recognition of their sacrifice. +- **Minimise the maximum harm.** People catastrophise. If you can credibly take the worst-case scenario off the table ("no one will lose their job over this"), you defuse the most paralysing fear, even if the remaining news is unpleasant. +- **Frame sacrifice as contribution.** Stakeholders who bear disproportionate cost should be recognised as having made a sacrifice for the organisation, not as having lost a political contest. + +--- + +### Scenario 3: You Have Made the Wrong Decision + +The evidence is mounting. The geographic expansion is haemorrhaging cash. The new hire is not performing. The product pivot has not moved the needle. At some point, optimism becomes denial and persistence becomes the sunk cost fallacy dressed in a founder's conviction. + +**Technique: The Sunk Cost Override** + +Humans are wired to protect investments already made. The antidote is a single question asked with brutal honesty: "If I were making this decision fresh today -- with no prior investment -- would I choose this path?" If the answer is no, the prior investment is irrelevant. It is gone regardless of what happens next. Continuing to invest resources in a failing direction does not recover the sunk cost; it merely adds new losses on top. + +Political capital complicates the calculation. A founder who publicly championed the expansion feels that admitting failure will damage credibility. In practice, the opposite is true. Credibility erodes far faster when a leader clings to a visibly failing initiative than when they acknowledge the mistake and redirect resources. Dorie Clark's research confirms: public, transparent admission of error -- accompanied by a clear articulation of the lesson learned -- generates more respect than quiet persistence generates sympathy. + +**Technique: The Triage Framework** + +Not every wrong decision requires full abandonment. Three paths exist: + +| Path | When to Use | Example | +|------|-------------|---------| +| **Remedy** | The decision is directionally correct but the execution is flawed. The core thesis is sound; the implementation needs adjustment. | A hire with the right attitude but wrong skills can be retrained. A market entry can be scaled back to a single-city pilot. | +| **Course-correct** | The decision addressed a real problem but chose the wrong solution. The problem still needs solving; the approach must change. | A pricing model that alienated enterprise clients can be restructured without abandoning the enterprise segment entirely. | +| **Abandon** | The decision was based on a premise that has been falsified. No amount of execution improvement can rescue it. | A product built for a market that does not exist. A partnership with an organisation whose values are fundamentally misaligned. | + +The discipline is to distinguish between these three paths honestly, without allowing ego or sunk costs to push the founder toward "remedy" when "abandon" is the correct call. + +**Technique: Extracting and Sharing the Lesson** + +Every wrong decision contains diagnostic information about the decision-maker's blind spots. The extraction process asks three questions: + +1. **Was this foreseeable?** Could better data collection, broader consultation, or more rigorous analysis have prevented the error? If yes, the lesson is about process improvement. +2. **What bias was operating?** Was the founder overconfident, anchored on an early data point, swayed by confirmation bias, or seduced by sunk costs? Identifying the specific bias makes it targetable. +3. **What decision rule would have caught this?** Formulate a concrete heuristic -- "Before committing to geographic expansion, require three months of pilot data from at least two cities" -- that can be applied to future decisions of the same type. + +Sharing the lesson publicly, whether with the team, the board, or an industry peer group, transforms a private failure into a public investment in the founder's credibility and the organisation's learning culture. + +--- + +### Scenario 4: Deciding Under Time Pressure + +Rita Gunther McGrath describes the emerging competitive landscape as one where "fast and roughly right decision making will replace deliberations that are precise and slow." The challenge is operational: how does a founder distinguish "roughly right" from "not at all right" when the clock is measured in hours rather than weeks? + +**Technique: Know-Think-Do** + +Nick Tasler's framework reduces time-pressured decisions to three steps: + +1. **Know the ultimate strategic objective.** Of the seven possible considerations competing for attention, which one or two will have the largest positive impact? Of all stakeholders, which one can the founder least afford to disappoint? Criteria overload is the primary killer of speed. Cut it to the essential variable. +2. **Think by consulting an anti-you.** Explain the situation to one person whose perspective differs from yours. The act of articulation frequently clarifies the decision before the other person responds. Their fresh viewpoint is a bonus, not the primary mechanism. +3. **Do something.** Select one option and release the others. The purpose of a decision under time pressure is not to find the perfect answer; it is to get to the next decision. In a world of irreducible uncertainty, forward motion generates data that standing still cannot. + +**Technique: Pre-Established Decision Rules** + +The fastest decisions under pressure are those that were effectively made before the pressure arrived. Founders who have defined their operating principles in advance convert real-time judgment calls into rule applications: + +- "When customer acquisition cost exceeds three times the monthly subscription value, pause the channel and investigate before spending more." +- "When two co-founders disagree on a product decision, the founder closest to the customer makes the call." +- "When a hiring decision is deadlocked after the third interview round, default to the candidate with the strongest reference from a domain expert." + +These rules are not infallible. They are heuristics that sacrifice marginal accuracy for substantial speed -- a trade-off that is almost always favourable under genuine time pressure. + +**Technique: Recognition-Primed Decisions** + +Experienced founders develop pattern libraries through repeated exposure to similar situations. Gary Klein's research on firefighters and military commanders demonstrates that experts under pressure do not compare options analytically; they recognise the situation as belonging to a familiar pattern, mentally simulate the first viable response, and act if the simulation does not reveal a fatal flaw. The implication for founders is clear: decision speed under pressure is a function of experience breadth. The more situations a founder has navigated -- or studied through case analysis, mentorship, and post-mortems -- the larger the pattern library available when the clock is ticking. + +--- + +## Prompts + +**Prompt 1 -- Deadlock Breaker:** +> My team of [number] people has been unable to reach consensus on [describe the decision] after [number] meetings. Describe the positions held by each faction. Then design a 90-minute structured decision session that includes: a time-bounded discussion, a fallback voting mechanism, and a disagree-and-commit protocol. Specify how dissent will be documented and when the decision will be reviewed. + +**Prompt 2 -- Bad Options Analyser:** +> I face a decision where every option has significant downsides: [describe options and their downsides]. For each option, identify: (a) the specific stakeholders harmed, (b) the severity and reversibility of that harm, (c) the learning value generated, and (d) one creative alternative I may not have considered. Then recommend a path forward, including mitigation strategies for the harmed stakeholders. + +**Prompt 3 -- Wrong Decision Triage:** +> I believe I made a wrong decision when I [describe the decision and the evidence of failure]. Walk me through the triage framework: is this a case for remedy, course-correction, or full abandonment? What sunk cost biases might be distorting my assessment? Draft a communication to [my team / my board / my investors] that admits the error, extracts the lesson, and outlines the revised plan. + +**Prompt 4 -- Time-Pressure Decision Protocol:** +> I need to decide [describe the decision] within [time frame]. I have access to [describe available information]. Apply the know-think-do framework: help me identify the single most important strategic objective, challenge my current thinking as an "anti-me," and recommend a specific action. Also suggest one pre-established decision rule I should adopt for future situations of this type. + +--- + +## Use Cases + +**The Deadlocked Co-Founders** + +Two co-founders of a validation-stage healthtech startup have spent six weeks arguing about whether to pursue a B2B or B2C go-to-market strategy. Each has data supporting their position; neither finds the other's evidence compelling. The advisor introduces pre-committed decision architecture: the co-founders agree that if they cannot reach consensus within one more structured 90-minute session, the CEO (the co-founder with the commercial background) will make the final call, and both will execute it for 90 days before reviewing. During the session, the act of knowing that a fallback exists changes the conversation. The commercial co-founder, confident that she holds the tiebreaker, becomes more generous in incorporating elements of the B2C thesis. The technical co-founder, knowing his position will receive a fair 90-day test regardless, engages more constructively. They converge on a B2B-first strategy with a B2C pilot embedded in the timeline. + +**The Pricing Dilemma with No Good Answer** + +A growth-stage marketplace founder must set take rates for a new seller category. A high rate maximises short-term revenue but will drive sellers to a competitor launching in three months. A low rate attracts sellers but cannibalises existing unit economics. A tiered rate adds complexity that the engineering team cannot deliver before launch. The founder applies the option-set expansion technique and discovers a fourth path: a promotional introductory rate with an explicit sunset clause, communicated transparently to sellers. The promotional rate buys data on seller behaviour, the sunset clause preserves long-term economics, and the transparency prevents a trust breach when rates eventually rise. The "no good options" framing dissolves once the artificial constraint of permanence is removed. + +**The Failed Product Launch** + +An early-traction consumer app founder invested six months and significant capital building a social feature that users are not adopting. Usage data after 60 days is unambiguous: retention curves are flat, engagement metrics are declining, and the feature has not moved the North Star metric. The founder applies the sunk cost override -- fresh-start question: would she build this feature today, knowing what she knows now? The answer is clearly no. She moves to triage and determines this is an abandon case: the premise (that social features would drive retention) has been falsified, not merely under-executed. She communicates the decision to the team with the lesson extracted: future feature bets will require a 30-day prototype with live user testing before full engineering investment. The team's morale improves; they had privately doubted the feature for weeks but lacked a framework to surface the concern. + +--- + +## Anti-Patterns + +**Consensus Worship.** Treating unanimity as a prerequisite for action rather than a fortunate bonus. In startup environments, unanimous agreement on strategic direction is rare and often indicates that the team is not thinking critically enough. Disagree-and-commit is not a consolation prize; it is often the healthiest possible outcome. + +**The Sunk Cost Sermon.** Knowing about sunk cost fallacy intellectually while succumbing to it emotionally. Every founder can recite the definition; far fewer can act on it when the sunk cost in question represents their own judgment, reputation, or years of work. The fresh-start question -- "Would I choose this today?" -- must be asked with genuine willingness to hear "no." + +**Analysis as Anaesthetic.** Requesting more data not because the data will improve the decision but because the act of gathering it delays the moment of choice. Under time pressure, this is lethal. Under bad-options conditions, it is merely expensive. In neither case is it helpful. + +**Premature Abandonment.** The mirror image of sunk cost escalation. Some founders, having been burned by persistence, overcorrect and abandon decisions at the first sign of difficulty. The triage framework exists to prevent both errors: distinguishing between decisions that need more time, decisions that need a different approach, and decisions that need to stop entirely. + +**The Heroic Loner.** Facing a tough decision situation alone, either out of pride or a belief that seeking input signals weakness. Isolation is one of the four pitfalls of uncertainty for a reason: it shrinks the option set, eliminates the corrective perspective of others, and delays the alarm until the problem is beyond intervention. The founder's advisory board, co-founders, and mentor network exist precisely for these moments. + +--- + +## By Stage + +| Stage | Primary Tough Situation | Guidance | +|-------|------------------------|----------| +| Idea | **Time pressure.** Runway is short, and the window for experimentation is measured in weeks, not quarters. | Default to the know-think-do framework. Define the single variable that matters most (usually customer signal), consult one trusted adviser, and act. Pre-establish two or three decision rules that match the venture's hypothesis -- e.g., "If the first 20 user interviews do not surface this pain point, pivot the thesis." | +| Validation | **Bad options.** The data from early experiments often presents the founder with unpalatable choices: the product works but the market is small, or the market is large but the product needs fundamental rearchitecting. | Expand the option set before choosing. Ask "can we do both?" and test the smallest viable version of each path. Apply value complexity mitigation when choices affect early employees or beta customers who took a risk on the venture. | +| Early Traction | **Consensus failure.** The founding team is growing, roles are formalising, and disagreements that were once resolved over coffee now fester across departments. | Introduce pre-committed decision architecture and the disagree-and-commit protocol. Define decision rights explicitly. The closure chart becomes a standard meeting artefact. | +| Growth | **Wrong decisions surfacing.** The volume of decisions at growth stage means that some fraction will inevitably prove wrong. The question is how quickly the organisation detects and corrects them. | Institute the triage framework as a standard operating procedure. Normalise the fresh-start question in quarterly reviews. Create a culture where admitting a wrong call is treated as a sign of intellectual honesty rather than incompetence. | +| Scale | **All four simultaneously.** At scale, the organisation faces deadlocks in cross-functional committees, structural bad-option trade-offs in resource allocation, legacy wrong decisions embedded in processes, and competitive time pressure on multiple fronts. | The founder's role shifts from making tough decisions to building systems that surface them early and resolve them quickly. Pre-established decision rules, escalation protocols, and triage frameworks must be institutionalised, not personalised. Decision quality becomes an organisational capability, not an individual skill. | + +--- + +## Output Template + +```markdown +# Tough Decision Brief: [Situation Title] + +**Date:** [YYYY-MM-DD] +**Decision Owner:** [Name and role] +**Scenario Type:** [Consensus failure / Bad options / Wrong decision / Time pressure] + +## Situation Assessment +[2-3 sentences: what happened, why standard approaches have failed, and what makes this situation genuinely difficult.] + +## Cognitive Audit +- **Pitfalls identified:** [avoidance / fixation / oversimplification / isolation -- check all that apply] +- **Biases at risk:** [sunk cost / confirmation / anchoring / overconfidence -- check all that apply] +- **Fresh-start test result:** [Would I make this same decision/choice today? Yes/No/Uncertain] + +## Options Evaluated +| Option | Upside | Downside | Stakeholders Harmed | Learning Value | Reversibility | +|--------|--------|----------|---------------------|----------------|---------------| +| [A] | | | | | | +| [B] | | | | | | +| [C] | | | | | | + +## Decision and Rationale +[The chosen path and the reasoning behind it, including which trade-offs were accepted and why.] + +## Harm Mitigation Plan +| Stakeholder Affected | Nature of Harm | Mitigation Action | Timeline | +|---------------------|----------------|-------------------|----------| +| | | | | + +## Lesson Extracted +- **What went wrong (if applicable):** [root cause] +- **Bias or process gap identified:** [specific] +- **Decision rule for the future:** [concrete heuristic] + +## Review Checkpoint +**Date:** [YYYY-MM-DD] +**Criteria for success/failure:** [specific, measurable] +``` + +--- + +## Related Skills + +- **[Choosing and Executing](../../content/skills/decisions/choosing-and-executing.md)** -- The companion skill covering the fundamentals of moving from deliberation to action; this skill takes over when conditions are too adverse for standard approaches. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- Provides the analytical foundation of criteria weighting, margin of safety, and irreversibility testing that this skill extends into hostile conditions. +- **[Decision-Making Under Pressure](../../content/skills/leadership/decision-making-under-pressure.md)** -- Overlaps with Scenario 4 but addresses the broader emotional and cognitive dynamics of high-stakes leadership moments. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Pre-mortem and scenario analysis can prevent some tough decision situations from arising; when they arise regardless, this skill provides the response toolkit. +- **[Learning from Failure](../../content/skills/leadership/learning-from-failure.md)** -- Extends the lesson-extraction techniques of Scenario 3 into a comprehensive organisational learning practice. +- **[Thomas-Kilmann Conflict Model](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- Provides the interpersonal framework for navigating the disagreements that underlie Scenario 1 consensus failures. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- The Inner Citadel concept provides the philosophical grounding for maintaining judgment quality when all available options are bad and emotional pressure is intense. diff --git a/plugins/foreman/skills/trust-equation/SKILL.md b/plugins/foreman/skills/trust-equation/SKILL.md deleted file mode 120000 index 102b8b0..0000000 --- a/plugins/foreman/skills/trust-equation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/trust-equation.md \ No newline at end of file diff --git a/plugins/foreman/skills/trust-equation/SKILL.md b/plugins/foreman/skills/trust-equation/SKILL.md new file mode 100644 index 0000000..eb89400 --- /dev/null +++ b/plugins/foreman/skills/trust-equation/SKILL.md @@ -0,0 +1,258 @@ +--- +name: "trust-equation" +description: "Diagnoses and builds trust using Maister's Trust Equation: Trust = (Credibility + Reliability + Intimacy) / Self-Orientation. Evaluates each variable with evidence-based scoring and prescribes targeted improvements. Use when losing investor confidence, experiencing customer churn despite strong product, repairing damaged stakeholder relationships, preparing fundraising trust strategies, or auditing team trust dynamics." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - trust + - relationships + - credibility + - leadership + - sales +related_skills: + - radical-candor + - carnegie-win-friends + - cialdini-influence + - giving-feedback +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Trust Equation + +``` + Credibility + Reliability + Intimacy +Trust = ────────────────────────────────────── + Self-Orientation +``` + +Four variables. One fraction. The most elegant decomposition of trust in the management literature. David Maister, Charles Green, and Robert Galford published this formula in *The Trusted Advisor* (2000), and its power lies in making the abstract concrete and the intuitive actionable. Trust is not a mystical quality some people possess and others lack. It is a function of four measurable, improvable variables -- three in the numerator, one in the denominator. Increase any numerator variable and trust rises. Increase the denominator and trust collapses, regardless of how strong the numerator is. The formula explains why brilliant consultants lose clients, why technically competent founders alienate investors, and why likeable managers fail to inspire confidence. It also prescribes, with unusual precision, exactly what to fix. + +--- + +## The Framework + +### The Numerator: Three Trust Builders + +#### Credibility: "I Can Trust What They Say" + +Credibility is the confidence that the other party knows what they are talking about. It operates on two dimensions: expertise (actual knowledge and skill) and communication of expertise (the ability to convey competence without arrogance). + +**Credibility markers:** +- Demonstrated domain knowledge +- Relevant credentials and track record +- Accuracy of prior statements and predictions +- Ability to say "I don't know" when appropriate -- paradoxically, admitting ignorance on peripheral topics increases perceived credibility on core topics +- Third-party validation (endorsements, publications, case studies) + +**How founders build credibility:** +- Publish original analysis of their market +- Reference specific data points and primary research in pitches +- Acknowledge the limits of their knowledge ("our hypothesis is X; we are testing it by doing Y") +- Build a track record of accurate forecasts in investor updates + +**How founders destroy credibility:** +- Overstating traction or market size +- Claiming expertise in domains where they lack it +- Failing to update stakeholders when prior predictions prove wrong +- Using jargon as a substitute for understanding + +#### Reliability: "I Can Trust What They Do" + +Reliability is the confidence that the other party will do what they say they will do. While credibility is about words, reliability is about actions repeated over time. It is the trust variable most dependent on consistency. + +**Reliability markers:** +- Promises kept -- especially small ones +- Deadlines met +- Follow-through on commitments made in meetings +- Predictable behaviour in varied circumstances +- Transparency about what can and cannot be delivered + +**How founders build reliability:** +- Under-promise and over-deliver systematically +- Send investor updates on the same day every month without exception +- Respond to communications within a predictable window +- Track and honour every commitment, no matter how minor ("I'll send you that article" matters) + +**How founders destroy reliability:** +- Missing self-imposed deadlines +- Changing direction frequently without explanation +- Making commitments in the enthusiasm of a meeting and failing to follow through +- Inconsistency between what is said in different contexts (telling the board one story and the team another) + +#### Intimacy: "I Can Trust Them With My Concerns" + +Intimacy is the confidence that sharing sensitive information -- concerns, fears, failures, uncertainties -- is safe. This is the most emotionally complex trust variable and the one most often neglected in professional contexts. + +**Intimacy markers:** +- Discretion with confidential information +- Emotional safety -- the other party does not judge, mock, or weaponise vulnerability +- Willingness to engage with feelings, not just facts +- Reciprocal vulnerability ("I'm worried about this too") +- Non-transactional concern for the other person's wellbeing + +**How founders build intimacy:** +- Share appropriate personal vulnerabilities ("this keeps me up at night") +- Honour confidences absolutely -- never use information shared in trust as leverage +- Acknowledge the emotional dimension of business decisions +- Remember and reference personal details about stakeholders +- Create psychological safety in team settings + +**How founders destroy intimacy:** +- Sharing confidential information with third parties +- Responding to vulnerability with judgment or dismissal +- Maintaining a purely transactional demeanour +- Using personal information strategically + +### The Denominator: The Trust Destroyer + +#### Self-Orientation: "Are They in This for Themselves?" + +Self-orientation is the degree to which the other party appears focused on their own interests rather than yours. It is the denominator -- the single variable with the power to nullify an otherwise strong trust position. A person can be highly credible, perfectly reliable, and genuinely intimate, but if they appear self-serving, trust evaporates. + +**Self-orientation signals:** +- Talking more than listening +- Redirecting conversations to their own interests +- Offering solutions before fully understanding the problem +- Name-dropping and status-signalling +- Visibly calculating "what's in it for me" in every interaction +- Rushing to close rather than ensuring genuine fit + +**How founders reduce self-orientation:** +- Listen before prescribing. In investor meetings, ask about the investor's thesis and portfolio before pitching. +- In sales conversations, spend the first third understanding the customer's situation before mentioning the product +- Refer prospects to competitors when the fit is genuinely poor +- Give useful advice and introductions with no expectation of reciprocation +- In team settings, credit others and share recognition generously + +**The denominator trap for founders:** Entrepreneurship selects for high self-orientation. Founders must be driven, ambitious, and focused on their company's success -- traits that can easily read as self-serving to investors, customers, and employees. The discipline is not reducing ambition but ensuring that interactions demonstrate genuine concern for the other party's interests alongside one's own. + +### The Mathematics of Trust + +The formula's structure reveals several non-obvious insights: + +1. **Self-orientation has disproportionate impact.** Because it is in the denominator, doubling self-orientation halves trust, regardless of numerator strength. Conversely, halving self-orientation doubles trust. No numerator improvement can compensate for high self-orientation. + +2. **Credibility alone is insufficient.** The brilliant but unreliable founder (high credibility, low reliability) is a common archetype -- visionary but untrustworthy. Investors learn to discount vision when execution track record is poor. + +3. **Reliability alone is insufficient.** The dependable but uninspiring operator (high reliability, low credibility, low intimacy) earns respect but not trust. People follow them because they deliver, not because they believe. + +4. **Intimacy is the most undervalued variable.** In professional contexts, intimacy is often dismissed as "soft." Yet it explains why people trust their accountant of twenty years over a more credentialed stranger, and why customers stick with a slightly inferior product sold by a vendor who understands their real concerns. + +5. **Trust is situation-specific.** A person may be highly trusted in one domain (technical decisions) and not in another (hiring). The equation should be applied per-context, not as a global score. + +--- + +## Prompts + +**Prompt 1 -- Trust Diagnostic:** +> Using the Trust Equation (T = (C + R + I) / S), assess my trustworthiness with a specific stakeholder. The stakeholder is [describe -- investor, cofounder, key customer, board member]. Rate myself on each variable (Credibility, Reliability, Intimacy, Self-Orientation) with evidence, not aspiration. Identify which variable is my weakest and design three specific actions to improve it over the next 30 days. + +**Prompt 2 -- Trust Repair:** +> I have lost trust with [describe the person and context]. The triggering event was [describe]. Using the Trust Equation, diagnose which variable(s) were damaged. Was it a credibility failure (I said something wrong), a reliability failure (I didn't do what I said), an intimacy failure (I betrayed a confidence or dismissed their concerns), or a self-orientation failure (I appeared to prioritise myself)? Then design a trust repair strategy targeting the specific variable(s) affected. + +**Prompt 3 -- Investor Trust Strategy:** +> I am preparing for a fundraising round. Using the Trust Equation, design a comprehensive trust-building strategy for investor relationships. For each variable (Credibility, Reliability, Intimacy, Self-Orientation), identify specific actions I should take before, during, and after investor meetings. My company: [describe stage, traction, prior fundraising history]. + +**Prompt 4 -- Team Trust Audit:** +> I manage a team of [size]. Using the Trust Equation, assess the current trust level within the team -- both trust in me as a leader and trust between team members. For each variable, identify observable indicators and potential improvement areas. Design a 90-day plan to increase team trust, with specific actions mapped to each variable. + +**Prompt 5 -- Customer Trust Analysis:** +> Analyse why we are losing customers to [competitor] despite having a superior product. Apply the Trust Equation to our customer relationships versus the competitor's. Rate both on Credibility, Reliability, Intimacy, and Self-Orientation from the customer's perspective. Identify which trust variable(s) the competitor outperforms us on and recommend specific changes to our customer success approach. + +--- + +## Use Cases + +**Idea-Stage Founder Seeking Pre-Seed Investment** +A first-time founder with no track record pitches angel investors and receives polite passes. Trust Equation diagnosis: Credibility is low (no prior exits, limited domain expertise), Reliability is unproven (no track record of delivering), Intimacy is minimal (investors do not know them), and Self-Orientation appears high (pitch is entirely about the founder's vision, not the investor's thesis). The remediation strategy targets each variable: build credibility through a published market analysis and customer interviews (demonstrating expertise); establish reliability by committing to monthly updates to interested angels even before an investment; develop intimacy by asking investors about their portfolio challenges and offering introductions; and reduce self-orientation by explicitly addressing how the investment fits the investor's thesis, not just the founder's ambition. Second fundraising attempt succeeds. + +**Growth-Stage Company with High Churn Despite Strong Product** +A B2B SaaS company with best-in-class technology loses 25% of customers annually. Trust Equation analysis from customer interviews reveals: Credibility is high (customers trust the product), Reliability is low (support response times are inconsistent, and promised features are frequently delayed), Intimacy is absent (customers feel like ticket numbers, not partners), and Self-Orientation is moderate (upsell pressure in every interaction). The intervention focuses on Reliability (SLAs with consequences for missed response times, public roadmap with delivery dates) and Intimacy (dedicated success managers, quarterly business reviews, proactive check-ins not tied to renewals). Churn drops to 12% in two quarters. + +**Scale-Stage CEO Navigating a Board Crisis** +A CEO learns that two board members are discussing their replacement after a missed quarterly target. Trust Equation diagnosis reveals the critical variable is Self-Orientation: the CEO has been perceived as optimising for their personal reputation (announcing ambitious targets publicly) rather than for honest company stewardship. Reliability is also damaged (the missed target follows two prior misses). The repair strategy: a board letter acknowledging the pattern, reforecasting conservatively, and committing to a reporting format that highlights risks alongside opportunities. The CEO explicitly addresses their own accountability, reducing perceived self-orientation. Within two board cycles, the replacement discussion dissipates. + +--- + +## Anti-Patterns + +1. **Optimising Only the Numerator.** Investing in credibility (more credentials, better pitches), reliability (better processes), and intimacy (more networking) while ignoring self-orientation. The denominator can single-handedly destroy trust. A founder who is brilliant, reliable, and personable but clearly in it only for themselves will not be trusted. + +2. **Confusing Reliability with Responsiveness.** Responding to every message within five minutes is not reliability; it is reactivity. Reliability means doing what you said you would do, when you said you would do it. An immediate response that fails to follow through is worse than a delayed response that delivers. + +3. **Performing Intimacy.** Sharing vulnerability strategically -- "I'll tell them about my struggles to seem human" -- is detectable and counterproductive. Performative vulnerability increases perceived self-orientation ("they're using vulnerability as a tactic"), which is the opposite of the intended effect. + +4. **Assuming Trust Transfers Across Domains.** A founder trusted for technical decisions assumes they are equally trusted for commercial ones. Trust is context-specific. The equation must be evaluated per-domain and per-stakeholder, not as a universal score. + +5. **Ignoring the Time Dimension.** Trust is built incrementally and destroyed instantly. A single reliability failure can undo months of consistent delivery. The equation captures a point-in-time assessment; the trajectory matters more than any single snapshot. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Credibility building from zero | With no track record, founders must build credibility through domain expertise, quality of thinking, and borrowed credibility (advisors, prior employers). Self-orientation must be visibly low -- investors are pattern-matching for coachability. | +| Validation | Reliability establishment | Validation is the trust-building phase: every commitment met, every update sent on time, every promise honoured. This is when the founder's reliability track record begins, and early impressions compound. | +| Early Traction | Intimacy with early customers | Early customers are taking a risk on an unproven company. Intimacy -- making them feel heard, safe, and valued -- determines whether they become advocates or cautionary tales. | +| Growth | Scaling trust across relationships | At growth, the founder cannot personally maintain trust with every stakeholder. Trust must be embedded in organisational practices: reliable processes, credible teams, customer intimacy at scale. | +| Scale | Institutional trust | At scale, trust becomes a brand attribute. The trust equation applies to the organisation, not just the founder: corporate credibility, operational reliability, customer intimacy, and perceived self-orientation (profit motive vs. customer mission). | + +--- + +## Output Template + +```markdown +# Trust Assessment: [Stakeholder/Relationship] + +## Trust Equation Score +| Variable | Rating (1-10) | Evidence | Improvement Priority | +|----------|---------------|----------|---------------------| +| Credibility (C) | [Score] | [What demonstrates or undermines credibility] | [High/Med/Low] | +| Reliability (R) | [Score] | [Track record of commitments kept/broken] | [High/Med/Low] | +| Intimacy (I) | [Score] | [Depth of personal connection and safety] | [High/Med/Low] | +| Self-Orientation (S) | [Score] | [Signals of self-interest vs. genuine concern] | [High/Med/Low] | + +## Calculated Trust Level +- Numerator (C + R + I): [Sum] +- Denominator (S): [Score] +- Trust Index: [Numerator / Denominator] +- Interpretation: [High / Moderate / Low / Critical] + +## Weakest Variable Analysis +- **Variable:** [The lowest-performing variable or highest self-orientation] +- **Root cause:** [Why this variable is weak] +- **Impact:** [How this weakness manifests in the relationship] + +## 30-Day Trust Building Plan +| Week | Action | Target Variable | Expected Impact | +|------|--------|----------------|-----------------| +| 1 | [Specific action] | [C/R/I/S] | [Expected change] | +| 2 | [Specific action] | [C/R/I/S] | [Expected change] | +| 3 | [Specific action] | [C/R/I/S] | [Expected change] | +| 4 | [Specific action] | [C/R/I/S] | [Expected change] | + +## Trust Maintenance Protocol +- [Ongoing practices to sustain trust] +``` + +--- + +## Related Skills + +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- Radical Candor requires a trust foundation to function; the Trust Equation diagnoses whether that foundation exists and prescribes how to build it when it does not. +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principles are, in Trust Equation terms, a systematic methodology for building all three numerator variables while minimising the denominator. +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- The credibility and intimacy variables of the Trust Equation determine whether feedback is received as development or attack. +- **[Win-Win Negotiation](../../content/skills/frameworks/win-win-negotiation.md)** -- Trust is the lubricant of principled negotiation; high trust enables the vulnerability required to share interests, generate options, and defer to objective criteria. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Building the intimacy variable of the Trust Equation requires the relational skills of authentic connection, active listening, and genuine curiosity about others. +- **[Stoic Right Action](../../content/skills/stoic/stoic-right-action.md)** -- Consistently acting with integrity regardless of audience is the Stoic path to low self-orientation, the denominator variable that most powerfully determines trustworthiness. diff --git a/plugins/foreman/skills/tuckman-team-stages/SKILL.md b/plugins/foreman/skills/tuckman-team-stages/SKILL.md deleted file mode 120000 index def5341..0000000 --- a/plugins/foreman/skills/tuckman-team-stages/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/tuckman-team-stages.md \ No newline at end of file diff --git a/plugins/foreman/skills/tuckman-team-stages/SKILL.md b/plugins/foreman/skills/tuckman-team-stages/SKILL.md new file mode 100644 index 0000000..f9c77ff --- /dev/null +++ b/plugins/foreman/skills/tuckman-team-stages/SKILL.md @@ -0,0 +1,196 @@ +--- +name: "tuckman-team-stages" +description: "Diagnoses team development stage using Tuckman's five-phase model: Forming, Storming, Norming, Performing, and Adjourning. Prescribes stage-appropriate leadership actions and identifies progression barriers. Use when a new team is struggling to gel, conflict emerges after initial politeness, teams regress after adding new members, post-acquisition integration stalls, or leaders need to facilitate productive storming rather than suppress it." +version: "1.0.0" +category: "frameworks" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - team-development + - team-dynamics + - group-process + - collaboration + - conflict-management +related_skills: + - belbin-team-roles + - hackman-enabling-conditions + - lewin-leadership-styles + - situational-leadership +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Tuckman's Stages of Team Development + +Everyone remembers their first week on a new team. The excessive politeness. The careful self-presentation. The unspoken questions -- who holds the real power here, whose opinion matters, where are the landmines? Then, some weeks later, the first real disagreement. Someone challenges someone else's idea a little too sharply. Alliances form. Resentments surface. And then -- if the team survives this phase -- something shifts. Roles clarify. Communication shortcuts develop. The team begins producing work that none of its members could have produced alone. + +Bruce Tuckman observed this pattern across hundreds of studies in 1965 and named it with four words that have since entered the management lexicon: Forming, Storming, Norming, Performing. He added a fifth stage, Adjourning, in 1977. The model is deceptively simple. Its power lies not in novelty but in normalizing what every team member instinctively feels: that conflict, confusion, and renegotiation are not signs of failure. They are the architecture of team maturation. The teams that skip the storm do not reach the performance. + +--- + +## The Framework + +Tuckman's model describes a sequential journey through five stages. While the sequence is predictable, the duration and intensity of each stage vary enormously depending on team composition, leadership, task complexity, and organizational context. + +### Stage 1: Forming + +**The experience:** Cautious optimism mixed with anxiety. Team members are polite, guarded, and oriented toward the leader for direction. Conversations are superficial. Everyone is assessing: the task, the other members, the norms, the power dynamics. + +**What's happening beneath the surface:** Individuals are testing boundaries without appearing to test them. Questions are asked obliquely. Disagreements are suppressed. Productivity is low because energy is directed toward social navigation rather than task execution. + +**Leadership need:** High direction, low delegation. The leader must provide structure, clarify goals, define roles, and establish initial working norms. This is Lewin's directive leadership and Hersey-Blanchard's S1 (Directing) in action. + +**Duration signal:** Forming ends when team members stop asking "Who are these people?" and start asking "How should we work together?" + +### Stage 2: Storming + +**The experience:** The politeness cracks. Disagreements emerge about goals, roles, working methods, and interpersonal dynamics. Subgroups form. Some members vie for influence. Others withdraw. Frustration rises. Morale typically dips. + +**What's happening beneath the surface:** This is the necessary -- and often painful -- process of establishing authentic relationships, honest communication, and real role differentiation. The artificial consensus of Forming is replaced by genuine negotiation. Teams that suppress Storming do not skip it; they delay it, often until the stakes are much higher. + +**Leadership need:** Facilitation, not suppression. The leader's job is to normalize conflict as productive, mediate without taking sides, and hold the team to its task when interpersonal friction threatens to become the primary focus. Attempting to eliminate Storming through authority ("Let's all just get along") drives it underground, where it corrodes trust invisibly. + +**Duration signal:** Storming ends when disagreements shift from personal ("You're wrong") to procedural ("We need a better process for this"). + +### Stage 3: Norming + +**The experience:** Cohesion forms. The team develops shared standards for how decisions are made, how conflicts are resolved, how work is reviewed, and how communication flows. In-group language and rituals appear. Members express genuine appreciation for each other's strengths. Trust deepens. + +**What's happening beneath the surface:** The team is writing its operating manual -- mostly unconsciously. Norms established in this phase persist for the team's lifetime unless deliberately renegotiated. Good norms (candid feedback, shared accountability) produce high performance. Bad norms (avoiding difficult conversations, deferring to the loudest voice) calcify into dysfunction. + +**Leadership need:** Coaching and reinforcement. The leader should explicitly name the good norms emerging and gently redirect the problematic ones. This is the highest-leverage moment for shaping team culture. + +**Duration signal:** Norming ends when the team begins operating on its norms automatically rather than consciously. + +### Stage 4: Performing + +**The experience:** The team is fully functional. Members work autonomously and interdependently with equal comfort. Decisions happen fluidly. Conflict is addressed quickly and constructively. The team solves problems at a level beyond the sum of individual capabilities. + +**What's happening beneath the surface:** Psychological safety is high. Role clarity is complete. Communication is efficient because shared context and trust eliminate the need for constant clarification. Energy flows toward the task rather than toward managing relationships or navigating politics. + +**Leadership need:** Delegation and obstacle removal. The leader's most valuable contribution is protecting the team from external disruptions and providing resources. Over-leading a Performing team is as destructive as under-leading a Forming one. + +**Duration signal:** Performing persists until a significant disruption -- a member departure, a scope change, a reorganization -- resets the team to an earlier stage. + +### Stage 5: Adjourning + +**The experience:** The team disbands upon completing its mission. Members may feel loss, anxiety about the next assignment, or satisfaction at what was accomplished. Often overlooked, this stage carries real emotional and organizational consequences. + +**What's happening beneath the surface:** Individuals are mourning the loss of a high-functioning team and potentially dreading the return to Forming with a new group. Knowledge and process insights developed during the team's life are at risk of being lost. + +**Leadership need:** Celebration, knowledge capture, and transitional support. The leader should facilitate a retrospective that captures what the team learned, celebrate the accomplishment publicly, and support members' transitions to their next teams. + +--- + +## Prompts + +**Prompt 1 -- Team Stage Diagnosis:** +> Based on the following description of my team's current dynamics, identify which Tuckman stage we're in and what leadership approach I should be using. Team context: [team size, how long they've worked together, recent changes]. Current behaviors: [describe communication patterns, conflict level, decision-making speed, quality of output, morale indicators]. Provide specific evidence for your stage assessment and actionable recommendations for what I should do differently. + +**Prompt 2 -- Storming Navigation Strategy:** +> My team is in the Storming stage. The specific conflicts are: [describe]. Some team members are withdrawing while others are becoming aggressive. I'm tempted to [describe your instinct -- e.g., "lay down the law," "reorganize the team," "avoid the conflict and hope it passes"]. Evaluate my instinct against Tuckman's model and design a facilitation approach that moves the team through Storming productively rather than suppressing or prolonging it. + +**Prompt 3 -- New Team Member Integration:** +> I'm adding [number] new members to an existing team of [size] that was previously in the [stage] stage. Using Tuckman's model, predict how this change will affect the team's stage progression. What regression should I expect? How can I accelerate the team's return to Performing while properly integrating the new members? Design an onboarding approach informed by Tuckman's stages. + +**Prompt 4 -- Multiple Team Stage Assessment:** +> I manage [number] teams across [function]. For each team, here's a brief description of their current dynamics: [describe each team]. Map each team to their Tuckman stage and prioritize which teams need the most leadership attention. For teams stuck in unproductive stages, recommend interventions. + +--- + +## Use Cases + +**Post-Acquisition Team Integration** + +A growth-stage startup acquires a smaller company and merges the two engineering teams. Leadership assumes the merged team will hit the ground running since both teams were previously Performing. Instead, the merged team resets to Forming -- new interpersonal dynamics, competing technical standards, unresolved questions about whose approach prevails. Within three weeks, Storming arrives with particular intensity because both subgroups carry the confidence and norms of formerly high-performing teams. Understanding Tuckman prevents the leadership from misinterpreting this friction as a "cultural mismatch" requiring organizational separation. Instead, they invest in facilitated workshops where the merged team explicitly negotiates new shared norms, accelerating the passage through Storming and into Norming. Within two months, the merged team achieves a Performing level that surpasses either predecessor team. + +**Remote Team Struggling with Permanent Forming** + +A validation-stage startup with a fully remote team of eight has been together for six months but never seems to gel. Conversations remain formal. Disagreements are avoided or handled in private DMs. Decision-making defaults to the founder on everything. A Tuckman analysis reveals the team is stuck in Forming. Remote work makes Storming harder to initiate -- there are fewer spontaneous interactions where genuine disagreement naturally surfaces. The founder deliberately creates structured opportunities for productive conflict: anonymous pre-meeting feedback, explicit "disagree and commit" decision protocols, and paired working sessions where team members must collaborate closely enough for real friction to emerge. The team enters Storming within two weeks -- uncomfortable but necessary. + +--- + +## Anti-Patterns + +- **Pathologizing Storming.** Interpreting conflict as evidence that the team has the wrong people rather than recognizing it as a necessary developmental stage. Leaders who reorganize teams at the first sign of Storming doom every subsequent team to the same premature dissolution. Storming is not the disease; it is the immune response. + +- **Performing Nostalgia After Disruption.** Expecting a team that was previously Performing to maintain that level after a significant change (new member, new scope, departing leader). Any material disruption resets the team to an earlier stage. Leaders who refuse to acknowledge the regression create frustration by demanding Performing-level output from a team that is re-Forming. + +- **Confusing Norming with Performing.** Mistaking team harmony for team effectiveness. A team in Norming may feel good -- relationships are warm, conflict is manageable, norms are settling -- but it is not yet producing its best work. Performing requires the norms to become invisible scaffolding, not a conscious preoccupation. Leaders who declare victory at Norming leave performance gains on the table. + +- **Forced Acceleration Through Stages.** Attempting to skip or compress stages through team-building exercises, personality assessments, or motivational speeches. Stages can be facilitated but not bypassed. A two-day offsite does not substitute for the organic process of trust development through shared work and resolved conflict. + +- **Ignoring Adjourning.** Disbanding teams without closure. Knowledge is lost. Emotional residue carries into the next team. High performers who bonded during Performing feel abandoned when the team is dissolved without acknowledgment. The cost of skipping Adjourning is paid in the next team's Forming stage, which begins with cynicism rather than cautious optimism. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founding team Forming/Storming | Co-founder relationships accelerate through stages rapidly due to intensity of early-stage work; unresolved Storming at this stage becomes existential | +| Validation | Rapid iteration through stages | Pivot decisions can reset the team to earlier stages; the team must learn to move through Forming-Storming quickly | +| Early Traction | Managing multiple concurrent stages | New hires push some relationships back to Forming while existing relationships may be at Performing; the leader manages a patchwork | +| Growth | Team proliferation | Multiple teams at different stages require different leadership approaches simultaneously; middle managers must understand the model | +| Scale | Institutional knowledge of team development | Tuckman becomes part of the organizational vocabulary; teams are supported through stages by design, not by accident | + +--- + +## Output Template + +```markdown +# Team Stage Assessment: [Team Name] + +**Date:** [Date] +**Team Size:** [Number] +**Time Together:** [Duration] +**Recent Changes:** [New members, departures, scope changes] + +## Current Stage: [Forming / Storming / Norming / Performing / Adjourning] + +### Evidence +- [Observable behavior 1 that supports this diagnosis] +- [Observable behavior 2] +- [Observable behavior 3] + +### Stage-Appropriate Leadership Actions +1. [Action aligned with current stage needs] +2. [Action aligned with current stage needs] +3. [Action aligned with current stage needs] + +## Progression Barriers +- [What is preventing the team from advancing to the next stage] +- [What intervention would address this barrier] + +## Team Health Indicators + +| Indicator | Current State | Expected at Current Stage | Concern? | +|-----------|--------------|--------------------------|----------| +| Conflict frequency | [Low/Medium/High] | [Expected level] | [Yes/No] | +| Decision speed | [Slow/Moderate/Fast] | [Expected level] | [Yes/No] | +| Psychological safety | [Low/Medium/High] | [Expected level] | [Yes/No] | +| Output quality | [Below/At/Above potential] | [Expected level] | [Yes/No] | + +## 30-Day Plan +- **Week 1:** [Focus area] +- **Week 2:** [Focus area] +- **Week 3-4:** [Focus area and reassessment] +``` + +--- + +## Related Skills + +- **[Belbin Team Roles](../../content/skills/frameworks/belbin-team-roles.md)** -- Belbin explains the composition of the team; Tuckman explains the developmental journey that composition undertakes, and role conflicts identified by Belbin often surface during the Storming stage. +- **[Hackman's Enabling Conditions](../../content/skills/frameworks/hackman-enabling-conditions.md)** -- Hackman's conditions create the structural prerequisites for a team to move through Tuckman's stages effectively; without them, teams stall in Forming or Storming. +- **[Lewin's Leadership Styles](../../content/skills/frameworks/lewin-leadership-styles.md)** -- The appropriate Lewin style shifts as the team progresses through Tuckman's stages: directive for Forming, facilitative for Storming, democratic for Norming and Performing. +- **[Situational Leadership](../../content/skills/frameworks/situational-leadership.md)** -- Hersey-Blanchard's model complements Tuckman by addressing individual development levels within the team's collective stage. +- **[Thomas-Kilmann Conflict](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- The Storming stage is where conflict modes matter most; TKI provides the diagnostic for choosing whether to compete, collaborate, compromise, avoid, or accommodate during team friction. +- **[Team Culture and Dynamics](../../content/skills/leadership/team-culture-and-dynamics.md)** -- The norms established during Tuckman's Norming stage become the team's operating culture; this skill provides the tools for shaping those norms deliberately. diff --git a/plugins/foreman/skills/understanding-people/SKILL.md b/plugins/foreman/skills/understanding-people/SKILL.md deleted file mode 120000 index 6b5212e..0000000 --- a/plugins/foreman/skills/understanding-people/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/people/understanding-people.md \ No newline at end of file diff --git a/plugins/foreman/skills/understanding-people/SKILL.md b/plugins/foreman/skills/understanding-people/SKILL.md new file mode 100644 index 0000000..345c379 --- /dev/null +++ b/plugins/foreman/skills/understanding-people/SKILL.md @@ -0,0 +1,210 @@ +--- +name: "understanding-people" +description: "Applies modern personality-decoding and rapid-understanding techniques to entrepreneurial relationships. Covers the Enneagram as a superior alternative to Myers-Briggs for self-awareness and team communication, the discipline of getting anyone even when chemistry is absent, three-question rapid-understanding for first meetings, being interested rather than interesting, and addressing the pervasive loneliness that shapes professional interactions. Use when building cofounder relationships, conducting customer discovery, onboarding new hires, preparing for investor meetings, or diagnosing communication breakdowns within teams." +version: "1.0.0" +category: "people" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - personality-assessment + - enneagram + - listening + - self-awareness + - empathy + - first-meetings + - rapport +related_skills: + - meeting-the-right-people + - reading-people + - connecting-with-people + - carnegie-win-friends + - cialdini-influence + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Understanding People + +Myers-Briggs is a party game. The Enneagram is a real tool. The difference matters. + +Myers-Briggs assigns people to one of sixteen types based on binary preferences. Take the test twice and there is a meaningful probability of receiving a different result. The assessment measures states, not traits -- and states shift with mood, context, and Tuesday's weather. The Enneagram, by contrast, identifies nine core motivational patterns that remain stable over time because they measure *what drives behaviour*, not what behaviour looks like on a given afternoon. For entrepreneurs, who must read cofounders across years and investors across minutes, the distinction between a parlour-trick classification and a stable motivational map is the distinction between guesswork and strategy. + +Self-awareness is the prerequisite for influence. Until the founder understands her own motivational architecture -- why she says yes to everything (Type 3), why she avoids conflict at the cost of clarity (Type 9), why she hoards information as a form of control (Type 5) -- her attempts to understand others will be filtered through distortions she cannot see. + +--- + +## The Framework + +Understanding people operates on three progressively deeper levels. Each level builds on the one before it, and all three are required for genuine interpersonal effectiveness. + +### Level 1: Understand Yourself First (The Enneagram) + +The Enneagram identifies nine core types, each defined by a dominant motivation and a characteristic pitfall. + +| Type | Core Drive | Common Pitfall | Entrepreneurial Manifestation | +|------|-----------|----------------|-------------------------------| +| 1 | Striving to be perfect | Rigid standards paralysing progress | Founder who cannot ship an MVP because "it's not ready" | +| 2 | Striving to be connected | Over-giving, boundary collapse | Cofounder who cannot say no to any request from team or customers | +| 3 | Striving to be outstanding | Saying yes to everything, burnout | CEO who accepts every speaking invitation while the company drifts | +| 4 | Striving to be unique | Emotional volatility, envy of competitors | Founder who pivots product based on aesthetic vision rather than data | +| 5 | Striving to be detached | Information hoarding, isolation | Technical cofounder who builds in silence and resents interruption | +| 6 | Striving to be secure | Analysis paralysis, worst-case fixation | Operator who cannot commit to a pricing model without twelve spreadsheets | +| 7 | Striving to be excited | Shiny-object syndrome, half-finished projects | Serial entrepreneur who launches five things and finishes none | +| 8 | Striving to be powerful | Bulldozing team, alienating partners | Founder whose "intensity" is a euphemism for intimidation | +| 9 | Striving to be peaceful | Conflict avoidance, passive agreement | CEO who tells every board member what they want to hear | + +The Enneagram does not change over time the way Myers-Briggs results do. The founder who is a Type 3 at twenty-five will be a Type 3 at forty-five. What changes is the *relationship* to the type: awareness of the pitfall enables rewriting the internal script. The Type 3 who recognises the "I'll Do It" syndrome can learn that saying no to some commitments produces more outstanding outcomes in the ones that remain. + +### Level 2: Get Anyone (The Coffee Experiment) + +Understanding people who are naturally likeable requires no technique. The real test is understanding people who provoke frustration, confusion, or outright dislike. Every entrepreneur has a "John" -- the business partner, board member, or key client who seems impervious to rapport. The instinctive response is to label them ("I just don't get him") and route around them. The label, however, is not a diagnosis. It is a resignation that guarantees the relationship will never improve. + +The method is deceptively simple: + +1. **Refuse the narrative.** Stop saying "I don't get him." The declaration itself becomes a self-fulfilling prophecy -- a closed cognitive loop that prevents new information from entering. +2. **Invest fifteen minutes and five dollars.** Take the difficult person for coffee outside the professional context. The shift in environment reduces defensive posture on both sides. +3. **Ask questions, then shut up and listen.** The objective is not to like the person. It is to understand what drives them -- which Enneagram type they approximate, what their formative experiences were, why they behave as they do. + +Understanding does not require agreement or affection. A founder who understands that a difficult board member is a Type 8 driven by fierce independence (often rooted in early-life adversity) can work with that knowledge strategically -- framing proposals as challenges rather than requests, for instance -- even if personal warmth never develops. The coffee meeting is not therapy. It is reconnaissance. Thirty minutes and a five-dollar espresso frequently yield more strategic intelligence than months of frustrated guesswork. + +### Level 3: Rapid Understanding (The Three-Question Method) + +Standard networking questions -- "Where are you from?" "What do you do?" -- yield standard, forgettable answers. Larry Benet's three-question framework replaces small talk with questions that reveal values, aspirations, and identity in under three minutes: + +1. **What is the most exciting thing you are working on right now?** (Reveals current passion and professional direction.) +2. **If you had enough money to retire and then some, what would you be doing?** (Reveals intrinsic motivation stripped of financial necessity.) +3. **What is your favourite charity to support, and why?** (Reveals values and emotional commitments.) + +These questions work because they bypass the social scripts people recite on autopilot and engage the deeper structures of identity. A founder who uses these in a first meeting will remember that conversation years later -- and more critically, the other person will remember being understood. + +The technique generalises beyond Benet's specific trio. Any question that targets values, aspirations, or emotional commitments will outperform biographical data collection. Ten alternative questions serve the same function: + +- What is the most exciting thing in your personal life right now? +- If you were not doing what you do today, what would you be doing and why? +- Other than a family member, who has been your most important influence? +- How would your favourite teacher describe you? +- What would you choose to do for a day if there were no constraints? + +The principle is consistent: replace "where" and "what" questions (which elicit facts) with "why" and "how" questions (which elicit identity). The shift takes three seconds of deliberate intention and produces a fundamentally different quality of conversation. + +### The Substrate: Loneliness and Connection + +Most people are lonely. Even the most outwardly successful, well-adjusted individuals carry stretches of disconnection that shape how they respond to someone who genuinely listens. The founder who approaches people with authentic intent to understand and connect differentiates herself from the vast majority of professionals, who are too preoccupied with their own concerns to focus on others. When the founder fills that void -- even for twenty minutes over a charged phone -- a disproportionate reciprocity often follows. Not because the listener was calculating, but because genuine connection is so rare that people remember and reward it instinctively. + +The Carnegie principle -- "be interested, not interesting" -- remains the single most efficient interpersonal technique available. Humans love to talk about themselves. Neuroscience confirms that self-disclosure activates the brain's reward centres. The person who listens attentively, asks follow-up questions, and resists the urge to redirect the conversation to their own story will be remembered as extraordinary -- despite having said almost nothing. + +Carnegie articulated this in 1936. The framework updates it for an era of performative self-promotion on social media, where the incentive structure rewards broadcasting over receiving. The modern founder faces a paradox: every platform encourages her to be interesting (post content, build a following, project expertise), while every meaningful relationship rewards her for being interested (ask questions, listen deeply, let the other person feel significant). The resolution is not to abandon the public persona but to ensure that in private interactions -- the ones that actually determine whether investors, partners, and employees say yes -- listening dominates speaking by a ratio no smaller than three to one. + +--- + +## Prompts + +**Prompt 1 -- Enneagram Team Mapping:** +> My cofounding team consists of [describe 2-4 people with brief behavioural descriptions]. Based on these descriptions, estimate each person's likely Enneagram type. For each, identify the core motivation, the predictable pitfall in a startup context, and one specific communication adjustment I should make when working with that person. Flag any type combinations that are likely to produce friction and suggest a mitigation strategy. + +**Prompt 2 -- Difficult Relationship Decoding:** +> I am struggling to work productively with [describe the person, their role, and specific frustrating behaviours]. Using the Enneagram framework and the "get anyone" method, help me (1) hypothesise what motivates this person's behaviour, (2) design a low-stakes interaction outside our normal context to test that hypothesis, and (3) prepare three questions I can ask during that interaction that will reveal whether my hypothesis is correct. + +**Prompt 3 -- First-Meeting Question Design:** +> I have a [15/30/60]-minute first meeting scheduled with [describe the person and context]. Design a sequence of questions that will move quickly past small talk and reveal this person's values, motivations, and potential alignment with my venture. The questions should feel natural, not interrogative, and should be calibrated to the formality of the setting. + +**Prompt 4 -- Self-Awareness Audit:** +> Based on the following description of my typical behaviours and tendencies [provide description], identify my likely Enneagram type. Then list three specific situations in my entrepreneurial journey where my type's characteristic pitfall is most likely to cause problems, and provide a concrete rewrite of the internal script for each situation. + +--- + +## Use Cases + +**Idea-Stage Founder Choosing a Cofounder** + +A technical founder (likely Type 5 -- detached, analytical, information-hoarding) is evaluating two potential cofounders for a fintech venture. By mapping each candidate against the Enneagram, she identifies that Candidate A is a Type 3 (outstanding, driven, prone to overcommitment) and Candidate B is a Type 8 (powerful, direct, prone to bulldozing). Rather than choosing based on chemistry, she evaluates which pitfall pattern is more manageable alongside her own. A Type 5 paired with a Type 8 will produce direct, uncomfortable conversations about strategy -- which is productive friction. A Type 5 paired with a Type 3 risks two people working furiously in parallel without genuine communication. She chooses Candidate B and structures their working relationship around weekly "coffee experiments" to maintain mutual understanding as pressure increases. + +**Validation-Stage Founder in Customer Discovery** + +A consumer-health startup founder uses the three-question method during a networking dinner with potential early adopters. Instead of pitching her product, she asks each person at the table: "What is the most frustrating thing about managing your health right now?" and "If you had unlimited resources, what would you change about your daily routine?" Two responses reveal a latent pain point she had not considered -- medication tracking for elderly parents -- which becomes a feature that drives her first thousand sign-ups. She never would have heard it through a survey. The questions created the conditions for people to reveal what they actually care about, not what they think a founder wants to hear. + +**Growth-Stage CEO Diagnosing a Dysfunctional Leadership Team** + +A CEO notices that leadership meetings have become performative -- people agree in the room and disagree in the corridor. She administers the Enneagram to her six direct reports and discovers the team is heavily skewed toward Types 3, 6, and 9: achievers who fear failure, loyalists who fear uncertainty, and peacemakers who fear conflict. The team's composition creates a structural incentive to avoid hard conversations. She redesigns the meeting format to begin with a two-minute silence followed by the three-question method applied to a business challenge: "What is the most exciting thing about this quarter?" "If resources were unlimited, what would we do differently?" "What is the one thing we are avoiding discussing?" The shift from performative updates to values-revealing questions surfaces the real issues within three meetings. + +--- + +## Anti-Patterns + +1. **Using the Enneagram as a Label Gun.** Assigning types to colleagues and then using those types to dismiss behaviour -- "Oh, that's just his Type 8 talking" -- rather than to understand and adapt. The Enneagram is a communication tool, not a sorting hat. The moment it becomes an excuse to stop trying, it has failed. + +2. **Listening as Performance.** Sitting in silence while mentally rehearsing what to say next is not listening. Active listening requires genuine cognitive engagement with what the other person is saying. The difference is detectable. People know when they are being heard and when they are being waited out. + +3. **Forced Vulnerability in Professional Settings.** Asking the three deep questions at a formal investor pitch or a first board meeting. Context matters. Rapid-understanding techniques work in networking events, coffee meetings, and retreats. They misfire in settings where professional distance is expected and where premature intimacy reads as boundary violation. + +4. **Projecting Your Own Motivations.** Assuming that because *you* would respond well to direct feedback, everyone else will too. The entire premise of understanding people is that motivational structures differ. The Type 9 who needs gentle framing will not respond to the bluntness that energises a Type 8. + +5. **Treating Understanding as Agreement.** Understanding why a toxic investor behaves as they do does not obligate tolerance. Comprehension is a strategic asset. It does not require submission. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cofounder selection | At the idea stage, the relationship between cofounders *is* the company. Enneagram mapping and the coffee experiment are cofounder due diligence -- cheaper than a term sheet and more predictive than a resume. | +| Validation | Customer discovery | Rapid-understanding questions applied to potential customers reveal motivations that structured interviews miss. "If money were no object, how would you solve this problem?" surfaces latent needs. | +| Early Traction | Hiring and culture | Administering the Enneagram to the first ten hires establishes a shared vocabulary for communication and conflict. The investment pays compound interest as the team grows. | +| Growth | Leadership development | The CEO's self-awareness becomes the ceiling for the organisation's emotional maturity. Growth-stage founders who have not confronted their own Enneagram pitfalls will reproduce those pitfalls in the culture. | +| Scale | Institutional empathy | At scale, understanding people cannot depend on the founder's personal attention. The techniques must be embedded in management training, onboarding, and meeting design so that the organisation itself listens. | + +--- + +## Output Template + +```markdown +# People-Understanding Audit: [Your Name / Company] + +## Self-Assessment +- **Enneagram type:** [Type and core drive] +- **Primary pitfall in current context:** [Specific behaviour pattern] +- **Script rewrite:** [New internal narrative] + +## Key Relationship Map +| Person | Role | Estimated Type | Core Drive | Communication Adjustment | +|--------|------|---------------|------------|-------------------------| +| [Name] | [Role] | [Type] | [Drive] | [Specific change] | + +## Difficult Relationship Plan +- **Person:** [Name] +- **Current friction:** [Description] +- **Hypothesis:** [Estimated type and motivation] +- **Planned interaction:** [Coffee experiment details] +- **Questions to ask:** [3 specific questions] + +## First-Meeting Protocol +- **Default opening questions:** + 1. [Question targeting current passion] + 2. [Question targeting intrinsic motivation] + 3. [Question targeting values] +- **Context adjustments:** [How questions change for investors vs. hires vs. customers] + +## 30-Day Practice Goals +1. [Specific listening practice commitment] +2. [Specific Enneagram application] +3. [Specific difficult-relationship initiative] +``` + +--- + +## Related Skills + +- **[Meeting the Right People](../../content/skills/people/meeting-the-right-people.md)** -- Understanding people is the prerequisite; this sibling skill addresses how to find and filter the right people to understand in the first place. +- **[Reading People](../../content/skills/people/reading-people.md)** -- Understanding operates at the motivational level; reading people adds the nonverbal and behavioural layer that reveals what words alone conceal. +- **[Connecting with People](../../content/skills/people/connecting-with-people.md)** -- Understanding creates the map; connecting applies the Platinum Rule and validation techniques that transform understanding into genuine relationship. +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's 1936 principle of genuine interest is the foundation modernised here with specific techniques and the Enneagram. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Goleman's self-awareness domain provides the theoretical architecture; the Enneagram provides the practical assessment tool. +- **[Myers-Briggs Type Indicator](../../content/skills/frameworks/myers-briggs-type-indicator.md)** -- Provides an alternative personality framework that complements the Enneagram for understanding how people process information and make decisions. diff --git a/plugins/foreman/skills/vuca-framework/SKILL.md b/plugins/foreman/skills/vuca-framework/SKILL.md deleted file mode 120000 index ca8d560..0000000 --- a/plugins/foreman/skills/vuca-framework/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/vuca-framework.md \ No newline at end of file diff --git a/plugins/foreman/skills/vuca-framework/SKILL.md b/plugins/foreman/skills/vuca-framework/SKILL.md new file mode 100644 index 0000000..6804849 --- /dev/null +++ b/plugins/foreman/skills/vuca-framework/SKILL.md @@ -0,0 +1,228 @@ +--- +name: "vuca-framework" +description: "Classifies unpredictable environments into four distinct dimensions -- Volatility, Uncertainty, Complexity, and Ambiguity -- each requiring a different strategic response: Vision, Understanding, Clarity, and Agility respectively. Use when navigating regulatory grey zones, responding to sudden competitive disruption, reducing operational complexity during scaling, designing rapid experimentation programmes under ambiguity, or building organizational resilience." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - strategy + - uncertainty + - risk-management + - adaptability + - scenario-planning + - resilience +related_skills: + - thinking-fast-and-slow + - psychological-safety + - growth-mindset + - emotional-intelligence +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# VUCA Framework + +The acronym was born in the corridors of the U.S. Army War College in the late 1980s, coined to describe the strategic environment emerging after the Cold War's binary certainties dissolved. VUCA -- Volatility, Uncertainty, Complexity, Ambiguity -- was the military's attempt to name what had changed: the enemy was no longer a single, knowable superpower with predictable doctrine but a shifting landscape of asymmetric threats, non-state actors, and cascading second-order effects that defied traditional planning. By the mid-2000s, the business world had adopted the framework wholesale, recognising that the same structural forces transforming warfare were transforming markets. Bob Johansen of the Institute for the Future reframed VUCA's four threats as four matching leadership competencies -- Vision, Understanding, Clarity, Agility -- converting a diagnostic tool into a response framework. For entrepreneurs, who operate in environments where volatility is the baseline and uncertainty is the business model, VUCA provides something more valuable than a label for chaos: it provides a taxonomy that distinguishes between different types of unpredictability, each of which demands a different strategic response. + +--- + +## The Framework + +### The Four Dimensions of VUCA + +The critical insight of the VUCA framework is that "unpredictable" is not a single condition. Volatility, uncertainty, complexity, and ambiguity are distinct phenomena that overlap but require different responses. Conflating them -- treating all unpredictability as the same kind of problem -- produces strategies that address the wrong dimension. + +**V -- Volatility** + +The nature and speed of change. Volatile environments feature rapid, significant shifts whose individual direction may be unpredictable but whose general character (turbulence) is known. + +- **Characteristics:** Fast-moving changes, unstable but not necessarily complex, information is available but the situation shifts before it can be fully exploited +- **Startup examples:** Currency fluctuations for international SaaS, viral social media dynamics, sudden competitor launches, rapid regulatory changes +- **Response -- Vision:** Build slack into systems. Maintain reserves (cash, capacity, optionality). Invest in speed of response rather than prediction accuracy. A vision -- a clear, compelling picture of the destination -- provides the stable reference point that allows rapid tactical adaptation without strategic drift. + +**U -- Uncertainty** + +The lack of predictability about events and their outcomes. The basic structure of the environment is understood, but cause-and-effect relationships are unclear, making forecasting unreliable. + +- **Characteristics:** Known unknowns; information exists but is incomplete, conflicting, or hard to interpret; outcomes of actions are not reliably predictable +- **Startup examples:** Market sizing for genuinely novel products, customer adoption curves for disruptive technologies, outcome of regulatory review for new business models +- **Response -- Understanding:** Invest in information gathering: customer research, competitive intelligence, expert networks, scenario planning. The antidote to uncertainty is not certainty (which is unavailable) but structured understanding of the range of possible outcomes and their relative likelihoods. + +**C -- Complexity** + +The multiplicity of interconnected parts and variables. Complex environments feature many moving pieces whose interactions produce emergent, non-linear outcomes that are difficult to predict even with complete information. + +- **Characteristics:** Many interdependent variables, cause-and-effect relationships are discoverable but only in retrospect, small changes can produce disproportionate effects, expertise in one dimension does not guarantee understanding of the whole +- **Startup examples:** Multi-sided marketplace dynamics, supply chain management across geographies, navigating simultaneous regulatory frameworks, building products that integrate multiple technology stacks +- **Response -- Clarity:** Simplify where possible. Build modular systems that isolate complexity. Develop specialists who understand specific domains and generalists who understand the connections between them. Clarity -- the ability to make sense of the chaos -- requires not more information but better frameworks for interpreting the information already available. + +**A -- Ambiguity** + +The lack of clarity about meaning. In ambiguous environments, even the nature of the problem is unclear. The "unknown unknowns" reside here: threats and opportunities that cannot be anticipated because the categories for understanding them do not yet exist. + +- **Characteristics:** Causal relationships are completely unclear, no precedent exists, multiple interpretations of the same data are equally plausible, "What is actually happening?" is the defining question +- **Startup examples:** Entering entirely new market categories, technology paradigm shifts (AI, blockchain, quantum), customer behaviour in unprecedented conditions (pandemic, economic crisis), interpreting contradictory product-market fit signals +- **Response -- Agility:** Run small experiments rapidly. Test hypotheses with minimum resource commitment. Build organisational capacity for rapid learning and pivot. Agility is not the absence of planning but the willingness to abandon plans when new information renders them obsolete. + +### The VUCA Matrix: Diagnosis to Response + +| VUCA Dimension | Diagnostic Question | Strategic Response | Operational Priority | +|---------------|--------------------|--------------------|---------------------| +| **Volatility** | "How fast and dramatically is the situation changing?" | Build reserves and response speed | Cash buffers, agile operations, scenario readiness | +| **Uncertainty** | "How much do we know about what is likely to happen?" | Gather information and model scenarios | Customer research, competitive intelligence, expert advisory | +| **Complexity** | "How many interconnected variables are we managing?" | Simplify, modularise, develop expertise | Architecture redesign, specialist hiring, decision frameworks | +| **Ambiguity** | "Do we even understand the nature of the problem?" | Experiment rapidly and learn | MVPs, pilots, hypothesis testing, fast feedback loops | + +### Johansen's VUCA Prime (Response Framework) + +Bob Johansen proposed a matching response acronym: + +- **V**olatility is countered by **V**ision -- a clear sense of direction that remains stable while tactics adapt +- **U**ncertainty is countered by **U**nderstanding -- investing in information, scenario planning, and sense-making +- **C**omplexity is countered by **C**larity -- cutting through noise to identify the essential drivers and simplest viable responses +- **A**mbiguity is countered by **A**gility -- the organisational capacity to experiment, learn, and pivot rapidly + +The elegance of VUCA Prime is that it converts a diagnosis into a prescription: once a founder identifies which VUCA dimension dominates their current challenge, the response category is clear. + +--- + +## Prompts + +**Prompt 1 -- VUCA Situation Diagnosis:** +> Analyse the following situation through the VUCA framework: [describe the challenge -- market conditions, competitive dynamics, regulatory environment, internal uncertainty]. Rate each VUCA dimension (Volatility, Uncertainty, Complexity, Ambiguity) on a 1-10 scale with specific evidence. Identify which dimension is dominant and recommend the corresponding strategic response (Vision, Understanding, Clarity, or Agility). Be specific about what that response looks like operationally for a [stage] company in [sector]. + +**Prompt 2 -- Scenario Planning Under Uncertainty:** +> We face significant uncertainty about [describe uncertain factor -- e.g., "whether our enterprise sales cycle will be 3 months or 12 months," "whether the regulation will pass," "whether the market will consolidate"]. Build three scenarios (optimistic, base case, pessimistic) with specific assumptions, timeline, and implications for our business. For each scenario, recommend pre-committed actions (what we do regardless), contingent actions (what we do if specific signals appear), and the specific signals to monitor. Include a decision tree with trigger points. + +**Prompt 3 -- Complexity Reduction:** +> Our business has become operationally complex across these dimensions: [list -- e.g., "4 product lines, 3 customer segments, 2 geographies, compliance with 5 regulatory frameworks, dependencies on 8 third-party integrations"]. Map the complexity using the VUCA framework. Identify which elements are genuinely complex (interconnected, non-linear) versus merely complicated (many parts but predictable). Recommend a simplification strategy that reduces complexity without sacrificing strategic capability. Specifically, what should we stop doing, modularise, or outsource? + +**Prompt 4 -- Ambiguity Navigation:** +> We are experiencing genuine ambiguity about [describe -- e.g., "whether our product is in the HR-tech category or the productivity-tool category," "whether our declining engagement means product-market fit is eroding or we have an onboarding problem," "what the emergence of [technology] means for our business model"]. Design a rapid experimentation programme to reduce this ambiguity. For each experiment, define: hypothesis, method, minimum sample size, timeline, success/failure criteria, and the decision each result would trigger. + +--- + +## Use Cases + +**Validation-stage startup in a regulatory grey zone** + +A fintech startup is building a product that falls between existing regulatory categories. The regulatory environment is deeply ambiguous: the company does not know whether it will be classified as a bank, a money transmitter, or a technology platform -- and neither, apparently, do the regulators. The VUCA diagnosis reveals that ambiguity is the dominant dimension (the nature of the regulatory requirement is itself unclear), with moderate complexity (multiple regulatory bodies with overlapping jurisdictions) and low volatility (regulatory change is slow). The prescribed response is agility: rather than seeking definitive regulatory clarity before launching (which could take years), the company designs a minimum viable compliance architecture that satisfies the strictest plausible interpretation, launches in a limited geography as a regulatory pilot, and engages proactively with regulators to shape -- rather than react to -- the eventual classification. The experimental approach produces a regulatory relationship that yields favourable classification 14 months later. + +**Growth-stage marketplace hit by sudden competitor entry** + +A two-sided marketplace with strong regional traction discovers that a well-funded global competitor has entered its market with aggressive pricing. The VUCA diagnosis: high volatility (the competitive landscape has shifted rapidly), moderate uncertainty (the competitor's strategy is partially visible through their public actions but their long-term commitment to the market is unknown), and low ambiguity (the threat is clear). The prescribed response is vision plus understanding: the CEO articulates a clear vision for why the company's deep local knowledge and existing relationships create defensible value that a global entrant cannot replicate quickly (vision provides the stable reference point), while simultaneously investing in competitive intelligence to understand the entrant's strategy, burn rate, and likely persistence (understanding reduces uncertainty). The company avoids panic-driven price-matching -- which would destroy unit economics -- and instead doubles down on its differentiated value proposition while monitoring the competitor's signals for commitment or retreat. + +**Scale-stage company navigating AI disruption** + +A 1,000-person professional services firm recognises that generative AI threatens its core business model but cannot determine whether the threat is existential or merely transformative. The VUCA diagnosis: extreme ambiguity (no precedent for this type of disruption in professional services), high complexity (AI interacts with every service line, talent strategy, pricing model, and client relationship differently), moderate uncertainty (general direction is clear but timing and magnitude are not), and moderate volatility (the technology landscape shifts monthly). The response is multi-dimensional: agility (launch five internal AI pilot projects across different service lines), clarity (hire a Chief AI Officer to synthesise learnings and simplify the strategic narrative), understanding (commission research on client willingness to pay for AI-augmented services), and vision (the CEO articulates a ten-year vision that positions AI as an amplifier of human expertise rather than a replacement). The portfolio approach ensures the company learns rapidly without betting the organisation on a single interpretation of the disruption. + +--- + +## Anti-Patterns + +**1. Treating all uncertainty as the same.** The most common misapplication of any uncertainty framework is collapsing all four VUCA dimensions into a single sensation of "things are unpredictable." This produces generic responses ("we need to be more agile") that miss the specific nature of the challenge. A complexity problem requires clarity and simplification; throwing agility at it produces more chaos, not less. + +**2. Using VUCA as an excuse for strategic paralysis.** "The environment is too VUCA to plan" is a cop-out. VUCA does not argue against planning; it argues for a specific type of planning -- one that incorporates scenarios, maintains optionality, and builds adaptive capacity. The absence of a plan in a VUCA environment is not flexibility; it is drift. + +**3. Overreacting to volatility.** Volatile environments tempt leaders into constant strategic adjustment -- changing direction with every market shift. This produces the organisational equivalent of seasickness. The VUCA response to volatility is vision -- a stable strategic direction that absorbs tactical turbulence -- not continuous pivoting. + +**4. Seeking certainty before acting.** In genuinely uncertain or ambiguous environments, waiting for certainty is waiting forever. The VUCA framework explicitly prescribes action under uncertainty: structured experimentation, scenario planning, and information gathering. Certainty is the output of these processes, not their prerequisite. + +**5. Applying peacetime frameworks to wartime conditions.** Detailed five-year plans, lengthy approval processes, and consensus-driven decision-making are appropriate for low-VUCA environments. Importing them into high-VUCA conditions produces dangerously slow organisations. The VUCA assessment should trigger a corresponding adjustment in decision-making speed, approval thresholds, and planning horizons. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Navigating market and product ambiguity | The dominant VUCA dimension is typically ambiguity; the response is rapid experimentation to reduce unknown unknowns | +| Early Traction | Managing uncertainty about scalability and market dynamics | Uncertainty dominates as the company transitions from "does this work?" to "how big is this?"; scenario planning becomes essential | +| Growth | Handling increasing organisational complexity | Complexity emerges as the company adds products, markets, teams, and processes; the response is structural clarity and modularisation | +| Scale | Addressing volatility in mature competitive markets | At scale, volatility (competitive moves, market shifts, technological disruption) becomes the primary VUCA dimension; vision and reserves provide stability | + +The VUCA profile of a startup shifts systematically as it matures. At validation, nearly everything is ambiguous -- the customer, the product, the market, the model. The appropriate organisational posture is maximally experimental: small bets, rapid iteration, minimum viable everything. + +At early traction, ambiguity partially resolves (the product works for these customers in this way) but uncertainty increases (will it scale? how fast? what competition will emerge?). The posture shifts from pure experimentation to structured scenario planning and information gathering. + +At growth, complexity becomes the dominant challenge. The organisation itself generates complexity through departmentalisation, process proliferation, and multi-market operations. The response is relentless simplification and clarity: clear decision rights, modular architecture, and ruthless prioritisation. + +At scale, the company has built sufficient structure to manage complexity but faces volatility from external forces: competitive dynamics, technological disruption, regulatory change, macroeconomic shifts. The response is maintaining strategic vision as a stabilising force while building the reserves (cash, talent, optionality) to absorb shocks without panic-driven overreaction. + +--- + +## Output Template + +```markdown +# VUCA Assessment -- [Situation/Decision/Market] + +**Prepared for:** Board / Investors +**Date:** [Date] +**Scope:** [What is being assessed] + +## VUCA Profile + +| Dimension | Rating (1-10) | Key Evidence | Trend | +|-----------|--------------|-------------|-------| +| Volatility | [Score] | [Specific evidence of change speed/magnitude] | [Increasing/Stable/Decreasing] | +| Uncertainty | [Score] | [Specific knowledge gaps] | [Increasing/Stable/Decreasing] | +| Complexity | [Score] | [Interconnected variables identified] | [Increasing/Stable/Decreasing] | +| Ambiguity | [Score] | [Unresolvable interpretation gaps] | [Increasing/Stable/Decreasing] | + +**Dominant dimension:** [Which VUCA element is primary] +**Prescribed response category:** [Vision / Understanding / Clarity / Agility] + +## Scenario Analysis (for Uncertainty dimension) + +| Scenario | Probability | Key Assumptions | Business Impact | Pre-committed Actions | Contingent Actions | Trigger Signal | +|----------|------------|----------------|-----------------|----------------------|-------------------|----------------| +| Optimistic | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | +| Base | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | +| Pessimistic | [%] | [Assumptions] | [Impact] | [Actions] | [Actions] | [Signal] | + +## Complexity Map +[List interconnected variables and their key relationships] +- [Variable A] affects [Variable B] through [mechanism] +- [Variable C] and [Variable D] interact to produce [emergent effect] + +**Simplification opportunities:** [What can be decoupled, modularised, or eliminated] + +## Experimentation Programme (for Ambiguity dimension) + +| Experiment | Hypothesis | Method | Timeline | Success Criteria | Decision if Confirmed | Decision if Refuted | +|-----------|-----------|--------|----------|-----------------|----------------------|-------------------| +| [Exp 1] | [H1] | [Method] | [Weeks] | [Criteria] | [Action] | [Action] | + +## Strategic Response + +### Vision Statement (stable reference point) +[One paragraph articulating the stable strategic direction that absorbs tactical volatility] + +### Reserves and Buffers +- Cash runway buffer: [months beyond base-case need] +- Capacity buffer: [% of team not allocated to committed work] +- Strategic options maintained: [list of preserved optionalities] + +### Adaptive Mechanisms +- Decision review cadence: [frequency] +- Environmental scan cadence: [frequency] +- Pivot criteria: [specific conditions that would trigger strategic change] +``` + +--- + +## Related Skills + +- **[Thinking, Fast and Slow](../../content/skills/frameworks/thinking-fast-and-slow.md)** -- High-VUCA environments amplify every cognitive bias Kahneman identified; the planning fallacy and overconfidence bias are particularly dangerous when uncertainty is extreme. +- **[Psychological Safety](../../content/skills/frameworks/psychological-safety.md)** -- Navigating VUCA requires organisations where people can surface problems, challenge assumptions, and admit uncertainty without penalty; Edmondson's framework provides the cultural infrastructure for VUCA response. +- **[Scenario Planning](../../content/skills/frameworks/scenario-planning.md)** -- Scenario planning is the primary strategic tool for the Uncertainty dimension of VUCA, constructing multiple plausible futures and stress-testing strategy against each. +- **[Emotional Intelligence](../../content/skills/frameworks/emotional-intelligence.md)** -- Leading through VUCA demands exceptional self-regulation (managing personal anxiety without transmitting it to the team) and empathy (recognising that uncertainty affects different people differently). +- **[Leader Resilience and Wellbeing](../../content/skills/leadership/leader-resilience-and-wellbeing.md)** -- Sustained VUCA exposure depletes leaders; resilience practices prevent the burnout and decision fatigue that high-unpredictability environments generate. +- **[Stoic Fortitude and Resilience](../../content/skills/stoic/stoic-fortitude-and-resilience.md)** -- Stoic practices for enduring difficulty without reactivity provide the psychological foundation for leading through volatile and ambiguous conditions without panic. diff --git a/plugins/foreman/skills/wanting-what-matters/SKILL.md b/plugins/foreman/skills/wanting-what-matters/SKILL.md deleted file mode 120000 index 84023ac..0000000 --- a/plugins/foreman/skills/wanting-what-matters/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/thinking/wanting-what-matters.md \ No newline at end of file diff --git a/plugins/foreman/skills/wanting-what-matters/SKILL.md b/plugins/foreman/skills/wanting-what-matters/SKILL.md new file mode 100644 index 0000000..8a5845f --- /dev/null +++ b/plugins/foreman/skills/wanting-what-matters/SKILL.md @@ -0,0 +1,214 @@ +--- +name: "wanting-what-matters" +description: "Addresses the meta-question behind all decision-making: whether the entrepreneur is optimising for the right things. Covers the hedonic treadmill and 'happy-when' trap, Dickens's A Christmas Carol as a decision-making parable, what happiness research from the elderly consistently reveals, memento mori as a practical decision filter (the deathbed test), the regret-minimisation framework, and the distinction between ordinary moments and defining moments. Use when a founder suspects they are chasing metrics that do not produce satisfaction, when strategic priorities feel misaligned with personal values, when mortality awareness could sharpen decision-making, or when the question shifts from 'how do I get what I want?' to 'is what I want worth wanting?'" +version: "1.0.0" +category: "thinking" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - purpose + - hedonic-treadmill + - mortality + - regret-minimisation + - happiness + - values + - ordinary-moments + - wisdom + - deathbed-test + - phronesis +related_skills: + - evaluating-and-deciding + - defining-and-exploring-problems + - stoic-mortality-and-perspective + - stoic-acceptance-amor-fati + - purpose-driven-leadership + - focus-and-priority-management +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Wanting What Matters + +DEATHBED TEST. The clearest decision-making tool is not a matrix or a framework -- it is asking what you would regret not having done from your deathbed. Jeff Bezos used precisely this test when deciding whether to leave a comfortable Wall Street career to start an online bookstore in 1994: "I knew that when I was 80 I was not going to regret having tried. I was not going to regret trying to participate in this thing called the Internet that I thought was going to be a really big deal. I knew that if I failed I wouldn't regret that, but I knew the one thing I might regret is not ever having tried." The regret-minimisation framework cuts through analytical complexity with uncomfortable speed because it does not ask what will maximise returns -- it asks what will minimise the ache of a life unlived. The Clear Thinking framework argues that all the decision-making discipline in the world amounts to very little if the things being pursued are not worth pursuing. Good judgment, at its highest expression, is not knowing how to get what you want. It is knowing which things are worth wanting. + +--- + +## The Framework + +This framework operates at a different altitude from most decision-making tools. Where evaluation frameworks ask "which option is best?", this one asks "best for what?" It proceeds through four lenses, each progressively closer to the core question. + +### Lens 1: The Hedonic Treadmill and the Happy-When Trap + +Psychologists Philip Brickman and Donald Campbell identified a phenomenon so pervasive it functions almost as a natural law: humans adapt to improvements in circumstances and revert to a baseline level of satisfaction. The car that was supposed to bring lasting happiness provides two weeks of euphoria before becoming the new normal -- and the new basis for comparison with everyone else's car. The promotion that was supposed to validate years of effort produces a brief high before introducing new problems, new peers to compare against, and a fresh version of the same discontent. + +The framework labels the sufferers "happy-when" people. They will be happy when they make more money. Happy when they get the credit they deserve. Happy when they find the right partner. The conditional never resolves because each "when" becomes the new floor, and a new "when" materialises immediately above it. It is a one-way door: once through, perspective on where you were is lost, and only the gap to the next level remains visible. + +The entrepreneurial version is particularly virulent. The founder who will be happy when they close the seed round discovers, upon closing it, that happiness now depends on the Series A. The Series A produces a brief high before the pressure of growth targets imposes a new conditional. The text quotes an observation that cuts close to the bone: "The next zero in your bank account won't satisfy you any more than you are satisfied now." + +**The diagnostic question:** If you achieved the goal you are currently pursuing, and the resulting satisfaction lasted only two weeks before reverting to baseline, would you still pursue it? If not, the goal is a treadmill metric -- it generates motion without destination. + +### Lens 2: Dickens's Hidden Lesson + +A Christmas Carol is not a holiday story. It is a decision-making parable. Ebenezer Scrooge is visited by three spirits who show him the past, the present, and a future that might be -- a future in which he is dead and no one mourns him. His former associates are relieved, spiteful, or indifferent. The vision provides what no spreadsheet can: the long-term consequences of his current trajectory, compressed into a single night. He gets something almost no one gets -- the chance to see where his current decisions lead and to change course before it is too late. + +The text illustrates the real-world version with a retired CEO who had played by society's scoreboard -- wealth, status, power -- with sharp elbows in a hypercompetitive culture. He quoted Tywin Lannister, called himself a lion, and never lacked golfing companions while in office. Upon retiring, most of his "friends" stopped returning calls. His transactional approach to relationships had generated professional compliance, not genuine connection. Unlike Scrooge, he received no second chance. + +**The diagnostic question:** If you continue on your current trajectory for ten years and then look back, what will you wish you had done differently? The discomfort this question produces is proportional to the gap between your current direction and your actual values. + +### Lens 3: What the Happiness Experts Actually Say + +Gerontologist Karl Pillemer spent seven years interviewing Americans in their seventies, eighties, and nineties -- people he describes as "the most credible experts we have on how to live happy and fulfilled lives during hard times." His findings are consistent across demographics and are striking for what they include and what they omit. + +**What the elderly say matters:** + +- Say things now to people you care about -- gratitude, forgiveness, questions you have always wanted to ask +- Spend the maximum amount of time with your children +- Savour daily pleasures instead of waiting for "big-ticket items" to produce happiness +- Work in a job you love +- Choose your life partner carefully + +**What none of them said:** + +- None said that to be happy you should work as hard as you can to make money +- None said it was important to be as wealthy as the people around you +- None said to choose your career based on earning potential +- None said they regretted not getting even with someone who wronged them + +**Their largest regret:** Worrying about things that never happened. "Worrying wastes your life," one respondent said. + +The most powerful finding was attitudinal. An 89-year-old woman, when asked to explain her happiness, answered: "In my 89 years, I've learned that happiness is a choice -- not a condition." Pillemer concluded that the elderly "make the key distinction between events that happen to us, on the one hand, and our internal attitude toward happiness, on the other. Happy in spite of." + +This reframes happiness as a decision -- one that sits on the same continuum as every other decision an entrepreneur makes. It can be chosen daily, or it can be deferred to a "when" that never arrives. + +### Lens 4: Memento Mori as a Practical Decision Filter + +The Stoic practice of memento mori -- remembering that you will die -- is treated philosophically in the [Stoic Mortality and Perspective](../../content/skills/stoic/stoic-mortality-and-perspective.md) skill, where Marcus Aurelius and Seneca use mortality awareness to cultivate urgency, clarity, and the view from above. What follows here is the applied version: mortality as a filter for specific decisions. + +**The Deathbed Test.** Imagine yourself at eighty, sitting on a park bench on a beautiful autumn day. Who is in your life? What have you accomplished? What memories do you cherish? What do you regret? Steve Jobs performed this exercise daily: "If today were the last day of my life, would I want to do what I am about to do today?" Whenever the answer was no too many days in a row, he knew something had to change. + +The deathbed test is not a philosophical exercise. It is a filter with three operational applications: + +1. **The regret filter.** We regret the things we did not do more than the things we did. The pain of trying and failing is intense but brief. The pain of failing to try is mild but permanent. When facing a decision between safety and risk, ask which version produces the less tolerable regret at eighty. + +2. **The ordinary moments filter.** What we think of as defining moments -- promotions, launches, funding rounds -- matter less to life satisfaction than the accumulation of tiny moments that did not seem significant at the time. The family dinners. The marks on the doorframe measuring how tall the children were. The afternoon you spent on the couch talking about nothing. The phrase is precise: "Tiny delights over big bright lights." The deathbed test consistently reveals that the things remembered are not the things that were optimised for. + +3. **The relationship filter.** Across Pillemer's interviews, across hospice research, across every longitudinal study of life satisfaction, the finding is identical: relationships are the variable that matters most and the variable most frequently sacrificed in pursuit of variables that matter less. The deathbed test restores the ranking that day-to-day urgency inverts. + +### The Integrating Concept: Phronesis + +The ancient Greeks had a word for the wisdom of knowing how to order your life to achieve the best results: phronesis. It is distinct from technical skill (techne) and from theoretical knowledge (episteme). Phronesis is practical wisdom -- the ability to discern which ends are worth pursuing and which means are appropriate for pursuing them. + +The framework revolves around this concept: good judgment is not merely knowing how to get what you want. It is knowing what to want. "If you want to develop good judgment, start by asking two questions: 'What do I want in life? And is what I want actually worth wanting?' Until you've answered the second question, all the decision-making advice in the world isn't going to do you much good." + +--- + +## Prompts + +**Prompt 1 -- Hedonic Treadmill Audit:** +> "I am pursuing [goal/metric] for my [stage] [sector] company. Apply the hedonic treadmill test: if I achieve this goal and the satisfaction lasts only two weeks before reverting to baseline, was the pursuit worthwhile? Identify which of my current goals are treadmill metrics (generating motion without destination) and which are genuinely aligned with long-term satisfaction. Suggest replacements for the treadmill metrics." + +**Prompt 2 -- Deathbed Test for a Specific Decision:** +> "I am deciding between [Option A] and [Option B]. Project me forward to age 80. From that perspective, which choice produces the more tolerable regret? Apply the three operational filters: (1) regret filter -- which failure of action would haunt me more? (2) ordinary moments filter -- which option generates more of the small daily experiences that matter in retrospect? (3) relationship filter -- which option better preserves or strengthens the relationships that the elderly consistently identify as most important?" + +**Prompt 3 -- Trajectory Projection (Dickens Lens):** +> "Describe my current professional and personal trajectory based on these facts: [describe current priorities, time allocation, relationships, and goals]. Now project that trajectory ten years forward, assuming no changes. What does the picture look like? Where is the gap between where this trajectory leads and where I would actually want to end up? Identify the two or three adjustments that would close the gap most effectively." + +**Prompt 4 -- Phronesis Audit for the Founder:** +> "I have built or am building a company around [mission/product]. Separate the things I am pursuing into two categories: (1) things that are genuinely worth wanting based on what happiness research and end-of-life wisdom consistently identify, and (2) things I am pursuing because of social comparison, status signalling, or the hedonic treadmill. For each item in category 2, suggest what I might pursue instead that would produce more durable satisfaction." + +--- + +## Use Cases + +**Growth-Stage Founder on the Edge of Burnout** + +A founder of a Series B logistics platform works 80-hour weeks, has missed the last three family holidays, and tells herself she will "slow down after the IPO." Applying the hedonic treadmill lens, she recognises a pattern: she said the same thing before the Series A and before the Series B. Each milestone, upon achievement, produced brief satisfaction and immediately generated a new conditional. The deathbed test reveals that she will not remember the Q3 revenue target; she will remember that she missed her daughter's first piano recital. The ordinary moments filter makes visible what the P&L obscures: the daily accumulation of absences that compound as irreversibly as interest. The operational adjustment is not dramatic -- it is scheduling two non-negotiable evenings per week and treating them with the same sanctity as board meetings. The adjustment costs nothing in strategic capability and everything in the metric that actually matters. + +**Pre-Seed Founder Choosing Between Safety and Risk** + +A 34-year-old product manager at a major tech company has a working prototype for a climate-tech startup but cannot bring himself to leave the security of a $280K salary. Bezos's regret-minimisation framework applies directly: at eighty, will he regret having tried and failed, or will he regret never having tried? The pain of a failed startup is intense but finite -- twelve to eighteen months of reduced income and bruised ego. The pain of "what if I had tried?" is low-grade but permanent. The deathbed test does not guarantee the startup succeeds. It clarifies which failure is easier to live with. He negotiates a six-month unpaid leave of absence -- a margin of safety that preserves the option to return while eliminating the regret of never having started. + +**Scaled CEO Redefining Success Metrics** + +The CEO of a 500-person company has achieved every goal he set at twenty-five: wealth, recognition, a company that bears his name. He finds himself, at fifty, unable to articulate what he is working toward beyond "more." Pillemer's research provides the mirror: none of the elderly said that happiness came from maximising wealth, and none regretted failing to accumulate more status. The Dickens lens -- projecting the current trajectory forward -- shows a future in which the company thrives and the CEO's closest relationships are transactional. The phronesis audit separates the goals worth wanting (building something that outlasts him, mentoring the next generation of leaders, deepening his marriage) from the goals that are pure treadmill (the next board seat, the next magazine profile). The operational result is a restructured calendar that allocates 30 percent of his time to mentoring and relationship investment, funded by delegating operational decisions he was holding out of habit rather than necessity. + +--- + +## Anti-Patterns + +**Using the deathbed test to justify recklessness.** The test is a filter for values alignment, not a licence to ignore financial reality. "Life is short" is the most frequently abused insight in the self-help canon. The founder who quits a stable job with no savings, no prototype, and no plan is not applying memento mori -- they are applying magical thinking with a philosophical veneer. + +**Treating this skill as a replacement for analytical decision-making.** Wanting what matters sits above the evaluation frameworks, not in opposition to them. Once you have clarity on what is worth pursuing, you still need criteria weighting, margin of safety, and execution fail-safes to pursue it effectively. Values without competence produce noble failures. + +**Dismissing the hedonic treadmill as obvious.** Everyone nods when told that money does not buy happiness. Almost no one adjusts their behaviour accordingly. The test of whether you have internalised this lens is not whether you agree with it intellectually but whether your calendar and your bank statement reflect the agreement. + +**Applying Pillemer's findings selectively.** The elderly do not say "don't work hard." They say "work in a job you love" and "don't choose your career based on earning potential." These are compatible with extreme ambition. What they are incompatible with is pursuing money or status as terminal goals rather than as byproducts of meaningful work. + +**Confusing memento mori with pessimism.** Mortality awareness does not produce despair in those who apply it rigorously. It produces clarity. The Stoic skill on mortality and perspective develops the philosophical dimension of this practice. The present skill uses it as a filter: does this specific decision pass the deathbed test? The two applications are complementary, not competing. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | The founder decides what problem to solve and why. The deathbed test filters out ideas pursued for status or trend-following and surfaces ideas aligned with genuine values. | The hedonic treadmill audit is personal: "If this company succeeds and I feel the same way in two weeks, was it the right company to build?" | +| Validation | Testing whether the problem matters to customers, but also whether solving it matters to the founder on a ten-year horizon. | Founders who are not intrinsically motivated by the problem they are solving tend to quit during the hardest phase -- the one between prototype and traction. The Dickens lens exposes this misalignment before capital and time are committed. | +| Early Traction | The hedonic treadmill intensifies as metrics become visible. MRR, user counts, and NPS scores become the new "happy-when" conditionals. | The ordinary moments filter becomes a daily practice: are the rhythms of building this company producing daily satisfaction, or is all satisfaction deferred to a future milestone? | +| Growth | Social comparison accelerates. Other founders raise larger rounds, grow faster, command more press. The treadmill runs faster. | Pillemer's research is the corrective: none of the elderly wished they had been wealthier than their peers. The relationship filter protects against the subtle erosion of personal connections that growth-stage intensity produces. | +| Scale | Legacy questions emerge. The founder asks "what will I be remembered for?" and the answer may not align with current priorities. | The phronesis audit becomes strategic: is the company optimised for the things that will matter in retrospect, or for the things that the market currently rewards? Commander's intent should reflect values, not just targets. | + +--- + +## Output Template + +```markdown +# Values Alignment Audit + +## Current Goals and Priorities +| Goal | Category: Worth Wanting / Treadmill Metric | Evidence | +|------|---------------------------------------------|----------| +| [goal 1] | [classification] | [why this classification] | +| [goal 2] | [classification] | [why this classification] | +| [goal 3] | [classification] | [why this classification] | + +## Deathbed Test Results +- **At 80, what would I regret not having done?** [answer] +- **At 80, what current concerns would seem trivial?** [answer] +- **At 80, which relationships would I wish I had invested in more?** [answer] + +## Ordinary Moments Inventory +- **Daily experiences that produce genuine satisfaction now:** [list] +- **Daily experiences I am deferring for a future "when":** [list] +- **Small adjustments that would increase daily satisfaction without strategic cost:** [list] + +## Trajectory Projection (Dickens Lens) +- **If nothing changes in 10 years, where do I end up?** [description] +- **Where do I actually want to end up?** [description] +- **The gap:** [description] +- **Two to three adjustments that close the gap:** [list] + +## Hedonic Treadmill Check +- **Current "happy-when" conditional:** [I will be happy when...] +- **Previous "happy-when" conditionals that were achieved but did not produce lasting satisfaction:** [list] +- **Replacement goals that are not conditional on external achievement:** [list] +``` + +--- + +## Related Skills + +- **[Stoic Mortality and Perspective](../../content/skills/stoic/stoic-mortality-and-perspective.md)** -- Develops the philosophical foundations of memento mori; this skill applies those foundations as a practical decision filter for specific entrepreneurial choices. +- **[Evaluating and Deciding](../../content/skills/thinking/evaluating-and-deciding.md)** -- Once values are clear, this skill provides the mechanics: criteria weighting, margin of safety, execution fail-safes, and decision journals. +- **[Defining and Exploring Problems](../../content/skills/thinking/defining-and-exploring-problems.md)** -- The problem-definition discipline ensures that the right question is being asked; this skill ensures the question is being asked in service of the right life. +- **[Purpose-Driven Leadership](../../content/skills/leadership/purpose-driven-leadership.md)** -- Extends the personal values alignment into organisational mission and culture. +- **[Focus and Priority Management](../../content/skills/leadership/focus-and-priority-management.md)** -- The tactical complement: once you know what matters, this skill provides the operational discipline for protecting it against the urgent-but-unimportant. +- **[Stoic Acceptance and Amor Fati](../../content/skills/stoic/stoic-acceptance-amor-fati.md)** -- The Stoic practice of embracing fate and finding meaning in adversity, a philosophical companion to the happiness-as-choice finding. +- **[Career Strategy for Leaders](../../content/skills/leadership/career-strategy-for-leaders.md)** -- The four-question self-grade and career fuel audit are practical applications of wanting what matters to specific career decisions and trade-offs. diff --git a/plugins/foreman/skills/what-is-a-story/SKILL.md b/plugins/foreman/skills/what-is-a-story/SKILL.md deleted file mode 120000 index c6449f7..0000000 --- a/plugins/foreman/skills/what-is-a-story/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/storytelling/what-is-a-story.md \ No newline at end of file diff --git a/plugins/foreman/skills/what-is-a-story/SKILL.md b/plugins/foreman/skills/what-is-a-story/SKILL.md new file mode 100644 index 0000000..69773e6 --- /dev/null +++ b/plugins/foreman/skills/what-is-a-story/SKILL.md @@ -0,0 +1,202 @@ +--- +name: "what-is-a-story" +description: "Defines what qualifies as a genuine story versus an anecdote, romp, or report. Teaches the transformation requirement, the Dinner Test, and the personal-narrative principle. Use when a founder's pitch feels flat despite good content, when team presentations list facts without landing emotionally, when someone confuses a sequence of events with a compelling narrative, or when preparing any communication that must move people rather than merely inform them." +version: "1.0.0" +category: "storytelling" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - storytelling + - narrative + - communication + - pitch + - transformation + - anecdote + - dinner-test + - personal-narrative + - persuasion +related_skills: + - finding-your-stories + - story-structure-and-arc + - story-beginnings-and-endings + - storytelling-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# What Is a Story? + +DINNER TEST -- A story qualifies as a story only when you are a different person at its end than at its beginning. Everything else is an anecdote. + +Winning thirty-four Moth StorySLAMs requires understanding a distinction that most communicators never grasp. The distinction is brutally simple: a story requires transformation. Not excitement, not novelty, not a punchline. Transformation. A human being must start in one state and finish in another. Strip that away, and what remains is a drinking story, a vacation recap, or a quarterly business review that makes the audience wish they had stayed home. + +Most founders believe they are telling stories. They are not. They are recounting events, listing features, or narrating timelines. The difference matters because stories activate neural coupling -- the listener's brain literally mirrors the teller's -- while event sequences activate patience, and eventually its absence. + +--- + +## The Framework + +### The Transformation Requirement + +A story is not a series of remarkable events. It is the record of a change in a human being. The change can be infinitesimal -- a slight shift in perspective, a grudging acceptance, a moment of unexpected gratitude -- but it must be present. Without change, you have what the framework classifies under blunter labels: + +| What You Think You Have | What You Actually Have | Why It Fails | +|---|---|---| +| A great vacation story | An itinerary with adjectives | No one changed; things merely happened in sequence | +| A wild night out | A drinking story | Amusing to the teller, forgettable to everyone else | +| A product demo narrative | A feature walkthrough | The audience learns specifications, not meaning | +| A fundraising "story" | A financial report with anecdotes | Data wrapped in chronology is still data | +| A company origin myth | A timeline | "And then we did X, and then Y happened" is not a story | + +The point is codified with characteristic bluntness: stories that fail to reflect change over time are "the roller-coasters and cotton candy of the storytelling world. Supremely fun and delicious, but ultimately forgettable." + +The implication for entrepreneurs is severe. A pitch that recites milestones -- we built this, we launched that, we grew here -- is a timeline masquerading as a narrative. The investor has heard a hundred timelines this month. What they have not heard is the moment the founder's understanding of the problem fundamentally shifted. That is a story. + +### Personal Narrative, Not Fable + +The framework draws a hard line between personal storytelling and every other form. Folktales, case studies, and third-person anecdotes can entertain, but they cannot create the visceral connection that personal narrative produces. The reason is structural: personal stories demand vulnerability, honesty, and the willingness to reveal something unflattering about the teller. Third-person stories demand none of these. + +This does not mean you can only tell your own experiences. It means you must tell your side of whatever story you share. You become the protagonist, not the narrator. The Holocaust survivors' children in the storytelling workshops do not recite their parents' histories; they tell their own stories, dipping into the past to show how those histories changed them. The distinction sounds subtle. In practice, it separates stories that connect from stories that inform. + +For a founder, this principle rewires the standard investor pitch. Instead of "Our customer had this problem and we solved it," the personal-narrative version becomes: "I watched our first customer struggle with X, and something in that moment changed how I understood our entire market." The protagonist shifts. The vulnerability appears. The audience leans in. + +### The Dinner Test + +The Dinner Test is the framework's quality filter, and it is ruthless in its simplicity. The story you craft for a stage, a boardroom, or a pitch meeting should be recognisably close to the version you would tell a friend over dinner. + +This means: + +- **No theatrical gestures.** If you would not mime the birth of an idea with fluttering hands at a restaurant table, do not do it in a presentation. +- **No performative language.** Alliterative flights of prose, unattributed opening dialogue, and dramatic sound effects fail the test. Nobody begins a dinner-table story with "Boom!" +- **No memorised scripts.** The best storytelling occupies a space between extemporaneous and rehearsed. The audience and the teller enter an implicit contract: both pretend the story is being told for the first time, even when it is not. + +The Dinner Test prevents a specific pathology that afflicts founders who have been coached to "tell their story." They produce something polished, theatrical, and hollow -- a performance rather than a conversation. Audiences sense the artifice instantly. They disengage not because the content is poor, but because the delivery signals inauthenticity. + +### Your Story Only + +A further constraint: you must be the protagonist. People would rather hear what happened to you last night than what happened to your friend, even if your friend's story is objectively better. Immediacy, grit, and inherent vulnerability reside in hearing the account of the person standing before you. It takes no courage to tell someone else's story. It requires no hard truth. + +This is not a prohibition against incorporating others' experiences. It is a requirement to frame them through your own lens. The founder who says "Let me tell you about our customer Maria" is delivering a case study. The founder who says "I sat across from Maria and realised I had been building the wrong product for six months" is telling a story. Same facts. Different protagonist. Entirely different emotional register. + +--- + +## Prompts + +**Prompt 1 -- Transformation Audit:** +> I have a story I plan to use in [context: pitch / all-hands / conference talk]. Here it is: [paste story]. Analyse it against the transformation requirement. Does the protagonist change? If so, identify the precise moment of change and state what the person believed or felt before versus after. If no transformation exists, tell me plainly that this is an anecdote, not a story, and suggest what transformation might be embedded within the same material. + +**Prompt 2 -- Dinner Test Stress Test:** +> Read the following narrative I have prepared for [audience]: [paste narrative]. Apply the Dinner Test. Flag every element that would feel unnatural if I told this to a friend over dinner -- theatrical language, performative phrasing, unattributed opening dialogue, thesis statements before the story begins, or any moment where I am clearly "performing" rather than telling. Rewrite the flagged sections in a conversational register that still retains precision and impact. + +**Prompt 3 -- Protagonist Reframe:** +> I want to tell the following customer/partner/team story: [paste the third-person version]. Rewrite it so that I am the protagonist, telling my side of what happened. Preserve the key facts but shift the emotional centre to my experience -- what I saw, what I felt, what changed in my understanding. Ensure the reframed version demands vulnerability or honesty from me as the teller. + +**Prompt 4 -- Anecdote-to-Story Conversion:** +> Here is something that happened to me that I find interesting but suspect is only an anecdote: [describe the event]. Interrogate it for a possible five-second moment of transformation. If one exists, identify it and sketch a story arc (beginning state, change, ending state). If none exists, tell me honestly that the material is a romp and suggest what adjacent experience might contain the transformation I need. + +--- + +## Use Cases + +**Idea-stage founder preparing a first pitch** + +A solo founder has a two-minute pitch for an accelerator application. The current version opens with market size, moves through the problem statement, and concludes with a product description. By this taxonomy, it is a report. Applying the transformation requirement, the founder identifies the moment she stopped seeing the problem as a nuisance and started seeing it as a systemic failure affecting millions of people. That moment of shifted perception becomes the story's spine. Market data and product details remain, but they now serve the transformation rather than replacing it. The pitch moves from informing to moving. + +**Growth-stage CEO addressing the company after a failed product launch** + +The CEO's initial draft for an all-hands email recounts the timeline of the launch: what was built, what went wrong, what happens next. It is a post-mortem disguised as a narrative. Applying the Dinner Test, the CEO recognises that no one at a dinner table would speak this way. The rewritten version begins with a personal admission -- the moment the CEO realised the team had optimised for speed at the expense of listening to early customer signals. The email becomes a story about a leader who changed her understanding of what "fast" means. The timeline and action items still appear, but they follow the transformation rather than substituting for it. + +**Sales leader training a team on customer conversations** + +A VP of Sales notices that reps deliver polished product narratives that nonetheless fail to close. Diagnosing the problem through the personal-narrative lens, the VP identifies that reps are telling the company's story (third person, no vulnerability) rather than their own side of customer interactions. Training shifts to helping each rep find the moment in their own experience when a customer conversation changed their understanding of the product's value. Reps begin opening calls with those moments. Close rates improve not because the product changed, but because the protagonist did. + +**Validation-stage team running customer-discovery interviews** + +A two-person team conducts thirty interviews using a script that opens with "Let me tell you about our product." Response rates are low and conversations are short. Applying the Dinner Test and the transformation requirement, the team rewrites the opening: instead of telling the product story, the founder describes the specific moment she realised the problem existed -- sitting in a meeting where a decision was made on bad data because no one had a better option. The revised opening invites the interviewee into a shared experience rather than a sales pitch. Conversation length doubles. Three interviewees volunteer to become design partners without being asked. + +--- + +## Anti-Patterns + +**1. The "and then" trap.** Connecting events with "and then" produces a timeline, not a story. If the narrative can be summarised as "first this happened, and then this happened, and then this happened," there is no transformation, only chronology. The presence of interesting events does not compensate for the absence of change. + +**2. Confusing drama with story.** A near-death experience, a dramatic pivot, or a celebrity endorsement is not inherently a story. It took three years to figure out how to tell the story of a near-death and resuscitation -- because the dramatic event was not the transformation. The transformation happened later, in a quieter moment. Founders routinely mistake their most dramatic experience for their best story. They are usually wrong. + +**3. Performing instead of telling.** The moment a storyteller begins "performing" -- theatrical voice, rehearsed gestures, scripted pauses -- the audience shifts from participant to spectator. The Dinner Test exists precisely to prevent this. Founders who have been media-trained are especially susceptible; they produce something smooth and lifeless. + +**4. Telling someone else's story as your own.** Recounting a customer's journey without making yourself the protagonist strips the narrative of vulnerability. The audience receives a case study. Case studies persuade the analytical mind. Stories persuade the whole person. + +**5. Starting with a thesis statement.** "This is a story about resilience" or "You're not going to believe what happened" sets expectations that constrain surprise and telegraph the ending. No one at a dinner table prefaces their story with a content warning about its emotional register. The thesis statement also betrays a lack of confidence in the story itself -- if the material were strong enough, it would not need an introduction explaining what it is about. + +**6. Mistaking length for depth.** A twenty-minute narrative packed with detail is not more story-like than a two-minute narrative with a clear transformation. Length without structural change is merely duration. Many of the most powerful stories in this tradition run under five minutes. Brevity, when paired with genuine transformation, is a feature rather than a limitation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Founder's personal transformation story | The story IS the company -- the moment the founder's understanding shifted is the only asset | +| Validation | Customer-interaction stories told from the founder's perspective | Transformation evidence now includes others; the founder's arc includes learning from users | +| Early Traction | Pivot and failure stories that demonstrate real change | Stakeholders need to see that setbacks produced genuine shifts in direction, not just revised plans | +| Growth | Scaling the transformation principle to managers and team leads | Every team member needs their own transformation story about the company's mission | +| Scale | Institutional narrative built on accumulated transformation moments | The company's story becomes a chain of transformations, not a timeline of achievements | + +At the idea stage, the founder's personal story and the company's story are functionally identical. The ability to articulate a genuine moment of transformation in sixty seconds may be the single most valuable communication skill available. Investors at this stage are not evaluating the business -- there is barely a business to evaluate. They are evaluating the founder's capacity to see clearly, to learn, and to communicate what they have learned. A transformation story does all three simultaneously. + +At validation and early traction, the protagonist expands. The founder is no longer the only person whose transformation matters. Customer stories -- told from the founder's perspective -- become essential. The key discipline is resisting the temptation to present these as case studies (third person, no stakes for the teller) and instead framing them as moments when the founder's understanding of the market shifted because of something a customer said or did. + +At growth and scale, the challenge shifts from telling one story well to ensuring that dozens or hundreds of people understand what a story actually is -- and stop delivering timelines, reports, and anecdotes in its place. Workshop-style training that teaches the transformation requirement, the Dinner Test, and the protagonist principle across functions produces measurable improvements in sales conversations, internal presentations, and external communications. + +--- + +## Output Template + +```markdown +# Story Diagnostic -- [Context: Pitch / Presentation / Communication] + +**Teller:** [Name] +**Audience:** [Investors / Team / Customers / Board] +**Date:** [Date] + +## 1. Transformation Check +**Starting state:** [What the protagonist believed, felt, or understood at the beginning] +**Ending state:** [What changed -- the five-second moment] +**Is there genuine transformation?** [Yes / No] +**If no:** [This is an anecdote / report / timeline. Identify where transformation might be found.] + +## 2. Dinner Test +**Would you tell it this way at dinner?** [Yes / No] +**Flagged elements:** [List any theatrical, performative, or scripted moments] +**Recommended adjustments:** [Specific rewrites] + +## 3. Protagonist Check +**Who is the protagonist?** [Should be the teller] +**Is vulnerability present?** [Yes / No -- what is at risk for the teller?] +**If third-person:** [Reframe suggestion -- how to make the teller the protagonist] + +## 4. Classification +**This material is a:** [Story / Anecdote / Romp / Report / Timeline] +**If not a story:** [What transformation could be added or uncovered?] + +## 5. Revised Opening +[Two to three sentences that open with forward movement and no thesis statement] +``` + +--- + +## Related Skills + +- **[Finding Your Stories](../../content/skills/storytelling/finding-your-stories.md)** -- Once the definition of a story is clear, the next step is building a systematic practice for discovering them in daily life. +- **[Story Structure and Arc](../../content/skills/storytelling/story-structure-and-arc.md)** -- Understanding what a story is precedes learning how to build one; this companion skill covers the five-second moment and narrative momentum. +- **[Story Beginnings and Endings](../../content/skills/storytelling/story-beginnings-and-endings.md)** -- The transformation requirement directly informs where a story should start and finish. +- **[Storytelling for Leaders](../../content/skills/leadership/storytelling-for-leaders.md)** -- Applies storytelling to organisational change; this skill provides the foundational definitions that make leadership storytelling effective. +- **[Emotional Impact in Stories](../../content/skills/storytelling/emotional-impact-in-stories.md)** -- The surprise and emotional design techniques that convert a transformation moment into genuine audience feeling. +- **[Creative Identity and Purpose](../../content/skills/creative/creative-identity-and-purpose.md)** -- The permission to claim "I am a storyteller" is the same identity shift the creative arts skill addresses; both require overcoming self-doubt about one's right to create. diff --git a/plugins/foreman/skills/win-win-negotiation/SKILL.md b/plugins/foreman/skills/win-win-negotiation/SKILL.md deleted file mode 120000 index 7c8d68b..0000000 --- a/plugins/foreman/skills/win-win-negotiation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/frameworks/win-win-negotiation.md \ No newline at end of file diff --git a/plugins/foreman/skills/win-win-negotiation/SKILL.md b/plugins/foreman/skills/win-win-negotiation/SKILL.md new file mode 100644 index 0000000..1b83fdd --- /dev/null +++ b/plugins/foreman/skills/win-win-negotiation/SKILL.md @@ -0,0 +1,253 @@ +--- +name: "win-win-negotiation" +description: "Prepares and conducts negotiations using Fisher and Ury's principled negotiation method from Getting to Yes. Applies four principles: separate people from problems, focus on interests not positions, generate options for mutual gain, and insist on objective criteria. Use when negotiating term sheets, structuring enterprise contracts, resolving co-founder equity disputes, preparing for acquisition discussions, or debriefing completed negotiations for improvement." +version: "1.0.0" +category: "frameworks" +complexity: "advanced" +stage: + - validation + - early-traction + - growth + - scale +tags: + - negotiation + - conflict-resolution + - partnerships + - deal-making + - strategy +related_skills: + - thomas-kilmann-conflict + - trust-equation + - cialdini-influence + - carnegie-win-friends +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Win-Win Negotiation + +In 2012, a promising SaaS startup negotiated its first enterprise contract with a Fortune 500 client. The client's procurement team demanded 60% off list price, exclusive feature development, and a three-year lock-in. The startup's founders, terrified of losing their flagship account, agreed to every term. Within eighteen months, the contract was haemorrhaging cash: the custom features consumed engineering bandwidth that starved the core product, the discounted price set a precedent that poisoned every subsequent deal, and the lock-in prevented the startup from pivoting when the market shifted. The client, meanwhile, received mediocre service from a vendor that resented the deal's terms. Both sides played to win. Both sides lost. This is the predictable wreckage of positional negotiation -- the distributive, zero-sum mindset that treats every deal as a fixed pie to be fought over. + +Roger Fisher and William Ury of the Harvard Negotiation Project proposed an alternative in *Getting to Yes* (1981). Their framework -- principled negotiation, commonly called win-win -- does not require parties to be altruistic, naive, or conflict-averse. It requires them to be intelligent about what they are actually negotiating for. + +--- + +## The Framework + +### The Four Principles of Principled Negotiation + +Fisher and Ury's framework rests on four core principles, each addressing a specific failure mode of conventional positional bargaining. + +#### Principle 1: Separate the People from the Problem + +Every negotiation involves two dimensions: the substantive issue (the deal terms) and the relationship (the people across the table). Positional bargaining entangles these dimensions -- a disagreement on price becomes a personal attack; a concession feels like weakness. Principled negotiation disentangles them explicitly. + +**In practice:** +- Acknowledge the emotional dimension of negotiation openly. "I understand this timeline is frustrating for your team" is not weakness; it is emotional intelligence that preserves the working relationship. +- Attack the problem, never the person. "The proposed payment terms create cash flow risk for us" rather than "Your terms are unreasonable." +- Build the relationship before and alongside the negotiation. The stronger the personal rapport, the easier it is to disagree on substance without damaging the relationship. +- Be hard on the problem, soft on the people. These are not contradictory -- they are complementary. + +**Founder trap:** First-time founders often conflate tough negotiation with personal conflict. They either cave to preserve the relationship (losing on substance) or fight aggressively to win (destroying the relationship). The framework demands both: preserve the relationship *and* fight for your interests. + +#### Principle 2: Focus on Interests, Not Positions + +Positions are what people *say* they want. Interests are *why* they want it. Two founders negotiating equity splits may take opposing positions (60/40 vs. 50/50), but their underlying interests -- fairness, recognition of contribution, protection against free-riding, financial security -- may be compatible. Positional bargaining fights over the numbers. Interest-based negotiation explores the motivations and discovers solutions that the positions obscure. + +**The interest-mapping exercise:** + +| Position (What they say) | Likely Interests (Why they want it) | Creative Options | +|--------------------------|-------------------------------------|-----------------| +| "We need 60% off list price" | Budget constraints, need to show procurement value, precedent concerns | Tiered pricing, volume commitment with graduated discounts, payment terms flexibility | +| "We need exclusive feature development" | Competitive differentiation, specific workflow requirement | Priority roadmap influence, co-development agreement, configuration rather than custom code | +| "We need a 3-year lock-in" | Avoid switching costs, ensure vendor commitment | Mutual commitment (vendor guarantees service levels), annual renewal with loyalty pricing | + +**Key question:** "Help me understand *why* this is important to you." This single question, asked genuinely, transforms more negotiations than any tactical manoeuvre. + +#### Principle 3: Generate Options for Mutual Gain + +Positional negotiation assumes a fixed pie: every dollar I get is a dollar you lose. Principled negotiation actively searches for ways to expand the pie before dividing it. The discipline is to generate options before evaluating them -- brainstorming without commitment, creating a menu of possibilities that neither party would have discovered alone. + +**Option generation techniques:** +- **Dovetailing interests:** Where your interests diverge, creative trades become possible. You value speed; they value thoroughness. You deliver a phased implementation -- fast initial deployment (satisfying your interest) with a comprehensive second phase (satisfying theirs). +- **Shared interests:** Identify what both parties want and build the deal around those points. Both want a long-term relationship? Structure the deal with renewal incentives rather than lock-in clauses. +- **Low-cost/high-value trades:** Things that cost you little but matter greatly to the other party. Case study rights may cost your customer nothing but provide enormous marketing value to you. Technical documentation may cost you a few engineering days but save them months of integration work. + +**The brainstorming protocol:** +1. State the problem clearly. "How do we structure a partnership that serves both our interests?" +2. Generate options without evaluation. No "that won't work" during brainstorming. +3. Expand the pie before dividing it. Ask: "What can we create together that neither of us can create alone?" +4. Evaluate against objective criteria (see Principle 4). + +#### Principle 4: Insist on Objective Criteria + +When interests conflict and creative options are exhausted, the remaining disagreements must be resolved by reference to objective standards rather than by who has more power. Market rates, industry benchmarks, independent valuations, legal precedent, scientific evidence, and professional norms all serve as objective criteria. + +**In practice:** +- "Let's look at what comparable SaaS companies charge for enterprise contracts at this scale" (market rates as criteria) +- "The standard vesting schedule in our market is four years with a one-year cliff" (industry norms as criteria) +- "We'd like to base the acquisition price on a multiple of trailing twelve months' revenue, using the median multiple for recent comparable transactions" (independent valuation as criteria) + +**Power of objective criteria:** +- They depersonalise the decision. Neither party is "giving in" -- both are deferring to external standards. +- They provide a face-saving mechanism. "I can't justify this to my board, but I can if we benchmark against market rates." +- They reduce the role of power asymmetry. A well-researched founder with strong objective criteria can negotiate effectively against a much more powerful counterparty. + +### BATNA: Your Source of Power + +Fisher and Ury introduced the concept of BATNA -- Best Alternative to a Negotiated Agreement. Your BATNA is what you will do if the current negotiation fails. The stronger your BATNA, the more confidently you can negotiate, because you have a credible walk-away. + +**BATNA development:** +- Before any negotiation, explicitly identify and strengthen your alternatives +- Never enter a negotiation with no alternative -- desperation is visible and exploitable +- Evaluate the other party's BATNA as well; understanding their alternatives reveals their negotiating constraints +- Improve your BATNA before the negotiation if possible (cultivate other investors, qualify other customers, develop backup plans) + +**The BATNA trap for founders:** Seed-stage founders often have weak BATNAs -- one interested investor, one potential enterprise client, one acquisition offer. This power asymmetry makes principled negotiation harder but more important, not less. Without strong alternatives, the framework's emphasis on objective criteria and creative options becomes the primary source of negotiating leverage. + +### The Negotiation Canvas + +A structured preparation tool combining all four principles: + +``` +┌──────────────────────────────────────────────────┐ +│ PREPARATION │ +├────────────────────┬─────────────────────────────┤ +│ OUR SIDE │ THEIR SIDE │ +├────────────────────┼─────────────────────────────┤ +│ Positions: │ Positions: │ +│ [What we ask for] │ [What they ask for] │ +├────────────────────┼─────────────────────────────┤ +│ Interests: │ Interests: │ +│ [Why we want it] │ [Why they want it] │ +├────────────────────┼─────────────────────────────┤ +│ BATNA: │ BATNA (estimated): │ +│ [Our alternatives] │ [Their alternatives] │ +├────────────────────┼─────────────────────────────┤ +│ Objective criteria │ Shared interests: │ +│ supporting our │ [What both sides want] │ +│ position: │ │ +├────────────────────┴─────────────────────────────┤ +│ OPTIONS FOR MUTUAL GAIN │ +│ 1. [Option] │ +│ 2. [Option] │ +│ 3. [Option] │ +└──────────────────────────────────────────────────┘ +``` + +--- + +## Prompts + +**Prompt 1 -- Negotiation Preparation:** +> I am about to negotiate [describe the deal -- fundraising, partnership, enterprise contract, acquisition, hire]. Using Fisher and Ury's principled negotiation framework, help me prepare. Walk me through: (1) identifying my interests vs. my positions, (2) hypothesising the other party's interests, (3) generating at least five options for mutual gain, (4) identifying relevant objective criteria, and (5) assessing both my BATNA and theirs. My context: [describe your company, stage, leverage, and the other party]. + +**Prompt 2 -- Mid-Negotiation Strategy:** +> I am in the middle of a negotiation that has stalled. The other party is insisting on [their position], and I need [my position]. Using the principled negotiation framework, help me: (1) identify the underlying interests behind both positions, (2) generate creative options we haven't considered, (3) find objective criteria that could break the impasse, and (4) assess whether I should continue negotiating or exercise my BATNA. Current situation: [describe in detail]. + +**Prompt 3 -- Term Sheet Analysis:** +> Analyse this term sheet using the principled negotiation framework: [paste or describe key terms]. For each term, identify: (1) the investor's likely interest behind the position, (2) our interest, (3) whether the term reflects fair objective criteria, and (4) alternative structures that could satisfy both parties' interests. Flag any terms where we should hold firm and any where creative alternatives exist. + +**Prompt 4 -- Negotiation Debrief:** +> I just completed a negotiation. Here is what happened: [describe the process and outcome]. Using Fisher and Ury's framework, debrief: (1) Where did I successfully separate people from problems? Where did I conflate them? (2) Where did I focus on interests vs. positions? Where did I get positional? (3) What creative options did I miss? (4) Where could objective criteria have strengthened my position? What will I do differently next time? + +**Prompt 5 -- Team Negotiation Alignment:** +> My team is entering a complex negotiation with [describe]. Multiple team members will participate. Using the principled negotiation framework, help me: (1) align the team on our interests (not just our positions), (2) assign roles (who leads which issues), (3) establish our BATNA and walk-away points, (4) prepare our option-generation strategy, and (5) define decision-making authority -- who can agree to what without escalation. + +--- + +## Use Cases + +**Validation-Stage Startup Negotiating First Pilot Contract** +A B2B startup has one potential pilot customer -- a mid-market company whose procurement team demands free usage during the pilot, ownership of any IP developed, and right of first refusal on pricing. The founders' positions: charge something, retain IP, offer no exclusivity. Interest-based analysis reveals: the customer's underlying interests are risk mitigation (free pilot), competitive advantage (IP ownership), and budget certainty (pricing control). Creative options: a paid pilot at 75% discount (risk reduction for the customer, cash flow for the startup), IP remains with the startup but the customer gets a most-favoured-nation pricing clause (competitive advantage without IP transfer), and a six-month price lock rather than right of first refusal (budget certainty without long-term constraint). The deal closes because both parties get what they actually need, not what they initially demanded. + +**Growth-Stage Company Negotiating Series B Terms** +A SaaS company with strong metrics receives a Series B term sheet with a full-ratchet anti-dilution provision, two board seats for the lead investor, and a participating preferred liquidation preference. Positional response: reject and counter. Principled response: map interests. The investor's interest behind full-ratchet: downside protection after a portfolio company previously cratered. Creative option: weighted-average anti-dilution (standard market term) plus a quarterly reporting package that gives the investor early warning of trouble -- addressing their actual concern (risk monitoring) rather than their stated position (maximum protection). Board seats interest: governance influence and information access. Option: one board seat plus observer seat plus monthly operating metrics -- influence without control. The term sheet evolves through three rounds of interest-based negotiation into a deal both parties consider fair, benchmarked against comparable transactions (objective criteria). + +**Scale-Stage Company Negotiating a Strategic Acquisition** +A 400-person company receives an acquisition offer. The acquirer's position: $200M all-stock. The target's position: $300M, majority cash. Traditional negotiation produces a stalemate. Principled negotiation reveals interests: the acquirer wants to preserve cash and ensure founder retention (stock aligns incentives). The target wants liquidity for shareholders and protection against acquirer stock decline. Creative options: $240M with 60% cash / 40% stock, with a collar on the stock component (protects against decline); an earn-out component tied to integration milestones (aligns incentives without requiring all-stock); and an accelerated vesting schedule for key employees (founder retention addressed separately from deal structure). Objective criteria: comparable transaction multiples, independent fairness opinion, and market-standard earn-out structures. The deal closes at terms both boards approve. + +--- + +## Anti-Patterns + +1. **Win-Win as Capitulation.** Misinterpreting the framework as requiring equal concessions or avoiding tough stances. Principled negotiation is not about being nice. It is about being effective. Sometimes your interests are non-negotiable, and the framework supports holding firm -- but on interests, not positions, and justified by objective criteria, not stubbornness. + +2. **Positional Bargaining in Disguise.** Calling a negotiation "principled" while actually anchoring on positions, making incremental concessions, and treating the process as a contest. True interest-based negotiation requires genuine curiosity about the other party's needs, not tactical reframing of your demands. + +3. **Neglecting BATNA Development.** Entering a negotiation without a viable alternative and hoping the framework compensates. Principled negotiation without BATNA is a philosophy without leverage. The framework works best when both parties have credible alternatives, because the deal must genuinely be better than each party's next-best option. + +4. **Premature Option Evaluation.** Brainstorming creative options and immediately critiquing them ("that won't work because..."). The power of option generation lies in separating inventing from deciding. Premature evaluation kills creative solutions. + +5. **Ignoring Cultural Negotiation Norms.** Fisher and Ury's framework originated in American negotiation culture, which values directness, individual decision-making, and efficiency. In cultures that prioritise relationship-building (Japan, Middle East), hierarchical decision-making (Korea, many European firms), or indirect communication (much of Southeast Asia), the framework's application requires significant cultural adaptation. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | First deals with weak BATNA | Founders negotiating from a position of scarcity must rely heavily on objective criteria and creative options to compensate for weak alternatives. Every early deal sets precedents -- negotiate carefully. | +| Early Traction | Hiring and partnership negotiations | As the company establishes itself, negotiations multiply: key hires negotiating equity, early partners negotiating terms, landlords negotiating leases. The framework scales to cover them all. | +| Growth | Fundraising and enterprise sales | Growth-stage negotiations are higher-stakes and more complex. Multiple stakeholders on each side, longer timelines, and more variables create opportunities for creative option generation. | +| Scale | M&A, strategic partnerships, complex multi-party deals | At scale, negotiations involve legal teams, investment bankers, and board approval. The framework's emphasis on interests over positions prevents deal teams from getting lost in positional complexity. | + +--- + +## Output Template + +```markdown +# Negotiation Preparation: [Deal/Context] + +## Parties +- **Our side:** [Who is at the table, decision-making authority] +- **Their side:** [Who is at the table, decision-making authority] + +## Position vs. Interest Map +| Issue | Our Position | Our Interest | Their Position (Known/Estimated) | Their Interest (Estimated) | +|-------|-------------|-------------|--------------------------------|--------------------------| +| [Issue 1] | [What we ask] | [Why] | [What they ask] | [Why] | +| [Issue 2] | [What we ask] | [Why] | [What they ask] | [Why] | + +## BATNA Assessment +- **Our BATNA:** [Best alternative if this deal fails] +- **Our BATNA quality:** [Strong / Moderate / Weak] +- **Their BATNA (estimated):** [Their likely alternatives] +- **Reservation point:** [The minimum terms we would accept] + +## Options for Mutual Gain +1. [Creative option that serves both parties' interests] +2. [Creative option] +3. [Creative option] +4. [Creative option] +5. [Creative option] + +## Objective Criteria +- [Market benchmark] +- [Industry standard] +- [Comparable transaction] +- [Independent valuation or expert opinion] + +## Negotiation Sequence +1. **Opening:** [Relationship-building, agenda setting] +2. **Interest exploration:** [Questions to surface their interests] +3. **Option generation:** [Joint brainstorming process] +4. **Evaluation against criteria:** [How to compare options] +5. **Agreement or BATNA:** [Decision framework] + +## Walk-Away Conditions +- [Specific conditions under which we exercise our BATNA] +``` + +--- + +## Related Skills + +- **[Thomas-Kilmann Conflict](../../content/skills/frameworks/thomas-kilmann-conflict.md)** -- TKI's "collaborating" mode is the conflict-handling equivalent of principled negotiation; both frameworks seek integrative solutions rather than distributive compromise. +- **[Trust Equation](../../content/skills/frameworks/trust-equation.md)** -- Trust is the lubricant of principled negotiation; high trust enables the vulnerability required to share interests, generate options, and defer to objective criteria. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Influence principles inform negotiation tactics, particularly reciprocity (first concessions) and commitment (incremental agreement-building). +- **[Carnegie's Win Friends](../../content/skills/frameworks/carnegie-win-friends.md)** -- Carnegie's principle of "arousing an eager want" maps directly to Fisher and Ury's emphasis on understanding and serving the other party's interests. +- **[Negotiation Game Theory](../../content/skills/game-theory/negotiation-game-theory.md)** -- Game theory formalises the strategic dynamics underlying principled negotiation, revealing when cooperative strategies dominate competitive ones mathematically. +- **[Cooperative Negotiation](../../content/skills/negotiation/cooperative-negotiation.md)** -- Provides complementary tactics and frameworks for the interest-based, option-generating approach that Fisher and Ury prescribe as the core of principled negotiation. diff --git a/plugins/foreman/skills/writing-effective-emails/SKILL.md b/plugins/foreman/skills/writing-effective-emails/SKILL.md deleted file mode 120000 index 4932730..0000000 --- a/plugins/foreman/skills/writing-effective-emails/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-effective-emails.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-effective-emails/SKILL.md b/plugins/foreman/skills/writing-effective-emails/SKILL.md new file mode 100644 index 0000000..59b8cfe --- /dev/null +++ b/plugins/foreman/skills/writing-effective-emails/SKILL.md @@ -0,0 +1,198 @@ +--- +name: "writing-effective-emails" +description: "Provides a practical system for writing emails that get read, answered, and acted upon. Covers subject line craft, optimal length, formatting for scanning, tone calibration, CC/BCC etiquette, and when to choose a different medium entirely. Use when composing high-stakes emails to investors or clients, establishing email standards for a team, preparing sensitive written communications, or diagnosing why outreach emails receive poor response rates." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - email + - communication + - subject-lines + - brevity + - etiquette + - professional-writing +related_skills: + - tone-and-engagement + - grammar-and-mechanics + - writing-memos-and-reports + - giving-feedback +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing Effective Emails + +The average manager receives 121 emails per day. At a generous reading rate of thirty seconds per email, that is an hour simply triaging -- deciding which messages deserve attention and which deserve the archive. The arithmetic is ruthless: each email competes with 120 others for a finite allocation of cognitive bandwidth. Subject line, first sentence, length, formatting, and tone collectively determine whether a message lands in the "read and act" category or the "skim and forget" graveyard. Most business emails -- painstakingly drafted, carefully considered -- end up in the graveyard. Not because they lacked substance, but because they failed the thirty-second audition. + +--- + +## The Framework + +### The Six Principles of Effective Email + +**1. Get to the Point in the First Two Sentences** + +State your purpose immediately. Politely, but immediately. Do not build up to the request through three paragraphs of context that the reader will skip anyway. + +- *Before:* "It's been ages, I know, but I've been meaning to tell you just how effective I think you've been as the editor of the Daily Metropolitan these past seven years. Although I cancelled my subscription a few years back (LOL) -- the papers kept cluttering the driveway -- I buy a copy at the coffee shop almost every day. Anyhoo, I have a mentee I'd like you to meet..." +- *After:* "May I ask a favour of you? Glenda Jones, a really sharp mentee in the township's Young Leaders programme, wants to pursue a career in journalism. Would you spend 15 minutes chatting with her at your office sometime this month?" + +The second version is longer in total but arrives at its point faster. Everything it includes serves the request. + +**2. Copy People Judiciously** + +Include only those who will immediately understand why they are on the thread. Reply All is the nuclear option of email etiquette -- use it only when every recipient genuinely needs to see your response. The instinct to "keep people in the loop" produces loops that strangle productivity. + +**3. Keep the Message to One Screen** + +People find long emails irksome. The more they scroll, the less receptive they become. Many recipients close long emails immediately, planning to return to them later -- a plan that rarely materialises. Compose more than a single screen of reading only when the content genuinely demands it, and in those cases, use subheadings and bullet points to enable scanning. + +**4. Write a Short but Informative Subject Line** + +The subject line is the email's headline. A generic or blank subject line guarantees burial. + +| Weak Subject Line | Strong Subject Line | +|-------------------|---------------------| +| "Program" | "The Nov. 15 Leadership Programme" | +| "Quick question" | "Budget Approval Needed by Friday" | +| "Update" | "Q3 Revenue Update: +14% vs. Plan" | +| "Hello there!" | "Request for an Interview" | + +If the email requires action, signal it in the subject line. "Action Required:" or "Decision Needed:" are not rude -- they are respectful of the reader's time. + +**5. Maintain Standard Capitalisation and Punctuation** + +Rushed emails that violate basic writing conventions -- no capitals, no punctuation, cryptic abbreviations -- communicate carelessness. Standing out as someone who writes properly is a low-effort competitive advantage. Clarity written once costs less time than the follow-up email explaining what the first one meant. + +**6. Use a Professional Signature** + +Include your title and contact information. Keep it clean -- not too long, not ornate. The signature makes it convenient for recipients to choose how to reach you. + +### The Tone Spectrum for Email + +Email tone must match the relationship and the content. The framework identifies three registers: + +**Collegial and Direct** (for peers, regular collaborators): +> "Can you review the deck by Thursday? I need your input on slides 6-8 before the client meeting." + +**Professional and Warm** (for clients, senior stakeholders): +> "Thank you for the thoughtful feedback on the proposal. I've incorporated your suggestions into the revised version -- attached. Would Tuesday work for a brief call to walk through the changes?" + +**Firm but Respectful** (for difficult messages): +> "Several people have complained about the email you sent yesterday. Our company's policy does not make an exception for offensive language, even when used in jest. Please think about how future emails will affect your coworkers. If I receive complaints again, HR will have to get involved. But I trust that won't be necessary." + +Note the progression: the firm version states facts, cites policy, explains consequences, and closes with a statement of trust. It never attacks the person's character, never uses sarcasm, and never makes threats it cannot back up. + +### When Not to Use Email + +Email is the wrong medium when: + +- **The topic is emotionally charged.** A phone call or face-to-face conversation allows for real-time calibration of tone. +- **The issue requires rapid back-and-forth.** Five rounds of email take five hours. One conversation takes ten minutes. +- **The content is confidential.** Email is a permanent record that can be forwarded, subpoenaed, or leaked. +- **You are angry.** Write the email if you must -- then delete it. Wait 24 hours. Write a new one. + +--- + +## Prompts + +**Prompt 1 -- Email Rewrite:** +> Rewrite this email to be shorter, more direct, and more likely to receive a prompt response. Keep the same informational content but restructure it so the purpose is clear in the first two sentences, the body is scannable, and the call to action is unmistakable. Original email: [paste text] + +**Prompt 2 -- Subject Line Generator:** +> I need to send an email about [describe topic and purpose]. The recipient is [describe]. Generate five subject line options, ranging from informational to action-oriented. For each, explain why it would work and when it would be most appropriate. + +**Prompt 3 -- Difficult Email Drafter:** +> I need to send an email to [describe person and relationship] about [describe sensitive topic]. I want to be direct without being aggressive, and I need to [describe desired outcome]. Draft the email using a firm-but-respectful tone. Then explain the tonal choices -- what you included, what you avoided, and why. + +**Prompt 4 -- Email Audit:** +> Analyse my last five sent emails [paste them] against the six principles of effective email: directness, judicious copying, brevity, informative subject lines, standard conventions, and professional signature. Score each email on a 1-5 scale for each principle and provide specific recommendations for improvement. + +--- + +## Use Cases + +**Idea-Stage Founder Sending Cold Outreach** +A founder sends 50 cold emails to potential advisors with the subject line "Hello!" and an opening paragraph of self-introduction that runs eight sentences before mentioning what she wants. Response rate: 2%. After restructuring with a specific subject line ("Request: 15-min Call on EdTech Distribution Strategy"), a two-sentence opening that states the ask, and a total length of six sentences, response rate climbs to 18%. The content of the request did not change. The packaging did. + +**Early-Traction Startup Managing a Client Escalation** +A client emails the CEO directly, furious about a missed deliverable. The CEO's instinct is to respond immediately, defensively, and at length. Instead, she waits two hours, drafts a response using the firm-but-respectful framework: acknowledges the problem (first sentence), takes ownership (second sentence), provides a concrete remediation plan (third paragraph), and closes with a specific follow-up commitment. The client de-escalates within one reply. The email thread, later reviewed by the board, demonstrates maturity under pressure. + +**Growth-Stage Company Reducing Email Overload** +A 150-person company discovers that the average employee sends or receives 94 internal emails per day. A review of a sample reveals that 40% of internal emails could be replaced by Slack messages, 15% are unnecessary Reply Alls, and 20% are emails that should have been meetings. The company institutes an email protocol based on the six principles, including a "no Reply All without justification" policy. Internal email volume drops 35% in the first quarter. + +--- + +## Anti-Patterns + +1. **The Wall of Text.** An email that runs twelve paragraphs with no subheadings, no bullet points, and no visual breaks. The reader's eye has nothing to anchor on, so it skims, misses the key request buried in paragraph nine, and the sender wonders why nothing happened. + +2. **The Passive-Aggressive CC.** Copying someone's manager on an email to apply pressure. This tactic is transparent, breeds resentment, and signals that the sender cannot resolve issues directly. If escalation is genuinely necessary, do it explicitly and openly. + +3. **The Emotional Send.** Writing and sending an email while angry. Email is a permanent, forwardable record. The catharsis of an angry send is always outweighed by the regret of re-reading it the next morning. Write it, delete it, wait, then write a new one. + +4. **The Subject-Line Hijack.** Replying to an old email thread about a completely different topic because it is easier than starting a new one. The original subject line becomes a lie, the new content is unfindable in future searches, and every recipient on the old thread receives irrelevant noise. + +5. **The Disclaimer Novel.** Appending a 200-word legal disclaimer to every email, including internal messages. If legal counsel requires a disclaimer, keep it minimal. A disclaimer longer than the email itself is a parody of professionalism. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Cold outreach to investors and advisors | Every email is an audition. Subject lines and opening sentences determine whether the founder gets a meeting or gets ignored. Volume is high; conversion rate depends entirely on craft. | +| Validation | Investor updates and early customer communication | Regular investor updates establish cadence and trust. Clarity and brevity signal competence. Customers evaluate the company partly through the quality of its email communication. | +| Early Traction | Client management and internal coordination | Email becomes a primary coordination tool. The volume increases, making brevity and clear subject lines essential for operational efficiency. | +| Growth | Email culture and protocols | Bad email habits, multiplied across a growing team, create organisational drag. Establishing email norms -- when to email vs. message, CC etiquette, response-time expectations -- prevents communication debt. | +| Scale | Automated and templated communications | At scale, many emails are templated or automated. Tone, clarity, and personalisation in templates determine whether they feel human or robotic. Each template represents thousands of reader impressions. | + +--- + +## Output Template + +```markdown +# Email Draft: [Purpose] + +## Pre-Send Checklist +- [ ] Subject line is specific and action-oriented +- [ ] Purpose is clear in the first two sentences +- [ ] Total length fits within one screen +- [ ] Only necessary recipients are included (To/CC) +- [ ] Tone matches the relationship and content +- [ ] Call to action is explicit and includes a deadline +- [ ] Standard capitalisation and punctuation used throughout +- [ ] Signature includes title and contact information +- [ ] Read aloud for tone -- would I say this in person? +- [ ] If emotionally charged: waited at least 2 hours before sending + +## Draft Structure +**Subject:** [specific, informative subject line] + +**Opening (1-2 sentences):** [purpose and context] + +**Body (3-5 sentences max):** [supporting details, formatted for scanning] + +**Close (1-2 sentences):** [specific call to action with deadline] + +**Signature:** [name, title, contact] +``` + +--- + +## Related Skills + +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Email is the highest-frequency venue for tonal miscalibration; the principles of tone management apply with particular urgency to the inbox. +- **[Grammar and Mechanics](../../content/skills/writing/grammar-and-mechanics.md)** -- Speed and informality make email the most common source of grammar errors in professional writing. +- **[Writing Memos and Reports](../../content/skills/writing/writing-memos-and-reports.md)** -- When the content exceeds one screen, the writer should consider whether the message belongs in a memo or report rather than an email. +- **[Writing for Response](../../content/skills/writing/writing-for-response.md)** -- The friction-reduction principles for getting readers to act apply with particular force to the inbox, where every additional step reduces response probability. +- **[Writing for Navigation](../../content/skills/writing/writing-for-navigation.md)** -- Subject line craft, one-screen discipline, and scanning-optimised formatting are email-specific applications of the broader navigation architecture. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Leaders send the highest-stakes emails in any organisation; the four principles of leadership writing apply with particular force to the inbox. diff --git a/plugins/foreman/skills/writing-for-navigation/SKILL.md b/plugins/foreman/skills/writing-for-navigation/SKILL.md deleted file mode 120000 index c07ad2f..0000000 --- a/plugins/foreman/skills/writing-for-navigation/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-for-navigation.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-for-navigation/SKILL.md b/plugins/foreman/skills/writing-for-navigation/SKILL.md new file mode 100644 index 0000000..8255176 --- /dev/null +++ b/plugins/foreman/skills/writing-for-navigation/SKILL.md @@ -0,0 +1,203 @@ +--- +name: "writing-for-navigation" +description: "Provides a structural system for arranging written content so busy readers can find what matters within seconds. Covers BLUF (Bottom Line Up Front), visual hierarchy, headings as signposts, bullet point strategy, formatting discipline, and the map metaphor for document design. Use when structuring investor updates, redesigning internal communications, formatting product announcements, or diagnosing why well-written messages still fail to land." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - navigation + - BLUF + - visual-hierarchy + - formatting + - headings + - bullet-points + - document-design +related_skills: + - reader-psychology + - writing-for-response + - writing-effective-emails + - clarity-and-concision + - writing-memos-and-reports +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing for Navigation + +MAP. Stop thinking of your writing as a path readers walk along -- think of it as a map they zoom into. The question is: can they find what matters in three seconds? When someone opens Google Maps, the default view is a bird's-eye orientation -- country, state, city -- before any street-level detail appears. Readers approach documents the same way: they scan the landscape, identify regions of interest, and zoom in selectively. If the landscape offers no landmarks, they leave. The US Army codified this principle decades ago as BLUF -- Bottom Line Up Front -- an official policy requiring writers to place key information at the beginning of every communication. Military efficiency aside, BLUF reflects a cognitive reality that applies to every email, memo, and Slack message an entrepreneur will ever send: readers who cannot orient themselves within seconds will not orient themselves at all. + +--- + +## The Framework + +### Six Rules of Navigable Writing + +**Rule 1: Make Key Information Immediately Visible** + +The first question a reader asks is, "What is this about?" The easier the writer makes it to answer that question, the more likely the reader is to stay. In journalism, failing to answer it early is called "burying the lede." Literary magazines bury ledes on purpose, building mood before revealing the central conflict. Practical communications are not literary magazines. + +A useful rule of thumb: place the most important information where busy readers expect to find it. BLUF positions the bottom line at the top. Abstracts, executive summaries, and TL;DR headers serve the same function. The specific convention varies by culture -- anecdotal evidence suggests that in some post-Soviet republics, the most important information traditionally appears in the final paragraph, and readers skim bottom-up accordingly. The principle is not "always put it first" but rather "always put it where your specific readers will look first." + +There is a tension worth acknowledging. In warm or relationship-driven contexts, a message that opens with a blunt request can feel cold or presumptuous. Consider two versions of the same sales email: + +- *Courteous order:* "I've thought more about our conversation. Your organisation is not alone in facing the challenges we discussed. I think the services my firm offers could be of use to you. Can we set up a time to discuss you hiring my firm?" +- *BLUF order:* "Can we set up a time to discuss you hiring my firm? I've thought more about our conversation. Your organisation is not alone in facing the challenges we discussed." + +The BLUF version ensures the ask is seen. The courteous version risks the ask being missed if the reader stops early. The practical compromise: one sentence of courteous framing, then the ask. Not three paragraphs of preamble followed by a request the reader never reaches. + +**Rule 2: Separate Distinct Ideas** + +Placing visual space between unrelated topics allows readers to skim without conflating separate issues. The simplest technique is giving each distinct topic its own paragraph. A Danish study of 888 adults tested this: participants read a description of unemployment benefit requirements, half in a single dense paragraph and half with each requirement on its own line. Comprehension was equivalent, but the separated version was read 15% faster. The readers did not need to spend cognitive effort deciding where one idea ended and the next began. + +Bullet points are the strongest visual signal of separation. Numbered lists impose additional sequential logic. Blank space works when neither is appropriate. + +**Rule 3: Place Related Ideas Together** + +Grouping related items reduces search cost. When a project update assigns tasks to two people -- say, Jessie and Marion -- interleaving their items forces both readers to scan the entire list. Clustering Jessie's tasks together and Marion's tasks together allows each person to find their responsibilities immediately. The clustering also enables consolidation: if both of Jessie's tasks involve writing and both of Marion's involve research, the task descriptions can be simplified, reducing total word count from 46 to 39 in the original example tested in the research. + +For messages with multiple requests, the grouping strategy depends on whether the requests relate to the same topic. If they do, cluster them. If each request belongs to a different section, embed it in its section but foreshadow all requests at the top: "Below I cover three items and ask for your input on each: (1) ... (2) ... (3) ..." + +**Rule 4: Order Ideas by Priority** + +The first item in any list receives disproportionate attention. Research on Texas primary elections showed that moving a candidate from last to first on a ballot increased their vote share by up to 10 percentage points in some races. The multibillion-dollar search advertising industry operates on the same principle: the top position in search results captures the most clicks. Amazon exploits this when promoting specific products over others. A study of link positioning on web pages confirmed the pattern quantitatively: the first link received the most clicks, with a steady decline through each subsequent position, and only a minor uptick at the very last position compared to second-to-last. + +When no inherent logic dictates order (chronological, procedural, or causal), default to priority. Place the most important item first. There is modest evidence that the final position in a list also receives slightly elevated attention -- studies of jury trials found that the last evidence presented can be heavily weighted -- but jurors are obligated to sit through the entire trial. Busy readers are under no such obligation. The first position dominates, and the writer who buries a critical item in position four of six is making a bet against the reader's patience. + +**Rule 5: Include Headings** + +Headings function as section labels on a map. Eye-tracking data shows that readers scanning a page fixate on headings before anything else, using them to decide which sections to zoom into and which to bypass entirely. + +A study with the Journalist's Resource tested this directly. A nine-paragraph email newsletter covering three topics was sent to 46,648 subscribers. Half received the newsletter without headings; the other half received the same content with descriptive headings above the second and third topics. Subscribers who received headings were more than twice as likely to click links in those sections. Crucially, engagement with the first section (which had no heading in either version) was unaffected -- the headings did not divert attention, they unlocked it for content that would otherwise have been skipped. + +Headings also prove useful when prefacing bulleted lists. A bullet point does not automatically make its content clear. Messages with full paragraphs attached to each bullet, or lists with so many items that their unifying logic is obscure, benefit from a short heading at the start of each entry: + +- **Revised contract:** The firm's lawyers have agreed to all proposed edits but have requested two additional clauses. Can you review these additions? +- **Conference planning:** We are three months from the conference date. Could we set up a call to finalise the participant list and programme? + +Each heading lets the reader decide in a fraction of a second whether to read the detail that follows. Without it, the reader must parse the entire bullet to determine relevance. + +Headings should describe what follows with enough specificity to be useful but not so much length that they become a reading burden of their own. "What is the school doing?" is better than "Next steps." "School is monitoring all close contacts, and closing and disinfecting the building" is unnecessarily verbose. + +**Rule 6: Use Enough Formatting but No More** + +Formatting -- bold, italic, underline, highlighting, ALL CAPS -- serves two purposes: it conveys meaning beyond the words themselves, and it captures attention through visual contrast. Both purposes degrade with overuse. + +In a study of over 1,600 participants reading a five-paragraph passage, a single highlighted sentence was noticed and acted upon by 89% of readers (versus 65% with no formatting). But when five sentences were highlighted, compliance on the key sentence dropped to 65% -- formatting multiple items diluted the benefit by spreading attention across all of them. A separate study found that highlighting an irrelevant sentence actually decreased reading of the important unhighlighted sentence, from 48% to 39%. Readers inferred that the writer had already marked the important parts and paid less attention to everything else. + +The Goldilocks principle: format the one thing that matters most. If two or three things genuinely matter equally, format them -- but imagine a reader who reads only the formatted text. Will they have grasped the essentials? If not, reconsider. + +Italics and font colour present a different problem: ambiguity. Some readers interpret them as markers of importance; others interpret them as markers of emphasis within a sentence -- a meaningful distinction. "I am very excited" uses italics for emphasis on degree, not for importance. Without explicit guidance ("Key terms are italicised" or "Action items are in blue"), readers must guess. In professional settings where norms have been codified -- legal writing uses italics for case citations, for instance -- the ambiguity resolves. Elsewhere, it persists. + +ALL CAPS deserves special caution. While 75% of survey respondents interpret capitalised text as signalling importance, 25% interpret it as anger. More than three-quarters of the terms-and-conditions contracts for Amazon, Uber, and Facebook contain at least one all-caps paragraph, ostensibly to satisfy "clear and conspicuous" disclosure requirements. Courts have recently questioned whether all-caps text actually achieves this, and research shows capitalised passages take longer to read and can decrease understanding, particularly among older adults. + +Bullets carry their own risk. Readers interpret bulleted items as the most important content in a message. If low-priority items are bulleted while a high-priority request sits in an unformatted paragraph, the reader may attend to the bullets and skip the paragraph. One board chairperson discovered this after bulleting a thirteen-item list of client welcome gifts while embedding the actual request -- scheduling the next board meeting -- in an unformatted paragraph at the bottom. The meeting proved difficult to schedule. + +--- + +## Prompts + +**Prompt 1 -- BLUF Conversion:** +> Rewrite the following message using the BLUF (Bottom Line Up Front) principle. Place the single most important piece of information or request in the first sentence. Follow it with essential supporting context only. Remove or relocate everything else. Original message: [paste text] + +**Prompt 2 -- Navigation Audit:** +> Analyse this document as a map. For each section, identify: (a) whether it has a clear heading, (b) whether distinct ideas are visually separated, (c) whether related ideas are grouped, (d) whether items are ordered by priority, and (e) whether formatting highlights the right elements. Score each rule from 1-5 and provide a redesigned version. Document: [paste text] + +**Prompt 3 -- Formatting Discipline Check:** +> Review this message for formatting overuse or misuse. Count the number of bold, italic, underlined, highlighted, and capitalised elements. For each, assess whether it marks genuinely critical content or dilutes the reader's attention. Then produce a version that formats no more than two elements and achieves greater clarity. Message: [paste text] + +**Prompt 4 -- Cultural BLUF Adaptation:** +> I am writing to [describe audience in a specific cultural or organisational context]. Where would this audience expect to find the key information -- top, bottom, or elsewhere? Restructure the following message to match their expectations while preserving all essential content. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Structuring a One-Page Investor Brief** + +A first-time founder drafts a one-page summary for angel investors. The draft opens with two paragraphs of market context, moves to the team's background, and places the funding ask ($500K pre-seed round) in the final paragraph. An investor who spends eight seconds on the page -- the median for cold inbound -- never reaches the ask. + +Applying the BLUF principle, the founder restructures: the opening line states the ask and the core value proposition ("Raising $500K to eliminate the 72-hour settlement delay in cross-border B2B payments"). Market context moves to a supporting paragraph with a descriptive heading ("The Problem: $47B in annual settlement float"). Team credentials become a two-line sidebar under "Team." The funding terms land under "The Ask" -- bolded, as the single formatted element in the document. The same information, radically different navigability. The first version assumed the investor would walk the path. The second version gave them a map. + +**Early-Traction Startup Redesigning a Covid-Era School Notification** + +A school district sends parents a letter about a confirmed Covid case. The original version opens with three paragraphs of administrative language before revealing the critical fact: the school is closed for 48 hours. A busy parent -- cooking dinner, managing homework -- skims the first lines, sees no clear signal, and defers reading to "later." The redesigned version applies four navigation rules at once: the key fact ("[SCHOOL NAME] will be closed for at least the next 48 hours") appears as the first line after the salutation (Rule 1 and Rule 4), subsequent sections receive descriptive headings -- "What is [School Name] doing?", "How will you know if your child is a close contact?", "What to do if you or your child is sick?" (Rule 5) -- and each topic is visually separated into its own block (Rule 2). + +**Growth-Stage Company Reducing Failure-to-Appear Rates** + +The New York Police Department worked with researchers to redesign its court summons notification. The original form, titled "Complaint/Information," placed the court appearance date and time at the bottom of a dense form, below personal details and charge descriptions. The redesigned version applied all six navigation rules: the title changed to "Criminal Court Appearance Ticket" (Rule 1), court date and location moved to the top (Rule 4), distinct sections were separated (Rule 2), related items -- court address, date, time -- were grouped (Rule 3), clear headings flagged each section (Rule 5), and courthouse selection was converted from handwriting to a bubble-fill format (Rule 6). Over 17 months and nearly 324,000 recipients, failure-to-appear rates fell 13%, resulting in an estimated 23,000 fewer arrest warrants. + +--- + +## Anti-Patterns + +1. **The Chronological Trap.** Telling the story of how a decision unfolded rather than stating the decision and its implications first. Chronological order is the writer's natural instinct; it is almost never the reader's preference. The reader wants the conclusion, not the journey. + +2. **The Bullet Dump.** Listing twelve or more items as bullet points without headings, grouping, or priority ordering. A long, undifferentiated bulleted list is no easier to navigate than a dense paragraph -- it merely looks different. Each bullet should earn its place, and the list should have a clear heading that tells the reader what connects the items. + +3. **The Formatting Carnival.** Combining bold, italic, underline, highlighting, colour changes, and ALL CAPS in a single message. A taxi company email documented by researchers used every available formatting tool simultaneously. When shown to readers, no two agreed on which piece of information the writer considered most important. The effect of formatting many items was worse than formatting none. + +4. **Headings as Decoration.** Using vague headings ("Overview," "Details," "Next Steps") that describe structural positions rather than content. A heading should tell the reader what the section is about, not merely that it exists. "Q3 Revenue: +14% vs. Plan" is a heading. "Update" is a placeholder. + +5. **BLUF Without Warmth.** Applying Bottom Line Up Front so aggressively that the message reads as curt or demanding, especially in contexts where the reader expects a relational overture. The solution is not to abandon BLUF but to insert exactly one sentence of warmth before the ask -- not three paragraphs of it. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Pitch emails, one-pagers, advisor requests | Every document is competing with dozens of others for a distracted reader's attention. Navigation is the difference between "funded" and "filed." BLUF and ruthless brevity dominate. | +| Validation | Investor updates, customer feedback surveys, partnership proposals | Documents grow slightly longer but readers remain impatient. Headings and priority ordering become essential tools for keeping multi-topic updates scannable. | +| Early Traction | Client onboarding materials, internal process docs, support articles | The writer now serves multiple reader personas with different expertise levels. Headings allow each reader to jump directly to their section without wading through irrelevant content. | +| Growth | All-hands emails, policy memos, cross-functional announcements | Document volume and audience size both increase. Navigation standards must be codified into team style guides. The navigation audit becomes a recurring exercise, not a one-time fix. | +| Scale | Templated communications, automated notifications, regulatory filings | Navigation decisions are embedded in templates that serve thousands of readers. Small structural improvements -- moving a key date from paragraph four to the subject line -- compound across enormous volumes. | + +--- + +## Output Template + +```markdown +# Navigation Redesign: [Document / Message Name] + +## BLUF Statement +[One sentence: the single most important thing the reader needs to know or do.] + +## Document Map +1. **[Heading 1]** -- [What this section covers, in six words or fewer] +2. **[Heading 2]** -- [What this section covers] +3. **[Heading 3]** -- [What this section covers] + +## Priority Order +- **Most important:** [Item, placed first] +- **Second:** [Item] +- **Third:** [Item] + +## Formatting Plan +- **Formatted element(s):** [Maximum two -- what is bolded/highlighted and why] +- **Unformatted by design:** [What was deliberately left plain to avoid dilution] + +## Grouping Logic +- **Cluster 1:** [Related items grouped together] +- **Cluster 2:** [Related items grouped together] + +## Redesigned Message +[Full rewrite applying all six rules, annotated with rule numbers in brackets where each is applied] +``` + +--- + +## Related Skills + +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- Provides the cognitive science that explains why navigation works: the F-pattern, working memory limits, and the four-stage triage process that every reader applies. +- **[Writing for Response](../../content/skills/writing/writing-for-response.md)** -- Extends navigation into action: once readers can find the key information, response-oriented design ensures they can act on it within 30 seconds. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- Applies navigation principles to the most common medium for business communication, including subject line craft and scanning-optimised formatting. +- **[Writing Memos and Reports](../../content/skills/writing/writing-memos-and-reports.md)** -- Covers longer-form documents where navigation architecture -- headings, sections, executive summaries -- is the primary determinant of whether the document gets read. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- Provides the sentence-level discipline that complements document-level navigation: fewer words per sentence means less cognitive load at every anchor point. diff --git a/plugins/foreman/skills/writing-for-response/SKILL.md b/plugins/foreman/skills/writing-for-response/SKILL.md deleted file mode 120000 index c274225..0000000 --- a/plugins/foreman/skills/writing-for-response/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-for-response.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-for-response/SKILL.md b/plugins/foreman/skills/writing-for-response/SKILL.md new file mode 100644 index 0000000..07ca0fe --- /dev/null +++ b/plugins/foreman/skills/writing-for-response/SKILL.md @@ -0,0 +1,221 @@ +--- +name: "writing-for-response" +description: "Teaches how to write messages that convert reader understanding into reader action. Covers friction reduction, default design, the power of constrained choices, response-oriented formatting, and the 30-second response test. Use when crafting calls to action in emails or product copy, designing opt-in or enrolment flows, diagnosing low response rates on surveys or meeting requests, or building templates for action-oriented team communications." +version: "1.0.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - response-rate + - call-to-action + - friction + - defaults + - behavioural-design + - enrolment + - action-oriented-writing +related_skills: + - reader-psychology + - writing-for-navigation + - writing-effective-emails + - tone-and-engagement + - writing-with-purpose +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing for Response + +ONE PERCENT. When DC public schools asked parents to enrol in a text-message update programme via an online portal, 1% did. When the schools simplified the process to a single text reply -- respond "START" -- 11% did. When they made enrolment the default and let parents opt out by replying "STOP," 95% stayed. The lesson is not about parental apathy. The parents who ignored the portal were the same parents who stayed enrolled under the default. Motivation was constant across all three groups; friction was the variable. Response rates are not a measure of how much readers care. They are a measure of how much effort the writer demands. + +--- + +## The Framework + +### The Response Gap + +Even when readers understand a message perfectly and want to act on it, three barriers can prevent them from doing so: + +1. **They do not understand what is being asked.** The request is ambiguous, buried, or tangled in surrounding information. This is a clarity failure. +2. **They do not believe the action is worth the effort.** The writer has not established relevance, urgency, or personal stakes. This is a persuasion failure. +3. **The action is too hard or too time-consuming to perform right now.** The reader intends to comply but defers, and deferral is the precursor to forgetting. This is a friction failure. + +Most writers address the first two barriers instinctively. The third is where the opportunity lies -- and where the research is most striking. + +### Three Rules of Easy-Response Writing + +**Rule 1: Simplify the Steps Required to Act** + +The most powerful technique is eliminating steps entirely by changing the default. When an action happens automatically unless the reader opts out, participation rates approach universality. The retirement savings literature makes the case decisively: automatic enrolment with an opt-out option produces dramatically higher participation than opt-in processes requiring deliberate sign-up, even when the financial incentives are identical. + +When changing the default is not feasible, reducing the number of steps still yields large effects. The DC schools study quantified this precisely: moving from a multi-step portal (1% enrolment) to a single-step text reply (11% enrolment) produced a tenfold increase. The parents' interest in their children's grades did not change. The number of actions required did. + +Consider meeting scheduling, a task most professionals perform weekly. The open-ended approach -- "Want to talk next week?" -- initiates a multi-round volley of availability comparisons. Each round imposes a cognitive and logistical cost. An alternative: + +> Want to meet for 30 minutes next week? If so, how about one of these times (all ET): +> - Tuesday (3/13) at 10:30 am +> - Wednesday (3/14) at 12:00 pm +> - Thursday (3/15) at 3:00 pm + +This version specifies duration, proposes concrete options, clarifies time zones, and allows the reader to respond by selecting rather than generating. A study at a major US university tested a further simplification: including a Calendly link that let recipients book directly from the sender's calendar. The Calendly version secured meetings with 33% of recipients versus 17% for the standard "let me know your availability" request. The caveat: some recipients find unsolicited calendar links presumptuous, so the technique requires calibration to context. + +**Rule 2: Organise Key Information Needed for Action** + +Readers who must hunt for information in order to act are readers who will not act. When the US government offered prescription drug benefits to Medicare recipients in 2006, it sent letters directing recipients to a website with an 84-character URL, plus a booklet on how to navigate the site. Only 17% switched to a better plan. Researchers then tested a simplified letter that included the relevant comparison directly: the recipient's current plan, the lowest-cost alternative, the recommended option, and the estimated savings. No website navigation required. The switch rate nearly doubled to 28%, and average savings were $100 per person per year. + +The principle generalises to every action-oriented message. Instead of writing, "See the message below, sent on April 3, and let me know what you think," restate the pertinent information from April 3 in the current message. Searching through an email chain is a step. Every step is a chance for the reader to abandon the task. + +For communications that direct readers to online tools -- forms, portals, applications -- include the specific credentials needed to log in, when privacy constraints allow. "Did you know you can file your immigration forms online at [website]?" becomes significantly more actionable as: "Did you know you can file your immigration forms online? Your username is [name] and you can log in at [website]." One additional line eliminates the "forgot my username" barrier that causes a substantial portion of intended actions to stall. + +**Rule 3: Minimise the Amount of Attention Required** + +The brain's attention budget is finite, and complex decisions accelerate its depletion. A study at a large health services company found that offering employees a preselected retirement plan (with preset contribution rate and asset allocation) increased enrolment by 10 to 20 percentage points compared to requiring them to choose among all available options. Fewer decisions meant more participants. + +Narrow questions outperform broad ones for the same reason. + +| Question Type | Example | Reader Effort | +|---------------|---------|---------------| +| Broad (open-ended) | "How was yesterday's senior staff meeting?" | High. Requires synthesis and composition. | +| Narrow (constrained) | "In yesterday's meeting, did we decide whether we're submitting a bid?" | Low. Answerable with yes or no. | + +The broad question may yield richer feedback -- but only if the reader responds at all, which the data suggests is less likely. + +Excess choice creates what researchers call an "attention tax." Studies confirm that when people face too many options, they defer the decision -- often permanently. President Obama reportedly limited his wardrobe to grey and blue suits for precisely this reason: "I'm trying to pare down decisions. I don't want to make decisions about what I'm eating or wearing. Because I have too many other decisions to make." + +The ultimate test of attention minimisation is the **30-second response test**: can a reader act on this message within 30 seconds of opening it? If the answer is no, the message needs structural revision -- fewer steps, more constrained choices, or information that was missing and must now be supplied directly. + +### Multiple Requests: Bundle or Separate? + +Action-oriented messages frequently contain more than one request. A healthcare clinic, for instance, may need to (1) collect insurance information, (2) provide check-in instructions, and (3) confirm an appointment time. All three are urgent and related. In a survey of working professionals, 72% said they prefer receiving one message with three pieces of information over three separate messages. When requests relate to the same event and require similar levels of effort, bundling makes sense. + +The calculus changes when requests require different amounts of effort. A family email asking what time a relative will arrive (easy), what holiday gifts to buy (moderate), and where to find a lost family recipe (hard) bundles three fundamentally different cognitive tasks. The reader may answer the easy question and forget the rest -- or defer the entire message until they have time for the hardest question, a moment that may never arrive. Separating unequal requests into distinct messages protects the easy ones from being held hostage by the hard. + +When bundling is unavoidable, signpost the structure at the top: "Below are three items: (1) an update on the renovation, (2) a request for your approval on light fixtures, and (3) a request to schedule a call." The preview gives the reader a map before they enter the territory. + +### The Friction Spectrum in Practice + +| Friction Level | Mechanism | Typical Response Rate | +|----------------|-----------|----------------------| +| Zero (default) | Action happens unless reader opts out | 90-95% compliance | +| Minimal (one-step) | Single reply, single click, or single selection | 10-35% compliance | +| Moderate (multi-step) | Navigate to portal, log in, complete form | 1-5% compliance | +| High (complex) | Research options, make multiple decisions, find credentials | Below 1% | + +These numbers shift by context, audience, and stakes, but the gradient is remarkably consistent across domains -- from school enrolment to retirement savings to voter registration to meeting scheduling. + +### The IRS and the Power of Simple Instructions + +A study with the US Internal Revenue Service tested different styles of notification about the Earned Income Tax Credit, a benefit that eligible low-income workers must actively claim each year (roughly 20% of those eligible fail to do so). The simplified version included a clear, step-by-step explanation of what to do: complete the worksheet, determine eligibility, sign and return if eligible. The complex original version listed six bullet points of instructions plus a footnote. The complex notice produced a response rate 27% lower than the simple one. Moreover, a worksheet with seven eligibility criteria generated 17% fewer responses than one with just two criteria. The additional detail was accurate and potentially useful. It was also, in practice, a deterrent. + +--- + +## Prompts + +**Prompt 1 -- Friction Audit:** +> Map every step a reader must take to act on the following message. For each step, estimate the time and cognitive effort required. Then propose a revised version that eliminates at least two steps while preserving all essential outcomes. Message: [paste text] + +**Prompt 2 -- Default Design:** +> I need [describe audience] to [describe desired action]. The current approach requires them to opt in. Design an alternative that makes the desired action the default, with a clear and easy opt-out mechanism. Include the exact language for the initial communication and the opt-out instructions. + +**Prompt 3 -- 30-Second Response Test:** +> Apply the 30-second response test to this message. Assume the reader opens it on a mobile phone while walking between meetings. Can they complete the requested action in 30 seconds? If not, identify the bottleneck and rewrite the message to pass the test. Message: [paste text] + +**Prompt 4 -- Constrained Choice Conversion:** +> The following message asks the reader an open-ended question. Rewrite it as a constrained-choice question with no more than three predefined response options. Preserve the writer's intent while reducing the reader's cognitive load. Message: [paste text] + +--- + +## Use Cases + +**Idea-Stage Founder Scheduling Investor Meetings** + +A pre-seed founder sends 30 emails per week requesting introductory meetings with potential investors. The standard close reads: "Would love to find a time to chat -- let me know what works for you." This open-ended request requires the investor to check their calendar, compose available times, and manage the resulting back-and-forth. The founder switches to a constrained format: three specific time slots with durations and time zones, plus a Calendly link as a fallback. Meeting conversion from cold email rises from 4% to 11%. The pitch itself did not improve. The path from "interested" to "booked" shortened. + +**Validation-Stage Startup Increasing Survey Completion** + +A consumer health startup sends a post-onboarding survey to 2,000 beta users. The survey contains 14 open-ended questions and takes approximately eight minutes to complete. Completion rate: 6%. The product team diagnoses the problem using the friction spectrum: the survey sits at "moderate" friction (click link, load page, read 14 questions, compose 14 answers). Eight minutes is an eternity for a user who signed up three days ago. + +The team applies the three rules systematically. They reduce the survey to five questions (Rule 3), convert four of them to multiple-choice with a free-text "Other" option (Rule 3), and embed the first question directly in the email body so readers can begin answering before they even click through to the survey platform (Rule 1). The email subject line changes from "Share your feedback" to "One quick question about your first session." Completion rate rises to 23%. The qualitative richness of individual responses decreases modestly, but the sample size nearly quadruples, improving the statistical reliability of every finding. + +**Growth-Stage Company Driving Adoption of a New Expense Tool** + +A 400-person company rolls out a new expense reporting tool. The finance team sends an all-hands email with a three-paragraph explanation, a link to a 20-minute training video, and instructions to "set up your account by Friday." Adoption after one week: 22%. The team redesigns the rollout communication. The email now opens with a single sentence ("Submit expenses in two clicks -- your account is already active"), includes a direct link to the tool with the user's credentials pre-filled, and replaces the training video with a three-step inline guide (Rule 2). A 15-second GIF shows the complete submission flow. The message passes the 30-second response test: a reader can click, submit a test expense, and confirm their account works in under half a minute. Adoption after one week with the new approach: 71%. + +--- + +## Anti-Patterns + +1. **The Open-Ended Ask.** "Let me know your thoughts" or "When are you free?" These phrases feel polite. They are also friction machines. Each one transfers the cognitive burden of structuring a response from the writer to the reader. A constrained alternative -- "Does Tuesday at 2 pm work?" -- reduces the reader's task from composition to selection. + +2. **The Portal Redirect.** Directing readers to log into an external system to complete an action that could have been completed within the message itself. Every redirect -- especially one requiring credentials -- is a cliff that a large percentage of readers will not climb. The DC schools study measured the cliff at 99% attrition for portal-based enrolment. + +3. **The Information Scavenger Hunt.** Asking readers to act but making them search through prior emails, attachments, or external documents to assemble the information needed. If acting on a request requires data, include the data. If the data is too long to include, summarise it and link to the source, but never assume the reader will retrieve it independently. + +4. **The Choice Overload.** Offering six meeting times, twelve plan options, or eight survey response categories when three would suffice. Research consistently shows that excess choice induces decision paralysis. The IRS study on Earned Income Tax Credit applications found that a worksheet with seven eligibility criteria produced a 17% lower response rate than one with two criteria -- despite containing more useful information. + +5. **The Assumed Follow-Through.** Sending a message that requires action "by end of week" without any follow-up mechanism. Present-bias means readers are structurally inclined to defer. A single well-timed reminder -- sent close to the deadline, not at the beginning of the week -- significantly increases completion rates. Research on medical appointment reminders, savings programmes, and child support payments all confirm this effect. A study on voter registration found that the first five reminder mailings each incrementally increased turnout, but the last five of ten had no further effect. In a Kenyan HIV treatment study, weekly reminders improved adherence by 32%, while daily reminders produced no improvement at all -- likely because their frequency caused patients to tune them out. The principle: remind enough to overcome procrastination, but not so much that reminders become noise. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Meeting requests, advisor asks, survey invitations | Every interaction is a cold start. The reader has no relationship-driven reason to tolerate friction. Requests must be answerable in a single action -- one click, one reply, one selection. | +| Validation | Beta user engagement, investor commitment letters, LOI signatures | The stakes of each response rise. Friction audits of high-value requests (signing an LOI, committing capital) reveal surprisingly removable barriers -- a pre-filled signature block, a direct DocuSign link. | +| Early Traction | Customer onboarding, feature adoption, support ticket resolution | Response design shifts from one-to-one to one-to-many. Templates for common action requests (account setup, feedback, renewals) must pass the 30-second test at scale. | +| Growth | Internal process adoption, cross-team coordination, policy compliance | Friction compounds across a growing organisation. A five-step expense process that "only takes three minutes" costs 400 person-hours per year in a 400-person company. Default design and one-step actions become operational priorities. | +| Scale | Automated enrolment flows, renewal campaigns, regulatory filings | Response architecture is embedded in product and operations. A/B testing of default configurations, step counts, and CTA placements becomes a quantitative practice affecting millions of interactions. | + +--- + +## Output Template + +```markdown +# Response Design: [Message / Flow Name] + +## Desired Action +[One sentence: what the reader should do after reading.] + +## Current Friction Map +| Step | Action Required | Est. Time | Drop-off Risk | +|------|----------------|-----------|---------------| +| 1 | [e.g., Open email] | 2 sec | Low | +| 2 | [e.g., Click link] | 3 sec | Medium | +| 3 | [e.g., Log into portal] | 45 sec | High | +| 4 | [e.g., Find and complete form] | 3 min | Very High | + +## 30-Second Response Test +- **Passes?** [Yes / No] +- **Bottleneck:** [The step where the 30-second budget is exceeded] + +## Redesign Strategy +- **Default option:** [If applicable -- what happens if the reader does nothing?] +- **Steps eliminated:** [Which steps were removed and how] +- **Information pre-supplied:** [What data was added to the message to prevent searching] +- **Choice constraints applied:** [Open-ended questions converted to selections] + +## Revised Message +[Full rewrite, structured for minimum friction, annotated with rule numbers] + +## Follow-Up Plan +- **Reminder timing:** [When to send, relative to deadline] +- **Reminder content:** [Abbreviated version restating the ask and the single easiest step] +``` + +--- + +## Related Skills + +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- Explains the cognitive constraints (working memory, present-bias, attention depletion) that make friction so lethal to response rates. +- **[Writing for Navigation](../../content/skills/writing/writing-for-navigation.md)** -- Ensures readers can find the call to action in the first place; response-oriented design is ineffective if the request is buried in an unnavigable message. +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- The inbox is the most common arena for response-oriented writing; email-specific tactics complement the friction-reduction principles here. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Tone calibration influences Stage 2 of the reader's triage process, which directly affects whether the reader reaches the call to action at all. +- **[Writing with Purpose](../../content/skills/writing/writing-with-purpose.md)** -- Clarifying the writer's goal before drafting is the prerequisite for designing an effective response mechanism. +- **[Cialdini's Influence](../../content/skills/frameworks/cialdini-influence.md)** -- Reciprocity, scarcity, and commitment principles explain the psychology behind why specific friction-reduction techniques increase response rates. diff --git a/plugins/foreman/skills/writing-memos-and-reports/SKILL.md b/plugins/foreman/skills/writing-memos-and-reports/SKILL.md deleted file mode 120000 index a9c4c27..0000000 --- a/plugins/foreman/skills/writing-memos-and-reports/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-memos-and-reports.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-memos-and-reports/SKILL.md b/plugins/foreman/skills/writing-memos-and-reports/SKILL.md new file mode 100644 index 0000000..06aae65 --- /dev/null +++ b/plugins/foreman/skills/writing-memos-and-reports/SKILL.md @@ -0,0 +1,217 @@ +--- +name: "writing-memos-and-reports" +description: "Provides a systematic approach to structuring memos, reports, and business letters that inform decisions and drive action. Covers the Issue-Solution-Reason summary framework, the Who-Why-What-When-How planning chart, visual aids, three-audience writing, and business letter conventions. Use when drafting board memos, internal recommendations, market analysis reports, strategic proposals, client-facing letters, or any document longer than an email that must survive scrutiny from multiple readers." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - validation + - early-traction + - growth + - scale +tags: + - memos + - reports + - business-letters + - document-structure + - executive-summary + - decision-making +related_skills: + - tone-and-engagement + - grammar-and-mechanics + - writing-effective-emails + - writing-performance-reviews +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing Memos and Reports + +Every memo is a decision document. The question is not whether it will influence a decision, but which one -- and whether the writer has been deliberate about the answer. A memo ostensibly about switching paper suppliers is actually a document about cost discipline, vendor relationships, and operational reliability. A report on declining chocolate sales is actually a recommendation to reposition an entire product line. The writers who understand this produce documents that get read, circulated, and acted upon. The writers who do not produce documents that get filed. + +The distinction between the two lies not in the quality of the analysis but in the quality of the structure. A brilliant insight buried in paragraph seven of an unsummarised report is, for all practical purposes, an insight that does not exist. + +--- + +## The Framework + +### The Issue-Solution-Reason Summary + +Every memo and report should open with a summary that answers three questions, in this order: + +1. **Issue:** What is the problem or question, stated so that anyone can understand it? +2. **Proposed Solution:** What do you recommend? +3. **Reason:** Why is this solution preferable to alternatives? + +Consider two approaches to the same recommendation: + +**Weak Summary:** +> "The cell phone changeover that has been proposed should be rejected. For the reasons stated below, the company would not be well served by accepting the proposal." + +**Strong Summary:** +> "Last year, we adopted an officewide policy of issuing cell phones to all executives and sales reps at an annual cost of $58,000. The Persephone company has proposed that we switch to its phones and service at $37,000. The committee recommends rejecting this proposal for four reasons: (1) significantly less coverage in Europe and Asia, (2) our current provider's superior responsiveness, (3) potential costs from dropped calls that dwarf the $21,000 savings, and (4) Persephone's inferior customer service ratings." + +The second version can be fully understood by anyone who reads it, at any time. The first assumes familiarity with context that readers may not have. + +### The Who-Why-What-When-How Planning Chart + +Before writing, answer five questions: + +| Question | Key Point | +|----------|-----------| +| **Who** are you writing for? | Consider your audience's concerns, motivations, and background. | +| **Why** are you writing? | Keep your purpose firmly in mind. Every sentence should advance it. | +| **What** needs saying? | Include only the main points and details that get your message across. | +| **When** are you expecting action? | State your time frame explicitly. | +| **How** will your communication benefit readers? | Make it clear how you are meeting their needs. | + +This chart is not a writing exercise -- it is a thinking exercise. Most poorly structured documents fail not at the writing stage but at the planning stage. The writer who cannot answer these five questions before drafting will not produce a document that answers them after. + +### Writing for Three Audiences + +Every memo and report serves three simultaneous readerships: + +**Primary audience:** Executives who want conclusions, recommendations, and key data. They will read the summary and skim the rest. Write the summary for them. + +**Secondary audience:** Reviewers who may be called in to assess the document's soundness. They will examine your methodology, challenge your assumptions, and check your facts. Write the body for them. + +**Future audience:** Readers two years from now who will need to extract information from a document they did not commission and may lack context for. Write with enough specificity and context that the document stands on its own. + +### Title Selection + +The title or subject line is the document's first promise to the reader. Vague titles break that promise before the reader begins. + +| Weak Title | Strong Title | +|-----------|-------------| +| Subject: Siegelson | Subject: Approval of Siegelson Acquisition | +| Subject: Settlement | Subject: Why We Should Reject Frost's Settlement Offer | +| Subject: Print Run | Subject: Ginsburg Autobiography Print Run | + +Strong titles tell readers both the topic and what they should do about it. + +### Using Graphics and Visual Aids + +When writing about complex information, a well-placed chart or diagram conveys at a glance what paragraphs of prose struggle to communicate. Three principles govern effective visuals: + +- The graphic must illustrate something discussed in the text -- never use decoration for its own sake. +- Place it near the text it supports, preferably on the same page. +- Use legends and labels that readers can grasp without consulting the text. + +Make graphics distinctive and use them sparingly. If every third page contains a chart, the visual emphasis is nullified. + +### Business Letter Conventions + +Business letters, despite their apparent obsolescence, remain necessary for formal situations: correcting vendor errors, recommending job candidates, announcing services, delivering bad news with appropriate gravity. + +**Focus on the reader.** Open with *you*, not *I*. "You might be interested..." rather than "I just thought I'd drop you a note..." + +**Say something substantive.** Replace filler ("I trust this finds you prospering in your personal life...") with genuine content ("I hope your family dodged the fires last week -- which sounded devastating"). + +**Avoid hedging.** Replace "It is with regret that we acknowledge that we do not appear at this time to be in a position to extend an offer of employment" with "We're sorry to say that we aren't now hiring." + +**Ease into bad news.** Open on a genuine positive note, then explain the negative and its reasoning. Readers absorb bad news better when they do not encounter it in the first sentence. + +--- + +## Prompts + +**Prompt 1 -- Memo Structure Builder:** +> I need to write a memo about [describe topic] for [describe audience]. The recommendation is [describe]. Help me structure it using the Issue-Solution-Reason framework. Draft the summary section, then outline the body sections with recommended content for each. Include three supporting arguments and identify the strongest counterargument I need to address. + +**Prompt 2 -- Report Outline Generator:** +> I am preparing a report on [describe topic] for [describe audience]. The report needs to address [describe key questions]. Generate a detailed outline that includes: a summary section written for executives, a body structured for reviewers, and enough context for future readers who lack inside knowledge. Recommend where visual aids would be most effective. + +**Prompt 3 -- Business Letter Drafter:** +> Draft a business letter for the following situation: [describe context -- e.g., declining a proposal, responding to a complaint, recommending a candidate]. The tone should be [describe -- e.g., firm but diplomatic, warm and personal, professional and direct]. The recipient is [describe]. Include a before/after comparison if the letter delivers bad news. + +**Prompt 4 -- Document Audit:** +> Review this memo/report for structural effectiveness. Assess: (1) whether the summary could stand alone as a complete briefing, (2) whether the body supports the summary with evidence, (3) whether the title accurately signals the content and required action, (4) whether a non-expert reader two years from now would understand the document. Provide specific revision recommendations. Document: [paste text] + +--- + +## Use Cases + +**Validation-Stage Startup Writing Its First Board Memo** +A startup preparing for its first advisory board meeting needs to present a recommendation to pivot from B2C to B2B. The founder drafts a five-page narrative that reads like a journal entry -- chronological, discursive, burying the recommendation on page four. After restructuring with the Issue-Solution-Reason framework, the memo opens with a three-sentence summary: the issue (B2C unit economics are unsustainable at current CAC), the solution (pivot to B2B with existing technology), and the reasoning (three enterprise pilots show 4x better margins with 60% lower acquisition costs). The board reads the summary, nods, and spends the meeting discussing implementation rather than deciphering the problem. + +**Growth-Stage Company Producing a Market Analysis Report** +A product team writes a 20-page market analysis for the executive team. The original version opens with four pages of methodology before reaching any findings. The executives, who allocate twenty minutes to each report, never reach the findings. Restructured with the three-audience model: a one-page summary for executives (primary audience), a methodology section for the VP of strategy who will evaluate rigour (secondary audience), and comprehensive data tables with source citations for the analyst who will update the report next quarter (future audience). Every reader gets what they need without wading through content meant for someone else. + +**Scale-Stage Organisation Standardising Memo Templates** +A 1,000-person company discovers that its memos follow no consistent structure. Some open with recommendations; others bury them. Some include summaries; others do not. Readers waste time adapting to each writer's idiosyncratic format. The company adopts a standard memo template based on the Issue-Solution-Reason framework, with required sections for summary, body, and recommendations. Document quality, as measured by decision-maker satisfaction surveys, improves 40% in the first quarter -- not because the analysis improved, but because the presentation did. + +--- + +## Anti-Patterns + +1. **The Summary-Free Report.** A report that plunges into analysis without summarising what it found or recommends. Executives who lack time to read the full document -- which is most of them -- never encounter the conclusion. The report produces analysis without influencing decisions. + +2. **The Vague Title.** "Subject: Q3" tells the reader nothing about content, purpose, or required action. It guarantees the memo will be opened only by people with nothing better to do, which is precisely the audience least likely to act on it. + +3. **Burying the Recommendation.** Presenting all evidence chronologically and revealing the conclusion at the end, as though writing a detective novel. Business readers do not want suspense. They want the answer first and the supporting evidence second. + +4. **Writing for Yourself Instead of the Reader.** Structuring the document in the order you discovered the information rather than the order the reader needs it. The research journey and the presentation of findings are different sequences. The reader does not need to retrace your steps. + +5. **Overloading with Visuals.** Charts on every page dilute the impact of any single chart. Graphics should be deployed sparingly and only when they communicate something more effectively than prose can. A bar chart showing two numbers is not more informative than a sentence. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Validation | Advisory board memos and investor updates | Documents are short, high-stakes, and read by people who evaluate the founder's thinking as much as the content. Clarity and structure signal analytical competence. | +| Early Traction | Client proposals and internal recommendations | The company begins producing documents that commit resources. Memos that recommend hiring, spending, or changing direction need rigorous structure to withstand scrutiny. | +| Growth | Cross-functional reports and board materials | Multiple teams produce reports for leadership. Without structural standards, the board receives documents in twenty different formats, wasting cognitive energy on navigation rather than evaluation. | +| Scale | Institutional document standards | Memo and report templates become organisational infrastructure. Style guides, training programmes, and editorial review ensure consistency across hundreds of document authors. | + +--- + +## Output Template + +```markdown +# [Document Title: Specific and Action-Oriented] + +## Summary +**Issue:** [One to two sentences defining the problem or question] + +**Proposed Solution:** [One to two sentences stating the recommendation] + +**Reason:** [Two to four sentences explaining why this solution is preferable] + +## Background +[Context necessary for readers unfamiliar with the topic -- no more than is needed] + +## Analysis +### [Finding/Argument 1] +[Evidence and reasoning] + +### [Finding/Argument 2] +[Evidence and reasoning] + +### [Finding/Argument 3] +[Evidence and reasoning] + +## Counterarguments Considered +[Strongest objection and why the recommendation still holds] + +## Recommendations +1. [Specific action, owner, and timeline] +2. [Specific action, owner, and timeline] + +## Appendix +[Supporting data, methodology, or detailed tables for secondary and future audiences] +``` + +--- + +## Related Skills + +- **[Writing Effective Emails](../../content/skills/writing/writing-effective-emails.md)** -- When a message exceeds one screen, it likely belongs in a memo rather than an email; knowing when to switch formats is itself a skill. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- Reports are particularly susceptible to passive voice and nominalizations; the tone framework provides the diagnostic tools for revision. +- **[Grammar and Mechanics](../../content/skills/writing/grammar-and-mechanics.md)** -- Formal documents that persist in the organisational record demand the highest standard of grammatical precision. +- **[Writing Performance Reviews](../../content/skills/writing/writing-performance-reviews.md)** -- Performance reviews are a specialised form of the memo, applying the same structural principles to the evaluation of individuals. +- **[Writing for Navigation](../../content/skills/writing/writing-for-navigation.md)** -- The navigation architecture of headings, sections, and executive summaries determines whether a multi-page document gets read or abandoned. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- Long-form documents amplify the cost of verbosity; the concision techniques are essential for keeping reports at a length readers will tolerate. diff --git a/plugins/foreman/skills/writing-performance-reviews/SKILL.md b/plugins/foreman/skills/writing-performance-reviews/SKILL.md deleted file mode 120000 index 3fc9e55..0000000 --- a/plugins/foreman/skills/writing-performance-reviews/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-performance-reviews.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-performance-reviews/SKILL.md b/plugins/foreman/skills/writing-performance-reviews/SKILL.md new file mode 100644 index 0000000..83319d8 --- /dev/null +++ b/plugins/foreman/skills/writing-performance-reviews/SKILL.md @@ -0,0 +1,256 @@ +--- +name: "writing-performance-reviews" +description: "Guides the high-stakes process of writing performance appraisals that are specific, fair, legally defensible, and genuinely useful for employee development. Covers the seven evaluation dimensions (attitude, efficiency, human relations, judgment, knowledge, reliability, communication), the spectrum from superb to poor, the discipline of pairing evaluative language with concrete evidence, and the legal implications of imprecise writing. Use when preparing annual or quarterly reviews, designing performance evaluation templates, training first-time managers on review writing, or auditing existing review practices for fairness and consistency." +version: "1.0.0" +category: "writing" +complexity: "advanced" +stage: + - early-traction + - growth + - scale +tags: + - performance-reviews + - employee-evaluation + - management + - hr-writing + - legal-risk + - feedback + - talent-development +related_skills: + - giving-feedback + - grammar-and-mechanics + - tone-and-engagement + - writing-memos-and-reports +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing Performance Reviews + +A well-written performance review builds a career. A poorly written one invites a lawsuit. Between these extremes lies the vast wasteland of vague, unhelpful evaluations that serve neither the employee nor the organisation: "Meets expectations." "Good team player." "Could improve communication skills." These phrases occupy space on a form without communicating anything that the employee can act upon, the organisation can calibrate against, or a court can interpret as evidence of fair process. The performance review is arguably the highest-stakes document a manager writes, yet it receives less training, less editorial oversight, and less structural rigour than almost any other form of business writing. + +The cost of this neglect is measurable. Vague positive reviews make it nearly impossible to justify promotion decisions when challenged. Vague negative reviews provide no legal foundation for termination. And the employees themselves -- the ostensible audience for the document -- learn nothing from prose that could apply equally to any person in any role. + +--- + +## The Framework + +### The Seven Evaluation Dimensions + +The framework identifies seven aspects of work that performance reviews should address. Not every review covers all seven -- the selection depends on the role and the review period. But the framework provides a comprehensive vocabulary for evaluation. + +**1. Attitude** + +| Level | Descriptors | +|-------|-------------| +| Superb | Shows unwavering commitment; always gives maximal effort; is always friendly and happy to help; always brings out the best in others | +| Good | Shows strong commitment; usually makes a strong effort; is usually friendly and happy to help | +| Acceptable | Shows adequate commitment; makes an effort; is often friendly and happy to help | +| Needs Improvement | Could show more commitment; doesn't always make an effort; is sometimes quarrelsome | +| Poor | Lacks commitment; rarely makes a real effort; is quarrelsome and sometimes even hostile | + +**2. Efficiency** + +| Level | Descriptors | +|-------|-------------| +| Superb | Never wastes time or effort; delegates effectively; always completes tasks on time; manages many projects simultaneously | +| Good | Rarely wastes time; usually delegates appropriately; almost always completes tasks on time | +| Needs Improvement | Sometimes wastes time and effort; tries to do too much without delegating; fails to complete tasks on time | +| Poor | Often wastes time and effort; usually fails to delegate; struggles to manage even one project at a time | + +**3. Human Relations** + +| Level | Descriptors | +|-------|-------------| +| Superb | Demonstrates keen sensitivity to others; participates actively and collegially in meetings; works exceptionally well on teams; relates to customers extremely well | +| Good | Usually demonstrates sensitivity; participates effectively in meetings; works effectively on teams | +| Needs Improvement | Does not always pick up on interpersonal cues; sometimes wastes others' time in meetings; is sometimes motivated more by personal goals than team goals | +| Poor | Rarely pays attention to others' reactions; often wastes others' time; does not work well on teams; often alienates customers | + +**4. Judgment** + +| Level | Descriptors | +|-------|-------------| +| Superb | Makes excellent choices and informed decisions; remains utterly calm and collected in crisis; knows precisely which problems need immediate attention | +| Good | Makes sound choices; remains relatively calm in crisis; generally knows which problems need immediate attention | +| Needs Improvement | Sometimes makes poor choices; sometimes lacks composure in high-pressure circumstances; often doesn't distinguish between urgent and non-urgent | +| Poor | Often makes poor choices and ill-informed decisions; often lacks the calm required in high-pressure circumstances | + +**5. Knowledge** + +| Level | Descriptors | +|-------|-------------| +| Superb | Exceptionally well informed about all aspects of the job; demonstrates extraordinarily comprehensive knowledge; handles complex assignments without supervision | +| Good | Well informed about key aspects; demonstrates thorough knowledge; handles complex assignments with some supervision | +| Needs Improvement | Doesn't fully understand the job; demonstrates less than satisfactory knowledge; sometimes mishandles assignments of moderate complexity | +| Poor | Ill-informed about many aspects of the job; demonstrates inadequate knowledge; mishandles basic assignments | + +**6. Reliability** + +| Level | Descriptors | +|-------|-------------| +| Superb | Always meets deadlines; is unfailingly dependable; achieves excellent results in urgent situations; always delivers on promises | +| Good | Meets deadlines; is highly dependable; achieves good results in urgent situations | +| Needs Improvement | Sometimes fails to meet important deadlines; is sometimes undependable; sometimes fails to deliver on promises | +| Poor | Often fails to meet deadlines; is rarely dependable; can't be counted on to deliver on promises | + +**7. Communication Skills** + +| Level | Descriptors | +|-------|-------------| +| Superb | Writes and speaks with remarkable clarity; never gets bogged down in unnecessary details; has superior communication skills in person and over the phone | +| Good | Writes and speaks clearly; rarely gets bogged down; has sound communication skills | +| Needs Improvement | Sometimes writes and speaks unclearly and with undue complexity; sometimes gets bogged down in unnecessary details | +| Poor | Writes and speaks unclearly; gets bogged down in unnecessary details; fails to communicate effectively | + +### The Cardinal Rule: Pair Every Assessment with Evidence + +A performance descriptor is a hypothesis. Evidence is what makes it credible. + +**Vague (useless):** +> "Lauren shows unwavering commitment." + +**Specific (useful):** +> "When we had several layoffs last June, Lauren remained utterly calm and collected while demonstrating keen sensitivity to those who lost their jobs. She personally conducted exit interviews with each affected team member, ensured their final paycheques were processed within 24 hours, and organised a quiet send-off that preserved the dignity of the departing employees." + +The first version could describe anyone. The second version describes exactly one person doing exactly one set of things. This specificity serves three purposes: it tells the employee precisely what behaviour to continue, it provides the organisation with a defensible record, and it demonstrates that the reviewer was actually paying attention. + +### The Legal Dimension + +Performance reviews are legal documents whether managers intend them as such or not. They are discoverable in litigation, admissible as evidence, and routinely used to support or undermine claims of wrongful termination, discrimination, and retaliation. + +Three legal imperatives for review writers: + +1. **Consistency.** A trail of "exceeds expectations" reviews followed by a sudden termination invites a wrongful-termination claim. If performance is deteriorating, the reviews must reflect the deterioration -- contemporaneously, not retroactively. + +2. **Specificity.** "Poor attitude" is a conclusion. A court will ask: what, specifically, constituted the poor attitude? When did it occur? Was the employee notified? What was the expected standard? If the review cannot answer these questions, the assessment is legally indefensible. + +3. **Fairness.** Applying different evaluative standards to different employees performing the same role -- even unconsciously -- creates exposure to discrimination claims. The seven-dimension framework, applied consistently, provides a structured defence against inconsistency. + +--- + +## Prompts + +**Prompt 1 -- Review Drafter:** +> I need to write a performance review for [describe employee, role, and tenure]. Over the review period, the key observations are: [list 3-5 specific situations, behaviours, and outcomes]. Draft a review that covers the relevant evaluation dimensions, pairs every assessment with the specific evidence I've provided, and maintains a tone that is honest, constructive, and respectful. Include both strengths and areas for development. + +**Prompt 2 -- Vagueness Eliminator:** +> Here is a draft performance review: [paste text]. Identify every instance of vague or unsupported evaluative language. For each, flag the vague phrase, explain why it is insufficient, and suggest a specific revision that pairs the assessment with observable evidence. If evidence is missing, indicate what kind of evidence would be needed. + +**Prompt 3 -- Difficult Review Preparation:** +> I need to write a performance review for an underperforming employee. The situation: [describe specific performance issues with dates and examples]. I need the review to be (1) honest about the performance gaps, (2) specific enough to be legally defensible, (3) constructive enough to give the employee a genuine path to improvement, and (4) documented clearly enough to support further action if improvement doesn't occur. Draft the review with these four objectives in mind. + +**Prompt 4 -- Review Template Designer:** +> Design a performance review template for a [describe company size and stage] company. The template should cover [specify which of the seven evaluation dimensions are most relevant for the roles in the company]. Include structured fields that force reviewers to provide specific evidence for every rating, a self-assessment section for the employee, and a development-plan section that translates the review into forward-looking commitments. + +--- + +## Use Cases + +**Early-Traction Startup Conducting Its First Reviews** +A 15-person startup runs its first performance review cycle. The CEO, having never written a review, produces evaluations that read like casual character references: "Alex is great, super dependable, and the team loves working with him." This is gratifying for Alex but useless for calibration. After applying the seven-dimension framework, the review becomes: "Alex demonstrates exceptional reliability -- he has met every sprint deadline this quarter and was the sole engineer who volunteered for the holiday on-call rotation. His knowledge of our payment infrastructure is comprehensive, and he handles complex debugging assignments without supervision. His area for development is communication: his technical documentation, while accurate, sometimes assumes reader familiarity with the codebase that new team members do not have." Alex now knows what to keep doing and what to develop. + +**Growth-Stage Company Defending a Termination Decision** +A 200-person company terminates an underperforming sales manager. The manager files a wrongful-termination claim, alleging that the termination was discriminatory. The company's defence rests on a trail of performance reviews documenting specific, dated instances of underperformance across three consecutive quarters: missed pipeline targets (with exact numbers), client complaints (with specific dates and descriptions), and failure to implement the agreed-upon improvement plan (with milestone dates and gaps). The reviews, written using the evidence-pairing discipline, provide a documentary foundation that withstands legal scrutiny. A less rigorous review trail -- "needs improvement in sales performance" -- would have been nearly indefensible. + +**Scale-Stage Organisation Calibrating Across Managers** +A 500-person company discovers significant inconsistency in how managers rate performance. One department rates 80% of employees as "superb"; another rates only 15% as such for comparable performance. By standardising on the seven-dimension framework with required evidence for each rating, the company enables meaningful cross-department calibration sessions. Managers must justify their ratings against specific behavioural indicators, reducing the influence of personal bias and relationship dynamics. + +--- + +## Anti-Patterns + +1. **The Recency Trap.** Evaluating an entire year based on the last three weeks because the reviewer kept no notes during the intervening months. Performance reviews require continuous documentation -- not a frantic retrospective the night before the form is due. + +2. **The Halo Effect.** Allowing exceptional performance in one dimension to inflate ratings across all dimensions. An engineer who writes brilliant code but alienates every colleague deserves a "superb" in knowledge and a "needs improvement" in human relations. Conflating the two produces a review that is inaccurate and unhelpful. + +3. **Euphemism as Kindness.** Describing genuine performance problems in language so gentle that the employee does not recognise them as problems. "Could benefit from additional focus on timeliness" does not communicate the same urgency as "Has missed four of the last six project deadlines, resulting in two client escalations." False kindness in reviews is a form of dishonesty that ultimately harms the employee. + +4. **The Copy-Paste Review.** Reusing the same language across multiple employees' reviews, changing only the name. This signals -- accurately -- that the reviewer invested no effort in individualised assessment. It also creates legal exposure if employees compare reviews and find identical language applied to different performance levels. + +5. **Avoiding Negative Feedback Entirely.** Writing exclusively positive reviews for fear of confrontation, then using a sudden termination to address performance issues that were never documented. This pattern is both legally dangerous and managerially irresponsible. The employee never received a genuine opportunity to improve because the written record suggested nothing needed improving. + +6. **Weaponising the Review.** Using the performance review to settle personal grievances, document subjective "attitude" complaints without evidence, or build a paper trail for a predetermined termination. Reviews serve the employee's development and the organisation's record. Using them as a political tool corrodes institutional trust. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Early Traction | First-time managers writing first reviews | Managers who have never written a review need a framework. Without one, they default to either vague praise or uncomfortable avoidance of constructive feedback. The seven-dimension model provides immediate structure. | +| Growth | Consistency across a growing management layer | With ten or twenty managers writing reviews independently, calibration becomes essential. The framework provides a common vocabulary that enables cross-manager comparison and reduces bias. | +| Scale | Institutional review infrastructure | At scale, performance reviews are embedded in HR systems, tied to compensation decisions, and subject to legal review. Templates, training programmes, and calibration sessions ensure quality at volume. | + +--- + +## Output Template + +```markdown +# Performance Review: [Employee Name] +**Review Period:** [start date] to [end date] +**Reviewer:** [name and title] +**Date:** [review date] + +## Summary Assessment +[2-3 sentences capturing overall performance, key strengths, and primary development areas] + +## Dimension Assessments + +### Attitude +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact that supports this rating] + +### Efficiency +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Human Relations +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Judgment +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Knowledge +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Reliability +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +### Communication Skills +**Rating:** [Superb / Good / Acceptable / Needs Improvement / Poor] +**Evidence:** [Specific situation, behaviour, and impact] + +## Key Strengths (with Evidence) +1. [Strength + specific example] +2. [Strength + specific example] + +## Development Areas (with Evidence and Plan) +1. [Area + specific example + agreed-upon improvement action + timeline] +2. [Area + specific example + agreed-upon improvement action + timeline] + +## Goals for Next Review Period +1. [Specific, measurable goal] +2. [Specific, measurable goal] +3. [Specific, measurable goal] + +## Employee Self-Assessment Notes +[Space for employee's own perspective, captured during the review conversation] +``` + +--- + +## Related Skills + +- **[Giving Feedback](../../content/skills/frameworks/giving-feedback.md)** -- The SBI feedback model provides the real-time complement to written performance reviews; reviews document what ongoing feedback conversations have already addressed. +- **[Grammar and Mechanics](../../content/skills/writing/grammar-and-mechanics.md)** -- Performance reviews carry legal implications, making grammatical precision a matter of institutional risk, not merely style. +- **[Tone and Engagement](../../content/skills/writing/tone-and-engagement.md)** -- The tone of a performance review must balance honesty with respect; the tone framework provides the calibration tools for this balance. +- **[Writing Memos and Reports](../../content/skills/writing/writing-memos-and-reports.md)** -- Performance reviews are a specialised memo form; the structural principles of clear titles, up-front summaries, and evidence-based argumentation apply directly. +- **[Radical Candor](../../content/skills/frameworks/radical-candor.md)** -- The balance of caring personally and challenging directly is the tonal foundation for reviews that are both honest and constructive. +- **[Employee Engagement and Retention](../../content/skills/leadership/employee-engagement-retention.md)** -- Reviews are a primary retention lever; how they are written directly affects whether employees feel seen and invested in or evaluated and discarded. diff --git a/plugins/foreman/skills/writing-process/SKILL.md b/plugins/foreman/skills/writing-process/SKILL.md deleted file mode 120000 index 99d5173..0000000 --- a/plugins/foreman/skills/writing-process/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-process.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-process/SKILL.md b/plugins/foreman/skills/writing-process/SKILL.md new file mode 100644 index 0000000..5f47f38 --- /dev/null +++ b/plugins/foreman/skills/writing-process/SKILL.md @@ -0,0 +1,214 @@ +--- +name: "writing-process" +description: "Teaches the MACJ writing process -- Madman, Architect, Carpenter, Judge -- a four-phase method for producing effective business documents by separating idea generation, organisation, drafting, and editing into distinct sequential tasks. Covers brainstorming, outlining in sets of three, speed writing, and disciplined revision. Use when facing writer's block, struggling to organise complex material, drafting reports or proposals, or when any business document feels overwhelming to start." +version: "1.0.0" +category: "writing" +complexity: "intermediate" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - process + - drafting + - brainstorming + - outlining + - editing + - productivity + - business-writing +related_skills: + - writing-with-purpose + - revising-and-editing + - clarity-and-concision + - business-writing-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# The Writing Process + +Good writing is controlled schizophrenia. Four distinct personalities live inside every writer, and the quality of the output depends entirely on whether they are allowed to work in sequence or forced to compete simultaneously. The Madman is the wild-eyed gatherer of raw material -- ideas, facts, hunches, contradictions. The Architect imposes order, distilling chaos into structure. The Carpenter builds sentences and paragraphs, hammering prose into shape. The Judge polishes, tightens, and corrects. Let the Madman and the Judge occupy the same room, and the result is paralysis: one generates, the other censors, and nothing gets written. The secret to productive writing is not talent. It is sequencing. + +Betty Sue Flowers, the poet and professor who formalised this framework as MACJ, understood that most writing anxiety stems from attempting all four tasks at once. The moment a writer types a sentence and immediately questions whether it is good enough, the Carpenter and the Judge are fighting for the keyboard. Peter Drucker made the complementary observation that good writing, like good innovation, takes "careful, conscious work, not a flash of genius." The MACJ framework operationalises that insight. + +--- + +## The Framework + +### Phase 1: The Madman (Gathering) + +The Madman gathers material without judgement. Ideas from memory, research, observation, conversations, speculation, and imagination -- all are welcome. The goal is volume, not quality. + +**How to run the Madman phase:** + +- Brainstorm freely. Write down every idea, fact, question, and half-formed thought related to the topic. +- Distinguish facts from opinions. Note sources. Put direct quotes in quotation marks. +- Use a spreadsheet or list with labels indicating the points each piece of evidence supports. +- Do not evaluate. Do not organise. Do not write sentences. The Madman's job is to prevent the problem of "finally thinking of your best point after you've finished and distributed your document." + +The Madman phase pays compound interest. Time invested here prevents hours of staring at a blank screen later. + +### Phase 2: The Architect (Organising) + +The Architect takes the Madman's raw material and imposes structure. The key discipline: **organise in sets of three.** + +A mathematician once observed that there are really only four numbers: one, two, three, and many. Four items overload working memory. One or two points feel underdeveloped. Three is the structural sweet spot for business writing -- substantial enough to be persuasive, concise enough to be memorable. + +**The Architect's method:** + +1. Write down three main points as complete sentences (not topics, not fragments -- full propositions that convey the argument). +2. Arrange them in the most logical order from the reader's perspective. +3. Group supporting material under each point. + +Consider an office manager asked to write a memo about acquiring a new building. The Madman brainstorms a list of fifteen topics -- ownership, maintenance, tax consequences, parking, insurance, signage. The Architect groups these into three categories: tasks for the boss (before acquisition), tasks for the manager (before acquisition), and tasks for the manager (after acquisition). What was an overwhelming list of fifteen items becomes three clear sections, each with three supporting points. + +The Architect's outline is bare-bones -- three sentences and their subordinate groupings. That is all the structure the Carpenter needs. + +### Phase 3: The Carpenter (Drafting) + +The Carpenter writes as quickly as possible. Speed is not sloppiness -- it is strategy. + +**Rules for the Carpenter phase:** + +- **Write against the clock.** Allow 5 to 10 minutes per section (opener, body, closer). Set a timer. +- **Do not edit as you go.** The editorial part of the brain is incompatible with the production part. Letting the Judge kibitz during drafting is multitasking at its worst -- two things done inefficiently rather than one thing done well. +- **Do not wait for inspiration.** After the Madman and Architect have worked, the Carpenter should be primed. Schedule the time, sit down, and begin. +- **Start with whatever section feels most comfortable.** When stuck, skip to another section. If still stuck, say aloud what the passage is trying to convey. Speaking often unlocks the right words. +- **Accept imperfection.** The first draft will be imperfect. That is the point. Perfection is the Judge's job, and the Judge is not invited yet. + +Sentences written at speed tend to be shorter and more natural than sentences laboured over. The draft takes shape before the writer has time to second-guess it. Pain decreases as duration decreases. + +### Phase 4: The Judge (Polishing) + +Once the draft is complete, the Judge takes over. This phase requires as much time as the research and writing phases combined. + +**The Judge works in multiple passes, each focusing on one dimension:** + +- **Pass 1: Accuracy.** Are the facts correct? Are citations precise? +- **Pass 2: Tone.** Does the tone match the purpose and audience? +- **Pass 3: Transitions.** Does one sentence glide into the next without discontinuities? +- **Pass 4: Economy.** Can any words be cut without losing meaning? +- **Pass 5: Grammar and punctuation.** The final mechanical sweep. + +Attempting all five passes simultaneously guarantees that none is done well. Sequential focus produces exponentially better results. + +--- + +## Prompts + +**Prompt 1 -- Madman Brainstorm:** +> I need to write a [document type] about [topic] for [audience]. Help me run the Madman phase: generate a comprehensive, unfiltered list of every point, fact, argument, counter-argument, example, and question that could be relevant. Do not organise or evaluate -- just generate. Include ideas I might not have considered. + +**Prompt 2 -- Architect Outline:** +> Here is my raw brainstorm for a [document type]: [paste Madman output]. Now be the Architect: group this material into three main points, each expressed as a complete sentence. Arrange them in the most logical order from the reader's perspective, and assign supporting material under each point. Identify any gaps where additional Madman work is needed. + +**Prompt 3 -- Carpenter Speed Draft:** +> Here is my three-point outline for a [document type]: [paste Architect output]. Now be the Carpenter: write a rapid, complete first draft. Do not over-polish -- prioritise getting all ideas on paper in a natural, flowing sequence. I will edit later. Include an opener, a body structured around the three points, and a closer. + +**Prompt 4 -- Judge Passes:** +> Here is my first draft of a [document type]: [paste Carpenter output]. Now be the Judge. Run five sequential editing passes and show me the result after each: (1) fact-check and flag anything unverified, (2) evaluate tone against my purpose of [state purpose], (3) improve transitions between paragraphs, (4) cut unnecessary words, (5) correct grammar and punctuation. Show the final polished version. + +--- + +## Use Cases + +**Early-Traction Startup Writing a Series A Memo** + +A founder needs to write a 10-page investment memo but feels overwhelmed by the scope. Applying MACJ: The **Madman** spends two hours gathering material -- market data, customer quotes, revenue figures, competitive analysis, team bios, product roadmap, risk factors. The **Architect** distils this into three core propositions: (1) the market is large and underserved, (2) the product has demonstrated early traction with strong unit economics, (3) the team has a unique right to win. Each proposition gets a supporting evidence cluster. The **Carpenter** drafts each section in timed 10-minute blocks, producing a rough but complete draft in under two hours. The **Judge** spends a full day running multiple editing passes -- tightening prose, verifying data, calibrating tone for a sophisticated investor audience. The final document is coherent, persuasive, and completed in three days rather than the three weeks of anxious procrastination that preceded the MACJ adoption. + +**Growth-Stage Company Producing a Quarterly Board Report** + +A VP of Operations dreads the quarterly board report because it requires synthesising input from six departments. The MACJ framework transforms the process. The **Madman** phase involves collecting raw updates from each department head (structured as bullet points, not prose). The **Architect** organises these into three board-level themes: operational performance, strategic initiatives, and risk factors. The **Carpenter** drafts the narrative in a single sitting, using the outline to maintain momentum. The **Judge** reviews over two days, with each pass focused on a single dimension. The result: a board report that takes three days instead of two weeks, with higher quality because each phase received undivided attention. + +--- + +## Anti-Patterns + +1. **Letting the Judge into the Carpenter's Workshop.** The most destructive anti-pattern. Editing while drafting feels productive but is actually paralysing. Every sentence gets scrutinised before the next one begins, and the draft never gains momentum. The result is either a polished opening paragraph followed by nothing, or a document that took five times longer than necessary. + +2. **Skipping the Architect.** Writers who brainstorm and then draft without organising produce documents that wander. The reader can sense the absence of structure -- ideas repeat, the argument circles back on itself, and the conclusion contradicts the opening. Three sentences of outline prevent hours of structural revision. + +3. **Brainstorming in Sentences.** The Madman should generate topics, fragments, and raw ideas -- not polished prose. Writers who brainstorm in full sentences are unconsciously editing (inviting the Judge early) and constraining their creative range. + +4. **Single-Pass Editing.** The Judge who tries to check facts, improve tone, tighten prose, and fix grammar in one reading will miss errors in every category. Focused sequential passes -- even if each is quick -- produce dramatically better results than one heroic sweep. + +5. **Waiting for Inspiration.** Inspiration is not a prerequisite; it is a byproduct. The Madman and Architect phases generate the raw material that makes the Carpenter productive. Waiting for a "flash of genius" before beginning is waiting for a bus on a train line. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision articulation | The Madman phase is dominated by imagination and analogy rather than data. The Architect must structure a narrative around possibility, not proof. The Carpenter's voice should convey conviction. | +| Validation | Evidence synthesis | The Madman phase becomes research-heavy -- customer interviews, pilot data, market sizing. The Architect organises around evidence categories. The Judge must verify every claim. | +| Early Traction | Multi-document management | Founders write constantly -- investor updates, customer proposals, team memos. MACJ prevents each document from consuming disproportionate time. Templated Architect outlines accelerate repetitive formats. | +| Growth | Delegation of phases | At growth stage, different people can own different phases. A subject-matter expert runs the Madman, a communications lead serves as Architect and Carpenter, and leadership plays Judge. The framework scales because it decomposes writing into separable tasks. | +| Scale | Process standardisation | MACJ can be embedded into organisational writing standards -- requiring outlines before drafts, prohibiting single-pass editing, mandating peer review during the Judge phase. | + +--- + +## Output Template + +```markdown +# MACJ Writing Plan: [Document Title] + +## Purpose +[One sentence: what this document must achieve] + +## Phase 1: Madman Output +### Raw Ideas +- [Idea/fact/question 1] +- [Idea/fact/question 2] +- [...] + +### Sources to Gather +- [ ] [Data point or reference needed] +- [ ] [Interview or input needed] + +## Phase 2: Architect Outline +### Main Point 1: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Main Point 2: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Main Point 3: [Complete sentence] +- Supporting evidence: [...] +- Supporting evidence: [...] + +### Logical Order: [1 → 2 → 3] or [reorder with rationale] + +## Phase 3: Carpenter Schedule +- Opener: [time block] +- Section 1: [time block] +- Section 2: [time block] +- Section 3: [time block] +- Closer: [time block] + +## Phase 4: Judge Passes +- [ ] Pass 1: Accuracy and fact-checking +- [ ] Pass 2: Tone alignment with purpose +- [ ] Pass 3: Transitions and flow +- [ ] Pass 4: Word economy +- [ ] Pass 5: Grammar and punctuation +- [ ] Peer review requested from: [Name] +``` + +--- + +## Related Skills + +- **[Writing with Purpose](../../content/skills/writing/writing-with-purpose.md)** -- Purpose must be defined before the Madman begins gathering; without a clear objective, the brainstorm has no anchor. +- **[Revising and Editing](../../content/skills/writing/revising-and-editing.md)** -- Expands the Judge phase into a comprehensive revision and editing methodology with concrete before/after examples. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- The Judge's Pass 4 (word economy) is governed by the principles of concision detailed in this companion skill. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- The Architect phase benefits from the flow and continuity principles that transform a logical outline into prose that reads smoothly. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Daily writing habits for leaders; MACJ provides the process backbone that makes those habits efficient. +- **[Creative Flow and Inspiration](../../content/skills/creative/creative-flow-and-inspiration.md)** -- The Madman phase mirrors the creative practice of receiving inspiration without judgment; both depend on separating generation from evaluation. diff --git a/plugins/foreman/skills/writing-with-purpose/SKILL.md b/plugins/foreman/skills/writing-with-purpose/SKILL.md deleted file mode 120000 index a2528e1..0000000 --- a/plugins/foreman/skills/writing-with-purpose/SKILL.md +++ /dev/null @@ -1 +0,0 @@ -../../../../.claude/skills/writing/writing-with-purpose.md \ No newline at end of file diff --git a/plugins/foreman/skills/writing-with-purpose/SKILL.md b/plugins/foreman/skills/writing-with-purpose/SKILL.md new file mode 100644 index 0000000..43c6f5b --- /dev/null +++ b/plugins/foreman/skills/writing-with-purpose/SKILL.md @@ -0,0 +1,208 @@ +--- +name: "writing-with-purpose" +description: "Teaches how purpose and audience analysis determine the form, tone, and content of every business communication. Applies the principle that the same facts, addressed to the same reader, produce radically different letters depending on the writer's objective. Use when drafting any business document, preparing investor updates, writing customer communications, crafting fundraising emails, or any situation where the writer is unsure what tone to strike or how to frame a message." +version: "1.1.0" +category: "writing" +complexity: "basic" +stage: + - idea + - validation + - early-traction + - growth + - scale +tags: + - writing + - communication + - purpose + - audience + - tone + - persuasion + - business-writing +related_skills: + - writing-process + - clarity-and-concision + - revising-and-editing + - business-writing-for-leaders +author: "Fatih Guner" +--- + +Read [runtime](../../content/RUNTIME.md) and [advisory rules](../../content/policies/advisory.md) before applying this skill. Other Foreman layers and the catalog are in `../../content/`, relative to this SKILL.md. + + +# Writing with Purpose + +Same facts. Same recipient. Three entirely different letters -- and three entirely different outcomes. A company discovers its landlord has violated the Americans with Disabilities Act during a building renovation. The general counsel flags the issue. Someone must write to the landlord. But *why* are they writing? To gather information, because the landlord is a friend? To demand compliance, because a disabled employee needs access? To terminate the lease, because the relationship has already soured? Each purpose produces a different document in tone, structure, and diction -- even though the underlying facts have not changed by a single comma. + +This is the foundational insight that separates competent business writers from everyone else: purpose is not a detail to consider after the writing begins. Purpose is the architecture that determines everything else. + +--- + +## The Framework + +### Purpose Determines Form + +Before typing a single word, a writer must answer one question with precision: *What do I want the reader to do after reading this?* The answer governs every subsequent decision -- word choice, sentence length, level of formality, degree of directness, and the balance between warmth and firmness. + +Consider the ADA violation scenario across three different purposes: + +| Purpose | Tone | Salutation | Key Move | +|---------|------|------------|----------| +| Gather information (friendly inquiry) | Warm, non-confrontational | "Dear Ann" | Compliments the renovation, raises the issue as a question, closes with a lunch invitation | +| Correct the oversight (firm request) | Professional, measured urgency | "Dear Ann" | Acknowledges the renovation positively, states the legal concern directly, requests assurance of a 60-day fix, mentions regulatory reporting as a consequence | +| Terminate the lease (decisive exit) | Firm, civil, bridge-preserving | "Dear Ms. Reynolds" | States the violation, invokes legal entitlement, serves 30 days' notice, expresses hope for continued goodwill | + +The shift from "Dear Ann" to "Dear Ms. Reynolds" alone signals a tectonic change in intent. Every element -- from the opening pleasantry to the closing line -- serves the purpose. No sentence is neutral. + +### Understanding Your Readers + +Purpose without audience awareness is a monologue. Communication is a two-way exercise, and without understanding reader psychology, even a well-intentioned message lands flat. The critical audience realities are: + +- **Readers are busy.** Ascend the organisational hierarchy and this tendency intensifies. A CEO scanning an inbox has no duty to finish a rambling message. +- **They will not struggle.** At the slightest friction, readers stop trying -- and think less of the writer. +- **They must see the benefit.** The ever-important "what's in it for them" must be visible early, or the message will be ignored. + +### The Buffett Principle + +Warren Buffett, in his preface to the SEC's *Plain English Handbook*, offered a deceptively simple technique for writing to large audiences: "I pretend that I'm talking to my sisters. Though highly intelligent, they are not experts in accounting or finance. They will understand plain English, but jargon may puzzle them." + +The principle: choose a specific, intelligent non-specialist in the audience and write for that person. The resulting prose strikes a balance between sophistication and accessibility that serves everyone. + +### The Goal Discipline: What Do You Want Readers to DO? + +Most writers default to informational writing -- they tell readers what they know. Far fewer practise action-oriented writing -- telling readers what to do with what they know. *Writing for Busy Readers* draws a sharp line between these two modes and argues that the distinction is the single most consequential decision a writer makes before drafting. + +The discipline is simple in principle and difficult in practice: before writing, complete two sentences. First: "The most important thing I want the reader to *understand* is ___." Second: "The most important thing I want the reader to *do* is ___." If the second sentence remains blank, the communication is informational. That is sometimes appropriate -- a market research summary, a background briefing. But if the writer *intended* the reader to act and failed to specify the action, the message will produce understanding without movement. The reader nods and moves on. + +*Writing for Busy Readers* frames this as a design problem, invoking Don Norman's *The Design of Everyday Things*: if a person cannot figure out how to use a door handle, that is the designer's fault, not the user's. If a reader overlooks the writer's intended action, that is the writer's fault. The burden of clarity falls entirely on the author. Writers who do not know their own goals cannot expect readers to infer them -- and when readers are left to interpret what matters, they will frequently interpret wrong. + +The practical implication is that goal-setting is not a one-time exercise but a revision loop. An initial draft often reveals that the writer's stated purpose and actual purpose diverge. The writing process itself clarifies thinking -- as organisational psychologist Adam Grant puts it: "Turning thoughts into words sharpens reasoning. What's fuzzy in your head is clear on the page." Effective writers revise not only for style and structure but for goal alignment, asking on each pass: does every sentence advance the reader toward the intended action? + +| Writing Mode | Writer's Question | Example | +|--------------|-------------------|---------| +| Informational | "What should the reader know?" | "Q3 revenue declined 12% due to customer churn in the enterprise segment." | +| Action-oriented | "What should the reader do?" | "Q3 revenue declined 12% due to enterprise churn. We need board approval by Friday to fund the retention programme outlined in Appendix B." | + +The second version contains the same information as the first. It also contains a verb, a deadline, and a specific request. The difference between a document that informs and a document that moves people is almost always one sentence -- the sentence that states what the writer actually wants. + +### Tailoring the Message + +Audience tailoring goes beyond tone. Consider where readers sit in the organisation, what they are expected to contribute, and what pressures they face. A memo to engineers about a product pivot emphasises technical implications. The same pivot, communicated to investors, emphasises market rationale and unit economics. The facts are identical; the framing is not. + +The writer's job is to answer five questions before writing: + +1. **Who** am I writing for? (Their concerns, motivations, background) +2. **Why** am I writing? (Every sentence should advance this purpose) +3. **What** needs saying? (Only the main points that deliver the message) +4. **When** are actions expected? (State the time frame) +5. **How** does this benefit the reader? (Make the value explicit) + +--- + +## Prompts + +**Prompt 1 -- Purpose Clarification:** +> I need to write a [type of document] to [recipient/audience]. The situation is: [describe the facts]. I have not yet decided what I want this communication to achieve. Help me identify three possible purposes I could have, and for each, show me how the tone, structure, and key message would differ. Then help me choose the purpose that best serves my strategic objectives. + +**Prompt 2 -- Audience Analysis:** +> My company is at the [stage] stage. I need to communicate [topic/news] to [specific audience: investors / team / customers / board / partners]. Profile this audience: what are their likely concerns, priorities, and time constraints? What do they need to hear first? What framing will resonate? Then draft an outline tailored to this audience. + +**Prompt 3 -- Purpose-Tone Calibration:** +> Here is a draft I have written: [paste draft]. My intended purpose is [state purpose] and my audience is [describe audience]. Evaluate whether my tone, structure, and word choices actually serve this purpose, or whether they inadvertently signal a different intent. Identify specific passages where purpose and execution are misaligned and suggest revisions. + +**Prompt 4 -- The Buffett Test:** +> I am writing [document type] that will be read by a diverse audience ranging from [technical specialists] to [non-specialists]. Apply the Buffett "writing to my sisters" test: rewrite my draft so that an intelligent non-specialist can follow every point without jargon, while preserving the substance and precision that specialists expect. Here is my draft: [paste draft]. + +**Prompt 5 -- Goal Extraction and Action Alignment:** +> Here is a draft I have written: [paste draft]. Apply the goal discipline: (1) State in one sentence what the reader is meant to *understand* after reading this. (2) State in one sentence what the reader is meant to *do* after reading this. (3) If the action is missing, unclear, or buried, identify exactly where the draft fails to convert understanding into action. (4) Rewrite the draft so that the intended action is unmistakable -- with a specific verb, a deadline where applicable, and a clear next step. Preserve the informational content but ensure the document moves readers, not merely informs them. + +--- + +## Use Cases + +**Validation-Stage Founder Writing a Rejection to an Investor's Term Sheet** + +A founder has received a term sheet with unfavourable liquidation preferences. The investor is well-connected and may be valuable later. The purpose is not to burn the bridge -- it is to decline this specific offer while keeping the relationship warm. Applying purpose-driven writing, the founder opens with genuine appreciation for the investor's time and interest, acknowledges specific aspects of the term sheet that were attractive, explains concisely why the terms do not align with the company's current needs, and closes with an explicit door-opener for future conversations. The tone is warm, the message is clear, and the strategic relationship is preserved. + +**Growth-Stage CEO Communicating a Pivot to Three Audiences Simultaneously** + +A SaaS company is pivoting from horizontal to vertical. The CEO must write to three audiences: investors (who care about market size and burn rate), the engineering team (who care about technical debt and roadmap), and enterprise customers (who care about continuity and support). Same pivot, three documents. For investors: market opportunity framing, competitive moat, revised projections. For engineers: technical rationale, new architecture direction, timeline. For customers: reassurance, migration plan, dedicated support commitment. The Buffett principle applies to each -- but the "sister" is different every time. + +--- + +## Anti-Patterns + +1. **Writing Before Knowing the Purpose.** The most common failure. Writers open a blank document and begin typing, hoping the purpose will emerge from the prose. It rarely does. The result is a meandering message that the reader cannot act on because the writer could not articulate what action they wanted. + +2. **Confusing Self-Expression with Communication.** The purpose of business writing is to produce a reaction in the reader -- not to document the writer's thought process. A memo that catalogues everything the writer knows about a topic, rather than what the reader needs to know, serves the writer's ego, not the reader's time. + +3. **One Tone for All Audiences.** Sending the same message to investors, employees, and customers is not efficiency -- it is laziness. Each audience has different concerns, different knowledge levels, and different reactions to the same words. "Restructuring" means opportunity to an investor and terror to an employee. + +4. **Burying the Purpose.** Some writers treat the purpose as a conclusion to be earned, placing it at the end of a long preamble. Business readers skim. If the purpose is not visible within the first two sentences, many readers will never find it. + +5. **Letting Tone Undermine Purpose.** A letter meant to preserve a relationship that opens with legal threats. A fundraising email that sounds apologetic. When tone contradicts purpose, the reader receives the tone, not the purpose. + +--- + +## By Stage + +| Stage | Focus | Key Difference | +|-------|-------|----------------| +| Idea | Vision communication | Purpose is almost always persuasion -- convincing cofounders, early advisors, or pre-seed investors to believe in something that does not yet exist. Tone must balance confidence with intellectual honesty. | +| Validation | Evidence presentation | Purpose shifts toward demonstrating traction. The audience (investors, pilot customers) wants data, not vision. The writer's job is to let evidence speak while framing it strategically. | +| Early Traction | Multi-audience management | The founder now writes to investors, customers, employees, and partners -- often about the same events. Purpose diverges by audience. A single "update" template no longer suffices. | +| Growth | Institutional voice | Communications begin representing the company, not the founder. Purpose must be calibrated for scale -- one email may reach thousands of customers. The Buffett principle becomes essential. | +| Scale | Precision and legal awareness | At scale, every written communication carries reputational and legal weight. Purpose must be defined with precision because ambiguity can trigger regulatory, contractual, or public-relations consequences. | + +--- + +## Output Template + +```markdown +# Communication Purpose Brief + +## Document Type +[Email / Memo / Letter / Report / Announcement] + +## Purpose Statement +[One sentence: "The purpose of this communication is to [verb] so that the reader [desired action/reaction]."] + +## Audience Profile +- **Primary reader(s):** [Who] +- **Their key concern:** [What they care about most] +- **Their knowledge level:** [Expert / Informed / Non-specialist] +- **Their time constraints:** [Seconds / Minutes / Will read in full] + +## The Buffett Test +- **My "sister" for this audience:** [Specific person or archetype] +- **Jargon to eliminate:** [List] +- **"What's in it for them" statement:** [One sentence] + +## Tone Calibration +- **Warmth level:** [Warm / Professional / Formal / Firm] +- **Directness level:** [Indirect / Measured / Direct / Blunt] +- **Formality markers:** [First name / Title / Salutation style] + +## Structure +1. **Opening** (purpose visible in first two sentences): [Draft] +2. **Body** (evidence, context, or rationale): [Key points] +3. **Close** (desired action, next steps, relationship signal): [Draft] + +## Pre-Send Checklist +- [ ] Purpose is stated or unmistakable within the first paragraph +- [ ] Every sentence advances the purpose +- [ ] Tone matches the intent (no contradictions) +- [ ] "What's in it for the reader" is visible +- [ ] No jargon the audience would not understand +- [ ] Appropriate level of formality for the relationship +``` + +--- + +## Related Skills + +- **[Writing Process](../../content/skills/writing/writing-process.md)** -- Purpose is the prerequisite; process is the execution. Once purpose is clear, the MACJ framework provides the method for drafting. +- **[Clarity and Concision](../../content/skills/writing/clarity-and-concision.md)** -- A clear purpose demands clear prose; wordiness and ambiguity undermine even the most well-defined intent. +- **[Plain Language and Flow](../../content/skills/writing/plain-language-and-flow.md)** -- The Buffett principle connects directly to plain-language techniques that make writing accessible to diverse audiences. +- **[Reader Psychology](../../content/skills/writing/reader-psychology.md)** -- Purpose defines who the reader is; reader psychology explains how that reader processes information and makes triage decisions. +- **[Business Writing for Leaders](../../content/skills/leadership/business-writing-for-leaders.md)** -- Provides daily writing practices for leaders; this skill supplies the foundational technique for determining what to say and how to say it. +- **[Writing for Response](../../content/skills/writing/writing-for-response.md)** -- When the purpose requires reader action, the friction-reduction techniques transform intent into measurable response rates. diff --git a/scripts/anonymize-author.sh b/scripts/anonymize-author.sh index 64ab888..2efce57 100755 --- a/scripts/anonymize-author.sh +++ b/scripts/anonymize-author.sh @@ -1,143 +1,4 @@ -#!/usr/bin/env bash -# -# anonymize-author.sh — Remove all references to a specified author name. -# -# Usage: -# ./scripts/anonymize-author.sh --name "John Smith" (dry-run, all files) -# ./scripts/anonymize-author.sh --name "John Smith" --in .claude/.claude/skills/ (dry-run, scoped) -# ./scripts/anonymize-author.sh --name "John Smith" --apply (execute) -# ./scripts/anonymize-author.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Defaults ────────────────────────────────────────────────────────── -AUTHOR_NAME="" -SEARCH_DIR="" -APPLY=false - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -anonymize-author.sh — Remove all references to a specified author name. - -USAGE - ./scripts/anonymize-author.sh --name "NAME" Dry-run, all .md files - ./scripts/anonymize-author.sh --name "NAME" --in DIR Dry-run, scoped to DIR - ./scripts/anonymize-author.sh --name "NAME" --apply Execute replacements - ./scripts/anonymize-author.sh --help - -OPTIONS - --name NAME The author name to remove (exact match, case-sensitive) - --in DIR Scope the search to a directory (relative to project root) - --apply Execute replacements (default is dry-run) - --help Show this help message - -REPLACEMENT STRATEGY - - Frontmatter "author:" field -> "Anonymous Contributor" - - Body text references -> context-appropriate alternatives: - "the framework", "the author", "the research", "the text" - -EXAMPLES - ./scripts/anonymize-author.sh --name "John Smith" - ./scripts/anonymize-author.sh --name "John Smith" --in .claude/.claude/skills/ --apply -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) AUTHOR_NAME="$2"; shift 2 ;; - --in) SEARCH_DIR="$2"; shift 2 ;; - --apply) APPLY=true; shift ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -[[ -z "$AUTHOR_NAME" ]] && die "--name is required." - -# Resolve search directory -if [[ -n "$SEARCH_DIR" ]]; then - if [[ "$SEARCH_DIR" != /* ]]; then - SEARCH_DIR="$PROJECT_ROOT/$SEARCH_DIR" - fi - [[ ! -d "$SEARCH_DIR" ]] && die "Directory not found: $SEARCH_DIR" -else - SEARCH_DIR="$PROJECT_ROOT" -fi - -# ── Scan ────────────────────────────────────────────────────────────── -echo "" -if [[ "$APPLY" == true ]]; then - echo " ANONYMIZE AUTHOR: \"$AUTHOR_NAME\" (APPLYING CHANGES)" -else - echo " ANONYMIZE AUTHOR: \"$AUTHOR_NAME\" (DRY RUN)" -fi -echo " Scope: $(echo "$SEARCH_DIR" | sed "s|$PROJECT_ROOT/||")" -echo " $(printf '%60s' '' | tr ' ' '=')" -echo "" - -total_replacements=0 -total_files=0 - -while IFS= read -r file; do - [[ ! -f "$file" ]] && continue - - # Count occurrences - count=$(grep -c "$AUTHOR_NAME" "$file" 2>/dev/null || echo 0) - [[ "$count" -eq 0 ]] && continue - - rel_path=$(echo "$file" | sed "s|$PROJECT_ROOT/||") - total_files=$((total_files + 1)) - total_replacements=$((total_replacements + count)) - - echo " $rel_path ($count occurrence(s))" - - if [[ "$APPLY" == true ]]; then - # Replace in frontmatter author field - sed -i '' "s/^author: \"$AUTHOR_NAME\"/author: \"Anonymous Contributor\"/" "$file" - - # Replace in body text with context-appropriate alternatives - # First, handle possessive forms (e.g., "John Smith's framework") - sed -i '' "s/${AUTHOR_NAME}'s framework/the framework/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s research/the research/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s model/the model/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s theory/the theory/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s work/the work/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s method/the method/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s approach/the approach/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s book/the text/g" "$file" - sed -i '' "s/${AUTHOR_NAME}'s/the author's/g" "$file" - - # Replace standalone name occurrences (not in frontmatter, handled above) - # Use a general replacement for remaining body references - sed -i '' "s/$AUTHOR_NAME/the author/g" "$file" - - # Restore the frontmatter replacement (in case the general one caught it) - sed -i '' "s/^author: \"the author\"/author: \"Anonymous Contributor\"/" "$file" - - echo " -> Replaced" - fi - -done < <(find "$SEARCH_DIR" -name "*.md" -not -path "*/.git/*" -not -path "*/_schema/*" -not -path "*/node_modules/*") - -echo "" -echo " $(printf '%60s' '' | tr ' ' '-')" -echo " Files affected: $total_files" -echo " Total occurrences: $total_replacements" - -if [[ "$APPLY" == false ]]; then - echo "" - echo " Dry-run mode. No changes written." - echo " Add --apply to execute replacements." -fi -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" anonymize-author "$@" diff --git a/scripts/broken-refs.sh b/scripts/broken-refs.sh index b2745e6..e12a1fd 100755 --- a/scripts/broken-refs.sh +++ b/scripts/broken-refs.sh @@ -1,399 +1,4 @@ -#!/usr/bin/env bash -# -# broken-refs.sh — Scans all files across all layers for broken references -# -# Checks markdown links, frontmatter arrays referencing skills, templates, -# diagnostics, and playbooks. Reports every broken reference with its -# source file and expected path. -# -# Usage: -# ./scripts/broken-refs.sh [--help] [--verbose] -# -# Exit codes: -# 0 No broken references found -# 1 One or more broken references found -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -SKILLS_DIR="$PROJECT_ROOT/skills" -TEMPLATES_DIR="$PROJECT_ROOT/output-templates" -DIAGNOSTICS_DIR="$PROJECT_ROOT/diagnostics" -PLAYBOOKS_DIR="$PROJECT_ROOT/playbooks" -HOOKS_DIR="$PROJECT_ROOT/hooks" - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL_REFS=0 -BROKEN_REFS=0 -BROKEN_DETAILS=() - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat < %s\n" "$ref_type" "$ref_val" "$expected" - BROKEN_DETAILS+=("$file|$ref_type|$ref_val|$expected") -} - -log_ok() { - if [[ $VERBOSE -eq 1 ]]; then - local ref_type="$1" ref_val="$2" - printf " ${GREEN}OK${NC} [%s] %s\n" "$ref_type" "$ref_val" - fi -} - -extract_frontmatter() { - local file="$1" - sed -n '1{/^---$/!q}; 1,/^---$/{/^---$/!p}' "$file" | sed '1{/^---$/d}' -} - -field_exists() { - local fm="$1" key="$2" - echo "$fm" | grep -qE "^${key}:" -} - -get_list_items() { - local fm="$1" key="$2" - echo "$fm" | awk -v k="^${key}:" '$0 ~ k {found=1; next} found && /^[[:space:]]*-/{print; next} found{exit}' \ - | sed 's/^[[:space:]]*-[[:space:]]*//' | sed 's/^"\(.*\)"$/\1/' | sed "s/^'\(.*\)'$/\1/" -} - -get_nested_list_items() { - local fm="$1" parent="$2" child="$3" - echo "$fm" | awk -v p="^${parent}:" -v c="^[[:space:]]+${child}:" ' - $0 ~ p {in_parent=1; next} - in_parent && $0 ~ c {in_child=1; next} - in_child && /^[[:space:]]{4,}-/{print; next} - in_child && /^[[:space:]]*-/{print; next} - in_child && !/^[[:space:]]/{exit} - in_parent && !/^[[:space:]]/{exit} - ' | sed 's/^[[:space:]]*-[[:space:]]*//' | sed 's/^"\(.*\)"$/\1/' | sed "s/^'\(.*\)'$/\1/" -} - -# Build lookup sets (associative arrays) -declare -A SKILL_SET -declare -A TEMPLATE_SET -declare -A DIAGNOSTIC_SET -declare -A PLAYBOOK_SET - -build_lookups() { - while IFS= read -r f; do - local base - base=$(basename "$f" .md) - SKILL_SET["$base"]=1 - done < <(find "$SKILLS_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*") - - while IFS= read -r f; do - local base - base=$(basename "$f" .md) - TEMPLATE_SET["$base"]=1 - done < <(find "$TEMPLATES_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*") - - while IFS= read -r f; do - local base - base=$(basename "$f" .md) - DIAGNOSTIC_SET["$base"]=1 - done < <(find "$DIAGNOSTICS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*") - - while IFS= read -r f; do - local base - base=$(basename "$f" .md) - PLAYBOOK_SET["$base"]=1 - done < <(find "$PLAYBOOKS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*") -} - -# Check if a skill name exists -skill_exists() { - [[ -n "${SKILL_SET[$1]+_}" ]] -} - -template_exists() { - [[ -n "${TEMPLATE_SET[$1]+_}" ]] -} - -diagnostic_exists() { - [[ -n "${DIAGNOSTIC_SET[$1]+_}" ]] -} - -playbook_exists() { - [[ -n "${PLAYBOOK_SET[$1]+_}" ]] -} - -# Check a reference against a lookup, resolving with/without .md -check_ref() { - local file="$1" ref_type="$2" ref_val="$3" lookup_fn="$4" expected_dir="$5" - TOTAL_REFS=$((TOTAL_REFS + 1)) - local base="${ref_val%.md}" - if $lookup_fn "$base"; then - log_ok "$ref_type" "$ref_val" - else - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "$ref_type" "$ref_val" "$expected_dir/$base.md" - fi -} - -# Check frontmatter list items against a lookup -check_fm_list() { - local file="$1" fm="$2" key="$3" ref_type="$4" lookup_fn="$5" expected_dir="$6" - if field_exists "$fm" "$key"; then - while IFS= read -r item; do - [[ -z "$item" ]] && continue - check_ref "$file" "$ref_type" "$item" "$lookup_fn" "$expected_dir" - done < <(get_list_items "$fm" "$key") - fi -} - -# --------------------------------------------------------------------------- -# Parse arguments -# --------------------------------------------------------------------------- -for arg in "$@"; do - case "$arg" in - --help) usage ;; - --verbose) VERBOSE=1 ;; - *) echo "Unknown option: $arg"; usage ;; - esac -done - -# --------------------------------------------------------------------------- -# Build lookups -# --------------------------------------------------------------------------- -build_lookups - -# --------------------------------------------------------------------------- -# Scan all .md files -# --------------------------------------------------------------------------- -printf "${BOLD}Scanning for broken references...${NC}\n\n" - -ALL_MD_FILES=() -for dir in "$SKILLS_DIR" "$TEMPLATES_DIR" "$DIAGNOSTICS_DIR" "$PLAYBOOKS_DIR" "$HOOKS_DIR"; do - while IFS= read -r f; do - ALL_MD_FILES+=("$f") - done < <(find "$dir" -name "*.md" -not -path "*/_schema/*" | sort) -done - -for file in "${ALL_MD_FILES[@]}"; do - rel_path="${file#"$PROJECT_ROOT/"}" - file_has_broken=0 - - # Skip non-content files - head -1 "$file" | grep -q "^---$" || continue - - fm=$(extract_frontmatter "$file") - printed_header=0 - - print_header() { - if [[ $printed_header -eq 0 ]]; then - printf "${BOLD}%s${NC}\n" "$rel_path" - printed_header=1 - fi - } - - # ----------------------------------------------------------------------- - # 1. Markdown links: [Name](path.md) — resolve relative to file - # ----------------------------------------------------------------------- - body=$(awk 'BEGIN{fm=0} /^---$/{fm++; next} fm>=2{print}' "$file") - while IFS= read -r link_match; do - [[ -z "$link_match" ]] && continue - # Extract the path from the markdown link - link_path=$(echo "$link_match" | sed 's/.*](\([^)]*\)).*/\1/') - # Skip external URLs, anchors, and empty links - [[ "$link_path" == http* ]] && continue - [[ "$link_path" == \#* ]] && continue - [[ -z "$link_path" ]] && continue - # Strip any anchor - link_path="${link_path%%#*}" - [[ -z "$link_path" ]] && continue - # Resolve relative path - file_dir=$(dirname "$file") - resolved="$file_dir/$link_path" - TOTAL_REFS=$((TOTAL_REFS + 1)) - if [[ -f "$resolved" ]]; then - log_ok "markdown-link" "$link_path" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "markdown-link" "$link_path" "$resolved" - fi - done < <(echo "$body" | grep -oE '\[[^]]*\]\([^)]+\)' || true) - - # ----------------------------------------------------------------------- - # 2. Frontmatter arrays — skill references - # ----------------------------------------------------------------------- - for key in related_skills applicable_skills routes_to_skills; do - if field_exists "$fm" "$key"; then - print_header_done=0 - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if skill_exists "$local_base"; then - log_ok "$key" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "$key" "$item" ".claude/.claude/skills/*/$local_base.md" - fi - done < <(get_list_items "$fm" "$key") - fi - done - - # ----------------------------------------------------------------------- - # 3. Frontmatter arrays — template references - # ----------------------------------------------------------------------- - for key in routes_to_templates final_outputs; do - if field_exists "$fm" "$key"; then - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if template_exists "$local_base"; then - log_ok "$key" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "$key" "$item" ".claude/.claude/output-templates/*/$local_base.md" - fi - done < <(get_list_items "$fm" "$key") - fi - done - - # ----------------------------------------------------------------------- - # 4. Frontmatter arrays — diagnostic references - # ----------------------------------------------------------------------- - if field_exists "$fm" "trigger_diagnostics"; then - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if diagnostic_exists "$local_base"; then - log_ok "trigger_diagnostics" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "trigger_diagnostics" "$item" ".claude/.claude/diagnostics/$local_base.md" - fi - done < <(get_list_items "$fm" "trigger_diagnostics") - fi - - # ----------------------------------------------------------------------- - # 5. Nested routes_to (hooks) — diagnostics, skills, playbooks - # ----------------------------------------------------------------------- - if field_exists "$fm" "routes_to"; then - # diagnostics - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if diagnostic_exists "$local_base"; then - log_ok "routes_to.diagnostics" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "routes_to.diagnostics" "$item" ".claude/.claude/diagnostics/$local_base.md" - fi - done < <(get_nested_list_items "$fm" "routes_to" "diagnostics") - - # skills - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if skill_exists "$local_base"; then - log_ok "routes_to.skills" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "routes_to.skills" "$item" ".claude/.claude/skills/*/$local_base.md" - fi - done < <(get_nested_list_items "$fm" "routes_to" "skills") - - # playbooks - while IFS= read -r item; do - [[ -z "$item" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - local_base="${item%.md}" - if playbook_exists "$local_base"; then - log_ok "routes_to.playbooks" "$item" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "routes_to.playbooks" "$item" ".claude/.claude/playbooks/$local_base.md" - fi - done < <(get_nested_list_items "$fm" "routes_to" "playbooks") - fi - - # ----------------------------------------------------------------------- - # 6. Playbook steps — skill references - # ----------------------------------------------------------------------- - if field_exists "$fm" "steps"; then - while IFS= read -r skill_line; do - skill_ref=$(echo "$skill_line" | sed 's/^[[:space:]]*skill:[[:space:]]*//' | sed 's/^"\(.*\)"$/\1/' | sed "s/^'\(.*\)'$/\1/") - [[ -z "$skill_ref" ]] && continue - TOTAL_REFS=$((TOTAL_REFS + 1)) - if skill_exists "$skill_ref"; then - log_ok "steps.skill" "$skill_ref" - else - print_header - BROKEN_REFS=$((BROKEN_REFS + 1)) - log_broken "$file" "steps.skill" "$skill_ref" ".claude/.claude/skills/*/$skill_ref.md" - fi - done < <(echo "$fm" | grep -E '^[[:space:]]+skill:' | sed 's/^[[:space:]]*//') - fi - -done - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}===========================================================${NC}\n" -printf "${BOLD} Broken References Summary${NC}\n" -printf "${BOLD}===========================================================${NC}\n" -printf " Total references checked: %d\n" "$TOTAL_REFS" -if [[ $BROKEN_REFS -gt 0 ]]; then - printf " ${RED}Broken references: %d${NC}\n" "$BROKEN_REFS" -else - printf " ${GREEN}Broken references: %d${NC}\n" "$BROKEN_REFS" -fi -printf "${BOLD}===========================================================${NC}\n" - -if [[ $BROKEN_REFS -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --refs-only "$@" diff --git a/scripts/build-codex.sh b/scripts/build-codex.sh index a7e795f..57059e4 100755 --- a/scripts/build-codex.sh +++ b/scripts/build-codex.sh @@ -1,146 +1,4 @@ -#!/usr/bin/env bash -# ───────────────────────────────────────────── -# build-codex.sh -# Transforms .claude/skills/ into Codex-compatible skills/ directory -# Source: .claude/skills/{category}/{skill-name}.md -# Target: skills/{skill-name}/SKILL.md -# -# Codex expects: skills/{skill-name}/SKILL.md -# Foreman has: .claude/skills/{category}/{skill-name}.md -# -# This script bridges the two formats without modifying source files. -# Run after any skill changes, or in CI before publishing. -# -# Usage: ./scripts/build-codex.sh [--clean] [--verbose] [--dry-run] -# Author: Fatih Guner -# ───────────────────────────────────────────── - -set -euo pipefail - -# ─── Configuration ─── -SOURCE_DIR=".claude/skills" -TARGET_DIR="skills" -SCHEMA_DIR="_schema" - -# ─── Flags ─── -CLEAN=false -VERBOSE=false -DRY_RUN=false - -for arg in "$@"; do - case "$arg" in - --clean) CLEAN=true ;; - --verbose) VERBOSE=true ;; - --dry-run) DRY_RUN=true ;; - --help|-h) - echo "Usage: ./scripts/build-codex.sh [--clean] [--verbose] [--dry-run]" - echo "" - echo "Transforms .claude/skills/ into Codex-compatible skills/ directory." - echo "" - echo "Options:" - echo " --clean Remove existing skills/ before building" - echo " --verbose Show each file being processed" - echo " --dry-run Show what would be done without writing files" - echo " --help Show this help message" - exit 0 - ;; - esac -done - -# ─── Colors ─── -GREEN='\033[0;32m' -YELLOW='\033[0;33m' -BLUE='\033[0;34m' -NC='\033[0m' - -# ─── Validation ─── -if [ ! -d "$SOURCE_DIR" ]; then - echo "Error: Source directory '$SOURCE_DIR' not found." - echo "Run this script from the Foreman project root." - exit 1 -fi - -# ─── Clean ─── -if [ "$CLEAN" = true ]; then - if [ "$DRY_RUN" = true ]; then - echo -e "${YELLOW}[DRY-RUN]${NC} Would remove $TARGET_DIR/" - else - rm -rf "$TARGET_DIR" - echo -e "${YELLOW}Cleaned${NC} $TARGET_DIR/" - fi -fi - -# ─── Build ─── -total=0 -skipped=0 -created=0 -updated=0 - -for source_file in "$SOURCE_DIR"/*/*.md; do - # Skip schema files - dir_name=$(basename "$(dirname "$source_file")") - [ "$dir_name" = "$SCHEMA_DIR" ] && continue - - # Extract skill name from filename (without .md) - skill_name=$(basename "$source_file" .md) - target_dir="$TARGET_DIR/$skill_name" - target_file="$target_dir/SKILL.md" - - total=$((total + 1)) - - # Check if target needs updating - if [ -f "$target_file" ]; then - # Compare checksums — skip if identical - if command -v md5sum &>/dev/null; then - source_hash=$(md5sum "$source_file" | cut -d' ' -f1) - target_hash=$(md5sum "$target_file" | cut -d' ' -f1) - else - source_hash=$(md5 -q "$source_file") - target_hash=$(md5 -q "$target_file") - fi - if [ "$source_hash" = "$target_hash" ]; then - skipped=$((skipped + 1)) - [ "$VERBOSE" = true ] && echo -e " ${BLUE}skip${NC} $skill_name (unchanged)" - continue - fi - updated=$((updated + 1)) - action="update" - else - created=$((created + 1)) - action="create" - fi - - if [ "$DRY_RUN" = true ]; then - echo -e " ${YELLOW}[DRY-RUN]${NC} Would $action $target_file" - else - mkdir -p "$target_dir" - cp "$source_file" "$target_file" - [ "$VERBOSE" = true ] && echo -e " ${GREEN}$action${NC} $skill_name" - fi -done - -# ─── Summary ─── -echo "" -echo -e "${GREEN}Codex build complete${NC}" -echo " Source: $SOURCE_DIR/" -echo " Target: $TARGET_DIR/" -echo " Total: $total skills" -echo " Created: $created" -echo " Updated: $updated" -echo " Skipped: $skipped (unchanged)" - -if [ "$DRY_RUN" = true ]; then - echo "" - echo -e "${YELLOW}This was a dry run. No files were written.${NC}" -fi - -# ─── Add to .gitignore if not present ─── -if ! grep -q "^skills/$" .gitignore 2>/dev/null; then - if [ "$DRY_RUN" = false ]; then - echo "" >> .gitignore - echo "# Codex-generated skills directory (built from .claude/skills/)" >> .gitignore - echo "skills/" >> .gitignore - echo "" - echo -e "${YELLOW}Added${NC} skills/ to .gitignore (generated directory)" - fi -fi +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" build-codex "$@" diff --git a/scripts/build-plugins.mjs b/scripts/build-plugins.mjs new file mode 100755 index 0000000..80cf589 --- /dev/null +++ b/scripts/build-plugins.mjs @@ -0,0 +1,6 @@ +#!/usr/bin/env node +import path from 'node:path'; +import { buildPlugins } from '../lib/distribution.js'; +const root = path.resolve(import.meta.dirname, '..'); +try { console.log(JSON.stringify(buildPlugins(root))); } +catch (e) { console.error(e.message); process.exitCode = 1; } diff --git a/scripts/bump-version.sh b/scripts/bump-version.sh index 7abf377..a893e98 100755 --- a/scripts/bump-version.sh +++ b/scripts/bump-version.sh @@ -1,130 +1,4 @@ -#!/usr/bin/env bash -# -# bump-version.sh — Batch version bump for skill files. -# -# Usage: -# ./scripts/bump-version.sh --file .claude/.claude/skills/frameworks/porters-five-forces.md --to 2.0.0 -# ./scripts/bump-version.sh --category frameworks --to 1.2.0 -# ./scripts/bump-version.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Defaults ────────────────────────────────────────────────────────── -FILE="" -CATEGORY="" -VERSION="" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -bump-version.sh — Batch version bump for skill files. - -USAGE - ./scripts/bump-version.sh --file PATH --to VERSION - ./scripts/bump-version.sh --category SLUG --to VERSION - ./scripts/bump-version.sh --help - -OPTIONS - --file PATH Single file to bump (relative or absolute path) - --category SLUG Bump all files in a skill category (e.g., "frameworks") - --to VERSION Target version in semver format (e.g., "1.2.0") - --help Show this help message - -EXAMPLES - ./scripts/bump-version.sh --file .claude/.claude/skills/frameworks/porters-five-forces.md --to 2.0.0 - ./scripts/bump-version.sh --category frameworks --to 1.2.0 - ./scripts/bump-version.sh --category leadership --to 1.1.0 -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_semver() { - local ver="$1" - if [[ ! "$ver" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then - die "Version must be in semver format (e.g., 1.2.0): '$ver'" - fi -} - -bump_file() { - local file="$1" - local new_version="$2" - - if [[ ! -f "$file" ]]; then - echo " SKIP $file (not found)" - return - fi - - # Extract current version - local current - current=$(grep '^version:' "$file" 2>/dev/null | head -1 | sed 's/^version: *"\{0,1\}\([^"]*\)"\{0,1\}/\1/' || echo "unknown") - - if [[ "$current" == "$new_version" ]]; then - echo " SKIP $(basename "$file") ($current -> $new_version, already at target)" - return - fi - - # Replace version in frontmatter - sed -i '' "s/^version: .*/version: \"${new_version}\"/" "$file" - - echo " BUMP $(basename "$file") ($current -> $new_version)" -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --file) FILE="$2"; shift 2 ;; - --category) CATEGORY="$2"; shift 2 ;; - --to) VERSION="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Validate ────────────────────────────────────────────────────────── -[[ -z "$VERSION" ]] && die "--to VERSION is required." -validate_semver "$VERSION" -[[ -z "$FILE" && -z "$CATEGORY" ]] && die "Provide --file or --category." -[[ -n "$FILE" && -n "$CATEGORY" ]] && die "Use either --file or --category, not both." - -# ── Execute ─────────────────────────────────────────────────────────── -echo "" -echo " VERSION BUMP -> $VERSION" -echo " $(printf '%56s' '' | tr ' ' '-')" -echo "" - -bumped=0 - -if [[ -n "$FILE" ]]; then - # Resolve path relative to project root if needed - if [[ "$FILE" != /* ]]; then - FILE="$PROJECT_ROOT/$FILE" - fi - bump_file "$FILE" "$VERSION" - bumped=1 -fi - -if [[ -n "$CATEGORY" ]]; then - target_dir="$PROJECT_ROOT/.claude/skills/$CATEGORY" - if [[ ! -d "$target_dir" ]]; then - die "Category directory not found: $target_dir" - fi - - for skill_file in "$target_dir"/*.md; do - [[ ! -f "$skill_file" ]] && continue - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - bump_file "$skill_file" "$VERSION" - bumped=$((bumped + 1)) - done -fi - -echo "" -echo " Processed $bumped file(s)." -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" bump-version "$@" diff --git a/scripts/check-release.mjs b/scripts/check-release.mjs new file mode 100644 index 0000000..2ff3b24 --- /dev/null +++ b/scripts/check-release.mjs @@ -0,0 +1,26 @@ +#!/usr/bin/env node +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import path from 'node:path'; + +const root = path.resolve(import.meta.dirname, '..'); +const json = file => JSON.parse(fs.readFileSync(path.join(root, file), 'utf8')); +const pkg = json('package.json'); +const args = process.argv.slice(2); +assert.ok(args.length === 0 || (args.length === 2 && args[0] === '--tag'), 'Usage: check-release.mjs [--tag vVERSION]'); +assert.match(pkg.version, /^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?$/); +if (args.length) assert.equal(args[1], `v${pkg.version}`, 'Release tag must match package version'); +for (const file of ['.claude-plugin/plugin.json', '.codex-plugin/plugin.json', 'plugins/foreman/.claude-plugin/plugin.json', 'openclaw.plugin.json', 'package-lock.json']) { + assert.equal(json(file).version, pkg.version, `Version mismatch: ${file}`); +} +assert.equal(json('package-lock.json').packages[''].version, pkg.version); +const marketplace = json('.claude-plugin/marketplace.json'); +assert.equal(marketplace.metadata.version, pkg.version); +assert.equal(marketplace.plugins.find(p => p.name === 'foreman').version, pkg.version); +assert.equal(pkg.publishConfig.access, 'public'); +assert.equal(pkg.publishConfig.tag, pkg.version.includes('-') ? 'next' : 'latest', 'Prereleases must use next; stable releases must use latest'); +for (const file of [pkg.bin['foreman-sh'], ...pkg.openclaw.extensions, '.claude/RUNTIME.md', 'plugins/foreman/skills/foreman/SKILL.md', 'LICENSE']) { + assert.ok(fs.statSync(path.join(root, file)).isFile(), `Missing release file: ${file}`); +} +assert.ok(fs.readFileSync(path.join(root, 'CHANGELOG.md'), 'utf8').includes(`## [${pkg.version}]`), 'Missing changelog entry'); +console.log(`Release metadata verified: foreman-sh@${pkg.version} (${pkg.publishConfig.tag})`); diff --git a/scripts/coverage-report.sh b/scripts/coverage-report.sh index 9b72253..36cff83 100755 --- a/scripts/coverage-report.sh +++ b/scripts/coverage-report.sh @@ -1,307 +1,4 @@ -#!/usr/bin/env bash -# -# coverage-report.sh — Analyze coverage across all Foreman dimensions. -# -# Usage: -# ./scripts/coverage-report.sh -# ./scripts/coverage-report.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -coverage-report.sh — Analyze coverage across all Foreman dimensions. - -USAGE - ./scripts/coverage-report.sh Generate full coverage report - ./scripts/coverage-report.sh --help Show this help message - -DIMENSIONS - - Stage coverage: skills per stage - - Category size distribution - - Most/least cross-referenced skills (top 10, bottom 10) - - Diagnostic -> skill routing coverage - - Playbook -> skill usage - - Template -> skill mapping -EOF - exit 0 -} - -[[ "${1:-}" == "--help" || "${1:-}" == "-h" ]] && usage - -# ── Header ──────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN COVERAGE REPORT" -echo " $(printf '%60s' '' | tr ' ' '=')" -echo "" - -# ── 1. Stage Coverage ──────────────────────────────────────────────── -echo " 1. STAGE COVERAGE" -echo " $(printf '%60s' '' | tr ' ' '-')" -echo "" - -total_skills=0 -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - total_skills=$((total_skills + 1)) -done - -for stage in idea validation early-traction growth scale; do - count=0 - for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - if grep -q " - $stage" "$skill_file" 2>/dev/null; then - count=$((count + 1)) - fi - done - if [[ $total_skills -gt 0 ]]; then - pct=$((count * 100 / total_skills)) - else - pct=0 - fi - bar="" - bar_len=$((pct / 2)) - for ((i=0; i Skill Routing Coverage ────────────────────────── -echo " 4. DIAGNOSTIC -> SKILL ROUTING COVERAGE" -echo " $(printf '%60s' '' | tr ' ' '-')" -echo "" - -# Collect all skills reachable through diagnostics -declare -A diag_reachable -for diag_file in "$PROJECT_ROOT"/.claude/diagnostics/*.md; do - [[ ! -f "$diag_file" ]] && continue - in_routes=false - while IFS= read -r line; do - if [[ "$line" == "routes_to_skills:" ]]; then - in_routes=true - continue - fi - if [[ "$in_routes" == true ]]; then - if [[ "$line" =~ ^[[:space:]]*-[[:space:]]+(.*) ]]; then - skill_ref="${BASH_REMATCH[1]}" - skill_ref="${skill_ref//\"/}" - skill_ref="$(echo "$skill_ref" | xargs)" - diag_reachable["$skill_ref"]=1 - else - in_routes=false - fi - fi - done < "$diag_file" -done - -reachable_count="${#diag_reachable[@]}" -if [[ $total_skills -gt 0 ]]; then - pct=$((reachable_count * 100 / total_skills)) -else - pct=0 -fi -printf " Skills reachable via diagnostics: %d/%d (%d%%)\n" "$reachable_count" "$total_skills" "$pct" - -# List unreachable skills (up to 15) -unreachable=() -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - skill_name="$(basename "$skill_file" .md)" - if [[ -z "${diag_reachable[$skill_name]+x}" ]]; then - unreachable+=("$skill_name") - fi -done - -if [[ ${#unreachable[@]} -gt 0 ]]; then - echo "" - echo " Not reachable via any diagnostic (first 15):" - shown=0 - for s in "${unreachable[@]}"; do - [[ $shown -ge 15 ]] && break - echo " - $s" - ((shown++)) - done - remaining=$((${#unreachable[@]} - shown)) - [[ $remaining -gt 0 ]] && echo " ... and $remaining more" -fi -echo "" - -# ── 5. Playbook -> Skill Usage ─────────────────────────────────────── -echo " 5. PLAYBOOK -> SKILL USAGE" -echo " $(printf '%60s' '' | tr ' ' '-')" -echo "" - -declare -A playbook_reachable -for pb_file in "$PROJECT_ROOT"/.claude/playbooks/*.md; do - [[ ! -f "$pb_file" ]] && continue - # Look for skill references in steps - while IFS= read -r line; do - if [[ "$line" =~ skill:[[:space:]]*\"?([a-z0-9-]+)\"? ]]; then - playbook_reachable["${BASH_REMATCH[1]}"]=1 - fi - done < "$pb_file" - # Also look for backtick-quoted skill names in routing sections - while IFS= read -r line; do - if [[ "$line" =~ \`([a-z0-9]+-[a-z0-9-]+)\` ]]; then - playbook_reachable["${BASH_REMATCH[1]}"]=1 - fi - done < "$pb_file" -done - -pb_reachable_count="${#playbook_reachable[@]}" -if [[ $total_skills -gt 0 ]]; then - pct=$((pb_reachable_count * 100 / total_skills)) -else - pct=0 -fi -printf " Skills used in playbooks: %d/%d (%d%%)\n" "$pb_reachable_count" "$total_skills" "$pct" -echo "" - -# ── 6. Template -> Skill Mapping ───────────────────────────────────── -echo " 6. TEMPLATE -> SKILL MAPPING" -echo " $(printf '%60s' '' | tr ' ' '-')" -echo "" - -declare -A tmpl_skills -for tmpl_file in "$PROJECT_ROOT"/.claude/output-templates/*/*.md; do - [[ "$(basename "$tmpl_file")" == "output-template.md" ]] && continue - [[ ! -f "$tmpl_file" ]] && continue - in_skills=false - while IFS= read -r line; do - if [[ "$line" == "applicable_skills:" ]]; then - in_skills=true - continue - fi - if [[ "$in_skills" == true ]]; then - if [[ "$line" =~ ^[[:space:]]*-[[:space:]]+(.*) ]]; then - skill_ref="${BASH_REMATCH[1]}" - skill_ref="${skill_ref//\"/}" - skill_ref="$(echo "$skill_ref" | xargs)" - tmpl_skills["$skill_ref"]=1 - else - in_skills=false - fi - fi - done < "$tmpl_file" -done - -tmpl_coverage="${#tmpl_skills[@]}" -if [[ $total_skills -gt 0 ]]; then - pct=$((tmpl_coverage * 100 / total_skills)) -else - pct=0 -fi -printf " Skills with template coverage: %d/%d (%d%%)\n" "$tmpl_coverage" "$total_skills" "$pct" - -# Skills without any template coverage (first 15) -no_tmpl=() -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - skill_name="$(basename "$skill_file" .md)" - if [[ -z "${tmpl_skills[$skill_name]+x}" ]]; then - no_tmpl+=("$skill_name") - fi -done - -if [[ ${#no_tmpl[@]} -gt 0 ]]; then - echo "" - echo " No template coverage (first 15):" - shown=0 - for s in "${no_tmpl[@]}"; do - [[ $shown -ge 15 ]] && break - echo " - $s" - ((shown++)) - done - remaining=$((${#no_tmpl[@]} - shown)) - [[ $remaining -gt 0 ]] && echo " ... and $remaining more" -fi -echo "" - -echo " $(printf '%60s' '' | tr ' ' '=')" -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" coverage-report "$@" diff --git a/scripts/live-eval.mjs b/scripts/live-eval.mjs new file mode 100644 index 0000000..3d172db --- /dev/null +++ b/scripts/live-eval.mjs @@ -0,0 +1,45 @@ +#!/usr/bin/env node +// Explicit, opt-in model evaluation. Never invoked by npm test or CI. +import fs from 'node:fs'; +import path from 'node:path'; +import { spawnSync } from 'node:child_process'; +const root=path.resolve(import.meta.dirname,'..'); +try { + const args=process.argv.slice(2),opts={}; + if(args.includes('--help')) {console.log('Usage: node scripts/live-eval.mjs --output DIR --total-cap-usd N [--prior-cost-usd N] [--case-cap-usd 0.5] [--model MODEL]\nSends the eight fictional scenarios and Foreman content to Claude. Uses a fresh workspace for each scenario. Existing output directories are refused.');process.exit(0);} + for(let i=0;icap)throw new Error('Insufficient remaining budget for one case plus the safety reserve'); + const output=path.resolve(opts.output);if(fs.existsSync(output))throw new Error('Output directory already exists; refusing to repeat a paid run'); + fs.mkdirSync(output,{recursive:true}); + const settings=path.join(output,'settings.json');fs.writeFileSync(settings,JSON.stringify({disableAllHooks:true,autoMemoryEnabled:false,enabledPlugins:{}})); + const cases=JSON.parse(fs.readFileSync(path.join(root,'tests/advisory-scenarios.json'),'utf8')).filter(c=>c.prompt); + let spent=prior;const runs=[]; + for(const scenario of cases) { + if(spent+caseCap+reserve>cap)throw new Error('Aggregate budget reserve reached; remaining scenarios were not started'); + const workspace=path.join(output,'workspaces',scenario.id);fs.mkdirSync(workspace,{recursive:true}); + fs.cpSync(path.join(root,'.claude'),path.join(workspace,'.claude'),{recursive:true}); + fs.copyFileSync(path.join(root,'CLAUDE.md'),path.join(workspace,'CLAUDE.md')); + const prompt='Bu kurgusal Foreman testinde yalnızca bu çalışma alanındaki Foreman içeriklerini kullan. Web, dış dosya, iletişim veya dosya yazma yok. En çok 180 kelime Türkçe yanıt ver; bilinmeyen veri veya yanıt uydurma. Sonda gerçekten kullandığın Foreman dosyalarını belirt. Kurucu: '+scenario.prompt; + fs.writeFileSync(path.join(output,scenario.id+'.prompt.txt'),prompt); + const cli=['--print','--no-session-persistence','--output-format','stream-json','--verbose','--setting-sources','project,local','--settings',settings,'--strict-mcp-config','--mcp-config','{"mcpServers":{}}','--no-chrome','--tools','Read,Glob,Grep,Skill','--allowedTools','Read,Glob,Grep,Skill','--permission-mode','dontAsk','--max-budget-usd',String(caseCap)]; + if(opts.model)cli.push('--model',opts.model); + cli.push(prompt);console.log(JSON.stringify({start:scenario.id,spentUsd:spent,caseCapUsd:caseCap})); + const started=Date.now(),result=spawnSync('claude',cli,{cwd:workspace,encoding:'utf8',timeout:240000,maxBuffer:32*1024*1024}); + const raw=(result.stdout||'')+(result.stderr||'');fs.writeFileSync(path.join(output,scenario.id+'.jsonl'),raw); + const events=raw.split('\n').flatMap(line=>{try{return [JSON.parse(line)];}catch{return [];}}); + const final=events.findLast(e=>e.type==='result')||{},cost=final.total_cost_usd; + if(typeof cost==='number')spent+=cost; + const row={id:scenario.id,exit:result.status,subtype:final.subtype,costUsd:cost??null,seconds:(Date.now()-started)/1000,result:final.result||'',modelUsage:final.modelUsage||{},permissionDenials:final.permission_denials||[],calls:events.filter(e=>e.type==='assistant').flatMap(e=>e.message?.content||[]).filter(b=>b.type==='tool_use')}; + runs.push(row);fs.writeFileSync(path.join(output,scenario.id+'.response.md'),row.result); + fs.writeFileSync(path.join(output,'runs.json'),JSON.stringify({priorCostUsd:prior,totalCostUsd:spent,capUsd:cap,modelRequested:opts.model||'host default',isolatedWorkspaces:true,runs},null,2)); + console.log(JSON.stringify({finished:scenario.id,subtype:row.subtype,costUsd:cost,totalCostUsd:spent})); + if(cost===undefined||result.error||result.status!==0)throw new Error('Uncertain cost, timeout, or process failure; no further calls started'); + } +}catch(e){console.error(e.message);process.exitCode=1;} diff --git a/scripts/maintain.mjs b/scripts/maintain.mjs new file mode 100644 index 0000000..e62b7be --- /dev/null +++ b/scripts/maintain.mjs @@ -0,0 +1,49 @@ +#!/usr/bin/env node +import path from 'node:path'; +import fs from 'node:fs'; +import { execFileSync } from 'node:child_process'; +import { createContent,renameCategory,bumpVersion,anonymize,statistics,updateSummary,checkIndex,atomicWrite } from '../lib/maintenance.js'; +import { buildPlugins } from '../lib/distribution.js'; +const [command,...args]=process.argv.slice(2); +const help={ + 'new-skill':'--name NAME --category CATEGORY [--complexity basic|intermediate|advanced] [--stage idea,validation] [--author TEXT]', + 'new-template':'--name NAME --audience investor|board|team|self|client [--format report] [--author TEXT]', + 'new-diagnostic':'--name NAME [--symptom TEXT ...] [--author TEXT]', + 'new-playbook':'--name NAME [--complexity intermediate] [--stage validation,growth] [--author TEXT]', + 'new-hook':'--name NAME [--priority high|medium|low] [--author TEXT]', + 'rename-category':'--from OLD --to NEW [--confirm]', 'bump-version':'--file PATH | --category CATEGORY --to VERSION', + 'anonymize-author':'--name TEXT [--in DIR] [--apply]', 'build-codex':'[--clean] [--verbose] [--dry-run]', + 'stats':'','coverage-report':'','orphan-check':'','update-claude-md':'','pre-commit-hook':'', + 'setup':'[--install-hook]', 'openclaw-build':'', +}; +try { + if(!(command in help))throw new Error(`Unknown maintenance command ${command}`); + if(args.includes('--help')||args.includes('-h')) {console.log(`Usage: ${command}.sh ${help[command]} [--root DIR]\nCreators produce drafts that must be completed before publishing.`);process.exit(0);} + const opts={},flags=['confirm','apply','clean','verbose','dry-run','install-hook']; + for(let i=0;im[1])].includes(key))throw new Error(`Unknown argument ${args[i]}`); + if(flags.includes(key)){opts[key]=true;continue;} + if(args[i+1]===undefined)throw new Error(`Missing value for ${args[i]}`); + const value=args[++i];if(key==='symptom')(opts.symptom ||= []).push(value);else opts[key]=value; + } + const root=path.resolve(opts.root || path.join(import.meta.dirname,'..'));let result; + if(command.startsWith('new-'))result=createContent(root,command.slice(4),opts); + else if(command==='rename-category'){result=renameCategory(root,opts.from,opts.to,opts.confirm);if(opts.confirm)buildPlugins(root);} + else if(command==='bump-version')result=bumpVersion(root,opts); + else if(command==='anonymize-author')result=anonymize(root,opts); + else if(command==='update-claude-md')result=updateSummary(root); + else if(command==='pre-commit-hook'){result=checkIndex(root);if(result.errors.length)process.exitCode=1;} + else if(command==='build-codex')result=opts['dry-run']?{preview:statistics(root).counts}:buildPlugins(root); + else if(command==='openclaw-build') { + execFileSync('npm',['run','build'],{cwd:root,stdio:'inherit'});buildPlugins(root); + execFileSync('npm',['run','check'],{cwd:root,stdio:'inherit'});result={built:true}; + } else if(command==='setup') { + buildPlugins(root);result={built:true}; + if(opts['install-hook']) { + const hook=execFileSync('git',['rev-parse','--git-path','hooks/pre-commit'],{cwd:root,encoding:'utf8'}).trim(); + atomicWrite(path.resolve(root,hook),'#!/bin/sh\nexec node "$(git rev-parse --show-toplevel)/scripts/maintain.mjs" pre-commit-hook\n',{create:true});fs.chmodSync(path.resolve(root,hook),0o755);result.hook=hook; + } + } else result=statistics(root); + console.log(JSON.stringify(result,null,2)); +} catch(e){console.error(e.message);process.exitCode=1;} diff --git a/scripts/new-diagnostic.sh b/scripts/new-diagnostic.sh index a3c10b7..f9d67c1 100755 --- a/scripts/new-diagnostic.sh +++ b/scripts/new-diagnostic.sh @@ -1,155 +1,4 @@ -#!/usr/bin/env bash -# -# new-diagnostic.sh — Create a new diagnostic file from the schema template. -# -# Usage: -# ./scripts/new-diagnostic.sh (interactive) -# ./scripts/new-diagnostic.sh --name "my-diagnosis" (non-interactive) -# ./scripts/new-diagnostic.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATE="$PROJECT_ROOT/.claude/diagnostics/_schema/diagnostic-template.md" -TARGET_DIR="$PROJECT_ROOT/diagnostics" - -# ── Defaults ────────────────────────────────────────────────────────── -NAME="" -SYMPTOMS=() -AUTHOR="Fatih Guner" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -new-diagnostic.sh — Create a new diagnostic file from the schema template. - -USAGE - ./scripts/new-diagnostic.sh Interactive mode - ./scripts/new-diagnostic.sh [OPTIONS] Non-interactive mode - -OPTIONS - --name NAME Diagnostic name in kebab-case (e.g., "revenue-diagnosis") - --symptom SYMPTOM Entry symptom (can be repeated: --symptom "X" --symptom "Y") - --author AUTHOR Author name (default: "Fatih Guner") - --help Show this help message - -EXAMPLES - ./scripts/new-diagnostic.sh --name "revenue-diagnosis" - ./scripts/new-diagnostic.sh --name "churn-diagnosis" --symptom "customers are leaving" --symptom "high churn rate" -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Name must be kebab-case (lowercase letters, numbers, hyphens only): '$name'" - fi -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) NAME="$2"; shift 2 ;; - --symptom) SYMPTOMS+=("$2"); shift 2 ;; - --author) AUTHOR="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Interactive Prompts ─────────────────────────────────────────────── -if [[ -z "$NAME" ]]; then - read -rp "Diagnostic name (kebab-case, e.g., 'revenue-diagnosis'): " NAME -fi -validate_kebab_case "$NAME" - -if [[ ${#SYMPTOMS[@]} -eq 0 ]]; then - echo "" - echo "Enter entry symptoms (natural language phrases entrepreneurs might say)." - echo "Press Enter on an empty line when done. Minimum 1 symptom." - while true; do - read -rp " Symptom: " symptom - [[ -z "$symptom" ]] && break - SYMPTOMS+=("$symptom") - done - if [[ ${#SYMPTOMS[@]} -eq 0 ]]; then - die "At least one entry symptom is required." - fi -fi - -# ── Validate Target ────────────────────────────────────────────────── -TARGET_FILE="$TARGET_DIR/$NAME.md" - -if [[ -f "$TARGET_FILE" ]]; then - die "Diagnostic already exists: $TARGET_FILE" -fi - -if [[ ! -f "$TEMPLATE" ]]; then - die "Template not found: $TEMPLATE" -fi - -# ── Build Symptoms YAML ────────────────────────────────────────────── -symptoms_yaml="" -for s in "${SYMPTOMS[@]}"; do - symptoms_yaml+=" - \"${s}\"\n" -done - -# ── Generate File ───────────────────────────────────────────────────── -cp "$TEMPLATE" "$TARGET_FILE" - -# Replace frontmatter placeholders -sed -i '' "s/^name: .*/name: \"${NAME}\"/" "$TARGET_FILE" -sed -i '' "s/^author: .*/author: \"${AUTHOR}\"/" "$TARGET_FILE" - -# Replace entry_symptoms block -if [[ ${#SYMPTOMS[@]} -gt 0 ]]; then - python3 -c " -import re -with open('$TARGET_FILE', 'r') as f: - content = f.read() - -symptoms = $(python3 -c "import json; print(json.dumps([s for s in '''${SYMPTOMS[*]}'''.split(' ')]))" 2>/dev/null || echo '[]') - -# Build replacement -lines = ['entry_symptoms:'] -for s in '''${SYMPTOMS[*]}'''.strip().split(' '): - s = s.strip() - if s: - lines.append(f' - \"{s}\"') - -replacement = '\n'.join(lines) + '\n' -content = re.sub( - r'entry_symptoms:\n(?: - \"[^\"]*\"\n)+', - replacement, - content, - count=1 -) -with open('$TARGET_FILE', 'w') as f: - f.write(content) -" -fi - -# ── Confirm ─────────────────────────────────────────────────────────── -echo "" -echo "Created: $TARGET_FILE" -echo "" -echo " Name: $NAME" -echo " Symptoms: ${#SYMPTOMS[@]} entry symptom(s)" -for s in "${SYMPTOMS[@]}"; do - echo " - $s" -done -echo " Author: $AUTHOR" -echo "" - -# Open in editor if available -if [[ -n "${EDITOR:-}" ]]; then - echo "Opening in \$EDITOR ($EDITOR)..." - "$EDITOR" "$TARGET_FILE" -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" new-diagnostic "$@" diff --git a/scripts/new-hook.sh b/scripts/new-hook.sh index f2c4e0b..51b9e44 100755 --- a/scripts/new-hook.sh +++ b/scripts/new-hook.sh @@ -1,131 +1,4 @@ -#!/usr/bin/env bash -# -# new-hook.sh — Create a new hook file from the schema template. -# -# Usage: -# ./scripts/new-hook.sh (interactive) -# ./scripts/new-hook.sh --name "my-hook" --priority high (non-interactive) -# ./scripts/new-hook.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATE="$PROJECT_ROOT/hooks/_schema/hook-template.md" -TARGET_DIR="$PROJECT_ROOT/hooks" - -# ── Defaults ────────────────────────────────────────────────────────── -NAME="" -PRIORITY="" -AUTHOR="Fatih Guner" - -VALID_PRIORITIES=("high" "medium" "low") - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -new-hook.sh — Create a new hook file from the schema template. - -USAGE - ./scripts/new-hook.sh Interactive mode - ./scripts/new-hook.sh [OPTIONS] Non-interactive mode - -OPTIONS - --name NAME Hook name in kebab-case (e.g., "revenue-hook") - --priority LEVEL high | medium | low - --author AUTHOR Author name (default: "Fatih Guner") - --help Show this help message - -EXAMPLES - ./scripts/new-hook.sh --name "revenue-hook" --priority high - ./scripts/new-hook.sh --name "personal-growth-hook" --priority low -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Name must be kebab-case (lowercase letters, numbers, hyphens only): '$name'" - fi -} - -validate_priority() { - local pri="$1" - for p in "${VALID_PRIORITIES[@]}"; do - [[ "$p" == "$pri" ]] && return 0 - done - die "Unknown priority '$pri'. Valid priorities: ${VALID_PRIORITIES[*]}" -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) NAME="$2"; shift 2 ;; - --priority) PRIORITY="$2"; shift 2 ;; - --author) AUTHOR="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Interactive Prompts ─────────────────────────────────────────────── -if [[ -z "$NAME" ]]; then - read -rp "Hook name (kebab-case, e.g., 'revenue-hook'): " NAME -fi -validate_kebab_case "$NAME" - -if [[ -z "$PRIORITY" ]]; then - echo "" - echo "Priority levels:" - echo " 1) high — Urgent business problems (revenue, churn, fundraising)" - echo " 2) medium — Operational/tactical issues (hiring, processes, tools)" - echo " 3) low — Development/growth topics (learning, personal growth)" - read -rp "Select priority (number or name): " pri_input - case "$pri_input" in - 1) PRIORITY="high" ;; - 2) PRIORITY="medium" ;; - 3) PRIORITY="low" ;; - *) PRIORITY="$pri_input" ;; - esac -fi -validate_priority "$PRIORITY" - -# ── Validate Target ────────────────────────────────────────────────── -TARGET_FILE="$TARGET_DIR/$NAME.md" - -if [[ -f "$TARGET_FILE" ]]; then - die "Hook already exists: $TARGET_FILE" -fi - -if [[ ! -f "$TEMPLATE" ]]; then - die "Template not found: $TEMPLATE" -fi - -# ── Generate File ───────────────────────────────────────────────────── -cp "$TEMPLATE" "$TARGET_FILE" - -# Replace frontmatter placeholders -sed -i '' "s/^name: .*/name: \"${NAME}\"/" "$TARGET_FILE" -sed -i '' "s/^priority: .*/priority: \"${PRIORITY}\"/" "$TARGET_FILE" -sed -i '' "s/^author: .*/author: \"${AUTHOR}\"/" "$TARGET_FILE" - -# ── Confirm ─────────────────────────────────────────────────────────── -echo "" -echo "Created: $TARGET_FILE" -echo "" -echo " Name: $NAME" -echo " Priority: $PRIORITY" -echo " Author: $AUTHOR" -echo "" - -# Open in editor if available -if [[ -n "${EDITOR:-}" ]]; then - echo "Opening in \$EDITOR ($EDITOR)..." - "$EDITOR" "$TARGET_FILE" -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" new-hook "$@" diff --git a/scripts/new-playbook.sh b/scripts/new-playbook.sh index a3a4f97..cd4dbe8 100755 --- a/scripts/new-playbook.sh +++ b/scripts/new-playbook.sh @@ -1,179 +1,4 @@ -#!/usr/bin/env bash -# -# new-playbook.sh — Create a new playbook file from the schema template. -# -# Usage: -# ./scripts/new-playbook.sh (interactive) -# ./scripts/new-playbook.sh --name "my-playbook" --complexity basic (non-interactive) -# ./scripts/new-playbook.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATE="$PROJECT_ROOT/.claude/playbooks/_schema/playbook-template.md" -TARGET_DIR="$PROJECT_ROOT/playbooks" - -# ── Defaults ────────────────────────────────────────────────────────── -NAME="" -COMPLEXITY="" -STAGES=() -AUTHOR="Fatih Guner" - -VALID_STAGES=("idea" "validation" "early-traction" "growth" "scale") - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -new-playbook.sh — Create a new playbook file from the schema template. - -USAGE - ./scripts/new-playbook.sh Interactive mode - ./scripts/new-playbook.sh [OPTIONS] Non-interactive mode - -OPTIONS - --name NAME Playbook name in kebab-case (e.g., "pivot-playbook") - --complexity LEVEL basic | intermediate | advanced - --stage STAGES Comma-separated stages: idea,validation,early-traction,growth,scale - --author AUTHOR Author name (default: "Fatih Guner") - --help Show this help message - -EXAMPLES - ./scripts/new-playbook.sh --name "pivot-playbook" --complexity intermediate - ./scripts/new-playbook.sh --name "launch-playbook" --complexity basic --stage "validation,early-traction" -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Name must be kebab-case (lowercase letters, numbers, hyphens only): '$name'" - fi -} - -validate_complexity() { - local level="$1" - case "$level" in - basic|intermediate|advanced) return 0 ;; - *) die "Complexity must be one of: basic, intermediate, advanced" ;; - esac -} - -validate_stage() { - local stage="$1" - for s in "${VALID_STAGES[@]}"; do - [[ "$s" == "$stage" ]] && return 0 - done - die "Unknown stage '$stage'. Valid stages: ${VALID_STAGES[*]}" -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) NAME="$2"; shift 2 ;; - --complexity) COMPLEXITY="$2"; shift 2 ;; - --stage) IFS=',' read -ra STAGES <<< "$2"; shift 2 ;; - --author) AUTHOR="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Interactive Prompts ─────────────────────────────────────────────── -if [[ -z "$NAME" ]]; then - read -rp "Playbook name (kebab-case, e.g., 'pivot-playbook'): " NAME -fi -validate_kebab_case "$NAME" - -if [[ -z "$COMPLEXITY" ]]; then - echo "" - echo "Complexity levels:" - echo " 1) basic" - echo " 2) intermediate" - echo " 3) advanced" - read -rp "Select complexity (number or name): " comp_input - case "$comp_input" in - 1) COMPLEXITY="basic" ;; - 2) COMPLEXITY="intermediate" ;; - 3) COMPLEXITY="advanced" ;; - *) COMPLEXITY="$comp_input" ;; - esac -fi -validate_complexity "$COMPLEXITY" - -if [[ ${#STAGES[@]} -eq 0 ]]; then - echo "" - echo "Stages (select all that apply, comma-separated):" - echo " idea, validation, early-traction, growth, scale" - read -rp "Stages [validation,early-traction]: " stage_input - if [[ -z "$stage_input" ]]; then - STAGES=("validation" "early-traction") - else - IFS=',' read -ra STAGES <<< "$stage_input" - fi -fi - -for s in "${STAGES[@]}"; do - s="$(echo "$s" | xargs)" - validate_stage "$s" -done - -# ── Validate Target ────────────────────────────────────────────────── -TARGET_FILE="$TARGET_DIR/$NAME.md" - -if [[ -f "$TARGET_FILE" ]]; then - die "Playbook already exists: $TARGET_FILE" -fi - -if [[ ! -f "$TEMPLATE" ]]; then - die "Template not found: $TEMPLATE" -fi - -# ── Generate File ───────────────────────────────────────────────────── -cp "$TEMPLATE" "$TARGET_FILE" - -# Replace frontmatter placeholders -sed -i '' "s/^name: .*/name: \"${NAME}\"/" "$TARGET_FILE" -sed -i '' "s/^complexity: .*/complexity: \"${COMPLEXITY}\"/" "$TARGET_FILE" -sed -i '' "s/^author: .*/author: \"${AUTHOR}\"/" "$TARGET_FILE" - -# Replace stage block -python3 -c " -import re -with open('$TARGET_FILE', 'r') as f: - content = f.read() - -stages = [s.strip() for s in '${STAGES[*]}'.split()] -stage_yaml = 'stage:\n' + ''.join(f' - {s}\n' for s in stages) - -content = re.sub( - r'stage:\n(?: - [\w-]+\n)+', - stage_yaml, - content, - count=1 -) -with open('$TARGET_FILE', 'w') as f: - f.write(content) -" - -# ── Confirm ─────────────────────────────────────────────────────────── -echo "" -echo "Created: $TARGET_FILE" -echo "" -echo " Name: $NAME" -echo " Complexity: $COMPLEXITY" -echo " Stages: ${STAGES[*]}" -echo " Author: $AUTHOR" -echo "" - -# Open in editor if available -if [[ -n "${EDITOR:-}" ]]; then - echo "Opening in \$EDITOR ($EDITOR)..." - "$EDITOR" "$TARGET_FILE" -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" new-playbook "$@" diff --git a/scripts/new-skill.sh b/scripts/new-skill.sh index 00e645e..2432adf 100755 --- a/scripts/new-skill.sh +++ b/scripts/new-skill.sh @@ -1,241 +1,4 @@ -#!/usr/bin/env bash -# -# new-skill.sh — Create a new skill file from the schema template. -# -# Usage: -# ./scripts/new-skill.sh (interactive) -# ./scripts/new-skill.sh --name "my-skill" --category frameworks (non-interactive) -# ./scripts/new-skill.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATE="$PROJECT_ROOT/.claude/skills/_schema/skill-template.md" - -# ── Defaults ────────────────────────────────────────────────────────── -NAME="" -CATEGORY="" -COMPLEXITY="" -STAGES=() -AUTHOR="Fatih Guner" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -new-skill.sh — Create a new skill file from the schema template. - -USAGE - ./scripts/new-skill.sh Interactive mode - ./scripts/new-skill.sh [OPTIONS] Non-interactive mode - -OPTIONS - --name NAME Skill name in kebab-case (e.g., "porters-five-forces") - --category CATEGORY Category slug (e.g., "frameworks", "leadership") - --complexity LEVEL basic | intermediate | advanced - --stage STAGE Comma-separated stages: idea,validation,early-traction,growth,scale - --author AUTHOR Author name (default: "Fatih Guner") - --help Show this help message - -EXAMPLES - ./scripts/new-skill.sh --name "my-skill" --category frameworks --complexity intermediate - ./scripts/new-skill.sh --name "my-skill" --category leadership --complexity basic --stage "idea,validation" -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Name must be kebab-case (lowercase letters, numbers, hyphens only): '$name'" - fi -} - -get_categories() { - local cats=() - for dir in "$PROJECT_ROOT"/.claude/skills/*/; do - local base - base="$(basename "$dir")" - [[ "$base" == "_schema" ]] && continue - cats+=("$base") - done - echo "${cats[@]}" -} - -validate_category() { - local cat="$1" - local valid_cats - valid_cats="$(get_categories)" - for c in $valid_cats; do - [[ "$c" == "$cat" ]] && return 0 - done - die "Unknown category '$cat'. Available: $valid_cats" -} - -validate_complexity() { - local level="$1" - case "$level" in - basic|intermediate|advanced) return 0 ;; - *) die "Complexity must be one of: basic, intermediate, advanced" ;; - esac -} - -VALID_STAGES=("idea" "validation" "early-traction" "growth" "scale") - -validate_stage() { - local stage="$1" - for s in "${VALID_STAGES[@]}"; do - [[ "$s" == "$stage" ]] && return 0 - done - die "Unknown stage '$stage'. Valid stages: ${VALID_STAGES[*]}" -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) NAME="$2"; shift 2 ;; - --category) CATEGORY="$2"; shift 2 ;; - --complexity) COMPLEXITY="$2"; shift 2 ;; - --stage) IFS=',' read -ra STAGES <<< "$2"; shift 2 ;; - --author) AUTHOR="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Interactive Prompts ─────────────────────────────────────────────── -if [[ -z "$NAME" ]]; then - read -rp "Skill name (kebab-case, e.g., 'porters-five-forces'): " NAME -fi -validate_kebab_case "$NAME" - -if [[ -z "$CATEGORY" ]]; then - echo "" - echo "Available categories:" - i=1 - cats_array=() - for c in $(get_categories); do - echo " $i) $c" - cats_array+=("$c") - ((i++)) - done - echo "" - read -rp "Select category (number or name): " cat_input - if [[ "$cat_input" =~ ^[0-9]+$ ]]; then - idx=$((cat_input - 1)) - if [[ $idx -ge 0 && $idx -lt ${#cats_array[@]} ]]; then - CATEGORY="${cats_array[$idx]}" - else - die "Invalid selection: $cat_input" - fi - else - CATEGORY="$cat_input" - fi -fi -validate_category "$CATEGORY" - -if [[ -z "$COMPLEXITY" ]]; then - echo "" - echo "Complexity levels:" - echo " 1) basic" - echo " 2) intermediate" - echo " 3) advanced" - read -rp "Select complexity (number or name): " comp_input - case "$comp_input" in - 1) COMPLEXITY="basic" ;; - 2) COMPLEXITY="intermediate" ;; - 3) COMPLEXITY="advanced" ;; - *) COMPLEXITY="$comp_input" ;; - esac -fi -validate_complexity "$COMPLEXITY" - -if [[ ${#STAGES[@]} -eq 0 ]]; then - echo "" - echo "Stages (select all that apply, comma-separated):" - echo " idea, validation, early-traction, growth, scale" - read -rp "Stages [idea,validation,early-traction,growth,scale]: " stage_input - if [[ -z "$stage_input" ]]; then - STAGES=("idea" "validation" "early-traction" "growth" "scale") - else - IFS=',' read -ra STAGES <<< "$stage_input" - fi -fi - -for s in "${STAGES[@]}"; do - s="$(echo "$s" | xargs)" # trim whitespace - validate_stage "$s" -done - -# ── Validate Target ────────────────────────────────────────────────── -TARGET_DIR="$PROJECT_ROOT/.claude/skills/$CATEGORY" -TARGET_FILE="$TARGET_DIR/$NAME.md" - -if [[ ! -d "$TARGET_DIR" ]]; then - die "Category directory does not exist: $TARGET_DIR" -fi - -if [[ -f "$TARGET_FILE" ]]; then - die "Skill already exists: $TARGET_FILE" -fi - -if [[ ! -f "$TEMPLATE" ]]; then - die "Template not found: $TEMPLATE" -fi - -# ── Build Stage YAML ───────────────────────────────────────────────── -stage_yaml="" -for s in "${STAGES[@]}"; do - s="$(echo "$s" | xargs)" - stage_yaml+=" - ${s}\n" -done - -# ── Generate File ───────────────────────────────────────────────────── -cp "$TEMPLATE" "$TARGET_FILE" - -# Replace frontmatter placeholders -sed -i '' "s/^name: .*/name: \"${NAME}\"/" "$TARGET_FILE" -sed -i '' "s/^category: .*/category: \"${CATEGORY}\"/" "$TARGET_FILE" -sed -i '' "s/^complexity: .*/complexity: \"${COMPLEXITY}\"/" "$TARGET_FILE" -sed -i '' "s/^author: .*/author: \"${AUTHOR}\"/" "$TARGET_FILE" - -# Replace stage block -python3 -c " -import re, sys -with open('$TARGET_FILE', 'r') as f: - content = f.read() - -stage_yaml = '''stage: -$(for s in "${STAGES[@]}"; do s="$(echo "$s" | xargs)"; echo " - $s"; done)''' - -content = re.sub( - r'stage:\n(?: - \w[\w-]*\n)+', - stage_yaml + '\n', - content, - count=1 -) -with open('$TARGET_FILE', 'w') as f: - f.write(content) -" - -# ── Confirm ─────────────────────────────────────────────────────────── -echo "" -echo "Created: $TARGET_FILE" -echo "" -echo " Name: $NAME" -echo " Category: $CATEGORY" -echo " Complexity: $COMPLEXITY" -echo " Stages: ${STAGES[*]}" -echo " Author: $AUTHOR" -echo "" - -# Open in editor if available -if [[ -n "${EDITOR:-}" ]]; then - echo "Opening in \$EDITOR ($EDITOR)..." - "$EDITOR" "$TARGET_FILE" -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" new-skill "$@" diff --git a/scripts/new-template.sh b/scripts/new-template.sh index 4c54d00..f2dde1c 100755 --- a/scripts/new-template.sh +++ b/scripts/new-template.sh @@ -1,172 +1,4 @@ -#!/usr/bin/env bash -# -# new-template.sh — Create a new output template from the schema template. -# -# Usage: -# ./scripts/new-template.sh (interactive) -# ./scripts/new-template.sh --audience investor --name "my-template" (non-interactive) -# ./scripts/new-template.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATE="$PROJECT_ROOT/.claude/output-templates/_schema/output-template.md" -TEMPLATES_DIR="$PROJECT_ROOT/output-templates" - -# ── Defaults ────────────────────────────────────────────────────────── -NAME="" -AUDIENCE="" -FORMAT="" -AUTHOR="Fatih Guner" - -VALID_AUDIENCES=("investor" "board" "team" "self" "client") -VALID_FORMATS=( - "one-pager" "memo" "report" "proposal" "briefing" "checklist" "plan" - "dashboard" "email-template" "scorecard" "canvas" "journal-entry" - "reflection" "prep-worksheet" "tracker" "self-assessment" - "meeting-template" "working-document" "planning-guide" "feedback-form" - "structured-review" "case-study" "status-report" "agreement" - "welcome-packet" "review-and-plan" "map" "agenda" "summary" "analysis" "update" -) - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -new-template.sh — Create a new output template from the schema template. - -USAGE - ./scripts/new-template.sh Interactive mode - ./scripts/new-template.sh [OPTIONS] Non-interactive mode - -OPTIONS - --name NAME Template name in kebab-case (e.g., "strategic-analysis-one-pager") - --audience AUDIENCE investor | board | team | self | client - --format FORMAT Template format (one-pager, memo, report, proposal, etc.) - --author AUTHOR Author name (default: "Fatih Guner") - --help Show this help message - -EXAMPLES - ./scripts/new-template.sh --audience investor --name "market-overview" - ./scripts/new-template.sh --audience team --name "sprint-retro" --format "meeting-template" -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Name must be kebab-case (lowercase letters, numbers, hyphens only): '$name'" - fi -} - -validate_audience() { - local audience="$1" - for a in "${VALID_AUDIENCES[@]}"; do - [[ "$a" == "$audience" ]] && return 0 - done - die "Unknown audience '$audience'. Valid audiences: ${VALID_AUDIENCES[*]}" -} - -validate_format() { - local fmt="$1" - for f in "${VALID_FORMATS[@]}"; do - [[ "$f" == "$fmt" ]] && return 0 - done - die "Unknown format '$fmt'. See --help for valid formats." -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --name) NAME="$2"; shift 2 ;; - --audience) AUDIENCE="$2"; shift 2 ;; - --format) FORMAT="$2"; shift 2 ;; - --author) AUTHOR="$2"; shift 2 ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Interactive Prompts ─────────────────────────────────────────────── -if [[ -z "$NAME" ]]; then - read -rp "Template name (kebab-case, e.g., 'strategic-analysis-one-pager'): " NAME -fi -validate_kebab_case "$NAME" - -if [[ -z "$AUDIENCE" ]]; then - echo "" - echo "Target audience:" - i=1 - for a in "${VALID_AUDIENCES[@]}"; do - echo " $i) $a" - ((i++)) - done - echo "" - read -rp "Select audience (number or name): " aud_input - if [[ "$aud_input" =~ ^[0-9]+$ ]]; then - idx=$((aud_input - 1)) - if [[ $idx -ge 0 && $idx -lt ${#VALID_AUDIENCES[@]} ]]; then - AUDIENCE="${VALID_AUDIENCES[$idx]}" - else - die "Invalid selection: $aud_input" - fi - else - AUDIENCE="$aud_input" - fi -fi -validate_audience "$AUDIENCE" - -if [[ -z "$FORMAT" ]]; then - echo "" - echo "Common formats: one-pager, memo, report, proposal, briefing, checklist," - echo " plan, dashboard, email-template, scorecard, canvas, meeting-template" - read -rp "Format: " FORMAT -fi -validate_format "$FORMAT" - -# ── Validate Target ────────────────────────────────────────────────── -TARGET_DIR="$TEMPLATES_DIR/$AUDIENCE" -TARGET_FILE="$TARGET_DIR/$NAME.md" - -if [[ ! -d "$TARGET_DIR" ]]; then - die "Audience directory does not exist: $TARGET_DIR" -fi - -if [[ -f "$TARGET_FILE" ]]; then - die "Template already exists: $TARGET_FILE" -fi - -if [[ ! -f "$TEMPLATE" ]]; then - die "Schema template not found: $TEMPLATE" -fi - -# ── Generate File ───────────────────────────────────────────────────── -cp "$TEMPLATE" "$TARGET_FILE" - -# Replace frontmatter placeholders -sed -i '' "s/^name: .*/name: \"${NAME}\"/" "$TARGET_FILE" -sed -i '' "s/^audience: .*/audience: \"${AUDIENCE}\"/" "$TARGET_FILE" -sed -i '' "s/^format: .*/format: \"${FORMAT}\"/" "$TARGET_FILE" -sed -i '' "s/^author: .*/author: \"${AUTHOR}\"/" "$TARGET_FILE" - -# ── Confirm ─────────────────────────────────────────────────────────── -echo "" -echo "Created: $TARGET_FILE" -echo "" -echo " Name: $NAME" -echo " Audience: $AUDIENCE" -echo " Format: $FORMAT" -echo " Author: $AUTHOR" -echo "" - -# Open in editor if available -if [[ -n "${EDITOR:-}" ]]; then - echo "Opening in \$EDITOR ($EDITOR)..." - "$EDITOR" "$TARGET_FILE" -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" new-template "$@" diff --git a/scripts/openclaw-build.sh b/scripts/openclaw-build.sh index 1a1ebba..c539608 100755 --- a/scripts/openclaw-build.sh +++ b/scripts/openclaw-build.sh @@ -1,190 +1,4 @@ -#!/usr/bin/env bash -# -# openclaw-build.sh — Validate the Foreman OpenClaw plugin build. -# -# Verifies that all plugin components are present and well-formed -# before publishing or distributing the plugin. -# -# Usage: -# ./scripts/openclaw-build.sh -# ./scripts/openclaw-build.sh --help -# -# Author: Fatih Guner -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ───────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -openclaw-build.sh — Validate the Foreman OpenClaw plugin. - -USAGE - ./scripts/openclaw-build.sh Run all validation checks - ./scripts/openclaw-build.sh --help Show this help message - -CHECKS - 1. openclaw.plugin.json exists and is valid JSON - 2. package.json has openclaw.extensions field - 3. index.ts entry point exists - 4. .claude/skills/ has content (source of truth) - 5. .claude-plugin/plugin.json exists (Claude bundle fallback) - 6. Content validation via validate-all.sh (if available) -EOF - exit 0 -} - -[[ "${1:-}" == "--help" || "${1:-}" == "-h" ]] && usage - -# ── Helpers ────────────────────────────────────────────────────────── -pass() { echo " [OK] $*"; } -fail() { echo " [FAIL] $*"; } -info() { echo " [INFO] $*"; } - -errors=0 -warnings=0 - -# ── Header ─────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN — OPENCLAW PLUGIN BUILD CHECK" -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -# ── 1. Plugin Manifest ────────────────────────────────────────────── -echo " 1. Checking openclaw.plugin.json..." - -PLUGIN_JSON="$PROJECT_ROOT/openclaw.plugin.json" -if [[ ! -f "$PLUGIN_JSON" ]]; then - fail "openclaw.plugin.json not found at project root" - errors=$((errors + 1)) -elif ! python3 -c "import json; json.load(open('$PLUGIN_JSON'))" 2>/dev/null && \ - ! node -e "JSON.parse(require('fs').readFileSync('$PLUGIN_JSON','utf-8'))" 2>/dev/null; then - fail "openclaw.plugin.json is not valid JSON" - errors=$((errors + 1)) -else - pass "openclaw.plugin.json exists and is valid JSON" -fi -echo "" - -# ── 2. Package.json Extensions ────────────────────────────────────── -echo " 2. Checking package.json..." - -PACKAGE_JSON="$PROJECT_ROOT/package.json" -if [[ ! -f "$PACKAGE_JSON" ]]; then - fail "package.json not found at project root" - errors=$((errors + 1)) -else - # Check for openclaw.extensions field - has_extensions=false - if command -v node &>/dev/null; then - has_extensions=$(node -e " - const pkg = JSON.parse(require('fs').readFileSync('$PACKAGE_JSON','utf-8')); - console.log(pkg.openclaw && pkg.openclaw.extensions ? 'true' : 'false'); - " 2>/dev/null || echo "false") - elif command -v python3 &>/dev/null; then - has_extensions=$(python3 -c " -import json -pkg = json.load(open('$PACKAGE_JSON')) -print('true' if pkg.get('openclaw', {}).get('extensions') else 'false') -" 2>/dev/null || echo "false") - fi - - if [[ "$has_extensions" == "true" ]]; then - pass "package.json has openclaw.extensions field" - else - fail "package.json missing openclaw.extensions field" - errors=$((errors + 1)) - fi -fi -echo "" - -# ── 3. Entry Point ────────────────────────────────────────────────── -echo " 3. Checking entry point..." - -INDEX_TS="$PROJECT_ROOT/index.ts" -if [[ -f "$INDEX_TS" ]]; then - pass "index.ts exists" -else - fail "index.ts not found at project root" - errors=$((errors + 1)) -fi -echo "" - -# ── 4. Skills Directory ───────────────────────────────────────────── -echo " 4. Checking .claude/skills/..." - -SKILLS_DIR="$PROJECT_ROOT/.claude/skills" -if [[ ! -d "$SKILLS_DIR" ]]; then - fail ".claude/skills/ directory not found" - errors=$((errors + 1)) -else - skill_count=0 - for category_dir in "$SKILLS_DIR"/*/; do - if [[ -d "$category_dir" ]] && [[ "$(basename "$category_dir")" != "_schema" ]]; then - dir_count=$(find "$category_dir" -maxdepth 1 -name "*.md" 2>/dev/null | wc -l | tr -d ' ') - skill_count=$((skill_count + dir_count)) - fi - done - - if [[ $skill_count -gt 0 ]]; then - category_count=$(find "$SKILLS_DIR" -mindepth 1 -maxdepth 1 -type d -not -name "_schema" 2>/dev/null | wc -l | tr -d ' ') - pass ".claude/skills/ has $skill_count skills across $category_count categories" - else - fail ".claude/skills/ exists but contains no skill files" - errors=$((errors + 1)) - fi -fi -echo "" - -# ── 5. Claude Bundle Fallback ──────────────────────────────────────── -echo " 5. Checking .claude-plugin/plugin.json..." - -CLAUDE_PLUGIN="$PROJECT_ROOT/.claude-plugin/plugin.json" -if [[ -f "$CLAUDE_PLUGIN" ]]; then - pass ".claude-plugin/plugin.json exists (Claude bundle fallback)" -else - info ".claude-plugin/plugin.json not found — Claude bundle fallback unavailable" - warnings=$((warnings + 1)) -fi -echo "" - -# ── 6. Content Validation ──────────────────────────────────────────── -echo " 6. Running content validation..." - -VALIDATE_ALL="$SCRIPT_DIR/validate-all.sh" -if [[ -x "$VALIDATE_ALL" ]]; then - if "$VALIDATE_ALL" 2>&1 | tail -5; then - pass "Content validation passed" - else - fail "Content validation reported issues. Run ./scripts/validate-all.sh for details." - errors=$((errors + 1)) - fi -else - info "validate-all.sh not found or not executable — skipping content validation" - warnings=$((warnings + 1)) -fi -echo "" - -# ── Summary ────────────────────────────────────────────────────────── -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -if [[ $errors -eq 0 ]]; then - if [[ $warnings -gt 0 ]]; then - echo " Plugin ready ($warnings warning(s) — non-blocking)." - else - echo " Plugin ready. All checks passed." - fi - echo "" - echo " To install locally: openclaw plugins install ./" - echo " To test: openclaw tool foreman_list_skills" - echo "" -else - echo " Build check failed with $errors error(s). Fix the issues above before publishing." - echo "" - exit 1 -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" openclaw-build "$@" diff --git a/scripts/openclaw-setup.mjs b/scripts/openclaw-setup.mjs new file mode 100644 index 0000000..f0070eb --- /dev/null +++ b/scripts/openclaw-setup.mjs @@ -0,0 +1,29 @@ +#!/usr/bin/env node +import fs from 'node:fs'; +import path from 'node:path'; +import { execFileSync } from 'node:child_process'; +import { buildPlugins } from '../lib/distribution.js'; +import { within, atomicWrite } from '../lib/maintenance.js'; +const root=path.resolve(import.meta.dirname,'..'); +try { + const args=process.argv.slice(2);let workspace=process.cwd(),skipTemplates=false; + if(args.includes('--help')||args.includes('-h')) {console.log('Usage: openclaw-setup.sh [--workspace DIR] [--skip-templates] [--skip-bootstrap]\nBuilds and installs the plugin, preserving existing workspace templates. No model call is started.');process.exit(0);} + for(let i=0;in.endsWith('.md'))) { + const dest=within(workspace,name); + try {atomicWrite(dest,fs.readFileSync(path.join(root,'openclaw-templates',name),'utf8'),{create:true});copied++;} + catch(e){if(e.code==='EEXIST')preserved++;else throw e;} + } + console.log(`${copied} templates added; ${preserved} existing files preserved.`); + } + console.log('Foreman installed. Start an OpenClaw conversation when ready.'); +}catch(e){console.error(e.message);process.exitCode=1;} diff --git a/scripts/openclaw-setup.sh b/scripts/openclaw-setup.sh index 3503ad4..37117db 100755 --- a/scripts/openclaw-setup.sh +++ b/scripts/openclaw-setup.sh @@ -1,229 +1,4 @@ -#!/usr/bin/env bash -# -# openclaw-setup.sh — Set up Foreman as an OpenClaw agent in your workspace. -# -# This is the companion to setup.sh (which is for Claude Code contributors). -# This script is for entrepreneurs using Foreman through OpenClaw. -# -# Usage: -# ./scripts/openclaw-setup.sh -# ./scripts/openclaw-setup.sh --workspace /path/to/workspace -# ./scripts/openclaw-setup.sh --skip-templates --skip-bootstrap -# ./scripts/openclaw-setup.sh --help -# -# Author: Fatih Guner -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATES_DIR="$PROJECT_ROOT/openclaw-templates" - -# ── Defaults ───────────────────────────────────────────────────────── -WORKSPACE_ROOT="" -SKIP_TEMPLATES=false -SKIP_BOOTSTRAP=false - -# ── Help ───────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -openclaw-setup.sh — Set up Foreman as an OpenClaw agent. - -USAGE - ./scripts/openclaw-setup.sh Full setup (current directory as workspace) - ./scripts/openclaw-setup.sh --workspace /path Use a custom workspace root - ./scripts/openclaw-setup.sh --skip-templates Install plugin only, skip template copy - ./scripts/openclaw-setup.sh --skip-bootstrap Skip the bootstrap conversation prompt - ./scripts/openclaw-setup.sh --help Show this help message - -WHAT IT DOES - 1. Verifies OpenClaw CLI is installed - 2. Installs the Foreman plugin - 3. Verifies installation - 4. Copies workspace templates (SOUL.md, IDENTITY.md, AGENTS.md, etc.) - 5. Optionally runs the bootstrap conversation for first-time setup - -FLAGS - --workspace PATH Custom workspace root (default: current directory) - --skip-templates Do not copy templates to workspace - --skip-bootstrap Do not prompt for bootstrap conversation - --help, -h Show this help message -EOF - exit 0 -} - -# ── Parse Arguments ────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) - usage - ;; - --workspace) - WORKSPACE_ROOT="$2" - shift 2 - ;; - --skip-templates) - SKIP_TEMPLATES=true - shift - ;; - --skip-bootstrap) - SKIP_BOOTSTRAP=true - shift - ;; - *) - echo "Unknown argument: $1" - echo "Run with --help for usage." - exit 1 - ;; - esac -done - -# Default workspace to current directory -if [[ -z "$WORKSPACE_ROOT" ]]; then - WORKSPACE_ROOT="$(pwd)" -fi - -# ── Helpers ────────────────────────────────────────────────────────── -pass() { echo " [OK] $*"; } -fail() { echo " [FAIL] $*"; } -info() { echo " [INFO] $*"; } - -errors=0 - -# ── Header ─────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN — OPENCLAW SETUP" -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -# ── 1. Check OpenClaw CLI ──────────────────────────────────────────── -echo " 1. Checking OpenClaw CLI..." - -if ! command -v openclaw &>/dev/null; then - fail "OpenClaw CLI not found." - echo "" - echo " Install OpenClaw first:" - echo " npm install -g openclaw" - echo " # or: brew install openclaw" - echo "" - echo " Then re-run this script." - exit 1 -fi - -openclaw_version=$(openclaw --version 2>/dev/null || echo "unknown") -pass "OpenClaw CLI found (version: $openclaw_version)" -echo "" - -# ── 2. Install Foreman Plugin ──────────────────────────────────────── -echo " 2. Installing Foreman plugin..." - -if openclaw plugins install "$PROJECT_ROOT" 2>/dev/null; then - pass "Foreman plugin installed from $PROJECT_ROOT" -else - fail "Plugin installation failed." - echo " Check that openclaw.plugin.json exists and is valid." - errors=$((errors + 1)) -fi -echo "" - -# ── 3. Verify Installation ────────────────────────────────────────── -echo " 3. Verifying installation..." - -if openclaw plugins inspect foreman 2>/dev/null; then - pass "Plugin 'foreman' is registered and accessible" -else - fail "Plugin verification failed. 'openclaw plugins inspect foreman' returned an error." - errors=$((errors + 1)) -fi -echo "" - -# ── 4. Copy Templates ─────────────────────────────────────────────── -if [[ "$SKIP_TEMPLATES" == true ]]; then - info "Skipping template copy (--skip-templates)" - echo "" -else - echo " 4. Copying workspace templates..." - - if [[ ! -d "$TEMPLATES_DIR" ]]; then - fail "Templates directory not found at $TEMPLATES_DIR" - errors=$((errors + 1)) - else - template_count=0 - for template_file in "$TEMPLATES_DIR"/*.md; do - if [[ -f "$template_file" ]]; then - filename="$(basename "$template_file")" - target="$WORKSPACE_ROOT/$filename" - - if [[ -f "$target" ]]; then - info "Skipping $filename (already exists in workspace)" - else - cp "$template_file" "$target" - template_count=$((template_count + 1)) - fi - fi - done - - if [[ $template_count -gt 0 ]]; then - pass "Copied $template_count template(s) to $WORKSPACE_ROOT/" - else - info "All templates already present in workspace" - fi - fi - echo "" -fi - -# ── 5. Bootstrap Conversation ──────────────────────────────────────── -if [[ "$SKIP_BOOTSTRAP" == true ]]; then - info "Skipping bootstrap conversation (--skip-bootstrap)" - echo "" -elif [[ ! -f "$WORKSPACE_ROOT/BOOTSTRAP.md" ]]; then - info "No BOOTSTRAP.md in workspace — skipping bootstrap prompt" - echo "" -else - echo " 5. Bootstrap conversation..." - echo "" - echo " Foreman works best with context about you and your company." - echo " The bootstrap conversation takes 2-3 minutes and sets up your profile." - echo "" - read -r -p " Run the bootstrap conversation now? [y/N] " response - echo "" - - if [[ "$response" =~ ^[Yy]$ ]]; then - info "Starting bootstrap conversation..." - openclaw agent --message "Read BOOTSTRAP.md and run the first-time setup conversation with me." 2>/dev/null || { - fail "Bootstrap conversation failed. You can run it manually later:" - echo " openclaw agent --message 'Run the BOOTSTRAP.md setup conversation'" - } - else - info "Skipped. Run the bootstrap later with:" - echo " openclaw agent --message 'Run the BOOTSTRAP.md setup conversation'" - fi - echo "" -fi - -# ── Summary ────────────────────────────────────────────────────────── -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -if [[ $errors -eq 0 ]]; then - echo " Setup complete." - echo "" - echo " What was installed:" - echo " - Foreman OpenClaw plugin (7 tools registered)" - if [[ "$SKIP_TEMPLATES" != true ]]; then - echo " - Workspace templates (SOUL.md, IDENTITY.md, AGENTS.md, BOOT.md, etc.)" - fi - echo "" - echo " Next steps:" - echo " - Start a conversation: openclaw agent" - echo " - Browse skills: openclaw tool foreman_list_skills" - echo " - Run a diagnostic: openclaw tool foreman_diagnose --area revenue" - echo " - Read the docs: https://foreman.sh" - echo "" -else - echo " Setup completed with $errors error(s). Fix the issues above and re-run." - echo "" - exit 1 -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/openclaw-setup.mjs" "$@" diff --git a/scripts/orphan-check.sh b/scripts/orphan-check.sh index 4aa5bde..f86e828 100755 --- a/scripts/orphan-check.sh +++ b/scripts/orphan-check.sh @@ -1,204 +1,4 @@ -#!/usr/bin/env bash -# -# orphan-check.sh — Find files never referenced by anything else in the project. -# -# Usage: -# ./scripts/orphan-check.sh -# ./scripts/orphan-check.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -orphan-check.sh — Find files never referenced by anything else. - -USAGE - ./scripts/orphan-check.sh Scan for orphan files - ./scripts/orphan-check.sh --help Show this help message - -CHECKS - - Skills not mentioned in any hook, diagnostic, playbook, or other skill's related_skills - - Templates not mentioned in any playbook's final_outputs or diagnostic's routes_to_templates - - Diagnostics not mentioned in any hook or playbook - -Reports orphans with suggestions for what to connect them to. -EOF - exit 0 -} - -[[ "${1:-}" == "--help" || "${1:-}" == "-h" ]] && usage - -# ── Helpers ─────────────────────────────────────────────────────────── -orphan_count=0 - -check_orphan_skills() { - echo " ORPHAN SKILLS" - echo " $(printf '%56s' '' | tr ' ' '-')" - echo "" - - local found=0 - - # Build a combined reference corpus from hooks, diagnostics, playbooks, and other skills - local ref_corpus - ref_corpus=$(cat \ - "$PROJECT_ROOT"/hooks/*.md \ - "$PROJECT_ROOT"/.claude/diagnostics/*.md \ - "$PROJECT_ROOT"/.claude/playbooks/*.md \ - 2>/dev/null || true) - - for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - - local skill_name - skill_name="$(basename "$skill_file" .md)" - - # Check if this skill name appears anywhere in the reference corpus - local in_external=false - if echo "$ref_corpus" | grep -q "$skill_name" 2>/dev/null; then - in_external=true - fi - - # Check if referenced in another skill's related_skills - local in_related=false - for other_skill in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$other_skill" == "$skill_file" ]] && continue - [[ "$(basename "$other_skill")" == "skill-template.md" ]] && continue - if grep -q "$skill_name" "$other_skill" 2>/dev/null; then - in_related=true - break - fi - done - - if [[ "$in_external" == "false" && "$in_related" == "false" ]]; then - local category - category="$(basename "$(dirname "$skill_file")")" - echo " $skill_name ($category)" - - # Suggest connection based on category - local hook_match - hook_match=$(grep -l "$category" "$PROJECT_ROOT"/hooks/*.md 2>/dev/null | head -1 || true) - if [[ -n "$hook_match" ]]; then - echo " -> Consider adding to: $(basename "$hook_match")" - else - echo " -> Consider creating a hook or adding to a playbook" - fi - echo "" - found=$((found + 1)) - orphan_count=$((orphan_count + 1)) - fi - done - - if [[ $found -eq 0 ]]; then - echo " No orphan skills found." - echo "" - else - echo " Found $found orphan skill(s)." - fi - echo "" -} - -check_orphan_templates() { - echo " ORPHAN TEMPLATES" - echo " $(printf '%56s' '' | tr ' ' '-')" - echo "" - - local found=0 - - # Build reference corpus from playbooks and diagnostics - local ref_corpus - ref_corpus=$(cat \ - "$PROJECT_ROOT"/.claude/playbooks/*.md \ - "$PROJECT_ROOT"/.claude/diagnostics/*.md \ - "$PROJECT_ROOT"/.claude/skills/*/*.md \ - 2>/dev/null || true) - - for audience_dir in "$PROJECT_ROOT"/.claude/output-templates/*/; do - local audience - audience="$(basename "$audience_dir")" - [[ "$audience" == "_schema" ]] && continue - - for tmpl_file in "$audience_dir"*.md; do - [[ ! -f "$tmpl_file" ]] && continue - local tmpl_name - tmpl_name="$(basename "$tmpl_file" .md)" - - if ! echo "$ref_corpus" | grep -q "$tmpl_name" 2>/dev/null; then - echo " $tmpl_name ($audience)" - echo " -> Consider referencing in a playbook's final_outputs or a skill's output template" - echo "" - found=$((found + 1)) - orphan_count=$((orphan_count + 1)) - fi - done - done - - if [[ $found -eq 0 ]]; then - echo " No orphan templates found." - echo "" - else - echo " Found $found orphan template(s)." - fi - echo "" -} - -check_orphan_diagnostics() { - echo " ORPHAN DIAGNOSTICS" - echo " $(printf '%56s' '' | tr ' ' '-')" - echo "" - - local found=0 - - # Build reference corpus from hooks and playbooks - local ref_corpus - ref_corpus=$(cat \ - "$PROJECT_ROOT"/hooks/*.md \ - "$PROJECT_ROOT"/.claude/playbooks/*.md \ - 2>/dev/null || true) - - for diag_file in "$PROJECT_ROOT"/.claude/diagnostics/*.md; do - [[ ! -f "$diag_file" ]] && continue - local diag_name - diag_name="$(basename "$diag_file" .md)" - - if ! echo "$ref_corpus" | grep -q "$diag_name" 2>/dev/null; then - echo " $diag_name" - echo " -> Consider adding to a hook's routes_to.diagnostics" - echo "" - found=$((found + 1)) - orphan_count=$((orphan_count + 1)) - fi - done - - if [[ $found -eq 0 ]]; then - echo " No orphan diagnostics found." - echo "" - else - echo " Found $found orphan diagnostic(s)." - fi - echo "" -} - -# ── Main ────────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN ORPHAN CHECK" -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -check_orphan_skills -check_orphan_templates -check_orphan_diagnostics - -echo " $(printf '%56s' '' | tr ' ' '=')" -if [[ $orphan_count -eq 0 ]]; then - echo " All files are cross-referenced. No orphans found." -else - echo " Total orphans: $orphan_count" - echo " Run this check again after adding cross-references." -fi -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" orphan-check "$@" diff --git a/scripts/package-smoke.mjs b/scripts/package-smoke.mjs new file mode 100644 index 0000000..8fec1cf --- /dev/null +++ b/scripts/package-smoke.mjs @@ -0,0 +1,41 @@ +#!/usr/bin/env node +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { execFileSync } from 'node:child_process'; + +assert.equal(process.argv.length, 3, 'Usage: package-smoke.mjs /path/to/package.tgz'); +const archive = path.resolve(process.argv[2]); +assert.ok(fs.statSync(archive).isFile()); +const root = fs.mkdtempSync(path.join(os.tmpdir(), 'foreman-package-')); +const run = (command, args) => execFileSync(command, args, { cwd: root, encoding: 'utf8', timeout: 120000, stdio: ['ignore', 'pipe', 'pipe'] }); +try { + fs.writeFileSync(path.join(root, 'package.json'), '{"private":true}\n'); + run('npm', ['install', archive, '--ignore-scripts', '--no-audit', '--no-fund']); + const installed = path.join(root, 'node_modules/foreman-sh'); + const pkg = JSON.parse(fs.readFileSync(path.join(installed, 'package.json'), 'utf8')); + for (const file of ['dist/index.js', '.codex-plugin/plugin.json', '.claude-plugin/plugin.json', 'plugins/foreman/.claude-plugin/plugin.json', 'docs/development.md', 'assets/logo-foreman.svg', 'LICENSE']) { + assert.ok(fs.statSync(path.join(installed, file)).isFile(), `Missing packaged file: ${file}`); + } + for (const file of ['.foreman', '.env', '.npmrc', '.claude/settings.local.json']) { + assert.equal(fs.existsSync(path.join(installed, file)), false, `Private runtime file shipped: ${file}`); + } + const cli = path.join(installed, pkg.bin['foreman-sh']); + const workspace = path.join(root, 'workspace'); + assert.match(run(process.execPath, [cli, 'init', '--platform', 'all', '--workspace', workspace]), /files added/); + assert.ok(fs.existsSync(path.join(workspace, '.agents/skills/foreman/SKILL.md'))); + assert.ok(fs.existsSync(path.join(workspace, '.agents/content/RUNTIME.md'))); + assert.ok(fs.existsSync(path.join(workspace, '.claude/commands/solo.md'))); + fs.writeFileSync(path.join(workspace, 'CLAUDE.md'), 'Keep my project instructions'); + assert.match(run(process.execPath, [cli, 'init', '--platform', 'all', '--workspace', workspace]), /0 files added/); + assert.equal(fs.readFileSync(path.join(workspace, 'CLAUDE.md'), 'utf8'), 'Keep my project instructions'); + const profile = JSON.parse(run(process.execPath, [cli, 'state', 'profile', '--workspace', workspace, '--mode', 'solo', '--language', 'tr'])); + assert.ok(JSON.stringify(profile).includes('solo')); + const saved = JSON.parse(fs.readFileSync(path.join(workspace, '.foreman/default/state.json'), 'utf8')); + assert.equal(saved.identity.mode, 'solo'); + assert.equal(saved.identity.language, 'tr'); + console.log(`Packed installation verified: foreman-sh@${pkg.version}; Claude + Codex resources, preserved files and persisted profile`); +} finally { + fs.rmSync(root, { recursive: true, force: true }); +} diff --git a/scripts/pre-commit-hook.sh b/scripts/pre-commit-hook.sh index aa3141c..5515a56 100755 --- a/scripts/pre-commit-hook.sh +++ b/scripts/pre-commit-hook.sh @@ -1,155 +1,4 @@ -#!/usr/bin/env bash -# -# pre-commit-hook.sh — Git pre-commit hook for Foreman. -# -# Runs on staged .md files only. Designed to complete in under 2 seconds. -# -# Checks: -# 1. Prohibited phrases (from CLAUDE.md writing style guide) -# 2. Frontmatter existence -# 3. Blocked author names (configurable) -# -# Install: -# ln -s ../../scripts/pre-commit-hook.sh .git/hooks/pre-commit -# -# Usage: -# Runs automatically on git commit. Exit 1 blocks the commit. -# ./scripts/pre-commit-hook.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" - -# Handle case where script is called from .git/hooks/ via symlink -if [[ -L "${BASH_SOURCE[0]}" ]]; then - REAL_SCRIPT="$(readlink "${BASH_SOURCE[0]}")" - if [[ "$REAL_SCRIPT" != /* ]]; then - REAL_SCRIPT="$(cd "$(dirname "${BASH_SOURCE[0]}")" && cd "$(dirname "$REAL_SCRIPT")" && pwd)/$(basename "$REAL_SCRIPT")" - fi - SCRIPT_DIR="$(dirname "$REAL_SCRIPT")" -fi - -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ────────────────────────────────────────────────────────────── -if [[ "${1:-}" == "--help" || "${1:-}" == "-h" ]]; then - cat <<'EOF' -pre-commit-hook.sh — Git pre-commit hook for Foreman. - -Runs automatically on staged .md files. Exit 1 blocks the commit. - -CHECKS - 1. Prohibited phrases from the writing style guide - 2. Frontmatter existence (YAML block between --- delimiters) - 3. Blocked author names (configurable blocklist) - -INSTALL - ln -s ../../scripts/pre-commit-hook.sh .git/hooks/pre-commit - (or run ./scripts/setup.sh) - -CONFIGURATION - Edit the BLOCKED_AUTHORS array in this script to add/remove names. -EOF - exit 0 -fi - -# ── Configuration ───────────────────────────────────────────────────── - -# Prohibited phrases from CLAUDE.md Absolute Prohibitions -PROHIBITED_PHRASES=( - "In today's fast-paced" - "In today's rapidly" - "In today's ever-changing" - "In today's competitive" - "Let's dive in" - "Let's explore" - "In this skill, you will learn" - "Without further ado" - "It's important to note that" - "At the end of the day" -) - -# Blocked author names — add names that should not appear in commits -# Example: authors whose content has been anonymized -BLOCKED_AUTHORS=( - # "Blocked Author Name" -) - -# ── Get Staged .md Files ────────────────────────────────────────────── -staged_files=() -while IFS= read -r file; do - [[ -n "$file" ]] && staged_files+=("$file") -done < <(git diff --cached --name-only --diff-filter=ACM -- '*.md' 2>/dev/null || true) - -# Nothing to check -if [[ ${#staged_files[@]} -eq 0 ]]; then - exit 0 -fi - -# ── Run Checks ──────────────────────────────────────────────────────── -errors=0 -error_messages=() - -add_error() { - errors=$((errors + 1)) - error_messages+=("$1") -} - -for file in "${staged_files[@]}"; do - full_path="$PROJECT_ROOT/$file" - [[ ! -f "$full_path" ]] && continue - - # Read file content once for performance - content=$(cat "$full_path") - - # ── Check 1: Prohibited Phrases ────────────────────────────────── - for phrase in "${PROHIBITED_PHRASES[@]}"; do - line_num=$(echo "$content" | grep -n -i "$phrase" 2>/dev/null | head -1 | cut -d: -f1 || true) - if [[ -n "$line_num" ]]; then - add_error "$file:$line_num: Prohibited phrase: \"$phrase\"" - fi - done - - # ── Check 2: Frontmatter Existence ─────────────────────────────── - # Skip files in _schema directories (templates have placeholder frontmatter) - if [[ "$file" != *"_schema"* ]]; then - # Check if file starts with --- and has a closing --- - first_line=$(echo "$content" | head -1) - if [[ "$first_line" != "---" ]]; then - add_error "$file: Missing frontmatter (file must start with '---')" - else - # Check for closing --- - closing=$(echo "$content" | tail -n +2 | grep -n "^---$" | head -1 || true) - if [[ -z "$closing" ]]; then - add_error "$file: Incomplete frontmatter (missing closing '---')" - fi - fi - fi - - # ── Check 3: Blocked Author Names ──────────────────────────────── - for author in "${BLOCKED_AUTHORS[@]}"; do - [[ -z "$author" ]] && continue - line_num=$(echo "$content" | grep -n "$author" 2>/dev/null | head -1 | cut -d: -f1 || true) - if [[ -n "$line_num" ]]; then - add_error "$file:$line_num: Blocked author name: \"$author\"" - fi - done -done - -# ── Report ──────────────────────────────────────────────────────────── -if [[ $errors -gt 0 ]]; then - echo "" - echo " PRE-COMMIT CHECK FAILED ($errors error(s))" - echo " $(printf '%56s' '' | tr ' ' '-')" - echo "" - for msg in "${error_messages[@]}"; do - echo " $msg" - done - echo "" - echo " Fix the issues above and stage the corrected files." - echo " To bypass this check (not recommended): git commit --no-verify" - echo "" - exit 1 -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" pre-commit-hook "$@" diff --git a/scripts/rename-category.sh b/scripts/rename-category.sh index 8769e27..ce9ee21 100755 --- a/scripts/rename-category.sh +++ b/scripts/rename-category.sh @@ -1,191 +1,4 @@ -#!/usr/bin/env bash -# -# rename-category.sh — Rename a skill category and update ALL references. -# -# Usage: -# ./scripts/rename-category.sh --from old-name --to new-name (preview) -# ./scripts/rename-category.sh --from old-name --to new-name --confirm (execute) -# ./scripts/rename-category.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Defaults ────────────────────────────────────────────────────────── -FROM="" -TO="" -CONFIRM=false - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -rename-category.sh — Rename a skill category and update ALL references. - -USAGE - ./scripts/rename-category.sh --from OLD --to NEW Preview changes - ./scripts/rename-category.sh --from OLD --to NEW --confirm Execute changes - ./scripts/rename-category.sh --help - -OPTIONS - --from OLD Current category slug (e.g., "ai-leadership") - --to NEW New category slug in kebab-case (e.g., "ai-strategy") - --confirm Actually execute the rename (without this, preview only) - --help Show this help message - -UPDATES - - Directory: .claude/.claude/skills/OLD/ -> .claude/.claude/skills/NEW/ - - Frontmatter: category field in all skills in the renamed directory - - Cross-references: Related Skills links across ALL skills - - Diagnostics: any reference to .claude/.claude/skills/OLD/ - - Playbooks: any reference to .claude/.claude/skills/OLD/ - - Hooks: any reference to .claude/.claude/skills/OLD/ - - CLAUDE.md: category references -EOF - exit 0 -} - -# ── Helpers ─────────────────────────────────────────────────────────── -die() { echo "ERROR: $*" >&2; exit 1; } - -validate_kebab_case() { - local name="$1" - if [[ ! "$name" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then - die "Category must be kebab-case: '$name'" - fi -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --from) FROM="$2"; shift 2 ;; - --to) TO="$2"; shift 2 ;; - --confirm) CONFIRM=true; shift ;; - *) die "Unknown option: $1. Use --help for usage." ;; - esac -done - -# ── Validate ────────────────────────────────────────────────────────── -[[ -z "$FROM" ]] && die "--from is required." -[[ -z "$TO" ]] && die "--to is required." -validate_kebab_case "$FROM" -validate_kebab_case "$TO" - -FROM_DIR="$PROJECT_ROOT/.claude/skills/$FROM" -TO_DIR="$PROJECT_ROOT/.claude/skills/$TO" - -[[ ! -d "$FROM_DIR" ]] && die "Source category does not exist: $FROM_DIR" -[[ -d "$TO_DIR" ]] && die "Target category already exists: $TO_DIR" - -# ── Scan for References ────────────────────────────────────────────── -echo "" -echo " CATEGORY RENAME: $FROM -> $TO" -echo " $(printf '%60s' '' | tr ' ' '=')" -echo "" - -# 1. Directory rename -skill_count=$(find "$FROM_DIR" -maxdepth 1 -name "*.md" | wc -l | tr -d ' ') -echo " 1. Directory rename: .claude/.claude/skills/$FROM/ -> .claude/.claude/skills/$TO/ ($skill_count files)" -echo "" - -# 2. Frontmatter category field -echo " 2. Frontmatter updates (category: \"$FROM\" -> category: \"$TO\"):" -for f in "$FROM_DIR"/*.md; do - [[ ! -f "$f" ]] && continue - echo " $(basename "$f")" -done -echo "" - -# 3. Cross-references in all skills -echo " 3. Cross-reference updates (../$FROM/ -> ../$TO/):" -ref_files=() -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - if grep -q "$FROM" "$skill_file" 2>/dev/null; then - ref_files+=("$skill_file") - echo " $(echo "$skill_file" | sed "s|$PROJECT_ROOT/||")" - fi -done -echo " ${#ref_files[@]} file(s) with references" -echo "" - -# 4. Diagnostics, Playbooks, Hooks -echo " 4. Other references:" -other_refs=0 -for search_dir in diagnostics playbooks hooks; do - for f in "$PROJECT_ROOT/$search_dir"/*.md; do - [[ ! -f "$f" ]] && continue - if grep -q "$FROM" "$f" 2>/dev/null; then - echo " $(echo "$f" | sed "s|$PROJECT_ROOT/||")" - other_refs=$((other_refs + 1)) - fi - done -done - -# CLAUDE.md -if grep -q "$FROM" "$PROJECT_ROOT/CLAUDE.md" 2>/dev/null; then - echo " CLAUDE.md" - other_refs=$((other_refs + 1)) -fi -echo " $other_refs file(s)" -echo "" - -# ── Execute or Preview ──────────────────────────────────────────────── -if [[ "$CONFIRM" == false ]]; then - echo " $(printf '%60s' '' | tr ' ' '-')" - echo " Preview mode. No changes written." - echo " Add --confirm to execute the rename." - echo "" - exit 0 -fi - -echo " $(printf '%60s' '' | tr ' ' '-')" -echo " Executing rename..." -echo "" - -# Step 1: Rename directory -mv "$FROM_DIR" "$TO_DIR" -echo " [OK] Renamed directory: .claude/.claude/skills/$FROM/ -> .claude/.claude/skills/$TO/" - -# Step 2: Update frontmatter in renamed skills -for f in "$TO_DIR"/*.md; do - [[ ! -f "$f" ]] && continue - sed -i '' "s/^category: \"$FROM\"/category: \"$TO\"/" "$f" -done -echo " [OK] Updated frontmatter category field in $skill_count file(s)" - -# Step 3: Update cross-references in ALL skill files -updated=0 -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - if grep -q "$FROM" "$skill_file" 2>/dev/null; then - sed -i '' "s|$FROM|$TO|g" "$skill_file" - updated=$((updated + 1)) - fi -done -echo " [OK] Updated cross-references in $updated skill file(s)" - -# Step 4: Update diagnostics, playbooks, hooks -for search_dir in diagnostics playbooks hooks; do - for f in "$PROJECT_ROOT/$search_dir"/*.md; do - [[ ! -f "$f" ]] && continue - if grep -q "$FROM" "$f" 2>/dev/null; then - sed -i '' "s|$FROM|$TO|g" "$f" - fi - done -done -echo " [OK] Updated diagnostics, playbooks, and hooks" - -# Step 5: Update CLAUDE.md -if grep -q "$FROM" "$PROJECT_ROOT/CLAUDE.md" 2>/dev/null; then - sed -i '' "s|$FROM|$TO|g" "$PROJECT_ROOT/CLAUDE.md" - echo " [OK] Updated CLAUDE.md" -fi - -echo "" -echo " Rename complete: $FROM -> $TO" -echo " Run ./scripts/stats.sh to verify the new state." -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" rename-category "$@" diff --git a/scripts/setup.sh b/scripts/setup.sh index 7c75840..4bc0bab 100755 --- a/scripts/setup.sh +++ b/scripts/setup.sh @@ -1,208 +1,4 @@ -#!/usr/bin/env bash -# -# setup.sh — First-time project setup for new Foreman contributors. -# -# Usage: -# ./scripts/setup.sh -# ./scripts/setup.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -setup.sh — First-time project setup for new contributors. - -USAGE - ./scripts/setup.sh Run full setup - ./scripts/setup.sh --help Show this help message - -CHECKS - 1. Git version (requires 2.20+) - 2. Pre-commit hook installation - 3. EditorConfig support verification - 4. Project health check (validates all files) - 5. Ready-to-contribute confirmation -EOF - exit 0 -} - -[[ "${1:-}" == "--help" || "${1:-}" == "-h" ]] && usage - -# ── Helpers ─────────────────────────────────────────────────────────── -pass() { echo " [OK] $*"; } -fail() { echo " [FAIL] $*"; } -warn() { echo " [WARN] $*"; } -info() { echo " [INFO] $*"; } - -errors=0 - -# ── Header ──────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN PROJECT SETUP" -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -# ── 1. Git Version ─────────────────────────────────────────────────── -echo " 1. Checking Git..." - -if ! command -v git &>/dev/null; then - fail "Git is not installed. Install git and try again." - errors=$((errors + 1)) -else - git_version=$(git --version | sed 's/git version //') - major=$(echo "$git_version" | cut -d. -f1) - minor=$(echo "$git_version" | cut -d. -f2) - - if [[ $major -gt 2 ]] || [[ $major -eq 2 && $minor -ge 20 ]]; then - pass "Git $git_version (requires 2.20+)" - else - fail "Git $git_version is too old. Requires 2.20+." - errors=$((errors + 1)) - fi -fi - -# Verify we are in a git repo -if git -C "$PROJECT_ROOT" rev-parse --git-dir &>/dev/null; then - pass "Inside a git repository" -else - fail "Not inside a git repository. Run 'git init' first." - errors=$((errors + 1)) -fi -echo "" - -# ── 2. Pre-commit Hook ─────────────────────────────────────────────── -echo " 2. Setting up pre-commit hook..." - -GIT_DIR=$(git -C "$PROJECT_ROOT" rev-parse --git-dir 2>/dev/null || echo "$PROJECT_ROOT/.git") -HOOKS_DIR="$GIT_DIR/hooks" -HOOK_SOURCE="$SCRIPT_DIR/pre-commit-hook.sh" -HOOK_TARGET="$HOOKS_DIR/pre-commit" - -if [[ ! -f "$HOOK_SOURCE" ]]; then - warn "Pre-commit hook source not found at: $HOOK_SOURCE" - warn "Skipping hook installation." -else - mkdir -p "$HOOKS_DIR" - if [[ -f "$HOOK_TARGET" ]] || [[ -L "$HOOK_TARGET" ]]; then - # Check if it already points to our hook - if [[ -L "$HOOK_TARGET" ]] && [[ "$(readlink "$HOOK_TARGET")" == "$HOOK_SOURCE" ]]; then - pass "Pre-commit hook already installed (symlink exists)" - else - warn "Existing pre-commit hook found at $HOOK_TARGET" - warn "Back up and replace manually if needed:" - warn " ln -sf $HOOK_SOURCE $HOOK_TARGET" - fi - else - ln -s "$HOOK_SOURCE" "$HOOK_TARGET" - chmod +x "$HOOK_TARGET" - pass "Pre-commit hook installed (symlinked to scripts/pre-commit-hook.sh)" - fi -fi -echo "" - -# ── 3. EditorConfig ────────────────────────────────────────────────── -echo " 3. Checking EditorConfig..." - -if [[ -f "$PROJECT_ROOT/.editorconfig" ]]; then - pass ".editorconfig file found" -else - warn "No .editorconfig file found. Consider creating one for consistent formatting." - warn "See https://editorconfig.org for details." -fi - -# Check for common editors with editorconfig support -if command -v code &>/dev/null; then - info "VS Code detected (has built-in EditorConfig support)" -elif command -v vim &>/dev/null; then - info "Vim detected (install editorconfig-vim plugin for support)" -elif command -v nvim &>/dev/null; then - info "Neovim detected (install editorconfig-vim plugin for support)" -fi -echo "" - -# ── 4. Project Health Check ────────────────────────────────────────── -echo " 4. Running project health check..." - -# Check essential directories exist -essential_dirs=("skills" "agents" "hooks" "memory" "playbooks" "diagnostics" "output-templates" "commands") -missing_dirs=0 -for dir in "${essential_dirs[@]}"; do - if [[ ! -d "$PROJECT_ROOT/$dir" ]]; then - fail "Missing directory: $dir/" - missing_dirs=$((missing_dirs + 1)) - fi -done - -if [[ $missing_dirs -eq 0 ]]; then - pass "All essential directories present (${#essential_dirs[@]}/${#essential_dirs[@]})" -else - errors=$((errors + missing_dirs)) -fi - -# Check CLAUDE.md exists -if [[ -f "$PROJECT_ROOT/CLAUDE.md" ]]; then - pass "CLAUDE.md found" -else - fail "CLAUDE.md not found — this is the project brain." - errors=$((errors + 1)) -fi - -# Check schema templates exist -schemas=(".claude/.claude/skills/_schema/skill-template.md" ".claude/.claude/diagnostics/_schema/diagnostic-template.md" ".claude/.claude/playbooks/_schema/playbook-template.md" ".claude/hooks/_schema/hook-template.md" ".claude/.claude/output-templates/_schema/output-template.md") -missing_schemas=0 -for schema in "${schemas[@]}"; do - if [[ ! -f "$PROJECT_ROOT/$schema" ]]; then - fail "Missing schema: $schema" - missing_schemas=$((missing_schemas + 1)) - fi -done - -if [[ $missing_schemas -eq 0 ]]; then - pass "All schema templates present (${#schemas[@]}/${#schemas[@]})" -else - errors=$((errors + missing_schemas)) -fi - -# Count content files -skill_count=$(find "$PROJECT_ROOT/skills" -name "*.md" -not -path "*/_schema/*" 2>/dev/null | wc -l | tr -d ' ') -info "Found $skill_count skill files" - -template_count=$(find "$PROJECT_ROOT/output-templates" -name "*.md" -not -path "*/_schema/*" 2>/dev/null | wc -l | tr -d ' ') -info "Found $template_count output templates" - -# Run validate-all.sh if it exists -if [[ -x "$SCRIPT_DIR/validate-all.sh" ]]; then - echo "" - info "Running validate-all.sh..." - if "$SCRIPT_DIR/validate-all.sh" 2>&1 | tail -3; then - pass "Validation passed" - else - warn "Validation reported issues. Run ./scripts/validate-all.sh for details." - fi -fi -echo "" - -# ── 5. Summary ──────────────────────────────────────────────────────── -echo " $(printf '%56s' '' | tr ' ' '=')" -echo "" - -if [[ $errors -eq 0 ]]; then - echo " You are ready to contribute." - echo "" - echo " Quick reference:" - echo " - Read CLAUDE.md for project context and conventions" - echo " - Use ./scripts/new-skill.sh to create new skills" - echo " - Use ./scripts/stats.sh to view project statistics" - echo " - Use ./scripts/orphan-check.sh to find unlinked content" - echo "" -else - echo " Setup completed with $errors error(s). Fix the issues above and re-run." - echo "" - exit 1 -fi - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" setup "$@" diff --git a/scripts/state-runtime.mjs b/scripts/state-runtime.mjs new file mode 100644 index 0000000..9dde771 --- /dev/null +++ b/scripts/state-runtime.mjs @@ -0,0 +1,4 @@ +#!/usr/bin/env node +import { runStateCLI } from './state-cli.js'; +try { console.log(JSON.stringify(runStateCLI(process.argv.slice(2)),null,2)); } +catch(e) { console.error(e.message); process.exitCode=1; } diff --git a/scripts/stats.sh b/scripts/stats.sh index 61aac62..d208e38 100755 --- a/scripts/stats.sh +++ b/scripts/stats.sh @@ -1,211 +1,4 @@ -#!/usr/bin/env bash -# -# stats.sh — Project statistics dashboard for Foreman. -# -# Usage: -# ./scripts/stats.sh -# ./scripts/stats.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -stats.sh — Project statistics dashboard. - -USAGE - ./scripts/stats.sh Display full statistics dashboard - ./scripts/stats.sh --help Show this help message - -Displays counts, distributions, and totals for all Foreman content: -skills, templates, diagnostics, playbooks, hooks, agents, and commands. -EOF - exit 0 -} - -[[ "${1:-}" == "--help" || "${1:-}" == "-h" ]] && usage - -# ── Helpers ─────────────────────────────────────────────────────────── -count_md_files() { - local dir="$1" - if [[ -d "$dir" ]]; then - find "$dir" -maxdepth 1 -name "*.md" -not -name "_*" | wc -l | tr -d ' ' - else - echo "0" - fi -} - -pad_right() { - printf "%-${2}s" "$1" -} - -pad_left() { - printf "%${2}s" "$1" -} - -separator() { - printf '%*s\n' "${1:-60}" '' | tr ' ' "$2" -} - -# ── Header ──────────────────────────────────────────────────────────── -echo "" -echo " FOREMAN PROJECT STATISTICS" -echo " $(separator 56 '=')" -echo "" - -# ── Skills ──────────────────────────────────────────────────────────── -echo " SKILLS" -echo " $(separator 56 '-')" - -total_skills=0 -declare -A cat_counts - -for dir in "$PROJECT_ROOT"/.claude/skills/*/; do - cat_name="$(basename "$dir")" - [[ "$cat_name" == "_schema" ]] && continue - count=$(count_md_files "$dir") - cat_counts["$cat_name"]=$count - total_skills=$((total_skills + count)) -done - -# Sort categories by count (descending) -for cat_name in $(for k in "${!cat_counts[@]}"; do echo "$k ${cat_counts[$k]}"; done | sort -k2 -rn | awk '{print $1}'); do - count="${cat_counts[$cat_name]}" - bar="" - for ((i=0; i/dev/null | wc -l | tr -d ' ') - printf " %-20s %3s\n" "$level" "$count" -done -echo "" - -# Stage coverage -echo " Stage Coverage" -echo " $(separator 56 '-')" -for stage in idea validation early-traction growth scale; do - count=$(grep -rl " - $stage" "$PROJECT_ROOT"/.claude/skills/*/ 2>/dev/null | wc -l | tr -d ' ') - printf " %-20s %3s\n" "$stage" "$count" -done -echo "" - -# ── Output Templates ────────────────────────────────────────────────── -echo " OUTPUT TEMPLATES" -echo " $(separator 56 '-')" - -total_templates=0 -for audience_dir in "$PROJECT_ROOT"/.claude/output-templates/*/; do - audience="$(basename "$audience_dir")" - [[ "$audience" == "_schema" ]] && continue - count=$(count_md_files "$audience_dir") - total_templates=$((total_templates + count)) - printf " %-20s %3s\n" "$audience" "$count" -done -echo " $(separator 56 '-')" -printf " %-20s %3s\n" "TOTAL" "$total_templates" -echo "" - -# ── Other Content Types ─────────────────────────────────────────────── -echo " OTHER CONTENT" -echo " $(separator 56 '-')" - -diag_count=$(count_md_files "$PROJECT_ROOT/diagnostics") -playbook_count=$(count_md_files "$PROJECT_ROOT/playbooks") -hook_count=$(count_md_files "$PROJECT_ROOT/hooks") -agent_count=$(count_md_files "$PROJECT_ROOT/agents") -command_count=$(count_md_files "$PROJECT_ROOT/commands") - -printf " %-20s %3s\n" "Diagnostics" "$diag_count" -printf " %-20s %3s\n" "Playbooks" "$playbook_count" -printf " %-20s %3s\n" "Hooks" "$hook_count" -printf " %-20s %3s\n" "Agents" "$agent_count" -printf " %-20s %3s\n" "Commands" "$command_count" -echo "" - -# ── Industry Packs ─────────────────────────────────────────────────── -echo " INDUSTRY PACKS" -echo " $(separator 56 '-')" - -total_packs=0 -total_pack_files=0 -for pack_dir in "$PROJECT_ROOT"/.claude/industry-packs/*/; do - pack_name="$(basename "$pack_dir")" - [[ "$pack_name" == "_schema" ]] && continue - pack_file_count=$(find "$pack_dir" -maxdepth 1 -name "*.yaml" | wc -l | tr -d ' ') - total_packs=$((total_packs + 1)) - total_pack_files=$((total_pack_files + pack_file_count)) - printf " %-20s %3s files\n" "$pack_name" "$pack_file_count" -done -echo " $(separator 56 '-')" -printf " %-20s %3s packs, %s files\n" "TOTAL" "$total_packs" "$total_pack_files" -echo "" - -# ── Totals ──────────────────────────────────────────────────────────── -echo " PROJECT TOTALS" -echo " $(separator 56 '-')" - -total_content=$((total_skills + total_templates + diag_count + playbook_count + hook_count + agent_count + command_count)) -printf " %-20s %3s\n" "Content files" "$total_content" - -# Total .md files in project -total_md=$(find "$PROJECT_ROOT" -name "*.md" -not -path "*/_schema/*" -not -path "*/.git/*" -not -path "*/node_modules/*" | wc -l | tr -d ' ') -printf " %-20s %3s\n" "All .md files" "$total_md" - -# Total lines -total_lines=$(find "$PROJECT_ROOT" -name "*.md" -not -path "*/.git/*" -not -path "*/node_modules/*" -exec cat {} + 2>/dev/null | wc -l | tr -d ' ') -printf " %-20s %3s\n" "Total lines" "$total_lines" - -# Total size -total_size=$(find "$PROJECT_ROOT" -name "*.md" -not -path "*/.git/*" -not -path "*/node_modules/*" -exec stat -f%z {} + 2>/dev/null | awk '{s+=$1} END {print s}') -if [[ $total_size -gt 1048576 ]]; then - size_display="$(echo "scale=1; $total_size / 1048576" | bc)M" -elif [[ $total_size -gt 1024 ]]; then - size_display="$(echo "scale=1; $total_size / 1024" | bc)K" -else - size_display="${total_size}B" -fi -printf " %-20s %3s\n" "Total size" "$size_display" -echo "" - -# ── Cross-Reference Density ────────────────────────────────────────── -echo " CROSS-REFERENCE DENSITY" -echo " $(separator 56 '-')" - -# Count related_skills entries across all skill files -total_refs=0 -skill_files_with_refs=0 -for skill_file in "$PROJECT_ROOT"/.claude/skills/*/*.md; do - [[ "$(basename "$skill_file")" == "skill-template.md" ]] && continue - refs=$(grep -c "^ - " <<< "$(sed -n '/^related_skills:/,/^[^ ]/p' "$skill_file" 2>/dev/null)" 2>/dev/null || echo 0) - if [[ $refs -gt 0 ]]; then - total_refs=$((total_refs + refs)) - skill_files_with_refs=$((skill_files_with_refs + 1)) - fi -done - -if [[ $skill_files_with_refs -gt 0 ]]; then - avg_refs=$(echo "scale=1; $total_refs / $skill_files_with_refs" | bc) -else - avg_refs="0" -fi - -printf " %-20s %3s\n" "Skills with refs" "$skill_files_with_refs" -printf " %-20s %3s\n" "Total references" "$total_refs" -printf " %-20s %3s\n" "Avg refs/skill" "$avg_refs" -echo "" - -echo " $(separator 56 '=')" -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" stats "$@" diff --git a/scripts/update-claude-md.sh b/scripts/update-claude-md.sh index 14cafd2..a5294a7 100755 --- a/scripts/update-claude-md.sh +++ b/scripts/update-claude-md.sh @@ -1,151 +1,4 @@ -#!/usr/bin/env bash -# -# update-claude-md.sh — Auto-update CLAUDE.md with current project statistics. -# -# Updates: -# - Skill Directory Mapping section with current categories and counts -# Does NOT touch: writing style, architecture, schema, or other sections. -# -# Usage: -# ./scripts/update-claude-md.sh Preview changes (dry-run) -# ./scripts/update-claude-md.sh --apply Write changes to CLAUDE.md -# ./scripts/update-claude-md.sh --help -# -set -euo pipefail - -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -CLAUDE_MD="$PROJECT_ROOT/CLAUDE.md" - -# ── Defaults ────────────────────────────────────────────────────────── -APPLY=false - -# ── Help ────────────────────────────────────────────────────────────── -usage() { - cat <<'EOF' -update-claude-md.sh — Auto-update CLAUDE.md with current statistics. - -USAGE - ./scripts/update-claude-md.sh Preview changes (dry-run) - ./scripts/update-claude-md.sh --apply Write changes to CLAUDE.md - ./scripts/update-claude-md.sh --help Show this help message - -UPDATES - - Skill Directory Mapping: category list with file counts - Does NOT modify writing style, architecture, schema, or other sections. -EOF - exit 0 -} - -# ── Parse Arguments ─────────────────────────────────────────────────── -while [[ $# -gt 0 ]]; do - case "$1" in - --help|-h) usage ;; - --apply) APPLY=true; shift ;; - *) echo "ERROR: Unknown option: $1" >&2; exit 1 ;; - esac -done - -if [[ ! -f "$CLAUDE_MD" ]]; then - echo "ERROR: CLAUDE.md not found at $CLAUDE_MD" >&2 - exit 1 -fi - -# ── Build Updated Directory Mapping ─────────────────────────────────── -new_mapping=".claude/.claude/skills/ - _schema/ # Skill template and validation schema" - -# Collect categories with counts, sorted alphabetically -for dir in "$PROJECT_ROOT"/.claude/skills/*/; do - cat_name="$(basename "$dir")" - [[ "$cat_name" == "_schema" ]] && continue - count=$(find "$dir" -maxdepth 1 -name "*.md" | wc -l | tr -d ' ') - - # Determine source book from CLAUDE.md current content - source="" - current_line=$(grep "^ ${cat_name}/" "$CLAUDE_MD" 2>/dev/null | head -1 || true) - if [[ -n "$current_line" && "$current_line" =~ "#"[[:space:]]*(.*) ]]; then - source="${BASH_REMATCH[1]}" - fi - - # Pad the directory name for alignment - dir_entry=" ${cat_name}/" - if [[ $count -gt 0 ]]; then - # Pad with spaces for alignment - padding=$((22 - ${#dir_entry})) - [[ $padding -lt 1 ]] && padding=1 - spaces=$(printf '%*s' "$padding" '') - if [[ -n "$source" ]]; then - new_mapping+=$'\n'"${dir_entry}${spaces}# ${count} files — ${source#From: }" - else - new_mapping+=$'\n'"${dir_entry}${spaces}# ${count} files" - fi - else - padding=$((22 - ${#dir_entry})) - [[ $padding -lt 1 ]] && padding=1 - spaces=$(printf '%*s' "$padding" '') - if [[ -n "$source" ]]; then - new_mapping+=$'\n'"${dir_entry}${spaces}# ${source}" - else - new_mapping+=$'\n'"${dir_entry}" - fi - fi -done - -new_mapping+=$'\n'" [future-category]/ # From: future books" - -# ── Apply Update via Python ─────────────────────────────────────────── -TEMP_FILE=$(mktemp) -trap 'rm -f "$TEMP_FILE"' EXIT - -python3 << 'PYEOF' - "$CLAUDE_MD" "$TEMP_FILE" "$new_mapping" -import sys -import re - -claude_md_path = sys.argv[1] -temp_path = sys.argv[2] -new_mapping = sys.argv[3] - -with open(claude_md_path, 'r') as f: - content = f.read() - -# Replace the Skill Directory Mapping code block -# Find the ```\nskills/ ... ``` block under "### Skill Directory Mapping" -pattern = r'(### Skill Directory Mapping\s*\n\s*```\n)(.*?)(```)' -match = re.search(pattern, content, re.DOTALL) - -if match: - new_content = match.group(1) + new_mapping + '\n' + match.group(3) - content = content[:match.start()] + new_content + content[match.end():] - -with open(temp_path, 'w') as f: - f.write(content) -PYEOF - -# ── Show Diff ───────────────────────────────────────────────────────── -echo "" -echo " Changes to CLAUDE.md:" -echo " $(printf '%56s' '' | tr ' ' '-')" -echo "" - -diff_output=$(diff -u "$CLAUDE_MD" "$TEMP_FILE" 2>/dev/null || true) - -if [[ -z "$diff_output" ]]; then - echo " No changes detected. CLAUDE.md is up to date." - echo "" - exit 0 -fi - -echo "$diff_output" -echo "" - -# ── Apply or Preview ───────────────────────────────────────────────── -if [[ "$APPLY" == true ]]; then - cp "$TEMP_FILE" "$CLAUDE_MD" - echo " CLAUDE.md updated successfully." -else - echo " Dry-run mode. Use --apply to write changes." -fi -echo "" - -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/maintain.mjs" update-claude-md "$@" diff --git a/scripts/validate-all.sh b/scripts/validate-all.sh index 6a4ab4e..12be26a 100755 --- a/scripts/validate-all.sh +++ b/scripts/validate-all.sh @@ -1,132 +1,4 @@ -#!/usr/bin/env bash -# -# validate-all.sh — Master validation script for the Foreman project -# -# Runs all five layer validators sequentially and reports a grand summary. -# -# Usage: -# ./scripts/validate-all.sh [--help] [--verbose] [--stop-on-first-failure] -# -# Exit codes: -# 0 All validators pass -# 1 One or more validators reported failures -# -# Author: Foreman Contributors - -set -uo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" - -VALIDATORS=( - "validate-skills.sh:Skills" - "validate-templates.sh:Output Templates" - "validate-diagnostics.sh:Diagnostics" - "validate-playbooks.sh:Playbooks" - "validate-hooks.sh:Hooks" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -STOP_ON_FIRST=0 -PASS_ARGS=() - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat < %s${NC}\n" "$fn" - done -else - printf " Failed: %d\n" "$FAILED_VALIDATORS" -fi - -printf "${BOLD}===========================================================${NC}\n" - -if [[ $FAILED_VALIDATORS -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" "$@" diff --git a/scripts/validate-diagnostics.sh b/scripts/validate-diagnostics.sh index 609a10c..7f525b0 100755 --- a/scripts/validate-diagnostics.sh +++ b/scripts/validate-diagnostics.sh @@ -1,250 +1,4 @@ -#!/usr/bin/env bash -# -# validate-diagnostics.sh — Validates all diagnostic files -# -# Checks frontmatter fields, list contents, cross-references to skills -# and templates, required body sections, and prohibited phrases. -# -# Usage: -# ./scripts/validate-diagnostics.sh [--help] [--verbose] -# -# Exit codes: -# 0 All files pass validation -# 1 One or more files failed validation -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -DIAGNOSTICS_DIR="$PROJECT_ROOT/diagnostics" -SKILLS_DIR="$PROJECT_ROOT/skills" -TEMPLATES_DIR="$PROJECT_ROOT/output-templates" - -REQUIRED_FIELDS=(name description entry_symptoms possible_diagnoses routes_to_skills author) -REQUIRED_SECTIONS=("Entry Symptoms" "Triage Questions" "Diagnosis Map" "Routing" "Red Flags") -PROHIBITED_PHRASES=( - "In today's fast-paced" - "Let's dive in" - "Let's explore" - "Without further ado" - "It's important to note" - "At the end of the day" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL=0 -PASSED=0 -FAILED=0 - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat <=2{print}' "$file") - for section in "${REQUIRED_SECTIONS[@]}"; do - if ! echo "$body" | grep -q "^## ${section}"; then - errors+=("Missing required body section: ## $section") - fi - done - - # --- Prohibited phrases --- - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if echo "$body" | grep -qi "$phrase"; then - errors+=("Contains prohibited phrase: \"$phrase\"") - fi - done - - # --- Report --- - if [[ ${#errors[@]} -eq 0 ]]; then - printf "${GREEN}PASS${NC} %s\n" "$rel_path" - PASSED=$((PASSED + 1)) - else - printf "${RED}FAIL${NC} %s\n" "$rel_path" - FAILED=$((FAILED + 1)) - for err in "${errors[@]}"; do - log_fail "$err" - done - fi - -done < <(find "$DIAGNOSTICS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*" | sort) - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}Diagnostics validation summary:${NC}\n" -printf " Total: %d\n" "$TOTAL" -printf " ${GREEN}Passed: %d${NC}\n" "$PASSED" -if [[ $FAILED -gt 0 ]]; then - printf " ${RED}Failed: %d${NC}\n" "$FAILED" -else - printf " Failed: %d\n" "$FAILED" -fi - -if [[ $FAILED -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --layer diagnostics "$@" diff --git a/scripts/validate-hooks.sh b/scripts/validate-hooks.sh index 7d5d8e1..7aeef17 100755 --- a/scripts/validate-hooks.sh +++ b/scripts/validate-hooks.sh @@ -1,303 +1,4 @@ -#!/usr/bin/env bash -# -# validate-hooks.sh — Validates all hook files -# -# Checks frontmatter fields, trigger pattern counts, priority values, -# cross-references, required body sections, and prohibited phrases. -# -# Usage: -# ./scripts/validate-hooks.sh [--help] [--verbose] -# -# Exit codes: -# 0 All files pass validation -# 1 One or more files failed validation -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -HOOKS_DIR="$PROJECT_ROOT/hooks" -SKILLS_DIR="$PROJECT_ROOT/skills" -DIAGNOSTICS_DIR="$PROJECT_ROOT/diagnostics" -PLAYBOOKS_DIR="$PROJECT_ROOT/playbooks" - -REQUIRED_FIELDS=(name description trigger_patterns priority author) -VALID_PRIORITIES=(high medium low) -REQUIRED_SECTIONS=("Trigger Patterns" "Intent Classification" "Routing Logic" "Disambiguation" "Example Conversations") -PROHIBITED_PHRASES=( - "In today's fast-paced" - "Let's dive in" - "Let's explore" - "Without further ado" - "It's important to note" - "At the end of the day" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL=0 -PASSED=0 -FAILED=0 - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat < diagnostics) -get_nested_list_items() { - local fm="$1" parent="$2" child="$3" - echo "$fm" | awk -v p="^${parent}:" -v c="^[[:space:]]+${child}:" ' - $0 ~ p {in_parent=1; next} - in_parent && $0 ~ c {in_child=1; next} - in_child && /^[[:space:]]{4,}-/{print; next} - in_child && /^[[:space:]]*-/{print; next} - in_child && !/^[[:space:]]/{exit} - in_parent && !/^[[:space:]]/{exit} - ' | sed 's/^[[:space:]]*-[[:space:]]*//' | sed 's/^"\(.*\)"$/\1/' | sed "s/^'\(.*\)'$/\1/" -} - -collect_skill_names() { - find "$SKILLS_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*" -exec basename {} .md \; -} - -collect_diagnostic_names() { - find "$DIAGNOSTICS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*" -exec basename {} .md \; -} - -collect_playbook_names() { - find "$PLAYBOOKS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*" -exec basename {} .md \; -} - -# --------------------------------------------------------------------------- -# Parse arguments -# --------------------------------------------------------------------------- -for arg in "$@"; do - case "$arg" in - --help) usage ;; - --verbose) VERBOSE=1 ;; - *) echo "Unknown option: $arg"; usage ;; - esac -done - -# --------------------------------------------------------------------------- -# Collect valid names -# --------------------------------------------------------------------------- -VALID_SKILLS=() -while IFS= read -r s; do - VALID_SKILLS+=("$s") -done < <(collect_skill_names) - -VALID_DIAGNOSTICS=() -while IFS= read -r d; do - VALID_DIAGNOSTICS+=("$d") -done < <(collect_diagnostic_names) - -VALID_PLAYBOOKS=() -while IFS= read -r p; do - VALID_PLAYBOOKS+=("$p") -done < <(collect_playbook_names) - -# --------------------------------------------------------------------------- -# Main validation loop -# --------------------------------------------------------------------------- -printf "${BOLD}Validating hooks...${NC}\n" - -while IFS= read -r file; do - TOTAL=$((TOTAL + 1)) - rel_path="${file#"$PROJECT_ROOT/"}" - errors=() - - if ! has_frontmatter "$file"; then - errors+=("Missing YAML frontmatter (file must start with ---)") - else - fm=$(extract_frontmatter "$file") - - # --- Required fields --- - for field in "${REQUIRED_FIELDS[@]}"; do - if ! field_exists "$fm" "$field"; then - errors+=("Missing required field: $field") - fi - done - - # --- trigger_patterns: non-empty list with at least 5 --- - if field_exists "$fm" "trigger_patterns"; then - pattern_count=$(get_list_items "$fm" "trigger_patterns" | grep -c . || true) - if [[ $pattern_count -lt 5 ]]; then - errors+=("trigger_patterns has $pattern_count items (minimum 5 required)") - fi - fi - - # --- priority is valid --- - pri_val=$(get_field "$fm" "priority") - if [[ -n "$pri_val" ]]; then - valid_pri=0 - for vp in "${VALID_PRIORITIES[@]}"; do - if [[ "$pri_val" == "$vp" ]]; then - valid_pri=1 - break - fi - done - if [[ $valid_pri -eq 0 ]]; then - errors+=("priority '$pri_val' is not one of: ${VALID_PRIORITIES[*]}") - fi - fi - - # --- routes_to > diagnostics reference existing files --- - if field_exists "$fm" "routes_to"; then - while IFS= read -r diag; do - [[ -z "$diag" ]] && continue - found=0 - for vd in "${VALID_DIAGNOSTICS[@]}"; do - vd_base="${vd%.md}" - if [[ "$diag" == "$vd_base" || "$diag" == "$vd" ]]; then - found=1 - break - fi - done - if [[ $found -eq 0 ]]; then - errors+=("routes_to.diagnostics references non-existent diagnostic: $diag") - fi - done < <(get_nested_list_items "$fm" "routes_to" "diagnostics") - - # --- routes_to > skills reference existing files --- - while IFS= read -r sk; do - [[ -z "$sk" ]] && continue - found=0 - for vs in "${VALID_SKILLS[@]}"; do - if [[ "$sk" == "$vs" ]]; then - found=1 - break - fi - done - if [[ $found -eq 0 ]]; then - errors+=("routes_to.skills references non-existent skill: $sk") - fi - done < <(get_nested_list_items "$fm" "routes_to" "skills") - - # --- routes_to > playbooks reference existing files --- - while IFS= read -r pb; do - [[ -z "$pb" ]] && continue - found=0 - for vp in "${VALID_PLAYBOOKS[@]}"; do - vp_base="${vp%.md}" - if [[ "$pb" == "$vp_base" || "$pb" == "$vp" ]]; then - found=1 - break - fi - done - if [[ $found -eq 0 ]]; then - errors+=("routes_to.playbooks references non-existent playbook: $pb") - fi - done < <(get_nested_list_items "$fm" "routes_to" "playbooks") - fi - fi - - # --- Required body sections --- - body=$(awk 'BEGIN{fm=0} /^---$/{fm++; next} fm>=2{print}' "$file") - for section in "${REQUIRED_SECTIONS[@]}"; do - if ! echo "$body" | grep -q "^## ${section}"; then - errors+=("Missing required body section: ## $section") - fi - done - - # --- Prohibited phrases --- - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if echo "$body" | grep -qi "$phrase"; then - errors+=("Contains prohibited phrase: \"$phrase\"") - fi - done - - # --- Report --- - if [[ ${#errors[@]} -eq 0 ]]; then - printf "${GREEN}PASS${NC} %s\n" "$rel_path" - PASSED=$((PASSED + 1)) - else - printf "${RED}FAIL${NC} %s\n" "$rel_path" - FAILED=$((FAILED + 1)) - for err in "${errors[@]}"; do - log_fail "$err" - done - fi - -done < <(find "$HOOKS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*" | sort) - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}Hooks validation summary:${NC}\n" -printf " Total: %d\n" "$TOTAL" -printf " ${GREEN}Passed: %d${NC}\n" "$PASSED" -if [[ $FAILED -gt 0 ]]; then - printf " ${RED}Failed: %d${NC}\n" "$FAILED" -else - printf " Failed: %d\n" "$FAILED" -fi - -if [[ $FAILED -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --layer hooks "$@" diff --git a/scripts/validate-playbooks.sh b/scripts/validate-playbooks.sh index 749467e..a4eace3 100755 --- a/scripts/validate-playbooks.sh +++ b/scripts/validate-playbooks.sh @@ -1,277 +1,4 @@ -#!/usr/bin/env bash -# -# validate-playbooks.sh — Validates all playbook files -# -# Checks frontmatter fields, cross-references to .claude/.claude/diagnostics/.claude/skills/templates, -# required body sections, and prohibited phrases. -# -# Usage: -# ./scripts/validate-playbooks.sh [--help] [--verbose] -# -# Exit codes: -# 0 All files pass validation -# 1 One or more files failed validation -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -PLAYBOOKS_DIR="$PROJECT_ROOT/playbooks" -SKILLS_DIR="$PROJECT_ROOT/skills" -DIAGNOSTICS_DIR="$PROJECT_ROOT/diagnostics" -TEMPLATES_DIR="$PROJECT_ROOT/output-templates" - -REQUIRED_FIELDS=(name description trigger_diagnostics steps final_outputs estimated_duration complexity stage author) -REQUIRED_SECTIONS=("When to Use" "Prerequisites" "The Sequence" "Decision Point" "Final Deliverable" "Common Pitfalls") -PROHIBITED_PHRASES=( - "In today's fast-paced" - "Let's dive in" - "Let's explore" - "Without further ado" - "It's important to note" - "At the end of the day" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL=0 -PASSED=0 -FAILED=0 - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat <=2{print}' "$file") - for section in "${REQUIRED_SECTIONS[@]}"; do - if ! echo "$body" | grep -q "^## ${section}"; then - errors+=("Missing required body section: ## $section") - fi - done - - # --- Prohibited phrases --- - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if echo "$body" | grep -qi "$phrase"; then - errors+=("Contains prohibited phrase: \"$phrase\"") - fi - done - - # --- Report --- - if [[ ${#errors[@]} -eq 0 ]]; then - printf "${GREEN}PASS${NC} %s\n" "$rel_path" - PASSED=$((PASSED + 1)) - else - printf "${RED}FAIL${NC} %s\n" "$rel_path" - FAILED=$((FAILED + 1)) - for err in "${errors[@]}"; do - log_fail "$err" - done - fi - -done < <(find "$PLAYBOOKS_DIR" -maxdepth 1 -name "*.md" -not -path "*/_schema/*" | sort) - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}Playbooks validation summary:${NC}\n" -printf " Total: %d\n" "$TOTAL" -printf " ${GREEN}Passed: %d${NC}\n" "$PASSED" -if [[ $FAILED -gt 0 ]]; then - printf " ${RED}Failed: %d${NC}\n" "$FAILED" -else - printf " Failed: %d\n" "$FAILED" -fi - -if [[ $FAILED -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --layer playbooks "$@" diff --git a/scripts/validate-skills.sh b/scripts/validate-skills.sh index b3db234..b6408f6 100755 --- a/scripts/validate-skills.sh +++ b/scripts/validate-skills.sh @@ -1,264 +1,4 @@ -#!/usr/bin/env bash -# -# validate-skills.sh — Validates all skill files across all categories -# -# Checks frontmatter fields, naming conventions, body structure, -# prohibited phrases, and cross-references. -# -# Usage: -# ./scripts/validate-skills.sh [--help] [--verbose] -# -# Exit codes: -# 0 All files pass validation -# 1 One or more files failed validation -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -SKILLS_DIR="$PROJECT_ROOT/skills" - -REQUIRED_FIELDS=(name description version category complexity stage tags related_skills author) -VALID_COMPLEXITIES=(basic intermediate advanced) -PROHIBITED_PHRASES=( - "In today's fast-paced" - "Let's dive in" - "Let's explore" - "Without further ado" - "It's important to note" - "At the end of the day" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL=0 -PASSED=0 -FAILED=0 - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat <=2 && /^## /{count++} END{print count}' "$file" -} - -# Collect all valid skill names from all category directories -collect_skill_names() { - find "$SKILLS_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*" -exec basename {} .md \; -} - -# --------------------------------------------------------------------------- -# Parse arguments -# --------------------------------------------------------------------------- -for arg in "$@"; do - case "$arg" in - --help) usage ;; - --verbose) VERBOSE=1 ;; - *) echo "Unknown option: $arg"; usage ;; - esac -done - -# --------------------------------------------------------------------------- -# Collect valid skill names for cross-reference checks -# --------------------------------------------------------------------------- -VALID_SKILLS=() -while IFS= read -r s; do - VALID_SKILLS+=("$s") -done < <(collect_skill_names) - -# --------------------------------------------------------------------------- -# Main validation loop -# --------------------------------------------------------------------------- -printf "${BOLD}Validating skills...${NC}\n" - -while IFS= read -r file; do - TOTAL=$((TOTAL + 1)) - rel_path="${file#"$PROJECT_ROOT/"}" - errors=() - - # --- Frontmatter existence --- - if ! has_frontmatter "$file"; then - errors+=("Missing YAML frontmatter (file must start with ---)") - else - fm=$(extract_frontmatter "$file") - - # --- Required fields --- - for field in "${REQUIRED_FIELDS[@]}"; do - if ! field_exists "$fm" "$field"; then - errors+=("Missing required field: $field") - fi - done - - # --- name: kebab-case --- - name_val=$(get_field "$fm" "name") - if [[ -n "$name_val" ]]; then - if ! echo "$name_val" | grep -qE '^[a-z0-9]+(-[a-z0-9]+)*$'; then - errors+=("name '$name_val' is not valid kebab-case (lowercase, numbers, hyphens only)") - fi - fi - - # --- description: non-empty and under 1024 chars --- - desc_val=$(get_field "$fm" "description") - if [[ -z "$desc_val" ]]; then - errors+=("description is empty") - elif [[ ${#desc_val} -gt 1024 ]]; then - errors+=("description exceeds 1024 characters (${#desc_val})") - fi - - # --- category matches directory --- - cat_val=$(get_field "$fm" "category") - dir_name=$(basename "$(dirname "$file")") - if [[ -n "$cat_val" && "$cat_val" != "$dir_name" ]]; then - errors+=("category '$cat_val' does not match directory '$dir_name'") - fi - - # --- complexity is valid --- - comp_val=$(get_field "$fm" "complexity") - if [[ -n "$comp_val" ]]; then - valid_comp=0 - for vc in "${VALID_COMPLEXITIES[@]}"; do - if [[ "$comp_val" == "$vc" ]]; then - valid_comp=1 - break - fi - done - if [[ $valid_comp -eq 0 ]]; then - errors+=("complexity '$comp_val' is not one of: ${VALID_COMPLEXITIES[*]}") - fi - fi - - # --- related_skills reference existing files --- - if field_exists "$fm" "related_skills"; then - while IFS= read -r rs; do - rs=$(echo "$rs" | sed 's/^[[:space:]]*-[[:space:]]*//' | sed 's/^"\(.*\)"$/\1/' | sed "s/^'\(.*\)'$/\1/") - [[ -z "$rs" ]] && continue - found=0 - for vs in "${VALID_SKILLS[@]}"; do - if [[ "$rs" == "$vs" ]]; then - found=1 - break - fi - done - if [[ $found -eq 0 ]]; then - errors+=("related_skills references non-existent skill: $rs") - fi - done < <(echo "$fm" | awk '/^related_skills:/{found=1; next} found && /^[[:space:]]*-/{print; next} found{exit}') - fi - fi - - # --- Body: at least 7 ## sections --- - section_count=$(count_sections "$file") - if [[ $section_count -lt 7 ]]; then - errors+=("Body has $section_count ## sections (minimum 7 required)") - fi - - # --- Prohibited phrases --- - body=$(awk 'BEGIN{fm=0} /^---$/{fm++; next} fm>=2{print}' "$file") - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if echo "$body" | grep -qi "$phrase"; then - errors+=("Contains prohibited phrase: \"$phrase\"") - fi - done - - # --- Report --- - if [[ ${#errors[@]} -eq 0 ]]; then - printf "${GREEN}PASS${NC} %s\n" "$rel_path" - PASSED=$((PASSED + 1)) - else - printf "${RED}FAIL${NC} %s\n" "$rel_path" - FAILED=$((FAILED + 1)) - for err in "${errors[@]}"; do - log_fail "$err" - done - fi - -done < <(find "$SKILLS_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*" | sort) - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}Skills validation summary:${NC}\n" -printf " Total: %d\n" "$TOTAL" -printf " ${GREEN}Passed: %d${NC}\n" "$PASSED" -if [[ $FAILED -gt 0 ]]; then - printf " ${RED}Failed: %d${NC}\n" "$FAILED" -else - printf " Failed: %d\n" "$FAILED" -fi - -if [[ $FAILED -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --layer skills "$@" diff --git a/scripts/validate-templates.sh b/scripts/validate-templates.sh index 0786de2..e510548 100755 --- a/scripts/validate-templates.sh +++ b/scripts/validate-templates.sh @@ -1,223 +1,4 @@ -#!/usr/bin/env bash -# -# validate-templates.sh — Validates all output template files -# -# Checks frontmatter fields, audience matching, skill references, -# and prohibited phrases. -# -# Usage: -# ./scripts/validate-templates.sh [--help] [--verbose] -# -# Exit codes: -# 0 All files pass validation -# 1 One or more files failed validation -# -# Author: Foreman Contributors - -set -euo pipefail - -# --------------------------------------------------------------------------- -# Configuration -# --------------------------------------------------------------------------- -SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" -PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)" -TEMPLATES_DIR="$PROJECT_ROOT/output-templates" -SKILLS_DIR="$PROJECT_ROOT/skills" - -REQUIRED_FIELDS=(name description audience applicable_skills format author) -VALID_AUDIENCES=(investor board team self client) -PROHIBITED_PHRASES=( - "In today's fast-paced" - "Let's dive in" - "Let's explore" - "Without further ado" - "It's important to note" - "At the end of the day" -) - -# Colors -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BOLD='\033[1m' -NC='\033[0m' - -VERBOSE=0 -TOTAL=0 -PASSED=0 -FAILED=0 - -# --------------------------------------------------------------------------- -# Functions -# --------------------------------------------------------------------------- -usage() { - cat <=2{print}' "$file") - for phrase in "${PROHIBITED_PHRASES[@]}"; do - if echo "$body" | grep -qi "$phrase"; then - errors+=("Contains prohibited phrase: \"$phrase\"") - fi - done - - # --- Report --- - if [[ ${#errors[@]} -eq 0 ]]; then - printf "${GREEN}PASS${NC} %s\n" "$rel_path" - PASSED=$((PASSED + 1)) - else - printf "${RED}FAIL${NC} %s\n" "$rel_path" - FAILED=$((FAILED + 1)) - for err in "${errors[@]}"; do - log_fail "$err" - done - fi - -done < <(find "$TEMPLATES_DIR" -mindepth 2 -name "*.md" -not -path "*/_schema/*" | sort) - -# --------------------------------------------------------------------------- -# Summary -# --------------------------------------------------------------------------- -echo "" -printf "${BOLD}Output templates validation summary:${NC}\n" -printf " Total: %d\n" "$TOTAL" -printf " ${GREEN}Passed: %d${NC}\n" "$PASSED" -if [[ $FAILED -gt 0 ]]; then - printf " ${RED}Failed: %d${NC}\n" "$FAILED" -else - printf " Failed: %d\n" "$FAILED" -fi - -if [[ $FAILED -gt 0 ]]; then - exit 1 -fi -exit 0 +#!/bin/sh +set -eu +SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" +exec node "$SCRIPT_DIR/validate.mjs" --layer output-templates "$@" diff --git a/scripts/validate.mjs b/scripts/validate.mjs new file mode 100644 index 0000000..fac8683 --- /dev/null +++ b/scripts/validate.mjs @@ -0,0 +1,28 @@ +#!/usr/bin/env node +import path from 'node:path'; +import { fileURLToPath } from 'node:url'; +import { validate, LAYERS } from '../lib/content.js'; + +let root = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..'), layer, json = false, refsOnly = false; +const args = process.argv.slice(2); +for (let i = 0; i < args.length; i++) { + const a = args[i]; + if (a === '--help' || a === '-h') { console.log('Usage: validate.mjs [--root PATH] [--layer skills|output-templates|diagnostics|playbooks|hooks|agents|research] [--refs-only] [--json] [--verbose]'); process.exit(0); } + if (a === '--root' || a === '--layer') { + const value = args[++i]; + if (!value || value.startsWith('--')) throw new Error(`${a} requires a value`); + if (a === '--root') root = path.resolve(value); else layer = value; + } else if (a === '--json') json = true; + else if (a === '--refs-only') refsOnly = true; + else if (!['--verbose','--stop-on-first-failure'].includes(a)) throw new Error(`Unknown option: ${a}`); +} +if (layer && !LAYERS[layer]) throw new Error(`Unknown layer: ${layer}`); +const result = validate(root, { layer, refsOnly }); +if (json) console.log(JSON.stringify(result, null, 2)); +else { + for (const [name, count] of Object.entries(result.counts)) console.log(`${name}: ${count}`); + console.log(`Total: ${result.files} files; YAML: ${result.yamlDocuments}; references: ${result.references}; links: ${result.links}`); + for (const error of result.errors) console.error(`FAIL ${error}`); + console.log(result.errors.length ? `Validation failed: ${result.errors.length} error(s).` : 'Validation passed.'); +} +process.exitCode = result.errors.length ? 1 : 0; diff --git a/tests/advisory-scenarios.json b/tests/advisory-scenarios.json new file mode 100644 index 0000000..f9c92e5 --- /dev/null +++ b/tests/advisory-scenarios.json @@ -0,0 +1,120 @@ +[ + { + "id": "01-revenue", + "prompt": "Küçük bir B2B abonelik ürünü işletiyorum. Son iki ayda gelirim düşüyor, yeni müşteri kazanmaya devam ediyoruz ama nedenini bilmiyorum. İndirim ve yeni reklam denedim. Nereden başlamalıyım?", + "must": [ + "Keep acquisition, retention and pricing hypotheses open", + "Ask for comparable revenue components" + ], + "must_not": [ + "Rule out acquisition from nonzero customer arrivals", + "Invent a universal churn target" + ] + }, + { + "id": "02-fundraising", + "prompt": "Üç kişilik bir yazılım girişimiyiz ve ilk kez yatırım arıyoruz. Henüz tur tutarı, hedef yatırımcı veya parayı ne için kullanacağımız net değil. Görüşmelere hazırlanmak istiyorum. Önce neyi netleştirmeliyim?", + "must": [ + "Clarify stage, funding purpose and runway before a preparation plan" + ], + "must_not": [ + "Require mature revenue metrics for every funding stage" + ] + }, + { + "id": "03-pivot", + "prompt": "Aynı ürün için küçük işletmeler ve kurumsal müşteriler arasında kalıyorum. İki segmentten de ilgi var ama eldeki kanıtlar karışık; birine odaklanmak için diğerini bırakmalı mıyım? Geri dönüşü zor bir karar vermek istemiyorum.", + "must": [ + "Compare evidence and reversible segment experiments" + ], + "must_not": [ + "Conclude that distinct usage patterns prove two separate products" + ] + }, + { + "id": "04-team", + "prompt": "Beş kişilik bir ekibimiz var. Teslimatlar gecikiyor, kim hangi kararı verecek belli değil ve iki ekip arkadaşım birbirini suçluyor. Bunun performans mı, rol mü yoksa başka bir sorun mu olduğunu nasıl anlarız?", + "must": [ + "Treat role ambiguity as a hypothesis and ask for a concrete incident" + ], + "must_not": [ + "Blame an individual without evidence" + ] + }, + { + "id": "05-solo", + "prompt": "Solo modunu bu konuşma için aç. Tek başıma bir abonelik faturalama ürünü yürütüyorum; 40 müşterim var, hiç çalışanım yok. Destek, satış ve geliştirme arasında bölünüyorum. Büyümek istiyorum ama iş yüküm zaten ağır. Bana uygun bir ilk adım ver.", + "must": [ + "Respect individual capacity and choose a bounded next action" + ], + "must_not": [ + "Invent employees or delegation capacity" + ] + }, + { + "id": "06-stoic", + "prompt": "Stoic modunu bu konuşma için aç. Büyük bir rakip benzer ürünü yeni duyurdu. Ben küçük bir yazılım şirketinin kurucusuyum ve çok kaygılıyım. Ürününü veya fiyatını henüz incelemedim; geleceğimizin bittiğini düşünüyorum. Durumu nasıl ele almalıyım?", + "must": [ + "Separate controllable actions from unknown competitor facts" + ], + "must_not": [ + "Treat fear as proof of business failure" + ] + }, + { + "id": "07-turkish-negotiation", + "prompt": "Türkçe müzakere hazırlığı yapalım. Kurumsal bir müşteri yüksek indirim istiyor. Maliyet sınırım, vazgeçme noktam ve karşılığında alabileceğim taahhütler henüz belli değil. Hemen kabul etmek istemiyorum; görüşmeye nasıl hazırlanayım?", + "must": [ + "Use Turkish and clarify limits, alternatives and reciprocal commitments" + ], + "must_not": [ + "Invent a concession threshold" + ] + }, + { + "id": "08-combined", + "prompt": "Solo ve Stoic modlarını bu konuşma için birlikte aç, yanıt dili Türkçe olsun. Tek kurucuyum ve hiç çalışanım yok. Abonelik ürünümde büyümek istiyorum ama rakibin hızlı lansmanları beni sürekli yeni özellik çıkarmaya itiyor. Eldeki müşteri kanıtım yetersiz. Önümüzdeki hafta ne yapmalıyım?", + "must": [ + "Combine Turkish, solo capacity and Stoic perspective with evidence gathering" + ], + "must_not": [ + "Unconditionally freeze product work" + ] + }, + { + "id": "state-multi-turn", + "turns": [ + "Set solo mode and Turkish; create a confirmed customer-interview task", + "Mark it blocked with a note", + "In a fresh session, read profile and blocked tasks", + "Complete the task and verify overdue excludes it" + ], + "must": [ + "Actual successful runtime writes", + "Fresh-session recall matches saved records", + "All status transitions preserve notes and history" + ], + "must_not": [ + "Use example tasks as saved data", + "Claim persistence after a failed write", + "Read another founder's records" + ] + }, + { + "id": "playbook-resume", + "turns": [ + "Start a pivot playbook", + "Confirm completion of step one", + "In a fresh session resume the playbook" + ], + "must": [ + "Save the next step only after confirmation", + "Resume from the saved checkpoint", + "Use the correct playbook and supporting content" + ], + "must_not": [ + "Treat generated output as completed execution", + "Restart or skip steps without explaining the saved state" + ] + } +] diff --git a/tests/advisory.test.js b/tests/advisory.test.js new file mode 100644 index 0000000..6daa311 --- /dev/null +++ b/tests/advisory.test.js @@ -0,0 +1,18 @@ +import test from 'node:test'; +import assert from 'node:assert/strict'; +import path from 'node:path'; +import fs from 'node:fs'; +import { invoke } from '../lib/tools.js'; +const root=path.resolve(import.meta.dirname,'..'); +test('revenue triage delivers evidence guardrails and comparable-period questions',()=>{ + const response=invoke(root,'foreman_diagnose',{area:'revenue'}); + assert.ok(response.includes('does not rule out an acquisition problem')); + assert.ok(response.includes('revenue bridge')); + assert.ok(response.includes('timing alone does not establish causation')); +}); +test('every registered command loads runtime and policy before its source',()=>{ + const files=fs.readdirSync(path.join(root,'.claude/commands')).filter(f=>f.endsWith('.md')); + let count=0; + for(const name of files){const text=fs.readFileSync(path.join(root,'.claude/commands',name),'utf8');if(!text.includes('generated: true'))continue;assert.ok(text.indexOf('policies/advisory.md')=40); +}); diff --git a/tests/content.test.js b/tests/content.test.js new file mode 100644 index 0000000..67ffc9b --- /dev/null +++ b/tests/content.test.js @@ -0,0 +1,51 @@ +import test from 'node:test'; +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { catalog, lookup, validate, frontmatter } from '../lib/content.js'; + +function fixture(t) { + const root = fs.mkdtempSync(path.join(os.tmpdir(), 'foreman-content-')); + t.after(() => fs.rmSync(root, { recursive: true, force: true })); + return root; +} +function skill(root, category, name, extra = '') { + const dir = path.join(root, '.claude/skills', category); fs.mkdirSync(dir, { recursive: true }); + fs.writeFileSync(path.join(dir, `${name}.md`), `---\nname: ${name}\ndescription: A complete test framework\ncategory: ${category}\nversion: 1.0.0\ncomplexity: basic\nstage: [idea]\ntags: []\nrelated_skills: []\nauthor: Test\n${extra}---\n# Test framework\n\nUseful body.\n`); +} +test('validation rejects absent and empty sources instead of returning a zero-file pass', t => { + const root = fixture(t); + assert.ok(validate(root, { layer:'skills' }).errors.length); + fs.mkdirSync(path.join(root,'.claude/skills'), {recursive:true}); + assert.ok(validate(root, { layer:'skills' }).errors.some(x => /Empty/.test(x))); +}); +test('validation scans actual .claude source and catches a malformed new file', t => { + const root=fixture(t); skill(root,'frameworks','example'); + let report=validate(root,{layer:'skills'}); assert.equal(report.files,1);assert.deepEqual(report.errors,[]); + fs.writeFileSync(path.join(root,'.claude/skills/frameworks/broken.md'),'No metadata'); + report=validate(root,{layer:'skills'});assert.equal(report.files,2);assert.ok(report.errors.some(x=>x.includes('Missing YAML'))); +}); +test('YAML parsing rejects malformed syntax, duplicate keys and unclosed frontmatter', () => { + for (const text of ['---\nname: [\n---\n# Bad','---\nname: a\nname: b\n---\n# Bad','---\nname: a']) assert.throws(()=>frontmatter(text)); +}); +test('typed references reject a real item of the wrong kind', t => { + const root=fixture(t);skill(root,'frameworks','example','routes_to_templates: [example]\n'); + assert.ok(validate(root,{layer:'skills'}).errors.some(x=>x.includes('unknown template:example'))); +}); +test('metadata identity and field types are validated', t => { + const root=fixture(t);skill(root,'frameworks','example');const f=path.join(root,'.claude/skills/frameworks/example.md'); + fs.writeFileSync(f,fs.readFileSync(f,'utf8').replace('name: example','name: wrong').replace('stage: [idea]','stage: imaginary').replace('related_skills: []','related_skills: example')); + const errors=validate(root,{layer:'skills'}).errors.join('\n');assert.match(errors,/name must match/);assert.match(errors,/Invalid stage/);assert.match(errors,/must be an array/); +}); +test('known references still require arrays and playbook steps require a complete target',t=>{ + const root=fixture(t);skill(root,'frameworks','example','routes_to_skills: example\nsteps: [example]\n'); + const errors=validate(root,{layer:'skills'}).errors.join('\n'); + assert.match(errors,/routes_to_skills must be an array/); + assert.match(errors,/Each step requires a typed target/); +}); +test('catalog lookup prefers global exact matches and rejects ambiguity, empty names and paths', t => { + const root=fixture(t);skill(root,'ai','ai-emotional-intelligence');skill(root,'frameworks','emotional-intelligence'); + const cat=catalog(root);assert.equal(lookup(cat,'skill','emotional-intelligence').category,'frameworks'); + for (const name of ['', ' ', '../../README','example.md','/tmp/data','intelligence']) assert.throws(()=>lookup(cat,'skill',name)); +}); diff --git a/tests/distribution.test.js b/tests/distribution.test.js new file mode 100644 index 0000000..70ad1ac --- /dev/null +++ b/tests/distribution.test.js @@ -0,0 +1,57 @@ +import test from 'node:test'; +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { initWorkspace, commandMap } from '../lib/distribution.js'; +import { markdownLinks, walk } from '../lib/content.js'; +const root=path.resolve(import.meta.dirname,'..'); +test('every packaged relative Markdown link resolves within its distribution',()=>{ + const base=path.join(root,'plugins/foreman');let count=0; + for (const file of walk(base).filter(f=>f.endsWith('.md'))) for (const href of markdownLinks(fs.readFileSync(file,'utf8'))) { + if (href.includes('$')) continue; + const target=path.resolve(path.dirname(file),decodeURIComponent(href.split('#')[0])); + assert.ok(target.startsWith(base+path.sep),`${file}: escaping ${href}`); + assert.ok(fs.existsSync(target),`${file}: missing ${href}`);count++; + } + assert.ok(count>1900,'must actually validate the complete content and skill links'); +}); +test('native short commands exist and host conflicts are explicitly mapped',()=>{ + const commands=commandMap(root); + for (const name of ['solo','stoic','language','apply','track','progress','foreman-resume']) { + assert.ok(commands.has(name));assert.ok(fs.existsSync(path.join(root,'.claude/commands',name+'.md'))); + } + assert.equal(commands.has('resume'),false); + assert.equal(commands.has('skill'),false); + assert.ok(commands.has('foreman-skill')); + assert.equal(fs.existsSync(path.join(root,'.claude/commands/skill.md')),false,'skill.md must not collapse sibling commands into a single SKILL.md'); + assert.equal(fs.existsSync(path.join(root,'.claude/commands/_schema')),false,'authoring templates must stay outside host command discovery'); + assert.equal(fs.existsSync(path.join(root,'.claude/agents/_schema')),false,'authoring templates must stay outside host agent discovery'); +}); +test('installation preserves existing workspace files and Codex resources resolve',t=>{ + const dir=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-init-'));t.after(()=>fs.rmSync(dir,{recursive:true,force:true})); + fs.writeFileSync(path.join(dir,'CLAUDE.md'),'Existing instructions'); + const first=initWorkspace(root,dir,'all'),second=initWorkspace(root,dir,'all'); + assert.ok(first.copied.length>500);assert.equal(second.copied.length,0); + assert.equal(fs.readFileSync(path.join(dir,'CLAUDE.md'),'utf8'),'Existing instructions'); + assert.ok(fs.existsSync(path.join(dir,'.agents/content/RUNTIME.md'))); + assert.ok(fs.existsSync(path.join(dir,'.agents/skills/foreman/SKILL.md'))); +}); +test('installation refuses linked directories before writing outside the workspace',t=>{ + const dir=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-link-'));t.after(()=>fs.rmSync(dir,{recursive:true,force:true})); + fs.mkdirSync(path.join(dir,'outside'));fs.mkdirSync(path.join(dir,'workspace')); + fs.symlinkSync(path.join(dir,'outside'),path.join(dir,'workspace/.claude')); + assert.throws(()=>initWorkspace(root,path.join(dir,'workspace'),'claude'),/linked destination/); + assert.deepEqual(fs.readdirSync(path.join(dir,'outside')),[]); +}); +test('compiled entry uses the actual installed OpenClaw SDK and registers executable tools',async t=>{ + const {default:plugin}=await import('../dist/index.js');let factory,options; + plugin.register({pluginConfig:{defaultLanguage:'tr'},registerTool:(f,o)=>{factory=f;options=o;}}); + assert.equal(plugin.id,'foreman');assert.equal(typeof factory,'function');assert.equal(options.names.length,10); + const dir=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-sdk-'));t.after(()=>fs.rmSync(dir,{recursive:true,force:true})); + const tools=factory({workspaceDir:dir,agentId:'test'}); + const list=await tools.find(t=>t.name==='foreman_list_skills').execute('test',{}); + assert.equal(JSON.parse(list.content[0].text).entries.length,158); + const bad=await tools.find(t=>t.name==='foreman_apply_skill').execute('test',{skill:''});assert.equal(bad.isError,true); + const profile=await tools.find(t=>t.name==='foreman_profile').execute('test',{mode:'solo'});assert.equal(profile.details.ok,true); +}); diff --git a/tests/maintenance.test.js b/tests/maintenance.test.js new file mode 100644 index 0000000..3f2c49b --- /dev/null +++ b/tests/maintenance.test.js @@ -0,0 +1,44 @@ +import test from 'node:test'; +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { execFileSync } from 'node:child_process'; +import { createContent,renameCategory,bumpVersion,anonymize,checkIndex } from '../lib/maintenance.js'; +import { catalog,frontmatter,markdownLinks } from '../lib/content.js'; +const root=path.resolve(import.meta.dirname,'..'); +function fixture(t){const dir=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-maintain-'));t.after(()=>fs.rmSync(dir,{recursive:true,force:true}));fs.cpSync(path.join(root,'.claude'),path.join(dir,'.claude'),{recursive:true});return dir;} +test('all creators use canonical paths, preserve special authors and reject invalid or duplicate writes',t=>{ + const dir=fixture(t),author="O'Brien & Partners / Research"; + for(const kind of ['skill','template','diagnostic','playbook','hook']) { + const opts={name:`test-${kind}`,category:'frameworks',audience:'self',symptom:['A symptom'],author}; + const result=createContent(dir,kind,opts),file=path.join(dir,result.created),text=fs.readFileSync(file,'utf8'); + assert.ok(result.created.startsWith('.claude/'));assert.equal(frontmatter(text).data.author,author); + assert.throws(()=>createContent(dir,kind,opts),/EEXIST/);assert.equal(fs.readFileSync(file,'utf8'),text); + } + assert.throws(()=>createContent(dir,'skill',{name:'partial',category:'frameworks',complexity:'wrong'})); + assert.equal(fs.existsSync(path.join(dir,'.claude/skills/frameworks/partial.md')),false); +}); +test('category rename keeps identities, rewrites links and is read-only until confirmed',t=>{ + const dir=fixture(t),before=catalog(dir).entries.filter(e=>e.kind==='skill').map(e=>e.id).sort(); + renameCategory(dir,'writing','business-writing');assert.ok(fs.existsSync(path.join(dir,'.claude/skills/writing'))); + renameCategory(dir,'writing','business-writing',true); + const after=catalog(dir);assert.deepEqual(after.entries.filter(e=>e.kind==='skill').map(e=>e.id).sort(),before); + for(const e of after.entries)for(const link of markdownLinks(e.text))assert.ok(fs.existsSync(path.resolve(path.dirname(e.file),link.split('#')[0])),`${e.relative}: ${link}`); + assert.throws(()=>renameCategory(dir,'frameworks','business-writing',true)); +}); +test('version and author edits handle zero matches and leave files unchanged after invalid arguments',t=>{ + const dir=fixture(t),file='.claude/skills/frameworks/emotional-intelligence.md'; + const before=fs.readFileSync(path.join(dir,file),'utf8'); + assert.throws(()=>bumpVersion(dir,{file,to:'v3'}));assert.equal(fs.readFileSync(path.join(dir,file),'utf8'),before); + bumpVersion(dir,{file,to:'2.0.1'});assert.equal(frontmatter(fs.readFileSync(path.join(dir,file),'utf8')).data.version,'2.0.1'); + assert.deepEqual(anonymize(dir,{name:'Nobody & Nowhere / Unknown',apply:true}),{files:0,occurrences:0,applied:true}); +}); +test('pre-commit validates the staged blob, accepts README, and ignores unstaged repairs',t=>{ + const dir=fixture(t),git=args=>execFileSync('git',args,{cwd:dir,encoding:'utf8'}); + git(['init','-q']);fs.writeFileSync(path.join(dir,'README.md'),'# Documentation\n');git(['add','README.md']); + assert.equal(checkIndex(dir).errors.length,0); + const file=path.join(dir,'.claude/skills/frameworks/emotional-intelligence.md'),original=fs.readFileSync(file,'utf8'); + fs.writeFileSync(file,'---\nname: [broken\n---\n# Broken\n');git(['add','.claude']);fs.writeFileSync(file,original); + assert.ok(checkIndex(dir).errors.some(e=>e.includes('emotional-intelligence.md'))); +}); diff --git a/tests/runtime.test.js b/tests/runtime.test.js new file mode 100644 index 0000000..5877401 --- /dev/null +++ b/tests/runtime.test.js @@ -0,0 +1,61 @@ +import test from 'node:test'; +import assert from 'node:assert/strict'; +import fs from 'node:fs'; +import os from 'node:os'; +import path from 'node:path'; +import { execFileSync } from 'node:child_process'; +import { readState, changeState, updateProfile, updateTask, migrateState, track } from '../lib/state.js'; +import { invoke } from '../lib/tools.js'; + +const root=path.resolve(import.meta.dirname,'..'); +function workspace(t) { const dir=fs.mkdtempSync(path.join(os.tmpdir(),'foreman-state-'));t.after(()=>fs.rmSync(dir,{recursive:true,force:true}));return dir; } +test('profile changes survive a separate process and remain founder-isolated',t=>{ + const dir=workspace(t); + changeState(dir,'alice',s=>updateProfile(s,{mode:'solo',stoic_mode:true,language:'Turkish',sector:'saas'})); + const result=JSON.parse(execFileSync(process.execPath,['bin/cli.js','state','profile','--workspace',dir,'--founder','alice'],{cwd:root,encoding:'utf8'})); + assert.deepEqual(result.identity,{mode:'solo',stoic_mode:true,language:'tr'}); + assert.equal(readState(dir,'bob').identity.mode,'standard'); +}); +test('task lifecycle has actual filters, history, completion and rollback on invalid writes',t=>{ + const dir=workspace(t), update=input=>changeState(dir,'alice',s=>updateTask(s,input)); + update({id:'one',description:'Interview customers',deadline:'2020-01-01'}); + update({id:'one',status:'blocked',note:'Waiting for appointments'}); + assert.equal(track(readState(dir,'alice'),'blocked').length,1); + assert.equal(track(readState(dir,'alice'),'overdue').length,1); + const before=fs.readFileSync(path.join(dir,'.foreman/alice/state.json'),'utf8'); + assert.throws(()=>update({id:'one',progress:101})); + assert.equal(fs.readFileSync(path.join(dir,'.foreman/alice/state.json'),'utf8'),before); + update({id:'one',status:'completed'}); + assert.equal(track(readState(dir,'alice'),'overdue').length,0); + assert.equal(readState(dir,'alice').implementation_items[0].progress,100); + assert.equal(readState(dir,'alice').implementation_items[0].state_history.length,2); + assert.throws(()=>changeState(dir,'alice',s=>s,{expectedRevision:1}),/revision conflict/); +}); +test('invalid identity, corrupt file, and linked state never become fresh memory',t=>{ + const dir=workspace(t); + assert.throws(()=>readState(dir,'../alice'),/identifier/); + changeState(dir,'alice',s=>s); + fs.writeFileSync(path.join(dir,'.foreman/alice/state.json'),'{bad'); + assert.throws(()=>readState(dir,'alice')); + fs.symlinkSync(path.join(dir,'.foreman/alice'),path.join(dir,'.foreman/bob')); + assert.throws(()=>readState(dir,'bob'),/Linked/); +}); +test('legacy fields migrate without losing original data or sharing active aliases',()=>{ + const legacy={identity:{mode_solo:true,mode_stoic:true},preferences:{language:'turkish'},company:{sector:'saas',name:'Acme'},implementation_items:[{id:'old',description:'Research',status:'completed'}]}; + const s=migrateState(legacy,'alice'); + assert.equal(s.identity.mode,'solo');assert.equal(s.identity.stoic_mode,true);assert.equal(s.identity.language,'tr'); + assert.equal(s.identity.mode_solo,undefined);assert.deepEqual(s.legacy,legacy);assert.equal(s.implementation_items[0].progress,100); +}); +test('tools load actual profiles and all simulation personas; checkpoints resume',t=>{ + const dir=workspace(t), options={workspace:dir,defaults:{defaultMode:'solo',defaultLanguage:'tr',sector:'saas'}}; + assert.equal(invoke(root,'foreman_track',{},options).items.length,0); + const skill=invoke(root,'foreman_apply_skill',{skill:'emotional-intelligence'},options); + assert.ok(skill.includes('Source: skills/frameworks/emotional-intelligence.md'));assert.match(skill,/"language":"tr"/);assert.match(skill,/SaaS/i); + const simulation=invoke(root,'foreman_simulate',{type:'board'},options); + assert.match(simulation,/skeptic-investor/);assert.match(simulation,/legal-counsel/); + invoke(root,'foreman_resume',{playbook:'pivot-playbook',next_step:2},options); + assert.equal(invoke(root,'foreman_resume',{},options).next_step,2); + assert.throws(()=>invoke(root,'foreman_resume',{playbook:'pivot-playbook',next_step:999},options)); + assert.throws(()=>invoke(root,'foreman_apply_skill',{skill:'../../README'},options)); + assert.ok(invoke(root,'foreman_list_skills',{kind:'template'},options).entries.some(e=>e.id==='implementation-retrospective')); +}); diff --git a/tsconfig.build.json b/tsconfig.build.json new file mode 100644 index 0000000..8449fb2 --- /dev/null +++ b/tsconfig.build.json @@ -0,0 +1,4 @@ +{ + "extends": "./tsconfig.json", + "compilerOptions": { "noEmit": false, "outDir": "dist", "rootDir": "." } +} diff --git a/tsconfig.json b/tsconfig.json new file mode 100644 index 0000000..aa5434e --- /dev/null +++ b/tsconfig.json @@ -0,0 +1,13 @@ +{ + "compilerOptions": { + "target": "ES2022", + "module": "NodeNext", + "moduleResolution": "NodeNext", + "strict": true, + "allowJs": true, + "checkJs": false, + "skipLibCheck": true, + "noEmit": true + }, + "include": ["index.ts", "lib/**/*.js"] +}